NanoPi M2

From FriendlyELEC WiKi
Jump to: navigation, search


1 Introduction

  • The NanoPi M2 is another Samsung 4418 based ARM board released by FriendlyARM after the NanoPi 2 and NanoPi 2 Fire. It is only two thirds the size of the Raspberry Pi. It is open source. It works with Ubuntu Core, Ubuntu Mate, Debian, Android 5.1 and etc.
  • Compared to the Raspberry Pi 2 the NanoPi M2 uses the Samsung Cortex-A9 S5P4418 Soc. It integrates Gbps Ethernet, AXP228 PMU which supports software power-on/off and wake up functions. It can be powered via the MicroUSB port
  • In such a small board it still integrates rich interfaces and ports. Besides the popular HDMI, 3.5mm audio jack, onboard microphone, four USB hosts and Gbit Ethernet it has a Raspberry Pi compatible 40 pin GPIO pin header and various video interfaces such as a DVP camera interface, an LCD interface which supports I2C capacitive LCD and etc. In addition, for user’s convenience it has a serial debug port for debugging and development.

2 Hardware Spec

  • CPU: S5P4418, 400Mhz~1.4GHz
  • DDR3 RAM: 32bit 1GB DDR3
  • MicroSD Slot x1
  • Connectivity: Gbps Ethernet port(RTL8211E)
  • Audio: 3.5mm audio jack/Via HDMI
  • Microphone: 1 x onboard Microphone
  • USB Host: 4 x USB 2.0 Host, two are standard type A ports and the other two are 2.54mm pitch pin headers
  • Micro USB: 1 x USB 2.0 Client
  • LCD Interface: 0.5 mm pitch SMT FPC seat, for full-color LCD (RGB: 8-8-8)
  • HDMI: HDMI 1.4A, Type-A, 1080P60
  • DVP Camera Interface: 0.5mm pitch FPC socket. It includes ITU-R BT 601/656 8-bit, I2C and IO
  • GPIO1: 2.54mm pitch 40pin, compatible with Raspberry Pi's GPIO. It includes UART, SPI, I2C, PWM, IO etc
  • Debug Serial Port: 4Pin 2.54mm pitch pin header
  • User Key: 1 x Power , 1 x Reset
  • LED: 1 x Power LED, 1 x System LED
  • RTC: RTC Pins
  • Power: DC 5V/2A
  • PCB Dimension(mm): 64 x 56, Six Layer
  • Temperature measuring range: -10℃ to 80℃
  • OS/Software: u-boot, Android5.1/4.4, Debian Jessie 8


3 Diagram, Layout and Dimension

3.1 Layout

NanoPi M2 Interfaces and Ports
NanoPi M201 Interfaces and Ports
  • GPIO1 Pin Spec
Pin# Name Pin# Name
1 SYS_3.3V 2 VDD_5V
3 I2C0_SDA 4 VDD_5V
13 GPIOB30 14 DGND
15 GPIOB31 16 GPIOC14/PWM2
17 SYS_3.3V 18 GPIOB27
25 DGND 26 GPIOB26
27 I2C1_SDA 28 I2C1_SCL
31 GPIOC7 32 GPIOC28
37 AliveGPIO3 38 SPI2_MOSI/GPIOC12

This GPIO pin spec is a little bit different from that of the NanoPi 2. Here is a comparison table of the two:40 pins GPIO comparison table

  • Debug Port(UART0)
Pin# Name
2 VDD_5V
  • DVP Camera IF Pin Spec
Pin# Name
1, 2 SYS_3.3V
7,9,13,15,24 DGND
3 I2C0_SCL
4 I2C0_SDA
8,10 NC
16-23 Data bit7-0
  • RGB LCD IF Pin Spec
Pin# Name Description
1, 2 VDD_5V 5V Output, it can be used to power LCD modules
11,20,29, 37,38,39,40, 45 DGND Gound
3-10 Blue LSB to MSB RGB blue
12-19 Green LSB to MSB RGB green
21-28 Red LSB to MSB RGB red
30 GPIOB25 available for users
31 GPIOC15 occupied by FriendlyARM one wire technology to recognize LCD models and control backlight and implement resistive touch, not applicable for users
32 XnRSTOUT Form CPU low when system is reset
33 VDEN signal the external LCD that data is valid on the data bus
34 VSYNC vertical synchronization
35 HSYNC horizontal synchronization
36 LCDCLK LCD clock, Pixel frequency
41 I2C2_SCL I2C2 clock signal, for capacitive touch data transmission
42 I2C2_SDA I2C2 data signal, for capacitive touch data transmission
43 GPIOC16 interrupt pin for capacitive touch, used with I2C2
44 NC not connected
  1. SYS_3.3V: 3.3V power output
  2. VVDD_5V: 5V power input/output. When the external device’s power is greater than the MicroUSB’s the external device is charging the board otherwise the board powers the external device. The input range is 4.7V ~ 5.6V
  3. All pins are 3.3V, output current is 5mA
  4. GPIO1's pin spec is a little bit different from that of the NanoPi 2. Refer to this comparison table 40 pins GPIO comparison table
  5. For more details refer to the document: NanoPi-M2-1602-Schematic.pdf

3.2 Board Dimension

NanoPi M2 Dimensions

For more details refer to the document: NanoPi-M2-1602-Dimensions(dxf).zip

4 Get Started

4.1 Essentials You Need

Before starting to use your NanoPi M2 get the following items ready

  • NanoPi M2
  • microSD Card/TFCard: Class 10 or Above, minimum 8GB SDHC
  • microUSB power. A 5V/2A power is a must
  • HDMI monitor or LCD
  • USB keyboard and mouse
  • A host computer running Ubuntu 18.04 64 bit system

4.2 TF Cards We Tested

To make your device boot and run fast we highly recommend you use a Class10 8GB SDHC TF card or a better one. The following cards are what we used in all our test cases presented here:

  • Sandisk MicroSDHC V30 32GB Extreme Pro (Developer choice)


  • SanDisk 32GB High Endurance Video MicroSDHC Card with Adapter for Dash Cam and Home Monitoring Systems (High reliability)


  • SanDisk TF 8G Class10 Micro/SD High Speed TF card:

SanDisk microSD 8G

  • SanDisk TF128G MicroSDXC TF 128G Class10 48MB/S:

SanDisk microSD 128G

  • 川宇 8G C10 High Speed class10 micro SD card:

chuanyu microSD 8G

4.3 Make an Installation MicroSD Card

4.3.1 Under Windows

Get the following files from here:[ to download image files.

  • Get a 4G SDHC card and backup its data if necessary.
Image Files Debian image file with X Window Debian image file with X Window and WiFi configured as AP Android4.4 image file with support for 4G LTE Android5.1 image file Ubuntu core with Qt Embedded
Flash Utility:
win32diskimager.rar Windows utility. Under Linux users can use "dd"
  • Uncompress these files. Insert an SD card(at least 4G) into a Windows PC and run the win32diskimager utility 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.
  • Insert this card into your NanoPi M2 and power on (with a 5V/2A power source). If the green LED is on and the blue LED is blinking this indicates your NanoPi M2 has successfully booted.

4.3.2 Under Linux Desktop

  • 1) Insert your microSD card into your host running Ubuntu and check your SD card's device name
dmesg | tail

Search the messages output by "dmesg" for similar words like "sdc: sdc1 sdc2". If you can find them it means your SD card is recognized as "/dev/sdc". Or you can check that by commanding "cat /proc/partitions"

  • 2) Download Flashing Script
git clone
cd sd-fuse_s5p4418
  • 3) Flash Android Firmware to MicroSD Card
./ /dev/sdx

(Note: you need to replace "/dev/sdx" with the device name in your system)
When you do “git clone” you have to hit “Y” within 10 seconds after it prompts you to download image files otherwise you will miss the download.

  • 4) Flash Debian Firmware to MicroSD Card
./ /dev/sdx debian

4.3.3 Extend NanoPi M2's TF Card Section

  • When Debian/Ubuntu is loaded the TF card's section will be automatically extended.
  • When Android is loaded you need to run the following commands on your host PC to extend your TF card's section:
sudo umount /dev/sdx?
sudo parted /dev/sdx unit % resizepart 4 100 resizepart 7 100 unit MB print
sudo resize2fs -f /dev/sdx7

(Note: you need to replace "/dev/sdx" with the device name in your system)

4.3.4 LCD/HDMI Resolution

When the system boots our uboot will check whether it is connected to an LCD or to an HDMI monitor. If it recognizes an LCD it will configure its resolution. Our uboot defaults to the HDMI 720P configuration.
If you want to modify the LCD resolution you can modify file "arch/arm/plat-s5p4418/nanopi2/lcds.c" in the kernel and recompile it.
If your NanoPi M2 is connected an HDMI monitor and it runs Android it will automatically set the resolution to an appropriate HDMI mode by checking the "EDID". If your NanoPi M2 is connected an HDMI monitor and it runs Debian by default it will set the resolution to HDMI 720P. If you want to modify the resolution to 1080P modify your kernel's configuration as explained above.

4.4 Update Image Files in MicroSD Card From PC Host

If you want to make some changes to the image files in your MicroSD card follow steps below otherwise you can skip this section.
Insert your MicroSD card into a PC host running Linux, mount the boot and rootfs sections of the SD card and follow the steps below:
1) If you want to change your kernel command line parameters you can do it via the fw_setevn utility under "sd-fuse_s5p4418/tools".
Check the current Command Line:

cd sd-fuse_s5p4418/tools
./fw_printenv /dev/sdc | grep bootargs

Android 5.1.1_r6 starts SELinux. By default it is enforcing. You can change it this way:

./fw_setenv /dev/sdc bootargs XXX androidboot.selinux=permissive

This sets it to "permissive". The "XXX" stands for the original bootargs' value.

2) Update Kernel
Our customized uboot will check the LCD type when it boots.
For a non-Android OS If it recognizes an LCD connected to the NanoPi M2 it will load "uImage" from "boot" otherwise it will load "uImage.hdmi".
For Android it doesn't make any difference which display device is detected. You can use your generated uImage to replace the existing one under "boot".
For Debian if your generated kernel is for an LCD you need to replace the existing uImage or if your kernel is for HDMI you need to replace the existing uImage.hdmi.

4.5 Run Android or Debian

  • Insert a MicroSD card with Android/Debian image files into your NanoPi M2, connect the NanoPi M2 to an HDMI monitor and a 5V/2A power source the NanoPi M2 will be automatically powered up. If you can see the blue LED flashing it means your board is working and you will see Android/Debain loading on the HDMI monitor.

1)If you connect the NanoPi M2 to an HDMI monitor you need to use a USB mouse and a USB keyboard to operate. If you connect it to an LCD with capacitive touch you can operate directly on the LCD.
2)If you want to do kernel development you'd better have a serial comms board which will allow you to operate the board via a serial terminal.

  • Here is a setup where we connect a NanoPi M2 to a PC running Ubuntu and Minicom via a serial cable you will see system messages output to the PC’s minicom terminal:


  • Under Debian the password for "root" is "fa".

5 Working with Debian

5.1 Ethernet Connection

If the NanoPi M2 is connected to a network via Ethernet before it is powered on it will automatically obtain an IP after it has powered up. If it is not connected via Ethernet or its DHCP is not activated obtaining an IP will fail and system will hang on for about 15 to 60 seconds

  • 1) Setup MAC Address

The NanoPi M2 by default doesn't have a valid MAC address. If the board connects a network successfully it will automatically generates a random MAC in "/etc/network/interfaces.d/eth0". Users can change it to a self-defined valid one:

vi /etc/network/interfaces.d/eth0

Here is the content of a sample configuration file:

auto eth0
allow-hotplug eth0
iface eth0 inet dhcp
hwaddress 76:92:d4:85:f3:0f

The "hwaddress" specifies the MAC address. Here the "76:92:d4:85:f3:0f" is a random MAC. We suggest users change it to a valid one.
Note: when you reset the MAC make sure your MAC meets IEEE's definition otherwise it will cause unexpected issues. After you make your change, save, exit and reboot your board or run the following commands to restart the network:

systemctl restart networking

5.2 Install Debian Packages

We provide a Debian Jessie image. You can install Jessie's packages by commanding "apt-get". If this is your first installation you need to update the package list by running the following command:

apt-get update

You can install your preferred packages. For example if you want to install an FTP server you can do this:

apt-get install vsftpd

Note: you can change your download server by editting "/etc/apt/sources.list". You can get a complete server list from [1]. You need to select the one with "armhf".

5.3 HDMI Audio Output/3.5mm Audio Jack Output Under Debian

By default our Debian system's HDMI output doesn't have audio output. To enable the HDMI audio output you need to install the alsa packages
Firstly, make sure your board runs our latest Debian image and is connected to the internet:
After your board is powered up run the following commands:

apt-get update
apt-get install libasound2
apt-get install alsa-base
apt-get install alsa-utils

After the installation is done copy a ".wav" audio file to your NanoPi M2, connect your NanoPi M2 to an HDMI monitor and play it by using the following command:

aplay music.wav

Our Debian system's default audio output is the 3.5mm audio jack. You can turn on the HDMI audio by editting the /etc/asound.conf file:

pcm.!default {
    type hw
    card 1
    device 0
ctl.!default {
    type hw
    card 1

card 0 points to the 3.5mm audio jack and card 1 points to the HDMI audio. You need to save your changes and reboot your system to make your changes take effect.

6 Make Your Own OS Image

6.1 Setup Development Environment

Install Cross Compiler:

git clone -b master --depth 1
cd prebuilts/gcc-x64
cat toolchain-4.9.3-armhf.tar.gz* | sudo tar xz -C /

Then add the compiler's directory to "PATH" by appending the following lines in "~/.bashrc":

export PATH=/opt/FriendlyARM/toolchain/4.9.3/bin:$PATH
export GCC_COLORS=auto

Execute "~/.bashrc" to make the changes into effect. Note that there is a space after the first ".":

. ~/.bashrc

This compiler is a 64-bit one therefore it cannot be run on a 32-bit Linux. After the compiler is installed you can verify it by running the following commands:

arm-linux-gcc -v
Using built-in specs.
Target: arm-cortexa9-linux-gnueabihf
Configured with: /work/toolchain/build/src/gcc-4.9.3/configure --build=x86_64-build_pc-linux-gnu
--host=x86_64-build_pc-linux-gnu --target=arm-cortexa9-linux-gnueabihf --prefix=/opt/FriendlyARM/toolchain/4.9.3
--with-sysroot=/opt/FriendlyARM/toolchain/4.9.3/arm-cortexa9-linux-gnueabihf/sys-root --enable-languages=c,c++
--with-arch=armv7-a --with-tune=cortex-a9 --with-fpu=vfpv3 --with-float=hard
Thread model: posix
gcc version 4.9.3 (ctng-1.21.0-229g-FA)

6.2 Compile U-Boot

Download the U-Boot source code and compile it. Note that the github's branch is nanopi2-lollipop-mr1:

git clone
cd uboot_nanopi2
git checkout nanopi2-lollipop-mr1
make s5p4418_nanopi2_config
make CROSS_COMPILE=arm-linux-

After your compilation succeeds a u-boot.bin will be generated. If you want to test it flash it to your installation MicroSD card via fastboot. Here is how you can do it:
1) On your PC host run "sudo apt-get install android-tools-fastboot" to install the fastboot utility;
2) Connect your NanoPi M2 to your PC host via a serial cable (e.g. PSU-ONECOME). Press the enter key within two seconds right after you power on your NanoPi M2 and you will enter uboot's command line mode;
3) After type in "fastboot" and press "enter" you will enter the fastboot mode;
4) Connect your NanoPi M2 to this PC host via a microUSB cable and type in the following command to flash the u-boot.bin:

fastboot flash bootloader u-boot.bin

Warning: you cannot update this MicroSD card by commanding "dd". This command will cause trouble when booting the NanoPi M2.

6.3 Prepare mkimage

You need the mkimage utility to compile a U-Boot source code package. Make sure this utility works well on your host before you start compiling a uImage.
You can install this utility by either commanding "sudo apt-get install u-boot-tools" or following the commands below:

cd uboot_nanopi2
make CROSS_COMPILE=arm-linux- tools
sudo mkdir -p /usr/local/sbin && sudo cp -v tools/mkimage /usr/local/sbin

6.4 Compile Linux kernel

6.4.1 Compile Kernel

  • Download Kernel Source Code
git clone
cd linux-3.4.y
git checkout nanopi2-lollipop-mr1

The NanoPi M2's kernel source code lies in the "nanopi2-lollipop-mr1" branch.

  • Compile Android Kernel
make nanopi2_android_defconfig
touch .scmversion
make uImage
  • Compile Debian Kernel
make nanopi2_linux_defconfig
touch .scmversion
make uImage

After your compilation succeeds a uImage will be generated in the "arch/arm/boot/uImage" directory. This kernel is for HDMI 720P. You can use it to replace the existing uImage.hdmi
If you want to generate a kernel for HDMI 1080P you can do it this way:

touch .scmversion
make nanopi2_linux_defconfig
make menuconfig
  Device Drivers -->
    Graphics support -->
      Nexell Graphics -->
        [ ] LCD
        [*] HDMI
        (0)   Display In  [0=Display 0, 1=Display 1]
              Resolution (1920 * 1080p)  --->
make uImage

After your compilation succeeds a uImage will be generated for HDMI 1080P. You can use it to replace the existing uImage.
If you want to generate a kernel for LCD you can do it this way:

touch .scmversion
make nanopi2_linux_defconfig
make menuconfig
  Device Drivers -->
    Graphics support -->
      Nexell Graphics -->
        [*] LCD
        [ ] HDMI
make uImage

After your compilation succeeds a uImage will be generated for LCD. You can use it to replace the existing uImage.

6.4.2 Compile Kernel Modules

Android contains kernel modules which are in the "/lib/modules" directory in the system section. If you want to add your own modules to the kernel or you changed your kernel configurations you need to recompile these new modules.
Compile Original Kernel Modules:

cd linux-3.4.y
make CROSS_COMPILE=arm-linux- modules

Here we have two new modules and we can compile them by following the commands below:

cd /opt/FriendlyARM/s5p4418/android

The "/opt/FriendlyARM/s5p4418/android" directory points to the top directory of Android source code. You can get more details by specifying option "-h".
After your compilation succeeds new modules will be generated

6.5 Compile Android

  • Install Cross Compiler

Installing 64 bit Ubuntu 16.04 on your PC host.

sudo apt-get install bison g++-multilib git gperf libxml2-utils make python-networkx zip
sudo apt-get install flex libncurses5-dev zlib1g-dev gawk minicom

For more details refer to

  • Download Source Code(Android 5.1)

You need to use repo to get the Android source code. Refer to

mkdir android && cd android
repo init -u -b nanopi2-lollipop-mr1
repo sync

The "android" directory is the working directory.

If you want to try Android4.4's source code you can run the following commands:

mkdir android && cd android
repo init -u -b nanopi2-kitkat
repo sync

Option "-b" specifies a branch

  • Compile System Package
source build/
lunch aosp_nanopi2-userdebug
make -j8

After your compilation succeeds the following files will be generated in the "out/target/product/nanopi2/" directory.

filename partition Description
boot.img boot -
cache.img cache -
userdata.img userdata -
system.img system -
partmap.txt - partition description file
  • Flash Image to TF Card

If you want to boot your board from a TF card you can copy your generated image files to your card's sd-fuse_s5p4418/android/ direcroty and flash the image to the card with our script. For more details refer to #Under Linux Desktop.

7 Connect NanoPi M2 to External Modules

7.1 Connect NanoPi M2 to USB Camera(FA-CAM202)

  • In this use case the NanoPi M2 runs Debian. If you connect your NanoPi M2 to our LCD or an HDMI monitor after Debain is fully loaded click on "other"-->"xawtv" on the left bottom of the GUI and the USB Camera application will be started. After enter "welcome to xawtv!" click on "OK" to start exploring.

USB camera-M2

7.2 Connect NanoPi M2 to CMOS 5M-Pixel Camera

For more details about the CAM500B camera refer to [1]

  • If your NanoPi M2 runs Android5.1 and it is connected to our LCD or an HDMI monitor after Android is fully loaded click on the "Camera" icon and the application will be started. You can take pictures or record videos

CMOS camera-M2

  • Under Debian/Ubuntu a camera utility "nanocams" is available for previewing 40 frames and picture taking. You can try it by following the commands below
sudo nanocams -p 1 -n 40 -c 4 -o IMG001.jpg

For more details about the usage of the nanocams run "nanocams -h". You can get its source code from our git hub:

git clone

7.3 Use OpenCV to Access USB Camera

  • The full name of "OpenCV" is Open Source Computer Vision Library and it is a cross platform vision library.
  • When the NanoPi M2 runs Debian users can use OpenCV APIs to access a USB Camera device.

1. Here is a guideline on how to use OpenCV with C++ on the NanoPi M2:

  • Firstly you need to make sure your NanoPi M2 is connected to the internet.Login to your NanoPi M2 via a serial terminal or SSH. After login type in your username(root) and password(fa):
  • Run the following commands:
apt-get update
apt-get install libcv-dev libopencv-dev

2. Make sure your USB camera works with the NanoPi M2. You can test your camera with NanoPi M2's camera utility.
3. Check your camera device:

ls /dev/video*
  • Note:in our case "video0" was the camera's device name.

4. OpenCV's code sample(Official Code Sample in C++) under /home/fa/Documents/opencv-demo. You can compile it by running the following command:

cd /home/fa/Documents/opencv-demo

If it is compiled successfully a demo executable will be generated

5. Connect NanoPi M2 to a USB Keyboard & Run the Following Command:


7.4 Connect NanoPi M2 to USB WiFi

Our system has support for popular USB WiFi drivers. Many USB WiFi modules are plug and play with our system. Here is a list of models we tested;

Number Model
1 RTL8188CUS/8188EU 802.11n WLAN Adapter
2 RT2070 Wireless Adapter
3 RT2870/RT3070 Wireless Adapter
4 RTL8192CU Wireless Adapter
5 MI WiFi mt7601

If you NanoPi M2 is connected to a USB WiFi and is powered up you can log into M2 and run the following command to check if the USB WiFi is recognized. If "wlan0" is listed it indicates your USB WiFi has been recognized:

ifconfig -a

Open the /etc/wpa_supplicant/wpa_supplicant.conf file and append the following lines:


The "YourWiFiESSID" and "YourWiFiPassword" need to be replaced with your actual ESSID and password.
Save, exit and run the following commands to connect to your WiFi router:

ifdown wlan0
ifup wlan0

If your WiFi password has special characters or you don't want your password saved as plain text you can use "wpa_passphrase" to generate a psk for your WiFi password. Here is how you can do it:

wpa_passphrase YourWiFiESSID

Following the prompt type in your password and you will get a new password in the /etc/wpa_supplicant/wpa_supplicant.conf file. Now you can replace the existing password in the wlan0 file with the new one.

  • Click on here to enter the kernel compilation [2]

7.5 Connect NanoPi M2 to Matrix GPS Module

  • The Matrix-GPS module is a small GPS module with high performance. It can be used in navigation devices, four-axle drones and etc.
  • The Matrix-GPS module uses serial communication. When the NanoPi M2 is connected to the Matrix GPS module, after the NanoPi M2 is powered up type in the following command in a terminal or click on the xgps icon it will be started.
$su - fa -c "DISPLAY=:0 xgps"
  • Or on the Debian GUI start the LXTerminal, type in "xgps" and enter it will be started too.

For more details about this GPS module refer to this link
Refer to the following diagram to connect the NanoPi M2 to the Matrix-GPS:

Connection Details:

Matrix-GPS NanoPi M2
RXD Pin8
TXD Pin10
5V Pin4
GND Pin6

7.6 Connect NanoPi M2 to I2C Device

  • The Matrix-I2C_LCD1602_Keypad module is an easy-to-use display module based on the LCD1602. This module integrates the LCD1602 and the MCP23017 module. It has five programmable keys which allow users to control the LCD1602's display and external devices connected to the module.
  • The MCP23017 communicates through I2C interface. You can learn how the NanoPi M2 communicates to an I2C device by studying this module.

For more details about the Matrix - I2C LCD1602 Keypad refer to this link
Refer to the following diagram to connect the NanoPi M2 to the Matrix-I2C_LCD1602_Keypad:

Connection Details:

Matrix-I2C_LCD1602_Keypad NanoPi M2
SDA Pin3
SCL Pin5
5V Pin4
GND Pin6

7.7 Connect NanoPi M2 to SPI Device

  • The Matrix-2'8_SPI_Key_TFT module is a 2.8" TFT LCD module. It uses the ST7789S IC and the XPT2046 resistive IC. The LCD's resolution is 320 * 240 and communicates via SPI. It has three programmable user keys.

For more details about the Matrix-2'8_SPI_Key_TFT SPI module refer to this link
Refer to the following diagram to connect the NanoPi M2 to the Matrix-2'8_SPI_Key_TFT module:

Connection Details

Matrix-2'8_SPI_Key_TFT NanoPi M2
GND Pin6
5V Pin2
LED_EN Pin11
LCD_D/C Pin22
LCD_CS Pin24
T_CS Pin26
T_IRQ Pin18

8 Android Hardware Access

FriendlyElec developed a library called “”, for android developer to access the hardware resources on the development board in their android apps, the library is based on Android NDK.
Accessible Modules:

  • Serial Port
  • PWM
  • ADC
  • LED
  • LCD 1602 (I2C)
  • OLED (SPI)

Accessible Ports:

  • GPIO
  • Serial Port
  • I2C
  • SPI

Please refer to the following url for details:

9 More OS Support

9.1 DietPi

DietPi is a highly optimised & minimal Debian-based Linux distribution. DietPi is extremely lightweight at its core, and also extremely easy to install and use.
Setting up a single board computer (SBC) or even a computer, for both regular or server use, takes time and skill. DietPi provides an easy way to install and run favourite software you choose.
For more information, please visit this link

DietPi supports many of the NanoPi board series, you may download the image file from here:

9.2 FriendlyCore

Ubuntu Core with Qt-Embedded is a light Linux system without X-windows. It uses the Qt-Embedded's GUI and is popular in industrial and enterprise applications. Besides the regular Ubuntu core's features our Ubuntu-Core has the following additional features:

  • it supports our LCDs with both capacitive touch and resistive touch(S700, X710, S70)
  • it supports WiFi
  • it supports Ethernet
  • it supports Bluetooth and has been installed with bluez utilities
  • it supports audio playing

For more details refer to Ubuntu Core with Qt-Embedded.

10 Source Code and Image Files Download Links

  • Images File: [3]
  • Source Code: [4]

11 3D Housing Printing Files

  • NanoPi M2 3D Housing Printing Files: [5]


12 Resources

13 Tech Support

If you have any further questions please visit our forum[6] and post a message or email us at We will endeavor to get back to you as soon as possible.

14 Update Log

14.1 March-01-2016

  • Released English Version

14.2 March-03-2016

  • Modified section 2

14.3 March-04-2016

  • added section 10

14.4 March-07-2016

  • rewrote section 1

14.5 March-17-2016

  • Updated Kali and Ubuntu-Mate download links

14.6 March-18-2016

  • Modified section 4.3.1

14.7 March-27-2016

  • Corrected expression errors

14.8 April-08-2016

  • Added sections 5.3, 7.5, 7.6, 7.7
  • Updated sections 8.1 and 11

14.9 July-05-2016

  • Rewrote section 4.3.3 and 6.5

14.10 Nov-03-2016

  • Updated sections 4.3.1, 7.2 and 7.4

14.11 Dec-07-2016

  • Updated sections 6.5