maximum GPIO interrupts nRF52

RE: maximum GPIO interrupts nRF52

Ole Bauck — Fri, 18 Mar 2016 12:03:19 GMT

If you configure a pin as low_accuracy it will wake up the CPU on level change, so all pins can be configured as a wake up source. In the driver you have to change the GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS to the number of wake up pins (the examples in SDK use 4 buttons on DK as wakeup).

RE: maximum GPIO interrupts nRF52

Thangaraj — Fri, 18 Mar 2016 05:38:43 GMT

Hi , My query in particular, is there any limitation is there on setting number of wake up source at a tie when the device enter into deep sleep mode

RE: maximum GPIO interrupts nRF52

Ole Bauck — Thu, 17 Mar 2016 14:44:40 GMT

You mean wake up from system OFF sleep? In that case the wake up pin needs to be another level than the wake up level or else the chip will wake up immediately, see this post. Other than that I can't think of any limitation. If you mean wake up fro system ON sleep there is no other than the ones I have pointed out.

RE: maximum GPIO interrupts nRF52

Thangaraj — Thu, 17 Mar 2016 14:01:39 GMT

Hi Sorry I have one more doubt similar to this, Is there any limitations for Wake up source configuration like this ??

RE: maximum GPIO interrupts nRF52

Thangaraj — Thu, 17 Mar 2016 12:14:17 GMT

Thanks a lot For your very quick response .........

RE: maximum GPIO interrupts nRF52

Ole Bauck — Thu, 17 Mar 2016 10:38:36 GMT

Hi,

This is possible using the PORT event. Using the PORT event / DETECT signal you can actually configure all gpio pins as interrupts. There are some drawbacks using the PORT event because it is shared between all gpio pins configured for it. As it is too complicated to explain it all here I recommend that you read the GPIO and GPIOTE chapters in the Product Specification.

Alternative to using PORT event is to use IN event. This can only be configured for 8 pins as there are only 8 channels in the GPIOTE peripheral. IN event is also more current demanding than PORT event as it requires certain resources like the HFCLK. PORT event use almost no power and can be used when device is in system OFF sleep mode (deep sleep).

With the SDK driver you should configure for so called "low accuracy" for using PORT event (for example GPIOTE_CONFIG_IN_SENSE_TOGGLE(false), where false means low accuracy). See also this post for more information about the PORT event and SDK driver (on nRF51, but still valid for nRF52).