What kernel version are you running? "uname -a"
You can use "dtoverlay -v ..." to get more debugging out of dtoverlay.
Have you checked the kernel logs for errors? "dmesg". If a driver fails to probe, then it won't claim the I2C address.
Can you confirm the output of "i2cdetect -l".
You can check for devices that have deferred via "sudo cat /sys/kernel/debug/devices_deferred". Unfortunately it isn't always the most helpful (I've tried it here without an MCP23017 connected, and it defers but with no reason logged).
You can use "dtoverlay -v ..." to get more debugging out of dtoverlay.
Have you checked the kernel logs for errors? "dmesg". If a driver fails to probe, then it won't claim the I2C address.
Can you confirm the output of "i2cdetect -l".
You can check for devices that have deferred via "sudo cat /sys/kernel/debug/devices_deferred". Unfortunately it isn't always the most helpful (I've tried it here without an MCP23017 connected, and it defers but with no reason logged).
Statistics: Posted by 6by9 — Tue Mar 26, 2024 5:47 pm