This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

App will not run on target when LFCLK is not present

SDK14.2.0 sd132v5.0.0 nRF52832

I've looked for a solution to my issue on the discussion forum, but can't find an answer. I am working with the buttonless DFU peripheral example. It works perfectly on my board when the LFCLK is running, but when I disconnect the LFCLK on my dev board (to match my custom product hardware) the App will not start. I've tried setting the LFCLK to both Synth and RC in the sdk_config.h file, and neither option makes any difference. My dev board has two dip switches that can isolate the LFCLK crystal, so it's easy to check with and without the clock. As soon as I turn the clock on, the App starts and runs normally.

Does anyone have any advice on what the problem might be? Hopefully we don't have to redesign our hardware to add a LFCLK crystal!!

Thanks

  • Please note that there is a change introduced in S132 v.5.0.0, from the migration document:

    RC Oscillator accuracy
    The RC oscillator accuracy can now be set to any of the defined NRF_CLOCK_LF_ACCURACY values and there is no default value anymore.
    In other words, the nrf_clock_lf_cfg_t::accuracy parameter now has the same functionality when used with the RCOSC clock
    source as with the XTAL clock source. The RC oscillator accuracy should be set to a value appropriate for the chip.

    I.e., make sure that you use #define NRF_SDH_CLOCK_LF_XTAL_ACCURACY 1, when using the LFRC.

Related