• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 100 subscribers
  • Views 1094 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.

Blaze Tablet Camera Issue

Johnny
Intellectual 585 points

Hi ,

    I try to connect the sensor OV2655 to OMAP4430,but it  failed ! I refered to that  TI provided documents (OPBU_L27_IS_2_M1_Release_Notes.doc and swpa199_Camera Sensor Adaptation on Ducati.pdf ) ,add OV2655 ,

Among the ov2665 driver code, we only modified

ov2655.c/ov2655_activate() to add a s/w reset and reg initialization, everything else simply returns MSP_ERROR_NONE.

One more note, the power seq and ECLK is done on A9 side,  cat log :

shell@android:/ $ cat /d/remoteproc/omap-rproc.1/trace1

[      0.000] DEH: Watchdog started

[      0.000] [MNU=0] src/mmsw_platform.c:[294]:

[      0.000]

[      0.000]  ***xiaohua.chen DUCATI VERSION INFO***

[      0.000] Compile DATE Jul  2 2012 TIME 11:37:17

[      0.000] GIT ducati_mmlegacy

[      0.000]          BRANCH: TAG:fatal: Not a git repository (or any

parent up to mount parent /media)

[      0.000]          COMMIT-ID:fatal:

[      0.000] CODEC-VER BEGIN:

[      0.000]

[      0.000]

[      0.000]

[      0.000]

[      0.000]

[      0.000]

[      0.000]

[      0.000] CODEC-VER END:

[      0.000] GIT OMAPHWA_Algorithm::

[      0.000] GIT OMAPHWA_Drivers::

[      0.000] ***DUCATI VERSION INFO***

[      0.001]

[      0.001]

[      0.001] [MNU=1] src/mmsw_platform.c:[296]:Processor family detected:

OMAP4430_ES2_3

[      0.004] serviceMgr: started on port: 60

[      0.004] registering rpmsg-omx service on 60 with HOST

[      0.004] [t=0x0019e49d] ti.ipc.rpmsg.MessageQCopy: MessageQCopy_send:

no object for endpoint: 53

shell@android:/ $

it seems there was no executive camera detection,and also to not execute below function

/omx/omx_il_1_x/omx_iss_cam/src/omx_iss_cam.c/OMX_TI_Camera_ComponentInit()

TIMM_OSAL_ErrorExt(TIMM_OSAL_TRACEGRP_SYSTEM, "##### Processor family

detected: %s ##### ", tools_omap_revision_print());

drivers/new_CAMERA/sensor_detect_drv/src/sensor_detect_MSP.c/MSP_SENSORDETEC

T_query()

TIMM_OSAL_ErrorExt(TIMM_OSAL_TRACEGRP_DRIVERS, "%d>>:%s Socket:%d", j, tSD[i].tData.ppSenName[j], (int)i);

  • 0
    TI__Mastermind 24525 points

    It appears that camera descriptor needs to be fixed.

    Please note that Ducati is not open source SW and can not be discussed in detail on this forum. Contact your TI representative for more help.

    Please also refrain from quoting parts of Ducati code on this forum.

  • 0 in reply to Mayank Mangla
    Intellectual 585 points

    Hi Mayank

    sorry ,The next time I not do so. ov2655 camera descriptor refer to ov5640 descriptor modify.and would you give me extra suggestion,thanks !

  • 0 in reply to Johnny
    TI__Mastermind 24525 points

    If you have fixed  the camera descriptor, you will be able to get I2C communication working with the sensor and SensorDetect should be passing.

    Once this is done, all you need to do is get the right sensor settings and set the parameters in modeConfig as specified in the sensor adaptation guide.

  • 0 in reply to Mayank Mangla
    Intellectual 585 points

    Hi Mayank,

          Now ,we can get I2C communication working and detect sensor ,and we had set the parameters in modeConfig ,but when we boot that it waiting one service overtime

    I/ServiceManager(  190): Waiting for service media.audio_policy...
    I/ServiceManager(  190): Waiting for service media.audio_policy...
    I/ServiceManager(  190): Waiting for service media.audio_policy...
    I/ServiceManager(  190): Waiting for service media.audio_policy...
    I/ServiceManager(  190): Waiting for service media.audio_policy...
    W/AudioSystem(  190): AudioPolicyService not published, waiting...
    I/ServiceManager(  190): Waiting for service media.audio_policy...

    then ,we modified get_number_cameras function ,let it return two directly .It can boot ,but we lunch camera ,some errors occurred,like this :

    E/CameraHal(  124): (400fa488)   hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXCameraAdapter.cpp:3735 switchToState - Timeout triggered while switching to state 0x1

    E/CameraHal(  124): (400fa488)   hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXCameraAdapter.cpp:3817 fetchCapabilitiesForSensor - Failed to switch to Loaded state, error: -10

    Thanks & Regards,

    Johhny

  • 0 in reply to Johnny
    TI__Mastermind 24525 points

    It is not a good idea to modify get_number_cameras function. The right way to do it is using capabilities DCC file. Please ask your TI representative about DCC.

  • 0 in reply to Mayank Mangla
    Intellectual 585 points

       The document said " Few sensor (especially SoC) DCC is irrelevant and specifying
    “OMX_CAMERA_DCC_NULL_CHAR” indicates no DCC for that sensor."I want to know whether want to use DCC file for OV2655 or not .Thanks !

  • 0 in reply to Johnny
    TI__Mastermind 24525 points

    Thanks for pointing it out. The document has not been updated for some recent SW changes. DCC capabilities need to be defined for every sensor.

  • 0 in reply to Mayank Mangla
    Intellectual 585 points

    Thank you reply !