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

working with s132 and app_timer but timing is not always good

hello Nordic 

i am working with nrf52832, sdk 16.0 s132

1. i see when i use the app_time i have to initialize it using this line of code :

static void lfclk_request(void)
{
    ret_code_t err_code = nrf_drv_clock_init();
    APP_ERROR_CHECK(err_code);
    nrf_drv_clock_lfclk_request(NULL);
}

though i thought and read that the softdevice activates the LFCLK

so why do i need to use this lines of code (if i don't then the timer does not work and the handler is not called ), why is that ?

2. when i use the handler just to toggle a led each second APP_TIMER_TICKS(1000) i see that when ble scan is not working the timing looks like one second but when i use the code with the ble scan the blinking is not right it blinks but week and not in intervals of 1 second, why is that ? 

3. how can i set scan to scan all the time, like its interval is = 0 ? i use the central app_ble_blinky example and i could not find yet what veritable controls this ?

best regards

Ziv

Parents Reply Children
No Data
Related