Most protocol tutorials show the correct sequence. These lessons show the failures, and give the check that finds each one. The labs operate in the browser. You need no hardware and no oscilloscope.
The serial buses used in most embedded products, and the failures that each bus causes without an error message. Each lesson gives the check that finds the failure, and a lab that operates in the browser.
I²C uses two wires on one shared bus. Each device can only pull a line down. This lesson gives the four common failures. The failures are absent pull-up resistors, address conflicts, clock stretching, and incorrect probe connections. A check finds each failure.
Lesson 1 · ~14 min
Clock polarity or phase can be incorrect. A chip-select signal can be incorrect. A slave can continue to drive MISO. The bus can stop at one clock frequency.
Coming soon · ~12 min
A filter can discard every frame and give no message. Bit timing can set the controller to the bus-off state. An ISO-TP flow control failure can come from real hardware.
Coming soon · ~14 min
TX and RX can connect incorrectly. Logic levels can disagree. A receiver overrun discards bytes. The system can look correct.
Coming soon · ~10 min
The ESP32-S3-DevKitC-1 N16R8, from the first GPIO write to a sketch you flash. Each lesson gives the wiring, the program, and a lab that operates in the browser.
How LabWired steps an analog circuit next to your firmware, and how to read the result on an oscilloscope in the browser.
3 lessons published. Want one on a bus we have not covered? Ask on r/labwired.