Forum Replies Created
-
Posts
-
Hi Keith,
I created a symbol for a NMOS(I followed the symbol creation guide from the forum) and was able to assign relevant propeties like, W, L, instanceName & modelName etc. When i use this symbol in schematic and later export it to CDL netlist I get the Instance name as I0, I1 etc… But gemini gives me an errors saying that the instance is not recognized LVS aborted, when I changed the name of the instance manually to M0, M1 etc it ran the lvs properly and shows appropriate match or mismatch accordingly.
My question here is using the @instanceName can i force the instance name to begin with M* instead of I*. Or is there something else that I might have missed?
Regards,
RiyazHi Keith,
I wanted to know if I want to write extraction for Asymmetric Devices
?: like DEMOS. Should I use extractDevice() and define the Drain and Source accordingly?Regards,
RiyazHi Keith,
I referred the example ext.py and have found where I went wrong in the extraction, Now its getting extracted as expected.
Thanks,
RiyazHi Keith,
I have created an extraction file.
And I also have created PCells.I have a Pcell NCH* & PCH*
When I use these Pcells in layout and later extract them. The extracted view shows me 2 geometries of the cell overlapping each other instead of one.I'm attaching the extraction file for reference. Please let me know whats going wrong.
Regards,
RiyazAs of now I'm using 4.5.24, Will download the latest version of the tool and get back to you.
Thanks Keith for such fast and prompt response.
Hi Keith,
The flags are Horizontal & Vertical. What if I want to have it checked both the sides. Is there some intermediate flag like "Both" ?
Thanks,
RiyazHi Keith,
The geomAllowedWidths() function is not working for some reason,
When used in the rule deck it gives the following error while i run it.geomAllowedWidths(VIA1,0.26)
NotImplementedError: No matching function for overloaded 'geomAllowedWidths'See if there is anything wrong with the function or with the syntax that i have used above.
Ex: geomAllowedWidths(VIA1,[0.26])
Regards,
RiyazHi Keith,
The Pcell which are present and also I had created few PCells of my own, One thing which is bugging me here is, when the cell is invoked as an Instance while doing the layout the Move option doesn't work on it. I have to flatten the cell and then it moves. This is very much hindering the speed of doing layouts. Please fix this.
Regards,
RiyazThanks a lot Keith,
As you mentioned I'll try to port the Cadence techfile in the format of Glade techfile.tch so that I can get maximum benefit out of it rather than writing a python code for MPPs & VIAs.
Regards,
RiyazThanks for fast response Keith,
Any easier way for me to create the VIAs, Any python template or code which I can write. Any similar example as the one you gave me before for MPP like python code for creating VIAs.
Regards,
RiyazHi Kieth,
As I had discussed earlier regarding MPPs, likewise I also wanted to know on how to create VIAs for different metal levels.
Note: I am able to read the Cadence techfile and Glade techfile in one common library, but as the layers and all are different I have to write the Cadence techfile in the same format as Glade techfile i.e. example.tch.
Can you please try on adding a functionality where the Glade can parse Create Vias and MPPs directly from the Cadence techfiles.
Thanks,
RiyazKieth,
I can work around with the quick solution that you mentioned for now. But I feel that it would be a great enhancement overall if you add the MPPs parsing from the native Cadence techfile. Because this will allow me to use the MPPs of any cadence tech-files without any need of modifications or additions.
Hope to see this feature soon. :angel:
Thanks a lot…
