forked from YosysHQ/nextpnr
-
Notifications
You must be signed in to change notification settings - Fork 2
Need site routing test framework #234
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
Labels
Comments
This was referenced Mar 29, 2021
Yes |
See YosysHQ#681 This probably makes most sense in a script that is run The relevant Python functions will be:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
One of the more fragile but critical pieces of logic in the FPGA interchange nextpnr arch is the site routing logic. For clarity, this is the collection of code that implements the isBelLocationValid part of the nextpnr Arch API. This implementation must both be fast (amortized over the entire placement step) and precise and accurate. That is a mixture that means that it should be well tested, so that as complexity increases or speed improvements are done, there is a way to verify that it is still correct.
The suggested site routing test framework would consists of 3 parts:
Example:
Netlist:
Test case:
Invocation might look like:
Alternate designs are welcome and accepted.
The text was updated successfully, but these errors were encountered: