FreeBSD-10-STABLE hangs when booting from BeagleBone Black eMMC

[Ian Lepore]

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:   <ethaddr> 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 at 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