KurtE
Senior Member+
I would guess that maybe adafruit.neopixel.show maybe initialized something in hardware the that fastled did not
If you reprogram it again after your fastled hangs, does the reprogram work? If so that could indicate somethings like maybe some startup timings are not working properly or... Been there. Although I have not done anything with fastled.
As I have mentioned before my other strategy for debugging is to use Logic Analyzer. I use it to detect the state of the output going to the LEDS, also I often setup unused IO pins to either toggle or set high and low around pieces of code to help see where the code is going or hanging....
Note: depending on Hang versus Reset... If I am using the Serial.print approach for debug,
You might want to put in Serial.flush calls as well, as you might do a print and the next code line faults (example address a piece of memory associated with a device that the code has not enabled access to that portion of memory). When that happens any data sitting in the USB serial cache will not be output
If you reprogram it again after your fastled hangs, does the reprogram work? If so that could indicate somethings like maybe some startup timings are not working properly or... Been there. Although I have not done anything with fastled.
As I have mentioned before my other strategy for debugging is to use Logic Analyzer. I use it to detect the state of the output going to the LEDS, also I often setup unused IO pins to either toggle or set high and low around pieces of code to help see where the code is going or hanging....
Note: depending on Hang versus Reset... If I am using the Serial.print approach for debug,
You might want to put in Serial.flush calls as well, as you might do a print and the next code line faults (example address a piece of memory associated with a device that the code has not enabled access to that portion of memory). When that happens any data sitting in the USB serial cache will not be output