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.
Hello, Cadence community,
A short question: has anyone tried to simulate extracted views and change them from the ocean environment?
I have, but didn't succeed (I'm not new to OCEAN or SKILL, so if anyone has any solutions, the level of complexity doesn't matter)... If I understand correctly, one can do this in several ways:
1) create a config file and bind the schematic to the extracted view;
2) bind the extracted view directrly from ADE using setup->environment options-> first two textboxes from the top...
I've tried to implement this in ocean and declare these lines in my script:
envOption('switchViewList '( "spectre" "cmos_sch" "cmos.sch" "schematicExtract" "veriloga" "ahdl"))
The schematicExtract is my extracted schematic :)
The lines above do not change the extracts, OCEAN still uses the simple schematic (not extract) during simulations...
I understand, that the hierarchy should be created (updated) for the software to bind extracts with schematics, but is there any way of doing that in OCEAN? May be OCEAN scripts are not capable of changing between extracted views?
By the by, the scripts DO calculate extracts when I first configure the config file (or through ADE) and then load the script. But as I mentioned earlyer - the calculations are conducted with only the present extract and if I try to change it to another one (now using the OCEAN lines and not from ADE or config file), nothing happens...
By the way, I do not generate the netlist after setting envOption in the script - maybe that's the case? (though I doubt it)
This should work fine - but I suspect it's related to how you've specified the design via the design() function in your OCEAN script.
Note that you don't have to renetlist for this to work - the run() function does a netlist and run (and does an incremental re-netlist as needed).
In reply to Andrew Beckett:
Thanks for the fast reply.
I've declared my design through design("/path/to/netlist") and as You said, it doesn't work.
After declaring the schematic with:
design("libName" "cellName" "schematic")
the lines with envOption now seem to work properly.
In reply to Alex Vasjanov:
Another question arose: say I have a schematic with only a block that has an extracted view and I need to change it's extracts within OCEAN. I assume that the envOption way isn't suitable for this. (didn't work for me) I can solve this with creating different config files every single of which binds the desired extract to that particular block and then change them (the configs) in the script.
Maybe there's another way, a smarter one?