Where the microamps go: low-power firmware

Low-power design is a partnership between hardware and firmware. The hardware sets the floor; the firmware decides how often you leave it.

Find the floor first

Measure sleep current with the firmware doing nothing but sleeping. If it is above the datasheet figure, look for floating inputs, pull-ups fighting outputs, peripherals left clocked and regulators with high quiescent current.

Then count the wake-ups

• Replace polling loops with interrupts and hardware timers.
• Batch sensor reads and radio transmissions instead of sending each sample.
• Let DMA move data while the core sleeps.
• Run fast and go back to sleep — finishing quickly at a higher clock is often cheaper than running slowly.

Watch the debug build

Debug interfaces, UART logging and assertions can keep clocks alive. Always validate power in the release configuration, with the debugger disconnected.

Make it testable

Add a production test that measures sleep current on every unit. A single mis-placed component or solder bridge can multiply consumption, and it is far cheaper to catch at the end of the line than in the field.