BQ24610: The battery level shows wrong when the battery pack is plugged into the target device.

Part Number: BQ24610
Other Parts Discussed in Thread: BQ78350, BQSTUDIO

Tool/software:

Dear,

When the battery pack is connected to the complete machine, the serial port information monitored via J-LINK shows the battery level as 0%,

and the same 0% is displayed on the machine itself. However, the complete machine does not shut down, indicating that it only shows no power while there is actually remaining battery.

However, when measuring the battery pack independently with EV2300, the battery level is normally 85%.
Why is the battery level displayed incorrectly on the complete machine only when the battery pack is connected to it?
This ia main board SCH.
This is Battery Pack SCH.
  • Hello Haoya,

    When the battery pack is connected to the complete machine, the serial port information monitored via J-LINK shows the battery level as 0%,

    and the same 0% is displayed on the machine itself. However, the complete machine does not shut down, indicating that it only shows no power while there is actually remaining battery.

    However, when measuring the battery pack independently with EV2300, the battery level is normally 85%.
    Why is the battery level displayed incorrectly on the complete machine only when the battery pack is connected to it?
    This ia main board SCH.

    This issue does not seem related to the BQ24610. I'm not sure what the J-Link is, or how you are measuring the 0%.

    Best Regards,

    Christian.

  • Hi Christian,

    Detect battery level via MCU's SMBC/SMBD lines communicating with battery pack BQ78350.

    J-Link is a serial port tool used for detecting MCUs,output MCUlog.

    This is critical SCH.

  • If the EV2300+GUI shows 85% then this looks to be a problem with the smbus communication on the target hardware. I recommend checking if the traffic on smbus/I2C is correct.

  • Hi Dominik,

    Not all battery packs will cause this issue when plugged into the target hardware, and the probability of occurrence is roughly 0.3%.

    Does this seem more like an SMBUS hardware communication issue or a software configuration issue?

  • It's difficult to say - this would have to be checked with an smbus analyzer when the 0.3% error occurs. I can't say what the root cause is. Once it reads 0%, is this permanent on the target hardware or does the next smbus read return correct results?

  • Hi Dominik,

    It is this permanent.

  • If it's permanent but it works in bqStudio then I would hook up an smbus sniffer and check the bus while your host reads SOC.