OpenFPGA/tutorials/fpga_flow/how2use.md

83 lines
4.1 KiB
Markdown
Raw Normal View History

2019-07-10 11:03:30 -05:00
# FPGA flow
2019-07-10 11:03:30 -05:00
This tutorial will help the user to understand how to use OpenFPGA flow.<br />
2019-07-10 12:00:36 -05:00
During this tutorial we consider the user start in the OpenFPGA folder and we'll use tips and informations provided in [tutorial index](https://github.com/LNIS-Projects/OpenFPGA/blob/documentation/tutorials/tutorial_index.md#tips-and-informations). Details on how the folder is organized are available [here](https://github.com/LNIS-Projects/OpenFPGA/blob/documentation/tutorials/fpga_flow/folder_organization.md).
2019-07-10 11:03:30 -05:00
## Running fpga_flow.pl
2019-07-10 11:03:30 -05:00
A script example can be found at OPENFPGAPATHKEYWORD/fpga_flow/tuto_fpga_flow.sh.
2019-07-10 11:37:05 -05:00
### Experiment
2019-07-10 11:03:30 -05:00
cd fpga_flow<br />
./tuto_fpga_flow.sh<br />
2019-07-10 11:37:05 -05:00
### Explanation
2019-07-10 11:03:30 -05:00
By running this script we took an architecture description file, generated its netlist, generated a bitstream to implement a benchmark on it and verified this implementation.<br />
When you open this file you can see that 2 scripts are called. The first one is **rewrite_path_in_file.pl** which allow us to make this tutorial generic by generating full path to dependancies.<br />
2019-07-10 12:00:36 -05:00
The second one is **fpga_flow.pl**. This script launch OpenFPGA flow and can be used with a lot of [options](https://github.com/LNIS-Projects/OpenFPGA/blob/documentation/tutorials/fpga_flow/options.md). In this example we activated all FPGA-Verilog options
2019-07-10 11:03:30 -05:00
2019-07-09 15:28:14 -05:00
*Any script provides help if launch without argument*
fpga_flow.pl has dependencies which need to be configured. They are:
* configuration file, which provides dependencies path and flow type
* benchmark list file
2019-07-10 11:03:30 -05:00
## Configuration file
2019-07-08 11:36:58 -05:00
In this file paths have to be full path. Relative path could lead to errors.<br />
The file is organized in 3 parts:
2019-07-08 17:18:08 -05:00
* **dir_path**: provides all the tools and repository path
* **flow_conf**: provides information on how the flow run
* **csv_tags**: *to complete*
While empty the file is as follow:
2019-07-08 11:36:58 -05:00
[dir_path]<br />
script_base = OPENFPGAPATHKEYWORD/fpga_flow/scripts<br />
benchmark_dir = *<Path to the folder containing all sources of the design>*<br />
2019-07-08 11:36:58 -05:00
yosys_path = OPENFPGAPATHKEYWORD/yosys<br />
odin2_path = not_used<br />
cirkit_path = not_used<br />
abc_path = OPENFPGAPATHKEYWORD/abc<br />
abc_mccl_path = OPENFPGAPATHKEYWORD/abc<br />
abc_with_bb_support_path = OPENFPGAPATHKEYWORD/abc<br />
mpack1_path = not_used<br />
m2net_path = not_used<br />
mpack2_path = not_used<br />
vpr_path = OPENFPGAPATHKEYWORD/vpr7_x2p/vpr<br />
rpt_dir = *<wherever you want logs to be saved>*<br />
2019-07-08 11:36:58 -05:00
ace_path = OPENFPGAPATHKEYWORD/ace2<br />
[flow_conf]<br />
flow_type = yosys_vpr *to use verilog input*<br />
vpr_arch = *<wherever the architecture file is saved>*<br />
2019-07-08 11:36:58 -05:00
mpack1_abc_stdlib = DRLC7T_SiNWFET.genlib # Use relative path under ABC folder is OK<br />
m2net_conf = not_used<br />
mpack2_arch = not_used<br />
power_tech_xml = *<wherever the xml tech file is saved>*<br />
2019-07-08 11:36:58 -05:00
[csv_tags] *to complete*<br />
mpack1_tags = Global mapping efficiency:|efficiency:|occupancy wo buf:|efficiency wo buf:<br />
mpack2_tags = BLE Number:|BLE Fill Rate: <br />
vpr_tags = Netlist clb blocks:|Final critical path:|Total logic delay:|total net delay:|Total routing area:|Total used logic block area:|Total wirelength:|Packing took|Placement took|Routing took|Average net density:|Median net density:|Recommend no. of clock cycles:<br />
vpr_power_tags = PB Types|Routing|Switch Box|Connection Box|Primitives|Interc Structures|lut6|ff<br />
*An example of this file can be found at OPENFPGAPATHKEYWORD/fpga_flow/configs/tutorial/tuto.conf*
2019-07-10 11:03:30 -05:00
## Benchmark list
The benchmark folder contains 3 sub-folders:
2019-07-08 17:18:08 -05:00
* **Blif**: contains .blif and .act of benchmarks
* **List**: contains all benchmark list files
* **Verilog**: contains Verilog designs
2019-07-09 15:28:14 -05:00
Blif and Verilog folders are organized by folders with the name of projects. **Folder, top module and top module file must share the same name.**<br />
The benchmark list file can contain as many benchmarks as available in the same folder targetted by "benchmark_dir" variable from the configuration file. It's written as:<br />
top_module/*.v,<int_value>; where <int_value> is the number of channel/wire between each block.
*An example of this file can be found at OPENFPGAPATHKEYWORD/fpga_flow/benchmarks/List/tuto_benchmark.txt*