• 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. Propagated clock for reg2out

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 92
  • Views 18115
  • 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

Propagated clock for reg2out

Aram Shahinyan
Aram Shahinyan over 12 years ago

Dear Friends,

I'm looking into Solution with ID 11327942. Can't figure out how clock latency 2.5ns is decided for reg2out paths

set_clock_latency 2.5 -rise clk2

 Can you please give me a hint?

 Thanks,

Aram

  • Cancel
Parents
  • fitz
    fitz over 12 years ago

    See my first response....................

    We always referenced ip / op delays relative to a "virtual" clock.
    This virtual clock must track the real clock before and after CTS.
    You can automatically update the virtual clock after CTS with the command update_io_latency.

    We have been doing it this way for so long I forgot  the reason why, but there must be a valid reason to put me through decades of pain .
    If you are doing anything different, like setting the output delay relative to the "actual" clock, sorry you are on your own.


    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sasikg59
    sasikg59 over 7 years ago in reply to fitz

    Hello

    I am facing a problem while using the command update_io_latency

    after i run the command. I used timeDesign to save the reports. But io_latency is not saved in the report folder. Is there anything that I could check to make sure io_latency is updated.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • sasikg59
    sasikg59 over 7 years ago in reply to fitz

    Hello

    I am facing a problem while using the command update_io_latency

    after i run the command. I used timeDesign to save the reports. But io_latency is not saved in the report folder. Is there anything that I could check to make sure io_latency is updated.

    • 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