My code is hanging in sd_softdevice_enable()

[AshokY]

Hi,

I designed my custom board with RF52832. I was able to detect my board using the debugger.

I am using the BLE mesh default "Light switch proxy server".

I could get the debug message " main.c,  310, ----- BLE Mesh Light Switch Proxy Server Demo -----" successfully.

I am not getting any further message. When I try to debug the code, it is getting into "sd_softdevice_enable()" and going to assembly code.

In assembly code it is looping in the following code.

BF20 wfe
F8D40104 ldr.w r0, [r4, #0x104]
2800 cmp r0, #0
D0FA beq 0x0000BAA2

Segger embedded studio is my toolchain.

I don't see this behavior when i use Nrf52 board. Can any one let me know where the problem is ?

Regards,

Ashok

[AmbystomaLabs]

Normally this is caused by not including the external RTC crystal in the new design.  All DKs have an external RTC crystal and the SD parameters in the examples are structured for it.  If this is true that your new board was designed to use internal RC RTC then change the SD parameters to RTC_RC.

[Vidar Berg]

Agree, this code is waiting for the external LFXO to start. See nrf_clock_lf_cfg_t for recommended LFRC configuration. Note that .accuracy must be set to 500 ppm when using the RC oscillator.

[AshokY]

Thanks for the support.

Currently I am going ahead without external RTC crystal.

Hence, I made changes in two places in my code.

1) #define NRF_SDH_CLOCK_LF_SRC 0               // <0=> NRF_CLOCK_LF_SRC_RC

2) #define NRF_SDH_CLOCK_LF_ACCURACY 1   // NRF_CLOCK_LF_ACCURACY_500_PPM

3) #define NRF_SDH_CLOCK_LF_RC_CTIV 16

4) #define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2

With these changes..my code is not stopping at the place I mentioned above, also working for my application.  Please correct me if any of my changes are wrong. Thanks for the support.

BTW, by not using the external RTC crystal, will there be any issues can any one anticipate in future?

Regards,

Ashok

[Vidar Berg]

Hi Ashok,

You are using the recommended settings for the RC oscillator so you should not encounter any problems related to the clock source and it's not required to use a LF crystal for BLE devices.