Difference between revisions of "NanoPi M3"

Revision as of 03:36, 20 May 2016

查看中文

1 Introduction

Overview

Front

Back

• The NanoPi M3 is another ARM board developed by FriendlyARM for makers, hobbyists and hackers. With this new friend we wish you could get not only tech skills but also unique experiences in various applications and hacking. It is small, elegant but has rich ports and interfaces. Playing with it and working with it the M3 will not only inspire your ideas but also turn them into realities.
• The NanoPi M3 uses the Samsung Octa-Core Cortex-A53 S5P6818 SoC. Its dynamic frequency scales from 400M up to 1.4GHz. It has Gbps Ethernet port, built-in WiFi and Bluetooth. Its AXP228 PMU supports software power-off, sleep and wakeup functions. In addition the NanoPi M3 has MicroUSB port for power supply and on-board porcelain antenna.
• On this tiny board various ports and interfaces are integrated. It has DVP Camera/LVDS/HDMI/LCD interfaces, Gbps Ethernet, I2S, 3.5mm audio jack, four USB ports and a serial debug port.

2 Features

• SoC： Samsung S5P6818 Octa-Core Cortex-A53, 400M Hz - 1.4G Hz
• Power Management Unit： AXP228 PMU, it supports software power-off and wake-up.
• System Memory： 1GB 32bit DDR3 RAM
• Storage： 1 x MicroSD Card Socket
• Ethernet： Gbit Ethernet(RTL8211E)
• WiFi： 802.11b/g/n
• Bluetooth： 4.0 dual mode
• Antenna： Porcelain Antenna IPX Interface
• Audio： 3.5 mm audio jack / via HDMI
• I2S: 7pin, 2.54mm pitch pin-header
• Microphone: onboard Microphone
• USB Host： 4 x USB 2.0 Host, two type A ports and two 2.54 mm pitch pin-headers
• MicroUSB: 1 x MicroUSB 2.0 Client, Type A
• LCD Interface： 0.5mm pitch 45 pin FPC seat, full color RGB 8-8-8
• HDMI: 1.4A Type A, 1080P
• LVDS: 20pin 2.00mm pitch pin-header
• DVP Camera： 0.5mm pitch 24 pin FPC seat
• GPIO： 2.54 mm pitch 40 pin-header
• Serial Debug Port： 2.54mm pitch 4pin-header
• User Key: K1 (power), Reset
• LED： 1 x power LED and 1 x status LED
• RTC Battery： RTC Battery Seat
• Heat Sink： 1 x Heat Sink with mounting holes
• Power： DC 5V/2A
• PCB： Six Layer, ENIG
• Dimension： 64 mm x 60 mm
• OS/Software: uboot, Android and Debian

3 Diagram, Layout and Dimension

3.1 Layout

NanoPC-M3 Layout

• GPIO Pin Spec

Pin#	Name	Pin#	Name
1	SYS_3.3V	2	VDD_5V
3	I2C0_SDA	4	VDD_5V
5	I2C0_SCL	6	DGND
7	GPIOD8/PPM	8	UART3_TXD/GPIOD21
9	DGND	10	UART3_RXD/GPIOD17
11	UART4_TX/GPIOB29	12	GPIOD1/PWM0
13	GPIOB30	14	DGND
15	GPIOB31	16	GPIOC14/PWM2
17	SYS_3.3V	18	GPIOB27
19	SPI0_MOSI/GPIOC31	20	DGND
21	SPI0_MISO/GPIOD0	22	UART4_RX/GPIOB28
23	SPI0_CLK/GPIOC29	24	SPI0_CS/GPIOC30
25	DGND	26	GPIOB26
27	I2C1_SDA	28	I2C1_SCL
29	GPIOC8	30	DGND
31	GPIOC7	32	GPIOC28
33	GPIOC13/PWM1	34	DGND
35	SPI2_MISO/GPIOC11	36	SPI2_CS/GPIOC10
37	AliveGPIO3	38	SPI2_MOSI/GPIOC12
39	DGND	40	SPI2_CLK/GPIOC9

The M3's GPIO pin spec is slightly different from the NanoPi 2's. Here is a comparison table:40 pins GPIO comparison table

• Debug Port（UART0）

Pin#	Name
1	DGND
2	VDD_5V
3	UART_TXD0
4	UART_RXD0

• DVP Camera Interface Pin Spec

Pin#	Name
1, 2	SYS_3.3V
7,9,13,15,24	DGND
3	I2C0_SCL
4	I2C0_SDA
5	GPIOB14
6	GPIOB16
8,10	NC
11	VSYNC
12	HREF
14	PCLK
16-23	Data bit7-0

• RGB LCD Interface Pin Spec

Pin#	Name	Description
1, 2	VDD_5V	5V Output, it can be used to power LCD modules
11，20，29, 37，38，39，40, 45	DGND	Ground
3-10	Blue LSB to MSB	RGB blue
12-19	Green LSB to MSB	RGB green
21-28	Red LSB to MSB	RGB red
30	GPIOB25	available for users
31	GPIOC15	occupied by FriendlyARM one wire technology to recognize LCD models and control backlight and implement resistive touch, not applicable for users.
32	XnRSTOUT Form CPU	low when system is reset
33	VDEN	signal the external LCD that data is valid on the data bus
34	VSYNC	vertical synchronization
35	HSYNC	horizontal synchronization
36	LCDCLK	LCD clock, Pixel frequency
41	I2C2_SCL	I2C2 clock signal, for capacitive touch data transmission
42	I2C2_SDA	I2C2 data signal, for capacitive touch data transmission
43	GPIOC16	interrupt pin for capacitive touch, used with I2C2
44	NC	Not connected

Notes

1. SYS_3.3V: 3.3V power output
2. VDD_5V: 5V power input/output. The input range is 4.7V ~ 5.6V
3. All pins are 3.3V, output current is 5mA
4. For more details refer to the document: NanoPi-M2A-M3-1604-Schematic.pdf

3.2 Board Dimension

For more details refer to the document:PCB dxf file

4 Get Started

4.1 Essentials You Need

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

• NanoPi M3
• SD Card: Class 10 or Above, minimum 8GB SDHC
• A DC 5V/2A power is a must
• HDMI monitor or LCD
• USB keyboard, mouse and possible a USB hub(or a TTL to serial board)
• A host computer running Ubuntu 14.04 64 bit system

4.2 Make an Installation SD Card

4.2.1 Boot NanoPi M3 from SD Card

Get the following files from the download link to download necessary files:

• Get a 4G SDHC card and backup its data if necessary.
  

For LCD or HDMI output use the following files:
s5p6818-debian-sd4g-20160426.img	Debian image files
s5p6818-android-sd4g-20160426.img	Android image files
s5p6818-core-qte-sd4g-20160426.img	Ubuntu Core + QT image files
Flash Utility:
win32diskimager.rar	Windows utility. Under Linux users can use "dd"

• Uncompress these files. Insert an SD card(at least 4G) into a Windows PC and run the win32diskimager utility as administrator. On the utility's main window select your SD card's drive, the wanted image file and click on "write" to start flashing the SD card.
• Insert this card into your NanoPi M3's boot slot, press and hold the boot key and power on (with a 5V/2A power source). If the PWR LED is on and LED1 is blinking and LED2 is off this indicates your NanoPC-T3 has successfully booted.
  

4.2.2 Under Linux Desktop

• 1) Insert your microSD card into your host running Ubuntu and check your SD card's device name

dmesg | tail

Search the messages output by "dmesg" for similar words like "sdc: sdc1 sdc2". If you can find them it means your SD card is recognized as "/dev/sdc". Or you can check that by commanding "cat /proc/partitions"

• 2) Download Flashing Script

git clone https://github.com/friendlyarm/sd-fuse_nanopi3.git
cd sd-fuse_nanopi3

• 3) Flash Android Firmware to MicroSD Card

su
./fusing.sh /dev/sdx

(Note: you need to replace "/dev/sdx" with the device name in your system)
When you do “git clone” you have to hit “Y” within 10 seconds after it prompts you to download image files otherwise you will miss the download.

• 4) Flash Debian Firmware to MicroSD Card

./fusing.sh /dev/sdx debian

4.2.3 LCD/HDMI Resolution

When the system boots our uboot will check whether it is connected to an LCD or to an HDMI monitor. If it recognizes an LCD it will configure its resolution. Our uboot defaults to the HDMI 720P configuration.
If you want to modify the LCD resolution you can modify file "arch/arm/plat-s5p6818/nanopi3/lcds.c" in the kernel and recompile it.
If your NanoPi M3 is connected an HDMI monitor and it runs Android it will automatically set the resolution to an appropriate HDMI mode by checking the "EDID". If your NanoPi M3 is connected an HDMI monitor and it runs Debian by default it will set the resolution to HDMI 720P. If you want to modify the resolution to 1080P modify your kernel's configuration as explained above.

4.3 Update Image Files in MicroSD Card From PC Host

If you want to make some changes to the image files in your MicroSD card follow steps below otherwise you can skip this section.
Insert your MicroSD card into a PC host running Linux, mount the boot and rootfs sections of the SD card and follow the steps below:
1) If you want to change your kernel command line parameters you can do it via the fw_setevn utility under "sd-fuse_nanopi3/tools".
Check the current Command Line

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

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

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

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

2) Update Kernel
Our customized uboot will check the LCD type when it boots.
For Android it doesn't make any difference which display device is detected. You can use your generated uImage to replace the existing one under "boot".
For Debian if your generated kernel is for an LCD you need to replace the existing uImage or if your kernel is for HDMI you need to replace the existing uImage.hdmi.

4.4 Run Android or Debian

• Insert a MicroSD card with Android/Debian image files into your NanoPi M3, connect the NanoPi M3 to an HDMI monitor and a 5V/2A power source the NanoPi M3 will be automatically powered up. If you can see the PWR LED is on and LED1 is flashing it means your board is working and you will see Android/Debain loading on the HDMI monitor.
  

1) If you connect the NanoPi M3 to an HDMI monitor you need to use a USB mouse and a USB keyboard to operate. If you connect it to an LCD with capacitive touch you can operate directly on the LCD.
2) If you want to do kernel development you need to use a serial communication board, ie a PSU-ONECOM board, which will allow you to operate the board via a serial terminal.

• Here is a setup where we connect a NanoPi M3 to a PC running Ubuntu and Minicom via a serial cable you will see system messages output to the PC’s minicom terminal:

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

4.5 Login Debian via VNC or SSH

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

You can login via "SSH -l root 192.168.8.1" the default password for "root" is "fa".

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

iwconfig wlan0 power off

5 Working with Debian

5.1 Ethernet Connection

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

5.2 Wireless Connection

Open the file "/etc/wpa_supplicant/wpa_supplicant.conf" with vi or gedit and append the following lines:

network={
        ssid="YourWiFiESSID"
        psk="YourWiFiPassword"
}

The "YourWiFiESSID" and "YourWiFiPassword" need to be replaced with your actual ESSID and password.
Save, exit and run the following commands your board will be connected to your specified WiFi.

ifdown wlan0
ifup wlan0

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

wpa_passphrase YourWiFiESSID

Following the prompt type in your password. If you open the file "/etc/wpa_supplicant/wpa_supplicant.conf" you will find that your password has been updated and you can delete your clear-text password.

If the system's WiFi AP mode is on it cannot search and connect to a wireless router. You need to turn off the WiFi AP mode by following the instructions below:

su
turn-wifi-into-apmode no

5.3 Setup Wi-Fi AP

You can follow the steps below to setup WiFi AP:

turn-wifi-into-apmode yes

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

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

ssh root@192.168.8.1

The password for it is "fa".

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

iwconfig wlan0 power off

You can check the WiFi mode via the following command:

cat /sys/module/bcmdhd/parameters/op_mode

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

turn-wifi-into-apmode no

5.4 Bluetooth

Click on the bluetooth icon on the GUI a menu will pop up:
Make discoverable... enables the NanoPC-T3 to be searched for by nearby bluetooth devices;
Devices... opens a search window and searches for nearby bluetooth devices(Note: the "Make discoverable" property needs to be enabled on those nearby devices as well);
Send Files to Device...enables the NanoPC-T3 to send files to another bluetooth device which is paired to the NanoPi M3;

5.5 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 如何编译系统

6.1 安装交叉编译器

首先下载并解压编译器:

git clone https://github.com/friendlyarm/prebuilts.git
sudo mkdir -p /opt/FriendlyARM/toolchain
sudo tar xf prebuilts/gcc-x64/arm-cortexa9-linux-gnueabihf-4.9.3.tar.xz -C /opt/FriendlyARM/toolchain/

然后将编译器的路径加入到PATH中，用vi编辑vi ~/.bashrc，在末尾加入以下内容：

export PATH=/opt/FriendlyARM/toolchain/4.9.3/bin:$PATH
export GCC_COLORS=auto

执行一下~/.bashrc脚本让设置立即在当前shell窗口中生效，注意"."后面有个空格：

. ~/.bashrc

这个编译器是64位的，不能在32位的Linux系统上运行，安装完成后，你可以快速的验证是否安装成功：

arm-linux-gcc -v
Using built-in specs.
COLLECT_GCC=arm-linux-gcc
COLLECT_LTO_WRAPPER=/opt/FriendlyARM/toolchain/4.9.3/libexec/gcc/arm-cortexa9-linux-gnueabihf/4.9.3/lto-wrapper
Target: arm-cortexa9-linux-gnueabihf
Configured with: /work/toolchain/build/src/gcc-4.9.3/configure --build=x86_64-build_pc-linux-gnu
--host=x86_64-build_pc-linux-gnu --target=arm-cortexa9-linux-gnueabihf --prefix=/opt/FriendlyARM/toolchain/4.9.3
--with-sysroot=/opt/FriendlyARM/toolchain/4.9.3/arm-cortexa9-linux-gnueabihf/sys-root --enable-languages=c,c++
--with-arch=armv7-a --with-tune=cortex-a9 --with-fpu=vfpv3 --with-float=hard
...
Thread model: posix
gcc version 4.9.3 (ctng-1.21.0-229g-FA)

6.2 编译U-Boot

下载U-Boot源代码并编译，注意分支是nanopi2-lollipop-mr1:

git clone https://github.com/friendlyarm/uboot_nanopi2.git
cd uboot_nanopi2
git checkout nanopi2-lollipop-mr1
make s5p6818_nanopi3_config
make CROSS_COMPILE=arm-linux-

编译成功结束后您将获得u-boot.bin，您可以通过fastboot来更新正在运行的NanoPC M3板上SD的U-Boot，方法如下：
1) 在电脑上先用命令 sudo apt-get install android-tools-fastboot 安装 fastboot 工具;
2) 用串口配件连接NanoPC M3和电脑，在上电启动的2秒内，在串口终端上按下回车，进入 u-boot 的命令行模式；
3) 在u-boot 命令行模式下输入命令 fastboot 回车，进入 fastboot 模式；
4) 用microUSB线连接NanoPC M3和电脑，在电脑上输入以下命令烧写u-boot.bin:

fastboot flash bootloader u-boot.bin

注意：您不能直接使用dd来更新SD卡，否则有可能会导致无法正常启动。

6.3 准备mkimage

编译内核需要用到U-Boot中的工具mkimage，因此，在编译内核uImage前，您需要保证您的主机环境可以成功运行它。
你可以直接使用命令 sudo apt-get install u-boot-tools 来安装，也可以自己编译并安装：

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

6.4 编译Linux kernel

6.4.1 编译内核

• 下载内核源代码

git clone https://github.com/friendlyarm/linux-3.4.y.git
cd linux-3.4.y
git checkout nanopi2-lollipop-mr1

NanoPC-T2内核所属的分支是nanopi2-lollipop-mr1，在开始编译前先切换分支。

• 编译Android内核

make nanopi3_android_defconfig
touch .scmversion
make uImage

• 编译Debian内核

make nanopi3_linux_defconfig
touch .scmversion
make uImage

编译成功结束后，新生成的内核烧写文件为 arch/arm/boot/uImage，此内核支持HDMI 720p输出，用于替换掉SD卡boot分区下的uImage.hdmi。
如果要支持HDMI 1080p，则需要修改内核配置：

touch .scmversion
make nanopi3_linux_defconfig
make menuconfig
  Device Drivers -->
    Graphics support -->
      Nexell Graphics -->
        [ ] LCD
        [*] HDMI
        (0)   Display In  [0=Display 0, 1=Display 1]
              Resolution (1920 * 1080p)  --->
make uImage

启用LCD，同时取消HDMI，然后退出并保存配置，编译后即可获得支持LCD显示的uImage，用于替换SD卡boot分区下的uImage。

6.4.2 如何使用新编译的内核

• 更新SD卡上的内核

如果您是使用SD卡启动Android，则在PC上复制为Android编译的uImage到SD卡的boot分区(即分区1，设备是/dev/sdX1)即可。
如果您是使用SD卡启动Debian系统，则需要编译好用于HDMI的uImage后替换SD卡boot分区下的uImage.hdmi，然后编译用于LCD的uImage并替换SD卡boot分区下的uImage。

• 更新eMMC上Android的内核

如果只想单独更新eMMC上的内核来测试，则需要先正常启动板，然后mount eMMC的boot分区，使用新编译的uImage来替换原有文件，完成后reboot即可。
从eMMC启动时可通过以下方法来更新内核：
1) 启动完成后，需要手动mount eMMC的boot分区(设备是/dev/mmcblk0p1), 可通过串口在板上操作:

su
mount -t ext4 /dev/block/mmcblk0p1 /mnt/media_rw/sdcard1/

2) 连接USB，在PC端Ubuntu下使用adb push命令复制新编译的uImage到已mount的boot分区下;

adb push uImage /mnt/media_rw/sdcard1/

3) 也可以将编译好的内核复制到SD卡或U盘，然后在板上复制到boot分区下；
4) 更新完成后，输入 reboot 命令重启即可，注意不要直接断电或按Reset键，否则可能会损坏文件。

• 更新eMMC上Debian的内核

从eMMC启动时可通过以下方法来更新内核：
1) 启动完成后，系统通常会自动mount eMMC的boot分区(设备是/dev/mmcblk0p1), 可输入命令mount来查看;
2) 连接网络，使用scp/ftp等方式复制新编译的uImage并替换boot分区下的文件，如果是用于HDMI的内核，则替换uImage.hdmi;
3) 也可以将编译好的内核复制到SD卡或U盘，然后在板止复制到boot分区下;
4) 更新完成后，输入 reboot 命令重启即可，注意不要直接断电或按Reset键，否则可能会损坏文件.

• 使用新的内核来生成boot.img

如果要生成直接烧写eMMC的文件，则需要使用新编译的内核来生成boot.img，然后复制到烧写用的SD卡即可直接烧写到eMMC.
对于Android，将新的uImage复制Android源码的device/friendly-arm/nanopi3/boot/ 下，然后编译Android即可获得新的boot.img .
对于Debian, 则需要使用按以下方法来生成boot.img :
1) 下载debian_nanopi2

git clone https://github.com/friendlyarm/debian_nanopi2.git

2) 复制用于HDMI的uImage到debian_nanopi2/boot/uImage.hdmi, 复制用于LCD的 uImage到debian_nanopi2/boot/uImage ;
3) 生成Debian的 boot.img

cd debian_nanopi2
mkdir rootfs
./build.sh

新的 boot.img 在 debian_nanopi2/sd-fuse_nanopi2/debian 下.
其中命令"mkdir rootfs"只是创建一个空的目录使得build.sh可以运行，因此生成的其它文件比如rootfs.img不能使用。

6.4.3 编译内核模块

Android包含内核模块，位于system分区的 /lib/modules/ 下，如果您有新的内核模块或者内核配置有变化，则需要重新编译。
首先编译内核源代码中的模块：

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

另外有2个内核模块的源代码位于Android源代码中，可使用以下命令来编译：

cd /opt/FriendlyARM/s5p6818/android
./vendor/friendly-arm/build/common/build-modules.sh

其中 “/opt/FriendlyARM/s5p6818/android” 是指Android源代码的TOP目录，使用参数“-h”可查看帮助。
编译成功结束后，会显示生成的内核模块。

6.5 编译Android

• 搭建编译环境

搭建编译Android的环境建议使用64位的Ubuntu 14.04，安装需要的包即可。

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

更多说明可查看 https://source.android.com/source/initializing.html 。

• 下载源代码

Android源代码的下载需要使用repo，其安装和使用请查看 https://source.android.com/source/downloading.html 。

mkdir android && cd android
repo init -u https://github.com/friendlyarm/android_manifest.git -b nanopi3-lollipop-mr1
repo sync

其中“android”是指工作目录。

• 编译系统

source build/envsetup.sh
lunch aosp_nanopi3-userdebug
make -j8

编译成功完成后，目录 out/target/product/nanopi3/ 下包含可用于烧写的image文件。

filename	partition	Description
boot.img	boot	-
cache.img	cache	-
userdata.img	userdata	-
system.img	system	-
partmap.txt	-	分区描述文件

• 烧写到SD卡

如果是采用SD卡启动Android，可复制编译生成的image文件到sd-fuse_nanopi3/android/ 下，使用脚本即可烧到到SD卡，具体请查看#在Linux Desktop下通过脚本制作。

• 烧写到eMMC

成功编译Android后，可过2种方式烧写到eMMC，分别如下：
1) fastboot: 板子从eMMC启动后通过串口快速按任意键进入uboot命令行模式，输入命令fastboot即可启动此方式。
连接USB线，然后PC端输入以下命令:

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

2) 使用SD卡烧写
复制out/target/product/nanopi3下的boot.img, cache.img, userdata.img, system.img, partmap.txt到烧写用SD卡的images/android下，再次烧写即可。

7 源代码和固件下载链接

• 烧写固件下载链接：[2]
• 源代码下载链接：[3]

8 资源链接

• CPU(SOC)数据手册: S5P6818 Datasheet
• 原理图: NanoPi-M2A-M3-1604-Schematic.pdf
• PCB详细尺寸: PCB DXF文件