DigitalOsc guides
Microcontroller Restarts: Supply Dip or Something Else?
DigitalOsc editorial team · Updated 19 November 2026
Compare the reset marker and local logic rail while a small development board is already running.
Use a marker tied to the observed restart
On your own low-voltage development board, identify a known restart marker, such as a documented reset line or a GPIO state emitted during boot. A boot GPIO occurs after the reset; its time is not the exact electrical reset edge. Test with a safe, repeatable load change and observe the local supply next to the controller, with a common reference.
Distinguish correlation from cause
If the local supply drops just before the restart marker, read the controller's brownout threshold and reset-cause flags for its configuration. Try a known suitable supply or reduce the test load to see whether both observations disappear. If the rail looks steady, check capture duration, probe reference, external reset and reset-cause flags before assuming the power supply is innocent.
Keep the evidence useful
Record the idle rail value, lowest observed value, delay to the marker and relevant firmware state. A normal meter reading after boot cannot settle an intermittent event. If the board resets even with no load change and no visible droop, move to the firmware watchdog or external reset branch. Avoid inferring a single cause from one trace.