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

Part Number: LM63

Dear Team,

It is about SMBus timing, the problem description is as follows:
1. Does this material comply with the SMBus 2.0 or 3.0 specification?
2. If tHD;DAT (ns) is smaller than the specification, is there any suggested way to adjust it?

Many Thanks,

Jimmy

  • LM63 was released before SMBus 3.0 was published. It was designed for SMBus 2.0 specification, but that does not make it incompatible with 3.0. 

    There is a difference between HDDAT created by the controller and HDDAT created by the target (LM63.) It's not possible to change the timing of HDDAT created by LM63. The LM63 may misinterpret transactions where the controller violates LM63's HDDAT requirement. Generally when HDDAT is violated by the controller, the target (LM63) does not ACK the address frame of the transaction, and the transaction cannot proceed.

    thanks,

    ren

  • Hi Ren,

    Thanks for your reply, I already understand that we should follow the 2.0 specification but I would like to confirm whether there are other ways to adjust SMBus timing(through SW or HW)?

    If not, do we have suitable solution can recommend to customer? p2p is better.

    Many Thanks,

    Jimmy

  • Jimmy, 

    I previously noted that it's not possible to change the timing of HDDAT created by LM63. Further, the LM63 may be incompatible with a controller that creates zero hold time. There's nothing that can be done about this from LM63 perspective.

    thanks,

    ren