• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 238 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

LM63: Questions of LM63

Jimmy Lai
Expert 6845 points
Part Number: LM63

Dear Team,

We found the minimum hold time requirement changed to 0sec in SMBus 3.0, which is aligned with I2C hold time requirement.

 

Is the LM63 compatible with SMBus 3.0?

 

We also followed your previous comments to perform the I2C loop detection test for 1000 times. The LM63 can be detected during this test. Could you help to confirm the hold time failing can be waived?

Many Thanks,

Jimmy

  • 0
    TI__Mastermind 43815 points

    Hi Jimmy,

    LM63 was designed before the release of SMBus 3.0. It was not designed to support zero hold time and is not specified to support zero hold time. It is not compatible with this aspect of SMBus 3.0.

    thanks,

    ren

  • 0 in reply to Ren Schackmann
    TI__Expert 6845 points

    Hi Ren,

    We appreciated your great support.

    Understood.

     

    From the SMBus 3.0 spec, there is a note as below

     

    Since the LM63 can be detected with ~120ns hold time in our system, could you help to confirm if LM63 is designed to have the internal hold time mechanism?

    Many Thanks,

    Jimmy

  • 0 in reply to Jimmy Lai
    TI__Mastermind 43815 points

    The LM63 was designed for SMBus 2.0 which did not have this internal hold time requirement. The SMBus 3.0 document describes this change in detail, and why they chose to mimic I2C's hold time instead. It explains that the burden is placed on the receiving device to handle this condition, and LM63 was designed prior to this publication. 

    thanks,

    ren