Data Acquisition Message Priority Loss Response - STMicroelectronics SPC572L series Reference Manual

e200z215An3 Nexus 3 Module
66.8.5

Data Acquisition Message Priority Loss Response

If a Data Acquisition Message (DQM) loses arbitration due to contention with higher priority
messages, an error message will be generated to indicate that a DQM has been lost due to
contention.
66.8.6 Ownership Trace Message Priority Loss Response
If an Ownership Trace message (OTM) due to software updates to the Process ID state
loses arbitration due to contention with higher priority messages other than a program
correlation message with EVCODE = 0101 (PID update), an error message will be
generated to indicate that a OTM has been lost due to contention. If the pending OTM is a
periodic update, the event is dropped without generating an error message.
66.8.7 Program Trace Message Priority Loss Response
If a Program Trace message (PTM) loses arbitration due to contention with higher priority
messages, and the discarded PTM is a Program Correlation message, a Resource Full
message for instruction count or history buffer, or a Branch Trace message, then an Error
message is generated to indicate that branch trace information has been lost, and the next
Branch Trace message will be upgraded to a sync-type message.
If the discarded PTM is a Program Correlation message with PID information
(EVCODE=0101), the Error message will indicate a dropped OTM and a dropped Program
Trace (Error code = xxxx11xx).
66.8.8 Program Trace Sync Message Priority Loss Response
If a Program Trace Sync message (SYNC) loses arbitration due to contention with higher
priority messages, the Sync event is discarded, and the next Branch Trace message will be
upgraded to a sync-type message.
66.8.9 Data Trace Message Priority Loss Response
If a Data Trace message (DTM) loses arbitration due to contention with higher priority
messages, the DTM event is discarded, and the next DTM will be upgraded to a sync-type
message.
66.9 Debug Status messages
Debug Status Messages report low power mode and debug status. Debug Status messages
are enabled when Nexus 3 is enabled. Entering/exiting Debug Mode as well as entering,
exiting, or changing Low Power Mode(s) will trigger a Debug Status message, indicating the
value of the most significant byte in the Development Status register. Debug status
information is sent out in the following format:
1948/2058
Figure 1159. Debug Status message format
(8 bits)
DS[31:24]
Fixed length = 18 bits
DocID027809 Rev 4
(4 bits)
(6 bits)
TCODE (000000)
Src. Proc.
RM0400