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 want to create path leCreatePath() to connect between terminals of instances in the layout, i used inst_id~>instTerm~>termPosition to get the drain, source, gate and bulk coordinates to draw a path from these coordinates but the output i get is (nil nil nil nil). Is there a better way to draw a path without using coordinates(using the database ids' of the terminals) ?One more question, How can i get the db_id of terminals that are tied together in the schematic ?ThanksTaher
In reply to TaherKotb:
If this is so urgent that you need to chase it within a day, you really should be using customer support. This forum is manned by volunteers (including those folks such as me who work for Cadence) - who try to fit this in during their spare time (which is rather limited for me at the moment), and as such you shouldn't expect fast response.
termPosition is not what you want. From the documentation:
Returns the position to which this terminal is assigned. Assigning a position or indicating an order for terminals is typically used by netlisters to compare the actual pin position to the position specified in the netlist.
In fact the terminals are not what you need. It's the pins - because the pins carry the physical information (e.g. geometry) of the pins, whereas the terminals hold the connectivity information.
So, assuming your instance has instTerms - which it will if it was created in VLS XL - you can find the figures. For example:
inst_id~>instTerms~>name("D" "G" "S")inst_id~>instTerms~>term~>pins~>figs(((db:0x18a87315 db:0x18a8731b)) ((db:0x18a87323)) ((db:0x18a87314 db:0x18a87316)))
So as you can see, some of these may have more than one fig (in OA-based releases). For example:
D_figs_bboxes=foreach(mapcar D_fig D_figs dbTransformBBox(D_fig~>bBox inst_id~>transform))
(((19.73 6.41) (20.03 7.61) ) ((19.79 6.41) (19.91 7.61) ))
This gives me a list of the transformed bounding boxes (i.e. the location of the pins) in the coordinate space of the cellView. The pin figures are in the instantiated master, and hence we have to transform it into the current cellView using dbTransformBBox.
Alternatively maybe you can use lxSelectedRoute to auto-route the selected nets?
I didn't really understand your second question. You also didn't say which version you're using, or whether you're using Layout XL or not.
In reply to Andrew Beckett: