READI Module
MPC561/MPC563 Reference Manual, Rev. 1.2
24-80
Freescale Semiconductor
When the RCPU is in debug mode, program trace is not allowed. If program trace is enabled, a program
trace synchronization message is generated when debug mode exits.
When the RCPU is in debug mode, data trace and R/W access are allowed.
The flow chart in
shows RCPU development access configuration via READI. The modes
of RCPU development access via READI are described below. Allowed modes are also summarized in
Section 24.14.2.4, “RCPU Development Access Flow Diagram
24.14.2.1 Enabling RCPU Development Access Via READI Signals
Reset sequencing is done by the tool to initialize the READI signals and registers by asserting RSTI (the
device sends out the device ID message after the RSTI negation). System reset is held by the tool until the
READI module is reset and initialized with desired RCPU development access setting.
NOTE
The READI module will ignore any incoming DSDI data messages when
the module is not configured for RCPU development access.
24.14.2.2 Entering Background Debug Mode (BDM) Via READI Signals
There are three ways to enter debug mode (provided debug mode has been enabled):
1. Enter debug mode (halted state) out-of-system reset through READI module configuration. This is
displayed in
.
2. Enter debug mode by downloading breakpoint instructions through RCPU development access
when in non-debug (running) mode.
3. Enter debug mode if an exception or interrupt occurs.
When entering debug mode following an exception/breakpoint, the RCPU signals VFLS[0:1] are equal to
0b11. This causes READI to send a BDM status message to the tool indicating that the RCPU has entered
debug mode and is now expecting instructions from the READI signals.
Debug mode enabling through READI and entering debug mode out of system reset is done by setting the
following bits in the DC register (DME=0b1, DOR=0b1) during system reset. Debug mode entry causes
RCPU to halt.
24.14.2.3 Non-Debug Mode Access of RCPU Development Access
The RCPU development access can be also be used while the RCPU is not halted (in debug mode). This
feature is used to send in breakpoints or synchronization events to the RCPU. Please refer to
” for further details.
Non-debug mode access of RCPU development can be achieved by configuring the READI module to take
control of RCPU development access during module configuration of the DC register (DME=0b0,
DOR=0bx).
Summary of Contents for MPC561
Page 84: ...MPC561 MPC563 Reference Manual Rev 1 2 lxxxiv Freescale Semiconductor...
Page 144: ...Signal Descriptions MPC561 MPC563 Reference Manual Rev 1 2 2 46 Freescale Semiconductor...
Page 206: ...Central Processing Unit MPC561 MPC563 Reference Manual Rev 1 2 3 62 Freescale Semiconductor...
Page 302: ...Reset MPC561 MPC563 Reference Manual Rev 1 2 7 14 Freescale Semiconductor...
Page 854: ...Time Processor Unit 3 MPC561 MPC563 Reference Manual Rev 1 2 19 24 Freescale Semiconductor...
Page 968: ...Development Support MPC561 MPC563 Reference Manual Rev 1 2 23 54 Freescale Semiconductor...
Page 1144: ...Internal Memory Map MPC561 MPC563 Reference Manual Rev 1 2 B 34 Freescale Semiconductor...
Page 1212: ...TPU3 ROM Functions MPC561 MPC563 Reference Manual Rev 1 2 D 60 Freescale Semiconductor...
Page 1216: ...Memory Access Timing MPC561 MPC563 Reference Manual Rev 1 2 E 4 Freescale Semiconductor...