• 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. Logic Design
  3. LEF in synthesis flow

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 62
  • Views 19220
  • 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 in synthesis flow

diablo
diablo over 14 years ago

Hi,

In RTL compiler synthesis flow, i have

set_attribute interconnect_mode ple /

And, i have inlcuded the cap table as well

set_attribute cap_table_file {$CAP_TABLE/bst.cap } 

Do i need to include the LEF library for std cells and io cells as well for correct interconnect delay estimation even after including cap table?

It seems including LEF file gives significant difference in total number of cells and area after synthesis as reported from RTL compiler. Below is the snippet of area report for two flow, 

one excluding LEF

 Cells       Cell Area       Net Area

 23283       715947       391632

and the other including LEF file 

Cells       Cell Area       Net Area

 22664       967042       246572

 Which one is correct flow? Or, which one is the better flow?

Thanks for your suggestions and your time.

Regards. 

  • Cancel
Parents
  • grasshopper
    grasshopper over 14 years ago

     Hi diablo,

     likely case is you are missing some LEF models for your memories. By default RC will zero macros that do not have corresponding LEF info. Indeed you always need your LEF models for cells, process, etc. The reason is the capTbl does not include any of that information. capTbl strictly has process information so it is more detailed in that respect but still missing plenty of information. As per recommended flow, you should certainly read in all LEFs as well as the capTbl. Setting the mode to PLE is not required since reading any LEF or capTbl will make RC default to PLE which is indeed the recommended mode. Here are some articles from http://support.cadence.com that may be of interest to you

     


    87%
    How is cell area picked in RC-PLE flow?
    Version:

     
    Chapter:

    During optimization with PLE mode does RC use the lib area or lef area? Also is there a way to force RC to use the LEF area? Using the LEF area is supported in 7.1 and is default in this version.
    Show Attributes
    Product(s)
    RTL Compiler
    Modified Date
    10-27-2009
    URL
    /wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11407106;searchHash=5a1316ab29765420388e613e58266132

    10-27-2009
    84%
    RC PLE: Cell area for macros is shown as zero. Why?
    Version:

     
    Chapter:

    Shouldn't the area be taken from .lib in absence of LEF information? As per the current behavior, if physical information or LEF for some macros are missing then their area will be shown as 0. The area of 0 is expected when LEF for the corresponding macros have not been read in.
    Show Attributes
    Product(s)
    RTL Compiler
    Modified Date
    10-01-2008
    URL
    /wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11476556;searchHash=5a1316ab29765420388e613e58266132

    10-01-2008
    73%
    What can go wrong if the cell areas in Liberty library are different from LEF?
    Version:

     
    Chapter:

    Problem: What can go wrong if the cell areas in Liberty library are different from LEF? Solution: RC uses the area numbers from the LEF files when the LEF files have been read in.
    Show Attributes
    Product(s)
    RTL Compiler
    Modified Date
    07-07-2010
    URL
    /wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11650922;searchHash=5a1316ab29765420388e613e58266132

    07-07-2010
    70%
    Does RC use cell areas from LEF or from Liberty in PLE mode?
    Version:

     
    Chapter:

    Problem: Does RC use cell areas from LEF or from Liberty in PLE mode? Solution: The cell dimensions defined in the LEF will be used if the LEFs have been imported and the tool is in PLE mode.
    Show Attributes
    Product(s)
    RTL Compiler
    Modified Date
    02-02-2009
    URL
    /wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11366954;searchHash=5a1316ab29765420388e613e58266132

    02-02-2009

     

    regards,

    gh-

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • grasshopper
    grasshopper over 14 years ago

     Hi diablo,

     likely case is you are missing some LEF models for your memories. By default RC will zero macros that do not have corresponding LEF info. Indeed you always need your LEF models for cells, process, etc. The reason is the capTbl does not include any of that information. capTbl strictly has process information so it is more detailed in that respect but still missing plenty of information. As per recommended flow, you should certainly read in all LEFs as well as the capTbl. Setting the mode to PLE is not required since reading any LEF or capTbl will make RC default to PLE which is indeed the recommended mode. Here are some articles from http://support.cadence.com that may be of interest to you

     


    87%
    How is cell area picked in RC-PLE flow?
    Version:

     
    Chapter:

    During optimization with PLE mode does RC use the lib area or lef area? Also is there a way to force RC to use the LEF area? Using the LEF area is supported in 7.1 and is default in this version.
    Show Attributes
    Product(s)
    RTL Compiler
    Modified Date
    10-27-2009
    URL
    /wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11407106;searchHash=5a1316ab29765420388e613e58266132

    10-27-2009
    84%
    RC PLE: Cell area for macros is shown as zero. Why?
    Version:

     
    Chapter:

    Shouldn't the area be taken from .lib in absence of LEF information? As per the current behavior, if physical information or LEF for some macros are missing then their area will be shown as 0. The area of 0 is expected when LEF for the corresponding macros have not been read in.
    Show Attributes
    Product(s)
    RTL Compiler
    Modified Date
    10-01-2008
    URL
    /wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11476556;searchHash=5a1316ab29765420388e613e58266132

    10-01-2008
    73%
    What can go wrong if the cell areas in Liberty library are different from LEF?
    Version:

     
    Chapter:

    Problem: What can go wrong if the cell areas in Liberty library are different from LEF? Solution: RC uses the area numbers from the LEF files when the LEF files have been read in.
    Show Attributes
    Product(s)
    RTL Compiler
    Modified Date
    07-07-2010
    URL
    /wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11650922;searchHash=5a1316ab29765420388e613e58266132

    07-07-2010
    70%
    Does RC use cell areas from LEF or from Liberty in PLE mode?
    Version:

     
    Chapter:

    Problem: Does RC use cell areas from LEF or from Liberty in PLE mode? Solution: The cell dimensions defined in the LEF will be used if the LEFs have been imported and the tool is in PLE mode.
    Show Attributes
    Product(s)
    RTL Compiler
    Modified Date
    02-02-2009
    URL
    /wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11366954;searchHash=5a1316ab29765420388e613e58266132

    02-02-2009

     

    regards,

    gh-

    • 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