Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 8013

Advanced users • Re: MCP23017 overlay error -EIO: can't write IOCON 32

$
0
0
..
You're on a 6.1.21 kernel, which is very old now. Presumably this means you're still on Bullseye too.

The backtrace looks to be that it is objecting when enabling the interrupt line for the MCP23017. I'd check that you have got your interrupts defined to use the correct GPIOs in the dtoverlay, and nothing else is trying to use the same GPIO.
from the log posted

Code:

Raspberry Pi Zero W Rev 1.1PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"NAME="Raspbian GNU/Linux"VERSION_ID="11"VERSION="11 (bullseye)" Raspberry Pi reference 2024-10-22Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 511ffc4ff1529cb6f3eb3c8143d21a30faa1c43e, stage2 Linux remote 6.1.21+ #1642 Mon Apr  3 17:19:14 BST 2023 armv6l GNU/Linux
so yes! Old kernel on bullseye OS.

Code:

GPIO 0: level=1 fsel=0 func=INPUTGPIO 1: level=1 fsel=0 func=INPUTGPIO 2: level=1 fsel=4 alt=0 func=SDA1GPIO 3: level=1 fsel=4 alt=0 func=SCL1
most likely enabled fo no good reeason (note: as the debug info for the overlays is not there this is just an assumption). There might be some HAT connected because of

Code:

001553.467: brfs: File read: /mfs/sd/overlays/overlay_map.dtb
looks odd

Code:

[   18.458076] i2c-gpio b.i2c: using lines 10 (SDA) and 11 (SCL)[   18.460179] i2c-gpio ffffffff.i2c: error trying to get descriptor: -16[   18.460232] i2c-gpio: probe of ffffffff.i2c failed with error -16
how do you start that DPI display?

Statistics: Posted by aBUGSworstnightmare — Tue Dec 17, 2024 7:12 pm



Viewing all articles
Browse latest Browse all 8013

Trending Articles