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 want to know how to write a ocean script that can create a file to display all MOS' region,but I don't know the function.
How to know that where are All MOS in ??
If you mean that you need to determine a region which each MOS in after some simulation, I'm affraid there is no one function to do this and you'll have to read skill docs to obtain a methodology.
If you are talking about values of the CDF description of each MOS (some CDF descriptions have the "reagion" parameter) I think "dbGet" function coul help you.
In reply to VKhlyupin:
If you're using OCEAN, and you've run a DC operating point simulation, then you can use the report() function to do this.
analysis('dc ?saveOppoint t)run()selectResult('dcOpInfo)report(?param "region")
You'll get the region of each device returned as a number. If you look at "spectre -h modelType" - e.g. "spectre -h bsim4" you get:
1 region=triode Estimated operating region. Spectre outputs the number (0-4) in a rawfile. Possible values are off, triode, sat, subth, and breakdown.
and for "spectre -h bjt" you get:
3 region=fwd Estimated operating region. Spectre outputs number (0-4) in a rawfile. Possible values are off, fwd, rev, sat, and breakdown.
So the numbers correspond to the various regions. So for a MOS, 2 means it is in the saturation region.
The previous reply talking about CDF parameters is not relevant - that was (presumably) talking about the instance parameter region - which is merely a hint to the simulator as to which region the device is in, to help with DC convergence (an option that is rarely set, because it's not that practical to set it on each transistor, and anyway it's not the final region - just a clue to the simulator to tell it (say) that the device is off and hence to expect it to be off when trying to reach DC convergence).
In reply to Andrew Beckett:
Thank you,the results are displayed in terminal using your function .But I want to save the results into a text file,can you give me some suggestions?
Can i use such a way to write the results into a text file?
Thank you very much!
In reply to MOSMOS:
ocean> ocnHelp 'report PROTOTYPE report([?output t_filename | p_port] [?type t_type] [?name t_name] [?param t_param] [?format s_reportStyle] [?maxLineWidth charsPerLine]) => t/nil...
So you can do report(?output "./region.txt" ?param "region") or report(?output p ?param "region")