Skip to content
STIMSMITH

Design and Application of a Co-Simulation Framework for Chisel

Paper
First seen 8/7/2026
Last seen 8/7/2026
Evidence 15 chunks

NEIGHBORHOOD

No graph connections found for this entity yet. It may appear in future ingestion runs.

explore full graph →

RELATIONSHIPS

35 connections
FPGA Emulation mentions → 85% 2e
The paper discusses FPGA emulation as used by other co-simulation frameworks.
RoCC Interface uses → 95% 2e
CFC targets RoCC-based accelerators for co-simulation.
FireSim compares with → 90% 2e
The paper compares CFC with FireSim as an existing co-simulation framework.
Co-Simulation Framework for Chisel (CFC) introduces → 100% 2e
The paper introduces CFC as its primary contribution.
CFC uses named pipes for IPC between simulations.
Binary Caching uses → 100% 2e
CFC introduces binary caching as an optimization to speed up test runs.
Rocket Chip uses → 90% 2e
CFC targets Rocket Chip-based designs and must handle Rocket Chip's Diplomacy and parameter system.
Out-of-Context Elaboration uses → 100% 2e
CFC uses out-of-context elaboration to test accelerators without a full SoC.
Co-simulation uses → 100% 2e
The paper uses co-simulation as its central verification technique.
spike uses → 95% 1e
CFC uses Spike as the software model for co-simulation.
Protocol Buffers (protobufs) uses → 100% 1e
CFC uses Protocol Buffers for inter-simulation communication.
Diplomacy Parameter Negotiation uses → 95% 1e
CFC must handle Diplomacy parameter negotiation for out-of-context elaboration.
RISC-V ISA uses → 90% 1e
CFC targets RISC-V based systems and uses Spike as RISC-V ISA simulator.
ChiselTest uses → 100% 1e
CFC is designed to work within a ChiselTest testing environment.
Chipyard uses → 90% 1e
CFC targets the Chipyard environment for accelerator testing.
Chisel uses → 100% 1e
CFC is built for Chisel-based hardware designs.
Mixed-Abstraction Verification mentions → 90% 1e
The paper describes mixed-abstraction verification as a category of co-simulation that CFC falls under.
Tandem Simulation mentions → 85% 1e
The paper distinguishes co-simulation from tandem simulation when discussing Dromajo.
ProtoToBundle introduces → 95% 1e
The paper introduces ProtoToBundle as a key utility in CFC.
BundleToProto introduces → 95% 1e
The paper introduces BundleToProto as a utility to convert hardware bundles to protobuf messages.
BundleToJson introduces → 95% 1e
The paper introduces BundleToJson as a helper for bundle-to-protobuf conversion.
PipeDriver introduces → 95% 1e
The paper introduces PipeDriver as a named pipe connector that drives data into DUTs.
PipeMonitor introduces → 95% 1e
The paper introduces PipeMonitor as a named pipe connector that monitors DUT outputs.
getVerifParameters introduces → 95% 1e
The paper introduces getVerifParameters as a utility for generating diplomatic parameters.
VerifRoCCStandaloneWrapper introduces → 95% 1e
The paper introduces VerifRoCCStandaloneWrapper for out-of-context elaboration of RoCC components.
Ryan Lund authored by → 100% 1e
Ryan Lund is the author of the paper.
CosimTester Trait introduces → 85% 1e
The paper introduces the CosimTester Trait as part of the co-simulation manager.
University of California, Berkeley authored by → 100% 1e
The paper was produced at the University of California, Berkeley.
University of California, Berkeley published by → 100% 1e
The paper is a technical report published by UC Berkeley.
Gemmini evaluates → 100% 1e
The paper demonstrates CFC by testing it on Gemmini.
Dromajo compares with → 90% 1e
The paper discusses Dromajo as an existing open-source co-simulation framework and contrasts it with CFC.
HDL Verifier compares with → 85% 1e
The paper discusses HDL Verifier as a commercial co-simulation framework and contrasts it with CFC.
Vitis HLS compares with → 85% 1e
The paper discusses Vitis HLS as a commercial co-simulation tool and contrasts it with CFC.
ISim compares with → 85% 1e
The paper discusses ISim as a commercial co-simulation tool and contrasts it with CFC.
pre-silicon verification mentions → 100% 1e
The paper discusses pre-silicon verification as the motivation for CFC.