• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 2889 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS: [CC3220S/SD4.10] How to upgrade sysconfig?

Eric Hsieh3
Intellectual 780 points

Other Parts Discussed in Thread: CC3220S, SYSCONFIG

Tool/software: Code Composer Studio

Hi TI,

We have a old project which was using old SDK with CC3220S_LAUNCHXL.c/h file.

Now, we use SDK 4.10. Is there a good way to upgrade sysconfig and CC3220S_LAUNCHXL.c/h from my project? Thanks. 

  • 0
    TI__Mastermind 31050 points

    Hi Eric,

    As I understand it, you have a software application based on older SDKs which used the LAUNCHXL.c/.h file approach for configuring pinmuxing and drivers and now you would like to migrate to the latest SDKs which support Sysconfig.

    Migration to Sysconfig is a manual process where you will have to edit a .sysconfig file to match the settings/requirements for the system. This is because the tool is currently a one-way process where scripts drive the generation of the source code based on the .sysconfig file. There is currently no mechanism for feeding settings in the source files back to the .sysconfig script.

    You have a couple options here:

    1.) Your existing LAUNCHXL.c/.h files can still be used in the application and should be compatible with the drivers. We include an example project in the drivers example folder of the SDK demonstrating this. The only thing to worry about in this case should be updates to drivers between versions. Should be minor if any at all.

    2.) Similar to (1), you can continue working directly with the source but rename your files to match the new generated files used in the sysconfig. The new convention is "ti_drivers_config.c/.h". Then you will effectively be working in the "sysconfig disabled" approach. See Task 8 in the Sysconfig SimpleLink Academy Training here: http://dev.ti.com/tirex/explore/node?node=AO3dBAhu05HBWXd.SPxt0g__fc2e6sr__LATEST&search=SysConfig%20Basics

    3.) Manually migrate configuration into Sysconfig. This is the recommended approach to simplify your development moving forward.

    Best Regards,

    Ben M

  • 0 in reply to Benjamin Moore
    Intellectual 780 points

    Hi Benjamin,

    Thanks. I will try to use manual migrate to try. Thanks a lot.