At 20 MHz the controller intermittently dropped every Ethernet frame
over about 900 bytes, while small packets got through. The web UI then
hung after the first chunk of a response. At 10 MHz, full-size pings
and repeated fetches of every UI file all succeed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tools/driver_ota.py (make ota-drivers) pushes the driver's .py files
through the controller, one file per POST /drivers/ota/file. Drivers
skip files they already have, and the rest are committed together.
- one target: acked unicast, two chunks in flight
- several targets: each file is broadcast once, then each driver is
asked for its missing chunks and repaired by unicast
- rel: rel_send_seq, rel_wait and rel_send_wait, plus a callback for
the drivers' 0x26 status replies
- commands are retried, because status replies are not acked
- broadcast chunks are paced 50 ms apart: faster broadcast left C3
drivers unable to receive until reset
- bench results in docs/BENCH_TEST.md, endpoints in docs/API.md
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The ESP-IDF project, docs, tools, tests and web UI move from v2/ to the
root, and the Makefile, README, build scripts and test runner drop the
v2/ prefix.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>