LAUNCHXL-F280039C: Launchpad debugger not responding

Hi Adrien,

You are getting what is known as a "Host Connection Error". Basically, the debugger is unable to communicate with the debug probe.

Error 260 is described in the Debugging JTAG page below, together with tips to fix this issue (search for the error number):

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

Hope this helps,

Matt

Hi,

I applied the methodology described in this post. However, the "fix" goes away when the launchpad is powered off : I reprogramm the XDS110 in the launchpad and am able to program my target MCU, but if I unplug the launchpad, I have to start the operation all over again.

This makes me think that the program is only loaded in RAM by this procedure, not in FLASH memory. Or maybe the new serial number set by the procedure is not right, and not recognized by CCS and that prevents it from working ?

This will work for today's training session, however it is not a viable solution long term. What can I do to fix these launchpads ?

Thanks in advance,

Adrien

Hi Adrien,

I'll be looping in the CCS team to assist with the xdsdfu utility.

Best,

Matt

Hello Ki,

Thanks. I did reprogrammed the debuggers with xds110 firmware v 3.0.0.33. That would explain the issue.

I have left the boards with the client, so I can't make the test myself, but I have sent the client de procedure to fix it himself, with a request to keep me updated on the issue.

I will let you know if the problem isn't fixed on his end, but in the meantime, I think we can assume it is likely it will.

Thanks a lot for your help.

Adrien

To confirm the issue, the customer can just try the workaround of plugging in the USB cable while S1 is being held down. If the XDS110 is detected after that, then it is the same exact issue. I am 99% sure it is the same issue.