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.

Sign up for GitHub

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

Jump to bottom

LV timing model workaround #1326

Open
litghost opened this issue Feb 20, 2020 · 2 comments
Open

LV timing model workaround #1326

litghost opened this issue Feb 20, 2020 · 2 comments
Labels
arch-artix7 cleanup help wanted todo 🗒️

Comments

@litghost
Copy link
Contributor

There is currently a workaround in place around the LV pip timing model.

There are two changes in prjxray for the workaround. First is here:
https://github.com/SymbiFlow/prjxray/blob/84b1457b885861fee221c5c6255d41cfb962ffc0/utils/create_timing_worksheet_db.py#L147-L155

Second is here:
https://github.com/SymbiFlow/prjxray/blob/84b1457b885861fee221c5c6255d41cfb962ffc0/fuzzers/074-dump_all/jobtiles.tcl#L51-L64

And one change in symbiflow-arch-defs, here:
https://github.com/SymbiFlow/symbiflow-arch-defs/blob/2bf2ed6ca1f8f158fa8fa8a9c0d506f2ca284029/xc7/utils/prjxray_edge_library.py#L545-L551

When/if the LV pip timing model is improved, these workarounds will likely no longer be required.
@litghost litghost mentioned this issue Feb 20, 2020
Merged
@litghost
Copy link
Contributor Author

This issue will track any progress to improving the LV pip timing models, and work to remove the current hack-y solution that is present. The current solution appears to generate error in the ~2-5% range, but further testing may show the workaround to behave worse in some circumstances.

@mithro
Copy link
Contributor

mithro commented Feb 20, 2020

FYI - @daveshah1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
arch-artix7 cleanup help wanted todo 🗒️
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mithro @litghost