Tool/software:
Hi There,
We have been having a couple of issues with the I2C communications on the BQ76942 device.
Firstly - we sometimes get garbled messages, or failed reads (Both with out host processor, and the EVM2400). This has been easily rectified by implementing the CRC functionaity on the I2C and re-reading failed messages.
Secondly - we have on occasion been able to lock ourselves out of the I2C communications on the BQ76942 device. This happens occasionally after an asynchronous reset of our MCU (which may occur during I2C traffic), and the BQ76942 is left in what appears to be a clock stretching state. Currently the only way we have been able to get around this is to shut down the BQ76942 using the RST_SHUT pin as the device will not recieve a reset command from either the host MCU or the EVM2400 in this state.
We are hoping that the I2C timeout configuration of Comm Type may be able to solve this second issue by forcing the I2C peripheral on the BQ76942 to be reset. But the listed options for Comm Type in the TRM do not support a configuration with both CRC and timeouts, which means in order to solve this second issue - we need to un-solve the first one.
Is it possible to configure this device to support both CRC and a timeout for I2C?
Thanks,
David
