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 Not loading for 512 MB RAM

Hi,

  Using SW release 4AJ.2.2  for OMAP4430 with 512MB RAM ,OV5640 .

Am loading ducati.512MB.bin and testla.512MB.bin as required by kernel.

My issue ,when I open camera application am getting bewlo error

01-01 00:44:35.843 D/DOMX ( 95): hardware/ti/domx/domx/plugins/memplugin_ion.c:172 MemPlugin_ION_Alloc()
01-01 00:44:35.843 D/DOMX ( 95): ERROR: FAILED to allocate secure buffer of size=86016. ret=0x0
01-01 00:44:35.843 D/DOMX ( 95): hardware/ti/domx/domx/omx_proxy_common/src/omx_proxy_common.c:1072 PROXY_UseBuffer()
01-01 00:44:35.843 D/DOMX ( 95): ERROR: Allocation failed 2

When I debugged in kernel, for 512MB ,omap4_ion heap memory is not allocated.

Any pointers or suggesions will be helpful

 

 

  • Hi,

    In the 4AJ2.2 kernel configuration, the ion carveout heap is reserved at 1G RAM boundary (something ~0xBA300000). And these addresses are known to regular ducati binary.

    But if you are trying it out on 512MB RAM part, and loading the corresponding ducati bianry, I think you may need to move the ion memory reserves to 512MB boundary, or make sure that Kernel ION component has dynamic page allocation support.

    btw, which kernel are you using?

    Thanks & Regards,

    Sunita.

  • Using Kernel: 3.0.31 

    and release from

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

  • The answer of the question from your specialist is as follow

    -       Android Version 4.1.2

    -       Kernel Version 3.0.31-g385b7f5

  • Hi,

    The support for 512MB RAM was developed in a separate branch, and not sure whether that is present in the Android release you are referring to. Here is the link to all Kernel patches that were created for 512MB RAM size.

    http://review.omapzoom.org/#/q/status:merged+project:kernel/omap+branch:p-android-omap-3.0-dev+topic:ics512mb,n,z

    Please check whether these changes are present are not. If present but still it is crashing in ion buffer allocation, then please add some traces in kernel ion component, and share the logs why the allocations are failing. 

    With the current user side log, it is hard to understand what is missing in the setup.

    Thanks & Regards,

    Sunita.

  • Hi,

      Thank you information.

    All the patches are integrated and kernel is in dynamic mode  for 512MB ram case.and Kernel logs are sent by mail 

    in file,not sure about change after analyses,modified below changes

    hardware/ti/domx/domx/plugins/memplugin_ion.c:169 

    if(sIonParams.alloc_flags != OMAP_ION_HEAP_SECURE_INPUT) to
    if(sIonParams.alloc_flags == OMAP_ION_HEAP_SECURE_INPUT)
    Now it is allocating for ION.
    but still failing with error

    01-01 04:31:01.687 F/libc ( 95): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 821 (Binder_2)
    01-01 04:31:01.687 D/DOMX ( 95): hardware/ti/domx/domx/omx_proxy_common/src/omx_proxy_common.c:722 PROXY_FillThisBuffer()
    01-01 04:31:01.687 D/DOMX ( 95): ERROR: failed check:(eError == OMX_ErrorNone) || (eError == OMX_ErrorNoMore) - returning error: 0x80001009 - Error returned from OMX API in ducati
    01-01 04:31:01.687 E/CameraHal( 95): (40b025a8) hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXCameraAdapter.cpp:2300 startPreview - OMX_FillThisBuffer-0x80001009
    01-01 04:31:01.687 E/CameraHal( 95): (40b025a8) hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXCameraAdapter.cpp:2351 startPreview - Exiting function startPreview because of ret 0 eError=80001009
    01-01 04:31:01.687 E/ion ( 95): ioctl -1073460991 failed with code -1: Bad file number
    01-01 04:31:01.687 E/ion ( 95): ioctl -1073460991 failed with code -1: Bad file number
    01-01 04:31:01.687 E/ion ( 95): ioctl -1073460991 failed with code -1: Bad file number
    01-01 04:31:01.687 E/ion ( 95): ioctl -1073460991 failed with code -1: Bad file number
    01-01 04:31:01.687 E/ion ( 95): ioctl -1073460991 failed with code -1: Bad file number
    01-01 04:31:01.687 E/ion ( 95): ioctl -1073460991 failed with code -1: Bad file number.

    Regards,

    Srikar