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.
I would strongly advise against using 1 - it is likely to change. There really is no public API to create an ADE state outside of ADE - whilst in theory it might be possible using the asiSaveState() API, that requires a "sev" (simulation environment, i.e. ADE window) around to about to save the state. That's because mostly the save state functionality is really part of the ADE interface.
In reply to Andrew Beckett:
Thanks for the reply.
I tried the below two methods to save state and my inferences are as below:
Schematic and ADE are open. Both were opened manually.
sevS = hiGetCurrentWindow()->sevSession
// Obtain ADE's o_session
sevSo1 = sevEnvironment(sevS)
//Add a new DesignVariable
asiAddDesignVarList(sevSo1, list('("x" "1"))
This opens a FORM to save the state. Human interface needs to be avoided !
so2 = asiGetCurrentSession()
// Save ASI State
WARNING (ADE-1071): Cellview nil of type nil already exists.
Above warning appears. However, so2->cellName has the correct value and is not 'nil'. But so2->name is nil.
Any clues on which approach is right and if Method(2) is correct, what is wrong in ASI state not getting saved.
In reply to GaneshShamnur:
Run out of time to check now, but my first guess is that in method 2 you need to provide some of the keyword arguments to asiSaveState (such as ?name, ?cell, ?lib etc) - see the documentation. Note that it's the lib/cell/view of the state that matters here, not the design.
Your guess was partly correct. The API needed 'name' parameter.
After passing a name for the state to save, i.e asiSaveState(so2 ?name "spectre_custom_state"), a proper ADE session state could be saved.
However, the interesting question is why does it seek 'name' as argument while the session-object already has a value for 'name'.
In API description, 'name' is an optional argument.Moreover the warning message didn't mean that either !.
But the API does work. Thank You.
How would the session object have a name for the state? I agree the error messages are not that great though - this API doesn't have as much checking as it should...
I meant about the default 'name' a session picks.
I expect it to save with the same name when no 'name' parameter is passed.
se4 = asiGetCurrentSession()
So, 'spectre6' is the expected state to be saved.
I have no idea why you think that name would have anything to do with the state name. It's a unique name given to the session (used to generate unique identifiers for certain objects), and is unrelated to the name of the state that you are saving.
It doesn't (as far as I know) say anywhere in the documentation that this is the state name.
Note that in general you should not be querying attributes on asi objects - these are not a public interface and may change without warning. Instead you should use the public API to isolate you from any necessary implementation that we might have to make to improve the tools in the future.
Thanks for the explanation.