SWRU626 December 2025 CC3501E , CC3551E
Table 5-22 lists the memory-mapped registers for the SOC_AON registers. All register offset addresses not listed in Table 5-22 should be considered as reserved locations and the register contents should not be modified.
| Offset | Acronym | Register Name | Section |
|---|---|---|---|
| Ch | SPEVTCTL | Peripheral Interrupt Control | Section 5.6.1 |
| 10h | TMEVTCTL | Timers Interrupt Control | Section 5.6.2 |
| 14h | GPT0EVTCTL0 | GPTIMER0 Interrupt Control 0 | Section 5.6.3 |
| 18h | GPT1EVTCTL0 | GPTIMER1 Interrupt Control | Section 5.6.4 |
| 54h | DMEMSTART | Data Ram Start Adress | Section 5.6.5 |
| 58h | DMEMEND | Data Ram End Adress | Section 5.6.6 |
| 64h | TCMSTART | TCM Data Ram Start Adress | Section 5.6.7 |
| 68h | TCMEND | TCM Data Ram End Adress | Section 5.6.8 |
| 7Ch | GPIOEVTS0 | GPIO Event Status 0 | Section 5.6.9 |
| 80h | GPIOEVTS1 | GPIO Event Status 1 | Section 5.6.10 |
| 84h | MEMSSCTL0 | MEMSS Control 0 | Section 5.6.11 |
| 88h | MEMSSCTL1 | MEMSS Control 1 | Section 5.6.12 |
| 9Ch | VTORS | VTOR Host Secure Address | Section 5.6.13 |
| A0h | VTORNS | VTOR Host Non-Secure Address | Section 5.6.14 |
| A8h | CPULOCKS | CPU Locks | Section 5.6.15 |
| ACh | HOSTLOCKS | Host Locks | Section 5.6.16 |
| B0h | HOSTBOOT | Host Boot Done | Section 5.6.17 |
| B4h | SECCFG | Security Configurations | Section 5.6.18 |
| D4h | ERRSIMASK | Error Host Secured Interrupt Mask | Section 5.6.19 |
| D8h | ERRSISET | Error Host Secured Interrupt Set | Section 5.6.20 |
| DCh | ERRSICLR | Error Host Secured Interrupt Clear | Section 5.6.21 |
| E0h | ERRSIMSET | Error Host Secured Masked Interrupt Set | Section 5.6.22 |
| E4h | ERRSIMCLR | Error Host Secured Masked Interrupt Clear | Section 5.6.23 |
| E8h | ERRSRIS | Error Host Secured Raw Interrupt Status | Section 5.6.24 |
| ECh | ERRSMIS | Doorbell Host Secured Masked Interrupt Status | Section 5.6.25 |
| F0h | GPT0EVTCTL1 | GPTIMER0 Interrupt Control 1 | Section 5.6.26 |
| F4h | GPT1EVTCTL1 | GPTIMER1 Interrupt Control 1 | Section 5.6.27 |
| 104h | ESMSTACST | ESM's Status | Section 5.6.28 |
| 10Ch | MEMSSCFG | MEMSS Configurations | Section 5.6.29 |
| 138h | GPIOMIS0S | GPIO's Masked Interrupt Status 0 | Section 5.6.30 |
| 13Ch | GPIOMIS1S | GPIO's Masked Interrupt Status 1 | Section 5.6.31 |
| 140h | GPIOFNC0S | GPIO's Interrupt Mask 0 | Section 5.6.32 |
| 144h | GPIOFNC1S | GPIO's Interrupt Mask 1 | Section 5.6.33 |
| 14Ch | ESM1VAL2ND | ESM1 Second Magic Value | Section 5.6.34 |
| 150h | ESM2VAL2ND | ESM2 Second Magic Value | Section 5.6.35 |
| 154h | ESM1STA2ND | ESM1 Second Magic Value Status | Section 5.6.36 |
| 158h | ESM2STA2ND | ESM2 Second Magic Value Status | Section 5.6.37 |
| 15Ch | FWCFGHOST | Host Firewall Bypass | Section 5.6.38 |
| 160h | FWCFGDMA | DMA Firewall Bypass | Section 5.6.39 |
| 164h | FWCFGFPRPH | Peripherals Firewall Bypass | Section 5.6.40 |
| 168h | FWCFGM33 | Cortex Firewall Bypass | Section 5.6.41 |
| 16Ch | FWCFGMEMSS | MEMSS Firewall Bypass | Section 5.6.42 |
| 170h | FWIOGENSEL | IOMUX Common Firewall Configuration | Section 5.6.43 |
| 174h | FWPRCMHOST | PRCM HOST Firewall Configuration | Section 5.6.44 |
| 178h | FWPRCMSPAD | PRCM Scratchpad Firewall Configuration | Section 5.6.45 |
| 17Ch | FWPRCMCMN | PRCM Common Firewall Configuration | Section 5.6.46 |
| 180h | FWCKM | Clock Manager Firewall Configuration | Section 5.6.47 |
| 184h | FWSOCIC | Interconnect Firewall Configuration | Section 5.6.48 |
| 188h | FWAONM33S | SOC AON Host Secure Aperture Firewall Configuration | Section 5.6.49 |
| 18Ch | FWAONM33NS | SOC AON Host Non-Secure Aperture Firewall Configuration | Section 5.6.50 |
| 190h | FWAAONM33S | SOC AAON Host Secure Aperture Firewall Configuration | Section 5.6.51 |
| 194h | FWAAONM33NS | SOC AAON Host Non-Secure Aperture Firewall Configuration | Section 5.6.52 |
| 198h | FWCMNRTC | RTC Firewall Configuration | Section 5.6.53 |
| 19Ch | FWMEMSS0 | MEMSS Region 0 Firewall Configuration | Section 5.6.54 |
| 1A0h | FWMEMSS1 | MEMSS Region 1 Firewall Configuration | Section 5.6.55 |
| 1A4h | FWMEMSS2 | MEMSS Region 2 Firewall Configuration | Section 5.6.56 |
| 1A8h | FWHOSTAON | HOST AON Target Firewall Configuration | Section 5.6.57 |
| 1B0h | FWHIF | HIF Firewall Configuration | Section 5.6.58 |
| 1B4h | FWHOST0 | HOST Target Region 0 Firewall Configuration | Section 5.6.59 |
| 1B8h | FWHOST1 | HOST Target Region 1 Firewall Configuration | Section 5.6.60 |
| 1BCh | FWHOST2 | HOST Target Region 2 Firewall Configuration | Section 5.6.61 |
| 1C0h | FWHOST3 | HOST Target Region 3 Firewall Configuration | Section 5.6.62 |
| 1C4h | FWHOST4 | HOST Target Region 4 Firewall Configuration | Section 5.6.63 |
| 1C8h | FWHOST5 | HOST Target Region 5 Firewall Configuration | Section 5.6.64 |
| 1CCh | FWHOST6 | HOST Target Region 6 Firewall Configuration | Section 5.6.65 |
| 1D0h | FWHOST7 | HOST Target Region 7 Firewall Configuration | Section 5.6.66 |
| 1D4h | FWHOST8 | HOST Target Region 8 Firewall Configuration | Section 5.6.67 |
| 1D8h | FWHOST9 | HOST Target Region 9 Firewall Configuration | Section 5.6.68 |
| 1DCh | FWHOST10 | HOST Target Region 10 Firewall Configuration | Section 5.6.69 |
| 1E0h | FWHOST11 | HOST Target Region 11 Firewall Configuration | Section 5.6.70 |
| 1E4h | FWXIPOSPI | xSPI Registers Firewall Configuration | Section 5.6.71 |
| 1E8h | FWXIPINDAC | xSPI Indac Firewall Configuration | Section 5.6.72 |
| 1ECh | FWXIPGEN | xSPI General Firewall Configuration | Section 5.6.73 |
| 1F0h | FWXIPUDMAS | xSPI uDMA Secured Firewall Configuration | Section 5.6.74 |
| 1F4h | FWXIPUDMANS | xSPI uDMA Non-Secured Firewall Configuration | Section 5.6.75 |
| 1F8h | FWOTFDE0 | xSPI OTFDE 0 Firewall Configuration | Section 5.6.76 |
| 1FCh | FWOTFDE1 | xSPI OTFDE 1 Firewall Configuration | Section 5.6.77 |
| 200h | FWOTFDE2 | xSPI OTFDE 2 Firewall Configuration | Section 5.6.78 |
| 204h | FWOTFDE3 | xSPI OTFDE 3 Firewall Configuration | Section 5.6.79 |
| 208h | FWDMAGEN | DMA Target Common Firewall Configuration | Section 5.6.80 |
| 20Ch | FWDMA0 | DMA Target Region 0 Firewall Configuration | Section 5.6.81 |
| 210h | FWDMA1 | DMA Target Region 1 Firewall Configuration | Section 5.6.82 |
| 214h | FWDMA2 | DMA Target Region 2 Firewall Configuration | Section 5.6.83 |
| 218h | FWDMA3 | DMA Target Region 3 Firewall Configuration | Section 5.6.84 |
| 21Ch | FWDMA4 | DMA Target Region 4 Firewall Configuration | Section 5.6.85 |
| 220h | FWDMA5 | DMA Target Region 5 Firewall Configuration | Section 5.6.86 |
| 224h | FWDMA6 | DMA Target Region 6 Firewall Configuration | Section 5.6.87 |
| 228h | FWDMA7 | DMA Target Region 7 Firewall Configuration | Section 5.6.88 |
| 22Ch | FWDMA8 | DMA Target Region 8 Firewall Configuration | Section 5.6.89 |
| 230h | FWDMA9 | DMA Target Region 9 Firewall Configuration | Section 5.6.90 |
| 234h | FWDMA10 | DMA Target Region 10 Firewall Configuration | Section 5.6.91 |
| 238h | FWDMA11 | DMA Target Region 11 Firewall Configuration | Section 5.6.92 |
| 23Ch | FWHSMEIPNS | HSM EIP Non-Secured Registers Firewall Configuration | Section 5.6.93 |
| 240h | FWHSMEIPS | HSM EIP Secured Registers Firewall Configuration | Section 5.6.94 |
| 244h | FWHSMWRAPNS | HSM Non-Secured Wrapper Firewall Configuration | Section 5.6.95 |
| 248h | FWHSMWRAPS | HSM Secured Wrapper Firewall Configuration | Section 5.6.96 |
| 24Ch | FWHSMDBG | HSM Debug Memory Firewall Configuration | Section 5.6.97 |
| 250h | FWI2C0 | I2C 0 Firewall Configuration | Section 5.6.98 |
| 254h | FWI2C1 | I2C 1 Firewall Configuration | Section 5.6.99 |
| 258h | FWSPSPI0 | SPI 0 Firewall Configuration | Section 5.6.100 |
| 25Ch | FWSPSPI1 | SPI 1 Firewall Configuration | Section 5.6.101 |
| 260h | FWSPUART0 | UART 0 Firewall Configuration | Section 5.6.102 |
| 264h | FWSPUART1 | UART 1 Firewall Configuration | Section 5.6.103 |
| 268h | FWSPGPT0 | GPTIMER0 Firewall Configuration | Section 5.6.104 |
| 26Ch | FWSPGPT1 | GPTIMER1 Firewall Configuration | Section 5.6.105 |
| 270h | FWSPI2S | I2S Firewall Configuration | Section 5.6.106 |
| 274h | FWPDM | PDM Firewall Configuration | Section 5.6.107 |
| 278h | FWSPCAN | DCAN Firewall Configuration | Section 5.6.108 |
| 27Ch | FWSPADC | ADC Firewall Configuration | Section 5.6.109 |
| 280h | FWSPSDMMC | SDMMC Firewall Configuration | Section 5.6.110 |
| 284h | FWSPSDIO | SDIO CARD Firewall Configuration | Section 5.6.111 |
| 288h | FWSPUART2 | UART 2 Firewall Configuration | Section 5.6.112 |
| 28Ch | UDMANSCTL | uDMA Non-Secured Channel Control | Section 5.6.113 |
| 290h | FWIOPAD0 | IOMUX PAD 0 Firewall Configuration | Section 5.6.114 |
| 294h | FWIOPAD1 | IOMUX PAD 1 Firewall Configuration | Section 5.6.115 |
| 298h | FWIOPAD2 | IOMUX PAD 2 Firewall Configuration | Section 5.6.116 |
| 29Ch | FWIOPAD3 | IOMUX PAD 3 Firewall Configuration | Section 5.6.117 |
| 2A0h | FWIOPAD4 | IOMUX PAD 4 Firewall Configuration | Section 5.6.118 |
| 2A4h | FWIOPAD5 | IOMUX PAD 5 Firewall Configuration | Section 5.6.119 |
| 2A8h | FWIOPAD6 | IOMUX PAD 6 Firewall Configuration | Section 5.6.120 |
| 2ACh | FWIOPAD7 | IOMUX PAD 7 Firewall Configuration | Section 5.6.121 |
| 2B0h | FWIOPAD8 | IOMUX PAD 8 Firewall Configuration | Section 5.6.122 |
| 2B4h | FWIOPAD9 | IOMUX PAD 9 Firewall Configuration | Section 5.6.123 |
| 2B8h | FWIOPAD10 | IOMUX PAD 10 Firewall Configuration | Section 5.6.124 |
| 2BCh | FWIOPAD11 | IOMUX PAD 11 Firewall Configuration | Section 5.6.125 |
| 2C0h | FWIOPAD12 | IOMUX PAD 12 Firewall Configuration | Section 5.6.126 |
| 2C4h | FWIOPAD13 | IOMUX PAD 13 Firewall Configuration | Section 5.6.127 |
| 2C8h | FWIOPAD14 | IOMUX PAD 14 Firewall Configuration | Section 5.6.128 |
| 2CCh | FWIOPAD15 | IOMUX PAD 15 Firewall Configuration | Section 5.6.129 |
| 2D0h | FWIOPAD16 | IOMUX PAD 16 Firewall Configuration | Section 5.6.130 |
| 2D4h | FWIOPAD17 | IOMUX PAD 17 Firewall Configuration | Section 5.6.131 |
| 2D8h | FWIOPAD18 | IOMUX PAD 18 Firewall Configuration | Section 5.6.132 |
| 2DCh | FWIOPAD19 | IOMUX PAD 19 Firewall Configuration | Section 5.6.133 |
| 2E0h | FWIOPAD20 | IOMUX PAD 20 Firewall Configuration | Section 5.6.134 |
| 2E4h | FWIOPAD21 | IOMUX PAD 21 Firewall Configuration | Section 5.6.135 |
| 2E8h | FWIOPAD22 | IOMUX PAD 22 Firewall Configuration | Section 5.6.136 |
| 2ECh | FWIOPAD23 | IOMUX PAD 23 Firewall Configuration | Section 5.6.137 |
| 2F0h | FWIOPAD24 | IOMUX PAD 24 Firewall Configuration | Section 5.6.138 |
| 2F4h | FWIOPAD25 | IOMUX PAD 25 Firewall Configuration | Section 5.6.139 |
| 2F8h | FWIOPAD26 | IOMUX PAD 26 Firewall Configuration | Section 5.6.140 |
| 2FCh | FWIOPAD27 | IOMUX PAD 27 Firewall Configuration | Section 5.6.141 |
| 300h | FWIOPAD28 | IOMUX PAD 28 Firewall Configuration | Section 5.6.142 |
| 304h | FWIOPAD29 | IOMUX PAD 29 Firewall Configuration | Section 5.6.143 |
| 308h | FWIOPAD30 | IOMUX PAD 30 Firewall Configuration | Section 5.6.144 |
| 30Ch | FWIOPAD31 | IOMUX PAD 31 Firewall Configuration | Section 5.6.145 |
| 310h | FWIOPAD32 | IOMUX PAD 32 Firewall Configuration | Section 5.6.146 |
| 314h | FWIOPAD33 | IOMUX PAD 33 Firewall Configuration | Section 5.6.147 |
| 318h | FWIOPAD34 | IOMUX PAD 34 Firewall Configuration | Section 5.6.148 |
| 31Ch | FWIOPAD35 | IOMUX PAD 35 Firewall Configuration | Section 5.6.149 |
| 320h | FWIOPAD36 | IOMUX PAD 36 Firewall Configuration | Section 5.6.150 |
| 324h | FWIOPAD37 | IOMUX PAD 37 Firewall Configuration | Section 5.6.151 |
| 328h | FWIOPAD38 | IOMUX PAD 38 Firewall Configuration | Section 5.6.152 |
| 32Ch | FWIOPAD39 | IOMUX PAD 39 Firewall Configuration | Section 5.6.153 |
| 330h | FWIOPAD40 | IOMUX PAD 40 Firewall Configuration | Section 5.6.154 |
| 334h | FWIOPAD41 | IOMUX PAD 41 Firewall Configuration | Section 5.6.155 |
| 338h | FWIOPAD42 | IOMUX PAD 42 Firewall Configuration | Section 5.6.156 |
| 33Ch | FWIOPAD43 | IOMUX PAD 43 Firewall Configuration | Section 5.6.157 |
| 340h | FWIOPAD44 | IOMUX PAD 44 Firewall Configuration | Section 5.6.158 |
| 344h | FWIOPAD45 | IOMUX PAD 45 Firewall Configuration | Section 5.6.159 |
| 348h | FWIOPAD46 | IOMUX PAD 46 Firewall Configuration | Section 5.6.160 |
| 34Ch | FWIOPAD47 | IOMUX PAD 47 Firewall Configuration | Section 5.6.161 |
| 350h | FWIOPAD48 | IOMUX PAD 48 Firewall Configuration | Section 5.6.162 |
| 354h | FWDMA12 | DMA Target Region 12 Firewall Configuration | Section 5.6.163 |
| 358h | FWDMA13 | DMA Target Region 13 Firewall Configuration | Section 5.6.164 |
| 1000h | USECSTB | Micro Second STB | Section 5.6.165 |
| 1044h | GPIOEVT0NS | GPIO Event Status 0 | Section 5.6.166 |
| 1048h | GPIOEVT1NS | GPIO Event Status 1 | Section 5.6.167 |
| 1054h | DBM33NS0 | Doorbell Host Non-Secured Interrupt Mask | Section 5.6.168 |
| 1058h | DBNSISET | Doorbell Host Non-Secured Interrupt Set | Section 5.6.169 |
| 105Ch | DBNSICLR | Doorbell Host Non-Secured Interrupt Clear | Section 5.6.170 |
| 1060h | DBNSIMSET | Doorbell Host Non-Secured Masked Interrupt Set | Section 5.6.171 |
| 1064h | DBNSIMCLR | Doorbell Host Non-Secured Masked Interrupt Clear | Section 5.6.172 |
| 1068h | DBNSRIS | Doorbell Host Non-Secured Raw Interrupt Status | Section 5.6.173 |
| 106Ch | DBNSMIS | Doorbell Host Non-Secured Masked Interrupt Status | Section 5.6.174 |
| 1070h | GPIOMIS0NS | GPIO's Non-Secured Masked Interrupt Status 0 | Section 5.6.175 |
| 1074h | GPIOMIS1NS | GPIO's Non-Secured Masked Interrupt Status 1 | Section 5.6.176 |
| 1078h | GPIOFNC0NS | GPIO's Non-Secured Function 0 | Section 5.6.177 |
| 107Ch | GPIOFNC1NS | GPIO's Non-Secured Function 1 | Section 5.6.178 |
Complex bit access types are encoded to fit into small table cells. Table 5-23 shows the codes that are used for access types in this section.
| Access Type | Code | Description |
|---|---|---|
| Read Type | ||
| R | R | Read |
| Write Type | ||
| W | W | Write |
| Reset or Default Value | ||
| -n | Value after reset or the default value | |
SPEVTCTL is shown in Table 5-24.
Return to the Summary Table.
Shared Peripherals Event MUXs Selectors. This register selects events to ADC, I2S and PDM.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-23 | RESERVED | R | 0h | Reserved |
| 22-16 | PDM | R/W | 0h | PDM Event Selector. This field selects event to PDM. |
| 15 | RESERVED | R | 0h | Reserved |
| 14-8 | I2S | R/W | 0h | I2S Event Selector. This field selects event to I2S. |
| 7-6 | RESERVED | R | 0h | Reserved |
| 5-0 | ADC | R/W | 0h | ADC Event Selector. This field selects event to ADC. |
TMEVTCTL is shown in Table 5-25.
Return to the Summary Table.
Timers Event MUXs Selectors. This register selects events to SYSTIMER and RTC. There are two MUXs of SYSTIMER and one for RTC.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-23 | RESERVED | R | 0h | Reserved |
| 22-16 | RTC | R/W | 0h | RTC Event Selector. This field selects event to RTC. |
| 15-14 | RESERVED | R | 0h | Reserved |
| 13-8 | SYSTM1 | R/W | 0h | SYSTIMER Event 2nd Selector. This field selects event to SYSTIMER. |
| 7-6 | RESERVED | R | 0h | Reserved |
| 5-0 | SYSTM0 | R/W | 0h | SYSTIMER Event 1st Selector. This field selects event to SYSTIMER. |
GPT0EVTCTL0 is shown in Table 5-26.
Return to the Summary Table.
GPTIMER0 Channels Event MUXs Selectors. This register selects events to GPTIMER0. There are 4 event MUXs for GPTIMER Channels.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-28 | RESERVED | R | 0h | Reserved |
| 27-21 | CH3SEL | R/W | 0h | This field selects MUX output to CH3 of GPTIMER0 IRQ. |
| 20-14 | CH2SEL | R/W | 0h | This field selects MUX output to CH2 of GPTIMER0 IRQ. |
| 13-7 | CH1SEL | R/W | 0h | This field selects MUX output to CH1 of GPTIMER0 IRQ. |
| 6-0 | CH0SEL | R/W | 0h | This field selects MUX output to CH0 of GPTIMER0 IRQ. |
GPT1EVTCTL0 is shown in Table 5-27.
Return to the Summary Table.
GPTIMER1 Event MUXs Selectors. This register selects events to GPTIMER1. There are 4 event MUXs for GPTIMER Channels.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-28 | RESERVED | R | 0h | Reserved |
| 27-21 | CH3SEL | R/W | 0h | This field selects MUX output to CH3 of GPTIMER1 IRQ. |
| 20-14 | CH2SEL | R/W | 0h | This field selects MUX output to CH2 of GPTIMER1 IRQ. |
| 13-7 | CH1SEL | R/W | 0h | This field selects MUX output to CH1 of GPTIMER1 IRQ. |
| 6-0 | CH0SEL | R/W | 0h | This field selects MUX output to CH0 of GPTIMER1 IRQ. |
DMEMSTART is shown in Table 5-28.
Return to the Summary Table.
DATA Memory MEMSS Start Address. DMEM Start Address-also define S/NS region split
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-12 | ADDR | R/W | 00028000h | DMEM Start Address-also define S/NS region split |
| 11-0 | RESERVED | R | 0h | Reserved |
DMEMEND is shown in Table 5-29.
Return to the Summary Table.
DATA Memory MEMSS End Address. DMEM end Address-also define S/NS region split
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-12 | ADDR | R/W | 0002FFFFh | DMEM end Address-also define S/NS region split |
| 11-0 | RESERVED | R | 0h | Reserved |
TCMSTART is shown in Table 5-30.
Return to the Summary Table.
TCM DATA Memory MEMSS Start Address. TCM data Start Address-also define S/NS region split
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-10 | ADDR | R/W | 00080000h | TCM data Start Address-also define S/NS region split |
| 9-0 | RESERVED | R | 0h | Reserved |
TCMEND is shown in Table 5-31.
Return to the Summary Table.
TCM DATA Memory MEMSS End Address. TCM data end Address-also define S/NS region split
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-10 | ADDR | R/W | 0009FFFFh | TCM data end Address-also define S/NS region split |
| 9-0 | RESERVED | R | 0h | Reserved |
GPIOEVTS0 is shown in Table 5-32.
Return to the Summary Table.
Secured GPIO Event Status, 1st Register. 45 bits status over two registers.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | STA31TO0 | R | 0h | Secured event status , first 32 bits. ([31:0]) |
GPIOEVTS1 is shown in Table 5-33.
Return to the Summary Table.
Secured GPIO Event Status, 2nd Register. 45 bits status over two registers.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-13 | RESERVED | R | 0h | Reserved |
| 12-0 | STA44TO32 | R | 0h | Secured event status , 13 MSBs. ([44:32]) |
MEMSSCTL0 is shown in Table 5-34.
Return to the Summary Table.
MEMSS General Control Register. This register controls starvation mechanism counter value and MEMSS bus fault mask.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-7 | RESERVED | R | 0h | Reserved |
| 6-4 | BFLTMSTA | R | 0h | Bus Fault Masked Status. Out of Memory Index: 0. No error 1. M33 Code 2. M33 Data #1 + #2 3. M3 Code 4. M3 Data 5. M3 PRAM 6. BLE Code 7. Global OCP |
| 3 | BFLTMASK | R/W | 0h | MEMSS Bus Fault Mask 1. Mask 0. Do not mask |
| 2-0 | STRVCNTV | R/W | 0h | Starvation Counter Value Configuration. That value reflect how long writing to mailbox can be delayed. |
MEMSSCTL1 is shown in Table 5-35.
Return to the Summary Table.
MEMSS General Control Register. This is a status register for bus fault raw status.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2-0 | BFLTRWSTA | R | 0h | Bus Fault Raw Status. Error indication from memss. Out of Memory Index: 0. No error 1. M33 Code 2. M33 Data #1 + #2 3. M3 Code 4. M3 Data 5. M3 PRAM 6. BLE Code 7. Global OCP Type: Read-Clear |
VTORS is shown in Table 5-36.
Return to the Summary Table.
M33 Secure Vector Table Base Address.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-7 | ADDR | R/W | 0h | init VTOR Secured Address. |
| 6-0 | RESERVED | R | 0h | Reserved |
VTORNS is shown in Table 5-37.
Return to the Summary Table.
M33 Non-Secure Vector Table Base Address.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-7 | ADDR | R/W | 0h | init VTOR non Secured address |
| 6-0 | RESERVED | R | 0h | Reserved |
CPULOCKS is shown in Table 5-38.
Return to the Summary Table.
CPU Locks. This register contain 5 locks. Issued to M33 Cortex and used to lock internal cortex registers. LOCKSVTAIRCR, LOCKNSVTOR, LOCKSMPU, LOCKNSMPU, LOCKSAU.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-5 | RESERVED | R | 0h | Reserved |
| 4 | SAU | R/W | 0h | Locking this Cortex internal configuration |
| 3 | NSPMU | R/W | 0h | Locking this Cortex internal configuration |
| 2 | SMPU | R/W | 0h | Locking this Cortex internal configuration |
| 1 | NSVTOR | R/W | 0h | Locking this Cortex internal configuration |
| 0 | SVTAIRCR | R/W | 0h | Locking this Cortex internal configuration |
HOSTLOCKS is shown in Table 5-39.
Return to the Summary Table.
Host Lock Signals. lock once. Do Not lock until written. When written Locked immediately, cleared only at soc aon reset or por reset. These are host security lock configurations (some can be also locked by TI)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-7 | RESERVED | R | 0h | Reserved |
| 6 | PERIPHEVT | R/W | 0h | Locking the firewall configurations of: HIF, CORE, CORE AON, HSM, shared Periphs |
| 5 | M3EVT | R/W | 0h | Locking the configurations of M3 Events |
| 4 | FLASH | R/W | 0h | Locking the configurations of On The Fly Enc/Decryption Module Region Related Registers (four registers per region, four regions) |
| 3 | DMA | R/W | 0h | Locking the configurations of System DMA |
| 2 | MEMSSANDFW | R/W | 0h | Locking the configurations of Memory Sub System |
| 1 | M33 | R/W | 0h | Locking the configurations of Host MCU, both Secured and non Secured |
| 0 | CACHE | R/W | 0h | Locking the configurations of ICACHE |
HOSTBOOT is shown in Table 5-40.
Return to the Summary Table.
Host Boot Done 1 lock. Write once. Asserted by FW by the end of soc boot done Or in elevated mode By either by TI of by the host and indicates device exit from secure boot mode. this signal also locks host security configurations , Locked immediately , cleared only at soc aon reset or por reset
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-1 | RESERVED | R | 0h | Reserved |
| 0 | DONE | R/W | 0h | Locking host security configurations |
SECCFG is shown in Table 5-41.
Return to the Summary Table.
Security Configurations.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | BLKSBSWR | R/W | 0h | BLOCK SBUS WRITE LOCK Enable this field to block sbus write transactions |
| 1 | SELNSIRQ | R/W | 0h | This field determine whether the 4 SW interrupts MSbits will be owned by secured/non secured. 0. Non-Secured 1. Secured |
| 0 | BLKDMA | R/W | 0h | This Field blocks the uDMA transactions to CMEM. 0. un-Block 1. Block |
ERRSIMASK is shown in Table 5-42.
Return to the Summary Table.
M33 Secured Error IMASK. Mask Event. '0' - CLR - Clear Interrupt Mask '1' - SET - Set Interrupt Mask
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-9 | RESERVED | R | 0h | Reserved |
| 8-0 | IMASK | R/W | 0h | Bits division to events: bit[8] - UDMA ERR IRQ bit[7] - CORE ELP WATCHDOG Timer bit[6] - SOC IC IRQs - Address Watch bit[5] - SOC IC IRQs - IC Timeout bit[4] - SOC IC IRQs - serror bit[3] - CORE to SDIO WATCHDOG bit[2] - PLL Unlock bit[1] - MEMss bus fault bit[0] - HSM fatal error |
ERRSISET is shown in Table 5-43.
Return to the Summary Table.
M33 Secured Error ISET. Sets event in RIS Write 0 - NO_EFFECT - Writing 0 has no effect Write 1 - SET - Sets interrupt
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-9 | RESERVED | R | 0h | Reserved |
| 8-0 | ISET | W | 0h | Bits division to events: bit[8] - UDMA ERR IRQ bit[7] - CORE ELP WATCHDOG Timer bit[6] - SOC IC IRQs - Address Watch bit[5] - SOC IC IRQs - IC Timeout bit[4] - SOC IC IRQs - serror bit[3] - CORE to SDIO WATCHDOG bit[2] - PLL Unlock bit[1] - MEMss bus fault bit[0] - HSM fatal error Type: Write-Clear |
ERRSICLR is shown in Table 5-44.
Return to the Summary Table.
M33 Secured Error ICLR. Clears event in RIS Write 0 - NO_EFFECT - Writing 0 has no effect Write 1 - CLR - Clears the Event
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-9 | RESERVED | R | 0h | Reserved |
| 8-0 | ICLR | W | 0h | Bits division to events: bit[8] - UDMA ERR IRQ bit[7] - CORE ELP WATCHDOG Timer bit[6] - SOC IC IRQs - Address Watch bit[5] - SOC IC IRQs - IC Timeout bit[4] - SOC IC IRQs - serror bit[3] - CORE to SDIO WATCHDOG bit[2] - PLL Unlock bit[1] - MEMss bus fault bit[0] - HSM fatal error Type: Write-Clear |
ERRSIMSET is shown in Table 5-45.
Return to the Summary Table.
M33 Secured Error IMSET. Sets Event Write 0 - NO_EFFECT - Writing 0 has no effect Write 1 - SET - Set interrupt mask
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-9 | RESERVED | R | 0h | Reserved |
| 8-0 | IMSET | W | 0h | Bits division to events: bit[8] - UDMA ERR IRQ bit[7] - CORE ELP WATCHDOG Timer bit[6] - SOC IC IRQs - Address Watch bit[5] - SOC IC IRQs - IC Timeout bit[4] - SOC IC IRQs - serror bit[3] - CORE to SDIO WATCHDOG bit[2] - PLL Unlock bit[1] - MEMss bus fault bit[0] - HSM fatal error Type: Write-Clear |
ERRSIMCLR is shown in Table 5-46.
Return to the Summary Table.
M33 Secured Error IMCLR. Clears Event Write 0 - NO_EFFECT - Writing 0 has no effect Write 1 - CLR - Clear interrupt mask
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-9 | RESERVED | R | 0h | Reserved |
| 8-0 | IMCLR | W | 0h | Bits division to events: bit[8] - UDMA ERR IRQ bit[7] - CORE ELP WATCHDOG Timer bit[6] - SOC IC IRQs - Address Watch bit[5] - SOC IC IRQs - IC Timeout bit[4] - SOC IC IRQs - serror bit[3] - CORE to SDIO WATCHDOG bit[2] - PLL Unlock bit[1] - MEMss bus fault bit[0] - HSM fatal error Type: Write-Clear |
ERRSRIS is shown in Table 5-47.
Return to the Summary Table.
M33 Secured Error RIS. Raw interrupt status for event. This bit is set to 1 when an event is received. when the corresponding bit in ICLR is set to 1, this bit will be cleared. Read 0 - CLR - Interrupt did not occur Read 1 - SET - Interrupt occurred
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-9 | RESERVED | R | 0h | Reserved |
| 8-0 | RIS | R | 0h | Bits division to events: bit[8] - UDMA ERR IRQ bit[7] - CORE ELP WATCHDOG Timer bit[6] - SOC IC IRQs - Address Watch bit[5] - SOC IC IRQs - IC Timeout bit[4] - SOC IC IRQs - serror bit[3] - CORE to SDIO WATCHDOG bit[2] - PLL Unlock bit[1] - MEMss bus fault bit[0] - HSM fatal error |
ERRSMIS is shown in Table 5-48.
Return to the Summary Table.
M33 Secured Error MIS. Mask interrupt status for event Read 0 - CLR - Interrupt did not occur Read 1 - SET - Interrupt occurred
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-9 | RESERVED | R | 0h | Reserved |
| 8-0 | MIS | R | 0h | Bits division to events: bit[8] - UDMA ERR IRQ bit[7] - CORE ELP WATCHDOG Timer bit[6] - SOC IC IRQs - Address Watch bit[5] - SOC IC IRQs - IC Timeout bit[4] - SOC IC IRQs - serror bit[3] - CORE to SDIO WATCHDOG bit[2] - PLL Unlock bit[1] - MEMss bus fault bit[0] - HSM fatal error |
GPT0EVTCTL1 is shown in Table 5-49.
Return to the Summary Table.
GPTIMER0 Sync, Tick Enable and Fault Event MUXs Selectors. This register selects events to GPTIMER0.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-23 | RESERVED | R | 0h | Reserved |
| 22-16 | FAULT | R/W | 0h | Selects fault MUX output to GPTIMER0 IRQ |
| 15 | RESERVED | R | 0h | Reserved |
| 14-8 | TICKEN | R/W | 0h | Selects tick enable MUX output to GPTIMER0 IRQ |
| 7 | RESERVED | R | 0h | Reserved |
| 6-0 | SYNC | R/W | 0h | Selects sync MUX output to GPTIMER0 IRQ |
GPT1EVTCTL1 is shown in Table 5-50.
Return to the Summary Table.
GPTIMER1 Sync, Tick Enable and Fault Event MUXs Selectors. This register selects events to GPTIMER1.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-23 | RESERVED | R | 0h | Reserved |
| 22-16 | FAULT | R/W | 0h | Selects fault MUX output to GPTIMER0 IRQ |
| 15 | RESERVED | R | 0h | Reserved |
| 14-8 | TICKEN | R/W | 0h | Selects tick enable MUX output to GPTIMER0 IRQ |
| 7 | RESERVED | R | 0h | Reserved |
| 6-0 | SYNC | R/W | 0h | Selects sync MUX output to GPTIMER0 IRQ |
ESMSTACST is shown in Table 5-51.
Return to the Summary Table.
Customer ESMs Status. status register , for each of the ESM (enable sequence monitor) what is the status (Done, violated, or None) Final ESM status for the entire ESM - ESM machine + magic value comparators
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-10 | RESERVED | R | 0h | Reserved |
| 9 | ESM2VIO | R | 0h | This field indicates that ESM1 is violated. |
| 8 | ESM2DONE | R | 0h | This field indicates that ESM2 is done. |
| 7-2 | RESERVED | R | 0h | Reserved |
| 1 | ESM1VIO | R | 0h | This field indicates that ESM1 is violated. |
| 0 | ESM1DONE | R | 0h | This field indicates that ESM1 is done. |
MEMSSCFG is shown in Table 5-52.
Return to the Summary Table.
MEMSS Configurations. Supported Memory configurations: Functional Modes: 0x0. Baseline 0x1. Extended M3 0x2. Extended throughput 0x3. Extended throughput + WIFI features 0x4. Extended Host Execution 0x5. Extended M33 Data Debug Modes (OCLA Memory): 0x6. Core debug (<M33 Data) 0x7. Core debug Extended throughput (<M33 Data <M3 Exec) 0x8. Core debug PHY only (<M3,M33 Data) 0x9. Host debug (<M3 Exec) 0xA. Host debug extended Host Execution 0xB. Host debug extended M33 Data
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-4 | RESERVED | R | 0h | Reserved |
| 3-0 | MODE | R/W | 0h | MEMSS mode of bank ownership |
GPIOMIS0S is shown in Table 5-53.
Return to the Summary Table.
Secured Gpio MIS.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | 31TO0 | R | 0h | 32 LSBs of MIS. (45 Total) |
GPIOMIS1S is shown in Table 5-54.
Return to the Summary Table.
Secured Gpio MIS.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-13 | RESERVED | R | 0h | Reserved |
| 12-0 | 44TO32 | R | 0h | 13 MSBs of MIS. (45 Total) |
GPIOFNC0S is shown in Table 5-55.
Return to the Summary Table.
Secured GPIO Functional Mask. 0. Mask 1. Un-Mask
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | MASK31TO0 | R/W | 0h | 32 LSBs of MASK. (45 Total) |
GPIOFNC1S is shown in Table 5-56.
Return to the Summary Table.
Secured GPIO Functional Mask. 0. Mask 1. Un-Mask
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-13 | RESERVED | R | 0h | Reserved |
| 12-0 | MASK44TO32 | R/W | 0h | 13 MSBs of MASK. (45 Total) |
ESM1VAL2ND is shown in Table 5-57.
Return to the Summary Table.
ESM1 2nd Magic Value. This value is compared to hard coded value and unmask ESM only when value is matched. This additional compare allow additional protection on ESM and also allow vendor to unmask ESM only at the end of vendor secure boot (SBL) is completed
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7-0 | MGCVAL | R/W | 0h | ESM 2nd magic value |
ESM2VAL2ND is shown in Table 5-58.
Return to the Summary Table.
ESM2 2nd Magic Value. This value is compared to hard coded value and unmask ESM only when value is matched. This additional compare allow additional protection on ESM and also allow vendor to unmask ESM only at the end of vendor secure boot (SBL) is completed
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-8 | RESERVED | R | 0h | Reserved |
| 7-0 | MGCVAL | R/W | 0h | ESM 2nd magic value |
ESM1STA2ND is shown in Table 5-59.
Return to the Summary Table.
ESM1 2nd Magic Value Status. ESM magic value match indication.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-2 | RESERVED | R | 0h | Reserved |
| 1 | FAULT | R | 0h | ESM 2nd magic val fault ( note: indicates fault before a write to the magic val register) |
| 0 | DONE | R | 0h | ESM 2nd magic val match |
ESM2STA2ND is shown in Table 5-60.
Return to the Summary Table.
ESM2 2nd Magic Value. ESM magic value match indication.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-2 | RESERVED | R | 0h | Reserved |
| 1 | FAULT | R | 0h | ESM 2nd magic val fault ( note: indicates fault before a write to the magic val register) |
| 0 | DONE | R | 0h | ESM 2nd magic val match |
FWCFGHOST is shown in Table 5-61.
Return to the Summary Table.
HOST FW Bypass.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-1 | RESERVED | R | 0h | Reserved |
| 0 | BYPASS | R/W | 1h | bypass the following module's firewall configuration: IOMUX_COMMON_SEL PRCM_AON_HOST PRCM_AON_COMMON SCRATCHPAD PLLSHARING SOC_IC SOC_AON_M33_S SOC_AON_M33_NS SOC_AAON_M33_S SOC_AAON_M33_NS RTC XIP_OSPI XIP_OSPI_INDAC XIP_GENERAL XIP_UDMA_SEC XIP_UDMA_NON_SEC OTFDE_REGION0-3 HOST_DMA_GENERAL_CFG |
FWCFGDMA is shown in Table 5-62.
Return to the Summary Table.
DMA FW BYPASS
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-1 | RESERVED | R | 0h | Reserved |
| 0 | BYPASS | R/W | 1h | Bypass the firewall configuration for HOST_DMA module |
FWCFGFPRPH is shown in Table 5-63.
Return to the Summary Table.
Peripheral Firewall Bypass.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-1 | RESERVED | R | 0h | Reserved |
| 0 | BYPASS | R/W | 1h | bypass the following module's firewall configuration: HIF HSM CORE_AON I2C0/1 SPI0/1 UART0/1 GPTIMER0/1 I2S PDM CAN ADC SDMMC SDIO |
FWCFGM33 is shown in Table 5-64.
Return to the Summary Table.
HOST MCU Firewall Bypass
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-1 | RESERVED | R | 0h | Reserved |
| 0 | BYPASS | R/W | 1h | bypass the firewall configuration for HOST MCU module. |
FWCFGMEMSS is shown in Table 5-65.
Return to the Summary Table.
MEMSS Firewall Bypass
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-1 | RESERVED | R | 0h | Reserved |
| 0 | BYPASS | R/W | 1h | bypass the Firewall configuration for MEMSS module. |
FWIOGENSEL is shown in Table 5-66.
Return to the Summary Table.
IOMUX General firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWPRCMHOST is shown in Table 5-67.
Return to the Summary Table.
PRCM_HOST firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
| 1 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
FWPRCMSPAD is shown in Table 5-68.
Return to the Summary Table.
M33 SCRATCHPAD firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWPRCMCMN is shown in Table 5-69.
Return to the Summary Table.
PRCM_COMMON firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-6 | RESERVED | R | 0h | Reserved |
| 5 | CORENSRD | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 4 | CORENSWR | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 3 | M33NSRD | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
| 2 | M33NSWR | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33SRD | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33SWR | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
FWCKM is shown in Table 5-70.
Return to the Summary Table.
CKM firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWSOCIC is shown in Table 5-71.
Return to the Summary Table.
SOC_IC firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-6 | RESERVED | R | 0h | Reserved |
| 5 | CORENSRD | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 4 | CORENSWR | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 3 | M33SRD | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 2 | M33SWR | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33NSRD | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NSWR | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWAONM33S is shown in Table 5-72.
Return to the Summary Table.
AON_M33_S firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWAONM33NS is shown in Table 5-73.
Return to the Summary Table.
AON_M33_NS firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWAAONM33S is shown in Table 5-74.
Return to the Summary Table.
AAON_M33_S firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWAAONM33NS is shown in Table 5-75.
Return to the Summary Table.
AAON_M33_NS firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWCMNRTC is shown in Table 5-76.
Return to the Summary Table.
RTC firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-6 | RESERVED | R | 0h | Reserved |
| 5 | CORENSRD | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 4 | CORENSWR | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 3 | M33SRD | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 2 | M33SWR | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33NSRD | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NSWR | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWMEMSS0 is shown in Table 5-77.
Return to the Summary Table.
MEMSS region 0 firewall access permission for 3 controller id : 0 - M33 Non Secured (valid only in privilege mode) 1 - M33 Secured (valid only in privilege mode) 2 - Core (Non Secure) MEMSS address space: 0x41C00000 - 0x41CCFFFF for Memss the base address for security firewalls is 0x41c40000 ( M33 Data Ram from global port access) max window size is 256Kb (M33D banks) + 10*32K (Flex) = 576Kb
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-26 | RESERVED | R | 0h | Reserved |
| 25-16 | LEN | R/W | 0h | address base with 1K granularity : address base len for firewall is the offset from the region's base address indicated in the same region field describing the end of a firewall window that has a certain access rules (R/W Permission) for each controller-id MEMSS address space: 0x41C00000 - 0x41CCFFFF for Memss the base address for security firewalls is 0x41c40000 ( M33 Data Ram from global port access) max window size is 576Kb example: worker base address: 0x41C40000 current address to access: 0x41C41514 region_base_address: 0x4 region_base_address_len: 0x2 --> (region_base_address + region_base_address_len) --> 0x4+0x2 -->0x6 0x41C41514 --> ((0x41C41514 - 0x41C40000) >> 10) -->0x5 0x4 <= 0x5 < 0x6 that address falls on the region window and therefor obeys to that region set of access rules |
| 15-14 | RESERVED | R | 0h | Reserved |
| 13-4 | BASE | R/W | 0h | address base with 1K granularity : address base for firewall is the the offset start address from a worker base address describing the beginning of a firewall window that has a certain access rules (R/W Permission) for each controller-id MEMSS address space: 0x41C00000 - 0x41CCFFFF for Memss the base address for security firewalls is 0x41c40000 ( M33 Data Ram from global port access) max base value is 0x23F max window size is 576Kb example: worker base address: 0x41C40000 current address to access: 0x41C40504 region_base_address: 0x1 region_base_address_len: 0x1 0x41C40504 --> ((0x41C40504 - 0x41C40000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: (valid only in privilege mode) '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: (valid only in privilege mode) '0' - access not allowed '1' - access allowed |
FWMEMSS1 is shown in Table 5-78.
Return to the Summary Table.
MEMSS region 1 firewall access permission for 3 controller id : 0 - M33 Non Secured (valid only in privilege mode) 1 - M33 Secured (valid only in privilege mode) 2 - Core (Non Secure) MEMSS address space: 0x41C00000 - 0x41CCFFFF for Memss the base address for security firewalls is 0x41c40000 ( M33 Data Ram from global port access) max window size is 256Kb (M33D banks) + 10*32K (Flex) = 576Kb
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-26 | RESERVED | R | 0h | Reserved |
| 25-16 | LEN | R/W | 0h | address base with 1K granularity : address base len for firewall is the offset from the region's base address indicated in the same region field describing the end of a firewall window that has a certain access rules (R/W Permission) for each controller-id MEMSS address space: 0x41C00000 - 0x41CCFFFF for Memss the base address for security firewalls is 0x41c40000 ( M33 Data Ram from global port access) max window size is 576Kb example: worker base address: 0x41C40000 current address to access: 0x41C41514 region_base_address: 0x4 region_base_address_len: 0x2 --> (region_base_address + region_base_address_len) --> 0x4+0x2 -->0x6 0x41C41514 --> ((0x41C41514 - 0x41C40000) >> 10) -->0x5 0x4 <= 0x5 < 0x6 that address falls on the region window and therefor obeys to that region set of access rules |
| 15-14 | RESERVED | R | 0h | Reserved |
| 13-4 | BASE | R/W | 0h | address base with 1K granularity : address base for firewall is the the offset start address from a worker base address describing the beginning of a firewall window that has a certain access rules (R/W Permission) for each controller-id MEMSS address space: 0x41C00000 - 0x41DFFFFF for Memss the base address for security firewalls is 0x41c40000 ( M33 Data Ram from global port access) max base value is 0x23F max window size is 576Kb example: worker base address: 0x41C40000 current address to access: 0x41C40504 region_base_address: 0x1 region_base_address_len: 0x1 0x41C40504 --> ((0x41C40504 - 0x41C40000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: (valid only in privilege mode) '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: (valid only in privilege mode) '0' - access not allowed '1' - access allowed |
FWMEMSS2 is shown in Table 5-79.
Return to the Summary Table.
MEMSS region 2 firewall access permission for 3 controller id : 0 - M33 Non Secured (valid only in privilege mode) 1 - M33 Secured (valid only in privilege mode) 2 - Core (Non Secure) MEMSS address space: 0x41C00000 - 0x41CCFFFF for Memss the base address for security firewalls is 0x41c40000 ( M33 Data Ram from global port access) max window size is 256Kb (M33D banks) + 10*32K (Flex) = 576Kb
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-26 | RESERVED | R | 0h | Reserved |
| 25-16 | LEN | R/W | 0h | address base with 1K granularity : address base len for firewall is the offset from the region's base address indicated in the same region field describing the end of a firewall window that has a certain access rules (R/W Permission) for each controller-id MEMSS address space: 0x41C00000 - 0x41CCFFFF for Memss the base address for security firewalls is 0x41c40000 ( M33 Data Ram from global port access) max window size is 576Kb example: worker base address: 0x41C40000 current address to access: 0x41C41514 region_base_address: 0x4 region_base_address_len: 0x2 --> (region_base_address + region_base_address_len) --> 0x4+0x2 -->0x6 0x41C41514 --> ((0x41C41514 - 0x41C40000) >> 10) -->0x5 0x4 <= 0x5 < 0x6 that address falls on the region window and therefor obeys to that region set of access rules |
| 15-14 | RESERVED | R | 0h | Reserved |
| 13-4 | BASE | R/W | 0h | address base with 1K granularity : address base for firewall is the the offset start address from a worker base address describing the beginning of a firewall window that has a certain access rules (R/W Permission) for each controller-id MEMSS address space: 0x41C00000 - 0x41DFFFFF for Memss the base address for security firewalls is 0x41c40000 ( M33 Data Ram from global port access) max base value is 0x23F max window size is 576Kb example: worker base address: 0x41C40000 current address to access: 0x41C40504 region_base_address: 0x1 region_base_address_len: 0x1 0x41C40504 --> ((0x41C40504 - 0x41C40000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: (valid only in privilege mode) '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 non Secured: (valid only in privilege mode) '0' - access not allowed '1' - access allowed |
FWHOSTAON is shown in Table 5-80.
Return to the Summary Table.
HOST_AON_SLV firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHIF is shown in Table 5-81.
Return to the Summary Table.
HIF firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure) - Not in use , core always has access.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHOST0 is shown in Table 5-82.
Return to the Summary Table.
HOST MCU region 0 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-26 | RESERVED | R | 0h | Reserved |
| 25-16 | LEN | R/W | 0h | address base with 1K granularity : address base len for firewall is the offset from the region's base address indicated in the same region field describing the end of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU_REGION_0 address space: 0x20000000 - 0x2FFFFFFF HOST_MCU_REGION_0 base_len can range from: ##register base_len value## 0x0 - 0x7F for HOST_MCU_REGION_0 the base address for security firewalls is 0x23F80000 ( HOST_MCU_REGION_0 ) max window size is 128Kb example: worker base address: 0x23F80000 current address to access: 0x23F81504 region_base_address: 0x4 region_base_address_len: 0x2 --> (region_base_address + region_base_address_len) --> 0x4+0x2 -->0x6 0x23F81504 --> ((0x23F81504 - 0x23F80000) >> 10) -->0x4 0x4 <= 0x5 < 0x6 that address falls on the region window and therefor obeys to that region set of access rules |
| 15 | RESERVED | R | 0h | Reserved |
| 14-4 | BASE | R/W | 0h | address base with 1K granularity : address base for firewall is the the offset start address from a worker base address describing the beginning of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU address space: 0x00000000 - 0x2FFFFFFF / 0x41900000 - 0x4190FFFF HOST_MCU_REGION_0 is assigned to TCM DATA RAM HOST_MCU_REGION_0 base address can range from: ##register base value## 0x0 - 0x27F ##absolute equivalent value## 0x23F800000 - 0x2401FC00 for HOST_MCU_REGION_0 the base address for security firewalls is 0x23F80000 ( M33 TCM Data RAM ) max window size is 128Kb example: worker base address: 0x23F80000 current address to access: 0x23F80504 region_base_address: 0x1 region_base_address_len: 0x1 0x23F80504 --> ((0x23F80504 - 0x23F800000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHOST1 is shown in Table 5-83.
Return to the Summary Table.
HOST MCU region 1 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-26 | RESERVED | R | 0h | Reserved |
| 25-16 | LEN | R/W | 0h | address base with 1K granularity : address base len for firewall is the offset from the region's base address indicated in the same region field describing the end of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU_REGION_0 address space: 0x20000000 - 0x2FFFFFFF HOST_MCU_REGION_0 base_len can range from: ##register base_len value## 0x0 - 0x7F for HOST_MCU_REGION_0 the base address for security firewalls is 0x23F80000 ( HOST_MCU_REGION_1 ) max window size is 128Kb example: worker base address: 0x23F80000 current address to access: 0x23F81504 region_base_address: 0x4 region_base_address_len: 0x2 --> (region_base_address + region_base_address_len) --> 0x4+0x2 -->0x6 0x23F81504 --> ((0x23F81504 - 0x23F80000) >> 10) -->0x4 0x4 <= 0x5 < 0x6 that address falls on the region window and therefor obeys to that region set of access rules |
| 15 | RESERVED | R | 0h | Reserved |
| 14-4 | BASE | R/W | 0h | address base with 1K granularity : address base for firewall is the the offset start address from a worker base address describing the beginning of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU address space: 0x00000000 - 0x2FFFFFFF / 0x41900000 - 0x4190FFFF HOST_MCU_REGION_1 is assigned to TCM DATA RAM HOST_MCU_REGION_1 base address can range from: ##register base value## 0x0 - 0x27F ##absolute equivalent value## 0x23F800000 - 0x2401FC00 for HOST_MCU_REGION_0 the base address for security firewalls is 0x23F80000 ( M33 TCM Data RAM ) max window size is 128Kb example: worker base address: 0x23F80000 current address to access: 0x23F80504 region_base_address: 0x1 region_base_address_len: 0x1 0x23F80504 --> ((0x23F80504 - 0x23F800000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHOST2 is shown in Table 5-84.
Return to the Summary Table.
HOST MCU region 2 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-26 | RESERVED | R | 0h | Reserved |
| 25-16 | LEN | R/W | 0h | address base with 1K granularity : address base len for firewall is the offset from the region's base address indicated in the same region field describing the end of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU_REGION_2 address space: 0x20000000 - 0x2FFFFFFF HOST_MCU_REGION_2 base_len can range from: ##register base_len value## 0x0 - 0x240 for HOST_MCU_REGION_0 the base address for security firewalls is 0x2BF00000 ( HOST_MCU_REGION_2 ) max window size is 576Kb example: worker base address: 0x2BF00000 current address to access: 0x2BF01504 region_base_address: 0x4 region_base_address_len: 0x2 --> (region_base_address + region_base_address_len) --> 0x4+0x2 -->0x6 0x2BF01504 --> ((0x2BF01504 - 0x2BF00000) >> 10) -->0x4 0x4 <= 0x5 < 0x6 that address falls on the region window and therefor obeys to that region set of access rules |
| 15 | RESERVED | R | 0h | Reserved |
| 14-4 | BASE | R/W | 0h | address base with 1K granularity : address base for firewall is the the offset start address from a worker base address describing the beginning of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU address space: 0x00000000 - 0x2FFFFFFF / 0x41900000 - 0x4190FFFF HOST_MCU_REGION_2 is assigned to M33 DATA RAM HOST_MCU_REGION_2 base address can range from: ##register base value## 0x0 - 0x63F ##absolute equivalent value## 0x2BF00000 - 0x2C08FC00 for HOST_MCU_REGION_2 the base address for security firewalls is 0x2BF00000 ( M33 Data RAM ) max window size is 576Kb (depending on the MEMSS mode) example: worker base address: 0x2BF000000 current address to access: 0x2BF00504 region_base_address: 0x1 region_base_address_len: 0x1 0x2BF00504 --> ((0x2BF00504 - 0x2BF000000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHOST3 is shown in Table 5-85.
Return to the Summary Table.
HOST MCU region 3 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-26 | RESERVED | R | 0h | Reserved |
| 25-16 | LEN | R/W | 0h | address base with 1K granularity : address base len for firewall is the offset from the region's base address indicated in the same region field describing the end of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU_REGION_2 address space: 0x20000000 - 0x2FFFFFFF HOST_MCU_REGION_2 base_len can range from: ##register base_len value## 0x0 - 0x240 for HOST_MCU_REGION_0 the base address for security firewalls is 0x2BF00000 ( HOST_MCU_REGION_2 ) max window size is 576Kb example: worker base address: 0x2BF00000 current address to access: 0x2BF01504 region_base_address: 0x4 region_base_address_len: 0x2 --> (region_base_address + region_base_address_len) --> 0x4+0x2 -->0x6 0x2BF01504 --> ((0x2BF01504 - 0x2BF00000) >> 10) -->0x4 0x4 <= 0x5 < 0x6 that address falls on the region window and therefor obeys to that region set of access rules |
| 15 | RESERVED | R | 0h | Reserved |
| 14-4 | BASE | R/W | 0h | address base with 1K granularity : address base for firewall is the the offset start address from a worker base address describing the beginning of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU address space: 0x00000000 - 0x2FFFFFFF / 0x41900000 - 0x4190FFFF HOST_MCU_REGION_3 is assigned to M33 DATA RAM HOST_MCU_REGION_3 base address can range from: ##register base value## 0x0 - 0x63F ##absolute equivalent value## 0x2BF00000 - 0x2C08FC00 for HOST_MCU_REGION_2 the base address for security firewalls is 0x2BF00000 ( M33 Data RAM ) max window size is 576Kb (depending on the MEMSS mode) example: worker base address: 0x2BF000000 current address to access: 0x2BF00504 region_base_address: 0x1 region_base_address_len: 0x1 0x2BF00504 --> ((0x2BF00504 - 0x2BF000000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHOST4 is shown in Table 5-86.
Return to the Summary Table.
access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-27 | RESERVED | R | 0h | Reserved |
| 26 | BASESEL | R/W | 0h | Base select for Reserved region defaulted to M33 TCM Data RAM (base_sel = 0): this select bit will assign this region to either TCM Data (base_sel = 0) ##register base value## 0x0 - 0x80 ##absolute equivalent value## 0x200000000 - 0x20001FFFF or Data RAM (base_sel = 1) ##register base value## 0x0 - 0x63F ##absolute equivalent value## 0x2BF00000 - 0x2C08FC00 for HOST_MCU_REGION_4 with base_sel = 0 the base address for security firewalls is 0x23F80000 ( M33 TCM Data RAM ) max window size is 128Kb (depending on the MEMSS mode) for HOST_MCU_REGION_4 with base_sel = 1 the base address for security firewalls is 0x2BF00000 ( M33 Data RAM ) max window size is 576Kb (depending on the MEMSS mode) example: worker base address: 0x2BF00000 current address to access: 0x2BF00504 region_base_address: 0x1 region_base_address_len: 0x1 0x2BF00504 --> ((0x2BF00504 - 0x2BF00000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 25-16 | LEN | R/W | 0h | address base len for firewall is the offset from the region's base address indicated in the same region field describing the end of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU_REGION_4 address space: 0x20000000 - 0x2FFFFFFF HOST_MCU_REGION_4 base_len can range from: base_sel = 0 ##register base_len value## 0x0 - 0x7F base_sel = 0 --> HOST_MCU_REGION_4 the base address for security firewalls is 0x23F80000 ( TCM M33 Data RAM ) max window size is 128Kb ################# base_sel = 1 ##register base_len value## 0x0 - 0x240 base_sel = 1 --> HOST_MCU_REGION_4 the base address for security firewalls is 0x2BF00000 (M33 Data RAM ) max window size is 576Kb ################# example: worker base address: 0x23F80000 current address to access: 0x23F81504 region_base_address: 0x4 region_base_address_len: 0x2 --> (region_base_address + region_base_address_len) --> 0x4+0x2 -->0x6 0x23F81504 --> ((0x23F81504 - 0x23F80000) >> 10) -->0x4 0x4 <= 0x5 < 0x6 that address falls on the region window and therefor obeys to that region set of access rules |
| 15 | RESERVED | R | 0h | Reserved |
| 14-4 | BASE | R/W | 0h | address base with 1K granularity : address base for firewall is the the offset start address from a worker base address describing the beginning of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU address space: 0x00000000 - 0x2FFFFFFF / 0x41900000 - 0x4190FFFF HOST_MCU_REGION_4 is assigned to TCM DATA RAM (base_sel = 0) or M33 Data Ram (base_sel = 1) HOST_MCU_REGION_4 base address can range from: (base_sel = 0) ##register base value## 0x0 - 0x27F ##absolute equivalent value## 0x23F80000 - 0x2401FC00 for HOST_MCU_REGION_4 the base address for security firewalls is 0x23F80000 ( TCM Data RAM ) max window size is 128Kb ################## (base_sel = 1) ##register base value## 0x0 - 0x63F ##absolute equivalent value## 0x2BF000000 - 0x2C08FC00 for HOST_MCU_REGION_4 the base address for security firewalls is 0x2BF00000 ( M33 Data RAM ) max window size is 576Kb (depending on the MEMSS mode) example: worker base address: 0x2BF000000 current address to access: 0x2BF00504 region_base_address: 0x1 region_base_address_len: 0x1 0x2BF00504 --> ((0x2BF00504 - 0x2BF00000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHOST5 is shown in Table 5-87.
Return to the Summary Table.
HOST MCU region 5 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-27 | RESERVED | R | 0h | Reserved |
| 26 | BASESEL | R/W | 0h | Base select for Reserved region defaulted to M33 TCM Data RAM (base_sel = 0): this select bit will assign this region to either TCM Data (base_sel = 0) ##register base value## 0x0 - 0x80 ##absolute equivalent value## 0x200000000 - 0x20001FFFF or Data RAM (base_sel = 1) ##register base value## 0x0 - 0x63F ##absolute equivalent value## 0x2BF00000 - 0x2C08FC00 for HOST_MCU_REGION_4 with base_sel = 0 the base address for security firewalls is 0x23F80000 ( M33 TCM Data RAM ) max window size is 128Kb (depending on the MEMSS mode) for HOST_MCU_REGION_4 with base_sel = 1 the base address for security firewalls is 0x2BF00000 ( M33 Data RAM ) max window size is 576Kb (depending on the MEMSS mode) example: worker base address: 0x2BF00000 current address to access: 0x2BF00504 region_base_address: 0x1 region_base_address_len: 0x1 0x2BF00504 --> ((0x2BF00504 - 0x2BF00000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 25-16 | LEN | R/W | 0h | address base len for firewall is the offset from the region's base address indicated in the same region field describing the end of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU_REGION_4 address space: 0x20000000 - 0x2FFFFFFF HOST_MCU_REGION_4 base_len can range from: base_sel = 0 ##register base_len value## 0x0 - 0x7F base_sel = 0 --> HOST_MCU_REGION_4 the base address for security firewalls is 0x23F80000 ( TCM M33 Data RAM ) max window size is 128Kb ################# base_sel = 1 ##register base_len value## 0x0 - 0x240 base_sel = 1 --> HOST_MCU_REGION_4 the base address for security firewalls is 0x2BF00000 (M33 Data RAM ) max window size is 576Kb ################# example: worker base address: 0x23F80000 current address to access: 0x23F81504 region_base_address: 0x4 region_base_address_len: 0x2 --> (region_base_address + region_base_address_len) --> 0x4+0x2 -->0x6 0x23F81504 --> ((0x23F81504 - 0x23F80000) >> 10) -->0x4 0x4 <= 0x5 < 0x6 that address falls on the region window and therefor obeys to that region set of access rules |
| 15 | RESERVED | R | 0h | Reserved |
| 14-4 | BASE | R/W | 0h | address base with 1K granularity : address base for firewall is the the offset start address from a worker base address describing the beginning of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU address space: 0x00000000 - 0x2FFFFFFF / 0x41900000 - 0x4190FFFF HOST_MCU_REGION_4 is assigned to TCM DATA RAM (base_sel = 0) or M33 Data Ram (base_sel = 1) HOST_MCU_REGION_4 base address can range from: (base_sel = 0) ##register base value## 0x0 - 0x27F ##absolute equivalent value## 0x23F80000 - 0x2401FC00 for HOST_MCU_REGION_4 the base address for security firewalls is 0x23F80000 ( TCM Data RAM ) max window size is 128Kb ################## (base_sel = 1) ##register base value## 0x0 - 0x63F ##absolute equivalent value## 0x2BF000000 - 0x2C08FC00 for HOST_MCU_REGION_4 the base address for security firewalls is 0x2BF00000 ( M33 Data RAM ) max window size is 576Kb (depending on the MEMSS mode) example: worker base address: 0x2BF000000 current address to access: 0x2BF00504 region_base_address: 0x1 region_base_address_len: 0x1 0x2BF00504 --> ((0x2BF00504 - 0x2BF00000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHOST6 is shown in Table 5-88.
Return to the Summary Table.
HOST MCU region 6 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-27 | RESERVED | R | 0h | Reserved |
| 26 | BASESEL | R/W | 1h | Base select for Reserved region defaulted to M33 TCM Data RAM (base_sel = 0): this select bit will assign this region to either TCM Data (base_sel = 0) ##register base value## 0x0 - 0x80 ##absolute equivalent value## 0x200000000 - 0x20001FFFF or Data RAM (base_sel = 1) ##register base value## 0x0 - 0x63F ##absolute equivalent value## 0x2BF00000 - 0x2C08FC00 for HOST_MCU_REGION_4 with base_sel = 0 the base address for security firewalls is 0x23F80000 ( M33 TCM Data RAM ) max window size is 128Kb (depending on the MEMSS mode) for HOST_MCU_REGION_4 with base_sel = 1 the base address for security firewalls is 0x2BF00000 ( M33 Data RAM ) max window size is 576Kb (depending on the MEMSS mode) example: worker base address: 0x2BF00000 current address to access: 0x2BF00504 region_base_address: 0x1 region_base_address_len: 0x1 0x2BF00504 --> ((0x2BF00504 - 0x2BF00000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 25-16 | LEN | R/W | 0h | address base len for firewall is the offset from the region's base address indicated in the same region field describing the end of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU_REGION_4 address space: 0x20000000 - 0x2FFFFFFF HOST_MCU_REGION_4 base_len can range from: base_sel = 0 ##register base_len value## 0x0 - 0x7F base_sel = 0 --> HOST_MCU_REGION_4 the base address for security firewalls is 0x23F80000 ( TCM M33 Data RAM ) max window size is 128Kb ################# base_sel = 1 ##register base_len value## 0x0 - 0x240 base_sel = 1 --> HOST_MCU_REGION_4 the base address for security firewalls is 0x2BF00000 (M33 Data RAM ) max window size is 576Kb ################# example: worker base address: 0x23F80000 current address to access: 0x23F81504 region_base_address: 0x4 region_base_address_len: 0x2 --> (region_base_address + region_base_address_len) --> 0x4+0x2 -->0x6 0x23F81504 --> ((0x23F81504 - 0x23F80000) >> 10) -->0x4 0x4 <= 0x5 < 0x6 that address falls on the region window and therefor obeys to that region set of access rules |
| 15 | RESERVED | R | 0h | Reserved |
| 14-4 | BASE | R/W | 0h | address base with 1K granularity : address base for firewall is the the offset start address from a worker base address describing the beginning of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU address space: 0x00000000 - 0x2FFFFFFF / 0x41900000 - 0x4190FFFF HOST_MCU_REGION_4 is assigned to TCM DATA RAM (base_sel = 0) or M33 Data Ram (base_sel = 1) HOST_MCU_REGION_4 base address can range from: (base_sel = 0) ##register base value## 0x0 - 0x27F ##absolute equivalent value## 0x23F80000 - 0x2401FC00 for HOST_MCU_REGION_4 the base address for security firewalls is 0x23F80000 ( TCM Data RAM ) max window size is 128Kb ################## (base_sel = 1) ##register base value## 0x0 - 0x63F ##absolute equivalent value## 0x2BF000000 - 0x2C08FC00 for HOST_MCU_REGION_4 the base address for security firewalls is 0x2BF00000 ( M33 Data RAM ) max window size is 576Kb (depending on the MEMSS mode) example: worker base address: 0x2BF000000 current address to access: 0x2BF00504 region_base_address: 0x1 region_base_address_len: 0x1 0x2BF00504 --> ((0x2BF00504 - 0x2BF00000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHOST7 is shown in Table 5-89.
Return to the Summary Table.
HOST MCU region 7 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-27 | RESERVED | R | 0h | Reserved |
| 26 | BASESEL | R/W | 01h | Base select for Reserved region defaulted to M33 TCM Data RAM (base_sel = 0): this select bit will assign this region to either TCM Data (base_sel = 0) ##register base value## 0x0 - 0x80 ##absolute equivalent value## 0x200000000 - 0x20001FFFF or Data RAM (base_sel = 1) ##register base value## 0x0 - 0x63F ##absolute equivalent value## 0x2BF00000 - 0x2C08FC00 for HOST_MCU_REGION_4 with base_sel = 0 the base address for security firewalls is 0x23F80000 ( M33 TCM Data RAM ) max window size is 128Kb (depending on the MEMSS mode) for HOST_MCU_REGION_4 with base_sel = 1 the base address for security firewalls is 0x2BF00000 ( M33 Data RAM ) max window size is 576Kb (depending on the MEMSS mode) example: worker base address: 0x2BF00000 current address to access: 0x2BF00504 region_base_address: 0x1 region_base_address_len: 0x1 0x2BF00504 --> ((0x2BF00504 - 0x2BF00000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 25-16 | LEN | R/W | 0h | address base len for firewall is the offset from the region's base address indicated in the same region field describing the end of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU_REGION_4 address space: 0x20000000 - 0x2FFFFFFF HOST_MCU_REGION_4 base_len can range from: base_sel = 0 ##register base_len value## 0x0 - 0x7F base_sel = 0 --> HOST_MCU_REGION_4 the base address for security firewalls is 0x23F80000 ( TCM M33 Data RAM ) max window size is 128Kb ################# base_sel = 1 ##register base_len value## 0x0 - 0x240 base_sel = 1 --> HOST_MCU_REGION_4 the base address for security firewalls is 0x2BF00000 (M33 Data RAM ) max window size is 576Kb ################# example: worker base address: 0x23F80000 current address to access: 0x23F81504 region_base_address: 0x4 region_base_address_len: 0x2 --> (region_base_address + region_base_address_len) --> 0x4+0x2 -->0x6 0x23F81504 --> ((0x23F81504 - 0x23F80000) >> 10) -->0x4 0x4 <= 0x5 < 0x6 that address falls on the region window and therefor obeys to that region set of access rules |
| 15 | RESERVED | R | 0h | Reserved |
| 14-4 | BASE | R/W | 0h | address base with 1K granularity : address base for firewall is the the offset start address from a worker base address describing the beginning of a firewall window that has a certain access rules (R/W Permission) for each controller-id HOST_MCU address space: 0x00000000 - 0x2FFFFFFF / 0x41900000 - 0x4190FFFF HOST_MCU_REGION_4 is assigned to TCM DATA RAM (base_sel = 0) or M33 Data Ram (base_sel = 1) HOST_MCU_REGION_4 base address can range from: (base_sel = 0) ##register base value## 0x0 - 0x27F ##absolute equivalent value## 0x23F80000 - 0x2401FC00 for HOST_MCU_REGION_4 the base address for security firewalls is 0x23F80000 ( TCM Data RAM ) max window size is 128Kb ################## (base_sel = 1) ##register base value## 0x0 - 0x63F ##absolute equivalent value## 0x2BF000000 - 0x2C08FC00 for HOST_MCU_REGION_4 the base address for security firewalls is 0x2BF00000 ( M33 Data RAM ) max window size is 576Kb (depending on the MEMSS mode) example: worker base address: 0x2BF000000 current address to access: 0x2BF00504 region_base_address: 0x1 region_base_address_len: 0x1 0x2BF00504 --> ((0x2BF00504 - 0x2BF00000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHOST8 is shown in Table 5-90.
Return to the Summary Table.
HOST MCU region 8 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHOST9 is shown in Table 5-91.
Return to the Summary Table.
HOST MCU region 9 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHOST10 is shown in Table 5-92.
Return to the Summary Table.
HOST MCU region 10 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHOST11 is shown in Table 5-93.
Return to the Summary Table.
HOST MCU region 11 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWXIPOSPI is shown in Table 5-94.
Return to the Summary Table.
XIP_OSPI firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWXIPINDAC is shown in Table 5-95.
Return to the Summary Table.
OSPI_INDAC firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWXIPGEN is shown in Table 5-96.
Return to the Summary Table.
XIP_GEN firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWXIPUDMAS is shown in Table 5-97.
Return to the Summary Table.
XIP_UDMA_SEC firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWXIPUDMANS is shown in Table 5-98.
Return to the Summary Table.
UDMA_NONSEC firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWOTFDE0 is shown in Table 5-99.
Return to the Summary Table.
OTFDE_REGION0 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWOTFDE1 is shown in Table 5-100.
Return to the Summary Table.
OTFDE_REGION1 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWOTFDE2 is shown in Table 5-101.
Return to the Summary Table.
OTFDE_REGION2 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWOTFDE3 is shown in Table 5-102.
Return to the Summary Table.
OTFDE_REGION3 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWDMAGEN is shown in Table 5-103.
Return to the Summary Table.
DMA_GEN firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWDMA0 is shown in Table 5-104.
Return to the Summary Table.
DMA_CH_0 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWDMA1 is shown in Table 5-105.
Return to the Summary Table.
DMA_CH_1 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWDMA2 is shown in Table 5-106.
Return to the Summary Table.
DMA_CH_2 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWDMA3 is shown in Table 5-107.
Return to the Summary Table.
DMA_CH_3 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWDMA4 is shown in Table 5-108.
Return to the Summary Table.
DMA_CH_4 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWDMA5 is shown in Table 5-109.
Return to the Summary Table.
DMA_CH_5 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWDMA6 is shown in Table 5-110.
Return to the Summary Table.
DMA_CH_6 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWDMA7 is shown in Table 5-111.
Return to the Summary Table.
DMA_CH_7 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWDMA8 is shown in Table 5-112.
Return to the Summary Table.
DMA_CH_8 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWDMA9 is shown in Table 5-113.
Return to the Summary Table.
DMA_CH_9 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWDMA10 is shown in Table 5-114.
Return to the Summary Table.
DMA_CH_10 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWDMA11 is shown in Table 5-115.
Return to the Summary Table.
DMA_CH_11 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHSMEIPNS is shown in Table 5-116.
Return to the Summary Table.
HSM EIP NONSEC firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-21 | RESERVED | R | 0h | Reserved |
| 20-16 | LEN | R/W | 0h | address base with 1K granularity : address base len for firewall is the offset from the region's base address indicated in the same region field describing the end of a firewall window that has a certain access rules (R/W Permission) for each controller-id HSM address space: 0x41B00000 - 0x41B3FFFF HSM_EIP_REGS base_len can range from: ##register base_len value## 0x0 - 0xF for HSM the base address for security firewalls is 0x41B00000 ( HSM_EIP_REGS ) max window size is 16Kb example: worker base address: 0x41B00000 current address to access: 0x41B01504 region_base_address: 0x4 region_base_address_len: 0x2 --> (region_base_address + region_base_address_len) --> 0x4+0x2 -->0x6 0x41B01504 --> ((0x41B01504 - 0x41B00000) >> 10) -->0x4 0x4 <= 0x5 < 0x6 that address falls on the region window and therefor obeys to that region set of access rules |
| 15-9 | RESERVED | R | 0h | Reserved |
| 8-4 | BASE | R/W | 0h | address base with 1K granularity : address base for firewall is the the offset start address from a worker base address describing the beginning of a firewall window that has a certain access rules (R/W Permission) for each controller-id HSM address space: 0x41B00000 - 0x41B3FFFF HSM_EIP_REGS base address can range from: ##register base value## 0x0 - 0xF ##absolute equivalent value## 0x41B00000 - 0x41B03FFF for HSM the base address for security firewalls is 0x41B00000 ( HSM_EIP_REGS ) max window size is 16Kb example: worker base address: 0x41B00000 current address to access: 0x41B00504 region_base_address: 0x1 region_base_address_len: 0x1 0x41B00504 --> ((0x41B00504 - 0x41B00000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHSMEIPS is shown in Table 5-117.
Return to the Summary Table.
HSM EIP SEC firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-21 | RESERVED | R | 0h | Reserved |
| 20-16 | LEN | R/W | 0h | address base with 1K granularity : address base len for firewall is the offset from the region's base address indicated in the same region field describing the end of a firewall window that has a certain access rules (R/W Permission) for each controller-id HSM address space: 0x41B00000 - 0x41B3FFFF HSM_EIP_REGS base_len can range from: ##register base_len value## 0x0 - 0xF for HSM the base address for security firewalls is 0x41B00000 ( HSM_EIP_REGS ) max window size is 16Kb example: worker base address: 0x41B00000 current address to access: 0x41B01504 region_base_address: 0x4 region_base_address_len: 0x2 --> (region_base_address + region_base_address_len) --> 0x4+0x2 -->0x6 0x41B01504 --> ((0x41B01504 - 0x41B00000) >> 10) -->0x4 0x4 <= 0x5 < 0x6 that address falls on the region window and therefor obeys to that region set of access rules |
| 15-9 | RESERVED | R | 0h | Reserved |
| 8-4 | BASE | R/W | 0h | address base with 1K granularity : address base for firewall is the the offset start address from a worker base address describing the beginning of a firewall window that has a certain access rules (R/W Permission) for each controller-id HSM address space: 0x41B00000 - 0x41B3FFFF HSM_EIP_REGS base address can range from: ##register base value## 0x0 - ##absolute equivalent value## 0x41B00000 - 0x41B03FFF for HSM the base address for security firewalls is 0x41B00000 ( HSM_EIP_REGS ) max window size is 16Kb example: worker base address: 0x41B00000 current address to access: 0x41B00504 region_base_address: 0x1 region_base_address_len: 0x1 0x41B00504 --> ((0x41B00504 - 0x41B00000) >> 10) --> 0x1 0x1(base) <= 0x1(current) < 0x1(base)+0x1(len) that address falls on the region window and therefor obeys to that region set of access rules |
| 3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHSMWRAPNS is shown in Table 5-118.
Return to the Summary Table.
HSM Wrapper NONSEC firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHSMWRAPS is shown in Table 5-119.
Return to the Summary Table.
HSM Wrapper SEC firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWHSMDBG is shown in Table 5-120.
Return to the Summary Table.
HSM DEBUG firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWI2C0 is shown in Table 5-121.
Return to the Summary Table.
I2C0 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWI2C1 is shown in Table 5-122.
Return to the Summary Table.
I2C1 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWSPSPI0 is shown in Table 5-123.
Return to the Summary Table.
SPI0 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWSPSPI1 is shown in Table 5-124.
Return to the Summary Table.
SPI1 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWSPUART0 is shown in Table 5-125.
Return to the Summary Table.
UART0 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWSPUART1 is shown in Table 5-126.
Return to the Summary Table.
UART1 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWSPGPT0 is shown in Table 5-127.
Return to the Summary Table.
GPTIMER0 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWSPGPT1 is shown in Table 5-128.
Return to the Summary Table.
GPTIMER1 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWSPI2S is shown in Table 5-129.
Return to the Summary Table.
I2S firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWPDM is shown in Table 5-130.
Return to the Summary Table.
PDM firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWSPCAN is shown in Table 5-131.
Return to the Summary Table.
CAN firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWSPADC is shown in Table 5-132.
Return to the Summary Table.
ADC firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWSPSDMMC is shown in Table 5-133.
Return to the Summary Table.
SDMMC firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWSPSDIO is shown in Table 5-134.
Return to the Summary Table.
SDIO firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWSPUART2 is shown in Table 5-135.
Return to the Summary Table.
UART2 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
UDMANSCTL is shown in Table 5-136.
Return to the Summary Table.
uDMA Non-secured Channel Control.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-1 | RESERVED | R | 0h | Reserved |
| 0 | ACCPER | R/W | 0h | Access Permission. Define uDMA non-sec channel access permission to secured flash address: '0' - access not allowed '1' - access allowed |
FWIOPAD0 is shown in Table 5-137.
Return to the Summary Table.
IOMUX_PAD_0 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD1 is shown in Table 5-138.
Return to the Summary Table.
IOMUX_PAD_1 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD2 is shown in Table 5-139.
Return to the Summary Table.
IOMUX_PAD_2 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD3 is shown in Table 5-140.
Return to the Summary Table.
IOMUX_PAD_3 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD4 is shown in Table 5-141.
Return to the Summary Table.
IOMUX_PAD_4 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD5 is shown in Table 5-142.
Return to the Summary Table.
IOMUX_PAD_5 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD6 is shown in Table 5-143.
Return to the Summary Table.
IOMUX_PAD_6 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD7 is shown in Table 5-144.
Return to the Summary Table.
IOMUX_PAD_7 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD8 is shown in Table 5-145.
Return to the Summary Table.
IOMUX_PAD_8 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD9 is shown in Table 5-146.
Return to the Summary Table.
IOMUX_PAD_9 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD10 is shown in Table 5-147.
Return to the Summary Table.
IOMUX_PAD_10 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD11 is shown in Table 5-148.
Return to the Summary Table.
IOMUX_PAD_11 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD12 is shown in Table 5-149.
Return to the Summary Table.
IOMUX_PAD_12 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD13 is shown in Table 5-150.
Return to the Summary Table.
IOMUX_PAD_13 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD14 is shown in Table 5-151.
Return to the Summary Table.
IOMUX_PAD_14 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD15 is shown in Table 5-152.
Return to the Summary Table.
IOMUX_PAD_15 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD16 is shown in Table 5-153.
Return to the Summary Table.
IOMUX_PAD_16 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD17 is shown in Table 5-154.
Return to the Summary Table.
IOMUX_PAD_17 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD18 is shown in Table 5-155.
Return to the Summary Table.
IOMUX_PAD_18 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD19 is shown in Table 5-156.
Return to the Summary Table.
IOMUX_PAD_19 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD20 is shown in Table 5-157.
Return to the Summary Table.
IOMUX_PAD_20 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD21 is shown in Table 5-158.
Return to the Summary Table.
IOMUX_PAD_21 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD22 is shown in Table 5-159.
Return to the Summary Table.
IOMUX_PAD_22 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD23 is shown in Table 5-160.
Return to the Summary Table.
IOMUX_PAD_23 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD24 is shown in Table 5-161.
Return to the Summary Table.
IOMUX_PAD_24 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD25 is shown in Table 5-162.
Return to the Summary Table.
IOMUX_PAD_25 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD26 is shown in Table 5-163.
Return to the Summary Table.
IOMUX_PAD_26 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD27 is shown in Table 5-164.
Return to the Summary Table.
IOMUX_PAD_27 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD28 is shown in Table 5-165.
Return to the Summary Table.
IOMUX_PAD_28 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD29 is shown in Table 5-166.
Return to the Summary Table.
IOMUX_PAD_29 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD30 is shown in Table 5-167.
Return to the Summary Table.
IOMUX_PAD_30 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD31 is shown in Table 5-168.
Return to the Summary Table.
IOMUX_PAD_31 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD32 is shown in Table 5-169.
Return to the Summary Table.
IOMUX_PAD_32 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD33 is shown in Table 5-170.
Return to the Summary Table.
IOMUX_PAD_33 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD34 is shown in Table 5-171.
Return to the Summary Table.
IOMUX_PAD_34 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD35 is shown in Table 5-172.
Return to the Summary Table.
IOMUX_PAD_35 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD36 is shown in Table 5-173.
Return to the Summary Table.
IOMUX_PAD_36 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD37 is shown in Table 5-174.
Return to the Summary Table.
IOMUX_PAD_37 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD38 is shown in Table 5-175.
Return to the Summary Table.
IOMUX_PAD_38 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD39 is shown in Table 5-176.
Return to the Summary Table.
IOMUX_PAD_39 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD40 is shown in Table 5-177.
Return to the Summary Table.
IOMUX_PAD_40 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD41 is shown in Table 5-178.
Return to the Summary Table.
IOMUX_PAD_41 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD42 is shown in Table 5-179.
Return to the Summary Table.
IOMUX_PAD_42 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD43 is shown in Table 5-180.
Return to the Summary Table.
IOMUX_PAD_43 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD44 is shown in Table 5-181.
Return to the Summary Table.
IOMUX_PAD_44 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD45 is shown in Table 5-182.
Return to the Summary Table.
IOMUX_PAD_45 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD46 is shown in Table 5-183.
Return to the Summary Table.
IOMUX_PAD_46 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD47 is shown in Table 5-184.
Return to the Summary Table.
IOMUX_PAD_47 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWIOPAD48 is shown in Table 5-185.
Return to the Summary Table.
IOMUX_PAD_48 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWDMA12 is shown in Table 5-186.
Return to the Summary Table.
DMA_CH_12 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
FWDMA13 is shown in Table 5-187.
Return to the Summary Table.
DMA_CH_13 firewall access permission for 3 controller id : 0 - M33 Non Secured 1 - M33 Secured 2 - Core (Non Secure)
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-3 | RESERVED | R | 0h | Reserved |
| 2 | CORENS | R/W | 0h | Controller Core Non Secured: '0' - access not allowed '1' - access allowed |
| 1 | M33S | R/W | 0h | Controller M33 Secured: '0' - access not allowed '1' - access allowed |
| 0 | M33NS | R/W | 0h | Controller M33 None Secured: '0' - access not allowed '1' - access allowed |
USECSTB is shown in Table 5-188.
Return to the Summary Table.
Micro Second STB
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-14 | RESERVED | R | 0h | Reserved |
| 13-8 | 16US | R/W | Fh | Set how many micro second strobes are in 16 micro seconds, minus 1. Default: 16-1 =15. |
| 7-0 | US | R/W | 4Fh | Set how many soc clk are in one micro second, minus 1. for 40mhz : should be 39. for 80mhz : should be 79. (Soc clock default is 80MHz) |
GPIOEVT0NS is shown in Table 5-189.
Return to the Summary Table.
Non-Secured GPIO Event Status, 1st Register. 45 bits status over two registers.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | STA31TO0 | R | 0h | Non-Secured event status , first 32 bits. ([31:0]) |
GPIOEVT1NS is shown in Table 5-190.
Return to the Summary Table.
Non-Secured GPIO Event Status, 2nd Register. 45 bits status over two registers.
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-13 | RESERVED | R | 0h | Reserved |
| 12-0 | STA44TO32 | R | 0h | Non-Secured event status , 13 MSBs. ([44:32]) |
DBM33NS0 is shown in Table 5-191.
Return to the Summary Table.
M33 Non-Secured Doorbell IMASK. Mask Event. '0' - CLR - Clear Interrupt Mask '1' - SET - Set Interrupt Mask
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-4 | RESERVED | R | 0h | Reserved |
| 3-0 | IMASK | R/W | 0h | bit3 - doorbell 7 M3 IRQ bit2 - doorbell 6 M3 IRQ bit1 - doorbell 3 M3 IRQ bit0 - doorbell 2 M3 IRQ |
DBNSISET is shown in Table 5-192.
Return to the Summary Table.
M33 Non-Secured Doorbells ISET. Sets event in RIS Write 0 - NO_EFFECT - Writing 0 has no effect Write 1 - SET - Sets interrupt
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-4 | RESERVED | R | 0h | Reserved |
| 3-0 | ISET | W | 0h | bit3 - doorbell 7 M3 IRQ bit2 - doorbell 6 M3 IRQ bit1 - doorbell 3 M3 IRQ bit0 - doorbell 2 M3 IRQ Type: Write-Clear |
DBNSICLR is shown in Table 5-193.
Return to the Summary Table.
M33 Non-Secured Doorbell ICLR. Clears event in RIS Write 0 - NO_EFFECT - Writing 0 has no effect Write 1 - CLR - Clears the Event
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-4 | RESERVED | R | 0h | Reserved |
| 3-0 | ICLR | W | 0h | bit3 - doorbell 7 M3 IRQ bit2 - doorbell 6 M3 IRQ bit1 - doorbell 3 M3 IRQ bit0 - doorbell 2 M3 IRQ Type: Write-Clear |
DBNSIMSET is shown in Table 5-194.
Return to the Summary Table.
M33 Non-Secured Doorbell IMSET. Sets Event Write 0 - NO_EFFECT - Writing 0 has no effect Write 1 - SET - Set interrupt mask
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-4 | RESERVED | R | 0h | Reserved |
| 3-0 | IMSET | W | 0h | bit3 - doorbell 7 M3 IRQ bit2 - doorbell 6 M3 IRQ bit1 - doorbell 3 M3 IRQ bit0 - doorbell 2 M3 IRQ Type: Write-Clear |
DBNSIMCLR is shown in Table 5-195.
Return to the Summary Table.
M33 Non-Secured Doorbell IMCLR, Clears Event Write 0 - NO_EFFECT - Writing 0 has no effect Write 1 - CLR - Clear interrupt mask
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-4 | RESERVED | R | 0h | Reserved |
| 3-0 | IMCLR | W | 0h | bit3 - doorbell 7 M3 IRQ bit2 - doorbell 6 M3 IRQ bit1 - doorbell 3 M3 IRQ bit0 - doorbell 2 M3 IRQ Type: Write-Clear |
DBNSRIS is shown in Table 5-196.
Return to the Summary Table.
M33 Non-Secured Doorbell RIS. Raw interrupt status for event. This bit is set to 1 when an event is received. when the corresponding bit in ICLR is set to 1, this bit will be cleared. Read 0 - CLR - Interrupt did not occur Read 1 - SET - Interrupt occurred
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-4 | RESERVED | R | 0h | Reserved |
| 3-0 | RIS | R | 0h | bit3 - doorbell 7 M3 IRQ bit2 - doorbell 6 M3 IRQ bit1 - doorbell 3 M3 IRQ bit0 - doorbell 2 M3 IRQ |
DBNSMIS is shown in Table 5-197.
Return to the Summary Table.
M33 Non-Secured Doorbell MIS. Mask interrupt status for event Read 0 - CLR - Interrupt did not occur Read 1 - SET - Interrupt occurred
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-4 | RESERVED | R | 0h | Reserved |
| 3-0 | MIS | R | 0h | bit3 - doorbell 7 M3 IRQ bit2 - doorbell 6 M3 IRQ bit1 - doorbell 3 M3 IRQ bit0 - doorbell 2 M3 IRQ |
GPIOMIS0NS is shown in Table 5-198.
Return to the Summary Table.
Non Secured GPIO MIS. 31-0
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | 31TO0 | R | 0h | 32 LSBs of GPIO MIS |
GPIOMIS1NS is shown in Table 5-199.
Return to the Summary Table.
Non Secure GPIO MIS. 44-32
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-13 | RESERVED | R | 0h | Reserved |
| 12-0 | 44TO32 | R | 0h | 13 MSBs of GPIO MIS. 44-32 |
GPIOFNC0NS is shown in Table 5-200.
Return to the Summary Table.
Non Secured GPIO Functional Mask. 31-0 0. Mask 1. Un-Mask
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | MASK31TO0 | R/W | 0h | 32 LSBs of non-secured functional mask for GPIO. |
GPIOFNC1NS is shown in Table 5-201.
Return to the Summary Table.
non secured gpio functional mask
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-13 | RESERVED | R | 0h | Reserved |
| 12-0 | MASK44TO32 | R/W | 0h | 13 MSBs of non-secured functional mask for GPIO. 44-32 |