View source for NanoPi K1 Plus

[[NanoPi K1 Plus/zh|查看中文]]

==Introduction==
[[File:NanoPi_K1_Plus1.jpg|thumb|300px]]
[[File:NanoPi_K1_Plus2.jpg|thumb|300px]]
[[File:NanoPi_K1_Plus3.jpg|thumb|300px]]
* The NanoPi K1 Plus uses the Allwinner 64-bit quad-core Cortex™-A53 H5 SoC. It can run either a 64-bit OS or a 32-bit OS. It has NEON multi-media engine and a hex-core Mali450 GPU. It supports various video formats and has strong HD encoding/decoding capabilities.
* The NanoPi K1 Plus has 2GB DDR3 RAM, onboard WiFi, DVP camera interface, Gbps Ethernet, USB, HDMI, infrared remote control, 3.5mm audio jack, I2S and etc. It can boot from a TF card and supports an external eMMC module.
* The NanoPi K1 Plus has the same dimension as RPi 3. Its 40-Pin GPIO pin-header is compatible with RPi 3's GPIO pin-header. It works with any RPi housing.
* A Ubuntu Core image and an Armbian image are ready for the NanoPi K1 Plus.

==Hardware Spec==
* CPU: Allwinner H5, Quad-core 64-bit high-performance Cortex™-A53
* GPU: Hexa-core Mali450 
* DDR3 RAM: 2GB
* Ethernet: 10/100/1000M Ethernet using RTL8211E IC
* Wireless: 802.11 b/g/n and onboard PCB antenna
* Infrared: Onboard infrared receiver
* Audio: 3.5mm audio jack/Via HDMI
* Mic: onboard microphone
* eMMC: onboard eMMC interface
* I2S: onboard I2S interface(7Pin, 2.54mm pin-header)
* MicroSD Slot: MicroSD card slot
* USB Host: 3 x USB 2.0 Host, type A port
* DVP Camera interface: 24-Pin, 0.5mm pitch FPC seat
* MicroUSB: 1 x USB 2.0, OTG, for power input and data transmission
* HDMI: HDMI Type-A port. It supports 4K@30fps dsplay
* Video Output: HDMI 1.4. It supports 4K@30fps display, CVBS
* GPIO Pin-header: 40 Pin,2.54mm pitch pin-header containing I2C, GPIO, UART, PWM, SPDIF, SPI and etc
* Serial Debug Port: 4Pin, 2.5mm pitch pin-header
* Button: 1 x GPIO button(user configurable)
* LED: 1 x power LED and 1 x status LED
* Power Interface: MicroUSB
* PCB Size:56 x 85mm, 6-layer, ENIG
* Power: DC 5V/2A

==Diagram, Layout and Dimension==
===Layout===
[[File:NanoPi-K1-Plus-001.png |thumb|500px|NanoPi-K1-Plus Interface Layout]]

* '''GPIO Pin Spec'''
::{| class="wikitable"
|-
|Pin# || Name || Linux gpio ||Pin#  || Name || Linux gpio       
|-
|1    || SYS_3.3V   ||     ||2     || VDD_5V ||
|-
|3    || I2C0_SDA / GPIOA12   ||     ||4     || VDD_5V ||
|- 
|5    || I2C0_SCL / GPIOA11  ||     ||6     || GND    ||
|-
|7    || GPIOG11    || 203 ||8     || UART1_TX / GPIOG6 || 198
|-
|9    || GND        ||     ||10    || UART1_RX / GPIOG7 || 199  
|-
|11   || UART2_TX / GPIOA0  || 0      ||12    || GPIOA6 || 6
|-
|13   || UART2_RTS / GPIOA2 || 2      ||14    || GND || 
|-
|15   || UART2_CTS / GPIOA3 || 3      ||16    || UART1_RTS / GPIOG8 || 200
|-
|17   || SYS_3.3V         ||        ||18    || UART1_CTS / GPIOG9 || 201
|-
|19   || SPI0_MOSI / GPIOC0 || 64     ||20    || GND              ||
|-
|21   || SPI0_MISO / GPIOC1 || 65     ||22    || UART2_RX / GPIOA1  || 1
|-
|23   || SPI0_CLK / GPIOC2 || 66     ||24    || SPI0_CS / GPIOC3   || 67
|-
|25   || GND              ||        ||26    || SPDIF-OUT / GPIOA17 || 17
|-
|27   || I2C1_SDA / GPIOA19 / PCM0_CLK / I2S0_BCK || 19     ||28    || I2C1_SCL / GPIOA18 / PCM0_SYNC / I2S0_LRCK || 18
|-
|29   || GPIOA20 / PCM0_DOUT / I2S0_SDOUT          || 20     ||30     || GND             ||
|-
|31   || GPIOA21 / PCM0_DIN/ I2S0_SDIN         || 21     ||32     || GPIOA7          || 7
|-
|33   || GPIOA8           || 8      ||34     || GND             ||
|-
|35   || UART3_CTS / SPI1_MISO / GPIOA16    || 16   ||36     || UART3_TX / SPI1_CS / GPIOA13    || 13
|-
|37   || GPIOA9           || 9      ||38     || UART3_RTS / SPI1_MOSI / GPIOA15 || 15
|-
|39   || GND              ||        ||40     || UART3_RX / SPI1_CLK / GPIOA14   || 14
|}


* '''eMMC Connector Pin Spec'''
::{| class="wikitable"
|-
|Pin# || Name          ||Pin#  || Name     
|-
|1    || eMMC_D0 ||2     || eMMC_D1
|-
|3    || eMMC_D2     ||4     || eMMC_D3
|- 
|5    || eMMC_D4      ||6     || eMMC_D5
|-
|7    || eMMC_D6       ||8     || eMMC_D7
|-
|9    || eMMC_DS          ||10    || GND
|-
|11   || eMMC_CMD       ||12    || eMMC_CLK
|-
|13   || NC      ||14    || GND
|-
|15   || NC       ||16    || 1.8V OUT
|-
|17   || eMMC_RST ||18    || 3.3V OUT
|-
|19   || GPIOY_5    ||20    || GND
|}

* '''Debug Port（UART0）'''
::{| class="wikitable"
|-
|Pin# || Name       
|-
|1    || GND    
|-
|2    || VDD_5V    
|- 
|3    || UART_TX   
|-
|4    || UART_RX
|}
* '''7Pin I2S Pin Spec'''
::{| class="wikitable"
|-
|Pin# || Name       
|-
|1    || GND    
|-
|2    || SYS_3.3V     
|- 
|3    || I2S0_BCK
|-
|4    || I2S0_LRCK
|-    
|5    || I2S0_SDOUT
|-
|6    || I2S0_SDIN
|-
|7    || I2S_MCLK
|}

:'''Notes'''
::#SYS_3.3V: 3.3V power output
::#VDD_5V: 5V power input/output. Input power range: 4.7～5.5V
::#All signal pins are 3.3V
::#For more details refer to :[http://wiki.friendlyelec.com/wiki/images/f/f3/Schematic_NanoPi-K1_Plus-1712_20171214.pdf Schematic_NanoPi-K1_Plus-1712_20171214.pdf]

===Board Dimension===
[[File:NanoPi_K1_Plus_V1.0_1712-Dim.png|frameless|600px|NanoPi_K1_Plus_V1.0_1712 Dimensions]]

::For more details refer to:[http://wiki.friendlyelec.com/wiki/index.php/File:Dimensions_NanoPi_K1_Plus-V1.0-1712_pcb(dxf).rar NanoPi_K1_Plus_V1.0_1712_dxf.zip]

==Software Features==
{{H5SoftwareFeature-FriendlyCore|NanoPi-K1-Plus}}
{{H5SoftwareFeature-FriendlyWrt|NanoPi-K1-Plus}}
{{H5SoftwareFeature-eFlasher|NanoPi-K1-Plus}}
{{H5SoftwareFeature-Android7|NanoPi-K1-Plus}}

==Get Started==
===Essentials You Need===
Before starting to use your NanoPi K1 Plus get the following items ready
* NanoPi K1 Plus
* MicroSD/TF Card: Class 10 or Above, minimum 8GB SDHC
* A DC 5V/2A power cord with MicroUSB port is a must
* HDMI monitor
* USB keyboard, mouse and possible a USB hub(or a TTL to serial board)
* A host computer running Ubuntu 18.04 64 bit system

{{TFCardsWeTested}}

===Install OS===
====Download Image Files====
Get the following files from here [http://download.friendlyelec.com/nanopik1plus download link] to download image files(under the "official-ROMs" directory) and the flashing utility(under the "tools" directory):<br />
::{| class="wikitable"
|-
|colspan=2|Image Files:
|-
|nanopi-k1-plus_sd_friendlycore-xenial_4.14_arm64_YYYYMMDD.img.zip || FriendlyCore(based on UbuntuCore), kernel:Linux-4.14                   
|-
|nanopi-k1-plus_eflasher_friendlycore-xenial_4.14_arm64_YYYYMMDD.img.zip  || eflasher image, for flashing FriendlyCore(Linux-4.14) to eMMC
|-
|nanopi-k1-plus_sd_android7.0_YYYYMMDD.img.zip  || Android7.0 image file, Linux-3.10 kernel
|-
|colspan=2|Flash Utility:  
|-
|win32diskimager.rar || Windows utility. Under Linux users can use "dd"
|- 
|}

{{BurnOS-Allwinner|NanoPi-K1-Plus}}

{{FriendlyCoreGeneral|NanoPi-K1-Plus}}
{{FriendlyCoreAllwinnerH5|NanoPi-K1-Plus}}

===Play & Record Audio===
You can play and record audio by running the following commands<br>
Check audio devices:
<syntaxhighlight lang="bash">
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
</syntaxhighlight>
Both Allwinner H5 and H3 have an internal codec which is recognized as [H3 Audio Codec]. You need to use the actual device name that your [H3 Audio Codec] device is recognized as in your system.<br>

Play Audio:
<syntaxhighlight lang="bash">
$ aplay /root/Music/test.wav -D plughw:0
</syntaxhighlight>
Parameter "-D plughw:0" means the "card 0" device is used to play the audio file. You need to choose a device from the list obtained by running "aplay -l".<br>
Record Audio:
<syntaxhighlight lang="bash">
$ arecord -f cd -d 5 test.wav
</syntaxhighlight>

==Compile FriendlyCore Source Code==
===Use Linux-4.14 BSP===
K1 Plus only works with 64-bit Linux-4.14 kernel and 64-bit Ubuntu Core 16.04. For more details on how to use a mainline U-boot and Linux-4.14 refer to:[[Building U-boot and Linux for H5/H3/H2+]] <br>

==Work with Android==
===Start Android For the First Time===
Before proceed make sure you either have Android installed on your board's eMMC or have a bootable TF card with Android image. Connect your board to an HDMI monitor and a USB mouse, and connect a 5V/2A power adapter to your board at its MicroUSB port. Power on the board and wait for Android to load. It takes relatively long time for Android to load for the first time.

===Connect to IR Control(RC-100)===
After Android is loaded you can interact with it with an IR remote control(Model:RC-100).<br>
Here is a table of function keys on the RC-100's panel:<br>
::{| class="wikitable"
|-
|Key||Function       
|-
|POWER  || Power
|-
|F1  ||  Search     
|- 
|F2  ||  PrintScreen
|-
|F3  ||  Enable/Disable Mouse
|-
|UP  ||  Move Up
|-
|DOWN  ||  Move Down
|-
|LEFT  ||  Move Left
|-
|RIGHT  ||  Move Right
|-
|OK  ||  Confirm
|-
|Volume-  ||  Turn Down Volume
|-
|Volume Mute  || Mute
|-
|Volume+  ||  Turn Up Volume
|-
|SETTING  || Enter Setting
|-
|HOME  ||  Return to Home Page
|-
|BACK  ||  Back to the Previous Page
|}
When Android is loaded for the first time you need to click on the buttons shown on the screen to proceed. You can press F3 to enable mouse and proceed. After Android is fully loaded you can turn off the HDMI monitor by short-pressing the power button and turn on the HDMI monitor by short-pressing the power button again. And you can power off the board by long-pressing the power button and power on the board by pressing the power button again.

===Set HDMI Resolution===
The default resolution for an HDMI monitor in Android for H5 is 720P/50Hz. You can change the resolution by following the steps below:
Go to "Settings":<br>
[[File:h5_setting.png|frameless|600px|]] <br>
Go to "Settings->Display":<br>
[[File:h5_setting_display.png|frameless|600px|]] <br>
Go to "Settings->Display->HDMI output mode": <br>
[[File:h5_setting_display_hdmires.png|frameless|600px|]] <br>
Select your wanted resolution.<br>

FriendlyELEC's Android for H5 automatically adjusts screen display for an HDMI monitor such that the output will adapt its screen size for HDMI monitors with different sizes. Here are the steps to follow:<br>
Go to "Settings":<br>
[[File:h5_setting.png|frameless|600px|]] <br>
Go to "Settings->Display":<br>
[[File:h5_setting_display_output.png|frameless|600px|]] <br>
Go to "Settings->Display->Display output mode": <br>
[[File:h5_setting_display_screen_percent.png|frameless|600px|]] <br>
You can adjust the screen size by moving the scroll bar.<br>

===Audio Output from HDMI and 3.5mm Audio Jack===
FriendlyELEC's Android by default sets audio output to both HDMI and 3.5mm audio jack. You can test this function by running Android's internal Music app.

===Play Video===
The H5's datasheet lists multiple video formats the H5 can support. FriendlyELEC used the antutu-benmarck utility to test H5's video playing and here are the formats that we tested and worked:<br>
[[File:h5_vpu_decode1.png|frameless|600px|]] <br>
[[File:h5_vpu_decode2.png|frameless|600px|]] <br>
[[File:h5_vpu_decode3.png|frameless|600px|]] <br>

If you want to play a 4K video visit this link [http://download.friendlyelec.com/nanopim1plus download link], go to the "test-video" directory, download the "4K-Chimei-inn-60mbps.mp4" file and copy it to an external storage device.<br>
Connect the external storage device to your board, boot Android, and you can play it with the Gallery utility.

===Connect to CAM500B Camera===
The CAM500B is a 500M camera module with a DVP interface. For more details refer to [[Matrix - CAM500B/zh|Matirx-CAM500B]].<br>
The CAM500B module doesn't support hot-plug therefore you need to connect it to your board before power on your board. For more details refer to [[Matrix - CAM500B/zh|Matirx-CAM500B]].<br>
After Android is booted you can test the camera module with Android's internal camera application. You can switch between picture taking and video recording by sliding your hand from the left edge of the screen to the right edge and you will see the following window:<br>
[[File:h5_camera_setting.png|frameless|600px|]] <br>
You can also change your settings on this window. For instance you can change image resolution by clicking on the "settings" icon:<br>
[[File:h5_camera_res.png|frameless|600px|]] <br>
For now the resolution for picture taking is only 1920 x 1080 (2.1 Mpx) and the resolutions for video recording are SD 480p/HD 720p/ HD 1080p.

==Compile Android Source Code==
===Preparations===
* You need a host PC running a 64bit Linux(FriendlyELEC used a Ubuntu-14.04 LTS-64bit system) and install the following packages on the system:
<syntaxhighlight lang="bash">
$ 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
</syntaxhighlight>

* Clone the lichee source code:
<syntaxhighlight lang="bash">
$ git clone https://gitlab.com/friendlyelec/h5_lichee.git lichee -b master-android7.0 
</syntaxhighlight>
Note: lichee is an Allwinner project for its CPUs. This project package contains U-boot's source code, Linux source code and various installation scripts. Generating an Android image relies on this "lichee" directory and its name cannot be changed.<br>
"-b master-android7.0" means the "master-android7.0" branch will be used. Generating an Android image from Android 7.0's source code relies on this branch.

* Clone Android Source Code:
<syntaxhighlight lang="bash">
$ git clone https://gitlab.com/friendlyelec/h5_android-7.0 android
</syntaxhighlight>
Since generating an Android image relies on the utilities in the lichee source code. You need to clone Android's source code under the directory where the lichee directory is located and keep the directory's name as "android":
<syntaxhighlight lang="bash">
$ ls ./
android lichee
</syntaxhighlight>

* Download Cross Compiler:
To compile the lichee source code you need to go to [http://download.friendlyelec.com/nanopineo2 download link] and go to the "toolchain" directory and download the cross compiler "gcc-linaro-arm-4.6.3.tar.xz" and "gcc-linaro-aarch64.tar.xz".<br>
"gcc-linaro-arm-4.6.3.tar.xz" is used to compile U-boot and "gcc-linaro-aarch64.tar.xz" is used to compile a Linux kernel. After download is done copy them to the "lichee/brandy/toochain/" directory.<br>
When compiling U-boot and Linux kernel these two cross compilers will be called.

===Introduction to lichee/fa_tools Scripts===
The scripts under the lichee/fa_tools directory are developed by FriendlyElec engineers for simplifying compilation and installation of the lichee project. Here are some tips.<br>

* build.sh is used to compile the whole lichee directory and U-boot/Linux kernel, generate an image file and clean the lichee directory after compilation is done. Here is its usage: <br>
<syntaxhighlight lang="bash">
$ ./build.sh 
Usage: build.sh -b board[nanopi-k1-plus] -p platform[android] -t target[all|u-boot|kernel|pack|clean]
</syntaxhighlight>
::{| class="wikitable"
|-
|option||comment       
|-
|b  || board model
|-
|p  || OS, now only Android is supported
|-
|t  || source code this compilation will work on, for Android:
* "all" means the whole lichee;<br>
* "u-boot" means only the U-boot;<br>
* "kernel" means only the Linux kernel;<br>
* "pack" means generating an image file. This option actually runs the "pack" command on the Android source code. The precondition to run "pack" successfully is to compile "lichee" and the Android source code successfully.<br>
* "clean" means clearing the lichee directory, temporary files and the U-boot\Linux kernel file.<br>
|}

* fuse.sh is used to flash a TF card or fastboot: <br>
<syntaxhighlight lang="bash">
$ ./fuse.sh
Usage: fuse.sh -d device[/dev/sd|fastboot] -p platform[android] -t target[u-boot|env.fex|boot.fex|system.fex]
</syntaxhighlight>
::{| class="wikitable"
|-
|Option||Comment       
|-
|d  || a device to which an image file will be installed, it can be either a TF card or "fastboot"
|-
|p  || for now it can only be Android
|-
|t  || the target this operation will work on, for Android:
* "u-boot" means to install U-boot;<br>
* "env.fex" means boot arguments, "lichee/tools/pack/out/env.fex" is converted from "lichee/tools/pack/chips/sun50iw2p1/configs/default/env.cfg";<br>
* "boot.fex" means to install boot.img, "lichee/tools/pack/out/boot.fex" points to "android/out/target/product/cheetah-p1/boot.img";<br>
* "system.fex" means to install system.img, "lichee/tools/pack/out/system.fex" points to "android/out/target/product/cheetah-p1/system.img";<br>
|}

* format_sd.sh is used to format a TF card: <br>
<syntaxhighlight lang="bash">
$ ./format_sd.sh /dev/sdX
</syntaxhighlight>
Note: you need to replace "/dev/sdX" with the device name your TF card is recognized as.<br>
To avoid flashing to a PC's hard disk a device with storage more than 32G will not be allowed to be a target device.

===Compile Android===
* Compile lichee source code, U-boot and Linux Kernel:<br>
<syntaxhighlight lang="bash">
$ cd lichee/fa_tools/
$ ./build.sh -b nanopi-k1-plus -p android -t all
</syntaxhighlight>

* Select openJDK-8.0:<br>
<syntaxhighlight lang="bash">
$ update-alternatives --config java
$ update-alternatives --config javac
</syntaxhighlight>
Compiling Android7.0 relies on openJDK-8.0。

* Compile Android source code and generate an Android image file:<br>
<syntaxhighlight lang="bash">
$ cd android
$ ./build.sh
</syntaxhighlight>
After compilation is done an Android image "sun50iw2p1_android_cheetah-p1_uart0.img" will be generated under the "lichee/tools/pack/" directory.

==Make Your Own Android System==
===Tech Documents Provided by Allwinner===
lichee/doc/allwinner-h5-doc.zip contains development documents provided by Allwinner. If you want to make your own Android system these are must-read reference materials:<br>
*《H5 SDK Quick Start Guide V1.0.pdf》
*《H5 Android定制化文档V1.0.pdf》
*《H5 Lichee使用说明书V1.0.pdf》
*《H5 sys_config.fex使用配置说明V1.0.pdf》

===Compile and Update U-boot===
Note: you need to compile the lichee directory successfully before you compile U-boot.
If you want to compile only U-boot you can run the following commands:
<syntaxhighlight lang="bash">
$ cd lichee/fa_tools/
$ ./build.sh -b nanopi-k1-plus -p android -t u-boot
</syntaxhighlight>
This will compile the "brandy/u-boot-2014.07" source code and call the "pack" command(to pack a kernel's dtb file, sys_config.fex and u-boot) and generate a "boot0_sdcard.fex" and a "boot_package.fex" under the "tools/pack/out/" directory.<br>
You can flash "boot0_sdcard.fex" and "boot_package.fex" to a TF card by running the following commands:
<syntaxhighlight lang="bash">
$ cd lichee/fa_tools/
$ ./fuse.sh -d /dev/sdX -p android -t u-boot
</syntaxhighlight>
You need to replace "/dev/sdX" with the device name your TF card is recognized as.<br>
These operations will update the dtb and sys_config.fex files on your TF card.

===Compile and Update Linux Kernel===
Note:you need to compile the lichee directory successfully before you can compile a Linux kernel.
If you want to compile only a Linux kernel you can run the following commands:
<syntaxhighlight lang="bash">
$ cd lichee/fa_tools/
$ ./build.sh -b nanopi-k1-plus -p android -t kernel
</syntaxhighlight>
After compilation is done a bImage and drivers will be generated under the "linux-3.10/output" directory. When compiling an Android source code the build.sh script will run the "extract-bsp" command to get the bImage and drivers from the "output" directory.<br>
If you want to update the Linux kernel on your TF card you need to generate a new boot.img. You can run the following commands:
<syntaxhighlight lang="bash">
$ cd android
$ build.sh bootimage
</syntaxhighlight>
After compilation is done a "lichee/tools/pack/out/boot.fex" file will be generated and it points to "android/out/target/product/cheetah-p1/boot.img". You can flash the boot.fex file by running the following commands:
<syntaxhighlight lang="bash">
$ cd lichee/fa_tools
$ ./fuse.sh -d /dev/sdX -p android -t boot.fex
</syntaxhighlight>
You need to replace /dev/sdX the with device name your TF card is recognized as.<br>

===Flash with Fastboot===
If you have successfully booted U-boot on your board you can flash Android components with USB:<br>
(1) Connect a MicroUSB cable to your board and a host PC;<br>
(2) Power on your board, press any key to enter the U-boot mode in a serial port; <br>
(3) Run "fastboot"; <br>
(4) Run the following commands to update the Android components on your board:<br>
<syntaxhighlight lang="bash">
$ cd lichee/fa_tools/
$ ./fuse.sh -d fastboot -p android -t u-boot
$ ./fuse.sh -d fastboot -p android -t env.fex
$ ./fuse.sh -d fastboot -p android -t boot.fex
$ ./fuse.sh -d fastboot -p android -t system.fex
</syntaxhighlight>

{{MoreOS}}
{{H5-KernelHeaderFile}}
==Work with External Modules==
===Matrix - 2'8 SPI Key TFT LCD Module===
The Matrix-2'8_SPI_Key_TFT LCD module is a 2.8' TFT LCD module with resistive touch. It uses the ST7789S IC and XPT2046 resistive touch IC. The LCD's resolution is 240 * 320. Its interface is SPI. The module has three independent buttons which are user-configurable. For more details refer to:[[Matrix - 2'8 SPI Key TFT]]<br />
[[File:Matrix-2'8_SPI_Key_TFT-1706.jpg|frameless|300px|File:Matrix-2'8_SPI_Key_TFT-1706]]

==3D Printed Housing==

==Resources==
===Datasheet and Schematics===
* Schematic: [http://wiki.friendlyelec.com/wiki/images/f/f3/Schematic_NanoPi-K1_Plus-1712_20171214.pdf Schematic_NanoPi-K1_Plus-1712_20171214.pdf]
* Dimensions: [http://wiki.friendlyelec.com/wiki/index.php/File:Dimensions_NanoPi_K1_Plus-V1.0-1712_pcb(dxf).rar Dimensions_NanoPi_K1_Plus-V1.0-1712_pcb(dxf).rar]
* H5 Datasheet: [http://wiki.friendlyelec.com/wiki/images/d/de/Allwinner_H5_Datasheet_V1.0.pdf Allwinner_H5_Datasheet_V1.0.pdf]

* unofficial ROM
** [http://www.dietpi.com/ DietPi]
** [https://www.armbian.com/download/?tx_maker=friendlyelec armbian]

* article
** [https://www.cnx-software.com/2018/04/24/nanopi-k1-plus-is-a-35-allwinner-h5-development-board-using-raspberry-pi-form-factor/]
{{H5ChangeLog}}

==Update Log==
===April-19-2018===
* Released English Version

===August-12-2018===
* Added sections 8, 9 and 10