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.

BQ25157: BQ25157 stuck when VBAT < 3.2V and VIN<4.2V

Part Number: BQ25157

Tool/software:


Hello,
I have an issue with the behavior of the BQ25157 in certain specific cases.
The system in which the BQ is embedded is standalone, with a battery powering the system — there is no external source other than the charger.

The battery used has an operating range from 3.2 V to 4.2 V.

The BATUVLO setting range only goes up to 3.0 V, so I disable this functionality (Register 0x16 bits [2–0] = 0b111).
My charger is quite low-power and its voltage varies, so I need to disable VINDPM (Register 0x18 bit 7 = 1b1).
These settings are volatile and therefore lost when I enter ship mode.

When the battery is at 3.3 V, I put the BQ25157 into ship mode to preserve battery life. If the battery remains on the shelf for a long time, it may discharge down to 3.0 V.
It’s when the battery drops below 3.2 V that I observe strange behavior:

1. If VBAT > 3.2 V, PMID is enabled when VIN > VBAT + VSLP → OK, charging works normally.
2. If VBAT < 3.2 V, PMID is enabled only when VIN > 4.2 V → OK, charging works, but why is there a 4.2 V VIN threshold now?
3. If VBAT < 3.2 V and VIN remains below 4.2 V, no charging occurs. If the charger is removed, PMID is NOT enabled, the always-on 1.8 V LDO stays active, and around 400 µA are drawn from the battey.

It there a solution to return into ship mode automatically if the charger failled to reach 4.2V I am afraid to kill the battery if 400µA are drown on a already discharged battery.

Please tell me if this behaviour seems normal for you?

Thank you for your help.

  • Hi,

    When the device is in shipmode, the register settings are reset to their default values so some of the register settings that are configured may be reset. Because of this the behavior you are seeing may be due to the following:

    1. If VBAT > 3.2 V, PMID is enabled when VIN > VBAT + VSLP → OK, charging works normally.

    This is fine, VBAT is above VBATUVLO required for Voltage at Power Up, and VIN crosses the threshold required for a sleep exit.

    2. If VBAT < 3.2 V, PMID is enabled only when VIN > 4.2 V → OK, charging works, but why is there a 4.2 V VIN threshold now?

    This is likely due to the register reset, VINDPM is re-enabled and set to its default value of 4.2V.

    3. If VBAT < 3.2 V and VIN remains below 4.2 V, no charging occurs. If the charger is removed, PMID is NOT enabled, the always-on 1.8 V LDO stays active, and around 400 µA are drawn from the battey.

    In this scenario, VIN being below the VINDPM threshold will prevent the device from powering up from VIN since it is current limited. Using the /MR press, are you able to exit ship mode as expected under this condition?

    Best Regards,

    Juan Ospina

  • This is likely due to the register reset, VINDPM is re-enabled and set to its default value of 4.2V.

    I agree but why in case # 1 BQ25157 remembers the VINDPM setting ? BQ was in ship mode during this test.

    4.2V on VIN should also be mandatory.

    Thank you for your help.

  • Hi Cedric,

    I'll try and recreate the behavior in lab so I can better analyze this issue. I'll follow up with additional information tomorrow.

    Best Regards,

    Juan Ospina

  • Hello, thank you for your help.
    Could you also explain the bahaviour of BQ25157 between 3.2V and 3.0V (3.0V is the default BATUVLOW threshold.) ?

    An other use case: 
    With VBAT = 3.1V. If I apply 4.2V on VIN with VBATUVLOW = 3.0V (Register 0x16 = 3b000) and remove Vin after; BQ25157 PMID is turned of and only VDD always on is enabled ( 400µA drown from the battery).
    What is BATUVLO threshold impact on PMID bus when no VIN is present?

    Than you very much for your help!

  • Hello,

    It appears that, in order for the device to be powered from battery, the battery voltage has to be greater than the 3.2V VBAT_POR threshold, rather than just VBUVLO. For instance, if the device is enabled first via VIN, then VBAT (<3.2V) is asserted, then the device will stay powered on only as long as VIN is powered. If VIN is removed, although VBAT is above 3.0V BUVLO, if it hasn't first crossed the 3.2V threshold then the device will not remain on.

    This seems to take place for the Shipmode exit as well, it effectively behaves as a POR driven by VIN first if shipmode is exited via VIN.

    I agree but why in case # 1 BQ25157 remembers the VINDPM setting ? BQ was in ship mode during this test.

    4.2V on VIN should also be mandatory.

    I believe the difference in this scenario is that, although VIN is high enough to trigger a shipmode exit, the VINDPM prevents the device from power from VIN. But since VBAT has crossed the VBAT_POR threshold, it is now being powered from VBAT. You can confirm this by attempting this test (Shipmode Exit via VIN with VIN < 4.2V) and measuring PMID voltage, which should be about equal to VBAT voltage. If you try it with VIN > 4.2V then PMID should be approximately VIN voltage.

    Unfortunately, this all means that in order to properly exit shipmode, VBAT will have to be greater than the 3.2V VBAT_POR requirement. Otherwise you will be dependent on VIN voltage in order to do so. If charging is enabled, and your VBAT is about 3.0V, then you might quickly cross that threshold. But if VIN is removed before then then PMID will remain low.

    Best Regards,

    Juan Ospina