![](http://datasheet.mmic.net.cn/230000/79RC32438-200BB_datasheet_15568909/79RC32438-200BB_438.png)
IDT Debugging and Performance Monitoring
IPBus Monitor
79RC32438 User Reference Manual
18 - 2
November 4, 2002
Notes
IPBus Monitor
The IPBus monitor provides on-chip “l(fā)ogic analyzer” functionality for debugging hardware and software.
It provides sophisticated support for debugging transactions on the internal IPBus that would otherwise not
be available to the user. Unlike most other blocks in the RC32438, the IPBus Monitor is
not reset
during a
warm reset. This allows the IPBus monitor to be used to debug across a warm reset.
The IPBus monitor allows IPBus transaction information to be recorded in on-chip memory for later anal-
ysis (for additional information, refer to Chapter 17, On-Chip Memory). The on-chip memory region used by
the IPBus monitor is determined by the IPBMBASE field of the IPBMRC register. As shown in Figure 18.1,
the IPBus monitor uses memory starting at IPBMBASE to the end of on-chip memory to record transac-
tions. Memory below IPBMBASE is available for other uses.
Figure 18.1 IPBus Monitor On-Chip Memory Usage
Transaction information is stored using two types of double word (i.e., 64-bit) records. A clock cycle
record is stored in on-chip memory during each clock cycle of a transaction. A transaction summary record
is stored in on-chip memory at the end of each transaction (refer to the IPBus Monitor Trigger Time section
later in this chapter). Records are stored in on-chip memory in a circular fashion. When the end of on-chip
memory is reached, recording continues starting at IPBMBASE.
When the IPBus monitor is enabled (i.e., the EN bit is set in the IPBMTCFG register), it begins recording
each IPBus transaction in on-chip memory. Recording stops shortly after a final trigger event occurs. Once
a final trigger event occurs the IPBus monitor continues storing transactions records in on-chip memory
until the space allocated by the Final Trigger Record Length (FTRL) field in the IPBMRC register is
exhausted. The FTRL field provides control over how many transactions are recorded before and after a
final trigger event. When a final trigger event occurs the FT bit is set in the IPBMTCFG register. This bit is
presented to the interrupt controller as an interrupt source.
When the EJTAG Debug Interrupt Enable (DIE) bit is set in the IPBMTCFG register, an EJTAG debug
interrupt request is generated to the CPU core whenever the FT bit is set in the IPBMTCFG register. This
allows synchronization between the IPBus monitor and an external EJTAG ICE. When the IPBus monitor
completes storing transaction records in on-chip memory (i.e., the space allocated by the FTRL field is
exhausted) the Recording Completed (RC) bit is set in the IPBMTCFG register. This bit is presented to the
interrupt controller as an interrupt source.
0x09_058
EM6COUNT
Event Monitor 6 Count
32-bit
0x09_05C
EM7COUNT
Event Monitor 7 Count
32-bit
0x09_0060 through 0x09_7FFF
Reserved
Register Offset
Register Name
Register Function
Size
Table 18.1 Debug and Performance Register Map (Part 2 of 2)
0x0000
0x0FFF
I
IPBMBASE