Home > Community > Blogs > Functional Verification > specman simvision interaction tips amp tricks
 
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).
 

Email

* 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: *

Specman – SimVision Interaction Tips and Tricks

Comments(5)Filed under: Functional Verification, Specman, SimVision

[Team Specman welcomes guest blogger Alex Chudnovsky of Specman R&D]


As we are all creatures of habit, sometimes it's hard to adapt to new work flows no matter how beneficial the change may be. Clearly this is the case in the transition of the Specman GUI from Specview to SimVision; so allow me to share with you some quick tips to ease the transition process and/or make you more productive with SimVision.

Opening SimVision as a Console rather as a Design Browser
Invoking SimVision with a “-input ” parameter will by default open the SimVision Console window and not open the Design Browser window. may be any file, including an empty one or even /dev/null.

Uncluttering your desktop and allowing for better performance
If you run a lot of simulations at the same time and need a GUI for all of them, your desktop becomes cluttered with SimVision windows easily. The farm gets overloaded at ease as well. Just run the simulations in batch mode and use the attach / detach feature of SimVision (“File – Open Simulation”). SimVision can connect to IES, stand-alone Specman, and even Specman running with a 3rd party simulator.

 

Show Simulations


Method and struct / unit extensions now accessible under “Files:” drop down pick list

When a Specman entity is shown in the SimVision Source Browser, its extensions are accessible under “Files:” dropdown.

 

source browser


Forcing SimVision to open Source Browser window upon hitting a breakpoint

Specview users are accustomed to Debug window opening automagically upon hitting a breakpoint. However, SimVision doesn’t open a Source Browser window by default. This is ease to remedy: as shown below, use the “Preferences” dialog to configure the desired behavior.

 

Picture1


Happy debugging!

Alex Chudnovsky
Specman R&D

Comments(5)

By Cedric Fau on December 7, 2009
Hello,
I'm interested by this point "Method and struct / unit extensions now accessible under “Files:” drop down pick list" but I don't know how to "index" the e files with SimVision.
I have the sys tree in the SimVision window but when i send a unit to Source Browser, it is the old fashion Specman which opens.
Thank you

By Alex Chudnovsky on December 7, 2009
Hi Cedric,
Are you using IES 9.2 / Specman 9.2? This feature is not available in earlier versions.

By Jason on December 7, 2009
Thanks for the tip on how to open the srcbrowser when a breakpoint is hit, ISX users have been asking about this since the arrival of 9.2.

By patrick on December 8, 2009
It s short, clear and usefull.
If you have any more tips like that they are more than welcome.
Thanks Alex.
Patrick.

By Cedric Fau on December 8, 2009
oups I'm on 8.2. I'm looking forward the 9.2 now ;o)

Leave a Comment


Name
E-mail (will not be published)
Comment
 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.