I received my Teensy 3.1 today.
I’ve been compiling several sketches, but when I try to compile the FirstLight example sketch included with FastSPI_LED2, I receive several errors.
I changed the LED Arrangement configuration to: FastSPI_LED2.addLeds<WS2811, DATA_PIN, GRB>(leds+18, NUM_LEDS/3);
The delay.h error I receive is: …FastSPI_LED2/delay.h: In function ‘void _delaycycles_AVR() [with int LOOP = 6; int PAD = 0]’: …FastSPI_LED2/delay.h:33:4: error: unknown register name ‘r16’ in ‘asm’
I’ve attached a screen-cap of the error screen.
Has anyone else seen this, or figured a workaround?
Teensy 3.1 is a new arm CPU - so there’s a bunch of changes I’m going to have to make to support it. I just got mine yesterday and will start playing with it.
I believe that it will mostly just be define juggling, but have still only made one pass over the data sheet.
@trenton_carr that’s a complex question. If you’re going solely by ram available on the device, then probably 10-20,000 rgb leds. However, each WS2811 takes 30µs to update, updating 20,000 rgb leds would take you 600ms (well over half a second) - which would give you a frame rate of about 1.6fps. Not terribly useful. If you were to use something like OctoWS2811 - you could improve things to where it’s 30µs to update 8 ws2811s in parallel - however, the ram overhead of OctoWS2811 halves the number of leds you can use by memory.
The ATTiny85 doesn’t have enough ram. At a minimum, you need 3 bytes of ram available per rgb led - so in your case, you’d need a minimum of 480 bytes available. While the ATTiny85 has 512 bytes of ram, it turns out there’s enough other overhead from things in the world that the practical limit of leds is much lower. (After this release, i’ll be looking into improving memory usage).
I find myself sitting on four T3.1s and seven meters of WS2812b strip. Any word on when a version of FastSPI2 that can be used on a Teensy 3.1 will become available? If it will be awhile I’ll order a few T3.0s for a current project and save the 3.1s for later.
I am still dealing with the life aftermath of some things that happened here recently - and have been pretty much stalled. Is like to get a beta w/3.1 support (and due as well) out by the end of the month. Sooner if this other stuff clears up. (I don’t mean to be a downer - sometimes life has a way of going sideways).
