Public Version
SDTI Module
www.ti.com
Table 27-39. SDTI Memory Mapping (continued)
Name
Address Offset
Address
Size
Start
Stop
Start
Stop
CPU1 timestamped
0x00 0400
0x00 07FF
0x5460 0400
0x5460 07FF
1k
message
CPU2 message
0x00 0800
0x00 0BFF
0x5460 0800
0x5460 0BFF
1k
CPU2 timestamped
0x00 0C00
0x00 0FFF
0x5460 0C00
0x5460 0FFF
1k
message
Channel 1
0x00 1000
0x00 1FFF
0x5460 1000
0x5460 1FFF
4k
Channel 2
0x00 2000
0x00 2FFF
0x5460 2000
0x5460 2FFF
4k
to
–
–
–
–
Channel 254
0x0F E000
0x0F EFFF
0x546F E000
0x546F EFFF
4k
Channel 255
0x0F F000
0x0F FFFF
0x546F F000
0x546F FFFF
4k
CPU1 message
0x0F F000
0x0F F3FF
0x546F F000
0x546F F3FF
1k
CPU1 timestamped
0x0F F400
0x0F F7FF
0x546F F400
0x546F F7FF
1k
message
CPU2 message
0x0F F800
0x0F FBFF
0x546F F800
0x546F FBFF
1k
CPU2 timestamped
0x0F FC00
0x0F FFFF
0x546F FC00
0x546F FFFF
1k
message
Table 27-40. Channel Access Example
Message
Channel Number
SDTI Address Offset
CPU1 message
0
0x00000 – 0x003FF
CPU1 timestamped message
0
0x00400 – 0x007FF
CPU1 message
26
0x1A000 – 0x1A3FF
CPU1 timestamped message
134
0x86400 – 0x867FF
CPU2 message
0
0x00800 – 0x00BFF
CPU2 timestamped message
0
0x00C00 – 0x00FFF
CPU2 message
51
0x33800 – 0x33BFF
CPU2 timestamped message
255
0xFFC00 – 0xFFFFF
27.3.4.9 SDTI Error Handling
The SDTI port returns the in-band error as a response in the following cases:
•
Unsupported master command
•
Unsupported byte enable
•
Unaligned address
•
Application write access to locked SDTI registers
Read and write accesses pointing to memory holes are considered as software errors, not interconnect
errors. Such accesses get a valid response, do not affect the module behavior, and are not reported. In
case of a read command, the returned data is zeroes.
A read from the trace matching address window is also considered a software error and returns a valid
response with don't care data (all zeroes).
A write access to the trace matching window with CPU1 or CPU2 message generation disabled returns a
valid response.
Read accesses are not affected by the state of the lock access register.
Debugger write accesses are never locked (affected by the state of the
register).
3618
Debug and Emulation
SWPU177N – December 2009 – Revised November 2010
Copyright © 2009–2010, Texas Instruments Incorporated