5.3 Batch Files for Command Line Simulators

Whenever you do a build or a run from the BugHunter GUI, it also creates batch files with all the commands needed to build, elaborate, and run the current simulator from the command line. These files can be used to create regression test suites that run on different computers.

Build, Elaborate, and Run batch files

The names of the created files are based on the simulator name and type of command to run. The table below shows the UNIX batch files. Windows batch files have a bat file extension instead of an sh extension.

SynaptiCAD Simulators

build_simx.sh run_simx.sh

build_vlogcmd.sh

Cadence Verilog

Cadence VHDL

build_ncvlog.sh elab_ncvlog.sh run_ncvlog.sh

build_ncvhdl.sh elab_ncvhdl.sh run_ncvhdl.sh

Mentor ModelSim Verilog

Mentor ModelSim VHDL

build_vlog.sh run_vlog.sh

build_vcom.sh run_vcom.sh

Synopsys

build_vcs.sh run_vcs.sh

Library mapping files for Cadence NCsim simulator

When compiling using Cadence Incisive (i.e. ncsim), BugHunter automatically creates a file called cds.lib in the project directory that tells Incisive how to map symbolic library names to physical directories on disk. This file also includes a link to a file called cds_project.lib (also in the project directory) where a user can add additional symbolic to physical mappings if needed.

•Open the cds_project.lib file located in the project directory and add the logical-library-to-physical-directory mapping.

DEFINE lib1 ./lib1_ncsim

•For example, the above would map a logical library named lib1 to a directory called lib1_ncsim. Note: If a directory called lib1_ncsim doesn't already exist, you will also need to create this directory from the shell.