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

Description

After a 14.1 PlanAhead project containing a DDS Compiler core has been imported in the Vivado 2012.2 tool, the generated instantiation template for the DDS Compiler core is completely different.

The following steps are used:

Import the PlanAhead project into Vivado.

Select the IP Sources tab in Sources View.

Open the "DDS_coregen_ip" Instantiation Template and note how the template is being exported.

Close the DDS core Instantiation template.

Now generate the DDS IP core again from the Sources View.

Switch back to the IP Sources tab and open the "DDS_coregen_ip" Instantiation Template.It can now be observed that the template is completely different from what is being exported or generated by the CORE Generator tool. The number of ports and the names of the ports in the instantiation template are very different.

If the project is now closed and re-opened, the following message occurs and the core is removed from the project:

When attempting to add the xci file back in to the project, a similar message appears.

The .xco file can be added.

Solution

This core is incorrectly being converted to a native Vivado IP during project migration.

The instantiation templates delivered are different because the original is generated by the CORE Generator tool with the ISE version of the core and the subsequent generation is done with the Vivado IP flow using the Native Vivado version of the core.

The original core should have been added to the project as it was without the core being reset or re-generated unless the user specifically upgraded to the newer version.

To work around this issue, the following two files should be deleted from the project before opening it in the Vivado tool:

The Vivado 2012.3 tool has been enhanced to prevent an IP core from being changed in this way.

However, if you have already attempted a conversion and are seeing this issue, you will still need to delete the above two files before opening the design in the Vivado tool to see the correct results.