Skip to content
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

teensy 4.0 only parallel output works, garbage output when FastLED.delay() is used #912

Open
apleschu opened this issue Oct 25, 2019 · 4 comments

Comments

@apleschu
Copy link

@apleschu apleschu commented Oct 25, 2019

With a teensy 4.0 only parallel output works. When compiling with without the parallel output it compiles fine, but the output is garbage.

FastLED.delay() also creates garbage output. The same code changed to delay() works.

@marmilicious

This comment has been minimized.

Copy link

@marmilicious marmilicious commented Oct 27, 2019

@apleschu Please put your code on pastebin.com or gist.github.com and share a link to the code so others might be able to better help you.

@apleschu

This comment has been minimized.

Copy link
Author

@apleschu apleschu commented Oct 29, 2019

@marmilicious This very simple code works: Please note that this is for parallel output. when I change this for non parallel output, the same code on the same HW does not work. Also if the delay() calls are changed to FastLED.delay() again, the code does not work. This is the most simple I could make the example to show the problem.

The hardware in question is a teensy4.0 and a strip of 2812B attached. No level shifters nothing else that could create a problem.


#include <FastLED.h>
#define NUM_LEDS 1
#define DATA_PIN 10

// Define the array of leds
CRGB leds[NUM_LEDS];

void setup() { 
     FastLED.addLeds<1,WS2812B, DATA_PIN,GRB>(leds, NUM_LEDS);
     FastLED.setBrightness(10);
}

void loop() { 
  leds[0] = CRGB::Red;
  FastLED.show();
  delay(500);
 
  leds[0] = CRGB::Black;
  FastLED.show();
  delay(500);
}
@apleschu

This comment has been minimized.

Copy link
Author

@apleschu apleschu commented Nov 1, 2019

@marmilicious I have seen this post, thats why I know that parallel output does work. Not the best for code portability, and still a bug in my book, but OK. The problem now starts if you have many strips of different length (as I have in the project I am working on) Parallel output assumes that you have a number of strips of the same length.

In addition that does not deal with the problem of the FastLED.delay()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.