I'm currently dealing with a very annoying issue in CCS v6.1.1.00022. As background, I'm working on a project where I need to load debug code to a number of "modules", each of which has two Tiva processors daisy-chained over JTAG. I'm doing this debugging using an XDS100v2 probe.
The two processors on each module are running different code, so each module needs a custom Debug Configuration to load the proper program onto each processor. The issue is, after the program to load is hard-coded into the Debug Configuration, it decides to randomly reset the field to its default value (${build_artifact:project_name}) after seemingly unrelated activity.
Here's an example with two Debug Configurations for two modules. Let's say the module names are A and B, and the program being loaded onto each processor is given in square brackets (e.g. A[0] is loaded onto the first processor on A, and B[1] is loaded onto the second processor on B).
- A[0] is set to the default value, so I change it to the correct binary and hit Apply
- I switch the processor through the Device dropdown to check A[1]. It is loading the correct binary so I don't change anything.
- I click on the B config and the window shows B[1]. It's set to the default value, so I change it to the correct binary and hit Apply
- I change the device and check B[0] which is loading the correct binary
- I click on the A config and the window jumps to A[0], which has now gone back to the default value.
I've been able to work around this by closing every module's project (thereby hiding their Debug Configurations) and setting up the configs one by one as I open the projects. It seems jumping between Debug Configurations is what causes the problem.
As I was doing the final configuration, I noticed that the save location (under the Common tab) of a few of my configurations were actually in the wrong location. As an example, both A and B had the configuration saved as a shared file with the path \A\.launches. I've fixed this up now so each debug configuration is stored in the appropriate folder, but I thought I'd mention this.
Is this a known bug in the latest CCS version?
