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.
Tool/software:
Hello,
I have a question about an I2C issue that I am trying to troubleshoot for root cause identification.
I have an I2C peripheral that I have been sending commands to immediately on powering up the I2C bus without incorporating a wait time before the I2C bus is fully powered up. After communication is completed, I then attempt to power down the I2C bus.
The problem is that 99.999% of the time this works ok, but 00.001% of the time the MCU seems to hang at powering down the I2C bus with the watchdog eventually kicking in and resetting the MCU.
I know sending commands before the I2C bus is fully powered up is not best practice here and I will be adding some delay to this step, but I would like to know if this could cause the MCU lockup?
Here is the scope where communication starts immediately after activating the I2C bus before it can reach full power:
Thanks.