version 11.0.3 couldnot not boot on rock960c (rk3399 smb)

hontoo · November 5, 2023 at 3:37 AM

I've try several times to boot libreelec on my rock960(c) sbc.

After making bootable sd card in every methods i know, win32image/ balenaecher , sdc just ignore the sd card and skip into emmc debian.

then i cancel the uboot fastboot , force it boot from sdmmc

`

Code

Hit any key to stop autoboot:  0
=> setenv devnum 1; run mmc_boot



switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
reading /extlinux/extlinux.conf
226 bytes read in 3 ms (73.2 KiB/s)
1:      LibreELEC
Retrieving file: /KERNEL
reading /KERNEL
23912456 bytes read in 1509 ms (15.1 MiB/s)
append: boot=UUID=1507-1947 disk=UUID=1fbab003-ab9a-42ee-8dcb-5ab2404e6770 quiet console=uart8250,mmio32,0xff1a0000 console=tty0 coherent_pool=2M cec.debounce_ms=5000
Retrieving file: /rk3399-rock960.dtb
reading /rk3399-rock960.dtb
77983 bytes read in 8 ms (9.3 MiB/s)
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Device Tree to 000000007def0000, end 000000007df0609e ... OK

Starting kernel ...

[    1.148515] rockchip-typec-phy ff800000.phy: wait pma ready timeout
[    1.149411] phy phy-ff800000.phy.12: phy poweron failed --> -110
[    1.150205] dwc3 fe900000.usb: error -ETIMEDOUT: failed to initialize core
[    1.226629] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with 0-001b
[    1.277356] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with 0-001b
[    1.325301] thermal_sys: Failed to bind 'cpu-thermal' with 'cpufreq-cpu4': -17
[    1.435403] mmc1: tuning execution failed: -5
[    1.435817] mmc1: error -5 whilst initialising SD card
[    1.562079] mmc1: tuning execution failed: -5
[    1.921629] rockchip-pcie f8000000.pcie: PCIe link train ing gen1 timeout!

Display More

after few minutes , will fallback to on-emmc debian.

Any Information should i provide more to solve it . thanks

**chewitt** · November 5, 2023 at 5:50 AM

If the board is booting from eMMC it's probably using an older u-boot version that shipped with the Debian image, and that might result in odd behaviour when partnered with newer kernels. I'd suggest erasing u-boot from eMMC so the board can find/use the version on the SD card, and also to use a current LE12 nightly to benefit from newer kernels and any fixes that have been made.

hontoo · November 5, 2023 at 1:31 PM

I've rollback to 10.0 , now it works, booting from images sd card

it maybe an u-boot issue as you've mentioned.

Quote from chewitt

If the board is booting from eMMC it's probably using an older u-boot version that shipped with the Debian image, and that might result in odd behaviour when partnered with newer kernels. I'd suggest erasing u-boot from eMMC so the board can find/use the version on the SD card, and also to use a current LE12 nightly to benefit from newer kernels and any fixes that have been made.

I will test an newer debian image later