SPRADK2A November   2024  – October 2025 F29H850TU , F29H859TU-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. Introduction
  5. Supplemental Online Information
  6. SSU Overview
  7. Key Concept Definitions
  8. Safety and Security Goals
  9. System Design
  10. 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. Debug Authorization
    1. 8.1 Password-Based Unlock
  12. 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

SSU Overview

The SSU is an integral part of the C29 CPU subsystem, providing context-sensitive memory protection and run-time code isolation, debug security, and secure firmware updates. The SSU acts as a firewall between the C29 CPU and the rest of the system, enforcing user access protection policies and managing debug access and Flash controller operations. Figure 3-1 shows a simplified overview of the SSU as integrated into the C29 subsystem. The features available in the SSU can be used to achieve true FFI in a real-time control system without adding software overhead, which can otherwise negatively impact real-time performance. With the SSU, system designers can combine multiple control and communication functions on the same CPU core, while keeping each function isolated from the others. This can lead to a reduction in the number of cores required to reach system goals, or help achieve higher system safety integrity levels.

 SSU System Block Diagram (Simplified View) Figure 3-1 SSU System Block Diagram (Simplified View)