CCSTUDIO: Debugging two MCUs with two XDS110

Hannes Thielke

Prodigy 10 points

Part Number: CCSTUDIO

Hello,

I'm trying to debug two MCUs at the same time using two XDS110 on the same laptop. In CCS12, my method was:

Open two CCS instances
Start the first debug session
When this is finished, start the second debug session

This worked fine.

Now, in CCS20 I couldn't find out how to do this. At first, I tried setting the serial numbers of both XDS110 using "Xdsdfu" and writing these serial numbers into the target config. Then, from the same CCS instance, I tried flashing both one after the other, which resulted in this error:

So I tried opening a second CCS instance with a new workspace and starting the debug session from there, which resulted in this error when starting the 2nd session:

I also tried connecting the debuggers to different ports, but this didnt help.

How do I get this running?

Kind regards,

Hannes

3 months ago

0 Ki 3 months ago

TI__Guru**** 484671 points

Hello Hannes,

Hannes Thielke said:
Now, in CCS20 I couldn't find out how to do this. At first, I tried setting the serial numbers of both XDS110 using "Xdsdfu" and writing these serial numbers into the target config. Then, from the same CCS instance, I tried flashing both one after the other, which resulted in this error:

Have you followed the steps in: https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs/ccs_debug-main.html#xds110

The above is the procedure for launching a single debug session for multiple XDS110 targets. Yes, you are setting the serial numbers as needed. But are you also using a single debug session?

Hannes Thielke said:
So I tried opening a second CCS instance with a new workspace and starting the debug session from there, which resulted in this error when starting the 2nd session:

You can't have multiple debug instances of the same CCS installation. I recommend you use the technique mentioned above.

Thanks

0 Hannes Thielke 3 months ago in reply to Ki

Prodigy 10 points

Hello KI,

thanks for your answers.

The method described in your link uses a single target-config with two debug probes.

In my case, I have two different projects with two separate target-config files.

As soon as I start the second debug session, I get this error:

Should I create a single target-config instead?

But when I do, where do I define which project goes to which MCU?

0 Ki 3 months ago in reply to Hannes Thielke

TI__Guru**** 484671 points

You will not be able to run two simultaneous debug session with the same CCS instance. You have two options:

1. Do the below as you ask:

Hannes Thielke said:
Should I create a single target-config instead?

or:

2. Launch separate instances of CCS. Note that the instances cannot share the same workspace. When launching the second instance, pass in a workspace location different than the current instance. Your projects should be split between the two workspaces.

https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs/ccs_faqs.html#how-do-i-start-up-code-composer-studio-with-a-specific-workspace

Thanks

0 Hannes Thielke 2 months ago in reply to Ki

Prodigy 10 points

1. I tried creating a single target-config for both debuggers but I did not find out how to specify that this belongs to two different projects. In my debug window, it appears as a single instance in the dropdown. How do I link the debuggers to the corresponding project?

2. I tried launching two CCS instances with two different workspaces. The projects are split into different folders. But I still get this "LIBUSB_ERROR_ACCESS"

0 Ki 2 months ago in reply to Hannes Thielke

TI__Guru**** 484671 points

Hannes Thielke said:
1. I tried creating a single target-config for both debuggers but I did not find out how to specify that this belongs to two different projects. In my debug window, it appears as a single instance in the dropdown. How do I link the debuggers to the corresponding project?

A project debug session would be linked to just one project. I typically prefer to use a project-less debug session in these cases and manually load the relevant program to each device. As long as the projects are open in the workspace, the debugger can access the project information from both.

Hannes Thielke said:
2. I tried launching two CCS instances with two different workspaces. The projects are split into different folders. But I still get this "LIBUSB_ERROR_ACCESS"

Can you confirm that you have the serial number for each properly configured in the ccxml file? Can you connect to each one separately?

0 Hannes Thielke 2 months ago in reply to Ki

Prodigy 10 points

Yes, I have set up the different serial numbers in the ccxml files and can connect to each one separately

+1 Ki 2 months ago in reply to Hannes Thielke

TI__Guru**** 484671 points

Hannes Thielke said:
2. I tried launching two CCS instances with two different workspaces. The projects are split into different folders. But I still get this "LIBUSB_ERROR_ACCESS"

Ah ok I believe you are running into this known issue:

https://sir.ext.ti.com/jira/browse/EXT_EP-12959

There is a workaround. Disable the "Detect Probe on Launch" option mentioned in my post below:

RE: AWRL1432: Can the awrL1432 be connected using the v20 version of CCS?

Thanks

0 Hannes Thielke 2 months ago in reply to Ki

Prodigy 10 points

this fixed my issues, thanks!

In my case, the first CCS instance had "Detect Probe on Launch" enabled and the second one didn't. Disabling in both instances made it work.

Processors

Processors forum

CCSTUDIO: Debugging two MCUs with two XDS110