Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
Under the old 3-step process (ncvlog+ncelab+ncsim), I could compile the testbench once. Then call ncsim multiple times to run the sim again(without recompiling.)
How do I do that with irun? What are the proper command-line switches?
In reply to Stewart:
I'll also add that, if you haven't updated the source code, using the exact same irun command line as used to compile the first time will behave the way you've described. irun will compare the timestamps of the source code files and if they are earlier than the snapshot, they won't be recompiled. If nothing is recompiled, the elaborator won't be run again either.
However, iIf you change the compiler's command-line options, then irun will recognize that and recompile when necessary.
The -r and -R options that Stewart mentioned are especially useful if you have changed a source file, but want to hold off recompiling 'til later.
I also in need of the same, compiling once and simulating that snapshot(INCA_libs) many times. If you have a solution, please share.
In reply to sivauvm:
On the first invocation of irun, add -elaborate to the command line. This will cause irun to perform compile and elaborate, creating a snapshot but not simulating.
The snapshot can then be simulated by using the irun -R option (or -r <snapshot>) that I described previously.
More detailed descrptions are availabe in the irun help: irun -helpall | grep "\-R"
Hope that helps,
In reply to tpylant:
Now I am able to do "compile once and simulate the snapshot many times" with irun.
One change in your command is it should be -nclibdirpath instead of -nclibdirname.
I am also thinking about this one-step/multi-step irun flow.
With one-step irun -nclibdirname $SNAPSHOT_DIR ... , my simulation works well and can be run anywhere. But later when I migrate this command into EManager, looks some of my cases terminated without running at all.
I think it is probably related to this one-step command may not work well in EManager with parallel simulation at the same time.
If I divide the irun by irun -c & irun -r , some questions below:
1. first invocation of irun with "-c" option, do I need to supply case name "+UVM_TESTNAME=$testname" ?
2, the second time when I want to sim only, what option is needed? Is it irun -R or irun -r ?
3. how to merge ifv commands into irun ?
I am now trying . if you can give some help meanwhile, very appreciated.