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.

TM4C Roadmap

Hi all, 

We're looking to replace the LM3S processor with something else.

Is there any information on the roadmap for the TM4C? Will it be available for the next 10+ years? 

Thanks,

Aleks

  • Hello Aleks,

    TM4C is in production and we do not plan to stop production of the device family TM4C123x and TM4C129x. There are no new devices planned for this year that are going to be in production soon enough.

    Regards
    Amit
  • Thanks for the reply Amit.

    Is there a guaranteed support period? I don't want to invest the resources to migrate if we'll have to do it again in less than 10 years.
  • Aleks,

    There is not a guarantee that you will be happy with.

    The semiconductor process is the key consideration.  There may be multiple products built on a process.  The TM4C12x product line is on a semiconductor process that is relatively young.  There are multiple TI products on the same process and the volumes are high.  I can not imagine discontinuing the process anytime soon.  But, it is still not a guarantee.

    Regards,

    Dave

  • That makes sense. Thanks for the reply.
  • Mr. Maples,

    May I commend you for such a fair, detailed & realistic writing?     Thank you - much appreciated.

    Along these (realistic) lines - may I ask you to comment upon the word, "Protect" - when describing the "security functions" - which this class of your MCUs provide?

    This recent link neatly summarizes:   https://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/t/433335

    My belief - aimed toward your MCUs and similar offerings from "others" - is that "protect" is too strong - and that, "resistant" instead - proves proper...

    Now to the original poster - you place a, "high hurdle" upon this vendor - do you not?    Yet - if well satisfied - cannot you regularly, "advance purchase" sufficient inventory - thus securing device availability?     (such is our tech firm's "modus operandi" - both here and w/other vendors...)

  • cb1,

    I don't have a good absolute answer for you.  Any type of protection or security is a continuum spanning from the very simple to ultra complex.  It is difficult to quantify with a few words without getting into the details.  The level of protection or security changes meaning relative to the expectations of the user.

    So, our marketing people take their best shot and then we try to help the user understand the details.

    Regards,

    Dave

  • Dave,

    Thank you - appreciated.

    My sense - having dealt w/this issue many times - "Protect implies a, "High Standard" - which may lull users into a, "False sense of security.""

    "Resistant" in contrast - provides a lower bar - easier for the vendor to meet - and hopefully encouraging the client-user to employ, "More rather than fewer" security methods to gain enhanced code safety...  

    Our findings - in dealing w/VC's and/or Investors - the use of "protect" and/or "research" triggers alarm bells which may be avoided via "resistant" and "investigate."    (i.e. our small tech firm always (& only) performs, "Design & Development" (D & D rather than R & D) - which better meets (IRS) directives...)