Low Power

Many peripheral problems do not look like clock problems at first.

UART baud rate is slightly wrong. SPI fails when the rate is raised. I2C occasionally times out. A timer period drifts. ADC sampling does not match the expected rate. The CPU runs at a high frequency, but peripheral register access is still slow. A more subtle case: everything works before sleep, but the first peripheral access after wakeup fails, or a UART works in the bootloader and then stops working once the operating system takes over.

A voltage divider looks like one of the simplest analog circuits.

Vout = Vin * R2 / (R1 + R2)

Two resistors in series, a midpoint into the ADC, and a high voltage becomes a lower voltage. Battery voltage, button ladders, external inputs, and NTC dividers often use this pattern.

But many field problems start here too. The ratio is correct, but the ADC value is not. Large resistors save power, but readings jitter. Connecting the next stage pulls the voltage down. Moisture makes the divider drift. Input overvoltage creates more protection current than expected.

Sensor designs often discuss sampling rate, filter window, response time, and power as separate parameters.

In a real device, they are tied together.

If sampling is too slow, the event has already happened before the system sees it. If filtering is too heavy, the system sees the event but reacts late. If sampling is too fast, power, bandwidth, noise, and processing cost increase. Battery devices that sleep between samples make this even more visible.

Many low-power wireless devices feel “not real-time enough”: a contact sensor reports slightly late, a sensor syncs periodically, BLE notifications jitter, or Zigbee and Thread end devices cannot always be awakened immediately.

This is usually not protocol laziness. It is the core trade-off of low-power wireless: a device that wants to save power cannot keep listening to the air all the time. If it does not listen all the time, wake windows, queues, and latency appear.