We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 67225

UltraScale/UltraScale+ Memory IP - CLOCK_DEDICATED_ROUTE BACKBONE constraint not automatically generated by IP


Version Found: DDR4 v2.0 (Rev. 1). DDR3 v1.2 (Rev. 1), RLDRAM3 v1.2 (Rev. 1), QDRII+ v1.2 (Rev. 1), QDRIV v1.1 (Rev. 1)

Version Resolved: See (Xilinx Answer 58435)

(PG150) states that the Memory IP will automatically generated the CLOCK_DEDICATED_ROUTE BACKBONE constraint if the "No Buffer" option is not used. Why do I not see the constraint added?


This is a known issue that can be resolved by manually adding the CLOCK_DEDICATED_ROUTE BACKBONE constraint using the following syntax:

set_property CLOCK_DEDICATED_ROUTE BACKBONE [get_pins -hier -filter {NAME =~ */u_ddr3_infrastructure/gen_mmcme3.u_mmcme_adv_inst/CLKIN1}]

Note: When using the "No Buffer" option the CLOCK_DEDICATED_ROUTE BACKBONE constraint must always be applied manually. Refer to (PG150) for more details.


Revision History:

05/13/2016 - Initial Release

Linked Answer Records

Master Answer Records

Answer Number Answer Title Version Found Version Resolved
58435 UltraScale/UltraScale+ Memory IP - Master Release Notes and Known Issues N/A N/A
AR# 67225
Date 12/20/2017
Status Active
Type Known Issues
  • Kintex UltraScale
  • Virtex UltraScale
  • Kintex UltraScale+
  • More
  • Virtex UltraScale+
  • Zynq UltraScale+ MPSoC
  • Less
  • Vivado Design Suite - 2016.1
  • MIG UltraScale
Page Bookmarked