The corrections below refer to the PDF versions of the user guide IAR Embedded Workbench IDE User Guide, UEW-5. The information in the PDF files is, in the event of any differences, more accurate than the printed user guides and the online help files.
Part 2, Tutorials, Simulating an interrupt, page 49-58.
Some of the names of registers, files and interrupts have changed:
Part 5, IAR C-SPY Simulator
The following information should be added to the description of the C-SPY Simulator
settings in the Project Options dialog box.
Enable register breakpoints
You can set a data breakpoint to stop execution on read/write accesses in the SFR
area. The simulator always checks for breakpoints during execution for module M0
- M6. Breakpoints in module M7 and up can also be checked for during execution if
you use this option.
Although checking for breakpoints is primarily intended to check for accesses to SFRs, it can also be used for breaking on an access to other registers. For example, to break on write accesses to DP[0], define a data breakpoint and in the Break At box, enter #DP0. For the simulator to handle this breakpoint, you must select Enable register breakpoints in the Project Options dialog box.
The breakpoint is only checked for on the initial address expression in the instruction. For example, if a breakpoint has been set on write access to A[0], and an instruction writes to Acc with AP having the value 0, the breakpoint will not be triggered. However, an instruction writing directly to A[0] would trigger the breakpoint.
When you specify a register in such a breakpoint, it is natural to use the register name, for example #A[0]. (When you use the name of a CPU register in an expression, it should be preceded with #.) Unfortunately, such register names will cause confusion when parsed, as the names will look very much like a C expression. For this reason, every register with a name containing brackets has been given an alias without the brackets. For example, #A0 will specify register A[0], and #LC0 will specify register LC[0].
ROM file
To execute correctly, the application will need the services of the Utility ROM.
In your target hardware, the Utility ROM is always present. However, when you use
the simulator, the contents of the Utility ROM must be loaded. You can specify an
Intel hex file containing the program code for the Utility ROM that corresponds
to your derivative for use with the simulator. The default Utility ROM used will
depend on the selected processor variant.
EWMAXQ-142: The segment definition for CCHECKSUM was missing in some of the linker configuration files.
Added support for the MAXQ1740 and the MAXQ615.
A new debugger driver for the 1-Wire interface found on certain MAXQ parts has been added.
The default memory model for all project templates has been changed to small.
EW20715: The default size of the stack was increased.
EW20714: The default "extra output format" from the linker was changed.
Several issues in the compiler was resolved. Refer to the compiler readme file for more detailed information.
Find in files
The find in files search mechanism has been improved. Various search scopes can
be specified like project files, directories and file groups.
Drag-and-drop to project manager
Files can be added to the project manager, and project files can be added to the
workspace by drag-and-drop.
Pre and post build
Pre and post build commands can be configured.
File viewers
Files in a project can now be opened with another application than the built-in
editor. Choose Tools>Configure Viewers and configure which application
to use with a certain filename extension.
File properties
You can now right-click on a file in the Workspace window to display the file properties.
File status
File name and line number are now displayed in the Build message log window.
Compiling a selection of source files
The Project>Compile command can now be applied to a selection of source
files.
Editor removes trailing blanks
The editor now removes trailing blanks when text files are saved. To turn off this
feature, choose Tools>Options, click the Editor tab and deselect
Remove trailing blanks.