• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 97 subscribers
  • Views 551 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

TDA4VM: the modification of csirx and csitx about YUV format in SDK7.3

TDA4VM: the modification of csirx and csitx about YUV format in SDK7.3

subin li
Expert 1050 points
Part Number: TDA4VM

Hi，all

The previous problem has not been completely solved, so create a new one.

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1024017/tda4vm-the-modification-of-csirx-and-csitx-about-yuv-format-in-sdk7-3

1. The document you sent me is basically the same as the one I read before. From this document, I don’t know what you mean by "the format is actually reverse". We can’t understand why this modification is needed

2. We just want to know If the image format output by our camera is YUYV, how to set this data format.

3. I mean SDK7.0. We have not yet started using SDK8.0. In the two pictures I attached when I asked the question before, you can see that the driver in SDK7.0 is different from SDK7.3.

Regards,

Subin

  • 0
    TI__Guru**** 475835 points

    Hi Subin li,

    I thought you are able to correctly capture data from the CSIRX in YUYV format, isn't it ? The only difference is in understanding.. What should be used in the output format of CSIRX for the the input data format, isn't it?

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Expert 1050 points

    Hi, Brijesh

    I can't understand what you mean very well.

    1. We can't understand why there are the following changes in SDK7.3. From the document, we cannot understand the corresponding relationship between the format.

    2. Our current usage scenario is, the image format output by our camera is YUYV, The parameters we use when calling Fvid2_create are, inCsiDataType=FVID2_CSI2_DF_YUV422_8B, outFmt.dataFormat=FVID2_DF_YUV422I_YUYV. Then the image data we received in DDR is UYVY. Is this correct？

    If we change outFmt.dataFormat=FVID2_DF_YUV422I_UYVY, the image data we received in DDR is YUYV.

    We want to figure out the principle and reason of this.

    Regards,

    Subin

  • 0 in reply to subin li
    TI__Guru**** 475835 points

    Hi Subin Li,

    I had already replied that the changes are done to align the data type with the FVID2 frame format. In FVID2, when we say UYVY format, the assumption is that U is stored in the lower byte and i had pointed in the fvid2 header file where this format is explained. 

    In earlier release, it was not matching, so this is corrected in the later release.

    Regarding your input and output format, let me check and get back to you.

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Expert 1050 points

    OK, Looking forward to your reply.

  • 0 in reply to Brijesh Jadav
    Expert 1050 points

    Brijesh Jadav said:
    Regarding your input and output format, let me check and get back to you.

    Hi, Brijesh

    Is there any new news?

    Regards,

    Subin

  • +1 in reply to subin li
    TI__Guru**** 475835 points

    Hi Subin li,

    According to TRM, when we set the output format as FVID2_DF_YUV422I_UYVY/VX_DF_IMAGE_UYVY, it internally set the MODE field as 3, which means the output, which means output frame would have U0 in the lower byte, followed by Y0, followed by V0 and then Y1. 

    Typically, on CSI2, YUV422 data is sent with U on the first clock cycle. so can you check what is the output format from the sensor? If it is U->Y->V->Y, then output could bein different order.

    Regards,

    Brijesh