Nordic nRF DISCUSSION

A Nordic power trace changes when logging is enabled: how can debugging stay useful?

Started by rrgiri nRF power profilingdebug loggingUART powermeasurement overheadfirmware diagnostics
3 replies 248 views 4 participants
Latest activity · 27 Sep 2026

A Nordic power trace changes when logging is enabled: how can debugging stay useful?

rrgiri Nordic nRF Forum
#1

Community replies 3

Re: A Nordic power trace changes when logging is enabled: how can debugging stay useful?

#2

Treat logging as part of the measured workload. Formatting, buffer handling and a running serial peripheral can consume time and keep resources active. Record whether output is synchronous, deferred or disabled, and compare otherwise identical builds.

Re: A Nordic power trace changes when logging is enabled: how can debugging stay useful?

#3

For a timing event, a short GPIO marker may perturb the system less than printing a full message, although it still has a cost. For state history, use a bounded compact event buffer and retrieve it after the measurement window. Include timestamps from an appropriate retained clock.

Re: A Nordic power trace changes when logging is enabled: how can debugging stay useful?

#4

Reproduce the failure with the smallest instrumentation that still reveals it, then confirm the fix with normal logging settings. Keep separate results for debugging and production builds. A lower current reading after removing logs does not by itself prove that the original wakeup bug was fixed.

TEP COMMUNITY