Document ID
APT-DS-SLVS-RX-0001
Revision
2.1
IP version
3.4.1
Release date
November 2026
Chapter 2: Functional Description

2.1Architecture

The core is the link layer of an SLVS-EC receiver and comes with the physical layer it runs on. The bundled PHY recovers the clock and data on each lane, aligns and decodes the 8b/10b symbols and deskews the lanes; the core takes the decoded lanes from there. Every packet then passes through the stages below and leaves as video on the output selected at build time.

data_clk_i (lane clock = line rate / 20) axi_aclk (independent) from the SLVS-EC PHY lane words and K flags Lane alignment Start / End Code byte realign Pad Code removal Header decode 3 copies x CRC16 Frame Start / End Line Valid Payload integrity CRC build: CRC32 ECC build: Reed- Solomon correct Pixel unpack RAW8 to RAW16 16-bit containers Line Length trim Framing and crop image / EBD split skip, width, height SOF / EOL marks Output FIFO 128 to 16384 words m_axis_aclk M_AXIS AXI4S build vid_io_out NATIVE build EBD FIFO 32 to 16384 M_AXIS_EBD EBD output on clock-domain crossing: configuration down, counters and status up (inside the core) AXI4-Lite register file ID, version, build | link configuration | error counters | crop, video and EBD status S_AXI 24 registers data_clk_i domain axi_aclk domain stream clock side of the FIFOs video data path
Figure 2-1.Functional block diagram. The video path runs on the lane clock; the register file has its own clock; an AXI4S build reads its output FIFO on the stream clock, and the embedded data output, when built, has its own FIFO and clock. All crossings are inside the core.
  1. Lane alignmentFinds the Start Code on the lanes, realigns bytes that arrive split across lane words, and removes Pad Codes, so each packet starts on a clean word boundary at any lane count.
  2. Header decodeChecks the three copies of the packet header with CRC16 and uses the first good copy. Frame Start, Frame End and Line Valid come from it.
  3. Payload integrityThe CRC build checks the CRC32 footer of each packet. The ECC build corrects the payload with Reed-Solomon codes and strips the parity bytes.
  4. Pixel unpackConverts the payload bytes back into RAW8 to RAW16 pixels, places each in a 16-bit container and cuts the line at Line Length so payload stuffing never reaches the output.
  5. Framing and cropBuilds frames from Frame Start to Frame End, sends image lines to the video output and embedded data lines to their own stream, applies the crop registers and marks start of frame and end of line.
  6. Output FIFOsA line buffer for native video, or a clock-crossing FIFO for AXI4-Stream, plus a second clock-crossing FIFO for the embedded data output when it is built. Both are sized in the IP GUI.