I/O D1/D3 delay values higher than needed.

Hi Anand!

Thank you for your answer.

In my second post I wrote that I can manually set the delays in order to meet timing.

So the question was what is the reason for Quartus engine not to choose delay settings in order to meet timing.

It is strange, isn't it, that Quartus sets the delays so timing fails, but you can manually choose the right values for timing to pass.

And the main part of question was - Quartus almost always chooses right values, except in the project I attached.

The small changes in the project, as I mentioned, lead to right values in delays which Quartus choose.

I thought that maybe it is a bug and our project could be helpful for the team to fix it.

It is strange and probably a bit useless if need to check correctness every time and manually set delays.

In our test project case we can show that Quartus automatically chooses delays which lead to perfect slacks in both setup and hold.

So it is arguably that Quartus chooses delay values and as you said "does not automatically set delay elements to maximize slack".

And I also asked for the root cause of the problem.

--

Best regards,

Ivan