Bruce Meacham Posted 4 hours ago Posted 4 hours ago I've spent a couple of days googling and "all the AI'ng" this and I just can't find anything that will get my Orange Pi 5 or Orange Pi 3 Zero Pin 3 or 5 to do anything at all. First, I'm running: v25.2.3 for Orange Pi 5 running Armbian Linux 6.1.99-vendor-rk35xx (similar for the zero) $ ls /dev/i2c* /dev/i2c-0 /dev/i2c-10 /dev/i2c-2 /dev/i2c-6 /dev/i2c-7 /dev/i2c-9 $GPIO readall SDA.5 | IN | 3 SCL.5 | IN | 5 (it says OFF on the zero) $sudo i2cdetect -y 2 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- I've tried.. \boot\ overlays=i2c2 I've also tried overlay .dts to turn off uart_a (shares the same pins) /dts-v1/; /plugin/; / { fragment@0 { target = <&i2c2>; __overlay__ { status = "okay"; }; }; fragment@1 { target = <&uart_A>; __overlay__ { status = "disabled"; }; }; }; No matter what I do the pins are all high, zero signal at all ever. What am I missing? Thanks! 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.