Async FIFO CDC: Expanded Case Study

Extended case study

Milestone review flags overflow/underflow risk, pointer synchronization integrity, latency throughput around Async FIFO CDC.

Background

Team believed crossings were stable until stress mode exposed intermittent anomalies.

Symptoms observed

• overflow/underflow risk, pointer synchronization integrity, latency throughput regression

• Mismatch between structural report and dynamic behavior

• Waiver debate under schedule pressure

Investigation timeline

1. Freeze design, reset, and tool configuration tags.

2. Reproduce failing scenario with minimized stimulus.

3. Map path/protocol/reset dependencies.

4. Classify root cause and containment options.

5. Execute minimal safe fix.

6. Run stress regression and review board.

Root cause

Root cause links to Async FIFO CDC: Async FIFOs decouple domains with gray-coded pointers and synchronized status logic; correctness depends on pointer math, full/empty rules, and reset behavior.

Fix and validation

• Targeted RTL/protocol/reset correction

• Evidence refresh

• Signoff board decision

Lessons learned

• Treat waivers as temporary risk contracts

• Track owner and expiry

• Regression before closure

CASE STUDY — Async FIFO CDC
critical issues before / after / signoff

Crossing sequence under stress

CROSSING FLOW — Async FIFO CDC

source clock domain -> launch signal -> crossing structure -> destination sample
      |                    |                 |                    |
   source FF           protocol           sync / fifo         destination FF

Key metric: overflow/underflow risk, pointer synchronization integrity, latency throughput

CDC/RDC deep dive

Protocol correctness is the bridge between structural clean and functional safe.

Concept diagram

PROTOCOL FLOW

intent -> transport protocol -> synchronization -> destination acceptance

Metric graph

PROTOCOL ISSUE BURNDOWN

open issues: 20 -> 11 -> 5 -> 0

Reports and artifacts

• FIFO pointer proofs

• req/ack liveness

• pulse miss checks

• protocol assertions

Mini case study

Async FIFO empty/full logic looked correct until gray decode mismatch appeared during reset overlap.

Debug branches

• Pointer sync audit

• formal liveness checks

• reset interaction review

Senior review question

Ask: what evidence proves this risk is closed for silicon, not just tool-clean?

Key takeaways

• State crossing class, assumptions, and owner with every issue.

• Run structural and dynamic regressions after each fix.

Common pitfalls

• Treating all warnings as equivalent risk.

• Waiving issues without containment evidence.

• Skipping reset and reconvergence stress after CDC fixes.

Principal CDC/RDC review addendum

Async FIFOs decouple domains with gray-coded pointers and synchronized status logic; correctness depends on pointer math, full/empty rules, and reset behavior.

Metric: overflow/underflow risk, pointer synchronization integrity, latency throughput