First go with a tiny85 and it's not happy.  I'm just trying to compile

First go with a tiny85 and it’s not happy. I’m just trying to compile the Blink example and it complains (actually, all the examples complain about the same thing):

Blink.ino: In function 'void setup()':
Blink:28: error: no matching function for call to 'CFastLED::addLeds(CRGB [6], int)'

The tiny cores I’m using were downloaded from http://code.google.com/p/arduino-tiny/
http://code.google.com/p/arduino-tiny

Hold up! That error is only for those controllers where there’s no data nor clock pin defined, plain FastLED.addLeds<WS2801, RGB>(leds, NUM_LEDS);

For those that do have a data pin defined, the error is as follows: http://pastebin.com/uziBzhuh

And for those that have both a data pin and clock pin, the error looks like this: http://pastebin.com/42bUaVW0

Interestingly enough, it compiles without any complaints if I pick the TM1804, but not the -03 nor the -09.

Hrm, I’m missing something.

I think I’m having similar issues.

I haven’t done any work on hardware or software spi for the tiny - I suspect that is contributing to your issues.

Ah - weird, there’s a slight different issue going on there. I’ll have to do some more digging into it.

Doesn’t FastLED work with the Trinket? It has a tiny85 on it …

Yeah - but I suspect adafruit is doing something different library wise for their trinket/gemma setups than what your arduino-tiny dist. is using.

Taa-haa, that could certainly be the case. I’m starting from bare components, straight out of Mouser’s stock room to my breadboard, connected to my programmer (through AS6.1) Other stuff works fine, meaning I can compile the Arduino Blink sketch (for the tiny85) and upload the hex file through AS6.1 and watch them blinkenlights. So that was the same path I took, open the FastLED Blink example, made sure I had the tiny selected and hit compile … No go.

See multiple previous comments about some elements of this release still being tied to elements of the arduino environment (namely, timing adjustments because of the interrupt stopping done by writing leds and default pin access fallbacks).

Yes, I did see that, however it is all done in the Arduino environment as far as the actual coding and compiling goes. The only step done outside is uploading the final (compiled) code. Those errors I’m getting, are all within the Arduino environment. Just opening the IDE, opening the sample sketch, setting the proper hardware, and hitting compile …

Right - in this case, though - while you’re using a modified arduino environment - it’s not providing everything the full environment does (in this case, missing some C++ support in the library, the cxa_guard stuff – though, your first error was because you’re building for something that doesn’t have hardware SPI - so you don’t get to not define pins for any chipsets :). I’ll grab that env over the weekend and figure out what else it is missing.

Actually, it looks like there’s a lot of stuff in that tiny core that’s missing.

Considering it was originally made for version 0018 of the IDE, that doesn’t surprise me. Let me see what the 1.5 version does. One sec.

So - the way adafruit does the trinket/gemma stuff, is they build on top of the arduino core, rather than making a new core. I should define what cores we currently support, it looks like currently that is arduino, teensy, teensy3, avr/arduino, and sam/arduino (the last 2 being arduino 1.5 versions).

Looking at the most recent code they have on their site, it looks like they haven’t changed/improved that side of things.

Yeah, it won’t work with the 1.5 cores they have listed there. Same error. I did try a handful of the stock Arduino IDE examples, and they do compile using those tiny cores. As soon as I use FastLED, picking anything OTHER than the TM1804, it throws errors. Using the 1804 appears to compile, no errors, no complaints, nothing. Of course I don’t have anything to test it on …

TM1804 compiles because I actually forgot to put a reference in there, so it’s compiling, but not including any code.

But yeah - I do a bit more to support the leds than the stock arduino examples do - so i’m not surprised that they work and the fastled stuff doesn’t :slight_smile:

If you want to do ATTiny stuff before I expand support to non-standard cores - look into adafruit’s gemma/trinket support - and there’s articles floating around on how to flash a bare attiny with the gemma/trinket stuff.

Yeah, it’s the same thing the Olimex guys are doing, custom USB boot loader.