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.

BQ25620: BQ25620RYKR/WQFN_18

Part Number: BQ25620

Tool/software:

The device keeps restarting by means of coding. During this process, it charges for 5 minutes and then does not charge for another 5 minutes, repeating this cycle continuously. After running for more than 10 hours, the device failed to charge. Through actual testing, it was found that the charging current was only 10mA, and the internal VINDPM register value was 7.04V. This led to the fact that the 5V adapter basically did not output any charging current. This register is set to run by default on our side and will not be rewritten. Let's check if there is any direction for improvement here.

  • Hello, 

    Thank you for reaching out via E2E. Please see my comments below. 

    Firstly, I can confirm that if VINDPM register is set to 7.04V and you are using a 5V adapter then the device will not charge. This is expected behavior when VINDPM setting is > VBUS voltage. 

    On BQ25620 device VINDPM power on default configuration is 4.6V and will not change on its own. If VINDPM value is 7.04V that means your I2C host wrote to REG0x08 and changed the setting. I recommend you double check your firmware implementation. 

    Additionally, as confirmation of VINDPM setting in your test what is the hex (or binary) value you read from REG0x08 and REG0x09? 

    Best Regards,

    Garrett 

  • The following is the value read out from the register.
    reg 0 ff
    reg 1 ff
    reg 2 40
    reg 3 6
    reg 4 20
    reg 5 d
    reg 6 40
    reg 7 6
    reg 8 0
    reg 9 16
    reg a 20
    reg b 3
    reg c c0
    reg d f
    reg e 0
    reg f b
    reg 10 50
    reg 11 0
    reg 12 a0
    reg 13 0
    reg 14 6
    reg 15 5d
    reg 16 a3
    reg 17 4f
    reg 18 4
    reg 19 c0
    reg 1a 3f
    reg 1b 25
    reg 1c 3f
    reg 1d 4
    reg 1e b
    reg 1f 0
    reg 20 4
    reg 21 9
    reg 22 80
    reg 23 0
    reg 24 0
    reg 25 0
    reg 26 30
    reg 27 0
    reg 28 0
    reg 29 0
    reg 2a 0
    reg 2b 0
    reg 2c 0
    reg 2d 0
    reg 2e 0
    reg 2f 0
    reg 30 0
    reg 31 0
    reg 32 0
    reg 33 0
    reg 34 0
    reg 35 0
    reg 36 0
    reg 37 0
    reg 38 2

    After the equipment malfunctioned, the values read out were all 7.04.Given this situation, if we want to test whether it is the I2C host causing this anomaly, are there any suggested testing methods?

  • Hello, 

    Thank you for providing your register outputs from the BQ25620 device. Both VINDPM register and status register outputs confirm VINDPM = 7.04V and the device is in VINDPM status. 

    You will need to debug the firmware implementation on your I2C host to determine what is causing VINDPM to be changed. As I am no expert on the I2C host being used in your system I cannot provide specific suggestions to test further.

    In general I recommended checking if all BQ25620 registers read out expected value after your initial configuration. This will allow you to check whether issue is with initial configuration or if your I2C host is unexpectedly writing to the charger VINDPM register at a later time. 

    Best Regards,

    Garrett