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: docs/advanced/vitis_accelerator.rst
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,18 +38,17 @@ Build workflow
38
38
39
39
At the call of the ``build`` method, the following option affect the build process:
40
40
41
-
* ``reset``: If True, clears files generated during previous build processes (STILL BEING TESTED).
42
-
* ``csim``: If True, builds the project for Vitis' software emulation validation flow (STILL BEING TESTED)
43
-
* ``synth``: If True, runs `make hls`, building object files for the kernel (STILL BEING TESTED)
44
-
* ``cosim``: If True, builds the project for Vitis' hardware emulation validation flow (STILL BEING TESTED)
45
-
* ``vsynth``: If True, runs `make xclbin`, building the .xclbin binary executable for the kernel (STILL BEING TESTED)
46
-
* ``debug``: If True, compiles the c++ host code and the HLS in debug mode (STILL BEING TESTED)
41
+
* ``reset``: If True, clears files generated during previous build processes (Equivalent to ``make clean`` in build folder).
42
+
* ``target``: Can be one of ``hw``, ``hw_emu``, ``sw_emu``, to define which build target to use (Default is ``hw``).
43
+
* ``debug``: If True, compiles the c++ host code and the HLS in debug mode.
47
44
48
45
Once the project is generated, it possible to run manually the build steps by using one of the following ``make`` targets in the generated project directory:
49
46
50
47
* ``host``: Compiles the host application.
51
48
* ``hls``: Produces only the kernel's object file.
52
49
* ``xclbin``: Produces only the kernel's .xclbin file.
50
+
* ``clean``: Removes all generated files.
51
+
* ``run``: Run the host application using the .xclbin file and the input data present in ``tb_data/tb_input_features.dat``.
53
52
54
53
It is also possible to run the full build process by calling ``make`` without any target. Modifications to the ``accelerator_card.cfg`` file can be done manually before running the build process (e.g., to change the clock period, or add addition ``.xo`` kernel to the build).
0 commit comments