Now I am trying return LCD i2c bus connection to CM4 I2C0 (GPIO0/GPIO1)
I add in config.txtIn lcd overlay I useLooks like DT for LCD and touch controller recognize i2c0
This part looks fine
I check pcb. It have good connection on GIO00 and GPIO1 pins.
Problem - I don't see any i2c bus probe during kernel boot (on oscilloscope).
I add in config.txt
Code:
dtoverlay=i2c0dtoverlay=vc4-kms-v3d,noaudiodtoverlay=vc4-kms-dsi-ti-sn65dsi83-10inch-overlayCode:
fragment@3 { target = <&i2c0>; __overlay__ { #gpio-cells = <2>; #address-cells = <1>; #size-cells = <0>; status = "okay";Code:
dmesg | grep -i 0-00 [ 0.356778] brcmstb-i2c fef04500.i2c: @97500hz registered in polling mode[ 0.357557] brcmstb-i2c fef09500.i2c: @97500hz registered in polling mode[ 2.444710] ilitek_ts 0-0041: protocol init failed: -5[ 2.449913] ilitek_ts: probe of 0-0041 failed with error -5[ 2.455893] i2c 0-002c: Fixed dependency cycle(s) with /panel/port/endpoint[ 2.597004] sn65dsi83 0-002c: supply vcc not found, using dummy regulator[ 2.756030] sn65dsi83 0-002c: failed to lock PLL, ret=-121[ 2.757996] sn65dsi83 0-002c: Unexpected link status 0xc2411740Code:
raspi-gpio getBANK0 (GPIO 0 to 27):GPIO 0: level=1 alt=0 func=SDA0 pull=UPGPIO 1: level=1 alt=0 func=SCL0 pull=UPGPIO 2: level=1 alt=0 func=SDA1 pull=UPGPIO 3: level=1 alt=0 func=SCL1 pull=UPI check pcb. It have good connection on GIO00 and GPIO1 pins.
Problem - I don't see any i2c bus probe during kernel boot (on oscilloscope).
Statistics: Posted by Kuzma30 — Wed Mar 06, 2024 4:27 pm