Honored Contributor
Honored ContributorThank you for your response Rysc.
You mentioned that people would place a "set_input/output_delay " constraint on it. I didn´t realise it was possible to use this constraint without using a clock. Can you just verify that for me? Also just one final thing I was curious about: I have some combinational logic carrying out a certain function which need to complete in 45ns once a signal is asserted. Quartus has no issue in meeting this time, but it does show up in the UCP, so I had a go at constraining it. I placed the following constraints (which it meets comfortably): set_max_delay = 20ns set_min_delay = 0ns My question is, is there any need to place the min constraint? Obviously Quartus can´t do it in 0ns, but it may do it in 8ns without any problems, so I didn´t want to put a min constraint in which would be above a value which Quartus could meet comfortably. Is just specifying the max delay sufficient in this case? What does Quartus do in this case, settle on any value less than 20ns for all corners or would it attempt to the delay close to 20ns? (I seem to remember reading something about classic timing analyzer when I used to use it where only specifying a max constraint would imply a min constraint of the same value, does timequest work in the same way?) Many thanks for the help
