twislaandClaude Sonnet 5.5
3b4100dc6a
/dev/ has Debug Builds and the Debug Console (builds and the token, the console and its protocol, files and screenshots, driving the UI, crashes and Safe Mode, the command reference), Build, test and release (including how an update works), the architecture decisions and the milestone plans. Generated from the repository by site/tools/gen_dev_docs.py: the ADRs, the milestones, the README's sections, and the command reference, read from the firmware's own `help` text. The pages are committed (Zola cannot read outside its folder); the Site workflow checks they are current, and now also runs when src/main.cpp changes. M0, M1 and CONTEXT.md are not published. README: the gnss commands that the table lacked. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT
1009 B
+++ title = "Developer docs" description = "How roro9stack is built, debugged, tested and released: the Debug Console, the build, the decisions and the plans, from the repository's own documents." template = "dev-index.html" sort_by = "weight"
[extra] eyebrow = "Developer docs" +++
The firmware is open source (GPL-3.0) and lives on Gitea. It is built for one device, the M5Stack Cardputer ADV with the Cap LoRa-1262, and it is built to be worked on without touching the device: install a build over Wi-Fi, read its console, press its keys, take screenshots of it, copy files to and from its SD card, and fetch its crash dumps, all from a PC on the same network. The first section is about exactly that.
Some of these pages are written by hand. The rest are generated from the repository's own documents (the decisions, the milestone plans, the README and the firmware's own help text), so they are never out of date: each says which file it comes from.