cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
puya
Contributor
Contributor
538 Views
Registered: ‎11-20-2018

config_vitis does not exist

Jump to solution

Hi,

In the vitis documentation and vivado_hls 2019.2 , it is mentioned that config_vitis is a valid TCL command but I get error when using that and should revert it to config_sdx.

Could you please check it? Is it my installation problem?

 

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
kmorris
Xilinx Employee
Xilinx Employee
425 Views
Registered: ‎01-11-2011

Hi @puya, thank you for the information. Please continue to use config_sdx for 2019.2. The config_vitis command is not correct for this flow, and we are working to correct this in the documentation.

-------------------------------------------------------------------------
Please don’t forget to reply, kudo, and accept as solution!
-------------------------------------------------------------------------

View solution in original post

3 Replies
kmorris
Xilinx Employee
Xilinx Employee
476 Views
Registered: ‎01-11-2011

Hi @puya, are you sourcing your own script when calling config_vitis? It would be better to understand the context of where the error is coming from. When looking into this, the bottom-up flow for vitis_hls uses:

config_flow -target vitis

If I can get more information about how you are running into the messaging I can examine it further.

-------------------------------------------------------------------------
Please don’t forget to reply, kudo, and accept as solution!
-------------------------------------------------------------------------
0 Kudos
puya
Contributor
Contributor
454 Views
Registered: ‎11-20-2018

@kmorris 

It is the script I used to use with SDAccel for compiling my HLS code to XO file. I sourced it with vivdo_hls -f script.tcl.

I got that in vitis things got changed and according to this page :

https://www.xilinx.com/html_docs/xilinx2019_2/vitis_doc/Chunk595166594.html#tvy1528754367816

I should be able to do the same with vitis. it is my sample script for vitis:

# Define variables for your HLS kernel:
set projName "box_filter_proj"
set krnlName "hls_top"
set krnlFile "box_filter.cpp hls_top.cpp"
set solution "solution1"
set krnlTB "dummy_tb.cpp"
set krnlPlatform "xcu280-fsvh2892-2L-e"
set path "./xoFlow"

#Script to create and output HLS kernel
open_project $projName
set_top $krnlName
add_files $krnlFile
add_files -tb $krnlTB
open_solution $solution
set_part $krnlPlatform
create_clock -period 10 -name default
#config_vitis -optimization_level none -target xocc
config_sdx -optimization_level none -target xocc
config_export -vivado_optimization_level 0 -vivado_phys_opt none
config_compile -name_max_length 256 -pipeline_loops 64
config_schedule -enable_dsp_full_reg
#source "./hlsKernel/solution1/directives.tcl"
csim_design
csynth_design
cosim_design
export_design -rtl verilog -format ip_catalog -xo \
        $path/$krnlName.xo
exit

Should I replace config_vitis with config_sdx as before? It seems config_vitis is not defined in vivado_hls or vitis_hls binaries..

 

0 Kudos
kmorris
Xilinx Employee
Xilinx Employee
426 Views
Registered: ‎01-11-2011

Hi @puya, thank you for the information. Please continue to use config_sdx for 2019.2. The config_vitis command is not correct for this flow, and we are working to correct this in the documentation.

-------------------------------------------------------------------------
Please don’t forget to reply, kudo, and accept as solution!
-------------------------------------------------------------------------

View solution in original post