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 able to create config view and extracting netlist from the config view in a simpler way. I will put my SKILL code here soon. But suggest me one thing, when ever I am connecting the pins of two instances by skill code ( schCreateWire ) they are getting connected in random order i.e. pin A of instance I0 is getting connected with pin B of I2 instead of getting connected to pin A of I2 . I want to connect the nets of same pins of two insatances ( i.e. pin A of I0 to pin A of I1 ). Please suggest some way to connect the pins properly.
As I said in the other post, without seeing your code, it's pretty much impossible to guess what you're doing wrong. schCreateWire creates wires between two coordinates, so presumably you just got the coordinates wrong. I doubt anything is really random.
In reply to mobileee:
It's very hard to read the code, because the formatting is terrible. Anyway, the key problem is that you are building the array inside a loop:
a[i] = wireOriginX i++ wireOriginY=(instTermLLY+instTermURY)/2 a[i] = wireOriginY i++
but the order of the loop is completely dependent on the database - you just have a foreach loop over the instances. That seems a very dangerous and illogical thing to do.
A far better approach would be to have a function which allowed you to find the coordinates of a particular pin on a particular named instance - something like:
) ; defun getPinPositions
This returns a has of pin positions for a particular master, indexed by pin name. I'd probably then keep a hash of all these hash tables indexed by cellView. You can then look up the location of a particular pin name in a particular cellView, and transform it (using dbTransformPoint) using the transform of the instance of that cellView, and do the same for the other instance and pin you're trying to connect to.
That way you can then describe your wiring as a set of connections from pin A of I1 to pin B of I2 and so on. No need for any assumed orders of the database.
Sorry for a not particularly complete example - I wanted to outline the principle. I think your code at the moment has too many assumptions hard coded in - better to try to make it more generic - give yourself the ability to create wires between pairs of named instance/pin combinations, and you'll find it much easier.