Description

Cases have been seen where BUFIODQS clock nets have not been routed when using the OPTDELAY resource.

This is required to match the delay of associated BUFR clocks when both are clocking the same I/O components.

There are two known causes:

1. If PAR is run with multi-threading enabled (-mt) the multi-threaded router does not respected the locked route previously done by PAR using the OPTDELAY resource.
   The multi-threaded router will only rip up and reroute the net if it is involved in a failing timing constraint (maxskew in one case).
    
2. If the net is unrouted and then rerouted in FPGA Editor it will not be rerouted with the necessary OPTDELAY resource.

Correct routing of BUFDQS net using the OPTDELAY resource:

Solution

A DRC check will be created to catch incorrectly routed BUFIODQS nets.

Meanwhile the design can be examined in FPGA Editor if incorrect routing is suspected.

Remove any unnecessary timing constraints to prevent the rip up and reroute behavior mentioned above.