I use a Rpi3b+ (hardware 1.3).
I connect a waveshare touchscreen 7.0'' ref 12104.
I install a fresh raspbian lite image (for example last working: raspios_lite_armhf-2023-12-11 )
I change /boot/config.txt with waveshare config:
hdmi_group=2 hdmi_mode=87 hdmi_cvt 1024 600 60 6 0 0 0 dtoverlay=ads7846,cs=1,penirq=25,penirq_pull=2,speed=50000,keep_vref_on=0,swapxy=0,pmax=255,xohms=150,xmin=200,xmax=3900,ymin=200,ymax=3900
I install evtest tool
apt-update && apt upgrade -yapt install evtest libts-bin
I copy my /etc/ts.env and /etc/pointercal files to the target
After a reboot, with evtest tool, everything works perfectly. get all signals.
when starting evtest , logs are:
Input driver version is 1.0.1
Input device ID: bus 0x1c vendor 0x0 product 0x1ea6 version 0x0
Input device name: "ADS7846 Touchscreen"
Since release raspios_lite_armhf-2024-03-13, the touchscreen is detected yet with evtest but no signal is detected.
I have make lot of test and confirm that issue appear as soon as I replace kernel 6.1.x by 6.6.x version.
Do you know a workaround ?
6by9
commented
6 months ago
I use a Rpi3b+ (hardware 1.3). I connect a waveshare touchscreen 7.0'' ref 12104.
I install a fresh raspbian lite image (for example last working: raspios_lite_armhf-2023-12-11 ) I change /boot/config.txt with waveshare config:
hdmi_group=2 hdmi_mode=87 hdmi_cvt 1024 600 60 6 0 0 0 dtoverlay=ads7846,cs=1,penirq=25,penirq_pull=2,speed=50000,keep_vref_on=0,swapxy=0,pmax=255,xohms=150,xmin=200,xmax=3900,ymin=200,ymax=3900I install evtest tool
apt-update && apt upgrade -yapt install evtest libts-binI copy my /etc/ts.env and /etc/pointercal files to the targetAfter a reboot, with evtest tool, everything works perfectly. get all signals. when starting evtest , logs are: Input driver version is 1.0.1 Input device ID: bus 0x1c vendor 0x0 product 0x1ea6 version 0x0 Input device name: "ADS7846 Touchscreen"
Since release raspios_lite_armhf-2024-03-13, the touchscreen is detected yet with evtest but no signal is detected.
I have make lot of test and confirm that issue appear as soon as I replace kernel 6.1.x by 6.6.x version. Do you know a workaround ?