On 13/05/19 6:36 pm, Vagrant Cascadian wrote:
[...]
>> U-Boot SPL 2019.01+dfsg-6 (May 12 2019 - 01:20:19 +0000)
>> DRAM: 2048 MiB
>> Trying to boot from MMC1
>> NOTICE:  BL3-1: Running on A64/H64 (1689) in SRAM A2 (@0x44000)
>> NOTICE:  Configuring SPC Controller
>> NOTICE:  BL3-1: v1.0(debug):
>> NOTICE:  BL3-1: Built : 12:32:39, Apr 11 2018
> 
> It looks like you're using the atf-allwinner package (or a custom ATF
> build) instead of arm-trusted-firmware. Both should work ok, but at some
> point atf-allwinner may get deprecated.
> 
> There's a u-boot-install-sunxi64 script that can be used to install
> u-boot, and will prefer firmware binaries from arm-trusted-firmware.

Thanks for the tip. I will make changes to freedom-maker to start using
arm-trusted-firmware instead. We are already using
u-boot-install-sunxi64 script.

Meanwhile, on a built image, I have switched to arm-trusted-firmware and
reran u-boot-install-sunxi64. Here is the fresh boot log:

U-Boot SPL 2019.01+dfsg-6 (May 12 2019 - 01:20:19 +0000)
DRAM: 2048 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.0(debug):
NOTICE:  BL31: Built : 23:33:29, Nov 27 2018
NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE:  BL31: Found U-Boot DTB at 0x407f2a8, model: Pine64 LTS
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
NOTICE:  BL31: PMIC: Detected AXP803 on RSB.
INFO:    PMIC: AXP803: dcdc1 voltage: 3.300V
INFO:    PMIC: AXP803: dcdc5 voltage: 1.200V
INFO:    PMIC: AXP803: dcdc6 voltage: 1.100V
INFO:    PMIC: AXP803: dldo1 voltage: 3.300V
INFO:    PMIC: AXP803: Enabling DC1SW
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 843419 was applied
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2019.01+dfsg-6 (May 12 2019 - 01:20:19 +0000) Allwinner Technology

CPU:   Allwinner A64 (SUN50I)
Model: Pine64 LTS
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
Loading Environment from FAT... Card did not respond to voltage select!
In:    serial
Out:   serial
Err:   serial
Net:   phy interface7
eth0: ethernet@1c30000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 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
2226 bytes read in 7 ms (310.5 KiB/s)
## Executing script at 4fc00000
18560880 bytes read in 858 ms (20.6 MiB/s)
16053 bytes read in 13 ms (1.2 MiB/s)
25179720 bytes read in 1169 ms (20.5 MiB/s)
Booting Debian 4.19.0-5-arm64 from mmc 0:1...
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
EHCI failed to shut down host controller.
EHCI failed to shut down host controller.
   Loading Ramdisk to 487fc000, end 49fff648 ... OK
   Loading Device Tree to 00000000487f5000, end 00000000487fbeb4 ... OK

Starting kernel ...

[    2.737551] sun50i-de2-bus 1000000.de2: Error couldn't map SRAM to device

Debian GNU/Linux 10 freedombox ttyS0

freedombox login:

-- 
Sunil

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to