BasicTester
Related Doc:
package testers
This must wrap the datatype used to set the io field of any Module.
This must wrap the datatype used to set the io field of any Module. i.e. All concrete modules must have defined io in this form: [lazy] val io[: io type] = IO(...[: io type])
Items in [] are optional.
The granted iodef WILL NOT be cloned (to allow for more seamless use of anonymous Bundles in the IO) and thus CANNOT have been bound to any logic. This will error if any node is bound (e.g. due to logic in a Bundle constructor, which is considered improper).
TODO(twigg): Specifically walk the Data definition to call out which nodes are problematic.
Desired name of this module.
Desired name of this module.
The finish method provides a hook that subclasses of BasicTester can use to alter a circuit after their constructor has been called.
The finish method provides a hook that subclasses of BasicTester can use to alter a circuit after their constructor has been called. For example, a specialized tester subclassing BasicTester could override finish in order to add flow control logic for a decoupled io port of a device under test
Signal name (for simulation).
Signal name (for simulation).
IO for this Module.
IO for this Module. At the Scala level (pre-FIRRTL transformations),
connections in and out of a Module may only go through io elements.
Legalized name of this module.
Legalized name of this module.
Ends the test reporting success.
Ends the test reporting success.
Does not fire when in reset (defined as the encapsulating Module's reset). If your definition of reset is not the encapsulating Module's reset, you will need to gate this externally.