Nexus3/ Module
e200z3 Power Architecture Core Reference Manual, Rev. 2
10-10
Freescale Semiconductor
NOTE
Program trace can be implemented using either branch history/predicate
instruction messages, or traditional direct/indirect branch messages, and the
user can select between the two types of program trace. The advantages of
each are discussed in
Section 10.7.1, “Branch Trace Messaging (BTM).”
If
the branch history method is selected, the shaded TCODES above will not
be messaged out.
10.4
Nexus3/ Programmer’s Model
This section describes the Nexus3/ programmers model. Nexus3/ registers are accessed
using the JTAG/OnCE port in compliance with IEEE 1149.1. See
Register Access Through JTAG/OnCE,”
for details on Nexus3/ register access.
NOTE
Nexus3/ registers and output signals are numbered using bit 0 as
the least significant bit. This bit ordering is consistent with the ordering
defined by the IEEE-ISTO 5001 standard.
shows the register map for the Nexus3/ module.
010
Word (4 bytes)
011
Double-word (8 bytes)
100
String (3 bytes)
101–111
Reserved
Table 10-7. Nexus3/ Register Map
Nexus Register
Nexus
Access
Opcode
Read/Write
Read
Address
Write
Address
Client select control (CSC)
1
0x1
R
0x02
—
Port configuration register (PCR)
PCR_INDEX
R/W
—
—
Development control1 (DC1)
0x2
R/W
0x04
0x05
Development control2 (DC2)
0x3
R/W
0x06
0x07
Development status (DS)
0x4
R
0x08
—
Read/write access control/status (RWCS)
0x7
R/W
0x0E
0x0F
Read/write access address (RWA)
0x9
R/W
0x12
0x13
Read/write access data (RWD)
0xA
R/W
0x14
0x15
Watchpoint trigger (WT)
0xB
R/W
0x16
0x17
Table 10-6. Data Trace Size Encodings (TCODE = 5, 6, 13, or 14) (continued)
DTM Size Encoding
Transfer Size