Technical information

4 / 7
1.10 Emulation
1.10.1 Temporary Breakpoints
• Run... (Run menu)
Do not set temporary breakpoints to an area wherein Software Break (User Read-only) cannot be set.
Otherwise, user program execution will not stop at the breakpoint. Moreover, the On Chip Breakpoint
may remain. In this case, delete the breakpoint from the [Breakpoints] window.
1.10.2 Rate of Stepping
• To perform stepping continuously with the [Image View] or [Waveform] window open, do not
select “0 seconds” as the delay.
• Do not perform stepping continuously if you have specified the realtime update of the [Image] or
[Waveform] window.
1.10.3 Go to Cursor
The [Go to Cursor] function uses one Software breakpoint. Note the followings:
• To use the [Go to Cursor] function, the number of Software breakpoints must be 255 or less.
• To use the [Go to Cursor] function for the ROM area on the target system, do not use the On Chip
Breakpoint by the Software break.
1.10.4 Note on Occurrence of Breaks
When a break occurs during execution of the user program with a dialog box open, the state of
High-performance Embedded Workshop may not transit to the breaking state. In this case, close the
dialog box and select [Halt Program] from the [Debug] menu or press the [Halt Program] button on the
toolbar. You can check whether a break has occurred or not by the RUN lamp (LED) on the emulator
station. The RUN lamp (LED) is illuminated while the user program is running.
1.10.5 Execution Status Display
• Execution Status Display on Status Bar
At memory access wait, not the address where the access is halted, but the next fetched address is
displayed.
1.10.6 Source-Level Execution
• Step
Even standard C libraries are executed. To return to a higher-level function, enter Step Out. In a for
statement or a while statement, executing a single step does not move execution to the next line. To move
to the next line, execute two steps.
1.11 The Load/Save of the Session File
Load the file after you confirm that the H/W environment is the same as that when the last session file was
loaded.
Note that the operation of High-performance Embedded Workshop may become incorrect when Target
Clock is chosen at the time when the session file was saved and Target was not connected at the time
when the session file was loaded.