Working, tested with two i2c busses

[skieast]

This draft PR demonstrates one fix for the hang with the ESP32S2 when using wifi and i2c. Hang occurs when interrupting a program and resuming. Appears to fix #3743

This code only creates the i2c driver once per i2c controller/bus, never deleting it.

There must be another underlying issue causing this, perhaps inside the ESP IDF.

[jepler]

Does this allow the pins associated with the I2C device to be used for other purposes?

[skieast]

Does this allow the pins associated with the I2C device to be used for other purposes?
By that do you mean in the same program? If so I haven't tried that. In a separate program yes as the pins are still setup in the constructor. I will try some more testing tomorrow on a better test setup. Currently everything is hanging from dupont wires and tape.
Following is a snippet of code setting up the I2C. IO17 and IO18 were just convenient pins to use.

i2c = I2C(board.SCL, board.SDA)
while not i2c.try_lock():
    pass
print("I2C board.SCL board.SDA addresses found:", [hex(device_address) for device_address in i2c.scan()])
i2c.unlock()

i2c2 = I2C(board.IO17, board.IO18)
while not i2c2.try_lock():
    pass
print("I2C IO17 IO18 addresses found:", [hex(device_address) for device_address in i2c2.scan()])
print("After scan")
i2c2.unlock()

[dhalbert]

Maybe interesting: here is someone else who is doing install/delete/install, and having trouble: https://www.esp32.com/viewtopic.php?f=2&t=10995&p=44960

[skieast]

I've tested this with code that uses both i2c peripherals, one with two i2c devices on it. I can interrupt the code with CTRL-C, continue with CTRL-D with no apparent issues. At the same time wifi is pinging some internet address. Also editing code and saving works as expected. I do not know if leaving the wifi driver always installed has any power and deep sleep issues.

[tannewt]

Thank you!