Pro lesson · Preview
Common Bus Bugs
A field guide to why a bus is dead, garbled, or flaky: pull-ups, baud/clock mismatch, drive contention, and wiring faults, plus a symptom→cause table and a scope-first method.
22 min read
This lesson is part of Pro
Upgrade to unlock the full lesson and the complete interview Q&A.
Unlock with Pro5 interview questions on this topic
Each one opens a full worked answer.
An I2C bus is completely dead, no device responds. What do you check first?Data on a bus is corrupted. How does the *pattern* of corruption narrow down the cause?What is bus contention and how does it show up on SPI and I2C?A bus works at low speed but fails when you increase the clock rate. What's going on?What's your general method for debugging a misbehaving bus?
This is just the start
Sign up free to track your progress through this course, mark lessons complete, and work through the full interview Q&A.