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

2.4Payload protection

SLVS-EC sensors protect the payload in one of two ways, chosen by the sensor mode. The receiver comes in a matching build, chosen with the Payload protection parameter (ECC_SEL). The lane count, ECC Option and CRC Option must match on both ends of the link.

Rule

Keep the protection of the build on. The CRC build runs with CRC Option on (CRC_OPTION = 1); the ECC build runs with ECC Option 1 or 2 (ECC_OPTION). The option of the other build has no effect. The core does not refuse a 0, but the supplied driver checks the setting against the build when an image stream starts and prints a warning if the protection is off or set on the wrong build. With the protection off the image still arrives; what is missing is the check.

Table 2-3.The two payload protection builds.
CRC build (ECC_SEL = 0)ECC build (ECC_SEL = 1)
Sensor modeCRC Option on (CRC32 footer)ECC Option 1 or 2
What the core doesChecks the CRC32 footer of every packetCorrects the payload block by block and removes the parity
CorrectionDetection onlyOption 1: 1 byte per block (2 parity bytes)
Option 2: up to 2 bytes per block (4 parity bytes)
ConfigurationCRC_OPTIONECC_OPTION, ECC_BLOCK
Error accountingPAY_CRC_ERR_CNT, and the Line Number of the last failing line in CRC_ERR_LINEC_ERR_CNT, FRAME_ERR_CNT and ECC_FAIL_CNT
Both buildsBad header copies and lost headers in HDR_CRC_ERR_CNT; one sticky flag for software to poll in CRC_ERR_LINE[31]

With ECC, the payload of every line is split into Basic Blocks of 224 information bytes and a last block holding the rest, each followed by its parity. The core needs to know where the last block starts; the ECC_BLOCK register gives that from Line Length and Pixel Bit (the driver computes it, see Programming ECC_BLOCK).

line payload, Payload Length PL = n x 224 + r bytesBasic Block 0224 BPBasic Block 1224 BP...Basic Block n-1224 BPLast blockr B (16 to 224)PP = parity: 2 bytes per block with ECC Option 1 (corrects 1 byte), 4 bytes with ECC Option 2 (corrects up to 2 bytes).The core corrects each block and removes the parity before it unpacks the pixels.
Figure 2-2.Reed-Solomon block structure of one line payload in the ECC build.

A block the code cannot correct is passed on unchanged and counted in ECC_FAIL_CNT; the core never alters data it cannot fix. On a healthy link ECC_FAIL_CNT stays at 0 and C_ERR_CNT grows slowly, if at all. A fast-growing corrected count is an early warning of a signal integrity problem, well before images degrade.