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.

TDA3XEVM: Vision SDK 3.1: How can I easily change the sensor from OV10640 to OV10635 using the same hardware interface of the RVP

Part Number: TDA3XEVM

Hello,

how can I change easily the sensor type in the demonstration software? I'm using the RVP which has the OV10640 as video sensors. For our own development we have to use the OV10635 with exactly the same interface connection (MIPI CSI-2) and I2C via CSI2 to control the sensor.

I see, that the FVID2 supports the required OV10635 sensor and I also saw that this sensor is still used in the non ISS-usecases, but I'm not confident on how it is meant to tell the VSDK system using this sensor in the given ISS usecases. 

In case of the OV10640 sensor I also saw, that there is a mode containing the letters "IMI" which seems having to do with the I2C interface. Is that the mode, which I need for stupid sensors, that require their setup by I2C commands send over MIPI CSI2? I'm a little bit confused about what I need. 

Thanks a lot in advance for helping me!

Regards,

Guenter

  • Hi Guenter,

    ISS Usecases are supported for the RAW-Bayer sensors. One of them is OV10640.
    OV10635 is YUV sensor and is not supported for ISS usecase. You could other non-ISS usecases for OV10635 sensor.
    IMI is module, which contains OV10640 sensor and UB913 serializer.

    Regards,
    Brijesh
  • Hi Brijesh,

    thanks for your fast reply. I thought, that I can use the ISS for all sensors connected to the LVDS interface of the TDA3x and that is not only for Raw-Bayer sensors. I understood, that the other usecases, especially those which are for the OV10635 are only for the parrallel VIP interface.

    Is that totally wrong ???

    But now I have the situation, that I have an OV10635, which uses a UB914 serializer and is connected to the RVP's serial CSI-2 port. That means I have to send the sensor control via the same way the OV10640 gets its settings and I get the video data also over this way.

    For my understanding I have to tell the system that it has to use the TDA3x's CSI-2 port instead of the parallel VIP. And so I'm trying to find a way how to tell this the system.

    But nevertheless your answer was helpful in that way, that I know now, that I cannot use any of the given ISS usecases for our sensor and that the remaining usecases also do not work with our camera without any further software adaptions.

    I have to think about how to handle this problem in a way which is compliant to the VSDK.

    Regards,
    Guenter