-
-
Notifications
You must be signed in to change notification settings - Fork 19
Raspberry Pi 5
I finally got my hands on the Raspberry Pi 5. I'll try and document my findings here.
For details, see the Raspberry Pi Documentation for the Raspberry Pi 5
The Pi 5 has a single multicoloured LED that combines the power and activity LEDs from previous models. The LED cannot be controlled (turned on or off).
I have yet to find a way to expose it, if at all possible.
Like the Pi 4B, the Pi 5 has no support for cutting power to the USB ports.
The Pi 5 needs active cooling.
Both the official Raspberry Pi Case for Raspberry Pi 5
and the Raspberry Pi Active Cooler connect to the fan header.
This header controls the fan speed through PWM, and reads the fan speed in rpm.
Both can be monitored through /sys/devices/platform/cooling_fan/hwmon/hwmon2/pwm1 and /sys/devices/platform/cooling_fan/hwmon/hwmon2/fan1_input respectively.
The internal UART on the Pi 5 has a dedicated header, and is not exposed through GPIO 14 and GPIO 15. As far as I can tell, it's not possible to re-route the UART to the GPIO pins in software. That means the HATs using the internal UART over GPIO won't work on the Pi 5. This includes the RaspBee and RaspBee II.
The way the Pi 5 controls the GPIO pins is completely different form previous Pi models.
The GPIO is connected to the RP1 south bridge, instead of directly to the SoC.
Consequently, pigpio no longer works.
lg looks promising as alternative, but I still have to look into that.
The rgpiod daemon is distributed with Pi OS Bookworm, but not with previous versions of Pi OS.
Also the rgs command-line utility is unavailable for installation through apt and needs to be compiled from sources.
I haven't been able to run 64-but Raspberry Pi OS bookworm from a RasPiKey, see https://www.uugear.com/forums/technial-support-discussion/raspikey-on-raspberry-pi-5/#post-328.
The Pi 5 requires Raspberry Pi OS Bookworm. It won't run earlier Pi OS versions, including Bullseye.
There's no supported way to upgrade Bullseye to Bookwork; you'll need to create a new image and re-install/restore your applications to the new image.
Bookworm comes with a new graphical system, Wayland.
Currenlty, RealVNC doesn't support Wayland.
To continue to use RealVNC, disable Wayland in favour of classic X11, in raspi-config (option A6 under Avanced Settings).
Alternatively, you could use wayvnc instead of RealVNC, but that requires a new VNC client. The suggested TigerVNC sucks imho, so I'll stick to X11 for now.
In bookworm, syslog has been replaced by journalctl.