See https://pip.raspberrypi.com/categories/651-pcn for the on the display.
It should be responding to address 0x45 as before, and be backwards compatible.
The fact that you are probing it as i2c-7, and have dw-dsi2h-pcie lines in your logging says it isn't a Pi you're running it with. That means there are a bundle of differences that could be present between your hardware and a Pi, and the display is designed to work with a Pi. The first query would be what speed you're running the I2C bus at, but beyond that we can only offer limited support.
Your i2cdetect is skipping many addresses, including 0x45 which won't help. "i2cdetect -r" will force it to use SMBus "receive byte" rather than it's slightly random choice of probing mechanism (https://git.kernel.org/pub/scm/utils/i2 ... tect.c#n68)
Please also note that Raspberry Pi OS does NOT use panel-raspberrypi-touchscreen, as it combines too many things into a monolithic block, and badly. The touch driver has no place to hook on to, and it gets powered down with no warning whenever the kernel disables the panel. Raspberry Pi OS uses rpi-panel-attiny-regulator, tc358762, panel-simple, and edt-ft5x06.
It should be responding to address 0x45 as before, and be backwards compatible.
The fact that you are probing it as i2c-7, and have dw-dsi2h-pcie lines in your logging says it isn't a Pi you're running it with. That means there are a bundle of differences that could be present between your hardware and a Pi, and the display is designed to work with a Pi. The first query would be what speed you're running the I2C bus at, but beyond that we can only offer limited support.
Your i2cdetect is skipping many addresses, including 0x45 which won't help. "i2cdetect -r" will force it to use SMBus "receive byte" rather than it's slightly random choice of probing mechanism (https://git.kernel.org/pub/scm/utils/i2 ... tect.c#n68)
Please also note that Raspberry Pi OS does NOT use panel-raspberrypi-touchscreen, as it combines too many things into a monolithic block, and badly. The touch driver has no place to hook on to, and it gets powered down with no warning whenever the kernel disables the panel. Raspberry Pi OS uses rpi-panel-attiny-regulator, tc358762, panel-simple, and edt-ft5x06.
Statistics: Posted by 6by9 — Mon Apr 15, 2024 5:57 pm