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.

[TM4C123G] Failed firmware update, now computer won't recognize Launchpad at all

Other Parts Discussed in Thread: EK-TM4C123GXL, TM4C1294NCPDT, TM4C123GH6PM

Hello,

I have been trying to get my Launchpad to work with the sample code provided with the LCD boosterpack. When I tried to run the code, I was directed by an error message to update the firmware and/or change the serial number of the XDS110. I went to that directory, and ran

xdsdfu -m

xdsdfu -f firmware.bin -r

Now, the Launchpad no longer shows up as a COM port under the device manager. I can't flash the device using LM Flash Programmer because my PC isn't even picking up the device. I'm thinking I failed the firmware update, and am wondering how to fix it. Is there some way to factory reset the Launchpad or am I just out of luck?

  • Hello Eric,

    XDS110 is not meant for TM4C LaunchPad. I believe you have bricked the part. I don't think you can recover the device.

    Regards
    Amit
  • Hi Amit,

    I'm suspecting that you believe that poster's "Killed" his ICDI MCU.

    If that's true - then indeed recovery of that device will be difficult (if even possible) .

    Might he then "break" the connections between ICDI MCU and board's main MCU - add a JTAG Header - and then program the main MCU? (assumes he employs another LPad or has a proper FTDI device at the ready...

  • Eric Hanf said:
    Now, the Launchpad no longer shows up as a COM port under the device manager. I can't flash the device using LM Flash Programmer because my PC isn't even picking up the device. I'm thinking I failed the firmware update, and am wondering how to fix it. Is there some way to factory reset the Launchpad or am I just out of luck?

    The ICDI on the EK-TM4C123GXL uses a TM4C123GH6PM processor, whereas the debug interface on a XDS110 uses a TM4C1294NCPDT processor.

    With the XDS110 firmware incorrectly flashed onto the EK-TM4C123GXL, the ICDI on the EK-TM4C123GXL is probably crashing without enumerating the USB debug interface which is why the LM Flash Programmer is unable to correct the problem.

    The readme for the XDS110 firmware update has the following:

    *** Recovering a Bricked XDS110 Without JTAG ***
    
    In the case that your XDS110 fails to enumerate as a USB device, or it
    fails to enter DFU programming mode, you can attempt the following steps
    to force it into DFU mode to recover:
    
    1) Ground the TCK pin (sometimes labeled as TCLK or SWCLK, check with your
    vendor for how to identify which pin to ground).
    
    2) Unplug and re-plug the XDS110 into the host PC while the pin is grounded.
    
    3) The XDS110 should now be in DFU programming mode and you can flash it 
    using the xdsdfu utility as detailed above.
    
    Note that this feature is currently only implemented in the XDS110 boot 
    loader that was first available in emupack 5.1.537.0. If your XDS110's
    boot loader is an earlier version, this procedure won't work, and you'll 
    need to use JTAG to recover.
    

    I think this procedure to recover a bricked XDS110 without JTAG is done by programming the BOOTCFG register to enable the ROM boot loader when the PA2 pin on the TM4C1294NCPDT debug processor is low at reset, where PA2 on the TM4C1294NCPDT debug processor is connected to TCK on the target processor.

    The ICDI on the EK-TM4C123GXL also uses PA2 on the TM4C123GH6PM debug processor for the TCK on the target processor, and the BOOTCFG register is the same on a TM4C123GH6PM and TM4C1294NCPDT.

    Therefore, you might be able to factory reset the bricked EK-TM4C123GXL by:

    1) Connect the pad labeled "TCK" on the EK-TM4C123GXL to ground.

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

    3) The EK-TM4C123GXL should now be in DFU programming mode and is able to be flashed using LM Flash Programmer.

    If the above fails, then the only other option to recover the EK-TM4C123GXL is to use JTAG, using the pads labeled "TC2050-IDC-NL" on the EK-TM4C123GXL which are connected for the JTAG interface of the TM4C123GH6PM debug processor.