Foundational theory

I2C Timing & Arbitration is a core topic in Embedded Peripherals (I2C / SPI / UART). I2C shares open-drain wires with address arbitration, acknowledge cycles, and optional clock stretching. Senior engineers treat it as a contract problem: each boundary must preserve transaction identity, ordering rules, and forward progress under backpressure.

Core concepts explained

• I2C shares open-drain wires with address arbitration, acknowledge cycles, and optional clock stretching.

• Primary metric: NACK rate, clock-stretch duration, bus recovery time

• Primary artifact: SCL/SDA waveform, transaction log, pull-up timing check

• Owners: peripheral owner, board owner, driver owner

• Layer model: software intent → transaction → channel/link → physical/timing

• Debug posture: find the first deviation, not the loudest timeout

Why this matters in real chips

In silicon integration, I2C Timing & Arbitration failures appear as hung transactions, corrupted data, bandwidth cliffs, or bring-up stalls. Low-speed serial protocols are timing contracts between RTL, board, and firmware. Without mechanism-first analysis, teams burn weeks widening buses or blaming firmware.

Mental model

I2C FRAME

SDA  ‾‾\__/‾‾\__ ... __/‾‾  ‾‾\__/‾‾
SCL  ‾‾‾‾\_/‾\_/‾ ... \_/‾‾‾‾‾‾‾‾
      S  A6..A0 R/W ACK  data..  ACK  P
      ^                            ^
    START                        STOP

START: SDA falls while SCL high
STOP : SDA rises while SCL high
ACK  : receiver pulls SDA low on the 9th clock

Worked intuition

1. Name the workload or traffic class exercising I2C Timing & Arbitration.

2. Open NACK rate, clock-stretch duration, bus recovery time and identify the failing cluster (p99 often matters more than average).

3. Tag transaction identity: ID, address, endpoint, lane, or cache line.

4. Map the symptom to protocol layer: transaction, link, or physical.

5. Collect SCL/SDA waveform, transaction log, pull-up timing check and align timestamp with VIP or analyzer view.

6. Reduce to smallest legal/illegal sequence that reproduces the bug.

7. Propose one bounded fix and list compliance + product regressions.

Common misconceptions

• Handshake activity implies the transaction is legal.

• Peak interface width equals useful payload bandwidth.

• A VIP pass guarantees integrated-system correctness.

• Software timeouts always mean the PHY or link is broken.

• More buffering fixes ordering or coherence bugs without analysis.

Visual reinforcement

I2C start/stop and ACK waveform

I2C FRAME

SDA  ‾‾\__/‾‾\__ ... __/‾‾  ‾‾\__/‾‾
SCL  ‾‾‾‾\_/‾\_/‾ ... \_/‾‾‾‾‾‾‾‾
      S  A6..A0 R/W ACK  data..  ACK  P
      ^                            ^
    START                        STOP

START: SDA falls while SCL high
STOP : SDA rises while SCL high
ACK  : receiver pulls SDA low on the 9th clock

Clock stretching

CLOCK STRETCHING (slave holds SCL low to buy time)

SCL master wants: ‾\_/‾\_/‾\_/
SCL on the bus  : ‾\_____/‾\_/   <- slave kept it low
                       ^^^^ stretch window

Master must tolerate stretch or it sees corrupted data.

Layer responsibilities

LAYER RESPONSIBILITY — I2C Timing & Arbitration

layer          owns                         common failure
-----------    --------------------------   -----------------------
software       intent, ordering needs       wrong assumption
transaction    id/addr/len/attributes       ordering / outstanding
link/channel   handshake, credits, retry    backpressure / deadlock
physical       clock/reset/lanes/PHY        timing / training / SI
observability  waveform/log/counter         missing evidence

Protocol deep dive

I2C/SPI/UART bugs are contract bugs: timing, reset value, IRQ type, and DMA watermark.

Concept diagram

PERIPHERAL CONTRACT

firmware writes regs -> RTL state machine -> pins -> board -> device
        ^                    |
        +------- IRQ/DMA ----+

If IRQ is level but driver assumes edge, you get lost events.

Metric graph

FIFO WATERMARK vs DMA

FIFO fill
 100%|        *** overrun risk
  75%|     ***
  50%|  ***     <- ideal DMA trigger band
  25%| *
   0%+----------------> time

Metrics and artifacts to collect

• NACK rate

• overrun count

• CS setup/hold violations

• IRQ miss rate

Mini case study

SPI flash worked in loopback but failed in system: CS deasserted one cycle early relative to device hold time. Board + RTL + mode bits together formed the contract.

Debug branches

• If overrun, FIFO depth vs ISR latency vs DMA burst.

• If NACK on I2C, pull-ups, speed, and clock stretch.

• If garbage data, CPOL/CPHA and MSB/LSB first.

Senior review question

Ask: what is the first transaction that deviates, and which spec rule does it test?

Key takeaways

• Connect every protocol claim to a transaction identity and measurable metric.

• Store the artifact (waveform, log, counter) next to every signoff decision.

Common pitfalls

• Debugging timeouts without finding the first bad transaction.

• Quoting peak bus width without payload efficiency and retry overhead.

• Treating VIP compliance as a substitute for system integration replay.

Theory reinforcement

Low-speed serial protocols are timing contracts between RTL, board, and firmware.