UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Participant bbharkhada
Participant
12,437 Views
Registered: ‎07-08-2014

Is it possible in Vivado to package a custom IP with relative paths for all rtl


Hi,

 

Is it possible to have all the rtl files in a separate directory structure and package the IP with relative path to all the files instead of absolute paths. I need to package multiple small designs into IPs which would eventually form multiple IPs (with relative paths to files) in IP repository that will be used across various designs. Can it be done ?

 

Thanks

Bharat

0 Kudos
3 Replies
Xilinx Employee
Xilinx Employee
12,429 Views
Registered: ‎10-24-2013

Re: Is it possible in Vivado to package a custom IP with relative paths for all rtl

Hi,
Please check if this helps.

http://www.xilinx.com/support/answers/56102.html
Thanks,Vijay
--------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.
0 Kudos
Xilinx Employee
Xilinx Employee
12,425 Views
Registered: ‎09-20-2012

Re: Is it possible in Vivado to package a custom IP with relative paths for all rtl

Hi Bharat,

 

The tool does use "relative" paths when you package a directory and if the RTL files are with in directory you are packaging.

 

Try packaging a directory with RTL and check the XML file created. You will find relative paths to RTL files here (paths will be relative to the directory you selected for packaging).

 

If the RTL files are outside the directory you are packaging then absolute location of files will be used and also you will encounter messages like below.

 

[IP_Flow 19-731] File Group 'xilinx_verilogsynthesis (Verilog Synthesis)': "C:/Users/vemulad/Desktop/my_run/gated_clock.v" file path is not relative to the IP root directory.

 

Thanks,

Deepika.

Thanks,
Deepika.
--------------------------------------------------------------------------------------------
Google your question before posting. If someone's post answers your question, mark the post as answer with "Accept as solution". If you see a particularly good and informative post, consider giving it Kudos (the star on the left)
0 Kudos
Participant bbharkhada
Participant
12,399 Views
Registered: ‎07-08-2014

Re: Is it possible in Vivado to package a custom IP with relative paths for all rtl

Hi Vijay, Deepika,

 

Thanks for the reply.

 

Vijay, I understand that modifying the .xci / .xml files is an option. I am trying to syntesize individual projects out of context and package that project as from under "tools menu -> create and package IP". Once the component .xml is generated I can modify it to use relative path and repackage the ip and regnerate the .zip file. this  zip file maintains the relative path mapping. But I was hoping that the tool would do the reative addressing itself as it does for Xilinx internal sources. if I look at any component.xml under the IP/xilinx directory under tool installation it has the path from any file from hdl/......v. It is not looking at absolute paths, I was hoping users can also do something like that by maybe setting a parameter which can specify the base path from where everything needs to be relative.

 

Deepika, When I package a directory, that directory as the ip_root_directory and puts the component.xml and xgui directory in that directory. If I select the archive location in a different place the archive includes the rtl. Hence it uses relative directory as it is the same directory.

 

I am trying to keep the source where they are and not package it in the archive. The sources should be referred by the path in the component.xml and should not be copied, thereby not creating duplicates of the RTL.

 

Thanks

Bharat

0 Kudos