RTC every second generates TIMER COUNT through PPI

RE: RTC every second generates TIMER COUNT through PPI

Chocol8 — Fri, 30 Mar 2018 14:58:35 GMT

Thanks for pointing out details. I totaly agree with you that it is waste of energy if being used this method in while(1) loop. I was not specific about how I finished up my situation. I just mentioned that I could not see any Increasement in CC register because I used power_manage(); function in the same while(1) loop. At the moment I use GPIOTE event on button push to read the time.

Anyway, thanks for replying.

Cheers!

RE: RTC every second generates TIMER COUNT through PPI

AmbystomaLabs — Fri, 30 Mar 2018 14:54:32 GMT

There is no reason to do anything in main. That would just be a waste of power.

The point of ppi/gpiote is that tasks and task end points can be tied together as you wish. You don't need interrupt handlers and you certainly don't need to poll registers in main.

You should read up on ppi/gpiote. There are many, many examples in the devzone also I think Nordic now includes a calendar function that does precisely what you are looking for in the current SDK.

RE: RTC every second generates TIMER COUNT through PPI

Chocol8 — Fri, 30 Mar 2018 11:52:55 GMT

Found the cause. TIMER COUNT register can be reached using this:

NRF_TIMER2->TASKS_CAPTURE[2] = 1;  // This is asking to capture the current counter into CC[2]
TIMER_COUNTER = NRF_TIMER1->CC[2];   // counter value  at the instant when capture task was triggered is now ready to be read in CC[2]

this was not capturing in my main function while(1) because I was using power_manage(); which somehow blocked capturing.