• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 537 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/LAUNCHXL-CC1352R1: Lock syscfg to build configuration

fel
Intellectual 300 points
Part Number: LAUNCHXL-CC1352R1


Tool/software: Code Composer Studio

Hello,

For the product I am currently working on we need to have multiple versions of the .syscfg file for mapping the GPIO pins on different hardware. We would like to keep everything in the same CCS project as they all use the same code base and only differ in how the pins are routed. I have previously accidentally enabled the resource locking feature that binds a file's content to a specific build configuration, which puts a small key icon in the project file tree. However, I am having a hard time figuring out how to do this now that I actually want to use this feature.

I tried to go through the CCS documentation; however, I did not find what I was looking for. Does anyone know how to enable this feature to lock the file contents in particular build configuration? Or is there a better approach to achieve this?

Regards,

Felix.

  • 0
    TI__Guru**** 162455 points

    Felix,

    One way of doing this is to have 2 syscfg files in the project and then to exclude them based on the build configuration.  The project system allows you to exclude source files on a per build configuration basis.  However you can right click on a file and select to exclude it.  This will exclude the file from the current build configuration.

    Here I have imported an example from the SDK.  I added a second build configuration called Release.  I then copied the .syscfg file and added the copy to the project.  When I did that CCS automatically excluded the old file from the build.

    Lets say that I want the original file to be used in my "Debug" build configuration and the new copy in my "Release" build configuration.  

    Currently the Debug configuration is active so I would right click on the buttonled2.syscfg file and exclude it.  I would then right click on the original buttonled.syscfg and uncheck the exclude option.

    No for the debug configuration things are as I want them.

    I then switch to the Release configuration and to the reverse:

    Can you show me the icon with the key on it?  Does it look like this?  Typically that indicates that there are file specific build options set.  

    I made this show up by right clicking on the .syscfg file and changing the build options.  File specific options apply more to .c file as you have your build settins defined at the project level and then you can change them on a per file basis as well.  

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 300 points

    Hello John,

    Thank you very much. Using two syscfg files will do just fine for what I am working on.

    And yes, that key icon is what I was referring to in my question.

    Regards,

    Felix.