Delay startup of STM32/decks with 1s to avoid GAP8 freeze #69
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.
When moving from bootloader to firmware on the nRF51 or when doing quick power off/on on the button, we've seen that the GAP8 end up in a state where it freezes and we need to power it off for a long while to get it to start again. It seems to be handling "quick" off/on cycles badly. This is fairly easy to reproduce in two cases:
Note that the behavior seems to be a bit different on different boards, some are very easy to freeze others not.
Initially the time when the STM32/decks domain was powered off was about 350-400ms when moving from bootloader to firmware. Keeping the power off for longer seems to solve the issue with the GAP8 freeze, this is also true for quickly powering off/on the platform. After doing some quick testing it seems as if 1s is enough, but we should test some more boards.
At this point we have information about the 1-wire memories and it would be possible to only have this delay when the AI-deck is attached, but this would create a special case that might be confusing down the line if there's any issues.