Forum Discussion
Altera_Forum
Honored Contributor
12 years agoHow many unconstrained paths? Because if you end up with entire unconstrained clock domains, it's possible that a big part of your design isn't analysed by Timequest at all, and you could have timing problems. Timing problems are one of the most common causes of erratic behaviours.
At least try to constrain all your I/O and clocks, and check in Timequest's clocks report that they are all there, with the correct frequencies.