10-13-2017 01:06 AM
The error is disappeared after i add an new */*/ hierarchy path before the MIG xdc constrain line . how to let MIG add the hierarch path automatic? The mig ip is instantied under top level.
set_max_delay 5.0 -datapath_only -from [get_pins */*/*/u_ddr_cal_addr_decode/io_ready_lvl_reg/C] -to [get_pins */u_io_ready_lvl_sync/SYNC[*].sync_reg_reg/D]
set_max_delay 5.0 -datapath_only -from [get_pins */*/*/*/*/u_ddr_cal_addr_decode/io_ready_lvl_reg/C] -to [get_pins */*/*/u_io_ready_lvl_sync/SYNC[*].sync_reg_reg/D]
10-13-2017 01:12 AM - edited 10-13-2017 01:12 AM
If you add IP XCI to the project then the constraints should be read by the tool correctly.
Can you share the IP XCI?
10-13-2017 01:46 AM
I have read your recent thread : https://forums.xilinx.com/t5/Implementation/CRITICAL-WARNING-Project-1-840/td-p/800344
Are you sure that you are using xci or xcix for the IPs?
10-13-2017 02:30 AM
When you use IP DCP and XDC files, the constraints will not be evaluated properly. This is the reason we recommend using IP XCI file instead.
10-20-2017 12:05 PM
The correct flow for reading in an IP DCP (for non-project mode) is to use: read_ip ip_name.xci. If a DCP/generated RTL exist, then it will they will be pulled in as well. Top level constraints can only be applied properly to an IP through an XCI file. read_checkpoint should only be used with top level DCP's and not standalone IP DCP's.
For more information on this flow, please look into https://www.xilinx.com/support/answers/69690.html