Introduction
MPC5565 Microcontroller Reference Manual, Rev. 1.0
Freescale Semiconductor
1-17
1.4.20
Nexus Development Interface (NDI)
The Nexus development interface (NDI) module provides real-time development support capabilities for
the MPC5500 family’s MCU built on the Power Architecture in compliance with the IEEE
®
-ISTO
5001-2003 standard. This development support is supplied for MCUs without requiring external address
and data pins for internal visibility. The NDI module integrates several Nexus modules to provide the
development support interface for the MPC5500 family. The NDI module interfaces to the host processor,
single or dual eTPU processors, and internal buses to provide development support as per the
IEEE
®
-ISTO 5001-2003 standard. The development support provided includes program trace, data trace,
watchpoint trace, ownership trace, run-time access to the MCU internal memory map, Nexus trace of
eDMA transfers, and access to the Power Architecture and eTPU internal registers during halt, via the
auxiliary port. The Nexus interface also supports a JTAG only mode using only the JTAG pins.
1.4.21
JTAG Controller (JTAGC)
The JTAG controller (JTAGC) module provides the means to test chip functionality and connectivity while
remaining transparent to system logic when not in test mode. Testing is performed via a boundary scan
technique, as defined in the IEEE
®
1149.1-2001 standard. All data input to and output from the JTAGC
module is communicated in serial format. The JTAGC module is compliant with the IEEE
®
1149.1-2001
standard.
1.5
MPC5500 Family Memory Map
This section describes the MPC5500 family memory map. All addresses in the device, including those that
are reserved, are identified in the tables. The addresses represent the physical addresses assigned to each
module. Logical addresses are translated by the MMU into physical addresses.
Reserved register bits are allocated for future products and have a default value of zero. When writing to
a register, the reserved bits default values must be written as well. Most device features are activated by
writing a non-zero value to them.
Reserved memory is allocated for future products, therefore do not write to memory segments that are
designated as reserved.
Under software control of the MMU, the logical addresses allocated to modules can be changed on a
minimum of a 4 KB boundary. Peripheral modules may be redundantly mapped. The customer must use
the MMU to prevent corruption.
Summary of Contents for MPC5565
Page 18: ...MPC5565 Microcontroller Reference Manual Devices Supported MPC5565 MPC5565 RM Rev 1 0 09 2007...
Page 34: ...MPC5565 Reference Manual Rev 1 0 Freescale Semiconductor 15...
Page 35: ...MPC5565 Reference Manual Rev 1 0 16 Freescale Semiconductor...
Page 553: ...Flash Memory MPC5565 Microcontroller Reference Manual Rev 1 0 13 38 Freescale Semiconductor...
Page 559: ...SRAM MPC5565 Microcontroller Reference Manual Rev 1 0 14 6 Freescale Semiconductor...
Page 973: ...Preface MPC5565 Microcontroller Reference Manual Rev 1 0 21 36 Freescale Semiconductor...
Page 1153: ...Calibration MPC5565 Microcontroller Reference Manual Rev 1 0 B 8 Freescale Semiconductor...