I’m able to use openocd to debug my application using the 5 steps post and I found another post from @rickkas7 where it mentions not to use the debug button, but rather, use the debug history (that helped a lot, it should be in the docs). What I’m not able to do is figure out where the firmware locks up when it stops breathing cyan (cyan on full, no breathing). I can’t quite tell from the output (sorry, my machine rebooted unexpectedly last night, so I don’t have the exact line), but it looks as if there was a SIGINT somewhere and I couldn’t do a backtrace to figure out where it happend. There was no output other than the SIGINT from gdb either.
This is just an LED controller, there are no other peripherals attached, so it’s not like I’m seeing I2C hang for me or something. I’m using FastLED 3.1.5.
Is there a way to use gdb to figure out what happens when the led breathing goes solid cyan?