Sleep mode with SoftDevice + DFU + RTC

RE: Sleep mode with SoftDevice + DFU + RTC

Vidar Berg — Fri, 04 Oct 2019 06:16:58 GMT

Ok good. Can you check if sd_app_evt_wait() always returns immediately, and comment out the initialization of UART?

RE: Sleep mode with SoftDevice + DFU + RTC

abe — Thu, 03 Oct 2019 15:14:44 GMT

Yes, the sd_app_evt_wait() returns NRF_SUCCESS

RE: Sleep mode with SoftDevice + DFU + RTC

Vidar Berg — Thu, 03 Oct 2019 14:48:44 GMT

[quote user="Abele"]Please note that when goes in System OFF the board current drop to few uA[/quote]

That's good to know. It indicates that the measurement setup is correct and that there isn't any external circuitry that draws the extra current.

Have you verified that sd_app_evt_wait() actually returns NRF_SUCCESS? Assume you have the Softdevice enabled since you're doing advertising, but note that most of the sd_ APIs, sd_app_evt_wait included, will only work when it is enabled.

RE: Sleep mode with SoftDevice + DFU + RTC

abe — Thu, 03 Oct 2019 13:39:56 GMT

Was the advertising BLE_ADV_EVT_IDLE inside on_adv_evt() callback. (I have reduced the APP_ADV_DURATION to 5 seconds for check)

Now I have commented the advertising_start() function call just before the main loop, but I have same result, same current
Please note that when goes in System OFF the board current drop to few uA

RE: Sleep mode with SoftDevice + DFU + RTC

Vidar Berg — Thu, 03 Oct 2019 12:47:58 GMT

What causes the program to enter System OFF when you're not advertising?

RE: Sleep mode with SoftDevice + DFU + RTC

abe — Thu, 03 Oct 2019 12:25:23 GMT

I also tried with BLE advertising/scanning disabled, but in this case goes into System OFF sleep and the awake is possible only with external event, not using the RTC/app timer as I need

RE: Sleep mode with SoftDevice + DFU + RTC

Vidar Berg — Thu, 03 Oct 2019 12:16:05 GMT

Hi,

To isolate the problem, can you try to only call sd_app_evt_wait(); from your main loop and don't perform the I2C reads or start any BLE advertising/scanning?

RE: Sleep mode with SoftDevice + DFU + RTC

abe — Thu, 03 Oct 2019 09:55:45 GMT

Hi Vidar,

I add the FPU disable code, but nothing change.
My main loop code is:

    // Enter main loop.
    for (;;)
    {
        //idle_state_handle();
      
        #if (__FPU_USED == 1)
        _set_FPSCR(_get_FPSCR() & ~(0x0000009F)); 
          (void) __get_FPSCR();
          NVIC_ClearPendingIRQ(FPU_IRQn);
        #endif
        sd_app_evt_wait();
        periph_check();

    }

the periph_check() reads some I2C data every 10 msec.
The current profile has a minimum sink of 3mA (in the "idle" time between I2C data reading)
Any other suggests?

RE: Sleep mode with SoftDevice + DFU + RTC

Vidar Berg — Thu, 03 Oct 2019 07:18:24 GMT

Hi,

The debugger should exit debug mode when it's done programming or when you exit a debug session. The chip will not go out of debug interface mode if you just disconnect the cable. Before you start measuring I would recommend you to do a power cycle of your board to make sure it boots into 'normal' mode.

Another possible explanation is that the CPU does not go to sleep because of a pending FPU event ([87] CPU: Unexpected wake from System ON Idle when using FPU). Of course, this is only relevant if you actually use FP instructions in your code. The workaround is included in power management module used in our examples, see nrf_pwr_mgmt_run()->PWR_MGMT_FPU_SLEEP_PREPARE()

RE: Sleep mode with SoftDevice + DFU + RTC

abe — Thu, 03 Oct 2019 07:04:00 GMT

Hi Vidar,

Yes, the call is inside the main loop, then the function is called multiple times.
It seems that idle current is same as run mode (in my case about 3mA).
A further request: the debug mode is automatically disabled when I disconnect the SWD pod?
Or there are some action to do inside the code to disable it?

RE: Sleep mode with SoftDevice + DFU + RTC

Vidar Berg — Thu, 03 Oct 2019 06:37:57 GMT

Hi,

Are you calling call sd_app_evt_wait() from your main loop like the idle_state_handle() function in the ble_app_buttonless example? Note that it may have to be called multiple times to clear the internal event registers before the CPU can go to sleep. Also, what is the idle current you measure now?