Build problems with Android BSP from Adeneo-Freescale-iMX53-QSB-Android 2.3-Version 4.0

cancel
Showing results for 
Search instead for 
Did you mean: 

Build problems with Android BSP from Adeneo-Freescale-iMX53-QSB-Android 2.3-Version 4.0

1,439 Views
TugrulGuclu
Contributor I
Hi
 
We are trying to compile i.mx53 BSP of Android but receive error messages due to corrupt file in archive file from Adeneo servers.

I download the sources for Freescale-iMX53-QSB-Android 2.3-Version 4.0 & when we execute ./download_android_fixed.sh we receive this error.
 
 
 
gzip: stdin: invalid compressed data--crc error
tar: Child returned status 1
tar: Exiting with failure status due to previous errors
Error: failed to extract sources
lucid@ubuntu:~/Desktop/android/Freescale-iMX53-QSB-Android_2.3-Version_4.0/i.MX53-QSB-Android-Ginger...
 
Below is the corresponding script
# Extract FSL sources if required
mkdir -p ${ANDROID_INSTALL_DIR}
if [ ! -d ${ANDROID_INSTALL_DIR}/imx-android-r10.2 ]; then
 echo "Extracting FSL sources...";
 tar -C ${ANDROID_INSTALL_DIR} -xzf ${ANDROID_DL_DIR}/imx-android-r10.2.tar.gz
 if [ "$?" -ne "0" ]; then
  echo "Error: failed to extract sources"
  exit 1
 fi
else
 echo "${ANDROID_INSTALL_DIR}/imx-android-r10 already exists"
 echo "Cowardly refusing to clobber it"
fi

If I test the imx-android-r10.2.tar.gz archive manually, I receive CRC error too.
 

Has anyone succeeded to compile Android BSP for i.mx53 from Adeneo  ?

Best Regards
 
Tugrul
Labels (1)
0 Kudos
18 Replies

578 Views
TugrulGuclu
Contributor I

it might be the case. I have seen this with the first script download_android.sh. If you don't shorten the name script does not work. And also the sources of img files have a long  pathname like

"media/Backupdisk/android/Freescale-iMX53-QSB-Android-2.3-Version-4.1/i.MX53-QSB-Android-Gingerbread-Release4.1/src/out/target/product/imx53_loco"

BR

tugrul

0 Kudos

578 Views
AhmetYUCE
Contributor II
Seems nonsense but if your BSP installation directory's name long, i.e. /opt/i.MX53-QSB-Android-Gingerbread-Release4.1 could you try shortening it like /opt/iMX53-QSB ?
0 Kudos

578 Views
TugrulGuclu
Contributor I

Hi

I build hte sources with build-choice=all but received an error during 

# Package and copy images to our output directory
if [ ${BUILD_ANDROID} -gt 0 ]; then
cd ${ANDROID_OUT_PATH} && \
mkimage -A arm -O linux -T ramdisk -C none -a 0x70308000 -n \
"Android Root Filesystem" -d ./ramdisk.img ./uramdisk.img && \
mkdir -p ${OUTPUT_DIR} && \
cp ramdisk.img ${OUTPUT_DIR} && \
cp uramdisk.img ${OUTPUT_DIR} && \
cp system.img ${OUTPUT_DIR} && \
cp recovery.img ${OUTPUT_DIR} && \
cd -
fi

At the beginning of the block uBoot and uImage is compiled and copied to /out folder.  I wonder what could go wrong with a standart build script. I checked that my toolchain is up to date.

0 Kudos

578 Views
AhmetYUCE
Contributor II
By the way be sure on calling the script as follow: ./build_android.sh --board=imx53_qsb --build-choice=all --lunch-type=eng Builds Android RFS + kernel + u-boot..
0 Kudos

578 Views
AhmetYUCE
Contributor II
No need to manual copy. Check out /out folder's contents. Mine have all the necessary binaries. Regards Ahmet
0 Kudos

578 Views
TugrulGuclu
Contributor I



Ahmet YUCE said:

My host is Ubuntu 11.04, not 10.04 sorry for mistype.

Hi

Thanks for answer. After I build all components  using build_android.sh I checked the out folder in ROOT_DIR. But ramdisk.img , recovery.img, system.img , uramdisk.img were missing and only boot.bin and uImage is present.

I had to copy them from prebuilt manually. Can you verify this in your environment ?

BR

Tugrul

0 Kudos

578 Views
AhmetYUCE
Contributor II
My host is Ubuntu 11.04, not 10.04 sorry for mistype.
0 Kudos

578 Views
AhmetYUCE
Contributor II
I've recently build Android RFS + Kernel + uboot successfully using Adenao's BSB (Adeneo i.MX53 for Android Gingerbread v4.1). Sources freely available from Adenaos web site:http://www.adeneo-embedded.com/iMX53 Although i'have freescale's ubuntu vmware image given with iMX53QSB, I've used my ubunutu 10.04 (32-bit) vmware which already being using for iMX28 development. Host setup related part of "User Guide and Release Notes" of Adenao's BSP is copied below. Hope it helps. ******************** Software prerequisites Some packages need to be installed on your host in order to build Android. Please refer to the AOSP documentation: http://source.android.com/source/initializing.htmlNote: Gingerbread requires the Java JDK6 to be installed on your host. It will not work with other Java environments (including JDK5, which is required for Froyo). Some of the instructions of the AOSP documentation might not apply to your Ubuntu version. If you have problems installing JDK6, please use the following command: $ sudo add-apt-repository "deb http://archive.canonical.com/ubuntu lucid partner" instead of the one listed on the website: $ sudo add-apt-repository "deb-src http://archive.canonical.com/ubuntu lucid partner" If any of the installation of packages does not work properly, you can use the following websites to assist you with the installation: ● http://askubuntu.com/questions/25727/how-do-i-install-the-build-dependencies-forandroidhttp://www.wildartist.org/archives/1178http://www.crashcourse.ca/wiki/index.php/Android_on_Ubuntu_10.04#Building_Android_in_its_entirety
0 Kudos

578 Views
Yuri
NXP TechSupport
NXP TechSupport

Here are the instructions to access the new git servers:
You need to get the latest version of the repo tool:

curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo

You need to initialize a new repository:

repo init -u https://android.googlesource.com/platform/manifest -b android-2.3.7_r1

The full instructions are at http://source.android.com/source/downloading.html

0 Kudos

577 Views
rlorriaux
Contributor I

Hi,

You want to use the latest release (r4.1) as it addresses these issues (the repositories have changed after the situation with kernel.org).

0 Kudos

578 Views
TugrulGuclu
Contributor I

Hi Yuri

Do you know valid Android repo adresses ? if yes can you provide ?

Thanks

Yuri Muhin said:

Some time ago I found some problems with both Android and Linux kernel 2.35.3 repo(s).
Android repo address was changed, and kernel one was not found at all.  

0 Kudos

578 Views
TugrulGuclu
Contributor I

Hi

The problem is figured out. It's about the gzip utility shipped with the VM image from Freescale.

We upgrade it  from it 1.3.12-9ubuntu1 to gzip 1.3.12.-9ubuntu1.1 and now extraction is working.

Thanks

0 Kudos

578 Views
Yuri
NXP TechSupport
NXP TechSupport

Some time ago I found some problems with both Android and Linux kernel 2.35.3 repo(s).
Android repo address was changed, and kernel one was not found at all.  

0 Kudos

577 Views
rlorriaux
Contributor I

Can you try using release 4.1?

If that does not work, I cannot think of any issue besides a problem with your host.

Remi

0 Kudos

577 Views
TugrulGuclu
Contributor I

Hi Remi

I contacted with support of Adeneo, md5 check of file is correct.

Any idea what could go wrong ? 

By the way , i run ubuntu on VMware.

Regards

0 Kudos

577 Views
rlorriaux
Contributor I

Hi,

We have never heard about such a problem. Can you please download again and let me know if you have any issues?

Also, I would recommend using release 4.1.

Remi Lorriaux - Adeneo Embedded

0 Kudos

578 Views
daiane_angolini
NXP Employee
NXP Employee

I took that file some time ago and it was ok to me.

try donwload it again, and please contact Adeneo. They can fix the file

0 Kudos

578 Views
TugrulGuclu
Contributor I

Hi

I also  logged the output of tar until error message. See it below please

imx-android-r10.2/
imx-android-r10.2/code/
imx-android-r10.2/code/r10.2.tar.gz
imx-android-r10.2/doc/
imx-android-r10.2/doc/bootloader/
imx-android-r10.2/doc/bootloader/uboot_mx5x.pdf
imx-android-r10.2/doc/i.MX_Android_R10.2_Release_Note.html
imx-android-r10.2/doc/i.MX_Android_R10.2_User_Guide.html
imx-android-r10.2/doc/images/
imx-android-r10.2/doc/images/dc37ttrp_52dswz9ggp_b.png
imx-android-r10.2/doc/images/dc37ttrp_53ds6qx4f2_b.png
imx-android-r10.2/doc/images/dc37ttrp_54cw52rjfs_b.png
imx-android-r10.2/doc/images/dfpb5q7n_2g9txk6gs_b.jpg
imx-android-r10.2/doc/images/dg9fs94x_189cdx5kpg2_b.jpg
imx-android-r10.2/doc/images/dg9fs94x_190cpq7jhvd_b.jpg
imx-android-r10.2/doc/images/Thumbs.db
imx-android-r10.2/doc/i_MX_Android_Codec_Release_Notes.html
imx-android-r10.2/doc/NAND Flash Bad Block Management.doc
imx-android-r10.2/doc/SDK_UserGuide/
imx-android-r10.2/doc/SDK_UserGuide/i.MX50_EVK_RD3_Linux_User_Guide.pdf
imx-android-r10.2/doc/SDK_UserGuide/i.MX50_RDP_Linux_BSP_UserGuide.pdf
imx-android-r10.2/doc/SDK_UserGuide/i.MX51_EVK_Linux_BSP_UserGuide.pdf
imx-android-r10.2/doc/SDK_UserGuide/i.MX53_ARD_Linux_BSP_UserGuide.pdf
imx-android-r10.2/doc/SDK_UserGuide/i.MX53_EVK_Linux_BSP_UserGuide.pdf
imx-android-r10.2/doc/SDK_UserGuide/i.MX53_SABRE_TABLET_Linux_BSP_UserGuide.pdf
imx-android-r10.2/doc/uboot_mx5x.pdf
imx-android-r10.2/EULA.txt
imx-android-r10.2/image/
imx-android-r10.2/image/imx50_rdp-eink/
imx-android-r10.2/image/imx50_rdp-eink/NFS/
imx-android-r10.2/image/imx50_rdp-eink/NFS/android_fs.tar.gz
imx-android-r10.2/image/imx50_rdp-eink/SD/
imx-android-r10.2/image/imx50_rdp-eink/SD/android_recovery.img
imx-android-r10.2/image/imx50_rdp-eink/SD/android_root.img
imx-android-r10.2/image/imx50_rdp-eink/SD/recovery.img
imx-android-r10.2/image/imx50_rdp-eink/SD/system.img
imx-android-r10.2/image/imx50_rdp-eink/SD/uramdisk.img
imx-android-r10.2/image/imx50_rdp-eink/u-boot-no-padding.bin
imx-android-r10.2/image/imx50_rdp-eink/u-boot.bin
imx-android-r10.2/image/imx50_rdp-eink/uImage
imx-android-r10.2/image/imx50_rdp-lcd/
imx-android-r10.2/image/imx50_rdp-lcd/NFS/
imx-android-r10.2/image/imx50_rdp-lcd/NFS/android_fs.tar.gz
imx-android-r10.2/image/imx50_rdp-lcd/SD/
imx-android-r10.2/image/imx50_rdp-lcd/SD/android_recovery.img
imx-android-r10.2/image/imx50_rdp-lcd/SD/android_root.img
imx-android-r10.2/image/imx50_rdp-lcd/SD/recovery.img
imx-android-r10.2/image/imx50_rdp-lcd/SD/system.img
imx-android-r10.2/image/imx50_rdp-lcd/SD/uramdisk.img
imx-android-r10.2/image/imx50_rdp-lcd/u-boot-no-padding.bin
imx-android-r10.2/image/imx50_rdp-lcd/u-boot.bin
imx-android-r10.2/image/imx50_rdp-lcd/uImage
imx-android-r10.2/image/imx51_bbg/
imx-android-r10.2/image/imx51_bbg/NFS/
imx-android-r10.2/image/imx51_bbg/NFS/android_fs.tar.gz
imx-android-r10.2/image/imx51_bbg/SD/
imx-android-r10.2/image/imx51_bbg/SD/recovery.img
imx-android-r10.2/image/imx51_bbg/SD/system.img
imx-android-r10.2/image/imx51_bbg/SD/uramdisk.img
imx-android-r10.2/image/imx51_bbg/u-boot-no-padding.bin
imx-android-r10.2/image/imx51_bbg/u-boot.bin
imx-android-r10.2/image/imx51_bbg/uImage
imx-android-r10.2/image/imx53_ard/
imx-android-r10.2/image/imx53_ard/NFS/
imx-android-r10.2/image/imx53_ard/NFS/android_fs.tar.gz
imx-android-r10.2/image/imx53_ard/SD/
imx-android-r10.2/image/imx53_ard/SD/recovery.img
imx-android-r10.2/image/imx53_ard/SD/system.img
imx-android-r10.2/image/imx53_ard/SD/uramdisk.img
imx-android-r10.2/image/imx53_ard/u-boot-no-padding.bin
imx-android-r10.2/image/imx53_ard/u-boot.bin
imx-android-r10.2/image/imx53_ard/uImage
imx-android-r10.2/image/imx53_smd/
imx-android-r10.2/image/imx53_smd/eMMC/
imx-android-r10.2/image/imx53_smd/eMMC/recovery.img
imx-android-r10.2/image/imx53_smd/eMMC/system.img
imx-android-r10.2/image/imx53_smd/eMMC/uramdisk.img
imx-android-r10.2/image/imx53_smd/NFS/
imx-android-r10.2/image/imx53_smd/NFS/android_fs.tar.gz
imx-android-r10.2/image/imx53_smd/SD/
imx-android-r10.2/image/imx53_smd/SD/recovery.img
imx-android-r10.2/image/imx53_smd/SD/system.img
imx-android-r10.2/image/imx53_smd/SD/uramdisk.img
imx-android-r10.2/image/imx53_smd/u-boot-no-padding.bin
imx-android-r10.2/image/imx53_smd/u-boot.bin
imx-android-r10.2/image/imx53_smd/uImage
imx-android-r10.2/package_manifest.txt
imx-android-r10.2/tool/
imx-android-r10.2/tool/android_usb_fsl.zip

I think  imx-android-r10.2/tool/android_usb_fsl.zip is the problematic file.

Best Regards 

0 Kudos