Difference between revisions of "Template:RockchipMiscCustome"
(updated by API) |
(updated by API) |
||
| Line 24: | Line 24: | ||
scp pi@BOARDIP:/rootfs.tar.gz /rootfs.tar.gz | scp pi@BOARDIP:/rootfs.tar.gz /rootfs.tar.gz | ||
mkdir rootfs | mkdir rootfs | ||
| − | tar | + | tar xvzfp rootfs.tar.gz -C rootfs --numeric-owner --same-owner |
./build-rootfs-img.sh rootfs friendlycore-lite-focal-arm64 | ./build-rootfs-img.sh rootfs friendlycore-lite-focal-arm64 | ||
./mk-sd-image.sh friendlycore-lite-focal-arm64 | ./mk-sd-image.sh friendlycore-lite-focal-arm64 | ||
| Line 39: | Line 39: | ||
scp pi@BOARDIP:/rootfs.tar.gz /rootfs.tar.gz | scp pi@BOARDIP:/rootfs.tar.gz /rootfs.tar.gz | ||
mkdir rootfs | mkdir rootfs | ||
| − | tar | + | tar xvzfp rootfs.tar.gz -C rootfs --numeric-owner --same-owner |
./build-rootfs-img.sh rootfs debian-bullseye-desktop-arm64 | ./build-rootfs-img.sh rootfs debian-bullseye-desktop-arm64 | ||
./mk-sd-image.sh debian-bullseye-desktop-arm64 | ./mk-sd-image.sh debian-bullseye-desktop-arm64 | ||
| Line 54: | Line 54: | ||
scp pi@BOARDIP:/rootfs.tar.gz /rootfs.tar.gz | scp pi@BOARDIP:/rootfs.tar.gz /rootfs.tar.gz | ||
mkdir rootfs | mkdir rootfs | ||
| − | tar | + | tar xvzfp rootfs.tar.gz -C rootfs --numeric-owner --same-owner |
./build-rootfs-img.sh rootfs debian-bullseye-desktop-arm64 | ./build-rootfs-img.sh rootfs debian-bullseye-desktop-arm64 | ||
./mk-sd-image.sh debian-bullseye-desktop-arm64 | ./mk-sd-image.sh debian-bullseye-desktop-arm64 | ||
| Line 69: | Line 69: | ||
scp pi@BOARDIP:/rootfs.tar.gz /rootfs.tar.gz | scp pi@BOARDIP:/rootfs.tar.gz /rootfs.tar.gz | ||
mkdir rootfs | mkdir rootfs | ||
| − | tar | + | tar xvzfp rootfs.tar.gz -C rootfs --numeric-owner --same-owner |
./build-rootfs-img.sh rootfs debian-bullseye-desktop-arm64 | ./build-rootfs-img.sh rootfs debian-bullseye-desktop-arm64 | ||
./mk-sd-image.sh debian-bullseye-desktop-arm64 | ./mk-sd-image.sh debian-bullseye-desktop-arm64 | ||
Revision as of 10:53, 28 March 2024
Contents
1 Backup rootfs and create custom SD image (to burn your application into other boards)
1.1 Backup rootfs
Run the following commands on your target board. These commands will back up the entire root partition:
sudo passwd root su root cd / tar --warning=no-file-changed -cvpzf /rootfs.tar.gz \ --exclude=/rootfs.tar.gz --exclude=/var/lib/docker/runtimes \ --exclude=/etc/firstuser --exclude=/etc/friendlyelec-release \ --exclude=/usr/local/first_boot_flag --one-file-system /
Note: if there is a mounted directory on the system, an error message will appear at the end, which can be ignored.
1.2 Making a bootable SD card from a root filesystem
Only support RK3328/RK3399/RK3568/RK3588
2 Configuring kernel command line parameters
2.1 eMMC Boot
Here are the steps:
Make an eflahser bootable SD card (use the firmware file starting with rk3xxxx-eflasher-)，
Insert the SD card into your computer, go to the SD card's OS-related directory, and edit the file parameter.txt, which is a text file containing command-line parameters，
Then boot from the SD card and burn the system to the eMMC.
2.2 SD Boot
To modify the command line parameters of the SD card, you need to repackage the SD card image file,
you can use the sd-fuse script we provide to assist packaging:
Only support RK3328/RK3399/RK3568/RK3588
