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.

EK-TM4C1294XL: repair EVK

Part Number: EK-TM4C1294XL
Other Parts Discussed in Thread: EK-TM4C123GXL, LMFLASHPROGRAMMER

Hi, I've been using using EK-TM4C1294XL to load firmware into an external board for a while and now I getting "Error connecting to the target", I had some earth problems recently and I think U20(tm4c123gh6pmi7) may be damaged. I'm connecting EK-TM4C1294XL trough USB connector U22 and already removed R6,R7,R8,R10,R11,R15,R16.

How can I check if U20 is damaged, I measure with osciloscope in jtag pins while trying to program (Error connecting to the target) from code composer studio and I see no switching in the signals, also without the target connected I measure voltage on jtag pins: reset=3.3V, TDO=0.75V, TDI=3.11V, TMS=0.75V and TCK=0.75V.

if U20 is damaged, is possible to replace the part? I have some tm4c123gh6pmi7.

thanks

Rafael

  • How can I check if U20 is damaged, I measure with osciloscope in jtag pins while trying to program (Error connecting to the target) from code composer studio and I see no switching in the signals, also without the target connected I measure voltage on jtag pins: reset=3.3V, TDO=0.75V, TDI=3.11V, TMS=0.75V and TCK=0.75V.

    if U20 is damaged, is possible to replace the part? I have some tm4c123gh6pmi7.

    The best way to confirm this is to use another EK-TM4C1294XL board to see if you connect to your custom board. If you can connect then it confirms that your first LaunchPad is not working. You can swap out the tm4c123 on the LaunchPad if you believe that it is damaged and you believe it is worth your time and effort to de-solder old and re-solder new part. You need to make that decision for yourself. Personally, I will just move on to a new EK-TM4C1294XL board or even EK-TM4C123GXL board if I'm short in time. See section 4.6 on how to use EK-TM4C123GXL on how to debug out another board. https://www.ti.com/lit/pdf/spma075.I will suggest you use a low cost debug probe like XDS100 or XDS200 to debug your system.  

  • Ok, is there another way to check? I don't have another EK-TM4C1294XL.

    if I decide to replace the tm4c123 what about the firmware?

    thanks for your help!

  • Hi,

    Ok, is there another way to check? I don't have another EK-TM4C1294XL.

      How many custom boards do you have? If the ICDI on your EK-TM4C1294XL board cannot connect to any of your boards, then it pretty much confirm something is wrong with the TM4C123 acting as the ICDI on the EK-TM4C1294XL board. 

    if I decide to replace the tm4c123 what about the firmware?

    That is a very good point I forgot to mention. There is a bootloader and an application on TM4C123. The application is the firmware to emulate ICDI. The bootloader is to receive the ICDI firmware update. The problem is that you need to have JTAG access to the TM4C123 to program the bootloader onto a virgin TM4C123. There is no easy way to do this. You will need a special tool to access the JTAG port for TM4C123. The tool may cost hundreds of dollars. I think you would rather just replace the launchpad board instead. 

  • That is a very good point I forgot to mention. There is a bootloader and an application on TM4C123.

    Is there a ROM bootloader in the TM4C123 which allows a USB DFU?

    From memory, I think LMFLASHPROGRAMMER cam program the IDCI firmware into a blank TM4C123 over USB.

  • Hi Chester,

      I don't think so even though there is a ROM bootloader on chip. However, I can check with our CCS experts.

      If you look at XDS110 (which is similar to ICDI) there is both the flash-based bootloader and the firmware. 

    LM flash programmer does allow ICDI firmware update but I think the assumption is that the flash-based bootloader is still in place and functioning. Whether or not the ROM bootloader on a virgin device can update the ICDI firmware, I don't know and I don't have time to prove it either. That will require me to de-solder and re-solder the TM4C123 MCU on the launchPad. Also bear in mind we don't provide a ICDI.bin file as it is a proprietary software. Clicking the ICDI firmware update button may not be the same as loading ICDI.bin (which we don't provide) in the Program tab assuming ROM bootloader is enumerating as DFU. 

  • Whether or not the ROM bootloader on a virgin device can update the ICDI firmware, I don't know and I don't have time to prove it either. That will require me to de-solder and re-solder the TM4C123 MCU on the launchPad.

    Since an EK-TM4C123GXL uses the same TM4C123GH6MPI device for the IDCI and target device performed a test with that launchpad and LM Flash Programmer Build 1613:

    1. Connect to the USB Debug port on the launchpad and use LM Flash Programmer to erase the entire flash of the target device.

    2. Connect to the USB Device port on the launchpad. The ROM bootloader in the target device enumerates as "Stellaris Device Firmware Upgrade".

    3. Try and use "Blank Check" on LM Flash Programmer and get a "**ERROR**: Unable to find a target!"

    4. Select the ICDI Firmware Update button on LM Flash Programmer and get the following:

    Selected Yes on the dialogue.

    This appeared to have programmed the ICDI firmware into the target device on the launchpad, since while still connected to the Device USB port is now enumerating as a "Stellaris In-Circuit Debug Interface".

    Therefore, think the LM Flash Programmer contains the ICDI.bin file internally, and *is* able to use the USB ROM bootloader in a blank TM4C123GH6MPI to program the IDCI firmware.

    I haven't actually replaced a TM4C123GH6MPI ICDI device on a launchpad and try and install the IDCI firmware with LM Flash Programmer, but based upon the above test think that would work.

  • HI Chester,

      Thanks a lot. The poster is free to try it out if he wants. The problem is that he only has one EK-TM4C1294XL LaunchPad, not EK-TM4C123GXL board which has the switch to select between USB debug port and USB device port. If the poster purchases a new EK-TM4C123GXL board, he might as well use it as is to debug his custom board instead of proving or disproving if the ROM bootloader will update the ICDI firmware.