timestamping w/o active timer (APP_TIMER_KEEPS_RTC_ACTIVE = 1)

RE: timestamping w/o active timer (APP_TIMER_KEEPS_RTC_ACTIVE = 1)

martin — Fri, 18 Aug 2017 15:04:31 GMT

APP_TIMER_KEEPS_RTC_ACTIVE won't work but this fixed it for me.

RE: timestamping w/o active timer (APP_TIMER_KEEPS_RTC_ACTIVE = 1)

martin — Fri, 18 Aug 2017 15:03:41 GMT

i guess i could - for now i switched to the soft-device, the app_timer is working nicely and provides some "comfort functions"i'd have to implement on top. i also created a new project and adding the call to rtc1_start () worked there - so i guess i made a mess somewhere.

RE: timestamping w/o active timer (APP_TIMER_KEEPS_RTC_ACTIVE = 1)

Hung Bui — Thu, 03 Aug 2017 10:21:54 GMT

Hi martin,

What about using the RTC directly and skip the apptimer ?

Hung

RE: timestamping w/o active timer (APP_TIMER_KEEPS_RTC_ACTIVE = 1)

martin — Tue, 01 Aug 2017 06:51:08 GMT

hello - i tried the attached project. you still have the start_app_timer () in there - thus a dummy-timer will be initialized and everything works. once you remove this line your output should also stall. tried it with UART as well as J-Link (using ozone).

to summarize: when i remove the start_app_timer() line plus add the rtc1_start() in app_timer_init i get ~2 prints of the RTC, then everything stops working. only if i break and resume the rtc_t0 gets updated.

RE: timestamping w/o active timer (APP_TIMER_KEEPS_RTC_ACTIVE = 1)

Jørgen Holmefjord — Fri, 28 Jul 2017 09:12:41 GMT

How do you check the variable? I tested your code and it seems to work fine. Attachecd project for SDK 13.1.0 (only Keil project and hex-files updated): app_timer.zip. Can you test this on your board? It will output value to UART.

RE: timestamping w/o active timer (APP_TIMER_KEEPS_RTC_ACTIVE = 1)

martin — Wed, 26 Jul 2017 16:42:17 GMT

thanks for the quick reply! that seems to do something but does not produce the expected outcome. somehow i can only see that a new value (e.g., rtc_t0) is only generated once i break ... so it behaves quite differently. or is there something else i'm missing?

RE: timestamping w/o active timer (APP_TIMER_KEEPS_RTC_ACTIVE = 1)

Jørgen Holmefjord — Wed, 26 Jul 2017 09:22:40 GMT

rtc1_start() will not be called in app_timer before a timer is created. You can bypass this by adding a call to rtc1_start() at the end of app_timer_init().