hdl-simulation

Compile and run HDL simulations across Verilator, VCS, and Xcelium.

Updated Jan 18, 2025
One-click install
npx skills add https://github.com/dv-flow/dv-flow-libhdlsim --skill hdl-simulation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hdl-simulation
Source: https://github.com/dv-flow/dv-flow-libhdlsim/tree/main/docs
Command: npx skills add https://github.com/dv-flow/dv-flow-libhdlsim --skill hdl-simulation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HDL design teams struggle to configure and run simulations across different toolchains and simulators, causing setup overhead and slow iteration.

Core Features & Use Cases

  • Unified tasks for building, elaborating, and running HDL simulations across Verilator, VCS, Xcelium, and other backends.
  • Abstract workflow that lets you plug in simulator-specific implementations without changing project code.
  • Reusable data types for compile, elaboration, and run arguments to customize behavior per project.

Quick Start

Configure a project to compile HDL sources and run simulations using the hdlsim package.

Frequently Asked Questions about hdl-simulation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run HDL simulations across multiple simulators like VCS and Verilator without changing project code?

To run HDL simulations across multiple simulators, use a unified workflow with abstract tasks that plug in simulator-specific implementations for Verilator, VCS, and Xcelium without changing project code.

What is the best way to configure a simulator-agnostic HDL simulation workflow?

Configuring a simulator-agnostic HDL simulation workflow involves using reusable data types for compile, elaboration, and run arguments to enforce a consistent dataflow interface across different simulator backends.

Does this HDL simulation workflow support Xcelium and Verilator backends?

Yes, this HDL simulation workflow supports Xcelium, Verilator, and VCS backends, enforcing a consistent dataflow interface for arguments, libraries, and run controls across all supported simulators.

How do I customize compile and elaboration arguments for HDL simulations per project?

You can customize compile and elaboration arguments for HDL simulations per project by using reusable data types designed to define build, elaboration, and run controls within the unified workflow.

Why does setting up HDL simulations across different toolchains cause slow iteration?

Setting up HDL simulations across different toolchains causes slow iteration due to the overhead of configuring separate simulator environments, which a unified workflow solves by abstracting build and run tasks.