Commit graph

2 commits

Author SHA1 Message Date
R. Sid Shaytay
60d1872f35
Report a dead radio clearly, retry receive once and drop stale repeats
A frequency scan was accepted when the radio was enabled but had failed its
checks, and the client waited for results that never came. It is now refused
with radioUnavailable: "The radio is disabled" or "The radio did not
respond". Generic boards are unchanged (available() equals config.enabled).

One missed switch into RX after a transmission or scan used to disable the
radio until reboot. startReceive() now goes idle and calls SetRx once more
(RADIO_RX_ATTEMPTS = 2, decided by radioRxOutcome) and gives up only after
that. Repeater frames are dropped while the integrated radio is unavailable
instead of being retried and sent stale later.

Serial output in startReceive(), checkBoardRadio() and BoardProfile moves to
ESP_LOG*, and the per-transmission RF switch readback is gone.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-14 18:50:41 -08:00
R. Sid Shaytay
28af01195a
Move the board profile tests into the native Unity suite
The board tests ran through tools/test-board-profile.sh with their own stubs, assert() and a script that copied nine method bodies out of Transceiver.cpp, so they were outside pio test -e native and the coverage report.

Pure decisions now live in units the native env builds: BoardProfile::usesPin is constexpr, RadioReadiness decides register validity, the receive-state outcome (ready, retry or unavailable, with one try today) and whether a queued job may transmit, and ShadeGpioGuard decides whether a shade's outputs touch a board pad. Transceiver and ShadeGpio call them with identical behaviour. New Unity suites cover the generic and LILYGO profiles (reserved pads, startup order, radio bring-up) and the readiness unit; the old harness, its script, CI step and stubs are deleted.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-14 18:47:04 -08:00