You hadn't said that it worked on Raspberry Pi OS but didn't on your Yocto build.
We supply defconfigs for the relevant platforms, and strongly recommend they are used.
If you're getting timed out errors after the rpi-panel-attiny-regulator driver has initially probed, then you're likely to have messed up the pinmuxing so RP1 is no longer connected to the display.
Check GPIOs 38-41 with "sudo pinctrl get". They should reportOr put a logic analyser on the I2C lines.
We supply defconfigs for the relevant platforms, and strongly recommend they are used.
If you're getting timed out errors after the rpi-panel-attiny-regulator driver has initially probed, then you're likely to have messed up the pinmuxing so RP1 is no longer connected to the display.
Check GPIOs 38-41 with "sudo pinctrl get". They should report
Code:
38: a3 pu | hi // CD0_SDA/GPIO38 = SDA639: a3 pu | hi // CD0_SCL/GPIO39 = SCL640: a2 pu | hi // CD1_SDA/GPIO40 = SDA441: a2 pu | hi // CD1_SCL/GPIO41 = SCL4Statistics: Posted by 6by9 — Mon Feb 26, 2024 11:39 am