set_input/output_delay 0 constraints?

141 views
Skip to first unread message

Adrian Holmes

unread,
May 18, 2021, 11:46:12 AM5/18/21
to corundum-nic
Just wondering what the significance of the constraints where an input or output delay of 0 is defined? For example:

set_false_path -to [get_ports {pps_out pps_out_en}]
set_output_delay 0.000 [get_ports {pps_out pps_out_en}]
set_false_path -from [get_ports pps_in]
set_input_delay 0.000 [get_ports pps_in]

I can't work out  what the set_input/output_delay of 0 is achieving.
Can anyone help?

Alex Forencich

unread,
May 18, 2021, 3:30:53 PM5/18/21
to corund...@googlegroups.com

This is merely to satiate Vivado.  Apparently adding only false path constraints on all of the non-critical inputs and outputs still results in warnings that the input/output delays are not specified.  So, you need a combination of both false path and input/output delay constraints to suppress all of the warnings.  Due to the false path constraints, the actual value of the input/output delay constraints is irrelevant.  If you know of a better way to do this, then I can certainly go update all of the constraints files again. 

Alex Forencich
--
You received this message because you are subscribed to the Google Groups "corundum-nic" group.
To unsubscribe from this group and stop receiving emails from it, send an email to corundum-nic...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/corundum-nic/df343c1a-671b-474e-b9be-414b61865e98n%40googlegroups.com.

Adrian Holmes

unread,
May 19, 2021, 3:27:37 AM5/19/21
to corundum-nic
Hi Alex,

Yes that makes sense, thanks for clarifying. It had been bugging me for a while!
I'm a fan of removing as many warnings as possible. Gives you a chance of spotting the ones that matter!
Reply all
Reply to author
Forward
0 new messages