Orange Pi RK3399

Orange Pi RK3399 Introduction

What is Orange Pi RK3399?

It’s an open-source single-board computer. It can run Android 6.0, Ubuntu, Debian, it uses the RK3399 SoC, and has 2GB DDR3 SDRAM

What can I do with Orange Pi RK3399?

You can use it to build...

• A computer
• A wireless server
• Games
• Music and sounds
• HD video
• A speaker
• Android
• Scratch

......
Pretty much anything else, because Orange Pi RK3399 is open source.

Whom is it for?

Orange Pi RK3399is for anyone who wants to create with technology– not just consuming. It's a simple, fun, useful tool and you can use it to take control of the world around you.

Orange Pi RK3399 Hardware specification

Hardware Specification
Soc	Rockchip RK3399 (28nm HKMG Process）
CPU	Six-CoreARM® 64-bit processor, up to 2.0GHz frequency Dual-Core Cortex-A72 and Quad-Core Cortex-A53
GPU	ARM Mali-T860 MP4 Quad-Core GPU Completely compatible with OpenGL ES1.1/2.0/3.0/3.1, OpenVG1.1, OpenCL, DX11 Support AFBC
VPU	Supports multi-format video decoders including H.264/H.265/VP9 4Kx2K@60fps 1080P Multi format video decoding (WMV, MPEG-1/2/4, VP8) 1080PVideo encoding, supporting H.264, VP8 format Video post processor: anti interleaving, denoising, edge/ detail / color optimization
PMU	RK808 PMU BQ25700 Charger IC CW2015 Fuel Gas
Memory	2GB DDR3
Storage	16GB High-Speed eMMC MicroSD (TF) Card Slot miniPCIe (for LTE / mSATA) mSATA interface
Wireless	Integrated WiFi Combo Module(AP6356S): 2.4GHz/5GHz Dual-Band WiFi Support 802.11a/b/g/n/ac 2x2 MIMO standard Bluetooth 4.1(Support BLE)
Ethernet	10/100/1000Mbps Ethernet ( Realtek RTL8211E )
Display	1 x HDMI 2.0 ( Type-A ), Support maximum 4K@60Hz display 1 x DP 1.2 (DisplayPort) , Support maximum 4K@60Hz display 2 x MIPI , support 2560x1600@60fps output with dual channel 1 x eDP 1.3 ( 4 lanes with 10.8Gbps ) 1 x HDMI IN
Audio	1 x HDMI or 1 x DP ( DispalyPort ) for audio output 1 x Analog audio (via 3.5mm Combo Audio Jack for audio input and ouput) 1 x Speaker for audio output ( 1.5W 8Ω or 2.5W 4Ω ) 1 x SPDIF 1 x On-board Microphone 1 x I2S (up to 8 channels) for audio input and output 1 x Mic Array Interface
Camera	2 x MIPI-CSI (13Mpixel Max for each port ) (OV13850(13M)) Support USB Camera
Sensor	1 x Gyroscope+G-Sensor(MPU6500) 1 x Gyroscope(LSM6DS3) 1 x HALL Sensor(HAL248TWCL) 1 x Light Sensor(CM32181) 1 x Compass(AK09911)
PCIe	1 x Mini PCIe Compatible USB, used for LTE or TF Card Compatible mSATA, used for expand SATA harddisk or SSD
SIM	1 x SIM slot, use as LTE module for miniPCIe extension
USB	4 x USB2.0 HOST, 1 x USB3.0 Type-C
IR	1 x IR, Support IR control function
LED	2 x Power Status LED (Red and Green) 1 x SATA Power Status LED(Green)
Key	1x Reset Button, 1 x Power Button, 1 x Recovery Button, 1 x Menu Button, 1 x Return Button, 1 x Vol+ Button, 1 x Vol- Button
Debugging	1 x Serial Console
Reserved Interface	40pin 2.54mm header 4 x I2C , 1 x SPI, 2 x UART, 5 x GPIO
External Power supply interface	DC12V - 2A (2 pins) DC5V - 2A (2 pins)
Power	DC12V-2A (via DC 5.5*2.1mm Jack) TypeC 5V-3A Battery (Dual Battery 7.4V)
OS / Software
OS	Android 6.0, Debian 9
Programming support	C, C++, Kotlin, Java, Shell, Pyhon
Interface definition
Size	129 mm × 99 mm
Weight	100g

800px|

800px|

GPIO Specifications

The following is GPIO definition of Orange Pi RK3399:

800px|

800px|

800px|

Using Method Introduction

Hardware Requirement

• Orange Pi RK3399 Development Board
• A PC for compilation with following specs:
  

64bit CPU
Up to 16GB RAM
UP to 40GB spare disk space
Operation system should up to Ubuntu12.04, it would be better if it is Ubuntu16.04 You could refer to Google file for more details: https://source.android.com/source/building

Software Requirement

• Orange Pi RK3399 SDK
• Orange Pi RK3399 Firmware
• Android-image-flash-tool

Power Supply Requirement

There are three methods for power supply:

• DC （12V 2A）in for power
• TypeC （5V 3A）in for power
• Battery （Dual Battery 7.4V）in for power, connect the battery with our BAT interface

If insert TypeC and DC connector in the same time, the system would default charge by DC in. It would not recommend to power by the battery, because different batteries need matching with BQ25700 battery management IC according to their respective parameters.

Android Compilation Environment Construction

Download SDK compression package

Take OrangePi-RK3399_Android6.0_V1.0_2017_0720.tgz as an example, after get the original compression package:

mkdir OrangePi-rk3399
tar xvf OrangePi-rk3399_Android6.0_V1.0_2017_0720.tgz -C OrangePi-rk3399
cd OrangePi-rk3399

Construct Compilation Environment

It could also refer to Google file: http://source.android.com/source/initializing.html

• Install JDK

Compilation of Android6.0 is based on JAVA7, it needs to first install OpenJDK before compilation.

Command for installing:

sudo apt-get install openjdk-7-jdk

Configure environment variable of JAVA, here is the path for installation:

/usr/lib/jvm/java-7-openjdk-amd64

It could configure on the terminal with the following command:

export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64
export PATH=$JAVA_HOME/bin:$PATH
export CLASSPATH=.:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar

• Install Software Package

For Ubuntu12.04:

sudo apt-get update
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
g++-multilib mingw32 tofrodos gcc-multilib ia32-libs \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386

For Ubuntu14.04:

sudo apt-get update
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev \
libesd0-dev libwxgtk2.8-dev squashfs-tools build-essential zip curl \
libncurses5-dev zlib1g-dev pngcrush schedtool libxml2 libxml2-utils \
xsltproc lzop libc6-dev schedtool g++-multilib lib32z1-dev lib32ncurses5-dev \
lib32readline-gplv2-dev gcc-multilib libswitch-perl

The relevant software package for installing ARM cross compilation tool chain and kernel:

sudo apt-get install gcc-arm-linux-gnueabihf \
lzop libncurses5-dev \
libssl1.0.0 libssl-dev

Compilation of SDK Source Code

• Compilation with auto-building shell scripts

We can make use of the RKTool/make.sh script in the SDK root directory for automatic compilation, using the following methods(Please ensure that it runs in the root directory):
U-boot Compilation:

./RKTools/make.sh -u -j4

Kernel Compilation:

./RKTools/make.sh -k -j4

Android Compilation: ./RKTools/make.sh -a -j4 </div> Compile u-boot、Kernel、Android in the same time:

cd SDK_ROOT/
./RKTools/make.sh -j4

• Manual Compilation with Different Module

U-boot Compilation:

cd u-boot
make rk3399_defconfig
make ARCHV=aarch64 -j4

Kernel Compilation:

cd kernel
make ARCH=arm64 orangepi_defconfig
make ARCH=arm64 rk3399-orangepi.img -j4

Android Compilation:

source build/envsetup.sh
lunch rk3399_mid-userdebug
make -j4

Generated Firmware

./mkimages.sh

After execute ./mkimages.sh, it will generate a full firmware package on the directory of rockdev/Image-rk3399_mid.

rockdev/Image-xxx/
├── boot.img
├── kernel.img
├── misc.img
├── parameter.txt
├── recovery.img
├── resource.img
├── RK3399MiniLoaderAll_V1.05.bin
├── system.img
├── trust.img
└── uboot.img

Except the above method, the unity image(update.img) could also be generated via Linux_Pack_Firmware.

Android Firmware Flashing

Relevant keys and connectors for firmware flashing of Orange Pi RK3399 :

800px|

There are two types of Firmware file:

• Multi-partition images: generated uboot.img, recovery.img, trust.img, kernel.img, resource.img, system.img, usually used for debug.
• One image: generated into update.img with packing tool from several partition image files, usually used for Firmware release.

(The official has already made Android image, also you could try to compile you own image with reference of our manual.)

Supporting OS of PC:

• Windows XP (32/64bit)
• Windows 7 (32/64bit)
• Windows 8 (32/64bit)
• Linux (32/64bit)

We use AndroidTool on Windows
Download path: AndroidTool
We use upgrade_tool on Linux:
Download path: upgrade_tool
Please select the corresponding tool according to your PC environment.。

Flashing image on Windows

The tool we should use on Windows is AndroidTool, you could use it for multi-partition image flashing or one image file: update.img.
Before image writing, we need to first install RK USB driver on Windows.

1)Install RK USB Driver
Download path: DriverAssitant
Run this after unzip: DriverInstall.exe
In order to use the latest driver of all device, please first click Drive unload and then click Drive install:

400px|

Connect with Type-C data cable and PC with Orange Pi RK3399 after installed USB driver, there would be show the status of USB driver on lower right corner like the following:

300px|

2)Enter into Flashing Mode

• Type-A Connect to PC
• Press on Recovery key of Orange Pi RK3399
• Type-C Connect to Orange Pi RK3399, there should be notice on the following :

400px|

There would be log information if you connect debug pin.

400px|

If there is no Loader device, then you need to flash image with short connect like the following:
When short connect EMMC Clk and GND, insert DC power supply, enter into Maskrom mode. And insert Type-C cable to connect both PC and RK3399.
Location of EMMC Clk is show on the following:

800px|

800px|

• Insert DC power supply
  

Since OrangePi RK3399 supports powered by TypeC, power voltage on USB of PC is enough for flashing image. However, it may not enough to support Orange Pi booting. In that case, we need to insert DC power supply to make sure the Orange Pi could boot successfully after flashed image.

• If need to flash every partition image(*.img) separately, right click Download Image then click corresponding firmware path. After that click Run, and the right side would show the status of running.

800px|

• If need to flash unity firmware(update.img), click Firmware on Upgrade Firmware, select path of update.img. After it recognized LOADER device, click Upgrade and it will begin to upgrade. The right side would show the status of flashing.

800px|

Flashing image on Linux

1)Flash tool: upgrade_tool
On Linux, the tool we use is upgrade_tool which is same with working on Windows. Enter into Loader flashing mode like the following:

• Type-A Connect to PC
• Press on Recovery key of Orange Pi RK3399
• Type-C Connect to Orange Pi RK3399
• Insert DC power supply

Since OrangePi RK3399 supports powered by TypeC, power voltage on USB of PC is enough for flashing image. However, it may not enough to support Orange Pi booting. In that case, we need to insert DC power supply to make sure the Orange Pi could boot successfully after flashed image.
There would be log information if you connect debug pin.

400px|

If there is no Loader device, then you need to flash image with short connect like the following: When short connect EMMC Clk and GND, insert DC power supply, enter into Maskrom mode. And insert Type-C cable to connect both PC and RK3399.
Location of EMMC Clk is show on the following:

800px|

800px|

Run upgrade_tool on terminal of Linux:

$ sudo ./upgrade_tool
List of rockusb connected
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=201 Loader
Found 1 rockusb,Select input DevNo,Rescan press <R>,Quit press <Q>:

Enter R: Re-scan the USB port to find the device
Enter Q: Exit flashing tool
Enter DevNo: Select the corresponding operation device
Here I would enter 1:

Found 1 rockusb,Select input DevNo,Rescan press <R>,Quit press <Q>:1

The help menu is displayed when you enter, and the Rockusb> prompt appears

600px|

• It could be operated by entering the corresponding instructions after the Rockusb> prompt. No distinguish between capital and lowercase.
  

TD Command: used to test whether the device status is normal

600px|

DI Command: used for flashing separate partitions *.img ：
DI <-p|-b|-k|-s|-r|-m image> [parameter file]
The first parameter is used to specify the partition name that needs to be flashed.
The second parameter is used to specify the path of the flashed image
For example, there would be two method to flash kernel.img:
Rockusb>di -k ./kernel.img
Rockusb>di kernel ./kernel.img

600px|

UF Command: used for unity flashed image update.img
UF <Firmware>
The only parameter is used to specify the need to burn the firmware path.
For example, if my firmware path is:
RK3399_IMAGE/Image_Android6.0_20171228.img
Then the command should be:
Rockusb>uf RK3399_IMAGE/Image_Android6.0_20171228.img

600px|

After flashed, there would show the following information and the Orange Pi would reboot. (UF command would reboot, but not DI command.)

600px|

2)Write Scripts to Implement User-Defined Flash
upgrade_tool also supports used as Linux command for flashing, you only need to add the path of tool into environment variable.
For example, when debug Kernel, if you want to make it realize modify-compile-flash, you could also try the following:

# Compile part of the firmware of kernel it will generated kernel.img and resource.img
make -j2 rk3399-orangepi.img
# enter into Loader mode with adb command
adb shell rebot bootloader
# finished flashing with di Command
sudo upgrade_tool di resource resource.img
sudo upgrade_tool di kernel kernel.img
# reboot with rd Command
sudo upgrade_tool rd

FAQ of Image Flashing

• Cannot power on because of error firmware

Usually we could enter into LOADER mode to flashing hardware, however, if it cannot be powered on because of error firmware, we could try to use MASKROM mode to write image and boot.
1. Power off the device
2. Use metal tweezers to keep TP50265 and GND connected
3. Power on the board with DC
4. Wait a moment then release the metal tweezers
5. Use a micro USB Type-C cable to connect device and host PC
6. Device should enter MASKROM mode

600px|

600px|

It would show the following with AndroidTools on Windows:

600px|

After this could flash the image in the normal way.

It would show the following if use upgrade_tool on Linux:

600px|

It would be re-flash the image with uf command.
Principle:
It would clean data on flash if short connect pin and GND because the system would consider data error of flash.

Linux Environment Construction and Firmware Compilation

Download Linux Source Code

• OrangePi Souce Code Downloader

The Linux source for the Orange Pi RK3399 has been uploaded to GitHub, the kernel version is Linux 4.4, we can use it
Download with the downloader for OrangePi Linux source code, the method to get the downloader source code is as follows:

$ sudo apt-get install git
$ git clone https://github.com/orangepi-xunlong/OrangePi_Build.git
$ cd OrangePi_Build
$ ls
Build_OrangePi.sh lib README.md

• Run the downloader

$ ./Build_OrangePi.sh

Enter the root password and press Enter

600px|

Select 0 Build system with kernel/uboot/rootfs, enter the development board model selection interface.

600px|

Select 20 orangepi RK3399 and press Enter to start downloading the Linux source code for Orange Pi RK3399

600px|

The downloaded source code will be stored in the same directory of OrangePi_Build

$ ls ../
OrangePi_Build OrangePiRK3399

The Linux source code directory structure of OrangePi RK3399 is as follows

$ cd OrangePiRK3399
$ tree -L 1
.
├── build.sh -> scripts/build.sh Compile the startup script
├── external Store extra configuration files
├── kernel Linux kernel source
├── output Store output files
├── scripts Compile script
├── toolchain Cross compilation tool
└── uboot uboot source code

6 directories, 1 file

Compile Linux source code

• Execute the compile startup script

$ cd OrangePiRK3399
$ ./build.sh

Select Enter

600px|

Enter the root password and press Enter, then select the function needed to be executed

600px|

The functions of each option are as follows:

• 0 Build Release Image Compile Ubuntu or Debian Release image
• 1 Build Uboot Compile uboot source code
• 2 Build Linux Compile Linux kernel source code
• 3 Update kernel Image Update kernel

0 SD Card Update the kernel of Linux in SD card
1 EMMC Update the kernel of Linux in EMMC

• 4 Update Module Update the kernel module of Linux in SD card
• 5 Update Uboot

0 SD Card Update the uboot of Linux in SD card 1 EMMC Update the uboot of Linux in EMMC

600px|

After compiling u-boot and kernel source code,the final generated file will be stored in the output directory

Uboot image

$ tree -L 1 output/u-boot/
├── idbloader.img
├── rk3399_loader_v1.08.106.bin
├── trust.img
└── uboot.img

0 directories, 4 files

Kernel image

$ tree -L 1 output/kernel/
output/kernel/
├── Image
└── rk3399-orangepi.dtb

0 directories, 2 files

Rootfs Compilation

Refer to the chapter "Building a Compilation Environment and Making a Rootfs Image"

Execute the following steps to package the images of all partitions into one complete firmware:

$ cd scripts

Package Image and extlinux configuration files to generate boot.img, path in the output folder

$ ./mk-image.sh -c rk3399 -t boot -f emmc

c for chip,represent chip

t for target,represent the generated image name

s for size,represent the pre-allocated size when making the firmware (does not represent the actual final firmware size, the final firmware will be dynamically re-adjusted), unit Mbyte

r for rootfs，represent the used rootfs path

After the execution is completed, system.img is generated in the out directory as the final complete firmware.

Linux firmware flashing

Flash the complete linux firmware to the EMMC

1.Connect the DC power supply while short-connecting the Clk and GND of the EMMC. Enter the Maskrom mode. EMMC Clk is on the lower left corner of the miniPCIe on the back of the board shown as following picture

600px|

600px|

2.Connect the TypeC line
3.Execute the following command to flash

./flash_tool.sh -c rk3399 -p system -i ../output/system.img

c for chip，represent the chip model
p for partation，represent Partition，such as boot loader1 system
i for image，represent the image path
You can also flash different partitions separately, such as Separately flash boot：

./flash_tool.sh -c rk3399 -p boot -i ../output//boot.img

Separately flash uboot:

./flash_tool.sh -p loader1 -i ../output/u-boot/idbloader.img -c rk3399
./flash_tool.sh -p loader2 -i ../output/u-boot/uboot.img -c rk3399

Flash the linux image published in the official website

./flash_tool.sh -c rk3399 -p system -i \
OrangePi_rk3399_xenial_desktop_v1.0.img

Compile Linux SDK and Make Firmware

It is defaulted compilation under userdebug mode.
U-boot Compilation:

./build/mk-u-boot.sh rk3399-orangepi

There will be generated the following file on out/u-boot directory:
➜ tree ./out/u-boot
u-boot
├── idbloader.img
├── rk3399_loader_v1.08.106.bin
├── trust.img
└── uboot.img

Kernel Compilation:

./build/mk-kernel.sh rk3399-orangepi

There will be generated the following file on out directory
➜ tree ./out/kernel
├── boot.img
└── kernel

   ├── Image

└── rk3399-orangepi.dtb
Rootfs Compilation:

You could use different Rootfs, what have already compiled just like the following which could be used directory:

Ubuntu16.04 Desktop version: ubuntu-desktop.img

Ubuntu16.04 Server version: ubuntu-server.img

Ubuntu16.04 LXDE version: ubuntu-lxde.img

Debian9 Desktop version: debian-desktop.img

You could also make your own Rootfs with reference of OrangePi RK3399 Rootfs Construction.

Pack every partitions’ image into a unity full firmware:

./build/mk-image.sh -c rk3399 -t system -s 4000 -r out/ubuntu-server.img

c for chip, represents the chip model
t for target, represents the generated image name
s for size, represents the predistribution size(but it does not means the final real size. The firmware will Redynamic adjustment the size), unit: Mbyte
r for rootfs, represents the path used by rootfs After execute the above command, there will be generate the unity full firmware(system.img ) on the directory of out.

Flash Linux Firmware

Flash the full Linux firmware into eMMC:
1.Short circuit connecting with Clk and GND of EMMC, connect DC power supply, enter into Maskrom mode.
EMMC Clk is like the following shows:

600px|

600px|

2.Connect TypeC cable with PC and RK3399
3.Execute the following command to flash

./build/flash_tool.sh -c rk3399 -p system -i out/system.img

c for chip, represents chip model

p for partition, represents partition, such as boot loader1 system

i for image, represents path of image

You could also flash different partitions separately, for example:

Separate flashing boot:

./build/flash_tool.sh -c rk3399 -p boot -i out/boot.img

Separate flashing uboot:

./build/flash_tool.sh -p loader1 -i out/u-boot/idbloader.img -c rk3399
./build/flash_tool.sh -p loader2 -i out/u-boot/uboot.img -c rk3399
./build/flash_tool.sh -p atf -i out/u-boot/trust.img -c rk3399

Construct Compilation Environment and Make Rootfs Image

Construct Compilation Environment

sudo apt-get update
sudo apt-get install qemu-user-static

If your development environment is not Ubuntu16.04, please make sure the gcc-arm-linux-gnueabihf and gcc-aarch64-linux-gnu compile tool train less than 6.0.

mkdir rootfs
sudo tar -xpf ubuntu-base-16.04.1-base-arm64.tar.gz -C rootfs

Modify Rootfs and Add Customize Software

sudo cp -b /etc/resolv.conf rootfs/etc/resolv.conf
sudo cp /usr/bin/qemu-aarch64-static rootfs/usr/bin/
# Enter into root system
sudo chroot rootfs /bin/bash

# Update software library and install software
apt update
apt upgrade
# according to you installation need
apt install build-essential vim ping ssh, etc.
# Install desktop version, it would take a little long time, please keep the network smooth.
# It would be Server version if do not execute
apt install ubuntu-desktop

# Add user and set password
useradd -s '/bin/bash' -m -G adm,sudo orangepi
# Set password for user orangepi
passwd orangepi
# Set password for rootpasswd root

# exit Rootfs
exit

Make Rootfs Image

# Generate spare image file
dd if=/dev/zero of=ubuntu-desktop.img bs=1M count=2048

# Format image file into ext4 format
sudo mkfs.ext4 ubuntu-desktop.img

# Load image file to ubuntu-desktop folder
mkdir ubuntu-desktop
sudo mount ubuntu-desktop.img ubuntu-desktop/

# copy the generated rootfs contents into folder which image loaded
sudo cp -rfp rootfs/* ubuntu-desktop/

# Unmount
sudo umount ubuntu-desktop/

# Check the correctness of the file system
e2fsck -p -f ubuntu-desktop.img

# Automatically adjust the size of the partition
resize2fs -M ubuntu-desktop.img

Using Debug tools on OrangePi

Hardware: RK3399 and TTL to USB cable

Operation Steps on Windows

1) Install USB driver on Windows

• Download and unzip the latest version of driver PL2303_Prolific_DriverInstaller_v130.zip

600px|

• Choose application installation as Administrator

600px|

• Wait for completing installation

600px|

2)Secure CRT Usage on Windows Use TTL to USB cable to connect RK3399 and PC, you could download securecrs_33lc tool of RK3399 from official website on the download section.
Click SecureCRTPortable after unzip the package, it would show like the following:

600px|

Select serial on Protocol, select corresponding port of your PC on port(you could use device manager to check the port number). On my PC it is COM6, input baud rate of 1500000, not click RTS/CTS.

600px|

Click connect and boot the board, there will print the debug log:

600px|

Operation Steps on Linux

There are minicom and kermit for debug on Linux, here we will make exampleofminicom since kermit do not support baud rate at 1500000. Connect RK3399 and PC with TTL cable.

• Install and configure minicom

Device node of serial port:

ls /dev/ttyUSB*

300px|

Device node is ttyUSB0
Execute command on the terminal and install minicom
sudo apt-get install minicom
After installation, configure minicom, input sudo minicom -s on the terminal

400px|

Select Serial port setup and press Enter, it will show like the following:

600px|

Press a to configure Serial Device as serial port device node, what I am working at is ttyUSB0, then press Enter. Press f to not click RTS/CTS. Press e will show the configure window like the following:

600px|

600px|

Select Save setup as dfl, press Enter and save it, then press ESC to exit.

600px|

Boot RK3399 it will print the log:

600px|