Add ONEWIRE_MULTICORE flag to run in multi-core env#104
Open
heeres wants to merge 1 commit intoPaulStoffregen:masterfrom
Open
Add ONEWIRE_MULTICORE flag to run in multi-core env#104heeres wants to merge 1 commit intoPaulStoffregen:masterfrom
heeres wants to merge 1 commit intoPaulStoffregen:masterfrom
Conversation
- At least on ESP32, both cores access the same flash memory and therefore only disabling interrupts is not enough to guarantee proper timing. Setting the ONEWIRE_MULTICORE flag makes sure the critical functions live in RAM, so that no flash latency occurs during execution
|
Similar to #93 |
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
2 participants
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.
I could not get the OneWire library working reliably on my ESP32 board while using both cores: WiFi stuff on core 0, main application on core 1. It seems the culprit is that flash is shared between both cores, and execution will stall when both cores have to access it. The solution is to make the critical functions live in RAM. Perhaps flash access could also result in improper timing in a single core situation, although I did not observe that.