• 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. Reading PCell Properties/Parameters using SKILL

Stats

  • Locked Locked
  • Replies 12
  • Subscribers 145
  • Views 7253
  • 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

Reading PCell Properties/Parameters using SKILL

frasheed
frasheed over 11 years ago

 Hello All,

I have a PCell that has nfet layout and I am writing a SKILL code to open the layout and label the Gate, Drain, Source and Bulk in layout. For that I need to read the parameters that where is the Gate, Drain and Sourcein layout. I tried some commands like :

pcGetParameters , pcGetParamLabelDefn, pcGetParamLabels, pcGetParamLayers but all of them are given me "Nil". Can anyone help me what's wrong ? Is it because the PCell doesn't have any properties ?

or is there any better way for labeling ?

Thanks

P.S: I didn't created that PCell and I am very beginner to SKILL.

 

  • Cancel
Parents
  • skillUser
    skillUser over 11 years ago

     Hi there,

    The commands that you list would most likely be used with a graphical PCell rather than a SKILL PCell. I'm a little confused by your question, is the PCell an nfet itself, or does it instantiate an instance of an nfet inside the PCell?  Also, the terminals (G, D, S, B) are not parameters; these will be physical shapes that are associated with pins, nets and terminals (these last three are all logical database objects).

    If I understand you correctly you wish to label the terminals - this can be achieved in one of two ways: create labels within the PCell code, or label the terminals on the (each) instance. It may be possible that the instance pin names can be 'turned on' using the Options -> Display "Pin Names" setting, though I think this might apply to terminals in the layout rather than the instance terminalson instances...

    If you can clarify a bit more about what you have then hopefully we (forum members) may be able to help you.

    Regards,

    Lawrence.

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

     Hi there,

    The commands that you list would most likely be used with a graphical PCell rather than a SKILL PCell. I'm a little confused by your question, is the PCell an nfet itself, or does it instantiate an instance of an nfet inside the PCell?  Also, the terminals (G, D, S, B) are not parameters; these will be physical shapes that are associated with pins, nets and terminals (these last three are all logical database objects).

    If I understand you correctly you wish to label the terminals - this can be achieved in one of two ways: create labels within the PCell code, or label the terminals on the (each) instance. It may be possible that the instance pin names can be 'turned on' using the Options -> Display "Pin Names" setting, though I think this might apply to terminals in the layout rather than the instance terminalson instances...

    If you can clarify a bit more about what you have then hopefully we (forum members) may be able to help you.

    Regards,

    Lawrence.

    • 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