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!

AR# 70080

2017.2 Vivado IP Flows - Upgrade Selected silently fails after changing the project target device


I have a block design (BD) that is in active development.

After changing the part in the project, the IP in the BD are locked.

The locked status is expected and I attempted to upgrade the IP by running "report_ip_status" and then clicking on the "Upgrade Selected" button. 

However, clicking on the "Upgrade Selected" button did nothing as far as I could tell. 

There were no messages and the IP in the BD is still locked.


This issue will happen in Vivado 2017.1 and 2017.2 if an IP instance was added to the BD after the last time the BD was saved and before the project part was changed.

The code handling for report_ip_status "Upgrade Selected" sets up a list of IP core files and passes that on to the Upgrade IP function. 

However, in this situation, the BD cell does not yet have an XCI file on disk so it is not added to the list.

A work-around is to save the BD first, and then upgrade the IP.

This issue is fixed in Vivado 2017.3.

AR# 70080
Date 12/04/2017
Status Active
Type General Article
  • Vivado Design Suite - 2017.2
  • Vivado Design Suite - 2017.1
Page Bookmarked