IAR Information Center for Arm

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

Important information

Driver Specific ReleaseNotes from before EWARM 8.20

The ARMv8-M Simulator does not fully support Secure and Non-secure mode.
New behaviour in assert() (new in 7.10.1)
The assert() function will now launch a dialog box, letting the user choose Abort, Debug, or Ignore.
If the old behaviour is wanted, then add the following to your application source code:
```
void __aeabi_assert(char const * msg, char const *file, int line)
{
  printf( "%s:%d %s -- assertion failed\n", file, line, msg );
  abort();
}
```
The C-SPY macro __loadModule(filename, suppress) has been renamed to __loadImage(patch, offset, debugInfoOnly).
The C-SPY macro __sleep(microseconds) has been replaced with __delay(milliseconds). Note the different time resolution.
C-SPY in IAR Embedded Workbench for ARM comes with an improved mechanism and configuration scheme for the flash loader function. An existing project that employs a flash loader with a legacy configuration, will be automatically migrated to the new scheme with default settings. The default settings will in most cases be sufficient. Old settings are converted to a new configuration file (with the extension .board) and may be used if the default settings are not appropriate. Read more about the new mechanism and configuration scheme for flash loaders in the Flash Loader Guide.
Before using CMSIS-DAP with an mbed device (for example LPC1768), read the technical note 69741.

New features

Debugging can now be done by using the ST-LINK server.
To use the ST-LINK server, do the following steps:

1. Ensure that the server has been installed.
The ST-LINK server is provided in the arm\drivers\ST-Link directory.
To install the server, run st-stlink-server.1.0.6-1.msi in administrator mode.

2. In your project, enable the Shared mode option, which is done in Project>Options>Debugger>ST-LINK>Setup

Known Problems

[EWARM-5724, EW26591] Source level debugging for functions (or assembly routines) placed at address zero is not supported. Instruction level stepping and breakpoints work, but source level stepping and breakpoints do not.
[EWARM-5694, EW26535] A file named JLinkARM.dll in C:\Windows\SysWOW64 or C:\Windows\system will give the error message armjlink2.dll The specified procedure could not be found. Remove this file and the problem will disappear.
[EWARM-5364, EW25944] Editing in the Memory Window with slow connection to the debug probe may write inconsistent data
[EWARM-5320, EW25847] Performing a hardware reset when debugging with an Atmel JTAGICE3 probe may cause the probe to become unresponsive. Disconnect and reconnect the probe and avoid using hardware reset.
[EWARM-5172, EW25521] In some cases, for instance when "Force PC sampling" is checked, power logging does not work. (include #25652 and #25694)
See also EWARM-5238, EWARM-5238, EWARM-5254, EWARM-5254
[EWARM-5148, EW25468] Setting breakpoints may fail when debugging some multicore systems with one or more disabled cores.
[EWARM-5113, EW25403] There could be a deadlock in the disassembly window when a breakpoint invokes a conditon macro, where the macro tries to manipulate breakpoints.
See also EWARM-5115, EWARM-5115
[EWARM-5017, EW25172] Trace clock calibration may fail (due to silicon errata in some EFM32 devices) when using I-jet Trace, resulting in incorrect trace data.
[EWARM-4977, EW25079] When C-SPY is used to attach to a running ThreadX application, the Task List window will not show the current tasks after halt.
[EWARM-4945, EW24984] In some situations, stepping out from an interrupt handler might cause the debugger to loose the connection to target.
[EWARM-4877, EW24834] After stepping over a statement that changes the value of the current stack pointer (for example by way of changing which SP that is the current SP) the execution might not stop as expected.
[EWARM-4796, EW24661] In some rare cases, code is shown as data in the Disassembly window.
[EWARM-4774, EW24591] If the embOS plugin is enabled, the contents of Locals window might fail to refresh when the execution stops.
[EWARM-4572, EW24089] If you enable Code Coverage in the Disassembly window, it might be incomplete unless you also enable the Function Profiler and choose "Source Trace (flat)" from the context menu in the Function Profiler window.
[EWARM-4555, EW24061] I-jet has problems to debug applications that spends long periods in sleep mode on some devices, for instance Fujitsu MB9BF506R and Toshiba TMPM369.
[EWARM-4552, EW24054] The dissasembly window might under certain circumstances reappear inadvertently.
[EWARM-4504, EW23914] C-SPY accesses Freescale Vybrid flexbus address range before the flexbus clock is enabled. This causes a bus error which makes the cpu unresponsive. A workaround is provided in EWARM 6.60.2: Excluding the address range for J-Link with a C-SPY macro and with a memory configuration change for I-jet will prevent reads from the flexbus address range.
[EWARM-4398, EW23684] When debugging with I-jet and selecting "PC Samples" only, "Power (I)" packets will be displayed in the SWO Trace Window as well.
[EWARM-4395, EW23673] The timeline and event log windows sometimes show wrong value for I-Jet probes.
[EWARM-4208, EW23161] Every debug session in the simulator "costs" about 500 kb RAM.
[EWARM-4171, EW23060] Environment variables are not expanded the same way in cspybat as in the IDE.
[EWARM-4165, EW23048] Timeline window cannot scroll to 0us with the scroll bar at Zoom setting 10ns.
[EWARM-4122, EW22933] The "Task List" window, column "Max" (and "Max %") display a value that is 4x the correct value in the uC/OS-II RTOS awareness plug-in.
[EWARM-4086, EW22839] When reading the FIQ register group in the XDS100 debugger driver, wrong values are achieved. The actual behaviour depends on the current cpu mode. This will cause the stack checking to give false warnings in the log window. A workaround is to turn off the stack checking from the menu Tools->Options->Stack and disable all stack options.
[EWARM-4056, EW22779] In same cases it is difficult to disable power sampling in the debugger. If the status text box for PC Sampling in the SWO Configuration dialog says "ON: PC Sampling for Power Logs", then the power sampling may be disabled by 1. Enable Function Profiling, 2. Right-click in the Function Profiler window and un-check Power Sampling.
[EWARM-4006, EW22550] Sometimes when starting a new debug session using J-Trace CM3 with the STM32F207ZG-SK board, you can get the error "No trace frequency measured" depending on if debugging with trace was recently performed. Just click on OK to continue.
[EWARM-4000, EW22529] Sometimes the value of a float type placed in a packed struct is displayed incorrectly.
[EWARM-3989, EW22487] A static variable, defined in more than one source file, will become ambiguous if a pre-include file is used by the compiler.
[EWARM-3388, EW20207] An array located at an absolute address is displayed in the watch window as a single int instead of an array. Problem does not occur if variable is located at a user defined segment.

Program Corrections

[EWARM-6157] The J-Link reset strategies "Hardware NXP LPC" and "Atmel AT91SAM7" are not available, despite being described in the documentation.

User guide corrections

None.

Miscellaneous

APB/AHB access ports available as memory zones

APB/AHB access ports that implement the MEM-AP architecture are now accessible as memory zones, and can be accessed through the Memory window, Debugger macros window, and the Register window using custom DDF files.

The zone names are:
- AP_Memory: The currently selected port.
- AP0_Memory - AP5_Memory: Shows ports 0 through 5.
The behavior of the access to these zones might be unpredictable when the selected port does not exist, is not a MEM-AP architecture, or if it's inaccessible for other reasons.
At the moment, these zones are only accessible when using the C-SPY I-jet driver, or the C-SPY CMSIS-DAP driver.

Release history

V8.20 2017-10-16

Program corrections

In EWARM 8.20.2
[EWARM-5968] The semihosting call SYS_ELAPSED writes an incorrect value if the value is larger than 0xFFFF.
[EWARM-5903] Attach to running target fails for devices with ECC RAM, for instance STM32F051R8.
[EWARM-5880] Under certain circumstances, spurious extra calls to host emulated C runtime library functions could occur in conjunction with regular such calls, causing unexpected and misleading error messages.
[EWARM-5853] Support for the nPRIV bit is missing for Cortex-M0+ in the Armv6 architecture.

New features

None

V8.11 2017-04-11

Program corrections

The simulator now throws a HardFault error when doing Unaligned accesses on a Cortex-M0/M0+
[EW26209]

New features

None.

V8.10 2017-03-10

Program corrections

When downloading an executable where some modules are produced by gcc, the debugger can terminate with an internal error.
[EW26384]

New features

None.

V7.80 2016-10-17

Program corrections

In EWARM 7.80.1:
A threadx task name could be corrupted when viewed in the threadx plugin if the string containing the name is stored near the end of memory.
[EW26211]
In EWARM 7.80.4:
It is not possible to debug on some Cortex-M0+ and Cortex-M7 based STM32 devices with I-jet, ST-Link, or J-Link. This error is issued:
Driver: Fatal Error: The selected device does not match the target device. Session aborted!
[EW26369]

New features

None.

V7.70 2016-06-17

Program corrections

None.

New features

None.

V7.60 2015-03-31

Program corrections

The Simulator crashes when using forced interrupt to generate SVC interrupt.
[EW25877]
The flash loader for STM32L151VD-X does not work.
[EW25974]
In EWARM 7.60.2
The CPU races when C-stepping out of an interrupt handler on Cortex-M.
[EW22343]
In EWARM 7.60.2
The Function Profiler and the Call Stack graph in the Timeline window both depend on identifying function calls and function returns in a traced instruction sequence. Problems can appear as an unbalanced graph, or as incorrectly attributed call counts in the profiler. This identification has been improved for certain sequences.
[EW26040]

New features

None.

V7.50 2015-11-10

Program corrections

In EWARM 7.50.2
CMSIS-DAP: Fixed the handling of the CSW register for Cortex-M7.
[EW25781]
In EWARM 7.50.3:
ST EEPROM flash loaders would fail to write correctly when the starting offset of the data was not 0.
[EW25899]
In EWARM 7.50.3:
Some Freescale Kinetis K devices could not be connected to using CMSIS-DAP.
[EW25910]
In EWARM 7.50.3:
Corrected ACTLR bit defintions for Cortex-A9.
[EW25912]

New features

None.

V7.40 2015-02-19

Program corrections

Variables in the Live Watch window might be marked red even though their values remain unchanged through several updates of the window.
[EW23114]
It is not possible to run the C-SPY simulator from Eclipse.
[EW25160]
Corrected missing interrupt names in the interrupt log for devices using SVD device description files.
[EW25190]
In EWARM 7.40.2:
The PC could sometimes be set to an incorrect value when using Download and Debug in certain situations.
[EW24825]
In EWARM 7.40.3:
The CMSIS-DAP support on Vybrid is improved.
[EW24616]
In EWARM 7.40.3:
The CMSIS-DAP driver is now correctly identified in C-SPY.
[EW24949]
In EWARM 7.40.3:
The ES1.21 CC3200 device is now a separate device, different from the generic CC3200 device. This is to correct inconsistencies in the linker configuration file.
[EW25307]
In EWARM 7.40.3:
When simulating pairwise SIMD operations, for example VPADD and VPMAX, the result is now correctly distributed in the D registers.
[EW25341]
In EWARM 7.40.3:
The SWO initialization macro for TI CC2538 is now correct.
[EW25352]
In EWARM 7.40.3:
The simulator now continues correctly when it returns from an interrupt inside the IT state.
[EW25353]
In EWARM 7.40.3:
CMSIS DSP libraries with support for FPU are now built with the correct parameters.
[EW25372]
In EWARM 7.40.3:
The memory configuration for EFM32GG is corrected.
[EW25400]
In EWARM 7.40.3:
The default reset strategy for online reset was not set to software in some cases for I-jet and CMSIS-DAP.
[EW25404]
In EWARM 7.40.3:
The C-SPY macros for ETM initialization on Kinetis W2x series devices are now working correctly.
[EW25435]
In EWARM 7.40.3:
Bit Banding is now working correctly in the simulator.
[EW25444]
In EWARM 7.40.5:
Attach to program is now working when debugging on ARM7 and ARM9.
[EW22435]
In EWARM 7.40.5:
Instability has been observed in some cases when using the RTOS awareness plugin for FreeRTOS.
[EW24317, EW25433]
In EWARM 7.40.5:
Setting/editing a data log breakpoint now works correctly.
[EW25386]
In EWARM 7.40.5:
Fixed a problem with debugging projects with only an externally built executable and debug info from an extra image.
[EW25479]
In EWARM 7.40.5:
CMSIS-DAP: C-SPY would sometimes crash when trying to attach to the same probe using multiple instances of IAR Embedded Workbench.
[EW25515]
In EWARM 7.40.5:
Too long texts in a tooltip could cause a crash. Now a text that does not fit is truncated.
[EW25525]
In EWARM 7.40.5:
If a program contains several different unnamed structure types with equally named and typed fields, but with different offsets, the debugger can display some of the structure types incorrectly.
[EW25545]
In EWARM 7.40.5:
Using more than 50 register groups would in some cases make C-SPY not to start correctly.
[EW25569]
In EWARM 7.40.5:
The Disassembly window now displays the labels of byte-long variables on odd addresses.
[EW25633]
In EWARM 7.40.5:
Saving the contents of the Interrupt Log window to a file now includes the Execution Time field.
[EW25649]
In EWARM 7.40.7:
An error in retrieving the current locale could load the wrong code page, thus misinterpreting non-ASCII characters.
[EW25720]
In EWARM 7.40.7:
When the ThreadX plugin was enabled C-SPY might crash unexpectedly when stopping at, for example, a breakpoint, even if the plugin was not being used.
[EW25737]

New features

None.

V7.30 2014-09-24

Program corrections

Fixed in new firmware. Use firmware in arm\drivers\pemicro\OpenSDA\DEBUG-FRDM-K64F_Pemicro_v108a_for_OpenSDA_v2.0.bin.
Use system reset and disable watchdog manually if needed.
[EW24841]
The simulator now simulates the SMMLS(R) instruction correctly.
[EW24912]
In EWARM 7.30.3:
If you use the same name for a variable as for a type, the Watch and Quick Watch windows will fail to evaluate such a variable or an expression containing it.
[EW19334, EW21566, EW25058]
In EWARM 7.30.3:
Additionally selectable memory zones do not work properly in some C-SPY drivers.
[EW24914]
In EWARM 7.30.3:
Data Log graph settings in the Timeline window are not preserved.
[EW24953]
In EWARM 7.30.3:
Expanding a pointer to function in the Watch/Quickwatch window might cause the debugger to crash.
[EW24989, EW25014, EW25016]
In EWARM 7.30.3:
Sometimes the automatic update of the Code Coverage window fails to mark executed statements as executed.
[EW25010]
In EWARM 7.30.3:
The FPCA bit in the CONTROL register is incorrectly masked away on access in some C-SPY drivers.
[EW25047]
In EWARM 7.30.3:
The message box caused by an assertion is not modal. This means that it is possible to execute other commands, which could lead to a crash.
[EW25070]
In EWARM 7.30.4:
The simulator now handles the CONTROL.FPCA bit correctly.
[EW25048]
In EWARM 7.30.4:
The ThreadX plugin now lets conditional breakpoints stop when a specific task is active.
[EW25127]

New features

None.

V7.20 2014-05-19

Program corrections

It is not possible to view a variable in the Watch window as a 64-bit signed or unsigned integer, because the Watch window does not have the Show As>64-bit Signed and Show As>64-bit Unsigned commands.
[EW24420]
Some objects of a class/struct/union type might be impossible to expand as there is no '+' sign in front of them.
[EW24598]
The menu command View>Cores was disabled even though the project was configured for asymmetrical multicore debugging.
[EW24606]
Selecting certain memory zones in the zone display drop-down list of various C-SPY windows, causes an unexpected termination of C-SPY with the error message "A fatal error has occurred. The debugger will terminate".
[EW24636]
The C-SPY simulator does not simulate Cortex M4F lazy stacking correctly.
[EW24675]
The instructions VFMA, VFMS, VFNMA, and VFNMS are now correctly simulated when using Cortex M4F.
[EW24692]
Simulation of the BFI instruction now produces correct results when LSB is 0 and the width is 32.
[EW24695]
In EWARM 7.20.2:
The instruction UXTAB now produces correct results when simulated in the C-SPY simulator.
[EW24693]
In EWARM 7.20.2:
Simulation of the VCVT instruction is now correct.
[EW24696]
In EWARM 7.20.2:
Adding a C-RUN rule or changing the default C-RUN action caused the IDE to crash when the C-RUN windows were grouped together.
[EW24708]
In EWARM 7.20.2:
The SymList plugin should be loaded by default but is not.
[EW24718]
In EWARM 7.20.2:
The simulator now only checks for denormal exceptions when the FZ bit in the FPSCR register is set.
[EW24726]
In EWARM 7.20.2:
Simulation of the BFC and BFI instructions now works as expected also when all bits are selected (lsb = 0 and width = 32).
[EW24727]
In EWARM 7.20.2:
The simulator now reports the correct number of cycles for the SMLAL instruction.
[EW24735]
In EWARM 7.20.2:
EWARM no longer crashes if using multiple ThreadX Mutexes and displaying the ThreadX plugin Mutex window.
[EW24752]
In EWARM 7.20.2:
Read-only SFRs placed in read-only-mapped memory no longer yield a warning message.
[EW24753]
In EWARM 7.20.5:
Long function names are truncated in the Call Stack window.
[EW24826]
In EWARM 7.20.5:
The Call Stack window leaks resources.
[EW24867]

New features

None.

V7.10 2014-02-21

Program corrections

Architecturally defined core registers, CP14 registers, and CP15 registers are now available in the Register window.
[EW23046,EW23780,EW23919,EW24276,EW24504]
If a problem arises in the download phase the state is now properly reset.
[EW24105, EW24520]
In EWARM 7.10.2:
CMSIS-DAP is now available in 7.10.
[EW24515]
In EWARM 7.10.3:
Very rarely, adding a variable to the Watch window might cause the debugger to exit abnormally.
[EW24398]
In EWARM 7.10.3:
In some cases, using a macro to save target memory to a file might cause the debugger to crash.
[EW24551, EW24553]
In EWARM 7.10.3:
Simulator now gives correct UDIV result when dividend is 0x80000000 and divisor is 0xFFFFFFFF.
[EW24563]
In EWARM 7.10.3:
In the simulator it is not possible to read registers using a # prefix (for instance #PC) in the execUserExecutionStopped() macro.
[EW24569]
In EWARM 7.10.3:
The Simulator does no longer terminate unexpectedly when the target application change to Monitor mode.
[EW24576]
In EWARM 7.10.3:
When debugging with the P&E Micro JTAG probe, verify download sometimes reported "Target inconsistency detected" when code was correcly downloaded.
[EW24579]
In some rare cases data is shown as code in the Disassembly window.
[EW24580]
Sometimes SFR groups might not be shown in the Register window even though they are defined in the device description file (.ddf).
[EW24592]

New features

Reset alternatives
For devices that support multiple reset alternatives, these can now easily be selected from a dropdown list in the tool bar.
Architecturally defined core registers, CP14 registers and CP15 registers are now available in the register window.

V6.70 2013-10-29

Program corrections

When C-SPY stops at a breakpoint, the Go to function button and the insertion point position on the status bar are not visible until you click in the editor window.
[EW24182]
An .svd file that contains extremely long lines might cause the IAR Embedded Workbench IDE to stop responding.
[EW24189]
For devices that support JTAG only or SWD only, the setting is now forced set to the supported mode.
[EW24234]
In EWARM 6.70.2:
When displaying the interrupt log in the Timeline window, the interrupt duration was always displayed in time units, even if Time Axis Unit was set to cycles.
[EW24291]
In EWARM 6.70.2:
If an externally built ELF/DWARF object file contained a struct declared in a function scope prototype, the debugger could exit unexpectedly while downloading the file.
[EW24312]
In EWARM 6.70.2:
Removing a breakpoint while the debugger is executing might make the debugger unstable.
[EW24374]

New features

None.

V6.60 2013-06-27

Program corrections

Expanding a huge array in a debugger watch window could cause an out-of-memory crash. Now array expansion is halted after 5000 elements, but can be continued manually.
[EW23262]
In EWARM 6.60.2:
End of file, EOF, condition on stdin is now handled correctly, causing _read(), fread(), and similar to return the proper status.
[EW24039]
In EWARM 6.60.2:
If you started and stopped the debugger several times during one IAR Embedded Workbench session, a serious memory leak could lead to abnormal termination.
[EW24052,EW24058,EW24081]
In EWARM 6.60.2:
The SVD reader can now handle <cluster> elements that do not contain any dimElementGroup.
[EW24163]

New features

CMSIS SVD cluster elements
The debugger now supports cluster elements in CMSIS System View Description files.
New behaviour in assert() (new in 6.60.2)
The assert() function will now launch a dialog box, letting the user choose Abort, Debug, or Ignore.
If the old behaviour is wanted, then add the following function to your application source code:
```
int __iar_ReportAssert(char const *file, char const *line, char const *func, char const * msg)
{
  printf( "%s:%s %s -- assertion failed\n", file, line, msg );
  return 0;
}
```

V6.50 2012-11-10

Program corrections

The enter/leave indication in the Interrupt log is now correct when there are several simultaneous interrupts.
[EW23457]
32-bit multiplication no longer fails when simulating an A9 processor with Neon and VFP.
[EW23516]
The ETM Trace Window now shows data output when debugging on STM32F4xx.
[EW23560]
In EWARM 6.50.2:
Expressions in the Live Watch window which did not evaluate to a C/C++ lvalue did not update during execution. This has been corrected.
[EW23205]
In EWARM 6.50.2:
The simulator now simulates MOV.W correctly when the register is SP.
[EW23575]
In EWARM 6.50.2:
The simulator now simulates the instructions FSTMIAX and FLDMIAX correctly.
[EW23577]
In EWARM 6.50.2:
The IT/ICI bits in the EPSR register are now cleared when the simulator enters an interrupt.
[EW23600]
In EWARM 6.50.2:
The instruction QDADD now saturates correctly.
[EW23604]
In EWARM 6.50.2:
Some problems that could cause the IDE to freeze terminating a debug session have been corrected.
[EW23618]
In EWARM 6.50.3:
Sometimes, setting a breakpoint in highly optimized code could cause IAR Embedded Workbench to exit unexpectedly. This has been corrected.
[EW23521]
In EWARM 6.50.3:
Setting a breakpoint in a uC/OS-III project could make C-SPY unresponsive. This has been corrected.
[EW23672]
In EWARM 6.50.3:
The uC/OS plugins keep responding even when the event flag group is corrupt.
[EW23723]
In EWARM 6.50.3:
In some cases incorrect project settings caused the debugger to issue an error upon starting, only to exit unexpectedly after the error was corrected. This no longer occurs.
[EW23725]
In EWARM 6.50.3:
Interrupt definitions are now correctly added in C-SPY when the SFR definitions are provided in an SVD file.
[EW23774]
In EWARM 6.50.6:
The driver-specific menu for CMSIS-DAP now has the correct name and content.
[EW23807]
In EWARM 6.50.6:
Executing a Reset command while debugging could lead to a crash if the Stack window was open.
[EW23916]
In EWARM 6.50.6:
Sometimes, when performing the internal integrity check, the flash loader caused a false alarm. This resulted in a long list of incorrect warnings in the flash0.trace file.
[EW23933]

New features

JTAGjet-Trace support
Full support, including ETB and ETM, for the JTAGjet-Trace debug probe from IAR Systems.
Source browser call graph display
The source browser can now display a call graph for easy navigation of the function hierarchy.
Multi-core SWD support
Two instances of IAR Embedded Workbench can now access one core each in a multi-core device via SWD.
New Macro Quicklaunch window for executing macros (and evaluating expressions) on demand.
The debugger drivers for I-jet and TI XDS100 can now handle multiple probes connected to the PC.

V6.40 2012-06-05

Program corrections

Opening the Symbolic Memory window when debugging an RVDS-built application that contains union data members without a location attribute, caused C-SPY to exit unexpectedly. This has been corrected.
[EW23143]
In EWARM 6.40.2:
The default value in Project>Options...>TI XDS100>Setup>TI emulation package installation path is now handled correctly.
[EW23158]
In EWARM 6.40.2:
The IDE could crash when a leaf was double clicked in the Code Coverage window, because of a missing path in the editor view. This has been corrected.
[EW23282]
In EWARM 6.40.2:
The IDE no longer becomes unresponsive when a device description file (.ddf) containing empty sections is opened.
[EW23286]
In EWARM 6.40.2:
Problems with the debugger driver for TI XDS100 has been corrected.
In EWARM 6.40.3:
The Timeline window was not updated correctly when data log breakpoints were enabled/disabled during a debug session. This has been corrected.
[EW22807]
In EWARM 6.40.3:
Setting/clearing breakpoints on the lowest line in the Disassembly window by clicking on the leftmost column now works correctly in all cases.
[EW23040]
In EWARM 6.40.3:
Sometimes the localized (Japanese) strings were garbled in the Watch window. This has been corrected.
[EW23335]
In EWARM 6.40.3:
The Memory window lost focus when editing memory content after entering one unit. This has been corrected.
[EW23340]
In EWARM 6.40.4:
The Symbolic Memory window know behaves correctly after resizing the tabs.
[EW21509]
In EWARM 6.40.4:
C-SPY could misinterpret certain flags in an ELF file such that some read-only segments were considered writable. This could interfere with memory integrity checks when launching a debug session. This has been corrected.
[EW23327]
In EWARM 6.40.4:
When the downloaded application does not contain any C variables (with static storage duration), the I-jet driver will no longer issue a warning about finding no variables in memory designated as RAM.
[EW23440]
In EWARM 6.40.4:
It is no longer possible in the Memory Configuration window to enter an end address that is lower than the start address.
[EW23450]
In EWARM 6.40.4:
Executing the context menu command Force on a vacant area in the Forced Interrupt window caused the debugger to exit unexpectedly. This has been corrected.
[EW23470]

New features

ITM event log
The ITM events can now be plotted as a line graph.
C-SPY macros
Two new C-SPY macros have been added, execUserExecutionStarted(), execUserExecutionStopped(). They can be used for executing C-SPY macro code immediately before starting and immediately after halting program execution.
I-jet memory configuration
The memory access map can be configured in detail to setup caching of regions and block accesses to restricted areas. The default memory configuration can be modified using the Memory Configuration dialog box.

V6.30 2011-10-22

Program corrections

Evaluating a cast expression that contains a plain char, such as (char *)42, when the application does not use the plain char type anywhere, could result in a crash. This has been corrected.
[EW20519]
C-SPY no longer terminates unexpectedly when right-clicking in a ThreadX RTOS plugin view.
[EW22508]
A warning message no longer pops up when debugging an AM1808 device.
[EW22557]
In the Watch window, pointers to Thumb functions are now displayed with the correct function name.
[EW22664]
Single stepping or running to breakpoints when the Call Stack window is open no longer causes the IDE to become unresponsive.
[EW22765]
If you used two or more monitors, ending a debug session with the main IDE window open on one monitor but the Disassembly window on another monitor, IAR Embedded Workbench could terminate unexpectedly when you restarted the debug session. This has been corrected.
[EW22762]
In EWARM 6.30.3:
The debugger no longer terminates unexpectedly during long trace acquisition (several hours) in the Timeline window.
[EW22452]
In EWARM 6.30.3:
The simulator now simulates the SPSR instruction correctly in System mode.
[EW22801]
In EWARM 6.30.3:
A problem in the breakpoint handling in the P&E Micro debugger driver could lead to unexpected behavior when stepping in the source code. This has been corrected.
[EW22838]
In EWARM 6.30.6:
Trying to load a file containing modules produced with gcc no longer causes the IDE to crash.
[EW22866]
In EWARM 6.30.6:
Support for the new CMSIS SVD keyword RESERVED is now implemented.
[EW22895]
In EWARM 6.30.6:
The contents of the Statics window were not filtered when it was opened after the start of a debugging session. The correct contents were not displayed until after a window update (for example after executing a step command). This has been corrected.
[EW22900]
In EWARM 6.30.6:
In some cases, executing multiple Page Up commands in the Disassembly window could cause the code to be disassembled incorrectly. This has been corrected.
[EW22922]
In EWARM 6.30.6:
The Interrupt Log Summary window could show uninitialized content directly after a debugging session started. This has been corrected.
[EW23007]
In EWARM 6.30.7:
It is now possible to set the offset on the Project>Options...>Debugger>Images page to a value greater than 0x7FFFFFFF.
[EW23030]
In EWARM 6.30.7:
It is now possible to use the RDI driver with CSpyBat.
[EW23068]
FreeRTOS 7.1.1 is compatible with the C-SPY FreeRTOS plugin. Read more in FreeRTOS 7.1.1 readme.
(This is not limited to any explicit EWARM version.)
[EW23130]

New features

ETM/ETB selection
It is now possible to chose between ETM and ETB for devices with support for both.

V6.21 2011-07-05

Program corrections

Executing Add to Watch on a selection in the editor window not only opens the Watch window but now also adds an entry to it.
[EW22408]
Disassembly of an unknown address no longer causes the debugger to crash.
[EW22458]
The Stack window no longer crashes upon opening when, under certain circumstances, C-Spy has insufficient information about target system stacks to display stack information as intended.
[EW22486]
In EWARM 6.21.2:
The C-SPY driver for P&E Micro no longer causes the debugger to crash.
[EW22554]
In EWARM 6.21.3:
The checkmark in front of the Mixed-Mode entry on the disassembly window context menu is now displayed correctly.
[EW22604]

New features

Support for Texas Instruments XDS100v2
The Texas Instruments debug probe XDS100v2 is now supported for TI TMS570 devices. To use XDS100v2, select TI XDS100 in the Driver drop-down list on the Debugger>Setup options page. The XDS100v2 debug driver requires the Texas Instruments emulator package to be installed. To install the emulator package, start ...\arm\drivers\ti-xds\ti_emupack_setup.exe and follow the installation procedure. Make sure to install the emulator package in the suggested default location. This will allow the debugger to find the emulator package automatically. If for some reason the package is installed in a custom location, the option --xds_rootdir=path must be specified on the options page Debugger>Extra Options.

V6.20 2011-04-29

Program corrections

Variables of array, struct, union or class type placed at an absolute address are now displayed properly in the Watch window family.
[EW19987]
Correct values are now displayed for the LR and PSP registers in the Register window.
[EW22279]
The simulator now resets the pending bit of the PendSV exception when that exception is executed. It also simulates exception priorities in a better way. Changing exception priorities dynamically and using priority grouping is now supported.
[EW22301]
The 32-bit thumb instruction LDR(literal) is now decoded and simulated correctly for all combinations of operands.
[EW22360]
LSRS R0,R0,#32 is now simulated correctly.
[EW22371]
In EWARM 6.20.4:
Now programming flash works correctly with macro execUserFlashInit().
[EW22473]

New features

None.

V6.10 2010-11-04

Program corrections

There was a redundant warning when the flash loader checked for the presence of arguments. This warning is no longer issued.
[EW21861]
Namespaces could not be used when the IAR C-SPY Debugger resolved names. This has been corrected.
[EW21868]
A variable declared in an assembly file could be given an incorrect address when displayed in a Watch window. This has been corrected.
[EW21873]
The embOS and PowerPac RTOS awareness plugins did not display the Settings and About dialog boxes correctly on Windows7.
[EW21901]
Setting up a Trace/SWO port now leaves other bits in the SFR (e.g. DBGMCU_CR) untouched.
[EW21970]
The last index in a trace is now included when saved to file.
[EW22012]
C-SPY macro __setLogBreak() is now recognized by all relevant debugger drivers.
[EW22030]
Stepping and setting breakpoints now take #line directives into account.
[EW22044]
In EWARM 6.10.2:
The uCOS-II plugin now save settings in the registry subtree HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE.
[EW22109]
In EWARM 6.10.2:
When displaying the CP15 register CPACR in the Register window, the values for the individual bits are now correctly displayed.
[EW22128]
In EWARM 6.10.2:
The IDE no longer crashes if the Message Queues window of the ThreadX plugin contains a lot of messages in a single queue.
[EW22142]
In EWARM 6.10.3:
Type definitions containing pointers to functions no longer produces incorrect debug information that led to unexpected IAR Embedded Workbench termination when the debugger was started.
[EW22176]

New features

Memory region blacklist (new in 6.10.2)
The device description file can optionally specify valid memory regions for a device. User access outside valid regions will be blocked.
New context menu entry in editor while debugging with trace
If Trace is available in a driver, a new context menu item Find in Trace will appear in the editor context menu (when the debugger is running). If you click in source code that corresponds to code in the target, and the trace window is not empty, the menu item will be enabled. If you select it, it will directly search the trace window for occurrences of the given trace data and report the result in the standard Find in Trace window.
Navigating to code from Timeline window and related windows
Existing functionality: Double-clicking in the Timeline window (when it has something to show, of course) will open an editor window with the insertion point at the corresponding source code location, if any. This also happens when double-clicking in some other related windows, such as the Data Log or Interrupt Log windows.
New functionality for the same situation: If the disassembly window is already open, its insertion point will also be positioned at the proper location. If the desired code location has no corresponding source code (and the code thus cannot be shown in an editor window) the code will only be shown in the disassembly window, and this window will then be opened if necessary.
The power log system will show if a log has been produced during processor 'idle' mode
The Power Log window, the PowerStripe tooltip, and the system saving power logs to a file will all be displaying the word 'idle' as the PC value if the target has signalled that the log is generated during idle mode.

V5.50 2010-04-21

Program corrections

In EWARM 5.50.5:
The CMX plugin module now updates the task window when used with J-Link and Cortex-M.
[EW21819]
In EWARM 5.50.6:
When returning from an exception routine executing in ARM to Thumb state, the return pc value was sometimes incorrect in the simulator.
[EW21908]
In EWARM 5.50.6:
The simulation of the instructions QADD, QDADD and QDSUB no longer produces incorrect result for some input values.
[EW21971]
In EWARM 5.50.6:
The debugger no longer terminates with a crasch when the trace-based profiling is activated while the Trace window is closed.
[EW21919]
In EWARM 5.50.6:
The UNPRIV bit in the CONTROL register is now reset correctly in the simulator. This means that the simulator no longer starts in unprivileged mode for Cortex-M3 and Cortex-M4 devices.
[EW21982]

New features

The Function Profiler window can now optionally use a flat sampling method when the input is ETM trace. This will give accurate profiling even in situations where the debugger fails to build a correct call chain, for example when the application uses a RTOS.

V5.41 2009-12-14

Program corrections

The LDREX and STREX instructions are no longer missing in the simulator for Cortex-M3.
[EW19814]
Dragging an expression containing a dereferenced function pointer onto the Memory window no longer causes the debugger to crash.
[EW21390]
Editing a Trace Starting, Stopping or Filter point, set on a source line, no longer results in an error message.
[EW21393]
The CMX RTOS plugin no longer fails if some symbols, for example "queue", are missing in the target project.
[EW21437]
In EWARM 5.41.2:
When simulating the RFE instructon, bits are no longer copied incorrectly from memory to the CPSR register.
[EW21580]
In EWARM 5.41.2:
Code size limitation control in C-SPY no longer includes constant data or data initializers.
[EW21591]

New features

New C-SPY macro function
__targetDebuggerVersion() returns the version of the debugger. This makes it possible to write debugger macro scripts that adapt to different versions of the debugger.

V5.40 2009-07-10

New features

Interrupt definitions in ddf files is available in the interrupt simulation setup dialogs for Cortex-M devices.
These new features have been added to cspybat:
- code coverage
- download only mode
- timeout option
A new C-SPY macro __delay(milliseconds).

Program corrections

The debugger could end up in infinite loops while unwinding call stack.
[EW20280]
Debug information for stepping was off by one line when an include file was completely empty.
[EW20541]
The C-SPY macro __gdbserver_exec_command was missing.
[EW20857]
It is now possible to simulate exceptions with exception numbers below 16 for Cortex-M cores.
[EW20866,EW20867,EW20931]
The possibility to edit interrupt descriptions has been disabled for cores that has only IRQ and FIQ interrupts. This will prevent confusing error messages from appearing.
[EW20868]
A rare problem with downloading files in the Motorola S37 format into the wrong memory location has been corrected.
[EW20964]
In EWARM 5.40.4:
Using the --drv_vector_table_base option no longer causes the flash loader to fail.
[EW21171]
In EWARM 5.40.4:
The Function Profiler now shows correct values.
The disassembly in the trace window is now correct for Cortex-M.
[EW21187]
In EWARM 5.40.4:
The source file paths retrieved from the externally built ELF/DWARF object file are now correctly interpreted by the debugger.
[EW21223]
In EWARM 5.40.4:
Line number information in the debugger is now accurate. Highlighting and breakpoint setting now works correctly.
[EW21268]
In EWARM 5.40.4:
Downloading to flash memory no longer causes the IDE to become unresponsive.
[EW21297]
In EWARM 5.40.4:
Stepping in a complex C++ program no longer causes the displayed source code location not to reflect the current program counter.
[EW21300]
In EWARM 5.40.4:
The CMX plugin no longer fails to detect the CMX RTOS when the RTOS is compiled in thumb mode.
[EW21311]

5.30 2009-01-23

Program corrections

The Auto window is available in this release.
The CMX plugin module uses one breakpoint instead of two during its initialization. This reduces the risk of plugin failure due to lack of hardware breakpoints.
[EW19139]
The result of some floating-point expressions was incorrectly displayed in the Watch window.
[EW20303]
With the Luminary FTDI driver, data breakpoints could only be used right after first download. For any subsequent download, data breakpoints were disabled and could not be enabled.
[EW20360]
CPSID and CPSIE were incorrectly exchanged when disassembling in ARM mode. This has been corrected.
[EW20521]
The MCR instruction was incorrectly disassembled as MCR2. This has been corrected.
[EW20523]
The flash loader based on a previous flash loader framework could not properly be invoked from cspybat.exe. This has been corrected.
[EW20529]
The C-SPY macro __openFile ( input_file, "r+b" ) could earlier fail if the input file had the read-only attribute set. This has been corrected.
[EW20268]
The debugger did not support the semihosting command SYS_FLEN which caused the C library functions fseek() and ftell() to fail. This has been corrected.
[EW20680]
When the Simulator attempted to execute a VFP instruction with VFP disabled (EN in FPSCR), it correctly took the UNDEF interrupt (offset 0x4) but the LR was off by 2 bytes - not 4 bytes as it should. This has been corrected.
[EWARM-169]

5.20 2008-07-11

Program corrections

If an external editor was used in the IDE, it was also used in the debugger. This could make it impossible to set breakpoints in the source code. Now the debugger always uses the built-in editor.
[EW19591]
If the simulator executed a tight loop containing illegal instructions, it would flood the debug log window with error messages and the IDE would hang. This has been corrected.
[EW19815]
The debugger can now read all RealView 3.1 generated ELF/DWARF files.
[EW19868]
Examining a function pointer that is a class member, either with a tooltip or by adding it to the watch window, no longer makes the debugger crasch.
[EW20034]
A multiple failure to open a file using the fopen() library function could use up all available file handles. This no longer occurs.
[EW20102]
For Cortex-M cores, the 16 bit MOV(register) instruction is now simulated correctly when PC is the destination register.
[EW20200]

New features

Debugger startup
You can now start the debugger with or without downloading code, using two new buttons on the toolbar, or two new Project menu commands. There are also two new corresponding ways to restart the debugger during the debug session.

Loading multiple ELF images
The debugger can load multiple ELF images using the C-SPY macro __loadModule().

Symbols window
The Symbols window displays the complete list of symbols used within the project. In contrast to the Source Browser, the list of symbols is not based on project source files but is retrieved from the debug information. This means, that it also lists symbols from libraries that you do not have the source for. It also lists assembler labels, which are not conveniently visible in any other window.

New flash loader mechanism
A new flash loader mechanism is available that adds increased speed and flexibility.

5.11 2007-11-28

Program corrections

The macro function __openFile() now takes all kind of parameters, not only "r" or "w". In particular, it is possible to use the "b" parameter, to open the file in binary mode.
[EW17017, EW19034]
CPSID and CPSIE were exchanged in disassembly for Cortex-M.
[EW18739]
When simulating a core with no system coprocessor (CP15) support, a CP15 instruction could crash the simulator.
[EW19244]
When several compilation units used the same type, a problem with debug information could earlier cause some of the instances of that type to be incorrectly handled by C-SPY. This could cause syntax errors in C-SPY expressions containing the type and also make it impossible to expand its members.
[EW19338, EW19340]
The simulator did not simulate the SVC instruction correctly for Cortex-M cores.
[EW19484]
Corrupted semihosting data structures could cause the debugger to crash.
[EW19507]
In some cases, references were incorrectly shown in the QuickWatch, Watch and Locals windows. This has been corrected.
[EW19542]
Setting a breakpoint in a large switch statement could earlier fail.
[EW19553,19611]
When debugging nested switch statement in ARM mode, the current source code location displayed could be incorrect. This made it look like the wrong case statement was executed.
[EW19681]

New features

Support for the Cortex-M1 core.

5.10 2007-07-02

Program corrections

Cortex-M3 devices were earlier started in unprivileged mode in the simulator.
[EW18742]
The debugger used to crash for code where the base class is a template class.
[EW18999]
C-SPY no longer crashes if a C-SPY macro invoked by a breakpoint deletes the very same breakpoint.
[EW19001]
C-SPY is now able to download a large image to the target.
[EW19855]

V4.41A 2006-12-08

Program corrections

Interrupt simulation was always incorrectly enabled after reload of a project.
[EW18578]

New features

Exporting command line for cspybat
C-SPY now generates a file with helpful information that can be used for running the debugger from the command line using the cspybat utility. Every time the debugger is initialized (technically, it happens when a project is loaded and when terminating a debug session) a bat file is generated that can be used almost without modifications to start cspybat from the command line with the same settings as in the IDE.
The file is generated as $PROJ_DIR$\settings\projectname.cspy.bat

V4.40A 2006-05-18

Program corrections

The CMX plugin could crash the debugger if debug information generation was disabled in project options.
[EW17832]
Debugger testing for read/write memory when setting breakpoints interfered with the ST STR910 flash controller.
[EW17930]
The C-SPY macro __emulatorStatusCheckOnRead() did not work correctly, causing problems when debugging TI TMS470R1B1M.
[EW17992,EW18012]
Some ThreadX views could crash the debugger when running in big endian mode.
[EW18010]
A row with a single newline in the debugger Extra Options dialog crashed the debugger.
[EW18011]
A syntax error message and a macro definition error message appeared erroneously in the debug window under certain circumstances.
[EW18069]

New features

Support for the Cortex-M series has been added
Symbolic Memory window
A symbolic memory window has been added. It displays raw memory contents annotated with any global symbols present.

V4.31A 2006-02-03

Program corrections

The Live watch window is currently only supported by the simulator, and should not be active for other debugger drivers, like JTAG.
[EW15698]
MSR with an immediate operand was disassembled and simulated incorrectly for some immediate values.
[EW17465]
The simulator could errorneously set the processor mode to system mode when running SWI, LDM, STM or BKPT instructions.
[EW17454]
Selecting hardware reset when using a flash loader should give one reset before flashing and a second reset just before starting the application. The second hardware reset was not performed.
[EW17777]

New features

Stack window
To monitor the memory consumption and the integrity of the stack, a new Stack window has been added. It shows the stack contents as raw data, C/C++ variables, and function frames. It also shows current and maximum stack consumption graphically. Warnings can be issued when the stack exceeds a certain level or if the stack pointer points outside the stack memory.
New breakpoint category - Log breakpoint
Log breakpoints make it easy to log messages whenever execution passes a certain code location without having to add any code to the target application. When a log breakpoint is triggered, it writes to the Debug Log window and then the application continues execution.
New way to toggle breakpoints
You can now set or clear a breakpoint by double-clicking in the left margin of the editor window; the breakpoint location is marked by a red X. If there is more than one possible breakpoint location in the source line, the breakpoint is placed on the first location.

V4.30A 2005-06-23

Program corrections

The Memory window now displays "--" for each individual memory unit that cannot be read accessed; as opposed to the whole row.
[EW16446]
Setting data breakpoints in explicitly sized (8/16/32) memory crashed the debugger. [EW16756]
The CMX RTOS plugin could fail to be activated because it did not properly detect the CMX operating system. [EW16890]
The simulation of the SMLAL instruction was incorrect. Upon entry to the instruction the content of the upper word RdHi was lost (RdHi was set equal to RdLo). [EW16902]
When disassembling in Thumb mode, labels were shown on a separate line, with a preceeding blank line. When single-stepping, the blank line was highlighted instead of the line with the current instruction.

V4.20A 2005-01-10

Program corrections

The simulation of the VFP coprocessor could not be disabled by clearing the EN bit in the VFPEXC.
[EW14654]
At certain conditions when debugging for big endian processors C-SPY could crash or stop responding.
[EW15126]
The debugger disassembly wrongly switched to thumb mode 64 bytes after an arm label if the code was followed further down by a thumb label.
[EW15571]
The Analog Devices (ADUC702X) flash programming algorithm failed if the binary image contained gaps.
[EW15780]
Setting breakpoints in C was not possible if the PC did not line up with a statement boundary.
[EW15590]
The simulator incorrectly set the Q-flag when executing SMLAxy or SMLAWy instructions even when no overflow occured in the execution.
[EW15603]
The file CMXTinyArmPlugin.ewplugin contained an incorrect path.
[EW15702]
Under certain circumstances, IAR Embedded Workbench could crash when starting C-SPY and the CmxArmPlugin or the CMXTinyArmPlugin was used.
[EW15703]
Annoying 'data coverage not supported' log message removed.
[EW15704]
If the flash loader operation failed and gave an error dialog box the progress bar could be left open.
[EW16050]
If, during a simulation, execution reached unallocated memory, a new memory block would be allocated and filled with zeros. Then the execution would continue in this block, since 0x0 is a valid instruction in both ARM and Thumb mode. The execution would continue, potentially until the memory runs out on the host machine. This has been fixed. Now the simulation stops and an error message is displayed whenever the program reaches memory that has not been allocated. The simulator allocates memory in 16 Kbyte blocks. If the error message "Tried to execute instruction in unallocated memory space, address 0xXXXXX000" is displayed, the execution did go wrong in the 16 Kbyte block before 0xXXXXX000. Then it continued until it reached the 16 Kbyte border, at 0xXXXXX000, where it stopped.
[EW16085]

New features

By using different memory zones, you can control the access width used for reading and writing in, for example, the Memory window. For normal memory, the default zone Memory can be used, but certain I/O registers may require to be accessed as 8, 16, or 32 bits to give correct results.

The debugger displays I/O register bit names for most supported devices.

V4.11A 2004-06-10

At certain conditions when debugging for big endian processors, C-SPY could crash or stop responding.
[EW15126]
Incorrect simulation of the SMULL instruction.
[EW15191]
Wrong simulation of the instructions
SMLAW (SMLAWB, SMLAWT) SMLA (SMLABB, SMLABT, SMLATB, SMLATT) SMLAL (SMLALBB, SMLALBT, SMLALTB, SMLALTT) SMULW (SMULWB, SMULWT) [EW15463]
A debug information construct was wrongly handled by the debugger and caused it to crash.
[EW15712]
The simulator always started at address zero regardless of the start address specified by the program start label. The simulator now starts at the program start label if it exists, if not it will start at address zero.

V4.10B 2004-03-09

None.

V4.10A 2004-02-21

Packed structs (#pragma pack) are not correctly displayed in C-SPY.
[EW14151]
Executing a "Memory Fill" command for very large chunks of memory could take a long time and occasionally lead to debugger crashes.
[EW14252]
The simulator responded with an illegal instruction error when executing coprocessor instructions. The new behavior is to silently ignore them unless it is recognized by the simulator, for example the VFP.
[EW14489]
Long pathnames to projects could trigger a bug that forced the driver to use big endian mode.
[EW14860]
Wrong simulation of QDADD and QDSUB.
[EW14884]

V3.40B-P1 2003-10-06

Error in simulation of the VFP instructions FMSC, FNMAC and FNMSC.
[EW14464]
VFP conversion of doubles to float could trash other VFP registers.
[EW14473]

V3.40A 2003-07-03

Program corrections

Pressing the End key anywhere on the last line in the Memory window will put the cursor to the end of the previous line. This also happens when selecting memory.
[EW12542, EW12645, EW12649]

A problem where .ddf files containing lines longer than 1024 characters could not be loaded has been fixed. The maximum line length is still fixed, but is now 16384 characters.
[EW13875]

New features

Support for the Vector Floating-point Architecture (VFP).

The simulator gives a warning in the log window if it detects an unaligned access. This is because ARM processors do not support unaligned accesses to memory.

V3.30A 2003-02-18

Fixed problem: When executing in pipeline simulation mode the fatal error "Unknown exception 9 in driver" occurred.
[EW13064, EW13065]

V3.21A 2002-09-30

The R0-R14, SPSR registers were not properly synchronized with the R0, R14, SPSR_<mode> registers when modifying one of these registers.

The MSR instruction was incorrectly simulated.

The LDM instruction restoring the PC and the CPSR masked bit 1 of the PC when switching to Thumb mode.

When enabling pipeline mode, breakpoints are triggered when OP-fetch is done which can cause the debugger to stop at an instruction that will not reach the execution stage later on. You must have this in mind when setting breakpoints when running in pipeline mode. In this release, the library function exit() has been modified, and will not interfere with the application anymore.

V3.20A 2002-06-19

ARM instruction set version 5TE is now supported.
Additional disassembly comments to instructions with the [#xx,PC] operand is now supported.
The registers SPSR, R8_usr to R14_usr are now accessible through the Register window.
C-SPY could could give an error message about an illegal instruction for valid code.

Reading SPSR does not take the current processor mode into account, causing the wrong value to be read.

When expanding a structure with bitfields, C-SPY crashed.

Terminal I/O input did only accept ASCII characters (0-127), now characters 0-255 are supported.

V3.11A 2001-12-03

The Call Stack window could sometimes fail to show parameter values.

Code coverage in Thumb mode did not work.
Interrupt simulation did not work properly.

V3.10A 2001-10-02

Data breakpoints on character variables located on even addresses could fail.

The C-SPY SFR window flagged some values as lost and no change of SFR value was possible.

Entering pointers to structure members or array elements in the location field of the edit breakpoint dialog caused a fatal C-SPY error.

The C-SPY simulator could mix up ASR and LSR in some cases. For example:

ldr r4, [r1, r2, LSR #24]

The C-SPY simulator did not handle the UMLAL instruction correctly.

The simulator did not handle the simulation of LDMIA SP!,{...,PC}^ correctly when returning from IRQ to SVC mode. Instead of incrementing SP_irq, SP_svc was modified.

The first message printed in a program using printf() could be lost in the terminal I/O window.

Doing a reset after program termination failed.

Enable pipeline mode. Select Low level - Memory Access Configuration from the menu bar. In the dialog box, click Add. If the OK or Cancel button was clicked, C-SPY crashed.

Single-step in assembler mode when debugging C code crashed C-SPY if the Trace option on the Control menu was enabled.

V2.10D 2001-06-29

The simulator does not consider the mode used when doing this instruction: MRS R3,SPSR. It always read from SPSR_SVR. This is now corrected.

V2.10A 2001-02-21

Support for big-endian mode is implemented in this release. Big-endian mode is selected with the command line option -e. The default mode is little-endian.
Support for ARM9TDMI simulation is implemented. This affects the pipeline simulation and the cycle counter. The ARM9 simulation mode is selected with the command line option -v1. The default mode is ARM7 ( -v0 ).

V1.30A 2000-09-08

Device definition file handling has been implemented in this release. Select the appropriate ddf file in the C-SPY options dialog box in the Embedded Workbench. It will then be possible to open the sfr window and access the sfrs defined for the current chip. The currently available ddf files are installed in the config directory. Corresponding include files (io*.h) are installed in the inc directory.

V1.20A 2000-05-28

The name of this component has been changed from CWARM to CSARM.
Selection of disassembly mode is implemented in this release. Select one of the entries in the Low Level menu.

The cycle-accurate simulation mode is implemented. To enter this mode from start, select "Enable pipeline simulation" on the Simulator tab on the C-SPY options page to start the simulation in cycle accurate mode.
Clock Speed Register is implemented. Fill in the clock speed in Hz. C-SPY will calculate the execution time in microseconds, and display it in the Register window.

V1.10A 1999-12-30

First release.