|
|
| (One intermediate revision by the same user not shown) |
| Line 1: |
Line 1: |
| − | ==Ubuntu-Core with Qt-Embedded==
| |
| − | ===Introduction===
| |
| − | 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
| |
| − |
| |
| − | ==Make Your Own OS Image==
| |
| − |
| |
| − | ===Install Cross Compiler===
| |
| − | Download the compiler package:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | 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/
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | Then add the compiler's directory to "PATH" by appending the following lines in "~/.bashrc":
| |
| − | <syntaxhighlight lang="bash">
| |
| − | export PATH=/opt/FriendlyARM/toolchain/4.9.3/bin:$PATH
| |
| − | export GCC_COLORS=auto
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | Execute "~/.bashrc" to make the changes take effect. Note that there is a space after the first ".":
| |
| − | <syntaxhighlight lang="bash">
| |
| − | . ~/.bashrc
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | 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:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | 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)
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | ===Compile U-Boot===
| |
| − | Download the U-Boot source code and compile it. Note that the github's branch is nanopi2-lollipop-mr1:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | 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-
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | After your compilation succeeds a u-boot.bin will be generated. If you want to test it flash it to your installation SD card via fastboot. Here is how you can do it:<br/>
| |
| − | 1) On your host PC run "sudo apt-get install android-tools-fastboot" to install the fastboot utility;<br/>
| |
| − | 2) Connect your NanoPC-T3 to your host PC via a serial cable (e.g. PSU-ONECOME). Press the enter key within two seconds right after you power on your NanoPC-T3 and you will enter uboot's command line mode;<br/>
| |
| − | 3) After type in "fastboot" and press "enter" you will enter the fastboot mode;<br/>
| |
| − | 4) Connect your NanoPC-T3 to this host PC via a microUSB cable and type in the following command to flash u-boot.bin:<br/>
| |
| − | <syntaxhighlight lang="bash">
| |
| − | fastboot flash bootloader u-boot.bin
| |
| − | </syntaxhighlight>
| |
| − | <br />
| |
| − | Warning: you cannot update this SD card by commanding "dd". This command will cause trouble when booting the NanoPC-T3.<br/>
| |
| − |
| |
| − | ===Prepare mkimage===
| |
| − | You need the mkimage utility to compile a U-Boot source code package. Make sure this utility works well on your host before you start compiling a uImage.<br/>
| |
| − | You can install this utility by either commanding "sudo apt-get install u-boot-tools" or following the commands below:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | cd uboot_nanopi2
| |
| − | make CROSS_COMPILE=arm-linux- tools
| |
| − | sudo mkdir -p /usr/local/sbin && sudo cp -v tools/mkimage /usr/local/sbin
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | ===Compile Linux Kernel===
| |
| − | ====Compile Kernel====
| |
| − | * Download Kernel Source Code
| |
| − | <syntaxhighlight lang="bash">
| |
| − | git clone https://github.com/friendlyarm/linux-3.4.y.git
| |
| − | cd linux-3.4.y
| |
| − | git checkout nanopi2-lollipop-mr1
| |
| − | </syntaxhighlight>
| |
| − | The NanoPC-T3's kernel source code lies in the "nanopi2-lollipop-mr1" branch.
| |
| − | * Compile Android Kernel
| |
| − | <syntaxhighlight lang="bash">
| |
| − | make nanopi3_android_defconfig
| |
| − | touch .scmversion
| |
| − | make uImage
| |
| − | </syntaxhighlight>
| |
| − | * Compile Debian Kernel
| |
| − | <syntaxhighlight lang="bash">
| |
| − | make nanopi3_linux_defconfig
| |
| − | touch .scmversion
| |
| − | make uImage
| |
| − | </syntaxhighlight>
| |
| − | After your compilation succeeds a uImage will be generated in the "arch/arm/boot/uImage" directory. This kernel is for LCD output. You can use it to replace the existing uImage.<br/>
| |
| − | If you want to generate a kernel for HDMI output you need to run nanopi3_linux_hdmi_defconfig and do it this way:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | make nanopi3_linux_hdmi_defconfig
| |
| − | touch .scmversion
| |
| − | make menuconfig
| |
| − | </syntaxhighlight>
| |
| − | After your compilation succeeds a uImage will be generated for HDMI 720P. If you want a uImage for 1080P you can do it this way:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | touch .scmversion
| |
| − | make nanopi3_linux_hdmi_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
| |
| − | </syntaxhighlight>
| |
| − | After your compilation succeeds a uImage will be generated for HDMI 1080P. You can use it to replace the existing uImage.hdmi.
| |
| − | * Compile Kernel for Ubuntu Core
| |
| − | The steps here are nearly the same as the steps for compiling a Debian kernel:<br />
| |
| − | LCD Output:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | make nanopi3_core-qt_defconfig
| |
| − | </syntaxhighlight>
| |
| − | HDMI Output:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | make nanopi3_core-qt_hdmi_defconfig
| |
| − | </syntaxhighlight>
| |
| − | Select your configuration file and run the following commands to generate a uImage.
| |
| − | <syntaxhighlight lang="bash">
| |
| − | touch .scmversion
| |
| − | make uImage
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | ====Use Your Generated Kernel====
| |
| − | * Update the kernel file in SD card
| |
| − | If you use an SD card to boot Android you can copy your generated uImage file to your SD card's boot section(e.g. section 1 /dev/sdX1).<br/>
| |
| − | If you use an SD card to Debian and you generated a uImage for an HDMI monitor you can use that uImage to replace the uImage.hdmi file in the SD card's boot section. If you use an SD card to Debian and you generated a uImage for an LCD you can use that uImage to replace the uImage file in the SD card's boot section.
| |
| − |
| |
| − | * Update Android kernel file in eMMC
| |
| − | If you want to update the kernel file in eMMC you need firstly boot your board, then mount eMMC's boot section, replace the boot section's kernel file with your generated one and reboot your board to make your new kernel run.<br/>
| |
| − | If you boot your board from eMMC you can update your kernel file by following the steps below:<br/>
| |
| − | 1) After Android is loaded mount eMMC's boot section (in our example eMMC's device name was /dev/mmcblk0p1) by using the following commands:<br/>
| |
| − | <syntaxhighlight lang="bash">
| |
| − | su
| |
| − | mount -t ext4 /dev/block/mmcblk0p1 /mnt/media_rw/sdcard1/
| |
| − | </syntaxhighlight>
| |
| − | 2) Connect your board to a host PC running Ubuntu and copy the uImage file to eMMC's boot section by running the following commands;<br/>
| |
| − | <syntaxhighlight lang="bash">
| |
| − | adb push uImage /mnt/media_rw/sdcard1/
| |
| − | </syntaxhighlight>
| |
| − | 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 section;<br/>
| |
| − | 4) After update is done type in "reboot" to reload Android. Note don't directly power off and on the board or press the reset button to reboot the board. These two actions will damage your kernel file.<br/>
| |
| − |
| |
| − | * Update Debian kernel file in eMMC
| |
| − | If you boot your board from eMMC you can update your kernel file by following the steps below:<br/>
| |
| − | 1) When Debian is being loaded eMMC's boot section will be automatically mounted(in our example eMMC's device name was /dev/mmcblk0p1). You can use "mount" to verify that;<br/>
| |
| − | 2) Connect your board to a host PC via Ethernet and copy your generated uImage file via scp/ftp to eMMC's boot section and replace the existing file. If your file is for an LCD use your uImage file to replace the existing uImage. If your file is for an HDMI monitor use your uImage.hdmi file to replace the existing uImage.hdmi file;<br/>
| |
| − | 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 section;<br/>
| |
| − | 4) After update is done type in "reboot" to reload Debian. Note don't directly power off and on the board or press the reset button to reboot the board. These two actions will damage your kernel file<br/>
| |
| − |
| |
| − | * Generate Your boot.img
| |
| − |
| |
| − | If you want to generate an image file that can be flashed to eMMC you need to generate a boot.img file and copy it to your installation SD card.<br/>
| |
| − | For Android copy the uImage file to Android source code's "device/friendly-arm/nanopi3/boot/" directory and compile this whole Android source code. After your compilation is successful you will get a boot.img file.<br/>
| |
| − | For Debian follow the steps below to generate a boot.img file:<br/>
| |
| − | 1) Download debian_nanopi2
| |
| − | <syntaxhighlight lang="bash">
| |
| − | git clone https://github.com/friendlyarm/debian_nanopi2.git
| |
| − | </syntaxhighlight>
| |
| − | 2) Copy the image file for an HDMI monitor and use it to replace the "debian_nanopi2/boot/uImage.hdmi" file and copy the image file for an LCD and use it to replace the "debian_nanopi2/boot/uImage" file;<br/>
| |
| − | 3) Generate Debian's boot.img
| |
| − | <syntaxhighlight lang="bash">
| |
| − | cd debian_nanopi2
| |
| − | mkdir rootfs
| |
| − | ./build.sh
| |
| − | </syntaxhighlight>
| |
| − | A newly generated boot.img will be under the "debian_nanopi2/sd-fuse_nanopi2/debian" directory.<br/>
| |
| − | The "mkdir rootfs" command creates a working directory for the build.sh script to run. It also creates some files such as "rootfs.img" but these files are useless.
| |
| − |
| |
| − | ====Compile Kernel Modules====
| |
| − | Android contains kernel modules which are in the "/lib/modules" directory in the system section. If you want to add your own modules to the kernel or you changed your kernel configurations you need to recompile these new modules.<br/>
| |
| − | Compile Original Kernel Modules:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | cd linux-3.4.y
| |
| − | make CROSS_COMPILE=arm-linux- modules
| |
| − | </syntaxhighlight>
| |
| − | Here we have two new modules and we can compile them by following the commands below:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | cd /opt/FriendlyARM/s5p6818/android
| |
| − | ./vendor/friendly-arm/build/common/build-modules.sh
| |
| − | </syntaxhighlight>
| |
| − | The "/opt/FriendlyARM/s5p6818/android" directory points to the top directory of Android source code. You can get more details by specifying option "-h".<br/>
| |
| − | After your compilation succeeds new modules will be generated
| |
| − |
| |
| − | ===Compile Android===
| |
| − |
| |
| − | * Install Cross Compiler
| |
| − | Install 64 bit Ubuntu 16.04 on your host PC.
| |
| − | <syntaxhighlight lang="bash">
| |
| − | 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
| |
| − | </syntaxhighlight>
| |
| − | For more details refer to https://source.android.com/source/initializing.html 。
| |
| − |
| |
| − | * Download Source Code
| |
| − | You need to use repo to get the Android source code. Refer to https://source.android.com/source/downloading.html 。
| |
| − | <syntaxhighlight lang="bash">
| |
| − | mkdir android && cd android
| |
| − | repo init -u https://github.com/friendlyarm/android_manifest.git -b nanopi3-lollipop-mr1
| |
| − | repo sync
| |
| − | </syntaxhighlight>
| |
| − | The "android" directory is the working directory.
| |
| − |
| |
| − | * Compile System Package
| |
| − | <syntaxhighlight lang="bash">
| |
| − | source build/envsetup.sh
| |
| − | lunch aosp_nanopi3-userdebug
| |
| − | make -j8
| |
| − | </syntaxhighlight>
| |
| − | After your compilation succeeds an image will be generated in the "out/target/product/nanopi3/" directory.
| |
| − | ::{| class="wikitable"
| |
| − | |-
| |
| − | |filename || partition || Description
| |
| − | |-
| |
| − | |boot.img || boot || -
| |
| − | |-
| |
| − | |cache.img || cache || -
| |
| − | |-
| |
| − | |userdata.img || userdata || -
| |
| − | |-
| |
| − | |system.img || system || -
| |
| − | |-
| |
| − | |partmap.txt || - || partition file
| |
| − | |-
| |
| − | |}
| |
| − |
| |
| − | * Flash Image to SD Card
| |
| − | If you want to boot your board from an SD card you need to copy your generated image file to the "sd-fuse_s5p6818
| |
| − | /android/" directory and flash it to your SD card with our script. For more details refer to [[# Make an Installation SD Card under Linux Desktop]]。
| |
| − |
| |
| − | * Flash Image to eMMC
| |
| − | After compiling Android successfully you can flash it to eMMC with either of the following methods:<br/>
| |
| − | 1) fastboot: right after the NanoPC-T2 is booted from eMMC press any key to enter the uboot commandline mode and type in "fastboot"<br/>
| |
| − | Connect your board to a host PC running Ubuntu with a USB cable and run the following commands in the PC's terminal:<br />
| |
| − | <syntaxhighlight lang="bash">
| |
| − | 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
| |
| − | </syntaxhighlight>
| |
| − | 2) Use an SD Card<br/>
| |
| − | Copy these files: boot.img, cache.img, userdata.img, system.img, partmap.txt from the out/target/product/nanopi3 directory to your installation SD card's images/android directory and you can use this SD card to flash Android to eMMC.<br/>
| |
| − |
| |
| − | ==Connect NanoPC-T3 to External Modules==
| |
| − | ===Connect NanoPC-T3 to USB Camera(FA-CAM202)===
| |
| − | * 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.
| |
| − | [[File:USB-camera-nanopi2.png|frameless|500px|USB camera]]
| |
| − | [[File:USB-camera-nanopC-T2-01.png|frameless|500px|USB camera-01]]
| |
| − |
| |
| − | ===Connect NanoPC-T3 to CMOS 5M-Pixel Camera===
| |
| − | <!---
| |
| − | * In this use case the NanoPC-T3 runs Android5.1. If you connect your NanoPC-T3 to our LCD or an HDMI monitor after Android is fully loaded click on the "Camera" icon and the application will be started.
| |
| − | [[File:CMOS-camera-nanopc-t2.png|frameless|500px|CMOS camera]]
| |
| − | --->
| |
| − | For more details about the CAM500A camera refer to [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_CAM500A]<br/>
| |
| − | *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
| |
| − | [[File:CMOS-camera-nanopc-t2.png|frameless|500px|CMOS camera]]
| |
| − |
| |
| − | *Under Debian/Ubuntu a camera utility "nanocams" is available for previewing 40 frames and picture taking. You can try it by following the commands below
| |
| − | <syntaxhighlight lang="bash">
| |
| − | sudo nanocams -p 1 -n 40 -c 4 -o IMG001.jpg
| |
| − | </syntaxhighlight>
| |
| − | For more details about the usage of the nanocams run "nanocams -h".
| |
| − | You can get its source code from our git hub:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | git clone https://github.com/friendlyarm/nexell_linux_platform.git
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | ===Use OpenCV to Access USB Camera===
| |
| − | * 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.<br>
| |
| − | 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:
| |
| − | <br>
| |
| − | <syntaxhighlight lang="bash">
| |
| − | apt-get update
| |
| − | apt-get install libcv-dev libopencv-dev
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | 2. Make sure your USB camera works with the NanoPC-T3. You can test your camera with NanoPC-T3's camera utility.<br>
| |
| − |
| |
| − | 3. Check your camera device:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | ls /dev/video*
| |
| − | </syntaxhighlight>
| |
| − | * 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:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | cd /home/fa/Documents/opencv-demo
| |
| − | make
| |
| − | </syntaxhighlight>
| |
| − | After it is compiled successfully a "demo" executable will be generated<br />
| |
| − |
| |
| − | 5. Connect NanoPC-T3 to USB Keyboard & Run the Following Command:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | ./demo
| |
| − | </syntaxhighlight>
| |
| − | opencv is successfully started
| |
| − |
| |
| − | ===Connect NanoPC-T3 to Matrix GPS Module===
| |
| − | * 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.
| |
| − | <syntaxhighlight lang="bash">
| |
| − | $su - fa -c "DISPLAY=:0 xgps 127.0.0.1:9999"
| |
| − | </syntaxhighlight>
| |
| − | * 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 [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_GPS Click to check]<br />
| |
| − | Refer to the following diagram to connect the NanoPC-T3 to the Matrix-GPS:<br />
| |
| − | [[File:GPS_NanoPC-T2.png|frameless|600px|GPS_NanoPC-T2]]
| |
| − |
| |
| − | Connection Details:
| |
| − | {| class="wikitable"
| |
| − | |-
| |
| − | |Matrix-GPS || NanoPC-T3
| |
| − | |-
| |
| − | |RXD || Pin11
| |
| − | |-
| |
| − | |TXD || Pin12
| |
| − | |-
| |
| − | |5V || Pin29
| |
| − | |-
| |
| − | |GND || Pin30
| |
| − | |}
| |
| − |
| |
| − | ===Connect NanoPC-T3 to FriendlyARM LCD Modules===
| |
| − | * 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.
| |
| − |
| |
| − | * Debian
| |
| − | Here are the LCDs that are supported under Debian:S430, S700/S701, S702, HD700, HD702, HD101 and X710 all of which are LCDs with capacitive touch;<br />
| |
| − | W35B, H43, P43, S70D and Matrix 2.8" SPI Key TFT LCD all of which are LCDs with resistive touch<br/>
| |
| − | All these LCD's tech details can be obtained on our wiki site:[http://wiki.friendlyarm.com/wiki/index.php/Main_Page#LCDModules LCDModules]
| |
| − |
| |
| − | ==Android Hardware Access==
| |
| − | FriendlyElec developed a library called “libfriendlyarm-hardware.so”, for android developer to access the hardware resources on the development board in their android apps, the library is based on Android NDK.<br />
| |
| − | Accessible Modules：
| |
| − | * Serial Port
| |
| − | * PWM
| |
| − | * EEPROM
| |
| − | * ADC
| |
| − | * LED
| |
| − | * LCD 1602 (I2C)
| |
| − | * OLED (SPI)
| |
| − |
| |
| − | Accessible Ports：
| |
| − | * GPIO
| |
| − | * Serial Port
| |
| − | * I2C
| |
| − | * SPI
| |
| − |
| |
| − | Please refer to the following url for details：<br />
| |
| − | * Homepage: http://wiki.friendlyarm.com/wiki/index.php/Android_Hardware_Access
| |
| − | * Examples: https://github.com/friendlyarm/AndroidHardwareAccess
| |
| − | * Guide to API in Chinese: https://github.com/friendlyarm/AndroidHardwareAccess/blob/master/友善电子Android硬件开发指南.pdf
| |
| − |
| |
| − | ==Source Code and Image Files Download Links==
| |
| − | * Image File:[http://dl.friendlyarm.com/]
| |
| − | * Source Code:[https://github.com/friendlyarm]
| |
