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.

TM4C123GH6PM: Other microcontrollers forum

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

Hi,

I am trying to program TIVA C launchpad using keil uvision v5.29. I do not see stellaris debug interface in keil. How can I program TIVA C launchpad without stellaris icdi interface with keil uvision?

Thanks and Regards,

Sudheesh

  • Hello Sudheesh,

    Do you see the Stellaris ICDI interface show up within your device manager?

    If the PC recognizes it, this may need to be routed to Keil as I am not familiar with the compiler.

    You may need the device package from: https://www.keil.com/dd2/texasinstruments/tm4c123gh6pm/

  • Hello Ralph Jacobi,

    Yes, I have already installed device package from TI and my PC recognizes stallaris icdi devices when I connect my TIVA C board. But, stellaris icdi is not listed in keil debugger list.

    Best Regards,

    Sudheesh

  • Hello Sudheesh,

    Unfortunately I am not sure what else to suggest here. You need to reach out to Keil about this. If the PC enumerates the LaunchPad properly, then the issue is with Keil and we are not able to help support because that is not a TI IDE so we don't have much experience with it. I have not seen that issue myself in my very limited usage of Keil uVision.

    I'm going to close out this thread as unfortunately we can't help further.

  • same problem. Stellaris ICDI is not in the list

  • Hello Marcos,

    Again this needs to be raised with Keil - we do not have any control over how their IDE is configured. As long as the LaunchPad enumerates in Windows with the ICDI showing in Device Manager then how to get Keil to see it is not something which we have the knowledge to assist with.

  • Hi,

    I agree that Texas and Keil are different companies but I also think that:

    a) you implement an ARM processor, Keil belongs to ARM and TI probably pays some royalties to ARM for each sold microcontroller. I wonder if you (TI) can push Keil/ARM because this new version is not good for your business or if you don't care at all (this is my impression).

    b) imagine you ara a car producer with leaded-fuel-engine and then the fuel supplier stops producing leaded fuel with any previous anouncement. Imagine that I purchased a car from you and I face the problem. Do you think that I will feel satisfied with your answer? will you try to find an alternative solution? (this was the case when there was a shift from leaded to unleaded fuel), and last but not least: will you continue selling cars ignoring this problem?

    Plese, tell me if you will update the lanuchpad TIVA or if you will discontinue it and sell a new model. This is someething I have the right to know, I think so.

    Have a nice day

    Marcos

  • Hello Marcos,

    I'll have to accept the fact I have some egg on my face regarding my initial responses to this topic.

    Doing further research into this, I have found that the release notes for uVision v5.29 specifically mentions the removal of support for Stellaris ICDI from the IDE. This was not done - to my knowledge - with our approval.

    As you surmised, that isn't a good message for the Tiva MCU's, and I will look into what occurred here and what needs to be done to get Stellaris ICDI added back in for future versions. If I had to take a guess, my suspicion about what may have happened is they removed it due to the "Stellaris" branding on the naming without realizing that Tiva also uses the Stellaris ICDI.

    In the meantime they would still be programmable with either older versions or by using JTAG.

    The Tiva LaunchPads are going to be around for a long time, and in fact we are working on a new TivaWare release which will include even more focus on support for both the EK-TM4C123GXL and the EK-TM4C1294XL (and by extension the EK-TM4C129EXL as well) by way of additional example projects to help with evaluation using the LaunchPad's.

    The LaunchPad's themselves are unlikely to be updated to new models.

  • Greetings,

    Might this issue produce the rare case when my small group ... 'Feels both poster Marco's & vendor (Ralph's) pain.

    Staff offers up 2 (potential) solutions:

    • we note that Keil has continued, Support for the J-Link.    Now my firm has used (both) the 'gone missing' ICDI & J-Link (as well as J-Trace) and we (along w/countless others) have judged the J-Link to be far superior.   (it is both the most popular - and most employed (and pirated) - in the world!)    Now this 'will add cost' (while increasing your operational satisfaction) yet there ARE 'Educational Versions' - which are 'near equals' of the standard (full priced versions) - yet are available at MAJOR Discount!     (And - at least recently - you do, 'Not have to pretend a Student/Educator Status!'
    • does not Ralph's 'investigation 'offer hope' that versions 'earlier than (dreaded)  uVision v5.29 - should work for you!   (i.e. support Stellaris ICDI... at least during this 'interim period' - while you & (perhaps) this vendor - approach Keil...)

    May we note that several major medical firms are clients - and the, use of 'research' proves a 'sore point' - 'investigation' is a far superior descriptor...   Many, many years of advanced schooling - coupled w/Millions of Dollars worth of specialized equipment - is the realm of 'researchers!'    (unfortunately - teachers & schools are hugely 'guilty' of word misuse - thus this alternative, more appropriate, substitution.)

  • Hello  and ,

    After raising the concerns here with Keil, a solution is now available for v5.29 and newer in the form on an add-on installer that provides the ICDI Debugger again: 

    Please try this out and let us know if you have any issues with using it.

    Also I'd like your feedback about how important it would be to have the ICDI within the compiler natively vs having this installer to provide the support as it is not clear yet if this is intended to be be the solution long term for all future releases of uVision. (cb1 you are most welcome to offer thoughts too!)

    http://www.keil.com/support/docs/4196.htm

  • Hi Ralph

    you are a master. Yes, it's working. 

    Many thanks for your really fast actions to fix this drawback

    My deepest gratitude

    Marcos

  • Hello Marcos,

    Credit here really goes to Keil/ARM for how quickly they acted and put up a solution. I was surprised by the fast resolution as well! All I did was mention the problem. :)

  • Marco's success is good news - and 'most pleased that vendor's Ralph' pursued his 'investigation' to completion.

    Firm/I used Keil till ~2007 - then switched to (paid) IAR.    Never looked back - and the Stellaris ICDI has been - and remains - present w/in IAR's selection listings.    (although most IAR users prefer 'J-Link and/or J-Trace' - found more suitable for this multi-vendor, high-performance IDE...)