NanoPi M6

查看中文

1 Introduction

Overview

Front

Back

Case

Case

Case

Case

The NanoPi M6 (as “M6”) is an open-sourced mini SBC device, designed and developed by FriendlyElec.It is based on Rockchip RK3588S SoC, with 64-bits LPDDR5 RAM, and eMMC flash Socket. It supports booting with TF cards and works with operating systems such as FriendlyWrt, Android, Debian, Ubuntu etc and works with headless systems as well.

The NanoPi M6 has rich hardware resources with a compact size of 90 x 62 mm, a 30-pin header is provided to expose hardware resources for secondary development, including interfaces such as GPIO, I2C, I2S, PWM and SPI, It alsa has one HDMI port. It supports decoding 8K@60fps H.265/VP9 and 8K@30fps H.264 formatted videos.

The NanoPi M6 has one M.2 NVME port and three USB ports, and supports USB type-C power delivery. It is an ideal portable drive for saving images and videos. FriendlyElec has released a carefully-designed custom CNC housing for it.

All in all, the NanoPi M6 is a board featured with multiple Ethernet ports, light NAS and video playing. It is a cannot-miss platform with infinite possibilities for geeks, fans and developers.

2 Hardware Spec

• SoC: Rockchip RK3588S
  • CPU: Quad-core ARM Cortex-A76(up to 2.4GHz) and quad-core Cortex-A55 CPU (up to 1.8GHz)
  • GPU: Mali-G610 MP4, compatible with OpenGLES 1.1, 2.0, and 3.2, OpenCL up to 2.2 and Vulkan1.2
  • VPU: 8K@60fps H.265 and VP9 decoder, 8K@30fps H.264 decoder, 4K@60fps AV1 decoder, 8K@30fps H.264 and H.265 encoder
  • NPU: 6TOPs, supports INT4/INT8/INT16/FP16
• RAM: 64-bit LPDDR5 at 2400MHz
• Flash: eMMC module socket, at HS400 mode
• Ethernet: 1x Native Gigabit Ethernet
• USB: 1x USB 3.0 Type-A and 2x USB 2.0 Type-A
• M.2 Connectors
  • one M.2 M-Key connector with PCIe 2.1 x1 for SSDs
  • one M.2 E-key connector with PCIe 2.1 x1 and USB2.0 Host for Wi-Fi&BT
• microSD: support up to SDR104 mode
• Video input:
  • 1x 4-lane MIPI-CSI V1.2
  • 1x 4-lane MIPI-CSI D/C PHY
• Video output:
  • 1x Standard HDMI output ports
    • compatible with HDMI2.1, HDMI2.0, and HDMI1.4 operation
    • support displays up to 7680x4320@60Hz
    • Support RGB/YUV(up to 10bit) format
  • 2x 4-lane MIPI-DSI, compatible with MIPI DPHY 2.0 or CPHY 1.1
• Audio:
  • 1x 3.5mm jack for stereo headphone output
  • 1x 2.0mm PH-2A connector for analog microphone input
• GPIO:
  • 30-pin 2.54mm header connector
  • up to 1x SPI, 6x UARTs, 3x I2Cs, 1x SPDIFs, 4x PWMs, 20x GPIOs
• Debug: UART via 3-Pin 2.54mm header
• LEDs: 2 x GPIO Controlled LED (SYS, LED1)
• others:
  • 2 Pin 1.27/1.25mm RTC battery input connector for low power RTC IC HYM8563TS
  • Buttons: MASK, Reset, Recovery, Power
  • one 5V Fan connector
• Power supply: USB-C, support PD and DC, 6V~20V input
• PCB: 8 Layer, 62x90x1.6mm
• Ambient Operating Temperature: 0℃ to 70℃

3 Diagram, Layout and Dimension

3.1 Layout

NanoPi M6 Layout

• 30-pin GPIO

Pin#	Assignment	Pin#	Assignment
1	VCC_3V3_S3*	2	VCC_5V0*
3	I2C8_SDA_M2	4	VCC_5V0*
5	I2C8_SCL_M2	6	GND
7	GPIO4_B0/UART8_TX_M0	8	GPIO3_C4/UART5_TX_M1
9	GND	10	GPIO3_C5/UART5_RX_M1
11	GPIO4_B1/UART8_RX_M0	12	GPIO4_B3/UART8_CTSN_M0_PWM15_M1
13	GPIO4_A3/UART0_RX_M0	14	GND
15	GPIO4_A4/UART0_TX_M0	16	GPIO0_D4/I2C1_SCL_M2/PWM3_IR_M0
17	VCC_3V3_S3*	18	GPIO0_D5/I2C1_SDA_M2
19	GPIO1_B2/SPI0_MOSI_M2/UART4_RX_M2	20	GND
21	GPIO1_B1/SPI0_MISO_M2	22	GPIO4_B2/UART8_RTSN_M0_PWM14_M1
23	GPIO1_B3/SPI0_CLK_M2/UART4_TX_M2	24	GPIO1_B4/SPI0_CS0_M2/UART7_RX_M2
25	GND	26	GPIO1_B5/SPI0_CS1_M2/UART7_TX_M2
27	GPIO0_C4/PWM2_M0	28	GPIO1_A0/UART6_RX_M1
29	GPIO1_A1/UART6_TX_M1	30	GND

The logic level of all signals is 3.3V.

VCC_3V3_S3 is 3.3V output with a maximum output of 500mA.

VCC_5V0 is 5V output with a maximum output of 1A.

• MIPI-DSI

0.5mm FPC Connector

Pin#	MIPI-DSI0	MIPI-DSI1	Description
1,2,3	VCC_5V0	VCC_5V0	5V Power ouput
4,7,9,11,15,18,21,24,27,30	GND	GND	Power and Signal Ground
5	I2C4_SDA_M3	I2C5_SDA_M2	3.3V, I2C Data, pulled up to 3.3V with 2.2K on M6
6	I2C4_SCL_M3	I2C5_SCL_M2	3.3V, I2C Clock, pulled up to 3.3V with 2.2K on M6
8	GPIO3_C0	GPIO4_A0	3.3V, GPIO
10	GPIO3_D3/PWM10_M2	GPIO3_D5/PWM11_M3	3.3V, GPIO/PWM
12	GPIO3_D2	GPIO4_A1	3.3V, GPIO
13	/NC	/NC	No Connection
14	GPIO3_C1	GPIO4_A2	3.3V, GPIO
16	MIPI_PHY0_TX_D3N	MIPI_PHY1_TX_D3N	MIPI TX Lane3 ouput N
17	MIPI_PHY0_TX_D3P	MIPI_PHY1_TX_D3P	MIPI TX Lane3 ouput P
19	MIPI_PHY0_TX_D2N	MIPI_PHY1_TX_D2N	MIPI TX Lane2 ouput N
20	MIPI_PHY0_TX_D2P	MIPI_PHY1_TX_D2P	MIPI TX Lane2 ouput P
22	MIPI_PHY0_TX_D1N	MIPI_PHY1_TX_D1N	MIPI TX Lane1 ouput N
23	MIPI_PHY0_TX_D1P	MIPI_PHY1_TX_D1P	MIPI TX Lane1 ouput P
25	MIPI_PHY0_TX_D0N	MIPI_PHY1_TX_D0N	MIPI TX Lane0 ouput N
26	MIPI_PHY0_TX_D0P	MIPI_PHY1_TX_D0P	MIPI TX Lane0 ouput P
28	MIPI_PHY0_TX_CLKN	MIPI_PHY1_TX_CLKN	MIPI TX Clock ouput N
29	MIPI_PHY0_TX_CLKP	MIPI_PHY1_TX_CLKP	MIPI TX Clock ouput P

• MIPI-CSI

0.5mm FPC Connector

Pin#	MIPI-CSI0	MIPI-DCSI0	Description
1,2	VCC_5V0	VCC_5V0	5V Power ouput
3,13,15,18,21,24,27,30	GND	GND	Power and Signal Ground
4	MIPI_CSI0_RX_CLK1P	/NC
5	MIPI_CSI0_RX_CLK1N	/NC
6	VCC_1V8_S3	VCC_1V8_S3	1.8V Power ouput, 100mA Max
7	/NC	/NC	No Connection
8	VSYNC_MASTER	VSYNC_SLAVE	Have been Connected together on M6 for sensor synchronization
9	I2C3_SCL_M0	I2C7_SCL_M0	1.8V, I2C Clock, pulled up to 1.8V with 2.2K on M6
10	I2C3_SDA_M0	I2C7_SDA_M0	1.8V, I2C Data, pulled up to 1.8V with 2.2K on M6
11	GPIO1_C6	GPIO1_D2	1.8V, GPIO
12	GPIO1_D5	GPIO1_D3	1.8V, GPIO
14	MIPI_CAMCLK1_M0	MIPI_CAMCLK2_M0	1.8V, CLock ouput for Sensor
16	MIPI_CSI0_RX_D3P	MIPI_PHY0_RX_D3P	MIPI RX Lane3 iuput P
17	MIPI_CSI0_RX_D3N	MIPI_PHY0_RX_D3N	MIPI RX Lane3 iuput N
19	MIPI_CSI0_RX_D2P	MIPI_PHY0_RX_D2P	MIPI RX Lane2 iuput P
20	MIPI_CSI0_RX_D2P	MIPI_PHY0_RX_D2N	MIPI RX Lane2 iuput N
22	MIPI_CSI0_RX_D1P	MIPI_PHY0_RX_D1P	MIPI RX Lane1 iuput P
23	MIPI_CSI0_RX_D1N	MIPI_PHY0_RX_D1N	MIPI RX Lane1 iuput N
25	MIPI_CSI0_RX_CLK0P	MIPI_PHY0_RX_CLKP	MIPI RX Clock iuput P
26	MIPI_CSI0_RX_CLK0N	MIPI_PHY0_RX_CLKN	MIPI RX Clock iuput N
28	MIPI_CSI0_RX_D0P	MIPI_PHY0_RX_D0P	MIPI RX Lane0 iuput P
29	MIPI_CSI0_RX_D0N	MIPI_PHY0_RX_D0N	MIPI RX Lane0 iuput N

• Debug UART Pin Spec

3.3V level signals, 1500000bps

Pin#	Assignment	Description
1	GND	0V
2	UART2_TX_M0_DEBUG	output
3	UART2_RX_M0_DEBUG	intput

• USB-A Port

Each USB 2.0 Type-A port has 1A overcurrent protection.

The USB 3.0 Type-A port has 1.4A overcurrent protection.

• RTC

RTC backup current is 0.25μA TYP (VDD =3.0V, TA =25℃).

Connector P/N: Molex 53398-0271

4 Get Started

4.1 Essentials You Need

Before starting to use your NanoPi-M6 get the following items ready

• NanoPi-M6
• MicroSD Card/TF Card: Class 10 or Above, minimum 8GB SDHC
• USB C PD Charger (10W & above)
• If you need to develop and compile,you need a computer that can connect to the Internet. It is recommended to install Ubuntu 20.04 64-bit system and use the following script to initialize the development environment, or use docker container:
  
  • How to setup the Compiling Environment on Ubuntu bionic
    
  • docker-cross-compiler-novnc
    

4.2 TF Cards We Tested

Refer to： TFCardsWeTested

4.3 Configure parameters for serial port

Use the following serial parameters:

Baud rate	1500000
Data bit	8
Parity check	None
Stop bit	1
Flow control	None

4.4 PD Power Adapters We Tested

Refer to： PD Power Adapters We Tested

4.5 Install OS

4.5.1 Downloads

4.5.1.1 Official image

Visit download link to download official image files (in the "01_Official images" directory).
The table below lists all official images, the word 'XYZ' in image filename meaning:

• sd: Use it when you need to boot the entire OS from the SD card
• eflasher: Use it when you need to flash the OS to eMMC via TF card
• usb: Use it when you need to flash the OS to eMMC via USB

Icon	Image Filename	Version	Description	Kernel Version
	rk3588-XYZ-debian-bookworm-core-6.1-arm64-YYYYMMDD.img.gz	bookworm	Debian 12 Core, command line only	6.1.y
	rk3588-XYZ-debian-bullseye-minimal-6.1-arm64-YYYYMMDD.img.gz	bullseye	Debian 11 Desktop, Xfce desktop, no pre-installed recommended software, supports HW acceleration	6.1.y
	rk3588-XYZ-debian-bullseye-desktop-6.1-arm64-YYYYMMDD.img.gz	bullseye	Debian 11 Desktop, Xfce desktop, pre-installed mpv, smplayer and chromium brower, supports HW acceleration	6.1.y
	rk3588-XYZ-ubuntu-focal-desktop-6.1-arm64-YYYYMMDD.img.gz	focal	Ubuntu 20.04 Desktop, LXQT desktop, pre-installed mpv, smplayer and chromium brower, supports HW acceleration	6.1.y
	rk3588-XYZ-ubuntu-noble-desktop-6.1-arm64-YYYYMMDD.img.gz	noble	Ubuntu 24.04 with GNOME and Wayland with recommended software	6.1.y
	rk3588-XYZ-ubuntu-noble-minimal-6.1-arm64-YYYYMMDD.img.gz	noble	Lightweight Ubuntu 24.04 with GNOME and Wayland	6.1.y
	rk3588-XYZ-ubuntu-jammy-x11-desktop-arm64-YYYYMMDD.img.gz	jammy	Ubuntu 22.04 with Xubuntu and X11, use Panfrost GPU driver	6.1.y
	rk3588-XYZ-friendlycore-focal-6.1-arm64-YYYYMMDD.img.gz	focal	FriendlyCore，command line only, pre-installed Qt5， based on Ubuntu core 20.04	6.1.y
	rk3588-XYZ-androidtv-YYYYMMDD.img.zip	12	Android 12 TV	5.10.y
	rk3588-XYZ-android12-YYYYMMDD.img.zip	12	Android 12 Tablet	5.10.y
	rk3588-XYZ-openmediavault-6.1-YYYYMMDD.img.gz	Shaitan	OpenMediaVault NAS system, base on Debian 12	6.1.y
	rk3588-XYZ-proxmox-6.1-YYYYMMDD.img.gz	8.2.7	Proxmox VE OS (Preview), base on Debian 12	6.1.y
	rk3588-XYZ-friendlywrt-21.02-YYYYMMDD.img.gz	21.02	FriendlyWrt, based on OpenWrt 21.02	6.1.y
	rk3588-XYZ-friendlywrt-21.02-docker-YYYYMMDD.img.gz	21.02	FriendlyWrt with Docker, based on OpenWrt 21.02	6.1.y
	rk3588-XYZ-friendlywrt-23.05-YYYYMMDD.img.gz	23.05	FriendlyWrt, based on OpenWrt 23.05	6.1.y
	rk3588-XYZ-friendlywrt-23.05-docker-YYYYMMDD.img.gz	23.05	FriendlyWrt with Docker, based on OpenWrt 23.05	6.1.y
Other Image
	Github Actions - FriendlyWrt	21.02,23.05	FriendlyWrt	6.1.y
	rk3588-eflasher-multiple-os-YYYYMMDD-25g.img.gz	-	It contains multiple OS image files, making it convenient for testing different operating systems, this image disables automatic flashing at startup; you will need to manually select the OS to flash.

4.5.1.2 Tools (optional)

Visit download link to download tools (in the "05_Tools" directory).

Filename	Description
win32diskimager.rar	This program is designed to write a raw disk image to a removable device or backup a removable device to a raw image file
SD Card Formatter	A program (application) that allows easy and quick clear the SD card
RKDevTool_Release_v2.84.zip	Rockchip flashing tool, for USB upgrade

4.5.2 Flashing the OS to the microSD card

Follow the steps below:

• Get an 8G microSD card;
• Visit download linkto download image files (in the "01_Official images/01_SD card images" directory);
• Download the win32diskimager tool (in the "05_Tools" directory), or use your preferred tool;
• Extract the .gz format compressed file to get the .img format image file;
• Run the win32diskimager utility under Windows as administrator. On the utility's main window select your SD card's drive, the wanted image file and click on "write" to start flashing the SD card.
• Take out the SD and insert it to NanoPi-M6's microSD card slot;
• Power on NanoPi-M6 and it will be booted from your TF card, some models may require pressing the Power button to start;

4.5.3 Install OS to eMMC

4.5.3.1 Option 1: Install OS via TF Card

This method firstly boots a mini Linux from a TF card and then automatically runs an EFlasher utility to install the OS to eMMC. You can connect your system to an HDMI monitor and watch its progress.
This is optional. You can watch its progress by observing its LEDs as well:

By default, flashing starts automatically upon power-up, so be sure to back up the data in eMMC. If you don't want it to start automatically, you can use image file with a filename containing the words 'multiple-os' and manually select the OS you want to flash on the interface.

4.5.3.1.1 Flash Official OS to eMMC

Follow the steps below:

• Get an SDHC card with a minimum capacity of 8G
• Visit download linkto download image files (in the "01_Official images/02_SD-to-eMMC images" directory) and win32diskimager tool (in the "05_Tools" directory);
• Extract the .gz format compressed file to get the .img format image file;
• Run the win32diskimager utility under Windows as administrator. On the utility's main window select your SD card's drive, the wanted image file and click on "write" to start flashing the SD card.
• Eject your SD card and insert it to NanoPi-M6’s microSD card slot.
• Turn on NanoPi-M6, it will boot from the SD card and automatically run EFlasher to install the OS to the board’s eMMC.
• After flashing is complete, eject the SD card from NanoPi-M6, NanoPi-M6 will automatically reboot and boot from eMMC.

4.5.3.1.2 Flash third party OS (Image file) to eMMC

• Auto Install (Default Behavior)

1) Download an “eflasher” firmware from network drive(in the "01_Official images/02_SD-to-eMMC images" directory), extract it and install it to a TF card ;
2) Eject and insert the TF card to your PC, after a “FriendlyARM” device shows up(Under Linux, it is a “FriendlyARM” directory), copy the image file ending with .raw or .gz into the directory (Note: if your file is in .img format, please rename it to .raw format).
3) Open the eflasher.conf file on the TF card, set “autoStart=” to the name of your image file, such as:

autoStart=openwrt-rockchip-armv8_nanopi-ext4-sysupgrade.img.gz

In addition to third-party image, official image files which with the '-sd-' word in the filename are also supported, for example: rk3NNN-sd-friendlywrt-21.02-YYYYMMDD.img.gz
4) Eject the TF card, insert the TF card to NanoPi-M6, power it on it will automatically install your firmware. You can watch the installation progress by observing the LEDs’ status.

4.5.3.2 Option 2: Install OS on Web Page

Get a TF card which has been installed with FriendlyWrt, log in FriendlyWrt on the web page, click on “System” ->”eMMC Tools”. Click on “Select file” to select your wanted image file, either an official image (filename containing '-sd-') or a third party image. The file should be a “.gz” or “.img” file.
After a file is selected, click on “Upload and Write” to start installing an OS.

After installation is done, eject the SD card, the system will automatically reboot and load the OS from eMMC. After the OS begins to load, if the system LED is flashing and the network LED is on, it means the the OS has loaded successfully. If the OS is FriendlyWrt, you can click on “Go to Homepage” to enter the homepage.
For official OS, you need select the file with the filename containing '-sd-', for example: rk3NNN-sd-friendlywrt-21.02-YYYYMMDD.img.gz, the compression file only supports the .gz format. If the file is too large, you can compress it into .gz format before uploading.

4.5.3.3 Option 3: Install OS via USB

4.5.3.3.1 Step 1: Install USB Driver and Tools/Utilities

Download a driver file DriverAssitant_v5.12.zip under the “tools” directory from network drive, extract and install it.
Under the same directory, download a utility RKDevTool_Release_v2.84.zip and extract it.

4.5.3.3.2 Step 2: Connect NanoPi-M6 to PC and Enter Installation Mode

Press and hold the “Mask” key, Use a USB cable, connect NanoPi-M6 to a PC，After the status LED has been on for at least 3 seconds, release the Mask key;

4.5.3.3.3 Step 3: Install image to eMMC

A firmware in general is packaged in either of the two options: the first is an whole image (ie, update.img) which is often offered by third party developers, the second is that an image is packaged and placed in multiple partition images. FriendlyElec offers an image in the latter option.

• Option 1: Install whole image (ie, update.img)
  

On a PC which has the extracted RKDevTool_Release_v2.84 utility, go to the RKDevTool_Release_v2.84 directory, run the RKDevTool.exe file. If everything works, you will see a “Found a new Maskrom device” message on the utility;
Go to “Upgrade Firmware(升级固件)”, click on “Firmware(固件)”, select your wanted image file, and click on “Upgrade(升级)” to install. After installation is done, your board will reboot automatically and load the system from eMMC;

• Option 2: Install OS that is packaged & placed in multiple partition images
  

Go to network drive to download your needed package and extract it (in the "01_Official images/03_USB upgrade images). After it is extracted, you will see some utilities and a configuration file under the directory. double click on RKDevTool.exe, you will see a “Found a new Maskrom device” message on the utility. Click on the “Execute”, wait a moment and it will be installed. After installation is done your system will automatically reboot and load the system from eMMC.

4.5.4 Installing the System to M.2 or USB Drive

You can use a TF card to boot the eFlasher system, allowing the boot and system to be installed on different storage devices. However, since the CPU doesn’t support booting directly from M.2 and USB devices, the system can be installed on M.2 and USB devices, but the boot must still be installed on eMMC or a TF card.
Steps are as follows:

• Prepare a TF card with a capacity of 32GB or larger.
• Visit [the download link here](http://download.friendlyelec.com/NanoPiM6) to download the firmware file named XXXX-eflasher-multiple-os-YYYYMMDD-30g.img.gz (located in the “01_Official images/02_SD-to-eMMC images” directory).
• Flash the firmware to the TF card, connect the storage device you intend to use on NanoPi-M6, insert the TF card and power on, we need to perform the operations in the eFlasher GUI. If your NanoPi-M6 does not have a display interface, you can use VNC; refer to Using VNC to Operate eFlasher.
• In the eFlasher GUI, select the OS to install, and in the OS settings interface, choose the destination for boot installation (typically eMMC), then choose the destination for system installation (options include eMMC, M.2 hard drive, USB storage, etc.), as shown below:

• If no eMMC is available, the TF card can serve as the boot by inserting another TF card into the USB port via a USB card reader and selecting it as the boot destination, enabling booting from the TF card with the system stored on the M.2 or USB drive.
• After flashing, eject the SD card from NanoPi-M6. If booting from eMMC, NanoPi-M6 will automatically restart into the newly flashed system. If boot installation is on a TF card, power off, insert the boot TF card, and power on again.
• For a more detailed installation guide, please refer to this link.

5 Work with Ubuntu 22.04 Desktop

5.1 Introduction to Ubuntu 22.04 Desktop

Ubuntu 22.04 Desktop has the following features：

• Uses GNOME 42 as default desktop;
  
• Uses Wayland as default display server;
  
• Mali GPU-based OpenGL ES support;
  
• Support Rockhip MPP video hard coding and hard decoding;
  
• Pre-installed mpv and kodi, support video hardware decoding;
  
• Compatible with Docker and Plex server;
  

5.2 Account & Password

Regular Account:
    User Name: pi
    Password: pi

Root:
    User Name: root
    Password: fa

5.3 View IP address

Since the hostname is FriendlyElec.lan by default, you can use the ping command to get the IP address:

ping FriendlyElec.lan

5.4 Connect to Ubuntu via SSH

ssh pi@FriendlyElec.lan

The default password is: pi

5.5 Update Software Packages

$ sudo apt-get update

5.6 Install Ubuntu software center

$ sudo apt-get install snapd
$ sudo snap install snap-store

5.7 Install the kernel-header package

sudo dpkg -i /opt/linux-headers-*.deb

try to compile a kernel module:

sudo apt update
sudo apt install git gcc make bc
git clone https://github.com/RinCat/RTL88x2BU-Linux-Driver.git
cd RTL88x2BU-Linux-Driver
make -j$(nproc)
sudo make install
sudo modprobe 88x2bu

5.8 Change time zone

5.8.1 Check the current time zone

timedatectl

5.8.2 List all available time zones

timedatectl list-timezones

5.8.3 Set the time zone (e.g. Shanghai)

sudo timedatectl set-timezone Asia/Shanghai

5.9 Change startup LOGO and Wallpaper

5.9.1 Change startup LOGO

Replace the following two files in the kernel source code directory and recompile the kernel：
kernel/logo.bmp
kernel/logo_kernel.bmp
Or use the script to operate, as shown below：

• Download scripts:

git clone https://github.com/friendlyarm/sd-fuse_rk3399.git -b kernel-4.19
cd sd-fuse_rk3399

• Compile kernel and repackage firmware

convert files/logo.jpg -type truecolor /tmp/logo.bmp
convert files/logo.jpg -type truecolor /tmp/logo_kernel.bmp
LOGO=/tmp/logo.bmp KERNEL_LOGO=/tmp/logo_kernel.bmp ./build-kernel.sh ubuntu-jammy-desktop-arm64
./mk-emmc-image.sh ubuntu-jammy-desktop-arm64

5.10 Soft Factory Reset

Execute the following command in a terminal:

sudo firstboot && sudo reboot

5.11 Start the program automatically at startup(For example Firefox)

Put the desktop file in the ~/.config/autostart/ directory, for example：

mkdir ~/.config/autostart/
cp /usr/share/applications/firefox.desktop ~/.config/autostart/

5.12 Disable auto-mounting

sudo systemctl mask udisks2
sudo reboot

5.13 Setup Chinese language and Input method

5.13.1 Setup Chinese language

Enter the following command and select 'zh_CN.UTF-8':

sudo dpkg-reconfigure locales

Add environment variables to .bashrc:

echo "export LC_ALL=zh_CN.UTF-8" >> ~/.bashrc
echo "export LANG=zh_CN.UTF-8" >> ~/.bashrc
echo "export LANGUAGE=zh_CN.UTF-8" >> ~/.bashrc

Reboot device:

sudo reboot

5.14 Video playback with hardware decoding

5.14.1 GUI

• Locate the video file in the file browser, right click and select "Play with mpv media player"
• Using Kodi player
• Using Chromium web browser, you can play videos on the web with hardware decoding (limited to the video formats supported by the CPU)

5.14.2 Command line

• Play local video file

export DISPLAY=:0.0
mpv --fs /home/pi/Videos/demo.mp4

• Play web-video

export DISPLAY=:0.0
mpv --fs https://www.youtube.com/watch?v=lK-nYDmC1Dk

5.15 How to Install Plex Media Server

Run the following command to install:

echo deb https://downloads.plex.tv/repo/deb public main | sudo tee /etc/apt/sources.list.d/plexmediaserver.list
curl https://downloads.plex.tv/plex-keys/PlexSign.key | sudo apt-key add -
sudo apt update
sudo apt install plexmediaserver

After successful installation, enable Plex (starts automatically at system startup):

sudo systemctl enable plexmediaserver
sudo systemctl start plexmediaserver
sudo systemctl status plexmediaserver

After installation, login to Plex server by entering the following address in your computer browser: http://IPAddress:32400/web/

5.16 Install Docker Engine

5.16.1 Install Docker Engine

sudo apt install apt-transport-https ca-certificates curl software-properties-common gnupg lsb-release
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt update
sudo apt install docker-ce docker-ce-cli containerd.io docker-compose-plugin

Let’s verify:

sudo docker info

5.16.2 Run Docker as a non-root user

sudo groupadd docker
sudo gpasswd -a ${USER} docker
sudo systemctl restart docker
sudo chmod a+rw /var/run/docker.sock

Let’s verify:

docker images

5.16.3 Testing Docker: Installing Nextcloud with docker

mkdir ~/nextcloud -p
docker run -d -p 8888:80  --name nextcloud  -v ~/nextcloud/:/var/www/html/ --restart=always --privileged=true  arm64v8/nextcloud

After installation, visit: http://Device-IP-Address:8888 on your computer browser to view the nextcloud web page.

5.17 Disable Automatic Login

Edit the /etc/gdm3/custom.conf file, set AutomaticLoginEnable to false:

[daemon]
AutomaticLoginEnable = false

5.18 WiFi Connection

5.18.1 Gui

Click on the icon on the top right in the FriendlyDesktop's main window, select your wanted WiFi hotspot and proceed with prompts

5.18.2 Console

Please visit: Use NetworkManager to configure network settings

5.19 Test OpenGL ES

First, change the CPU governor to performance:

sudo sh -c 'echo performance > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor'
sudo sh -c 'echo performance > /sys/devices/system/cpu/cpufreq/policy4/scaling_governor'
sudo sh -c 'echo performance > /sys/devices/system/cpu/cpufreq/policy6/scaling_governor'

Start glmark2-es2-wayland:

glmark2-es2-wayland

5.20 Chromium web browser

5.20.1 GPU

Chromium web browser has enabled hardware acceleration by default, supports WebGL, and can view hardware acceleration details by entering the URL chrome://gpu, as shown below:

5.20.2 VPU

Play a video in the browser, then use fuser on the command line to view the mpp device node to confirm that the vpu interface is being called:

pi@FriendlyElec:~$ fuser /dev/mpp_service
/dev/mpp_service:     3258

If there is no content output from the fuser command, it means software decoding.

5.20.3 Check Supported Hardware Decoding Formats

Enter about://gpu in your browser's address bar and scroll to the bottom of the page to view the "Video Acceleration Information" table.
After playing a video, enter about://media-internals in your browser's address bar to check if hardware decoding was enabled for the most recent playback.

6 Work with Android

Android include the following features:

• There are two versions, TV and Tablet;
  
• Support infrared remote control (only for models with Ir Receiver);
  
• Support Bluetooth remote control (requires USB or M.2 Bluetooth module);
  
• Support wired network;
  
• Support WiFi (requires external USB or M.2 WIFI module);
  
• Support video hard decoding;
  

6.1 WiFi models supported by Android

6.1.1 M.2 WiFi Module

• RTL8822CE

6.1.1.1 Usb Dongle

• RTL8821CU (Vid: 0BDA, Pid: C811) (Test sample:TP-Link TL-WDN5200H)
• RTL8812AU (Vid: 0BDA, Pid: 8812)
• MediaTek MT7662 (Vid: 0E8D, Pid: 7612) (Test sample:COMFAST CF-WU782AC V2)

6.2 Bluetooch models supported by Android

6.2.1 Bluetooth Adapters

• RTL8822CE
• RTL8761B
• CSR8510 A10 Bluetooth Dongle 0a12:0001

(Note: unsupported device ID 0x2B89:0x8761)

6.2.2 Bluetooth Remote

• Amazon Fire TV Remote

6.3 How to use ADB

6.3.1 USB connection

Please note: After turning on the ADB, the USB3 port will work in Device mode, if you need to connect a device such as a USB stick, you need to turn off the ADB and restart the board
In general, ADB is disabled by default, please follow the steps below to enable it:

• Connect your development board to your computer using a USB A-to-A data cable, referring to the figure below, be sure to connect it to the USB port closest to the edge:
  

6.3.2 For Android Tablet

• Go to Settings -> About tablet -> tap the "Build number" at the bottom of the screen 7 times in a row;
• Go to Settings -> System -> Advance -> Developer options, check USB-Debugging, and then reboot;
• To use ADB over the network, you need to connect to WiFi first, then enable Wireless debugging. In the prompt "Allow wireless debugging on the network", select "Always allow on this network", and then click "Allow".

6.3.3 For Android TV

• Click the Settings icon -> Device Preferences -> About -> tap the "Android TV OS build" at the bottom of the screen 7 times in a row;
• Click the Settings icon -> Device Preferences -> Developer options, check USB-Debugging, and then reboot;
• To use ADB over the network, on Android TV, which supports both WiFi and wired networks, enable network ADB by checking "Internet ADB" on the "Developer options" UI.

6.3.4 Using ADB

• Install ADB drivers and commands based on your operating system;
• Normally, the Android status bar will prompt "USB debugging connected", indicating that ADB has been enabled. Enter the following command on your computer to check the connection：

$ adb devices
List of devices attached
27f7a63caa3faf16	device

• Enter adb shell:

$ adb shell
nanopi3:/ $

6.3.5 Using ADB over the network

• On an Android Tablet, go to Settings -> System -> Advance -> Developer options, then click on Wireless debugging to view the IP address and port.
• The default network ADB port for Android TV is 5555.

Assuming the IP address and port displayed on the Wireless debugging interface are 192.168.1.167:45055, the ADB commands are as follows:

• To connect to the device:

$ adb connect 192.168.1.167:45055

connected to 192.168.1.167:45055

• To enter ADB shell:

$ adb shell
nanopi3:/ $

If there are multiple devices, use the -s parameter to specify the device's IP and port, as shown below:

$ adb -s 192.168.1.167:45055 shell
nanopi3:/ $

6.4 How to Change Default Launcher in Android TV

• Refer to the previous section to enable adb
• For example, install the third-party launcher Emotn UI via APK, visit the website https://app.emotn.com/ui/ to download the APK, and then install it using ADB:

$ adb install com.oversea.aslauncher_1.0.9.0_5094.apk
Performing Streamed Install
Success

• After the installation is complete, launch it, and then enter the following ADB command to obtain its package name:

$ adb shell dumpsys window | grep mCurrentFocus
mCurrentFocus=Window{7a950fb u0 com.oversea.aslauncher/com.oversea.aslauncher.ui.main.MainActivity}

• As you can see, the package name of Emotn UI is com.oversea.aslauncher, set it as the default launcher:

$ adb shell pm set-home-activity com.oversea.aslauncher
Success

• Then comes the critical step, you need to disable the native launcher using the following command:

$ adb shell pm disable-user --user 0 com.google.android.tvlauncher
Package com.google.android.tvlauncher new state: disabled-user

• Finally, restart the device to see the effect, the device should boot directly into Emotn UI:

$ adb shell reboot

• From now on, if you want to install another launcher, you can switch between them through the GUI. for example, after installing FLauncher, you can enter the following settings interface to set FLauncher as the default launcher: Settings -> Device Preferences -> Advanced setting -> Default Launcher:
  

6.5 Wired networks on Android

• Any network port can connect to the network via DHCP
• If you want to configure a static IP, only eth0 interface is supported
• Some applications may have compatibility issues and report no network connection error, but the network is actually connected

6.6 EC20 4G LTE module on Android

EC20 support is disabled by default, you can check the status with the following command, if the EC20 is disabled, the number 1 will be displayed:

su
getprop persist.vendor.radio.no_modem_board

To enable EC20, use the following command (takes effect after a reboot):

su
setprop persist.vendor.radio.no_modem_board 0

7 Work with Debian11 Desktop

7.1 Introduction to Debian11 Desktop

Debian11 Desktop is a light-weighted debian desktop system，it has the following features：

• Uses Xfce as default desktop;
  
• Mali GPU-based OpenGL support;
  
• Support Rockhip MPP video hard coding and hard decoding;
  
• Pre-installed mpv and smplayer, both support 4K video hardware decoding;
  
• Pre-installed Chromium browser, support vpu/gpu hardware acceleration (video hard decoding limited to h264/mp4 format);
  
• Compatible with Plex Server and Docker;
  

7.2 Account & Password

Regular Account:
    User Name: pi
    Password: pi

Root:
    the root user account is disabled by default, you may configure the root password through the 'sudo passwd root' command.

7.3 View IP address

Since the Debian Bullseye hostname is the hardware model by default, you can use the ping command to get the IP address:ping NanoPi-M6

7.4 Connect to Debian via SSH

Run the following commandssh pi@NanoPi-M6
The default password is: pi

7.5 Update Software Packages

$ sudo apt-get update

7.6 Install x11vnc Server on Debian for Remote Access

7.6.1 Install x11vnc server

The following command to install x11vnc server:

sudo apt-get install x11vnc

7.6.2 Set your password

sudo x11vnc -storepasswd /etc/x11vnc.pwd

7.6.3 Setup x11vnc server with systemd auto start up

Create service configuration file:

sudo vi /lib/systemd/system/x11vnc.service

Let’s copy and paste the following configuration into our newly create service file:

[Unit]
Description=Start x11vnc at startup.
Requires=display-manager.service
After=syslog.target network-online.target
Wants=syslog.target network-online.target
 
[Service]
Type=simple
ExecStart=/usr/bin/x11vnc -display :0 -forever -loop -noxdamage -repeat -rfbauth /etc/x11vnc.pwd -rfbport 5900 -shared -capslock -nomodtweak
ExecStop=/usr/bin/x11vnc -R stop
Restart=on-failure
 
[Install]
WantedBy=multi-user.target

The following commands to reload the systmd system and to enable and start the x11vnc service:

sudo systemctl daemon-reload
sudo systemctl enable x11vnc.service
sudo systemctl start x11vnc

7.6.4 Testing remote access

Start the VNC client software, input IP:5900 to connect:

7.7 Install the kernel-header package

sudo dpkg -i /opt/linux-headers-*.deb

try to compile a kernel module:

sudo apt update
sudo apt install git gcc make bc
git clone https://github.com/RinCat/RTL88x2BU-Linux-Driver.git
cd RTL88x2BU-Linux-Driver
make -j$(nproc)
sudo make install
sudo modprobe 88x2bu

7.8 Change time zone

7.8.1 Check the current time zone

timedatectl

7.8.2 List all available time zones

timedatectl list-timezones

7.8.3 Set the time zone (e.g. Shanghai)

sudo timedatectl set-timezone Asia/Shanghai

7.9 Change startup LOGO and Wallpaper

7.9.1 Change startup LOGO

Replace the following two files in the kernel source code directory and recompile the kernel：
kernel/logo.bmp
kernel/logo_kernel.bmp
Or use the script to operate, as shown below：

• Download scripts:

git clone https://github.com/friendlyarm/sd-fuse_rk3399.git -b kernel-4.19 --single-branch
cd sd-fuse_rk3399

• Compile kernel and repackage firmware

convert files/logo.jpg -type truecolor /tmp/logo.bmp
convert files/logo.jpg -type truecolor /tmp/logo_kernel.bmp
sudo LOGO=/tmp/logo.bmp KERNEL_LOGO=/tmp/logo_kernel.bmp ./build-kernel.sh debian-bullseye-desktop-arm64
sudo ./mk-sd-image.sh debian-bullseye-desktop-arm64
sudo ./mk-emmc-image.sh debian-bullseye-desktop-arm64

Note: If your system is not debian-bullseye-desktop-arm64, please specify according to the actual situation

7.9.2 Change Wallpaper

Modify the following configuration file:

/home/pi/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-desktop.xml

7.10 Soft Factory Reset

Execute the following command in a terminal:

sudo firstboot && sudo reboot

7.11 Start the program automatically at startup(For example Kodi)

Put the desktop file in the ~/.config/autostart/ directory, for example：

mkdir ~/.config/autostart/
cp /usr/share/applications/kodi.desktop ~/.config/autostart/

7.12 Disable auto-mounting

sudo systemctl mask udisks2
sudo reboot

7.13 Setup Chinese language and Input method

7.13.1 Setup Chinese language

Enter the following command and select 'zh_CN.UTF-8':

sudo dpkg-reconfigure locales

Add environment variables to .bashrc:

echo "export LC_ALL=zh_CN.UTF-8" >> ~/.bashrc
echo "export LANG=zh_CN.UTF-8" >> ~/.bashrc
echo "export LANGUAGE=zh_CN.UTF-8" >> ~/.bashrc

Reboot device:

sudo reboot

7.13.2 Installing Chinese input method

Enter the following command to install fcitx and Pinyin input method:

sudo apt update
sudo apt-get install fcitx fcitx-pinyin
sudo apt-get install im-config
sudo apt-get install fcitx-table*
sudo apt-get install fcitx-ui-classic fcitx-ui-light
sudo apt-get install fcitx-frontend-gtk2 fcitx-frontend-gtk3 fcitx-frontend-qt4
sudo apt-get remove --purge scim* ibus*
sudo reboot

After reboot, press Ctrl+Space to switch between Chinese and English input methods, and the input method icon will appear in the upper right corner, right-click the input method icon in the upper right corner to switch input methods in the pop-up menu, as shown below:

7.14 Installing Plex Multimedia Server

Visit the Plex website: https://www.plex.tv/media-server-downloads/
On the download page, select the category "Plex Media Server", choose "Linux" for the platform and "Ubuntu(16.04+)/Debian(8+) - ARMv8" for the version,
After downloading the deb package, use the dpkg command to install the package:

sudo dpkg -i plexmediaserver_1.31.0.6654-02189b09f_arm64.deb

After installation, login to the Plex server by typing the following URL into your computer browser: http://IP地址:32400/web/

7.15 Install Docker on Debian

Please refer to: How to Install Docker on Debian

7.16 How to test NPU

Please refer to: NPU

7.17 How to test VPU

Please refer to: VPU

7.18 WiFi Connection

7.18.1 Gui

Click on the icon on the top right in the Debian's main window, select your wanted WiFi hotspot and proceed with prompts

7.18.2 Console

Please visit: Use NetworkManager to configure network settings

7.19 Cancel auto-login

Edit file:

sudo vim /etc/lightdm/lightdm.conf

Comment out the following two lines (insert # in front of them):

autologin-user=pi
autologin-user-timeout=0

7.20 Test OpenGL ES

You can test it by clicking on the Terminator icon to start a commandline utility in the System Tools and run the following commands:

glmark2-es2

7.21 HDMI/DP LCD Resolution

Open the system's menu and go to Settings -> Display to customize your settings.

7.22 HiDPI and display scaling

Xfce supports HiDPI scaling which can be enabled using the settings manager: Go to Settings Manager > Appearance > Settings > Window Scaling and select 2 as the scaling factor.
Or Edit this file: ~/.config/xfce4/xfconf/xfce-perchannel-xml/xsettings.xml

7.23 Adjust HDMI overscan

Open the command line terminal and enter the command to operate, Note:
1) You need to login to the desktop;
2) If you are using ssh terminal, please use the same username as the desktop login. The default is pi. You cannot use the root user. you also need to assign the DISPLAY variable:

export DISPLAY=:0.0

7.23.1 Query which resolutions the display supports

xrandr -q

7.23.2 Set resolution

For example set to 1920X1080@60Hz:

xrandr --output HDMI-1 --mode 1920x1080 --refresh 60

7.23.3 Adjust the HDMI overscan

For example, the transformation scaling horizontal coordinates by 0.8, vertical coordinates by 1.04 and moving the screen by 35 pixels right and 19 pixels down:

xrandr --output HDMI-1 --transform 0.80,0,-35,0,1.04,-19,0,0,1

7.23.4 Automatic adjustment at boot

Edit ~/.config/autostart/lxrandr-autostart.desktop，Write the full xrandr command to the key at the beginning of "Exec= as shown below：

[Desktop Entry]
Type=Application
Name=LXRandR autostart
Comment=Start xrandr with settings done in LXRandR
Exec=sh -c 'xrandr --output HDMI-1 --mode 1920x1080 --refresh 50 --transform 1.04,0,-35,0,1.05,-30,0,0,1'

7.24 Chromium web browser

7.24.1 GPU

Chromium web browser has enabled hardware acceleration by default, supports WebGL, and can view hardware acceleration details by entering the URL chrome://gpu, as shown below:

7.24.2 VPU

Play a video in the browser, then use fuser on the command line to view the mpp device node to confirm that the vpu interface is being called:

pi@FriendlyElec:~$ fuser /dev/mpp_service
/dev/mpp_service:     3258

If there is no content output from the fuser command, it means software decoding.

7.25 Test hardware encoding

mpi_enc_test -w 1920 -h 1080 -t 7 -f 0 -o test.h264 -n 300
export XDG_RUNTIME_DIR=/run/user/0
ffplay test.h264

7.25.1 Check Supported Hardware Decoding Formats

Enter about://gpu in your browser's address bar and scroll to the bottom of the page to view the "Video Acceleration Information" table.
After playing a video, enter about://media-internals in your browser's address bar to check if hardware decoding was enabled for the most recent playback.

8 Getting Started with OpenMediaVault

8.1 Introduction to OpenMediaVault

OpenMediaVault is the next-generation Network Attached Storage (NAS) solution based on Debian Linux. It includes services such as SSH, (S)FTP, SMB/CIFS, DAAP media server, RSync, BitTorrent client, and more. Due to its modular framework design, it can be enhanced through plugins.
OpenMediaVault version：

• OS: Debian 12
  
• OpenMediaVault: 7.0.5-1 (Sandworm)
  
• Others: built-in OMV-Extras
  

• Please refer to the following link for details：
  • Getting Started with OpenMediaVault

9 Work with FriendlyCore

9.1 FriendlyCore User Account

• Non-root User:

   User Name: pi
   Password: pi

• Root:

   User Name: root
   Password: fa

9.2 Update Software Packages

$ sudo apt-get update

9.3 Setup Network Configurations

9.3.1 Set static IP address

By default "eth0" is assigned an IP address obtained via dhcp. If you want to change the setting you need to change the following file:

vi /etc/network/interfaces.d/eth0

For example if you want to assign a static IP to it you can run the following commands:

auto eth0
iface eth0 inet static
    address 192.168.1.231
    netmask 255.255.255.0
    gateway 192.168.1.1

9.3.2 Set a DNS

You also need to modify the following file to add the DNS configuration:

vi /etc/systemd/resolved.conf

For example, set to 192.168.1.1:

[Resolve]
DNS=192.168.1.1

Restart the systemd-resolved service with the following command:

sudo systemctl restart systemd-resolved.service
sudo systemctl enable systemd-resolved.service

9.3.3 Set up to use another network interface

To change the setting of "eth1" you can add a new file similar to eth0's configuration file under the /etc/network/interfaces.d/ directory.

9.4 Setup Wi-Fi

First, use the following command to check if Network-Manager is installed on your system:

which nmcli

If you have installed it, refer to this link to connect to WiFi: Use NetworkManager to configure network settings, If you do not have Network-Manager installed on your system, please refer to the following method to configure WiFi,
By default the WiFi device is "wlan0". You need to create a configuration file under "/etc/network/interfaces.d/" for WiFi:

vi /etc/network/interfaces.d/wlan0

Here is a sample wlan0 file:

auto lo
iface lo inet loopback
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid YourWiFiESSID
wpa-ap-scan 1
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk YourWiFiPassword

Please replace "YourWiFiESSID" and "YourWiFiPassword" with your WiFiESSID and password. After save and close the file you can connect to your WiFi source by running the following command:

sudo systemctl daemon-reload
sudo systemctl restart networking

After you power on your board it will automatically connect to your WiFi source.
Please note that if you use one TF card to boot multiple boards the WiFi device name will likely be named to "wlan1", "wlan2" and etc. You can reset it to "wlan0" by deleting the contents of the following file and reboot your board: /etc/udev/rules.d/70-persistent-net.rules

9.5 Install the kernel-header package

sudo dpkg -i /opt/linux-headers-*.deb

9.6 Delete Qt5 and related files

Execute the following commands：

su root
cd /
rm -rf usr/local/Trolltech/Qt-5.10.0-rk64one usr/local/Trolltech/Qt-5.10.0-rk64one-sdk usr/bin/setqt5env* usr/bin/qt5demo etc/qt5
rm -rf opt/{qt5-browser,Qt5_CinematicExperience,qt5-multi-screen-demo,qt5-nmapper,qt5-player,qt5-smarthome,QtE-Demo,qt5-qml-image-viewer,dual-camera}

10 Installing Third-Party Armbian System

Please refer to: Armbian Installation Guide

11 How to Compile

11.1 Setup Development Environment

11.1.1 Method 1: Using docker to cross-compile

Please refre to docker-cross-compiler-novnc

11.1.2 Method 2: Setup build environment on the host machine

11.1.2.1 Install required packages

Install and run requirements ubuntu 20.04, install required packages using the following commands:

sudo apt-get -y update
sudo apt-get install -y sudo curl
sudo bash -c \
  "$(curl -fsSL https://raw.githubusercontent.com/friendlyarm/build-env-on-ubuntu-bionic/master/install.sh)"

The following cross-compilers will be installed:

Version	Architecture	Compiler path	Purpose
4.9.3	armhf	/opt/FriendlyARM/toolchain/4.9.3	Can be used to build 32-bit ARM applications
6.4	aarch64	/opt/FriendlyARM/toolchain/6.4-aarch64	Can be used to build kernel 4.4
11.3	aarch64	/opt/FriendlyARM/toolchain/11.3-aarch64	Can be used to build kernel 4.19 or higher and U-Boot

11.1.2.2 Setting the compiler path

Based on the table in the previous section, select the appropriate version of the compiler and add the compiler's path to PATH. For example, if you want to use the 11.3 cross-compiler, edit ~/.bashrc using vi and add the following content to the end:

export PATH=/opt/FriendlyARM/toolchain/11.3-aarch64/bin:$PATH
export GCC_COLORS=auto

Run the ~/.bashrc script to make it effective in the current commandline. Note: there is a space after ".":

. ~/.bashrc

To verify if the installation was successful：

$ aarch64-linux-gcc -v
Using built-in specs.
COLLECT_GCC=aarch64-linux-gcc
COLLECT_LTO_WRAPPER=/opt/FriendlyARM/toolchain/11.3-aarch64/libexec/gcc/aarch64-cortexa53-linux-gnu/11.3.0/lto-wrapper
Target: aarch64-cortexa53-linux-gnu
Configured with: /home/cross/arm64/src/gcc/configure --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu --target=aarch64-cortexa53-linux-gnu --prefix=/opt/FriendlyARM/toolchain/11.3-aarch64 --exec_prefix=/opt/FriendlyARM/toolchain/11.3-aarch64 --with-sysroot=/opt/FriendlyARM/toolchain/11.3-aarch64/aarch64-cortexa53-linux-gnu/sysroot --enable-languages=c,c++ --enable-fix-cortex-a53-843419 --with-arch=armv8-a+crypto+crc --with-cpu=cortex-a53 --with-pkgversion=ctng-1.25.0-119g-FA --with-bugurl=http://www.friendlyelec.com/ --enable-objc-gc --enable-__cxa_atexit --disable-libmudflap --disable-libgomp --disable-libssp --disable-libquadmath --disable-libquadmath-support --disable-libsanitizer --disable-libmpx --with-gmp=/home/cross/arm64/buildtools --with-mpfr=/home/cross/arm64/buildtools --with-mpc=/home/cross/arm64/buildtools --with-isl=/home/cross/arm64/buildtools --enable-lto --enable-threads=posix --disable-libstdcxx-pch --enable-clocale=gnu --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-indirect-function --enable-gnu-unique-object --enable-default-pie --enable-linker-build-id --with-linker-hash-style=gnu --enable-plugin --enable-gold --with-libintl-prefix=/home/cross/arm64/buildtools --disable-multilib --with-local-prefix=/opt/FriendlyARM/toolchain/11.3-aarch64/aarch64-cortexa53-linux-gnu/sysroot --enable-long-long --enable-checking=release --enable-link-serialization=2
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 11.3.0 (ctng-1.25.0-119g-FA)

11.2 Build Openwrt/Friendlywrt

11.2.1 Download Code

Two versions are available, please choose as required:

11.2.1.1 FriendlyWrt 21.02

mkdir friendlywrt21-rk3588
cd friendlywrt21-rk3588
git clone https://github.com/friendlyarm/repo --depth 1 tools
tools/repo init -u https://github.com/friendlyarm/friendlywrt_manifests -b master-v21.02 \
        -m rk3588.xml --repo-url=https://github.com/friendlyarm/repo  --no-clone-bundle
tools/repo sync -c  --no-clone-bundle

11.2.1.2 FriendlyWrt 23.05

mkdir friendlywrt23-rk3588
cd friendlywrt23-rk3588
git clone https://github.com/friendlyarm/repo --depth 1 tools
tools/repo init -u https://github.com/friendlyarm/friendlywrt_manifests -b master-v23.05 \
        -m rk3588.xml --repo-url=https://github.com/friendlyarm/repo  --no-clone-bundle
tools/repo sync -c  --no-clone-bundle

11.2.2 First compilation step

./build.sh rk3588.mk  # or rk3588-docker.mk

All the components (including u-boot, kernel, and friendlywrt) are compiled and the sd card image will be generated, then execute the following command to generate the image file for installing the system into the emmc:

./build.sh emmc-img

After making changes to the project, the sd card image needs to be repackaged by running the following command:

./build.sh sd-img

11.2.3 Secondary compilation steps

cd friendlywrt
make menuconfig
rm -rf ./tmp
make -j${nproc}
cd ../
./build.sh sd-img
./build.sh emmc-img

11.2.4 Build u-boot only

./build.sh uboot

11.2.5 Build kernel only

./build.sh kernel

11.2.6 Build friendlywrt only

./build.sh friendlywrt

Or go to the friendlywrt directory and follow the standard openwrt commands. If you get an error with the above command, try using the following command to compile in a single thread:

cd friendlywrt
make -j1 V=s

11.3 Build Buildroot

please refer to: Buildroot

11.4 Build Other Linux

11.4.1 Kernel and u-boot versions

Operating System	Kernel Version	U-boot version	Cross-compiler	Partition type	Packaging Tool	Kernel branch	Kernel configuration	U-boot branch	U-boot configuration
buildroot	linux v5.10.y	u-boot v2017.09	11.3-aarch64	GPT	sd-fuse	nanopi5-v5.10.y_opt	nanopi6_linux_defconfig	nanopi6-v2017.09	nanopi6_defconfig
openmediavault-arm64	linux v6.1.y			GPT	sd-fuse	nanopi6-v6.1.y
ubuntu-jammy-desktop-arm64				GPT
ubuntu-jammy-minimal-arm64
ubuntu-jammy-x11-desktop-arm64
ubuntu-focal-desktop-arm64
friendlycore-focal-arm64
debian-bookworm-core-arm64
debian-bullseye-desktop-arm64
debian-bullseye-minimal-arm64
friendlywrt21							nanopi6_linux_defconfig friendlywrt.config
friendlywrt21-docker
friendlywrt23
friendlywrt23-docker

• Kernel git repo：https://github.com/friendlyarm/kernel-rockchip
• U-boot git repo：https://github.com/friendlyarm/uboot-rockchip
• The cross-compile toolchain is located in the path: /opt/FriendlyARM/toolchain/
• The sd-fuse is a helper script to make bootable SD card image.

11.4.2 Build kernel linux-v6.1.y

Clone the repository to your local drive then build:

git clone https://github.com/friendlyarm/kernel-rockchip --single-branch --depth 1 -b nanopi6-v6.1.y kernel-rockchip
cd kernel-rockchip
export PATH=/opt/FriendlyARM/toolchain/11.3-aarch64/bin/:$PATH
touch .scmversion
# Configuring the Kernel
# Load default configuration
make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 nanopi6_linux_defconfig
# Optionally, load configuration for FriendlyWrt
# make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 nanopi6_linux_defconfig friendlywrt.config
# Optionally, if you want to change the default kernel config
# make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 menuconfig
# Start building kernel
make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 nanopi6-images -j$(nproc)
# Start building kernel modules
mkdir -p out-modules && rm -rf out-modules/*
make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 INSTALL_MOD_PATH="$PWD/out-modules" modules -j$(nproc)
make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 INSTALL_MOD_PATH="$PWD/out-modules" modules_install
KERNEL_VER=$(make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 kernelrelease)
[ ! -f "$PWD/out-modules/lib/modules/${KERNEL_VER}/modules.dep" ] && depmod -b $PWD/out-modules -E Module.symvers -F System.map -w ${KERNEL_VER}
(cd $PWD/out-modules && find . -name \*.ko | xargs aarch64-linux-strip --strip-unneeded)

The generated files:

kernel.img

resource.img

boot.img This img is deprecated

The kernel modules are located in the out-modules directory

Run your build:
Please refre to #Running the build

11.4.3 Build u-boot v2017.09

Clone the repository to your local drive then build:

git clone https://github.com/friendlyarm/rkbin --single-branch --depth 1 -b nanopi6
git clone https://github.com/friendlyarm/uboot-rockchip --single-branch --depth 1 -b nanopi6-v2017.09
export PATH=/opt/FriendlyARM/toolchain/11.3-aarch64/bin/:$PATH
cd uboot-rockchip/
./make.sh nanopi6

After the compilation, the following files will be generated:

uboot.img

rk3588_spl_loader_xx.yy.zzz.bin (aka MiniLoaderAll.bin)

Run your build:
Please refre to #Running the build

11.4.4 Running the build

11.4.4.1 Install to target board

RK3588 uses GPT partitions by default, you can use the dd command, but be careful to choose the right output device:

• The SD/TF Card device node: /dev/mmcblk0
  
• The eMMC device node: /dev/mmcblk2
  

Use the 'parted' command to view the partition layout:

parted /dev/mmcblk2 print

Sample outputs:

Model: MMC A3A551 (sd/mmc)
Disk /dev/mmcblk2: 31.0GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
 
Number  Start   End     Size    File system  Name      Flags
 1      8389kB  12.6MB  4194kB               uboot
 2      12.6MB  16.8MB  4194kB               misc
 3      16.8MB  21.0MB  4194kB               dtbo
 4      21.0MB  37.7MB  16.8MB               resource
 5      37.7MB  79.7MB  41.9MB               kernel
 6      79.7MB  113MB   33.6MB               boot
 7      113MB   147MB   33.6MB               recovery
 8      147MB   31.0GB  30.9GB  ext4         rootfs

as shown above, the resource partition is located at 4 and the kernel partition is located at 5. Use the dd command to write the resource.img and kernel.img files to these partitions, the commands are as follows:

dd if=resource.img of=/dev/mmcblk2p4 bs=1M
dd if=kernel.img of=/dev/mmcblk2p5 bs=1M

If you want to update u-boot:

dd if=uboot.img of=/dev/mmcblk2p1 bs=1M

To update new driver modules, copy the newly compiled driver modules to the appropriate directory under /lib/modules.

11.4.4.2 Packaging and creating an SD image

To create a new OS image file, you need to use the "sd-fuse" packaging tool.

"sd-fuse" is a collection of scripts that can be used to create bootable SD card images for FriendlyElec boards. Its main features include:

• Creation of root filesystem images from a directory
  
• Building of bootable SD card images
  
• Simple compilation of kernel, U-Boot, and third-party drivers
  

Please click on the following link to find out more:

Kernel version	Packaging Tool
linux v6.1.y	sd-fuse_rk3588

11.4.4.3 USB flashing

11.4.4.3.1 Linux

Reboot the board and enter loader mode with the following command:

sudo reboot loader

To flash U-Boot and kernel using the "upgrade_tool_v2.17_for_linux" tool, please use the following command:

sudo upgrade_tool di -k kernel.img
sudo upgrade_tool di -re resource.img
sudo upgrade_tool di -u uboot.img
sudo upgrade_tool RD

Note: "upgrade_tool" is a command-line tool provided by Rockchip for Linux operating systems (Linux_Upgrade_Tool).

11.5 Build the code using scripts

11.5.1 Download scripts and image files

git clone https://github.com/friendlyarm/sd-fuse_rk3588.git --single-branch -b kernel-6.1.y
cd sd-fuse_rk3588
tar xvzf /path/to/netdrive/03_Partition\ image\ files/friendlycore-focal-arm64-images.tgz

11.5.2 Compile the kernel

Download the kernel source code and compile it. the relevant image files in the friendlycore-focal-arm64 directory will be automatically updated, including the kernel modules in the file system:

git clone https://github.com/friendlyarm/kernel-rockchip --depth 1 -b nanopi6-v6.1.y kernel-rk3588
KERNEL_SRC=$PWD/kernel-rk3588 ./build-kernel.sh friendlycore-focal-arm64

11.5.3 Compile the kernel headers

git clone https://github.com/friendlyarm/kernel-rockchip --depth 1 -b nanopi6-v6.1.y kernel-rk3588
MK_HEADERS_DEB=1 BUILD_THIRD_PARTY_DRIVER=0 KERNEL_SRC=$PWD/kernel-rk3588 ./build-kernel.sh friendlycore-focal-arm64

11.5.4 Compile the uboot

Download the uboot source code and compile it. the relevant image files in the friendlycore-focal-arm64 directory will be automatically updated:

git clone https://github.com/friendlyarm/uboot-rockchip --depth 1 -b nanopi6-v2017.09
UBOOT_SRC=$PWD/uboot-rockchip ./build-uboot.sh friendlycore-focal-arm64

11.5.5 Generate new image

Repackage the image file in the friendlycore-focal-arm64 directory into sd card image:

./mk-sd-image.sh friendlycore-focal-arm64

After the command is completed, the image is in the out directory, you can use the dd command to make the SD boot card, for example:

dd if=out/rk3588-sd-friendlycore-focal-5.10-arm64-YYYYMMDD.img of=/dev/sdX bs=1M

11.6 Building AOSP from source

11.6.1 Hardware and Software Requirements

• Your computer should have at least 16GB of RAM and 300GB of disk space. We recommend using a machine with 32GB of RAM and a large-capacity, high-speed SSD, and we do not recommend using virtual machines.
• If you encounter compilation errors, they may be caused by problems with the compilation environment. We recommend using the following Docker container for compilation: docker-cross-compiler-novnc.

11.6.2 Download source from the netdrive

Netdisk URL: Click here
File location on netdisk："07_Source codes/rk35xx-android12-xxxxxxx-YYYYMMDD.tgz" (YYYYMMDD represents the date of the package, and xxxxxxx represents the final commit-id)
Unzip and fetch updates:

tar xzf '/path/to/netdisk/07_Source codes/rk35xx-android12-xxxxxxx-YYYYMMDD.tgz'
cd rk35xx-android12
git pull

11.6.3 Tablet profile build (First Build)

echo "ROCKCHIP_DEVICE_DIR := device/rockchip/rk3588/nanopi6" > .rockchip_device.mk
# export INSTALL_GAPPS_FOR_TESTING=yes  # include google apps
. setenv.sh
./build.sh -FMu

11.6.4 TV profile build (First Build)

echo "ROCKCHIP_DEVICE_DIR := device/rockchip/rk3588/nanopi6_box" > .rockchip_device.mk
# export INSTALL_GAPPS_FOR_TESTING=yes  # include google apps
. setenv.sh
./build.sh -FMu

11.6.5 Second build

# export INSTALL_GAPPS_FOR_TESTING=yes  # include google apps
. setenv.sh
make
./build.sh -Mu

11.6.6 Running your AOSP build

After the Android compilation is completed, the image file will be stored in the rockdev/Image-aosp_nanopi3 subdirectory of the Android source code directory.

11.6.6.1 USB Flashing

Use the rockchip tool to flash the following file: rockdev/Image-aosp_nanopi3/update.img

11.6.6.2 SD-to-eMMC Flashing

Refer to the following steps：
1) Insert the SD card of the eflasher system into the host;
2) Copy the files in the rockdev/Image-aosp_nanopi3 directory to the android12 or androidtv directory in the FRIENDLYARM partition of the SD card:

sudo cp -af parameter.txt config.cfg MiniLoaderAll.bin uboot.img \
    dtbo.img vbmeta.img boot.img recovery.img \
    misc.img pcba_small_misc.img pcba_whole_misc.img \
    baseparameter.img super.img /media/$USER/FriendlyARM/android12

3) Insert the SD card into NanoPi-M6 and re-flash;

11.6.7 Pack the new SD Image

git clone https://github.com/friendlyarm/sd-fuse_rk3588.git
SDFUSE=$PWD/sd-fuse_rk3588
mkdir $SDFUSE/android12
 
cd /path/to/rk35xx-android12/rockdev/Image-aosp_nanopi3
cp -af parameter.txt config.cfg MiniLoaderAll.bin uboot.img \
    dtbo.img vbmeta.img boot.img recovery.img \
    misc.img pcba_small_misc.img pcba_whole_misc.img \
    baseparameter.img super.img $SDFUSE/android12
 
cd $SDFUSE/
./mk-sd-image.sh android12
 
tar xvzf /path/to/netdrive/03_Partition\ image\ files/emmc-flasher-images.tgz
./mk-emmc-image.sh android12

For more information, please refer to #Packaging and creating an SD image

12 Using On-Board Hardware Resources

12.1 Using VPU

Please refer to NPU

12.2 Using NPU

Please refer to NPU

13 Backup rootfs and create custom SD image (to burn your application into other boards)

13.1 Backup rootfs

Run the following commands on your target board. These commands will back up the entire root partition:

sudo passwd root
su root
cd /
tar --warning=no-file-changed -cvpzf /rootfs.tar.gz \
    --exclude=/rootfs.tar.gz --exclude=/var/lib/docker/runtimes \
    --exclude=/etc/firstuser --exclude=/etc/friendlyelec-release \
    --exclude=/usr/local/first_boot_flag --one-file-system /

Note: if there is a mounted directory on the system, an error message will appear at the end, which can be ignored.

13.2 Making a bootable SD card from a root filesystem

Run the following script on your Linux PC host, we'll only mention "debian-bullseye-desktop-arm64 os" for brevity, but you can apply the same process for every linux OS.

su root
git clone https://github.com/friendlyarm/sd-fuse_rk3588 --single-branch -b kernel-6.1.y
cd sd-fuse_rk3588
tar xvzf /path/to/netdrive/03_Partition\ image\ files/debian-bullseye-desktop-arm64-images.tgz
tar xvzf /path/to/netdrive/03_Partition\ image\ files/emmc-eflasher-images.tgz
scp pi@BOARDIP:/rootfs.tar.gz /rootfs.tar.gz
mkdir rootfs
tar xvzfp rootfs.tar.gz -C rootfs --numeric-owner --same-owner
./build-rootfs-img.sh rootfs debian-bullseye-desktop-arm64
./mk-sd-image.sh debian-bullseye-desktop-arm64
./mk-emmc-image.sh debian-bullseye-desktop-arm64 autostart=yes

14 Connect NVME SSD High Speed Hard Disk

14.1 Detection of SSD

root@FriendlyELEC:~# cat /proc/partitions 
major minor  #blocks  name
   1        0       4096 ram0
 259        0  125034840 nvme0n1

If there is a nvme0n1 device node it means an SSD is recognized.

14.2 Partition of SSD

To mount an SSD under Linux we re-partition it as one section by running the following command:

(echo g; echo n; echo p; echo 1; echo ""; echo ""; echo w; echo q) | fdisk /dev/nvme0n1

If you want to re-partition it to multiple sections you can run "fdisk /dev/nvme0n1". For more detail about this command refer to the fdisk's manual.

14.3 Format Section to EXT4

After an SSD is successfully partitioned you can check its sections by running "cat /proc/partitions". The /dev/nvme0n1p1 section is used to store data:

root@FriendlyELEC:~# cat /proc/partitions
major minor  #blocks  name
 
   1        0       4096 ram0
 259        0  125034840 nvme0n1
 259        2  125033816 nvme0n1p1

The following command formats a section to ext4:

mkfs.ext4 /dev/nvme0n1p1

14.4 Auto Mount SSD on System Startup

Before we mount an SSD's section you need to know its Block ID. You can check it by running "blkid":

blkid /dev/nvme0n1p1
/dev/nvme0n1p1: UUID="d15c4bbf-a6c3-486f-8f81-35a8dbd46057" TYPE="ext4" PARTUUID="887628f0-01"

Add a "Block ID" to "/etc/fstab" and here is what it looks like

UUID=<Block ID> /media/nvme ext4 defaults 0 0

You need to replace <Block ID> with the UUID obtained by running "blkid". To mount the SSD in our example we made the "/etc/fstab" file as follows:

UUID=d15c4bbf-a6c3-486f-8f81-35a8dbd46057 /media/nvme ext4 defaults 0 0

We want to mount an SSD to "/media/nvme" but this directory doesn't exist. Therefore we create it and change its access right by running the following commands:

mkdir -p /media/nvme
chmod 777 /media/nvme

Run "mount" to check if the SSD is mounted successfully:

mount /media/nvme

You can reboot your board to check if your SSD will be automatically mounted:

reboot

15 Common Linux-based operating system operations

15.1 Using ADB on Linux Systems

15.1.1 Enabling ADB in Buildroot System

Enable on Startup

mv /etc/init.d/K50usbdevice.sh /etc/init.d/S50usbdevice.sh
reboot

Enable Temporarily

usbdevice-wrapper start

15.1.2 Enabling ADB in Ubuntu and Debian Systems

Enable on Startup

sudo systemctl enable usbdevice
sudo reboot

Enable Temporarily

usbdevice-wrapper start

15.1.3 How to Connect

When using ADB, the port connected to the computer is the same as the USB flashing port.

15.2 Install Kernel Headers

To install the .deb file located in the /opt/archives directory:

sudo dpkg -i /opt/archives/linux-headers-*.deb

To download and update the kernel header files online:

wget http://112.124.9.243/archives/rk3588/linux-headers-$(uname -r)-latest.deb
sudo dpkg -i ./linux-headers-latest.deb

You can visit http://112.124.9.243/archives/rk3588 to see which kernel deb packages are available.

15.3 Update Kernel to Latest Version

This will update the kernel to the latest version and update the kernel and resource partitions, as well as the kernel modules:

wget http://112.124.9.243/archives/rk3588/linux-image-$(uname -r)-latest.deb
sudo dpkg -i ./linux-image-latest.deb
sudo reboot

15.4 Setting Kernel Boot Parameters (eMMC Only)

Flash the firmware file XXXX-eflasher-multiple-os-YYYYMMDD-30g.img.gz to a TF card, then insert the TF card into your computer. Windows will usually recognize the TF card partition automatically (formatted as exFAT). For Linux or Mac users, manually mount the first partition of the TF card. Assuming the TF card’s device name is /dev/sdX, mount /dev/sdX1.

Edit the info.conf configuration file in the OS directory on the TF card, adding the bootargs-ext parameter. For example:

bootargs-ext=rockchipdrm.fb_max_sz=2048

To remove a specified parameter, set it to empty. For example, to remove the userdata parameter:

bootargs-ext=userdata=

After editing, use this TF card to flash the system to eMMC.

To set kernel boot parameters during the creation of a mass production card, refer to the following script (example for RK3588): https://github.com/friendlyarm/sd-fuse_rk3588/blob/kernel-6.1.y/test/test-custom-bootargs.sh

16 Unbricking Method

If the ROM is not installed correctly, causing the development board to become bricked, and you might not have the opportunity to reinstall the ROM via an SD card, you need to enter Maskrom mode to unbrick it by erasing the storage device.

16.1 Windows Users

16.1.1 Download Required Files

• Get the necessary tools: Visit here, find RKDevTool_v3.19_for_window.zip and DriverAssitant_v5.12.zip in the 05_Tools directory, and download them to your local machine.
• Install Rockchip USB driver and RKDevTool: Extract DriverAssitant_v5.12.zip to install the Rockchip USB driver, and extract RKDevTool_v3.19_for_window.zip to obtain the Rockchip flashing tool RKDevTool.
• Get the loader: Visit here, enter the tools directory corresponding to your CPU model, and download MiniLoaderAll.bin.

16.1.2 Enter Maskrom Mode to Erase the Storage Device

• Start RKDevTool on your computer.
• Press and hold the “Mask” key, Use a USB cable, connect NanoPi-M6 to a PC，After the status LED has been on for at least 3 seconds, release the Mask key

• You will see Found One MASKROM Device displayed at the bottom of the RKDevTool interface, as shown below:

• Click the Advanced Function tab in the RKDevTool interface.
• In the Boot text box, select MiniLoaderAll.bin, then click the Download button.
• Select EMMC, click Switch Storage, then click the EraseAll button to erase the eMMC.

• At this point, NanoPi-M6 is restored to its initial state and can be normally booted via SD card or eMMC.

16.2 Linux Users

16.2.1 Download the Required Files

• Get the necessary tools: Visit here and find upgrade_tool_v2.30_for_linux.tgz in the 05_Tools directory and download it locally.
• Get the loader: Visit here, enter the tools directory corresponding to your CPU model, and download MiniLoaderAll.bin.

16.2.2 Installation for upgrade_tool

Using the following commands:

tar xzf upgrade_tool_v2.30_for_linux.tgz
cd upgrade_tool_v2.30_for_linux
sudo cp upgrade_tool /usr/local/sbin/
sudo chmod 755 /usr/local/sbin/upgrade_tool

16.2.3 Enter Maskrom Mode to Erase the Storage Device

• Connect NanoPi-M6 to the computer using a USB data cable.
• Disconnect the power from NanoPi-M6, hold down the MASK button, connect the power, and release the button after 4 seconds.
• Check the connection with the following command:

upgrade_tool LD

A result similar to "DevNo=1 Vid=0x2207,Pid=0x350b,LocationID=13 Mode=Maskrom SerialNo=" indicates that the device has been detected.

• Erase the eMMC with the following command:

upgrade_tool EF MiniLoaderAll.bin

• At this point, NanoPi-M6 has been restored to its initial state and can boot the system normally via SD card or eMMC.

16.3 Mac Users

Our tests found that upgrade_tool_v2.25 does not work properly on macOS. Therefore, we recommend using Windows or Linux unless an updated version of upgrade_tool becomes available.

18 Schematic, PCB CAD File

• Schematic: NanoPi_M6_2405_SCH.PDF
• PCB CAD File：NanoPi_M6_2405_2D_CAD_DXF.zip

19 Update Logs

Initial Release