• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. lef generation

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 14403
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

lef generation

spach
spach over 16 years ago

can any one explain different ways of generating lef form GDS?

what are all inputs we needed for lef generation using GDS?

and what is the difference between technology lef and technology files used for layout?

regards

suresh

  • Cancel
Parents
  • Kari
    Kari over 16 years ago

     Hi Suresh,

    I don't usually have to create my own LEFs from GDS, but here's what I remember:

    One way is to use DFII/Virtuoso to export LEF from your layout view. If you have all the pins and the boundary layer defined correctly, this should work. You may need to add blocakges, I don't recall.

    Another thing you can do is use an abstract tool. I know there is one in the Cadence toolset - back when I used it, it was called Picasso. It may just be called Abstract now. It involves reading in your GDS and setting everything up for how you want pins and blockages to look, if you want antenna info, etc.

    As for the tech LEF, this is usually a LEF file that just has your layer and via info, along with a few other things like manufacturing grid, etc. It does not contain any macros, but may contain SITE definitions. Sometimes a LEF that does contain the macros/std cells/rams etc. will have the tech info at the top. In that case, you would want to rip it out of each lef and just have one tech lef you read in at the beginning.

    I'm thinking the tech file used for layout that you mention is the DFII tech file (usually .tf). The tech LEF is in LEF format. They contain some of the same information, but the DFII tech file will contain more detail about how the layers appear in the layout, etc.

    Hope this helps - I'm a bit rusty on all of it. Most of my work happens inside Encounter these days!

     - Kari

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Kari
    Kari over 16 years ago

     Hi Suresh,

    I don't usually have to create my own LEFs from GDS, but here's what I remember:

    One way is to use DFII/Virtuoso to export LEF from your layout view. If you have all the pins and the boundary layer defined correctly, this should work. You may need to add blocakges, I don't recall.

    Another thing you can do is use an abstract tool. I know there is one in the Cadence toolset - back when I used it, it was called Picasso. It may just be called Abstract now. It involves reading in your GDS and setting everything up for how you want pins and blockages to look, if you want antenna info, etc.

    As for the tech LEF, this is usually a LEF file that just has your layer and via info, along with a few other things like manufacturing grid, etc. It does not contain any macros, but may contain SITE definitions. Sometimes a LEF that does contain the macros/std cells/rams etc. will have the tech info at the top. In that case, you would want to rip it out of each lef and just have one tech lef you read in at the beginning.

    I'm thinking the tech file used for layout that you mention is the DFII tech file (usually .tf). The tech LEF is in LEF format. They contain some of the same information, but the DFII tech file will contain more detail about how the layers appear in the layout, etc.

    Hope this helps - I'm a bit rusty on all of it. Most of my work happens inside Encounter these days!

     - Kari

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information