APITestPage
Contents
- 1 How to compile custom kernel and u-boot
- 2 Compile Android
1 How to compile custom kernel and u-boot
1.1 Kernel and u-boot versions for each OS
| Operating System | Kernel Version | U-boot version | Cross-compiler | Partition type | Build toolset | Kernel code branch | Kernel configuration | U-boot code branch | u-boot configuration |
|---|---|---|---|---|---|---|---|---|---|
| lubuntu | linux v4.4.y | u-boot v2014.10 | 6.4-aarch64 |
MBR | sd-fuse | nanopi4-linux-v4.4.y | nanopi4_linux_defconfig | nanopi4-v2014.10_oreo | rk3399_defconfig |
| friendlycore-arm64 | |||||||||
| friendlydesktop-arm64 | |||||||||
| eflasher | |||||||||
| buildroot | linux v4.19.y | u-boot v2017.09 |
11.3-aarch64 | GPT | sd-fuse | nanopi4-v4.19.y | nanopi4_linux_defconfig | nanopi4-v2017.09 | rk3399_defconfig |
| debian-buster-desktop-arm64 | |||||||||
| debian-bullseye-core-arm64 | |||||||||
| debian-bullseye-desktop-arm64 | |||||||||
| debian-bullseye-minimal-arm64 | |||||||||
| friendlycore-focal-arm64 | |||||||||
| friendlycore-lite-focal-kernel4-arm64 | |||||||||
| friendlywrt21-kernel4 | nanopi4_linux_defconfig +friendlywrt.config | ||||||||
| friendlycore-lite-focal-kernel5-arm64 | linux v5.15.y | u-boot v2017.09 |
11.3-aarch64 | GPT | sd-fuse |
nanopi-r2-v5.15.y | nanopi4_linux_defconfig | nanopi4-v2017.09 |
rk3399_defconfig |
| friendlywrt21 | nanopi4_linux_defconfig +friendlywrt.config | ||||||||
| friendlywrt21-docker | |||||||||
| friendlywrt22 | |||||||||
| friendlywrt22-docker |
- Kernel source code repository：https://github.com/friendlyarm/kernel-rockchip
- u-boot source code repository：https://github.com/friendlyarm/uboot-rockchip
- The cross-compile toolchain is stored in the following path: /opt/FriendlyARM/toolchain/. Before using it, it needs to be exported to the PATH environment variable. For example, if you need to use version 11.3-aarch64 of the compiler, use the following command:
export PATH=/opt/FriendlyARM/toolchain/11.3-aarch64/bin/:$PATH
- The SD-Fuse build toolset can be used to quickly compile the kernel and u-boot, as well as repackaging SD card image and SD-to-eMMC image.
- Click on MBR and GPT in the table to view the partition layout (configuration file) for each system.
1.2 Compile kernel linux-v4.4.y
This section applies to the following operating systems:
| lubuntu | eflasher | friendlydesktop-arm64 | friendlycore-arm64 |
Download the source code and compile as follows:
git clone https://github.com/friendlyarm/kernel-rockchip --single-branch --depth 1 -b nanopi4-linux-v4.4.y kernel-rockchip cd kernel-rockchip export PATH=/opt/FriendlyARM/toolchain/6.4-aarch64/bin/:$PATH touch .scmversion # Compile the kernel make ARCH=arm64 CROSS_COMPILE=aarch64-linux- nanopi4_linux_defconfig # make ARCH=arm64 CROSS_COMPILE=aarch64-linux- menuconfig # Modifying the configuration make ARCH=arm64 CROSS_COMPILE=aarch64-linux- nanopi4-images -j$(nproc) # Compile the kernel modules mkdir -p out-modules make ARCH=arm64 CROSS_COMPILE=aarch64-linux- INSTALL_MOD_PATH="$PWD/out-modules" modules -j$(nproc) make ARCH=arm64 CROSS_COMPILE=aarch64-linux- INSTALL_MOD_PATH="$PWD/out-modules" modules_install KERNEL_VER=$(make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 kernelrelease) rm -rf $PWD/out-modules/lib/modules/${KERNEL_VER}/kernel/drivers/gpu/arm/mali400/ [ ! -f "$PWD/out-modules/lib/modules/${KERNEL_VER}/modules.dep" ] && depmod -b $PWD/out-modules -E Module.symvers -F System.map -w ${KERNEL_VER} (cd $PWD/out-modules && find . -name \*.ko | xargs aarch64-linux-strip --strip-unneeded)
After the compilation, the following files will be generated:
| kernel.img | resource.img | The kernel modules are located in the out-modules directory |
Installing the kernel:
Please click on #Download u-boot and the kernel to the target board
1.3 Compile u-boot v2014.10
This section applies to the following operating systems:
| lubuntu | eflasher | friendlydesktop-arm64 | friendlycore-arm64 |
Download the source code and compile as follows:
git clone https://github.com/friendlyarm/uboot-rockchip --single-branch --depth 1 -b nanopi4-v2014.10_oreo cd uboot-rockchip export PATH=/opt/FriendlyARM/toolchain/6.4-aarch64/bin/:$PATH make CROSS_COMPILE=aarch64-linux- rk3399_defconfig make CROSS_COMPILE=aarch64-linux-
After the compilation, the following files will be generated:
| uboot.img | trust.img | rk3399_loader_v1.22.119.bin |
Installing the u-boot:
Please click on #Download u-boot and the kernel to the target board
1.4 Compile kernel linux-v4.19.y
This section applies to the following operating systems:
| debian-buster-desktop-arm64 | debian-bullseye-core-arm64 | debian-bullseye-desktop-arm64 | debian-bullseye-minimal-arm64 |
| friendlycore-focal-arm64 | friendlycore-lite-focal-kernel4-arm64 | friendlywrt21-kernel4 | buildroot |
Download the source code and compile as follows:
git clone https://github.com/friendlyarm/kernel-rockchip --single-branch --depth 1 -b nanopi4-v4.19.y kernel-rockchip cd kernel-rockchip export PATH=/opt/FriendlyARM/toolchain/11.3-aarch64/bin/:$PATH touch .scmversion # Compile the kernel make ARCH=arm64 CROSS_COMPILE=aarch64-linux- nanopi4_linux_defconfig # make ARCH=arm64 CROSS_COMPILE=aarch64-linux- menuconfig # Modifying the configuration make ARCH=arm64 CROSS_COMPILE=aarch64-linux- nanopi4-images -j$(nproc) # Compile the kernel modules mkdir -p out-modules make ARCH=arm64 CROSS_COMPILE=aarch64-linux- INSTALL_MOD_PATH="$PWD/out-modules" modules -j$(nproc) make ARCH=arm64 CROSS_COMPILE=aarch64-linux- INSTALL_MOD_PATH="$PWD/out-modules" modules_install KERNEL_VER=$(make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 kernelrelease) rm -rf $PWD/out-modules/lib/modules/${KERNEL_VER}/kernel/drivers/gpu/arm/mali400/ [ ! -f "$PWD/out-modules/lib/modules/${KERNEL_VER}/modules.dep" ] && depmod -b $PWD/out-modules -E Module.symvers -F System.map -w ${KERNEL_VER} (cd $PWD/out-modules && find . -name \*.ko | xargs aarch64-linux-strip --strip-unneeded)
After the compilation, the following files will be generated:
| kernel.img | resource.img | The kernel modules are located in the out-modules directory |
Installing the kernel:
Please click on #Download u-boot and the kernel to the target board
1.5 Compile kernel linux-v5.15.y
This section applies to the following operating systems:
| friendlywrt21 | friendlywrt21-docker | friendlywrt22 | friendlywrt22-docker | friendlycore-lite-focal-kernel5-arm64 |
Download the source code and compile as follows:
git clone https://github.com/friendlyarm/kernel-rockchip --single-branch --depth 1 -b nanopi-r2-v5.15.y kernel-rockchip cd kernel-rockchip export PATH=/opt/FriendlyARM/toolchain/11.3-aarch64/bin/:$PATH touch .scmversion # Compile the kernel make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 nanopi4_linux_defconfig # make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 menuconfig # Modifying the configuration make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 -j$(nproc) # Compile the kernel modules mkdir -p out-modules && rm -rf out-modules/* make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 INSTALL_MOD_PATH="$PWD/out-modules" modules -j$(nproc) make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 INSTALL_MOD_PATH="$PWD/out-modules" modules_install KERNEL_VER=$(make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 kernelrelease) [ ! -f "$PWD/out-modules/lib/modules/${KERNEL_VER}/modules.dep" ] && depmod -b $PWD/out-modules -E Module.symvers -F System.map -w ${KERNEL_VER} (cd $PWD/out-modules && find . -name \*.ko | xargs aarch64-linux-strip --strip-unneeded)
打包kernel.img与resource.img:
wget https://raw.githubusercontent.com/friendlyarm/sd-fuse_rk3399/kernel-5.15.y/tools/mkkrnlimg && chmod 755 mkkrnlimg wget https://raw.githubusercontent.com/friendlyarm/sd-fuse_rk3399/kernel-5.15.y/tools/resource_tool && chmod 755 resource_tool wget https://raw.githubusercontent.com/friendlyarm/sd-fuse_rk3399/kernel-5.15.y/prebuilt/boot/logo.bmp wget https://raw.githubusercontent.com/friendlyarm/sd-fuse_rk3399/kernel-5.15.y/prebuilt/boot/logo_kernel.bmp ./mkkrnlimg arch/arm64/boot/Image kernel.img mkdir kernel-dtbs cp -f arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dtb kernel-dtbs/rk3399-nanopi4-rev09.dtb cp -f arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dtb kernel-dtbs/rk3399-nanopi4-rev0a.dtb cp -f arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4se.dtb kernel-dtbs/rk3399-nanopi4-rev0b.dtb cp -f arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dtb kernel-dtbs/rk3399-nanopi4-rev00.dtb ./resource_tool --dtbname kernel-dtbs/*.dtb logo.bmp logo_kernel.bmp
After the compilation, the following files will be generated:
| kernel.img | resource.img | The kernel modules are located in the out-modules directory |
Installing the kernel:
Please click on #Download u-boot and the kernel to the target board
1.6 Compile u-boot v2017.09
This section applies to the following operating systems:
| debian-buster-desktop-arm64 | debian-bullseye-core-arm64 | debian-bullseye-desktop-arm64 | debian-bullseye-minimal-arm64 |
| friendlycore-focal-arm64 | friendlycore-lite-focal-kernel4-arm64 | friendlywrt21-kernel4 | buildroot |
Download the source code and compile as follows:
git clone https://github.com/friendlyarm/rkbin --single-branch --depth 1 -b friendlyelec git clone https://github.com/friendlyarm/uboot-rockchip --single-branch --depth 1 -b nanopi4-v2017.09 -j$(nproc) export PATH=/opt/FriendlyARM/toolchain/11.3-aarch64/bin/:$PATH cd uboot-rockchip/ ./make.sh nanopi4
After the compilation, the following files will be generated:
| uboot.img | trust.img | rk3399_loader_v1.24.126.bin |
Installing the u-boot:
Please click on #Download u-boot and the kernel to the target board
1.7 Download u-boot and the kernel to the target board
1.7.1 Download to the installed system
1.7.1.1 MBR partition
This section applies to the following operating systems:
| lubuntu | eflasher | friendlydesktop-arm64 | friendlycore-arm64 |
Currently, only the Linux v4.4 kernel uses MBR partitioning. Please refer to the partmap file in this link: partmap，calculate the offset addresses of each partition, and use the dd command to write them. For example, in the contents of the parameter.template file, "0x00014000@0x00014000(kernel)" indicates that the position of kernel.img is at 0x00014000, which converted to decimal is 81920, so the dd command would be as follows：
dd if=kernel.img of=/dev/mmcblk0 seek=81920
1.7.1.2 GPT partition
This section applies to the following operating systems:
| debian-buster-desktop-arm64 | debian-bullseye-core-arm64 | debian-bullseye-desktop-arm64 | debian-bullseye-minimal-arm64 |
| friendlycore-focal-arm64 | friendlycore-lite-focal-kernel4-arm64 | friendlywrt21-kernel4 | buildroot |
| friendlywrt21 | friendlywrt21-docker | friendlywrt22 | friendlywrt22-docker |
Systems using the Linux v4.19 and Linux v5.15 kernels use GPT partitioning by default. Just use the dd command to write the image file to the corresponding partition.
- The SD/TF Card device node: /dev/mmcblk0
- The eMMC device node: /dev/mmcblk2
The following is an example of how to update the kernel to eMMC:
Use the 'parted' command to view the partition layout:
parted /dev/mmcblk2 print
You should get output similar to the following:
Model: MMC A3A551 (sd/mmc) Disk /dev/mmcblk2: 31.0GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 8389kB 12.6MB 4194kB uboot 2 12.6MB 16.8MB 4194kB misc 3 16.8MB 21.0MB 4194kB dtbo 4 21.0MB 37.7MB 16.8MB resource 5 37.7MB 79.7MB 41.9MB kernel 6 79.7MB 113MB 33.6MB boot 7 113MB 147MB 33.6MB recovery 8 147MB 31.0GB 30.9GB ext4 rootfs
s shown above, the resource partition is located at 4 and the kernel partition is located at 5. Use the dd command to write the resource.img and kernel.img files to these partitions, respectively. The commands are as follows:
dd if=resource.img of=/dev/mmcblk2p4 bs=1M dd if=kernel.img of=/dev/mmcblk2p5 bs=1M
If you want to update u-boot, the command is:
dd if=boot.img of=/dev/mmcblk2p1 bs=1M
To update the kernel driver modules, simply upload and replace the files in the following directory with the new driver module directory: /lib/modules.
1.7.2 To package a new SD card image or an SD-to-eMMC image
The sd-fuse is a bunch of scripts to build bootable SD card images for FriendlyElec boards, the main features are as follows:
- Create root filesystem image from a directory
- Build bootable SD card image
- Easy way to compile kernel、uboot and third-party driver
Please click on the corresponding link to learn more:
| Kernel version | Build toolset |
|---|---|
| linux v4.4.y | sd-fuse |
| linux v4.19.y | sd-fuse |
| linux v5.15.y | sd-fuse |
1.7.3 USB flashing
You can directly flash the compiled files. It's important to note that the rk3399_loader generated by u-boot needs to be renamed to MiniLoaderAll.bin. The following command demonstrates how to flash u-boot and the kernel. You need to load parameter.txt first before flashing other files:
sudo upgrade_tool ul MiniLoaderAll.bin sudo upgrade_tool di -p parameter.txt sudo upgrade_tool di uboot uboot.img sudo upgrade_tool di trust trust.img sudo upgrade_tool di resource resource.img sudo upgrade_tool di kernel kernel.img sudo upgrade_tool RD
Note: upgrade_tool is a command-line tool provided by Rockchip for Linux (Linux_Upgrade_Tool).
2 Compile Android
2.1 Compile Android10
2.1.1 Download Android10 Source Code
There are two ways to download the source code:
- repo archive file on netdisk
Netdisk URL: Click here
File location on netdisk："07_Source codes/rk3399-android-10.git-YYYYMMDD.tar.xz" (YYYYMMDD means the date of packaging)
After extracting the repo package from the network disk, you need to execute the sync.sh script, which will pull the latest code from gitlab:
tar xf "/path/to/netdisk/07_Source codes/rk3399-android-10.git-YYYYMMDD.tar.xz" cd rk3399-android-10 ./sync.sh
- git clone from gitlab
{{{1}}} source code is maintained in gitlab, You can download it by running the following command:
git clone --recursive https://gitlab.com/friendlyelec/rk3399-android-10.git -b main
Note: If the following error "error: unknown option `recurse-submodules'" appears, please upgrade git to v2.0.0 or above.
2.1.2 Generate Image File
You can compile an Android source code and generate an image file (non-root user is recommended):
cd rk3399-android-10 ./build-nanopc-t4.sh -F -M
If you need to include google apps, you need to set an environment variable and then compile, as shown below:
cd rk3399-android-10 export INSTALL_GAPPS_FOR_TESTING=yes ./build-nanopc-t4.sh -F -M
2.1.3 Make OTA Packages
If you need the support of A/B (Seamless) System Updates, you need to do the following:
a) Build your own update server for http download of update files;
b) Customize the Updater application, the code is located in packages/apps/Updater, let it connect and download file from your server;
c) Use the quick compilation script parameter -O or --ota to compile OTA Packages, as shown below:
cd rk3399-android-10 ./build-nanopc-t4.sh -F -O -M
After the compilation is successfully completed, the OTA update related packages are located in the directory: rockdev/otapackage/ ，Please do not delete this directory.
After you have made some changes, compiling again with the parameter -O will generate ota-update-XXXXXXXX.zip, which is an incremental update package.
OTA Packages decides whether to generate incremental update package according to BUILD_NUMBER, for details, please refer to build-nanopc-t4.sh.
To disable the A/B feature, you can refer to the following to modify device/rockchip/rk3399/nanopc-t4/BoardConfig.mk, and then recompile uboot and android:
BOARD_USES_AB_IMAGE := false
2.1.4 Update System with New Image
After compilation is done a new image file will be generated in the "rockdev/Image-nanopc_t4/" directory under Android 10's source code directory. You can follow the steps below to update the OS in {{{1}}}:
1) Insert an SD card which is processed with EFlasher to an SD card reader and insert this reader to a PC running Ubuntu. The SD card's partitions will be automatically mounted;
2) Copy all the files under the "rockdev/Image-nanopc_t4/" directory to the SD card's android10 directory in the "FRIENDLYARM" partition;
3) Insert this SD card to {{{1}}} and reflash Android
When flashing Android 10, EFlasher requires v1.3 or above. When flashing with Type-C, please use the tool AndroidTool v2.71 or Linux_Upgrade_Tool v1.49 provided by Rockchip.
2.2 Compile Android8.1
2.2.1 Download Android8.1 Source Code
There are two ways to download the source code:
- repo archive file on netdisk
Netdisk URL: Click here
File location on netdisk：sources/rk3399-android-8.1.git-YYYYMMDD.tgz (YYYYMMDD means the date of packaging)
After extracting the repo package from the network disk, you need to execute the sync.sh script, which will pull the latest code from gitlab:
tar xvzf /path/to/netdisk/sources/rk3399-android-8.1.git-YYYYMMDD.tgz cd rk3399-android-8.1 ./sync.sh
- git clone from gitlab
{{{1}}} source code is maintained in gitlab, You can download it by running the following command:
git clone https://gitlab.com/friendlyelec/rk3399-android-8.1 --depth 1 -b master
2.2.2 Generate Image File
You can compile an Android source code and generate an image file:
cd rk3399-android-8.1 ./build-nanopc-t4.sh -F -M
2.2.3 Update System with New Image
After compilation is done a new image file will be generated in the "rockdev/Image-nanopc_t4/" directory under Android 8.1's source code directory. You can follow the steps below to update the OS in {{{1}}}:
1) Insert an SD card which is processed with EFlasher to an SD card reader and insert this reader to a PC running Ubuntu. The SD card's partitions will be automatically mounted;
2) Copy all the files under the "rockdev/Image-nanopc_t4/" directory to the SD card's android8 directory in the "FRIENDLYARM" partition;
3) Insert this SD card to {{{1}}} and reflash Android
Here is an alternative guide to update OS: sd-fuse_rk3399
2.3 Compile Android7
2.3.1 Download Android7 Source Code
There are two ways to download the source code:
- repo archive file on netdisk
Netdisk URL: Click here
File location on netdisk：sources/rk3399-android-7.git-YYYYMMDD.tgz (YYYYMMDD means the date of packaging)
After extracting the repo package from the network disk, you need to execute the sync.sh script, which will pull the latest code from gitlab:
tar xvzf /path/to/netdisk/sources/rk3399-android-7.git-YYYYMMDD.tgz cd rk3399-nougat ./sync.sh
- git clone from gitlab
{{{1}}} source code is maintained in gitlab, You can download it by running the following command:
git clone https://gitlab.com/friendlyelec/rk3399-nougat --depth 1 -b nanopc-t4-nougat
2.3.2 Generate Image File
You can compile an Android7 source code and generate an image file:
cd rk3399-nougat ./build-nanopc-t4.sh -F -M
2.3.3 Update System with New Image
After compilation is done a new image file will be generated in the "rockdev/Image-nanopc_t4/" directory under Android7's source code directory. You can follow the steps below to update the OS in {{{1}}}:
1) Insert an SD card which is processed with EFlasher to an SD card reader and insert this reader to a PC running Ubuntu. The SD card's partitions will be automatically mounted;
2) Copy all the files under the "rockdev/Image-nanopc_t4/" directory to the SD card's android8 directory in the "FRIENDLYARM" partition;
3) Insert this SD card to {{{1}}} and reflash Android
Here is an alternative guide to update OS: sd-fuse_rk3399
