Boot a simulation
Introduction
Below is an example hardware definition + testbench:
import spinal.core._
// Identity takes n bits in a and gives them back in z
class Identity(n: Int) extends Component {
val io = new Bundle {
val a = in Bits(n bits)
val z = out Bits(n bits)
}
io.z := io.a
}
import spinal.core.sim._
object TestIdentity extends App {
// Use the component with n = 3 bits as "dut" (device under test)
SimConfig.withWave.compile(new Identity(3)).doSim{ dut =>
// For each number from 3'b000 to 3'b111 included
for (a <- 0 to 7) {
// Apply input
dut.io.a #= a
// Wait for a simulation time unit
sleep(1)
// Read output
val z = dut.io.z.toInt
// Check result
assert(z == a, s"Got $z, expected $a")
}
}
}
Configuration
SimConfig
will return a default simulation configuration instance on which you can call multiple functions to configure your simulation:
Syntax |
Description |
---|---|
|
Enable simulation wave capture (default format) |
|
Enable simulation wave capture (VCD text format) |
|
Enable simulation wave capture (FST binary format) |
|
Specify the |
|
Enable all the RTL compilation optimizations to reduce simulation time (will increase compilation time) |
|
Change the folder where the sim files are generated |
|
Use Verilator as simulation backend (default) |
|
Use GHDL as simulation backend |
|
Use Icarus Verilog as simulation backend |
|
Use Synopsys VCS as simulation backend |
Then you can call the compile(rtl)
function to compile the hardware and warm up the simulator.
This function will return a SimCompiled
instance.
On this SimCompiled
instance you can run your simulation with the following functions:
doSim[(simName[, seed])]{dut => /* main stimulus code */}
Run the simulation until the main thread runs to completion and exits/returns. It will detect and report an error if the simulation gets fully stuck. As long as e.g. a clock is running the simulation can continue forever, it is therefore recommended to use
SimTimeout(cycles)
to limit the possible runtime.doSimUntilVoid[(simName[, seed])]{dut => ...}
Run the simulation until it is ended by calling either
simSuccess()
orsimFailure()
. The main stimulus thread can continue or exit early. As long as there are events to process, the simulation will continue. The simulation will report an error if it gets fully stuck.
The following testbench template will use the following toplevel :
class TopLevel extends Component {
val counter = out(Reg(UInt(8 bits)) init (0))
counter := counter + 1
}
Here is a template with many simulation configurations:
val spinalConfig = SpinalConfig(defaultClockDomainFrequency = FixedFrequency(10 MHz))
SimConfig
.withConfig(spinalConfig)
.withWave
.allOptimisation
.workspacePath("~/tmp")
.compile(new TopLevel)
.doSim { dut =>
SimTimeout(1000)
// Simulation code here
}
Here is a template where the simulation ends by completing the simulation main thread execution:
SimConfig.compile(new TopLevel).doSim { dut =>
SimTimeout(1000)
dut.clockDomain.forkStimulus(10)
dut.clockDomain.waitSamplingWhere(dut.counter.toInt == 20)
println("done")
}
Here is a template where the simulation ends by explicitly calling simSuccess():
SimConfig.compile(new TopLevel).doSimUntilVoid{ dut =>
SimTimeout(1000)
dut.clockDomain.forkStimulus(10)
fork {
dut.clockDomain.waitSamplingWhere(dut.counter.toInt == 20)
println("done")
simSuccess()
}
}
Note is it equivalent to:
SimConfig.compile(new TopLevel).doSim{ dut =>
SimTimeout(1000)
dut.clockDomain.forkStimulus(10)
fork {
dut.clockDomain.waitSamplingWhere(dut.counter.toInt == 20)
println("done")
simSuccess()
}
simThread.suspend() // Avoid the "doSim" completion
}
Note that by default, the simulation files will be placed into the simWorkspace/xxx
folders. You can override the simWorkspace location by setting the SPINALSIM_WORKSPACE
environnement variable.
Running multiple tests on the same hardware
val compiled = SimConfig.withWave.compile(new Dut)
compiled.doSim("testA") { dut =>
// Simulation code here
}
compiled.doSim("testB") { dut =>
// Simulation code here
}
Throw Success or Failure of the simulation from a thread
At any moment during a simulation you can call simSuccess
or simFailure
to end it.
It is possible to make a simulation fail when it is too long, for instance because the test-bench is waiting for a condition which never occurs. To do so, call SimTimeout(maxDuration)
where maxDuration
is the time (in simulation units of time) after the which the simulation should be considered to have failed.
For instance, to make the simulation fail after 1000 times the duration of a clock cycle:
val period = 10
dut.clockDomain.forkStimulus(period)
SimTimeout(1000 * period)