TIMER 2 not capturing value

RE: TIMER 2 not capturing value

Jared — Fri, 03 Feb 2023 14:42:37 GMT

Hi,

Yes, Whatever that happens in the callback handler will happen after the PPI have performed the Clear mask task. The callback handler runs in the CPU while the clearing of the mask use PPI which is independent of the CPU.

regards

Jared

RE: TIMER 2 not capturing value

inspiringdev123 — Wed, 01 Feb 2023 16:47:08 GMT

I removed the extended compare to a normal compare and am now reading in values on CC[1]. Would the Clear Mask Task clear the timer before I am able to capture the value?

RE: TIMER 2 not capturing value

inspiringdev123 — Wed, 01 Feb 2023 15:39:01 GMT

An input pulse is controlling the GPIOTE event (from a car's speed sensor or tachometer pin). Still early in development, so I am not concerned with this aspect yet. I want to get the Compare event on CC[1] to work first. The compare should allow me to capture a value above 60,000, but the value in the register when I capture is very low at times. The bit width is set to 16 bit in my Config

RE: TIMER 2 not capturing value

Jared — Wed, 01 Feb 2023 15:31:46 GMT

Hi,

Could explain a bit more in detail what your code does?

As far as I can see you're setting up a PPI on channel 2 that connects the LoToHigh event on a GPIOTE pin to a CAPTURE task. Which means that when the pin is toggled from low to high, the value of the Timer will be captured in the CC2 register. At same time you're setting up a COMPARE event on CC1 register for 60000. What is controlling the GPIOTE pin? And can you share a screenshot of the the Timer registers when you get the first event.

Also what is TIMER_DEFAULT_CONFIG_BIT_WIDTH set to in your config file?

regards
Jared