piCore TouchScreen Not Working Properly

[lwhritner]

Hi there, I am a student interning for a small company that uses piCore for its embedded systems. I've been running into a problem with the touchscreen that neither I nor my coworker/supervisor can figure out.

The issue is that while the screen detects touch, it processes it as a touch that occurs on the bottom right of the screen and nowhere else. Specifically, we are using a screen that is 1024x600, and the touch is processed at the point 1023x599. See below the log when using libinput debug-events:

Code: [Select]

-event0   DEVICE_ADDED                 QDtech MPI7003 Touchscreen        seat0 default group1  cap:t ntouches 1 calib
-event1   DEVICE_ADDED                   RPI Wired Keyboard 4            seat0 default group2  cap:k
-event2   DEVICE_ADDED                   RPI Wired Keyboard 4            seat0 default group2  cap:k
-event3   DEVICE_ADDED                 vc4-hdmi-0                        seat0 default group3  cap:k
-event5   DEVICE_ADDED                 vc4-hdmi-1                        seat0 default group4  cap:k
-event0   TOUCH_DOWN                   +0.000s -1 (0) 99.90/99.83 (1024.00/600.00mm)
 event0   TOUCH_FRAME                  +0.000s
 event0   TOUCH_UP                     +0.097s -1 (0)
 event0   TOUCH_FRAME                  +0.097s
 event0   TOUCH_DOWN                   +2.173s -1 (0) 99.90/99.83 (1024.00/600.00mm)
 event0   TOUCH_FRAME                  +2.173s
 event0   TOUCH_UP                     +2.323s -1 (0)
event0   TOUCH_FRAME                  +2.323s
We are using a QDtech MPI7003 Touchscreen and a Raspberry Pi CM4. This occurs on both PiCore 13 and 16.

We have flwm_topside.tcz and all of its dependencies installed, as well as libXrandr.tcz and Xorg-3d.tcz and their respective dependencies. Through our research, I came across using xinput a lot, though I cannot seem to find a way to install it (if it'll even be helpful in the first place).

Our guess is that there's something up with how the transformations are being processed. It could also be a kernel issue, but I wanna exhaust any and all further options before debugging the kernel. I am also going to try using other hardware such as a mouse, a CM5, and a different touchscreen once I get them from my supervisor. I am also very new to Linux, so this could even be a simple fix I am overlooking.

Any further insight would be greatly appreciated. I can provide more info to this forum if need be to help troubleshoot.

    [Edit]: Added code tags.  Rich

[Rich]

Hi lwhritner
Welcome to the forum.

Please use  Code Tags  when posting commands and responses seen in a terminal. To use  Code Tags  click on the  #  icon
above the reply box and paste your text between the  Code Tags  as shown in this example:

[code][   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]

It will appear like this in your post:

Code: [Select]

[   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517
Code Tags  serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly. Code tags also automatically add horizontal and or vertical scrollbars
to accommodate long lines and listings.

[Paul_123]

This touchscreen is notorious for having poor USB configuration data.  I have seen some that work with X OOTB, and some that don't.

This screen is a multitouch screen, and requries a different driver.  Try loading the kernel module  "hid_multitouch"

Do this in /opt/bootlocal.sh before you try to do anything with Xorg.