Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I would like to get some confirmation on the use of gpio_getPinInterruptStatus().
My goal is to discover whether a GPIO line caused the BCM20737S to wake up from timed deep sleep or whether it was just time to wake up. While I'm able to find out whether I just came from POR or not, I'm not sure how I can make certain that a GPIO interrupt caused that wake up.
The next best thing to try was using the following code:
else if(mia_isResetReasonTimedWake()) // this function is not working (button press reset also return TRUE
Also notice that I'm using SDK 2.2.0 by now. To refine the question further, what I'm looking for is a separation
between GPIO based wakeup from deep sleep and wakeup from timed deep sleep. I don't like the ideas I have to achieve that, i.e. to measure the time since sleep start and guess whether we should behave as if we came from timed wakeup, or to develop an external circuit that stores the GPIO state during bootup.