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

Automatic definition of false path constraints #87

Closed
whitequark opened this issue Jun 5, 2019 · 3 comments
Closed

Automatic definition of false path constraints #87

whitequark opened this issue Jun 5, 2019 · 3 comments
Labels
improvement
Milestone
0.1

Comments

@whitequark
Copy link
Contributor

In oMigen, there is some code that adds false path constraints on MultiReg and AsyncResetSynchronizer automatically. Unfortunately it looks like it is only designed to work properly with Xilinx; the relevant code for every other platform seems to be blindly copied from the Xilinx file and as far as I can tell it has never worked in any meaningful way.

This needs to be replicated in nMigen, and that requires carefully investigating the data toolchains require to add false path constraints.
@Wren6991 Wren6991 mentioned this issue Jun 28, 2019
Open
@whitequark
Copy link
Contributor Author

Good documentation on synchronizers: #227 (comment)

@whitequark
Copy link
Contributor Author

Implemented for Vivado in #227.

@whitequark
Copy link
Contributor Author

AFAIU, ISE and Diamond do not consider all clocks related by default. So, there is no need to automatically define false path constraints in these toolchains; although one might need to manually add false path constraints for clocks that go through PLLs, etc.

@whitequark whitequark added this to the 0.1 milestone Sep 24, 2019
Closed
@cklarhorst cklarhorst mentioned this issue Oct 12, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
improvement
Projects
None yet
Milestone
0.1
Development

No branches or pull requests
1 participant
@whitequark