Stats

  • Locked Locked
  • Replies 21
  • Subscribers 148
  • Views 31785
  • 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

pCell skill for beginners

stuso

Hi,

i'd like some advice for creating my first simple pCell from skill. I have no skill experience so i'm looking for a good place to start.

My ultimate aim (for now) is to create a rectangular via array with X and Y stretch handles. For example you have M1->M4(the top & bottom layers would be parameters) that you can stretch in X or Y and it fills with the max vias allowed by spacing rules. However to begin with i'd be happy to create a parameterised rectangle of M1 that i can stretch in one direction & take it from there.

Pointers to on-line tutorials and very simple examples would be great, right now i am blindly searching around source-link.

Thanks

Stu

Parents

  • Hi Stuart,

    1. Simple way would be to add something like w=max(w 0.2) and l=max(l 0.2) (0.2 is just an example of a minimum) before the rodCreateRect. That would clip it to the minimum value.
    2. Surround the pcDefinePCell call in a procedure definition, and then load the SKILL code from a file called libInit.il in  the library that contains the pcell ("stu_test_skill" in this case).
      The reason for wrapping the pcDefinePCell is a procedure is that you don't want to redefine the pcell every time it gets loaded - just when you choose. By having the code loaded from libInit.il, it will get auto-loaded by PVS, by Virtuoso, for any user that references the library. If you put the code in the .cdsinit, it won't get picked up by PVS.

    Regards,

    Andrew.

Reply

  • Hi Stuart,

    1. Simple way would be to add something like w=max(w 0.2) and l=max(l 0.2) (0.2 is just an example of a minimum) before the rodCreateRect. That would clip it to the minimum value.
    2. Surround the pcDefinePCell call in a procedure definition, and then load the SKILL code from a file called libInit.il in  the library that contains the pcell ("stu_test_skill" in this case).
      The reason for wrapping the pcDefinePCell is a procedure is that you don't want to redefine the pcell every time it gets loaded - just when you choose. By having the code loaded from libInit.il, it will get auto-loaded by PVS, by Virtuoso, for any user that references the library. If you put the code in the .cdsinit, it won't get picked up by PVS.

    Regards,

    Andrew.

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.