Difference between revisions of "NanoPi M1"

From FriendlyELEC WiKi
Jump to: navigation, search
(→‎Debian8(Jacer))
(updated by API)
 
(127 intermediate revisions by 5 users not shown)
Line 25: Line 25:
 
* Debug Serial Port: 4Pin, 2.54mm pitch pin header
 
* 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
 
* 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
+
* User Key: GPIO Key x 1, Reset x 1
 
* PC Size: 64 x 56mm
 
* PC Size: 64 x 56mm
 
* Power Supply: DC 5V/2A
 
* Power Supply: DC 5V/2A
 +
* Working Temperature: -30℃ to 70℃
 
* OS/Software: u-boot，Ubuntu MATE，Debian
 
* OS/Software: u-boot，Ubuntu MATE，Debian
 
[[File:NanoPi-M1-B03.png|frameless|500px|compact01]]
 
[[File:NanoPi-M1-B03.png|frameless|500px|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
 +
<!---
 +
* wiringNP to access GPIO pins
 +
--->
 +
* networkmanager: manage network
 +
* system log output from serial port
 +
<!---
 +
* nano editor
 +
* welcome window with basic system information and status
 +
--->
 +
* auto-login with user account "pi" with access to npi-config
 +
<!---
 +
* sudoers include "fa"
 +
* on first system boot file system will be automatically extended.
 +
* supports file system auto check and repair on system boot.
 +
* supports FriendlyElec's [http://wiki.friendlyelec.com/wiki/index.php/NanoHat_PCM5102A NanoHat-PCM5102A] 
 +
* supports USB WiFi module: refer to [[#Connect USB WiFi to NEO]]
 +
* supports audio recording and playing with 3.5mm audio jack
 +
* supports USB Host and 100M Ethernet
 +
* supports FriendlyElec BakeBit modules
 +
* supports dynamic frequency scaling and voltage regulation
 +
* relieves overheat compared to kernel Linux-3.4
 +
* fixed MAC address
 +
--->
 +
<!---
 +
===Ubuntu OLED===
 +
* mainline kernel: Linux-4.11.2
 +
* supports FriendlyElec's OLED module
 +
--->
 +
 +
===Debian Jessie===
 +
* welcome window with basic system information and status
 +
* npi-config: system configuration utility for setting passwords, language, timezone, hostname,
 +
<!---
 +
===Debian for NAS Dock===
 +
* mainline kernel: Linux-4.11.2
 +
* supports FriendlyElec's NAS Dock
 +
* optimized OpenMediaVault configuration options
 +
* allocated swap section
 +
--->
 +
 +
===Android===
 +
* supports USB WiFi
  
 
==Diagram, Layout and Dimension==
 
==Diagram, Layout and Dimension==
Line 42: Line 95:
 
|1    || SYS_3.3V  ||    ||2    || VDD_5V ||
 
|1    || SYS_3.3V  ||    ||2    || VDD_5V ||
 
|-
 
|-
−
|3    || I2C0_SDA  ||    ||4    || VDD_5V ||
+
|3    || I2C0_SDA/GPIOA12   ||    ||4    || VDD_5V ||
 
|-  
 
|-  
−
|5    || I2C0_SCL   ||    ||6    || GND    ||
+
|5    || I2C0_SCL/GPIOA11  ||    ||6    || GND    ||
 
|-
 
|-
 
|7    || GPIOG11    || 203 ||8    || UART1_TX/GPIOG6 || 198
 
|7    || GPIOG11    || 203 ||8    || UART1_TX/GPIOG6 || 198
Line 50: Line 103:
 
|9    || GND        ||    ||10    || UART1_RX/GPIOG7 || 199   
 
|9    || GND        ||    ||10    || UART1_RX/GPIOG7 || 199   
 
|-
 
|-
−
|11  || UART2_TX/GPIOA0  || 0      ||12    || PWM1/GPIOA6 || 6
+
|11  || UART2_TX/GPIOA0  || 0      ||12    || GPIOA6 || 6
 
|-
 
|-
 
|13  || UART2_RTS/GPIOA2 || 2      ||14    || GND ||  
 
|13  || UART2_RTS/GPIOA2 || 2      ||14    || GND ||  
Line 66: Line 119:
 
|25  || GND              ||        ||26    || SPDIF-OUT/GPIOA17 || 17
 
|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
+
|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            ||
 
|29  || GPIOA20/PCM0_DOUT/I2S0_SDOUT          || 20    ||30    || GND            ||
 
|-
 
|-
−
|31  || GPIOA21/PCM0_DIN/I2S0_SDIN         || 21    ||32    || GPIOA7          || 7
+
|31  || GPIOA21/PCM0_DIN/I2S0_SDIN         || 21    ||32    || GPIOA7          || 7
 
|-
 
|-
 
|33  || GPIOA8          || 8      ||34    || GND            ||
 
|33  || GPIOA8          || 8      ||34    || GND            ||
Line 80: Line 133:
 
|39  || GND              ||        ||40    || UART3_RX/SPI1_CLK/GPIOA14  || 14
 
|39  || GND              ||        ||40    || UART3_RX/SPI1_CLK/GPIOA14  || 14
 
|}
 
|}
−
<!---
 
−
::{| class="wikitable"
 
−
|-
 
−
|Pin# || Name          ||Pin#  || Name   
 
−
|-
 
−
|1    || SYS_3.3V  ||2    || VDD_5V
 
−
|-
 
−
|3    || I2C0_SDA      ||4    || VDD_5V
 
−
|-
 
−
|5    || I2C0_SCL      ||6    || GND
 
−
|-
 
−
|7    || GPIOG11      ||8    || UART1_TX/GPIOG6
 
−
|-
 
−
|9    || GND          ||10    || UART1_RX/GPIOG7 
 
−
|-
 
−
|11  || UART2_TX/GPIOA0      ||12    || PWM1/GPIOA6
 
−
|-
 
−
|13  || UART2_RTS/GPIOA2      ||14    || GND
 
−
|-
 
−
|15  || UART2_CTS/GPIOA3      ||16    || UART1_RTS/GPIOG8
 
−
|-
 
−
|17  || SYS_3.3V ||18    || UART1_CTS/GPIOG9
 
−
|-
 
−
|19  || SPI0_MOSI/GPIOC0    ||20    || GND
 
−
|-
 
−
|21  || SPI0_MISO/GPIOC1    ||22    || UART2_RX/GPIOA1
 
−
|-
 
−
|23  || SPI0_CLK/GPIOC29    ||24    || SPI0_CS/GPIOC3
 
−
|-
 
−
|25  || GND          ||26    || SPDIF-OUT/GPIOA17
 
−
|-
 
−
|27  || I2C1_SDA/GPIOA19    ||28    || I2C1_SCL/GPIOA18
 
−
|-
 
−
|29  || GPIOA20        ||30    || GND
 
−
|-
 
−
|31  || GGPIOA21    ||32    || GPIOA7
 
−
|-
 
−
|33  || GPIOA8      ||34    || GND
 
−
|-
 
−
|35  || UART3_CTS/SPI1_MISO/GPIOA16    ||36    || UART3_TX/SPI1_CS/GPIOA13
 
−
|-
 
−
|37  || GPIOA9    ||38    || UART3_RTS/SPI1_MOSI/GPIOA15
 
−
|-
 
−
|39  || GND          ||40    || UART3_RX/SPI1_CLK/GPIOA14
 
−
|}
 
−
--->
 
  
 
* '''Debug Port（UART0）'''
 
* '''Debug Port（UART0）'''
Line 136: Line 143:
 
|2    || VDD_5V     
 
|2    || VDD_5V     
 
|-  
 
|-  
−
|3    || UART_TXD0     
+
|3    || UART_TXD0/GPIOA4    
 
|-
 
|-
−
|4    || UART_RXD0  
+
|4    || UART_RXD0/GPIOA5/PWM0
 
|}
 
|}
  
Line 172: Line 179:
 
:'''Note:'''
 
:'''Note:'''
 
::#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.5V
 
::#All pins are 3.3V and output current is 5mA. It can drive small loads. No IO pins can drive a load.
 
::#All pins are 3.3V and output current is 5mA. It can drive small loads. No IO pins can drive a load.
−
::#For more details refer to the document: [http://wiki.friendlyarm.com/wiki/images/6/68/NanoPi-M1-1603B-Schematic.pdf NanoPi-M1-1603B-Schematic.pdf]
+
::#For more details refer to the document: [http://wiki.friendlyelec.com/wiki/images/1/1e/Schematic_NanoPi-M1-V1.1_1804.pdf NanoPi-M1-V1.1-1804-Schematic.pdf]
  
 
===Board Dimension===
 
===Board Dimension===
 
[[File:NanoPi-M1-1603B-dimensions.png|frameless|500px|]]
 
[[File:NanoPi-M1-1603B-dimensions.png|frameless|500px|]]
  
−
::For more details please refer to: [http://wiki.friendlyarm.com/wiki/images/0/01/NanoPi-M1-1603B-dimensions%28dxf%29.zip pcb file in dxf]
+
::For more details please refer to: [http://wiki.friendlyelec.com/wiki/index.php/File:NanoPi_M1_v1.1_1804_PCB.rar NanoPi-M1-V1.0-1804-dimensions(dxf)]
  
 
==Get Started==
 
==Get Started==
Line 189: Line 196:
 
* HDMI monitor
 
* HDMI monitor
 
* USB keyboard and mouse
 
* USB keyboard and mouse
−
* A host computer running Ubuntu 14.04 64 bit system
+
* A host computer running Ubuntu 18.04 64 bit system
  
−
===TF Cards We Tested===
+
{{TFCardsWeTested}}
−
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:
+
−
[[File:SanDisk MicroSD.png|frameless|100px|SanDisk MicroSD 8G]]
+
−
* SanDisk TF128G MicroSDXC TF 128G Class10 48MB/S:
+
−
[[File:SanDisk MicroSD-01.png|frameless|100px|SanDisk MicroSD 128G]]
+
−
* 川宇 8G C10 High Speed class10 micro SD card:
+
−
[[File:SanDisk MicroSD-02.png|frameless|100px|chuanyu MicroSD 8G]]
+
  
−
===Make an Installation TF Card===
+
{{Downloads-H3|NanoPi-M1}}
−
====Get Image Files====
+
−
Visit this link [https://www.mediafire.com/folder/3q2911p1qp33p/NanoPi-M1Board download link] to download image files and the flashing utility:<br />
+
  
−
::{| class="wikitable"
+
====Comparison of Linux-3.4 and Linux-4.14====
−
|-
+
{{AllwinnerH3-KernelDiff|NanoPi-M1}}
−
|colspan=2|Image Files
+
−
|-
+
−
|nanopi-m1-debian-sd4g.img.zip      || Debian Image File       
+
−
|-
+
−
|nanopi-m1-ubuntu-core-qte-sd4g.img.zip      || Ubuntu core Image File. This system has a Qt Embedded library       
+
−
|-
+
−
|nanopi-m1-android.img.zip      || Android Image File                 
+
−
|-
+
−
|colspan=2|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
+
−
|-  
+
−
|}
+
  
−
====Make Debian Image Card====
+
{{BurnOS-Allwinner|NanoPi-M1}}
−
* Uncompress the nanopi-m1-debian-sd4g.img.zip and win32diskimager.rar files. 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.<br />
+
−
Note:you can make a Ubuntu image card in this way too.
+
  
−
====Make Android Image Card====
+
{{DebianJessieGeneral|NanoPi-M1}}
−
* 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.
+
{{DebianJessieAllwinnerH3|NanoPi-M1}}
−
* Uncompress the nanopi-m1-android.img.zip and PhoenixCard_V310.rar files. 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.<br />
+
−
Note: you must format your TF card before you start making it an Android image card.
+
  
−
==Working with Debian==
+
{{FriendlyCoreGeneral|NanoPi-M1}}
−
===Run Debian===
+
{{FriendlyCoreAllwinnerH3|NanoPi-M1}}
−
* 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.<br />
+
−
1）If you connect the NanoPi M1 to an HDMI monitor you need to use a USB mouse and a USB keyboard to operate.<br />
+
−
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.<br />
+
−
* 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:
+
−
[[File:PSU-ONECOM-M1.jpg|frameless|400px|PSU-ONECOM-M1]]
+
−
* The password for "root" is "fa".
+
−
* Update packages
+
−
<syntaxhighlight lang="bash">
+
−
sudo apt-get update
+
−
</syntaxhighlight>
+
  
−
===Extend TF Card's rootfs Section===
+
{{OpenWrt1|NanoPi-M1}}
−
<!---
+
−
We strongly recommend you to do this right after you have made an installation TF card since this will greatly enhance your M1's experience.<br>
+
−
Insert your TF card into a host PC and run the following commands on your PC'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>
+
−
Note: you need to replace "/dev/sdx" with the device name in your system
+
  
−
* If you want to resize the rootfs section of the TF card run the following commands on the NanoPi M1's Debian terminal:
+
==Make Your Own Linux System==
−
<syntaxhighlight lang="bash">
+
===Make Image Based on Linux-4.14 BSP===
−
sudo fs_resize
+
The NanoPi M1 supports the Linux-4.14 kernel which is mainly maintained and supported by open source communities. FriendlyElec ported this kernel to the NanoPi M1.<br>
−
</syntaxhighlight>
+
Here is a reference link to more details about how to make image files for Allwinner H3 based on mainline U-boot and Linux-4.14:[[Building U-boot and Linux for H5/H3/H2+]] <br>
−
Following the prompt type in "y" to start re-sizing the file system and a second "y" to reboot the M1. After the M1 is rebooted check the new section by using the following command：
+
−
--->
+
−
When you boot Debian 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:
+
−
<syntaxhighlight lang="bash">
+
−
df -h
+
−
</syntaxhighlight>
+
  
−
===Ethernet Connection===
+
===Make Image Based on Linux-3.4 BSP===
−
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
+
The Linux3.4 BSP is provided by Allwinner. FriendlyElec ported this to the NanoPi M1.<br>
−
* Setup MAC Address
+
 
−
The NanoPi M1 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:
+
====Preparations====
 +
Get lichee source:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
vi /etc/network/interfaces.d/eth0
+
$ git clone https://github.com/friendlyarm/h3_lichee.git lichee --depth 1
−
</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.
+
−
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>
 
</syntaxhighlight>
 +
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.
  
−
===Login to Debian via VNC and SSH===
+
====Install Cross Compiler====
−
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 [http://www.realvnc.com/download/ here] on a mobile phone and login to the NanoPi M1 via VNC at port 1. Its default password is "fa123456".<br />
+
Visit this site [http://download.friendlyelec.com/nanopim1 download link], enter the "toolchain" directory, download the cross compiler "gcc-linaro-arm.tar.xz" and copy it to the "lichee/brandy/toochain/" directory.<br/>
−
Here is a screenshot which shows how it looks like when users login to the NanoPi M1 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" and the default password for "root" is "fa". You need to replace "192.168.8.1" with your actual IP address.<br />
+
−
<br />
+
−
 
+
 
<!---
 
<!---
−
===HDMI Resolution===
+
If you want to compile your own programs you need to setup a development environment. For more details about this you can refer to "Setup Cross Compiler for User Space Programs".<br />
−
Our Debian system's HDMI resolution is set by a script.bin file in the root directory of the installation TF card's boot section. By default the resolution is 1080P60. There are multiple script.bin files under that directory for different resolutions. For example if you want to modify the resolution to 720P60 you can use the script-720p-60.bin file to replace the existing one by using the following command:
+
(Allwinner's compiler doesn't work very well for some programs)
−
<syntaxhighlight lang="bash">
+
−
# in TF card boot partition
+
−
cp script/script-720p-60.bin ./script.bin
+
−
</syntaxhighlight>
+
 
--->
 
--->
  
−
===HDMI Audio Output===
+
====Compile lichee Source Code====
−
Our Debian 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:
+
−
<syntaxhighlight lang="bash">
+
−
pcm.!default {
+
−
    type hw
+
−
    card 1
+
−
    device 0
+
−
}
+
−
 
+
−
ctl.!default {
+
−
    type hw
+
−
    card 1
+
−
}
+
−
</syntaxhighlight>
+
−
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===
+
−
After Debian loads please login from a terminal and run "glmark2-es2":
+
−
<syntaxhighlight lang="bash">
+
−
glmark2-es2
+
−
</syntaxhighlight>
+
−
[[File:m1-gpu-glmark2.png|frameless|500px|m1-gpu-glmark2]]
+
−
 
+
−
===Test VPU===
+
−
Visit this link [http://pan.baidu.com/s/1eRefpT4 download link] to download files<br>
+
−
After Debian is loaded login from a terminal and run the following commands:
+
−
<syntaxhighlight lang="bash">
+
−
sudo apt-get install mpv
+
−
video_play mpv ./big_buck_bunny_1080p_H264_AAC_25fps_7200K.MP4
+
−
</syntaxhighlight>
+
−
In our test it could do hard coding and play 1080P video fluently.
+
−
 
+
−
===Test USB WiFi===
+
−
Our Debian 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;
+
−
::{| class="wikitable"
+
−
|-
+
−
|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 you 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 "wlan0" is listed it indicates your USB WiFi has been recognized:
+
−
<syntaxhighlight lang="bash">
+
−
ifconfig -a
+
−
</syntaxhighlight>
+
−
Open the /etc/wpa_supplicant/wpa_supplicant.conf file and append the following lines:
+
−
<syntaxhighlight lang="bash">
+
−
network={
+
−
        ssid="YourWiFiESSID"
+
−
        psk="YourWiFiPassword"
+
−
}
+
−
</syntaxhighlight>
+
−
The "YourWiFiESSID" and "YourWiFiPassword" need to be replaced with your actual ESSID and password.<br/>
+
−
Save, exit and run the following commands to connect to your WiFi router:
+
−
<syntaxhighlight lang="bash">
+
−
ifdown wlan0
+
−
ifup wlan0
+
−
</syntaxhighlight>
+
−
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:
+
−
<syntaxhighlight lang="bash">
+
−
wpa_passphrase YourWiFiESSID
+
−
</syntaxhighlight>
+
−
Following the prompt type in your password and you will get a new password in the /etc/wpa_supplicant/wpa_supplicant.conf file. Now you can replace the existing password in the wlan0 file with the new one.
+
−
 
+
−
===Connect NanoPi M1 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]].<br>
+
−
[[File:NanoPi-M1-cam500a.jpg|frameless|500px|NanoPi-M1-cam500a]] <br>
+
−
Follow the hardware setup presented in the above picture to connect your NanoPi M1 to a CAM500B. Then boot Debian, connect your M1 to a network, log into the board as root and run "mjpg-streamer":
+
−
<syntaxhighlight lang="bash">
+
−
cd /root/mjpg-streamer
+
−
make
+
−
./start.sh
+
−
</syntaxhighlight>
+
−
The mjpg-streamer application is an open source video steam server. After it is successfully started the following messages will be popped up:
+
−
<syntaxhighlight lang="bash">
+
−
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
+
−
</syntaxhighlight>
+
−
 
+
−
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:<br>
+
−
[[File:mjpg-streamer-cam500a.png|frameless|600px|mjpg-streamer-cam500a]] <br>
+
−
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:
+
−
<syntaxhighlight lang="bash">
+
−
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
+
−
</syntaxhighlight>
+
−
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.<br>
+
−
In this use case the NanoPi M1 runs Debian. Connect your NanoPi M1 to an HDMI monitor. After Debain is fully loaded open a terminal and run the following command:
+
−
<syntaxhighlight lang="bash">
+
−
xawtv 0
+
−
</syntaxhighlight>
+
−
You will be able to preview with your camera
+
−
Note: "0" in our case stands for the camera's device name "/dev/video0". You need to use your camera's index in this command.
+
−
 
+
−
===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:
+
−
<syntaxhighlight lang="bash">
+
−
apt-get update
+
−
apt-get install libcv-dev libopencv-dev
+
−
</syntaxhighlight>
+
−
* 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):
+
−
<syntaxhighlight lang="bash">
+
−
cd /home/fa/Documents/opencv-demo
+
−
make
+
−
./demo
+
−
</syntaxhighlight>
+
−
Here is what you expect to observe:<br>
+
−
[[File:OpenCV-M1.png|frameless|600px|OpenCV-M1]]
+
−
 
+
−
===Check CPU's Working Temperature===
+
−
You can use the following command to read H3's temperature and frequency
+
−
<syntaxhighlight lang="bash">
+
−
cpu_freq
+
−
</syntaxhighlight>
+
−
 
+
−
===Check System Information with Rpi-Monitor===
+
−
Our Debian contains the Rpi-Monitor utility with which users can check system information and status.<br>
+
−
In our case our NanoPi M1's IP was 192.168.1.230 and we typed the following IP in a browser:
+
−
<syntaxhighlight lang="bash">
+
−
192.168.1.230:8888
+
−
</syntaxhighlight>
+
−
We were directed to the following page:<br>
+
−
[[File:rpi-monitor.png|frameless|500px|rpi-monitor]] <br>
+
−
Users can easily check these system information and status.
+
−
 
+
−
==Make Your Own Debian==
+
−
===Preparations===
+
−
Visit this link [https://www.mediafire.com/folder/u05rynncjgkse/sources] and enter the "sources/nanopi-H3-bsp" directory and download all the source code.Use the 7-zip utility to uncompress it and a lihee directory and an Android directory will be generated.You can check that by running the following command:
+
−
<syntaxhighlight lang="bash">
+
−
ls ./
+
−
android lichee
+
−
</syntaxhighlight>
+
−
 
+
−
Or you can get it from our github:
+
−
<syntaxhighlight lang="bash">
+
−
git clone https://github.com/friendlyarm/h3_lichee.git lichee
+
−
</syntaxhighlight>
+
−
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 [https://pan.baidu.com/s/1dF7HL0P 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:
 
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:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
sudo apt-get install gawk git gnupg flex bison gperf build-essential \
+
$ sudo apt-get install gawk git gnupg flex bison gperf build-essential \
 
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
 
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
 
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
 
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
Line 480: Line 247:
 
</syntaxhighlight>
 
</syntaxhighlight>
  
−
Enter the lichee directory and un the following command to compile the whole package:
+
Enter the lichee directory and run the following command to compile the whole package:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
cd lichee
+
$ cd lichee/fa_tools
−
./build.sh -p sun8iw7p1 -b nanopi-h3
+
$ ./build.sh -b nanopi-m1 -p linux -t all
 
</syntaxhighlight>
 
</syntaxhighlight>
 
After this compilation succeeds a u-boot, Linux kernel and kernel modules will be generated<br>
 
After this compilation succeeds a u-boot, Linux kernel and kernel modules will be generated<br>
−
Note: the lichee directory contains a cross-compiler we have setup. When the build.sh script runs it will automatically call this cross-compiler.
+
Note: the lichee directory contains a cross-compiler we have setup. When you compile the source code it will automatically call this cross-compiler.
  
−
===Package System Modules===
+
====Compile U-boot====
 +
Note:you need to compile the whole lichee directory before you can compile U-boot individually.<br>
 +
You can run the following commands to compile U-boot:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
./gen_script.sh -b nanopi-m1
+
$ cd lichee/fa_tools/
−
</syntaxhighlight>
+
$ ./build.sh -b nanopi-m1-plus -p linux -t u-boot
−
This command patches the uboot with Allwinner features and copies the generated executables including u-boot and Linux kernel and configuration files to the "lichee/tools/pack/out/" directory and generates a script.bin.<br>
+
−
<!---
+
−
The script.bin file is designed by Allwinner for its CPUs. For more details refer to [http://linux-sunxi.org/Script.bin script.bin].
+
−
--->
+
−
 
+
−
Run the following commands to update the uboot on your MicroSD card:
+
−
<syntaxhighlight lang="bash">
+
−
./fuse_uboot.sh /dev/sdx
+
−
</syntaxhighlight>
+
−
Replace the "/dev/sdx" with the actual device name of your MicroSD card.<br>
+
−
The boot.img and kernel modules are under the "linux-3.4/output" directory. You can copy the new boot.img file to your MicroSD card's boot section.
+
−
 
+
−
===Compile U-boot===
+
−
<syntaxhighlight lang="bash">
+
−
./build.sh -p sun8iw7p1 -b nanopi-h3 -m uboot
+
−
./gen_script.sh -b nanopi-m1
+
 
</syntaxhighlight>
 
</syntaxhighlight>
 
The gen_script.sh script patches the U-boot with Allwinner features. A U-boot without these features cannot work.<br>
 
The gen_script.sh script patches the U-boot with Allwinner features. A U-boot without these features cannot work.<br>
 
Type the following command to update the U-boot on the MicroSD card:
 
Type the following command to update the U-boot on the MicroSD card:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
./fuse_uboot.sh /dev/sdx
+
$ cd lichee/fa_tools/
 +
$ ./fuse.sh -d /dev/sdX -p linux -t u-boot
 
</syntaxhighlight>
 
</syntaxhighlight>
 
Note: you need to replace "/dev/sdx" with the device name in your system.
 
Note: you need to replace "/dev/sdx" with the device name in your system.
  
−
===Compile Linux Kernel===
+
====Compile Linux Kernel====
 +
Note:you need to compile the whole lichee directory before you can compile Linux kernel individually.<br>
 
If you want to compile the Linux kernel run the following command:
 
If you want to compile the Linux kernel run the following command:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
./build.sh -p sun8iw7p1 -b nanopi-h3 -m kernel
+
$ cd lichee/fa_tools/
 +
$ ./build.sh -b nanopi-m1 -p linux -t kernel
 
</syntaxhighlight>
 
</syntaxhighlight>
 
After the compilation is done a boot.img and its kernel modules will be generated under "linux-3.4/output".
 
After the compilation is done a boot.img and its kernel modules will be generated under "linux-3.4/output".
  
−
===Clean Source Code===
+
====Clean Source Code====
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
./build.sh -p sun8iw7p1 -b nanopi-h3 -m clean
+
$ cd lichee/fa_tools/
 +
$ ./build.sh -b nanopi-m1 -p linux -t clean
 
</syntaxhighlight>
 
</syntaxhighlight>
  
Line 572: Line 329:
  
 
===Play 4K Video===
 
===Play 4K Video===
−
Visit this the test-video directory of this link [https://pan.baidu.com/s/1dF7HL0P download link] and download the 4K video file: 4K-Chimei-inn-60mbps.mp4 and copy it to an SD card or USB drive.<br>
+
Visit this the test-video directory of this link [http://download.friendlyelec.com/nanopim1 download link] and download the 4K video file: 4K-Chimei-inn-60mbps.mp4 and copy it to an SD card or USB drive.<br>
 
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.<br>
 
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.<br>
 
In our test playing this 4K video file from a USB drive worked better.
 
In our test playing this 4K video file from a USB drive worked better.
Line 578: Line 335:
 
==Make Your Own Android==
 
==Make Your Own Android==
 
===Preparations===
 
===Preparations===
−
Visit this link [http://wiki.friendlyarm.com/wiki/nanopim1/download/] and enter the "sources/nanopi-H3-bsp" directory and download all the source code.Use the 7-zip utility to uncompress it and a lihee directory and an Android directory will be generated.You can check that by running the following command:
+
* 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:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
ls ./
+
$ sudo apt-get install gawk git gnupg flex bison gperf build-essential \
−
android lichee
+
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
 
</syntaxhighlight>
 
</syntaxhighlight>
  
−
Or you can get it from our github:
+
* Generating an Android image relies on the scripts in the lichee's source code. Therefore you need to clone lichee's source code:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
git clone https://github.com/friendlyarm/h3_lichee.git lichee
+
$ git clone https://github.com/friendlyarm/h3_lichee.git lichee
 
</syntaxhighlight>
 
</syntaxhighlight>
−
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.
+
Note:lichee is the name of the project in which Allwinner provides support for its CPUs. The lichee source code includes the source code of U-boot, Linux and various scripts. You cannot rename the "lichee" directory.<br>
  
−
===Install Cross Compiler===
+
* Clone Android Source Code:
−
Visit this site [https://pan.baidu.com/s/1dF7HL0P 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:
+
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
sudo apt-get install gawk git gnupg flex bison gperf build-essential \
+
$ git clone https://gitlab.com/friendlyelec/h3_android-4.4 android
−
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
+
 
</syntaxhighlight>
 
</syntaxhighlight>
−
 
+
Since generating an Android image relies on the scripts in the lichee's source code. Therefore you need to clone the Android source code under the same directory where lichee is located and name the cloned directory "android":
−
Enter the lichee directory and un the following command to compile the whole package:
+
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
cd lichee
+
$ ls ./
−
./build.sh lunch
+
android lichee
 
</syntaxhighlight>
 
</syntaxhighlight>
−
Select 2. sun8iw7p1-android-dolphin to compile the whole package and generate U-boot, Linux kernel and kernel modules.<br>
 
−
Note: the lichee directory contains a cross-compiler we have setup. When the build.sh script runs it will automatically call this cross-compiler.
 
  
−
===Compile Android Source Code===
+
* Install Cross Compiler:
−
Attention: before you start to compile the Android system you must compile the lichee.
+
In order to compile the lichee source code you need to visit this site [http://download.friendlyelec.com/nanopim1 download link], enter the "toolchain" directory, download the cross compiler "gcc-linaro-arm.tar.xz" and copy it to the "lichee/brandy/toochain/" directory.<br/>
−
* Setup Compiler
+
 
 +
===Compile Android===
 +
* Setup Environment
 
Run the following commands on a host PC running 64-bit Ubuntu-14.04 LTS-64bit:
 
Run the following commands on a host PC running 64-bit Ubuntu-14.04 LTS-64bit:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
sudo apt-get install bison g++-multilib git gperf libxml2-utils make python-networkx zip
+
$ sudo apt-get install bison g++-multilib git gperf libxml2-utils make python-networkx zip flex libncurses5-dev zlib1g-dev gawk minicom
−
sudo apt-get install flex libncurses5-dev zlib1g-dev gawk minicom
+
 
</syntaxhighlight>
 
</syntaxhighlight>
−
For more details refer to :[https://source.android.com/source/initializing.html android_initializing]。
+
For more details refer to:[https://source.android.com/source/initializing.html android_initializing]。
  
 
* Install JDK
 
* Install JDK
Line 626: Line 376:
 
* Compile System
 
* Compile System
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
cd lichee
+
$ cd lichee/fa_tools/
−
export PATH=/usr/lib/jvm/jdk1.6.0_45/bin:$PATH
+
$ ./build.sh -b nanopi-m1 -p android -t all            # compile lichee's source code and this will generate a kernel and drivers for Android.
−
./gen_android_img.sh -b nanopi-m1 -t android
+
$ cd ../../android
 +
$ export PATH=/usr/lib/jvm/jdk1.6.0_45/bin:$PATH
 +
$ ./build.sh -b nanopi-m1     # compile android's source code and this will generate an Android image file.
 
</syntaxhighlight>
 
</syntaxhighlight>
−
After the above commands are finished an Android image "sun8iw7p1_android_nanopi-h3_uart0.img" will be generated under the "lichee/tools/pack/" directory.
+
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===
 
===Clean Source Code===
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
./build.sh -p sun8iw7p1_android -b nanopi-h3 -m clean
+
$ cd lichee/fa_tools/
 +
$ ./build.sh -b nanopi-m1 -p android -t clean
 
</syntaxhighlight>
 
</syntaxhighlight>
  
−
==More OS Support==
+
==Developer Guide==
−
===Ubuntu-Core with Qt-Embedded===
+
===CVBS===
−
<!---
+
[[CVBS | Linux-3.4 - Set up CVBS ]]
−
Ubuntu-Core is a basic verson which has support for Ethernet and SSH.<br>
+
−
FriendlyARM doesn't provide technical support for it.<br>
+
−
* Go to this link [http://wiki.friendlyarm.com/nanopim1/download/ download link] to download the image file nanopi-m1-ubuntu-core-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
+
−
--->
+
−
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 [http://wiki.friendlyarm.com/wiki/index.php/Ubuntu_Core_with_Qt-Embedded Ubuntu Core with Qt-Embedded].<br>
+
−
 
+
−
Flash Ubuntu-Core with Qt-Embedded to TF Card:<br>
+
−
* Download the firmware nanopi-m1-core-qte-sd4g-20160628.img.zip (under official-ROMs) [http://wiki.friendlyarm.com/nanopim1/download/ click to download]
+
−
* Uncompress the file and flash the image to a TF card with win32diskimager.
+
−
* Insert this card to your NanoPi M1, power on the board and you will be able to play with your UbuntuCore
+
−
* Login name is root or fa and the password is fa
+
−
 
+
−
For more details visit [http://wiki.friendlyarm.com/wiki/index.php/Ubuntu_Core_with_Qt-Embedded Ubuntu Core with Qt-Embedded].
+
  
 +
{{H3-KernelHeaderFile}}
 +
{{MoreOS}}
 
===Ubuntu-MATE===
 
===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<br>
 
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<br>
 
FriendlyARM doesn't provide technical support for it
 
FriendlyARM doesn't provide technical support for it
−
* Go to this link [http://wiki.friendlyarm.com/nanopim1/download/ download link] to download the image file nanopi-m1-ubuntu-mate-sd4g.img.zip
+
* Go to this link [http://wiki.friendlyelec.com/nanopim1/download/ 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
 
* 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
 
* After it is done you can boot your NanoPi M1 with this card
 
* Login name: "root" or "fa", Password: fa
 
* Login name: "root" or "fa", Password: fa
 
[[File:MATE-desktop.png|frameless|600px|MATE-desktop]]
 
[[File:MATE-desktop.png|frameless|600px|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.<br />
 
−
The following steps are for reference only. FriendlyElec doesn't provide technical support for them.<br />
 
−
Installation guide:
 
−
* Download the image file "DietPi_NanoPiNEO-armv7-(Jessie)" from [http://dietpi.com/downloads/images/DietPi_NanoPiNEO-armv7-(Jessie).7z 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)===
 
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.<br>
 
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.<br>
 
FriendlyARM doesn't provide technical support for it.
 
FriendlyARM doesn't provide technical support for it.
−
* Please visit here :[http://wiki.friendlyarm.com/nanopim1/download/ download link] to download its image file Debian8(unofficial-Jacer).rar.
+
* Please visit here :[http://wiki.friendlyelec.com/nanopim1/download/ 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.
 
* 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
 
* After it is done you can boot your NanoPi M1 with this card
Line 720: Line 441:
 
FriendlyARM doesn't provide technical support for it.
 
FriendlyARM doesn't provide technical support for it.
 
* Download image files and utilities
 
* Download image files and utilities
−
1. Please visit here :[http://pan.baidu.com/s/1bAOPf4 download link] to download its image file Android(Beelink_X2_v205k4_for_NanoPiM1).<br/>
+
1. Please visit here :[http://download.friendlyelec.com/nanopim1 download link] to download its image file Android(Beelink_X2_v205k4_for_NanoPiM1).<br/>
−
2. Download Windows utility (HDDLLF.4.40)[http://pan.baidu.com/s/1i5xZ8dZ download link] for formatting a TF card.<br/>
+
2. Download Windows utility (HDDLLF.4.40) for formatting a TF card.<br/>
−
3. Download Windows utility (PhoenixCard)[http://pan.baidu.com/s/1nvqzPYp download link] for flashing Android image files.<br/>
+
3. Download Windows utility (PhoenixCard) for flashing Android image files.<br/>
 
* Make Android TF Card
 
* 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;<br />
 
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;<br />
Line 744: Line 465:
 
[[File:Armbian-desktop.png|frameless|600px|Armbian-desktop]]
 
[[File:Armbian-desktop.png|frameless|600px|Armbian-desktop]]
  
−
===OpenWRT===
+
==Download Link to Image Files==
−
OpenWRT was migrated to the M1 by one hobbyist "Tom".<br>
+
* Image files: [http://download.friendlyelec.com/nanopim1]
−
FriendlyARM doesn't provide technical support for it.
+
−
* Visit [http://pan.baidu.com/s/1kUMdCQr/ 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
+
−
<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"
+
−
* 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:
+
−
<syntaxhighlight lang="bash">
+
−
dd if=openwrt-sunxi-NanoPi_M1-sdcard-vfat-ext4.img  of=/dev/sdx
+
−
</syntaxhighlight>
+
−
(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.
+
−
[[File:OpenWRT.png|frameless|600px|OpenWRT]]
+
  
 
==3D Housing Printing Files==
 
==3D Housing Printing Files==
Line 767: Line 473:
  
 
==Matrix Compact Kit B:A Good Kit for Starters==
 
==Matrix Compact Kit B:A Good Kit for Starters==
−
* Matrix - Compact Kit B:[http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Compact_Kit_B click to visit]
+
* Matrix - Compact Kit B:[http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Compact_Kit_B click to visit]
  
 +
{{DeveloperGuildH3|NanoPi-M1}}
 
==Resources==
 
==Resources==
 +
===User's Manual & Datasheets===
 
* Schematic  
 
* Schematic  
−
** [http://wiki.friendlyarm.com/wiki/images/d/d8/NanoPi-M1-1603-Schematic.pdf NanoPi-M1-1603-Schematic.pdf]  
+
** [http://wiki.friendlyelec.com/wiki/images/1/1e/Schematic_NanoPi-M1-V1.1_1804.pdf NanoPi-M1-V1.0-1804-Schematic.pdf]
−
** [http://wiki.friendlyarm.com/wiki/images/6/68/NanoPi-M1-1603B-Schematic.pdf NanoPi-M1-1603B-Schematic.pdf]
+
** [http://wiki.friendlyelec.com/wiki/images/d/d8/NanoPi-M1-1603-Schematic.pdf NanoPi-M1-1603-Schematic.pdf]  
 +
** [http://wiki.friendlyelec.com/wiki/images/6/68/NanoPi-M1-1603B-Schematic.pdf NanoPi-M1-1603B-Schematic.pdf]
 +
 
 
* Dimensional Diagram  
 
* Dimensional Diagram  
−
** [http://wiki.friendlyarm.com/wiki/images/a/ad/NanoPi-M1-1603-dimensions%28dxf%29.zip NanoPi-M1-1603-dimensions(dxf).zip]
+
** [http://wiki.friendlyelec.com/wiki/index.php/File:NanoPi_M1_v1.1_1804_PCB.rar NanoPi-M1-V1.0-1804-dimensions(dxf).rar]
−
** [http://wiki.friendlyarm.com/wiki/images/0/01/NanoPi-M1-1603B-dimensions%28dxf%29.zip NanoPi-M1-1603B-dimensions(dxf).zip]
+
** [http://wiki.friendlyelec.com/wiki/images/a/ad/NanoPi-M1-1603-dimensions%28dxf%29.zip NanoPi-M1-1603-dimensions(dxf).zip]
−
* Allwinner H3 datasheet [http://wiki.friendlyarm.com/wiki/images/4/4b/Allwinner_H3_Datasheet_V1.2.pdf Allwinner_H3_Datasheet_V1.2.pdf]
+
** [http://wiki.friendlyelec.com/wiki/images/0/01/NanoPi-M1-1603B-dimensions%28dxf%29.zip NanoPi-M1-1603B-dimensions(dxf).zip]
 +
* Allwinner H3 datasheet [http://wiki.friendlyelec.com/wiki/images/4/4b/Allwinner_H3_Datasheet_V1.2.pdf Allwinner_H3_Datasheet_V1.2.pdf]
 +
 
 +
===Development Guide===
 
* Matrix Modules & Wiki Sites:
 
* Matrix Modules & Wiki Sites:
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Button Button]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Button Button]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_LED LED]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_LED LED]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Analog_to_Digital_Converter A/D Converter]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Analog_to_Digital_Converter A/D Converter]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Relay Relay]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Relay Relay]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_3-Axis_Digital_Accelerometer 3-Axis Digital Accelerometer]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_3-Axis_Digital_Accelerometer 3-Axis Digital Accelerometer]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_3-Axis_Digital_Compass 3-Axis Digital Compass]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_3-Axis_Digital_Compass 3-Axis Digital Compass]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Temperature_Sensor Temperature Sensor]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Temperature_Sensor Temperature Sensor]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Temperature_and_Humidity_Sensor Temperature & Humidity Sensor]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Temperature_and_Humidity_Sensor Temperature & Humidity Sensor]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Buzzer Buzzer]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Buzzer Buzzer]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Joystick Joystick]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Joystick Joystick]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_I2C_LCD1602_Keypad I2C(PCF8574)+LCD1602]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_I2C_LCD1602_Keypad I2C(PCF8574)+LCD1602]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Sound_Sensor Sound Sensor]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Sound_Sensor Sound Sensor]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Ultrasonic_Ranger Ultrasonic Ranger]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Ultrasonic_Ranger Ultrasonic Ranger]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_GPS GPS]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_GPS GPS]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Compact_Kit Matrix - Compact Kit]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Compact_Kit Matrix - Compact Kit]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Fire_Sensor Fire Sensor]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Fire_Sensor Fire Sensor]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_CAM500A CAM500A Camera]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_CAM500A CAM500A Camera]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_BAll_Rolling_Switch BAll Rolling Switch]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_BAll_Rolling_Switch BAll Rolling Switch]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_2%278_SPI_Key_TFT 2'8 SPI Key TFT 2.8" SPI LCD]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_2%278_SPI_Key_TFT 2'8 SPI Key TFT 2.8" SPI LCD]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_IR_Counter IR Counter]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_IR_Counter IR Counter]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_IR_Receiver IR Receiver]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_IR_Receiver IR Receiver]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_L298N_Motor_Driver L298N Motor Driver]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_L298N_Motor_Driver L298N Motor Driver]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_MQ-2_Gas_Sensor MQ-2 Gas Sensor]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_MQ-2_Gas_Sensor MQ-2 Gas Sensor]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_MQ-3_Gas_Sensor MQ-3 Gas Sensor]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_MQ-3_Gas_Sensor MQ-3 Gas Sensor]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_One_Touch_Sensor One_Touch_Sensor]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_One_Touch_Sensor One_Touch_Sensor]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Photoresistor _Photoresistor]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Photoresistor _Photoresistor]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Potentiometer _Potentiometer]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Potentiometer _Potentiometer]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Pressure_and_Temperature_Sensor Pressure & Temperature Sensor]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Pressure_and_Temperature_Sensor Pressure & Temperature Sensor]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_RGB_LED RGB LED]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_RGB_LED RGB LED]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_RTC RTC]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_RTC RTC]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Rotary_Encoder Rotary Encoder]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Rotary_Encoder Rotary Encoder]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Soil_Moisture_Sensor Soil Moisture Sensor]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Soil_Moisture_Sensor Soil Moisture Sensor]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Thermistor Thermistor]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Thermistor Thermistor]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_USB_WiFi USB WiFi]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_USB_WiFi USB WiFi]
−
** [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_Water_Sensor Water Sensor]
+
** [http://wiki.friendlyelec.com/wiki/index.php/Matrix_-_Water_Sensor Water Sensor]
  
−
==Update Log==
+
==Hardware Differences Among Different Versions==
−
===March-22-2016===
+
* '''NanoPi M1 Version Compare & List（Hardware）'''
−
* Released English Version
+
::{| class="wikitable"
−
 
+
|-
−
===March-29-2016===
+
|version || NanoPi M1 1603B || NanoPi M1 V1.1 1804
−
* Corrected expression errors
+
|-
−
 
+
|Photo    ||[[File:NanoPi_M1_1603B.jpg |thumb|]]||[[File:NanoPi_M1_V1.1_1804.jpg |thumb|]]
−
===Apr-02-2016===
+
|-
−
* Rewrote sections 4.3, 5, 6 and 8
+
|Power Design  || ① VDD-CPUX use SY8113B || ① VDD-CPUX use MP2143DJ
−
 
+
|-
−
===Apr-15-2016===
+
|Audio  ||  ||② NanoPi M1 V1.1 1804 added C14 Capacitance to improve recording quality which 1603B doesn't have<br>
−
* Added sections 5.10, 5.11, 7 and 9
+
|-  
−
* Rewrote sections 5.9, 6.2
+
|MicroSD Card Slot ||  || ③ NanoPi M1 V1.1 1804 use new microSD card slot which is different from 1603B
−
 
+
|-  
−
===Apr-18-2016===
+
|Reset circuit||  || ③ NanoPi M1 V1.1 1804 added a reset IC which 1603B doesn't have<br>
−
* 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===
+
{{H3ChangeLog|NanoPi-M1}}
−
* Updated section 5.8, 6.1, 8.1 and 8.3
+
−
* Added section 7.3
+

Latest revision as of 08:38, 14 November 2023

查看中文

Contents

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

2 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: GPIO Key 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

3 Software Features

3.1 uboot

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

3.2 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

3.3 Debian Jessie

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

3.4 Android

  • supports USB WiFi

4 Diagram, Layout and Dimension

4.1 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.5V
  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-V1.1-1804-Schematic.pdf

4.2 Board Dimension

NanoPi-M1-1603B-dimensions.png

For more details please refer to: NanoPi-M1-V1.0-1804-dimensions(dxf)

5 Get Started

5.1 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 18.04 64 bit system

5.2 TF Cards We Tested

To make your device 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 MicroSDHC V30 32GB Extreme Pro (Developer choice)

SanDiskExtremePro

  • SanDisk 32GB High Endurance Video MicroSDHC Card with Adapter for Dash Cam and Home Monitoring Systems (High reliability)

SanDiskHighEndurance

  • SanDisk TF 8G Class10 Micro/SD High Speed 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

5.2.1 Downloads

5.2.1.1 Official image

Visit download link to download official image files (in the "01_Official images" directory).
The table below lists all official images, the word 'XYZ' in image filename meaning:

  • sd: Use it when you need to boot the entire OS from the SD card
  • eflasher: Use it when you need to flash the OS to eMMC via TF card
Icon Image Filename Version Description Kernel Version
Debian-icon.svg h3-XYZ-debian-bookworm-core-4.14-armhf-YYYYMMDD.img.gz bookworm Debian12 core，command line only 4.14.y
Debian-icon.svg h3-XYZ-debian-jessie-3.4-armhf-YYYYMMDD.img.gz jessie Debian8 Desktop 3.4.y
Debian-icon.svg h3-XYZ-debian-jessie-4.14-armhf-YYYYMMDD.img.gz jessie Debian8 Desktop 4.14.y
Ubuntu-icon.svg h3-XYZ-friendlycore-focal-4.14-armhf-YYYYMMDD.img.gz focal FriendlyCore, based on ubuntu focal, command line only 4.14.y
Ubuntu-icon.svg h3-XYZ-friendlycore-jammy-4.14-armhf-YYYYMMDD.img.gz jammy FriendlyCore, based on ubuntu jammy, command line only 4.14.y
Ubuntu-icon.svg h3-XYZ-friendlycore-xenial-4.14-armhf-YYYYMMDD.img.gz xenial FriendlyCore, based on ubuntu xenial, command line only 4.14.y
Ubuntu-icon.svg h3-XYZ-friendlycore-xenial-3.4-armhf-YYYYMMDD.img.gz xenial FriendlyCore, based on ubuntu xenial, command line only 3.4.y
Openwrt-icon.svg h3-XYZ-friendlywrt-4.14-armhf-YYYYMMDD.img.gz 19.07.1 base on openwrt 4.14.y
Other Image
Android-icon.svg sun8iw7p1_android_h3_uart0.img.zip Android4.4.2 Android, only supports SD card booting 3.4.y
Linux-tux.svg h3-XYZ-multiple-os-YYYYMMDD-25g.img.gz - It contains multiple OS image files, making it convenient for testing different operating systems, this image disables automatic flashing at startup; you will need to manually select the OS to flash.
5.2.1.2 Tools (optional)

Visit download link to download tools (in the "05_Tools" directory).

Filename Description
win32diskimager.rar This program is designed to write a raw disk image to a removable device or backup a removable device to a raw image file
SD Card Formatter A program (application) that allows easy and quick clear the SD card

5.2.2 Comparison of Linux-3.4 and Linux-4.14

  • Our Linux-3.4 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. If your application needs to use VPU or GPU you need to use the 3.4 kernel based ROM and use a heat sink together with your board.
  • Our Linux-4.14 is based on the mainline kernel. We will keep this kernel with the latest one released by Linus Torvalds. This kernel is stable and doesn't generate heat that much. If your application doesn't need to use VPU or GPU we recommend you to use this kernel.
  • For more details about the Linux-4.14 kernel refer to: Building U-boot and Linux for H5/H3/H2+


5.2.3 Android

5.2.3.1 Flash to TF

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 8G) 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 the the Android image 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.

PhoenixCard boot.png
(In the screenshot an Android image file for the NanoPi M1 Plus was selected. You need to select a correct image file for your board.)

  • Insert this card into your board' 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 board has successfully booted.

6 Working with Debian

6.1 Ethernet Connection

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

6.2 Wireless Connection

Under Debian you can manage your network with NetworkManager.
After Debian boots click on the network icon on the bottom right of the task bar a NetworkManger menu will pop up and all the available networks will be listed. If there is an active wireless network you will see something similar to the following screenshot:
NetworkManagerIcon
You can click on a WiFI AP and connect your board to it.
For more details refer to:NetworkManager.

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.


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

6.4 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。

6.5 Login via VNC and SSH

If your board is not connected to a display device you can login to your board from a mobile phone. You need to download and install a "VNC Viewer" from here on a mobile phone and login to the board 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 board from an iPhone via VNC:
VNC to NanoPi2
In our case our board'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.

6.6 Connect to USB Camera(FA-CAM202)

The FA-CAM202 is a 200M USB camera.
Refer to this link for more details on how to connect to a FA-CAM202: Connect NanoPi M1 to DVP Camera CAM500B
In Debian, 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.

6.7 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 board is connected to the internet and an HDMI monitor, Boot Debian 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

6.8 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.
connect your H3 board to a CAM500B. Then boot OS, connect your board 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 board'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 utility uses libjpeg to software-encode steam data. The Linux-4.x based ROM currently doesn't support hardware-encoding. If you use a Linux-3.x based ROM you can use the ffmpeg utility to hardware-encode stream data and this can greatly release CPU's resources and speed up 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.

6.9 Check CPU's Working Temperature

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

cpu_freq

6.10 Test GPU

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

glmark2-es2

m1-gpu-glmark2

6.11 Test VPU

Note: this function is only supported in Allwinner 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.

7 Work with FriendlyCore

7.1 Introduction

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

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

  • it integrates Qt4.8;
  • it integrates NetworkManager;
  • it has bluez and Bluetooth related packages;
  • it has alsa packages;
  • it has npi-config;
  • it has RPiGPIO, a Python GPIO module;
  • it has some Python/C demo in /root/ directory;
  • it enables 512M-swap partition;

7.2 System Login

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

allow you to operate the board via a serial terminal.Here is a setup where we connect a board 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.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:
USB2UART-M1.jpg

  • FriendlyCore User Accounts:

Non-root User: 

   User Name: pi
   Password: pi

Root: 

   User Name: root
   Password: fa

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

  • Update packages
$ sudo apt-get update

7.3 Configure System with npi-config

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

$ sudo npi-config

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

7.4 Develop Qt Application

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

7.5 Setup Program to AutoRun

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

sudo npi-config

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

7.6 Extend TF Card's Section

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

$ df -h


7.7 WiFi

For either an SD WiFi or a USB WiFi you can connect it to your board in the same way. The APXX series WiFi chips are SD WiFi chips. By default FriendlyElec's system supports most popular USB WiFi modules. Here is a list of the USB WiFi modules we tested:

Index Model
1 RTL8188CUS/8188EU 802.11n WLAN Adapter
2 RT2070 Wireless Adapter
3 RT2870/RT3070 Wireless Adapter
4 RTL8192CU Wireless Adapter
5 mi WiFi mt7601
6 5G USB WiFi RTL8821CU
7 5G USB WiFi RTL8812AU

You can use the NetworkManager utility to manage network. You can run "nmcli" in the commandline utility to start it. Here are the commands to start a WiFi connection:

  • Change to root
$ su root
  • Check device list
$ nmcli dev

Note: if the status of a device is "unmanaged" it means that device cannot be accessed by NetworkManager. To make it accessed you need to clear the settings under "/etc/network/interfaces" and reboot your system.

  • Start WiFi
$ nmcli r wifi on
  • Scan Surrounding WiFi Sources
$ nmcli dev wifi
  • Connect to a WiFi Source
$ nmcli dev wifi connect "SSID" password "PASSWORD" ifname wlan0

The "SSID" and "PASSWORD" need to be replaced with your actual SSID and password.If you have multiple WiFi devices you need to specify the one you want to connect to a WiFi source with iface
If a connection succeeds it will be automatically setup on next system reboot.

For more details about NetworkManager refer to this link: Use NetworkManager to configure network settings

If your USB WiFi module doesn't work most likely your system doesn't have its driver. For a Debian system you can get a driver from Debian-WiFi and install it on your system. For a Ubuntu system you can install a driver by running the following commands: 

$ apt-get install linux-firmware

In general all WiFi drivers are located at the "/lib/firmware" directory.


7.8 Ethernet Connection

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

7.9 WiringPi and Python Wrapper

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

7.11 Modify timezone

For exampe, change to Shanghai timezone: 

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

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


7.13 Connect to DVP Camera CAM500B

For NanoPi-M1 the CAM500B can work with both Linux-3.4 Kernel and Linux-4.14 Kernel.
The CAM500B camera module is a 5M-pixel camera with DVP interface. For more tech details about it you can refer to Matrix - CAM500B.

connect your board to camera module. Then boot OS, connect your board to a network, log into the board as root and run "mjpg-streamer": 

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

You need to change the start.sh script and make sure it uses a correct /dev/videoX node. You can check your camera's node by running the following commands: 

$ apt-get install v4l-utils
$ v4l2-ctl -d /dev/video0 -D
Driver Info (not using libv4l2):
        Driver name   : sun6i-video
        Card type     : sun6i-csi
        Bus info      : platform:camera
        Driver version: 4.14.0
	...

The above messages indicate that "/dev/video0" is camera's device node.The mjpg-streamer application is an open source video steam server. After it is successfully started the following messages will be popped up: 

 
$ ./start.sh
 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

start.sh runs the following two commands: 

export LD_LIBRARY_PATH="$(pwd)"
./mjpg_streamer -i "./input_uvc.so -d /dev/video0 -y 1 -r 1280x720 -f 30 -q 90 -n -fb 0" -o "./output_http.so -w ./www"

Here are some details for mjpg_streamer's major options:
-i: input device. For example "input_uvc.so" means it takes input from a camera;
-o: output device. For example "output_http.so" means the it transmits data via http;
-d: input device's subparameter. It defines a camera's device node;
-y: input device's subparameter. It defines a camera's data format: 1:yuyv, 2:yvyu, 3:uyvy 4:vyuy. If this option isn't defined MJPEG will be set as the data format;
-r: input device's subparameter. It defines a camera's resolution;
-f: input device's subparameter. It defines a camera's fps. But whether this fps is supported depends on its driver;
-q: input device's subparameter. It defines the quality of an image generated by libjpeg soft-encoding;
-n: input device's subparameter. It disables the dynctrls function;
-fb: input device's subparameter. It specifies whether an input image is displayed at "/dev/fbX";
-w: output device's subparameter. It defines a directory to hold web pages;

In our case the board'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 utility uses libjpeg to software-encode steam data. The Linux-4.14 based ROM currently doesn't support hardware-encoding. If you use a H3 boards with Linux-3.4 based ROM you can use the ffmpeg utility to hardware-encode stream data and this can greatly release CPU's resources and speed up 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.

7.14 Connect to USB Camera(FA-CAM202)

The FA-CAM202 is a 200M USB camera. Connect your board to camera module. Then boot OS, connect your board to a network, log into the board as root and run "mjpg-streamer": 

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

You need to change the start.sh script and make sure it uses a correct /dev/videoX node. You can check your camera's node by running the following commands: 

$ apt-get install v4l-utils
$ v4l2-ctl -d /dev/video0 -D
Driver Info (not using libv4l2):
        Driver name   : uvcvideo
        Card type     : HC 3358+2100: HC 3358+2100  / USB 2.0 Camera: USB 2.0 Camera
        Bus info      : usb-1c1b000.usb-1
	...

The above messages indicate that "/dev/video0" is camera's device node.The mjpg-streamer application is an open source video steam server. After it is successfully started the following messages will be popped up: 

 
$ ./start.sh
 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

start.sh runs the following two commands: 

export LD_LIBRARY_PATH="$(pwd)"
./mjpg_streamer -i "./input_uvc.so -d /dev/video0 -y 1 -r 1280x720 -f 30 -q 90 -n -fb 0" -o "./output_http.so -w ./www"

Here are some details for mjpg_streamer's major options:
-i: input device. For example "input_uvc.so" means it takes input from a camera;
-o: output device. For example "output_http.so" means the it transmits data via http;
-d: input device's subparameter. It defines a camera's device node;
-y: input device's subparameter. It defines a camera's data format: 1:yuyv, 2:yvyu, 3:uyvy 4:vyuy. If this option isn't defined MJPEG will be set as the data format;
-r: input device's subparameter. It defines a camera's resolution;
-f: input device's subparameter. It defines a camera's fps. But whether this fps is supported depends on its driver;
-q: input device's subparameter. It defines the quality of an image generated by libjpeg soft-encoding;
-n: input device's subparameter. It disables the dynctrls function;
-fb: input device's subparameter. It specifies whether an input image is displayed at "/dev/fbX";
-w: output device's subparameter. It defines a directory to hold web pages;

In our case the board'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

7.15 Check CPU's Working Temperature

You can get CPU's working temperature by running the following command: 

$ cpu_freq 
Aavailable frequency(KHz):
        480000 624000 816000 1008000
Current frequency(KHz):
        CPU0 online=1 temp=26548C governor=ondemand freq=624000KHz
        CPU1 online=1 temp=26548C governor=ondemand freq=624000KHz
        CPU2 online=1 temp=26548C governor=ondemand freq=624000KHz
        CPU3 online=1 temp=26548C governor=ondemand freq=624000KHz

This message means there are currently four CPUs working. All of their working temperature is 26.5 degree in Celsius and each one's clock is 624MHz.
Set CPU frequency: 

$ cpu_freq -s 1008000
Aavailable frequency(KHz):
        480000 624000 816000 1008000
Current frequency(KHz):
        CPU0 online=1 temp=36702C governor=userspace freq=1008000KHz
        CPU1 online=1 temp=36702C governor=userspace freq=1008000KHz
        CPU2 online=1 temp=36702C governor=userspace freq=1008000KHz
        CPU3 online=1 temp=36702C governor=userspace freq=1008000KHz


7.16 Test Infrared Receiver

Note: Please Check your board if IR receiver exist.
By default the infrared function is disabled you can enable it by using the npi-config utility: 

$ npi-config
    6 Advanced Options     Configure advanced settings
        A8 IR              Enable/Disable IR
            ir Enable/Disable ir[enabled]

Reboot your system and test its infrared function by running the following commands: 

$ apt-get install ir-keytable
$ echo "+rc-5 +nec +rc-6 +jvc +sony +rc-5-sz +sanyo +sharp +mce_kbd +xmp" > /sys/class/rc/rc0/protocols   # Enable infrared
$ ir-keytable -t
Testing events. Please, press CTRL-C to abort.

"ir-keytable -t" is used to check whether the receiver receives infrared signals. You can use a remote control to send infrared signals to the receiver. If it works you will see similar messages as follows: 

1522404275.767215: event type EV_MSC(0x04): scancode = 0xe0e43
1522404275.767215: event type EV_SYN(0x00).
1522404278.911267: event type EV_MSC(0x04): scancode = 0xe0e42
1522404278.911267: event type EV_SYN(0x00).

7.17 Run Qt Demo

Run the following command

$ sudo /opt/QtE-Demo/run.sh

Here is what you expect to observe. This is an open source Qt Demo:
K2-QtE

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

7.18.1 How to Install Docker

Run the following commands：

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

7.18.2 Test Docker installation

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

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


8 Work with OpenWrt

8.1 Introduction

OpenWrt is a highly extensible GNU/Linux distribution for embedded devices.Unlike many other distributions for routers, OpenWrt is built from the ground up to be a full-featured, easily modifiable operating system for embedded devices. In practice, this means that you can have all the features you need with none of the bloat, powered by a modern Linux kernel. For more details you can refer to:OpenWrt Website.

8.2 System Login

  • Login via Serial Port

When you do kernel development you'd better get a serial communication board. After you connect your board to a serial communication board you will be able to do development work from a commandline utility.
Here is a hardware setup:
After you connect your board to a serial communication board (e.g. FriendlyElec's serial communication board) you can power the whole system from either the DC port on the serial communication board or the MicroUSB port(if there is one) on your board:
PSU-ONECOM-M1.jpg

or you can use a USB to serial board and power on the whole system at the MicroUSB port with a 5V/2A power:
USB2UART-M1.jpg

By default you will login as root without a password. You can use "passwd" to set a password for root.
op_login
On first boot the system will automatically extend the file system on the TF card to the max capacity:
resize_rootfs_userdata
Please wait for this to be done.

  • Login via SSH

In FriendlyElec's OpenWrt system the Ethernet(eth0) is configured as WAN.
Before power on your board make sure your board is connected to a master router's LAN with an Ethernet cable and the eth0 will be assigned an IP address by DHCP.
For example, if your eth0 is assigned an IP address 192.168.1.163 you can login with SSH by running the following command: 

$ ssh root@192.168.1.163

You can login without a password.

  • Login via Web

You can login OpenWrt via a LuCI Web page.
After you go through all the steps in <Login via SSH> and get an IP address e.g. 192.168.1.163 for the Ethernet connection, type this IP address in a browser's address bar and you will be able to login OpenWrt-LuCI:
R1-OpenWrt-LuCI
By default you will login as root without a password, just click on "Login" to login.

8.3 Manage Software Packages

OpenWrt has a package management utility: opkg. You can get its details by running the following command: 

$ opkg
Package Manipulation:
        update                  Update list of available packages
        upgrade <pkgs>          Upgrade packages
        install <pkgs>          Install package(s)
        configure <pkgs>        Configure unpacked package(s)
        remove <pkgs|regexp>    Remove package(s)
        flag <flag> <pkgs>      Flag package(s)
         <flag>=hold|noprune|user|ok|installed|unpacked (one per invocation)
 
Informational Commands:
        list                    List available packages
        list-installed          List installed packages
        list-upgradable         List installed and upgradable packages
        list-changed-conffiles  List user modified configuration files
        files <pkg>             List files belonging to <pkg>
        search <file|regexp>    List package providing <file>
        find <regexp>           List packages whose name or description matches <regexp>
        info [pkg|regexp]       Display all info for <pkg>
        status [pkg|regexp]     Display all status for <pkg>
        download <pkg>          Download <pkg> to current directory
...

These are just part of the manual. Here are some popular opkg commands.

  • Update Package List

Before you install a package you'd better update the package list: 

$ opkg update
  • Check Available Packages
$ opkg list

At the time of writing there are 3241 packages available.

  • Check Installed Packages:
$ opkg list-installed

At the time of writing 124 packages have been installed.

  • Install/Delete Packages:
$ opkg install <pkgs>
$ opkg remove <pkgs>
  • Check Files Contained in Installed Packages:
$ opkg files <pkg>
  • Install Chinese Language Package for LuCI
$ opkg install luci-i18n-base-zh-cn
  • Check Changed Files:
$ opkg list-changed-conffiles

8.4 Check System Status

  • Check CPU Temperature & Frequency via Commandline
$ cpu_freq 
Aavailable frequency(KHz):
        480000 624000 816000 1008000
Current frequency(KHz):
        CPU0 online=1 temp=26548C governor=ondemand freq=624000KHz
        CPU1 online=1 temp=26548C governor=ondemand freq=624000KHz
        CPU2 online=1 temp=26548C governor=ondemand freq=624000KHz
        CPU3 online=1 temp=26548C governor=ondemand freq=624000KHz

These messages mean that there are four CPU cores working online simultaneously. Each core's temperature is 26.5 degrees in Celsius, the scheduling policy is on-demand and the working frequency is 624MHz. You can set the frequency by running the following command: 

$ cpu_freq -s 1008000
Aavailable frequency(KHz):
        480000 624000 816000 1008000
Current frequency(KHz):
        CPU0 online=1 temp=36702C governor=userspace freq=1008000KHz
        CPU1 online=1 temp=36702C governor=userspace freq=1008000KHz
        CPU2 online=1 temp=36702C governor=userspace freq=1008000KHz
        CPU3 online=1 temp=36702C governor=userspace freq=1008000KHz

These messages mean four CPU cores are working online. Each core's temperature is 26.5 degrees. Each core's governor is on demand and the frequency is 480 MHz.

  • Check System Status on OpenWrt-LuCI Web Page

After open the OpenWrt-LuCI page, go to "Statistics ---> Graphs" and you will see various system statistics e.g.:
1) System Load:
statistics_system_load
2) RAM:
statistics_memory
3) CPU Temperature:
statistics_thermal
All the statistics listed on the Statistics page are presented by the luci-app-statistics package which uses the Collectd utility to collect data and presents them with the RRDtool utility.
If you want to get more statistics you can install other collectd-mod-* packages. All collectd-mod-* packages use the same configuration file: /etc/config/luci_statistics.

8.5 Check Network->Interfaces Configurations

  • After open the OpenWrt-LuCI page, go to "Network" ---> "Interfaces" and you will see the current network's configurations:

op_interface_eth0

  • All the configurations listed on the Network->Interfaces page are stored in the "/etc/config/network" file.




8.6 USB WiFi

Currently the NanoPi NEO2 Black only works with a RTL8821CU USB WiFi dongle, plug and play. After this module is connected to the board it will by default work under AP mode and the hotspot's name is "rtl8821cu-mac address" and the password is "password";

8.7 Huawei's WiFi 2 mini(E8372H-155) Module

After this module is connected to the board it will be plug and play. The hotspot's name is "HUAWEI-8DA5". You can connect a device to the internet by connecting to this hotspot.

9 Make Your Own Linux System

9.1 Make Image Based on Linux-4.14 BSP

The NanoPi M1 supports the Linux-4.14 kernel which is mainly maintained and supported by open source communities. FriendlyElec ported this kernel to the NanoPi M1.
Here is a reference link to more details about how to make image files for Allwinner H3 based on mainline U-boot and Linux-4.14:Building U-boot and Linux for H5/H3/H2+

9.2 Make Image Based on Linux-3.4 BSP

The Linux3.4 BSP is provided by Allwinner. FriendlyElec ported this to the NanoPi M1.

9.2.1 Preparations

Get lichee source: 

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

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.

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

9.2.3 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/fa_tools
$ ./build.sh -b nanopi-m1 -p linux -t all

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.

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

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

9.2.6 Clean Source Code

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

10 Applications under Android

10.1 USB WiFi

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

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

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

11 Make Your Own Android

11.1 Preparations

  • 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
  • Generating an Android image relies on the scripts in the lichee's source code. Therefore you need to clone lichee's source code:
$ git clone https://github.com/friendlyarm/h3_lichee.git lichee

Note:lichee is the name of the project in which Allwinner provides support for its CPUs. The lichee source code includes the source code of U-boot, Linux and various scripts. You cannot rename the "lichee" directory.

  • Clone Android Source Code:
$ git clone https://gitlab.com/friendlyelec/h3_android-4.4 android

Since generating an Android image relies on the scripts in the lichee's source code. Therefore you need to clone the Android source code under the same directory where lichee is located and name the cloned directory "android": 

$ ls ./
android lichee
  • Install Cross Compiler:

In order to compile the lichee source code you need to 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.

11.2 Compile Android

  • Setup Environment

Run the following commands on a host PC running 64-bit Ubuntu-14.04 LTS-64bit: 

$ 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            # compile lichee's source code and this will generate a kernel and drivers for Android.
$ cd ../../android
$ export PATH=/usr/lib/jvm/jdk1.6.0_45/bin:$PATH
$ ./build.sh -b nanopi-m1			    # compile android's source code and this will generate an Android image file.

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

11.3 Clean Source Code

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

12 Developer Guide

12.1 CVBS

Linux-3.4 - Set up CVBS

13 Build Kernel Headers Package

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

13.1 Software Version

The OS image file name: nanopi-XXX_sd_friendlycore-focal_4.14_armhf_YYYYMMDD.img 

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04 LTS
Release:        20.04
Codename:       focal
 
$ cat /proc/version
Linux version 4.14.111 (root@ubuntu) (gcc version 4.9.3 (ctng-1.21.0-229g-FA)) #193 SMP Thu Jun 10 18:20:47 CST 2021

13.2 Install the required packages

sudo apt-get update
sudo apt-get install dpkg-dev libarchive-tools

13.3 Build Kernel Headers Package

git clone https://github.com/friendlyarm/linux -b sunxi-4.14.y --depth 1 kernel-h3
cd kernel-h3
rm -rf .git
make distclean
touch .scmversion
make CROSS_COMPILE= ARCH=arm sunxi_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-headers-4.14.111' in '../linux-headers-4.14.111_4.14.111-1_armhf.deb'.
dpkg-deb: building package 'linux-libc-dev' in '../linux-libc-dev_4.14.111-1_armhf.deb'.
dpkg-deb: building package 'linux-image-4.14.111' in '../linux-image-4.14.111_4.14.111-1_armhf.deb'.
dpkg-genchanges: warning: substitution variable ${kernel:debarch} used, but is not defined
dpkg-genchanges: info: binary-only upload (no source code included)

14 Installation=

sudo dpkg -i ../linux-headers-4.14.111_4.14.111-1_armhf.deb

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

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

sudo insmod ./pf_ring.ko

15 More OS Support

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

15.2 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

15.3 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

15.4 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) for formatting a TF card.
3. Download Windows utility (PhoenixCard) 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

15.5 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

16 Download Link to Image Files

  • Image files: [2]

17 3D Housing Printing Files

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

3D打印M1

18 Matrix Compact Kit B:A Good Kit for Starters

19 Developer's Guide

20 Resources

20.1 User's Manual & Datasheets

20.2 Development Guide

21 Hardware Differences Among Different Versions

  • NanoPi M1 Version Compare & List（Hardware）
version NanoPi M1 1603B NanoPi M1 V1.1 1804
Photo
NanoPi M1 1603B.jpg
NanoPi M1 V1.1 1804.jpg
Power Design ① VDD-CPUX use SY8113B ① VDD-CPUX use MP2143DJ
Audio ② NanoPi M1 V1.1 1804 added C14 Capacitance to improve recording quality which 1603B doesn't have
MicroSD Card Slot ③ NanoPi M1 V1.1 1804 use new microSD card slot which is different from 1603B
Reset circuit ③ NanoPi M1 V1.1 1804 added a reset IC which 1603B doesn't have

22 ChangeLog

2023-11-07
h3 FriendlyCore：
- Upgrade to Ubuntu Core 22.04;
h3 Debian Core：
- Add Debian bookworm core;

Retrieved from "https://wiki.friendlyelec.com/wiki/index.php?title=NanoPi_M1&oldid=25327"