Digital Logic & Protocols#
Logic levels, bus health, protocol decode (SPI, I2C, UART, CAN). MCU I/O verification. Where analog measurement meets digital communication.
- Are logic levels correct for this voltage domain? — VOH, VOL, VIH, VIL thresholds. Level shifting between 3.3V and 5V domains. Marginal logic levels that work sometimes.
- Is this bus communicating? — Quick checks: is there activity? Are clock and data both toggling? Is the bus stuck high, low, or floating?
- Is the device ACKing / responding? — Protocol-level verification. I2C ACK/NACK, SPI response bytes, UART framing. Using protocol decode to see what’s actually on the wire.
- Are clock and data edges aligned? — Setup and hold timing. SPI clock phase/polarity, I2C timing margins, and catching the cases where it works on the bench but fails in production.
- Why does it fail at higher speeds? — Signal integrity at speed. Reflections, crosstalk, inadequate termination, and the point where a breadboard prototype hits a wall.