Just a short update after upgrading to mainline kernel 5.10.4 in Debian unstable and U-Boot 2020.10. My boot now hangs after the dtbs have been detected (tried booting from sdcard):
The same issue is present with the pinebookpro, so I assume the 5.10 kernel in Debian has some issue here.
Edit: Issue seems to be specific for the rk3399 as the smaller rock64 boots fine with the same kernel.
Update: For the current kernel to work you have to compile u-boot with "PREBOOT=y" disabled as mentioned by toons. Then it will probably boot - at least the pinebook pro does. See here for details:
https://forum.pine64.org/showthread.php?...5#pid86475
Update 2: Confirmed. The rockpro64 boots up fine with the change in u-boot and is usable. I tried only booting from eMMC as I keep having issues with the sdcard in the official Debian kernels.
Code:
U-Boot 2020.10 (Jan 03 2021 - 03:00:07 +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... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment
In: serial
Out: serial
Err: serial
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... 1 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!
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:2...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
210 bytes read in 4 ms (50.8 KiB/s)
1: Linux devuan
Retrieving file: /initrd.img
28216151 bytes read in 1274 ms (21.1 MiB/s)
Retrieving file: /vmlinuz
23842672 bytes read in 1077 ms (21.1 MiB/s)
append: root=LABEL=root cryptopts=source=LABEL=rootencrypted,target=root_crypt,luks
Retrieving file: /dtbs/rockchip/rk3399-rockpro64.dtb
56849 bytes read in 10 ms (5.4 MiB/s)
Moving Image from 0x2080000 to 0x2200000, end=3960000
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
The same issue is present with the pinebookpro, so I assume the 5.10 kernel in Debian has some issue here.
Edit: Issue seems to be specific for the rk3399 as the smaller rock64 boots fine with the same kernel.
Update: For the current kernel to work you have to compile u-boot with "PREBOOT=y" disabled as mentioned by toons. Then it will probably boot - at least the pinebook pro does. See here for details:
https://forum.pine64.org/showthread.php?...5#pid86475
Update 2: Confirmed. The rockpro64 boots up fine with the change in u-boot and is usable. I tried only booting from eMMC as I keep having issues with the sdcard in the official Debian kernels.