Problem between soft device handler and clock driver.

[Vincent Belaïche]

Hello,

I am starting a new thread concerning the two messages that I have posted about generating a 4MHz clock on nRF52832. I am using the nRF5_SDK_14.2.0_17b948a SDK.

See :

• https://devzone.nordicsemi.com/f/nordic-q-a/12177/nrf52-clock-in-and-out/120302#120302
• https://devzone.nordicsemi.com/f/nordic-q-a/12177/nrf52-clock-in-and-out/120292#120292

[MartinBL]

Hi,

I think that your answer may be found in the comment I just posted here: ble with timer.

Try using sd_clock_hfclk_request() instead of nrf_drv_clock_hfclk_request().Can you check that out?

[Vincent Belaïche]

Hello Martin,
Thank-you for your answer. Functions sd_clock_hfclk_request and nrf_drv_clock_hfclk_request do not have the same prototype. The former takes no argument, so I presume that when the hfclk is not ready then the function will not return until it is ready. Could you please confirm that this is its behaviour?
The latter takes one argument which is a handler to be called immediately when the hfclk is ready, or later on when the hfclk has become ready.

[MartinBL]

Hi,

Actually, sd_clock_hfclk_request () will not wait until the clock has started. If you need confirmation when the clock has started you can register a Softdevice Handler Observer listening for SoC events: SoftDevice Handler library. Then the stack will send you an NRF_EVT_HFCLKSTARTED event when the clock has started. So you can still get a callback when the clock is ready, you will just have to take a different road to Rome.