booting current from nano-neo/allwinner now failes

Fri Aug 3 08:32:36 UTC 2018

some time later - actually several hours - I made a new image and

- using latest ubldr and with boot.scr
  I think my problem is the sd image, it doesn’t like my MBR because as 
  opposed to you I get:
  …
  Probing all disk devices…
  Checking unit=0 slice=<auto> partition=<auto>…

as opposed tour case where after the … you get good.

- so switching to EFI it get stuck:

U-Boot SPL 2018.07 (Aug 01 2018 - 17:37:02 +0300)
DRAM: 512 MiB
Trying to boot from MMC1

U-Boot 2018.07 (Aug 01 2018 - 17:37:02 +0300) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyARM NanoPi NEO
DRAM:  512 MiB
MMC:   SUNXI SD/MMC: 0
Loading Environment from FAT... *** Warning - bad CRC, using default environment

Failed (-5)
In:    serial
Out:   serial
Err:   serial
Net:   phy interface0
eth0: ethernet at 1c30000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
scanning bus 0 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...
Found EFI removable media binary efi/boot/bootarm.efi
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disks on usb...
Disk usb0 not ready
Disk usb1 not ready
Disk usb2 not ready
Disk usb3 not ready
Scanning disks on mmc...
MMC Device 1 not found
MMC Device 2 not found
MMC Device 3 not found
Found 3 disks
493860 bytes read in 25 ms (18.8 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
## Starting EFI application at 42000000 ...
Consoles: EFI console  
FreeBSD/arm EFI loader, Revision 1.1
(Fri Aug  3 10:00:59 IDT 2018 danny at pe-44)

  Command line arguments: l
  EFI version: 2.70
  EFI Firmware: Das U-Boot (rev 0.00)
  Console: efi (0)
  Load Path: /\efi\boot\bootarm.efi
  Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/USB(0x6,0x0)/HD(1,0x01,0,0xc0f,0x1ffe0)
Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/USB(0x6,0x0)/HD(1,0x01,0,0xc0f,0x1ffe0)
Setting currdev to disk0p1:
Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/USB(0x6,0x0)/HD(2,0x01,0,0x20c2e,0x3df3c2)
Setting currdev to disk0p2:
ubenv not found
Loading /boot/defaults/loader.conf
/boot/kernel/kernel text=0x6cf66c data=0x68938+0x4f048 syms=[0x4+0x807e0+0x4+0xd2a75]
efi-autoresizecons: Neither Graphics Output Protocol nor Universal Graphics Adapter present

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...               
Using DTB provided by EFI at 0x47ffb000.
EHCI failed to shut down host controller.
Kernel entry at 0x53000180...
Kernel args: (null)
modulep: 0xc08e1000
relocation_offset 0

I will now try to build a new MBR/image …

cheers,

	danny

> On 3 Aug 2018, at 09:08, Daniel Braniss <danny at cs.huji.ac.il> wrote:
> 
> 
> 
>> On 3 Aug 2018, at 08:43, Emmanuel Vadot <manu at bidouilliste.com> wrote:
>> 
>> On Fri, 3 Aug 2018 08:16:06 +0300
>> Daniel Braniss <danny at cs.huji.ac.il <mailto:danny at cs.huji.ac.il>> wrote:
>> 
>>> 
>>> 
>>>> On 2 Aug 2018, at 21:45, Emmanuel Vadot <manu at bidouilliste.com> wrote
>>> ...
>>>> Did you also update ubldr.bin ? (not just ubldr)
>>> I did, and it went straight to net boot, and failed.
>>> 
>>> ...
>>>> 
>>>> Also please consider switching to efi boot, just deleting boot.scr and
>>>> copying loader.efi as EFI/BOOT/bootarm.efi is enough.
>>> 
>>> no problem, i?ll try ASAP.
>>> Q: this to the FAT partition?
>>> 
>>> my fat did not have the boot.scr, adding it did not change things
>> 
>> Based on your first mail you did have it
> 
> I was trying to answer too many questions with a one liner :-)
> I first tried booting an old sd image with latest current but old u-boot, old FAT stuff, and got stuck.
> I then upgraded the u-boot, got different results 
> then upgraded ubldr[.bin]
> different results but no success, adding the boot.scr didn’t seem to make a 
> difference.
> In any case I will try efi boot ASAP with latest ubldr.
> 
> 
>> 
>>> BTW, iboot.scr has some binary stuff, is that ok?
>> 
>> yes it's supposed to be a binary file.
>> 
>>> 
>>> thanks,
>>> 	danny
>>> 
>>>> 
>>>>> in any case I would like to help  but things are getting too complicated :-)
>>>>> 
>>>>> 
>>>>> thanks,
>>>>> 	danny
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> freebsd-arm at freebsd.org <mailto:freebsd-arm at freebsd.org> mailing list
>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>
>>>>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org <mailto:freebsd-arm-unsubscribe at freebsd.org>"
>>>> 
>>>> 
>>>> -- 
>>>> Emmanuel Vadot <manu at bidouilliste.com <mailto:manu at bidouilliste.com>> <manu at freebsd.org <mailto:manu at freebsd.org>>
>>> 
>> 
>> 
>> -- 
>> Emmanuel Vadot <manu at bidouilliste.com <mailto:manu at bidouilliste.com>> <manu at freebsd.org <mailto:manu at freebsd.org>>
> 
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"