Hallo I am trying a wemo D1 (esp8266) board with fast led but there

Hallo I am trying a wemo D1 (esp8266) board with fast led but there an error http://codepad.org/mMF48Ptu seems like __cxa_guard is defined in both libraries …

try using a old version of arduino like version 1.6.4 or older might help helped me a lot

its version 2.1.0 of the esp8266 core.

There is an issue open on github #266 that has a work around.

You can also go to Boards Manager, find esp8266 by ESP8266 Communitiy, click on More info and Select version 2.0.0 or older

Ok great, I even tried to get it with git , but I see it is a problem with the latest version, thanks

yeah getting it manually with git is a bit rough. It works, but its rough, especially in Arduino 1.6.4 - its a bit smoother in 1.6.7 (the arduino project is quite the moving target).

Arduino 1.6.7 is broken for FastLED (well its ctags that is broken) and so is 1.6.8 - but 1.6.8 hourly builds after jan 20th are fixed.

I manually installed the latest master of esp8266 core (which is needed for websockets), and that got my tool-chain fixed, on Arduino 1.6.5-rc4, with master FastLed. But the collision will remain until issue #266 is fixed.

So FastLED is working on ESP8266 now?
I asked months ago and it wasn’t compatible…

Almost there, it didn t work in Windows but in Linux as you suggested (1.6.5 and latest fastled) it compiles but at the end of th eupload I get a
warning: espcomm_send_command(FLASH_DOWNLOAD_DATA) failed
warning: espcomm_send_command: wrong direction/command: 0x01 0x03, expected 0x01 0x04

Ahh… Ok. Keep cracking at it. I have a few projects in mind that would depend on it. Lol

@Jon_Bruno ​ yes FastLED is working just fine on arduino 1.6.4 and 1.6.5-rc4 but not 1.6.7 or 1.6.8 - that said. FastLED is working with esp8266 core 2.0.0 but 2.1.0 will throw an error.

error "XTENSA-architecture microcontrollers are not supported?

dropping back to 2.0… I’ll try again

@Jon_Bruno ​ make sure you have the latest FastLED from the master branch at github.

i can use one of the examples from Fastled and get it working but if I try my own code, which is just some serial reading which controls the leds, it does not work. The same code in an Arduino UNO works just fine. Is there any catch up in the serial communication I am missing here?

@Simone_Marin ​ i havent tried reading from serial (given that its the wifi chip) but reading from serial often has garbage first the first few lines. I doubt its FastLED. Try reading from serial and echoing it back as your first test.

Do you mean that when I do a serial read it is reading from the lines attached to the wifi module and not from the USB ?

@Simone_Marin ​ no. I meant, that given everyone buys the esp because of its wifi features, reading from serial is not a feature that will get used too often. You should write some code that echos back what it recieved and validate that the esp core is working the way you expect, before integrating FastLED. #babysteps

@Stuart_Taylor Thanks! that was the trick. question, without me digging through the cfg files… what do we call GPIO 0 and GPIO 2 when referencing them as LED_PIN ? “0” and “2” ?

and is this ok? #warning “No hardware SPI pins defined. All SPI access will default to bitbanged output”

@Jon_Bruno ​​ gald to hear its working. I defined pin13 and thats where the led data came out. Dan has done the hard work for us.
Yes. Its just a warning. Not an error.