topic Android on imx51 issues in i.MX Processors

Android on imx51 issues

TomErikson — Mon, 03 Oct 2011 15:43:31 GMT

from these directions http://reviews.androids.name/2011/03/i-mx-android-firmware-developers-manual-very-good/ I followed steps

3.2.1

3.2.3

3.2.5

for the imx51 bbg. The board I am using is the imx51 evk, which might be the issue but I am unsure. Just to be clear on exactly what I did:

I used fdisk to partition an sd card like this:

Partition Type/Index	Name	Start Offset	Size	File System	Content
N/A	BOOT	0	10 MB	N/A	bootloader/kernel/uramdisk images
Primary 1	MEDIA	11 MB	User Defined	VFAT. Mount as /sdcards	Media file storage
Primary 2	SYSTEM	follow MEDIA	>= 200 MB	EXT4. Mount as /system (with read only)	Android system bin/libs (system.img)
Logic 5 (Extended 3)	DATA	follow SYSTEM	> 200 MB	EXT4. Mount as /data	Android data (e.g. installed app)
Logic 6 (Extended 3)	CACHE	follow DATA	> 10 MB	EXT4. Mount as /cache	Android cache
Primary 4	RECOVERY	follow CACHE	> 20 MB	EXT4. Mount as / in recovery mode	Root file system for recovery mode (recovery.img)

Then I ran these commands

# mkfs.vfat /dev/sdx1
# mkfs.ext4 /dev/sdx2 -O ^extent -L system
# mkfs.ext4 /dev/sdx4 -O ^extent -L recovery
# mkfs.ext4 /dev/sdx5 -O ^extent -L data
# mkfs.ext4 /dev/sdx6 -O ^extent -L cache

# sudo dd if=u-boot-no-padding.bin of=/dev/sdx bs=1K seek=1; sync

# sudo dd if=uImage of=/dev/sdx bs=1M seek=1; sync

# sudo dd if=uramdisk.img of=/dev/sdx bs=1M seek=6; sync

Then I put the sd card into the imx51 and powered up the board (dip switch set all off except 7 and 8). UBoot loaded and I changed the environment variables to

bootdelay=1
baudrate=115200
netdev=eth0
ethprime=FEC0
uboot_addr=0xa0000000
kernel=uImage
nfsroot=/opt/eldk/arm
bootargs_base=setenv bootargs console=ttymxc0,115200 gpu_memory=16M
bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
bootcmd_net=run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${kernel}; bootm
prg_uboot=tftpboot ${loadaddr} ${uboot}; protect off ${uboot_addr} 0xa003ffff; erase ${uboot_addr} 0xa003ffff; cp.b ${loadaddr} ${uboot_addr} ${filesize}; setenv filesize; saveenv
bootcmd_SD=run bootargs_base bootargs_android;mmc read 0 ${loadaddr} 0x800 1800;mmc read 0 ${rd_loadaddr} 0x2000 0x258;bootm ${loadaddr} ${rd_loadaddr}
bootargs_android=setenv bootargs ${bootargs} androidboot.console=ttymxc0 init=/init di1_primary calibration
bootcmd_android_recovery=run bootargs_base bootargs_android_recovery;mmc read 0 ${loadaddr} 0x800 0x1800;bootm
bootargs_android_recovery=setenv bootargs ${bootargs} init=/init root=/dev/mmcblk0p4 rootfs=ext4 di1_primary
ethact=FEC0
ethaddr=00:04:9f:00:ea:d3
fec_addr=00:04:9f:00:ea:d3
bootcmd=run bootcmd_SD; bootm ${loadaddr} 0x800 0x2000; mmc read 0 ${rd_loadaddr} 0x3000 0x300;
uboot=u-boot-no-padding.bin
bootargs=console=ttymxc0,115200 gpu_memory=16M androidboot.console=ttymxc0 init=/init di1_primary calibration
stdin=serial
stdout=serial
stderr=serial
loadaddr=0x90800000
rd_loadaddr=0x90B00000

And I get this error when I try to boot

BBG U-Boot > bootd

MMC read: dev # 0, block # 2048,count 6144 ...
6144 blocks read: OK

MMC read: dev # 0, block # 8192,count 600 ...
600 blocks read: OK
## Booting kernel from Legacy Image at 90800000 ...
   Image Name:   Linux-2.6.35.3-00026-g37d9315
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3150972 Bytes = 3 MB
   Load Address: 90008000
   Entry Point: 90008000
   Verifying Checksum ... OK
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
## Booting kernel from Legacy Image at 90800000 ...
Bad Header Checksum
ERROR: can't get kernel image!

MMC read: dev # 0, block # 12288,count 768 ...
768 blocks read: OK

I am unfamiliar with UBoot / Android / Linux so I am expecting it to be a simple mistake. Let me know if you need anything else to diagnose why it won't boot the image.

Thanks

Re: Android on imx51 issues

daiane_angolini — Mon, 03 Oct 2011 17:27:57 GMT

I used to configure uboot this way:

U-Boot > setenv loadaddr 0x90800000
U-Boot > setenv rd_loadaddr 0x90D00000
U-Boot > setenv bootcmd 'run bootcmd_SD; bootm ${loadaddr} ${rd_loadaddr}'
U-Boot > setenv bootcmd_SD 'mmc read 0 ${loadaddr} 0x800 0x2000; mmc read 0 ${rd_loadaddr} 0x3000 0x300;'

Can you, please, try it?

Re: Android on imx51 issues

TomErikson — Mon, 03 Oct 2011 17:53:03 GMT

this appears to work however I am not getting any output on my dvi monitor. This is the last chunk of output that i have.

EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
EXT4-fs (mmcblk0p5): recovery complete
EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (mmcblk0p6): recovery complete
EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts: (null)
usb 2-1.6: new high speed USB device using fsl-ehci and address 3
scsi0 : usb-storage 2-1.6:1.0
scsi 0:0:0:0: Direct-Access USB TO I DE/SATA Device 0009 PQ: 0 ANSI: 0
sd 0:0:0:0: [sda] Attached SCSI disk
usb wakeup is here
otg udc wakeup
android_usb gadget: high speed config #1: android

Re: Android on imx51 issues

TomErikson — Mon, 03 Oct 2011 18:43:26 GMT

I think the video not working is due to this env variable but I am not sure.

bootargs=console=ttymxc0,115200 gpu_memory=16M androidboot.console=ttymxc0 init=/init di1_primary calibration

Re: Android on imx51 issues

daiane_angolini — Mon, 03 Oct 2011 19:06:40 GMT

You're right.

You are using parameters for using WVGA. But you're using DVI instead.

Pleae, use this:

console=ttymxc0 init=/init androidboot.console=ttymxc0 di0_primary gpu_nommu, gpu_memory=32M video=mxcdi0fb:RGB24,1024x768M@60

di0_primary is for DVI

video=mxcdi0fb:RGB24,1024x768M@60 is the resolution and color.

Please, take a look on release notes to further info.

Re: Android on imx51 issues

TomErikson — Mon, 03 Oct 2011 19:59:29 GMT

thank you. Its all working now.