This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/DM385: The video have critical problem

Part Number: DM385

Tool/software: Linux

Hello, 

I have encounter a critical problem in DM385

The video format is YUV4:2:2, 1920x1080, video pixel clock is 74.25MHz. the timing is as follows: 

DM385 is DM385AAARD21F,the voltage of ARM, HDVICP, CORE is 1.35V; DDR3 is two 256MB DDR3L,clock is 533MHz。

Rdk is ipnc rdk 3.8.0,I modified the base on MN34041 full feature config。The modified code is as below :

In cameraLink_drv.c add:

pVipCreateArgs->inFmt.dataFormat = FVID2_DF_YUV422SP_UV;
pVipCreateArgs->videoIfMode = ISS_CAPT_YUV_16BIT;

In issdrv_captureApi.c add:

ipipeif_reg->CFG2 = 0x08;

ipipe_reg->SRC_FMT = 0x03;
ipipe_reg->SRC_HPS = 192;
ipipe_reg->SRC_VPS = 41;

isif_reg->MODESET = 1000;
isif_reg->SPH = 192;
isif_reg->SLV0 = 41;
isif_reg->SLV1 = 41;
isif_reg->CLDCOFST = 0;
isif_reg->SYNCEN = 0x1;

There is critical problem in the motion scene:

1. if I change the value of the vdint0, the raw data saved from DCC like below:

a. vdint0 = 100:

b. vdint0 = 1000:

2. The YUV data save from DCC is more serious like this:

I don't know the reason of the problem, could you help me? Thans!

  • Hi,

    If there is no slice processing concept, we usually set vint0 same as active vertical lines.

    If you set a smaller value, Rest of the pipeline will be using a partially filled buffer.(Artifacts will be visible only during motion in the scene).

    ~Nithin

  • Hi

    Thanks for your reply.

    When we set the vint0 = 1075, the raw data is only 1035 line video data, follow-up is 80h.

    No matter what vdint0 value is set, the YUV data always has the same problem.

    The attachment is a video record by vlc