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.

BQ25720: Spurious register 0x32 setting change

Part Number: BQ25720
Other Parts Discussed in Thread: EV2400

Hello,
we are using BQ25720 in a system with a exchangeable 4s LiIon battery.

Now we have spurious issues with the BQ25720 disconnecting from supply, showing a SYSOVP bit set in register 0x20 = ChargerStatus. Also register 0x32 = ChargeOption3 changed its value from the reset value 0x434 to 0x20. Our host firmware never sets this register so it is very unlikely to be changed this way. Also we see a short voltage spike > 20V towards the battery and meanwhile we have four batteries being destroyed.
We want to ask TI for assistance in this case. Are there any known issues like that? What is the meaning of value 0x20 in register 0x32 = ChargeOption3 (only bit OTG_VAP_MODE set)? What can we do to keep register 0x32 from changing its value?

Thanks for any help

Kind regards

Martin Mensch

  • Hi Martin,

    I would first suggest to check SMBus log for any read /write. You can isolate the SMBus from the host and manually connect to a computer using EV2400. 

    If EN_PORT_CTRL is set to zero by accident, the BATFET will be floated. This is not allowed. 

    Regards,

    Tiger