EmberRTOS on the Raspberry Pi
EmberRTOS 0.1.5 added the Raspberry Pi, and 0.1.9 is the release to download. There are two flashable disk images for the Raspberry Pi 4 and the Raspberry Pi 5, built from the same image description as the x86_64 installers, so a Pi is the same node as an industrial PC: the same setup app, the same enrollment, the same cluster steps, the same signed update repository.
| Image | Kernel | What it is for |
|---|---|---|
| Headless RT | Real-time | A Pi with a deadline. The real-time kernel is the default boot, with the tuning layer and the Real-time screen in the setup app. The general-purpose kernel stays beside it in the boot menu as the fallback. |
| Headless | General-purpose | A Pi that is a gateway, a collector, or a container host. No real-time kernel, no tuning, and no Real-time screen. |
Both show the setup app on the HDMI screen. The Desktop edition is not part of this release: the Pi has the two Headless editions only.
A Raspberry Pi 5 and a Compute Module 5 have each booted the 0.1.5 images. The 0.1.9 images have not been booted on a Pi yet. Booted is all this page claims for the 0.1.5 images. The Raspberry Pi 4 had no board available for this release, so its firmware, device tree and kernel drivers are in the image and in the check that reads them off the finished disk, and booting it is unchecked. The section What is proven, and what is not lists the rest.
What the image is
The Pi image is a raw disk image, not an installer. You write it to the boot card, put the card in the Pi, and power on. On its first boot the box grows its root filesystem to the whole card, then starts the setup app.
Everything else is the node the x86_64 editions carry: the cluster service, the EmberNet endpoint, the Plasma firewall as a container (off by default), the maintenance login, the keyed install, and the signed update repository. Updates go into a new snapshot and take effect at the next restart a person plans. From 0.1.6 the box never restarts itself for one; 0.1.5 could, as the update section explains. Its updates are signed with the same key as the x86_64 ones.
The Pi image arms no hardware watchdog. A watchdog armed by the operating system put real Pi 5 boxes into a reboot loop, so nothing here arms one.
Which boot media work
| Boot media | Raspberry Pi 4 | Raspberry Pi 5 |
|---|---|---|
| SD card | Yes | Yes |
| USB | Yes | No |
| NVMe as the boot disk | No | No |
The boot loader this image uses has no NVMe support, and on the Pi 5 it has no USB either, because both sit behind the Pi 5's PCIe. A Pi 5 boots EmberRTOS from the SD card. An NVMe drive works as a data disk once the system is up. Booting a Pi 5 from NVMe or USB needs the boot loader to gain Pi 5 PCIe support, which is not in this release.
Update the Pi's EEPROM firmware before the first boot, with rpi-eeprom-update or the Raspberry Pi
Imager's EEPROM tool. The Pi 5 needs a current one.
Write the image to a card
Each release has two Pi images, each with a .sha256 file. Download the one you want, check it against its
.sha256 file, and write it to a card of at least 16 GB:
0.1.9, the current release:
| Image | Download | Checksum |
|---|---|---|
| Headless RT | EmberRTOS-Headless-RT-0.1.9-aarch64.raw.xz | .sha256 |
| Headless | EmberRTOS-Headless-0.1.9-aarch64.raw.xz | .sha256 |
The downloads index lists the versions on offer, and latest.json beside it names the newest
version with each file's size and checksum. Download both files into one folder before you check:
sha256sum -c EmberRTOS-Headless-RT-0.1.9-aarch64.raw.xz.sha256
xzcat EmberRTOS-Headless-RT-0.1.9-aarch64.raw.xz | sudo dd of=/dev/<card> bs=4M conv=fsync status=progress
Check the device name first. dd overwrites whatever it is pointed at.
Put the card in the Pi and power on. The first boot takes longer than the ones after it, because it grows the root filesystem. Then follow First boot and the setup app.
What is not in 0.1.9
- Desktop on the Raspberry Pi.
- Arm64 MicroVM disks. The containerdisk tags stay amd64 and follow as their own release.
- Booting a Pi 5 from NVMe or USB.
- The Raspberry Pi 3, Zero 2 and earlier boards, the Pi 400, and the Compute Modules other than the Compute Module 5. The image is built and checked for the Pi 4 and Pi 5 boards, and a Compute Module 5 has booted it.
What is proven, and what is not
What ran: a Raspberry Pi 5 and a Compute Module 5 booted the 0.1.5 images. Both 0.1.9 Pi images were built by the release run on native arm64 runners, after the same steps had been rehearsed on an emulated arm64 build host for 0.1.7, and each build ended with the checks that read the finished disk: the partition table, the firmware, the boot loader, the Pi 4 and Pi 5 hardware descriptions, the boot menu, and the edition. The real-time kernel for arm64 boots in a virtual machine.
What did not:
- Booting the 0.1.9 images on any Raspberry Pi, and booting on a Raspberry Pi 4 at all. No Pi 4 has booted these images. Beyond "booted", nothing about what ran on the Pi 5 and the Compute Module 5 with 0.1.5 is claimed here.
- Rehearsal timings. The rehearsal ran on an emulated arm64 host sized like the release runner (14 GiB disk, 8 GB of memory, no swap), so its timings say nothing about the runner's.
- Real-time latency on a Pi, and the real-time kernel on a Pi 4. The kernel is built with the distribution's own Pi options and boots in a virtual machine. A latency measurement on a Pi with 0.1.9 has not been taken. The latency figures on the EmberRTOS Headless RT page are from earlier builds, on a Pi 5.
- The setup app on a Pi display, Wi-Fi, and Bluetooth.
- A Pi taking an update from the aarch64 repository, end to end. The repository exists and is signed, and no Pi has taken an update from it.
Next steps
- First boot and the setup app: bring the node up from its own screen
- EmberRTOS Headless RT: the real-time kernel, and how to check it
- EmberRTOS Headless: updates, rollback, and what is included