MPC564EVB Freescale Semiconductor, MPC564EVB Datasheet - Page 915

• Manufacturer Part Number: MPC564EVB
• Description: KIT EVAL FOR MPC561/562/563/564
• Manufacturer: Freescale Semiconductor
• Type: Microcontrollerr

Specifications of MPC564EVB

• Contents: Module Board, Installation Guide, Power Supply, Cable, Software and more
• Processor To Be Evaluated: MPC56x
• Data Bus Width: 32 bit
• Interface Type: RS-232, Ethernet
• For Use With/related Products: MPC561, 562, 563, 564
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant

Chapter 23
Development Support
The visibility and controllability requirements of emulators and bus analyzers are in opposition to the trend
of modern microcomputers and microprocessors where many bus cycles are directed to internal resources
and are not visible externally.
In order to enhance the development tool visibility and controllability, some of the development support
functions are implemented in silicon. These functions include program flow tracking, internal watchpoint,
breakpoint generation, and emulation while in debug mode.
This section covers program flow tracking support, breakpoint/watchpoint support, development system
interface support (debug mode) and software monitor debugger support. These features allow efficiency
in debugging systems based on the MPC561/MPC563.
23.1
The mechanism described in this section allows tracking of program instruction flow with almost no
performance degradation. The information provided may be compressed and captured externally and then
parsed by a post-processing program using the microarchitecture defined below.
The program instructions flow is visible on the external bus when the MPC561/MPC563 is programmed
to operate in serial mode and show all fetch cycles on the external bus. This mode is selected by
programming the ISCT_SER (instruction fetch show cycle control) field in the I-bus support control
register (ICTRL), as shown in
fetch cycles appear on the external bus. Processor performance is, therefore, much lower than when
working in regular mode.
These features, together with the fact that most fetch cycles are performed internally (e.g., from the
I-cache), increase performance but make it very difficult to provide the real program trace.
In order to reconstruct a program trace, the program code and the following additional information from
the MCU are needed:
Instructions are fetched sequentially until branches (direct or indirect) or exceptions appear in the program
flow or some stall in execution causes the machine not to fetch the next address. Instructions may be
architecturally executed, or they may be canceled in some stage of the machine pipeline.
Freescale Semiconductor
•
•
•
A description of the last fetched instruction (stall, sequential, branch not taken, branch direct taken,
branch indirect taken, exception taken)
The addresses of the targets of all indirect flow change. Indirect flow changes include all branches
using the link and count registers as the target address, all exceptions, and rfi, mtmsr and mtspr (to
some registers) because they may cause a context switch.
The number of instructions canceled each clock
Program Flow Tracking
Table
MPC561/MPC563 Reference Manual, Rev. 1.2
23-26. In this mode, the processor is fetch serialized, and all internal
23-1