Crash in sd_clock_hfclk_is_running on Soft Device S140, 7.3.0

[jthlim]

Hi, I recently noticed crashing in sd_clock_hfclk_is_running() on a nrf52840 using SoftDevice S140 7.3.0. This is the callstack:

??@0x00000ac4 (Unknown Source:0)

<signal handler called>@0xffffffe9 (Unknown Source:0)

sd_clock_hfclk_is_running@0x000276ae (.../nRF5_SDK_17.1.0_ddde560/components/softdevice/s140/headers/nrf_soc.h:720)

I'm using the following to enable the hfclk whenever I enable QSPI to avoid errata 244:

sd_clock_hfclk_request();

uint32_t isHfclkRunning = 0;

do {

  APP_ERROR_CHECK(sd_clock_hfclk_is_running(&isHfclkRunning));

} while (!isHfclkRunning);

I can trigger this somewhat reliably if I unplug and plug usb power while this code triggers.

Any tips on how I can avoid this issue?

Thanks,

Jeff

[Priyanka]

Hi Jeff,

Are you using a custom board or the nRF2840DK?

Regards,

Priyanka

[jthlim]

I am using a Holyiot 18010 on a custom board

The code works reliably in the absence of power being toggled to the pin

[Priyanka]

Please make sure that the SoftDevice is properly initialized and also check the state of the softdevice when requesting the HFCLK. Ensure that the power management is properly handled during USB power plug/unplug events. Also, ensure that the HFCLK status is checked properly and avoid race conditions.

-Priyanka

[jthlim]

How can I check that these are all handled properly?

Everything works outside of USB plugging, and USB plugging works fine 19 times out of 20. Bluetooth works fine, USB power detection works fine. The soft device is always enabled right at startup.

The crashing call stack is inside sd_clock_hfclk_is_running. How can I tell if I'm checking it properly? The code for this is in the original post.