10-06-2019 10:39 AM - edited 10-06-2019 10:39 AM
I have a Vivado 2018.3 project that contains the SDI Tx Subsystem, controlled by PetaLinux 2018.3 on the KCU116 board.
I can happily see 1080p@60Hz (3GA) SDI output on my SDI scope (Tektronix Prism), but the scope informs me that the CRC values are incorrect (or missing?) and the VPID value is missing.
How can I resolve this? While this specific 1080p mode is detected by the scope, other modes (particularly the 3GB modes) cannot be detected correctly without the VPID.
10-09-2019 06:42 AM
What command are you using to start the SDI TX?
What do you get if you are using the modetest command?
modetest –M xlnx -s <connector_id>[@<crtc_id>]:<mode>[-<vrefresh>][@<format> - w <connector_id>:<property_name>:<property_value>
10-11-2019 08:50 AM
Dear @florentw ,
Thanks a lot for your response, and apologies for the delay.
My set up is slightly different: I've taken the Xilinx SDI driver (https://github.com/Xilinx/linux-xlnx/blob/xilinx-v2018.3/drivers/gpu/drm/xilinx/xilinx_drm_sdi.c) and slightly modified it to suit my design. To start the SDI TX, I simply insmod the driver.
In order to change the mode, I use the xilinx_sdi_mode_set () function in the driver with one of the modes listed in xlnx_sdi_modes.
As far as I can tell, the driver is going through the process of setting the VPID with xilinx_sdi_set_payload_line () and xilinx_sdi_set_payload_data (), and setting a bit to send the CRCs.
Is there something else that perhaps needs changing in the driver itself?
10-14-2019 11:59 PM
I do not know. If you start modifying the driver, then you only can know what you have done and what you need to make it work
Note that this is not supported by Xilinx
I suggest you start back with the released driver and you check if it works with modetest.
10-15-2019 04:44 AM
10-22-2019 09:07 AM
Could you find the solution to your problem?
If you did, could you share it with the community?