Difference between revisions of "NanoPi S2"

From FriendlyELEC WiKi
Jump to: navigation, search
(在电脑上修改SD卡上的系统)
(updated by API)
 
(92 intermediate revisions by 5 users not shown)
Line 2: Line 2:
  
 
==Introduction==
 
==Introduction==
[[File:NanoPi S2-01B.jpg|thumb|Overview]]
+
[[File:NanoPi S2-01B.png|thumb|Overview]]
[[File:NanoPi S2-A01.png|thumb|Front]]
+
[[File:NanoPi S2-Front.png|thumb|Front]]
[[File:NanoPi S2-B01.png|thumb|Back]]
+
[[File:NanoPi S2-Back.png|thumb|Back]]
  
* The NanoPi S2(S2) is is designed and developed by FriendlyElec for professionals, enterprise users, makers and hobbyists. It is a small board with WiFi, Bluetooth and eMMC.
+
* The NanoPi S2(S2) is designed and dev
* It uses the Samsung Quad Core Cortex-A9 S5P4418 SoC with dynamic frequency scaling up to 1.4GHz. It has 1G DDR3 RAM, 802.11 b/g/n WiFi & Bluetooth 4.0 module. Its in-built power management unit uses the AXP228 chip which supports software shutdown. It takes power over the MicroUSB port. It has video input/output interface, 3.5mm audio jack, USB port and MicroSD card slot, serial debug port and ADC pin-header.
+
* An Android and a Debian images are ready for the NanoPi S2. The Android OS supports HDMI and LCD output.
+
* The NanoPi S2 has various IO ports which are compatible with Raspberry Pi's GPIOs. Its PCB dimension is 40 * 75 mm. The NanoPi S2 works with most of the modules and OS images that are developed for FriendlyElec's S5P4418 based boards.
+
  
==Specifications==
+
==Hardware Spec==
 
* CPU: S5P4418, dynamic frequency from 400Mhz to 1.4GHz
 
* CPU: S5P4418, dynamic frequency from 400Mhz to 1.4GHz
* PMU Power Management Unit: AXP228. It supports software shutdown and wake-up functions.
+
* PMU Power Management: Implemented by a Cortex-M0 MCU, support software power-off, and RTC alarm power-on functions
 
* DDR3 RAM: 1GB  
 
* DDR3 RAM: 1GB  
 
* eMMC: 8GB
 
* eMMC: 8GB
* Wireless:802.11 b/g/s
+
* Wireless:802.11 b/g/n
 
* Bluetooth:4.0 dual mode
 
* Bluetooth:4.0 dual mode
* MicroSD Slot:x1
+
* MicroSD Slot: 1 x MicroSD Slot
 
* Audio: 3.5mm jack/Via HDMI
 
* Audio: 3.5mm jack/Via HDMI
* Microphone: Onboard microphone
+
* Microphone: 3.5mm jack
* USB Host: 1 x USB 2.0 Host Micro USB: 1 x USB 2.0 Client
+
* USB Host: 1 x USB 2.0 Host  
 +
* Micro USB: 1 x MicroUSB, USB 2.0 for both data transmission and power input
 
* LCD Interface: 0.5 mm pitch 45-pin SMT FPC seat, for full-color LCD (RGB: 8-8-8)
 
* LCD Interface: 0.5 mm pitch 45-pin SMT FPC seat, for full-color LCD (RGB: 8-8-8)
 
* HDMI: microHDMI,1080P60 output
 
* HDMI: microHDMI,1080P60 output
* DVP Camera Interface: 0.5mm pitch 24-pin FPC socket.  
+
* DVP Camera Interface: 0.5mm pitch 24-pin FPC seat.  
* LVDS:2.0mm pitch 20-Pin header
+
* LVDS:0.5mm pitch 24-Pin FPC seat
 
* GPIO1: 2.54mm pitch 40pin, compatible with Raspberry Pi's GPIO. It includes UART, SPI, I2C, PWM, IO and etc
 
* GPIO1: 2.54mm pitch 40pin, compatible with Raspberry Pi's GPIO. It includes UART, SPI, I2C, PWM, IO and etc
 
* ADC: onboard ADC pin header
 
* ADC: onboard ADC pin header
 
* Serial Debug Port:2.54mm pitch 4-Pin header
 
* Serial Debug Port:2.54mm pitch 4-Pin header
* Antenna Interface: IPX
+
* Antenna Interface: IPEX connector
* User Key: 1 x Power , 1 x Reset
+
* User Key: 1 x Power , 1 x Boot Mode Switch
 
* LED: 1 x Power LED, 1 x System LED
 
* LED: 1 x Power LED, 1 x System LED
 
* RTC: RTC Pins
 
* RTC: RTC Pins
* PCB Size(mm): 64 x 56, 6 layer, ENIG
+
* PCB Size(mm): 75 x 40, 8 layer, ENIG
 
* Power Supply: DC 5V/2A
 
* Power Supply: DC 5V/2A
 +
* Working Temperature: -40℃ to 80℃
 
* OS/Software: u-boot, Android5.1, Debian8
 
* OS/Software: u-boot, Android5.1, Debian8
  
 
==Diagram, Layout and Dimension==
 
==Diagram, Layout and Dimension==
 
===Layout===
 
===Layout===
[[File:NanoPi-S2-IF.png |thumb|300px|NanoPi S2 Layout]]
+
[[File:NanoPi-S2-interface.png |thumb|500px|NanoPi S2 Layout]]
  
 
* '''GPIO1 Pin Description'''
 
* '''GPIO1 Pin Description'''
Line 86: Line 85:
 
|39  || DGND          ||40    || SPI2_CLK/GPIOC9
 
|39  || DGND          ||40    || SPI2_CLK/GPIOC9
 
|}
 
|}
The above pin description is different from that of the NanoPi 2. Here is a comparison table:[[40 pins GPIO comparison table]]
+
 
 
* '''Debug Port(UART0)'''
 
* '''Debug Port(UART0)'''
 
::{| class="wikitable"
 
::{| class="wikitable"
Line 100: Line 99:
 
|4    || UART_RXD0  
 
|4    || UART_RXD0  
 
|}
 
|}
 +
 +
* '''ADC'''
 +
:: ADC rang: 0~1.8V
 +
::{| class="wikitable"
 +
|-
 +
|Pin# || Name     
 +
|-
 +
|1    || 1.8V reference output 
 +
|-
 +
|2    || ADC3   
 +
|-
 +
|3    || ADC4 
 +
|-
 +
|4    || DGND
 +
|-
 +
|5    || AUD_LIN2, audio line in 2 of ES8316
 +
|}
 +
 
* '''DVP Camera Interface Pin Description'''
 
* '''DVP Camera Interface Pin Description'''
 
::{| class="wikitable"
 
::{| class="wikitable"
Line 127: Line 144:
 
|16-23 || Data bit7-0
 
|16-23 || Data bit7-0
 
|}
 
|}
 +
 +
* '''LVDS '''
 +
::{| class="wikitable"
 +
|-
 +
|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  || GPIOC15
 +
|-
 +
|20 || DGND
 +
|-
 +
|21  || I2C2_SCL
 +
|-
 +
|22 || I2C2_SDA
 +
|-
 +
|23  || GPIOC16
 +
|-
 +
|24 || DGND
 +
|}
 +
 
* '''RGB LCD Interface Pin Description'''
 
* '''RGB LCD Interface Pin Description'''
 +
:: The NanoPi S2's LCD interface is a top FPC connector while the LCD interface on the NanoPi M3/M2/Fire and NanoPC-T2/T3 is a bottom contact. The pin sequence of the NanoPi S2's LCD interface is the reverse of the pin sequence of the LCD interface on the other Nano boards.
 +
:: When you connect a FriendlyElec's LCD with resistive touch e.g. P43 or H43 to the NanoPi S2 you need to connect the FPC cable' pin1 to pin 45 of the S2's LCD interface.
 
::{| class="wikitable"
 
::{| class="wikitable"
 
|-
 
|-
 
|Pin# || Name  || Description   
 
|Pin# || Name  || Description   
 
|-
 
|-
|1, 2 || VDD_5V || 5V Output, it can be used to power LCD modules
+
|44, 45 || VDD_5V || 5V Output, it can be used to power LCD modules
 
|-
 
|-
|11,20,29, 37,38,39,40, 45|| DGND || Ground
+
|1,6,7,8,9,17,26,35|| DGND || Ground
 
|-
 
|-
|3-10   || Blue LSB to MSB  || RGB blue
+
|36-43   || Blue MSB to LSB || RGB blue
 
|-  
 
|-  
|12-19   || Green LSB to MSB || RGB green
+
|27-34   || Green MSB to LSB || RGB green
 
|-
 
|-
|21-28   || Red LSB to MSB  || RGB red
+
|18-25   || Red MSB to LSB   || RGB red
 
|-
 
|-
|30     || GPIOB25          || available for users
+
|16     || 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
+
|15     || 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
+
|14     || XnRSTOUT Form CPU || low when system is reset
 
|-
 
|-
|33     || VDEN  || signal the external LCD that data is valid on the data bus
+
|13     || VDEN  || signal the external LCD that data is valid on the data bus
 
|-
 
|-
|34     || VSYNC || vertical synchronization
+
|12     || VSYNC || vertical synchronization
 
|-
 
|-
|35     || HSYNC || horizontal synchronization
+
|11     || HSYNC || horizontal synchronization
 
|-
 
|-
|36     || LCDCLK || LCD clock, Pixel frequency
+
|10     || LCDCLK || LCD clock, Pixel frequency
 
|-
 
|-
|41     || I2C2_SCL  || I2C2 clock signal, for capacitive touch data transmission
+
|5     || I2C2_SCL  || I2C2 clock signal, for capacitive touch data transmission
 
|-
 
|-
|42     || I2C2_SDA  || I2C2 data signal, for capacitive touch data transmission
+
|4     || I2C2_SDA  || I2C2 data signal, for capacitive touch data transmission
 
|-
 
|-
|43     || GPIOC16 || interrupt pin for capacitive touch, used with I2C2
+
|3     || GPIOC16 || interrupt pin for capacitive touch, used with I2C2
 
|-
 
|-
|44     || NC  || Not connected
+
|2     || NC  || Not connected
 
|}
 
|}
 
:'''Notes'''
 
:'''Notes'''
Line 169: Line 243:
 
::#All pins are 3.3V, output current is 5mA
 
::#All pins are 3.3V, output current is 5mA
 
::#GPIO1' pin description is different from that of the NanoPi 2. Here is a comparison table[[40 pins GPIO comparison table]]
 
::#GPIO1' pin description is different from that of the NanoPi 2. Here is a comparison table[[40 pins GPIO comparison table]]
::#For more details refer to the document:[]
+
::#For more details refer to the document:[http://wiki.friendlyelec.com/wiki/images/9/98/NanoPi-S2-1710-Schematic.pdf NanoPi-S2-1710-Schematic.pdf]
  
 
===Board Dimension===
 
===Board Dimension===
[[File:NanoPi2_S2_Dimensions.png|frameless|500px|NanoPi S2 Dimensions]]
+
[[File:NanoPi-S2-1710-Drawing.jpg|frameless|500px|NanoPi S2 Dimensions]]
  
::For more details please refer to the document:[http://wiki.friendlyarm.com/wiki/index.php/File:NanoPi-S2-1609-dimensions.png NanoPi-S2-1609-dimensions]
+
::For more details please refer to the document:[http://wiki.friendlyelec.com/wiki/images/5/5c/NanoPi-S2-1710-Drawing%28dxf%29.zip dxf file]
  
 
==Get Started==
 
==Get Started==
Line 180: Line 254:
 
Before starting to use your NanoPi S2 get the following items ready
 
Before starting to use your NanoPi S2 get the following items ready
 
* NanoPi S2
 
* NanoPi S2
* MicroSD Card/TF Card: Class 10 or Above, minimum 8GB SDHC
+
* microSD Card/TFCard: Class 10 or Above, minimum 8GB SDHC
* A DC 5V/2A power is a must
+
* microUSB power. A 5V/2A power is a must
 
* 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 computer running Ubuntu 14.04 64 bit system
+
* A host computer running Ubuntu 18.04 64 bit system
 
+
{{S5P4418BootFromSDCard|NanoPi-S2}}
 
+
{{BurnOSToEMMC|NanoPi-S2|s5p4418-eflasher}}
===TF Card We Tested===
+
{{S5PXX18MakeSDCardViaSDFusing|NanoPi-S2|sd-fuse_s5p4418}}
To make your NanoPi S2 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:
+
{{ResizeTFCardFS|NanoPi-S2}}
*SanDisk TF 8G Class10 Micro/SD TF card:
+
{{S5Pxx18HDMI|NanoPi-S2|arch/arm/plat-s5p4418/nanopi2/lcds.c}}
[[File:SanDisk MicroSD.png|frameless|100px|SanDisk MicroSD 8G]]
+
{{S5Pxx18MofidyKernelCommandLineOnHostPC|NanoPi-S2|sd-fuse_s5p4418}}
*SanDisk TF128G MicroSDXC TF 128G Class10 48MB/S:
+
{{NanoPCStartToUse|NanoPi-S2}}
[[File:SanDisk MicroSD-01.png|frameless|100px|SanDisk MicroSD 128G]]
+
{{FriendlyCoreGeneral|NanoPi-S2}}
*川宇 8G C10 High Speed class10 micro SD card:
+
{{FriendlyCoreRunX11Application|NanoPi-S2}}
[[File:SanDisk MicroSD-02.png|frameless|100px|chuanyu MicroSD 8G]]
+
{{FriendlyCoreS5Pxx18|NanoPi-S2}}
 
+
{{UbuntuXenial-Armhf-Install-Docker|NanoPi-S2}}
 
+
{{S5Pxx18Android|NanoPi-S2}}
===Make an Installation MicroSD Card===
+
{{MoreOS}}
====Under Windows====
+
{{S5P4418BuildFromSource|NanoPi-S2}}
Please get the following files from here [http://wiki.friendlyarm.com/wiki/nanopi2/download/ download link] to download image files<br />
+
{{S5P4418-KernelHeaderFile|NanoPi-S2}}
* Get a 4G SDHC card and backup its data if necessary
+
{{S5Pxx18ExternalModules|NanoPi-S2}}
FriendlyARM migrated both Android 5.1 and Android 4.4 to the NanoPi S2. Android 4.4 includes features that professional users usually need: 4G, Ethernet configuration and etc.
+
{{S5Pxx18AccessHWUnderAndroid|NanoPi-S2}}
 
+
{{S5Pxx18ConnectToLCDModules|NanoPi-S2}}
::{| class="wikitable"
+
{{S5Pxx18HWfiles|NanoPi-S2}}
|-
+
{{S5P4418Resources|NanoPi-S2}}
|colspan=2|For LCD or HDMI output please use the following files:
+
{{DownloadUrl|NanoPi-S2}}
|-
+
{{TechSupport|NanoPi-S2}}
|nanopi2-debian-sd4g.img.zip      || Debian image file                 
+
{{S5P4418ChangeLog}}
|-
+
|nanopi2-android-sd4g.img.zip      || Android5.1 image file
+
|-
+
|s5p4418-kitkat-sd4g-20160803.img.zip    ||  Android4.4 image file
+
|-
+
|colspan=2|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 NanoPi S2's boot slot, press and hold the boot key and power on (with a 5V/2A power source). If the green LED is on and the blue LED is blinking this indicates your NanoPi S2 has successfully booted.<br />
+
 
+
====Under Linux Desktop====
+
*1) Insert your microSD card to your host running Ubuntu and check your SD card's device name
+
<syntaxhighlight lang="bash">
+
dmesg | tail
+
</syntaxhighlight>
+
Search the messages output by "dmesg" for similar words like "sdc: sdc1 sdc2". If you can find them it means your SD card is recognized as "/dev/sdc". Or you can check that by commanding "cat /proc/partitions".
+
 
+
*2) Download Flashing Script
+
<syntaxhighlight lang="bash">
+
git clone https://github.com/friendlyarm/sd-fuse_nanopi2.git
+
cd sd-fuse_nanopi2
+
</syntaxhighlight>
+
 
+
*3) Flash Android Firmware to MicroSD Card
+
<syntaxhighlight lang="bash">
+
su
+
./fusing.sh /dev/sdx
+
</syntaxhighlight>
+
(Note: you need to replace "/dev/sdx" with the device name in your system)
+
When you do “git clone” you have to hit “Y” within 10 seconds after it prompts you to download image files otherwise you will miss the download.
+
 
+
*4) Flash Debian Firmware to MicroSD Card
+
<syntaxhighlight lang="bash">
+
./fusing.sh /dev/sdx debian
+
</syntaxhighlight>
+
 
+
====Flash image to eMMC with eflasher====
+
* Download eflasher <br />
+
Get the eflasher utility s5p4418-eflasher-sd8g-xxx-full.img.7z<br />
+
This package includes a Ubuntu Core, Debian, Android 5 and Android 4.4 image files;<br />
+
Get the Windows utility: win32diskimager.rar;<br/>
+
* Flash eflasher Image <br />
+
Extract the .7z package and you will get .img 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.<br/>
+
If your PC runs Linux you can use the dd command to flash a .img file to the SD card;<br />
+
* Flash image to eMMC
+
Insert this card into your NanoPi S2, connect the board to an HDMI monitor or an LCD, press and hold the boot key and power on (with a 5V/2A power source) the board. After your board is powered on you will see multiple OS options and you can select an OS to start installation.
+
 
+
====Extend NanoPi S2's TF 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:
+
<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>
+
(Note: you need to replace "/dev/sdx" with the device name in your system)
+
 
+
====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.<br/>
+
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.<br/>
+
If your NanoPi S2 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 NanoPi S2 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.
+
 
+
===Update Image Files in SD Card From PC Host===
+
If you want to make some changes to the image files in your SD card follow the steps below otherwise you can skip this section.<br />
+
Insert your SD card into a host PC running Linux, mount the boot and rootfs sections of the SD card and follow the steps below:<br />
+
1) If you want to change your kernel command line parameters you can do it via the fw_setevn utility under "sd-fuse_nanopi2/tools".<br />
+
Check the current Command Line:
+
<syntaxhighlight lang="bash">
+
cd sd-fuse_nanopi2/tools
+
./fw_printenv /dev/sdc | grep bootargs
+
</syntaxhighlight>
+
Android 5.1.1_r6 starts SELinux. By default it is enforcing. You can change it this way:
+
<syntaxhighlight lang="bash">
+
./fw_setenv /dev/sdc bootargs XXX androidboot.selinux=permissive
+
</syntaxhighlight>
+
This sets it to "permissive". The "XXX" stands for the original bootargs' value.<br />
+
 
+
2) Update Kernel <br />
+
Our customized uboot will check the LCD type when it boots.<br/>
+
For a non-Android OS if it recognizes that an LCD is connected to the NanoPi S2 it will load "uImage" from "boot" otherwise it will load "uImage.hdmi".<br />
+
For Android it doesn't make any difference which display device is detected. You can use your generated uImage to replace the existing one under "boot".<br />
+
For Debian if your generated kernel is for an LCD you need to replace the existing uImage or if your kernel is for an HDMI monitor you need to replace the existing uImage.hdmi.<br />
+
 
+
===运行Android或Debian===
+
*将制作好microSD卡插入NanoPi S2,连接HDMI,最后连接电源(5V 2A),NanoPi S2会上电自动开机,看到板上的蓝色LED闪烁,这说明系统已经开始启动了,同时电视上也将能看到系统启动的画面。<br />
+
1)要在电视上进行操作,你需要连接USB鼠标和键盘;如果你选购了LCD配件,则可以直接使用LCD上面的触摸屏进行操作。<br />
+
2)如果您需要进行内核开发,你最好选购一个串口配件,连接了串口,则可以通过终端对NanoPi S2进行操作。<br />
+
*以下是串口的接法,假如你已经拿到串口,则可直接串口供电,不需要再通过microUSB供电,接上串口,即可调试:
+
[[File:NanoPi S2-PSU-ONECOM.png|frameless|400px|NanoPi S2-PSU-ONECOM]]
+
*如果提示输入密码,Debian的root用户的默认密码是两个字母fa。
+
 
+
===通过VNC和ssh登录Debian===
+
如果你是祼板运行系统(既没有连接LCD也没有连接HDMI),你可以使用手机或电脑到[http://www.realvnc.com/download/ 这里]下载并安装一个名为VNC Viewer的软件,用VNC连接到NanoPi S2,默认密码为:fa123456 。<br />
+
以下是在iPhone上用VNC登录NanoPi S2的画面:<br />
+
[[File:iphone6-vnc-nanopi2.png|frameless|400px|VNC to NanoPi2]]
+
<br />
+
你也可以通过 ssh -l root 192.168.8.1 命令在终端上登录,默认的root用户密码是 fa 。<br />
+
<br />
+
 
+
==Debian系统的使用==
+
===连接有线网络===
+
NanoPi S2在加电开机前如果已正确的连接网线,则系统启动时会自动获取IP地址,如果没有连接网线、没有DHCP服务或是其它网络问题,则会导致获取IP地址失败,同时系统启动会因此等待约15~60秒的时间。
+
* 1) 配置MAC地址
+
板子没有提供有效的Ethernet的MAC地址,系统在连接网络时会自动生成一个随机的MAC地址,您可以修改 /etc/network/interfaces.d/eth0 ,配置一个固定的MAC地址:
+
<syntaxhighlight lang="bash">
+
vi /etc/network/interfaces.d/eth0
+
</syntaxhighlight>
+
以下是配置文件的具体内容:
+
<syntaxhighlight lang="bash">
+
auto eth0
+
allow-hotplug eth0
+
iface eth0 inet dhcp
+
hwaddress 76:92:d4:85:f3:0f
+
</syntaxhighlight>
+
其中"hwaddress" 就是用来指定MAC地址,"76:92:d4:85:f3:0f"是一个随机生成的地址,为防止冲突导致网络问题,请修改为一个不同的且有效的地址。<br />
+
需要注意的一点是,MAC地址必须符合IEEE的规则,请不要随意指定,否则会出现无法获取IP地址、无法上网等问题。
+
修改完配置文件并保存后,可重启板子或直接下列命令重启网络服务:
+
<syntaxhighlight lang="bash">
+
systemctl restart networking
+
</syntaxhighlight>
+
 
+
===安装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来更新正在运行的NanoPi S2板上SD的U-Boot,方法如下:<br />
+
1) 在电脑上先用命令 sudo apt-get install android-tools-fastboot 安装 fastboot 工具;<br />
+
2) 用串口配件连接NanoPi S2和电脑,在上电启动的2秒内,在串口终端上按下回车,进入 u-boot 的命令行模式;<br />
+
3) 在u-boot 命令行模式下输入命令 fastboot 回车,进入 fastboot 模式;<br />
+
4) 用microUSB线连接NanoPi S2和电脑,在电脑上输入以下命令烧写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>
+
NanoPi2内核所属的分支是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>
+
使用新生成的uImage替换掉SD卡boot分区下的uImage.hdmi即可获得HDMI 1080p输出。<br />
+
如果要编译支持LCD显示的内核,则需要修改内核配置:
+
<syntaxhighlight lang="bash">
+
touch .scmversion
+
make nanopi2_linux_defconfig
+
make menuconfig
+
  Device Drivers -->
+
    Graphics support -->
+
      Nexell Graphics -->
+
        [*] LCD
+
        [ ] HDMI
+
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文件。
+
::{| class="wikitable"
+
|-
+
|filename    || partition || Description 
+
|-
+
|boot.img    || boot      || -
+
|-  
+
|cache.img    || cache    || -
+
|-  
+
|userdata.img || userdata  || -
+
|-  
+
|system.img  || system    || -
+
|-  
+
|partmap.txt  || -        || 分区描述文件
+
|-
+
|}
+
 
+
* 烧写到SD卡
+
如果是采用SD卡启动Android,可复制编译生成的image文件到sd-fuse_nanopi2/android/ 下,使用脚本即可烧到到SD卡,具体请查看[[#在Linux Desktop下通过脚本制作]]。
+
 
+
==源代码和固件下载链接==
+
* 烧写固件下载链接:[http://wiki.friendlyarm.com/wiki/nanopi2/download/]
+
* 源代码下载链接:[https://github.com/friendlyarm]
+
 
+
==资源链接==
+
* 《创客秘籍》[http://wiki.friendlyarm.com/wiki/index.php/File:%E5%88%9B%E5%AE%A2%E7%A7%98%E7%B1%8D.pdf 创客秘籍]
+
* 《创客秘籍-02》[http://pan.baidu.com/s/1hrDu9es 创客秘籍-02]
+
* 《创客秘籍-03》[http://wiki.friendlyarm.com/wiki/index.php/File:%E5%88%9B%E5%AE%A2%E7%A7%98%E7%B1%8D-03.pdf 创客秘籍-03]
+
* Schematic ([http://wiki.friendlyarm.com/wiki/index.php/File:NanoPi-S2-1609-Schematic.pdf NanoPi-S2-1609-Schematic])
+
* S5P4418 Datasheet ([http://wiki.friendlyarm.com/wiki/images/a/a7/Pi2_SOC_DS_0.1.pdf S5P4418_Datasheet_0.1.pdf])
+
* 模块介绍以及开发文档:
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Button/zh 按键模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_LED/zh LED模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Analog_to_Digital_Converter/zh 模数转换]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Relay/zh 继电器模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_3-Axis_Digital_Accelerometer/zh 三轴重力加速度模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_3-Axis_Digital_Compass/zh 三轴数字指南针模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Temperature_Sensor/zh 温度传感器模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Temperature_and_Humidity_Sensor/zh 温湿度传感器模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Buzzer/zh 蜂鸣器]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Joystick/zh 摇杆模块(Joystick)]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_I2C_LCD1602_Keypad/zh I2C(PCF8574)+LCD1602]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Sound_Sensor/zh 声音传感器]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Ultrasonic_Ranger/zh 超声波模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_GPS/zh GPS模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Compact_Kit/zh 迷你扩展板Matrix - Compact Kit]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Fire_Sensor 火焰传感器]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_CAM500A/zh CAM500 500万像素摄像头]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_BAll_Rolling_Switch/zh 滚珠开关模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_2%278_SPI_Key_TFT/zh 2'8 SPI Key TFT 2.8寸spi液晶屏]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_IR_Counter/zh 红外计数模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_IR_Receiver/zh 红外接收模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_L298N_Motor_Driver/zh 电机驱动器模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_MQ-2_Gas_Sensor/zh MQ-2 烟雾传感器模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_MQ-3_Gas_Sensor/zh MQ-3 气体传感器]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_One_Touch_Sensor/zh 单点电容式数字触摸传感器模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Photoresistor/zh 光敏电阻模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Potentiometer/zh 电位器模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Pressure_and_Temperature_Sensor 压力传感器模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_RGB_LED/zh RGB LED]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_RTC/zh RTC模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Rotary_Encoder/zh Rotary Encoder]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Soil_Moisture_Sensor/zh 土壤湿度检测传感器模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Thermistor/zh 热敏电阻模块]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_USB_WiFi/zh USB WiFi]
+
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Water_Sensor 水位/水滴识别检测传感器模块]
+

Latest revision as of 08:15, 3 July 2024

查看中文

Contents

1 Introduction

Overview
Front
Back
  • The NanoPi S2(S2) is designed and dev

2 Hardware Spec

  • CPU: S5P4418, dynamic frequency from 400Mhz to 1.4GHz
  • PMU Power Management: Implemented by a Cortex-M0 MCU, support software power-off, and RTC alarm power-on functions
  • DDR3 RAM: 1GB
  • eMMC: 8GB
  • Wireless:802.11 b/g/n
  • Bluetooth:4.0 dual mode
  • MicroSD Slot: 1 x MicroSD Slot
  • Audio: 3.5mm jack/Via HDMI
  • Microphone: 3.5mm jack
  • USB Host: 1 x USB 2.0 Host
  • Micro USB: 1 x MicroUSB, USB 2.0 for both data transmission and power input
  • LCD Interface: 0.5 mm pitch 45-pin SMT FPC seat, for full-color LCD (RGB: 8-8-8)
  • HDMI: microHDMI,1080P60 output
  • DVP Camera Interface: 0.5mm pitch 24-pin FPC seat.
  • LVDS:0.5mm pitch 24-Pin FPC seat
  • GPIO1: 2.54mm pitch 40pin, compatible with Raspberry Pi's GPIO. It includes UART, SPI, I2C, PWM, IO and etc
  • ADC: onboard ADC pin header
  • Serial Debug Port:2.54mm pitch 4-Pin header
  • Antenna Interface: IPEX connector
  • User Key: 1 x Power , 1 x Boot Mode Switch
  • LED: 1 x Power LED, 1 x System LED
  • RTC: RTC Pins
  • PCB Size(mm): 75 x 40, 8 layer, ENIG
  • Power Supply: DC 5V/2A
  • Working Temperature: -40℃ to 80℃
  • OS/Software: u-boot, Android5.1, Debian8

3 Diagram, Layout and Dimension

3.1 Layout

NanoPi S2 Layout
  • GPIO1 Pin Description
Pin# Name Pin# Name
1 SYS_3.3V 2 VDD_5V
3 I2C0_SDA 4 VDD_5V
5 I2C0_SCL 6 DGND
7 GPIOD8/PPM 8 UART3_TXD/GPIOD21
9 DGND 10 UART3_RXD/GPIOD17
11 UART4_TX/GPIOB29 12 GPIOD1/PWM0
13 GPIOB30 14 DGND
15 GPIOB31 16 GPIOC14/PWM2
17 SYS_3.3V 18 GPIOB27
19 SPI0_MOSI/GPIOC31 20 DGND
21 SPI0_MISO/GPIOD0 22 UART4_RX/GPIOB28
23 SPI0_CLK/GPIOC29 24 SPI0_CS/GPIOC30
25 DGND 26 GPIOB26
27 I2C1_SDA 28 I2C1_SCL
29 GPIOC8 30 DGND
31 GPIOC7 32 GPIOC28
33 GPIOC13/PWM1 34 DGND
35 SPI2_MISO/GPIOC11 36 SPI2_CS/GPIOC10
37 AliveGPIO3 38 SPI2_MOSI/GPIOC12
39 DGND 40 SPI2_CLK/GPIOC9
  • Debug Port(UART0)
Pin# Name
1 DGND
2 VDD_5V
3 UART_TXD0
4 UART_RXD0
  • ADC
ADC rang: 0~1.8V
Pin# Name
1 1.8V reference output
2 ADC3
3 ADC4
4 DGND
5 AUD_LIN2, audio line in 2 of ES8316
  • DVP Camera Interface Pin Description
Pin# Name
1, 2 SYS_3.3V
7,9,13,15,24 DGND
3 I2C0_SCL
4 I2C0_SDA
5 GPIOB14
6 GPIOB16
8,10 NC
11 VSYNC
12 HREF
14 PCLK
16-23 Data bit7-0
  • 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 GPIOC15
20 DGND
21 I2C2_SCL
22 I2C2_SDA
23 GPIOC16
24 DGND
  • RGB LCD Interface Pin Description
The NanoPi S2's LCD interface is a top FPC connector while the LCD interface on the NanoPi M3/M2/Fire and NanoPC-T2/T3 is a bottom contact. The pin sequence of the NanoPi S2's LCD interface is the reverse of the pin sequence of the LCD interface on the other Nano boards.
When you connect a FriendlyElec's LCD with resistive touch e.g. P43 or H43 to the NanoPi S2 you need to connect the FPC cable' pin1 to pin 45 of the S2's LCD interface.
Pin# Name Description
44, 45 VDD_5V 5V Output, it can be used to power LCD modules
1,6,7,8,9,17,26,35 DGND Ground
36-43 Blue MSB to LSB RGB blue
27-34 Green MSB to LSB RGB green
18-25 Red MSB to LSB RGB red
16 GPIOB25 available for users
15 GPIOC15 occupied by FriendlyARM one wire technology to recognize LCD models and control backlight and implement resistive touch, not applicable for users
14 XnRSTOUT Form CPU low when system is reset
13 VDEN signal the external LCD that data is valid on the data bus
12 VSYNC vertical synchronization
11 HSYNC horizontal synchronization
10 LCDCLK LCD clock, Pixel frequency
5 I2C2_SCL I2C2 clock signal, for capacitive touch data transmission
4 I2C2_SDA I2C2 data signal, for capacitive touch data transmission
3 GPIOC16 interrupt pin for capacitive touch, used with I2C2
2 NC Not connected
Notes
  1. SYS_3.3V: 3.3V power output
  2. VDD_5V: 5V power output5V. 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. GPIO1' pin description is different from that of the NanoPi 2. Here is a comparison table40 pins GPIO comparison table
  5. For more details refer to the document:NanoPi-S2-1710-Schematic.pdf

3.2 Board Dimension

NanoPi S2 Dimensions

For more details please refer to the document:dxf file

4 Get Started

4.1 Essentials You Need

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

  • NanoPi S2
  • microSD Card/TFCard: Class 10 or Above, minimum 8GB SDHC
  • microUSB power. A 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

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

4.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 NanoPi-S2, 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 NanoPi-S2, log into or SSH to your board and run the following command to start EFlasher:

sudo eflasher

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

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

4.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 NanoPi-S2 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 NanoPi-S2 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.

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

4.7 Run Android or Linux (TODO)

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

5 Work with FriendlyCore

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

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

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

5.4 Develop Qt Application

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

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

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

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

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


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


5.10 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

5.11 Modify timezone

For exampe, change to Shanghai timezone:

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

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


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

5.14 Run Qt 5.10.0 Demo with GPU acceleration

Run the following command

$ sudo qt5demo

S5pxx18-QtE

5.15 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/

5.16 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

5.17 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

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

5.19 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

5.20 Installing and Using Caffe

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

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

5.21.1 How to Install Docker

Run the following commands:

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

5.21.2 Test Docker installation

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

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

6 Work with Android

6.1 Work with 4G Module EC20 under Android5

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

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

6.4 Android Keys

Android 5:

  vendor/friendly-arm/nanopi3/security/

Android 7:

  build/target/product/security/

6.5 Optimizing HDMI Performance on Android 7

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

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

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

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

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

7 More OS Support

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

8 Make Your Own OS Image

8.1 Install Cross Compiler

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

8.2 Compile Linux kernel for FriendlyCore/Lubuntu/EFlasher

8.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 NanoPi-S2'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.

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

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

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

8.5 Compile Android 7.1.2

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

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

NanoPi-S2 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

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

9 Build Kernel Headers Package

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

9.1 Software Version

The OS image file name: 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

9.2 Install the required packages

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

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

10 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

10.1 Testing

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

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

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

sudo insmod ./pf_ring.ko

11 Connect NanoPi-S2 to External Modules

11.1 Connect NanoPi-S2 to USB Camera(FA-CAM202)

  • In this use case the NanoPi-S2 runs Debian. If you connect your NanoPi-S2 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

11.2 Connect NanoPi-S2 to CMOS 5M-Pixel Camera

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

  • If your NanoPi-S2 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

11.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 NanoPi-S2 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 NanoPi-S2:

  • Firstly you need to make sure your NanoPi-S2 is connected to the internet.Login to your NanoPi-S2 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 NanoPi-S2. You can test your camera with NanoPi-S2'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 NanoPi-S2 to USB Keyboard & Run the Following Command:

./demo

opencv is successfully started

11.4 Connect NanoPi-S2 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 NanoPi-S2 is connected to the Matrix GPS module, after the NanoPi-S2 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 NanoPi-S2 to the Matrix-GPS:
GPS_NanoPC-T2

Connection Details:

Matrix-GPS NanoPi-S2
RXD Pin11
TXD Pin12
5V Pin29
GND Pin30

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

13 Connect NanoPi-S2 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

14 Schematics & Mechanical drawing

15 Resources

16 Source Code and Image Files Download Links

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

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

18 Update Log

18.1 2023-01-09

18.1.1 FriendlyCore:

  • optimized the systemd service

18.2 2020-10-26

  • FriendlyCore, Lubuntu:

Fix Bluetooth stability issue

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

18.4 2019-11-26

  • FriendlyCore:

Pre-installed OpenCV 4.1.2

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

18.6 2019-10-18

  • Android7, FriendlyCore, Lubuntu:

Fixed audio playback issue.

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

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

18.9 2019-06-25

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

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

18.11 2019-01-24

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

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

18.13 March-04-2016

  • Released English version

18.14 March-09-2016

  • Corrected a typo

18.15 March-23-2016

  • Added section 11

18.16 March-27-2016

  • Corrected expression errors

18.17 April-08-2016

  • Added section 6.4.2 and 7.4
  • Updated section 6.5

18.18 June-30-2016

  • Added section 9 and 10

18.19 Sep-04-2016

  • Updated section 5.2.2 and 10.1.1

18.20 Sep-27-2016

  • Updated section 5.2.2, 7.5 and 8.2

18.21 Nov-2-2016

  • Updated section 6.2, 6.3, 6.4 and 12

18.22 Nov-17-2016

  • Added section 10.6

18.23 Dec-7-2016

  • Added section 6.6
  • Updated section 7.5

18.24 June-13-2016

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

18.25 June-20-2016

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