MPC561MZP56 Freescale, MPC561MZP56 Datasheet - Page 919

• Manufacturer Part Number: MPC561MZP56
• Manufacturer: Freescale

Specifications of MPC561MZP56

• Cpu Family: MPC56x
• Device Core: PowerPC
• Device Core Size: 32b
• Frequency (max): 56MHz
• Interface Type: QSPI/SCI/SPI/UART
• Total Internal Ram Size: 32KB
• # I/os (max): 56
• Number Of Timers - General Purpose: 22
• Operating Supply Voltage (typ): 2.6/5V
• Operating Supply Voltage (max): 2.7/5.25V
• Operating Supply Voltage (min): 2.5/4.75V
• On-chip Adc: 2(32-chx10-bit)
• Instruction Set Architecture: RISC
• Operating Temp Range: -40C to 125C
• Operating Temperature Classification: Automotive
• Mounting: Surface Mount
• Pin Count: 388
• Package Type: BGA
• Program Memory Type: ROMLess
• Program Memory Size: Not Required
• Lead Free Status / RoHS Status: Not Compliant

Program trace can be used in various ways. Below are two examples of how program trace can be used:
23.1.4.1
The assertion/negation of VSYNC is done using the serial interface implemented in the development port.
In order to synchronize the assertion/negation of VSYNC to an internal event of the CPU, it is possible to
use the internal breakpoints together with debug mode. This method is available only when debug mode
is enabled. For more information on debug mode refer to
The following is an example of steps that enable synchronization of the trace window to the CPU internal
events:
Freescale Semiconductor
•
•
1. Enter debug mode, either immediately out of reset or using the debug mode request
2. Program the hardware to break on the event that marks the start of the trace window using the
3. Enable debug mode entry for the programmed breakpoint in the debug enable register (DER). See
4. Return to the regular code run (see
5. The hardware generates a breakpoint when the programmed event is detected and the machine
6. Program the hardware to break on the event that marks the end of the trace window
7. Assert VSYNC
8. Return to the regular code run. The first report on the VF pins is a VSYNC (VF = 011).
9. The external hardware starts sampling the program trace information upon the report on the VF
10. The hardware generates a breakpoint when the programmed event is detected and the machine
Back trace — Back trace is useful when a record of the program trace before some event occurred
is needed. An example of such an event is some system failure.
In case back trace is needed the external hardware should start sampling the status pins (VF and
VFLS) and the address of all cycles marked with the program trace cycle attribute immediately
when reset is negated. If show cycles is programmed out of reset to show all, all cycles marked
with program trace cycle attribute are visible on the external bus. VSYNC should be asserted
sometime after reset and negated when the programmed event occurs. If no show is programmed
for show cycles, make sure VSYNC is asserted before the Instruction show cycles programming is
changed from show all.
Note that in case the timing of the programmed event is unknown it is possible to use cyclic buffers.
After VSYNC is negated the trace buffer will contain the program flow trace of the program
executed before the programmed event occurred.
Window trace — Window trace is useful when a record of the program trace between two events
is needed. In case window trace is needed the VSYNC pin should be asserted between these two
events.
After the VSYNC pin is negated the trace buffer will contain information describing the program
trace of the program executed between the two events.
control registers defined in
Section 23.6.13, “Development Port Data Register
enters debug mode (see
pins of VSYNC
enters debug mode
Synchronizing the Trace Window to the CPU Internal Events
Section 23.3.1.2, “Entering Debug
MPC561/MPC563 Reference Manual, Rev. 1.2
Section 23.2, “Watchpoints and Breakpoints
Section 23.3.1.6, “Exiting Debug
Section 23.3, “Development System
(DPDR)”)
Mode”)
Mode”)
Support”
Development Support
Interface.”
23-5