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

hold timing problem #838

Open
drorar opened this issue Jan 6, 2022 · 1 comment
Open

hold timing problem #838

drorar opened this issue Jan 6, 2022 · 1 comment
Labels

Comments

@drorar
Copy link

drorar commented Jan 6, 2022

Describe the bug
Hello

In the AD9361 (Xilinx -- Vivado 2021.2) I get hold time issue between up_d_count and d_count in the up_clock_mon file
The d_count is generate in a different clock then the up_d_count

To Reproduce

image

Desktop (please complete the following information):

  • Project name and used carrier board [e.g. FMCOMMS2 ZC706]
  • Used Software: [e.g. Linux or No-OS]
  • Tool version [e.g. Vivado 2018.3, Quartus PRO 18.1]
  • HDL Release version [e.g. hdl_2019_r1]
  • Software Release version [e.g. 2019_R1]

Additional context
Add any other context about the problem here.

@drorar drorar added the bug label Jan 6, 2022
@jamesoncollins
Copy link

I've also seen issues with this module. The clock monitor appears to have synchronization registers but doesn't have constraints, or perhaps ASYNC_REG attributes, to tell the tool its an async clock path. For some reason I don't get a timing error, just a critical warning.

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

No branches or pull requests

2 participants