如何有效使用EDA工具 How To Start Using Tools Efficiently-v2.pdf

Background In VLSI design, electronic design automation (EDA) tools are used for different design stages, including logic synthesis, placement, routing, extraction and timing verification. Some of these stages can potentially take several days depending on design complexity. These tools support interactive commands with/without graphic user interface (GUI). Interactive commands along with GUI environment are easier to navigate through and allow intuitive understanding of the design and impact of each design decision on potential outcomes. However, usually design choices and flow details are already decided, and only need to be executed in a sequential manner. Hence, using GUI mode is inefficient and is prone to errors since it requires human interaction. Well-designed command scripts relieve such efforts and prevent human errors, by automating the set of all tasks through a command script. The purpose of this document is to show some of the practical exercises to make well-designed command scripts. Tip1: Prior to running a tool To run a tool, the location of binary and license files must be set by shell commands. Location of binary file must be stored in the shell variable “path”. set path=(Full_path_that_contains_the_binary_file $path) and the location of license file must be specified as follows. setenv LM_LICENSE_FILE port1@address1:port2@address2:... The following is an example of setting up the basic environment variables for Cadence SOCEncounter within ieng6 machines. set path=(/software/nonrdist/cadence-soc71/bin $path) setenv LM_LICENSE_FILE 1704@ieng9.ucsd.edu Unless path and license file are correctly set, you cannot run the tools. Therefore, make sure your shell command script points to correct environments. Tip2: Command line helps to find valid options Most tools support both command line and GUI modes. You can select one of them by setting command options. To find appropriate options, you can run the binary wit