SLAU846B June 2023 – November 2024 MSPM0G1105 , MSPM0G1106 , MSPM0G1107 , MSPM0G1505 , MSPM0G1506 , MSPM0G1507 , MSPM0G1519 , MSPM0G3105 , MSPM0G3105-Q1 , MSPM0G3106 , MSPM0G3106-Q1 , MSPM0G3107 , MSPM0G3107-Q1 , MSPM0G3505 , MSPM0G3505-Q1 , MSPM0G3506 , MSPM0G3506-Q1 , MSPM0G3507 , MSPM0G3507-Q1 , MSPM0G3519
In dual-bank/quad-bank devices, based on which bank (or pair) is executable, that bank (pair) gets read-execute privileges and loses write/erase privileges. The other bank (or pair) is readable, and writeable but not executable. This mechanism enforces the policy that any firmware update can only be saved in the writeable bank in the current session but can never be executed.
Upon a subsequent BOOTRST, the CSC runs and needs to authenticate the update and decide if the updated image should be made executable. If yes, then the bank holding the updated image can be configured to become executable (this is done by configuring the SYSCTL.SECCFG.FLBANKSWP.USEUPPER to 1 along with the correct KEY value of 0x58). When the CSC issues INITDONE, this bank-swap will take effect, swapping the execution/write privileges of the upper and lower banks as well as re-mapping the upper bank (or pair) to the lower half of the flash memory address space and re-mapping the upper bank (or pair) to the upper half of the flash memory address space.
Creating swappable configurations is a two-step process.
At any time, status of the bank swap policy and the currently executable bank can be obtained by reading the SYSCTL.SECCFG.SECSTATUS register. Fields FLBANKSWPPOLICY and FLBANKSWP provide this status.