From owner-freebsd-arm@FreeBSD.ORG Sun Apr 27 17:16:28 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B36CACC7 for ; Sun, 27 Apr 2014 17:16:28 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7612FC4E for ; Sun, 27 Apr 2014 17:16:28 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1WeSgl-0008aD-DJ; Sun, 27 Apr 2014 17:16:27 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s3RHGPRk014023; Sun, 27 Apr 2014 11:16:25 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19m8/PGcIAtAwpc2CfizL6D Subject: Re: FreeBSD-10-STABLE hangs when booting from BeagleBone Black eMMC From: Ian Lepore To: Winston Smith In-Reply-To: References: Content-Type: text/plain; charset="us-ascii" Date: Sun, 27 Apr 2014 11:16:24 -0600 Message-ID: <1398618984.61646.165.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: FreeBSD ARM X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Apr 2014 17:16:28 -0000 On Sat, 2014-04-26 at 18:23 -0400, Winston Smith wrote: > After some success with 11-CURRENT on the BBB/eMMC, I switched back to > 10-STABLE but after building a crotchet-freebsd image (using Patrick's > script), I can't get it to boot from the eMMC. > > The image works ok on the SD card, but if I either use the new > copy-to-emmc.sh script, or build an eMMC specific image (using > BEAGLEBONE_BOOT_EMMC=y), it hangs during the boot (below). It seems > to fail when trying to access /boot/defaults/loader.conf > > Any ideas welcome! > > > --- > > U-Boot SPL 2013.04 (Apr 18 2014 - 20:25:05) > OMAP SD/MMC: 0 > reading bb-uboot.img > reading bb-uboot.img > > > U-Boot 2013.04 (Apr 18 2014 - 20:25:05) > > I2C: ready > DRAM: 512 MiB > WARNING: Caches not enabled > MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 > 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 > cpsw, usb_ether > Hit any key to stop autoboot: 0 > mmc1(part 0) is current device > SD/MMC found on device 1 > reading bb-uEnv.txt > reading bbubldr > 247304 bytes read in 35 ms (6.7 MiB/s) > reading bboneblk.dtb > 15278 bytes read in 6 ms (2.4 MiB/s) > Booting from mmc ... > ## Starting application at 0x88000054 ... > Consoles: U-Boot console > Compatible API signature found @9f242240 > MMC Device 2 not found > MMC Device 3 not found > MMC Device 2 not found > Number of U-Boot devices: 3 > > FreeBSD/armv6 U-Boot loader, Revision 1.2 > (root@freebsd, Fri Apr 25 20:27:41 EDT 2014) > DRAM: 512MB > > Device: disk > MMC Device 2 not found > MMC Device 3 not found > disk0: device open failed with error=2, handle=1 > > Device: net > cpsw Waiting for PHY auto negotiation to complete. done > link up on port 0, speed 100, full duplex I only have a BBW, no BBB to play with, so I can't help too much with this. I can say however that if you're having trouble with reading the eMMC in ubldr, the trouble is probably in u-boot. U-boot is still in memory when ubldr is running, and it serves as a kind of mini-bios, providing access to console, disk, and network IO. I heard a rumor a while back that Patrick Kelsey had some patches for u-boot to fix problems with probing for disk devices. It may be that they were only needed for older versions of u-boot, I'm not sure. -- Ian