Stats

  • Locked Locked
  • Replies 2
  • Subscribers 92
  • Views 13223
  • 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

Cause of long timing delays in Encounter Timing

jkang

I have a timing path (several actually) that seem to be unusually long. I've tracked it to one AO22 cell that has a huge timing arc (~40ns) from its A1 -> Z. I want to know what's causing this; how is the tool calculating the delay?

I've been messing around with get_property, report_property and a few other DB commands but I am kinda groping in the dark here. Is there a way to tell how the delay is being calculated? Specifically, calculated input transition times, dot-lib look-up table and the calculations for output delay.

Parents

  •  You may also want to report net delays and cell delays separately; report_timing -net will do this. It could be you have a long route on this pin which is really causing the delay. Also, using the Global Timing Debug in Encounter can help you find the cause.

Reply

  •  You may also want to report net delays and cell delays separately; report_timing -net will do this. It could be you have a long route on this pin which is really causing the delay. Also, using the Global Timing Debug in Encounter can help you find the cause.

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.