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 sometimes see a strange behaviour when creating a layout in IC6.15:
Starting at some time (do not know when/why) doing a fit does fit the layout in the middle of the layout editor, but there is a huge black area around it. So the size of the layout (rectangle form) shown is <<50% of the available area in x and y direction. When adding this block into an other layout, Virtuoso indicates a very big device size/boundry (dashed line) when hoving over the block.
I know this might happen if a small device/path/contact is placed outside of the main layout block (and due to its small size it might be nearly unvisible).
But: I (and my colleagues) have checked for such things about 100 times (including changing the visability and selectivty of layers, changing the shown layers at the Techfile, marking & deleting everything outside the block, ...). We are absolutely sure that there is no device left outside of the instance's boundry!
Has anybody an idea what might cause this behaviour and how we can get rid of that effect?
The only way we found yet, is to copy the whole layout into a new layout cell...
Thank you very much!
In reply to ColinSutlieff:
thank you for this hint.
We tried it, but we it didn't solve that issue :-(
I'll update the software to the most recent version. If it will occur again, I will send an other post :-)
we are facing the same problem.
Unfortunable your proposal doesn't fix this.
What about your other ideas?
In reply to wschwab:
It is possible that there are steiner objects that are causing this problem.
Try this in the CIW:
foreach(st geGetEditCellView()~>steiners dbDeleteObject(st))
Hope this helps
thank you very much! For my design(s) this works great!
running extract after deleting the Steiners and the Boundary is as it should be.
Thanks for the solution.