Hi all,
We're building a PoC of a simple BLE device with a following setup:
- custom PCB with nrf54l15 rev2 and 32MHz oscillator
- FreeRTOS + custom port
- nrfx version 3.14.0
- softdevice s145 version 10.0.0
- our application layer
In order to handle the softdevice operation we're using some of the modules from nRF5 SDK (like nrf_sdh, nrf_sdh_ble etc.).
The baseline current consumption for now for most of the functionalities disabled and the mcu sleeping is 6uA. The moment the softdevice is enabled with
nrf_clock_lf_cfg_t const clock_lf_cfg =
{
.source = 0,
.rc_ctiv = 32,
.rc_temp_ctiv = 2,
.accuracy = 1,
.hfclk_latency = 1000,
.hfint_ctiv = 8,
};
ret_code = sd_softdevice_enable(&clock_lf_cfg, app_error_fault_handler);
the current consumption increases to about 140uA and stays on this level as long as the softdevice is enabled. The moment the softdevice is disabled with
sd_softdevice_disable() the level goes back to 6uA. That is the case even if no BLE functionalities are started.
If the NRF_CLOCK.TASKS_XOSTOP is triggered manually, the current level goes back to 6uA, but the softdevice stops working correctly.
On initialization the nrf_oscillators_hfxo_cap_set is called.
After a full power cycle the behaviour is the same.
For the builds with app protection off, if the device is reset by the debbuger - the moment the debugging session is closed and the debugger is disconnected, the current also goes back to 6uA even if the softdevice is still enabled (the debugging session is crucial not physically disconnecting the probe). After that, softdevice and the device itself are working correctly.
Is the clock configuration wrong? Some peripherals are handled incorrectly?
Regards,
Maciej
