NRF52833 SLEEP MODE & WAKEUP THROUGH GPIO INTERRUPT.

RE: NRF52833 SLEEP MODE & WAKEUP THROUGH GPIO INTERRUPT.

Jørgen Holmefjord — Fri, 22 Jul 2022 12:15:59 GMT

How do you configure/setup the timer? Are you using RTC/app_timer or the TIMER peripheral? As long as you only enter System ON idle mode, not System OFF, the timer can run during the sleep period. The timer will then wakeup the chip every 20 second. If you shut down the timer when going to sleep, you need to restart it when you press the button to wakeup.

Please post your code to show what you are doing and what is not working.

RE: NRF52833 SLEEP MODE & WAKEUP THROUGH GPIO INTERRUPT.

sne_333 — Wed, 13 Jul 2022 03:14:35 GMT

Hi Jorgen,

Can you please help?

I observed is that the timers are not getting initialized again after waking up. I have one timer which runs few tasks at an interval of 20seconds. How to start that after waking up??

Thanks & Regards,

Snehal

RE: NRF52833 SLEEP MODE & WAKEUP THROUGH GPIO INTERRUPT.

sne_333 — Fri, 08 Jul 2022 04:28:23 GMT

Hi Jorgen,

I am setting a flag when we first advertise. If error code is 0 then I set the flasg adv_success. I am setting it back to 0 when device enters sleep mode. So I am checking this flag inside the interuupt handler. If flag is set to 0 only then it will advertise after switch is pressed. This is working.

But what I observed is that the timers are not getting initialized again after waking up. I have one timer which runs few tasks at an interval of 20seconds. How to start that after waking up??

Thanks & Regards,

Snehal

RE: NRF52833 SLEEP MODE & WAKEUP THROUGH GPIO INTERRUPT.

Jørgen Holmefjord — Thu, 07 Jul 2022 12:49:26 GMT

How do you declare and set the flag in your code? Do you unset the flag anywhere?

Did you check with a debugger/log message that the event handler is not entered, or did you just not see advertising_init() being called?

The double-trigger may be caused by noise/bouncing signals from the button.

RE: NRF52833 SLEEP MODE & WAKEUP THROUGH GPIO INTERRUPT.

sne_333 — Thu, 07 Jul 2022 11:07:37 GMT

Hi Jørgen,

Thanks for your reply. I tried to change the setting to GPIOTE_CONFIG_IN_SENSE_LOTOHI. After doing this also I am observing it gets interrupt twice and device throws error on 2nd advertising. For this I added one check point flag and if that flag is set only then I advertise. But after adding that the interrupt is not detected when i press the switch button.

What might be wrong?

RE: NRF52833 SLEEP MODE & WAKEUP THROUGH GPIO INTERRUPT.

Jørgen Holmefjord — Thu, 07 Jul 2022 09:22:51 GMT

Hi,

I'm not sure if using GPIOTE_CONFIG_IN_SENSE_TOGGLE() will give you the intended behavior. If you are using a button to generate the interrupt, this will trigger the handler both on push and release of the button, which will try to call advertising_init() two times. This may generate error codes and restarts, as the advertising is already started from the button push. If your signal comes from a switch or another device that only generates 1 signal, it may work. You should either way make sure that you keep track of when the advertising is enabled, and only try to enable it when it is not already enabled.

If you are using a push-button, I would recommend that you rather use GPIOTE_CONFIG_IN_SENSE_LOTOHI() or GPIOTE_CONFIG_IN_SENSE_HITOLO based on your button connections and desired behavior.

Best regards,
Jørgen