SPRUJ17I March 2022 – August 2025 AM2631 , AM2631-Q1 , AM2632 , AM2632-Q1 , AM2634 , AM2634-Q1
Table 7-5 through Table 7-6 list some R5FSS features associated with special signals.
| Feature | Comment |
|---|---|
| Cluster affinity group ID | R5F Cluster 0 (ID = 0x0) |
| Exception handling state at reset 0 = Arm 1 = Thumb |
Controlled via MSS_CTRL R5SS0_TEINIT register
setting. Defaults to Arm mode |
|
Dual core or Lockstep mode 0 = Dual Core mode 1 = Lockstep mode |
Controlled via MSS_CTRL R5SS0_CONTROL register
setting. Defaults to a value defined by eFuse/MMR control |
| CPUn execution halt when coming out of reset (CPUn_HALT) | Controlled via MSS_CTRL R5SS0_COREx_HALT register
setting. Defaults to halted state. See R5 Core Halting and Unhalting for more detail. |
| CPUn exception vectors base address | Defaults to Bootvector RAM address 0x0000_0000 |
| CPUn VIM base address | 0x50F0 0000 |
| CPUn non-maskable fast interrupts enable | Disabled |
| CPUn VBUSM peripheral port enabled at reset | Disabled, not used. |
| CPUn VBUSP peripheral port enable at reset |
Defaults to Enabled state |
| CPUn VBUSP peripheral port base address |
Defaults to 0x5000_0000 |
| CPUn VBUSP peripheral port size |
Defaults to 256MB 0x5000_0000 to 0x5FFFF_FFFF |
| CPUn VBUSM normal peripheral port base address | Not used |
| CPUn VBUSM normal peripheral port size | Not used |
| CPUn VBUSM virtual peripheral port base address | Not used |
| CPUn VBUSM virtual peripheral port size | Not used |
| CPUn WFI state | Status logged into MSS_CTRL R5SS0_COREx_STAT register bit. See the R5 WFI section. |
| CPUn WFE state | Status logged into MSS_CTRL R5SS0_COREx_STAT register bit. See the R5 WFI section. |
| CPU Clockgate Control | Controlled via MSS_RCM R5SS0_COREx_GATE register setting. Individual Core clocks can be gated |
| CPUn TCM Bus Parity | Enabled |
| Feature | Comment |
|---|---|
| Cluster affinity group ID | R5F Cluster 1 (ID = 0x1) |
| Exception handling state at reset 0 = Arm 1 = Thumb |
Controlled via MSS_CTRL R5SS1_TEINIT register
setting. Defaults to Arm mode |
|
Dual core or Lockstep mode 0 = Dual Core mode 1 = Lockstep mode |
Controlled via MSS_CTRL R5SS1_CONTROL register
setting. Defaults to a value defined by eFuse/MMR control |
| CPUn execution halt when coming out of reset (CPUn_HALT) | Controlled via MSS_CTRL R5SS1_COREx_HALT register
setting. Defaults to halted state. See R5 Core Halting and Unhalting for more detail. |
| CPUn exception vectors base address | Defaults to Bootvector RAM address 0x0000_0000 |
| CPUn VIM base address | 0x50F0 0000 |
| CPUn non-maskable fast interrupts enable | Disabled |
| CPUn VBUSM peripheral port enabled at reset | Disabled, not used. |
| CPUn VBUSP peripheral port enable at reset |
Defaults to Enabled state |
| CPUn VBUSP peripheral port base address |
Defaults to 0x5000_0000 |
| CPUn VBUSP peripheral port size |
Defaults to 256MB 0x5000_0000 to 0x5FFFF_FFFF |
| CPUn VBUSM normal peripheral port base address | Not used |
| CPUn VBUSM normal peripheral port size | Not used |
| CPUn VBUSM virtual peripheral port base address | Not used |
| CPUn VBUSM virtual peripheral port size | Not used |
| CPUn WFI state | Status logged into MSS_CTRL R5SS1_COREx_STAT register bit. See the R5 WFI section. |
| CPUn WFE state | Status logged into MSS_CTRL R5SS1_COREx_STAT register bit. See the R5 WFI section. |
| CPU Clockgate Control | Controlled via MSS_RCM R5SS1_COREx_GATE register setting. Individual Core clocks can be gated |
| CPUn TCM Bus Parity | Enabled |
By default, the R5FSS[0-1] will be in lockstep mode. Switching to dual core mode or staying in lockstep mode is handled through setting a combination of eFuse and MMR bits. See Table 7-7 for a summary of possible combinations.
| eFuse BitEFUSE1_ROW_12_R5SS[0-1]_FORCE_DUAL_CORE | eFuse BitEFUSE1_ROW_12_R5SS[0-1]_DUAL_CORE_DISABLE | MMR BitR5SS[0-1]_CONTROL_LOCK_STEP | R5FSS[0-1] Mode |
|---|---|---|---|
| 0 | 0 | 0 | Dual Core |
| 0 | 0 | 1 | Lockstep (default) |
| 1 | X | X | Dual Core |
| 0 | 1 | X | Lockstep |
Based on the part number, the eFuse bits will decide whether the MMR can be used for switching to dual core. Follow the below sequence in such cases.