• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 19 subscribers
  • Views 215 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.

SN74LVC1G17-Q1: Rev.C PCN

Yuto Sakai
Mastermind 6100 points
Part Number: SN74LVC1G17-Q1

Hi,

Could you tell me about the revision of the Rev.C data sheet?
Why did you return the values of V +, V-, ΔV, and tpd to Rev.A specifications?
Are there any changes to inspection standards or shipping inspections?
The customer is concerned about re-evaluation, so could you give me information?

Best regards,
Yuto Sakai

  • 0
    TI__Mastermind 42670 points

    Hey Yuto,

    The PCN issued to all customers using this device will contain all of this info.

  • 0 in reply to Dylan Hubbard
    Mastermind 6100 points

    Hi Dylan-san,

    Thank you for your reply.

    The PCN says "To accurately reflect device characteristics."
    It changes the device threshold and rise time. Is these a correction of a typo?

    I understand that some test conditions have not changed. Is this understanding correct?

    Best regards,
    Yuto Sakai

  • 0 in reply to Yuto Sakai
    TI__Guru* 96591 points

    Hello Sakai-san,

    The SN74LVC1G17-Q1 datasheet (revision A) was in an older format than what we currently use. When we released the DRY package option for this device, the datasheet had to be updated to the latest format before the new package could be added.

    Often the first step in updating a datasheet to our latest format includes copying an existing datasheet. The values and other content are then modified to match the device to be released.

    In this case, due to human error, the datasheet was released before all values had been updated to match the SN74LVC1G17-Q1. We quickly realized the mistake and re-released the datasheet with the corrections you see.  If you check version A of the datasheet, you will see that no values have changed from version A to version C -- version B included a significant amount of incorrect values due to this mistake.