- •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
Frequently Asked Questions
I specified times in the rules file. What are the default units?
The default unit for all of the times that you specify, either in the rules file or in the Command
Options form, is the lowest time unit in the simulation results databases that you are comparing.
For example, if the golden file has a timescale of 1ns and the test file has a timescale of
100ns, the default timescale is 1ns in Comparescan.
You can always avoid timescale problems by specifying your times with units, as follows:
compare top.module1 -tol 100ps
compare top.module3 -pos 75ps -neg 40ps
Comparescan Error Messages
What does “Out of Memory” mean?
The Out of Memory error message indicates that you have run out of virtual memory. On some machines, virtual memory is the amount of swap space that you have. On other machines, virtual memory is the amount of physical RAM that you have plus the amount of swap space that you have.
To fix Out of Memory errors, add more swap space. Ask your system administrator to add more swap space for you by using the swapon command.
Note: You cannot fix Out of Memory errors by deleting files from your disk.
What does “fork failed” mean?
Sometimes, when you try to start Signalscan Waves from the Comparescan GUI, you get the message fork failed. A fork is the mechanism by which a process starts another process. Comparescan starts Signalscan Waves by forking a new process, and then executing Signalscan Waves in that new process. If a fork fails, it is usually because some system resources are unavailable. For example, there may be no more processes allowed, or there may be no more virtual memory.
See your system administrator for more details about fork-related problems.
December 2000 |
102 |
Product Version 1.9 |
Comparescan User Guide
Frequently Asked Questions
How do I find out how big my processes are?
You can use the ps command from most UNIX prompts to check a process that is alive. On the SunOs platform, for example, use ps -clax to get output similar to the following:
F |
UID |
PID |
PPID |
CP |
PRI |
NI |
SZ |
RSS |
WCHAN |
STAT TT |
TIME COMMAND |
20008021 272 |
5239 |
1209 |
0 |
1 |
01520 |
720 |
select |
S |
p5 |
0:01 comparescan |
How do I find out how much memory my machine has?
You can use the pstat command from most UNIX prompts to check your machine memory.
On the SunOs platform, for example, use pstat -T, which produces output similar to the following:
277/1017 files
222/554 inodes
85/266 processes
36280/258044 swap
December 2000 |
103 |
Product Version 1.9 |