Hi,
Error goes here:
[m3vpss ] 641630: Assertion @ Line: 669 in links_m3vpss/display/displayLink_drv.c: status == FVID2_SOK : failed !!!
what kind of FVID2_Format is correct?
Best regards,
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.
Hi,
Error goes here:
[m3vpss ] 641630: Assertion @ Line: 669 in links_m3vpss/display/displayLink_drv.c: status == FVID2_SOK : failed !!!
what kind of FVID2_Format is correct?
Best regards,
Hi Ariel,
It could fail only in one of the below condition
1, pitch is less than the width of the image
2, picture size is more than VENC frame size
3, input format is not supported.
Could you please check your input parameters and see what is wrong?
Regards,
Brijesh Jadav
Hi Ariel,,
Could you provide more details like what format you are using, resolution of the display etc.
Regards,
Brijesh Jadav
Brijesh Jadav said:It could fail only in one of the below condition
1, pitch is less than the width of the image
2, picture size is more than VENC frame size
3, input format is not supported.
Thank you, Brijesh. And sorry for my late reply. I check the three condition you listed, pitch of the image and picture size of venc are correct, so it maybe due to the wrong input format.
I use VSYS_STD_1080P_60 for display. If I directly connect vdec to vdis(decId - ipcOutVideoId - ipcInVpssId - displayId), it caused to format incompatibility, and tilerEnable of vdec also should be set to FALSE, otherwise it will fail to TILER, what puzzled me. I don't know why TILER should be OFF.
Then I inserted swms between vdec and vdis(decId - ipcOutVideoId - ipcInVpssId - swMsId - displayId), it can work well now.
hi Ariel,
Decoder outputs in YUV420 format but this format is not supported in the display driver. Display supports YUV422I format, which is why it is failing. If you use swms in between, it converts YUV420 format to YUV422i, so it will work.
Regards,
Brijesh Jadav
Thank you very much, Brijesh. As you said, I realized this issue afterwards. But I am still curious about why TILER should be OFF, can you explain it?
Display path does not support Tiler buffer, so input buffer for display should be from non-Tiled memory. That's why you have to set Tiler to OFF.
Regards,
Brijesh Jadav
But in case multich_progressive_vcap_venc_vdec_vdis, tiler of vdec is set enable and it can display without TILER issue:
decPrm.tilerEnable = TRUE;
but in that case, swms will convert tiled YUV420 to non-Tiled YUV422I.
Regards,
Brijesh Jadav
Brijesh Jadav said:Decoder outputs in YUV420 format but this format is not supported in the display driver. Display supports YUV422I format, which is why it is failing. If you use swms in between, it converts YUV420 format to YUV422i, so it will work.
But the Display Link -Features part of the file DVRRDK_02.80.00.10\dvr_rdk\docs\Trainings\DVR_RDK_McFW_Link_API_Training.pdf says Input Data format of display can be YUV422/YUV420.
Hi Ariel,
In 2.8 release, YUV420 is supported only on SD TV display, So
SDTV supports YUV422 and YUV420 display
HDTV supports only YUV422I display,
Regards,
Brijesh Jadav