Solution

1

Supported Operating Systems

Windows 2000 Professional (Service Pack 2 to 4)
Windows XP Home (Service Pack 1)/Professional (Service Pack 1)
Sun Solaris 8/9
Linux Red Hat Enterprise 3.0 (32 bit and 64 bit)

Tool Requirements

To use this IP Update, first ensure that you have installed ISE 7.1i with Service Pack 2 (7.1i.02i) or later. ISE 7.1i Service Packs can be downloaded from this page:
http://www.xilinx.com/xlnx/xil_sw_updates_home.jsp

Acrobat Reader Requirement

Acrobat Reader Version 5 or later must be installed to view core data sheets. You can download the latest Acrobat software from the following Adobe site:
http://www.adobe.com/products/acrobat/readstep.html

To search for other available IP cores, please see:
http://www.xilinx.com/xlnx/xebiz/search/ipsrch.jsp

If you have comments, questions, or problems, please contact Xilinx Technical and Applications Support at:
http://www.xilinx.com/support/techsup/tappinfo.htm

2

Install the IP Update using one of the following methods:

Method 1: Automated Update using the Updates Installer

1. Start the CORE Generator Update Installer (from the CORE Generator Main GUI, select Tools -> Update Installer).
If you are prompted for a proxy host, contact your administrator to determine the proxy host address and port number that you should be using to get through your firewall.
2. Select " ISE 7.1i IP Update 1 (FTP)", or " ISE 7.1i IP Update 1 (HTTP)" from the list of updates in the Available Packages panel, depending on which mechanism works better for you.
3. Click "Add To Install Queue" to add the zip file for the update to the install queue.
If you are prompted to enter a login name and password, use the Xilinx login and password that you normally use to download IP Updates and software Service Packs.
4. Click "Install All Packages From Queue" to automatically initiate a download of the update.
After the update is downloaded, the Updates Installer displays a dialog box indicating that it is terminating the CORE Generator session and installing the downloaded archive. Another dialog box will indicate when the update installation is complete; you can then restart CORE Generator.
5. To confirm that you have installed the update properly, check the following file:
C:\Xilinx\coregen\install\install_history

NOTE: This step assumes that your Xilinx software is installed in C:\Xilinx.

Method 2: Manual Installation Method

1. Close the CORE Generator application if it is running.
2. Download the zip file (PC) or tar.gz file (UNIX) from the following location and save it to a temporary directory:
http://www.xilinx.com/xlnx/xil_sw_updates_home.jsp?update=ip&software=7.1i

NOTE: Before you can access this page and the files listed on it, you must be registered for CORE Generator IP Updates access.

3. Extract the zip file (71i_ip_update1.zip) or tar.gz (71i_ip_update1.tar.gz) archive to the root directory of your Xilinx software installation. Allow your extractor utility to overwrite all existing files and maintain the directory structure pre-defined in the archive.

PC
Unzip the zip file using WinZip 7.0 SR-1 or later.
The Xilinx software installation directory is typically located at "C:\XILINX" if the installation defaults were used. You can verify the location of the Xilinx install by entering the following on the DOS command line:
echo %XILINX%

UNIX
Use UnZip to unpack the zip file. Xilinx recommends that you download the "tar.gz" file and unpack it using the UNIX command line gunzip and tar utilities. WinZip and GNU tar are not recommended for extracting the "tar.gz" archive because of differences in the way they handle files with long path names. Please see (Xilinx Answer 11162) for more details.

If you have already installed your Xilinx ISE software, the Xilinx installation directory location is the value of the XILINX variable, which is defined by your setup script. After sourcing your Xilinx setup script, enter the following to determine the location of your Xilinx installation:
echo $XILINX

You might need system administrator privileges to install the update.

4. Restart CORE Generator. During start-up, CORE Generator automatically detects that new IP has been added to your installation. It allows you to specify which IP customizers (cores) will be visible in your currently active CORE Generator project. For your current project, you can select the following:
- Display only the latest versions for "All" cores in the catalog.
- Update the catalog view to add only "New" cores to the display.
- Make a "Custom" selection of cores visible in the CORE Generator catalog display for your current project.
5. Determine whether the installation was successful by verifying that the new cores are visible in the CORE Generator GUI.

3

MXE Simulation Library

The cores delivered with this IP Update require updated XilinxCoreLib libraries; please see (Xilinx Answer 10616) for information on how to obtain the latest pre-compiled MXE libraries.

4

What's New

Cores Included in this Release

http://www.xilinx.com/ipcenter/coregen/coregen_iplist_71i_ip1.htm

b>What's New in the CORE Generator application

- New C++-based IP customization GUIs are available for most new core versions in this release load and display faster on your desktop.
- CORE Generator now passes device-specific data to the customization GUIs instead of just the device architecture family. This enables CORE Generator to optimize the generated core for the specific device and also prevents you from trying to generate a core that would be too large for a particular device.

5

General Known Issues
6.1i COREGen - CORE Viewer reports incorrect resource utilization for XST-based cores (Xilinx Answer 14676).
6.3i CORE Generator - "ERROR:NgdBuild:76" given for CORE Generator ".ngc" file (Xilinx Answer 20483).
7.1i CORE Generator - Some Core Viewer data, from footprint, is not readable (Xilinx Answer 20692).
7.1i CORE Generator - 'xlicmgr status' no longer returns full list of licenses. "ERROR:coreutil - Please use -c to specify feature name." (Xilinx Answer 20481).
7.1i CORE Generator - COREGen will not launch. Error messages: "Could not reserve enough space for object heap" and "Could not create the Java virtual machine" (Xilinx Answer 20708).
7.1i CORE Generator - COREGen returns message "ERROR:coreutil:195 - Could not create Java virtual machine" - JVM (Xilinx Answer 20780).
7.1i CORE Generator - "ERROR:sim:4 - Could not create clean working directory \\<unc_path>\myproj\tmp\_cg." (Xilinx Answer 20721).
7.1i CORE Generator - CORE Generator gives the message "Ignoring command: UNK." (Xilinx Answer 20695).
7.1i CORE Generator - COREGen core customization GUI appears to hang (Xilinx Answer 20720).
7.1i CORE Generator - No IP is available for Automotive parts (Xilinx Answer 20765).
7.1i CORE Generator (Japanese version) - If the "_" (underscore) character is used in a component name, the character is written out as a "|" (pipe character). For details on this possible naming issue when using a machine with a Japanese 106-character keyboard, see (Xilinx Answer 15312).
7.1i CORE Generator - Error occurred while executing formal verification script "core2formal_wrp" (Xilinx Answer 20715).
7.1i CORE Generator - Attempting to open a core customization GUI opens the data sheet for the selected IP core. (Xilinx Answer 21364)

6

Issues resolved in IP Update 1 for 7.1i

7.1i CORE Generator - XCO file for block RAM components is not read correctly. Regeneration gives "ERROR:coreutil - Illegal combination: Port B Width invalid for Port A settings." (Xilinx Answer 21301)
7.1i ECS - Symbols created for Core Generator IP cores do not include a functional label for the symbol (Xilinx Answer 21306).
7.1i CORE Generator - Creating a New Project yields the message "Could not create directory <dir_name>" (Xilinx Answer 20707).
7.1i CORE Generator - The core view window shows multiple listings of IP Cores (Xilinx Answer 20479).
7.1i CORE Generator - If an IP core is both Scheduled for Obsolescence and is a Licensed IP, the only status displayed is Licensed IP (Xilinx Answer 21308).
7.1i CORE Generator - COREGen inserts an extra backslash when trying to read in the XCO files that exist in a project (Xilinx Answer 21312).