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

Intel quartus axis_async_fifo constraints #17

Open
alexisfrjp opened this issue Jun 5, 2022 · 2 comments
Open

Intel quartus axis_async_fifo constraints #17

alexisfrjp opened this issue Jun 5, 2022 · 2 comments

Comments

@alexisfrjp
Copy link

Quartus gives HOLD slack using the quartus and quartus_pro constraint files.

  • rd_ptr_gray_reg[1] rd_ptr_gray_sync1_reg[1]
  • rd_ptr_gray_reg[0] rd_ptr_gray_sync1_reg[0]
  • rd_ptr_gray_reg[2] rd_ptr_gray_sync1_reg[2]
  • wr_ptr_update_sync3_reg wr_ptr_update_ack_sync1_reg

The problem is the Data Required Path, clock path:
image

@alexforencich
Copy link
Owner

Unfortunately, the only solution I have found for this is to use clock groups. Which is a terrible solution because clock groups are terrible and should never be used, ever. But unfortunately timing constraint support in Quartus is also terrible, so I have not been able to find a better solution for setting a "datapath only" delay constraint that supersedes all other setup and hold constraints.

@alexforencich
Copy link
Owner

If you have a better idea though, please let me know!

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

No branches or pull requests

2 participants