37-2
MPC860 PowerQUICC UserÕs Manual
MOTOROLA
Part VI. Debug and Test
using this information to reconstruct which instructions actually reach retirement.
Instructions are fetched sequentially until branches (direct or indirect), exceptions or
interrupts appear in the program ßow or until a stall in execution forces the machine to
avoid fetching the next address. These instructions may be architecturally executed or they
may be canceled in some stage of the machine pipeline.
The information required to enable reconstruction of program trace includes:
¥
A description of the last fetched instruction (stall, sequential, branch not taken,
branch direct taken, branch indirect taken, interrupt/exception taken).
¥
The addresses of the targets of all indirect ßow changes. Indirect ßow changes
include all branches using the link and count registers as the target address, all
interrupts/exceptions, and rÞ and mtmsr (because they may cause context
switches).
¥
The number of instructions canceled on each clock.
The following sections deÞne how this information is generated and how it should be used
to reconstruct the program trace.
37.1.1 Program Trace Functional Description
To make the events that occur in the machine visible, a few dedicated pins are used. Also,
a special bus cycle attribute called program trace cycle is deÞned. The program trace cycle
attribute is attached to all fetch cycles resulting from indirect ßow changes. When program
trace recording is required, the user can ensure these cycles are visible on the external bus.
The core can be forced to show all fetch cycles marked with the program trace cycle
attribute either by setting TECR[VSYNC] of the development port or by programming
ISCT_SER in the instruction support control register (ICTRL). For more information on
VSYNC see Section 37.3.2, ÒDevelopment Port Communication.Ó Both states described
here are subsequently referred to as VSYNC state.
The VSYNC state forces all fetch cycles marked with the program trace cycle attribute to
be visible on the external bus, even if their data is found in one of the internal devices. To
enable the external hardware to properly synchronize with the internal activity of the core,
entering VSYNC state forces the machine to synchronize and the Þrst fetch after this
synchronization to be marked as a program trace cycle and be seen on the external bus.
In VSYNC state, fetch cycles marked with the program trace cycle attribute become visible
on the external bus. These cycles generate regular bus cycles when the instructions reside
in an external device or generate address-only cycles when instructions are in internal
devices (I-cache and internal memory). In VSYNC state, performance degrades because of
the additional external bus cycles. However, this degradation is very small.
Summary of Contents for MPC860 PowerQUICC
Page 3: ...MPC860UM AD 07 98 REV 1 MPC860 PowerQUICC ª UserÕs Manual ...
Page 36: ...xxxvi MPC860 PowerQUICC UserÕs Manual MOTOROLA CONTENTS Paragraph Number Title Page Number ...
Page 78: ...I iv MPC860 PowerQUICC UserÕs Manual MOTOROLA Part I Overview ...
Page 88: ...1 10 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part I Overview ...
Page 114: ...3 16 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part I Overview ...
Page 226: ...8 32 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part II PowerPC Microprocessor Module ...
Page 262: ...9 36 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part II PowerPC Microprocessor Module ...
Page 274: ...III iv MPC860 PowerQUICC UserÕs Manual MOTOROLA Part III Configuration ...
Page 320: ...12 12 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part III Configuration ...
Page 325: ...MOTOROLA Part IV Hardware Interface IV v Part IV Hardware Interface ...
Page 326: ...IV vi MPC860 PowerQUICC UserÕs Manual MOTOROLA Part IV Hardware Interface ...
Page 352: ...13 26 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part IV Hardware Interface ...
Page 394: ...14 42 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part IV Hardware Interface ...
Page 426: ...15 32 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part IV Hardware Interface ...
Page 530: ...17 26 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part IV Hardware Interface ...
Page 632: ...21 44 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part V The Communications Processor Module ...
Page 660: ...22 28 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part V The Communications Processor Module ...
Page 708: ...24 24 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part V The Communications Processor Module ...
Page 748: ...27 20 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part V The Communications Processor Module ...
Page 846: ...31 20 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part V The Communications Processor Module ...
Page 914: ...35 12 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part V The Communications Processor Module ...
Page 948: ...36 34 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part V The Communications Processor Module ...
Page 998: ...37 48 MPC860 PowerQUICC UserÕs Manual MOTOROLA Part VI Debug and Test ...
Page 1016: ...A 10 MPC860 PowerQUICC UserÕs Manual MOTOROLA Appendixes ...
Page 1024: ...B 8 MPC860 PowerQUICC UserÕs Manual MOTOROLA Appendixes ...
Page 1030: ...C 6 MPC860 PowerQUICC UserÕs Manual MOTOROLA Appendixes ...
Page 1086: ...Glossary 12 MPC860 PowerQUICC UserÕs Manual MOTOROLA ...
Page 1106: ......