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 had added two pins in schematic view.
At the same time i want to add those pins in symbol view also.
I used "schDrawSymbolPin" function to draw.But whatever it created is not consistency with the other pins already present.
i.e Creating somewhere else in symbol view,with different shapes.
How to get the exact list points where,it should be created.
Finally,how to create,or replace already existing symbol pins.
How to get the list points,because different cells will have different boundary box?
Could you please list the steps to be followed?
Thanks and regards
I suspect you really want to be using schCreateSymbolPin - this creates a pin using a cellView as a master - which is what the create pin command in the symbol editor does.
In the CIW, if you type:
you'll see which cellViews are used for which master. For example, you can see that basic/actHiInp/symbol is used for actHi input.
So you could do:
; coord is where you want to place the pin. cvId is the database Id of the symbolpinMaster=dbOpenCellViewByType("basic" "actHiInp" "symbol")schCreateSymbolPin( cvId pinMaster "myinp" "input" coord "R0")
Only you can know where on the symbol you wish to place the symbol. In the symbol editor, if you do Options->Display and turn on "Coordinates in status banner" so you can see where is a relevant location.
The same would be true if using schDrawSymbolPin - this is just expecting a list of coordinates for the red blob which is the pin. You need to determine where you want them to be - I can't work that out for you.As for replacing an existing pin, easiest to delete it and re-add it, I guess:; termName is the terminal you want to delete, cvId the cellViewterm=dbFindTermByName(cvId termName)foreach(pin term~>pins dbDeleteObject(pin~>fig) dbDeleteObject(pin))dbDeleteObject(term)
Or something like that...