• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 34 subscribers
  • Views 425 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.

DS90UB960-Q1: Does our 960 support transfer RAW format data to YUV format data and output to SoC

Zirui Su
Expert 5340 points
Part Number: DS90UB960-Q1


Hi team,

I would like to ask that does our DS90UB960Q1 support transferring RAW received data to YUV format and output to SoC?

My customer is asking that and they would like to know if the sample code part refer to this function, please kindly help to confirm it, thank you!

  • 0
    TI__Mastermind 29190 points

    Hi Zirui,

    1) What serializer is being used? If you are using a camera with a parallel 10-bit or 12-bit interface and using one of our 913A/933 parallel interface serializers, then our 960 device will take the received RAW data and repackage it as CSI-2 packets. During the repackage process, it is possible for our 960 device to set the data type of the packaged CSI-2 packets to YUV format. Recommend to see Section 7.4.16 CSI-2 Data Identifier in the 960 datasheet for more details on the process. See also registers 0x70 or 0x71 in the 960 datasheet, to see how to configure the data type in the CSI-2 packets, when operating in RAW mode.

    a) The code example that you shared is for when the 960 is connected to a 913A/933 serializer. Parallel data is being sent to the DES, which will be repackaged to a CSI-2 packet format. Part of the process is setting the data type in the data identifier byte. You can change the data type to YUV by changing the DT field in registers 0x70 or 0x71, to the appropriate CSI-2 data type code, which can be found online.

    2) If the 960 is connected to a serializer (953 or 935), which is feeding it CSI-2 packets, then you would not be operating in RAW mode. It would be in Synchronous or Non-Synchronous mode. In this case, there is no way to change the data type of the CSI-2 packets that the 960 receives. The 960 will only be capable of forwarding or aggregating the received CSI-2 packets to a specific output port.

    Best,

    Justin Phan

  • 0 in reply to Justin Phan
    TI__Expert 5340 points

    Hi Justin

    Thanks for your detailed clarify.

    Could you please kindly tell me which value should I write into 0x70 register since I want to change RAW to YUV? Is that 0x1F? Since I just see the default value is 0x2B and no more details for switching RAW to YUV, so I would like to know this.

    Besides, here are my 2 questions below:

    1. The approximate algorithm and workload of converting RAW10/8 to YUV422, want to know how to accomplish this convert?
    2. This part of the encoder is completed in which part of the circuit in the 960 chip?

  • 0 in reply to Zirui Su
    TI__Guru 66880 points

    Hi Jerry, 

    Since today is a US holiday for TI, we will resume activity on Monday 4/18. Thanks for your patience. 

    Regards, 

    Logan

  • 0 in reply to Logan Cummins
    TI__Guru** 103215 points

    Zirui,

    960 does not actually do color space conversions. What this is saying, is that if you are connected to a RAW mode serializer 913A or 933, those parts support RAW10 or RAW12 formats. But if you want to send a different format such as YUV422 10 bit from the sensor you can support that by sending one pixel over 2x RAW10 clock cycles (20 bits total), and then tell the 960 to output those packets with YUV422 10 bit data type instead of RAW10 in the packet header so the SoC will recognize. It does not actually perform any transform on the data - it just adjusts the packet header data type info. 

    Again, note this is only for RAW mode serializers 913A and 933. None of this applies to CSI-2 type serializers such as 953, 935, etc. For CSI-2 serializers the 960 does not change the data type in the packet header. 

    Best Regards,

    Casey