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.

BQ7693006DBT I2C Interface crashed

Other Parts Discussed in Thread: BQ76930

Hi at all,

i was sending my issue to the technical support of ti and they replied that i should post my problem in this forum, so here it is...

we are using your bq76930 battery monitor chip for a battery pack for our new power tool. We did a lot of testing in our laboratory and also started field tests 3 weeks ago. During our laboratory test no failures occured, but in the field test one device stuck in a unsafe mode. In the following I will describe the Problem: The BQ7693006DBT communicates with a STM32F103RBT6 Microcontroller over its I2C Interface. We oriented our code design to the bq769x0 I2C Sample Code With CRC which could be downloaded on tiŽs homepage. And also the hardware design is according to tiŽs design considerations. During the field test the communication between the microcontroller and the bmc stuck. There was no chance to reactivate the communication. The bmc stuck in this operating state which he had when the failure occures. The discharge Mosfet was active and the Charge Mosfet was deactivated. The ALERT Line did not show an ALERT state. The only solution was to disconnect and reconnect the battery from the bmc and transit the device out of ship mode. My question now ist if there is a method to establish a more secure communication. Is this a well known issue with this device? I could not find any errata facing this problem. By the way it is not possible to provocate and recreate this failure again so it is very difficult to find a solution.

  • Seems the I2C bus is intermittently getting out of sync.
    In the event of the slave( bq76930) being unresponsive and if SDA is low, the master should send 9 clk pulses to reset. In the event of the SCLK low, cycle power to the device or generate a POR event.
  • Thank you for your fast response!
    we are allready sending 9clk pulses to clean the buffer.
    what do you mean with cycle power to the device?
    it is not possible to generate a POR reset except we will disconnect and reconnect the battery isnt it?
  • Yes, the only way to generate a POR ( to go below Vshut  is to disconnect and connect ) the battery. there is no HW reset pin on the device.  

    Also, please check if the following suggestion can help...

    For noise immunity , use time constant= 250us on the ALERT pin.

    Need Time constant on pulldown to settle within ~ 250uS to avoid the part from detecting residual ALERT pin voltage after status register CLEAR

    add  resistor ( ~500K) to GND. Also add Cap[ 500pF}to GND .