toggle quoted messageShow quoted text
The board is one of these: http://www.waveshare.com/nrf51822-eval-kit.htm
I have been flashing it with STLink + OpenOCD and I’m trying to figure out how I can debug the chip with that setup + GDB. I am not using the Nordic dev kit. Let me know if there’s any additional info I can provide and thanks for you help!
Is there a way I can override the Zephyr fault hander so that I could, for example, flash an LED or repeatedly log something to the serial output?
On Aug 14, 2017, at 1:51 PM, Cufi, Carles <Carles.Cufi@nordicsemi.no> wrote:
Can you tell us a bit more about the board itself and whether you can debug post-mortem by plugging it and attaching to the executing code? Are you using a Nordic development kit and if not, are you using a Segger debugger chip?
On 14/08/2017, 19:46, "firstname.lastname@example.org on behalf of Scott Nelson" <email@example.com on behalf of firstname.lastname@example.org> wrote:
I’m running the Zephyr RTOS on an NRF51822 board. Occasionally I notice that the code execution is hung up for some reason (I have a status LED that stops flashing and I can no longer connect via BLE). I’m assuming there’s some kind of fault and I’ve tried debugging this by capturing the serial output (Zephyr logs faults, etc.). Oddly though, the issue never seems to arise when I have a little USB-to-serial board plugged in. How do you recommend I get to the bottom of this?
Zephyr-users mailing list