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

5.1 Files Generated by CodeGen Tool

The CodeGen tool of SysConfig generates C source and header files which are used during the application development to avoid errors and boost productivity. This generated file can be directly imported to application for driver initialization & configuration.

The files generated are listed below.

  1. ti_dpl_config.h – contains the declaration for the DPL (Driver Porting Layer) initialization API.
  2. ti_dpl_config.c – contains the code for DPL initialization. The DPL initialization includes initializing the Interrupt Controller, MMU & RAT configurations, Debug Logs & System tick initialization. The DPL initialization is done using the Kernel Level API call by generated code.
  3. ti_drivers_config.h – contains the declaration for driver initialization APIs for all the configured drivers.
  4. ti_drivers_config.c - contains code for the initialization of the configured peripheral drivers, clock initialization, PinMux settings and driver initialization. This file also contains global handles for configured peripherals.
  5. ti_drivers_open_close.h – contains the declaration for drivers open/close API for configured peripheral along with required handler.
  6. ti_drivers_open_close.c - contains code to Open/Close the driver for configured peripheral. This file also contains the handler with configured parameters required by the added peripheral.
  7. ti_pinmux_config.c - contains the pinmux configuration required by the configured peripheral to achieve required functionality configured via GUI.
  8. ti_power_clock_config.c – contains the code to enable the clock and modify the clock frequency for configured peripheral. The generated code uses the TISCI calls to configure the clock frequency.
  9. ti_board_config.h – contains declaration for board specific driver configuration.
  10. ti_board_config.c – contains definition for board specific driver configuration.
  11. ti_board_open_close.h – contains declaration for board specific driver open/close APIs.
  12. ti_board_open_close.c – contains definition for board specific driver open/close APIs.
  13. ti_enet_config.h – contains the definition of all macros used by enet module.
  14. ti_enet_config.c – contains definition for global structure and APIs required to provide enet functionality.
  15. ti_enet_open_close.h - contains the declaration for enet open/close API along with the required utility API.
  16. ti_enet_open_close.c – contains the definition for enet open/close API along with required structure definition.
  17. ti_enet_soc.c – contains the definition for required structure and APIs for enet interrupt setup, clock frequency configuration and to set/get other necessary configurations.
  18. ti_enet_lwipif.h – contains declaration of enet Lwip interface layer for driver callback.
  19. ti_enet_lwipif.c - contains enet Lwip interface layer implementation for driver callback.