Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Layout efficiency: Substrate tap, nwell tap, vias, improved MOSFET cells #265

Open
hpretl opened this issue Nov 16, 2024 · 8 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@hpretl
Copy link
Contributor

hpretl commented Nov 16, 2024

Maybe I just don't know how to do it properly, but it looks like a few fundamental thing are still missing from the KLayout setup:

  • Via generator (with selectable start and end layers, and number of X/Y multiples)
  • Substrate contact (maybe merge into via generator); ideal would be the possibility to make a substrate contact as a path
  • Option to NMOS pcell to add a guardings
  • Nwell contact (maybe merge into via generator); ideal would be the possibility to make an nwell contact as a path
  • Option to PMOS pcell to add a guardings

In addition, it would be good have the option in the MOSFET pcells to have the gates connected.

@KrzysztofHerman KrzysztofHerman added the enhancement New feature or request label Nov 18, 2024
@KrzysztofHerman KrzysztofHerman self-assigned this Nov 18, 2024
@KrzysztofHerman
Copy link
Contributor

@hpretl thank you for your comment.

there is ongoing discussion of the via should be generated natively by the tool, Klayout in this case, or as a separate PyCell. Do you have any opinion on that ?

Substrate/Nwell contacts are among the devices that are planned to be delivered soon.

I have develop a guard ring PyCell and I can share the code. The feature to have it as a mosfet PyCell option we have to discuss internally.

@hpretl
Copy link
Contributor Author

hpretl commented Nov 18, 2024

there is ongoing discussion of the via should be generated natively by the tool, Klayout in this case, or as a separate PyCell. Do you have any opinion on that ?

As a via/viastack is a fundamental component of any PDK, a KLayout implementation would definitely make sense. But given the current state where custom layout in KLayout is really cumbersome due to lack of vias any solution in a reasonable timeline would help. 😀

@hpretl
Copy link
Contributor Author

hpretl commented Nov 18, 2024

@KrzysztofHerman One more argument for having vias inside KLayout: Eventually I would like to have a path function where I can change layers while routing. For this functionality, we need vias, and probably everything is easier if vias are a native functionality of KLayout.

@sergeiandreyev
Copy link
Contributor

btw, regarding the Via question..
I guess we did not open any GitHub request on KLayout to track this item, there was only email communication

@hpretl
Copy link
Contributor Author

hpretl commented Nov 18, 2024

@sergeiandreyev Could you please open a KLayout issue (or should I)? Would be great to track this feature request there.

@sergeiandreyev
Copy link
Contributor

ok, will do

@sergeiandreyev
Copy link
Contributor

FYI, KLayout/klayout#1931

@sergeiandreyev
Copy link
Contributor

But given the current state where custom layout in KLayout is really cumbersome due to lack of vias any solution in a reasonable timeline would help.

@hpretl, maybe for the time being you can use the via Pycell (via_stack) from the old version of IHP OpenPDK as a temporary workaround:

> git checkout 8dbe642b8c0512d3c6b52feee1e3beac837b191e

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants