Fix nrf52 radio init recovery#2869
Open
yg-ht wants to merge 2 commits into
Open
Conversation
yg-ht
force-pushed
the
fix-nrf52-radio-init-recovery
branch
from
7836920 to
d4074e8
Compare
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
1 participant
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.
Turns out this isn't the bug I was looking for....
However, I think this might be useful anyway so thought I would hand it over to the community just in case.
When trying to work out the cause of a brown-out recovery issue (think very low-battery situations) I spotted that there are some edge-case scenarios that could result in the board hanging on boot if the radio doesn't come online correctly. To work this out I ended up implementing a load of instrumentation as well as some routines that should prevent trivial lockups from occurring if the power rail isn't stable enough to support a radio init at boot time.