--- Quote Start ---
Good call on checking what the routing was trying to do - turns out it actually was routing the signal half way round the device in an attempt to make a hold requirement that is utterly nuts! I'm working on playing with multicycle constraints to get it to actually analyze the path in a more sane way...
Thanks all for the help!
--- Quote End ---
This is identical to a problem I had to a global fanout async reset.
The Reset was coming from an synchronous source, and for some reason, it decided that a reg somewhere had some crazy hold requirement, and hence routed the single output through a global buffer (as expected), then through some logic on the edge of the chip, then fanout all over the chip giving me 1000s of recovery violations up to 10ns (in a S4)
Solution (as supplied by altera) was to relax the hold time on the fanout of this reg, and the problem went away.
Honored Contributor
