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 think one definitely would have faced this problem while integratiing many instances/blocks in the top level layout in Virtuso.
The problem I am facing is as follows:-
In the top level of the layout, I have to integrate many instances of layout blocks.
While connecting two blocks ( these two blocks are inside a bigger blocks (like PAD array) or may be crossing over another small block) , some how some the other blocksare getting moved.
Ideally like to keep the positions of other instances ( let's say A, B, C) fixed, while editing the desired instances ( let's say E,F) as movable.
I tried in LSW. I dehighlighted the 'inst'. In that process, all the instances are becoming un-movable. Even if you bring a VIA , you can't move it around.
Could anybody please tell what I should do thing smoothly.
In IC615 (you didn't say which version you are using, and it's rather useful to know...) you can use Edit->Select->Set Selection Protection to "protect" a number of shapes/instances. This will make those objects unselectable (you can highlight them from the same menu, or temporarily override the protection, or remove the protection). That means you won't be able to accidentally select them and hence not be able to move them.
In earlier releases, you can use my SKILL code as described in this article on Cadence Online Support to do the same thing.
If you're using VLS XL you can also use the constraint manager to add a "locked" constraint on the instance to stop you being able to move it when in Constraint Aware Editing mode. Could also use a "fixed" constraint.
In IC5141 it's also possible using Virtuoso Layout XL - you have to use Tools->Constraint Manager in the CIW, and then you can add a "fixed" constraint for some instance. You have to turn on "Constraint Assisted Move and Stretch" in the Layout XL Options form too.
In reply to Andrew Beckett:
Thanks alot for your reply.
I am using IC5141. I tried Tool ->Constraint Manager in the CIW.
But couldn't figure out how to 1) Select a instance to be added to the manager
2) To make the instance Fixed
Could you please tell how it can be done.
In reply to RFStuff:
I also tried with your SKILL code.
Itis working fine.
But, I protected A,B,C
Then I want to unprtect only C , then what I should do.
I got. I think I should have selected Create, Then add the instances in the 'Fixed" option.
With that, I am able to keep them fixed in the layout but they are selectable unlike your SKILL code.
If using my SKILL code, you have two choices:
Obviously this tends to be easier if you have things defined on bindkeys. You could also define a bindkey to be:
which will toggle protect mode on or off each time you press it.
In the IC615 implementation, there's the option to unprotect an object post-selection, so you can click on it regardless of whether it is selectable (I didn't add that in my code, but it wouldn't be too difficult with an enterFunction).
Thanks a lot for your reply.
I like to do some modification to your skill code.
But the "SKILL" is a new language to me.
I want to know the meaning of each standard function present in thye code.
I went through "Cadence Analog Design Environment SKILL Language Reference", but I could not find the many functions present in your code.
Could you please point to some document/source from where I can get the meaning of all the STANDARD functions you have written in the code.
Given that this code is for the layout editor, it's hardly surprising that nothing is covered in the Cadence Analog Design Environment SKILL Language Reference.
There are functions from three groups in this code:
The code is written using LISP style (SKILL also allows you to use a C-style which is probably more common, but I tend to write most of my code using LISP style; the language is really a LISP flavour underneath, but it makes no difference to efficiency or speed which style you choose).
Hope that helps!
Sorry, I think I have searched the functions in the wrong reference.
Thanks a lot. I will dig into the documents to understand the functions.