English
Language : 

PXN20RM Datasheet, PDF (1176/1376 Pages) Freescale Semiconductor, Inc – PXN20 Microcontroller
Nexus Development Interface (NDI)
Table 36-13. Terms and Definitions (continued)
Term
JTAG Compliant
JTAG IR & DR Sequence
Nexus1
Ownership Trace
Message (OTM)
Public Messages
Standard
Transfer Code (TCODE)
Watchpoint
Description
Device complying to IEEE 1149.1 JTAG standard
JTAG instruction register (IR) scan to load an opcode value for selecting a development
register. The JTAG IR corresponds to the OnCE command register (OCMD). The selected
development register is then accessed via a JTAG data register (DR) scan.
The e200z6 (OnCE) debug module. This module integrated with each e200z6 processor
provides all static (core halted) debug functionality. This module is compliant with Class1 of the
IEEE-ISTO 5001 standard.
Visibility of process/function that is currently executing.
Messages on the auxiliary pins for accomplishing common visibility and controllability
requirements
The phrase ‘according to the standard’ is used to indicate according to the IEEE-ISTO 5001
standard.
Message header that identifies the number and/or size of packets to be transferred, and how
to interpret each of the packets.
A data or instruction breakpoint that does not cause the processor to halt. Instead, a pin is used
to signal that the condition occurred. A watchpoint message is also generated.
36.6.4 Nexus3+ Features
The Nexus3+ module is compliant with Class 3 of the IEEE-ISTO 5001-2003 standard. The following
features are implemented:
• Program trace via branch trace messaging (BTM). Branch trace messaging displays program flow
discontinuities (direct and indirect branches, exceptions, etc.), allowing the development tool to
interpolate what transpires between the discontinuities. Thus static code may be traced.
• Data trace via data write messaging (DWM) and data read messaging (DRM). This provides the
capability for the development tool to trace reads and/or writes to selected internal memory
resources.
• Ownership trace via ownership trace messaging (OTM). OTM facilitates ownership trace by
providing visibility of which process ID or operating system task is activated. An ownership trace
message is transmitted when a new process/task is activated, allowing the development tool to
trace ownership flow.
• Run-time access to embedded processor registers and memory map via the JTAG port. This allows
for enhanced download/upload capabilities.
• Watchpoint messaging via the auxiliary pins.
• Watchpoint trigger enable of Program and/or Data Trace Messaging.
• Higher speed data input/output via the auxiliary port.
• Registers for Program Trace, Data Trace, Ownership Trace and Watchpoint Trigger.
• All features controllable and configurable via the JTAG port.
36-26
PXN20 Microcontroller Reference Manual, Rev. 1
Freescale Semiconductor