This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
Hello,
I have been using the XDS-110 in combination with the CC1354P10-1 kits for the past 2 weeks now. It seems I have managed to brick 2 XDS-110s. Both of them light up the solid red LED and I can no longer interact with the programmer. The things I have done with them were to use CCS 12.8 and Uniflash to program some samples on to the CC1354P10. Before first use, CCS 12.8 did an upgrade of the firmware on the XDS once. The current firmware version running on XDS is 3.0.0.31. I still have a couple of working XDS110s (still in boxes). I want to know how to recover the bricked XDS110s and also to prevent any future bricking.
Cheers,
Balaji
Unfortunately one more XDS-110 that I just unboxed got bricked the same way. This time I tried to program it using Code Composer Studio Theia IDE. When I hit 'Debug' (because I could not find a way to Load the hex file), I got the error 'Module Closed' from the IDE and after that the XDS lights up just solid Red.
Hi Balaji,
Which XDS version is it? The LP-XDS110 (without EnergyTrace)? Can you tell me which revision is it?
Regards,
Arthur
Hi Arthur,
My XDS110 does not have EnergyTrace. It is this one -> https://www.ti.com/tool/LP-XDS110
The version on the back of the XDS board is BOM Rev: E1 2422.
Regards,
Balaji
Hi Balaji,
Can you also tell me where did you buy those? Was it on TI.com?
Regards,
Arthur
Also,
Can you check if the XDS110 device is in bootloader mode by running the following command from the ccs install folder: ccs****\ccs\ccs_base\common\uscif\xds110
xdsdfu.exe -m
Regards,
Arthur
This is the output I get. It seems as if the device is not detected.
C:\ti\ccs1280\ccs\ccs_base\common\uscif\xds110> .\xdsdfu.exe -m
USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.
Scanning USB buses for supported XDS110 devices...
The requested device was not found on the bus.
I see, then the procedure to recover the device would be the following one: https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/887212/faq-launchxl-cc1352p-debugger-firmware-upgrade-failure/3281522#3281522
As to what caused the bricking in the first place, I am not sure as of now.
Could you try updating the device firmware without the CC1354P10-1 kit connected to it ?
Regards,
Arthur
The issue fixed itself when I was dismantling the setup to do the suggested re-programming. Here is what I did.
- Disconnect the CC1354P10 from the XDS.
- Disconnect and reconnect the USB cable connected to the XDS. The LED turned solid green.
- Reconnect the CC1354P10.
- Disconnect the USB cable and reconnect.
My guess is that some pin state or timing issue between the target MCU (CC1354P10) and the debugger chip (MSP432E401YT) resulted in the XDS110 board getting stuck this way.