These are chat archives for Makuna/NeoPixelBus

4th
Jun 2015
Michael Miller
@Makuna
Jun 04 2015 04:47
Could you look in Arduino.h for the no interrupt macro, copy it into here
sticilface
@sticilface
Jun 04 2015 06:47
#define noInterrupts() __asm__ __volatile__("rsil %0,15; esync; isync; dsync" : "=a" (interruptsState))
Michael Miller
@Makuna
Jun 04 2015 07:16
What esp do you use again? That initial bit/pulse starting early and lasting long was what I was seeing before I added the isync to the nointerrupts, you have this though. I will do some more research.
sticilface
@sticilface
Jun 04 2015 11:00
This is happening on ESP-01 and ESP-12s (i have a test rig, 2x 2m strips, and 1 144m stip.. so 4 eps in total). If a binary flashes on the test rig, it flashes on all of them..) Using even using the latest IDE. i'm suspicious that it might be some compiler or memory thing. Why am i suspicious... considering that I know nothing about how any of this works... well... it is seemingly random. it will be there. then i add a variable, remove a serial.print. and it goes away.. there is no common factor to it, that i can identify. I'm trying to provide you with two simple versions 1 that flashes and one that doesn't
your help is much appreciated btw.
Michael Miller
@Makuna
Jun 04 2015 14:41
Its a strange problem. Something else to try is to move the include for NeoPixelBus.h to the top (not sure this really does anything) on the thought of memory layout of the instructions might be an issue.
sticilface
@sticilface
Jun 04 2015 16:03
Indeed.. here is a link to an .ino that blinks... it didn't blink, then i moved the neopixelbus.h to the top and boom... blinks especially when you hit refresh on a web browser. you'll have to put your wifi credentials in... at the top, -/+ MQTT server if you have one... i've taken most stuff out.
I apologise in advance for the messy coding. not been at it for very long