Driver
Related Doc:
package iotesters
Runs the ClassicTester and returns a Boolean indicating test success or failure
Runs the ClassicTester and returns a Boolean indicating test success or failure
This is the device under test.
The default backend is "firrtl" which uses the firrtl interperter. Other options "verilator" will use the verilator c++ simulation generator "vcs" will use the VCS simulation
Setting this to true will make the tester display information on peeks, pokes, steps, and expects. By default only failed expects will be printed
Set the random number generator seed
This is a test harness subclassing PeekPokeTester for dutGen,
This will be true if all tests in the testerGen pass
val testsPassed = iotesters.Driver(() => new CircuitX, testerSeed = 0L, verbose = true) { circuitX => CircuitXTester(circuitX) }
This executes the test with options provide from an array of string -- typically provided from the command line
This executes the test with options provide from an array of string -- typically provided from the command line
A *main* style array of string options
The device to be tested, (device-under-test)
A peek-poke tester with test for the dey
Returns true if all tests in testerGen pass
This executes a test harness that extends peek-poke tester upon a device under test with an optionsManager to control all the options of the toolchain components
This executes a test harness that extends peek-poke tester upon a device under test with an optionsManager to control all the options of the toolchain components
The device under test, a subclass of a Chisel3 module
Use this to control options like which backend to use
A peek poke tester with tests for the dut
Returns true if all tests in testerGen pass
Start up the interpreter repl with the given circuit
To test a class X extends Module {}, add the following code to the end
of the file that defines
Start up the interpreter repl with the given circuit
To test a class X extends Module {}, add the following code to the end
of the file that defines
options from the command line
Module to run in interpreter
object XRepl { def main(args: Array[String]) { iotesters.Driver.executeFirrtlRepl(args, () => new X) } }
running main will place users in the repl with the circuit X loaded into the repl
Start up the interpreter repl with the given circuit
To test a class X extends Module {}, add the following code to the end
of the file that defines
Start up the interpreter repl with the given circuit
To test a class X extends Module {}, add the following code to the end
of the file that defines
Module to run in interpreter
options
object XRepl { def main(args: Array[String]) { val optionsManager = new ReplOptionsManager if(optionsManager.parse(args)) { iotesters.Driver.executeFirrtlRepl(() => new X, optionsManager) } }
running main will place users in the repl with the circuit X loaded into the repl
This is just here as command line way to see what the options are It will not successfully run TODO: Look into dynamic class loading as way to make this main useful
This is just here as command line way to see what the options are It will not successfully run TODO: Look into dynamic class loading as way to make this main useful
unused args
Runs the ClassicTester using the verilator backend without doing Verilator compilation and returns a Boolean indicating success or failure Requires the caller to supply path the already compile Verilator binary