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 get a list of pins names and which direction the pins have from a symbol/schematic. I guess SKILL is the way to go? I new to SKILL, so if someone could push me in the right direction I would be grateful:)
Okay, so I've been playing around and found a function call schSymbolToPinList. This gives me what I want, however it gives a bit too much info. I only want a simple list like this:
I am able to use perl or similar script to fix this, but if SKILL can do this I'm interested to do this in one operation:)
In reply to Tobben24:
cv=geGetEditCellView() ; or wherevertermDirMap=foreach(mapcar term cv~>terminals list(term~>name term~>direction))
Does that do what you want?
In reply to Andrew Beckett:
Hi Andrew, I try to get the accessDir of my different pin from my symbol cell. Because i try to create automaticelly a verilog file for creating a schematic decoder who use my logic cell. So i must to have the differents pins from my symbol and the direction ( left right top bottom) because i need the CORECT order of my pins => DVDDBIPBIP must to connect to DVDDDBIPBIP and not AB. Actually I use that for having the order => cv~>nets~>term~>name / but it's not the good order of my pins. When i create a symbol from my schematic i put some pins in the left list some pins in the right list... so the order pin is different and i think i could find the order if i find the pointer on this diffrent list ( left right...) but there is nothing in cv~>lpps~>shapes~>pin~>accessDir... so i don't understant how cadence manage the order to connect the pin when it use a verilog file. Do you know ?
module AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATST_1_131(XBIPBIP, ABIP, AB, DVSSBIPBIP, DVDDBIPBIP);
input DVSSBIPBIP, DVDDBIPBIP;
AAA_COL1U1SRAM_ADD_DEC cell1( XBIPBIP, ABIP, AB, AB, AB, AB, AB, AB, AB, AB, AB, DVDDBIPBIP, DVSSBIPBIP );
AAA_COL1U1SRAM_ADD_DEC cell2( XBIPBIP, ABIP, ABIP, AB, AB, AB, AB, AB, AB, AB, AB, DVDDBIPBIP, DVSSBIPBIP );
In reply to Theo38240:
In general it's best to connect to verilog by name (i.e. explicit connections) rather than by order. That way you don't need to worry about pin orders.
If the netlister is taking care of netlisting both the module and the instance (e.g. if it's an instance of a schematic), then the order doesn't really matter, because it will be consistent anyway.
If it is an instance of a textual view, and it is doing implicit connections (by order rather than by name), then the Verilog netlister would find:
cv=dbOpenCellViewByType("mylib" "mymodule" "functional")cv~>portOrder
and you might see: ("XBIPBIP<131:1>" "ABIP<11:2>" "AB<11:2>" "DVSSBIPBIP" "DVDDBIPBIP")
If you want to find out port directions (I think that's what you wanted rather than accessDir), then you'd use:
cv~>terminals~>name("XBIPBIP<131:1>" "ABIP<11:2>" "AB<11:2>" "DVSSBIPBIP" "DVDDBIPBIP")cv~>terminals~>direction("output" "input" "input" "input" "input")
The order of these two is the same. Note that it may not be the same as the order of the portOrder property though, AFAIK.
Looking the physical attributes of the pins (i.e. position etc) won't help you much I don't think. I don't believe accessDir is used on symbols (it's more for layout use, to restrict the direction that you can approach a pin from).