Make sure the scheduling won't start before everything is setup #324
Conversation
This file contains 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.
This fixes some obscure timing related problem that was first reliably discovered in #300 but I think I also have seen it on ESP32-C3's static-ip example (but there it magically disappeared)
This PR disables interrupts globally until all the interrupts are configured
I also found a way to reproduce the problem on current main (at the time of writing) on ESP32-C6:
#[cfg(coex)]preemt/mod.rsmake sure to allocate three stackscargo run --release --example ble --features=ble,wifi(This supersedes #322)