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.
Hi,One problem we're finding is inexperienced layouters/designers inadvertantly moving instances by accident. In the Schematic tool they are getting used to clicking outside the area to deselect everything. In layout this is not always possible and if the last stacked command they have is move, then a double click ends up shifting some instance a few microns, which if found days / weeks later could mean a lot of rework of layout to move devices which have been placed in what looks like a blank space, but is actually taken up by devsices in the 'correctly' spaced instance.Is there a way to lock instances so that they can not be moved by accident? I know that we can turn off instance selection in the LSW but this means that instances of devices can not be manifulated in the layout of a cell.I'm looking to lock certain cells by name if possible.Thanks,Dave C
Dave,There are two commands recently added to Cadence (within the last 3 years) that help do this.leRegUserLayerSelectionFilterleRegUserObjectSelectionFilterThese two commands register functions that you create to be used as selection filters. The layer selection filter is the simpler of the two. It registers a routine that accepts an lpId (layer purpose object id). If you want the layer to be selectable, the routine returns t, otherwise it returns nil. This will make layers unselectable in the LSW and users will not be able to make them selectable. You will need to re-run leRegUserLayerSelectionFilter if your layer selectability criteria changes. We use this to lock down layers after they tapeout since we don't tapeout all layers at once. We have a separate interface to change what is "permanently locked".The second routine is what you are looking for. It registers a routine that you create that will accept an object id. The code will determine if the object is selectable or not and return t or nil. This routine must be written efficiently since it effectively runs everytime your cursor moves over a new object. If you have the dynamic hilight option turned on, then you see a dotted line appear over selectable objects when you move your mouse. Your routine will be called prior to displaying this dynamic hilight. If your routine indicates the object is not selectable, then it will not hilight. Keep your code efficient.We wrote an interface that allows users to mark cells as "unselectable". This information is saved in the cellview. Our routine simply checks to see if the cell is read-only. If it is, then the filter is not applied. If the cell is editable, then if the object id is an instance or a mosaic or a mosaicInst, then it's cellname is compared to the list of unselectable cellnames. If the name is in the list, nil is returned, otherwise it returns t.I hop this helps.-Derek