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.

BQ79616-Q1: BQ79616 SOF and daisy chain crc error

Part Number: BQ79616-Q1
Other Parts Discussed in Thread: BQ79616

We connected 4 Bq79616 devices to BQ79600.

Immediately after a power ON reset and once BQ79616 devices started communicating, we observe the bit FAULT_COMM in FAULT_SUMMARY resistor gets set.

On further analyzing it was observed that all the BQ79616 reports Start of Frame Error (“RR_SOF” or “RC_SOF”)  and Daisy chain error (“RR_CRC” or “RC_CRC”).

If we break the daisy chain communication in forward direction and communicate in reverse direction, it was observed for BQ79616 1, 2, 3 devices still FAULT_COMM bit is set to 1, and no error for 4th device.

even for devices 1,2,3 none of relevant bits in fault_comm1,2 or 3 are set.

               

The good thing is even with these error status, we haven’t observed any functionality limitation.

  1. All the functionality works fine(including reading the cell voltage, bus bar voltage, cell temperature etc)

 

could you please let us know what can cause this behaviour?

  • Hi Rakesh,

    Apologies for the delay as our E2E system had some changes. Perhaps this was due to swapping direction but not completely following the full addressing routine to swap directions. Can you please check the datasheet section steps for Ring Architecture addressing to ensure the commands were followed properly?

    Thanks,

    Taylor

  • Hi Taylor,

    Sorry for confusion.

    Let me put with more clarity.

    These errors are present the moment we start communicating with BQ79616 devices.

    even a single read operation @ 10s these errors are getting reported.

    Later once we developed/enhanced our code for ring communication we observed these errors are not getting reported once we break communication.

  • Hi Rakesh,

    Is this on the EVM or on custom hardware? Has this been resolved?

    Regards,

    Taylor