Skip to main content

Linux BSP User Guide for RK3399 Series Debian10

1. Introduction​

This document provides comprehensive instructions for building and deploying Linux BSP for RK3399 series platforms running Debian10. The guide covers environment setup, source code acquisition, building processes for multiple processors platforms, and deployment methods.

2. Linux BSP Version​

  • OS: Debian 10.x
  • Kernel: 4.4.xxx

3. Build Environment on Host​

Currently, we adopt Docker as build environment.

You can get the latest version of advrisc/u18.04-rklbv1 Docker image for developing Rockchip RK3399 projects.

3.1 Docker Installation Commands​

$ sudo apt-get update
$ sudo apt-get install -y qemu-user-static
$ sudo apt-get install -y live-build
$ sudo docker pull advrisc/u18.04-rklbv1

3.2 Run Docker Example​

  • Step 1: Run Docker Container
    Assume your working directory is home/bsp/myLinux and the Docker container name is rk3399_linux_risc.
    Replace home/bsp/myLinux and rk3399_linux_risc with the actual ones based on your environment.
$ export WORKSPACE="home/bsp/myLinux"
$ export CONTAINER_NAME="rk3399_linux_risc"
$ sudo docker run -it --name ${CONTAINER_NAME} -v ${WORKSPACE}:/home/adv/BSP:rw --privileged advrisc/u18.04-rklbv1:latest /bin/bash
  • Step 2: Change User in Container
$ adv@7cc0fa834366:~$ sudo chown adv:adv -R BSP
  • Step 3: Install build dependencies in Container
    • Install qemeu and binfmts 
      adv@7cc0fa834366:~$ sudo apt-get update
      adv@7cc0fa834366:~$ sudo apt-get install binfmt-support qemu-user-static --reinstall
      adv@7cc0fa834366:~$ sudo update-binfmts --enable qemu-aarch64
    • Install gettext 
      adv@7cc0fa834366:~$ sudo apt-get update
      adv@7cc0fa834366:~$ sudo apt-get install gettext expect -y

4. Getting Linux Source Code​

4.1 Full SDK​

$ cd ~/BSP
$ sudo git clone https://github.com/ADVANTECH-Rockchip/repo.git
$ mkdir rk3399_linux_risc
$ cd rk3399_linux_risc
$ git config --global user.name "Your Name"
$ git config --global user.email you@example.com
$ ../repo/repo init -u https://github.com/ADVANTECH-Rockchip/linux-manifest.git -b rk3399_linux_v251_risc -m default.xml
$ ../repo/repo sync
$ ../repo/repo forall -c git checkout -b local --track advantech-github/rk3399_linux_v251_risc
$

5. Building​

5.1 Choose Project​

  • Build RSB-3710 Project
$ export TOP=`pwd`
$ cd $TOP
$ export UBOOT_PROJECT="rk3399_rsb3710a2_2G"
$ export KERNEL_PROJECT="rk3399-rsb3710-a2.img"
  • Build RSB-4710 Project
$ export TOP=`pwd`
$ cd $TOP
$ export UBOOT_PROJECT="rk3399_rsb4710a2_2G"
$ export KERNEL_PROJECT="rk3399-rsb4710-a2.img"
  • Build ROM-5780 Project
$ export TOP=`pwd`
$ cd $TOP
$ export UBOOT_PROJECT="rk3399_rom5780a3_2G"
$ export KERNEL_PROJECT="rk3399-rom5780-a3.img"

5.2 Build U-boot​

$ cd $TOP
$ cd u-boot
$ ./make.sh ${UBOOT_PROJECT}

5.3 Build Kernel​

$ cd $TOP
$ cd kernel
$ make ARCH=arm64 rk3399_adv_defconfig -j8
$ make ARCH=arm64 ${KERNEL_PROJECT} -j12

5.4 Build Recovery​

$ cd $TOP
$ rm buildroot/output/rockchip_rk3399_recovery -rf
$ source envsetup.sh rockchip_rk3399_recovery
$ ./build.sh recovery

5.5 Build Debian 10.x​

$ cd $TOP
$ source envsetup.sh rockchip_rk3399
$ sudo BUILD_IN_DOCKER=TRUE ./mk-debian.sh

5.6 Push All Images to Rockdev Folder​

$ cd $TOP
$ ./build.sh firmware

The common image files in rockdev/ directory are listed below:

boot.img
misc.img
oem.img
recovery.img
rootfs.img
uboot.img
userdata.img
MiniLoaderAll.bin
parameter.txt

5.7 Make update.img​

$ cd $TOP
$ source envsetup.sh rockchip_rk3399
$ ./build.sh updateimg

You can get update.img in rockdev/ directory.

6. Update Images​

There are three ways to update images:

6.1 Using RKDevTool via USB Cable​

There is no limitation by this method.

6.2 Local OTA​

There are some limitations:

  1. The device must be able to boot up to Debian
  2. Only update images from the same OS (e.g., Debian upgrade to Debian)
  3. Using update.img to upgrade

6.3 Via SD card​

  1. Only update images from the same OS (e.g., Debian upgrade to Debian)
  2. Using update.img to upgrade

7. Summary​

7.1 Supported Hardware Platforms​

  • RSB-3710
  • RSB-4710
  • ROM-5780

7.2 System Requirements​

  • Docker environment with advrisc/u18.04-rklbv1 image
  • Ubuntu 18.04 base system
  • BSP tarball from PM
  • Build tools and dependencies
  • Sufficient disk space for source code and build artifacts
  • Internet connection for package installation
  • Target processors (RSB-3710, RSB-4710, or AFE-E6390)

7.3 Build Workflow Summary​

  1. Environment Setup → Docker + Ubuntu 18.04
  2. Source Acquisition → BSP tarball or Full SDK
  3. Project Selection → Choose target processors platform
  4. Component Build → U-boot → Kernel → (Recovery)* → (Debian)*
  5. Image Generation → Firmware packaging → (Update image)*
  6. Deployment → AndroidTool, SD/USB storage, or SDDiskTool

Components marked with asterisk () are not supported in BSP tarball mode.

7.4 Development Modes​

7.4.1 BSP Tarball Mode (Limited)​

  • Use Case: Quick U-boot and kernel development
  • Advantages: Fast setup, smaller download size
  • Limitations: Cannot build recovery, debian, or update images
Important Notes about BSP Tarball

The BSP tarball is designed for fast development of uboot and kernel components. However, it has some limitations.

  • ✅ Supported: U-boot building
  • ✅ Supported: Kernel building
  • ❌ NOT Supported: Recovery building
  • ❌ NOT Supported: Debian building
  • ❌ NOT Supported: Update image building

7.4.2 Full SDK Mode (Complete)​

  • Use Case: Complete system development and customization
  • Advantages: Full build capability, all components supported
  • Limitations: Larger download size