Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Oct 2019 10:18:32 +0200
From:      Emmanuel Vadot <manu@bidouilliste.com>
To:        Gary Otten <gdotten@gmail.com>
Cc:        freebsd-uboot@freebsd.org
Subject:   Re: u-boot-a64-olinuxino difference between U-Boot SPL 2019.10 & U-Boot SPL 2019.07
Message-ID:  <20191025101832.2b442ecdbf10b68edd7a78ea@bidouilliste.com>
In-Reply-To: <CABZQu%2BgR_LPMSxJoZ0XnOqXecwK=QUnd%2B-TUQC5RgM4GSNKFmA@mail.gmail.com>
References:  <CABZQu%2BgR_LPMSxJoZ0XnOqXecwK=QUnd%2B-TUQC5RgM4GSNKFmA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

 Hi Gary,

On Thu, 24 Oct 2019 19:37:48 -0400
Gary Otten <gdotten@gmail.com> wrote:

> The 2019.10 u-boot I compiled with with the a64-olinuxino_defconfig
> configuration doesn't find the UFS partition the old one 2019.07 that is in
> the ports pre-compiled does.  Is there a configuration setting that I must
> set before compiling?  Or did I overlook something else? Is my SD card
> layout appropriate, or causing the problem?
> 
> ***********************************************************************************
> U-Boot SPL 2019.07  (from the pre-made package)    (this works)
> (partial bootup txt)
> 
>   Initializing modules: ZFS UFS
>    Load Path: /efi\boot\bootaa64.efi
>    Load Device:
> /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x800,0x64000)
>    Probing 3 block devices.....* done
>     ZFS found no pools
>     UFS found 1 partition
> Consoles: EFI console
> FreeBSD/arm64 EFI loader, Revision 1.1
> 
>    Command line arguments: loader.efi
>    EFI version: 2.70
>    EFI Firmware: Das U-Boot (rev 8217.1792)
>    Console: efi (0)
>  Load Device:
> /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(2,0x01,0,0x96800,0x1c8b800)
> Trying ESP:
> /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(2,0x01,0,0x96800,0x1c8b800)
> Setting currdev to disk0p2:
> Loading /boot/defaults/loader.conf
> Loading /boot/device.hints
> Loading /boot/loader.conf
> Loading /boot/loader.conf.local
> -
> Loading kernel...
> 
> *******************************************************************************
> 
> 
>   U-Boot SPL 2019.10 (Compiled by myself)
>   (partial bootup txt)
> 
>  Initializing modules: ZFS UFS
>    Load Path: /efi\boot\bootaa64.efi
>    Load Device:
> /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x800,0x64000)
>    Probing 3 block devices...... done
>     ZFS found no pools
>     UFS found no partitions
> Failed to load '/boot/loader.efi'
> panic: No bootable partitions found!
> ## Application terminated, r = 1
> EFI LOAD FAILED: continuing...
> Card did not respond to voltage select!
> Device 0: unknown device
> ethernet@1c30000 Waiting for PHY auto negotiation to complete.........
> TIMEOUT !
> BOOTP broadcast 1
> BOOTP broadcast 2
> BOOTP broadcast 3
> ****************************************************************************************************
> My SD card layout.
> 
> da2   MBR (15G)
>            free  (993k)
>     1  efi (200M)
>            free (100M)
>     2 freebsd  (active)  (14G)
> 
> 
> da2s2    BSD (14G)
>      1  freebsd-ufs   (14G)
> _______________________________________________
> freebsd-uboot@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-uboot
> To unsubscribe, send any mail to "freebsd-uboot-unsubscribe@freebsd.org"

 You are using boot1.efi as EFI/BOOT/BOOTAA64.EFI while you should use
loader.efi directly.
 U-Boot 2019.10 changed some stuff related to alignement for IO and
only loader.efi was updated to cope with this changed.
 boot1.efi was never really supported on aarch64.

 Cheers,

-- 
Emmanuel Vadot <manu@bidouilliste.com>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191025101832.2b442ecdbf10b68edd7a78ea>