Behavioral simulation and validation
------------------------------------
 
A behavioral description without simulation patterns is useless. In order
to see if the behavior you have just written is correct, you must
write simulation patterns and use the asimut simulator function.
 
Simulation patterns are contained in a plain text file, addaccu.pat.
For more informations about the pat format you can read the appropriate
on-line man or read the printed documentation.
 
To get acquainted with addaccu.pat, please issue the following
command:
 
> vi addaccu.pat
 
There are several interesting things here. First, you can recognize the
circuit interface again. Second, you can see that output terminals are
now located at the end of the interface. Ordering terminals is very
important for .pat files. The order you use to specify terminals greatly
influences the way you will have to write simulation patterns.
It is important to notice that simulation patterns contain both
input and output values. The behavior must be checked using these values.
Comments are prefixed by a '#', and are of much interest here.
 
Once you have understood the structure of this file, you are able
to simulate the previous behavioral description.
 
In order to simulate, please type:
 
> asimut -b addaccu addaccu result1 
 
The following figure describes asimut arguments.
addaccu.vbe is the behavioral description.
addaccu.pat is the original pattern file.
result1.pat is the resulting computed pattern file.
 
> asimut -b addaccu addaccu result1 
         |  |        |      |     
         |  |        |      |    
         |  |        |      -----------  name of the resulting pattern file
         |  |        ------------------  name of the original pattern file
         |  ---------------------------  name of the behavioral view
         ------------------------------  behavioral file option
 
Feel free to add new simulation vectors, as it's a very good practise. You
can also write obviously wrong patterns to see how asimut behaves when it
encounters errors.

Press <return> to continue.
