03-20-2021, 12:20 PM
(03-14-2021, 03:48 AM)mdesign Wrote: Hi, could you or someone resolve this "Booting using fdtblob at 0x1f0000000" somehow?
I got the same with latest Armbian_21.02.3_Rockpro64_focal_current_5.10.21.img.xz and U-Boot 2020.10-07966-ge34a1785a0 (Nov 17 2020 - 19:32:18 +0000))
Code:U-Boot 2020.10-07966-ge34a1785a0 (Nov 17 2020 - 19:32:18 +0000)
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 RockPro64 v2.1
DRAM: 3.9 GiB
PMIC: RK808
MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: vidconsole
Err: vidconsole
Model: Pine64 RockPro64 v2.1
Net: eth0: ethernet@fe300000
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3a0000: USB OHCI 1.0
Bus usb@fe3c0000: USB EHCI 1.00
Bus usb@fe3e0000: USB OHCI 1.0
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus usb@fe3a0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3e0000 for devices... 2 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
Card did not respond to voltage select!
Device 0: unknown device
scanning bus for devices...
Target spinup took 0 ms.
SATA link 1 timeout.
SATA link 2 timeout.
SATA link 3 timeout.
SATA link 4 timeout.
AHCI 0001.0301 32 slots 5 ports 6 Gbps 0x1f impl SATA mode
flags: 64bit ncq stag pm led clo pmp fbss pio slum part ccc apst boh
Device 0: (0:0) Vendor: ATA Prod.: INTEL SSDSC2KW48 Rev: LSF
Type: Hard Disk
Capacity: 457862.8 MB = 447.1 GB (937703088 x 512)
Device 0: (0:0) Vendor: ATA Prod.: INTEL SSDSC2KW48 Rev: LSF
Type: Hard Disk
Capacity: 457862.8 MB = 447.1 GB (937703088 x 512)
... is now current device
Scanning scsi 0:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 9 ms (344.7 KiB/s)
## Executing script at 00500000
Boot script loaded from scsi 0
166 bytes read in 8 ms (19.5 KiB/s)
15335962 bytes read in 254 ms (57.6 MiB/s)
28582400 bytes read in 463 ms (58.9 MiB/s)
75809 bytes read in 19 ms (3.8 MiB/s)
2698 bytes read in 15 ms (174.8 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 15335898 Bytes = 14.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
I think you're encountering the same problem, where U-Boot starting USB before boot will cause booting the kernel to hang.
I noticed that Debian has disabled starting USB in U-Boot preboot (https://bugs.debian.org/cgi-bin/bugrepor...bug=973323), I haven't seen this problem on my RockPro64 board but enough other people have reported issues with USB that I decided to make another release, updating to be based on v2021.01, with starting USB disabled in preboot: https://github.com/sigmaris/u-boot/relea...ckpro64-ci
Try that and see if it fixes the issue (though it will sacrifice the use of USB keyboard in U-Boot).