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

14.x Constraints - Wildcard '*' is not working as expected


I am using a wildcard in my constraint, however, I am not seeing all of the correct components being added to this group.

NET "my_design/my_*" TNM = "my_grp";

Why is this not working as expected?


The example above is a rare and isolated situation where the downstream components are not added to the time group as expected. However, when you specifically use the net, then the downstream componentsare added:

NET "my_design/my_my_net[0]" TNM = "my_grp";

This should have been covered by the previously mentioned constraint with the wildcard.

The root cause of this issue is that the search algorithm in the Constraint System searches for wildcard matches in the design networks. If none are found, then the search algorithm checks for wildcard matches in the designs signals.

The problemis thatif the wildcard matches some networks and some signals, then the Constraint System stops searching after the network matches, thus the signal matchesare notadded.

Ifyou turn thison by default, a large design run-time would increase as there are a significantly larger number of signals in a design than there are networks.To control this, you can choose to force the wildcard matching of signals (regardless if a network name was matched or not) by setting this environment variable to 1 (this only works in 12.3 and later):


AR# 34908
Date 12/15/2012
Status Active
Type General Article
  • ISE Design Suite - 12.1
  • ISE Design Suite - 12.2
  • ISE Design Suite - 12.3
  • More
  • ISE Design Suite - 12.4
  • ISE Design Suite - 13
  • ISE Design Suite - 13.1
  • ISE Design Suite - 13.2
  • ISE Design Suite - 13.3
  • ISE Design Suite - 13.4
  • ISE Design Suite - 14.1
  • Less
Page Bookmarked