PXR40RM Datasheet, PDF (1322/1434 Pages) Freescale Semiconductor, Inc – PXR40 Microcontroller

Nexus Development Interface (NDI)
Signal Name
EVTO
EVTI
MCKO
MDO[11:0] or
MDO[15:0]
MSEO[1:0]
RDY
JCOMP
TCK
TDI
TDO
TMS
Table 31-1. Signal Properties
Port
Auxiliary
Auxiliary
Auxiliary
Auxiliary
Function
Event out pin
Event in pin
Message clock out pin (from NPC)
Message data out pins
Auxiliary
Auxiliary
JTAG
JTAG
JTAG
JTAG
JTAG
Message start/end out pins
Ready out pin
JTAG compliancy and TAP sharing control
Test clock input
Test data input
Test data output
Test mode select input
Reset State
Negated
Pullup
Enabled
Driven Low
Negated
Negated
Pulldown
Pulldown
Pullup
High Z / Pullup
Pullup
31.2.1 Detailed Signal Descriptions
This section describes each of the signals listed in Table 31-1 in more detail.
31.2.1.1 Event Out (EVTO)
EVTO is an output pin that is asserted upon breakpoint occurrence to provide breakpoint status indication
or to signify that an event has occurred. The EVTO output of the NPC is generated based on the values of
the individual EVTO signals from all Nexus modules that implement the signal.
31.2.1.2 Event In (EVTI)
EVTI is used to initiate program and data trace synchronization messages or to generate a breakpoint.
EVTI is edge-sensitive for synchronization and breakpoint generation.
31.2.1.3 Message Data Out (MDO[11:0] or [15:0])
Message data out (MDO) are output pins used for uploading OTM, BTM, DTM, and other messages to
the development tool. The development tool must sample MDO on the rising edge of MCKO. The width
of the MDO bus used is determined by the Nexus PCR[FPM] configuration.
31.2.1.4 Message Start/End Out (MSEO[1:0])
MSEO[1:0] are output pins that indicates when a message on the MDO pins has started, when a variable
length packet has ended, or when the message has ended. The development tool must sample the MSEO
pins on the rising edge of MCKO.
31-6
PXR40 Microcontroller Reference Manual, Rev. 1
Freescale Semiconductor