Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

himbaechel/gowin: add timing information #1345

Merged
merged 2 commits into from
Aug 21, 2024

Conversation

Ravenslofty
Copy link
Collaborator

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.

@Ravenslofty Ravenslofty force-pushed the lofty/himbaechel-gowin-timing branch 3 times, most recently from 336c915 to f4ea232 Compare August 2, 2024 05:12
Copy link
Member

@gatecat gatecat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, feel free to merge whenever you're happy with it

@Ravenslofty Ravenslofty merged commit 01737a4 into master Aug 21, 2024
16 checks passed
@Ravenslofty Ravenslofty deleted the lofty/himbaechel-gowin-timing branch August 21, 2024 09:58
@gatecat
Copy link
Member

gatecat commented Aug 21, 2024

It would be nice to get BRAM timings added at some point, depending on the clock-to-out time it's not uncommon for it to actually be the critical path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants