Takashi Kawamoto

How to configuring an Android image for i.MX53 onto microSD

Discussion created by Takashi Kawamoto on Jun 1, 2011
Latest reply on Jun 23, 2011 by Takashi Kawamoto

I'm now configuring an Android image on Sundisk microSD for i.MX53 Quick Start Kit, referring to i.MX_Android_R9.4_User_Guide.html in the i.MX53-QSB-Android-Release3.3 package, and I'm troubled with unsuccessful booting from the microSD card. When i.MX53 Quick Start Kit is powered on with the card, even u-boot doesn't boot up and no messages appear on serial console.

I'm doing all configurations on Ubuntu Linux with the i.MX53 Quick Start Kit.

The partition is configured to be as follows.


Device                Boot      Start         End         Blocks     Id       System

/dev/mmcblk1p1                 321       64320     2048000   83         Linux

/dev/mmcblk1p2              64321       77120      409600   83          Linux

/dev/mmcblk1p3              77121       90560      430080    5     Extended

/dev/mmcblk1p4              90561       91840       40960   83          Linux

/dev/mmcblk1p5              77121       89920      409592   83         Linux

/dev/mmcblk1p6              89921       90560       20472    83          Linux


After creating those partitions, I formatted each file systems as follows.


mkfs.vfat /dev/mmcblk1p1
mkfs.ext4 /dev/mmcblk1p2 -O ^extent -L system
mkfs.ext4 /dev/mmcblk1p4 -O ^extent -L recovery
mkfs.ext4 /dev/mmcblk1p5 -O ^extent -L data
mkfs.ext4 /dev/mmcblk1p6 -O ^extent -L cache


I used dd utility to download the Android image files, according to Section 3.2.3 in the above mentioned users guide. I executed each command after moving to i.MX53-QSB-Android-elease3.3/download/imx-android-r9.4/image/imx53_smd directory.


dd if=u-boot.bin of=/dev/mmcblk1 bs=1K skip=1 seek=1; sync
dd if=uImage of=/dev/mmcblk1 bs=1M seek=1; sync
dd if=SD/uramdisk.img of=/dev/mmcblk1 bs=1M seek=6; sync
dd if=SD/system.img of=/dev/mmcblk1p2; sync
dd if=SD/recovery.img of=/dev/mmcblk1p4; sync


I suspect that the above dd command parameters have something to do with this failure to boot up. For example, "seek" parameters are same between the first command (u-boot.bin) and the second commands (uImage), so it seems that uImage could overwrite the u-boot.bin.


Has anyone followed this Users Guide and come across the similar issue?