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

10.1/9.2i ChipScope Pro Core Inserter - Core Inserter does not open when I double-click the ".cdc" file in ISE


When I double-click the ".cdc" file in the sources pane in ISE ChipScope, Core Inserter does not open. What is the problem?


Work-Around 1

If an ISE project is created using the Core Inserter flow to insert ChipScope in 9.2i, there are two ways to work around this issue:

- Change the target device of the ISE project to a device in another family and subsequently change it back to the original target. Double-clicking the ".cdc" file will now open Core Inserter.

- Right-click the ".cdc" file and use the Open function in the menu.

This problem has been fixed in the latest 9.2i Service Pack available at:

The first service pack containing the fix is 9.2i Service Pack 4.

Work-Around 2

Alternatively, this might be an issue with a corrupt ISE project. If the above work-arounds do not help, set the following Environment variable and attempt again: XIL_PROJNAV_FLOW_DEBUG_LEVEL=99. If you see messages similar to these:

DEBUG (dpm_chSNEditOperationWithUpdate): processing Edit request for SourceDUNode

DEBUG (_GetListPropDefaultValue): The property PROP_DevFamily has a default value of an empty string.

DEBUG (_GetListPropDefaultValue): The property PROP_DevDevice has a default value of an empty string.

DEBUG (_GetListPropDefaultValue): The property PROP_DevPackage has a default value of an empty string.

DEBUG (_GetListPropDefaultValue): The property PROP_DevSpeed has a default value of an empty string.

Then, the issue is that your ".ise" file is corrupted. To work around the issue, you will need to delete the ISE project and associated ".prj" files and rebuild the project.

Work-Around 3

If you are using an EDIF flow, and the top level ".edf" file does not match the HDL top level file it was synthesized from, then that is the issue. Change the EDIF name to match the top level HDL file it was synthesized from and this issue should be resolved.

AR# 25281
Date 12/15/2012
Status Active
Type General Article