0% found this document useful (0 votes)

3K views57 pages

RK3576 Developer Guide Android14 SDK en

Uploaded by

jasonfeng.hot

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

3K views57 pages

RK3576 Developer Guide Android14 SDK en

Uploaded by

jasonfeng.hot

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 57

Security Class: Top-Secret( ) Secret( ) Internal( ) Public( √ )

RK3576 Android 14.0 SDK Developer

Guide

File No.: RK-KF-YF-790

Current Version: V1.0.0

Status:
[ ] Draft Author: Wu Liangqing

[ √ ] Released
Finish Date: 2024-04-20
[ ] Modifying
Auditor: Jin Huajun

Finish Date: 2024-04-30

DISCLAIMER
THIS DOCUMENT IS PROVIDED “AS IS”. ROCKCHIP ELECTRONICS CO., LTD.(“ROCKCHIP”)DOES NOT
PROVIDE ANY WARRANTY OF ANY KIND, EXPRESSED, IMPLIED OR OTHERWISE, WITH RESPECT TO
THE ACCURACY, RELIABILITY, COMPLETENESS,MERCHANTABILITY, FITNESS FOR ANY PARTICULAR
PURPOSE OR NON-INFRINGEMENT OF ANY REPRESENTATION, INFORMATION AND CONTENT IN
THIS DOCUMENT. THIS DOCUMENT IS FOR REFERENCE ONLY. THIS DOCUMENT MAY BE UPDATED
OR CHANGED WITHOUT ANY NOTICE AT ANY TIME DUE TO THE UPGRADES OF THE PRODUCT OR
ANY OTHER REASONS.

Trademark Statement
"Rockchip", "瑞芯微", "瑞芯" shall be Rockchip’s registered trademarks and owned by Rockchip. All
the other trademarks or registered trademarks mentioned in this document shall be owned by
their respective owners.

All rights reserved. ©2024. Rockchip

Electronics Co., Ltd.
Beyond the scope of fair use, neither any entity nor individual shall extract, copy, or distribute
this document in any form in whole or in part without the written approval of Rockchip.

Rockchips Electronics Co., Ltd.

No.18 Building, A District, No.89, software Boulevard Fuzhou, Fujian, PRC
Website: www.rock-chips.com
Customer service Tel: +86-4007-700-590
Customer service Fax: +86-591-83951833
Customer service e-Mail: [email protected]

RK3576 Android 14.0 SDK Chipset

support
Chipset platform Support or not SDK version

RK3576 Support RKR4

Revision History
Version Revision
Author Revision Description Remark
no. Date

Wu release RKR4 SDK supporting

V1.0.0 2024-04-20
Liangqing RK3576

If there is any question about the document, please email to: [email protected]

RK3576 Android 14.0 SDK Developer Guide

DISCLAIMER
Trademark Statement
All rights reserved. ©2024. Rockchip Electronics Co., Ltd.
RK3576 Android 14.0 SDK Chipset support
Revision History
RK3576 Android 14.0 SDK code download and compile
Code download
Download address
Download server mirroring
Set up your own repo code server
Environment
Set up gitolite
Server-side operation
Client-side operation
Set up repo mirror
Server-side operation
Client-side operation
Client-side operation
Code management
Switch your own code branches
Code modification submittal
Synchronize RK codes
kernel Code path description
Code compiling
Lunch item Description
One key compiling command
Compiling command summary
GKI
Other compiling instruction
Android14.0 cannot directly flash kernel.img and resource.img
Image flashing
Image flashing tool
Image instruction
Image instruction
Generic Kernel Image（GKI）
Use fastboot to flash dynamic partition
DTBO function
Modify fstab file
Modify parameter.txt
Android common configuration
Create product lunch
Kernel dts instruction
Create new product dts
Patch release
Document instruction
Peripheral support list
Camera IQ Tool Document
rknn-toolkit2 developing SDK and document
RKDocs Instruction
Tool usage
StressTest
Module related
Non module related
PCBA test tool
DeviceTest
USB driver
Development flashing tool
Windows version
Linux version
Tool to implement SD upgrading and boot
Write SN tool
DDR welding test tool
efuse flashing tool
efuse/otp sign tool
Factory production image flashing tool
userdata partition data prebuilt tool
Camera IQ Tool
System debugging
ADB tool
Overview
USB adb usage
ADB commonly used command elaboration
Logcat tool
Logcat command usage
The commonly used logcat filter method
Procrank tool
Use procrank
Search the specific content information
Trace the process memory status
Dumpsys tool
Use Dumpsys
Last log enable
FIQ mode
Common issues
What is current kernel version and u-boot version?
How to acquire the corresponding RK release version for current SDK
How to confirm if local SDK is already updated to the latest SDK version released by RK
Replace uboot and kernel logo picture
How to modify Android system to support 64-bit only
Power off charging and low battery precharging
Uboot charging logo package and replace
HDMI IN configuration
RM310 4G configuration
WIFI Sleep Policy configuration
Recovery rotation configuration
Android Surface rotation
Replace some remote of AOSP source code
Data area read and write performance optimization
Change userdata partition file system to EXT4
Modify power on/off animation and tones
APP performance mode setting
Debugging method of GPU related issues
OTP and efuse instruction
How to judge from the code whether OTP/EFUSE of the device is already flashed or not
Enable/disable selinux
Warning “There's an internal problem with your device.” pops up after boot up
How to enable the setting options for Ethernet in Settings
About AVB and security boot
Cannot use IO commands
The SN command rules
Failer about LZ4 when Kernel compiling
Android Samba function
NFS boot
Update RK3528 DDR 4BIT Loader
Multi-screen display and touch
Different screen different sound
APPENDIX A Compiling and development environment setup
Initializing a Build Environment
Choosing a Branch
Setting up a Linux build environment
Installing the JDK
Configuring USB Access
APPENDIX B SSH public key operation instruction
APPENDIX B-1 SSH public key generation
APPENDIX B-2 Use key-chain to manage the key
APPENDIX B-3 Multiple devices use the same ssh public key
APPENDIX B-4 Switch different ssh public keys on one device
APPENDIX B-5 Key authority management
APPENDIX B-6 Git authority application instruction

RK3576 Android 14.0 SDK code download

and compile
Code download
Download address

repo init --repo-url https://gerrit.rock-chips.com:8443/repo-release/tools/repo

-u https://gerrit.rock-chips.com:8443/Android_U/manifests -b rk3576 -m
Android14.xml

If you request Express permission, then the download address is as follows:

repo init --repo-url https://gerrit.rock-chips.com:8443/repo-release/tools/repo

-u https://gerrit.rock-chips.com:8443/Android_U/manifests -b rk3576 -m
Android14_Express.xml

Download server mirroring

repo init --repo-url https://gerrit.rock-chips.com:8443/repo-release/tools/repo

-u https://gerrit.rock-chips.com:8443/Android_U/manifests -b rk3576 -m
Android14.xml --mirror

If you request Express permission, then the download address is as follows:

repo init --repo-url https://gerrit.rock-chips.com:8443/repo-release/tools/repo

-u https://gerrit.rock-chips.com:8443/Android_U/manifests -b rk3576 -m
Android14_Express.xml --mirror

Note: repo is a script invoking git developed by Google using Python script, and mainly used to
download, manage Android project software lib. The download address is as follows:

git clone https://gerrit.rock-chips.com:8443/repo-release/tools/repo

Generally, Rockchip FAE contact will provide the initial compressed package of the corresponding
version SDK in order to help customers acquire SDK source code quickly. Take
Rockchip_Android14.0_SDK_RELEASE.tar.gz.* as an example, you can sync the source code
through the following command after getting the initial package:

mkdir RK3576_Android14.0_SDK_RELEASE
cat RK3576_Android14.0_SDK_RELEASE.tar.gz* | tar -zx -C
RK3576_Android14.0_SDK_RELEASE
cd RK3576_Android14.0_SDK_RELEASE
.repo/repo/repo sync -l
.repo/repo/repo sync -c

Set up your own repo code server

Environment
You can install openssh-server for remote login, git for project management, and keychain for
public key and private key management tools.

sudo apt-get install openssh-server git keychain

Set up gitolite
Server-side operation

Take server address: 10.10.10.206 as an example for description.

1. create git account：

sudo adduser --system --shell /bin/bash --group git

sudo passwd git

2. Log in to the server as a 'git' account;

3. Make sure that '~/.ssh/authorized_keys' is empty or non-existent;
4. Copy the server administrator's public key to '~/ yourname.pub';
5. Download gitolite source code;

git clone https://github.com/sitaramc/gitolite.git

6. Create bin directory in git user directory;

mkdir -p ~/bin

7. Please execute following commands to install gitolite, and the installation method is
diﬀerent for diﬀerent versions. Please refer to the documentation in source code:

gitolite/install -to ~/bin

8. Set the administrator.

~/bin/gitolite setup -pk YourName.pub

Client-side operation

1. Clone gitolite management warehouse of the server;

git clone ssh://[email protected]/gitolite-admin.git

2. Add user's public key to the gitolite directory;

cp username.pub keydir/username.pub

3. Add an administrator user.

vi conf/gitolite.conf
@admin = admin1 admin2 admin3
repo gitolite-admin
RW+ = @admin

Set up repo mirror

Server-side operation
1. Log in to the server as a 'git' account;
2. Download the repo tool in the root directory；

git clone https://gerrit.rock-chips.com:8443/repo-release/tools/repo

3. Create a new RK_Android14_mirror directory;

mkdir RK_Android14_mirror

4. Enter the RK_Android14_mirror directory;

cd RK_Android14_mirror

5. Download RK Android14 SDK mirror;

repo init --repo-url https://gerrit.rock-chips.com:8443/repo-release/tools/repo

-u https://gerrit.rock-chips.com:8443/Android_U/manifests -b rk3576 -m
Android14.xml --mirror

6. Create warehouse group permissions.

.repo/repo/repo list -n > android_u.conf

sed -i 's/^/@android_t = RK_Android14_mirror\/&/g' android_u.conf

Client-side operation

1. Copy android_u.conf on the server-side to ·gitolite-admin/conf/· on the client-side;

2. Add group permissions.

vi conf/android_u.conf
@usergroup = user1 user2 user3
repo @android_u
R = @usergroup
RW+ = @admin

vi conf/gitolite.conf
include "android_u.conf"

3. Create your own new manifests warehouse.

vi conf/android_u.conf
@android_u = Android_T/manifests_xxx

Client-side operation
1. Download manifests_xxx warehouse on the client-side;
Download manifests_xxx.git warehouse on other client-side

git clone ssh://[email protected]/Android_u/manifests_xxx.git

2. Download original manifests warehouse on the client-side;

git clone ssh://[email protected]/Android_U/manifests.git

3. Submit manifest.xml ﬁle to manifest_xxx warehouse created newly;

Copy the ﬁles below original manifests to the manifests_xxx

cd manifests_xxx
cp -rf manifests/*.xml manifests_xxx/

check copy ﬁles

git status

Android14.xml
Android14_Express.xml
default.xml
include/rk3576_repository.xml
include/rk_checkout_from_aosp.xml
include/rk_modules_repository.xml
remote.xml
remove_u.xml
remove_unused.xml

Local commits

git add -A
git commit -m "init xxx"

Push to the remote branch

git push origin master:master

4. Create your own code download link.

Download the repo tool in the root directory

git clone https://gerrit.rock-chips.com:8443/repo-release/tools/repo

After following the above steps, your own code download link is as follows

mkdir Android14
cd Android14
~/repo/repo init -u ssh://[email protected]/Android_U/manifests_xxx.git -m
Android14.xml

Thereinto:
//10.10.10.206 which is your server address
You can complete your own repo server set-up with above steps, and you can share your code
server links with colleagues to work together.

Code management
After setting up the code server with above steps, most of the code warehouses use the default
branches of RK. If some warehouses need to modify their own codes, you can refer to the
following steps for operation.

Switch your own code branches

1. Enter the code warehouse that needs to be modiﬁed, and we take the kernel directory as an
example to illustrate;

cd kernel-6.1

2. Switch a local branch;

git checkout remotes/m/master -b xxx_branch

3. Push xxx_branch to remote server;

git push rk29 xxx_branch:xxx_branch

Thereinto, rk29 is remote, which can be completed automatically by tab key directly

4. Enter .repo/manifests directory and modify the branch which is appointed by manifest;
Enter .repo/manifests directory, and you can ﬁnd the manifest location corresponding to the
kernel warehouse by grep kernel

cd .repo/manifests

--- a/include/rk_modules_repository.xml
+++ b/include/rk_modules_repository.xml
@@ -10,7 +10,7 @@
<project path="hardware/rockchip/libgraphicpolicy"
name="rk/hardware/rk29/libgraphicpolicy" remote="rk"
revision="refs/tags/android-1s.0-mid-rkr1" />
<project path="hardware/rockchip/libhwjpeg" name="rk/hardware/rk29/libhwjpeg"
remote="rk" revision="refs/tags/android-14.0-mid-rkr1"/>
<project path="u-boot" name="rk/u-boot" remote="rk"
revision="refs/tags/android-14.0-mid-rkr1"/>
- <project path="kernel" name="rk/kernel" remote="rk29"
revision="refs/tags/android-14.0-mid-rkr1"/>
+ <project path="kernel" name="rk/kernel" remote="rk29" revision="xxx_branch"/>

5. Submit the modiﬁed manifest to the remote branch.

git add include/rk_modules_repository.xml

git commit -m "change kernel branch on xxx_branch"
git push origin default:master
After submitting manifests warehouse, other colleagues can synchronize the kernel codes of your
own branches.

Code modiﬁcation submittal

After switching branches according to the steps above, you can commit your modiﬁcation on
your branches and push them directly to the xxx_branch.

Synchronize RK codes
1. It's required to synchronize RK codes on the server-side;

cd RK_Android14_mirror

.repo/repo/repo sync -c

2. The manifests that RK modiﬁes are combined by client-side;

Download the original manifests warehouse of RK;

git clone //10.10.10.206/wlq/test/manifests.git

The manifests (RK original) and the manifests_xxx (yourselves) are compared with the contrast
tools to combine the diﬀerent parts that RK modiﬁes to your own warehouses (mainly modify the
tag, adding and removing the warehouse, etc)

After comparing and conﬁrming, the modiﬁcation will be pushed to the manifests_xxx.

You can also confirm which warehouses are modified in this step, and in the next step you will
combine the modified warehouses.

3. The directories switched branches by yourselves need to push the merge that RK modiﬁes
to your own branches manually.
Take kernel as an example：

Check the pointed remote branches at present

wlq@wlq:~/home1/test2/kernel-6.1$ git branch -av

* android-11.0-mid-rkr7 0bde59fad73a ARM: configs: rockchip_defconfig enable
ION_CMA_HEAP
xxx_branch 0bde59fad73a ARM: configs: rockchip_defconfig enable
ION_CMA_HEAP
remotes/m/master -> rk29/xxx_branch
remotes/rk29/xxx_branch 0bde59fad73a ARM: configs: rockchip_defconfig enable
ION_CMA_HEAP

You can ﬁnd that the branch pointed at present is: remotes/m/master ->
rk29/xxx_branch

Create a local branch (switch from your own remote branch)

git checkout remotes/m/xxx_branch -b local_xxx_branch

You can ﬁnd the latest tag of Android14 currently is android-14.0-mid-rkr1

combine android-14.0-mid-rkr1 to the local branch

git merge android-14.0-mid-rkr1

Check if there is a conflict. If there is a conflict, resolve the conflict firstly. You can execute the
next step when there is no conflict.

push the codes which have been combined to the remote branch

git push rk29 local_xxx_branch:xxx_branch

The other directories swiched can be combined and submitted in this way

kernel Code path description

Android14 supports version 6.1 of the kernel, kernel source code in the project kernel-6.1
directory,

Code compiling
Lunch item Description
lunch chipest
other description
item adapted

Suitable for Android 14 products, compatible with RK3576

rk3576_u-
RK3576 development board hardware, compiled as user version, used
user
in production, Android system supports 64-bit and 32-bit

Suitable for Android 14 products, hardware adapted for RK3576

rk3576_u- development board, compiled as userdebug version, used for
RK3576
userdebug development and debugging, Android system supports 64-bit
and 32-bit

One key compiling command

./build.sh -UKAup
（ WHERE: -U = build uboot
-C = build kernel with Clang
-K = build kernel
-A = build android
-p = will build packaging in IMAGE
-o = build OTA package
-u = build update.img
-v = build android with 'user' or 'userdebug'
-d = huild kernel dts name
-V = build version
-J = build jobs
------------you can use according to the requirement, no need to record
uboot/kernel compiling commands------------------
）

============================================================
Please remember to set the environment variable before using the one key
compiling command, and select the platform to be compiled, for example:
source build/envsetup.sh
lunch rk3588_t-userdebug
============================================================

Compiling command summary

The
one key kernel uboot
Soc type reference Android
compiling compiling compiling
model

rk3576- build/envsetup.sh;lunch ./build.sh - ./build.sh - ./build.sh -

RK3576 EVB
evb1-v10 rk3576_u-userdebug AUCKu K U

GKI
To enable GKI (Generic Kernel Image) functionality on the RK3576 platform, follow these steps:

wlq@sys2206:~/b0_A14_bringup/device/rockchip/rk3576$ git diff

diff --git a/rk3576_u/BoardConfig.mk b/rk3576_u/BoardConfig.mk
index eb52fb6..f59df62 100755
--- a/rk3576_u/BoardConfig.mk
+++ b/rk3576_u/BoardConfig.mk
@@ -14,7 +14,7 @@
# limitations under the License.
#
BUILD_WITH_GO_OPT := false
-BOARD_BUILD_GKI := false
+BOARD_BUILD_GKI := true

BOARD_GRAVITY_SENSOR_SUPPORT := true

After BOARD_BUILD_GKI := false, the AB function will close automatically.

Please refer to the document about GKI details:
RKDocs/android/《Rockchip_Developer_Guide_Android14_GKI_CN》

Other compiling instruction

Android14.0 cannot directly ﬂash kernel.img and resource.img

The following compilation is only applicable for non-GKI. For GKI, please refer to the document
RKDocs/android/《Rockchip_Developer_Guide_Android14_GKI_CN》.
The kernel.img and resource.img of Android 14.0 are included in the boot.img. To compile the
kernel, use the build.sh -AK command. After compilation, burn the boot.img under rockdev. This
process involves recompiling Android, so compilation time will be relatively long. It is
recommended to use the following method to compile the kernel separately.
Compile Kernel Separately to Generate boot.img
Principle of compilation: Replace the compiled kernel.img and resource.img in the kernel
directory with the old boot.img.
Taking the RK3576 prototype as an example, replace the corresponding boot.img and DTS during
compilation. Here, BOOT_IMG=../rockdev/Image-rk3576_u/boot.img speciﬁes the path of the old
boot.img. The command is as follows:

Export clang to the environment

cd kernel-6.1
export PATH=../prebuilts/clang/host/linux-x86/clang-r487747c/bin:$PATH
alias msk='make CROSS_COMPILE=aarch64-linux-gnu- LLVM=1 LLVM_IAS=1'

rk3576:
msk ARCH=arm64 rockchip_defconfig android-14.config rk3576.config && msk
ARCH=arm64 BOOT_IMG=../rockdev/Image-rk3576_u/boot.img rk3576-evb1-v10.img -j32

You can flash boot.img under the catalogue of kernel-6.1 directly to boot position of machine
after compiling, and please load the partition table（parameter.txt） when flashing, for fear of
flashing to the wrong place.

Image ﬂashing
Image ﬂashing tool

Android14 requires to update the USB driver DriverAssitant to V5.1.1 version. You can refer to the
tool instruction chapter to do the upgrade.
Windows ﬂashing tool:
The ﬁrmware burning tool for the RK3576 platform on Windows requires the use of version
3.28 or above.
RKTools/windows/AndroidTool/AndroidTool_Release_v3.28

Linux烧写工具：
<span style="color:red;">**The firmware flashing tool for the RK3576 platform on
Linux requires the use of version 2.30 or above.**</span>
RKTools/linux/Linux_Upgrade_Tool/Linux_Upgrade_Tool_v2.30

There are more details in the tool instruction chapter.

Image instruction

After complete compiling, it will generate the following ﬁles:

rockdev/Image-rk3576_u/
├── boot-debug.img
├── boot.img
├── config.cfg
├── dtbo.img
├── MiniLoaderAll.bin
├── misc.img
├── parameter.txt
├── pcba_small_misc.img
├── pcba_whole_misc.img
├── recovery.img
├── resource.img
├── super.img
├── uboot.img
├── update.img
└── vbmeta.img

Just ﬂash the following ﬁles:

rockdev/Image-rk3576_u/
├── boot.img
├── dtbo.img
├── MiniLoaderAll.bin
├── misc.img
├── parameter.txt
├── recovery.img
├── super.img
├── uboot.img
└── vbmeta.img

or you can directly ﬂash update.img

Image instruction

Image Instruction

boot.img including ramdis、kernel、dtb

the diﬀerence between boot.img and boot-debug.img is that user

boot-debug.img
image can ﬂash this boot.img to do root operation

dtbo.img Device Tree Overlays refer to dtbo chapter instruction later

the configuration file of the flash tool, you can directly load the
config.cfg
options required to be flashed for the flash tool

MiniLoaderAll.bin including ﬁrst level loader

including recovery-wipe boot symbol information, after ﬂashing it

misc.img
will enter recovery

parameter.txt including partition information

including pcba boot symbol information, after ﬂashing it will enter

pcba_small_misc.img
the simple pcba mode

including pcba boot symbol information, after ﬂashing it will enter

pcba_whole_misc.img
the complete pcba mode

recovery.img including recovery-ramdis、kernel、dtb

super.img including the contents of odm、vendor、system partitions

including BL31、BL32 which are not generated for

trust.img
RK3566/RK3568, no need to ﬂash

uboot.img including uboot image

vbmeta.img including avb veriﬁcation information, used for AVB veriﬁcation

including the above img files to be flashed, can be used for the
update.img
tool to directly flash the whole image package

Generic Kernel Image（GKI）

All the Android 14 products certiﬁcating GMS and EDLA are forced to use GKI for kernel, please
refer to the document for GKI conﬁguration and compiling:

RKDocs/android/Rockchip_Developer_Guide_Android14_GKI_CN.pdf

Use fastboot to ﬂash dynamic partition

The new device with R supports dynamic partition, and already
removessystem/vendor/odm/product/system_ext partitions. Please ﬂash super.img. Use
fastbootd can ﬂash system/vendor/odm alone. The version of adb and fastboot should be the
latest. SDK provides the compiled tool package:

RKTools/linux/Linux_adb_fastboot (Linux_x86 version)

RKTools/windows/adb_fastboot (Windows_x86 version)

Use the command to ﬂash dynamic partition:

adb reboot fastboot

fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash odm odm.img

Note: After entering fastbootd mode, relative information of the device will be displayed on the
screen, as shown below:

Note: please enter bootloader when using fastboot in the non-dynamic partition:

adb reboot bootloader

The way to ﬂash GSI:

After the device is unlocked, enter fastbootd, only need to flash system.img of GSI and
misc.img of the image, and after flashing it will enter recovery to do factory reset. Attach the
complete flashing process as below:

1. Reboot to bootloader, lock->unlock the device:

adb reboot bootloader

fastboot oem at-unlock-vboot ## for the customers already flashing avb public
key, please refer to the corresponding document to unlock.

2. Reset to factory setting, reboot to fastbootd:

fastboot flash misc misc.img

fastboot reboot fastboot ## now it will enter fastbootd

3. Start to ﬂash GSI

fastboot delete-logical-partition product ## (optional) for the device with

small partition space, you can execute this command to delete product partition
first and then flash GSI
fastboot flash system system.img
fastboot reboot ## after flashing successfully, reboot the device

Use DSU(Dynamic System Updates) to flash GSI, and current Rockchip platform already
supports DSU by default. As this function requires large memory, it is not recommended to
use on the device with 1G DDR or less. For the instruction and usage of DSU, please refer to
Android official website:
https://source.android.com/devices/tech/ota/dynamic-system-updates
Note 1: when testing VTS, need to flash the compiled boot-debug.img to boot partition.
Note 2: when testing CTS-ON-GSI, no need to flash boot-debug.img.
Note 3: please use GSI image ended with -signed released by Google for testing.

DTBO function
Android 10.0 and above versions support Device Tree Overlays function, which requires to ﬂash
dtbo.img during development, and is compatible with multiple products.
The modiﬁcation method:

1. Find (or specify) the template ﬁle:

get_build_var PRODUCT_DTBO_TEMPLATE

For example:

PRODUCT_DTBO_TEMPLATE := $(LOCAL_PATH)/dt-
overlay.in(device/rockchip/rk576/rk3576_u/dt-overlay.in)

2. Add or modify the required node:

For example:

/dts-v1/;
/plugin/;
&chosen {
bootargs_ext = "androidboot.boot_devices=${_boot_device}";
};

&firmware_android {
vbmeta {
status = "disabled";
};
fstab {
status = "disabled";
};
};

&reboot_mode {
mode-bootloader = <0x5242C309>;
mode-charge = <0x5242C30B>;
mode-fastboot = <0x5242C303>;
mode-loader = <0x5242C301>;
mode-normal = <0x5242C300>;
mode-recovery = <0x5242C303>;
};

Note: There must be alias in the dts when using dtbo, otherwise it cannot overlay
successfully

Modify fstab ﬁle

1. Fine (or specify) the template ﬁle:

get_build_var PRODUCT_FSTAB_TEMPLATE

For example:

PRODUCT_FSTAB_TEMPLATE := device/rockchip/common/scripts/fstab_tools/fstab.in

2. Modify: add partition mounting, modify swap_zram parameter, modify data partition format
and so on

Modify parameter.txt
Android 14 adds the tool that can generate parameter.txt, and support to compile parameter.txt
according to the configuration parameters. If there is no configuration template file, it will find
and add the modified parameter.txt file.

1. Find (or specify) the template ﬁle:

get_build_var PRODUCT_PARAMETER_TEMPLATE

For example:

PRODUCT_PARAMETER_TEMPLATE :=
device/rockchip/common/scripts/parameter_tools/parameter.in
2. Partition size conﬁguration(example as below):

BOARD_SUPER_PARTITION_SIZE := 2688548864
BOARD_DTBOIMG_PARTITION_SIZE := xxxx
BOARD_BOOTIMAGE_PARTITION_SIZE := xxxxx
BOARD_CACHEIMAGE_PARTITION_SIZE := xxxx

3. Not to use parameter generation tool:

Just add a parameter.txt ﬁle to your device directory:
For example:

device/rockchip/rk3576/rk3576_u/parameter.txt

4. Only use the tool to generate parameter.txt(example as below)：

parameter_tools --input
device/rockchip/common/scripts/parameter_tools/parameter.in --firmware-version
14.0 --machine-model rk3576 --manufacturer rockchip --machine rk3576_u --
partition-list
uboot_a:4096K,trust_a:4M,misc:4M,dtbo_a:4M,vbmeta_a:4M,boot_a:33554432,backup:30
0M,security:4M,cache:300M,metadata:4096,frp:512K,super:2G --output
parameter_new.txt

Note: If need to do the big version upgrade through OTA, please directly use the previous
version's parameter.txt

5. Add a new partition

Take baseparameter adding for example:

Give a deﬁnition in the BoardConﬁg.mk of the product:BOARD_WITH_SPECIAL_PARTITIONS

like: BOARD_WITH_SPECIAL_PARTITIONS := baseparameter:1M,logo:16M

device/rockchip/rk3576/rk3576_u/BoardConfig.mk
+++ b/BoardConfig.mk
@@ -494,4 +494,11 @@ ifeq ($(strip $(BOARD_TWRP_ENABLE)), true)
+BOARD_WITH_SPECIAL_PARTITIONS := baseparameter:1M

Add BOARD_WITH_SPECIAL_PARTITIONS to RebuildParameter.mk

device/rockchip/common/build/rockchip/RebuildParameter.mk
+ifneq ($(strip $(BOARD_WITH_SPECIAL_PARTITIONS)), )
+partition_list := $(partition_list),$(BOARD_WITH_SPECIAL_PARTITIONS)
+endif

Android common conﬁguration

Create product lunch

Here are the steps to create a new product named "rk3576_new_u" based on the RK3576
platform:

1. Navigate to the device/rockchip/rk3576 directory.

2. Create a new directory named rk3576_new_u under the device/rockchip/rk3576 directory.
3. Refer to the existing rk3576_u product directory under device/rockchip/rk3576. You can start
by copying the rk3576_u directory and renaming it to rk3576_new_u.
You can use the following command to copy the directory:

cp -r rk3576_u rk3576_new_u

4. Once you have copied the directory, navigate into the rk3576_new_u directory.
5. Replace all occurrences of the string rk3576_u with rk3576_new_u in the ﬁles inside the
rk3576_new_u directory. You can use tools like sed or manually edit the ﬁles to make the
changes.
For example, you can use sed command like this:

sed -i 's/rk3576_u/rk3576_new_u/g' *

This command will replace all occurrences of rk3576_u with rk3576_new_u in all ﬁles inside the
rk3576_new_u directory.

6. Once you have made the changes, your new product directory rk3576_new_u is ready for
further customization and development.

Kernel dts instruction

Create new product dts

You can select the corresponding dts according to the conﬁguration in the following table as
reference to create new product dts.

Soc PMIC Type Model DTS

RK3576 RK806 EVB RK3576 EVB1 rk3576-evb1-v10

RK3576 RK806 EVB RK3576 EVB1 + RK628 rk3576-evb1-v10-rk628-hdmi2csi

Patch release
Redmine system will release some important patches from time to time, the link is as follows:

https://redmine.rock-chips.com/projects/rockchip_patch/issues

You can subscribe to receive real-time email notiﬁcation of patch release in the following ways:
Step 1: Log in to redmine system
Log in to redmine system with redmine account registered with Rockchip.
Step 2: access my account

Step 3: Select an email notiﬁcation type

In the following figure, select the mail notification drop-down to receive all notifications for the
selected items

Step 4: Select the project

Check the patch release item as shown below and click Save

Done:
After a successful subscription, Rockchip can receive email notiﬁcations when patches are
released through the email address registered on redmine.

Document instruction

Peripheral support list

DDR/EMMC/NAND FLASH/WIFI/3G/CAMERA support lists keep updating in redmine, through the
following link:

https://redmine.rockchip.com.cn/projects/fae/documents

Camera IQ Tool Document

external/camera_engine_rkaiq/rkisp2x_tuner/doc/
├── Rockchip_Color_Optimization_Guide_ISP2x_CN_v2.0.0.pdf
├── Rockchip_IQ_Tools_Guide_ISP2x_CN_v2.0.0.pdf
└── Rockchip_Tuning_Guide_ISP21_CN_v2.0.0.pdf

rknn-toolkit2 developing SDK and document

hardware/rockchip/rknn-toolkit2/doc/

RKDocs Instruction
RKDocs/
├── android
│ ├── Android11 异显开发说明.zip
│ ├── audio
│ │ └── Rockchip_Developer_Guide_Android_Multi_Audio_CN.pdf
│ ├── bt
│ │ └── Rockchip_Introduction_Android9.0_BT_Configuration_CN.pdf
│ ├── patches
│ │ └── root
│ │ ├── android11_root.pdf
│ │ └── RootChecker.apk
│ ├── Rockchip_Android14_GKI_Developer_Guide_CN.pdf
│ ├── Rockchip_Android14_SDK_Developer_Guide_CN.pdf
│ ├── Rockchip_Android14_SDK_Developer_Guide_EN.pdf
│ ├── Rockchip_Android_Remote_key_Provisioning_Guide.pdf
│ ├── Rockchip_Developer_Guide_Android11_Optimization_CN.pdf
│ ├── Rockchip_Developer_Guide_Android_AB_System_Upgrading_CN.pdf
│ ├── Rockchip_Developer_Guide_Android_Recovery_CN.pdf
│ ├── Rockchip_Developer_Guide_Android_SELinux(Sepolicy)CN.pdf
│ ├── Rockchip_Developer_Guide_PCBA_Test_Tool_V1.3_CN&EN.pdf
│ ├── Rockchip_Firmware_Upgrade_Failed_Analyze_Method_CN.pdf
│ ├── Rockchip_Introduction_Android_Application_Preinstallation_CN&EN.pdf
│ ├── Rockchip_Introduction_Android_Boot_Video_CN.pdf
│ ├── Rockchip_Introduction_Android_BOX_Display_Framework_Configuration_CN.pdf
│ ├── Rockchip_Introduction_Android_Factory_Reset_Protection_CN&EN.pdf
│ ├── Rockchip_Introduction_Android_Log_System.pdf
│ ├── Rockchip_Introduction_Android_Performance_Mode_CN&EN.pdf
│ ├──
Rockchip_Introduction_Android_Power_On_Off_Animation_and_Tone_Customization_CN&EN.pdf
│ ├── Rockchip_Introduction_Android_Samba_CN.pdf
│ ├── Rockchip_Introduction_Android_Widevine_Project_Start_Preparation_CN.pdf
│ ├── Rockchip_Introduction_Box_Media_Application_CN&EN.pdf
│ ├── Rockchip-Parameter-File-Format-Version1.4-CN.pdf
│ ├── Rockchip_User_Guide_Android_GMS_Configuration_CN.pdf
│ ├── Rockchip_User_Guide_Android_GMS_Configuration_EN.pdf
│ ├── Rockchip_User_Guide_Box_FactoryTestTool_V3.0_CN.pdf
│ ├── Rockchip_User_Guide_Dr.G_CN&EN.pdf
│ ├── Rockchip_User_Guide_Magisk_Installation_EN.pdf
│ ├── video
│ │ └── Rockchip_Android_Multimedia_FAQ_CN.pdf
│ └── wifi
│ ├── Rockchip_Introduction_REALTEK_WIFI_Driver_Porting_CN&EN.pdf
│ └── Rockchip_Introduction_WIFI_Configuration_CN&EN.pdf
└── common
├── Audio
│ ├── Rockchip_Developer_Guide_Android_EQ_DRC_CN.pdf
│ ├── Rockchip_Developer_Guide_Android_Multi_Audio_CN.pdf
│ ├──
Rockchip_Developer_Guide_Audio_Call_3A_Algorithm_Integration_and_Parameter_Debugging_CN.pdf
│ ├── Rockchip_Developer_Guide_Audio_CN.pdf
│ └── Rockchip_Developer_Guide_RK817_RK809_Codec_CN.pdf
├── camera
│ ├── common
│ │ └── Camera_External_FAQ_v1.0 .pdf
│ ├── HAL1
│ │ ├── README_CN.txt
│ │ ├── README_EN.txt
│ │ ├── RK312x_Camera_User_Manual_v1.4(3288&3368).pdf
│ │ ├── RK_ISP10_Camera_User_Manual_v2.3.pdf
│ │ ├── RKISPV1_Camera_Module_AVL_v1.7.pdf
│ │ ├── Rockchip_Camera_AVL_v2.0_Package_20180515.7z
│ │ ├── Rockchip_Introduction_RKISPV1_Camera_Driver_Debugging_Method_CN.pdf
│ │ ├── Rockchip_Introduction_RKISPV1_Camera_FAQ_CN.pdf
│ │ ├── Rockchip SOFIA 3G-R_PMB8018(x3_C3230RK)Camera_Module_AVL_v1.6_20160226.pdf
│ │ └── Rockchip_Trouble_Shooting_Android_CameraHAL1_CN_EN.pdf
│ ├── HAL3
│ │ ├── camera_engine_rkisp_user_manual_v2.2.pdf
│ │ ├── camera_hal3_user_manual_v2.3.pdf
│ │ ├── README_CN.txt
│ │ ├── RKCIF_Driver_User_Manual_v1.0.pdf
│ │ ├── RKISP1_IQ_Parameters_User_Guide_v1.2.pdf
│ │ ├── RKISP_Driver_User_Manual_v1.3.pdf
│ │ ├── Rockchip_Color_Optimization_Guide_ISP
│ │ │ ├── ISP21
│ │ │ │ └── CN
│ │ │ │ └── Rockchip_Color_Optimization_Guide_ISP21_CN_v2.0.1.pdf
│ │ │ ├── ISP30
│ │ │ │ └── CN
│ │ │ │ └── Rockchip_Color_Optimization_Guide_ISP30_CN_v3.0.0.pdf
│ │ │ └── ISP32-lite
│ │ │ └── CN
│ │ │ └── Rockchip_Color_Optimization_Guide_ISP32_Lite_CN_v3.1.0.pdf
│ │ ├── Rockchip_Development_Guide_3A_ISP
│ │ │ └── ISP30
│ │ │ └── CN
│ │ │ └── Rockchip_Development_Guide_3A_ISP30_v1.1.0.pdf
│ │ ├── Rockchip_Development_Guide_ISP
│ │ │ ├── ISP21
│ │ │ │ └── CN
│ │ │ │ └── Rockchip_Development_Guide_ISP21_CN_v2.1.0.pdf
│ │ │ ├── ISP30
│ │ │ │ └── CN
│ │ │ │ └── Rockchip_Development_Guide_ISP30_CN_v1.2.3.pdf
│ │ │ └── ISP32-lite
│ │ │ └── CN
│ │ │ └── Rockchip_Development_Guide_ISP32_Lite_CN_v1.0.0.pdf
│ │ ├── Rockchip_Driver_Guide_VI
│ │ │ ├── CN
│ │ │ │ └── Rockchip_Driver_Guide_VI_CN_v1.1.4.pdf
│ │ │ └── EN
│ │ │ └── Rockchip_Driver_Guide_VI_EN_v1.0.7.pdf
│ │ ├── Rockchip_IQ_Tools_Guide_ISP
│ │ │ ├── ISP21
│ │ │ │ └── Rockchip_IQ_Tools_Guide_ISP2x_CN_v2.0.3.pdf
│ │ │ ├── ISP30
│ │ │ │ └── Rockchip_IQ_Tools_Guide_ISP21_ISP30_CN_v2.0.4.pdf
│ │ │ └── ISP32-lite
│ │ │ └── CN
│ │ │ └── Rockchip_IQ_Tools_Guide_v2.0.7_CN.pdf
│ │ ├── Rockchip_Trouble_Shooting_CameraHAL3_CN_EN.pdf
│ │ ├── Rockchip_Tuning_Guide_ISP
│ │ │ ├── ISP21
│ │ │ │ └── CN
│ │ │ │ └── Rockchip_Tuning_Guide_ISP21_CN_v2.1.0.pdf
│ │ │ ├── ISP30
│ │ │ │ └── CN
│ │ │ │ └── Rockchip_Tuning_Guide_ISP30_CN_v1.1.0.pdf
│ │ │ └── ISP32-lite
│ │ │ └── CN
│ │ │ └── Rockchip_Tuning_Guide_ISP32-lite_CN_v1.0.0.pdf
│ │ └── USB_UVC_Integrated_Cameras.pdf
│ ├── README.txt
│ └── vehicle
│ └── Rockchip_Android_Fast_Reverse_Image_System_Developer_Guide_CN_V1.0.3.pdf
├── Can
│ ├── Rockchip_Developer_Guide_Can_CN.pdf
│ └── Rockchip_Developer_Guide_CAN_FD_CN.pdf
├── CLK
│ ├── Rockchip_Developer_Guide_Clock_CN.pdf
│ ├── Rockchip_Developer_Guide_Gpio_Output_Clocks_CN.pdf
│ ├── Rockchip_Develop_Guide_Pll_Ssmod_Clock_CN.pdf
│ └── Rockchip_RK3399_Developer_Guide_Clock_CN.pdf
├── CRU
│ ├── Rockchip_Developer_Guide_Linux3.10_Clock_CN.pdf
│ ├── Rockchip_Developer_Guide_Linux4.4_4.19_Clock_CN.pdf
│ ├── Rockchip_Develop_Guide_Pll_Ssmod_Clock_CN.pdf
│ ├── Rockchip_RK3399_Developer_Guide_Clock_CN.pdf
│ └── Rockchip_RK3399_Developer_Guide_Linux4.4_Clock_CN.pdf
├── CRYPTO
│ ├── Rockchip_Developer_Guide_Crypto_HWRNG_CN.pdf
│ └── Rockchip_Developer_Guide_Crypto_HWRNG_EN.pdf
├── DDR
│ ├── DDR_bandwidth_statistics_tool
│ │ ├── rk-msch-probe-for-user-32bit
│ │ ├── rk-msch-probe-for-user-64bit
│ │ └── Rockchip_Introduction_DDR_Bandwidth_Tool_CN.pdf
│ ├── Rockchip-Developer-Guide-DDR-CN.pdf
│ ├── Rockchip-Developer-Guide-DDR-EN.pdf
│ ├── Rockchip-Developer-Guide-DDR-Problem-Solution-CN.pdf
│ ├── Rockchip-Developer-Guide-DDR-Problem-Solution-EN.pdf
│ ├── Rockchip-Developer-Guide-DDR-Verification-Process-CN.pdf
│ ├── Rockchip_Developer_Guide_DDR_Verification_Process_EN.pdf
│ ├── Rockchip_Developer_Guide_HAL_DDR_ECC_CN.pdf
│ └── Rockchip-User-Guide-DDR-DQ-Eye-Tool-CN.pdf
├── debug
│ ├── RK3399-LOG-EXPLANATION.pdf
│ ├── Rockchip_Developer_Guide_DS5_CN.pdf
│ ├── Rockchip_Quick_Start_Linux_Perf.pdf
│ ├── Rockchip_Quick_Start_Linux_Streamline.pdf
│ ├── Rockchip_Quick_Start_Linux_Systrace.pdf
│ ├── Rockchip_RK3399_JTAG_Configuration_CN.pdf
│ └── Rockchip_User_Guide_J-Link_CN.pdf
├── display
│ ├── Rockchip_BT656_TX_AND_BT1120_TX_Developer_Guide_CN.pdf
│ ├── Rockchip_Developer_Guide_Baseparameter_Format_Define_And_Use_CN.pdf
│ ├── Rockchip_Developer_Guide_DRM_Display_Driver_CN.pdf
│ ├── Rockchip_Developer_Guide_DRM_Panel_Porting_CN&EN.pdf
│ ├── Rockchip_Developer_Guide_DRM_Panel_Porting_CN.pdf
│ ├── Rockchip_Developer_Guide_Dual_Display_Rotation_Direction_Debugging_CN.pdf
│ ├── Rockchip_Developer_Guide_HDMI_Based_on_DRM_Framework_CN&EN.pdf
│ ├── Rockchip_Developer_Guide_HDMI-CEC_CN.pdf
│ ├── Rockchip_Developer_Guide_HDMI_CN.pdf
│ ├── Rockchip_Develop_Guide_DRM_Direct_Show_CN.pdf
│ ├── Rockchip_Display_Issues_FAQ_V1.1.pdf
│ ├── Rockchip_DRM_RK628_Porting_Guide_CN.pdf
│ ├── Rockchip FAQ DRM Hardware Composer V1.00-20181213.pdf
│ ├── Rockchip_Introduction_DisplayAdjust_APK_CN.pdf
│ ├── Rockchip_Introduction_DRM_Integration_Helper_CN.pdf
│ ├── Rockchip_RK3588_Developer_Guide_DisplayPort_CN.pdf
│ ├── Rockchip_RK3588_Developer_Guide_MIPI_DSI2_CN.pdf
│ ├── Rockchip_RK3588_Developer_Guide_Vsync_Adjust_CN.pdf
│ ├── Rockchip_RK3588_User_Guide_DP_CN.pdf
│ ├── Rockchip_RK3588_User_Guide_eDP_CN.pdf
│ └── Rockchip_Trouble_Shooting_Graphics
├── DVFS
│ ├── Rockchip_Developer_Guide_CPUFreq_CN.pdf
│ ├── Rockchip_Developer_Guide_CPUFreq_EN.pdf
│ ├── Rockchip_Developer_Guide_Devfreq_CN.pdf
│ ├── Rockchip_Developer_Guide_Devfreq_EN.pdf
│ ├── Rockchip_Developer_Guide_Linux4.4_CPUFreq_CN.pdf
│ └── Rockchip_Developer_Guide_Linux4.4_Devfreq_CN.pdf
├── Ebook
│ ├── Rockchip_RK3566_Introduction_EBOOK_Display_Mode_CN.pdf
│ └── Rockchip_RK3566_Introduction_EBOOK_Sleep_Mode_CN.pdf
├── GMAC
│ ├── Rockchip_Developer_Guide_Ethernet_CN.pdf
│ ├── Rockchip_Developer_Guide_Linux_GMAC_CN.pdf
│ ├── Rockchip_Developer_Guide_Linux_GMAC_Mode_Configuration_CN.pdf
│ ├── Rockchip_Developer_Guide_Linux_GMAC_RGMII_Delayline_CN.pdf
│ └── Rockchip_Developer_Guide_Linux_GMAC_RGMII_Delayline_EN.pdf
├── hdmi-in
│ ├── apk
│ │ ├── HdmiInDemo_based_on_CameraHal1_2020.06.11_v1.2.tar.gz
│ │ └── rkCamera2_based_on_CameraHal3_V1.3.tar.gz
│ ├── Rockchip_Developer_Guide_HDMI_IN_Based_On_CameraHal1_CN.pdf
│ ├── Rockchip_Developer_Guide_HDMI_IN_Based_On_CameraHal3_CN.pdf
│ └── Rockchip_Developer_Guide_HDMI_RX_CN.pdf
├── I2C
│ ├── Rockchip_Developer_Guide_I2C_CN.pdf
│ └── Rockchip_Developer_Guide_I2C_EN.pdf
├── IO-Domain
│ ├── Rockchip_Developer_Guide_Linux_IO_DOMAIN_CN.pdf
│ ├── Rockchip_PX30_Introduction_IO_Power_Domains_Configuration.pdf
│ ├── Rockchip_RK3288_Introduction_IO_Power_Domains_Configuration.pdf
│ ├── Rockchip_RK3326_Introduction_IO_Power_Domains_Configuration.pdf
│ ├── Rockchip_RK3399_Introduction_IO_Power_Domains_Configuration.pdf
│ ├── Rockchip_RK3399Pro_Introduction_IO_Power_Domains_Configuration.pdf
│ └── Rockchip_RK356X_Introduction_IO_Power_Domains_Configuration.pdf
├── IOMMU
│ ├── Rockchip_Developer_Guide_Linux_IOMMU_CN.pdf
│ └── Rockchip_Developer_Guide_Linux_IOMMU_EN.pdf
├── Leds
│ └── Rockchip_Introduction_Leds_GPIO_Configuration_for_Linux4.4_CN.pdf
├── MCU
│ ├── Rockchip_RK3399_Developer_Guide_MCU_CN.pdf
│ └── Rockchip_RK3399_Developer_Guide_MCU_EN.pdf
├── Memory
│ └── Rockchip_Developer_Guide_Linux_CMA_CN.pdf
├── MMC
│ ├── Rockchip_Developer_Guide_SD_Boot_CN.pdf
│ └── Rockchip_Developer_Guide_SDMMC_SDIO_eMMC_CN.pdf
├── mobile-net
│ ├── Rockchip_Introduction_3G_Data_Card_USB_File_Conversion_CN.pdf
│ ├── Rockchip_Introduction_3G_Dongle_Configuration_CN&EN.pdf
│ └── Rockchip_Introduction_4G_Module_Configuration_CN&EN.pdf
├── MPP
│ ├── Rockchip_Developer_Guide_MPP_CN.pdf
│ └── Rockchip_Developer_Guide_MPP_EN.pdf
├── NVM
│ ├── Rockchip_Application_Notes_Storage_CN.pdf
│ ├── Rockchip_Developer_FAQ_Storage_CN.pdf
│ ├── Rockchip_Developer_Guide_OTP_CN.pdf
│ ├── Rockchip_Developer_Guide_OTP_EN.pdf
│ ├── Rockchip_Developer_Guide_SATA_CN.pdf
│ ├── Rockchip_Introduction_Partition_CN.pdf
│ ├── Rockchip_Introduction_Partition_EN.pdf
│ └── Rockchip_RK356X_Developer_Guide_SATA_CN.pdf
├── PCie
│ ├── Rockchip-Developer-Guide-linux4.4-PCIe.pdf
│ ├── Rockchip_Developer_Guide_PCIe_CN.pdf
│ ├── Rockchip_PCIe_Virtualization_Developer_Guide_CN.pdf
│ └── Rockchip_RK3399_Developer_Guide_PCIe_CN.pdf
├── perf
│ ├── perf使用说明.pdf
│ ├── Rockchip_Developer_FAQ_FileSystem_CN.pdf
│ ├── Rockchip_Optimize_Tutorial_Linux_IO_CN.pdf
│ ├── Rockchip_Quick_Start_Linux_Performance_Analyse_CN.pdf
│ └── systrace使用说明.pdf
├── PIN-Ctrl
│ ├── Rockchip_Developer_Guide_Linux_Pinctrl_CN.pdf
│ └── Rockchip_Developer_Guide_Linux_Pinctrl_EN.pdf
├── PMIC
│ ├── Rockchip_Developer_Guide_FreeRTOS_PMIC_CHARGER_POWERKEY_CN.pdf
│ ├── Rockchip_Developer_Guide_Power_Discrete_DCDC_EN.pdf
│ ├── Rockchip_Developer_Guide_RK817_RK809_Fuel_Gauge_CN&EN.pdf
│ ├── Rockchip_RK805_Developer_Guide_CN.pdf
│ ├── Rockchip_RK806_Developer_Guide_CN.pdf
│ ├── Rockchip_RK808_Developer_Guide_CN.pdf
│ ├── Rockchip_RK809_Developer_Guide_CN.pdf
│ ├── Rockchip_RK816_Developer_Guide_CN.pdf
│ ├── Rockchip_RK817_Developer_Guide_CN.pdf
│ ├── Rockchip_RK818_Developer_Guide_CN.pdf
│ ├── Rockchip_RK818_RK816_Developer_Guide_Fuel_Gauge_CN.pdf
│ └── Rockchip_RK818_RK816_Introduction_Fuel_Gauge_Log_CN.pdf
├── power
│ ├── Rockchip_Developer_Guide_Power_Analysis_EN.pdf
│ └── Rockchip_Developer_Guide_Sleep_and_Resume_CN.pdf
├── PWM
│ ├── Rockchip_Developer_Guide_Linux_PWM_CN.pdf
│ ├── Rockchip_Developer_Guide_Linux_PWM_EN.pdf
│ └── Rockchip_Developer_Guide_PWM_IR_CN.pdf
├── RGA
│ ├── Rockchip_Developer_Guide_RGA_CN.pdf
│ ├── Rockchip_Developer_Guide_RGA_EN.pdf
│ ├── Rockchip_FAQ_RGA_CN.pdf
│ └── Rockchip_FAQ_RGA_EN.pdf
├── RK628
│ ├── Rockchip_RK628D_Application_Notes_CN.pdf
│ └── Rockchip_RK628D_For_All_Porting_Guide_CN.pdf
├── RKTools manuals
│ ├── RKIQTool_User_Manual_v1.5-CH.pdf
│ ├── RKIQTool_User_Manual_v1.5-EN.pdf
│ ├── RK_Platform_apache_tomcat_ota_Server_Setup_Introduction.rar
│ ├── Rockchip_Box_Factory_Test_Tool_V2.0.rar
│ ├── Rockchip_Developer_Guide_Linux_Nand_Flash_Open_Source_Solution_CN.pdf
│ ├── Rockchip_Introduction_Image_Upgrading_Failure_Analysis_CN.pdf
│ ├── Rockchip_Introduction_MP_Tool_Upgrading_and_Related_Issues_Debugging_CN.pdf
│ ├── Rockchip_Introduction_REPO_Mirror_Server_Build_and_Management_CN.pdf
│ ├── Rockchip_Introduction_Stresstest_for_VR_CN.pdf
│ ├── Rockchip_Introduction_WNpctool_Write_Tool_CN.pdf
│ ├── Rockchip_User_Guide_Box_Factory_Test_Tool_CN.pdf
│ ├── Rockchip_User_Guide_Keybox_Burning_EN.pdf
│ ├── Rockchip_User_Guide_KeyWrite_CN.pdf
│ ├── Rockchip_User_Guide_MP_Flashing_v1.2_CN.pdf
│ ├── Rockchip_User_Guide_Production_For_Firmware_Download_CN.pdf
│ ├── Rockchip_User_Guide_RKDevInfoWriteTool_CN.pdf
│ ├── Rockchip_User_Guide_RKDevInfoWriteTool_EN.pdf
│ ├── Rockchip_User_Guide_RK_Platform_MP_Upgrading_CN.pdf
│ ├── Rockchip_User_Manual_Android_Development_Tool_CN.pdf
│ ├── Rockchip_User_Manual_RKIQTool_CN.pdf
│ ├── Rockchip_User_Manual_RKIQTool_EN.pdf
│ ├── Rockchip_User_Manual_RKUpgrade_Dll_CN.pdf
│ └── SecureBootTool_UserManual.pdf
├── SARADC
│ ├── Rockchip_Developer_Guide_Linux_SARADC_CN.pdf
│ └── Rockchip_Developer_Guide_Linux_SARADC_EN.pdf
├── security
│ ├── patch
│ │ └── u-boot
│ │ └── 0001-avb-add-embedded-key.patch
│ ├── RK3399_Efuse_Operation_Instructions_V1.00_EN.pdf
│ ├── RK356X_SecurityBoot_And_AVB_instructions_CN.pdf
│ ├── RK356X_SecurityBoot_And_AVB_instructions_EN.pdf
│ ├── RK3588_SecurityBoot_And_AVB_instructions_CN.pdf
│ ├── RK3588_SecurityBoot_And_AVB_instructions_EN.pdf
│ ├── Rockchip_Developer_Guide_Crypto_HWRNG_CN.pdf
│ ├── Rockchip_Developer_Guide_Secure_Boot_Application_Note_EN.pdf
│ ├── Rockchip_Developer_Guide_Secure_Boot_for_UBoot_Next_Dev_CN.pdf
│ ├── Rockchip_Developer_Guide_Secure_Boot_for_UBoot_Next_Dev_EN.pdf
│ ├── Rockchip_Developer_Guide_TEE_SDK_CN.pdf
│ ├── Rockchip_RK3399_User_Guide_SecurityBoot_And_AVB_CN.pdf
│ └── Rockchip Vendor Storage Application Note.pdf
├── Sensors
│ └── Rockchip_Developer_Guide_Sensors_CN.pdf
├── SPI
│ ├── Rockchip_Developer_Guide_Linux_SPI_CN.pdf
│ └── Rockchip_Developer_Guide_Linux_SPI_EN.pdf
├── Thermal
│ ├── Rockchip_Developer_Guide_Thermal_CN.pdf
│ └── Rockchip_Developer_Guide_Thermal_EN.pdf
├── TRUST
│ ├── Rockchip_Developer_Guide_Trust_CN.pdf
│ ├── Rockchip_Developer_Guide_Trust_EN.pdf
│ └── Rockchip_RK3588_Developer_Guide_System_Suspend_CN.pdf
├── Tutorial
│ ├── RK3399-CPUINFO.pdf
│ ├── RK3399-LOG-EXPLANATION.pdf
│ ├── Rockchip_Developer_FAQ_FileSystem_CN.pdf
│ ├── Rockchip_Introduction_Browser_FAQ_CN.pdf
│ └── Rockchip_Trouble_Shooting_Firmware_Upgrade_Issue_CN.pdf
├── UART
│ ├── Rockchip-Developer-Guide-RT-Thread-UART.pdf
│ ├── Rockchip_Developer_Guide_UART_CN.pdf
│ ├── Rockchip_Developer_Guide_UART_EN.pdf
│ └── Rockchip_Developer_Guide_UART_FAQ_CN.pdf
├── u-boot
│ ├── Rockchip-Developer-Guide-Linux-AB-System.pdf
│ ├── Rockchip-Developer-Guide-Uboot-mmc-device-driver-analysis.pdf
│ └── Rockchip_Developer_Guide_UBoot_Nextdev_CN.pdf
├── usb
│ ├── Rockchip_Developer_Guide_Linux_USB_Initialization_Log_Analysis_CN_V1.1.1.pdf
│ ├── Rockchip_Developer_Guide_Linux_USB_Performance_Analysis_CN_V1.1.1.pdf
│ ├── Rockchip_Developer_Guide_Linux_USB_PHY_CN.pdf
│ ├── Rockchip_Developer_Guide_USB_CN.pdf
│ ├── Rockchip_Developer_Guide_USB_EN.pdf
│ ├── Rockchip_Developer_Guide_USB_FFS_Test_Demo_CN.pdf
│ ├── Rockchip_Developer_Guide_USB_FFS_Test_Demo_CN_V1.2.1.pdf
│ ├── Rockchip_Developer_Guide_USB_Gadget_UAC_CN.pdf
│ ├── Rockchip_Developer_Guide_USB_Gadget_UAC_CN_V1.1.1.pdf
│ ├── Rockchip_Developer_Guide_USB_SQ_Test_CN.pdf
│ ├── Rockchip_Introduction_USB_SQ_Tool_CN.pdf
│ ├── Rockchip_RK3399_Developer_Guide_USB_CN.pdf
│ ├── Rockchip_RK356x_Developer_Guide_USB_CN.pdf
│ ├── Rockchip_RK356X_User_Guide_USB_CN.pdf
│ ├── Rockchip_RK3588_Developer_Guide_USB_CN.pdf
│ └── Rockchip_User_Guide_USB_PHY_Tuning_CN.pdf
└── watchdog
├── Rockchip_Developer_Guide_Linux_WDT_CN.pdf
└── Rockchip_Developer_Guide_Linux_WDT_EN.pdf

Tool usage

StressTest
Use the Stresstest tool to do the stress test for the various functions on the target devices to
make sure the whole system running stably. SDK can start StressTest application and perform
stress test of various functions by entering “83991906=” code in the calculator.
The test items of Stresstest tool mainly include:

Module related

Camera stress test: including Camera on/off, Camera taking photo and Camera switch.
Bluetooth stress test: including Bluetooth on/off.
Wi-Fi stress test: including Wi-Fi on/off, (plan to add ping test and iperf test).

Non module related

Fly mode on/oﬀ test

Suspend and resume stress test
Video playing stress test
Reboot stress test
Recovery stress test
ARM frequency scaling test
GPU frequency scaling test
DDR frequency scaling test

PCBA test tool

PCBA test tool is used to help quickly identify good and bad product features during production
to improve the production eﬃciency. Current test items include panel (LCD), wireless (Wi-Fi),
Bluetooth, DDR/EMMC memory, SD card, USB HOST, key, speaker earphone (Codec).
These test items include automatic test item and manual test item. Wireless network,
DDR/EMMC, Ethernet are automatic test items, while key, SD card, USB Host, Codec are manual
test items.
For the detailed PCBA function conﬁguration and usage, please refer to:

RKDocs\android\Rockchip_Developer_Guide_PCBA_Test_Tool_CN&EN.pdf_V1.1_20171222.p
df。

DeviceTest
DeviceTest is used for the whole device test in factory, which mainly test whether the peripheral
components work normally after assembling. SDK will enter DeviceTest by entering “000.=” code
in the calculator, as shown below:

In factory, you can test the corresponding peripheral according to this interface. Click “TEST
CHECKED” to test the items one by one. If succeed, click pass, if fail, click failed, the ﬁnal result will
display on the screen, as shown below. Red means failed item, others are pass, and the factory
can repair accordingly based on the test result. Besides, if customers need to customize the tool,
please contact FAE to apply for the corresponding source code.
USB driver
Rockchip USB driver install package includes ADB and image ﬂashing driver

RKTools\windows\DriverAssitant_v5.1.1.zip

Development ﬂashing tool

Windows version

RKTools/windows/AndroidTool/AndroidTool_Release_v3.28.zip

The tool version will update time by time, please synchronize and update in time.

Linux version

RKTools/linux/Linux_Upgrade_Tool/Linux_Upgrade_Tool_v2.30.zip

Linux_Upgrade_Tool_v2.26$ sudo ./upgrade_tool -h

Program Data in /home/wlq/.config/upgrade_tool

---------------------Tool Usage ---------------------

Help: H
Quit: Q
Version: V
Clear Screen: CS
------------------Upgrade Command ------------------
ChooseDevice: CD
ListDevice: LD
SwitchDevice: SD
UpgradeFirmware: UF <Firmware> [-noreset]
UpgradeLoader: UL <Loader> [-noreset]
DownloadImage: DI <-p|-b|-k|-s|-r|-m|-u|-t|-re image>
DownloadBoot: DB <Loader>
EraseFlash: EF <Loader|firmware> [DirectLBA]
PartitionList: PL
WriteSN: SN <serial number>
ReadSN: RSN
----------------Professional Command -----------------
TestDevice: TD
ResetDevice: RD [subcode]
ResetPipe: RP [pipe]
ReadCapability: RCB
ReadFlashID: RID
ReadFlashInfo: RFI
ReadChipInfo: RCI
ReadSector: RS <BeginSec> <SectorLen> [-decode] [File]
WriteSector: WS <BeginSec> <File>
ReadLBA: RL <BeginSec> <SectorLen> [File]
WriteLBA: WL <BeginSec> <File>
EraseLBA: EL <BeginSec> <EraseCount>
EraseBlock: EB <CS> <BeginBlock> <BlokcLen> [--Force]
-------------------------------------------------------

Tool to implement SD upgrading and boot

It is used to implement SD card upgrading, SD card boot, SD card PCBA test.

RKTools\windows\SDDiskTool_v1.74.zip

Write SN tool
RKTools\windows\RKDevInfoWriteTool-1.3.0.7z
Install after unzip RKDevInfoWriteTool-1.3.0.7z
Use admin ID to open the software

For the tool instruction, please refer to:

RKDocs\common\RKTools manuals\Rockchip_User_Guide_RKDevInfoWriteTool_CN.pdf

DDR welding test tool

It is used to test DDR hardware conncection, troubleshooting hardware issues such as virtual
welding.

RKTools\windows\Rockchip_Platform_DDR_Test_Tool_V1.38_Release_Annoucement_CN.7z
RKTools\windows\Rockchip_Platform_DDR_Test_Tool_V1.38_Release_Annoucement_EN.7z

efuse ﬂashing tool

It is used to ﬂash efuse, suitable for RK3288W/RK3368/RK3399 platforms.

RKTools\windows\efuse_v1.37.rar

efuse/otp sign tool

It is used to sign efuse/otp of image.

RKTools\windows\SecureBootTool_v1.94.zip

Factory production image ﬂashing tool

It is uesed for batch image ﬂashing in factory.

RKTools\windows\FactoryTool-1.72.9.7z

userdata partition data prebuilt tool

It is the tool used to make userdata partition pre-built data package.

RKTools\windows\OemTool_v1.3.rar

Camera IQ Tool
It is used for debugging ISP image eﬀects.

external/camera_engine_rkaiq/rkisp2x_tuner

System debugging

ADB tool

Overview
ADB (Android Debug Bridge) is a tool in Android SDK which can be used to operate and manage
Android simulator or the real Android device. The functions mainly include:

Run the device shell (command line)

Manage the port mapping of the simulator or the device
Upload/download ﬁles between the computer and the device
Install the local apk to simulator or Android device
ADB is a “client – server” program. Usually the client is PC and the server is the actual
Android device or simulator. The ADB can be divided into two categories according to the
way PC connects to the Android device:
Network ADB: PC connects to STB device through cable/wireless network.
USB ADB: PC connects to STB device through USB cable.

USB adb usage

USB adb usage has the following limitations:

Only support USB OTG port

Not support multiple clients at the same time (such as cmd window, eclipse etc.)
Support host connects to only one device but not multiple devices
The connection steps are as below:
1、The device already running Android system, setting -> developer option -> connect to the
computer, enable usb debugging switch.
2、PC connects to the device USB otg port only through USB cable, and then the computer
connects with Android device through below command:

adb shell

3、Execute the command ”adb devices” to see if the connection is successful or not. If the device
serial number shows up, the connection is successful.
ADB commonly used command elaboration
（1）Check the device situation
Check the Android device or simulator connected to computer:

adb devices

The return result is the serial number or IP and port number, status of the Android device
connected to PC.
（2）Install APK
Install the speciﬁc apk ﬁle to the device:

adb install <apk file path>

For example:

adb install “F:\WishTV\WishTV.apk”

Re-install application:

adb install –r “F:\WishTV\WishTV.apk”

（3）Uninstall APK
Complete uninstall:

adb uninstall <package>

For example:

adb uninstall com.wishtv

（4）Use rm to remove apk ﬁle:

adb shell rm <filepath>

For example:

adb shell rm “system/app/WishTV.apk”

Note: remove “WishTV.apk” ﬁle in the directory of “system/app”.

（5）Enter shell of the device and simulator
Enthe the shell environment of the device or simulator:

adb shell

（6）Upload the ﬁle to the device from PC

Use push command can upload any ﬁle or folder from PC to the device. Generally local path
means the computer and remote path means the single board device connected with ADB.
adb push
For example:
adb push “F:\WishTV\WishTV.apk” “system/app”

Note: upload local “WishTV.apk” file to the “system/app” directory of the Android system.
（7）Download the file from the device to PC
Use pull command can download the file or folder from the device to local computer.

adb pull <remote path> <local path>

For example:

adb pull system/app/Contacts.apk F:\

Note: download the ﬁle or folder from the “system/app” directory of Android system to local “F:\”
directory.
（8）Check bug report
Run adb bugreport command can check all the error message report generated by system. The
command will show all dumpsys, dumpstate and logcat information of the Android system.
（9）Check the device system information
The speciﬁc commands in adb shell to check the device system information.

adb shell getprop

Logcat tool
Android logcat system provides the function to record and check the system debugging
information. The logcats are all recorded from various softwares and some system buffer. The
buffer can be checked and used through Logcat. Logcat is the function most commonly used by
debugging program. The function shows the program running status mainly by printing logcat.
Because the amount of logcat is very large, need to do filtering and other operations.

Logcat command usage

Use logcat command to check the contents of the system logcat buﬀer:
The basic format:

[adb] logcat [<option>] [<filter-spec>]

For example:

adb shell
logcat

The commonly used logcat ﬁlter method

Several ways to control the logcat output:

Control the logcat output priority

For example:

adb shell
logcat *:W
Note: show the logcat information with priority of warning or higher.

Control the logcat label and output priority

For example:

adb shell
logcat ActivityManager:I MyApp:D *:S

Note: support all the logcat information except those with label of “ActivityManager” and priority
of “Info” above, label of “MyApp” and priority of “Debug” above.

Only output the logcat with the speciﬁc label

For example:

adb shell
logcat WishTV:* *:S

adb shell
logcat –s WishTV

Note: only output the logcat with label of WishTV.

Only output the logcat with the speciﬁc priority and label
For example:

adb shell
logcat WishTV:I *:S

Note: only output the logcat with priority of I and label of WishTV.

Procrank tool
Procrank is a debugging tool with Android, running in the shell environment of the device, used
to output the memory snapshot of the process in order to eﬀectively observe the memory usage
status of the process.
Include the following memory information:

VSS：Virtual Set Size The memory size used by virtual (including the memory used by the
shared lib)
RSS：Resident Set Size The actually used physical memory size (including the memory used
by the shared lib)
PSS：Proportional Set Size The actually used physical memory size (allocate the memory
used by the shared lib in proportion)
USS：Unique Set Size The physical memory used exclusively by the process (not including
the memory used by the shared lib)
Note:
USS size represents the memory size only used by the process, and it will be completely
recovered after the process is killed.
VSS/RSS includes the memory used by the shared lib, so it is not helpful to check the
memory status of the single process.
PSS is the shared memory status used by the speciﬁc single process after the shared
memory is allocated in proportion.
Use procrank

Make sure the terminal has the root authority before executing procrank
su
The command format:

procrank [ -W ] [ -v | -r | -p | -u | -h ]

The commonly used command instructions:

-v：order by VSS
-r：order by RSS
-p：order by PSS
-u：order by USS
-R：convert to order by increasing[decreasing] method
-w：only display the statistical count of working set
-W：reset the statistical count of working set
-h：help
For example:
Output the memory snapshot:

procrank

Output the memory snapshot in VSS decreasing order:

procrank –v

Procrank is output in PSS order by default.

Search the speciﬁc content information

Use below command format to view the memory status of the speciﬁc process:

procrank | grep [cmdline | PID]

cmdline means the target application name, PID means the target application process.
Output the memory status used by systemUI process:

procrank | grep “com.android.systemui”

or:

procrank | grep 3396

Trace the process memory status

Analyze if there is memory leakage in the process by tracing the memory usage status. Use the
script to continuously output the process memory snapshot, and compare with USS segment to
see if there is memory leakage in this process.
For example: output the application memory usage of the process named com.android.systemui
to see if there is leakage:
1、Write the script test.sh
#!/bin/bash
while true;do
adb shell procrank | grep “com.android.systemui”
sleep 1
done

2、After connect to the device by adb tool, run the script: ./test.sh

Dumpsys tool
Dumpsys tool is a debugging tool in Android system, running in the shell environment of the
device, and provides the service status information running in the system. The running service
means the service process in the Android binder mechanism.
The conditions for dumpsys to output the print:
1、Only print the services already loaded to ServiceManager.
2、If the dump function in the service code is not implemented, there will be no information
output.

Use Dumpsys

View Dumpsys help

Function: output dympsys help information.

dumpsys -help

View the service list of Dumpsys

Function: output all the printable service information of dumpsys, developer can pay
attention to the service names required for debugging.

dumpsys -l

Output the speciﬁc service information

Function: output the speciﬁc service dump information.
Format: dumpsys [servicename]
For example: execute below command can output the service information of SurfaceFlinger:

dumpsys SurfaceFlinger

Output the speciﬁc service and application process information

Function: output the speciﬁc service and application process information.
Format: dumpsys [servicename] [application name]
For example: execute below command to output the memory information for the service
named meminfo and process named com.android.systemui:

dumpsys meminfo com.android.systemui

Note: the service name is case sensitive and must input the full service name.

Last log enable

Add the following two nodes in dts ﬁle
ramoops_mem: ramoops_mem {
reg = <0x0 0x110000 0x0 0xf0000>;
reg-names = "ramoops_mem";
};

ramoops {
compatible = "ramoops";
record-size = <0x0 0x20000>;
console-size = <0x0 0x80000>;
ftrace-size = <0x0 0x00000>;
pmsg-size = <0x0 0x50000>;
memory-region = <&ramoops_mem>;
};

- Check last log in the device

130|root@rk3399:/sys/fs/pstore # ls
dmesg-ramoops-0 Log saved after last kernel panic
pmsg-ramoops-0 Log of last user space, android log
ftrace-ramoops-0 Print function trace during some period
console-ramoops-0 kernel log when last_log was enabled last time, but only save
the log with higher priority than default log level

Usage:

cat dmesg-ramoops-0
cat console-ramoops-0
logcat -L （pmsg-ramoops-0） pull out by logcat and parse
cat ftrace-ramoops-0

FIQ mode
You can input ﬁq command through the serial port to check the system status when the device
crashes or gets stuck. The speciﬁc command is as below:

127|console:/ $ fiq
debug> help
FIQ Debugger commands:
pc PC status
regs Register dump
allregs Extended Register dump
bt Stack trace
reboot [<c>] Reboot with command <c>
reset [<c>] Hard reset with command <c>
irqs Interupt status
kmsg Kernel log
version Kernel version
sleep Allow sleep while in FIQ
nosleep Disable sleep while in FIQ
console Switch terminal to console
cpu Current CPU
cpu <number> Switch to CPU<number>
ps Process list
sysrq sysrq options
sysrq <param> Execute sysrq with <param>
Common issues
What is current kernel version and u-boot version?

The corresponding kernel version of Android14.0 is: 6.1, u-boot branch is next-
dev branch

How to acquire the corresponding RK release

version for current SDK
Rockchip Android14.0 SDK includes AOSP source code and RK changed code. RK changed libs are
involved in xml under the directory .repo/manifests/include , while AOSP default libs are in
.repo/manifests/default.xml 。
Version conﬁrm:

RK modiﬁcation part

vim .repo/manifests/include/rk_checkout_from_aosp.xml
<project groups="pdk" name="platform/build" path="build/make" remote="rk"
revision="refs/tags/android-14.0-mid-rkr1">

Means RK version is android-14.0-mid-rkr1

AOSP part

vim .repo/manifests/default.xml
<default revision="refs/tags/android-14.0.0_r11"...>

Means OASP version is android-14.0.0_r11

Just provide the above two version information when needed.
You can directly acquire tag information through the following command for single lib:

kernel-6.1$ git tag

android-14.0-mid-rkr1

RK version is incremental with the format of android-14.0-mid-rkrxx, so current latest tag is

android-14.0-mid-rkr1

How to conﬁrm if local SDK is already updated to

the latest SDK version released by RK
When RK SDK is released, the commit information corresponding to the version will be submited
under the .repo/manifests/commit/ directory. Customers can conﬁrm whether SDK is updated
completely or not by comparing with the commit information. The speciﬁc operations are as
follows:

First conﬁrm RK version of SDK according to the instruction of "How to acquire the
corresponding RK release version for current SDK". Below take RKR6 version as example to
introduce.
Use the following command to save local commit information
.repo/repo/repo manifest -r -o release_manifest_rkr1_local.xml

Comparing .repo/manifests/commit/commit_release_rkr1.xml with

release_manifest_rkr1_local.xml can conﬁrm whether SDK code is completely updated or
not, while .repo/manifests/commit/commit_release_rkr1.xml is the commit information
released along with RKR6 version.

Replace uboot and kernel logo picture

uboot and kernel logo are the first and second logo picture displayed during bootup, and they
can be changed according to the product requirement.
uboot logo source file: kernel-6.1/logo.bmp
kernel logo source file: kernel-6.1/logo_kernel.bmp
If need to change the picture, just use the bmp with the same name to replace, and re-compile
kernel. The compiled file is in boot.img.
Note: Logo picture size currently only supports to 8M with 8, 16, 24, 32bit bmp format.

How to modify Android system to support 64-bit

only
The Android 14 products certifying GMS and EDLA are required to be conﬁgured to support 64-bit
system only, not 32-bit one for reducing the memory usage. The detailed modiﬁcation is as
followed:(take rk3562_ugo as an example)

Modify corresponding conﬁguration in the BoardConﬁg.mk of the product directory, as followed:

diff --git a/rk3562_ugo/BoardConfig.mk b/rk3562_ugo/BoardConfig.mk

index c06433e..dc9cc50 100644
--- a/rk3562_ugo/BoardConfig.mk
+++ b/rk3562_ugo/BoardConfig.mk
@@ -18,3 +18,11 @@ PRODUCT_KERNEL_DTS := rk3562-rk817-tablet-v10
CAMERA_SUPPORT_AUTOFOCUS := true
BOARD_BUILD_GKI := true
include device/rockchip/rk3562/BoardConfig.mk
+
+DEVICE_IS_64BIT_ONLY := true
+
+TARGET_2ND_ARCH :=
+TARGET_2ND_ARCH_VARIANT :=
+TARGET_2ND_CPU_ABI :=
+TARGET_2ND_CPU_ABI2 :=
+TARGET_2ND_CPU_VARIANT :=

Power oﬀ charging and low battery precharging

Power oﬀ charging and low battery precharging can be conﬁgured in dts, as shown below:
charge-animation {
compatible = "rockchip,uboot-charge";
rockchip,uboot-charge-on = <1>;
rockchip,android-charge-on = <0>;
rockchip,uboot-low-power-voltage = <3400>;
rockchip,screen-on-voltage = <3500>;
status = "okay";
};

Note:
rockchip,uboot-charge-on: uboot power off charging is mutually exclusive with android power off
charging
rockchip,android-charge-on: android power off charging is mutually exclusive with uboot power
off charging
rockchip,uboot-low-power-voltage: configure the voltage for low battery precharging to boot, it
can be configured according to the actual requirement
rockchip,screen-on-voltage: configure the voltage for low battery precharging to light the panel, it
can be configured according to the actual requirement

Uboot charging logo package and replace

Charging logo path, you can directly replace with the ﬁle with the same name, and the format
should be the same as original ﬁle.

u-boot/tools/images/
├── battery_0.bmp
├── battery_1.bmp
├── battery_2.bmp
├── battery_3.bmp
├── battery_4.bmp
├── battery_5.bmp
└── battery_fail.bmp

If uboot charging is enabled, but there is no charging logo displaed, maybe it is because the
picture is not packaged into resource.img. You can package per the following command:

cd u-boot
./scripts/pack_resource.sh ../kernel-6.1/resource.img
cp resource.img ../kernel/resource.img

After executing the above command, uboot charging logo will be packaged into resource.img in
kernel directory. Now need to re-package resource.img into boot.img. You can execute
./mkiamge.sh in android root directory, and then ﬂash boot.img under rockdev/.

HDMI IN conﬁguration
hdmi in function is disabled in SDK by default. If need to enable, operate as below:

vim device/rockchip/rk3588/BoardConfig.mk
+BOARD_HDMI_IN_SUPPORT := true

RM310 4G conﬁguration
4G function is disabled in SDK by default. If need to enable, operate as below:

vim device/rockchip/common/BoardConfig.mk
#for rk 4g modem
-BOARD_HAS_RK_4G_MODEM ?= false
+BOARD_HAS_RK_4G_MODEM ?= true

WIFI Sleep Policy conﬁguration

WIFI sleep policy is to keep sleep connecting, if you need to disconnect the sleep, please refer to
the following:

---
a/rk3566_rgo/overlay/frameworks/base/packages/SettingsProvider/res/values/defaul
ts.xml
+++
b/rk3566_rgo/overlay/frameworks/base/packages/SettingsProvider/res/values/defaul
ts.xml
@@ -24,5 +24,5 @@
You can configure persist.wifi.sleep.delay.ms to delay closing wifi.
The default is 15 minutes, 0 means that the wifi is turned off
immediately after the screen is off. -->
- <integer name="def_wifi_sleep_policy">2</integer>
+ <integer name="def_wifi_sleep_policy">0</integer>
</resources>

Recovery rotation conﬁguration

Support Recovery rotation with 0/90/180/270 degree. Disabled by default（that is to rotate 0
degree）. The rotation conﬁguration is described as below:

vim device/rockchip/common/BoardConfig.mk
#0: ROTATION_NONE rotate 0 degree
#90: ROTATION_RIGHT rotate 90 degrees
#180: ROTATION_DOWN rotate 180 degrees
#270: ROTATION_LEFT rotate 270 degrees
# For Recovery Rotation
TARGET_RECOVERY_DEFAULT_ROTATION ?= ROTATION_NONE

Android Surface rotation

For Android system display rotation, you can modify the following conﬁguration with the
parameters 0/90/180/270

# For Surface Flinger Rotation

SF_PRIMARY_DISPLAY_ORIENTATION ?= 0

Replace some remote of AOSP source code

The speed for customer to download RK release code is relatively slow. You can change the
remote of AOSP to domestic mirror source, or Google mirror source for foreign customers, to
improve the downloading speed. The detailed method is described as below:
After executing repo init (or unpacking base package), modify .repo/manifests/remote.xml.
Change the remote fetch of AOSP from

< remote name="aosp" fetch="./" review="https://10.10.10.29" />

to
for domestic customers: (here we take Tsinghua university mirror source as example. You can
change to other domestic mirror source)

< remote name="aosp" fetch="https://aosp.tuna.tsinghua.edu.cn" />;

for foreign customers: (Google mirror source)

< remote name="aosp" fetch="https://android.googlesource.com" />

Data area read and write performance optimization

For devices with batteries, advised to add ‘fsync_mode=nobarrier’ to the data partition mounting
parameter of fstab to improve storage read/write rates and performance. This parameter may
cause data damage on devices without batteries. Therefore, it is not recommended to add this
parameter to devices without batteries. Modiﬁed patches as follows:

cd device/rockchip/common

diff --git a/scripts/fstab_tools/fstab.in b/scripts/fstab_tools/fstab.in

index 2ec6c265..c890cc84 100755
--- a/scripts/fstab_tools/fstab.in
+++ b/scripts/fstab_tools/fstab.in
@@ -23,6 +23,6 @@ ${_block_prefix}odm /odm ext4 ro,barrier=1
${_flags},first_stage_mount
# For sdmmc
/devices/platform/${_sdmmc_device}/mmc_host* auto auto defaults
voldmanaged=sdcard1:auto
# Full disk encryption has less effect on rk3326, so default to enable this.
-/dev/block/by-name/userdata /data f2fs
noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065
latemount,wait,check,fileencryption=aes-256-xts:aes-256-
cts:v2+inlinecrypt_optimized,keydirectory=/metadata/vold/metadata_encryption,quo
ta,formattable,reservedsize=128M,checkpoint=fs
+/dev/block/by-name/userdata /data f2fs
noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier
latemount,wait,check,fileencryption=aes-256-xts:aes-256-
cts:v2+inlinecrypt_optimized,keydirectory=/metadata/vold/metadata_encryption,quo
ta,formattable,reservedsize=128M,checkpoint=fs
# for ext4
#/dev/block/by-name/userdata /data ext4
discard,noatime,nosuid,nodev,noauto_da_alloc,data=ordered,user_xattr,barrier=1
latemount,wait,formattable,check,fileencryption=software,quota,reservedsize=128M
,checkpoint=block
diff --git a/scripts/fstab_tools/fstab_go.in b/scripts/fstab_tools/fstab_go.in
index 582557f2..05c7653c 100755
--- a/scripts/fstab_tools/fstab_go.in
+++ b/scripts/fstab_tools/fstab_go.in
@@ -17,6 +17,6 @@ ${_block_prefix}odm /odm ext4 ro,barrier=1
${_flags},first_stage_mount
# For sdmmc
/devices/platform/${_sdmmc_device}/mmc_host* auto auto defaults
voldmanaged=sdcard1:auto
# Full disk encryption has less effect on rk3326, so default to enable this.
-/dev/block/by-name/userdata /data f2fs
noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065
latemount,wait,check,fileencryption=aes-256-xts:aes-256-
cts:v2+inlinecrypt_optimized,keydirectory=/metadata/vold/metadata_encryption,quo
ta,formattable,reservedsize=128M,checkpoint=fs
+/dev/block/by-name/userdata /data f2fs
noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065i,fsync_mode=nobarrie
r latemount,wait,check,fileencryption=aes-256-xts:aes-256-
cts:v2+inlinecrypt_optimized,keydirectory=/metadata/vold/metadata_encryption,quo
ta,formattable,reservedsize=128M,checkpoint=fs
# for ext4
#/dev/block/by-name/userdata /data ext4
discard,noatime,nosuid,nodev,noauto_da_alloc,data=ordered,user_xattr,barrier=1
latemount,wait,formattable,check,fileencryption=software,quota,reservedsize=128M
,checkpoint=block

Change userdata partition ﬁle system to EXT4

The default file system of data partition is f2fs. Recommend to change the file system of data
partition to ext4 for the product without battery, as it can reduce the risk of data loss after
abnormal power down. The modification method is as below:
Take rk3566_r as example:

device/rockchip/common$ git diff

diff --git a/scripts/fstab_tools/fstab.in b/scripts/fstab_tools/fstab.in
index 6e78b00..a658332 100755
--- a/scripts/fstab_tools/fstab.in
+++ b/scripts/fstab_tools/fstab.in
@@ -20,6 +20,6 @@ ${_block_prefix}system_ext /system_ext ext4 ro,barrier=1
${_flags},first_stage_
# For sdmmc
/devices/platform/${_sdmmc_device}/mmc_host* auto auto defaults
voldmanaged=sdcard1:auto
# Full disk encryption has less effect on rk3326, so default to enable this.
-/dev/block/by-name/userdata /data f2fs
noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065
latemount,wait,check,fileencryption=aes-256-xts:aes-256-
cts:v2+inlinecrypt_optimized,quota,formattable,reservedsize=128M,checkpoint=fs
+#/dev/block/by-name/userdata /data f2fs
noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065
latemount,wait,check,fileencryption=aes-256-xts:aes-256-
cts:v2+inlinecrypt_optimized,quota,formattable,reservedsize=128M,checkpoint=fs
# for ext4
-#/dev/block/by-name/userdata /data ext4
discard,noatime,nosuid,nodev,noauto_da_alloc,data=ordered,user_xattr,barrier=1
latemount,wait,formattable,check,fileencryption=software,quota,reservedsize=128M
,checkpoint=block
+/dev/block/by-name/userdata /data ext4
discard,noatime,nosuid,nodev,noauto_da_alloc,data=ordered,user_xattr,barrier=1
latemount,wait,formattable,check,fileencryption=software,quota,reservedsize=128M
,checkpoint=block

device/rockchip/rk356x$ git diff

diff --git a/rk3566_r/recovery.fstab b/rk3566_r/recovery.fstab
index 7532217..cf789ac 100755
--- a/rk3566_r/recovery.fstab
+++ b/rk3566_r/recovery.fstab
@@ -7,7 +7,7 @@
/dev/block/by-name/odm /odm ext4
defaults defaults
/dev/block/by-name/cache /cache ext4
defaults defaults
/dev/block/by-name/metadata /metadata ext4
defaults defaults
-/dev/block/by-name/userdata /data f2fs
defaults defaults
+/dev/block/by-name/userdata /data ext4
defaults defaults
/dev/block/by-name/cust /cust ext4
defaults defaults
/dev/block/by-name/custom /custom ext4
defaults defaults
/dev/block/by-name/radical_update /radical_update ext4
defaults defaults

Modify power on/oﬀ animation and tones

Reference document:

RKDocs\android\Rockchip_Introduction_Android_Power_On_Off_Animation_and_Tone_Cus
tomization_CN&EN.pdf

APP performance mode setting

Configure the file: package_performance.xml in device/rockchip/rk3xxx/. Add the package names
which need to use performance mode in the node:（use aapt dump badging (file_path.apk) to
acquire the package name）

< app package="package name" mode="whether to enable the acceleration, 1 for

enable, 0 for disable"/>

Take antutu as example as below:

< app package="com.antutu.ABenchMark"mode="1"/>

< app package="com.antutu.benchmark.full"mode="1"\/>
< app package="com.antutu.benchmark.full"mode="1"\/>

It will package the ﬁle into the image when compiling.

Debugging method of GPU related issues
You can do the initial debugging for the issues referring to the following documents.

RKDocs\android\Rockchip_User_Guide_Dr.G_CN&EN.pdf

OTP and efuse instruction

OTP support chipset

RK3326
PX30
RK3566
RK3568
RK3588
RK3568S
EFUSE support chipset
RK3288
RK3368
RK3399
Refer to the document for image signing and otp/efuse ﬂashing:

RKDocs\common\security\Rockchip-Secure-Boot-Application-Note-V1.9.pdf

How to judge from the code whether OTP/EFUSE of

the device is already ﬂashed or not
The status of OTP/EFUSE will be transmitted through kernel cmdline and fuse.programmed in
cmdline is used to mark the status of OTP/EFUSE. The details are as follows:

"fuse.programmed=1": the software image package is already signed by secure-boot and

efuse/otp of the hardware device is already ﬂashed.
"fuse.programmed=0": the software image package is already signed by secure-boot but
efuse/otp of the hardware device is not ﬂashed.
there is no fuse.programmed in cmdline: the software image package is not signed by
secure-boot (Miniloader doesn't tramsmit), or Miniloader is too old to support transmission.

Enable/disable selinux
Refer to the following modiﬁcation, false to disable, true to enable

device/rockchip/common$
--- a/BoardConfig.mk
+++ b/BoardConfig.mk
@@ -67,7 +67,7 @@ endif

# Enable android verified boot 2.0

BOARD_AVB_ENABLE ?= false
-BOARD_SELINUX_ENFORCING ?= false
+BOARD_SELINUX_ENFORCING ?= true
Warning “There's an internal problem with your
device.” pops up after boot up
There are two reasons to pop up the warning:

1. Image mismatch, the ﬁngerprints of system/boot/vendor are not consistent.

2. The device is enabled with a conﬁguration that supports IO debugging. This problem can be
solved by using the previous compile kernel command in the documentation.
3. For projects with IO debugging, regardless of the above two reasons, please merge the
following patches directly to eliminate the warning:

diff --git
a/services/core/java/com/android/server/wm/ActivityTaskManagerService.java
b/services/core/java/com/android/server/wm/ActivityTaskManagerService.java
index 595c340..d4e495a 100644
---
a/services/core/java/com/android/server/wm/ActivityTaskManagerService.java
+++
b/services/core/java/com/android/server/wm/ActivityTaskManagerService.java
@@ -6555,7 +6555,7 @@ public class ActivityTaskManagerService extends
IActivityTaskManager.Stub {
} catch (RemoteException e) {
}

- if (!Build.isBuildConsistent()) {
+ if (0 && !Build.isBuildConsistent()) {
Slog.e(TAG, "Build fingerprint is not consistent, warning
user");
mUiHandler.post(() -> {
if (mShowDialogs) {

How to enable the setting options for Ethernet in

Settings
There is no default option of Ethernet setting in the system Settings. If Ethernet is needed in the
project, it can be turned on as follows:

--- a/BoardConfig.mk
+++ b/BoardConfig.mk
@@ -146,3 +146,6 @@ endif
ifeq ($(strip $(BOARD_USES_AB_IMAGE)), true)
DEVICE_MANIFEST_FILE :=
device/rockchip/$(TARGET_BOARD_PLATFORM)/manifest_ab.xml
endif

+# for ethernet
+BOARD_HS_ETHERNET := true

About AVB and security boot

For AVB and security boot related instruction and conﬁgurations, you can refer to the document
RKDocs/common/security/RK356X_SecurityBoot_And_AVB_instructions_CN.pdf

Cannot use IO commands

IO commands rely on DEVMEM which is disabled by default, so it is not able to use IO by default.
If need to use IO commands for debugging, you can modify as follows:

wlq@ubuntu:~/rk3562_Android14.0/$ vim mkcombinedroot/configs/android-14.config

For GO produts, need to modify:

wlq@ubuntu:~/rk3562_Android14.0$ vim mkcombinedroot/configs/android-14-go.config

delete the following line:

# CONFIG_DEVMEM is not set

If you want to compile Android, you also need to modify the following code

cd rk3562_Android14.0/kernel/configs

diff --git a/android-6.1/android-base.config b/android-6.1/android-base.config

index 5de76f0..6dcdf86 100644
--- a/android-6.1/android-base.config
+++ b/android-6.1/android-base.config
@@ -2,7 +2,6 @@
# CONFIG_ANDROID_LOW_MEMORY_KILLER is not set
# CONFIG_ANDROID_PARANOID_NETWORK is not set
# CONFIG_BPFILTER is not set
-# CONFIG_DEVMEM is not set
# CONFIG_FHANDLE is not set
# CONFIG_FW_CACHE is not set
# CONFIG_IP6_NF_NAT is not set
wlq@sys2206:~/rk3562_Android14.0/kernel/configs$ git diff
diff --git a/u/android-6.1/android-base.config b/u/android-6.1/android-
base.config
index 29b9e98..c1b21cf 100644
--- a/u/android-6.1/android-base.config
+++ b/u/android-6.1/android-base.config
@@ -2,7 +2,6 @@
# CONFIG_ANDROID_LOW_MEMORY_KILLER is not set
# CONFIG_ANDROID_PARANOID_NETWORK is not set
# CONFIG_BPFILTER is not set
-# CONFIG_DEVMEM is not set
# CONFIG_FHANDLE is not set
# CONFIG_FW_CACHE is not set
# CONFIG_IP6_NF_NAT is not set

The SN command rules

The SN must begin with a letter and be no more than 14 bytes.
Failer about LZ4 when Kernel compiling
kernel compiling fail log as：

problem：
The LZ4 version of the system is too low, and the version 1.8.3 or above is required

wlq@ubuntu:~$ lz4 -v
*** LZ4 command line interface 64-bits v1.8.3, by Yann Collet ***
refusing to read from a console

solution：
copy the LZ4 compiled by Android to override the LZ4 of the system

sudo cp out/host/linux-x86/bin/lz4 /usr/bin/lz4

Android Samba function

reference ﬁle

RKDocs/android/Rockchip_Introduction_Android_Samba_CN.pdf

NFS boot
Refer to the documents and patches:

RKDocs/android/patches/customized_functions/nfs_boot_patch_v1.1.0.zip

Update RK3528 DDR 4BIT Loader

diff --git a/RKBOOT/RK3528MINIALL.ini b/RKBOOT/RK3528MINIALL.ini
index a7e3779..6a952cf 100644
--- a/RKBOOT/RK3528MINIALL.ini
+++ b/RKBOOT/RK3528MINIALL.ini
@@ -14,7 +14,7 @@ Path1=bin/rk35/rk3528_usbplug_v1.03.bin
NUM=2
LOADER1=FlashData
LOADER2=FlashBoot
-FlashData=bin/rk35/rk3528_ddr_1056MHz_v1.05.bin
+FlashData=bin/rk35/rk3528_ddr_1056MHz_4BIT_PCB_v1.05.bin

Multi-screen display and touch

Referenced document

RKDocs\android\patches\customized_functions/Android11异显开发说明.zip

Diﬀerent screen diﬀerent sound

Referenced document

RKDocs/android/patches/customized_functions/Dual_Audio_v1.0.zip

APPENDIX A Compiling and

development environment setup
Initializing a Build Environment
This section describes how to set up your local work environment to build the Android source
files. You must use Linux or Mac OS; building under Windows is not currently supported.
For an overview of the entire code-review and code-update process, see Life of a Patch.
Note: All commands in this site are preceded by a dollar sign ($) to differentiate them from
output or entries within files. You may use the Click to copy feature at the top right of each
command box to copy all lines without the dollar signs or triple-click each line to copy it
individually without the dollar sign.

Choosing a Branch
Some requirements for the build environment are determined by the version of the source code
you plan to compile. For a full list of available branches, see Build Numbers. You can also choose
to download and build the latest source code (called master), in which case you will simply omit
the branch speciﬁcation when you initialize the repository.
After you have selected a branch, follow the appropriate instructions below to set up your build
environment.

Setting up a Linux build environment

These instructions apply to all branches, including master.
The Android build is routinely tested in house on recent versions of Ubuntu LTS (14.04) and
Debian testing. Most other distributions should have the required build tools available.
For Gingerbread (2.3.x) and newer versions, including the master branch, a 64-bit environment is
required. Older versions can be compiled on 32-bit systems.
Note: See Requirements for the complete list of hardware and software requirements, then
follow the detailed instructions for Ubuntu and Mac OS below.

Installing the JDK

The master branch of Android in the Android Open Source Project (AOSP) comes with prebuilt
versions of OpenJDK below prebuilts/jdk/ so no additional installation is required.
Older versions of Android require a separate installation of the JDK. On Ubuntu, use OpenJDK.
See JDK Requirements for precise versions and the sections below for instructions.
For Ubuntu >= 15.04
Run the following:

sudo apt-get update

sudo apt-get install openjdk-8-jdk

For Ubuntu LTS 14.04

There are no available supported OpenJDK 8 packages for Ubuntu 14.04. The Ubuntu 15.04
OpenJDK 8 packages have been used successfully with Ubuntu 14.04. Newer package versions
(e.g. those for 15.10, 16.04) were found not to work on 14.04 using the instructions below.

1. Download the .deb packages for 64-bit architecture from old-releases.ubuntu.com:

openjdk-8-jre-headless_8u45-b14-1_amd64.deb with SHA256

0f5aba8db39088283b51e00054813063173a4d8809f70033976f83e214ab56c0
openjdk-8-jre_8u45-b14-1_amd64.deb with SHA256
9ef76c4562d39432b69baf6c18f199707c5c56a5b4566847df908b7d74e15849
openjdk-8-jdk_8u45-b14-1_amd64.deb with SHA256
6e47215cf6205aa829e6a0a64985075bd29d1f428a4006a80c9db371c2fc3c4c

2. Optionally, conﬁrm the checksums of the downloaded ﬁles against the SHA256 string listed
with each package above. For example, with the sha256sum tool:

sha256sum {downloaded.deb file}

3. Install the packages:

sudo apt-get update

Run dpkg for each of the .deb ﬁles you downloaded. It may produce errors due to missing
dependencies:

sudo dpkg -i {downloaded.deb file}

To ﬁx missing dependencies:

sudo apt-get -f install

Update the default Java version - optional
Optionally, for the Ubuntu versions above update the default Java version by running:

sudo update-alternatives --config javasudo update-alternatives --config javac

Note: If, during a build, you encounter version errors for Java, see Wrong Java version for likely
causes and solutions.
Installing required packages (Ubuntu 14.04)
You will need a 64-bit version of Ubuntu. Ubuntu 14.04 is recommended.

sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl
zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-
core-dev libx11-dev lib32z-dev ccache libgl1-mesa-dev libxml2-utils xsltproc
unzip python-pyelftools python3-pyelftools device-tree-compiler libfdt-dev
libfdt1

Note: To use SELinux tools for policy analysis, also install the python-networkx package. Note: If
you are using LDAP and want to run ART host tests, also install the libnss-sss:i386 package.

Conﬁguring USB Access

Under GNU/linux systems (and specifically under Ubuntu systems), regular users can't directly
access USB devices by default. The system needs to be configured to allow such access.
The recommended approach is to create a file /etc/udev/rules.d/51-android.rules (as the root
user) and to copy the following lines in it. must be replaced by the actual username of the user
who is authorized to access the phones over USB.

# adb protocol on passion (Rockchip products)

SUBSYSTEM=="usb", ATTR{idVendor}=="2207", ATTR{idProduct}=="0010", MODE="0600",
OWNER="<username>"

Those new rules take effect the next time a device is plugged in. It might therefore be necessary
to unplug the device and plug it back into the computer.
This is known to work on both Ubuntu Hardy Heron (8.04.x LTS) and Lucid Lynx (10.04.x LTS).
Other versions of Ubuntu or other variants of GNU/linux might require different configurations.
References : http://source.android.com/source/initializing.html

APPENDIX B SSH public key operation

instruction
APPENDIX B-1 SSH public key generation
Use the following command to generate:

ssh-keygen -t rsa -C "user@host"

Please replace user@host with your email address.

It will generate the key ﬁle in your directory after the command is executed successfully.

Please keep carefully the generated private key ﬁle id_rsa and password, and send id_rsa.pub to
SDK release server admin through email.

APPENDIX B-2 Use key-chain to manage the key

Recommend you use the simple tool keychain to manage the key.
The detailed usage is as follows:

1. Install keychain software package:

$sudo aptitude install keychain

2. Conﬁgure to use the key:

$vim ~/.bashrc

Add the following command:

eval `keychain --eval ~/.ssh/id_rsa`

Among which, id_rsa is the ﬁle name of the private key.

Log in the console again after conﬁguring as above, and it will prompt to input the password.
Only need to input the password used for generating the key if there is one.
Besides, please avoid using sudo or root user unless you know clearly how to deal with,
otherwise it will cause the authority and key management problems.

APPENDIX B-3 Multiple devices use the same ssh

public key
In order to use on diﬀerent devices, you can copy ssh private key ﬁle id_rsa to the target device
“~/.ssh/id_rsa”.
Below hint will show up if using the wrong private key. Please replace with the correct private key.

After adding the correct private key, you can use git to clone code, shown as below picture:

Below error may occur when adding ssh private key:

Agent admitted failture to sign using the key

Input the following command at console can ﬁx it.

ssh-add ~/.ssh/id_rsa

APPENDIX B-4 Switch diﬀerent ssh public keys on

one device
You can refer to ssh_conﬁg document to conﬁgure ssh.

~$ man ssh_config
Use the following commands to conﬁgure ssh for current user.

~$ cp /etc/ssh/ssh_config ~/.ssh/config
~$ vi .ssh/config

As below picture, identify another directory ssh file ”~/.ssh1/id_rsa” as certificate private key. In
this way, you can switch different keys.
APPENDIX B-5 Key authority management
The server can real-time monitor for the specific key the download times, IP and other
information. If any abnormal case is found, it will prohibit the download authority of the
corresponding key.
Please keep carefully the private key file. DO NOT re-authorize it to the third party.

APPENDIX B-6 Git authority application instruction

Refer to above chapters, generate the public key ﬁle, and send email to [email protected]
applying for SDK code download authority.

Common questions

To create a new product directory for Rockchip development, you need to copy the existing directory, for example using the command 'cp -r rk3576_u rk3576_new_u'. After copying, navigate into the new directory and replace all occurrences of the old directory name with the new one using a tool like 'sed', for example: 'sed -i 's/rk3576_u/rk3576_new_u/g' *'. After these changes, the new product directory 'rk3576_new_u' is set up for further customization and development .

Dumpsys and logcat are essential tools for debugging and analyzing system performance on Rockchip platforms. Dumpsys provides comprehensive system information, allowing developers to examine service outputs and system states, which is critical for identifying performance bottlenecks and system issues. Logcat, on the other hand, captures and filters log messages, aiding in real-time analysis of system activity and application behavior, which helps quickly diagnose problems and verify system and application interactions under various conditions .

The MiniLoaderAll.bin file in the RK3576 image structure serves as the first-level loader that initializes the boot process by setting up necessary hardware and preparing the system to load subsequent boot stages. It is an integral part of the flashing image files that enables the device to begin booting .

Enabling the Generic Kernel Image (GKI) in Android 14 for Rockchip devices streamlines kernel management by using a standard, device-agnostic kernel. It affects the way kernels are compiled and bundled, as GKI requires kernel.img and resource.img to be included in boot.img rather than being separately flashed. This change supports greater modularity and consistency across devices that are GMS or EDLA certified, but necessitates careful updating and adherence to GKI specifications .

To confirm if the local SDK is updated to the latest release by RK, one needs to acquire the corresponding RK release version information and compare it with the local setup. Ensuring the SDK is up-to-date is crucial for accessing the latest features, security updates, and compatibility improvements provided by Rockchip, thereby enhancing development efficiency and device performance .

The Rockchip platform meets GMS and EDLA certification requirements in Android 14 by implementing the Generic Kernel Image (GKI), aligned with Google's mandate for kernel standardization. GKI ensures that Rockchip devices use a standardized, modular kernel, which simplifies updates and compatibility across diverse hardware configurations, thus fulfilling certification requirements while maintaining performance and security .

For the RK3576 platform, flashing images requires several steps and specific tool versions. First, ensure the USB driver is updated to DriverAssistant V5.1.1. For Windows, the firmware burning tool must be version 3.28 or above. For Linux, use the Linux Upgrade Tool version 2.30 or above. The image flashing process involves compiling the boot.img separately, if necessary, and managing partition tables such as parameter.txt to avoid incorrect flashing .

Rockchip provides tools and methods including modifying filesystem type to EXT4 for better logging and journaling capabilities, and using partitioning strategies within their provided SDK and tools. These modifications aim to optimize the read and write performance by making more efficient use of available storage hardware and reducing system overheads in data operations .

The Rockchip platform supports Dynamic System Updates (DSU) by default, which allows for over-the-air updates through Google's official DSU mechanism. However, DSU requires a considerable amount of memory, and it is not recommended for devices with DDR of 1GB or less due to potential performance constraints .

Modifying the Android system to support 64-bit only on Rockchip devices involves changing the build configuration to exclude 32-bit binaries. This can be done by setting relevant compilation flags in the build environment and ensuring that all dependencies and libraries are available in 64-bit versions. Comprehensive testing is necessary to confirm that the applications and system services operate correctly with these modifications, as this affects overall system compatibility and performance .

Android Porting To Beagleboard
No ratings yet
Android Porting To Beagleboard
14 pages
MSM8916 Linux Android™ Software User Manual
No ratings yet
MSM8916 Linux Android™ Software User Manual
75 pages
Ducati2 SCH 20140506 0930 PDF
No ratings yet
Ducati2 SCH 20140506 0930 PDF
34 pages
List of All Widely Used ADB Commands - Tech Blogs
100% (1)
List of All Widely Used ADB Commands - Tech Blogs
14 pages
Samsung Level 3 Repair Guide
0% (2)
Samsung Level 3 Repair Guide
27 pages
Android Terminal Commands Guide
No ratings yet
Android Terminal Commands Guide
14 pages
Arduino Cloud
No ratings yet
Arduino Cloud
53 pages
18865-OnePlus 7T Pro User Manual EN
No ratings yet
18865-OnePlus 7T Pro User Manual EN
108 pages
Schematics Iphone 6s+ Alpha2000
No ratings yet
Schematics Iphone 6s+ Alpha2000
62 pages
9 Android Broadcast Receivers
No ratings yet
9 Android Broadcast Receivers
9 pages
H158-381 5G CPE Product Description - (V100R001 - 02, English)
No ratings yet
H158-381 5G CPE Product Description - (V100R001 - 02, English)
53 pages
Galaxy Tab Parts & Repair Guide
No ratings yet
Galaxy Tab Parts & Repair Guide
83 pages
Samsung Galaxy A12
No ratings yet
Samsung Galaxy A12
21 pages
Ti - Bluetooth - Guide
100% (2)
Ti - Bluetooth - Guide
163 pages
How To Use QPST Tool To Flash or Install Firmware
No ratings yet
How To Use QPST Tool To Flash or Install Firmware
1 page
Applea10seriesapplicationprocessor 170822124054
No ratings yet
Applea10seriesapplicationprocessor 170822124054
30 pages
Flashing Firmware Image Files Using The Rockchip Tool
No ratings yet
Flashing Firmware Image Files Using The Rockchip Tool
10 pages
8 Android Services
No ratings yet
8 Android Services
9 pages
NCK Dongle Ultimate NCK Huawei Module FRP Read Guide
No ratings yet
NCK Dongle Ultimate NCK Huawei Module FRP Read Guide
3 pages
ASCII Characters Set
No ratings yet
ASCII Characters Set
8 pages
Kindle Fastboot
No ratings yet
Kindle Fastboot
11 pages
How To Putty in To Android Device Via Usb
100% (1)
How To Putty in To Android Device Via Usb
3 pages
Unisoc Confidential For Aptiv: Android 13 Secure Boot User Guide
0% (1)
Unisoc Confidential For Aptiv: Android 13 Secure Boot User Guide
40 pages
Mediatek Unrooted ROM Backup Guide
No ratings yet
Mediatek Unrooted ROM Backup Guide
14 pages
Qualcomm Writing IMEI Guide For 870: 1. Install GN - QC - EG - WRTIMEI - V1.0.0.msi
No ratings yet
Qualcomm Writing IMEI Guide For 870: 1. Install GN - QC - EG - WRTIMEI - V1.0.0.msi
6 pages
Secret Code Fujitsu
No ratings yet
Secret Code Fujitsu
6 pages
Android-x86 Debugging Guide
No ratings yet
Android-x86 Debugging Guide
3 pages
DS-70095K DSPic
No ratings yet
DS-70095K DSPic
24 pages
Snapdragon 8 Elite Platform Product Brief
No ratings yet
Snapdragon 8 Elite Platform Product Brief
2 pages
SensorTile - Box Pro Mode Naples 2019
No ratings yet
SensorTile - Box Pro Mode Naples 2019
67 pages
Linux
No ratings yet
Linux
38 pages
Design of A RISC Microcontroller Core in 48 Hours
No ratings yet
Design of A RISC Microcontroller Core in 48 Hours
11 pages
5G Outdoor CPE N5368X Quick Start Guide
No ratings yet
5G Outdoor CPE N5368X Quick Start Guide
5 pages
Samsung GT-P1000 Galaxy Tab Level 3 Service Manual
No ratings yet
Samsung GT-P1000 Galaxy Tab Level 3 Service Manual
49 pages
UpgradeDownload User Guide (En)
No ratings yet
UpgradeDownload User Guide (En)
18 pages
Configure Your Build - Android Developers
No ratings yet
Configure Your Build - Android Developers
13 pages
ADB & Fastboot Guide for Developers
No ratings yet
ADB & Fastboot Guide for Developers
7 pages
Introduction To In-Circuit Test
No ratings yet
Introduction To In-Circuit Test
30 pages
Programming On-Chip Flash Memories of 56F80X Devices Using The Jtag/Once Interface
No ratings yet
Programming On-Chip Flash Memories of 56F80X Devices Using The Jtag/Once Interface
20 pages
Unbricking MTK Devices: A Guide
No ratings yet
Unbricking MTK Devices: A Guide
3 pages
MTK Upgrade Tool User Guide
No ratings yet
MTK Upgrade Tool User Guide
23 pages
PAXSTORE Developer Guide V1.08 02 04 2020 1
No ratings yet
PAXSTORE Developer Guide V1.08 02 04 2020 1
10 pages
(SVC-09) IMEI Cloud Guide For Service Center User - Rev1.0
No ratings yet
(SVC-09) IMEI Cloud Guide For Service Center User - Rev1.0
18 pages
Ducati2 Trouble Shooting Guide20140611 PDF
No ratings yet
Ducati2 Trouble Shooting Guide20140611 PDF
12 pages
Docklight Manual
No ratings yet
Docklight Manual
55 pages
LG+Mobile+TestMode+v13 3
No ratings yet
LG+Mobile+TestMode+v13 3
401 pages
IOT Record
No ratings yet
IOT Record
29 pages
Hardware Maintenance Manual ThinkPad X1 Carbon and X1 Yoga
No ratings yet
Hardware Maintenance Manual ThinkPad X1 Carbon and X1 Yoga
122 pages
Kuongshun Electronic Product Catalog
No ratings yet
Kuongshun Electronic Product Catalog
584 pages
SM-A605FN Common Tshoo 7 PDF
No ratings yet
SM-A605FN Common Tshoo 7 PDF
50 pages
Pro Tools Key Command Preset
No ratings yet
Pro Tools Key Command Preset
3 pages
Initializing A Build Environment
No ratings yet
Initializing A Build Environment
26 pages
Rockchip RK3576 Linux6.1 SDK Beta V0.1.0 20240420 EN
No ratings yet
Rockchip RK3576 Linux6.1 SDK Beta V0.1.0 20240420 EN
8 pages
How To Build Android ROM From Source
No ratings yet
How To Build Android ROM From Source
36 pages
Building Custom Android Kernels Guide
No ratings yet
Building Custom Android Kernels Guide
23 pages
Android Auto User's Guide
No ratings yet
Android Auto User's Guide
64 pages
Compilation Guide A13 AllWinneR
No ratings yet
Compilation Guide A13 AllWinneR
5 pages
CM9 For NookColor Build Instructions
No ratings yet
CM9 For NookColor Build Instructions
6 pages
Kernel Configuration Presets Guide
No ratings yet
Kernel Configuration Presets Guide
4 pages
Make Network Path Visible For SQL Server Backup and Restore in
No ratings yet
Make Network Path Visible For SQL Server Backup and Restore in
6 pages
Essential Windows CMD Commands
0% (1)
Essential Windows CMD Commands
23 pages
Bither iOS: Secure Bitcoin Wallet
No ratings yet
Bither iOS: Secure Bitcoin Wallet
1 page
NSGW-203 00 Overview v0.1
No ratings yet
NSGW-203 00 Overview v0.1
11 pages
Apache2 Ubuntu Default Page
No ratings yet
Apache2 Ubuntu Default Page
2 pages
Examen ACE 86%
No ratings yet
Examen ACE 86%
2 pages
Dark Dex
No ratings yet
Dark Dex
274 pages
Install and Use Apache Pig Scripts
No ratings yet
Install and Use Apache Pig Scripts
4 pages
ADBS
No ratings yet
ADBS
3 pages
Access Control Software - V2.3.2.11
No ratings yet
Access Control Software - V2.3.2.11
76 pages
Cve 2014 4133
No ratings yet
Cve 2014 4133
8 pages
CEH Test - System Hacking
No ratings yet
CEH Test - System Hacking
2 pages
Upsell Pop-Up Documentation
No ratings yet
Upsell Pop-Up Documentation
18 pages
iOS Views & Hierarchy Explained
No ratings yet
iOS Views & Hierarchy Explained
15 pages
9699 Slot APK Initialization Log
No ratings yet
9699 Slot APK Initialization Log
1,326 pages
McAfee WebAdvisor Launch Errors
No ratings yet
McAfee WebAdvisor Launch Errors
10 pages
Compiling and Linking RFC Programs With The Sap Netweaver RFC SDK 7.50
No ratings yet
Compiling and Linking RFC Programs With The Sap Netweaver RFC SDK 7.50
5 pages
Word Processing
No ratings yet
Word Processing
3 pages
Tekla - Steel Detailing - Basic Training Drawing
100% (1)
Tekla - Steel Detailing - Basic Training Drawing
160 pages
Online Flight Booking for Travelers
No ratings yet
Online Flight Booking for Travelers
3 pages
Log
No ratings yet
Log
548 pages
A04 Os Exp08
No ratings yet
A04 Os Exp08
14 pages
Wireshark Display Filters
No ratings yet
Wireshark Display Filters
315 pages
SAP Solution Manager 7.1 SP14 Setup Guide
No ratings yet
SAP Solution Manager 7.1 SP14 Setup Guide
60 pages
MSProject Exercise3
No ratings yet
MSProject Exercise3
18 pages
3.) C4 All - No Changes Needed
No ratings yet
3.) C4 All - No Changes Needed
44 pages
B8 Computing Lesson: Charms Bar & File Management
No ratings yet
B8 Computing Lesson: Charms Bar & File Management
4 pages
Logging Buffer Analysis Report
No ratings yet
Logging Buffer Analysis Report
73 pages
OpenFOAM Heat Transfer Setup Guide
No ratings yet
OpenFOAM Heat Transfer Setup Guide
24 pages

RK3576 Developer Guide Android14 SDK en

Uploaded by

RK3576 Developer Guide Android14 SDK en

Uploaded by

Security Class: Top-Secret( ) Secret( ) Internal( ) Public( √ )

RK3576 Android 14.0 SDK Developer

File No.: RK-KF-YF-790

Current Version: V1.0.0

Finish Date: 2024-04-30

All rights reserved. ©2024. Rockchip

Rockchips Electronics Co., Ltd.

RK3576 Android 14.0 SDK Chipset

RK3576 Support RKR4

Wu release RKR4 SDK supporting

RK3576 Android 14.0 SDK Developer Guide

RK3576 Android 14.0 SDK code download

repo init --repo-url https://gerrit.rock-chips.com:8443/repo-release/tools/repo

If you request Express permission, then the download address is as follows:

repo init --repo-url https://gerrit.rock-chips.com:8443/repo-release/tools/repo

Download server mirroring

repo init --repo-url https://gerrit.rock-chips.com:8443/repo-release/tools/repo

If you request Express permission, then the download address is as follows:

repo init --repo-url https://gerrit.rock-chips.com:8443/repo-release/tools/repo

git clone https://gerrit.rock-chips.com:8443/repo-release/tools/repo

Set up your own repo code server

sudo apt-get install openssh-server git keychain

Take server address: 10.10.10.206 as an example for description.

1. create git account：

sudo adduser --system --shell /bin/bash --group git

2. Log in to the server as a 'git' account;

git clone https://github.com/sitaramc/gitolite.git

6. Create bin directory in git user directory;

gitolite/install -to ~/bin

8. Set the administrator.

~/bin/gitolite setup -pk YourName.pub

1. Clone gitolite management warehouse of the server;

git clone ssh://[email protected]/gitolite-admin.git

2. Add user's public key to the gitolite directory;

3. Add an administrator user.

Set up repo mirror

git clone https://gerrit.rock-chips.com:8443/repo-release/tools/repo

3. Create a new RK_Android14_mirror directory;

4. Enter the RK_Android14_mirror directory;

5. Download RK Android14 SDK mirror;

repo init --repo-url https://gerrit.rock-chips.com:8443/repo-release/tools/repo

6. Create warehouse group permissions.

.repo/repo/repo list -n > android_u.conf

1. Copy android_u.conf on the server-side to ·gitolite-admin/conf/· on the client-side;

3. Create your own new manifests warehouse.

git clone ssh://[email protected]/Android_u/manifests_xxx.git

2. Download original manifests warehouse on the client-side;

3. Submit manifest.xml ﬁle to manifest_xxx warehouse created newly;

check copy ﬁles

Push to the remote branch

git push origin master:master

4. Create your own code download link.

git clone https://gerrit.rock-chips.com:8443/repo-release/tools/repo

Switch your own code branches

2. Switch a local branch;

git checkout remotes/m/master -b xxx_branch

3. Push xxx_branch to remote server;

git push rk29 xxx_branch:xxx_branch

5. Submit the modiﬁed manifest to the remote branch.

git add include/rk_modules_repository.xml

Code modiﬁcation submittal

2. The manifests that RK modiﬁes are combined by client-side;

Download the original manifests warehouse of RK;

git clone //10.10.10.206/wlq/test/manifests.git

Check the pointed remote branches at present

wlq@wlq:~/home1/test2/kernel-6.1$ git branch -av

Create a local branch (switch from your own remote branch)

git checkout remotes/m/xxx_branch -b local_xxx_branch

Check latest TAG published currently by RK

You can ﬁnd the latest tag of Android14 currently is android-14.0-mid-rkr1

combine android-14.0-mid-rkr1 to the local branch

git merge android-14.0-mid-rkr1

git push rk29 local_xxx_branch:xxx_branch

kernel Code path description

Suitable for Android 14 products, compatible with RK3576

Suitable for Android 14 products, hardware adapted for RK3576