ID:188000 Following signals have routing constraints that seem to cause deterministic congestion. Routing constraints for some of these signals will be removed.

CAUSE: The signals listed in the sub-messages have routing constraints that seem to be causing unresolvable congestion in the router. The most likely cause of such a congestion is constraining two signals to use the same routing resource. For example, two signals are constrained to use route_port = DATAA to drive the same destination atom. Note that the Fitter cannot tell which sets of signals have conflicting constraints. For example, if signals A and B vie for the same resource, and signals C, D, and E vie for another pair of resources, all five signals will be listed in no particular order. Some of the listed signals can have routing constraints auto-generated by the Fitter (for example, DDIO I/O driving DDIO input registers), and they will be marked as such. If you have manually constrained signals that are listed below along with auto-generated constrained signals, remove manual routing constraints to allow the Fitter to obey the auto-generated constraints. The Fitter will remove routing constraints for some of the listed signals to get a legal route. The signals will get their constraints removedone by one, until a legal route can be achieved. When a constraint for a signal is removed, a separate information message will be issued. Do note that the routing constraints for all the destinations of a signal will be removed, since the Fitter cannot determine which particular path in the constrainthas caused the congestion.

ACTION: The Fitter will achieve a legal route by removing some routing constraints. However, it is recommended that you either edit or removethe offending routing constraints for the following reasons:
  • Compilation without offending routing constraints is faster.
  • If some of the offending constraints are auto-generated, the Fitter will have a higher chance of obeying them if non-auto-generated offendingconstraints are removed.