Own firmware that speaks Meshtastic, not a Meshtastic fork
Superseded in part by ADR 0011 (2026-11-10): the mesh speaks MeshCore, not Meshtastic. "Our own firmware, not a fork" still holds.
The architecture decision records: why the firmware is built the way it is, and what each choice costs. Generated from docs/adr/ in the repository.
One page for each architecture decision: the choice, what it was chosen over, and its consequences. They are written when the decision is made and kept; a later decision that changes an earlier one says so. Generated from docs/adr/ in the repository: edit those files, not these pages.
Superseded in part by ADR 0011 (2026-11-10): the mesh speaks MeshCore, not Meshtastic. "Our own firmware, not a fork" still holds.
The UI is drawn with M5GFX into an off-screen buffer, using a small widget kit we own: list, text view, line editor, dialog, Status Bar and Toast. We chose this over LVGL.
Firmware Updates are accepted only when their Update File carries a valid ECDSA P-256 signature over the image's SHA-256. The firmware itself checks it, against a public key compiled into it, before switching the boot partition.…
Superseded in part by ADR 0010 (2026-10-06): there is no Debug Build any more. The console is in every firmware, off until switched on, and its token belongs to the device, not to the build. What this record says about how the…
Rollback protects against new firmware that fails Probation. It does nothing for firmware that was confirmed and crashes later: a corrupt setting, a server that sends something unexpected, a bug that takes an hour to show.…
Arduino-ESP32 ships its ESP-IDF libraries prebuilt, with one sdkconfig for every ESP32-S3 board. Its TLS settings give every connection a 16 KB receive buffer and a 16 KB send buffer for its whole life. On a device with no PSRAM…
Arduino-ESP32's SD library talks to the card over SPI through sd_diskio.cpp. That driver gives up on a write without saying why, and about once in 1,500 multi-block writes it gave up on one that had worked (issue #21). A 1.7 MB…
A tag v is built, signed and published by Gitea Actions with nobody at a keyboard. The signing key of ADR 0003 is therefore held twice: in ~/.config/roro9stack/ota-key.pem on the development machine, as before, and as the…
The firmware talks to the project's Gitea over HTTPS (issue #6, and #4 after it). A TLS client has to decide whose certificates it believes. Three ways were possible:
There is one firmware. The Debug Console of ADR 0004 is compiled into it, and so are the commands that used to exist only in Debug Builds. It listens only while Settings → Debug Console is on, which is not the default, and it…
Supersedes in part ADR 0001: the device's mesh protocol is MeshCore, not Meshtastic. The rest of ADR 0001 still holds: this is our own firmware, built from libraries, not a fork of anyone's node firmware.
M6 has the official MeshCore app drive the device over Bluetooth Low Energy. The rebuilt framework (ADR 0006) already has NimBLE, ESP-IDF's BLE host, and Arduino's BLE library on top of it. Linked as it comes, it didn't fit (M6…