Branch: poky/master Git rev: eaa5df34af42b6a37f6506847d0f3ef6ba0d298a steps: 1. download beagleboard images from http://autobuilder.yoctoproject.org/pub/nightly/20130703-3 2. this image could not bootup the beagleboard xM target. 3. build the beagleboard on my host again, the image still can not bootup the target The root cause of this issue is maybe gcc is upgrade to 4.8, but beagleboard kernel still 3.4 on this build. I found in yoctoproject mail list, mail "yocto Digest, Vol 33, Issue 95" said the qemuarm has upgrade to kernel 3.8 to fit for gcc4.8. So i think beagleboard kernel should be upgraded too. =================Beagleboard bootup log:=================== Texas Instruments X-Loader 1.5.0 (Jul 4 2013 - 17:36:22) Beagle xM Reading boot sector Loading u-boot.bin from mmc U-Boot 2011.06 (Jul 04 2013 - 17:36:32) OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0 *** Warning - readenv() failed, using default environment In: serial Out: serial Err: serial Beagle unknown 0x02 No EEPROM on expansion board Die ID #11c400229ff80000016830100e014012 Hit any key to stop autoboot: 0 OMAP3 beagleboard.org # OMAP3 beagleboard.org # OMAP3 beagleboard.org # setenv bootcmd 'mmc rescan 0; fatload mmc 0:1 0x80300000 uImage; bootm 0x80300000' OMAP3 beagleboard.org # setenv bootargs 'console=tty0 console=ttyO2,115200n8 root=/dev/mmcblk0p2 rootwait rootfstype=ext3 ro' OMAP3 beagleboard.org # boot reading uImage 4298168 bytes read ## Booting kernel from Legacy Image at 80300000 ... Image Name: Linux-3.4.36-yocto-standard Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4298104 Bytes = 4.1 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. <====It hangs here!!
We already have plans to update the beagleboard to the 3.8 kernel (and then to the 3.11+ kernel for Yocto 1.5). The board works out of the box in the mainline kernel, but the board configuration needs updated to work with the 3.8 kernel (you get a rolling oops with the Yocto config on 3.8, but the 3.8 yocto kernel with the omap3defconfig is fine). We just need to find someone with the board, and the time to do the uprev. (hint: it is unlikely to be me). I'll hold the bug in my name for now, but we need to find the resource, and then move on replacing the beagleboard as the reference ARM platform.
When i use 20130710-1 image (master: a63229917a5708de2d161aba0d67168ce0da6365), it could bootup the beagleboard. The kernel is "Linux beagleboard 3.4.52-yocto-standard"
beagleboard login: root root@beagleboard:~# uname -a Linux beagleboard 3.4.52-yocto-standard #1 Tue Jul 16 12:48:08 EDT 2013 armv7l GNU/Linux Agreed. This boots now.
root@beagleboard:~# uname -a Linux beagleboard 3.4.52-yocto-standard #1 Tue Jul 23 14:51:31 EDT 2013 armv7l GNU/Linux root@beagleboard:~# cat /proc/version Linux version 3.4.52-yocto-standard (bruce@yow-bashfiel-d2) (gcc version 4.8.1 (GCC) ) #1 Tue Jul 23 14:51:31 EDT 2013
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