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.2 Version Mismatch

In Figure 5-1, the error message Update Required shows because of the version mismatch between the MCU SDK version and Sysconfig tool. The cliArgs used in the syscfg file is not correct and hence the tool reports errors while opening GUI view.

Version Mismatch Figure 5-1 Version Mismatch

To resolve the above issue, make sure the correct version of SysConfig is being used as mentioned in the MCU SDK documentation. Check the product.json file provided in the MCU SDK for version details.

In the previous example, SysConfig v1.23.0 and MCU+SDK v11.00 are used. The cliArgs used in the example.syscfg file are as follows which has incorrect MCU SDK version.

/** * These arguments were used when this file was generated. They will be automatically applied on subsequent loads * via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments. *
                @cliArgs --device "AM64x" --part "Default" --package "ALV" --context "r5fss0-0" --product "MCU_PLUS_SDK@07.03.01" * @v2CliArgs --device "AM6442" --package "FCBGA (ALV)" --variant "AM6442-D" --context "r5fss0-0" --product
                "MCU_PLUS_SDK@07.03.01" * @versions {"tool":"1.21.2+3837"} */

After modifying the above cliArgs to have correct MCU SDK version in the example.syscfg file, the tool works as expected.

/** * These arguments were used when this file was generated. They will be automatically applied on subsequent loads * via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments. *
                @cliArgs --device "AM64x" --part "Default" --package "ALV" --context "r5fss0-0" --product "MCU_PLUS_SDK_AM64x@11.00.00" * @v2CliArgs --device "AM6442" --package "FCBGA (ALV)" --variant "AM6442-D" --context "r5fss0-0" --product
                "MCU_PLUS_SDK_AM64x@11.00.00" * @versions {"tool":"1.21.2+3837"} */

Other issues can show device variant not found, package/part number not found, and so on. See Figure 5-2, Figure 5-3, and Figure 5-4, for details.

Device Not Found Figure 5-2 Device Not Found
Package Not Found Figure 5-3 Package Not Found
Unknown Context Specified Figure 5-4 Unknown Context Specified

All the previous parameters must be correctly passed in the cliArgs of example.syscfg file. Passing incorrect argument will lead to one of the issues specified above.

If the user is still confused about what parameters to use in cliArgs, open the CodeGen tool with MCU SDK selected as software product and copy the cliArgs from the generated untitled.syscfg file.

SysConfig CodeGen cliArgs Figure 5-5 SysConfig CodeGen cliArgs