Difference between revisions of "Template:RockchipMiscCustome"

From FriendlyELEC WiKi
Jump to: navigation, search
(updated by API)
(updated by API)
 
(4 intermediate revisions by the same user not shown)
Line 15: Line 15:
 
{{#switch: {{{1}}}
 
{{#switch: {{{1}}}
 
  | RK3328 =
 
  | RK3328 =
−
Run the following script on your Linux PC host, we'll only mention "friendlycore-lite-focal-arm64 os" for brevity, but you can apply the same process for every linux OS.
+
Run the following script on your Linux PC host, we'll only mention "ubuntu-noble-core-arm64 os" for brevity, but you can apply the same process for every linux OS.
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
 
su root
 
su root
 
git clone https://github.com/friendlyarm/sd-fuse_rk3328 --single-branch -b kernel-6.1.y
 
git clone https://github.com/friendlyarm/sd-fuse_rk3328 --single-branch -b kernel-6.1.y
 
cd sd-fuse_rk3328
 
cd sd-fuse_rk3328
−
tar xvzf /path/to/netdrive/03_Partition\ image\ files/friendlycore-lite-focal-arm64-images.tgz
+
tar xvzf /path/to/netdrive/03_Partition\ image\ files/ubuntu-noble-core-arm64-images.tgz
 
tar xvzf /path/to/netdrive/03_Partition\ image\ files/emmc-eflasher-images.tgz
 
tar xvzf /path/to/netdrive/03_Partition\ image\ files/emmc-eflasher-images.tgz
 
scp pi@BOARDIP:/rootfs.tar.gz /rootfs.tar.gz
 
scp pi@BOARDIP:/rootfs.tar.gz /rootfs.tar.gz
 
mkdir rootfs
 
mkdir rootfs
−
tar xzf rootfs.tar.gz -C rootfs
+
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 ubuntu-noble-core-arm64
−
./mk-sd-image.sh friendlycore-lite-focal-arm64
+
./mk-sd-image.sh ubuntu-noble-core-arm64
−
./mk-emmc-image.sh friendlycore-lite-focal-arm64 autostart=yes
+
./mk-emmc-image.sh ubuntu-noble-core-arm64 autostart=yes
 
</syntaxhighlight>
 
</syntaxhighlight>
 
  | RK3399 =
 
  | RK3399 =
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 xzf rootfs.tar.gz -C rootfs
+
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 xzf rootfs.tar.gz -C rootfs
+
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 xzf rootfs.tar.gz -C rootfs
+
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 75: Line 75:
 
</syntaxhighlight>
 
</syntaxhighlight>
 
  | #default =
 
  | #default =
−
Only support RK3328/RK3399/RK3568/RK3588<br />
+
Only support RK3328/RK3399/RK3568/RK3566/RK3588<br />
 
}}
 
}}
−
==Configuring kernel command line parameters==
+
{{#switch: {{{1}}}
 +
| RK3399 =
 +
==Configuring kernel command line parameters (only support for kernel4.4)==
 
===eMMC Boot===
 
===eMMC Boot===
 
Here are the steps:<br />
 
Here are the steps:<br />
Line 85: Line 87:
 
===SD Boot===
 
===SD Boot===
 
To modify the command line parameters of the SD card, you need to repackage the SD card image file, <br />
 
To modify the command line parameters of the SD card, you need to repackage the SD card image file, <br />
−
you can use the sd-fuse script we provide to assist packaging:<br />
+
you can use the sd-fuse script we provide to assist packaging:
−
:<br />
+
| #default =
 +
}}
 
{{#switch: {{{1}}}
 
{{#switch: {{{1}}}
−
| RK3328 =
 
−
<syntaxhighlight lang="bash">
 
−
git clone https://github.com/friendlyarm/sd-fuse_rk3328.git -b kernel-6.1.y --single-branch
 
−
cd sd-fuse_rk3328
 
−
tar xvzf /path/to/netdrive/03_Partition\ image\ files/friendlywrt23-images.tgz
 
−
tar xvzf /path/to/netdrive/03_Partition\ image\ files/emmc-flasher-images.tgz
 
−
vim friendlywrt23/parameter.txt  # Edit command-line parameters
 
−
./mk-sd-image.sh friendlywrt23    # Repackage sd image file
 
−
./mk-emmc-image.sh friendlywrt23  # Repackage sd-to-emmc image file
 
−
</syntaxhighlight>
 
 
  | RK3399 =
 
  | RK3399 =
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
git clone https://github.com/friendlyarm/sd-fuse_rk3399.git -b kernel-6.1.y --single-branch
+
git clone https://github.com/friendlyarm/sd-fuse_rk3399.git -b master --single-branch
 
cd sd-fuse_rk3399
 
cd sd-fuse_rk3399
−
tar xvzf /path/to/netdrive/03_Partition\ image\ files/friendlywrt23-images.tgz
+
tar xvzf /path/to/netdrive/03_Partition\ image\ files/friendlydesktop-arm64-images.tgz
−
tar xvzf /path/to/netdrive/03_Partition\ image\ files/emmc-flasher-images.tgz
+
−
vim friendlywrt23/parameter.txt  # Edit command-line parameters
+
−
./mk-sd-image.sh friendlywrt23    # Repackage sd image file
+
−
./mk-emmc-image.sh friendlywrt23  # Repackage sd-to-emmc image file
+
−
</syntaxhighlight>
+
−
| RK3568 =
+
−
<syntaxhighlight lang="bash">
+
−
git clone https://github.com/friendlyarm/sd-fuse_rk3568.git -b kernel-6.1.y --single-branch
+
−
cd sd-fuse_rk3568
+
−
tar xvzf /path/to/netdrive/03_Partition\ image\ files/friendlywrt23-images.tgz
+
−
tar xvzf /path/to/netdrive/03_Partition\ image\ files/emmc-flasher-images.tgz
+
−
vim friendlywrt23/parameter.txt  # Edit command-line parameters
+
−
./mk-sd-image.sh friendlywrt23    # Repackage sd image file
+
−
./mk-emmc-image.sh friendlywrt23  # Repackage sd-to-emmc image file
+
−
</syntaxhighlight>
+
−
| RK3588 =
+
−
<syntaxhighlight lang="bash">
+
−
git clone https://github.com/friendlyarm/sd-fuse_rk3588.git -b kernel-6.1.y --single-branch
+
−
cd sd-fuse_rk3588
+
−
tar xvzf /path/to/netdrive/03_Partition\ image\ files/friendlywrt23-images.tgz
+
 
tar xvzf /path/to/netdrive/03_Partition\ image\ files/emmc-flasher-images.tgz
 
tar xvzf /path/to/netdrive/03_Partition\ image\ files/emmc-flasher-images.tgz
−
vim friendlywrt23/parameter.txt  # Edit command-line parameters
+
vim friendlydesktop-arm64/parameter.txt  # Edit command-line parameters
−
./mk-sd-image.sh friendlywrt23   # Repackage sd image file
+
./mk-sd-image.sh friendlydesktop-arm64   # Repackage sd image file
−
./mk-emmc-image.sh friendlywrt23 # Repackage sd-to-emmc image file
+
./mk-emmc-image.sh friendlydesktop-arm64 # Repackage sd-to-emmc image file
 
</syntaxhighlight>
 
</syntaxhighlight>
 
  | #default =
 
  | #default =
−
Only support RK3328/RK3399/RK3568/RK3588<br />
 
 
}}
 
}}

Latest revision as of 08:15, 26 August 2024

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/RK3566/RK3588


Retrieved from "https://wiki.friendlyelec.com/wiki/index.php?title=Template:RockchipMiscCustome&oldid=26259"