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

[fmc516] Select the appropriate delays to clock and data coming from ADC #6

Closed
lerwys opened this issue Dec 4, 2012 · 3 comments
Closed

Comments

@lerwys
Copy link
Owner

lerwys commented Dec 4, 2012

There is a timing violation in that 1.4 acquisition window is not sufficient for IDDR, as reported
by timing analyzer.

Calibrate the delay from clock and data to match them.

@lerwys
Copy link
Owner Author

lerwys commented Dec 6, 2012

Applying both data and clock delay in an ADC channel basis is not possible to achieve timing closure. Although, the clock from ADC is half the specified in the constraint. So, we should be fine with a small setup/hold violation.

@lerwys
Copy link
Owner Author

lerwys commented Mar 19, 2013

The clock from the ADC is only half of the specified in the consttraint if some divider option is used in the ISLA216. By default, the divider is set to 1 and, thus, the clock from the ADCs are the same as the acquisition clock.

However, thus far, the tests show correct acquisition of data, just some delays (see .ucf and/or embedded-sw for the values) were needed to fix some inconsistencies.

@lerwys
Copy link
Owner Author

lerwys commented Jun 27, 2013

No problems detected so far.

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