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.

TMS320F28388D: Debug multi-core on F28388D with CCS 20.x

Part Number: TMS320F28388D

Tool/software:

I have a project using CPU1 and CM. Each codebase is on separated folders: 

.
├── README.md
├── cm
│   ├── CM_FLASH
│   │   ├── ...
│   │   └── cm.out
│   └── cmd
│       └── flash.cmd
├── cpu1
│   ├── Debug
│   │   ├── ...
│   │   └── cpu1.out
│   └── cmd
│       └── flash.cmd
├── debug.launch
├── shared
│   ├── .../.cpp
│   └── .../.hpp
├── sw-motion.yaml
└── target.ccxml

With CCS 12.x I can manage a debug configuration that would:

  • Build both subprojects
  • Load the flash on each cores
  • Start with initial breakpoint

With CCS 20.x it doesn't work the same. I opened as workspace the root folder which contains the two subprojects. I can build each subproject successfully, but I did not find how to configure the launch. 

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "cm+cpu1",
            "type": "ccs-debug",
            "request": "launch",
            "groupInfo": [
                {
                    "name": "group",
                    "cores": [
                        "cm",
                        "cpu1"
                    ],
                    "syncMode": true
                }
            ],
            "targetConfig": "$(cwd)/target.ccxml"
        },
        {
            "name": "cm",
            "type": "ccs-debug",
            "request": "launch",
            "projectInfo": {
                "name": "motion-cm",
                "resourceId": "/motion-cm"
            }
        },
        {
            "name": "cpu1",
            "type": "ccs-debug",
            "request": "launch",
            "projectInfo": {
                "name": "motion-cpu1",
                "resourceId": "/motion-cpu1"
            }
        }
    ]
}

I don't find how to properly setup this launch.json.