AM2434: Multiple different sysconfig configurations in a CCS project

Hello Andy,

Which version of the SDK and SysConfig are you using?

I tested the renaming of a syscfg file and rebuilding initially with CCS 12.4 and mcu_plus_sdk_am243x_09_00_00_35 and did not see this issue so I want to setup your exact environment on my end.

Best Regards,

Ralph Jacobi

mcu_plus_sdk_am243x_08_06_00_45

Sysconfig 1.18.0.3266

Ideally it would be nice to have multiple syscfg files in the project and switch between them being active.

Hi Andrew,

So to answer the original question at hand here, you can have multiple SysConfig files associated with a specific project as long as you only have one 'included' at a time. The other SysConfig files that are not being used for the build must be 'excluded' by right clicking and selecting "Exlcude from Build'

When done it should look like this:

Regarding the issue you reported of this:

Andrew Kirby1 said:

any attempt to change the filename from 'example' results in a broken build. 

I have not been able to reproduce this issue at all and tried a number of different tactics while using the exact versions of the SDK, SysConfig, and CCS you have.

Can you try re-starting your Code Composer Studio instance? I've also rarely but occasionally seen making a new workspace clears up oddities with builds that are not replicable.

Best Regards,

Ralph Jacobi

Hello Andrew,

I see you've indicated that I haven't been able to fully resolve your issue, but without a follow-up on what part of my feedback has not helped I am not sure how to further advise on this.

Best Regards,

Ralph Jacobi

Just trying to do some further testing to get a handle on what's going wrong.

Here's where I am at:

Started with a working system using example.syscfg

I copied the example.sysfg file to two files alpha.syscfg and beta.syscfg

I did not modify the alpha and beta yet.

I removed the example.syscfg file in all the sub projects and made beta.syscfg excluded from the build

I rebuilt the project and subprojects.

No errors in build - I am hopeful...

But... I am now left with a project that doesn't work - I get 'Unable to access the DAP' errors when attempting to debug the solution.

I restored example.syscfg from version control in each of the subprojects and excluded both alpha.syscfg and beta.syscfg Filecompare shows it is the same as alpha and beta.

Rebuild and I get the same result - a non working project with 'Unable to access the DAP'.

Comparing the files, example.syscfg, alpha.syscfg and beta.syscfg are identical.

I pulled the entire project out of version control at the point prior to messing with this and it works fine. 

This seems to support our previous experience that using anything except the example.syscfg leads to a broken build.

Hello Andrew,

What hardware are you using and what process are you following to load the image(s) onto it? Asking both to see if there is anything that stands out but also so that I can follow the same process to see if I can re-create the DAP issue.

Best Regards,

Ralph Jacobi