NanoPi M1

From FriendlyARM WiKi
Jump to: navigation, search

查看中文

Contents

Introduction

Overview
Front
Back
frameless
  • The NanoPi M1 is an Allwinner H3 based ARM board designed and released by FriendlyARM for hobbyists, makers and electronic fans. It is only two thirds the size of the Raspberry Pi. It is open source. It works with Ubuntu MATE, Debian and etc.
  • The NanoPi M1 uses the Allwinner H3 Soc. It integrates Ethernet, IR receiver, video/audio output and supports HDMI and AVOUT. It can be powered via the MicroUSB port
  • In such a small board it still integrates rich interfaces and ports. Besides the popular HDMI, Ethernet, USB-Host, USB-OTG, DVP camera interface and AVOUT (audio and video) it has an onboard Microphone, IR receiver, a serial debug port and a Raspberry Pi compatible 40 pin GPIO pin header.

Hardware Spec

  • CPU: Allwinner H3, Quad-core Cortex-A7@1.2GHz
  • GPU: Mali400MP2@600MHz,Supports OpenGL ES2.0
  • DDR3 RAM: 512MB/1GB
  • Connectivity: 10/100M Ethernet
  • Audio: 3.5mm audio jack/Via HDMI
  • Microphone: Onboard microphone
  • IR Receiver: Onboard IR receiver
  • USB Host:Type A, USB 2.0 x 3
  • MicroSD Slot x 1
  • MicroUSB: for data transmission and power input, OTG
  • Video Output: HDMI 1.4 1080P, CVBS
  • DVP Camera Interface: 24pin, 0.5mm pitch FPC seat
  • Debug Serial Port: 4Pin, 2.54mm pitch pin header
  • GPIO: 2.54mm spacing 40pin, compatible with Raspberry Pi's GPIO. It includes UART, SPI, I2C, IO etc
  • User Key: Power LED x 1, Reset x 1
  • PC Size: 64 x 56mm
  • Power Supply: DC 5V/2A
  • Working Temperature: -30℃ to 70℃
  • OS/Software: u-boot,Ubuntu MATE,Debian

compact01

Software Features

uboot

  • mainline uboot released on May 2017
  • supports fastboot to update uboot

UbuntuCore 16.04

  • mainline kernel: Linux-4.11.2
  • rpi-monitor: check system status and information
  • npi-config: system configuration utility for setting passwords, language, timezone, hostname, SSH and auto-login,and enabling/disabling i2c, spi, serial and PWM
  • networkmanager: manage network
  • system log output from serial port
  • auto-login with user account "pi" with access to npi-config

Debian Jessie

  • welcome window with basic system information and status
  • npi-config: system configuration utility for setting passwords, language, timezone, hostname,

Android

  • supports USB WiFi

Diagram, Layout and Dimension

Layout

NanoPi M1 Layout
  • GPIO Pin Spec
Pin# Name Linux gpio Pin# Name Linux gpio
1 SYS_3.3V 2 VDD_5V
3 I2C0_SDA/GPIOA12 4 VDD_5V
5 I2C0_SCL/GPIOA11 6 GND
7 GPIOG11 203 8 UART1_TX/GPIOG6 198
9 GND 10 UART1_RX/GPIOG7 199
11 UART2_TX/GPIOA0 0 12 GPIOA6 6
13 UART2_RTS/GPIOA2 2 14 GND
15 UART2_CTS/GPIOA3 3 16 UART1_RTS/GPIOG8 200
17 SYS_3.3V 18 UART1_CTS/GPIOG9 201
19 SPI0_MOSI/GPIOC0 64 20 GND
21 SPI0_MISO/GPIOC1 65 22 UART2_RX/GPIOA1 1
23 SPI0_CLK/GPIOC2 66 24 SPI0_CS/GPIOC3 67
25 GND 26 SPDIF-OUT/GPIOA17 17
27 I2C1_SDA/GPIOA19/PCM0_CLK/I2S0_BCK 19 28 I2C1_SCL/GPIOA18/PCM0_SYNC/I2S0_LRCK 18
29 GPIOA20/PCM0_DOUT/I2S0_SDOUT 20 30 GND
31 GPIOA21/PCM0_DIN/I2S0_SDIN 21 32 GPIOA7 7
33 GPIOA8 8 34 GND
35 UART3_CTS/SPI1_MISO/GPIOA16 16 36 UART3_TX/SPI1_CS/GPIOA13 13
37 GPIOA9 9 38 UART3_RTS/SPI1_MOSI/GPIOA15 15
39 GND 40 UART3_RX/SPI1_CLK/GPIOA14 14
  • Debug Port(UART0)
Pin# Name
1 GND
2 VDD_5V
3 UART_TXD0/GPIOA4
4 UART_RXD0/GPIOA5/PWM0
  • DVP Camera IF Pin Spec
Pin# Name Description
1, 2 SYS_3.3V 3.3V power output, to camera modules
7,9,13,15,24 GND Gound, 0V
3 I2C2_SCL I2C Clock Signal
4 I2C2_SDA I2C Data Signal
5 GPIOE15 Regular GPIO, control signals output to camera modules
6 GPIOE14 Regular GPIO, control signals output to camera modules
8 MCLK Clock signals output to camera modules
10 NC Not Connected
11 VSYNC vertical synchronization to CPU from camera modules
12 HREF/HSYNC HREF/HSYNC signal to CPU from camera modules
14 PCLK PCLK signal to CPU from camera modules
16-23 Data bit7-0 data signals
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. All pins are 3.3V and output current is 5mA. It can drive small loads. No IO pins can drive a load.
  4. For more details refer to the document: NanoPi-M1-1603B-Schematic.pdf

Board Dimension

NanoPi-M1-1603B-dimensions.png

For more details please refer to: pcb file in dxf

Get Started

Essentials You Need

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

  • NanoPi M1
  • microSD Card/TFCard: Class 10 or Above, minimum 8GB SDHC
  • microUSB power. A 5V/2A power is a must
  • HDMI monitor
  • USB keyboard and mouse
  • A host computer running Ubuntu 14.04 64 bit system

TF Cards We Tested

To make your NanoPi M1 boot and run fast we highly recommend you use a Class10 8GB SDHC TF card or a better one. The following cards are what we used in all our test cases presented here:

  • SanDisk TF 8G Class10 Micro/SD TF card:

SanDisk MicroSD 8G

  • SanDisk TF128G MicroSDXC TF 128G Class10 48MB/S:

SanDisk MicroSD 128G

  • 川宇 8G C10 High Speed class10 micro SD card:

chuanyu MicroSD 8G

Make an Installation TF Card

Get Image Files

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

Image Files:
nanopi-m1_ubuntu-core-xenial_3.4.y_YYYYMMDD.img.zip Ubuntu-Core with Qt-Embedded Image File, kernel:Linux-3.4.y
nanopi-m1_ubuntu-core-xenial_4.x.y_YYYYMMDD.img.zip Ubuntu-Core with Qt-Embedded Image File, kernel:Linux-4.x.y
nanopi-m1_debian-jessie_3.4.y_YYYYMMDD.img.zip Debian-Desktop Image File, kernel:Linux-3.4.y
nanopi-m1_debian-jessie_4.x.y_YYYYMMDD.img.zip Debian-Desktop Image File, kernel:Linux-4.x.y
nanopi-m1_android_YYYYMMDD.img.zip Android Image File, kernel:Linux-3.4
Flash Utility:
win32diskimager.rar Windows utility for flashing Debian image. Under Linux users can use "dd"
PhoenixCard_V310.rar Windows utility for flashing Android image. Attention: the "dd" command under Linux doesn't work for flashing Android image
HDDLLF.4.40.exe Windows utility for formatting a TF card

Comparison of Linux-3.4.y and Linux-4.x.y

  • Our Linux-3.4.y is provided by Allwinner. Allwinner has done a lot of customization work which on one hand contains many features and functions but on the other hand incurs overheat issues;
  • Our Linux-4.x.y is updated very often. We will keep this kernel with the latest one released by Linus Torvalds. This kernel doesn't generate heat that much and if you don't need to use VPU or GPU you can try this kernel;

Here is a comparison table:
M1-plus-3x-4x.png

Make Debian/Ubuntu Image Card

  • Extract an image file and win32diskimager.rar. Insert a TF card(at least 4G) into a Windows PC and run the win32diskimager utility as administrator. On the utility's main window select your TF card's drive, the wanted image file and click on "write" to start flashing the TF card.
  • Insert this card into your NanoPi M1's BOOT slot and power on (with a 5V/2A power source). If the green LED is on and the blue LED is blinking this indicates your NanoPi M1 has successfully booted.

Make Android Image Card

Note:before make a MicroSD card to an Android image card you need to format this card.

  • On a Windows PC run the HDDLLF.4.40 utility as administrator. Insert a TF card(at least 4G) into this PC and format it. After formatting is done take out the TF card, insert it into the PC again and format it with Windows internal format utility to format it to FAT32. After this formatting is done take out the card.
  • Extract an Android image file and PhoenixCard_V310.rar. Insert the TF card you made in the previous step into a Windows PC and run the PhoenixCard_V310 utility as administrator. On the utility's main window select your TF card's drive, the wanted image file and click on "write" to start flashing the TF card.
  • Insert this card into your NanoPi M1's BOOT slot and power on (with a 5V/2A power source). If the green LED is on and the blue LED is blinking this indicates your NanoPi M1 has successfully booted.

Working with Debian

Run Debian

  • Insert a TF card with Debian image files into your NanoPi M1, connect the NanoPi M1 to an HDMI monitor and a 5V/2A power source the NanoPi M1 will be automatically powered on. If you can see the blue LED flashing it means your board is working and you will see Debain being loaded on the HDMI monitor.

1)If you connect the NanoPi M1 to an HDMI monitor you need to use a USB mouse and a USB keyboard to operate.
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 where we connect a NanoPi M1 to a PC via the PSU-ONECOM and you can power on your M1 from either the PSU-ONECOM or M1's MicroUSB:

PSU-ONECOM-M1

  • The password for both "root" and "fa" is "fa". All the commands we tested in this section were executed under "root"
  • Update packages
$ apt-get update

Extend TF Card's rootfs Section

When you boot OS for the first time with your image card your OS will automatically resize the file system and this process takes a relatively long time.After your OS is fully loaded you can check the file system's size by using the following command:

$ df -h

Ethernet Connection

If the NanoPi M1 is connected to a network via Ethernet before it is powered on it will automatically obtain an IP after it is powered up. 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. Run the following command to check its MAC address:

$ dhclient eth0

Login via VNC and SSH

If your NanoPi M1 is not connected to a display device you can login to your NanoPi M1 from a mobile phone. You need to download and install a "VNC Viewer" from here on a mobile phone and login to the NanoPi M1 via VNC at port 1. Its default password is "fa123456".
Here is a screenshot which shows how it looks like when users login to the NanoPi M1 from an iPhone via VNC:
VNC to NanoPi2
In our case our M1's IP address is 192.168.1.230. You can login via SSH by running the following commands:

$ ssh root@192.168.1.230

The password is fa.

HDMI Audio Output

Note: this function is only supported in Linux-3.4.y.
Our system's default audio output is the 3.5mm audio jack. You can turn on the HDMI audio by editing the /etc/asound.conf file:

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

card 0 points to the 3.5mm audio jack and card 1 points to the HDMI audio. You need to save your changes and reboot your system to make your changes take effect.

Test GPU

Note: this function is only supported in Linux-3.4.y.
After OS loads please login from a terminal and run the following command:

glmark2-es2

m1-gpu-glmark2

Test VPU

Note: this function is only supported in Linux-3.4.y
Visit this link download link to download files
After OS is loaded login from a terminal and run the following commands:

$ sudo apt-get install mpv
$ video_play mpv ./big_buck_bunny_1080p_H264_AAC_25fps_7200K.MP4

In our test it could do hard coding and play 1080P video fluently.

Test USB WiFi

Our OS system has support for popular USB WiFi drivers. Many USB WiFi modules are plug and play with our system. Here is a list of models we tested;

Number Model
1 RTL8188CUS 802.11n WLAN Adapter
2 RT2070 Wireless Adapter
3 RT2870/RT3070 Wireless Adapter
4 RTL8192CU Wireless Adapter
5 mi WiFi mt7601
  • Check device list
$ nmcli dev
DEVICE  TYPE      STATE         CONNECTION         
eth0    ethernet  connected     Wired connection 1 
wlan0   wifi      disconnected  --                                  
lo      loopback  unmanaged     --

Note: if the status of a device is "unmanaged" it means that device cannot be accessed by NetworkManager. To make is 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"

The "SSID" and "PASSWORD" need to be replaced with your actual SSID and password.
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

Connect NanoPi M1 to DVP Camera CAM500B

Note: this function is only supported in Linux-3.4.y
The CAM500B camera module is a 5M-pixel camera with DVP interface. For more tech details about it you can refer to Matrix - CAM500B.
NanoPi-M1-cam500a
Follow the hardware setup presented in the above picture to connect your NanoPi M1 to a CAM500B. Then boot OS, connect your M1 to a network, log into the board as root and run "mjpg-streamer":

$ cd /root/mjpg-streamer
$ make
$ ./start.sh

The mjpg-streamer application is an open source video steam server. After it is successfully started the following messages will be popped up:

 
 i: Using V4L2 device.: /dev/video0
 i: Desired Resolution: 1280 x 720
 i: Frames Per Second.: 30
 i: Format............: YUV
 i: JPEG Quality......: 90
 o: www-folder-path...: ./www/
 o: HTTP TCP port.....: 8080
 o: username:password.: disabled
 o: commands..........: enabled

In our case the M1's IP address was 192.168.1.230. We typed 192.168.1.230:8080 in a browser and were able to view the images taken from the camera's. Here is what you would expect to observe:
mjpg-streamer-cam500a
The mjpg-streamer soft-encodes data with libjpeg and you can hard-encode its data with ffmpeg which will greatly increase CPU's efficiency and speed up data encoding:

$ ffmpeg -t 30 -f v4l2 -channel 0 -video_size 1280x720 -i /dev/video0 -pix_fmt nv12 -r 30 \
        -b:v 64k -c:v cedrus264 test.mp4

By default it records a 30-second video. Typing "q" stops video recording. After recording is stopped a test.mp4 file will be generated.

Connect NanoPi M1 to USB Camera(FA-CAM202)

The FA-CAM202 is a 200M USB camera.
Refer to this link for more details on how to connect a M1 to a FA-CAM202. The hardware setup is the same as connecting a M1 to a CAM500B: Connect NanoPi M1 to DVP Camera CAM500B

Use OpenCV to Access Camera

  • The full name of "OpenCV" is Open Source Computer Vision Library and it is a cross platform vision library.
  • Make sure your NanoPi M1 is connected to the internet and an HDMI monitor. Boot Debian on the NanoPi M1 and login
  • Install OpenCV libraries:
$ apt-get update
$ apt-get install libcv-dev libopencv-dev
  • Refer to the instructions in the previous sections to make sure the camera works
  • Compile and run a code sample(Official Code Sample in C++ provided by the OpenCV organization):
$ cd /home/fa/Documents/opencv-demo
$ make
$ ./demo

Here is what you expect to observe:
OpenCV-M1

Check CPU's Working Temperature

You can use the following command to read H3's temperature and frequency

cpu_freq

Check System Information with Rpi-Monitor

Our OS contains the Rpi-Monitor utility with which users can check system information and status.
In our case our NanoPi M1's IP was 192.168.1.230 and we typed the following IP in a browser:

192.168.1.230:8888

We were directed to the following page:
rpi-monitor
Users can easily check these system information and status.

Work with Ubuntu-Core with Qt-Embedded

Run Ubuntu-Core with Qt-Embedded

  • Insert a MicroSD card with Ubuntu-Core image into your M1, connect the NanoPi M1 to an HDMI monitor and to a 5V/2A power source the NanoPi M1 will be automatically powered on. If you can see the blue LED flashing it means your board is working.

m1-login
1)If your board outputs to an HDMI monitor you can connect a USB mouse and keyboard to your board to operate it.
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 where we connect a NanoPi M1 to a PC via the PSU-ONECOM and you can power on your board from either the PSU-ONECOM or its MicroUSB:

PSU-ONECOM-M1

  • The password for "root" is "fa". All the commands were executed under "root" in this section.
  • Update packages:
$ apt-get update

Extend TF Card's rootfs Section

When you boot OS for the first time with your image card your OS will automatically resize the file system and this process takes a relatively long time.After your OS is fully loaded you can check the file system's size by using the following command:

$ df -h

Ethernet Connection

If the NanoPi M1 is connected to a network via Ethernet before it is powered on it will automatically obtain an IP after it is powered up. 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. You can get its IP address by running the following command:

$ dhclient eth0

Login via SSH

You can log into the board via SSH. In our test the IP address detected by our router was 192.168.1.230 and we ran the following command to log into the NanoPi M1:

$ ssh root@192.168.1.230

The password is fa

HDMI Audio Output

Note:this function is only supported in Linux-3.4.y
Our system's default audio output is the 3.5mm audio jack. You can turn on the HDMI audio by editing the /etc/asound.conf file:

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

card 0 points to the 3.5mm audio jack and card 1 points to the HDMI audio. You need to save your changes and reboot your system to make your changes take effect.

Test USB WiFi

Our system has support for popular USB WiFi drivers. Many USB WiFi modules are plug and play with our system. Here is a list of models we tested;

Number Model
1 RTL8188CUS 802.11n WLAN Adapter
2 RT2070 Wireless Adapter
3 RT2870/RT3070 Wireless Adapter
4 RTL8192CU Wireless Adapter
5 mi WiFi mt7601

If your NanoPi M1 is connected to a USB WiFi and is powered up you can log into M1 and run the following command to check if the USB WiFi is recognized. If "wlan" is listed it indicates your USB WiFi has been recognized:

$ nmcli dev
DEVICE  TYPE      STATE         CONNECTION         
eth0    ethernet  connected     Wired connection 1 
wlan0   wifi      disconnected  --                 
wlan1   wifi      disconnected  --                 
lo      loopback  unmanaged     --

Note: if a device's state is unmanaged it means it is not accessed by the NetworkManager utility and you need to clear the settings in "/etc/network/interfaces" and reboot.

  • Start WiFi
$ nmcli r wifi on
  • Scan Surrounding WiFi Hotspots
$ nmcli dev wifi
  • Connect to a WiFi
$ nmcli dev wifi connect "SSID" password "PASSWORD"

Replace SSID and PASSWORD with your real ones.
If a connection is established successfully your board will be automatically connected to this WiFi on system reboot.

For more details on how to use the NetworkManager utility refer to :[1]

Connect NanoPi M1 to DVP Camera(CAM500B)

Note:this function is only supported in Linux-3.4.y.
The CAM500B camera module is a 5M-pixel camera with DVP interface. For more tech details about it you can refer to Matrix - CAM500B.
NanoPi-M1-cam500a
Boot your NanoPi M1, connect it to a network, log into the board as root and run "mjpg-streamer":

$ cd /root/mjpg-streamer
$ make
$ ./start.sh

The mjpg-streamer application is an open source video steam server. After it is successfully started the following messages will be popped up:

 
 i: Using V4L2 device.: /dev/video0
 i: Desired Resolution: 1280 x 720
 i: Frames Per Second.: 30
 i: Format............: YUV
 i: JPEG Quality......: 90
 o: www-folder-path...: ./www/
 o: HTTP TCP port.....: 8080
 o: username:password.: disabled
 o: commands..........: enabled

In our case the M1's IP address was 192.168.1.230. We typed 192.168.1.230:8080 in a browser and were able to view the images taken from the camera's. Here is what you would expect to observe:
mjpg-streamer-cam500a
The mjpg-streamer soft-encodes data with libjpeg and you can hard-encode(note:this function is supported only in Linux-3.4.y) its data with ffmpeg which will greatly increase CPU's efficiency and speed up data encoding:

$ ffmpeg -t 30 -f v4l2 -channel 0 -video_size 1280x720 -i /dev/video0 -pix_fmt nv12 -r 30 -b:v 64k -c:v cedrus264 test.mp4

By default it records a 30-second video. Typing "q" stops video recording. After recording is stopped a test.mp4 file will be generated.

Connect NanoPi M1 to USB Camera(FA-CAM202)

The FA-CAM202 is a 200M USB camera.
Refer to this link for more details on how to connect a M1 to a FA-CAM202. The hardware setup is the same as connecting a M1 to a CAM500B: Connect NanoPi M1 to DVP Camera(CAM500B)

Check CPU's Working Temperature

You can use the following command to read H3's temperature and frequency

$ cpu_freq

Check System Information with Rpi-Monitor

Our OS contains the Rpi-Monitor utility with which users can check system information and status.
In our case our NanoPi M1's IP was 192.168.1.230 and we typed the following IP in a browser:

192.168.1.230:8888

We were directed to the following page:
rpi-monitor
Users can easily check these system information and status.

Work with npi-config Utility

The npi-config is a system configuration utility for setting passwords, language, timezone, hostname, SSH and auto-login,and enabling/disabling i2c, spi, serial and PWM. You can start this utillity by running the following command:

$ npi-config

Here is the npi-config's main window:
npi-config
For more details refer to:npi-config

Make Your Own Debian

Use Mainline BSP

The NanoPi M1 has gotten support for kernel Linux-4.x.y. For more details about how to use mainline u-boot and Linux-4.x.y refer to :Mainline U-boot & Linux

Use Allwinner's BSP

Preparations

Visit this link [2] and enter the "sources/nanopi-H3-bsp" directory and download all the source code.Use the 7-zip utility to uncompress it and a lichee directory and an Android directory will be generated.You can check that by running the following command:

$ ls ./
android lichee

Or you can get it from our github:

$ git clone https://github.com/friendlyarm/h3_lichee.git lichee

Note: "lichee" is the project name named by Allwinner for its CPU's source code which contains the source code of U-boot, Linux kernel and various scripts.

Install Cross Compiler

Visit this site download link, enter the "toolchain" directory, download the cross compiler "gcc-linaro-arm.tar.xz" and copy it to the "lichee/brandy/toochain/" directory.

Compile lichee Source Code

Compilation of the H3's BSP source code must be done under a PC running a 64-bit Linux.The following cases were tested on Ubuntu-14.04 LTS-64bit:

$ sudo apt-get install gawk git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386

Enter the lichee directory and run the following command to compile the whole package:

$ cd lichee
$ ./build.sh -p sun8iw7p1 -b nanopi-h3

After this compilation succeeds a u-boot, Linux kernel and kernel modules will be generated
Note: the lichee directory contains a cross-compiler we have setup. When you compile the source code it will automatically call this cross-compiler.


Compile U-boot

Note:you need to compile the whole lichee directory before you can compile U-boot individually.
You can run the following commands to compile U-boot:

$ cd lichee/fa_tools/
$ ./build.sh -b nanopi-m1-plus -p linux -t u-boot

The gen_script.sh script patches the U-boot with Allwinner features. A U-boot without these features cannot work.
Type the following command to update the U-boot on the MicroSD card:

$ cd lichee/fa_tools/
$ ./fuse.sh -d /dev/sdX -p linux -t u-boot

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

Compile Linux Kernel

Note:you need to compile the whole lichee directory before you can compile Linux kernel individually.
If you want to compile the Linux kernel run the following command:

$ cd lichee/fa_tools/
$ ./build.sh -b nanopi-m1 -p linux -t kernel

After the compilation is done a boot.img and its kernel modules will be generated under "linux-3.4/output".

Clean Source Code

$ cd lichee/fa_tools/
$ ./build.sh -b nanopi-m1 -p linux -t clean

Applications under Android

USB WiFi

The rtl8188etv/rtl8188eu USB WiFi modules are supported in Android.

IR Controller(RC-100)

You can use FriendlyARM's IR controller(RC-100) to navigate the Android system.
Here is a list of the function keys on the RC-100 IR controller

Key Function
POWER On/Off
F1 Search
F2 Open Browser
F3 Enable/Disable Mouse
UP Move Up
DOWN Move Down
LEFT Move Left
RIGHT Move Right
OK OK
Volume- Turn Down Volume
Mute Mute
Volume+ Turn Up Volume
SETTING Go to Setting Window
HOME Go to Home Window
BACK Go Back to the Previous Window

After Android is loaded for the first time you need to follow the prompts on Android's GUI to enter the main window and then press F3 to enable mouse and complete the setup process by navigating "up", "down", "left", "right" and "OK".

Play 4K Video

Visit this the test-video directory of this link download link and download the 4K video file: 4K-Chimei-inn-60mbps.mp4 and copy it to an SD card or USB drive.
Boot Android on your M1(512M RAM) and insert this SD card or USB drive to your M1. After locate the 4K video file with ESFileExplorer click on and play it with Android's Gallery player.
In our test playing this 4K video file from a USB drive worked better.

Make Your Own Android

Preparations

Visit this link [3] and enter the "sources/nanopi-H3-bsp" directory and download all the source code.Use the 7-zip utility to uncompress it and a lichee directory and an Android directory will be generated.You can check that by running the following command:

$ ls ./
android lichee

Or you can get it from our github:

$ git clone https://github.com/friendlyarm/h3_lichee.git lichee

Note: "lichee" is the project name named by Allwinner for its CPU's source code which contains the source code of U-boot, Linux kernel and various scripts.

Install Cross Compiler

Visit this site download link, enter the "toolchain" directory, download the cross compiler "gcc-linaro-arm.tar.xz" and copy it to the "lichee/brandy/toochain/" directory.

Compile lichee Source Code

Compilation of the H3's BSP source code must be done under a PC running a 64-bit Linux.The following cases were tested on Ubuntu-14.04 LTS-64bit:

$ sudo apt-get install gawk git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386

Compile Android

  • Setup Environment

A 64-bit Ubuntu-14.04 LTS-64bit is needed. Run the following command.

$ sudo apt-get install bison g++-multilib git gperf libxml2-utils make python-networkx zip flex libncurses5-dev zlib1g-dev gawk minicom

For more details refer to:android_initializing

  • Install JDK

We used the JDK1.6.0_45. You can get it from Oracle: Oracle JDK . In our test we installed it in the /usr/lib/jvm/ directory.

  • Compile System
$ cd lichee/fa_tools/
$ ./build.sh -b nanopi-m1 -p android -t all
$ cd ../../android
$ export PATH=/usr/lib/jvm/jdk1.6.0_45/bin:$PATH
$ ./build.sh -b nanopi-m1

After the above commands are finished an Android image "sun8iw7p1_android_nanopi-m1_uart0.img" will be generated under the "lichee/tools/pack/" directory.

Clean Source Code

$ cd lichee/fa_tools/
$ ./build.sh -b nanopi-m1 -p android -t clean

More OS Support

Ubuntu-MATE

Ubuntu-Mate is a Ubuntu variant and its GUI is Mate-desktop. You can login via SSH when you connect a NanoPi M1 to an HDMI monitor
FriendlyARM doesn't provide technical support for it

  • Go to this link download link to download the image file nanopi-m1-ubuntu-mate-sd4g.img.zip
  • Uncompress it and flash the image file to a TF card with win32diskimager under Windows
  • After it is done you can boot your NanoPi M1 with this card
  • Login name: "root" or "fa", Password: fa

MATE-desktop

DietPi_NanoPiNEO-armv7-(Jessie)

DietPi is an extremely lightweight Debian Jessie OS. Its image file starts at 400MB and nearly 3x lighter than 'Raspbian Lite'.It is pre-installed with DietPi-RAMLog. These features enable users to get the best performance of a device.
The following steps are for reference only. FriendlyElec doesn't provide technical support for them.
Installation guide:

  • Download the image file "DietPi_NanoPiNEO-armv7-(Jessie)" from DietPi_NanoPiNEO-armv7-(Jessie)
  • Extract the package and use the win32diskimager to write it to a MicroSD card under Windows.
  • Insert this MicroSD card to your NanoPi M1 and power up.

Username:root , Password: dietpi

Debian8(Jacer)

Debian8(Jacer) is a Debian 8 variant developed by a developer "Jacer". It uses Debian 8's desktop and has good support for the Chinese language. Users need to run this OS with an HDMI monitor and can login to the system via SSH.
FriendlyARM doesn't provide technical support for it.

  • Please visit here :download link to download its image file Debian8(unofficial-Jacer).rar.
  • Uncompress it and flash the image file to a TF card with win32diskimager under Windows.
  • After it is done you can boot your NanoPi M1 with this card
  • Login name: "fa", Password: fa

Note: When the NanoPi M1 is connected to an HDMI monitor and runs Debian8(Jacer) we don't suggest login to the system as root. If you do that the HDMI monitor will show black instead of a Debian8 GUI;
Debian8(Jacer) is integrated with GPU drivers, H264 and H265 hard decoding code. It defaults to the HDMI 720P configuration. If you want to modify its resolution to 1080P you can set the "HDMI MODE =" setting in the script.fex (under the "/boot" section) to the 1080P definition and use the corresponding script.bin file. For more details refer to the h3disp.sh file;
Debian8(Jacer) supports these WiFi card models: 8192cu, 8188cus, 8188eu, rt3070.
Debian8(Jacer)has the following support too:

  • 1.Mali400 GPU driver
  • 2.mpv hard decoding H264, H265
  • 3.Chromium and flash
  • 4.Netease's feeluown
  • 5.Games such as Chess and Minesweeper
  • 6.retroarch game simulator
  • 7.Virtual memory
  • 8.Dynamic frequency scaling
  • 9.aria2 download utility
  • 10.samba
  • 11.WiFi cards: 8192cu/8188cus/8188eu/rt3070/rt2800/rt5370
  • 12.GIMP utility
  • 13.SSH
  • 14.xrdp and vnc
  • 15.HTML5 media player
  • 16.goldendict
  • 17.audacious music player
  • 18.pulseaudio volume control utility
  • 19.USB bluetooth

Debian-Jacer-desktop

Android(Jacer)

Android(Jacer) is an Android4.4.2 variant developed by a developer "Jacer". It uses Android's desktop. Users need to run this OS with an HDMI monitor and can login to the system via SSH.
FriendlyARM doesn't provide technical support for it.

  • Download image files and utilities

1. Please visit here :download link to download its image file Android(Beelink_X2_v205k4_for_NanoPiM1).
2. Download Windows utility (HDDLLF.4.40)download link for formatting a TF card.
3. Download Windows utility (PhoenixCard)download link for flashing Android image files.

  • Make Android TF Card

1. On a Windows PC run the HDDLLF.4.40 utility as administrator. Insert a TF card(at least 4G) into this PC and format it. After formatting is done take out the TF card;
2. Insert it into the PC again and format it with Windows internal format utility to format it to FAT32. After this formatting is done take out the card;
3. Insert the TF card you made in the previous step into a Windows PC and run the PhoenixCard_V310 utility as administrator. On the utility's main window select your TF card's drive, the wanted image file and click on "write" to start flashing the TF card.
Note: none of the above steps should be missed otherwise the TF card you made may not work.

  • Boot Android

1. Insert an installation TF card into an M1, power on the board and you will be able to work with it
Android(Jacer) supports these WiFi cards: rtl8188etv, rt8188eus and rt8189.
Android(Jacer) has the following features:

  • 1. the menu bar can be set hidden; a power button can be added; dynamic frequency scaling is enabled
  • 2. GAAPS
  • 3. it supports rtl8188etv/eus 8189 WiFi cards and CSR bluetooth
  • 4. relative low working voltage and low working temperature

For details about its full features try it by yourself:)
Android-Jacer-desktop

Armbian

For image download links and instructions visit Armbian's page for the NanoPi M1:armbian-m1
Armbian provides a server and a desktop versions. Here is how the desktop GUI looks like:
Armbian-desktop

OpenWRT

OpenWRT was migrated to the M1 by one hobbyist "Tom".
FriendlyARM doesn't provide technical support for it.

  • Visit download link to download openwrt-sunxi-NanoPi_M1-sdcard-vfat-ext4.img(unofficail-ROMs directory).
  • Uncompress the file and you will get openwrt-sunxi-NanoPi_M1-sdcard-vfat-ext4.img.
  • Insert a microSD to a host PC running Ubuntu and check the SD card's device name by using the following command
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 is recognized as "/dev/sdc". Or you can check that by commanding "cat /proc/partitions"

  • Go to the directory where openwrt-sunxi-NanoPi_M1-sdcard-vfat-ext4.img is located and run the following command to flash the image to your MicroSD card:
dd if=openwrt-sunxi-NanoPi_M1-sdcard-vfat-ext4.img  of=/dev/sdx

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

  • After it is done insert the card to your board and power on. Here is what you expect to observe.

OpenWRT

Download Link to Image Files

  • Image files: [4]

3D Housing Printing Files

  • NanoPi M1 3D housing printing files:[5]

3D打印M1

Matrix Compact Kit B:A Good Kit for Starters

Resources

User's Manual & Datasheets

Development Guide

Update Log

March-22-2016

  • Released English Version

March-29-2016

  • Corrected expression errors

Apr-02-2016

  • Rewrote sections 4.3, 5, 6 and 8

Apr-15-2016

  • Added sections 5.10, 5.11, 7 and 9
  • Rewrote sections 5.9, 6.2

Apr-18-2016

  • Update Features sections, "DDR3 RAM: 512MB" to "DDR3 RAM: 512MB/1GB"
  • Update Board Dimension to 1603B
  • Add dxf file and Schematic of 1603B to Resources section

July-07-2016

  • Added sections 7, 9.5, 9.6 and 11

Sep-08-2016

  • Added sections 5.10
  • Updated sections 5.11

Nov-03-2016

  • Updated section 5.10

Dec-09-2016

  • Updated section 5.8, 6.1, 8.1 and 8.3
  • Added section 7.3

Jan-30-2017

  • Added section 6.2, 8.2 and 9.3

June-4-2017

  • Added section 3: software features
  • Added section 10: setup compiler for user space programs

June-15-2017

  • Added section 7: UbuntuCore
  • Updated section 10

July-8-2017

  • Updated section 6.8