SLAU887 February 2023 MSPM0G1105 , MSPM0G1106 , MSPM0G1107 , MSPM0G1505 , MSPM0G1506 , MSPM0G1507 , MSPM0G3105 , MSPM0G3105-Q1 , MSPM0G3106 , MSPM0G3106-Q1 , MSPM0G3107 , MSPM0G3107-Q1 , MSPM0G3505 , MSPM0G3505-Q1 , MSPM0G3506 , MSPM0G3506-Q1 , MSPM0G3507 , MSPM0G3507-Q1 , MSPM0L1105 , MSPM0L1106 , MSPM0L1303 , MSPM0L1304 , MSPM0L1304-Q1 , MSPM0L1305 , MSPM0L1305-Q1 , MSPM0L1306 , MSPM0L1306-Q1 , MSPM0L1343 , MSPM0L1344 , MSPM0L1345 , MSPM0L1346
ROM Bootloader provides an option to use Custom Bootloader. To achieve this, load the custom bootloader in the Main flash memory and register it in the BSL configuration in Non-main Flash. When ROM BSL is invoked next time, it will check for the Secondary Bootloader configuration field and branches to it, and the control is not expected to return back to ROM BSL.
BSL mode configuration in the BCR configuration is applicable for Secondary BSL as well. When this setting is disabled, Secondary BSL will not be invoked.
The flash memory region where the Custom BSL is loaded should be write protected in the BCR configuration, to avoid unintended erase during the bootloading process. Non-main write protection is optional in case of Secondary bootloader use case. But the Secondary Bootloader pointer should be properly restored after erase.
Erasing the Secondary bootloader could cause a device lock up. Hence it is necessary to write protect the Secondary Bootloader memory region.