GPIO LED/power switch do not work with 5.26

arthur

I installed the newest 5.26 build in my RPi4 and configured it via SSH, editing file /userdata/system/batocera.conf to activate system.power.switch=PIN56ONOFF. But after rebooting, looks like the GPIO power switch and LED scripts do not work properly.
Is there something I should do to fix this?
Thanks in advance.
Arthur

[deleted]

arthur The python GPIO lib does not properly work for Pi4 only.
It should be fixed in upcoming version.

arthur

OK, thanks, @[deleted] . No Python yet, that makes sense.

What about enabling GPIO LED/shutdown/etc using device tree overlays in boot/config.txt? In Batocera, it looks like at the moment the status LED could be set up at GPIO 14, using enable _uart=1.

In Raspberry Pi OS, we can also enable the shutdown switch at GPIO 3 with dtoverlay=gpio-shutdown, but that does not work with Batocera. The automatic cooling fan control at GPIO 12, enabled with dtoverlay=gpio-fan (which I did not test for Batocera), would also be particularly useful for RPi4s - they get hot quickly.

I’m no coder, I have no idea why some distros allow using DT overlays, while others do not, or what are the pros and cons, but this LED/shutdown/fan control stuff becomes much simpler to set up compared to Python scripts - at least for a RPi4 without any fancy external LED/power/fan circuitry.

All the best
arthur

[deleted]

arthur Yes dto overlays should work but imho the python lib can not initialze internal pullup resistors.

adelin

hi, i try this version : https://batocera.org/upgrades/rpi4/beta/last/
the gpio work, can you test this version because i have a problem with the button

arthur

Hi
Sorry for the late reply.
I already tested the first 5.27 stable build, right after its release, some weeks ago, and the gpio overlays for shutdown button and status led were OK.
Haven’t tested other gpio overlays, namely for fan control, nor these latest 5.27.x builds.
Will post the results soon.
Thanks for the heads-up