• 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. rc extraction in encounter

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 92
  • Views 13377
  • 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

rc extraction in encounter

berbagci
berbagci over 12 years ago

Hi,

 I'm using encounter for a tape-out. I want to use QRC for higher accuracy. However, I think I need to tell the tool where the executable for QRC is. How do I do that? Modifying PATH variable didn't help. Is there a command to do that?

In addition, I know for static timing analysis, coupling capacitances are not extracted seperately with setExtractRCMode -coupled false command. However, when I do timeDesign with -si option, I see some negative slack. Since the block I'm working on is a timing critical one, I need to make sure timing is accurate. You think I should take signal integrity into account for timing analysis and optimization?

Thanks!

  

  • Cancel
Parents
  • ajay01
    ajay01 over 11 years ago

     below command helpful at optimization step:

    setExtractRCMode -engine postRoute

     setExtractRCMode -effortLevalmedium

    setDelayCalMode -engine aae -considerMillerEffect true -ignorNetLoad false..

    check and update

    Thanks,

    Ajay

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • ajay01
    ajay01 over 11 years ago

     below command helpful at optimization step:

    setExtractRCMode -engine postRoute

     setExtractRCMode -effortLevalmedium

    setDelayCalMode -engine aae -considerMillerEffect true -ignorNetLoad false..

    check and update

    Thanks,

    Ajay

    • 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