Difference between revisions of "NanoPi M1 Plus"

Revision as of 02:27, 1 March 2017

查看中文

1 Introduction

Overview

Front

Back

File:NanoPi M1 Plus-4.jpg

3D Housing

The NanoPi M1 Plus is designed and developed by FriendlyElec for professionals, enterprise users, makers and hobbyists. It is only two thirds the size of a Raspberry Pi. FriendlyElec has made a Debian, Ubuntu-MATE, Ubuntu-Core and Android images ready for it.
The NanoPi M1 Plus uses the Allwinner H3 Soc. It integrates Gbps Ethernet, IR receiver, video/audio output, WiFi & Bluetooth, onboard microphone and supports DVP/Camera/HDMI and CVBS. It has a serial debug port. Its GPIO pins are compatible with those of a Raspberry Pi.

2 Hardware Spec

CPU: Allwinner H3, Quad-core Cortex-A7@1.2GHz
GPU: Mali400MP2@600MHz，Supports OpenGL ES2.0
DDR3 RAM: 1GB
eMMC: 8GB
Wireless: 802.11 b/g/n
Bluetooth: 4.0 dual mode
Antenna Interface: Shared by WiFi and Bluetooth, IPX interface
Connectivity: 10/100/1000M Ethernet
Audio: 3.5mm jack/Via HDMI
Microphone: onboard microphone
IR: onboard IR receiver
USB Host: USB 2.0 x 3, 2 x USB Type A and 1 x 2.54mm pitch pin-header
MicroSD Slot: x1
MicroUSB: power input and data transmission, OTG
Audio Output: HDMI 1.4 1080P, CVBS
DVP Camera Interface: 24pin, 0.5mm pitch FPC seat
Serial Debug Port: 4Pin, 2.54mm pitch pin-header
GPIO： 40pin, 2.54mm pitch pin-header, compatible with RasberryPi 2's GPIO. It contains UART, SPI, I2C, I2S/PCM, SPDIF-OUT and IO
User Button: 1 x Power Button and 1 x Reset Button
LED: 1 x Power LED and 1 x System Status LED
PCB Dimension: 64 x 60 mm, ENIG
Power Supply: DC 5V/2A
OS/Software: u-boot, Debian, Ubuntu-MATE, Ubuntu-Core

3 Diagram, Layout and Dimension

3.1 Layout

NanoPi M1 Plus Layout

GPIO Pin Description

Pin#	Name	Linux gpio	Pin#	Name	Linux gpio
1	SYS_3.3V		2	VDD_5V
3	I2C0_SDA		4	VDD_5V
5	I2C0_SCL		6	GND
7	GPIOG11	203	8	UART1_TX/GPIOG6	198
9	GND		10	UART1_RX/GPIOG7	199
11	UART2_TX/GPIOA0	0	12	PWM1/GPIOA6	6
13	UART2_RTS/GPIOA2	2	14	GND
15	UART2_CTS/GPIOA3	3	16	UART1_RTS/GPIOG8	200
17	SYS_3.3V		18	UART1_CTS/GPIOG9	201
19	SPI0_MOSI/GPIOC0	64	20	GND
21	SPI0_MISO/GPIOC1	65	22	UART2_RX/GPIOA1	1
23	SPI0_CLK/GPIOC2	66	24	SPI0_CS/GPIOC3	67
25	GND		26	SPDIF-OUT/GPIOA17	17
27	I2C1_SDA/GPIOA19/PCM0_CLK/I2S0_BCK	19	28	I2C1_SCL/GPIOA18/PCM0_SYNC/I2S0_LRCK	18
29	GPIOA20/PCM0_DOUT/I2S0_SDOUT	20	30	GND
31	GPIOA21/PCM0_DIN/I2S0_SDIN	21	32	NC
33	NC		34	GND
35	NC		36	NC
37	GPIOA9	9	38	NC
39	GND		40	NC

Debug Port（UART0）

Pin#	Name
1	GND
2	VDD_5V
3	UART_TXD0
4	UART_RXD0

USB Pin Header

Pin#	Name
1	5V
2	DM
3	DP
4	GND

DVP Camera Interface Pin Description

Pin#	Name	Description
1, 2	SYS_3.3V	3.3V Output, it can be used to power camera modules
7,9,13,15,24	GND	Ground, 0V
3	I2C2_SCL	I2C clock signal
4	I2C2_SDA	I2C data signal
5	GPIOE15	regular GPIO, used to control connected camera modules
6	GPIOE14	regular GPIO, used to control connected camera modules
8	MCLK	Clock signals output to camera modules
10	NC	Not connected
11	VSYNC	vertical synchronization
12	HREF/HSYNC	horizontal synchronization
14	PCLK	peripheral clock
16-23	Data bit7-0	data bits

Notes

SYS_3.3V: 3.3V power output
VDD_5V: 5V power output5V. 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
All pins are 3.3V, output current is 5mA
For more details refer to the document:NanoPi-M1-Plus-1702-Schematic.pdf

3.2 Board Dimension

For more details please refer to the document:pcb in dxf format

4 Get Started

4.1 Essentials You Need

Before starting to use your NanoPi M1 Plus get the following items ready

NanoPi M1 Plus
MicroSD Card/TF Card: Class 10 or Above, minimum 8GB SDHC
A DC 5V/2A power is a must
HDMI monitor
USB keyboard, mouse and possible a USB hub(or a TTL to serial board)
A host computer running Ubuntu 14.04 64 bit system

4.2 TF Cards We Tested

To make your NanoPi M1 Plus 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 TF 8G Class10 Micro/SD TF card:

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

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

4.3 Make an Installation TF Card

4.3.1 Download Image Files

Get the following files from here download link to download image files (under the "officail-ROMs" diirectory) and the flashing utility (under the "tools" diirectory):

Image Files
nanopi-m1-plus-debian-sd4g.img.zip	Debian Image File
nanopi-m1-plus-ubuntu-core-qte-sd4g.img.zip	Ubuntu core with Qt Embedded
nanopi-m1-eflasher-sd8g.img.zip	eflasher which can be used to Flash image files to eMMC
nanopi-m1-plus-android.img.zip	Android Image File
Flash Utility
win32diskimager.rar	Windows utility. Under Linux users can use "dd"
PhoenixCard_V310.rar	Windows utility for flashing Android image. Attention: the "dd" command under Linux doesn't work for flashing Android image
HDDLLF.4.40.exe	Windows utility for formatting a TF card

4.3.2 TF Card Systems

4.3.2.1 Make Debian Image Card

Extract the nanopi-m1-plus-debian-sd4g.img.zip and win32diskimager.rar files. Insert a TF card(at least 8G) into a Windows PC and run the win32diskimager utility as administrator. On the utility's main window select your TF card's drive, the wanted image file and click on "write" to start flashing the TF card.
Insert this card into your NanoPi M1 Plus' BOOT slot 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 M1 Plus has successfully booted.

Note:you can make a Ubuntu image card in this way too.

4.3.2.2 Make Android Image Card

On a Windows PC run the HDDLLF.4.40 utility as administrator. Insert a TF card(at least 8G) into this PC and format it. After formatting is done take out the TF card, insert it into the PC again and format it with Windows internal format utility to format it to FAT32. After this formatting is done take out the card.
Extract the nanopi-m1-plus-android.img.zip and PhoenixCard_V310.rar files. Insert the TF card you made in the previous step into a Windows PC and run the PhoenixCard_V310 utility as administrator. On the utility's main window select your TF card's drive, the wanted image file and click on "write" to start flashing the TF card.
Insert this card into your NanoPi M1 Plus' BOOT slot 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 M1 Plus has successfully booted.

Note: you must format your TF card before you start making it an Android image card.

4.3.3 Flash image to eMMC with eflasher

Extract the nanopi-m1-eflasher-sd8g.img.zip and win32diskimager.rar files. Insert a TF card(at least 4G) into a Windows PC and run the win32diskimager utility as administrator. On the utility's main window select your TF card's drive, the wanted image file and click on "write" to start flashing the TF card.
Insert this card into your NanoPi M1 Plus' BOOT slot 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 M1 Plus has successfully booted.
Connect the board to an HDMI monitor or an LCD and a USB mouse, and select an OS to start installation.

If no monitor is connected you can select an OS by running the following command:

eflasher

Type a number and enter to select an OS, then type "yes" and enter to start installation. After installation is done shutdown the system, take out the TF card, power on your board again and it will boot from eMMC.

5 Work with Debian

5.1 Run Debian

Insert a TF card with Debian image into your NanoPi M1 Plus, connect the it to an HDMI monitor and a 5V/2A power it will be automatically powered on. If you can see the blue LED flashing it means your board is working and you will see Debain being loaded on the HDMI monitor.

1) If you connect your NanoPi M1 Plus to an HDMI monitor you need to use a USB mouse and a USB keyboard to operate.
2) If you want to do kernel development you need to use a serial communication board, ie a PSU-ONECOM board, which will allow you to operate the board via a serial terminal.

Here is a setup where we connect a NanoPi M1 Plus to a PC via the PSU-ONECOM and you can power on your M1 Plus from either the PSU-ONECOM or its MicroUSB:

The password for both "root" and "fa" is "fa" under Debian.
Update packages

sudo apt-get update

5.2 Extend TF Card's rootfs Section

When you boot Debian for the first time with your image card your OS will automatically resize the file system and this process takes a relatively long time.After your OS is fully loaded you can check the file system's size by using the following command:

df -h

5.3 Ethernet Connection

If the NanoPi M1 Plus is connected to a network via Ethernet before it is powered on it will automatically obtain an IP after it is 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. Run the following command to check its MAC address:

dhclient eth0

5.4 Wireless Connection

Open the file "/etc/wpa_supplicant/wpa_supplicant.conf" with vi or gedit and append the following lines:

network={
        ssid="YourWiFiESSID"
        psk="YourWiFiPassword"
}

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

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. If you open the file "/etc/wpa_supplicant/wpa_supplicant.conf" you will find that your password has been updated and you can delete your clear-text password.

5.5 Login to Debian via VNC and SSH

If your NanoPi M1 Plus is not connected to a display device you can login to your NanoPi M1 Plus from a mobile phone or PC. You need to download and install a "VNC Viewer" from here and login to the NanoPi M1 Plus via VNC at port 1. Its default password is "fa123456".
Here is a screenshot which shows how it looks like when users login to a NanoPi M1 Plus from an iPhone via VNC:

You can login via "SSH -l root 192.168.8.1" and the default password for "root" is "fa". You need to replace "192.168.8.1" with your actual IP address.

5.6 HDMI Audio Output

Our Debian system's default audio output is the 3.5mm audio jack. You can turn on the HDMI audio by editing 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.

5.7 Test GPU

After Debian loads please login from a terminal and run "glmark2-es2":

glmark2-es2

5.8 Test VPU

Visit this link download link to download the test files under the "test-video" directory
After Debian is loaded login from a terminal and run the following commands:

sudo apt-get install mpv
video_play mpv ./big_buck_bunny_1080p_H264_AAC_25fps_7200K.MP4

In our test it could do hard coding and play 1080P video fluently.

5.9 Test USB WiFi

Our Debian 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 802.11n WLAN Adapter
2	RT2070 Wireless Adapter
3	RT2870/RT3070 Wireless Adapter
4	RTL8192CU Wireless Adapter
5	mi WiFi mt7601

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

ifconfig -a

We assume the USB WiFi's node is wlan1.
Open the /etc/wpa_supplicant/wpa_supplicant.conf file and append the following lines:

network={
        ssid="YourWiFiESSID"
        psk="YourWiFiPassword"
}

The "YourWiFiESSID" and "YourWiFiPassword" need to be replaced with your actual ESSID and password.

Append the following lines in the "/etc/network/interfaces" file:

allow-hotplug wlan1
iface wlan1 inet dhcp
        wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

By running the following commands you will be able to connect your board to a WiFi router:

ifdown wlan1
ifup wlan1

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.

5.10 Connect NanoPi M1 Plus to DVP Camera CAM500B

The CAM500B camera module is a 5M-pixel camera with DVP interface. For more tech details about it you can refer to Matrix - CAM500B.

Follow the hardware setup presented in the above picture to connect your NanoPi M1 Plus to a CAM500B. Then boot Debian on your M1 Plus, connect your M1 Plus to a network, log into the board as root and run "mjpg-streamer":

cd /root/mjpg-streamer
make
./start.sh

The mjpg-streamer application is an open source video steam server. After it is successfully started the following messages will be popped up:

 
 i: Using V4L2 device.: /dev/video0
 i: Desired Resolution: 1280 x 720
 i: Frames Per Second.: 30
 i: Format............: YUV
 i: JPEG Quality......: 90
 o: www-folder-path...: ./www/
 o: HTTP TCP port.....: 8080
 o: username:password.: disabled
 o: commands..........: enabled

In our case the M1 Plus' IP address was 192.168.1.230. We typed 192.168.1.230:8080 in a browser and were able to view the images taken from the camera's. Here is what you would expect to observe:

The mjpg-streamer soft-encodes data with libjpeg and you can hard-encode its data with ffmpeg which will greatly increase CPU's efficiency and speed up data encoding:

ffmpeg -t 30 -f v4l2 -channel 0 -video_size 1280x720 -i /dev/video0 -pix_fmt nv12 -r 30 \
        -b:v 64k -c:v cedrus264 test.mp4

By default it records a 30-second video. Typing "q" stops video recording. After recording is stopped a test.mp4 file will be generated.

5.11 Connect NanoPi M1 Plus to USB Camera(FA-CAM202)

The FA-CAM202 is a 200M USB camera.
In this use case the NanoPi M1 Plus runs Debian. Connect your NanoPi M1 Plus to an HDMI monitor. After Debain is fully loaded open a terminal and run the following command:

xawtv 0

You will be able to preview with your camera Note: "0" in our case stands for the camera's device name "/dev/video0". You need to use your camera's index in this command.

5.12 Use OpenCV to Access Camera

The full name of "OpenCV" is Open Source Computer Vision Library and it is a cross platform vision library.
Make sure your NanoPi M1 is connected to the internet and an HDMI monitor. Boot Debian on the NanoPi M1 and login
Install OpenCV libraries:

apt-get update
apt-get install libcv-dev libopencv-dev

Refer to the instructions in the previous sections to make sure the camera works
Compile and run a code sample（Official Code Sample in C++ provided by the OpenCV organization):

cd /home/fa/Documents/opencv-demo
make
./demo

Here is what you expect to observe:

5.13 Check CPU's Working Temperature

You can use the following command to read H3's temperature and frequency

cpu_freq

5.14 Check System Information with Rpi-Monitor

Our Debian contains the Rpi-Monitor utility with which users can check system information and status.
In our case our NanoPi M1's IP was 192.168.1.230 and we typed the following IP in a browser:

192.168.1.230:8888

We were directed to the following page:

Users can easily check these system information and status.

6 Make Your Own Debian

6.1 Preparations

Visit this link [1] and enter the "sources/nanopi-H3-bsp" directory and download all the source code.Use the 7-zip utility to extract it and a lichee directory and an Android directory will be generated.You can check that by running the following command:

ls ./
android lichee

Or you can get it from our github:

git clone https://github.com/friendlyarm/h3_lichee.git lichee

Note: "lichee" is the project name named by Allwinner for its CPU's source code which contains the source code of U-boot, Linux kernel and various scripts.

6.2 Install Cross Compiler

Visit this site download link, enter the "toolchain" directory, download the cross compiler "gcc-linaro-arm.tar.xz" and copy it to the "lichee/brandy/toochain/" directory.

6.3 Compile lichee Source Code

Compilation of the H3's BSP source code must be done under a PC running a 64-bit Linux.The following cases were tested on Ubuntu-14.04 LTS-64bit:

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

Enter the lichee directory and run the following command to compile the whole package:

cd lichee
./build.sh -p sun8iw7p1 -b nanopi-h3

After this compilation succeeds a u-boot, Linux kernel and kernel modules will be generated
Note: the lichee directory contains a cross-compiler we have setup. When the build.sh script runs it will automatically call this cross-compiler.

6.4 Package System Modules

./gen_script.sh -b nanopi-m1-plus

This command patches the uboot with Allwinner features and copies the generated executables including u-boot and Linux kernel and configuration files to the "lichee/tools/pack/out/" directory and generates a script.bin.

Run the following commands to update the uboot on your MicroSD card:

./fuse_uboot.sh /dev/sdx

Replace the "/dev/sdx" with the actual device name of your MicroSD card.
The boot.img and kernel modules are under the "linux-3.4/output" directory. You can copy the new boot.img file to your MicroSD card's boot section.

6.5 Compile U-boot

./build.sh -p sun8iw7p1 -b nanopi-h3 -m uboot
./gen_script.sh -b nanopi-m1-plus

The gen_script.sh script patches the U-boot with Allwinner features. A U-boot without these features cannot work.
Type the following command to update the U-boot on the MicroSD card:

./fuse_uboot.sh /dev/sdx

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

6.6 Compile Linux Kernel

If you want to compile the Linux kernel run the following command:

./build.sh -p sun8iw7p1 -b nanopi-h3 -m kernel

After the compilation is done a boot.img and its kernel modules will be generated under "linux-3.4/output".

6.7 Clean Source Code

./build.sh -p sun8iw7p1_linux -b nanopi-h3 -m clean

7 Applications under Android

7.1 USB WiFi

The rtl8188etv/rtl8188eu USB WiFi modules are supported in Android.

7.2 IR Controller(RC-100)

You can use FriendlyARM's IR controller(RC-100) to navigate the Android system.
Here is a list of the function keys on the RC-100 IR controller

Key	Function
POWER	On/Off
F1	Search
F2	Open Browser
F3	Enable/Disable Mouse
UP	Move Up
DOWN	Move Down
LEFT	Move Left
RIGHT	Move Right
OK	OK
Volume-	Turn Down Volume
Mute	Mute
Volume+	Turn Up Volume
SETTING	Go to Setting Window
HOME	Go to Home Window
BACK	Go Back to the Previous Window

After Android is loaded for the first time you need to follow the prompts on Android's GUI to enter the main window and then press F3 to enable mouse and complete the setup process by navigating "up", "down", "left", "right" and "OK".

7.3 Play 4K Video

Visit this the test-video directory of this link download link and download the 4K video file: 4K-Chimei-inn-60mbps.mp4 and copy it to an SD card or USB drive.
Boot Android on your M1 Plus and insert this SD card or USB drive to it. After locate the 4K video file with ESFileExplorer click on and play it with Android's Gallery player.
In our test playing this 4K video file from a USB drive worked better.

8 Make Your Own Android

8.1 Preparations

Visit this download link and enter the "sources/nanopi-H3-bsp" directory and download all the source code.Use the 7-zip utility to extract it and a lichee directory and an Android directory will be generated.You can check that by running the following command:

ls ./
android lichee