3.4.1AXI4S
Standard AXI4-Stream rules: tvalid and the payload hold until the handshake, and
tready may do anything while the FIFO has room. The capture below shows the start of a frame,
two line ends and a sink stall.
tready returns.3.4.2NATIVE
The blanking follows the sensor: the line pitch on the output is the line pitch on the link. The capture shows the shortest intervals the output can produce, reached only when lines or frames arrive back to back.
data_clk_i clocks: a frame of two short lines, then the start of the next frame. Breaks mark compressed time.| Interval | Clocks |
|---|---|
vid_vblank fall to first beat of a frame | 4 |
vid_hblank between two lines | 3 or more |
Last beat of a frame to vid_vblank rise | 2 |
vid_vblank between two frames | 9 or more |
vid_hsync width / vid_vsync width | 1 / 4 |
| Latency, link to output | one line |
To feed AMD Video In to AXI4-Stream, connect vid_io_out to vid_io_in, clock
vid_io_in_clk from data_clk_i with vid_io_in_ce tied high, and set its
width for 32 x LANE_NUM bits (for example 4 pixels per clock, 1 component of 16 bits for 2 lanes). Use
its independent clock mode to move the stream to another clock. A block built for frame, line and data
valid inputs takes fv = not vid_vblank, lv = dv = vid_active_video. The NATIVE
output never carries embedded data lines; with the embedded data output built they arrive on
M_AXIS_EBD.
3.4.3Embedded data
The same AXI4-Stream rules as the image stream, on its own clock and FIFO. Each embedded data line is
ceil(Line Length / (2 x LANE_NUM)) beats long and ends with tlast; the first beat after each
Frame Start carries tuser. A frame without embedded data lines sends nothing, so the stream is
idle between groups. The capture in Embedded data output
shows it next to the image stream.