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.

DS32EL0124, DS32EL0421: Planned life time (EOL)?

Other Parts Discussed in Thread: DS32EL0124, DS32EL0421

Hi,

we plan to use pairs of DS32EL0124 / DS32EL0421 in a future design. Is there some information around its life cycle? Or even an estimation for its EOL?

I'm asking because the design will be tight focused on these chips which will make it very difficult to replace. And I doubt that there are replacables for it?

Maybe someone has a clue, would be great to know!

Thanks, best regards,

  • Hi Wolfgang,

    The short answer is that there is currently no estimation available for this device pair's EOL. However, TI will notify you up to one year in advance if an EOL occurs.

    Please see TI's obsolescence policy below:

    "We are not in a position to speculate on how long a TI component will remain in production, since factors like market demand, process efficiency, device reliability, and technology trends must be considered when TI decides how it will allocate its limited resources. Nonetheless, it is TI's intention to maximize customer service with a reliable source of product supply for as long as TI practically can, in order to optimize our long-term customer/supplier relationship. When products are made obsolete, Texas Instruments will provide notification of Product Obsolescence and offer a Life Time Buy (LTB) opportunity, where applicable. TI allows up to 12 months from the date of notification for an order to be placed, and allows an additional 6 months to take delivery of the ordered product."

    For more information on the obsolescence policy, please refer to TI Policies & Procedures: Process/Product Change Notification.

    There are currently no further plans for future generation of these specific products.

    Thanks,

    Michael

  • Hi Michael,

    thank you very much for the quick response and the reference to the EOL policy.

    We've expected this situation, but nevertheless we posted this question because it's quite difficult for a small developer team facing an upcoming one year EOL, which may start any time.

    Thanks,