i2c clock speed reduction when failing to communicate to a slave
Posted: Thu Jun 01, 2023 12:24 pm
Hi all,
i am facing a problem when my ESP32-S2 fails to communicate to an i2c slave, the problem is better described in the following.
At start the i2c port is set to work with a clock frequency of 400 MHz and it works fine until i disconnect the i2c slave. When i connect it again, the esp32s2 is able to start communicating with it again but at a much lower clock speed (around 5 kHz). Reading the values of configured with the function i2c_get_period(), i can notice that the returned value is not changed, however the clock frequency changes so it should be something related to the hardware i think.
Any one can explain this behaviour?
Thanks.
i am facing a problem when my ESP32-S2 fails to communicate to an i2c slave, the problem is better described in the following.
At start the i2c port is set to work with a clock frequency of 400 MHz and it works fine until i disconnect the i2c slave. When i connect it again, the esp32s2 is able to start communicating with it again but at a much lower clock speed (around 5 kHz). Reading the values of configured with the function i2c_get_period(), i can notice that the returned value is not changed, however the clock frequency changes so it should be something related to the hardware i think.
Any one can explain this behaviour?
Thanks.