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.1 Enabling System Security Configuration

The first step to enabling SSU functionality in an application is to add the System Security option in SysConfig, by clicking the (+) button to the right of the module name in the left bar, see Figure 7-1.

System Security Configuration Page Figure 7-1 System Security Configuration Page

In the System Security module, there are several configuration option groups. The first of these is the General Settings, which contains settings for SSU operation mode, UPP revision number, and cores enabled.

The System Security module also includes configuration options for selecting the device boot mode, configuring Flash update protections, debug passwords (Only visible when SSUMODE 3 is selected as the SSU Mode), and locking SSU registers. Some of these settings, such as debug passwords and Flash update owner settings, require SSUMODE3 operation to take effect.

When the System Security module is added in SysConfig, there are other modules that get automatically added such as the LINK, STACK, and Memory Region modules. There is no need to modify the LINK and STACK modules. All of the configuration is be done through the System Security module. The LINK and STACK modules simply provide a summary of the LINK and STACK configurations selected through the System Security module. The linker command file (.cmd) is also auto generated from SysConfig once the System Security module is added. If using an existing project, exclude the .cmd file from the project build to prevent conflicts.

Note: If extra modifications or additions need to be made to the linker command file, use the Memory Region and Sections modules within the Memory Configuration section of SysConfig.
Note: When the System Security module is first added in SysConfig, there is a warning that the CommonCodeModule_Link is not associated with a STACK/SANDBOX in the System Security module. To resolve this warning, go to the SANDBOX tab located within the SSU Setup of the System Security module and add a SANDBOX with CommonCodeModule_LINK selected as one of the Modules.