Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
| resources:eval:user-guides:ad-fmcomms2-ebz:interface_timing_validation [08 Mar 2018 12:37] – [Digital Interface Timing Verification] Michael Hennerich | resources:eval:user-guides:ad-fmcomms2-ebz:interface_timing_validation [01 Jun 2018 13:22] – [Digital Interface Timing Verification] Michael Hennerich | ||
|---|---|---|---|
| Line 67: | Line 67: | ||
| sample rate of 61.44MSPS the data/clock delays originally computed during driver initialization don't work anymore. | sample rate of 61.44MSPS the data/clock delays originally computed during driver initialization don't work anymore. | ||
| For this reason we always rerun the interface tuning algorithm whenever a filter is enabled at the target baseband rate. if the FIR is disabled the original settings are restored. | For this reason we always rerun the interface tuning algorithm whenever a filter is enabled at the target baseband rate. if the FIR is disabled the original settings are restored. | ||
| + | |||
| + | Interface tuning upon FIR enable can be omitted by setting following device tree attribute: | ||
| + | |||
| + | * adi, | ||
| + | |||
| + | |||
| In some cases the Digital Interface Timing Analysis and Verification is not required. For example: | In some cases the Digital Interface Timing Analysis and Verification is not required. For example: | ||
resources/eval/user-guides/ad-fmcomms2-ebz/interface_timing_validation.txt · Last modified: 30 Oct 2018 16:34 by Michael Hennerich