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.

ducati DCC files

Other Parts Discussed in Thread: TPS61325

Hi there,


I'm currently using 4AJ.2.5P2 release prebuilt binaries on omap4470 blaze board, when I place CID42_OV5650 binaries under /data/misc/camera/R12_MVEN002_LD2_ND0_IR0_SH0_FL0_SVEN002_DCCID42/ and enabled the few debug prints in hardware/ti/omap44xx/camera/OMXAdapter/OMXDCC.c for readDCC() function I'm able to see this loading and I don't see any error on the ducati logs in
 cat /d/remoteproc/remoteproc0/trace1

However when I use the same DCC file for our custom board with OV5650 [ducati is modified for same] I see following error

[      1.447] [ERR=43] src/config/omx_sup/cam_super_cfg_plugin.c:[108]:[Error] Get Index: 0x7f00005b
[      1.447] [ERR=44] src/conf_mng.c:[159]:
[      1.447] Error in src/conf_mng.c, line:159
[      1.447]
[      1.447] [ERR=45] omx_rpc/src/omx_rpc_skel.c:[322]:Component returned error: 0x8000100e
[      1.501] [ERR=46] src/parse_dcc_headers.c:[162]:
[      1.502] Error in src/parse_dcc_headers.c, line:162
[      1.502]
[      1.502] [ERR=47] src/msp_dcc_server.c:[248]:Cannot load specified dcc database!
[      1.502]  Last valid DCC component found 255
[      1.504] [ERR=48] src/omx_iss_cam_usecase_manager.c:[410]:


I have below questions

1. Can I use the blaze ov5650 DCC files on our custom board as sensor is same.

2. If not what needs to be done ?

3. Do we need to generate the new set of DCC files?

4. Why does the DCC for same sensor does not work if the modification are only in the socket location and i2c of the sensor?

Regards

Anuroop

  • If you have modified only the socket location and I2C address, DCC profile should not change.

    If you have modified sensor ID or sensor properties like orientation then it may cause failures at DCC load.

  • Hi Mayank,

    Yes I have below changes with respect to sensor.


    1. Socket is 0 for where as it is socket 1/2 for ov5650 on blaze board.

    2. I2c bus is 2 which is same as one of 5650 on blaze board.

    3. TPS61325 flash is not present in our case.

    4. the #define OV5650_CAMERA BOARD_MOD_1 which in case of the blaze for ov5650 is #define OV5650_CAMERA BOARD_MOD_2

    Does 3/4  give the issue for DCC? below is the quick summary of the ducati logs for blaze ducati and modified ducati.

    Blaze:

    [      1.930]  ##### PPM: Closed MSP.OMX_CAM.UC.CPCAM usecase.
    [      1.932] [ERR=456] src/sensor_detect_MSP.c:[266]:0>>:IMX060 Socket:0
    [      1.932] [ERR=457] src/sensor_detect_MSP.c:[266]:1>>:TPS61325 Socket:0
    [      1.932] [ERR=458] src/sensor_detect_MSP.c:[266]:2>>:LV8093 Socket:0
    [      1.932] [ERR=459] src/sensor_detect_MSP.c:[266]:3>>:CSI2 Socket:0
    [      1.932] [ERR=460] src/sensor_detect_MSP.c:[266]:0>>:OV5650 Socket:1
    [      1.932] [ERR=461] src/sensor_detect_MSP.c:[266]:1>>:TPS61325 Socket:1
    [      1.932] [ERR=462] src/sensor_detect_MSP.c:[266]:2>>:AD5820 Socket:1
    [      1.932] [ERR=463] src/sensor_detect_MSP.c:[266]:3>>:CSI2 Socket:1
    [      1.933] [ERR=464] src/sensor_detect_MSP.c:[266]:0>>:OV5650 Socket:2
    [      1.933] [ERR=465] src/sensor_detect_MSP.c:[266]:1>>:TPS61325 Socket:2
    [      1.933] [ERR=466] src/sensor_detect_MSP.c:[266]:2>>:AD5820 Socket:2
    [      1.933] [ERR=467] src/sensor_detect_MSP.c:[266]:3>>:CSI2 Socket:2

    Our Board:

    [      1.745]  ##### PPM: Closed MSP.OMX_CAM.UC.VIDEO usecase.
    [      1.746] [ERR=100] src/sensor_detect_MSP.c:[266]:0>>:OV5650 Socket:0
    [      1.747] [ERR=101] src/sensor_detect_MSP.c:[266]:1>>:AD5820 Socket:0
    [      1.747] [ERR=102] src/sensor_detect_MSP.c:[266]:2>>:CSI2 Socket:0
    [      1.747] [ERR=103] src/sensor_detect_MSP.c:[271]:On Socket:1 Sensor no detected
    [      1.747] [ERR=104] src/sensor_detect_MSP.c:[271]:On Socket:2 Sensor no detected

    Regards

    Anuroop