 |
|
The VCD file does not contain module port information, so any comparison with a -boundary switch will fail since it will not find any module ports.
You can also save the error database using the -save filename on the command line.
To print a short summary of the errors, use -r 1 on the command line.
To print the entire error report, use -r 2 on the command line.
All reports are printed on the standard output.
Use the -batch command line option. When running in batch mode, you should normally specify a rules file to process on the command line.
The "cannot allocate colormap" warning is printed when DAI Comparescan cannot allocate all the colors it needs. This is usually caused by some other application using all the colors from the X server. Possible culprits are Netscape, FrameMaker, or some other color intensive application.
Warning: Cannot allocate colormap entry for "Blue"
Warning: Cannot allocate colormap entry for "gray"
Warning: Cannot allocate colormap entry for \
"#b0b000"
You can force DAI Comparescan to operate in a Black and White mode, by adding the following lines to your ~/.Xdefaults file:
DAI Comparescan*foregroundcolor : black
DAI Comparescan*backgroundcolor : white
If you don't want to use black and white mode, you'll need make the other graphics programs use less of the colormap.
Netscape has a resource named 'maxImageColors' which controls how many color cells it allocates from the default colormap at startup. The default value for this resource is 256 on an 8-bit system and this means that Netscape will hog all of the available color cells, leaving none for your application.
The solution is simple: supply a lower value for this resource, eg in your .Xdefaults file:
Netscape*maxImageColors: 100
A similar affect can be acheived by starting Netscape with the "-ncols" command line option:
netscape -ncols 100
Type netscape -h to see all the command line options for Netscape.
xrdb ~/.Xdefaults
compare test -depth 1 -internalJust specify the two module names or signal names to be compared.
compare test.cpu.adder3 test.cpu.module2.module87.adder4
compare test.cpu.clk test.memory.refresh.clock
compare -tol 45ns top.clk
compare -tol 30ns top.sum
compare -tol 15ns top.data
eg. If the golden SST file has a timescale of 1ns and the test SST file has a timescale of 100ns, the timescale would be 1ns in DAI Comparescan.
You can always avoid timescale problems by specifying your time with the units:
compare top.module1 -tol 100ps
compare top.module2 -tol 150ps
compare top.module3 -pos 75ps -neg 40ps
"Out of Memory" cannot be fixed by deleting files from your disk.
"Out of Memory" can be fixed by adding more swap space. Ask your system administrator to add more swap space by using the "swapon" command.
A Fork is how a process starts another process. Comparescan starts Signalscan by "forking" a new process, and then executing Signalscan in that new process. If a fork fails it is usually because some sytem resources are unavailable - like no more processes allowed, no more virtual memory, etc.
See you System Administrator for more details.
On SunOs use "ps -clax":
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
277/1017 files
222/554 inodes
85/266 processes
36280/258044 swap
| |
|