High sleep power consumption with onewire after migrating to 3.2.1

RE: High sleep power consumption with onewire after migrating to 3.2.1

sasodoma — Thu, 19 Feb 2026 13:26:26 GMT

It seems that in the end Kentarou was able to reduce power consumption by suspending uart0, which is what I've been doing before the update and it doesn't work anymore. Given that this change was caused by a Zephyr update and is not directly nRF related, I will try to open an issue with them and see if someone can tell me what's to do in the new version. I will post the answer here if I get it.

RE: High sleep power consumption with onewire after migrating to 3.2.1

Ressa — Thu, 19 Feb 2026 12:55:06 GMT

Hi Sašo,

I think so. USB CDC‑ACM is not enabled by default on DKs. It seems like device power management is not implemented for USB CDC-ACM. So it will not work with pm_device_action_run() the same way as for example UART hardware peripherals.

Please have a look at below case which is similar to your question:
(+) How to disable USB CDC-ACM during running - Nordic Q&A - Nordic DevZone - Nordic DevZone

Best regards,
Ressa

RE: High sleep power consumption with onewire after migrating to 3.2.1

sasodoma — Tue, 17 Feb 2026 16:18:45 GMT

Thank you for the test. Is it possible that the difference is due to the DK not having USB CDC ACM enabled by default?

Unfortunately I do not have a DK with the nRF52840 to test, but I do have a different DK that I could use to program the ProMicro board as if it was a DK, to see if the difference is the default settings.

RE: High sleep power consumption with onewire after migrating to 3.2.1

Ressa — Tue, 17 Feb 2026 10:13:29 GMT

Hi Sašo,

I just tried your code with different ncs versions including 3.2.1 on nRF52840 DK and I am getting around 10 uA average current in all of them. The current is just for SoC. The supply is connected externally using P21 connector. Not sure why you see different current. Do you have a DK to try on that as well?

RE: High sleep power consumption with onewire after migrating to 3.2.1

sasodoma — Sat, 14 Feb 2026 18:18:22 GMT

I have bisected the difference to the commit https://github.com/nrfconnect/sdk-nrf/commit/c2eab60735568bb24788d3767a3b7f321a8a8360

I'm guessing the actual difference is in the zephyr that got updated, but I'm having trouble building while trying to bisect the zephyr repo.

EDIT: I have managed to bisect the zephyr repo as well, and the commit that causes the problem is https://github.com/nrfconnect/sdk-zephyr/commit/b03b65a9b51ae869bd36fde687ec142e970660e0, which switches CDC ACM to the new USB device stack. I can lower the power consumption by setting CONFIG_CDC_ACM_SERIAL_INITIALIZE_AT_BOOT=n, but this disables it completely. I also tried suspending both the usbd and the cdc-acm but was unsuccessful:

static const struct device *usbd = DEVICE_DT_GET(DT_NODELABEL(usbd));
static const struct device *board_cdc_acm_uart = DEVICE_DT_GET(DT_NODELABEL(board_cdc_acm_uart));

...

pm_device_action_run(usbd, PM_DEVICE_ACTION_SUSPEND);
pm_device_action_run(board_cdc_acm_uart, PM_DEVICE_ACTION_SUSPEND);

How can I keep power consumption low in sleep without disabling USB CDC ACM?

RE: High sleep power consumption with onewire after migrating to 3.2.1

sasodoma — Sat, 14 Feb 2026 10:11:55 GMT

Hi Ressa,

I can't believe I've missed that, thanks for pointing it out. Unfortunately, it appears this wasn't the cause of the problem, as power consumption is still high, even after correcting the overlay.

RE: High sleep power consumption with onewire after migrating to 3.2.1

Ressa — Fri, 13 Feb 2026 14:31:48 GMT

Hi Sašo,

It seems you are swapping TX, RX pins in uart0_sleep compared to uart0_default. Can you try to have same TX, RX pins on both to see if it makes any difference ?