I tried using defconfig + the mainline DTB (rk3588-rock-5b-plus.dtb) but the board failed to boot.
I’m guessing it’s missing some driver configs.
Don’t guess. Check.
Defconfigs are usually OK. Missing drivers is unlikely to be the cause.
If you connect an USB serial console cable to pins 6 8 10 of the 40-pin header and make sure kernel loglevel is set to 7, you will see both bootloader and kernel messages and it should be easy to see what is wrong.
Thanks for your answer. After I use serial concsole. The log print below:
I can’t see kernel info.
Adding bank: 0x00200000 - 0xf0000000 (size: 0xefe00000)
Adding bank: 0x100000000 - 0x3fc000000 (size: 0x2fc000000)
Adding bank: 0x3fc500000 - 0x3fff00000 (size: 0x03a00000)
Adding bank: 0x4f0000000 - 0x500000000 (size: 0x10000000)
Total: 10633.39/11757.17 ms
Starting kernel …
You need to set kernel loglevel=7
You need to add that to the kernel cmdline
Where that is, depends on what method you use to boot, can be in extlinux.conf or grub.cfg or other config files
I already have loglevel=7 and earlycon=uart8250,mmio32,0xfeb50000,1500000 in cmdline. The issue is:
the pre-installed vmlinuz-6.1.84-8-rk2410 boots fine, but any self-compiled kernel (BSP build,
mainline, or Armbian) all hang at “Starting kernel …” with zero output. Is there something special
about the pre-installed kernel binary?
Should i update uboot?My version is rknext-2017.09-33-f73b1ee
Thanks.
Yes that is what I already thought you should do. That version you use I have never used and it prints almost no info. An Armbian current or edge based prints much more and is also more flexible and should run fine with mainline
I have put EDK2 UEFIv1.1 in SPI-flash (ROCK5B) and set it to ‘mainline‘, then you can just boot a standard distro kernel via grub-efi. When 6.19 or 7.0, most things work.