PINE64+ 2GB - with U-Boot SPL 2019.10 - bootaa64.efi do not find UFS partition

Sat Oct 12 14:39:50 UTC 2019

On 10/12/19 11:10 AM, Emmanuel Vadot wrote:
> On Sat, 12 Oct 2019 10:03:10 +0200
> Henri Hennebert <hlh at restart.be> wrote:
> 
>> On 10/11/19 1:50 PM, Emmanuel Vadot wrote:
>>> On Fri, 11 Oct 2019 13:36:26 +0200
>>> Henri Hennebert via freebsd-arm <freebsd-arm at freebsd.org> wrote:
>>>
>>>> U-Boot SPL 2019.10 (Oct 10 2019 - 18:05:29 +0200)
>>>> DRAM: 2048 MiB
>>>> Trying to boot from MMC1
>>>> NOTICE:  BL31: v2.0(release):
>>>>
>>>>>> FreeBSD EFI boot block
>>>>       Loader path: /boot/loader.efi
>>>>
>>>>       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,0x403b,0x20000)
>>>>       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
>>>>
>>>> Revert to U-Boot SPL 2019.07 with the same bootaa64.efi boot OK
>>>>
>>>> Henri
>>>
>>>    Is this boot1.efi that you've installed as bootaa64.efi ?
>>>
>>>    Try installing loader.efi directly.
>>>
>>
>> I try with loader.efi as bootaa64.efi to no avail:
>>
>> U-Boot 2019.10 (Oct 10 2019 - 18:05:29 +0200) Allwinner Technology
>>
>> CPU:   Allwinner A64 (SUN50I)
>> Model: Pine64+
>> DRAM:  2 GiB
>> MMC:   mmc at 1c0f000: 0
>> Loading Environment from FAT... *** Warning - bad CRC, using default
>> environment
>>
>> In:    serial
>> Out:   serial
>> Err:   serial
>> Net:   phy interface7
>> eth0: ethernet at 1c30000
>> starting USB...
>> Bus usb at 1c1a000: USB EHCI 1.00
>> Bus usb at 1c1a400: USB OHCI 1.0
>> Bus usb at 1c1b000: USB EHCI 1.00
>> Bus usb at 1c1b400: USB OHCI 1.0
>> scanning bus usb at 1c1a000 for devices... 1 USB Device(s) found
>> scanning bus usb at 1c1a400 for devices... 1 USB Device(s) found
>> scanning bus usb at 1c1b000 for devices... EHCI timed out on TD -
>> token=0x80008d80
>>
>>         USB device not accepting new address (error=22)
>> 1 USB Device(s) found
>> scanning bus usb at 1c1b400 for devices... 1 USB Device(s) found
>>          scanning usb for storage devices... 0 Storage Device(s) found
>> Hit any key to stop autoboot:  0
>> switch to partitions #0, OK
>> mmc0 is current device
>> Scanning mmc 0:1...
>> 31963 bytes read in 3 ms (10.2 MiB/s)
>> Found EFI removable media binary efi/boot/bootaa64.efi
>> Scanning disk mmc at 1c0f000.blk...
>> Found 3 disks
>> BootOrder not defined
>> EFI boot manager: Cannot load any image
>> 607648 bytes read in 29 ms (20 MiB/s)
>> Consoles: EFI console
>> efipart_readwrite: rw=1, blk=0 size=1 status=2
>> efipart_readwrite: rw=1, blk=64 size=1 status=2
>> efipart_readwrite: rw=1, blk=1 size=1 status=2
>> efipart_readwrite: rw=1, blk=30883840 size=1 status=2
>> efipart_readwrite: rw=1, blk=0 size=1 status=2
>> efipart_readwrite: rw=1, blk=64 size=1 status=2
>> efipart_readwrite: rw=1, blk=1 size=1 status=2
>> efipart_readwrite: rw=1, blk=30883840 size=1 status=2
>> FreeBSD/arm64 EFI loader, Revision 1.1
>>
>>      Command line arguments: loader.efi
>>      EFI version: 2.80
>>      EFI Firmware: Das U-Boot (rev 8217.4096)
>>      Console: efi (0)
>>      Load Path: /efi\boot\bootaa64.efi
>>      Load Device:
>> /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,MBR,0x2b49e90d,0x403b,0x20000)
>> Trying ESP:
>> /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,MBR,0x2b49e90d,0x403b,0x20000)
>> Setting currdev to disk0p1:
>> efipart_readwrite: rw=1, blk=0 size=1 status=2
>> efipart_readwrite: rw=1, blk=64 size=1 status=2
>> efipart_readwrite: rw=1, blk=1 size=1 status=2
>> efipart_readwrite: rw=1, blk=30883840 size=1 status=2
>> efipart_readwrite: rw=1, blk=0 size=1 status=2
>> efipart_readwrite: rw=1, blk=64 size=1 status=2
>> efipart_readwrite: rw=1, blk=1 size=1 status=2
>> efipart_readwrite: rw=1, blk=30883840 size=1 status=2
>> Trying:
>> /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(2,MBR,0x2b49e90d,0x24400,0x1d4f800)
>> Setting currdev to disk0p2:
>> efipart_readwrite: rw=1, blk=0 size=1 status=2
>> efipart_readwrite: rw=1, blk=64 size=1 status=2
>> efipart_readwrite: rw=1, blk=1 size=1 status=2
>> efipart_readwrite: rw=1, blk=30883840 size=1 status=2
>> efipart_readwrite: rw=1, blk=0 size=1 status=2
>> efipart_readwrite: rw=1, blk=64 size=1 status=2
>> efipart_readwrite: rw=1, blk=1 size=1 status=2
>> efipart_readwrite: rw=1, blk=30883840 size=1 status=2
>> Failed to find bootable partition
>> ## Application terminated, r = 14 in 1 seconds
>> EFI LOAD FAILED: continuing...
>>
>> Device 0: unknown device
>> ethernet at 1c30000 Waiting for PHY auto negotiation to complete.... done
>> BOOTP broadcast 1
>> BOOTP broadcast 2
> 
>   You must have some problem either with your sd card or something weird
> in your partitioning. I've just checked the latest snapshot from
> yesterday which have u-boot v2019.10 and it worked flawlessly on my
> unit.
> 

I put FreeBSD-12.1-RC1-arm64-aarch64-PINE64.img on the sd card. It is 
created with u-boot 2019-07 and boot correctly.

If I put u-boot 2019-10 the same problem occurs.