EDAboard.com | EDAboard.de | EDAboard.co.uk | WTWH Media

cadence simulation dumps

Ask a question - edaboard.com

elektroda.net NewsGroups Forum Index - Verilog Language - cadence simulation dumps

Goto page 1, 2  Next

Jason Zheng
Guest

Tue Feb 01, 2005 2:29 am   



Does anyone know if any 3rd-party waveform viewer can view the
simulation dumps generated by cadence ncverilog (via $shm_open, not
$dumpfile)? What's the standard or format used by shm_open?

thanks

Ajeetha
Guest

Tue Feb 01, 2005 5:44 am   



Hi,
I don't think you'll find one - all these compiled waveform formats
are kept proprietary by individual vendors (CDN - SHM, SNPS - VPD, MTI
-WLF etc.). However one option can be to open their SHM file in
simvision and convert to VCD. But - why do you want to do that? I
thought Simvision is a nice viewer Smile
Regards,
Ajeetha
http://www.noveldv.com

Jason Zheng
Guest

Tue Feb 01, 2005 7:11 pm   



Ajeetha wrote:
Quote:
Hi,
I don't think you'll find one - all these compiled waveform formats
are kept proprietary by individual vendors (CDN - SHM, SNPS - VPD, MTI
-WLF etc.). However one option can be to open their SHM file in
simvision and convert to VCD. But - why do you want to do that? I
thought Simvision is a nice viewer Smile
Regards,
Ajeetha
http://www.noveldv.com

Thanks for the suggestion. You actually don't have to convert it to VCD,

though. All the simulators can take the standard $dumpfile and $dumpvars
tasks to generate VCD directly.

The problem I am facing right now, is that we don't have enough
ncverilog license for everyone in my team to use Simvision at the same
time, and cadence does not offer seperate licensing for simvision along.
Hence if we need more simvision, we'd have to pay for the entire
ncverilog license (for each additional simvision). That is the
movitation behind my pursuit for some 3rd-party waveform viewer.

Our design simulations are relatively large, so VCD dumps can be
multiple hundred megabytes. The free waveform viewer gtkwave, which I
tried, cannot handle huge VCD dumps very well. In fact, it crashes
everytime I tried to add any trace to it.

-jz

Stephen Williams
Guest

Tue Feb 01, 2005 7:23 pm   



Jason Zheng wrote:

Quote:
Our design simulations are relatively large, so VCD dumps can be
multiple hundred megabytes. The free waveform viewer gtkwave, which I
tried, cannot handle huge VCD dumps very well. In fact, it crashes
everytime I tried to add any trace to it.

Try converting the VCD dump to lxt using tools that come with gtkwave,
and then use gtkwave to display the lxt file instead.

--
Steve Williams "The woods are lovely, dark and deep.
steve at icarus.com But I have promises to keep,
http://www.icarus.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."

Jason Zheng
Guest

Tue Feb 01, 2005 9:39 pm   



Stephen Williams wrote:
Quote:
Jason Zheng wrote:

Our design simulations are relatively large, so VCD dumps can be
multiple hundred megabytes. The free waveform viewer gtkwave, which I
tried, cannot handle huge VCD dumps very well. In fact, it crashes
everytime I tried to add any trace to it.


Try converting the VCD dump to lxt using tools that come with gtkwave,
and then use gtkwave to display the lxt file instead.

Thanks for that suggestion. I gave it a try and found out either vcd2lxt

or gtkwave is buggy, apparently most of my signals got changed to X's.
It does have a great compression ratio, though. Hopefully this will be
fixed in the future.

-jz

Stephen Williams
Guest

Tue Feb 01, 2005 11:03 pm   



Jason Zheng wrote:
Quote:
Stephen Williams wrote:

Jason Zheng wrote:

Our design simulations are relatively large, so VCD dumps can be
multiple hundred megabytes. The free waveform viewer gtkwave, which I
tried, cannot handle huge VCD dumps very well. In fact, it crashes
everytime I tried to add any trace to it.



Try converting the VCD dump to lxt using tools that come with gtkwave,
and then use gtkwave to display the lxt file instead.

Thanks for that suggestion. I gave it a try and found out either vcd2lxt
or gtkwave is buggy, apparently most of my signals got changed to X's.
It does have a great compression ratio, though. Hopefully this will be
fixed in the future.

Safe bet that Tony would like to hear about that. What version of
gtkwave are you using?

--
Steve Williams "The woods are lovely, dark and deep.
steve at icarus.com But I have promises to keep,
http://www.icarus.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."


Guest

Tue Feb 01, 2005 11:51 pm   



I seem to recall hearing something about a Post-Processing Environment
mode in Simvision, which would allow looking at waveforms without using
up a simulation license. It might have required some other kind of
license,
but that might be no worse than getting a third-party tool.


Guest

Wed Feb 02, 2005 12:38 am   



Stephen Williams wrote:
Quote:
Jason Zheng wrote:

Thanks for that suggestion. I gave it a try and found out either
vcd2lxt
or gtkwave is buggy, apparently most of my signals got changed to
X's.
It does have a great compression ratio, though. Hopefully this will
be
fixed in the future.

Safe bet that Tony would like to hear about that. What version of
gtkwave are you using?

Yeah, I'm curious as I've never seen X corruption like that. Anyway,
considering the number of people I've seen have problems with enormous
VCD files, I'm half-tempted to have the viewer prompt the user if it's
OK to convert the file over to a database format instead like
signalscan does.

Note that if you're using gtkwave-2.x I have no idea if lxt works for
it as there were problems with lxt in that branch when the internal
value change representation was restructured by APT--don't know if the
lxt bugs there still exist as I only maintain/bugfix the 1.3 series.

wget ftp://metalab.unc.edu/pub/linux/apps/circuits/gtkwave-1.3.53.tgz

I regularly generate lxt traces with about 300k signals so if you have
a real problem Jason, I'm curious.

-Tony

Jason Zheng
Guest

Wed Feb 02, 2005 2:14 am   



sharp_at_cadence.com wrote:
Quote:
I seem to recall hearing something about a Post-Processing Environment
mode in Simvision, which would allow looking at waveforms without using
up a simulation license. It might have required some other kind of
license,
but that might be no worse than getting a third-party tool.

Sharp,


Would you share more information on the post-processing environment? I
have never heard of that sort of license from cadence.

thanks,

jz

Jason Zheng
Guest

Wed Feb 02, 2005 2:43 am   



bybell_at_rocketmail.com wrote:
Quote:
Stephen Williams wrote:


Safe bet that Tony would like to hear about that. What version of
gtkwave are you using?


Yeah, I'm curious as I've never seen X corruption like that. Anyway,
considering the number of people I've seen have problems with enormous
VCD files, I'm half-tempted to have the viewer prompt the user if it's
OK to convert the file over to a database format instead like
signalscan does.

Note that if you're using gtkwave-2.x I have no idea if lxt works for
it as there were problems with lxt in that branch when the internal
value change representation was restructured by APT--don't know if the
lxt bugs there still exist as I only maintain/bugfix the 1.3 series.

wget ftp://metalab.unc.edu/pub/linux/apps/circuits/gtkwave-1.3.53.tgz

I regularly generate lxt traces with about 300k signals so if you have
a real problem Jason, I'm curious.

-Tony


Yes, I'm running gtkwave 2.0.0pre3-20030319. I noticed the warning about
lxt format on APT's website. However, their warning came after pre4
release, didn't it?
I'll give the version 1.3 a try as suggested by Tony.

Thanks to both of you.

-jz

Jason Zheng
Guest

Wed Feb 02, 2005 3:12 am   



Jason Zheng wrote:
Quote:
bybell_at_rocketmail.com wrote:

Yeah, I'm curious as I've never seen X corruption like that. Anyway,
considering the number of people I've seen have problems with enormous
VCD files, I'm half-tempted to have the viewer prompt the user if it's
OK to convert the file over to a database format instead like
signalscan does.

Note that if you're using gtkwave-2.x I have no idea if lxt works for
it as there were problems with lxt in that branch when the internal
value change representation was restructured by APT--don't know if the
lxt bugs there still exist as I only maintain/bugfix the 1.3 series.

wget ftp://metalab.unc.edu/pub/linux/apps/circuits/gtkwave-1.3.53.tgz

I regularly generate lxt traces with about 300k signals so if you have
a real problem Jason, I'm curious.

-Tony


Yes, I'm running gtkwave 2.0.0pre3-20030319. I noticed the warning about
lxt format on APT's website. However, their warning came after pre4
release, didn't it?
I'll give the version 1.3 a try as suggested by Tony.

Thanks to both of you.

-jz
I just tried version 1.3.53, and it works like a charm with all the lxt

conversion and large vcd dumps. Thanks for all the help!

-jz

p.s. Does gtkwave have rising/falling edge finders like
signalscan/simvision? I looked and couldn't find any.


Guest

Wed Feb 02, 2005 5:18 am   



Jason Zheng wrote:

Quote:
I just tried version 1.3.53, and it works like a charm with all the
lxt
conversion and large vcd dumps. Thanks for all the help!

No problem. Glad to be of help.


Quote:
-jz

p.s. Does gtkwave have rising/falling edge finders like
signalscan/simvision? I looked and couldn't find any.

Yes. Highlight the signal in question then click on Search->Pattern
Search in the menu.

Then a popup will appear. Click the button on the left to, say,
"rising edge" then press "Mark" to lay down alternate gridlines or
"Fwd" or "Bkwd" to move the marker to the next edge/string/whatever.

Note that you can do this with multiple signals at once like an address
bus equals a value and valid is high on a rising clock edge, etc. Also
note that for strings you will have to press enter on the value. The
finder also works with timeshifted signals which is how you can do
searches that don't happen in zero time. (e.g., if you're watching
something move through pipe stages)

If you haven't already, copy .gtkwaverc to your home directory and the
viewer will look nicer than the black and white screens I've seen on
some people's screen grabs.

BTW, something not really documented that works nicely is to zoom full
then click the RMB, drag it left or right, and release. The area
between the two cursors defines the new left and right margins. A
couple of iterations of this is a quick way to zero in to a specific
part of a trace.

Regards,
-Tony

Ajeetha
Guest

Wed Feb 02, 2005 6:28 am   



But isn't it true that generating VCD takes much longer than say SHM,
as it is a binary format and file size being small, file-IO is expected
to be faster? That's the reason why I recommended using SHM2VCD
conversion.

Anyway I learnt quite some useful stuff via this thread on this
LXT/GTKWave features - thanks!

Ajeetha

Ajeetha
Guest

Wed Feb 02, 2005 6:29 am   



Hi,
Perhaps Steve is referring to ncsim -ppe option. I thought that holds
up a license too - not sure which one though.

Ajeetha

Chris Briggs
Guest

Wed Feb 02, 2005 3:41 pm   



Jason Zheng wrote:
Quote:
The problem I am facing right now, is that we don't have enough
ncverilog license for everyone in my team to use Simvision at the
same
time, and cadence does not offer seperate licensing for simvision
along.
Hence if we need more simvision, we'd have to pay for the entire
ncverilog license (for each additional simvision). That is the
movitation behind my pursuit for some 3rd-party waveform viewer.

I'm surprised. A little less than 2 years ago we asked Cadence about
additional Simvision licenses and they gave us a price. We didn't end
up getting them though. But our rep has always been good about letting
us buy extra short-term licenses for whatever.

-cb

Goto page 1, 2  Next

elektroda.net NewsGroups Forum Index - Verilog Language - cadence simulation dumps

Ask a question - edaboard.com

Arabic version Bulgarian version Catalan version Czech version Danish version German version Greek version English version Spanish version Finnish version French version Hindi version Croatian version Indonesian version Italian version Hebrew version Japanese version Korean version Lithuanian version Latvian version Dutch version Norwegian version Polish version Portuguese version Romanian version Russian version Slovak version Slovenian version Serbian version Swedish version Tagalog version Ukrainian version Vietnamese version Chinese version Turkish version
EDAboard.com map