Touch screen problem on PiCore (bug/ just some tslib setting?)

[paul-]

Can you unplug the USB connector for the touch? If so.
Boot system, and validate the screen resolution is 800x480 with fbset

Then plug in the USB to let the touch initialize. Then see if there is any difference with ts_calibrate.

Do you have a direct link to the product?

[streampunk]

https://wimaxit.com/products/wimaxit-raspberry-pi-7-touch-screen-display-monitor-1024x600-usb-powered-hdmi-screen-monitor-ips-178-with-rear-speakers-stand-for-raspberry-4-3-2-laptop-pc

I‘ll try unplugging the USB to USB adaptor tomorrow.
Wouldn‘t it be possible to simply grab the integration of this screen from Buster, where it works out-of-the-box, without any need to use ts_calibrate etc?

[streampunk]

And this is what the vendor suggests to modify in config.txt:

hdmi_force_edid_audio=1
max_usb_current=1
hdmi_force_hotplug=1
config_hdmi_boost=7
hdmi_group=2
hdmi_mode=87
hdmi_drive=2
display_rotate=0
hdmi_cvt 1024 600 60 6 0 0 0

And this for Bullseye:

Change dtoverlay=vc4-kms-v3d to dtoverlay=vc4-fkms-v3d

[paul-]

RaspiOS is using Xorg. That is a completely different system.

[kjansik]

I 'll do it tomorrow. USB touch conector on screen provides power supply for screen as well. Screen has separate input for power supply only. Product link:http://www.lcdwiki.com/7inch_HDMI_Display-H. Product is available from dozen different sellers. I got 2 pieces from different sellers, different brand. Both are identical in detail, behavior is exactly the same.

[kjansik]

Hi Paul

i did following:

dtoverlay=vc4-kms-v3d-pi4
​

touch is disconnected :

tc@pCP:~$ fbset

mode "800x480-0"
        # D: 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz
        geometry 800 480 1024 600 16
        timings 0 0 0 0 0 0 0
        accel false
        rgba 5/11,6/5,5/0,0/0
endmode
​

touch is conncted:

tc@pCP:~$ fbset

mode "800x480-0"
        # D: 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz
        geometry 800 480 1024 600 16
        timings 0 0 0 0 0 0 0
        accel false
        rgba 5/11,6/5,5/0,0/0
endmode
​

I did it on the fly and after reboot, no difference.
Joggler screen is just on part of the screen.

#dtoverlay=vc4-kms-v3d-pi4 commented out

tc@pCP:~$ fbset

mode "800x480-0"
        # D: 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz
        geometry 800 480 800 480 32
        timings 0 0 0 0 0 0 0
        accel false
        rgba 8/16,8/8,8/0,8/24
endmode
​

with touch, without touch. Changed on the fly, after reboot.
Joggler is full screen

Calibration (fbset as above):

tc@pCP:~$ sudo TSLIB_FBDEVICE=/dev/fb0 TSLIB_TSDEVICE=/dev/input/event0 /usr/loc
al/bin/ts_calibrate
xres = 800, yres = 480
Took 1 samples...
Top left : X = 1024 Y =  600
Took 1 samples...
Top right : X = 1024 Y =  600
Took 1 samples...
Bot right : X = 1024 Y =  600
Took 1 samples...
Bot left : X = 1024 Y =  600
Took 1 samples...
Center : X = 1024 Y =  600
ts_calibrate: determinant is too small -- 0.000000
Calibration failed.
​

[darkblue68]

Hi Paul

I own a Wimaxit 7inch touchscreen display too.
I've exactly the same problem and I tried all what is possible but the touchscreen isn't working.
I tried Max2play, the screen and the touch features are working.
But I prefer PicorePlayer of course !

Thanks in advance if you find a solution

[streampunk]

https://wimaxit.com/products/wimaxit...-3-2-laptop-pc
I‘ll try unplugging the USB to USB adaptor tomorrow.

Sorry for not responding, my display is in the suitcase that got lost on my way back from holiday. Expecting to get it this weekend :-((

[kjansik]

Anyway, there is no difference in fbset values if touch USB is connected or disconnected. I noticed difference in fbset values in the case vc4-kms-v3d-pi4 is commented out - but not dependent on connected touch USB..

[paul-]

I went ahead and ordered one of these. I'll let you guys know what I find.

[streampunk]

Thanks a lot Paul, you‘re my heroe! I‘ve just made a donation to compensate at least part of your investment, and I encourage all to do the same.

[kjansik]

Glad to hear it. What brand, seller (if not confidentially)?

[paul-]

Its the Elecrow brand, as that was what I could get on Amazon. I confirm everything you have tried.. This might take a bit to figure out. But it really looks like bad firmware on the card. I'm reading the raw device events (not using TSLIB). This is a single touch and release, as you can see from the timestamps, its generating different X/Y positions from a single touch. This is a multitouch screen, but with linux, it is supposed to only work in single touch mode. hmmm.

Event: time 1682263797.983528, -------------- SYN_REPORT ------------
Event: time 1682263826.427998, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1682263826.427998, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1682263826.427998, type 3 (EV_ABS), code 0 (ABS_X), value 521
Event: time 1682263826.427998, type 3 (EV_ABS), code 1 (ABS_Y), value 380
Event: time 1682263826.427998, type 3 (EV_ABS), code 0 (ABS_X), value 973
Event: time 1682263826.427998, type 3 (EV_ABS), code 1 (ABS_Y), value 93
Event: time 1682263826.427998, type 3 (EV_ABS), code 0 (ABS_X), value 1024
Event: time 1682263826.427998, type 3 (EV_ABS), code 1 (ABS_Y), value 600
Event: time 1682263826.427998, -------------- SYN_REPORT ------------
Event: time 1682263826.895977, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1682263826.895977, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1682263826.895977, type 3 (EV_ABS), code 0 (ABS_X), value 0
Event: time 1682263826.895977, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 1682263826.895977, type 3 (EV_ABS), code 0 (ABS_X), value 1024
Event: time 1682263826.895977, type 3 (EV_ABS), code 1 (ABS_Y), value 600
​

I'll take load raspiOS and see what changes with the drivers.

[kjansik]

Really curious what would be your conclusions after raspiOS try. In my case touch is working flawlessly without any calibration. Same with Windows11. From my point of view problem is concerning TinyCore. I tried TinyCore even with XORG, same problem...

[darkblue68]

Hello PAul

Any news about your Wimaxit screen?