Unable to enable the softdevice on custom board.

RE: Unable to enable the softdevice on custom board.

Sourabh — Tue, 21 Nov 2017 09:09:50 GMT

The issue was with the RAM settings, i made the appropriate change referring to the softdevice specification.

RE: Unable to enable the softdevice on custom board.

Petter Myhre — Mon, 20 Nov 2017 15:23:31 GMT

Sorry, that should have been included in my comment. Edited now.

RE: Unable to enable the softdevice on custom board.

reva — Mon, 20 Nov 2017 15:21:52 GMT

Thank you for your answer. I set NRF_SDH_CLOCK_LF_RC_CTIV to 16 and it works now. And one more question: if my board will be contain XTAL 32.768 kHz, can I set NRF_SDH_CLOCK_LF_SRC to 1 and CLOCK_CONFIG_LF_SRC to 1 simultaneously?

RE: Unable to enable the softdevice on custom board.

Petter Myhre — Mon, 20 Nov 2017 15:09:56 GMT

NRF_SDH_CLOCK_LF_RC_CTIV can't be 0, for nRF52 1-32 is valid. 16 recommended.

NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2 is recommended.

NRF_SDH_CLOCK_LF_XTAL_ACCURACY should be set to NRF_CLOCK_LF_ACCURACY_500_PPM = 1

NRF_SDH_CLOCK_LF_SRC 2 -> LFCLK Synthesized from HFCLK is according to SoftDevice release notes not recommended:

Synthesized low frequency clock source is not tested or intended for use with the BLE stack.

RE: Unable to enable the softdevice on custom board.

reva — Mon, 20 Nov 2017 14:33:40 GMT

I can enable softdevice successfully now if NRF_SDH_CLOCK_LF_SRC=2. But I get NRF_ERROR_INVALID_PARAM error from sd_softdevice_enable() if NRF_SDH_CLOCK_LF_SRC=0 (NRF_SDH_CLOCK_LF_RC_CTIV=0, NRF_SDH_CLOCK_LF_RC_TEMP_CTIV=0, NRF_SDH_CLOCK_LF_XTAL_ACCURACY=1). Why can it be so? ps: I have no 32.768 kHz crystal on my board.

RE: Unable to enable the softdevice on custom board.

Petter Myhre — Mon, 20 Nov 2017 09:53:03 GMT

So how far do you get? Where do you get "stuck"?

RE: Unable to enable the softdevice on custom board.

reva — Thu, 16 Nov 2017 17:17:31 GMT

Yes, I'm going through sd_state_evt_handler() in nrf_drv_clock.c.

RE: Unable to enable the softdevice on custom board.

Petter Myhre — Thu, 16 Nov 2017 16:44:02 GMT

Then I recommend you to try to debug a bit more. Turn off optimizations. You are both saying that you are not getting past sdh_state_observer_notify(NRF_SDH_EVT_STATE_ENABLED);?

sdh_state_observer_notify() should notify sd_state_evt_handler() in nrf_drv_clock.c and nrf_fstorage_sdh_state_handler() in nrf_fstorage_sd.c

If you put breakpoints in these? Are they hit? If they are, are you getting through the function?

RE: Unable to enable the softdevice on custom board.

reva — Thu, 16 Nov 2017 13:42:56 GMT

No, it doesn't help.

RE: Unable to enable the softdevice on custom board.

Petter Myhre — Thu, 16 Nov 2017 12:55:11 GMT

What if you set NRF_SDH_CLOCK_LF_XTAL_ACCURACY to 1 (NRF_CLOCK_LF_XTAL_ACCURACY_500_PPM)?

RE: Unable to enable the softdevice on custom board.

reva — Wed, 15 Nov 2017 20:29:24 GMT

I have the same problem with my BMD-300 on nRF52832 (s132 5.1.0, nRF5 SDK 14.2.0) and simple ble_app_ blinky_c example. And it doesn't matter what value set for CLOCK_CONFIG_LF_SRC parameter.

RE: Unable to enable the softdevice on custom board.

Petter Myhre — Tue, 14 Nov 2017 15:14:31 GMT

You didn't really answer my other questions. What if you set CLOCK_CONFIG_LF_SRC 0? Does that help?

RE: Unable to enable the softdevice on custom board.

Sourabh — Tue, 14 Nov 2017 14:36:27 GMT

Yes the code is working fine on the nRF52 DK.

RE: Unable to enable the softdevice on custom board.

Petter Myhre — Tue, 14 Nov 2017 13:15:03 GMT

Does the code work on the nRF52 DK?

RE: Unable to enable the softdevice on custom board.

Petter Myhre — Tue, 14 Nov 2017 13:13:23 GMT

The module should include a 32MHz crystal, are you talking about the 32kHz crystal? The 32kHz crystal is not mandatory, the 32MHz crystal is mandatory.

RE: Unable to enable the softdevice on custom board.

Sourabh — Tue, 14 Nov 2017 06:42:00 GMT

APP_ERROR_CHECK() is not called. We do not have a external 32MHz crystal, is it mandatory. But according to the , nRF52 PCB guidelines it states that the 32MHz crystal is mandatory. Could this be the issue?

RE: Unable to enable the softdevice on custom board.

Petter Myhre — Wed, 08 Nov 2017 15:31:27 GMT

What do mean by stuck? Where exactly are you stuck? Are you sure that APP_ERROR_CHECK() isn't called with an error somewhere? That would cause a reset. See this for more information.