Description
I have been running into an issue where the hard-fault handler gets triggered on the Feather nRF52840. Unfortunately, the board starts flashing yellow and isn't visible on USB when this happens: neither as a serial port, nor as a drive. Pressing reset is required.
I tried disabling the bluetooth code.
I tried 5.0.0b2
I tried master
I tried new-pixelbuf-api without bluetooth code.
I tried not using pixelbuf at all (just neopixel).
I tired without USB connected.
The same code on the Feather M4 (except the bluetooth part) works fine and is still running hours later.
The NRF board always eventually hardfaults. All tests are running the animations. Using pixelbuf speeds up the fault. Using the classes that slice pixelbufs cause faster faults.
Tracing with the JLink was inconclusive... The hardfault was happening from an unknown address.
TODO: Test on a fresh Feather NRF board.