e200z4 CoreMPC5644A Microcontroller Reference Manual, Rev. 6136 Freescale Semiconductor• Per-entry multiple page size support from 1 Kbyte to 4 Gbyte• Entry Flush Protection• Process ID manipulation for the MMU using an external tool7.3.6 e200z4 system bus featuresThe features of the e200z4 System Bus interface are as follows:• Independent Instruction and Data buses• 32-bit address bus, 64-bit data bus, plus attributes and control• Data interface provides separate unidirectional 64-bit read and write data buses7.3.7 Nexus 3 featuresThe Nexus 3 module is compliant with Class 3 of the IEEE-ISTO 5001™ - 2003 standard, with certainadditional Class 4 features available. The following features are implemented:• Program Trace via Branch Trace Messaging (BTM). Branch trace messaging displays programflow discontinuities (direct and indirect branches, exceptions, etc.), allowing the development toolto interpolate what transpires between the discontinuities. Thus, static code may be traced.• Data Trace via Data Write Messaging (DWM) and Data Read Messaging (DRM). This providesthe capability for the development tool to trace reads and/or writes to selected internal memoryresources.• Ownership Trace via Ownership Trace Messaging (OTM). OTM facilitates ownership trace byproviding visibility of which process ID or operating system task is activated. An Ownership TraceMessage is transmitted when a new process/task is activated, allowing the development tool totrace ownership flow.• Run-time access to the processor memory map via the JTAG port. This allows for enhanceddownload/upload capabilities.• Watchpoint Messaging via the auxiliary interface.• Watchpoint Trigger enable of Program and/or Data Trace Messaging.• Data Acquisition Messaging (DQM) allows code to be instrumented to export customizedinformation to the Nexus Auxiliary Output Port.• Auxiliary interface for higher data input/output.• Registers for Program Trace, Data Trace, Ownership Trace, Data Acquisition, and WatchpointTrigger control.• All features controllable and configurable via the JTAG port.
