When using the XAUI v11.0 core with the following Variants:
- 10G or 20G rate for Artix-7 devices
- 10G rate for Virtex-7 devices using GTH Transceivers
Critical Warnings such as the one below are seen:
[Vivado 12-180] No cells matched 'get_cells -hierarchical -filter {NAME =~ */gt_wrapper_i/gt0_core_gt_wrapper_i/gtrxreset_seq_i/DRP_OP_DONE_reg}'. ["/example_project/core_xaui_example/core
e_example.srcs/sources_1/ip/core_name/synth/core_name.xdc":17]
To properly constraint these paths, the word "core" in the path should be replaced with the component name that the XAUI core was generated with in /sources_1/ip/core_name/synth/core_name.xdc. This file is read only, but can be edited outside of the Vivado GUI. In the following constraints "core" should be replaced with the name of the core as shown below:
set_false_path -to [get_cells -hierarchical -filter {NAME =~ */gt0_core_name_gt_wrapper_i/gtrxreset_seq_i/gtrxreset_s_reg}]
set_false_path -to [get_cells -hierarchical -filter {NAME =~ */gt_wrapper_i/gt0_core_name_gt_wrapper_i/gtrxreset_seq_i/DRP_OP_DONE_reg}]
set_false_path -to [get_cells -hierarchical -filter {NAME =~ */gt_wrapper_i/gt1_core_name_gt_wrapper_i/gtrxreset_seq_i/DRP_OP_DONE_reg}]
set_false_path -to [get_cells -hierarchical -filter {NAME =~ */gt_wrapper_i/gt2_core_name_gt_wrapper_i/gtrxreset_seq_i/DRP_OP_DONE_reg}]
set_false_path -to [get_cells -hierarchical -filter {NAME =~ */gt_wrapper_i/gt3_core_name_gt_wrapper_i/gtrxreset_seq_i/DRP_OP_DONE_reg}]
These constraints could also be added to the design top level to constrain the path, although the critical warning will still be reported if the core specific xdc is not edited.
| Answer Number | Answer Title | Version Found | Version Resolved |
|---|---|---|---|
| 54666 | IP Release Notes and Known Issues for LogiCORE XAUI for Vivado 2013.1 and Forward | N/A | N/A |