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 am trying to use the soft_bin option.
1) I created a stimulus file containing the line: soft_bin=allmodels
2) I included the file using the stimulusFile command in Ocean
However, I received the following runtime error:
soft_bin: Too few terminals given (0 < 2)
What are "terminals" that this message refers to?
I couldn't find much information regarding this simulation option so I would appreciate any guidance.
In reply to Andrew Beckett:
Thanks for the help.
I am getting a different kind of error now:
The instance `myOpts' does not have a valid master.
In reply to Eshar:
Add this in your stimulus file:
instanceInfo info what=inst where=logfile
and it will output information on each instance, including the name of the model (including the bin number) that was used, into the log file (spectre.out if run from OCEAN). You can use where=file if you want it to go to an ASCII file.
It's also stored in the binary results database (from selectData('instance), but currently requires a private SKILL function to access it - there's a CCR to make a public function available - if you want that, please log a service request with customer support to add yourself to the customers requesting this.
In a related matter, is it possible to use a stimulus file in ocean?
When I include a stimulus file using stimulusFile, I get error that I must use the command design("lib" "cell" "view") instead of design("netlistfile"). However, once I run the script with the command design("lib" "cell" "view") I receive an error stating that ocean cannot be run using this format of the design command. Ocean can only be run using a specified netlist file.
Is there a workaround to this which will allow me to include a stimulus file and run the script in cadence?
I am using IC 184.108.40.2060.6.151
This is because stimulus files can use "schematic names" (with a special syntax) and these are then mapped into the netlist names. To do that, it needs to know the design hierarchy.
If you don't need that capability, you can use:
stimulusFile("myfile.scs" ?xlate nil)
and this is supported even when the design is specified as a netlist. Note that design(lib cell view) can be used, but you'd have to run it from icfb (in IC615 it also is supported in the "ocean" executable). This is because in IC5141 the "ocean" executable doesn't support netlisting.