From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from vms173023pub.verizon.net (vms173023pub.verizon.net [206.46.173.23]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 9A98AE00B83 for ; Sun, 13 Apr 2014 19:33:46 -0700 (PDT) Received: from gandalf.denix.org ([unknown] [71.191.205.189]) by vms173023.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0N4000J661RSDV80@vms173023.mailsrvcs.net> for yocto@yoctoproject.org; Sun, 13 Apr 2014 21:33:29 -0500 (CDT) Received: by gandalf.denix.org (Postfix, from userid 1000) id A89EB201C0; Sun, 13 Apr 2014 22:33:28 -0400 (EDT) Date: Sun, 13 Apr 2014 22:33:28 -0400 From: Denys Dmytriyenko To: Gary Thomas Message-id: <20140414023328.GY3370@denix.org> References: <534A54F0.5020203@mlbassoc.com> MIME-version: 1.0 In-reply-to: <534A54F0.5020203@mlbassoc.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Yocto Project Subject: Re: BBB doesn't boot X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Apr 2014 02:33:46 -0000 Content-type: text/plain; charset=us-ascii Content-disposition: inline On Sun, Apr 13, 2014 at 03:12:16AM -0600, Gary Thomas wrote: > I just tried building (core-image-sato) for my BeagleBoneBlack > using the latest Poky/Yocto master: > > Build Configuration: > BB_VERSION = "1.23.0" > BUILD_SYS = "i686-linux" > NATIVELSBSTRING = "Fedora-13" > TARGET_SYS = "arm-poky-linux-gnueabi" > MACHINE = "beaglebone" > DISTRO = "poky" > DISTRO_VERSION = "1.6+snapshot-20140411" > TUNE_FEATURES = "armv7a vfp neon callconvention-hard cortexa8" > TARGET_FPU = "vfp-neon" > meta > meta-yocto > meta-yocto-bsp = "master:863cc7483f5ee43189537940de8ee5c0964d24cc" > > This built the kernel using SRCREV 928d7b2dda > > I followed the bring-up instructions from README.hadware and the > boot failed to even start the kernel. Here's what I see: > > =============================== boot log ========================================= > U-Boot 2013.07 (Apr 11 2014 - 15:03:04) > > I2C: ready > DRAM: 512 MiB > WARNING: Caches not enabled > NAND: 0 MiB > MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 > *** Warning - readenv() failed, using default environment > > musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) > musb-hdrc: MHDRC RTL version 2.0 > musb-hdrc: setup fifo_mode 4 > musb-hdrc: 28/31 max ep, 16384/16384 memory > USB Peripheral mode controller at 47401000 using PIO, IRQ 0 > musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) > musb-hdrc: MHDRC RTL version 2.0 > musb-hdrc: setup fifo_mode 4 > musb-hdrc: 28/31 max ep, 16384/16384 memory > USB Host mode controller at 47401800 using PIO, IRQ 0 > Net: not set. Validating first E-fuse MAC > Phy not found > PHY reset timed out > cpsw, usb_ether > Hit any key to stop autoboot: 0 > mmc0 is current device > SD/MMC found on device 0 > reading uEnv.txt > ** Unable to read file uEnv.txt ** > 4981688 bytes read in 613 ms (7.7 MiB/s) > 29192 bytes read in 46 ms (619.1 KiB/s) > Booting from mmc ... > ## Booting kernel from Legacy Image at 80200000 ... > Image Name: Linux-3.14.0-yocto-standard > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 4981624 Bytes = 4.8 MiB > Load Address: 80008000 > Entry Point: 80008000 > Verifying Checksum ... OK > ## Flattened Device Tree blob at 80f80000 > Booting using the fdt blob at 0x80f80000 > Loading Kernel Image ... OK > Using Device Tree in place at 80f80000, end 80f8a207 > > Starting kernel ... > ================================================================================== > > Any ideas what I've done wrong? Hmm, everything looks sane. What revision is your BBB? And did you press USER/BOOT button or erased eMMC partition per instructions? -- Denys