CODECOMPOSER: Code Composer Studio suddenly stopped connecting to XDS110 Debug Probe

Hi Tim,

Are you working with the standalone XDS110 debug probe in the link below?

https://www.ti.com/tool/TMDSEMU110-U

Thanks

ki

Hi Ki, 

Thank you for the fast response. 

Correct, I am working with the standalone debug probe.

Kind Regards

Tim

Thanks.

Tim Kostorz said:

-The Debug Probe works fine on a different machine (Windows 10, also CCS 12.3.0)

-I tested 2 more XDS110 debug probes, none of them work anymore on this specific machine

The probe and firmware running on the probe must be fine since it works on other machines.

For some reason your system is no longer able to detect the XDS110. You mentioned things used to work but one day it stopped. Do you recall if you had sometime of system update around the time? I did update one of my Windows 11 machines recently but XDS110 still seems to work ok.

You also mentioned reinstalling CCS. Did you try using a later CCS version? CCS 20 would be the latest but that would be quite a change given the overhaul to the IDE. CCS 12.8.1 would be the latest CCS 12.x version.

Thanks

ki

Tim Kostorz said:

Good news: The debug probe is working again. 

Great!

Tim Kostorz said:

After having a look into my windows update history, I noticed that there has been an update (23H2 - build KB5048685) on the 11th of december, which seems to have been the root cause of the malfunction. Fortunately, there has been a new windows update release (24H2) this night, which fixed the problem again

Interesting. The Windows 11 PC I used has 24H2.

Tim Kostorz said:

Let`s hope, it stays that way in future.

Yes, hopefully there are no more issues!

Tim Kostorz said:

Nevertheless, thank you very much for your help.

And thank you for providing and update and also details on your environment. Much appreciated!

ki

Hi Ki, 

Unfortunately, the debug probe broke down again after about a week, but this time without any Windows update. Since then, I have not been able to get it workig again, while it is still running flawlessly on my other windows 10 machine. It is kind of frustrating. 

Kind Regards,

Tim  

Ah, that is unfortunate. I'm pretty sure it is not a Windows 11 thing. Many people in my office are using Windows 11 without issue.

Since it works on other machines, it must be some other issue. 

Tim Kostorz said:

-The device gets correctly listed in the windows device manager. Thus, the USB Connection is working fine. I

Can you show me how it appears in Device Manager? If properly enumerated, you should see:

Hi Ki, 

this is how the device gets enumerated in the device manager:

Thank you for your help. 

Kind Regards,

Tim

The entries under "Texas Instruments Debug Probes" look fine. But it looks like ports for the XDS110 are not detected.

And you mentioned that "xdsdfu -e" returns no detected probes. This is odd. Usually if "xdsdfu -e" returns nothing, then no XDS110 related entry appears in device manager.

A bit if grasping at straws here but have you rebooted your PC since you reinstalled the device drivers?

Hi Ki, 
Yes, I did a complete restart (not just the normal shutdown / reboot process a the end of the day) after the driver installation. That is usually the first thing I do, when stuff doesn't behave as intended. 

Regarding the device manager: The ports for the XDS110 show up at the top of my screenshot ( "Ports" equals "Anschlüsse" in the german operating system). So to me, the entries look the same in comparison to the ones shown in your picture.  

As a last resort, I could try to do a complete windows operating system rebuild, but I would happily avoid this action, if there is a different solution to the problem.   

 Thank you for your help!

Kind Regards,

Tim

Tim Kostorz said:

The ports for the XDS110 show up at the top of my screenshot ( "Ports" equals "Anschlüsse" in the german operating system).

Ah, I completely missed that somehow. Sorry about that.

Your device manager entries look completely fine. I am really confused why CCS and xdsdfu does not detect any XDS110.

Tim Kostorz said:

As a last resort, I could try to do a complete windows operating system rebuild, but I would happily avoid this action

Yes I would hope that you would not need to do such a drastic action.

I will check with engineering to see if there is anything they can think of.

Ki said:

I will check with engineering to see if there is anything they can think of

Hi Ki, 

any updates on this topic? If you need further information from my side, just let me know. 

Kind Regards,

Tim

Sorry for the slow delay. We are indeed confused that Device Manager shows the device fine but CCS does not.

Can you generate a debug server log while reproducing the failed launch?

https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html

Then zip the log and attach to this thread. 

Hi Ki,

Yesterday, I tried generating the debug log and was completely confused, when I saw  the debug probe working completly normal again. When I checked it last week, the error was still persistent. It really gets kind of spooky now. 

Nevertheless, if / as soon as the debug probe stops working again, I will try to get the requested debug server log. But let's hope for the best, that this was the last time, this issue occured. 

Thank you very much for your support!

Kind Regards,

Tim  

I'm glad it is working again but the unreliability is concerning. I'm wondering if the probe may be a little defective. Yes, next time please provide a DS log and if it keeps happening it may be worth considering to get a replacement.