GPIO wakeup low power workarounds?

RE: GPIO wakeup low power workarounds?

Ole Morten — Thu, 31 Oct 2013 11:28:55 GMT

Just in case it's unclear: The regular support portal is open to anyone, and you don't need to be a special customer in any way to post cases there. However, if there isn't any secrecy regarding your question, we do prefer to answer it here, since it potentially also benefits other users! :)

RE: GPIO wakeup low power workarounds?

Ling LI — Thu, 31 Oct 2013 10:01:52 GMT

Great news! Thanks for the clarification.

I'm sure there are many potential users who are not on your official support yet would find it userful.

RE: GPIO wakeup low power workarounds?

Ole Morten — Thu, 31 Oct 2013 09:41:37 GMT

It's only the CONFIG channels in GPIOTE that will cause high current consumption, and the chip can always be woken up by using the PORT event instead of the CONFIG channels. This means that it's perfectly possible to achieve low sleep current and wake on a GPIOTE.

The port event is what is behind app_button, but Håkon have also made a quick example here that shows how it can be used. The summary is just to set the SENSE field in PIN_CNF as wanted for the appropriate pin.

RE: GPIO wakeup low power workarounds?

Ling LI — Thu, 31 Oct 2013 06:58:48 GMT

I thought for a while... maybe an external solution is possible? But can the chip be waken up from an external source without involving GPIOTE?

For example, how about (mis)using the CTS/RTS pins to fake a successful TX/RX and use one of the EVENTS generated? Leaving the UART running still needs ~0.2mA, though.

Better ideas?