User`s manual

206
8.3.7 Signals to Indicate Bus States and Areas
The following tables show examples of signals to indicate the bus states and areas that can be acquired by the
emulator.
Table 8.21 Bus State Signals Acquired by the Emulator
Bus State Trace Display (Status) Description
CPU Prefetch CPU_PREFETCH CPU prefetch cycles (high-speed mode)
CPU Data CPU CPU data access cycles (high-speed mode)
CPU Medium
Prefetch
CPU_MEDIUM_PREFETCH CPU prefetch cycles (medium-speed mode)
CPU Medium data CPU_MEDIUM_DATA CPU data access cycles (medium-speed mode)
Sub Active Prefetch SUB_ACTIVE_PREFETCH Prefetch cycles in subactive mode
Sub Active Data SUB_ACTIVE_DATA Data access cycles in subactive mode
Table 8.22 Area Signals Acquired by the Emulator
Area Trace Display (Area) Description
On-chip ROM IN-ROM Internal ROM
On-chip RAM IN-RAM Internal RAM
On-chip I/O I/O I/O
LCD RAM LCD-RAM LCD RAM area
Note: The signals to indicate bus states and areas are used to set the [Bus/Area] condition of the event point.
They can also be acquired as the trace information. The bus state signals are also used to set the
condition not to acquire the trace ([Suppress] option).
8.3.8 Monitoring Function
The emulator of HS38000EPI61H + HS388REBK61H incorporates the bus monitoring circuit as the standard,
which thus allows a use of the monitoring function to update the content of memory without affecting the
realtime operation.
HS3880EPI60H and HS388REPI60H do not incorporate the bus monitoring circuit. To use the monitoring
function, the bus monitor board (HS6000EBR01H) is required.
8.3.9 Trigger Points
The emulator of HS38000EPI61H + HS388REBK61H incorporates the bus monitoring circuit as the standard,
which thus allows a use of trigger points that can be set on the [Trigger] sheet in the [Event] window.
HS3880EPI60H and HS388REPI60H do not incorporate the bus monitoring circuit. Connecting the bus monitor
board (HS6000EBR01H) allows use of trigger points that can be set on the [Trigger] sheet in the [Event]
window.