• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 97 subscribers
  • Views 268 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.

TDA2PXEVM: AR0233 Camera Sensor Integration for TDA2P

Dipti Natu
Intellectual 700 points

Part Number: TDA2PXEVM

Hello,

We are integrating AR0233 sensor in VisionSDK using TDA2P. We are using Maxim SERDES along with the sensor.
Specifications of Input sensor are as follows:
  1. Resolution : 1920 * 1080 at 60 fps
  2. Data format : RGB Bayer RAW 12 bit
  3. MIPI 4 lanes 
Settings done in init() function of sensor.c file are as follows : 
The interface information for the sensor is as follows : 
Input image received with this settings is as follows : We dumped the RAW image from usecase and tried to visualise it : 
Can you tell us if any modifications are need in the settings, to receive correct data from sensor?
We would like to know if csi2PhyClk parameter setting done in interface_info structure is corrrect and how this value results in certain frequency for CSI interface.
Thanks,
Dipti
  • 0
    TI__Guru**** 500825 points

    Dipti,

    I am not able to view captured image. Can you please share it on the forum? 

    If you are able to capture it and view it without any artifacts, capture seems to be fine.. 

    CSI2PhyClk will depend on the deserializer output lane speed, so please check with Maxim what is the output lane rate.

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Intellectual 700 points

    Hello Brijesh,

    With the settings mentioned for sensor and interface information structure following is the image received :

    According to the Deserialiser settings the output is set to 4 lanes with 700 MHz . What should be the value according to this for our CSI2PhyClk. Currently it is  CSI2PhyClk = 800 in sensor interface info structure.

    I would like to know the relation of Deserialiser lane rate and CSI2PhyClk to be set.

    Thanks,

    Dipti

  • 0 in reply to Dipti Natu
    TI__Guru**** 500825 points

    Dipti,

    Lane rate is typically specific in terms of Mbps and clock is exactly half of lane rate in Mbps. So if deserializer outputting at 700MHz/1.4Gbps, then CSI2PHyClk should be set to 700. 

    Looking at the picture, not clear though, it seems that data is getting overwritten or multiple frames are getting merged into single frame in the camera due to some incorrect configuration. Can you check both of these items?

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Intellectual 700 points

    Hello Brijesh,

    Understood the relation of CSI2PHyClk with Deserialiser lane rate. I set the CSI2PHyClk parameter to 700 and now the output image issue is resolved. This is the output image we get now is sometimes correct and some times is distorted. Following is the yuv image dumped after ISP link  : 


    At the end few rows we can still some incorrect data. Some more investigation will be needed. 

    In case you feel we are missing anything from the details I have shared, please let us know.

    Thanks,

    Dipti

  • 0 in reply to Dipti Natu
    TI__Guru**** 500825 points

    Dipti,

    It looks like AR0233 is sending some extra lines or some meta/embedded data. See if it can be disable or you could trim off them in the capture, by slightly reducing height. 

    Regards,

    Brijesh