Difference between revisions of "NanoPi NEO2 Black"

Revision as of 08:19, 22 October 2019

查看中文

1 Introduction

Overview

Front

Back

• The NanoPi NEO2 Black is another fun board developed by FriendlyELEC for makers, hobbyists and fans.

2 Hardware Spec

• CPU: Allwinner H5, Quad-core 64-bit high-performance Cortex A53
• DDR3 RAM: 512MB/1GB
• Flash: no onboard Flash, but one eMMC flash module socket
• Connectivity: 10/100/1000M Ethernet, RTL8211E-VB-CG chip
• USB Host: USB Type A x 1 and USB pin header x 1
• MicroSD Slot: MicroSD x 1 for system boot and storage
• LED: Power LED x 1, System LED x 1
• GPIO1: 2.54mm pitch 10 pin-header, includes UART, I2C, IO, 5VIN/(or OUT)etc
• GPIO2: 2.54mm pitch 6 pin-header, includes USB, line out, IO etc
• Serial Debug Port: 2.54mm pitch 2pin-pads, 115200bps
• Audio: line out on GPIO2
• MicroUSB: Power input(5V/2A) and OTG
• PCB Dimension: 40 x 40mm
• Working Temperature: -20℃ to 70℃
• Weight: 16.37g

3 Software Features

4 Diagram, Layout and Dimension

4.1 Layout

NanoPi NEO2 Black Layout

• GPIO1（I2C/UART/GPIO）

Pin#	Name	Linux gpio	Pin#	Name	Linux gpio
1	GPIOA0	0	2	5V in or out	-
3	I2C_SDA0	-	4	5V in or out	-
5	I2C_SCL0	-	6	GND	-
7	GPIOA2	2	8	UART1_TX	-
9	GND	-	10	UART1_RX	-

• GPIO2（USB/Audio OUT）

Pin#	Name	Linux gpio	Pin#	Name	Linux gpio
1	Line out Right	-	2	USB DM	-
3	Line out Left	-	4	USB DP	-
5	GND	-	6	GPIOA3	3

• eMMC Module Socket Pinout

Pin#	Name	Pin#	Name
1	EMMC_D0	2	EMMC_D1
3	EMMC_D2	4	EMMC_D3
5	EMMC_D4	6	EMMC_D5
7	EMMC_D6	8	EMMC_D7
9	N/C	10	GND
11	EMMC_CMD	12	EMMC_CLK
13	N/C	14	GND
15	N/C	16	3.3V OUT
17	eMMC_RST	18	3.3V OUT
19	GND	20	GND

Note:

1. For more details refer to the document: NanoPi_NEO2_Black_1907_Schematic.pdf

4.2 Dimensional Diagram

Refer to the document: pcb file in dxf format

5 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 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 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.
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 uses overlayfs. 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.

eFlasher 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	Same as FriendlyCore
Linux-4.14	Same as FriendlyCore
File System	Based on UbuntuCore-16.04, it has original UbuntuCore features. It has an eFlasher utility with GUI, which is set to auto-run on system startup. For more details refer to EFlasher. It has an eFlasher commandline utility. It supports multiple OS options. It shows system installation process bar. It supports data backup from and restoration to eMMC. It can detect image files located on the root directory of an external storage device(e.g. USB disk).

6 Get Started

6.1 Essentials You Need

Before starting to use your NanoPi NEO2 Black get the following items ready

• NanoPi NEO2 Black
• TF Card: Class 10 or Above, minimum 8GB SDHC
• 5V/2A Power adapter with microUSB port
• A host computer running Ubuntu 16.04 64-bit system

6.2 TF Cards We Tested

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

6.3 Install OS

6.3.1 Get Image Files

Visit this linkdownload linkto download image files(under the officail-ROMs directory) and the flashing utility(under the tools directory):

Image Files:
nanopi-neo2-black_sd_friendlycore-xenial_4.14_arm64_YYYYMMDD.img.zip	基于UbuntuCore构建的系统固件，使用Linux-4.14内核
nanopi-neo2-black_sd_friendlywrt_4.14_arm64_YYYYMMDD.img.zip	基于OpenWrt构建的系统固件，使用Linux-4.14内核
nanopi-neo2-black_eflasher_friendlycore-xenial_4.14_arm64_YYYYMMDD.img.zip	eflasher系统固件，用于将FriendlyCore(Linux-4.14)系统烧写到eMMC
nanopi-neo2-black_eflasher_friendlywrt_4.14_armhf_YYYYMMDD.img.zip	eflasher系统固件，用于将OpenWrt(Linux-4.14)系统烧写到eMMC
烧写工具：
win32diskimager.rar	Windows平台下的系统烧写工具，Linux平台下可以用dd命令烧写系统

6.3.2 Linux

6.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-black_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.3.2.2 Flash to eMMC

6.3.2.2.1 Flash OS with eflasher Utility

• For more details about eflasher refer to the wiki link: EFlasher。
• Extract the eflasher Image and win32diskimager.rar files. Insert a TF card(at least 4G) 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.
• Insert this card into your board's BOOT slot and power on (with a 5V/2A power source). If the green LED is on and the blue LED is blinking this indicates your board has successfully booted.
• If your board doesn't support HDMI or no monitor is connected you can select an OS by running the following command:

$ su root
$ eflasher

The password for "root" is "fa".

We take "nanopi-neo2-black_eflasher_friendlycore-xenial_4.14_arm64_YYYYMMDD.img" as an example. After you run the "eflasher" command you will see the following messages:

Type "1", select writing friendlycore system to eMMC you will see the following messages:

Type "yes" to start installation:

After it is done power off the system, take off the TF card, power on again your system will be booted from eMMC.

• If you want to flash other system to eMMC you can download the whole images-for-eflasher directory and extract the package under that directory to the FRIENDLYARM partition of an installation SD card.
  

7 Work with FriendlyCore

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

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

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

7.4 Develop Qt Application

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

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

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

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

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

7.9 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

7.10 Modify timezone

For exampe, change to Shanghai timezone:

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

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

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

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

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

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

7.16 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

7.17 Run Qt Demo

Run the following command

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

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

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

7.18.1 How to Install Docker

Run the following commands：

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

7.18.2 Test Docker installation

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

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

8 Work with OpenWrt

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

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

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

By default you will login as root without a password. You can use "passwd" to set a password for root.

On first boot the system will automatically extend the file system on the TF card to the max capacity:

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:

By default you will login as root without a password, just click on "Login" to login.

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

• Reference Links:
  • openwrt opkg

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

2) RAM:

3) CPU Temperature:

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.

• Reference Links:
  • openwrt luci_app_statistics
  • openwrt statistics.chart.public
  • openwrt statistic.custom

8.5 Check Network->Interfaces Configurations

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

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

8.6 USB WiFi

Currently the NanoPi NEO2 Black only works with a RTL8821CU USB WiFi dongle, plug and play. After this module is connected to the board it will by default work under AP mode and the hotspot's name is "rtl8821cu-mac address" and the password is "password";

8.7 Huawei's WiFi 2 mini(E8372H-155) Module

After this module is connected to the board it will be plug and play. The hotspot's name is "HUAWEI-8DA5". You can connect a device to the internet by connecting to this hotspot.

9 如何编译FriendlyCore系统

9.1 使用Linux-4.14 BSP

NanoPi NEO2 Black仅支持使用64位Linux-4.14内核，并使用64位Ubuntu Core 16.04，关于H5芯片系列开发板使用主线U-boot和Linux-4.14的方法，请参考维基：Building U-boot and Linux for H5/H3/H2+

10 使用扩展配件及编程示例

10.1 使用Python编程操作NanoHat OLED扩展板

NanoHat OLED是一款精致小巧的单色OLED显示屏，带3个按键，我们不仅提供了源代码级驱动，而且为您展现了一个简单实用的Shell界面, 通过它你可以查看系统时间，系统运行状态，以及关机等操作；你还可以下载所有源代码自行修改编译，设计自己喜欢的界面； 配上我们专门为其定制的全金属铝外壳，相信你一定会爱不释手！详见：NanoHat OLED
NanoHat OLED_nanopi_NEO2_Black

11 Developer's Guide

• System Development
  • Building U-boot and Linux for H5/H3/H2+
  • How to Build FriendlyWrt
  • Qt dev: How to Build, Install and Setting Qt Application

• Image Utilities
  • How to make your own SD-bootable ROM
  • How to use overlayfs on Linux
  • EFlasher

• System Configurations
  • npi-config
  • Use NetworkManager to configure network settings

• Hardware Access
  • WiringNP: NanoPi NEO/NEO2/Air GPIO Programming with C
  • RPi.GPIO : NanoPi NEO/NEO2/Air GPIO Programming with Python
  • Hardware Misc
  • Matrix
  • BakeBit
  • HATs&Docks

12 资源链接

12.1 手册原理图等开发资料

• 原理图
  • NanoPi_NEO2_Black_1907_Schematic.pdf
• 尺寸图
  • pcb file in dxf format
• H5芯片手册 Allwinner_H5_Datasheet_V1.0.pdf

12.2 网络资源

• 第三方ROM
  • armbian
• 第三方文章