Using a different sensor with the camera_mipi example

Hi,

We're currently evaluating the 11x11 kit with the KL720.

We're trying to modify the camera_mipi example from the 1.5.0 SDK and use a different sensor (OV9281).

The example lists the GC2145 and SC132GS as the sensors this example was designed for.


We changed the register settings and when monitoring the I2C communication via console we see that it is being received and the sensor enters a 640x480 30fps mode.

We are getting callbacks in myCamera_image_callback as expected, but when we dump one of the 2 buffers to a hex file and plot it using python, we don't get any recognizable image, only noise. We parse it using a python Intel Hex package and plot a 640x480 image. Even a test pattern sent from the sensor looks mostly like noise.

We didn't receive any other sensor with the kit, so we have no way of performing a sanity check.

Is there any documentation on how to integrate new sensors? do we need to change any special settings? how do we debug this issue?


Thanks!

Tagged:

Comments

  • Hi, we have contacted you via email.

    Here we still record some general solution in case other people have the same question.


    Is there any documentation on how to integrate new camera sensors?

    You can see the ToF ppt and set the clock.

    Do we need to change any special settings?

    In ToF case, we need to know :

    (1)  the frequency of mipi clock to determine the pll setting

    (2)  check if the content in CSIRX and D2A are correct in project.h

    (3)  The sequence of MIPI waveforms must be confirmed to meet the specification

    How would you suggest debugging this issue?

    You can see the reference ”mipiSpec_error_status _reg.pdf”

    If the content is set incorrectly in project.h, there will be related error status in csirx.

     Thanks!

The discussion has been closed due to inactivity. To continue with the topic, please feel free to post a new discussion.