LAUNCHXL-F28379D: How to flash both CPU programs using CCS Theia [led_ex1_blinky]

Lucas Malo Belanger

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: C2000WARE, SYSCONFIG

Tool/software:

I'm unsure how to flash both CPU programs using the led_ex1_blinky exercise example found in the DriverLib for the F28379D Microcontroller. The CPU1 program is running, but when I try to run the CPU2 program, neither LEDs blink.

I'm using Debug Project, then stopping the debugger to flash the program. I didn't find a way to flash both programs in one shot. Can anyone guide me for this?

Thanks.

I found this video but this is with the Eclipse version of CCS, hence it's not up to date.

https://www.ti.com/video/series/c2000-f2837xd-microcontroller-one-day-workshop-series.html?keyMatch=C2000%20workshop&tisearch=universal_search

over 1 year ago

0 Aishwarya Rajesh over 1 year ago

TI__Mastermind 21515 points

Hi Lucas,

CCS 20 is a VS Code based CCS, so while the IDEs look different from each other, they support the same basic debugging functionalities such as debug project. The example you are running is a single-core example designed to be run on CPU1. If you would like to run examples on CPU2, you will have to transfer ownership of the peripheral to CPU2, etc. Please refer to the multi-core examples present in C2000Ware on how to do this in your code.

These E2Es also serve as a helpful resource for this process:

(+) CCS/TMS320F28379D: How to combine the CPU1 and CPU2 firmware together - C2000 microcontrollers forum - C2000︎ microcontrollers - TI E2E support forums

(+) TMS320F28388D: How to debug CPU2 only? - C2000 microcontrollers forum - C2000︎ microcontrollers - TI E2E support forums

Best Regards,

Aishwarya

0 Lucas Malo Belanger over 1 year ago in reply to Aishwarya Rajesh

Prodigy 40 points

Hi Rajesh.

I was talking about the blinky example in C2000Ware_5_01_00_00\driverlib\f2837xd\examples\dual\led.

led_ex2_sysconfig_cpu1.c and led_ex2_sysconfig_cpu2.c seem to take care of the synchronisation between the 2 cpus. My question is how to debug with both cpus flashed correctly as I seem to be only able to flash one cpu at a time.

Thanks.

0 Aishwarya Rajesh over 1 year ago

TI__Mastermind 21515 points

Lucas,

Refer to this E2E for more information: (+) TMS320F28379D: Debugging: auto-connect and flashing of all cores - C2000 microcontrollers forum - C2000︎ microcontrollers - TI E2E support forums

Best Regards,

Aishwarya

0 Lucas Malo Belanger over 1 year ago in reply to Aishwarya Rajesh

Prodigy 40 points

Those examples work fine with the Eclipse version of CCS, but the GUI changed with the Theia version. I'm searching for a way to do the same thing as described in your link in CCS Theia.

0 Aishwarya Rajesh over 1 year ago

TI__Mastermind 21515 points

Lucas,

Understood. The process is actually pretty simple on CCS Theia / 20 using the concept of a launch.json file. More information here on this: 7.1. Debug Overview — Code Composer Studio Theia 1.5.0 Documentation. These are the steps to create a configuration for an example that flashes both CPUs at the same time and can be replicated to be used with any software example:

Import example.
Right click on 'led_ex1_blinky_cpu1' > Debug Project.
In the 'Debug Core Selection' pop up, select both cores to load the program onto and press 'OK'. It is up to you if you want to remember this selection for every launch of this project or not. NOTE: This pop up will show up in the first launch of a new project and/or if you do not select the 'Remember my selection' button.

The launch configuration in the launch.json will now look something like this:

{
            "name": "led_ex1_blinky_cpu1",
            "type": "ccs-debug",
            "request": "launch",
            "projectInfo": {
                "name": "led_ex1_blinky_cpu1",
                "resourceId": "/led_ex1_blinky_cpu1"
            },
            "launchSettings": {
                "coresToLoadForProjectLaunch": [
                    "C28xx_CPU1",
                    "C28xx_CPU2"
                ]
            }
        }

At this point, CCS will load the program onto and halt the cores. Run program.

Best Regards,

Aishwarya

0 Lucas Malo Belanger over 1 year ago in reply to Aishwarya Rajesh

Prodigy 40 points

I've tried what you indicated, but this loads the same program on both CPUs. How do I specify a different program for each CPU?

0 Aishwarya Rajesh over 1 year ago

TI__Mastermind 21515 points

Lucas,

Let me get back to you tomorrow on this matter.

Best Regards,

Aishwarya

0 Aishwarya Rajesh over 1 year ago

TI__Mastermind 21515 points

Lucas,

I believe you can use that same launch.json file to take care of that. Let me connect you with the CCS folks for further comment.

Best Regards,

Aishwarya

0 Ki over 1 year ago in reply to Lucas Malo Belanger

TI__Guru**** 486221 points

Lucas Malo Belanger said:
I've tried what you indicated, but this loads the same program on both CPUs. How do I specify a different program for each CPU?

Please take a look at section 7.2.2: https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs/ccs_debug-main.html#launch-configurations

You can specify a connections object that defines multiple cores objects, one for each core. Each core object can have a program property which specifies the program to load for that core. The cores object for CPU1 would can specify the program to load for CPU1 and the cores object for CPU2 would have the same for CPU2. See the last screenshot in the section for example usage for the connections, cores, and program objects/properties.

0 Ki over 1 year ago in reply to Ki

TI__Guru**** 486221 points

Ki said:
You can specify a connections object that defines multiple cores objects, one for each core. Each core object can have a program property which specifies the program to load for that core. The cores object for CPU1 would can specify the program to load for CPU1 and the cores object for CPU2 would have the same for CPU2. See the last screenshot in the section for example usage for the connections, cores, and program objects/properties.

Here is an example:

       {
            "name": "LAUNCHXL-F28379D.ccxml",
            "type": "ccs-debug",
            "request": "launch",
            "targetConfig": "/c:/Users/xxxxxxx/ti/CCSTargetConfigurations/LAUNCHXL-F28379D.ccxml",
            "connections": [
                {
                    "name": "Texas Instruments XDS100v2 USB Debug Probe",
                    "cores": [
                        {
                            "name": "C28xx_CPU1",
                            "program": "C:/Users/xxxxxxx/workspace_ccstheia2/led_ex1_blinky_cpu1/CPU1_RAM/led_ex1_blinky_cpu1.out"
                        },
                        {
                            "name": "C28xx_CPU2",
                            "program": "C:/Users/xxxxxxx/workspace_ccstheia2/led_ex1_blinky_cpu2/CPU2_RAM/led_ex1_blinky_cpu2.out"
                        }
                    ]
                }
            ]
        }

0 Lucas Malo Belanger over 1 year ago in reply to Ki

Prodigy 40 points

I've tried the config file with the two connections as mentionned above but it still loads the led_ex1_blinky_cpu1.out program on both CPUs. Here are the steps I'm doing for launching the program:

Click on the green arrow with the bug
It asks for which core to load the program on. I select both and click OK.
When I see the debug tab, I see that the call stack of the CPU2 is on led_ex1_blinky_cpu1.c, which should not be the case

I've attached both projects in a .zip, maybe there is something wrong with the project configuration files?

Thanks and happy new year!

led_ex1_blinky_dual.zip

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "led_ex1_blinky_dual",
            "type": "ccs-debug",
            "request": "launch",
            "projectInfo": {
                "name": "led_ex1_blinky_cpu1",
                "resourceId": "/led_ex1_blinky_cpu1"
            },
            "targetConfig": "led_ex1_blinky_cpu1/targetConfigs/TMS320F28379D.ccxml",
            "groupInfo": [
                {
                    "name": "group_0",
                    "syncMode": true,
                    "cores": [
                        "Texas Instruments XDS100v2 USB Debug Probe/C28xx_CPU1",
                        "Texas Instruments XDS100v2 USB Debug Probe/C28xx_CPU2"
                    ]
                }
            ],
            "connections": [
                {
                    "name": "Texas Instruments XDS100v2 USB Debug Probe",
                    "cores": [
                        {
                            "name": "C28xx_CPU1",
                            "program": "led_ex1_blinky_cpu1/CPU1_RAM/led_ex1_blinky_cpu1.out"
                        },
                        {
                            "name": "C28xx_CPU2",
                            "program": "led_ex1_blinky_cpu2/CPU2_RAM/led_ex1_blinky_cpu2.out"
                        }
                    ]
                }
            ],
        }
    ]
}

+1 Ki over 1 year ago in reply to Lucas Malo Belanger

TI__Guru**** 486221 points

It looks like you are using a launch for a project session. Please use a project-less debug session.

0 Lucas Malo Belanger over 1 year ago in reply to Ki

Prodigy 40 points

When I try to remove the projectInfo field in the launch.json, it complains that the project does not have a target configuration file. How can I be outside of a project when clicking the green debug button?

0 Ki over 1 year ago in reply to Lucas Malo Belanger

TI__Guru**** 486221 points

Please do a project-less (manual) launch for a ccxml file. This will create a launch for that ccxml file. It is with this launch that you can modify to load separate *.out files for each CPU.

0 Lucas Malo Belanger over 1 year ago in reply to Ki

Prodigy 40 points

This seems to resolve my issue. I have some concerns about this method though:

The launch config for the debug less is in the .theia folder of the workspace. I had to open the file explorer and go drag the file in Theia because it was a hidden folder.
I have to put absolute paths to the executables, which is bad for code portability. Is there any other method of doing so with only using relative paths?

Thanks for all your help!

+1 Ki over 1 year ago in reply to Lucas Malo Belanger

TI__Guru**** 486221 points

Lucas Malo Belanger said:
The launch config for the debug less is in the .theia folder of the workspace. I had to open the file explorer and go drag the file in Theia because it was a hidden folder.

There is a button to open the launch.json file in the Debug view:

https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs/ccs_debug-main.html#debug-view

It looks like a little gear icon:

Lucas Malo Belanger said:
I have to put absolute paths to the executables, which is bad for code portability. Is there any other method of doing so with only using relative paths?

It is possible to use variables. ${workspaceFolder} is likely the most useful one and refers to the location of your workspace folder (CTRL+SPACE bring up the auto-complete suggestions):

Thanks

C2000™︎ microcontrollers

C2000 microcontrollers forum

LAUNCHXL-F28379D: How to flash both CPU programs using CCS Theia [led_ex1_blinky]