SLUUDG7 December   2025 MSPM33C321A

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Overview of Security Functionality
    1. 1.1 Terminology
  5. 2Secure Execution Environment
    1. 2.1 TrustZone
      1. 2.1.1 Implementation Defined Attribution Unit
      2. 2.1.2 Security Attribution Unit
      3. 2.1.3 TrustZone software development
    2. 2.2 Memory Protection Unit
      1. 2.2.1 TrustZone and MPU
    3. 2.3 Global Security Controller
      1. 2.3.1 GSC Memory configuration
        1. 2.3.1.1 Security Exceptions through the GSC & SAU
        2. 2.3.1.2 Priviledge exceptions with GSC & MPU
  6. 3Security Modules
    1. 3.1 AES
      1. 3.1.1 AES Overview
      2. 3.1.2 AES Usage
        1. 3.1.2.1 Configuration
        2. 3.1.2.2 Setup
        3. 3.1.2.3 Operation
    2. 3.2 Keystore
      1. 3.2.1 Overview
      2. 3.2.2 Keystore Usage
        1. 3.2.2.1 Configuration
        2. 3.2.2.2 Setup
        3. 3.2.2.3 Operation
    3. 3.3 SHA2
      1. 3.3.1 SHA Introduction
        1. 3.3.1.1 SHA features
      2. 3.3.2 SHA Performance
      3. 3.3.3 SHA Usage
        1. 3.3.3.1 Configuration
        2. 3.3.3.2 Setup
        3. 3.3.3.3 Operation
    4. 3.4 PKA
      1. 3.4.1 PKA Introduction
        1. 3.4.1.1 PKA features
      2. 3.4.2 PKA Usage
        1. 3.4.2.1 Configuration
        2. 3.4.2.2 Setup
        3. 3.4.2.3 Operation
    5. 3.5 PQC
      1. 3.5.1 ML-DSA
        1. 3.5.1.1 ML-DSA Introduction
        2. 3.5.1.2 ML-DSA Usage
          1. 3.5.1.2.1 Configuration
          2. 3.5.1.2.2 Setup
          3. 3.5.1.2.3 Operation
  7. 4Revision History

2.3.1.2 Priviledge exceptions with GSC & MPU

The GSC and MPU can be used together to define regions of memory as priviledge or unpriviledge similar to how the GSC and SAU define regions of memory as secure or non-secure. This allows the programmer to add another layer of protection on regions of memory by using priviledge access. Due to the priviledge state also changing with exceptions occuring make sure priviledge access is expected when an interrupt occurs.

Use Table 2-2 to determine which fault will occur first when using the GSC and MPU to attribute regions of memory as priviledge or unpriviledge.

Table 2-2 Priviledge exception based on GSC and MPU priviledge attributions
Processor State MPU Privilege Attribution GSC Privilege Attribution Resulting Interrupt Access violation
Privilege Privilege Privilege None None
Unprivilege Privilege Privilege MemMange fault Yes blocked by CPU
Privilege Privilege Unprivilege None None
Unprivilege Privilege Unprivilege MemMange fault Yes blocked by CPU
Privilege Unprivilege Privilege None None
Unprivilege Unprivilege Privilege Priviledge NMI Yes blocked by GSC
Privilege Unprivilege Unprivilege None None
Unprivilege Unprivilege Unprivilege None None