On Mon, Mar 05, 2018 at 06:18:59PM +0000, Peter Robinson wrote:
> >>> Hi!
> >>> I'm trying to boot from u-boot on a Raspberry Pi 3. But for some reason
> >>> it
> >>> isn't autobooting on the SD-card.
> >>> Is it possible to get more debug output on the screen console? I don't
> >>> have
> >>> a serial console at the moment.
> >>> The output on the screen is:
> >>> Net: No ehternet found.
> >>> starting USB...
> >>> USB: Core Release 2.80a
> >>> scanning bus 0 for devices... 4 USB Devices found
> >>> scanning usb for storage devices... 0 Storage Device(s) found
> >>> Hit any key to stop autoboot: 0
> >>> U-Boot>
> >>> Shouldn't it mention mmc somewhere in the boot message?
> >>> The first command I type on the prompt is always failing, it's not
> >>> outputting anything. Just a new prompt on the next line. The next
> >>> commands i
> >>> type in are working. Which seems strange.
> >>> I got boot.scr set up right, except graphic settings which are wrong. It
> >>> is
> >>> booting the kernel when I type 'run bootcmd'. But only after I type in
> >>> another command before it.
> >>> It seems like it's not detecting the SD-card (mmc0) until I have typed
> >>> anything into the prompt.
> >>> Do I have to set any other env variable for it to autoboot? I would have
> >>> printed the output of printenv here, but since I don't have a serial
> >>> console, retyping everything is very time consuming.
> >>> printenv seems to have the right settings. It's basically a full console
> >>> screen of variables. It just doesn't seem to load them until I type in
> >>> another command before it.
> >>> boot_targets=mmc0 usb0 pxe dhcp
> >>> Which seems right to me.
> >>> I compiled the latest u-boot from github.
> >>> If you need more info please let me know and I'll post it.
> >>> Hope that anyone can point me in the right direction here. Would really
> >>> appreciate it.
> >> I'm seeing the same issues with 2018.03 rc3.
> >> I'm not sure what the issue is and I've not had time to investigate it
> >> further yet, but if you type "boot" and hit enter it should boot,
> >> sometimes you actually have to type it twice. It will boot but I'm not
> >> sure which bits here have causes this regression.
> > I do not see this at all on my RPi3. Maybe it's firmware version dependent?
> > Do you happen to have an image that always fails for you?
> 2018.03 rc3 with "2018-02-09" firmware (so fairly recent) fails for me.
2018.03 rc4 works fine on rpi_3 here with
20180221 / 9ab68bf218ffc84423a2591658260676d373259a
MD5 (bcm2710-rpi-3-b.dtb) = e5ee32f0c14cd23c327f1615df5d6bb4
MD5 (bootcode.bin) = 17efaf1c1ef89289168d71cdc8194982
MD5 (fixup.dat) = fe33157cedaf8130fa4587341553b26b
MD5 (start.elf) = 9c98e338a47e242f1726c508e60c4cc7
with 'boot_targets=usb0 mmc0 pxe dhcp' as root is on usb.
U-Boot 2018.03-rc4-00001-gc06b786faf (Mar 06 2018 - 23:30:47 +1100)
DRAM: 948 MiB
RPI 3 Model B (0xa02082)
MMC: mmc@7e202000: 0, sdhci@7e300000: 1
Loading Environment from FAT... OK
Net: No ethernet found.
USB0: Core Release: 2.80a
scanning bus 0 for devices... 4 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Hit any key to stop autoboot: 0
Device 0: Vendor: SanDisk Rev: 1.00 Prod: Ultra
Type: Removable Hard Disk
Capacity: 29327.3 MB = 28.6 GB (60062500 x 512)
... is now current device
Scanning usb 0:1...
Found EFI removable media binary efi/boot/bootaa64.efi
82812 bytes read in 90 ms (898.4 KiB/s)
## Starting EFI application at 01000000 ...
Scanning disk m...@7e202000.blk...
Card did not respond to voltage select!
Scanning disk sd...@7e300000.blk...
Disk sd...@7e300000.blk not ready
Scanning disk usb_mass_storage.lun0...
Found 6 disks
>> OpenBSD/arm64 BOOTAA64 0.11
booting sd0a:/bsd: 3990100+592528+580128+806208
U-Boot mailing list