Controller (NPC, used on the previous MPC5500/MPC5600 devices) that supports selection between two different port
widths, and the Nexus Aurora Router (NAR, used on some of the MPC5700 devices) that supports only a single port width.
The port width, along with the port speed, define the maximum bandwidth that is available for trace information.
Table 8. Typical Nexus port width usage
Number of Message Data Outputs
Typical use
4
Low-bandwidth parallel Nexus Auxiliary trace port
8
Medium-bandwidth parallel Nexus Auxiliary trace port
1
12
Medium-bandwidth parallel Nexus Auxiliary trace port
16
High-bandwidth parallel Nexus Auxiliary trace port
30
Very high-bandwidth serial Nexus Aurora trace
1. This depends on the number of cores and the Nexus parallel port clock speed.
JTAG Nexus State Machine Reset - In some cases, the Nexus state machine in the e200zx core does not get properly reset
when the JTAG TAP is changed to a different JTAG client (to a different core or other client). Previously, the Nexus JTAG
state machine was reset only if the JTAG IR changed the CMD/DATA. It has been modified to reset the Nexus state machine
anytime the JTAG state machine goes through the UPDATE_IR state.
Data Acquisition Message (DQM) Data Tag (DQTAG) packet type - The Data Tag (DQTAG) packet of the Data
Acquisition Message (DQM) is defined by the IEEE-ISTO 5001 standard as a Fixed length field. Some versions of the cores
incorrectly implement the DQTAG as a Variable length packet instead of the Fixed length field.
Appendix A Revision history
The table below shows the complete revision history of this document.
Table A-1. Revision History
Revision
Author
Changes
0
Randy Dees
Initial customer release.
Qorivva MPC57xx e200zx Core Differences, Rev 0, 10/2013
10
Freescale Semiconductor, Inc.
