User guide

CSPC7501R-2:1

Using the emulator

TR A C E

The Trace window—available from the Emulator menu—displays a recorded sequence

of executed machine instructions. In addition, the window can display trace data for

expressions. For more information, see the IAR Embedded Workbench® IDE User

Guide.

Using breakpoints

This section describes issues related to using breakpoints in the C-SPY hardware

debugger systems.

BREAKPOINT USAGE DIALOG BOX

The Breakpoint Usage dialog box—available from the Emulator menu—lists all

active breakpoints. For more information, see the IAR Embedded Workbench® IDE

User Guide.

C-SPY USE OF BREAKPOINTS

If you set a breakpoint using the IAR CLIB runtime environment, C-SPY sets two

breakpoints for internal use. To do this, the breakpoints in the emulator are used. The

fact that C-SPY uses breakpoints is normally not a problem. However, one exception is

C-SPY profiling, which require many breakpoints. (The emulators have 64 software

breakpoints and 2–8 hardware breakpoints.)

Note: If you are using the IAR DLIB runtime environment, only one internal

breakpoint will be needed per breakpoint that you set.

C-SPY will set a breakpoint if:

● the C-SPY option Run to has been selected (one breakpoint is set temporarily after

each reset)

● the stack plugin is being used (if the C-SPY option Run to has been selected, the

breakpoint needed for that will be used also by the stack plugin)

● the linker option With runtime control modules has been selected (debug support

for program termination and optionally file I/O).

Exceeding the number of available software breakpoints will cause the debugger to

single step. This will significantly reduce the execution speed.

You can prevent the debugger from using breakpoints in these situations by deselecting

these options.