BQ76972: In SPI communication, after each byte sent is delayed, the chip returns 0XFFFF00 multiple times

Part Number: BQ76972

1, the current problem is that using the official demo code, there is a delay time for each byte sent in SPI communication. If this delay time is not added, it will cause communication problems. The return is 0XFFFF00.

Only the SPI part of the manual has the content of operation delay. Does the completion time listed in this table refer to the delay time required after sending a byte?

2. We find that in the process of SPI communication, sometimes after sending a byte, the chip will reply 0XFFFF00, repeat sending for many times, and still reply 0XFFFF00 until the number of retries is used up. I set a 50us delay after each send. Retry 5 times, which is about 250us time. If the number of retries is changed to 10, it is found that the maximum number of retries reaches 8. This is far beyond the execution time range given in the manual and affects our requirements for interaction time. What causes this? Is there a solution or a solution?

3、if the SPI needs at least 50us delay for each byte sent, and there may be multiple retries to send a byte, then we consider changing the communication mode to IIC. Because it seems that the IIC does not need delay, and we expect to reduce the communication time between the chip and the MCU. For the IIC communication mode, will the MCU communicate with the BQ76972 in less time and more efficiently? Is there any previous test data or information about IIC communication available? For example, how long it takes to read the voltage of a cell and how long it takes for the host to turn on the equalization using the command CB_ACTIVE_CELLS().

that‘s all  thank you。