mirrors/sby
3
0
Fork 0
mirror of https://github.com/YosysHQ/sby.git synced 2025-04-05 22:14:08 +00:00
Code Activity

Improve docs

Browse source
This commit is contained in:
Clifford Wolf 2017-01-30 12:15:12 +01:00
parent 9064f7e6f6
commit 8aaf40d54c
1 changed files with 6 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
docs/source/quickstart.rst
View file

@ -70,7 +70,9 @@ fail because the output directory ``demo/`` already exists.)
Time for a simple exercise: Modify the design so that the property is false
and the offending state is reachable within 100 cycles. Re-run ``sby`` with
the modified design and see if the proof now fails.
the modified design and see if the proof now fails. Inspect the counter example
trace (``.vcd`` file) produced by ``sby``. (`GTKWave <http://gtkwave.sourceforge.net/>`_
is an open source VCD viewer that you can use.)
Selecting the right engine
--------------------------
@ -82,7 +84,7 @@ returned by the first engine to finish is the result returned by SymbiYosys.)
Each engine has its strengths and weaknesses. Therefore it is important to
select the right engine for each project. The documentation for the individual
engines can provide some guidance for engine selection. (Trial and error can
also be a useful method for engine selection.)
also be a useful method for evaluating engines.)
Let's consider the following example:
@ -108,7 +110,8 @@ permissively licensed solver Z3 instead. Z3 is the default solver when no
Exercise: The engine ``abc bmc3`` does not provide abstract memory models.
Therefore SymbiYosys has to synthesize the memories in the example to FFs
and address logic. How does the performance of this project change if
``abc bmc3`` is used as engine instead of ``smtbmc -s boolector``?
``abc bmc3`` is used as engine instead of ``smtbmc -s boolector``? How fast
can either engine verify the design when the bug has been fixed?
Beyond bounded model checks
---------------------------