• 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. input for generating SDF

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 92
  • Views 17603
  • 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

input for generating SDF

gops
gops over 16 years ago
What is the input file for generating SDF?In encounter there is a command writesdf.Is SDF calculated based on extracted RC.I mean SPEF file. Please somebody tell me the exact operation running in tool background when i execute writesdf.
  • Cancel
Parents
  • BobD
    BobD over 16 years ago
    write_sdf is most typically run after the design has been timed already which is usually performed with the timeDesign super-command: "timeDesign -postRoute [-si]".  Once the design has been timed, and write_sdf is called the delay calculation in-memory will be used to output the SDF file.  I'm not sure right off whether write_sdf would trigger delay calculation if called on a design that wasn't already timed.  To be safe, I'd recommend calling timeDesign prior to write_sdf.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • BobD
    BobD over 16 years ago
    write_sdf is most typically run after the design has been timed already which is usually performed with the timeDesign super-command: "timeDesign -postRoute [-si]".  Once the design has been timed, and write_sdf is called the delay calculation in-memory will be used to output the SDF file.  I'm not sure right off whether write_sdf would trigger delay calculation if called on a design that wasn't already timed.  To be safe, I'd recommend calling timeDesign prior to write_sdf.
    • 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