RE: nRF52832 + NCS v2.9.2: high BLE power on official bluetooth/peripheral sample (PPK2)

Einar Thorsrud — Wed, 03 Jun 2026 07:20:23 GMT

Hi,

Generally comparing average current between applications can be difficult, as for instance in a bluetooth application advertising interval and packet length matters significantly, as does connection parameters in a connection. So I would first start with looking at the idle current consumption. Most samples have UART logging enabled by default. Disabling that is the most important factor for current consumption. See Power optimization recommendations.

Assuming you are referring to the Zephyr Bluetooth peripheral sample, I did a quick test on my end with an nRF52840 DK (as I do not have a nRF52832 DK at hand right now), and see that I get the idle current consumption down to an expected level if I disable UART logging by adding this to prj.conf:

CONFIG_LOG=n
CONFIG_SERIAL=n
CONFIG_CONSOLE=n
CONFIG_UART_CONSOLE=n

The current consumption when for instance the CPU or radio is active will be higher on your device as you do not have the DCDC components. If current consumption matters and depending on your supply voltage, I would recommend considering adding the DCDC inductors if you still have flexibility to update your hardware.

If you still see high current consumption after disabling logging, can you share your modified sample application and PPK2 plots showing both idle and active current (the exported ppk2 file would be good as well)?