android运行iwconfig命令,NanoPC-T3

最新推荐文章于 2022-10-11 13:09:48 发布

浩泽天

最新推荐文章于 2022-10-11 13:09:48 发布

阅读量781

点赞数

文章标签： android运行iwconfig命令

Overview

Front

Back

The NanoPC-T3 octa-core single board computer is designed and developed by FriendlyARM for professional and enterprise users. It uses the Samsung Octa-Core Cortex-A53 S5P6818 SoC. Compared to the FriendlyARM NanoPC-T2 the NanoPC-T3 not only has all the T2’s interfaces and ports but also has a more powerful SoC. Its dynamic frequency scales from 400M up to 1.4GHz. The NanoPC-T3 has 8G eMMC onboard, audio jack, video input/output interfaces, built-in WiFi, Bluetooth and Gbps Ethernet port. In addition the NanoPC-T3 has power management, on board porcelain antenna and serial debug port. To avoid overheat issues the NanoPC-T3 has a heat sink with mounting holes.

The NanoPC-T3 has two camera interfaces: a DVP camera interface and a MIPI-CSI interface, and four video interfaces: HDMI 1.4A, LVDS, parallel RGB-LCD interface and MIPI-DSI interface. It supports RTC and has RTC interface pins. It has four USB ports with two being type A ports and two being 2.54mm pitch pin-headers.

The NanoPC-T3 supports muitple OS systems e.g. Android5.1, Debian and UbuntoCore+Qt. It is an open source project with rich interfaces and ports. It is born a choice for professional and enterprise users.

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/2GB 32bit DDR3 RAM

Storage: 1 x SD Card Socket

Ethernet: Gbit Ethernet(RTL8211E)

WiFi: 802.11b/g/n

Bluetooth: 4.0 dual mode

Antenna: Porcelain Antenna IPX Interface

eMMC: 8GB

Video Input: DVP Camera/MIPI-CSI (two camera interfaces)

Video Output: HDMI Type-A / LVDS / Parallel RGB-LCD / MIPI-DSI (four video output interfaces)

Audio: 3.5 mm audio jack / via HDMI

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

DVP Camera: 0.5mm pitch 24 pin FPC seat

GPIO: 2.54 mm pitch 30 pin-header

Serial Debug Port: 2.54mm pitch 4-pin-header

User Key: K1 (power), Reset

LED: 1 x power LED and 2 x GPIO LED

Other Resources: CPU’s internal TMU

RTC Battery: RTC Battery Seat

Heat Sink: 1 x Heat Sink with mounting holes

Power: DC 5V/2A

PCB: Six Layer

Dimension: 100 mm x 60 mm

Working Temperature: -40℃ to 80℃

OS/Software: uboot, Android and Debian

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

welcome window with basic system information and status

auto-login with user account "pi" with access to npi-config

UART2 enabled

supports CAM500B

supports setting up static IP

supports accessing hardware with FriendlyElec's libfriendlyarm-things.so

integrated iTest utility for testing hardware

NanoPC-T3 Layout

30Pin GPIO Pin Spec

Pin#

Name

Pin#

Name

SYS_3.3V

DGND

UART2_TX/GPIOD20

UART2_RX/GPIOD16

I2C0_SCL

I2C0_SDA

SPI0_MOSI/GPIOC31

SPI0_MISO/GPIOD0

SPI0_CLK/GPIOC29

SPI0_CS/GPIOC30

UART3_TX/GPIOD21

UART3_RX/GPIOD17

UART4_TX/GPIOB29

UART4_RX/GPIOB28

UART5_TX/GPIOB31

UART5_RX/GPIOB30

GPIOC4

GPIOC7

GPIOC8

GPIOC24

GPIOC28

GPIOB26

GPIOD1/PWM0

GPIOD8/PPM

GPIOC13/PWM1

AliveGPIO3

GPIOC14/PWM2

AliveGPIO5

VDD_5V

DGND

20Pin LVDS Interface Pin Spec

Pin#

Name

Pin#

Name

SYS_3.3V

GPIOC16

GPIOB18

DGND

LVDS_D0-

LVDS_D0+

LVDS_D1-

LVDS_D1+

LVDS_D2-

LVDS_D2+

DGND

LVDS_CLK-

LVDS_CLK+

LVDS_D3-

LVDS_D3+

I2C2_SCL

I2C2_SDA

DVP Camera Interface Pin Spec

Pin#

Name

1, 2

SYS_3.3V

7,9,13,15,24

DGND

I2C0_SCL

I2C0_SDA

GPIOB14

GPIOB16

8,10

VSYNC

HREF

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

GPIOB25

available for users

GPIOC15

occupied by FriendlyARM one wire technology to recognize LCD models and control backlight and implement resistive touch, not applicable for users

XnRSTOUT Form CPU

low when system is reset

VDEN

signal the external LCD that data is valid on the data bus

VSYNC

vertical synchronization

HSYNC

horizontal synchronization

LCDCLK

LCD clock, Pixel frequency

I2C2_SCL

I2C2 clock signal, for capacitive touch data transmission

I2C2_SDA

I2C2 data signal, for capacitive touch data transmission

GPIOC16

interrupt pin for capacitive touch, used with I2C2

Not connected

MIPI-DSI Interface Pin Spec

Pin#

Name

1, 2, 3

VDD_5V

DGND

I2C2_SDA

I2C2_SCL

DGND

GPIOC0

DGND

GPIOC1

DGND

GPIOA28

nRESETOUT

14, 15

DGND

MIPIDSI_DN3

MIPIDSI_DP3

DGND

MIPIDSI_DN2

MIPIDSI_DP2

DGND

MIPIDSI_DN1

MIPIDSI_DP1

DGND

MIPIDSI_DN0

MIPIDSI_DP0

DGND

MIPIDSI_DNCLK

MIPIDSI_DPCLK

DGND

MIPI-CSI Interface Pin Spec

Pin#

Name

1, 2

SYS_3.3V

DGND

I2C0_SDA

I2C0_SCL

DGND

SPI2_MOSI/GPIOC12

SPI2_MISO/GPIOC11

SPI2_CS/GPIOC10

SPI2_CLK/GPIOC9

DGND

GPIOB9

GPIOC2

14, 15

DGND

MIPICSI_DN3

MIPICSI_DP3

DGND

MIPICSI_DN2

MIPICSI_DP2

DGND

MIPICSI_DN1

MIPICSI_DP1

DGND

MIPICSI_DN0

MIPICSI_DP0

DGND

MIPICSI_DNCLK

MIPICSI_DPCLK

DGND

Notes

SYS_3.3V: 3.3V power output

VDD_5V: 5V power output

For more details refer to the document: NanoPC-T2-T3-1711-Schematic.pdf

For more details refer to the document: NanoPC-T3-Dimensions(dxf)

Power Jack

DC 4.7~5.6V IN, 4.0*1.7mm Power Jack

The board has an EEPROM(model: 24AA025E48T-I/OT) with a unique MAC. This EEPROM is connected to I2C0 and its address is 0x51 therefore some EEPROM chips cannot be connected to I2C0 which will cause conflicts of addresses.

In our tests these EEPROM chips cannot be connected to I2C0: 24C04, 24C08 and 24C16. There chips which we tested can be connected to I2C0: 24C01, 24C02 and 24C256

Before starting to use your NanoPC-T3 get the following items ready

NanoPC-T3

SD Card: Class 10 or Above

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 16.04 64 bit system

Get the following files from here download link:

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

Image Files

s5p6818-sd-friendlycore-xenial-4.4-armhf-YYYYMMDD.img.zip

FriendlyCore(32bit) with Qt 5.10.0 (base on Ubuntu core) image file

s5p6818-sd-friendlycore-xenial-4.4-arm64-YYYYMMDD.img.zip

FriendlyCore(64bit) with Qt 5.10.0 (base on Ubuntu core) image file

s5p6818-sd-lubuntu-desktop-xenial-4.4-armhf-YYYYMMDD.img.zip

LUbuntu Desktop image file with X Window

s5p6818-sd-friendlywrt-4.4-YYYYMMDD.img.zip

FriendlyWrt image file (base on OpenWrt)

s5p6818-sd-android7-YYYYMMDD.img.zip

Android7 image file

s5p6818-sd-android-lollipop-YYYYMMDD.img.zip

Android5.1 image file

s5p6818-eflasher-lubuntu-desktop-xenial-4.4-armhf-YYYYMMDD.img.zip

SD card image, which is used to install a lubuntu desktop to eMMC

s5p6818-eflasher-friendlywrt-4.4-YYYYMMDD.img.zip

SD card image, which is used to install a FriendlyWrt to eMMC

s5p6818-eflasher-android7-YYYYMMDD.img.zip

SD card image, which is used to install a android7 to eMMC

s5p6818-eflasher-android-lollipop-YYYYMMDD.img.zip

SD card image, which is used to install an Android to eMMC

s5p6818-eflasher-friendlycore-xenial-4.4-arm64-YYYYMMDD.img.zip

SD card image, which is used to install a FriendlyCore-arm64 to eMMC

s5p6818-eflasher-friendlycore-xenial-4.4-armhf-YYYYMMDD.img.zip

SD card image, which is used to install a FriendlyCore-armhf to eMMC

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 board's boot slot, press and hold the boot key (only applies to a board with onboard eMMC) and power on (with a 5V/2A power source). If the PWR LED is on and LED1 is blinking this indicates your board has successfully booted.

Download eflasher image file

An image file's name is as : s5p6818-eflasher-OSNAME-YYYYMMDD.img.zip

The "OSNAME" is the name of an OS e.g. android, friendlycore and etc;

This image file is used for making an installation SD card and it contains a Ubuntu core system and a utility EFlasher;

Download s5p6818-eflasher-OSNAME-YYYYMMDD.img.zip to a host PC and get a windows utility win32diskimager.rar as well;

Make Installation SD Card with eflasher

Extract the package with a 7z utility and you will get a file with an extension ".img". Insert an SDHC card(minimum 8G or above) to a PC running Windows, run the Win32DiskImager utility as administrator, click on "Image File" to select your wanted file, select your SD card and click on "Write" to start flashing the Image to your SD card;

If your PC runs Linux you can command "dd" to extract the package and get an ".img" file and write it to your SD card;

Operate in GUI Window: Flash OS to eMMC

Insert your SD card to NanoPC-T3, connect an HDMI monitor or LCD to your board, press and hold the "boot" key beside the Ethernet port, power on the board you will see a pop-up window asking you to select an OS for installation. Select your wanted OS and start installation.

Operate in Commandline Utility: Flash OS to eMMC

Insert an installation SD card to NanoPC-T3, log into or SSH to your board and run the following command to start EFlasher:

sudo eflasher

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

dmesg | tail

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

2) Downlaod Linux script

3) Here is how to make a Lubuntu desktop SD card

sudo ./fusing.sh /dev/sdx lubuntu

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

When you run the script for the first time it will prompt you to download an image you have to hit “Y” within 10 seconds otherwise you will miss the download

4) Run this command to make a complete image file:

sudo ./mkimage.sh lubuntu

When Debian/Ubuntu is loaded the SD card's section will be automatically extended.

When Android is loaded you need to run the following commands on your host PC to extend your SD card's section:

sudo umount /dev/sdx?

sudo parted /dev/sdx unit % resizepart 4 100 resizepart 7 100 unit MB print

sudo resize2fs -f /dev/sdx7

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

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 NanoPC-T3 is connected to an HDMI monitor and it runs Android it will automatically set the resolution to an appropriate HDMI mode by checking the "EDID". If your NanoPC-T3 is connected to an HDMI monitor and it runs Debian by default it will set the resolution to the HDMI 720P configuration. If you want to modify the HDMI resolution to 1080P modify your kernel's configuration as explained above.

Insert your SD card into a host PC running Linux, if you want to change your kernel command line parameters you can do it via the fw_setevn utility.

Check the current Command Line:

git clone https://github.com/friendlyarm/sd-fuse_s5p6818.git

cd sd-fuse_s5p6818/tools

./fw_printenv /dev/sdx | grep bootargs

For example, to disable android SELinux, You can change it this way:

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

The "XXX" stands for the original bootargs' value.

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 our FriendlyCore has the following additional features:

it supports our LCDs with both capacitive touch and resistive touch(S700, X710, HD702, S430, HD101 and S70)

it supports WiFi

it supports Ethernet

it supports Bluetooth and has been installed with bluez utilities

it supports audio playing

it supports Qt 5.10.0 EGLES and OpenGL ES1.1/2.0 (Only for S5P4418/S5P6818)

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

For example, NanoPi-M1：

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:

For example, NanoPi-NEO2：

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

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:

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

RTL8188CUS/8188EU 802.11n WLAN Adapter

RT2070 Wireless Adapter

RT2870/RT3070 Wireless Adapter

RTL8192CU Wireless Adapter

mi WiFi mt7601

5G USB WiFi RTL8821CU

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.

Follow the steps below. Since our OS image by default already has the NetworkManager utility you will be prompted to uninstall it first:

sudo turn-wifi-into-apmode yes

After you uninstall the NetworkManager reboot your board.

After your board is rebooted run the above commands again and you will be prompted to type in a WIFI's name and password. Type in your wanted name and password

If this is successful you will be able to find and connect your board to a WIFI. Login to your board at 192.168.8.1:

ssh root@192.168.8.1

Type in a password. In our system the password is "fa".

To login smoothly via SSH we recommend you turning off WIFI's power save mode by running the following commands:

sudo iwconfig wlan0 power off

You can check your WiFi's mode by running the following command:

sudo cat /sys/module/bcmdhd/parameters/op_mode

Number 2 means your WiFi is in AP mode. You can switch to the Station mode by running the following command:

sudo 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

You can set the system default audio device by following the steps below.

Use the following command to view all the sound card devices in the system (Note: different development boards will have different results):

pi@NanoPi:~$aplay -l

**** List of PLAYBACK Hardware Devices ****

card 0: nanopi2audio [nanopi2-audio], device 0: c0055000.i2s-ES8316 HiFi ES8316 HiFi-0 []

Subdevices: 1/1

Subdevice #0: subdevice #0

card 0: nanopi2audio [nanopi2-audio], device 1: c0059000.spdiftx-dit-hifi dit-hifi-1 []

Subdevices: 1/1

Subdevice #0: subdevice #0

As you can see, the following sound card devices are available on the hardware:

Sound card device

Sound card number

Description

nanopi2audio

device 0

3.5mm jack interface

nanopi2audio

device 1

HDMI

To configure the audio output to the 3.5mm jack, create or modify the configuration file /etc/asound.conf and modify it to the following:

pcm.!default {

type hw

card 0

device 0

}

ctl.!default {

type hw

card 0

}

To configure to output audio to HDMI, change the device 0 above to device 1.

FriendlyCore system built-in lightweight Xorg，although there is no window manager, you can still run a single X-Windows application，For example, the program to run is ~/YourX11App，use the following command：

. /usr/bin/setqt5env-xcb

startx ~/YourX11App -geometry 1280x800

Note that there is a space between "." and /usr/bin/setqt5env-xcb. In addition, the resolution after -geometry should be changed to the actual resolution of your screen.

Run the following command

$sudo qt5demo

Run the following command

. setqt5env

cd $QTDIR

cd /examples/opengl/qopenglwidget

./qopenglwidget

For more Qt 5.10.0 examples, please go to:

cd $QTDIR/examples/

gst-player is console player, it base on GStreamer, support VPU with Hardware-decoding:

sudo gst-player /home/pi/demo.mp4

The equivalent gsteamer command is as follows：

sudo gst-launch-1.0 filesrc location=/home/pi/demo.mp4 ! qtdemux name=demux demux. ! queue ! faad ! audioconvert ! audioresample ! alsasink device="hw:0,DEV=1" demux. ! queue ! h264parse ! nxvideodec ! nxvideosink dst-x=0 dst-y=93 dst-w=1280 dst-h=533

The CAM500B camera module is a 5M-pixel camera with DVP interface. For more tech details about it you can refer to Matrix - CAM500B.

Enter the following command to preview the video：

gst-launch-1.0 -e v4l2src device=/dev/video6 ! video/x-raw,format=I420,framerate=30/1,width=1280,height=720 ! nxvideosink

Enter the following command to start recording (VPU hardware encoding)：

gst-launch-1.0 -e v4l2src device=/dev/video6 ! video/x-raw,format=I420,framerate=30/1,width=1280,height=720 ! tee name=t t. \

! queue ! nxvideosink t. ! queue ! nxvideoenc bitrate=12000000 ! mp4mux ! \

filesink location=result_720.mp4

“PMU Power Management” feature helps us to auto power on the board at a specific time, it is implemented by an MCU, support software power-off, and RTC alarm power-up functions.

Here’s a simple guide:

Turn on automatically after 100 seconds. (Time must be greater than 60 seconds.):

$sudo echo 100 > /sys/class/i2c-dev/i2c-3/device/3-002d/wakealarm

After setting up the automatic boot, turn off board with the 'poweroff’ command:

$sudo poweroff

Cancel automatic boot:

$sudo echo 0 > /sys/class/i2c-dev/i2c-3/device/3-002d/wakealarm

Query the current settings, in the front is current time, followed by the time of automatic booting:

If no automatic boot is set, it will display "disabled”.

$sudo cat /sys/class/i2c-dev/i2c-3/device/3-002d/wakealarm

Note that some older versions of hardware may not support this feature, if you don't see this file node in your system:

/sys/class/i2c-dev/i2c-3/device/3-002d/wakealarm

your board may be it does not support this feature.

OpenCV has been pre-installed in FriendlyCore (Version after 20191126) and does not require manual installation.

Please refre this link: https://github.com/friendlyarm/install-opencv-on-friendlycore/blob/s5pxx18/README.md

Quick test：

. /usr/bin/cv-env.sh

. /usr/bin/setqt5env-eglfs

cd /usr/local/share/opencv4/samples/python

python3 turing.py

git clone https://github.com/friendlyarm/install-caffe-on-friendlycore

cd install-caffe-on-friendlycore

sudo ./install-caffe.sh

Run the following commands：

wget https://download.docker.com/linux/ubuntu/dists/xenial/pool/stable/arm64/containerd.io_1.2.6-3_arm64.deb

wget https://download.docker.com/linux/ubuntu/dists/xenial/pool/stable/arm64/docker-ce-cli_19.03.2~3-0~ubuntu-xenial_arm64.deb

wget https://download.docker.com/linux/ubuntu/dists/xenial/pool/stable/arm64/docker-ce_19.03.2~3-0~ubuntu-xenial_arm64.deb

sudo dpkg -i containerd.io_1.2.6-3_arm64.deb

sudo dpkg -i docker-ce-cli_19.03.2~3-0~ubuntu-xenial_arm64.deb

sudo dpkg -i docker-ce_19.03.2~3-0~ubuntu-xenial_arm64.deb

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

Connect an EC20 module to a USB to miniPCIe board and connect the board to an ARM board's USB Host. Here is a hardware setup:

Power on the board and you will be able to surf the internet with the 4G module like using an Android phone.

Replace the logo.bmp:

/opt/FriendlyARM/smart4418/android/device/friendly-arm/nanopi3/boot/logo.bmp

/opt/FriendlyARM/smart4418/android/device/friendly-arm/nanopi2/boot/logo.bmp

Replace the bootanimation.zip:

/opt/FriendlyARM/smart4418/android/device/friendly-arm/nanopi3/bootanimation.zip

/opt/FriendlyARM/smart4418/android/device/friendly-arm/nanopi2/bootanimation.zip

Re-compile android.

Enter the uboot command line mode on the serial terminal when powering on, and then enter the following command:

fastboot 0

For S5P4418:

fastboot flash partmap partmap.txt

fastboot flash 2ndboot bl1-mmcboot.bin

fastboot flash fip-loader loader-mmc.img

fastboot flash fip-secure bl_mon.img

fastboot flash fip-nonsecure bootloader.img

fastboot flash boot boot.img

fastboot flash system system.img

fastboot flash cache cache.img

fastboot flash userdata userdata.img

For S5P6818:

fastboot flash partmap partmap.txt

fastboot flash 2ndboot bl1-mmcboot.bin

fastboot flash fip-loader fip-loader.img

fastboot flash fip-secure fip-secure.img

fastboot flash fip-nonsecure fip-nonsecure.img

fastboot flash boot boot.img

fastboot flash system system.img

fastboot flash cache cache.img

fastboot flash userdata userdata.img

Android 5:

vendor/friendly-arm/nanopi3/security/

Android 7:

build/target/product/security/

Download the compiler package:

git clone https://github.com/friendlyarm/prebuilts.git -b master --depth 1

cd prebuilts/gcc-x64

cat toolchain-4.9.3-armhf.tar.gz* | sudo tar xz -C /

Then add the compiler's directory to "PATH" by appending the following lines in "~/.bashrc":

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

export GCC_COLORS=auto

Execute "~/.bashrc" to make the changes take effect. Note that there is a space after the first ".":

. ~/.bashrc

This compiler is a 64-bit one therefore it cannot be run on a 32-bit Linux machine. After the compiler is installed you can verify it by running the following commands:

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)

Download Kernel Source Code

git clone https://github.com/friendlyarm/linux.git -b nanopi2-v4.4.y --depth 1

cd linux

The kernel source for S5P6818 is in the "nanopi2-v4.4.y" branch. Before you start compiling it you need to switch to this branch.

Compile Ubuntu Kernel

touch .scmversion

make ARCH=arm64 nanopi3_linux_defconfig

make ARCH=arm64

After your compilation succeeds an "arch/arm/boot/Image" will be generated and a DTB file(s5p6818-nanopi3-rev*.dtb) will be generated in the "arch/arm/boot/dts/nexell" directory. You can use them to replace the existing Image and DTB files in the boot partition of your bootable SD card.

Update kernel in SD card

If you use an SD card to boot Ubuntu you can copy your generated Image and DTB files to your SD card's boot partition(e.g. partition 1 /dev/sdX1).

Update kernel in eMMC

If you boot your board from eMMC you can update your kernel file by following the steps below:

1) Usually after OS is loaded eMMC's boot partition (in our example eMMC's device name was /dev/mmcblk0p1) will be automatically mounted and you can verify that by running "mount"

2) Connect your board to a host PC running Ubuntu and copy the Image and DTB files to eMMC's boot partition

3) Or you can copy your generated kernel file to an external storage card(e.g. an SD card or a USB drive), connect the storage card to your board the move the file from the card to eMMC's boot partition

4) After update is done type "reboot" to reboot your board. Note: don't just directly disconnect your board from its power source or press the reset button to reboot the board. These actions will damage your kernel file

Generate Your boot.img

The Android 7.1.2 source code already contains the pre-compiled kernel. If you need to customize it, you can compile the kernel according to the following guide.

git clone https://github.com/friendlyarm/linux.git -b nanopi2-v4.4.y --depth 1

cd linux

touch .scmversion

make ARCH=arm64 nanopi3_nougat_defconfig

make ARCH=arm64

The newly generated kernel is arch/arm64/boot/Image，The new DTB file is also included under the directory arch/arm64/boot/dts/nexell/.(s5p6818-nanopi3-rev*.dtb).

If you only want to debug the kernel, you can quickly update it with adb:

adb root; adb shell mkdir /storage/sdcard1/; adb shell mount -t ext4 /dev/block/mmcblk0p1 /storage/sdcard1/;

adb push arch/arm64/boot/Image arch/arm64/boot/dts/nexell/s5p6818-nanopi3-rev*.dtb /storage/sdcard1/

If you want to generate boot.img for burning, you can copy the kernel Image and DTB files to the Android7 source code directory: device/friendlyelec/nanopi3/boot, then recompile Android7.

Download the U-Boot v2016.01 source code and compile it. Note that the github's branch is nanopi2-v2016.01:

git clone https://github.com/friendlyarm/u-boot.git

cd u-boot

git checkout nanopi2-v2016.01

make s5p6818_nanopi3_config

make CROSS_COMPILE=aarch64-linux-

After your compilation succeeds a fip-nonsecure.img will be generated. If you want to test it flash it to your installation SD card to replace an existing U-Boot v2016.01 file via fastboot, sd-fuse_s5p6818 or eflasher ROM.

For Android7: You can copy fip-nonsecure.img to the Android7 source directory device/friendlyelec/nanopi3/boot and recompile Android7.

Note: you cannot use mixed U-Boot files. For example you cannot use fastboot to update an existing U-Boot V2014.07 and you cannot use bootloader.img to replace an existing u-boot.bin.

Install 64 bit Ubuntu 16.04 on your host PC.

sudo apt-get install bison g++-multilib git gperf libxml2-utils make python-networkx zip

sudo apt-get install flex curl libncurses5-dev libssl-dev zlib1g-dev gawk minicom

sudo apt-get install openjdk-8-jdk

sudo apt-get install exfat-fuse exfat-utils device-tree-compiler liblz4-tool

There are two ways to download the source code:

repo archive file on netdisk

Netdisk URL: Click here

File location on netdisk：sources/s5pxx18-android-7.git-YYYYMMDD.tgz (YYYYMMDD means the date of packaging)

After extracting the repo package from the network disk, you need to execute the sync.sh script, which will pull the latest code from gitlab:

tar xvzf /path/to/netdisk/sources/s5pxx18-android-7.git-YYYYMMDD.tgz

cd s5pxx18-android-7

./sync.sh

git clone from gitlab

NanoPC-T3 source code is maintained in gitlab, You can download it by running the following command:

git clone https://gitlab.com/friendlyelec/s5pxx18-android-7.git -b master

cd s5pxx18-android-7

source build/envsetup.sh

lunch aosp_nanopi3-userdebug

make -j8

After your compilation succeeds the following files will be generated in the "out/target/product/nanopi3/" directory.

filename

partition

Description

bl1-mmcboot.bin

raw

boot firmware

fip-loader.img

raw

boot firmware

fip-secure.img

raw

boot firmware

fip-nonsecure.img

raw

uboot-v2016.01

env.conf

Uboot environment variable containing Android kernel command line parameters

boot.img

boot

kernel Image, DTBs; logo; Android ramdisk

cache.img

cache

userdata.img

userdata

system.img

system

partmap.txt

Partition description file

In this use case the NanoPC-T3 runs Debian. If you connect your NanoPC-T3 to our LCD or an HDMI monitor after Debain is fully loaded 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.

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

If your NanoPC-T3 runs Android5.1 and it is connected to our LCD or an HDMI monitor after Android is fully loaded click on the "Camera" icon and the application will be started. You can take pictures or record videos

Under Debian a camera utility "nanocams" is available for previewing 40 frames and picture taking. You can try it by following the commands below

sudo nanocams -p 1 -n 40 -c 4 -o IMG001.jpg

For more details about the usage of the nanocams run "nanocams -h".

You can get its source code from our git hub:

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

Under FriendlyCore (kernel 4.4), You can try it by following the commands below:

Enter the following command to preview the video：

gst-launch-1.0 -e v4l2src device=/dev/video6 ! video/x-raw,format=I420,framerate=30/1,width=1280,height=720 ! nxvideosink

Enter the following command to start recording (VPU hardware encoding)：

gst-launch-1.0 -e v4l2src device=/dev/video6 ! video/x-raw,format=I420,framerate=30/1,width=1280,height=720 ! tee name=t t. \

! queue ! nxvideosink t. ! queue ! nxvideoenc bitrate=12000000 ! mp4mux ! \

filesink location=result_720.mp4

The full name of "OpenCV" is Open Source Computer Vision Library and it is a cross platform vision library.

When the NanoPC-T3 runs Debian users can use OpenCV APIs to access a USB Camera device.

1. Here is a guideline on how to use OpenCV with C++ on the NanoPC-T3:

Firstly you need to make sure your NanoPC-T3 is connected to the internet.Login to your NanoPC-T3 via a serial terminal or SSH. After login type in your username(root) and password(fa):

Run the following commands:

apt-get update

apt-get install libcv-dev libopencv-dev

2. Make sure your USB camera works with the NanoPC-T3. You can test your camera with NanoPC-T3's camera utility.

3. Check your camera device:

ls /dev/video*

Note:in our test case video0 was the device name.

4. OpenCV's code sample(official code in C++) is under /home/fa/Documents/opencv-demo. Compile the code sample with the following commands:

cd /home/fa/Documents/opencv-demo

make

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

5. Connect NanoPC-T3 to USB Keyboard & Run the Following Command:

./demo

opencv is successfully started

The Matrix-GPS module is a small GPS module with high performance. It can be used in navigation devices, four-axle drones and etc.

The Matrix-GPS module uses serial communication. When the NanoPC-T3 is connected to the Matrix GPS module, after the NanoPC-T3 is powered up type in the following command in a terminal or click on the xgps icon it will be started.

$su - fa -c "DISPLAY=:0 xgps 127.0.0.1:9999"

Or on the Debian GUI start the LXTerminal, type in "xgps" and enter it will be started too.

For more details about this GPS module refer to Click to check

Refer to the following diagram to connect the NanoPC-T3 to the Matrix-GPS:

Connection Details:

Matrix-GPS

NanoPC-T3

RXD

Pin11

TXD

Pin12

Pin29

GND

Pin30

FriendlyElec developed a library called “libfriendlyarm-things.so”, for android developer to access the hardware resources on the development board in their android apps, the library is based on Android NDK.

Accessible Modules:

Serial Port

PWM

EEPROM

ADC

LED

LCD 1602 (I2C)

OLED (SPI)

Interfaces & Ports:

GPIO

Serial Port

I2C

SPI

Refer to the following url for details：

Android

Here are the LCDs that are supported under Android:S430, S700/S701, S702, HD700, HD702, HD101 and X710 all of which are LCDs with capacitive touch.

FriendlyCore & Lubuntu Desktop

Here are the LCDs that are supported under FriendlyCore and Lubuntu Desktop:S430, S700/S701, S702, HD700, HD702, HD101 and X710 all of which are LCDs with capacitive touch;

W35B, H43, P43, S70D and Matrix 2.8" SPI Key TFT LCD all of which are LCDs with resistive touch

All these LCD's tech details can be obtained on our wiki site:LCDModules

Image File: [2]

Source Code: [3]

If you have any further questions please visit our forum http://www.friendlyarm.com/Forum/ and post a message or email us at techsupport@friendlyarm.com. We will endeavor to get back to you as soon as possible.

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:

FriendlyCore, Lubuntu：

Fix Bluetooth stability issue

FriendlyWrt：

Upgrade to OpenWrt r19-snapshot 64bit, support Docker CE

eflasher：

1) Supports flashing only some files, such as updating only the kernel and uboot in emmc

2) Added gui option to disable overlay filesystem

3) Add command line parameters to achieve one-click installation without interaction

4) Fix the issue that the same mac address will appear on different devices after backup and restore image

5) UI interface can now be configured with title, hide interface menus and buttons

FriendlyCore:

Pre-installed OpenCV 4.1.2

Introducing a new system FriendlyWrt:

FriendlyWrt is a customized OpenWrt system developed by FriendlyElec. It is open source and suitable for applications in IoT, NAS and smart home gateways and etc.

Please refre: http://wiki.friendlyarm.com/wiki/index.php/How_to_Build_FriendlyWrt

FriendlyCore, Lubuntu updated as follows:

1) Added support for new 4.3-inch screen YZ43

2) Compile bcmdhd as a module.

Android7 update is as follows:

1) Added support for new 4.3-inch screen YZ43

2) Optimize the touch experience when using HD900 screen under Android 7 system

Android7, FriendlyCore, Lubuntu：

Fixed audio playback issue.

Android7 updated as follows:

1)Added support for Android hardware access library (named FriendlyThing), support access to hardware resources such as GPIO, PWM, RTC, serial port and watchdog, providing open source demo

2) Added support for camera CAM500B (OV5640)

3) Added support for LCD W500 (800x480)

4) Fixed LCD-S430 compatibility issues

FriendlyCore, FriendlyDesktop updated as follows:

1) Kernel version updated to v4.4.172, same as Android 7

2) Added Docker support, support 32bit and 64bit file systems

3) Kernel configuration items are optimized to enable more features and device drivers

Introducing a new system Android 7.1.2

1) Features similar to the old version of Android 5, support 4G, WiFi, Ethernet, Bluetooth, etc.

2) Kernel version: 4.4.172

3) Known issue: The camera is not working yet

Android/FriendlyCore/Lubuntu updated as follows：

1) Fix an issue where HD101B can't be touched in some cases

2) Fix GPIO configuration of Power key

3) Solve the problem of too small volume: the volume of the DAC is changed from -20dB to -6dB during playback.

4) Add more models of USB Wi-Fi support, built-in driver rtl8821CU.ko, rtl88XXau.ko

Updates for Lubuntu only：

1) Modify Lubuntu's Power key behavior to (without pop-ups) shut down directly

2) Add script xrotate.sh to simplify screen rotation settings (Note: screen rotation will lose performance)

The following updates are only available for NanoPC T3/T3+, Smart6818:

Support for reading Ethernet Mac addresses from the onboard EEPROM, only supports the following systems: FriendlyCore, Lubuntu, Android7

Linux(Ubuntu 16.04/18.04) uses OverlayFS to enhance filesystem stability.

1) Configure LED1 to be in heartbeat mode

2) Fix HDMI 1080P may have no display problem in some cases

3) Fix the issue that mysql cannot be installed under Linux

4) Fix the issue that the 1-wire touch resistance screen cannot be used under lubuntu

1) Update uboot-v2014.07, uboot-v2016.01 for HD702V LCD

2) Adjust Qt5 font path

Android5 updated as follows:

1) Add support for 4G network, support module: Quectel EC20

2) Add audio setting UI, you can set the default output to headphones or HDMI

3) Synchronously turn off the backlight of the one-line touch screen when the system Shutdown

FriendlyCore updated as follows:

1) Add OV5640 camera support

2) Update BL1 to improve system startup stability

Lubuntu updated as follows:

1) Add Chrome-browser browser, support web page 1080P hardware decoding, support WebGL

2) Set the audio output channel to HDMI by default (can be changed via /etc/asound.conf)

3) Update BL1 to improve system startup stability

4) Fixed some issues regarding the package error in the previous version

5) Adjust DPMS settings, turn off automatic sleep by default

Released English version

Added sections 5.2.4 and 8

Added section 9

Updated sections 5.2.2 and 8.2

Updated sections 6.4 and 11

Updated sections 6.2 and 6.3: wireless connection and setting up WIFI AP

Updated section 8.4.1: added compiling kernel for UbuntuCore

Added section 3: software features

Added section 7: UbuntuCore

Added section 9.5: LCD support

Updated sections 6.10

浩泽天

关注

0
点赞
踩
0

收藏

觉得还不错? 一键收藏
0
评论
android运行iwconfig命令,NanoPC-T3

Overview Front BackThe NanoPC-T3 octa-core single board computer is designed and developed by FriendlyARM for professional and enterprise users. It uses the Samsung Octa-Core Cortex-A53 S5P6818 So...
复制链接

扫一扫