External count

RE: External count

mad qu — Wed, 13 Apr 2022 07:29:47 GMT

我已经处理好了

RE: External count

mad qu — Fri, 17 Dec 2021 07:33:07 GMT

Thank you for your reply. I'll verify it. Give me more feedback.

RE: External count

Einar Thorsrud — Fri, 17 Dec 2021 07:27:14 GMT

There may still be ways to handle this. You could use a timer as counter, and do the counting with a GPIOTE input connected to a TIMER in counter mode. That way, no CPU intervention is needed to count. Then you would only need the CPU for configuration, and to read the counter value (trigger capture task and read captured value). You can even do that from another timer via PPI in order to do this in HW, so that this is accurate even if there are interrupts at the "wrong" times. See an example of that in this old thread.

RE: External count

mad qu — Fri, 17 Dec 2021 00:57:26 GMT

The external interrupt data source is a motor acceleration pulse output. I start the motor, and the motor will accelerate from 0Hz to 1kHz, and then slow down to 0Hz. This process takes only 5-7s. Once the process is started, I can't control it.

RE: External count

mad qu — Thu, 16 Dec 2021 13:10:07 GMT

I'll study it

RE: External count

Einar Thorsrud — Thu, 16 Dec 2021 12:28:16 GMT

Hi,

If you can control when the external interrupts come (for instance if you start a process of some sorts which takes a small amount of time and during that time there are many interrupts), then you can use the timeslot API for this. With that you can be granted a duration of time where you are guaranteed that there will be no SoftDevice interrupts.