文件列表:

fre_dev_v0.1 (0, 2015-07-16)
fre_dev_v0.1\core (0, 2015-04-29)
fre_dev_v0.1\core\blk_mem_gen_ds512.pdf (41717, 2011-02-04)
fre_dev_v0.1\core\coregen.cgc (12435, 2015-03-25)
fre_dev_v0.1\core\coregen.cgp (238, 2015-03-23)
fre_dev_v0.1\core\coregen.log (606, 2015-04-21)
fre_dev_v0.1\core\cos_coe.coe (28738, 2015-03-22)
fre_dev_v0.1\core\create_fir.tcl (1266, 2015-03-26)
fre_dev_v0.1\core\create_rom4096x16.tcl (1291, 2015-03-23)
fre_dev_v0.1\core\create_rrc.tcl (1266, 2015-03-25)
fre_dev_v0.1\core\edit_rom4096x16.tcl (1136, 2015-04-21)
fre_dev_v0.1\core\rom4096x16.asy (622, 2015-03-23)
fre_dev_v0.1\core\rom4096x16.gise (2820, 2015-07-22)
fre_dev_v0.1\core\rom4096x16.hex (73728, 2015-03-23)
fre_dev_v0.1\core\rom4096x16.mif (73728, 2015-03-23)
fre_dev_v0.1\core\rom4096x16.ncf (0, 2015-04-29)
fre_dev_v0.1\core\rom4096x16.ngc (45088, 2015-03-23)
fre_dev_v0.1\core\rom4096x16.sym (1798, 2015-03-23)
fre_dev_v0.1\core\rom4096x16.v (5842, 2015-03-23)
fre_dev_v0.1\core\rom4096x16.veo (3959, 2015-03-23)
fre_dev_v0.1\core\rom4096x16.vhd (5749, 2015-03-23)
fre_dev_v0.1\core\rom4096x16.vho (4301, 2015-03-23)
fre_dev_v0.1\core\rom4096x16.xco (3061, 2015-03-23)
fre_dev_v0.1\core\rom4096x16.xise (5255, 2015-03-25)
fre_dev_v0.1\core\rom4096x16_flist.txt (307, 2015-03-23)
fre_dev_v0.1\core\rom4096x16_xmdf.tcl (3561, 2015-03-23)
fre_dev_v0.1\core\tmp (0, 2015-04-21)
fre_dev_v0.1\core\tmp\xlnx_auto_0_xdb (0, 2015-03-23)
fre_dev_v0.1\core\tmp\_cg (0, 2015-04-21)
fre_dev_v0.1\core\tmp\_cg\rom4096x16.mif (73728, 2015-04-21)
fre_dev_v0.1\core\tmp\_cg\_dbg (0, 2015-04-21)
fre_dev_v0.1\core\tmp\_cg\_dbg\xil_288.in (4530, 2015-04-21)
fre_dev_v0.1\core\tmp\_cg\_dbg\xil_288.out (2443, 2015-04-21)
fre_dev_v0.1\core\tmp\_xmsgs (0, 2015-03-23)
fre_dev_v0.1\core\tmp\_xmsgs\ngcbuild.xmsgs (367, 2015-03-23)
fre_dev_v0.1\core\tmp\_xmsgs\pn_parser.xmsgs (759, 2015-03-23)
fre_dev_v0.1\core\tmp\_xmsgs\xst.xmsgs (68743, 2015-03-23)
fre_dev_v0.1\core\_xmsgs (0, 2015-04-21)
fre_dev_v0.1\core\_xmsgs\cg.xmsgs (739, 2015-04-21)
... ...

Core name: Xilinx LogiCORE Block Memory Generator Version: 6.1 Release Date: March 01 2011 ================================================================================ This document contains the following sections: 1. Introduction 2. New Features 3. Supported Devices 4. Resolved Issues 5. Known Issues 6. Technical Support 7. Core Release History 8. Legal Disclaimer ================================================================================ 1. INTRODUCTION For the IP installation instructions for this core,please go to: http://www.xilinx.com/ipcenter/coregen/ip_update_install_instructions.htm For system requirements: http://www.xilinx.com/ipcenter/coregen/ip_update_system_requirements.htm This file contains release notes for the Xilinx LogiCORE IP Block Memory Generator v6.1 solution. For the latest core updates, see the product page at: http://www.xilinx.com/products/ipcenter/Block_Memory_Generator.htm 2. NEW FEATURES - ISE 13.1 Software support - Virtex-7 and Kintex-7 device support - AXI4/AXI4-Lite interface support for Virtex-6 and Spartan-6 devices 3. SUPPORTED DEVICES The following device families are supported by the core for this release. - Virtex-7 - Kintex-7 - Virtex-6 XC CXT/LXT/SXT/HXT - Virtex-6 XQ LXT/SXT - Virtex-6 -1L XC LXT/SXT - Spartan-6 XC LX/LXT - Spartan-6 XA - Spartan-6 XQ LX/LXT - Spartan-6 -1L XC LX - Virtex-5 XC LX/LXT/SXT/TXT/FXT - Virtex-5 XQ LX/ LXT/SXT/FXT - Virtex-4 XC LX/SX/FX - Virtex-4 XQ LX/SX/FX - Virtex-4 XQR LX/SX/FX - Spartan-3 XC - Spartan-3 XA - Spartan-3A XC 3A / 3A DSP / 3AN DSP - Spartan-3A XA 3A / 3A DSP - Spartan-3E XC - Spartan-3E XA 4. RESOLVED ISSUES The following issues are resolved in Block Memory Generator v6.1: a. "Fill remaining memory locations" - option disabled in GUI - Version fixed : 6.1 1.Core does not allow the customer to use the "remaining memory locations" option. Solution: "Fill remaining memory locations" - option enbaled in GUI - CR 575015 - AR 37944 5. KNOWN ISSUES The following are known issues for v6.1 of this core at time of release: a. Core errors in NGDBuild when the depth is too large (especially for Spartan-6 devices) Workaround: Generate two shallower FIFOs and pass the appropriate address lines to implement the FIFO of the required depth - CR587481 - AR 39718 b. Virtex-6 and Spartan-6: BRAM Memory collision error, when the user selects TDP (write_mode= Read First) Solution: The user must review the possible scenarios that causes the collission and revise their design to avoid those situations. - CR588505 Note: Refer to UG383, 'Conflict Avoidance' section when using TDP Memory - with Write Mode = Read First in conjunction with asynchronous clocking c. Power estimation figures in the datasheet are preliminary for Virtex-5 and Spartan-3. d. Core does not generate for large memories. Depending on the machine the ISE CORE Generator software runs on, the maximum size of the memory that can be generated will vary. For example, a Dual Pentium-4 server with 2 GB RAM can generate a memory core of size 1.8 MBits or 230 KBytes - CR 415768 - AR 24034 e. Out-of-range address input can cause the core to generate X's on the DOUT bus - AR 23744 f. When the IP core is generated for Spartan-6 devices, the core does not combine two adjacent 9k BRAMs into one 18K BRAM. - CR 52***29 The most recent information, including known issues, workarounds, and resolutions for this version is provided in the IP Release Notes User Guide located at www.xilinx.com/support/documentation/user_guides/xtp025.pdf 6. TECHNICAL SUPPORT To obtain technical support, create a WebCase at www.xilinx.com/support. Questions are routed to a team with expertise using this product. Xilinx provides technical support for use of this product when used according to the guidelines described in the core documentation, and cannot guarantee timing, functionality, or support of this product for designs that do not follow specified guidelines. 7. CORE RELEASE HISTORY Date By Version Description ================================================================================ 03/01/2011 Xilinx, Inc. 6.1 ISE 13.1 support and Virtex-7 and Kintex-7 device support; AXI4/AXI4-Lite Support 10/29/2010 Xilinx, Inc. 5.2 ISE 13.0.2 support 09/21/2010 Xilinx, Inc. 4.3 ISE 12.3 support 07/30/2010 Xilinx, Inc. 5.1 ISE 13.0.1 support 07/23/2010 Xilinx, Inc. 4.2 ISE 12.2 support 04/19/2010 Xilinx, Inc. 4.1 ISE 12.1 support 03/09/2010 Xilinx, Inc. 3.3 rev 2 Fix for V6 Memory collision issue 12/02/2009 Xilinx, Inc. 3.3 rev 1 ISE 11.4 support; Spartan-6 Low Power Device support; Automotive Spartan 3A DSP device support 09/16/2009 Xilinx, Inc. 3.3 Revised to v3.3 06/24/2009 Xilinx, Inc. 3.2 Revised to v3.2 04/24/2009 Xilinx, Inc. 3.1 Revised to v3.1 09/19/2008 Xilinx, Inc. 2.8 Revised to v2.8 03/24/2008 Xilinx, Inc. 2.7 10.1 support; Revised to v2.7 10/03/2007 Xilinx, Inc. 2.6 Revised to v2.6 07/2007 Xilinx, Inc. 2.5 Revised to v2.5 04/2007 Xilinx, Inc. 2.4 Revised to v2.4 rev 1 02/2007 Xilinx, Inc. 2.4 Revised to v2.4 11/2006 Xilinx, Inc. 2.3 Revised to v2.3 09/2006 Xilinx, Inc. 2.2 Revised to v2.2 06/2006 Xilinx, Inc. 2.1 Revised to v2.1 01/2006 Xilinx, Inc. 1.1 Initial release ================================================================================ 8. Legal Disclaimer (c) Copyright 2006 - 2011 Xilinx, Inc. All rights reserved. This file contains confidential and proprietary information of Xilinx, Inc. and is protected under U.S. and international copyright and other intellectual property laws. DISCLAIMER This disclaimer is not a license and does not grant any rights to the materials distributed herewith. Except as otherwise provided in a valid license issued to you by Xilinx, and to the maximum extent permitted by applicable law: (1) THESE MATERIALS ARE MADE AVAILABLE "AS IS" AND WITH ALL FAULTS, AND XILINX HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS, EXPRESS, IMPLIED, OR STATUTORY, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, NON- INFRINGEMENT, OR FITNESS FOR ANY PARTICULAR PURPOSE; and (2) Xilinx shall not be liable (whether in contract or tort, including negligence, or under any other theory of liability) for any loss or damage of any kind or nature related to, arising under or in connection with these materials, including for any direct, or any indirect, special, incidental, or consequential loss or damage (including loss of data, profits, goodwill, or any type of loss or damage suffered as a result of any action brought by a third party) even if such damage or loss was reasonably foreseeable or Xilinx had been advised of the possibility of the same. CRITICAL APPLICATIONS Xilinx products are not designed or intended to be fail- safe, or for use in any application requiring fail-safe performance, such as life-support or safety devices or systems, Class III medical devices, nuclear facilities, applications related to the deployment of airbags, or any other applications that could lead to death, personal injury, or severe property or environmental damage (individually and collectively, "Critical Applications"). Customer assumes the sole risk and liability of any use of Xilinx products in Critical Applications, subject only to applicable laws and regulations governing limitations on product liability. THIS COPYRIGHT NOTICE AND DISCLAIMER MUST BE RETAINED AS PART OF THIS FILE AT ALL TIMES.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：