Table of Contents
Advertisement
1.3.2 Event Detection Functions
The emulator has complex event detection functions in addition to the standard PC breakpoints of
the High-performance Embedded Workshop.
(1) Events
In most practical debugging applications, the program or hardware errors that you are trying to
debug occur under a certain restricted set of circumstances. For example, a hardware error may
only occur after a specific area of memory has been accessed. Tracking down such problems using
simple PC breakpoints can be very time-consuming.
With the emulator, the combination of the specified conditions such as address, data, or access
condition can be defined as the eventpoint. When an eventpoint condition is satisfied, an event
will occur. The event detection function of the emulator can be used to detect a generated event
and control the operations of break, trace, and performance measurement start/end.
(2) Types of Events
The emulator has four types of events.
(a) On-chip event function (Onchip Event)
This is a function that uses an on-chip break controller and sets eventpoints according to the
information in the MPU. There are 13 event detection channels. The eventpoints can be defined as
a combination of one or more of the following:
• Address condition
• Data condition
• ASID condition
• Bus state condition
• Address condition for the destination of memory access
• System bus condition
• LDTLB instruction execution
• Branch condition
• Software trace condition*
• Event count condition
Note: The PC value when executing the Trace() function and the contents of the specified
general register are acquired by trace; this function is hereafter called as the software trace
function.
24
Advertisement
Table of Contents
