Difference between revisions of "NanoPi Duo"

From FriendlyELEC WiKi
Jump to: navigation, search
(Work with Ubuntu-Core with Qt-Embedded)
(updated by API)
 
(61 intermediate revisions by 4 users not shown)
Line 5: Line 5:
 
[[File:NanoPi Duo-2.jpg|thumb|frameless|300px|正面]]
 
[[File:NanoPi Duo-2.jpg|thumb|frameless|300px|正面]]
 
[[File:NanoPi Duo-3.jpg|thumb|frameless|300px|背面]]
 
[[File:NanoPi Duo-3.jpg|thumb|frameless|300px|背面]]
* The NanoPi Duo(abbreviated as Duo) is designed and developed by FriendlyElec for makers, hobbyists and fans. It is open source. It uses Allwinner's Coretex-A7 H2+ with internal Mali400MP2 GPU. It has 256MB/512MB DDR3 RAM.  
+
* The NanoPi Duo is designed and developed by FriendlyElec for makers, hobbyists and professionals. It is small, just 50 x 25.4 mm. It uses Allwinner’s Cortex-A7 H2+ SoC. It has 256M/512M DDR3 RAM and an onboard WiFi module. A UbuntuCore image is ready for it.
* The NanoPi Duo's dimension is 25.4 x 50mm. It exposes interfaces such as Ethernet, two USB ports and audio. It can boot from a MicroSD card.
+
* On such a small board rich interfaces such as Ethernet, USB, SPI, UART, I2C, PWM, IR and audio are exposed. It is powered from a MicroUSB port and boots OS from a MicroSD card.
 +
* Popular libraries and utilities: WiringNP and Python are ported to the NanoPi Duo’s system and they all are open source. The NanoPi Duo perfectly suits various light-weight IoT applications.
  
 
==Hardware Spec==
 
==Hardware Spec==
Line 13: Line 14:
 
* Connectivity: 10/100M Ethernet
 
* Connectivity: 10/100M Ethernet
 
* Wifi:XR819
 
* Wifi:XR819
* USB Host: 2.54mm pin x2
+
* USB Host: 2.54mm pin x2, exposed in 2.54mm pitch pin header
 
* MicroSD Slot x 1
 
* MicroSD Slot x 1
 
* MicroUSB: OTG and power input  
 
* MicroUSB: OTG and power input  
* Debug Serial Port:2.54mm pitch pin header
+
* Debug Serial Interface: exposed in 2.54mm pitch pin header
* Audio input/output Port: 2.54mm pitch pin header
+
* Audio input/output Interface: exposed in 2.54mm pitch pin header
* GPIO: 2.54mm spacing 12pin x2, It includes UART, SPI, I2C, IO etc
+
* GPIO1: 2.54mm spacing 16pin. It includes UART, SPI, I2C, Audio etc
* PC Size: 25.4 x 50mm
+
* GPIO2: 2.54mm spacing 16pin. It includes USB,10/100M Ethernet, IO etc
 +
* PCB Dimension: 25.4 x 50mm
 
* Power Supply: DC 5V/2A
 
* Power Supply: DC 5V/2A
* Working Temperature: -40℃ to 80℃
+
* Temperature measuring range: -20℃ to 70℃
* OS/Software: U-boot,Ubuntu-Core
+
* OS/Software: U-boot,Linux Kernel 4.11.2 (mainline) , Ubuntu 16.04.2 LTS (Xenial)
 
* Weight: xxg(With Pin-headers)
 
* Weight: xxg(With Pin-headers)
 +
 +
==Software Features==
 +
===uboot===
 +
* uboot
 +
 +
===Ubuntu 16.04===
 +
* mainline kernel: Linux-4.11.2
 +
* Ubuntu 16.04.2
 +
* rpi-monitor: check system status and information
 +
* npi-config: system configuration utility for setting passwords, language, timezone, hostname, SSH and auto-login, and enabling/disabling i2c, spi, serial and PWM
 +
* software utility: wiringNP to access GPIO pins
 +
* software utility: RPi.GPIO_NP to access GPIO pins
 +
* networkmanager: manage networks
 +
* system log output from serial port
 +
* nano editor
 +
* welcome window with basic system information and status
 +
* auto-login with user account "pi" with access to npi-config
 +
* sudoers include "fa"
 +
* on first system boot file system will be automatically extended.
 +
* supports file system auto check and repair on system boot.
 +
* supports audio recording and playing with 3.5mm audio jack
 +
* supports USB Host and 100M Ethernet
 +
* fixed MAC address
  
 
==Diagram, Layout and Dimension==
 
==Diagram, Layout and Dimension==
 
===Layout===
 
===Layout===
[[File:NanoPi-Duo-layout.jpg |thumb|600px|NanoPi Duo Layout]]
+
[[File:NanoPi-Duo-layout.jpg |thumb|500px|NanoPi Duo Layout]]
[[File:Duo pinout-02.jpg|thumb|frameless|600px|pinout]]
+
[[File:Duo pinout-02.jpg|thumb|frameless|500px|pinout]]
 
* '''GPIO Pin Description'''
 
* '''GPIO Pin Description'''
 
::{| class="wikitable"
 
::{| class="wikitable"
Line 71: Line 96:
 
:'''Note:'''
 
:'''Note:'''
 
::#SYS_3.3V: 3.3V power output
 
::#SYS_3.3V: 3.3V power output
::#VDD_5V: 5V power input/output. When the external device’s voltage is greater than the MicroUSB's voltage the external device is charging the board otherwise the board powers the external device. The input range is 4.7V ~ 5.6V
+
::#VDD_5V: 5V power input/output. When the external device’s voltage is greater than the MicroUSB's voltage the external device is powering the board,
 +
otherwise the board powers the external device. The input range is 4.7V ~ 5.5V
 
::#All pins are 3.3V, output current is 5mA
 
::#All pins are 3.3V, output current is 5mA
::#For more details refer to the document [http://wiki.friendlyarm.com/wiki/images/b/b0/Schematic_NanoPi_Duo-v1.0-1706.pdf  NanoPi Duo Schematic]
+
::#For more details refer to the document [http://wiki.friendlyelec.com/wiki/images/8/8a/Schematic_NanoPi_Duo-v1.1.pdf  NanoPi Duo Schematic]
  
 
===Dimensional Diagram===
 
===Dimensional Diagram===
 
[[File:NanoPi-Duo-1606-dimensions.png|frameless|550px|]]
 
[[File:NanoPi-Duo-1606-dimensions.png|frameless|550px|]]
  
::For more details refer to the document [http://wiki.friendlyarm.com/wiki/index.php/File:Dimension_NanoPi_Duo_v1.0_1706-PCB.rar NanoPi_Duo_v1.0_1706 pcb file in dxf format]
+
::For more details refer to the document [http://wiki.friendlyelec.com/wiki/index.php/File:Dimension_NanoPi_Duo_v1.0_1706-PCB.rar NanoPi_Duo_v1.0_1706 pcb file in dxf format]
  
 
==Get Started==
 
==Get Started==
Line 86: Line 112:
 
* 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 18.04 64 bit system
 
* a serial communication board
 
* a serial communication board
  
===TF Cards We Tested===
+
{{TFCardsWeTested}}
To make your NanoPi Duo 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:
+
[[File:SanDisk MicroSD.png|frameless|100px|SanDisk MicroSD 8G]]
+
* SanDisk TF128G MicroSDXC TF 128G Class10 48MB/S:
+
[[File:SanDisk MicroSD-01.png|frameless|100px|SanDisk MicroSD 128G]]
+
* 川宇 8G C10 High Speed class10 micro SD card:
+
[[File:SanDisk MicroSD-02.png|frameless|100px|chuanyu MicroSD 8G]]
+
  
===Make an Installation TF Card===
+
===Install OS===
 
====Download Image Files====
 
====Download Image Files====
Get the following files from here [https://pan.baidu.com/s/1pLLmV27 download link] to download image files (under the official-ROMs directory) and the flashing utility(under the tools directory):<br />
+
Get the following files from here [http://download.friendlyelec.com/nanopiduo download link] to download image files (under the official-ROMs directory) and the flashing utility (under the tools directory):<br />
 
::{| class="wikitable"
 
::{| class="wikitable"
 
|-
 
|-
 
|colspan=2|Image Files:
 
|colspan=2|Image Files:
 
|-
 
|-
|nanopi-duo_ubuntu-core-xenial_4.x.y_YYYYMMDD.img.zip || Ubuntu-Core with Qt-Embedded Image File, kernel:Linux-4.x.y                     
+
|nanopi-duo_sd_friendlycore-xenial_4.14.y_YYYYMMDD.img.zip || FriendlyCore (base on UbuntuCore) Image File, kernel:Linux-4.x.y                     
 +
|-
 +
|nanopi-duo_sd_friendlywrt_4.14_armhf_YYYYMMDD.img.zip || Base on OpenWrt, kernel:Linux-4.14
 
|-
 
|-
 
|colspan=2|Flash Utility:   
 
|colspan=2|Flash Utility:   
Line 113: Line 134:
 
|}
 
|}
  
====Make Installation MicroSD Card with Ubuntu-Core with Qt-Embedded Image====
+
{{BurnOS-Allwinner|NanoPi-Duo}}
Extract an OS image and win32diskimager.rar. Insert a MicroSD 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 SD card till it is done.Insert this card into your Duo's MicroSD card slot and power on (with a 5V/2A power source). If the blue LED is blinking this indicates your Duo has successfully booted.<br/>
+
  
==Work with Ubuntu-Core with Qt-Embedded==
+
====NanoPi Duo can work with FriendlyElec's Mini Shield====
===Run Ubuntu-Core with Qt-Embedded===
+
The NanoPi Duo can work with FriendlyElec's Mini Shield for NanoPi Duo. Here is link to the wiki site of Mini Shield for NanoPi Duo [http://wiki.friendlyelec.com/wiki/index.php/Mini_Shield_for_NanoPi_Duo Mini Shield for NanoPi Duo]. Here is a hardware setup.<br>
* 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
+
[[File:Mini Shield for NanoPi Duo.jpg|frameless|600px|Mini Shield for NanoPi Duo_NanoPi_Duo]]
[[File:USB2UART-Duo.jpg|frameless|400px|USB2UART-Duo]]
+
 
+
* The NanoPi Duo can work with FriendlyElec's Mini Shield for NanoPi Duo.Here is link to the wiki site of Mini Shield for NanoPi Duo [http://---n/zh Mini Shield for NanoPi Duo底板介绍]. Here is a hardware setup.<br>
+
[[File:Mini_Shield_for_NanoPi_Duo-Duo.jpg|frameless|400px|Mini Shield for NanoPi Duo-Duo]]
+
* Ubuntu-Core User Accounts:
+
Non-root User:
+
    User Name: pi
+
    Password: pi
+
 
+
Root:
+
    User Name: root
+
    Password: fa
+
[[File:duo-login.jpg|frameless|500px|duo-login]]<br>
+
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 OS 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>
+
 
+
===Work with npi-config Utility===
+
The npi-config is a system configuration utility for setting passwords, language, timezone, hostname, SSH and auto-login,and enabling/disabling i2c, spi, serial and PWM and I2S. You can start this utillity by running the following command:
+
<syntaxhighlight lang="bash">
+
$ sudo npi-config
+
</syntaxhighlight>
+
Here is the npi-config's main window:<br />
+
[[File:npi-config.jpg|frameless|500px|npi-config]]<br />
+
 
+
===连接有线网络===
+
使用Mini Shield for NanoPi Duo底板能方便的连接有线网络,Duo在加电开机前如果已正确的连接网线,则系统启动时会自动获取IP地址,如果没有连接网线、没有DHCP服务或是其它网络问题,则会导致获取IP地址失败,同时系统启动会因此等待约15~60秒的时间。
+
手动获取IP地址
+
<syntaxhighlight lang="bash">
+
$ dhclient eth0
+
</syntaxhighlight>
+
 
+
===连接WiFi===
+
使用以下命令连接Wifi,Duo板子上集成了Wifi天线,为保证数据传输稳定可靠,建议外接扩转天线。<br />
+
* 查看网络设备列表
+
<syntaxhighlight lang="bash">
+
$ sudo nmcli dev
+
</syntaxhighlight>
+
注意,如果列出的设备状态是 unmanaged 的,说明网络设备不受NetworkManager管理,你需要清空 /etc/network/interfaces下的网络设置,然后重启.
+
 
+
* 开启WiFi
+
<syntaxhighlight lang="bash">
+
$ sudo nmcli r wifi on
+
</syntaxhighlight>
+
 
+
* 扫描附近的 WiFi 热点
+
<syntaxhighlight lang="bash">
+
$ sudo nmcli dev wifi
+
</syntaxhighlight>
+
 
+
* 连接到指定的 WiFi 热点
+
<syntaxhighlight lang="bash">
+
$ sudo nmcli dev wifi connect "SSID" password "PASSWORD"
+
</syntaxhighlight>
+
请将 SSID和 PASSWORD 替换成实际的 WiFi名称和密码。<br />
+
连接成功后,下次开机,WiFi 也会自动连接。<br />
+
<br />
+
更详细的NetworkManager使用指南可参考这篇维基:[[Use NetworkManager to configure network settings]]<br />
+
 
+
搭配Mini Shield for NanoPi Duo底板使用,还可使用USB WiFi。系统默认已经支持市面上众多常见的USB WiFi,想知道你的USB WiFi是否可用只需将其接在Duo上即可,已测试过的USB WiFi型号如下:
+
::{| class="wikitable"
+
|-
+
|序号||型号     
+
|-
+
|1  ||  RTL8188CUS/8188EU 802.11n WLAN Adapter   
+
|-
+
|2  ||  RT2070 Wireless Adapter   
+
|-
+
|3  ||  RT2870/RT3070 Wireless Adapter
+
|-
+
|4  ||  RTL8192CU Wireless Adapter
+
|-
+
|5  ||  小米WiFi mt7601
+
|}
+
  
===SSH登录===
+
{{FriendlyCoreGeneral|NanoPi-Duo}}
Duo没有任何图形界面输出的接口,如果你没有串口模块,可以通过SSH协议登录Duo。假设通过路由器查看到Duo的IP地址为192.168.1.230,你可以在PC机上执行如下命令登录Duo:
+
{{FriendlyCoreAllwinnerH3|NanoPi-Duo}}
<syntaxhighlight lang="bash">
+
{{FriendlyCoreAllwinnerH2|NanoPi-Duo}}
$ ssh root@192.168.1.230
+
</syntaxhighlight>
+
密码为fa。
+
  
===连接USB摄像头模块(FA-CAM202)使用===
+
{{OpenWrt1|NanoPi-Duo}}
搭配Mini Shield for NanoPi Duo底板可连接USB摄像头模块(FA-CAM202)模块。<br>
+
[[File:USB-Camera-NanoPi-duo.png|frameless|500px|USB camera]]<br/>
+
FA-CAM202是一款200万像素的USB摄像头模块,参考维基[[Matrix - USB_Camera(FA-CAM202)|Matrix - USB_Camera(FA-CAM202)]]。<br>
+
启动系统,连接网络,以root用户登录终端并编译运行mjpg-streamer:
+
<syntaxhighlight lang="bash">
+
$ su root
+
$ cd /root/mjpg-streamer
+
$ make
+
$ ./start.sh
+
</syntaxhighlight>
+
mjpg-streamer是一个开源的网络视频流服务器,在板子上成功运行mjpg-streamer后会打印下列信息:
+
<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>
+
  
假设Duo的IP地址为192.168.1.123,在PC的浏览器中输入 192.168.1.123:8080 就能浏览摄像头采集的画面了,效果如下:<br>
+
==Make Your Own FriendlyCore==
[[File:mjpg-streamer-cam500a.png|frameless|600px|mjpg-streamer-cam500a]] <br>
+
===Use Mainline BSP===
 +
The NanoPi Duo has support for kernel Linux-4.14.y with Ubuntu Core 16.04. For more details about how to use mainline u-boot and Linux-4.14.y refer to :[[Mainline U-boot & Linux|Mainline U-boot & Linux]] <br>
  
===命令行查看CPU工作温度===
+
{{H3-KernelHeaderFile}}
在串口终端执行如下命令,可以快速地获取CPU的当前温度和运行频率等信息:
+
==Connect External Modules to Duo==
<syntaxhighlight lang="bash">
+
===Connect Mini Shield for NanoPi NEO Duo to Duo===
$ cpu_freq
+
</syntaxhighlight>
+
  
===通过Rpi-Monitor查看系统状态===
+
==3D Printing Files==
Ubuntu-Core系统里已经集成了Rpi-Monitor,该服务允许用户在通过浏览器查看开发板系统状态。<br>
+
假设Duo的IP地址为192.168.1.230,在PC的浏览器中输入下述地址:
+
<syntaxhighlight lang="bash">
+
192.168.1.230:8888
+
</syntaxhighlight>
+
可以进入如下页面:<br>
+
[[File:rpi-monitor.png|frameless|700px|rpi-monitor]] <br>
+
  
用户可以非常方便地查看到系统负载、CPU的频率和温度、可用内存、SD卡容量等信息。
+
==Developer Guide==
 +
===How to make ROM===
 +
* [[How_to_make_your_own_SD-bootable_ROM | How to make your own SD-bootable ROM]]
 +
===SPI===
 +
* [[SPI | How to Use SPI ]]
  
===通过WiringNP测试GPIO===
+
==Resources==
wiringPi库最早是由Gordon Henderson所编写并维护的一个用C语言写成的类库,除了GPIO库,还包括了I2C库、SPI库、UART库和软件PWM库等,由于wiringPi的API函数和arduino非常相似,这也使得它广受欢迎。
+
===Schematics & Datasheets===
wiringPi库除了提供wiringPi类库及其头文件外,还提供了一个命令行工具gpio:可以用来设置和读写GPIO管脚,以方便在Shell脚本中控制GPIO管脚。<br>
+
* Schematics: [http://wiki.friendlyelec.com/wiki/images/9/9a/Schematic_NanoPi_Duo-V1.0_1706.pdf  NanoPi Duo V1.0 1706 schematic]
我们在Duo系统中集成了这个工具以便客户测试GPIO管脚。详细信息请参看 [[WiringNP:_WiringPi_for_NanoPi_NEO/NEO2|WiringNP]]<br />
+
* Schematics: [http://wiki.friendlyelec.com/wiki/images/8/8a/Schematic_NanoPi_Duo-v1.1.pdf  NanoPi Duo V1.1 1709 Schematics]
 +
* Dimensional Diagram: [http://wiki.friendlyelec.com/wiki/index.php/File:Dimension_NanoPi_Duo_v1.0_1706-PCB.rar  NanoPi Duo V1.0 1706 PCB Dimensional Diagram]  
 +
* Datasheet:[http://wiki.friendlyelec.com/wiki/images/0/08/Allwinner_H2%2B_Datasheet_V1.2.pdf  Allwinner_H2+_Datasheet]
  
==如何编译Ubuntu-Core with Qt-Embedded系统==
+
==Update Log==
===使用开源社区主线BSP===
+
===July-17-2017===
Duo现已支持使用Linux-4.x.y内核,并使用Ubuntu Core 16.04,关于H2+芯片系列开发板使用主线U-boot和Linux-4.x.y的方法,请参考维基:[[Mainline U-boot & Linux|Mainline U-boot & Linux]] <br>
+
* Released English Version
  
==使用扩展配件及编程示例==
+
===August-12-2017===
===使用Mini Shield for NanoPi NEO Duo===
+
* Updated section 1
  
 +
===August-29-2017===
 +
* Added section 3
  
==3D 打印外壳==
+
===Sep-3-2017===
 +
* Corrected spelling and grammar errors
  
==资源链接==
+
===Nov-9-2017===
===手册原理图等开发资料===
+
* Added section 6.11
* 原理图: [http://wiki.friendlyarm.com/wiki/images/b/b0/Schematic_NanoPi_Duo-v1.0-1706.pdf  NanoPi Duo V1.0 1706原理图]
+
* 尺寸图: [http://wiki.friendlyarm.com/wiki/index.php/File:Dimension_NanoPi_Duo_v1.0_1706-PCB.rar  NanoPi Duo V1.0 1706 PCB尺寸图]
+
* 芯片手册:
+

Latest revision as of 07:56, 21 March 2022

查看中文

Contents

1 Introduction

概览
正面
背面
  • The NanoPi Duo is designed and developed by FriendlyElec for makers, hobbyists and professionals. It is small, just 50 x 25.4 mm. It uses Allwinner’s Cortex-A7 H2+ SoC. It has 256M/512M DDR3 RAM and an onboard WiFi module. A UbuntuCore image is ready for it.
  • On such a small board rich interfaces such as Ethernet, USB, SPI, UART, I2C, PWM, IR and audio are exposed. It is powered from a MicroUSB port and boots OS from a MicroSD card.
  • Popular libraries and utilities: WiringNP and Python are ported to the NanoPi Duo’s system and they all are open source. The NanoPi Duo perfectly suits various light-weight IoT applications.

2 Hardware Spec

  • CPU: Allwinner H2+, Quad-core Cortex-A7
  • DDR3 RAM: 256MB/512MB
  • Connectivity: 10/100M Ethernet
  • Wifi:XR819
  • USB Host: 2.54mm pin x2, exposed in 2.54mm pitch pin header
  • MicroSD Slot x 1
  • MicroUSB: OTG and power input
  • Debug Serial Interface: exposed in 2.54mm pitch pin header
  • Audio input/output Interface: exposed in 2.54mm pitch pin header
  • GPIO1: 2.54mm spacing 16pin. It includes UART, SPI, I2C, Audio etc
  • GPIO2: 2.54mm spacing 16pin. It includes USB,10/100M Ethernet, IO etc
  • PCB Dimension: 25.4 x 50mm
  • Power Supply: DC 5V/2A
  • Temperature measuring range: -20℃ to 70℃
  • OS/Software: U-boot,Linux Kernel 4.11.2 (mainline) , Ubuntu 16.04.2 LTS (Xenial)
  • Weight: xxg(With Pin-headers)

3 Software Features

3.1 uboot

  • uboot

3.2 Ubuntu 16.04

  • mainline kernel: Linux-4.11.2
  • Ubuntu 16.04.2
  • rpi-monitor: check system status and information
  • npi-config: system configuration utility for setting passwords, language, timezone, hostname, SSH and auto-login, and enabling/disabling i2c, spi, serial and PWM
  • software utility: wiringNP to access GPIO pins
  • software utility: RPi.GPIO_NP to access GPIO pins
  • networkmanager: manage networks
  • system log output from serial port
  • nano editor
  • welcome window with basic system information and status
  • auto-login with user account "pi" with access to npi-config
  • sudoers include "fa"
  • on first system boot file system will be automatically extended.
  • supports file system auto check and repair on system boot.
  • supports audio recording and playing with 3.5mm audio jack
  • supports USB Host and 100M Ethernet
  • fixed MAC address

4 Diagram, Layout and Dimension

4.1 Layout

NanoPi Duo Layout
pinout
  • GPIO Pin Description
Pin silk screen Name Linux gpio Pin silk screen Name Linux gpio
MICN MIC_N SPD EPHY-LED-SPD
MICP MIC_P LNK EPHY-LED-LINK
LOR LINEOUT_R TD+ EPHY-TXP
LOL LINEOUT_L TD- EPHY-TXN
CVB CVBS RD+ EPHY-RXP
TX1 UART1_TX/GPIOG6 198 RD- EPHY-RXN
RX1 UART1_RX/GPIOG7 199 DP2 USB-DP2
MO UART3_RTS/SPI1_MOSI/GPIOA15 15 DM2 USB-DM2
MI UART3_CTS/SPI1_MISO/GPIOA16 16 DP3 USB-DP3
CLK UART3_RX/SPI1_CLK/GPIOA14 14 DM3 USB-DM3
CS UART3_TX/SPI1_CS/GPIOA13 13 IOG11 GPIOG11 203
SDA I2C0_SDA/GPIOA12 12 IRRX GPIOL11/IR-RX 363
SCL I2C0_SCL/GPIOA11 11 GND GND
GND GND 3V3 SYS_3.3V
DTX DEBUG_TX(UART_TXD0)/GPIOA4 4 5Vin VDD_5V
DRX DEBUG_RX(UART_RXD0)/GPIOA5/PWM0 5 5Vin VDD_5V


Note:
  1. SYS_3.3V: 3.3V power output
  2. VDD_5V: 5V power input/output. When the external device’s voltage is greater than the MicroUSB's voltage the external device is powering the board,
otherwise the board powers the external device. The input range is 4.7V ~ 5.5V
  1. All pins are 3.3V, output current is 5mA
  2. For more details refer to the document NanoPi Duo Schematic

4.2 Dimensional Diagram

NanoPi-Duo-1606-dimensions.png

For more details refer to the document NanoPi_Duo_v1.0_1706 pcb file in dxf format

5 Get Started

5.1 Essentials You Need

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

  • NanoPi Duo
  • microSD Card/TFCard: Class 10 or Above, minimum 8GB SDHC
  • microUSB power. A 5V/2A power is a must
  • A host computer running Ubuntu 18.04 64 bit system
  • a serial communication board

5.2 TF Cards We Tested

To make your device 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 MicroSDHC V30 32GB Extreme Pro (Developer choice)

SanDiskExtremePro

  • SanDisk 32GB High Endurance Video MicroSDHC Card with Adapter for Dash Cam and Home Monitoring Systems (High reliability)

SanDiskHighEndurance

  • SanDisk TF 8G Class10 Micro/SD High Speed 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 Download Image Files

Get the following files from here download link to download image files (under the official-ROMs directory) and the flashing utility (under the tools directory):

Image Files:
nanopi-duo_sd_friendlycore-xenial_4.14.y_YYYYMMDD.img.zip FriendlyCore (base on UbuntuCore) Image File, kernel:Linux-4.x.y
nanopi-duo_sd_friendlywrt_4.14_armhf_YYYYMMDD.img.zip Base on OpenWrt, kernel:Linux-4.14
Flash Utility:
win32diskimager.rar Windows utility. Under Linux users can use "dd"


5.3.2 NanoPi Duo can work with FriendlyElec's Mini Shield

The NanoPi Duo can work with FriendlyElec's Mini Shield for NanoPi Duo. Here is link to the wiki site of Mini Shield for NanoPi Duo Mini Shield for NanoPi Duo. Here is a hardware setup.
Mini Shield for NanoPi Duo_NanoPi_Duo

6 Work with FriendlyCore

6.1 Introduction

FriendlyCore is a light Linux system without X-windows, based on ubuntu core, It uses the Qt-Embedded's GUI and is popular in industrial and enterprise applications.

Besides the regular Ubuntu Core's features FriendlyCore has the following additional features:

  • it integrates Qt4.8;
  • it integrates NetworkManager;
  • it has bluez and Bluetooth related packages;
  • it has alsa packages;
  • it has npi-config;
  • it has RPiGPIO, a Python GPIO module;
  • it has some Python/C demo in /root/ directory;
  • it enables 512M-swap partition;

6.2 System Login

  • If your board is connected to an HDMI monitor you need to use a USB mouse and keyboard.
  • If you want to do kernel development you need to use a serial communication board, ie a PSU-ONECOM board, which will

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-Duo.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
6 5G USB WiFi RTL8821CU
7 5G USB WiFi RTL8812AU

You can use the NetworkManager utility to manage network. You can run "nmcli" in the commandline utility to start it. Here are the commands to start a WiFi connection:

  • Change to root
$ su root
  • Check device list
$ nmcli dev

Note: if the status of a device is "unmanaged" it means that device cannot be accessed by NetworkManager. To make it accessed you need to clear the settings under "/etc/network/interfaces" and reboot your system.

  • Start WiFi
$ nmcli r wifi on
  • Scan Surrounding WiFi Sources
$ nmcli dev wifi
  • Connect to a WiFi Source
$ nmcli dev wifi connect "SSID" password "PASSWORD" ifname wlan0

The "SSID" and "PASSWORD" need to be replaced with your actual SSID and password.If you have multiple WiFi devices you need to specify the one you want to connect to a WiFi source with iface
If a connection succeeds it will be automatically setup on next system reboot.

For more details about NetworkManager refer to this link: Use NetworkManager to configure network settings

If your USB WiFi module doesn't work most likely your system doesn't have its driver. For a Debian system you can get a driver from Debian-WiFi and install it on your system. For a Ubuntu system you can install a driver by running the following commands:

$ apt-get install linux-firmware

In general all WiFi drivers are located at the "/lib/firmware" directory.


6.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 Custom welcome message

The welcome message is printed from the script in this directory:

/etc/update-motd.d/

For example, to change the FriendlyELEC LOGO, you can change the file /etc/update-motd.d/10-header. For example, to change the LOGO to HELLO, you can change the following line:

TERM=linux toilet -f standard -F metal $BOARD_VENDOR

To:

TERM=linux toilet -f standard -F metal HELLO

6.12 Modify timezone

For exampe, change to Shanghai timezone:

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

6.13 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.14 Connect to USB Camera(FA-CAM202)

The FA-CAM202 is a 200M USB camera. Connect your board to camera module. Then boot OS, connect your board to a network, log into the board as root and run "mjpg-streamer":

$ cd /root/C/mjpg-streamer
$ make
$ ./start.sh

You need to change the start.sh script and make sure it uses a correct /dev/videoX node. You can check your camera's node by running the following commands:

$ apt-get install v4l-utils
$ v4l2-ctl -d /dev/video0 -D
Driver Info (not using libv4l2):
        Driver name   : uvcvideo
        Card type     : HC 3358+2100: HC 3358+2100  / USB 2.0 Camera: USB 2.0 Camera
        Bus info      : usb-1c1b000.usb-1
	...

The above messages indicate that "/dev/video0" is camera's device node.The mjpg-streamer application is an open source video steam server. After it is successfully started the following messages will be popped up:

 
$ ./start.sh
 i: Using V4L2 device.: /dev/video0
 i: Desired Resolution: 1280 x 720
 i: Frames Per Second.: 30
 i: Format............: YUV
 i: JPEG Quality......: 90
 o: www-folder-path...: ./www/
 o: HTTP TCP port.....: 8080
 o: username:password.: disabled
 o: commands..........: enabled

start.sh runs the following two commands:

export LD_LIBRARY_PATH="$(pwd)"
./mjpg_streamer -i "./input_uvc.so -d /dev/video0 -y 1 -r 1280x720 -f 30 -q 90 -n -fb 0" -o "./output_http.so -w ./www"

Here are some details for mjpg_streamer's major options:
-i: input device. For example "input_uvc.so" means it takes input from a camera;
-o: output device. For example "output_http.so" means the it transmits data via http;
-d: input device's subparameter. It defines a camera's device node;
-y: input device's subparameter. It defines a camera's data format: 1:yuyv, 2:yvyu, 3:uyvy 4:vyuy. If this option isn't defined MJPEG will be set as the data format;
-r: input device's subparameter. It defines a camera's resolution;
-f: input device's subparameter. It defines a camera's fps. But whether this fps is supported depends on its driver;
-q: input device's subparameter. It defines the quality of an image generated by libjpeg soft-encoding;
-n: input device's subparameter. It disables the dynctrls function;
-fb: input device's subparameter. It specifies whether an input image is displayed at "/dev/fbX";
-w: output device's subparameter. It defines a directory to hold web pages;

In our case the board's IP address was 192.168.1.230. We typed 192.168.1.230:8080 in a browser and were able to view the images taken from the camera's. Here is what you would expect to observe:
mjpg-streamer-cam500a

6.15 Check CPU's Working Temperature

You can get CPU's working temperature by running the following command:

$ cpu_freq 
Aavailable frequency(KHz):
        480000 624000 816000 1008000
Current frequency(KHz):
        CPU0 online=1 temp=26548C governor=ondemand freq=624000KHz
        CPU1 online=1 temp=26548C governor=ondemand freq=624000KHz
        CPU2 online=1 temp=26548C governor=ondemand freq=624000KHz
        CPU3 online=1 temp=26548C governor=ondemand freq=624000KHz

This message means there are currently four CPUs working. All of their working temperature is 26.5 degree in Celsius and each one's clock is 624MHz.
Set CPU frequency:

$ cpu_freq -s 1008000
Aavailable frequency(KHz):
        480000 624000 816000 1008000
Current frequency(KHz):
        CPU0 online=1 temp=36702C governor=userspace freq=1008000KHz
        CPU1 online=1 temp=36702C governor=userspace freq=1008000KHz
        CPU2 online=1 temp=36702C governor=userspace freq=1008000KHz
        CPU3 online=1 temp=36702C governor=userspace freq=1008000KHz


6.16 Test Infrared Receiver

Note: Please Check your board if IR receiver exist.
By default the infrared function is disabled you can enable it by using the npi-config utility:

$ npi-config
    6 Advanced Options     Configure advanced settings
        A8 IR              Enable/Disable IR
            ir Enable/Disable ir[enabled]

Reboot your system and test its infrared function by running the following commands:

$ apt-get install ir-keytable
$ echo "+rc-5 +nec +rc-6 +jvc +sony +rc-5-sz +sanyo +sharp +mce_kbd +xmp" > /sys/class/rc/rc0/protocols   # Enable infrared
$ ir-keytable -t
Testing events. Please, press CTRL-C to abort.

"ir-keytable -t" is used to check whether the receiver receives infrared signals. You can use a remote control to send infrared signals to the receiver. If it works you will see similar messages as follows:

1522404275.767215: event type EV_MSC(0x04): scancode = 0xe0e43
1522404275.767215: event type EV_SYN(0x00).
1522404278.911267: event type EV_MSC(0x04): scancode = 0xe0e42
1522404278.911267: event type EV_SYN(0x00).

6.17 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.18 How to install and use docker (for armhf system)

6.18.1 How to Install Docker

Run the following commands:

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

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

6.19 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.20 Boot System from SSD

A NanoPi-Duo can be booted from the SSD on a Mini Shield for NanoPi Duo. Booting OS from an SSD has the following benefits:
1) faster read/write;
2) much longer life time than a TF card;
3) more reliable than booting from a TF card;

You can install an OS to SSD by using the npi-config utility. Here are the steps to follow:

sudo npi-config

Enter the "Boot Options" menu, go to "Boot device" and you will see two options:
1) D1 Hard drive
2) D2 TF card
Select "D1 Hard drive" and proceed with its prompts.
Select "D2 TF card" to boot OS from a TF card.

If your npi-config doesn't have a "Boot device" menu it might be that your npi-config is out of date and you can update it by selecting "Update" in the menu.

6.21 How to install and use docker (for armhf system)

6.21.1 How to Install Docker

Run the following commands:

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

6.21.2 Test Docker installation

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

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

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


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

By default in FriendlyElec's OpenWrt system the WiFi AP hotspot's name is like "OpenWrt-10:d0:7a:de:3d:92" and the network segment is 192.168.2.x. You can connect your device to it and login with SSH without a password by running the following command:

$ ssh root@192.168.2.1

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.2.1 for the Ethernet connection, type this IP address in a browser's address bar and you will be able to login OpenWrt-LuCI:
OpenWrt-LuCI_wlan0
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_br

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

7.6 Check Netwrok->Wireless Configurations

  • After open the OpenWrt-LuCI page, go to Network ---> Wireless and you will see the WiFi hotspot's configurations:

op_wireless
A default WiFi AP's hotspot name looks like "OpenWrt-10:d0:7a:de:3d:92". It doesn't have a password. You can connect your smart phone to it and browse the internet.

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



7.7 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";

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

8 Make Your Own FriendlyCore

8.1 Use Mainline BSP

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

9 Build Kernel Headers Package

The following commands need to be executed on the development board:

9.1 Software Version

The OS image file name: nanopi-XXX_sd_friendlycore-focal_4.14_armhf_YYYYMMDD.img

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04 LTS
Release:        20.04
Codename:       focal
 
$ cat /proc/version
Linux version 4.14.111 (root@ubuntu) (gcc version 4.9.3 (ctng-1.21.0-229g-FA)) #193 SMP Thu Jun 10 18:20:47 CST 2021

9.2 Install the required packages

sudo apt-get update
sudo apt-get install dpkg-dev libarchive-tools

9.3 Build Kernel Headers Package

git clone https://github.com/friendlyarm/linux -b sunxi-4.14.y --depth 1 kernel-h3
cd kernel-h3
rm -rf .git
make distclean
touch .scmversion
make CROSS_COMPILE= ARCH=arm sunxi_defconfig
alias tar=bsdtar
make CROSS_COMPILE= ARCH=arm bindeb-pkg -j4

The following message is displayed to indicate completion:

dpkg-deb: building package 'linux-headers-4.14.111' in '../linux-headers-4.14.111_4.14.111-1_armhf.deb'.
dpkg-deb: building package 'linux-libc-dev' in '../linux-libc-dev_4.14.111-1_armhf.deb'.
dpkg-deb: building package 'linux-image-4.14.111' in '../linux-image-4.14.111_4.14.111-1_armhf.deb'.
dpkg-genchanges: warning: substitution variable ${kernel:debarch} used, but is not defined
dpkg-genchanges: info: binary-only upload (no source code included)

10 Installation=

sudo dpkg -i ../linux-headers-4.14.111_4.14.111-1_armhf.deb

10.1 Testing

To compile the pf_ring module as an example, refer to the documentation: https://www.ntop.org/guides/pf_ring/get_started/git_installation.html.

git clone https://github.com/ntop/PF_RING.git
cd PF_RING/kernel/
make

After compiling, use insmod to try to load the module:

sudo insmod ./pf_ring.ko

11 Connect External Modules to Duo

11.1 Connect Mini Shield for NanoPi NEO Duo to Duo

12 3D Printing Files

13 Developer Guide

13.1 How to make ROM

13.2 SPI

14 Resources

14.1 Schematics & Datasheets

15 Update Log

15.1 July-17-2017

  • Released English Version

15.2 August-12-2017

  • Updated section 1

15.3 August-29-2017

  • Added section 3

15.4 Sep-3-2017

  • Corrected spelling and grammar errors

15.5 Nov-9-2017

  • Added section 6.11