Honored Contributor
Honored ContributorThanks for your reply Rysc. Both devices are definitely single data rate. As you recommended I ran TimeQuest again with zero max and min input/output delays:
set_input_delay -clock tvp_dataclk -max 0 [get_ports {tvp_yout*}] -add_delay set_input_delay -clock tvp_dataclk -min 0 [get_ports {tvp_yout*}] -add_delay set_output_delay -clock adv_clk -max 0 [get_ports {adv7171_d*}] -add_delay set_output_delay -clock adv_clk -min 0 [get_ports {adv7171_d*}] -add_delay This made absolutely no difference to the slack values in the setup and hold summary reports, for both sets of constraints the results were: Summary (Setup) adv_clk slack=-10.730 End Point TNS=-2884.669 tvp_dataclk slack=-6.053 End Point TNS=-144.271 Summary (Hold) adv_clk slack=-1.859 End Point TNS=-139.715 tvp_dataclk slack=-1.859 End Point TNS=-135.955 I don't understand this result. Surely the slack values are determined by the actual timing and the constraints applied. If I don't change the design, but I do change the constraints, I would expect the setup and hold slacks to change. Is that thinking flawed?
