• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 2061 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

CCS: New XDS110 unable to update firmware

CCS: New XDS110 unable to update firmware

Adriana Gomez88
Prodigy 140 points
Other Parts Discussed in Thread: TM4C1294NCPDT

Tool/software: Code Composer Studio

I follow the instructions on the readme for recovering a Bricked XDS110 without JTAG, but now my device is not recognized and the led does not blink.  What can I do to recover or flash my device ?  

1) Ground the JTAG TDO pin of the XDS110's Tiva CPU. This is pin 97
on the 128 pin device. This is a JTAG pin for flashing the XDS110 via
JTAG; it is not the JTAG TDO pin of the debug target. If the board has
a JTAG header for flashing the XDS110 you may use that, otherwise you
can ground the pin on the device. (Check the TM4C1294NCPDT datasheet
for the pin location; it is located on a corner and easy to access.)

2) Unplug and re-plug the XDS110 into the host PC while the pin is grounded.

3)I scanned my device

C:\ti\ccsv7\ccs_base\common\uscif\xds110>xdsdfu -m

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2015 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...


<<<< Device 0 >>>>

VID: 0x0451 PID: 0xbef3
Device Name: XDS110 Embed with CMSIS-DAP
Version: 2.3.0.11
Manufacturer: Texas Instruments
Serial Num: L5000HXQ
Mode: Runtime

Switching device into DFU mode.

4)     download the bootloader

C:\ti\ccsv7\ccs_base\common\uscif\xds110>xdsdfu -f boot_loader.bin -r

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2015 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...

Downloading boot_loader.bin to device...

  • 0
    TI__Guru**** 171044 points
    Hi,

    I am a bit confused by the sequence of events done by you. What exactly the xdsdfu utility reported before you performed steps 1/2 above?

    The reason of my question is that, at step 3, it seems the XDS110 bootloader is already working and properly loading the custom XDS110 firmware - thus not requiring the recovery process mentioned in the previous steps.

    Also, after step 4 what happens? Does the process complete successfully?

    In case negative, wait for some time to allow the operation to complete (maximum of 5~7 minutes, depending on the type of the USB port used) and unplug and replug the XDS110 from the USB port and re-issue xdsdfu to verify what is the status of the probe.

    In case positive, re-issue the xdsdfu and verify what is the status of the probe.

    In both cases:
    - If the status is similar to what is reported in step 3, then the probe should be working fine. From inside CCS I would try to run the Test Connection from the Target Configuration Editor.
    - If the status is "not found", retry steps 1/2 to bring it back to "DFU Mode" and flash the firmware.
    - If the status is in "DFU mode", then you should try to write the firmware (xdsdfu -f firmware.bin -r) and unplug/replug the XDS110 after the operation completes successfully.

    At this point you should have a working XDS110. In case negative, I would inspect USB cables, switch the USB port, try in another host, etc.

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Prodigy 140 points
    I loaded the boot_loader.bin, but then my debugger was not recognized by the computer anymore. I think I erase all flash with the last command because the green led does not blink.
    I tried with another USB cable but it does not work and I tried with another host but it does not power on the led
  • 0 in reply to Adriana Gomez88
    TI__Guru**** 171044 points
    Hi,

    At this point I would retry steps 1) and 2) of your original post - this should bring the ROM bootloader and put your Debug Probe in DFU, allowing you to re-write the bootloader and firmware.

    If that does not work, I am afraid your Debug Probe faulty.

    Hope this helps,
    Rafael