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: 
Highlighted
Adventurer
Adventurer
174 Views
Registered: ‎09-14-2018

no ports update in .xml file after re-packaging custom IP

Jump to solution

I tried to re-package custom IP (File -> IP -> Open IP-XACT File…). I expected that the component.xml file would have the updated port list, but it still has the old ports. Any suggestions?

I do not want to delete the IP from IP catalog and create another IP from scratch, as I need to replace the old IP symbol on BD with a new one nicely.

Thank you

0 Kudos
1 Solution

Accepted Solutions
Xilinx Employee
Xilinx Employee
112 Views
Registered: ‎03-29-2013

Re: no ports update in .xml file after re-packaging custom IP

Jump to solution

Did you refresh the IP catalog – after repackaging the IP?

It is possible that the component.xml was already updated, but you may be referencing the old pointer in the IP repo.

Also, is this a new issue with 2018.3 ?

0 Kudos
4 Replies
Xilinx Employee
Xilinx Employee
143 Views
Registered: ‎03-29-2013

Re: no ports update in .xml file after re-packaging custom IP

Jump to solution

Which Vivado release are you using?

0 Kudos
Adventurer
Adventurer
138 Views
Registered: ‎09-14-2018

Re: no ports update in .xml file after re-packaging custom IP

Jump to solution

Vivado v2018.3 (64-bit)

0 Kudos
Xilinx Employee
Xilinx Employee
113 Views
Registered: ‎03-29-2013

Re: no ports update in .xml file after re-packaging custom IP

Jump to solution

Did you refresh the IP catalog – after repackaging the IP?

It is possible that the component.xml was already updated, but you may be referencing the old pointer in the IP repo.

Also, is this a new issue with 2018.3 ?

0 Kudos
Adventurer
Adventurer
94 Views
Registered: ‎09-14-2018

Re: no ports update in .xml file after re-packaging custom IP

Jump to solution

I did refresh the IP catalog after repackaging, but it is the first time (I am relatively a new Vivado user) the ports have been affected. Actually, the file component.xml has not been updated. I though it should, correct?
I am not aware of all issues with 2018.3, but I had troubles in a past to upgrade the IPs from 2017.2.

0 Kudos