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.

BQ25710: Issue with CHRG_OK pin is always low

Part Number: BQ25710
Other Parts Discussed in Thread: BQ25720

Tool/software:

Hi Team,

    we are using BQ25710 charger IC in our custom designed board to charge the 3 cell smart battery (RRC-2040-2). we can able to charge the battery but CHRG_OK pin is always low. please the configuration settings used for communication. 

Observation / issues:

CHRG_OK pin is always low

ADCVSYSVBAT register read value 9 V instead of 12 V

ADCVBUS/PSYS register value VBUS equivalent to 1.9 V instead of 5 V and PSYS is always 0 V

Settings:

Communication: I2C

Device address: 0x09H

VBUS: 5 V

I2C Communication between MCU and Charger IC is working properly and we are able read and write the registers. Please find the register log given below:

SMBus ADDR REGISTER NAME TYPE DESCRIPTION SMBUS READING
12H ChargeOption0() R/W Charge Option 0 0xE70E
14H ChargeCurrent() R/W 7-bit charge current setting
LSB 64 mA, Range 0 mA - 8128 mA
0x0000
15H MaxChargeVoltage() R/W 12-bit charge voltage setting
LSB 16 mV, Default: 1S-4200mV, 2S-8400mV, 3S-12600mV, 4S-16800mV
0x3130
30H ChargeOption1() R/W Charge Option 1 0x0211
31H ChargeOption2() R/W Charge Option 2 0x02B7
32H ChargeOption3() R/W Charge Option 3 0X0030
33H ProchotOption0() R/W PROCHOT Option 0 0X4A65
34H ProchotOption1() R/W PROCHOT Option 1 0X81A0
35H ADCOption() R/W ADC Option 0X2000
20H ChargerStatus() R Charger Status 0X8000
21H ProchotStatus() R Prochot Status 0XA800
22H IIN_DPM() R 7-bit input current limit in use
LSB: 50 mA, Range: 50 mA - 6400 mA
0X4100
23H ADCVBUS/PSYS() R 8-bit digital output of input voltage,
8-bit digital output of system power
PSYS: Full range: 3.06 V, LSB: 12 mV
VBUS: Full range: 3.2 V - 19.52 V, LSB 64 mV
0X1E00
24H ADCIBAT() R 8-bit digital output of battery charge current,
8-bit digital output of battery discharge current
ICHG: Full range 8.128 A, LSB 64 mA
IDCHG: Full range: 32.512 A, LSB: 256 mA
0X0000
25H ADCIINCMPIN() R
8-bit digital output of input current,
8-bit digital output of CMPIN voltage
POR State - IIN: Full range: 12.75 A, LSB 50 mA
CMPIN: Full range 3.06 V, LSB: 12 mV
0X0000
26H ADCVSYSVBAT() R 8-bit digital output of system voltage,
8-bit digital output of battery voltage
VSYS: Full range: 2.88 V - 19.2 V, LSB: 64 mV
VBAT: Full range : 2.88 V - 19.2 V, LSB 64 mV
0X0000
3BH OTGVoltage() R/W 12-bit OTG voltage setting
LSB 8 mV, Range: 3000 mV – 20800 mV
0X0000
3CH OTGCurrent() R/W
7-bit OTG output current setting
LSB 50 mA, Range: 0 A – 6350 mA
0X0000
3DH InputVoltage() R/W
8-bit input voltage setting
LSB 64 mV, Range: 3200 mV – 19520 mV
0X0280
3EH MinSystemVoltage() R/W
6-Bit minimum system voltage setting
LSB: 256 mV, Range: 1024 mV - 16182 mV
Default: 1S-3.584V, 2S-6.144V, 3S-9.216V, 4S-
12.288V
0X2400
3FH IIN_HOST() R/W
6-bit Input current limit set by host
LSB: 50 mA, Range: 50 mA - 6400 mA
0X4100
FEH ManufacturerID() R Manufacturer ID - 0x0040H 0X0040
FFH DeviceID() R Device ID 0X0089

Kindly look into this issue and give your feedback as soon as possible.

  • Hi, Sabbani,

    The charger status looks normal. Does the charger operate under 12V? CHGOK needs a pull-up rail. Please share your schematic when available. 

    Regards,

    Tiger

  • Hi Tiger,

    The charger is operating under 12 V and we are not allowed to share the schematic in forum. 

    We have a pull up to the internal LDO - VDDA (pin 7) with 10K resistor for the charge ok pin and the Vsys is 12.5V and Vbus is 5V and Battery Volt is 12V.

    Query regarding I2C communication:

    We are using I2C to communicate with the charger IC and slave address used is 0x09H and the pullup used is 4.7 k. In the datasheet, we have device address(0x09 H) and SMBUS address (0x12 H). Do we have to use I2C or SMBUS for communication.

    If possible please share your TI Email ID so that if required I can setup a teams meeting. 

    Please follow up with k-vashisht@ti.com for more information.

     

  • Hi, Sabbani,

    BQ25720 is a SMBus device, thus we use SMBus for communication. There is a slight difference between I2C and SMBus. The SMBus reads registers in word format, instead of multiple (>3) bytes.

    The CHRGOK is a little strange. Did you see this issue on the TI EVM or other boards?

    The other two questions are actually related to how to interpret the register values. 

    ADCVSYSVBAT register read value 9 V instead of 12 V

    There is a 2.88V offset on the VSYS and VBAT reading. 

    ADCVBUS/PSYS register value VBUS equivalent to 1.9 V instead of 5 V and PSYS is always 0 V

    Your input voltage is set at 3.84V, which indicates the VBUS =5.1V or so. You may need to enable ADC to read the VBUS and PSYS. 

    Regards,

    Tiger

  • Hi Tiger,

     we can able to communicate with charger IC through I2C and we can able to read all the registers. Please let us know if you want to read any specific register.

    This issue was going on from few weeks now and we need to resolve the issue asap as this holds our gerber release. please let us know if can able to join a teams call tomorrow. please share your email ID so that we can send you the invitation.

  • Hi, Sabbani,

    See below the startup waveform taken from the BQ25710EVM. Could you repeat and take a similar waveform?

    Regards,

    Tiger

  • Hi Tiger,

    Will capture the waveform and get back to you. In our design Vsys is 12 V and whenever No LION battery is connected we are getting Vsys of 9 V(powered by Type C wall mount adapter 3 A Rated) . is it a normal behaviour? Our Vbus voltage is 5 V.

  • Hi Tiger, 

    Here are the captures we got:

    1. With Vsw1(yellow) and Vbus_in (Blue)

    2. With Vsw1(yellow) and Chrg_ok (Blue)

    3. With Vbus(yellow) and VDDA(Blue)

    Please give us your feedback asap as we need to complete it urgently.

  • The CHRGOK is a little strange. Did you see this issue on the TI EVM or other boards?

    I suspect this is a single incident. I would like to suggest ABA swap. 

    "The A-B-A Swap Method is a simple cross check test, which can confirm the observed issue is not systemic.

    • A-B-A Swap Method
      (1) Remove the suspected component (A) from the original failing board.
      (2) Replace the suspected component (A) with a known good component (B) and check if the original board now works properly.
      (3) Mount the suspected component (A) to a known good board and see if the same faliure occurs on the good board.

    Step 3 is important because it helps us to exclude any possibility that the issue is caused by a systemic issue or the interaction of multiple slightly bad components on a good board."

    Let me know the results. 

    Regards,

    Tiger

  • is it a normal behaviour? Our Vbus voltage is 5 V.

    This is normal. Without battery, the system regulates at minimum system voltage, which is 9.216V.