0% found this document useful (0 votes)
868 views

DC v2016.12-SP3 Lab Setup Checks: 1. UNIX% CP - R Lab5 Test - Lab5 CD Test - Lab5 DC - Shell - Topo

This document provides steps to test Design Compiler, Library Compiler, DC-Ultra, DesignWare, DFT Compiler, DC-Graphical, Design Vision, Formality, and dcprocheck licenses and functionality. It also includes steps to check Solvnet access and man pages. Resolving a Library Compiler error requires creating a symbolic link. Finally, it notes to delete the test directory upon completion.

Uploaded by

manojkumar
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
868 views

DC v2016.12-SP3 Lab Setup Checks: 1. UNIX% CP - R Lab5 Test - Lab5 CD Test - Lab5 DC - Shell - Topo

This document provides steps to test Design Compiler, Library Compiler, DC-Ultra, DesignWare, DFT Compiler, DC-Graphical, Design Vision, Formality, and dcprocheck licenses and functionality. It also includes steps to check Solvnet access and man pages. Resolving a Library Compiler error requires creating a symbolic link. Finally, it notes to delete the test directory upon completion.

Uploaded by

manojkumar
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

DC v2016.

12-SP3 Lab Setup checks


(updated August 25, 2017)

Please follow the steps below to test the various tools, licenses and features which are needed for a
successful lab. Please report ANY issues with any of these steps to the instructor assigned to teach
this workshop.

dc_shell, Library Compiler, DC-Ultra, DesignWare and DFT Compiler:

1. UNIX% cp -r lab5 test_lab5


2. UNIX% cd test_lab5
3. UNIX% dc_shell -topo
Design Compiler should start without any error messages. Verify from the log message on the
screen (near the top) that the software version is version 2016.12-SP3.
4. At the tool prompt “dc_shell-topo>” enter (copy-paste) the following commands:
read_verilog STOTO.v
current_design STOTO
link
check_library

If the check_library command issues an error message similar to the following, do not
panic; continue with the remaining steps (#5 onwards), and at the end of this document, you will
find the needed instructions to resolve the error.
Error: The check_library command failed to run. Check the
installation of Library Compiler. (LCSH-3)

5. At the tool prompt “dc_shell-topo>” continue entering the following commands (you can
copy the entire set of commands from this file and paste them all simultaneously in the DC-shell,
however, make sure that no compile_ultra command option “dashes” ( - ) are left off when
copied) :
source STOTO.con
source STOTO.pcon
set_host_options -max_cores 16
compile_ultra -scan -spg -retime
list_licenses

The compile_ultra command above should invoke synthesis optimization. If optimization is


successful, this confirms that you have the needed Ultra, DesignWare and DFT compiler
licenses. When synthesis is done you will see the message “Optimization Complete” .
You should also expect to see no more than (2) licenses are in use for each license feature listed.

If you see the following error message, “Error: extra positional option …”, a “dash” (- )
character was likely left off of one or more command options when the last command was
copied. Use the up-arrow key to trace back to the command and enter the missing dash(es).
DC-Graphical (DC-Extension):
1. Remain in the test_lab5 directory.
2. dc_shell-topo> start_gui
3. Design Vision GUI: Window  New Layout Window
4. A separate LayoutWindow should open, displaying a rectangular box, with small light-blue input
(I) and output (O) “pins” along its edges.
5. From either GUI window enter: File  Exit  OK
6. dc_shell> exit

Design Vision:

1. Remain in the test_lab5 directory.


2. UNIX% design_vision -topo
3. The Design Vision GUI should come up after a few seconds.
Look at the top of the log to verify that it is version 2016.12-SP3.
4. Exit the GUI: File  Exit  OK

fm_shell

1. Remain in the test_lab5 directory.


2. UNIX% fm_shell
The formality prompt should appear. Verify from the log message on the screen (near the top)
that the Formality software version is 2016.12-SP3.
3. fm_shell (setup)> exit

dcprocheck

1. Remain in the test_lab5 directory.


2. UNIX% dcprocheck ../lab5/.solutions /dc.tcl
This should invoke the “Synopsys Tcl Syntax Checker”. You should get your UNIX
prompt back when it completes the check. You can ignore the syntax errors that are reported:
“undefined procedure: all_output”.
“undefined procedure: rc”

man pages

1. UNIX% alias dcman ‘/usr/bin/man –M $SYNOPSYS/doc/syn/man’


UNIX% dcman compile_ultra
The “man page” for this command should open up.
2. Quit “dcman” by typing the lower-case [Q] key.
Web browser and Solvnet access

1. Ensure that all class attendees have their own Solvnet userid and password. They can register for
a free userid at www.solvnet.synopsys.com  “SIGN UP FOR AN ACCOUNT”. They will
need your company’s “Synopsys Site ID Number”, which can be found in the Synopsys license
key file.
2. Open a web browser, for example: UNIX% firefox &
3. Enter the following URL: solvnet.synopsys.com
4. Enter a Solvnet User Name and Password.
5. Select the “Documentation” from the top banner area of the page.
6. Select “Design Vision”
7. Open “Design Vision User Guide, version M-2016.12” [or a later version is acceptable]
8. If able to view the document, close the browser.

Resolving Library Compiler installation error (if encountered in Step #4 earlier):

A symbolic link to Library Compiler is required to be created under Design Compiler’s installation
path: ${DC}_INSTALL_DIR/$platform/syn/bin/lc_shell_exec
This is done by running the script install_lc provided with Library Compiler installation.
For details, refer to page 84 (reproduced below) of the following application note:
https://solvnet.synopsys.com/retrieve/customer/application_notes/attached_files/2226768/Design_Comp
iler_K-2015.06_TrainingUpdate.pdf

Upon creating the symbolic link to Library Compiler, you should be able to successfully repeat the steps
(#1-4) that were at the beginning of this document.

Cleanup

Delete the following directory: test_lab5.

You might also like