
- •Contents
- •Introducing Comparescan
- •Features
- •Applications
- •Organization of this Guide
- •Getting Started
- •Starting Comparescan
- •Specifying Input Files
- •Specifying Simulation Results Databases for Comparison
- •Specifying a Comparescan Rules File
- •Specifying a Comparescan Error Database for Viewing
- •Using Automatically Generated Files
- •Using the State File
- •Using the Preferences File
- •Using X Resources
- •Understanding Comparescan Exit Status Codes
- •Comparescan Tutorial
- •Accessing the Tutorial Source Files
- •Simulation Results Databases
- •Comparescan Rules Files
- •Generating a Comparescan Error Database
- •Viewing a Comparescan Error Database
- •Viewing Errors in Hierarchical Order
- •Viewing Errors in Signalscan Waves
- •Viewing Multiple Objects in Signalscan Waves
- •Viewing Errors in Time Order
- •Exiting Comparescan
- •Giving More Information in the Rules File
- •Reviewing the demo.rules Rules File
- •Using the demo.rules Rules File
- •Viewing Clocked Miscompares in Signalscan Waves
- •Comparescan Graphical User Interface
- •Comparescan Window
- •Menu Bar
- •File Menu
- •Tools Menu
- •View Menu
- •Window Menu
- •Button Bar
- •Application Examples
- •Making Absolute Comparisons
- •Specifying the Filename of an Object
- •Comparing Two Objects from the Same File
- •Comparing Two Objects on a Condition
- •Making Clocked Comparisons
- •Using One Clock and Two Simulation Files
- •Using One Clock and One Simulation File
- •Using Two Clocks and Two Simulation Files
- •Using Two Clocks and One Simulation File
- •Performing a Clock Compare with Timing Checks
- •Checking Stability
- •Specifying Objects in the Design Hierarchy
- •Command Option Examples
- •Specifying Start and End Times for Golden and Test Files
- •Specifying Start and End Times for Comparison
- •Specifying a Time Shift
- •Specifying compare Command Tolerance Windows
- •Special Syntax Examples
- •Commenting
- •Continuing Long Lines
- •Specifying Both a Golden and a Test File
- •Specifying Filenames Using UNIX Filename Syntax
- •Writing Comparescan Rules
- •Default Comparison Rules
- •Absolute and Clocked Comparisons
- •Rules File Parsing and Execution
- •Command Syntax and Options
- •General Command Syntax
- •Command Summary
- •General Command Options
- •datafile1
- •datafile2
- •compare
- •clkdef
- •clkcompare
- •stability
- •sequencetime
- •nosequencetime
- •statemapping
- •threshold
- •report
- •savedata
- •loaddata
- •translate
- •Frequently Asked Questions
- •Comparescan Input
- •Comparescan Output
- •How do I view a comparison report that I have generated?
- •Can I print a report of my errors?
- •Can I run the tool in batch mode?
- •Graphical User Interface (GUI)
- •How do I run the program without the user interface?
- •Why can’t Comparescan allocate colors?
- •How do I change the colors in the GUI?
- •Why can’t I read the text in the GUI?
- •Comparescan Features
- •How can I compare a digital simulation with an analog simulation?
- •How do I match an X value?
- •How do I compare only the top-level signals in my design?
- •How do I compare modules at different levels in the hierarchy?
- •What if I want a different tolerance window for every signal?
- •Comparescan Error Messages
- •What does “Out of Memory” mean?
- •What does “fork failed” mean?
- •Index

Comparescan User Guide
Getting Started
Using the State File
Comparescan saves data about its configuration into a state file. By default, this file is named
~/.comparescan.state; you can change this name and location by using the -state command-line option.
The state file contains the set of options that you used the last time you ran Comparescan.
This file also stores the warning messages that have previously been displayed, so that they are not repeatedly displayed.
Comparescan automatically updates the state file when you specify different options on the command line or change the options in the Compare Options form. (Click the Options button or select Tools—Compare Options to display the Compare Options form.) The state file does not store any of the comparison results information.
Using the Preferences File
Comparescan saves your Comparescan GUI preferences in a preferences file. By default, this file is named ~/.comparescan.pref; you can change this name and location by using the -pref command-line option.
Comparescan automatically updates the preferences file when you use the Preferences form. (Select File—Preferences to display this form.)
Using X Resources
Comparescan utilizes the resource settings that you set using xrdb or .Xdefaults. Comparescan can also utilize resource settings in an Appdefaults file, but it does not require that you install an Appdefaults file.
Note: If you change a setting in your .Xdefaults file, you must use xrdb to apply the changes to the running X server.
Comparescan uses the following resources and the following default values:
Comparescan*foregroundcolor: #ffff00
Comparescan*backgroundcolor: #6e6e6e
Comparescan*selectcolor: #ff8080
Comparescan*foregroundinactivecolor: #b0b000
Comparescan*dialogmessagefont: -*-helvetica-bold-r-*--14-*
Comparescan*menufont: -*-helvetica-bold-r-*--12-*
Comparescan*buttonfont: -*-helvetica-bold-r-*--14-*
December 2000 |
15 |
Product Version 1.9 |
|
Comparescan User Guide |
|
Getting Started |
|
|
Comparescan*titlefont: |
-*-helvetica-bold-r-*--14-* |
Comparescan*userfont: |
-*-helvetica-medium-r-*--12- |
Comparescan*infofont: |
-*-helvetica-medium-r-*--11-* |
Comparescan*labelfont: |
-*-helvetica-medium-r-*--12- |
Comparescan*fixedfont: |
-*-fixed-medium-*-semicondensed-*-13-* |
Understanding Comparescan Exit Status Codes
Comparescan exits with either a 0 or a 1 exit status code after performing a comparison. An exit status code of 0 means that no mismatches were found. An exit status code of 1 means that some mismatches were found, some signals were missing, or some other error was detected.
December 2000 |
16 |
Product Version 1.9 |