Hi, all<div><br></div><div>I met a problem that the omapzoom and aosp build of panda can&#39;t be booted up in lava. </div><div>here is the bug link:</div><div><a href="https://bugs.launchpad.net/lava-dispatcher/+bug/1012546" target="_blank">https://bugs.launchpad.net/lava-dispatcher/+bug/1012546</a></div>

<div><br></div><div>When we passed the bootcmd and bootargs via u-boot, and run boot to boot the images deployed on partition3,</div><div>the u-boot load kernel image and initrd file successfully, and displayed the line:</div>
<div>     &quot;<span style="background-color:rgb(255,255,255);color:rgb(51,51,51);font-family:&#39;Ubuntu Mono&#39;,monospace;font-size:12px;line-height:18px;text-align:left">Uncompressing Linux... done, booting the kernel.</span>&quot;</div>
<div>but after this line, it seems that the board rebooted and boot the master image as default again, not boot up the android image.</div><div><br></div><div>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</div>
<div>to replace the files on boot partition of master image, then I can boot the omapzoom and aosp build successfully.</div><div>(also can boot the tracking build)</div><div><br></div><div>What I did was as following:</div>
<div>1. deploy  omapzoom build to sdcard with linaro-android-media-create command</div><div>2. copy the MLO and u-boot.bin and u-boot.img  3 file from sdcard to someplace in local</div><div>3. use &quot;./lava-create-master -r 2G panda&quot; to create the sdcard used for master image</div>
<div>    we can get the lava-create-master script from lp:lava-master-image-scripts</div><div>4. plug in the sdcard and boot the board</div><div>5. wait the board to complete the partition job.</div><div>    after this, the uImage and uInitrd file in boot partition has been change,</div>
<div>    and then the master image can be booted with the uboot files from omapzoom build</div><div>    but I don&#39;t know why and what change has been done.</div><div>6. copy the MLO and u-boot.bin and u-boot.img 3 file to the boot partition of sdcard</div>
<div>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.</div><div><br></div><div>The version original u-boot for master image is: <span style="background-color:rgb(255,255,255);color:rgb(68,68,68);font-size:13px">U-Boot 2011.12 (Feb 16 2012 - 21:46:14)</span></div>
<div>The u-boot version of omapzoom build is: <span style="background-color:rgb(255,255,255);color:rgb(68,68,68);font-size:13px">U-Boot 2011.06 (Aug 20 2011 - 18:00:16).</span></div><div>The u-boot version of tracking build is :<span style="background-color:rgb(255,255,255);color:rgb(68,68,68);font-size:13px"> </span><font color="#444444">U-Boot SPL 2012.04.01 (Jun 14 2012 - 08:05:54)</font></div>
The tracking build works fine with the original uboot of master image.<div><font color="#444444"><br></font></div>So I guess there are some differences between the original uboot for master image and the uboot build in omapzoom build.<div>
Anyone know the details why it can not boot the omapzoom and aosp build on the 3rd partition,</div><div>and if I can boot the omapzoom and aosp build of panda with the original u-boot of master image?</div><div><br></div>
<div><br></div><div>Thanks,</div><div>Yongqin Liu</div>