feat: Add v0.3 OTA updates — dual partition, esp-ota tool, rollback

Dual OTA partition table (ota_0/ota_1, 1920 KB each) on 4MB flash.
Firmware gains OTA command, LED_OTA double-blink, version in STATUS,
and automatic rollback validation. Pi-side esp-ota tool serves firmware
via HTTP and orchestrates the update flow. esp-fleet gains ota subcommand.
This commit is contained in:
user
2026-02-04 16:19:09 +01:00
parent 44bd549761
commit d65ac208b9
8 changed files with 368 additions and 36 deletions

View File

@@ -2,30 +2,45 @@
**Last Updated:** 2026-02-04
## Current Sprint: v0.2 - Remote Management
## Current Sprint: v0.3 - OTA Updates
### P0 - Critical
- [x] Firmware: UDP command listener (port 5501)
- [x] Firmware: LED status indicator (GPIO2)
- [x] Firmware: NVS config persistence (rate, tx_power)
- [~] Build and flash firmware to device
- [x] Create dual OTA partition table (`partitions.csv`)
- [x] Update `sdkconfig.defaults` (4MB flash, custom partitions, rollback, HTTP OTA)
- [x] Firmware: OTA command, ota_task, LED_OTA, rollback validation
- [x] Firmware: Add version to STATUS reply
- [ ] `idf.py reconfigure` to regenerate sdkconfig
- [ ] Build and USB-flash first device (partition table change requires USB)
### P1 - Important
- [x] Firmware: REBOOT, IDENTIFY, STATUS commands
- [x] Firmware: RATE command (10-100 Hz, restarts ping)
- [x] Firmware: POWER command (2-20 dBm)
- [x] Firmware: Refactor ping to support restart
- [x] Pi-side: `esp-cmd` CLI tool
- [ ] Update CHEATSHEET.md with esp-cmd usage
- [x] Pi-side `esp-ota` tool (HTTP server + OTA orchestration)
- [x] `esp-fleet ota` subcommand (sequential fleet OTA)
- [ ] Test OTA end-to-end: `esp-ota amber-maple.local`
- [ ] Regenerate `sdkconfig.sample`
### P2 - Normal
- [ ] Document esp-cmd in USAGE.md
- [ ] Add Kconfig CSI_CMD_PORT option
- [ ] OTA update remaining fleet (muddy-storm, hollow-acorn) via USB
- [ ] Test rollback (flash bad firmware, verify auto-revert)
- [ ] Document esp-ota in USAGE.md
### P3 - Low
- [ ] Document esp-crab dual-antenna capabilities
- [ ] Document esp-radar console features
## Completed: v0.2 - Remote Management
- [x] Firmware: UDP command listener (port 5501)
- [x] Firmware: LED status indicator (GPIO2)
- [x] Firmware: NVS config persistence (rate, tx_power)
- [x] Firmware: REBOOT, IDENTIFY, STATUS commands
- [x] Firmware: RATE command (10-100 Hz, restarts ping)
- [x] Firmware: POWER command (2-20 dBm)
- [x] Pi-side: `esp-cmd` CLI tool
- [x] Pi-side: `esp-fleet` fleet management tool
- [x] mDNS hostname, watchdog, human-readable uptime
- [x] Build and flash to device
- [x] Update CHEATSHEET.md
## Completed: v0.1 - Documentation
- [x] Copy firmware sources to project
@@ -34,12 +49,11 @@
- [x] Create .gitignore for build artifacts
- [x] Test building firmware from this repo
- [x] Document CSI config options
- [x] Compare csi_recv vs csi_recv_router differences
## Notes
- Build confirmed working on ESP-IDF v5.5.2 (aarch64/Pi 5)
- v0.2 firmware adds ~1.5 KB heap + 6 KB stack usage
- NVS namespace: `csi_config` (keys: `send_rate`, `tx_power`)
- LED uses GPIO2 (built-in on most ESP32 dev boards)
- Command port default: 5501 (configurable via menuconfig)
- NVS offset changes with new partition table — first USB flash resets saved config
- First device must be USB-flashed to switch partition table, subsequent updates via OTA
- `esp_https_ota` is built into ESP-IDF core — no extra deps needed
- OTA download ~790 KB on LAN takes ~3-5s, well under 30s watchdog
- CSI data keeps flowing during OTA download