• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 99 subscribers
  • Views 2470 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.

Camera connectivity on OMAP4470 blaze tablet with 4AJ1.1.

mayank jain3
Prodigy 50 points

Hii..

I've flashed JB 4.1.1 image on OMAP 4470 blaze tablet platform. The Release code reference used is:

http://www.omappedia.com/wiki/4AJ.1.1_OMAP4_Jelly_Bean_Release_Notes

Initially everything was working perfectly well. I was able to access Camera. But suddenly I am encountering some issues while accessing camera.

When turning on the CameraOMAP7740 App, a message stating "Unable to connect to camera" pops up.

The logcat file is attached alongwith the post for reference.

I've tried executing the following command:

am start –a android.intent.action.MAIN –n com.android.camera/com.android.camera.Camera

The terminal output is as given below:

Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] pkg=–a }
Error: Activity not started, unable to resolve Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=–a }

Please help me to resolve the issue.

Regards,

Mayank

  • 0
    TI__Mastermind 29520 points

    Hello Mayank,

    My first suggestion is for checking if Ducati-m3.bin is available in the path /system/vendor/firmware/
    Could you try to flash your Blaze tablet with pre-built binaries available in the link:

    http://www.omappedia.com/wiki/Android:_Working_with_pre-built_binaries

    Best regards,

    Yanko

  • 0 in reply to Yanko Todorov-XID
    Prodigy 50 points

    Hi Yanko,

    Thank you for your prompt reply.

    First of all I've checked with the path /system/vendor/firmware/.  Ducati-m3.bin is present there.

    Secondly, as suggested by you, I've flashed the Blaze tablet pre-built binary from the link given above. Unfortunately the issue persists. So I guess there is no problem with the Ducati-m3.bin file.

    I've also checked for existence of camera tuning related DCC files.

    The terminal output is as follows:

    root@android:/ # ls -l /data/misc/camera
    drwxrwx--- media media 2000-01-02 00:15 R5_MVEN003_LD2_ND0_IR0_SH0_FL1_SVEN003_DCCID1044

     

    While searching for some help on this issue, I found out that CameraHal should be loaded and num_cameras should not be 0. But in the logcat file, I cannot find the following command:

    E/CameraHal(  126): num_cameras =

    So I guess maybe some issue on that part. I'm attaching the log file for your reference.

    Kindly help.

    Best regards,

    Mayank

  • 0 in reply to mayank jain3
    TI__Mastermind 29520 points

    Hello Mayank,

    Please search for source files inside the folder

    hardware/ti/omap4xxx/camera/OMXCameraAdapter/

    Camera driver is not V4L or ISS (not sure what it means). The driver is based on OMX.

    I suggest you to see following link:

    https://gitorious.org/omap4-v4l2-camera/pages/Home

    The supported sensors for TI designs are:

    Sony IMX060 - 12MP RAW sensor

    Omnivision OV5650 - 5MP RAW sensor

    Omnivision OV5640 - 5MP smart sensor

    Omnivision OV14825 - 14MP RAW sensor

    What is the camera connected to your Blaze board?

    Please see Gstreamer configuration - http://www.ti.com/tool/gstreamer

    Best regards,

    Yanko

  • 0 in reply to Yanko Todorov-XID
    Prodigy 50 points

    Hello Yanko,

    Sorry for the inconvenience. The logcat file which I've updated earlier had some build issues because of which CameraHal was not loaded.

    Now I've resolved the issue. The CameraHal is now being loaded but still the camera is not working. It shows num_cameras=0, which I suppose should not be 0. I've attached the correct log file for your reference.

    Also the camera sensor connected to blaze board is:

    Omnivision OV5650 - 5MP RAW sensor

    I found the following traces in ducati log file:

    [ 0.000] Watchdog enabled: TimerBase = 0xa8088000 Freq = 38400000
    [ 0.000] Watchdog_restore registered as a resume callback
    [ 0.000] [MNU=0] src/mmsw_platform.c:[305]:
    [ 0.000]
    [ 0.000] ***DUCATI VERSION INFO***
    [ 0.000] Compile DATE Aug 29 2012 TIME 17:46:24
    [ 0.000] GIT ducati_mmlegacy
    [ 0.000] BRANCH:(no branch) TAG:DUCATIMM-2.1.15
    [ 0.000] COMMIT-ID:9491160
    [ 0.000] CODEC-VER BEGIN:
    [ 0.000] H264D-01.00.00.11
    [ 0.000] MPEG4D-01.00.09.00
    [ 0.000] MPEG2D-01.00.09.00
    [ 0.000] VC1D-01.00.00.04
    [ 0.000]
    [ 0.000] H264E-01.00.05.00
    [ 0.000] MPEG4E-01.00.00.04
    [ 0.000] CODEC-VER END:
    [ 0.000] GIT OMAPHWA_Algorithm:: 4230069
    [ 0.000] GIT OMAPHWA_Drivers:: 69638d1
    [ 0.000] ***DUCATI VERSION INFO***
    [ 0.001]
    [ 0.001]
    [ 0.001] [MNU=1] src/mmsw_platform.c:[307]:Processor family detected: OMAP4470_ES1_0
    [ 0.001] [MNU=2] src/mmsw_platform.c:[309]:
    [ 0.001]
    [ 0.001] Trace Buffer PA 0xb2970000
    [ 0.001]
    [ 0.001] Trace Usage::
    [ 0.001] level:[1-5: err-1, warn-2, info]
    [ 0.001] groups:[simcop|driver|imgdec|cam|viddec|videnc|domx|base|system]
    [ 0.001] traceLevel 0x2 traceGroups 0xffffffff,
    [ 0.001] traceLevel PA 0xb353e194 traceGroups PA 0xb353e174
    [ 0.001]
    [ 0.002] OMAPRPC: registered channel: dvp_kgm_simcop
    [ 0.004] OmxSrvMgr: started on port: 60
    [ 0.004] registering rpmsg-omx1 service on 60 with HOST
    [ 0.004] OmxSrvMgr: Proc#2 sending BOOTINIT_DONE
    [ 0.004] [t=0x00230be9] ti.ipc.rpmsg.MessageQCopy: MessageQCopy_send: no object for endpoint: 53
    [ 0.005] OMAPRPC: connecting from local endpoint 59 to port 59
    [ 0.005] registering omaprpc service on 59 with HOST
    [ 0.005] OMAPRPC: started channel on port: 59
    [ 0.033] OMAPRPC: received msg type: 9 len: 12 from addr: 1025
    [ 0.033] OMAPRPC: channel info query - name dvp_kgm_simcop
    [ 0.033] OMAPRPC: Replying with msg type: 10 to addr: 1025 from: 59 len: 76
    [ 0.875] OmxSrvMgr: received msg type: 0 from addr: 1026
    [ 0.875] OmxSrvMgr: CONN_REQ: len: 4, name: OMX
    [ 0.875] createService: new OMX Service at endpoint: 101
    [ 0.875] OmxSrvMgr: Replying with msg type: 1 to addr: 1026 from: 60
    [ 0.876] [ERR=3] src/omx_core.c:[136]:
    [ 0.876] ====
    [ 0.876] RPMSG Trace log Buffer A9 Address: 0xb2970000
    [ 0.876] ====
    [ 0.877] [ERR=4] src/omx_iss_cam.c:[360]:##### Processor family detected: OMAP4470_ES1_0 #####
    [ 0.879] [MNU=5] rm_plugin_res/src/rm_pluginpower_resource.c:[608]:Requesting ISS resource from IPC ResMgr
    [ 0.880] [MNU=6] rm_plugin_res/src/rm_pluginres_iss.c:[127]:User requested ISS Mhz:200
    [ 0.880] [MNU=7] rm_plugin_res/src/rm_pluginres_iss.c:[131]:Request:: Setting ISS Mhz:200
    [ 0.880] [MNU=8] rm_plugin_res/src/rm_pluginpower_resource.c:[1445]:[ISS]: Succesfull Request of Mhz constraints
    [ 0.880] [MNU=9] rm_plugin_res/src/rm_pluginres_iss.c:[136]:User requested ISS Latency:10
    [ 0.880] [MNU=10] rm_plugin_res/src/rm_pluginres_iss.c:[140]:Request:: Setting ISS Latency:10
    [ 0.881] [MNU=11] rm_plugin_res/src/rm_pluginpower_resource.c:[1459]:[ISS]: Succesfull request of latency constraints
    [ 0.881] [MNU=12] rm_plugin_res/src/rm_pluginres_ipu.c:[137]:User requested IPU[1] Mhz:200
    [ 0.882] [MNU=13] rm_plugin_res/src/rm_pluginres_ipu.c:[141]:Request:: Setting IPU[1] Mhz:200
    [ 0.882] [MNU=14] rm_plugin_res/src/rm_pluginres_ipu.c:[146]:User requested IPU[1] Latency:10
    [ 0.882] [MNU=15] rm_plugin_res/src/rm_pluginres_ipu.c:[150]:Request:: Setting IPU[1] Latency:10
    [ 0.882] [MNU=16] rm_plugin_res/src/rm_pluginpower_resource.c:[1356]:[IPU]: Succesfull request of latency constraints
    [ 0.882] [MNU=17] rm_plugin_res/src/rm_pluginres_l3bus.c:[116]:User requested L3BUS BW:1000
    [ 0.882] [MNU=18] rm_plugin_res/src/rm_pluginres_l3bus.c:[120]:Request:: Setting L3BUS BW:1000
    [ 0.883] [MNU=19] rm_plugin_res/src/rm_pluginpower_resource.c:[1368]:[IPU]: Succesfull request of BW Constraints
    [ 0.883] [MNU=20] rm_plugin_res/src/rm_pluginpower_resource.c:[1387]:[L3BUS]: Succesfull request of BW constraints
    [ 0.885] [ERR=21] src/sensor_detect_MSP.c:[303]:0>>:OV5650 Socket:0
    [ 0.885] [ERR=22] src/sensor_detect_MSP.c:[303]:1>>:AD5820 Socket:0
    [ 0.885] [ERR=23] src/sensor_detect_MSP.c:[303]:2>>:CSI2 Socket:0
    [ 0.886] [ERR=24] src/sensor_detect_MSP.c:[303]:0>>:OV5650 Socket:1
    [ 0.886] [ERR=25] src/sensor_detect_MSP.c:[303]:1>>:AD5820 Socket:1
    [ 0.886] [ERR=26] src/sensor_detect_MSP.c:[303]:2>>:CSI2 Socket:1
    [ 0.887] [ERR=27] src/omx_iss_cam.c:[674]:
    [ 0.887] ====
    [ 0.887] Profiler Buffer A9 Dump Address: 0xb3587940, Size:65536 bytes
    [ 0.887] ====
    [ 0.887] [ERR=28] src/msp_mem_mngr.c:[366]:Mem_mngr Successfully created. MEM_MNGR address: 85c2c948
    [ 0.887] [ERR=29] src/config/omx_config/configs/omx_configs_custom.c:[2722]:
    [ 0.887] OMX_ConfMngPlugin_SetToDefault_TiCamConfigs_COMP_MipiCounters_CUSTOM called.
    [ 0.887]
    [ 0.887] [ERR=30] src/config/omx_conv/configs/conv_omx_configs_fxns.c:[2410]:OMX_SetConfig(AlgoAreas) bad parameter: shared buffer is NULL pointer. Nothing to set.
    [ 0.887] [ERR=31] src/config/omx_conv/params/conv_omx_params_fxns.c:[370]:VTC Slice configured to 0 height!
    [ 0.887] [ERR=32] src/config/omx_conv/params/conv_omx_params_fxns.c:[377]:#0 VTC buffers for ISP: Y:0x0 UV:0x0, Y:0x0 UV:0x0, Y:0x0 UV:0x0
    [ 0.887]
    [ 0.887] [ERR=33] src/config/omx_conv/params/conv_omx_params_fxns.c:[379]:VTC Slice information is received by ducati
    [ 0.887]
    [ 0.887] [ERR=34] src/config/omx_conv/params/conv_omx_params_fxns.c:[387]:VTC Slice configured along with Buffer Configuration!
    [ 0.889] [ERR=35] src/omx_iss_cam_usecase_manager.c:[426]:
    [ 0.889]
    [ 0.889] ##### PPM: Opened MSP.OMX_CAM.UC.DUMMY usecase.
    [ 0.892] [ERR=36] src/omx_iss_cam_usecase_manager.c:[410]:
    [ 0.892]
    [ 0.892] ##### PPM: Closed MSP.OMX_CAM.UC.DUMMY usecase.
    [ 0.941] [ERR=37] src/new_sensor_MSP.c:[1177]:Sen Read ID: 0, expected ID:22097
    [ 0.941]
    [ 0.941] [ERR=38] src/new_sensor_MSP.c:[1185]:
    [ 0.942] Error in src/new_sensor_MSP.c, line:1185
    [ 0.942]
    [ 0.985] [ERR=39] src/new_sensor_MSP.c:[1177]:Sen Read ID: 0, expected ID:22080
    [ 0.985]
    [ 0.985] [ERR=40] src/new_sensor_MSP.c:[1185]:
    [ 0.985] Error in src/new_sensor_MSP.c, line:1185
    [ 0.985]
    [ 1.029] [ERR=41] src/new_sensor_MSP.c:[1177]:Sen Read ID: 0, expected ID:59408
    [ 1.029]
    [ 1.029] [ERR=42] src/new_sensor_MSP.c:[1185]:
    [ 1.030] Error in src/new_sensor_MSP.c, line:1185
    [ 1.030]
    [ 1.046] [ERR=43] src/new_sensor_MSP.c:[1177]:Sen Read ID: 0, expected ID:96
    [ 1.047]
    [ 1.047] [ERR=44] src/new_sensor_MSP.c:[1185]:
    [ 1.047] Error in src/new_sensor_MSP.c, line:1185
    [ 1.047]
    [ 1.048] [ERR=45] src/sensor_detect_MSP.c:[271]:On Socket:0 Sensor no detected
    [ 1.095] [ERR=46] src/new_sensor_MSP.c:[1177]:Sen Read ID: 0, expected ID:22097
    [ 1.095]
    [ 1.095] [ERR=47] src/new_sensor_MSP.c:[1185]:
    [ 1.095] Error in src/new_sensor_MSP.c, line:1185
    [ 1.095]
    [ 1.138] [ERR=48] src/new_sensor_MSP.c:[1177]:Sen Read ID: 0, expected ID:22080
    [ 1.138]
    [ 1.138] [ERR=49] src/new_sensor_MSP.c:[1185]:
    [ 1.138] Error in src/new_sensor_MSP.c, line:1185
    [ 1.138]
    [ 1.180] [ERR=50] src/new_sensor_MSP.c:[1177]:Sen Read ID: 0, expected ID:59408
    [ 1.180]
    [ 1.180] [ERR=51] src/new_sensor_MSP.c:[1185]:
    [ 1.181] Error in src/new_sensor_MSP.c, line:1185
    [ 1.181]
    [ 1.196] [ERR=52] src/new_sensor_MSP.c:[1177]:Sen Read ID: 0, expected ID:96
    [ 1.196]
    [ 1.196] [ERR=53] src/new_sensor_MSP.c:[1185]:
    [ 1.196] Error in src/new_sensor_MSP.c, line:1185
    [ 1.196]
    [ 1.197] [ERR=54] src/sensor_detect_MSP.c:[271]:On Socket:1 Sensor no detected
    [ 1.197] [ERR=55] src/sensor_detect_MSP.c:[271]:On Socket:2 Sensor no detected
    [ 1.197] [ERR=56] src/camera_fw_core.c:[211]:
    [ 1.197] Error in src/camera_fw_core.c, line:211
    [ 1.197]
    [ 1.197] [ERR=57] src/camera_fw_MSP.c:[710]:
    [ 1.198] Error in src/camera_fw_MSP.c, line:710
    [ 1.198]
    [ 1.198] [ERR=58] src/msp_video.c:[1506]:
    [ 1.198] Error in src/msp_video.c, line:1506
    [ 1.198]
    [ 1.198] [ERR=59] src/msp_base_node_active.c:[1221]:
    [ 1.198] Error in src/msp_base_node_active.c, line:1221
    [ 1.198]
    [ 1.198] [ERR=60] src/msp_pipe_mngr.c:[936]:
    [ 1.198] Error in src/msp_pipe_mngr.c, line:936
    [ 1.198]
    [ 1.198] [ERR=61] src/msp_pipe_mngr.c:[1659]:
    [ 1.198] Error in src/msp_pipe_mngr.c, line:1659
    [ 1.198]
    [ 1.198] [ERR=62] src/msp_base_node_active.c:[1418]: BaseNodeActive: Invalid state
    [ 1.199] [ERR=63] src/msp_base_node_active.c:[1419]:
    [ 1.199] Error in src/msp_base_node_active.c, line:1419
    [ 1.199]
    [ 1.199] [ERR=64] src/omx_iss_cam_usecase_with_pipe_common.c:[3684]:
    [ 1.199] Error in src/omx_iss_cam_usecase_with_pipe_common.c, line:3684
    [ 1.199]
    [ 1.199] [ERR=65] src/omx_iss_cam_usecase_manager.c:[417]:
    [ 1.199] Error in src/omx_iss_cam_usecase_manager.c, line:417
    [ 1.199]
    [ 1.199] [ERR=66] src/msp_pipe_mngr.c:[1813]: PipeMngr: Invalid state
    [ 1.199] [ERR=67] src/msp_pipe_mngr.c:[1814]:
    [ 1.199] Error in src/msp_pipe_mngr.c, line:1814
    [ 1.199]
    [ 1.200] [ERR=68] src/omx_iss_cam_usecase_manager.c:[539]:
    [ 1.200] Error in src/omx_iss_cam_usecase_manager.c, line:539
    [ 1.200]
    [ 1.200] [ERR=69] src/omx_iss_cam_usecase_manager.c:[602]:
    [ 1.200] Error in src/omx_iss_cam_usecase_manager.c, line:602
    [ 1.200]
    [ 1.200] [ERR=70] src/conf_mng.c:[159]:
    [ 1.200] Error in src/conf_mng.c, line:159
    [ 1.200]
    [ 1.200] [ERR=71] src/omx_iss_cam.c:[958]:Failed check: eMSP == MSP_ERROR_NONE
    [ 1.200] [ERR=72] src/omx_iss_cam.c:[958]:Returning error: OMX_ErrorUndefined
    [ 1.200] [ERR=73] omx_rpc/src/omx_rpc_skel.c:[289]:Component returned error: 0x80001001
    [ 1.204] [ERR=74] src/omx_core.c:[257]:
    [ 1.204] ====
    [ 1.204] RPMSG Trace log Buffer A9 Address: 0xb2970000
    [ 1.204] ====
    [ 1.205] [MNU=75] rm_plugin_res/src/rm_pluginres_iss.c:[194]:User releasing ISS Mhz:200
    [ 1.205] [MNU=76] rm_plugin_res/src/rm_pluginres_iss.c:[197]:Release:: Setting ISS Mhz:0
    [ 1.206] [MNU=77] rm_plugin_res/src/rm_pluginpower_resource.c:[1445]:[ISS]: Succesfull Request of Mhz constraints
    [ 1.206] [MNU=78] rm_plugin_res/src/rm_pluginpower_resource.c:[1459]:[ISS]: Succesfull request of latency constraints
    [ 1.206] [MNU=79] rm_plugin_res/src/rm_pluginres_iss.c:[208]:Release:: Freeing ISS Mhz:0 before resource disable
    [ 1.206] [MNU=80] rm_plugin_res/src/rm_pluginpower_resource.c:[1638]:[ISS]: Succesfull Release of Mhz constraints
    [ 1.206] [MNU=81] rm_plugin_res/src/rm_pluginpower_resource.c:[1651]:[ISS]: Succesfull release of latency constraints
    [ 1.207] [MNU=82] rm_plugin_res/src/rm_pluginpower_resource.c:[1079]:Releasing ISS
    [ 1.207] [MNU=83] rm_plugin_res/src/rm_pluginres_ipu.c:[206]:User releasing IPU[1] Mhz:200
    [ 1.207] [MNU=84] rm_plugin_res/src/rm_pluginres_ipu.c:[209]:Release:: Setting IPU[1] Mhz:0
    [ 1.207] [MNU=85] rm_plugin_res/src/rm_pluginpower_resource.c:[1356]:[IPU]: Succesfull request of latency constraints
    [ 1.207] [MNU=86] rm_plugin_res/src/rm_pluginres_ipu.c:[220]:Release:: Freeing IPU[1] Mhz:0 before resource disable
    [ 1.208] [MNU=87] rm_plugin_res/src/rm_pluginpower_resource.c:[1546]:[IPU]: Succesfull release of latency constraints
    [ 1.208] [MNU=88] rm_plugin_res/src/rm_pluginres_l3bus.c:[169]:User releasing L3BUS BW:1000 MB/s
    [ 1.208] [MNU=89] rm_plugin_res/src/rm_pluginres_l3bus.c:[172]:Release:: Setting L3BUS BW:0 MB/s
    [ 1.208] [MNU=90] rm_plugin_res/src/rm_pluginpower_resource.c:[1368]:[IPU]: Succesfull request of BW Constraints
    [ 1.208] [MNU=91] rm_plugin_res/src/rm_pluginpower_resource.c:[1387]:[L3BUS]: Succesfull request of BW constraints
    [ 1.208] [MNU=92] rm_plugin_res/src/rm_pluginres_l3bus.c:[178]:Release:: Freeing L3BUS BW:0 MB/s before resource disable
    [ 1.209] [MNU=93] rm_plugin_res/src/rm_pluginpower_resource.c:[1558]:[IPU]: Succesfull request of BW Constraints
    [ 1.209] [MNU=94] rm_plugin_res/src/rm_pluginpower_resource.c:[1577]:[L3BUS]: Succesfull release of BW constraints
    [ 1.209] [WAR=95] bios6/src/timm_osal_task.c:[191]:Task omx.iss_cam is in ready state, will wait for task to terminate before deleting
    [ 1.210] [ERR=96] src/omx_iss_cam.c:[1316]:Memory leak detected. Bytes lost = 4135812
    [ 1.210] [ERR=97] src/omx_iss_cam.c:[1317]: Value from GetMemCounter = 68
    [ 1.210] [ERR=98] src/omx_iss_cam.c:[1318]: Value from GetMemUsage = 4192332
    [ 1.210] [ERR=99] src/omx_iss_cam.c:[1321]:Total size = 6291456
    [ 1.210] [ERR=100] src/omx_iss_cam.c:[1322]:Total free size = 6100352
    [ 1.210] [ERR=101] src/omx_iss_cam.c:[1323]:Largest Free size = 5924280
    [ 1.210] [ERR=102] src/omx_iss_cam.c:[1324]:
    [ 1.211] [ERR=103] src/omx_iss_cam.c:[1325]:-----------------------------------------------
    [ 1.211] [ERR=104] src/omx_iss_cam.c:[1326]:
    [ 1.211] [MNU=105] src/omx_core.c:[280]:
    [ 1.211]
    [ 1.211] Trace Buffer PA 0xb2970000
    [ 1.211]
    [ 1.211] Trace Usage::
    [ 1.211] level:[1-5: err-1, warn-2, info]
    [ 1.211] groups:[simcop|driver|imgdec|cam|viddec|videnc|domx|base|system]
    [ 1.211] traceLevel 0x2 traceGroups 0xffffffff, kpi_control 0x0
    [ 1.211] traceLevel PA 0xb353e194 traceGroups PA 0xb353e174, kpi_control PA 0xb34dda98
    [ 1.212]
    [ 1.212] OmxSrvMgr: received msg type: 4 from addr: 1026
    [ 1.212] OmxSrvMgr: OMX_DISCONNECT: len 4, addr: 101
    [ 1.213] RcmServer_serverThrFxn_P: Exiting thread.
    [ 1.213] deleteService: removed RcmServer at endpoint: 101

    Best Regards,

    Mayank

  • 0 in reply to mayank jain3
    TI__Mastermind 29520 points

    Hello Mayank,

    Do you have a driver file for OV5650 - drivers/media/video/ov5650.c and include/media/ov5650.h

    https://www.gitorious.org/omap4-v4l2-camera/omap4-v4l2-camera/source/4fef45fed2d522090b9fd4b5049096b0e8a1875b:drivers/media/video/ov5650.c#L502

    https://android.googlesource.com/kernel/tegra/+/c3f125ab692f1d80b7fd71c2ccfe8b8ab79b5017/drivers/media/video/tegra/ov5650.c

    Could you check if OV5650 is defined in drivers/media/video/Kconfig?

    Example:

    comment "Camera sensor devices"

    config VIDEO_OV5650
        tristate "OmniVision OV5650 sensor support"
        depends on I2C && VIDEO_V4L2
        ---help---
          This is a Video4Linux2 sensor-level driver for the OmniVision
          OV5650 VGA camera.  It currently only works with the M88ALP01
          controller.

    Could you check if OV5650 is defined in drivers/media/video/Makefile?

    obj-$(CONFIG_SOC_CAMERA_OV5650)        += ov5650.o

    In the end:

    I suggest you to add in board-4430sdp.c OV5650 definitions, described in this link:

    https://gitorious.org/omap4-v4l2-camera/omap4-v4l2-camera/source/9bc389d8a8fc8860e9e5de38dc46677048523b7f:arch/arm/mach-omap2/board-4430sdp-camera.c

    omap2plus: Add support for omap4iss camera support for following sensors: - OV5640 - OV5650

    https://gitorious.org/omap4-v4l2-camera/omap4-v4l2-camera/commit/da3d3a03b2d1fb8a6506846e698f04e7b1eabd18

    Best regards,

    Yanko

  • 0 in reply to Yanko Todorov-XID
    TI__Mastermind 24525 points

    Yanko,

    Since he is using Ducati based camera, he does not need V4L2 support.

    Mayank,

    Please confirm which camera you are plugging into the tablet. There are two ports, please to switch the camera to another port and restart.

    Regards,

    Mayank

  • 0 in reply to Mayank Mangla
    Prodigy 50 points
    Hi MayankMangla,

    We have used ducati-m3.bin for camera module. "ducati-m3.bin" was given by our client.
    with this .bin, "camera test_f" also failed. We have only one camera with cameraId as "0", which is causing the error in camera launch/start. (CameraService.cpp file) during camera::connect - mNumberofCameras is zero.
    We dont have any idea why "mModule->get_numberof_cameras()" returning zero to mNumberofCameras.

    As per Yanko's suggestion, we may also not require the V4L2 support ?
    please confirm the same.
    Thanks in advance.

    -Mayank
  • 0 in reply to mayank jain3
    TI__Mastermind 24525 points
    If you are planning to use OMX camera you don't need V4L support. ducati-m3.bin has support for a limited number of camera sensors. If you have the same sensor on your board and GPIO, I2C etc is identical then only ducati-m3.bin will work for you. Otherwise you will need to get access to Ducati source code and add driver for the sensor you are using.