nRF51: Timer Capture Task

RE: nRF51: Timer Capture Task

FormerMember — Fri, 25 Nov 2016 09:28:35 GMT

Good that you were able to make it work!

RE: nRF51: Timer Capture Task

mr91 — Fri, 25 Nov 2016 08:43:49 GMT

Got it. I found out, that Timer2/3 are only 16 Bit. After adjusting the reload value, everything seems to work fine :)

RE: nRF51: Timer Capture Task

mr91 — Fri, 25 Nov 2016 07:52:49 GMT

Think I found the problem (using the linked example above):

300 kHz -> Capture Value is 0x919B (37,2 kHz). I found out, that 0x4919B would match the frequency (299419 Hz).

Question: Why is Timer2 (used as counter) only delivering 16-Bit CC-values, despite it is initialized in 32 Bit-Mode:

NRF_TIMER2->BITMODE = (TIMER_BITMODE_BITMODE_32Bit << TIMER_BITMODE_BITMODE_Pos);

RE: nRF51: Timer Capture Task

mr91 — Fri, 25 Nov 2016 07:22:03 GMT

Thank you for your answer. It works both ways. However, I have encountered another problem. I can measure frequencies only up to 60 kHz with this method. I also tried another approach: devzone.nordicsemi.com/.../ but with exactly the same result. Everything is ok when the frequency is under 60 kHz (e.g. 50 kHz is measured as 49992 Hz), but the result is totally wrong above (70 kHz is measured as 4330 Hz).

Is there a maximum frequency the GPIOTE/PPI-combination can handle? The maximum frequency I want to measure is about 300 kHz.

Thank you very much in advance!

RE: nRF51: Timer Capture Task

FormerMember — Wed, 23 Nov 2016 12:24:09 GMT

Unfortunately, there is no event when the capture is finished, so I would think that it will be executed immediately. If you are not using the softdevice, the GPIOTE event can be set to have the highest priority, and you know that you won't have any other interrupt.

You can check if the following will work:

GPIOTE event --> PPI --> TASKS_CAPTURE
GPIOTE event handler: clear timer, then read the CC register.

If the above doesn't work, i.e the capture has not finished before clearing the timer, you can test the following:

GPIOTE event --> PPI --> TASKS_CAPTURE
GPIOTE event handler: dummy read CC values, clear timer, then read the CC register.

Even though the capture/clear timing may be a little delayed, this delay will always be the same, so it should be possible to measure the frequency.

RE: nRF51: Timer Capture Task

mr91 — Mon, 21 Nov 2016 10:09:00 GMT

Thank you very much for your support. In order to get that working accurately, it seems necessary to clear the timer immediately after the capture is done. Is the timer generating an interrupt after finishing the capture?

RE: nRF51: Timer Capture Task

FormerMember — Mon, 21 Nov 2016 10:01:27 GMT

There is no specific ideal place to copy the content of the CC register, typically, the content in the CC register can be copied to a variable, a data array should work fine.

The benefit of using PPI instead of normal GPIO interrupt handling is that when using PPI, the CPU is not being used:

The Programmable Peripheral Interconnect (PPI) enables different peripherals to interact autonomously with each other using tasks and events without use of the CPU. The PPI provides a mechanism to automatically trigger a task in one peripheral as a result of an event occurring in another. A task is connected to an event through a PPI channel.

(nRF51 series reference manual chapter 3.3.4)

Clearing timer as soon as the capture is done:

Capture value (will be copied to the CC register).
Clear timer
Read captured value from the CC register.

This should work as long as every reading of captured values is finished before the next captured value.