• 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. dbgAutoCellFunction and RC scale factors

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 91
  • Views 14141
  • 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

dbgAutoCellFunction and RC scale factors

archive
archive over 16 years ago

 Dear All,

I have two questions regarding Encounter v6.2:

1) I read somewhere that before starting to work on a design in Encounter I should do: set dbgAutoCellFunction 1

Does anyone know why is that? What does this function do?

2) Does anyone know where to find or how to calculate the Capacitance/Resistance Scale Factors that are needed for RC extraction? These are filled in the Avanced> RC Extraction tab of Design Import window.

 Thanks in advance,

 Alex

  • Cancel
Parents
  • GangaAtFPS
    GangaAtFPS over 13 years ago

    Hi Kari Thank you,

    I got hold Violations (for Reg2Reg paths) for my block as follows:

    @CTS:: -0.405ns,

    @POST_CTS_OPTIMIZATION: -0.3ns,

    @ROUTE: -0.45ns ,

    @POST_ROUTE_OPT: -0.5ns ,

    After I extracted spef and I correlate spef and detailed spef i derived new scaling factors(0.9 for both res and cap) by using Ostrich tool.With those new scaling factors how can i avoid hold violations for tha block.

    And Where to use those Scaling factors exactly? What tool will do exactly if I run with new scaling factors?Will it take different Ressistance and capacitance values while calculating delays??

    I use them as follows in config file::

    postroute_res=0.9;

    postroute_cap=0.9; 

    My Primary doubt was as iam moving from post_cts_opt to routing stage the hold should be improved right.Then what will be the reason for hold degradation for my block? Is the tool doing RC extraction with very pessimism before routing the design??

    2nd doubt::

    Can the design density crosses more than 100%?? 

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • GangaAtFPS
    GangaAtFPS over 13 years ago

    Hi Kari Thank you,

    I got hold Violations (for Reg2Reg paths) for my block as follows:

    @CTS:: -0.405ns,

    @POST_CTS_OPTIMIZATION: -0.3ns,

    @ROUTE: -0.45ns ,

    @POST_ROUTE_OPT: -0.5ns ,

    After I extracted spef and I correlate spef and detailed spef i derived new scaling factors(0.9 for both res and cap) by using Ostrich tool.With those new scaling factors how can i avoid hold violations for tha block.

    And Where to use those Scaling factors exactly? What tool will do exactly if I run with new scaling factors?Will it take different Ressistance and capacitance values while calculating delays??

    I use them as follows in config file::

    postroute_res=0.9;

    postroute_cap=0.9; 

    My Primary doubt was as iam moving from post_cts_opt to routing stage the hold should be improved right.Then what will be the reason for hold degradation for my block? Is the tool doing RC extraction with very pessimism before routing the design??

    2nd doubt::

    Can the design density crosses more than 100%?? 

     

    • 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