Your thoughts? about esp8266ws2812i2s HOT 7 CLOSED

hey, I'm really sorry it took so long to get back in the swing of things.

You can totally just call whatever you want from inside the interrupt. You can actually do a fair bit in there. That's how I did a lot of the stuff for my Channel3 project. I would STRONGLY recommend bigger buffers though, and there is so much overhead when getting an interrupt called. Function calls aren't free.

That's not to say some degree of buffering wouldn't be good. It is annoying to give up such a huge buffer :-/... so I don't really know what the right answer is.

from esp8266ws2812i2s.

Thanks for your thoughts :) I've been tinkering a lot towards this already. Last code is here:
https://github.com/cranphin/esp8266-dev/blob/master/esp8266-neo/dev/driver/ws2812_i2s.c
though there is no interrupt handling in there, -YET- :)
My local code does have it, and it almost works? :)
But I think I'm running exactly into what you're suggesting, possibly.. at 32 byte buffers, the interrupt might not finish fast enough to actually fill the next buffer before it's used.. :)

Will try and test more, could be another bug.. I also need more rgb leds.. XD 8 is not enough to test with larger buffers.. :) Should have a string of 30 here soon ;)

from esp8266ws2812i2s.

30? We routinely use 300+! Rolls are ~$25, you don't have an excuse :-p

from esp8266ws2812i2s.

I have to justify expenses with my better half, it's a limiting factor :)
And 30 leds I'm confident of driving of a usb charger, more I might have to look into better power supplies, and things add up :) But we'll see how 30 goes, then consider going up more ;)

from esp8266ws2812i2s.

Do you actually have source code for the stuff in the web folder?

Right now, it seems to be just symlink paths in the .c files...

Or is this supposed to be relative to YOUR entire github layout (not a standalone project)?

from esp8266ws2812i2s.

A little of colmun B.

The symlinks you refer to, point to files in the ./esp82xx directory, which is a git-submodule. Think of submodules as a link to a specific commit in another repository. By default, git does not clone submodules when you clone a root project. I suspect, that is what's throwing you off.

To mitigate that you have either make recursive cloning default (git config --global alias.clone = 'clone --recursive') or use

    git clone --recursive https://github.com/cnlohr/esp82xx.git

every time you clone a repository that uses submodules. With an already cloned repository you'll need to run

git submodule update --init --recursive

Submodules are the most common way to include other code and split up development effort. The next most common way would be subtrees.

You should look into the basics of git.

from esp8266ws2812i2s.

Just as a reminder by me. Thank you, @con-f-use for making "make" get the recurse if you forget to do it the first time.

from esp8266ws2812i2s.