Difference between revisions of "NanoPi NEO"

Revision as of 04:24, 27 December 2017

查看中文

1 Introduction
2 Hardware Spec
3 Software Features
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
- 7.2 Use Allwinner's BSP
8 3D Printing Files
9 Other OS Support
10 Connect External Modules to NEO
11 Resources
- 11.1 Development Guide & Tutorials
  - 11.1.1 Access Hardware in Python
  - 11.1.2 Access Hardware in C
12 Hardware Differences Among Different Versions
13 Update Log

1 Introduction

Overview

Front

Back

The NanoPi NEO(abbreviated as NEO) is another fun board developed by FriendlyARM for makers, hobbyists and fans.

2 Hardware Spec

CPU: Allwinner H3, Quad-core Cortex-A7 Up to 1.2GHz
DDR3 RAM: 256MB/512MB
Connectivity: 10/100M Ethernet
USB Host: Type-A x 1, 2.54 mm pin x 2
MicroSD Slot x 1
MicroUSB: OTG, for power input
Debug Serial Port: 4Pin, 2.54 mm pitch pin header
Audio input/output Port: 5Pin, 2.0mm pitch pin header
GPIO: 2.54mm pitch 36pin. It includes UART, SPI, I2C, IO etc
Power Supply: DC 5V/2A
PCB Dimension: 40 x 40 mm
Working Temperature: -40℃ to 80℃
Weight: 14g(WITHOUT Pin-headers)
OS/Software: u-boot, UbuntuCore and Android

3 Software Features

3.1 uboot

mainline uboot released on May 2017
supports fastboot to update uboot

3.2 UbuntuCore 16.04

mainline kernel: Linux-4.11.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 network
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 FriendlyElec's NanoHat-PCM5102A
supports USB WiFi module: refer to #Connect USB WiFi to NEO
supports audio recording and playing with 3.5mm audio jack
supports USB Host and 100M Ethernet
supports FriendlyElec BakeBit modules
supports dynamic frequency scaling and voltage regulation
relieves overheat compared to kernel Linux-3.4
fixed MAC address

3.3 Ubuntu OLED

mainline kernel: Linux-4.11.2
supports FriendlyElec's OLED module

3.4 Debian

welcome window with basic system information and status

3.5 Debian for NAS Dock

mainline kernel: Linux-4.11.2
supports FriendlyElec's NAS Dock
optimized OpenMediaVault configuration options
allocated swap section

3.6 Android

basic system

4 Diagram, Layout and Dimension

4.1 Layout

NanoPi NEO Layout

pinout

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	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

USB/Audio/IR Pin Description

NanoPi-NEO			NanoPi-NEO V1.1/V1.2
Pin#	Name	Description	Pin#	Name	Description
1	VDD_5V	5V Power Out	1	VDD_5V	5V Power Out
2	USB-DP1	USB1 DP Signal	2	USB-DP1	USB1 DP Signal
3	USB-DM1	USB1 DM Signal	3	USB-DM1	USB1 DM Signal
4	USB-DP2	USB2 DP Signal	4	USB-DP2	USB2 DP Signal
5	USB-DM2	USB2 DM Signal	5	USB-DM2	USB2 DM Signal
6	GPIOL11/IR-RX	GPIOL11 or IR Receive	6	GPIOL11/IR-RX	GPIOL11 or IR Receive
7	SPDIF-OUT/GPIOA17	GPIOA17 or SPDIF-OUT	7	SPDIF-OUT/GPIOA17	GPIOA17 or SPDIF-OUT
8	MICIN1P	Microphone Positive Input	8	PCM0_SYNC/I2S0_LRC	I2S/PCM Sample Rate Clock/Sync
9	MICIN1N	Microphone Negative Input	9	PCM0_CLK/I2S0_BCK	I2S/PCM Sample Rate Clock
10	LINEOUTR	LINE-OUT Right Channel Output	10	PCM0_DOUT/I2S0_SDOUT	I2S/PCM Serial Data Output
11	LINEOUTL	LINE-OUT Left Channel Output	11	PCM0_DIN/I2S0_SDIN	I2S/PCM Serial Data Input
12	GND	0V	12	GND	0V

V1.1/V1.2 Audio

Pin#	Name	Description
1	MICIN1P	Microphone Positive Input
2	MICIN1N	Microphone Negative Input
3	LINEOUTR	LINE-OUT Right Channel Output
4	GND	0V
5	LINEOUTL	LINE-OUT Left Channel Output

Debug Port（UART0）

Pin#	Name
1	GND
2	VDD_5V
3	UART_TXD0
4	UART_RXD0

Note:

SYS_3.3V: 3.3V power output
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
All pins are 3.3V, output current is 5mA
For more details refer to the document: NanoPi-NEO-v1.31-1703-Schematic.pdf

4.2 Dimensional Diagram

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

5 Get Started

5.1 Essentials You Need

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

NanoPi NEO
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

5.2 TF Cards We Tested

To make your NanoPi NEO 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:

5.3 Make an Installation TF Card

5.3.1 Get Image Files

Visit this link download link to download image files and the flashing utility:

Image Files:
nanopi-neo_friendlycore-xenial_3.4.y_YYYYMMDD.img.zip	FriendlyCore (base on UbuntuCore) Image File, Kernel: Linux-3.4.y
nanopi-neo_friendlycore-xenial_4.x.y_YYYYMMDD.img.zip	FriendlyCore (base on UbuntuCore) Image File, Kernel: Linux-4.x.y
nanopi-neo_debian-nas-jessie_4.x.y_YYYYMMDD.img.zip	Image File with Support for NAS Dock, Kernel: Linux-4.x.y, applicable to 1-bay NAS Dock
nanopi-neo_ubuntu-oled_4.x.y_YYYYMMDD.img.zip	Image File with Support for OLED Module, Kernel: Linux-4.x.y, applicable to NanoHat OLED
Flash Utility:
win32diskimager.rar	Windows utility for flashing Debian image. Under Linux users can use "dd"

5.3.2 Comparison of Linux-3.4.y and Linux-4.x.y

Our Linux-3.4.y is provided by Allwinner. Allwinner has done a lot of customization work which on one hand contains many features and functions but on the other hand incurs overheat issues;
Our Linux-4.x.y is updated very often. We will keep this kernel with the latest one released by Linus Torvalds. This kernel doesn't generate heat that much and if you don't need to use VPU or GPU you can try this kernel;

Here is a comparison table:

5.3.3 Make UbuntuCore with Qt Embedded Image Card

Extract the image file 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.After flashing is done insert this TF card to your NanoPi NEO and connect the board to a 5V/2A power NEO will be automatically powered on. If the blue LED is flashing it indicates the system is being booted.

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

allow you to operate the board via a serial terminal.Here is a setup where we connect a board to a PC via the PSU-ONECOM and you can power on your board from either the PSU-ONECOM or its MicroUSB:
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 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.8 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.9 WiringPi and Python Wrapper

6.10 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.11 Modify timezone

For exampe, change to Shanghai timezone:

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

6.12 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.13 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.14 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.15 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.16 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.17 How to install and use docker (for armhf system)

6.17.1 How to Install Docker

Run the following commands：

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

6.17.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

7 Make Your Own FriendlyCore

7.1 Use Mainline BSP

The NanoPi NEO has gotten support for kernel Linux-4.x.y with Ubuntu Core 16.04. For more details about how to use mainline u-boot and Linux-4.x.y refer to :Mainline U-boot & Linux

7.2 Use Allwinner's BSP

7.2.1 Preparations

Visit this link 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

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.

7.2.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.

7.2.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 u-boot-tools

Run the following command to compile lichee:

$ cd lichee/fa_tools
$ ./build.sh -b nanopi-neo -p linux -t all

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. 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.
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 partition.

7.2.4 Compile U-boot

Note:you need to compile the whole lichee directory before you can compile U-boot individually.

$ cd lichee/fa_tools/
$ ./build.sh -b nanopi-neo -p linux -t u-boot

Type the following command to update the U-boot on the MicroSD card:

$ cd lichee/fa_tools/
$ ./fuse.sh -d /dev/sdX -p linux -t u-boot

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

7.2.5 Compile Linux Kernel

Note:you need to compile the whole lichee directory before you can compile Linux kernel individually.
If you want to compile the Linux kernel run the following command:

$ cd lichee/fa_tools/
$ ./build.sh -b nanopi-neo -p linux -t kernel

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

7.2.6 Clean Source Code

$ cd lichee/fa_tools/
$ ./build.sh -b nanopi-neo -p linux -t clean

8 3D Printing Files

Link to 3D Printing Files

9 Other OS Support

9.1 DietPi_NanoPiNEO-armv7-(Jessie)

DietPi is an extremely lightweight Debian Jessie OS. Its image file starts at 400MB and nearly 3x lighter than 'Raspbian Lite'.It is pre-installed with DietPi-RAMLog. These features enable users to get the best performance of a device.
The following steps are for reference only. FriendlyElec doesn't provide technical support for them.
Installation guide:

Download the image file "DietPi_NanoPiNEO-armv7-(Jessie)" from DietPi_NanoPiNEO-armv7-(Jessie)
Extract the package and use the win32diskimager to write it to a MicroSD card under Windows.
Insert this MicroSD card to your NanoPi NEO and power up.

Username:root , Password: dietpi

9.2 Armbian

Armbian releases Armbian_5.20_Nanopineo_Debian_jessie_3.4.112 and Armbian_5.20_Nanopineo_Ubuntu_xenial_3.4.112 for the NanoPi NEO. You can refer to its home page for more details.
home page: http://www.armbian.com/nanopi-neo/

9.3 Android

This Android system is an Android4.4.2 variant.
FriendlyARM doesn't provide technical support for it.

Download image files and utilities

Visit this download link and enter the "unofficail-ROMs" to download the nanopi-neo-android.img.zip image file, HDDLLF.4.40 and HDDLLF(under the "tools" directory).

Make Android Installation Card

1. On a Windows PC run the HDDLLF.4.40 utility as administrator. Insert a TF card(at least 4G) into this PC and format it. After formatting is done take out the TF card;
2. 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;
3. Insert the TF card you made in the previous step into a Windows PC and run the PhoenixCard 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.
Note: none of the above steps should be missed otherwise the TF card you made may not work.

Boot Android

Insert this installation card into your NanoPi NEO, power on the board and you will be able to work with it
The password for "root" or "fa" is "fa"

This Android supports these WiFi cards: rtl8188etv and rt8188eus.

10 Connect External Modules to NEO

10.1 DIY NAS Server with 1-bay NAS Dock & NEO

The 1-bay NAS Dock is an expansion board which can be used to connect an external hard disk to a NanoPi NEO.It uses JSM568 USB3.0 to SATA IC and communicates with a NanoPi NEO via USB interface. It works with a 2.5" SATA hard disk.It uses TI's DC-DC chipset to convert a 12V input to 5V. It has a power switch for users to turn on/off the device.It supports an onboard RTC battery. FriendlyElec migrated mainline Linux-4.11 kernel and Debian-Jessie with OpenMediaVault. Together with FriendlyElec's customized aluminum case you can quickly assemble a storage server. Here is a hardware setup :1-bay_NAS_Dock

10.2 Connect Python Programmable NanoHat OLED to NEO

The NanoHat OLED module is a small and cute monochrome OLED module with low power consumption. It has three user buttons. We provide its driver's source code and a user friendly shell interface on which you can check system information and status.A customized aluminum case is made for it. You cannot miss this lovely utility! Here is a hardware setup:NanoHat OLED

10.3 Connect Python Programmable NanoHat Motor to NEO

The NanoHat Motor module can drive four 5V PWM steering motors and four 12V DC motors or four 5V PWM steering motors and two 12V four-wire step motors.Here is a hardware setup: NanoHat Motor

10.4 Connect NanoHat PCM5102A to NEO

The NanoHat PCM5102A module uses TI's DAC audio chip PCM5102A, a convenient and easy-to-use audio module for hobbyists. Here is a hardware setup:NanoHat PCM5102A

10.5 Connect Arduino Compatible UNO Dock to NEO

The UNO Dock module is an Arduino board compatible with Arduino UNO and works with Arduino programs.You can use Arduino IDE to run all Arduino programs on the Dock.It also exposes the NanoPi NEO's pins.It converts 12V power input to 5V/2A output.You can search for various code samples from Ubuntu's ecosystem and run on the Dock. These features make it a powerful platform for IOT projects and cloud related applications. Here is a hardware setup:UNO Dock for NanoPi NEO v1.0

10.6 Connect Power Dock to NEO

The Power Dock for NanoPi NEO is a high efficiency power conversion module. It provides stable and reliable power source. Here is a hardware setup:Power Dock for NanoPi NEO

10.7 Connect NanoHat Proto to NEO

The NanoHat Proto is an expansion board which exposes NEO's various pins.It has an onboard EEPROM for data storage.Here is a hardware setup:NanoHat Proto

10.8 Connect Matrix - 2'8 SPI Key TFT to NanoPi NEO

The Matrix-2'8_SPI_Key_TFT module is a 2.8" TFT LCD with resistive touch. It uses the ST7789S IC and XPT2046 resistive touch IC. It has SPI interface and three configurable user keys.Here is its wiki page Matrix - 2'8 SPI Key TFT

11 Resources

11.1 Development Guide & Tutorials

11.1.1 Access Hardware in Python

Programming Python on NanoPi NEO:

The following BakeBit modules can work with BakeBit - NanoHat Hub:

11.1.2 Access Hardware in C

Matrix Modules & Wiki Sites:

12 Hardware Differences Among Different Versions

NanoPi NEO Version Compare & List（Hardware）

version	NanoPi NEO V1.0	NanoPi NEO V1.1	NanoPi NEO V1.2	NanoPi NEO V1.3
Photo
Power Design	① VDD1V2-SYS's power input from LDO	① VDD1V2-SYS's power input from LDO	① VDD1V2-SYS's power input changed from LDO to DC/DC (Most changes applied to NanoPi NEO V1.2 are to relieve over-heat)	① VDD1V2-SYSDC/DC's power input is the same as that of V1.2 ⑤ Used VDD-CPUX's DC/DC chip to MP2143DJ to relieve over heat
Audio Interface		② NanoPi NEO V1.1/V1.2 has onboard audio which V1.0 doesn't have	② NanoPi NEO V1.1/V1.2 has onboard audio which V1.0 doesn't have	② ④ NanoPi NEO V1.3 swapped the positions of the audio and Debug_UART compared to their positions in V1.1/V1.2 ② Improve audio's performance
12Pin 2.54mm Pitch Pinheader	③ NanoPi NEO V1.0's Pin Description	③ NanoPi NEO V1.1's Pin Description Different from That of V1.0	③ NanoPi NEO V1.2's Pin Description Same as That of V1.1	③ NanoPi NEO V1.3's Pin Description Same as That of V1.1/V1.2

13 Update Log

13.1 July-07-2016

Released English Version

13.2 August-09-2016

Added Other OS Support

13.3 Sep-08-2016

Added Section 7
Updated sections 5.3, 5.5 and 9

13.4 Nov-03-2016

Added Section 5.6

13.5 Dec-20-2016

Added Section 5.8

13.6 Jan-10-2017

Added Section 8.1
Updated Section 8.2

13.7 Feb-1-2017

Added Section 8.3
Updated Sections 6 and 9

13.8 March-5-2017

Added section 8, 9 and 13
Updated section 12.1

13.9 April-5-2017

Added sections 5.2
Updated sections 5.5 and 13

13.10 May-7-2017

Added section 12: mainline support for H3
Added section 13: support for external modules

13.11 May-17-2017

Added section 5.10: WiringNP support for NEO

13.12 May-24-2017

Updated section 4.3.1: More image files for NEO
Added section 6.1: Mainline support for NEO
Added section 3: software features

13.13 June-4-2017

Updated section 5.3.1: updated image files' version numbers
Updated section 3: added more OS features

13.14 June-8-2017

Updated section 3.2: added support for RPi.GPIO_NP
Added section 6.11: added support for RPi.GPIO_NP

13.15 June-12-2017

Added section 5.3.2: added comparison table of Linux-3.4.y and Linux-4.x.y

13.16 July-8-2017

Added section 10.8: added working with 2.8"TFT LCD

13.17 July-12-2017

Updated section 1: revised picture resolutions

@@ Line 280: / Line 280: @@
 </syntaxhighlight>
 Note: you need to replace "/dev/sdx" with the device name in your system.<br>
-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.
+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 partition.
 ====Compile U-boot====