SPRUIM2H May 2020 – October 2023 AM2431 , AM2432 , AM2434 , AM6411 , AM6412 , AM6421 , AM6422 , AM6441 , AM6442
Table 8-2664 lists the memory-mapped registers for a RAT module. All register offset addresses not listed in Table 8-2664 should be considered as reserved locations and the register contents should not be modified.
This section contains only the RAT register descriptions. For specific physical addresses associated with a RAT module, see the corresponding Registers section of the modules and subsystems listed in Table 8-2662 that have integrated RAT.
Offset | Acronym | Register Name |
---|---|---|
0h | RAT_PID | Revision Register |
4h | RAT_CONFIG | Configuration Register |
20h + formula | RAT_CTRL_k | Region Control Register |
24h + formula | RAT_BASE_k | Region Base Register |
28h + formula | RAT_TRANS_L_k | Region Translated Lower Address |
2Ch + formula | RAT_TRANS_U_k | Region Translated Upper Address |
804h | RAT_DESTINATION_ID | Destination ID Register |
820h | RAT_EXCEPTION_LOGGING_CONTROL | Exception Logging Control Register |
824h | RAT_EXCEPTION_LOGGING_HEADER0 | Exception Logging Header 0 Register |
828h | RAT_EXCEPTION_LOGGING_HEADER1 | Exception Logging Header 1 Register |
82Ch | RAT_EXCEPTION_LOGGING_DATA0 | Exception Logging Data 0 Register |
830h | RAT_EXCEPTION_LOGGING_DATA1 | Exception Logging Data 1 Register |
834h | RAT_EXCEPTION_LOGGING_DATA2 | Exception Logging Data 2 Register |
838h | RAT_EXCEPTION_LOGGING_DATA3 | Exception Logging Data 3 Register |
840h | RAT_EXCEPTION_PEND_SET | Exception Logging Interrupt Pending Set Register |
844h | RAT_EXCEPTION_PEND_CLEAR | Exception Logging Interrupt Pending Clear Register |
848h | RAT_EXCEPTION_ENABLE_SET | Exception Logging Interrupt Enable Set Register |
84Ch | RAT_EXCEPTION_ENABLE_CLEAR | Exception Logging Interrupt Enable Clear Register |
850h | RAT_EOI_REG | EOI Register |
RAT_PID is shown in Figure 8-1330 and described in Table 8-2665.
Return to Summary Table.
The Revision Register contains the major and minor revisions for the module.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
SCHEME | BU | FUNC | |||||
R-1h | R-2h | R-680h | |||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
FUNC | |||||||
R-680h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RTL | MAJOR | ||||||
R-5h | R-1h | ||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
CUSTOM | MINOR | ||||||
R-0h | R-0h | ||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-30 | SCHEME | R | 1h | PID register scheme |
29-28 | BU | R | 2h | Business Unit: 2h = Processors |
27-16 | FUNC | R | 680h | Module ID |
15-11 | RTL | R | 5h | RTL Revision. Will vary depending on release. |
10-8 | MAJOR | R | 1h | Major Revision |
7-6 | CUSTOM | R | 0h | Custom |
5-0 | MINOR | R | 0h | Minor Revision |
RAT_CONFIG is shown in Figure 8-1331 and described in Table 8-2666.
Return to Summary Table.
The Configuration Register contains the configuration values for the module.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | ADDR_WIDTH | ||||||||||||||
R-X | R-30h | ||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
ADDRS | REGIONS | ||||||||||||||
R-1h | R-10h | ||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | RESERVED | R | X | |
23-16 | ADDR_WIDTH | R | 30h | Number of address bits |
15-8 | ADDRS | R | 1h | Number of addresses |
7-0 | REGIONS | R | 10h | Number of regions |
RAT_CTRL_k is shown in Figure 8-1332 and described in Table 8-2667.
Return to Summary Table.
The Control for Region a
Offset = 1020h + (k * 10h); where k = 0h to Fh
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
EN | RESERVED | ||||||
R/W-0h | R/W-X | ||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | |||||||
R/W-X | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | |||||||
R/W-X | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | SIZE | ||||||
R/W-X | R/W-0h | ||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | EN | R/W | 0h | Enable for the Region 0h = Region disabled 1h = Region enabled |
30-6 | RESERVED | R/W | X | |
5-0 | SIZE | R/W | 0h | Size of the Region in Address Bits. 0h = 1 byte, 1h = 2B, 2h = 4B, 3h = 8B, etc. up to 20h = 4GB. |
RAT_BASE_k is shown in Figure 8-1333 and described in Table 8-2668.
Return to Summary Table.
The Base Address for Region a. This is the source address for matching to a region.
Offset = 1024h + (k * 10h); where k = 0h to Fh
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
BASE | |||||||||||||||||||||||||||||||
R/W-0h | |||||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | BASE | R/W | 0h | Base Address for the Region. It must be aligned to the programmed size. |
RAT_TRANS_L_k is shown in Figure 8-1334 and described in Table 8-2669.
Return to Summary Table.
The Translated Lower Address Bits for Region a
Offset = 1028h + (k * 10h); where k = 0h to Fh
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
LOWER | |||||||||||||||||||||||||||||||
R/W-0h | |||||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | LOWER | R/W | 0h | Translated Lower Address Bits for the Region. It must be aligned to the programmed size. |
RAT_TRANS_U_k is shown in Figure 8-1335 and described in Table 8-2670.
Return to Summary Table.
The Translated Upper Address Bits for Region a
Offset = 102Ch + (k * 10h); where k = 0h to Fh
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | UPPER | ||||||||||||||||||||||||||||||
R/W-X | R/W-0h | ||||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | RESERVED | R/W | X | |
15-0 | UPPER | R/W | 0h | Translated Upper Address Bits for the Region |
RAT_DESTINATION_ID is shown in Figure 8-1336 and described in Table 8-2671.
Return to Summary Table.
The Destination ID Register defines the destination ID value for error messages.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | |||||||||||||||
R/W-X | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | DEST_ID | ||||||||||||||
R/W-X | R/W-0h | ||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-8 | RESERVED | R/W | X | |
7-0 | DEST_ID | R/W | 0h | The destination ID. This field can be used for identifying a destination tag so that software can identify who should process the error message. In case of single consumer of the error messages this field is not useful and can be programmed to any value. |
RAT_EXCEPTION_LOGGING_CONTROL is shown in Figure 8-1337 and described in Table 8-2672.
Return to Summary Table.
The Exception Logging Control Register controls the exception logging.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RESERVED | |||||||
R/W-X | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | |||||||
R/W-X | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | |||||||
R/W-X | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | DISABLE_INTR | DISABLE_F | |||||
R/W-X | R/W-0h | R/W-0h | |||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-2 | RESERVED | R/W | X | |
1 | DISABLE_INTR | R/W | 0h | Disables logging interrupt when set. |
0 | DISABLE_F | R/W | 0h | Disables logging when set. |
RAT_EXCEPTION_LOGGING_HEADER0 is shown in Figure 8-1338 and described in Table 8-2673.
Return to Summary Table.
The Exception Logging Header 0 Register contains the first word of the header.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
TYPE_F | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
SRC_ID | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
SRC_ID | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
DEST_ID | |||||||
R-0h | |||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | TYPE_F | R | 0h | Type. 4h = RAT. |
23-8 | SRC_ID | R | 0h | Source ID. This field uniquely identifies the particular RAT and region that caused the error. Each RAT has a unique source ID value (see Table 8-2663). The error message increments that value by the region number associated with the error. |
7-0 | DEST_ID | R | 0h | Destination ID. |
RAT_EXCEPTION_LOGGING_HEADER1 is shown in Figure 8-1339 and described in Table 8-2674.
Return to Summary Table.
The Exception Logging Header 1 Register contains the second word of the header.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
GROUP | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
CODE | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | |||||||
R-X | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | |||||||
R-X | |||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-24 | GROUP | R | 0h | Group. |
23-16 | CODE | R | 0h | Code. 1h = Boundary crossing error. |
15-0 | RESERVED | R | X |
RAT_EXCEPTION_LOGGING_DATA0 is shown in Figure 8-1340 and described in Table 8-2675.
Return to Summary Table.
The Exception Logging Data 0 Register contains the first word of the data.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
ADDR_L | |||||||||||||||||||||||||||||||
R-0h | |||||||||||||||||||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-0 | ADDR_L | R | 0h | The lower 32 bits of the address attempted to be accessed. |
RAT_EXCEPTION_LOGGING_DATA1 is shown in Figure 8-1341 and described in Table 8-2676.
Return to Summary Table.
The Exception Logging Data 1 Register contains the second word of the data.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | |||||||||||||||
R-X | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
ADDR_H | |||||||||||||||
R-0h | |||||||||||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | RESERVED | R | X | |
15-0 | ADDR_H | R | 0h | The upper 12 bits of the address attempted to be accessed. |
RAT_EXCEPTION_LOGGING_DATA2 is shown in Figure 8-1342 and described in Table 8-2677.
Return to Summary Table.
The Exception Logging Data 2 Register contains the third word of the data.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RESERVED | ROUTEID | ||||||
R-X | R-0h | ||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
ROUTEID | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | WRITE | READ | DEBUG | CACHEABLE | PRIV | SECURE | |
R-X | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | |
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
PRIV_ID | |||||||
R-0h | |||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-28 | RESERVED | R | X | |
27-16 | ROUTEID | R | 0h | Route ID transaction attribute. |
15-14 | RESERVED | R | X | |
13 | WRITE | R | 0h | Indicates write transaction. 0h = No write transaction 1h = Write transaction |
12 | READ | R | 0h | Indicates read transaction. 0h = No read transaction 1h = Read transaction |
11 | DEBUG | R | 0h | Indicates debug access. 0h = No debug access 1h = Debug access |
10 | CACHEABLE | R | 0h | Cacheable transaction attribute. 0h = The transaction could not cache the data for the CPU 1h = The transaction could cache the data for the CPU |
9 | PRIV | R | 0h | Indicates privilege access. 0h = No privilege access 1h = Privilege access |
8 | SECURE | R | 0h | Indicates secure access. 0h = No secure access 1h = Secure access |
7-0 | PRIV_ID | R | 0h | Priv ID transaction attribute. |
RAT_EXCEPTION_LOGGING_DATA3 is shown in Figure 8-1343 and described in Table 8-2678.
Return to Summary Table.
The Exception Logging Data 3 Register contains the fourth word of the data. Reading this register will clear the error pending bit.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RESERVED | |||||||
R-X | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | |||||||
R-X | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | BYTECNT | ||||||
R-X | R-0h | ||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
BYTECNT | |||||||
R-0h | |||||||
LEGEND: R = Read Only; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-10 | RESERVED | R | X | |
9-0 | BYTECNT | R | 0h | Byte count transaction attribute. |
RAT_EXCEPTION_PEND_SET is shown in Figure 8-1344 and described in Table 8-2679.
Return to Summary Table.
The Exception Logging Interrupt Pending Set Register allows to set the pend signal.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RESERVED | |||||||
R/W-X | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | |||||||
R/W-X | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | |||||||
R/W-X | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | PEND_SET | ||||||
R/W-X | R/W1S-0h | ||||||
LEGEND: R/W = Read/Write; R/W1S = Read/Write 1 to Set Bit; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-1 | RESERVED | R/W | X | |
0 | PEND_SET | R/W1S | 0h | Write a 1 to set the exception pend signal. |
RAT_EXCEPTION_PEND_CLEAR is shown in Figure 8-1345 and described in Table 8-2680.
Return to Summary Table.
The Exception Logging Interrupt Pending Clear Register allows to clear the pend signal.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RESERVED | |||||||
R/W-X | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | |||||||
R/W-X | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | |||||||
R/W-X | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | PEND_CLR | ||||||
R/W-X | R/W1C-0h | ||||||
LEGEND: R/W = Read/Write; R/W1C = Read/Write 1 to Clear Bit; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-1 | RESERVED | R/W | X | |
0 | PEND_CLR | R/W1C | 0h | Write a 1 to clear the exception pend signal. |
RAT_EXCEPTION_ENABLE_SET is shown in Figure 8-1346 and described in Table 8-2681.
Return to Summary Table.
The Exception Logging Interrupt Enable Set Register allows to set the interrupt enable signal.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RESERVED | |||||||
R/W-X | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | |||||||
R/W-X | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | |||||||
R/W-X | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | ENABLE_SET | ||||||
R/W-X | R/W1S-0h | ||||||
LEGEND: R/W = Read/Write; R/W1S = Read/Write 1 to Set Bit; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-1 | RESERVED | R/W | X | |
0 | ENABLE_SET | R/W1S | 0h | Write a 1 to set the exception interrupt enable signal. |
RAT_EXCEPTION_ENABLE_CLEAR is shown in Figure 8-1347 and described in Table 8-2682.
Return to Summary Table.
The Exception Logging Interrupt Enable Clear Register allows to clear the interrupt enable signal.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RESERVED | |||||||
R/W-X | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | |||||||
R/W-X | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | |||||||
R/W-X | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | ENABLE_CLR | ||||||
R/W-X | R/W1C-0h | ||||||
LEGEND: R/W = Read/Write; R/W1C = Read/Write 1 to Clear Bit; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-1 | RESERVED | R/W | X | |
0 | ENABLE_CLR | R/W1C | 0h | Write a 1 to clear the exception interrupt enable signal. |
RAT_EOI_REG is shown in Figure 8-1348 and described in Table 8-2683.
Return to Summary Table.
EOI Register
The EOI register is used to re-trigger the pulse interrupt signal to ensure that any nested interrupt events are serviced. The software interrupt handler must write to the EOI register at the end of the current interrupt processing routine, so that new events can re-trigger the pulse interrupt signal again. For level interrupt signals the EOI register is not functional and must not be used.
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | EOI_WR | ||||||||||||||||||||||||||||||
R/W-X | R/W-0h | ||||||||||||||||||||||||||||||
LEGEND: R/W = Read/Write; -n = value after reset |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | RESERVED | R/W | X | |
15-0 | EOI_WR | R/W | 0h | EOI Register |