Simulation
The Simulation page runs a testbench with one of the simulators installed on the machine where your project is. The assistant runs its simulations with the same simulator.
Run a simulation
Section titled “Run a simulation”- Open the Simulation page.
- Choose a simulator from the simulator list. A simulator that Chipforge can’t use is marked Not found, Not usable or Not available on this OS.
- Choose the testbench.
- Under Sources, tick the files the simulation needs.
- Select Run Simulation. The simulator’s output streams into the page, and the run reports whether the testbench passed.
To stop a run, select Cancel.
The project’s simulator
Section titled “The project’s simulator”The simulator you choose is saved with the project, in chipforge/project.json, so it travels with the project folder. The assistant uses the same simulator unless you, or the plan, name a different one.
If you haven’t chosen one, Chipforge uses the Vivado simulator (xsim) if it can run on this machine, and otherwise another simulator that can.
If you open the project on a machine that doesn’t have its simulator, Chipforge runs with one that is installed and says so: This project uses …, which isn't available on this machine — running with … instead. The project’s choice isn’t changed.
Some simulators, such as Questa, Xcelium and VCS, need a licence. See Licences.
Results and waveforms
Section titled “Results and waveforms”Each simulation run gets its own folder under chipforge/runs/ in your project, with its report, log and waveform together.
A run produces a waveform only if the testbench writes one, with $dumpfile and $dumpvars. The testbenches the assistant writes do. When the run finishes, open the Waveform tab to see it. See Waveforms.
To save space, Chipforge removes the oldest run folders that don’t hold a bitstream, simulation runs and their waveforms included. Copy a waveform somewhere else if you need to keep it.