• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 898 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.

CCS/J6EVM5777: camera OV10635 via FPD-LINK III interface

ALA BACCAR
Prodigy 155 points
Part Number: J6EVM5777
Other Parts Discussed in Thread: TVP5158, TFP410, TPD12S015

Tool/software: Code Composer Studio

Hi Texas Instruments,

what are the HAL camera changes (hardware / ti / dra7xx / camera) to test camera OV10635 sensor (Capturing through LVDS camera)
knowing that Linux kernel has driver for FPDlink serializers and deserializers(ti_fpd3_serdes) .         

Regards,
Ala

  • 0
    Prodigy 155 points

    Part Number: J6EVM5777

    Tool/software: Linux

    Any help please.

  • 0 in reply to ALA BACCAR
    TI__Intellectual 2440 points

    Hi Ala,

    Please try this patch to disable the resolution check:

    http://review.omapzoom.org/#/c/38614/ or edit the resolution in camera/V4LCameraAdapter/V4LCapabilities.cpp

    -const char V4LCameraAdapter::DEFAULT_PREVIEW_SIZE[] = "640x480";
    +const char V4LCameraAdapter::DEFAULT_PREVIEW_SIZE[] = "1280x720";

    This should enable use of the OV10635 sensor, though I believe it may have incorrect colors. I believe the issue is that the output ends up as NV21 instead of NV12, though I'm not sure of that. I'll follow up on the color issue.

    Thanks,

    David

  • 0 in reply to David Huang
    Prodigy 155 points
    Hi David


    I did a command on this camera OV1365
    You can see the link :
    store.d3engineering.com/.../

    while waiting for this COMMAND :

    first: I activated the kernel module fpdlink: "ti_fpd3_serdes "
    you can see output:

    jacinto6evm:/ # lsmod
    Module Size Used by
    pvrsrvkm 288948 48
    snd_soc_tlv320aic3x 48807 2
    gpio_pca953x 9709 0
    tvp5158 7072 1
    ov490 5014 0
    ov1063x 14068 0
    ldc3001_ts 4718 0
    goodix 9068 0
    input_polldev 4492 1 goodix
    edt_ft5x06 11534 0
    pwm_bl 4714 0
    led_bl 2991 0
    gpio_backlight 2844 0
    leds_tlc591xx 5019 1
    panel_dpi 4046 1
    connector_dvi 3916 0
    connector_hdmi 4197 1
    ti_fpd3_serdes 8523 0
    encoder_tfp410 3490 0
    encoder_tpd12s015 3933 0
    encoder_tc358768 5932 1
    dra7_evm_encoder_tpd12s015 5442 1
    sd_mod 31226 0
    usb_storage 48124 0
    scsi_mod 164778 2 sd_mod,usb_storage
    wlcore_sdio 6907 0
    wl18xx 85776 0
    wlcore 183653 1 wl18xx


    Second : I'm doing the implementation of cameraHAL to connect it with camera2 framework.

    Am I in the right solution ?

    Thanks,
    Ala
  • 0 in reply to ALA BACCAR
    TI__Intellectual 2440 points

    Hi Ala,

    If you can, try to download and compile omapdrmtest: https://git.ti.com/glsdk/omapdrmtest

    There's an Android.mk so you should be able to compile it within AOSP, may have to push to system manually.

    On Android, you'll have to issue the following commands:

    su

    stop

    stop media

    dmabuftest -c 1280x720@YUYV -d /dev/video1 -s 32:1920x1200

    You may need to change the options on the dmabuftest commands to fit your system. 

    The -c is 720x240 since we're taking interlaced 720x480 video, which means each frame is vertically halved.

    -d gives the video device node (vip1-s0). May need to be another video node

    -s sets the output. You should be able to find what display you're using via the modetest (In my example my display was crtc 32)

    Thanks,

    David

  • 0 in reply to David Huang
    Prodigy 155 points
    Hi David

    thanks for your information.

    Regards
    Ala