im53 QSB Android Boot hangs up

[TugrulGuclu]

Hello

Finally I managed to build android image for imx53 QSB but now I can not get into  Android Home Screen because CPU hangs up somewhere. I believe it's is due to touch  screen calibration but could not find how to disable touch screeen calibration at startup. I know it's about bootargs in uBoot but documentation is not clear enought to understand the way yo disable it. Attached is the serial log during boot up.

Serial log of boot

Last traces are these:

Freeing init memory: 196K
init: cannot open '/initlogo.rle'
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: nodelalloc
EXT4-fs (mmcblk0p6): recovery complete
EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts: (null)

[rlorriaux]

You need to enable "Stay awake" in Settings | Applications | Development

[EricNelson]

I'm not sure if it's related, but I found that a similar issue was triggered by trying to mount an EXT4 partition that didn't exist on an i.MX6 SABRE Lite board.

    http://boundarydevices.com/android-r13-4-ga-for-i-mx6-in-stages-stage-2-booting-sd-card/#update

In the i.MX6 case, the system call <tt>mount_bdev</tt> wouldn't return until a wake event (hard key or USB plug/unplug).

A mount error message was generated, but the system call didn't return. It appears that the system entered a sleep state at some point in the return path. More details are available in this Linaro bug report.

     Comment #7 : Bug #966114 : Bugs : Linaro Android

[TugrulGuclu]

VGA connection is suspended after a while.

I think it's about suspend mode. Do you know how to disable suspend mode ?

[TugrulGuclu]

It worked.

I changed set_display=run vga

[TugrulGuclu]

Hi

I modified them too. Below is the output from U-Boot>printenv

MX53-LOCO U-Boot > printenv vga
vga=setenv bootargs di1_primary video=mxcdi1fb:GBR24,1024x768@60 vga
MX53-LOCO U-Boot > vga=setenv bootargs di1_primary video=mxcdi1fb:GBR24,1024x768@60 vga
Unknown command 'vga=setenv' - try 'help'
MX53-LOCO U-Boot > printenv
baudrate=115200
loadaddr=0x70800000
netdev=eth0
ethprime=FEC0
uboot=u-boot.bin
kernel=uImage
loadaddr=0x70800000
rd_loadaddr=0x70D00000
nfsroot=/opt/eldk/arm
bootargs_base=setenv bootargs console=ttymxc0,115200
hdmi_720p=setenv bootargs ${bootargs} di0_primary video=mxcdi0fb:RGB24,1280x720M@60 hdmi gpu_nommu gpu_memory=64M
hdmi_1080p=setenv bootargs ${bootargs} di0_primary video=mxcdi0fb:RGB24,1080P60 hdmi gpu_nommu gpu_memory=64M
claa_lcd=setenv bootargs ${bootargs} di0_primary video=mxcdi0fb:RGB565,CLAA-WVGA calibration
set_display=run lcd
bootargs_android=setenv bootargs ${bootargs} init=/init androidboot.console=ttymxc0
bootcmd=run bootcmd_SD
bootcmd_SD=run bootcmd_SD1 bootcmd_SD2
bootcmd_SD1=run bootargs_base set_display bootargs_android
bootcmd_SD2=mmc read 0 ${loadaddr} 0x800 0x2000;mmc read 0 ${rd_loadaddr} 0x3000 0x300;bootm ${loadaddr} ${rd_loadaddr}
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
bootcmd_android_recovery=run bootargs_base bootargs_android_recovery;mmc read 0 ${loadaddr} 0x800 0x2000;bootm
bootargs_android_recovery=setenv bootargs ${bootargs} init=/init root=/dev/mmcblk0p4 rootfs=ext4
ethact=FEC0
bootdelay=3
bootdelay=3
lcd=setenv bootargs di0_primary calibration
vga=setenv bootargs di1_primary video=mxcdi1fb:GBR24,1024x768@60 vga
stdin=serial
stdout=serial
stderr=serial

[AhmetYUCE]

I'm using iMX53-QSB without touchscreen using vga monitor. Didn't get such an issue. The only change i've made to u-boot params was changing default display from lcd to vga.

[TugrulGuclu]

Hi

I removed my USB  keyboard - nothing happened. 

Then from uBoot settings I removed "calibration" in lcd variable. Now it still hangs up but now traces are different. see the attached file please

[AhmetYUCE]

Try booting by removing any connected USB device. Be patient, first boot takes some time, since some SD card contents recreated. (i think because of dex file decompression or smtg similar. )