Cause of wake-up

RE: Cause of wake-up

Susheel Nuguru — Fri, 04 Nov 2016 09:38:53 GMT

similar discussion here

RE: Cause of wake-up

Susheel Nuguru — Fri, 04 Nov 2016 09:26:55 GMT

True, does not look very optimum because after the wakeup and before you read the pins, their status might have changed. For example if the wakeup is caused by a button connected to a gpio, then we hope that the button is still pressed after the wakeup till we read the button status.

RE: Cause of wake-up

Manu — Tue, 01 Mar 2016 17:09:06 GMT

I only used the pin status reading on wake up. It was sufficent to decide the option to take .

Thanks at all !

RE: Cause of wake-up

John — Tue, 01 Mar 2016 14:39:20 GMT

The only issue here is that the NRF_GPIO->IN register is 32 bits and POWER->GPREGRET is 8 bits according to the reference manual I am looking at. You may need to come up with a way to translate the GPREGRET contents to pin numbers and vice versa.

RE: Cause of wake-up

Susheel Nuguru — Tue, 01 Mar 2016 10:20:50 GMT

pin_status1 = (NRF_GPIO->IN & (1 << pin1_no) & (1 << pin2_no));

RE: Cause of wake-up

Manu — Tue, 01 Mar 2016 09:54:44 GMT

What do you call the GPIO pin status ? Is it IN ?

RE: Cause of wake-up

Susheel Nuguru — Tue, 01 Mar 2016 08:53:01 GMT

If you see the Reset behavior chapter, you will see that the GPIO is not reset on wake up from System off. So the below solution should work.

read and store(persistently or in GPREGRET register) the GPIO pin status before going to system off and then read again after waking from system off and compare them.