|> We have recently upgraded our verilog to the turbo version. With that, we
|> got cwaves which we find very useful in being able to graphically put
|> together the list of signals that we want to look at. Our approach, with
|> multiple designers, is to run verilog and then look at the results with
|> cwaves. Another simulation can be running while you are staring at the
|> waveforms. With multiple users, we would like to have one copy of
|> verilog and multiple copies of cwaves which I assume would be cheaper
|> than one copy of verilog for each user. My Cadence salesman tells me that
|> Cadence does not sell cwaves separately. They have had requests to do that
|> and his claim is that it will take them a year to do that. Does anyone know
|> why? maybe there's someone from cadence out there that can explain it. I
|> need a solution now. I might as well go to signalscan and buy their
|> software. It requires use dump files that occupy more disk space than using
|> cwaves but at least I can use it now. I feel that Cadence is encouraging me
|> to go to the competition. Am I the only one that gets that feeling?
You can bring up cwaves standalone and by itself, by just typing cwave. It
invokes a special cwaves only opus when you do this. I believe it is because
of this opus framework dependency that the problem you are discribing exists
and is taking so long to remedy. In the mean time I would buy a venders
debug environment. They are really cheap and really trick. At ovi last week
alot of companies where demoing new verilog UI's that were cool. Here are
the list in order of which I like (based on slick demo's only, not on
actual evaluation as of yet). I was looking for good source level debugging
and good waveform display
Simulation Technologies - Virsim 612 631 1858
Veritools - Undertow 415 941 5050
System Science INc - Magellan 415 812 1800
Maybe I'll write up a little report for the net when I am done evaluating
each. My guess is that any of these would more than please most verilog
users debug needs.