Long button sleep/wakeup

RE: Long button sleep/wakeup

Sejl — Thu, 30 Nov 2017 06:38:07 GMT

Again, let me comment on myself :)

If I'm already setting flag for a device to shutdown, I can turn off everything in this procedure, and then just shut down processor on button release. Customer will see that device is apparently turned off when shutdown flag has been set, and will release button...

RE: Long button sleep/wakeup

Sejl — Wed, 29 Nov 2017 15:28:06 GMT

Yes, that is an option, but as in original post my pcb is already layed out so... Thank you anyway.

RE: Long button sleep/wakeup

Jørn — Wed, 29 Nov 2017 15:10:39 GMT

Yet another possibility, as described in this post is to use the low power comparator to trigger a wake-up signal on high to low transition. That way you can simply disable sensing of the pin, and configure the LPCOMP. This will allow the chip to go to sleep, as the DETECT signal will now be low, and releasing the button will not affect it.

RE: Long button sleep/wakeup

Sejl — Wed, 29 Nov 2017 14:32:53 GMT

This is exactly what I am doing right now :) Thank you!

EDIT: It is working. However, it is not elegant solution because device is powered off upon release. Customer can expect to hold down button until device turns off, and it will never happen until he releases the button. But, OK....

RE: Long button sleep/wakeup

Jørn — Wed, 29 Nov 2017 14:31:33 GMT

Another possibility is instead of triggering the actual sleep routine by the long press, the long press detection could simply set a flag, and when the release of the button triggers a new event you can perform a check on said flag and go to sleep if it is set.

RE: Long button sleep/wakeup

Sejl — Wed, 29 Nov 2017 14:27:31 GMT

Since there is only one button in my system, I will have to rethink moving sleep action from long press to short. Thank you for your answer.

RE: Long button sleep/wakeup

Jørn — Wed, 29 Nov 2017 14:00:25 GMT

Hello Sejl

According to the product specification page 44, the chip is brought out of system off by an active DETECT signal. The DETECT signal is generated when a pin is in the state it is configured to sense. The bsp module uses the app_button library, which in turn uses GPIOTE.

By default it configures the buttons to detect toggle, this is implemented by the GPIOTE driver by changing the sense configuration for the specific pin whenever the DETECT signal triggers. So as you push the button, the pin it is connected to goes low, which triggers a low-to-high transition of the DETECT signal. The GPIOTE driver then changes the polarity, causing the DETECT signal to go low again, and then executes the specified handlers. Now your button is specified to generate a DETECT signal on a high input, which is what you get when you release the button.

You could try use bsp_buttons_disable() and bsp_wakeup_button_enable before you initiate sleep. The first function disables sense for all buttons, and the second enables sensing for the state defined as active state in pca10028.h (Low state).

Edit: I realized this wouldn't work properly if your designated wake-up pin is the same as the pin you use to put it to sleep as the button would naturally have a high DETECT signal since you're holding it down. You would then need to wait to initate the sleep until you have released the button, or use different buttons for sleep and wake.

Best regards

Jørn Frøysa