Stats

  • Locked Locked
  • Replies 1
  • Subscribers 61
  • Views 13010
  • 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

No Hold Time Constrains Read In

archive

    Hi,

I have a sdc file in which defined the ports hold time and setup time like :
set_output_delay -clock [get_clocks {clk}]  -min 5 -add_delay [get_ports {mem_d}]  //for hold time
set_output_delay -clock [get_clocks {clk}]  -max .3 [get_ports {mem_d}]                  //for setup time

but when i run the nano encounter, I get the message:
No Hold Time Constrains Read In.
As It appear the encounter read setup time and do setup fix, but it doesn't read the hold constrain.
I also tried to change the -min value but I got similar results for hold WNS(which shows the tool didn't respect the hold time)

Can anyone help on this.

Thanks,

Houman



Originally posted in cdnusers.org by houmanh

  • I didn't get a chance to test but you either need to change the order of the constraints or need to remove the -add_delay as the constraint are not for the same timing type. The -add_delay is typically for associating a timing with a second clock.


    Originally posted in cdnusers.org by evenditti

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.