Switch the console on
The Debug Console is in every firmware, and off. How to switch it on, where its token comes from, and how to set a device up without typing anything.
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.
The Debug Console is the serial console, over Wi-Fi, for whoever holds the device's token. It is in every firmware, switched off until you switch it on, and it is the most useful thing in the project. With it you can:
Start with Switch the console on, then the Debug Console. The rest are what you can do with it.
The Debug Console is in every firmware, and off. How to switch it on, where its token comes from, and how to set a device up without typing anything.
Connect to the console 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.