Nexus Development Interface (NDI)
MPC5510 Microcontroller Family Reference Manual, Rev. 1
20-20
Freescale Semiconductor
Preliminary
20.5.8.1
EVTI Generated Break Request
To use the EVTI pin as a debug request, the EIC field in the e200z0 Development Control
Register 1 (DC1) must be set to configure the EVTI input as a debug request. The Shared Nexus Control
Register (SNC) EVTI Debug Request Enable field can then be used to control which core, or both,
responds to the assertion of the EVTI pin.
20.5.8.2
Nexus Event-Out Generated Break Request
On MPC5510, the event-out signal has been connected to the external debug event 2 input to
both cores. This allows the assertion of a Nexus event-out signal to trigger a debug request to either or both
cores.
To use the Nexus event-out signal as a debug request, the EOC field in the e200z0 development
control register 1 (DC1) must be set to enable the assertion of the event-out signal on the occurrence of a
watchpoint, entry into debug mode, or upon a time-stamping event.
To enable the debug request for a given core, the DEVT2 field of the associated core’s OnCE debug control
register 0 (DBCR0) must be set to enable debug events when the DEVT2 input asserts.
A description of Nexus support when leaving low power sleep mode is given in
”.
show the process flow to initialize the e200z1 as the core generating the
event-out break request, and the e200z0 as the core receiving the break request. This configuration will
cause the e200z0 to follow the e200z1 into debug mode. The e200z0 may be configured as the core
generating the break request, and the e200z1 as the core receiving the break request, by reversing the roles
of the e200z0 and e200z1 in