How to ? : Button Press Event Register & Enable a selected button to wake up the NRF52 DK from Deep Sleep

RE: How to ? : Button Press Event Register & Enable a selected button to wake up the NRF52 DK from Deep Sleep

Kenneth — Tue, 24 Sep 2019 06:04:27 GMT

Both app_gpiote and bsp provide a higher layer level of abstraction than using nrf_drv_gpiote directly. You can find various topics on both, but in specific for board support package (bsp) you can find this tutorial useful:

https://devzone.nordicsemi.com/nordic/short-range-guides/b/software-development-kit/posts/board-support-package-bsp

RE: How to ? : Button Press Event Register & Enable a selected button to wake up the NRF52 DK from Deep Sleep

german_wings — Mon, 23 Sep 2019 13:52:00 GMT

Why do we have BSP and app_gpiote , do they have overlapping functionalities , if yes which one to be used ? , do we have brief examples on either of them (Like Examples and not API documentation) , looking at the api docs , I don't understand what to start or initialize with to use the other functions in the API, I tried to use app_gpiote lib which has some functions to register a callback on button events , then along the docs I found even BSP Lib has few to register callbacks ? , Am I wrong to interpret the functionality of those APIs ,

An example of each lib just to get the basic functionality would act as a building block to further use the API for me and other users here , if any like me 😇 ,

Thank You , for your reply.

RE: How to ? : Button Press Event Register & Enable a selected button to wake up the NRF52 DK from Deep Sleep

Kenneth — Mon, 23 Sep 2019 12:25:15 GMT

Did you take a look at the documentation:
https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/lib_gpiote.html?cp=5_1_3_19

MAX_USERS simply specify how many callback handlers you want to be called.

Just make sure you understand that wakeup from deep sleep will cause chip reset, while app_gpiote is typically used in system ON idle when you want action to occur when the chip for instance is in "normal" sleep, e.g. wait for event (maintaining connection and should take appropriate action based on user input).