[Buildroot] Orange Pi Prime does not boot

Christoph Engelbert me at noctarius.com
Wed Jul 18 11:10:38 UTC 2018


If the board just stops when loading the kernel you’re most probably having an issue with the memory address, like overwriting parts of the extracted kernel (for example) with the device tree.

Try to change the load address for the kernel. Had the same base issue with my kernel and the nanopi neo air board.

Chris

> On 18. Jul 2018, at 13:01, aai at tut.by wrote:
> 
> 
> 
> 16.07.2018, 16:23, "aai at tut.by" <aai at tut.by>:
>> 13.07.2018, 21:18, "Peter Seiderer" <ps.report at gmx.net>:
>>>  Hello,
>>> 
>>>  On Fri, 13 Jul 2018 20:43:49 +0530, Jagan Teki <jagan at amarulasolutions.com> wrote:
>>> 
>>>>   On Tue, Jul 10, 2018 at 2:23 PM, <aai at tut.by> wrote:
>>>>   > Hello,
>>>>   >
>>>>   > orangepi_prime_defconfig does not work for me (try buildroot 2018.02.3 and 2018.05)
>>>>   >
>>>>   > I do:
>>>>   > make orangepi_prime_defconfig
>>>>   > make
>>>>   >
>>>>   > boot log:
>>>>   > --------------------------------------------------------------
>>>>   > Terminal ready
>>>>   >
>>>>   > U-Boot SPL 2017.11 (Jul 09 2018 - 10:12:15)
>>>>   > DRAM: 2048 MiB
>>>>   > Trying to boot from MMC1
>>>>   >
>>>>   >
>>>>   > U-Boot 2017.11 (Jul 09 2018 - 10:12:15 +0300) Allwinner Technology
>>>>   >
>>>>   > CPU: Allwinner H5 (SUN50I)
>>>>   > Model: OrangePi Prime
>>>>   > DRAM: 2 GiB
>>>>   > MMC: SUNXI SD/MMC: 0
>>>>   > *** Warning - bad CRC, using default environment
>>>>   >
>>>>   > In: serial
>>>>   > Out: serial
>>>>   > Err: serial
>>>>   > Net: No ethernet found.
>>>>   > 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 U-Boot script /boot.scr
>>>>   > reading /boot.scr
>>>>   > 277 bytes read in 14 ms (18.6 KiB/s)
>>>>   > ## Executing script at 4fc00000
>>>>   > reading Image
>>>>   > 17365504 bytes read in 870 ms (19 MiB/s)
>>>>   > reading sun50i-h5-orangepi-prime.dtb
>>>>   > 13714 bytes read in 25 ms (535.2 KiB/s)
>>>>   > ## Flattened Device Tree blob at 4fa00000
>>>>   > Booting using the fdt blob at 0x4fa00000
>>>>   > Loading Device Tree to 0000000049ff9000, end 0000000049fff591 ... OK
>>> 
>>>  From Jagans boot log:
>>> 
>>>  reading /boot.scr
>>>  277 bytes read in 15 ms (17.6 KiB/s)
>>>  ## Executing script at 4fc00000
>>>  reading Image
>>>  16310784 bytes read in 820 ms (19 MiB/s)
>>>  reading sun50i-h5-orangepi-prime.dtb
>>>  13714 bytes read in 26 ms (514.6 KiB/s)
>>>  ## Flattened Device Tree blob at 4fa00000
>>>     Booting using the fdt blob at 0x4fa00000
>>>     Loading Device Tree to 0000000049ff9000, end 0000000049fff591 ... OK
>>> 
>>>  Jagan Image size: 16310784
>>>  aai Image size: 17365504
>> 
>> I built the image again on another computer. Image size is 16310784. But I can not check booting now.
>> I will try later, maybe by the end of the week
> 
> 
> 17365504 - I made a mistake and posted the wrong log with optimization level 2.
> 
> I tried Buildroot 2018.05 + Ubuntu 16.04 and Buildroot 2018.02.3 + Fedors 28. Not work.
> 
> Maybe my board is broken, but Armbian 5.38 works.
> 
> 
>> 
>>>  The only visible difference (besides not booting)...
>>> 
>>>  Regards,
>>>  Peter
>>> 
>>>>   >
>>>>   > Starting kernel ...
>>>>   > --------------------------------------------------------------
>>>> 
>>>>   It's booting fine with my side, here is full boot log[1]
>>>> 
>>>>   [1] https://paste.ubuntu.com/p/mQsRxMrKnh/
>>>> 
>>>>   Jagan.
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot




More information about the buildroot mailing list