BLE stack initialization stucks

RE: BLE stack initialization stucks

Vidar Berg — Wed, 04 Nov 2020 11:20:13 GMT

Thanks, I will follow up in the other ticket you created. It appears to be a different error now.

RE: BLE stack initialization stucks

Kampino — Wed, 04 Nov 2020 11:16:03 GMT

It seems that the error comes from my PPI and timer initialization. Anyway, I have opened a private ticket, so you can debug my project.

RE: BLE stack initialization stucks

Kampino — Wed, 04 Nov 2020 10:41:54 GMT

Yes I can to it. Let me check how I can achieve this.

RE: BLE stack initialization stucks

Vidar Berg — Wed, 04 Nov 2020 10:29:05 GMT

Suprised you still get the same error after removing initialization of the other peripherals. Are you able to share your project here or in a private support ticket so I can try debug it?

RE: BLE stack initialization stucks

Kampino — Wed, 04 Nov 2020 10:11:03 GMT

mmh I don´t see any invalid interrupt priorities. I use the default configuration for each device and even when I comment out the initialization of all other peripherals the error still exist.

RE: BLE stack initialization stucks

Vidar Berg — Wed, 04 Nov 2020 09:39:47 GMT

It's defined in nrf_error_sdm.h:

#define NRF_ERROR_SDM_INCORRECT_INTERRUPT_CONFIGURATION (NRF_ERROR_SDM_BASE_NUM + 1)  ///< Incorrect interrupt configuration (can be caused by using illegal priority levels, or having enabled SoftDevice interrupts).

RE: BLE stack initialization stucks

Kampino — Wed, 04 Nov 2020 09:37:53 GMT

Hello,

why do you think it is the error NRF_ERROR_SDM_INCORRECT_INTERRUPT_CONFIGURATION? When I take a look at "nrf_error.h" I get the base "NRF_ERROR_SDM_BASE_NUM" and the error "NRF_ERROR_SVC_HANDLER_MISSING".
Do I understand it wrong?

RE: BLE stack initialization stucks

Vidar Berg — Wed, 04 Nov 2020 09:09:35 GMT

Hello,

Error 4097=0x1001 corresponds to NRF_ERROR_SDM_INCORRECT_INTERRUPT_CONFIGURATION and will be returned from sd_softdevice_enable() if you have enabled an IRQ vector with one of the interrupt priorities reserved to the Softdevice (Interrupt priority levels). SDK examples usually use interrupt priority '6' for application interrutps.

RE: BLE stack initialization stucks

Kampino — Wed, 04 Nov 2020 08:32:03 GMT

Hello,

thank you for the help. The application doesn´t stuck anymore but will jump into the error handler(error 4097).

RE: BLE stack initialization stucks

Vidar Berg — Wed, 04 Nov 2020 07:41:58 GMT

Hello,

The application is supposed to run on top of the Softdevice as you can see from the memory layout here in the Softdevice specification: Memory resource map and usage. So you will need to change the linker settings of your app so it doesn't overlap with the Softdevice.

Relevant linker settings from BLE template example in SDK 17.0.2

And the setting to make Embedded Studio program the Softdevice toghether with the application image

RE: BLE stack initialization stucks

Kampino — Tue, 03 Nov 2020 18:46:21 GMT

Hello,

sorry I missed it again...
It is an nRF52 DK with no modifications. Please take a look at the screenshot. I hope it helps.

RE: BLE stack initialization stucks

Vidar Berg — Tue, 03 Nov 2020 14:14:46 GMT

Hello,

Ok, so it still hangs after you've changed the clock source? Is it a custom board or a nordic DK? Maybe you post a screenshot showing the CPU registers and disassembly when it hangs?

RE: BLE stack initialization stucks

Kampino — Tue, 03 Nov 2020 13:56:34 GMT

Hello,

yes a 32 kHz crystal is mounted and I update the config file according to your example.

RE: BLE stack initialization stucks

Vidar Berg — Tue, 03 Nov 2020 13:38:57 GMT

Hello,

It's almost always a problem with the clock source selection when the program hangs in sd_softdevice_enable(). Does your board have a 32KHz crystal mounted? If not, the p_clock_lf_cfg argument which specifies what clock source the Softdevice shall use must be set to use the LFRC.

sdk_config.h settings to use internal RC oscillator with periodic calibration:

//==========================================================

// <h> Clock - SoftDevice clock configuration

//==========================================================
// <o> NRF_SDH_CLOCK_LF_SRC  - SoftDevice clock source.
 
// <0=> NRF_CLOCK_LF_SRC_RC 
// <1=> NRF_CLOCK_LF_SRC_XTAL 
// <2=> NRF_CLOCK_LF_SRC_SYNTH 

#ifndef NRF_SDH_CLOCK_LF_SRC
#define NRF_SDH_CLOCK_LF_SRC 0
#endif

// <o> NRF_SDH_CLOCK_LF_RC_CTIV - SoftDevice calibration timer interval. 
#ifndef NRF_SDH_CLOCK_LF_RC_CTIV
#define NRF_SDH_CLOCK_LF_RC_CTIV 2
#endif

// <o> NRF_SDH_CLOCK_LF_RC_TEMP_CTIV - SoftDevice calibration timer interval under constant temperature. 
// <i> How often (in number of calibration intervals) the RC oscillator shall be calibrated
// <i>  if the temperature has not changed.

#ifndef NRF_SDH_CLOCK_LF_RC_TEMP_CTIV
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 16
#endif

// <o> NRF_SDH_CLOCK_LF_ACCURACY  - External clock accuracy used in the LL to compute timing.
 
// <0=> NRF_CLOCK_LF_ACCURACY_250_PPM 
// <1=> NRF_CLOCK_LF_ACCURACY_500_PPM 
// <2=> NRF_CLOCK_LF_ACCURACY_150_PPM 
// <3=> NRF_CLOCK_LF_ACCURACY_100_PPM 
// <4=> NRF_CLOCK_LF_ACCURACY_75_PPM 
// <5=> NRF_CLOCK_LF_ACCURACY_50_PPM 
// <6=> NRF_CLOCK_LF_ACCURACY_30_PPM 
// <7=> NRF_CLOCK_LF_ACCURACY_20_PPM 
// <8=> NRF_CLOCK_LF_ACCURACY_10_PPM 
// <9=> NRF_CLOCK_LF_ACCURACY_5_PPM 
// <10=> NRF_CLOCK_LF_ACCURACY_2_PPM 
// <11=> NRF_CLOCK_LF_ACCURACY_1_PPM 

#ifndef NRF_SDH_CLOCK_LF_ACCURACY
#define NRF_SDH_CLOCK_LF_ACCURACY 1
#endif

Best regards,

Vidar