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'm trying to use the OCEAN outputs() function with the filter ?type in IC12.10.500 / 12.10.060 but I'm facing an error message.
I want to isolate the MOS devices from what returns the outputs() command.
Here is how I expect it to work and how it DOES work in IC6
ocean> outputs()("M0.Cs0" "M0.Cd0" "M0.Cds" "M0.Cg0" "M0.Cgs" "M0.Cgd" "M0.Rg" "M0.Rs" "M0.Rd" "M0.XM" "/V0" "/V1" "/V2" )
ocean> dataTypes()("capacitor" "resistor" "tmibsimcmg" "vsource")
ocean> outputs(?type "tmibsimcmg")("M0.XM")
EPIC SUCCESS !
Now, in IC12, everything is the very same, except the last command does not want to do the job:
ocean> outputs(?type "tmibsimcmg")*Error* car: argument #1 should be a list (type template = "l") - "tmibsimcmg"
ocean> outputs(?type "vsource")*Error* car: argument #1 should be a list (type template = "l") - "vsource"
I kinda understand there could be an evolution allowing user to have a 'list of type' instead of a single type... Actually, that could be great... Let's try to make it 'list of type' compliant then:
ocean> outputs(?type '(tmibsimcmg))*Error* _srrMakeSignalListFromType: argument #2 should be either a string or a symbol (type template = "gS") - (tmibsimcmg)
outputs(?type '("tmibsimcmg"))*Error* _srrMakeSignalListFromType: argument #2 should be either a string or a symbol (type template = "gS") - ("tmibsimcmg")
ocean> outputs(?type '(vsource))*Error* _srrMakeSignalListFromType: argument #2 should be either a string or a symbol (type template = "gS") - (tmibsimcmg)
ocean> outputs(?type '("vsource"))*Error* _srrMakeSignalListFromType: argument #2 should be either a string or a symbol (type template = "gS") - (tmibsimcmg)
I just can't get it working...
Where is the trick ?
Unfortunately, the documentation seem not have been updated for this :'(
I reproduced the problem. It's broken in IC616 ISR3/4 and ICADV121 ISR5/6 (these correspond to each other).
It's working in IC616 ISR5 (I checked a pre-release build) - that's due for release at the end of February.
In reply to Andrew Beckett:
Thanks a lot for this ! Looking forward to the next update then:)
Meanwhile, here is the (ugly) workaround:
rexMatchList( "[A-Za-z0-9_.<>]*.XM" outputs() )
That should do the job for me at the moment.