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.

LAUNCHXL-CC1352P: Unable to load XDS110 debugger driver after firmware update from TI Flash Programmer v2

Part Number: LAUNCHXL-CC1352P


I opened the SmartRF Flash Programmer in order to flash program my image to the CC1352 on board the CC1352P1 launchpad , which is connected with a USB cable to my PC. once choosing the XDS110 from the connected devices pane (left side) i was asked to perform an update to the XDS110. I pressed ok and after a few seconds the update stopped on 50% and said theres some kind of ERROR(dont remember which, and its already not availble for me). I waited a bit more and since there was no change I pressed cancel. Then after resetting the launchpad, the XDS drivers didnt load anymore and the device manager doesnt show any xds device under "Ports".

It seems the firmware upgrader messed up the xds firmware and it doesnt load anymore..my launch pad is useless now..@!

  • I will check with the tools team if it's possible to save the launchpad

  • Have you installed Code Composer Studio (CCS) already?

    In that case you could try to use the XDS tools that is included in this installation. 

    In a typical installation you will find the tool here: C:\ti\ccs_base\common\uscif\xds110

    The xdsdfu.exe can be used to update the firmware of the XDS110 emulator. You will find a "readme" file with further information about how to use the tool.

    I hope this can help to resolve the problem.

    Regards,

    Øyvind

  • Hi Øyvind,

    Thanks for your reply. 

    The main issue here is that the XDS is no longer loaded in windows device manager, no response at all when I plug in the Launchpad via the USB. windows doesnt even attempt to identify something. 

    I think that when the XDS firmware update was interrupted, its firmware is now corrupt and nothing loads..

    The question is is there a tool, or back door/reset for the XDS firmware itself..

    BR

    Arie

  • If the XDS110 does not pop up in SmartRF Studio etc you most likely need to reflash the bootloader code into the TIVA: The hex file for this is could be found under C:\ti\ccs920\ccs\ccs_base\common\uscif\xds110\firmware.bin but that require that you have a functional XDS110 and a debug connector for the TICA. The connector is P8 (on the C1310 LP) up in the right corner if you look at the LP from the underside. 

  • Hi,

    i have a similar problem with my CC1352R1-Launchpad. The onboard XDS110 is no longer loaded in windows device manager after an unintended "USB-cable-remove" during a firmware update. Can you tell me the exakt type of connector (of P8) so i can find a suitable cable to flash the firmware.bin into the  TM4C-controller? Within the BOM (bill of material) there is not much info about this (only "DNM", do not mount, not very helpful...)
    Is this any ARM-standard-connector or something TI proprietary?

    Thanks, best regards
    Albert

  • I don't have the exact order number but you can look at http://www.tag-connect.com and look for TC2050. If you are going to use it once it may be cheaper to get a new LP. 

  • Thank you, this information was helpful!
    i managed to get this TC2050-adapter cable and flashed the boot_loader.bin from \ti\ccs910\ccs\ccs_base\common\uscif\xds110, but unfortunately the Leds of the XDS110 are still dark and Windows is not detecting the device. (also not the xdsdfu.exe application).

    Anything else i can do?

  • Did you remember to program the firmware.bin file? If not, connect the  board with the USB cable and use xdsdfu.exe to program the firmware.

  • Thanks for the hint! I actually did not think to try it again with the xdsdfu-utility after flashing the bootloader with the JTAG adapter because I expected the board to be recognized by windows.
    Applying the commands
    xdsdfu -m
    xdsdfu -f firmware.bin -r
    as explained in the XDS110 Support Notes indeed solved my problem!

    Thanks a lot Øyvind K, you saved my Launchpad!