Retargeting a Design to a Different Family

You can retarget your designs from one device family to another provided both your source (original) and target designs include only Unified Library components. Because most of the symbols in the Unified Libraries have the same footprint and naming across all device families, you can easily convert your designs without extensive design re-entry.

In the following example, you retarget your design to an XC5200 device from an XC4000E device.

Follow these steps to convert your designs.

1. Start Concept and open your design.
   
   
2. Enter the following Concept commands in the command line window.
   
   ignore xce4000e
   library xce5200
   get
   write
   
   The ignore command removes a specified library from the active search list.
   
   The library command adds the specified library to the search list.
   
   When specified with no arguments, the get command reads in the object references in the design and displays the design using components from the currently active libraries.
   
   When specified with no arguments, the write command writes or saves the active design view to disk. The prior example shows the active view as the logic, or schematic view, logic.1.1.
   
   Alternatively, you can convert the design to the target family by first changing your global.cmd file to point to the target family library, then reading in the design and saving it with the new library references. A sample global.cmd file reads as follows.
   
   

      library “xce5200”,
              “xcepads”,
              “hdl_direct_lib”,
              “standard” ;
      use “design.wrk” ;

   
   You must define both device architecture libraries in either your master.lib or master.local file.
   
   When accessing a library, Concept searches through the libraries using a “last read, first out” protocol. For the sample global.cmd file, Concept searches the libraries in the following order: standard, hdl_direct_lib, xcepads, and xce5200.
   
   The use command specifies the SCALD library map file used for the design.
   
   After the conversion process, the symbols common to both the source (XC4000E, in this case) and target families maintain their relative location and pin position in the target design schematic. The symbols do so because of the uniformity in size, shape and naming of symbols in the Unified Libraries across all device architectures or families. Pins on these symbols also retain their connectivity to the nets they were originally attached to in the source design.
   
   
3. You must manually replace symbols not common to your source and target families with equivalent logic. For example, consider an XC3000A design which earlier used a GCLK. To retarget for use in an XC4000E device, you must manually replace the GCLK symbol with a BUFGP, BUFG, or BUFGS.
   
   
4. You must also manually replace components that are macros in the source (or target) library, but primitives in the other. For example, an AND5 is a primitive in the XC4000E family, but a macro in the XC5200 library. If converting an XC4000E design to the XC5200 family, you must manually replace all instances of AND5s in the target design after you complete the initial library retargeting step described in Step 2. Use the replace command in Concept to make your replacements.
   
   Use the replace command as shown in the following example.
   
   select the AND5 symbol
   replace and5
   
   
5. For an XC4000E/L/EX/XL/XV to XC5200 conversion, you must also replace all XC4000 wide decoder macros (DECODExxx) with XC5200 DECODExxx macros.
   
   

The following table lists components to manually replace in the case of an XC4000 to XC5200 conversion.