Stats

Locked Locked
Replies 2
Subscribers 91
Views 15714
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

set_propagated_clock

In one of design's my collegue used set_propagated_clock [all_clocks ] in the preCTS stage . He also applied latency on the memory clock pins .

a. what might be the reason for using set_propagated_clock [all_clocks ] in the prects case

b . If we use set_propagated_clock [all_clocks ] command at the end of SDC file which one take precedance . Can we see latency applied on memory clock pins in the timing report .

Regards

Shiva

Kari over 13 years ago

I think set_propagated_clock is ignored in the preCTS stage. I can't think of a reason to do it anyway.
Cancel
Vote Up 0 Vote Down

Cancel
Andrea Spiezia over 6 years ago in reply to Kari

Hi,

in the Innovus User Guide 18.11 is reported: set_propagated_clock will limit preCTS optimization by not allowing resize on sequential elements.

So it seems that set_propagated_clock has some effects in preCTS, but in the specific page of set_propagated_clock in the same UG, is not mentioned any limitation of this command.

So my question is: is it true that set_propagated_clock not allowing resize in preCTS? If yes, why?

https://support.cadence.com/apex/techpubDocViewerPage?path=innovusTCR/innovusTCR18.11/set_propagated_clock.html
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.