• 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. how to create pin(pinname<1:10>) using skill scripting.

Stats

  • Locked Locked
  • Replies 15
  • Subscribers 143
  • Views 9873
  • 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

how to create pin(pinname<1:10>) using skill scripting.

sritha
sritha over 12 years ago

Hi All,

I am new to skill scripting. could please give me the guidelines to create pin (pinname<1:10>).

Thanks,

Leela.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Leela,

    Is this in a schematic, a symbol, or a layout (where probably you'd want 10 individual pins)?

    In general you'd do:

    net=dbMakeNet(cvId "pinname<1:10>")
    pinMaster=dbOpenCellViewByType("basic" "ipin" "symbol")
    pinFig=dbCreateInst(cvId pinMaster "" 0:0 "R0")
    pin=dbCreatePin(net pinFig)

    Or you could use:

    pinMaster=dbOpenCellViewByType("basic" "ipin" "symbol")
    schCreatePin(cvId pinMaster "pinname<1:10>" "input" nil 0:0 "R0")

    Something like that.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sritha
    sritha over 12 years ago

     In layout.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Obviously you'll need to create separate pins for each bit, so you'd do something like:

    pinWidth=0.5
    pinPitch=1.2:0
    pinOrigin=0:0
    pinLayer="Metal1"
    pinDirection="input"
    busPin="pinname<1:10>"
    foreach(pinName dbProduceMemName(busPin)
      ; create the pin shape, then the net (if it doesn't already exist), and then create the pin
      pinFig=dbCreateRect(cvId pinLayer list(pinOrigin xCoord(pinOrigin)+pinWidth:yCoord(pinOrigin)+pinWidth))
      net=dbMakeNet(cvId pinName)
      pin=dbCreatePin(net pinFig)
      ; make sure the terminal direction is what we want too
      pin~>term~>direction=pinDirection
      pinOrigin=xCoord(pinOrigin)+xCoord(pinPitch):yCoord(pinOrigin)+yCoord(pinPitch)
    )

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sritha
    sritha over 12 years ago

     Thank you, I used "dbProduceMemName()" in foreach loop to get each pin bit and then created a pin.  Its working good.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Purge2343
    Purge2343 over 5 years ago in reply to Andrew Beckett

    *Error* eval: unbound variable - cvId

    I tried this for generating schematic pin list and I have the following error 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Purge2343

    If you have the schematic window open, do:

    cvId=geGetEditCellView()

    first to store the database object of the cellView you're hoping to update into the variable cvId.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Purge2343
    Purge2343 over 5 years ago in reply to Andrew Beckett

    Thank you for your reply,
    I have one more quick question.
    I want to create multiple buffers with different i/p and o/p. Is there a way to do it in skill? 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Purge2343

    I'm sure "it" can be done in SKILL - I just don't know what it is you're asking for!

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Purge2343
    Purge2343 over 5 years ago in reply to Andrew Beckett

    I want to create 71 buffers with 71 input pins and 71 output pins all the buffers are of same size.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Purge2343

    Well, you can definitely do that in SKILL.

    Regards,

    Andrew.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
>

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