Werner

Not an Armbian-kernel. I suggest asking where you get this Linux image.

Works nicely for me. No need to adjust any parameter besides baud rate to 1.5Mbaud as it is default to all Rockchip SoCs. Make sure your adapter can handle this rather high speed. Also make sure to cross-connect RX/TX.

That is UEFI generic image which will not work on OPi5 due to lack of UEFI presence. As you can see above I use the same vendor bsp kernel 5.10.110. Userspace (Bullseye or Jammy to say) make usually no difference since both flavours are always shipped with the very same kernel package. The only difference for me is that I disabled debugfs in kernel config to get rid of some dmesg annoyance but thats it. Again, read and check here: https://forum.armbian.com/forum/31-sd-card-and-psu-issues/

That is odd. Is console set to "both" on armbianEnv?

Set baud rate to 1500000

There is serial login. I more assume that boot fails for some reason. increase verbosity via armbianEnv.txt to 7 and boot again to see what happens.

Cannot reproduce. https://forum.armbian.com/forum/31-sd-card-and-psu-issues/

adb is a tool for Android based OS. Armbian is not Android but Linux. Use ssh to connect.

Agreed. Better hit a bit of cache than not at all. So still a win if I understood everything else correctly.

https://docs.armbian.com/User-Guide_Getting-Started/#how-to-login

moved to tvboxes

moved to tvboxes

Take note that there is no guarantee that community-hacked Armbian versions will work on that hardware properly. TVboxes are like cancer on the SBC market. You can read more on that here: https://docs.armbian.com/User-Guide_FAQ/#i-have-a-tv-boxtablet-from-insert-random-vendor-can-i-use-armbian-on-it

Split post into separate topic

I think @rpardini can explain best what is happening there.

Such development usually takes a lot of time. Don't expect much within this year.

It will most likely be mentioned in changelog once this is fixed.

If somebody volunteers to do so...

https://www.armbian.com/newsflash/armbian-23-02/ Changelog: https://docs.armbian.com/Release_Changelog/

I assume OP is preferring a software-based solution but I like your thinking

Hooking up a serial console is best possible way to debug boot issues.

Providing full build log would be the first one

Since there are no standards vendors of more or less cheap boards follow names are not standardized. Try something like code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } find /sys |grep led|grep trigger

As always the solution pops up once I start complaining Seems like my 64G microSD is cursed. It works well on common usage but it refuses to work properly on SBCs. Not wrote the same image to a 32G SD of same quality and brand and it works...

This might be interesting. It seems like it tries SD but cannot find valid partitions... U-Boot 2022.04-armbian (Feb 13 2023 - 01:06:32 +0000) SoC: Rockchip rk3399 Reset cause: POR Model: Firefly ROC-RK3399-PC-PLUS Board DRAM: 3.9 GiB PMIC: RK808 Core: 295 devices, 29 uclasses, devicetree: separate MMC: mmc@fe310000: 2, mmc@fe320000: 1, mmc@fe330000: 0 Loading Environment from SPIFlash... SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Firefly ROC-RK3399-PC-PLUS Board Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 starting USB... Bus usb@fe380000: USB EHCI 1.00 Bus usb@fe3c0000: USB EHCI 1.00 Bus usb@fe900000: 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@fe3c0000 for devices... 2 USB Device(s) found scanning bus usb@fe900000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device switch to partitions #0, OK mmc1 is current device ** No partition table - mmc 1 ** Couldn't find partition mmc 1:1 switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 1: Armbian Retrieving file: /boot/uInitrd