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-TM4C123GXL: Intermittent Problems with Stellaris ICDI Debug Interface on EK-TM4C123GXL Launchpad

Part Number: EK-TM4C123GXL
Other Parts Discussed in Thread: TM4C123GH6PM, , SEGGER

Hello Forum,

I am working with EK-TM4C123GXL Launchpad with TM4C123GH6PM MCU,  Keil uVision5 IDE, and LM Flash Programmer - Build 1613. I had this whole development chain working perfectly and was going good. But some days when I fire up the system my PC does not see the Stellaris Virtual COM Port, nor the Stellaris ICDI Debug Interface - i.e. these are NOT listed in the Hardware list of my PC. If I restart PC, which powers down and powers up again the EK-TM4C123GXL Launchpad via USB port, sometimes then the Stellaris Virtual COM Port, and the Stellaris ICDI Debug Interface are listed in the Hardware list of my PC. I can then proceed to open up Keil uVison5 and try programming my Launchpad via the Load button at top of IDE screen. LM Flash Programmer opens up, but when I try Program, the Programming often fails after 17%, 25% etc. The LM Flash Programmer just not functioning perfectly. Sometimes Programming does complete to 100% and Verify succeeds but the loaded program will not run. I have searched and read on the Forums regarding problems related to mine and similar to mine. It makes somewhat torturous and tiresome reading. 

I am going to bin my Stellaris IDCE Debug Interface. Could anyone please suggest a recommend a better not too expensive Programming/Debugging method for the EK-TM4C123GXL Launchpad?, please.

Yours Sincerely,

John O'Connor

  • Many here (especially poster Robert & myself) have enjoyed far more reliable/robust results via Segger's J-Link - which is available at "educational discount" (granted (even) if you are "outside" normal "educator" status.)

    My firm's choice is the pro IDE - IAR - and those two in combination are rarely (perhaps never) found "broken/bruised/bleeding" as "so often" is the fate of those here - employing "lesser" JTAG/SWD Pods.

    You will have to "defeat the connections" between the ICDI MCU and the "user MCU" (upon the LPad) to engage the J-Link - and create a custom cable, too...    Segger site provides rich detail - note the J-Link has a long & distinguished "history" - has a vastly larger "installed base" - and surely justifies (any) extra cost...     (the place to "save" is NOT w/your Tech Tools!)

  • In reply to: cb1_mobile

    Thank you ever so much for such a prompt, informed and helpful reply.

    Kind Regards,

    John O'Connor
  • Speaking of such, "Prompt, informed, helpful reply" - somehow you've, "Suggested your post as the answer" - not the one of which you wrote so fondly! Might you correct this - by clicking the same box - except this time w/in my answering post? Thank you...