nRF52 LF crystal initialization best practices

RE: nRF52 LF crystal initialization best practices

run_ar — Thu, 05 Jul 2018 13:36:50 GMT

1) The SD will start the LF clock. Either the RC or the crystal depending on configuration.

2.1) yes.

2.2) It think it will continue to run from RC. So you should start the crystal first.

RE: nRF52 LF crystal initialization best practices

Valerii_Ie — Thu, 05 Jul 2018 13:03:02 GMT

Thanks run_ar,

1) According to the code

bool nrf_drv_clock_lfclk_is_running(void)
{
    ASSERT(m_clock_cb.module_initialized);

#ifdef SOFTDEVICE_PRESENT
    if (nrf_sdh_is_enabled())
    {
        return true;
    }
#endif // SOFTDEVICE_PRESENT

    return nrfx_clock_lfclk_is_running();
}

I suggest that if I receive NRF_SDH_EVT_STATE_ENABLED event after calling nrf_sdh_enable_request() the LF clock have to be enabled. So if I use softdevice I do not need to init LF clock manually. Does it make sense?

2) If I start LF clock (on crystal source) before starting WDT, the last will use crystal as a clock source?

2') If I start WDT before starting softdevice with NRF_SDH_CLOCK_LF_SRC == 1 (XTAL). Will WDT stay on RC clock source or switch to XTAL clock?

3)clear

thanks!

RE: nRF52 LF crystal initialization best practices

run_ar — Thu, 05 Jul 2018 11:39:51 GMT

1) you can add a while(nrf_drv_clock_lfclk_is_running()); after the request. This will make sure the app is not proceeding unless you are able to start the LF crystal.

2)According to documentation: When started, the watchdog will automatically force the 32.768 kHz RC oscillator on as long as no other 32.768 kHz clock source is running and generating the 32.768 kHz system clock, see chapter CLOCK — Clock control.

3) Yes. Not sure which sdk version you are using ,but you do not want to rely in the bootloader to do initialization for the application.