Original question:
TM4C1233H6PGE: Programming Tool and Connector for the TM4C1233H6PGE
I was experimenting with the programming interface on the EK-TM4C1294XL LaunchPad and I mistakenly programmed the TM4C123xH6PMI that serves as the in-circuit debugger. Can I get the hex file for the in-circuit debugger so that I can fix my mistake? Thank you.
Hi,
Please try the to restore the ICDI firmware by clicking the Update button and see if that works. I'm worry that the bootloader in the TM4C123 is wiped and not just the ICDI firmware.
If you are running some type of USB DFU application, please be extremely careful on which DFU device to select for firmware update as both the Stellaris DFU for the ICDI emulator and the device DFU can show up on the Windows device manager or dfuprog.exe . If you are using dfuprog.exe, you can specify which device using the -index switch. Another method to avoid programming the wrong device is to supply power to the target through the USB Device Port and unconnect the USB debug port. There is a jumper on the LaunchPad to select the power source.
I am a bit unfamiliar with LM Flash Programmer (I was working in Code Composer Studio). I downloaded the tool and on the configuration tab I selected the board I am using. The LaunchPad is connected to my computer via the USB Debug Port (U22).
Notice at the bottom it says connecting to ICDI device. If I go to the Other Utilities tab and click the Update Button, I get the following error message.
Notice at the bottom it says connecting to ICDI device. If I go to the Other Utilities tab and click the Update Button, I get the following error message.
Thanks for the clarification. There is the U6 available for external debugger connection. I think what you have done is what I was worried that the bootloader is wiped out on TM4C123. This is what I think for the TM4C123 part. On TM4C123, there is a flash-bootloader residing at 0x0 acting as a USB DFU device that will download the ICDI firmware. After the ICDI firmware is downloaded, it is how the TM4C123 will emulate as a ICDI debug probe. The recovery method I was suggesting was assuming that the bootloader is still intact. In this case, you just use the LM flash programmer to download the ICDI firmware again. In your current situation, I think you corrupt even the bootloader residing at 0x0 because you use the pogo port that actually download your simple application using the JTAG interface. What you need is not just the the ICDI firmware but also the bootloader. The problem I see is that the ICDI firmware is part of the LM flash programmer. There is no standalone ICDI firmware binary for distribution.
One more suggestion I can make is as follows but I doubt it will work.
1. Connect to the TM4C123 through the pogo port as you did earlier by mistake.
2. Once connected, erase the flash on TM4C123. You can use CCS or Uniflash. I don't know which external debug probe you use. If it is not one of the supported debug probes like XDS110, XDS200 or etc then you can't even continue with the next step. See below screenshot that uses Uniflash to erase the flash on TM4C123.
3. Go back to my last reply and use the LM flash programmer to update the ICDI firmware.
