Timer Disturb Main Loop

RE: Timer Disturb Main Loop

Sagisawa Yukichi — Wed, 13 Sep 2017 01:30:07 GMT

Thank you so much:)! I did not know the setting!

RE: Timer Disturb Main Loop

MartinBL — Tue, 12 Sep 2017 11:33:43 GMT

Just somewhere before you start your timers.

RE: Timer Disturb Main Loop

Sagisawa Yukichi — Tue, 12 Sep 2017 01:36:49 GMT

Thanks your comment! Where your code should I write?

RE: Timer Disturb Main Loop

MartinBL — Mon, 11 Sep 2017 11:25:03 GMT

The app_timer library uses RTC1 as a timer and the Low Frequency 32.768kHz clock as the clock source. However, app_timer doesn't start the LF clock so this has to be done by you. A simple way to do it is like this:

NRF_CLOCK->TASKS_LFCLKSTART = 1;
while(NRF_CLOCK->EVENTS_LFCLKSTARTED != 1)
{
    ;
}

RE: Timer Disturb Main Loop

Sagisawa Yukichi — Fri, 08 Sep 2017 09:48:14 GMT

I attached my code at top of this question.

RE: Timer Disturb Main Loop

Sagisawa Yukichi — Fri, 08 Sep 2017 09:27:50 GMT

I think so, too. I added printf("ul_pasttime++"); in timer_timeout_handler（void * p_context).

RE: Timer Disturb Main Loop

MartinBL — Fri, 08 Sep 2017 09:15:21 GMT

Strange. The app_timer code looks good. How do you know that the handler is never called? Did you put a breakpoint in it?

By the way, ul_pasttime should be declared volatile. Otherwise it might not behave as you would expect when you use it in an interrupt.

RE: Timer Disturb Main Loop

Sagisawa Yukichi — Fri, 08 Sep 2017 09:02:18 GMT

Thanks your comment, I debugged, There was an error at function of device_init (I abridgemed). The problem of disturb is solved. But another problem happened. This code never call timer_timeout_handler(void * p_context). Please tell me how to rewrite this code correctly.

RE: Timer Disturb Main Loop

MartinBL — Thu, 07 Sep 2017 15:05:01 GMT

Have you tried debugging your code to pinpoint what piece of code causes your chip to reset?