Setting Up for Concept

Concept requires several files to be present in the design directory. The $XILINX/cadence/tutorial/calc_sch directory contains these files, but you must modify some of them for your environment.

• global.cmd
  
  You need a global.cmd that references the proper libraries. An example global.cmd for this tutorial follows.
  
  

      master_library "./master.local" ;
      library "xce4000e" ,
              "xcepads",
              "hdl_direct_lib",
              “standard” ;
      use "calc.wrk" ;
      root_drawing "calc" ;

  
  
  
  • The actual path to each library is defined in the master.local file. The master_library line, (the first line in the global.cmd file), points to this local library file, which resides in the design directory.
    
    
  • One of the entries in the “library” listing should point to the library supporting the Xilinx architecture you use. In the example above, this corresponds to the xce4000e library, which supports the Xilinx XC4000E/L architectures.
    
    
  • Note the presence of the “hdl_direct_lib” library; SLICE, INPORT, OUTPORT, and IOPORT bodies required for HDL Direct compliance is provided here. Use SLICEs in place of taps and ctaps in the “standard” library for tapping bits off a bus. Use INPORT, OUTPORT, and IOPORT bodies on interface signals in a logic drawing that connects to a higher level symbol body.
    
    
  • The “xcepads” library contains the Xilinx pad symbols.
    
    
  • The “use” line points to a file (typically with a .wrk extension) that Concept can use to store information about your design.
    
    
• master.local
  
  This file contains the actual UNIX paths to the libraries referenced in global.cmd. It does not need to contain the path to local libraries. The following shows an example master.local file for a 4000E design.
  
  

      file_type = master_library;
      "xce4000e" '/xlx/cadence/data/xce4000e/xce4000e.lib';
      "xcepads" '/xlx/cadence/data/xcepads/xcepads.lib';
      end.

  
  
  You do not have to reference other Cadence-supplied Concept libraries (such as the HDL Direct library) here, assuming an entry exists in the $CDS_INST_DIR/lib/master.lib file pointing to those libraries. Do not use variables (such as $XILINX) in this file; instead use absolute path names.
  
  For the Calc design, you must modify master.local to point to location_of_Xilinx_software/cadence/data/xce4000e/xce4000e.lib.
  
  
• calc.wrk
  
  This file contains the correlation between the names of the various schematics and the UNIX directory where they reside. Concept automatically creates this file if a “use” line in the global.cmd references it. No alterations are necessary.
  
  
• cds.lib
  
  

CONCEPT2XIL requires this file, and it must point to the location that contains VAN-compiled (Verilog Analyzer-Compiled) library files for the compiler. As an example, a sample cds.lib file for a 4000E design follows.

define xce4000e_syn /xlx/cadence/data/xce4000e_syn

Use the following format for entries in this file.

define target_tech_syn path_to_XILINX/cadence/data/ target_tech_syn

target_tech is xce3000, xce4000e, xce4000x, xce5200, or xce9000.