Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

What is GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS?

Hello,

I am wondering what this "Low Power Event" is.

I am looking through the document but I can't find the place that explains this.

Can somebody point me to the place I should look into?

Parents Reply Children
  • Thank you for your pointers!

    I read the document and have few questions.

    In the document, it is said that Low Power Events are ' not that accurate and cannot be used to track high-speed pin changes".

    What does it mean to be not accurate. Will some of the events not be generated? Is this to due with when you have multiple pins to connected?

    How is the high-speed pin changes defined. If I have a interrupt pin that is generated every ~50ms, will it be feasible to use the "low power event? What about 1ms? Multiple peripherals wiht independent interrupts? 

    WIll there be a delay to the event that is generated with the low power events?

    Thanks in advance,

    Best John

  • The port event will trigger from any pin change, the driver will then read the state of every pin declared as a low power GPIOTE pin and then execute the pins event handler. I believe 1ms is doable, but it depends on what the CPU is doing at the time. The GPIOTE event handler is executing from main context and priority level. Any SoftDevice or other higher priority activity will delay the execution of the pin event handler.

Related