Forum Discussion
Altera_Forum
Honored Contributor
8 years ago --- Quote Start --- You better run TimeQuest GUI and check all failing paths and io paths. --- Quote End --- It's the case, I generated these reports in TimeQuest GUI. I've just run failing paths - 200 violations (I suppose it's maximum that can be displayed, probably there are more ...) --- Quote Start --- Your setup report seems about internal paths [launch and latch are divclk] but your hold report is io path which shows some negative slack. You need to check setup for io paths as well. Both inputs and output io paths need to be reported. --- Quote End --- Ok, I did it - there are no violations in "Report All I/O Timings" --- Quote Start --- If io paths are failing you can use some phase shift to help it out [you can experiment on that]. For internal paths on 150MHz that is a design issue and basically 150MHz should not be a problem in many fpgas. But it is not clear why this failure occurs. --- Quote End --- Do you mean here "Report All I/O Timings" ?