Warnings and Critical Warnings that objects in XDC constraints are not found are occasionally seen in Synthesis but not in Implementation.
Below are some examples:
WARNING: [Synth 8-3321] Empty from list for constraint at line 57 of xxxx.xdc.
CRITICAL WARNING: [Synth 8-3321] create_clock attempting to set clock on an unknown port/pin for constraint at line 41 of xxxx.xdc
WARNING: [Vivado 12-1387] No valid object(s) found for set_false_path constraint with option '-from [get_pins -hier -filter {NAME =~/RAM*/CLK}]'. ["xxxx.xdc":4]
WARNING: [Vivado 12-180] No cells matched ' <cell_name> '. ["xxxx.xdc":5]
WARNING: [Vivado 12-584] No ports matched ' <port_name> '. ["xxxx.xdc":36]
WARNING: [Vivado 12-508] No pins matched ' <pin_name> '. ["xxxx.xdc":35]
WARNING: [Vivado 12-507] No nets matched ' <net_name> '. ["xxxx.xdc":23]
WARNING: [Vivado 12-627] No clocks matched ' <clock_name> '. ["xxxx.xdc":24]
Why are these messages only seen in Synthesis?
Can these be safely ignored?
Below are some possible reasons why Synthesis will give an error that a constraint object (cell/net/pin) is not found but Implementation will not.
If the constraint is not important to Synthesis, the message can be safely ignored as the constraint works well post-Synthesis.
However, if you want to remove these messages, you can use the following solutions.
AR# 54799 | |
---|---|
日期 | 04/18/2016 |
状态 | Active |
Type | 综合文章 |
Tools |