These are chat archives for Makuna/NeoPixelBus

21st
Oct 2015
patjazz
@patjazz
Oct 21 2015 10:05
hi @Makuna .
1) If i compile with 160Mhz option, nothing seems to work in setup() ???? (OK in loop() !)
2) is stability problems with gpio15 ? Also, I can’t use it with gpio16 ?
sticilface
@sticilface
Oct 21 2015 10:34
I discovered that as well. Nothing works in setup, but loop is fine. Not sure why. Hadn't tried with 160mhz.
sticilface
@sticilface
Oct 21 2015 12:28
Sorry hadn't tried that at 80mhz. I only use 160...where it doesn't work!
Which branch are you using. Uart branch?
patjazz
@patjazz
Oct 21 2015 14:22
I’m using "NeoPixelBus-master » and an esp12e on a board i made with WS connected on gpio16 -> don’t work. I wire on gpio15 (10k pulldown) -> erratic working….. so now, I wire it on gpio14 ! ;-) and i have to low cpu to 80Mhz… pfffttttt
I must say, my first use of IDE/SDK 10 month ago where more stable…. Now, with last staging… i have to rewrite many parts of my apps. (many new WDT errors)
sticilface
@sticilface
Oct 21 2015 14:51
There is an issue with the bit banging part of neopixels, and it is basically broken until something changes with the esspressif sdk... i would recommend using the uartbranch, and only GPIO2 for neopixels. how many pixels are you using? the fact that nothing is working for you in setup(), and that this occurs with all branches is interesting.
its not neopixels per say.... just anything that involves pausing interrupts... causes a reset... eventually...
patjazz
@patjazz
Oct 21 2015 16:34

Whis 160Mhz compil option, CPU is at 80Mhz in setup() and 160Mhz in loop()….. very strange no ? :
´´´
xxxx test xxxx

set up

Free Heap: 46120
Boot Vers: 31
CPU : 80
SDK : 1.3.0
Chip ID : 15951091
Flash ID : 1458400
Vcc : 65.53

ESP.getFlashChipSize : 4194304
ESP.getFlashChipRealSize : 4194304
ESP.getCpuFreqMHz : 80
ESP.getFlashChipSpeed : 80000000
ESP.getFreeSketchSpace : 823296
ESP.getVcc : 65535
ESP.getSketchSize : 223084

loop
Free Heap: 46120
ESP.getCpuFreqMHz : 160
´´´

sticilface
@sticilface
Oct 21 2015 16:38
ah well that would explain it then, good find
Michael Miller
@Makuna
Oct 21 2015 16:42
@patjazz GPIO16 was never supported. That pin is special on the ESP and doesn't work like the others requiring extra code which slows down the timing.
In general Arduino programming, you should avoid any work in Setup other than initializing the objects. Unfortunately this isn't widely adhered to and you see samples that really are not good samples. For the ESP, as sticilface stated, there things that happen with Wifi startup that cause interrupt hickups to happen.
Michael Miller
@Makuna
Oct 21 2015 16:47
@patjazz you should bring up the 80mhz in Setup and 160mhz in Loop on the esp8266/Arduino gitter group to see if this is a requirement. But it does sound like it could be a problem.
patjazz
@patjazz
Oct 21 2015 17:30
@Makuna I know for GPIO16 (but for me it should be only an optional RST add-on). In teh setup(), i just have a led that indicate the boot state progress by colors ! so, not an x-mas tree !
For the rest, i think really that ESP-IDE-SDK loss stability since i use it… And this is problematic.
I have also another problem : i have 2 prototypes esp12
  • one is just plug in an USB alimentation (2A) and run an meteo station that show on OLED and send infos wia WiFi…..
  • another one on witch i upload/test other apps…. and, sometime, at the (near ?) end of uploading, the 2 ESP resets !
    (on the first one, i have tested OTA…. is there some relation ?)