Difference between revisions of "NanoPC-T2"

From FriendlyELEC WiKi
Jump to: navigation, search
(制作一张带运行系统的SD卡)
(updated by API)
 
(257 intermediate revisions by 6 users not shown)
Line 2: Line 2:
  
 
==Introduction==
 
==Introduction==
[[File:NanoPC-T2-01B.jpg|thumb|Overview]]
+
[[File:NanoPC-T2-1B.jpg|thumb|Overview]]
[[File:NanoPC-T2-A01.jpg|thumb|Front]]
+
[[File:NanoPC-T2-A1.jpg|thumb|Front]]
[[File:NanoPC-T2-B01.jpg|thumb|Back]]
+
[[File:NanoPC-T2-B1.jpg|thumb|Back]]
* The NanoPC-T2 quad core Cortex A9 single board computer is designed and developed by FriendlyARM for professional and enterprise users. It uses Samsung Quad Core Cortex-A9 S5P4418 SoC with dynamic frequency scaling up to 1.4GHz. Compared to FriendlyARM's existing 4418 based boards the NanoPC-T2 has 8G eMMC onboard, audio jack and video input/output interfaces. Compared to its predecessor the NanoPC-T1 the NanoPC-T2 has built-in WiFi, Bluetooth and Gbps Ethernet port. In addition the NanoPC-T2 has power management which the NanoPC-T1 doesn't support. To avoid overheat issues the NanoPC-T2 has a heat sink with mounting holes.  
+
* The NanoPC-T2 quad core Cortex A9 single board computer is designed and developed by FriendlyARM for professional and enterprise users. It uses the Samsung Quad Core Cortex-A9 S5P4418 SoC with dynamic frequency scaling up to 1.4GHz. Compared to FriendlyARM's existing 4418 based boards the NanoPC-T2 has 8G eMMC onboard, audio jack and video input/output interfaces. Compared to its predecessor the NanoPC-T1 the NanoPC-T2 has built-in WiFi, Bluetooth and Gbps Ethernet port. In addition the NanoPC-T2 has power management which the NanoPC-T1 doesn't support. To avoid overheat issues the NanoPC-T2 has a heat sink with mounting posts.  
* The NanoPC-T2 combines all the ports and interfaces the existing FriendlyARM 4418 boards have. Currently it has the most interfaces and ports among all existing ARM boards of this size. Its rich video interfaces and support for HDMI 1080P make it work with not only popular display devices but also various FriendlyARM LCDs with both resistive touch and capacitive touch.  
+
* The NanoPC-T2 combines all the ports and interfaces the existing FriendlyARM 4418 boards have. Currently it has the most interfaces and ports among all existing ARM boards of this size. Its rich video interfaces and support for HDMI 1080P enable it to work with not only popular display devices but also various FriendlyARM LCDs (both resistive touch and capacitive touch).  
 
* The NanoPC-T2 is FriendlyARM's most complete solution based on Samsung 4418 for both commercial and industrial applications.
 
* The NanoPC-T2 is FriendlyARM's most complete solution based on Samsung 4418 for both commercial and industrial applications.
  
==Features==
+
==Hardware Spec==
 
* SoC: Samsung S5P4418 Quad Core Cortex-A9 with dynamic frequency scaling up to 1.4G Hz
 
* SoC: Samsung S5P4418 Quad Core Cortex-A9 with dynamic frequency scaling up to 1.4G Hz
* Power Management Unit: AXP228 PMU, it supports software power-off and wake-up.
+
* PMU Power Management: Implemented by an MCU, support solftware power-off, and RTC alarm power-on functions
 
* System Memory: 1GB 32bit DDR3 RAM
 
* System Memory: 1GB 32bit DDR3 RAM
 
* eMMC: 8GB
 
* eMMC: 8GB
* Storage: 1 x SD Card Socket
+
* Storage: 1 x SD Card Slot
* Ethernet: Gbps Ethernet Port (RTL8211E)
+
* Ethernet: Gbps Ethernet Port (RTL8211E) with unique MAC
 
* WiFi: 802.11b/g/n
 
* WiFi: 802.11b/g/n
 
* Bluetooth: 4.0 dual mode
 
* Bluetooth: 4.0 dual mode
Line 32: Line 32:
 
* LED: 1 x power LED , 2 x GPIO LED
 
* LED: 1 x power LED , 2 x GPIO LED
 
* User Key: 1 x K1 (power), 1 x Reset
 
* User Key: 1 x K1 (power), 1 x Reset
 +
* Other Resource: 1 x onboard thermistor
 
* RTC Battery: RTC Seat Pins
 
* RTC Battery: RTC Seat Pins
 
* Power: DC 5V/2A
 
* Power: DC 5V/2A
 
* Heat Sink: 1 x Heat Sink with mounting holes
 
* Heat Sink: 1 x Heat Sink with mounting holes
* PCB: Six Layer
+
* PCB: Six Layer, ENIG
 
* PCB Dimension: 100 mm x 60 mm
 
* PCB Dimension: 100 mm x 60 mm
* OS/Software: u-boot, Android5.1, Debian8
+
* Working Temperature: -40℃ to 70℃
 +
* OS/Software: u-boot, Android 4.4, Android5.1 and Debian8
 +
 
 +
==Software Features==
 +
===UbuntuCore===
 +
<!---
 +
* mainline kernel: Linux-4.11.2
 +
* rpi-monitor: check system status and information
 +
--->
 +
* npi-config: system configuration utility for setting passwords, language, timezone, hostname, SSH and auto-login,and enabling/disabling i2c, spi, serial and PWM
 +
<!---
 +
* software utility: wiringNP to access GPIO pins
 +
* software utility: RPi.GPIO_NP to access GPIO pins
 +
--->
 +
* networkmanager: manage network
 +
* system log output from serial port
 +
<!---
 +
* nano editor
 +
--->
 +
* welcome window with basic system information and status
 +
* auto-login with user account "pi" with access to npi-config
 +
* UART2 enabled
 +
* supports CAM500B
 +
<!---
 +
* sudoers include "fa"
 +
* on first system boot file system will be automatically extended.
 +
* supports file system auto check and repair on system boot.
 +
* supports FriendlyElec's [http://wiki.friendlyelec.com/wiki/index.php/NanoHat_PCM5102A NanoHat-PCM5102A] 
 +
* supports USB WiFi module: refer to [[#Connect USB WiFi to NEO]]
 +
* supports audio recording and playing with 3.5mm audio jack
 +
* supports USB Host and 100M Ethernet
 +
* supports FriendlyElec BakeBit modules
 +
* supports dynamic frequency scaling and voltage regulation
 +
* relieves overheat compared to kernel Linux-3.4
 +
* fixed MAC address
 +
 
 +
===Ubuntu OLED===
 +
* mainline kernel: Linux-4.11.2
 +
* supports FriendlyElec's OLED module
 +
--->
 +
 
 +
===Debian===
 +
* supports CAM500B
 +
 
 +
<!---
 +
===Debian for NAS Dock===
 +
* mainline kernel: Linux-4.11.2
 +
* supports FriendlyElec's NAS Dock
 +
* optimized OpenMediaVault configuration options
 +
* allocated swap section
 +
--->
 +
===Android===
 +
* supports setting up static IP
 +
* supports accessing hardware with FriendlyElec's libfriendlyarm-things.so
 +
* integrated iTest utility for testing hardware
  
 
==Diagram, Layout and Dimension==
 
==Diagram, Layout and Dimension==
 
===Layout===
 
===Layout===
[[File:NanoPC-T2-1512B-IF.png |thumb|600px|NanoPC-T2 Layout]]
+
[[File:NanoPC-T2-IF.png |thumb|600px|NanoPC-T2 Layout]]
  
 
* '''30Pin GPIO Pin Spec'''
 
* '''30Pin GPIO Pin Spec'''
Line 79: Line 134:
 
|}
 
|}
  
* '''20Pin LVDS Interface Pin Spec'''
+
* '''LVDS '''
 
::{| class="wikitable"
 
::{| class="wikitable"
 
|-
 
|-
|Pin# || Name         ||Pin#  || Name   
+
|Pin# || Name      
 
|-
 
|-
|1   || SYS_3.3V ||2    || SYS_3.3V
+
|1  || VDD_5V
 
|-
 
|-
|3   ||GPIOC16      ||4     || GPIOB18
+
|2 || VDD_5V
 +
|-
 +
|3 || VDD_5V
 +
|-
 +
|4   || LVDS_Y0M
 
|-  
 
|-  
|5    || DGND      ||6     || DGND  
+
|5    || LVDS_Y0P 
 +
|-
 +
|6 || DGND
 +
|-
 +
|7    || LVDS_Y1M
 +
|-
 +
|8    || LVDS_Y1P
 +
|-
 +
|9 || DGND
 +
|-
 +
|10  || LVDS_Y2M
 +
|-
 +
|11  || LVDS_Y2P
 +
|-
 +
|12 || DGND
 +
|-
 +
|13  || LVDS_CLKM
 +
|-
 +
|14  || LVDS_CLKP
 
|-
 
|-
|7    || LVDS_D0-      ||8    || LVDS_D0+
+
|15 || DGND
 
|-
 
|-
|9    || LVDS_D1-          ||10    || LVDS_D1+
+
|16  || LVDS_Y3M
 
|-
 
|-
|11  || LVDS_D2-      ||12    || LVDS_D2+
+
|17  || LVDS_Y3P
 
|-
 
|-
|13  || DGND        ||14    || DGND  
+
|18  || DGND
 
|-
 
|-
|15  || LVDS_CLK-      ||16    || LVDS_CLK+
+
|19  || GPIOB18
 
|-
 
|-
|17  || LVDS_D3- ||18    || LVDS_D3+
+
|20 || DGND
 
|-
 
|-
|19  ||I2C2_SCL     ||20    || I2C2_SDA
+
|21  || I2C2_SCL
 +
|-
 +
|22 || I2C2_SDA
 +
|-
 +
|23  || GPIOC16
 +
|-
 +
|24 || DGND
 
|}
 
|}
  
Line 122: Line 205:
 
|6    || GPIOB16
 
|6    || GPIOB16
 
|-
 
|-
|8,10  || NC
+
|8   || GPIOC13/PWM1
 +
|-
 +
|10  || NC
 
|-
 
|-
 
|11  || VSYNC
 
|11  || VSYNC
Line 162: Line 247:
 
|36      || LCDCLK || LCD clock, Pixel frequency
 
|36      || LCDCLK || LCD clock, Pixel frequency
 
|-
 
|-
|41      || I2C2_SCL  || I2C2 clock signal, for capacitive touch's data transmission
+
|41      || I2C2_SCL  || I2C2 clock signal, for capacitive touch data transmission
 
|-
 
|-
|42      || I2C2_SDA  || I2C2 data signal, for capacitive touch's data transmission
+
|42      || I2C2_SDA  || I2C2 data signal, for capacitive touch data transmission
 
|-
 
|-
 
|43      || GPIOC16 || interrupt pin for capacitive touch, used with I2C2
 
|43      || GPIOC16 || interrupt pin for capacitive touch, used with I2C2
Line 186: Line 271:
 
|7  || DGND
 
|7  || DGND
 
|-
 
|-
|8      || GPIOC0
+
|8      || GPIOC16
 
|-
 
|-
 
|9      || DGND
 
|9      || DGND
Line 256: Line 341:
 
|11      || DGND
 
|11      || DGND
 
|-
 
|-
|12      || GPIOB9
+
|12      || GPIOB23
 
|-
 
|-
 
|13      || GPIOC2
 
|13      || GPIOC2
 
|-
 
|-
|14, 15 || DGND
+
|14     || GPIOC13/PWM1
 +
|-
 +
15 || DGND
 
|-
 
|-
 
|16      || MIPICSI_DN3
 
|16      || MIPICSI_DN3
Line 294: Line 381:
 
:'''Note:'''
 
:'''Note:'''
 
::#SYS_3.3V: 3.3V power output
 
::#SYS_3.3V: 3.3V power output
::#VDD_5V: 5V power input/output. The input range is 4.7V ~ 5.6V
+
::#VDD_5V: 5V power output
::#For more details please refer to the document: [http://wiki.friendlyarm.com/wiki/images/0/00/NanoPC-T2_1601B_Schematic.pdf NanoPC-T2_1601B_Schematic.pdf]
+
::#For more details refer to the document: [http://wiki.friendlyelec.com/wiki/images/b/b4/NanoPC-T2-T3-1711-Schematic.pdf NanoPC-T2-T3-Schematic.pdf]
  
 
===Board Dimension===
 
===Board Dimension===
[[File:NanoPC-T2_1601B_Dimensions.png|frameless|600px|NanoPC-T2 1601B Dimensions]]
+
[[File:NanoPC-T2-T3.png|frameless|800px|NanoPC-T2 Dimensions]]
  
::For more details please refer to the document: [http://wiki.friendlyarm.com/wiki/images/c/c8/NanoPC-T2-1601B-Dimensions%28dxf%29.zip NanoPC-T2-1601B-Dimensions(dxf).zip]
+
::For more details refer to the document: [http://wiki.friendlyelec.com/wiki/images/8/88/NanoPC-T2-T3_1711_Draw_dxf.zip NanoPC-T2-T3_1711_Draw_dxf.zip]
 +
 
 +
*'''Power Jack'''
 +
::*DC 4.7~5.6V IN, 4.0*1.7mm Power Jack
 +
::[[File:DC-023.png]]
 +
 
 +
==Notes in Hardware Design==
 +
===EEPROM===
 +
* The board has an EEPROM(model: 24AA025E48T-I/OT) with a unique MAC. This EEPROM is connected to I2C0 and its address is 0x51 therefore some EEPROM chips cannot be connected to I2C0 which will cause conflicts of addresses.
 +
* In our tests these EEPROM chips cannot be connected to I2C0: 24C04, 24C08 and 24C16. There chips which we tested can be connected to I2C0: 24C01, 24C02 and 24C256
 +
* For more details about EEPROM address issues refer to http://www.onsemi.com/pub_link/Collateral/CAT24C01-D.PDF
  
 
==Get Started==
 
==Get Started==
 
===Essentials You Need===
 
===Essentials You Need===
Before play with your NanoPC-T2 please get the following items ready
+
Before starting to use your NanoPC-T2 get the following items ready
 
* NanoPC-T2
 
* NanoPC-T2
 
* SD Card: Class 10 or Above, minimum 8GB SDHC
 
* SD Card: Class 10 or Above, minimum 8GB SDHC
Line 310: Line 407:
 
* HDMI monitor or LCD
 
* HDMI monitor or LCD
 
* USB keyboard, mouse and possible a USB hub(or a TTL to serial board)
 
* USB keyboard, mouse and possible a USB hub(or a TTL to serial board)
* A Host running Ubuntu 14.04 64 bit system
+
* A host computer running Ubuntu 18.04 64 bit system
 
+
{{S5P4418BootFromSDCard|NanoPC-T2}}
===Make an Installation SD Card===
+
{{BurnOSToEMMC|NanoPC-T2|s5p4418-eflasher}}
====Boot NanoPC-T2 from SD Card====
+
{{S5PXX18MakeSDCardViaSDFusing|NanoPC-T2|sd-fuse_s5p4418}}
首先访问[http://wiki.friendlyarm.com/wiki/nanopi2/download/ 此处的下载地址]下载需要的固件文件:<br />
+
{{ResizeTFCardFS|NanoPC-T2}}
* 您需要准备一张4G或以上容量的SDHC卡,该卡的已有数据将会被破坏,因此请先对SD卡上的数据进行备份。 <br />
+
{{S5Pxx18HDMI|NanoPC-T2|arch/arm/plat-s5p4418/nanopi2/lcds.c}}
::{| class="wikitable"
+
{{S5Pxx18MofidyKernelCommandLineOnHostPC|NanoPC-T2|sd-fuse_s5p4418}}
|-
+
{{NanoPCStartToUse|NanoPC-T2}}
|colspan=2|使用LCD或HDMI作来输出的用户,使用以下固件:
+
{{FriendlyCoreGeneral|NanoPC-T2}}
|-
+
{{FriendlyCoreRunX11Application|NanoPC-T2}}
|nanopi2-debian-sd4g.img.zip      || Debian系统固件                 
+
{{FriendlyCoreS5Pxx18|NanoPC-T2}}
|-
+
{{UbuntuXenial-Armhf-Install-Docker|NanoPC-T2}}
|nanopi2-android-sd4g.img.zip      || Android系统固件 
+
{{S5Pxx18Android|NanoPC-T2}}
|-
+
{{MoreOS}}
|colspan=2|烧写工具: 
+
{{S5P4418BuildFromSource|NanoPC-T2}}
|-
+
{{S5P4418-KernelHeaderFile|NanoPC-T2}}
|win32diskimager.rar || Windows平台下的烧写工具,Linux系统可以用dd命令
+
{{S5Pxx18ExternalModules|NanoPC-T2}}
|-
+
{{S5Pxx18AccessHWUnderAndroid|NanoPC-T2}}
|}
+
{{S5Pxx18ConnectToLCDModules|NanoPC-T2}}
 
+
{{S5Pxx18HWfiles|NanoPC-T2}}
*将固件和烧写工具分别解压,在Windows下插入SD卡(限4G及以上的卡),以管理员身份运行 win32diskimager 工具, 在win32diskimager工具的界面上, 选择你的SD卡盘符,选择你要烧写的系统固件,点击 Write 按钮烧写即可。
+
{{S5P4418Resources|NanoPC-T2}}
*当制作完成 SD 卡后,拔出 SD 卡插入 NanoPC-T2 的 BOOT 卡槽,按住靠网口位置的boot按键上电启动(注意,这里需要 5V/2A 的供电),你可以看到板上红灯常亮,PWR绿灯闪烁,这时你已经成功启动NanoPC-T2。<br />
+
{{DownloadUrl|NanoPC-T2}}
 
+
{{TechSupport|NanoPC-T2}}
====Boot NanoPC-T2 from eMMC====
+
{{S5P4418ChangeLog}}
* 下载RAW Image <br />
+
用于制作烧写eMMC的SD卡的RAW Image: nanopi2-eflasher-sd4g.img.zip。并且需要下载Windows下的烧写工具: win32diskimager.rar;
+
* 烧写RAW Image <br />
+
在Windows下插入SDHC卡(限4G及以上的卡),以管理员身份运行Win32DiskImager,选择 Image File,选择你的SD卡盘符,点 Write 即开始写Image到SD卡。
+
* 准备好烧写到eMMC的ROM
+
到以下链接[http://wiki.friendlyarm.com/wiki/nanopi2/download/]相关Android或者Debian的Images(System-image-files-for-eMMC),下载完成后,在本地解压 .tgz 压缩包,然后将解压出来的文件(不包含目录)复制到SD卡对应的文件夹/目录。
+
::{| class="wikitable"
+
|-
+
|OS || Image  || Files || Copy to...
+
|-
+
|Android 5.1  || android-lollipop-images.tgz <br /> android-lollipop-images.tgz.hash.md5
+
|| boot.img <br /> system.img <br /> userdata.img <br /> cache.img <br /> partmap.txt <br />
+
|| images\android
+
|-
+
|Debian (Jessie) || debian-jessie-images.tgz <br />debian-jessie-images.tgz.hash.md5
+
|| boot.img <br />rootfs.img <br />partmap.txt <br />
+
|| images\debian
+
|-
+
|}
+
 
+
* 指定需要烧写的OS
+
SD卡上配置文件 images\FriendlyARM.ini 缺省是将烧写 Android,如果要烧写Debian,则只需要编辑此文件:
+
<syntaxhighlight lang="bash">
+
OS = Debian
+
</syntaxhighlight>
+
即可,其中配置文件中”#” 开始行的是注释。
+
 
+
* 烧写到NanoPC-T2的eMMC
+
将制作好的SD卡插入NanoPC-T2,连接HDMI或LCD, 按住网口旁边标住有boot的按键,拨动电源开关,板子则会自动开始烧写,你可以通过HDMI或LCD上的显示来查看烧写状态,如果看到以下内容即表示成功,否则失败。
+
<syntaxhighlight lang="bash">
+
Android is fused successfully.
+
All done.
+
</syntaxhighlight>
+
烧写成功完成后,必须按复位键或重新加电, 即可从eMMC启动。
+
+
;你可以根据LED来确定烧写状态,以下是状态检查表:
+
::{| class="wikitable"
+
|-
+
|LED闪烁状态 || 系统状态
+
|-
+
|LED1心跳模式闪 (连续快闪2次) <br /> LED2灭  || 加电后正常启动的状态 <br /> 如果没有进行烧写则会保
+
|-
+
|LED1和LED2交替闪烁 (0.3s) || 正在烧写系统
+
|-
+
|LED1和LED2交替的呼吸效果 (1.2s) || 烧写成功
+
|-  
+
|LED1和LED2同时快闪 || 烧写失败
+
|-
+
|}
+
 
+
====在Linux Desktop下通过脚本制作====
+
* 1) 将SD卡插入Ubuntu的电脑,用以下命令查看你的SD卡设备名
+
<syntaxhighlight lang="bash">
+
dmesg | tail
+
</syntaxhighlight>
+
当dmesg输出类拟信息 sdc: sdc1 sdc2时,则表示SD卡对应的设备名为 /dev/sdc,也通过用命令cat /proc/partitions来查看。
+
 
+
*2) 下载Linux下的制作脚本
+
<syntaxhighlight lang="bash">
+
git clone https://github.com/friendlyarm/sd-fuse_nanopi2.git
+
cd sd-fuse_nanopi2
+
</syntaxhighlight>
+
 
+
*3) 以下是制作启动Android的SD卡的方法
+
<syntaxhighlight lang="bash">
+
su
+
./fusing.sh /dev/sdx
+
</syntaxhighlight>
+
(注:/dev/sdx请替换为实际的SD卡设备文件名) <br />
+
制作包中未包含Android和Debian的烧写文件,第一次使用时会提示需要下载,输入Y下载,N或10秒未输入则取消。
+
 
+
*4) 以下是制作启动Debian的SD卡的方法
+
<syntaxhighlight lang="bash">
+
./fusing.sh /dev/sdx debian
+
</syntaxhighlight>
+
 
+
====关于LCD/HDMI分辨率====
+
系统启动时uboot会自动识别LCD,成功则会设置为该LCD的显示分辨率,失败则缺省会设置为HDMI 720P模式。<br />
+
如果要修改LCD的显示分辨率,可以直接修改内核中的文件 arch/arm/plat-s5p4418/nanopi2/lcds.c , 然后重新编译内核并更新即可。<br />
+
对于HDMI的显示模式,Android则是会通过EDID获得HDMI设备如电视机所支持的显示模式,然后自动选择一个合适的分辨率。如果使用的是Debian,则缺省是720P,可通过修改内核配置来切换为1080P。
+
 
+
===在电脑上修改SD卡上的系统===
+
如果你想在运行系统之前,先对系统做一些修改,可以参看本节内容,否则可以跳过本节。<br />
+
将制作好SD卡插入一台运行Linux的电脑,可以挂载SD卡上的boot和rootfs等分区,对分区内容进行修改,通过在以下情况下你需要进行这些操作:<br />
+
1) 你想更改Kernel Command Line参数,则可以通过sd-fuse_nanopi2/tools目录下的fw_setenv工具来操作。<br />
+
查看当前的Command Line:
+
<syntaxhighlight lang="bash">
+
cd sd-fuse_nanopi2/tools
+
./fw_printenv /dev/sdc | grep bootargs
+
</syntaxhighlight>
+
目前的Android 5.1.1_r6启用了SELinux,缺省模式是enforcing,你可以通过Command Line来修改它,例如:
+
<syntaxhighlight lang="bash">
+
./fw_setenv /dev/sdc bootargs XXX androidboot.selinux=permissive
+
</syntaxhighlight>
+
即可修改为permissive模式,其中上面的XXX需要替换成原来的bootargs值。<br />
+
 
+
2) 更新内核 <br />
+
新版本的uboot在启动时如果识别到LCD,将读取SD卡boot分区的uImage,否则将读取uImage.hdmi。<br />
+
对于Android来说是同一个文件,因此直接使用新编译的uImage来替换SD卡boot分区下的文件即可。<br />
+
对于Debian来说,这2个文件是不相同的,使用新编译的支持LCD的uImage直接替换SD卡boot分区的文件,如果是支持HDMI的内核,则替换uImage.hdmi。<br />
+
 
+
===运行Android或Debian===
+
*将制作好SD卡插入NanoPC-T2,连接HDMI,按住靠近网口的boot按键,最后接电源(5V 2A)拨动开关,NanoPC-T2会从SD卡启动。你可以看到板上红灯常亮,PWR绿灯闪烁,这说明系统已经开始启动了,同时电视上也将能看到系统启动的画面。<br />
+
1)要在电视上进行操作,你需要连接USB鼠标和键盘;如果你选购了LCD配件,则可以直接使用LCD上面的触摸屏进行操作。<br />
+
2)如果您需要进行内核开发,你最好选购一个串口配件,连接了串口,则可以通过终端对NanoPC-T2进行操作。<br />
+
*以下是串口的接法。接上串口,即可调试:
+
[[File:PSU-ONECOM02.png|frameless|400px|PSU-ONECOM02]]
+
*如果提示输入密码,Debian的root用户的默认密码是两个字母fa。
+
 
+
===通过VNC和ssh登录Debian===
+
如果你是祼板运行系统(既没有连接LCD也没有连接HDMI),并且烧写了带 -wifiap.img 后辍的固件,你可以使用手机,或者有无线网卡的电脑连接到NanoPC-T2开放的 nanopi2-wifiap 无线热点(默认密码是123456789),连接成功后,无论是手机还是电脑,你可以到[http://www.realvnc.com/download/ 这里]下载并安装一个名为VNC Viewer的软件,用VNC连接到NanoPC-T2,NanoPC-T2在使用VNC时的连接地址和端口为:192.168.8.1:5901,默认密码为:fa123456,以下是在iPhone上用VNC登录NanoPC-T2的画面:<br />
+
[[File:iphone6-vnc-nanopi2.png|frameless|400px|VNC to NanoPi2]]
+
<br />
+
你也可以通过 ssh -l root 192.168.8.1 命令在终端上登录,默认的root用户密码是 fa。<br />
+
<br />
+
为了保证ssh的流畅,我们用以下命令关闭wifi的省电模式:
+
<syntaxhighlight lang="bash">
+
iwconfig wlan0 power off
+
</syntaxhighlight>
+
 
+
==Debian系统的使用==
+
===连接有线网络===
+
* NanoPC-T2支持千兆网络,Debian或者Android系统在启动前,只要接上网线,系统启动后则会自动分配IP地址,不需要额外去配置。
+
===连接无线网络===
+
;以下针对接了HDMI 或者LCD屏的用户:
+
* 在Debian的图形界面上,点击右下角的网络图标,程序会自动搜索到附近的WiFi热点,找到你需要连接的热点,点击旁边的Properties按钮,输入WiFi密码后保存退出,再点击Connect按钮即可。<br /><br />
+
;以下内容仅适用于祼板运行的用户,即没有接LCD屏也没有接HDMI(使用 -wifiap.img 后辍的固件): <br />系统默认处于无线热点模式,因此无法搜索和连接到无线路由器,需要先退出无线执点模式才可以,请按照如下步骤操作:
+
第一步:我们先把要连接的无线路由器配置好,方法如下:<br />
+
使用ssh连接NanoPC-T2,输入以下命令查询一下WiFi的网络接口,wlan开头的就是WiFi:
+
<syntaxhighlight lang="bash">
+
ifconfig -a
+
</syntaxhighlight>
+
默认情况下是wlan0,你需要在/etc/network/interfaces.d/目录下新建一个与网络接口同名的配置文件 ,以wlan0为例,用vi命令新建以下文件:
+
<syntaxhighlight lang="bash">
+
vi /etc/network/interfaces.d/wlan0
+
</syntaxhighlight>
+
wlan0文件的内容如下:
+
<syntaxhighlight lang="bash">
+
auto wlan0
+
iface wlan0 inet dhcp
+
wpa-driver nl80211
+
wpa-ssid YourWiFiESSID
+
wpa-ap-scan 1
+
wpa-psk YourWiFiPassword
+
</syntaxhighlight>
+
其中,YourWiFiESSID和YourWiFiPassword请替换成你要连接的无线AP名称和密码。<br /><br />
+
如果你的WiFi密码中有特殊字符,或者你不希望明文存放密码,你可以使用wpa_passphrase命令为WiFi密码生成一个密钥(psk),用密钥来代替密码 ,在NanoPC-T2命令行下,可输入以下命令生成密钥: <br />
+
<syntaxhighlight lang="bash">
+
wpa_passphrase YourWiFiESSID
+
</syntaxhighlight>
+
在提示输入密码时,输入你的WiFi密码,然后就会得到类拟以下的内容,其中psk=后面的一串字符就是WiFi的密钥:
+
<syntaxhighlight lang="bash">
+
network={
+
        ssid="YourWiFiESSID"
+
        #psk="YourWiFiPassword"
+
        psk=1b66ca678d6f439f7360686ff5eeb7519cdc44b76a40d96515e4eb807a6d408b
+
}
+
</syntaxhighlight>
+
 
+
最后,我们将上个步骤中生成的密钥替换掉wlan0文件中的密码,如下所示:
+
<syntaxhighlight lang="bash">
+
auto wlan0
+
iface wlan0 inet dhcp
+
wpa-driver nl80211
+
wpa-ssid YourWiFiESSID
+
wpa-ap-scan 1
+
wpa-psk 1b66ca678d6f439f7360686ff5eeb7519cdc44b76a40d96515e4eb807a6d408b
+
</syntaxhighlight>
+
最后一步,使用以下命令退出无线热点模式,需要使用root用户操作,turn-wifi-into-apmode在执行后会重启设备,重启后,会根据上面的配置,自动连接WIFI:
+
<syntaxhighlight lang="bash">
+
su
+
turn-wifi-into-apmode no
+
</syntaxhighlight>
+
 
+
===配置Wi-Fi无线热点===
+
可以通过以下命令,将Wi-Fi切换至无线热点模式:<br />
+
<syntaxhighlight lang="bash">
+
turn-wifi-into-apmode yes
+
</syntaxhighlight>
+
按提示重启即可,默认的热点名称为 nanopi2-wifiap,密码为123456789。<br />
+
<br />
+
现在,你可以在电脑上搜索并连接nanopi2-wifiap这个无线热点,连接成功后,可以通过ssh到192.168.8.1这个地址来登录NanoPC-T2:
+
<syntaxhighlight lang="bash">
+
ssh root@192.168.8.1
+
</syntaxhighlight>
+
在提示输入密码时,输入预设的密码fa,即可登入。<br />
+
<br />
+
为了保证ssh的流畅,我们用以下命令关闭wifi的省电模式:
+
<syntaxhighlight lang="bash">
+
iwconfig wlan0 power off
+
</syntaxhighlight>
+
WiFi工作模式可通过以下命令查询:<br />
+
<syntaxhighlight lang="bash">
+
cat /sys/module/bcmdhd/parameters/op_mode
+
</syntaxhighlight>
+
输出为数字2则表示当前处于无线热点模式,要切换回普通的Station模式,输入如下命令:<br />
+
<syntaxhighlight lang="bash">
+
turn-wifi-into-apmode no
+
</syntaxhighlight>
+
 
+
===使用蓝牙传输===
+
点击右下角的蓝牙图标,会弹出一个操作菜单,其中,<br />
+
Make discoverable菜单项是打开NanoPC-T2蓝牙的可发现属性,这样其他设备(例如手机)就可以搜索到NanoPC-T2并进行配对了; <br />
+
Devices... 菜单项可以打开搜索界面,主动搜索周边的蓝牙设备(注:需要这个设备先打开可发现属性);<br />
+
Send Files to Device...菜单项则可以通过蓝牙发送文件到已配对的指定设备上。<br />
+
 
+
===安装Debian软件包===
+
我们提供的是标准的Debian jessie系统,你可以使用apt-get等命令来安装软件包,如果板子是首次运行,需要先用以下命令更新软件包列表:
+
<syntaxhighlight lang="bash">
+
apt-get update
+
</syntaxhighlight>
+
然后就可以安装软件包了,例如要安装ftp服务器,使用以下命令:
+
<syntaxhighlight lang="bash">
+
apt-get install vsftpd
+
</syntaxhighlight>
+
如果软件包下载速度不理想,你可以编辑 /etc/apt/sources.list 更换一个更快的源服务器,这个网址[http://www.debian.org/mirror/list]有一份完整的源镜像服务器列表,注意要选用一个带armhf架构的。
+
 
+
==如何编译系统==
+
 
+
===安装交叉编译器===
+
首先下载并解压编译器:
+
<syntaxhighlight lang="bash">
+
git clone https://github.com/friendlyarm/prebuilts.git
+
sudo mkdir -p /opt/FriendlyARM/toolchain
+
sudo tar xf prebuilts/gcc-x64/arm-cortexa9-linux-gnueabihf-4.9.3.tar.xz -C /opt/FriendlyARM/toolchain/
+
</syntaxhighlight>
+
 
+
然后将编译器的路径加入到PATH中,用vi编辑vi ~/.bashrc,在末尾加入以下内容:
+
<syntaxhighlight lang="bash">
+
export PATH=/opt/FriendlyARM/toolchain/4.9.3/bin:$PATH
+
export GCC_COLORS=auto
+
</syntaxhighlight>
+
 
+
执行一下~/.bashrc脚本让设置立即在当前shell窗口中生效,注意"."后面有个空格:
+
<syntaxhighlight lang="bash">
+
. ~/.bashrc
+
</syntaxhighlight>
+
 
+
这个编译器是64位的,不能在32位的Linux系统上运行,安装完成后,你可以快速的验证是否安装成功:
+
<syntaxhighlight lang="bash">
+
arm-linux-gcc -v
+
Using built-in specs.
+
COLLECT_GCC=arm-linux-gcc
+
COLLECT_LTO_WRAPPER=/opt/FriendlyARM/toolchain/4.9.3/libexec/gcc/arm-cortexa9-linux-gnueabihf/4.9.3/lto-wrapper
+
Target: arm-cortexa9-linux-gnueabihf
+
Configured with: /work/toolchain/build/src/gcc-4.9.3/configure --build=x86_64-build_pc-linux-gnu
+
--host=x86_64-build_pc-linux-gnu --target=arm-cortexa9-linux-gnueabihf --prefix=/opt/FriendlyARM/toolchain/4.9.3
+
--with-sysroot=/opt/FriendlyARM/toolchain/4.9.3/arm-cortexa9-linux-gnueabihf/sys-root --enable-languages=c,c++
+
--with-arch=armv7-a --with-tune=cortex-a9 --with-fpu=vfpv3 --with-float=hard
+
...
+
Thread model: posix
+
gcc version 4.9.3 (ctng-1.21.0-229g-FA)
+
</syntaxhighlight>
+
 
+
===编译U-Boot===
+
下载U-Boot源代码并编译,注意分支是nanopi2-lollipop-mr1:
+
<syntaxhighlight lang="bash">
+
git clone https://github.com/friendlyarm/uboot_nanopi2.git
+
cd uboot_nanopi2
+
git checkout nanopi2-lollipop-mr1
+
make s5p4418_nanopi2_config
+
make CROSS_COMPILE=arm-linux-
+
</syntaxhighlight>
+
 
+
编译成功结束后您将获得u-boot.bin,您可以通过fastboot来更新正在运行的NanoPC-T2板上SD的U-Boot,方法如下:<br />
+
1) 在电脑上先用命令 sudo apt-get install android-tools-fastboot 安装 fastboot 工具;<br />
+
2) 用串口配件连接NanoPC-T2和电脑,在上电启动的2秒内,在串口终端上按下回车,进入 u-boot 的命令行模式;<br />
+
3) 在u-boot 命令行模式下输入命令 fastboot 回车,进入 fastboot 模式;<br />
+
4) 用microUSB线连接NanoPC-T2和电脑,在电脑上输入以下命令烧写u-boot.bin:<br />
+
<syntaxhighlight lang="bash">
+
fastboot flash bootloader u-boot.bin
+
</syntaxhighlight>
+
<br />
+
注意:您不能直接使用dd来更新SD卡,否则有可能会导致无法正常启动。<br />
+
 
+
===准备mkimage===
+
编译内核需要用到U-Boot中的工具mkimage,因此,在编译内核uImage前,您需要保证您的主机环境可以成功运行它。<br />
+
你可以直接使用命令 sudo apt-get install u-boot-tools 来安装,也可以自己编译并安装:
+
<syntaxhighlight lang="bash">
+
cd uboot_nanopi2
+
make CROSS_COMPILE=arm-linux- tools
+
sudo mkdir -p /usr/local/sbin && sudo cp -v tools/mkimage /usr/local/sbin
+
</syntaxhighlight>
+
 
+
===编译Linux kernel===
+
====编译内核====
+
* 下载内核源代码
+
<syntaxhighlight lang="bash">
+
git clone https://github.com/friendlyarm/linux-3.4.y.git
+
cd linux-3.4.y
+
git checkout nanopi2-lollipop-mr1
+
</syntaxhighlight>
+
NanoPC-T2内核所属的分支是nanopi2-lollipop-mr1,在开始编译前先切换分支。
+
* 编译Android内核
+
<syntaxhighlight lang="bash">
+
make nanopi2_android_defconfig
+
touch .scmversion
+
make uImage
+
</syntaxhighlight>
+
* 编译Debian内核
+
<syntaxhighlight lang="bash">
+
make nanopi2_linux_defconfig
+
touch .scmversion
+
make uImage
+
</syntaxhighlight>
+
编译成功结束后,新生成的内核烧写文件为 arch/arm/boot/uImage,此内核支持HDMI 720p输出,用于替换掉SD卡boot分区下的uImage.hdmi。<br />
+
如果要支持HDMI 1080p,则需要修改内核配置:
+
<syntaxhighlight lang="bash">
+
touch .scmversion
+
make nanopi2_linux_defconfig
+
make menuconfig
+
  Device Drivers -->
+
    Graphics support -->
+
      Nexell Graphics -->
+
        [ ] LCD
+
        [*] HDMI
+
        (0)  Display In  [0=Display 0, 1=Display 1]
+
              Resolution (1920 * 1080p)  --->
+
make uImage
+
</syntaxhighlight>
+
启用LCD,同时取消HDMI,然后退出并保存配置,编译后即可获得支持LCD显示的uImage,用于替换SD卡boot分区下的uImage。
+
 
+
====编译内核模块====
+
Android包含内核模块,位于system分区的 /lib/modules/ 下,如果您有新的内核模块或者内核配置有变化,则需要重新编译。 <br />
+
首先编译内核源代码中的模块:
+
<syntaxhighlight lang="bash">
+
cd linux-3.4.y
+
make CROSS_COMPILE=arm-linux- modules
+
</syntaxhighlight>
+
另外有2个内核模块的源代码位于Android源代码中,可使用以下命令来编译:
+
<syntaxhighlight lang="bash">
+
cd /opt/FriendlyARM/s5p4418/android
+
./vendor/friendly-arm/build/common/build-modules.sh
+
</syntaxhighlight>
+
其中 “/opt/FriendlyARM/s5p4418/android” 是指Android源代码的TOP目录,使用参数“-h”可查看帮助。<br />
+
编译成功结束后,会显示生成的内核模块。
+
 
+
===编译Android===
+
 
+
* 搭建编译环境
+
搭建编译Android的环境建议使用64位的Ubuntu 14.04,安装需要的包即可。
+
<syntaxhighlight lang="bash">
+
sudo apt-get install bison g++-multilib git gperf libxml2-utils make python-networkx zip
+
sudo apt-get install flex libncurses5-dev zlib1g-dev gawk minicom
+
</syntaxhighlight>
+
更多说明可查看 https://source.android.com/source/initializing.html 。
+
 
+
* 下载源代码
+
Android源代码的下载需要使用repo,其安装和使用请查看 https://source.android.com/source/downloading.html 。
+
<syntaxhighlight lang="bash">
+
mkdir android && cd android
+
repo init -u https://github.com/friendlyarm/android_manifest.git -b nanopi2-lollipop-mr1
+
repo sync
+
</syntaxhighlight>
+
其中“android”是指工作目录。
+
 
+
* 编译系统
+
<syntaxhighlight lang="bash">
+
source build/envsetup.sh
+
lunch aosp_nanopi2-userdebug
+
make -j8
+
</syntaxhighlight>
+
编译成功完成后,目录 out/target/product/nanopi2/ 下包含可用于烧写的image文件。
+
 
+
==扩展连接==
+
===NanoPi 2连接USB(FA-CAM202)200万摄像头模块===
+
*NanoPi 2使用Debian系统,假设你已接好LCD屏或者HDMI,进入系统后,点击左下角的菜单键“Other”-->xawtv9,打开USB Camera软件。进入“welcome  to  xawtv!”,选择OK即可进行拍照。
+
[[File:USB-camera-nanopi2.png|frameless|500px|USB camera]]
+
[[File:USB-camera-nanopi2-01.png|frameless|500px|USB camera-01]]
+
===NanoPC-T2连接CMOS 500万摄像头模块===
+
*NanoPi 2使用Android5.1系统,假设你已经接好LCD屏或者HDMI,进入系统后,直接点击“camera”图标,即可打开摄像头进行拍照。
+
[[File:CMOS-camera-nanopi2.png|frameless|500px|CMOS camera]]
+
===NanoPi 2接USB摄像头使用OpenCV===
+
* OpenCV的全称是Open Source Computer Vision Library,是一个跨平台的计算机视觉库。
+
* NanoPi 2跑Debian系统时,接USB Camera,可直接使用官方的OpenCV。<br>
+
1、以下介绍的是NanoPi 2用C++使用的OpenCV:
+
* 首先需要保证你的NanoPi 2能连外网,假如你有串口,直接串口登陆超级终端(或者ssh登陆)。进入系统后,输入用户名(root),密码(fa)登陆;
+
* 以下命令在超级终端执行:
+
<br>
+
<syntaxhighlight lang="bash">
+
apt-get update
+
apt-get install libcv-dev libopencv-dev
+
</syntaxhighlight>
+
 
+
2、NanoPi 2烧写Debian系统启动后,接上USB Camera,使用Debian系统自带的摄像头软件测试,确定摄像头能正常使用。<br>
+
3、通过终端执行命令,查看你的摄像头设备:
+
<syntaxhighlight lang="bash">
+
ls /dev/video*
+
</syntaxhighlight>
+
* 注:video9 是你的USB摄像头设备(注:video0到8均被其它设备占用了)
+
 
+
4、opencv的测试代码(官方C++示例代码)在 /home/fa/Documents/opencv-demo, 使用以下命令即可编译:
+
<syntaxhighlight lang="bash">
+
cd /home/fa/Documents/opencv-demo
+
make
+
</syntaxhighlight>
+
编译成功后,得到可执行文件demo <br />
+
 
+
5、这里特别说明:目前NanoPi 2的内核注册了9个video设备,而opencv的官方源码定义了最多只能使用8个Camera,所以这里需要删掉一个暂时没用到的video,我们把video0设备删掉:
+
<syntaxhighlight lang="bash">
+
rm /dev/video0
+
mv /dev/video9 /dev/video0
+
</syntaxhighlight>
+
 
+
6、以下步骤需要在NanoPi 2上接上键盘执行:
+
<syntaxhighlight lang="bash">
+
./demo
+
</syntaxhighlight>
+
 
+
你便可以看到opencv已经用起来,如图:<br>
+
[[File:OpenCV-01.png|frameless|600px|OpenCV-01]]
+
 
+
==NanoPC-T2 扩展TF卡分区==
+
===NanoPC-T2 Debian系统扩展TF卡分区===
+
* Debian扩展分区,要在pc上执行下列操作:
+
<syntaxhighlight lang="bash">
+
sudo umount /dev/sdx?
+
sudo parted /dev/sdx unit % resizepart 2 100 unit MB print
+
sudo resize2fs -f /dev/sdx2
+
</syntaxhighlight>
+
* Android扩展分区,要在pc上执行下列操作:
+
<syntaxhighlight lang="bash">
+
sudo umount /dev/sdx?
+
sudo parted /dev/sdx unit % resizepart 4 100 resizepart 7 100 unit MB print
+
sudo resize2fs -f /dev/sdx7
+
</syntaxhighlight>
+
(注:/dev/sdx请替换为实际的SD卡设备文件名)
+
 
+
==源代码和固件下载链接==
+
* 烧写固件下载链接:[http://wiki.friendlyarm.com/wiki/nanopi2/download/]
+
* 源代码下载链接:[https://github.com/friendlyarm]
+
 
+
==资源链接==
+
* SEC_Users_Manual_S5P4418_Users_Manual_Preliminary[http://wiki.friendlyarm.com/wiki/images/3/3d/SEC_Users_Manual_S5P4418_Users_Manual_Preliminary_Ver.0.10.pdf]
+
* 原理图([http://wiki.friendlyarm.com/wiki/images/0/00/NanoPC-T2_1601B_Schematic.pdf NanoPC-T2_1601B_Schematic.pdf])
+

Latest revision as of 08:14, 3 July 2024

查看中文

Contents

1 Introduction

Overview
Front
Back
  • The NanoPC-T2 quad core Cortex A9 single board computer is designed and developed by FriendlyARM for professional and enterprise users. It uses the Samsung Quad Core Cortex-A9 S5P4418 SoC with dynamic frequency scaling up to 1.4GHz. Compared to FriendlyARM's existing 4418 based boards the NanoPC-T2 has 8G eMMC onboard, audio jack and video input/output interfaces. Compared to its predecessor the NanoPC-T1 the NanoPC-T2 has built-in WiFi, Bluetooth and Gbps Ethernet port. In addition the NanoPC-T2 has power management which the NanoPC-T1 doesn't support. To avoid overheat issues the NanoPC-T2 has a heat sink with mounting posts.
  • The NanoPC-T2 combines all the ports and interfaces the existing FriendlyARM 4418 boards have. Currently it has the most interfaces and ports among all existing ARM boards of this size. Its rich video interfaces and support for HDMI 1080P enable it to work with not only popular display devices but also various FriendlyARM LCDs (both resistive touch and capacitive touch).
  • The NanoPC-T2 is FriendlyARM's most complete solution based on Samsung 4418 for both commercial and industrial applications.

2 Hardware Spec

  • SoC: Samsung S5P4418 Quad Core Cortex-A9 with dynamic frequency scaling up to 1.4G Hz
  • PMU Power Management: Implemented by an MCU, support solftware power-off, and RTC alarm power-on functions
  • System Memory: 1GB 32bit DDR3 RAM
  • eMMC: 8GB
  • Storage: 1 x SD Card Slot
  • Ethernet: Gbps Ethernet Port (RTL8211E) with unique MAC
  • WiFi: 802.11b/g/n
  • Bluetooth: 4.0 dual mode
  • Antenna: Porcelain Antenna IPX Interface
  • Video Input: DVP Camera/MIPI-CSI (two camera interfaces)
  • Video Output: HDMI Type-A / LVDS / LCD / MIPI DSI (four video output interfaces)
  • Audio: 3.5 mm audio jack / via HDMI
  • Microphone: 1 x onboard Microphone
  • USB: 4 x USB 2.0 Host, two standard type A ports and two 2.54mm pitch pin headers
  • MicroUSB: 1 x MicroUSB 2.0 Client, Type A
  • LCD Interface: 0.5mm pitch 45 pin FPC seat, full color RGB 8-8-8
  • HDMI: 1.4A Type A, 1080P
  • DVP Camera: 0.5mm pitch 24 pin FPC seat
  • GPIO: 2.54 mm pitch 30 pin header
  • Serial Debug Port: 2.54mm pitch 4pin header
  • LED: 1 x power LED , 2 x GPIO LED
  • User Key: 1 x K1 (power), 1 x Reset
  • Other Resource: 1 x onboard thermistor
  • RTC Battery: RTC Seat Pins
  • Power: DC 5V/2A
  • Heat Sink: 1 x Heat Sink with mounting holes
  • PCB: Six Layer, ENIG
  • PCB Dimension: 100 mm x 60 mm
  • Working Temperature: -40℃ to 70℃
  • OS/Software: u-boot, Android 4.4, Android5.1 and Debian8

3 Software Features

3.1 UbuntuCore

  • npi-config: system configuration utility for setting passwords, language, timezone, hostname, SSH and auto-login,and enabling/disabling i2c, spi, serial and PWM
  • networkmanager: manage network
  • system log output from serial port
  • welcome window with basic system information and status
  • auto-login with user account "pi" with access to npi-config
  • UART2 enabled
  • supports CAM500B

3.2 Debian

  • supports CAM500B

3.3 Android

  • supports setting up static IP
  • supports accessing hardware with FriendlyElec's libfriendlyarm-things.so
  • integrated iTest utility for testing hardware

4 Diagram, Layout and Dimension

4.1 Layout

NanoPC-T2 Layout
  • 30Pin GPIO Pin Spec
Pin# Name Pin# Name
1 SYS_3.3V 2 DGND
3 UART2_TX/GPIOD20 4 UART2_RX/GPIOD16
5 I2C0_SCL 6 I2C0_SDA
7 SPI0_MOSI/GPIOC31 8 SPI0_MISO/GPIOD0
9 SPI0_CLK/GPIOC29 10 SPI0_CS/GPIOC30
11 UART3_TX/GPIOD21 12 UART3_RX/GPIOD17
13 UART4_TX/GPIOB29 14 UART4_RX/GPIOB28
15 GPIOB31 16 GPIOB30
17 GPIOC4 18 GPIOC7
19 GPIOC8 20 GPIOC24
21 GPIOC28 22 GPIOB26
23 GPIOD1/PWM0 24 GPIOD8/PPM
25 GPIOC13/PWM1 26 AliveGPIO3
27 GPIOC14/PWM2 28 AliveGPIO5
29 VDD_5V 30 DGND
  • LVDS
Pin# Name
1 VDD_5V
2 VDD_5V
3 VDD_5V
4 LVDS_Y0M
5 LVDS_Y0P
6 DGND
7 LVDS_Y1M
8 LVDS_Y1P
9 DGND
10 LVDS_Y2M
11 LVDS_Y2P
12 DGND
13 LVDS_CLKM
14 LVDS_CLKP
15 DGND
16 LVDS_Y3M
17 LVDS_Y3P
18 DGND
19 GPIOB18
20 DGND
21 I2C2_SCL
22 I2C2_SDA
23 GPIOC16
24 DGND
  • DVP Camera Interface Pin Spec
Pin# Name
1, 2 SYS_3.3V
7,9,13,15,24 DGND
3 I2C0_SCL
4 I2C0_SDA
5 GPIOB14
6 GPIOB16
8 GPIOC13/PWM1
10 NC
11 VSYNC
12 HREF
14 PCLK
16-23 Data bit7-0
  • RGB LCD IF Pin Spec
Pin# Name Description
1, 2 VDD_5V 5V Output, it can be used to power LCD modules
11,20,29, 37,38,39,40, 45 DGND Ground
3-10 Blue LSB to MSB RGB blue
12-19 Green LSB to MSB RGB green
21-28 Red LSB to MSB RGB red
30 GPIOB25 available for users
31 GPIOC15 occupied by FriendlyARM one wire technology to recognize LCD models and control backlight and implement resistive touch, not applicable for users
32 XnRSTOUT Form CPU low when system is reset
33 VDEN signal the external LCD that data is valid on the data bus
34 VSYNC vertical synchronization
35 HSYNC horizontal synchronization
36 LCDCLK LCD clock, Pixel frequency
41 I2C2_SCL I2C2 clock signal, for capacitive touch data transmission
42 I2C2_SDA I2C2 data signal, for capacitive touch data transmission
43 GPIOC16 interrupt pin for capacitive touch, used with I2C2
44 NC Not connected
  • MIPI-DSI Interface Pin Spec
Pin# Name
1, 2, 3 VDD_5V
4 DGND
5 I2C2_SDA
6 I2C2_SCL
7 DGND
8 GPIOC16
9 DGND
10 GPIOC1
11 DGND
12 GPIOA28
13 nRESETOUT
14, 15 DGND
16 MIPIDSI_DN3
17 MIPIDSI_DP3
18 DGND
19 MIPIDSI_DN2
20 MIPIDSI_DP2
21 DGND
22 MIPIDSI_DN1
23 MIPIDSI_DP1
24 DGND
25 MIPIDSI_DN0
26 MIPIDSI_DP0
27 DGND
28 MIPIDSI_DNCLK
29 MIPIDSI_DPCLK
30 DGND
  • MIPI-CSI Interface Pin Spec
Pin# Name
1, 2 SYS_3.3V
3 DGND
4 I2C0_SDA
5 I2C0_SCL
6 DGND
7 SPI2_MOSI/GPIOC12
8 SPI2_MISO/GPIOC11
9 SPI2_CS/GPIOC10
10 SPI2_CLK/GPIOC9
11 DGND
12 GPIOB23
13 GPIOC2
14 GPIOC13/PWM1
15 DGND
16 MIPICSI_DN3
17 MIPICSI_DP3
18 DGND
19 MIPICSI_DN2
20 MIPICSI_DP2
21 DGND
22 MIPICSI_DN1
23 MIPICSI_DP1
24 DGND
25 MIPICSI_DN0
26 MIPICSI_DP0
27 DGND
28 MIPICSI_DNCLK
29 MIPICSI_DPCLK
30 DGND
Note:
  1. SYS_3.3V: 3.3V power output
  2. VDD_5V: 5V power output
  3. For more details refer to the document: NanoPC-T2-T3-Schematic.pdf

4.2 Board Dimension

NanoPC-T2 Dimensions

For more details refer to the document: NanoPC-T2-T3_1711_Draw_dxf.zip
  • Power Jack
  • DC 4.7~5.6V IN, 4.0*1.7mm Power Jack
DC-023.png

5 Notes in Hardware Design

5.1 EEPROM

  • The board has an EEPROM(model: 24AA025E48T-I/OT) with a unique MAC. This EEPROM is connected to I2C0 and its address is 0x51 therefore some EEPROM chips cannot be connected to I2C0 which will cause conflicts of addresses.
  • In our tests these EEPROM chips cannot be connected to I2C0: 24C04, 24C08 and 24C16. There chips which we tested can be connected to I2C0: 24C01, 24C02 and 24C256
  • For more details about EEPROM address issues refer to http://www.onsemi.com/pub_link/Collateral/CAT24C01-D.PDF

6 Get Started

6.1 Essentials You Need

Before starting to use your NanoPC-T2 get the following items ready

  • NanoPC-T2
  • SD Card: Class 10 or Above, minimum 8GB SDHC
  • A DC 5V/2A power is a must
  • HDMI monitor or LCD
  • USB keyboard, mouse and possible a USB hub(or a TTL to serial board)
  • A host computer running Ubuntu 18.04 64 bit system

6.2 Boot from SD Card

Get the following files from here download link:

  • Get a 8G SDHC card and backup its data if necessary.
Image Files
s5p4418-sd-friendlycore-xenial-4.4-armhf-YYYYMMDD.img.zip FriendlyCore with Qt 5.10.0 (base on Ubuntu core) image file
s5p4418-sd-lubuntu-desktop-xenial-4.4-armhf-YYYYMMDD.img.zip LUbuntu Desktop image file with X Window
s5p4418-sd-friendlywrt-4.4-YYYYMMDD.img.zip FriendlyWrt image file (base on OpenWrt)
s5p4418-sd-android7-YYYYMMDD.img.zip Android7 image file
s5p4418-sd-android-kitkat-YYYYMMDD.img.zip Android4.4 image file with support for 4G LTE
s5p4418-sd-android-lollipop-YYYYMMDD.img.zip Android5.1 image file
s5p4418-eflasher-lubuntu-desktop-xenial-4.4-armhf-YYYYMMDD.img.zip SD card image, which is used to install a lubuntu desktop to eMMC
s5p4418-eflasher-friendlywrt-4.4-YYYYMMDD.img.zip SD card image, which is used to install a FriendlyWrt to eMMC
s5p4418-eflasher-android7-YYYYMMDD.img.zip SD card image, which is used to install a android7 to eMMC
s5p4418-eflasher-friendlycore-xenial-4.4-armhf-YYYYMMDD.img.zip SD card image, which is used to install a friendly-core to eMMC
s5p4418-eflasher-android-kitkat-YYYYMMDD.img.zip SD card image, which is used to install a android4 to eMMC
s5p4418-eflasher-android-lollipop-YYYYMMDD.img.zip SD card image, which is used to install a android5 to eMMC
Flash Utility:
win32diskimager.rar Windows utility. Under Linux users can use "dd"
  • Uncompress these files. Insert an SD card(at least 4G) into a Windows PC and run the win32diskimager utility as administrator. On the utility's main window select your SD card's drive, the wanted image file and click on "write" to start flashing the SD card.
  • Insert this card into your board's boot slot, press and hold the boot key (only applies to a board with onboard eMMC) and power on (with a 5V/2A power source). If the PWR LED is on and LED1 is blinking this indicates your board has successfully booted.

6.3 Flash image to eMMC with eflasher

  • Download eflasher image file

An image file's name is as : s5p4418-eflasher-OSNAME-YYYYMMDD.img.zip
The "OSNAME" is the name of an OS e.g. android, friendlycore and etc;
This image file is used for making an installation SD card and it contains a Ubuntu core system and a utility EFlasher;
Download s5p4418-eflasher-OSNAME-YYYYMMDD.img.zip to a host PC and get a windows utility win32diskimager.rar as well;

  • Make Installation SD Card with eflasher

Extract the package with a 7z utility and you will get a file with an extension ".img". Insert an SDHC card(minimum 8G or above) to a PC running Windows, run the Win32DiskImager utility as administrator, click on "Image File" to select your wanted file, select your SD card and click on "Write" to start flashing the Image to your SD card;
If your PC runs Linux you can command "dd" to extract the package and get an ".img" file and write it to your SD card;

  • Operate in GUI Window: Flash OS to eMMC

Insert your SD card to NanoPC-T2, connect an HDMI monitor or LCD to your board, press and hold the "boot" key beside the Ethernet port, power on the board you will see a pop-up window asking you to select an OS for installation. Select your wanted OS and start installation.

  • Operate in Commandline Utility: Flash OS to eMMC

Insert an installation SD card to NanoPC-T2, log into or SSH to your board and run the following command to start EFlasher:

sudo eflasher

6.3.1 Make Installation Card under Linux Desktop

  • 1) Insert your SD card into a host computer running Ubuntu and check your SD card's device name
dmesg | tail

Search the messages output by "dmesg" for similar words like "sdc: sdc1 sdc2". If you can find them it means your SD card has been recognized as "/dev/sdc". Or you can check that by commanding "cat /proc/partitions"

  • 2) Downlaod Linux script

git clone https://github.com/friendlyarm/sd-fuse_s5p4418.git
cd sd-fuse_s5p4418

  • 3) Here is how to make a Lubuntu desktop SD card
sudo ./fusing.sh /dev/sdx lubuntu

(Note: you need to replace "/dev/sdx" with the device name in your system)
When you run the script for the first time it will prompt you to download an image you have to hit “Y” within 10 seconds otherwise you will miss the download

  • 4) Run this command to make a complete image file:
sudo ./mkimage.sh lubuntu

More content please refre: Assembling the SD card image yourself

6.4 Extend SD Card Section

  • When Debian/Ubuntu is loaded the SD card's section will be automatically extended.
  • When Android is loaded you need to run the following commands on your host PC to extend your SD card's section:
sudo umount /dev/sdx?
sudo parted /dev/sdx unit % resizepart 4 100 resizepart 7 100 unit MB print
sudo resize2fs -f /dev/sdx7

(Note: you need to replace "/dev/sdx" with the device name in your system)

6.5 LCD/HDMI Resolution

When the system boots our uboot will check whether it is connected to an LCD or to an HDMI monitor. If it recognizes an LCD it will configure its resolution. Our uboot defaults to the HDMI 720P configuration.
If you want to modify the LCD resolution you can modify file "arch/arm/plat-s5p4418/nanopi2/lcds.c" in the kernel and recompile it.
If your NanoPC-T2 is connected to an HDMI monitor and it runs Android it will automatically set the resolution to an appropriate HDMI mode by checking the "EDID". If your NanoPC-T2 is connected to an HDMI monitor and it runs Debian by default it will set the resolution to the HDMI 720P configuration. If you want to modify the HDMI resolution to 1080P modify your kernel's configuration as explained above.

6.6 Update SD Card's boot parameters From PC Host

Insert your SD card into a host PC running Linux, if you want to change your kernel command line parameters you can do it via the fw_setevn utility.
Check the current Command Line:

git clone https://github.com/friendlyarm/sd-fuse_s5p4418.git
cd sd-fuse_s5p4418/tools
./fw_printenv /dev/sdx | grep bootargs

For example, to disable android SELinux, You can change it this way:

./fw_setenv /dev/sdc bootargs XXX androidboot.selinux=permissive

The "XXX" stands for the original bootargs' value.

6.7 Run Android or Linux (TODO)

  • 将制作好SD卡插入NanoPC-T2,连接HDMI,按住靠近网口的boot按键,最后接电源(5V 2A)拨动开关,NanoPC-T2会从SD卡启动。你可以看到板上PWR灯常亮,LED1灯闪烁,这说明系统已经开始启动了,同时电视上也将能看到系统启动的画面。
  • 要在电视上进行操作,你需要连接USB鼠标和键盘;如果你选购了LCD配件,则可以直接使用LCD上面的触摸屏进行操作。

7 Work with FriendlyCore

7.1 Introduction

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

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

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

7.2 System Login

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

For example, NanoPi-M1:
PSU-ONECOM-M1.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:
For example, NanoPi-NEO2:
USB2UART-NEO2.jpg

  • FriendlyCore User Accounts:

Non-root User:

   User Name: pi
   Password: pi

Root:

   User Name: root
   Password: fa

The system is automatically logged in as "pi". You can do "sudo npi-config" to disable auto login.

  • Update packages
$ sudo apt-get update

7.3 Configure System with npi-config

The npi-config is a commandline utility which can be used to initialize system configurations such as user password, system language, time zone, Hostname, SSH switch , Auto login and etc. Type the following command to run this utility.

$ sudo npi-config

Here is how npi-config's GUI looks like:
npi-config

7.4 Develop Qt Application

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

7.5 Setup Program to AutoRun

You can setup a program to autorun on system boot with npi-config:

sudo npi-config

Go to Boot Options -> Autologin -> Qt/Embedded, select Enable and reboot.

7.6 Extend TF Card's Section

When FriendlyCore is loaded the TF card's section will be automatically extended.You can check the section's size by running the following command:

$ df -h

7.7 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

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

7.9 Setup Wi-Fi AP

Follow the steps below. Since our OS image by default already has the NetworkManager utility you will be prompted to uninstall it first:

sudo turn-wifi-into-apmode yes

After you uninstall the NetworkManager reboot your board.
After your board is rebooted run the above commands again and you will be prompted to type in a WIFI's name and password. Type in your wanted name and password

If this is successful you will be able to find and connect your board to a WIFI. Login to your board at 192.168.8.1:

ssh root@192.168.8.1

Type in a password. In our system the password is "fa".

To login smoothly via SSH we recommend you turning off WIFI's power save mode by running the following commands:

sudo iwconfig wlan0 power off

You can check your WiFi's mode by running the following command:

sudo cat /sys/module/bcmdhd/parameters/op_mode

Number 2 means your WiFi is in AP mode. You can switch to the Station mode by running the following command:

sudo turn-wifi-into-apmode no

7.10 Bluetooth

Search for surrounding bluetooth devices by running the following command:

$ su root
$ hciconfig hci0 up
$ hcitool scan

You can run "hciconfig" to check bluetooth's status.

7.11 Ethernet Connection

If a board is connected to a network via Ethernet before it is powered on it will automatically obtain an IP with DHCP activated after it is powered up. If you want to set up a static IP refer to: Use NetworkManager to configure network settings


7.12 Custom welcome message

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

/etc/update-motd.d/

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

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

To:

TERM=linux toilet -f standard -F metal HELLO

7.13 Modify timezone

For exampe, change to Shanghai timezone:

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

7.14 Select the system default audio device

You can set the system default audio device by following the steps below.
Use the following command to view all the sound card devices in the system (Note: different development boards will have different results):

pi@NanoPi:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: nanopi2audio [nanopi2-audio], device 0: c0055000.i2s-ES8316 HiFi ES8316 HiFi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: nanopi2audio [nanopi2-audio], device 1: c0059000.spdiftx-dit-hifi dit-hifi-1 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

As you can see, the following sound card devices are available on the hardware:

Sound card device Sound card number Description
nanopi2audio device 0 3.5mm jack interface
nanopi2audio device 1 HDMI

To configure the audio output to the 3.5mm jack, create or modify the configuration file /etc/asound.conf and modify it to the following:

pcm.!default {
    type hw
    card 0
    device 0
}
 
ctl.!default {
    type hw
    card 0
}

To configure to output audio to HDMI, change the device 0 above to device 1.


7.15 Run the X11 application

FriendlyCore system built-in lightweight Xorg,although there is no window manager, you can still run a single X-Windows application,For example, the program to run is ~/YourX11App,use the following command:

. /usr/bin/setqt5env-xcb
startx ~/YourX11App -geometry 1280x800

Note that there is a space between "." and /usr/bin/setqt5env-xcb. In addition, the resolution after -geometry should be changed to the actual resolution of your screen.

7.16 Run Qt 5.10.0 Demo with GPU acceleration

Run the following command

$ sudo qt5demo

S5pxx18-QtE

7.17 Run Qt 5.10.0 Demo with OpenGL

Run the following command

. setqt5env
cd $QTDIR
cd /examples/opengl/qopenglwidget
./qopenglwidget

For more Qt 5.10.0 examples, please go to:
cd $QTDIR/examples/

7.18 Play HD Video with Hardware-decoding

gst-player is console player, it base on GStreamer, support VPU with Hardware-decoding:

sudo gst-player /home/pi/demo.mp4

The equivalent gsteamer command is as follows:

sudo gst-launch-1.0 filesrc location=/home/pi/demo.mp4 ! qtdemux name=demux demux. ! queue ! faad ! audioconvert ! audioresample ! alsasink device="hw:0,DEV=1" demux. ! queue ! h264parse ! nxvideodec ! nxvideosink dst-x=0 dst-y=93 dst-w=1280 dst-h=533

7.19 Connect to DVP Camera CAM500B

The CAM500B camera module is a 5M-pixel camera with DVP interface. For more tech details about it you can refer to Matrix - CAM500B.
Enter the following command to preview the video:

gst-launch-1.0 -e v4l2src device=/dev/video6 ! video/x-raw,format=I420,framerate=30/1,width=1280,height=720 ! nxvideosink

Enter the following command to start recording (VPU hardware encoding):

gst-launch-1.0 -e v4l2src device=/dev/video6 ! video/x-raw,format=I420,framerate=30/1,width=1280,height=720 ! tee name=t t. \
 ! queue ! nxvideosink t. ! queue ! nxvideoenc bitrate=12000000 ! mp4mux ! \
 filesink location=result_720.mp4

7.20 Power Off and Schedule Power On

“PMU Power Management” feature helps us to auto power on the board at a specific time, it is implemented by an MCU, support software power-off, and RTC alarm power-up functions.

Here’s a simple guide:
Turn on automatically after 100 seconds. (Time must be greater than 60 seconds.):

$ sudo echo 100 > /sys/class/i2c-dev/i2c-3/device/3-002d/wakealarm

After setting up the automatic boot, turn off board with the 'poweroff’ command:

$ sudo poweroff

Cancel automatic boot:

$ sudo echo 0 > /sys/class/i2c-dev/i2c-3/device/3-002d/wakealarm

Query the current settings, in the front is current time, followed by the time of automatic booting: If no automatic boot is set, it will display "disabled”.

$ sudo cat /sys/class/i2c-dev/i2c-3/device/3-002d/wakealarm


Note that some older versions of hardware may not support this feature, if you don't see this file node in your system:
/sys/class/i2c-dev/i2c-3/device/3-002d/wakealarm
your board may be it does not support this feature.

7.21 Installing and Using OpenCV 4.1.2

OpenCV has been pre-installed in FriendlyCore (Version after 20191126) and does not require manual installation.
Please refre this link: https://github.com/friendlyarm/install-opencv-on-friendlycore/blob/s5pxx18/README.md
Quick test:

. /usr/bin/cv-env.sh
. /usr/bin/setqt5env-eglfs
cd /usr/local/share/opencv4/samples/python
python3 turing.py

7.22 Installing and Using Caffe

git clone https://github.com/friendlyarm/install-caffe-on-friendlycore
cd install-caffe-on-friendlycore
sudo ./install-caffe.sh

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

7.23.1 How to Install Docker

Run the following commands:

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

7.23.2 Test Docker installation

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

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

8 Work with Android

8.1 Work with 4G Module EC20 under Android5

8.1.1 Hardware Setup

Connect an EC20 module to a USB to miniPCIe board and connect the board to an ARM board's USB Host. Here is a hardware setup:
T2-4G-EC20.jpg
Power on the board and you will be able to surf the internet with the 4G module like using an Android phone.


Replace the logo.bmp:

/opt/FriendlyARM/smart4418/android/device/friendly-arm/nanopi3/boot/logo.bmp
/opt/FriendlyARM/smart4418/android/device/friendly-arm/nanopi2/boot/logo.bmp

Replace the bootanimation.zip:

/opt/FriendlyARM/smart4418/android/device/friendly-arm/nanopi3/bootanimation.zip
/opt/FriendlyARM/smart4418/android/device/friendly-arm/nanopi2/bootanimation.zip

Re-compile android.

8.3 Use fastboot command to flash android firmware

Enter the uboot command line mode on the serial terminal when powering on, and then enter the following command:

fastboot 0

For S5P4418:

fastboot flash partmap partmap.txt
fastboot flash 2ndboot bl1-mmcboot.bin
fastboot flash fip-loader loader-mmc.img
fastboot flash fip-secure bl_mon.img
fastboot flash fip-nonsecure bootloader.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img

For S5P6818:

fastboot flash partmap partmap.txt
fastboot flash 2ndboot bl1-mmcboot.bin
fastboot flash fip-loader fip-loader.img 
fastboot flash fip-secure fip-secure.img 
fastboot flash fip-nonsecure fip-nonsecure.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img

8.4 Android Keys

Android 5:

  vendor/friendly-arm/nanopi3/security/

Android 7:

  build/target/product/security/

8.5 Optimizing HDMI Performance on Android 7

8.5.1 Note

By default, the driver initializes two framebuffers, one for the primary LCD display and the other for HDMI. If your project specifically requires the use of HDMI and not the LCD, you can follow the steps outlined in this chapter to make modifications. After making these changes, HDMI will be configured as the primary display, resulting in the initialization of only one framebuffer. This optimization conserves resources and leads to corresponding improvements in UI performance and boot speed.
The content of this chapter is applicable exclusively to S5P6818 running Android 7. For S5P4418, the modification process is similar, with adjustments needed in the corresponding files.

8.5.2 Modify the kernel

You need to modify the kernel Device Tree Source (DTS) to disable the dp_drm_lvds node, as shown below:

--- a/arch/arm64/boot/dts/nexell/s5p6818-nanopi3-common.dtsi
+++ b/arch/arm64/boot/dts/nexell/s5p6818-nanopi3-common.dtsi
@@ -810,6 +810,7 @@
                        plane-names = "video", "rgb", "primary";
                };
                port@1 {
+                       status = "disabled";
                        reg = <1>;
                        back_color = < 0x0 >;
                        color_key = < 0x0 >;
@@ -820,7 +821,7 @@
 
 &dp_drm_lvds {
        remote-endpoint = <&lcd_panel>;
-       status = "ok";
+       status = "disabled";
 
        display-timing {
                clock-frequency = <50000000>;

After compilation, you will obtain a new arch/arm64/boot/dts/nexell/s5p6818-nanopi3-rev*.dtb file.
During the testing phase, you can directly update it to the board using adb with the following command:

adb root; adb wait-for-device; adb shell mkdir /storage/sdcard1/; adb
shell mount -t ext4 /dev/block/mmcblk0p1 /storage/sdcard1/
adb push arch/arm64/boot/dts/nexell/s5p6818-nanopi3-rev*.dtb /storage/sdcard1/

For a complete firmware update, you will need to replace the files in the device/friendlyelec/nanopi3/boot directory of the Android 7 source code.

8.5.3 Modify env.conf

To modify the device/friendlyelec/nanopi3/boot/env.conf file and add a line

lcdtype     HDMI1080P60

This mode needs to match the mode detected by Android 7 after startup; otherwise, it may result in a prolonged black screen state or even no display output. In such cases, you may need to manually set it in the U-Boot command-line environment:

setenv lcdtype HDMI1080P60; saveenv; reset

8.5.4 Modify system.prop

To modify the device/friendlyelec/nanopi3/system.prop file in Android 7

ro.sf.lcd_density=240

Alternatively, you can adjust the system property or experiment with different values that you deem more appropriate. You can also use the following command to change the display density under the serial or adb environment and observe if the effect is suitable:

adb shell wm density 240

8.5.5 Compiling Android

Follow the instructions in the wiki to compile Android 7 and conduct testing. If you encounter any exceptions, please carefully review the preceding steps.

9 More OS Support

9.1 DietPi

Dietpi-logo.png
DietPi is a highly optimised & minimal Debian-based Linux distribution. DietPi is extremely lightweight at its core, and also extremely easy to install and use.
Setting up a single board computer (SBC) or even a computer, for both regular or server use, takes time and skill. DietPi provides an easy way to install and run favourite software you choose.
For more information, please visit this link https://dietpi.com/docs/.

DietPi supports many of the NanoPi board series, you may download the image file from here:

10 Make Your Own OS Image

10.1 Install Cross Compiler

10.1.1 Install arm-linux-gcc 4.9.3

Download the compiler package:

git clone https://github.com/friendlyarm/prebuilts.git -b master --depth 1
cd prebuilts/gcc-x64
cat toolchain-4.9.3-armhf.tar.gz* | sudo tar xz -C /

Then add the compiler's directory to "PATH" by appending the following lines in "~/.bashrc":

export PATH=/opt/FriendlyARM/toolchain/4.9.3/bin:$PATH
export GCC_COLORS=auto

Execute "~/.bashrc" to make the changes take effect. Note that there is a space after the first ".":

. ~/.bashrc

This compiler is a 64-bit one therefore it cannot be run on a 32-bit Linux machine. After the compiler is installed you can verify it by running the following commands:

arm-linux-gcc -v
Using built-in specs.
COLLECT_GCC=arm-linux-gcc
COLLECT_LTO_WRAPPER=/opt/FriendlyARM/toolchain/4.9.3/libexec/gcc/arm-cortexa9-linux-gnueabihf/4.9.3/lto-wrapper
Target: arm-cortexa9-linux-gnueabihf
Configured with: /work/toolchain/build/src/gcc-4.9.3/configure --build=x86_64-build_pc-linux-gnu
--host=x86_64-build_pc-linux-gnu --target=arm-cortexa9-linux-gnueabihf --prefix=/opt/FriendlyARM/toolchain/4.9.3
--with-sysroot=/opt/FriendlyARM/toolchain/4.9.3/arm-cortexa9-linux-gnueabihf/sys-root --enable-languages=c,c++
--with-arch=armv7-a --with-tune=cortex-a9 --with-fpu=vfpv3 --with-float=hard
...
Thread model: posix
gcc version 4.9.3 (ctng-1.21.0-229g-FA)

10.2 Compile Linux kernel for FriendlyCore/Lubuntu/EFlasher

10.2.1 Compile Kernel

  • Download Kernel Source Code
git clone https://github.com/friendlyarm/linux.git -b nanopi2-v4.4.y --depth 1
cd linux

The NanoPC-T2's kernel source code is in the "nanopi2-v4.4.y" branch.You need to switch to this branch.

  • Compile Ubuntu Kernel
touch .scmversion
make ARCH=arm nanopi2_linux_defconfig
make ARCH=arm

After your compilation succeeds an "arch/arm/boot/zImage" will be generated and a DTB file(s5p4418-nanopi2-rev*.dtb) will be generated in the "arch/arm/boot/dts/" directory. You can use them to replace the existing zImage and DTB files in the boot partition of your bootable SD card.

10.2.2 Use Your Generated Kernel

  • Update kernel in SD card

If you use an SD card to boot Ubuntu you can copy your generated zImage and DTB files to your SD card's boot partition(e.g. partition 1 /dev/sdX1).

  • Update kernel in eMMC

If you boot your board from eMMC you can update your kernel file by following the steps below:
1) Usually after OS is loaded eMMC's boot partition (in our example eMMC's device name was /dev/mmcblk0p1) will be automatically mounted and you can verify that by running "mount"
2) Connect your board to a host PC running Ubuntu and copy the zImage and DTB files to eMMC's boot partition
3) Or you can copy your generated kernel file to an external storage card(e.g. an SD card or a USB drive), connect the storage card to your board the move the file from the card to eMMC's boot partition
4) After update is done type "reboot" to reboot your board. Note: don't just directly disconnect your board from its power source or press the reset button to reboot the board. These actions will damage your kernel file

  • Generate Your boot.img

Refer to this repo: https://github.com/friendlyarm/sd-fuse_s5p4418

10.3 Compile Linux kernel for Android7

The Android 7.1.2 source code already contains the pre-compiled kernel. If you need to customize it, you can compile the kernel according to the following guide.

git clone https://github.com/friendlyarm/linux.git -b nanopi2-v4.4.y --depth 1
cd linux
touch .scmversion
make ARCH=arm nanopi2_nougat_defconfig
make ARCH=arm

The newly generated kernel is arch/arm/boot/zImage,The new DTB file is also included under the directory arch/arm/boot/dts/.(s5p4418-nanopi2-rev*.dtb).
If you only want to debug the kernel, you can quickly update it with adb:

adb root; adb shell mkdir /storage/sdcard1/; adb shell mount -t ext4 /dev/block/mmcblk0p1 /storage/sdcard1/;
adb push arch/arm/boot/zImage arch/arm/boot/dts/s5p4418-nanopi2-rev*.dtb /storage/sdcard1/

If you want to generate boot.img for burning, you can copy the kernel zImage and DTB files to the Android7 source code directory: device/friendlyelec/nanopi2/boot, then recompile Android7.

10.4 Compile U-Boot for Android7/FriendlyCore/Lubuntu/EFlasher

Download the U-Boot source code and compile it. Note that the github's branch is nanopi2-v2016.01:

git clone https://github.com/friendlyarm/u-boot.git 
cd u-boot
git checkout nanopi2-v2016.01
make s5p4418_nanopi2_defconfig
make CROSS_COMPILE=arm-linux-

After your compilation succeeds a bootloader.img will be generated. If you want to test it flash it to your installation SD card to replace an existing U-Boot v2016.01 file via fastboot, sd-fuse_s5p4418 or eflasher ROM.
For Android7: Copy bootloader.img to Android7 source directory device/friendlyelec/nanopi2/boot, then recompile Android7.
Note: you cannot use mixed U-Boot files. For example you cannot use fastboot to update an existing U-Boot V2014.07 and you cannot use bootloader.img to replace an existing u-boot.bin

10.5 Compile Android 7.1.2

10.5.1 Install Cross Compiler

Install 64 bit Ubuntu 16.04 on your host PC.

sudo apt-get install bison g++-multilib git gperf libxml2-utils make python-networkx zip
sudo apt-get install flex curl libncurses5-dev libssl-dev zlib1g-dev gawk minicom
sudo apt-get install openjdk-8-jdk
sudo apt-get install exfat-fuse exfat-utils device-tree-compiler liblz4-tool

For more details refer to https://source.android.com/source/initializing.html

10.5.2 Download Android7 Source Code

There are two ways to download the source code:

  • repo archive file on netdisk

Netdisk URL: Click here
File location on netdisk:sources/s5pxx18-android-7.git-YYYYMMDD.tar (YYYYMMDD means the date of packaging)
After extracting the repo package from the network disk, you need to execute the sync.sh script, which will pull the latest code from gitlab:

tar xvf /path/to/netdisk/sources/s5pxx18-android-7.git-YYYYMMDD.tar
cd s5pxx18-android-7
./sync.sh
  • git clone from gitlab

NanoPC-T2 source code is maintained in gitlab, You can download it by running the following command:

git clone https://gitlab.com/friendlyelec/s5pxx18-android-7.git -b master

10.5.3 Compile Android7

cd s5pxx18-android-7
source build/envsetup.sh
lunch aosp_nanopi2-userdebug
make -j8

After your compilation succeeds the following files will be generated in the "out/target/product/nanopi2/" directory.

filename partition Description
bl1-mmcboot.bin raw boot firmware
loader-mmc.img raw boot firmware
bl_mon.img raw boot firmware
bootloader.img raw uboot-v2016.01
env.conf - Uboot environment variable containing Android kernel command line parameters
boot.img boot kernel zImage, DTBs; logo; Android ramdisk
cache.img cache -
userdata.img userdata -
system.img system -
partmap.txt - Partition description file

11 Build Kernel Headers Package

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

11.1 Software Version

The OS image file name: s5p4418-sd-friendlycore-xenial-4.4-armhf-YYYYMMDD.img, s5p4418-eflasher-friendlycore-xenial-4.4-armhf-YYYYMMDD.img

pi@NanoPC-T2:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.6 LTS
Release:        16.04
Codename:       xenial
pi@NanoPC-T2:~$ cat /proc/version
Linux version 4.4.172-s5p4418 (root@jensen) (gcc version 7.5.0 (ctng-1.24.0-108g-FA) ) #1 SMP PREEMPT Wed Mar 24 15:17:25 CST 2021

11.2 Install the required packages

sudo apt-get update
sudo apt-get install -y dpkg-dev bsdtar

11.3 Build Kernel Headers Package

git clone https://github.com/friendlyarm/linux -b nanopi2-v4.4.y --depth 1 kernel-s5pxx18-arm
cd kernel-s5pxx18-arm
rm -rf .git
make distclean
touch .scmversion
make CROSS_COMPILE= ARCH=arm nanopi2_linux_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-firmware-image-4.4.172-s5p4418' in '../linux-firmware-image-4.4.172-s5p4418_4.4.172-s5p4418-1_armhf
.deb'.
dpkg-deb: building package 'linux-headers-4.4.172-s5p4418' in '../linux-headers-4.4.172-s5p4418_4.4.172-s5p4418-1_armhf.deb'.
dpkg-deb: building package 'linux-libc-dev' in '../linux-libc-dev_4.4.172-s5p4418-1_armhf.deb'.
dpkg-deb: building package 'linux-image-4.4.172-s5p4418' in '../linux-image-4.4.172-s5p4418_4.4.172-s5p4418-1_armhf.deb'.
dpkg-genchanges: binary-only upload (no source code included)

12 Installation=

sudo rm -f /lib/modules/4.4.172-s5p4418/build
sudo rm -f /lib/modules/4.4.172-s5p4418/source
sudo dpkg -i ../linux-headers-4.4.172-s5p4418_4.4.172-s5p4418-1_armhf.deb

12.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 CROSS_COMPILE=

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

sudo insmod ./pf_ring.ko

13 Connect NanoPC-T2 to External Modules

13.1 Connect NanoPC-T2 to USB Camera(FA-CAM202)

  • In this use case the NanoPC-T2 runs Debian. If you connect your NanoPC-T2 to our LCD or an HDMI monitor after Debain is fully loaded click on "other"-->"xawtv" on the left bottom of the GUI and the USB Camera application will be started. After enter "welcome to xawtv!" click on "OK" to start exploring.

USB camera USB camera-01

13.2 Connect NanoPC-T2 to CMOS 5M-Pixel Camera

For more details about the CAM500A camera refer to [1]

  • If your NanoPC-T2 runs Android5.1 and it is connected to our LCD or an HDMI monitor after Android is fully loaded click on the "Camera" icon and the application will be started. You can take pictures or record videos

CMOS camera

  • Under Debian a camera utility "nanocams" is available for previewing 40 frames and picture taking. You can try it by following the commands below
sudo nanocams -p 1 -n 40 -c 4 -o IMG001.jpg

For more details about the usage of the nanocams run "nanocams -h". You can get its source code from our git hub:

git clone https://github.com/friendlyarm/nexell_linux_platform.git
  • Under FriendlyCore (kernel 4.4), You can try it by following the commands below:

Enter the following command to preview the video:

gst-launch-1.0 -e v4l2src device=/dev/video6 ! video/x-raw,format=I420,framerate=30/1,width=1280,height=720 ! nxvideosink

Enter the following command to start recording (VPU hardware encoding):

gst-launch-1.0 -e v4l2src device=/dev/video6 ! video/x-raw,format=I420,framerate=30/1,width=1280,height=720 ! tee name=t t. \
 ! queue ! nxvideosink t. ! queue ! nxvideoenc bitrate=12000000 ! mp4mux ! \
 filesink location=result_720.mp4

13.3 Use OpenCV to Access USB Camera

  • The full name of "OpenCV" is Open Source Computer Vision Library and it is a cross platform vision library.
  • When the NanoPC-T2 runs Debian users can use OpenCV APIs to access a USB Camera device.

1. Here is a guideline on how to use OpenCV with C++ on the NanoPC-T2:

  • Firstly you need to make sure your NanoPC-T2 is connected to the internet.Login to your NanoPC-T2 via a serial terminal or SSH. After login type in your username(root) and password(fa):
  • Run the following commands:


apt-get update
apt-get install libcv-dev libopencv-dev

2. Make sure your USB camera works with the NanoPC-T2. You can test your camera with NanoPC-T2's camera utility.

3. Check your camera device:

ls /dev/video*
  • Note:in our test case video0 was the device name.

4. OpenCV's code sample(official code in C++) is under /home/fa/Documents/opencv-demo. Compile the code sample with the following commands:

cd /home/fa/Documents/opencv-demo
make

After it is compiled successfully a "demo" executable will be generated

5. Connect NanoPC-T2 to USB Keyboard & Run the Following Command:

./demo

opencv is successfully started

13.4 Connect NanoPC-T2 to Matrix GPS Module

  • The Matrix-GPS module is a small GPS module with high performance. It can be used in navigation devices, four-axle drones and etc.
  • The Matrix-GPS module uses serial communication. When the NanoPC-T2 is connected to the Matrix GPS module, after the NanoPC-T2 is powered up type in the following command in a terminal or click on the xgps icon it will be started.
$su - fa -c "DISPLAY=:0 xgps 127.0.0.1:9999"
  • Or on the Debian GUI start the LXTerminal, type in "xgps" and enter it will be started too.

For more details about this GPS module refer to Click to check
Refer to the following diagram to connect the NanoPC-T2 to the Matrix-GPS:
GPS_NanoPC-T2

Connection Details:

Matrix-GPS NanoPC-T2
RXD Pin11
TXD Pin12
5V Pin29
GND Pin30

14 Access Hardware under Android

FriendlyElec developed a library called “libfriendlyarm-things.so”, for android developer to access the hardware resources on the development board in their android apps, the library is based on Android NDK.
Accessible Modules:

  • Serial Port
  • PWM
  • EEPROM
  • ADC
  • LED
  • LCD 1602 (I2C)
  • OLED (SPI)


Interfaces & Ports:

  • GPIO
  • Serial Port
  • I2C
  • SPI


Refer to the following url for details:

15 Connect NanoPC-T2 to FriendlyARM LCD Modules

  • Android

Here are the LCDs that are supported under Android:S430, S700/S701, S702, HD700, HD702, HD101 and X710 all of which are LCDs with capacitive touch.

  • FriendlyCore & Lubuntu Desktop

Here are the LCDs that are supported under FriendlyCore and Lubuntu Desktop:S430, S700/S701, S702, HD700, HD702, HD101 and X710 all of which are LCDs with capacitive touch;
W35B, H43, P43, S70D and Matrix 2.8" SPI Key TFT LCD all of which are LCDs with resistive touch
All these LCD's tech details can be obtained on our wiki site:LCDModules

16 Schematics & Mechanical drawing

17 Resources

18 Source Code and Image Files Download Links

  • Image File: [3]
  • Source Code: [4]

19 Tech Support

If you have any further questions please visit our forum http://www.friendlyarm.com/Forum/ and post a message or email us at techsupport@friendlyarm.com. We will endeavor to get back to you as soon as possible.

20 Update Log

20.1 2023-01-09

20.1.1 FriendlyCore:

  • optimized the systemd service

20.2 2020-10-26

  • FriendlyCore, Lubuntu:

Fix Bluetooth stability issue

20.3 2019-12-28

  • eflasher:

1) Supports flashing only some files, such as updating only the kernel and uboot in emmc
2) Added gui option to disable overlay filesystem
3) Add command line parameters to achieve one-click installation without interaction
4) Fix the issue that the same mac address will appear on different devices after backup and restore image
5) UI interface can now be configured with title, hide interface menus and buttons

20.4 2019-11-26

  • FriendlyCore:

Pre-installed OpenCV 4.1.2

20.5 2019-11-14

  • Introducing a new system FriendlyWrt:

FriendlyWrt is a customized OpenWrt system developed by FriendlyElec. It is open source and suitable for applications in IoT, NAS etc.
Please refre: http://wiki.friendlyelec.com/wiki/index.php/How_to_Build_FriendlyWrt

  • FriendlyCore, Lubuntu updated as follows:

1) Added support for new 4.3-inch screen YZ43
2) Compile bcmdhd as a module.

  • Android7 update is as follows:

1) Added support for new 4.3-inch screen YZ43
2) Optimize the touch experience when using HD900 screen under Android 7 system
3) Optimize the touch experience when using S702 screen under Android 7 system

20.6 2019-10-18

  • Android7, FriendlyCore, Lubuntu:

Fixed audio playback issue.

20.7 2019-09-30

  • Android7 updated as follows:

1)Added support for Android hardware access library (named FriendlyThing), support access to hardware resources such as GPIO, PWM, RTC, serial port and watchdog, providing open source demo
2) Added support for camera CAM500B (OV5640)
3) Added support for LCD W500 (800x480)
4) Fixed LCD-S430 compatibility issues

  • FriendlyCore, FriendlyDesktop updated as follows:

1) Kernel version updated to v4.4.172, same as Android 7
2) Added Docker support, support 32bit and 64bit file systems
3) Kernel configuration items are optimized to enable more features and device drivers

20.8 2019-07-18

  • Introducing a new system Android 7.1.2

1) Features similar to the old version of Android 5, support 4G, WiFi, Ethernet, Bluetooth, etc.
2) Kernel version: 4.4.172
3) Known issue: The camera is not working yet

  • Android/FriendlyCore/Lubuntu updated as follows:

1) Fix an issue where HD101B can't be touched in some cases
2) Fix GPIO configuration of Power key
3) Solve the problem of too small volume: the volume of the DAC is changed from -20dB to -6dB during playback.
4) Add more models of USB Wi-Fi support, built-in driver rtl8821CU.ko, rtl88XXau.ko

  • Updates for Lubuntu only:

1) Modify Lubuntu's Power key behavior to (without pop-ups) shut down directly
2) Add script xrotate.sh to simplify screen rotation settings (Note: screen rotation will lose performance)

  • The following updates are only available for NanoPC T2, Smart4418:

Support for reading Ethernet Mac addresses from the onboard EEPROM, only supports the following systems: FriendlyCore, Lubuntu, Android7

20.9 2019-06-25

Linux(Ubuntu 16.04/18.04) uses OverlayFS to enhance filesystem stability.

20.10 2019-06-03

1) Configure LED1 to be in heartbeat mode
2) Fix HDMI 1080P may have no display problem in some cases
3) Fix the issue that mysql cannot be installed under Linux
4) Fix the issue that the 1-wire touch resistance screen cannot be used under lubuntu

20.11 2019-01-24

1) Update uboot-v2014.07, uboot-v2016.01 for HD702V LCD
2) Adjust Qt5 font path

20.12 2018-12-17

  • Android5 updated as follows:

1) Add support for 4G network, support module: Quectel EC20
2) Add audio setting UI, you can set the default output to headphones or HDMI
3) Synchronously turn off the backlight of the one-line touch screen when the system Shutdown

  • FriendlyCore updated as follows:

1) Add OV5640 camera support
2) Update BL1 to improve system startup stability

  • Lubuntu updated as follows:

1) Add Chrome-browser browser, support web page 1080P hardware decoding, support WebGL
2) Set the audio output channel to HDMI by default (can be changed via /etc/asound.conf)
3) Update BL1 to improve system startup stability
4) Fixed some issues regarding the package error in the previous version
5) Adjust DPMS settings, turn off automatic sleep by default

20.13 March-04-2016

  • Released English version

20.14 March-09-2016

  • Corrected a typo

20.15 March-23-2016

  • Added section 11

20.16 March-27-2016

  • Corrected expression errors

20.17 April-08-2016

  • Added section 6.4.2 and 7.4
  • Updated section 6.5

20.18 June-30-2016

  • Added section 9 and 10

20.19 Sep-04-2016

  • Updated section 5.2.2 and 10.1.1

20.20 Sep-27-2016

  • Updated section 5.2.2, 7.5 and 8.2

20.21 Nov-2-2016

  • Updated section 6.2, 6.3, 6.4 and 12

20.22 Nov-17-2016

  • Added section 10.6

20.23 Dec-7-2016

  • Added section 6.6
  • Updated section 7.5

20.24 June-13-2016

  • Added section 7: added UbuntuCore
  • Added section 11.3: added DietPi

20.25 June-20-2016

  • Updated sections 6.2 & 6.3: Wireless connection and WiFi AP setting
  • Added section 3: software features