Application Timer RTC1 with Critical sections

RE: Application Timer RTC1 with Critical sections

Hung Bui — Tue, 25 Oct 2022 14:49:45 GMT

Ok, I see what you meant.
You can call NRFX_IRQ_DISABLE(RTC1_IRQn) to disable the interrupt from IRQ1.

However, I don't think it's a good idea since it may mess up the compare event handling. As you can see in the IRQ handler:

Not having the CC counter handling correctly the app_timer may not work correctly after you enable the RTC1 interrupt again.
Have you considered using the app timer with the scheduler ? The RTC interrupt may still come but the timeout handler will come on main context.
Another option is to consider put the RTC interrupt at lower priority than the code you plan to execute.

RE: Application Timer RTC1 with Critical sections

Schmale — Tue, 25 Oct 2022 13:58:48 GMT

Hi Hung,

no worries, first of all the Application Timer is running fine.

I dont want to go into detail, since this would not help at all, instead let me reframe my question.

Is there a possibilty to disable/mask out the RTC1-timer Interrupt? Just the RTC1-Timer, since I dont want to disable the global interrupts.

I know that i can "Pause" and "Resume" the application timer via the API, but this would result in a shift of the timebase, which I would like to avoid.

RE: Application Timer RTC1 with Critical sections

Hung Bui — Wed, 19 Oct 2022 12:59:05 GMT

Hi Jan,
I'm sorry that I don't fully understand your set up.
Could you explain why you want to

Is there a possibilty to enable/disable the interrupt source of the Application Timer (RTC1)?

What exactly is your challenge with the timer ?