IMX6 Q Build Android - Empty device/fsl directory

[rickeywang]

Hi

I am trying to build the Android JB4.2.2_1.1.0-GA release for IMX6Q SABRE AI, following instructions in android_jb4.2.2_1.1.0-ga_doc.tar.gz/Android_User_Guide.pdf

I have patched the Android source and gotten the "Success: Now you can build the Android code for FSL i.MX platform " message. However, when I try to build the image, none of the fsl options came up on the lunch menu.

~/droid4darren$ source build/envsetup.sh
including device/asus/grouper/vendorsetup.sh
including device/asus/tilapia/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/lge/mako/vendorsetup.sh
including device/samsung/maguro/vendorsetup.sh
including device/samsung/manta/vendorsetup.sh
including device/samsung/toroplus/vendorsetup.sh
including device/samsung/toro/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including sdk/bash_completion/adb.bash

~/droid4darren$ lunch

You're building on Linux

Lunch menu... pick a combo:
     1. full-eng
     2. full_x86-eng
     3. vbox_x86-eng
     4. full_mips-eng
     5. full_grouper-userdebug
     6. full_tilapia-userdebug
     7. mini_armv7a_neon-userdebug
     8. mini_armv7a-userdebug
     9. mini_mips-userdebug
     10. mini_x86-userdebug
     11. full_mako-userdebug
     12. full_maguro-userdebug
     13. full_manta-userdebug
     14. full_toroplus-userdebug
     15. full_toro-userdebug
     16. full_panda-userdebug

Which would you like? [full-eng]

           

Turns out the entire device/fsl directory is empty:

~/droid4darren/device/fsl$ ls -l -a
total 12
drwxrwxr-x  3 hmi hmi 4096 Oct 16 01:04 .
drwxrwxr-x 12 hmi hmi 4096 Oct 16 01:04 ..
-rw-rw-r--  1 hmi hmi    0 Oct 16 01:04 .dummy
drwxrwxr-x  8 hmi hmi 4096 Oct 16 01:06 .git

So is the fsl-proprietary folder.

What am I missing? I must have overlooked something but I have no idea what that might be. Any help would be appreciated. Thank you!

Thanks!

[rickchu]

Hi Rickey,

Have same issue when I first build up develop environment.

In my case, the reason was caused by incorrect branch status in Android source codes.

After switch branch into "android-4.2.2_r1", the patch should working fine.

Hope this information may help you.

Rick

[rickeywang]

By switch branch, you mean "repo init -u https://android.googlesource.com/platform/manifest -b android-4.2.2_r1", right?

I deleted everything and started over again, and made sure that the branch is "android-4.2.2_r1". Patching also appeared to be successful... but device/fsl is still empty.. I feel like it's something i should download from a freescale git of sorts but couldn't find these files anywhere.

I even tried manually copying device/fsl files from https://github.com/onyx-intl/platform_device, but just end up with this error instead =(

build/core/config.mk:157: *** TARGET_ARCH not defined by board config: device/fsl/sabreauto_6q/BoardConfig.mk.  Stop.

** Don't have a product spec for: 'sabreauto_6q'

** Do you have the right repo manifest?

[rickchu]

My steps are list on below:

# I download the latest Android source codes without assign branch

$ repo init -u https://android.googlesource.com/platform/manifest

$ repo sync

# switch branch to android-4.2.2_r1

$ cd ~/WORKING_DIRECTORY

$ repo init -b android-4.2.2_r1

$ ./.repo/repo/repo sync --local-only

and then applying i.MX6 patch process. This works fine for me.

[rickeywang]

Thanks Rick for your help! My branch was already correctly checked-out.

Turns out I didn't make all of the files in /opt/android_jb4.2.2_1.1.0-ga_source/ executable, so some of the patches were actually not being applied at all! Despite this, the script still tells you "Success: Now you can build the Android code for FSL i.MX platform" when it completes, which in my case is an outrageous lie.

To Freescale: please update the Android User Guide to remind people that the files in /opt/android_jb4.2.2_1.1.0-ga_source/ needs to be executable...