Introductory Examples for Vitis HLS

https://github.com/xilinx/vitis-hls-introductory-examples
Admin
A collection of C/C++ synthesizable examples for Vitis High-Level Synthesis (HLS), demonstrating...
Tokens:3,855
Snippets:49
Trust Score:9.3
License:Apache-2.0
Update:1 month ago
Show doc for...
Tokens:
Raw
### Run HLS Flow with Python Script

Source: https://github.com/xilinx/vitis-hls-introductory-examples/blob/master/DSP/fft/readme.md

Execute the Vitis HLS flow including simulation, synthesis, and cosimulation using the provided Python script. This is the recommended method for running the examples.

```bash
$ vitis --source run.py
```

--------------------------------

### Vitis Unified CLI for C Synthesis

Source: https://github.com/xilinx/vitis-hls-introductory-examples/blob/master/Migration/README.md

Compile HLS projects for C synthesis using the Vitis Unified Command Line Interface. Requires a configuration file and a working directory.

```bash
v++ --compile --mode hls --config <config_file> --work_dir <work_dir>
```

--------------------------------

### Vitis Unified CLI for C Simulation

Source: https://github.com/xilinx/vitis-hls-introductory-examples/blob/master/Migration/README.md

Perform C simulation for HLS projects using the Vitis Unified Command Line Interface. Requires a configuration file and a working directory.

```bash
vitis-run --mode hls --csim --config <config_file> --work_dir <work_dir>
```

--------------------------------

### Vitis Unified CLI for Co-Simulation

Source: https://github.com/xilinx/vitis-hls-introductory-examples/blob/master/Migration/README.md

Execute co-simulation for HLS projects using the Vitis Unified Command Line Interface. Requires a configuration file and a working directory.

```bash
vitis-run --mode hls --cosim --config <config_file> --work_dir <work_dir>
```

--------------------------------

### Run Vitis Unified Python Script

Source: https://github.com/xilinx/vitis-hls-introductory-examples/blob/master/Migration/README.md

Launch the Vitis Unified IDE using a Python script. Configuration can be embedded within the script or provided in a separate file.

```bash
vitis -s <python_script>
```

--------------------------------

### Run Vitis HLS with Tcl Script

Source: https://github.com/xilinx/vitis-hls-introductory-examples/blob/master/Migration/README.md

Execute HLS flow using a Tcl script. The `open_component` command replaces `open_project` and `open_solution`.

```bash
vitis-run --mode hls --tcl <tcl_script>
```

--------------------------------

### Run Python script for Vitis HLS

Source: https://github.com/xilinx/vitis-hls-introductory-examples/blob/master/README.md

Executes the Python script to run HLS processes. Open the created directory 'w' as a workspace in the Vitis Unified IDE after execution.

```bash
vitis -s run.py
```

--------------------------------

### Open Vitis Component in IDE

Source: https://github.com/xilinx/vitis-hls-introductory-examples/blob/master/DSP/fft/readme.md

Open a specific Vitis HLS test case component in the Vitis Unified IDE after running the Python script. Replace '<testcase>' with the actual test case name.

```bash
$ vitis -w work_<testcase>
```

--------------------------------

### Run Tcl script for Vitis HLS

Source: https://github.com/xilinx/vitis-hls-introductory-examples/blob/master/README.md

Executes the Tcl script to run HLS processes. Open the directory containing run_hls.tcl as a workspace in the Vitis Unified IDE after execution.

```bash
vitis-run --mode hls --tcl run_hls.tcl
```

--------------------------------

### Run HLS Flow with Tcl Script

Source: https://github.com/xilinx/vitis-hls-introductory-examples/blob/master/DSP/fft/readme.md

Alternatively, run the Vitis HLS flow using the provided Tcl script. This command also creates a component that can be opened in the Vitis IDE.

```bash
$ vitis-run --mode hls --tcl run_hls.tcl
```

--------------------------------

### Extracting Throughput from Latency Reports

Source: https://github.com/xilinx/vitis-hls-introductory-examples/blob/master/DSP/fft/readme.md

Use this command to parse latency reports and extract throughput values for different FFT interface configurations. It filters for 'THROUGHPUT' and formats the output to show the interface type and its corresponding throughput.

```bash
$ find . -name lat.rpt | xargs grep -H THROUGHPUT | sed 's|\./\([^/]*\)/.*:\(.*\)|\1: \2|'
```
Tokens:
Raw