0x08000000
0x08001000
0x080013FF
0x08003800
0x08003FFF
RTPRAM1REG1 = 0x33001000
RTPRAM1REG2 = 0x74003800
4GB Address
Space
2kB
Region 2
1kB
Region 1
2 Trace Regions
• Region 1
– starts at 0x08001000 with size of 1kB
– CPU write access are traced
• Region 2
– starts at 0x08003800 with size of 2kB
– CPU and other master write accesses are traced
Module Operation
2160
SPNU563A – March 2018
Copyright © 2018, Texas Instruments Incorporated
RAM Trace Port (RTP)
37.2.3.1 Inverse Trace Regions
The RTP can be configured to trace accesses which fall into, or are made outside of the specified regions.
This can be accomplished by the INV_RGN bit. If this bit is 0, all access which are made inside a region
are traced. If the bit is 1, all accesses outside the region are traced. The INV_RGN bit affects all regions
of the RTP, see the RTP global control register (RTPGLBCTRL).
There are certain restrictions when using INV_RGN = 1:
•
In this mode up to 2 regions can be excluded from tracing accesses to a particular RAM.
•
Inverse trace regions with one or both regions of a RAM programmed with blocksize = 0 is not
supported. If only one address range should be excluded from the trace, either the address range has
to be covered by both regions (e.g. excluding 1kB range with two 512B regions), or both regions have
to be programmed with the same start address and region size. If the whole RAM should be traced,
inverse region mode should not be used, instead the 2 regions could be programmed to cover the
entire address range with INV_RGN = 0.
•
Both regions have to define the same access rights (bits CPU_DMA and RW; see
) for
accesses outside of the region of each RAM block, otherwise the result is undefined.
•
Peripheral trace in inverse region mode is not supported. The 16 MByte peripheral address range
cannot be covered entirely by the 17 bit address definition of the RTP protocol.
37.2.3.2 Overlapping Trace Regions
When in INV_RGN = 0 mode with both regions overlapping and an access is done into the overlapping
address range, both regions will be checked for their access rights and if one or both is satisfied, the
access will be traced. In the case that both regions would allow the data to be traced, there will still be
only one entry into the FIFO.
If accesses to peripherals are done within overlapping regions, the REG bit in the protocol will be 0,
denoting Region 1 (see
).
Figure 37-5. Example for Trace Region Setup