Motorola MPC533 Reference Manual page 1012

Ownership Trace
22.8 Ownership Trace
This section details the ownership trace support features of the READI module.
Ownership trace provides a macroscopic view, such as task flow reconstruction, when
debugging software written in a high level (or object-oriented) language. It offers the
highest level of abstraction for tracking operating system software execution. This is
especially useful when the developer is not interested in debugging at lower levels.
22.8.1 Ownership Trace Messaging
Ownership trace information is messaged via the auxiliary port using an ownership trace
message (OTM). The ownership trace register (OT), which can be accessed via auxiliary
port, is updated by the operating system software to provide task/process ID information.
When new information is updated in the register by the embedded processor, it is messaged
out via the auxiliary port, allowing development tools to trace ownership flow.
Ownership trace information is messaged out in the following format:
Figure 22-73. Ownership Trace Message Format
22.8.2 Queue Overflow Ownership Trace Error Message
A program/data/ownership trace overrun error occurs when a trace message cannot be
queued due to the queue being full, provided ownership trace is enabled.
The overrun error causes the message queue to be flushed, and a error message to be
queued. The error code within the error message indicates that a program/data/ownership
trace overrun error has occurred. Refer to Table 22-20.
The error message has the following format:
22-80
PRELIMINARY—SUBJECT TO CHANGE WITHOUT NOTICE
[6 bits]
TCODE (2)
Task/Process ID Tag
Length = 38 bits
[6 bits]
TCODE (8)
Length = 11 bits
Figure 22-74. Error Message Format
MPC533 Reference Manual
[32 bits]
[5 bits]
Error Code (0b0 0000,
0b0 0001, 0b0 0010,
0b0 0111)
MOTOROLA