All technical data contained in this publication is subject to the export control laws of the United States of America. Disclosure to nationals of other countries contrary to United States law is prohibited. It is the reader's responsibility to determine the applicable regulations and to comply with them.
Disclaimer SYNOPSYS, INC., AND ITS LICENSORS MAKE NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Trademarks Synopsys and certain Synopsys product names are trademarks of Synopsys, as set forth at http://www.synopsys.com/Company/Pages/Trademarks.aspx. All other product or company names may be trademarks of their respective owners.
Third-Party Links Any links to third-party websites included in this document are for your convenience only. Synopsys does not endorse and is not responsible for such websites and their practices, including privacy practices, availability, and content.
Synopsys, Inc. 690 E. Middlefield Road Mountain View, CA 94043 www.synopsys.com Synopsys Statement on Inclusivity and Diversity Synopsys is committed to creating an inclusive environment where every employee, customer, and partner feels welcomed. We are reviewing and removing exclusionary language from our products and supporting customer facing collateral. Our effort also includes internal initiatives to remove biased language from our engineering and working environment, including terms that are embedded in our software and IPs. At the same time, we are working to ensure that our web content and software applications are usable to people of varying abilities. You may still find examples of non- inclusive language in our software or documentation as our IPs implement industry- standard specifications that are currently under review to remove exclusionary language. Contents
Getting Started ............................................................................5
Prerequisites .......................................................................................... 6 Setting up Your Environment ................................................................. 7
Using TCL for Debug Queries ........................................................9
3 Feedback Synopsys, Inc. 4 Synopsys, Inc. Feedback Getting Started
This quick start guide enables SpyGlass CDC users to migrate designs from SpyGlass CDC to VC SpyGlass CDC. You can reuse your existing SpyGlass setup up files, project (.prj) files, constraints, waivers and command line to run VC SpyGlass CDC and perform CDC analysis.
5 Feedback Synopsys, Inc. Getting Started
Prerequisites
Prerequisites Before you migrate a design from SpyGlass CDC to VC SpyGlass CDC, consider the following: A design to be considered for migration to VC SpyGlass CDC 2018.09 release, should have run successfully with SpyGlass version 2018.09. If your design uses DW components, refer Handling DW Components section. If your current SpyGlass setup reads in .lib cells, provide the equivalent .db cells for design read. To provide .db cells for VC SpyGlass CDC, specify the .db file in the .synopsys_vcst.setup file in the design directory ($DESIGN_DIR) by using the following commands: set search_path <Path to db directory> set link_library <db file list> For example, consider the following commands in a sample .synopsys_vcst.setup file: set search_path "/remote/group/project/design_cdc/ LIBRARIES_db/" set link_library "TOP_2M3PIX.db FU_SAFMEMHV_LSOD25.db ISC_19_CLK_LVT.db SC_19_CLK_SVT.db " NOTE: If you do not specify the .db file corresponding to the .lib files specified in the SpyGlass setup, VC SpyGlass CDC will consider the lib cells as a black box.
6 Synopsys, Inc. Feedback Getting Started
Setting up Your Environment
Setting up Your Environment
To run VC SpyGlass CDC in SpyGlass Use Model (SGUM), set the following environment variables: $VC_STATIC_HOME environment variable: Set the VC_STATIC_HOME environment variable to the path where VC SpyGlass CDC is installed as shown below: % setenv VC_STATIC_HOME <installation_path > $PATH environment variable: Set your UNIX PATH variable to $VC_STATIC_HOME/bin as shown below: % set path = ($VC_STATIC_HOME/bin $path) Or % setenv PATH $VC_STATIC_HOME/bin:$PATH LM_LICENSE_FILE or SNPSLMD_LICENSE_FILE environment variable: Set the LM_LICENSE_FILE or the SNPSLMD_LICENSE_FILE license variable to your license file as shown below: % setenv LM_LICENSE_FILE <Location_to_the_license_file> OR % setenv SNPSLMD_LICENSE_FILE /u/edatools/vcsgcdc/ license.dat Note the following: You can use the SNPSLMD_LICENSE_FILE environment variable to set licenses explicitly for Synopsys tools. If you set the SNPSLMD_LICENSE_FILE environment variable, VC SpyGlass CDC ignores the LM_LICENSE_FILE environment variable. If you are in the Synopsys network, use % module load vcstatic
7 Feedback Synopsys, Inc. Getting Started
Setting up Your Environment
8 Synopsys, Inc. Feedback Using TCL for Debug Queries
VC SpyGlass CDC has very strong TCL interface debug with query and collections. The salient features are: All the design objects have attributes Attributes can be used for filtering collections and object query Attributes on cell, port, pin, net, design, lib_cell, lib_pin base_name, full_name, is_sequential, is_clock_pin, direction Design query commands get_cells, get_pins, get_nets, get_ports Design tracing using all_fanin, all_fanout, all_connected commands Most of the commands return collections Regexp and filter options, commands to manipulate collections Query_objects and support for wild cards to access collections
9 Feedback Synopsys, Inc. Using TCL for Debug Queries
10 Synopsys, Inc. Feedback Debugging Violations in GUI
When you run in GUI mode, the Verdi GUI displays the results of cdc_verify_struct goal loaded for the design after the run. Figures 1 shows the Verdi GUI. Note that the Activity View has SpyGlass style
11 Feedback Synopsys, Inc. Debugging Violations in GUI
naming of violations
FIGURE 1. Verdi GUI showing the results of cdc_verify_struct goal
To debug the errors, select an error in the Activity View and review the setup error. Select a violation and then click the Toggle Information View to review the violation details. Figures 2 shows the Toggle Information View
12 Synopsys, Inc. Feedback Debugging Violations in GUI
icon.
FIGURE 2. Toggle Information View
13 Feedback Synopsys, Inc. Debugging Violations in GUI
14 Synopsys, Inc. Feedback Appendix
Appendix This section covers the following: Handling DW Components
15 Feedback Synopsys, Inc. Appendix
Handling DW Components
Handling DW Components DesignWare components are handled differently in VC SpyGlass CDC as compared to SpyGlass CDC. If the SpyGlass project file has the set_option DW command set to yes, DW components need to be precompiled and then provided to VC setup. To provide the DW components to VC setup, perform the following steps: 1. Precompile the DW component by using the following command: % module load syn 2. Create a Tcl file, such as precompile_dwlib.tcl, by using the following command: % dw_analyze -dwroot $env(SYNOPSYS) -log precomp_dwlib.log ./DW_WORK 3. Add the following application variable to the precompile_dwlib.tcl file: set_app_var vsi_dwroot ./DW_WORK 4. Provide the updated precompile_dwlib.tcl file to the VC setup by using the following command: % ${VC_STATIC_HOME}/auxx/monet/scripts/spyglass_vc_1.8 - project <spyglass project file> -goal cdc/ cdc_verify_struct -app cdc run -batch -pre_tcl <precompile_dwlib.tcl> NOTE: If your project uses DW components and you do not provide the precompiled DW components, VC SpyGlass CDC reports them as black box. Refer the Prerequisites section for other factors to consider before you migrate a design from SpyGlass CDC to VC SpyGlass CDC.
Instant download Microsoft Azure Architect Technologies Study Companion: Hands-on Preparation and Practice for Exam AZ-300 and AZ-303 Rahul Sahay pdf all chapter
Instant download Microsoft Azure Architect Technologies Study Companion: Hands-on Preparation and Practice for Exam AZ-300 and AZ-303 Rahul Sahay pdf all chapter
