A new circuit design using the BQ25713 was done. Unfortunately there were some mistakes that are now corrected and we are trying to test.
I am now able to communicate reliably to the BQ25713 via I2C (thank you tech support from previous case). The issue now faced is that on the circuit board the BattDrv does not change when sending any I2C command. The python script that is being used works as expected on the eval board and is being used it to test the circuit design.
Things to Note from the Schematic:
- PGnd did not get tied to GND (fixed now)
- CELL_BATT Presz = 1.5V to be 1S (Voltage Divider of two 10kohm resistors
- Ilim has been left floating (when tied to a voltage it has a large ringing on the output and battery)
- disabled via 0x32[7] -ILim is 1.835V on the EVAL Board and 0.167V on mine (left floating and disabled via 0x32[7])
- Chrg_Ok is good
- Vsys to BATDRV is a static (-3.2V or -1.6V) and does not move
- EN_OTG is true (3.3V to the IC Pin)
- The BatFET (ie. Q10) was originally a N channel mosfet (though it needed to be a P Channel) and the board has been powered several times before this error was realized. It is now corrected to a P channel.
Notes:
- When Ilim is not floating (ie tied to 3.3V) the Vsys and Vbattery have a noisy decaying sinusoidal signal.
- When disabled via 0x32[7] then the output of BattDrv is static.
What is the best way to troubleshoot the BattDrv not changing at all?
Could the chip be bad since many incorrect hardware configurations were powered up? If so what is the best way determine it is bad.
Should I configure a new board that has not been powered?