首页资源分类PCB layoutPCB设计技巧 > Cadence to Synopsys Interface User Guide.pdf

Cadence to Synopsys Interface User Guide.pdf

已有 445499个资源

下载专区

上传者其他资源

    文档信息举报收藏

    标    签:cadence

    分    享:

    文档简介

    很有用的资源,尤其是对于cadence软件有点不懂的可以下载看看

    文档预览

    Cadence to Synopsys Interface User Guide Product Version 4.4.0 June 2000 © 1990-1997 Cadence Design Systems, Inc. All rights reserved. Printed in the United States of America. Cadence Design Systems, Inc., 555 River Oaks Parkway, San Jose, CA 95134, USA Trademarks: Trademarks and service marks of Cadence Design Systems, Inc. (Cadence) contained in this document are attributed to Cadence with the appropriate symbol. For queries regarding Cadence’s trademarks, contact the corporate legal department at the address shown above or call 1-800-862-4522. All other trademarks are the property of their respective holders. Restricted Print Permission: This publication is protected by copyright and any unauthorized use of this publication may violate copyright, trademark, and other laws. Except as specified in this permission statement, this publication may not be copied, reproduced, modified, published, uploaded, posted, transmitted, or distributed in any way, without prior written permission from Cadence. This statement grants you permission to print one (1) hard copy of this publication subject to the following conditions: 1. The publication may be used solely for personal, informational, and noncommercial purposes; 2. The publication may not be modified in any way; 3. Any copy of the publication or portion thereof must include all original copyright, trademark, and other proprietary notices and this permission statement; and 4. Cadence reserves the right to revoke this authorization at any time, and any such use shall be discontinued immediately upon written notice from Cadence. Disclaimer: Information in this publication is subject to change without notice and does not represent a commitment on the part of Cadence. The information contained herein is the proprietary and confidential information of Cadence or its licensors, and is supplied subject to, and may be used only by Cadence’s customer in accordance with, a written agreement between Cadence and its customer. Except as may be explicitly set forth in such agreement, Cadence does not make, and expressly disclaims, any representations or warranties as to the completeness, accuracy or usefulness of the information contained in this document. Cadence does not warrant that use of such information will not infringe any third party rights, nor does Cadence assume any liability for damages or costs of any kind that may result from use of such information. Restricted Rights: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in FAR52.227-14 and DFAR252.227-7013 et seq. or its successor. Cadence to Synopsys Interface User Guide Contents Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Finding Information in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Learning the Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Other Sources of Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Cadence Online Documentation System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 SourceLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 SOLV-IT! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Newsgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 About the Cadence to Synopsys Interface (CSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 CSI Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Required and Optional Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Limitations of CSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 CSI in the Design Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2 Using CSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Setting Up CSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Modifying the .cdsinit File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Compiling the .slib Library File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Setting Up for Remote Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Initializing CIW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Initializing CSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 From the CIW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 June 2000 2 Product Version 4.4.0 Cadence to Synopsys Interface User Guide From a Design Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 From the VHDL Toolbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Creating a Symbol Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Selecting CSI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Selecting Synopsys Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Editing Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Exporting the Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Building the Command File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Creating the Default Command File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Creating a Custom Command File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Using a Custom Command File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Running Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Design Compiler in Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Design Compiler in Interactive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Design Analyzer in Interactive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Importing the Synthesized Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Examining the Synthesized Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Installing the Synthesized Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 3 Session, Utilities, and Run Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Session Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Session – Environment Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Session – Environment – Change Run Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Session – Environment – Delete Remote Run Directory . . . . . . . . . . . . . . . . . . . . . . 55 Session – Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Session – Setup – CSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Session – Setup – Synopsys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Session – Setup – Verilog Netlister . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Session – Edit Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Utilities Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Utilities – Show Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Utilities – Show – Job Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 June 2000 3 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Utilities – Show – CSI Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Utilities – Show – DC Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Utilities – Show – Command File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Utilities – Show – DC Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Utilities – Show – Other File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Utilities – Show – Synthesized Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Utilities – Symbol Compilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Utilities – Custom Command File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Utilities – Custom Command File – Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Utilities – Custom Command File – Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Utilities – Custom Command File – Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Run Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Run – Export Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Run – Build Command File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Run – Synopsys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Run – Import Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Run – Install Synthesized Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 A Run Directory Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Synthesis Run Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Files in the Synthesis Run Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 B SKILL Cross-Reference Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Mapping SKILL Functions to Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Mapping SKILL Variables to Field Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 June 2000 4 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Before You Start About This Manual This manual contains user and reference information about the Cadence to Synopsys Interface (CSI). This interface lets you use the Synopsys tools for logic synthesis and optimization within the Cadence Design Framework II™ (Composer) environment. If you have a Concept schematic, you must use the SynLink Interface to Synopsys. This manual is intended for logic designers as well as custom library developers. To use this product you should be familiar with the Synopsys Design Compiler® software. Finding Information in This Manual The topics covered in this manual are summarized in the following table. If you want to . . . Read . . . Know about CSI functions and when to use Chapter 1, “Introduction” CSI in the design process Learn about the tasks for synthesizing a design using CSI Chapter 2, “Using CSI” See a description of CSI commands and forms Chapter 3, “Session, Utilities, and Run Menu Commands” See a list of the files in the synthesis run directory Appendix A, “Run Directory Files” See the cross-reference between the SKILL Appendix B, “SKILL Cross-Reference functions and the CSI commands and forms Tables” Conventions Here are the conventions used in Chapter 3 to describe the menu commands. June 2000 5 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Before You Start Boxes and arrows in a sequence like the one below show you the order in which you select a command from a menu. Run ¿ Synopsys Each form shows you the system defaults: s Filled buttons are the default selections. s Filled-in values are the default values. Learning the Basics Before you begin using CSI, you should be familiar with the Design Framework II environment. Design Framework II Help shows you how to s Start the Cadence software s Get around in the Cadence software s Get help on a command s Use the mouse s Use menus s Use standard and options forms s Start a design session Other Sources of Information For more information about CSI and other related products, you can consult the sources listed below. Product Installation The Cadence™ Software Installation and License Management Reference tells you how to install the product. June 2000 6 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Before You Start The Design Framework II Configuration Information manual tells you how to configure your environment for Design Framework II. The Synopsys System Installation and Configuration Guide, Version 3.3 tells you how to install the Synopsys software. You can install the Synopsys software on your system or on a remote system. Important CSI 4.4.3 works only with the following versions of the Synopsys software: 1997.02, 1997.08, and 1998.02. Related Manuals CSI is often used with other Cadence products to develop logic designs. The following manuals give you more information about the Cadence tools used in design synthesis. If you want to use the Cadence schematic editor to enter your design, refer to the Composer: Design Entry User Guide. If you have never used Composer before, start with the Design Entry: Composer Tutorial. To learn about using Verilog-XL with Composer, see Composer: Verilog-XL Integration User Guide. For more detail about the Verilog-XL netlister, refer to the Verilog-XL Integration Reference Manual. If you want to know more about the Standard Delay Format, refer to the SDF Annotator User Guide. Cadence Online Documentation System The documentation system lets you read Cadence help systems and manuals online. You can s Search for words or phrases in Cadence documents s Navigate each document by clicking on topics or scrolling through s Print all or part of the documents To start the online documentation system: 1. Type /tools/bin/cdsdoc & 2. Double-click Cadence Online Documentation System 3. Click Cadence Documentation Help June 2000 7 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Before You Start The user guide for the Cadence online documentation system is loaded into your web browser. Customer Support There are several ways to obtain support when using Cadence products. s Cadence offers many classes. Ask your sales representative for more information. s The Cadence Customer Support hotline telephone number operates from 8 a.m. to 8 p.m. Eastern Time: 1-877-CDS-4911 (1-877-237-4911) SourceLink SourceLink is the Cadence Customer Support information service available free of charge to Cadence customers who have a maintenance contract. To get a SourceLink account, go to the Cadence home page on the World Wide Web: http://www.cadence.com When the home page appears: 1. Click on "Customer Support" 2. Select your location ("Japan/Asia Pacific", "North America", or "Europe") 3. Click on "SourceLink - Online Technical Support." Use the on-line form to open your account. TalkVerilog TalkVerilog is the Cadence on-line newsletter for Verilog-XL users. TalkVerilog is available to Cadence customers by e-mail subscription or on the Web. To request a free subscription or submit articles, please e-mail to talkverilog@cadence.com. Use the words "RequestTalkVerilog" or "subscribe" in the subject line of your e-mail header and include your name, company name and address in the body of the message. SourceLink subscribers can view TalkVerilog at http://sourcelink.cadence.com/TalkVerilog. June 2000 8 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Before You Start SOLV-IT! SOLV-IT!® is the Synopsys on-line knowledge database available free of charge to all Synopsys customers with a maintenance contract. To get a SOLV-IT! account, go to the Synopsys home page on the World Wide Web: http://www.synopsys.com Click on SolvNET. Fill out and submit the registration form to use SOLV-IT! Newsgroups You can find user discussions of topics related to design, simulation, synthesis, and test in these newsgroups: s comp.cad.cadence u Cadence tool topics s comp.cad.synthesis u Synopsys tool topics u General synthesis information s comp.lang.verilog s comp.lang.vhdl s comp.arch s comp.lsi s comp.lsi.cad s comp.lsi.testing June 2000 9 Product Version 4.4.0 Cadence to Synopsys Interface User Guide 1 Introduction About the Cadence to Synopsys Interface (CSI) Today’s design solutions require effective logic synthesis and optimization. Logic synthesis translates textual circuit descriptions into gate-level representations. Optimization minimizes the area of the synthesized design and improves the design’s performance. CSI is an interactive and graphical user interface that lets you use the Synopsys tools in the Cadence Design Framework II environment to synthesize and optimize your design. Typically, you synthesize a design iteratively. After each synthesis run, you examine the design, and if the results are not satisfactory, you specify different design constraints and synthesize again. You optimize design performance by specifying timing delays and parasitic data. CSI Functions CSI lets you do the following: s Transfer mixed-level design data (schematic and HDL description) to the Synopsys Design Compiler. Your design data can include hierarchy, buses, and multisheet schematics. The design data can reference any Cadence or ASIC-vendor gate array and standard cell libraries. s Transfer timing and delay data in Standard Delay Format (SDF) and parasitic data in Standard Parasitic Format (SPF) to and from the Synopsys Design Compiler for design optimization. s Generate a Synopsys symbol library from a Cadence symbol library. s Define and manage customized Synopsys command files. s Specify design constraints and synthesis run options. s Synthesize and optimize your design in batch or interactive mode from a local or a remote machine. June 2000 10 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Introduction s Transfer a synthesized schematic design from the Synopsys Design Compiler back to Design Framework II environment. s Display a synthesized hierarchical schematic design from the current CSI run directory. s Save a synthesized design from the current CSI run directory into the Cadence original source libraries. s Display a CSI or Synopsys report. s Manage run directory files for iterative synthesis runs. s Use command macros and most Synopsys commands. June 2000 11 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Introduction Required and Optional Products CSI requires the following Cadence and Synopsys software. Table 1-1 CSI Required Products Product Synopsys Design Compiler Cadence Design Framework II Composer Design Entry On-line Documentation Methodology Notes (Read first) Design Compiler Family Reference Design Compiler Tutorial Synthesis Quick Reference Synthesis Application Notes Design Framework II Help Design Entry: Composer Tutorial Composer: Design Entry User Guide Important CSI 4.4.3 works only with the following versions of the Synopsys software: 1997.02, 1997.08, and 1998.02. CSI also supports the following optional products. Table 1-2 CSI Optional Products Product On-line Documentation Synopsys Design Analyzer Design Analyzer Reference HDL Compiler (Verilog option) HDL Compiler for Verilog Reference VHDL Compiler VHDL Compiler Reference June 2000 12 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Introduction Limitations of CSI s CSI does not support the Synopsys Test Compiler. s CSI does not support the use of Synopsys DesignWare macros in its flow at this time. If Synopsys Design Compiler attempts to map your design to DesignWare macros, you must perform an “ungroup” command in Synopsys Design Compiler, then re-synthesize the design. CSI in the Design Process CSI is a part of the design process when you use the Synopsys tools in the Cadence Design Framework II environment. The figure on the following page shows CSI in the design process. First you enter and simulate your behavioral design (in schematic or Verilog HDL description). Then you export the Cadence cellview to the Synopsys Design Compiler via CSI. When you export the design, you can interactively specify design constraints, timing and delay data (SDF file), and parasitic data (SPF file). The Synopsys Design Compiler outputs a synthesized and optimized schematic design in EDIF format. The Design Compiler can generate a timing constraints SDF file and report files about various information such as design data, optimization data, and timing data. You import the synthesized and optimized design, in EDIF format, into a Cadence cellview to perform post-synthesis simulation and timing analysis. June 2000 13 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Introduction Table 1-3 CSI in the Design Process Behavioral (rtl) Design Entry Composer Behavioral (rtl) Simulation Verilog-XL Cadence Cellview (schematic or HDL view) CSI Design Constraints Design Export Logic Synthesis Design Compiler Cadence Cellview (schematic view) Logic Optimization Design Compiler Design Import Synthesized Design EDIF Format SDF SPF SDF SPF Simulation Verilog-XL Timing Analysis Veritime Floorplanning Preview Delay Calculation CDC Test Synthesis Test Compiler Legend Task Cadence Product Task Synopsys Product CSI Product covered in this manual June 2000 14 Product Version 4.4.0 Cadence to Synopsys Interface User Guide 2 Using CSI Introduction on page 15 Setting Up CSI on page 16 Initializing CIW on page 25 Initializing CSI on page 26 Creating a Symbol Library on page 32 Selecting CSI Options on page 34 Selecting Synopsys Options on page 37 Editing Constraints on page 39 Exporting the Design on page 41 Building the Command File on page 41 Running Synthesis on page 44 Importing the Synthesized Design on page 47 Examining the Synthesized Design on page 48 Installing the Synthesized Design on page 48 Introduction CSI lets you use the Synopsys tools in the Cadence Design Framework II environment to perform design synthesis. The diagram on the following page shows the tasks you need to perform for synthesizing a design using CSI. This chapter describes each box shown in the diagram. June 2000 15 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI Table 2-1 Task Flow for Synthesizing a Design Using CSI Task Setting Up CSI Initializing CSI Selecting CSI Options Selecting Synopsys Options Creating a Symbol Library Editing Constraints Exporting the Design Building the Command File Running Synthesis Importing the Synthesized Design Examining the Synthesized Design Installing the Synthesized Design Menu Command None Tools – Design Synthesis – CSI Session – Setup – CSI Session – Setup – Synopsys Utilities – Symbol Compilation Session – Edit Constraints Run – Export Design Run – Build Command File Run – Synopsys Run – Import Design Show – Synthesized Design Run – Install Synthesized Design Setting Up CSI If any of your existing Synopsys symbol libraries are not compatible with CSI version 4.2.2 or greater, compile the Synopsys symbol library in text format, the .slib library file. See Compiling the .slib Library File. Before using CSI, make the following changes if you want to s Change the default values in the CSI form, or customize your CSI environment, modify the default Cadence Design Framework II environment file, the .cdsinit file, to include the SKILL variables that are specific to CSI. See Modifying the .cdsinit File. s Run synthesis on a remote machine using the Network File System (NFS), set up the CSI mount files. See Setting Up for Remote Synthesis. s Run synthesis in interactive mode, be sure you can access the xterm program through the UNIX command path on the local or the remote machine. See Remote Synthesis. Once you do the initial setup, you do not have to repeat it unless you change either the library or a technology file. June 2000 16 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI Modifying the .cdsinit File The .cdsinit file contains all the default SKILL variables used by the Design Framework II environment. You can change the CSI default values used in the CSI form by adding certain SKILL variables to the .cdsinit file. You can also customize your CSI environment by adding optional SKILL variables to the .cdsinit file. CSI Related SKILL Variables When you add the following SKILL variables to the .cdsinit file, these variables set the default values on the CSI form. Each variable is listed with its default value. Important Appendix B, “Mapping SKILL Variables to Field Names” shows the mapping from these SKILL variables to the names of the fields on the forms and the menu commands. = "localhost" Specifies the Synopsys host machine name. csiSynopsysRoot = "/synopsys" Specifies the Synopsys software installation directory path on the csiRemoteHostName machine. sprintf(csiSynopsysLibPath ". %s/etc/dci/synlibs" car(getInstallPath()) ) Specifies the Synopsys library search path. Always specify the “.” first, Synopsys interprets the “.” as the current run directory. csiSynSymbolLibs = "sample.sdb" Specifies the Synopsys symbol library. You can specify more than one library. csiSynTargetLibs = "sample.db" Specifies the Synopsys technology library. You can specify more than one library. Display Mode If you want to customize the display mode for the synthesis run directory files, add the following variable to your .cdsinit file. June 2000 17 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI csiShowWorksLikeEdit = nil Specifies the read or edit mode for the Show command. If you set this variable to t, the Show command will be in edit mode. Verilog Netlisting If you want to customize the Verilog netlisting, add the following variables to your .cdsinit file. csiViewListVerilog = '("functional" "behavioral" "system" "verilog" "opt_net" "opt_sch" "schematic" "symbol") Specifies the view list of the Verilog netlister. It lists the view sequence that the netlister uses when deciding which view of a cell to traverse when descending the design hierarchy. Use this variable only when running Verilog netlister. csiStopListVerilog = '("system" "verilog" "dc" "symbol") Specifies which cells the Verilog netlister stops at as it traverses the design hierarchy. If the netlister finds one of the stopping views in the csiViewListVerilog variable, the netlister does not expand that particular cell. This variable works only with the Verilog netlister running through CSI. Command File If you want to customize the command file, which is an input file to the Design Compiler, add the following variables to your .cdsinit file. csiMinInteractive = nil Specifies that you want to run synthesis in interactive mode without transferring the design data to the Synopsys Design Compiler through CSI. When you use this variable, CSI creates the command file without including the commands to read in the netlist or to assign constraints. csiAutoGenDesignSymbols = t Generates a Synopsys symbol library that includes cells for symbols of intermediate levels of your design hierarchy. When you set this variable to t, the Run – Build Command File command generates the Synopsys symbol library automatically. csiUseCustomCmdFile = nil Specifies that you want to use a custom command file for the synthesis run. When you set this variable to t, you must also specify the csiCustomCmdFile variable. csiCustomCmdFileList =’("filename1" "filename2"... "filenameN") Specifies a list of available custom command files for the synthesis run. June 2000 18 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI csiCustomCmdFile = "filename" Specifies the name of the custom command file that you want to use as the input for synthesis. Synopsys Library Path If you want to customize the Synopsys libraries, add the following variable to your .cdsinit file. csiSynLinkFiles = "sample.db" Specifies the Synopsys link path. The link file is usually the same library as the Synopsys technology library (the .db file). You can specify more than one library. For more information about when you should or should not use this command, see Selecting Synopsys Options on page 37. Synopsys Software If you want to customize the Synopsys installation path or the tool you use, add the following variables to your .cdsinit file. csiSynopsysBin = "sparc/syn/bin" Specifies the path to the Synopsys executable directory from the Synopsys installation directory. For example, if the Synopsys software is installed at /usr/synopsys and the executable directory is /usr/synopsys/sparc/syn/bin, the value you specify for this variable is sparc/syn/bin. The format for sparc is typically the architecture_name, such as Sun SPARC or SUN4 = "sparc" HP 700 = "hp700" csiSynopsysExec = "dc_shell" Specifies the name of the Synopsys binary executable as either dc_shell or design_analyzer. Remote Synthesis If you want to customize your network environment to run remote synthesis, add the following variables to your .cdsinit file. csiAutomountPrefix = "/net" Specifies the root name in automounting directories across the network. csiRemoteMounting = t Specifies that you want to use NFS mounting when running remote synthesis. When you set this variable to t, CSI accesses all search paths and run directory paths from the remote June 2000 19 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI machine through NFS automounts or hardmounts. If you set this variable to nil, CSI copies the run directory from the local machine to the remote machine for synthesis. csiLocalMountFile csiRemoteMountFile Specifies the mount files for remote synthesis. These variables are strings and there are no default values. Refer to Other Network Environments on page 24 for more information. csiRemoteRunDirRoot = "/tmp" Specifies the name of the remote synthesis run directory. The local run directory is copied to this remote run directory. When using this variable, do not select Use NFS for Remote Synthesis on the CSI Options form. See Selecting CSI Options on page 34. csiRemoteXWindowHome = nil Specifies the root path for csiRemoteHostName X window installation. You must have a remote X environment to run remote synthesis in interactive or minimum interactive mode. Use this variable when your login shell on the remote machine does not include any X window paths. Do not specify this variable if the remote machine is set up for a remote X environment. For example, for the /usr/openwin X window install directory, CSI adds the following command paths in the run file: /usr/openwin /usr/openwin/bin /usr/openwin/demo The value of this variable is a string of path names separated by spaces, as in this example csiRemoteXWindowHome = "/usr/openwin /usr/openwin-2" The default nil means that CSI assumes the “standard setup” for the X window on the remote machine where Synopsys is installed. June 2000 20 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI Compiling the .slib Library File Synopsys Design Compiler requires a target symbol library in Synopsys binary format (the .sdb file) and a target technology library in Synopsys binary format (the .db file) to synthesize and optimize the design input. Synopsys symbol library in text format (.slib file) Compile Synopsys symbol library in binary format (.sdb file) Synopsys Design Compiler Synopsys technology library (.db file) Before Compiling a Symbol Library Typically, the ASIC vendor or library administrator creates the .sdb file by compiling the Synopsys symbol library in text format (the .slib file). Before creating the Synopsys library, decide which Cadence libraries you need (CSI provides the Synopsys libraries for the basic, US_8ths, ripper, and sample Cadence libraries.) The Synopsys target libraries you create must include all the cells referenced in your designs and any other primitive cells you want to use as the target library. Be sure that the Cadence-format library you are using to create the target Synopsys-format library contains: s A symbol view for each cell in the library. The symbol views must have u The correct unit for the UserUnits property. This value must be consistent with all symbol libraries you are using. The Composer default for UserUnits is inches. u The correct value for the DBUperUU property. This value must be consistent with all symbol libraries you are using. The Composer default for DBUperUU is 160. u The correct value for the xSnapSpace and ySnapSpace properties. For best results, set this value equal to the value of the same properties on the schematic view of your user-design library. The Composer default SnapSpace value is 0.0625 (1/16 inches). June 2000 21 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI Compiling a Symbol Library To compile your existing .slib file and create the .sdb file, follow these steps. 1. Initialize CSI as described in Initializing CSI on page 26. 2. From the CSI window select Utilities – Symbol Compilation... The Symbol Compilation form appears. Symbol Compilation 3. From the Source Library cyclic field, select the name of the Cadence library you want to use to create the .slib text file. 4. From the Symbol Library field, select create binary. 5. Click OK. CSI creates the .slib library text file. CSI then creates the Synopsys symbol library in binary format (the .sdb file) using the new .slib text file. If there is an existing .slib file, CSI updates it by adding the following scale values. Note: These are the required values for any library used with CSI. SYMBOLU_PER_ UU = 1.0; METER_PER_UU = 0.0254; ROUTE_GRID = 1024; SNAP_SPACE = 0.0625; If symbols are defined in user units, this variable is set to 1.0. If symbols are in Data Base Units use DBUperUU. Default is 160. Meter per user unit ratio. 0.0254 m/in. Hard-coded constant that represents the number of pixels defined between two grid points. xSnapSpace value of the symbol views in the library. Default is 1/16. June 2000 22 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI SCALE = 1.0 /SNAP_SPACE; The symbols are defined with this scale factor. METER_SCALE = METER_PER_UU/(SCALE * SYMBOLU_PER_ UU * ROUTE_GRID); set_route_grid ( ROUTE_GRID ); set_meter_scale ( meter_scale ); Note: The Cadence ripper.sdb, basic.sdb, US_8ths.sdb, and sample.sdb libraries in the etc/dci/synlibs directory are already updated and compiled with the correct scale values. Setting Up for Remote Synthesis If you want to run synthesis on a remote machine, you must follow the setup instructions for your network environment so that you can use the Network File System (NFS) utility to access files on other machines. CSI creates the NFS path names for input and output files you use in a remote synthesis run. To use NFS in CSI, you perform a different setup depending on the network environment you have. Your network environment can be one of the following types: s “Automounted Network Environment,” where you can access all relevant machines by using an automount prefix and the machine host name in the format // s Global Pathnames Environment on page 24 where pathnames are global across the network s Other Network Environments on page 24 in which you can use neither the automount prefix nor global pathnames to access the relevant machines on your network. Automounted Network Environment To set up CSI for using NFS in an automounted environment, do the following: ® In the .cdsinit file, add the automount prefix to the csiAutomountPrefix SKILL variable. For example csiAutomountPrefix = "/net" June 2000 23 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI The default automount prefix is /net. CSI uses the csiAutomountPrefix variable to create the NFS path names for the input and output files for the synthesis run. Global Pathnames Environment If your network environment lets you access the CSI run directory using the same path for both the remote Synopsys machine and the local machine, set the automount prefix to nil in the .cdsinit file. csiAutomountPrefix = nil When you set this variable to nil, CSI does not modify the path names in the command file and run scripts for remote synthesis. Other Network Environments To set up CSI for using NFS for all other network environment where you cannot use an automount prefix to access the remote machine you need on your network, do the following. 1. Set up two files: the local mount file and the remote mount file. These files may have any name and reside in any directory. If you need help, contact your system administrator. The local mount file describes file systems mounted on the local machine which is running CSI. The remote mount file describes file systems mounted on the remote machine which is the remote Synopsys machine. Each line of the mount file has the following syntax: For example sunshine /usr3/mnt2 /usr/mnt2 Suppose that LocalHost is the name of the local machine, and RemoteHost is the name of the remote machine. Also, suppose that the local mount file for machine LocalHost contains RemoteHost /usr1 sunset /usr3/mnt2 /usr/mnt1 /usr/mnt2 This means the RemoteHost:/usr1 file system is mounted on the LocalHost machine at /usr/mnt1. Similarly, sunset:/usr3/mnt2 file system is mounted on the LocalHost machine at /usr/mnt2. The interpretation of the remote mount file is similar, but it June 2000 24 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI describes the mounted file systems on the remote machine (RemoteHost in this example). You can specify any number of machines and mounts in the mount files. The mount files can apply to an entire environment of multiple machines and multiple CSI users. CSI creates the path names in the command file and runs the scripts according to the information in the mount files. When CSI cannot find the file pathnames using the mount file information, it uses the value you specified for the csiAutomountPrefix variable (default is /net). The mount files let you describe a variety of network environments including hardmount, softmount, and automount file systems. You need only specify relevant file systems to the CSI run. CSI reads the information in the mount files and produces a table. CSI uses this table to create a path name to a file or directory which can be used by the remote Synopsys server. CSI tries each entry in the table and tests each entry to produce a usable path name for the remote server. Thus, the order of the entries in the mount file might matter. If CSI tries all possibilities and fails to create a usable path, CSI tries the automount prefix before aborting. 2. In the .cdsinit file, add the csiLocalMountFile and the csiRemoteMountFile SKILL variables. For example, you can add csiLocalMountFile = "/etc/csimount.local" csiRemoteMountFile = "/etc/csimount.remote" Initializing CIW To open the Command Interpreter Window (CIW) so that you can initialize CSI: ® At the UNIX prompt in your project directory, type one of the following commands depending on your site license s icca & s icds & s icfb & s icms & June 2000 25 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI The Command Interpreter Window opens. Initializing CSI You initialize the CSI environment to create the synthesis run directory and to display the CSI top-level commands. You can initialize the CSI environment s From the CIW on page 26 u To use the CSI top-level menus without opening or editing your design s From a Design Window on page 28 u A schematic, symbol, or read-only text cellview s From the VHDL Toolbox on page 30 u If your input design is in VHDL format, you must use the VHDL Toolbox to initialize CSI. From the CIW When you initialize the environment from the CIW, the CSI window appears. The CSI window displays all the CSI top-level commands and you can perform design synthesis without opening a design window. To initialize CSI from the CIW and display the CSI window, follow these steps. 1. Select Tools – Synopsys Integration... June 2000 26 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI 2. The CSI Initialization form opens. Keep or change the synthesis run directory name in the Run Directory field. Keep the default run directory name (dci.run1) or enter a different name. CSI assumes the current directory as the location for the run directory, you do not have to type the whole pathname. Each time you open a design in CSI, you must create a new run directory or reinitialize an existing run directory. After the first CSI initialization, you have three choices for the run directory: a. Type the name of a new run directory. b. Type the name of an existing run directory. c. Keep dci.run1 as the name of the run directory. 3. Click on Browse. The Library Browser opens. 4. Select the library name, cell name, and the view name of your design. The CSI Initialization form is automatically filled in when you make your selection from the Library Browser. For information about how to select a design using the Library Browser, refer to Composer: Design Entry User Guide. 5. Click OK. June 2000 27 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI The CSI window opens. This window lets you use the CSI top-level menu commands to synthesize your design without opening a Composer or HDL design window. Note: The Session menu command that appears in the CSI window includes the following two additional commands: Session – Environment – Change Design Session – Close From a Design Window To initialize CSI from a design window and display the CSI top-level commands, follow these steps. 1. Select File – Open... from the CIW. Design Framework II displays the Open File form. 2. Fill in the Open File form to display your design in a schematic, symbol, or text window. Your design can include any of the following view types: u Cadence schematic view (the schematic view) Select the edit mode in the Open Design form when opening a schematic or symbol view of your design. u Cadence connectivity-only schematic view (the opt_sch view) This view does not contain any graphical information. June 2000 28 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI u Verilog HDL view (the functional view) Note: You must select the read mode in the Open File form to get the tool banner to appear on the text view. 3. Select Tools – Design Synthesis – CSI from the design window banner. CSI displays the CSI Initialization form. CSI fills in the Library, Cell, and View Name fields and you cannot change them. 4. Keep or change the synthesis run directory name in the Run Directory field. Keep the default run directory name (dci.run1) or enter a different name. CSI assumes the current directory as the location for the run directory, you do not have to type the whole pathname. Each time you open a design in CSI, you must create a new run directory or reinitialize an existing run directory. After the first CSI initialization, you have three choices for the run directory: a. Type the name of a new run directory. b. Type the name of an existing run directory. c. Keep dci.run1 as the name of the run directory. 5. Click OK. The design window banner changes to display the top-level CSI commands (Session, Utilities, and Run). June 2000 29 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI Here is a sample of a text (functional view) design window banner with the CSI top-level commands after initializing CSI. Tools Design Session Utilities Run From the VHDL Toolbox If your design is VHDL, you must initialize CSI from the VHDL Tool Box in order to get the VHDL netlisting option. To open a design from the VHDL Tool Box, initialize CSI, and display the CSI top-level commands, follow these steps. 1. From the CIW, select Tools – VHDL Toolbox... Design Framework II displays the VHDL Tool Box window. 2. Select Setup – Synthesis... The VHDL Set Up Synthesis form opens. 3. Select Synopsys from the Synthesis Tool list. June 2000 30 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI 4. Click OK. 5. Click Browse under Top of Hierarchy or Working Cellview. The Library Browser opens. 6. Select the library name, cell name, and the view name of your design. The CSI Initialization form is automatically filled in when you make your selection from the Library Browser. For information about how to select a design using the Library Browser, refer to Composer: Design Entry User Guide. 7. Select Commands – Synthesis The netlister runs, CSI reads the netlist and displays the CSI Initialization form. CSI fills in the Library, Cell, and View Name fields and you cannot change them. Note: You must re-initialize CSI every time you create a new netlist for synthesis. You can use different run directories for different netlists. 8. Keep or change the synthesis run directory name in the Run Directory field. Keep the default run directory name (dci.run1) or enter a different name. CSI assumes the current directory as the location for the run directory, you do not have to type the whole pathname. Each time you open a design in CSI, you must create a new run directory or reinitialize an existing run directory. After the first CSI initialization, you have three choices for the run directory: a. Type the name of a new run directory. b. Type the name of an existing run directory. June 2000 31 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI c. Keep dci.run1 as the name of the run directory. 9. Click OK. The CSI window opens. This window lets you use the CSI top-level menu commands to synthesize your VHDL design. Note: The Session menu command that appears in the CSI window includes the following two commands for using CSI with VHDL Toolbox: Session – Environment – Change Design Session – Close Creating a Symbol Library When your design includes symbols of intermediate levels of design hierarchy, you need to compile these symbols and create a Synopsys symbol library before running synthesis. Otherwise, the imported design from Synopsys will have instances of new symbols that differ by either size or shape from the original symbols. The new symbols could adversely affect net connectivity. To create a Synopsys symbol library for the symbols of intermediate levels of the design hierarchy, follow these steps. 1. Select Utilities – Symbol Compilation. June 2000 32 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI The Symbol Compilation form appears. 2. Click and hold the Source Library cyclic field to select the Cadence source library. 3. If you want to create a symbol library that contains only a subset of the cells from the Cadence library u Select the User-Supplied Cell Names button. u In the Cell Names File field, specify the name of the file that contains the cells in the subset. 4. From the Symbol Library field, select create binary. 5. Click OK. CSI creates the symbol library (.slib) in Synopsys text format using the symbol views from the source library, and then compiles the .slib file to create the .sdb file, the symbol library in Synopsys binary format. You will use the symbol library you compiled in the Symbol Library field of the Synopsys Options form. This form is described in Selecting Synopsys Options on page 37. The dciLib.dc file logs any messages generated by the Symbol Compilation command. For more information about this file and other files generated by Symbol Compilation, see Appendix A, “Files in the Synthesis Run Directory.” For information about the syntax Synopsys requires for a text library file, refer to the Synopsys Library Compiler Reference Manuals. Note: The Run – Build Command File command can build symbol libraries automatically for any hierarchical cells which have a dont_touch constraint. These symbol libraries, when built, are also automatically added to the Symbol Libraries field. You can control this automatic symbol generation option by selecting Session – Setup – CSI and selecting Generate Design Symbols on the CSI Options form. June 2000 33 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI Selecting CSI Options CSI lets you select the s Display mode for the Show command s Netlist format for exporting the design s CSI command file options u Use a custom command file u Automatically generate design symbols s Synopsys run options u Tool execution mode u Executable name u Use NFS for remote synthesis s Import design options u Netlist format for importing the design u Automatically import design after batch synthesis u Automatically delete remote files after importing design A more detailed explanation of each of the options is contained in the steps for selecting them. To select any of these options, follow these steps. 1. Select Session – Setup – CSI. June 2000 34 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI The CSI Options form appears. 2. Select read or edit to set the display mode for the files in the synthesis run directory. If you want to display the run directory files, select read. If you want to edit the run directory files, select edit. For example, to add synthesis commands to the all.cmd file, which is an input file to the Design Compiler, you need to select the edit mode. 3. Select EDIF netlist or Verilog HDL as the netlist format from the Netlist Format cyclic field for exporting the design to Synopsys. If your design is Verilog HDL or a combination of Verilog HDL and schematics, select Verilog HDL. If your design is a schematic, select Verilog HDL or EDIF netlist. If you started CSI from the VHDL Tool Box, you can only select the VHDL format. 4. Select Use Custom Command File. Click on the Command File Name field to select the custom command file for this synthesis run. June 2000 35 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI This step is optional. The desired custom command file must already exist. For information about creating custom command files, see Chapter 3, “Utilities – Custom Command File Menu.” 5. Select Generate Design Symbols if your design has schematic symbols of intermediate levels of the design hierarchy. 6. Select batch, interactive, or minimum interactive for running synthesis. batch lets you run the Design Compiler in batch mode when you select the Run – Synopsys command. interactive and minimum interactive let you run the Design Compiler or the Design Analyzer in interactive mode depending on what you select in the Executable Name field. The difference between the interactive and the minimum interactive mode is that in the interactive mode CSI transfers your design data and the constraints file to the Design Compiler, but in the minimum interactive mode CSI does not transfer any design data or constraint information. The minimum interactive mode is for the advanced user of the Synopsys tools. When using the interactive or the minimum interactive mode, to ensure that the synthesized design in EDIF format has the correct file name, parameters, and is readable by CSI, you must use the following Design Compiler alias commands: cadence_schematic_out cadence_netlist_out For a schematic netlist file EDIF netlist-only file (no schematic data, only connectivity information) These aliases are defined in the .synopsys_dc.setup file. For information about the .synopsys_dc.setup file, see Appendix A, “Files in the Synthesis Run Directory.”. 7. Select dc_shell to run the Design Compiler or design_analyzer to run the Design Analyzer from Executable Name. You can select design_analyzer only if you selected interactive or minimum interactive Tool Execution Mode. 8. Select Use NFS for Remote Synthesis, if you want to use the NFS utility to run synthesis on a remote machine. When you select this button, CSI accesses the run directory files across the network rather than copying the files from the remote machine to your local machine. Use this option as much as possible to save copying time. June 2000 36 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI When you select this button, all path names in the command input file and in the invocation script use NFS path names. For information about how to set up CSI to use NFS, see Setting Up for Remote Synthesis on page 23. If you want to run synthesis on a remote machine without using the NFS utility, deselect this button. In this case, CSI copies the symbol and target libraries referenced in the Synopsys Options form (using the Session – Setup – Synopsys command) to the local run directory, so that when CSI copies the run directory to the remote machine, it contains all the necessary data to run the synthesis job remotely. You can specify the remote machine run directory name in Remote Run Directory Root. 9. Specify the remote machine run directory name in Remote Run Directory Root. This field is available only when you deselect Use NFS for Remote Synthesis. 10. Select a format from the Design Import Format cyclic field for importing the design from Synopsys. When you select batch for Tool Execution Mode, the Design Import Format field lets you select the type of design format you want the Design Compiler to write. The two formats you can select are Schematic or Netlist-only. When you select interactive or minimum interactive for Tool Execution Mode, you choose the import format by specifying the cadence_schematic_out alias or the cadence_netlist_out alias while in the Design Compiler. See Running Synthesis on page 44 for more information about an interactive run and the use of these aliases. 11. Select Import Design After Batch Run, if you want to run the edifin program after each Synopsys run is done. You can deselect this button if you don’t want to run edifin every time you run a synthesis job. 12. Select yes, no, or ask me for Delete Remote Files After Import. When debugging your design, select no or ask me. 13. Click OK. Selecting Synopsys Options CSI lets you select any machines on the network, the location of the Synopsys library and design text, the names of the symbol libraries, the target libraries, and any link files for the Synopsys Design Compiler. To select any of these options, follow these steps. June 2000 37 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI 1. Select the Session – Setup – Synopsys command. The Synopsys Options form appears. 2. Verify or change the Synopsys Installation Path. This is the path to the Synopsys software. 3. If the Synopsys software is installed on a remote machine, select remote. When you select remote the Remote Hostname field becomes highlighted and available. 4. If you selected remote, specify the remote machine name in Remote Hostname. 5. Verify or change the Synopsys Search Path. The Synopsys Search Path specifies the Synopsys symbol libraries (the .sdb files) and technology libraries (the .db files). This search path is different from the Cadence library search path. 6. Verify or change the Symbol Libraries. You can specify more than one library. 7. Verify or change the Target Libraries. You can specify more than one library. 8. If your source design is a behavioral description, do not specify a Link file name. June 2000 38 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI The Link file name is usually the same as the Target Library name. Specify the name of a Link File if you want to u Optimize a schematic and the target library is different from the source library (the cells in the schematic come from the source library) u Map your design from one library to another library The Link command in Synopsys resolves design and library component references for the design. For more detail about the Synopsys Link command, see the Synopsys Design Compiler Family Reference and Command Reference for Synthesis Manuals 9. Click OK. After setting the CSI and Synopsys options you are ready to apply constraints to the design as described next. Editing Constraints Synopsys Design Compiler requires design constraint information to synthesize a design. CSI extracts the constraints that you apply to the design and creates a command file for input to the Design Compiler. Basically, there are two types of constraints. Design rule constraints and optimization constraints. Design rule constraints are technology specific restrictions that must be met for a functional design. Optimization constraints represents design goals and restrictions that are desirable but not crucial for the operation of the design. Design Compiler tries to meet both types of constraints, but gives emphasis to design rule constraints. To set and apply design constraints, follow these steps. 1. Select Session – Edit Constraints. u For a schematic design, the Constraints form appears. This form lets you set and edit synthesis constraint properties for the top-level schematic and design objects you select on the schematic in the current window. June 2000 39 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI u For a Verilog HDL design, the Top-Level Design Constraint form appears. The following steps do not apply to Verilog HDL designs. For information about the TopLevel Design Constraint form, see Chapter 3, “Session – Edit Constraints.”. 2. Select the types of schematic object from the Object Type field to which you want to apply constraints. For example, to apply constraints to the instances in your schematic select instances. The default is top-level design. You can select more than one type of schematic object. 3. Click OK. If top-level design was selected, the Top-Level Design Constraint form opens. Refer to Chapter 3, “Top-Level Design Constraints Subform” for information on filling out this form. After the Top-Level Design Constraints form is dismissed, Composer prompts you to select an object on the schematic. 4. In your schematic, select the same type of schematic object you selected in the Object Type field of the Constraints form. The subform for the object you selected appears. The subforms display any existing constraint values stored on the selected object. For example, if you selected instances in the Constraints form, when you select an instance in the schematic (by clicking the left mouse button on the instance), the Instance Constraint subform appears. If you selected more than one object type, the subform for the first selected object type appears. 5. For each subform, type the constraint values and the run options. Refer to the Synopsys Design Compiler Family Reference Manual for information about the constraint values to use in the fields of the Constraints subforms. 6. Click OK. June 2000 40 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI The Session – Edit Constraints command applies the constraints you entered to the object and then displays the subform for the next object type you selected. When you are finished with the last subform, Composer prompts you for another selection. If you select Cancel rather than OK, the Session – Edit Constraints command discards the entries and displays the next subform, or returns you to the CIW. 7. Press the Esc key to indicate end of object-selection. The Session – Edit Constraints command continues to bring up forms and Composer continues to prompt for another selection until you indicate the end of object selection. Exporting the Design Exporting a design means netlisting the design and transferring the design data from the Cadence Design Framework II environment to the Synopsys Design Compiler. To export your design: ® Select Run – Export Design. CSI creates the netlist file according to your Export Format selection on the CSI Options form. If you have selected EDIF netlist for your schematic design, CSI uses the edifout program to create the netlist. If you selected Verilog HDL for your mixed-level design or a design in Verilog HDL format, CSI uses the Cadence Verilog netlister to create the netlist. The netlist file contains the design connectivity data as the input to the Synopsys Design Compiler. You can display the netlist file by using the Utilities – Show – Other File command and selecting netlist from the cyclic field. Note: If you are using the VHDL Tool Box for your synthesis run, you must create a netlist of your design before initializing CSI. When you set up CSI, VHDL is the only choice for export format on the CSI Options form. The Run – Export Design command prepares the existing netlist file and transfers it to the Synopsys tool. Building the Command File After you edit and apply the design constraints, you must create a command file. The Synopsys Design Compiler uses the command file to control and run synthesis. You can use the default command file, or create and use a custom command file. June 2000 41 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI Creating the Default Command File To create the default command file: ® Select Run – Build Command File. CSI creates the default command file, all.cmd. CSI uses the all.cmd file as an input to the Synopsys tool, unless you tell CSI to use a custom command file. The all.cmd file contains five command file sections. CSI also creates a file called inc.cmd that contains Synopsys include commands.The five included files correspond to the five sections of the all.cmd file. For more information about the all.cmd and inc.cmd file, see Chapter 3, “Run – Build Command File.” You can display the all.cmd command file by selecting Utilities – Show – Command File. Creating a Custom Command File You can create a custom command file for a synthesis run in batch mode. CSI can use the custom command file instead of the all.cmd file. There are two ways to create a custom command file: s “Using a Template” for new custom command files s Using SKILL on page 43 and custom command files from other directories Using a Template After selecting the Run – Build Command File command to create the all.cmd and inc.cmd command files, you can use all.cmd or inc.cmd or any previously defined command file as a template. To create a custom command file from a template, follow these steps. 1. Select Utilities – Custom Command File – Create. June 2000 42 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI The Create Custom Command File form appears. Create Custom Command File 2. Type a name for the command file you want to create. 3. Select a file from Template File Name as the template file for creating your custom command file. When you click and hold this cyclic field, the command files that CSI maintains in the current run directory appear. The list of files that appear include the all.cmd file, inc.cmd file, and any custom command files that you have previously created. 4. Click OK. CSI copies the template file you selected to the file name you specified on the form, and displays the custom command file for you to edit. When editing the command file, make sure that the Design Compiler can read the file by using legal Synopsys commands and the correct syntax. CSI doesn’t check the custom command file for correctness. Using SKILL If you have existing custom command files from other run directories or from another project, you can tell CSI to list them in the Command File Name field on the CSI Options form by using this SKILL command: csiCustomCmdFileList =’("filename1" "filename2"... "filenameN") You can put this command in your .cdsinit file. or you can type it into the CIW command window before you initialize CSI. You can use relative pathnames for the filenames. Using a Custom Command File CSI manages the custom command file on a run directory basis, therefore each run directory can have a different set of command files. To use your custom command file for the synthesis run, you can do one of the following: June 2000 43 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI s Display the CSI Options form and select Use Custom Command File. When the Command File Name field appears, select the name of the custom command file that you want to use for this run. s Use these SKILL commands: csiUseCustomCmdFile = t specifies that you want to use a custom command file for the synthesis run, when you set this variable to t, you must also specify the csiCustomCmdFile variable csiCustomCmdFile = "filename" specifies the name of the custom command file that you want to use as the input for synthesis You can put these commands in your .cdsinit file. or you can type them into the CIW command window before you initialize CSI. You can use a relative pathname for the filename. Running Synthesis Typically, you synthesize a design iteratively using the Run – Synopsys command. After each synthesis run, you analyze the design. If the results do not meet the design specifications, you run synthesis again with different constraints and run options. To synthesize your design: ® Select Run – Synopsys. Depending on your selection when you used the Session – Setup – CSI command, the Design Compiler runs in batch or interactive mode, or the Design Analyzer runs in interactive mode. After the synthesis run is complete, you can display a number of log and report files. The following table shows the log and report files. File name dci.log dci.runout Contains Messages from the Run – Synopsys Command Messages from the Design Compiler To display the file select Utilities – Show – CSI Log File Utilities – Show – DC Log File June 2000 44 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI File name dci.report Contains To display the file select Circuit characteristics, such as timing, area, Utilities – Show – and synthesis constraints data. The content DC Report of this file depends on the latest settings you select from the Report Options subform of the Session – Edit Constraints command. Design Compiler in Batch Mode For more information about these files and other files generated during design synthesis, see Appendix A, “Files in the Synthesis Run Directory.” When you run the Design Compiler in batch mode, CSI starts the Synopsys dc_shell program as a process running outside the Cadence environment. CSI monitors the dc_shell process and determines when it has completed. Monitoring a Batch Run When running synthesis in batch mode, you can monitor the run status. 1. Select Utilities – Show – Job Monitor. The Analysis Job Monitor form appears. 2. Select the job you want to monitor from the Run Directory field. 3. Select Show Run Log from the top of the form. A window appears showing the log file for the job you selected. 4. If you want to change the priority of a job, click Set Priority. A dialog box appears. In the dialog box click and drag the bar in the Job Priority field and click OK. June 2000 45 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI 5. If you want to terminate a job, click Kill. A dialog box appears asking you to confirm that you want to kill the job. 6. If you want to stop a job, click Suspend. The status for the job you select will appear as suspended. 7. If you want to restart a job, click Continue. The status for the job you select will appear as running. 8. If you want to delete a job from the Analysis Job Monitor form, click Delete. A dialog box appears asking you to confirm that you want to delete the job. CSI does not stop the synthesis run, it only removes the job from the form. You can still look at the log file to see the output. June 2000 46 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI Design Compiler in Interactive Mode When you run the Design Compiler in interactive mode, CSI creates an xterm window and starts dc_shell in the xterm window. Entering the quit command to the dc_shell program, deletes the window immediately after the dc_shell process terminates.Your X window configuration can affect the appearance of the xterm window. When you synthesize your design using the Design Compiler in interactive or minimum interactive mode, you need an EDIF file to import the synthesized design from Synopsys into Cadence. Synopsys can write the correct file name and parameters to the EDIF file when you use the following Design Compiler alias commands: cadence_schematic_out cadence_netlist_out For a schematic netlist file EDIF netlist-only file (no schematic data, only connectivity information) These aliases are defined in the .synopsys_dc.setup file. For information about the .synopsys_dc.setup file, see Appendix A, “Files in the Synthesis Run Directory.” Note: CSI does not create the dci.runout log file in the run directory for interactive runs. Design Analyzer in Interactive Mode When you want to run the Design Analyzer in interactive mode, CSI specifies the local machine as the display terminal and starts the design_analyzer program. Once the Design Analyzer window appears, you can access the Design Analyzer commands. For more information on the commands, see Synopsys Design Analyzer Reference. Importing the Synthesized Design Importing a design means copying the synthesized design from the Synopsys Design Compiler to the Cadence Design Framework II environment. The type of design format that the Design Compiler writes depends on the import format you selected when you used the Session – Setup – CSI command for a batch synthesis run, or the Design Compiler command alias you used in an interactive synthesis run. To import your design: ® Select Run – Import Design. June 2000 47 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI CSI creates the .optToCds UNIX shell script that u Runs the awk utility to preprocess the EDIF netlist (the dci.edif file) u Runs the edifin program on the preprocessed EDIF netlist (the dci.edifin file) If you get an edifin failed message, see the files edifin.log and edifin.errs, the log and error message files from the edifin program. CSI imports the synthesized design to a library called DESIGNS in the main CIW directory. CSI modifies the cds.lib file to include the DESIGNS library. Note: If you have selected the Import Design After Batch Run option in the CSI Options form, CSI runs edifin and imports your design automatically after running the Synopsys tool. Examining the Synthesized Design You can display the synthesis results before installing the design. To display your synthesized design: ® Select Session – Show – Synthesized Design. CSI opens a schematic window and displays your synthesized design. The view name for the synthesized schematic design is schematic, and this design resides in the DESIGNS library in the main CIW directory. CSI modifies cds.lib to include the DESIGNS library. You can also use Session – Show to display the default report file, the dci.report file, or any other report file you specified on the Constraints subform. Installing the Synthesized Design After you have viewed the design and are satisfied with the reports, you can install the synthesized and optimized design. Installing a design means saving the synthesized and optimized cellviews to the source library of the design. You can save your original source library by copying it to a different name before you install the synthesized design. To install your design, follow these steps. 1. Select Run – Install Synthesized Design. June 2000 48 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI The DFII Library Manager Copy form opens. The following instructions are for the Simple Copy Option form. For more information, click Help on the Copy form. 2. Install cellviews To install all of the cellviews from the synthesized design into the source design, click Select All. To install some of the cellviews, click Deselect All; click in the boxes at the far left of the form to select the cellviews that you want installed. A green dot indicates your selection. 3. Click OK. The Copy process begins and the hourglass window opens. June 2000 49 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Using CSI If you click Cancel, the Copy command does not complete. If you click OK, the hourglass window closes, and the Copy command continues to run. When the Copy is completed, CSI saves the synthesized and optimized cellviews to the library you specified. You can now use your synthesized design in simulation and timing analysis. June 2000 50 Product Version 4.4.0 Cadence to Synopsys Interface User Guide 3 Session, Utilities, and Run Menu Commands Introduction When you select the Tools – Design Synthesis – CSI command from your design window banner and click OK on the CSI Initialization form, the CSI top-level menus appear on the design window. The CSI top-level menus are Session, Utilities, and Run. This chapter describes the menu commands in the order in which they appear on the menus. A typical synthesis run uses the commands in a top-to-bottom order as shown here. Design Session Utilities Run Environment → Setup → Edit Constraints... Show → Symbol Compilation... Custom Command File → Export Design Build Command File Synopsys Import Design Install Synthesized Design... June 2000 51 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Session Menu Session Utilities Run Environment→ Setup→ Edit Constraints... Environment lets you change the current synthesis run directory and deletes an existing remote synthesis run directory. Setup lets you choose the environment and run options for CSI and Synopsys tools. It also lets you specify the netlisting options when using Verilog as the export format. Edit Constraints lets you apply and modify constraints for design objects and for the toplevel schematic. June 2000 52 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Session – Environment Menu Session Utilities Environment→ Setup→ Edit Constraints... Run Change Run Directory... Delete Remote Run Directory Change Run Directory lets you change the current synthesis run directory to a new or existing run directory. Delete Remote Run Directory deletes an existing synthesis run directory on the remote server. June 2000 53 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Session – Environment – Change Run Directory Session ¿ Environment ¿ Change Run Directory… Lets you change the current synthesis run directory to a new or existing run directory. When you change the run directory from a design window, the window stays open and you do not need to reinitialize the CSI environment. Change Run Directory Form Run Directory is the only field you can edit on this form and is the name of a new or an existing run directory. SKILL Function csiChangeRunDir() June 2000 54 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Session – Environment – Delete Remote Run Directory Session ¿ Environment ¿ Delete Remote Run Directory Deletes an existing synthesis run directory on the remote server. When you run synthesis on a remote server (with the following selections in the CSI Options form: no for Delete Remote Files After Import and deselect NFS for Remote Synthesis), CSI copies and saves the local synthesis run directory to the remote machine. Later, when you want to delete the remote run directories, you can use the Delete Remote Run Directory command. SKILL Function csiDeleteRemoteRunDir() June 2000 55 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Session – Setup Menu Design Session Utilities Environment→ Setup→ Edit Constraints... Run CSI... Synopsys... Verilog Netlister... CSI lets you set the display mode for the Show command, select a netlist format for exporting the design, select Synopsys tools run options, select a format for importing a design, select a command file, and specify if you want to use NFS for remote synthesis. Synopsys lets you specify the location of the Synopsys tool, the name of the symbol libraries, the target ASIC kit, the target libraries, and any link files for the Synopsys Design Compiler. Verilog Netlister lets you select netlisting options when you want to use Verilog as the netlist format for transferring your design data to the Design Compiler. June 2000 56 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Session – Setup – CSI Session ¿ Setup ¿ CSI... Lets you set the display mode for the Show command, select a netlist format for exporting the design, select the run options for the Synopsys tools, select a format for importing a design, and specify any machines on the network. CSI Options Form The options you set on the CSI Options form are saved while you are in the Composer environment, even if you quit CSI. Show File Command Mode lets you specify whether you want to display run directory text files or display and edit them. You can change the mode any number of times without affecting other commands. The change in mode takes effect when you use the Utilities – Show menu commands. The default is the read mode. June 2000 57 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands read lets you display but not edit the run directory files. Read mode makes Utilities – Show menu commands equivalent to the Show File command on the CIW Open menu. edit lets you display and edit the run directory files. Edit mode makes Utilities – Show menu commands equivalent to the Text Editor command on the CIW Open menu. You must select the edit mode to modify any text files, such as the command file (the all.cmd file). This file contains the input commands to the Design Compiler for running synthesis. Netlist Format lets you select a netlist format (EDIF netlist or Verilog HDL) from the cyclic field for exporting the design to Synopsys. If your input is a . . . Schematic design Verilog HDL description Combination of schematic design and Verilog HDL description Netlist format to select is . . . EDIF netlist or Verilog HDL Verilog HDL Verilog HDL If you are using CSI from the VHDL Tool Box, you can select only VHDL as the netlist format. CSI uses the VHDL netlist that it read during initialization. You must re-initialize CSI every time you create a new netlist to synthesize. Use Custom Command File lets you specify whether you want to use custom command file or the command file created by the Run – Build Command File command. You can select this button only if you have created one or more custom command files. Once you select this button, a second form field appears to let you select the command file to use from the current list of custom command files in the current run directory. Generate Design Symbols lets you specify whether or not you want CSI to automatically generate symbols for the intermediate levels of your design hierarchy. Tool Execution Mode lets you select batch, interactive, or minimum interactive mode for running synthesis. batch runs the Design Compiler in batch mode. CSI generates a command file that contains all the Synopsys commands necessary to read-in the design, run synthesis and optimization, generate the schematic, and writeout the EDIF file. The Synopsys tools starts in batch mode with the command file as an input. Note: If you select batch, set Executable Name to dc_shell. June 2000 58 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands interactive runs the Design Compiler or the Design Analyzer in interactive mode. For interactive runs, CSI generates a command file that does not include the Synopsys commands to optimize, generate a schematic, or write the output EDIF file. The command file only initializes, specifies the constraints, and reads in the input netlist. The Design Compiler starts in an xterm window, and the command file is read in. After the last command, the prompt appears in the window, and you can enter interactive commands. The Design Analyzer starts in the Synopsys Design Analyzer window, the command file is read in, and you can use the interactive commands. minimum interactive runs the Design Compiler in interactive mode. The minimum interactive mode is for the advanced user of the Synopsys tools. The difference between the interactive and the minimum interactive mode is that in the interactive mode CSI transfers your design data and the constraints file to the Design Compiler, but in the minimum interactive mode CSI does not transfer any design data or constraint information. When using the interactive or the minimum interactive mode, to ensure that the synthesized design in EDIF format has the correct file name, parameters, and is readable by CSI, you must use the following Design Compiler alias commands: cadence_schematic_out cadence_netlist_out For a schematic netlist file EDIF netlist-only file (no schematic data, only connectivity information) These aliases are defined in the .synopsys_dc.setup file. For information about the .synopsys_dc.setup file, see Files in the Synthesis Run Directory on page 105. Executable Name lets you select the Synopsys tool you want to run from the cyclic field. You can select dc_shell to run Design Compiler or design_analyzer to run Design Analyzer. Note: If you select design_analyzer, set Tool Execution Mode to interactive. Use NFS for Remote Synthesis lets you specify whether or not CSI must use the Network File System (NFS) utility to specify the location of the files for a remote synthesis run. If you do not select this option, the run directory is copied to the remote machine. If you select this option, the run directory is not copied, but the input files in the command input file and the job execution scripts are modified to use path names so that the remote machine can find the files. Depending on the type of your network environment, you perform a different setup for using NFS. Refer to Setting Up for Remote Synthesis on page 23 for more information. June 2000 59 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Remote Run Directory Root lets you specify a remote run directory name when you don’t want to use NFS. You must deselect Use NFS for Remote Synthesis on the CSI Options form. Design Import Format lets you select a format from the cyclic field for the EDIF file from Synopsys. You can select Schematic or Netlist-only. The Schematic format contains schematic information, including graphics. The Netlist-only format contains connectivity information, a schematic with no graphics. Import Design After Batch Run lets you specify whether or not you want to automatically start the Run – Import Design command after the Synopsys batch run is done. Delete Remote Files After Import lets you select one of three choices for handling the remote run directory after a remote synthesis run, when not using the Network File System (NFS). yes deletes the remote run directory after the remote synthesis run. no does not delete the remote run directory after the remote synthesis run. ask me prompts you about whether or not you want to delete the remote run directory after the synthesis run. SKILL Function csiSetupCSI() June 2000 60 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Session – Setup – Synopsys Session ¿ Setup ¿ Synopsys... Lets you specify the location of the Synopsys library and design text, the name of the symbol libraries, the target libraries, and any link files for the Synopsys Design Compiler. Synopsys Options Form The options you set in the Synopsys Options form are saved while you are in the Composer environment, even if you quit CSI. Synopsys Installation Path is the UNIX directory path to the local or the remote machine where the Synopsys software is installed. The default is /synopsys. Synopsys Execution lets you specify whether you want to run synthesis on your local or a remote machine. Remote Hostname lets you specify the machine name where the Synopsys software is installed when you select remote for Synopsys Execution. This name can be any host machine on your network. The default is localhost that indicates your local machine. June 2000 61 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Synopsys Search Path is the directory that contains the Synopsys library files and design text files. The directory path name in this field defines the search_path Design Compiler variable. The directory path names must be relative to the local Synopsys run directory and separated by a space. The default is set by the csiSynopsysLibPath SKILL variable. When you run a remote synthesis, CSI searches all design files using this directory path and copies the design files to the local run directory before copying the files to the remote run directory. Symbol Libraries are the name of the Synopsys symbol libraries (the .sdb files) that CSI uses as the target symbol libraries for synthesis. The library name defines the symbol_library Design Compiler variable. The default is csiSynSymbolLibs. Target Libraries are the Synopsys technology libraries (.db files) that CSI uses for synthesis. This library name defines the target_library Design Compiler variable.The default is csiSynTargetLibs value. Link File is an optional field and is the Synopsys technology library file name. Synopsys uses this file to resolve design references. The link file defines the link_library Design Compiler variable. The default is csiSynLinkFiles value. SKILL Function csiSetupSynopsys() June 2000 62 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Session – Setup – Verilog Netlister Session ¿ Setup ¿ Verilog Netlister... Lets you specify netlisting options for a netlist in Verilog HDL format. Verilog Netlist Options Form View List lets you verify or edit the order in which the views are search by the Verilog netlister. Stop List lets you verify or edit the order in which the Verilog netlister stops the search sequence once it finds a view. For example, the netlister stops when it finds the system view. If it can’t find system it will stop at the verilog view and so on. Preserve Buses lets you specify whether or not you want to keep the buses in your netlist the same way you specified them in you design. Select this button if you do not want to expand buses to single-bit signals in the netlist. Deselect the button for bit netlisting. Netlist Explicitly lets you specify whether you want to generate name-based port lists or order-based port lists. Select this button to generate name-based port lists (using connection-by-name syntax) for modules in Verilog views. Deselect this button to generate order-based port lists. This button does not apply to instances whose master module is generated by the netlister. For example, the netlister converts all schematics into Verilog modules. For instances of these modules, the netlister always creates order-based port lists. June 2000 63 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Netlist Uppercase lets you specify whether or not you want to generate the netlist names all in uppercase letters. Global Power Nets lets you specify the global power net name that you want netlisted with supply1 wire types. Global net names must end in an exclamation point as shown in this example VDD! Global Ground Nets lets you specify the global ground net name that you want netlisted with supply0 wire types. Global net names must end in an exclamation point as shown in this example GND! June 2000 64 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Session – Edit Constraints Session ¿ Edit Constraints... Lets you apply and modify constraints for design objects and for the top-level schematic. Constraints Form This form appears for a schematic design. Object Type lets you select the type of object for which you want to apply constraints. To display the subform for the type of objects you select, first you must select that object from the schematic window. The default is the top-level design button, in which case you do not need to select any objects from the schematic window. top-level design lets you set constraints on the top-level schematic of the design. instances lets you set constraints on the instances in your schematic. instance pins lets you set constraints on the instance pins in your schematic. input pins lets you set constraints on the input pins in your schematic. output pins lets you set constraints on the output pins in your schematic. nets lets you set constraints on the nets in your schematic. select all types lets you set constraints on all of the objects listed above. The Constraints subforms are shown in the following section. June 2000 65 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Important For information about the constraint values to use in the fields of the Constraints subforms, refer to the Synopsys Design Compiler Family Reference Manual. Using the Constraints Form When you select Edit Constraints the Constraints form appears. From the Constraints form of a schematic design, you can display the following subforms: Top-Level Design Constraints Instance Constraints Instance Pin Constraints Input Pin Constraints Output Pin Constraints Net Constraints To display the subforms, except the Top-Level Design Constraints form, first you must select the corresponding object from the schematic. For example, if you select Input Pin on the Constraints form, you must select an input pin from the schematic to display the Input Pin Constraints form. From the Top-Level Design Constraint subform, you can display the following subforms: Text Description Plot Options Create Schematic Options Report Options SPF Options Finite State Machine Options Register Attributes Additional Output Formats The structure of the Constraint form and subforms is shown next. June 2000 66 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Constraints Form and Subform Names Constraints Top-Level Design Constraints Instance Constraints Instance Pin Constraints Input Pin Constraints Output Pin Constraints Net Constraints Instance Compile Constraints Plot Options Create Schematic Options Report Options Finite State Machine Options Register Attributes Additional Output Formats Text Description SPF Options June 2000 67 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Top-Level Design Constraints Subform When you select top-level design on the Constraints form, the Top-Level Design Constraints subform appears. For information about the constraint values to use on the Top-Level Design Constraints form, refer to the Synopsys Design Compiler Family Reference Manual. Read SDF File is the name of the Standard Delay Format file to use for running synthesis. When you run synthesis by using the Run – Synopsys command, CSI automatically reads the SDF file you specified, maps the names in this file to Verilog HDL names, and creates a new SDF file in the synthesis run directory with the same name plus an .export extension. This new SDF file and the Verilog HDL netlist are two inputs to the Design Compiler and the names in these two files are consistent. Write SDF File is the name of the SDF file that you want Synopsys to generate. When you use the Run – Build Command File command, CSI creates a command file, the all.cmd file, that includes the name of the SDF file you specified. Other Options lets you specify any other Synopsys constraint commands. Be sure to use the Synopsys format when entering the command. June 2000 68 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Text Description Subform When you select Text Description in the Top-Level Design Constraints subform, the Text Description subform appears. File Name lets you specify a list of additional design files that you want to transfer to the Synopsys tool. Text Format lets you specify a list of formats for each of the files in the File Name field. File Name and Text Format must contain the same number of items in the list. Sub-Design File Names lets you specify a list of design files for any sub-cells in the design that you want to transfer to the Synopsys tool. Sub-Design Text Formats lets you specify the list of formats for each of the files listed in Sub-Design File Names. Plot Options Subform dont_touch lets you specify a list of cells or instances that you want the Synopsys tool to handle them as dont_touch blocks. June 2000 69 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands When you select Plot in the Top-Level Design Constraints subform, or when you select Plot from the Instance Compile Constraints subform, as described later, the Plot Options subform appears. For information about the fields on this form, refer to the Synopsys Design Compiler Family Reference Manual. Create Schematic OptionsSubform When you select Schematic in the Top-Level Design Constraints subform, or when you select Schematic from the Instance Compile Constraints subform, as described later, the Create Schematic Options subform appears. Options lets you specify additional options for the create_schematic Synopsys command. Sheet lets you select a sheet size for the schematic design that Synopsys generates. If you select a sheet size other than infinite (A, B, C, or D), Synopsys generates a multi-sheet schematic, assuming the size of the synthesized design did not fit in the sheet size you selected. For information about the fields on this form, refer to the Synopsys Design Compiler Family Reference Manual. June 2000 70 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Report Options Subform When you select Report in the Top-Level Design Constraints subform, or when you select Report from the Instance Compile Constraints subform, as described later, the Report Options subform appears. Report lets you specify the information you need from the Design Compiler when it generates the report file (the dci.report). Report File Name is the name of the report file. You can specify any name you want. Other Options lets you specify any additional information you want in the report file. For information about any other options, refer to the Synopsys Design Compiler Family Reference Manual. SPF Options Subform When you select Use SPF File in the Top-Level Design Constraints subform, the SPF Options subform appears. June 2000 71 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands CSI reads the Standard Parasitic Format (SPF) file that contains timing parasitics data, and writes timing parasitics data to the Design Compiler. CSI reads and writes the SPF file by converting the SPF file to a list of Design Complier set_load commands. Generate "set_load" Constraints from SPF File generates the set_load commands from the SPF file. You must select this button. SPF File Name is the name of an existing and valid SPF file. Additional Loading of Primary Outputs is a capacitance value that you want to add to the capacitance value assigned in the SPF file for each of the primary outputs in top-level cell. Capacitance Scale Factor is a scale factor by which you want to multiply each capacitance value specified in the SPF file. CSI applies this scale factor after it adds any additional loading to the primary output. apply to top level nets specifies whether or not CSI must write the set_load commands for the nets in the top-level cell. If you select this field, CSI ignores the nets that are not in the top-level cell in the SPF file. June 2000 72 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Finite State Machine Options Subform When you select Finite State Machine in the Top-Level Design Constraints subform, or when you select Finite State Machine from the Instance Compile Constraints subform, as described later, the Finite State Machine Options subform appears. For information about the fields on this form, refer to the Synopsys Design Compiler Family Reference Manual. Instance Constraints Subform When you select instances on the Constraints form and select an instance from the schematic, the Instance Constraints subform appears. For information about the fields on this form, refer to the Synopsys Design Compiler Family Reference Manual. June 2000 73 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Instance Compile Constraints Subform When you select Compile Separately on the Instance Constraints subform, the Instance Compile Constraints subform appears. If you select Plot, Schematic, Report, and Finite State Machine a subform for that option appears. These subforms are described above with the Top-Level Design Constraint subform. For information about the fields on this form, refer to the Synopsys Design Compiler Family Reference Manual. June 2000 74 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Instance Pin Constraints Subform When you select instance pins on the Constraints form and you select an instance pin from the schematic, the Instance Pin Constraints subform appears. For information about the fields on this form, refer to the Synopsys Design Compiler Family Reference Manual. Input Pin Constraints Subform When you select input pins on the Constraints form and you select an input pin from the schematic, the Input Pin Constraints subform appears. June 2000 75 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands For information about the fields on this form, refer to the Synopsys Design Compiler Family Reference Manual. Output Pin Constraints Subform When you select output pins on the Constraints form and you select an output pin from the schematic, the Output Pin Constraints subform appears. For information about the fields on this form, refer to the Synopsys Design Compiler Family Reference Manual. Net Constraints Subform When you select nets on the Constraints form and you select a net from the schematic, the Net Constraints subform appears. For information about the fields on this form, refer to the Synopsys Design Compiler Family Reference Manual. SKILL Function csiMenuConstr() June 2000 76 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Utilities Menu Design Session Utilities Run Show → Symbol Compilation... Custom Command File... Show lets you display the run directory files, edit the command file, and display the synthesized design. Symbol Compilation lets you run the Design Compiler in batch mode to compile a library into Synopsys format. Custom Command File lets you create a customized command file for input to the Design Compiler. June 2000 77 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Utilities – Show Menu Design Session Utilities Run Show → Symbol Compilation... Custom Command File... Job Monitor... CSI Log File DC Log File Command Fie DC Report Other File... Synthesized Design Job Monitor lets you monitor, stop, or terminate a job running in batch mode. CSI Log File displays the dci.log file in a text viewing window. DC Log File displays the dci.runout file in a text viewing window. Command File displays the all.cmd file in a text viewing window. DC Report displays the dci.report file in a text viewing window. Other File lets you view or edit any of the text files in the run directory. Synthesized Design displays the schematic view of your synthesized design in a schematic window. Show menu commands have two modes, read and edit. Use the Session – Setup – CSI command to set the mode. read mode lets you display the files, and edit mode lets you view and edit the file. For example, you can edit the command file (the all.cmd file) to add more input commands to the Design Compiler for running synthesis. June 2000 78 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Utilities – Show – Job Monitor Utilities ¿ Show ¿ Job Monitor... Lets you check the status of a job running in batch mode, monitor its output, suspend it, change its execution priority, or terminate it. Analysis Job Monitor Form When you select Job Monitor, the Analysis Job Monitor form appears. Show Run Log displays the dci.log file in a text viewing window when you select a job on this form. Set Priority lets you specify a new priority number for the job you select. You can only decrease the priority of a job. For example, to decrease the priority of a job set at 10, change the priority to 12. Kill terminates the batch job and displays a dialog box asking you to confirm that you want to kill the job. Once you kill a job, you cannot continue it with the Continue button. Suspend stops the batch job temporarily until you use the Continue button. Continue starts the job if you have stopped it with Suspend. Continue does not start a job terminated with Kill. Delete removes the jobs you have selected from the Analysis Job Monitor form but does not terminate or suspend them. A dialog box asks you to confirm that you want to delete the job from the form. Once deleted from the form, you cannot change the priority, suspend, or kill the job. All jobs running in batch mode are listed on the form with the following information: Run Directory lists the run directory of the batch job. June 2000 79 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Start Time lists the time when the job was started. Host lists the name of the host machine running the job. Status lists the status of the job. Priority lists the UNIX priority of the job. SKILL Function csiJobMonitor() June 2000 80 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Utilities – Show – CSI Log File Utilities ¿ Show ¿ CSI Log File Displays the dci.log file in a text viewing window. The dci.log file is generated when you initialize the CSI environment. The dci.log file contains information about initialization of the environment and run-time messages from the synthesis run. June 2000 81 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Utilities – Show – DC Log File Utilities ¿ Show ¿ DC Log File Displays the dci.runout file in a text viewing window. The dci.runout file is generated by the Design Compiler during the synthesis run and contains the run-time messages for all running jobs. June 2000 82 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Utilities – Show – Command File Utilities ¿ Show ¿ Command File Displays the all.cmd file in a text viewing window. The all.cmd file is generated when you use the Run – Build Command File command and contains the design constraints information. To modify the command file before running synthesis, set the Show command mode to edit on the CSI Options form. However, any changes you make are overwritten the next time you use the Build Command File command. June 2000 83 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Utilities – Show – DC Report Utilities ¿ Show ¿ DC Report Displays the dci.report file in a text viewing window. The dci.report file is generated by the Design Compiler for the design that you synthesized most recently. The dci.report file contains the circuit characteristics, such as, timing, area, and synthesis constraints. The content of this file is dependent on the latest settings you selected from the Report Options subform of the Session – Edit Constraints command. June 2000 84 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Utilities – Show – Other File Utilities ¿ Show ¿ Other File... Lets you view or edit any of the text files in the run directory. To edit the run directory files you must set the Show command mode to edit on the CSI Options form before using this command. CSI View Run Directory File Form File Name lets you select a run directory file. When you click and hold the left mouse on the cyclic field, a list of all the files in the run directory appears for your selection. The files that start with a dot are not displayed. June 2000 85 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Utilities – Show – Synthesized Design Utilities ¿ Show ¿ Synthesized Design Displays the schematic view of your synthesized design in a schematic window. CSI generates the top-level cell by converting the Design Compiler output into the Cadence format. The top-level cell is schematic view of your synthesized design. June 2000 86 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Utilities – Symbol Compilation Utilities ¿ Symbol Compilation... Lets you run the Design Compiler in batch mode to compile a Cadence library into a Synopsys library. The Symbol Compilation command converts a group of cells in Cadence format or a complete Cadence library to a Synopsys symbol library in text or binary format. The synthesis run uses the Synopsys library as an input. Before Using This Command Before using the Symbol Compilation command you must set the library path for the Cadence source libraries. To do this, select the Open – Library command from the CIW and in the Open Library form specify the library path names in the Library Path field. Symbol Compilation Form Symbol Compilation Source Library lets you select the name of the Cadence source library you want to compile. When you click and hold the cyclic field the list of libraries appears. These are the same libraries you specified when using the Open – Library command from the CIW. The Symbol Compilation command accepts only these source libraries. The default is the first library name in the search path. User-Supplied Cell Names lets you specify a file that contains the names of the cells you want to compile. The cells must be a subset of the source library specified in the Source Library field. The default is off. Cell Names File lets you specify the name of a user file that contains a list of the source library cell names. See the User-Supplied Cell Names field described previously. June 2000 87 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Symbol Library lets you select one of the following options when generating a symbol library in binary format. The default is the last settings you used. create binary creates the symbol library file in text format (.slib) and then creates a symbol library file in binary format (.sdb). If you want to use an existing symbol library in text format to create the binary format, select the use existing text library file option. create text creates the symbol library file in text format (.slib) without compiling it. check only checks the validity of the compilation on the source library to ensure that the library data meets symbol library compilation requirements. The Symbol Compilation command does not generate an output for this check. use existing text library file uses an existing symbol library file in text format (.slib) to create the symbol library file in binary format. SKILL Function csiMenuLibCompile() Required Libraries The libraries required for running Synopsys tools are typically provided by an ASIC vendor or by a library administrator. Two libraries are required, the symbol library and the technology library. The Synopsys symbol library in binary format must be compatible with the corresponding Cadence symbol library. By running the Symbol Compilation command in CSI you can generate the Synopsys symbol library in binary format from the Cadence symbol library. The Cadence default symbol and technology library for CSI (the sample library) is already compiled to the Synopsys symbol and technology libraries in binary format. The Synopsys technology library contains technology-dependent data and is not specific to Cadence. CSI currently does not provide a method for generating the technology library from Cadence formats. Cadence Cells That Cannot be Compiled During library compilation, if your design contains any cells that the Symbol Compilation command can not compile to generate a symbol, CSI issues warning messages but continues with the compilation. We suggest that you manually delete these cells from the list June 2000 88 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands of library cells in the dciLib.list file. For more information about the dciLib.list file, see Files in the Synthesis Run Directory on page 105. Cadence Standard Libraries Cadence provides a standard library, which includes both symbol and technology information, with a compatible Synopsys symbol and technology library. The Cadence standard library (sample) is located in the /samples/cdslib directory. The corresponding Synopsys symbol (sample.sdb) and technology (sample.db) libraries are located in the /etc/dci/synlibs directory. CSI does not require the sample library. The following table shows an example of required libraries for CSI. Library Name Cadence Library basic US_8ths ripper Synopsys Symbol Library basic.sdb US_8ths.sdb ripper.sdb Directory Name /etc/cdslib /etc/cdslib/sheets /etc/dci ASIC Vendors ASIC vendors can use the Symbol Compilation command in CSI to compile a Cadenceformat symbol library into a Synopsys-format symbol library after s Adding custom cells to the Cadence-format library s Creating a custom library from Cadence-format symbols June 2000 89 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Utilities – Custom Command File Menu Design Session Utilities Run Show → Symbol Compilation... Custom Command File → Configuration Management→ Create... Edit... Delete Create lets you create a new custom command file. Utilities – Custom Command File – Create on page 91 Edit lets you modify an existing custom file. Utilities – Custom Command File – Edit on page 92 Delete lets you delete a custom command file. Utilities – Custom Command File – Delete on page 93 June 2000 90 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Utilities – Custom Command File – Create Utilities ¿ Custom Command File ¿ Create... Lets you create a custom command file for a synthesis run in batch mode. You must select the Run – Build Command File command before selecting the Utilities – Custom Command File – Create command. The Run – Build Command File command creates the all.cmd and inc.cmd files. You can use the all.cmd or the inc.cmd file as the template file and create your custom command file when you select the Utilities – Custom Command File – Create command. When editing the command file, make sure that the Design Compiler can read the file by using legal Synopsys commands and the correct syntax. CSI doesn’t check the custom command file for correctness. CSI manages the custom command file on a run directory basis, therefore each run directory has a different set of command files. Create Custom Command File Form Create Custom Command File File Name lets you specify the name of the command file you want to create. Template File Name lets you select the command file you want to use as the template file to create your command file. When you click and hold this cyclic field, the command files that CSI maintains in the current run directory appear. The list of files that appear include the all.cmd file, inc.cmd file, and any custom command files that you have previously created. When you click OK on the form, CSI copies the template file you selected to the file name you specified on the form, and the custom command file is displayed for edit. The value of the EDITOR environment variable in your .cshrc file sets the text editor. June 2000 91 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Utilities – Custom Command File – Edit Utilities ¿ Custom Command File ¿ Edit... Lets you modify an existing command file. When editing the command file, make sure that the Design Compiler can read the file by using legal Synopsys commands and the correct syntax. CSI doesn’t check the custom command file for correctness. Edit Custom Command File Form Edit Custom Command File File Name lets you select the name of the command file that you want to edit. When you click and hold the cyclic field a list of all previously defined custom command files appear.You can select one of the command files to edit. When you click OK on the form, the file you selected for editing displays in a xterm window. June 2000 92 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Utilities – Custom Command File – Delete Utilities ¿ Custom Command File ¿ Delete... Lets you delete an existing custom command file. Delete Custom Command File Form Delete Custom Command File File Name lets you select the name of the command file that you want to delete. When you click and hold the cyclic field a list of all previously defined custom command files appear.You can select one of the command files to delete. When you click OK on the form, CSI removes the file you selected from the list of custom command files maintained for the run directory. Run Menu Design Session Utilities Run Export Design Build Command File Synopsys Import Design Install Synthesized Design... You must select the Run menu commands in the following order: 1. Export Design 2. Build Command File 3. Synopsys June 2000 93 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands 4. Import Design 5. Install Synthesized Design Export Design creates a netlist of the design and transfers the design files from the Cadence Design Framework II environment to the Design Compiler. Build Command File creates the input command file to the Design Compiler. Synopsys runs the Design Compiler or Design Analyzer. Import Design transfers the design output from the Design Compiler in EDIF format to the Cadence Design Framework II environment in a netlist format. Install Synthesized Design copies and saves the synthesized design from the Cadence temporary library in the run directory (DESIGNS) to the Cadence-format library that you specify. You can use this command to replace the source design with the synthesized design. June 2000 94 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Run – Export Design Run ¿ Export Design Creates a netlist of the design and transfers the design files from the Cadence Design Framework II environment to the Design Compiler. For VHDL designs, use the VHDL Tool Box to netlist your design before starting CSI. CSI reads the netlist files before creating the command file. Select the Export Design command if you s Change the value of the csiVerilogViewList or csiVerilogStopList variables (for Verilog format only) s Update the design s Create new cellviews Before Using This Command Before using the Run – Export Design command, do the following: 1. Select the Session – Setup – CSI command. The CSI Options form appears. 2. Select a netlist format from the Netlist Format field. SKILL Function csiExportDesign() June 2000 95 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Run – Build Command File Run ¿ Build Command File Creates the command files called all.cmd and inc.cmd. Use the Build Command File command before using the Run – Synopsys command or if you change either the CSI Options form or the Synopsys Options form. The all.cmd file contains five command file sections. These file sections are used as include files in the inc.cmd file. The inc.cmd file only contains Synopsys include commands that correspond to the all.cmd file sections. The all.cmd file is the default file when CSI invokes the Synopsys tool. You can use a custom command file instead of all.cmd. To create a custom command file you can use the all.cmd file sections or the inc.cmd file. If you are an advanced Synopsys tool user, you can also use the all.cmd file sections and the inc.cmd file in the minimum interactive mode as command sequences. The inc.cmd file contains the Synopsys include commands of any of the section files of the all.cmd file that you want to use for the synthesis run. The following is a sample of the inc.cmd file The inc.cmd file sample include include include include include setup.inc netlist.inc constr.inc compile.inc write.inc Before Using This Command Before using the Build Command File command, do the following: 1. Select Session – Edit Constraints to apply the design constraints. 2. Select Utilities – Setup – CSI to change or check the default environment and run options for CSI. June 2000 96 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands 3. Select Utilities – Setup – Synopsys to change or check the default run options for the Synopsys tools. 4. Select Run – Export Design. SKILL Function csiBuildCmdFile() June 2000 97 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Run – Synopsys Run ¿ Synopsys Runs the Design Compiler or the Design Analyzer. Depending on the options you set in the CSI options form when using the Session – Setup – CSI command the s Design Compiler runs in batch, interactive, or minimum interactive mode on a local or a remote server s Design Analyzer runs in interactive or minimum interactive mode Before Using This Command Before using the Run – Synopsys command, do the following: 1. Select Session – Setup – CSI, and on the CSI Options form, specify the Synopsys installation path. 2. Run the Run – Export Design command at least once for the current CSI run directory. 3. Run the Run – Build Command File command at least once for the current CSI run directory, or specify the use of a custom command file either from the CSI Options form or SKILL commands. SKILL Function csiRunSynopsys() June 2000 98 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Run – Import Design Run ¿ Import Design Transfers the design output from the Design Compiler in EDIF format to the Cadence Design Framework II environment in a netlist format. The Import Design creates the .optToCds file and runs the Cadence edifin program on the EDIF netlist from Synopsys to create the Cadence cellview in a temporary library called DESIGNS. The edifin program creates the DESIGNS library in the directory running icds. There must be no other library named DESIGNS in the library search path. When the DESIGNS library is created in the top-level directory, you can copy and save all or part of the synthesized design back in to the your design library using the Session – Install Synthesized Design command. Before Using This Command Before using the Import Design command, do the following: 1. Select the Session – Setup – CSI command, and on the CSI Options form, be sure the Import Design After Batch Run field is not selected. 2. Select the Run – Build Command File command at least once for the current run directory for the design. 3. Run the Run – Synopsys command at least once with a successful result, to create an EDIF file in the current run directory. Import Design Formats CSI can import two types of data from Synopsys: s EDIF netlist with schematic data s EDIF netlist without schematic data (connectivity-only) When you run the Design Compiler in batch mode, the Design Import command selects the type of format. If you run synthesis in interactive mode, you can choose the format by using the cadence_schematic_out alias or the cadence_netlist_out alias while in the Design Compiler or the Design Analyzer. See Building the Command File on page 41 for more information on these aliases. June 2000 99 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands SKILL Function csiImportDesign() June 2000 100 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands Run – Install Synthesized Design Run ¿ Install Synthesized Design... Copies and saves the synthesized design from the Cadence temporary library in the run directory to the Cadence symbol library. This command copies and saves the synthesized design in the Cadence symbol library as a schematic view plus a cellview version number. Using this command, you can save multiple versions of the synthesized design. Before Using This Command Before using Install Synthesized Design, you must do the following: 1. Synthesize the source schematic by using the Run – Synopsys command. 2. Import the synthesized design by using the Run – Import Design command. 3. If you want to look at the synthesized design, use the 4. Utilities – Show – Synthesized Design command. June 2000 101 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands CSI Install Design Form When you select Install Synthesized Design, the DFII Library Manager Copy form appears. Simple lets you copy whole libraries or selected cells or views in a library. Hierarchical lets you copy all the cells in a hierarchical design. By View lets you copy only the views you specify. By Configuration lets you copy a configuration of cells that you have previously specified. A configuration is a set of cells that belong together. Destination Library is the library to which the files are copied. The following descriptions are for the Simple Copy Option form. For more information, click Help on the Copy form. Select All lets you install all of the cellviews from the synthesized design into the installation design. Deselect All clears any selections. You can individually select the ones you want to install by clicking on the box at the far left. A green dot indicates your selection. June 2000 102 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Session, Utilities, and Run Menu Commands OK installs the synthesized cells into the installation library according to your selections. SKILL Function csiInstallOptDesign() June 2000 103 Product Version 4.4.0 Cadence to Synopsys Interface User Guide A Run Directory Files Synthesis Run Directory For each Synopsys Design Compiler run, CSI uses a run directory. A run directory can contain some or all of the following files: control-command, input, output, and log. The Tools – Design Synthesis – CSI command creates, initializes, and reinitializes the run directory. Before synthesizing a design or compiling a library, you must either create and initialize a new run directory or reinitialize an existing run directory. A new run directory contains input files and templates. After a design synthesis run or library compilation, the run directory contains intermediate and output files. Some output files can contain data from multiple runs; data from each new run is appended to the file. Before using an existing run directory, you must use the Tools – Design Synthesis – CSI command to reinitialize it. You can use an existing run directory for multiple CSI selections. You can edit some of the run directory files as an input for subsequent CSI selection. To examine a run result, you must reinitialize the existing run directory. Note: Unless you are an advanced Synopsys Design Compiler user, do not edit run directory files or work directly in the run directory to perform design syntheses or library compilations. Work only through CSI. June 2000 104 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Run Directory Files Files in the Synthesis Run Directory The following table lists all the synthesis run directory files in alphabetical order. File Name all.cmd compile.inc Contains Created by Synthesis Run – Build command file Command File that CSI created command for running Design Compiler Used by Run – Synopsys command Commands that Run – Build Custom compile the Command File command file design command utility Comments You can automatically add control commands to this file by using the Constraint – Edit command to enter synthesis constraints. Optional use constr.inc dci.edif dci.edifin dci.env dci.log Commands that Run – Build extract synthesis Command File constraint command values from CSI Custom command file utility Optional use Optimized schematic in Synopsys EDIF format Run – Synopsys Run – Import command Design command Optimized Run – Import schematic in Design EDIF format and command modified by CSI Run – Import Design command Global environment variables Tools – Design All commands Synthesis – CSI command Do not edit this file. Run-time Tools – Design All commands messages from Synthesis – CSI CSI command June 2000 105 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Run Directory Files File Name dci.plot dci.report dci.runout dciLib.cmd dciLib.dc dciLib.list dciLib.nlist dciLib.warn Contains Created by Used by Optimized schematic for plotting in EDIF format Run – Synopsys command Area, timing, create text constraints, and option of the other reports in Utilities – a text format Symbol Compilation command and the Run – Synopsys command Run-time Run – messages from Synopsys Design Compiler command Script to run the Utilities – Library Compiler Symbol Compilation command Utilities – Symbol Compilation command Run-time messages from the Design Compiler run Utilities – Symbol Compilation command Cell names in the source library create text option of the Utilities – Symbol Compilation command Utilities – Symbol Compilation command Cell names not translated Utilities – Symbol Compilation command Utilities – Symbol Compilation command Run-time messages from the CSI run Utilities – Symbol Compilation command Comments Output log file from batch runs Do not edit this file. June 2000 106 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Run Directory Files File Name inc.cmd Contains Created by Include files that Run – Build correspond to Command File the sections of command the all.cmd file Used by Custom command file utility netlist.inc The commands that read the exported netlist file Run – Build Command File command Custom command file utility setup.inc The commands that define the setup variables, set the search path, and read the symbol libraries Run – Build Command File command write.inc The commands that create the schematic and write the EDIF file Run – Build Command File command .sd b Symbol library in Utilities – binary format Symbol Compilation command Custom command file utility Custom command file utility Utilities – Symbol Compilation and Run – Synopsys commands Comments Optional use Optional use for batch or interactive runs Optional use Optional use for batch runs only June 2000 107 Product Version 4.4.0 Cadence to Synopsys Interface User Guide Run Directory Files File Name Contains Created by .slib Symbol library in Utilities – text format Symbol Compilation command or external programs Used by Utilities – Symbol Compilation command .rundc .synopsys_ dc.setup .optToCds Shell script to start batch or interactive synthesis Run – Synopsys Run – command Synopsys command Design Compiler Tools – Design Run – functions that Synthesis – CSI Synopsys make CSI work command command and it includes definitions of several aliases. You can use some of these aliases when running synthesis in interactive mode. Some of the other aliases are referenced in the all.cmd file. Shell script for importing the design Run – Import Design command Run – Import Design command Comments You can edit the file – After using the create text option – Before using the create binary option with the use existing text library file option Located in the /etc/dci directory, CSI copies this file into each run directory that it creates. June 2000 108 Product Version 4.4.0 Cadence to Synopsys Interface User Guide B SKILL Cross-Reference Tables Mapping SKILL Functions to Menu Commands The following table lists the SKILL functions associated with the Session, Utilities, and Run menu commands. SKILL Function csichangeRunDir csiDeleteRemoteRunDir csiSetupCSI csiSetupSynopsys csiSetupVlgNetlister csiMenuConstr csiJobMonitor csiMenuLibCompile csiExportDesign csiBuildCmdFile csiRunSynopsys csiImportDesign csiInstalloptDesign Menu Command Session – Run Directory – Change Run Directory Session – Run Directory – Delete Remote Run Directory Session – Setup – CSI Session – Setup – Synopsys Session – Setup – Verilog Netlist Session – Edit Constraints Utilities – Show – Job Monitor Utilities – Symbol Compilation Run – Export Design Run – Build Command File Run – Build Command File Run – Import Design Run – Install Synthesized Design June 2000 109 Product Version 4.4.0 Cadence to Synopsys Interface User Guide SKILL Cross-Reference Tables Mapping SKILL Variables to Field Names The following table lists the SKILL variables associated with the field names on the CSI forms from the Session, Utilities, and Run menu commands. SKILL Variable Field Name on the Form csiSynopsysExec Executable Name csiAutoGenDesignSymbols Generate Design Symbols csiCustomCmdFiles Command File Names csiUseCustomCmdFile Use Custom Command File csiShowWorksLikeEdit Show File Command Mode csiRemoteMounting Use NFS for Remote Synthesis csiRemoteHostName Hostname csiSynopsysRoot Synopsys Installation Path csiSynopsysLibPath Synopsys Search Path csiSynSymbolLibs Symbol Libraries csiSynTargetLibs Target Libraries csiSynLinkFiles Link File Menu Command Session – Setup – CSI Session – Setup – CSI Session – Setup – CSI Session – Setup – CSI Session – Setup – CSI Session – Setup – CSI Session – Setup – Synopsys Session – Setup – Synopsys Session – Setup – Synopsys Session – Setup – Synopsys Session – Setup – Synopsys Session – Setup – Synopsys June 2000 110 Product Version 4.4.0

    Top_arrow
    回到顶部
    EEWORLD下载中心所有资源均来自网友分享,如有侵权,请发送举报邮件到客服邮箱bbs_service@eeworld.com.cn 或通过站内短信息或QQ:273568022联系管理员 高进,我们会尽快处理。