On 9 July 2012 15:31, YongQin Liu <[email protected]> wrote:

> Hi, all
>
> I met a problem that the omapzoom and aosp build of panda can't be booted
> up in lava.
> here is the bug link:
> https://bugs.launchpad.net/lava-dispatcher/+bug/1012546
>
> When we passed the bootcmd and bootargs via u-boot, and run boot to boot
> the images deployed on partition3,
> the u-boot load kernel image and initrd file successfully, and displayed
> the line:
>      "Uncompressing Linux... done, booting the kernel."
> but after this line, it seems that the board rebooted and boot the master
> image as default again, not boot up the android image.
>
> I guess it has relation with uboot in master image because I have tried to
> use the MLO and u-boot.bin and u-boot.img in omapzoom build
> to replace the files on boot partition of master image, then I can boot
> the omapzoom and aosp build successfully.
> (also can boot the tracking build)
>
> What I did was as following:
> 1. deploy  omapzoom build to sdcard with linaro-android-media-create
> command
> 2. copy the MLO and u-boot.bin and u-boot.img  3 file from sdcard to
> someplace in local
> 3. use "./lava-create-master -r 2G panda" to create the sdcard used for
> master image
>     we can get the lava-create-master script from
> lp:lava-master-image-scripts
> 4. plug in the sdcard and boot the board
> 5. wait the board to complete the partition job.
>     after this, the uImage and uInitrd file in boot partition has been
> change,
>     and then the master image can be booted with the uboot files from
> omapzoom build
>     but I don't know why and what change has been done.
> 6. copy the MLO and u-boot.bin and u-boot.img 3 file to the boot partition
> of sdcard
> 7. plug the sdcard to the board and boot it, then it can be use to boot
> the tracking/omapzoom/aosp 3 builds of panda.
>
> The version original u-boot for master image is: U-Boot 2011.12 (Feb 16
> 2012 - 21:46:14)
> The u-boot version of omapzoom build is: U-Boot 2011.06 (Aug 20 2011 -
> 18:00:16).
> The u-boot version of tracking build is : U-Boot SPL 2012.04.01 (Jun 14
> 2012 - 08:05:54)
> The tracking build works fine with the original uboot of master image.
>
> So I guess there are some differences between the original uboot for
> master image and the uboot build in omapzoom build.
> Anyone know the details why it can not boot the omapzoom and aosp build on
> the 3rd partition,
> and if I can boot the omapzoom and aosp build of panda with the
> original u-boot of master image?
>

The kernel from aosp/omapzoom doesn't seem to boot with the uboot-SPL built
from linaro-uboot. The kernel booted with linaro-uboot seems to be giving
kernel panic. This was the reason I had to revert to older MLO and uboot
release.


>
> Thanks,
> Yongqin Liu
>
> _______________________________________________
> linaro-android mailing list
> [email protected]
> http://lists.linaro.org/mailman/listinfo/linaro-android
>
>
_______________________________________________
linaro-validation mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-validation

Reply via email to