Xilinx MicroBlaze Reference Manual page 106

Table 2-62: MicroBlaze Cross Trigger Events
Number
0 MicroBlaze halted
1 Execution resumed
2 Program trace
stopped
3 Program trace
4 Performance
monitoring stopped
5 Performance
monitoring started
6 Profiling disabled
7 Profiling enabled
Trace Interface Overview
The MicroBlaze trace interface exports a number of internal state signals for performance
monitoring and analysis. Xilinx recommends that users only use the trace interface through
Xilinx developed analysis cores. This interface is not guaranteed to be backward compatible
in future releases of MicroBlaze.
See Table 3-15
MicroBlaze Processor Reference Guide
UG984 (v2016.2) June 8, 2016
UG984 (v2016.1) April 6, 2016
Event
Generate an event when MicroBlaze is halted. The same event is signalled
when the MB_Halted output is set.
Generate an event when the processor resumes execution from debug halt.
The same event is signalled when the MB_Halted output is cleared.
Generate an event when program trace is stopped by writing a command to
the Program Trace Command Register, when the trace buffer is full, or by a
cross trigger action.
Generate an event when program trace is started by writing a command to
started the Program Trace Command Register, by hitting a tracepoint, or by a cross
trigger action.
Generate an event when performance monitoring is stopped by writing a
command to the Performance Counter Command Register or by a cross
trigger action.
Generate an event when performance monitoring is started by writing a
command to the Performance Counter Command Register, or by a cross
trigger action.
Generate an event when profiling is enabled by writing a command to the
Profiling Control Register or by a cross trigger action.
Generate an event when profiling is disabled by writing a command to the
Profiling Control Register or by a cross trigger action.
for a list of exported signals.
www.xilinx.com
Chapter 2: MicroBlaze Architecture
Description
Send Feedback
106