I have always had to intervene in the boot process of FreeBSDARM on pandaboard before it boots to the login screen. And it takes minutes of trial-by-error.
They include interrupting the boot loader and typing "boot" then ENTER.
Below is the log via minicom:
I would hit any key to stop autoboot, type 'boot' then hit the ENTER button. At the next prompt/countdown, I would hit ENTER. I always have to do this trick several times before I get the image to boot to login otherwise, it would hang as shown above {nothing comes next after .....(based on LLVM 4.0.0)}}.
What do I need do? I have tried different OSes on ARM (Android, Boot2Gecko/FirefoxOS, Ubuntu, etc) and I never had this issue before.
They include interrupting the boot loader and typing "boot" then ENTER.
Below is the log via minicom:
Code:
U-Boot SPL 2017.01-rc3 (Jul 21 2017 - 14:48:43)
OMAP4430-GP ES2.1
Trying to boot from MMC1SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
reading u-boot.img
reading u-boot.img
U-Boot 2017.01-rc3 (Jul 21 2017 - 14:48:43 +0000)
CPU : OMAP4430-GP ES2.1
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0
reading uboot.env
** Unable to read "uboot.env" from mmc0:1 **
Using default environment
Net: No ethernet found.
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
reading boot.scr
** Unable to read file boot.scr **
reading uEnv.txt
** Unable to read file uEnv.txt **
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found FreeBSD U-Boot Loader (bin)
reading ubldr.bin
234640 bytes read in 16 ms (14 MiB/s)
## Starting application at 0x82000000 ...
Consoles: U-Boot console
Compatible U-Boot API signature found @0xbdf42c60
FreeBSD/armv6 U-Boot loader, Revision 1.2
(Fri Jul 21 15:04:31 UTC 2017 root@releng2.nyi.freebsd.org)
DRAM: 1024MB
Number of U-Boot devices: 1
U-Boot env: loaderdev not set, will probe all devices.
Found U-Boot device: disk
Probing all disk devices...
Checking unit=0 slice=<auto> partition=<auto>... good.
Booting from disk0s2a:
/boot/kernel/kernel text=0x5b7ec8 data=0x56440+0x4ccc0 syms=[0x4+0x8f120+0x4+0x90358]
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
Using DTB compiled into kernel.
Kernel entry at 0x82200180...
Kernel args: (null)
Copyright (c) 1992-2017 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.1-RELEASE #0 r321309: Fri Jul 21 15:10:30 UTC 2017
root@releng2.nyi.freebsd.org:/usr/obj/arm.armv6/usr/src/sys/PANDABOARD arm
FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0)
I would hit any key to stop autoboot, type 'boot' then hit the ENTER button. At the next prompt/countdown, I would hit ENTER. I always have to do this trick several times before I get the image to boot to login otherwise, it would hang as shown above {nothing comes next after .....(based on LLVM 4.0.0)}}.
What do I need do? I have tried different OSes on ARM (Android, Boot2Gecko/FirefoxOS, Ubuntu, etc) and I never had this issue before.