Nexus Development Interface (NDI)
PXN20 Microcontroller Reference Manual, Rev. 1
36-74 Freescale Semiconductor
Table 36-45 shows the error code encodings used when reporting an error via the Nexus2+ Error Message.
Table 36-46 shows the encodings used for resource codes for certain messages.
Program Trace —
Program Correlation
Message
6 6 TCODE Fixed TCODE number = 33 (0x21)
4 4SRCFixed source processor identifier
4 4 EVCODE Fixed event correlated w/ program flow (Refer to Table 36-47)
1 8 I-CNT Variable # sequential instructions executed since last taken branch
1 32 HIST Variable branch / predicate instruction history (see Section 36.7.9.3.1,
Branch Trace Messaging (BTM))
1
The user can select between the two types of program trace. The advantages for each are discussed in Section 36.7.9.3.1,
Branch Trace Messaging (BTM). If the branch history method is selected, the shaded TCODEs above are not messaged out.
Table 36-45. Error Code Encoding (TCODE = 8)
Error Code
(ECODE)
Description
00000 Ownership trace overrun
00001 Program trace overrun
00010 Reserved
00011 Read/write access error
00101 Invalid access opcode (Nexus register unimplemented)
00110 Watchpoint overrun
00111 Program trace and ownership trace overrun
01000 (Program trace or ownership trace) and watchpoint overrun
01001–0111 Reserved
11000 BTM lost due to collision w/ higher priority message
11001–11111 Reserved
Table 36-46. RCODE values (TCODE = 27)
Resource Code
(RCODE)
Description
Resource Data
(RDATA)
0000 Program Trace Instruction Counter overflow (reached 255 and was reset) 0xFF
0001 Program Trace, Branch / Predicate Instruction History. This type of packet
is terminated by a stop bit set to 1 after the last history bit.
Branch History. This type of
packet is terminated by a stop bit
set to a 1 after the last history bit.
Table 36-44. Public TCODEs Supported by Nexus2+ (continued)
Message Name
Packet Size
(bits) Packet
Name
Packet
Type
Packet Description
Min Max
To Next Page
Loading...
