Google Chat: zj734465502@gmail.com
+86-0755-88291180
sales01@spotpear.com
dragon_manager@163.com
services01@spotpear.com
manager01@spotpear.com
WhatsApp:13246739196
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 |
Pin# | Name | Description |
1 | VDD_5V | 5V Power Out |
2 | USB-DP2 | USB2 DP Signal |
3 | USB-DM2 | USB2 DM Signal |
4 | USB-DP3 | USB3 DP Signal |
5 | USB-DM3 | USB3 DM Signal |
6 | GPIOL11/IR-RX | GPIOL11 or IR Receive |
7 | SPDIF-OUT/GPIOA17 | GPIOA17 or SPDIF-OUT |
8 | PCM0_SYNC/I2S0_LRC | I2S/PCM Sample Rate Clock/Sync |
9 | PCM0_CLK/I2S0_BCK | I2S/PCM Sample Rate Clock |
10 | PCM0_DOUT/I2S0_SDOUT | I2S/PCM Serial Bata Output |
11 | PCM0_DIN/I2S0_SDIN | I2S/PCM Serial Data Input |
12 | GND | 0V |
Pin# | Name |
1 | GND |
2 | VDD_5V |
3 | UART_TXD0/GPIOA4 |
4 | UART_RXD0/GPIOA5/PWM0 |
Pin# | Name | Description |
1 | LL | LINEOUTL, LINE-OUT Left Channel Output |
2 | LR | LINEOUTR, LINE-OUT Right Channel Output |
3 | MICN | MICIN1N, Microphone Negative Input |
4 | MICP | MICIN1P, Microphone Positive Input |
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 |
Before starting to use your NanoPi NEO AIR get the following items ready
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:
Image Files: | |
nanopi-neo-air_sd_friendlycore-xenial_3.4_armhf_YYYYMMDD.img.zip | Base on UbuntuCore, kernel:Linux-3.4 |
nanopi-neo-air_sd_friendlycore-xenial_4.14_armhf_YYYYMMDD.img.zip | Base on UbuntuCore, kernel:Linux-4.14 |
nanopi-neo-air_sd_friendlywrt_4.14_armhf_YYYYMMDD.img.zip | Base on OpenWrt, kernel:Linux-4.14 |
nanopi-neo-air_eflasher_friendlycore-xenial_4.14_armhf_YYYYMMDD.img.zip | eflasher image, for flashing FriendlyCore(Linux-4.14) to eMMC |
nanopi-neo-air_eflasher_openwrt_4.14_armhf_YYYYMMDD.img.zip | eflasher image, for flashing OpenWrt(Linux-4.14) to eMMC |
Flash Utility: | |
win32diskimager.rar | Windows utility. Under Linux users can use "dd" |
After it is installed you will see the following window:
$ su root
$ eflasher
The password for "root" is "fa".
We take "nanopi-neo-air_eflasher_friendlycore-xenial_4.14_armhf_YYYYMMDD.img" as an example. After you run the "eflasher" command you will see the following messages:
Type "1", select writing friendlycore system to eMMC you will see the following messages:
Type "yes" to start installation:
After it is done power off the system, take off the TF card, power on again your system will be booted from eMMC.
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:
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:
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:
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.
$ sudo apt-get update
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:
Please refer to: How to Build and Install Qt Application for FriendlyELEC Boards
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.
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
Take the example of transferring files to the mobile phone. First, set your mobile phone Bluetooth to detectable status, then execute the following command to start Bluetooth search.:
hcitool scan
Search results look like:
Scanning ... 2C:8A:72:1D:46:02 HTC6525LVW
This means that a mobile phone named HTC6525LVW is searched. We write down the MAC address in front of the phone name, and then use the sdptool command to view the Bluetooth service supported by the phone:
sdptool browser 2C:8A:72:1D:46:02
Note: Please replace the MAC address in the above command with the actual Bluetooth MAC address of the mobile phone.
This command will detail the protocols supported by Bluetooth for mobile phones. What we need to care about is a file transfer service called OBEX Object Push. Take the HTC6525LVW mobile phone as an example. The results are as follows:
Service Name: OBEX Object Push Service RecHandle: 0x1000b Service Class ID List: "OBEX Object Push" (0x1105) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 12 "OBEX" (0x0008) Profile Descriptor List: "OBEX Object Push" (0x1105) Version: 0x0100
As can be seen from the above information, the channel used by the OBEX Object Push service of this mobile phone is 12, we need to pass it to the obexftp command, and finally the command to initiate the file transfer request is as follows:
obexftp --nopath --noconn --uuid none --bluetooth -b 2C:8A:72:1D:46:02 -B 12 -put example.jpg
Note: Please replace the MAC address, channel and file name in the above command with the actual one.
After executing the above commands, please pay attention to the screen of the mobile phone. The mobile phone will pop up a prompt for pairing and receiving files. After confirming, the file transfer will start.
Bluetooth FAQ:
1) Bluetooth device not found on the development board, try to open Bluetooth with the following command:
rfkill unblock 0
2) Prompt can not find the relevant command, you can try to install related software with the following command:
apt-get install bluetooth bluez obexftp openobex-apps python-gobject ussp-push
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:
$ su root
$ 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.
$ nmcli r wifi on
$ nmcli dev wifi
$ 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.
Run the following command to enter AP mode:
$ su root $ turn-wifi-into-apmode yes
You will be prompted to type your WiFi hotspot's name and password and then proceed with default prompts.
After this is done you will be able to find this hotspot in a neadby cell phone or PC. You can login to this board at 192.168.8.1:
$ ssh root@192.168.8.1
When asked to type a password you can type "fa".
To speed up your ssh login you can turn off your wifi by running the following command:
$ iwconfig wlan0 power off
To switch back to Station mode run the following command:
$ turn-wifi-into-apmode no
Search for surrounding bluetooth devices by running the following command:
$ su root
$ hciconfig hci0 up
$ hcitool scan
You can run "hciconfig" to check bluetooth's status.
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。
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
For exampe, change to Shanghai timezone:
sudo rm /etc/localtime sudo ln -ls /usr/share/zoneinfo/Asia/Shanghai /etc/localtime
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.
$ apt-get update $ apt-get install libasound2 $ apt-get install alsa-base $ apt-get install alsa-utils
$ 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。
For NanoPi-NEO-Air 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:
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.
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:
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
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).
Run the following command
$ sudo /opt/QtE-Demo/run.sh
Here is what you expect to observe. This is an open source Qt Demo
Run the following commands:
sudo apt-get update sudo apt-get install docker.io
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
The NanoPi NEO Air have an audio interface (2.54mm pin header) whose pin spec is as follows:
Pin# | Name | Description |
1 | LL | LINE-OUT Left Channel Output |
2 | LR | LINE-OUT Right Channel Output |
3 | MN | Microphone Negative Input |
4 | MP | Microphone Positive Input |
Here is a hardware setup:
Earphone
Make sure your board is connected to an audio device before proceed with the following steps
List audio devices:
$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0
Both Allwinner H5 and H3 have an internal codec device which is recognized as an [H3 Audio Codec] card device in the kernel.
Play video:
$ aplay /root/Music/test.wav -D plughw:0
Parameter -D plughw:0 means device "card 0" is in use. Make sure you use a correctly recognized card device.
Record video:
$ arecord -f cd -d 5 test.wav
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
The default user is root without a password. You can click on "Login" to sign in.
1) After you load the LuCI Web page, click on Network ---> Wireless and open the configuration page:
2) Click on "Scan" to search surrounding hotspots:
3) Click on "Join network":
4) Fill your password in the "WPA passphrase" field and click on "Save & Apply":
Your board will switch from AP mode to STA mode, "OpenWrt-10:d0:7a:de:3d:92" will be removed” and the page will be disconnected. In 30 seconds you can check if your board's wlan0 will be assigned an IP.
Here is a hardware setup:
Connect the following serial communication board to your board and power on the whole system from the serial board's DC or MicroUSB port:
By default you will login as root without a password. You can set your password by commanding "passwd".
When your board loads OS for the first time the TF card's rootfs system in your board will be automatically partitioned to its max capacity:
Be patient for this process to be done.
Make sure you connect your board to the internet following the steps in <Configure WiFi> and your board's wlan0 IP address is 192.168.1.163. Run the following commands to login via SSH:
$ ssh root@192.168.1.163
By default you will login as root without a password.
OpenWrt supports web login via the LuCI Web GUI. Configure your system following the steps in <Login via SSH>. In our test the board's wlan0 IP address was 192.168.1.163. Type your IP address in a browser and you will be able to load the OpenWrt-LuCI page:
If your board is connected to the internet and your board's wlan0 is assigned an IP address, after you type the IP address in a browser you will be able to load the OpenWrt-LuCI page:
By default you will login as root without a password. After click on "Login" you will sign in.
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.
Before you install a package you'd better update the package list:
$ opkg update
$ opkg list
At the time of writing there are 3241 packages available.
$ opkg list-installed
At the time of writing 124 packages have been installed.
$ opkg install <pkgs> $ opkg remove <pkgs>
$ opkg files <pkg>
$ opkg install luci-i18n-base-zh-cn
$ opkg list-changed-conffiles
$ cpu_freq CPU0 online=1 temp=26581 governor=ondemand cur_freq=480000 CPU1 online=1 temp=26581 governor=ondemand cur_freq=480000 CPU2 online=1 temp=26581 governor=ondemand cur_freq=480000 CPU3 online=1 temp=26581 governor=ondemand cur_freq=480000
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。
After you load the OpenWrt-LuCI page, click on "Statistics ---> Graphs" and you will be able to check all the statistics:
1) System Load:
2) RAM:
3) CPU Temperature:
"Statistics" is collected by the luci-app-statistics package. The luci-app-statistics package uses the Collectd utility to collect statistics and presents them using the RRDtool utility.
If you want to get more statistics you can install various collectd-mod-* packages. All collectd-mod-* packages use the same configuration file: /etc/config/luci_statistics.
The NanoPi NEO Air has gotten support for kernel Linux-4.14. For more details about how to use mainline U-boot and Linux-4.14 refer to :Building U-boot and Linux for H5/H3/H2+
Visit this link download link and enter the "sources/nanopi-H3-bsp" directory and download all the source code.Use the 7-zip utility to extract it and a lihee directory and an Android directory will be generated. You can check that by running the following command:
$ ls ./ android lichee
Or you can get it from our github:
$ git clone https://github.com/friendlyarm/h3_lichee.git lichee
Note: "lichee" is the project name named by Allwinner for its CPU's source code which contains the source code of U-boot, Linux kernel and various scripts.
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.
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 u-boot-tools
Enter the lichee directory and un the following command to compile the whole package:
$ cd lichee/fa_tools $ ./build.sh -b nanopi-air -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 the build.sh script runs it will automatically call this cross-compiler.
Type the following command to update the U-boot on your TF 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.
The boot.img and kernel modules are under the "linux-3.4/output" directory. You can copy the new boot.img file to your TF card's boot partition.
You can compile u-boot individually by using the following command:
$ cd lichee/fa_tools/ $ ./build.sh -b nanopi-air -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 your TF 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.
If you want to compile the Linux kernel run the following command:
$ cd lichee/fa_tools/ $ ./build.sh -b nanopi-air -p linux -t kernel
After the compilation is done a uImage and its kernel modules will be generated under "linux-3.4/output".
$ cd lichee/fa_tools/ $ ./build.sh -b nanopi-air -p linux -t clean
The following commands need to be executed on the development board:
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
sudo apt-get update sudo apt-get install dpkg-dev libarchive-tools
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)
sudo dpkg -i ../linux-headers-4.14.111_4.14.111-1_armhf.deb
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
[http:// NanoPi NEO Air V1.1 3D printing files]
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:
The following BakeBit modules can work with BakeBit - NanoHat Hub: