Home > Community > Blogs > Functional Verification > tech tip waving specman objects in simvision
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more conveniennt.

Register | Membership benefits
Get email delivery of the Functional Verification blog (individual posts).


* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

Tech Tip: Waving Specman Objects in SimVision

Comments(2)Filed under: Functional Verification, e, Specman, IES-XL, debug, SimVision

Did you know that you can wave Specman objects in IES-XL *and* also save the wave setup for automatically restarting the simulation? If not, this tech tip is for you! Here is the process:

Step 0 – Once you are happy with your waveform setup, don’t forget the basic step of saving your mix of RTL signals and Specman fields/events using the [File] → [Save] command script menu item in SimVision.

Step 1 - After adding all the desired fields, signals, and events to the waveform, use the “write wave to” Specman command to create an ecom file named <filename>.ecom with all the wave commands Specman needs to recreate your trace setup:

      > write wave to <filename>

Step 2 - When you “source” this ecom file in a new simulation, either using “sn @<filename>” in IES-XL or “@<filename>” in stand-alone Specman, the fields and events will be added to a new waveform window.

Important: the environment must be generated (by running the test command) before the trace ecom can be applied. In other words, in the new simulation load the ecom file before sourcing the saved command script

Step 3 - To automate this for follow-on simulations (where “sn_wave” is the <filename> you specified in step 1 above):

       % irun -input nc_in.tcl

Where inside the file “nc_in.tcl” you have:

   sn test
   sn @sn_wave
   simvision input simvision.svcf

Happy debugging!

Nils Luetke-Steinhorst
Sales Technical Leader
Cadence Germany


By Ensoul Chi on January 22, 2010
I am using IES 9.2 and try to add event and uint variable into waveform. But it only work fine for the first time. If I want to reload the e code and rerun the simulation. The waveform become very ugly. All the event and uint variables display far behind the real time it should be trigged.
Such the simulation finished at 1000ns, the first event may only changed on the waveform at 500ns.

By teamspecman on January 25, 2010
Hi Ensoul,
This is actually a known bug (see CCMPR00739590), which has been fixed and merged into the latest branch.
It should be available on the upcoming 8.2 S8 and 9.2 S6.
Please let us know if you have additional questions.
Team Specman

Leave a Comment

E-mail (will not be published)
 I have read and agree to the Terms of use and Community Guidelines.
Community Guidelines
The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.