Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 2 Sep 2018 09:39:10 +0300
From:      Daniel Braniss <danny@cs.huji.ac.il>
To:        Emmanuel Vadot <manu@bidouilliste.com>
Cc:        Jakob Alvermark <jakob@alvermark.net>, "freebsd-arm@freebsd.org" <arm@freebsd.org>
Subject:   Re: allwinner/nanopi neo boot issues
Message-ID:  <9EE16E32-AE1F-49DC-BF85-2AF4ECA00B0D@cs.huji.ac.il>
In-Reply-To: <20180901224629.3997b4de29e4bf5f893dac79@bidouilliste.com>
References:  <42AA3AE2-E101-4B7B-B373-BEC178321671@cs.huji.ac.il> <C745EB05-187D-4821-8CE3-5ADEF055231A@cs.huji.ac.il> <0fdbd315-f37d-e3d3-9309-612f53c4d379@alvermark.net> <8459A9BA-183A-461B-9050-3631C51218F9@cs.huji.ac.il> <474af48e-ba82-62ce-34a3-70dfc4382723@alvermark.net> <20180901224629.3997b4de29e4bf5f893dac79@bidouilliste.com>

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


> On 1 Sep 2018, at 23:46, Emmanuel Vadot <manu@bidouilliste.com> wrote:
>=20
> On Sat, 1 Sep 2018 15:50:25 +0200
> Jakob Alvermark <jakob@alvermark.net <mailto:jakob@alvermark.net>> =
wrote:
>=20
>> On 8/29/18 2:22 PM, Daniel Braniss wrote:
>>>=20
>>>=20
>>>> On 29 Aug 2018, at 15:17, Jakob Alvermark <jakob@alvermark.net =
<mailto:jakob@alvermark.net>=20
>>>> <mailto:jakob@alvermark.net <mailto:jakob@alvermark.net>>> wrote:
>>>>=20
>>>>=20
>>>> On 8/24/18 10:02 AM, Daniel Braniss wrote:
>>>>>=20
>>>>>> On 24 Aug 2018, at 09:34, Daniel Braniss <danny@cs.huji.ac.il =
<mailto:danny@cs.huji.ac.il>=20
>>>>>> <mailto:danny@cs.huji.ac.il <mailto:danny@cs.huji.ac.il>>> wrote:
>>>>>>=20
>>>>>> hi,
>>>>>> with the latest current r338243 no longer boots via ubldr, efi =
does
>>>>>> but with overlays I have to manually enter the root partition.
>>>>>>=20
>>>>>> this is where it hangs via ubldr:
>>>>>>=20
>>>>>> Autoboot in 8 seconds, hit [Enter] to boot or any other key to =
stop
>>>>>>=20
>>>>>> Loading kernel...
>>>>>> /boot/kernel/kernel text=3D0x8a0950 data=3D0xae160+0x184520=20
>>>>>> syms=3D[0x4+0xa6d70+0x4+0x109f17]
>>>>>> Loading configured modules...
>>>>>> /boot/entropy size=3D0x1000
>>>>>> /boot/dtb/sun8i-h3-nanopi-neo.dtb size=3D0x601b
>>>>>> Loaded DTB from file 'sun8i-h3-nanopi-neo.dtb'.
>>>>>> Kernel entry at 0x42400180...
>>>>>> Kernel args: (null)
>>>>>>=20
>>>>>> older - r337232 - boots fine,
>>>>>>=20
>>>>>> any ideas where to look?
>>>>> should have done an update before writing!
>>>>>=20
>>>>> with the latest (and greatest) all is back to normal!
>>>>> so now on to test orange pi one(h3), nanopi neo 2 (h5) and nanopi=20=

>>>>> neo a64
>>>>>=20
>>>>> thanks,
>>>>> danny
>>>>=20
>>>>=20
>>>> Hi,
>>>>=20
>>>>=20
>>>> I am trying to get an Orange Pi R1 going, I get the same.
>>>>=20
>>>> Loading kernel...
>>>> /boot/kernel/kernel text=3D0x89ee40 data=3D0xae620+0x1f5ba0=20
>>>> syms=3D[0x4+0xa6d20+0x4+0x109e51]
>>>> Loading configured modules...
>>>> Could not load one or more modules!
>>>> /boot/dtb/sun8i-h2-plus-orangepi-r1.dtb size=3D0x6333
>>>> Loaded DTB from file 'sun8i-h2-plus-orangepi-r1.dtb'.
>>>> Kernel entry at 0x42400180...
>>>> Kernel args: (null)
>>>>=20
>>>> This is at r338369.
>>>>=20
>>>>=20
>>>=20
>>> try booting via efi;
>>> make sure to copy /boot/loader.efi to =
/boot/msdos/EFI/BOOT/bootaa64.efi
>>> remove /boot/msdos/boot.scr
>>> good luck,
>>> danny
>>=20
>> I tried the ALPHA4 snapshot, this happens:
>>=20
>> Hit any key to stop autoboot:  0
>> switch to partitions #0, OK
>> mmc0 is current device
>> Scanning mmc 0:1...
>> 25395 bytes read in 4 ms (6.1 MiB/s)
>> Found EFI removable media binary efi/boot/bootarm.efi
>> 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
>> 508704 bytes read in 26 ms (18.7 MiB/s)
>> ## Starting EFI application at 42000000 ...
>> Consoles: EFI console
>> failed to allocate staging area: 14
>> failed to allocate staging area
>> ## Application terminated, r =3D 5
>> EFI LOAD FAILED: continuing...
>>=20
>>=20
>> Tried manually loading ubldr.bin:
>>=20
>> =3D> fatload mmc 0 0x42000000 ubldr.bin
>> 306972 bytes read in 15 ms (19.5 MiB/s)
>> =3D> go 0x42000000
>> Loading kernel...
>> /boot/kernel/kernel text=3D0x85d7f0 data=3D0xaf620+0x24e1e0=20
>> syms=3D[0x4+0xa87d0+0x4+0x10c603]
>> Loading configured modules...
>> /boot/kernel/umodem.ko text=3D0x1bf4 text=3D0x1320 data=3D0x1080+0xf88=20=

>> syms=3D[0x4+0x1070+0x4+0xbcd]
>> loading required module 'ucom'
>> /boot/kernel/ucom.ko text=3D0x1f8c text=3D0x2e90 data=3D0x1080+0x17bc=20=

>> syms=3D[0x4+0x14f0+0x4+0xc5d]
>> Could not load one or more modules!
>>=20
>> Hit [Enter] to boot immediately, or any other key for command prompt.
>> Booting [/boot/kernel/kernel]...
>> /boot/dtb/sun8i-h2-plus-orangepi-r1.dtb size=3D0x6333
>> Loaded DTB from file 'sun8i-h2-plus-orangepi-r1.dtb'.
>> Kernel entry at 0x42400180...
>> Kernel args: (null)
>>=20
>> And then it reboots...
>=20
> I've just re-introduce the cache patches for u-boot as it appears that
> some boards needs them (I've probably tested the wrong unpatched =
u-boot
> when I removed them ...) so booting with ubldr.bin should work now.

confirmed working on h3/neo, both ublfr/efi.

> For the EFI issue I don't really know what is happening.

I think Jakob had the wrong loader.efi, by mistake I told him to copy it =
as bootaa64.efi instead
of bootarm.efi.

danny





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9EE16E32-AE1F-49DC-BF85-2AF4ECA00B0D>