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
    • VIP & Agent Architecture
    • Scoreboard & Checker Strategy
      • Scoreboard & Checker Strategy: Concepts
      • Scoreboard & Checker Strategy: Integration
      • Scoreboard & Checker Strategy: Debug
      • Scoreboard & Checker Strategy: Interview
    • Compliance & Coverage Plan
    • Protocol Waveform Debug
    • Bus Integration Lab
    • Protocol Verification & Compliance: Tricky Q&A
  • Protocols Interview Prep5
  • Interface Protocols Cheatsheet
Loading lesson

←Protocol Verification & Compliance
  1. Topics
  2. Bus Protocols
  3. Protocol Verification & Compliance
  4. Scoreboard & Checker Strategy
On this page

    Interface ProtocolsAll levels

    Scoreboard & Checker Strategy

    Assertions and scoreboards provide complementary, sometimes overlapping evidence when their scopes and assumptions are explicit.

    • 4topics
    • 4lessons

    What you'll learn

    Assertions and scoreboards provide complementary, sometimes overlapping evidence when their scopes and assumptions are explicit.

    • Assertions: temporal rules on signals (valid/ready, protocol state).

    • Scoreboards: end-to-end request/response correlation.

    • A scoreboard correlation key must distinguish simultaneous operations; other correctness fields belong in the stored transaction context and checks.

    Connection

    Verification strategy for any protocol in the course.


    Key diagram

    Separate legality from identity and value

    Separate legality from identity and value. A retained response can have offer-time legality obligations before acceptance. Queue identity and byte-value checks answer additional questions.
    A retained response can have offer-time legality obligations before acceptance. Queue identity and byte-value checks answer additional questions.
    Check yourself Can an ID-only busy bit replace the queue when two requests reuse one ID?

    No. It cannot distinguish their order, expected byte ranges and identities.


    Study this topic

    1. Predict the first checker failure — Read the sampled rules and queue trace, then inspect the runnable observers.

    2. Map each requirement to evidence — Separate correctness, coverage, cancellation and observer capacity.

    3. Check a reported mismatch — Distinguish DUT, monitor and expectation-model errors.

    4. Explain the evidence boundary — State what the checker establishes and what remains unobserved.

    PreviousNext: Scoreboard & Checker Strategy: Concepts

    Up next

    Up nextScoreboard & Checker Strategy: Concepts

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • VIP & Agent Architecture
    • Compliance & Coverage Plan
    • Protocol Waveform Debug