Nrfx timer capturing/comparing

RE: Nrfx timer capturing/comparing

Sigurd — Thu, 05 Sep 2024 14:15:00 GMT

[quote user="trafficode"]Major question is: Why I read so bad values from channel 1 if it is not used to nothing more, and it looks like is reseted when channel 2 is captured...[/quote]

Looking at the code, you have e.g. this line:

nrfx_timer_extended_compare(&TimerInst, NRF_TIMER_CC_CHANNEL2, cc + us,
NRF_TIMER_SHORT_COMPARE2_CLEAR_MASK, true);

So you have a shortcut between the compare event on the channel and the timer CLEAR task

RE: Nrfx timer capturing/comparing

trafficode — Thu, 05 Sep 2024 06:54:35 GMT

Yeap

RE: Nrfx timer capturing/comparing

Sigurd — Wed, 04 Sep 2024 13:39:41 GMT

[quote user="trafficode"]One thing I forgot to mention is that I have it working with nRF Connect SDK 1.8, but I'm encountering problems while trying to migrate to the newest version.[/quote]

You are testing with NCS 2.7.0 ?

RE: Nrfx timer capturing/comparing

trafficode — Wed, 04 Sep 2024 13:15:34 GMT

You did this for a very old version of nrfx. One thing I forgot to mention is that I have it working with nRF Connect SDK 1.8, but I'm encountering problems while trying to migrate to the newest version. Previously I was using input capture to measure input pulse, this one I decided to start with something more simple.

Major question is: Why I read so bad values from channel 1 if it is not used to nothing more, and it looks like is reseted when channel 2 is captured...

RE: Nrfx timer capturing/comparing

Sigurd — Wed, 04 Sep 2024 12:23:32 GMT

Hi!

I implemented a "pulse detector" some years ago, it measures the time, and gives the frequency of the input signal. Maybe that can be useful in what you are trying to do: https://github.com/sigurdnev/ncs-playground/blob/master/samples/pulse_detector/src/main.c