• 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. long wire transition time issues

Stats

  • Locked Locked
  • Replies 14
  • Subscribers 90
  • Views 18328
  • 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

long wire transition time issues

archive
archive over 17 years ago

In my current design,some wires are quite long,look like over 3000ums,diriven by a buffer,fe does not report the net has transition violation.it should be a problem for the wires are so long.these pins/path are not constrained,could encounter fix this kind thing?if so,what should i do?


Originally posted in cdnusers.org by yhu
  • Cancel
Parents
  • archive
    archive over 17 years ago

    You may face such problem if there is no timing path through this net.
    No timing path can come from a false_path, disable_timing_arc or constant propagation from SDC or tie connection coming from the netlist.
    The transition is calculate by the timer, and the consequence is that is there is no path, there is no transition, so no fix on your long wire.
    The trick you can use is to defined a default SDC, where you only put the set_load, set_input_transition ... constrains.
    Load only this new SDC and run optDesign -drv.
    Now the tools should be able to catsh your long net....

    Pat.


    Originally posted in cdnusers.org by bougantp
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 17 years ago

    You may face such problem if there is no timing path through this net.
    No timing path can come from a false_path, disable_timing_arc or constant propagation from SDC or tie connection coming from the netlist.
    The transition is calculate by the timer, and the consequence is that is there is no path, there is no transition, so no fix on your long wire.
    The trick you can use is to defined a default SDC, where you only put the set_load, set_input_transition ... constrains.
    Load only this new SDC and run optDesign -drv.
    Now the tools should be able to catsh your long net....

    Pat.


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