Re: issues with technology editing in version 7
Pierce Keating <[email protected]> Fri, 20 Apr 2007 18:09:03 -0700 (PDT)
| Newsgroups | gmane.comp.cad.electric.bugs |
|---|---|
| Message-ID | <[email protected]> |
--===============0678322112== Content-Type: multipart/alternative; boundary="0-507990447-1177117743=:16747" Content-Transfer-Encoding: 8bit --0-507990447-1177117743=:16747 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hello, I've since found that the metal spacing error mentioned below does get detected by the DRC. I've also discovered that connecting to the transistor pins is better than I first thought, if I work with it, but I still haven't been able to avoid OVERLAP DRC errors. Thank you, Pierce Pierce Keating <[email protected]> wrote: Hello, I have have been attempting to modify the mocmos library for the (MOSIS) AMI 1.5u SCNA ABN process. In the modified technology, I built an NPN transistor using a pbase layer, all created according to the SCNA layer map as described here: http://www.mosis.com/Technical/Layermaps/lm-scmos_scna.html (I also removed the P-Well in the N-Transistor, since this process does not have a P-Well.) There are at least two issues I have run into. First I deliberately included a metal1-metal1 spacing error to see if the DRC would detect the error but it doesn't. Also, I can't seem to connect to the pins of the npn transistor Node, when trying to use the node in a layout. Actually I can connect to them but not without a DRC metal1 spacing error. For other nodes, the layout editor seems to know to connect a metal1 arc to a metal1 port, and without DRC errors. I've attached the libary to this email. If anyone would check it out and let me know what I'm doing wrong I would appreciate it very much. Thank you, Pierce Keating --------------------------------- Ahhh...imagining that irresistible "new car" smell? Check out new cars at Yahoo! Autos. _______________________________________________ Bug-gnu-electric mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnu-electric --------------------------------- Ahhh...imagining that irresistible "new car" smell? Check outnew cars at Yahoo! Autos. --0-507990447-1177117743=:16747 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit <div>Hello,</div> <div> </div> <div>I've since found that the metal spacing error mentioned below does get detected by the DRC. I've also discovered that connecting to the transistor pins is better than I first thought, if I work with it, but I still haven't been able to avoid OVERLAP DRC errors.</div> <div> </div> <div>Thank you,</div> <div>Pierce<BR><BR><B><I>Pierce Keating <[email protected]></I></B> wrote:</div> <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid"> <DIV>Hello,</DIV> <DIV> </DIV> <DIV>I have have been attempting to modify the mocmos library for the (MOSIS) AMI 1.5u SCNA ABN process. In the modified technology, I built an NPN transistor using a pbase layer, all created according to the SCNA layer map as described here: <A href="http://www.mosis.com/Technical/Layermaps/lm-scmos_scna.html">http://www.mosis.com/Technical/Layermaps/lm-scmos_scna.html</A></DIV> <DIV> </DIV> <DIV>(I also removed the P-Well in the N-Transistor, since this process does not have a P-Well.)</DIV> <DIV> </DIV> <DIV>There are at least two issues I have run into. First I deliberately included a metal1-metal1 spacing error to see if the DRC would detect the error but it doesn't. Also, I can't seem to connect to the pins of the npn transistor Node, when trying to use the node in a layout. Actually I can connect to them but not without a DRC metal1 spacing error. For other nodes, the layout editor seems to know to connect a metal1 arc to a metal1 port, and without DRC errors.</DIV> <DIV> </DIV> <DIV>I've attached the libary to this email. If anyone would check it out and let me know what I'm doing wrong I would appreciate it very much.</DIV> <DIV> </DIV> <DIV>Thank you,</DIV> <DIV>Pierce Keating</DIV> <div> <HR SIZE=1> Ahhh...imagining that irresistible "new car" smell?<BR>Check out <A href="http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-">new cars at Yahoo! Autos.</A> _______________________________________________<BR>Bug-gnu-electric mailing list<BR>[email protected]<BR>http://lists.gnu.org/mailman/listinfo/bug-gnu-electric<BR></BLOCKQUOTE><BR><p>  <hr size=1>Ahhh...imagining that irresistible "new car" smell?<br> Check out <a href="http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-">new cars at Yahoo! Autos.</a> --0-507990447-1177117743=:16747-- --===============0678322112== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Bug-gnu-electric mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnu-electric --===============0678322112==--