sd_softdevice_enable() crashes on nRF52832 when debugging

RE: sd_softdevice_enable() crashes on nRF52832 when debugging

Bill Finger — Tue, 23 Jul 2019 21:37:26 GMT

In case anyone runs into this issue using IAR, the key is to add, under Project Options->Debugger->Extra Options, the command line option:

-drv_vector_table_base=0x0

RE: sd_softdevice_enable() crashes on nRF52832 when debugging

raccoon — Mon, 11 Jun 2018 13:16:31 GMT

May the force be with you, I was banging my head for the past 3 hours...

RE: sd_softdevice_enable() crashes on nRF52832 when debugging

Fabien Comte — Mon, 28 May 2018 13:06:27 GMT

Thank you it fixed my issue

RE: sd_softdevice_enable() crashes on nRF52832 when debugging

bjorn-spockeli — Wed, 11 Apr 2018 10:55:45 GMT

Could you post your setup, i.e. SDK version, SD version SES version, HW used etc?

RE: sd_softdevice_enable() crashes on nRF52832 when debugging

jmag999 — Thu, 05 Apr 2018 12:52:03 GMT

Embedded Studio

RE: sd_softdevice_enable() crashes on nRF52832 when debugging

bjorn-spockeli — Thu, 05 Apr 2018 12:34:28 GMT

jmag999: Is this using Segger Embedded Studio or Segger Ozone?

RE: sd_softdevice_enable() crashes on nRF52832 when debugging

jmag999 — Wed, 04 Apr 2018 13:27:27 GMT

I just ran into this same issue trying to debug the DFU project in Segger Embedded Studio. I don't see a similar setting for causing the j-link to start from a reset. Anyone know how to do this?

RE: sd_softdevice_enable() crashes on nRF52832 when debugging

Jimmie Johansson — Wed, 04 Apr 2018 13:06:35 GMT

I know that this is an old question, but I found the solution and it may help another person in the future:

Open the ozone project file (.jdebug) and look for AfterTargetReset and AfterTargetDownload. Change so VectorTableAddress is set to 0x0.

RE: sd_softdevice_enable() crashes on nRF52832 when debugging

bjorn-spockeli — Mon, 10 Jul 2017 14:39:01 GMT

@facotl: So using Ozone, resetting and run does not work for you?

RE: sd_softdevice_enable() crashes on nRF52832 when debugging

Fabien Comte — Fri, 07 Jul 2017 17:34:29 GMT

I have the same issue but no success... (i have a bootloader)

RE: sd_softdevice_enable() crashes on nRF52832 when debugging

bjorn-spockeli — Tue, 09 May 2017 10:51:43 GMT

@fwanner: Does the approach described by Shane work for you?

RE: sd_softdevice_enable() crashes on nRF52832 when debugging

Shane Anderson — Sat, 06 May 2017 21:37:26 GMT

Hello Fabi,

I believe I'm encountering the same error and I think I know why. Note: I'm using the S140 softdevice on the nRF52840, but I believe it's the same issue.

When you are debugging with the J-Link, you load your app past the SoftDevice and the debugger will typically start you in the Reset_Handler of your app. The key here is that debugging avoids running the Reset_Handler in the SoftDevice, which appears to setup a bunch of stuff that must be done before calling sd_softdevice_enable.

On the flip-side, a true reset, launches using the Reset_Handler as specified in the SoftDevice, which then eventually runs the Reset_Handler of your app. As it should be.

So, I think you can possibly specify the initial actions of your debugger and instruct it to do a hardware reset and run from there. I'm currently stuck on this part--I'm using Segger's Ozone and can't seem to find a way to specify the Reset Strategy. However, I have a pretty easy workaround--use the reset button in Ozone and then run from there--that seems to do the trick--I just wish I could get it to reset on first debug.

I hope that helps! (And I hope this is what's really going on..)

RE: sd_softdevice_enable() crashes on nRF52832 when debugging

bjorn-spockeli — Mon, 30 Jan 2017 14:06:08 GMT

Are you able to see if sd_softdevice_enable() returns an error code or doesnt it return at all? As long as you do not step after you hit a breakpoint set after ble_stack_init is called you should be OK.

RE: sd_softdevice_enable() crashes on nRF52832 when debugging

Fabi — Wed, 25 Jan 2017 09:56:16 GMT

I just run the solution without any breakpoint and get a 'SIGTRAP: Trace/breakpoint trap' error in Visual Studio. By placing breakpoints I could figure out that the error occures when executing sd_softdevice_enable(). Because every breakpoint before the execution of this function can be executed, all after this call can not.

RE: sd_softdevice_enable() crashes on nRF52832 when debugging

bjorn-spockeli — Wed, 25 Jan 2017 09:47:36 GMT

How do you know that the nRF52832 crashed when executing sd_softdevice_enable() if you're not using breakpoints? Once you've enabled the SoftDevice you cannot halt the program as this will break the timing requirements of the SoftDevice and it will Hardfault.