Tool/software:
I've seen guidance on e.g. the CCS Users Guide Launch Configurations section on editing the launch configuration to support a project-less multi-core debug.
However, is there a way to edit the launch configuration to make use of existing separate projects for each core?
I have my projects structured at the top level of my workspace directory as such:
`My Workspace`
- `CPU1` (Project for CPU1 core)
- `BuildConf1` (Build Configuration 1, contains the "CPU1.out" file for this build configuration)
- `BuildConf2` (Build Configuration 2, contains the "CPU1.out" file for this build configuration)
- `CPU2` (Project for CPU2 core)
- `BuildConf1` (Build Configuration 1, contains the "CPU2.out" file for this build configuration)
- `BuildConf2` (Build Configuration 2, contains the "CPU2.out" file for this build configuration)
And currently, the below `launch.json` file.
{ "version": "0.2.0", "configurations": [ { "name": "CPU1", "type": "ccs-debug", "request": "launch", "projectInfo": { "name": "CPU1", "resourceId": "/CPU1" }, "groupInfo": [ { "name": "group_0", "syncMode": false, "cores": [ "Texas Instruments XDS2xx USB Debug Probe_0/C28xx_CPU1", "Texas Instruments XDS2xx USB Debug Probe_0/C28xx_CPU2" ] } ] } ] }
What changes would I need to make here to ensure that both `CPU1` and `CPU2` projects are auto-loaded onto their respective cores, using their currently selected build configurations, at the start of a debug session?
Thank you!