• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. List of symbol pin names and direction using SKILL

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 144
  • Views 19261
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

List of symbol pin names and direction using SKILL

Tobben24
Tobben24 over 12 years ago

Hi,

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:)

  • Cancel
Parents
  • Theo38240
    Theo38240 over 11 years ago

    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[6]. 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 ? 

    Exemple :  

    module AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATST_1_131(XBIPBIP, ABIP, AB, DVSSBIPBIP, DVDDBIPBIP);

    output[131:1] XBIPBIP;

    input[11:2] ABIP;

    input[11:2] AB;

    input DVSSBIPBIP, DVDDBIPBIP;


    AAA_COL1U1SRAM_ADD_DEC cell1(  XBIPBIP[1],   ABIP[2],   AB[3],   AB[4],   AB[5],   AB[6],   AB[7],   AB[8],   AB[9],   AB[10],   AB[11], DVDDBIPBIP, DVSSBIPBIP );

    AAA_COL1U1SRAM_ADD_DEC cell2(  XBIPBIP[2],   ABIP[2], ABIP[3],   AB[4],   AB[5],   AB[6],   AB[7],   AB[8],   AB[9],   AB[10],   AB[11], DVDDBIPBIP, DVSSBIPBIP );

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Theo38240
    Theo38240 over 11 years ago

    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[6]. 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 ? 

    Exemple :  

    module AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATST_1_131(XBIPBIP, ABIP, AB, DVSSBIPBIP, DVDDBIPBIP);

    output[131:1] XBIPBIP;

    input[11:2] ABIP;

    input[11:2] AB;

    input DVSSBIPBIP, DVDDBIPBIP;


    AAA_COL1U1SRAM_ADD_DEC cell1(  XBIPBIP[1],   ABIP[2],   AB[3],   AB[4],   AB[5],   AB[6],   AB[7],   AB[8],   AB[9],   AB[10],   AB[11], DVDDBIPBIP, DVSSBIPBIP );

    AAA_COL1U1SRAM_ADD_DEC cell2(  XBIPBIP[2],   ABIP[2], ABIP[3],   AB[4],   AB[5],   AB[6],   AB[7],   AB[8],   AB[9],   AB[10],   AB[11], DVDDBIPBIP, DVSSBIPBIP );

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. 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. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information