These signals are available when the Video Interface is set to Native Video in the Vivado IDE.
| Signal | I/O | Description |
|---|---|---|
| VID_IO_IN_data[n-1:0] | I |
Native video input data Where n=bpc*ppc*3. For 10bpc at 2ppc, n=10*2*3=60 For 12bpc at 2ppc, n=12*2*3=72 |
| VID_IO_IN_active_video | I | Native video active video input |
| VID_IO_IN_field | I |
Native video field input For interlaced videos, fid toggles based on the field selected: 0- even field 1- odd field For progressive videos, fid is set to 0. Note: fid is expected to toggle in case of psf and 3G-level B
progressive videos, as in these modes, one progressive frame is split into two
fields. These two fields are transported independently, similar to interlaced
video, and again combined and correctly paired together at receiver side with the
help of fid signal to construct the original progressive frame.
For example, when 1080p 60 Hz video is transported on 3G-SDI level B-DL, the video transport is actually 1080i 60 Hz. The transport is interlaced, but the picture is progressive. |
| VID_IO_IN_hblank | I | Native video hblank input |
| VID_IO_IN_vblank | I | Native video vblank input |
| vid_ce | O | Native video clock enable |
The native video interface is expected to start from the start of active video or start of blanking. In interlaced video format, the data of field 0 comes before field 1.
Vertical timing is defined by vblank signal. VBLANK is 1
indicates, vertical blanking lines. Similarly, for horizontal timing information, hblank
signal is used. Active video is sent only when hblank and vblank is 0 and
active_video signal is asserted. A sample of native video interface
timing is shown in the following image.
