Oscilloscope probing technique and ground lead effects, bandwidth-matched measurement, logic and protocol analyzer use on SPI/I2C/UART, a systematic isolate-reproduce-narrow-verify methodology, common power-rail, signal integrity, and thermal failure signatures, and JTAG-based debug for embedded firmware bring-up.
A confusing scope trace is, more often than engineers expect, a measurement artifact rather than a real circuit defect — a six-inch ground lead can ring on a fast digital edge all by itself, and a bandwidth-limited probe can just as easily hide a real overshoot problem entirely. This module builds the actual bench discipline behind reliable hardware debugging: probing technique and ground lead effects, matching probe and scope bandwidth to the signal you're actually chasing, and reaching for a logic or protocol analyzer instead of a scope the moment the question becomes digital-bus-shaped rather than analog-waveform-shaped.
From there this module builds a systematic isolate-reproduce-narrow-verify debug methodology, and teaches you to recognize the failure signatures a debug session is usually actually chasing underneath the surface symptom — power-rail sag and noise (the physical territory Module 10 covers from the power-electronics design side), and signal integrity artifacts like ringing and crosstalk (Module 9's territory from the transmission-line side) — plus JTAG-based hardware debug for embedded firmware bring-up. Module 17, Troubleshooting, immediately following, applies every tool and technique here to four real, worked diagnostic scenarios.