Difference between revisions of "NanoPi NEO2"
(→July-9-2017) |
(→Hardware Change List) |
||
Line 393: | Line 393: | ||
|Audio Connector ||②NanoPi NEO V1.0 1701's Audio connector is a 2.0mm 5Pin-header<br/> [[File:NanoPi-NEO2-V1.0.jpg |thumb|]] ||②NanoPi NEO V1.1 1711's Audio connector is a 2.54mm 4Pin-header<br/>[[File:NanoPi-NEO2-V1.1.jpg |thumb|]] | |Audio Connector ||②NanoPi NEO V1.0 1701's Audio connector is a 2.0mm 5Pin-header<br/> [[File:NanoPi-NEO2-V1.0.jpg |thumb|]] ||②NanoPi NEO V1.1 1711's Audio connector is a 2.54mm 4Pin-header<br/>[[File:NanoPi-NEO2-V1.1.jpg |thumb|]] | ||
|- | |- | ||
− | |RJ45 Gbps Ethernet ||③ NanoPi NEO V1.0 1701's Ethernet port is an SMT connector ||③ NanoPi NEO V1.1 1711's Ethernet port is a | + | |RJ45 Gbps Ethernet ||③ NanoPi NEO V1.0 1701's Ethernet port is an SMT connector ||③ NanoPi NEO V1.1 1711's Ethernet port is a pin connector. |
|- | |- | ||
|CVBS Output || ||④ NanoPi NEO V1.1 1711 has a CVBS output which V1.0 doesn't have | |CVBS Output || ||④ NanoPi NEO V1.1 1711 has a CVBS output which V1.0 doesn't have |
Revision as of 08:24, 20 March 2018
Contents
- 1 Introduction
- 2 Hardware Spec
- 3 Software Features
- 4 Diagram, Layout and Dimension
- 5 Get Started
- 6 Work with FriendlyCore
- 6.1 Introduction
- 6.2 System Login
- 6.3 Configure System with npi-config
- 6.4 Develop Qt Application
- 6.5 Setup Program to AutoRun
- 6.6 Extend TF Card's Section
- 6.7 WiFi
- 6.8 Ethernet Connection
- 6.9 WiringPi and Python Wrapper
- 6.10 Custom welcome message
- 6.11 Modify timezone
- 6.12 Set Audio Device
- 6.13 Connect to USB Camera(FA-CAM202)
- 6.14 Check CPU's Working Temperature
- 6.15 Test Watchdog
- 6.16 Test Infrared Receiver
- 6.17 Read CHIP ID
- 6.18 Access GPIO Pins/Wirings with WiringNP
- 6.19 Run Qt Demo
- 6.20 How to install and use docker (for arm64 system)
- 6.21 Play & Record Audio
- 7 Make Your Own FriendlyCore
- 8 Connect External Modules to NEO2
- 8.1 DIY NAS Server with 1-bay NAS Dock & NEO2
- 8.2 Connect Python Programmable NanoHat OLED to NEO2
- 8.3 Connect Python Programmable NanoHat Motor to NEO2
- 8.4 Connect NanoHat PCM5102A to NEO2
- 8.5 Connect Arduino Compatible UNO Dock to NEO2
- 8.6 Connect Power Dock to NEO2
- 8.7 Connect NanoHat Proto to NEO2
- 8.8 Connect Matrix - 2'8 SPI Key TFT to NanoPi NEO2
- 9 3D Printing Files
- 10 Resources
- 11 Hardware Change List
- 12 Update Log
1 Introduction
- The NanoPI NEO2 is a newly released super tiny ARM board by FriendlyElec. It uses Allwinner’s 64-bit H5 quad-core SoC (ARM Cortex-A53). It has internal hexa-core Mail450 GPU, 512M DDR3 RAM. A UbuntuCore and Armbian image files are ready for it.
- The NanoPi NEO2 inherits NEO's form factor and has compatible interfaces and ports with NEO. In addition in such a small dimension it has Gbps Ethernet and one USB host port. These features make it especially suitable for applications that require high data throughput , speedy data transmission and high performance. Hobbyists and makers will just love it.
2 Hardware Spec
- CPU: Allwinner H5, Quad-core 64-bit high-performance Cortex A53
- DDR3 RAM: 512MB
- Connectivity: 10/100/1000M Ethernet, RTL8211E-VB-CG chip
- USB Host: USB Type A x 1 and USB pin header x 2
- MicroSD Slot: MicroSD x 1 for system boot and storage
- LED: Power LED x 1, System LED(Blue) x 1
- GPIO1: 2.54mm pitch 24 pin-header, compatible with Raspberry Pi's GPIO pin1 - pin 24. It includes UART, SPI, I2C, IO etc
- GPIO2: 2.54mm pitch 12 pin-header. It includes USB, IR receiver, I2S, IO etc
- Serial Debug Port: 2.54mm pitch 4pin-header
- Audio In/Out: 2.54mm pitch 4 pin-header
- MicroUSB: Power input(5V/2A) and OTG
- PCB Dimension: 40 x 40mm
- Working Temperature: -30℃ to 70℃
- Weight: 13g(WITHOUT Pin-headers)
- OS/Software: u-boot,Ubuntu Core
3 Software Features
3.1 uboot
- mainline uboot released on May 2017
3.2 UbuntuCore 16.04
- 64-bit system
- 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. When enabling PWM it will prompt that Serial debug port will be disabled.
- 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
- supports USB WiFi module: refer to #Connect USB WiFi to NEO
- supports audio recording and playing with 3.5mm audio jack
- supports I2C 0/1
- 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
4 Diagram, Layout and Dimension
4.1 Layout
- GPIO Pin Description
Pin# Name Linux gpio Pin# Name Linux gpio 1 SYS_3.3V 2 VDD_5V 3 I2C0_SDA/GPIOA12 12 4 VDD_5V 5 I2C0_SCL/GPIOA11 11 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 Descripton
NanoPi-NEO2 Pin# Name Description 1 VDD_5V 5V Power Out 2 USB-DP1 USB1 DP Signal 3 USB-DM1 USB1 DM Signal 4 USB-DP2 USB2 DP Signal 5 USB-DM2 USB2 DM Signal 6 GPIOL11/IR-RX GPIOL11 or IR Receive 7 SPDIF-OUT/GPIOA17 GPIOA17 or SPDIF-OUT 8 PCM0_SYNC/I2S0_LRC I2S/PCM Sample Rate Clock/Sync 9 PCM0_CLK/I2S0_BCK I2S/PCM Sample Rate Clock 10 PCM0_DOUT/I2S0_SDOUT I2S/PCM Serial Data Output 11 PCM0_DIN/I2S0_SDIN I2S/PCM Serial Data Input 12 GND 0V
- Audio
Pin# Name Description 1 MP Microphone Positive Input 2 MN Microphone Negative Input 3 LR LINE-OUT Right Channel Output 4 LL 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
- VDD_5V: 5V power input/output. The input range is 4.7V ~ 5.6V. It can take power input from the MicroUSB.
- All pins are 3.3V and output current is 5mA
- For more details refer to the document: NanoPi_NEO2_V1.1_1711-Schematic.pdf
4.2 Dimensional Diagram
- For more details refer to pcb file in dxf format
5 Get Started
5.1 Essentials You Need
Before starting to use your NanoPi NEO2 get the following items ready
- NanoPi NEO2
- 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 NEO2 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 Install OS
5.3.1 Get Image File
Get the following files from download link to download image files (under the officail-ROMs directory) and the flashing utility(under the tools directory):
Image Files: nanopi-neo2_friendlycore-xenial_3.10.y_YYYYMMDD.img.zip FriendlyCore (base on UbuntuCore) Image File, kernel:Linux-3.10 nanopi-neo2_friendlycore-xenial_4.x.y_YYYYMMDD.img.zip FriendlyCore (base on UbuntuCore) Image File, kernel:Linux-4.x nanopi-neo2_debian-nas-jessie_4.x.y_YYYYMMDD.img.zip Image File with Support for NAS Dock, Kernel: Linux-4.x, applicable to 1-bay NAS Dock nanopi-neo2_ubuntu-oled_4.x.y_YYYYMMDD.img.zip Image File with Support for OLED Module, Kernel: Linux-4.x, applicable to NanoHat OLED Flash Utility: win32diskimager.rar Windows utility. Under Linux users can use "dd"
5.3.2 Linux
5.3.2.1 Flash to TF
- FriendlyCore / Debian / Ubuntu / OpenWrt / DietPi are all based on a same Linux distribution and their installation methods are the same.
- Extract the Linux image 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.
Take "nanopi-neo2_sd_friendlycore-xenial_4.14_arm64_YYYYMMDD.img" as an example here is the installation window. Other image files are installed on the similar window:
After it is installed you will see the following window:
- Insert this card into your board's BOOT slot and power on (with a 5V/2A power source). If the PWR LED is on and the STAT LED is blinking this indicates your board has successfully 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
- WiringNP: NanoPi NEO/NEO2/Air GPIO Programming with C
- RPi.GPIO : NanoPi NEO/NEO2/Air GPIO Programming with Python
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. You can refer to <Connect DVP Camera (CAM500B) to Board> on how to connect a USB camera to a board.
You need to change the start.sh script and make sure it uses a correct /dev/videoX node. You can check your FA-CAM202's node by running the following commands:
$ apt-get install v4l-utils $ v4l2-ctl -d /dev/video1 -D Driver Info (not using libv4l2): Driver name : uvcvideo Card type : HC 3358+2100: HC 3358+2100 Bus info : usb-1c1b000.usb-1 ...
Information above indicates that /dev/video1 is the device node of the FA-CAM 202.
6.14 Check CPU's Working Temperature
You can get CPU's working temperature by running the following command:
$ cpu_freq CPU0 online=1 temp=26581 governor=ondemand cur_freq=480000 CPU1 online=1 temp=26581 governor=ondemand cur_freq=480000 CPU2 online=1 temp=26581 governor=ondemand cur_freq=480000 CPU3 online=1 temp=26581 governor=ondemand cur_freq=480000
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 480MHz.
6.15 Test Watchdog
You can test watchdog by running the following commands:
$ cd /root/demo/watchdog/ $ gcc watchdog_demo.c -o watchdog_demo $ ./watchdog_demo /dev/watchdog0 10 Set timeout: 10 seconds Get timeout: 10 seconds System will reboot in 10 second
System will reboot in 10 seconds.
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 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.18 Access GPIO Pins/Wirings with WiringNP
The wiringPi library was initially developed by Gordon Henderson in C. It contains libraries to access GPIO, I2C, SPI, UART, PWM and etc. The wiringPi library contains various libraries, header files and a commandline utility:gpio. The gpio utility can be used to read and write GPIO pins.
FriendlyElec integrated this utility in FriendlyCore system allowing users to easily access GPIO pins. For more details refer to WiringNP WiringNP
6.19 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.20 How to install and use docker (for arm64 system)
6.20.1 How to Install Docker
Run the following commands:
sudo apt-get update sudo apt-get install docker.io
6.20.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.21 Play & Record Audio
The NanoPi NEO2 has an audio interface (2.0mm pitch 5-pin header) whose pin description is as follows:
Pin# Name Description 1 MICIN1P Microphone Positive Input 2 MICIN1N Microphone Negative Input 3 LINEOUTR LINE-OUT Right Channel Output 4 GND Ground 5 LINEOUTL LINE-OUT Left Channel Output
Here is a hardware setup on how to connect an audio device to a NEO2:
Before begin to play or record a audio make sure your NEO2 is connected to an audio device.
Check a recognized audio device:
$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0
Both Allwinner's H5 and H3 have an internal codec which is named as [H3 Audio Codec] in mainline kernels.
Play an audio file:
$ aplay /root/Music/test.wav -D plughw:0
Record an audio file:
$ arecord -f cd -d 5 test.wav
7 Make Your Own FriendlyCore
7.1 Mainline U-boot & Linux(64 bit)
Now the NanoPi NEO2 can run a 64-bit Linux kernel with 64-bit Ubuntu Core 16.04. Here is a detailed reference on how to run mainline U-boot and Linux on H5: Mainline U-boot & Linux
7.2 Use Allwinner's BSP
7.2.1 Preparations
Visit this link download link and enter the "sources/nanopi-H5-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 ./ $ lichee
Or you can get it from our github:
$ git clone https://github.com/friendlyarm/h5_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-4.6.3.tar.xz" and "gcc-linaro-aarch64.tar.xz" and copy them to the "lichee/brandy/toochain/" directory.
"gcc-linaro-arm-4.6.3.tar.xz"is for compiling u-boot and "gcc-linaro-aarch64.tar.xz" is for compiling Linux kernel.
7.2.3 Compile lichee Source Code
Compilation of the H5'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/fa_tools $ ./build.sh -b nanopi-neo2 -p linux -t all
After this compilation succeeds a u-boot, Linux kernel and kernel modules will be generated.
Note: the lichee directory contains cross-compilers we have setup. When the build.sh script runs it will automatically call these cross-compilers.
The following commands can be used to update the u-boot on an installation TF 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.
The boot.img and kernel modules are under the "linux-3.10/output" directory. You can copy the new boot.img file to your TF 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.
You can run the following commands to compile u-boot individually:
$ cd lichee/fa_tools/ $ ./build.sh -b nanopi-neo2 -p linux -t u-boot
7.2.5 Compile Linux Kernel
Note:you need to compile the whole lichee directory before you can compile Linux kernel individually.
You can run the following commands to compile Linux kernel individually:
$ cd lichee/fa_tools/ $ ./build.sh -b nanopi-neo2 -p linux -t kernel
The boot.img and kernel modules are under the "linux-3.10/output" directory. You can copy the new boot.img file to your TF card's boot partition.
7.2.6 Clean Source Code
$ cd lichee/fa_tools/ $ ./build.sh -b nanopi-neo2 -p linux -t clean
8 Connect External Modules to NEO2
8.1 DIY NAS Server with 1-bay NAS Dock & NEO2
The 1-bay NAS Dock is an expansion board which can be used to connect an external hard disk to a NanoPi NEO2.It uses JSM568 USB3.0 to SATA IC and communicates with a NanoPi NEO2 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 v1.2 for NanoPi NEO/NEO2
8.2 Connect Python Programmable NanoHat OLED to NEO2
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
8.3 Connect Python Programmable NanoHat Motor to NEO2
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
8.4 Connect NanoHat PCM5102A to NEO2
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
8.5 Connect Arduino Compatible UNO Dock to NEO2
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 NEO2'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
8.6 Connect Power Dock to NEO2
The Power Dock for NanoPi NEO2 is a high efficiency power conversion module. It provides stable and reliable power source. Here is a hardware setup:Power Dock for NanoPi NEO
8.7 Connect NanoHat Proto to NEO2
The NanoHat Proto is an expansion board which exposes NEO2's various pins.It has an onboard EEPROM for data storage.Here is a hardware setup:NanoHat Proto
8.8 Connect Matrix - 2'8 SPI Key TFT to NanoPi NEO2
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
9 3D Printing Files
- NanoPi_NEO2_V1.0-1701 3D Printing Files
- [xxx NanoPi_NEO2_V1.1-1711 3D Printing Files]
10 Resources
10.1 Datasheet & Schematics
- Schematics
- Dimensional Diagram
- H5 Datesheet Allwinner_H5_Datasheet_V1.0.pdf
11 Hardware Change List
- NanoPi NEO2 Version Compare & List(Hardware)
version NanoPi NEO2 V1.0 NanoPi NEO2 V1.1 Photo TF Card Slot ① Non-Popup TF Card Slot
①Popup TF Card Slot Audio Connector ②NanoPi NEO V1.0 1701's Audio connector is a 2.0mm 5Pin-header
②NanoPi NEO V1.1 1711's Audio connector is a 2.54mm 4Pin-header
RJ45 Gbps Ethernet ③ NanoPi NEO V1.0 1701's Ethernet port is an SMT connector ③ NanoPi NEO V1.1 1711's Ethernet port is a pin connector. CVBS Output ④ NanoPi NEO V1.1 1711 has a CVBS output which V1.0 doesn't have Mounting Hole ⑤ NanoPi NEO V1.1 1711 has two more mounting holes of 1.7 mm in diameter GPIO voltage regulation ⑥ NanoPi NEO V1.1 1711 has 1.1V/1.3V GPIO voltage regulation
12 Update Log
12.1 March-14-2017
- Released English Version
12.2 April-5-2017
- Added sections 5.2 and 5.8
12.3 May-7-2017
- Added sections 7: mainline support for H5
- Added sections 8: support for external modules
12.4 May-17-2017
- Added sections 5.9: WiringNP support for H5
12.5 May-24-2017
- Added section 3: Software Features
12.6 June-4-2017
- Updated section 5.3.1
- Updated section 3: added more OS features
12.7 June-8-2017
- Updated section 3.2: added support for RPi.GPIO_NP
- Added section 6.10: added support for RPi.GPIO_NP
12.8 July-5-2017
- Updated sections 5.3.2, 6.5 and 6.8
- Added section 8.8: connect 2.8"TFT to NEO2
12.9 July-9-2017
- Updated section 7.2
12.10 March-20-2018
- Updated sections 4, 9 and 10
- Added section 11