Vivado IP Integrator Differences – Creating Wrappers - Vivado IP Integrator Differences – Creating Wrappers - 2.3 English - XAPP1335

Isolation Design Flow for Zynq UltraScale+ MPSoCs and UltraScale+ FPGAs (XAPP1335)

Document_ID
XAPP1335
Release_Date
2026-08-04
Revision
2.3 English

The Vivado Design Suite IP integrator is fully compatible with the IDF. In some cases, it even makes it easier, such as having the ability to add hierarchy with a single click/command.

There is one feature to be mindful of when creating isolated designs in the IP integrator. To preserve the IP being instantiated, the IP integrator automatically adds the DONT_TOUCH property to all instances of IP. This is good because it adds the IP vendors’ IP without modification. However, this impacts the feature of the IDF where isolated nets can drive multiple isolated regions. In this case, the Vivado tools attempts to split that net to follow the IDF rules but is prevented from doing so due to the DONT_TOUCH attribute. Thus, if an IP is marked as an isolated module, that IP must be wrapped with a level of hierarchy that does not have the DONT_TOUCH attribute. In such cases, follow the Vivado Design Suite User Guide: Implementation (UG904) to add a level of hierarchy to a module (a right-click operation).