SLAU847E October 2022 – May 2025 MSPM0L1105 , MSPM0L1106 , MSPM0L1116 , MSPM0L1117 , MSPM0L1227 , MSPM0L1227-Q1 , MSPM0L1228 , MSPM0L1228-Q1 , MSPM0L1303 , MSPM0L1304 , MSPM0L1304-Q1 , MSPM0L1305 , MSPM0L1305-Q1 , MSPM0L1306 , MSPM0L1306-Q1 , MSPM0L1343 , MSPM0L1344 , MSPM0L1345 , MSPM0L1346 , MSPM0L2227 , MSPM0L2227-Q1 , MSPM0L2228 , MSPM0L2228-Q1
Table 1-36 lists the memory-mapped registers for the NONMAIN_TYPEC registers. All register offset addresses not listed in Table 1-36 should be considered as reserved locations and the register contents should not be modified.
| Offset | Acronym | Register Name | Group | Section |
|---|---|---|---|---|
| 41C00000h | BCRCONFIGID | Configuration ID of BCR Structure | Go | |
| 41C00004h | BOOTCFG0 | Serial wire debug (SWD) lock policy. | Go | |
| 41C00008h | BOOTCFG1 | TI Failure Analysis (FA) mode and BSL invoke pin policies | Go | |
| 41C0000Ch | FLASHSWP0 | Static write protection policy for the first 32kB of flash memory. When protected, sectors will not be available for program or erase by either the bootloader or application code | Go | |
| 41C00010h | FLASHSWP1 | Static write protection policy for additional sectors of flash memory. When protected, sectors will not be available for program or erase by either the bootloader or application code | Go | |
| 41C00014h | BOOTCFG4 | Configures Static write protection policy for Configuration flash memory(NONMAIN) and Debug Hold Policy | Go | |
| 41C00018h | BOOTCFG5 | Configures the existence of Customer Secure Code(CSC) and Flash Bank Swap Policy | Go | |
| 41C0001Ch | BOOTCFG2 | Fast boot mode policy and BSL mode policy | Go | |
| 41C00020h | BOOTCFG3 | Mass erase and factory reset mode policies. These policies affect SWD initiated and BSL initiated mass erase and factory reset commands. If the SW-DP is disabled (SWDP_MODE is disabled), SWD initiated commands are not allowed as the SW-DP is fully disabled. If the BSL is disabled (BSLMODE is disabled), these settings are a a don't care for BSL initiated commands as the BSL is not enabled to be invoked. | Go | |
| 41C00024h + formula | PWDMASSERASE[y] | SHA2-256 Digest of the SWD mass erase command password (must be provided via DSSM to authenticate a mass erase command) | Go | |
| 41C00044h + formula | PWDFACTORYRESET[y] | SHA2-256 digest of the SWD factory reset command password (must be provided via DSSM to authenticate a factory reset command) | Go | |
| 41C00064h + formula | PWDDEBUGLOCK[y] | SHA2-256 Digest of the Debug Lock Password. This password is used when the BOOTCFG0.DEBUGACCESS field is configured as Enable with password. | Go | |
| 41C00084h | BOOTCFG6 | Application digest check policy | Go | |
| 41C00088h | APPDIGESTSTART | Start address of the application CRC/SHA Digest check (must be an address in a MAIN flash region). | Go | |
| 41C0008Ch | APPDIGESTLENGTH | Length of the application to be include in the application CRC/SHA Digest check (in bytes), starting from APPDIGESTSTART | Go | |
| 41C00090h + formula | APPDIGEST[y] | Expected application CRC32/SHA2-256 digest to test against during boot. Note: If CRC check is enabled only the first 32bit word of this DIGEST is used. | Go | |
| 41C000B0h | FLASHSWP2 | Static write protection policy for additional sectors of flash memory. When protected, sectors will not be available for program or erase by either the bootloader or application code | Go | |
| 41C000B4h | BOOTCRC | CRC digest of the BCR configuration portion of the NONMAIN memory. | Go | |
| 41C00100h | BSLCONFIGID | Configuration ID of BSL Structure | Go | |
| 41C00104h | BSLPINCFG0 | BSL UART PIN Configuration. The reset value of these fields differ for each device, based on the pins used. | Go | |
| 41C00108h | BSLPINCFG1 | BSL I2C PIN Configuration. The reset value of these fields differ for each device, based on the pins used. | Go | |
| 41C0010Ch | BSLCONFIG0 | BSL invoke pin configuration and memory read-out policy. | Go | |
| 41C00110h + formula | PWDBSL[y] | SHA2-256 Digest of BSL password. | Go | |
| 41C00130h | BSLPLUGINCFG | Defines the presence and type of a BSL plug-in in MAIN flash memory. | Go | |
| 41C00134h + formula | BSLPLUGINHOOK[y] | Function pointers for plug-in init, receive, transmit, and de-init functions. | Go | |
| 41C00144h | BSLCONFIG1 | Go | ||
| 41C00148h | SBLADDRESS | Address of an alternate BSL. | Go | |
| 41C0014Ch | BSLAPPVER | Address of the application version word. | Go | |
| 41C00150h | BSLCONFIG2 | Configures the BSL Alert Configuration and I2C Target address of BSL. | Go | |
| 41C00154h | BSLCRC | CRC digest of the BSL_CONFIG portion of the NONMAIN memory. | Go |
Complex bit access types are encoded to fit into small table cells. Table 1-37 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 | |
| Register Array Variables | ||
| i,j,k,l,m,n | When these variables are used in a register name, an offset, or an address, they refer to the value of a register array where the register is part of a group of repeating registers. The register groups form a hierarchical structure and the array is represented with a formula. | |
| y | When this variable is used in a register name, an offset, or an address it refers to the value of a register array. | |
BCRCONFIGID is shown in Figure 1-29 and described in Table 1-38.
Return to the Summary Table.
Configuration ID of BCR Structure
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| CONFIG | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | CONFIG | R/W | 0h | Configuration ID of the BCR Structure |
BOOTCFG0 is shown in Figure 1-30 and described in Table 1-39.
Return to the Summary Table.
Serial wire debug (SWD) lock policy.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| SWDP_MODE | DEBUGACCESS | ||||||||||||||||||||||||||||||
| R/W-0h | W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | SWDP_MODE | R/W | AABBh | The serial wire debug port (SW-DP) access policy. This policy sets whether any communication is allowed with the device via the SWD pins (to any DAP). When disabled, no SWD communication is possible regardless of the configuration of the DEBUGACCESS field.
|
| 15-0 | DEBUGACCESS | W | AABBh | The debug access policy for accessing the AHB-AP, ET-AP, and PWR-AP debug access ports. Note that if SWDP_MODE is set to DISABLED, the value of this field is ignored and the debug port will remain fully locked
|
BOOTCFG1 is shown in Figure 1-31 and described in Table 1-40.
Return to the Summary Table.
TI Failure Analysis (FA) mode and BSL invoke pin policies
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| BSL_PIN_INVOKE | TI_FA_MODE | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | BSL_PIN_INVOKE | R/W | AABBh | Boot strap loader (BSL) pin invoke method enable/disable policy
|
| 15-0 | TI_FA_MODE | R/W | AABBh | Sets the TI failure analysis enable/disable policy. If enabled, a re-test request through DSSM is allowed, else it is not allowed. Note that if SWDP_MODE is set to disabled, this field is ignored and failure analysis is not possible.
|
FLASHSWP0 is shown in Figure 1-32 and described in Table 1-41.
Return to the Summary Table.
Static write protection policy for the first 32kB of flash memory. When protected, sectors will not be available for program or erase by either the bootloader or application code
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| DATA | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | DATA | R/W | FFFFFFFFh | 1 bit per sector
|
FLASHSWP1 is shown in Figure 1-33 and described in Table 1-42.
Return to the Summary Table.
Static write protection policy for additional sectors of flash memory. When protected, sectors will not be available for program or erase by either the bootloader or application code
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| DATA | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | DATA | R/W | FFFFFFFFh | 1 bit per 8 sectors. This is used to protect Flash memory from (0 to 256 kb)
|
BOOTCFG4 is shown in Figure 1-34 and described in Table 1-43.
Return to the Summary Table.
Configures Static write protection policy for Configuration flash memory(NONMAIN) and Debug Hold Policy
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| DEBUGHOLD | NONMAINSWP | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | DEBUGHOLD | R/W | AABBh | Controls the release of debug access until INITDONE is issued by Customer Secure Code(CSC). This configuration is applicable only when DEBUGACCESS and CSCEXISTS is enabled.
|
| 15-0 | NONMAINSWP | R/W | AABBh | Static write protection policy for entire NONMAIN device configuration memory.
|
BOOTCFG5 is shown in Figure 1-35 and described in Table 1-44.
Return to the Summary Table.
Configures the existence of Customer Secure Code(CSC) and Flash Bank Swap Policy
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| FLASHBANKSWAPPOLICY | |||||||||||||||
| R/W-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| CSCEXISTS | |||||||||||||||
| R/W-0h | |||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | FLASHBANKSWAPPOLICY | R/W | AABBh | Controls the Flash Bank Swap Policy. This configuration is valid only, if CSCEXISTS is enabled.
|
| 15-0 | CSCEXISTS | R/W | AABBh | Controls the existence of Customer Secure Code(CSC).
|
BOOTCFG2 is shown in Figure 1-36 and described in Table 1-45.
Return to the Summary Table.
Fast boot mode policy and BSL mode policy
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| BSLMODE | FASTBOOTMODE | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | BSLMODE | R/W | AABBh | BSLMODE configures the boot strap loader enable/disable policy
|
| 15-0 | FASTBOOTMODE | R/W | FFFFh | FASTBOOTMODE configures the fast boot mode enable/disable policy
|
BOOTCFG3 is shown in Figure 1-37 and described in Table 1-46.
Return to the Summary Table.
Mass erase and factory reset mode policies. These policies affect SWD initiated and BSL initiated mass erase and factory reset commands. If the SW-DP is disabled (SWDP_MODE is disabled), SWD initiated commands are not allowed as the SW-DP is fully disabled. If the BSL is disabled (BSLMODE is disabled), these settings are a a don't care for BSL initiated commands as the BSL is not enabled to be invoked.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| FACTORYRESETCMDACCESS | |||||||||||||||
| R/W-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| MASSERASECMDACCESS | |||||||||||||||
| R/W-0h | |||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | FACTORYRESETCMDACCESS | R/W | AABBh | The factory reset command policy
|
| 15-0 | MASSERASECMDACCESS | R/W | AABBh | The mass erase command policy
|
PWDMASSERASE[y] is shown in Figure 1-38 and described in Table 1-47.
Return to the Summary Table.
SHA2-256 Digest of the SWD mass erase command password (must be provided via DSSM to authenticate a mass erase command)
Offset = 41C00024h + (y * 4h); where y = 0h to 7h
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| DIGEST | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | DIGEST | R/W | FFFFFFFFh | SHA2-256 Bit digest of Mass Erase Password of size 128 bit |
PWDFACTORYRESET[y] is shown in Figure 1-39 and described in Table 1-48.
Return to the Summary Table.
SHA2-256 digest of the SWD factory reset command password (must be provided via DSSM to authenticate a factory reset command)
Offset = 41C00044h + (y * 4h); where y = 0h to 7h
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| DIGEST | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | DIGEST | R/W | FFFFFFFFh | SHA2-256 Bit digest of Factory Reset Password of size 128 bit |
PWDDEBUGLOCK[y] is shown in Figure 1-40 and described in Table 1-49.
Return to the Summary Table.
SHA2-256 Digest of the Debug Lock Password. This password is used when the BOOTCFG0.DEBUGACCESS field is configured as Enable with password.
Offset = 41C00064h + (y * 4h); where y = 0h to 7h
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| DIGEST | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | DIGEST | R/W | FFFFFFFFh | SHA2-256 Bit digest of Debug Lock Password of size 128 bit |
BOOTCFG6 is shown in Figure 1-41 and described in Table 1-50.
Return to the Summary Table.
Application digest check policy
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| APPDIGESTMODE | RESERVED | ||||||||||||||||||||||||||||||
| R/W-0h | R-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | APPDIGESTMODE | R/W | FFFFh | APPDIGESTMODE configures the boot time CRC/SHA Digest check of a segment of MAIN flash memory.
|
| 15-0 | RESERVED | R | FFFFh |
APPDIGESTSTART is shown in Figure 1-42 and described in Table 1-51.
Return to the Summary Table.
Start address of the application CRC/SHA Digest check (must be an address in a MAIN flash region).
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| ADDRESS | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | ADDRESS | R/W | FFFFFFFFh | Application CRC/SHA Digest check start address |
APPDIGESTLENGTH is shown in Figure 1-43 and described in Table 1-52.
Return to the Summary Table.
Length of the application to be include in the application CRC/SHA Digest check (in bytes), starting from APPDIGESTSTART
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| LENGTH | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | LENGTH | R/W | FFFFFFFFh | Application CRC/SHA Digest check source data length |
APPDIGEST[y] is shown in Figure 1-44 and described in Table 1-53.
Return to the Summary Table.
Expected application CRC32/SHA2-256 digest to test against during boot.
Note: If CRC check is enabled only the first 32bit word of this DIGEST is used.
Offset = 41C00090h + (y * 4h); where y = 0h to 7h
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| DIGEST | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | DIGEST | R/W | FFFFFFFFh | CRC-32 bit/or SHA-256 bit Digest of the application in Main Flash |
FLASHSWP2 is shown in Figure 1-45 and described in Table 1-54.
Return to the Summary Table.
Static write protection policy for additional sectors of flash memory. When protected, sectors will not be available for program or erase by either the bootloader or application code
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| DATA | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | DATA | R/W | FFFFFFFFh | 1 bit per 8 sectors. This is used to protect Flash memory from (256 to 512 kb). It is not applicable for devices that have Flash memory less than 256KB.
|
BOOTCRC is shown in Figure 1-46 and described in Table 1-55.
Return to the Summary Table.
CRC digest of the BCR configuration portion of the NONMAIN memory.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| DIGEST | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | DIGEST | R/W | 0h | BCR configuration data CRC digest. 32 bit CRC Digest, if the device supports CRC32-ISO3309. Otherwise 16 bit CRC digest, using polynomial CRC16-CCITT. Configuration to be used for CRC calulation: 1. Polynomial should be as per the chosen standard, 2. Input reflected, 3. Output reflected, 4. Initial value should be 0xFFFFFFFF, 5. Final XOR value should be 0x0. |
BSLCONFIGID is shown in Figure 1-47 and described in Table 1-56.
Return to the Summary Table.
Configuration ID of BSL Structure
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| CONFIG | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | CONFIG | R/W | 0h | Configuration ID of BSL Structure |
BSLPINCFG0 is shown in Figure 1-48 and described in Table 1-57.
Return to the Summary Table.
BSL UART PIN Configuration. The reset value of these fields differ for each device, based on the pins used.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| UARTTX_MUX_SEL | UARTTX_PAD_NUM | ||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| UARTRX_MUX_SEL | UARTRX_PAD_NUM | ||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-24 | UARTTX_MUX_SEL | R/W | 0h | UART TX IOMUX PINCM mux selection. |
| 23-16 | UARTTX_PAD_NUM | R/W | 0h | UART TX IOMUX PINCM register |
| 15-8 | UARTRX_MUX_SEL | R/W | 0h | UART RX IOMUX PINCM mux selection |
| 7-0 | UARTRX_PAD_NUM | R/W | 0h | UART RX IOMUX PINCM register |
BSLPINCFG1 is shown in Figure 1-49 and described in Table 1-58.
Return to the Summary Table.
BSL I2C PIN Configuration. The reset value of these fields differ for each device, based on the pins used.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| I2CSCL_MUX_SEL | I2CSCL_PAD_NUM | ||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| I2CSDA_MUX_SEL | I2CSDA_PAD_NUM | ||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-24 | I2CSCL_MUX_SEL | R/W | 0h | I2C SCL IOMUX PINCM mux selection |
| 23-16 | I2CSCL_PAD_NUM | R/W | 0h | I2C SCL IOMUX PINCM register |
| 15-8 | I2CSDA_MUX_SEL | R/W | 0h | I2C SDA IOMUX PINCM mux selection |
| 7-0 | I2CSDA_PAD_NUM | R/W | 0h | I2C SDA IOMUX PINCM register |
BSLCONFIG0 is shown in Figure 1-50 and described in Table 1-59.
Return to the Summary Table.
BSL invoke pin configuration and memory read-out policy.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
| READOUTEN | |||||||
| R/W-0h | |||||||
| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| READOUTEN | |||||||
| R/W-0h | |||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| RESERVED | BSLIVK_GPIOPORT | BSLIVK_GPIOPIN | |||||
| R-0h | R/W-0h | R/W-0h | |||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| BSLIVK_LVL | RESERVED | BSLIVK_PAD_NUM | |||||
| R/W-0h | R-0h | R/W-0h | |||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | READOUTEN | R/W | FFFFh | Sets the memory read-out policy for the BSL interface
|
| 15-14 | RESERVED | R | 0h | |
| 13 | BSLIVK_GPIOPORT | R/W | 0h | The BSL_invoke GPIO port index corresponding to the pad used for BSL_invoke
|
| 12-8 | BSLIVK_GPIOPIN | R/W | 0h | The BSL_invoke GPIO pin index corresponding to the pad used for BSL_invoke. Valid values are 0 to 31. |
| 7 | BSLIVK_LVL | R/W | 1h | The BSL_invoke input logic level which shall invoke the BSL
|
| 6 | RESERVED | R | 0h | |
| 5-0 | BSLIVK_PAD_NUM | R/W | 40h | The IOMUX PINCM register corresponding to the pad to be used for BSL_invoke |
PWDBSL[y] is shown in Figure 1-51 and described in Table 1-60.
Return to the Summary Table.
SHA2-256 Digest of BSL password.
Offset = 41C00110h + (y * 4h); where y = 0h to 7h
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| DIGEST | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | DIGEST | R/W | 0h | SHA2-256 Bit Digest of BSL access Password of size 256 bit. The hash of the default password (all 1's of 256 bit password) is stored here by default when devices are shipped from factory. |
BSLPLUGINCFG is shown in Figure 1-52 and described in Table 1-61.
Return to the Summary Table.
Defines the presence and type of a BSL plug-in in MAIN flash memory.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| SRAMUSED | FLASHPLUGINEXISTS | ||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| PLUGINTYPE | |||||||||||||||
| R/W-0h | |||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-24 | SRAMUSED | R/W | FFh | SRAM consumed by Flash plugin, from 0x00 to 0xFF. |
| 23-16 | FLASHPLUGINEXISTS | R/W | FFh | The field tells if Flash Plugin exists are not
|
| 15-0 | PLUGINTYPE | R/W | FFFFh | The Plugin type specifies which interface plugin is added in Flash. When the same interface is supported by ROM Bootloader, then ROM interface will be overridden with the Flash interface. If the same interface as in ROM BSL should be added as an additional interface without overriding ROM interface, a new value that is not part of this list should be chosen.
|
BSLPLUGINHOOK[y] is shown in Figure 1-53 and described in Table 1-62.
Return to the Summary Table.
Function pointers for plug-in init, receive, transmit, and de-init functions.
Offset = 41C00134h + (y * 4h); where y = 0h to 3h
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| BSLPLUGININIT | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 127-96 | BSLPLUGINDEINIT | R/W | FFFFFFFFh | Function pointer for the Deinit API |
| 95-64 | BSLPLUGINSEND | R/W | FFFFFFFFh | Function pointer for the Send API |
| 63-32 | BSLPLUGINRECEIVE | R/W | FFFFFFFFh | Function pointer for the Receive API |
| 31-0 | BSLPLUGININIT | R/W | FFFFFFFFh | Function pointer for the Init API |
BSLCONFIG1 is shown in Figure 1-54 and described in Table 1-63.
Return to the Summary Table.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| ALTBSLCONFIG | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | ALTBSLCONFIG | R/W | FFFFFFFFh | Controls the invocation of alternate BSL in main flash region.
|
SBLADDRESS is shown in Figure 1-55 and described in Table 1-64.
Return to the Summary Table.
Address of an alternate BSL.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| ADDRESS | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | ADDRESS | R/W | FFFFFFFFh | Address of the alternate BSL, if present. |
BSLAPPVER is shown in Figure 1-56 and described in Table 1-65.
Return to the Summary Table.
Address of the application version word.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| ADDRESS | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | ADDRESS | R/W | FFFFFFFFh | Address of the application version word (must be a valid flash address to be returned). If the given flash address is not programmed, then 0h will be returned. |
BSLCONFIG2 is shown in Figure 1-57 and described in Table 1-66.
Return to the Summary Table.
Configures the BSL Alert Configuration and I2C Target address of BSL.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| I2CTARGETADDR | ALERTACTION | ||||||||||||||||||||||||||||||
| R/W-0h | R/W-0h | ||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | I2CTARGETADDR | R/W | 48h | I2C target address to be used for the ROM BSL I2C communication. |
| 15-0 | ALERTACTION | R/W | FFFFh | Action to take upon a security alert condition.
|
BSLCRC is shown in Figure 1-58 and described in Table 1-67.
Return to the Summary Table.
CRC digest of the BSL_CONFIG portion of the NONMAIN memory.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| DIGEST | |||||||||||||||||||||||||||||||
| R/W-0h | |||||||||||||||||||||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-0 | DIGEST | R/W | 0h | BSL configuration data CRC digest. 32 bit CRC Digest, if the device supports CRC32-ISO3309. Otherwise 16 bit CRC digest, using polynomial CRC16-CCITT. Configuration to be used for CRC calulation: 1. Polynomial should be as per the chosen standard, 2. Input reflected, 3. Output reflected, 4. Initial value should be 0xFFFFFFFF, 5. Final XOR value should be 0x0. |