← Back to the chapter · Next detail →
Technical detail · Edge Acquisition: Power and Gateway Functions
TPL5110 wake, commit, DONE, and charge ledger
A TPL5110-class arrangement has two power domains. The timer remains connected to the battery at nanoamp-class quiescent current. Its DRV output controls a MOSFET or load switch feeding the MCU, sensors, and radio. The MCU’s DONE output returns to the timer. Keep those signals distinct from a reset pin: DRV controls energy to the entire load, while a low-to-high DONE transition is the firmware’s declaration that durable work has finished. For the TPL5110 specifically, DRV low turns the external MOSFET on and DRV high turns it off; other timer/load-switch combinations may use the opposite polarity.
Follow one cycle:
- Off interval.
DRVholds the TPL5110’s MOSFET off, and only timer, switch leakage, and any deliberately retained domain draw current. - Timed wake. At the programmed interval, the TPL5110 drives
DRVlow; the MOSFET conducts, the rail rises, and the MCU starts from reset rather than resuming retained RAM. - Acquire and transmit. Firmware initializes peripherals, samples the sensor, records a timestamp or sequence, and attempts the bounded communication policy.
- Commit state. Before shutdown, firmware stores only the state required for the next cold boot and verifies that the write or queued hand-off completed.
- Assert
DONE. A clean low-to-high transition tells the timer to driveDRVhigh. The MOSFET removes power until the next interval.
That boundary changes the ledger as well as the boot sequence. The energy ledger must include the always-on timer and switch leakage. For a period , load-on time , load current , timer current , and off-state leakage ,
Suppose the load draws 25 mA for 0.50 s every 600 s, the timer draws 0.035 microamps, and the disconnected load path leaks 0.10 microamps:
The active burst still dominates, but the example shows why board leakage belongs beside the timer data-sheet number. A 10 microamp regulator or programming interface left across the battery would materially change the result even though the MCU is physically off.