← Back to the chapter · Next detail →

Technical detail · Development Environments: Reproducibility and Debugging

Probe and toolchain evidence ladder

A watchdog is a timer that can reset a device when software stops responding. Its reset reason helps the team identify that failure in a field log. Run the harness on the host to test logic without a board. Include real hardware when the question depends on timing, power, or physical signals. I2C shares data and clock wires among devices. SPI uses clock and data lines with a selection for each device. UART sends serial data between endpoints. A logic analyzer can show whether the expected bits travel on these buses. Choose the tool based on the question:

QuestionToolEvidence
What did firmware believe happened?Serial monitor or structured logBoot log, version, state transition, error counter, and timestamp
Where did execution stop?Debugger, trace, or crash dumpStack frame, register state, variable value, and source revision
Did the digital bus carry the expected bits?Logic analyzerI2C/SPI/UART trace with voltage level, sample rate, and decoded transaction
Did the analog or power signal behave correctly?Oscilloscope or current probeRail sag, reset line, clock, wake signal, or current profile under load
Can another developer reproduce the build?CI build node or scripted local buildCommand, target profile, warnings, artifact, dependency lock, and size report
Does the behavior survive outside the bench?Field log or long-running harnessRecovery event, reconnect count, watchdog reason, and retest trigger

A probe can draw current or add capacitance to a circuit. This probe loading can change the signal that it is meant to measure. Before attaching a debugger, logic analyzer, or scope, check ground reference, voltage level, connector pinout, and probe loading. A debug session should not become the fault being debugged.

← Back to the chapter · Next detail →