Using P0.26 with App Timer

RE: Using P0.26 with App Timer

phipi — Wed, 04 Oct 2017 13:08:33 GMT

That's what I was missing, thanks!

RE: Using P0.26 with App Timer

Jørn — Wed, 04 Oct 2017 12:16:09 GMT

When using the LFCLK driver the clock source is defined in sdk_config.h with the CLOCK_CONFIG_LF_SRC define. This is used as argument in the nrf_clock_lf_src_set function call, line 197 of nrf_drv_clock.c. Have you tried setting the define in sdk_config.h to 0 (RC source)?

RE: Using P0.26 with App Timer

phipi — Tue, 03 Oct 2017 21:40:16 GMT

I'm not using the softdevice. I was able to work around by using this:

  NRF_CLOCK->LFCLKSRC = (CLOCK_LFCLKSRC_SRC_RC << CLOCK_LFCLKSRC_SRC_Pos);
  NRF_CLOCK->EVENTS_LFCLKSTARTED = 0;
  NRF_CLOCK->TASKS_LFCLKSTART = 1;

  // Wait for the low frequency clock to start
  while (NRF_CLOCK->EVENTS_LFCLKSTARTED == 0) {}
  NRF_CLOCK->EVENTS_LFCLKSTARTED = 0;

instead of nrf_drv_clock_lfclk_is_running(). Does that make sense?

RE: Using P0.26 with App Timer

RK — Tue, 03 Oct 2017 21:17:05 GMT

You pick the LF clock source when you start the softdevice. If you don't have a softdevice then you start the LF clock source yourself and choose it then, so there isn't a parameter in the timer library and there doesn't need to be, it just uses the LF clock source you already started.

RE: Using P0.26 with App Timer

phipi — Tue, 03 Oct 2017 21:14:10 GMT

"Function for requesting LFCLK. LFCLK can be repeatedly requested.

If it is first request, selected LFCLK source will be started. The nrf_drv_clock_lfclk_is_running() function can be polled to check if it has started."

Any thoughts on what "requesting LFCLK" means exactly? Is this equivalent to enabling it?

Also, how do we specify "selected LFCLK source"?

RE: Using P0.26 with App Timer

RK — Tue, 03 Oct 2017 21:13:23 GMT

No you do not - so you have a different issue