RTL simulation examples
Run checked-in multi-file Verilog and SystemVerilog projects using file lists, including the multifile project, polyglot example, and Nova SoC example.
VIKAS is an open-source EDA tool by Sairam Ginnela: a Rust CLI and TypeScript workbench for selected Verilog and SystemVerilog RTL simulation, hardware-design checks, and VCD waveform workflows. Explore the source, download a CLI release, try the examples, or contribute.
If you are searching for the VIKAS EDA tool by Ginnela Sairam, this page is the project home for an open-source hardware-design toolkit covering selected RTL simulation, Verilog and SystemVerilog examples, static checks, and waveforms. VIKAS brings together a native CLI and a browser-based workbench backed by a Node.js server. It is an evolving open-source EDA project: review its repository and release notes to understand what is implemented today, then test the workflows with your own designs and toolchain. GitHub currently shows a v3.1.0 release tag while the README and source metadata still identify 3.0.0, so check the release notes and artifacts before selecting a build.
Run checked-in multi-file Verilog and SystemVerilog projects using file lists, including the multifile project, polyglot example, and Nova SoC example.
Explore project-specific latch, CDC, FSM, and signoff reporting commands. These checks are useful to evaluate, but are not a substitute for complete standards compliance or formal verification.
Inspect the project's binary VWF and VWM waveform formats and VCD interchange. Format support is backed by repository examples and round-trip tests.
Use a native Rust command-line app for supported workflows, or run the TypeScript/React workbench with its Node.js server for interactive project exploration.
These example commands are taken from the project README. Build the CLI first and run commands from the repository root; the checked-in examples make it easier to reproduce a first simulation or inspect a specific static-check workflow.
cargo build --release --locked --offline
./target/release/vikas run examples/multifile_proj/project.f
./target/release/vikas latch examples/demo_latch_trap.sv
./target/release/vikas cdc examples/demo_cdc.sv
./target/release/vikas fsm examples/demo_fsm_uart.sv
These are project-specific static checks; inspect the reports and source rather than treating them as formal proof.
npm install
npm run dev
The web workbench requires Node.js 18 or newer and its Node.js server; it is not a static GitHub Pages app.
The repository is open for engineers, independent developers, students, educators, researchers, and teams investigating RTL and hardware-design tooling. Fabless and semiconductor companies can review the implementation and examples as an exploratory project; suitability for a specific design flow must be established through their own technical evaluation. Contributors can help by reproducing issues, improving tests and documentation, or proposing focused changes through the project's contribution process.
Build from source, review the Rust workspace and TypeScript workbench, run CI-style examples, and follow the contribution guide before opening a change.
Use the checked-in examples to inspect software-based RTL and waveform workflows. Treat the results as learning and evaluation material, not proof of chip correctness.
Inspect the code, documented experiments, and citation metadata. Separate reproducible software behavior from analytical scenarios that are not independently validated physical models.
Assess the implemented features against your own requirements and trusted tool flows before adopting any output in a production or signoff process.
The README and beginner guide list the current prerequisites and exact commands. Prebuilt CLI releases are provided for Linux x86_64 and Apple Silicon macOS; building from source uses the repository's Rust workspace and vendored dependencies. The web workbench needs Node.js and its server, so it is not a static GitHub Pages application.
Install Rust/Cargo 1.70 or newer and a C++20 compiler, clone the repository, then run the documented locked offline build. Check the README for platform-specific release binaries.
cargo build --release --locked --offline
./target/release/vikas version
./target/release/vikas run examples/nova_soc/nova.f --max-ns 8000
Use Node.js 18 or newer, install the project dependencies, and start the local development server. A Codespaces configuration is also documented in the repository.
Choose the published command-line archive for your supported platform. These are CLI downloads; the TypeScript web workbench is not included in the release archives. Review the release page for installation instructions and the latest assets.
Check version notes: GitHub's latest release is tagged v3.1.0, while its release description and the repository README identify the CLI binaries as 3.0.0. Verify the release notes and archive contents before use.
VIKAS describes itself as a selected-workflow simulation and EDA project. Its own documentation explicitly says the static checks are project-specific heuristics, not complete IEEE language compliance or formal proof. Analytical physics and architectural scenarios are software-model outputs, not foundry-calibrated data, silicon measurements, or independently reproduced benchmarks.
Not a production signoff guarantee: validate outputs independently against your design requirements and qualified tools. Do not treat example execution, benchmark-like values, or exploratory models as proof of hardware feasibility, manufacturing readiness, or tapeout qualification.
Version transparency: at the time this page was reviewed, GitHub's latest release tag was v3.1.0, but the README and source metadata still reported 3.0.0. Review the release notes and repository before relying on version-specific claims.
VIKAS is dual-licensed under MIT OR Apache-2.0, at your option, with third-party components retaining their own license terms. Read the contribution and conduct guides, check existing issues, and include a small reproducible example when reporting a problem. The project also publishes a software-paper draft and citation metadata for researchers and educators who want to reference the work.
No. The project describes selected RTL workflows and explicitly does not claim complete IEEE language compliance, formal equivalence, or tapeout qualification.
No. The TypeScript workbench needs its Node.js server. Follow the repository setup guide or use the documented Codespaces workflow.
The README documents Linux x86_64 and Apple Silicon macOS builds. Check the latest release page for the current assets and release notes.
Read the contribution guide, run the relevant checks, and submit a focused pull request or a reproducible issue through GitHub.