SPRADK2A November   2024  – October 2025 F29H850TU , F29H859TU-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1 Introduction
  5. 2 Supplemental Online Information
  6. 3 SSU Overview
  7. 4 Key Concept Definitions
  8. 5 Safety and Security Goals
  9. 6 System Design
  10. 7 Configuring the SSU
    1. 7.1 Flash SECCFG Region
    2. 7.2 SSU Development Life Cycle
    3. 7.3 Using the SysConfig Tool
      1. 7.3.1 Enabling System Security Configuration
      2. 7.3.2 Configuring Application Modules
      3. 7.3.3 Configuring Special Modules
        1. 7.3.3.1 LINK2 Configuration
        2. 7.3.3.2 LINK1 Configuration
        3. 7.3.3.3 Common Code Link Configuration
      4. 7.3.4 Defining Sandboxes
      5. 7.3.5 Adding Shared Memory
  11. 8 Debug Authorization
    1. 8.1 Password-Based Unlock
  12. 9 Debugging the SSU
    1. 9.1 Debugging Build Errors
    2. 9.2 Debugging Runtime Errors
  13. 10SSU Frequently Asked Questions (FAQ)
  14. 11Summary
  15. 12References
  16. 13Revision History

7.3.5 Adding Shared Memory

Shared memory regions are special access protection regions (APRs) that are accessible by multiple application modules. In SysConfig, shared memories can be added by selecting the Shared Memory tab on the System Security page, and clicking the Add button. Multiple shared memories can be added, limited by the total number of APRs available on the CPU (including APRs that have been defined for the various Application Modules). For each shared memory, source files can be included; SysConfig adds the .bss, .data, .const, and .rodata sections from these files as configured. Custom section names can also be defined to be included.

For each shared memory, you can select which application modules require read-only permission, and which modules require write permission. SysConfig automatically configures the APR permissions as defined for the LINK for each module.

Shared Memory Configuration Example Figure 7-5 Shared Memory Configuration Example