You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/src/quickstart/index.rst
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,6 +48,12 @@ On most unix-like systems you can run:
48
48
49
49
> make
50
50
51
+
The default front-end for VTR is :ref:`Parmys<parmys>`, but you can build with ODIN II instead using the command below. This is required to run :ref:`Synthesizing with ODIN II<synthesizing_with_odin_ii>`.
52
+
53
+
.. code-block:: bash
54
+
55
+
> make CMAKE_PARAMS="-DWITH_ODIN=on"
56
+
51
57
from the VTR root directory (hereafter referred to as :term:`$VTR_ROOT`) to build VTR.
52
58
53
59
.. note::
@@ -63,6 +69,8 @@ from the VTR root directory (hereafter referred to as :term:`$VTR_ROOT`) to buil
63
69
* define VTR_ROOT as a variable in your shell (e.g. if ``~/trees/vtr`` is the path to the VTR source tree on your machine, run the equivalent of ``VTR_ROOT=~/trees/vtr`` in BASH) which will allow you to run the commands as written in this guide, or
64
70
* manually replace `$VTR_ROOT` in the example commands below with your path to the VTR source tree.
65
71
72
+
73
+
66
74
For more details on building VTR on various operating systems/platforms see :doc:`Building VTR</BUILDING>`.
67
75
68
76
@@ -235,6 +243,7 @@ Next we need to run the three main sets of tools:
235
243
* :ref:`ABC` performs 'logic optimization' which simplifies the circuit logic, and 'technology mapping' which converts logic equations into the Look-Up-Tables (LUTs) available on an FPGA, and
236
244
* :ref:`VPR` which performs packing, placement and routing of the circuit to implement it on the targetted FPGA architecture.
The subdirectory ``regression_tests/vtr_reg_basic`` contains tests that are to be run before each commit. They check for basic functionallity to make sure nothing was extremely out of order. This command runs the VTR flow on a set of circuits and a single architecture.
20
+
The subdirectory ``regression_tests/vtr_reg_basic`` contains tests that are to be run before each commit. They check for basic functionality to make sure nothing was extremely out of order. This command runs the VTR flow on a set of circuits and a single architecture.
21
21
The files generated from the run are stored in ``basic_no_timing/run[#]`` where ``[#]`` is the number of runs you have done.
22
-
If this is your first time running the flow, the results will be stored in basic_no_timing/run001.
23
-
When the script completes, enter the following command:
This parses out the information of the VTR run and outputs the results in a text file called ``run[#]/parse_results.txt``.
22
+
If this is your first time running the flow, the results will be stored in basic_no_timing/run001. The command parses out the information of the VTR run and outputs the results in a text file called ``run[#]/parse_results.txt``.
30
23
31
24
More info on how to run the flow on multiple circuits and architectures along with different options later.
32
25
Before that, we need to ensure that the run that you have done works.
Copy file name to clipboardExpand all lines: requirements.txt
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ psutil
4
4
5
5
# Python linter and formatter
6
6
click==8.0.2# Our version of black needs an older version of click (https://stackoverflow.com/questions/71673404/importerror-cannot-import-name-unicodefun-from-click)
"The number of placer non timing move probabilities should equal to the total number of supported moves. %d\n", PlacerOpts.place_static_notiming_move_prob.size());
57
+
"The number of placer non timing move probabilities (%d) should equal to or less than the total number of supported moves (%d).\n",
0 commit comments