Co-Simulation Framework for Chisel (CFC)
ToolFirst seen 8/7/2026
Last seen 8/7/2026
Evidence 14 chunks
NEIGHBORHOOD
No graph connections found for this entity yet. It may appear in future ingestion runs.
explore full graph →RELATIONSHIPS
26 connectionsCFC pairs an instruction-accurate software simulation with an RTL simulation, implementing mixed-abstraction verification.
CFC uses Protocol Buffers for inter-simulation communication.
CFC uses protobuf-to-bundle conversion to drive data into hardware DUTs.
CFC implements the co-simulation paradigm for Chisel-based hardware designs.
CFC introduces binary caching to avoid rebuilding simulation binaries between test runs.
The paper introduces CFC as its primary contribution.
CFC uses out-of-context elaboration to test accelerators independently from the full SoC.
CFC must handle Diplomacy parameter negotiation for out-of-context elaboration of RoCC components.
CFC is tested against Gemmini as a demonstration of its capabilities.
CFC targets the Chipyard environment for SoC-level testing.
CFC is designed to integrate with the Chipyard ecosystem.
ProtoToBundle is a component of CFC.
BundleToProto is a component of CFC.
BundleToJson is a component of CFC.
PipeDriver is a component of CFC.
PipeMonitor is a component of CFC.
getVerifParameters is a component of CFC.
VerifRoCCStandaloneWrapper is a component of CFC.
CosimTester Trait is a component of CFC's co-simulation manager.
CosimTestUtils.scala contains key CFC utility functions.
VerifRoCCStandalone.scala contains the implementation of VerifRoCCStandaloneWrapper.
CFC uses bundle-to-protobuf conversion to monitor hardware outputs and send them to the software model.
CFC is described as an instruction-accurate co-simulation framework.
CFC relies on ChiselTest for threading and testbench utilities.
CFC uses Spike as the software model for RISC-V co-simulation.
CFC uses named pipes for IPC between the software and hardware simulations.