nrf51822 debug HardFault Blinky project with openocd

RE: nrf51822 debug HardFault Blinky project with openocd

manuwind — Thu, 27 Feb 2020 16:26:55 GMT

I fianlly got a DK52, SES and project done! a different story...
Thank you

RE: nrf51822 debug HardFault Blinky project with openocd

manuwind — Tue, 10 Dec 2019 16:36:08 GMT

I will try and let you know, thank you!

RE: nrf51822 debug HardFault Blinky project with openocd

Susheel Nuguru — Tue, 10 Dec 2019 12:05:18 GMT

I do not know why OpenOCD debugger connected makes the chip hardfault.

Trying to look around in the devzone for similar old issues shows that many of them got this problem solved after a mass erase.

Normally I would not suggest to do a mass erase on production chips, but, if yours is a development kit then you can try the solutions mentioned here

RE: nrf51822 debug HardFault Blinky project with openocd

manuwind — Tue, 10 Dec 2019 10:30:43 GMT

Hi, Any clue of why the application runs without debugging but crashes when I launch the debugger?

RE: nrf51822 debug HardFault Blinky project with openocd

manuwind — Mon, 09 Dec 2019 11:30:50 GMT

Thank you for your reply. As I mentioned, it is the blinky project from the SDK 11. I am using the Board 20006 for the nrf51822.

RE: nrf51822 debug HardFault Blinky project with openocd

Susheel Nuguru — Mon, 09 Dec 2019 08:18:58 GMT

What is your application? is it using some RTOS ? I am not expert in OpenOCD, but I think based on the hardfault address we should be able to figure out what is going on inside your application.

Normally when you see signal handler at 0xffffff9, then it means that your PC tried to execute some code from the end of the stack. Normally happens when

you have a stack overflow
or when you are trying to derefer some pointers that are not properly initialized.