Skip to the content
nullroute

Suggested

GitHub Get started
Browse the docs

Start here

Install

Run the whole device on your computer, build or download a card, flash it, and what the device does at first boot.

This device is pre-release and unaudited. Hardware bring-up is next, starting on a Pi 5. If you flash a card now, use a spare and expect to be part of that bring-up.

Pick a way in:

  1. Run it on your computer with make dev.
  2. Take the UNSIGNED card CI built: A card from CI.
  3. Build a card yourself with Docker.

For a card, check What you need, then flash it and boot it.

In this chapter

  1. 01Running it on your computerNeeds Node 24 and git.
  2. 02What you needThe parts list is in the README, under What you need to build one.
  3. 03A card from CI, for bring-upEvery push to main that touches provisioning/ builds the card with the same make image-system you would run. CI boots it under QEMU, requires a copy with one byte changed to be...
  4. 04Building a cardNeeds Docker. It builds for arm64: native on Apple silicon, much slower under emulation on Intel.
  5. 05Flashing itFind the card first: diskutil list on macOS, lsblk on Linux. Get this wrong and you will overwrite something else. Read the size and confirm it is the card.
  6. 06What the device does at bootYou type nothing and configure nothing.
  7. 07Verifying before you flash, and the tiersTier 0 is building the card yourself, checking its hash, and reading it back after writing. It costs nothing irreversible and is the only tier that works on any board.
  8. 08Where this stands todayHardware bring-up is the next milestone, starting on a Pi 5. The image boots under QEMU and the signing daemon starts on it. The firmware path from power-on to the kernel, and the...

Rendered from docs/INSTALL.md, the same bytes that ship with the code. SHA-256 2c8eeb5da574c931efdb3a904d2ca1c92cd033bd6d70e07ac5c33c811c14972f