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

Why is certain clock frequency producing protocol violations? #6

Open
nileshbpat opened this issue Jan 8, 2025 · 0 comments
Open

Comments

@nileshbpat
Copy link

Observation is,
There is a functional dependence on core clock frequency.
In general, design is not working at lower frequencies (i.e. 100MHz).
For 500Mhz, we're seeing the following error, which points to dependency on the programmed frequency.
Error > Clock in to Data Out for Slave(16.990ns) is more than tSCO(12.000ns)

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

1 participant