CCSTUDIO: Unable to connect multiple XDS110 debuggers

Hello,

Bryan McDonald said:

 to have two separate running instances of CCS 12.6 communicating to two different debug probes connected to two different targets at the same time. 

If you only have one CCS instance running, can that one instance communicate to each XDS110 target via serial number without issue? Can you successfully start a multi-emulator debug session for both XDS110 targets using one instance of CCS?

Thanks

ki

Also, I can see that one of your targets is an MSPM0G3507 but has a serial number starting with M432. "M432" is typically reserved for MSP432 launchpads. Did you program the serial number to that value yourself?

Also, what is the other target (SATELLIT)? Is that a different launchpad? Or a board with an external XDS110 connected to it?

Thanks

ki

I have been able to connect to two separate XDS110 based launchpads connected to the same PC using two separate running instances of CCS:

Hi Ki,

These are XDS110 debuggers on MSPM0G3507 launchpads.  As best as I can recall, they both had SN M4321005 so I renamed one of them as SATELLIT so their SNs are unique.

Ok, thanks for clearing that up. Please note that for autodetect to properly detect the launchpads as MSPM0G3507 launchpads, the first four characters of the serial number should be MG35. It should have come programmed with that. How long have you had your launchpads?

In any case, regardless of the serial numbers, what you are trying to do should work. I can try using two MSPM0G3507 launchpads like you are and see if that makes a difference. I won't have access to this until next week.

In the mean time, can you try using CCS 12.7.0? We made several fixes to the XDS110 firmware the ships with CCS 12.7.0 (3.0.0.29) to make things more robust. I'm hoping that some of those improvements can help.

Thanks

ki

Hi Ki,

These Launchpads are older, as the MSPM0 devices are rev A. However I'm only using the XDS110 debugger from the Launchpads and am connecting to production silicon devices for programming via J102. (All J101 jumpers are removed.) I upgraded to CCS 12.7 and I changed the XDS110 serial numbers to MG350000 and MG350001.

I would prefer to run 2 debug sessions within the same running instance of CCS as you did, rather than to require 2 running instances. How would I do this if the sessions are for 2 separate projects loaded into the single CCS instance?

 BTW I'm able to run 2 debug sessions on 2 separate instances of CCS now after upgrading to CCS 12.7. 

That link appears to map to the link I posted at the beginning of this thread (or vise-versa).  I didn't see from it how to run 2 debug sessions with 2 separate projects in 1 CCS instance.  It seems you'd need to run 2 separate debug windows since the target configuration doesn't include project information.  But CCS wants me to terminate an existing debug session before starting another.  

Hi Ki,

Did you ultimately conclude as I did that separate instances of CCS are required to debug different projects at once?

Bryan McDonald said:

I didn't see from it how to run 2 debug sessions with 2 separate projects in 1 CCS instance.  It seems you'd need to run 2 separate debug windows since the target configuration doesn't include project information.  But CCS wants me to terminate an existing debug session before starting another.  

What you wish to do is to start one debug session for both boards. To do that, you need to create a single target configuration file for both boards (as mentioned in the above article) and then do a manual launch to have a single debug session to control both cores:

https://dev.ti.com/tirex/explore/node?node=A__AGAHo7UeU2QJmaEHpuoGUQ__ccs_devtools__FUz-xrs__LATEST

The video from you link demonstrates how to configure CCS to simultaneously debug two separate boards.  But both are running the same project.  How do I debug two different projects simultaneously?

Bryan McDonald said:

The video from you link demonstrates how to configure CCS to simultaneously debug two separate boards.  But both are running the same project.  How do I debug two different projects simultaneously?

You need to manually load each separate executable to the relevant core. Each debug context would reference the same project resources.

"Each debug context would reference the same project resources."  Sorry, I'm not understanding this.  Does this mean I would only be able to read variables from one project but not the other?

Does TI have a document or video describing how to debug two projects simultaneously?

Bryan McDonald said:

Does this mean I would only be able to read variables from one project but not the other?

No. When you load an *.out file to the CPU on one of the launchpads, the debug symbols (which include source file information from the project) are also loaded to the debugger for that CPU. So when you load a *.out file for each CPU/launchpad, you are loading the debug information for each one. So in your debug session where you are communicating to two launchpads (each with *.out file loaded), debug information associated with each project is available. 

Essentially you are now doing what is called "multi-core debug". You are debugging multiple cores (one on each launchpad) at the same time.

See the below article regarding multi-core debug:

https://dev.ti.com/tirex/explore/node?node=A__AF77MYXC5GXV9l1NS.Clig__ccs_devtools__FUz-xrs__LATEST