Difference between revisions of "NanoPi NEO Core"

From FriendlyARM WiKi
Jump to: navigation, search
(资源特性)
(Hardware Spec)
 
(45 intermediate revisions by 4 users not shown)
Line 5: Line 5:
 
[[File:NanoPi NEO Core-2.jpg|thumb|frameless|300px|Front]]
 
[[File:NanoPi NEO Core-2.jpg|thumb|frameless|300px|Front]]
 
[[File:NanoPi NEO Core-3.jpg|thumb|frameless|300px|Back]]
 
[[File:NanoPi NEO Core-3.jpg|thumb|frameless|300px|Back]]
* The NanoPi NEO Core(abbreviated as "NEO Core") is an alternative NanoPi NEO that works like a CPU board with male pin-headers. It has the same form factor as the NanoPi NEO and same pin descriptions. The connectors and ports are populated to pin-headers on the NEO Core. In addition the NEO Core can have an optional onboard eMMC flash which is preferred by industrial customers.
+
* The NanoPi NEO Core(abbreviated as "NEO Core") is an alternative NanoPi NEO that works like a CPU board with male pin-headers. It has the same form factor as the NanoPi NEO and same pin descriptions. The connectors and ports are populated to pin-headers on the NEO Core. The NanoPi NEO Core has ESD protection for its MicroUSB port and TF card slot. In addition the NEO Core can have an optional onboard eMMC flash which is preferred by industrial customers.
 
* The NEO Core uses a popular Allwinner H3 SoC and has onboard 256M/512M DDR3 RAM. FriendlyElec offers  models with three eMMC options: 8GB/16GB/32GB and one that doesn't have eMMC at all.
 
* The NEO Core uses a popular Allwinner H3 SoC and has onboard 256M/512M DDR3 RAM. FriendlyElec offers  models with three eMMC options: 8GB/16GB/32GB and one that doesn't have eMMC at all.
* FriendlyElec migrated UbuntuCore with mainline kernel 4.11 for it.
+
* FriendlyElec migrated UbuntuCore with mainline kernel 4.14 for it.
 
* FriendlyElec develops a [[Mini Shield for NanoPi NEO Core/Core2]] which has the same form factor as the RPi 3. When a NanoPi NEO Core is connected to this Mini Shield the whole assembled module can be well fit into a common RPi 3's case.
 
* FriendlyElec develops a [[Mini Shield for NanoPi NEO Core/Core2]] which has the same form factor as the RPi 3. When a NanoPi NEO Core is connected to this Mini Shield the whole assembled module can be well fit into a common RPi 3's case.
  
Line 24: Line 24:
 
* PC Size: 40 x 40mm
 
* PC Size: 40 x 40mm
 
* Power Supply: DC 5V/2A
 
* Power Supply: DC 5V/2A
* Temperature measuring range: -40℃ to 80℃
+
* Temperature measuring range: -20℃ to 70℃
 
* OS/Software: U-boot,Ubuntu-Core
 
* OS/Software: U-boot,Ubuntu-Core
 
* Weight: xxg(WITHOUT Pin-headers)
 
* Weight: xxg(WITHOUT Pin-headers)
  
==接口布局和尺寸==
+
==Diagram, Layout and Dimension==
===接口布局===
+
===Layout===
[[File:NanoPi-NEO Core-layout.jpg |thumb|600px|NanoPi NEO Core接口布局]]
+
[[File:NanoPi-NEO Core-layout.jpg |thumb|600px|NanoPi NEO Core Layout]]
 
[[File:NEO Core pinout-02.jpg|thumb|frameless|600px|pinout]]
 
[[File:NEO Core pinout-02.jpg|thumb|frameless|600px|pinout]]
  
* '''GPIO1管脚定义'''
+
* '''GPIO1 Pin Description'''
 
::{| class="wikitable"
 
::{| class="wikitable"
 
|-
 
|-
Line 63: Line 63:
 
|}
 
|}
  
* '''GPIO2管脚定义'''
+
* '''GPIO2 Pin Description'''
 
::{| class="wikitable"
 
::{| class="wikitable"
 
|-
 
|-
Line 93: Line 93:
 
|}
 
|}
  
* '''GPIO3管脚定义'''
+
* '''GPIO3 Pin Description'''
 
::{| class="wikitable"
 
::{| class="wikitable"
 
|-
 
|-
Line 118: Line 118:
 
|19  || 5V  ||      ||20    || SYS_3.3V    ||  
 
|19  || 5V  ||      ||20    || SYS_3.3V    ||  
 
|}
 
|}
:'''说明'''
+
:'''Note:'''
::#SYS_3.3V: 3.3V电源输出
+
::# SYS_3.3V: 3.3V power output
::#VDD_5V: 5V电源输入/输出,输入范围:4.7~5.6V
+
::# VVDD_5V: 5V power input/output. When the external device’s power is greater than the MicroUSB's the external device is charging the board otherwise the board powers the external device. The input range is 4.7V ~ 5.6V
::#全部信号引脚均为3.3V电平,输出电流为5mA,可以带动小负荷模块,io都不能带负载
+
::# All pins are 3.3V, output current is 5mA
::#更详细的信息请查看原理图
+
::# For more details refer to its schematic [http://wiki.friendlyarm.com/wiki/images/a/a4/Nanopi_neo_core-v1.1-1802.pdf NanoPi-NEO-Core-V1.1-1802-Schematic.pdf]
  
===机械尺寸===
+
===Dimensional Diagram===
 
[[File:NanoPi-NEO-Core-v1_0-1705-dimensions.png|frameless|450px|]]
 
[[File:NanoPi-NEO-Core-v1_0-1705-dimensions.png|frameless|450px|]]
::详细尺寸:[http://wiki.friendlyarm.com/wiki/index.php/File:NanoPi_NEO_Core-1_0_1705_Dimensions.rar pcb的dxf文件] <br />
+
::For more details refer to the document: [http://wiki.friendlyarm.com/wiki/index.php/File:NanoPi_NEO_Core-V1.1_pcb-Dim.rar NanoPi NEO Core V1.1 1802 pcb in dxf format] <br />
  
==快速入门==
+
==Get Started==
===准备工作===
+
===Essentials You Need===
要开启你的NanoPi NEO Core新玩具,请先准备好以下硬件
+
Before starting to use your NanoPi NEO Core get the following items ready
* NanoPi NEO Core主板
+
* NanoPi NEO Core
* microSD卡/TF卡: Class10或以上的 8GB SDHC卡
+
* microSD Card/TF Card: Class 10 or Above, minimum 8GB SDHC
* 一个microUSB接口的外接电源,要求输出为5V/2A(可使用同规格的手机充电器)
+
* microUSB power. A 5V/2A power is a must
* 一台电脑,需要联网,建议使用Ubuntu 14.04 64位系统
+
* A Host computer running Ubuntu 16.04 64 bit system
===经测试使用的TF卡===
+
 
制作启动NanoPi NEO Core的TF卡时,建议Class10或以上的 8GB SDHC卡。以下是经友善之臂测试验证过的高速TF卡:
+
===TF Cards We Tested===
*SanDisk闪迪 TF 8G Class10 Micro/SD 高速 TF卡:
+
To make your NanoPi NEO Core 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]]
 
[[File:SanDisk MicroSD.png|frameless|100px|SanDisk MicroSD 8G]]
*SanDisk闪迪 TF128G 至尊高速MicroSDXC TF 128G Class10 48MB/S:
+
* SanDisk TF128G MicroSDXC TF 128G Class10 48MB/S:
 
[[File:SanDisk MicroSD-01.png|frameless|100px|SanDisk MicroSD 128G]]
 
[[File:SanDisk MicroSD-01.png|frameless|100px|SanDisk MicroSD 128G]]
*川宇 8G手机内存卡 8GTF卡存储卡 C10高速class10 micro SD卡:
+
* 川宇 8G C10 High Speed class10 micro SD card:
 
[[File:SanDisk MicroSD-02.png|frameless|100px|chuanyu MicroSD 8G]]
 
[[File:SanDisk MicroSD-02.png|frameless|100px|chuanyu MicroSD 8G]]
  
===制作一张带运行系统的TF卡===
+
===Install OS===
====下载系统固件====
+
====Get Image Files====
首先访问[https://pan.baidu.com/s/1gfvKKIf 下载地址]下载需要的固件文件(officail-ROMs目录)和烧写工具(tools目录):<br />
+
Visit this link [http://download.friendlyarm.com/nanopineocore download link] to download image files and the flashing utility:<br />
 
+
 
::{| class="wikitable"
 
::{| class="wikitable"
 
|-
 
|-
|colspan=2|使用以下固件:
+
|colspan=2|Image Files:
 
|-
 
|-
|nanopi-neo-core_ubuntu-core-xenial_4.x.y_YYYYMMDD.img.zip || Ubuntu-Core with Qt-Embedded系统固件,使用Linux-4.x.y内核                    
+
|nanopi-neo-core_sd_friendlycore-xenial_4.14_armhf_YYYYMMDD.img.zip || FriendlyCore (base on UbuntuCore) Image File, kernel: Linux-4.14                    
 
|-
 
|-
|nanopi-neo-core_eflasher_4.x.y_YYYYMMDD.img.zip || eflasher系统固件,使用Linux-4.x.y内核
+
|nanopi-neo-core_sd_openwrt_4.14_armhf_YYYYMMDD.img.zip || OpenWrt, kernel:Linux-4.14
 
|-
 
|-
|colspan=2|烧写工具:  
+
|nanopi-neo-core_eflasher_friendlycore-xenial_4.14_armhf_YYYYMMDD.img.zip || eflasher image, for flashing FriendlyCore(Linux-4.14) to eMMC
 
|-
 
|-
|win32diskimager.rar || Windows平台下的系统烧写工具,Linux平台下可以用dd命令烧写系统
+
|nanopi-neo-core_eflasher_openwrt_4.14_armhf_YYYYMMDD.img.zip || eflasher image, for flashing OpenWrt(Linux-4.14) to eMMC
|-  
+
|}
+
 
+
====TF卡启动系统====
+
=====制作Ubuntu-Core with Qt-Embedded系统TF卡=====
+
*将Ubuntu-Core系统固件和烧写工具win32diskimager.rar分别解压,在Windows下插入TF卡(限4G及以上的卡),以管理员身份运行 win32diskimager 工具,
+
在win32diskimager工具的界面上,选择你的TF卡盘符,选择系统固件,点击 Write 按钮烧写即可。
+
*当制作完成TF卡后,拔出TF卡插入NEO Core的BOOT卡槽,上电启动(注意,这里需要5V/2A的供电),你可以看到绿灯常亮以及蓝灯闪烁,这时你已经成功启动Ubuntu-Core系统。<br />
+
注意: Debian/Ubuntu系列的ROM都可以使用上述方法制作TF系统启动卡。
+
 
+
====烧写系统到eMMC====
+
* 将eflasher系统固件和烧写工具win32diskimager.rar分别解压,在Windows下插入TF卡(限8G及以上的卡),以管理员身份运行 win32diskimager 工具,
+
在win32diskimager工具的界面上,选择你的TF卡盘符,选择系统固件,点击 Write 按钮烧写即可。
+
* 当制作完成TF卡后,拔出TF卡插入NEO Core的BOOT卡槽,上电启动(注意,这里需要5V/2A的供电),你可以看到绿灯常亮以及蓝灯闪烁,这时你已经成功启动eflasher系统。<br />
+
* 在命令行终端中通过执行下列命令进行烧写:
+
<syntaxhighlight lang="bash">
+
$ su root
+
$ eflasher
+
</syntaxhighlight>
+
root用户的密码是fa,输入数字并回车选择想要安装到eMMC的系统,然后输入yes并回车确定开始烧写:<br>
+
[[File:eflasher-console.jpg|frameless|600px|eflasher-console]]<br>
+
等待烧写完毕后,断电并从BOOT卡槽中取出TF卡,此时再上电就会从eMMC启动系统了。
+
 
+
==Ubuntu-Core with Qt-Embedded系统的使用==
+
===运行Ubuntu-Core with Qt-Embedded系统===
+
* 如果您需要进行内核开发,你最好选购一个串口配件,连接了串口,则可以通过串口终端对NEO Core进行操作。以下是串口的接法,接上串口,即可调试。接上串口后你可以选择从串口模块的DC口或者从NEO Core的MicroUSB口进行供电:
+
[[File:PSU-ONECOM-NEO-Core.jpg|frameless|400px|PSU-ONECOM-NEO-Core]]
+
* 推荐搭配Mini Shield for NanoPi NEO Core/Core2底板使用,Mini Shield for NanoPi NEO Core/Core2底板详细介绍请参考[http://wiki.friendlyarm.com/wiki/index.php/Mini_Shield_for_NanoPi_NEO_Core/Core2/zh#.E4.BB.8B.E7.BB.8D Mini Shield for NanoPi NEO Core/Core2底板介绍],以下是底板的接法。<br>
+
[[File:Core_Mini_Shield_for_NanoPi_NEO_Core_Core2.jpg|frameless|600px|Mini Shield for NanoPi NEO Core/Core2]]
+
* Ubuntu-Core默认帐户:
+
普通用户:
+
    用户名: pi
+
    密码: pi
+
 
+
root用户:
+
    用户名: root
+
    密码: fa
+
[[File:neo-core-login.jpg|frameless|500px|neo-core-login]]<br>
+
默认会以 pi 用户自动登录,你可以使用 sudo npi-config 命令取消自动登录。
+
 
+
* 更新软件包:
+
<syntaxhighlight lang="bash">
+
$ sudo apt-get update
+
</syntaxhighlight>
+
 
+
===扩展TF卡文件系统===
+
第一次启动系统时,系统会自动扩展文件系统分区,请耐心等待,TF卡的容量越大,需要等待的时间越长,进入系统后执行下列命令查看文件系统分区大小:
+
<syntaxhighlight lang="bash">
+
$ df -h
+
</syntaxhighlight>
+
 
+
===使用npi-config配置系统===
+
npi-config是一个命令行下的系统配置工具,可以对系统进行一些初始化的配置,可配置的项目包括:用户密码、系统语言、时区、Hostname、SSH开关、自动登录选项、硬件接口(Serial/I2C/SPI/PWM/I2S)使能等,在命令行执行以下命令即可进入:
+
<syntaxhighlight lang="bash">
+
$ sudo npi-config
+
</syntaxhighlight>
+
npi-config的显示界面如下:<br />
+
[[File:npi-config.jpg|frameless|500px|npi-config]]<br />
+
 
+
===连接有线网络===
+
NEO Core在加电开机前如果已正确的连接网线,则系统启动时会自动获取IP地址,如果没有连接网线、没有DHCP服务或是其它网络问题,则会导致获取IP地址失败,同时系统启动会因此等待约15~60秒的时间。
+
手动获取IP地址
+
<syntaxhighlight lang="bash">
+
$ dhclient eth0
+
</syntaxhighlight>
+
 
+
===连接USB WiFi===
+
系统默认已经支持市面上众多常见的USB WiFi,想知道你的USB WiFi是否可用只需将其接在NEO Core上即可,已测试过的USB WiFi型号如下:
+
::{| class="wikitable"
+
 
|-
 
|-
|序号||型号     
+
|colspan=2|Flash Utility: 
 
|-
 
|-
||| RTL8188CUS/8188EU 802.11n WLAN Adapter   
+
|win32diskimager.rar || Windows utility for flashing Debian image. Under Linux users can use "dd"
|-
+
|2  ||  RT2070 Wireless Adapter   
+
 
|-  
 
|-  
|3  ||  RT2870/RT3070 Wireless Adapter
 
|-
 
|4  ||  RTL8192CU Wireless Adapter
 
|-
 
|5  ||  小米WiFi mt7601
 
 
|}
 
|}
* 查看网络设备列表
 
<syntaxhighlight lang="bash">
 
$ sudo nmcli dev
 
</syntaxhighlight>
 
注意,如果列出的设备状态是 unmanaged 的,说明网络设备不受NetworkManager管理,你需要清空 /etc/network/interfaces下的网络设置,然后重启.
 
  
* 开启WiFi
+
{{BurnOS-Allwinner|NanoPi-NEO-Core}}
<syntaxhighlight lang="bash">
+
$ sudo nmcli r wifi on
+
</syntaxhighlight>
+
  
* 扫描附近的 WiFi 热点
+
==Mini Shield for NanoPi NEO Core/Core2==
<syntaxhighlight lang="bash">
+
Here is a setup where we connect a NanoPi NEO Core to a Mini Shield for NanoPi NEO Core/Core2. Here is an introduction to [http://wiki.friendlyarm.com/wiki/index.php/Mini_Shield_for_NanoPi_NEO_Core/Core2/zh#.E4.BB.8B.E7.BB.8D Mini Shield for NanoPi NEO Core/Core2 Mini Shield]<br>:
$ sudo nmcli dev wifi
+
[[File:Core_Mini_Shield_for_NanoPi_NEO_Core_Core2.jpg|frameless|600px|Mini Shield for NanoPi NEO Core/Core2]]
</syntaxhighlight>
+
  
* 连接到指定的 WiFi 热点
+
{{FriendlyCoreGeneral|NanoPi-NEO-Core}}
<syntaxhighlight lang="bash">
+
{{FriendlyCoreAllwinnerH3|NanoPi-NEO-Core}}
$ sudo nmcli dev wifi connect "SSID" password "PASSWORD"
+
</syntaxhighlight>
+
请将 SSID和 PASSWORD 替换成实际的 WiFi名称和密码。<br />
+
连接成功后,下次开机,WiFi 也会自动连接。<br />
+
<br />
+
更详细的NetworkManager使用指南可参考这篇维基:[[Use NetworkManager to configure network settings]]<br />
+
  
===SSH登录===
+
{{OpenWrt1|NanoPi-NEO-Core}}
NEO Core没有任何图形界面输出的接口,如果你没有串口模块,可以通过SSH协议登录NEO Core。假设通过路由器查看到NEO Core的IP地址为192.168.1.230,你可以在PC机上执行如下命令登录NEO Core:
+
<syntaxhighlight lang="bash">
+
$ ssh root@192.168.1.230
+
</syntaxhighlight>
+
密码为fa。
+
  
===连接USB摄像头模块(FA-CAM202)使用===
+
==Make Your Own FriendlyCore==
[[File:USB-Camera-NanoPi-neo-core.png|frameless|500px|USB camera]]<br/>
+
===Use Linux-4.14 BSP===
FA-CAM202是一款200万像素的USB摄像头模块,参考维基[[Matrix - USB_Camera(FA-CAM202)|Matrix - USB_Camera(FA-CAM202)]]。<br>
+
The NanoPi NEO Core has gotten support for kernel Linux-4.14. For more details about how to use mainline u-boot and Linux-4.14 refer to :[[Building U-boot and Linux for H5/H3/H2+]] <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>
+
  
假设NEO Core的IP地址为192.168.1.123,在PC的浏览器中输入 192.168.1.123:8080 就能浏览摄像头采集的画面了,效果如下:<br>
+
==Connect External Modules to NEO Core==
[[File:mjpg-streamer-cam500a.png|frameless|600px|mjpg-streamer-cam500a]] <br>
+
===Connect Mini Shield for NanoPi NEO Core/Core2 to NEO Core===
  
===命令行查看CPU工作温度===
+
===Connect Python Programmable NanoHat OLED to NEO Core===
在串口终端执行如下命令,可以快速地获取CPU的当前温度和运行频率等信息:
+
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]]<br />
<syntaxhighlight lang="bash">
+
$ cpu_freq
+
</syntaxhighlight>
+
 
+
===通过Rpi-Monitor查看系统状态===
+
Ubuntu-Core系统里已经集成了Rpi-Monitor,该服务允许用户在通过浏览器查看开发板系统状态。<br>
+
假设NEO Core的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卡容量等信息。
+
 
+
===通过WiringNP测试GPIO===
+
wiringPi库最早是由Gordon Henderson所编写并维护的一个用C语言写成的类库,除了GPIO库,还包括了I2C库、SPI库、UART库和软件PWM库等,由于wiringPi的API函数和arduino非常相似,这也使得它广受欢迎。
+
wiringPi库除了提供wiringPi类库及其头文件外,还提供了一个命令行工具gpio:可以用来设置和读写GPIO管脚,以方便在Shell脚本中控制GPIO管脚。<br>
+
我们在NEO Core系统中集成了这个工具以便客户测试GPIO管脚。详细信息请参看 [[WiringNP:_WiringPi_for_NanoPi_NEO/NEO2|WiringNP]]<br />
+
 
+
==如何编译Ubuntu-Core with Qt-Embedded系统==
+
===使用开源社区主线BSP===
+
NEO Core现已支持使用Linux-4.x.y内核,并使用Ubuntu Core 16.04,关于H3芯片系列开发板使用主线U-boot和Linux-4.x.y的方法,请参考维基:[[Mainline U-boot & Linux|Mainline U-boot & Linux]] <br>
+
 
+
==使用扩展配件及编程示例==
+
===使用Mini Shield for NanoPi NEO Core/Core2===
+
 
+
===使用Python编程操作NanoHat OLED扩展板===
+
NanoHat OLED是一款精致小巧的单色OLED显示屏,带3个按键,我们不仅提供了源代码级驱动,而且为您展现了一个简单实用的Shell界面, 通过它你可以查看系统时间,系统运行状态,以及关机等操作;你还可以下载所有源代码自行修改编译,设计自己喜欢的界面; 配上我们专门为其定制的全金属铝外壳,相信你一定会爱不释手!详见:[[NanoHat OLED]]<br />
+
 
[[File:NanoHat OLED_nanopi_NEO_Core.jpg|frameless|300px|NanoHat OLED_nanopi_NEO_Core]]
 
[[File:NanoHat OLED_nanopi_NEO_Core.jpg|frameless|300px|NanoHat OLED_nanopi_NEO_Core]]
  
===使用Python编程控制NanoHat Motor 电机驱动模块===
+
===Connect Python Programmable NanoHat Motor to NEO Core===
该模块可驱动四个5V PWM舵机模块和四个12V直流电机或者两个12V四线步进电机,详见:[[NanoHat Motor]]<br />
+
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]]<br />
 
[[File:NanoHat Motor_nanopi_NEO_Core.jpg|frameless|300px|NanoHat Motor_nanopi_NEO_Core]]
 
[[File:NanoHat Motor_nanopi_NEO_Core.jpg|frameless|300px|NanoHat Motor_nanopi_NEO_Core]]
  
===使用NanoHat PCM5102A 数字音频解码模块===
+
===Connect NanoHat PCM5102A to NEO Core===
NanoHat PCM5102A采用了TI公司专业的立体声DAC音频芯片PCM5102A,为您提供数字音频信号完美还原的音乐盛宴, 详见:[[NanoHat PCM5102A]]<br />
+
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]]<br />
 
[[File:Matrix - NanoHat PCM5102A_nanopi_NEO_Core.jpg|frameless|300px|Matrix - NanoHat PCM5102A_nanopi_NEO_Core]]
 
[[File:Matrix - NanoHat PCM5102A_nanopi_NEO_Core.jpg|frameless|300px|Matrix - NanoHat PCM5102A_nanopi_NEO_Core]]
  
===完全兼容的Arduino的UNO Dock扩展板===
+
===Connect Arduino Compatible UNO Dock to NEO Core===
UNO Dock本身就是一个Arduino UNO,你可以使用Arduino IDE开发下载运行所有Arduino工程项目;它还是NanoPi NEO的扩展坞,不仅为其提供稳定可靠的电源输入,还可以使用Python编程控制Arduino配件,借助强大的Ubuntu生态系统,快速把你的Arduino项目送上云端,详见:[[UNO Dock for NanoPi NEO v1.0]]<br />
+
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 NEO Core'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]]<br />
 
[[File:Matrix-UNO_Dock_NEO_Core.jpg|frameless|300px|Matrix-UNO_Dock_NEO_Core]]
 
[[File:Matrix-UNO_Dock_NEO_Core.jpg|frameless|300px|Matrix-UNO_Dock_NEO_Core]]
  
===Power Dock 高效的电源转换模块===
+
===Connect Power Dock to NEO Core===
Power Dock for NanoPi NEO是一个高效的电源转换模块,能为用电设备提供稳定可靠的供电,  详见:[[Power Dock for NanoPi NEO]]<br />
+
The Power Dock for NanoPi NEO Core is a high efficiency power conversion module. It provides stable and reliable power source. Here is a hardware setup:[[Power Dock for NanoPi NEO]]<br />
 
[[File:Power Dock for NanoPi NEO_nanopi_NEO_Core.jpg|frameless|300px|Power Dock for NanoPi NEO_nanopi_NEO_Core]]
 
[[File:Power Dock for NanoPi NEO_nanopi_NEO_Core.jpg|frameless|300px|Power Dock for NanoPi NEO_nanopi_NEO_Core]]
  
===NanoHat Proto 可堆叠的面包板模块===
+
===Connect NanoHat Proto to NEO Core===
NanoHat Proto是一个功能高度自由的模块, 板载EEPROM,详见:[[NanoHat Proto]]<br />
+
The NanoHat Proto is an expansion board which exposes NEO Core'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_Core.jpg|frameless|300px|Matrix - NanoHat Proto_nanopi_NEO_Core]]
 
[[File:Matrix - NanoHat Proto_nanopi_NEO_Core.jpg|frameless|300px|Matrix - NanoHat Proto_nanopi_NEO_Core]]
  
===Matrix - 2'8 SPI Key TFT显示模块===
+
===Connect Matrix - 2'8 SPI Key TFT to NanoPi NEO Core===
Matrix-2'8_SPI_Key_TFT模块是一款2.8英寸的TFT 触摸LCD,模块采用ST7789S驱动IC和XPT2046电阻式触摸IC,屏幕分辨率为240*320,采用SPI控制接口,模块还包含3个独立按键,可根据需要自定义功能。详见:[[Matrix - 2'8 SPI Key TFT]]<br />
+
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]]
 
[[File:Matrix-2'8_SPI_Key_TFT-1706.jpg|frameless|300px|File:Matrix-2'8_SPI_Key_TFT-1706]]
  
==3D 打印外壳==
+
==3D Printing Files==
 +
 
 +
{{DeveloperGuildH3|NanoPi-NEO-Core}}
 +
 
 +
==Resources==
 +
===Datasheet & Schematics===
 +
* Schematic
 +
** [http://wiki.friendlyarm.com/wiki/images/7/7a/NANOPI_NEO_CORE-V1.0.pdf NanoPi-NEO-Core-V1.0-1705-Schematic.pdf]
 +
** [http://wiki.friendlyarm.com/wiki/images/a/a4/Nanopi_neo_core-v1.1-1802.pdf NanoPi-NEO-Core-V1.1-1802-Schematic.pdf]
 +
* Dimensional Diagram
 +
** [http://wiki.friendlyarm.com/wiki/index.php/File:NanoPi_NEO_Core-1_0_1705_Dimensions.rar NanoPi-NEO-Core-1705 pcb的dxf文件]
 +
** [http://wiki.friendlyarm.com/wiki/index.php/File:NanoPi_NEO_Core-V1.1_pcb-Dim.rar NanoPi-NEO-Core-1802 pcb的dxf文件]
 +
* H3's datasheet
 +
** [http://wiki.friendlyarm.com/wiki/images/4/4b/Allwinner_H3_Datasheet_V1.2.pdf Allwinner_H3_Datasheet_V1.2.pdf]
  
==资源链接==
+
==Update Log==
===手册原理图等开发资料===
+
===Dec-1-2017===
* 原理图 [http://wiki.friendlyarm.com/wiki/images/f/f0/NanoPi_NEO_Core-V1.0_1705.pdf NanoPi-NEO-Core-V1.0-1705-Schematic.pdf]
+
* Released English version
* 尺寸图 [http://wiki.friendlyarm.com/wiki/index.php/File:NanoPi_NEO_Core-1_0_1705_Dimensions.rar NanoPi-NEO-Core-1705 pcb的dxf文件]
+
* H3芯片手册 [http://wiki.friendlyarm.com/wiki/images/4/4b/Allwinner_H3_Datasheet_V1.2.pdf Allwinner_H3_Datasheet_V1.2.pdf]
+

Latest revision as of 03:54, 1 July 2019

查看中文

Contents

1 Introduction

Overview
Front
Back
  • The NanoPi NEO Core(abbreviated as "NEO Core") is an alternative NanoPi NEO that works like a CPU board with male pin-headers. It has the same form factor as the NanoPi NEO and same pin descriptions. The connectors and ports are populated to pin-headers on the NEO Core. The NanoPi NEO Core has ESD protection for its MicroUSB port and TF card slot. In addition the NEO Core can have an optional onboard eMMC flash which is preferred by industrial customers.
  • The NEO Core uses a popular Allwinner H3 SoC and has onboard 256M/512M DDR3 RAM. FriendlyElec offers models with three eMMC options: 8GB/16GB/32GB and one that doesn't have eMMC at all.
  • FriendlyElec migrated UbuntuCore with mainline kernel 4.14 for it.
  • FriendlyElec develops a Mini Shield for NanoPi NEO Core/Core2 which has the same form factor as the RPi 3. When a NanoPi NEO Core is connected to this Mini Shield the whole assembled module can be well fit into a common RPi 3's case.

2 Hardware Spec

  • CPU: Allwinner H3, Quad-core Cortex-A7 Up to 1.2GHz
  • DDR3 RAM: 256MB/512MB DDR3 RAM
  • Storage: NC/8GB/16GB/32GB eMMC
  • MicroSD Slot x 1
  • MicroUSB: OTG and power input
  • GPIO: two 2.54mm spacing 12x2pin header,one 2.54mm spacing 10x2pin header
  • Connectivity: 10/100M Ethernet(6Pin, included in 2.54mm pitch pin header)
  • USB Host x3(included in 2.54mm pitch pin header)
  • Debug Serial Port(4Pin, included in 2.54mm pitch pin header )
  • Audio input/output Port(4Pin, included in 2.54mm pitch pin header )
  • GPIO:It includes UART, SPI, I2C, IO etc
  • PC Size: 40 x 40mm
  • Power Supply: DC 5V/2A
  • Temperature measuring range: -20℃ to 70℃
  • OS/Software: U-boot,Ubuntu-Core
  • Weight: xxg(WITHOUT Pin-headers)

3 Diagram, Layout and Dimension

3.1 Layout

NanoPi NEO Core Layout
pinout
  • GPIO1 Pin Description
Pin# Name Linux gpio Pin# Name Linux gpio
1 SYS_3.3V 2 VDD_5V
3 I2C0_SDA / GPIOA12 4 VDD_5V
5 I2C0_SCL / GPIOA11 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
  • GPIO2 Pin Description
Pin# Name Linux gpio Pin# Name Linux gpio
1 VDD_5V 2 SPI1_MOSI / GPIOA15 15
3 USB-DP1 4 SPI1_MISO / GPIOA16 16
5 USB-DM1 6 SPI1_CLK / GPIOA14 14
7 USB-DP2 8 SPI1_CS / GPIOA13 13
9 USB-DM2 10 MICIN1P
11 GPIOL11/IR-RX 363 12 MICIN1N
13 SPDIF-OUT/GPIOA17 17 14 LINEOUTR
15 PCM0_SYNC/I2S0_LRCK/I2C1_SCL 16 LINEOUTL
17 PCM0_CLK/I2S0_BCK/I2C1_SDA 18 UART_RXD0 / GPIOA5 / PWM0 5
19 PCM0_DOUT/I2S0_SDOUT 20 UART_TXD0 / GPIOA4 4
21 PCM0_DIN/I2S0_SDIN 22 VDD_5V
23 GND 24 GND
  • GPIO3 Pin Description
Pin# Name Linux gpio Pin# Name Linux gpio
1 EPHY-LINK-LED 2 EPHY-SPD-LED
3 EPHY-TXP 4 EPHY-TXN
5 EPHY-RXP 6 EPHY-RXN
7 NC 8 NC
9 NC 10 NC
11 GND 12 GND
13 USB-DP3 14 GPIOA7 7
15 USB-DM3 16 I2C2_SCL / GPIOE12
17 5V 18 I2C2_SDA / GPIOE13
19 5V 20 SYS_3.3V
Note:
  1. SYS_3.3V: 3.3V power output
  2. VVDD_5V: 5V power input/output. When the external device’s power is greater than the MicroUSB's the external device is charging the board otherwise the board powers the external device. The input range is 4.7V ~ 5.6V
  3. All pins are 3.3V, output current is 5mA
  4. For more details refer to its schematic NanoPi-NEO-Core-V1.1-1802-Schematic.pdf

3.2 Dimensional Diagram

NanoPi-NEO-Core-v1 0-1705-dimensions.png

For more details refer to the document: NanoPi NEO Core V1.1 1802 pcb in dxf format

4 Get Started

4.1 Essentials You Need

Before starting to use your NanoPi NEO Core get the following items ready

  • NanoPi NEO Core
  • microSD Card/TF Card: 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

4.2 TF Cards We Tested

To make your NanoPi NEO Core 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

4.3 Install OS

4.3.1 Get Image Files

Visit this link download link to download image files and the flashing utility:

Image Files:
nanopi-neo-core_sd_friendlycore-xenial_4.14_armhf_YYYYMMDD.img.zip FriendlyCore (base on UbuntuCore) Image File, kernel: Linux-4.14
nanopi-neo-core_sd_openwrt_4.14_armhf_YYYYMMDD.img.zip OpenWrt, kernel:Linux-4.14
nanopi-neo-core_eflasher_friendlycore-xenial_4.14_armhf_YYYYMMDD.img.zip eflasher image, for flashing FriendlyCore(Linux-4.14) to eMMC
nanopi-neo-core_eflasher_openwrt_4.14_armhf_YYYYMMDD.img.zip eflasher image, for flashing OpenWrt(Linux-4.14) to eMMC
Flash Utility:
win32diskimager.rar Windows utility for flashing Debian image. Under Linux users can use "dd"

4.3.2 Linux

4.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-neo-core_sd_friendlycore-xenial_4.14_armhf_YYYYMMDD.img" as an example here is the installation window. Other image files are installed on the similar window:
win32disk-h3

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.
4.3.2.2 Flash to eMMC
4.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.
  • Connect the board to an HDMI monitor or an LCD and a USB mouse, and select an OS to start installation.

eflasher_friendlycore

  • 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-neo-core_eflasher_friendlycore-xenial_4.14_armhf_YYYYMMDD.img" as an example. After you run the "eflasher" command you will see the following messages:

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

eflasher_friendlycore2_h3
Type "yes" to start installation:

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

eflasher_friendlyarm_h3

5 Mini Shield for NanoPi NEO Core/Core2

Here is a setup where we connect a NanoPi NEO Core to a Mini Shield for NanoPi NEO Core/Core2. Here is an introduction to Mini Shield for NanoPi NEO Core/Core2 Mini Shield
: Mini Shield for NanoPi NEO Core/Core2

6 Work with FriendlyCore

6.1 Introduction

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

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

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

6.2 System Login

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

allow you to operate the board via a serial terminal.Here is a setup where we connect a board to a PC via the PSU-ONECOM and you can power on your board from either the PSU-ONECOM or its MicroUSB: PSU-ONECOM-NEO-Core.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-NEO-Core.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. 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.13 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.14 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.15 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

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-NEO-Core.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-NEO-Core.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 Use Linux-4.14 BSP

The NanoPi NEO Core has gotten support for kernel Linux-4.14. For more details about how to use mainline u-boot and Linux-4.14 refer to :Building U-boot and Linux for H5/H3/H2+

9 Connect External Modules to NEO Core

9.1 Connect Mini Shield for NanoPi NEO Core/Core2 to NEO Core

9.2 Connect Python Programmable NanoHat OLED to NEO Core

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_Core

9.3 Connect Python Programmable NanoHat Motor to NEO Core

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_Core

9.4 Connect NanoHat PCM5102A to NEO Core

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_Core

9.5 Connect Arduino Compatible UNO Dock to NEO Core

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 NEO Core'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_Core

9.6 Connect Power Dock to NEO Core

The Power Dock for NanoPi NEO Core 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_Core

9.7 Connect NanoHat Proto to NEO Core

The NanoHat Proto is an expansion board which exposes NEO Core's various pins.It has an onboard EEPROM for data storage.Here is a hardware setup:NanoHat Proto
Matrix - NanoHat Proto_nanopi_NEO_Core

9.8 Connect Matrix - 2'8 SPI Key TFT to NanoPi NEO Core

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

11 Developer Guide

11.1 Linux 4.14 BSP

11.2 Linux 3.4 BSP

  • Allwinner's document is located at DVD/doc/allwinner-h3-doc.zip,download

11.3 OpenWrt

11.4 ROM

11.5 Hardware access

12 Resources

12.1 Datasheet & Schematics

13 Update Log

13.1 Dec-1-2017

  • Released English version