This script runs the VTR flow for a single benchmark circuit and architecture file.
The script is located at:
At a minimum
run_vtr_flow.py requires two command-line arguments:
run_vtr_flow.py <circuit_file> <architecture_file>
<circuit_file>is the circuit to be processed
<architecture_file>is the target FPGA architecture
The script will create a
./temp directory, unless otherwise specified with the
The circuit file and architecture file will be copied to the temporary directory.
All stages of the flow will be run within this directory.
Several intermediate files will be generated and deleted upon completion.
Users should ensure that no important files are kept in this directory as they may be deleted.
The standard out of the script will produce a single line with the format:
If execution completed successfully the status will be ‘OK’. Otherwise, the status will indicate which stage of execution failed.
The script will also produce an output files (*.out) for each stage, containing the standout output of the executable(s).
Additional optional command arguments can also be passed to
run_vtr_flow.py <circuit_file> <architecture_file> [<options>] [<vpr_options>]
<options>are additional arguments passed to
<vpr_options>are any arguments not recognized by
run_vtr_flow.py. These will be forwarded to VPR.
run_vtr_flow.py my_circuit.v my_arch.xml -track_memory_usage --pack --place
will run the VTR flow to map the circuit
my_circuit.v onto the architecture
my_arch.xml; the arguments
--place will be passed to VPR (since they are unrecognized arguments to
They will cause VPR to perform only packing and placement.
Detailed Command-line Options¶
Any options not recognized by this script is forwarded to VPR.
Start the VTR flow at the specified stage.
End the VTR flow at the specified stage.
Delete intermediate files (i.e.
Delete result files (i.e. VPR’s
Record peak memory usage and additional statistics for each stage.
/usr/bin/time -vcommand. Some operating systems do not report peak memory.
Kill benchmark if it is taking up too much memory to avoid slow disk swaps.
Maximum amount of time to spend on a single stage of a task in seconds.
Default: 14 days
Temporary directory used for execution and intermediate files. The script will automatically create this directory if necessary.
Run the flow with valgrind while using the following valgrind options:
Tells ODIN II the minimum multiplier size that should be implemented using hard multiplier (if available). Smaller multipliers will be implemented using soft logic.
Tells ODIN II the minimum adder size that should be implemented using hard adders (if available). Smaller adders will be implemented using soft logic.
Tells ODIN II to connect the first cin in an adder/subtractor chain to a global gnd/vdd net. Instead of creating a dummy adder to generate the input signal of the first cin port of the chain.
Tells VTR flow to use a custom ODIN II configuration value. The default behavior is to use the vtr_flow/misc/basic_odin_config_split.xml. Instead, an alternative config file might be supplied; compare the default and vtr_flow/misc/custom_odin_config_no_mults.xml for usage scenarios. This option is needed for running the entire VTR flow with additional parameters for ODIN II that are provided from within the .xml file.