Iserdese2 to iserdese3?
Iserdese3 doesn't support 6:1 ratio...could go with a 4x clock and 8:1, but that seems like overkill. Is there a reason behind going to 3x clock rather than 2x?
Might need to do idelay, but seems like that's probably the way to go for iserdese3. And if idelay, depending on routing, etc, maybe could do 1x and do away with the dru?
Hi Rich..
I hit the same issue just around the same time as you.. I'm looking at this issue. If the customer approves using this core, I'll be working on it. My first inclination was to go 8:1, but I'll ponder going 2:1
I'm not associated with this project, but adding the capabilities to go to Ultrascale/Ultrascale+ to this project would make it much more useful.
https://github.com/OVGN/OpenHBMC/issues/5
Take a look how the dru works. Lasse