Advertisement
Section 5 Debugging
5.5
Using the Event Points
The emulator has the event point function that performs breaking, tracing, and execution time
measurement by specifying more complex conditions along with the PC breakpoints standard for
the High-performance Embedded Workshop.
5.5.1
PC Breakpoints
When the instruction of the specified address is fetched, the user program is stopped. Up to 255
points can be set.
These settings will not be common to the High-performance Embedded Workshops for CPU0 and
CPU1. That is, each High-performance Embedded Workshop has its own settings.
5.5.2
Event Conditions
Event conditions can be used for more complex conditions such as the data condition as well as
specification of the single address.
When the condition is satisfied, break conditions are also used as the start/end conditions for
performance measurement in addition to halting the user program. When event conditions are
used as the start/end conditions for performance measurement, start from setting in the
[Performance Analysis] window.
Several event conditions can be combined in a more complex condition. These settings are
common to the High-performance Embedded Workshops for CPU0 and CPU1.
Notes: 1. When break conditions are used as the start/end conditions for performance
measurement, step operation cannot be performed. In addition, when execution is
restarted from the address where step operation has been stopped by the
BREAKPOINT, the single step function is used and operation is disabled. Restart
execution after the BREAKPOINT has been canceled.
2. It is not possible to use the break conditions and the start/end conditions for
performance measurement at the same time with one channel. If the performance
measurement start/end conditions are set, the settings of the break conditions will be
disabled.
3. The break conditions that can be set vary according to the emulator in use. For details,
refer to the online help.
Rev. 1.00 Nov. 26, 2007 Page 100 of 230
REJ10J1766-0100
Advertisement
Troubleshooting
