2884 2012-08-03 03:03:01 +0000 Pandaboard fails to boot 2012-11-09 15:17:30 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-meta-ti 1.3 Other arm VERIFIED FIXED https://lists.yoctoproject.org/pipermail/yocto/2012-July/010540.html Medium normal 1.3 M4 1 maniacbug denis corneliux.stoicescu meta.mr.watcher meta.watcher sgw --- --- --- oldest_to_newest 23779 0 maniacbug 2012-08-03 03:03:01 +0000 See https://lists.yoctoproject.org/pipermail/yocto/2012-July/010540.html Using this configuration, master from today, core-image-sato fails to boot. meta-yocto = "master:c4a7517f8ae6e176a0b8e59b1176cf65bb45aa78" meta-ti = "master:d3ff5630a74640f46ca2ceaef1aa1baa86b9b795" It is suggested that gcc 4.7 is to blame. This problem does not exist on the denzil release. U-Boot 2011.12-dirty (Aug 02 2012 - 16:46:30) CPU : OMAP4430 ES2.3 Board: OMAP4 Panda I2C: ready DRAM: 1 GiB MMC: OMAP SD/MMC: 0 Using default environment In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 reading boot.scr ** Unable to read "boot.scr" from mmc 0:1 ** reading uImage 4176540 bytes read Booting from mmc0 ... ## Booting kernel from Legacy Image at 82000000 ... Image Name: Linux-3.1.0 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4176476 Bytes = 4 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. *** NO FURTHER OUTPUT *** 26879 1 denis 2012-10-25 02:07:57 +0000 The kernel for Pandaboard in meta-ti has been upgraded from 3.1 to 3.4, which does not exhibit problems with GCC 4.7 27264 2 corneliux.stoicescu 2012-11-06 15:18:40 +0000 I sent an email to the bug owner in order to set this to verified. Waiting for feedback. 27327 3 corneliux.stoicescu 2012-11-09 15:17:30 +0000 As per no input from the owner, I am setting this from resolved to verified. Feel free to reopen if necessary.