Difference between revisions of "NanoPi 2 Fire"

From FriendlyELEC WiKi
Jump to: navigation, search
(Deepin15 ARM)
(updated by API)
 
(60 intermediate revisions by 5 users not shown)
Line 4: Line 4:
 
[[File:NanoPi 2 Fire-A01.jpg|thumb|Front]]
 
[[File:NanoPi 2 Fire-A01.jpg|thumb|Front]]
 
[[File:NanoPi 2 Fire-B01.jpg|thumb|Back]]
 
[[File:NanoPi 2 Fire-B01.jpg|thumb|Back]]
* The NanoPi 2 Fire is a high performance ARM Board developed by FriendlyARM for Hobbysts, Makers and Hackers for IOT projects. It features Samsung's Cortex-A9 Quad Core S5P4418@1.4GHz SoC and 1G 32bit DDR3 RAM. It has a Gbps Ethernet port. It boots Android and Debian from a TF card. It integrates an HDMI and LCD interface. Its adoption of the Raspberry Pi's GPIO pin header makes it compatible with both Raspberry Pi's external GPIO modules and Arduino's shield boards. Its PCB dimension is 75 x 40 mm.
+
* The NanoPi 2 Fire is a high performance ARM Board developed by FriendlyARM for Hobbyists, Makers and Hackers for IOT projects. It features Samsung's Cortex-A9 Quad Core S5P4418@1.4GHz SoC and 1G 32bit DDR3 RAM. It has a Gbps Ethernet port. It boots Android and Debian from a TF card. It integrates an HDMI and LCD interface. Its adoption of the Raspberry Pi's GPIO pin header makes it compatible with both Raspberry Pi's external GPIO modules and Arduino's shield boards. Its PCB dimension is 75 x 40 mm.
  
==Features==
+
==Hardware Spec==
 
* CPU: S5P4418, 1.4GHz
 
* CPU: S5P4418, 1.4GHz
 
* RAM: 1GB DDR3
 
* RAM: 1GB DDR3
 
* Connectivity: Gbps Ethernet port
 
* Connectivity: Gbps Ethernet port
* PMU Power Management: AXP228, support software power-off, sleep and wakeup functions
 
 
* USB 2.0 Type A x 1
 
* USB 2.0 Type A x 1
 
* Debug Serial Port/UART0 x 1
 
* Debug Serial Port/UART0 x 1
Line 23: Line 22:
 
* PCB Dimension: 75 x 40mm
 
* PCB Dimension: 75 x 40mm
 
* Power: DC 5V/2A
 
* Power: DC 5V/2A
 +
* Temperature measuring range: -20℃ to 80℃
 
* OS: Android, Debian
 
* OS: Android, Debian
 +
[[File:NanoPi 2 Fire-B03.png|frameless|500px|compact]]
  
 
==Diagram, Layout and Dimension==
 
==Diagram, Layout and Dimension==
Line 158: Line 159:
 
::#SYS_3.3V: 3.3V power output
 
::#SYS_3.3V: 3.3V power output
 
::#VDD_5V: 5V power input/output. When the external device’s 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
 
::#VDD_5V: 5V power input/output. When the external device’s power is greater than the MicroUSB’s the external device is charging the board otherwise the board powers the external device. The input range is 4.7V ~ 5.6V
::#For more details please refer to the document:[http://wiki.friendlyarm.com/wiki/images/9/97/NanoPi2_Fire_1512B_Schematic.pdf NanoPi2_Fire_1512B_Schematic.pdf]
+
::#For more details please refer to the document:[http://wiki.friendlyelec.com/wiki/images/9/97/NanoPi2_Fire_1512B_Schematic.pdf NanoPi2_Fire_1512B_Schematic.pdf]
  
 
===Board Dimension===
 
===Board Dimension===
 
[[File:NanoPi2_Fire_1512B_Dimensions.png|frameless|500px|NanoPi 2 Fire Dimensions]]
 
[[File:NanoPi2_Fire_1512B_Dimensions.png|frameless|500px|NanoPi 2 Fire Dimensions]]
  
::For more details please refer to the document:[http://wiki.friendlyarm.com/wiki/images/b/b4/NanoPi2_Fire_1512B_Dimensions%28dxf%29.zip NanoPi2_Fire_1512B_Dimensions(dxf).zip]
+
::For more details please refer to the document:[http://wiki.friendlyelec.com/wiki/images/b/b4/NanoPi2_Fire_1512B_Dimensions%28dxf%29.zip NanoPi2_Fire_1512B_Dimensions(dxf).zip]
  
 
==Get Started==
 
==Get Started==
Line 173: Line 174:
 
* HDMI monitor or LCD   
 
* HDMI monitor or LCD   
 
* USB keyboard and mouse
 
* USB keyboard and mouse
* A Host running Ubuntu 14.04 64 bit system
+
* A Host running Ubuntu 18.04 64 bit system
  
===TF Card We Tested===
+
{{ResizeTFCardFS|NanoPi2-Fire}}
To make your NanoPi 2 Fire boot and run fast we highly recommand 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:
+
{{S5Pxx18HDMI|NanoPi2-Fire|arch/arm/plat-s5p4418/nanopi2/lcds.c}}
*SanDisk TF 8G Class10 Micro/SD TF card:
+
{{S5Pxx18MofidyKernelCommandLineOnHostPC|NanoPi2-Fire|sd-fuse_s5p4418}}
[[File:SanDisk MicroSD.png|frameless|100px|SanDisk MicroSD 8G]]
+
{{NanoPiStartToUse|NanoPi2-Fire}}
*SanDisk TF128G MicroSDXC TF 128G Class10 48MB/S:
+
{{FriendlyCoreGeneral|NanoPi2-Fire}}
[[File:SanDisk MicroSD-01.png|frameless|100px|SanDisk MicroSD 128G]]
+
{{FriendlyCoreRunX11Application|NanoPi2-Fire}}
*川宇 8G C10 High Speed class10 micro SD card:
+
{{FriendlyCoreS5Pxx18|NanoPi2-Fire}}
[[File:SanDisk MicroSD-02.png|frameless|100px|chuanyu MicroSD 8G]]
+
{{UbuntuXenial-Armhf-Install-Docker|NanoPi2-Fire}}
 
+
{{S5Pxx18Android|NanoPi2-Fire}}
===Make an Installation MicroSD Card===
+
{{S5P4418BuildFromSource|NanoPi2-Fire}}
====Under Windows====
+
{{S5P4418-KernelHeaderFile|NanoPi2-Fire}}
Please get the following files from here:[http://wiki.friendlyarm.com/wiki/nanopi2/download/ download link] to download image files: <br />
+
{{S5Pxx18ExternalModules|NanoPi2-Fire}}
 
+
{{S5Pxx18AccessHWUnderAndroid|NanoPi2-Fire}}
::{| class="wikitable"
+
{{S5Pxx18ConnectToLCDModules|NanoPi2-Fire}}
|-
+
{{S5P4418Resources|NanoPi2-Fire}}
|colspan=2|For LCD or HDMI output please use the following files:
+
{{DownloadUrl|NanoPi2-Fire}}
|-
+
{{TechSupport|NanoPi2-Fire}}
|nanopi2-debian-sd4g.img.zip      || Debian image files                 
+
{{MoreOS}}
|-
+
{{S5P4418ChangeLog}}
|nanopi2-android-sd4g.img.zip      || Android image files 
+
|-
+
|colspan=2|Flash Utility: 
+
|-
+
|win32diskimager.rar || Windows utility. Under Linux users can use "dd"
+
|-
+
|}
+
 
+
* Please uncompress these files. Insert an SD card(at least 4G) to a Windows PC, run the win32diskimager utility as administrator,On the utility's main window select your SD card's drive and the image files and click on "write" to start flashing the SD card.
+
* Please insert this card to your NanoPi 2 Fire and power on (with a 5V/2A power source). If the blue LED and green LED are blinking this indicates your NanoPi 2 Fire is 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 Firmware Package
+
<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>
+
 
+
====LCD/HDMI Resolution====
+
When system boots our uboot will check whether it is connected to an LCD. If it recognizes an LCD it will configure its resolution. By default our uboot configures the display to HDMI 720P.<br/>
+
If you want to reset the LCD resolution you can modify file "arch/arm/plat-s5p4418/nanopi2/lcds.c" in the kernel and recompile it.<br/>
+
If your NanoPi 2 connects an HDMI monitor and it runs Android it will automatically set the resolution to an appropriate HDMI mode by checking "EDID". If your NanoPi 2 connects an HDMI monitor and it runs Debian by default it will set the resolution to HDMI 720P and in this case you can set it to 1080P by modifying your kernel's configuration.<br/>
+
 
+
===Update Image Files in MicroSD Card From PC Host===
+
If you want to make some changes to the image files in your MicroSD card please follow steps below otherwise you can skip this section.<br/>
+
Please insert your MicroSD card to a PC host 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 will set 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.For a non-Android OS If it recognizes an LCD connected to the NanoPi 2 Fire it will load "uImage" from "boot" otherwise it will load "uImage.hdmi"<br />
+
However for Android these two files don't make any differences for whatever display device it detects. You can use your generated uImage to replace the existing one under "boot".<br />
+
For Debian if your generated kernel is for LCD you need to replace the existing uImage or if your kernel is for HDMI you need to replace the existing uImage.hdmi .<br />
+
 
+
===Run Android or Debian===
+
* Insert a MicroSD card with Android image files to your NanoPi 2 Fire, connect the NanoPi 2 Fire to an HDMI monitor and a 5V/2A power source the NanoPi 2 Fire will be automatically powered on. If you can see the blue LED flashing it means your board is working and you will see Android loading on the HDMI monitor. <br/>
+
1) If you connect the NanoPi 2 Fire to an HDMI monitor you need to use a USB mouse and a USB keyboard to operate. If you connect it to an LCD with capacitive touch you can operate directly on the LCD.
+
2)If you want to do kernel development you'd better have a serial board which allows you to operate the board via a serial terminal.
+
* Here is a case in which we connect a NanoPi 2 Fire to a PC running Ubuntu and Minicom via a serial cable you will see system messages output to the PC’s minicom terminal:[[File:PSU-ONECOM01.png|frameless|400px|PSU-ONECOM01]]
+
* Under Debian the password for "root" is "fa".
+
 
+
===Login Debian via VNC or SSH===
+
If your NanoPi 2 Fire is not connected to a display device you can download and install a "VNC Viewer" on your PC or mobile phone and login the NanoPi 2 Fire via VNC. Its default password is "fa123456". Here is a screenshot which shows how it looks like when users login the NanoPi 2 Fire from an iPhone via VNC:<br />
+
[[File:iphone6-vnc-nanopi2.png|frameless|400px|VNC to NanoPi2]]
+
<br />
+
You can login via "SSH -l root 192.168.8.1" too and the default password for "root" is "fa".
+
<br />
+
 
+
==Play with Debian==
+
===Ethernet Connection===
+
If the NanoPi 2 Fire is connected to a network via Ethernet before it is powered on it will automatically obtain an IP after it is powered on. If it is not connected via Ethernet or its DHCP is not activated obtaining an IP will fail and system will hang on for about 15 to 60 seconds.
+
* 1) Setup MAC Address
+
The NanoPi 2 Fire by default doesn't have a valid MAC address. If the board connects a network successfully it will automatically generates a random MAC in "/etc/network/interfaces.d/eth0". Users can change it to a self-defined valid one:
+
<syntaxhighlight lang="bash">
+
vi /etc/network/interfaces.d/eth0
+
</syntaxhighlight>
+
Here is the content of a sample configuration file:
+
<syntaxhighlight lang="bash">
+
auto eth0
+
allow-hotplug eth0
+
iface eth0 inet dhcp
+
hwaddress 76:92:d4:85:f3:0f
+
</syntaxhighlight>
+
The "hwaddress" specifies the MAC address. Here the "76:92:d4:85:f3:0f" is a random MAC. We suggest users change it to a valid one<br />
+
Note: when you reset the MAC please make sure your MAC meets IEEE's definition otherwise it will cause unexpected issues.<br/>
+
After you make your change, save, exit and reboot your board or run the following commands to restart the network:
+
<syntaxhighlight lang="bash">
+
systemctl restart networking
+
</syntaxhighlight>
+
 
+
===Install Debian Packages===
+
We provide a Debian jessie image. You can install Jessie's packages by commanding "apt-get". If this is your first installation you need to update the package list by running the following command:
+
<syntaxhighlight lang="bash">
+
apt-get update
+
</syntaxhighlight>
+
You can install your preferred packages. For example if you want to install an FTP server you can do this:
+
<syntaxhighlight lang="bash">
+
apt-get install vsftpd
+
</syntaxhighlight>
+
Note: you can change your download server by editting "/etc/apt/sources.list". You can get a complete server list from [http://www.debian.org/mirror/list]. You need to select the one with "armhf".
+
 
+
==Make Your Own OS Image==
+
 
+
===Setup Development Environment===
+
 
+
===Install Cross Compiler===
+
Please download the compiler package:
+
<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>
+
 
+
Then add the compiler's directory to "PATH" by appending the following lines in "~/.bashrc":
+
<syntaxhighlight lang="bash">
+
export PATH=/opt/FriendlyARM/toolchain/4.9.3/bin:$PATH
+
export GCC_COLORS=auto
+
</syntaxhighlight>
+
 
+
Execute "~/.bashrc" to make the changes into effect. Please note that there is a space after ".":
+
<syntaxhighlight lang="bash">
+
. ~/.bashrc
+
</syntaxhighlight>
+
 
+
This compiler is a 64-bit one therefore it cannot be run on a 32-bit LINUX. After the compiler is installed you can verify it by running the following commands:
+
<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>
+
 
+
===Compile U-Boot===
+
Download the U-Boot source code and compile it. Please note the github's branch is 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>
+
 
+
After your compilation succeeds a u-boot.bin will be generated. If you want to test it please flash it to your installation MicroSD card via fastboot. Here is how you can do it:<br />
+
1) On your PC host please run "sudo apt-get install android-tools-fastboot" to install the fastboot utility<br />
+
2) Connect your NanoPi 2 Fire to your PC host via a serial cable (e.g. PSU-ONECOME). Press the enter key within two seconds right after you power on your NanoPi 2 Fire and you will enter uboot's command line mode:<br />
+
3) After type "fastboot" and press "enter" you will enter the fastboot mode:<br />
+
4) Connect your NanoPi 2 Fire to this PC host via a microUSB cable and type the following command to flash the u-boot.bin:<br />
+
<syntaxhighlight lang="bash">
+
fastboot flash bootloader u-boot.bin
+
</syntaxhighlight>
+
<br />
+
Warning: you cannot update this MicroSD card by commanding "dd". This command which will cause trouble when booting the NanoPi 2 Fire.<br />
+
 
+
===Prepare mkimage===
+
You need the mkimage utility to compile a U-Boot source code package. Please make sure this utility works well on your host before you start compiling a uImage.<br />
+
You can install this utility by either commanding "sudo apt-get install u-boot-tools" or following the commands below:
+
<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>
+
 
+
===Compile Linux kernel===
+
====Compile Kernel====
+
* Download Kernel Source Code
+
<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>
+
The NanoPi 2 Fire's kernel source code lies in the "nanopi2-lollipop-mr1" branch.
+
* Compile Android Kernel
+
<syntaxhighlight lang="bash">
+
make nanopi2_android_defconfig
+
touch .scmversion
+
make uImage
+
</syntaxhighlight>
+
* Compile Debian Kernel
+
<syntaxhighlight lang="bash">
+
make nanopi2_linux_defconfig
+
touch .scmversion
+
make uImage
+
</syntaxhighlight>
+
After your compilation succeeds a uImage will be generated in the "arch/arm/boot/uImage" directory. This kernel is for HDMI. You can use it to replace the existing uImage.hdmi<br/>
+
If you want to generate a kernel for LCD you can do it this way:
+
<syntaxhighlight lang="bash">
+
touch .scmversion
+
make nanopi2_linux_defconfig
+
make menuconfig
+
  Device Drivers -->
+
    Graphics support -->
+
      Nexell Graphics -->
+
        [*] LCD
+
        [ ] HDMI
+
make uImage
+
</syntaxhighlight>
+
After your compilation succeeds a uImage will be generated for LCD. You can use it to replace the existing uImage.
+
 
+
====Compile Kernel Modules====
+
Android contains kernel modules which are in the "/lib/modules" directory in the system section. If you want to add your own modules to the kernel or you changed your kernel configurations you need to recompile these new modules.<br />
+
Compile Original Kernel Modules:
+
<syntaxhighlight lang="bash">
+
cd linux-3.4.y
+
make CROSS_COMPILE=arm-eabi- modules
+
</syntaxhighlight>
+
Here we have two new modules and we can compile them by following the commands below:
+
<syntaxhighlight lang="bash">
+
cd /opt/FriendlyARM/s5p4418/android
+
./vendor/friendly-arm/build/common/build-modules.sh
+
</syntaxhighlight>
+
The "/opt/FriendlyARM/s5p4418/android" directory points to the top directory of Android source code. You can get more details by specifying option "-h".<br />
+
After your compilation succeeds new modules will be generated
+
 
+
===Compile Android===
+
 
+
* Install Cross Compiler
+
We recommend installing 64 bit Ubuntu 14.04 on your PC host.
+
<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>
+
For more details please refer to https://source.android.com/source/initializing.html 。
+
 
+
* Download Source Code
+
You need to use repo to get the Android source code. Please refer to 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>
+
The "android" directory is the working directory.
+
 
+
* Compile System Package
+
<syntaxhighlight lang="bash">
+
source build/envsetup.sh
+
lunch aosp_nanopi2-userdebug
+
make -j8
+
</syntaxhighlight>
+
After your compilation succeeds an image will be generated in the "out/target/product/nanopi2/" directory.
+
 
+
==Connect NanoPi 2 Fire to External Modules==
+
===Connect NanoPi 2 Fire to USB Camera(FA-CAM202)===
+
*In this usecase the NanoPi 2 Fire runs Debian. If you connect your NanoPi 2 Fire to our LCD after Debain is fully loaded please click on "other"-->"xawtv9" on the left bottom of the GUI and the USB Camera application will be started. After enter "welcome  to  xawtv!" please click on "OK" to start exploring.
+
[[File:USB-camera-nanopi2.png|frameless|500px|USB camera]]
+
[[File:USB-camera-nanopi2-01.png|frameless|500px|USB camera-01]]
+
===Connect NanoPi 2 Fire to CMOS 5M-Pixel Camera===
+
*In this usecase the NanoPi 2 Fire runs Android5.1. If you connect your NanoPi 2 Fire to our LCD after Debain is fully loaded please click on the "Camera" icon the  application will be started.
+
[[File:CMOS-camera-nanopi2.png|frameless|500px|CMOS camera]]
+
===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 2 Fire runs Debian users can use OpenCV APIs to access a USB Camera device<br>
+
Here is a guideline on how to use OpenCV with C++ on the NanoPi 2 Fire<br>
+
1. Preparations
+
<syntaxhighlight lang="bash">
+
---Firstly you need to make sure your NanoPi 2 Fire is connected to the internet.
+
  Login your NanoPi 2 Fire via a serial terminal or SSH. After login please type your username(root) and password(fa):
+
---Run the following commands:
+
</syntaxhighlight>
+
<br>
+
<syntaxhighlight lang="bash">
+
#apt-get update
+
(The OS images we provide for the NanoPi 2 Fire by default have the vi utility. However we suggest you install the vim utility)
+
#apt-get install vim
+
#apt-get install libcv-dev libopencv-dev
+
</syntaxhighlight>
+
 
+
2. Make sure your USB camera works with the NanoPi 2 Fire. You can test your camera with NanoPi 2 Fire's camera utility.<br>
+
 
+
3. Check your camera device:
+
<syntaxhighlight lang="bash">
+
#ls /dev/video + "Tab" key (This lists available USB camera devices. In our test case video9 was available and video0 to video8 were occupied)
+
</syntaxhighlight>
+
 
+
4. OpenCV's code sample:
+
<syntaxhighlight lang="bash">
+
#cd /home/fa
+
#vim test.cpp
+
</syntaxhighlight>
+
<br>
+
<syntaxhighlight lang="bash">
+
#include "opencv2/opencv.hpp"
+
 
+
using namespace cv;
+
 
+
int main(int, char**)
+
{
+
    VideoCapture cap(0); // open the default camera
+
    if(!cap.isOpened())  // check if we succeeded
+
        return -1;
+
 
+
    Mat edges;
+
    namedWindow("edges",1);
+
    for(;;)
+
    {
+
        Mat frame;
+
        cap >> frame; // get a new frame from camera
+
        cvtColor(frame, edges, CV_BGR2GRAY);
+
        GaussianBlur(edges, edges, Size(7,7), 1.5, 1.5);
+
        Canny(edges, edges, 0, 30, 3);
+
        imshow("edges", edges);
+
        if(waitKey(30) >= 0) break;
+
    }
+
    // the camera will be deinitialized automatically in VideoCapture destructor
+
    return 0;
+
}
+
</syntaxhighlight>
+
Compile the code sample:
+
<syntaxhighlight lang="bash">
+
#g++ test.cpp -o test -lopencv_core -lopencv_highgui -lopencv_imgproc
+
</syntaxhighlight>
+
 
+
If it is compiled successfully a "test" executable will be generated:<br>
+
5. Note: the NanoPi 2 Fire has nine video devices. However this OpenCV's code sample defines a maximum of 8 cameras can be accessed therefore one video needs to be removed. Here we removed video0
+
<syntaxhighlight lang="bash">
+
#rm /dev/video0
+
#mv /dev/video9 /dev/video0
+
</syntaxhighlight>
+
 
+
6. Connect NanoPi 2 Fire to USB Keyboard & Run the Following Command:
+
<syntaxhighlight lang="bash">
+
#./test
+
</syntaxhighlight>
+
 
+
This is what you expect to observe:<br>
+
[[File:OpenCV-Fire.png|frameless|600px|OpenCV-Fire]]
+
 
+
==Extend NanoPi 2 Fire's TF Card Section==
+
===For Debian===
+
* Please run the following commands on a PC host's terminal:
+
<syntaxhighlight lang="bash">
+
sudo umount /dev/sdx?
+
sudo parted /dev/sdx unit % resizepart 2 100 unit MB print
+
sudo resize2fs -f /dev/sdx2
+
</syntaxhighlight>
+
 
+
===For Android===
+
* Please run the following commands on a PC host's terminal:
+
<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)
+
 
+
==More OS Support==
+
===Ubuntu-Mate===
+
* Please go to this link [https://www.mediafire.com/folder/28mhgfosn62d5/Ubuntu-Mata] to download the image files
+
* Please uncompress it and flash the image file to a TF card with win32diskimager under Windows
+
* After it is done you can boot your NanoPi 2 Fire with this card
+
* Login name: "root" or "fa", Password: fa
+
Note: this UbuntuMate works with both NanoPi 2 and NanoPi 2 Fire
+
 
+
===Ubuntu-Core===
+
* Please go to this link [http://pan.baidu.com/s/1hrbFm0s] to download the image files
+
* Please uncompress it and flash the image file to a TF card with win32diskimager under Windows
+
* After it is done you can boot your NanoPi 2 Fire with this card
+
* Login name: "root" or "fa", Password: fa
+
Note: this Ubuntu-Core is a basic verson which has support for Ethernet and SSH. If you need other functions and modules you can add what you need by apt.
+
 
+
===Kali===
+
* Please go to this link [https://www.mediafire.com/folder/nbuvkg07p74er/Kali] to download the image files
+
* Please prepare an 8G High Speed MicroSD card, insert it to a Linux host and do "sudo fdisk -l" to check its device name, i.e. "/dev/sd*"
+
* Please copy the image files to the card by running the following commands as root:
+
<syntaxhighlight lang="bash">
+
xzcat kali-2.0-nanopi2.img.xz | dd of=<YOURDEVICE> bs=1m
+
</syntaxhighlight>
+
* After it is done you can boot your NanoPi 2 Fire with this card.
+
Note: this is offered by Kali and FriendlyARM doesn't provide technical support for it.
+
 
+
===Deepin15 ARM===
+
* Please go to this link [https://www.mediafire.com/folder/rh97bk9o3rpiv/deepin15] to download the image files
+
* Please uncompress the file and you will get a 16g.img file which is the image file for MicroSD card.
+
<syntaxhighlight lang="bash">
+
tar -xf deepin15_nanopi2_armhf_16g.tar.gz
+
</syntaxhighlight>
+
* Please prepare an 16G High Speed MicroSD card, insert it to a Linux host and do "sudo fdisk -l" to check its device name, i.e. "/dev/sd*"
+
* Please flash the image files to the card by running the following command as root(in our case our card was recognized as "/dev/sdc"):
+
<syntaxhighlight lang="bash">
+
sudo dd if=16g.img of=/dev/sdc
+
</syntaxhighlight>
+
 
+
(This process takes a while which can be up to one hour)
+
 
+
* After it is done you can boot your NanoPi 2 Fire with this card
+
 
+
 
+
Notes:<br>
+
1. The password for login name "deepin" is "deepin". The password for login name "root" is "admin".<br>
+
2. The initial booting of Deepin15 takes a relative long time for it generates some configuration files.<br>
+
3. If WIFI is activated in your system booting might take longer. In this case please wait for the sound and wifi icons on the right bottom of the GUI to appear before you start any action.<br>
+
<syntaxhighlight lang="bash">
+
    ARM code: http://packages.deepin.com/armhf/<br>
+
 
+
    NanoPi 2 Image: http://cdimage.deepin.com/armhf/15/beta1.0/<br>
+
 
+
    NanoPi 2 Image Installation Instruction; http://bbs.deepin.org/forum.php?mod=viewthread&tid=36670<br>
+
 
+
    Forum for Migrating Deepin15 to ARM: http://bbs.deepin.org/<br>
+
 
+
</syntaxhighlight>
+
Note: this is offered by the Deepin15 team and FriendlyARM doesn't provide technical support for it.
+
 
+
==Resources==
+
* Schematic ([http://wiki.friendlyarm.com/wiki/images/9/97/NanoPi2_Fire_1512B_Schematic.pdf NanoPi2_Fire_1512B_Schematic.pdf])
+
* Dimensions ([http://wiki.friendlyarm.com/wiki/images/b/b4/NanoPi2_Fire_1512B_Dimensions%28dxf%29.zip NanoPi2_Fire_1512B_Dimensions(dxf).zip])
+
* S5P4418 Datasheet ([http://wiki.friendlyarm.com/wiki/images/a/a7/Pi2_SOC_DS_0.1.pdf S5P4418_Datasheet_0.1.pdf])
+
 
+
==External Links==
+
* [http://www.friendlyarm.com/Forum/viewtopic.php?f=17&t=73  How to setup Qt development environment for NanoPi 2 & NanoPi 2 Fire]
+
 
+
==Update Log==
+
===Jan-29-2016===
+
* Add 9 More OS Support
+
 
+
===Feb-02-2016===
+
* Add 9.1 Ubuntu-Mate
+
* Add 9.2 Ubuntu-Core
+
* Add 11 External Links
+
 
+
===Mar-03-2016===
+
* Modified Section 4.5
+
 
+
===Mar-09-2016===
+
* Corrected a typo
+

Latest revision as of 08:14, 3 July 2024

查看中文

Contents

1 Introduction

Overview
Front
Back
  • The NanoPi 2 Fire is a high performance ARM Board developed by FriendlyARM for Hobbyists, Makers and Hackers for IOT projects. It features Samsung's Cortex-A9 Quad Core S5P4418@1.4GHz SoC and 1G 32bit DDR3 RAM. It has a Gbps Ethernet port. It boots Android and Debian from a TF card. It integrates an HDMI and LCD interface. Its adoption of the Raspberry Pi's GPIO pin header makes it compatible with both Raspberry Pi's external GPIO modules and Arduino's shield boards. Its PCB dimension is 75 x 40 mm.

2 Hardware Spec

  • CPU: S5P4418, 1.4GHz
  • RAM: 1GB DDR3
  • Connectivity: Gbps Ethernet port
  • USB 2.0 Type A x 1
  • Debug Serial Port/UART0 x 1
  • microSD Slot x 1
  • microUSB x 1: for data transmission and power input
  • LCD Interface: 0.5 mm pitch SMT FPC seat, for full-color LCD (RGB: 8-8-8)
  • HDMI: HDMI 1.4A, Type-A, 1080P60
  • DVP Camera Interface: 0.5mm spacing FPC socket. It includes ITU-R BT 601/656 8-bit, I2C and IO
  • GPIO: 2.54mm spacing 40pin, compatible with Raspberry Pi's GPIO. It includes UART, SPI, I2C, PWM, IO etc
  • Button: Power Button x 1, Reset Button x 1
  • LED: LED for Power Indication x 1, System LED x 1
  • PCB Dimension: 75 x 40mm
  • Power: DC 5V/2A
  • Temperature measuring range: -20℃ to 80℃
  • OS: Android, Debian

compact

3 Diagram, Layout and Dimension

3.1 Layout

NanoPi 2 Fire Layout
  • GPIO Pin Spec
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
  • 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,10 NC
11 VSYNC
12 HREF
14 PCLK
16-23 Data bit7-0
  • RGB LCD Interface Pin Spec
Pin# Name Description
1, 2 VDD_5V 5V output, LCD power
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's data transmission
42 I2C2_SDA I2C2 data signal, for capacitive touch's data transmission
43 GPIOC16 interrupt pin for capacitive touch, used with I2C2
44 NC not connected
Note
  1. SYS_3.3V: 3.3V power output
  2. VDD_5V: 5V power input/output. When the external device’s power is greater than the MicroUSB’s the external device is charging the board otherwise the board powers the external device. The input range is 4.7V ~ 5.6V
  3. For more details please refer to the document:NanoPi2_Fire_1512B_Schematic.pdf

3.2 Board Dimension

NanoPi 2 Fire Dimensions

For more details please refer to the document:NanoPi2_Fire_1512B_Dimensions(dxf).zip

4 Get Started

4.1 Essentials You Need

Before play with your NanoPi 2 Fire please get the following items ready

  • NanoPi 2 Fire
  • 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 and mouse
  • A Host running Ubuntu 18.04 64 bit system

4.2 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.3 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 NanoPi2-Fire 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 NanoPi2-Fire 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.4 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.5 Run Android or Linux (TODO)

  • 将制作好SD卡插入NanoPi2-Fire,连接HDMI,连接电源(5V 2A), NanoPi2-Fire会从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 Set Audio Device

If your system has multiple audio devices such as HDMI-Audio, 3.5mm audio jack and I2S-Codec you can set system's default audio device by running the following commands.

  • After your board is booted run the following commands to install alsa packages:
$ apt-get update
$ apt-get install libasound2
$ apt-get install alsa-base
$ apt-get install alsa-utils
  • After installation is done you can list all the audio devices by running the following command. Here is a similar list you may see after you run the command:
$ aplay -l
card 0: HDMI
card 1: 3.5mm codec
card 2: I2S codec

"card 0" is HDMI-Audio, "card 1" is 3.5mm audio jack and "card 2" is I2S-Codec. You can set default audio device to HDMI-Audio by changing the "/etc/asound.conf" file as follows:

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

If you change "card 0" to "card 1" the 3.5mm audio jack will be set to the default device.
Copy a .wav file to your board and test it by running the following command:

$ aplay /root/Music/test.wav

You will hear sounds from system's default audio device.
If you are using H3/H5/H2+ series board with mainline kernel, the easier way is using npi-config


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 Make Your Own OS Image

7.1 Install Cross Compiler

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

7.2 Compile Linux kernel for FriendlyCore/Lubuntu/EFlasher

7.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 NanoPi2-Fire'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.

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

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

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

7.5 Compile Android 7.1.2

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

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

NanoPi2-Fire 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

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

8 Build Kernel Headers Package

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

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

8.2 Install the required packages

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

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

9 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

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

10 Connect NanoPi2-Fire to External Modules

10.1 Connect NanoPi2-Fire to USB Camera(FA-CAM202)

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

10.2 Connect NanoPi2-Fire to CMOS 5M-Pixel Camera

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

  • If your NanoPi2-Fire 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

10.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 NanoPi2-Fire 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 NanoPi2-Fire:

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

./demo

opencv is successfully started

10.4 Connect NanoPi2-Fire 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 NanoPi2-Fire is connected to the Matrix GPS module, after the NanoPi2-Fire 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 NanoPi2-Fire to the Matrix-GPS:
GPS_NanoPC-T2

Connection Details:

Matrix-GPS NanoPi2-Fire
RXD Pin11
TXD Pin12
5V Pin29
GND Pin30

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

12 Connect NanoPi2-Fire 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

13 Resources

14 Source Code and Image Files Download Links

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

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

16 More OS Support

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

17 Update Log

17.1 2023-01-09

17.1.1 FriendlyCore:

  • optimized the systemd service

17.2 2020-10-26

  • FriendlyCore, Lubuntu:

Fix Bluetooth stability issue

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

17.4 2019-11-26

  • FriendlyCore:

Pre-installed OpenCV 4.1.2

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

17.6 2019-10-18

  • Android7, FriendlyCore, Lubuntu:

Fixed audio playback issue.

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

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

17.9 2019-06-25

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

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

17.11 2019-01-24

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

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

17.13 March-04-2016

  • Released English version

17.14 March-09-2016

  • Corrected a typo

17.15 March-23-2016

  • Added section 11

17.16 March-27-2016

  • Corrected expression errors

17.17 April-08-2016

  • Added section 6.4.2 and 7.4
  • Updated section 6.5

17.18 June-30-2016

  • Added section 9 and 10

17.19 Sep-04-2016

  • Updated section 5.2.2 and 10.1.1

17.20 Sep-27-2016

  • Updated section 5.2.2, 7.5 and 8.2

17.21 Nov-2-2016

  • Updated section 6.2, 6.3, 6.4 and 12

17.22 Nov-17-2016

  • Added section 10.6

17.23 Dec-7-2016

  • Added section 6.6
  • Updated section 7.5

17.24 June-13-2016

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

17.25 June-20-2016

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