The Test Vector feature supports both combinational and sequential circuit testing. By default, tests are combinational: the circuit is reset before each test, ensuring each test is independent.
For sequential circuits, you can specify test sequences using the special
<set> and <seq> header columns:
<seq> value within each <set>. Tests with <seq> of 0
or missing are treated as combinational (circuit resets between tests, even if they share
the same set).Here is an example of a sequential test vector:
# Sequential test for a counter Clock Reset Count <set> <seq> 0 0 0 1 1 1 0 0 1 2 0 0 1 1 3 1 0 1 1 4 0 0 2 1 5 1 0 2 1 6 0 1 0 2 1
In this example, the first six tests all have <set> 1 with <seq>
values 1-6, so they form one sequence that runs in order (seq 1, then 2, then 3, etc.)
without resetting between steps. The last test has <set> 2, so it starts
a new sequence and the circuit is reset before it runs.
Note also that Clock could be an input pin here. But it could also be a labeled clock component (see below).
<set> number (> 0) belong to the same sequence.<seq> value (seq 1, then 2, then 3, etc.)<set> number)<seq> = 0 or missing must also have <set> = 0 or missing and are always combinational (reset between tests)In a sequential test, the first step begins with a reset. In every step after the first, it begins with a simulation tick. Any Clock components in the simulation will be updated by that tick and their signals will be propagated along with any input pin values for that step. You may add a column to the test to show the ticks. The column will be checked against the clock in the circuit as if it were an output pin to verify it describes the clocks behavior. Here is an example for a simple positive edge-triggered D flip-flop test with a standard clock:
<clk> D Q NotQ <set> <seq> 0 0 0 1 1 1 1 0 0 1 1 2 0 1 0 1 1 3 1 1 1 0 1 4 0 1 1 0 1 5 1 1 1 0 1 6 0 0 1 0 1 7
The <clk> header is a special name for an unlabeled clock component. You may also label the clock and use the label as the column header (see earlier example).
We recommend that when using a Clock, you should not change the values of memory inputs during the same step that the clock makes a triggering transition. Doing so may allow an input signal to reach the component at near the same time as the clock signal giving surprising behavior. In the example above, the D input does not change in steps with a rising edge of the clock.
Here is a complete example combining all features:
# Mixed combinational and sequential tests A B C Out <clk> <set> <seq> 0 0 0 0 0 0 0 0 0 1 1 0 0 0 1 1 0 1 0 1 1 0 1 0 0 1 1 2 1 1 1 1 0 1 3 0 0 0 <DC> 0 2 1 1 0 1 <float> 1 2 2
In this example:
<DC> for the output, so any output value passes.<float> for the output, expecting a floating value.Thus the execution might look like this:
Previous: Special Values | Next: Command Line Usage.