-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request Support for Addressable LED Libraries #171
Comments
Hi Owen (@oclyke), |
Oh cool!!!!! I did not know you had been working on that. Thanks a bunch! |
I am getting the error "Unrecognised APOLLO3 board!" Looks like there is a mismatch of board definitions with those expected in the FastLED library file fastpin_apollo3.h I noticed that the DevKit is not actualy defined in that file so I defined that, trying a format found in the board definitions for apollo3. Here is that code
|
Rolling back to v1.2.1 I can compile FastLED sketches. So it must just be a rename of the board defs in the new v2 core |
Nope wait, I just had the board set to Yun accidentally. Same error in v1.2.1 |
Ok, it's working with the nano now but not the dev kit. It must be that I have the board def for it wrong in that file. |
Ok finally got the board def name right and it compiled. Not sure if the pins are right here still as I just copied the ATP pins above.
|
So with that the Dev Kit will work with FastLED on the v1.2.1 core |
I'm new to the FastLED library and looking to add support for the MicroMod Artemis Processor (for now to the 1.2.1 Apollo Core). Going off of @PaulZC's previous work, it appears that the
There does appear to be a small conflict between the
However, once Are any other files required to be changed? |
Hmm, actually with the above modifications to
This does not:
The LED seems to default on and never change. Similar behaviour is experienced when trying to set and leave the colour of the LED. Cheers, |
closed due to inactivity |
We want to support both FastLED and NeoPixel libraries
Requests:
Resources:
The text was updated successfully, but these errors were encountered: