PXN20RM Datasheet, PDF (1237/1376 Pages) Freescale Semiconductor, Inc – PXN20 Microcontroller

Nexus Development Interface (NDI)
Traditional BTM messages maintain their temporal ordering because each event that can cause a message
to be queued enters the FIFO in the order it occurred and is messaged out in that same order.
36.7.9.3.2 BTM Message Formats
The e200z0 Nexus2+ module supports three types of traditional BTM messages—direct, indirect, and
synchronization messages. It supports two types of branch history BTM messages—indirect branch
history, and indirect branch history with synchronization messages. Debug status messages and error
messages are also supported.
Indirect Branch Messages (History)
Indirect branches include all taken branches whose destination is determined at run time, interrupts and
exceptions. If DC[PTM] is set, indirect branch information is messaged out in the following format:
5
4
3
2
1
HIST
U-ADDR
I-CNT
SRC
TCODE (011100)
MSB 1–32 bits
1–32 bits
1–8 bits
4 bits
6 bits LSB
Max length = 82 bits; Min length = 13 bits
Figure 36-63. Indirect Branch Message (History) Format
Indirect Branch Messages (Traditional)
If DC[PTM] is cleared, indirect branch information is messaged out in the following format:
4
3
2
1
U-ADDR
I-CNT
SRC
TCODE (000100)
MSB 1–32 bits
1–8 bits
4 bits
6 bits LSB
Max length = 50 bits; Min length = 12 bits
Figure 36-64. Indirect Branch Message Format
Direct Branch Messages (Traditional)
Direct branches (conditional or unconditional) are all taken branches whose destination is fixed in the
instruction opcode. Direct branch information is messaged out in the following format:
3
2
1
I-CNT
SRC
TCODE (000011)
MSB 1–8 bits
4 bits
6 bits
LSB
Max length = 18 bits; Min length = 11 bits
Figure 36-65. Direct Branch Message Format
Freescale Semiconductor
PXN20 Microcontroller Reference Manual, Rev. 1
36-87