Repository navigation
clear-wifi: wait 60 s for the pod's C3 NVS erase - #42
Merged
Merged
Conversation
The pod answers wifi-clear only after it erased the ESP32-C3's NVS over the C3's ROM loader. The 10 s timeout cut that off on new digital pods (2026-10-15). 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.
benchpod clear-wifitimed out on new digital pods (2026-10-15). The pod answerswifi-clearonly after it has erased the ESP32-C3's NVS over the C3's ROM loader (16 blocks). That takes a few seconds normally, and longer when blocks have to be resent. The 10 s default cut it off. The default is now 60 s, and--timeoutstill overrides it.Firmware side (fewer resends, faster erase): embeddedci-com/benchpod-firmware#56.
Tested:
go build,go vet,go test ./cmd/... ./internal/serialconsole/....🤖 Generated with Claude Code