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.
I'm using OMAP5432 EVM which has a CSI. We haven't connected camera. Instead, we use Toshiba's TC358743 HDMI to CSI bridge and give a HDMI video as a CSI input, through CSI. I'm facing the following issue. I have included the logs which has my debug prints. I find that there had been no error in GetHandle.
D/DOMX ( 109): hardware/ti/domx/domx/omx_proxy_common/src/omx_proxy_common.c:1671 __PROXY_SetConfig() D/DOMX ( 109): ERROR: failed check:(eError == OMX_ErrorNone) || (eError == OMX_ErrorNoMore) - returning error: 0x80001009 - Error returned from OMX API in ducatiE/CameraHal( 109): (400243dc) hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXCameraAdapter.cpp:4355 fetchCapabilitiesForSensor - Selecting sensor 0... DONEE/CameraHal( 109): (400243dc) hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXCameraAdapter.cpp:4498 OMXCameraAdapter_Capabilities - CamTest: hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXCameraAdapter.cpp: handler.fetchCapabilitiesForSensor error
What can be reason for this? What kind of information does it expect from Ducati driver?
From the following link,
I came to know that,
In the absence of primary sensor OR some error in the primary sensor simply exit from the sensor detection of other sensor ids. Because with the current implementation, if the primary sensor is not present, application can not switch to other sensors.
The ducati logs are,
[ 0.394] [ERR=24] src/sensor_detect_DRV.c::Try defatult detect socket 0 [ 0.395] [ERR=25] src/sensor_detect_DRV.c::Default Sensor detect [ 0.395] [ERR=26] src/sensor_detect_MSP.c::0>>:TC358743 Socket:0 [ 0.395] [ERR=27] src/sensor_detect_MSP.c::1>>:CSI2 Socket:0 [ 0.395] [ERR=28] src/sensor_detect_MSP.c::On Socket:1 Sensor no detected [ 0.395] [ERR=29] src/sensor_detect_MSP.c::On Socket:2 Sensor no detected [ 0.395] [ERR=30] src/sensor_detect_MSP.c::pGetEeprom->nEepromBuff==NULL
Does it mean that, as I didn't connect any hardware camera, this error is rising?
In the ducati Makefile, under myxdcargs, I haven't changed the default SenPosition=TABLET. Does it has to do anything with this? Based on what should I give this as BLAZE or TABLET?
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Gomathi Chan:
Yes the absence of connected camera or bridge to the csi interface is rising the error.
Have you tried with the blaze value for SenPosition. Also what board_config did you use? (BOARD_CONFIG_C_V2)
Please click the Verify Answer button on this post if it answers your question.
Be sure to read the OMAP4 and OMAP5 Forum Guidelines and FAQ
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.