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.

IWRL6432: XDS110 Not Recoverable (Code 45)

Part Number: IWRL6432

Tool/software:

Hi Team, seeking for some insights. 

I would like to sincerely explain my situation and kindly ask for further assistance.

This XDS110 issue is part of a university research project involving the IWRL6432 LaunchPad. I’m a student working on a mmWave sensing system, and I accidentally executed a firmware update command while the board was not properly connected. Since then, I’ve spent weeks attempting to recover the board using all available troubleshooting methods, including:

- Multiple USB cable and port swaps (direct to motherboard USB 2.0)
- System cold shutdown and USB power resets
- Holding the reset button while inserting USB
- Driver cleanup and reinstallation (including Stellaris DFU)
- Trying on multiple PCs
- Following both the XDS110 recovery guide and JTAG troubleshooting checklist

Currently, the board only appears in Device Manager as:

    Stellaris Device Firmware Upgrade (Code 45)

There is no USB response or sound, and the xdsdfu tool still returns "Found 0 devices". This clearly indicates that the onboard XDS110 is stuck in DFU mode but unable to communicate. I believe the bootloader or firmware is corrupted in a way that cannot be recovered without a second debugger, which I do not have access to.

This board is used in my coursework and I do not have the resources to reflash the XDS110 via JTAG or purchase a new LaunchPad at the moment.

Thank you.

-Mark

  • Hello,

    The XDS should never show up as "Stellaris Device Firmware Upgrade (Code 45)". I have never seen this. It should look like my COM71 and 72 below

    Do you have other driver software on your computer that may be conflicting with this? Causing the hardware to be misidentified as this "Stellaris" device rather than XDS?

    Best Regards,

    Pedrhom

  • Hi Pedrhom,

    I’d like to ask two questions:

    1. Is there any remaining recovery path available for this device?
    2. If we purchase a standalone XDS110 Debug Probe, would it be possible to restore the onboard TM4C1294 (e.g., via JTAG or SWD)?

    Thank you.

    -Mark

  • Hello Mark,

    Since we have never seen this behavior, it would be hard to say if a recovery path does or does not exist. I will also note that bricking a device via a cable not being connected seems odd, I would think you would just get an error since nothing could be established in the first place. It would be easiest to get a replacement. See if you can contact your TI Representative or TI Customer Service to get a new one, they can refer back to this thread and I'd approve a new one.

    Best Regards,

    Pedrhom