Silicon, power, area, and timing impact

SerDes power, equalization, and lane margin dominate bring-up risk.

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 — Ethernet MAC / PHY Basics

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 — Ethernet MAC / PHY Basics

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

Protocol deep dive

USB/Ethernet/MIPI failures cross MAC counters, PCS framing, PHY adaptation, and channel SI.

Concept diagram

HIGH-SPEED STACK

app -> MAC/framing -> PCS/encoding -> SerDes/PHY -> channel

CRC errors often mean PCS/PHY/channel, not TCP.

Metric graph

BER vs EQ SETTING

BER
1e-3 |*
1e-6 |  *
1e-9 |     **** usable window
1e-12|          *
     +-----------------> EQ tap

Metrics and artifacts to collect

• CRC error rate

• retrain count

• frame drop

• lane error

• BER

Mini case study

Ethernet link up at 100G but lossy: equalization margin on one lane narrow after package change. Digital counters were clean; PHY margin was not.

Debug branches

• If link up but lossy, PHY margin and retrain.

• If enumeration OK but throughput low, check packet size and DMA batching.

• If MIPI frame drops, blanking budget and lane polarity.

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 Ethernet MAC / PHY Basics against one concrete product workload, not a synthetic directed test.

Ethernet splits packet framing, MAC behavior, PCS, PHY training, and board/channel constraints.