08-17-2020, 11:17 PM
Thank you for the heads up!
I also run into the issue, but I think ArchLinuxARM fixed their flashing procedure by providing different files to store in the initial non-partitioned space (now called "rksd_loader.img" and "u-boot.itb", see "https://archlinuxarm.org/platforms/armv8/rockchip/rock64").
I simply stored these files into the SD card as the procedure step (9) says:
dd if=rksd_loader.img of=/dev/mmcblk0 seek=64 conv=notrunc
dd if=u-boot.itb of=/dev/mmcblk0 seek=16384 conv=notrunc
After that the board booted normally and I didn't see any loss of data.
I also run into the issue, but I think ArchLinuxARM fixed their flashing procedure by providing different files to store in the initial non-partitioned space (now called "rksd_loader.img" and "u-boot.itb", see "https://archlinuxarm.org/platforms/armv8/rockchip/rock64").
I simply stored these files into the SD card as the procedure step (9) says:
dd if=rksd_loader.img of=/dev/mmcblk0 seek=64 conv=notrunc
dd if=u-boot.itb of=/dev/mmcblk0 seek=16384 conv=notrunc
After that the board booted normally and I didn't see any loss of data.
