Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 13596
  • 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

Toggle implant layers in qcells

MarkTown

 Hi,

     I got the qcells working for a pfet and a nfet.  Liked how well that worked.

     We have 2 VT layer to adject the Vts in our process. So I need them to be toggled on and off. I can get the layers to be added. But I couldn't figure out how to get them to toggle so they are not in the layout or are in the layout.

 

    Secondly, I'll need to create some devices that aren't in the qcell code. Is the code behind the qcell menu accessable to be modified?

 

thanks

Mark

  • 1st when I do a q on the instanciated qcell the Edit Instance Property form doesn't come up. Instead the Edit Qcell Propertiesform opens.

    Then I notice the parameter botton is greyed out. So I can't get to the parametors to change what would normally be there.

     

    Any thoughts on this?

  • What I learned:

        While Qcells create very functional mos devices very quickly, they do have some limitation.

        While implants can be added to the mos devices, there is no opt ion to make implants optional. As in we have different VTs but don't want them all the time there is no way with Qcells to make them toggleable in any specific placement.

  • Hi Mark,

    Did you consider "wrapping" the QCell in a PCell so that the PCell takes one extra parameter, the toggle option for the implant layer, and use this to decide whic of two QCells should be placed (the one with the implant, or the one without), and all the other parameters are passed directly to the QCell.  I have not tried this, so I don't know if you lose flexibility in the QCell instances (for example, you would get the Edit Instance properties form for the PCell instances, rather than the Edit QCell Properties form that you have been getting for the QCell instances, and the chaining etc. that you can do directly on the form would not be form driven by that interface any longer.)

    Just a thought.

    Regards,

    Lawrence.

  •  Hi Lawrence,

        I hadn't thought of doing that. Sounds like a pretty good suggestion. Not sure I've had enough experience programming to impliment that. But I'll keep it in mind.

     

    thanks

    Mark

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.