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.

CCS: Can't update XDS110 firmware

Other Parts Discussed in Thread: CC1350, CC1310

Tool/software: Code Composer Studio

Hi,

I have 2 CC1310 Launchpads and 2 CC1350 Launchpads which I am only using the XDS110 to connect to my custom boards.

Two of them are working and two aren't.

I recently switch from Windows 7 to Windows 10.

The ones that aren't working are shown as follows:

I am trying to update the XDS110 firmware, doing the following steps:

  1. Go to the directory where the utility is installed:
    C:\>cd C:\ti\ccsv6\ccs_base\common\uscif\xds110
  2. Run the configuration just to make sure a XDS110-class debugger is connected (or to list how many are connected) and what is the firmware revision installed on it:
    C:\ti\ccsv6\ccs_base\common\uscif\xds110>xdsdfu -e
  3. Put the XDS110 in DFU mode:
    C:\ti\ccsv6\ccs_base\common\uscif\xds110>xdsdfu -m
  4. Run the updater, passing the firmware file and resetting the debug probe afterwards:
    C:\ti\ccsv6\ccs_base\common\uscif\xds110>xdsdfu -f firmware.bin -r

But after "xdsdfu -f firmware.bin -r" I am getting: Device is in runtime mode. Switch to DFU mode using '-m' before attempting any other operation.

I already tried "xdsdfu -m" several times. It says "switching device inot DFU mode" but I still get the error message when trying "xdsdfu -f firmware.bin -r".

What must I do to Windows recognize the XDS110 device?

  • Hi,

    The thread below shows a very similar scenario as your screenshot: "XDS110 Embed with CMSIS-DAP". Perhaps the device drivers are failing for this particular USB device instance.
    e2e.ti.com/.../1766726

    If that does not help, you can try:
    1. uninstall this instance and re-install it using the drivers supplied by the CCS install, typically located at:
    C:\ti\ccsv7\ccs_base\emulation\windows\xds110_drivers

    2. Try the same board in another PC. The reason is to determine if the problem is originated in the PC or the HW.

    Usually when the xdsdfu -e lists the XDS110, its device drivers should be properly instantiated but the drivers may not be up-to-date.

    Hope this helps,
    Rafael