On Thu, Mar 3, 2011 at 8:02 PM, Alexander Sack <a...@linaro.org> wrote: > On Thu, Mar 3, 2011 at 9:14 AM, Jeremy Chang <jeremy.ch...@linaro.org> wrote: >> On Thu, Mar 3, 2011 at 3:43 PM, John Stultz <john.stu...@linaro.org> wrote: >>> On Thu, 2011-03-03 at 15:27 +0800, Jeremy Chang wrote: >>>> Hi, John: >>>> Thanks. Though the problem for me is still the same. >>>> >>>> I tried in uboot with following commands. >>>> # mmc init >>>> # setenv bootargs 'console=ttyO2,115200n8 mem=256M >>>> root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait init=/init' >>>> # fatload mmc 1 0x82000000 uImage >>>> # bootm 0x82000000 >>>> >>>> Any idea about if there could be any other difference in between? >>>> Thanks. >>> >>> I'm baffled. Do you have any further details on the beagleboard xm >>> revision? I think mine is an A2. >> From the box and the sticker on the board, it says Rev B. >> So it looks like the u-boot I used from rowboat[1] shows RevA as >> below messages, > > I tarred up the boot/vfat partition that i successfully used for > booting our android beagle build: > > http://people.linaro.org/~asac/tmp/beagle-boot.tar.gz > > its > 1. linaro u-boot with a good boot.scr that boots android from mmcblk0p2 > 2. uImage built from johns tree using android omap3 defconfig ... > > see if that changes anything (i see output on terminal for whole boot process)
Hi, Alexander: Thanks for the help. It turns out that just after I changed to using the Android toolchain from 4.4.3 to 4.4.0 , this problem is solved. So this may be the toolchain and the kernel source code compatible issue. Regards, -Jeremy > > -- > > - Alexander > _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
