Files
MeshCore/variants
agessaman 51cbab5311 feat(rak3401): report onboard SX1262 sleep state via BUSY
BUSY is driven low in STDBY_RC and high while asleep, so reading it either
side of the sleep gives a non-invasive readback of the state the chip was
found in and the state it was left in. Confirmed on hardware.

This is what makes the sleep observable at all. The only other symptom of
a failed sleep is ~600 uA, which is below what an inline USB meter can
resolve, so without this a regression would be silent.

It immediately earned itself: busy_before reads 0 on every boot, showing
the cold sleep does not survive an MCU reset. GPIOs revert to input during
reset, NSS stops being driven high, and the falling edge wakes the chip.
The helper re-sleeps it, so this is self-healing, but it means the chip is
never found already asleep.
2026-08-17 22:19:49 -07:00
..
2026-08-13 00:12:37 +10:00
2026-07-06 12:04:42 -04:00