With trinket and neopixels. I’m pretty new to this type of programming and in my current project I’m running low on space on the trinket. Would there be anything to gain by stripping out support for other chipsets/controller types leaving only trinket and neopixel? Is that even possible? Has it been done before?
The compiler only includes code that you actually are using, so this is already being done for you automatically. It automatically ‘strips out’ anything that’s not actually called.
While I like the price point of the Trinket, it’s chronically low on memory and CPU power. For an roughly similar price, you could get a DFRobot “Beetle”, or an Arduino Nano v3 (many vendors), either of which is faster and has more RAM, and has the small form factor.
How many pixels are you hoping to drive, and how sophisticated an animation are you hoping for?
Just a ring of 12 pixels, an a bunch of different animations as many as I can fit in I suppose. Nothing special or particularly useful. Just something to show off my new hobby.
Huh. And what’s fitting? (Or not?)
I’ve got 5 different animations at the moment with randomization of the colours and some timing elements. So that’s probably enough at this point. I’ll definitely try out that beetle board next time though.
I am using $2 chinese (Baite) Pro Mini boards with great results - 16MHz/5V/32KB.
If you have to have USB, they do a Nano V3.0 for about a buck and a half more in lots of 10, but at $2 ea, I live with the PITA of FTDI…