Read the common verilog pitfalls and suggestions web page.
If you experience problems starting the tools in our environment, email the course TA or me (Bevan Baas) and not ece support since the installations are on my group's server.
Source verilog file(s)
$recordfile("DumpFileName"); $recordvars(TopLevelModuleName);Your simulation signal traces will be stored in DumpFileName.dsn and DumpFileName.trn
Running the simulator
make runYou can add more source files into the *.vf file.
Starting the waveform viewer
make viewerthen select "File" -> "Open Database" and choose your *.trn file. Your design should now show up in the "Scope Tree" section of the window. Select signals you would like to view by left clicking and then right click and select "Send to waveform viewer" to view signals in a new Waveform window.
64-bit systems: acroread /net/pizza/tools/cadence/IUS81/doc/ncvlog/ncvlog.pdf & 32-bit systems: acroread /net/pizza/tools/cadence/IUS62/doc/ncvlog/ncvlog.pdf &A shorter description of various ncverilog command line options can be found by typing
ncverilog -h | less -Mq
2017/01/24, 16:00 Updates to page intro 2007/01/31, 23:45 Updated paths from /net/pizza/3/... to /net/pizza/8/... 2005/01/25, 12:45 Added "ssh" login info 2005/01/24, 15:45 Added "setenv CDS_*" to environment additions list 2005/01/21, 11:10 Filled out list of linux ECE machines 2005/01/20, 20:30 A number of updates including abc.v and tbench.sv 2005/01/20, 14:00 First pass
2005/02/03 First pass
Installing Icarus Verilog and GTKWave for MacOS X
1. Apple's XCode: This can be found on the OS X install CD/DVD or downloaded through the Apple Developer Connection (http://developer.apple.com/). This will provide you with the gcc 3.3 compiler needed to compile the applications from the source code. The X11 SDK must also be installed which is an optional component during install.
2. Apple's X11: This provides an X11 interface for the GTKWave application which can be found on the install CD/DVD or downloaded (http://www.apple.com/macosx/features/x11/).
3. Fink: This provides a bridge between the Unix world and OS X and can be downloaded at http://fink.sourceforge.net/ (10.3 required). Look at the documentation on the website for installing FinkCommander and switching to the unstable tree. In the unstable tree you will find the "iverilog" and "gtkwave" packages. Due to dependencies it might take several hours to build all the required packages.
4. Download the Makefile.icarus from the website, name it "Makefile" and place it in a directory with the sample test bench code. With luck "make compile", "make run", and "make viewer" will work. Remeber to start X11 before running make viewer.
1. Cygwin: An enviornment, complete with the "make" utility, is required to use and build GTKWave. To do this obtain setup.exe from http://www.cygwin.com/. In addition to the default packages install: Devel => gcc, gtk+-devel, libxml2-devel ; X11 -> xorg-x11-base, xwinwm.
2. Go to the Icarus Verilog website and download the Windows setup package from the FTP. Install the program into C:\IVerilog or some other path without spaces. Add this location to your system PATH variable using the Windows "System" control panel applet.
3. Download the GTKWave source code from the GTKWave website and move the file into C:\cygwin\home\(USERNAME) and extract the archive.
4. Start a cygwin shell instance which should put you in your home directory. Build the application with "./configure --enable-builtin-readers="vcd"", then make, then make install. If you wish to use LXT files or other input formats you might need to apply the patch below using "patch -p1 < (PATCH_FILE)" in the extracted directory.
5. Download the Makefile.icarus from the website, name it "Makefile" and place it in a directory within your home folder with the sample test bench code. With luck "make compile", "make run", and "make viewer" will work. Before using make viewer, you must first run "/usr/X11R6/bin/startxwin.sh" to start and X11 session.
Here is a patch gtkwave.patch written by Eric to correct compile errors in cygwin.
2005/02/11 Installation process added (from Eric Work) 2005/02/02 First pass
synopsys2002 #synopsys VCS_7 #VCSAfter adding the lines, you must log out and log back in for the changes to take effect.
Source verilog file(s)
$vcdplusfile("prob1.vpd"); // .vpd extension is nice reminder $vcdpluson;Running the simulator
vcs -Mdir=/tmp/MyInitialsverilog -Mupdate -PP -R file1.v file2.v or simply make runWhere file1.v and file2.v are source verilog files. Of course, you can add more source files and even include all source files in a separate file and include them with the -f command line option.
The -Mdir=/tmp/MyInitialsverilog option directs vcs to use your workstation's local /tmp disk for temporary compile files (can speed up your simulation significantly). Choose a unique name for your /tmp directory so there aren't conflicts with other students' directories.
The -PP option enables vcs to work with vcd+ files.
The -R option tells vcs to run the simulation after compilation.
Starting the waveform viewer
vcs -RPP &then select File -> Open in the "VirSim - Hierarchy" window and choose your .vpd file. If you had previously saved a configuration file, open it from the File menu. If not, select Window -> Waveform and select signals from the "VirSim - Hierarchy" window and drag and drop them using your center mouse button into the "VirSim - Waveform" window.
The -RPP option puts vcs into post-processing mode so that vcs starts virsim for looking at a vcd+ file.
Re-running a simulation
cd $VCS_HOME/examples/XVCSDEMO acroread tutorial.pdf & cd $VCS_HOME/doc/UserGuide/ acroread vcs.pdf & acroread vsim.pdf &A shorter description of various vcs command line options can be found by typing
vcs -help | less -Mq
make run_interactiveThe -RI option starts-up Virsim immediately after vcs compiles the source files.
Once the simulator is invoked, open up the hierarchy window by selecting Window->Hierarchy in the Interactive window
The waveform view can be changed by selecting Zoom in the waveform window.
Because of the delays specified in the initial block of TB.v, this simulation will need to be run to 675ns to complete. Do this by choosing "Go To Time" and entering 67500. Hit "OK" and adjust the zoom and the entire test simulation can be seen. Note: The simulator can be stopped using the red "Stop Simulation" button in the Interactive window
To re-run a simulation after making a change to a verilog source file, select Sim -> Rebuild and Re-exec and then follow the "Simulator Control" procedure above. Note that the -Mupdate option must be given for this to work.