Pulse Width Counter using peripheral only

RE: Pulse Width Counter using peripheral only

ovrebekk — Wed, 19 Oct 2022 14:02:27 GMT

Hi Martin

That is great news 🙂

For full disclosure, since I had limited time to make the example I didn't take the time to properly implement it as a Zephyr library. Ideally you would want to integrate the example with the Kconfig and device tree architecture, rather than hard coding everything in the application.

I might try to do this later, but I don't know when I will have more time to look at it.

Best regards
Torbjørn

RE: Pulse Width Counter using peripheral only

Martin Rupp — Wed, 19 Oct 2022 07:24:49 GMT

Hello Torbjorn,

I got word from our FW engineer, he says it is running fine.

Thanks for your support,

Martin

RE: Pulse Width Counter using peripheral only

Martin Rupp — Mon, 17 Oct 2022 04:48:03 GMT

thanks a lot, we will test this as soon as possible.

Best regards

Martin

RE: Pulse Width Counter using peripheral only

ovrebekk — Sat, 15 Oct 2022 11:08:36 GMT

Hi Martin

Please have a look at this example:

devzone.nordicsemi.com/.../pulse_5F00_length_5F00_measurement.zip

Best regards
Torbjørn

RE: Pulse Width Counter using peripheral only

ovrebekk — Mon, 10 Oct 2022 13:20:15 GMT

Hi Martin

I will try to provide an example by the end of the week.

Best regards
Torbjørn

RE: Pulse Width Counter using peripheral only

Martin Rupp — Fri, 07 Oct 2022 13:48:34 GMT

Hello Torbjorn,

Thanks for responding so quickly. We are using nRF Connect.

Sounds straight forward indeed. If you happen to have an example, this would accelerate things greatly.

Thanks

Martin

RE: Pulse Width Counter using peripheral only

ovrebekk — Fri, 07 Oct 2022 13:28:25 GMT

Hi Martin

Which SDK are you using?

It should be relatively straight forward to implement something like this. Essentially you need to set up two GPIOTE channels on the same pin, one configured to generate an event on a low to high transition, and one for the high to low transition.

Then you need to connect the first GPIOTE channel to the timer START task over PPI, and the second GPIOTE channel needs to be connected to the timer STOP, CLEAR and CAPTURE tasks (for this you will need an additional two PPI channels).

Then you can just read the corresponding CC register any time you want to know the value of the last pulse.

Best regards
Torbjørn