Nexus Development Interface (NDI)
MPC5606S Microcontroller Reference Manual, Rev. 7
972 Freescale Semiconductor
26.7.5 Nexus messaging
Most of the messages transmitted by the NDI include an SRC field. This field is used to identify which
source generated the message. Table 26-15 shows the values used for the SRC field by the different clients
on the MPC5606S. These values are specific to the MPC5606S. The size of the SRC field in transmitted
messages is 4 bits. This value is also specific to the MPC5606S.
26.7.6 EVTO sharing
The NPC block controls sharing of the EVTO output between all Nexus clients that generate an EVTO
signal. The sharing mechanism is a logical AND of all incoming EVTO signals from Nexus blocks,
thereby asserting EVTO whenever any block drives its EVTO. When there is no active MCKO, such as in
disabled mode, the NPC drives EVTO for two system clock periods. EVTO sharing is active as long as the
NDI is not in reset.
26.7.7 Debug mode control
On MPC5606S, program breaks can be requested either by using the EVTI pin as a break request, or when
a Nexus event is triggered.
26.7.7.1 EVTI generated break request
To use the EVTI pin as a debug request, the EIC field in the e200z0 Nexus2+ Development Control
Register 1 (DC1[4:3]) must be set to configure the EVTI input as a debug request.
26.7.8 Nexus reset control
The JCOMP input that is used as the primary reset signal for the NPC is also used by the NPC to generate
a single-bit reset signal for other Nexus blocks. The single bit reset signal functions much like the IEEE
1149.1-2001 defined
TRST signal but has a default value of disabled (JCOMP is pulled low during reset).
The IEEE 1149.1-2001 defines
TRST to be pulled up (enabled) by default.
0b110 Reserved
0b111 SYS_CLK8
Table 26-15. SRC packet encodings
SRC[3:0] MPC5606S client
0b0000 e200z0
All other combinations Reserved
Table 26-14. MCKO_DIV Values (continued)
MCKO_DIV[2:0] MCKO frequency
To Next Page
Loading...
