( ESNUG 355 Item 4 ) --------------------------------------------- [7/26/00]
Subject: ( ESNUG 344 #9 345 #11 ) Issues Running TCL In Design Analyzer
> Oh Great! We get our entire synthesis environment setup for TCL-based
> scripting (DC, PT, etc) and find out that Design Analyzer doesn't support
> TCL. This really blows chunks, considering there is no elegant way to
> automagically determine if you would like TCL or DC-flavored usage in your
> ~/.synopsys_dc.setup file. Hence any DA usage must now have a separate
> kludge to get the library paths, environment setups, etc to work! Yuck!
>
> Rumours say that Synposys is re-writing the GUI interface of Design
> Analyzer to be TCL-friendly, but that isn't available now when I need it.
> Now why can't Synopsys release tools (DA & DC) that at least work together
> in a nice fashion?
>
> - Gregg Lahti
> Intel Corp Chandler, AZ
From: [ A Synopsys CAE ]
Hi John,
I would like to respond to Gregg Lahti's post ( ESNUG 344 #9 ), concerning
the how to use Design Analyzer in a Tcl based synthesis environment.
DC has a special group of commands called the TCL subset which can be used
in the .synopsys_dc.setup files and will work for both DCSH and DCTCL. To
tell DC that the .synopsys_dc.setup contains TCL subset commands the first
character in the first column must contain a '#' character. An example:
# TCL / DCSH compatible ~/.synopsys_dc.setup file
set target_library {lsi_10k.db};
set link_library {* lsi_10k.db};
set symbol_library {lsi_10k.sdb};
This script will work for Design Analyzer in a DC-Tcl environment.
The following table summarizes the possible combinations of
.synopsys_dc.setup files in the various directories for the two dc_shell
modes (for DC-Tcl environment + DA use the last configuration):
Current Working
dc_shell Mode Synopsys Root Home Directory Directory
------------- ------------- -------------- -----------
dcsh mode Tcl-subset dcsh dcsh
dcsh mode Tcl-subset Tcl-subset dcsh
dctcl mode Tcl-subset Tcl Tcl
dcsh/dctcl mode Tcl-subset Tcl-subset Tcl-subset
More details of the TCL subset can be found in the "Design Compiler
Command-Line Interface Guide".
A New GUI for synthesis will be available later this year.
- [ A Synopsys CAE ]
---- ---- ---- ---- ---- ---- ----
From: Gregg Lahti <gregg.d.lahti@intel.com>
I jogged my memory this morning and realized my post caused me to remember
the workaround that fixes my gripe. A big, hearty, thank-you to Synposys AE
Chris Papademetrious [chrispy@synopsys.com] for recommending this fix!
I paired down his example to something that I use when going between the two
synthesis enviroments:
# Tcl-s
#
# Sample .synopsys_dc.setup file.
echo {Sourcing home .synopsys_dc.setup file}
echo {}
set company {Intel Corporation}
set designer [getenv USER]
# Also note that the source command is sensitive to the setting of
# the sh_source_uses_search_path variable.
set sh_source_uses_search_path {true}
if { [getenv {PROJ_SYN_SETUP}] != {} } {
set proj_startup_file [getenv {PROJ_SYN_SETUP}]
echo {Including project startup file } $proj_startup_file
source $proj_startup_file; ## -echo -verbose
echo {Done including} $proj_startup_file
redirect /dev/null { unset proj_startup_file }
} else {
echo {No project startup file included}
echo {Set environment variable "PROJ_SYN_SETUP" for project-wide setup}
}
# this is for personal aliases
source ~/.synopsys_aliases.tcl
Good Luck.
- Gregg Lahti
Intel Corp Chandler, AZ
|
|
