ID:171055 Can't globally route signal "<name>" into a region -- total global routing resources requested would exceed hardware limits

CAUSE: The Fitter cannot follow a constraint because it would require that the specified signal be globally routed into a certain region on the device, but doing so would exceed the global routing resources in that region. The following messages list the existing allocation of those resources to user signals.

ACTION: Refer to the message that appears above this message to determine what constraint cannot be honored. One of the following actions may resolve the issue.

Remove the constraint that could not be honored.
Remove or relax location constraints on nodes requiring the global routing resources in the given region.
Set the Global Signal logic option to OFF for some of the signals that are allocated global routing resources in the given region. You may do this for that entire global signal, or only between that global signal and destination nodes in the specified region. The previous messages indicate the destination nodes requiring the globally routed signals.