NanoPi Duo

查看中文

1 Introduction
2 Hardware Spec
3 Software Features
- 3.1 uboot
- 3.2 Ubuntu 16.04
4 Diagram, Layout and Dimension
- 4.1 Layout
- 4.2 Dimensional Diagram
5 Get Started
6 Work with FriendlyCore
7 Make Your Own FriendlyCore
- 7.1 Use Mainline BSP
8 Connect External Modules to Duo
- 8.1 Connect Mini Shield for NanoPi NEO Duo to Duo
9 3D Printing Files
10 Resources
- 10.1 Schematics & Datasheets
11 Update Log

1 Introduction

概览

正面

背面

The NanoPi Duo is designed and developed by FriendlyElec for makers, hobbyists and professionals. It is small, just 50 x 25.4 mm. It uses Allwinner’s Cortex-A7 H2+ SoC. It has 256M/512M DDR3 RAM and an onboard WiFi module. A UbuntuCore image is ready for it.
On such a small board rich interfaces such as Ethernet, USB, SPI, UART, I2C, PWM, IR and audio are exposed. It is powered from a MicroUSB port and boots OS from a MicroSD card.
Popular libraries and utilities: WiringNP and Python are ported to the NanoPi Duo’s system and they all are open source. The NanoPi Duo perfectly suits various light-weight IoT applications.

2 Hardware Spec

CPU: Allwinner H2+, Quad-core Cortex-A7
DDR3 RAM: 256MB/512MB
Connectivity: 10/100M Ethernet
Wifi：XR819
USB Host: 2.54mm pin x2, exposed in 2.54mm pitch pin header
MicroSD Slot x 1
MicroUSB: OTG and power input
Debug Serial Interface: exposed in 2.54mm pitch pin header
Audio input/output Interface: exposed in 2.54mm pitch pin header
GPIO1: 2.54mm spacing 16pin. It includes UART, SPI, I2C, Audio etc
GPIO2: 2.54mm spacing 16pin. It includes USB,10/100M Ethernet, IO etc
PCB Dimension: 25.4 x 50mm
Power Supply: DC 5V/2A
Temperature measuring range: -20℃ to 70℃
OS/Software: U-boot，Linux Kernel 4.11.2 (mainline) , Ubuntu 16.04.2 LTS (Xenial)
Weight: xxg(With Pin-headers)

3 Software Features

3.1 uboot

uboot

3.2 Ubuntu 16.04

mainline kernel: Linux-4.11.2
Ubuntu 16.04.2
rpi-monitor: check system status and information
npi-config: system configuration utility for setting passwords, language, timezone, hostname, SSH and auto-login, and enabling/disabling i2c, spi, serial and PWM
software utility: wiringNP to access GPIO pins
software utility: RPi.GPIO_NP to access GPIO pins
networkmanager: manage networks
system log output from serial port
nano editor
welcome window with basic system information and status
auto-login with user account "pi" with access to npi-config
sudoers include "fa"
on first system boot file system will be automatically extended.
supports file system auto check and repair on system boot.
supports audio recording and playing with 3.5mm audio jack
supports USB Host and 100M Ethernet
fixed MAC address

4 Diagram, Layout and Dimension

4.1 Layout

NanoPi Duo Layout

pinout

GPIO Pin Description

Pin silk screen	Name	Linux gpio	Pin silk screen	Name	Linux gpio
MICN	MIC_N		SPD	EPHY-LED-SPD
MICP	MIC_P		LNK	EPHY-LED-LINK
LOR	LINEOUT_R		TD+	EPHY-TXP
LOL	LINEOUT_L		TD-	EPHY-TXN
CVB	CVBS		RD+	EPHY-RXP
TX1	UART1_TX/GPIOG6	198	RD-	EPHY-RXN
RX1	UART1_RX/GPIOG7	199	DP2	USB-DP2
MO	UART3_RTS/SPI1_MOSI/GPIOA15	15	DM2	USB-DM2
MI	UART3_CTS/SPI1_MISO/GPIOA16	16	DP3	USB-DP3
CLK	UART3_RX/SPI1_CLK/GPIOA14	14	DM3	USB-DM3
CS	UART3_TX/SPI1_CS/GPIOA13	13	IOG11	GPIOG11	203
SDA	I2C0_SDA/GPIOA12	12	IRRX	GPIOL11/IR-RX	363
SCL	I2C0_SCL/GPIOA11	11	GND	GND
GND	GND		3V3	SYS_3.3V
DTX	DEBUG_TX(UART_TXD0)/GPIOA4	4	5Vin	VDD_5V
DRX	DEBUG_RX(UART_RXD0)/GPIOA5/PWM0	5	5Vin	VDD_5V

Note:

SYS_3.3V: 3.3V power output
VDD_5V: 5V power input/output. When the external device’s voltage is greater than the MicroUSB's voltage the external device is powering 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 Duo Schematic

4.2 Dimensional Diagram

For more details refer to the document NanoPi_Duo_v1.0_1706 pcb file in dxf format

5 Get Started

5.1 Essentials You Need

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

NanoPi Duo
microSD Card/TFCard: Class 10 or Above, minimum 8GB SDHC
microUSB power. A 5V/2A power is a must
A Host computer running Ubuntu 16.04 64 bit system
a serial communication board

5.2 TF Cards We Tested

To make your NanoPi Duo boot and run fast we highly recommend you use a Class10 8GB SDHC TF card or better. 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:

5.3 Install OS

5.3.1 Download Image Files

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

Image Files:
nanopi-duo_friendlycore-xenial_4.x.y_YYYYMMDD.img.zip	FriendlyCore (base on UbuntuCore) Image File, kernel:Linux-4.x.y
Flash Utility:
win32diskimager.rar	Windows utility. Under Linux users can use "dd"

5.3.2 NanoPi Duo can work with FriendlyElec's Mini Shield

The NanoPi Duo can work with FriendlyElec's Mini Shield for NanoPi Duo. Here is link to the wiki site of Mini Shield for NanoPi Duo Mini Shield for NanoPi Duo. Here is a hardware setup.
Mini Shield for NanoPi Duo-Duo

6 Work with FriendlyCore

6.1 Introduction

FriendlyCore is a light Linux system without X-windows, based on ubuntu core, It uses the Qt-Embedded's GUI and is popular in industrial and enterprise applications.

Besides the regular Ubuntu Core's features FriendlyCore has the following additional features:

it integrates Qt4.8;
it integrates NetworkManager;
it has bluez and Bluetooth related packages;
it has alsa packages;
it has npi-config;
it has RPiGPIO, a Python GPIO module;
it has some Python/C demo in /root/ directory;
it enables 512M-swap partition;

6.2 System Login

If your board is connected to an HDMI monitor you need to use a USB mouse and keyboard.
If you want to do kernel development you need to use a serial communication board, ie a PSU-ONECOM board, which will

You can use a USB to Serial conversion board too.
Make sure you use a 5V/2A power to power your board from its MicroUSB port:

FriendlyCore User Accounts:

Non-root User:

   User Name: pi
   Password: pi

Root:

   User Name: root
   Password: fa

The system is automatically logged in as "pi". You can do "sudo npi-config" to disable auto login.

Update packages

$ sudo apt-get update

6.3 Configure System with npi-config

The npi-config is a commandline utility which can be used to initialize system configurations such as user password, system language, time zone, Hostname, SSH switch , Auto login and etc. Type the following command to run this utility.

$ sudo npi-config

Here is how npi-config's GUI looks like:

6.4 Develop Qt Application

Please refer to: How to Build and Install Qt Application for FriendlyELEC Boards

6.5 Setup Program to AutoRun

You can setup a program to autorun on system boot with npi-config:

sudo npi-config

Go to Boot Options -> Autologin -> Qt/Embedded, select Enable and reboot.

6.6 Extend TF Card's Section

When FriendlyCore is loaded the TF card's section will be automatically extended.You can check the section's size by running the following command:

$ df -h

6.7 Transfer files using Bluetooth

Take the example of transferring files to the mobile phone. First, set your mobile phone Bluetooth to detectable status, then execute the following command to start Bluetooth search.：

hcitool scan

Search results look like：

Scanning ...
    2C:8A:72:1D:46:02   HTC6525LVW

This means that a mobile phone named HTC6525LVW is searched. We write down the MAC address in front of the phone name, and then use the sdptool command to view the Bluetooth service supported by the phone：

sdptool browser 2C:8A:72:1D:46:02

Note: Please replace the MAC address in the above command with the actual Bluetooth MAC address of the mobile phone.
This command will detail the protocols supported by Bluetooth for mobile phones. What we need to care about is a file transfer service called OBEX Object Push. Take the HTC6525LVW mobile phone as an example. The results are as follows：

Service Name: OBEX Object Push
Service RecHandle: 0x1000b
Service Class ID List:
  "OBEX Object Push" (0x1105)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 12
  "OBEX" (0x0008)
Profile Descriptor List:
  "OBEX Object Push" (0x1105)
    Version: 0x0100

As can be seen from the above information, the channel used by the OBEX Object Push service of this mobile phone is 12, we need to pass it to the obexftp command, and finally the command to initiate the file transfer request is as follows：

obexftp --nopath --noconn --uuid none --bluetooth -b 2C:8A:72:1D:46:02 -B 12 -put example.jpg

Note: Please replace the MAC address, channel and file name in the above command with the actual one.

After executing the above commands, please pay attention to the screen of the mobile phone. The mobile phone will pop up a prompt for pairing and receiving files. After confirming, the file transfer will start.

Bluetooth FAQ：
1) Bluetooth device not found on the development board, try to open Bluetooth with the following command：

rfkill unblock 0

2) Prompt can not find the relevant command, you can try to install related software with the following command：

apt-get install bluetooth bluez obexftp openobex-apps python-gobject ussp-push

6.8 WiFi

For either an SD WiFi or a USB WiFi you can connect it to your board in the same way. The APXX series WiFi chips are SD WiFi chips. By default FriendlyElec's system supports most popular USB WiFi modules. Here is a list of the USB WiFi modules we tested:

Index	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
6	5G USB WiFi RTL8821CU
7	5G USB WiFi RTL8812AU

You can use the NetworkManager utility to manage network. You can run "nmcli" in the commandline utility to start it. Here are the commands to start a WiFi connection:

Change to root

$ su root

Check device list

$ nmcli dev

Note: if the status of a device is "unmanaged" it means that device cannot be accessed by NetworkManager. To make it accessed you need to clear the settings under "/etc/network/interfaces" and reboot your system.

Start WiFi

$ nmcli r wifi on

Scan Surrounding WiFi Sources

$ nmcli dev wifi

Connect to a WiFi Source

$ nmcli dev wifi connect "SSID" password "PASSWORD" ifname wlan0

The "SSID" and "PASSWORD" need to be replaced with your actual SSID and password.If you have multiple WiFi devices you need to specify the one you want to connect to a WiFi source with iface
If a connection succeeds it will be automatically setup on next system reboot.

For more details about NetworkManager refer to this link: Use NetworkManager to configure network settings

If your USB WiFi module doesn't work most likely your system doesn't have its driver. For a Debian system you can get a driver from Debian-WiFi and install it on your system. For a Ubuntu system you can install a driver by running the following commands:

$ apt-get install linux-firmware

In general all WiFi drivers are located at the "/lib/firmware" directory.

6.9 Ethernet Connection

If a board is connected to a network via Ethernet before it is powered on it will automatically obtain an IP with DHCP activated after it is powered up. If you want to set up a static IP refer to: Use NetworkManager to configure network settings。

6.10 WiringPi and Python Wrapper

6.11 Custom welcome message

The welcome message is printed from the script in this directory：

/etc/update-motd.d/

For example, to change the FriendlyELEC LOGO, you can change the file /etc/update-motd.d/10-header. For example, to change the LOGO to HELLO, you can change the following line：

TERM=linux toilet -f standard -F metal $BOARD_VENDOR

To:

TERM=linux toilet -f standard -F metal HELLO

6.12 Modify timezone

For exampe, change to Shanghai timezone:

sudo rm /etc/localtime
sudo ln -ls /usr/share/zoneinfo/Asia/Shanghai /etc/localtime

6.13 Set Audio Device

If your system has multiple audio devices such as HDMI-Audio, 3.5mm audio jack and I2S-Codec you can set system's default audio device by running the following commands.

After your board is booted run the following commands to install alsa packages:

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

After installation is done you can list all the audio devices by running the following command. Here is a similar list you may see after you run the command:

$ aplay -l
card 0: HDMI
card 1: 3.5mm codec
card 2: I2S codec

"card 0" is HDMI-Audio, "card 1" is 3.5mm audio jack and "card 2" is I2S-Codec. You can set default audio device to HDMI-Audio by changing the "/etc/asound.conf" file as follows:

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

If you change "card 0" to "card 1" the 3.5mm audio jack will be set to the default device.
Copy a .wav file to your board and test it by running the following command:

$ aplay /root/Music/test.wav

You will hear sounds from system's default audio device.
If you are using H3/H5/H2+ series board with mainline kernel, the easier way is using npi-config。

6.14 Connect to USB Camera(FA-CAM202)

The FA-CAM202 is a 200M USB camera. Connect your board to camera module. Then boot OS, connect your board to a network, log into the board as root and run "mjpg-streamer":

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

You need to change the start.sh script and make sure it uses a correct /dev/videoX node. You can check your camera's node by running the following commands:

$ apt-get install v4l-utils
$ v4l2-ctl -d /dev/video0 -D
Driver Info (not using libv4l2):
        Driver name   : uvcvideo
        Card type     : HC 3358+2100: HC 3358+2100  / USB 2.0 Camera: USB 2.0 Camera
        Bus info      : usb-1c1b000.usb-1
	...

The above messages indicate that "/dev/video0" is camera's device node.The mjpg-streamer application is an open source video steam server. After it is successfully started the following messages will be popped up:

 
$ ./start.sh
 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

start.sh runs the following two commands:

export LD_LIBRARY_PATH="$(pwd)"
./mjpg_streamer -i "./input_uvc.so -d /dev/video0 -y 1 -r 1280x720 -f 30 -q 90 -n -fb 0" -o "./output_http.so -w ./www"

Here are some details for mjpg_streamer's major options:
-i: input device. For example "input_uvc.so" means it takes input from a camera;
-o: output device. For example "output_http.so" means the it transmits data via http;
-d: input device's subparameter. It defines a camera's device node;
-y: input device's subparameter. It defines a camera's data format: 1:yuyv, 2:yvyu, 3:uyvy 4:vyuy. If this option isn't defined MJPEG will be set as the data format;
-r: input device's subparameter. It defines a camera's resolution;
-f: input device's subparameter. It defines a camera's fps. But whether this fps is supported depends on its driver;
-q: input device's subparameter. It defines the quality of an image generated by libjpeg soft-encoding;
-n: input device's subparameter. It disables the dynctrls function;
-fb: input device's subparameter. It specifies whether an input image is displayed at "/dev/fbX";
-w: output device's subparameter. It defines a directory to hold web pages;

In our case the board's 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:

6.15 Check CPU's Working Temperature

You can get CPU's working temperature by running the following command:

$ cpu_freq 
Aavailable frequency(KHz):
        480000 624000 816000 1008000
Current frequency(KHz):
        CPU0 online=1 temp=26548C governor=ondemand freq=624000KHz
        CPU1 online=1 temp=26548C governor=ondemand freq=624000KHz
        CPU2 online=1 temp=26548C governor=ondemand freq=624000KHz
        CPU3 online=1 temp=26548C governor=ondemand freq=624000KHz

This message means there are currently four CPUs working. All of their working temperature is 26.5 degree in Celsius and each one's clock is 624MHz.
Set CPU frequency:

$ cpu_freq -s 1008000
Aavailable frequency(KHz):
        480000 624000 816000 1008000
Current frequency(KHz):
        CPU0 online=1 temp=36702C governor=userspace freq=1008000KHz
        CPU1 online=1 temp=36702C governor=userspace freq=1008000KHz
        CPU2 online=1 temp=36702C governor=userspace freq=1008000KHz
        CPU3 online=1 temp=36702C governor=userspace freq=1008000KHz

6.16 Test Infrared Receiver

Note: Please Check your board if IR receiver exist.
By default the infrared function is disabled you can enable it by using the npi-config utility:

$ npi-config
    6 Advanced Options     Configure advanced settings
        A8 IR              Enable/Disable IR
            ir Enable/Disable ir[enabled]

Reboot your system and test its infrared function by running the following commands:

$ apt-get install ir-keytable
$ echo "+rc-5 +nec +rc-6 +jvc +sony +rc-5-sz +sanyo +sharp +mce_kbd +xmp" > /sys/class/rc/rc0/protocols   # Enable infrared
$ ir-keytable -t
Testing events. Please, press CTRL-C to abort.

"ir-keytable -t" is used to check whether the receiver receives infrared signals. You can use a remote control to send infrared signals to the receiver. If it works you will see similar messages as follows:

1522404275.767215: event type EV_MSC(0x04): scancode = 0xe0e43
1522404275.767215: event type EV_SYN(0x00).
1522404278.911267: event type EV_MSC(0x04): scancode = 0xe0e42
1522404278.911267: event type EV_SYN(0x00).

6.17 Run Qt Demo

Run the following command

$ sudo /opt/QtE-Demo/run.sh

Here is what you expect to observe. This is an open source Qt Demo:

6.18 How to install and use docker (for armhf system)

6.18.1 How to Install Docker

Run the following commands：

sudo apt-get update
sudo apt-get install docker.io

6.18.2 Test Docker installation

Test that your installation works by running the simple docker image:

git clone https://github.com/friendlyarm/debian-jessie-arm-docker
cd debian-jessie-arm-docker
./rebuild-image.sh
./run.sh

6.19 Read CHIP ID

As for Allwinner H2+/H3/H5/ SoCs each of these CPUs has an internal 16-btye CHIP ID which can be read by running the following commands in the Linux-4.14 kernel:

$ apt-get install bsdmainutils
$ hexdump /sys/bus/nvmem/devices/sunxi-sid0/nvmem 
0000000 8082 0447 0064 04c3 3650 ce0a 1e28 2202
0000010 0002 0000 0000 0000 0000 0000 0000 0000
0000020 0000 0000 0000 0000 0000 0000 0000 0000
0000030 0000 0008 0508 0000 0000 0000 0000 0000
0000040 0000 0000 0000 0000 0000 0000 0000 0000

"8082 0447 0064 04c3 3650 ce0a 1e28 2202" is the 16-byte CHIP ID.

6.20 Boot System from SSD

A NanoPi-Duo can be booted from the SSD on a Mini Shield for NanoPi Duo. Booting OS from an SSD has the following benefits:
1) faster read/write;
2) much longer life time than a TF card;
3) more reliable than booting from a TF card;

You can install an OS to SSD by using the npi-config utility. Here are the steps to follow:

sudo npi-config

Enter the "Boot Options" menu, go to "Boot device" and you will see two options:
1) D1 Hard drive
2) D2 TF card
Select "D1 Hard drive" and proceed with its prompts.
Select "D2 TF card" to boot OS from a TF card.

If your npi-config doesn't have a "Boot device" menu it might be that your npi-config is out of date and you can update it by selecting "Update" in the menu.

6.21 How to install and use docker (for armhf system)

6.21.1 How to Install Docker