Don't Panic: Low-Power Embedded Design

A small computer that runs on a battery has a peculiar accounting problem. It may spend most of its day waiting, yet the few moments when it wakes can consume much of the day's energy. Low-power embedded design means arranging the whole device so its useful work costs less energy while it still responds on time. The word "whole" matters: the processor does not get to file a separate electricity bill from the sensor, radio, regulator, and circuit board.

Think of a sensor that takes a reading once each second. It wakes, starts the sensor, measures, processes, perhaps sends a message, then waits again. The wait interval may look wonderfully quiet on a graph. The short burst still counts. Add current multiplied by time for each interval, then divide the total charge by the cycle time. That gives average current for this particular workload. A single low point on the graph gives you a pleasing number and very little else.

The obvious next move is to pick the deepest sleep state. Unfortunately, power states come with terms and conditions. A deeper state may wake more slowly, stop the timer you intended to use, or forget data you meant to keep. Exit latency is the time needed to return to useful work. Retention means which memory and registers survive while waiting. If the application has a response deadline, the lowest-current state can be the wrong state. That is not a paradox; it is a missed requirement.

There are also two separate knobs hiding under the word "sleep." System power management handles the CPU or whole-chip state. Device power management handles peripherals that are no longer in use. An idle CPU beside an awake sensor is still an awake product. A regulator can draw current with nothing useful happening at all. If the wait baseline remains high, inspect the powered rails and device requests before spending a week polishing the CPU idle loop.

The useful habit is to draw the supply boundary, record one complete work cycle, and then change one thing at a time. Include the active peaks as well as the quiet baseline. Keep the workload and measurement setup the same across comparisons. The Intro explains the device and its decisions; the Cheatsheet keeps the equations and state checks close by; the Practice Reference shows how to build and measure a budget. The Exercise lets you reject a tempting sleep mode when its wake time misses the deadline. That is the sort of rejection a battery can live with.