Skip to content

docs: clarify bounded busy recovery #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
flowcool merged 3 commits into from
Oct 20, 2026
Merged

docs: clarify bounded busy recovery #19

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f4e260a
docs: align BUSY guide with bounded emergency sleep
flowcool Oct 20, 2026
f4399bd
Merge branch 'V2R1' into docs/busy-recovery-guide
flowcool Oct 20, 2026
96e87b1
Merge branch 'V2R1' into docs/busy-recovery-guide
flowcool Oct 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions examples/multi-device/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,10 +126,13 @@ window.

Maintenance Status becomes `DISPLAY_REFRESH_FAILED` when the firmware cannot
confirm a complete BUSY HIGH-to-LOW refresh cycle, and OTA readiness is not
published. If BUSY remains high, `DISPLAY_BUSY_TIMEOUT` is reported and the
device refuses deep sleep or a power cut so the panel is not interrupted. A
lightweight recovery loop keeps observing BUSY and resumes safe sleep
automatically 500 ms after the line eventually clears. Every daily Storage wake
published. If BUSY remains high, `DISPLAY_BUSY_TIMEOUT` is reported and normal
sleep is deferred. Recovery observes BUSY with one total 30-second budget across
retries and final sleep delays. If it cannot finish safely, the terminal path
resets the panel and requests emergency sleep. Native shutdown hooks remain
active, including the driver's final SPI sleep command. See
[display recovery timing](../../docs/display-recovery.md) for the distinction
between the bounded sleep action and physical sleep. Every daily Storage wake
reads and publishes a fresh battery value, refreshes the Storage page once, and
keeps temperature, humidity, light, and soil acquisition disabled.

Expand Down
Loading