10-02-2015 12:01 PM - edited 10-02-2015 01:29 PM
First some complaints:
Why in the world can't this core be generated for Tx-only? This thing is a bear to use, with pieces needed from all over the place. Starting with XAPP592 in my case (Zynq 045), generate the SDI core, generate the GTX transceiver separately, then hack the SDI wrapper from XAPP592 to wire everything up. And for me, where I do not need the Rx path (which includes a ton of extra stuff such as the DRU), there's a lot of hacking required.
Life would be a lot easier if the wizard that generates this core allowed customization of what features are needed (which standards (SD/HD/3G), which directions (Rx/Tx), clocking options, etc), then spit out the whole design all wired up inside a wrapper that includes the SDI core, the GTX transceiver, and support logic. The way it works now is almost starting from scratch. XAPP592 helps, but c'mon guys! We're making the transition from HDMI with an external HDMI transmitter. HDMI is a piece of cake compared to this beast and makes me seriously wonder if SDI is worth the hassle.
Now my question:
If I'm only using the SDI core to transmit can I tie all of the input ports for the receiver side to GND and leave all of the outputs on the receiver side unconnected? Or just leave all of the receiver ports unconnected? Neither PG071 nor XAPP592 addresses the Tx-only case.
10-06-2015 10:17 PM
10-02-2015 01:53 PM
10-06-2015 10:17 PM
10-09-2015 08:55 AM
Thanks for the response. Yeah, I was already heading down that path. Still disappointed by the cobbled-together nature of this IP. But at least it's free!
02-21-2020 11:34 PM
I know this is a really old post, but I have encountered a problem which is really related to this and I can't still solve it. I want to use the core for Tx only and I have made the connections as mentioned above. But in SD format, I have no video output. Any help is highly appreciated. I have explained the problem in more details here, but no one has answered yet!