Forum Discussion
How could I understand “IOPLL could drive the lvds tx transmitter in adjacent bank"
- 1 year ago
Hi,
that sounds plausible:problem is that tx_outclock is generated differently in single-bank and "wide" SERDES. SERDES IP editor doesn't know about final implementation, thus it accpects tx_outclock phaseshifts that are only applicable in single bank design.
A separate pair of PLL outputs drives tx_outclock SERDES channel through dedicated "phase_shifted_tx_outclock_serdes.outclock_tree". In wide SERDES topology, the phase shifted outclock is apparently not available or not used for some reason. You can only implement phase shift values that are aligned with regular bit clock, e.g. 180° for frequency factor 2.
SERDES IP editor should issue a warning about possible phase shift implementation issues.
Oh, it's weird.
My quartus is Quartus Prime Version 19.1.0 Build 240 03/26/2019 SJ Pro Edition.
May be there's any Patches which I need to install?
- FvM1 year ago
Super Contributor
Hi,
I found that above posted .qar file generated with Quartus V19.1 Std. can be flawlessly imported in Quartus Pro, your V19.1.0 or any newer version. All you need to do is to regenerate SERDES IP.- lambert_yu1 year ago
Contributor
Yes, I just updated the IP and select the enable tx_outclock port.
- FvM1 year ago
Super Contributor
With which result? SERDES TX driven by PLL in adjacent banks works for me with all tested Quartus versions, Std. and Pro. But as stated, you need to use the "wide SERDES" approach, using only a single SERDES TX instance that drives all TX pins. They can be either located in the PLL bank, defined by refclk pin location or both adjacent banks.