• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 63 subscribers
  • Views 152 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.

BQ25890H: Clarification on INT behavior on VBUS disconnect

Marcus Niekraszewicz
Prodigy 80 points
Part Number: BQ25890H

I'm trying to reliably detect a VBUS disconnect, and I'm having trouble understanding the intended behavior.

The datasheet states that INT should be asserted in the following cases:


• USB/adapter source identified (through PSEL or DPDM detection, with OTG pin)
• Good input source detected
– VBUS above battery (not in sleep)
– VBUS below VACOV threshold
– VBUS above VVBUSMIN (typical 3.8 V) when IBADSRC (typical 30 mA) current is applied (not a poor source)
• Input removed
• Charge Complete
• Any FAULT event in REG0C

I'm receiving the interrupt as expected when I connect an input source, and can see that VBUS_GD has been asserted. But if I disconnect the input source while VBUS_STAT is still 000, I'm not receiving any interrupt. Is this expected behavior?

Thanks,
Marcus

  • +1
    TI__Mastermind 31840 points

    Hi Marcus, 

    Yes this is the expected behavior. When the input source is connected and then quickly disconnected before VBUS_STAT is set following input source type detection there will not be an interrupt. After the conclusion of input source type detection an input source removal will generate an interrupt. 

    If AUTO_DPDM_EN is set to 0 to disable d+/d- detection, you can expect the device to generate an interrupt for input removal even for the scenario when the input is plugged in and then quickly removed. 

    Regards,

    Garrett