nrf52810 goes to power off after BLE diconnect.

RE: nrf52810 goes to power off after BLE diconnect.

Håkon Alseth — Wed, 05 Jul 2023 12:08:25 GMT

Hi,

Could you enter debug mode and place a breakpoint on that specific function to see if it hits?

If there is no other places where you enter systemoff, I find it strange that there's no print.

Kind regards,

Håkon

RE: nrf52810 goes to power off after BLE diconnect.

Pavlin Georgiev — Wed, 05 Jul 2023 11:43:53 GMT

Yes this is the only place.

I call NRF_LOG_FINAL_FLUSH() before entering sleep. Also I see log in normal case when there is no paired device.

Regards,

Pavlin

RE: nrf52810 goes to power off after BLE diconnect.

Håkon Alseth — Wed, 05 Jul 2023 11:40:50 GMT

Hi,

Is this the only place you call the systemoff-function?

Please note: If you are using deferred logging (see sdk_config.h::NRF_LOG_DEFERRED), then you need to call NRF_LOG_FLUSH(); before entering sleep to get the log.

Kind regards,

Håkon

RE: nrf52810 goes to power off after BLE diconnect.

Pavlin Georgiev — Wed, 05 Jul 2023 10:25:21 GMT

Hi,

I use peer manager to store pairing data. And on disconnect I check with pm_peer_count for devices.

If it is 0 I call sd_power_system_off() else I start white list advertising.

But right before this calling I add log, and i do not see this log when issue appear.

Regards,

Pavlin

RE: nrf52810 goes to power off after BLE diconnect.

Håkon Alseth — Wed, 05 Jul 2023 08:51:31 GMT

Hi,

[quote user="Pavlin Georgiev"]I change sd_power_system_off() with nrf_pwr_mgmt_shutdown(NRF_PWR_MGMT_EVT_PREPARE_SYSOFF) for the cases when there is no paired device.[/quote]

How is your logic related to going to systemoff?

If you store pairing info on disconnect, then it might be a race-condition that causes the nRF to go to systemoff sometimes.

Kind regards,

Håkon

RE: nrf52810 goes to power off after BLE diconnect.

Pavlin Georgiev — Wed, 05 Jul 2023 07:24:59 GMT

Hi Håkon,

Some additional info. I change sd_power_system_off() with nrf_pwr_mgmt_shutdown(NRF_PWR_MGMT_EVT_PREPARE_SYSOFF) for the cases when there is no paired device. So naw in this case I see logs from shutdown_handler, but I still do not see logs when issue appears.

RE: nrf52810 goes to power off after BLE diconnect.

Pavlin Georgiev — Tue, 04 Jul 2023 16:12:41 GMT

Hi,

I added this code in my project:

static bool m_shutdown_handler(nrf_pwr_mgmt_evt_t event)
{
    NRF_LOG_INFO("m_shutdown_handler: %d", event);

    return true;
}

NRF_PWR_MGMT_HANDLER_REGISTER(m_shutdown_handler, 0);

But I do not see any logs when issue occurs. I also do not see logs when sd_power_system_off() is called(I use this function to put system in sleep mode when there is no know(paired) device).

Regards,

Pawlin

RE: nrf52810 goes to power off after BLE diconnect.

Håkon Alseth — Fri, 30 Jun 2023 12:07:51 GMT

Hi,

Some examples uses the button handler to go to systemoff.

Before the nrf_pwr_mgmt module should go to systemoff (if that is requested), it should give a callback through the applications registered "shutdown_handler" if that is registered within your application.

Could you enter debug mode and see if there's any calls that ends up in the function "nrf_pwr_mgmt_shutdown"?

Kind regards,

Håkon

RE: nrf52810 goes to power off after BLE diconnect.

Pavlin Georgiev — Thu, 29 Jun 2023 12:51:14 GMT

Hi Håkon,

Thank You for fast response!

Q1: Yes. I check this with Nordic Power Pofiler Kit ||. I see that consumption go around 0,38uA.

Q2: In code I use only nrf_pwr_mgmt_init() and nrf_pwr_mgmt_run().

Q3: No I have not. I use only RTT log debugging, and from logs i do not see where the code ends up.

Regards,

Pavlin

RE: nrf52810 goes to power off after BLE diconnect.

Håkon Alseth — Thu, 29 Jun 2023 11:57:20 GMT

Hi,

Q1: Have you checked the power consumption to ensure that the nRF goes into power off state?

Q2: Is your application using nrf_pwr_mgmt API? If yes, is there any calls to " nrf_pwr_mgmt_shutdown(NRF_PWR_MGMT_SHUTDOWN_GOTO_SYSOFF);" anywhere in your code?

Q3: Have you checked where the code ends up when this happens? This can be done by attaching a debugger.

Kind regards,

Håkon