Bug esp8266 interupt #368
Open
Bug esp8266 interupt #368
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
|
This pull request is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
github-actions
bot
added
the
stale
foorschtbar
removed
the
stale
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.
Since the update of espressif Framework to V3 there have been problems with the FastLED Lib.
esp8266/Arduino: esp8266/Arduino#8054
FastLED: FastLED/FastLED#1237
The whole thing has something to do with the interups in the ESP8266. These have been changed since V3 and are causing problems. The current workaround is a delay as soon as data is sent to the matrix.
matrix->show()-->FastLED.delay(5); FastLED.show();Firmware works on esp8266 and esp32.
Update:
another Issue: FastLED/FastLED#1374
FastLED/FastLED#1563