I’ve been putting together NixOS support for the A06 module, built against a
mainline kernel rather than the vendor tree: Linux 6.18, U-Boot 2026.07 and
upstream Trusted Firmware-A, with no vendor blobs in the boot chain.
All the testing was done on a DevTerm A06, because that’s the machine I
have. Since the uConsole uses the same A06 module, nearly all of it should
carry over — the SoC, PMIC, WiFi, audio codec and power management are
identical, and the kernel binary is the same for both. The panel is the real
difference, so the tree carries a uconsole variant throughout: the CWU50
panel driver, its own device tree and compatible, and its own U-Boot defconfig.
It all builds. It has simply never been run on a uConsole, so I have no idea
whether it comes up.
The thing I’d most expect to be wrong is panel rotation. It’s inherited
from the DevTerm, and ClockworkPi’s own uConsole patch doesn’t change it
either, so there was no reference to copy from. If the display comes up
sideways or upside down, that’s the first thing to look at.
If you have a uConsole A06 and a spare SD card, I’d be glad of a report either
way — “it booted” is as useful as “it didn’t”:
nix build git+https://codeberg.org/cckuoescxethyomogoet/clockworkpi-a06.git#sd-image-uconsole-a06-installer
sudo dd if=result/sd-image/*.img of=/dev/sdX bs=4M status=progress conv=fsync
That’s the installer image, so it boots to a normal NixOS installer
environment — nixos login, empty password, sshd running. You’ll need Nix
with flakes on an x86_64 or aarch64 Linux machine; it cross-compiles, so you
don’t build on the device itself.
Useful things to note, roughly in order:
- does it reach a login prompt at all, and is anything on screen
- is the display the right way up, and the right resolution
- keyboard and trackball
- WiFi, etc.
If it doesn’t boot, the serial console should be reachable at 1500000 baud
The full write-up, including what doesn’t work on the DevTerm and why, is over
in the DevTerm category at