Nexus Development Interface (NDI)
MPC5510 Microcontroller Family Reference Manual, Rev. 1
20-4
Freescale Semiconductor
Preliminary
•
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.
•
Watchpoint messaging via the auxiliary pins.
•
Watchpoint trigger enable of program trace messaging.
•
Auxiliary interface for higher data input/output.
— Configurable (min./max) message data out pins (four MDO in reduced-port mode or eight
MDO in full-port mode.
— One message start/end out pins (MSEO).
— One watchpoint event pin (EVTO).
— One event-in pin (EVTI).
— One message clock out pin (MCKO).
— Five pin JTAG port (JCOMP, TDI, TDO, TMS, and TCK).
•
Registers for program trace, ownership trace, and watchpoint trigger.
•
All features controllable and configurable via the JTAG port.
•
Run-time access to the on-chip memory map via the Nexus read/write access protocol. This allows
for enhanced download/upload capabilities.
•
All features are independently configurable and controllable via the IEEE 1149.1 I/O port.
•
The NDI block reset is controlled with JCOMP, power-on reset, and the TAP state machine. All
theses sources are independent of system reset.
•
Power-on-reset status indication via MDO[0].
•
Support for internal censorship mode to prevent external access to flash memory contents when
censorship is enabled.
NOTE
If the e200z1 and e200z0 cores have executed a wait instruction, then the
controller clocks are gated off. While both cores are in this state,
it will not be possible to perform Nexus read/write operations.
20.2.2
Modes of Operation
The NDI block is in reset when the TAP controller state machine is in the TEST-LOGIC-RESET state. The
TEST-LOGIC-RESET state is entered on the assertion of the power-on reset signal, negation of JCOMP,
or through state machine transitions controlled by TMS. Assertion of JCOMP allows the NDI to move out
of the reset state, and is a prerequisite to grant Nexus clients control of the TAP. Ownership of the TAP is
achieved by loading the appropriate enable instruction for the desired Nexus client in the JTAGC controller
(JTAGC) block when JCOMP is asserted.
The NPC transitions out of the reset state immediately following negation of power-on reset.