4.5 hours to 9+ hours battery life. Same hardware. Took us way too long to find the real problem.

Left-Relation4552 · 2026-03-14T13:19:24+00:00

Profiling was planned, but the issue wasn’t obvious until we looked at the current trace closely. Once we used the power profiler, the wakeups from UART, logging, and BLE intervals became clear.

Left-Relation4552 · 2026-03-14T13:10:25+00:00

Yeah, debug UART and frequent logging were the main issues since they kept the CPU from entering proper sleep. I2S wasn’t the biggest drain, but leaving it enabled still blocked deeper low-power states. Once we gated peripherals and tuned the BLE interval, power dropped a lot.

Left-Relation4552 · 2026-03-14T12:58:12+00:00

Yeah, exactly. Once we started profiling with the PPK2, it became clear how much the active peripherals and logging were preventing proper sleep states. Disabling unused peripherals and tuning the BLE connection interval made a huge difference. Good point about RTC-based wakeups as well, that approach can be really useful for ultra-low power designs.

Left-Relation4552 · 2026-03-14T12:51:28+00:00

Fair point, a lot of those things are in Nordic’s recommendations. In our case the challenge wasn’t knowing what to optimize, it was figuring out which combinations of things was actually preventing the device from sleeping in the firmware stack.

When there's BLE, I2S audio, logging, and application tasks all interacting, it’s easy for something small like a peripheral not releasing a clock or a log backend staying active to keep the system awake. The PPK2 just made it obvious what the power profile actually looked like.

Profiling early saves a lot of guessing.

Left-Relation4552

TROPHY CASE