MAGIC Magic Mailing List
 
 

From: Philippe Pouliquen (philippe AT alpha DOT ece.jhu.edu)
Date: Wed Apr 30 2003 - 11:42:32 EDT

  • Next message: R. Timothy Edwards: "Re: layer density in magic techfiles"

    Hi Tim,
    
    On Wed, 30 Apr 2003, R. Timothy Edwards wrote:
    >
    > In addition, I would like to get away from the habit of labeling all
    > technologies "scmos". Since version 7.2 is able to load and reload
    > technology files on-the-fly, it makes more sense to match the name in
    > the tech file to something having to do with the actual process and
    > vendor (e.g., "ami05").
    
    Well, there's the tech file name and there is the tech name.  Which is the
    one you want to get rid of?  Jeff has already gotten rid of the
    scmos.tech27 tech file name.  And the tech name itself is to tell magic
    whether the currently loaded tech matches the layout you are trying to
    load (the "tech xxx" in the tech file and layout file must match).
    
    When I use vendor design rules, I use a different tech name.  For instance
    "tech sos" for all my Peregrine designs.
    
    I think Jeff has it the right way:  Magic displays the "description" entry
    of the tech file on start up, so you know what rule set got loaded.  Then,
    as long as you have a copy of the correct tech file in your layout
    directory, under the generic name of scmos.tech27, the tech file gets
    loaded on start up.
    
    There's no point having a "tech xxx" entry at all if you're not going to
    do any checking.
    
    Perhaps "magic.tech" would be a better name for the default tech file
    name.
    
    > The widespacing rule is problematic largely because it describes a
    > discontinuous rule.  For all the simple edge-based rules, moving a piece
    > of layout by 1 unit will increase or decrease the DRC violation area by
    > 1 unit.  With the widespacing rule, moving or stretching certain pieces
    > of the layout can cause large areas of DRC violation to suddenly appear
    > or disappear.  The main consequence of this is that there is no single,
    > obvious way to define a widespacing rule.
    
    This is currently handled by making the wide metal (or narrow metal) a
    different tile type.  You make regular metal have a maximum width.  If the
    maximum width is exceeded, then the user has to replace the regular metal
    with the wide metal type.  This assumes that the wide metal has a wider
    spacing rule, but if not, you just reverse the set-up (regular metal is
    wide, and the special metal is the narrow metal).
    
    Philippe
    


  •  
     
    Questions? Contact Rajit Manohar
    cornell logo