himbaechel/gowin: add timing information #1345
Merged
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 wires up enough of the Apicula timing data to give an Fmax for most designs. There are gaps in the implementation, but those gaps also existed in nextpnr-gowin, so it's not much of a loss.
The Fmax numbers do appear to be optimistic though - compared to the vendor tooling the numbers are about 20% higher and I don't entirely trust them. However, if the optimistic numbers say that a design doesn't meet timing, it definitely doesn't.