Configurable UVM agent
Active and passive modes, configurable lane counts and timing parameters driven from a single configuration object.
Verification IP
MIPI Verification IP built on standard UVM practice
Protocol agents with checking and coverage, delivered as readable source and supported through integration. Availability is stated honestly: C-PHY today, more on the roadmap.
Overview
A verification component, not a black box
Our MIPI Verification IP is designed for teams that need to understand and extend what they run. Every agent ships as source with its checking and coverage intent documented, so it can be reviewed by your verification leads and reused across derivatives.
Typical use cases include block-level verification of a PHY or controller, passive monitoring at SoC level, and building a protocol-aware regression around an existing design. Where a feature is not yet implemented, we say so during scoping and, if it matters to your project, quote it as custom development.
- Source-level UVM delivery
- Documented coverage intent
- Passive and active modes
- Extensible sequence library
Key capabilities
What comes with an agent
Sequence library
Reusable base sequences for common traffic patterns, extensible for project-specific scenarios.
Protocol checking
Monitor-side checks and SVA covering legal state transitions and structural rules of the interface.
Coverage model
Covergroups for states, transitions and configuration combinations, delivered as editable source.
Scoreboarding hooks
Analysis ports and reference-model interfaces so the agent slots into your existing checking strategy.
Debug support
Structured logging, transaction recording hooks and human-readable protocol traces.
Supported and roadmap
Protocol availability
Roadmap ordering is influenced by customer demand. If a planned protocol is on your critical path, talk to us about sponsoring it.
| Protocol | Status | Notes |
|---|---|---|
| MIPI C-PHY | Available | Symbol-level stimulus, protocol checks and coverage model. |
| MIPI D-PHY | In development | HS/LP handling and escape mode support in progress. |
| MIPI CSI-2 | Planned | Packet-layer agent planned on top of PHY support. |
| MIPI DSI-2 | Planned | Command and video mode traffic planned. |
| MIPI I3C | Planned | Controller/target agent planned. |
| Custom protocol | On request | Bespoke agents scoped per engagement. |
UVM architecture
Structured for reuse across your projects
The value of Verification IP shows up on the second project. We keep the structure conventional so any UVM engineer can pick it up without a translation layer.
- Layered agent structure (sequencer, driver, monitor) that mirrors standard UVM practice.
- Configuration-object driven setup instead of hard-coded parameters.
- Passive monitoring mode for integration into existing SoC-level environments.
- Source-level delivery so your team can extend, review and debug without a black box.
- Clear separation between protocol logic, checking and coverage for independent reuse.
Coverage and checking
Confidence you can measure
Checking and coverage are treated as first-class deliverables, not an afterthought bolted on at the end.
Functional coverage
Covergroups for interface states, transitions, configuration space and error paths, with documented intent per coverpoint.
Protocol checks
Assertions and monitor checks that fire at the point of violation with descriptive messages.
Coverage closure support
Gap analysis and targeted sequence development to move remaining bins toward closure.
Integration approach
From scoping to a running regression
- 01
Scoping
Review your interface configuration, simulator and existing environment structure.
- 02
Delivery
Source-level UVM package with example environment, documentation and a smoke-test setup.
- 03
Bring-up
Support during first integration, connection to your scoreboard and initial regression runs.
- 04
Ongoing support
Issue resolution, extensions and coverage work as the project evolves.
Engagement models
Ways to work with us
Commercial terms are agreed per engagement based on scope, protocol and support level.
VIP licence
Access to the agent source for a defined project scope, with documentation and bring-up support.
VIP plus integration
Licence combined with an engineering block to integrate and validate it in your environment.
Custom development
A protocol agent built to your specification, with agreed milestones and deliverables.
Ongoing support
Retainer-style support for maintenance, extensions and verification questions.
FAQ
Common questions
Request a technical discussion
Send us your interface configuration and schedule. We'll come back with a concrete view of what our Verification IP covers today and what would need building.