Closed nbingham1 closed 3 years ago
Two changes have been made and pushed.
(1) There was an error message in the fet type (both n/p fet errors were printed out as pfet; now fixed).
(2) The second issue is that width and length parameters are maintained as an integer multiple of the manufacturing grid (default is 5nm). The configuration file settings have lambda=0.03 meters used to work-around the issue that Skywater's model deck includes a global scale factor of 1e-6, forcing all input spice decks to multiply device w/l by 1e6 to compensate.
Instead, use what you actually mean: lambda=0.03e-6. That will get rid of the error; the error was caused by an integer overflow in width/length calculations. A new option "-s scale" has been added to prs2net to scale all transistor parameters by the specified scale factor. So you can workaround the scale factor in the Skywater technology setup using "-s 1e6" as an option to prs2net.
It works, that was amazingly fast. Reported at 10pm, fixed by 6am o.O
Is it possible to associate the scale factor directly with the configuration file instead of having it as a CLI option?
Complete test cases make debugging easier. :-)
Yup, you can do that right now. Use: real output_scale_factor 1e6
in the net
section of the configuration file.
Perfect, thank you!
Describe the bug Act incorrectly errors against the maximum nfet width limit when writing the netlist for a pfet transistor for the skywater 130 open source pdk.
Here are the relevent global.conf rules (whole file posted below)
To Reproduce Steps to reproduce the behavior:
ACT source global.conf
wchb.act
Expected behavior prs2net should complete without errors
Computer setup (please complete the following information):