Recent Posts

1

Raspberry Pi / Re: piCore 16.0 and Raspi Touchscreen.

« Last post by MrPorcine on Today at 08:50:06 PM »

Rich,
Yes, thanks for the heads up. This is an embedded system where the Pi power is supplied via the GPIO pins. It's been working well for several years. Maybe only marginally working   . I don't think we've ever actually monitored the voltage drop across the GPIO pins.

So we've got some work to do. The test setup I've been using to solve this problem has a 40-wide flat cable that is probably twice as long as the one in the actual product. Hopefully this is the issue. TBD.

2

Raspberry Pi / Re: piCore 16.0 and Raspi Touchscreen.

« Last post by Rich on Today at 08:39:23 PM »

Hi MrPorcine

... I wonder if by specifing rpi-ft5406 separately in config.txt I got two instances that were quarrelling.

Whatever it was, it sounds like it caused the hardware to work very
hard and seriously increase its power consumption.

3

Raspberry Pi / Re: piCore 16.0 and Raspi Touchscreen.

« Last post by Rich on Today at 08:10:22 PM »

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.

4

Raspberry Pi / Re: piCore 16.0 and Raspi Touchscreen.

« Last post by MrPorcine on Today at 08:09:47 PM »

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.

5

Raspberry Pi / Re: piCore 16.0 and Raspi Touchscreen.

« Last post by MrPorcine on Today at 07:14:46 PM »

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.

6

General TC Talk / Re: Serial Port

« Last post by Rich on Today at 05:13:55 PM »

Hi MTCAT
Try this:

Code: [Select]

date > test.log; sudo microcom -s 9600 /dev/ttyACM0 >> test.log
This should work too:

Code: [Select]

sudo microcom -s 9600 /dev/ttyACM0 > $(date +"%y%m%d%H%M%S").logThat should create a log file whose name is the date code that looks like:

Code: [Select]

YYMMDDHHMMSS.logThis creates a unique file every time it's run. In a directory listing they
would all be grouped together and sorted from oldest to newest.

7

Raspberry Pi / Re: piCore 16.0 and Raspi Touchscreen.

« Last post by Rich on Today at 04:38:39 PM »

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.

8

Raspberry Pi / Re: piCore 16.0 and Raspi Touchscreen.

« Last post by MrPorcine on Today at 04:01:32 PM »

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.

9

Off-Topic - Tiny Core Lounge / Re: Conspiracy Theory: The Simpsons' "Power Outage"

« Last post by xor on Today at 03:41:38 PM »

https://web.archive.org/web/20260210203433/https://forum.tinycorelinux.net/index.php/topic,28011.0.html

10

TCB Talk / Re: xfbdev (xlibre)?

« Last post by nixmonkey on Today at 03:38:07 PM »

Thanks for looking at that! stefan11111 seems to be contributing quite a bit, over there. Looking at stefan11111's github repos, I see some interesting things I may need to consider.

I did notice stefan11111 has a fork of Tinyx, and Tinyx pull requests, at github.

The GLX (EGL), for xfbdev, is interesting

Looking through the Gentoo work, by that contributor, sheds a little light. Could be just trying to merge those interests into xlibre, as it was likely not gonna happen at X.org (no criticism intended, there is legitimate reasoning there).

I don't care for all of the xorg/xlibre/wayland "noise", but it would be nice it some good things "quietly" came out of it.