• Important information
• New features
• Known problems
• Program corrections
• User guide corrections
• Miscellaneous
• Release history

Important information

• To enable PTM Trace select On-Chip (ETB/MTB) in Project>Options>Debugger>I-jet/JTAGjet>Trace
  
  If PTM could not be automatically detected, add the option --jet_sigprobe_opt=trace(ETB,baseptm=<base PTM address + access port number>, baseetb=<base ETB address + access port number>) in Project>Options>Debugger>Extra Options
  
  Example where port number is 1, Base PTM address is 0x8009D000 and base ETB address is 0x80001000
--jet_sigprobe_opt=trace(ETB,baseptm=0x8009D001,baseetb=0x80001001)

• Information about I-jet, JTAGjet-Trace, and JTAGjet firmware versions.

• Unlock utilities for EFM32, Kinetis, and LM3S devices are inluded in $EW_DIR$\arm\bin\jet\bin as Windows batch files. They are run without parameters. Please make certain that the correct utility is used, according to the available debugger interface (JTAG or SWD).

• Unlock utilities for STM32 devices are provided as C-SPY macros found in the Macro Quicklaunch window.

• To debug a multi-core system using multiple instances of the C-SPY debugger that accesses the same I-jet debug probe, add the option
  --jet_sigprobe_opt=shared in Project>Options>Debugger>Extra Options. Note, this must be done in all Embedded Workbench projects.

• To trace a core with ETM Trace other than core 0 in a multicore SMP system, add the option
  --trace_from_core=<core number> in Project>Options>Debugger>Extra Options.
  
  For Xilinx Zynq 7000 devices also add the option --macro_param trace_core=<core number> in Project>Options>Debugger>Extra Options.

New features

• None.

Known Problems

• If two images are loaded, and both contains the __vector_table symbol, then a confusing debug log is generated.
  [EW23506]

• Some devices suffer from I-jet and/or JTAGJet-Trace interoperability problems.
  [EW23746,EW23785,EW23882]

• The Timeline and Event Log windows sometimes show incorrect time.
  [EW23673]

• When debugging with I-jet and selecting "PC Samples" only, "Power (I)" packets will be displayed in the SWO Trace Window as well.
  [EW23684]

• I-jet has problems to debug applications that spend long periods in sleep mode on some devices, for instance on Fujitsu MB9BF506R and Toshiba TMPM369.
  [EW24061]

• ETM data from JTAGjet-Trace might in some cases have missing branch instructions when used with an ARM Cortex device. Near breakpoints, duplicated instructions may also appear in the trace data.
  [EW24112]

• Trace clock calibration might fail (due to silicon errata in some EFM32 devices) when using I-jet Trace, resulting in incorrect trace data.
  [EW25172]

• Setting breakpoints might fail when debugging some multicore systems with one or more disabled cores.
  [EW25468]

• In some cases, for instance when Force PC sampling is checked, power logging might stop working.
  [EW25521, EW25652, EW25694]

• JTAGjet and JTAGjet-Trace does not support SWO. This is a hardware limitation and can not be fixed.
  The I-jet and I-jet Trace debug probes support SWO.

• Current limitations in the MTB (Micro Trace Buffer) implementation
  

  • The Trace Start/Stop/Filter breakpoints are not supported in MTB.

  • The timestamps for MTB trace records come from a simple counter and have no relation to CPU/clock cycles. Any conversion between cycles and time for MTB trace data will be misleading. The Call Stack graph in the Timeline window, for example, should not be used to measure time intervals.

  • The MTB trace data sequence might not present discontinuities correctly. Lines in the ETM Trace window (also used for MTB trace) might be marked as discontinuous, i.e. red, even though the trace sequence is contiguous. Conversely, trace data from a buffer that has overflowed will not always be marked as discontinuous. This is mostly a cosmetic problem, except for the Call Stack graph in the Timeline window, which only displays the latest continuous sequence of trace data.

  • The ETM Trace window (and related windows) are used for all variants of full instruction trace, ETM, ETB, and MTB.

• Updates of the Function Trace window can be slow when the application is executing loops without any function calls. Applications that spend most time in a tight loop waiting for events fall into that category.

Program Corrections

• None.

User guide corrections

• None.

Miscellaneous

• None.

Release history

V7.70 2016-06-17

Program corrections

• I-jet and I-jet Trace now have trace support for single core tracing of Vybrid devices.
  [EW24813]

• SWO/ITM is now supported on Toshiba TMPR454 with I-jet and I-jet Trace.
  [EW24828]

New features

• None.

V7.60 2015-03-31

Program corrections

• With I-jet Trace, Flat time is sometimes longer than Accumulated time.
  [EW26010]

New features

• Flash breakpoints
  Flash breakpoints adds unlimited number of breakpoints for selected Cortex-M devices when using the I-jet debug probe. A flash breakpoint must be set explicitly from the context menu. To find out if flash breakpoints are supported for your device, see the semiconductor vendor specific device lists below.

• cJTAG support
  The IAR C-SPY Debugger now supports the cJTAG interface on the TI connectivity devices CC13xx/2538/26xx when using the I-jet debug probe.

V7.50 2015-11-10

Program corrections

• Corrected problem where I-jet would sometimes fail to connect to STM32 cores that were in sleep mode and never woke up.
  [EW25783]

New features

• None.

V7.40 2015-02-19

Program corrections

• Function trace is now processed correctly when using I-jet Trace. Note, this requires update of I-jet Trace firmware to at least version 3.2. Read more in Information about I-jet, JTAGjet-Trace, and JTAGjet firmware versions.
  [EW25140, EW25141]

• In EWARM 7.40.2:
  ETM/ETB trace support for I-jet/JTAGJet-trace added for Toshiba TMPR454.
  [EW24829]

• In EWARM 7.40.2:
  When debugging devices with a faulty ROM table, a connection error was reported instead of trying to connect.
  [EW25261]

• In EWARM 7.40.3:
  The private peripheral bus memory range and its registers are shown with incorrect byte order for Cortex-M devices with BE32 byte order when using I-jet (for example TMS470M06607).
  [EW24604]

• In EWARM 7.40.3:
  I-jet Trace revisions A and B do not have external pull-up on the nRESET line. When connecting to a device where the nRESET line is not connected, a 100K pull-up resistor should be used on the probe pin, connected to Vref. This external pull-up is present in I-jet Trace revision C.
  [EW25203, EW25420]

• In EWARM 7.40.3:
  Connecting to a Kinetis L may sometimes fail when using I-jet.
  [EW25293]

• In EWARM 7.40.3:
  The I-scope detection and initialization mechanism is now working correctly.
  [EW25376]

• In EWARM 7.40.3:
  MPU_CTRL is now handled correctly.
  [EW25436]

• In EWARM 7.40.3:
  DAP read commands did not return a value, leading to type mismatch if used.
  [EW25469]

• In EWARM 7.40.5:
  ETM trace now works with JTAGjet-Trace.
  [EW24267]

• In EWARM 7.40.5:
  I-jet could fail to set up stimulus port permissions properly on some Cortex-M7 devices causing ITM to fail. This affected stdio/stderr over SWO.
  [EW25364]

• In EWARM 7.40.5:
  An encoding error caused MVFR0 and MVFR1 to be swapped during a register access.
  [EW25522]

• In EWARM 7.40.5:
  The C-Spy I-jet/JTAGjet driver can now find the address of the __vector_table symbol when it is a struct.
  [EW25561]

• In EWARM 7.40.5:
  Entering wait mode and backup mode on a SAM4S device (and models with the same sleep modes) will no longer yield fatal errors, and I-scope measurements will not stop while in these deep sleep modes.
  [EW25581]

• In EWARM 7.40.5:
  Software breakpoints are verified and a message is now given when memory contents are damaged while trying to set a software breakpoint. To avoid this you should use hardware breakpoints instead.
  [EW25586]

New features

• None.

V7.30 2014-09-24

Program corrections

• Unlocking of Kinetis L and E devices has been added, as a C-SPY macro.
  [EW24397]

• In EWARM 7.30.3:
  Power samples are no longer dropped on devices without SWO/TPIU when debugging with I-jet/I-scope.
  [EW24959]

New features

• None.

V7.20 2014-05-19

Program corrections

• Power logging now survives a reset.
  [EW24554]

• SWD mode could not be selected for Cortex A/R.
  [EW24630]

• Multicore slave probe configuration is not inherited from the master configuration.
  [EW24684]

• In EWARM 7.20.2:
  A problem that made it impossible to debug an AMP multicore application has been corrected.
  [EW24743]

• In EWARM 7.20.2:
  The debugger no longer terminates unexpectedly when trying to initialize ETM trace with a 1 bit port width. (The only port width supported in JTAGjet Trace is 4 bits.)
  [EW24779]

• In EWARM 7.20.5:
  The number of HW breakpoints is no longer limited to six for Cortex-R4.
  [EW24638]

• In EWARM 7.20.5:
  An intermittent problem when debugging with JTAGjet, related to a newer version of Windows USB drivers, has been fixed.
  [EW24750]

• In EWARM 7.20.5:
  The SWO interrupt log is now correctly handled on devices with slow SWO clock.
  [EW24840]

• In EWARM 7.20.5:
  Debugger reads of memory on Cortex-A when cache is enabled now shows the correct values.
  [EW24857, EW24780, EW24796]

• In EWARM 7.20.5:
  Software breakpoints are restored at main() in CM408F example project Button_LED_GPIO.
  [EW24866]

New features

• None.

V7.10 2014-02-21

Program corrections

• A data breakpoint with Match Data on Cortex-M0 might cause the debugger to terminate unexpectedly, and might also make the EWARM project file corrupt.
  [EW24307]

• When debugging an ARMv7-R/A core, and stepping on a branch to self instruction, the C-SPY driver reports Unknown stop condition or CPU is running.
  [EW24419]

• C-SPY is now able to read the FPSCR register on Cortex-M with FPU extension.
  [EW24496]

• In EWARM 7.10.3:
  The option Restore software breakpoints at did not work as expected after reset. It has now been corrected.
  [EW24498]

• In EWARM 7.10.3:
  I-jet correctly disables cache on Vybrid on a software reset.
  [EW24562]

New features

• None.

V6.70 2013-10-29

Program corrections

• The I-jet in-circuit debugging probe now operates more smoothly when the host system is a one-core Windows XP computer.
  Note, make sure to update I-jet firmware to 4.2 or later. Read more in Information about I-jet, JTAGjet-Trace, and JTAGjet firmware versions
  [EW23848, EW24016]

• The C-SPY driver now reports the correct CPUID in the Debug Log window.
  [EW24199]

• The C-SPY driver now access CP15 registers correctly when debugging a Faraday FA606TE.
  [EW24213]

• In EWARM 6.70.2:
  Setting a breakpoint directly on a vector in the interrupt vector table no longer disables the interrupt.
  [EW24230]

• In EWARM 6.70.2:
  Custom reset strategies are now available for NXP LCP23xx and LPC24xx devices.
  [EW24253]

New features

• None.

V6.60 2013-06-27

Program corrections

• ETM trace is now working when debugging a TMDXRM48HDK with JTAGjet-Trace.
  [EW23843]

• Terminating a debug session while the Terminal I/O window still prints, no longer causes the debugger to crash.
  [EW23893]

• I-Jet can now download to flash on an ADuC7026. If this problem persists, open the I-jet/JTAGjet>Memory Configuration dialog box, in the Used Ranges pane, define the Cache Type of memory in range 0-0xF7FF as ROM/Flash.
  [EW23932]

• MTB trace now works also when power logging is active.
  [EW23951]

• The unlock scripts now run without doing a license check.
  [EW23955]

• Debug mechanisms are now kept enabled in sleep mode on STM32 devices. This is done through STM32-specific C-SPY macros.
  [EW23998, EW24011, EW24021]

• In EWARM 6.60.2:
  I-jet now supports ETB trace when debugging on Cortex-M4.
  [EW23748]

• In EWARM 6.60.2:
  Improved wording and nature of a warning message.
  [EW24063]

• In EWARM 6.60.2:
  Stability when receiving ETM trace data from a Kinetis K60 is improved.
  [EW24073]

• In EWARM 6.60.2:
  EmuDiag can now update the firmware in JTAGjet-Trace.
  [EW24082]

• In EWARM 6.60.2:
  Using BE8 big-endian mode and I-jet no longer gets the application to malfunction when hitting a software breakpoint.
  [EW24092]

• In EWARM 6.60.2:
  The unlock scripts, Kinetis_unlock_jtag.bat and Kinetis_unlock_swd.bat now work on Freescale Kinetis devices.
  [EW24125]

New features

• None.

V6.50 2012-11-10

Program corrections

• The C-SPY driver for I-jet is now enhanced to serve JTAGjet as well.
  [EW23152]

• Debugging on Freescale i.MX25 is now possible without workaround.
  [EW23364]

• In EWARM 6.50.3:
  It is now possible to use CSpyBat with the I-jet/JTAGjet debugger driver.
  [EW23504]

• In EWARM 6.50.3:
  The intrinsic function __WFI is now handled correctly in I-jet.
  [EW23533]

• In EWARM 6.50.3:
  If you set up I-jet not to supply the target board with power, power delivery to the target board will now stop when the debug session starts.
  [EW23633]

• In EWARM 6.50.3:
  When SWO interrupt information packets have to be dropped because of excessive amounts of data, this is now handled gracefully.
  [EW23675]

• In EWARM 6.50.3:
  Pressing Reset just when the CPU has started autonomously no longer causes a deadlock.
  [EW23693]

• In EWARM 6.50.3:
  Interrupts are now logged and presented correctly in C-SPY windows. (However, the interrupt specifications in the Freescale SVD files are not correct, so the naming of such interrupts might be misleading. See EW23788 for more information.)
  [EW23694]

• In EWARM 6.50.3:
  Running EmuDiag.exe no longer requires administrator privileges.
  [EW23695]

• In EWARM 6.50.5:
  It is now possible to download and verify with I-jet on LPC2103. Note however that it might be necessary to add an execUserPreload macro to set MEMMAP to the proper value, 1 for a flash configuration and 2 for a RAM configuration.
  [EW23652]

• In EWARM 6.50.5:
  It is now possible to set a breakpoint when running on a Freescale Kinetis K60.
  [EW23692]

• In EWARM 6.50.5:
  The example projects for Spear3xx are now adapted to I-jet/JTAGjet.
  [EW23794]

• In EWARM 6.50.5:
  It is now possible to debug AM335x with I-jet and JTAGjet.
  [EW23806]

• In EWARM 6.50.5:
  JTAGjet-trace now handles trace data (ETM) correctly when debugging on STM32F407ZG-SK.
  [EW23899]

• In EWARM 6.50.6:
  Match data for data breakpoints is no longer ignored by I-jet.
  [EW23505]

• In EWARM 6.50.6:
  The C-SPY driver for I-jet now handles SWO on MB9AFB44N correctly.
  [EW23595]

• In EWARM 6.50.6:
  Data log is now working when debugging on MB9BF506R.
  [EW23708]

• In EWARM 6.50.6:
  The C-SPY driver for I-jet now handles FPU registers correctly.
  [EW23778]

• In EWARM 6.50.6:
  C-SPY now behaves robustly when the ETM signal from the device is unstable.
  [EW23786]

• In EWARM 6.50.6:
  The last ITM event log before execution is stopped at a breakpoint, is no longer missing.
  [EW23832]

• In EWARM 6.50.6:
  Power sampling now works for devices without SWO.
  [EW23876]

• In EWARM 6.50.6:
  ITM logging is now intact, also when Power sampling is not active.
  [EW23879]

• In EWARM 6.50.6:
  C-SPY can now download an image to a K60 device.
  [EW23931]

New features

• In EWARM 6.50.5:
  Unlock utilities for EFM32, Kinetis and LM3S devices are inluded in $EW_DIR$\arm\bin\jet\bin as Windows batch files. They are run without parameters. Please make certain that the correct utility is used, according to the available debugger interface (JTAG or SWD).

• Support for MTB (Micro Trace Buffer)
  The MTB trace mechanism gives access to instruction trace on devices based on the Cortex-M0+ core.

V6.40 2012-06-05

Program corrections

• THUMB breakpoints that end up in the same 32-bit word are now handled correctly by C-SPY.
  [EW23243]

• When debugging on an AM1808 device with I-jet you no longer get warnings about misplaced SFRs.
  [EW23289]

• In EWARM 6.40.5:
  I-jet now works with TMS470R1B1M.
  [EW23310]

• In EWARM 6.40.5:
  C-SPY no longer terminates unexpectedly when closing a debug session.
  [EW23370, EW23531]

• In EWARM 6.40.5:
  I-jet now works with LPC2138. Note, reset strategy must be set to "Hardware" or "Software".
  [EW23427, EW23442, EW23443]

• In EWARM 6.40.5:
  Turning on "Power Sampling" in the Function Profiler window could sometimes cause a crash, e.g. if Profiling was turned on already when launching a debug session, but Power Sampling was turned on later. This has been fixed.
  [EW23509]

• In EWARM 6.40.5:
  Creating or editing configurations in the Memory Configuration dialog box when running a session in Japanese could cause IAR Embedded Workbench to exit unexpectedly. This has been corrected.
  [EW23513]

• In EWARM 6.40.5:
  I-jet now works with LPC2378. Note, reset strategy must be set to "Hardware" or "Software" and JTAG/SWD speed must be set to "Adaptive".
  [EW23515]

New features

• None.

V6.30 2011-10-22

Program corrections

• None.

New features

• None.

• None.