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
      • VIP & Agent Architecture: Concepts
      • VIP & Agent Architecture: Integration
      • VIP & Agent Architecture: Debug
      • VIP & Agent Architecture: Interview
    • Scoreboard & Checker Strategy
    • 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. VIP & Agent Architecture
On this page

    Interface ProtocolsAll levels

    VIP & Agent Architecture

    VIP turns protocol rules into observable, checkable behavior — but only for the boundaries it sees.

    • 4topics
    • 4lessons

    What you'll learn

    VIP turns protocol rules into observable, checkable behavior — but only for the boundaries it sees.

    • Separate sequence intent, driver activity, sampled monitor events and independently checked expectations.

    • Choose active versus passive from stimulus ownership at each boundary, not simply block versus chip level.

    • VIP models the spec, not your RTL — integration assumptions can differ.

    Connection

    Applies verification methodology to all protocol topics in the course.


    Key diagram

    Intent and observation are different evidence

    Intent and observation are different evidence. Role-level UVM-style agent. The monitor's sampled acceptance evidence must not be replaced by the sequence's intended operations.
    Role-level UVM-style agent. The monitor's sampled acceptance evidence must not be replaced by the sequence's intended operations.
    Check yourself If a sequence sends ten items, does that establish ten accepted DUT transactions?

    No. The monitor must establish the actual acceptance events; stalls, cancellation or stimulus errors can change the count.


    Study this topic

    1. Concepts — rules and mental models

    2. Integration — system contracts

    3. Debug — trace the first divergence

    4. Interview — explain and defend your answer

    PreviousNext: VIP & Agent Architecture: Concepts

    Up next

    Up nextVIP & Agent Architecture: Concepts

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • Scoreboard & Checker Strategy
    • Compliance & Coverage Plan
    • Protocol Waveform Debug