Power Management blocks main loop

RE: Power Management blocks main loop

ThomasDmr — Tue, 25 Oct 2022 13:44:23 GMT

Thank you very much for these clarifications.

RE: Power Management blocks main loop

Vidar Berg — Tue, 25 Oct 2022 12:32:13 GMT

No problem!

[quote userid="116018" url="~/f/nordic-q-a/93207/power-management-blocks-main-loop/392372"]If I understand correctly, the main loop is looped through after an interrupt is called by any of the services ?[/quote]

Yes, your understanding is correct.

[quote userid="116018" url="~/f/nordic-q-a/93207/power-management-blocks-main-loop/392372"]In my case, the flags are indeed updated by bluetooth communication, so I imagine the loop is called afterwards ? (this part of the code was actually working, so this makes sense).[/quote]

Correct. Bluetooth events are notified by the Softdevice to the application through the softdevice interrupt.

[quote userid="116018" url="~/f/nordic-q-a/93207/power-management-blocks-main-loop/392372"]The only part of the code that was having trouble was the last part where I try to catch GPIO input actions. I guess that I should manage the GPIO through interrupts as well ?[/quote]

Yes, sounds like this will be the solution for you.

[quote userid="116018" url="~/f/nordic-q-a/93207/power-management-blocks-main-loop/392372"]Related question : what would be the consequence of not putting the device in sleep when operating ? Just a higher power consumption ?[/quote]

Yes, the consequence is increased power consumption.

[quote userid="116018" url="~/f/nordic-q-a/93207/power-management-blocks-main-loop/392372"]In my case, the device is functioning for a few minutes during which the user configures the device, then, once the alarm is set, the device enters the deep sleep mode. Not using the nrf_pwr_mgmt_run() would only impact the times the board isn't deep sleep right ?[/quote]

Yes, it will not affect the device when it is in deep sleep (aka System OFF mode).

RE: Power Management blocks main loop

ThomasDmr — Tue, 25 Oct 2022 11:58:31 GMT

Hi Vidar,

Thanks a lot for your quick reply !

If I understand correctly, the main loop is looped through after an interrupt is called by any of the services ?

In my case, the flags are indeed updated by bluetooth communication, so I imagine the loop is called afterwards ? (this part of the code was actually working, so this makes sense).

The only part of the code that was having trouble was the last part where I try to catch GPIO input actions. I guess that I should manage the GPIO through interrupts as well ?

Related question : what would be the consequence of not putting the device in sleep when operating ? Just a higher power consumption ?

In my case, the device is functioning for a few minutes during which the user configures the device, then, once the alarm is set, the device enters the deep sleep mode. Not using the nrf_pwr_mgmt_run() would only impact the times the board isn't deep sleep right ?

Thanks again for your precious help !

RE: Power Management blocks main loop

Vidar Berg — Tue, 25 Oct 2022 10:40:32 GMT

Hello,

nrf_pwr_mgmt_run() will make the device enter sleep (i.e. System ON mode), and the program will not return from this function until next time the CPU is woken up by an interrupt.

The program should iterate through the loop again after servicing the interrupt, even if you enter sleep with nrf_pwr_mgmt_run(). So, Are your state flags (wakeFromAlarm, etc) updated from interrupts?

Best regards,

Vidar