-
Notifications
You must be signed in to change notification settings - Fork 111
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
Subhampal9 current mirror fix #355
base: main
Are you sure you want to change the base?
Subhampal9 current mirror fix #355
Conversation
1. drc and lvs reports are also attached 2. sample picture of gds is attached 3. README file and annotations in fvf.py are added
added FVF Pcell files, Analog Vibes, Chipathon 2024
Previously a ptap and pwell was layed out irrespective of the device type. Added the code to add specific tap and well layers for each device type
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
|
||
return netlist | ||
|
||
def sky130_add_fvf_labels(fvf_in: Component) -> Component: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this function be made pdk agnostic?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function is only used for LVS check
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is fine. Is it specific to the sky130 pdk? If so, can it be made generic using the MappedPDK
class?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It uses layers which are not mapped in Mappedpdk(as far as I know).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, in that case it is fine.
…F directory Now it only contains the change in current_mirror block
https://open-source-silicon.slack.com/archives/C072ZFE19FH/p1732758626658539?thread_ts=1732636138.678739&cid=C072ZFE19FH
Previously ptap and pwell was getting layed out irrespective of the device type. Codes were added to add tap and well layers depending on the device type