FPGA: clean up false timing violations and make the core clock configurable#935
Draft
AlessandroVaraldi wants to merge 10 commits into
Draft
FPGA: clean up false timing violations and make the core clock configurable#935AlessandroVaraldi wants to merge 10 commits into
AlessandroVaraldi wants to merge 10 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR cleans up the FPGA timing flow so that Vivado reports the real critical paths instead of being dominated by non-functional timing violations.
In particular, it:
The main goal is to mask the non-real timing violations that were previously polluting the reports. Before these changes, Vivado was spending attention on artificial CDC/debug paths that do not represent the actual performance limit of the design. After this cleanup, the timing reports expose the real bottlenecks.
With these fixes in place, the maximum synthesizable frequency without timing violations is now approximately:
This makes the timing results much more meaningful and gives a realistic basis for future RTL optimization work.