View source for Orange Pi Plus 2E

__TOC__
== '''Orange Pi Introduction''' ==
<br>
=== '''What is Orange Pi Plus 2E?''' ===
<br>
　It’s an open-source single-board computer. It can run Android 4.4, Ubuntu, Debian, Rasberry Pi Image, it uses the AllWinner H3SoC, and has 2GB DDR3 SDRAM.<br>
<br>
=== '''What can I do with Orange Pi Plus 2E?''' ===
<br>
You can use it to build...<br>
<br>
* A computer
* A wireless server
* Games
* Music and sounds
* HD video
* A speaker
* Android
* Scratch
* ......
* Pretty much anything else, because Orange Pi Plus 2E is open source
<br>
=== '''Whom is it for?''' ===
<br>
Orange Pi Plus 2E is for anyone who wants to create with technology– not just consuming. It's a simple, fun, useful tool and you can use it to take control of the world around you.<br>
<br>
=== '''Hardware specification of Orange Pi Plus 2E''' ===
<br>
{| class="wikitable" style="width:800px;background:#ffffff;"
|-
| colspan=2 | <div>Hardware specification</div>
|-
| CPU|| H3 Quad-core Cortex-A7 H.265/HEVC 4K
|-
| GPU|| 
* Mali400MP2 GPU @600MHz
* Supports OpenGL ES 2.0
|-
| Memory (SDRAM) || 2GB DDR3 (shared with GPU)
|-
| On-board Storage|| 
TF card (Max. 64GB) /?MMC card slot <br>
16GB EMMC Flash
|-
| On-board Network|| 10/100/1000M Ethernet RJ45
|-
| Onboard WIFI|| Realtek RTL8189ETV, IEEE 802.11 b/g/n
|-
| Video Input|| 
A CSI input connector Camera:<br>
Supports 8-bit YUV422 CMOS sensor interface <br>
Supports CCIR656 protocol for NTSC and PAL <br>
Supports SM pixel camera sensor<br>
Supports video capture solution up to 1080p@30fps
|-
| Audio Input|| MIC
|-
| Video Outputs|| 
Supports HDMI output with HDCP <br>
Supports HDMI CEC<br>
Supports HDMI 30 function <br>
Integrated CVBS<br>
Supports simultaneous output of HDMI and CVBS
|-
| Audio Output|| 3.5 mm Jack and HDMI
|-
| Power Source|| DC input, USB OTG input don't supply power
|-
| USB 2.0 Ports|| Three USB 2.0 HOST, one USB 2.0 OTG
|-
| Buttons || 
Power button: Next to Reset button<br>
UBoot button (optional): Behind HDMI connector
|-
| Low-level peripherals|| 40 Pins Header,compatible with Raspberry Pi B+
|-
| GPIO(1x3) pin|| UART, ground.
|-
| LED|| Power led & Status led
|-
| Key|| IR input,UBOOT,POWER
|-
| Supported OS|| Android Lubuntu, Debian, Raspberry Pi Image
|-
| colspan=2 | Interface definition
|-
| Product size|| 108mm × 67mm
|-
| Weight|| 85g
|-
| colspan=2 | Orange Pi™ is a trademark of the Shenzhen Xunlong Software CO., Limited
|}
<br>
'''Interface instructions'''
<div>[[File:Orange-pi-plus-2e-img1.png|800px]]</div>
<br>

=== '''GPIO Specifications''' ===
<br>
A 40-pin GPIO interface on the Orange Pi Plus 2E is the same as Model A and Model B of Raspberry Pi. The picture below is GPIO pin define of Orange Pi Plus 2E.
<div>[[File:Orange-pi-pc2-img5.png|800px]]</div>
<br>
    <table style=" min-width: 800px;text-align: center;" border="1" bordercolor="#d8d8d8" cellspacing="0"
        cellpadding="0">
       <tr>
           <td>OrangePi(H3)</td>
           <td></td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #5a5a5a;">CON3-P01</td>
           <td style="background-color: #5a5a5a;">VCC-3V3</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #5a5a5a;">CON3-P02</td>
           <td style="background-color: #5a5a5a;">VCC-5V</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #b1a0c6;">CON3-P03</td>
           <td style="background-color: #b1a0c6;">TWI0-SDA</td>
           <td style="background-color: #b1a0c6;">PA12</td>
       </tr>
       <tr>
           <td style="background-color: #5a5a5a;">CON3-P04</td>
           <td style="background-color: #5a5a5a;">VCC-5V</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #b1a0c6;">CON3-P05</td>
           <td style="background-color: #b1a0c6;">TWI0-SCK</td>
           <td style="background-color: #b1a0c6;">PA11</td>
       </tr>
       <tr>
           <td style="background-color: #5a5a5a;">CON3-P06</td>
           <td style="background-color: #5a5a5a;">GND</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #938a53;">CON3-P07</td>
           <td style="background-color: #938a53;">PWM1</td>
           <td style="background-color: #938a53;">PA6</td>
       </tr>
       <tr>
           <td style="background-color: #d99694;">CON3-P08</td>
           <td style="background-color: #d99694;">UART3_TX</td>
           <td style="background-color: #d99694;">PA13</td>
       </tr>
       <tr>
           <td style="background-color: #5a5a5a;">CON3-P09</td>
           <td style="background-color: #5a5a5a;">GND</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #d99694;">CON3-P10</td>
           <td style="background-color: #d99694;">UART3_RX</td>
           <td style="background-color: #d99694;">PA14</td>
       </tr>
       <tr>
           <td style="background-color: #c2d59a;">CON3-P11</td>
           <td style="background-color: #c2d59a;">UART2_RX</td>
           <td style="background-color: #c2d59a;">PA1</td>
       </tr>
       <tr>
           <td style="background-color: #938a53;">CON3-P12</td>
           <td style="background-color: #938a53;">PD14</td>
           <td style="background-color: #938a53;">PD14</td>
       </tr>
       <tr>
           <td style="background-color: #c2d59a;">CON3-P13</td>
           <td style="background-color: #c2d59a;">UART2_TX</td>
           <td style="background-color: #c2d59a;">PA2</td>
       </tr>
       <tr>
           <td style="background-color: #5a5a5a;">CON3-P14</td>
           <td style="background-color: #5a5a5a;">GND</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #c2d59a;">CON3-P15</td>
           <td style="background-color: #c2d59a;">UART2_CTS</td>
           <td style="background-color: #c2d59a;">PA3</td>
       </tr>
       <tr>
           <td style="background-color: #f9c090;">CON3-P16</td>
           <td style="background-color: #f9c090;">PC4</td>
           <td style="background-color: #f9c090;">PC4</td>
       </tr>
       <tr>
           <td style="background-color: #5a5a5a;">CON3-P17</td>
           <td style="background-color: #5a5a5a;">VCC-3V3</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #f9c090;">CON3-P18</td>
           <td style="background-color: #f9c090;">CAN_RX</td>
           <td style="background-color: #f9c090;">PC7</td>
       </tr>
       <tr>
           <td style="background-color: #92cddd;">CON3-P19</td>
           <td style="background-color: #92cddd;">SPI0_MOSI</td>
           <td style="background-color: #92cddd;">PC0</td>
       </tr>
       <tr>
           <td style="background-color: #5a5a5a;">CON3-P20</td>
           <td style="background-color: #5a5a5a;">GND</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #92cddd;">CON3-P21</td>
           <td style="background-color: #92cddd;">SPI0_MISO</td>
           <td style="background-color: #92cddd;">PC1</td>
       </tr>
       <tr>
           <td style="background-color: #c2d59a;">CON3-P22</td>
           <td style="background-color: #c2d59a;">UART2_RTS</td>
           <td style="background-color: #c2d59a;">PA2</td>
       </tr>
       <tr>
           <td style="background-color: #92cddd;">CON3-P23</td>
           <td style="background-color: #92cddd;">SPI0_CLK</td>
           <td style="background-color: #92cddd;">Plus 2E</td>
       </tr>
       <tr>
           <td style="background-color: #92cddd;">CON3-P24</td>
           <td style="background-color: #92cddd;">SPI0_CS0</td>
           <td style="background-color: #92cddd;">PC3</td>
       </tr>
       <tr>
           <td style="background-color: #5a5a5a;">CON3-P25</td>
           <td style="background-color: #5a5a5a;">GND</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #92cddd;">CON3-P26</td>
           <td style="background-color: #92cddd;">PA21</td>
           <td style="background-color: #92cddd;">PA21</td>
       </tr>
       <tr>
           <td style="background-color: #528ed4;">CON3-P27</td>
           <td style="background-color: #528ed4;">TWI1-SDA</td>
           <td style="background-color: #528ed4;">PA19</td>
       </tr>
       <tr>
           <td style="background-color: #938a53;">CON3-P28</td>
           <td style="background-color: #938a53;">TWI1-SCK</td>
           <td style="background-color: #938a53;">PA18</td>
       </tr>
       <tr>
           <td style="background-color: #528ed4;">CON3-P29</td>
           <td style="background-color: #528ed4;">PA7</td>
           <td style="background-color: #528ed4;">PA7</td>
       </tr>
       <tr>
           <td style="background-color: #5a5a5a;">CON3-P30</td>
           <td style="background-color: #5a5a5a;">GND</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #528ed4;">CON3-P31</td>
           <td style="background-color: #528ed4;">PA8</td>
           <td style="background-color: #528ed4;">PA8</td>
       </tr>
       <tr>
           <td style="background-color: #d99694;">CON3-P32</td>
           <td style="background-color: #d99694;">UART1_RTS</td>
           <td style="background-color: #d99694;">PG8</td>
       </tr>
       <tr>
           <td style="background-color: #528ed4;">CON3-P33</td>
           <td style="background-color: #528ed4;">PA9</td>
           <td style="background-color: #528ed4;">PA9</td>
       </tr>
       <tr>
           <td style="background-color: #5a5a5a;">CON3-P34</td>
           <td style="background-color: #5a5a5a;">GND</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #528ed4;">CON3-P35</td>
           <td style="background-color: #528ed4;">PA10</td>
           <td style="background-color: #528ed4;">PA10</td>
       </tr>
       <tr>
           <td style="background-color: #d99694;">CON3-P36</td>
           <td style="background-color: #d99694;">UART1_CTS</td>
           <td style="background-color: #d99694;">PG9</td>
       </tr>
       <tr>
           <td style="background-color: #938a53;">CON3-P37</td>
           <td style="background-color: #938a53;">PA20</td>
           <td style="background-color: #938a53;">PA20</td>
       </tr>
       <tr>
           <td style="background-color: #938a53;">CON3-P38</td>
           <td style="background-color: #938a53;">UART1_TX</td>
           <td style="background-color: #938a53;">PG6</td>
       </tr>
       <tr>
           <td style="background-color: #5a5a5a;">CON3-P39</td>
           <td style="background-color: #5a5a5a;">GND</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #938a53;">CON3-P40</td>
           <td style="background-color: #938a53;">UART1_RX</td>
           <td style="background-color: #938a53;">PG7</td>
       </tr>
    </table>
<br>

=== '''Specification of CSI Camera Connector''' ===
<br>
The CSI Camera Connector is a 24-pin FPC connector which can connect external camera module with proper signal pin mappings. The pin of CIS connector can be defined as follows. The connector marked with "CON 1" on the Orange Pi Plus 2E is camera connector.
<div>[[File:Orange-pi-pc2-img6.png|800px]]</div>
<br>
'''Orange Pi Plus 2E-CSI'''
<br>
 <table style=" min-width: 800px;text-align: center;" border="1" bordercolor="#d8d8d8" cellspacing="0"
        cellpadding="0">
       <tr>
           <td style="background-color: #808080;">CON1-P01</td>
           <td style="background-color: #808080;">NC</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #808080;">CON1-P02</td>
           <td style="background-color: #808080;">GND</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #33cccc;">CON1-P03</td>
           <td style="background-color: #33cccc;">TWI2-SDA</td>
           <td style="background-color: #33cccc;">PE13</td>
       </tr>
       <tr>
           <td style="background-color: #808080;">CON1-P04	</td>
           <td style="background-color: #808080;">VCC-CSI</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #33cccc;">CON1-P05	</td>
           <td style="background-color: #33cccc;">TWI2-SCK</td>
           <td style="background-color: #33cccc;">PE12</td>
       </tr>
       <tr>
           <td style="background-color: #33cccc;">CON1-P06	</td>
           <td style="background-color: #33cccc;">CSI-RESET#</td>
           <td style="background-color: #33cccc;">PE15</td>
       </tr>
       <tr>
           <td style="background-color: #ff9900;">CON1-P07	</td>
           <td style="background-color: #ff9900;">CSI-VSYNC</td>
           <td style="background-color: #ff9900;">PE3</td>
       </tr>
       <tr>
           <td style="background-color: #33cccc;">CON1-P08	</td>
           <td style="background-color: #33cccc;">CSI-STBY-EN</td>
           <td style="background-color: #33cccc;">PE15</td>
       </tr>
       <tr>
           <td style="background-color: #ff9900;">CON1-P09	</td>
           <td style="background-color: #ff9900;">CSI-HSYNC</td>
           <td style="background-color: #ff9900;">PE2</td>
       </tr>
       <tr>
           <td style="background-color: #808080;">CON1-P10	</td>
           <td style="background-color: #808080;">VDD1V8-CSI</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #808080;">CON1-P11	</td>
           <td style="background-color: #808080;">VCC-CSI</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #ff9900;">CON1-P12	</td>
           <td style="background-color: #ff9900;">CSI-D7</td>
           <td style="background-color: #ff9900;">PE11</td>
       </tr>
       <tr>
           <td style="background-color: #ff9900;">CON1-P13	</td>
           <td style="background-color: #ff9900;">CSI-MCLK</td>
           <td style="background-color: #ff9900;">PE1</td>
       </tr>
       <tr>
           <td style="background-color: #ff9900;">CON1-P14	</td>
           <td style="background-color: #ff9900;">CSI-D6</td>
           <td style="background-color: #ff9900;">PE10</td>
       </tr>
       <tr>
           <td style="background-color: #808080;">CON1-P15	</td>
           <td style="background-color: #808080;">GND</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #ff9900;">CON1-P16	</td>
           <td style="background-color: #ff9900;">CSI-D5</td>
           <td style="background-color: #ff9900;">PE9</td>
       </tr>
       <tr>
           <td style="background-color: #ff9900;">CON1-P17	</td>
           <td style="background-color: #ff9900;">CSI-PCLK</td>
           <td style="background-color: #ff9900;">PE0</td>
       </tr>
       <tr>
           <td style="background-color: #ff9900;">CON1-P18	</td>
           <td style="background-color: #ff9900;">CSI-D4</td>
           <td style="background-color: #ff9900;">PE8</td>
       </tr>
       <tr>
           <td style="background-color: #ff9900;">CON1-P19	</td>
           <td style="background-color: #ff9900;">CSI-D0</td>
           <td style="background-color: #ff9900;">PE4</td>
       </tr>
       <tr>
           <td style="background-color: #ff9900;">CON1-P20	</td>
           <td style="background-color: #ff9900;">CSI-D3</td>
           <td style="background-color: #ff9900;">PE7</td>
       </tr>
       <tr>
           <td style="background-color: #ff9900;">CON1-P21	</td>
           <td style="background-color: #ff9900;">CSI-D1</td>
           <td style="background-color: #ff9900;">PE5</td>
       </tr>
       <tr>
           <td style="background-color: #ff9900;">CON1-P22	</td>
           <td style="background-color: #ff9900;">CSI-D2</td>
           <td style="background-color: #ff9900;">PE6</td>
       </tr>
       <tr>
           <td style="background-color: #808080;">CON1-P23</td>
           <td style="background-color: #808080;">GND</td>
           <td></td>
       </tr>
       <tr>
           <td style="background-color: #808080;">CON1-P24</td>
           <td style="background-color: #808080;">AFVCC-CSI</td>
           <td></td>
       </tr>
    </table>
<br>

== '''Using Method Introduction''' ==
<br>
Follow these steps, you can configure and run your Orange Pi in a very short period of time. Boot your Orange Pi need to complete the following steps.<br>
<br>
=== '''Step 1: Prepare Accessories Needed''' ===
<br>
You need at least some accessories like the following if it is your first time to use the Orange Pi.<br>
<br>
{| class="wikitable" style="width:800px;background:#fff;"
|-
! No. !! Items !! Requirements and Instructions
|-
| 1|| TF card|| 8GB min.; class 10. Branded TF cards would be reference which are much more reliable.
|-
| 2|| HDMI to HDMI cable or HDMI to DVI cable|| HDMI to HDMI cable is used to connect HD TV or HD monitor
|-
| 3|| AV video cable|| A standard AV video cable can be used to connect stimulated monitor if a HDMI monitor is unavailable.
|-
| 4|| Keyboard and mouse|| Any keyboard and mouse with USB port is applicable; Keyboard and mouse are
high-power, so a USB concentrator is required.
|-
| 5|| Ethernet cable/USB WiFi(Optional)|| Network is optional, It makes more convenient to mount and upgrade software in your Orange
Pi PC.
|-
| 6|| DC power adapter|| 5V/2V min. high qualified power adapter, OTG can not used a power supply.
|-
| 7|| Audio cable (Optional)|| You can select an audio cable with 3.5mm jack to feel stereo audio.
|}
<br>
<div style="display:flex;  ">
<div style="text-align:center;">
[[File:Orange-pi-pc2-img7.png|200px200px|]]<br>
HDMI to HDMI cable
</div>
<div style="text-align:center;margin-left:100px;padding-top:3px;">
[[File:Orange-pi-pc2-img8.png|200px200px|]]<br>
HDMI to DVI cable
</div>
<div style="text-align:center;margin-left:100px;padding-top:1px;">
[[File:Orange-pi-pc2-img9.png|200px200px|]]<br>
AV video cable
</div>
</div>
<br>
<div style="display:flex; ;">
<div style="text-align:center;">
[[File:Orange-pi-pc2-img10.png|200px200px|]]<br>
TF card
</div>
<div style="text-align:center;margin-left:100px;padding-top:15px;">
[[File:Orange-pi-pc2-img11.png|200px200px|]]<br>
DC power adapter
</div>
</div>
<br>

=== '''Step 2:Prepare a TF Card or EMMC Image''' ===
<br>
In order to use Orange Pi normally, you must install the operating system into TF card first.<br>
<br>
'''1)Write Linux into TF Card Based on Windows Platform'''<br>
<br>
a.Inserting the TF card into the computer, the capacity of the card must be bigger than the operating system, usually requires 8GB or bigger.<br>
b.Formatting the TF card.<br>
<div style="padding-left:20px;">
i Download tools for formatting TF card, such as TF Formatter, it could be downloaded from:<br>
https://www.sdcard.org/downloads/formatter_4/eula_windows/<br>
<br>
ii Unzip the downloaded files, and run setup.exe<br>
<br>
iii In the options settings select the "format" button for quick formatting. "Format size adjustment" select "(ON)"<br>
<br>
<div style="padding-left:180px;">[[File:Orange-pi-pc2-img12.png|400px|]]</div>
<br>
<div style="padding-left:180px;">[[File:Orange-pi-pc2-img13.png|400px|]]</div>
<br>
iv Make sure the inserted TF card disk are in accordance with the chosen disk.<br>
<br>
v Click the "Format" button.
</div>
c.Download the operating system image file from the download page, the page address is as following:<br>
http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Plus-2-E.html<br>
d.Unzip the downloaded file (in addition to the Android system, this method can be used to burn to write, the Android system need another burn, the following will introduce)<br>
e.Right click to download the file, select "Unzip file" to write image to TF card
<div style="padding-left:20px;">
i Download tools to write image,such as Win32 Diskimager, here is the download page: <br>
http://sourceforge.net/projects/win32diskimager/files/Archive/<br>
<br>
ii Select the image file path that has been unzipped.<br>
<br>
<div style="padding-left:180px;">[[File:Orange-pi-pc2-img14.png|400px|]]</div>
<br>
iii Click "Write" button and wait for the image to write. <br>
<br>
iv After the image is written, click "Exit" button.
</div>
<br>
'''2)Write Linux into TF card based on Linux platform?'''
<br>
a.Inserting the TF card into the computer, the capacity of the card must be larger than the operating system image, usually requires 4GB or greater capacity.<br>
<br>
b.Formatting the TF card.<br>
<br>
i Run fdisk –l order to make sure TF disk.<br>
ii Run umount /dev/sdxx to uninstall all partitions of TF Card. <br>
iii Run sudo fdisk /dev/sdx order. Use o command to delete all
partitions of TF Card, and then us n order to add a new partition, finally use
w command to save and exit.<br>
iv Run sudo mkfs.vfat /dev/sdx1 command to format the TF card partition set up last step to FAT32 form(according to your TF card disk to replacex). Or you could skip this step since command in Linux will format TF card automatic.<br>
<br>
c.Download the OS image from download page <br>
http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Plus-2-E.html<br>
<br>
d.Unzip and right click the downloaded file, select " Unzip file"<br>
<br>
e.Write image to TF card<br>
<br>
i Run sudo fdisk –l order to make sure the TF card disk<br>
ii make sure the image file hash key is the same as download page mention(optional). It will output sha1sum [path]/[imagename], which should be same as the image paye "SHA-1"<br>
iii Run umount /dev/sdxx order to uninstall all partitions in TF Card<br>
iv Run sudo dd bs=4M if=[path]/[imagename] of=/dev/sdx to write down image file. Wait for the image to write. If it cannot work at 4M, then replace a 1M which takes more time. You can run sudo pkill –USR1 –n –x dd order to monitoring procedure.<br>
<br>
'''3)Use PhoenixCard tool to write Android image into TF card'''
<br>
It is impossible for Android image to be written into TF card by using
dd command under Linux or using Win32 Diskimager under Windows. Here
PhoenixCard tool is applicable for Android image writing.<br>
<br>
a.Download the Android OS image and PhoenixCard tool. Download PhoenixCard from here:<br>
https://drive.google.com/file/d/0B_VynIqhAcB7NTg2UkRDdHRWX2s/edit?usp=sharing<br>
Download Android OS image from here: <br>
http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Plus-2-E.html<br>
b.Format the TF card<br>
<div style=" ;">[[File:Orange-pi-pc2-img15.png|400px|]]</div>
<br>
c.Please make sure the inserted TF card is in accordance with the chosen TF card, click "restore" button for TF card formatting.<br>
<br>
<div style=" ;">[[File:Orange-pi-pc2-img16.png|600px|]]</div>
<br>
d.Click "OK" button after successfully formatted the TF card to normal.<br>
<br>
e.Burn the Android OS image into your TF card. Please pay attention to the following with red marks.<br>
<br>
<div style=" ;">[[File:Orange-pi-pc2-img17.png|600px|]]</div>
<br>
f.Click "Burn" button for writing to TF card and wait for it finish<br>
<br>
<div style=" ;">[[File:Orange-pi-pc2-img18.png|600px|]]</div>
<br>
g.Click "Exit" button after burn Android image to TF card successfully.<br>
<br>
'''4)Write Armbian Image into TF Card'''<br>
<br>
a.Insert TF card into computer, please note that the TF card capacity must bigger than the operating system image, usually need to be 8GB or bigger.<br>
b.Download the OS image file from the download page: http://www.armbian.com/download/<br>
c.Write the image into TF card.<br>
i. Download image writing tool such as Rufus, the download page: https://rufus.akeo.ie/
<br>
<br>
<div style=" ;">[[File:Orange-pi-pc2-img19.png|400px|]]</div>
<br>
ii. Select the image file path that has been unzipped<br>
<br>
<div style=" ;">[[File:Orange-pi-pc2-img20.png|600px|]]</div>
<br>
iii. Click "start" button and wait for the image to write.<br>
<br>
iv. After the image is written, click "close" button<br>
<br>
'''5)Write Android image into EMMC'''<br>
<br>
Steps for writing image into EMMC is almost the same with writing into TF card.<br>
<br>
a.Download corresponding Android image and Phoenix Card writing tool.<br>
b.Formatting SD card.<br>
c.Make sure the Disk is same as TF card, and start formatting SD card.<br>
d.Write Android into TF card, please note the red mark, which is different
from writing into TF card.<br>
<br>
<div style=" ;">[[File:Orange-pi-plus-2e-img2.png|600px|]]</div>
<br>
After written image with Card production, then exit.<br>
<br>
e.Power it on, you could found that the red LED on board is flashing which means the image is writing. When the red LED off, image written finished. Take off the TF card, then power the board on, it should run.<br>
<br>
'''6)Write Linux image into EMMC'''<br>
<br>
It is same of H3 serial for image writing into EMMC. In this charter would take Plus 2E as an example to illustrate which just need to install_to_emmc.<br>
a.Official website image<br>
$ sudo install_to_emmc<br>
Enter Y to make sure data in emmc has been erased
<div style=" ;">[[File:Orange-pi-plus-2e-img3.png|400px|]]</div>
<br>
After finished writing into EMMC, take SD card off and it will boot from EMMC.
<div style=" ;">[[File:Orange-pi-plus-2e-img4.png|400px|]]</div>
<br>
b.Armbian image<br>
$ sudo nand-sata-install
<div style=" ;">[[File:Orange-pi-plus-2e-img5.png|400px|]]</div>
<br>
Select OK
<div style=" ;">[[File:Orange-pi-plus-2e-img6.png|400px|]]</div>
<br>
Select EXT4 as the format of the image
<div style=" ;">[[File:Orange-pi-plus-2e-img7.png|400px|]]</div>
<br>
Formatting partition
<div style=" ;">[[File:Orange-pi-plus-2e-img8.png|400px|]]</div>
<br>
Wait image writing to EMMC.
<div style=" ;">[[File:Orange-pi-plus-2e-img9.png|400px|]]</div>
<br>

=== '''Step 3: Boot your Orange Pi''' ===
<br>
'''1)Hardware Connection Sketch Map'''<br>
<br>
<div style=" ;">
[[File:Orange-pi-plus-2e-img10.png|400px|]]<br>
<div style="width:400px;text-align:center;">Orange Pi PC2 runs on Android 4.4 system</div>
</div>
<br>
<div style=" ;">
[[File:Orange-pi-plus-2e-img11.png|400px|]]<br>
<div style="width:400px;text-align:center;">Orange Pi PC2 runs on Debian system</div>
</div>
<br>
<div style=" ;">
[[File:Orange-pi-plus-2e-img12.png|400px|]]<br>
<div style="width:400px;text-align:center;">Orange Pi PC2 runs on Ubuntu system</div>
</div>
<br>
'''2)Details of Booting Steps'''<br>
<br>
a.Insert the TF card with written image in to the TF card slot on the left edge of the bottom of Orange Pi.<br>
b.You could use HDMI cable to connect your Orange Pi to HDMI TV or monitor.<br>
<br>
You could also use AV interface and audio interface to connect output video and audio to analog TV or display.<br>
<br>
c.Insert USB keyboard and mouse into the right edge of the USB interface.<br>
d.It is the network port in the middle of 3USB interfaces, which you can access Orange Pi to the wired network.<br>
e.It is the power input interface on the right side for connecting a 5V and at least 2A or bigger than 2A power adapter. Avoid using smaller power GSM mobile phone charger, it is not able to output 2A even if it marked "2A 5V".<br>
<br>
Note: Micro-USB（OTG）cannot use as power input which may cause the fail boot of the OrangePi. Only the power interface could input power.<br>
<br>
The Orange Pi will boot in a few minutes If the above steps are successful. There will be graphical interface in he monitor. It may take a long time to start the first time, please wait patiently. The next time will boot very fast.<br>
<br>

=== '''Step 4: Turn off your Orange Pi Correctly''' ===
<br>
* You can use the shutdown button on the interface to safety close the Orange Pi.
* You can also close the system by entering commands in the shell:
<br>
'''sudo halt''' or '''sudo shutdown –h'''<br>
<br>
It will be safety to turn off the Orange Pi. If directly use the power button to shut down the system may damage the file system on TF Card. After the system is closed, the power can be cut off by more than 5 seconds’ press.<br>
<br>
=== '''Other configuration''' ===
<br>
'''1)Connect to the wired network'''<br>
<br>
If Orange pi has already connected to wire cable before powered on, then the system would get the IP address automatically. If it has not connected to wire cable or other problem of network, then it will fail to get the IP address. The system would take some time to load but it has no influence for the board running.<br>
It should be green LED light on and yellow LED flash. You need to make sure the image you wrote is accordingly to the board you use, since there are some board that is Megabit and some are Gigabit which could not be used mixed .<br>
Megabit is using internal phy, here is the configuration: <br>
2 indicates internal phy
<div style=" ;">
[[File:Orange-pi-pc2-img26.png|600px|]]
</div>
<br>
Gigabit is using	external phy, here is the configuration: <br>
1 indicates external phy
<div style=" ;">
[[File:Orange-pi-pc2-img27.png|600px|]]
</div>
<br>
It is defaulted configured, you could take that as reference.<br>
<br>
'''2)Login via vnc and ssh'''<br>
<br>
If there is no condition for connecting HDMI, you could enter the system via vnc or ssh remote login.<br>
* Login via serial port and install ssh apt-get install ssh
* Modify ssh configuration file /etc/ssh/sshd_config
<br>
<div style=" ;">
[[File:Orange-pi-pc2-img28.png|400px|]]
</div>
<br>
* Check the IP with ifconfig, login via ssh of root user
<br>
<div style=" ;">
[[File:Orange-pi-pc2-img29.png|600px|]]
</div>
<br>
'''3)HDMI or 3.5mm Sound Output'''<br>
<br>
a.The sound was default to output via HDMI on image, it could check and change via alsamixer.<br>
ls /etc/asound.conf<br>
card indicates card number, device indicates device number.<br>
aplay -l	it could check the system to load the sound card number and details<br>
cat /proc/asound/cards	it also could check the sound card and details It could be used after use alsamixer to change the sound card.<br>
alsactl store -f /var/lib/alsa/asound.state	used for saving modified parameters<br>
b.It needs to modify configuration on file system for output on 3.5mm of
/etc/asound.conf, modify card1 into card0, or use amixer to modify. The default one is configured, or you could use player on graphical interface to switch via sound channel selection.<br>
c.How to use mic sound recording <br>
arecord -d 5 -f cd -t wav 123.wav<br>
After recording, use the following to play <br>
aplay 123.wav<br>
<br>
'''4)Test GPU'''<br>
<br>
After boot the board, login on hami interface and open terminal. Execute the following command:<br>
glmark2-es2<br>
You could see the test result of mali400.

=== '''Universal Software Configuration''' ===
<br>
'''1)Default Account Changing'''<br>
<br>
The default log in account is orangepi. In order to secure, it is recommended to modify the default orangepi accounts to your own account, for example Zhangsan. Steps are as follows:<br>
a.Use root account to login Orange Pi(please note that do not login with the account of orangepi<br>
b.$ usermod -l zhangsan orangepi Change orangepi account into Zhangsan
<div style="  ">
[[File:Orange-pi-pc2-img30.png|400px|]]
</div>
c.$ groupmod -n zhangsan orangepi	Change group
<div style="  ">
[[File:Orange-pi-pc2-img31.png|400px|]]
</div>
d.$ mv /home/ornagepi	/home/zhangsan	Change directory of original orangepi
<div style="padding-left:80px;">
[[File:Orange-pi-pc2-img32.png|600px|]]
</div>
e.$ usermod -d /home/orangepi orangepi	Set this directory to orangepi user's home directory
<div style="padding-left:80px;">
[[File:Orange-pi-pc2-img33.png|600px|]]
</div>
f.$ cat /etc/passwd	It should be shown as below:
<div>
[[File:Orange-pi-pc2-img34.png|800px|]]
</div>
After the modification of the above iterms, it can be used the new account Zhangsan to land.<br>
<br>
'''2)U Disk Automatic Mounted Configuration'''<br>
<br>
a.sudo apt-get install usbmount<br>
b.sudo vim /etc/udev/rules.d/automount.rules <br>
ACTION=="add",KERNEL=="sdb*",	RUN+="/usr/bin/pmount	--sync
--umask 000 %k"<br>
ACTION=="remove", KERNEL=="sdb*", RUN+="/usr/bin/pumount %k" ACTION=="add",KERNEL=="sdc*",	RUN+="/usr/bin/pmount	--sync
--umask 000 %k"<br>
ACTION=="remove", KERNEL=="sdc*", RUN+="/usr/bin/pumount %k"<br>
<br>
c.udevadm control –reload-rules <br>
It could refer to this:<br>
http://unix.stackexchange.com/questions/134797/how-to-automatically-mount-an-usb-device-on-plugin-time-on-an-already-running-sy<br>
<br>
'''3)System Source Configuration'''<br>
<br>
Take Ubuntu as an example:<br>
a.Open the source file<br>
$ sudo vi /etc/apt/sources.list
<div>
[[File:Orange-pi-pc2-img35.png|800px|]]
</div>
b.Edit source file<br>
Replace the source file with your favorite source. Take an example of Ubuntu 16.04 on Zhonkeda source:<br>
deb	http://mirrors.ustc.edu.cn/ubuntu-ports/	xenial	main multiverse restricted universe<br>
deb	http://mirrors.ustc.edu.cn/ubuntu-ports/	xenial-backports main multiverse restricted universe<br>
deb	http://mirrors.ustc.edu.cn/ubuntu-ports/	xenial-proposed main multiverse restricted universe<br>
deb http://mirrors.ustc.edu.cn/ubuntu-ports/ xenial-security main multiverse restricted universe<br>
deb http://mirrors.ustc.edu.cn/ubuntu-ports/ xenial-updates main multiverse restricted universe<br>
deb-src	http://mirrors.ustc.edu.cn/ubuntu-ports/	xenial	main multiverse restricted universe<br>
deb-src http://mirrors.ustc.edu.cn/ubuntu-ports/ xenial-backports main multiverse restricted universe<br>
deb-src http://mirrors.ustc.edu.cn/ubuntu-ports/ xenial-proposed main multiverse restricted universe<br>
deb-src	http://mirrors.ustc.edu.cn/ubuntu-ports/	xenial-security main multiverse restricted universe<br>
deb-src	http://mirrors.ustc.edu.cn/ubuntu-ports/	xenial-updates main multiverse restricted universe<br>
Note: xenial is the version of the code name in this source, if the other version of Ubuntu needs to replace the corresponding version code which can be found on the internet.<br>
<br>
'''4)Remote desktop installation'''
<br>
There are a lot of software, such as VNG, XRDP, X2GO, etc. For X2GO, it has more functions, and desktop color restore is very good which does not need too much configuration. And XRDP is much more safety than VNC.<br>
a.$sudo apt-get install tightvncserver      Install VNC
<div>[[File:Orange-pi-pc2-img36.png|400px|]]</div>
<br>
b.vncpassw Set the password: do not execute this command but executing vncserver directly. It will prompt you to enter the password twice, when prompted whether can be read only to select the N.
<div>[[File:Orange-pi-pc2-img37.png|800px|]]</div>
<br>
c.Open one or more of desktops by vncserver or vncserver:1(vncserver:2)… you can also transfer more parameters through the full command as below:<br>
vncserver :1 -geometry 1024x768 -depth 16 -pixelformat rgb565<br>
(Note: If it prompted you that cannot find the file or other error when installing, please run sudo apt-get update to update the software source and try installing again.)<br>
<br>
'''5)NAS and DLAN Configuration'''
<br>
a.NAS：<br>
There are many files could be reference from Internet, for example: http://www.geekfan.net/5003/, it detailed descriptions on the operation and the mounted of U disk is very useful.<br>
b.DLNA:<br>
Mainly through the minidlna software to achieve the sharing of media resources within the LAN, such as sharing video, music, etc.. The installation steps are as follows:<br>
i. sudo apt-get minidlna<br>
ii. Execute the following command to modify the configuration file: <br>
sudo nano /etc/minidlna.conf<br>
Note: you can also use other text editor to modify. <br>
iii. Add the following:<br>
media_dir=A,/nas, path: /DLNA/Music<br>
media_dir=V,/nas, path: /DLNA/Video <br>
media_dir=P,/nas, path: DLNA/Picture <br>
db_dir=/nas, path: /DLNA/log <br>
db_dir=/nas, path: /DLNA/db<br>
ctrl +o and enter, ctrl +x to save and exit.<br>
iv. Established above folders respectively, noted that path consistency and assigned to read and write permissions. In order for convenient, it could be Chmod 755, such as sudo Chmod 755 /nas path /DLNA/Music<br>
v. Re-start minidlna to take effect the configuration: /etc/init.d/minidlna restart.<br>
Transmit the corresponding file on the computer to the corresponding folder through samba.<br>
Note: It is recommended to download MoliPlayer on the mobile device. The effect is good and no blue light pressure on both Android and IOS.<br>
<br>
'''6)Thunder remote download'''
<br>
a.Go to the Thunder routing forum to download the required installation package first. The link for stable version:<br>
http://luyou.xunlei.com/thread-12545-1-1.html. <br>
Download Xware1.0.31_cubieboard zip file.
<div style=" ;">[[File:Orange-pi-pc2-img38.png|800px|]]</div>
<br>
Note: If you want to try the latest version, you can download the latest test version: http://luyou.xunlei.com/thread-15167-1-1.htm.<br>
b.Enter the directory after uploaded the unzip file to OrangePi. It is recommended to rename the file to xunlei<br>
c.Installation method of version 1.0.31:<br>
i	$ cd /xxx/xunlei	The xxx is the directory of installation xunlei file <br>
ii		$ chmod 755 portal<br>
iii $ ./portal
<div>[[File:Orange-pi-pc2-img39.png|800px|]]</div>
<br>
iv You will get an activation code after booting like the following:
<div>[[File:Orange-pi-pc2-img40.png|800px|]]</div>
<br>
v Copy this activation code to http://yuancheng.xunlei.com (Which required to log in with account of Thunder). Then click the tab on the top right corner to add, fill in the activation code to complete the binding according to the following figure.
<div>[[File:Orange-pi-pc2-img41.png|800px|]]</div>
<br>
vi Setting start up<br>
$ sudo nano /etc/rc.loacl<br>
add the following contents before exit 0 <br>
cd /xx/xunlei<br>
./portal	&
ctrl +o and enter, ctrl +x to save and exit.<br>
d.Installation of version 3.0.32.253:<br>
i $ cd /xxx/xunlei	The xxx is the directory of installation file of xunlei<br>
ii $ sudo nano thunder_mounts.cfg	Modify the download path
<div style=" ;">[[File:Orange-pi-pc2-img42.png|400px|]]</div>
<br>
iii chmod +x etm_monitor<br>
iv Run ./etm_monitor, there will be an activation code page like
version 1.0.32. And then binding on the Thunder remote page (above steps 4, 5). There might be one or two errors while running, ignore it (selection type of shell and generation of INI file).<br>
v Setting start up<br>
sudo nano /etc/rc.loacl	<br>
add the following contents before exit 0 <br>
cd /xx/xunlei<br>
./etm_monitor &<br>
ctrl +o and enter, ctrl +x to save and exit.<br>
It could be remote downloading on computer, mobile phone or tablet by login yuancheng.xunlei.com<br>
<br>
'''7)Modify the size of ext4 file system'''
<br>
After made the written image into SD card for booting, enter into rootfs partition’s expansion of file system. It could enhance the performance of SD card to avoid limited storage cause prblem.<br>
<br>
* Method 1
<br>
Extend rootfs file partition of TF card on PC:
Select the specified disk, right click and select the corresponding disk, select "change size" and adjust it into your desired size, click "resize", close the dialog box and click "apply all operations", select the application to complete the expansion operation<br>
<br>
* Method 2
<br>
Enter into the system and extend via shell Before partition
<div style=" ;">[[File:Orange-pi-pc2-img43.png|400px|]]</div>
<br>
Eneter into system and expend via resize_rootfs.sh
<div style=" ;">[[File:Orange-pi-pc2-img44.png|400px|]]</div>
<br>
Enter	resize_rootfs.sh	on	command	line,	the	system	will	expending automatically,
Reboot the system and use df -lh to check whether expending is successful
<div style=" ;">[[File:Orange-pi-pc2-img45.png|400px|]]</div>
<br>
a.Expand file system<br>
i. Boot to Linux, umount /dev/sdb1 and /dev/sdb2, if it prompts disk busy, then use fuser to clean the using disk(we will recommend using another Linux booting disk to lead the system).<br>
ii. Use fdisk /dev/sdb to adjust the partition size, after into it, enter p, and keep in mind about the initial position of needed extending size partition.<br>
iii. Enter d to delete the partition need to change the size(my file system is /dev/sdb2, which is the 2 partition ).<br>
iv. Enter n to build a new partition, make sure the initial position is the same as you deleted, and enter the number as you desire.<br>
v. Enter w to save the partition data.<br>
vi. Use the following command to check the file system(make sure it is a right file system)<br>
e2fsck -f /dev/sdb2<br>
vii. Adjust the partition size <br>
resize2fs /dev/sdb2<br>
viii. It could mount a disk partition, you could check whether it has changed.<br>
<br>
b.Shrink file system<br>
i. Boot to Linux, umount /dev/sdb1 and /dev/sdb2, if it prompts disk busy, then use fuser to clean the using disk(we will recommend using another Linux booting disk to lead the system).<br>
ii. Use the following command to check the file system(make sure it is a right file system)<br>
e2fsck -f /dev/sdb2<br>
iii. Modify the size of file system(Use resize2fs)<br>
resize2fs /dev/sdb2 900M<br>
The "s"after the number represents specifying the size of file system via the sectors(every sector calculated by 512 bite). You could also specify it into K(KB), M(MB), G(GB), etc.<br>
iv. Use fdisk /dev/sdb to adjust the partition size, after into it, enter p, and keep in mind about the initial position of needed extending size partition. You need to first delete the partition then build a new one because the fdisk could not modify the size dynamic(you need to calculate the size, it have to enough to contain the file system adjusted in last step).
v. Enter d to delete the partition need to change the size(my file system is /dev/sdb2, which is the 2 partition ).<br>
vi. Enter n to build a new partition, make sure the initial position is the same as you deleted, and enter the number as you desire. Besides, if it is bootable partition you want to change, note that need to keep the bootable mark in case cannot boot.<br>
The above illustration is using fdisk and resize2fs to modify partition and file system, you could also use gparted. Gparted has graphical interface and it could help you to re-size file system at the same time of re-sizing partition. Goarted is much easier to use and reduce the change to make mistake. For now our offial Lubuntu and Raspbian could not use it.<br>
<br>
'''8)How to use gc2035 on Linux'''
<br>
a.Use find command to find the location of the following files, and load it according to the specified order<br>
insmod videobuf-core.ko <br>
insmod videobuf-dma-contig.ko <br>
insmod uvcvideo.ko<br>
insmod cci.ko <br>
insmod vfe_os.ko<br>
insmod vfe_subdev.ko <br>
insmod gc2035.ko <br>
insmod vfe_v4l2.ko<br>
There should be generated video0 on /dev/ after loaded. After low-level driver install, then the Andoird could be used directory.<br>
b. Use camera in Linux<br>
i	Load up driver<br>
sudo modprobe gc2035 <br>
sudo modprobe vfe_v4l2<br>
ii. Install motion<br>
sudo apt-get install motion<br>
iii. Modify configuration <br>
sudo nano /etc/motion/motion.conf <br>
stream_localhost off<br>
iv. Create folder for images saving <br>
mkdir ~/motion<br>
v. Modify permission <br>
chmod 777 motion<br>
vi. Continue modifying configuration <br>
sudo nano /etc/default/motion <br>
start_motion_daemon=yes<br>
vii. Boot the server <br>
Sudo /etc/init.d/motion start<br>
Enter the following in browser: localhost:8081 <br>
You could check image output from camera.<br>
Besides, you could also refer to this link:<br>
http://www.cnx-software.com/2015/09/26/how-to-use-orange-pi-camera-in-linux-with-motion/<br>
<br>
'''9)eth0 and wlan0 static mac address setting'''
<br>
a.If the system do not use systemd, you could modify rc.local directory and add the following:<br>
$ vim /etc/rc.local <br>
MAC=00:e0:4c:a1:2b:d4<br>
ifconfig wlan0 down<br>
ifconfig wlan0 hw ether $MAC <br>
ifconfig wlan0 up<br>
dhclient &<br>
After rebooting, you could use ifconfig to check whether mac address has changed.<br>
b.If the system used systemd, you also need to add the following besides the above steps:<br>
$ cd /etc/systemd/system/<br>
$ vim change_mac_address.service (You could name the server, format just like the following)<br>
<br>
[unit]<br>
Description=Change OrangePi Wifi mac address<br>
<br>
[Service] <br>
ExecStart=/etc/rc.local RemainAfterExit=yes<br>
<br>
[Install]<br>
sWantedBy=multi-user.target<br>
<br>
$ systemctl enable change_mac_address.service<br>
Modify mac address of eth0 is same as modifying wlan0’s, just need to replace wlan0 into eth0.<br>
<br>
'''10)Orange Pi Android root'''
<br>
There is defaulted with root permission on Android pre-installed, but lacking authorization management software. The following is how to add authorization management software.<br>
<br>
You need to have UsbModeSwitch.apk and UPDATE-SuperSU-v2.46.zip, install kingroot and make sure OTG on Orange Pi could connect to PC.<br>
<br>
a.Open adb debug mode<br>
Use U disk or card reader to install UsbModeSwitch.apk into Orange Pi OS and open it, tick "enable usb device mode" and use debug cable to connect OTG port and PC (make sure it is micro usb-cable in case other cables could not be recognized). Normally PC would search and install adb driver software automatically. If PC failed to install, you could install PC version’s Peasecod to install the driver software.<br>
<br>
b.After connected Orange PI and PC, open command mode of PC, enter related command of adb(you need to install adb debug command, which Peasecod has adb command ). Here is the command:<br>
adb remount <br>
adb shell<br>
windows(win+r) command line enter into command mode, then enter into kingroot directory and execute the following steps:<br>
adb shell<br>
root@rabbit-p1:/ # mkdir /tmp <br>
root@rabbit-p1:/ # cd /system/bin<br>
root@rabbit-p1:/ # mount -o remount, rw /system<br>
root@rabbit-p1:/system/bin # ln -s busybox-smp unzip <br>
Logout adb shell Mode<br>
root@rabbit-p1:/exit (Or Ctrl + C) <br>
Unzip UPDATE-SuperSU-v2.46.zip<br>
You will obtain META-INF/com/google/android/update-binary and put it into specific catalog.<br>
adb push /path/UPDATE-SuperSU-v2.46.zip /data/local/tmp	path is file’s path<br>
adb push /path/ update-binary /data/local/tmp <br>
adb shell<br>
root@rabbit-p1:/ #cd /data/local/tmp <br>
root@rabbit-p1:/ #sh update-binary 0 1<br>
/data/local/tmp/UPDATE-SuperSU-v2.46.zip<br>
<nowiki>......</nowiki><br>
<nowiki>......</nowiki><br>
After executed scripts, enter reboot command and reboot it, you could use the device authorization management software normally.<br>
After rebooted, there might be no super administrator icon, you need to delete the desk configuration file and reboot the board.<br>
<br>
'''11)WiringPi installation and usage'''
<br>
a.	Install WiringPi<br>
i	Install compilation tools for source code compilation<br>
$ sudo apt-get install gcc g++ make <br>
ii	Compile GPIO driver of H5<br>
git clone https://github.com/kazukioishi/WiringOP.git -b h5 <br>
cd WiringOP<br>
chmod +x ./build <br>
sudo ./build<br>
iii	GPIO print out information <br>
# gpio -v<br>
gpio version: 2.20<br>
Copyright (c) 2012-2014 Gordon Henderson<br>
This is free software with ABSOLUTELY NO WARRANTY. For details type: gpio -warranty<br>
<br>
Banana Pro Details:<br>
<br>
Type: Banana Pro, Revision: 1.2, Memory: 1024MB, Maker: LeMaker <br>
iv	Display<br>
gpio readall
<div>[[File:Orange-pi-pc2-img46.png|800px|]]</div>
<br>
'''12)Configure Network'''<br>
<br>
* '''Method 1:'''
a.Enter following on the command line:<br>
$ ifconfig<br>
To chcek whether	there is wlan(wlan*)<br>
b.If no, load corresponding wlan model<br>
$ insmod 8189*.ko<br>
For example, RTL8189ftv is corresponding to 8189fs.ko, while RTL8189etv is corresponding to 8189es.ko<br>
c.Enter command ifconfig you should find there is wlan0(Hypothesis it is wlan0)<br>
d.Configure wireless, first you need to know ssid and psk(account and password), enter corresponding wlan*，ssid，psk<br>
$ sudo nano /etc/network/interfaces	(add the following contents) <br>
auto wlan0<br>
iface wlan0 inet dhc<br>
wpa-ssid xxxx<br>
wpa-psk xxxx<br>
e.Reboot the board and wireless should be available<br>
$ sudo reboot<br>
<br>
* '''Method 2:'''
a.Establish a wifi hotspot configure file wpa_supplication.conf on the directory of
/etc/network/ and add the following contents: <br>
network={<br>
ssid="wifi hotspot name" <br>
psk="wifi hotspot password" <br>
priority=1<br>
}<br>
b.Connect wifi with the following command:<br>
<br>
ifconfig wlan0 up<br>
sudo wpa_supplicant -i wlan0 -c /etc/network/wpa_supplication.conf & dhcpcd wlan0 &<br>
<br>
c.Test the condition of wifi connection<br>
Use ifconfig command you could check the information of wlan0 and use ping command to test.<br>
<br>
'''13)Use USBwifi of official image'''<br>
<br>
a.Insert USBwifi and make sure USB is opened. Enter command lsusb to check the detail information of USB<br>
$ dmesg<br>
$ lsusb<br>
(Bus 008 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter) id is 8176 and check the driver from internet it is rtl8188cu. You could find it from the following link:<br>
https://sites.google.com/site/easylinuxtipsproject/reserve-7#TOC-Realtek-RTL8188CUS- and-RTL8192CU-chipsets-0bda:8176-and-0bda:8178-<br>
<br>
1 Determine the chipset<br>
2 Realtek RTL8188CUS and RTL8192CU chipsets (0bda:8176 and 0bda:8178)
Source code compile lib/modules/*/drivers/net/wireless/realtak/ and it will generated into 8192CU.ko<br>
b.Source code in disk <br>
(rtl8188C_8192C_usb_linux_v4.0.2_9000.20130911.tar.gz)<br>
Update the directory of uImage and lib<br>
<br>
c.Power it on, and it will load the following module:<br>
rtlwifi.ko,rtl8192c_common.ko,mac80211.ko,rtl8192cu.ko.<br>
<br>
d.Uninstall the module of rtl8192cu.ko and install 8192cu.ko, modify /etc/modules and add 8192cu, to make it could boot after power on<br>
e.Modify /etc/network/interfaces, add ssid and psk.<br>
f.Reboot and USBwifi should be available.<br>
<br>

== '''Linux Kernel Source Code Compilation''' ==
<br>
In order to support the rapid development of the project, we are writing this sections for project configuration options to the binary file. When the system is running, it can get the information of the system running by reading the binary file, which can greatly simplify the time of project development.<br>
This manual describes how to use the binary file to speed up the development of the project.<br>
Hardware: Orange Pi development board*1, Card reader*1, TF card*1, power supply*1
<div style=" ;">[[File:Orange-pi-plus-2e-img13.png|800px|]]</div>
<br>
Note: In the following sections, * indicates wild-cards, you need to fill in the actual values according to their file storage path.<br>
<br>
=== '''Download Linux Source Code''' ===
<br>
You could download the source code from the official website(Source code for H3 chip are the same): <br>
http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Plus-2-E.html<br>
<br>
Subsection and compress the file, then unzip it after finish downloaded:
<div style=" ;">[[File:Orange-pi-pc2-img49.png|600px|]]</div>
<br>
buildroot: Project compilation script<br>
brandy: gcc-linaro, boot and uboot source code and open source cross compiler tool<br>
linux-3.10: Kernel source code <br>
tools: Tools of project compilation <br>
build.sh: compilation script<br>
<br>

=== '''Compile Project Source Code''' ===
<br>
You need to compile the entire project while it is your first time to use the source code. You can use the following commands in the /lichee directory to complete the project:<br>
* Enter into content of lichee, command<br>
$ ll -a<br>
Check if there is an executable permission on build.sh, if not, modify the permissions<br>
$ chmod   755   build.sh<br>
* If there is .buildconfig after commanded ll –a, delete it<br>
$ rm –rf .buildconfig
<div>[[File:Orange-pi-pc2-img50.png|800px|]]</div>
<br>
* Use the following command to compile the entire project<br>
$ ./build.sh	config
<div>[[File:Orange-pi-pc2-img51.png|800px|]]</div>
<br>
At this point the system will prompt the choice of the chip, as shown below, for OrangePi, select sun50iw2p1<br>
At this point, the system will be prompted to select the platform, as shown below, for OrangePi, select Android<br>
At this point, the system will be prompted the choice of the board, as shown below, for the OrangePi, select dolphin-p1
<div style=" ;">[[File:Orange-pi-pc2-img52.png|400px|]]</div>
<br>
Appear this interface indicates waiting for the compiler.
<div style=" ;">[[File:Orange-pi-pc2-img53.png|400px|]]</div>
<br>
Wait fifteen minutes or so, compile complete.
<div style=" ;">[[File:Orange-pi-pc2-img54.png|400px|]]</div>
<br>
=== '''Update the Kernel Image File and Replace Library''' ===
<br>
* After compilation is finished, the following files will be generated in the directory：
libs：	lichee/out/sun8iw7p1/android/common/lib/modules/3.4.39 <br>
Download image from official website：<br>
http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Plus-2-E.html<br>
<br>
* Write the image：<br>
$ sudo dd bs=4M if=*.img of=/dev/sdb<br>
<br>
<div>[[File:Orange-pi-plus-2e-img16.png|800px|]]</div>
<br>
Pull out the card reader, and then insert it again.<br>
At this time, the SD card is inserted into PC, view the SD card mount point (if you don't know how to get a mount point for the SD card, please refer to the diagram below).
<div>[[File:Orange-pi-pc2-img57.png|800px|]]</div>
<br>
The first boot partition
<div>[[File:Orange-pi-pc2-img58.png|800px|]]</div>
<br>
The second rootfs partition
<div>[[File:Orange-pi-pc2-img59.png|800px|]]</div>
<br>
Copy the kernel image file generated by the compiler to the first partition (boot partition)<br>
Copy the lib library which generated after compilation to the second partition (rootfs partition)<br>
'''We would suggest using compilation system on github of official website.'''
<div>[[File:Orange-pi-pc2-img60.png|800px|]]</div>
<br>
build.sh			Execute script into the graphical interface of compilation <br>
extenal	Inside are patch and some configuration kernel file <br>
output File generated<br>
script	Script compiled <br>
toolchain Cross compiler location <br>
uboot	uboot source code<br>
<br>
Execute./build.sh enter into graphical interface and select Plus 2E
<div style=" ;">[[File:Orange-pi-pc2-img61.png|600px|]]</div>
<br>
Enter password of root
<div style=" ;">[[File:Orange-pi-pc2-img62.png|600px|]]</div>
<br>
Update Kernel directory and module
<div style=" ;">[[File:Orange-pi-pc2-img63.png|600px|]]</div>
<br>
Select corresponding file directory and update uImage and modules
<div style=" ;">[[File:Orange-pi-pc2-img64.png|600px|]]</div>
<br>

== '''Android Kernel Source Code Compilation''' ==
<br>
Hardware: Orange Pi development board*1, Card reader*1, TF card*1, power supply*1
<div style=" ;">[[File:Orange-pi-plus-2e-img13.png|800px|]]</div>
<br>
Software<br>
Linux host computer, which hard disk space at least 50G (to meet a fully compiled need)<br>
Linux host computer needs: <br>
Version 2.7.3 of Python;<br>
Version 3.81-3.82 of GNU Make; JDK 6;<br>
Version 1.7 or higher version of Git.<br>
<br>
=== '''Install JDK''' ===
<br>
The following will be illustrating jdk1.6 installation, it would be same for jdk1.7 installation.
* Download and install JDK, you will obtain jdk-6u31-linux-x64.bin
* Modify the permission of jdk-6u31-linux-x64.bin, which has no prior permission
* $./jdk-6u31-linux-x64.bin <br>
It will generate a folder:
<div>[[File:Orange-pi-pc2-img66.png|800px|]]</div>
<br>
* Input at terminal<br>
Note that JAVA_HOME is the name of the current directory, you need to fill in according to your own storage directory.
<div>[[File:Orange-pi-pc2-img67.png|800px|]]</div>
<br>
$ export	JAVA_HOME=*/jdk1.6.0_31<br>
$ export	PATH=$PATH:/$JAVA_HOME/bin<br>
$ export	CLASSPATH=.:$JAVA_HOME/lib<br>
$ export	JRE_HOME=$JAVA_HOME/jre
<div>[[File:Orange-pi-pc2-img68.png|800px|]]</div>
<br>
* Command line input Jav and press tab to see whether it can auto completion (Java), which indicates it can successfully installed<br>
<br>
=== '''Install Platform Supported Software''' ===
<br>
$ sudo apt-get install git gnupg flex bison gperf build-essential \ zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \ libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \ libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386<br>
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1
/usr/lib/i386-linux-gnu/libGL.so<br>
<br>

=== '''Download Android Source Package''' ===
<br>
Download website(source code is same for all boards of H3 chip):<br>
http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Plus-2-E.html<br>
<br>
Then you will obtain the following directories:
<div style=" ;">[[File:Orange-pi-pc2-img69.png|300px|]]</div>
<br>

=== '''Install Compiler Tool Chain''' ===
<br>
The compiler tool chain has been integrated in Android SDK. Tool chain is on: lichee/brandy/gcc-linaro/ of Android SDK(already exist)<br>
<br>
<div>[[File:Orange-pi-pc2-img70.png|800px|]]</div>
<br>
=== '''Compile Lichee source Code''' ===
<br>
There are Android and Lichee after unzipped the package, enter the directory of Lichee:<br>
$ cd lichee<br>
$ ./build.sh lunch <br>
<div>[[File:Orange-pi-plus-2e-img18.png|400px|]]</div>
<br>
Select sun8iw7p1<br>
Print information of successful compilation
<div>[[File:Orange-pi-pc2-img71.png|400px|]]</div>
<br>

=== '''Compile Command of Android Code''' ===
<br>
Input the command:<br>
$ cd android<br>
$ source ./build/envsetup.sh
<div>[[File:Orange-pi-plus-2e-img20.png|600px|]]</div>
<br>
$ lunch dolphin_fvd_p1-eng	# Select the scheme number
<div>[[File:Orange-pi-plus-2e-img21.png|600px|]]</div>
<br>
$ extract-bsp	# Copy the kernel and the drive module
<div>[[File:Orange-pi-plus-2e-img22.png|600px|]]</div>
<br>
$ make	The rear values of # is for the simultaneous compilation process, dependent on the host configuration
<div>[[File:Orange-pi-plus-2e-img23.png|600px|]]</div>
<br>
$ pack	#Packaged into firmware
<div>[[File:Orange-pi-plus-2e-img24.png|600px|]]</div>
<br>
$ cd */lichee/tools/pack/
<div>[[File:Orange-pi-plus-2e-img25.png|600px|]]</div>
<br>

== '''Use Project Configuration Files''' ==
<br>
=== '''sys_config.fex Introduction''' ===
<br>
'''Configure hardware: sys_config.fe'''
<br>
<br>
The sys_config.fex is a binary configuration file that used by the SOC kernel driver or LiveSuit for a particular target board, including how to set up a variety of peripherals, ports, and I/O which based on the target version.<br>
For OrangePi, the location of the project configuration document is： lichee/tools/pack/chips/sun8iw7p1/configs/dolphin-p1/sys_config.fex<br>
Copy the file to the directory of /lichee, use command:<br>
$ cd ./lichee<br>
$ cp ./tools/pack/chips/sun8iw7p1/configs/dolphin-p1/sys_config.fex ./ <br>
<div>[[File:Orange-pi-plus-2e-img26.png|800px|]]</div>
<br>
You could personalized configuration of sys_config.fex according to
sysconfig1.fex_manul_linux_BSP_v0.4.pdf.<br>
Direcotory of sysconfig1.fex_manul_linux_BSP_v0.4.pdf is
/lichee/buildroot/docs.<br>
<br>
=== '''Update Uboot and boot''' ===
<br>
After modified sys_config.fex, update the new data into SD card(please note that the SD card should have wrote with image, if not, please first finished image writing). Uboot tool will supply in the official website.<br>
<br>
If the mounted point of image is“/dev/sdb”, then you could enter the following command to update u-boot, boot and script.bin:<br>
$ dd if=boot0_sdcard_sun8iw7p1.bin	of=/dev/sdb bs=1024	seek=8<br>
$ dd if=u-boot-sun8iw7p1.bin	of=/dev/sdb bs=1024	seek=16400<br>
<br>
u-boot and boot should have been update after the above commands, but the engineering configuration of the binary file has not yet been updated.<br>
Copy the generated script.bin to boot partition:<br>
$ cd /lichee/<br>
$ cp script.bin	/media/*/boot/	-rf<br>
<br>
After that, engineering configuration file should have been updated and Orange Pi would run with the new configuration data.<br>
<br>
=== '''Examples''' ===
<br>
'''1)Modify the output mode into tv'''
<br>
* tv-out out, the output type of tv0 is invalid, you need to set the output type of tv1 into pal.
Modify defaulted enable display output configuration into tv <br>
[tv0]<br>
used	= 1<br>
tv_dac_used	= 1<br>
dac_src0	= 0<br>
dac_type0= 0<br>
interface= 1 <br>
[tvout_para] <br>
tvout_used= 1<br>
tvout_channel_num= 1<br>
<br>
[disp] <br>
disp_init_enable= 1<br>
disp_mode= 1<br>
screen0_output_type= 2<br>
screen0_output_mode= 11<br>
screen1_output_type= 2<br>
screen1_output_mode= 11<br>
dev0_output_type = 4<br>
dev0_output_mode = 4<br>
dev0_screen_id = 0<br>
dev0_do_hpd = 1<br>
dev1_output_type = 2<br>
dev1_output_mode = 11<br>
Modify sys_confi and replace it when it generated OrangePiH5.dtb. If would be faster if use compilation system on githug. About compilation you could refer to the charter of Linux Compilation.<br>
<br>
'''2)Loading tv.ko module automatically after booted'''
<br>
Enter /lib/ directory, enter command: <br>
depmod -a<br>
Add one more line on /etc/modules <br>
tv<br>
It would be tv out after booted<br>
* Capacitance touch panel (capacitor tp)
<br>
{| class="wikitable" style="background:#fff;width:800px;"
|-
| Configuration Item|| Configuration Meaning
|-
| ctp_used=xx|| Whether turn on capacitance touch panel, if so set the value as 1, and vice verso 0.
|-
| ctp_name =xx|| Indicates the control scheme used in the specified scheme, for now there are: "ft5x_ts" or "Goodix-TS".
|-
| ctp_twi_id=xx|| Used for selecting i2c adapter, there are 0 and 2.
|-
| ctp_twi_addr =xx|| Indicates the device address of i2c, it is related to the specific hardware.
|-
| ctp_screen_max_x＝xx|| Maximum coordinates of the X axis of the touch panel
|-
| ctp_screen_max_y=xx|| Maximum coordinates of the Y axis o the touch panel
|-
| ctp_revert_x_flag=xx|| Whether	needed	to	flip	the	X coordinates, if so then set 1, and vice verso 0.
|-
| ctp_revert_y_flag=xx|| Whether	needed	to	flip	the	Y coordinates, if so then set 1, and vice verso 0.
|-
| ctp_int_port=xx|| GPIO configuration of the interrupt signal of capacitive touch panel
|-
| ctp_wakeup=xx|| GPIO configuration of the wake-up signal of capacitive touch panel
|-
| ctp_io_port=xx|| Capacitive screen IO signal, currently share with interrupt signal common pin
|}
Configuration samples:<br>
<br>
ctp_used	= 1<br>
ctp_name	= "ft5x_ts"<br>
ctp_twi_id	= 2<br>
ctp_twi_addr	= 0x70 <br>
ctp_screen_max_x	= 800<br>
ctp_screen_max_y	= 480<br>
ctp_revert_x_flag	= 0<br>
ctp_revert_y_flag	= 0<br>
ctp_int_port	= port:PH21<6><default><br>
ctp_wakeup	= port:PB13<1><default><default><1><br>
ctp_io_port	= port:PH21<0><default><br>
<br>
Note: If you want to support the new capacitive touch IC, you need to combine the configuration of the BSP A10 layer, which should be based on the original capacitive touch IC code, to make the appropriate changes. Specifically, 1) ctp_twi_id should be consistent with the hardware connection in sys_config; 2) In the drive part of the code: the use of twi from the device name + address should be consistent with the ctp_name and ctp_twi_addr in sys_config configuration. At the same time, the other sub configuration in sysconfig should also be properly configured, these configurations should be corresponding processing in the program.<br>
<br>
'''3)Modify Resolution'''<br>
<br>
Open item of disp_init and modify the subitem screen0_output_mode, it would modify into different resolution.<br>
Such as: Screen 0 output mode:(used for tv/hdmi output, 0:480i 1:576i 2:480p 3:576p 4:720p50 5:720p60 6:1080i50 7:1080i60 8:1080p24 9:1080p50 10:1080p60
11:pal 14:ntsc)<br>
The above are some main resolution, you could also find the patch of z-0003-add-additional-video-modes.patch and use it to change the resolution into what you want.<br>
How to make the patch:<br>
patch -p1 < z-0003-add-additional-video-modes.patch<br>
After patched up, recompile the source code with replacing uImage and script.bin.<br>
For example:<br>
1024*768	is 32<br>
1280*1024	is 33<br>
1360*768	is 34<br>
1440*900	is 35<br>
1680*1050	is 36<br>
<br>

== '''Orange Pi Driver development''' ==
<br>
　In order to help developers become more familiar with OrangePi, this manual describes how to use simple device driver modules and applications on the development board. <br>
<br>
Hardware: Orange Pi development board*1, Card reader*1, TF card*1, power supply*1
<div style=" ;">[[File:Orange-pi-plus-2e-img13.png|600px]]</div>
<br>
=== '''Device driver and application programming''' ===
<br>
'''1)Application Program (app.c)'''<br>
<br>
<div>[[File:Orange-pi-i96-img50.png|600px]]</div>
<br>
'''2)Driver Program (OrangePi_misc.c)'''<br>
<br>
<div>[[File:Orange-pi-i96-img51.png|600px]]</div>
<br>
<div>[[File:Orange-pi-i96-img52.png|600px]]</div>
<br>

=== '''Compile device driver''' ===
<br>
Copy the OrangePi_misc.c to the directory of :<br>
<nowiki>*/lichee/linux-3.4.39/driver/misc</nowiki><br>
<div>[[File:Orange-pi-pc2-img83.png|800px]]</div>
<br>
Enter to */lichee/linux-3.4.39/drivers/misc/, and modify makefile<br>
<div>[[File:Orange-pi-pc2-img84.png|800px]]</div>
<br>
Modify Makefile on currently file, shown as following:
<div>[[File:Orange-pi-i96-img53.png|800px]]</div>
<br>
There is Kconfig on the same sibling folders with Makefile. Each Kconfig respectively describes the the source directory file related kernel configuration menu. In the kernel configuration making menuconfig, it read from the Kconfig config menu and the user configuration saved to the config. In the kernel compile, the main Makefile by calling this.Config could know the user's configuration of the kernel.<br>
Kconfig is corresponding to the kernel configuration menu. Add a new driver to the kernel source code, you can modify the Kconfig to increase the configuration menu for your drive, so you can choose whether the menuconfig driver was compiled or not.
<div>[[File:Orange-pi-i96-img54.png|800px]]</div>
<br>
Back to the source code directory:<br>
<div>[[File:Orange-pi-pc2-img85.png|800px]]</div>
<br>
$ ./build.sh<br>
After compiled the kernel, there will be an orangepi_misc.ko file generated on the directory of lichee/linux-3.4/output/lib/modules/3.4.39<br>
<div>[[File:Orange-pi-plus-2e-img27.png|800px]]</div>
<br>
There is a .ko module which generated after compiled of OrangePi_misc.c on */lichee/linux-3.4/output/lib/modules/3.4.39/
<div>[[File:Orange-pi-plus-2e-img28.png|800px]]</div>
<br>
Insert U disk (please note the SD card should have been written image) if the SD card system is mounted to the directory / dev / SDB, SD card will have two sub mount points, respectively are / dev / sdb1 and /dev/sdb2. Two partition of SD card will automatically mount to the PC /media/ directory, the first partition is the boot partition and the second partition is the rootfs partition.
<div>[[File:Orange-pi-i96-img55.png|800px]]</div>
<br>
Copy the OrangePi_misc.ko file to /media/*/lib/modules/3.4.39.
$ cp OrangePi_misc.ko	/media/*/lib/modules/3.4.39<br>
<br>

=== '''Corss-complile or compiled Application code''' ===
<br>
Here will take arm-linux-gnueabihf-gcc as an example. Check whether there is the cross compiler, if not, then download and install it.<br>
$ arm-linux-gnueabihf-gcc -v
<div>[[File:Orange-pi-i96-img56.png|800px]]</div>
<br>
While compiling the application, you will fill that  you need the cross compiler arm-linux-gnueabihf-gcc, download and install it.
<div>[[File:Orange-pi-i96-img57.png|800px]]</div>
<br>
Unzip the downloaded file and enter the the directory
<div>[[File:Orange-pi-i96-img58.png|800px]]</div>
<br>
Check the information after entering bin directory
<div>[[File:Orange-pi-i96-img59.png|800px]]</div>
<br>
pwd hows the path and export it into the whole project
<div>[[File:Orange-pi-i96-img60.png|800px]]</div>
<br>
$ ll /etc/environment  shows that the file can only read, need to modify permissions <br>
$ chmod 755 /etc/environment<br>
Modify permission
<div>[[File:Orange-pi-i96-img61.png|800px]]</div>
<br>
Add the path to the whole environment variable<br>
<div>[[File:Orange-pi-i96-img62.png|800px]]</div>
<br>
Compile the application with cross compiler<br>
<br>
$ arm-linux-gnueabihf-gcc app.c –o aq<br>
There will be an ap application generated in the directory, copy it to the development board file system(on the rootfs directory of /home/orangepi/)<br>
$ cp aq /media/*/home/orangepi/<br>
<br>

=== '''Running driver and application''' ===
<br>
Removed the SD card and inserted it into the development board and power on.<br>
You need to switch to root users and load module driver module to the development board first.<br>
$ insmod /lib/modules/orangepi.ko
<div>[[File:Orange-pi-i96-img63.png|800px]]</div>
<br>
$ lsmod      To check whether it is loaded
<div>[[File:Orange-pi-i96-img64.png|800px]]</div>
<br>
$ ll /dev/orangepimisc( Miscellaneous equipment automatically generated device files, the specific look at the driver code)
<div>[[File:Orange-pi-i96-img65.png|800px]]</div>
<br>
Executive application (note the use of the application, check the code for specify)<br>
$ ./aq /dev/orangepimisc
<br>
<br>

== '''Using Debug tools on OrangePi ''' ==
<br>
Hardware: Orange Pi development board*1, Card reader*1, TF card*1, power supply*1
<div style=" ;">[[File:Orange-pi-plus-2e-img13.png|800px]]</div>
<br>
'''TTL to USB cable'''
<div style=" ;">[[File:Orange-pi-i96-img67.png|800px]]</div>
<br>
=== '''Operations on Windows''' ===
<br>
　In order to get more debugging information in the project development process of using OrangePi, OrangePi default support for serial information debugging. For developers, you can simply get the serial port debugging information with the materials mentioned above. The host computer using different serial debugging tools are similar, basically can reference with the following manual for deployment. There are a lot of debugging tools for Windows platform, the most commonly used tool is putty. This section takes putty as an example to explain the deployment.<br>
<br>
'''1)Install USB driver on Windows'''<br>
<br>
* Download and unzip the latest version of driver: <br>
　PL2303_Prolific_DriverInstaller_v130.zip
<div>[[File:Orange-pi-i96-img68.png|800px]]</div>
<br>
* Choose application installation as Administrator
<div>[[File:Orange-pi-i96-img69.png|800px]]</div>
<br>
* Wait for installation completing 
<div>[[File:Orange-pi-i96-img70.png|800px]]</div>
<br>
'''2)Install putty on Windows'''<br>
<br>
* Download putty installation package
<div>[[File:Orange-pi-i96-img71.png|800px]]</div>
<br>
* Unzip and install it
<div>[[File:Orange-pi-i96-img72.png|800px]]</div>
<br>
* Open it after installed, shown as below:
<br>
<div style=" ;">[[File:Orange-pi-i96-img73.png|600px]]</div>
<br>
'''3)Connect method'''<br>
<br>
Use the TTL to the serial port cable, one end connected to OrangePi, the other end connected to PC
<br>
'''4)Equipment information acquisition'''
<br>
* Select control panel on Start menu
<div style=" ;">[[File:Orange-pi-i96-img75.png|400px]]</div>
<br>
<div style=" ;">[[File:Orange-pi-i96-img76.png|600px]]</div>
<br>
* Click on the device manager to check the port number
<div style=" ;">[[File:Orange-pi-i96-img77.png|400px]]</div>
<div style=" ;">[[File:Orange-pi-i96-img78.png|400px]]</div>
<br>
'''5)Putty configuration'''
<div style=" ;">[[File:Orange-pi-i96-img79.png|400px]]</div>
<br>
Serial port should set to the corresponding port number (COM5), the speed should set to 115200<br>
<br>
'''6)Start debug'''<br>
Power Orange Pi on and boot it, the serial port will automatic print out debug log.
<div style="  ">[[File:Orange-pi-i96-img80.png|600px]]</div>
<br>

=== '''Operations on Linux''' ===
<br>
There are Minicom and Kermit serial debugging tools for Linux, this section will take Kermit as an example to have an illustrate.<br>
<br>
'''1)Install Kermit'''
<br>
* Install the Kermit by execute command:
　$ sudo apt-get install ckermit
<div>[[File:Orange-pi-i96-img81.png|800px]]</div>
<br>
* Configurate Kermit
　$ sudo vi /etc/kermit/kermrc
<div>[[File:Orange-pi-i96-img82.png|800px]]</div>
<br>
* Add lines：
<div style="padding-left:20px;">
set line			/dev/ttyUSB1<br>
set speed			115200<br>
set carrier-watch	off<br>
set handshake	none<br>
set flow-control	none<br>
robust<br>
set file type		bin<br>
set file name		lit<br>
set rec pack		1000<br>
set send pack    1000<br>
set window      5
</div>
<div style=" ;">[[File:Orange-pi-i96-img83.png|600px]]</div>
<br>
'''2)Connect method for debug'''
<br>
　Use the TTL to the serial port cable, one end connected to OrangePi, the other end connected to PC
<br>
'''3)Equipment information acquisition'''<br>
<br>
$ ls /dev/  (Input command in the PC terminal to check the device number of TTL to the serial cable)
<div style="  ">[[File:Orange-pi-i96-img85.png|800px]]</div>
<br>
* It can be seen from the figure that TTL to the serial port cable is identified as ttyUSB0, configure the /ect/kermit/kermitc file, update the serial port information.<br>
　$ sudo vi /etc/kermit/kermitc
* Set the value of setline into /dev/ttyUSB0
<div style="  ">[[File:Orange-pi-i96-img86.png|800px]]</div>
<br>
'''4)Start debug'''
<br>
* Input command in the host computer terminal, enter the Kermit mode:
　$ sudo kermit –c
<div style="  ">[[File:Orange-pi-i96-img87.png|800px]]</div>
<br>
* Power it on and boot Orange Pi, the serial port will automatic print debug log, the account and password ard root/orangepi and orangepi/orangepi
<div style="  ">[[File:Orange-pi-i96-img88.png|800px]]</div>
<br>
== '''Download the Orange Pi Plus 2E User Manual''' ==
<br>
For more information on using the Orange Pi Plus 2E, please see the [https://drive.google.com/open?id=1ba5k1C0iGj7oHfQnCGAz2lgm7Vn30FPk <span style="color:red;">Orange Pi Plus 2E User Manual</span>]. (Click to download)