Improved version for NEOpixel #7136
Unanswered
espruino-discuss3
asked this question in
ESP32
Replies: 1 comment
-
Posted at 2019-02-19 by SergeP I've just created pull request with the changes. File in the pull request is slightly different because I try to make it more readable. So I've changed one variable name and removed some unused code. Posted at 2019-02-20 by Wilberforce @sergep Posted at 2019-02-21 by SergeP I hope you can. I am not sure. Posted at 2019-02-21 by Wilberforce https://github.com/espruino/Espruino/pulls Can't see anything here. Is it in your copy? Posted at 2019-03-06 by @gfwilliams It's now in espruino/Espruino#1621 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Posted at 2019-02-13 by JumJum
@sergep took a closer look to NEOpixel and created a new version.
Please see attached file.
And this is explanation from @sergep
After FIFO maximizing everything works in my case. I've found that, as I wrote, there are two classes of high-priority delays (it may be other interrupts) which delay neopixel_handleInterrupt() call. One class is about 1 original buffer, so about 1,25us*64bit=80us, another one is about 4..5 times longer - 300...400 us.
Now I use full RMT buffer and it's enough to neopixel code work. But it is impossible to use pulses on pins at the same time. This was not possible before my changes, too. But it was possibility to fix that, while my code makes it principially impossible.
Attachments:
Beta Was this translation helpful? Give feedback.
All reactions