• 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 unit confusion

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 93
  • Views 20492
  • 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 unit confusion

Holdsworth
Holdsworth over 15 years ago
Hello there, I'm a bit confused with LEF unit: I've a LEF file with DATABASE MICRONS 2000 ; However, the LEF/DEF language reference interprets one LEF distance unit as multiplied when converted into database units. In other words, if for a LAYER M1 WIDTH 0.10 ; , does this mean that the actual width of M1 is (0.1*2000)um ?
  • Cancel
  • Kari
    Kari over 15 years ago

     No, the M1 width is 0.10 microns. The numbers in the LEF are always in microns, but the tech LEF also happens to be where you specify what the DB Units are for the design. The numbers in the DEF file are in DB Units. The statement DATABASE MICRONS 2000 means that for any numbers in the DEF file, to convert to microns, you divide by 2000. (A long time ago, the tool GUIs would display things in DB Units also, but I believe everything is displayed in microns now.)

    Sometimes the LEF will have DATABASE MICRONS 1000, or some other number. It depends on the technology and what the manufacturing grid is.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mdconcepts
    mdconcepts over 14 years ago

    Do you know how to set the LEF UNITS DATABASE MICRONS?  The digital vendor is asking for 2000, but the default in the technology file is creating MICRON UNITS as 100.  I am exporting a flat abstract viewcell with only ports and metal blocking layers using the File, Export, LEF.

     

    Thanks,

          MD

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 14 years ago

     You can just edit the LEF manually to change the DATABASE MICRONS line to whatever you want. 

    If you want this to happen automatically when you export LEF, then I *think* it's a setting in the DFII tech file, but it's been a long time since I played in that arena. ;-)

    - Kari

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mdconcepts
    mdconcepts over 14 years ago

    Thanks for the reply.  I was guessing as much as I noticed that the coordinates seem to be correct and since you will be importing in, the units will adjust accordingly to whatever is in the LEF file.  I searched around in the techfile, but didn't see the specific unit under the CONTROLS portion or the P&R portion.

     

    Thanks,

     

         MD

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Ramil
    Ramil over 10 years ago
    Hello Kari. What would be the effect when my PNR tech lef has DATABASE MICRONS set to 2000 and the technology file in my virtuoso is set to 1000? Would it introduced possible DRC errors when the PNR def file is imported to virtuoso?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 10 years ago
    It's been a long time since I've worked in Virtuoso, but I think this will be ok. Run DRC and if you see lots of really strange errors, that that could be the culprit.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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