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

ChipScope - How do I use ChipScope Core Inserter with Design Manager?


Keywords: ChipScope, ILA, ICON, Core Inserter, NGO, flow, Design, Manager

Urgency: Standard

General Description:
ChipScope 2000-12 introduced a new mechanism for generating and inserting ICON and ILA cores called the "Core Inserter." This tool reads in the post-synthesis top-level EDIF and allows users to set ICON and ILA core parameters and define signal connections; it then generates these cores and creates new top-level .ngo files for implementation.

How can the Core Inserter (in version 2000-12, 3.3i, or 4.1i) be used with Design Manager version 3.x or 4.x?


The following steps must be carefully followed to process a design through Design Manager when inserting ChipScope cores via the Core Inserter:

1. Initially Translate the design.

2. Run the ChipScope Core Inserter.
- Launch the Core Inserter from Start -> Programs -> ChipScope -> ChipScope Core Inserter.
- Set the following parameters under the Device tab:

Input Design Netlist = <ProjectDir>\<design>.edn
Input Constraints File = <ProjectDir>\<design>.ucf (valid for 3.3i only)
Output Design Netlist = <ProjectDir>\xproj\ver<#>\<design>.ngo
Output Constraints File = <ProjectDir>\<design>_ila.ucf (valid for 3.3i only)
Output Directory = <ProjectDir>\xproj\ver<#>

(NOTE: Browse for the input <design>.edf or <design>.edn file. All fields except "Input Constraints File" will be filled in. Modify the directories as shown above.)

3. Define Core parameters and connect all signals, then generate the cores. Core Generation will place new .ngo files for the top level (as well as the .ncf file in version 4.1i), as well as for the ICON and ILA cores, in the <ProjectDir>\xproj\ver<#> directory.

4. Rerun "translate", using the UCF generated by the Core Inserter if you are using 3.3i. For 4.1i ChipScope, .ncf files are used, and they do not need to be explicitly specified -- they are picked up automatically by NGDBuild when the core .edf files are detected. The new .ngo will be used as long as the time stamp on the file is more recent than the .edn netlist.

5. Continue with the implementation. Be sure to specify the ChipScope options (JTAG clock, enable Readback) when creating the bit stream.
AR# 11650
Date Created 08/29/2007
Last Updated 09/30/2005
Status Archive