How can Silicon Labs Energy Profiler identify an unexpected wakeup?

Start by identifying which supply path the instrument measures. Then correlate the current trace with available execution and radio information. The profiler supports these correlations, but a current spike alone does not identify its cause or prove that the MCU was in the intended sleep mode beforehand.

Change one expected event interval and see whether the spike follows it. Disable a nonessential peripheral temporarily and compare traces under the same conditions. A compact event marker can help alignment, provided its timing and energy overhead are accounted for.

Measure the charge associated with each event and its repetition rate. A small frequent wakeup can consume more energy than an occasional larger burst. Save the trace and configuration together, then verify the fix in the normal build without additional diagnostic activity.