SPI Modes & Chip-Select Rules: Silicon PPA Impact

Silicon, power, area, and timing impact

Small peripherals are cheap in area but expensive in integration-debug time.

Area drivers

• FIFOs and reorder buffers scale with outstanding depth

• Wide muxes at bridges and fabric ports

• Scoreboards and ID trackers for verification-visible RTL

• PHY/SerDes macros for high-speed attachments

Power drivers

• Toggling wide buses during idle DMA

• PHY link states (L0 vs low-power)

• Clock gating vs wake-up latency tradeoff

Timing and frequency impact

• Channel handshake loops (valid/ready, credit return)

• Cross-clock domain paths at fabric boundaries

• PHY training margin vs frequency target

PD and floorplan consequences

• Place memory controller near DRAM PHY

• Keep coherent home nodes near CPU clusters

• Route high-speed lanes with SI-aware floorplan

Verification burden

• Legal transaction combinations grow with modes

• Ordering and coherence require directed + random stress

• Compliance mapping must trace to requirements

PPA SNAPSHOT — SPI Modes & Chip-Select Rules

area     ████████░░  FIFOs + bridges
power    ██████░░░░  link/PHY dependent
timing   ███████░░░  handshake paths
verif    █████████░  modes × ordering

Signoff requires workload proof, not block-level optimism.

PPA takeaways

• Protocol features are gates and wires, not abstractions

• Every added mode needs a regression owner

• PD placement changes latency as much as microarchitecture

Design option PPA snapshot

BEFORE / AFTER — SPI Modes & Chip-Select Rules

           failing        target
metric  |    ●              ┄┄┄┄┄┄┄
        |     \
        |      \___ ● bounded fix
        |           \
        |            ● validated
        +-------------------------------> change set
Prove the mechanism moved the metric; one good dot is not proof.

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.

Principal review addendum

Re-read SPI Modes & Chip-Select Rules against one concrete product workload, not a synthetic directed test.

SPI relies on CPOL/CPHA, chip-select timing, shift order, and device-specific framing agreements.