• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 132 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.

TMS320F2800137: After Flash Project, Can Not connect to XDS110

Derrick Tuten
Prodigy 10 points

Part Number: TMS320F2800137
Other Parts Discussed in Thread: LAUNCHXL-F2800137

I flased a project to my launchxl-f2800137 board and niw i can no longer connect to the board with the debugger.

I get this error:

IcePick_C_0: Error initializing emulator: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the XDS110SupportReadMe.pdf file there for instructions. (Emulation package 20.5.0.3902) 

 

When I use the xdsdfu -e command, i get this response:

./xdsdfu -e

 

USB Device Firmware Upgrade Utility

Copyright (c) 2008-2019 Texas Instruments Incorporated.  All rights reserved.

 

Scanning USB buses for supported XDS110 devices...

 

 

Found 0 devices.

How do I get my board back to nornal?

  • 0
    TI__Mastermind 34353 points

    Hi Derrik,

    Your board is almost certainly not damaged. This is a well-known issue where the application you flashed is interfering with the JTAG/debug connection, which in turn prevents the XDS110 from communicating with the target MCU [1]. The XDS110 debugger hardware itself is likely fine.

    There are two possible scenarios here, and you should try them in order:

    Step 1: Put the Device in "Wait Boot Mode"

    This is the most likely fix. Your flashed code is running immediately on power-up and reconfiguring pins (or otherwise blocking JTAG), so the debugger can't connect. By changing the boot mode, you prevent the flash code from executing:

    1. Locate the boot mode switch (S3) on your LAUNCHXL-F2800137
    2. Set it to "Wait Boot" mode — this forces the MCU to wait in the boot ROM instead of jumping to your flash application
    3. Power cycle the board (unplug and replug USB)
    4. Try xdsdfu -e again — the XDS110 should now be detected

    Once detected, connect via CCS and either erase the flash or load a corrected program. After flashing working code, you can switch back to Flash Boot mode [1].

    The LAUNCHXL-F2800137 uses 2-pin cJTAG mode by default, so ensure your target configuration (.ccxml) is set accordingly [2].

    Step 2: If xdsdfu Still Shows 0 Devices (XDS110 Firmware Recovery)

    If changing boot mode doesn't help and the XDS110 still isn't detected at all (not even appearing in your OS's device manager), the XDS110 controller firmware itself may be corrupted. The recovery procedure is [3]:

    1. Disconnect the USB cable
    2. Ground Pin 97 (TDO) of the MSP432E (the XDS110 controller chip) — this forces it into bootloader mode. You may need to locate the corresponding test point on your board.
    3. Reconnect the USB cable while keeping pin 97 grounded
    4. Wait ~5 seconds, then release the ground connection
    5. Run xdsdfu -e — the device should now appear
    6. Reflash the firmware:
      xdsdfu -f *firmware*.bin -r
      (The firmware file is in your CCS install at ccs_base/common/uscif/xds110/)

    Quick Diagnostic Checklist

    Check
    What to look for
    LEDs on board
    LED7 (5V USB power) and LED0/LED1 (3.3V) should be lit [2]
    USB cable
    Verify it's a data cable, not charge-only
    J101 jumpers
    Ensure TCK and TMS shunts are installed [2]
    Device Manager
    Does the XDS110 appear at all as a USB device?

    Most Likely Outcome

    Based on identical cases with C2000 LaunchPads, Step 1 (Wait Boot Mode) will resolve this. The flashed application is simply preventing JTAG access. Once you regain debugger connectivity, load a program that doesn't reconfigure the JTAG pins (GPIO35/TDI and GPIO37/TDO on this device, or the TMS/TCK pins used for 2-pin cJTAG) [1][2].

    To help refine this recommendation, it would be helpful to know:

    • Whether the XDS110 appears at all in your operating system's device manager (Windows) or lsusb (Linux)
    • Which LEDs on the board are illuminated when USB is connected
    • What your flashed application does (specifically, does it reconfigure GPIO pins or enter low-power modes early in execution?)
    • Your operating system and CCS version
    1. LAUNCHXL-F2800157: Error -260 with XDS110 Debugger - TI E2E
    2. LAUNCHXL-F2800137 User's Guide (SPRUJ32)
    3. LAUNCHXL-F280039C: XDS110 (MSP432E401) Bricked Recovery - TI E2E

    Best Regards,

    Zackary Fleenor