Forum Discussion
3% Logic Utilization and 125% Peak routing doesn't make sense. There's a message that a lot of routing is being added for hold time, which I'm pretty sure is the problem. Go to Assignments -> Settings -> Fitter and disable Hold Time Optimizations, so the router won't add any delay for hold time. It should fit pretty quickly. Then launch TimeQuest, and Report Hold Summary(also Report Removal Summary, which is like a hold check for asynch. resets). Then analyze what's failing and why. There's going to be something strange(passing data between unrelated clock domains that shouldn't be analyzed, multicycle setup assignments without a multicycle hold, or maybe gated clocks) that is causing large hold requirements and breaking things when the fitter tries to meet your requirements. The source of those large hold requirements needs to be fixed.