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# 6130

14.x Constraints Editor - The Constraints Editor cannot locate clock signals in a global tab


The Constraints Editor is not locating all clock signals in my design. Generally, the Constraints Editor finds clock nets and traces them back to their source. At the source, they are named and made available for period constraints. Net names along the path of that clock are displayed with the source signal name.

Specifically, derived clocks do not appear; a clock signal that is derived from multiple clock signals through a MUX or other such function does not appear. Even if a BUFG is applied to that signal, it is not visible.


Using the UCF file, you can name any clock net, and you can add a period constraint (this is limited to the Constraints Editor, not to the constraint itself). You can manually add a clock signal that is not available in the Constraints Editor to the UCF file and apply the constraint.

For details on adding period constraints, refer to the software manuals at:

AR# 6130
Date Created 08/21/2007
Last Updated 12/19/2012
Status Active
Type Known Issues
  • ISE Design Suite - 11
  • ISE Design Suite - 12
  • ISE Design Suite - 13
  • ISE Design Suite - 14