DEBUGDIGITAL BUSES / MISSION 007Intermediate

The I²C Device Has Disappeared

The environmental sensor worked on the controller PCB. After a 30 cm display harness was added and the bus changed to 400 kbit/s, firmware reports repeated NACKs. Determine whether the failure is power, addressing, connectivity, or bus timing, and choose a defensible board change.

Requirements

Bus 3.3 VSpeed 400 kbit/sTarget 7-bit 0x44Pull-ups 10 kΩCBUS 180 pFtR limit 300 ns · 30–70%
  1. 01Check the bus
  2. 02Build evidence
  3. 03Size the correction
Circuit overview
ASSEMBLED SYSTEMREV B · 30 cm HARNESS
CONTROLLERMCU · 3.3 VREMOTESENSOR · 0x44SDASCL+3V3R1110 kΩ+3V3R1210 kΩCBUS180 pF+3V3TP1TP2TP3TP4J3 · 30 cm harnessEquivalent measured bus capacitance to ground
Firmware: sensor request retries three times, then reports “0x44 NACK.” The same firmware worked before the harness and speed change.
MEASUREMENT BENCHReady to measure
INSTRUMENT

Sensor supply at the remote board.

Select a measurement target, then measure to inspect the result.

Evidence notebook 0 saved

No evidence saved yet. Measure, inspect the result, then save useful observations.

Current task
Current task
Technical references

Timing model and sources

The first-order 30–70% rise-time model is tR ≈ 0.8473 × RP × CB. Also check LOW-state sink current: (VDD − VOL) / RP. References: NXP, UM10204 I²C specification. TI, SLVA689 pull-up calculation.