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.

CCSTUDIO: How to Change Target Configuration File Via Build Configuration?

Part Number: CCSTUDIO
Other Parts Discussed in Thread: SYSCONFIG

Hello,

I have a project that I am using to program two different devices: F28379D and F28374S. I have created multiple Build Configurations which set various predefined symbols depending which target device is being programmed.

But I still have one question. I have two custom Target Configuration files that I have created (one for each target device). I need the appropriate Target Config file to be set as "Active" depending on which Build Config is selected. How can I automatically set the Active Target Config file for each Build Configuration?

Thank you in advance.

- Matthew

  • Hi Matthew,

    I need the appropriate Target Config file to be set as "Active" depending on which Build Config is selected. How can I automatically set the Active Target Config file for each Build Configuration?

    This is not supported for target configuration files.

    I have a project that I am using to program two different devices: F28379D and F28374S.

    This is not a typical use case. A device is specified at the project level and that typically remains fixed. Are you using the "Custom" or "Generic" option for the device? Most people have separate projects for different devices.

    ki

  • Hi Ki. Thank you for the response.

    Would manually assigning the target_config_active Build Variable to my desired Target Configuration file work?

    I'm not sure what you mean by "Custom" or "Generic." When I want to change processors, I have separate linker command files (that I include/exclude) and I manually set the corresponding Target Config file to "Active." Because the F28379D and F28374S are both in the F2837x family, I don't need to change anything else. It has been working fine for me, but I just wanted to automate the steps with a Build Configuration for each device.

    If I were to have different projects for each device, how I would share the same source files between multiple projects?

    Thanks,

    - Matthew

  • I'm not sure what you mean by "Custom" or "Generic.

    I was referring to:

    When you set it to a specific device, it will typically apply default settings for that device. Hence it is not recommended to then use that project for a different device (unless the variant is changed). But of course you can tweak the project settings to whatever you wish regardless of what device is selected as the variant.

    Would manually assigning the target_config_active

    I was experimenting around with this variable and it does not look like setting this will override what the CCS project will use. Engineering took a look and thinks this could potentially be a bug.

  • Hi Ki. Thanks for the response.

    I cannot select "Custom" or "Generic." As shown below, the option is greyed out for me. I don't know why.

  • I assume it is a sysconfig project. In this case you would need to change the variant in sysconfig.