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

6.1i CORE Generator - No CORE Generator cores are shown in the COREGen GUI or ISE Create Core Catalog (Waiting for core data from COREGen)


Keywords: manage, select, install, available, empty, missing

Urgency: Standard

General Description:
From the Project Navigator New Source Wizard or when CORE Generator opens in stand-alone mode, the cores are not displayed in the GUI box (it is empty).



A case sensitivity problem on PCs could cause this problem. If your $XILINX variable does not exactly match the case of your installation directory, CORE Generator will display zero cores.

If the XILINX environment variable does not exactly match the case of the DOS path, COREGen will not pick up the repositories correctly.

If the Xilinx ISE 6.1i tools are installed in the directory "C:\ISE6.1," setting the XILINX variable to "c:\ise6.1" or "c:\ISE6.1" will cause this problem.

A space after the Xilinx variable will also cause this problem.

After correcting the XILINX variable, delete the "coregen.prj" file in an existing project. Close and reopen Project Navigator, if Project Navigator is being used to call COREGen.


CORE Generator cores do not appear in the Project Navigator New Source Wizard if the project is opened with a network path designation.


An open project using the network path "//net/drive/projects/projectdir/my.npl" will not display CORE Generator cores. However, if the network path "//net/drive/projects" is mapped to a drive letter (e.g., G:), the project can be opened using the drive letter G:/projectdir/my.npl; all of the cores will appear correctly in the New Source Wizard.

When the cores are not appearing correctly, CORE Generator can still be displayed using Manage Cores (if there is an existing ".xco" in the project). All of the cores will be available, and new cores can be created and added to the project.


Try opening COREGen in stand-alone mode.

If there are no cores available when COREGen is opened by itself, try selecting:

Project -> Cores Catalog Display -> Show Latest Version Only... or Project -> Cores Catalog Display -> Customize

If the cores have been successfully installed, they should be available in the Cores Catalog and selectable for displaying.


If COREGen is opened from a Project Navigator project with the device set as "QPro Virtex Hi-Rel" or "QPro Virtex Rad-Hard", no cores are displayed in the "Select Core Dialog."

Cores are not being displayed because COREGen has no knowledge of what QPro Virtex is; therefore, it has no core list to pass back to Project Navigator.

To work around this problem, create the desired core(s) with the Xilinx Project device set to the equivalent non-QPro device, and then change the device field back to the desired QPro device after the core creation. The CLB structure for the QPro and non-QPro parts is the same for a related device.


On some Windows XP systems, the Core Catalog comes up empty in the Project Navigator New Source window if you do not have administrator privileges.

The administrator privileges issue has been fixed in the latest 6.1i Service Pack available at:
The first service pack containing the fix is 6.1i Service Pack 3.


This can happen when creating a new project and using the New Source option to create a new core. If the New Project Wizard (Edit -> Preferences "Use New Project Wizard") option is set, the New Project Wizard is used for the creation of new projects. The New Project Wizard does not correctly poll for available cores. Therefore, if the available cores for a given family are not already available in the system cache, they will not be seen in the core catalog.

In this case, the cores will be available after the project has been created. Alternatively, turn off the "Use New Project Wizard" option for creating new projects.


This issue can be caused when cores from an unsupported family exist in the repository. This may happen if ISE 6.1i is installed over an older version of ISE.

To check for cores from the XC4000-based families, search the $XILINX/coregen/ip tree for ".xcd" files containing the text "xc4000_all."


An ".xcd" file might contain a line similar to the following, indicating the supported families for the core:
chipfamily=Virtex_all virtex2 virtex2p spartan3 xc4000_all

Remove or rename (with a new extension) any files that match the search.


Other possible fixes that have been found for this problem involve cleaning up possibly corrupted files related to COREGen.

Close COREGen and Project Navigator, if Project Navigator is being used to call COREGen.
-Delete the HKEY_CURRENT_USER\Software\Xilinx\Coregen\Preferences key in the registry.
-Delete existing "__projnav\coregen.rsp" and "__projnav\launchCoregen.rsp" file in the current project directory.
-Delete the "coregen.prj" file in the current project directory.


If the value of the DEVFAM line, in the Project Navigator project (.npl) file, has any capital letters in it, COREGen Cores will not be available from that project when using Project -> New Source to create a new IP.

An ".npl" file with the following line will not allow the COREGen/Project Navigator interface to work:
DEVFAM Virtex2

The line must be changed to:
DEVFAM virtex2

If this problem persists for newly created projects, check the value of the following registry key. If the value contains a capital letter, modify it to be all lower case:
HKEY_CURRENT_USER\Software\Xilinx\Project Navigator\V1.0\Preferences\DefaultDeviceFamily
AR# 17685
Date 03/19/2006
Status Archive
Type General Article
Page Bookmarked