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
A region of flash memory can be configured for read-execute protection - read and instruction fetch accesses to this region will return an error. CPU, DMA and debugger accesses are all treated the same way. This is configured by writing to the SYSCTL.SECCFG.FRXPROTMAINSTART and SYSCTL.SECCFG.FRXPROTMAINEND registers with the start and end addresses of the range to be protected respectively. Both addresses are set up for writing at 64B granularity. To enable this protection, the FLRXPROT bit must be ENABLED (1) by writing to SYSCTL.SECCFG.FWENABLE register along with the correct KEY value (0x76).
At any time, status of the RX protection can be obtained by reading the SYSCTL.SECCFG.SECSTATUS register. The FLRXPROT field provide this status.
This mechanism is useful in scenarios where it may be required to prevent re-execution of the CSC. The protected address range of the CSC essentially runs only once at BOOTRST and can not subsequently be re-executed. Note that caution needs to be exercised in configuring the flash memory range that is configured for this protection. Address space that holds the interrupt vectors or the portion of CSC that needs to be able to run a second time after BOOTRST should not be execute-protected.