Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutRoadmapCareersInternshipsFAQContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Protocol Metrics Reference
  • Protocols Glossary
  • Reading Path
  • Protocol Fundamentals25
  • AMBA Family (APB / AHB / AXI)17
  • Coherence Fabrics (ACE / CHI)17
  • Memory Interfaces (DDR / LPDDR / HBM)17
  • PCIe & CXL17
  • Embedded Peripherals (I2C / SPI / UART)17
  • High-Speed I/O (USB / Ethernet / MIPI)17
  • Protocol Verification & Compliance21
  • Protocols Interview Prep5
  • Interface Protocols Cheatsheet
Loading lesson

←Bus Protocols
  1. Topics
  2. Bus Protocols
  3. Protocol Metrics Reference

Interface ProtocolsAll levels

Protocol Metrics Reference

Common metrics for protocol performance, correctness, and debug.

Core metric families

  • Correctness: protocol violations, ordering escapes, stale data, ECC/CRC errors.

  • Performance: throughput, p99 latency, payload efficiency, retry rate, credit stalls.

  • Bring-up: enumeration success, link width/speed, training margin, boot failure rate.

  • Verification: compliance pass rate, coverage closure, waiver count, false fail rate.

Record the measurement contract

Metric

Boundary and denominator to retain

Useful throughput

Enabled useful bytes on accepted transfers / elapsed seconds; name the interface, traffic and observation interval.

Conditional stall fraction

Samples with VALID && !READY / samples with VALID. With zero offers, report no offers rather than a misleading zero stall rate.

Payload efficiency

Useful payload bytes / transmitted bytes at the specified layer; idle time and retries need clearly separated accounting.

Latency percentile

Name admission and completion events, clock/time conversion, sample population and warm-up/cancellation handling.

Retry or error rate

Name the counter, direction, traffic class, interval and attempted/completed-work denominator; a counter alone does not identify a cause.

Verification result

Requirement, enabled checker, actual observed work, configuration/source revision and verdict; distinguish expected fault detection from compliance.

Previous

2 / 158

Next: Protocols Glossary

Up next

Up nextProtocols Glossary

Sign in to save progress

Practice this lessonPrevious lessonReport an error

See also

  • Reading Path
  • Protocol Fundamentals
  • AMBA Family (APB / AHB / AXI)