• 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. Operating Conditions during predict_qos and synthesize ...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 91
  • Views 798
  • 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

Operating Conditions during predict_qos and synthesize -to_placed process.

admin
admin over 16 years ago

Hi there,

How can I change the operating conditions to ensure that RC extraction agrees with my synthesis settings?

Is the RTL Compiler physical synthesis enough, or the best practice is to run trial place and route on the Encounter?

At least in Encounter I have more control over the RC extraction process.

Thanks

  • Cancel
Parents
  • grasshopper
    grasshopper over 16 years ago

    Hi Julian,

     not sure I follow your question but operating conditions used in RTL Compiler are honored during R/C extraction so both should line up when using RTL Compiler Physical. In addition operating conitions changes using something like

    set_attr temperature 43.2 [find / -operating_condition nominal] 

     will also be taken into account during R/C extraction

     hope this helps,

    gh-

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

    Hi Julian,

     not sure I follow your question but operating conditions used in RTL Compiler are honored during R/C extraction so both should line up when using RTL Compiler Physical. In addition operating conitions changes using something like

    set_attr temperature 43.2 [find / -operating_condition nominal] 

     will also be taken into account during R/C extraction

     hope this helps,

    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