CCS/CC2642R: i2c

If deadlock often occurs when calling I2C for data collection, I would suggest you to use sensor controller to do such task to avoid watchdog reset.

 I would like to ask i2c deadlock this problem is certain to exist。If not used sensor controller，is there any other way to solve it?

Can you show me how you use blocking i2c mode in your application?

The above shows the initialization and read-write drivers of i2c.

Do you connect I2C slave device when you test your codes?

I2C peripherals are always mounted on the MCU.

If I2C peripherals are always mounted, I see no reason it would be blocked and reset. Do you add pull-high circuit on I2C SCL/SDA lines?

Just pull up two pins of i2c, no other operation.

Based on your experience, what are the common causes of i2c deadlock

According to my experiences, it is usually caused by bad SCL/SDA connection. I suggest you to use protocol analyzer or scope to check your SCL/SDA signal.

This means that the peripheral connection suddenly breaks, causing the slave to fail to respond, and the MCU never reads the data, resulting in a deadlock

Hi,

As YiKai Chen mentioned, the first step would be to verify the integrity of the signals arriving on the slave (BTW, I could not the images you attached in your very first message).

For the rest, I understand you are transferring the I2C data in blocking mode. Correct? It means the device will block until all the I2C data are transferred. In your case, don't you think Callback mode is a better choice?

Kind regards,