Fixed interrupt handling on ESP8266#27
Open
matthias-bs wants to merge 1 commit intopimatic:masterfrom
matthias-bs:patch-1
Open
Fixed interrupt handling on ESP8266#27matthias-bs wants to merge 1 commit intopimatic:masterfrom matthias-bs:patch-1
matthias-bs wants to merge 1 commit intopimatic:masterfrom
matthias-bs:patch-1
Conversation
With ESP8266 Arduino noard support package V3.0.0 an exception is issued whenever an interrupt occurs: [...] connected...yeey :) HTTP server started local ip: 192.168.156.166 *WM: freeing allocated params! pm open,type:2 0 handleReceive() ISR not in IRAM! User exception (panic/abort/assert) --------------- CUT HERE FOR EXCEPTION DECODER --------------- Abort called >>>stack>>> [...]
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.
With ESP8266 Board support package V3.0.0 an exception is issued whenever an interrupt occurs:
This is not specific to RFControl. I found a hint to fix the issue as follows:
Change
to
and added some C pre-processing to leave the code untouched for non ESP8266 targets.