----------------------------------------------------------------------------------------------------------------------------
开发板 ：ArmSoM-Sige7开发板eMMC ：64GBLPDDR4 ：8GB
显示屏 ：15.6英寸HDMI接口显示屏u-boot ：2017.09linux ：5.10
----------------------------------------------------------------------------------------------------------------------------
一、SDK软件架构
1.1 SDK工程目录介绍
一个通用Linux SDK工程目录包含有buildroot、debian、app、kernel、u-boot、device、external等目录；
app：存放上层应用APP，主要是一些应用Demo；buildroot：存放Buildroot开发的根文件系统；debian：存放Debian开发的根文件系统；device/rockchip：存放芯片板级配置以及一些编译和打包固件的脚本和文件；docs：存放通用开发指导文档、Linux系统开发指南、芯片平台相关文档等；external：存放第三方相关仓库，包括显示、音视频、摄像头、网络、安全等；kernel：存放Kernel开发的代码；output：存放每次生成的固件信息、编译信息、XML、主机环境等；prebuilts：存放交叉编译工具链；rkbin：存放Rockchip相关二进制和工具；rockdev：存放编译输出固件，实际软链接到output/firmware；tools：存放Linux和Window操作系统下常用工具；u-boot：存放基于v2017.09版本进行开发的U-Boot代码；yocto：存放Yocto开发的根文件系统；
1.2 SDK概述
通用Linux SDK目前已集成主流的几个Linux发行版(Distribution)，发行版就是我们日常在Linux主机上使用的那些系统，为用户预先集成好的Linux操作系统及各种应用软件。Linux发行版的形式多种多样，有从功能齐全的桌面系统到服务器版本到小型系统。比如支持桌面版本的Debian系统，可定制化的Buildroot/Yocto轻量级系统。
1.2.1 Buildroot系统
Rockchip Linux SDK的Buildroot系统，其包含了基于Linux系统开发用到的各种系统源码，驱动，工具，应用软件包。Buildroot 是Linux平台上一个开源的嵌入式Linux系统自动构建框架。整个Buildroot是由Makefile脚本和Kconfig配置文件构成的。可通过Buildroot配置，编译出一个完整的可以直接烧写到机器上运行的Linux系统软件。
Buildroot有以下几点优势：
- 通过源码构建，有很大的灵活性；
- 方便的交叉编译环境，可以进行快速构建，容易上手；
- 提供系统各组件的配置，方便定制开发。
使用Buildroot的project最出名的就是Openwrt。可以看到，由它制作出的镜像可以跑在搭载16 Mb SPINOR的路由器上，系统基本没包含多余的东西。 这就是得益于Buildroot的简单化。整个Buildroot工程在一个git维护。
Buildroot使用kconfig和make，一个defconfig配置代表一种BSP支持。Buildroot 本身不具备扩展能力，用户需要自己通过脚本来完成工作。这些列出来的特点，都是和Yocto不同的地方。
注意：Buildroot实际上使用Busybox来制作根文件系统。
1.2.2 Yocto
Yocto和Buildroot一样， 是一套构建嵌入式系统的工具，但是两者的风格完全不同。
Yocto工程是通过一个个单独的包(meta)来维护，比如有的包负责核心，有的包负责外围。有的包用于跑Rockchip的芯片，有的包用于安装上weston, 有的包是则是用于跑debian， 同样采用类似机制的nodejs，社区膨胀非常厉害，活跃度很高，每个人都可分享自己的成果到github上，这样的机制保证了我们可从互联网复用别人的工作成果，相当有价值。
相比Buildroot系统，Yocto有其更强的编译机制，比如第三方包的依赖和重编，都会自动处理。缺点相对复杂、需VPN网络。
Yocto是一个非常灵活的构建系统，允许用户使用shell和Python来处理各种特殊情况。目前，该系统主要针对国外客户。如果您需要更多关于Yocto的信息，请查看以下参考资料：
Yocto；Rockchip Yocto；Yocto stable branch；
1.2.3 Debian
Debian是一种完全自由开放并广泛用于各种设备的Linux操作系统，选择Debian原因如下：
Debian是自由软件：Debian是由自由和开放源代码的软件组成，并将始终保持100%自由，每个人都能自由使用、修改，以及发布，大家可以基Rockchip构建的Debian系统进行二次开发；Debian是一个基于Linux稳定且安全的的操作系统：Debian是一个广泛用于各种设备的操作系统，其使用范围包括笔记本计算机，台式机和服务器。自1993年以来，它的稳定性和可靠性就深受用户的喜爱。我们为每个软件包提供合理的默认配置，Debian开发人员会尽可能在其生命周期内为所有软件包提供安全更新；Debian具有广泛的硬件支持：大多数硬件已获得Linux内核的支持。当自由软件无法提供足够的支持时，也可使用专用的硬件驱动程序。目前Rockchip RK3588/RK3568/RK3566/RK3399/RK3288等芯片已经适配并支持；Debian提供平滑的更新：Debian以在其发行周期内轻松流畅地进行更新而闻名，不仅如此，还包括轻松升级到下一个大版本。Rockchip目前已从Debian Stretch(9)升级到Debian Buster(10)和Bullseye(11)版本；Debian是许多其他发行版的种子和基础：许多非常受欢迎的Linux发行版，例如Ubuntu、Knoppix、PureOS、SteamOS以及Tails，都选择了Debian作为它们的软件基础。Debian提供了所有工具，因此每个人都可以用能满足自己需求的软件包来扩展Debian档案库中的软件包；Debian项目是一个社区：Debian不只是一个Linux操作系统。该软件由来自世界各地的数百名志愿者共同制作。即使您不是一个程序员或系统管理员，也可以成为Debian社区的一员；
Rockchip定制版的Debian系统是通过Shell脚本来达到获取构建Linux Debian发行版源码，编译和安装适配Rockchip硬加速包的操作系统。
1.3 SDK软件框图
SDK软件框图如下图所示：
从下至上分为启动层、内核层、库、应用层四个层次。各层次内容如下：
- 启动层主要提供系统启动，如
BootROM、U-Boot、ATF等相关支持； - 内核层主要提供
Linux Kernel的标准实现，Linux也是一个开放的操作系统，Rockchip平台的Linux核心为标准的Linux4.4/4.19/5.10内核，提供安全性，内存管理，进程管理，网络协议栈等基础支持；主要是通过Linux内核管理设备硬件资源，如CPU调度、缓存、内存、I/O等； - 库层对应一般嵌入式系统，相当于中间件层次。包含了各种系统基础库，及第三方开源程序库支持，对应用层提供
API接口，系统定制者和应用开发者可以基于Libraries层的API开发新的应用； - 应用层主要是实现具体的产品功能及交互逻辑，需要一些系统基础库及第三方程序库支持，开发者可以开发实现自己的应用程序，提供系统各种能力给到最终用户。
SDK系统启动流程是指系统上电到系统启动完成的一个软件流程，下面是linux系统启动流程：
注意：
AP和MCU内部都有集成一个BootROM，系统上电时先会运行BootROM代码，然后BootROM代码会探测外设存储器并加载Loader代码；PreLoader前有3个：miniloader(非开源)，uboot tpl和uboot splloader；
1.4 SDK开发流程
Rockchip Linux系统是基于Buildroot/Yocto/Debian系统,,内核基于kernel 4.4/4.19/5.10开发，针对多种不同产品形态开发的SDK。可以基于本SDK，有效地实现系统定制和应用移植开发。
如图所示，开发者可以遵循上述开发流程，在本地快速构建Rockchip Linux系统的开发环境和编译代码。下面将简单介绍下该流程：
- 检查系统需求：在下载代码和编译前，需确保本地的开发设备能够满足需求，包括机器的硬件能力，软件系统，工具链等。目前
SDK支持Linux操作系统环境下编译，并仅提供Linux环境下的工具链支持，其他如MacOS，Windows等系统暂不支持； - 搭建编译环境：介绍开发机器需要安装的各种软件包和工具，详见第二节
SDK开发坏境搭建。 - 选择设备：在开发过程中，需要开发者根据自己的需求，选择对应的硬件板型；
- 下载源代码：选定设备类型后，需要安装
repo工具用于批量下载源代码； - 系统定制：开发者可以根据使用的硬件板子、产品定义，定制
u-boot、kernel及rootfs，详见第五节SDK开发； - 编译与打包：介绍具备源代码后，选择产品及初始化相关的编译环境，而后执行编译命令，包括整体或模块编译以及编译清理等工作，进一步内容详见第三节
SDK编译说明。 - 烧录并运行：继生成镜像文件后，将介绍如何烧录镜像并运行在硬件设备，进一步内容详见第四节
SDK固件升级；
二、SDK开发环境搭建
2.1 概述
本节主要介绍了如何在本地搭建编译环境来编译Rockchip Linux SDK源代码，当前SDK只支持在Linux环境下编译和进行二次开发。
一个典型的嵌入式开发环境通常包括Linux服务器、PC和目标硬件版，典型开发环境如下图所示；
其中：
Linux服务器上建立交叉编译环境，为软件开发提供代码、更新下载和进行编译等服务；PC和Linux服务器共享程序，并安装Putty或Minicom，通过网络远程登陆到Linux服务器，进行交叉编译，及代码的开发调试；PC通过串口和USB与目标硬件板连接，可将编译后的镜像文件烧写到目标硬件板，并调试系统或应用程序。
2.2 源码获取
在一个大型项目中，一般会拆成多个子系统来分开管理，每一个子系统都对应着一个git仓库。但在拉取整个项目的时候就需要一个一个去拉取仓库，或者要写一个shell脚本去拉取，这样做可以，但略显笨拙。于是repo来拯救了我们，它是一个建立在git上的工具，本质其实是一个Python脚本，所以需要安装Python，像Android这样的系统也是用repo来管理的。
Rockchip Linux SDK的代码和相关文档被划分为了若干git仓库分别进行版本管理，开发者可以使用repo对这些git仓库进行统一的下载、提交、切换分支等操作。
获取Rockchip Linux软件包，需要有一个帐户访问Rockchip提供的源代码仓库。客户向瑞芯微技术窗口申请SDK，同步提供SSH公钥进行服务器认证授权，获得授权后即可同步代码。
请根据《Rockchip_User_Guide_SDK_Application_And_Synchronization_CN》文档说明操作，生成SSH公钥，发邮件至fae@rock-chips.com，申请开通SDK代码。该文档会在申请开通权限流程中，释放给客户使用。
作为一个用户这里我们大概率是无法直接申请开通SDK代码的，所以这里直接使用armsom开发板厂商提供的SDK源码；
这里我们从https://github.com/ArmSoM/armsom-rk3588-bsp下载SDK源码，命令如下：
root@ubuntu:/work/sambashare/rk3588/armsom# git clone https://github.com/ArmSoM/armsom-rk3588-bsp.git
root@ubuntu:/work/sambashare/rk3588/armsom# cd armsom-rk3588-bsp
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# ll
drwxr-xr-x 5 zhengyang zhengyang 4096 6月 10 21:42 ../
drwxr-xr-x 10 root root 4096 6月 9 12:58 app/
drwxr-xr-x 16 root root 4096 6月 9 12:58 buildroot/
lrwxrwxrwx 1 root root 39 6月 9 12:58 build.sh -> device/rockchip/common/scripts/build.sh*
drwxr-xr-x 9 root root 4096 6月 9 12:58 debian/
drwxr-xr-x 3 root root 4096 6月 9 12:58 device/
drwxr-xr-x 6 root root 4096 6月 9 12:58 docs/
lrwxrwxrwx 1 root root 27 6月 9 12:58 envsetup.sh -> buildroot/build/envsetup.sh*
drwxr-xr-x 26 root root 4096 6月 9 12:59 external/
drwxr-xr-x 8 root root 4096 6月 9 12:59 .git/
drwxr-xr-x 26 root root 4096 6月 9 12:59 kernel/
lrwxrwxrwx 1 root root 31 6月 9 12:58 Makefile -> device/rockchip/common/Makefile
drwxr-xr-x 3 root root 4096 6月 9 12:59 prebuilts/
drwxr-xr-x 9 root root 4096 6月 9 12:59 rkbin/
lrwxrwxrwx 1 root root 41 6月 9 12:59 rkflash.sh -> device/rockchip/common/scripts/rkflash.sh*
drwxr-xr-x 5 root root 4096 6月 9 12:59 tools/
drwxr-xr-x 24 root root 4096 6月 9 12:59 u-boot/
drwxr-xr-x 5 root root 4096 6月 9 12:59 uefi/
drwxr-xr-x 9 root root 4096 6月 9 12:59 yocto/注意：这里我直接从开发板厂商获取了最新的代码。
2.2.1 u-boot及kernel编译工具链
鉴于Rockchip Linux SDK目前只在Linux PC环境下编译，SDK提供了Linux下的交叉编译工具链。prebuilt目录下的工具链是u-boot和kernel使用；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# ls prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/
aarch64-none-linux-gnu-addr2line aarch64-rockchip1031-linux-gnu-addr2line
aarch64-none-linux-gnu-ar aarch64-rockchip1031-linux-gnu-ar
aarch64-none-linux-gnu-as aarch64-rockchip1031-linux-gnu-as
aarch64-none-linux-gnu-c++ aarch64-rockchip1031-linux-gnu-c++
aarch64-none-linux-gnu-c++filt aarch64-rockchip1031-linux-gnu-c++filt
aarch64-none-linux-gnu-cpp aarch64-rockchip1031-linux-gnu-cpp
aarch64-none-linux-gnu-dwp aarch64-rockchip1031-linux-gnu-dwp
aarch64-none-linux-gnu-elfedit aarch64-rockchip1031-linux-gnu-elfedit
aarch64-none-linux-gnu-g++ aarch64-rockchip1031-linux-gnu-g++
aarch64-none-linux-gnu-gcc aarch64-rockchip1031-linux-gnu-gcc
aarch64-none-linux-gnu-gcc-10.3.1 aarch64-rockchip1031-linux-gnu-gcc-10.3.1
aarch64-none-linux-gnu-gcc-ar aarch64-rockchip1031-linux-gnu-gcc-ar
aarch64-none-linux-gnu-gcc-nm aarch64-rockchip1031-linux-gnu-gcc-nm
aarch64-none-linux-gnu-gcc-ranlib aarch64-rockchip1031-linux-gnu-gcc-ranlib
aarch64-none-linux-gnu-gcov aarch64-rockchip1031-linux-gnu-gcov
aarch64-none-linux-gnu-gcov-dump aarch64-rockchip1031-linux-gnu-gcov-dump
aarch64-none-linux-gnu-gcov-tool aarch64-rockchip1031-linux-gnu-gcov-tool
aarch64-none-linux-gnu-gdb aarch64-rockchip1031-linux-gnu-gdb
aarch64-none-linux-gnu-gdb-add-index aarch64-rockchip1031-linux-gnu-gdb-add-index
aarch64-none-linux-gnu-gfortran aarch64-rockchip1031-linux-gnu-gfortran
aarch64-none-linux-gnu-gprof aarch64-rockchip1031-linux-gnu-gprof
aarch64-none-linux-gnu-ld aarch64-rockchip1031-linux-gnu-ld
aarch64-none-linux-gnu-ld.bfd aarch64-rockchip1031-linux-gnu-ld.bfd
aarch64-none-linux-gnu-ld.gold aarch64-rockchip1031-linux-gnu-ld.gold
aarch64-none-linux-gnu-lto-dump aarch64-rockchip1031-linux-gnu-lto-dump
aarch64-none-linux-gnu-nm aarch64-rockchip1031-linux-gnu-nm
aarch64-none-linux-gnu-objcopy aarch64-rockchip1031-linux-gnu-objcopy
aarch64-none-linux-gnu-objdump aarch64-rockchip1031-linux-gnu-objdump
aarch64-none-linux-gnu-ranlib aarch64-rockchip1031-linux-gnu-ranlib
aarch64-none-linux-gnu-readelf aarch64-rockchip1031-linux-gnu-readelf
aarch64-none-linux-gnu-size aarch64-rockchip1031-linux-gnu-size
aarch64-none-linux-gnu-strings aarch64-rockchip1031-linux-gnu-strings
aarch64-none-linux-gnu-strip aarch64-rockchip1031-linux-gnu-strip对应版本：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu-gcc -v
......
gcc 版本 10.3.1 20210621 (GNU Toolchain for the A-profile Architecture 10.3-2021.07 (arm-10.29))2.2.2 rootfs编译工具链
具体rootfs需要用各自对应的工具链，或者使用第三方工具链进行编译。
以Buildroo为例，具体参考：
buildroot/docs/manual/using-buildroot-toolchain.txt；buildroot/docs/manual/adding-packages.txt。
2.3 Linux服务器搭建
2.3.1 ubuntu 22.04
这里我们使用ubuntu 22.04来进行编译，因为只有该版本及以上版本glibc才支持GLIBC_2.33、GLIBC_2.34版本；由于我之前在虚拟机搭建的ubuntu版本为20.04，因此这里需要对系统进行升级；
zhengyang@ubuntu:~/桌面$ sudo apt install update-manager-core然后运行软件更新器：
主要：这里不要通过对glibc源码进行编译得到高版本的glibc，这种做法可能导致系统崩溃。
此外：硬盘空间大于40G，如果您进行多个构建，将需要更大的硬盘空间。
2.3.2 安装库和工具集
使用命令行进行设备开发时，可以通过以下步骤安装编译SDK需要的库和工具；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# sudo apt update
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# sudo apt install git ssh make gcc libssl-dev
liblz4-tool expect expect-dev g++ patchelf chrpath gawk texinfo chrpath
diffstat binfmt-support qemu-user-static live-build bison flex fakeroot
cmake gcc-multilib g++-multilib unzip device-tree-compiler ncurses-dev
libgucharmap-2-90-dev bzip2 expat gpgv2 cpp-aarch64-linux-gnu libgmp-dev
libmpc-dev bc python-is-python3 python22.3.3 设置DNS支持kgithub.com
如果PC在编译Buildroot时无法访问Google网站，需设置DNS来支持使用国内镜像kgithub.com下载dl包。
sudo sed -i '$a 43.154.68.204 kgithub.com' /etc/hosts
sudo sed -i '$a 43.155.83.75traw.kgithub.com objects.githubusercontent.kgithub.com' /etc/hosts2.3.4 检查和升级主机的python版本
python要求安装python 3.6及以上版本，检查主机python版本：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# python3 --version
Python 3.10.12如果不满足python>=3.6版本的要求， 可通过如下方式升级：
PYTHON3_VER=3.6.15
echo "wget
https://www.python.org/ftp/python/${PYTHON3_VER}/Python-${PYTHON3_VER}.tgz"
echo "tar xf Python-${PYTHON3_VER}.tgz"
echo "cd Python-${PYTHON3_VER}"
echo "sudo apt-get install libsqlite3-dev"
echo "./configure --enable-optimizations"
echo "sudo make install -j8"2.3.5 检查和升级主机的make版本
make要求安装make 4.0及以上版本，检查主机make版本；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# make -v
GNU Make 4.3
为 x86_64-pc-linux-gnu 编译
Copyright (C) 1988-2020 Free Software Foundation, Inc.
许可证：GPLv3+：GNU 通用公共许可证第 3 版或更新版本。
本软件是自由软件：您可以自由修改和重新发布它。
在法律允许的范围内没有其他保证。 如果不满足make>=4.0版本的要求， 可通过如下方式升级：
sudo apt update && sudo apt install -y autoconf autopoint
git clone https://gitee.com/mirrors/make.git
cd make
git checkout 4.2
git am $BUILDROOT_DIR/package/make/*.patch
autoreconf -f -i
./configure
make make -j8
sudo install -m 0755 make /usr/bin/make2.3.6 检查和升级主机的lz4版本
lz4要求安装1.7.3及以上版本，检查主机lz4版本
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# lz4 -v
*** LZ4 command line interface 64-bits v1.9.3, by Yann Collet ***
refusing to read from a console如果不满足LZ4>=1.7.3版本的要求， 可通过如下方式升级：
git clone https://gitee.com/mirrors/LZ4_old1.git
cd LZ4_old1
make
sudo make install
sudo install -m 0755 lz4 /usr/bin/lz4三、SDK编译说明
3.1 SDK编译命令查看
首先通过help命令查看SDK编译命令：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# make help
menuconfig - interactive curses-based configurator
oldconfig - resolve any unresolved symbols in .config
syncconfig - Same as oldconfig, but quietly, additionally update deps
olddefconfig - Same as syncconfig but sets new symbols to their default value
savedefconfig - Save current config to RK_DEFCONFIG (minimal config)
clean - Cleanup
......make实际运行是./build.sh，即也可运行./build.sh 来编译相关功能，具体可通过./build.sh help查看具体编译命
令：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# ./build.sh help
Usage: build.sh [OPTIONS]
Available options:
chip[:[:]] choose chip
defconfig[:] choose defconfig
*_defconfig switch to specified defconfig
available defconfigs:
rockchip_defconfig
rockchip_rk3588_evb1_lp4_v10_defconfig
rockchip_rk3588_evb7_v11_defconfig
rockchip_rk3588_sige7_defconfig
rockchip_rk3588s_evb1_lp4x_v10_defconfig
olddefconfig resolve any unresolved symbols in .config
savedefconfig save current config to defconfig
menuconfig interactive curses-based configurator
config modify SDK defconfig
shell setup a shell for developing
print-parts print partitions
mod-parts interactive partition table modify
edit-parts edit raw partitions
new-parts:::... re-create partitions
insert-part::[:] insert partition
del-part:(|) delete partition
move-part:(|): move partition
rename-part:(|): rename partition
resize-part:(|): resize partition
kernel[:cmds] build kernel
modules[:cmds] build kernel modules
linux-headers[:cmds] build linux-headers
kernel-config[:cmds] modify kernel defconfig
kernel-make[::] run kernel make (alias kmake)
wifibt[:[:]] build Wifi/BT
rtos build and pack RTOS
buildroot-config[:] modify buildroot defconfig
buildroot-make[::] run buildroot make (alias bmake)
rootfs[:] build default rootfs
buildroot build buildroot rootfs
yocto build yocto rootfs
debian build debian rootfs
recovery build recovery
pcba build PCBA
security_check check contidions for security boot
createkeys build security boot keys
security_ramboot build security ramboot
security_uboot build uboot with security
security_boot build boot with security
security_recovery build recovery with security
security_rootfs build rootfs with security
loader[:cmds] build loader (uboot)
uboot[:cmds] build u-boot
uefi[:cmds] build uefi
firmware pack and check firmwares
edit-package-file edit package-file
edit-ota-package-file edit A/B OTA package-file
updateimg build update image
otapackage build A/B OTA update image
all build all images
save save images and build info
allsave build all images and save them
cleanall cleanup
clean[:module[:module]]... cleanup modules
available modules:
all
config
firmware
kernel
loader
pcba
recovery
rootfs
updateimg
post-rootfs trigger post-rootfs hook scripts
help usage
Default option is 'allsave'. 我们定位到build.sh脚本入口，当我们执行./build.sh 时将会执行如下代码；
if [ "$0" != "$BASH_SOURCE" ]; then
# Sourced, executing it directly
"$BASH_SOURCE" ${@:-shell}
elif [ "$0" == "$BASH_SOURCE" ]; then
# Executed directly
main $@
fi$0代表脚本名，而$BASH_SOURCE代表脚本文件的路径，因此当执行./build.sh 时，$0和$BASH_SOURCE会相同。
因此执行main $@，将调用名为main的函数，并将所有传递给脚本的参数传递给main函数。
有关build.sh文件的分析参考最后一节内容。
3.2 SDK板级配置
具体板级配置说明如下，进入工程device/rockchip/rk3588目录
| 板级配置 | 说明 |
|---|---|
| rockchip_rk3588_evb1_lp4_v10_defconfig | 适用于RK3588 EVB1搭配LPDDR4开发板 |
| rockchip_rk3588_evb3_lp5_v10_defconfig | 适用于RK3588 EVB3 搭配 LPDDR5开发板 |
| rockchip_rk3588_evb7_lp4_v10_defconfig | 适用于RK3588 EVB7搭配LPDDR4开发板 |
| rockchip_rk3588s_evb1_lp4x_v10_defconfig | 适用于RK3588S EVB1搭配LPDDR4开发板 |
| rockchip_rk3562_evb1_lp4x_v10_defconfig | 适用于RK3562 EVB1搭配LPDDR4开发板 |
| rockchip_rk3562_evb2_ddr4_v10_defconfig | 适用于 RK3566 EVB2 搭配DDR4开发板 |
| rockchip_rk3588_sige7_defconfig | 适用于RK3355 Sige7开发板 |
| ...... | ...... |
| rockchip_defconfig | 默认配置, 具体会软链接到默认一个板级配置 |
可通过make lunch或者./build.sh lunch进行配置，比如rk3588芯片；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# ./build.sh lunch
Log saved at /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/sessions/2024-06-10_22-25-38
Pick a defconfig:
1. rockchip_defconfig
2. rockchip_rk3588_evb1_lp4_v10_defconfig
3. rockchip_rk3588_evb7_v11_defconfig
4. rockchip_rk3588_sige7_defconfig
5. rockchip_rk3588s_evb1_lp4x_v10_defconfig
Which would you like? [1]:比如这里我们选择4：
Which would you like? [1]: 4
Switching to defconfig: /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/.chip/rockchip_rk3588_sige7_defconfig
make: Entering directory '/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/common'
#
# configuration written to /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/.config
#
make: Leaving directory '/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/common'这里生成了output/.config配置文件，内容如下：
#
# Automatically generated file; DO NOT EDIT.
# Rockchip Linux SDK Configuration
#
RK_DEFCONFIG="/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/.chips/rk3588/rockchip_rk3588_sige7_defconfig"
RK_CHIP_FAMILY="rk3588"
RK_CHIP="rk3588"
#
# Rootfs
#
RK_BUILDROOT_BASE_CFG="rk3588"
RK_BUILDROOT_CFG="rockchip_${RK_BUILDROOT_BASE_CFG}"
RK_YOCTO_CFG="rockchip-rk3588-evb"
RK_YOCTO_CHROMIUM=y
RK_YOCTO_DISPLAY_PLATFORM="wayland"
RK_YOCTO_DISPLAY_PLATFORM_WAYLAND=y
# RK_YOCTO_DISPLAY_PLATFORM_X11 is not set
RK_YOCTO_USBMOUNT=y
RK_DEBIAN_VERSION="bullseye"
RK_DEBIAN_ARCH="arm64"
RK_DEBIAN_ARM64=y
# RK_DEBIAN_ARMHF is not set
RK_ROOTFS_SYSTEM="buildroot"
RK_ROOTFS_SYSTEM_BUILDROOT=y
# RK_ROOTFS_SYSTEM_DEBIAN is not set
# RK_ROOTFS_SYSTEM_YOCTO is not set
RK_ROOTFS_TYPE="ext4"
# RK_ROOTFS_INITRD is not set
......3.3 配置不同启动/内核/系统等组件
SDK可通过make menuconfig进行相关配置，目前可配组件主要如下:
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# make menuconfig
(/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/.chips/rk3588/rockchip_rk
Rootfs --->
Loader (u-boot) --->
RTOS --->
Kernel --->
Boot --->
Recovery (buildroot) --->
PCBA test (buildroot) --->
Security --->
Extra partitions --->
Firmware --->
Update (Update image, OTA and A/B) --->
Others configurations --->通过以上config，可选择不同rootfs/loader/kernel等配置，进行各种定制化编译。另外还带有强大命令行切换功能。
注意menuconfig配置之后，需要make savedefconfig保存配置；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# make savedefconfig这里本质上就是修改output/.config文件。
3.4 全自动编译
进入工程根目录执行以下命令自动完成所有的编译，如果只编译模块代码(uboot，kernel，rootfs，recovery)，运行：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# ./build.sh all输出内容如下：
点击查看代码
Log saved at /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/sessions/2024-06-10_22-51-26
==========================================
Final configs
==========================================
RK_BOOT_FIT_ITS=boot.its
RK_BOOT_IMG=boot.img
RK_BUILDROOT_CFG=rockchip_rk3588
RK_CHIP=rk3588
RK_CHIP_FAMILY=rk3588
RK_DEBIAN_ARCH=arm64
RK_DEBIAN_ARM64=y
RK_DEBIAN_VERSION=bullseye
RK_DEFCONFIG=/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/.chips/rk3588/rockchip_rk3588_sige7_defconfig
RK_EXTRA_PARTITION_NUM=2
RK_EXTRA_PARTITION_STR=oem:oem:/oem:ext4:defaults:normal:auto:@userdata:userdata:/userdata:ext4:defaults:normal:auto:@@@
RK_KERNEL_ARCH=arm64
RK_KERNEL_ARM64=y
RK_KERNEL_CFG=rockchip_linux_defconfig
RK_KERNEL_CFG_FRAGMENTS=rk3588_linux.config
RK_KERNEL_DTB=kernel/arch/arm64/boot/dts/rockchip/rk3588-armsom-sige7.dtb
RK_KERNEL_DTS=kernel/arch/arm64/boot/dts/rockchip/rk3588-armsom-sige7.dts
RK_KERNEL_IMG=kernel/arch/arm64/boot/Image
RK_KERNEL_KBUILD_ARCH=host
RK_KERNEL_KBUILD_HOST=y
RK_KERNEL_VERSION=5.10
RK_KERNEL_VERSION_REAL=5.10
RK_MISC=y
RK_MISC_BLANK=y
RK_PARAMETER=parameter.txt
RK_PCBA_CFG=rockchip_rk3588_pcba
RK_RECOVERY_CFG=rockchip_rk3588_recovery
RK_RECOVERY_FIT_ITS=boot4recovery.its
RK_ROOTFS_IRQBALANCE=y
RK_ROOTFS_OVERLAY_DIRS=y
RK_ROOTFS_SYSTEM=buildroot
RK_ROOTFS_SYSTEM_BUILDROOT=y
RK_ROOTFS_TYPE=ext4
RK_ROOTFS_UDEV_RULES=y
RK_SAVE_TRACKED=y
RK_SESSION=2024-06-11_22-45-04
RK_UBOOT_ARCH=arm64
RK_UBOOT_ARM64=y
RK_UBOOT_CFG=rk3588
RK_UPDATE=y
RK_USB_ADBD=y
RK_USB_ADBD_BASH=y
RK_USB_ADBD_TCP_PORT=5555
RK_USE_FIT_IMG=y
RK_WIFIBT_CHIP=ALL_AP
RK_YOCTO_CFG=rockchip-rk3588-evb
RK_YOCTO_CHROMIUM=y
RK_YOCTO_DISPLAY_PLATFORM=wayland
RK_YOCTO_DISPLAY_PLATFORM_WAYLAND=y
RK_YOCTO_USBMOUNT=y
==========================================
Start building all images
==========================================
Using kernel version(5.10) from environment
Toolchain for kernel:
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu-
==========================================
Start building kernel
==========================================
+ make -C /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/kernel/ -j7 CROSS_COMPILE=/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu- ARCH=arm64 rockchip_linux_defconfig rk3588_linux.config
make: Entering directory '/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/kernel'
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/confdata.o
HOSTCC scripts/kconfig/expr.o
LEX scripts/kconfig/lexer.lex.c
YACC scripts/kconfig/parser.tab.[ch]
HOSTCC scripts/kconfig/preprocess.o
HOSTCC scripts/kconfig/symbol.o
HOSTCC scripts/kconfig/util.o
HOSTCC scripts/kconfig/lexer.lex.o
HOSTCC scripts/kconfig/parser.tab.o
HOSTLD scripts/kconfig/conf
#
# configuration written to .config
#
......
LD [M] drivers/leds/trigger/ledtrig-camera.ko
Image: resource.img (with rk3588-armsom-sige7.dtb logo.bmp logo_kernel.bmp) is ready
Image: boot.img (with Image resource.img) is ready
Image: zboot.img (with Image.lz4 resource.img) is ready
make: Leaving directory '/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/kernel'
+ /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/common/scripts/mk-fitimage.sh kernel/boot.img boot.its kernel/arch/arm64/boot/Image
FIT description: U-Boot FIT source file for arm
Created: Tue Jun 11 22:52:08 2024
Image 0 (fdt)
Description: unavailable
Created: Tue Jun 11 22:52:08 2024
Type: Flat Device Tree
Compression: uncompressed
Data Size: 276878 Bytes = 270.39 KiB = 0.26 MiB
Architecture: AArch64
Load Address: 0xffffff00
Hash algo: sha256
Hash value: 2e1efecb7de8f6d6f6dc99aceac3316169528dbe2343075acbc97c676863a54a
Image 1 (kernel)
Description: unavailable
Created: Tue Jun 11 22:52:08 2024
Type: Kernel Image
Compression: uncompressed
Data Size: 35650048 Bytes = 34814.50 KiB = 34.00 MiB
Architecture: AArch64
OS: Linux
Load Address: 0xffffff01
Entry Point: 0xffffff01
Hash algo: sha256
Hash value: 2de5ee7d2ebdda89a527236a37b485ec9a695366fee730a72d5c887f76026682
Image 2 (resource)
Description: unavailable
Created: Tue Jun 11 22:52:08 2024
Type: Multi-File Image
Compression: uncompressed
Data Size: 1692160 Bytes = 1652.50 KiB = 1.61 MiB
Hash algo: sha256
Hash value: 16b3aea0b954a45350b6569f67cd6aa082d112a288a4d22331a41b1dee58699d
Default Configuration: 'conf'
Configuration 0 (conf)
Description: unavailable
Kernel: kernel
FDT: fdt
Not Found io-domains in kernel/arch/arm64/boot/dts/rockchip/rk3588-armsom-sige7.dts
==========================================
Start building rootfs(buildroot)
==========================================
==========================================
Start building buildroot(2021.11)
==========================================
make: Entering directory '/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot'
GEN /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588/Makefile
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/build/parse_defconfig.sh /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/configs/rockchip_rk3588_defconfig /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588/.config.in
Parsing defconfig: /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/configs/rockchip_rk3588_defconfig
.......
Log saved on /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/sessions/2024-06-11_22-45-04/br-rockchip_rk3588_2024-06-11_22-52-17.log
Generated images:
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/rootfs/rootfs.cpio
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/rootfs/rootfs.cpio.gz
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/rootfs/rootfs.ext2
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/rootfs/rootfs.ext4
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/rootfs/rootfs.squashfs
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/rootfs/rootfs.tar
you take 7:31.54 to build buildroot
# 2024-06-11 22:53:12
# run hook: /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588/target rockchip_rk3588_defconfig"
Running 00-wifibt.sh for /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588/target (buildroot init=busybox)...
Building Wifi/BT module and firmwares...
==========================================
Start building wifi/BT (ALL_AP)
==========================================
kernel config: CONFIG_USB=y CONFIG_MMC=y CONFIG_RFKILL=y
building bcmdhd sdio
make[1]: Entering directory '/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/kernel'
CC [M] /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/external/rkwifibt/drivers/bcmdhd/aiutils.o
CC [M] /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/external/rkwifibt/drivers/bcmdhd/siutils.o
CC [M] /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/external/rkwifibt/drivers/bcmdhd/sbutils.o
......
sent 1,143,224 bytes received 71 bytes 2,286,590.00 bytes/sec
total size is 1,143,678 speedup is 1.00
Handling overlay: /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/common/overlays/rootfs/frecon)...
Installing overlay: /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/common/overlays/rootfs/common-tools to /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588/target...
sending incremental file list
copying unsafe symlink "usr/bin/vendor_storage" -> "../../../../../tools/armhf/vendor_storage"
copying unsafe symlink "usr/bin/modetest" -> "../../../../../tools/armhf/modetest"
copying unsafe symlink "usr/bin/updateEngine" -> "../../../../../tools/armhf/updateEngine"
copying unsafe symlink "usr/bin/update" -> "../../../../../tools/armhf/update"
copying unsafe symlink "usr/bin/io" -> "../../../../../tools/armhf/io"
usr/bin/io
usr/bin/update
usr/bin/updateEngine
usr/bin/vendor_storage
sent 4,384,849 bytes received 94 bytes 8,769,886.00 bytes/sec
total size is 4,999,800 speedup is 1.14
Running 95-partitions.sh for /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588/target (buildroot init=busybox)...
Preparing extra partitions...
Running 99-owner.sh for /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588/target (buildroot init=busybox)...
Running mk-rootfs.sh - build_buildroot /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/rootfs succeeded.
Running mk-rootfs.sh - build_rootfs succeeded.
==========================================
Start building recovery(buildroot)
==========================================
make: Entering directory '/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot'
GEN /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588_recovery/Makefile
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/build/parse_defconfig.sh /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/configs/rockchip_rk35
......
2024-06-11T23:00:03 >>> Generating root filesystems common tables
2024-06-11T23:00:03 >>> Generating filesystem image rootfs.cpio
2024-06-11T23:00:06 >>> Generating filesystem image rootfs.ext2
2024-06-11T23:00:06 >>> Generating filesystem image rootfs.squashfs
2024-06-11T23:00:07 >>> Generating filesystem image rootfs.tar
Done in 21s
Log saved on /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/sessions/2024-06-11_22-45-04/br-rockchip_rk3588_recovery_2024-06-11_22-59-47.log
Generated images:
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/rootfs.cpio
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/rootfs.cpio.gz
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/rootfs.ext2
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/rootfs.ext4
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/rootfs.squashfs
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/rootfs.tar
you take 0:27.69 to build recovery(buildroot)
Packing /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/rootfs.cpio.gz to /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/recovery.img
FIT description: U-Boot FIT source file for arm
Created: Tue Jun 11 23:00:08 2024
Image 0 (fdt)
Description: unavailable
Created: Tue Jun 11 23:00:08 2024
Type: Flat Device Tree
Compression: uncompressed
Data Size: 276878 Bytes = 270.39 KiB = 0.26 MiB
Architecture: AArch64
Load Address: 0xffffff00
Hash algo: sha256
Hash value: 2e1efecb7de8f6d6f6dc99aceac3316169528dbe2343075acbc97c676863a54a
Image 1 (kernel)
Description: unavailable
Created: Tue Jun 11 23:00:08 2024
Type: Kernel Image
Compression: uncompressed
Data Size: 35650048 Bytes = 34814.50 KiB = 34.00 MiB
Architecture: AArch64
OS: Linux
Load Address: 0xffffff01
Entry Point: 0xffffff01
Hash algo: sha256
Hash value: 2de5ee7d2ebdda89a527236a37b485ec9a695366fee730a72d5c887f76026682
Image 2 (ramdisk)
Description: unavailable
Created: Tue Jun 11 23:00:08 2024
Type: RAMDisk Image
Compression: uncompressed
Data Size: 6673958 Bytes = 6517.54 KiB = 6.36 MiB
Architecture: AArch64
OS: Linux
Load Address: 0xffffff02
Entry Point: unavailable
Hash algo: sha256
Hash value: 61124fb71f146a757ce43bb199e5fa39be4c6adb56ba80251cd3b184c3aca900
Image 3 (resource)
Description: unavailable
Created: Tue Jun 11 23:00:08 2024
Type: Multi-File Image
Compression: uncompressed
Data Size: 1692160 Bytes = 1652.50 KiB = 1.61 MiB
Hash algo: sha256
Hash value: 16b3aea0b954a45350b6569f67cd6aa082d112a288a4d22331a41b1dee58699d
Default Configuration: 'conf'
Configuration 0 (conf)
Description: unavailable
Kernel: kernel
Init Ramdisk: ramdisk
FDT: fdt
you take 0:00.51 to pack recovery image
Running mk-recovery.sh - build_recovery succeeded.
Toolchain for loader (u-boot):
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu-
==========================================
Start building loader
==========================================
+ cd u-boot
+ ./make.sh CROSS_COMPILE=/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu- rk3588
## make rk3588_defconfig -j12
#
# configuration written to .config
#
scripts/kconfig/conf --silentoldconfig Kconfig
CHK include/config.h
CFG u-boot.cfg
GEN include/autoconf.mk.dep
CFG spl/u-boot.cfg
CFG tpl/u-boot.cfg
GEN include/autoconf.mk
......
CAT spl/u-boot-spl-dtb.bin
COPY spl/u-boot-spl.bin
CFGCHK u-boot.cfg
SEC=1
pack u-boot.itb okay! Input: /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/rkbin/RKTRUST/RK3588TRUST.ini
FIT description: FIT Image with ATF/OP-TEE/U-Boot/MCU
Created: Tue Jun 11 23:00:17 2024
Image 0 (uboot)
Description: U-Boot
Created: Tue Jun 11 23:00:17 2024
Type: Standalone Program
Compression: uncompressed
Data Size: 1317128 Bytes = 1286.26 KiB = 1.26 MiB
Architecture: AArch64
Load Address: 0x00200000
Entry Point: unavailable
Hash algo: sha256
Hash value: 7fd2ffe37130ca48d6f18001add4039373925d4d0619cc31de411ef3e187f02d
Image 1 (atf-1)
Description: ARM Trusted Firmware
Created: Tue Jun 11 23:00:17 2024
Type: Firmware
Compression: uncompressed
Data Size: 200008 Bytes = 195.32 KiB = 0.19 MiB
Architecture: AArch64
Load Address: 0x00040000
Hash algo: sha256
Hash value: c902200be1343fe569e54778c286005b1c6163606664c463a24d787be4376966
Image 2 (atf-2)
Description: ARM Trusted Firmware
Created: Tue Jun 11 23:00:17 2024
Type: Firmware
Compression: uncompressed
Data Size: 24576 Bytes = 24.00 KiB = 0.02 MiB
Architecture: AArch64
Load Address: 0x000f0000
Hash algo: sha256
Hash value: aa71013e72d7ab4be264c1093b155ef06e65d0a263d552be25b13c8ddf285586
Image 3 (atf-3)
Description: ARM Trusted Firmware
Created: Tue Jun 11 23:00:17 2024
Type: Firmware
Compression: uncompressed
Data Size: 24576 Bytes = 24.00 KiB = 0.02 MiB
Architecture: AArch64
Load Address: 0xff100000
Hash algo: sha256
Hash value: 225d6bf0712f850648223365ba06a73ba5f6315fb8a9580f23ab48ece795f91e
Image 4 (optee)
Description: OP-TEE
Created: Tue Jun 11 23:00:17 2024
Type: Firmware
Compression: uncompressed
Data Size: 465304 Bytes = 454.40 KiB = 0.44 MiB
Architecture: AArch64
Load Address: 0x08400000
Hash algo: sha256
Hash value: 66e30bf9e879405a49797aaa6c08ca1c41aa325443e910af42e3df309e65909b
Image 5 (fdt)
Description: U-Boot dtb
Created: Tue Jun 11 23:00:17 2024
Type: Flat Device Tree
Compression: uncompressed
Data Size: 8141 Bytes = 7.95 KiB = 0.01 MiB
Architecture: AArch64
Hash algo: sha256
Hash value: 8ecccd16d2f12c4f5639c386e51f206eb679638495283d9297497ddfb0aae01a
Default Configuration: 'conf'
Configuration 0 (conf)
Description: rk3588-evb
Kernel: unavailable
Firmware: atf-1
FDT: fdt
Loadables: uboot
atf-2
atf-3
optee
********boot_merger ver 1.31********
Info:Pack loader ok.
pack loader okay! Input: /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/rkbin/RKBOOT/RK3588MINIALL.ini
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/u-boot
Image(no-signed, version=0): uboot.img (FIT with uboot, trust...) is ready
Image(no-signed): rk3588_spl_loader_v1.13.112.bin (with spl, ddr...) is ready
pack uboot.img okay! Input: /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/rkbin/RKTRUST/RK3588TRUST.ini
Platform RK3588 is build OK, with new .config(make rk3588_defconfig -j12)
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu-
Tue Jun 11 23:00:17 CST 2024
+ cd ..
Running mk-loader.sh - build_loader succeeded.
==========================================
Start packing firmwares
==========================================
Linking /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/firmware/parameter.txt from /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/.chip/parameter.txt...
Generating blank misc...
Generated blank misc image:
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/firmware/misc.img
Preparing partiton oem
Merging /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/common/images/oem/normal into /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/oem
Packing /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/firmware/oem.img from /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/oem.fs
Using host tools in /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588/host
Making /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/firmware/oem.img from /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/oem (auto sized)
Making /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/firmware/oem.img from /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/oem with size(17048KB)
mke2fs 1.46.5 (30-Dec-2021)
Creating regular file /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/firmware/oem.img
Creating filesystem with 17048 1k blocks and 4272 inodes
Filesystem UUID: b3ce6911-8296-4559-b1bc-df021c5476d0
Superblock backups stored on blocks:
8193
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Copying files into the device: done
Writing superblocks and filesystem accounting information: done
tune2fs 1.46.5 (30-Dec-2021)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
Done packing /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/firmware/oem.img
Preparing partiton userdata
Merging /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/common/images/userdata/normal into /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/userdata
Packing /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/firmware/userdata.img from /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/userdata.fs
Using host tools in /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588/host
Making /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/firmware/userdata.img from /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/userdata (auto sized)
Making /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/firmware/userdata.img from /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/userdata with size(4368KB)
mke2fs 1.46.5 (30-Dec-2021)
Creating regular file /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/firmware/userdata.img
Creating filesystem with 4368 1k blocks and 1088 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Copying files into the device: done
Writing superblocks and filesystem accounting information: done
tune2fs 1.46.5 (30-Dec-2021)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
Done packing /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/firmware/userdata.img
Packed files:
MiniLoaderAll.bin(/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/u-boot/rk3588_spl_loader_v1.13.112.bin): 461K
boot.img(/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/kernel/boot.img): 36M
misc.img: 48K
oem.img: 17M
parameter.txt(/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/.chips/rk3588/parameter.txt): 539
recovery.img(/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588_recovery/images/recovery.img): 43M
rootfs.img(/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588/images/rootfs.ext2): 728M
uboot.img(/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/u-boot/uboot.img): 4.0M
userdata.img: 4.3M
Images in /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/firmware are ready!
Running mk-firmware.sh - build_firmware succeeded.
==========================================
Start packing update image
==========================================
Generating package-file for update:
# NAME PATH
package-file package-file
parameter parameter.txt
bootloader MiniLoaderAll.bin
uboot uboot.img
misc misc.img
boot boot.img
recovery recovery.img
backup RESERVED
rootfs rootfs.img
oem oem.img
userdata userdata.img
Packing /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/rockdev/update.img for update...
Android Firmware Package Tool v2.2
------ PACKAGE ------
Add file: ./package-file
package-file,Add file: ./package-file done,offset=0x800,size=0xe1,userspace=0x1
Add file: ./parameter.txt
parameter,Add file: ./parameter.txt done,offset=0x1000,size=0x227,userspace=0x1,flash_address=0x00000000
Add file: ./MiniLoaderAll.bin
bootloader,Add file: ./MiniLoaderAll.bin done,offset=0x1800,size=0x731c0,userspace=0xe7
Add file: ./uboot.img
uboot,Add file: ./uboot.img done,offset=0x75000,size=0x400000,userspace=0x800,flash_address=0x00004000
Add file: ./misc.img
misc,Add file: ./misc.img done,offset=0x475000,size=0xc000,userspace=0x18,flash_address=0x00006000
Add file: ./boot.img
boot,Add file: ./boot.img done,offset=0x481000,size=0x23e1200,userspace=0x47c3,flash_address=0x00008000
Add file: ./recovery.img
recovery,Add file: ./recovery.img done,offset=0x2862800,size=0x2a3ea00,userspace=0x547e,flash_address=0x00028000
Add file: ./rootfs.img
rootfs,Add file: ./rootfs.img done,offset=0x52a1800,size=0x2d800000,userspace=0x5b000,flash_address=0x00078000
Add file: ./oem.img
oem,Add file: ./oem.img done,offset=0x32aa1800,size=0x10a6000,userspace=0x214c,flash_address=0x01c78000
Add file: ./userdata.img
userdata,Add file: ./userdata.img done,offset=0x33b47800,size=0x444000,userspace=0x888,flash_address=0x01cb8000
Add CRC...
Make firmware OK!
------ OK ------
********rkImageMaker ver 2.23********
Generating new image, please wait...
Writing head info...
Writing boot file...
Writing firmware...
Generating MD5 data...
MD5 data generated successfully!
New image generated successfully!
Running mk-updateimg.sh - build_updateimg succeeded.
Running 99-all.sh - build_all succeeded.从输出日志可以看出编译顺序，我们接下来依次介绍。
3.4.1 编译kernel
通过mk-fitimage.sh脚本生成boot.img位于kernel目录下；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll kernel/boot.img
-rw-r--r-- 1 root root 37622272 6月 11 22:52 kernel/boot.img3.4.2 编译rootfs
编译输出根文件系统rootfs.ext4位于output/rootfs目录下；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll output/rootfs
lrwxrwxrwx 1 root root 42 6月 11 22:52 output/rootfs -> ../buildroot/output/rockchip_rk3588/images/
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll output/rootfs/
-rw-r--r-- 1 root root 615713280 6月 11 22:58 rootfs.cpio
-rw-r--r-- 1 root root 273882955 6月 11 22:59 rootfs.cpio.gz
-rw-r--r-- 1 root root 763363328 6月 11 22:59 rootfs.ext2
lrwxrwxrwx 1 root root 11 6月 11 22:59 rootfs.ext4 -> rootfs.ext2
-rw-r--r-- 1 root root 275013632 6月 11 22:59 rootfs.squashfs
-rw-r--r-- 1 root root 624517120 6月 11 22:59 rootfs.tar系统默认是Buildroot，可以通过设置坏境变量RK_ROOTFS_SYSTEM指定不同rootfs。RK_ROOTFS_SYSTEM目前可设定三种系统：buildroot、debian、 yocto。
比如需要debain可以通过以下命令进行生成：
RK_ROOTFS_SYSTEM=debian ./build.sh all3.4.3 编译wifi/BT模块
编译wifi/BT模块，并打包到根文件系统。
3.4.4 编译recovery
通过mk-recovery.sh脚本编译完成输出recovery.img，位于output/recovery目录下；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll output/recovery
lrwxrwxrwx 1 root root 51 6月 11 22:59 output/recovery -> ../buildroot/output/rockchip_rk3588_recovery/images/
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll output/recovery/
-rw-r--r-- 1 root root 44296704 6月 11 23:00 recovery.img
-rw-r--r-- 1 root root 15763968 6月 11 23:00 rootfs.cpio
-rw-r--r-- 1 root root 6673958 6月 11 23:00 rootfs.cpio.gz
-rw-r--r-- 1 root root 43187200 6月 11 23:00 rootfs.ext2
lrwxrwxrwx 1 root root 11 6月 11 23:00 rootfs.ext4 -> rootfs.ext2
-rw-r--r-- 1 root root 6635520 6月 11 23:00 rootfs.squashfs
-rw-r--r-- 1 root root 16844800 6月 11 23:00 rootfs.tar注意：recovery.img是由kernel+dtb+ramdisk组成的根文件系统，主要用于升级操作。
3.4.5 编译u-boot
通过mk-loader.sh脚本编译loader，编译完成生成uboot.img、rk3588_spl_loader_v1.13.112.bin位于u-boot目录下；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll u-boot/uboot.img
-rw-r--r-- 1 root root 4194304 6月 11 23:00 u-boot/uboot.img
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll u-boot/rk3588_spl_loader_v1.13.112.bin
-rw-r--r-- 1 root root 471488 6月 11 23:00 u-boot/rk3588_spl_loader_v1.13.112.bin3.4.6 打包分区镜像
通过mk-firmware.sh 脚本生成存放各个分区镜像的目录，位于output/firmware/目录下；
- 创建
parameter.txt链接文件，指向device/rockchip/.chips/rk3588/parameter.txt； - 创建
misc分区镜像文件：misc.img； - 创建
oem分区镜像文件：oem.img； - 创建
userdata分区镜像文件：userdata.img； - 创建
MiniLoaderAll.bin链接文件，指向u-boot/rk3588_spl_loader_v1.13.112.bin； - 创建
uboot.img链接文件，指向u-boot/uboot.img； - 创建
boot.img链接文件，指向kernel/boot.img； - 创建
recovery.img链接文件，指向buildroot/output/rockchip_rk3588_recovery/images/recovery.img； - 创建
rootfs.img链接文件，指向buildroot/output/rockchip_rk3588/images/rootfs.img。
查看目录：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll output/firmware/
lrwxrwxrwx 1 root root 21 6月 11 22:52 boot.img -> ../../kernel/boot.img
lrwxrwxrwx 1 root root 44 6月 11 23:00 MiniLoaderAll.bin -> ../../u-boot/rk3588_spl_loader_v1.13.112.bin
-rw-r--r-- 1 root root 49152 6月 11 23:00 misc.img
-rw-r--r-- 1 root root 17457152 6月 11 23:00 oem.img
lrwxrwxrwx 1 root root 49 6月 11 23:00 parameter.txt -> ../../device/rockchip/.chips/rk3588/parameter.txt
lrwxrwxrwx 1 root root 67 6月 11 23:00 recovery.img -> ../../buildroot/output/rockchip_rk3588_recovery/images/recovery.img
lrwxrwxrwx 1 root root 57 6月 11 22:59 rootfs.img -> ../../buildroot/output/rockchip_rk3588/images/rootfs.ext2
lrwxrwxrwx 1 root root 22 6月 11 23:00 uboot.img -> ../../u-boot/uboot.img
lrwxrwxrwx 1 root root 26 6月 11 23:00 update.img -> ../update/Image/update.img
-rw-r--r-- 1 root root 4472832 6月 11 23:00 userdata.img此外，我们在rockdev 目录下也可看到这些分区镜像；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll rockdev/
lrwxrwxrwx 1 root root 21 6月 11 22:52 boot.img -> ../../kernel/boot.img
lrwxrwxrwx 1 root root 44 6月 11 23:00 MiniLoaderAll.bin -> ../../u-boot/rk3588_spl_loader_v1.13.112.bin
-rw-r--r-- 1 root root 49152 6月 11 23:00 misc.img
-rw-r--r-- 1 root root 17457152 6月 11 23:00 oem.img
lrwxrwxrwx 1 root root 49 6月 11 23:00 parameter.txt -> ../../device/rockchip/.chips/rk3588/parameter.txt
lrwxrwxrwx 1 root root 67 6月 11 23:00 recovery.img -> ../../buildroot/output/rockchip_rk3588_recovery/images/recovery.img
lrwxrwxrwx 1 root root 57 6月 11 22:59 rootfs.img -> ../../buildroot/output/rockchip_rk3588/images/rootfs.ext2
lrwxrwxrwx 1 root root 22 6月 11 23:00 uboot.img -> ../../u-boot/uboot.img
lrwxrwxrwx 1 root root 26 6月 11 23:00 update.img -> ../update/Image/update.img
-rw-r--r-- 1 root root 4472832 6月 11 23:00 userdata.img3.4.7 打包统一固件
打包各个分区镜像生成update.img；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll output/update/
drwxr-xr-x 2 root root 4096 6月 11 23:00 Image/
lrwxrwxrwx 1 root root 18 6月 11 23:00 package-file -> Image/package-file
lrwxrwxrwx 1 root root 16 6月 11 23:00 update.img -> Image/update.img
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll output/update/Image/
lrwxrwxrwx 1 root root 24 6月 11 23:00 boot.img -> ../../../kernel/boot.img
lrwxrwxrwx 1 root root 47 6月 11 23:00 MiniLoaderAll.bin -> ../../../u-boot/rk3588_spl_loader_v1.13.112.bin
lrwxrwxrwx 1 root root 23 6月 11 23:00 misc.img -> ../../firmware/misc.img
lrwxrwxrwx 1 root root 22 6月 11 23:00 oem.img -> ../../firmware/oem.img
-rw-r--r-- 1 root root 225 6月 11 23:00 package-file
lrwxrwxrwx 1 root root 52 6月 11 23:00 parameter.txt -> ../../../device/rockchip/.chips/rk3588/parameter.txt
lrwxrwxrwx 1 root root 70 6月 11 23:00 recovery.img -> ../../../buildroot/output/rockchip_rk3588_recovery/images/recovery.img
lrwxrwxrwx 1 root root 60 6月 11 23:00 rootfs.img -> ../../../buildroot/output/rockchip_rk3588/images/rootfs.ext2
lrwxrwxrwx 1 root root 25 6月 11 23:00 uboot.img -> ../../../u-boot/uboot.img
-rw-r--r-- 1 root root 872409674 6月 11 23:00 update.img
-rw-r--r-- 1 root root 871938052 6月 11 23:00 update.raw.img
lrwxrwxrwx 1 root root 27 6月 11 23:00 userdata.img -> ../../firmware/userdata.img3.4.8 清理磁盘
因此我们将根文件系统移动到/work/tftproot文件；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ cp buildroot/output/rockchip_rk3588/images/rootfs.ext2 /work/tftpboot/该次编译会占用大量磁盘空间(我这里占用了40G+)，导致剩余磁盘空间不充足，因此必要时候可以删除buildroot/output目录。
3.5 模块编译
3.5.1 U-Boot编译
编译命令如下：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# ./build.sh uboot输出详情如下：
点击查看代码
Log saved at /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/sessions/2024-06-16_19-21-59
==========================================
Final configs
==========================================
RK_BOOT_FIT_ITS=boot.its
RK_BOOT_IMG=boot.img
RK_BUILDROOT_CFG=rockchip_rk3588
RK_CHIP=rk3588
RK_CHIP_FAMILY=rk3588
RK_DEBIAN_ARCH=arm64
......
Toolchain for loader (u-boot):
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu-
==========================================
Start building uboot
==========================================
+ cd u-boot
+ ./make.sh CROSS_COMPILE=/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu- rk3588
## make rk3588_defconfig -j12
#
# configuration written to .config
#
scripts/kconfig/conf --silentoldconfig Kconfig
CHK include/config.h
CFG u-boot.cfg
......
CAT spl/u-boot-spl-dtb.bin
COPY spl/u-boot-spl.bin
CFGCHK u-boot.cfg
SEC=1
pack u-boot.itb okay! Input: /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/rkbin/RKTRUST/RK3588TRUST.ini
FIT description: FIT Image with ATF/OP-TEE/U-Boot/MCU
Created: Sun Jun 16 19:23:11 2024
Image 0 (uboot)
Description: U-Boot
Created: Sun Jun 16 19:23:11 2024
Type: Standalone Program
Compression: uncompressed
Data Size: 1317128 Bytes = 1286.26 KiB = 1.26 MiB
Architecture: AArch64
Load Address: 0x00200000
Entry Point: unavailable
Hash algo: sha256
Hash value: de3ce33f68a9408cbcdfd582c4455ea803ca5fbc5a4c96d07f7a519c4d110340
Image 1 (atf-1)
Description: ARM Trusted Firmware
Created: Sun Jun 16 19:23:11 2024
Type: Firmware
Compression: uncompressed
Data Size: 200008 Bytes = 195.32 KiB = 0.19 MiB
Architecture: AArch64
Load Address: 0x00040000
Hash algo: sha256
Hash value: c902200be1343fe569e54778c286005b1c6163606664c463a24d787be4376966
Image 2 (atf-2)
Description: ARM Trusted Firmware
Created: Sun Jun 16 19:23:11 2024
Type: Firmware
Compression: uncompressed
Data Size: 24576 Bytes = 24.00 KiB = 0.02 MiB
Architecture: AArch64
Load Address: 0x000f0000
Hash algo: sha256
Hash value: aa71013e72d7ab4be264c1093b155ef06e65d0a263d552be25b13c8ddf285586
Image 3 (atf-3)
Description: ARM Trusted Firmware
Created: Sun Jun 16 19:23:11 2024
Type: Firmware
Compression: uncompressed
Data Size: 24576 Bytes = 24.00 KiB = 0.02 MiB
Architecture: AArch64
Load Address: 0xff100000
Hash algo: sha256
Hash value: 225d6bf0712f850648223365ba06a73ba5f6315fb8a9580f23ab48ece795f91e
Image 4 (optee)
Description: OP-TEE
Created: Sun Jun 16 19:23:11 2024
Type: Firmware
Compression: uncompressed
Data Size: 465304 Bytes = 454.40 KiB = 0.44 MiB
Architecture: AArch64
Load Address: 0x08400000
Hash algo: sha256
Hash value: 66e30bf9e879405a49797aaa6c08ca1c41aa325443e910af42e3df309e65909b
Image 5 (fdt)
Description: U-Boot dtb
Created: Sun Jun 16 19:23:11 2024
Type: Flat Device Tree
Compression: uncompressed
Data Size: 8141 Bytes = 7.95 KiB = 0.01 MiB
Architecture: AArch64
Hash algo: sha256
Hash value: 8ecccd16d2f12c4f5639c386e51f206eb679638495283d9297497ddfb0aae01a
Default Configuration: 'conf'
Configuration 0 (conf)
Description: rk3588-evb
Kernel: unavailable
Firmware: atf-1
FDT: fdt
Loadables: uboot
atf-2
atf-3
optee
********boot_merger ver 1.31********
Info:Pack loader ok.
pack loader okay! Input: /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/rkbin/RKBOOT/RK3588MINIALL.ini
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/u-boot
Image(no-signed, version=0): uboot.img (FIT with uboot, trust...) is ready
Image(no-signed): rk3588_spl_loader_v1.13.112.bin (with spl, ddr...) is ready
pack uboot.img okay! Input: /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/rkbin/RKTRUST/RK3588TRUST.ini
Platform RK3588 is build OK, with new .config(make rk3588_defconfig -j12)
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu-
Sun Jun 16 19:23:11 CST 2024
+ cd ..
Running 70-loader.sh - build_uboot succeeded.编译生成uboot.img、MiniLoaderAll.bin，同时更新rockdev目录下uboot.img、MiniLoaderAll.bin；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll u-boot/uboot.img
-rw-r--r-- 1 root root 4194304 6月 16 19:23 u-boot/uboot.img
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll u-boot/rk3588_spl_loader_v1.13.112.bin
-rw-r--r-- 1 root root 471488 6月 16 19:23 u-boot/rk3588_spl_loader_v1.13.112.bin
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll rockdev/
lrwxrwxrwx 1 root root 21 6月 11 22:52 boot.img -> ../../kernel/boot.img
lrwxrwxrwx 1 root root 44 6月 16 19:23 MiniLoaderAll.bin -> ../../u-boot/rk3588_spl_loader_v1.13.112.bin
-rw-r--r-- 1 root root 49152 6月 11 23:00 misc.img
-rw-r--r-- 1 root root 17457152 6月 11 23:00 oem.img
lrwxrwxrwx 1 root root 49 6月 11 23:00 parameter.txt -> ../../device/rockchip/.chips/rk3588/parameter.txt
lrwxrwxrwx 1 root root 67 6月 11 23:00 recovery.img -> ../../buildroot/output/rockchip_rk3588_recovery/images/recovery.img
lrwxrwxrwx 1 root root 57 6月 11 22:59 rootfs.img -> ../../buildroot/output/rockchip_rk3588/images/rootfs.ext2
lrwxrwxrwx 1 root root 22 6月 16 19:23 uboot.img -> ../../u-boot/uboot.img
lrwxrwxrwx 1 root root 26 6月 11 23:00 update.img -> ../update/Image/update.img
-rw-r--r-- 1 root root 4472832 6月 11 23:00 userdata.img3.5.2 Kernel编译
编译命令如下：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp#./build.sh kernel输出详情如下：
点击查看代码
Log saved at /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/sessions/2024-06-16_19-27-50
==========================================
Final configs
==========================================
RK_BOOT_FIT_ITS=boot.its
RK_BOOT_IMG=boot.img
RK_BUILDROOT_CFG=rockchip_rk3588
RK_CHIP=rk3588
RK_CHIP_FAMILY=rk3588
RK_DEBIAN_ARCH=arm64
RK_DEBIAN_ARM64=y
......
==========================================
Start building kernel
==========================================
+ make -C /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/kernel/ -j7 CROSS_COMPILE=/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu- ARCH=arm64 rockchip_linux_defconfig rk3588_linux.config
make: Entering directory '/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/kernel'
#
# No change to .config
#
Using .config as base
Merging ./arch/arm64/configs/rk3588_linux.config
#
# merged configuration written to .config (needs make)
#
#
# configuration written to .config
#
make: Leaving directory '/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/kernel'
+ make -C /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/kernel/ -j7 CROSS_COMPILE=/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu- ARCH=arm64 rk3588-armsom-sige7.img
......
Image: zboot.img (with Image.lz4 resource.img) is ready
make: Leaving directory '/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/kernel'
+ /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/common/scripts/mk-fitimage.sh kernel/boot.img boot.its kernel/arch/arm64/boot/Image
FIT description: U-Boot FIT source file for arm
Created: Sun Jun 16 19:28:28 2024
Image 0 (fdt)
Description: unavailable
Created: Sun Jun 16 19:28:28 2024
Type: Flat Device Tree
Compression: uncompressed
Data Size: 276878 Bytes = 270.39 KiB = 0.26 MiB
Architecture: AArch64
Load Address: 0xffffff00
Hash algo: sha256
Hash value: 2e1efecb7de8f6d6f6dc99aceac3316169528dbe2343075acbc97c676863a54a
Image 1 (kernel)
Description: unavailable
Created: Sun Jun 16 19:28:28 2024
Type: Kernel Image
Compression: uncompressed
Data Size: 35650048 Bytes = 34814.50 KiB = 34.00 MiB
Architecture: AArch64
OS: Linux
Load Address: 0xffffff01
Entry Point: 0xffffff01
Hash algo: sha256
Hash value: 75156ece8874de3e407e006dc1cc4b471fccbb3d192a7f57b9aeb85419d34445
Image 2 (resource)
Description: unavailable
Created: Sun Jun 16 19:28:28 2024
Type: Multi-File Image
Compression: uncompressed
Data Size: 1692160 Bytes = 1652.50 KiB = 1.61 MiB
Hash algo: sha256
Hash value: 35f3f91ac5fc2bbcfc9e9922ead7f9df34d9a5b31be32cb144a9366852fc514c
Default Configuration: 'conf'
Configuration 0 (conf)
Description: unavailable
Kernel: kernel
FDT: fdt
Not Found io-domains in kernel/arch/arm64/boot/dts/rockchip/rk3588-armsom-sige7.dts
Running 10-kernel.sh - build_kernel succeeded.编译生成boot.img，同时更新rockdev目录下boot.img；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll kernel/boot.img
-rw-r--r-- 1 root root 37622272 6月 16 19:28 kernel/boot.img
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll rockdev/
lrwxrwxrwx 1 root root 21 6月 16 19:28 boot.img -> ../../kernel/boot.img
lrwxrwxrwx 1 root root 44 6月 16 19:23 MiniLoaderAll.bin -> ../../u-boot/rk3588_spl_loader_v1.13.112.bin
-rw-r--r-- 1 root root 49152 6月 11 23:00 misc.img
-rw-r--r-- 1 root root 17457152 6月 11 23:00 oem.img
lrwxrwxrwx 1 root root 49 6月 11 23:00 parameter.txt -> ../../device/rockchip/.chips/rk3588/parameter.txt
lrwxrwxrwx 1 root root 67 6月 11 23:00 recovery.img -> ../../buildroot/output/rockchip_rk3588_recovery/images/recovery.img
lrwxrwxrwx 1 root root 57 6月 11 22:59 rootfs.img -> ../../buildroot/output/rockchip_rk3588/images/rootfs.ext2
lrwxrwxrwx 1 root root 22 6月 16 19:23 uboot.img -> ../../u-boot/uboot.img
lrwxrwxrwx 1 root root 26 6月 11 23:00 update.img -> ../update/Image/update.img
-rw-r--r-- 1 root root 4472832 6月 11 23:00 userdata.img3.5.3 Recovery编译
编译命令如下：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp#./build.sh recovery输出详情如下：
点击查看代码
Log saved at /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/sessions/2024-06-16_19-45-21
==========================================
Final configs
==========================================
RK_BOOT_FIT_ITS=boot.its
RK_BOOT_IMG=boot.img
RK_BUILDROOT_CFG=rockchip_rk3588
RK_CHIP=rk3588
RK_CHIP_FAMILY=rk3588
RK_DEBIAN_ARCH=arm64
RK_DEBIAN_ARM64=y
......
RK_YOCTO_USBMOUNT=y
==========================================
Start building recovery(buildroot)
==========================================
make: Entering directory '/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot'
GEN /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588_recovery/Makefile
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/build/parse_defconfig.sh /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/configs/rockchip_rk3588_recovery_defconfig /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588_recovery/.config.in
Parsing defconfig: /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/configs/rockchip_rk3588_recovery_defconfig
Using configs/rockchip/base/kernel.config as base
Merging configs/rockchip/fs/e2fs.config
Merging configs/rockchip/base/common.config
Merging configs/rockchip/base/base.config
Merging configs/rockchip/base/kernel.config
Merging configs/rockchip/fs/e2fs.config
Merging configs/rockchip/base/common.config
Merging configs/rockchip/fs/vfat.config
Merging configs/rockchip/base/recovery.config
Merging configs/rockchip/chips/rk3588.config
Value of BR2_ROOTFS_OVERLAY is redefined by configs/rockchip/chips/rk3588.config:
Previous value: BR2_ROOTFS_OVERLAY="board/rockchip/common/base"
Modify value: BR2_ROOTFS_OVERLAY+="board/rockchip/rk3588/fs-overlay/"
New value: BR2_ROOTFS_OVERLAY="board/rockchip/common/base board/rockchip/rk3588/fs-overlay/"
Merging configs/rockchip/chips/rk3588_aarch64.config
Merging /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/configs/rockchip_rk3588_recovery_defconfig
#
# merged configuration written to /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588_recovery/.config.in (needs make)
#
BR2_DEFCONFIG='' KCONFIG_AUTOCONFIG=/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588_recovery/build/buildroot-config/auto.conf KCONFIG_AUTOHEADER=/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588_recovery/build/buildroot-config/autoconf.h KCONFIG_TRISTATE=/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588_recovery/build/buildroot-config/tristate.config BR2_CONFIG=/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588_recovery/.config HOST_GCC_VERSION="9" BASE_DIR=/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588_recovery SKIP_LEGACY= CUSTOM_KERNEL_VERSION="5.10" BR2_DEFCONFIG=/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/configs/rockchip_rk3588_recovery_defconfig /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588_recovery/build/buildroot-config/conf --defconfig=/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588_recovery/.config.in Config.in
#
# configuration written to /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588_recovery/.config
#
make: Leaving directory '/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot'
3c3
< # Buildroot -g28f720bc5-dirty Configuration
---
> # Buildroot -g2d3236bd2-dirty Configuration
Buildroot config changed!
You might need to clean it before building:
rm -rf /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/buildroot/output/rockchip_rk3588_recovery
2024-06-16T19:45:36 >>> Finalizing host directory
2024-06-16T19:45:36 >>> Finalizing target directory
2024-06-16T19:45:38 >>> Sanitizing RPATH in target tree
2024-06-16T19:45:39 >>> Sanity check in overlay board/rockchip/common/base
2024-06-16T19:45:39 >>> Sanity check in overlay board/rockchip/rk3588/fs-overlay/
2024-06-16T19:45:39 >>> Copying overlay board/rockchip/common/base
2024-06-16T19:45:39 >>> Copying overlay board/rockchip/rk3588/fs-overlay/
2024-06-16T19:45:40 >>> Executing post-build script board/rockchip/common/post-build.sh
2024-06-16T19:45:41 >>> Generating root filesystems common tables
2024-06-16T19:45:41 >>> Generating filesystem image rootfs.cpio
2024-06-16T19:45:44 >>> Generating filesystem image rootfs.ext2
2024-06-16T19:45:45 >>> Generating filesystem image rootfs.squashfs
2024-06-16T19:45:45 >>> Generating filesystem image rootfs.tar
Done in 20s
Log saved on /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/sessions/2024-06-16_19-45-21/br-rockchip_rk3588_recovery_2024-06-16_19-45-26.log
Generated images:
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/rootfs.cpio
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/rootfs.cpio.gz
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/rootfs.ext2
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/rootfs.ext4
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/rootfs.squashfs
/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/rootfs.tar
you take 0:23.86 to build recovery(buildroot)
Packing /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/rootfs.cpio.gz to /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/recovery/recovery.img
FIT description: U-Boot FIT source file for arm
Created: Sun Jun 16 19:45:46 2024
Image 0 (fdt)
Description: unavailable
Created: Sun Jun 16 19:45:46 2024
Type: Flat Device Tree
Compression: uncompressed
Data Size: 276878 Bytes = 270.39 KiB = 0.26 MiB
Architecture: AArch64
Load Address: 0xffffff00
Hash algo: sha256
Hash value: 2e1efecb7de8f6d6f6dc99aceac3316169528dbe2343075acbc97c676863a54a
Image 1 (kernel)
Description: unavailable
Created: Sun Jun 16 19:45:46 2024
Type: Kernel Image
Compression: uncompressed
Data Size: 35650048 Bytes = 34814.50 KiB = 34.00 MiB
Architecture: AArch64
OS: Linux
Load Address: 0xffffff01
Entry Point: 0xffffff01
Hash algo: sha256
Hash value: 75156ece8874de3e407e006dc1cc4b471fccbb3d192a7f57b9aeb85419d34445
Image 2 (ramdisk)
Description: unavailable
Created: Sun Jun 16 19:45:46 2024
Type: RAMDisk Image
Compression: uncompressed
Data Size: 6673191 Bytes = 6516.79 KiB = 6.36 MiB
Architecture: AArch64
OS: Linux
Load Address: 0xffffff02
Entry Point: unavailable
Hash algo: sha256
Hash value: efbbfccf3445edd16363ee75449e13cabf19c48910354004f788878afb628d25
Image 3 (resource)
Description: unavailable
Created: Sun Jun 16 19:45:46 2024
Type: Multi-File Image
Compression: uncompressed
Data Size: 1692160 Bytes = 1652.50 KiB = 1.61 MiB
Hash algo: sha256
Hash value: 35f3f91ac5fc2bbcfc9e9922ead7f9df34d9a5b31be32cb144a9366852fc514c
Default Configuration: 'conf'
Configuration 0 (conf)
Description: unavailable
Kernel: kernel
Init Ramdisk: ramdisk
FDT: fdt
you take 0:00.60 to pack recovery image
Running 40-recovery.sh - build_recovery succeeded.编译后在buildroot/output/rockchip_rk3588_recovery/images/生成recovery.img，同时更新rockdev目录下recovery.img；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll buildroot/output/rockchip_rk3588_recovery/images/
-rw-r--r-- 1 root root 44295680 6月 16 19:45 recovery.img
-rw-r--r-- 1 root root 15763968 6月 16 19:45 rootfs.cpio
-rw-r--r-- 1 root root 6673191 6月 16 19:45 rootfs.cpio.gz
-rw-r--r-- 1 root root 43187200 6月 16 19:45 rootfs.ext2
lrwxrwxrwx 1 root root 11 6月 16 19:45 rootfs.ext4 -> rootfs.ext2
-rw-r--r-- 1 root root 6635520 6月 16 19:45 rootfs.squashfs
-rw-r--r-- 1 root root 16844800 6月 16 19:45 rootfs.tar
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll rockdev/
lrwxrwxrwx 1 root root 21 6月 16 19:28 boot.img -> ../../kernel/boot.img
lrwxrwxrwx 1 root root 44 6月 16 19:23 MiniLoaderAll.bin -> ../../u-boot/rk3588_spl_loader_v1.13.112.bin
-rw-r--r-- 1 root root 49152 6月 11 23:00 misc.img
-rw-r--r-- 1 root root 17457152 6月 11 23:00 oem.img
lrwxrwxrwx 1 root root 49 6月 11 23:00 parameter.txt -> ../../device/rockchip/.chips/rk3588/parameter.txt
lrwxrwxrwx 1 root root 67 6月 16 19:45 recovery.img -> ../../buildroot/output/rockchip_rk3588_recovery/images/recovery.img
lrwxrwxrwx 1 root root 57 6月 11 22:59 rootfs.img -> ../../buildroot/output/rockchip_rk3588/images/rootfs.ext2
lrwxrwxrwx 1 root root 22 6月 16 19:23 uboot.img -> ../../u-boot/uboot.img
lrwxrwxrwx 1 root root 26 6月 11 23:00 update.img -> ../update/Image/update.img
-rw-r--r-- 1 root root 4472832 6月 11 23:00 userdata.img注意：recovery.img是由kernel+dtb+ramdisk组成的根文件系统，主要用于升级操作。因此所以每次kernel更改，recovery.img是需要重新打包生成。
recovery重新打包的方法如下：
source buildroot/envsetup.sh
cd buildroot
make recovery-reconfigure
cd -
./build.sh recovery注意：recovery是非必需的功能。
3.5.4 Buildroot编译
执行以下命令自动完成Buildroot的编译及打包：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# ./build.sh buildroot编译后在buildroot/output/rockchip_rk3588/images下生成不同格式的镜像, 默认使用rootfs.ext4格式。
由于全自动编译默认系统就是Buildroot，这里我就不重新编译了；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll buildroot/output/rockchip_rk3588/images/
-rw-r--r-- 1 root root 615713280 6月 11 22:58 rootfs.cpio
-rw-r--r-- 1 root root 273882955 6月 11 22:59 rootfs.cpio.gz
-rw-r--r-- 1 root root 763363328 6月 11 22:59 rootfs.ext2
lrwxrwxrwx 1 root root 11 6月 11 22:59 rootfs.ext4 -> rootfs.ext2
-rw-r--r-- 1 root root 275013632 6月 11 22:59 rootfs.squashfs
-rw-r--r-- 1 root root 624517120 6月 11 22:59 rootfs.tar其中：rockdev/目录下的rootfs.img指向了buildroot/output/rockchip_rk3588/images/rootfs.ext2。
3.5.5 Debian编译
需要预先安装以下相关依赖包:
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# cd debian
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# sudo apt install binfmt-support qemu-user-static live-build
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# sudo dpkg -i ubuntu-build-service/packages/*
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# sudo apt install -f执行以下命令自动完成Debian的编译及打包：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# ./build.sh debian输出详情如下：
点击查看代码
Log saved at /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/sessions/2024-06-16_19-48-51
WARN: /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/defconfig not exists
Pick a defconfig:
1. rockchip_defconfig
2. rockchip_rk3588_evb1_lp4_v10_defconfig
3. rockchip_rk3588_evb7_v11_defconfig
4. rockchip_rk3588_sige7_defconfig
5. rockchip_rk3588s_evb1_lp4x_v10_defconfig
Which would you like? [1]: 4
Switching to defconfig: /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/.chip/rockchip_rk3588_sige7_defconfig
make: Entering directory '/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/common'
......
make: Leaving directory '/work/sambashare/rk3588/armsom/armsom-rk3588-bsp/device/rockchip/common'
Using rootfs system(debian) from cmdline
==========================================
Final configs
==========================================
RK_BOOT_FIT_ITS=boot.its
RK_BOOT_IMG=boot.img
RK_BUILDROOT_CFG=rockchip_rk3588
RK_CHIP=rk3588
RK_CHIP_FAMILY=rk3588
RK_DEBIAN_ARCH=arm64
RK_DEBIAN_ARM64=y
RK_DEBIAN_VERSION=bullseye
......
==========================================
Start building rootfs(debian)
==========================================
==========================================
Start building bullseye(arm64)
==========================================
Staring Download......
sudo lb clean --purge
[2024-06-16 19:49:07] lb clean --purge
P: Cleaning chroot
rm -f linaro-bullseye-alip-*
rm -rf config
I: create configuration
.......
Fixing up owner for /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/debian/binary...
Fixing up /home/armsom for uid=1000(armsom)...
Running build.sh - post-rootfs succeeded.
mke2fs 1.46.5 (30-Dec-2021)
Creating regular file linaro-rootfs.img
Creating filesystem with 808960 4k blocks and 202400 inodes
Filesystem UUID: c93a2c93-553d-44d8-aa57-dddb8c8a33e8
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Copying files into the device: done
Writing superblocks and filesystem accounting information: done
Rootfs Image: linaro-rootfs.img
Running 30-rootfs.sh - build_debian /work/sambashare/rk3588/armsom/armsom-rk3588-bsp/output/rootfs succeeded.
Running 30-rootfs.sh - build_rootfs debian succeeded.该次编译会重新编译内核和根文件系统。耐心等待1个小时，与buildroot编译类似，编译完成我们在rockdev 目录下可以看到各个分区镜像；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll rockdev/
lrwxrwxrwx 1 root root 21 6月 16 19:28 boot.img -> ../../kernel/boot.img
lrwxrwxrwx 1 root root 44 6月 16 19:35 MiniLoaderAll.bin -> ../../u-boot/rk3588_spl_loader_v1.13.112.bin
-rw-r--r-- 1 root root 49152 6月 11 23:00 misc.img
-rw-r--r-- 1 root root 17457152 6月 11 23:00 oem.img
lrwxrwxrwx 1 root root 49 6月 11 23:00 parameter.txt -> ../../device/rockchip/.chips/rk3588/parameter.txt
lrwxrwxrwx 1 root root 67 6月 16 19:45 recovery.img -> ../../buildroot/output/rockchip_rk3588_recovery/images/recovery.img
lrwxrwxrwx 1 root root 30 6月 16 19:59 rootfs.img -> ../../debian/linaro-rootfs.img
lrwxrwxrwx 1 root root 22 6月 16 19:35 uboot.img -> ../../u-boot/uboot.img
lrwxrwxrwx 1 root root 26 6月 11 23:00 update.img -> ../update/Image/update.img
-rw-r--r-- 1 root root 4472832 6月 11 23:00 userdata.img
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll debian/
drwxr-xr-x 22 root root 4096 6月 9 12:58 binary/
-rw-rw-rw- 1 root root 579714760 6月 16 13:24 linaro-bullseye-alip-20240616-1.tar.gz
lrwxrwxrwx 1 root root 38 6月 16 13:26 linaro-bullseye-arm64.tar.gz -> linaro-bullseye-alip-20240616-1.tar.gz
-rw-r--r-- 1 root root 3362783232 6月 16 19:59 linaro-rootfs.img
-rwxr-xr-x 1 root root 955 6月 9 12:58 mk-base-debian.sh*
-rwxr-xr-x 1 root root 526 6月 9 12:58 mk-image.sh*
-rwxr-xr-x 1 root root 4554 6月 9 12:58 mk-iso-debian.sh*
-rwxr-xr-x 1 root root 7358 6月 11 22:36 mk-rootfs-bullseye.sh*
-rwxr-xr-x 1 root root 87 6月 9 12:58 mk-rootfs.sh*
drwxr-xr-x 4 root root 4096 6月 9 12:58 overlay/
drwxr-xr-x 5 root root 4096 6月 9 12:58 overlay-debug/
drwxr-xr-x 3 root root 4096 6月 9 12:58 overlay-firmware/
drwxr-xr-x 4 root root 4096 6月 9 12:58 packages/
drwxr-xr-x 7 root root 4096 6月 9 12:58 packages-patches/
-rwxr-xr-x 1 root root 2483 6月 9 12:58 post-build.sh*
-rw-r--r-- 1 root root 2373 6月 9 12:58 readme.md
drwxr-xr-x 4 root root 4096 6月 9 12:58 scripts/
drwxr-xr-x 11 root root 4096 6月 9 12:58 ubuntu-build-service/可以看到该次编译重新生成了boot.img、rootfs.img。此外由于我们执行了./build.sh debian，此时output/.config中默认系统已经设置为了debian。
编译完成会在debian目录下生成：linaro-buster-alip-xxxxx-1.tar.gz(xxxxx 表示生成时间戳)。
因此我们将debian根文件系统移动到/work/tftproot文件；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ mv debian/linaro-rootfs.img /work/tftpboot/3.5.6 Yocto编译
执行以下命令自动完成Yocto的编译及打包：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp# ./build.sh yocto编译后在yocto目录build/lastest下生成rootfs.img。
3.5.7 打包分区镜像
执行以下命令更新output/firmware/下各个分区镜像；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ./build.sh firmware查看目录：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll rockdev/
lrwxrwxrwx 1 root root 21 6月 16 19:28 boot.img -> ../../kernel/boot.img
lrwxrwxrwx 1 root root 44 6月 16 19:35 MiniLoaderAll.bin -> ../../u-boot/rk3588_spl_loader_v1.13.112.bin
-rw-r--r-- 1 root root 49152 6月 16 21:13 misc.img
-rw-r--r-- 1 root root 21651456 6月 16 21:13 oem.img
lrwxrwxrwx 1 root root 49 6月 16 21:13 parameter.txt -> ../../device/rockchip/.chips/rk3588/parameter.txt
lrwxrwxrwx 1 root root 67 6月 16 19:45 recovery.img -> ../../buildroot/output/rockchip_rk3588_recovery/images/recovery.img
lrwxrwxrwx 1 root root 30 6月 16 19:59 rootfs.img -> ../../debian/linaro-rootfs.img
lrwxrwxrwx 1 root root 22 6月 16 19:35 uboot.img -> ../../u-boot/uboot.img
lrwxrwxrwx 1 root root 26 6月 11 23:00 update.img -> ../update/Image/update.img
-rw-r--r-- 1 root root 4472832 6月 16 21:13 userdata.img可以看到该次编译重新生成了： parameter.txt、 misc.img、 oem.img、 userdata.img。
3.5.8 打包统一固件
执行如下命令重新生成统一固件；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ./build.sh updateimg查看目录：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll rockdev/
lrwxrwxrwx 1 root root 21 6月 16 19:28 boot.img -> ../../kernel/boot.img
lrwxrwxrwx 1 root root 44 6月 16 19:35 MiniLoaderAll.bin -> ../../u-boot/rk3588_spl_loader_v1.13.112.bin
-rw-r--r-- 1 root root 49152 6月 16 21:13 misc.img
-rw-r--r-- 1 root root 21651456 6月 16 21:13 oem.img
lrwxrwxrwx 1 root root 49 6月 16 21:13 parameter.txt -> ../../device/rockchip/.chips/rk3588/parameter.txt
lrwxrwxrwx 1 root root 67 6月 16 19:45 recovery.img -> ../../buildroot/output/rockchip_rk3588_recovery/images/recovery.img
lrwxrwxrwx 1 root root 30 6月 16 19:59 rootfs.img -> ../../debian/linaro-rootfs.img
lrwxrwxrwx 1 root root 22 6月 16 19:35 uboot.img -> ../../u-boot/uboot.img
lrwxrwxrwx 1 root root 26 6月 16 21:20 update.img -> ../update/Image/update.img
-rw-r--r-- 1 root root 4472832 6月 16 21:13 userdata.img
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ls -l output/update/
drwxr-xr-x 2 root root 4096 6月 16 21:19 Image
lrwxrwxrwx 1 root root 18 6月 16 21:20 package-file -> Image/package-file
lrwxrwxrwx 1 root root 16 6月 16 21:20 update.img -> Image/update.img
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll output/update/Image/
lrwxrwxrwx 1 root root 24 6月 16 21:18 boot.img -> ../../../kernel/boot.img
lrwxrwxrwx 1 root root 47 6月 16 21:18 MiniLoaderAll.bin -> ../../../u-boot/rk3588_spl_loader_v1.13.112.bin
lrwxrwxrwx 1 root root 23 6月 16 21:18 misc.img -> ../../firmware/misc.img
lrwxrwxrwx 1 root root 22 6月 16 21:18 oem.img -> ../../firmware/oem.img
-rw-r--r-- 1 root root 225 6月 16 21:18 package-file
lrwxrwxrwx 1 root root 52 6月 16 21:18 parameter.txt -> ../../../device/rockchip/.chips/rk3588/parameter.txt
lrwxrwxrwx 1 root root 70 6月 16 21:18 recovery.img -> ../../../buildroot/output/rockchip_rk3588_recovery/images/recovery.img
lrwxrwxrwx 1 root root 33 6月 16 21:18 rootfs.img -> ../../../debian/linaro-rootfs.img
lrwxrwxrwx 1 root root 25 6月 16 21:18 uboot.img -> ../../../u-boot/uboot.img
-rw-r--r-- 1 root root 3480216138 6月 16 21:20 update.img
-rw-r--r-- 1 root root 3479744516 6月 16 21:19 update.raw.img
lrwxrwxrwx 1 root root 27 6月 16 21:18 userdata.img -> ../../firmware/userdata.img可以看到该次编译重新生成了： update.img。
四、SDK固件升级
RK3588有两种工作模式，
| 工作模式 | Normal 模式 | 升级模式 |
|---|---|---|
| 启动介质 | eMMC 接口/SDMMC 接口 | |
| 描述 | Normal 模式就是正常的启动过程， 各个组件依次加载，正常进入系统。 | 目前支持3种升级模式，各有优缺点： 1. Maskrom升级模式 2. Loader 升级模式 3. SD 升级模式 |
一般情况下，开机直接进入Normal模式正常启动系统。
其中升级模式中，不同升级模式之间的对比：
| 升级模式 | Maskrom升级模式 | Loader 升级模式 | SD 升级模式 |
|---|---|---|---|
| 简单描述 | 1. 使用USB线将主板连接到电脑上； 2. 硬件操作使板子进入升级模式； 3. 在PC上使用USB升级单板固件。 | 1. 使用USB线将主板连接到电脑上； 2. 软件或按键操作使板子进入升级模式； 3. 在PC上使用USB升级单板固件。 | 1. 通过升级卡制作工具，将MicroSD卡制作为升级卡； 2. 将升级卡插入主板，上电开机，机器自动执行升级。 |
| 连接方式 | USB | USB | TF卡(少数为SD卡槽) |
| 升级工具 Windows PC Linux PC | Windows 上升级固件 Linux 上升级固件 | Windows 上升级固件Linux 上升级固件 | Windows 上制作升级卡 不支持 |
| 进入方法 | 需要硬件操作 | 按键或软件进入(在串口或 ADB 命令行模式下，输入 reboot loader 命令) | 上电直接进入 |
| 使用条件 | 硬件操作进入 | 能正常使用uboot | 无 |
| 使用场景推荐 | 1. 当板子无法正常启动时候； 2. 在切换烧写Linux和Android固件的情况下。 | 1. 有完整uboot或能正常进入系统； 2. 需要单独烧写分区(uboot或boot分区等)。 | 1. 工人操作方便，适合产品批量生产时候； 2. 产品定型后升级，方便最终客户操作。 |
| 优点 | 1. 最基本的烧写方式； 2. 非固件和硬件问题，一般都能成功烧写； 3. 不需要uboot支持，拯救变砖的单板； 4. 支持跨系统升级(Linux和安卓等)。 | 1. 烧写效果Maskrom升级模式差不多； 2. 能单独烧写分区； 3. 进入Loader模式方便。 | 1. 操作方便，只需插卡启动； 2.集合了Maskrom升级模式的优点。 |
| 缺点 | 1. 进入方式麻烦，不适难拆除外壳的产品； 2. 烧写分区表麻烦，较难单独烧写分区； 3. 需要完全擦除设备再烧写。 | 1. 需要完整的Loader(通常指uboot)； 2. 跨系统升级需要完全擦除设备再烧写。 | 1. 需要合成完整固件。 |
4.1 Windows刷机
Winodws刷机我们有两种方式：
- 采用
SD升级模式： RKDevTool烧写固件到eMMC；
4.1.1 SD卡升级模式
这里我们就采用SD升级模式来将我们全自动编译的镜像文件烧录到eMMC，具体可以参考《若固件大于4G的SD升级卡制作教程》。
(1) 准备工作：
- 烧写工具下载：将
tools/windows目录下的SDDiskTool_v1.76.zip工具上传到Windows系统，并进行解压； - 下载需要升级的统一固件：将
buildroot系统统一镜像rockdev/update.img上传到Windows系统； - 将
MicroSD通过读卡器插入PC； - 将开发板连接到
HDMI显示屏；
(2) 以管理员身份运行SD_Firmware_Tool.exe，勾选固件升级框，选择正确的可移动磁盘设备和升级固件；
(3) 点击开始创建之后，等待创建结束；烧录完成后，可以查看MicroSD的内容：
(4) 取出MicroSD卡，插入开发板的MicroSD卡插槽，对主板上电开机，主板自动开始升级。
注意：由于我们无法可视化查看升级进度，因此此处需要耐心等待3分钟。
(5) 升级完成后，取出MicroSD卡，开发板自动重启，显示屏显示如下；
关于buildroot系统简单测试可以参考后续《Rockchip RK3588 - Rockchip Linux SDK Buildroot文件系统构建》。
4.1.2 RKDevTool烧写固件到eMMC
SDK提供Windows烧写工具(RKDevTool工具版本需要V3.15或以上)，工具位于工程根目录：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll tools/windows/
-rwxr-xr-x 1 root root 7080412 6月 9 12:59 boot_merger_v1.32.zip*
-rwxr-xr-x 1 root root 27440555 6月 9 12:59 DDR_UserTool_v1.41.zip*
-rwxr-xr-x 1 root root 9814896 6月 9 12:59 DriverAssitant_v5.12.zip*
-rwxr-xr-x 1 root root 731921 6月 9 12:59 EfuseTool_v1.42.zip*
-rw-r--r-- 1 root root 1793777 6月 9 12:59 FactoryTool_v1.81.zip
-rwxr-xr-x 1 root root 19443215 6月 9 12:59 ParameterTool_v1.2.zip*
-rw-r--r-- 1 root root 50668825 6月 9 12:59 pin_debug_tool_v1.12_20230310_win.zip
-rw-r--r-- 1 root root 380719 6月 9 12:59 programmer_image_tool_v1.26.zip
-rwxr-xr-x 1 root root 59731296 6月 9 12:59 rk_ddrbin_tool_V1.01.7z*
drwxr-xr-x 2 root root 4096 6月 9 12:59 RKDevInfoWriteTool/
-rwxr-xr-x 1 root root 3140313 6月 9 12:59 RKDevInfoWriteTool-1.3.0.7z*
drwxr-xr-x 4 root root 4096 6月 9 12:59 RKDevTool/
-rw-r--r-- 1 root root 2433639 6月 9 12:59 RKDevTool_Release_v3.19.zip
-rwxr-xr-x 1 root root 4181454 6月 9 12:59 RKImageMaker_20230109.zip*
-rwxr-xr-x 1 root root 4164049 6月 9 12:59 RKPCBATool_V1.0.9.zip*
-rwxr-xr-x 1 root root 26104417 6月 9 12:59 rk_sign_tool_v1.42.zip*
-rwxr-xr-x 1 root root 4334042 6月 9 12:59 Rockchip_HdcpKey_Writer_V1.0.5.7z*
drwxr-xr-x 2 root root 4096 6月 9 12:59 Rockchip_USB_SQ_Tool/
-rwxr-xr-x 1 root root 17253972 6月 9 12:59 Rockchip_USB_SQ_Tool_V1.5.7z*
-rw-r--r-- 1 root root 331802 6月 9 12:59 SDDiskTool_v1.76.zip
-rwxr-xr-x 1 root root 3011296 6月 9 12:59 SecureBootTool_v2.2.zip*
-rwxr-xr-x 1 root root 1089 6月 9 12:59 ToolsRelease.txt*
-rw-r--r-- 1 root root 676148 6月 9 12:59 upgrade_tool_v2.23.zip该方式我们在前面的文章中已经介绍了，具体可以参考《Rockchip RK3588 - NanoPC-T6开发板介绍》第2.3节。
4.2 Linux刷机
Linux下的烧写工具位于tools/linux目录下(Linux_Upgrade_Tool工具版本需要V2.17或以上)，请确认你
的板子连接到Maskrom/Loader rockusb；
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll tools/linux/
drwxr-xr-x 2 root root 4096 6月 9 12:59 boot_merger/
drwxr-xr-x 2 root root 4096 6月 9 12:59 Firmware_Merger/
drwxr-xr-x 2 root root 4096 6月 9 12:59 Linux_DDR_Bandwidth_Tool/
drwxr-xr-x 2 root root 4096 6月 9 12:59 Linux_Diff_Firmware/
drwxr-xr-x 3 root root 4096 6月 9 12:59 Linux_Pack_Firmware/
drwxr-xr-x 2 root root 4096 6月 9 12:59 Linux_SecureBoot/
drwxr-xr-x 4 root root 4096 6月 9 12:59 Linux_SecurityAVB/
-rw-r--r-- 1 root root 5393885 6月 9 12:59 Linux_SecurityDM_v1_01.tar.gz
drwxr-xr-x 3 root root 4096 6月 9 12:59 Linux_Upgrade_Tool/
drwxr-xr-x 2 root root 4096 6月 9 12:59 PinDebug/
drwxr-xr-x 2 root root 4096 6月 9 12:59 programming_image_tool/
-rw-r--r-- 1 root root 81801567 6月 9 12:59 rk_ddrbin_tool_V1.01.7z
drwxr-xr-x 3 root root 4096 6月 9 12:59 rk_sign_tool/
-rwxr-xr-x 1 root root 22457713 6月 9 12:59 rk_sign_tool_v1.42_linux.zip*
-rwxr-xr-x 1 root root 794 6月 9 12:59 ToolsRelease.txt*比如buildroot系统编译生成的固件在rockdev目录下：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ll rockdev/
lrwxrwxrwx 1 root root 21 6月 11 22:52 boot.img -> ../../kernel/boot.img
lrwxrwxrwx 1 root root 44 6月 11 23:00 MiniLoaderAll.bin -> ../../u-boot/rk3588_spl_loader_v1.13.112.bin
-rw-r--r-- 1 root root 49152 6月 11 23:00 misc.img
-rw-r--r-- 1 root root 17457152 6月 11 23:00 oem.img
lrwxrwxrwx 1 root root 49 6月 11 23:00 parameter.txt -> ../../device/rockchip/.chips/rk3588/parameter.txt
lrwxrwxrwx 1 root root 67 6月 11 23:00 recovery.img -> ../../buildroot/output/rockchip_rk3588_recovery/images/recovery.img
lrwxrwxrwx 1 root root 57 6月 11 22:59 rootfs.img -> ../../buildroot/output/rockchip_rk3588/images/rootfs.ext2
lrwxrwxrwx 1 root root 22 6月 11 23:00 uboot.img -> ../../u-boot/uboot.img
lrwxrwxrwx 1 root root 26 6月 11 23:00 update.img -> ../update/Image/update.img
-rw-r--r-- 1 root root 4472832 6月 11 23:00 userdata.img升级命令如下：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ ./rkflash.sh这里rkflash.sh脚本实际上就是使用upgrade_tool命令烧写各个分区，比如核心脚本：
if [ ! -n "$1" ];then
echo "flash all images as default"
FLASH_TYPE=all
else
FLASH_TYPE="$1"
fi
if [ $FLASH_TYPE = all ]
then
$UPGRADETOOL ul -noreset $LOADER
$UPGRADETOOL di -p $PARAMETER
$UPGRADETOOL di -uboot $UBOOT
$UPGRADETOOL di -trust $TRUST
$UPGRADETOOL di -b $BOOT
$UPGRADETOOL di -r $RECOVERY
$UPGRADETOOL di -m $MISC
$UPGRADETOOL di -oem $OEM
$UPGRADETOOL di -userdata $USERDATA
$UPGRADETOOL di -rootfs $ROOTFS
$UPGRADETOOL rd
fi当然也可以直接使用upgrade_tool命令一一烧写各个分区镜像或者打包后完整的固件，具体操作可以参考：《Linux下烧录固件》。
4.3 系统分区介绍
parameter.txt保存着分区信息：
FIRMWARE_VER: 1.0
MACHINE_MODEL: RK3588
MACHINE_ID: 007
MANUFACTURER: RK3588
MAGIC: 0x5041524B
ATAG: 0x00200800
MACHINE: 0xffffffff
CHECK_MASK: 0x80
PWR_HLD: 0,0,A,0,1
TYPE: GPT
GROW_ALIGN: 0
CMDLINE: mtdparts=:0x00002000@0x00004000(uboot),0x00002000@0x00006000(misc),0x00020000@0x00008000(boot),0x00040000@0x00028000(recovery),0x00010000@0x00068000(backup),0x01c00000@0x00078000(rootfs),0x00040000@0x01c78000(oem),-@0x01cb8000(userdata:grow)
uuid:rootfs=614e0000-0000-4b53-8000-1d28000054a9
uuid:boot=7A3F0000-0000-446A-8000-702F00006273解析信息如下：
| Number | Start (sector) | Start (sector) End (sector) | Size | Name |
|---|---|---|---|---|
| 1 | 0x4000(16384) | 0x5FFF(24575) | 4M | uboot |
| 2 | 0x6000(24576) | 0x7FFF(32767) | 4M | misc |
| 3 | 0x8000(32768) | 0x27FFF(163839) | 64M | boot |
| 4 | 0x28000(163840) | 0x67FFF(425983) | 128M | recovery |
| 5 | 0x68000(425984) | 0x77FFF(491519) | 32M | backup |
| 6 | 0x78000(491520) | 0x1C77FFF(29851647) | 14GB | rootfs |
| 7 | 0x1C78000(29851648) | 0x01CB7FFF(30113791) | 128M | oem |
| 8 | 0x01CB8000(30113792) | - | userdata |
其中：
uboot分区：供uboot编译出来的uboot.img；misc分区：引导参数分区，供misc.img，给recovery使用；boot分区：供kernel编译出来的boot.img(kernel+dtb)；recovery分区：供recovery编译出的recovery.img(kernel+dtb+ramdisk组成的根文件系统)；backup分区：预留，暂时没有用；rootfs分区：供buildroot、debian或yocto编出来的rootfs.img；oem分区：给厂家使用，存放厂家的APP或数据。挂载在/oem目录；userdata分区：供APP临时生成文件或给最终用户使用，挂载在/userdata目录下。
4.4 dd烧录分区
我们也可以通过dd命令烧写各个分区镜像；
dd if=uboot.img of=/dev/mmcblk0p1 bs=1M
dd if=boot.img of=/dev/mmcblk0p3 bs=1M
dd if=rootfs.img of=/dev/mmcblk0p6 bs=1M
dd if=oem.img of=/dev/mmcblk0p7 bs=1M
dd if=userdata.img of=/dev/mmcblk0p8 bs=1M4.4.1 烧录userdata.img
如果要更新userdata.img，具体流程如下。
(1) 首先将userdata.img拷贝到tftp根目录下(/work/tftpboot/)：
root@ubuntu:/work/sambashare/rk3588/armsom/armsom-rk3588-bsp$ cp rockdev/userdata.img /work/tftpboot/busybox内置tftp，可以直接从ubuntu宿主机tftp服务器下载文件：
root@rk3588-buildroot:/opt# tftp -g -l userdata.img 192.168.0.200从ubuntu中的tftp根目录下(/work/tftpboot/)，下载文件userdata.img。
root@rk3588-buildroot:/opt# ls -l
drwxr-xr-x 6 root root 4096 Jun 11 14:52 unixbench
-rw-r--r-- 1 root root 4472832 Jun 16 04:51 userdata.img(2) 接着我们在/userdata目录下创建一个test.txt文件；
root@rk3588-buildroot:/opt# touch /userdata/test.txt
root@rk3588-buildroot:/opt# ls -l /userdata/
total 279
-rw-r--r-- 1 root root 87402 Jun 9 04:58 200frames_count.h264
-rw-r--r-- 1 root root 81582 Jun 9 04:58 belle-nuit-testchart-1080p.png
drwx------ 2 root root 12288 Jun 11 15:00 lost+found
-rw-r--r-- 1 root root 101760 Jun 9 04:58 piano2-CoolEdit.mp3
-rw-r--r-- 1 root root 0 Jun 16 04:31 test.txt(3) 重新烧写userdata分区：
root@rk3588-buildroot:/opt# dd if=userdata.img of=/dev/mmcblk0p8 bs=1M
4+1 records in
4+1 records out
4472832 bytes (4.5 MB, 4.3 MiB) copied, 0.00915314 s, 489 MB/s再次查看/userdata：
root@rk3588-buildroot:/opt# ls -l /userdata/
total 278
-rw-r--r-- 1 root root 87402 Jun 9 04:58 200frames_count.h264
-rw-r--r-- 1 root root 81582 Jun 9 04:58 belle-nuit-testchart-1080p.png
drwx------ 2 root root 12288 Jun 11 15:00 lost+found
-rw-r--r-- 1 root root 101760 Jun 9 04:58 piano2-CoolEdit.mp3可以看到该目录下已经不存在test.txt文件了，说明分区烧录成功了。
4.4.2 烧录debian根文件系统
从ubuntu中的tftp根目录下(/work/tftpboot/)，下载文件linaro-rootfs.img。
# 耐心等待50分钟
root@rk3588-buildroot:/opt# tftp -g -l linaro-rootfs.img 192.168.0.200
root@rk3588-buildroot:/opt# ls -l
-rw-r--r-- 1 root root 3313500160 Jun 16 15:40 linaro-rootfs.img
drwxr-xr-x 6 root root 4096 Jun 11 14:52 unixbench
-rw-r--r-- 1 root root 4472832 Jun 16 04:51 userdata.img重新烧写rootfs分区：
root@rk3588-buildroot:/opt# dd if=linaro-rootfs.img of=/dev/mmcblk0p6 bs=1M
3160+0 records in
3160+0 records out
3313500160 bytes (3.3 GB, 3.1 GiB) copied, 13.3972 s, 247 MB/s4.5 debain系统测试
4.5.1 查看系统
重启开发板，查看系统信息；
root@armsom-sige7:/# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye4.5.2 设置DNS服务器
设置DNS服务器：
root@armsom-sige7:/# sudo vi /etc/resolv.conf
# 追加
nameserver 114.114.114.114
root@armsom-sige7:/# sudo /etc/init.d/networking restart4.5.3 查看磁盘空间
这里我们可以通过df -hT查看磁盘空间信息；
root@armsom-sige7:/# df -hT
文件系统 类型 容量 已用 可用 已用% 挂载点
/dev/root ext4 3.0G 3.0G 0 100% /
devtmpfs devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs tmpfs 1.6G 2.1M 1.6G 1% /run
tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock
/dev/mmcblk0p7 ext4 121M 12M 103M 11% /oem
/dev/mmcblk0p8 ext4 43G 288K 42G 1% /userdata
tmpfs tmpfs 793M 28K 793M 1% /run/user/1000
tmpfs tmpfs 793M 28K 793M 1% /run/user/110这里我们可以看到根目录挂载在/dev/root设备节点上，文件系统格式是ext4，/dev/root其实就是/dev/mmcblk0p6，也就是eMMC设备的rootfs分区。
但是为什么这里看到的/dev/root大小只有3.0G呢？rootfs分区我们不是指定了14G么？这主要是因为我们的根文件系统镜像制作的就是那么大，剩余的分区空间并未使用。
4.5.4 resize2fs扩容
文件系统能通过扩充容量来利用其分区后的空闲空间。通常情况下，这甚至可以在文件系统被挂载时进行。
这里我们可以通过resize2fs指令进行扩容：
root@armsom-sige7:/# resize2fs /dev/mmcblk0p6
resize2fs 1.46.2 (28-Feb-2021)
Filesystem at /dev/mmcblk0p6 is mounted on /; on-line resizing required
[ 1881.827893] EXT4-fs warning (device mmcblk0p6): ext4_resize_begin:82: There are errors in the filesystem, so online resizing is not allowed
old_desc_blocks = 1, new_desc_blocks = 2
resize2fs: Permission denied to resize filesystem很明显扩容失败了，主要是因为该设备被挂载到/，内核不支持在线调整已挂载文件系统的大小。
为此我们制作一个SD卡启动盘，使开发板从SD启动，此时eMMC设备节点为/dev/mmcblk0。
这里我们可以通过resize2fs指令进行扩容：
zhengyang@armsom-sige7:~$ sudo e2fsck -f /dev/mmcblk0p6
e2fsck 1.46.5 (30-Dec-2021)
/dev/mmcblk0p6: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (32132, counted=9666).
Fix? yes
Free inodes count wrong (130235, counted=129568).
Fix? yes
/dev/mmcblk0p6: ***** FILE SYSTEM WAS MODIFIED *****
/dev/mmcblk0p6: 72832/202400 files (0.2% non-contiguous), 799294/808960 blocks
zhengyang@armsom-sige7:~$ sudo resize2fs /dev/mmcblk0p6
resize2fs 1.46.5 (30-Dec-2021)
Resizing the filesystem on /dev/mmcblk0p6 to 3670016 (4k) blocks.
The filesystem on /dev/mmcblk0p6 is now 3670016 (4k) blocks long. 开发板拔掉SD卡，重启启动开发板，稍等一会，显示器上会进入debain桌面系统(如果不扩容的话，由于/目录没有磁盘空间了，也就进不了debain桌面环境的)；
注意：此时需要进行应用程序 --> 设置 --> 显示进行配置，关闭调用DSI-1。
再次查看磁盘空间：
root@armsom-sige7:/# df -hT
文件系统 类型 容量 已用 可用 已用% 挂载点
/dev/root ext4 14G 3.0G 11G 23% /
devtmpfs devtmpfs 3.9G 8.0K 3.9G 1% /dev
tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs tmpfs 1.6G 2.2M 1.6G 1% /run
tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock
/dev/mmcblk0p7 ext4 121M 12M 103M 11% /oem
/dev/mmcblk0p8 ext4 43G 288K 42G 1% /userdata
tmpfs tmpfs 793M 40K 793M 1% /run/user/1000五、SDK开发
六、build.sh分析
6.1 main函数
由于main函数代码内容较长，我们只对重点内容进行分析：
点击查看代码
main()
{
[ -z "$DEBUG" ] || set -x
trap 'err_handler' ERR
set -eE
# Save intial envionments
unset INITIAL_SESSION
INITIAL_ENV=$(mktemp -u)
if [ -z "$RK_SESSION" ]; then
INITIAL_SESSION=1
env > "$INITIAL_ENV"
fi
export LC_ALL=C
export SCRIPTS_DIR="$(dirname "$(realpath "$BASH_SOURCE")")"
export COMMON_DIR="$(realpath "$SCRIPTS_DIR/..")"
export SDK_DIR="$(realpath "$COMMON_DIR/../../..")"
export DEVICE_DIR="$SDK_DIR/device/rockchip"
export CHIPS_DIR="$DEVICE_DIR/.chips"
export CHIP_DIR="$DEVICE_DIR/.chip"
export RK_DATA_DIR="$COMMON_DIR/data"
export RK_TOOL_DIR="$COMMON_DIR/tools"
export RK_IMAGE_DIR="$COMMON_DIR/images"
export RK_KBUILD_DIR="$COMMON_DIR/linux-kbuild"
export RK_CONFIG_IN="$COMMON_DIR/configs/Config.in"
export RK_BUILD_HOOK_DIR="$COMMON_DIR/build-hooks"
export BUILD_HELPER="$RK_BUILD_HOOK_DIR/build-helper"
export RK_POST_HOOK_DIR="$COMMON_DIR/post-hooks"
export POST_HELPER="$RK_POST_HOOK_DIR/post-helper"
export PARTITION_HELPER="$SCRIPTS_DIR/partition-helper"
export RK_SESSION="${RK_SESSION:-$(date +%F_%H-%M-%S)}"
export RK_OUTDIR="$SDK_DIR/output"
export RK_SESSION_DIR="$RK_OUTDIR/sessions"
export RK_LOG_BASE_DIR="$RK_OUTDIR/log"
export RK_LOG_DIR="$RK_SESSION_DIR/$RK_SESSION"
export RK_INITIAL_ENV="$RK_LOG_DIR/initial.env"
export RK_CUSTOM_ENV="$RK_LOG_DIR/custom.env"
export RK_FINAL_ENV="$RK_LOG_DIR/final.env"
export RK_ROCKDEV_DIR="$SDK_DIR/rockdev"
export RK_FIRMWARE_DIR="$RK_OUTDIR/firmware"
export RK_SECURITY_FIRMWARE_DIR="$RK_OUTDIR/security-firmware"
export RK_CONFIG="$RK_OUTDIR/.config"
export RK_DEFCONFIG_LINK="$RK_OUTDIR/defconfig"
# For Makefile
case "$@" in
make-targets)
# Chip targets
ls "$CHIPS_DIR"
;&
make-usage)
run_build_hooks "$@"
rm -f "$INITIAL_ENV"
exit 0 ;;
esac
# Log SDK information
MANIFEST="$SDK_DIR/.repo/manifest.xml"
if [ -e "$MANIFEST" ]; then
if [ ! -L "$MANIFEST" ]; then
MANIFEST="$SDK_DIR/.repo/manifests/$(grep -o "[^"]*.xml" "$MANIFEST")"
fi
TAG="$(grep -o "linux-.*-gen-rkr[^."]*" "$MANIFEST" |
head -n 1 || true)"
MANIFEST="$(basename "$(realpath "$MANIFEST")")"
echo
echo -e "e[35m############### Rockchip Linux SDK ###############e[0m"
echo
echo -e "e[35mManifest: $MANIFESTe[0m"
if [ "$TAG" ]; then
echo -e "e[35mVersion: $TAGe[0m"
fi
echo
fi
# Prepare firmware dirs
mkdir -p "$RK_FIRMWARE_DIR" "$RK_SECURITY_FIRMWARE_DIR"
cd "$SDK_DIR"
[ -f README.md ] || ln -rsf "$COMMON_DIR/README.md" .
[ -d common ] || ln -rsf "$COMMON_DIR" .
# TODO: Remove it in the repo manifest.xml
rm -f envsetup.sh
OPTIONS=${@:-allsave}
# Special handle for chip and defconfig
# e.g. ./build.sh rk3588:rockchip_defconfig
for opt in $OPTIONS; do
if [ -d "$CHIPS_DIR/${opt%%:*}" ]; then
OPTIONS=$(echo "$OPTIONS" | xargs -n 1 |
sed "s/^$opt$/chip:$opt/" | xargs)
elif echo "$opt" | grep -q "^[0-9a-z_]*_defconfig$"; then
OPTIONS=$(echo "$OPTIONS" | xargs -n 1 |
sed "s/^$opt$/defconfig:$opt/" | xargs)
fi
done
# Options checking
CMDS="$(run_build_hooks support-cmds all | xargs)"
for opt in $OPTIONS; do
case "$opt" in
help | h | -h | --help | usage | ?) usage ;;
clean:*)
# Check cleanup modules
for m in $(echo ${opt#clean:} | tr ':' ' '); do
grep -wq clean_hook
"$SCRIPTS_DIR/mk-$m.sh"
2>/dev/null || usage
done
;&
shell | cleanall)
# Check single options
if [ "$opt" = "$OPTIONS" ]; then
break
fi
echo "ERROR: $opt cannot combine with other options!"
;;
post-rootfs)
if [ "$opt" = "$1" -a -d "$2" ]; then
# Hide other args from build stages
OPTIONS=$opt
break
fi
echo "ERROR: $opt should be the first option followed by rootfs dir!"
;;
*)
# Make sure that all options are handled
if option_check "$CMDS" $opt; then
continue
fi
echo "ERROR: Unhandled option: $opt"
;;
esac
usage
done
# Prepare log dirs
if [ ! -d "$RK_LOG_DIR" ]; then
rm -rf "$RK_LOG_BASE_DIR" "$RK_LOG_DIR" "$RK_SESSION_DIR/latest"
mkdir -p "$RK_LOG_DIR"
ln -rsf "$RK_SESSION_DIR" "$RK_LOG_BASE_DIR"
ln -rsf "$RK_LOG_DIR" "$RK_SESSION_DIR/latest"
echo -e "e[33mLog saved at $RK_LOG_DIRe[0m"
echo
fi
# Drop old logs
cd "$RK_LOG_BASE_DIR"
rm -rf $(ls -t | sed '1,10d')
cd "$SDK_DIR"
# Save initial envionments
if [ "$INITIAL_SESSION" ]; then
rm -f "$RK_INITIAL_ENV"
mv "$INITIAL_ENV" "$RK_INITIAL_ENV"
ln -rsf "$RK_INITIAL_ENV" "$RK_OUTDIR/"
fi
# Init stage (preparing SDK configs, etc.)
run_build_hooks init $OPTIONS
rm -f "$RK_OUTDIR/.tmpconfig*"
# No need to go further
CMDS="$(run_build_hooks support-cmds pre-build build
post-build | xargs) cleanall clean post-rootfs"
option_check "$CMDS" $OPTIONS || return 0
# Force exporting config environments
set -a
# Load config environments
source "$RK_CONFIG"
cp "$RK_CONFIG" "$RK_LOG_DIR"
if [ -z "$INITIAL_SESSION" ]; then
# Inherit session environments
sed -n 's/^(RK_.*=)(.*)/""/p' "$RK_FINAL_ENV" >
"$INITIAL_ENV"
source "$INITIAL_ENV"
rm -f "$INITIAL_ENV"
else
# Detect and save custom environments
# Find custom environments
rm -f "$RK_CUSTOM_ENV"
for cfg in $(grep "^RK_" "$RK_INITIAL_ENV" || true); do
env | grep -q "^${cfg//"/}$" ||
echo "$cfg" >> "$RK_CUSTOM_ENV"
done
# Allow custom environments overriding
if [ -e "$RK_CUSTOM_ENV" ]; then
ln -rsf "$RK_CUSTOM_ENV" "$RK_OUTDIR/"
echo -e "e[31mWARN: Found custom environments: e[0m"
cat "$RK_CUSTOM_ENV"
echo -e "e[31mAssuming that is expected, please clear them if otherwise.e[0m"
read -t 10 -p "Press enter to continue."
source "$RK_CUSTOM_ENV"
if grep -q "^RK_KERNEL_VERSION=" "$RK_CUSTOM_ENV"; then
echo -e "e[31mCustom RK_KERNEL_VERSION ignored!e[0m"
load_config RK_KERNEL_VERSION
fi
if grep -q "^RK_ROOTFS_SYSTEM=" "$RK_CUSTOM_ENV"; then
echo -e "e[31mCustom RK_ROOTFS_SYSTEM ignored!e[0m"
load_config RK_ROOTFS_SYSTEM
fi
fi
fi
source "$PARTITION_HELPER"
rk_partition_init
set +a
export PYTHON3=/usr/bin/python3
export RK_KERNEL_VERSION_REAL=$(kernel_version_real)
# Handle special commands
case "$OPTIONS" in
cleanall)
run_build_hooks clean
rm -rf "$RK_OUTDIR" "$SDK_DIR/rockdev"
finish_build cleanall
exit 0 ;;
clean:*)
MODULES="$(echo ${OPTIONS#clean:} | tr ':' ' ')"
for m in $MODULES; do
"$SCRIPTS_DIR/mk-$m.sh" clean
done
finish_build clean - $MODULES
exit 0 ;;
post-rootfs)
shift
run_post_hooks $@
finish_build post-rootfs
exit 0 ;;
esac
# Save final environments
rm -f "$RK_FINAL_ENV"
env > "$RK_FINAL_ENV"
ln -rsf "$RK_FINAL_ENV" "$RK_OUTDIR/"
# Log configs
echo
echo "=========================================="
echo " Final configs"
echo "=========================================="
env | grep -E "^RK_.*=.+" | grep -vE "PARTITION_[0-9]" |
grep -vE "=""$|_DEFAULT=y" |
grep -vE "^RK_CONFIG|_BASE_CFG=|_LINK=|DIR=|_ENV=|_NAME=" | sort
echo
# Pre-build stage (submodule configuring, etc.)
run_build_hooks pre-build $OPTIONS
# No need to go further
CMDS="$(run_build_hooks support-cmds build post-build | xargs)"
option_check "$CMDS" $OPTIONS || return 0
# Build stage (building, etc.)
run_build_hooks build $OPTIONS
# No need to go further
CMDS="$(run_build_hooks support-cmds post-build | xargs)"
option_check "$CMDS" $OPTIONS || return 0
# Post-build stage (firmware packing, etc.)
run_build_hooks post-build $OPTIONS
}6.1.1 提示模式和错误处理
调试模式设置：首先通过判断是否设置了环境变量DEBUG，决定是否启用调试模式。如果 DEBUG 被设置为非空值，则运行 set -x 开启调试模式，这样脚本执行时会显示每一行命令的执行情况。
错误处理：使用 trap 和 ERR 捕获脚本中的错误。一旦发生错误，将调用 err_handler 函数；同时，set -eE 确保如果任何命令失败，脚本会立即退出，并且支持 ERR 跟踪。
保存初始环境变量：接着尝试保存当前的环境变量到一个临时文件中。首先，它解除定义了 INITIAL_SESSION 变量(如果存在)，然后使用 mktemp -u 生成一个唯一的临时文件路径。如果 RK_SESSION 变量未设置，则认为这是一个新的会话，并将所有当前环境变量保存到生成的临时文件中。
6.1.2 设置环境变量
接着是设置一系列环境变，这些变量定义了一些重要的目录路径，通常在脚本执行过程中会用到这些路径。
export LC_ALL=C
export SCRIPTS_DIR="$(dirname "$(realpath "$BASH_SOURCE")")"
export COMMON_DIR="$(realpath "$SCRIPTS_DIR/..")"
......realpath "$BASH_SOURCE" 获取当前脚本的绝对路径，由于build.sh指向了device/rockchip/common/scripts/build.sh；所以：
SCRIPTS_DIR = /device/rockchip/common/scripts
COMMON_DIR = /device/rockchip/common
SDK_DIR =
DEVICE_DIR = /device/rockchip
CHIPS_DIR = /device/rockchip/.chips
CHIP_DIR = /device/rockchip/.chip
...... 6.1.3 选项make-targets/make-usage
接着就是对选项make-targets和make-usage的支持，实际上也是输出帮助信息。
6.1.4 选项chip/defconfig
接着就是对如下选项的支持：
chip[:：[: ]] SoC，比如rk3588；rockchip_defconfig；defconfig[::] rockchip_defconfig；
(1) 如果有参数传递给脚本，则OPTIONS被设置为这些参数的组合；如果没有参数传递，则OPTIONS被设置为 allsave。
(2) 接着对$OPTIONS变量进行特殊处理，用于处理 chip和defconfig的情况。它会检查每个参数，并根据特定的条件对其进行转换。
首先：
if [ -d "$CHIPS_DIR/${opt%%:*}" ]; then
OPTIONS=$(echo "$OPTIONS" | xargs -n 1 |
sed "s/^$opt$/chip:$opt/" | xargs)检查是否存在以$CHIPS_DIR开头、后面跟着$opt变量:分隔之前的字符串作为目录名， 如果满足；修改 $OPTIONS 变量，替换内容$opt 为 chip:$opt；
- 比如
./builsh rk3588:rockchip_defconfig，opt=rk3588:rockchip_defconfig，处理后OPTIONS=chip:rk3588:rockchip_defconfig；
接着：
elif echo "$opt" | grep -q "^[0-9a-z_]*_defconfig$"; then
OPTIONS=$(echo "$OPTIONS" | xargs -n 1 |
sed "s/^$opt$/defconfig:$opt/" | xargs)
fi如果是以_defconfig结尾命名，修改 $OPTIONS 变量，替换内容$opt 为 defconfig:$opt；
- 比如
./builsh rockchip_defconfig，opt=rockchip_defconfig，处理后OPTIONS=defconfig:rockchip_defconfig；
6.1.5 选项检查
首先：
CMDS="$(run_build_hooks support-cmds all | xargs)"执行run_build_hooks support-cmds all，并将输出结果经过xargs处理后赋值给CMDS变量；
xargs是一个常用的命令行工具，用于将输入转换为命令行参数；- 在这种情况下，没有指定任何选项，意味着
xargs将把输入中的所有元素合并成一行，以空格分隔；
接着是一段选项检查的代码；
for opt in $OPTIONS; do
case "$opt" in
help | h | -h | --help | usage | ?) usage ;;
clean:*)
# Check cleanup modules
for m in $(echo ${opt#clean:} | tr ':' ' '); do
grep -wq clean_hook
"$SCRIPTS_DIR/mk-$m.sh"
2>/dev/null || usage
done
;&
shell | cleanall)
# Check single options
if [ "$opt" = "$OPTIONS" ]; then
break
fi
echo "ERROR: $opt cannot combine with other options!"
;;
post-rootfs)
if [ "$opt" = "$1" -a -d "$2" ]; then
# Hide other args from build stages
OPTIONS=$opt
break
fi
echo "ERROR: $opt should be the first option followed by rootfs dir!"
;;
*)
# Make sure that all options are handled
if option_check "$CMDS" $opt; then
continue
fi
echo "ERROR: Unhandled option: $opt"
;;
esac
usage
done根据传入的选项($OPTIONS)进行判断和处理；
- 当选项满足
help | h | -h | --help | usage | ?，执行usage函数。比如我们前文执行./build.sh help，就是则调用usage函数来显示帮助信息； - 如果选项以
clean:开头，则验证验证相应的清理模块是否存在，比如./build.sh clean:kernel，则判断"device/rockchip/common/scripts/mk-kernel.sh/mk-kernel.sh中是否包含clean_hook方法；后续会调用mk-kernel.sh clean执行清理工作； - 如果选项是
shell或cleanall，执行函数run_build_hooks clean，该函数则会遍历device/rockchip/common/scripts下shell脚本文件，并传入clean参数函数依次执行； - 如果选项是
post-rootfs，则后续会调用run_post_hooks $@以trigger post-rootfs hook scripts；
参考文章
[1] Rockchip_Developer_Guide_Linux_Software_CN.pdf
[2] repo介绍与使用
[3] Rockchip_Developer_Guide_Linux_Upgrade_CN.pdf
[4] Rockchip RK3588 - NanoPC-T6开发板介绍
[5] Rockchip RK3399 - NanoPC-T4开发板介绍
[6] Buildroot根文件系统构建
[7] Debian根文件系统构建
