• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Subscribers 101 subscribers
  • Views 2005 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.

Jelly bean Android build fails

Nithya Sundaram
Prodigy 80 points
Other Parts Discussed in Thread: 4460

Hi,

I'm trying to build Android Jelly bean for blaze board ( OMAP4 4460 )

I am referring to the release notes http://www.omappedia.com/wiki/4AJ.1.0_OMAP4_Jelly_Bean_Release_Notes 

I am able to build x-loader, u-boot and kernel

I followed the same steps as in 4AJ.1.0_OMAP4_Jelly_Bean_Release_Notes

To build Android for blaze board 

source build/envsetup.sh

lunch full_blaze-userdebug

make -j4

Build fails with the following error, if i missed out something, please let me know

In file included from frameworks/av/media/libstagefright/colorconversion/ColorConverter.cpp:22:0:
frameworks/av/include/media/stagefright/ColorConverter.h:56:13: error: 'OMX_TI_INTERLACETYPE' has not been declared
frameworks/av/media/libstagefright/colorconversion/ColorConverter.cpp:141:9: error: 'OMX_TI_INTERLACETYPE' has not been declared
frameworks/av/media/libstagefright/colorconversion/ColorConverter.cpp: In member function 'android::status_t android::ColorConverter::convertInterlacedBuffer(void const*, size_t, size_t, size_t, size_t, size_t, size_t, int, void*, size_t, size_t, size_t, size_t, size_t, size_t)':
frameworks/av/media/libstagefright/colorconversion/ColorConverter.cpp:149:24: error: 'OMX_InterlaceFrameTopFieldFirst' was not declared in this scope
frameworks/av/media/libstagefright/colorconversion/ColorConverter.cpp:150:24: error: 'OMX_InterlaceFrameBottomFieldFirst' was not declared in this scope
make: *** [out/target/product/blaze/obj/STATIC_LIBRARIES/libstagefright_color_conversion_intermediates/ColorConverter.o] Error 1
make: *** Waiting for unfinished jobs....
In file included from frameworks/av/media/libstagefright/colorconversion/../include/SoftwareRenderer.h:21:0,
from frameworks/av/media/libstagefright/colorconversion/SoftwareRenderer.cpp:20:
frameworks/av/include/media/stagefright/ColorConverter.h:56:13: error: 'OMX_TI_INTERLACETYPE' has not been declared
make: *** [out/target/product/blaze/obj/STATIC_LIBRARIES/libstagefright_color_conversion_intermediates/SoftwareRenderer.o] Error 16038.androidJB_blazelog.txt

I have attached the complete log file for your reference, looking forward for your comments

Thanks Regards

Nithya

  • 0
    TI__Expert 5515 points

    It might be that there are some missing files in your repository due to network issues.

    Can you try running "repo sync" in your mydroid directory and try compiling again?, let me know what happen.

  • 0 in reply to Israel Cepeda
    Prodigy 80 points

    Hi,

    I tried running " repo sync " in my mydroid directory and compiled again,but still i'm getting the same error.

    I made changes to the following files :

    1.I added the following lines to  mydroid/device/ti/blaze/AndroidProducts.mk

    # define OMAP_ENHANCEMENT variables

    include device/ti/blaze_tablet/Config.mk

    PRODUCT_MAKEFILES := $(LOCAL_DIR)/full_blaze.mk

    ifdef OMAP_ENHANCEMENT_CPCAM

    PRODUCT_MAKEFILES += \

        $(LOCAL_DIR)/sdk_addon/ti_omap_addon.mk

    # clear OMAP_ENHANCEMENT variables

    $(call ti-clear-vars)

    endif

    2.I edited some features in  mydroid/device/ti/blaze/BoardConfig.mk

    #OMAP_ENHANCEMENT := true

    ENHANCED_DOMX := true

    After making changes to these two files,I am able to build for Blaze board successfully.

    I used the following bootargs.

    setenv bootargs 'console=ttyO2,115200n8 mem=1G androidboot.console=ttyO2 console=ttyO2,115200n8 root=/dev/mmcblk1p2 init=/init vram=64'
    setenv bootcmd 'mmcinit 0;fatload mmc 0 0x80000000 uImage; bootm 0x80000000'
    boot

    But when I try to boot from sdcard,I'm getting the following error.

    shell@android:/ $ [   11.445190] (stc): add_channel_to_table: id 2

    [   11.450408] (stc): st_register(3)

    [   11.454193] (stc): add_channel_to_table: id 3

    [   11.459075] (stc): st_register(4)

    [   11.465362] PVR: Installing MISR with cookie bf046560

    [   11.471252] (stc): add_channel_to_table: id 4

    [   11.476135] PVR: Installing device LISR SGX ISR on IRQ 53 with cookie c701a800

    [   11.483917] PVR: OSUnMapPhysToLin: unmapping 65535 bytes from c8d20000

    [   11.490936] PVR: SysFinalise: Version string: SGX revision = 1.2.0

    [   11.497528] omaplfbOMAPLFBInit: Blitsville gc2d not present, blits disabled

    [   11.505004] omaplfb: OMAPLFBInitIonOmap: Device 0: Requesting 2 TILER 2D framebuffers

    [   12.699920] EMIF: Access error from EMIF0 SYS port - 1

    I have attached the complete error log for your reference.

    Please let me know If I missed out something.

    Regards

    Nithya

  • 0 in reply to Nithya Sundaram
    TI__Expert 8055 points

    Hi Nithya,

    You shouldn't need to make changes to the makefiles.  Do you have a Blaze Tablet that you can test with?  Does the build with your same manifest complete successfully for Blaze Tablet?

    Thanks,
    Gina 

  • 0 in reply to Gina Glaser
    TI__Genius 10545 points

    Nithya,

    I am trying configuration for Blaze in order to try reproduce your issue, and I found similar error,

    frameworks/av/media/libstagefright/ACodec.cpp:1216:9: error: 'OMX_AUDIO_PARAM_FLACTYPE' was not declared in this scope
    frameworks/av/media/libstagefright/ACodec.cpp:1216:34: error: expected ';' before 'def'
    frameworks/av/media/libstagefright/ACodec.cpp:1217:24: error: 'def' was not declared in this scope
    frameworks/av/media/libstagefright/ACodec.cpp:1221:50: error: 'OMX_IndexParamAudioFlac' was not declared in this scope
    frameworks/av/media/libstagefright/ACodec.cpp: In member function 'android::status_t android::ACodec::setSupportedOutputFormat()':
    frameworks/av/media/libstagefright/ACodec.cpp:1359:5: warning: comparison between 'OMX_COLOR_FORMATTYPE {aka enum OMX_COLOR_FORMATTYPE}' and 'enum OMX_TI_COLOR_FORMATTYPE' [-Wenum-compare]

    in my case it is fixed by

    user@user:/jb/4AJ.1.0/mydroid/device/ti/blaze$ git diff
    diff --git a/BoardConfig.mk b/BoardConfig.mk
    index 0fb38c5..9be077b 100644
    --- a/BoardConfig.mk
    +++ b/BoardConfig.mk
    @@ -31,7 +31,7 @@ OMAP_ENHANCEMENT_CPCAM := true
     OMAP_ENHANCEMENT_VTC := true
     endif
     
    -ENHANCED_DOMX :=
    +ENHANCED_DOMX := true
     BLTSVILLE_ENHANCEMENT :=true
     USE_ITTIAM_AAC := true
     # Use the non-open-source parts, if they're present

    this is because of

    ./jb/4AJ.1.0/mydroid/frameworks/av/media/libstagefright/Android.mk

    ifdef OMAP_ENHANCEMENT
    LOCAL_C_INCLUDES += $(DOMX_PATH)/omx_core/inc
    else
    LOCAL_C_INCLUDES += $(TOP)/frameworks/native/include/media/openmax
    endif

    that are defined in

    ./jb/4AJ.1.0/mydroid/device/ti/common-open/BoardConfig.mk

    # Makefile variable and C/C++ macro to recognise DOMX version
    ifdef ENHANCED_DOMX
        COMMON_GLOBAL_CFLAGS += -DENHANCED_DOMX
        DOMX_PATH := hardware/ti/domx
    else
        DOMX_PATH := hardware/ti/omap4xxx/domx
    endif

    and it is called at the end of next file

    ./jb/4AJ.1.0/mydroid/device/ti/blaze/BoardConfig.mk

    # Common device independent definitions

    include device/ti/common-open/BoardConfig.mk

    /.../

  • 0 in reply to Gina Glaser
    Prodigy 80 points

    Hi Gina,

    Thanks for your reply, I am able to successfully build sources for Blaze Tablet with the same manifest, however I don't have Blaze Tablet to test and verify this.

    Thanks

    Nithya

  • 0 in reply to Nithya Sundaram
    TI__Expert 5515 points

    Nithya,

    If you look at the introduction of the release notes for JB it is only being tested on a TI OMAP4470 ES1.0 HS Blaze Tablet, so at this point Blaze is not being supported, that's why you are seeing problems when trying to compile. So for now you will need to fix compilation issues if you want to get JB working on your Blaze.

  • 0 in reply to Manuel Contreras
    Prodigy 50 points

    Hi all,

    I'm trying compile Jelly Bean for PandaBoard, but now, i'm getting some errors like follow:

    hardware/ti/omap4xxx/camera/ANativeWindowDisplayAdapter.cpp:18:26: fatal error: OMX_IVCommon.h: No such file or directory
    compilation terminated.

    Firstly, I installed OMX lib and the OMX_IVCommon.h was installed into /usr/include. Then, I continued make mydroid. But the same error happened.

    Please help me fix this error.

    Thanks so much.

  • 0 in reply to Huy-Tinh Nguyen
    TI__Expert 5515 points

    For Pandaboard supported releases you may want to ask the google group pandaboard@googlegroups.com

  • 0 in reply to Israel Cepeda
    Prodigy 50 points

    Thanks for your reply. I will.

  • 0 in reply to Nithya Sundaram
    Prodigy 80 points

    Hi,

    I am referring to the release notes http://www.omappedia.com/wiki/4AJ.2.0_OMAP4_Jelly_Bean_Release_Notes.

    I am trying to port Android Jellybean on blaze. I am following the release notes and I can able to build for blaze successfully.

    But When I try to boot ,it fails with the following crash.

    E/audio_hw_primary( 130): Unable to locate all mixer controls, aborting.
    E/AudioFlinger( 130): couldn't open audio hw device in audio.primary (Invalid argument)
    I/AudioFlinger( 130): Loaded a2dp audio interface from A2DP Audio HW HAL (audio)
    I/AudioFlinger( 130): Using 'A2DP Audio HW HAL' (audio.a2dp) as the primary audio interface

    I have attached the complete log for your reference.Please let me know if I missed out something.

    Regards,

    Nithya

  • 0 in reply to Nithya Sundaram
    TI__Expert 8055 points

    Nithya,

    It looks like you are trying to boot from SD card.  Could you please use fastboot to flash the files into eMMC and try to boot from eMMC instead, as described in the release notes?  Booting Android from SD card is not officially supported.  It requires some additional tweaks, which just introduces additional variables at this point.

    Thank you,
    Gina