• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 8 subscribers
  • Views 116 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

UCC33420:

UCC33420: When is UCC33420 RTM?

Kazuya Nakai59
Guru 21165 points
Part Number: UCC33420

Tool/software:

Hello guys,

One of my customers is waiting for UCC33420 RTM.

The following E2E says that the device RTM is December 2024. 
https://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1383160/ucc33420-rtm

But UCC33420 has not been released yet.

Could you please tell me when the device RTM?

Your reply would be much appreciated.

Best regards,
Kazuya.

  • 0
    TI__Genius 11241 points

    Hi Kazuya,

    UCC33420-Q1 (automotive) has been RTM back in 12/18/2024. UCC33420 (industrial) is planned to be RTM soon (before the end of this month). The only difference between both is the WF (wettable flank) in the package.

    Thank you

  • 0 in reply to Manuel Alva Hernandez
    Guru 21165 points

    Hi Manuel,

    Thank you very much for your reply.

    I understood TI was going to release UCC33420 by the end of February.
    Also I understood ucc33420-q1 has VSON package with wettable frank.

    But I found on TI web site that TI code of PUCC33420RAQR package is RAQ(VSON-FCRLF).
    I think RAQ(VSON-FCRLF) is a package with wettable frank.

    Is my thought correct?

    Thank you again and best regards,
    Kazuya.

  • 0 in reply to Kazuya Nakai59
    TI__Genius 11241 points

    Hi Kazuya,

    Both have the same package RAQ(VSON-FCRLF) but the Q1 version has the additional WF. I hope this helps.

    Thank you

  • 0 in reply to Manuel Alva Hernandez
    Guru 21165 points

    Hi Manuel,

    Thank you very much for your explanation.

    We understood.

    Thank you again and best regards,
    Kazuya.