• 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. Path _Delay Command

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 63
  • Views 958
  • 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

Path _Delay Command

Kliatakis
Kliatakis over 16 years ago

Hello!

I am a new user of RTL Compiler and i am trying to synthesize a combinational circuit(with inputs A,B and an output named Output) in order to get later a layout from SoC Encounter and i want to constraint its delay. I saw in RTL compiler's manual the command

path_delay -delay integer
     { {-from {instance |external_delay |clock |port |pin }...
       |-through {instance |port |pin }...[-through...]...
       |-to {instance |external_delay |clock |port |pin }...}...
       |-paths string }
     [-lenient] [-mode mode_name ] [-name string ]

 in RC i put the command like this:  path_delay -from {A} -to {Output} -delay 4000 but this does not seem to be correct.I would appreciate any help!Thanks in advance!

  • Cancel
  • johannes
    johannes over 16 years ago

    Hi!

    In general, this is correct, as long as an input port "A" and an output port "Output" exist in your design. What error do you get?

    Nevertheless, I would recommend to use the following style:
    path_delay -from [find /designs -port A] -to [find /designs -port Output] -delay 4000

    Regards,
    Johannes

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kliatakis
    Kliatakis over 16 years ago
    I managed to get it to work properly!but thanks !
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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