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 am working on a design that uses a number of level shifters, whose height is unfortunately not a multiple of the standard cell height (level shifter height is 3.9µm whereas the standard cell height is 2.6µm).
In order to accomodate this, as per the recommendations in the NIMH section of the Floorplan design user manual, I have set up seperate power domains for all the different types of level shifters, containing only instances containing just level shifter cells, and create the rows within these power domains via the createRow command, specifying the new appropriate core SITE to use:
createRow -site CORE_LS -noFlip -noAbut -spacing 1.3 -powerDomain PD_LS1
This creates the correct rows, but unfortunately during the placeDesign (and refinePlace) steps, the level shifter cells are not placed within these rows, and in such a way that the followpins that are created do not line up properly with the power rail connections within the cells.
While it is possible to force correct alignment of these cells through the use of the snapFPlan and some scripting, violations are generated, and some domains have incomplete followpins.
Therefore could anyone give me some guidance as to how to align these level shifters properly within the rows of their respective power domains to avoid such problems?
Thank you for your time and trouble,Franchie.
In reply to Kari:
Hello, and thanks for your help!
Because the level shifters are not multiples of a standard cell height, according to the Cadence documentation they must be placed in their own power domains. This was done, I believe, correctly, but still did not align them with the rows.
The tape-out has passed now, so I gave up trying to find a solution to this and instead concentrated on getting the cells in the right place through less elegant methods. I was able to get limited success by using the adjustPowerDomainToAlignRows command, which resized the various power domains in order to align their rows.
Thank you for your help in any case, it is really greatly appreciated!