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# 66982

2016.3 Vivado IP Flows - The Customization GUI of IP offer connection(s) to board components that have already been used in a project


In a project that uses the board flow, I can drag and drop components from the Board Tab on to the canvas. This instantiates the IP and then connects its interface to the right component on the board.

If I instantiate another instance of an IP that can connect to the same component on the board, the IP customization GUI will still show these components as valid options.

For example:

I have a project with a MicroBlaze design for the KCU105 board. This design uses the following components on the board:

  • the 300 MHz differential clock
  • the Reset
  • the LEDs
  • the UART

A MIG and a GPIO core are also present in the Board Design (BD). All these components are hooked up using the board interface tab. 

However, I can still instantiate another instance of these IPs and by double clicking on the IP, I can re-use the already used interfaces.

Is this expected behavior? I cannot drag and drop an interface from the BI tab multiple times, so I would not expect to be allowed to do this through the IP customization window either.


Once an interface is used, the IP customization GUI should not offer it as a valid choice anymore.

This will be fixed in a future Vivado release, so that when IP cores are added to a block design and those IP are customized on the canvas, the IP customization GUIs will not allow a connection to an already used resource.

AR# 66982
Date Created 04/06/2016
Last Updated 10/13/2016
Status Active
Type General Article
  • Vivado Design Suite - 2015.4
  • Vivado Design Suite - 2016.1
  • Vivado Design Suite - 2016.2
  • Vivado Design Suite - 2016.3