RE: How to Use RTC peripheral and GPIO pin as Wake-Up Sources in nRF7002DK (Zephyr)

Kazi Afroza Sultana — Fri, 14 Mar 2025 12:42:39 GMT

2. RTC as a wakeup

You can use kernel-based sleep APIs, such as k_msleep or k_sleep() functions. No need to add specific NRF_RTC libraries, as the kernel provides timing-based APIs.

3. We do use zephyr rtos, which supports many architectures, so I fully understand your confusion here.

Zephyr based samples often does not include a "requirement" section, as can be seen here on the basic/button sample (which includes APIs on how to wakeup from button press):

https://docs.nordicsemi.com/bundle/ncs-2.9.0-nRF54H20-rc1/page/zephyr/samples/basic/button/README.html#button

while this sample works on almost all nRF-based boards, as long as "sw0" and "led0" is defined in the device tree, zephyr does not explicitly list which boards are supported.

In NCS, we do this in our sample applications, as shown here in the bluetooth/peripheral_uart sample documentation:

https://docs.nordicsemi.com/bundle/ncs-2.9.0-nRF54H20-rc1/page/nrf/samples/bluetooth/peripheral_uart/README.html#requirements

RE: How to Use RTC peripheral and GPIO pin as Wake-Up Sources in nRF7002DK (Zephyr)

Kazi Afroza Sultana — Fri, 14 Mar 2025 06:21:21 GMT

Hello,

a. GPIO as Wake-Up Source:

For configuring GPIO pin (for example: SW0) as a wake-up source, you need to configure GPIO with the SENSE mechanism. It is not enabled in zephyr by default for all GPIOs. You need to enable the sense edge mask in the device tree file.

&gpio0 {
    sense-edge-mask = <0xffffffff>; /* Enable PORT event for all pins on GPIO0 */
};

Adding the sense-edge-mask property, which will make the GPIO driver use the GPIOTE PORT event rather than dedicated GPIOTE IN channels.

I have found this case (+) Proper configuration of GPIO IRQ on nRF52 - Nordic Q&A - Nordic DevZone - Nordic DevZone, which may help.