刷了系统不启动，怎么回事？

george

@emtohere
机器默认刷机是使用etcher来刷。不是用RK官方工具，上电多次按开机按键，机器就会进入UMS模式，然后使用etcher软件加载固件，选择设备刷机即可。

emtohere

@george 这倒没试过，etcher直刷tf卡就是各种开不机。有空再试一次。

emtohere

@george 我用tf卡，不用进ums模式吧。按你的说法，是不是得借助一个u盘，用ether刷iso镜像，然后u盘插入开发板，u盘引导进入系统，最后在系统里dd刷入目标系统？

george

@emtohere
使用TF卡的话不需要进入UMS模式，直接用读卡器通过etcher软件写就好了。不要用RKD工具。

emtohere

@george 试过了，不行。只有armbian可以

Neozy

@emtohere I have the same problem. Only Armbian will boot. No other image works on TF card or USB drive.

zehui

@george @emtohere 我看了一些镜像的内容，发现你们一些镜像实际搞了两个分区
1）boot：从0x4000开始，image，dtb，ramfs都放在这里
2）rootfs：从0x84000开始，linux就放在这里，然后boot下面是空的
而armbian就按照正常的Linux distro那样，把image、dtb，ramfs放到rootfs的boot下面，所以导致了只有armbian能够启动。

如果要刷你们的镜像的话，bootloader就需要改一下。比如U-Boot那边改一下启动脚本什么的。

zehui

@Neozy Because the other images are split into two partitions:

Boot partition (starting at 0x4000): contains the Linux image and DTB files.
Rootfs partition (starting at 0x84000): contains kernel modules and binaries, but has an empty /boot directory.

This layout is somewhat uncommon, as most distributions place the kernel image and DTB files directly under the /boot directory within the root filesystem. As a result, you may need to modify the boot script of your bootloader (e.g., U-Boot) to account for this partitioning scheme.

george

@zehui
The use of cloud storage images requires updating uboot to the latest version. Currently, RK3588/3588S uses a unified image, and machine models are distinguished in uboot. As for the partitions of the image, they are boot and rootfs. Boot stores kernel related files.
As shown in the following figure：

zehui

@george It's fine for me—as a TrustZone developer, I always use a custom U-Boot and build the entire system myself.

However, it's good to keep this as a note to inform other developers.