From FriendlyARM WiKi
Jump to: navigation, search



  • The Smart4418 CPU board is a quad core Cortex A9 CPU board designed and developed by FriendlyARM for industrial applications. As a successor of the Smart210 CPU board it uses the Samsung Quad Core Cortex-A9 S5P4418 SoC with dynamic frequency scaling up to 1.4GHz. The standard Smart4418 CPU board has 1GB DDR3 RAM and 8GB eMMC. It has the AXP229 PMU enabling software power off/on and wake-up functions. In addition its Gbps Ethernet and audio jack make it suitable for various industrial applications.
  • The Smart4418 CPU board has 2.0mm pitch double row pin headers(P1, P2 and P4) containing 174 pins in total. These pins contain most popular interface pins. By default we have P1 and P2 soldered on the board and leave P4 for users' applications. It works with various FriendlyARM LCDs e.g. 3.5"LCD, 4.3"LCD, 5"LCD, 7"LCD and 10.1"LCD.
  • In addition we have a Smart4418/6818SDK carrier board which enables the Smart4418 CPU board's Gbps Ethernet.In addition FriendlyARM will soon release a Samsung Octa Core Cortex-A53 S5P6818@1.4GHz based board which is pin to pin compatible to the Smart4418 CPU board.
  • For more details about the Smart4418 SDK carrier board V1606 refer to Smart4418SDK 1606.


  • CPU: Samsung S5P4418 Quad Core Cortex-A9, with dynamic frequency scaling from 400M Hz to 1.4G Hz
  • PMU Power Management Unit: AXP228. it supports software power-off and wake-up functions.
  • DDR3 RAM: 1GB 32bit DDR3 RAM
  • Ethernet: Gbps Ethernet(RTL8211E) with unique MAC
  • eMMC: 8GB
  • Audio: 1 x audio codec chip, 1 x onboard Microphone and 1 x audio jack
  • LED: 1 x Power LED, 2 x GPIO LED
  • Others: onboard thermistor
  • PCB Dimension: 74 x 55 mm, Six-Layer
  • Power: DC 5V, up to 1.2A
  • Temperature measuring range: -40℃ to 80℃
  • OS/Software: u-boot, Android5.1/4.4, Debian8, ubuntu-core
  • 3 x 2.0mm pitch double row pin header, 174 pins in total:
    • USB 2.0 - Host x1, OTG x1
    • Video output/Display - RGB Parallel I/F (24-bit), LVDS and HDMI 1.4a
    • Video input - DVP Camera interface, ITU-R BT 601/656 8-bit and MIPI-CSI
    • Audio input - Microphone
    • Audio output - Audio jack (with headset detection) and HDMI audio
    • Ethernet - 10/100/1000Mbps Ethernet x 1
    • ADC - CPU internal ADC, 7 channels, 12-bit, range: 0 ~ 1.8V
    • External interface - SDIO/MMC x2, SPI x2, I2C x3, UART x5, PWM x3, GPIOs x24
    • Others - Power key input, RESET input, RESET output, RTC battery input

Pin Spec

P1 P2
Pin# Name Pin# Name Pin# Name Pin# Name
11 MMC0_D0 12 MMC1_D0 11 CAM0_D0 12 CAM0_D1
13 MMC0_D1 14 MMC1_D1 13 CAM0_D2 14 CAM0_D3
15 MMC0_D2 16 MMC1_D2 15 CAM0_D4 16 CAM0_D5
17 MMC0_D3 18 MMC1_D3 17 CAM0_D6 18 CAM0_D7
33 GPIOD1/PWM0 34 I2C0_SCL 33 I2C1_SDA 34 I2C1_SCL
35 GPIOC13/PWM1 36 I2C0_SDA 35 USB_OTG_ID 36 SPI0_CS
41 LCD_B0 42 LCD_B1 41 VBUS_5V 42 SPI0_CL
43 LCD_B2 44 LCD_B3 43 LVDS_CLKP 44 GPIOB25
45 LCD_B4 46 LCD_B5 45 LVDS_CLKM 46 DGND
47 LCD_B6 48 LCD_B7 47 LVDS_Y0P 48 LAN_MDI1_N
49 LCD_G0 50 LCD_G1 49 LVDS_Y0M 50 LAN_MDI1_P
51 LCD_G2 52 LCD_G3 51 LVDS_Y1P 52 LAN_MDI0_N
53 LCD_G4 54 LCD_G5 53 LVDS_Y1M 54 LAN_MDI0_P
55 LCD_G6 56 LCD_G7 55 LVDS_Y2P 56 LINK_LED
57 LCD_R0 58 LCD_R1 57 LVDS_Y2M 58 SPEED_LED
59 LCD_R2 60 LCD_R3 59 LVDS_Y3P 60 DGND
61 LCD_R4 62 LCD_R5 61 LVDS_Y3M 62 HP_DETECT
63 LCD_R6 64 LCD_R7 63 HP-R 64 HP-L
69 DGND 70 BOOT_CS 69 Mic-P 70 Mic-N
Pin# Name Pin# Name
21 GPIOB9 22 ADC1
23 GPIOB26 24 ADC3
25 GPIOC4 26 ADC4
27 AliveGPIO3 28 ADC5
31 GPIOC14/PWM2 32 ADC7
  1. VDD_5V: Supply voltage, range:4.7 ~ 5.6V. We recommend a 5V/1.2A(MAX) power. You can lower the clock to decrease the power consumption. When the clock is lowered by 200MHz the power consumption roughly decreases 0.5W .
  2. BOOT_CS: Boot chip selection. When it is not connected or pulled up the board boots from eMMC otherwise it boots from SD card
  3. NRESETIN: Reset input. Activated when it is low. A reset signal is input to CPU from this pin
  4. NRESETOUT: Reset output. Activated when it is low. CPU's reset signal outputs to this pin.
  5. RTC_BATT: RTC's input, direct connection to a 3V power source. If the CPU board is powered on the RTC seat is powered by 3.3V external power otherwise when the CPU board is not powered on it is powered by the RTC battery.
  6. ADC1~7: CPU internal ADC, 12-bit, 7 channels 1~7, range:0 ~ 1.8V
  7. 10/100M Ethernet mode: LAN_MDI1_N/P=RX-/+, LAN_MDI0_N/P=TX-/+, four pins connected to RJ45
  8. 10/100/1000M Ethernet mode: LAN_MDI0_N/P~LAN_MDI3N/P, all eight pins connected to RJ45
  9. For more details refer to our carrier board's design:Smart210/4418 SDK
    • For more details about the Smart4418 SDK carrier board V1606 refer to Smart4418SDK 1606.
  10. Smart4418 Schematic in pdf

Board Dimension

For more details refer to the dxf file:Smart4418-1608-Dimension(dxf).zip

Notes in Hardware Design


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

Carrier Board

Smart4418SDK Comparison
Smart210/4418 SDK

Get Started

Essentials You Need

Before starting to use your Smart4418 get the following items ready

  • Smart4418 CPU board and Smart210/4418 SDK carrier board
  • Standard SD card: Class10 or above 8GB SDHC card
  • A DC 12V/2A power is a must
  • HDMI monitor or LCD
  • USB keyboard and mouse
  • A host computer running Ubuntu 14.04 64 bit system

Make an Installation SD Card

Boot Smart4418 from SD Card

Get the following files from here download link:

  • Get a 8G SDHC card and backup its data if necessary
Image Files Debian image file with X Window Debian image file with X Window and WiFi configured as AP Android4.4 image file with support for 4G LTE Android5.1 image file Ubuntu core with Qt Embedded
Flash Utility:
win32diskimager.rar Windows utility. Under Linux users can use "dd"
  • Uncompress these files. Insert an SD card(at least 8G) 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 Smart4418's boot slot, press and hold the boot key and power on (with a 12V/2A power source). If the PWR LED is on and LED1 is blinking this indicates your Smart4418 has successfully booted.

Flash Image to Smart4418's eMMC

  • Download eflasher

Get the eflasher utility s5p4418-eflasher-sd8g-xxx-full.img.7z
This package includes a Ubuntu Core, Debian, Android 5 and Android 4.4 image files;
Get the Windows utility: win32diskimager.rar;

  • Flash eflasher Image

Extract the .7z package and you will get .img files.Insert an SD card(at least 8G) 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.
If your PC runs Linux you can use the dd command to flash a .img file to the SD card;

  • Flash image to eMMC

Insert this card into your Smart4418 SDK carrier board, connect the board to an HDMI monitor or an LCD, press and hold the boot key and power on (with a 12V/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.

Make Installation Card under Linux Desktop

  • 1) Insert your SD card into your host PC 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
cd sd-fuse_nanopi2
  • 3) Make Android SD Card
./ /dev/sdx

(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) Here is how to make a Debian SD card
./ /dev/sdx debian

Extend Smart4418's SD Card Section

  • When Debian/Ubuntu boots it will automatically extend its SD card's section. On its initial booting the system will extend the root file system and other sections.
  • Under Android users need to extend the section by using the following commands:
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)

LCD/HDMI Resolution

When system boots our uboot will check whether it is connected to an LCD or 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 Smart4418 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 Smart4418 is connected an HDMI monitor and it runs Debian by default it will set the resolution to HDMI 720P. 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 steps below otherwise you can skip this section.
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:
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":
Check the current Command Line:

cd sd-fuse_nanopi2/tools
./fw_printenv /dev/sdc | grep bootargs

Android 5.1.1_r6 starts SELinux. By default it is enforcing. You can change it this way:

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

This sets it to "permissive". The "XXX" stands for the original bootargs' value.

2) Update Kernel
Our customized uboot will check the LCD type when it boots.
For a non-Android OS If it recognizes an LCD connected to the Smart4418 it will load "uImage" from "boot" otherwise it will load "uImage.hdmi".
For Android it doesn't make any difference what display device is detected. You can use your generated uImage to replace the existing one under "boot".
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.

Run Android or Debian

  • Insert an SD card with Android/Debian image file into your Smart4418's carrier board, connect the board to an HDMI monitor, switch S2 to "SDBOOT", power on the board the Smart4418 will be booted from the SD card. If you can see the PWR LED on and the LED1 flashing it means your board is working and you will see Android/Debain being loaded on the HDMI monitor.

1) If you connect the Smart4418 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 need to use a serial communication board, ie a PSU-ONECOM board, which will allow you to operate the board via a serial terminal.

  • Here is a setup in which we connect the COM0 on the Smart4418's V1606 SDK carrier board to a PC running Ubuntu and Minicom via a serial cable you will see system messages output to the PC’s minicom terminal


  • Under Debian the password for "root" is "fa"

Login Debian via VNC or SSH

If your Smart4418 is not connected to a display device and your board runs the "-wifiap.img" image you can login to your Smart4418's nanopi2-wifiap(the default password is "123456789") via a mobile phone. You can download and install a "VNC Viewer" from here on mobile phone and login to the Smart4418 via VNC. Its default password is "fa123456". Here is a screenshot which shows how it looks like when users login to the Smart4418 from an iPhone via VNC:
VNC to NanoPi2
You can login via "SSH -l root" too and the default password for "root" is "fa"

To make SSH session run faster turn off the WiFi's power saving mode by using the following command:

iwconfig wlan0 power off

Working with Debian

Ethernet Connection

  • If the Smart4418 is connected to a network via Ethernet before it is powered on, it will automatically obtain an IP after it is powered up.

Wireless Connection

Open the file /etc/wpa_supplicant/wpa_supplicant.conf and append the following lines:


The "YourWiFiESSID" and "YourWiFiPassword" need to be replaced with your actual ESSID and password.
Save, exit and run the following commands to connect to a WiFi:

ifdown wlan0
ifup wlan0

If your WiFi password has special characters or you don't want your password saved as plain text you can use "wpa_passphrase" to generate a psk for your WiFi password. Here is how you can do it:

wpa_passphrase YourWiFiESSID

Following the prompt type in your password and open the file /etc/wpa_supplicant/wpa_supplicant.conf you will find that your password has been changed and your can delete your plain text password.

If your AP mode is turned on you need to turn it off. You can do it by using the following commands:

turn-wifi-into-apmode no

Setup Wi-Fi AP

You can follow the steps below to setup Wi-Fi AP:

turn-wifi-into-apmode yes

Reboot the system as prompted. By default the AP's name is "nanopi2-wifiap" and the password is 123456789.

Now you are able to find the "nanopi2-wifiap" from a host PC and connect to it. If the connection is successful you will be able to SSH to this Smart4418 at "":

ssh root@

The password for it is "fa".

To make SSH run faster turn off the WiFi's power saving mode by using the following command:

iwconfig wlan0 power off

You can check the WiFi mode via the following command:

cat /sys/module/bcmdhd/parameters/op_mode

If the result is "2" it means it is currently working as a WiFi AP.If you want to switch back to the Station mode you can do it this way:

turn-wifi-into-apmode no


Here are the steps to transfer a file from Smart4418 to a mobile phone. Run the following command to search a surrounding Bluetooth device:

hcitool scan

In our example a mobile phone was detected and the following messages were listed:
Scanning ...

These messages indicated that a MEIZU MX4 mobile phone was detected. We then checked the Bluetooth services this phone supported with its MAC address presented in front of its device name

sdptool browse 38:BC:1A:B1:7E:DD

Note: you need to use your device's name and its MAC address when you run these commands.

The command listed all the services the phone supported. We needed the "OBEX Object Push" service which is for file transfers.
Service Name: OBEX Object Push
Service RecHandle: 0x1000b
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 25
"OBEX" (0x0008)
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100

From the above messages we could get the channel number 25 for the "OBEX Object Push" service. We input this number to the "ussp-push" by running the following command:

ussp-push 38:BC:1A:B1:7E:DD@25 example.jpg example.jpg

Note: you need to use your device's name, its MAC address and channel number when you run these commands.

Usually after the above commands are run a popup window will show on the phone that communicates with Smart4418 and you can start file transfers.

Common Issues:
1) If Smart4418 cannot find a Bluetooth device you can try this command to restart its Bluetooth:

rfkill unblock 0

2) If any of these commands is not installed you can try this command to install it:

apt-get install bluetooth bluez obexftp openobex-apps python-gobject ussp-push

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:

apt-get update

You can install your preferred packages. For example if you want to install an FTP server you can do this:

apt-get install vsftpd

Note: you can change your download server by editting "/etc/apt/sources.list". You can get a complete server list from [1]. You need to select the one with "armhf".

Make Your Own OS Image

Install Cross Compiler

Download the compiler package:

git clone
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/

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 into 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. After the compiler is installed you can verify it by running the following commands:

arm-linux-gcc -v
Using built-in specs.
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)

Compile U-Boot

Download the U-Boot source code and compile it. Note the github's branch is nanopi2-lollipop-mr1:

git clone
cd uboot_nanopi2
git checkout nanopi2-lollipop-mr1
make s5p4418_nanopi2_config
make CROSS_COMPILE=arm-linux-

After your compilation succeeds a u-boot.bin will be generated. If you want to test it flash it to your installation SD card via fastboot. Here is how you can do it
1) On your host PC run "sudo apt-get install android-tools-fastboot" to install the fastboot utility;
2) Connect your Smart4418 to your host PC via a serial cable (e.g. PSU-ONECOME). Press the enter key within two seconds right after you power on your Smart4418 and you will enter uboot's command line mode;
3) After type in "fastboot" and press "enter" you will enter the fastboot mode;
4) Connect your Smart4418 to this host PC via a microUSB cable and type in the following command to flash the u-boot.bin you generated:

fastboot flash bootloader u-boot.bin

Warning: you cannot update this SD card by commanding "dd". This command which will cause trouble when booting the Smart4418.

Prepare mkimage

You need the mkimage utility to compile a U-Boot source code package. Make sure this utility works well on your host before you start compiling a uImage.
You can install this utility by either commanding "sudo apt-get install u-boot-tools" or following the commands below:

cd uboot_nanopi2
make CROSS_COMPILE=arm-linux- tools
sudo mkdir -p /usr/local/sbin && sudo cp -v tools/mkimage /usr/local/sbin

Compile Linux Kernel

Compile Kernel

  • Download Kernel Source Code
git clone
cd linux-3.4.y
git checkout nanopi2-lollipop-mr1

The Smart4418's kernel source code lies in the "nanopi2-lollipop-mr1" branch.

  • Compile Android Kernel
make nanopi2_android_defconfig
touch .scmversion
make uImage
  • Compile Debian Kernel
make nanopi2_linux_defconfig
touch .scmversion
make uImage

After your compilation succeeds a uImage will be generated in the "arch/arm/boot/uImage" directory. This kernel is for HDMI 720P. You can use it to replace the existing uImage.hdmi.
If you want to generate a kernel for HDMI 1080P you can do it this way

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

After your compilation succeeds a uImage will be generated for HDMI 1080P. 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.
Compile Original Kernel Modules:

cd linux-3.4.y
make CROSS_COMPILE=arm-linux- modules

Here we have two new modules and we can compile them by following the commands below:

cd /opt/FriendlyARM/s5p4418/android

The "/opt/FriendlyARM/s5p4418/android" directory points to the top directory of Android source code. You can get more details by specifying option "-h".
After your compilation succeeds new modules will be generated

Compile Android

  • Install Cross Compiler

Install 64 bit Ubuntu 14.04 on your PC host.

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

For more details refer to

  • Download Source Code(Android 5.1)

You need to use repo to get the Android source code. Refer to

mkdir android && cd android
repo init -u -b nanopi2-lollipop-mr1
repo sync

The "android" directory is the working directory.

If you want to try Android4.4's source code you can run the following commands:

mkdir android && cd android
repo init -u -b nanopi2-kitkat
repo sync

Option "-b" specifies a branch

  • Compile System Package
source build/
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
boot.img boot -
cache.img cache -
userdata.img userdata -
system.img system -
partmap.txt - partition description file
  • Flash Image to eMMC

After compiling Android successfully you can flash it to eMMC with either of the following methods
1) fastboot: right after the Smart4418 is booted from eMMC press any key to enter the uboot commandline mode and type in "fastboot"
Connect your board to a host PC running Ubuntu with a USB cable and run the following commands in the PC's terminal:

cd out/target/product/nanopi2
sudo fastboot flash boot boot.img
sudo fastboot flash cache cache.img
sudo fastboot flash userdata userdata.img
sudo fastboot flash system system.img
sudo fastboot reboot

2) Use an SD Card
Copy these files: boot.img, cache.img, userdata.img, system.img, partmap.txt from the out/target/product/nanopi2 directory to your installation SD card's images/android directory and you can use this SD card to flash Android to eMMC

Connect Smart4418 to External Modules

Connect Smart4418 to 4G Module

  • The Smart4418 can work with some 4G modules under Android 4.4. After you connect a 4G module (e.g. ME909u-521 which supports FDD-LTE) to a Smart4418 power on the board the 4G module will be activated automatically

4G Model

Connect Smart4418 to USB Camera(FA-CAM202)

  • In this use case the Smart4418 runs Debian. If you connect your Smart4418 to our LCD or an HDMI monitor after Debain is fully loaded click on "other"-->"xawtv9" 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

Connect Smart4418 to CMOS 5M-Pixel Camera

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

  • If your Smart4418 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/Ubuntu 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

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

  • Firstly you need to make sure your Smart4418 is connected to the internet. Login to your Smart4418 via a serial terminal or SSH. After login type 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 Smart4418. You can test your camera with Smart4418's camera utility.
3. Check your camera device:

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

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

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

6. Connect Smart4418 to USB Keyboard & Run the Following Command


This is what you expect to observe:

More OS Support

Ubuntu-Core with Qt-Embedded

Ubuntu Core with Qt-Embedded is a light Linux system without X-windows. It uses the Qt-Embedded's GUI and is popular in industrial and enterprise applications.

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

  • it supports our LCDs with both capacitive touch and resistive touch(S700, X710, S70)
  • it supports WiFi
  • it supports Ethernet
  • it supports Bluetooth and has been installed with bluez utilities
  • it supports audio playing

For more details refer to Ubuntu Core with Qt-Embedded.

Flash Ubuntu-Core with Qt-Embedded to eMMC

1. Make an installation SD card with the win32 utility;
2. Insert this SD card to a host PC and copy the UbuntuCore image (in our example it was "ubuntu_core.img") and 2nboot file(in our example it was "2ndboot.bin.emmc") to it;
2nboot can be downloaded from:
3. Run the following commands to flash the image file to your board's eMMC:

dd  if=ubuntu_core.img   of= /dev/mmcblk1

4. Flash the 2nboo file to the eMMC:

dd if=2ndboot.bin.emmc of=/dev/mmcblk1 bs=512 seek=1


Ubuntu-Mate is a Ubuntu variant and its GUI is Mate-desktop. You can log in via SSH when you connect the Smart4418 to an LCD or HDMI
FriendlyARM doesn't provide technical support for it

  • Go to this link download link to download the image files
  • Uncompress it and flash the image file to a TF card with win32diskimager under Windows
  • After it is done you can boot your Smart4418 with this card
  • Login name: "root" or "fa", Password: fa


  • Go to this link [3] to download the image files;
  • 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*".
  • Copy the image files to the card by running the following commands as root:
xzcat kali-2.0-nanopi2.img.xz | dd of=<YOURDEVICE> bs=1m
  • After it is done you can boot your Smart4418 with this card.

Note: this is offered by Kali and FriendlyARM doesn't provide technical support for it.

Deepin15 ARM

  • Go to this link [4] to download the image files
  • Uncompress the file and you will get a 16g.img file which is the image file for MicroSD card.
tar -xf deepin15_nanopi2_armhf_16g.tar.gz
  • Prepare an 16G High Speed SD card, insert it into a Linux host and do "sudo fdisk -l" to check its device name, i.e. "/dev/sd*"
  • Flash the image files to the card by running the following command as root(in our case our card was recognized as "/dev/sdc"):
sudo dd if=16g.img of=/dev/sdc

This process takes a while which can be up to one hour

  • After it is done you can boot your Smart4418 with this card

1. The password for login name "deepin" is "deepin". The password for login name "root" is "admin".
2. The initial booting of Deepin15 takes a relative long time for it generates some configuration files.
3. If WiFi is activated in your system booting might take longer. In this case wait for the sound and wifi icons on the right bottom of the GUI to appear before you start any action.

    ARM code:
    NanoPC-T2 Image:
    NanoPC-T2 Image Installation Instruction;
    Forum for Migrating Deepin15 to ARM:

Note: this is offered by the Deepin15 team and FriendlyARM doesn't provide technical support for it.


Go to this link [5] to download the image files;

  • Untar the image ball:
tar -xf nanopi2-android-remixos-sd4g.tar
  • Use the win32diskimager utility to flash the image to an SD card.

It supports HDMI and LCD output and works with all existing FriendlyARM 4418 boards.
Note: this is offered by Remix team and FriendlyARM doesn't provide technical support for it.


Smart4418 1512 Schematic in PDF
Smart4418 1608 Schematic in PDF
dimension (Smart4418-1512-Dimension(dxf).zip)
dimension (Smart4418-1608-Dimension(dxf).zip)

Update Log


  • Released English version
  • Updated features and bug fixes:

1) Released Android 5.1.1_r6
2) Updated code branch to nanopi2-lollipop-mr1
3) Updated kernel module compilation by adding LCD support in Debian's uImage
4) kernel: developed a function to generate a MAC address based on CPU ECID;
5) kernel: fixed a refresh issue in framebuffer console
6) kernel: fixed a bug in PWM LED;
7) Debian: fixed a bug in hostname;
8) Debian: started framebuffer console by default and system boot information can be displayed on LCD/HDMI;
9) Debian: integrated fw_printenv;
10) Android: started ffmpeg by default more video formats get supported


  • Updated features and bug fixes:

1) Debian: added support for external USB Wi-Fi modules and USB to serial;
2) Debian: fixed a bug in audio output;
3) Debian: added support for LVDS. But by default LVDS is not enabled;
4) UbuntuCore with Qt-Embedded: added support for FriendlyElec's LCDs with resistive touch and capacitive touch(model: S700, X710, S70)
5) UbuntuCore with Qt-Embedded: added WiFi
6) UbuntuCore with Qt-Embedded: added Ethernet
7) UbuntuCore with Qt-Embedded: added Bluetooth, integrated bluez utility
8) UbuntuCore with Qt-Embedded: added support for audio


  • Updated sections 7.2.2 and 10.3
  • Updated features and bug fixes

1) SD card's section will be automatically extended on fist system boot.
2) Integrated NxPlayerConsole in Debian/Ubuntu Core. To run it an LCD must be connected to board.(Note: no source code is provided for the library by vendor)
3) Integrated open source gltest1 utility for OpenGL under Ubuntu Core
4) Added support for USB Wi-Fi - rtl8187 under Debian/Ubuntu Core;
5) Reset USB device to /dev/video0 under Debian/Ubuntu Core, it is easy for access with opencv
6) Set wifi management utility to wpa_supplicant instead of wicd
7) Android: added support for Ethernet setting(static IP and DHCP);
8) Android: added for serial port access;
Here are the serial ports' device names under NanoPi2/NanoPi M2/NanoPi2 Fire/NanoPC-T2:
UART2 -> N/A
UART3 -> /dev/ttyAMA2
UART4 -> /dev/ttyAMA3
9) Android: integrated iTest utility which has a serial port test utility;
10) Ubuntucore with Qt-Embedded: replaced the startup GUI: Qt Demo with a FriendlyElec developed open source Qt GUI (source code under /opt) which shows system information and status;
11) Ubuntucore with Qt-Embedded: Fixed a bug in loading firmware for USB WiFi;
12) Updated Bootloader by adding support for dd to write RAW image to eMMC;
13) Released Android4.4 ( and its source code;
14) Released ROM s5p4418-eflasher-sd8g-xxx-full.img;
15) Integrated a demo utility for CAM500A(OV5640) for Debian and Ubuntu Core;


  • Updated sections 7.1, 7.2, 7.4, 8.4, 9.5 and 10.1
  • add Smart4418 1608 Schematic in PDF
  • Added features and bug fixes:

1) Added support for H43 LCD for s5p4418 and s5p6818 boards under ONLY Debian and UbuntuCore


  • Updated features and bug fixes:

1) Added support for S70B under UbuntuCore and Debian
2) Reset eFlasher Rom's root section to 1GB


  • Updated features and bug fixes:

1) Added support for UART2
2) Added support for HD101B
3) Added library for hardware access in Android4.4 and Android5:[7]
4) Fixed a bug in S430 LCD's abnormal shutdown under Android4.4