Xilinx MicroBlaze Reference Manual page 115

Table 2-61: Profiling Data Write Register (PDWR)
Bits Name
31:0 Write Data
Cross Trigger Support
With basic debugging, cross trigger support is provided by two signals,
.
MB_Halted
• When the
DBG_STOP
will detect that MicroBlaze has halted, and indicate where the halt occurred. The signal
can be used to halt MicroBlaze at any external event, for example when a Vivado®
Integrated Logic Analyzer (ILA) is triggered.
• Whenever MicroBlaze is halted, the
after a breakpoint or watchpoint is hit, after a stop XSDB command, or when the
input is set. The output is cleared when MicroBlaze execution is resumed by
DBG_STOP
an XSDB command.
The
MB_Halted
other MicroBlaze cores in a multiprocessor system by connecting the signal to their
inputs.
DBG_STOP
With extended debugging, cross trigger support is available in conjunction with the MDM.
The MDM provides programmable cross triggering between all connected processors, as
well as external trigger inputs and outputs. For details, see the MicroBlaze Debug Module
(MDM) Product Guide (PG115)
MicroBlaze can handle up to eight cross trigger actions. Cross trigger actions are generated
by the corresponding MDM cross trigger outputs, connected using the Debug bus. The
effect of each of the cross trigger actions is listed in
MicroBlaze can generate up to eight cross trigger events. Cross trigger events affect the
corresponding MDM cross trigger inputs, connected using the Debug bus. The cross trigger
events are described in
MicroBlaze Processor Reference Guide
UG984 (v2018.2) June 21, 2018
Data to write to a bin.
input is set to 1, MicroBlaze will halt after a few instructions. XSDB
MB_Halted
signal can be used to trigger a Vivado integrated logic analyzer, or halt
[Ref 4].
Table 2-63.
www.xilinx.com
Chapter 2: MicroBlaze Architecture
Description
output signal is set to 1; for example
Table 2-62.
Reset Value
0
and
DBG_STOP
115
Send Feedback