Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basic_Neopixel not working (interrupt issue) #142

Open
tht opened this issue Oct 16, 2016 · 3 comments
Open

Basic_Neopixel not working (interrupt issue) #142

tht opened this issue Oct 16, 2016 · 3 comments
Labels

Comments

@tht
Copy link

tht commented Oct 16, 2016

The example compiles and uploads just fine. I had to change #define PIN 5 to #define PIN 15. With this value the signal is available on pin D8. The data signal to the LEDs is often interrupted by something else (clearly visible on scope). This adds bad flickering to the LEDs and sometimes wrong colors. I've attached 60 LEDs and a strong lab PSU.

I've also tried some other pins, these are the values I've used:

#define PIN 15 // output on D8
#define PIN 14 // output on D5
#define PIN 13 // output on D7
#define PIN 12 // output on D6
#define PIN 11 // not booting up - WDT resets
#define PIN 10 // not booting up - WDT resets
#define PIN 9 // not booting up - WDT resets
#define PIN 8 // not booting up - WDT resets
#define PIN 7 // not booting up - WDT resets
#define PIN 6 // not booting up - WDT resets
#define PIN 5 // output on D1

I couldn't figure out how these numbers are connected. IMHO this should be documented in the sample application. What I know for sure there is something interrupting the output of the data stream to the LEDs every now and then. Looks like an interrupt issue. It's the same on all the pins listed above.

The ESP8244 (actually a WEMOS D1 mini) and the WS2812B LED strip are good. If I upload a simple NodeMCU program it works flawless.

@tht
Copy link
Author

tht commented Oct 16, 2016

Updated the Adafruit_NeoPixel library to the current version (1.0.6). This does not solve the issue. It's behaving exactly the same as with the included version (1.0.3).

I've also tried to use cli() in void ICACHE_RAM_ATTR espShow(…) to prevent interrupts but this also does not change the behavior.

@tht
Copy link
Author

tht commented Oct 19, 2016

I've switched my development environment to SMING (non-RTOS). I can confirm that there is no issue with interrupts on Sming.

@tht
Copy link
Author

tht commented Oct 19, 2016

Issue may be related to this one:
http://www.esp8266.com/viewtopic.php?f=9&t=3979

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants