• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 109 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.

AM62A3: Driver for OS02C10 camera sensor

shaik adnan pasha
Prodigy 45 points
Part Number: AM62A3

Tool/software:

Hi Team,

We are currently developing a camera module based on the AM62A32AOMHIAMBR processor and are using the OS02C10 image sensor.

While attempting to integrate the driver for this sensor, we could not locate an existing supported driver in the SDK. We reached out to the camera module vendor, but they advised us to seek support from the platform provider for driver integration.

We are using the Linux SDK for Edge AI, version 09.01.00.07, and would appreciate your guidance or support in obtaining or integrating the OS02C10 camera driver for this platform.

Looking forward to your assistance.

Thanks,

  • 0
    TI__Guru 59025 points

    Hello,

    We do not have a Linux driver for OS02C10. My recommendations to develop the driver are:

    1. look at existing sensor drivers in the SDK you have, under drivers/media/i2c, for a template of V4L2 compliant driver. Especially you can look at Omnivision sensor drivers, such as ovxxxx.c.

    2. contact Ominivision for register setting for the specific sensor you're going to use.

    Regards,

    Jianzhong

  • 0 in reply to Jianzhong Xu
    Prodigy 45 points

    Hello,

    Thank you for your input.

    We are currently working with Omnivision, and they have shared complete register settings documentation for the OS02C10 sensor. As part of our integration process, we had asked them to suggest which of the existing OV-series sensor drivers in our SDK would be the closest match to the OS02C10. Our intent was to use such a driver as a base to minimize development effort and accelerate initial bring-up.

    However, their response was that the sensors listed below are either very old, possibly EOL parts, or belong to different market segments:

    Existing OV-Series Sensor Drivers in TI SDK:

    ov02a10.c  ov13b10.c  ov2659.c  ov2740.c  ov5647.c  ov5675.c  ov6650.c  ov7670.c  ov8856.c  ov9640.c
    ov08d10.c  ov2312.c   ov2680.c  ov5640.c  ov5648.c  ov5693.c  ov7251.c  ov772x.c  ov8865.c  ov9650.c
    ov13858.c  ov2640.c   ov2685.c  ov5645.c  ov5670.c  ov5695.c  ov7640.c  ov7740.c  ov9282.c  ov9734.c

    I am considering using the ov02a10.c driver as a reference base for our custom driver development, since it appears to be in the same resolution range and possibly shares structural similarities.

    Do you have any input or recommendations on this approach?

    Can we expect any assistance or technical review from TI during the development phase of this driver?

    Regards,
    Adnan

  • 0 in reply to shaik adnan pasha
    TI__Guru 59025 points

    Hi Adnan,

    shaik adnan pasha said:
    However, their response was that the sensors listed below are either very old, possibly EOL parts, or belong to different market segments:

    Then I would recommend to look at a relatively new driver to learn about the V4L2 framework API. The IMX728 driver can be a good reference for the API. You can follow the example driver to write the necessary API functions required by V4L2 and then just fill in OS02C10 register settings.

    shaik adnan pasha said:
    Can we expect any assistance or technical review from TI during the development phase of this driver?

    Unfortunately, we do not provide driver review support. 

    Regards,

    Jianzhong