12-03-2018 09:19 PM - edited 12-03-2018 09:27 PM
I am using spartan 6 fpga for Hd-Sdi video streaming, for this application am using spartan 6 GTP transiver and tripple rate sdi core, to make sure the external link i used ibert core, here loopback and near end is working and i checked pattern generation code which is also working fine.
but when i give HD video am not getting the output.
the below image shows when i connect HD video, i can see data is flowing in the core which was captured in chip scope.
My video resolution is 1280*720 and this is verified in chipscope am getting 1650*750 and in below image you can see that there is no payload data and it is showing payload valid id is one always.
12-03-2018 09:53 PM
the below image shows the width of the TRS signal and EAV, i don't know whether data between TRS and EAV is proprer or not?
12-05-2018 01:42 PM
@hemanth_93I recommend you take a look at XAPP1076. It is an example design that runs on the Spartan-6 SP605 demo board. It not only contains the example design, but it also give some design advice that may help you in implementing and testing your Spartan-6 SDI design.
For the Spartan-6 FPGA Triple Rate SDI v1.0 (Rx) to work, the GT PLLs need to be locked on the reference clock. The recommended reference clock for Spartan-6 SD-SDI is either 148.5MHz or 74.25MHz as documented in DS849 and XAPP1076. Then once the PLLs are locked, then the IP will attempt to lock on the incoming stream. If it can't lock on the incoming stream, then nothing else will work. So you need to make sure that the Trile Rate SDI is locking to the proper mode.
If at all possible try to get an SP605 and the related AVB FMC (CTXIL671) card so that you can test out the example. If you can't do that then at least review how the design is connected, and make sure to use the provided control logic as this is necessary to properly setup and control the GTs with the Triple Rate SDI IP.
12-05-2018 11:44 PM - edited 12-06-2018 12:15 AM
@chrisaras per my knowledge pll's were locked and here, transport family is also showing 1280x720 which is equal to 0001 in code this i saw in chip-scope and sometimes 1111
transport_lock is '1' from line number 1A to 1F(26th line to 31st line) i.e it became high when active pixel started.
this is in the attached picture.