SLAAE29A January 2023 – December 2025 MSPM0C1105 , MSPM0C1106 , MSPM0G1105 , MSPM0G1106 , MSPM0G1107 , MSPM0G1505 , MSPM0G1506 , MSPM0G1507 , MSPM0G1518 , MSPM0G1519 , MSPM0G3105 , MSPM0G3106 , MSPM0G3106-Q1 , MSPM0G3107 , MSPM0G3107-Q1 , MSPM0G3505 , MSPM0G3506 , MSPM0G3506-Q1 , MSPM0G3507 , MSPM0G3507-Q1 , MSPM0G3518 , MSPM0G3518-Q1 , MSPM0G3519 , MSPM0G3519-Q1 , MSPM0L1105 , MSPM0L1106 , 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
| Term | Meaning |
|---|---|
| NONMAIN | A dedicated flash memory region which configures device boot related parameters. See MSPM0 NONMAIN FLASH Operation Guide for NONMAIN operation guide. |
| Secure Boot | The process of verifying and validating the integrity and authenticity of updateable firmware and software components as a pre-requisite to the execution. |
| INITDONE | INITDONE is a register in some MSPM0 devices that is used to isolate privileged state and unprivileged state. INITDONE is triggered at the end of the privileged state by the CSC and all non-static security policies configured in CSC will take effect during INITDONE. |
| Customer Secure Code (CSC) | A secure boot solution provided in MSPM0 SDK for the devices with INITDONE mechanism. It works as part of root of trust and keeps immutable after production and achieves application image integrity and authenticity verification as well as other security policy configuration. CSC could also represent a MSPM0 hardware feature which means a MSPM0 device supports INITDONE mechanism. |
| Boot Image Manager (BIM) | A secure boot solution provided in MSPM0 SDK for devices without INITDONE mechanism. |
| Root of Trust (RoT) | Especially refers to immutable Root of Trust, the most trusted security component on the device. It is inherently trusted because it cannot be modified following manufacture. There is no software at a deeper level that can verify that it as authentic and unmodified. Including ROM-boot code and CSC with static write protection in CSC solution. |
| Keystore | Secure storage for AES key. Only CSC can configure keys into Keystore and the main application can configure the crypto engine (AES) to use one of the stored keys but can never access any stored keys. |
| Firewall | A dynamic protection mechanism for some specific region of Flash memory, including write protection, read-execute protection and IP protection. |
| Bank Swap | A mechanism to configure flash bank address mapping on MSPM0 dual-bank devices. It is configured in CSC and takes effects after INITDONE. |
| Static Write Protection | The static write protection mechanism enabled by NONMAIN configuration. The protected region could not be modified after ROM-boot code finished unless the NONMAIN configuration is changed for enabling writing again. |
| SHA2-256 | The hashing algorithm which takes an entire message and condenses it into a fixed-length (256bit) digest. It is used for verifying message integrity. Only supported via software in MSPM0 devices. |
| ECDSA P256 | An asymmetric algorithm to verifymessage authenticity. Only supported via software in MSPM0 devices. |
| AES | Advanced Encryption Standard, some MSPM0 devices offer hardware accelerators for AES. |
| TRNG | True Random Number Generator, some MSPM0 devices offer hardware accelerators for TRNG. |