Debug Builds
What a Debug Build is, how to build and flash one, how its token works, and why you should keep one in the fallback slot.
A firmware you can drive from your desk: its console over Wi-Fi, its screen as a PNG, its SD card, its crash dumps, and a way back when an update goes wrong.
A Debug Build is the same firmware plus a Debug Console: the serial console, over Wi-Fi, behind a token. It is the most useful thing in the project. With it you can:
Start with Debug Builds to put one on a device, then the Debug Console. The rest are what you can do with it.
What a Debug Build is, how to build and flash one, how its token works, and why you should keep one in the fallback slot.
Connect to a Debug Build over Wi-Fi: the protocol, what you get when you connect, how commands run, and what the console can and cannot do.
Copy files to and from the card, take a screenshot, fetch a core dump and restart the device, all over Wi-Fi, with checksums.
Press keys, take screenshots, fake inputs and test the awkward paths (updates, crashes, fixed IPs, crowded folders) without touching the device.
What happens when the firmware crashes: the report, the core dump, the build it is decoded against, the main-loop watchdog and Safe Mode.
Every command the firmware understands, over USB serial or the Debug Console: what `help` prints, then what each one does.