Rockchip Linux Recovery Developer Guide

:::info 文档信息

文档标识：RK-KF-YF-353　·　发布版本：V1.2.1　·　发布日期：2021-07-30　·　页数：22　·　语言：英文

原始文档：Rockchip_Developer_Guide_Linux_Recovery_EN.pdf

:::

章节大纲

• Rockchip Linux Recovery Developer Guide（P1）
  • OTA Upgrading（P4）
    • Overview（P4）
    • Build（P4）
    • Upgrading Process（P5）
      • Firmware Preparation for Upgrade（P5）
      • Upgrading（P5）
    • Restore the Factory Mode（P6）
    • Notices（P7）
  • Debugging（P7）
    • Check the Log of Recovery Mode（P7）
    • With and Without Panels（P8）
      • Rotation and Display of Device with Panels（P9）
    • Upgrade in Debian and Ubuntu System（P10）
  • Upgrade by SD Card Boot Disk（P10）
  • Appendix（P12）
    • The misc Partition Introduction（P12）
      • Select misc.img（P13）
    • Recovery Usage in Different Cases（P14）
      • First Power up（P14）
      • Restore the Factory Configuration（P15）
      • Upgrade（P15）
    • FAQ（P15）
      • “cannot find or open a drm device ”（P16）
      • Default Command For misc Partition Firmware Modification（P17）
      • Set userdata Partition as vfat File System（P18）
      • Do not Format the userdata or data Partition（P19）
      • SD card upgrade（P20）

在线预览

若预览无法显示，请直接下载 PDF 后用本地阅读器打开。

---

1. OTA Upgrading

1.1 Overview

OTA (Over-the-Air) is a space download technology. OTA upgrading is the standard software upgrading method provided by Android system. It is powerful and can upgrade system without loss, mainly through network such as WIFI, 3G/4G to download OTA package and upgrade automatically, also support to download OTA package to SD card or USB Flash drive to upgrade. OTA package is very small, generally from several MB to a dozen MB.

This document mainly introduces the local upgrading program of recovery execution process and technical details when using OTA technology to upgrade, to help customers understand the upgrading process and notices during development.

1.2 Build

rootfs main system

The update should be enable in rootfs , set BR2_PACKAGE_UPDATE=y in configs file.

1 source envsetup.sh 2 #choose a combo number to build rootfs according to platform chip 3 make menuconfig
1 2 3	source envsetup.sh #choose a combo number to build rootfs according to platform chip make menuconfig

Detailed configurations are as follows:

1 Target packages ---> 2 [*] Rockchip BSP packages ---> 3 [*] Rockchip OTA update for linux
1 2 3	Target packages ---> [*] Rockchip BSP packages ---> [*] Rockchip OTA update for linux

Recovery

The recovery configurations of different platforms are independent: in:

buildroot/configs/rockchip/recovery.config

Just run the following command in system root directory:

1 ./build.sh recovery
1	./build.sh recovery

It will generate the following file when run successfully:

buildroot/output/rockchip_rkxxxx_recovery/images/recovery.img

rkxxxx is the detailed chip name.

Execute the following command:

1 ./mkfirmware.sh
1	./mkfirmware.sh

Will copy the generated firmware to the directory of rockdev/. The path of the main source code related with recovery are as follows:

external/recovery/ : generate recovery binary files, it is the key program of recovery mode.

external/rkupdate/ : generate rkupdate binary files, parse the date of each partition in the update.img firmware and execute the key program of upgrade for each partition.

If the source files in above two directories are changed, please refer to the following build method:

1.  source envsetup.sh

2. Select the recovery configuration of one platform

3.  make recovery-dirclean && recovery
4.  make rkupdate-dirclean && make rkupdate
5.  ./build.sh recovery
6.  ./mkfirmware.sh

7. Flash recovery.img

1.3 Upgrading Process

1.3.1 Firmware Preparation for Upgrade

Modify tools/linux/Linux_Pack_Firmware/rockdev/package-file based on the partition configuration that needs to be upgraded,

Execute the following command in the root directory:

1 ./build.sh updateimg
1	./build.sh updateimg

When successful, the partition image specified by the package-file will be packaged to generate the update.img firmware, and will be placed in the rockdev/ directory, finally updated using this update.img.

If the error “Error！imageHead.uiTag !=0x57464B52” occurs during upgrading, it means there are errors with firmware package. Please follow the above steps to regenerate update.img and retry.

1.3.2 Upgrading

Put the upgrading firmware update.img in the root directory of the SD card or U disk or in the /userdata directory of the device. Execute the program: update ota /xxx/update.img in normal system, the device will enter recovery mode and start upgrading

The usable paths are as below:

U disk mount path: /udisk SD card mount path: /mnt/sdcard/ or /sdcard

Flash mount path: /userdata/`

After upgrading successfully, the device will reboot to normal system.

Upgrading flow chart is as follows:

1.4 Restore the Factory Mode

The readable and writable configuration files are saved in the userdata partition. There are some default configuration parameters with factory firmware and users may generate or modify the configuration files after using for a period of time. Sometimes users want to erase these data, and then they need to restore the factory configuration.

Directly run update without adding any parameter or adding factory/reset parameters will enter recovery to restore the factory mode.

1.5 Notices

When packing update.img, need to pay attention to that, full partition upgrading is not necessary for firmware upgrading, you can change the package-file to remove the partition which is no need to upgrade, and in this way you will reduce the size of upgrading package (update.img). If recovery.img is packed in package-file, it will not upgrade in recovery mode, in order to prevent that other partitions cannot upgrade normally due to power off during recovery.img upgrading, this partition upgrading is done in normal system, that is, it will check if the recovery.img is packed in update.img package before executing update command, if so, it will upgrade recovery partition and then enter recovery mode to upgrade other partition images. Do not recommend to pack misc partition into update.img. Even if it is packed, it will also be checked and ignored while loading the upgrading program. Even if the misc partition is upgraded, after upgrading successfully, recovery program will still clear up all the commands and parameters in misc partition, as a result, the expected results cannot be achieved. If putting the update.img package in userdata partition of flash, need to ensure that userdata.img is not packed in package-file. Because it may cause the damage of the file system, and make the oem or userdata partitions fail to mount after upgrading successfully. If upgrading from SD card or U disk, userdata.img can be packed to update userdata partition. It will resize userdata partition after upgrading.

2. Debugging

2.1 Check the Log of Recovery Mode

Create a hidden file in the directory: buildroot/output/rockchip_rkxxxx_recovery/target :

1 touch .rkdebug
1	touch .rkdebug

It is going to print out the upgrade log of recovery mode through serial port: The other way is checking through userdata/recovery/Log file.

After upgrading successfully, check log files in the directory of userdata/recovery on the device.

1 cat userdata/recovery/log
1	cat userdata/recovery/log

2.2 With and Without Panels

If it failed during recovery process and prompt below log:

failed to read font: res=-1, fall back to the compiled-in font
cannot find/open a drm device: No such file or directory

The log means it cannot find or open a drm device, if it is a device with panels, need to connect a panel; if not, need to do the following configurations.

Devices are all without panels by default in recovery configuration of SDK code.

1 cd Path to SDK/buildroot/package/rockchip/recovery _ _ 2 3 vim recovery.mk
1 2 3	cd Path to SDK/buildroot/package/rockchip/recovery _ _ vim recovery.mk

Open the recovery Makefile of buildroot/package/rockchip/recovery as shown below: As showed in the figure above, if BR2_PACKAGE_RECOVERY_NO_UI is configured, the macro RecoveryNoUi is defined as true. Otherwise the related libraries are linked and displayed.

1 ifeq ($(BR2 PACKAGE RECOVERY NO UI),y) _ _ _ _ 2 TARGET MAKE ENV += RecoveryNoUi=true _ _ 3 else 4 RECOVERY BUILD OPTS += -lz -lpng -ldrm _ _ 5 RECOVERY DEPENDENCIES += libzlib libpng libdrm _ 6 endif
1 2 3 4 5 6	ifeq ($(BR2 PACKAGE RECOVERY NO UI),y) _ _ _ _ TARGET MAKE ENV += RecoveryNoUi=true _ _ else RECOVERY BUILD OPTS += -lz -lpng -ldrm _ _ RECOVERY DEPENDENCIES += libzlib libpng libdrm _ endif

enabled in the recovery configuration.

Build after modifying:

1. source envsetup.sh rockchip_xxxx_recovery (xxxx is a detailed chip platform) 2. make menuconfig , enable the configuration No UI for recovery .

3.  make recovery-dirclean && make recovery
4.  ./build.sh recovery
5.  ./mkimage.sh

6. Flash rockdev/recovery.img

2.2.1 Rotation and Display of Device with Panels

If you need to do some rotation during the recovery upgrade process according to the orientation of the display device, you can follow the introduction below.

1. Update to the latest recovery code. 2. Modify the parameters of the gr_rotate interface function called by the gr_init function in

minui/graphics.c .

Rotation parameters: ROTATION_NONE: do not rotate by default ROTATION_RIGHT: rotate 90 ° clockwise ROTATION_DOWN: rotate 180 ° clockwise ROTATION_LEFT: rotate 270 ° clockwise

3. Rebuild recovery, generate recovery partition firmware, and flash.

If you need to adjust the brightness of UI display, you can modify the last parameter alpha transparency in the gr_color interface. Maximum 255 means opaque, minimum 0 means fully transparent. Replace the background picture displayed in the UI in recovery. You can replace the image files in the external/recovery/res/images directory by yourself, keeping the file names unchanged.

2.3 Upgrade in Debian and Ubuntu System

Like the recovery upgrade in Buildroot, this recovery OTA upgrade solution also supports upgrades in Debian or Ubuntu systems. For upgrade in recovery mode needs to identify and write the firmware data of different device partition nodes through each partition node of the device, Buildroot system uses the alias method (by-name) in udev to make the device partition nodes universal and easy to identify. Debian or Ubuntu systems lack such a method, which leads to a situation where recovery does not work properly in practice. Therefore, you only need to identify the nodes of the device partition in the Debian or Ubuntu system like Buildroot system, recovery will work normally.

Detailed method to modify is as follows:

buildroot/output/rockchip_rkxxxx/target/lib/udev/rules.d/61-partition-init.rules , or
buildroot/output/rockchip_rkxxxx_recovery/target/lib/udev/rules.d/61-partition-
init.rules

Copy to the corresponding path under Debian or Ubuntu, like rootfs/overlay-debug/lib/udev/rules.d/, where rkxxxx is one of Rockchip chipset (RK3308, RK3328, RK3399, RK3326 and so on), the purpose of the modification is to change each partition node like /dev/mmcblk0p0 , /dev/mmcblk0p1 , /dev/mmcblk0p2 , /dev/mmcblk0p3 ... in Debian system or Ubuntu system to /dev/block/by-name/uboot ,

/dev/block/by-name/misc ,  /dev/block/by-name/boot ,  /dev/block/by-name/rootfs ... on so on

after booting.

If the following similar device nodes still appear:

1 root@linaro-alip :~# ls /dev/block/ 2 179:0 179:3 179:5 179:7 179:96 7:0 7:3 7:6 3 179:1 179:32 179:6 179:8 1:0 7:1 7:4 7:7 4 179:2 179:4 179:64 179:9 254:0 7:2 7:5
1 2 3 4	root@linaro-alip :~# ls /dev/block/ 179:0 179:3 179:5 179:7 179:96 7:0 7:3 7:6 179:1 179:32 179:6 179:8 1:0 7:1 7:4 7:7 179:2 179:4 179:64 179:9 254:0 7:2 7:5

Try to place 61-partition-init.rules in Debian or Ubuntu /etc/udev/rules.d/ or /lib/udev/rules.d/ .

3. Upgrade by SD Card Boot Disk

This chapter mainly describes how to make SD card boot disk and relative upgrading issues in order to meet the upgrading requirement of bare chip using SD card to boot.

Use the SD card boot disk upgrade creation tool in the project directory tools\windows\SDDiskTool to

make a SD card boot disk

Select the packed update.img file in the firmware.

After all the preparation work is done, click start to create, and it will prompt if creation is successful.

Now there are two files in the root directory of SD card, where the image choosing to upgrade update.img will be renamed as sdupdate.img.

After all the preparation work is done, insert SD card to the device and then power on again.

If below information occurs in Log, it means the device is booted by SD card successfully.

U-Boot 2017.09-g1bee468 (Oct 11 2018 - 16:53:06 +0800) V1.000
Model: USM-110 a102-1
Board:Advantech usm110_rk3288 Board,HW version:0
DRAM: 2 GiB
Relocation Offset is: 7ff5a000
PMIC: RK808
vdd_arm 1100000 uV
vdd_gpu 1100000 uV
vcc_io 3300000 uV
regulator(LDO_REG2) init 3300000 uV
regulator(LDO_REG3) init 1100000 uV
regulator(LDO_REG4) init 1800000 uV
regulator(LDO_REG5) init 3300000 uV
regulator(LDO_REG6) init 1100000 uV
regulator(LDO_REG7) init 1800000 uV
regulator(LDO_REG8) init 1800000 uV
MMC: dwmmc@ff0c0000: 1, dwmmc@ff0f0000: 0
SF: Detected w25q32bv with page size 256 Bytes, erase size 4 KiB, total 4
MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
switch to partitions #0, OK
mmc1 is current device
do_rkimg_test found IDB in SDcard
Boot from SDcard
enter Recovery mode!
SF: Detected w25q32bv with page size 256 Bytes, erase size 4 KiB, total 4
MiB
Skipped ethaddr assignment due to invalid,using default!
Net: No ethernet found.
Hit any key to stop autoboot: 0
ANDROID: reboot reason: "recovery"
FDT load addr 0x10f00000 size 263 KiB
Booting kernel at 0x3575c70 with fdt at 42cf470...

If below log is printed out through serial port, it means the recovery image upgrading process of bare chip through SD card boot up is ongoing.

firmware update will from SDCARD.
is_sdcard_update out
sdupdate_package = /mnt/sdcard/sdupdate.img
Command: "/usr/bin/recovery"
sdboot update will update from /mnt/sdcard/sdupdate.img
start with main.

4. Appendix

4.1 The misc Partition Introduction

Misc actually is the first four letters of miscellaneous, which means sundry, mixture and mess.

The concept of misc partition comes from Android system. It is usually used for system upgrading or restore to factory configuration in Linux system.

The write/read of misc partition: misc partition will be written/read in the following cases:

1. Uboot: when the device is powered on, it will firstly boot up uboot, and read the content of misc partition in uboot. Then decide will enter normal system or recovery mode according to the command of misc partition.

If command is "boot-recovery", it will enter recovery mode.

If command is empty, it will enter normal system.

2. Recovery: when the device enters recovery mode, it can read recovery part contents of misc partition, and then execute different actions such as upgrading or erasing user data and so on.

The structure and content of misc partition:

The structure of misc partition is shown as below: It will take RK3308 misc partition as an example below, use the tool such as winhex or ultraEdit etc. to open misc.img file with binary format, and save the content of struct BootLoader Msg starting at 16K (16384 Byte) byte offset from file start position.

For the supported commands in recovery, please refer to the contents of struct OPTIONS in external/recovery/recovery.c.

4.1.1 Select misc.img

The misc.img is a frequently used file in the SDK root directory device device/rockchip/rockimg . When generating firmware, choose which misc.img file to copy based on the configuration.

1 . 2 ├ ── blank-misc.img #blank misc partition file 3 ├── pcba small misc.img #infrequently used _ _ 4 ├── pcba whole misc.img #infrequently used _ _ 5 └── wipe all-misc.img #format the misc partition file used by the user _ partition
1 2 3 4 5	. ├ ── blank-misc.img #blank misc partition file ├── pcba small misc.img #infrequently used _ _ ├── pcba whole misc.img #infrequently used _ _ └── wipe all-misc.img #format the misc partition file used by the user _ partition

cd device/rockchip/rkxxxx
vim BoardConfig.mk

As shown from the above figure, wipe_all-misc.img is used as the firmware of the misc partition by default. After flash this misc firmware, the user (/userdata or /data) partition and the customize (/ oem) partition will be formatted. If you want to boot into the normal system without going into recovery mode, you can modify the specific file of misc image in BoardConfig.mk as blank-misc.img. Then rebuild to generate a new firmware.

4.2 Recovery Usage in Different Cases

4.2.1 First Power up

The device have been flashed misc.img and recovery.img will enter the first power up process.

The serial port will print the following log:

Boot command: boot-recovery
Got arguments from boot message
Command: "recovery" "--wipe_all"
format '/dev/block/by-name/userdata' to ext2 filesystem
executing '/sbin/mke2fs'
executed '/sbin/mke2fs' done
executed '/sbin/mke2fs' return 0
executing '/sbin/e2fsck'
e2fsck 1.43.9 (8-Feb-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/by-name/userdata: 11/2304 files (0.0% non-contiguous), 82/2299
blocks
executed '/sbin/e2fsck' done
executed '/sbin/e2fsck' return 0
executing '/usr/sbin/e2fsck'
e2fsck 1.43.9 (8-Feb-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/by-name/oem: 18/2448 files (0.0% non-contiguous), 513/16384
blocks
executed '/usr/sbin/e2fsck' done
executed '/usr/sbin/e2fsck' return 1
executing '/usr/sbin/resize2fs'
resize2fs 1.43.9 (8-Feb-2018)
The filesystem is already 16384 (1k) blocks long. Nothing to do!
executed '/usr/sbin/resize2fs' done
executed '/usr/sbin/resize2fs' return 0

4.2.2 Restore the Factory Configuration

Run update program in Command line, the device will enter recovery mode and start formatting, and it will automatically enter normal system after formatting.

update (or update reset)

The serial port will print the following log::

1 I:Boot command: boot-recovery 2 I:Got arguments from boot message 3 Command: "recovery" "--wipe data" _ 4 format '/dev/block/by-name/userdata' to ext2 filesystem 5 executing '/sbin/mke2fs' 6 [ 4.692437] vendor storage:20160801 ret = -1 7 [ 6.030842] phy phy-ff008000.syscon:usb2-phy@100.0: charger = 8 USB SDP CHARGER _ _ 9 [ 10.891460] random: nonblocking pool is initialized
1 2 3 4 5 6 7 8 9	I:Boot command: boot-recovery I:Got arguments from boot message Command: "recovery" "--wipe data" _ format '/dev/block/by-name/userdata' to ext2 filesystem executing '/sbin/mke2fs' [ 4.692437] vendor storage:20160801 ret = -1 [ 6.030842] phy phy-ff008000.syscon:usb2-phy@100.0: charger = USB SDP CHARGER _ _ [ 10.891460] random: nonblocking pool is initialized

Run update ota /xxx/update.img , the device will enter recovery and start upgrading.

1 update ota /udisk/update.img
1	update ota /udisk/update.img

Take upgrading from U disk as an example, the serial port may print the following log::

1 I:Boot command: boot-recovery 2 I:Got arguments from boot message 3 Command: "recovery" "--update package=/udisk/update.img" _ 4 。。。。 5 librkupdate ui print = parameter writing.... _ _ 6 ########### RKA Gpt Download ######### _ _ 7 librkupdate ###### Download trust ... ####### _
1 2 3 4 5 6 7	I:Boot command: boot-recovery I:Got arguments from boot message Command: "recovery" "--update package=/udisk/update.img" _ 。。。。 librkupdate ui print = parameter writing.... _ _ ########### RKA Gpt Download ######### _ _ librkupdate ###### Download trust ... ####### _

4.3 FAQ

4.3.1 “cannot find or open a drm device ”

For Non RK3308 platforms, after the device enters recovery mode, usually it will to see below log printed from serial port:

1 we are in recovery, skip init oem/userdata 2 start debug recovery... 3 Starting recovery on Fri Jan 18 09:19:51 2013 4 failed to read font: res=-1, fall back to the compiled-in font 5 Starting network: cannot find/open a drm device: No such file or directory
1 2 3 4 5	we are in recovery, skip init oem/userdata start debug recovery... Starting recovery on Fri Jan 18 09:19:51 2013 failed to read font: res=-1, fall back to the compiled-in font Starting network: cannot find/open a drm device: No such file or directory

In this case, the solution is to connect supported display panel or HDMI device to the device.

Analysis: it cannot find or open a drm device from the log. Because for non RK3308 platforms, build of recovery program enables UI display by default, if it cannot open the display device after entering recovery mode, it will lead to recovery execution failure.

If you want to support recovery upgrading feature without display for non RK3308 platforms such as RK3399, RK3288 etc., users can run according to below method:

Solution:

1.  source envsetup.sh

2. Use the recovery of the current platform to configure the number and enter 3. make menuconfig , enable the No UI for recovery configuration

1 > Target packages ---> 2 [*] Rockchip BSP packages ---> 3 [*] Rockchip recovery for linux 4 [*] No UI for recovery 5 [ ] Linux AB bool control 6 Linux A/B bringup features. (successful boot) ---> _ 7 choice the update bin of recovery. (rkupdate) ---> 8 -*- recovery bin 9 [ ] updateEngine bin
1 2 3 4 5 6 7 8 9	> Target packages ---> [*] Rockchip BSP packages ---> [*] Rockchip recovery for linux [*] No UI for recovery [ ] Linux AB bool control Linux A/B bringup features. (successful boot) ---> _ choice the update bin of recovery. (rkupdate) ---> -*- recovery bin [ ] updateEngine bin
It is n

4. Rebuild the recovery package

1 make recovery-dirclean && make recovery
1	make recovery-dirclean && make recovery

5. Regenerate recovery firmware

1 ./build.sh recovery
1	./build.sh recovery

6. Generate a firmware.

1 ./mkfirmware.sh
1	./mkfirmware.sh

4.3.2 Default Command For misc Partition Firmware Modification

If you want to modify the different recovery commands packaged in the misc firmware, or use a empty misc partition firmware. Please refer to the following modification:

Modify the mkfirmware.sh in the project root directory:

4.3.3 Set userdata Partition as vfat File System

The userdata partition is ext2/ext4 file system in the SDK by default, if you want to change it to vfat32 file system, please refer to following modification:

1. Modify  board/rockchip/rkxxxx/fs-overlay-recovery/etc/fstab :

Before modificaiton:

1 /dev/block/by-name/userdata /userdata ext2 defaults0
1	/dev/block/by-name/userdata /userdata ext2 defaults0

After modificaiton:

1 /dev/block/by-name/userdata /userdata vfat defaults0 0
1	/dev/block/by-name/userdata /userdata vfat defaults0 0

2. Modify  configs/rockchip_rkxxxx_release_defconfig :

Add below configuration:

1 BR2 PACKAGE DOSFSTOOLS=y _ _ 2 BR2 PACKAGE DOSFSTOOLS FATLABEL=y _ _ _ 3 BR2 PACKAGE DOSFSTOOLS FSCK FAT=y _ _ _ _ 4 BR2 PACKAGE DOSFSTOOLS MKFS FAT=y _ _ _ _
1 2 3 4	BR2 PACKAGE DOSFSTOOLS=y _ _ BR2 PACKAGE DOSFSTOOLS FATLABEL=y _ _ _ BR2 PACKAGE DOSFSTOOLS FSCK FAT=y _ _ _ _ BR2 PACKAGE DOSFSTOOLS MKFS FAT=y _ _ _ _

3. Modify  package/rockchip/usbdevice/S50usbdevice

1 start) 2 mkdir /dev/usb-ffs -m 0770 3 mkdir /dev/usb-ffs/adb -m 0770 4 mount -t configfs none /sys/kernel/config 5 mkdir /sys/kernel/config/usb gadget/rockchip -m 0770 _ 6 echo 0x2207 > /sys/kernel/config/usb gadget/rockchip/idVendor _ 7 echo "ums adb" > _ 8 /sys/kernel/config/usb gadget/rockchip/configs/b.1/strings/0x409/configurati _ on 9 mount -t functionfs adb /dev/usb-ffs/adb 10 mount -t vfat /dev/disk/by-partlabel/userdata /media/usb0 11 export service adb tcp port=5555 _ _ _ 12 adbd & 13 sleep 1

1 2 3 4 5 6 7 8 9 10 11 12 13

start) mkdir /dev/usb-ffs -m 0770 mkdir /dev/usb-ffs/adb -m 0770 mount -t configfs none /sys/kernel/config mkdir /sys/kernel/config/usb gadget/rockchip -m 0770 _ echo 0x2207 > /sys/kernel/config/usb gadget/rockchip/idVendor _ echo "ums adb" > _ /sys/kernel/config/usb gadget/rockchip/configs/b.1/strings/0x409/configurati _ on mount -t functionfs adb /dev/usb-ffs/adb mount -t vfat /dev/disk/by-partlabel/userdata /media/usb0 export service adb tcp port=5555 _ _ _ adbd & sleep 1

4. Make sure the following patch is already updated.

0001-common-mk-userdata-Fix-wrong-FS_TYPE-check.patch

1 case $FS TYPE in _ 2 ext[2-4]) 3 $COMMON DIR/mke2img.sh $USERDATA DIR $USERDATA IMG _ _ _ 4 ;; 5 fat|vfat) 6 SIZE=$(du -h -BM --max-depth=1 $USERDATA DIR|awk '{print int($1)}') _ 7 # echo "create image size=${SIZE}M" 8 dd if=/dev/zero of=$USERDATA IMG bs=1M count=$SIZE >/dev/null 2>&1 _ 9 mkfs.vfat $USERDATA IMG >/dev/null 2>&1 _ 10 mcopy -i $USERDATA IMG $USERDATA DIR/* ::/ >/dev/null 2>&1 _ _ 11 ;; 12 *) 13 echo "file system: $FS TYPE not support." _ 14 exit 1 15 ;; 16 Esac
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16	case $FS TYPE in _ ext[2-4]) $COMMON DIR/mke2img.sh $USERDATA DIR $USERDATA IMG _ _ _ ;; fat|vfat) SIZE=$(du -h -BM --max-depth=1 $USERDATA DIR|awk '{print int($1)}') _ # echo "create image size=${SIZE}M" dd if=/dev/zero of=$USERDATA IMG bs=1M count=$SIZE >/dev/null 2>&1 _ mkfs.vfat $USERDATA IMG >/dev/null 2>&1 _ mcopy -i $USERDATA IMG $USERDATA DIR/* ::/ >/dev/null 2>&1 _ _ ;; *) echo "file system: $FS TYPE not support." _ exit 1 ;; Esac
5. M
1
2 3 4 5 6 7
6.

export RK_USERDATA_FS_TYPE=ext2
# Set userdata partition type, including ext2, fat
export RK_USERDATA_FS_TYPE=vfat

4.3.4 Do not Format the userdata or data Partition

The wipe_all-misc.img is configured in the BoardConfig.mk , but sometimes users don't want to format user or custom (userdata or oem) partitions. in this case, the recovery code external/recovery/reocvery.c should be modified: the code in the main function as shown below, delete the code in the red box below, rebuild the the recovery partition firmware and flash the firmware.

4.3.5 SD card upgrade

In the actual project development, SD card is often used to make the startup disk to upgrade the bare chip or upgrade flash firmware. In Chapter 3, we describe the SD card to make the startup disk and can enter recovery mode and upgrade it normally. However, in the actual use, it is often encountered that the SD card upgrade can not be carried out normally and the serial port has no output. This section provides a targeted description of this scenario.

Here, taking rk1808 platform as an example, other RK platform chips (rk3288, rk3399, rk3399pro) are similar. After SD card pins and UART 2 debug serial port IO multiplexing, SD card is used as a solution to upgrade boot card.

1. First, check the hardware original circuit diagram to see whether the GPIO pin of SD card is multiplexed with UART2 serial port pin. If the hardware is multiplexed, adjust the dtsi under uboot, enable SDMMC, and disable UART2 (the system uses UART2 as the debugging serial port by default). If there is no multiplexing, check the power and initialization part of SD card.

2. Modify the loader, reconfigure the print of UART in the loader, and modify SDK / rkbin / tools / ddrbin_ param.txt UART ID. If the serial fly line can be connected to uart1 M0, then UART id = 1; if it flies to uart1 M1, then UART id = 1, UART iomux = 1.

3. Regenerate ddr.bin , execute the following command:

1 cd SDK/rkbin/tools 2 rkbin/tools$./ddrbin tool ddrbin param.txt _ _ ../bin/rk1x/rk1808 ddr 933MHz v1.04.bin _ _ _
1 2	cd SDK/rkbin/tools rkbin/tools$./ddrbin tool ddrbin param.txt _ _ ../bin/rk1x/rk1808 ddr 933MHz v1.04.bin _ _ _

The 1808_ ddr_ 933MHz_ The v1.04.bin file is consistent with the file name in the current rkbin/bin/rk1x directory in the SDK.

Different platform directory may be different, and it is named according to the first two digits of the actual chip platform. ddrbin_tool For details of parameters, please refer to the document: SDK

/rkbin/tools/ddrbin_ tool_user_guide.txt .

4. Modify the kernel DTS configuration.

Modify debug serial port, in addition to ddr.bin modification, the kernel needs to be modified. 5. Modify the startup parameter cmdline:

kernel/arch/arm64/boot/dts/rockchip/rk1808-evb-v10.dts

1 chosen { 2 bootargs = "earlycon=uart8250,mmio32,0xff550000 console=ttyFIQ0 root=PARTUUID=614e0000-0000 rootfstype=ext4 rootwait swiotlb=1 kpti=0 snd aloop.index=7"; _ 3 };
1 2 3	chosen { bootargs = "earlycon=uart8250,mmio32,0xff550000 console=ttyFIQ0 root=PARTUUID=614e0000-0000 rootfstype=ext4 rootwait swiotlb=1 kpti=0 snd aloop.index=7"; _ };

The address 0xff550000 here is to be modified according to the actual serial port. Different serial addresses can be found in the file arch/arm64/boot/dts/rockchip/rk1808.dtsi , similar to other platforms, by searching the device tree file of the corresponding platform.

For example: RK1808 platform uart2:Serial@ff550000, uart1:Serial@ff540000.

6. Compile firmware

Uboot compilation: ./build.sh uboot

or enter the u-boot directory, execute ./make.sh rk1808

The generated files after compiling are in the u-boot directory:

1 u-boot/ 2 ├── rk1808 loader v1.03.104.bin _ _ 3 ├── trust.img 4 └── uboot.img
1 2 3 4	u-boot/ ├── rk1808 loader v1.03.104.bin _ _ ├── trust.img └── uboot.img

Kenel compilation: . /build.sh kernel

Recoy compilation: . /build.sh recovery

Last  . /build.sh updateimg .

7. After properly flashing the firmware:

8. Package generation update.img , use "SDDiskTool_v1.62" or newer version to flash the update.img to the SD card. 2. Power off the development board, plug in the SD card and power on.At this time, the serial port can print the log from uart1 or other serial port currently specified by flight lines, and analyze the SD card upgrade problem according to the log.