- 1 Introduction
- 2 Hardware Spec
- 3 Diagram, Layout and Dimension
- 4 Get Started
- 5 Work with Ubuntu-Core with Qt-Embedded
- 6 Using the GPIO pins/Wiring for NanoPi NEO
- 7 Make Your Own Ubuntu-Core with Qt-Embedded
- 8 Setup Cross Compiler for User Space Programs
- 9 Applicable Mainline U-boot & Linux for H3
- 10 3D Printing Files
- 11 Other OS Support
- 12 Resources
- 13 Hardware Differences Among Different Versions
- 14 Update Log
- The NanoPi NEO(abbreviated as NEO) is another fun board developed by FriendlyARM for makers, hobbyists and fans.
- 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
Diagram, Layout and Dimension
- 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
- 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
- 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-1606-Schematic.pdf
- For more details refer to the document: pcb file in dxf format
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 14.04 64 bit system
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:
Make an Installation TF Card
Get Image Files
Visit this link download link to download image files and the flashing utility:
Image Files nanopi-neo-ubuntu-core-qte-sd4g.img.zip UbuntuCore with Qt-Embedded Image File Flash Utility: win32diskimager.rar Windows utility for flashing Debian image. Under Linux users can use "dd"
Make UbuntuCore with Qt Embedded Image Card
- Extract the nanopi-neo-ubuntu-core-qte-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.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.
Work with Ubuntu-Core with Qt-Embedded
Run Ubuntu-Core with Qt-Embedded
- Insert a TF card with UbuntuCore image files into your NanoPi NEO, connect the board to a 5V/2A power source the board will be automatically powered on. If you can see the blue LED flashing it means your board is working and UbuntuCore is being loaded.
- 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 NEO to a PC via the PSU-ONECOM and you can power on your NEO from either the PSU-ONECOM or the board's MicroUSB:
- Ubuntu-Core's User Accounts:
User Name: pi Password: pi
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
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.
If the NanoPi NEO 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.
Login via SSH
The NanoPi NEO doesn't have a video output interface. You can log into the board via SSH. In our test the IP address detected by our router was 192.168.1.230 and we ran the following command to log into the NanoPi NEO:
The password is fa
Connect USB WiFi to NEO
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 NEO is connected to a USB WiFi and is powered up you can log into NEO 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:
sudo ifconfig -a
You can use the NetworkManager utility in Ubuntu to manager its network. You can run "nmcli" in the commandline utility to start it. Here are the commands to start a WiFi connection:
- Check device list
sudo nmcli dev
Note: if the status of a device is "unmanaged" it means that device cannot be accessed by NetworkManager. To make is accessed you need to clear the settings under "/etc/network/interfaces" and reboot your system.
- Start WiFi
sudo nmcli r wifi on
- Scan Surrounding WiFi Sources
sudo nmcli dev wifi
- Connect to a WiFi Source
sudo nmcli dev wifi connect "SSID" password "PASSWORD"
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: NetworkManager
Connect NanoPi NEO to USB Camera(FA-CAM202)
cd /root/mjpg-streamer make ./start.sh
The mjpg-streamer is an open source media server. After it is started successfully you will see the following messages:
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 our NEO's IP address was 192.168.1.123. We typed "192.168.1.123:8080" on a browser, entered and we got the following screenshot:
The mjpg-streamer uses libjpeg to soft-encode camera's input data. You can use ffmpeg to hard-encode data which greatly increases system's efficiency:
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. When you type "q" it will stop recording and the recorded video will be saved as a test.mp4 file.
Check CPU's Working Temperature
Open a terminal on your NanoPi NEO and you can type the following command to read H3's temperature and frequency:
Check System Information with Rpi-Monitor
Our Ubuntu-Core contains the Rpi-Monitor utility with which users can check system information and status.
In our case our NEO's IP was 192.168.1.230 and we typed the following IP in a browser:
Using the GPIO pins/Wiring for NanoPi NEO
Please refer to WiringPi for NanoPi
Make Your Own Ubuntu-Core with Qt-Embedded
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.
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.
If you want to compile your own programs you need to setup a development environment. For more details about this you can refer to section 8 "Setup Cross Compiler for User Space Programs".
(Allwinner's compiler doesn't work very well for some programs)
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
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.
Package System Modules
./gen_script.sh -b nanopi-neo
The gen_script.sh script patches the U-boot 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 file.
Type the following command to update the U-boot on the MicroSD card:
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 section.
./build.sh -p sun8iw7p1 -b nanopi-h3 -m uboot ./gen_script.sh -b nanopi-neo
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:
Note: you need to replace "/dev/sdx" with the device name in your system.
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".
Clean Source Code
./build.sh -p sun8iw7p1_linux -b nanopi-h3 -m clean
Setup Cross Compiler for User Space Programs
Download and extract cross compiler:
git clone https://github.com/friendlyarm/prebuilts.git sudo mkdir -p /opt/FriendlyARM/toolchain sudo tar xf prebuilts/gcc-x64/arm-cortexa9-linux-gnueabihf-4.9.3.tar.xz -C /opt/FriendlyARM/toolchain/
Add the compiler's path to the "PATH" variable by appending the following lines in the ~/.bashrc file:
export PATH=/opt/FriendlyARM/toolchain/4.9.3/bin:$PATH export GCC_COLORS=auto
Run the ~/.bashrc script to make the changes in effect immediately in your working shell. Attention: there is a space after ".":
This is a 64-bit compiler and it cannot run on a 32-bit Linux. You can check whether or not your compiler is setup correctly by running the following commands:
arm-linux-gcc -v Using built-in specs. COLLECT_GCC=arm-linux-gcc COLLECT_LTO_WRAPPER=/opt/FriendlyARM/toolchain/4.9.3/libexec/gcc/arm-cortexa9-linux-gnueabihf/4.9.3/lto-wrapper 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)
Applicable Mainline U-boot & Linux for H3
Now our H3 based boards can run mainline u-boot and Linux. For more details refer to H3 Mainline U-boot & Linux
3D Printing Files
Other OS Support
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.
- 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
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/
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.
Thanks to Ganbold Tsagaankhuu FreeBSD runs on NEO. He has created FreeBSD 12.0-CURRENT image and it can be downloaded from: https://www.mediafire.com/folder/bfbs771c3ajar/FreeBSD
- Dimensional Diagram
- H3 Datesheet Allwinner_H3_Datasheet_V1.2.pdf
Development Guide & Tutorials
Access Hardware in Python
- Programming Python on NanoPi NEO:
The following BakeBit modules can work with BakeBit - NanoHat Hub:
- 3.Green LED
- 5.LED Bar
- 6.Light Sensor
- 8.Red LED
- 9.Rotary Angle Sensor
- 11.Sound Sendor
- 12.Ultrasonic Ranger
Access Hardware in C
- Matrix Modules & Wiki Sites:
- A/D Converter
- 3-Axis Digital Accelerometer
- 3-Axis Digital Compass
- Temperature Sensor
- Temperature & Humidity Sensor
- Sound Sensor
- Ultrasonic Ranger
- Matrix - Compact Kit
- Fire Sensor
- CAM500A Camera
- BAll Rolling Switch
- 2'8 SPI Key TFT 2.8" SPI LCD
- IR Counter
- IR Receiver
- L298N Motor Driver
- MQ-2 Gas Sensor
- MQ-3 Gas Sensor
- Pressure & Temperature Sensor
- RGB LED
- Rotary Encoder
- Soil Moisture Sensor
- USB WiFi
- Water Sensor
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
- Released English Version
- Added Other OS Support
- Added Section 7
- Updated sections 5.3, 5.5 and 9
- Added Section 5.6
- Added Section 5.8
- Added Section 8.1
- Updated Section 8.2
- Added Section 8.3
- Updated Sections 6 and 9
- Added section 8, 9 and 13
- Updated section 12.1
- Added sections 5.2
- Updated sections 5.5 and 13