Stats

  • Locked Locked
  • Replies 12
  • Subscribers 90
  • Views 19365
  • 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

How to report latency at a sink pin in encounter

archive

I want to know how to report latency of a sink pin in encounter.
Suppose I have a pin "a/b/c/d/CK" .How to report the latency.

I tried the following command.
get_property [get_pins a/b/c/d/CK] arrival_rise_max..But the value it reports is quite different from the value I see at the same pin after timedesign and report_timing.Is there a more reliable command.
Most of the switches in get_property are not working like latency_max_rise etc..


Originally posted in cdnusers.org by abhiroy03
Parents

  • Hi Sanjay,

    I'm not sure what you mean by "how do you declare a pin to be a sync pin". I'm not sure if you're asking this from a clock tree synthesis (CTS) perspective -or- from a static timing analysis (STA) perspective. Could you clarify? If you could provide the syntax you use in Synopsys we could probably map it to an equivalent notion in Encounter.

    For setting a clock latency on a pin, we'd use the same convention as the Synopsys tools: "set_clock_latency":
    Usage: set_clock_latency [-source [-early | -late]]
    [-rise | -fall] [-min | -max]


    Thanks,
    Bob


    Originally posted in cdnusers.org by BobD
Reply

  • Hi Sanjay,

    I'm not sure what you mean by "how do you declare a pin to be a sync pin". I'm not sure if you're asking this from a clock tree synthesis (CTS) perspective -or- from a static timing analysis (STA) perspective. Could you clarify? If you could provide the syntax you use in Synopsys we could probably map it to an equivalent notion in Encounter.

    For setting a clock latency on a pin, we'd use the same convention as the Synopsys tools: "set_clock_latency":
    Usage: set_clock_latency [-source [-early | -late]]
    [-rise | -fall] [-min | -max]


    Thanks,
    Bob


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