Chapter 20 Debug (S12XDBGV2)
MC9S12XDP512 Data Sheet, Rev. 2.11
816 Freescale Semiconductor
20.4.2.3.2 Outside Range (Address < CompAC_Addr or Address > CompBD_Addr)
In the outside range comparator mode, either comparator pair A and B or comparator pair C and D can be
configured for range comparisons. A single match condition on either of the comparators is recognized as
valid. An aligned word access which straddles the range boundary will cause a trigger only if the aligned
address is outside the range.
Outside range mode in combination with tagged triggers can be used to detect if the opcode fetches are
from an unexpected range. In forced trigger modes the outside range trigger would typically be activated
at any interrupt vector fetch or register access. This can be avoided by setting the upper range limit to
0x7FFFFF or lower range limit to 0x000000 respectively.
When comparing the XGATE address bus in outside range mode, the initial vector fetch as determined by
the vector contained in the XGATE XGVBR register should be taken into consideration. The XGVBR
register and hence vector address can be modified.
20.4.3 Trigger Modes
Trigger modes are used as qualifiers for a state sequencer change of state. The control logic determines the
trigger mode and provides a trigger to the state sequencer. The individual trigger modes are described in
the following sections.

20.4.3.1 Trigger On Comparator Match

If a comparator match occurs, a trigger occurs to initiate a transition to another state sequencer state and
the corresponding flags in DBGSR are set. For a comparator match to trigger firstly the comparator must
be enabled by setting the COMPE bit in the corresponding comparator control register. Secondly the state
control register for the current state must enable the match for that state. The state control registers allow
for different matches to be enabled in each of the states 1 to 3.

20.4.3.2 Trigger On Comparator Related Taghit

If either a CPU or XGATE taghit occurs a transition to another state sequencer state is initiated and the
corresponding DBGSR flags are set. For a comparator related taghit to occur, the DBG must first generate
tags based on comparator matches. When the tagged instruction reaches the execution stage of the
instruction queue a taghit is generated by the CPU/XGATE.

20.4.3.3 External Tag Trigger

In external tagging trigger mode, the TAGLO and TAGHI pins (mapped to device pins) are used to tag an
instruction. This function can be used as another breakpoint source. When the tagged opcode reaches the
execution stage of the instruction queue a transition to the disarmed state0 occurs, ending the debug session
and generating a breakpoint, if breakpoints are enabled. External tagging is only possible in device
emulation modes.