How can I connect to two C6678 EVM by two ccs5.5?

Hi Si,

You're experiencing emulator conflict issue. Can you give me more info on the emulator you're using?

Regards,

Gautam

Hi Gautam,

One of the emulator  is Spectrum Digital XDSPRO USB Emulator , other is Blackhawk XDS560v2-USB Mezzanine

Emulator. and they use different  emulator  I/O port number, Blackhawk XDS560v2-USB Mezzanine use I/O port =

0, Spectrum Digital XDSPRO USB use user defined port number 10. I use these Emulators in one target

configurations file, and can connect to the two EVMs. And when used in two ccs, one will abort.

Regards,

Si

si cheng said:

One of the emulator  is Spectrum Digital XDSPRO USB Emulator , other is Blackhawk XDS560v2-USB Mezzanine

Emulator. and they use different  emulator  I/O port number, Blackhawk XDS560v2-USB Mezzanine use I/O port =

0, Spectrum Digital XDSPRO USB use user defined port number 10. I use these Emulators in one target

configurations file, and can connect to the two EVMs. And when used in two ccs, one will abort.

Yes Si, this bound to happen if same emulators are selected on both CCS instances. So please check whether correct emulator is selected, as there might be 2 emulators listed during debugging.

Regards,

Gautam

Gautam,

I am sure I do not use the same emulators. Here are some pictures.

ccs1:

it can connect to evm board.

ccs2:

when I connect to the evm board, I just can connet to core0, after I core0, I connect core1, it aborts.

Regards,

Si

hi,

another question.

I use two Texas Instruments XDS100v1 USB Emulator  with two c6678 EVM,  and the USB serial port is COM11 and 5, then I use the tool xds100serial.exe  to get the   serial number, it output is:

C:\Users\ChengSi>C:\ti\ccsv5\ccs_base\common\uscif\xds100serial.exe
Scanning for XDS100 emulators...

VID/PID    Type                    Serial #       Description
0403/a6d0 XDS100v1/v2 TIU72PWC Texas Instruments XDS100+RS232 V1.0
0403/a6d0 XDS100v1/v2 TIU72PWC Texas Instruments XDS100+RS232 V1.0

why the serial # is the same, it should not be the same,because I will use it in the two target configuration file.

Regards,

Si

Si, can your perform one experiment? Try another emulator in CCS v6.

Regards,

Gautam

Si,

I see you have two .ccxml files, but I am not 100% sure why you are assigning a different port number to the Pro Trace. 

I created similar configurations but using the default I/O Port 0 on both and it worked just fine in my setup.

What is exactly the error shown in the message box you sent before?

Regards,

Rafael

Rafael,

The picture you pasted just connect to one core every ccs, it's also OK for me. You can try connect all core every ccs,when you connect to the second ccs, it will stop woking.

The error shown in the message box I sent before means ccs has stopped woking, it appears a problem which leads to program stop woking normally.

Regards,

Si

Si,

Thanks for reporting this. Yesterday I found out the same thing as you but couldn't reply in time - connecting to multiple cores yields to a lockup in one of the systems.

I am still unsure what is the root cause, therefore I will reply back when I get additional details, ok? I will file a bug when I get a better idea where the issue is coming from.

I apologize for the inconvenience,

Rafael

Si,

I filed the bug SDSCM00050737 today. Please check its status and a published workaround on the link SDOWP in my signature below.

Regards,

Rafael

Si,

I updated the bug case above with a less intrusive workaround.

I talked yesterday with the developers and a definitive fix for that will only happen in a longer term release, as it implies fundamental changes to some of the inner components of the tool.

Again, I apologize for the inconvenience.

Rafael

Rafael,

Thanks for your reply. But I can't find the workaround of the bug SDSCM00050737 in the  SDOWP .

Can you  describe the workaround  in detail? 

Regards,

Si