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.

BQ4050: Abnormal number of cycles

Part Number: BQ4050

During the use of one of our batteries, the cycle count has changed to over 10,000 times, which is an obvious abnormal phenomenon. May I ask if this problem is related to the battery being in the UNSEAL mode? If it is in the UNSEAL_FULL_ACCESS mode, can such problems be eliminated

  • 您好,

    已经收到了您的案例,调查需要些时间,感谢您的耐心等待。

  • 你好,是否有调查到呢

  • Sealing only prevents the host uC from accessing data memory. It doesn't affect the Cycle Count.

    If the gauge is unsealed, then it's possible for the host uC to write to Cycle Count (which is in Gas Gauging->State) so this can cause the Cycle Count to exceed 10000.

  • Thank you for your reply. Maybe my question was not expressed clearly. Let me re-describe our problem. During our normal use, there was an abnormal change in the number of cycles. What kind of problem is this change related to? Looking forward to your reply.

  • Sealing only prevents the host uC from accessing data memory. It doesn't affect the Cycle Count.

    If the gauge is unsealed, then it's possible for the host uC to write to Cycle Count (which is in Gas Gauging->State) so this can cause the Cycle Count to exceed 10000.

  • Hello, we have just discovered the following patterns. Could you please help us take a look and see if there are any good suggestions?

    1. Both the number of cycles and the health status become abnormal simultaneously.
    2. The outliers for the number of cycles are two fixed values, 14336 and 15929, while the outlier for health is a fixed 103%.
    3. The outliers in the number of cycles and health status can automatically return to normal after some time.

  • Hi TI Experts

    We are currently experiencing multiple instances of abnormal battery cycle count readings in market applications. These abnormal readings are specific values (14336 and 15929). Furthermore, some cycle counts return to normal after a period of time (approximately one month) – not through a reset, but by continuing from the value prior to the abnormality. Based on these abnormal data points, it is difficult to attribute the issue to uC misoperation or unlocked registers causing the anomaly. Please assist in analyzing the cause as soon as possible. Thank you!

  • I just checked the FW. All it does is increment the cycle count by one if the coulomb count exceeds the cycle threshold. There isn't anything else in the code or gauge that would change this to enormous numbers suddenly (and back).

    The code is literally:

        uint16_t count = flash.CycleCount + 1;
        writeflash(flash.CycleCount, count);

    This is either a broken gauge (where flash memory fails) or the gauge is unlocked and the host inadvertently writes to the flash address for Cycle Count.

  • Thank you for your kind help. We will continue to check for other possible causes.