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-TM4C129EXL: Implementing the on-chip programmer that is on the development kit

Part Number: EK-TM4C129EXL
Other Parts Discussed in Thread: EK-TM4C1294XL

Tool/software:

Hello,

We are moving forward building our design around the TM4C129xxx MCU, and we want to implement the on-chip programmer that is present on the development kit. Can we purchase this with directly from TI? Or, does TI provide the binaries for the MSP430 used for the USB interface?

Our design will be installed within a rack, and it is preferred to just have a USB connector exposed. This would be far better than removing the board and using an external JTAG.

Thank you,

Noah

  • We are moving forward building our design around the TM4C129xxx MCU, and we want to implement the on-chip programmer that is present on the development kit.

    Hi,

      Which development kit are you referring to?

    does TI provide the binaries for the MSP430 used for the USB interface?

    I'm confused. Why is MSP430 mentioned here? TM4C129 MCU is a vastly different MCU family from MSP430. What binary are you looking for? Perhaps you can answer the first question as to what programmer and what development kit you are talking about. 

  • Hello Charles,

    First of all, I was mistaken to mention the MSP430; I should have mentioned theTM4C123xH6PMI. This is the MCU used on the development kit EK-TM4C129EXL, and it facilitates the on-board debug capabilities.

    Does TI sell this onboard debugger as a product, and/or can we get the binaries for this MCU so that we can implement this on-board debugger into our design? 

    Thank you!

  • First of all, I was mistaken to mention the MSP430; I should have mentioned theTM4C123xH6PMI. This is the MCU used on the development kit EK-TM4C129EXL, and it facilitates the on-board debug capabilities.

    Thanks for the clarification. TM4C123 on the EK-TM4C1294XL LaunchPad serves the role as a ICDI debug probe. The ICDI firmware is proprietary and we do not distribute the source code or the binary. If you design your custom board with the TM4C123 intended as a ICDI debug probe then you can use the "ICDI Firmware Update" to load the firmware. After clicking "Update" the flash bootloader as well as the ICDI firmware will be loaded to the TM4C123 chip through the USB Debug Port. See below. 

    Just to add a note that I did an experiment. I first erase the flash content on the TM4C123 chip on the  LaunchPad using the pogo pins. With an empty flash content, I use the Update ICDI firmware in LM Flash Programmer and I can see both the flash-based bootloader as well as the ICDI firmware reloaded to TM4C123. Afterward, I can program and debug the target device (TM4C129) on the EK-TM4C1294XL LaunchPad. The pogo pins are JTAG pins to directly access the TM4C123. You need special hardware tool to do this. 

  • Charles, 

    Thank you for the information. This seems like a viable option. 

    As another programming approach, we are also considering using FTDI's FT2232 (https://ftdichip.com/products/ft2232hq/). Does TI offer any design examples, application notes, or other design guides to support flashing and debugging with this chipset, or similar?

    Thank you!

  • Hi,  

    Attached is a LaunchPad user's guide for a discontinued TI Cortex-M3 MCU that uses FT2232 as a USB to JTAG bridge. You will need to consider the additional cost adder using FTDI chips vs TM4C123 because I believe FTDI chips are not cheap considering you are adding one to every single board you have. 

    EKK-LM3S811 spmu030b.pdf