Freescale Semiconductor MCF5329 Reference Manual page 857

be displayed (debug data, DDATA). The processor status may not be related to the current bus transfer, due
to the decoupling FIFOs.
External development systems can use PST outputs with an external image of the program to completely
track the dynamic execution path. This tracking is complicated by any change in flow, where branch target
address calculation is based on the contents of a program-visible register (variant addressing). DDATA
outputs can display the target address of such instructions in sequential nibble increments across multiple
processor clock cycles, as described in
Two 32-bit storage elements form a FIFO buffer connecting the processor's high-speed local bus to the
external development system through PST[3:0] and DDATA[3:0]. The buffer captures branch target
addresses and certain data values for eventual display on the DDATA port, one nibble at a time starting
with the least significant bit (lsb).
Execution speed is affected only when both storage elements contain valid data to be dumped to the
DDATA port. The core stalls until one FIFO entry is available.
Table 36-24 shows the encoding of these signals.
PST[3:0]
0x0 Continue execution. Many instructions execute in one processor cycle. If an instruction requires more clock
cycles, subsequent clock cycles are indicated by driving PST outputs with this encoding.
0x1 Begin execution of one instruction. For most instructions, this encoding signals the first processor clock cycle
of an instruction's execution. Certain change-of-flow opcodes, plus the PULSE and WDDATA instructions,
generate different encodings.
0x2 Used by the debug translate module to indicate two consecutive PST = 1 values.
0x3 Entry into user-mode. Signaled after execution of the instruction that caused the ColdFire processor to enter
user mode.
0x4 Begin execution of PULSE and WDDATA instructions. PULSE defines logic analyzer triggers for debug
and/or performance analysis. WDDATA lets the core write any operand (byte, word, or longword) directly to
the DDATA port, independent of debug module configuration. When WDDATA is executed, a value of 0x4 is
signaled on the PST port, followed by the appropriate marker, and then the data transfer on the DDATA port.
Transfer length depends on the WDDATA operand size.
0x5 Begin execution of taken branch or SYNC_PC command issued. For some opcodes, a branch target
address may be displayed on DDATA depending on the CSR settings. CSR also controls the number of
address bytes displayed, indicated by the PST marker value preceding the DDATA nibble that begins the
data output. See
SYNC_PC command has been issued.
0x6 Used by the debug translate module to indicate a PST = 5 value followed by a PST = 1 value.
0x7 Begin execution of return from exception (RTE) instruction.
0x8– Indicates the number of bytes to be displayed on the DDATA port on subsequent clock cycles. The value is
0xB driven onto the PST port one PSTCLK cycle before the data is displayed on DDATA.
0x8 Begin 1-byte transfer on DDATA.
0x9 Begin 2-byte transfer on DDATA.
0xA Begin 3-byte transfer on DDATA.
0xB Begin 4-byte transfer on DDATA.
Freescale Semiconductor
Section 36.4.4.1, "Begin Execution of Taken Branch (PST =
Table 36-24. Processor Status Encoding
Section 36.4.4.1, "Begin Execution of Taken Branch (PST =
MCF5329 Reference Manual, Rev 3
Definition
0x5)". Also indicates that the
Debug Module
0x5)".
36-41