This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

[FAQ] How to use Sysconfig with CC32XXMOD devices?

Other Parts Discussed in Thread: SYSCONFIG, CC3235MODSF

Problem: Currently, online Sysconfig does not generate the correct source files for CC32XXMOD devices. Customers who try to use the ti_drivers_config files for MOD devices generated by Sysconfig will get build errors when they try to compile their project.

The fix for this issue is expected to be released Q1 SDK - specifically the generation of source files for MOD devices. Further enhancements will be made to our SW for MOD devices in Q2 SDK.

  • Workaround for CC32XX SDK v3.x: Select the non-MOD counterpart (e.g. if using CC3235SFMOD select CC3235SF) to work off of and refer to table 4-1 in the datasheet for the device you selected. Table 4-1 tells you the equivalent non-MOD pin numbers (CC32XX Device Pin No. column) for every corresponding module pin (Module Pin column). For example: if you want to use module pin 9 (GPIO12) as SCL for I2C, the equivalent selection in non-MOD would be pin 3 as the table shows. Do this for all sysconfig selections and the generated file will build without error.

    NOTE: If you're just trying to run an SDK example for a MOD device, it is not necessary to generate ti_driver_config files for MOD devices. SDK examples work for MOD devices as well and do not require any changes for this. If you're trying to make Sysconfig changes to an SDK example refer to table 4-1 in the datasheet as explained above.

    For CC32XX SDK v4.10+: The 4.10 version of the CC32XX SDK added MOD board data for Sysconfig. If you are using a MOD device follow the steps below so that Sysconfig is using the appropriate data for your MOD device. 

    1. Assuming you have imported an example from the CC32XX SDK, right click the Sysconfig example file and select open with->text editor
    2. You then need to modify the cliArgs to reference the MOD board instead of the CC32XX device
      1. for example if using a CC3235MODSF device change the cliArgs to the following: "@cliArgs --board "/ti/boards/CC3235MODSF_LAUNCHXL"
    3. Save the changes and open with Sysconfig editor to see the changes reflect in the GUI

  • Thanks for the info Jesus!