Issue with TIMER in soft device S132

RE: Issue with TIMER in soft device S132

GK — Mon, 03 Sep 2018 04:41:53 GMT

Hi, Currently I am trying to do the same with app_timer.Thank you for your suggestion

RE: Issue with TIMER in soft device S132

Jørgen Holmefjord — Fri, 31 Aug 2018 12:42:57 GMT

If the timeout handler is called 20-30 times per second there is definitely something wrong. Can you check the value of time_ticks passed to nrf_drv_timer_extended_compare? Yes, if the config is set to 0, the timer should run at 16 MHz.

I would still recommend that you look into using app_timer for controlling your application. You can find a tutorial here. Plese note that there are some changes in newer SDKs.

RE: Issue with TIMER in soft device S132

GK — Fri, 31 Aug 2018 08:15:52 GMT

Yes..I have modified and forgot to revert it. Sorry for that.But it is not coming for every 10 seconds also.It is too fast .

Here the define statement is as follows

#define TIMER_DEFAULT_CONFIG_FREQUENCY 0. I think it is set to ' NRF_TIMER_FREQ_16MHz'.right?

RE: Issue with TIMER in soft device S132

Jørgen Holmefjord — Fri, 31 Aug 2018 07:30:10 GMT

If you run a timer at highest frequency (16 MHz), the timer will overflow after ~4.47 minutes. What have you set the frequency (TIMER_DEFAULT_CONFIG_FREQUENCY) to in your sdk_config.h file? It also looks like you set time_ms to 10 seconds in your code, not 1 minute as you claim.

RE: Issue with TIMER in soft device S132

GK — Thu, 30 Aug 2018 15:50:07 GMT

Dear Jørgen Holmefjord

Thank you very much for your reply.

I am using SDK version 15.0.0_a53641a. Currently the time out handler is calling around 20 -30 times per second(it (the print statement) goes too fast so exact value I could not get ).The timer I want to use for 5 minute. Just for checking I used the value 1 minute. Actually I want to wake up the system every 5 minute and start advertising for say 1 minute. Then go to sleep. Again after 5 minute start advertising...go on like this. So I am planning to call advertiing_start() function inside the handler, so that it will get called every 5 minute.

I am copying the code( excluded the part not related to timer).

Please correct me if I am wrong somewhere.

#include <stdbool.h>
#include <stdint.h>
#include "nrf.h"
#include "nrf_drv_timer.h"
#include "bsp.h"
#include "app_error.h"

const nrf_drv_timer_t TIMER_LED = NRF_DRV_TIMER_INSTANCE(1);

.......(some functions are there)

void timer_led_event_handler(nrf_timer_event_t event_type, void* p_context)
{
static uint32_t i;
uint32_t led_to_invert = 2;//((i++) % LEDS_NUMBER);

switch (event_type)
{
case NRF_TIMER_EVENT_COMPARE1:
NRF_LOG_INFO("Inside handler");
break;

default:
//Do nothing.
break;
}
}

............................

...............................

int main(void)
{

bool erase_bonds;

uint32_t time_ms = 1000*10; //Time(in miliseconds) between consecutive compare events.//GK added
uint32_t err_code = NRF_SUCCESS;//GK added
uint32_t time_ticks; //GK added

// Initialize.
log_init();
timers_init();
leds_init(&erase_bonds);//GK modified
power_management_init();
ble_stack_init();
gap_params_init();
gatt_init();
advertising_init();
services_init();
conn_params_init();
peer_manager_init();

// Start execution.
NRF_LOG_INFO("Sieva example started.");

application_timers_start();

advertising_start(erase_bonds);

nrf_drv_timer_config_t timer_cfg = NRF_DRV_TIMER_DEFAULT_CONFIG;//GK added for timer
err_code = nrf_drv_timer_init(&TIMER_LED, &timer_cfg, timer_led_event_handler);//GK added for timer
APP_ERROR_CHECK(err_code);//GK added for timer

time_ticks = nrf_drv_timer_ms_to_ticks(&TIMER_LED, time_ms); //GK added for timer

nrf_drv_timer_extended_compare(
&TIMER_LED, NRF_TIMER_CC_CHANNEL1, time_ticks, NRF_TIMER_SHORT_COMPARE1_CLEAR_MASK, true);//GK added for timer

nrf_drv_timer_enable(&TIMER_LED);//GK added for timer

// Enter main loop.
for (;;)
{
idle_state_handle();
}
}

RE: Issue with TIMER in soft device S132

Nguyen Hoan Hoang — Thu, 30 Aug 2018 13:18:09 GMT

yes, you are right. I was thinking about RTC timer. The High Freq timer is mostly use for the radio and the RTC is mostly used as app timer. That is what I was thinking about.

RE: Issue with TIMER in soft device S132

Jørgen Holmefjord — Thu, 30 Aug 2018 13:05:36 GMT

Nguyen Hoan Hoang: TIMER1 is not used by the softdevice or SDK. Application timer library use RTC1 as its timer source.

GK: How did you configure the timer? How often is the timeout handler called? Which SDK version are you using? I would not recommend using a timer for 1 minute intervals, app_timer or RTC would be a better alternative, as it runs on lower frequency clock source, giving you lower accuracy but also much lower current consumption.

RE: Issue with TIMER in soft device S132

Nguyen Hoan Hoang — Thu, 30 Aug 2018 12:29:26 GMT

timer0 & 1 are used by softdevice and SDK. 2 way to use timer with softdevice.

1) use app_timer (timer1)

2) use timer2