• 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. BUffer Profiling

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 90
  • Views 15555
  • 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

BUffer Profiling

archive
archive over 18 years ago

Is there a way to get the buffer classiifcation in encounter i.e a way to report the number of CTS buffers, hold buffers etc .


Originally posted in cdnusers.org by mvvijay78
  • Cancel
  • archive
    archive over 18 years ago

    In the Encounter User Guide doc, you can find the naming convention used by Encounter during implementation to added cells and nets.
    In Optimizing Timing -> Naming Conventions

    Typically you can find that buffer added for fix Hold will be prefix with "FE_PHC".

    You can use this prefix analysis to sort all your buffers.


    Originally posted in cdnusers.org by bougantp
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Really learn a lot of things from you, bougantp!! Solute!!


    Originally posted in cdnusers.org by eminemshow
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Hi please make a note to get number of CTS buffers :

    easy way : in "Clock Tree Timing Report" you will get Nr. of Buffer : ** " value directly but need to take from all CTS root point.

    alternative way for design : grep "__L" in def file .

    Note :
    NameDelimiter

    if you change in any case by
    NameDelimiter # creates names with the format clk##L3#I2, rather than the default format, clk__L3_I2.

    UseSingleDelim YES
    (creates clock and net names with the format clk_L3_I2, rather than the default format, clk__L3_I2)

    Naming Conventions
    Instance Description Command
    FE_ABC Instance name added by multi-driver netbuffering.optDesign
    FE_ABN Net name added by multi-driver net buffering. optDesign
    FE_OCPN Net name added by critical path optimization. optDesign
    FE_OCPC Instance name added by critical path optimization.optDesign
    FE_FHN Net name added by hold time repair optDesign
    FE_FHC Instance name added by hold time repair. optDesign
    FE_RC Instance created by netlist restructuring. optDesign
    FE_RN Net created by netlist restructuring. optDesign
    FE_OFN Buffer net name added by rule-based buffer insertion insertRepeater/optFanout
    FE_OFC Buffer instance name added by rule-basedbuffer insertion insertRepeater/optFanout
    FE_PHC Cell name added by post-route hold repair. optDesign
    FE_PHN Net name added by post-route hold repair. optDesign
    FE_PSC Cell name added by post-route setup repair. optDesign
    FE_PSN Net name added by post-route setup repair. optDesign
    FE_ECON A net added by interactive ECO
    FE_ECOC An instance added by interactive ECO


    Regards,
    Mohan


    Originally posted in cdnusers.org by mohanch007
    • 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