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.