|
|
| Line 367: |
Line 367: |
| | * For more details about EEPROM address issues refer to http://www.onsemi.com/pub_link/Collateral/CAT24C01-D.PDF | | * For more details about EEPROM address issues refer to http://www.onsemi.com/pub_link/Collateral/CAT24C01-D.PDF |
| | | | |
| − | ==Get Started==
| + | {{S5P6818Software}} |
| − | ===Essentials You Need===
| + | |
| − | Before starting to use your NanoPC-T3 get the following items ready
| + | |
| − | * NanoPC-T3
| + | |
| − | * SD Card: Class 10 or Above, minimum 8GB SDHC
| + | |
| − | * A DC 5V/2A power is a must
| + | |
| − | * HDMI monitor or LCD
| + | |
| − | * USB keyboard, mouse and possible a USB hub(or a TTL to serial board)
| + | |
| − | * A host computer running Ubuntu 14.04 64 bit system
| + | |
| − | | + | |
| − | | + | |
| − | ===Make an Installation SD Card===
| + | |
| − | ====Boot NanoPC-T3 from SD Card====
| + | |
| − | Get the following files from [https://www.mediafire.com/folder/gg764iwvfm0mf/S5P6818_Board here] to download necessary files:<br />
| + | |
| − | * Get a 4G SDHC card and backup its data if necessary <br />
| + | |
| − | ::{| class="wikitable"
| + | |
| − | |-
| + | |
| − | |colspan=2|Image Files:
| + | |
| − | |-
| + | |
| − | |s5p6818-debian-sd4g-YYYYMMDD.img || Debian image files
| + | |
| − | |-
| + | |
| − | |s5p6818-android-sd4g-YYYYMMDD.img || Android image files
| + | |
| − | |-
| + | |
| − | |s5p6818-ubuntu-core-qte-sd4g-YYYYMMDD.img || Ubuntu Core + QT image files
| + | |
| − | | + | |
| − | |-
| + | |
| − | |colspan=2|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 NanoPC-T3's boot slot, press and hold the boot key and power on (with a 5V/2A power source). If the PWR LED is on and LED1 is blinking this indicates your NanoPC-T3 has successfully booted.<br />
| + | |
| − | | + | |
| − | ====Flash image to eMMC with eflasher====
| + | |
| − | * Download eflasher <br />
| + | |
| − | Get the eflasher utility s5p6818-eflasher-sd8g-xxx-full.img.7z<br />
| + | |
| − | This package includes a Ubuntu Core, Debian, Android 5 image files;<br />
| + | |
| − | Get the Windows utility: win32diskimager.rar;<br/>
| + | |
| − | * Flash eflasher Image <br />
| + | |
| − | Extract the .7z package and you will get .img 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.<br/>
| + | |
| − | If your PC runs Linux you can use the dd command to flash a .img file to the SD card;<br />
| + | |
| − | * Flash image to eMMC
| + | |
| − | Insert this card into your NanoPC-T3, connect the board to an HDMI monitor or an LCD, press and hold the boot key and power on (with a 5V/2A power source) the board. After your board is powered on you will see multiple OS options and you can select an OS to start installation.
| + | |
| − | <!---
| + | |
| − | * Download RAW Image<br />
| + | |
| − | Get the image file: s5p6818-eflasher-sd4g.img.zip and the Windows utility: win32diskimager.rar;
| + | |
| − | * Flash RAW Image to SD Card<br />
| + | |
| − | 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
| + | |
| − | * Prepare RAW image
| + | |
| − | Go to this link [https://www.mediafire.com/folder/gg764iwvfm0mf/NanoPC-T3_Board] to download Android and Debian image files(System-image-files-for-eMMC). After download untar the ".tgz" ball and copy the files to your SD card.
| + | |
| − | ::{| class="wikitable"
| + | |
| − | |-
| + | |
| − | |OS || Image || Files || Copy to...
| + | |
| − | |-
| + | |
| − | |Android 5.1 || android-lollipop-images.tgz <br /> android-lollipop-images.tgz.hash.md5
| + | |
| − | || boot.img <br /> system.img <br /> userdata.img <br /> cache.img <br /> partmap.txt <br />
| + | |
| − | || images\android
| + | |
| − | |-
| + | |
| − | |Debian (Jessie) || debian-jessie-images.tgz <br />debian-jessie-images.tgz.hash.md5
| + | |
| − | || boot.img <br />rootfs.img <br />partmap.txt <br />
| + | |
| − | || images\debian
| + | |
| − | |-
| + | |
| − | |Ubuntu Core + QT || core-qte-images.tgz <br />core-qte-images.tgz.hash.md5
| + | |
| − | || boot.img <br />rootfs.img <br />partmap.txt <br />
| + | |
| − | || images\core-qte
| + | |
| − | | + | |
| − | |-
| + | |
| − | |}
| + | |
| − | | + | |
| − | * Specify OS
| + | |
| − | By default the SD card's configuration file "images\FriendlyARM.ini" specifies Android to be flashed to eMMC. If you want to install Debian make the following change:
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | OS = Debian
| + | |
| − | </syntaxhighlight>
| + | |
| − | "#" is a comment
| + | |
| − | | + | |
| − | * Flash Image to NanoPC-T3's eMMC
| + | |
| − | Insert this card into your NanoPC-T3, connect the board to an HDMI monitor or an LCD, press and hold the boot key and power on (with a 5V/2A power source) the board to start installation. You can watch the whole installation process from the HDMI monitor or LCD. If the following messages pop up it means the installation has succeeded.
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | Android is fused successfully.
| + | |
| − | All done.
| + | |
| − | </syntaxhighlight>
| + | |
| − | After installation is done do "reset" or power off and on the board to boot the board from eMMC.
| + | |
| − |
| + | |
| − | You can check the LED's status to monitor the installation process too:
| + | |
| − | ::{| class="wikitable"
| + | |
| − | |-
| + | |
| − | |LED Status || Installation Status
| + | |
| − | |-
| + | |
| − | |LED1 blinks twice continuously <br /> LED2 off || Power on normal.<br /> If installation doesn't proceed LED1 will keep behaving this way and LED2 will be off
| + | |
| − | |-
| + | |
| − | |LED1 and LED2 blink alternatively with each blink for 0.3s || Installation proceeding
| + | |
| − | |-
| + | |
| − | |LED1 and LED2 blink alternatively with each blink for 1.2s || Installation succeeded
| + | |
| − | |-
| + | |
| − | |LED1 and LED2 blink simultaneously || Installation failed
| + | |
| − | |-
| + | |
| − | |}
| + | |
| − | ---><br/ >
| + | |
| − | [[File:NanoPC-T3-eMMC.png|frameless|500px|NanoPC-T3-eMMC]]
| + | |
| − | | + | |
| − | ====Make Installation Card under Linux Desktop====
| + | |
| − | *1) Insert your SD card into a host computer running Ubuntu and check your SD card's device name
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | dmesg | tail
| + | |
| − | </syntaxhighlight>
| + | |
| − | Search the messages output by "dmesg" for similar words like "sdc: sdc1 sdc2". If you can find them it means your SD card has been recognized as "/dev/sdc". Or you can check that by commanding "cat /proc/partitions"
| + | |
| − | | + | |
| − | *2) Downlaod Linux script
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | git clone https://github.com/friendlyarm/sd-fuse_s5p6818.git
| + | |
| − | cd sd-fuse_s5p6818
| + | |
| − | </syntaxhighlight>
| + | |
| − | | + | |
| − | *3) Make Android SD Card
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | su
| + | |
| − | ./fusing.sh /dev/sdx
| + | |
| − | </syntaxhighlight>
| + | |
| − | (Note: you need to replace "/dev/sdx" with the device name in your system) <br />
| + | |
| − | 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) Here is how to make a Debian SD card
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | ./fusing.sh /dev/sdx debian
| + | |
| − | </syntaxhighlight>
| + | |
| − | | + | |
| − | ====Extend NanoPC-T3's SD Card Section====
| + | |
| − | * 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:
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | sudo umount /dev/sdx?
| + | |
| − | sudo parted /dev/sdx unit % resizepart 4 100 resizepart 7 100 unit MB print
| + | |
| − | sudo resize2fs -f /dev/sdx7
| + | |
| − | </syntaxhighlight>
| + | |
| − | (Note: you need to replace "/dev/sdx" with the device name in your system)
| + | |
| − | | + | |
| − | ====LCD/HDMI Resolution====
| + | |
| − | When the system boots our uboot will check whether it is connected to an LCD or to an HDMI monitor. If it recognizes an LCD it will configure its resolution. Our uboot defaults to the HDMI 720P configuration.<br/>
| + | |
| − | 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.<br/>
| + | |
| − | 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.
| + | |
| − | | + | |
| − | ===Update Image Files in SD Card From PC Host===
| + | |
| − | If you want to make some changes to the image files in your SD card follow the steps below otherwise you can skip this section.<br/>
| + | |
| − | Insert your SD card into a host PC running Linux, mount the boot and rootfs sections of the SD card and follow the steps below:<br/>
| + | |
| − | 1) If you want to change your kernel command line parameters you can do it via the fw_setevn utility under "sd-fuse_s5p6818/tools".
| + | |
| − | Check the current Command Line:
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | cd sd-fuse_s5p6818/tools
| + | |
| − | ./fw_printenv /dev/sdc | grep bootargs
| + | |
| − | </syntaxhighlight>
| + | |
| − | Android 5.1.1_r6 starts SELinux. By default it is enforcing. You can change it this way:
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | ./fw_setenv /dev/sdc bootargs XXX androidboot.selinux=permissive
| + | |
| − | </syntaxhighlight>
| + | |
| − | This sets it to "permissive". The "XXX" stands for the original bootargs' value.<br/>
| + | |
| − | | + | |
| − | 2) Update Kernel<br/>
| + | |
| − | Our customized uboot will check the LCD type when it boots.<br/>
| + | |
| − | For Android it doesn't make any difference which display device is detected. You can use your generated uImage to replace the existing one under "boot".<br/>
| + | |
| − | For Debian if your generated kernel is for an LCD you need to replace the existing uImage or if your kernel is for an HDMI monitor you need to replace the existing uImage.hdmi.<br/>
| + | |
| − | | + | |
| − | ===Run Android or Debian===
| + | |
| − | * Insert an SD card with Android/Debian image file into your NanoPC-T3, connect the board to an HDMI monitor, press and hold the boot key, power on the board the NanoPC-T3 will boot from the SD card. If you can see the PWR LED on and the LED1 flashing it means your board is working and you will see Android/Debain being loaded on the HDMI monitor.<br/>
| + | |
| − | 1) If you connect the NanoPC-T3 to an HDMI monitor you need to use a USB mouse and a USB keyboard to operate. If you connect it to an LCD with capacitive touch you can operate directly on the LCD.<br/>
| + | |
| − | 2）If you want to do kernel development you need to use a serial communication board, ie a PSU-ONECOM board, which will allow you to operate the board via a serial terminal<br/>
| + | |
| − | * Here is a setup where we connect a NanoPC-T3 to a PC running Ubuntu and Minicom via a serial cable you will see system messages output to the PC’s minicom terminal:
| + | |
| − | [[File:PSU-ONECOM02.png|frameless|400px|PSU-ONECOM02]]
| + | |
| − | * Under Debian the password for "root" is "fa"
| + | |
| − | | + | |
| − | ==Working with Debian==
| + | |
| − | ===Ethernet Connection===
| + | |
| − | * If the NanoPC-T3 is connected to a network via Ethernet before it is powered on, it will automatically obtain an IP after it is powered up.
| + | |
| − | | + | |
| − | ===Wireless Connection===
| + | |
| − | Under Debian you can manage your network with [[Use NetworkManager to configure network settings|NetworkManager]].<br />
| + | |
| − | After Debian boots click on the network icon on the bottom right of the task bar a NetworkManger menu will pop up and all the available networks will be listed. If there is an active wireless network you will see something similar to the following screenshot:<br />
| + | |
| − | [[File:NetworkManagerIcon.png|frameless|400px|NetworkManagerIcon]]<br />
| + | |
| − | You can click on a WiFI AP and connect your board to it.<br />
| + | |
| − | For more details refer to:[[Use NetworkManager to configure network settings|NetworkManager]].<br />
| + | |
| − | | + | |
| − | ===Setup Wi-Fi AP===
| + | |
| − | Follow the steps below. Since our OS image by default already has the NetworkManager utility you will be prompted to uninstall it first:<br />
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | sudo turn-wifi-into-apmode yes
| + | |
| − | </syntaxhighlight>
| + | |
| − | After you uninstall the NetworkManager reboot your board.<br />
| + | |
| − | 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<br />
| + | |
| − | <br />
| + | |
| − | 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:
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | ssh root@192.168.8.1
| + | |
| − | </syntaxhighlight>
| + | |
| − | Type in a password. In our system the password is "fa".<br />
| + | |
| − | <br />
| + | |
| − | To login smoothly via SSH we recommend you turning off WIFI's power save mode by running the following commands:
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | sudo iwconfig wlan0 power off
| + | |
| − | </syntaxhighlight>
| + | |
| − | You can check your WiFi's mode by running the following command:<br />
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | sudo cat /sys/module/bcmdhd/parameters/op_mode
| + | |
| − | </syntaxhighlight>
| + | |
| − | Number 2 means your WiFi is in AP mode. You can switch to the Station mode by running the following command:<br />
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | sudo turn-wifi-into-apmode no
| + | |
| − | </syntaxhighlight>
| + | |
| − | | + | |
| − | ===Bluetooth===
| + | |
| − | Here are the steps to transfer a file from T2 to a mobile phone. Run the following command to search a surrounding Bluetooth device:<br />
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | hcitool scan
| + | |
| − | </syntaxhighlight>
| + | |
| − | <br />
| + | |
| − | In our example a mobile phone was detected and the following messages were listed:<br />
| + | |
| − | Scanning ...<br />
| + | |
| − | 38:BC:1A:B1:7E:DD MEIZU MX4<br />
| + | |
| − | <br />
| + | |
| − | These messages indicated that a MEIZU MX4 mobile phone was detected. We then checked the Bluetooth services this phone supported with its MAC address presented in front of its device name<br />
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | sdptool browse 38:BC:1A:B1:7E:DD
| + | |
| − | </syntaxhighlight>
| + | |
| − | Note: you need to use your device's name and its MAC address when you run these commands.<br /><br />
| + | |
| − | The command listed all the services the phone supported. We needed the "OBEX Object Push" service which is for file transfers.<br />
| + | |
| − | Service Name: OBEX Object Push<br />
| + | |
| − | Service RecHandle: 0x1000b<br />
| + | |
| − | Service Class ID List:<br />
| + | |
| − | "OBEX Object Push" (0x1105)<br />
| + | |
| − | Protocol Descriptor List:<br />
| + | |
| − | "L2CAP" (0x0100)<br />
| + | |
| − | "RFCOMM" (0x0003)<br />
| + | |
| − | Channel: 25<br />
| + | |
| − | "OBEX" (0x0008)<br />
| + | |
| − | Profile Descriptor List:<br />
| + | |
| − | "OBEX Object Push" (0x1105)<br />
| + | |
| − | Version: 0x0100<br />
| + | |
| − | <br />
| + | |
| − | From the above messages we could get the channel number 25 for the "OBEX Object Push" service. We input this number to the "ussp-push" by running the following command:
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | ussp-push 38:BC:1A:B1:7E:DD@25 example.jpg example.jpg
| + | |
| − | </syntaxhighlight>
| + | |
| − | Note: you need to use your device's name, its MAC address and channel number when you run these commands.<br /><br />
| + | |
| − | Usually after the above commands are run a popup window will show on the phone that communicates with T2 and you can start file transfers.<br />
| + | |
| − | <br />
| + | |
| − | Common Issues:<br />
| + | |
| − | 1) If T2 cannot find a Bluetooth device you can try this command to restart its Bluetooth:<br />
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | rfkill unblock 0
| + | |
| − | </syntaxhighlight>
| + | |
| − | 2) If any of these commands is not installed you can try this command to install it:<br />
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | apt-get install bluetooth bluez obexftp openobex-apps python-gobject ussp-push
| + | |
| − | </syntaxhighlight>
| + | |
| − | | + | |
| − | ===Install Debian Packages===
| + | |
| − | We provide a Debian Jessie image. You can install Jessie's packages by commanding "apt-get". If this is your first installation you need to update the package list by running the following command
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | apt-get update
| + | |
| − | </syntaxhighlight>
| + | |
| − | You can install your preferred packages. For example if you want to install an FTP server you can do this：
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | apt-get install vsftpd
| + | |
| − | </syntaxhighlight>
| + | |
| − | Note: you can change your download server by editting "/etc/apt/sources.list". You can get a complete server list from [http://www.debian.org/mirror/list]. You need to select the one with "armhf".
| + | |
| − | | + | |
| − | ===Audio Output from HDMI or 3.5mm Jack under Debian===
| + | |
| − | Our default Debian image for the NanoPC-T3 doesn't support audio output. If you want to enable this function you need to install the alsa package.
| + | |
| − | * Make sure your Debian OS is our latest version and your board has access to the internet;
| + | |
| − | * Power up your board and run the following commands on your board's commandline utility to install the alsa package:
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | apt-get update
| + | |
| − | apt-get install libasound2
| + | |
| − | apt-get install alsa-base
| + | |
| − | apt-get install alsa-utils
| + | |
| − | </syntaxhighlight>
| + | |
| − | * After the installation is done copy a ".wav" audio file to your NanoPC-T3, connect your T3 to a earphone or speaker and try playing this audio file(By default Debian's audio output is from the 3.5mm audio jack):
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | aplay music.wav
| + | |
| − | </syntaxhighlight>
| + | |
| − | * By default Debian's audio output is from the 3.5mm audio jack. If you want audio output from the HDMI you need to change the setting by editing the "/etc/asound.conf" file:
| + | |
| − | <syntaxhighlight lang="bash">
| + | |
| − | pcm.!default {
| + | |
| − | type hw
| + | |
| − | card 1
| + | |
| − | device 0}
| + | |
| − |
| + | |
| − | ctl.!default {
| + | |
| − | type hw
| + | |
| − | card 1}
| + | |
| − | </syntaxhighlight>
| + | |
| − | card 0 stands for the 3.5mm audio jack and card 1 stands for the HDMI audio. After you make your change reboot your board to make it effective.
| + | |
| − | | + | |
| − | ==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>
| + | |
| − | | + | |
| − | ====User 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 14.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:[https://www.mediafire.com/folder/gg764iwvfm0mf/S5P6818]
| + | |
| − | * Source Code:[https://github.com/friendlyarm]
| + | |
| − | | + | |
| − | ==Resources==
| + | |
| − | ===User's Manual, Datasheet & Schematics===
| + | |
| − | *SOC Datasheet: [http://wiki.friendlyarm.com/wiki/images/8/8b/SEC_S5P6818X_Users_Manual_preliminary_Ver_0.00.pdf S5P6818 Datasheet]
| + | |
| − | * AXP228_Users_Manual [http://wiki.friendlyarm.com/wiki/index.php/File:116.AXP228_V1.1_20130106.pdf AXP228_V1.1_20130106]
| + | |
| − | * eMMC [http://wiki.friendlyarm.com/wiki/index.php/File:KLMxGxxEMx-B031(eMMC5.0_1xnm_based_e_MMC)1.0.pdf eMMC5.0_1xnm_based_e_MMC]
| + | |
| − | *Schematic: [http://wiki.friendlyarm.com/wiki/images/d/d5/NanoPC-T2-T3-1603-Schematic.pdf NanoPC-T3 Schematic]
| + | |
| − | *PCB Dimension: [http://wiki.friendlyarm.com/wiki/images/2/24/NanoPC-T2-T3-1603-Dimensions%28dxf%29.zip NanoPC-T3-Dimensions(dxf)]
| + | |
| − | | + | |
| − | ==Update Log==
| + | |
| − | ===April-28-2016===
| + | |
| − | * Released English version
| + | |
| − | | + | |
| − | ===June-30-2016===
| + | |
| − | * Added sections 5.2.4 and 8
| + | |
| − | | + | |
| − | ===Sep-27-2016===
| + | |
| − | * Added section 9
| + | |
| − | * Updated sections 5.2.2 and 8.2
| + | |
| − | | + | |
| − | ===Nov-2-2016===
| + | |
| − | * Updated sections 6.4 and 11
| + | |
| − | | + | |
| − | ===June-20-2017===
| + | |
| − | * 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
| + | |
