Table 6. e200zx cores debug feature options (continued)
Device
Revision
Instantiation
Core Name
Nexus class support
Timestamp
Nexus Port Width (MDO)
JTAG Nexus State
Machine Reset
DQM DQTAG packet type
e200z720 based cores
MPC5777M
1.0
Core 0/1
e200z720n3
3+
No
30
Fixed
Fixed
e200z7260 based cores
MPC5775K
1.0/1.1/
2.0
Core 1/2
e200z7260n3
3+
Yes
(buffered)
30 or 16
3
Fixed
Fixed
e200z759 based cores
Future device 2
1.0
Core 0/1
e200z759n3
3+
No
16 or 12
Fixed
Variable
1. Although a 4-bit parallel Nexus MDO port is implemented in the core, it is not possible to select this mode in the Nexus
Aurora Router (NAR).
2. Unbuffered timestamps had been planned for these cores.
3. Although a 16-bit parallel Nexus MDO port can be selected, pins are not available on the package to allow it to be
accessed.
Nexus Class support - The IEEE-ISTO 5001 standard supports multiple "Classes" of support. The e200zx cores can be
instantiated with different levels of support. An overview of the Nexus Class definitions can be found in AN4088
"MPC5500/MPC5600 Nexus Support Overview".
Nexus Timestamp Support - The IEEE-ISTO 5001 standard allows Nexus messages to have timestamps appended to the
message to better track the exact timing of the messages. Timestamps are an optional feature. When implemented on the
e200zx cores, the timestamps can either be implemented as buffered or non-buffered. In general, the unbuffered mode is
implemented on devices with a Nexus Aurora Router (NAR) as the Nexus output controller. Devices that instantiate the
Nexus Port Controller (NPC) use the buffered timestamps. This difference is due to the minimal time that messages spend in
the core Nexus buffers on NAR devices since the NAR implements dedicated input queues from each Nexus client on the
device. However, the NPC only acts as a switch from the output of the individual Nexus clients directly to the Nexus output
port. The NPC implements no buffers for holding messages. On NPC based devices, each client implements the buffers that
hold Nexus messages while other Nexus clients are transmitting their message out of the device.
Table 7. Nexus Timestamp support
Timestamp type
Description
Buffered
The buffered option appends the timestamp to the Nexus message when the message is
written into the e200z
x
core Nexus message buffers.
Unbuffered
The unbuffered option appends the timestamp to the Nexus message when the message
leaves the core buffers and is transferred to the device level NPC or NAR.
Nexus Port Width - The width of the Nexus Auxiliary port (trace information) is definable for the e200zx core definition.
Typically, a 30-bit Message Data Output port is used when supporting the IEEE-ISTO 5001-2012 high-speed serial Nexus
Aurora port. Smaller sizes are generally used for a parallel Message Data Output Nexus port. Some core variations support
two port widths, while some variations support only a single port width. This is primarily to support either the Nexus Port
Differences between MPC57xx e200zx cores
Qorivva MPC57xx e200zx Core Differences, Rev 0, 10/2013
Freescale Semiconductor, Inc.
9
