Using app timer in sdk13

RE: Using app timer in sdk13

Tostikoning — Fri, 21 Apr 2017 10:19:03 GMT

With help from @Sigurd I managed to find the problem. It was a problem all programmers will experience in their careers and one of my finest "d'oh" moments.

You should create the timer with the following function:

ret_code_t app_timer_create(app_timer_id_t const *      p_timer_id,
                            app_timer_mode_t            mode,
                            app_timer_timeout_handler_t timeout_handler)

And start the timer with the following function:

ret_code_t app_timer_start(app_timer_id_t timer_id, uint32_t timeout_ticks, void * p_context)

Notice the difference in the first argument. The init requires an address of your timer id, and when you start a timer it only needs a copy. So when I changed my call from:

err_code = app_timer_start(&m_pt100_timer_id, APP_TIMER_TICKS(1000), NULL);

err_code = app_timer_start(m_pt100_timer_id, APP_TIMER_TICKS(1000), NULL);

It worked like a charm! Oh and btw, do not try to debug after the softdevice was enabled, it can get quirky.

RE: Using app timer in sdk13

Tostikoning — Fri, 21 Apr 2017 09:42:34 GMT

Okay, this helped me. Not in an expected way. I missed a reset. i put a breakpoint in the measurement start function. No error code is returned but i can see it resetting. I'll try to investigate this further.

EDIT 1: Strange things are happening. I also placed a breakpoint in the RTC1_IRQHandler in app_timer.c . Another breakpoint is in measurement_start() just after

err_code = app_timer_start(m_pt100_timer_id, APP_TIMER_TICKS(5000), NULL);

btw app_timer_start does not like to get a address of the timer id, but would rather like a copy.

ret_code_t app_timer_start(app_timer_id_t timer_id, uint32_t timeout_ticks, void * p_context);

This change allows me to enter the RTC1_IRQHandler() however I still do not enter my own handler and it still resets.

Also it only enters the RTC1_IRQhandler if I wait a a few seconds, if I just continue it resets without entering the RTC1_IRQHandler(). I will continue..

EDIT 2: If I change the timeout value from 5s to 100ms it fires RTC1_IRQHandler a few times before restting. Is something else resetting my program? Further investigation.. EDIT 3: I fixed it. I will update the question with an answer. The reset was probably induced by adding the breakpoints, after the SD was enabled.

RE: Using app timer in sdk13

Sigurd — Fri, 21 Apr 2017 09:39:03 GMT

What does app_timer_start(m_pt100_timer_id, APP_TIMER_TICKS(100), NULL); return? Try do send the err_code to the error handler:

void measurement_start(void)
{
    ret_code_t err_code;
    /* Start timer */
    err_code = app_timer_start(&m_pt100_timer_id, MEAS_TIMER_INTERVAL, NULL);
    APP_ERROR_CHECK(err_code);

    /* Clear previous measurement in flash */

}

RE: Using app timer in sdk13

Tostikoning — Fri, 21 Apr 2017 09:34:18 GMT

Yeah, I mean I can connect to my application and read all my data. I use a LED blinking from main, just to detect if no error has occured or if it is stuck. It keeps blinking. A different LED is toggled in the handler, which does not blink, even when I set it to 1s instead of 100ms. In the debugger I do not enter the handler. Should I use the wait for event functions? Are those mandatory for the intterupt to fire? Also I do not use the scheduler.

RE: Using app timer in sdk13

Sigurd — Fri, 21 Apr 2017 09:25:53 GMT

The rest of the application is working fine? The only problem is that the timeout is not fired?

Have you tried debugging the application? Are you running into the error handler somewhere? See this post on how to debug.

RE: Using app timer in sdk13

Tostikoning — Fri, 21 Apr 2017 09:20:10 GMT

Hi Sigurd,

I tried the change you suggested in A4. Unfortunately it did not work. The following snippet is from the sdk_config.h:

    // <e> APP_TIMER_ENABLED - app_timer - Application timer functionality
//==========================================================
#ifndef APP_TIMER_ENABLED
#define APP_TIMER_ENABLED 1
#endif
#if  APP_TIMER_ENABLED
// <o> APP_TIMER_CONFIG_RTC_FREQUENCY  - Configure RTC prescaler.

// <0=> 32768 Hz
// <1=> 16384 Hz
// <3=> 8192 Hz
// <7=> 4096 Hz
// <15=> 2048 Hz
// <31=> 1024 Hz

#ifndef APP_TIMER_CONFIG_RTC_FREQUENCY
#define APP_TIMER_CONFIG_RTC_FREQUENCY 0
#endif

// <o> APP_TIMER_CONFIG_IRQ_PRIORITY  - Interrupt priority


// <i> Priorities 0,2 (nRF51) and 0,1,4,5 (nRF52) are reserved for SoftDevice
// <0=> 0 (highest)
// <1=> 1
// <2=> 2
// <3=> 3
// <4=> 4
// <5=> 5
// <6=> 6
// <7=> 7

#ifndef APP_TIMER_CONFIG_IRQ_PRIORITY
#define APP_TIMER_CONFIG_IRQ_PRIORITY 7
#endif

// <o> APP_TIMER_CONFIG_OP_QUEUE_SIZE - Capacity of timer requests queue.
// <i> Size of the queue depends on how many timers are used
// <i> in the system, how often timers are started and overall
// <i> system latency. If queue size is too small app_timer calls
// <i> will fail.

#ifndef APP_TIMER_CONFIG_OP_QUEUE_SIZE
#define APP_TIMER_CONFIG_OP_QUEUE_SIZE 10
#endif

// <q> APP_TIMER_CONFIG_USE_SCHEDULER  - Enable scheduling app_timer events to app_scheduler


#ifndef APP_TIMER_CONFIG_USE_SCHEDULER
#define APP_TIMER_CONFIG_USE_SCHEDULER 0
#endif

// <q> APP_TIMER_WITH_PROFILER  - Enable app_timer profiling
 

#ifndef APP_TIMER_WITH_PROFILER
#define APP_TIMER_WITH_PROFILER 0
#endif

// <q> APP_TIMER_KEEPS_RTC_ACTIVE  - Enable RTC always on
 

// <i> If option is enabled RTC is kept running even if there is no active timers.
// <i> This option can be used when app_timer is used for timestamping.

#ifndef APP_TIMER_KEEPS_RTC_ACTIVE
#define APP_TIMER_KEEPS_RTC_ACTIVE 0
#endif

// <o> APP_TIMER_CONFIG_SWI_NUMBER  - Configure SWI instance used.

// <0=> 0
// <1=> 1

#ifndef APP_TIMER_CONFIG_SWI_NUMBER
#define APP_TIMER_CONFIG_SWI_NUMBER 0
#endif

#endif //APP_TIMER_ENABLED
// </e>

Do you have any other suggestions?

RE: Using app timer in sdk13

Sigurd — Fri, 21 Apr 2017 09:13:30 GMT

Hi,

Q1: Does app_timer module enable RTC1 or do I need to enable it?

A1: The app_timer module enable RTC1 in the function app_timer_init()

Q2:Do I need to initialize the LF clk?

A2:If you are using the SoftDevice, the LFCLCK gets initialized and enabled when you enable the SoftDevice.

Q3:Should I first enable the softdevice and then the timer, or the other way around?

A3: You can do both, but you won't get any timeout before the LFCLK is started.

Q4:Do you guys know why my timeout is not fired?

A4: Try to change app_timer_start(&m_pt100_timer_id, MEAS_TIMER_INTERVAL, NULL); with app_timer_start(m_pt100_timer_id, APP_TIMER_TICKS(100), NULL);