PiicoDev Sensor - Connection error

Support Raspberry Pi
1

Hi
I am following the tutorial to test the Atmospheric Sensor (BME280) on my Raspberry Pi Pico, and I keep getting OSError: [Errno 5] EIO
Here is the full error:

MPY: soft reboot
PiicoDev could not communicate with module at address 0x77, check wiring
Traceback (most recent call last):
  File "main.py", line 9, in <module>
  File "PiicoDev_BME280.py", line 32, in __init__
  File "PiicoDev_BME280.py", line 29, in __init__
  File "PiicoDev_BME280.py", line 64, in _read16
OSError: [Errno 5] EIO
MicroPython v1.19.1 on 2022-09-13; Raspberry Pi Pico with RP2040
Type "help()" for more information.

I connected and disconnected all the cables, rebooted the computer, etc., but keep getting the same error.

PXL_20220914_053927883
PXL_20220914_0539278831920Ă—2560 341 KB

I thought something could be broken, but the sensor’s light is on, and I tested the Pico following the Led tutorial. Seems to be working fine

Any help would be great.
Cheers

1 Like
2

I’ve had the same issue with my Pico W, I think it’s an issue with the latest nightly build of micropython.

It’s also been mentioned here: PiicoDev with the Pico-W - #6 by James46717

I think if you go back a couple of versions of micropython it will work, otherwise hopefully the issue gets ironed out soon!

7 Likes
3

Thanks @ShaneC!
I went back to MicroPython v1.18 and that solved the issue

6 Likes
4

Im having the same issue using
rp2-pico-w-20220926-unstable-v1.19.1-451-gbdbc44474.uf2

%Run -c $EDITOR_CONTENT
PiicoDev could not communicate with module at address 0x77, check wiring
Traceback (most recent call last):
File “”, line 9, in
File “PiicoDev_BME280.py”, line 32, in init
File “PiicoDev_BME280.py”, line 29, in init
File “PiicoDev_BME280.py”, line 64, in _read16
OSError: [Errno 5] EIO

anyone got this working?

5

Hi Phil,

There is a bug in the nightly build for the Pico W that breaks the I2C interface, unfortunately that bug has now been baked into every nightly release firmware version on the micropython site.

James has found a pre-release version of the Pico W firmware that does not feature the bug, you can find it in his thread below.

2 Likes
6

Hi Trent, thanks for the info.

I can confirm that this has now resolved this!

image
image749Ă—631 28 KB

3 Likes