riscv-sim-run

Run prebuilt RISC-V RTL simulation binaries with Verilator and capture results.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/etewe333/eda_first --skill riscv-sim-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: riscv-sim-run
Source: https://github.com/etewe333/eda_first/tree/main/.claude/skills/riscv-sim-run
Command: npx skills add https://github.com/etewe333/eda_first --skill riscv-sim-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

本技能提供在 Verilator 环境下对 RISC-V RTL 设计进行仿真验证的自动化支持,简化从编译到日志分析的流程。

Core Features & Use Cases

  • 进行已编译的仿真可执行文件的运行,例如 ./sim/build/V<模块名>
  • 自动记录日志到 sim/logs/sim_result.log 并分析结果
  • 在 RISC-V RTL 自动化流水线的验证阶段提供快速的结果判断

Quick Start

编译并确保可执行仿真文件存在后直接运行仿真以生成并保存日志。

Frequently Asked Questions about riscv-sim-run

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

FAQPage Schema
How do I automate RISC-V RTL simulation runs with Verilator?

RISC-V RTL simulation automation with Verilator works by executing prebuilt sim binaries from sim/build/V<module>. It automatically captures execution results and writes PASS/FAIL analysis logs to sim/logs/sim_result.log.

What files and directory structure are required to run a Verilator testbench?

Running a Verilator testbench requires a prebuilt executable in sim/build/V<module>, a writable sim/logs directory for result storage, and .claude/env_info.json specifying msys_root and msystem environment paths.

Where does the automated Verilator simulation save its testbench results?

Automated Verilator simulations save testbench results to sim/logs/sim_result.log. This specific log file contains the captured execution output necessary for PASS/FAIL analysis of the RISC-V pipeline modules.

Can I validate RISC-V processor pipeline modules without manually checking logs?

Yes, you can validate RISC-V processor pipeline modules without manual checks using this automation. It executes the simulation binary and parses sim_result.log to provide immediate PASS/FAIL analysis for hardware verification.

Why does my Verilator simulation fail to find the msys_root environment path?

Verilator simulation fails to find the msys_root path when .claude/env_info.json is missing or misconfigured. This file is strictly required to locate msys_root and msystem for executing the RISC-V sim binaries.