• 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. Create an alternative pmos/nmos pcell, with all virtuoso...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 1720
  • 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

Create an alternative pmos/nmos pcell, with all virtuoso functionality

RVERP
RVERP over 9 years ago

Hi,

I want to replace the nmos/pmos of the fab with an alternative pcell I have created myself.

This custom pcell uses the mos pcell, and adds things depending on the parameters I have added. Now I want to use this custom pcell in my layouts, but I also want to use the virtuoso functionality

I should be able to:

  1. Do a gen form source. The new pcell must be used.
  2. Maintain the connectivity.

Things I have so for:

  1. Gen form source: I have changed the physical cell in the physconfig. The gen from source picks the custom cell I want, but the parameters set in the schematic aren't transferred correctly to the new pcell. I have changed my custom pcell so that the names are the same as the ones I see in the cdf.
    Now if I do a gen from source, parrameters are filled in, but the numbers filled in are float (1e5), while in cdf they are a string (10u).
    QUESTION: How are parrameters tranfered to the pcell in a gen from source. Are the always passed as a float? Does this happen in a standard way or is this dependant of the techno?
  2. Maintain connectivity: I suppose adding pins/terminals is enough here. Only I have to have the naming right.
    QUESTION: Is it oke to suppose that these are s d g b by default?

I hope the above description is a bit clear, if not, I am happy to clarify is some more.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    What are the parameters on the source component in the schematic? Are these float too?

    Adding pins/terminals will be needed. You'll need to call them whatever they are called on the source device. There's no "default" naming for them - it purely depends on what the source device has called them.

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RVERP
    RVERP over 9 years ago
    The numbers in the schematic parameters have the suffix "u" so I suppose they are also a string.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RVERP
    RVERP over 9 years ago

    I still can't find a way to "replace" a pcell.

    Imagine I have a pcell is generated with generate all from schematic. Then I change the instance lib and cellname so it references to another pcell.

    What is the criterea for a parameter that it can be passed to the new cell? They are already of the same type.

    I can do it with the pcells from the fab (tsmc18), if I change the cellname from nmos to pmos, all the parameters are applied to the new cell. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RVERP
    RVERP over 9 years ago

    Update: There is something moving :)

    The values I want to pass between the pcells is width and length. I was using width as a test, and it never did what I wanted. I tried length, and it worked. Width is not working only if the value results in an integer (example width =5u), if the value is a float (width=5.1u), there is no problem. To understand what this is causing, I just know not enough of pcells.

    • Cancel
    • Vote Up 0 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