• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 83 subscribers
  • Views 458 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.

LAUNCHXL-F280025C: CCS Updating firmware bricks board

Shawn Wu42
Prodigy 50 points

Part Number: LAUNCHXL-F280025C

Tool/software:

I've already read through this thread: https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/614357/ccs-can-t-update-xds110-firmware

and this page: https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html

The problem:

I tried the Servo Drive with CAN for F28002X example project. When trying to debug, CCS 20.0.0 requires to update the XDS110 Probe:

However, after updating the probe, it no longer detects the probe:

I tried updating through xdsdfu, as stated here: https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html#manual-update

However, xdsdfu can't detect the board:

And the board doesn't show up in Device Manager either:

The troubleshooting section:https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html#option-1-flash-the-bootloader-from-the-command-line-using-the-xdsdfu-utility

says to short the JTAG TDO to ground to force the board to DFU mode to try to unbrick the board. I believe this is J102 on the LAUNCHXL-F280025C board, so I put a jumper on J102 but xdsdfu gives the same results (can't find the board).

I've tried this on two different Win 10 computers and two different recently purchased LAUNCHXL-F280025C boards, so it's not the computer or board.

I have a third board, so unbricking is not the priority, but rather how to debug without bricking the board or needing to update the firmware.

-Shawn

  • 0
    TI__Mastermind 20380 points

    Hi Shawn,

    Shawn Wu42 said:
    says to short the JTAG TDO to ground to force the board to DFU mode to try to unbrick the board. I believe this is J102 on the LAUNCHXL-F280025C board, so I put a jumper on J102 but xdsdfu gives the same results (can't find the board).

    I believe J101 has the JTAG TDO signal that you'd need to short. 

    I've personally had this issue before and was able to fix it using the xdsdfu utility (without forcing DFU mode), even though xdsdfu couldn't detect the board with the -e flag:

    1. Unplug and re-plug the USB to the LaunchPad
    2. Execute: xdsdfu.exe -m 
    3. Execute: xdsdfu.exe -f <most_recent_firmware.bin> -r

    Once the second command has completed, the firmware is updated, and the XDS110 should be ready to use.

    Best,

    Matt

  • 0 in reply to Matt Kukucka
    Prodigy 50 points

    Matt,

         Thanks for the suggestion, but the board still cannot be detected even after playing with the TMS and TCK jumpers on J101.

         I tried your solution (xdsdfu.exe -m) but it wouldn't work because the board still wasn't detected, and this was tried on two different boards and two different computers.

          Hopefully someone will post a different solution or diagnostic. Again, thank you for your help.

    -Shawn

  • +1 in reply to Shawn Wu42
    TI__Guru**** 486181 points

    Hi Shawn,

    This is a known issue: https://sir.ext.ti.com/jira/browse/EXT_EP-12143

    An official fix will be coming firmware version 36 which ships with the upcoming CCS 20.1.0 release coming Monday.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 50 points

    Ki,

         Thank you, this was the issue. Holding down the side button when plugging in the USB port solved everything. Guess I'll wait until Monday for the fix.

    Shawn