
Nexus
MPC5566 Microcontroller Reference Manual, Rev. 2
Freescale Semiconductor
25-3
– Two MSEO (message start/end out) pins
– One RDY (ready) pin
– One EVTO (event out) pin
— Auxiliary input port uses one EVTI (event in) pin
— Five-pin JTAG port (JCOMP, TDI, TDO, TMS, and TCK)
•
Host processor (e200z6) development support features (NZ6C3)
— IEEE-ISTO 5001-2003 standard class 3 compliant.
— Data trace via data write messaging (DWM) and data read messaging (DRM). This allows the
development tool to trace reads and/or writes to selected internal memory resources.
— 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 development tools
to trace ownership flow.
— Program trace via branch trace messaging (BTM). Branch trace messaging displays program
flow discontinuities (direct branches, indirect branches, exceptions, etc.), allowing the
development tool to interpolate what transpires between the discontinuities. Thus, static code
can be traced.
— Watchpoint messaging (WPM) via the auxiliary port.
— Watchpoint trigger enable of program and/or data trace messaging.
— Data tracing of instruction fetches via private opcodes.
— Subset of Power Architecture Book E software debug facilities with OnCE block
(Nexus class 1 features).
•
eDMA development support features (NXDM)
— Data trace via data write messaging (DWM) and data read messaging (DRM). This allows the
development tool to trace DMA generated reads and/or writes to selected address ranges in the
device’s memory map.
— Watchpoint messaging (WPM) via the auxiliary port.
— Watchpoint trigger enable/disable of data trace messaging.
•
eTPU development support features (NDEDI)
— IEEE-ISTO 5001-2002 standard Class 3 compliant for the eTPU engines.
— Data trace via data write messaging and data read messaging. This allows the development tool
to trace reads and writes to selected shared parameter RAM (SPRAM) address ranges. Four
data trace windows are shared by the two eTPU engines.
— Ownership trace via ownership trace messaging (OTM). OTM facilitates ownership trace by
providing visibility of which channel is being serviced. An ownership trace message is
transmitted to indicate when a new channel service request is scheduled, allowing the
development tools to trace task flow. A special OTM is sent when the engine enters in idle state,
meaning that all requests were serviced and no new requests are yet scheduled.
— Program trace via branch trace messaging. BTM displays program flow discontinuities (start,
jumps, return, etc.), allowing the development tool to interpolate what transpires between the
Summary of Contents for MPC5566
Page 81: ...Introduction MPC5566 Microcontroller Reference Manual Rev 2 1 24 Freescale Semiconductor...
Page 135: ...Signal Description MPC5566 Microcontroller Reference Manual Rev 2 2 54 Freescale Semiconductor...
Page 189: ...Reset MPC5566 Microcontroller Reference Manual Rev 2 4 20 Freescale Semiconductor...
Page 603: ...Flash Memory MPC5566 Microcontroller Reference Manual Rev 2 13 38 Freescale Semiconductor...
Page 609: ...SRAM MPC5566 Microcontroller Reference Manual Rev 2 14 6 Freescale Semiconductor...
Page 1073: ...MPC5566 Microcontroller Reference Manual Rev 2 22 36 Freescale Semiconductor...
Page 1185: ...Nexus MPC5566 Microcontroller Reference Manual Rev 2 25 92 Freescale Semiconductor...