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 have a problem executing envlp analysis through OCEAN scripts. If I try to execute the simulation with the graphic interface, all is ok, but saving the script and executing it, an error stops the envlp simulation. The error is:
ERROR (SPCRTRF-15099): The clock name is not specified for the envelope
following analysis.To fix the problem, use the 'clockname' parameter to
specify a clock name. "
But there is not this error when I execute it from icfb.
My script is something like that:
analysis('envlp ?harms "1" ?stop "200u" ?clockname "fc"
?errpreset "conservative" ?readic "enc.fc" ?writefinal "env.fc" ?method "gear2only"
?relref "alllocal" ?lteratio "10" )
analysis('pss ?fund "915M" ?harms "1" ?errpreset "conservative"
?readic "env.fc" ?tstabmethod "gear2only" ?relref "alllocal" ?lteratio "10" )
desVar( "W2" 15 )
desVar( "W1" 10 )
desVar( "Vrf" 185m )
option( 'temp "27.0"
temp( 27.0 )
paramAnalysis("W1" ?values '(0.3 3 )
paramAnalysis("W2" ?values '(0.3 3 )
Thanks a lot.
What version of the IC tools are you using (Help->About in the CIW)? And which version of spectre (should appear at the top of the log file)?
Can you check in the input.scs and post the envlp analysis line that you see in this file?
In reply to Andrew Beckett:
Thanks for your answer!
The version of icfb is 5.1.0, the sub-version 188.8.131.520.5.96!
If I generate the netlist in an OCEAN script, in the file input.scs there is not the clockname, as shown in the following lines:
envlp envlp harms=1 stop=200u errpreset=conservative readic="enc.fc" \
writefinal="env.fc" method=gear2only relref=alllocal lteratio=10 \
But if I write the clockname in the file, the OCEAN simulation works.
Why do you think I have this problem?
Is it possible to change this file directly from the OCEAN script?
In reply to Ueue:
I did a bit of searching, and found exactly the same problem reported (in IC612) which was fixed (under CCR 466387) in November 2008. I certainly don't see the problem in the latest IC5141 ISR, so I think you will need to install the latest hotfix, or alternatively specify a frequency or period directly rather than via a clockname.