Stats

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

  • I do postCTS timing analysis
    and I get this issue too.  there is no error or warnings, But the rerurned value seems quiet odds. 

    I am wondering it a bug or feature?



    Posted By BobD on 2/06/2008 12:31 PM
    latency_max_rise *should* be reporting the value you're looking for. It sounds like a bug to me.

    Are you trying to get the latency preCTS or postCTS? If preCTS, is the latency on the CK pin you're querying asserted on the pin itself? Somewhere upstream from the pin? Or on the clock that is connected to the pin?

    Thanks,
    Bob



    Originally posted in cdnusers.org by aidans
Reply

  • I do postCTS timing analysis
    and I get this issue too.  there is no error or warnings, But the rerurned value seems quiet odds. 

    I am wondering it a bug or feature?



    Posted By BobD on 2/06/2008 12:31 PM
    latency_max_rise *should* be reporting the value you're looking for. It sounds like a bug to me.

    Are you trying to get the latency preCTS or postCTS? If preCTS, is the latency on the CK pin you're querying asserted on the pin itself? Somewhere upstream from the pin? Or on the clock that is connected to the pin?

    Thanks,
    Bob



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