• 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. reading synthesized design

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 61
  • Views 14065
  • 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

reading synthesized design

archive
archive over 18 years ago

Is it possible to read in a synthesized design in rtlcompiler for reporting purposes? I know that in synopsys there is a possibility to read in the .db file and thus not having to re synthesize an old design for reporting purposes. My synthesis takes several hours and one little ctrl z by mistake can end the whole session which can be really frustrating...

/Mike


Originally posted in cdnusers.org by mike.c
  • Cancel
Parents
  • archive
    archive over 18 years ago

    I never managed to read in the .sdc file properly, instead I use my .tcl constraint files and then It works to some extend. When comparing my old report files with the new ones most of the paths are the same but some differ, is this correct or should the report files come out identical?

    /Mike


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

    I never managed to read in the .sdc file properly, instead I use my .tcl constraint files and then It works to some extend. When comparing my old report files with the new ones most of the paths are the same but some differ, is this correct or should the report files come out identical?

    /Mike


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