Support field recovery
A radio node may be installed where development tools are unavailable. Update and recovery procedures must account for missing drivers, interrupted power, a damaged application image, and operators without source-code experience.
The browser flasher provides the primary update path. UF2 drag-and-drop works without the browser and serial stack. Direct bootloader entry, through a command or hardware action, provides a recovery path when the application is not functioning.
textPRIMARY browser flasher -> verify -> reboot
FALLBACK UF2 volume -> copy -> reboot
RECOVERY bootloader entry -> flash -> verify
Describe the update before transfer
Before transfer begins, the interface should identify the target device, firmware version, erase behavior, and available recovery procedure.
Verify operation after reboot
Update verification continues after transfer. The new image must boot, report its version, initialize the radio, and continue operating within the watchdog requirements.
- Verify the artifact before transfer.
- Keep the bootloader path outside the application image.
- Report the running version after restart.
- Exercise every recovery route in release validation.
These recovery options cover different dependencies, allowing service to continue when one update path is unavailable.