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.

Debugging TM4C using Stellaris ICDI in Eclipse IAR Plugin?

Other Parts Discussed in Thread: SEGGER, EK-TM4C1294XL

Hello,

I have a TM4C129X Development Kit as well as a TM4C1294XL Launchpad that I'm struggling to connect to with my debugger.

For legacy reasons, our development team is using Eclipse as our development environment, and I am using the IAR compiler plugin for Eclipse as is available from here: http://eclipse-update.iar.com

I have installed the latest version of Stellaris ICDI drivers for Windows 10 (v1.0, dated 21-JAN-2016), and by all indications they are installed correctly and visible in Device Manager:

According to spmu287c, this seems to be the indication that the drivers are installed correctly and should be ready for use.

However, when I go to Eclipse and attempt to select the TI Stellaris driver in my debugger configuration, it is not available as an option in the drop-down list:

I have tried uninstalling and reinstalling the plugin software, but it didn't seem to have any visible effect.  Any idea what I'm doing wrong, or what I might try?

For my toolchain, I am using IAR Embedded Workbench 7.5.  

I have tried this with both Eclipse Kepler and Eclipse Neon and both show the same results.

I am able to flash my device through the ICDI interface using LM Flash Programmer, but I am really hoping for symbolic debugger capability.

If I use Code Composer 6.20, then I am able to debug the device -- the trouble is that our team is not in a place to switch over to this tool at this time, and my code project is not setup to compile in this environment.  

For completeness, this is running Windows 10 on an x64 environment.  

Thank you very much for any help you can provide

  • Hello Clint,

    I am not aware if there is an Eclipse Plugin for Stellaris ICDI. I would ask you to check on the code composer forum.
  • Thank you very much, Amit.

    I don't know why I thought that this should have been an option, but it definitely appears that ICDI is not supported under Eclipse.

    At least I won't keep beating my head against the wall, wondering why this wasn't working. :)

    Much appreciated!

    --clint
  • I note that J-Link IS supported - and firm/I find - proves far superior to (any) vendor's ICDI.

    Even better - J-Link is available from Segger at great discount.    Search for "Educational use" - and you do NOT have to be in school or have such affiliation to reap that discount.

    If you like your doctor (Eclipse) you can keep your doctor (Eclipse.)   And gain better and more robust performance - at the same time...

  • Hello cb1

    Good point. The EK-TM4C1294XL would work with J-link but not the DK-TM4C129x (need to run wires).