• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 63 subscribers
  • Views 171 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.

BQ35100: Basic questions about I2C rise/fall time regulation

Ryotaro Fukui
Intellectual 2345 points
Part Number: BQ35100

Hello team,

I received some questions from my customer about I2C rise/fall time of BQ35100. It may be a basic question, but I would appreciate if you could give us an advice about it.

The TR/TF for I2C in BQ35100 appears to be listed in the Datasheet 6.14 as max 300ns each, but should I be strictly adhered to?

It would be very helpful if you could explain what will be the problem if the requirements are not met.

The customers thinks that TR and TF are not relevant to the data ingestion itself, and they want to know what these specifications are for.

If it is necessary to strictly follow the TR/TF, is the reason common to any other devices such as amplifiers?

Best Regards,

Ryotaro Fukui

  • +1
    TI__Genius 11535 points

    Hi Ryotaro Fukui,

    Yes this should be strictly adhered to. It can cause timing and capturing issues, which in turn will prevent any communication with their gauge. This document does a pretty good job of explaining it. 

    Best,

    Jessica

  • 0 in reply to Jessica H.
    TI__Intellectual 2345 points

    Hi Jessica,

    I am sorry for my late reply. I received a feedback from the customer.

    The customer understood the potential issues that could arise if he did not follow rise / fall time, and has commented that he will continue to use the device in accordance with the regulations.

    Thank you for your advice. I would like to declare this case closed here.

    Best Regards,

    Ryotaro Fukui