SPRUJF2A March 2026 – March 2026 AM13E23019
Table 33-14 lists the memory-mapped registers for the DEBUGSS_REGS registers. All register offset addresses not listed in Table 33-14 should be considered as reserved locations and the register contents should not be modified.
| Offset | Acronym | Register Name |
|---|---|---|
| 1020h | IIDX | Interrupt index |
| 1028h | IMASK | Interrupt mask |
| 1030h | RIS | Raw interrupt status |
| 1038h | MIS | Masked interrupt status |
| 1040h | ISET | Interrupt set |
| 1048h | ICLR | Interrupt clear |
| 10E0h | EVT_MODE | Event Mode |
| 10FCh | DESC | Module Description |
| 1100h | TXD | Transmit data register |
| 1104h | TXCTL | Transmit control register |
| 1108h | RXD | Receive data register |
| 110Ch | RXCTL | Receive control register |
| 1200h | SPECIAL_AUTH | Special enable authorization register |
| 1210h | APP_AUTH | Application CPU0 authorization register |
Complex bit access types are encoded to fit into small table cells. Table 33-15 shows the codes that are used for access types in this section.
| Access Type | Code | Description |
|---|---|---|
| Read Type | ||
| R | R | Read |
| R-0 | R -0 | Read Returns 0s |
| Write Type | ||
| W | W | Write |
| WK | W K | Write Write protected by a key |
| Reset or Default Value | ||
| -n | Value after reset or the default value | |
IIDX is shown in Figure 33-2 and described in Table 33-16.
Return to the Summary Table.
This register provides the highest priority enabled interrupt index. 0xFF means no event pending. Interrupt 0x0 is the highest priority, 0x1 next highest, and 0xFE is the least priority. The priority order is fixed. However, users can implement their own prioritization schemes using other registers that expose the full set of interrupts that have occurred.
On each read, only one interrupt is indicated. On a read, the current interrupt (highest priority) is automatically cleared by the hardware and the corresponding interrupt flag in the RIS and MIS are cleared as well. After a read from the CPU (not from the debug interface), the register must be updated with the next highest priority interrupt, if none are pending, then it displays 0xFF.
| 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 | STAT | ||||||||||||||||||||||||||||||
| R-0h | R-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | |
| 7-0 | STAT | R | 0h | Interrupt index status
|
IMASK is shown in Figure 33-3 and described in Table 33-17.
Return to the Summary Table.
Interrupt Mask. If a bit is set, then corresponding interrupt is un-masked. Un-masking the interrupt causes the raw interrupt to be visible in IIDX, as well as MIS.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R/W-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R/W-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R/W-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | PWRDWNIFG | PWRUPIFG | RXIFG | TXIFG | |||
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | R/W-0h | |||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-4 | RESERVED | R/W | 0h | |
| 3 | PWRDWNIFG | R/W | 0h | Masks PWRDWNIFG in MIS register
|
| 2 | PWRUPIFG | R/W | 0h | Masks PWRUPIFG in MIS register
|
| 1 | RXIFG | R/W | 0h | Masks RXIFG in MIS register
|
| 0 | TXIFG | R/W | 0h | Masks TXIFG in MIS register
|
RIS is shown in Figure 33-4 and described in Table 33-18.
Return to the Summary Table.
Raw interrupt status. Reflects all pending interrupts, regardless of masking. The RIS register allows the user to implement a poll scheme. A flag set in this register can be cleared by writing 1 to the ICLR register bit even if the corresponding IMASK bit is not enabled.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | PWRDWNIFG | PWRUPIFG | RXIFG | TXIFG | |||
| R-0h | R-0h | R-0h | R-0h | R-0h | |||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-4 | RESERVED | R | 0h | |
| 3 | PWRDWNIFG | R | 0h | Raw interrupt status for PWRDWNIFG
|
| 2 | PWRUPIFG | R | 0h | Raw interrupt status for PWRUPIFG
|
| 1 | RXIFG | R | 0h | Raw interrupt status for RXIFG
|
| 0 | TXIFG | R | 0h | Raw interrupt status for TXIFG
|
MIS is shown in Figure 33-5 and described in Table 33-19.
Return to the Summary Table.
Masked interrupt status. This is an AND of the IMASK and RIS registers.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | PWRDWNIFG | PWRUPIFG | RXIFG | TXIFG | |||
| R-0h | R-0h | R-0h | R-0h | R-0h | |||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-4 | RESERVED | R | 0h | |
| 3 | PWRDWNIFG | R | 0h | Masked interrupt status for PWRDWNIFG
|
| 2 | PWRUPIFG | R | 0h | Masked interrupt status for PWRUPIFG
|
| 1 | RXIFG | R | 0h | Masked interrupt status for RXIFG
|
| 0 | TXIFG | R | 0h | Masked interrupt status for TXIFG
|
ISET is shown in Figure 33-6 and described in Table 33-20.
Return to the Summary Table.
Interrupt set. Allows interrupts to be set by software (useful in diagnostics and safety checks). Writing a 1 to a bit in ISET will set the event and therefore the related RIS bit also gets set. If the interrupt is enabled through the mask, then the corresponding MIS bit is also set.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| W-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| W-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| W-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | PWRDWNIFG | PWRUPIFG | RXIFG | TXIFG | |||
| W-0h | W-0h | W-0h | W-0h | W-0h | |||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-4 | RESERVED | W | 0h | |
| 3 | PWRDWNIFG | W | 0h | Sets PWRDWNIFG in RIS register
|
| 2 | PWRUPIFG | W | 0h | Sets PWRUPIFG in RIS register
|
| 1 | RXIFG | W | 0h | Sets RXIFG in RIS register
|
| 0 | TXIFG | W | 0h | Sets TXIFG in RIS register
|
ICLR is shown in Figure 33-7 and described in Table 33-21.
Return to the Summary Table.
Interrupt clear. Write a 1 to clear corresponding Interrupt.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| W-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| W-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| W-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | PWRDWNIFG | PWRUPIFG | RXIFG | TXIFG | |||
| W-0h | W-0h | W-0h | W-0h | W-0h | |||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-4 | RESERVED | W | 0h | |
| 3 | PWRDWNIFG | W | 0h | Clears PWRDWNIFG in RIS register
|
| 2 | PWRUPIFG | W | 0h | Clears PWRUPIFG in RIS register
|
| 1 | RXIFG | W | 0h | Clears RXIFG in RIS register
|
| 0 | TXIFG | W | 0h | Clears TXIFG in RIS register
|
EVT_MODE is shown in Figure 33-8 and described in Table 33-22.
Return to the Summary Table.
Event mode register. It is used to select whether each line is disabled, in software mode (software clears the RIS) or in hardware mode (hardware clears the RIS)
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | INT0_CFG | ||||||
| R-0h | R-0h | ||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-2 | RESERVED | R | 0h | Reserved |
| 1-0 | INT0_CFG | R | 1h | Event line mode select for peripheral events
|
DESC is shown in Figure 33-9 and described in Table 33-23.
Return to the Summary Table.
This register identifies the peripheral and its exact version.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| MODULEID | |||||||||||||||
| R-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| FEATUREVER | INSTNUM | MAJREV | MINREV | ||||||||||||
| R-0h | R-0h | R-0h | R-0h | ||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | MODULEID | R | 340h | Module identification contains a unique peripheral identification number. The assignments are maintained in a central database for all of the platform modules to ensure uniqueness. |
| 15-12 | FEATUREVER | R | 0h | Feature Set for the module debug sub-system |
| 11-8 | INSTNUM | R | 0h | Instance Number within the device. This will be a parameter to the RTL for modules that can have multiple instances |
| 7-4 | MAJREV | R | 0h | Major rev of the IP |
| 3-0 | MINREV | R | 0h | Minor rev of the IP |
TXD is shown in Figure 33-10 and described in Table 33-24.
Return to the Summary Table.
This register is used for data transfers from external debug tools to the DSSM module. The register is written by the debug tool and read by the CPU.
| 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 |
| TX_DATA | |||||||||||||||||||||||||||||||
| R-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | TX_DATA | R | 0h | Contains data written by an external debug tool to the SEC-AP TXDATA register |
TXCTL is shown in Figure 33-11 and described in Table 33-25.
Return to the Summary Table.
Transmit control register
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| TRANSMIT_FLAGS | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| TRANSMIT_FLAGS | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| TRANSMIT_FLAGS | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| TRANSMIT_FLAGS | TRANSMIT | ||||||
| R-0h | R-0h | ||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-1 | TRANSMIT_FLAGS | R | 0h | Generic TX flags that can be set by external debug tool. Functionality is defined by SW. |
| 0 | TRANSMIT | R | 0h | Indicates data request in DSSM.TXD, set on write via Debug AP to DSSM.TXD. A read of the DSSM.TXD register by SW will clear the TX field. The tool can check that TXD is empty by reading this field.
|
RXD is shown in Figure 33-12 and described in Table 33-26.
Return to the Summary Table.
Receive data register. This register contains the data written by the CPU.
This data is read by external debug tool.
| 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 |
| RX_DATA | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | RX_DATA | R/W | 0h | Contains data written by CPU core to SEC-AP RX_DATA for an external debug tool access |
RXCTL is shown in Figure 33-13 and described in Table 33-27.
Return to the Summary Table.
Receive control register
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RECEIVE_FLAGS | RECEIVE | ||||||
| R/W-0h | R-0h | ||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7-1 | RECEIVE_FLAGS | R/W | 0h | Generic RX flags that can be set by SW and read by external debug tool. Functionality is defined by SW. |
| 0 | RECEIVE | R | 0h | Indicates SW write to the DSSM.RXD register. A read of the DSSM.RXD register by SWD Access Port will clear the RX field.
|
SPECIAL_AUTH is shown in Figure 33-14 and described in Table 33-28.
Return to the Summary Table.
This register is used to control ET-AP, DFT-TAP, SWJD, CFG-AP and SEC-AP.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | PWRAPEN | AHBAPEN | CFGAPEN | ETAPEN | DFTAPEN | SWJDPORTEN | SECAPEN |
| R-0h | R-0h | R-0h | R-1h | R-0h | R-0h | R-1h | R-1h |
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-7 | RESERVED | R | 0h | Reserved |
| 6 | PWRAPEN | R | 0h | An active high input. When asserted (and SWJD access is also permitted), the debug tools can then access the PWR-AP to power and reset state of the CPU. When deasserted, a DAPBUS firewall will isolate the AP and prevent access.
|
| 5 | AHBAPEN | R | 0h | Disabling / enabling debug access to the AM13 M33 Core via the AHB-AP DAP bus isolation.
|
| 4 | CFGAPEN | R | 1h | An active high input. When asserted (and SWJD access is also permitted), the debug tools can use the Config-AP to read device configuration information. When deasserted, a DAPBUS firewall will isolate the AP and prevent access to the Config-AP.
|
| 3 | ETAPEN | R | 0h | An active high input. When asserted (and SWJD access is also permitted), the debug tools can then access an ET-AP external to the DebugSS lite. When deasserted, a DAPBUS firewall will isolate the AP and prevent access.
|
| 2 | DFTAPEN | R | 0h | An active high input. When asserted (and SWJD access is also permitted), the debug tools can then access the DFT-AP external to the DebugSS . When deasserted, a DAPBUS firewall will isolate the AP and prevent access.
|
| 1 | SWJDPORTEN | R | 1h | When asserted, the SWJ-DP functions normally. When deasserted, the SWJ-DP effectively disables all external debug access.
|
| 0 | SECAPEN | R | 1h | An active high input. When asserted (and SWD access is also permitted), the debug tools can use the Security-AP to communicate with security control logic. When deasserted, a DAPBUS firewall will isolate the AP and prevent access to the Security-AP.
|
APP_AUTH is shown in Figure 33-15 and described in Table 33-29.
Return to the Summary Table.
This register is used to control DBGEN, NIDEN, SPIDEN, and SPNIDEN of Application CPU0.
DBGEN, NIDEN are further processed by DSW based on Active and Debug IPF ID.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| RESERVED | |||||||
| R-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||
| R-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | |||||||
| R-0h | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| RESERVED | SPNIDEN | SPIDEN | NIDEN | DBGEN | |||
| R-0h | R-0h | R-0h | R-0h | R-0h | |||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-4 | RESERVED | R | 0h | Reserved |
| 3 | SPNIDEN | R | 0h | Secure non-invasive debug enable.
|
| 2 | SPIDEN | R | 0h | Secure invasive debug enable.
|
| 1 | NIDEN | R | 0h | Controls non-invasive debug enable.
|
| 0 | DBGEN | R | 0h | Controls invasive debug enable.
|