wouldn't it be so much simpler when simply telling us which GPIO signals you've connected to the DSI connector? You're speaking of how you've used overlays, what you've done here and there, but not a single word on which GPIOs you've used for the I2C...
thank you for the help, I had a look at both the files and can confirm the changes they make should in theory fix the issue. Unfortunately, even after adding device_tree=bcm2712-rpi-cm5-cm4io.dtb the behavior doesnt change. This is what I experience currently, regardless of whether said line was added:
Adding dtoverlay=vc4-kms-dsi-7inch causes NO display output nor touch recognition on CM5 but works fine on CM4
Adding dtoverlay=vc4-kms-dsi-7inch,dsi0 or dtoverlay=vc4-kms-dsi-7inch,dsi1 have display out but no touch however with dsi0 specified, it thinks there is a touch screen and the touchscreen does work when I remote into it via VNC but display is blank/unpowered.
Adding BOTH dtoverlay=vc4-kms-dsi-7inch,dsi0 and dtoverlay=vc4-kms-dsi-7inch,dsi1 makes the display turn on AND touch works, however the touch is mapped to the imaginary dsi0 display. I was only able to realize this because touching the far right of the display allowed the cursor to peek through the far left. It seems adding device_tree=bcm2712-rpi-cm5-cm4io.dtb doesnt actually swap the I2C mapping properly, or am I doing something wrong? I have attached a copy of my config.txt if it helps.
It's your custom board -> look at the schematics, let us now what you've did and we will be able to tell you what you need to add to your config.txt
Statistics: Posted by aBUGSworstnightmare — Fri Mar 07, 2025 5:25 am