CCS/CC1352R: XDS110 gives Error when try to debug

Erwin Ahlers

Part Number: CC1352R

Tool/software: Code Composer Studio

I use Code Composer together with XDS110 debugger to put my program to CC1352R. With my program I use I2C data that is generated from another HW which is connected to the same PC Code Composer is running of. On this PC another program is running that talks with the I2C device via a virtual COM Port (other contains I2C to USB converter). When I now start the other PC program to send talk with the I2C device via virtual COM Code Composer doesn't find the debugger. I got the error

I searched already for this error but it seems to be a kind of general error without more special information. Unluckily this is a kind of show stopper. Or I have to develop my application without the help of a debugger. I don't want to tell my manager that I need 2 month more time for development as I have do implement/test it without a debugger.

So do you have a hint that could resolve this issue?

BTW: We have different HW with Atmel Processor that talks also with this I2C device and there is no problem. Debugger and programm works nicely at the same time.

Regards
Erwin

over 5 years ago

0 Ki over 5 years ago

TI__Guru**** 472291 points

Hello Erwin,

The link to your screenshot is broken. Please re-post it.

If you continue to have issues posting images, please see the below faq:

https://e2e.ti.com/support/tools/ccs/f/81/t/821597

Thanks

0 Erwin Ahlers over 5 years ago in reply to Ki

Intellectual 570 points

Here is the error message, now inserted as picture.

0 Ki over 5 years ago in reply to Erwin Ahlers

TI__Guru**** 472291 points

Thank you. I assume the issue only occurs when the other host program is interfacing with the virtual COM port of the XDS110. That would explain the error message since that error message often occurs when more than one channel of the XDS110 is attempted to be used simultaneously:

https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html#invalid-response-was-received-from-the-xds110

It appears this is likely what is happening in your case, though I need to confirm

0 Erwin Ahlers over 5 years ago in reply to Ki

Intellectual 570 points

This fits perfectly to my observation. Yesterday I put the whole code composer with the debugger into a virtual machine. Only then I can use the debugger together with a different tool, that also uses virtual com ports via USB.

Is this an XDS110 exclusive problem? As far as I know there are also other debug probes. Could some of these been used together with other virtual com usage?

Erwin

0 Ki over 5 years ago in reply to Erwin Ahlers

TI__Guru**** 472291 points

I have only heard issues with the XDS110 though the scenario wasn't necessarily validated with other debug probes

Code Composer Studio™︎

Code Composer Studio forum

CCS/CC1352R: XDS110 gives Error when try to debug