Difference between revisions of "NanoPi NEO2"

From FriendlyARM WiKi
Jump to: navigation, search
(Run Ubuntu-Core with Qt-Embedded)
(Diagram, Layout and Dimension)
(62 intermediate revisions by 4 users not shown)
Line 5: Line 5:
 
[[File:NanoPi NEO2-2.jpg|thumb|frameless|300px|Front]]
 
[[File:NanoPi NEO2-2.jpg|thumb|frameless|300px|Front]]
 
[[File:NanoPi NEO2-3.jpg|thumb|frameless|300px|Back]]
 
[[File:NanoPi NEO2-3.jpg|thumb|frameless|300px|Back]]
* 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 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.
 
* 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.
  
Line 14: Line 14:
 
* USB Host: USB Type A x 1 and USB pin header x 2
 
* USB Host: USB Type A x 1 and USB pin header x 2
 
* MicroSD Slot: MicroSD x 1 for system boot and storage
 
* MicroSD Slot: MicroSD x 1 for system boot and storage
* LED: Power LED x 1, System LED(Blue) x 1
+
* LED: Power LED x 1, System LED 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
 
* 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
 
* GPIO2: 2.54mm pitch 12 pin-header. It includes USB, IR receiver, I2S, IO etc
 
* Serial Debug Port: 2.54mm pitch 4pin-header
 
* Serial Debug Port: 2.54mm pitch 4pin-header
* Audio In/Out: 2.0mm pitch 5 pin-header
+
* Audio In/Out: 2.54mm pitch 4 pin-header
 
* MicroUSB: Power input(5V/2A) and OTG  
 
* MicroUSB: Power input(5V/2A) and OTG  
 
* PCB Dimension: 40 x 40mm
 
* PCB Dimension: 40 x 40mm
 +
* Working Temperature: -20℃ to 70℃
 
* Weight: 13g(WITHOUT Pin-headers)
 
* Weight: 13g(WITHOUT Pin-headers)
 
* OS/Software: u-boot,Ubuntu Core
 
* OS/Software: u-boot,Ubuntu Core
  
 +
<!--
 
==Software Features==
 
==Software Features==
 
===uboot===
 
===uboot===
Line 33: Line 35:
 
===UbuntuCore 16.04===
 
===UbuntuCore 16.04===
 
* 64-bit system
 
* 64-bit system
* mainline kernel: Linux-4.11.2
+
* mainline kernel: Linux-4.14
 
* rpi-monitor: check system status and information
 
* 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.
 
* 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.
Line 58: Line 60:
  
 
===Ubuntu OLED===
 
===Ubuntu OLED===
* mainline kernel: Linux-4.11.2
+
* mainline kernel: Linux-4.14
 
* supports FriendlyElec's OLED module
 
* supports FriendlyElec's OLED module
  
Line 65: Line 67:
  
 
===Debian for NAS Dock===
 
===Debian for NAS Dock===
* mainline kernel: Linux-4.11.2
+
* mainline kernel: Linux-4.14
 
* supports FriendlyElec's NAS Dock
 
* supports FriendlyElec's NAS Dock
 
* optimized OpenMediaVault configuration options
 
* optimized OpenMediaVault configuration options
 
* allocated swap section
 
* allocated swap section
 +
-->
  
 
==Diagram, Layout and Dimension==
 
==Diagram, Layout and Dimension==
Line 142: Line 145:
 
|Pin# || Name      ||  Description   
 
|Pin# || Name      ||  Description   
 
|-
 
|-
|1    || MICIN1P   ||  Microphone Positive Input  
+
|1    || MP   ||  Microphone Positive Input  
 
|-
 
|-
|2    || MICIN1N   ||  Microphone Negative Input     
+
|2    || MN   ||  Microphone Negative Input     
 
|-  
 
|-  
|3    || LINEOUTR || LINE-OUT Right Channel Output  
+
|3    || LR || LINE-OUT Right Channel Output  
 
|-
 
|-
|4    || GND      || 0V
+
|4    || LL || LINE-OUT Left Channel Output
|-
+
|5    || LINEOUTL || LINE-OUT Left Channel Output
+
 
|}
 
|}
  
Line 170: Line 171:
 
:'''Note'''
 
:'''Note'''
 
::#SYS_3.3V: 3.3V power output
 
::#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.
+
::#VDD_5V: 5V power input/output. The input range is 4.7V ~ 5.5V. It can take power input from the MicroUSB.
 
::#All pins are 3.3V and output current is 5mA
 
::#All pins are 3.3V and output current is 5mA
::#For more details refer to the document: [http://wiki.friendlyarm.com/wiki/images/a/a1/Schematic_NanoPi_NEO2-v1.0_1701.pdf NanoPi_NEO2-1701-Schematic.pdf]
+
::#For more details refer to the document: [http://wiki.friendlyarm.com/wiki/images/d/db/Schematic_NanoPi_NEO2-V1.1-1711.pdf NanoPi_NEO2_V1.1_1711-Schematic.pdf]
  
 
===Dimensional Diagram===
 
===Dimensional Diagram===
 
[[File:NanoPi-NEO2-1701-dimensions.png|frameless|400px|]]
 
[[File:NanoPi-NEO2-1701-dimensions.png|frameless|400px|]]
  
::For more details refer to [http://wiki.friendlyarm.com/wiki/index.php/File:NanoPi_NEO_2_Dimesions(dxf).rar pcb file in dxf format]
+
::For more details refer to [http://wiki.friendlyarm.com/wiki/index.php/File:NanoPi_NEO2_V1.1-1711_PCB-Dimensional.rar pcb file in dxf format]
 +
 
 +
==Software Features==
 +
{{H5SoftwareFeature-FriendlyCore|NanoPi-NEO2}}
  
 
==Get Started==
 
==Get Started==
Line 185: Line 189:
 
* microSD Card/TFCard: Class 10 or Above, minimum 8GB SDHC
 
* microSD Card/TFCard: Class 10 or Above, minimum 8GB SDHC
 
* microUSB power. A 5V/2A power is a must
 
* microUSB power. A 5V/2A power is a must
* A Host computer running Ubuntu 14.04 64 bit system
+
* A Host computer running Ubuntu 16.04 64 bit system
  
 
===TF Cards We Tested===
 
===TF Cards We Tested===
Line 196: Line 200:
 
[[File:SanDisk MicroSD-02.png|frameless|100px|chuanyu MicroSD 8G]]
 
[[File:SanDisk MicroSD-02.png|frameless|100px|chuanyu MicroSD 8G]]
  
===Make an Installation TF Card===
+
===Install OS===
 
====Get Image File====
 
====Get Image File====
Get the following files from [https://www.mediafire.com/folder/ah4i6w029912b/NanoPi-NEO2 download link] to download image files (under the officail-ROMs directory) and the flashing utility(under the tools directory):<br />
+
Get the following files from [http://download.friendlyarm.com/nanopineo2 download link] to download image files (under the officail-ROMs directory) and the flashing utility(under the tools directory):<br />
<!---
+
 
::{| class="wikitable"
 
::{| class="wikitable"
 
|-
 
|-
 
|colspan=2|Image Files:
 
|colspan=2|Image Files:
 
|-
 
|-
|nanopi-neo2-ubuntu-core-qte-sd4g.img.zip      || Ubuntu-Core with Qt-Embedded Image File                 
+
|nanopi-neo2_sd_friendlycore-xenial_3.10_arm64_YYYYMMDD.img.zip || FriendlyCore (base on UbuntuCore) Image File, kernel:Linux-3.10                   
|-
+
|colspan=2|Flash Utility: 
+
|-
+
|win32diskimager.rar || Windows utility. Under Linux users can use "dd"
+
|-
+
|}
+
--->
+
::{| class="wikitable"
+
|-
+
|colspan=2|Image Files:
+
|-
+
|nanopi-neo2_ubuntu-core-xenial_3.10.y_YYYYMMDD.img.zip || Ubuntu-Core with Qt-Embedded Image File, kernel:Linux-3.10                   
+
|-
+
|nanopi-neo2_ubuntu-core-xenial_4.x.y_YYYYMMDD.img.zip || Ubuntu-Core with Qt-Embedded 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 v1.2 for NanoPi NEO/NEO2|1-bay NAS Dock]]                    
+
|nanopi-neo2_sd_friendlycore-xenial_4.14_arm64_YYYYMMDD.img.zip || FriendlyCore (base on UbuntuCore) Image File, kernel:Linux-4.14                    
 
|-
 
|-
|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|NanoHat OLED]]
+
|nanopi-neo2_sd_openwrt_4.14_arm64_YYYYMMDD.img.zip  || OpenWrt, kernel:Linux-4.14
 
|-
 
|-
 
|colspan=2|Flash Utility:   
 
|colspan=2|Flash Utility:   
Line 230: Line 219:
 
|}
 
|}
  
====Make Ubuntu-Core with Qt-Embedded Image Card====
+
{{BurnOS-Allwinner|NanoPi-NEO2}}
* Extract the UbuntuCore file. 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 this writing process is done insert this card into your NanoPi NEO2's TF card slot and power on (with a 5V/2A power source). If the blue LED is blinking this indicates your NanoPi NEO2 has successfully booted.<br />
+
Note:you can make both a Debian and a Ubuntu image card in this way.
+
  
==Work with Ubuntu-Core with Qt-Embedded==
+
{{FriendlyCoreGeneral|NanoPi-NEO2}}
===Run Ubuntu-Core with Qt-Embedded===
+
{{FriendlyCoreAllwinnerH5|NanoPi-NEO2}}
* 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 NEO2 to a PC via the PSU-ONECOM and you can power on your NEO2 from either the PSU-ONECOM or the board's MicroUSB:
+
[[File:PSU-ONECOM-NEO2.jpg|frameless|400px|PSU-ONECOM-NEO2]]<br>
+
Or you can use a USB to Serial module to do it. Here is a hardware setup:<br>
+
[[File:USB2UART-NEO2.jpg|frameless|400px|USB2UART-NEO2]]
+
* Ubuntu-Core's 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:
+
<syntaxhighlight lang="bash">
+
$ sudo apt-get update
+
</syntaxhighlight>
+
 
+
===Extend TF Card's rootfs Section===
+
When you boot Debian/UbuntuCore for the first time with your image card your OS will automatically resize the file system and this process takes a relatively long time.After your OS is fully loaded you can check the file system's size by using the following command:
+
<syntaxhighlight lang="bash">
+
df -h
+
</syntaxhighlight>
+
 
+
===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.
+
<syntaxhighlight lang="bash">
+
sudo npi-config
+
</syntaxhighlight>
+
Here is how npi-config's GUI looks like:<br />
+
[[File:npi-config.jpg|frameless|500px|npi-config]]<br />
+
 
+
===Ethernet Connection===
+
If a NanoPi NEO2 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.In this case you can try obtaining an IP by using the following command:
+
<syntaxhighlight lang="bash">
+
dhclient eth0
+
</syntaxhighlight>
+
 
+
===Login via SSH===
+
The NanoPi NEO2 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 NEO2:
+
<syntaxhighlight lang="bash">
+
ssh root@192.168.1.230
+
</syntaxhighlight>
+
The password is fa
+
 
+
===Connect USB WiFi to NEO2===
+
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;
+
::{| class="wikitable"
+
|-
+
|Number || Model     
+
|-
+
|1  ||  RTL8188CUS 802.11n WLAN Adapter   
+
|-
+
|2  ||  RT2070 Wireless Adapter   
+
|-
+
|3  ||  RT2870/RT3070 Wireless Adapter
+
|-
+
|4  ||  RTL8192CU Wireless Adapter
+
|-
+
|5  ||  NetGear, Inc. WG111v3 54 Mbps Wireless [realtek RTL8187B]
+
|}
+
If you NanoPi NEO2 is connected to a USB WiFi and is powered up you can log into NEO2 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:
+
<syntaxhighlight lang="bash">
+
sudo ifconfig -a
+
</syntaxhighlight>
+
 
+
Open this file "/etc/wpa_supplicant/wpa_supplicant.conf": <br />
+
<syntaxhighlight lang="bash">
+
sudo vi /etc/wpa_supplicant/wpa_supplicant.conf
+
</syntaxhighlight>
+
 
+
Open the /etc/wpa_supplicant/wpa_supplicant.conf file and append the following lines:
+
<syntaxhighlight lang="bash">
+
network={
+
        ssid="YourWiFiESSID"
+
        psk="YourWiFiPassword"
+
}
+
</syntaxhighlight>
+
The "YourWiFiESSID" and "YourWiFiPassword" need to be replaced with your actual ESSID and password.<br/>
+
Save, exit and run the following commands to connect to your WiFi router:
+
<syntaxhighlight lang="bash">
+
$ sudo ifdown wlan0
+
$ sudo ifup wlan0
+
</syntaxhighlight>
+
If your WiFi password has special characters or you don't want your password saved as plain text you can use "wpa_passphrase" to generate a psk for your WiFi password. Here is how you can do it:
+
<syntaxhighlight lang="bash">
+
$ sudo wpa_passphrase YourWiFiESSID
+
</syntaxhighlight>
+
Following the prompt type in your password and you will get a new password in the /etc/wpa_supplicant/wpa_supplicant.conf file. Now you can replace the existing password in the wlan0 file with the new one.
+
 
+
===Connect NanoPi NEO2 to USB Camera(FA-CAM202)===
+
[[File:USB-Camera-NanoPi-NEO2.png|frameless|500px|USB camera]]<br/>
+
The FA-CAM202 is a 2M-pixel USB camera module.
+
Boot your NEO2, connect NEO2 to the internet, log in the system as root, compile and run the mjpg-streamer utility:
+
<syntaxhighlight lang="bash">
+
cd /root/mjpg-streamer
+
apt-get install libjpeg62-dev
+
make
+
./start.sh
+
</syntaxhighlight>
+
The mjpg-streamer is an open source media server. After it is started successfully you will see the following messages:
+
<syntaxhighlight lang="bash">
+
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
+
</syntaxhighlight>
+
 
+
In our case our NEO2'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:<br>
+
[[File:mjpg-streamer-cam500a.png|frameless|400px|mjpg-streamer-cam500a]] <br>
+
<!---
+
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:
+
<syntaxhighlight lang="bash">
+
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
+
</syntaxhighlight>
+
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.
+
--->
+
  
 
===Play & Record Audio===
 
===Play & Record Audio===
Line 374: Line 236:
 
|3    || LINEOUTR  || LINE-OUT Right Channel Output  
 
|3    || LINEOUTR  || LINE-OUT Right Channel Output  
 
|-
 
|-
|4    || GND      ||
+
|4    || GND      || Ground
 
|-
 
|-
 
|5    || LINEOUTL  || LINE-OUT Left Channel Output
 
|5    || LINEOUTL  || LINE-OUT Left Channel Output
 
|}
 
|}
 
Here is a hardware setup on how to connect an audio device to a NEO2:<br>
 
Here is a hardware setup on how to connect an audio device to a NEO2:<br>
[[File:耳麦标注.jpg|frameless|400px|耳麦标注]]<br>
+
[[File:耳麦标注.jpg|frameless|400px| Earphone]]<br>
 
Before begin to play or record a audio make sure your NEO2 is connected to an audio device.<br>
 
Before begin to play or record a audio make sure your NEO2 is connected to an audio device.<br>
 
Check a recognized audio device:
 
Check a recognized audio device:
Line 385: Line 247:
 
$ aplay -l
 
$ aplay -l
 
**** List of PLAYBACK Hardware Devices ****
 
**** List of PLAYBACK Hardware Devices ****
card 0: audiocodec [audiocodec], device 0: SUNXI-CODEC sun50iw2codec-0 []
+
card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 []
 
   Subdevices: 1/1
 
   Subdevices: 1/1
 
   Subdevice #0: subdevice #0
 
   Subdevice #0: subdevice #0
 
</syntaxhighlight>
 
</syntaxhighlight>
 +
Both Allwinner's H5 and H3 have an internal codec which is named as [H3 Audio Codec] in mainline kernels.<br>
  
 
Play an audio file:
 
Play an audio file:
Line 400: Line 263:
 
</syntaxhighlight>
 
</syntaxhighlight>
  
<!--
+
{{OpenWrt1|NanoPi-NEO2}}
===Check CPU's Working Temperature===
+
Open a terminal on your NanoPi NEO2 and you can type the following command to read H5's temperature and frequency:
+
<syntaxhighlight lang="bash">
+
cpu_freq
+
</syntaxhighlight>
+
===通过Rpi-Monitor查看系统状态===
+
Ubuntu-Core系统里已经集成了Rpi-Monitor,该服务允许用户在通过浏览器查看开发板系统状态。<br>
+
假设NEO2的IP地址为192.168.1.230,在PC的浏览器中输入下述地址:
+
<syntaxhighlight lang="bash">
+
192.168.1.230:8888
+
</syntaxhighlight>
+
可以进入如下页面:<br>
+
[[File:rpi-monitor.png|frameless|500px|rpi-monitor]] <br>
+
用户可以非常方便地查看到系统负载、CPU的频率和温度、可用内存、SD卡容量等信息。
+
-->
+
===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.<br>
+
FriendlyElec integrated this utility in NEO2's system allowing users to easily access GPIO pins. For more details refer to  [http://wiki.friendlyarm.com/wiki/index.php/WiringNP:_WiringPi_for_NanoPi_NEO/NEO2]
+
  
===Access GPIO Pins/Wirings with RPi.GPIO_NP===
+
==Make Your Own FriendlyCore==
RPi.GPIO is a famous library in python for Raspberry Pi. FriendlyElec ported it to the NanoPi NEO/NEO2's UbuntuCore images and renamed it as RPi.GPIO_NP.<br/>
+
For more details refer to [http://wiki.friendlyarm.com/wiki/index.php/RPi.GPIO_NP:_RPi.GPIO_for_NanoPi_NEO/NEO2]
+
 
+
==Make Your Own Ubuntu-Core with Qt-Embedded==
+
 
===Mainline U-boot & Linux(64 bit)===
 
===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/zh|Mainline U-boot & Linux]] <br>
 
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/zh|Mainline U-boot & Linux]] <br>
Line 431: Line 271:
 
===Use Allwinner's BSP===
 
===Use Allwinner's BSP===
 
====Preparations====
 
====Preparations====
Visit this link [https://www.mediafire.com/folder/ah4i6w029912b/NanoPi-NEO2 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:
+
Visit this link [http://download.friendlyarm.com/nanopineo2 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:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
ls ./
+
$ ls ./
lichee
+
$ lichee
 
</syntaxhighlight>
 
</syntaxhighlight>
  
 
Or you can get it from our github:
 
Or you can get it from our github:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
git clone https://github.com/friendlyarm/h5_lichee.git lichee
+
$ git clone https://github.com/friendlyarm/h5_lichee.git lichee --depth 1
 
</syntaxhighlight>
 
</syntaxhighlight>
 
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.
 
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====
 
====Install Cross Compiler====
Visit this site [https://www.mediafire.com/folder/ah4i6w029912b/NanoPi-NEO2 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.<br>  
+
Visit this site [http://download.friendlyarm.com/nanopineo2 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.<br>  
 
"gcc-linaro-arm-4.6.3.tar.xz"is for compiling u-boot and "gcc-linaro-aarch64.tar.xz" is for compiling Linux kernel.
 
"gcc-linaro-arm-4.6.3.tar.xz"is for compiling u-boot and "gcc-linaro-aarch64.tar.xz" is for compiling Linux kernel.
  
Line 450: Line 290:
 
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:
 
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:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
sudo apt-get install gawk git gnupg flex bison gperf build-essential \
+
$ sudo apt-get install gawk git gnupg flex bison gperf build-essential \
 
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
 
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
 
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
 
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
Line 459: Line 299:
 
Enter the lichee directory and run the following command to compile the whole package:
 
Enter the lichee directory and run the following command to compile the whole package:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
cd lichee/fa_tools
+
$ cd lichee/fa_tools
./build.sh -b nanopi-neo2 -p linux -t all
+
$ ./build.sh -b nanopi-neo2 -p linux -t all
 
</syntaxhighlight>
 
</syntaxhighlight>
 
After this compilation succeeds a u-boot, Linux kernel and kernel modules will be generated.<br>
 
After this compilation succeeds a u-boot, Linux kernel and kernel modules will be generated.<br>
Line 467: Line 307:
 
The following commands can be used to update the u-boot on an installation TF card:
 
The following commands can be used to update the u-boot on an installation TF card:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
cd lichee/fa_tools/
+
$ cd lichee/fa_tools/
./fuse.sh -d /dev/sdx -p linux -t u-boot
+
$ ./fuse.sh -d /dev/sdx -p linux -t u-boot
 
</syntaxhighlight>
 
</syntaxhighlight>
 
Note: you need to replace "/dev/sdx" with the device name in your system.<br>
 
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.10/output" directory. You can copy the new boot.img file to your TF card's boot section.
+
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.
  
 
====Compile U-boot====
 
====Compile U-boot====
 +
Note:you need to compile the whole lichee directory before you can compile U-boot individually.<br>
 
You can run the following commands to compile u-boot individually:
 
You can run the following commands to compile u-boot individually:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
cd lichee/fa_tools/
+
$ cd lichee/fa_tools/
./build.sh -b nanopi-neo2 -p linux -t u-boot
+
$ ./build.sh -b nanopi-neo2 -p linux -t u-boot
 
</syntaxhighlight>
 
</syntaxhighlight>
  
 
====Compile Linux Kernel====
 
====Compile Linux Kernel====
 +
Note:you need to compile the whole lichee directory before you can compile Linux kernel individually.<br>
 
You can run the following commands to compile Linux kernel individually:
 
You can run the following commands to compile Linux kernel individually:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
cd lichee/fa_tools/
+
$ cd lichee/fa_tools/
./build.sh -b nanopi-neo2 -p linux -t kernel
+
$ ./build.sh -b nanopi-neo2 -p linux -t kernel
 
</syntaxhighlight>
 
</syntaxhighlight>
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 section.
+
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.
  
 
====Clean Source Code====
 
====Clean Source Code====
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
cd lichee/fa_tools/
+
$ cd lichee/fa_tools/
./build.sh -b nanopi-neo2 -p linux -t clean
+
$ ./build.sh -b nanopi-neo2 -p linux -t clean
 
</syntaxhighlight>
 
</syntaxhighlight>
  
 
==Connect External Modules to NEO2==
 
==Connect External Modules to NEO2==
 
===DIY NAS Server with 1-bay NAS Dock & NEO2===
 
===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]]<br />
+
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.14 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]]<br />
 
[[File:step4.png | frameless|300px| Step 4]]
 
[[File:step4.png | frameless|300px| Step 4]]
  
Line 522: Line 364:
 
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]]<br />
 
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]]<br />
 
[[File:Matrix - NanoHat Proto_nanopi_NEO.jpg|frameless|300px|Matrix - NanoHat Proto_nanopi_NEO]]
 
[[File:Matrix - NanoHat Proto_nanopi_NEO.jpg|frameless|300px|Matrix - NanoHat Proto_nanopi_NEO]]
 +
 +
===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]]<br />
 +
[[File:Matrix-2'8_SPI_Key_TFT-1706.jpg|frameless|300px|File:Matrix-2'8_SPI_Key_TFT-1706]]
  
 
==3D Printing Files==
 
==3D Printing Files==
[[File:NanoPi NEO2-3D.jpg|thumb|frameless|300px]]
+
[[File:NanoPi NEO2-3D.jpg|thumb|NanoPi_NEO2_V1.0-1701 3D Printed Housing|300px]]
[http://www.thingiverse.com/thing:2180624 downloadfile]
+
*[http://www.thingiverse.com/thing:2180624 NanoPi_NEO2_V1.0-1701 3D Printing Files]
 +
*[xxx NanoPi_NEO2_V1.1-1711 3D Printing Files]
  
 
==Resources==
 
==Resources==
Line 531: Line 378:
 
* Schematics
 
* Schematics
 
** [http://wiki.friendlyarm.com/wiki/images/a/a1/Schematic_NanoPi_NEO2-v1.0_1701.pdf NanoPi-NEO2-1701-Schematic.pdf]
 
** [http://wiki.friendlyarm.com/wiki/images/a/a1/Schematic_NanoPi_NEO2-v1.0_1701.pdf NanoPi-NEO2-1701-Schematic.pdf]
 +
** [http://wiki.friendlyarm.com/wiki/images/d/db/Schematic_NanoPi_NEO2-V1.1-1711.pdf NanoPi-NEO2-V1.1-1711-Schematic.pdf]
 
* Dimensional Diagram
 
* Dimensional Diagram
 
** [http://wiki.friendlyarm.com/wiki/index.php/File:NanoPi_NEO_2_Dimesions(dxf).rar NanoPi-NEO2-1701 pcb in dxf format]
 
** [http://wiki.friendlyarm.com/wiki/index.php/File:NanoPi_NEO_2_Dimesions(dxf).rar NanoPi-NEO2-1701 pcb in dxf format]
* H5 Datesheet [http://wiki.friendlyarm.com/wiki/images/d/de/Allwinner_H5_Datasheet_V1.0.pdf Allwinner_H5_Datasheet_V1.0.pdf]
+
** [http://wiki.friendlyarm.com/wiki/index.php/File:NanoPi_NEO2_V1.1-1711_PCB-Dimensional.rar NanoPi_NEO2_V1.1-1711 pcb file in dxf format]
 +
** [http://wiki.friendlyarm.com/wiki/images/3/35/NEO_Heat_sink_dimension.pdf NanoPi-NEO2 Heat sink file in pdf format]
 +
* H5 Datesheet  
 +
** [http://wiki.friendlyarm.com/wiki/images/d/de/Allwinner_H5_Datasheet_V1.0.pdf Allwinner_H5_Datasheet_V1.0.pdf]
 +
 
 +
===Internet resources===
 +
* unofficial ROM
 +
** [http://www.dietpi.com/ DietPi]
 +
** [https://www.armbian.com/download/?tx_maker=friendlyelec armbian]
 +
 
 +
* article
 +
** [https://linux-sunxi.org/FriendlyARM_NanoPi_NEO2]
 +
** [https://www.cnx-software.com/2017/03/14/nanopi-neo2-development-bord-powered-by-allwinner-h5-64-bit-arm-processor-sells-for-15/]
 +
** [https://www.cnx-software.com/2017/03/26/nanopi-neo-2-board-nanohats-and-bakebit-starter-kit-review-part-1-hardware-overview-assembly/]
 +
** [https://www.cnx-software.com/2017/04/02/nanopi-neo-2-board-benchmarks-with-ubuntu-16-04-2-using-linux-3-10-and-linux-4-10/]
 +
** [https://tech.scargill.net/nanopi-neo-2/]
 +
** [https://tech.scargill.net/diy-nas/]
 +
{{H5ChangeLog}}
 +
 
 +
==Hardware Change List==
 +
* '''NanoPi NEO2 Version Compare & List(Hardware)'''
 +
::{| class="wikitable"
 +
|-
 +
|version || NanoPi NEO2 V1.0 || NanoPi NEO2 V1.1
 +
|-
 +
|Photo    || [[File:NanoPi-NEO2-V1.0-1701-update.jpg |thumb|]] || [[File:NanoPi-NEO2-V1.1-1711.jpg |thumb|]]
 +
|-
 +
|TF Card Slot  || ① Non-Popup TF Card Slot<br> || ①Popup TF Card Slot 
 +
|-
 +
|Audio Connector  ||②NanoPi NEO V1.0 1701's Audio connector is a 2.0mm 5Pin-header<br/> [[File:NanoPi-NEO-V1.1A.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 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
 +
|}
 +
 
 +
{{H5ChangeLog}}
  
 
==Update Log==
 
==Update Log==
Line 559: Line 447:
 
* Updated section 3.2: added support for RPi.GPIO_NP
 
* Updated section 3.2: added support for RPi.GPIO_NP
 
* Added section 6.10:  added support for RPi.GPIO_NP
 
* Added section 6.10:  added support for RPi.GPIO_NP
 +
 +
===July-5-2017===
 +
* Updated sections 5.3.2, 6.5 and 6.8
 +
* Added section 8.8:  connect 2.8"TFT to NEO2
 +
 +
===July-9-2017===
 +
* Updated section 7.2
 +
 +
===March-20-2018===
 +
* Updated sections 4, 9 and 10
 +
* Added section 11

Revision as of 08:25, 31 July 2019

查看中文

Contents

1 Introduction

Overview
Front
Back
  • 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 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: -20℃ to 70℃
  • Weight: 13g(WITHOUT Pin-headers)
  • OS/Software: u-boot,Ubuntu Core


2.1 UbuntuCore 16.04

  • 64-bit system
  • mainline kernel: Linux-4.14
  • 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

2.2 Ubuntu OLED

  • mainline kernel: Linux-4.14
  • supports FriendlyElec's OLED module

2.3 Debian

  • welcome window with basic system information and status

2.4 Debian for NAS Dock

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

-->

3 Diagram, Layout and Dimension

3.1 Layout

NanoPi NEO2 Layout
pinout
  • 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)
DBG_UART
Pin# Name
1 GND
2 VDD_5V
3 UART_TXD0
4 UART_RXD0
Note
  1. SYS_3.3V: 3.3V power output
  2. VDD_5V: 5V power input/output. The input range is 4.7V ~ 5.5V. It can take power input from the MicroUSB.
  3. All pins are 3.3V and output current is 5mA
  4. For more details refer to the document: NanoPi_NEO2_V1.1_1711-Schematic.pdf

3.2 Dimensional Diagram

NanoPi-NEO2-1701-dimensions.png

For more details refer to pcb file in dxf format

4 Software Features

FriendlyCore System
Cross-Compiler
  • gcc-linaro-6.3.1-2017.02-x86_64_aarch64-linux-gnu
  • it applies to 64-bit Armv8 Cortex-A, little-endian architechture. FriendlyElec uses it for its H5 based boards.
U-boot-2017.11
  • It can recognize a FriendlyElec's H5 based board and load its dtb file accordingly.
  • It optimizes memory settings.
  • It supports voltage regulation IC sy8106a and applies only to NanoPi K1 Plus/NanoPi NEO Core2.
  • It supports MAC generation from H5's CPU ID.
  • It supports system booting from either SD card or eMMC and can automatically load the kernel from the booting device.
Linux-4.14
  • It supports LED. You can access it via "/sys/class/leds".
  • It supports GPIO. You can access it via "/sys/class/gpio/".
  • It supports UART0/1/2/3. You can access it via "/dev/ttySX".
  • It supports I2C0. You can access it via "/dev/i2c-X".
  • It supports SPI0. You can access it via "/dev/spidevX.X".
  • It supports PWM0. You can access it via "/sys/class/pwm/". The UART0 pin is multiplexed.
  • It supports I2S0. It works together with PCM5102A codec. The I2C1 pin is multiplexed.
  • It supports Watchdog. You can access it via "/dev/watchX".
  • It can read a CPU ID. You can access it via "/sys/bus/nvmem/devices/sunxi-sid0/nvmem".
  • It supports IR Receiver. You need to connect an IR receiver to the board.
  • It supports dynamic CPU voltage regulation.
  • It supports Micro USB OTG.
  • It supports USB Host1/2/3.
  • It supports TF Card.
  • It supports 1000M Ethernet.
  • It supports H5's internal Codec and supports voice playing and recording.
  • It supports USB Camera(CAM202).
  • It supports popular USB WiFi Adapters.
  • It supports popular USB Ethernet Adapters.
  • It supports popular USB Serial Converters.
  • It supports popular USB Sound Cards.
  • It supports FriendlyElec's NanoHat PCM5102A.
File System
  • Based on UbuntuCore-16.04, it has original UbuntuCore features.
  • It has popular utilties:VIM/Nano/SSHserver and etc.
  • It has Qt-Embedded-4.8 and suitable for rapid product prototyping which needs a GUI.
  • It has a network management utility "NetworkManager" which can automatically detect and connect to a network. For more details refer to: NetworkManager
  • It has a commandline utility "npi-config" which can be used to set a user password, language, timezone, Hostname, SSH enable/disable, auto-login, hardware interface and etc. For more details refer to Npi-config
  • It expands the file system on the first system boot.
  • It supports file system auto-repair on system boot.
  • It supports 512MB's swap.
  • It supports WiringNP which functions like Arduino's API and can be used to access NanoPi boards' gpio/i2c/spi and etc. For more details refer to: WiringNP
  • It supports FriendlyElec's BakeBit which is a set of sensor modules including hardware components(such as NanoHat Hub extension board) and software (such as BakeBit). For more details refer to BakeBit .
  • It supports RPi.GPIO which can be used to access NanoPi boards' gpio with Python. For more details refer to RPi.GPIO.

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 MicroSD 8G

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

SanDisk MicroSD 128G

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

chuanyu MicroSD 8G

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_sd_friendlycore-xenial_3.10_arm64_YYYYMMDD.img.zip FriendlyCore (base on UbuntuCore) Image File, kernel:Linux-3.10
nanopi-neo2_sd_friendlycore-xenial_4.14_arm64_YYYYMMDD.img.zip FriendlyCore (base on UbuntuCore) Image File, kernel:Linux-4.14
nanopi-neo2_sd_openwrt_4.14_arm64_YYYYMMDD.img.zip OpenWrt, kernel:Linux-4.14
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:
win32disk-h5

After it is installed you will see the following window:
win32disk-finish

  • 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 our FriendlyCore has the following additional features:

  • it supports our LCDs with both capacitive touch and resistive touch(S700, X710, HD702, S430, HD101 and S70)
  • it supports WiFi
  • it supports Ethernet
  • it supports Bluetooth and has been installed with bluez utilities
  • it supports audio playing
  • it supports Qt 5.10.0 EGLES and OpenGL ES1.1/2.0 (Only for S5P4418/S5P6818)

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: PSU-ONECOM-NEO2.jpg
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:
USB2UART-NEO2.jpg

  • 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:
npi-config

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

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 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.12 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.13 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.14 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.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 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.17 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.18 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:
K2-QtE

6.19 How to install and use docker (for arm64 system)

6.19.1 How to Install Docker

Run the following commands:

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

6.19.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.20 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:
Earphone
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 Work with OpenWrt

7.1 Introduction

OpenWrt is a highly extensible GNU/Linux distribution for embedded devices.Unlike many other distributions for routers, OpenWrt is built from the ground up to be a full-featured, easily modifiable operating system for embedded devices. In practice, this means that you can have all the features you need with none of the bloat, powered by a modern Linux kernel. For more details you can refer to:OpenWrt Website.

7.2 System Login

  • Login via Serial Port

When you do kernel development you'd better get a serial communication board. After you connect your board to a serial communication board you will be able to do development work from a commandline utility.
Here is a hardware setup:
After you connect your board to a serial communication board (e.g. FriendlyElec's serial communication board) you can power the whole system from either the DC port on the serial communication board or the MicroUSB port(if there is one) on your board:
PSU-ONECOM-NEO2.jpg

or you can use a USB to serial board and power on the whole system at the MicroUSB port with a 5V/2A power:
USB2UART-NEO2.jpg

By default you will login as root without a password. You can use "passwd" to set a password for root.
op_login
On first boot the system will automatically extend the file system on the TF card to the max capacity:
resize_rootfs_userdata
Please wait for this to be done.

  • Login via SSH

In FriendlyElec's OpenWrt system the Ethernet(eth0) is configured as WAN.
Before power on your board make sure your board is connected to a master router's LAN with an Ethernet cable and the eth0 will be assigned an IP address by DHCP.
For example, if your eth0 is assigned an IP address 192.168.1.163 you can login with SSH by running the following command:

$ ssh root@192.168.1.163

You can login without a password.

  • Login via Web

You can login OpenWrt via a LuCI Web page.
After you go through all the steps in <Login via SSH> and get an IP address e.g. 192.168.1.163 for the Ethernet connection, type this IP address in a browser's address bar and you will be able to login OpenWrt-LuCI:
R1-OpenWrt-LuCI
By default you will login as root without a password, just click on "Login" to login.

7.3 Manage Software Packages

OpenWrt has a package management utility: opkg. You can get its details by running the following command:

$ opkg
Package Manipulation:
        update                  Update list of available packages
        upgrade <pkgs>          Upgrade packages
        install <pkgs>          Install package(s)
        configure <pkgs>        Configure unpacked package(s)
        remove <pkgs|regexp>    Remove package(s)
        flag <flag> <pkgs>      Flag package(s)
         <flag>=hold|noprune|user|ok|installed|unpacked (one per invocation)
 
Informational Commands:
        list                    List available packages
        list-installed          List installed packages
        list-upgradable         List installed and upgradable packages
        list-changed-conffiles  List user modified configuration files
        files <pkg>             List files belonging to <pkg>
        search <file|regexp>    List package providing <file>
        find <regexp>           List packages whose name or description matches <regexp>
        info [pkg|regexp]       Display all info for <pkg>
        status [pkg|regexp]     Display all status for <pkg>
        download <pkg>          Download <pkg> to current directory
...

These are just part of the manual. Here are some popular opkg commands.

  • Update Package List

Before you install a package you'd better update the package list:

$ opkg update
  • Check Available Packages
$ opkg list

At the time of writing there are 3241 packages available.

  • Check Installed Packages:
$ opkg list-installed

At the time of writing 124 packages have been installed.

  • Install/Delete Packages:
$ opkg install <pkgs>
$ opkg remove <pkgs>
  • Check Files Contained in Installed Packages:
$ opkg files <pkg>
  • Install Chinese Language Package for LuCI
$ opkg install luci-i18n-base-zh-cn
  • Check Changed Files:
$ opkg list-changed-conffiles

7.4 Check System Status

  • Check CPU Temperature & Frequency via Commandline
$ 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

These messages mean that there are four CPU cores working online simultaneously. Each core's temperature is 26.5 degrees in Celsius, the scheduling policy is on-demand and the working frequency is 624MHz. You can set the frequency by running the following command:

$ 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

These messages mean four CPU cores are working online. Each core's temperature is 26.5 degrees. Each core's governor is on demand and the frequency is 480 MHz.

  • Check System Status on OpenWrt-LuCI Web Page

After open the OpenWrt-LuCI page, go to "Statistics ---> Graphs" and you will see various system statistics e.g.:
1) System Load:
statistics_system_load
2) RAM:
statistics_memory
3) CPU Temperature:
statistics_thermal
All the statistics listed on the Statistics page are presented by the luci-app-statistics package which uses the Collectd utility to collect data and presents them with the RRDtool utility.
If you want to get more statistics you can install other collectd-mod-* packages. All collectd-mod-* packages use the same configuration file: /etc/config/luci_statistics.

7.5 Check Network->Interfaces Configurations

  • After open the OpenWrt-LuCI page, go to "Network" ---> "Interfaces" and you will see the current network's configurations:

op_interface_eth0

  • All the configurations listed on the Network->Interfaces page are stored in the "/etc/config/network" file.




8 Make Your Own FriendlyCore

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

8.2 Use Allwinner's BSP

8.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 --depth 1

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.

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

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

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

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

8.2.6 Clean Source Code

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

9 Connect External Modules to NEO2

9.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.14 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
Step 4

9.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
NanoHat OLED_nanopi_NEO

9.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
NanoHat Motor_nanopi_NEO

9.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
Matrix - NanoHat PCM5102A_nanopi_NEO

9.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
Matrix-UNO_Dock_NEO

9.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
Power Dock for NanoPi NEO_nanopi_NEO

9.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
Matrix - NanoHat Proto_nanopi_NEO

9.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
File:Matrix-2'8_SPI_Key_TFT-1706

10 3D Printing Files

NanoPi_NEO2_V1.0-1701 3D Printed Housing

11 Resources

11.1 Datasheet & Schematics

11.2 Internet resources


12 Hardware Change List

  • NanoPi NEO2 Version Compare & List(Hardware)
version NanoPi NEO2 V1.0 NanoPi NEO2 V1.1
Photo
NanoPi-NEO2-V1.0-1701-update.jpg
NanoPi-NEO2-V1.1-1711.jpg
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.1A.jpg
②NanoPi NEO V1.1 1711's Audio connector is a 2.54mm 4Pin-header
NanoPi-NEO2-V1.1.jpg
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


13 Update Log

13.1 March-14-2017

  • Released English Version

13.2 April-5-2017

  • Added sections 5.2 and 5.8

13.3 May-7-2017

  • Added sections 7: mainline support for H5
  • Added sections 8: support for external modules

13.4 May-17-2017

  • Added sections 5.9: WiringNP support for H5

13.5 May-24-2017

  • Added section 3: Software Features

13.6 June-4-2017

  • Updated section 5.3.1
  • Updated section 3: added more OS features

13.7 June-8-2017

  • Updated section 3.2: added support for RPi.GPIO_NP
  • Added section 6.10: added support for RPi.GPIO_NP

13.8 July-5-2017

  • Updated sections 5.3.2, 6.5 and 6.8
  • Added section 8.8: connect 2.8"TFT to NEO2

13.9 July-9-2017

  • Updated section 7.2

13.10 March-20-2018

  • Updated sections 4, 9 and 10
  • Added section 11