low-power-debuglisted

# Low Power Debug ## Overview Use this skill to debug low-power behavior by measuring current and wake sources before changing sleep configuration. Low-power bugs often involve board leakage, clocks, wake flags, debug settings, peripheral state, and firmware sequencing. ## When To Use Use this skill when: - Current consumption is too high or unexpectedly low. - The device fails to enter sleep, cannot wake, wakes immediately, or loses debug access. - The task involves sleep, stop, standby, deep sleep, retention RAM, wake pins, RTC, watchdog, clock gating, or PMIC sequencing. Do not use this skill when the board cannot boot at all; establish basic boot first. ## First Questions Ask for: - Chip/board and intended low-power mode. - Measured current, expected current, and measurement setup. - Wake sources and whether wake flags are available. - Debug probe attached or detached during measurement. - Peripherals left enabled before sleep. - Power rails, external devices, pull-ups, and board revision. ## Workflow 1. Confirm measurement validity. Check meter range, sampling rate, burden voltage, shunt placement, rails included, and whether debugger/USB is attached. 1. Separate firmware from board leakage. Measure baseline board state, external devices, pull-ups, LEDs, regulators, and sensors. 1. Confirm intended sleep mode. Verify the actual mode entered, not just the API called. 1. Capture wake reason. Read wake flags immediately after wake before clearing t