Stuck Timer Value always reading Zero!

RE: Stuck Timer Value always reading Zero!

Sigurd — Mon, 03 Jun 2019 14:51:24 GMT

What prescaler do you use for the timer ?

Are you using the projects found in this post?

RE: Stuck Timer Value always reading Zero!

AimHigh — Wed, 22 May 2019 18:47:29 GMT

Hi, Well LATCH_GPIOTE is integer declared as global and initialized to value 0. I am using it if(Latch_GPIOTE==0) then start the timer on LoToHi on PIN_IN2 and increment Latch_GPIOTE++, else if(Latch_GPIOTE==1) stop the timer and reset Latch_GPIOTE to 0. And this else If(Latch_GPIOTE==1) is executed on next LoToHi pulse on PIN_IN2.

I did try to read CC[0] reg somehow nothing came out. But eventually, I have added

if(pin==PIN_IN2)&&(action==NRF_GPIOTE_POLARITY_LOTOHI) this worked for it.

But got a new problem here. when I give 2microsecond pulse to PIN_IN2, the timer ticks value I am getting is 513 which is 32.0625 microseconds. Hence the scale is way off.

What could be the problem here? I have got the range to measure from 2us to 135us.

Here is the Output on debugging terminal for 2us pulse with 50% duty cycle.

time in us: 33.062500
Timer Ticks: 529
time in us: 33.187500
Timer Ticks: 531

RE: Stuck Timer Value always reading Zero!

Sigurd — Wed, 22 May 2019 18:19:01 GMT

Ok, the timer is started via PPI if "LATCH_GPIOTE" is set to 0, and you get a in event for PIN2. Where are you setting LATCH_GPIOTE ? and why do you need LATCH_GPIOTE ?

And the timer_compare_task_addr is using CC[2] register, but in the in_pin_handler() you are reading the CC[0] register. So try using NRF_TIMER_TASK_CAPTURE0 for the timer_compare_task_addr instead.

RE: Stuck Timer Value always reading Zero!

AimHigh — Wed, 22 May 2019 15:31:03 GMT

Yes, In CMSIS congif window.

RE: Stuck Timer Value always reading Zero!

Sigurd — Wed, 22 May 2019 14:37:29 GMT

Hi,

Are you enabling the timer somewhere?

nrf_drv_timer_enable(&m_timer);