Add a post-route Fmax and utilization table - #1
Merged
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 branch adds post-route timing and utilization for the synchronous and asynchronous FIFOs through the open nextpnr-xilinx flow. A reusable fmax.sh script places and routes each FIFO in a registered-boundary harness and reports the maximum clock frequency alongside LUT, flip-flop, block RAM, and distributed RAM counts. The sync_fifo reaches 324 MHz. The async_fifo carries one frequency per clock domain, 296 MHz on the write clock and 343 MHz on the read clock, since a single figure has no meaning across the two independent clocks. The README carries the numbers with an honest note that the open flow is experimental and not vendor signed timing analysis.