Timer handler called immediately on app_timer_start()

RE: Timer handler called immediately on app_timer_start()

HSA — Thu, 24 Sep 2015 06:15:43 GMT

Ok, I will check.

Please let me know, which "timeout_handler", I have to use...i mean, in which file, i hv to check for this handler..?

Thanks

RE: Timer handler called immediately on app_timer_start()

Dave_couling — Thu, 24 Sep 2015 06:12:51 GMT

There are many examples, both on the Github and in the SDK for this.

RE: Timer handler called immediately on app_timer_start()

HSA — Thu, 24 Sep 2015 05:36:41 GMT

Hello @Dave_couling,

you suggested:

[In that case I would use a REPEATING timer. In the timeout handler increment a global variable to track the number of times it has timed out. If you set the timer to 1sec timeout, then the counting variable in effect counts the seconds. In the button is released simply stop the timer].

sir, I am sorry, I am a newbie to this; could you please suggest some example code steps for this implementation~ please.

Thanks n Regards

RE: Timer handler called immediately on app_timer_start()

HSA — Thu, 24 Sep 2015 05:22:30 GMT

Hi @Dave_couling,

Thanks for your reply~

well,I am following [--nrf51-ble-app-lbs--] example. In this the button_detection_delay is using in a handler for short_button_push (1s) and I want to use the same handler for long_button_push (3s)........

static void button_event_handler(uint8_t pin_no, uint8_t button_action)

err_code = ble_lbs_on_button_change(&m_lbs, button_action);

Do I need to create new timer to handle the same handler again.

Please suggest~

Thanks n Regards

RE: Timer handler called immediately on app_timer_start()

Dave_couling — Thu, 24 Sep 2015 05:05:42 GMT

use an app_timer created as a APP_TIMER_MODE_SINGLE_SHOT

RE: Timer handler called immediately on app_timer_start()

HSA — Thu, 24 Sep 2015 04:46:29 GMT

Hi @Håkon Alseth

I want my timer to work only for one time; How can I implement that in code?

Please suggest.

Thanks n Regards

RE: Timer handler called immediately on app_timer_start()

Dave_couling — Fri, 28 Aug 2015 19:18:47 GMT

Hi Hakon, I will try this. Also note that as a general rule in my application I always stop an app_timer before starting it, to assure any timer is started fresh if already running. Could this increase the likelihood of this issue?

I have been able to recreate my issue but hard-coding rtc1_stop() and rtc_start() from app_timer.c in the Button_handler at a Button push. Normally a button push causes a button_timer to run to measure how long the button is held. At specific intervals of this timer I schedule events. After a specific amount of time the device is shutoff System_off via a scheduled event. However adding the above code causes an immediate shutdown and seems to crash/overflow the scheduler???

RE: Timer handler called immediately on app_timer_start()

Håkon Alseth — Fri, 28 Aug 2015 09:21:06 GMT

Hi Dave, This should have been fixed in the later version of the app_timer. Here's the link to our SDKs: developer.nordicsemi.com/.../

Could you try to use app_timer from a later SDK than v6 and see if the issue still occurs?

RE: Timer handler called immediately on app_timer_start()

Dave_couling — Fri, 28 Aug 2015 04:27:19 GMT

I have seen this bug in SDK 6.1. Has there been any progress on this issue?

Similar situation we have timer that works 99.99% of the time. However seemingly at random the handler will be called immediately rather than run for 8 seconds. Causing havoc for our application logic. We are also using the Scheduler for our app_timers

RE: Timer handler called immediately on app_timer_start()

Eliot Stock — Thu, 03 Jul 2014 21:46:45 GMT

No problem, I can leave the dummy handler in. Might be worth a docs change to mention it's required though.

RE: Timer handler called immediately on app_timer_start()

Håkon Alseth — Thu, 03 Jul 2014 07:38:20 GMT

Unfortunately, this is a side effect of the bug fixes in the last revisions. If we do not clear the COUNTER register in the case that one-shot timer is the only one running and this one times out, we stop the RTC and clear the COUNTER after this instance has timed out, as no other instances are using the app_timer library.

In order to use the COUNTER register for timestamping, you will have to have at least one app_timer instance always running.

RE: Timer handler called immediately on app_timer_start()

Eliot Stock — Wed, 02 Jul 2014 20:22:16 GMT

Hakon, I just upgraded to SDK 6.0.0 and this is still broken there. I still require the dummy handler in my code for app_timer_cnt_get() to work.

RE: Timer handler called immediately on app_timer_start()

Håkon Alseth — Mon, 16 Jun 2014 08:16:29 GMT

You'll need that dummy-handler. If its not registered with the app_timer library, it will stop the RTC when there's nothing running, resulting in a cleared COUNTER register.

RE: Timer handler called immediately on app_timer_start()

Eliot Stock — Thu, 12 Jun 2014 13:05:37 GMT

Will do. Do you want me to continue to use this dummy timer with the patched app_timer.c as a work around until the next SDK version ships?

RE: Timer handler called immediately on app_timer_start()

Håkon Alseth — Thu, 12 Jun 2014 13:00:00 GMT

Great to hear! I would change the dummy handlers app_timer_create(..., APP_TIMER_MODE_REPEATED, ...) to ensure that the NRF_RTC1->COUNTER register is never cleared.

RE: Timer handler called immediately on app_timer_start()

Eliot Stock — Thu, 12 Jun 2014 12:52:54 GMT

Have added a dummy timer, created and started after the Soft Device is enabled and never stopped, like so:

uint32_t err_code = app_timer_create(&m_empty_timeout_timer_id, APP_TIMER_MODE_SINGLE_SHOT, empty_timeout_handler);
	APP_ERROR_CHECK(err_code);

	// 0x00FFFFFF is MAX_RTC_COUNTER_VAL from app_timer.c
	uint32_t timeout = (0x00FFFFFF / 2);
	err_code = app_timer_start(m_empty_timeout_timer_id, timeout, NULL);
	APP_ERROR_CHECK(err_code);

And yes indeed, I no long see the problem when this app timer is running.

RE: Timer handler called immediately on app_timer_start()

Håkon Alseth — Thu, 12 Jun 2014 11:24:15 GMT

Sorry for the delay, Eliot. I had to get a hold of the developer of app_timer to understand the changes made. The issue you're seeing is due to a bugfix, where the counter is reset if it sees that no other app_timer instances are running.

If you add a dummy-timeout handler (empty handler) with a timeout of MAX_RTC / 2 (255 seconds if prescaler 0 set, see RM chapter 18 for calculation) do you still see the issue of the counter being reset?

RE: Timer handler called immediately on app_timer_start()

Eliot Stock — Mon, 09 Jun 2014 14:41:40 GMT

I spoke too soon. Although the patched app_timer.c fixes the issue I was seeing originally, it also breaks the implementation of app_timer_cnt_get() for me. That function is now returning a very low number of ticks (3) where it used to return the right value. This breaks all the timestamps in my log.

Do you want me to try this patched app_timer.c with the 5.2.0 SDK instead?

RE: Timer handler called immediately on app_timer_start()

Eliot Stock — Wed, 04 Jun 2014 18:03:34 GMT

That does indeed seem to have fixed the problem! My code's been running for 18 mins now without seeing the same behaviour.

I'm using SDK 5.1.0 though, not 5.2.0, just FYI. Not sure if the same problem exists in 5.2.0 but I'll stick with 5.1.0 plus this modified source until the next release I guess.

RE: Timer handler called immediately on app_timer_start()

Håkon Alseth — Wed, 04 Jun 2014 13:56:21 GMT

We've had a couple of known bugs regarding the app_timer in the latest release, which we are working on fixing. I have the app_timer source file that will be included in the next release of the nRF51 SDK. Could you try that?

-H

app_timer.c

RE: Timer handler called immediately on app_timer_start()

Eliot Stock — Fri, 30 May 2014 09:31:02 GMT

This is happening at 4 minutes and 18 seconds after reset, every time, like clockwork.