CCS 5.x/CCS 6.x - Problem with multiple instance of CCS / multiple JTAG emulator (to debug C6657 and DM647)

Hello Anthony,

AnBer said:

- Could you please confirm if it is a supported scenario or if we instead encourage to use a single JTAG chain/Single emulator/Single CCS instance to debug multiple processors?

Is should be a supported scenario (expect for the bug mentioned regarding two XDS560v2) though we usually recommend a single debug instance connected to multiple emulators instead.

AnBer said:

- Looking at the actual the SDSCM00048813 entry it seems that the bug is still present in 6.0 ad not plan to be fixed:
https://cqweb.ext.ti.com/cqweb/#/SDO-Web/SDOWP&format=HTML&version=cqwj

This bug is specific to two XDS560v2 emulators.

AnBer said:

The actual scenario failing scenario that is seen:
    Config:    CCS 5.5.0.00077 to debug 2 targets boards with 2 emulators below:
    Board                                        DSP                                EMU
    TMDSEVM6657LS                 TMS320C6657             on board XDS200 mezzanine
    custom                                    TMS320DM647             Spectrum Digital XDS510PLUS USB
can start 2 instances of CCS, and start debugging both, with the execution running.
Then pause with a breakpoint one instance. When pressing F6, the other instance of CCS crashes.
No matters which system I'm debugging: if I debug one of these, the other one crashes.

I will have to try this out myself when I am back in the office. Is there any particular reason why you wish to have two debug instances instead of just one that is connected to both targets?

Thanks

ki

Hi Ki,

Customer want to debug a system that uses 2 boards therefore the processors are not in the same JTAG chain.
They would need to use a custom connector in order to place the 2 devices in the same JTAG chain in order to debug.
I am not sure at all if you can use the XDS200 mezzanine with a custom connector.

Anthony

Ok I see. I will have a try.

Thanks Ki!

A.

Let me know how it goes. Note the one limitation documented here:

http://processors.wiki.ti.com/index.php/Multi-Emulator_Debug_with_CCSv5#Different_Type_Multi-Emulator_Configurations

You should be ok with an XDS510 and XDS200.

Hi Ki,

I am also trying to run multiple CCS instances for debugging multiple boards with XDS560v2. I have been doing this successfully with a single CCS instance using a target configuration that lists multiple emulator connections. However, a good reason to do it from different CCS instances is to separate out console output of different boards. With a single CCS instances, they all show up in the same window, which makes it hard to debug parallel runs.

Is there a bugfix on the roadmap for multiple instances with XDS560v2s? If not, is there a workaround, or another way to separate out printfs from different boards/cores?

Thanks,
Manu

Hi Manu

Manu Bansal said:

However, a good reason to do it from different CCS instances is to separate out console output of different boards. With a single CCS instances, they all show up in the same window, which makes it hard to debug parallel runs.

Is there a bugfix on the roadmap for multiple instances with XDS560v2s? If not, is there a workaround, or another way to separate out printfs from different boards/cores?

Check out the below url:

In the graphic (Fig. 3) note the check-box option "Use the same console for the CIO of all CPUs". Disable that checkbox to have each CPU have it's own CIO console.

Thanks

ki