Stats

  • Locked Locked
  • Replies 13
  • Subscribers 145
  • Views 23740
  • 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 a transistor pcell in SKILL?

Elezebeth

Hi,

I am new to SKILL coding.I have not done any pcell coding in SKILL.I would like to know whether we can create mosfet pcells using SKILL code.The way I tried to do this is using rodCreateRect( ) to create different layers of the transistor say diffusion,poly,contacts etc.and allign all these layers using rodAlign( ).But the transistor that got created could not be deleted at a time....ie.the layout is flattened.If i select the rectangle that I have set as reference and try to delete the whole transistor layout doesn't get deleted, only that particular layer is deleted.

The other way I found is to do using ?subRectArray.but the problem with that is, the number of contacts in a transistor will increase as the width of the transistor increase.So the number of sub-rectangles that have to be created is variable.How to do that?

Can anybody please guide me on this?

Thanks and Regards,

Elezebeth 

 

 

Parents

  • This is something in your environment - somebody has called either dbRegPostSaveTrigger or dbRegSaveTrigger (there's a couple of other triggers it might be) and then not defined the function. The function tscSchCheckDbcv is not one of ours - my guess is that the "tsc" might give you a clue - perhaps it is related to a design kit that you're using?

    It's probably harmless, and if you do:

    dbUnregSaveTrigger('tscSchCheckDbcv)
    dbUnregPostSaveTrigger('tscSchCheckDbcv)

    (since I don't know what kind of trigger it is), that should remove the trigger and hence remove the warning.

    Regards,

    Andrew.

Reply

  • This is something in your environment - somebody has called either dbRegPostSaveTrigger or dbRegSaveTrigger (there's a couple of other triggers it might be) and then not defined the function. The function tscSchCheckDbcv is not one of ours - my guess is that the "tsc" might give you a clue - perhaps it is related to a design kit that you're using?

    It's probably harmless, and if you do:

    dbUnregSaveTrigger('tscSchCheckDbcv)
    dbUnregPostSaveTrigger('tscSchCheckDbcv)

    (since I don't know what kind of trigger it is), that should remove the trigger and hence remove the warning.

    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.