Repository navigation
fix(boot): skip the boot screen when no panel responds - #179
Merged
Merged
Conversation
After a reset every controller reports idle on BUSY within milliseconds. If BUSY stays busy for 2 s there is no panel (or a dead one), and every later BUSY wait would run into its timeout: booting without a panel took about 10 minutes, now about 4 seconds. Dual chip-select panels are not probed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Booting with no panel connected (or a panel that does not respond) took about 10 minutes: every BUSY wait in the boot-screen path ran into its timeout. This adds a short presence check before the boot screen.
bootPanelResponds()pulses the panel reset and waits up to 2 s for BUSY to report idle (HIGH on UC81xx, LOW on SSD16xx). After a hardware reset every controller does that within milliseconds, which is also what the GoodDisplay sample code waits for. If BUSY stays busy,initDisplay()logs a warning, cuts the rail withpwrmgm(false)and skips the boot screen.pwrmgm(false)instead ofepdSessionForceOff(): ForceOff sends sleep commands and waits on BUSY, which is exactly what hangs here (same pattern as the FastEPD init-failed tail).BBEP_SPLIT_BUFFER) panels, and configs without a BUSY or RESET pin, are not probed (untested), so their behaviour is unchanged.Testing
On a Seeed EN04 (nRF52840), with this change on top of a branch that also adds new panels (not part of this PR):
Panel not responding (BUSY stays busy after reset) - skipping boot screen, BLE works and a config can be written.Builds against the current bb_epaper pin:
nrf52840custom,esp32-s3-N16R8,esp32-c3-N4,esp32-wrover-e-N4R8.🤖 Generated with Claude Code