hardware i2c deprecated

[jbar]

You did not tell which board you use. Is it an ESP32? Or RPi Pico? And you could show the error message which you get.

The following message pops up in the shell:
Warning: I2C(-1, ...) is deprecated, use SoftI2C(...) instead

I'm using an ESP32.

[JDRBoston]

Thank you for this update about how i2c can be instantiated in the newer MicroPython versions. Is there a way to turn off the "Warning: I2C(-1,...)..." message that is sent to shell? I am using the hardware I2C pins of my device and the machine.I2C() instantiation accordingly. I don't want the user to see the "Warning" when it does not apply and worry. Alternatively, is there a down side to using machine.SoftI2C() with the hardware I2C pins declared. I'm likely wrong, but would this then cause bit banging the port and cause some speed and other software overhead when it isn't needed. Or, does SoftI2C() default to using the hardware I2C resources when the hardware I2C pins are defined. Thank you, J

[jimmo]

Thank you for this update about how i2c can be instantiated in the newer MicroPython versions. Is there a way to turn off the "Warning: I2C(-1,...)..." message that is sent to shell? I am using the hardware I2C pins of my device and the machine.I2C() instantiation accordingly. I don't want the user to see the "Warning" when it does not apply and worry. Alternatively, is there a down side to using machine.SoftI2C() with the hardware I2C pins declared. I'm likely wrong, but would this then cause bit banging the port and cause some speed and other software overhead when it isn't needed. Or, does SoftI2C() default to using the hardware I2C resources when the hardware I2C pins are defined. Thank you, J

If you were previously using

Code: Select all

machine.I2C(-1, sda=..., scl=...)

then you were never using hardware I2C, it was always software (bit banged).

The deprecation warning is to encourage you to make it explicit (i.e. use SoftI2C).

On ESP32 pins can be anything, there's no "hardware i2c pins" because any pin can be mapped to a given i2c peripheral.

If you want to use the hardware I2C, you must specify a bus ID (0 or 1) and the pins.

[JDRBoston]

Thank you, jimmo!