• 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. Custom IC Design
  3. Writing out .lib & lef from virtuoso

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 5472
  • 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

Writing out .lib & lef from virtuoso

Shameel
Shameel over 11 years ago

 Hi All

How can I write out .lib file of a digital module designed in virtuoso ?

Also If I want to import this module as a digital block to encounter, how can I make it as a macro/cell ? How to take care of this while

writing out lef from virtuoso ?

 

Thanks

Shameel

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    LEF can be written with File->Export->LEF. .lib could be generated with the Liberate family of tools - there's not really a direct way of writing .LIB from Virtuoso because it generally needs characterization. There is the Tools->Characterization and Modelling->Black Box Liberty (MS) menu - not sureif that's really what you want either.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Shameel
    Shameel over 11 years ago

    Hello Andrew,

    Thanks for the help..

    The issue with lef is that  once I export  lef from virtuoso and read this to encounter,its not recognised by encounter as a macro.

    Can we use the lef generated by  File->Export->LEF in virtuoso directly to encounter ? Or anything else need to be done for generating abstract  views so as to deal with the module as a macro in encounter?

     

    Thanks

    Shameel

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Alex Soyer
    Alex Soyer over 11 years ago

    Hi Shameel,

     If you have already generated your abstract then you could use (Shift+Q) Edit Master Properties and set the 'cellType' to 'block'.

    Otherwise you can do the setting using abstract generator when creating teh abstract by moving the cell to the 'macro' 'bin'.

    Another solution in case you have to do it for multiple cellviews is to use teh CIW -> Tools -> Set cellType.

     Thanks,

    Alex

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Shameel
    Shameel over 11 years ago

    Hi Alex,

    I have made the option " CIW -> Tools -> Set cellType>   *   " Still encounter does n't recognize it as MACRO

    If I change CLASS to PAD instead of CORE or BLOCK ,encounter is recognizing it as IO pad with pins and exactly how I need it; except that it is IO .

    But its not supporting CORE,BLOCK

    Is there any attribute in lef that does n't support for CORE but IO ? 

    Thanks

    Shameel

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Alex Soyer
    Alex Soyer over 11 years ago

    Hi Shameel,

    For CORE you need additional information like the sitePattern (which is the legal row site pattern in which you can place it) and SYMMETRY set to XY (allowed orientation)

    For BLOCK I think the missing information is the SYMMETRY which is mots of the time ANY.

    In order to set the information you need to open the cellview and do Shift+Q and then complete the Edit Cellview Properties form as mentioned above.

     Thanks,
    Alex

    • 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