SDAA194 November   2025 AM2431 , AM2432 , AM2434 , AM62P , AM6412 , AM6421 , AM6422 , AM6441 , AM6442

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
    1. 1.1 SysConfig CodeGen Tool
  5. 2Getting Started Guide
    1. 2.1 How to Launch SysConfig (GUI and Command-Line)
    2. 2.2 Integration with CCS and Makefile builds
    3. 2.3 Location of SysConfig file in MCU SDK
      1. 2.3.1 Using Existing SysConfig File
      2. 2.3.2 Creating New SysConfig File
  6. 3Example Sysconfig in CCS
    1. 3.1 Example I2C Read
  7. 4Common Application Configuration
    1. 4.1 RAT Configuration
    2. 4.2 MPU Configuration
    3. 4.3 MMU Configuration
    4. 4.4 System Initialization
      1. 4.4.1 DPL Initialization
      2. 4.4.2 Clock Initialization
      3. 4.4.3 PinMux Configuration
      4. 4.4.4 Driver Initialization
      5. 4.4.5 Board Peripheral Initialization
  8. 5Output File
    1. 5.1 Files Generated by CodeGen Tool
      1. 5.1.1 Debugging and Troubleshooting
    2. 5.2 Version Mismatch
    3. 5.3 Resource Conflict
      1. 5.3.1 Pin Conflict
      2. 5.3.2 Module Instance Conflict
      3. 5.3.3 Multicore Resource Conflict
    4. 5.4 Unsupported Drivers
    5. 5.5 Use of Reserve Peripheral
  9. 6Disclaimers and Intended Use
  10. 7Summary
  11. 8References

6 Disclaimers and Intended Use

SysConfig core tool follows TI baseline quality development process. This means that there are no automotive or functional safety claims that can be made on code that is generated using SysConfig. The expectation is that it is the responsibility of the customer to perform standard qualification on generated code according to requirements of a particular standard.