mc9s12xd256 Freescale Semiconductor, Inc, mc9s12xd256 Datasheet - Page 770

• Manufacturer Part Number: mc9s12xd256
• Description: Hcs12x Microcontrollers
• Manufacturer: Freescale Semiconductor, Inc

Chapter 20 S12X Debug (S12XDBGV3) Module
before the tagged instruction executes (tagged-type trigger). Whilst tagging the RW, RWE, SZE, and SZ
bits are ignored and the comparator register must be loaded with the exact opcode address.
If the TAG bit is clear (forced type trigger) a comparator match is generated when the selected address
appears on the system address bus. If the selected address is an opcode address, the match is generated
when the opcode is fetched from the memory. This precedes the instruction execution by an indefinite
number of cycles due to instruction pipe lining. For a comparator match of an opcode at an odd address
when TAG = 0, the corresponding even address must be contained in the comparator register. Thus for an
opcode at odd address (n), the comparator register must contain address (n–1).
Once a successful comparator match has occurred, the condition that caused the original match is not
verified again on subsequent matches. Thus if a particular data value is verified at a given address, this
address may not still contain that data value when a subsequent match occurs.
Comparators C and D can also be used to select an address range to trace from. This is determined by the
TRANGE bits in the DBGTCR register. The TRANGE encoding is shown in
bits select a range definition using comparator D, then comparator D is configured for trace range
definition and cannot be used for address bus comparisons. Similarly if the TRANGE bits select a range
definition using comparator C, then comparator C is configured for trace range definition and cannot be
used for address bus comparisons.
Match[0, 1, 2, 3] map directly to Comparators[A, B, C, D] respectively, except in range modes (see
Section
(Section
20.4.2.1
With range comparisons disabled, the match condition is an exact equivalence of address/data bus with the
value stored in the comparator address/data registers. Further qualification of the type of access (R/W,
word/byte) is possible.
Comparators A and C do not feature SZE or SZ control bits, thus the access size is not compared. The exact
address is compared, thus with the comparator address register loaded with address (n) a misaligned word
access of address (n–1) also accesses (n) but does not cause a match.
considerations without data bus compare.
comparison. To compare byte accesses DBGXDH must be loaded with the data byte. The low byte must
be masked out using the DBGXDLM mask register. On word accesses the data byte of the lower address
is mapped to DBGXDH.
770
20.3.2.4”). Comparator priority rules are described in the trigger priority section
Access
20.4.3.6”).
Word
Word
Word
Byte
Exact Address Comparator Match (Comparators A and C)
Address
ADDR[n]
ADDR[n]
ADDR[n]
ADDR[n]
Table 20-36. Comparator A and C Data Bus Considerations
DBGxDH
Data[n]
Data[n]
Data[n]
x
MC9S12XDP512 Data Sheet, Rev. 2.17
Data[n+1]
Data[n+1]
DBGxDL
Table 20-36
x
x
DBGxDHM
$FF
$FF
$FF
$00
lists access considerations with data bus
DBGxDLM
$FF
$FF
$00
$00
Table 20-37
MOVW #$WORD ADDR[n]
MOVW #$WORD ADDR[n]
MOVW #$WORD ADDR[n]
MOVB #$BYTE ADDR[n]
Example Valid Match
Table
20-10. If the TRANGE
lists access
Freescale Semiconductor