• Recent
    • Docs
    • Github
    • 百度网盘
    • Onedrive
    • Official
    • Shop
    • Register
    • Login

    刷了系统不启动,怎么回事?

    Scheduled Pinned Locked Moved Pi 4B
    15 Posts 4 Posters 733 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • E
      emtohere @emtohere
      last edited by

      @emtohere said in 刷了系统不启动,怎么回事?:

      @george TF卡。目前用armbian,不想折腾了。我还买了3块,打算刷android的,才发现这问题,之前一直用armbian。

      云盘里的镜像差不多都试了,问题各种各样:固件格式不对rkd打不开、镜像分区定义大于设备、好不容易找到一个刷进去了开不了机,有卡在logo画面的,有不停重启的、离线刷也是开不了机。只有armbian刷 完就进系统!!!!!

      G 1 Reply Last reply Reply Quote 0
      • G
        george @emtohere
        last edited by

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

        E Z 3 Replies Last reply Reply Quote 0
        • E
          emtohere @george
          last edited by

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

          1 Reply Last reply Reply Quote 0
          • E
            emtohere @george
            last edited by

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

            G 1 Reply Last reply Reply Quote 0
            • G
              george @emtohere
              last edited by

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

              E 1 Reply Last reply Reply Quote 0
              • E
                emtohere @george
                last edited by

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

                NeozyN 1 Reply Last reply Reply Quote 0
                • NeozyN
                  Neozy @emtohere
                  last edited by

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

                  Z 1 Reply Last reply Reply Quote 0
                  • Z
                    zehui @george
                    last edited by

                    @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那边改一下启动脚本什么的。

                    1 Reply Last reply Reply Quote 0
                    • Z
                      zehui @Neozy
                      last edited by

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

                      1. Boot partition (starting at 0x4000): contains the Linux image and DTB files.
                      2. 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.

                      G 1 Reply Last reply Reply Quote 0
                      • G
                        george @zehui
                        last edited by

                        @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:
                        eb6320f6-b51c-424f-8a7b-6bb08a9c68d8-image.png

                        1 Reply Last reply Reply Quote 0
                        • 1 / 1
                        • First post
                          Last post