piCore 16.0 and Raspi Touchscreen.

[MrPorcine]

I'm trying to get the Raspberry Pi 7" touch screen to work (not the newer Touch Display 2). It displays text and graphics fine. So far no touch input.

I have a working piCore13 where the display does touch correctly. When I look at the Xorg.0.log, with the piCore 13, Xorg loads a module called "raspberrypi-ts". Here's the line in the log:

Code: [Select]

Adding input device raspberrypi-ts (/dev/input/mouse0)
There is no such line in the log for the piCore 16. When I look at the list of optional tcz in each version (13,16) the list is exactly the same.

If anyone knows how to make this work it would be really helpful.

[Paul_123]

I split this topic off.

Comparing piCore 13 to 16 is like night and day in regards to video drivers.

You need to be using the vc4 driver base in piCore16.  What do you have in your config.txt, and what extensions do you have load3d?

[MrPorcine]

cmdline.txt has:

dwc_otg.fiq_fsm_mask=0xF dwc_otg.lpm_enable=0 console=tty1 root=/dev/ram0 rootwait quiet nortc loglevel=3 noembed

config.txt is:

Code: [Select]

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# RPi PI0-1-2 are not supported on this image.

[PI02]
initramfs rootfs-piCore64-16.0.gz,modules-6.12.25-piCore-v8.gz followkernel
kernel kernel61225v8.img

[PI3]
initramfs rootfs-piCore64-16.0.gz,modules-6.12.25-piCore-v8.gz followkernel
kernel kernel61225v8.img

[PI4]
initramfs rootfs-piCore64-16.0.gz,modules-6.12.25-piCore-v8.gz followkernel
kernel kernel61225v8.img

[PI5]
initramfs rootfs-piCore64-16.0.gz,modules-6.12.25-piCore-v8-16k.gz followkernel
kernel kernel61225v8-16k.img

[CM4]
otg_mode=1

[cm5]
dtoverlay=dwc2,dr_mode=host

[ALL]
cmdline cmdline.txt

# Run in 64-bit mode
arm_64bit=1

# Run as fast as firmware / board allows
arm_boost=1

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
# Does not work with the vc4 driver.

#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on
dtparam=i2s=on
dtparam=spi=on

# Additional overlays and parameters are documented /mnt/mmcblk0p1/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[PI5]
# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1

[all]
dtoverlay=disable-bt
dtoverlay=miniuart-bt
dtoverlay=sdio,poll_once
display_auto_detect=1
#official 7" touchscreen driver
dtoverlay=rpi-ft5406
dtoverlay=vc4-kms-dsi-7inch

# Enable DRM VC4 V3D driver
#dtoverlay=vc4-kms-v3d
max_framebuffers=2
disable_fw_kms_setup=1
Onboot.lst has:

Code: [Select]

Xorg.tcz
openssh.tcz

I'm using a pi 3B+.

[Paul_123]

You need to uncomment this line in config.txt

Code: [Select]

#dtoverlay=vc4-kms-v3d
You also need more extensions.

Code: [Select]

touchscreen-KERNEL.tcz   (This will load graphics-KERNEL.tcz as well)
flwm.tcz   (You need some sort of window manager)
aterm.tcz 
Xorg.tcz   (I would use Xorg-3d.tcz)


[MrPorcine]

Maybe a missing module? When I look at Bookworm for the Raspberry Pi (same hardware), Xorg appears to be using a module "edt_ft5x06". I haven't located it in piCore16.

[Paul_123]

Its in the touchscreen-KERNEL extension,  Please do what I told you.

For the record when you use KERNEL in the name the extension loader properly resolves your running kernel to get the correct extension.

[MrPorcine]

Code: [Select]

tce-fetch.sh touchscreen-KERNEL gets a Not Found error. Same for

Code: [Select]

tce-fetch.sh touchscreen-KERNEL.gzOr maybe you meant for me to insert the kernel version.

Code: [Select]

tce-fetch.sh touchscreen-6.12.25-piCore-v8.gz gets the same Not Found error.

tce Search "touchscreen" finds 4 citations, 2 that match the 6.12.25 part of my kernel. Neither will load  (error: checksums did not match), so apparently they don't match.

uname yields:

Code: [Select]

tc@box:~$ uname -rsv
Linux 6.12.25-piCore-v8 #5 SMP PREEMPT Sat Apr 26 13:42:06 EDT 2025
My application makes direct reads and writes to the Xorg server. No window manager, no toolkit. The app writes to the screen without a problem, it's only that Xorg doesn't see the touchscreen. It finds a mouse OK.

I enabled the vc4-kms-v3d line in config.txt.

[MrPorcine]

Hmmm, should be tcz, not gz. Still won't install with 65 checksums not matching.

[Rich]

Hi MrPorcine
Why are you using  tce-fetch?
It doesn't fetch .md5.txt files, .dep files, or resolve dependencies.

If you just want an extension downloaded:

Code: [Select]

tce-load -w touchscreen-KERNEL
If you just want an extension downloaded and installed:

Code: [Select]

tce-load -wil touchscreen-KERNEL
If you want an extension downloaded, installed, and added to onboot.lst:

Code: [Select]

tce-load -wi touchscreen-KERNEL

... Still won't install with 65 checksums not matching.

See if running this fixes your checksum issue:

Code: [Select]

update-everything

[MrPorcine]

Hi Rich,
Update-everything allows touchscreen-KERNEL to load. Unfortunately, when I put it in onboot.lst Xorg fails to initialize. Here's the last few lines of Xorg.0.log after a failed attempt to launch:

Code: [Select]

[    11.237] (II) Module fbdevhw: vendor="X.Org Foundation"
[    11.237] compiled for 1.21.1.13, module version = 0.0.2
[    11.237] ABI class: X.Org Video Driver, version 25.2
[    11.237] (EE) open /dev/fb0: No such file or directory
[    11.237] (EE) No devices detected.
[    11.237] (EE)
Fatal server error:
[    11.237] (EE) no screens found(EE)
[    11.237] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
 for help.
[    11.237] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    11.237] (EE)
[    11.237] (EE) Server terminated with error (1). Closing log file.
When I remove touchscreen-KERNEL from onboot.lst, Xorg finds the framebuffer and continues successfully. (Although without finding the touchscreen driver.)

I'm not sure this is important, I substuted a custom version of Xorg-fonts as my app needs a couple of fonts not in the original.

[MrPorcine]

There must be some timing issues here. I've seen it come up perfectly once, on a reboot. Touch worked. I've never seen it come up from a power-up start. Maybe I can put a test for /dev/fb0 before I start up Xorg.

[Rich]

Hi MrPorcine

Xorg.0.log after a failed attempt to launch:

Code: [Select]

[    11.237] (II) Module fbdevhw: vendor="X.Org Foundation"
[    11.237] compiled for 1.21.1.13, module version = 0.0.2
[    11.237] ABI class: X.Org Video Driver, version 25.2
[    11.237] (EE) open /dev/fb0: No such file or directory
[    11.237] (EE) No devices detected.
 ----- Snip ----- ...

I've run into a similar timing situation with one of my machines.
I solved it by placing this at the beginning of ~/.xsession:

Code: [Select]

Timeout=0
while [ $Timeout -lt 40 ]
do
        [ -e /dev/dri/card0 ] && break
        Timeout=$(($Timeout + 1))
        sleep 0.25
doneIt checks once every 0.25 seconds for the device to show up.
Once the device shows up, the rest of ~/.xsession will run.
Just change  /dev/dri/card0  to  /dev/fb0.

[MrPorcine]

I don't have an answer yet, but this is what I've determined
-With touchscreen-KERNEL in onboot.lst, something is removing /dev/fb0 and reinserting it. There is ~8 seconds before /dev/fb0 reappears. This must be some sort of hardware timeout, no process is going to take that long. I know that /dev/fb0 is present in the early boot stages because I use fbv to write images during early boot. If I boot from power-on, the bootstrap works eventually. If I reboot my app usually doesn't start because it can't find display :0.0.
The edt-ft5X06 module is not happy. Here's a snippit from dmesg:

Code: [Select]

[    6.504608] edt_ft5x06 10-0038: supply iovcc not found, using dummy regulator
[    6.551449] input: raspberrypi-ts as /devices/platform/soc/soc:firmware/soc:firmware:touchscreen/input/input7
[    6.947147] input: 10-0038 generic ft5x06 (79) as /devices/platform/soc/3f205000.i2c/i2c-11/i2c-10/10-0038/input/in
put8
[    6.955178] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[    6.991278] bcm2835-audio bcm2835-audio: card created with 8 channels
[    7.116179] /soc/dsi@7e700000: Fixed dependency cycle(s) with /soc/dsi@7e700000/bridge@0
[    7.116385] /soc/dsi@7e700000/bridge@0: Fixed dependency cycle(s) with /soc/dsi@7e700000
[    7.161534] Console: switching to colour dummy device 80x25
[    7.180313] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
[    7.181871] Registered IR keymap rc-cec
[    7.182141] rc rc0: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0
[    7.182498] input: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0/input9
[    8.317478] edt_ft5x06 10-0038: Unable to fetch data, error: -110
[    8.545320] hwmon hwmon1: Undervoltage detected!
[    9.377471] edt_ft5x06 10-0038: Unable to fetch data, error: -110
[   10.397500] edt_ft5x06 10-0038: Unable to fetch data, error: -110
[   11.014762] lan78xx 1-1.1.1:1.0 eth0: Link is Down
[   11.043736] EXT4-fs (mmcblk1p2): mounting ext2 file system using the ext4 subsystem
[   11.044976] EXT4-fs (mmcblk1p2): warning: mounting unchecked fs, running e2fsck is recommended
[   11.048366] EXT4-fs (mmcblk1p2): mounted filesystem 82bc8d10-3c7c-433c-93ea-da1700e29567 r/w without journal. Quota
 mode: none.
[   11.052678] EXT4-fs (mmcblk1p1): mounting ext2 file system using the ext4 subsystem
[   11.060145] EXT4-fs (mmcblk1p1): warning: mounting unchecked fs, running e2fsck is recommended
[   11.062128] EXT4-fs (mmcblk1p1): mounted filesystem a0191bca-2ad0-4489-940d-d5fcaad56f0e r/w without journal. Quota
 mode: none.
[   11.421382] edt_ft5x06 10-0038: Unable to fetch data, error: -110
[   12.445379] edt_ft5x06 10-0038: Unable to fetch data, error: -110
[   12.573423] hwmon hwmon1: Voltage normalised
[   13.469380] edt_ft5x06 10-0038: Unable to fetch data, error: -110
[   14.085177] lan78xx 1-1.1.1:1.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[   14.493388] edt_ft5x06 10-0038: Unable to fetch data, error: -110
[   15.549378] edt_ft5x06 10-0038: Unable to fetch data, error: -110
[   16.573382] edt_ft5x06 10-0038: Unable to fetch data, error: -110
There are many more "Unable to fetch data" lines in dmesg.

-Without the touchscreen-KERNEL in onboot.lst, bootstrap progresses normally, but no touch driver.

[MrPorcine]

OK, it seems to be workng . Here's config.txt:

Code: [Select]

[PI3]
initramfs rootfs-piCore64-16.0.gz,modules-6.12.25-piCore-v8.gz followkernel
kernel kernel61225v8.img

[PI4]
initramfs rootfs-piCore64-16.0.gz,modules-6.12.25-piCore-v8.gz followkernel
kernel kernel61225v8.img

[ALL]
cmdline cmdline.txt

# Run in 64-bit mode
arm_64bit=1

# Run as fast as firmware / board allows
arm_boost=1

# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on
dtparam=i2s=on
dtparam=spi=on

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[all]
dtoverlay=disable-bt
dtoverlay=miniuart-bt
dtoverlay=sdio,poll_once
display_auto_detect=1
#official 7" touchscreen driver which includes rpi-ft5406
dtoverlay=vc4-kms-dsi-7inch

# Enable DRM VC4 V3D driver
#needed for the 7" touchscreen, nohdmi as we're not using hdmi
dtoverlay=vc4-kms-v3d,nohdmi
max_framebuffers=2
disable_fw_kms_setup=1
And here's onboot.lst:

Code: [Select]

touchscreen-6.12.25-piCore-v8.tcz
Xorg.tcz
openssh.tcz
What made it work? Removing the extra rpi-ft5406 from config.txt as it's included in vc4-kms-dsi-7inch, and adding nohdmi to vc4-kms-v3d. Onboot.lst hasn't changed. When I look at dmesg there are no more error messages from edt_ft5x06 10-0038. I wonder if by specifing rpi-ft5406 separately in config.txt I got two instances that were quarrelling.

[Rich]

Hi MrPorcine
These lines caught my attention:

...

Code: [Select]

[    6.504608] edt_ft5x06 10-0038: supply iovcc not found, using dummy regulator
 ----- Snip -----
[    8.545320] hwmon hwmon1: Undervoltage detected!
 ----- Snip -----
[   11.014762] lan78xx 1-1.1.1:1.0 eth0: Link is Down
 ----- Snip -----
[   12.573423] hwmon hwmon1: Voltage normalised
 ----- Snip -----
[   14.085177] lan78xx 1-1.1.1:1.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx
 ----- Snip -----


I would check to make sure your power supply is strong enough to
supply your hardware.

Double check your wiring/cabling to make sure all connections are solid.
No clip leads allowed.

Just because it says "Voltage normalised" and the network claims it
recovered, doesn't mean the rest of the hardware is properly configured.