NRF_BREAKPOINT causes hard fault with ARM-GCC

RE: NRF_BREAKPOINT causes hard fault with ARM-GCC

liteyear — Wed, 12 May 2021 22:42:00 GMT

This Q never seemed to get A'ed, and I recently ran in to it and solved it, so FWIW, here's what I found:

I also found __builtin_trap() resulted in an "undefined opcode" and a hard fault. Then I stumbled across another version of NRF_BREAKPOINT defined like this instead:

#if defined(__GNUC__)

#define NRF_BREAKPOINT __asm__("BKPT 0");

#else

#define NRF_BREAKPOINT __BKPT(0)

#endif

which works as expected on a nRF9160 using the NRF Connect SDK, despite this code not otherwise appearing in that SDK anywhere.

RE: NRF_BREAKPOINT causes hard fault with ARM-GCC

bjorn-spockeli — Fri, 12 Jan 2018 10:31:47 GMT

You should not have any issues with GCC ARM Embedded 4.9 2015q3. Could you create a new question and describe your setup and post the build output?

RE: NRF_BREAKPOINT causes hard fault with ARM-GCC

vincent.golle — Thu, 11 Jan 2018 15:00:23 GMT

Hi,

I am having the same issue Austin exprienced with both GCC 4.9 2015q3 and GCC 6.3.1

RE: NRF_BREAKPOINT causes hard fault with ARM-GCC

bjorn-spockeli — Wed, 20 Sep 2017 09:08:13 GMT

Hi Austin ,

SDK v14.0.0 has only been production tested using GCC ARM Embedded 4.9 2015q3, stated in the nRF5 SDK v14.0.0 Release Notes.

Thus I recommend that you use the same version of the toolchain when developing.

Best regards

Bjørn

RE: NRF_BREAKPOINT causes hard fault with ARM-GCC

Austin Glaser — Tue, 19 Sep 2017 21:59:59 GMT

I'll take a look at the monitor mode debugging. For me, using the debugger is a core part of my workflow, though this is more of a question of ergonomics than functionality.

RE: NRF_BREAKPOINT causes hard fault with ARM-GCC

Matt — Tue, 19 Sep 2017 21:58:21 GMT

This may have something to do with the monitor mode debugging: devzone.nordicsemi.com/.../

I seldom use breakpoint and rely on the Segger RTT (real time terminal) instead for tracing purpose.