Poky: master: 5745e45b18e5099e94b4d5a73bc97dc6d4cdc91f Steps: 1. download beagleboard core-image-sato-sdk image from http://autobuilder.yoctoproject.org/pub/releases/1.5_M4.rc2/machines/beagleboard/ 2. use this image to boot up beagleboard xM, boot up failed. It hangs at loading u-boot.bin: Texas Instruments X-Loader 1.5.0 (Aug 28 2013 - 06:34:32) Beagle xM Reading boot sector Loading u-boot.bin from mmc This is a regression issue, 1.5M3_rc1 image worked well, its poky commit number is: 9de0ad47462c13ac4a2d73e12e92be6c1b4e0415
1.5_M4.rc2 upgraded u-boot version to 2013.07 (./meta/recipes-bsp/u-boot/u-boot_2013.07.bb). And this version of u-boot may be not compatible with x-loader. It seems that u-boot 2013.7 has its own MLO file after building. Please use the MLO file in u-boot building directory to test on xM board. Maybe we should give up x-loader from building images and replace it with MLO from u-boot.
I thought that we had marked 2013.07 as DEFAULT_PREFERENCE = "-1", apparently it not. If liming suggestion does not work we have options below. So we have 2 choices, either patch it with DEFAULT_PREFERENCE or add a PREFERRED_VERSION_u_boot ?= "v2011.06%" to the beagleboard.conf file, this is probably the preferred option.
OK
(In reply to comment #1) > 1.5_M4.rc2 upgraded u-boot version to 2013.07 > (./meta/recipes-bsp/u-boot/u-boot_2013.07.bb). And this version of u-boot > may be not compatible with x-loader. > It seems that u-boot 2013.7 has its own MLO file after building. Please use > the MLO file in u-boot building directory to test on xM board. > > Maybe we should give up x-loader from building images and replace it with > MLO from u-boot. Does this work? If it does we could get rid of old versions.
Hi all, I tried liming's workaround. It works. But it needs to replace 2 files. MLO and u-boot.bin workaround step: 1. build u-boot: bitbake u-boot 2. copy tmp/work/beagleboard-poky-linux-gnueabi/u-boot/v2013.07+gitAUTOINC+62c175fbb8-r0/git/MLO to replace MLO file 3. copy tmp/work/beagleboard-poky-linux-gnueabi/u-boot/v2013.07+gitAUTOINC+62c175fbb8-r0/git/u-boot.img to replace u-boot.bin 4. Then the beagleboard could be boot up. But since this workaround used u-boot.img replace u-boot.bin, i am not sure whether it is necessary to continue the beagleboard test with 1.5_M4.rc2 image.
Hey guys, can you update the target milestone? Currently it is set to 1.1.2. Thanks!
poky commit id "3aa68fd9014a4745486a2e8ab03292b39ce11862" has resolved the issue. We should use the MLO of latest u-boot, not x-load.
The final release candidate for 1.5: 1.5_M5.rc8 did manage to boot, even though it had some issues with X, network and USB. Regardless, this issue does not happen. Marking as VERIFIED. The beagleboard status for 1.5: 1.5_M5.rc8 can be seen here: https://wiki.yoctoproject.org/wiki/WW41_-_2013-10-08_-_Full_Pass_Release_1.5_M5.rc8#Beagleboard:_core-image-sato-sdk
Thanks.