Changes

← Older edit

Orange Pi 5 Plus

19,124 bytes added, 10:25, 15 June 2023

→‎Burn Orange Pi OS (Droid) image toeMMC

• 1 x HDMI input, up to 4K@60FPS

• 1 x MIPI DSI 4 Lane output, up to 4K@~~60Hz~~60FPS

|-

== Top view and bottom view of Orange Pi 5 Plus ==

[[File:~~media/image4~~plus5-img4.~~jpeg|486x342px|Orange-Pi-5-PLUS-1~~png]]

</div>

<big>'''Bottom view：'''</big>

[[File:~~media/image5~~plus5-img5.~~jpeg|495x329px|Orange-Pi-5-PLUS-2~~png]]

</div>

== Interface details of Orange Pi 5 Plus ==

[[File:~~media/image6~~plus5-img6.png~~|600x553px~~]]

<div style="margin-left: 100px;">[[File:~~media/image7~~plus5-img7.~~jpeg|576x483px|未标题-1~~png]]</div>

# TF card, a class 10 or above high-speed SanDisk card with a minimum capacity of 16GB (32GB or above is recommended)

::[[File:~~media/image8~~plus5-img8.png~~|124x96px~~]]

<li>TF card reader, used to burn the image into the TF card</li>

[[File:~~media/image9~~plus5-img9.png~~|139x106px~~]]

</ol>

<li>Display with HDMI interface</li>

[[File:~~media/image10~~plus5-img10-1.png~~|313x205px~~]]

</ol>

<li>HDMI to HDMI cable, used to connect the development board to an HDMI monitor or TV for display</li>

[[File:~~media/image11~~plus5-img11.png~~|199x129px~~]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|

<big>'''\Note, if you want to connect a 4K or 8K display, please make sure that the HDMI cable supports 4K or 8K video display.'''</big>

|}

</ol>

[[File:~~media/image12~~plus5-img12.~~jpeg|243x166px|IMG_256~~png]]

</div></ol>

[[File:~~media/image13~~plus5-img13.~~jpeg|245x166px|98F5D70E2C9B3673E8ECE4B8ABDDFD80~~png]]

</div></ol>

[[File:~~media/image14~~plus5-img14.~~jpeg|223x203px|IMG_7546~~png]]

</div></ol>

<li>Power adapter, Orange Pi 5 Plus is recommended to use 5V/4A Type-C power supply for power supply</li>

[[File:~~media/image15~~plus5-img15.png~~|274x194px~~]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|

<big>'''There are two Type-C ports that look the same on the development board. The one next to the network port is the power port, and the other Type-C port has no power supply function. Please ~~don’t~~ don't connect it wrong.'''</big>

[[File:~~media/image16~~plus5-img16.~~jpeg~~png|~~269x240px|01~~center]]

</div>

<li>The mouse and keyboard of the USB interface, as long as the mouse and keyboard of the standard USB interface are acceptable, the mouse and keyboard can be used to control the Orange Pi development board</li>

[[File:~~media/image17~~plus5-img17.png~~|311x264px~~]]

</ol>

<li>USB camera</li>

[[File:~~media/image18~~plus5-img18.png~~|331x191px~~]]

</ol>

<li>'''5V cooling fan. As shown in the figure below, the development board has an interface for connecting the cooling fan, and the interface specification is~~''' 2p'''in~~ 2pin 1.25mm pitch'''</li>

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|}

[[File:~~media/image19~~plus5-img19.png~~|410x171px~~]]

</ol>

<li>Network cable, used to connect the development board to the Internet</li>

[[File:~~media/image20~~plus5-img20.png~~|143x112px~~]]

</ol>

<li>The data cable of the Type-C interface, used for burning images, using ADB and other functions</li>

[[File:~~media/image21~~plus5-img21.png~~|143x113px~~]]

</ol>

<li>Infrared remote control</li>

[[File:~~media/image22~~plus5-img22.png~~|170x173px~~]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

<li>OV13850 camera with 13 million MIPI interface (common with OPi5/OPi5B)

[[File:~~media/image23~~plus5-img23.png~~|268x151px~~]]</li>

<li>OV13855 camera with 13 million MIPI interface (common with OPi5/OPi5B)

[[File:~~media/image24~~plus5-img24.png~~|253x150px~~]]</li>

<li>M.2 M-KEY 2280 specification NVMe SSD solid state drive, PCIe interface specification is PCIe3.0x4</li>

[[File:~~media/image25~~plus5-img25.png~~|358x104px~~]]</ol>

<li>eMMC expansion module (to be added physical pictures)</li>

<big>'''The position where the eMMC module is inserted on the development board is shown in the figure below:'''</big>

[[File:~~media/image26~~plus5-img26.png|~~317x144px~~center]]

|}

</ol>

<li>RTC battery, the interface is 2pin, 1.25mm pitch

[[File:~~media/image27~~plus5-img27.png~~|250x134px~~]]</li>

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

<big>'''The location of the RTC battery interface on the development board is shown in the figure below:'''</big>

[[File:~~media/image28~~plus5-img28.png|~~344x126px~~center]]

|}

</ol>

<li>Horn, the interface is 2pin, 1.25mm pitch</li>

[[File:~~media/image29~~plus5-img29.png~~|200x138px~~]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

<big>'''The interface position of the speaker on the development board is shown in the figure below:'''</big>

[[File:~~media/image30~~plus5-img30.png|~~312x158px~~center]]

|}

</ol>

<li>3.3V USB to TTL module and DuPont line, when using serial port debugging function, need USB to TTL module and DuPont line to connect the development board and computer</li>

[[File:~~media/image31~~plus5-img31.png~~|217x89px|G7U7JZX(V`L$`A6864]38$P~~]] [[File:~~media/image32~~plus5-img32.png~~|305x110px~~]]

</ol>

'''http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html'''

|}

::[[File:~~media/image33~~plus5-img33.png~~|361x300px~~]]

|-

|

<big>'''Note that the Linux image mentioned here specifically refers to the image of Linux distributions such as Debian, Ubuntu, OpenWRT or OPi OS Arch downloaded from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''].'''</big>

|}

# First prepare a TF card with a capacity of 16GB or more. The transmission speed of the TF card must be '''class 10''' or above. It is recommended to use a TF card of SanDisk and other brands

# Then use the card reader to insert the TF card into the computer

# Download the Linux operating system image file compression package that you want to burn from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''], and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system. The size is generally above 2GB.

::{| class="wikitable" style="background-color:#ffffdc;width:800px;"

<big>'''Note, if you download the OpenWRT image, you will see the following two types of images in the download link of the OpenWRT image, please download the image file in the "TF card, eMMC and NVME SSD boot image" folder.'''</big>

[[File:~~media/image34~~plus5-img34.png|~~277x88px~~center]]

|}

<li>After entering the balenaEtcher download page, click the green download button to jump to the place where the software is downloaded

[[File:~~media/image35~~plus5-img35.png~~|575x276px~~]]</li>

<li>Then you can choose to download the Portable version of balenaEtcher software. The Portable version does not need to be installed, and you can use it by double-clicking to open it</li>

[[File:~~media/image36~~plus5-img36.png~~|576x213px~~]]

</ol>

<li>If the downloaded version of balenaEtcher needs to be installed, please install it before using it. If you downloaded the Portable version of balenaEtcher, just double-click to open it. The balenaEtcher interface after opening is shown in the figure below:</li>

[[File:~~media/image37~~plus5-img37.png~~|483x304px~~]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

<big>'''When opening balenaEtcher, if the following error is prompted:'''</big>

[[File:~~media/image38~~plus5-img38.png|~~261x205px~~center]]

<big>'''Please select balenaEtcher, right-click, and select Run as administrator.'''</big>

[[File:~~media/image39~~plus5-img39.png|~~300x104px|图形用户界面, 文本, 应用程序描述已自动生成~~center]]

</div>

[[File:~~media/image40~~plus5-img40.png~~|501x281px|03~~]]

</div></ol>

<li>The interface displayed in the process of burning the Linux image by balenaEtcher is shown in the figure below, and the progress bar displays purple, indicating that the Linux image is being burned into the TF card.</li>

[[File:~~media/image41~~plus5-img41.png~~|506x317px~~]]

</ol>

<li>After burning the Linux image, balenaEtcher will also verify the image burned to the TF card by default to ensure that there is no problem in the burning process. As shown in the figure below, a green progress bar indicates that the image has been burnt, and balenaEtcher is verifying the burnt image.</li>

[[File:~~media/image42~~plus5-img42.png~~|519x325px~~]]

</ol>

<li>After successful burning, the display interface of balenaEtcher is as shown in the figure below. If the green indicator icon is displayed, it means that the image burning is successful. At this time, you can exit balenaEtcher, and then pull out the TF card and insert it into the TF card slot of the development board.</li>

[[File:~~media/image43~~plus5-img43-1.png~~|523x324px~~]]

</ol>

# First, you need to prepare a data cable with a good quality Type-C interface

::[[File:~~media/image21~~plus5-img21.png~~|193x196px~~]]

<li>Then insert the TF card into the card slot of the development board</li>

[[File:~~media/image44~~plus5-img44.png~~|300x87px~~]]

</ol>

<li>Then download Rockchip '''DriverAssitant_v5.12.zip''' and MiniLoader and the burning tool '''RKDevTool_Release_v2.96.~~zipRKDevTool_Release_v3~~zip RKDevTool_Release_v3.15.zip''' from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''], please ensure that the version of the downloaded RKDevTool tool is v2.96

<li>On the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''], first select the official tool, and then enter the following folder.</li>

[[File:~~media/image45~~plus5-img45.png~~|382x97px~~]]

</ol>

<li>Then download all the files below</li>

[[File:~~media/image46~~plus5-img46.png~~|392x145px~~]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

</li></ol>

<li>Then download the Linux operating system image file compression package that you want to burn from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''], and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system , the size is generally more than 2GB</li>

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

<big>'''Note, if you download the OpenWRT image, you will see the following two types of images in the download link of the OpenWRT image, please download the image file in the "TF card, eMMC and NVME SSD boot image" folder.'''</big>

[[File:~~media/image34~~plus5-img34.png|~~301x95px~~center]]

|}

</ol>

<li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>

[[File:~~media/image47~~plus5-img47.png~~|575x169px~~]]

</ol>

<li>Click the "'''Driver Installation'''" button</li>

[[File:~~media/image48~~plus5-img48.png~~|300x157px~~]]

</ol>

<li>After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button.</li>

[[File:~~media/image49~~plus5-img49.png~~|429x223px~~]]

</ol>

</li></ol>

<li>Then decompress '''RKDevTool_Release_v2.96.zipRKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li>

[[File:~~media/image50~~plus5-img50.png~~|575x170px~~]]

</ol>

<li>After opening the '''RKDevTool''' burning tool, because the computer has not been connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li>

[[File:~~media/image51~~plus5-img51.png~~|402x189px~~]]

</ol>

[[File:~~media/image52.jpeg|400x113px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~plus5-2img52.~~jpg未标题-2~~png]]

</div></ol>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below：</li>

[[File:~~media/image53~~plus5-img53.png~~|382x93px~~]]

</ol>

<li>Finally, connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button. The location of the Type-C power interface is as follows：</li>

[[File:~~media/image54~~plus5-img54.png~~|404x123px~~]]

</ol>

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li>

[[File:~~media/image55~~plus5-img55.png~~|457x215px~~]]

</ol>

[[File:~~media/image56~~plus5-img56.png~~|455x216px|图片1~~]]

</div></ol>

<li>Then click the right mouse button and the selection interface shown in the figure below will pop up</li>

[[File:~~media/image57~~plus5-img57.png~~|453x213px~~]]

</ol>

<li>Then select the '''import configuration''' option</li>

[[File:~~media/image58~~plus5-img58.png~~|458x215px~~]]

</ol>

<li>Then select the '''rk3588_linux_tfcard.cfg''' configuration file in the '''MiniLoader''' folder downloaded earlier, and click '''Open'''</li>

[[File:~~media/image59~~plus5-img59.png~~|483x227px~~]]

</ol>

<li>Then click '''OK'''</li>

[[File:~~media/image60~~plus5-img60.png~~|483x227px~~]]

</ol>

<li>Then click the position shown in the figure below</li>

[[File:~~media/image61~~plus5-img61.png~~|486x228px~~]]

</ol>

<li>Then select '''MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and then click to '''open'''</li>

[[File:~~media/image62~~plus5-img62.png~~|492x231px~~]]

</ol>

<li>Then click the position shown in the figure below</li>

[[File:~~media/image63~~plus5-img63.png~~|493x232px~~]]

</ol>

|}

[[File:~~media/image64~~plus5-img64.png~~|499x234px~~]]

</ol>

<li>Then please check the '''option to force writing by address'''</li>

[[File:~~media/image65~~plus5-img65.png~~|489x230px~~]]

</ol>

<li>Then click the execute button to start burning the linux image to the tf card of the development board</li>

[[File:~~media/image66~~plus5-img66.png~~|492x231px~~]]

</ol>

[[File:~~media/image67~~plus5-img67.png~~|492x231px|%O4~FPPAT$0RH{3S~CGJ@@Q(1)~~]]

</div></ol>

[[File:~~media/image68~~plus5-img68.png~~|209x228px|选区_199~~]]

</div></ol>

<li>Then click "'''Format'''", a warning box will pop up before formatting, and formatting will start after selecting "'''Yes (Y)'''"</li>

[[File:~~media/image69~~plus5-img69.png~~|304x147px~~]]

</ol>

<li>After formatting the TF card, the message shown in the figure below will pop up, click OK</li>

[[File:~~media/image70~~plus5-img70.png~~|186x149px~~]]</ol>

</li></ol>

<li>Download the image file compression package of the Linux operating system that you want to burn from the '''Orange Pi ~~data~~ 's download page''', and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system. The size is generally more than 2GB</li>

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

<big>'''Note, if you download the OpenWRT image, you will see the following two types of images in the download link of the OpenWRT image, please download the image file in the "TF card, eMMC and NVME SSD boot image" folder.'''</big>

[[File:~~media/image34~~plus5-img34.png|~~309x98px~~center]]

|}

</ol>

<li>After downloading, install it directly. The interface of ~~>~~ Win32Diskimager is as follows</li>

a) First select the path of the image file

[[File:~~media/image71~~plus5-img71.png~~|297x206px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\a8fda8737c5b0b3b38fbb75ef68acfc.pnga8fda8737c5b0b3b38fbb75ef68acfc~~]]

</div></ol>

|-

|

<big>'''Note that the Linux image mentioned here specifically refers to the image of Linux distributions such as Debian, Ubuntu, OpenWRT or OPi OS Arch downloaded from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''], and the Ubuntu PC refers to the personal computer with the Ubuntu system installed.'''</big>

|}

<li>After entering the balenaEtcher download page, click the green download button to jump to the place where the software is downloaded</li>

[[File:~~media/image35~~plus5-img35.png~~|575x276px~~]]

</ol>

<li>Then choose to download the Linux version of the software</li>

[[File:~~media/image72~~plus5-img72.png~~|575x218px~~]]

</ol>

<li>Download the Linux operating system image file compression package that you want to burn from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''], and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system. The size is generally more than 2GB</li>

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

[[File:~~media/image73~~plus5-img73.png|~~275x87px|e6986fc9c8fc078e8cb6a9c39b76fb8~~center]]

</div>

<li>Then double-click '''balenaEtcher-1.14.3-x64.AppImage''' on the graphical interface of Ubuntu PC to open balenaEtcher (no installation required), and the interface after balenaEtcher is opened is shown in the figure below</li>

[[File:~~media/image74~~plus5-img74.png~~|423x251px~~]]

</ol>

[[File:~~media/image40~~plus5-img40.png~~|501x281px|03~~]]

</div></ol>

<li>The interface displayed in the process of burning the Linux image by balenaEtcher is shown in the figure below, and the progress bar displays purple, indicating that the Linux image is being burned into the TF card</li>

[[File:~~media/image75~~plus5-img75.png~~|576x247px~~]]

</ol>

<ol start="1211" style="list-style-type: decimal;"><li>~~The interface displayed in the process of~~ After burning the Linux image , balenaEtcher will also verify the image burned into the TF card by ~~balenaEtcher~~ default to ensure that there is no problem in the burning process. As shown in the figure below, ~~and the~~ a green progress bar ~~displays purple, indicating~~ indicates that the ~~Linux~~ image has been burnt, and balenaEtcher is ~~being burned into~~ verifying the ~~TF card~~burnt image</li>

[[File:~~media/image76~~plus5-img76.png~~|576x252px~~]]

</ol>

<li>After successful burning, the display interface of balenaEtcher is as shown in the figure below. If a green indicator icon is displayed, it means that the image burning is successful. At this time, you can exit balenaEtcher, and then pull out the TF card and insert it into the TF card slot of the development board for use.

[[File:~~media/image77~~plus5-img77.png~~|576x340px~~]]</li></ol>

|-

|

<big>'''Note that the Linux image mentioned here specifically refers to the image of Linux distributions such as Debian, Ubuntu, OpenWRT or OPi OS Arch downloaded from the''' [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page''']</big>

|}

# The development board reserves the expansion interface of the eMMC module. Before programming the system to the eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The location of the eMMC interface is as follows：

::[[File:~~media/image78~~plus5-img78-1.png]][[File:plus5-img78-2.png]] ::[[File:plus5-img78-3.png~~|307x141px~~]]

<li>It is also necessary to prepare a data cable with a good quality Type-C interface</li>

[[File:~~media/image21~~plus5-img21.png~~|150x152px~~]]

</ol>

<li>Then download Rockchip '''DriverAssitant_v5.12.zip''' and '''MiniLoader''' and the burning tool RKDevTool_Release_v2.96.zipRKDevTool_Release_v3.15.zip from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''], please make sure that the version of the downloaded RKDevTool tool is v2.96.

<li>On the download page of Orange Pi, first select the official tool, and then enter the following folder</li>

[[File:~~media/image79~~plus5-img79.png~~|408x99px|c40e71d1a66216e12b3b4297138f749~~]]

</div></ol>

[[File:~~media/image80~~plus5-img80.png~~|337x138px|2feec28318eaa60c0514000158b889a~~]]

</div></ol>

</li></ol>

<li>Then download the Linux operating system image file compression package that you want to burn from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''], and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system , the size is generally more than 2GB</li>

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

[[File:~~media/image73~~plus5-img73.png|~~340x108px|e6986fc9c8fc078e8cb6a9c39b76fb8~~center]]

</div>

<li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>

[[File:~~media/image47~~plus5-img47.png~~|496x146px~~]]

</ol>

<li>Click the "'''Driver Installation'''" button</li>

[[File:~~media/image48~~plus5-img48.png~~|284x149px~~]]

</ol>

<li>After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button.</li>

[[File:~~media/image49~~plus5-img49.png~~|296x154px~~]]

</ol>

</li></ol>

<li>Then decompress RKDevTool_Release_v3.15.zip, this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li>

[[File:~~media/image50~~plus5-img50.png~~|484x143px~~]]

</ol>

<li>After opening the '''RKDevTool''' burning tool, because the computer has not been connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li>

[[File:~~media/image51~~plus5-img51.png~~|442x208px~~]]

</ol>

[[File:~~media/image52.jpeg|403x114px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~plus5-2img52.~~jpg未标题-2~~png]]

</div></ol>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:</li>

[[File:~~media/image53~~plus5-img53.png~~|418x94px~~]]

</ol>

<li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button</li>

[[File:~~media/image54~~plus5-img54.png~~|407x124px~~]]

</ol>

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li>

[[File:~~media/image55~~plus5-img55.png~~|457x215px~~]]

</ol>

<li>Then place the mouse cursor in the area below</li>

[[File:~~media/image81~~plus5-img81-1.png~~|458x215px~~]]

</ol>

<li>Then click the right mouse button and the selection interface shown in the figure below will pop up</li>

[[File:~~media/image57~~plus5-img57.png~~|460x216px~~]]

</ol>

<li>Then select the '''import configuration''' option</li>

[[File:~~media/image58~~plus5-img58.png~~|458x215px~~]]

</ol>

<li>Then select the '''rk3588_linux_emmc.cfg''' configuration file in the '''MiniLoader''' folder downloaded earlier, and click '''Open'''</li>

[[File:~~media/image82~~plus5-img82.png~~|466x219px~~]]

</ol>

<li>Then click '''OK'''</li>

[[File:~~media/image83~~plus5-img83.png~~|468x220px~~]]

</ol>

<li>Then click the position shown in the figure below</li>

[[File:~~media/image84~~plus5-img84.png~~|462x217px~~]]

</ol>

<li>Then select '''MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and then click to '''open'''</li>

[[File:~~media/image85~~plus5-img85.png~~|463x217px~~]]

</ol>

<li>Then click the position shown in the figure below</li>

[[File:~~media/image86~~plus5-img86.png~~|459x216px~~]]

</ol>

<big>'''Before burning the image, it is recommended to rename the linux image to be burned to orangepi.img or other shorter names, so that you can see the percentage value of the burning progress when burning the image.'''</big>

[[File:~~media/image64~~plus5-img64.png~~|499x234px~~]]

|}

</ol>

<li>Then please check the option to '''force writing by address'''</li>

[[File:~~media/image87~~plus5-img87.png~~|501x235px~~]]

</ol>

<li>Then click the execute button to start burning the linux image to the eMMC of the development board</li>

[[File:~~media/image88~~plus5-img88.png~~|502x236px~~]]

</ol>

<li>The log displayed after burning the linux image is shown in the figure below</li>

[[File:~~media/image89~~plus5-img89.png~~|500x235px~~]]

</ol>

<li>After burning the linux image into the eMMC, the linux system will start automatically.</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note, after burning the image into eMMC, if the test finds that it cannot be started, please clear the SPIFlash and try again. For the method of clearing SPIFlash, please refer to the method of using RKDevTool to clear SPIFlash.'''</big>|}</ol>

</li></ol>

|-

|

<big>'''Note that the Linux image mentioned here specifically refers to the image of Linux distributions such as Debian, Ubuntu, OpenWRT or OPi OS Arch downloaded from the Orange Pi ~~data~~ 's download page.'''</big>

|}

# The development board reserves the expansion interface of the eMMC module. Before programming the system to the eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The location of the eMMC interface is as follows:

::[[File:~~media/image78~~plus5-img78-1.png]][[File:plus5-img78-2.png]] ::[[File:plus5-img78-3.png~~|312x143px~~]]

<li>After using the TF card to start the linux system, we first upload the decompressed linux image file (Debian, Ubuntu image or OPi Arch image downloaded from the official website) to the TF card. For the method of [[Orange Pi 5 Plus#The method of uploading files to the Linux system of the development board|'''uploading the linux image file to the development board,''']] please refer to the description in the section of the method of uploading files to the development board Linux system.</li>

<li>After uploading the image to the linux system of the development board, we enter the storage path of the image file in the command line of the linux system of the development board. For example, I store the linux image of the development board in the '''/home/orangepi/Desktop''' directory Download it, and then enter the /'''/home/orangepi/Desktop''' directory to see the uploaded image file.</li>

{| class="wikitable" style="width:800px;"

|-

|

<big>'''Note that the Linux image mentioned here specifically refers to the image of Linux distributions such as Debian, Ubuntu, OpenWRT or OPi OS Arch downloaded from the''' [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''].</big>

|}

# First, you need to prepare an M-Key 2280 specification NVMe SSD solid state drive, and the specification of the PCIe interface in the M.2 slot of the development board is PCIe3.0x4.

::[[File:~~media/image25~~plus5-img25.png~~|306x89px~~]]

<li>Then insert the NVMe SSD into the M.2 PCIe interface of the development board shown in the figure below, and fix it</li>

[[File:~~media/image90~~plus5-img90.png~~|274x110px~~]]

</ol>

<li>The position of the SPI Flash on the development board is shown in the figure below, no other settings are required before starting the programming</li>

[[File:~~media/image91~~plus5-img91.png~~|416x115px~~]]

</ol>

[[File:~~media/image92~~plus5-img92.png~~|355x174px|IMG_256~~]]

</div></ol>

[[File:~~media/image93~~plus5-img93.png~~|356x179px|IMG_256~~]]

</div></ol>

<li>Then please wait patiently for the burning to complete. After the burning is completed, the display will be as follows (a '''Done''' will be displayed in the lower left corner):</li>

[[File:~~media/image94~~plus5-img94.png~~|406x199px~~]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

[[File:~~media/image73~~plus5-img73.png|~~284x90px|e6986fc9c8fc078e8cb6a9c39b76fb8~~center]]

</div>

# First, you need to prepare an M-Key 2280 specification NVMe SSD solid state drive, and the specification of the PCIe interface in the M.2 slot of the development board is PCIe3.0x4.

::[[File:~~media/image25~~plus5-img25.png~~|375x108px~~]]

<li>Then insert the NVMe SSD into the M.2 PCIe interface of the development board shown in the figure below, and fix it</li>

[[File:~~media/image90~~plus5-img90.png~~|349x140px~~]]

</ol>

<li>The position of the SPI Flash on the development board is shown in the figure below, no other settings are required before starting the programming</li>

[[File:~~media/image91~~plus5-img91.png~~|395x109px~~]]

</ol>

<li>Burning the linux image to SPIFlash+NVMe SSD needs to be done with a TF card, so first you need to burn the linux image to the TF card, and then use the TF card to start the development board to enter the linux system. For the method of burning the Linux image to the TF card, please refer to the instructions in the two sections of [[Orange Pi 5 Plus#Method of burning Linux image to TF card based on Windows PC|'''the method of burning the Linux image to the TF card based on the Windows PC''']] and [[Orange Pi 5 Plus#Method of burning Linux image to TF card based on Ubuntu PC|'''the method of burning the Linux image to the TF card based on the Ubuntu PC''']].</li>

<li>After booting into the linux system in the TF card, please confirm that the NVMe SSD has been recognized by the linux system of the development board. If the NVMe SSD is recognized normally, use the '''sudo fdisk -l'''command to see nvme-related information</li>

{| class="wikitable" style="width:800px;"

[[File:~~media/image95~~plus5-img95.png~~|506x249px|IMG_256~~]]

</div>

[[File:~~media/image96~~plus5-img96.png~~|406x207px|IMG_256~~]]

</div></ol>

[[File:~~media/image97~~plus5-img97.png~~|406x205px|IMG_256~~]]

</div></ol>

<li>Then enter the '''/usr/lib/linux-u-boot-legacy-orangepi5plus_1.x.x_arm64''' directory, select '''rkspi_loader.img''', and click '''Open''' to open</li>

[[File:~~media/image98~~plus5-img98.png~~|575x162px~~]]

</ol>

<li>The interface after opening '''rkspi_loader.img''' is as follows:</li>

[[File:~~media/image99~~plus5-img99.png~~|379x181px~~]]

</ol>

[[File:~~media/image100~~plus5-img100.png~~|379x171px|IMG_256~~]]

</div></ol>

[[File:~~media/image101~~plus5-img101.png~~|385x155px|IMG_256~~]]

</div></ol>

[[File:~~media/image102~~plus5-img102.png~~|389x264px|IMG_256~~]]

</div></ol>

<li>Then click'''Flash'''</li>

[[File:~~media/image103~~plus5-img103.png~~|394x268px|IMG_256~~]]

</div></ol>

<li>Then click'''Yes, I’m sure'''</li>

[[File:~~media/image104~~plus5-img104.png~~|396x269px|IMG_256~~]]

</div></ol>

[[File:~~media/image105~~plus5-img105.png~~|393x269px|IMG_256~~]]

</div></ol>

[[File:~~media/image106~~plus5-img106.png~~|397x272px|IMG_256~~]]

</div></ol>

[[File:~~media/image107~~plus5-img107.png~~|395x225px|IMG_256~~]]

</div></ol>

[[File:~~media/image108~~plus5-img108.png~~|386x204px|IMG_256~~]]

</div></ol>

[[File:~~media/image109~~plus5-img109.png~~|386x261px|IMG_256~~]]

</div></ol>

[[File:~~media/image110~~plus5-img110.png~~|381x191px|IMG_256~~]]

</div></ol>

[[File:~~media/image100~~plus5-img100.png~~|379x171px|IMG_256~~]]

</div></ol>

[[File:~~media/image101~~plus5-img101.png~~|385x155px|IMG_256~~]]

</div></ol>

<li>Then select the device name of the NVMe SSD '''/dev/nvme0n1''', and click '''Select'''</li>

[[File:~~media/image111~~plus5-img111.png~~|386x264px~~]]

</ol>

[[File:~~media/image112~~plus5-img112.png~~|389x264px|IMG_256~~]]

</div></ol>

[[File:~~media/image113~~plus5-img113.png~~|392x268px|IMG_256~~]]

</div></ol>

[[File:~~media/image114~~plus5-img114.png~~|390x267px|IMG_256~~]]

</div></ol>

<li>The display of the burning process is as follows:</li>

[[File:~~media/image115~~plus5-img115.png~~|393x212px~~]]

[[File:~~media/image116~~plus5-img116.png~~|395x205px|IMG_256~~]]

</div></ol>

<li>After the burning is completed, the display is as follows:</li>

[[File:~~media/image117~~plus5-img117.png~~|398x227px~~]]

</ol>

<li>Then you need to expand the capacity of the rootfs partition in the NVMe SSD. The steps are as follows:

<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) open first '''GParted''', if the system does not have Gparted pre-installed, please use the apt command to install it</li> {| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt-get install -y gparted'''|}

[[File:~~media/image118~~plus5-img118.png~~|590x317px|IMG_256~~]]

</div></ol>

<ol start="2" style="list-style-type: ~~lower-alpha~~none;"><li>b) Then enter the password orangepi of the linux system, and then click '''Authenticate'''</li>

[[File:~~media/image119~~plus5-img119.png~~|356x173px~~]]

</ol>

<ol start="3" style="list-style-type: ~~lower-alpha~~none;"><li>c) Then click '''Fix'''</li>

[[File:~~media/image120~~plus5-img120.png~~|375x276px~~]]

</ol>

<ol start="4" style="list-style-type: ~~lower-alpha~~none;"><li>d) Then select NVMe SSD</li>

[[File:~~media/image121~~plus5-img121.png~~|452x187px|IMG_256~~]]

</div></ol>

<ol start="5" style="list-style-type: ~~lower-alpha~~none;"><li>e) The display interface after selecting NVMe SSD is as follows:</li>

[[File:~~media/image122~~plus5-img122.png~~|451x187px|IMG_256~~]]

</div></ol>

<ol start="6" style="list-style-type: ~~lower-alpha~~none;"><li>f) Then select the '''/dev/nvme0n1p2''' partition, then right-click, and then select '''Resize/Move'''</li>

[[File:~~media/image123~~plus5-img123.png~~|448x345px|IMG_256~~]]

</div></ol>

<ol start="7" style="list-style-type: ~~lower-alpha~~none;"><li>g) Then drag the capacity to the maximum at the position shown in the figure below</li>

[[File:~~media/image124~~plus5-img124.png~~|339x210px~~]]

</ol>

<ol start="8" style="list-style-type: ~~lower-alpha~~none;"><li>h) and click '''Resize/Move'''</li>

[[File:~~media/image125~~plus5-img125.png~~|339x212px~~]]

</ol>

<ol start="9" style="list-style-type: ~~lower-roman~~none;"><li>i) Then click the green one in the picture below'''√'''</li>

[[File:~~media/image126~~plus5-img126.png~~|425x166px~~]]

</ol>

<ol start="10" style="list-style-type: ~~lower-alpha~~none;"><li>j) Click again '''Apply'''</li>

[[File:~~media/image127~~plus5-img127.png~~|378x276px~~]]

</ol>

<ol start="11" style="list-style-type: ~~lower-alpha~~none;"><li>k) Then click '''Close''' to close</li>

[[File:~~media/image128~~plus5-img128.png~~|383x234px~~]]

</ol>

</li></ol>

<li>Step '''9)''' is to clone the system in the TF card to the NMVe SSD. We can also directly burn the linux image file to the NVMe SSD. Here are the steps:

<li>Upload the linux image file to the linux system of the development board</li>

[[File:~~media/image129~~plus5-img129.png~~|575x361px|图片1~~]]

</div></ol>

# First, you need to prepare an M-Key 2280 specification NVMe SSD solid state drive, and the specification of the PCIe interface in the M.2 slot of the development board is PCIe3.0x4.

::[[File:~~media/image25~~plus5-img25.png~~|261x75px~~]]

<li>Then insert the NVMe SSD into the M.2 PCIe interface of the development board shown in the figure below, and fix it</li>

[[File:~~media/image90~~plus5-img90.png~~|259x104px~~]]

</ol>

<li>The position of the SPI Flash on the development board is shown in the figure below, no other settings are required before starting the programming</li>

[[File:~~media/image91~~plus5-img91.png~~|340x94px~~]]

</ol>

<li>Then you need to prepare a data cable with good quality Type-C interface</li>

[[File:~~media/image21~~plus5-img21.png~~|123x124px~~]]

</ol>

<li>Then download the Rockchip driver '''DriverAssitant_v5.12.zip''' and MiniLoader and the burning tool '''RKDevTool_Release_v3.15.zip''' from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page''']

<li>On the download page of Orange Pi, first select the official tool, and then enter the following folder</li>

[[File:~~media/image79~~plus5-img79.png~~|371x90px|c40e71d1a66216e12b3b4297138f749~~]]

</div></ol>

[[File:~~media/image80~~plus5-img80.png~~|340x140px|2feec28318eaa60c0514000158b889a~~]]

</div></ol>

</li></ol>

<li>Then download the Linux operating system image file compression package that you want to burn from the Orange Pi ~~data~~ 's download page, and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system , the size is generally more than 2GB</li>

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

[[File:~~media/image73~~plus5-img73.png|~~340x108px|e6986fc9c8fc078e8cb6a9c39b76fb8~~center]]

</div>

<li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', then find '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>

[[File:~~media/image47~~plus5-img47.png~~|429x126px~~]]

</ol>

<li>Click the "'''Driver Installation'''" button</li>

[[File:~~media/image48~~plus5-img48.png~~|300x157px~~]]

</ol>

<li>After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button.</li>

[[File:~~media/image49~~plus5-img49.png~~|324x168px~~]]

</ol>

</li></ol>

<li>Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li>

[[File:~~media/image50~~plus5-img50.png~~|455x135px~~]]

</ol>

<li>After opening the '''RKDevTool''' burning tool, because the computer is not connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li>

[[File:~~media/image51~~plus5-img51.png~~|436x205px~~]]

</ol>

[[File:~~media/image52.jpeg|446x126px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~plus5-2img52.~~jpg未标题-2~~png]]

</div></ol>

<li>Then press and hold the MaskROM button on the development board. The position of the MaskROM button on the development board is shown in the figure below:</li>

[[File:~~media/image53~~plus5-img53.png~~|424x103px~~]]

</ol>

<li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button. The location of the Type-C power interface is as follows:</li>

[[File:~~media/image54~~plus5-img54.png~~|439x134px~~]]

</ol>

<li>If the previous steps are successful, the development board will enter the MASKROM mode at this time, and the interface of the burning tool will prompt "'''Found a MASKROM device'''"</li>

[[File:~~media/image55~~plus5-img55.png~~|457x215px~~]]

</ol>

[[File:~~media/image130.jpeg|452x212px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~plus5-4img130.~~jpg未标题-4~~png]]

</div></ol>

<li>Then ~~place~~ click the right mouse ~~cursor~~ button and the selection interface shown in the ~~area~~ figure belowwill pop up</li>

[[File:~~media/image57~~plus5-img57.png~~|453x213px~~]]

</ol>

<li>Then select the '''Import configuration''' option</li>

[[File:~~media/image58~~plus5-img58.png~~|458x215px~~]]

</ol>

<li>Then enter the MiniLoader folder downloaded earlier, then select the '''rk3588_linux_pcie.cfg''' configuration file, and click '''Open'''</li>

[[File:~~media/image131~~plus5-img131.png~~|462x217px~~]]

</ol>

<li>Then click '''OK'''</li>

[[File:~~media/image132~~plus5-img132.png~~|468x220px~~]]

</ol>

<li>Then click the location shown in the figure below</li>

[[File:~~media/image133~~plus5-img133.png~~|480x225px~~]]

</ol>

<li>Then select '''MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and then click to '''open'''</li>

[[File:~~media/image62~~plus5-img62.png~~|484x227px~~]]

</ol>

<li>Then click the position shown in the figure below</li>

[[File:~~media/image134~~plus5-img134.png~~|486x228px~~]]

</ol>

<li>Then enter the '''MiniLoader''' folder downloaded earlier, select '''rkspi_loader.img,''' and click '''Open'''</li>

[[File:~~media/image135~~plus5-img135.png~~|501x235px~~]]

</ol>

<li>Then click the location shown in the figure below</li>

[[File:~~media/image136~~plus5-img136.png~~|501x235px~~]]

</ol>

|}

[[File:~~media/image64~~plus5-img64.png~~|499x234px~~]]

</ol>

<li>Then please check the option to '''force write by address'''</li>

[[File:~~media/image137~~plus5-img137.png~~|487x229px~~]]

</ol>

<li>Click the Execute button again to start burning the u-boot+linux image to SPIFlash+SSD</li>

[[File:~~media/image138~~plus5-img138.png~~|489x230px~~]]

</ol>

<li>The display log after burning the image is shown in the figure below</li>

[[File:~~media/image139~~plus5-img139.png~~|490x230px~~]] {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If there is a problem with burning, please clear the SPIFlash first and then try burning again. For the method of clearing SPIFlash, please refer to the instructions in the section of using RKDevTool to clear SPIFlash.'''</big>|}

</ol>

::[[File:~~media/image140~~plus5-img140.png~~|329x112px|25566f72fb1f4567c78af07e73b5134~~]]

</div>

# The position of the SPI Flash on the development board is shown in the figure below, no other settings are required before starting the programming

::[[File:~~media/image91~~plus5-img91.png~~|389x107px~~]]

<li>Then you need to prepare a data cable with good quality Type-C interface</li>

[[File:~~media/image21~~plus5-img21.png~~|152x154px~~]]

</ol>

<li>Then download the Rockchip driver '''DriverAssitant_v5.12.zip''' and MiniLoader and the burning tool '''RKDevTool_Release_v3.15.zip''' from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page''']

<li>On the download page of Orange Pi, first select the official tool, and then enter the following folder</li>

[[File:~~media/image73~~plus5-img73.png~~|340x108px|e6986fc9c8fc078e8cb6a9c39b76fb8~~]]

</div></ol>

[[File:~~media/image80~~plus5-img80.png~~|401x165px|2feec28318eaa60c0514000158b889a~~]]

</div></ol>

[[File:~~media/image140~~plus5-img140.png~~|329x112px|25566f72fb1f4567c78af07e73b5134~~]]

</div></ol>

<li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>

[[File:~~media/image47~~plus5-img47.png~~|472x139px~~]]

</ol>

<li>Click the "'''Driver Installation'''" button</li>

[[File:~~media/image48~~plus5-img48.png~~|276x145px~~]]

</ol>

<li>After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button.</li>

[[File:~~media/image49~~plus5-img49.png~~|292x151px~~]]

</ol>

</li></ol>

<li>Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li>

[[File:~~media/image50~~plus5-img50.png~~|467x138px~~]]

</ol>

<li>After opening the '''RKDevTool''' burning tool, because the computer has not been connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li>

[[File:~~media/image51~~plus5-img51.png~~|402x189px~~]]

</ol>

[[File:~~media/image52.jpeg|424x120px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~plus5-2img52.~~jpg未标题-2~~png]]

</div></ol>

<li>Then press and hold the MaskROM button on the development board. The position of the MaskROM button on the development board is shown in the figure below:</li>

[[File:~~media/image53~~plus5-img53.png~~|444x100px~~]]

</ol>

<li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button</li>

[[File:~~media/image54~~plus5-img54.png~~|402x123px~~]]

</ol>

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''Found a MASKROM device'''"</li>

[[File:~~media/image55~~plus5-img55.png~~|457x215px~~]]

</ol>

[[File:~~media/image130.jpeg|452x212px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~plus5-4img130.~~jpg未标题-4~~png]]

</div></ol>

<li>Then click the right mouse button and the selection interface shown in the figure below will pop up</li>

[[File:~~media/image57~~plus5-img57.png~~|453x213px~~]]

</ol>

<li>Then select the '''Import configuration''' option</li>

[[File:~~media/image58~~plus5-img58.png~~|458x215px~~]]

</ol>

<li>Then select the '''rk3588_linux_spiflash.cfg''' configuration file in the MiniLoader folder downloaded earlier, and click '''Open'''</li>

[[File:~~media/image141~~plus5-img141.png~~|465x218px~~]]

</ol>

<li>Then click '''OK'''</li>

[[File:~~media/image142~~plus5-img142.png~~|466x219px~~]]

</ol>

<li>Then click the location shown in the figure below</li>

[[File:~~media/image143~~plus5-img143.png~~|467x219px~~]]

</ol>

<li>Then select '''MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and click '''Open'''</li>

[[File:~~media/image144~~plus5-img144.png~~|469x220px~~]]

</ol>

<li>Then click the location shown in the figure below</li>

[[File:~~media/image145~~plus5-img145.png~~|452x212px~~]]

</ol>

</li>

[[File:~~media/image64~~plus5-img64.png~~|456x214px~~]]

</ol>

<li>Then please make sure that the option to '''force writing by address''' is ticked</li>

[[File:~~media/image146~~plus5-img146.png~~|463x217px~~]]

</ol>

<li>Click the '''Execute''' button again to start burning the OpenWRT image into SPIFlash</li>

[[File:~~media/image147~~plus5-img147.png~~|463x218px~~]]

</ol>

<li>The display log after burning the OpenWRT image is shown in the figure below</li>

[[File:~~media/image148~~plus5-img148.png~~|465x219px~~]] {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If there is a problem with burning, please clear the SPIFlash first and then try burning again. For the method of clearing SPIFlash, please refer to the instructions in the section of using RKDevTool to clear SPIFlash.'''</big>|}

</ol>

<li>First prepare a TF card with a capacity of 16GB or greater. The transmission speed of the TF card must be class10 or above. It is recommended to use a TF card of SanDisk and other brands</li>

<li>Then use the card reader to insert the TF card into the computer</li>

<li>Then download the SDDiskTool programming tool from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''], '''please make sure that the version of the SDDiskTool tool is the latest v1.72'''</li>

<li>Then download the Android12 image from the Orange Pi download page

<li>After opening the download link of the Android image, you can see the following two types of Android images, please select the image in the '''TF card and eMMC boot image''' folder to download</li>

[[File:~~media/image149~~plus5-img149.png~~|240x98px~~]]

</ol>

c) The image with box is a image dedicated to the TV box

[[File:~~media/image150~~plus5-img150.png~~|255x97px~~]]

</ol>

</li></ol>

<li>Then use decompression software to decompress '''SDDiskTool_v1.72.zip''', this software does not need to be installed, just find '''SD_Firmware_Tool.exe''' in the decompressed folder and open it</li>

[[File:~~media/image151~~plus5-img151.png~~|575x138px~~]]

</ol>

<li>After opening SDDiskTool, if the TF card is recognized normally, the inserted disk device will be displayed in the "'''Select Removable Disk Device'''" column. '''Please make sure that the displayed disk device is consistent with the drive letter of the TF card you want to burn''' If there is no display, you can try to unplug the TF card</li>

[[File:~~media/image152~~plus5-img152.png~~|267x228px~~]]

</ol>

<li>After confirming the drive letter, you can format the TF card first, click the restore disk button in '''SDDiskTool''', or use the SD Card Formatter mentioned above to format the TF card</li>

[[File:~~media/image153~~plus5-img153.png~~|247x212px~~]]

</ol>

c. Finally click the "'''Start Create'''" button to start burning the Android image to the TF card

[[File:~~media/image154~~plus5-img154.png~~|346x292px~~]]

</ol>

<li>After burning, you can exit the SDDiskTool software, and then you can pull out the TF card from the computer and insert it into the development board to start</li>

[[File:~~media/image155~~plus5-img155.png~~|304x258px~~]]

</ol>

# The development board reserves an eMMC expansion interface. Before programming the system to eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The location of the eMMC interface is as follows:

::[[File:~~media/image78~~plus5-img78-1.png]][[File:plus5-img78-2.png]] ::[[File:plus5-img78-3.png~~|307x141px~~]]

<li>It is also necessary to prepare a data cable with a good quality Type-C interface

[[File:~~media/image21~~plus5-img21.png~~|134x136px~~]]</li><li>Then download Rockchip driver '''DriverAssitant_v5.12.zip''' and burning tool '''RKDevTool_Release_v3.15.zip''' from [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page''']</li><li>Then download the Android image from [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''].</li>

<li>After opening the download link of the Android image, you can see ~~>~~ the following two types of Android images, please select the image ~~>~~ in the '''TF card and eMMC startup image''' folder to download</li>

[[File:~~media/image156~~plus5-img156.png~~|240x98px|4db492fa03e0cf83396c36286128350~~]]

</div></ol>

<li>After entering the TF card and eMMC boot image folder, you can see ~~>~~ the following three images, the difference between them is:</li>

<li>The first image is dedicated to HDMI display and supports 8K ~~>~~ display. If you don’t use LCD screen, please download the image ~~>~~ without lcd</li>

<li>If you want to use lcd screen, please choose image with lcd</li>

<li>The image with box is a image dedicated to the TV box</li>

[[File:~~media/image150~~plus5-img150.png~~|255x97px~~]]

</ol>

<li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>

[[File:~~media/image47~~plus5-img47.png~~|575x169px~~]]

</ol>

<li>Click the "'''Driver Installation'''" button</li>

[[File:~~media/image48~~plus5-img48.png~~|300x157px~~]]

</ol>

<li>After waiting for a period of time, a pop-up window will prompt "driver installed successfully", then click "OK"</li>

[[File:~~media/image49~~plus5-img49.png~~|315x164px~~]]

</ol>

</li></ol>

<li>Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li>

[[File:~~media/image50~~plus5-img50.png~~|454x134px~~]]

</ol>

<li>After opening the '''RKDevTool''' burning tool, because the computer has not been connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li>

[[File:~~media/image51~~plus5-img51.png~~|442x208px~~]]

</ol>

[[File:~~media/image52.jpeg|439x124px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~plus5-2img52.~~jpg未标题-2~~png]]

</div></ol>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below：</li>

[[File:~~media/image53~~plus5-img53.png~~|456x103px~~]]

</ol>

<li>Then connect the power supply of the Type-C interface to the development board, and power on</li>

[[File:~~media/image54~~plus5-img54.png~~|441x135px~~]]

</ol>

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li>

[[File:~~media/image55~~plus5-img55.png~~|457x215px~~]]

</ol>

<li>Then click the "'''Upgrade Firmware'''" column of the burning tool</li>

[[File:~~media/image157~~plus5-img157.png~~|442x208px~~]]

</ol>

<li>Then click the "'''Firmware'''" button to select the path of the Android image that needs to be burned</li>

[[File:~~media/image158~~plus5-img158.png~~|444x209px~~]]

</ol>

<li>Finally, click the "'''Upgrade'''" button to start burning, and the log during the burning process is shown in the figure below. After burning is completed, the Android system will start automatically.

[[File:~~media/image159~~plus5-img159.png~~|449x211px~~]]</li></ol>

</li></ol>

# The development board reserves an eMMC expansion interface. Before programming the system to eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The location of the eMMC interface is as follows:

::[[File:~~media/image78~~plus5-img78-1.png]][[File:plus5-img78-2.png]] ::[[File:plus5-img78-3.png~~|392x180px~~]]

<li>You also need to prepare a TF card with 8GB or larger capacity. The transmission speed of the TF card must be class10 or above. It is recommended to use a TF card of SanDisk and other brands</li>

<li>Then use the card reader to insert the TF card into the computer</li>

<li>Then download the SDDiskTool programming tool from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''], '''please ensure that the version of the SDDiskTool tool is the latest v1.72'''</li><li>Then download the Android image from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page''']

<li>After opening the download link of the Android image, you can see the following two types of Android images, please '''select the image in the TF card and eMMC startup image''' folder to download</li>

[[File:~~media/image156~~plus5-img156.png~~|240x98px|4db492fa03e0cf83396c36286128350~~]]

</div></ol>

<li>The mirror with box is a mirror dedicated to the TV box</li>

[[File:~~media/image150~~plus5-img150.png~~|255x97px~~]]</ol>

</li></ol>

<li>Then use decompression software to decompress the compressed package of the downloaded Android image. Among the decompressed files, the file ending with ".img" is the Android image file, and the size is more than 1GB</li>

<li>Then use decompression software to decompress '''SDDiskTool_v1.72.zip''', this software does not need to be installed, just find '''SD_Firmware_Tool.ex''' in the decompressed folder and open it</li>

~~<li>~~

[[File:~~media/image151~~plus5-img151.png~~|429x103px~~]]~~</li>~~</ol><ol start="98" style="list-style-type: decimal;">

<li>After opening '''SDDiskTool''', if the TF card is recognized normally, the inserted disk device will be displayed in the "'''Select Removable Disk Device'''" column. '''Please make sure that the displayed disk device is consistent with the drive letter of the TF card you want to burn''', if there is no display, you can try to unplug the TF card</li>

[[File:~~media/image152~~plus5-img152.png~~|267x228px~~]]

</ol>

<li>After confirming the drive letter, you can format the TF card first, click the '''restore disk''' button in '''SDDiskTool,''' or use the '''SD Card Formatter''' mentioned above to format the TF card</li>

[[File:~~media/image153~~plus5-img153.png~~|247x212px~~]]

</ol>

<li>Then start to write the Android image into the TF card

<li>Finally click the "'''Start Create'''" button to start burning</li>

[[File:~~media/image160~~plus5-img160.png~~|290x246px~~]]

</ol>

</li></ol>

<li>After the burning is completed, the display is as shown in the figure below, and then you can exit SDDiskTool</li>

~~<li>~~

[[File:~~media/image161~~plus5-img161.png~~|285x243px~~]]~~</li>~~</ol><ol start="1412" style="list-style-type: decimal;">

<li>Then pull out the TF card from the computer and insert it into the development board. After the development board is powered on, it will automatically start burning the Android image in the TF card to the eMMC of the development board.</li>

<li>If the development board is connected to an HDMI display, you can also see the progress bar of burning the Android image to eMMC from the HDMI display</li>

~~<li>~~

[[File:~~media/image162~~plus5-img162.png~~|430x247px~~]]~~</li>~~</ol><ol start="1714" style="list-style-type: decimal;">

<li>When the HDMI monitor displays the following information, it means that the burning of the Android image into the eMMC has been completed. At this time, the TF card can be pulled out, and then the Android system in the eMMC will start.

[[File:~~media/image163~~plus5-img163.png~~|576x389px~~]]</li></ol>

# First, you need to prepare an M-Key 2280 specification NVMe SSD solid state drive, and the specification of the PCIe interface in the M.2 slot of the development board is PCIe3.0x4.

::[[File:~~media/image25~~plus5-img25.png~~|361x104px~~]]

<li>Then insert the NVMe SSD into the M.2 PCIe interface of the development board and fix it</li>

[[File:~~media/image90~~plus5-img90.png~~|355x143px~~]]

</ol>

<li>The position of the SPI Flash on the development board is shown in the figure below, no other settings are required before starting the programming</li>

[[File:~~media/image91~~plus5-img91.png~~|415x114px~~]]

</ol>

<li>It is also necessary to prepare a data cable with a good quality Type-C interface</li>

[[File:~~media/image21~~plus5-img21.png~~|150x152px~~]]

</ol>

<li>Then download Rockchip driver '''DriverAssitant_v5.12.zip''' and burning tool '''RKDevTool_Release_v3.15.zip''' from [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page''']</li><li>Then download the Android12 image from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page''']

<li>After opening the download link of the Android image, you can see the following two types of Android images, please select the image in the '''SPIFlash-NVME SSD boot image''' folder to download</li>

[[File:~~media/image164~~plus5-img164.png~~|234x91px~~]]

</ol>

<li>The image with box is a image dedicated to the TV box</li>

[[File:~~media/image165~~plus5-img165.png~~|241x70px~~]]

</ol>

</li></ol>

<li>Then use the decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>

[[File:~~media/image47~~plus5-img47.png~~|575x169px~~]]

</ol>

:8. After opening DriverInstall.exe, the steps to install the Rockchip driver are as followsa. Click the "'''Driver Install'''" button

::[[File:~~media/image48~~plus5-img48.png~~|300x157px~~]]

:::a. After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", then click the "'''OK'''" button

::::[[File:~~media/image49~~plus5-img49.png~~|429x223px~~]]

:9. Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it

::[[File:~~media/image50~~plus5-img50.png~~|421x124px~~]]

<li>After opening the '''RKDevTool''' burning tool, because the computer is not connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li>

[[File:~~media/image51~~plus5-img51.png~~|442x208px~~]]

</ol>

[[File:~~media/image52.jpeg|418x118px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~plus5-2img52.~~jpg未标题-2~~png]]

</div></ol>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:</li>

[[File:~~media/image53~~plus5-img53.png~~|443x100px~~]]

</ol>

<li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button</li>

[[File:~~media/image54~~plus5-img54.png~~|449x137px~~]]

</ol>

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''Found a MASKROM device'''"</li>

[[File:~~media/image55~~plus5-img55.png~~|457x215px~~]]

</ol>

<li>Then click the "Upgrade Firmware" column of the burning tool</li>

[[File:~~media/image157~~plus5-img157.png~~|442x208px~~]]

</ol>

<li>Then click the "Firmware" button to select the Android image to be burned</li>

[[File:~~media/image158~~plus5-img158.png~~|447x210px~~]]

</ol>

<li>Finally, click the "Upgrade" button to start burning. The burning process is shown in the figure below. After the burning is completed, the Android system will automatically start.</li>

[[File:~~media/image166~~plus5-img166.png~~|450x210px~~]]

</ol>

</li></ol>

# First prepare a TF card with 8GB or larger capacity. The transmission speed of the TF card must be class10 or above. It is recommended to use a TF card of SanDisk and other brands

# Then use the card reader to insert the TF card into the computer

# Then download the SDDiskTool programming tool from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''], '''please make sure that the version of the SDDiskTool tool is the latest v1.72.'''# Then download the Orange Pi OS (Droid) image from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''], open the download link of the Orange Pi OS (Droid) image, and you can see the following two types of images, please select the image below

::[[File:~~media/image167~~plus5-img167.png~~|286x49px~~]]

<li>Then use decompression software to decompress '''SDDiskTool_v1.72.zip''', this software does not need to be installed, just find '''SD_Firmware_Tool.ex''' in the decompressed folder and open it</li>

[[File:~~media/image151~~plus5-img151.png~~|486x117px~~]]

</ol>

<li>After opening '''SDDiskTool''', if the TF card is recognized normally, the inserted disk device will be displayed in the "'''Select Removable Disk Device'''" column. '''Please make sure that the displayed disk device is consistent with the drive letter of the TF card you want to burn''' , if there is no display, you can try to unplug the TF card</li>

[[File:~~media/image152~~plus5-img152.png~~|248x212px~~]]

</ol>

<li>After confirming the drive letter, you can format the TF card first, click the '''restore disk''' button in SDDiskTool, or use the '''SD Card Formatter''' mentioned above to format the TF card</li>

[[File:~~media/image153~~plus5-img153.png~~|261x224px~~]]

</ol>

<li>Finally, click the "'''Start Create'''" button to start burning the Orange Pi OS (Droid) image to the TF card</li>

[[File:~~media/image154~~plus5-img154.png~~|279x236px~~]]

</ol>

</li></ol>

<li>After burning, you can exit the SDDiskTool software, and then you can pull out the TF card from the computer and insert it into the development board to start</li>

[[File:~~media/image155~~plus5-img155.png~~|304x258px~~]]

</ol>

=== Burn Orange Pi OS (Droid) image ~~toeMMC~~ to eMMC ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

# The development board reserves an eMMC expansion interface. Before programming the system to eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The location of the eMMC interface is as follows:

::[[File:~~media/image78~~plus5-img78-1.png]][[File:plus5-img78-2.png]] ::[[File:plus5-img78-3.png~~|324x149px~~]]

<li>It is also necessary to prepare a data cable with a good quality Type-C interface</li>

[[File:~~media/image21~~plus5-img21.png~~|127x129px~~]]

</ol>

<li>Then download Rockchip driver DriverAssitant_v5.12.zip and burning tool '''RKDevTool_Release_v3.15.zip''' from [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page''']</li><li>Then download the Orange Pi OS (Droid) image from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page''']</li>

[[File:~~media/image167~~plus5-img167.png~~|286x49px~~]]

</ol>

<li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>

[[File:~~media/image47~~plus5-img47.png~~|575x169px~~]]

</ol>

<li>Click the "Driver Installation" button</li>

[[File:~~media/image48~~plus5-img48.png~~|300x157px~~]]

</ol>

<li>After waiting for a period of time, a pop-up window will prompt "driver installed successfully", and then click the "OK" button.</li>

[[File:~~media/image49~~plus5-img49.png~~|318x165px~~]]

</ol>

</li></ol>

<li>Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li>

[[File:~~media/image50~~plus5-img50.png~~|575x170px~~]]

</ol>

<li>After opening the '''RKDevTool''' burning tool, because the computer is not connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li>

[[File:~~media/image51~~plus5-img51.png~~|442x208px~~]]

</ol>

[[File:~~media/image52.jpeg|468x132px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~plus5-2img52.~~jpg未标题-2~~png]]

</div></ol>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:</li>

[[File:~~media/image53~~plus5-img53.png~~|479x108px~~]]

</ol>

<li>Then connect the power supply of the Type-C interface to the development board, and power on</li>

[[File:~~media/image54~~plus5-img54.png~~|457x140px~~]]

</ol>

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li>

[[File:~~media/image55~~plus5-img55.png~~|457x215px~~]]

</ol>

<li>Then click the "'''Upgrade Firmware'''" column of the burning tool</li>

[[File:~~media/image157~~plus5-img157.png~~|461x217px~~]]

</ol>

<li>Then click the "'''Firmware'''" button to select the path of the Orange Pi OS (Droid) image that needs to be burned</li>

[[File:~~media/image158~~plus5-img158.png~~|453x213px~~]]

</ol>

<li>Finally, click the "'''Upgrade'''" button to start burning, and the log during the burning process is shown in the figure below. After burning, the Orange Pi OS (Droid) system will start automatically.</li>

[[File:~~media/image168~~plus5-img168.png~~|456x214px~~]]

</ol>

</li></ol>

# The development board reserves an eMMC expansion interface. Before programming the system to eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The location of the eMMC interface is as follows:

::[[File:~~media/image78~~plus5-img78.png~~|342x157px~~]]

<li>You also need to prepare a TF card with 8GB or larger capacity. The transmission speed of the TF card must be class10 or above. It is recommended to use a TF card of SanDisk and other brands</li>

<li>Then use the card reader to insert the TF card into the computer</li>

<li>Then download the SDDiskTool programming tool from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page'''], '''please ensure that the version of the SDDiskTool tool is the latest v1.72.'''</li><li>Then download the Orange Pi OS (Droid) image from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page''']</li>

[[File:~~media/image167~~plus5-img167.png~~|286x49px~~]]

</ol>

<li>Then use decompression software to decompress '''SDDiskTool_v1.72.zip''', this software does not need to be installed, just find '''SD_Firmware_Tool.exe''' in the decompressed folder and open it</li>

[[File:~~media/image151~~plus5-img151.png~~|454x109px~~]]

</ol>

<li>After opening '''SDDiskTool''', if the TF card is recognized normally, the inserted disk device will be displayed in the "'''Select Removable Disk Device'''" column. '''Please make sure that the displayed disk device is consistent with the drive letter of the TF card you want to burn''', if there is no display, you can try to unplug the TF card.</li>

[[File:~~media/image152~~plus5-img152.png~~|267x228px~~]]

</ol>

<li>After confirming the drive letter, you can format the TF card first, click the restore disk button in '''SDDiskTool''', or use the '''SD Card Formatter''' mentioned above to format the TF card</li>

[[File:~~media/image153~~plus5-img153.png~~|267x228px~~]]

</ol>

d. Finally click the "'''Start Create'''" button to start burning

[[File:~~media/image160~~plus5-img160.png~~|289x246px~~]]

</ol>

<li>After the burning is completed, the display is as shown in the figure below, and then you can exit SDDiskTool</li>

[[File:~~media/image161~~plus5-img161.png~~|285x243px~~]]

</ol>

<li>If the development board is connected to an HDMI display, you can also see the progress bar of burning the Orange Pi OS (Droid) image to eMMC from the HDMI display</li>

[[File:~~media/image162~~plus5-img162.png~~|430x247px~~]]

</ol>

<li>When the HDMI monitor displays the following information, it means that the burning of the Orange Pi OS (Droid) image to the eMMC has been completed. At this time, the TF card can be pulled out, and then the Orange Pi OS (Droid) system in the eMMC will start to start .</li>

[[File:~~media/image163~~plus5-img163.png~~|576x389px~~]]

</ol>

# First, you need to prepare a 2280 specification NVMe SSD solid state drive. The specification of the PCIe interface in the M.2 slot of the development board is PCIe3.0x4.

::[[File:~~media/image25~~plus5-img25.png~~|314x91px~~]]

<li>Then insert the NVMe SSD into the M.2 PCIe interface of the development board and fix it</li>

[[File:~~media/image90~~plus5-img90.png~~|323x130px~~]]

</ol>

<li>The position of the SPI Flash on the development board is shown in the figure below, no other settings are required before starting the programming</li>

[[File:~~media/image91~~plus5-img91.png~~|382x105px~~]]

</ol>

<li>It is also necessary to prepare a data cable with a good quality Type-C interface</li>

[[File:~~media/image21~~plus5-img21.png~~|143x145px~~]]

</ol>

<li>Then download the Rockchip driver '''DriverAssitant_v5.12.zip''' and the burning tool '''RKDevTool_Release_v3.15.zip''' from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page''']，</li>

<li>Then download the Orange Pi OS (Droid) image, open the download link of the Orange Pi OS (Droid) image and you can see the following two types of images, please select the image with '''spi-nvme''' to download</li>

[[File:~~media/image169~~plus5-img169.png~~|352x62px~~]]

</ol>

<li>Then use the decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>

[[File:~~media/image47~~plus5-img47.png~~|423x124px~~]]

</ol>

<li>Click the "Driver Installation" button</li>

[[File:~~media/image48~~plus5-img48.png~~|268x140px~~]]

</ol>

<li>After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button.</li>

[[File:~~media/image49~~plus5-img49.png~~|301x156px~~]]

</ol>

</li></ol>

<li>Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li>

[[File:~~media/image50~~plus5-img50.png~~|455x134px~~]]

</ol>

<li>After opening the '''RKDevTool''' burning tool, because the computer is not connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li>

[[File:~~media/image51~~plus5-img51.png~~|442x208px~~]]

</ol>

[[File:~~media/image52.jpeg|435x123px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~plus5-2img52.~~jpg未标题-2~~png]]

</div></ol>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:</li>

[[File:~~media/image53~~plus5-img53.png~~|460x103px~~]]

</ol>

<li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button</li>

[[File:~~media/image54~~plus5-img54.png~~|440x134px~~]]

</ol>

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li>

[[File:~~media/image55~~plus5-img55.png~~|457x215px~~]]

</ol>

<li>Then click the "'''Upgrade Firmware'''" column of the burning tool</li>

[[File:~~media/image157~~plus5-img157.png~~|457x215px~~]]

</ol>

<li>Then click the "'''Firmware'''" button to select the Orange Pi OS (Droid) image to be burned</li>

[[File:~~media/image158~~plus5-img158.png~~|472x222px~~]]

</ol>

<li>Finally, click the "'''Upgrade'''" button to start burning. The burning process is shown in the figure below. After the burning is completed, the Orange Pi OS (Droid) system will automatically start.

[[File:~~media/image170~~plus5-img170.png~~|476x225px~~]]</li></ol>

</li></ol>

<li>The position of SPI Flash on the development board is shown in the figure below

[[File:~~media/image91~~plus5-img91.png~~|389x107px~~]]</li>

<li>First, you need to prepare a data cable with a good quality Type-C interface

[[File:~~media/image21~~plus5-img21.png~~|152x154px~~]]</li><li>Then download the Rockchip driver '''DriverAssitant_v5.12.zip''' and '''MiniLoader''' and the burning tool '''RKDevTool_Release_v3.15.zip''' from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''Orange Pi ~~data~~ 's download page''']

<li>On the Orange Pi ~~data~~ 's download page, first select the '''official tool''', and then enter the following folder[[File:~~media/image171~~plus5-img171.png~~|486x155px~~]]</li>

<li>Then download all the files below

[[File:~~media/image172~~plus5-img172.png~~|389x175px~~]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

</li>

<li>Then use the decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it

[[File:~~media/image47~~plus5-img47.png~~|472x139px~~]]</li>

<li>After opening '''DriverInstall.exe''', the steps to install the Rockchip driver are as follows

<li>Click the "'''Driver Installation'''" button

[[File:~~media/image48~~plus5-img48.png~~|276x145px~~]]</li>

<li>After waiting for a period of time, a pop-up window will prompt "'''The driver is installed successfully'''", and then click the "'''OK'''" button.

[[File:~~media/image49~~plus5-img49.png~~|292x151px~~]]</li></ol>

</li>

<li>Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it

[[File:~~media/image50~~plus5-img50.png~~|467x138px~~]]</li>

<li>After opening the '''RKDevTool''' burning tool, because the computer has not been connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"

[[File:~~media/image51~~plus5-img51.png~~|402x189px~~]]</li>

<li>Then you can start to clear the contents of the SPI FLASH

[[File:~~media/image173.jpeg|424x120px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~plus5-1img173.~~jpg未标题-1~~png]]

</div></li>

<li>Make sure the development board is not connected to the power supply</li>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:

[[File:~~media/image53~~plus5-img53.png~~|444x100px~~]]</li>

<li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button

[[File:~~media/image54~~plus5-img54.png~~|402x123px~~]]</li>

<li>If the previous steps are smooth, at this time the development board will enter the '''Maskrom''' mode, and it will be prompted "'''Find a Maskrom device'''" on the interface of the recording tool

[[File:~~media/image55~~plus5-img55.png~~|457x215px~~]]</li>

<li>Then please select '''advanced features'''

[[File:~~media/image174~~plus5-img174.png~~|458x138px~~]]</li>

<li>Then click the position shown in the figure below

[[File:~~media/image175~~plus5-img175.png~~|459x216px~~]]</li>

<li>Then select '''MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and then click Open

[[File:~~media/image144~~plus5-img144.png~~|469x220px~~]]</li>

<li>Then click '''download'''

[[File:~~media/image176~~plus5-img176.png~~|472x222px~~]]</li>

<li>The display after downloading '''MiniLoaderAll.bin''' is shown in the figure below

[[File:~~media/image177~~plus5-img177.png~~|474x223px~~]]</li>

<li>Then select the storage device as '''SPINOR'''

[[File:~~media/image178~~plus5-img178.png~~|467x220px~~]]</li>

<li>Then click '''switch storage'''

[[File:~~media/image179~~plus5-img179.png~~|464x218px~~]]</li>

<li>Then click '''Erase All''' to start erasing SPIFlash

[[File:~~media/image180~~plus5-img180.png~~|467x220px~~]]</li>

<li>The display log after erasing SPIFlash is shown in the figure below

[[File:~~media/image181~~plus5-img181.png~~|450x212px~~]]</li></ol>

</li></ol>

[[File:~~media/image182~~plus5-img182.~~jpeg~~png|~~262x234px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\01.jpg01~~center]]

</div>

::[[File:~~media/image183~~plus5-img183.png~~|576x115px|07~~]]

</div>

<li>The corresponding relationship between GND, RXD and TXD pins of the debugging serial port of the development board is shown in the figure below:

[[File:~~media/image184~~plus5-img184.png~~|485x174px~~]]</li>

<li>The GND, TXD and RXD pins of the USB to TTL module need to be connected to the debugging serial port of the development board through a DuPont line

[[File:~~media/image185~~plus5-img185.png~~|524x189px|08~~]]

</div>

</li>

<li>After executing the putty command, the following interface will pop up

[[File:~~media/image186~~plus5-img186.png~~|367x321px~~]]</li>

<li>First select the setting interface of the serial port

[[File:~~media/image187~~plus5-img187.png~~|359x352px~~]]</li>

<li>Then set the parameters of the serial port

<li>Set the Serial line to connect to as /dev/ttyUSB0 (modify to the ~~>~~ corresponding node name, generally /dev/ttyUSB0)</li><li>Set Speed(baud) to '''1500000''' (the baud rate of the serial ~~>~~ port)</li>

<li>Set Flow control to None

[[File:~~media/image188~~plus5-img188.png~~|317x312px|09~~]]

</div></li></ol>

[[File:~~media/image189~~plus5-img189.png~~|345x340px|10~~]]

</div></li></ol>

</li>

<li>After starting the development board, you can see the Log information output by the system from the opened serial port terminal

[[File:~~media/image190~~plus5-img190.png~~|287x208px~~]]</li></ol>

=== How to use the debugging serial port on Windows platform ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''There are many serial port debugging software that can be used under Windows, such as SecureCRT, MobaXterm, etc. The following demonstrates how to use MobaXterm. This software has a free version and can be used without buying a serial number.'''</big>|}

<li>Download MobaXterm

</li>

<li>After entering the MobaXterm download page, click '''GET XOBATERM NOW!'''

[[File:~~media/image191~~plus5-img191.png~~|576x334px~~]]</li>

<li>Then choose to download the Home version

[[File:~~media/image192~~plus5-img192.png~~|353x231px~~]]</li>

<li>Then select Portable portable version, no need to install after downloading, just open it and use it

[[File:~~media/image193~~plus5-img193.png~~|575x259px~~]]</li></ol>

</li>

<li>After downloading, use decompression software to decompress the downloaded compressed package, you can get the executable software of MobaXterm, and then double-click to open

[[File:~~media/image194~~plus5-img194.png~~|576x81px~~]]</li>

<li>After opening the software, the steps to set up the serial port connection are as follows

[[File:~~media/image195~~plus5-img195.png~~|575x438px|11~~]]

</div></ol>

[[File:~~media/image196~~plus5-img196.png~~|575x291px|12~~]]

</div></li></ol>

== Instructions for using the 5v pin in the 40pin interface of the development board to supply power ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|

<big>'''The power supply method we recommend for the development board is to use the 5V/4A or 5V/5A Type-C interface power cord to plug into the Type-C power interface of the development board for power supply. If you need to use the 5V pin in the 40pin interface to power the development board, please make sure that the power cable and power adapter used can meet the power supply requirements of the development board. If the use is unstable, please switch back to the Type-C power supply.'''</big>

|}

<li>First, you need to prepare a power cord as shown in the figure below

[[File:5plus-1.png]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|

<big>'''The power cord shown in the picture above can be bought on Taobao, please search and buy by yourself.'''</big>

|}

</li>

<li>Use the 5V pin in the 40pin interface to supply power to the development board. The connection method of the power line is as follows

<li>The USB A port of the power cord shown in the above picture needs to be plugged into the 5V/4A or 5V/5A power adapter connector '''(please do not plug into the USB port of the computer for power supply, nor can the general mobile phone charging head, because the development board Without the PD function, the general mobile phone charging head can only output the lowest 5V/2A)'''</li>

<li>The red DuPont line needs to be plugged into the 5V pin of the development board 40pin</li>

<li>The black DuPont line needs to be inserted into the GND pin of the 40pin interface</li>

<li>The positions of the 5V pin and the GND pin of the 40pin interface in the development board are shown in the figure below, '''remember not to reverse the connection'''

[[File:5plus-2.png]]</li></ol>

</li>

</ol>

= '''Ubuntu/Debian Server and Xfce desktop system instructions''' =

<li>'''root@orangepi:~#''' The prompt indicates that this command is entered in the '''linux system of the development board''', and the '''#''' at the end of the prompt indicates that the current user of the system is the root user, who can execute any desired command</li>

<li>'''test@test:~$''' prompt indicates that this command is entered in the Ubuntu PC or Ubuntu virtual machine, not in the linux system of the development board. The '''$''' at the end of the prompt indicates that the current user of the system is an ordinary user. When executing privileged commands, you need to add '''sudo'''</li>

<li>'''root@test:~#''' prompt indicates that this command is entered in the Ubuntu PC or Ubuntu virtual machine, not in the linux system of the development board. The '''#''' at the end of the prompt indicates that the current user of the system is the root user and can execute any command you want</li></ol>

</li>

<li>What are the commands that need to be entered?

<li>By default, the Linux system automatically logs in to the terminal, and the default login user name is '''orangepi'''

[[File:~~media/image197~~plus5-img197.png~~|387x253px~~]]</li>

<li>Use the following command to set the root user to automatically log in to the terminal

{| class="wikitable" style="width:800px;"

[[File:~~media/image198~~plus5-img198.png~~|576x324px|1~~]]

</div></li>

[[File:~~media/image199~~plus5-img199.png~~|569x320px|IMG_256~~]]

</div></ol>

</li>

<li>Then restart the system, it will automatically use the root user to log in to the desktop

[[File:~~media/image200~~plus5-img200.png~~|362x152px~~]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|

orangepi@orangepi:~$ '''sudo systemctl start lightdm.service'''

orangepi@orangepi:~$ '''sudo systemctl enable lightdm.service'''

|}

</li>

<li>There is a red, green and blue three-color light on the development board, and its location is shown in the figure below:

[[File:~~media/image201~~plus5-img201.png~~|374x77px~~]]</li>

<li>'''As long as the development board is powered on, the red LED light will always be on, which is controlled by the hardware and cannot be turned off by the software. The red LED light can be used to determine whether the power supply of the development board is turned on normally.'''</li>

<li>The green and blue LED lights will keep blinking after the kernel boots, which is controlled by software.</li>

root@orangepi:/sys/class/leds/blue_led# '''echo heartbeat > trigger'''

|}

</li></ol>

<li>If you don't want the LED light to flash after booting, you can use the following method to turn off the green light and blue light

<li>First run '''orangepi-config''', normal users remember to add sudo permission

{| class="wikitable" style="width:800px;"

|-

|

orangepi@orangepi:~$ '''sudo orangepi-config'''

|}

</li>

<li>Then select '''System'''

[[File:5plus-51.png]]

</li>

<li>Then select '''Hardware'''

[[File:5plus-52.png]]

</li>

<li>Then use the arrow keys of the keyboard to navigate to the position shown in the figure below, and then use the space to select the '''opi5plus-disable-leds''' configuration

[[File:5plus-53.png]]

</li>

<li>Then select '''<Save>''' to save

[[File:5plus-54.png]]

</li>

<li>Then select '''<Back>'''

[[File:5plus-55.png]]

</li>

<li>Then select '''<Reboot>''' to restart the system to make the configuration take effect

[[File:5plus-56.png]]

</li>

<li>After restarting, you can see that only the red light on the development board is always on, and the green and blue lights will not flash

</li></ol>

<li>'''Try another router (I have encountered many problems with the router, such as the router cannot assign the IP address normally, or the IP address has been'''

'''assigned normally but cannot be seen in the router);'''</li>

<li>'''If there is no router to replace, you can only connect to an HDMI display or use the debugging serial port to check the IP address.'''</li></ol>'''In addition, it should be noted that the development board DHCP automatically assigns an IP address without any settings.'''</p~~></li></ol~~>

</big>

|}

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|

<big>'''Please do not connect to WIFI by modifying the /etc/network/interfaces configuration file. There will be problems connecting to the WIFI network in this way.'''</big>

|}

==== The server image connects to WIFI through commands ====

[[File:~~media/image202~~plus5-img202.png~~|575x250px|选区_011~~]]

</div></li>

</li>

<li>Enter the nmtui command to open the interface as shown below

[[File:~~media/image203~~plus5-img203.png~~|345x215px~~]]</li>

<li>Select '''Activate a connect''' and press Enter

[[File:~~media/image204~~plus5-img204.png~~|349x216px~~]]</li>

<li>Then you can see all the searched WIFI hotspots

[[File:~~media/image205~~plus5-img205.png~~|358x226px~~]]</li>

<li>Select the WIFI hotspot you want to connect to, then use the Tab key to position the cursor on '''Activate''' and press Enter

[[File:~~media/image206~~plus5-img206.png~~|357x226px~~]]</li>

<li>Then a dialog box for entering a password will pop up, enter the corresponding password in '''Password''' and press Enter to start connecting to WIFI

[[File:~~media/image207~~plus5-img207.png~~|352x225px~~]]</li>

<li>After the WIFI connection is successful, a "*" will be displayed in front of the connected WIFI name

[[File:~~media/image208~~plus5-img208.png~~|349x223px~~]]</li>

<li>You can view the IP address of wifi through the '''ip addr show wlan0''' command

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

<li>Click the network configuration icon in the upper right corner of the desktop (please do not connect the network cable when testing WIFI)

[[File:~~media/image209~~plus5-img209.png~~|377x166px~~]]</li>

<li>Click '''More networks''' in the pop-up drop-down box to see all scanned WIFI hotspots, and then select the WIFI hotspot you want to connect to

[[File:~~media/image210~~plus5-img210.png~~|576x353px~~]]</li>

<li>Then enter the password of the WIFI hotspot, and then click '''Connect''' to start connecting to WIFI

[[File:~~media/image211~~plus5-img211.png~~|320x163px~~]]</li>

<li>After connecting to WIFI, you can open the browser to check whether you can access the Internet. The entrance of the browser is shown in the figure below

[[File:~~media/image212~~plus5-img212.png~~|576x308px~~]]</li>

<li>If you can open other web pages after opening the browser, it means that the WIFI connection is normal

[[File:~~media/image213~~plus5-img213.png~~|574x222px~~]]</li></ol>

</li>

<li>Then select '''Edit a connection''' and press Enter

[[File:~~media/image214~~plus5-img214.png~~|234x234px~~]]</li>

<li>Then select the network interface that needs to set a static IP address, such as setting the static IP address of the Ethernet interface to select '''Wired connection 1''' or '''Wired connection 2'''

[[File:~~media/image215~~plus5-img215.png~~|306x121px~~]]</li>

<li>Then select '''Edit''' via the '''Tab''' key and press the Enter key

[[File:~~media/image216~~plus5-img216.png~~|356x142px~~]]</li>

<li>Then use the Tab key to move the cursor to the <'''Automatic'''> position shown in the figure below to configure IPv4

[[File:~~media/image217~~plus5-img217.png~~|576x215px~~]]</li>

<li>Then press Enter, select '''Manual''' through the up and down arrow keys, and press Enter to confirm

[[File:~~media/image218~~plus5-img218.png~~|575x212px~~]]</li>

<li>The display after selection is shown in the figure below

[[File:~~media/image219~~plus5-img219.png~~|575x215px~~]]</li>

<li>Then move the cursor to <'''Show'''> via the Tab key

[[File:~~media/image220~~plus5-img220.png~~|576x215px~~]]</li>

<li>Then press Enter, and the following setting interface will pop up after entering

[[File:~~media/image221~~plus5-img221.png~~|576x386px~~]]</li>

<li>Then you can set the IP address (Addresses), gateway (Gateway) and DNS server address in the position shown in the figure below (there are many other setting options in it, please explore by yourself), '''please set according to your specific needs, The values set in the image below are just an example'''

[[File:~~media/image222~~plus5-img222.png~~|575x217px~~]]</li>

<li>After setting, move the cursor to '''<OK>''' in the lower right corner, and press Enter to confirm

[[File:~~media/image223~~plus5-img223.png~~|575x114px~~]]</li>

<li>Then click '''<Back>''' to return to the previous selection interface

[[File:~~media/image224~~plus5-img224.png~~|278x341px~~]]</li>

<li>Then select '''Activate a connection''', then move the cursor to '''<OK>''', and finally click Enter

[[File:~~media/image225~~plus5-img225.png~~|226x224px~~]]</li>

<li>Then select the network interface that needs to be set, such as '''Wired connection 2''', then move the cursor to '''<Deactivate>''', and press the Enter key to disable '''Wired connection 2'''

[[File:~~media/image226~~plus5-img226.png~~|417x159px~~]]</li>

<li>Then re-select and enable '''Wired connection 2''', so that the static IP set earlier will take effect

[[File:~~media/image227~~plus5-img227.png~~|414x160px~~]]</li>

<li>Then you can exit nmtui through the '''<Back>''' and '''Quit''' buttons

[[File:~~media/image228~~plus5-img228.png~~|260x224px~~]] [[File:~~media/image229~~plus5-img229.png~~|225x225px~~]]</li>

<li>Then through '''ip addr show,''' you can see that the IP address of the network port has changed to the static IP address set earlier

{| class="wikitable" style="width:800px;"

'''（PCIE+USB port)'''

| [[File:~~media/image230~~plus5-img230.png]]

| '''Debian'''

'''（PCIE+USB port)'''

| [[File:~~media%20/image231~~plus5-img231.png]]

| '''Debian'''

'''（PCIE+USB port)'''

| [[File:~~media/image232~~plus5-img232.png]]

| '''Debian'''

<li>Then insert the module into the M.2 E-Key interface of the development board and fix it. The position is shown in the figure below:

[[File:~~media/image233~~plus5-img233.png~~|296x133px~~]]</li><li>Then ~~open~~ use the '''lspci''' command, if you can see the ~~configuration~~ information of the WIFI module ~~in the Linux system~~, it means that the ~~steps are as follows:~~module is in good contact

<li>~~First run '''~~AX200 displays as follows{| class="wikitable" style="width:800px;" |-|orangepi@orangepi~~-config~~:~$ '''~~, normal users remember to add~~ lspci | grep "Network"'''~~sudo''' permission~~0002:21:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)|}</li><li>AX210 displays as follows

{| class="wikitable" style="width:800px;"

|-

|

orangepi@orangepi:~$ '''~~sudo orangepi-config~~lspci | grep "Network"'''0002:21:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a)

|}

</li>

<li>~~Then select '''System'''~~RTL8852 display as shown below~~[[File~~{| class="wikitable" style="width:~~media/image234.png|374x173px]]</li><li>Then select '''Hardware'''~~800px;" ~~[[File:media/image235.png~~|~~373x162px]]</li><li>Then use the arrow keys of the keyboard to navigate to the position shown in the figure below, and then use the space to select the '''wifi~~-~~pcie''' configuration[[File:media/image236.png~~|~~298x40px]]</li><li>~~~~Then select~~ orangepi@orangepi:~$ '''~~<Save>~~lspci | grep "Network"''' ~~to save~~~~[[File~~0002:21:~~media/image237~~00.~~png|297x80px]]~~0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)</p~~></li~~>~~<li>Then select '''<Back>'''[[File:media/image238.png~~|~~255x71px]]</li>~~}~~<li>Then select '''<Reboot>''' to restart the system to make the configuration take effect[[File:media/image239.png|256x113px]]~~</li></ol>

</li>

<li>~~If everything is normal after restarting the system,~~ Then use the following command to see that there will be an additional WIFI device node~~. If you can't see it, please check if there is any problem with the previous configuration~~

{| class="wikitable" style="width:800px;"

|-

|

[orangepi@orangepi ~]$ '''ip ~~addr show~~a'''

|}

</li>

[[File:~~media/image240~~plus5-img240.png~~|437x262px|953iring_001~~]]

</div>

[[File:~~media/image241~~plus5-img241.png~~|575x292px|13~~]]

</div></li></ol>

<big>'''Note that when entering the password, the specific content of the entered password will not be displayed on the screen, please do not think that there is any fault, just press Enter after inputting.'''</big>

[[File:~~media/image242~~plus5-img242.png|~~576x192px~~center]]

|}

</li></ol>

<li>After successfully logging in to the system, the display is as shown in the figure below</li>

[[File:~~media/image243~~plus5-img243.png~~|575x353px~~]]

</ol>

<big>'''If there is no adb tool in your Windows system, you can use the adb program in the RKDevTool software (this software is useful in the section on [[Orange Pi 5 Plus#How to use RKDevTool to burn Linux image to TF card|'''how to use RKDevTool to burn the Linux image to the TF card''']]).'''</big>

[[File:~~media/image244~~plus5-img244.png~~|576x131px~~]]

<big>'''An example using adb in Windows looks like this:'''</big>

[[File:~~media/image245~~plus5-img245.png|~~576x335px~~800px]]

|}

</li></ol>

<li>First prepare a good quality Type-C data cable

[[File:~~media/image21~~plus5-img21.png~~|125x126px~~]]</li>

<li>Then connect the development board and Ubuntu PC through the Type-C data cable. The position of the Type-C interface of the development board is shown in the figure below:

[[File:~~media/image173.jpeg|323x91px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~plus5-1img173.~~jpg未标题-1~~png]]

</div></li>

<big>'''If there is no adb tool in your Windows system, you can use the adb program in the RKDevTool software (this software is useful in the section on [[Orange Pi 5 Plus#How to use RKDevTool to burn Linux image to TF card|'''how to use RKDevTool to burn the Linux image to the TF card''']]).'''</big>

[[File:~~media/image244~~plus5-img244.png~~|576x131px~~]]

<big>'''An example using adb in Windows looks like this:'''</big>

[[File:~~media/image246~~plus5-img246.png|~~576x304px~~800px]]

|}

</ol>

[[File:~~media/image247~~plus5-img247.png~~|576x453px|截图 2022-12-03 19-04-40~~]]

</div></li>

[[File:~~media/image248~~plus5-img248.png~~|575x128px|图片565~~]]

</div></ol>

<li>Then choose to '''save the password''', and then click '''OK'''

[[File:~~media/image249~~plus5-img249.png~~|249x181px~~]]</li>

<li>Then choose to '''always trust this host''', and then click '''OK'''</li>

[[File:~~media/image250~~plus5-img250.png~~|278x150px|IMG_256~~]]

</div></ol>

[[File:~~media/image251~~plus5-img251.png~~|533x330px|IMG_256~~]]

</div></ol>

[[File:~~media/image252~~plus5-img252.png~~|529x414px|IMG_256~~]]

</div></ol>

[[File:~~media/image253~~plus5-img253.png~~|472x171px|IMG_256~~]]

</div>

[[File:~~media/image254~~plus5-img254.png~~|384x276px~~]]

</li></ol>

[[File:~~media/image255~~plus5-img255.png~~|355x279px|IMG_256~~]]

</div>

[[File:~~media/image256~~plus5-img256.png~~|451x357px|IMG_256~~]]

</div></ol>

[[File:~~media/image248~~plus5-img248.png~~|575x128px|图片565~~]]

</div></ol>

[[File:~~media/image257~~plus5-img257.png~~|207x146px|IMG_256~~]]

</div></ol>

[[File:~~media/image258~~plus5-img258.png~~|221x109px|IMG_256~~]]

</div></ol>

[[File:~~media/image259~~plus5-img259.png~~|449x332px|IMG_256~~]]

</div></ol>

[[File:~~media/image260~~plus5-img260.png~~|461x340px|IMG_256~~]]

</div></ol>

<li>There are two HDMI output interfaces on the development board, and their locations are shown in the figure below:

[[File:~~media/image261~~plus5-img261.png~~|333x92px~~]]</li>

<li>By default, the Linux system configures HDMI_TX1 to support 8K display, and HDMI_TX2 supports only 4K display by default (only one HDMI_TX interface can support 8K display at a time). If you want to set HDMI_TX2 to support 8K display, please follow the steps below:

</li>

<li>Then select '''System'''

[[File:~~media/image234~~plus5-img234.png~~|362x167px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image235~~plus5-img235.png~~|362x157px~~]]</li>

<li>Then use the arrow keys of the keyboard to navigate to the > position shown in the figure below, and then use the '''space''' > to select '''hdmi2-8k''' configuration

[[File:~~media/image262~~plus5-img262.png~~|361x66px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image263~~plus5-img263.png~~|363x105px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image264~~plus5-img264.png~~|362x110px~~]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the > configuration take effect

[[File:~~media/image239~~plus5-img239.png~~|276x121px~~]]</li></ol>

</li>

<li>Then use HDMI to HDMI cable to connect Orange Pi development board and HDMI display

[[File:~~media/image11~~plus5-img11.png~~|199x129px~~]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

<li>The location of the HDMI In interface on the development board is as follows:

[[File:~~media/image265~~plus5-img265.png~~|351x112px~~]]</li>

<li>First use the HDMI to HDMI cable shown in the figure below to connect the HDMI output of other devices to the HDMI In interface of the development board

[[File:~~media/image11~~plus5-img11.png~~|199x129px~~]]</li>

<li>The HDMI In function of the Linux system is disabled by default, and the opening method is as follows:

</li>

<li>Then select '''System'''

[[File:~~media/image234~~plus5-img234.png~~|362x167px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image235~~plus5-img235.png~~|362x157px~~]]</li>

<li>Then use the arrow keys of the keyboard to navigate to the position shown in the figure below, and then use the '''space''' to select the '''hdmirx''' configuration

[[File:~~media/image266~~plus5-img266.png~~|359x82px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image263~~plus5-img263.png~~|363x105px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image264~~plus5-img264.png~~|362x110px~~]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the configuration take effect

[[File:~~media/image239~~plus5-img239.png~~|276x121px~~]]</li></ol>

</li>

<li>Restart the system and open a terminal on the desktop, then run the '''test_hdmiin.sh''' script

[[File:~~media/image267~~plus5-img267.png~~|576x324px|1~~]]

</div></li></ol>

<li>HDMI to VGA Converter

[[File:~~media/image268~~plus5-img268.png~~|155x104px~~]]</li>

<li>A VGA cable

[[File:~~media/image269~~plus5-img269.png~~|148x133px~~]]</li>

<li>A monitor or TV that supports VGA interface</li></ol>

</li>

<li>The HDMI to VGA display test is as follows:

[[File:~~media/image270~~plus5-img270.png~~|575x341px~~]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

<li>First open '''Display''' in '''Settings'''

[[File:~~media/image271~~plus5-img271.png~~|576x370px~~]]</li>

<li>Then you can see the current resolution of the system

[[File:~~media/image272~~plus5-img272.png~~|288x191px~~]]</li>

<li>Click the drop-down box of Resolution to see all resolutions currently supported by the monitor

[[File:~~media/image273~~plus5-img273.png~~|353x233px~~]]</li>

<li>Then select the resolution you want to set, and click Apply

[[File:~~media/image274~~plus5-img274.png~~|351x234px~~]]</li>

<li>After the new resolution is set, select '''Keep the configuration'''

[[File:~~media/image275~~plus5-img275.png~~|462x251px~~]]</li></ol>

<li>Click on the Bluetooth icon in the upper right corner of the desktop

[[File:~~media/image276~~plus5-img276.png~~|386x149px~~]]</li>

<li>Then select the adapter

[[File:~~media/image277~~plus5-img277.png~~|375x165px~~]]</li>

<li>If there is a prompt on the following interface, please select '''Yes'''

[[File:~~media/image278~~plus5-img278.png~~|248x85px~~]]</li>

<li>Then set the '''Visibility Setting''' to '''Always visible''' in the Bluetooth adapter setting interface, and then close it

[[File:~~media/image279~~plus5-img279.png~~|243x229px~~]]</li>

<li>Then open the configuration interface of the Bluetooth device

[[File:~~media/image280~~plus5-img280.png~~|438x179px~~]]</li>

<li>Click '''Search''' to start scanning the surrounding Bluetooth devices

[[File:~~media/image281~~plus5-img281.png~~|322x217px~~]]</li></ol>

<li>Then select the Bluetooth device you want to connect to, and then click the right mouse button to pop up the operation interface for this Bluetooth device, select '''Pair''' to start pairing, and the demonstration here is to pair with an Android phone

[[File:~~media/image282~~plus5-img282.png~~|338x263px~~]]</li>

<li>When pairing, a pairing confirmation box will pop up in the upper right corner of the desktop, just select '''Confirm''' to confirm, and the phone also needs to confirm at this time

[[File:~~media/image283~~plus5-img283.png~~|417x152px~~]]</li>

<li>After pairing with the mobile phone, you can select the paired Bluetooth device, then right-click and select '''Send a File''' to start sending a picture to the mobile phone

[[File:~~media/image284~~plus5-img284.png~~|439x259px~~]]</li>

<li>The interface for sending pictures is as follows

[[File:~~media/image285~~plus5-img285.png~~|437x253px~~]]</li></ol>

Support 2.4G WIFI+BT4.0

| [[File:~~me%20dia/image286~~plus5-img286.png]]

|-

| 2

Support 2.4G +5G WIFI

| [[File:~~me%20dia/image287~~plus5-img287.png]]

|-

| 3

Support BitTorrent 4.2

| [[File:~~med%20ia/image288~~plus5-img288.~~jpeg|tb_image_s hare_1670833201123~~png]]

|}

</li>

<li>You can also see the bluetooth icon on the desktop. At this time, the bluetooth is not turned on, so a red '''x''' will be displayed

[[File:~~media/image289~~plus5-img289.png~~|576x157px~~]]</li>

<li>Click '''Turn Bluetooth On''' to turn on Bluetooth

[[File:~~media/image290~~plus5-img290.png~~|576x262px~~]]</li>

<li>The display after turning on Bluetooth is as follows

[[File:~~media/image291~~plus5-img291.png~~|576x164px~~]]</li>

<li>For the test method of Bluetooth, please refer to the section on [[Orange Pi 5 Plus#How to use E-Key PCIe WIFI6+Bluetooth module|'''Bluetooth usage''']], so I won't go into details here</li></ol>

<li>First, you need to prepare a USB camera that supports the UVC protocol as shown in the figure below or similar, and then insert the USB camera into the USB port of the Orange Pi development board

[[File:~~media/image18~~plus5-img18.png~~|277x160px~~]]</li>

<li>Through the v4l2-ctl command, you can see that the device node information of the USB camera is '''/dev/video0'''

{| class="wikitable" style="width:800px;"

</li>

<li>In the desktop system, Cheese can be used to directly open the USB camera. The method of opening Cheese is shown in the figure below:

[[File:~~media/image292~~plus5-img292.png~~|474x302px~~]]

The interface after Cheese turns on the USB camera is shown in the figure below:

[[File:~~media/image293~~plus5-img293.png~~|480x282px~~]]</li>

<li>Method of using fswebcam to test USB camera

</li>

<li>After installing fswebcam, you can use the following command to take pictures

<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) -d option is used to specify the device node of the USB camera</li><li>b) --no-banner is used to remove the watermark of the photo</li><li>c) -r option is used to specify the resolution of the photo</li><li>d) -S option is used to set the number of previous frames to skip</li><li>e) ./image.jpg is used to set the name and path of the generated photo

{| class="wikitable" style="width:800px;"

|-

<li>First open the file manager

[[File:~~media/image294~~plus5-img294.png~~|257x126px~~]]</li>

<li>Then find the following file (if there is no audio file in the system, you can upload an audio file to the system yourself)

[[File:~~media/image295~~plus5-img295.~~jpeg|236x186px|图片10~~png]]

</div></li>

<li>Then select the audio.wav file, right click and select open with vlc to start playing

[[File:~~media/image296~~plus5-img296.png~~|241x195px~~]]</li>

<li>How to switch between different audio devices such as HDMI playback and headphone playback

<li>First open the volume control interface

[[File:~~media/image297~~plus5-img297.png~~|294x161px~~]]</li>

<li>When playing audio, the audio device options that the playback software can use will be displayed in '''Playback''', as shown in the figure below, where you can set which audio device to play to

[[File:~~media/image298~~plus5-img298.png~~|575x303px~~]]</li></ol>

</li></ol>

<li>First insert the earphone into the earphone jack of the development board

[[File:~~media/image299~~plus5-img299.png~~|365x89px~~]]</li>

<li>Then you can use the '''aplay -l''' command to view the sound card devices supported by the linux system. From the output below, you can see that '''card 3''' is the sound card device of es8388, that is, the sound card device of the headset

{| class="wikitable" style="width:800px;"

<li>First, you need to prepare a speaker as shown in the figure below. The specification of the speaker seat on the development board is 2pin 1.25mm pitch

[[File:~~media/image29~~plus5-img29.png~~|229x158px~~]]</li>

<li>The position of the speaker interface on the development board is as follows. After preparing the speaker, please insert it into the speaker interface of the development board

[[File:~~media/image300~~plus5-img300.png~~|325x184px~~]]</li>

<li>The speaker and earphone use the same sound card. Before using the speaker, please make sure that the earphone jack is not plugged into the earphone (if the earphone is plugged in, the audio will be played to the earphone). Then use the '''aplay''' command to play the audio file that comes with the system. If the speaker can hear the sound, it means that the hardware can be used normally.

{| class="wikitable" style="width:800px;"

<li>There is an onboard MIC on the development board, the location is as follows:

[[File:~~media/image301~~plus5-img301.png~~|339x112px~~]]</li>

<li>Running the '''test_record.sh main''' command will record a piece of audio through the onboard MIC, and then play it to HDMI_TX1 and the headset.

{| class="wikitable" style="width:800px;"

::[[File:~~media/image302~~plus5-img302.~~jpeg|575x166px|5725d46c4ff256fbd1d42ed5ba883f9f~~png]]

</div>

<li>Please refer to the figure below for the order of the 40 pin expansion interface pins on the Orange Pi 5 Plus development board:

[[File:~~media/image303~~plus5-img303.png~~|567x418px~~]]</li>

<li>The functions of the 40 pin interface pins on the Orange Pi 5 Plus development board are shown in the table below

<li>The following is the complete pin diagram of 40 pin

[[File:~~media/image304~~plus5-img304.png~~|575x137px~~]]

The following is a color map containing some of the content in the above table:

[[File:~~media/image305~~plus5-img305.png~~|575x199px~~]]</li>

<li>The table below is the picture of the left half of the complete > table above, so you can see it clearly

[[File:~~media/image306~~plus5-img306.png~~|576x287px~~]]</li>

<li>The table below is the picture of the right half of the complete > table above, so you can see it clearly

[[File:~~media/image307~~plus5-img307.png~~|575x263px~~]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

[[File:~~media/image308~~plus5-img308.png~~|575x403px|876iring_001~~]]

</div>

[[File:~~media/image308~~plus5-img308.png~~|575x403px|876iring_001~~]]

</div></li></ol>

[[File:~~media/image309~~plus5-img309.png~~|575x145px|874iring_001~~]]

</div></li>

[[File:~~media/image310~~plus5-img310.png~~|575x127px|874iring_002~~]]

</div></li>

[[File:~~media/image311~~plus5-img311.png~~|575x131px|875iring_001~~]]

</div></li>

[[File:~~media/image311~~plus5-img311.png~~|575x131px|875iring_001~~]]

</div></li>

<li>As can be seen from the figure below, the SPIs available for Orange Pi 5 Plus are SPI0 and SPI4

[[File:~~media/image304~~plus5-img304.png~~|575x137px~~]]</li>

<li>The corresponding pins of SPI0 and SPI4 in 40pin are shown in the table below. SPI4_M1 and SPI4_M2 can only use one of them at the same time, and they cannot be used at the same time. They are all the same SPI4, but they are connected to different pins. Please don't think that they are two different sets of SPI buses.</li>

| '''none'''

|-

| '''dtbo ~~confi guration~~configuration'''| '''~~spi 0~~spi0-m2-cs0-spidev'''

'''~~spi 0~~spi0-m2-cs1-spidev'''

'''spi0-m2 -cs0-cs1-spidev'''

| '''~~spi 4~~spi4-m1-cs0-spidev'''

'''~~spi 4~~spi4-m1-cs1-spidev'''

'''spi4-m1 -cs0-cs1-spidev'''

| '''spi4-~~m 2~~m2-cs0-spidev'''

|}

</ol>

</li>

<li>Then select '''System'''

[[File:~~media/image234~~plus5-img234.png~~|389x180px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image235~~plus5-img235.png~~|389x169px~~]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the position shown in the figure below, and then use the '''space''' to select the SPI configuration you want to open

[[File:~~media/image312~~plus5-img312.png~~|388x132px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image263~~plus5-img263.png~~|391x113px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image264~~plus5-img264.png~~|404x123px~~]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the configuration take effect

[[File:~~media/image239~~plus5-img239.png~~|332x146px~~]]</li></ol>

</li>

<li>After restarting, enter the system and first check whether there is a '''spidevx.x''' device node in the linux system. If it exists, it means that the SPI has been set up and can be used directly.

<li>As can be seen from the table below, the available i2c for Orange Pi 5 Plus is i2c2, i2c4, i2c5 and i2c8, a total of four sets of i2c buses.

[[File:~~media/image304~~plus5-img304.png~~|575x137px~~]]</li>

<li>The corresponding pins of the 4 groups of I2C buses in 40pin are shown in the table below. I2C2_M0 and I2C2_M4 can only use one of them at the same time, and they cannot be used at the same time. They are all the same I2C2, but they are connected to different pins. Please don’t think that they are two different sets of I2C2 buses.</li>

</li>

<li>Then select '''System'''

[[File:~~media/image234~~plus5-img234.png~~|397x184px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image235~~plus5-img235.png~~|401x174px~~]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the position shown in the figure below, and then use the '''space''' to select the I2C configuration you want to open

[[File:~~media/image313~~plus5-img313.png~~|406x153px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image263~~plus5-img263.png~~|380x109px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image264~~plus5-img264.png~~|355x108px~~]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the configuration take effect

[[File:~~media/image239~~plus5-img239.png~~|323x142px~~]]</li></ol>

</li>

<li>After starting the linux system, first confirm that there are device nodes that need to use I2C under '''/dev'''

[[File:~~media/image314~~plus5-img314.png~~|336x170px|521iring_001~~]]

</div>

<li>As can be seen from the table below, the uarts available for Orange Pi 5 Plus are uart1, uart3, uart4, uart6, uart7 and uart8, a total of 6 sets of uart buses

[[File:~~media/image304~~plus5-img304.png~~|575x137px~~]]</li>

<li>The corresponding pins of the 6 groups of UART buses in 40pin are shown in the following table:</li>

</li>

<li>Then select '''System'''

[[File:~~media/image234~~plus5-img234.png~~|403x186px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image235~~plus5-img235.png~~|413x179px~~]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the position shown in the figure below, and then use the space to select the UART configuration you want to open

[[File:~~media/image315~~plus5-img315.png~~|408x144px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image263~~plus5-img263.png~~|405x117px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image264~~plus5-img264.png~~|401x122px~~]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the configuration take effect

[[File:~~media/image239~~plus5-img239.png~~|320x141px~~]]</li></ol>

</li>

<li>After entering the linux system, first confirm whether there is a device node corresponding to uart under /dev

<li>As can be seen from the table below, the available PWM for Orange Pi 5 Plus includes six channels of PWM: pwm0, pwm1, pwm11, pwm12, pwm13 and pwm14

[[File:~~media/image304~~plus5-img304.png~~|575x137px~~]]</li>

<li>The corresponding pins of PWM in 40pin are shown in the table below. Only one of PWM0_M0 and PWM0_M2, PWM1_M0 and PWM1_M2, PWM14_M0 and PWM14_M2 can be used at the same time, and they cannot be used at the same time. They are all the same PWM, but they are connected to different pins. Please don’t think that they are two different PWM bus.</li>

</li>

<li>Then select '''System'''

[[File:~~media/image234~~plus5-img234.png~~|416x192px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image235~~plus5-img235.png~~|457x198px~~]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the position shown in the figure below, and then use the space to select the PWM configuration you want to open

[[File:~~media/image316~~plus5-img316.png~~|279x222px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image263~~plus5-img263.png~~|368x106px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image264~~plus5-img264.png~~|370x112px~~]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the configuration take effect

[[File:~~media/image239~~plus5-img239.png~~|303x133px~~]]</li></ol>

</li>

<li>After opening a pwm, there will be an extra pwmchipX in '''/sys/class/pwm/''' (X is a specific number), for example, after opening pwm14, check the pwmchipX under '''/sys/class/pwm/''' two became three

[[File:~~media/image317~~plus5-img317.png~~|576x77px|985iring_001~~]]

</div></li>

<li>Then it can be known from the table below that the base address of the pwm14 register is febf0020, and then look at the output of the '''ls /sys/class/pwm/ -l''' command, you can see that pwmchip2 is linked to febf0020.pwm, so pwm14 corresponds to pwmchip as pwmchip2

[[File:~~media/image318~~plus5-img318.png~~|575x287px~~]]</li>

<li>Then use the following command to make pwm14 output a 50Hz square wave (please switch to the root user first, and then execute the following command)</li>

root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip2/pwm0/enable'''

[[File:~~media/image319~~plus5-img319.png~~|575x346px~~]]

|}

</ol>

<li>As can be seen from the table below, the available CAN bus for Orange Pi 5 Plus is CAN0 and CAN1, a total of two CAN buses

[[File:~~media/image320~~plus5-img320.png~~|574x137px~~]]</li>

<li>In the linux system, the CAN in the 40 pin is closed by default, and it needs to be opened manually before it can be used. The detailed steps are as follows:

</li>

<li>Then select '''System'''

[[File:~~media/image234~~plus5-img234.png~~|374x173px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image235~~plus5-img235.png~~|370x160px~~]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the > position shown in the figure below, and then use the space to > select the CAN configuration you want to open ('''can0-m0''' and > '''cam1-m0''' are optional for OPi 5 Plus)

[[File:~~media/image321~~plus5-img321.png~~|370x61px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image263~~plus5-img63.png~~|332x96px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image264~~plus5-img264.png~~|341x103px~~]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the > configuration take effect

[[File:~~media/image239~~plus5-img239.png~~|283x125px~~]]</li></ol>

</li>

<li>After entering the Linux system, use the '''sudo ifconfig -a''' command, if you can see the CAN device node, it means that the CAN has been opened correctly

<li>The CANalyst-II analyzer used in the test is shown in the figure below

[[File:~~media/image322~~plus5-img322.png~~|165x134px~~]]</li>

<li>CANalyst-II analyzer data download link

{| class="wikitable" style="width:800px;"

</li>

<li>First install the software USBCANToolSetup

[[File:~~media/image323~~plus5-img323.png~~|553x94px~~]]</li>

<li>The shortcut after installation of USBCANToolSetup is

[[File:~~media/image324~~plus5-img324.png~~|59x80px~~]]</li>

<li>In addition, you need to install the USB driver

[[File:~~media/image325~~plus5-img325.png~~|553x112px~~]]</li>

<li>The end of the USB interface of the CANalyst-II analyzer needs to be connected to the USB interface of the computer

[[File:~~media/image326~~plus5-img326.png~~|137x121px~~]]</li>

<li>To test the CAN function, you need to prepare a CAN transceiver as shown in the figure below. The main function of the CAN transceiver is to convert the TTL signal of the CAN controller into the differential signal of the CAN bus

<li>The CANL pin of the CAN transceiver needs to be connected to the H interface of the analyzer</li>

<li>The CANL pin of the CAN transceiver needs to be connected to the L interface of the analyzer

[[File:~~media/image327~~plus5-img327.png~~|243x78px~~]]</li></ol>

</li>

<li>Then you can open the USB-CAN software

[[File:~~media/image328~~plus5-img328.png~~|553x267px~~]]</li>

<li>Then click to start the device

[[File:~~media/image329~~plus5-img329.png~~|553x238px~~]]</li>

<li>Then click OK

[[File:~~media/image330~~plus5-img330.png~~|279x110px~~]]</li>

<li>Set the baud rate to 1000k bps

[[File:~~media/image331~~plus5-img331.png~~|322x268px~~]]</li>

<li>After successful opening, the USB-CAN software will display the serial number and other information

[[File:~~media/image332~~plus5-img332.png~~|553x262px~~]]</li>

<li>Development board receives CAN message test

</li>

<li>Then send a message to the development board in the USB-CAN software

[[File:~~media/image333~~plus5-img333.png~~|553x188px~~]]</li>

<li>If the message sent by the analyzer can be received in the development board, it means that the CAN bus can be used normally

{| class="wikitable" style="width:800px;"

[[File:~~media/image334~~plus5-img334.~~jpeg|483x377px|未标题-5~~png]]

</div></li></ol>

|-

|

~~~~root@orangepi:~# '''git clone --recursive https://github.com/orangepi-xunlong/wiringOP-Python -b next'''~~~~

root@orangepi:~# '''cd wiringOP-Python'''

~~Cloning into '~~root@orangepi:~/wiringOP-Python# '~~...remote: Enumerating objects: 602, done.remote: Counting objects: 100% (40/40), done.remote: Compressing objects: 100% (28/28), done.remote: Total 602 (delta 20), reused 26 (delta 12), pack-reused 562Receiving objects: 100% (602/602), 309.30 KiB | 1.23 MiB/s, done.Resolving deltas: 100% (349/349), done.Submodule~~ '~~wiringOP~~' ~~(https://github.com/orangepi~~git submodule update --init -~~xunlong/wiringOP.git) registered for path 'wiringOP'Cloning into '/root/test/wiringOP~~-~~Python/wiringOP'...~~remote~~: Enumerating objects: 654, done.remote: Counting objects: 100% (273/273), done.remote: Compressing objects: 100% (33/33), done.remote: Total 654 (delta 244), reused 245 (delta 238), pack-reused 381Receiving objects: 100% (654/654), 360.54 KiB | 1.73 MiB/s, done.Resolving deltas: 100% (424/424), done.Submodule path~~ '~~wiringOP~~'~~: checked out~~ '~~85f1331cd8fda668115461ec1c06cb342057eb03'~~

|}

</li>

[[File:~~media/image308~~plus5-img308.png~~|415x291px|876iring_001~~]]

</div>

[[File:~~media/image309~~plus5-img309.png~~|419x106px|874iring_001~~]]

</div></li>

<li>As can be seen from the figure below, the SPIs available for Orange Pi 5 Plus are SPI0 and SPI4

[[File:~~media/image304~~plus5-img304.png~~|575x137px~~]]</li><li>The corresponding pins of SPI0 and SPI4 in 40pin are shown in the table below. SPI4_M1 and SPI4_M2 can only use one of them at the same time, and they cannot be used at the same time. They are all the same SPI4, but they are connected to different pins. Please don't think that they are two different sets of SPI buses.</li~~></ol~~>

{| class="wikitable" style="width:800px;"

| '''none'''

|-

| '''dtbo ~~confi guration~~configuration'''| '''~~spi 0~~spi0-m2-cs0-spidev'''

'''~~spi 0~~spi0-m2-cs1-spidev'''

'''spi0-m2 -cs0-cs1-spidev'''

| '''~~spi 4~~spi4-m1-cs0-spidev'''

'''~~spi 4~~spi4-m1-cs1-spidev'''

'''spi4-m1 -cs0-cs1-spidev'''

| '''spi4-~~m 2~~m2-cs0-spidev'''

|}

</ol>

<li>In the linux system, the SPI in the 40 pin is closed by default, and it needs to be opened manually before it can be used. The detailed steps are as follows:

</li>

<li>Then select '''System'''

[[File:~~media/image234~~plus5-img234.png~~|413x191px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image235~~plus5-img235.png~~|419x182px~~]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the > position shown in the figure below, and then use the space to > select the SPI configuration you want to open

[[File:~~media/image312~~plus5-img312.png~~|415x141px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image263~~plus5-img263.png~~|415x120px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image264~~plus5-img264.png~~|414x126px~~]]</li><li>g. Then select '''<Reboot>''' to restart the system to make the > configuration take effect[[File:~~media/image239~~plus5-img239.png~~|293x129px~~]]</li></ol>

</li>

<li>After restarting, enter the system and first check whether there is a '''spidevx.x''' device node in the linux system. If it exists, it means that the SPI has been set up and can be used directly.

<li>As can be seen from the table below, the available i2c for Orange Pi 5 Plus is i2c2, i2c4, i2c5 and i2c8, a total of four sets of i2c buses.

[[File:~~media/image304~~plus5-img304.png~~|575x137px~~]]</li>

<li>The corresponding pins of the 4 groups of I2C buses in 40pin are shown in the table below. I2C2_M0 and I2C2_M4 can only use one of them at the same time, and they cannot be used at the same time. They are all the same I2C2, but they are connected to different pins. Please don’t think that they are two different sets of I2C2 buses.</li>

</li>

<li>Then select '''System'''

[[File:~~media/image234~~plus5-img234.png~~|382x176px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image235~~plus5-img235.png~~|385x167px~~]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the > position shown in the figure below, and then use the space to > select the I2C configuration you want to open

[[File:~~media/image313~~plus5-img313.png~~|381x144px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image263~~plus5-img263.png~~|347x100px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image264~~plus5-img264.png~~|325x98px~~]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the > configuration take effect

[[File:~~media/image239~~plus5-img239.png~~|254x112px~~]]</li></ol>

</li>

<li>After starting the linux system, first confirm that there is a device node corresponding to i2c under '''/dev'''

</li>

<li>Then connect an i2c device to the i2c pin of the 40 pin connector, here we take the ds1307 RTC module as an example

[[File:~~media/image335~~plus5-img335.png~~|124x106px~~]]</li>

<li>Then use the '''i2cdetect -y''' command, if the address of the connected i2c device can be detected, it means that i2c can be recognized normally.

{| class="wikitable" style="width:800px;"

<li>As can be seen from the table below, the uarts available for Orange Pi 5 Plus are uart1, uart3, uart4, uart6, uart7 and uart8, a total of 6 sets of uart buses

[[File:~~media/image304~~plus5-img304.png~~|575x137px~~]]</li>

<li>The corresponding pins of the 6 groups of UART buses in 40pin are shown in the following table:</li>

</li>

<li>Then select '''System'''

[[File:~~media/image234~~plus5-img234.png~~|404x186px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image235~~plus5-img235.png~~|403x175px~~]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the position shown in the figure below, and then use the '''space''' to select the UART configuration you want to open

[[File:~~media/image315~~plus5-img315.png~~|350x124px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image263~~plus5-img263.png~~|334x96px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image264~~plus5-img264.png~~|336x102px~~]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the configuration take effect

[[File:~~media/image239~~plus5-img239.png~~|235x103px~~]]</li></ol>

</li>

<li>After entering the linux system, first confirm whether there is a device node corresponding to uart under /dev

[[File:~~media/image336~~plus5-img336.png|~~527x211px|IMG_256~~1200px]]

</div></ol>

[[File:~~media/image95~~plus5-img95.png|~~507x249px|IMG_256~~1200px]]

</div></li>

[[File:~~media/image337~~plus5-img337.png~~|429x263px|IMG_256~~]]

</div></ol>

</li>

<li>Then select the AppImage version balenaEtcher, click the right mouse button, and then click Execute to open balenaEtcher

[[File:~~media/image338~~plus5-img338.png~~|145x118px~~]]</li></ol>

</li></ol>

|-

|

'''Debian11 ~~>~~ > Ubuntu 22.04> Debian12'''

|}

</li>

<li>Then what to do is to wait patiently. When you see the printing information below the terminal output, it means that the pagoda has been installed. The entire installation process takes about 9 minutes. There may be some differences according to the difference in network speed

[[File:~~media/image339~~plus5-img339.png~~|363x237px~~]]</li>

<li>At this time, enter the '''panel address''' displayed above in the browser to open the login interface of the pagoda Linux panel, and then enter the '''username''' and '''password''' displayed above in the corresponding position to log in to the pagoda.

[[File:~~media/image340~~plus5-img340.png~~|576x241px~~]]</li>

<li>After successfully logging in to the pagoda, the following welcome interface will pop up. First, please take the intermediate user notice to read to the bottom, and then you can choose "I have agreed and read" User Agreement ", and then click" Enter the panel " You can enter the pagoda

[[File:~~media/image341~~plus5-img341.png|~~576x213px~~1500px]]</li>

<li>After entering the pagoda, you will first prompt that you need to bind the account of the pagoda official website. If you do n’t have an account, you can go to the official website of the pagoda '''(https://www.bt.cn)''' to register one

[[File:~~media/image342~~plus5-img342.png|~~576x218px~~1500px]]</li>

<li>The final display interface is shown in the figure below. You can intuitively see some status information of the development board Linux system, such as load status, CPU usage, memory usage, and storage space usage

[[File:~~media/image343~~plus5-img343.png~~|574x283px~~]]</li>

<li>Test the SSH terminal login of the pagoda

<li>After opening the SSH terminal of the pagoda, you will first prompt that you need to enter the password of the development board system. At this time, enter '''orangepi''' in the password box (the default password, if you have modification, please fill in the modified one).

[[File:~~media/image344~~plus5-img344.png~~|475x330px~~]]</li>

<li>The display after successful login is shown in the figure below

[[File:~~media/image345~~plus5-img345.png~~|575x206px~~]]</li></ol>

</li>

<li>Software such as Apache, MySQL, and PHP can be installed in the software store of the pagoda. You can also deploy various applications in one click. Please explore it yourself

[[File:~~media/image346~~plus5-img346.png|~~575x279px~~1500px]]</li>

<li>Pagoda command line tool test

[[File:~~media/image347~~plus5-img347.png~~|388x343px|815iring_001~~]]

</div></li>

|-

|

<big>'''Note that before installing the Chinese input method, please make sure that the Linux system used in the development board is the desktop version ~~system。~~system.'''</big>

|}

</li>

<li>Then select '''zh_CN.UTF-8 UTF-8''' in the pop-up interface (through the upper and lower direction keys on the keyboard to move up and down, select it through the space key, and finally move the cursor to '''<OK>''' through the Tab key, and then press Enter key.)

[[File:~~media/image348~~plus5-img348.png|~~575x296px~~1500px]]</li>

<li>Then set the default '''locale''' as '''zh_CN.UTF-8'''

[[File:~~media/image349~~plus5-img349.png|~~575x160px~~1500px]]</li>

<li>After exiting the interface,'''locale''' will be set. The output displayed by the command line is shown below

{| class="wikitable" style="width:800px;"

</li>

<li>Then open '''Input Method'''

[[File:~~media/image350~~plus5-img350.png~~|575x361px~~]]</li>

<li>Then choose '''OK'''

[[File:~~media/image351~~plus5-img351.png~~|295x212px~~]]</li>

<li>Then choose '''Yes'''

[[File:~~media/image352~~plus5-img352.png~~|303x192px~~]]</li>

<li>Then choose '''fcitx'''

[[File:~~media/image353~~plus5-img353.png~~|307x220px~~]]</li>

<li>Then choose '''OK'''

[[File:~~media/image354~~plus5-img354.png~~|305x216px~~]]</li>

<li>'''Then restart the Linux system to make the configuration effective'''</li>

<li>Then Open '''Fcitx configuration'''

[[File:~~media/image355~~plus5-img355.png~~|575x376px~~]]</li>

<li>Then click the “+” of the position shown in the figure below

[[File:~~media/image356~~plus5-img356.png~~|280x187px~~]]</li>

<li>Then search '''Google Pinyin''' and click '''OK'''

[[File:~~media/image357~~plus5-img357.png~~|291x196px~~]]</li>

<li>Then put '''Google Pinyin''' to the forefront

[[File:~~media/image358~~plus5-img358.png~~|299x202px~~]][[File:~~media/image359~~plus5-img359.png~~|300x202px~~]]</li>

<li>Then open the '''Geany''' Editor and test the Chinese input method.

[[File:~~media/image360~~plus5-img360.png~~|349x212px~~]]</li>

<li>Chinese input method test is shown below

[[File:~~media/image361~~plus5-img361.png~~|575x325px~~]]</li>

<li>You can switch between Chinese and English input methods through '''Ctrl+Space''' shortcut</li>

<li>If the entire system is required as Chinese, the variables in '''/etc/default/locale''' can be set to '''zh_CN.UTF-8'''

</li>

<li>Then '''restart the system''' to see the system display as Chinese

[[File:~~media/image362~~plus5-img362.png~~|576x356px~~]]</li></ol>

<li>First open '''Language Support'''

[[File:~~media/image363~~plus5-img363.png~~|575x351px~~]]</li>

<li>Then find the '''Chinese (China)''' option

[[File:~~media/image364~~plus5-img364.png~~|318x311px~~]]</li>

<li>Then use the left mouse button to select '''Chinese (China)''' and hold it down, and then drag it up to the beginning. The display after dragging is shown in the figure below：

[[File:~~media/image365~~plus5-img365.png~~|324x320px~~]]</li>

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

<li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system

[[File:~~media/image366~~plus5-img366.png~~|321x316px~~]]</li>

<li>Then set the '''Keyboard input method system''' as '''fcitx'''

[[File:~~media/image367~~plus5-img367.png~~|327x320px~~]]</li>

<li>'''Then restart the linux system to make the configuration effective'''</li>

<li>After re -entering the system, please choose '''not to ask me again''' at the interface below, and then determine whether the standard folder should be updated in Chinese according to your preference

[[File:~~media/image368~~plus5-img368.png~~|303x247px~~]]</li>

<li>Then you can see that the desktop is displayed as Chinese

[[File:~~media/image369~~plus5-img369.png~~|575x383px~~]]</li>

<li>Then we can open the '''Geany''' test in the Chinese input method. The way to open the way is shown in the figure below

[[File:~~media/image370~~plus5-img370.png~~|576x292px~~]]</li>

<li>After opening '''Geany''', the default is an English input method. We can switch into Chinese input method through the '''Ctrl+Space''' shortcut keys, and then we can enter Chinese

[[File:~~media/image371~~plus5-img371.png~~|575x308px~~]]</li></ol>

<li>First open '''Language Support'''

[[File:~~media/image363~~plus5-img363.png~~|575x351px~~]]</li>

<li>Then find the '''Chinese (China)''' option

[[File:~~media/image372~~plus5-img372.png~~|249x242px~~]]</li>

<li>Then please use the mouse to select '''Chinese (China)''' and hold it down, and then drag it up to the beginning. The display after the dragging is shown in the figure below:

[[File:~~media/image373~~plus5-img373.png~~|267x262px~~]]</li>

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|

<big>'''Note that this step is not very easy to drag, please try a few more ~~times。~~times.'''</big>

|}

</ol>

<li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system

[[File:~~media/image374~~plus5-img374.png~~|287x282px~~]]</li>

<li>'''Then restart the linux system to make the configuration effective'''</li>

<li>After re-entering the system, please choose '''not to ask me again''' at the interface below, and then determine whether the standard folder should be updated to Chinese according to your preference

[[File:~~media/image368~~plus5-img368.png~~|303x247px~~]]</li>

<li>Then you can see that the desktop is displayed as Chinese

[[File:~~media/image369~~plus5-img369.png~~|575x383px~~]]</li>

<li>Then open the Fcitx5 configuration program

[[File:~~media/image375~~plus5-img375.png~~|575x349px~~]]</li>

<li>Then choose to use Pinyin input method

[[File:~~media/image376~~plus5-img376.png~~|338x267px~~]]</li>

<li>The interface after selecting is shown below, then click OK

[[File:~~media/image377~~plus5-img377.png~~|366x290px~~]]</li>

<li>Then we can open the '''Geany''' to test Chinese input method.The way to open is shown in the figure below

[[File:~~media/image370~~plus5-img370.png~~|576x292px~~]]</li>

<li>After opening '''Geany''', the default is an English input method. We can switch into Chinese input method through the '''Ctrl+Space''' shortcut keys, and then we can enter Chinese

[[File:~~media/image378~~plus5-img378.png~~|434x308px~~]]</li></ol>

|-

|

<big>'''Ubuntu Gnome Wayland image does not support ~~nomachine~~ NoMachine and VNC described here to remotely log in to the desktop.'''</big>

|}

|-

|

<big>'''Make sure the Ubuntu or Debian system installed on the development board is a desktop version. In addition, ~~nomachine~~ NoMachine also provides detailed documents. It is strongly recommended to read this document to be familiar with the use of ~~nomachine~~NoMachine. The document links are shown below：'''

'''https://knowledgebase.nomachine.com/DT10R00166'''</big>

|-

|

<big>'''~~Nomachine~~ NoMachine supports Windows, Mac, Linux, iOS, and Android platforms, so we can remotely log in to control Orange PI development boards through ~~Nomachine~~ NoMachine on multiple devices. The following demonstrates the Linux system desktop of the Orange PI development board through ~~Nomachine~~ NoMachine in Windows. For installation methods for other platforms, please refer to the official documentation of ~~Nomachine。~~NoMachine.'''</big>

|}

[[File:~~media/image379~~plus5-img379.png~~|575x227px~~]]

</ol>

~~</li></ol>~~

<li>In addition, you can also download the installation package of '''NoMachine''' in the '''official tools'''

[[File:~~media/image380~~plus5-img380.png~~|70x86px~~]]

First Enter the '''remote login software-Nomachine''' Folder

[[File:~~media/image381~~plus5-img381.png~~|256x46px~~]]

Then download the arm64 version of the deb installation package

[[File:~~media/image382~~plus5-img382.png~~|180x109px~~]]</li>

<li>Then upload the downloaded '''nomachine_x.x.x_x_arm64.deb''' to the Linux system of the development board</li>

<li>Then use the following command to install '''NoMachine''' in the Linux system in the development board

|}

</li></ol>

<li>Then download the NoMachine software Windows version of the installation package, the download address is shown below</li>

|}

[[File:~~media/image383~~plus5-img383.png~~|575x163px~~]]

</ol>

<li>Then install nomachine in Windows. '''Please restart the computer after installation'''</li>

<li>Then open '''NoMachine''' in Window

[[File:~~media/image384~~plus5-img384.png~~|76x66px~~]]</li>

<li>After Nomachine is started, it will automatically scan other devices installed in the local area network. After entering the main interface of Nomachine, you can see that the development board is already in the connected device list, and then click the location shown in the red box below in the figure below. You can start logging in to the Linux system desktop of the development board

[[File:~~media/image385~~plus5-img385.png~~|321x92px~~]]</li>

<li>Then click '''OK'''

[[File:~~media/image386~~plus5-img386.png~~|269x184px~~]]</li>

<li>Then enter the username and password of the linux system in the corresponding position in the figure below, and then click '''OK''' to start logging in

[[File:~~media/image387~~plus5-img387-1.png~~|303x204px~~]]</li>

<li>Then click OK in the next interface</li>

<li>Finally, you can see the desktop of the development board Linux system

[[File:~~media/image388~~plus5-img388.png~~|411x246px~~]]</li></ol>

<li>The steps of using MobaxTerm software to connect the development board Linux system desktop are shown below：

<li>First click the session, then select VNC, then fill in the IP ~~>~~ address and port of the development board, and finally click ~~>~~ OK to confirm</li>

[[File:~~media/image389~~plus5-img389.png~~|490x349px|图片1208~~]]

</div></ol>

<li>Then enter the password of the previously set VNC

[[File:~~media/image390~~plus5-img390.png~~|221x105px~~]]</li><li>The interface after the login is successfully displayed as shown in ~~>~~ the figure below, and then you can remotely operate the desktop of ~~>~~ the linux system remotely</li>

[[File:~~media/image391~~plus5-img391.png~~|405x293px~~]]

</ol>

</li></ol>

|-

|

<big>'''Use CTRL+D shortcut key to exit Python's interactive ~~mode。~~mode.'''</big>

|}

</li>

<li>Debian Bullseye's compilation tool and operating environment without Java default

<li>You can use the following command to install openjdk. The latest ~~>~~ version in Debian Bullseye is openjdk-17

{| class="wikitable" style="width:800px;"

|-

|

<big>'''Use CTRL+D shortcut key to exit Python's interactive ~~mode。~~mode.'''</big>

|}

</li>

|-

|

<big>'''Use CTRL+D shortcut key to exit Python's interactive ~~mode。~~mode.'''</big>

|}

</li>

QMake version 3.1

Using Qt version '''5.15.2''' in /usr/lib/aarch64-linux-gnu

|}

</li>

<li>The QT version that comes with Debian12 is '''5.15.8'''

{| class="wikitable" style="width:800px;"

|-

|

orangepi@orangepi:~$ '''install_qt.sh'''

......

QMake version 3.1

Using Qt version '''5.15.8''' in /usr/lib/aarch64-linux-gnu

|}

</li></ol>

</li>

<li>Then you can see the lax icon of QT Creator in '''Applications'''

[[File:~~media/image392~~plus5-img392.png~~|576x270px~~]]

You can also use the following command to open QT Creator

{| class="wikitable" style="width:800px;"

|-

|

<big>'''During the startup process of QT and QT applications, if the error below is prompted, please ignore it directly. This error will not affect the operation of the application.。'''

</li>

<li>The interface after the QT Creator is opened is shown below

[[File:~~media/image393~~plus5-img393.png~~|576x306px~~]]</li>

<li>The version of QT Creator is shown below

<li>The default version of QT Creator in '''Ubuntu20.04''' is shown ~~>~~ below[[File:~~media/image394~~plus5-img394.png~~|576x308px~~]]</li><li>The default version of QT Creator in '''Ubuntu22.04''' is shown ~~>~~ below[[File:~~media/image395~~plus5-img395.png~~|575x307px~~]]</li>

<li>The default version of QT Creator in '''Debian11''' is shown below

[[File:~~media~~plus5-img396.png]]</li><li>The default version of QT Creator in '''Debian12''' is as follows</~~image396~~p>[[File:plus5-img396-1.png~~|575x309px~~]]</li></ol>

</li>

<li>Then set the QT

<li>First open '''Help'''->'''About Plugins...'''

[[File:~~media/image397~~plus5-img397.png~~|573x164px~~]]</li>

<li>Then remove the hook of '''ClangCodeModel'''

[[File:~~media/image398~~plus5-img398.png~~|575x359px~~]]</li>

<li>'''After setting, you need to restart Qt Creator'''</li>

<li>Then make sure ~~that~~ the GCC compiler used by QT Creator, if the ~~>~~ default is ~~CLANG~~Clang, please modify it to GCC{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Debian12 please skip this step.'''</big>|}[[File:~~media/image399~~plus5-img399.png~~|576x315px~~]][[File:~~media/image400~~plus5-img400.png~~|575x307px~~]]</li></ol>

</li>

<li>Then you can open an example code

[[File:~~media/image401~~plus5-img401.png~~|575x312px~~]]</li>

<li>After clicking the example code, you will automatically open the corresponding description document. You can carefully look at the instructions for the use

[[File:~~media/image402~~plus5-img402.png~~|576x218px~~]]</li>

<li>Then click '''Configure Project'''

[[File:~~media/image403~~plus5-img403.png~~|575x304px~~]]</li>

<li>Then click the sample code under the green triangle compilation and run in the lower left corner

[[File:~~media/image404~~plus5-img404.png~~|575x312px~~]]</li>

<li>After waiting for a while, the interface shown in the figure below will pop up. At this time, it means that QT can compile and run normally

[[File:~~media/image405~~plus5-img405.png~~|576x308px~~]]</li>

<li>Reference information

{| class="wikitable" style="width:800px;"

# The current active version of ROS 1 is shown below. The recommended version is '''Noetic Ninjemys'''

::[[File:~~media/image406~~plus5-img406.png~~|345x235px~~]]

::[[File:~~media/image407~~plus5-img407.png~~|576x210px~~]]

::{| class="wikitable" style="width:800px;"

'''http://wiki.ros.org/noetic/Installation'''

|}

[[File:~~media/image408~~plus5-img408.png~~|312x176px~~]]</li>

<li>Then install Ros1 with the following script

{| class="wikitable" style="width:800px;"

[[File:~~media/image409~~plus5-img409.png~~|575x275px|图片4~~]]

</div></li>

[[File:~~media/image410~~plus5-img410.png~~|576x275px|图片5~~]]

</div></ol>

<li>At this time, press the direction button on the keyboard to control the small turtles up, down, left and right

[[File:~~media/image411~~plus5-img411.png~~|575x296px~~]]</li></ol>

<li>The current active version of ROS 2 is shown below. The recommended version is '''Galactic Geochelone'''

[[File:~~media/image412~~plus5-img412.png~~|576x271px~~]][[File:~~media/image413~~plus5-img413.png~~|575x265px~~]]

{| class="wikitable" style="width:800px;"

[[File:~~media/image414~~plus5-img414.png~~|576x324px|1~~]]

</div></li>

[[File:~~media/image415~~plus5-img415.png~~|576x324px|Screenshot from 2023-05-20 17-42-58~~]]

</div></li>

<big>'''If you compile the code you copy here, if you have any problems, go to the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''official tool'''] to download the source code and upload it to the Linux system of the development board for testing'''</big>

[[File:~~media/image416~~plus5-img416.png|~~253x41px~~center]]

|}

<li>10.1 -inch MIPI LCD display+touch screen (this screen and OPI5/OPI5B universal)

[[File:~~media/image417~~plus5-img417.png~~|338x252px~~]]</li>

<li>Screen divert plate+31pin to 40pin line

[[File:~~media/image418~~plus5-img418.png~~|230x199px|DD9A8F44-0D8F-4f06-9473-B539DEED850C~~]]

</div></li>

[[File:~~media/image419~~plus5-img419.png~~|443x41px|C2164119-6EC3-49ae-9A95-BE323F51FAE1~~]]

</div></li>

<li>12pin touch screen row line

[[File:~~media/image420~~plus5-img420.png~~|344x50px~~]]</li></ol>

</li>

<li>According to the figure below, the 12PIN touch screen row, 31PIN to 40PIN ducts, and 30pin MIPI cables get on the screen dial board. Pay attention to line of the touch screen the blue insulation face under. If you get an error, it will cause no display or unable to touch

[[File:~~media/image421~~plus5-img421.png~~|574x142px~~]]</li>

<li>Place the connected rotor connected to the puzzle on the MIPI LCD screen according to the figure below, and connect the MIPI LCD screen and the rotary board through 31PIN to 40Pin row</li>

[[File:~~media/image422~~plus5-img422.png~~|382x563px~~]]

</ol>

<li>Then connect the touch screen and the rotor board through the 12PIN touch screen line, pay attention to the orientation of the insulating surface.

[[File:~~media/image423~~plus5-img423.png~~|253x161px~~]]</li>

<li>Finally connect to the LCD interface of the development board through the 30PIN MIPI duct

[[File:~~media/image424~~plus5-img424.png~~|405x225px~~]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

<big>'''Note that the touch interface below is not used for the LCD MIPI screen. It is currently a spare interface and cannot be used'''</big>

[[File:~~media/image425~~plus5-img425.png|~~334x70px~~center]]

|}

</li></ol>

<li>The Linux image defaults to the configuration of the mipi lcd screen by default. If you need to use the mipi lcd screen, you need to open it ~~manually。~~manually.</li>

<li>The position of the development board MIPI LCD screen interface is shown below：

[[File:~~media/image426~~plus5-img426.png~~|428x77px~~]]</li>

<li>The steps of opening the MIPI LCD configuration are shown below：

</li>

<li>Then choose '''System'''

[[File:~~media/image234~~plus5-img234.png~~|379x175px~~]]</li>

<li>Then choos '''Hardware'''

[[File:~~media/image235~~plus5-img235.png~~|379x164px~~]]</li>

<li>Then use the keyboard orientation to position the '''opi5plus-lcd''', and then use the '''space''' to select

[[File:~~media/image427~~plus5-img427.png~~|349x57px~~]]</li>

<li>Then select <Save>

[[File:~~media/image428~~plus5-img428.png~~|263x123px~~]]</li>

<li>Then sele '''<Back>'''

[[File:~~media/image429~~plus5-img429.png~~|264x116px~~]]</li>

<li>Then select the '''<Reboot>''' restart system to make the configuration effective

[[File:~~media/image430~~plus5-img430.png~~|226x105px~~]]</li></ol>

</li>

<li>After starting, you can see the display of the LCD screen as shown below (the default is vertical screen)：</li>

[[File:~~media/image431~~plus5-img431.png~~|169x244px~~]]

</ol>

|-

|

<big>'''Note that if/boot/orangepienv.txt is configured in the default default exiArgs = CMA = 128M, fbcon = rotate: 3 The configuration can be added to the extensraargs = cma = 128m (need to be separated by spaces)。.'''</big>

|}

</li></ol>

<li>First open '''Display''' settings in the Linux system

[[File:~~media/image432~~plus5-img432.png~~|339x234px~~]]</li>

<li>Then select the direction you want to rotate in the '''Rotation'''

<li>'''Inverted''': Flipting up and down is equivalent to rotating 180 > degrees</li>

<li>'''Right''': Rotate 90 degrees to the right

[[File:~~media/image433~~plus5-img433.png~~|330x208px~~]]</li></ol>

</li>

<li>Then click '''Apply'''

[[File:~~media/image434~~plus5-img434.png~~|330x207px~~]]</li>

<li>Then click '''Keep this configuration'''

[[File:~~media/image435~~plus5-img435.png~~|458x258px~~]]</li>

<li>At this time, the screen display has been rotated, and then the '''Display''' program is turned off</li>

<li>The above steps will only select the display direction, and it will not rotate the direction of touch. Use set_lcd_rotate.sh script to rotate the direction of touch. After this script is set, it will be automatically restarted, and then you can test whether the touch can be used normally

|}

</li>

<li>Set the '''bootlogo''' variable to '''true''' in'''/boot/orangepiEnv.txt''' to turn the opening and the logo

{| class="wikitable" style="width:800px;"

|-

<li>OV13850 camera at 13 million MIPI interface

[[File:~~media/image23~~plus5-img23.png~~|268x151px~~]]</li>

<li>13 million MIPI interface OV13855 camera

[[File:~~media/image24~~plus5-img24.png~~|253x150px~~]]The rotary board used by OV13850 and OV13855 cameras is the same as the FPC cable, but the two cameras are different from the position on the rotary board. The FPC lines are shown in the figure below. Please note that the FPC line is directed. It is marked that the '''TO MB''' must be inserted into the camera interface of the development board. It is marked that the end of '''TO CAMERA''' needs to be inserted on the camera transfer ~~board。~~board.</li>

[[File:~~media/image436~~plus5-img436.png~~|373x78px~~]]

</ol>

There are a total of 3 cameras on the camera to connect to the board, which can only be used one at the same time, as shown in the figure below, among which：

<li>The No. 3 interface is not used, just ignore it.</li>

[[File:~~media/image437~~plus5-img437-1.png~~|288x172px~~]]

</ol>

Orange Pi 5 Plus development board has a total of 1 camera interface, which is shown below：

[[File:~~media/image438~~plus5-img438.png~~|408x95px~~]]

The method of the camera inserted in the development board interface is shown below：

[[File:~~media/image439~~plus5-img439.png~~|332x154px~~]]

After connecting the camera to the development board, we can use the following method to test the camera：

</li>

<li>Then select '''System'''

[[File:~~media/image234~~plus5-img234.png~~|399x184px~~]]</li>

<li>Then choose '''Hardware'''

[[File:~~media/image235~~plus5-img235.png~~|403x175px~~]]</li><li>Then use the keyboard to locate the position shown in the figure below, and then use the camera you want to open in the space. Among them, '''opi5plus-ov13850''' means using an OV13850 camera, '''opi5plus-ov13855''' indicates the use of OV13855 ~~camera。~~camera.[[File:~~media/image440~~plus5-img440.png~~|400x37px~~]]</li>

<li>Then choose '''<Save>'''

[[File:~~media/image441~~plus5-img441.png~~|338x109px~~]]</li>

<li>Then choose '''<Back>'''

[[File:~~media/image442~~plus5-img442.png~~|338x86px~~]]</li>

<li>Then select the'''<Reboot>''' restart system to make the configuration effective

[[File:~~media/image239~~plus5-img239.png~~|316x139px~~]]</li>

<li>Then open a terminal in the desktop system and run the script below

{| class="wikitable" style="width:800px;"

[[File:~~media/image443~~plus5-img443.png~~|576x324px|1~~]]

</div></li></ol>

[[File:~~media/image444~~plus5-img444.~~jpeg|199x183px|IMG_256~~png]]

</div></li>

<li>Then press the button on the infrared receiver on the development board to press the button on the remote control. The position of the infrared receiver on the development board is as shown in the figure below：

[[File:~~media/image445~~plus5-img445.png~~|346x92px~~]]</li>

<li>Then you can see that '''evtest''' will print the received key value

{| class="wikitable" style="width:800px;"

<li>A RTC battery interface is reserved on the development board, which is shown below：

[[File:~~media/image28~~plus5-img28.png~~|344x126px~~]]</li>

<li>The RTC battery that needs to be purchased is shown below. The interface is 2pin, 1.25mm spacing

[[File:~~media/image27~~plus5-img27.png~~|152x81px~~]]</li>

<li>The RTC chip used on the development board is Hym8563TS. This chip has the following characteristics：

<li>The development board is used for interfaces that connect the heat sink fan. The interface specifications are '''2pin 1.25mm''' spacing, '''5V voltage driver''', and the position of the fan interface is shown in the figure below：

[[File:~~media/image19~~plus5-img19.png~~|410x171px~~]]</li>

<li>The fan on the development board can adjust the speed and switch through PWM, and the PWM pins used are '''PWM3_IR_M1'''</li>

<li>The Linux system uses the [https://github.com/orangepi-xunlong/linux-orangepi/blob/orange-pi-5.10-rk3588/drivers/hwmon/pwm-fan.c '''pwm-fan'''] driver to control the fan by default. The DTS configuration used is shown below：

== ~~The method of shutting down and restarting~~ How to use the ~~development board~~ ZFS file system ==

~~<ol style="list-style-type: decimal;">~~<li>In the process of running the Linux system, if the Type-C power supply is directly out of power, it may cause the file system to lose certain data or damage. Therefore, please use the '''poweroff''' command to turn off the linux system of the development board before power off. Then Unplug the power supply.{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|<pbig>'''The latest version of Ubuntu20.04, Ubuntu22.04, Debian11 and Debian12 desktop version systems have pre-installed zfs, you can use it directly.''' '''The pre-installed zfs version in Ubuntu20.04 and Ubuntu22.04 desktop systems is 2.1.6.''' '''The pre-installed zfs version in Debian11 and Debian12 desktop systems is 2.1.11.''' '''After the system starts, please first confirm whether the zfs kernel module has been loaded. If you can see zfs-related content using the lsmod command, it means that the system has pre-installed zfs.''' orangepi@orangepi:~$ '''~~sudo poweroff~~lsmod | grep "zfs"'''</pbig> zfs                     2801664     0 zunicode             327680     1   zfs zzstd                  471040     1   zfs zlua                    139264     1   zfs zcommon             69632     1   zfs znvpair                 61440     2   zfs,zcommon zavl                      16384     1   zfs icp                     221184     1   zfs spl                       77824     6   zfs,icp,zzstd,znvpair,zcommon,zavl

|}

~~</li>~~

~~<li>In addition, the development board is equipped with a switch button, and you can also '''short press''' the switch button on the development board to turn off.~~

~~[[File:media/image446.png|444x98px]]</li>~~

=== How to install ZFS ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|

<big>'''~~Note~~ Before installing zfs, please ensure that the Linux ~~desktop system will pop up~~ image used is the ~~confirmation box shown~~ latest version. In addition, if zfs is already installed in the ~~figure below after pressing the buttons~~system, there is no need to install it again. ~~You~~ '''</big>|}Before installing zfs, you need to ~~click~~ install the ~~Shut Down option~~ kernel header file first. '''For the method of installing the kernel header file''', please refer to ~~shut down~~the instructions in the section on the method of installing the kernel header file. In Ubuntu20.04, Ubuntu22.04 and Debian11 systems, zfs cannot be installed directly through apt, because the default apt source zfs version is lower than 2.1.6, and there is a problem of incompatibility with rk linux5.10 kernel. This problem is fixed in zfs version 2.1.6 and later. To solve this problem, we provide a zfs deb package that can be installed normally, which can be downloaded from the '''official tool''' of the development board. Open the '''official tool''', and then enter the '''zfs-related deb package folders used by Ubuntu and Debian systems'''. You can see three types of deb packages: Ubuntu20.04, Ubuntu22.04 and Debian11. Please download the required version. [[File:5plus-3.png]]</~~big~~p> After downloading the zfs deb packages of the corresponding version, please upload them to the Linux system of the development board. For the upload method, please refer to the description in [[Orange Pi 5 Plus#The method of uploading files to the Linux system of the development board|'''the section of the method of uploading files to the Linux system of the development board''']].

~~[[File~~After the upload is complete, use the '''cd''' command in the command line of the development board linux system to enter the deb package directory, and then use the following command to install the zfs deb package.{| class="wikitable" style="width:~~media~~800px;" |-|orangepi@orangepi:~$ '''sudo apt install ./~~image447~~*.~~png|256x240px]]~~deb'''

|}

~~</ol><ol start="3" style="list-style-type: decimal;"><li>~~After ~~shutting down~~the installation is complete, ~~press~~ use the ~~switch button on~~ following command to see the ~~development board to turn on.[[File~~zfs-related kernel modules:~~media/image446.png|444x98px]]</li><li>Restart the command of the Linux system.~~

{| class="wikitable" style="width:800px;"

|-

|

~~~~orangepi@orangepi:~$ '''~~sudo~~ls /lib/modules/5.10.110-rockchip-rk3588/updates/dkms/icp.ko spl.ko zavl.ko zcommon.ko zfs.ko zlua.ko znvpair.ko zunicode.ko zzstd.ko''' ~~'''reboot'''~~

|}

~~</li></ol>~~

~~~~ ~~= '''Ubuntu22.04 Gnome Wayland Desktop system instructions''' =~~to see that the zfs kernel module will be automatically loaded:

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|

~~<big>~~orangepi@orangepi:~$ '''~~ubuntu22.04 gnome image default pre -installed PanFork Mesa user space library, pre -installed Kodi player and Chromium browser support hard solution video.~~lsmod | grep "zfs"''' zfs                     2801664     0 zunicode             327680     1   zfs zzstd                  471040     1   zfs zlua                    139264     1   zfs zcommon             69632     1   zfs znvpair                 61440     2   zfs,zcommon zavl                      16384     1   zfs icp                     221184     1   zfs

~~'''It should be noted that this image needs to be used under Wayland. If you need to use X11~~spl                       77824     6   zfs, ~~select the XFCE type image.'''</big>~~icp,zzstd,znvpair,zcommon,zavl

|}

~~<span id="ubuntu22~~In Debian12, the default version of zfs is 2.~~04-gnome-desktop-~~1.11, so we can install zfs directly through the following command. Again, please make sure that the system~~-adaptation-situation">== Ubuntu22~~has installed the deb package of the kernel header file before installation.~~04 GNOME desktop system adaptation situation ==~~

{| class="wikitable" style="width:800px;"

|-

| ~~style="text-align~~orangepi@orangepi: ~~left;"|~~ ~$ '''~~Function~~sudo apt install -y zfsutils-linux zfs-dkms'''| } === Methods of creating ZFS pools ==={| class="wikitable" style="~~text~~background-~~align~~color:#ffffdc;width: ~~left~~800px;"~~| '''Ubuntu22.04 Gnome Wayland'''~~

|-

| ~~style="text-align: left;"~~<big>'''ZFS is based on storage pools, we can add multiple physical storage devices to the pool, and then allocate storage space from this pool.''' '''The following content is demonstrated based on the development board connected to an NVMe SSD and a USB flash drive.'''</big>| } 1) First, we can use the '''~~HDMI TX1video~~lsblk'''command to view all storage devices on the development board. The current development board is connected to an NVMe SSD and a U disk. The output is as follows: [[File:5plus-4.png]] 2) Then enter the following command to create a ZFS pool, including two storage devices, NVMe SSD and U disk {| class="wikitable" style="~~text-align~~width: ~~left~~800px;"~~| '''OK'''~~

|-

| ~~style="text~~orangepi@orangepi:~$ '''sudo zpool create -~~align~~f pool1 /dev/nvme0n1 /dev/sda'''|} 3) Then use the '''zpool list''' command to see that the system has created a ZFS pool named '''pool1''', and the size of the ZFS pool pool1 is the size of the NVME SSD plus the size of the U disk [[File: ~~left;"|~~ 5plus-5.png]] 4) Then execute '''df -h''' to see that '''pool1''' is mounted to the '''~~HDMI TX1 Audio~~/pool1'''directory {| class="wikitable" style="~~text-align~~width: ~~left~~800px;"~~| '''OK'''~~

|-

| ~~style="text~~orangepi@orangepi:~$ '''df -~~align: left~~h''' Filesystem                 Size     Used Avail Use% Mounted on tmpfs                    1.6G     18M 1.6G 2% /run /dev/mmcblk0p2     29G     6.0G 22G 22% / tmpfs                    7.7G     46M 7.7G 1% /dev/shm tmpfs                    5.0M     4.0K 5.0M 1% /run/lock tmpfs                    7.7G     944K 7.7G 1% /tmp /dev/mmcblk0p1     1022M     115M 908M 12% /boot /dev/zram1                 188M     4.5M 169M 3% /var/log tmpfs                    1.6G    "| 80K 1.6G 1% /run/user/1000 '''~~HDMI TX2 video~~pool1                    489G     9.3M 489G 1% /pool1''' |}5) Use the following command to see that the file system type of pool1 is zfs {| class="wikitable" style="~~text-align~~width: ~~left~~800px;"~~| '''OK'''~~

|-

| ~~style="text-align~~orangepi@orangepi: ~~left;"~~~$ '''mount | grep pool1''' pool1 on /pool1 type '''~~HDMI TX2 Audio~~zfs'''(rw,xattr,noacl)|}6) Then we can test copying a file to the ZFS pool {| class="wikitable" style="~~text-align~~width: ~~left~~800px;"~~| '''OK'''~~

|-

| ~~style="text~~orangepi@orangepi:~$ '''sudo cp -~~align: left;"|~~ v /usr/local/test.mp4 /pool1/''' '~~HDMI RX video~~/usr/local/test.mp4'-> '/pool1/test.mp4'| } === Test the data deduplication function of ZFS ===1) The data deduplication function of ZFS is disabled by default, we need to execute the following command to enable it {| class="wikitable" style="~~text-align~~width: ~~left~~800px;"~~| '''OK'''~~

|-

| ~~style="text-align~~orangepi@orangepi: ~~left;"|~~ ~$ '''~~HDMI RX Audio~~sudo zfs set dedup=on pool1'''| }2) Then do a simple test, first enter pool1, and then execute the following command to generate a random file with a size of 1G {| class="wikitable" style="~~text-align~~width: ~~left~~800px;"~~| '''OK'''~~

|-

| ~~style="text-align~~orangepi@orangepi:~$ '''cd /pool1/ ''' root@orangepi: ~~left;"|~~ /pool1$ '''~~USB2~~sudo dd if=/dev/urandom of=test.~~0X2~~1g bs=1M count=1024''' 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 5.04367 s, 213 MB/s | }3) Then use the following command to copy 1000 random files of size 1G {| class="wikitable" style="~~text-align~~width: ~~left~~800px;"~~| '''OK'''~~

|-

| ~~style~~root@orangepi:/pool1$ '''for ((i=~~"text-align: left~~0; i<1000; i++)); do sudo cp test.1g $i.test.1g;"done'''| }4) Then use '''~~USB3.0X2~~du -lh''' to see that there are currently 1002G of data in the pool, but in fact the size of the ZFS pool is only '''504GB'''(the total capacity of SSD+U disk), which cannot hold such a large amount of data {| class="wikitable" style="~~text-align~~width: ~~left~~800px;"~~| '''OK'''~~

|-

| ~~style="text~~root@orangepi:/pool1$ '''du -~~align: left;"~~lh''' 1002G| }5) Then use the '''zpool list'''2command to see that only 1.01G is actually occupied, because these 1001 files are all duplicates, indicating that the data deduplication function is effective.~~5G PCIe network port X2~~ [[File:5plus-6.png]] === Test the data compression function of ZFS === 1) Because the stored data is different, the disk space saved by compression will also be different, so we choose to compress relatively large plain text files for compression testing, and execute the following commands to pack the '''/var/log/''' and '''/etc/'''directories into a tarball {| class="wikitable" style="~~text-align~~width: ~~left~~800px;"~~| '''OK'''~~

|-

| ~~style="text-align~~orangepi@orangepi:~$ '''cd /pool1/''' root@orangepi: ~~left;"|~~ /pool1$ '''2sudo tar -cf text.~~5G PCIe network port light~~tar /var/log/ /etc/'''| ~~style="text~~}2) Then the file size that can be seen through the '''ls -~~align: left;"|~~ lh''' command and the space occupied in the ZFS pool are both '''OK27M''' [[File:5plus-7.png]] 3) Then we enable compression in the ZFS pool pool1 {| class="wikitable" style="width:800px;"

|-

| ~~style~~root@orangepi:/pool1$ '''sudo zfs set compression=~~"text-align: left;"~~lz4 pool1'''| }4) Then execute the following command again to package the '''/var/log/''' and '''~~Debug serial port~~/etc/'''directories into a tar package {| class="wikitable" style="~~text-align~~width: ~~left~~800px;"~~| '''OK'''~~

|-

| ~~style="~~root@orangepi:/pool1$ '''sudo tar -cf text~~-align: left;"~~.tar /var/log/ /etc/'''| }5) At this time, you can see that the size of the '''~~RTC chip~~text.tar'''file is still 27M, but it only occupies 9.47M in the ZFS pool, indicating that the file is compressed [[File:5plus-8.png]] == The method of shutting down and restarting the development board == | <ol style="~~text~~list-style-~~align~~type: ~~left~~decimal;"| ><li>In the process of running the Linux system, if the Type-C power supply is directly out of power, it may cause the file system to lose certain data or damage. Therefore, please use the '''OKpoweroff'''command to turn off the linux system of the development board before power off. Then Unplug the power supply.{| class="wikitable" style="width:800px;"

|-

| ~~style="text-align~~orangepi@orangepi: ~~left;"~~~$ '''sudo poweroff'''| }</li><li>In addition, the development board is equipped with a switch button, and you can also '''~~FAN Fan interface~~short press'''the switch button on the development board to turn off.[[File:plus5-img446.png]]</li> {| class="wikitable" style="~~text~~background-~~align~~color:#ffffdc;width: ~~left~~800px;"~~| '''OK'''~~

|-

| ~~style="text-align: left;"|~~ <big>'''~~eMMC Extension ports~~Note that the Linux desktop system will pop up the confirmation box shown in the figure below after pressing the buttons. You need to click the Shut Down option to shut down.'''</big> [[File:plus5-img447.png| center]]|}</ol><ol start="3" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"><li>After shutting down, press the switch button on the development board to turn on.[[File:plus5-img446.png]]</li><li>Restart the command of the Linux system.{| ~~'''OK'''~~class="wikitable" style="width:800px;"

|-

| ~~style~~orangepi@orangepi:~$ '''sudo''' '''reboot'''|}</li></ol> = '''~~AP6275P-WIFI~~Ubuntu22.04 Gnome Wayland Desktop system instructions'''= {| class="wikitable" style="~~text~~background-~~align~~color:#ffffdc;width: ~~left~~800px;"~~| '''OK'''~~

|-

| <big>'''ubuntu22.04 gnome image default pre -installed PanFork Mesa user space library, pre -installed Kodi player and Chromium browser support hard solution video.''' '''It should be noted that this image needs to be used under Wayland. If you need to use X11, select the XFCE type image.'''</big>|} == Ubuntu22.04 GNOME desktop system adaptation situation == {| class="wikitable" style="width:800px;"|-| style="text-align: left;"| '''Function'''| style="text-align: left;"| '''Ubuntu22.04 Gnome Wayland'''|-| style="text-align: left;"| '''HDMI TX1video'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''HDMI TX1 Audio'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''HDMI TX2 video'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''HDMI TX2 Audio'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''HDMI RX video'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''HDMI RX Audio'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''USB2.0X2'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''USB3.0X2'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''2.5G PCIe network port X2'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''2.5G PCIe network port light'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''Debug serial port'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''RTC chip'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''FAN Fan interface'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''eMMC Extension ports'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''AP6275P-WIFI'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''AP6275P-BT'''

| style="text-align: left;"| '''OK'''

|-

<li>First open the settings

[[File:~~media/image448~~plus5-img448.png~~|243x181px~~]]</li>

<li>Then select about, if the '''Wayland''' description settings displayed by '''Windowing System''' in a column are correct

[[File:~~media/image449~~plus5-img449.png~~|362x303px~~]]</li></ol>

</li>

<li>When the '''Log Out''' is out of the system, it will enter the login interface below

[[File:~~media/image450~~plus5-img450.png|258x108px]]</li>

<li>Please click the location shown below before logging in to the system again

[[File:~~media/image451~~plus5-img451.png~~|259x108px~~]]</li>

<li>Then select '''Ubuntu on Wayland''' and enter the password login system

[[File:~~media/image452~~plus5-img452.png~~|218x312px~~]]</li></ol>

<li>Open the settings first

[[File:~~media/image448~~plus5-img448.png~~|221x164px~~]]</li>

<li>Then select '''Sound''', and then select the audio device you want to use in '''Output Device'''

[[File:~~media/image453~~plus5-img453.png~~|375x314px~~]]</li></ol>

orangepi@orangepi:~$ '''glmark2'''

|}

[[File:~~media/image454~~plus5-img454.png~~|381x258px~~]]</li>

<li>glmark2 running score test is generally more than 1,000 points

[[File:~~media/image455~~plus5-img455.png~~|331x222px~~]]</li>

<li>Run '''gpu_load.sh''' script to view the current load of the GPU

{| class="wikitable" style="width:800px;"

orangepi@orangepi:~$ '''gpu_load.sh'''

|}

[[File:~~media/image456~~plus5-img456.png~~|529x281px~~]]</li></ol>

<li>First open the chromium browser

[[File:~~media/image457~~plus5-img457.png~~|576x324px~~]]</li>

<li>Then enter '''chrome://gpu''' in the Chromium browser to view the support of GPU and video decoding

[[File:~~media/image458~~plus5-img458.png~~|337x197px~~]]</li>

<li>Then you can open a video website to play a video file, or enter the following path name player to play a test video file in the browser.

{| class="wikitable" style="width:800px;"

[[File:~~media/image459~~plus5-img459.png~~|576x324px|Screenshot from 2023-05-22 15-01-46~~]]

</div></li></ol>

<li>First log in the system

[[File:~~media/image460~~plus5-img460.png~~|231x153px~~]] [[File:~~media/image461~~plus5-img461.png~~|266x118px~~]]</li>

<li>When the login system will enter the login interface below

[[File:~~media/image450~~plus5-img450.png~~|258x108px~~]]</li>

<li>Then click the location shown in the figure below

[[File:~~media/image451~~plus5-img451.png~~|259x108px~~]]</li>

<li>Then select '''Kodi Wayland''', then enter the password login system

[[File:~~media/image462~~plus5-img462.png~~|262x273px~~]]</li>

<li>The interface after Kodi is opened is displayed as shown below

[[File:~~media/image463~~plus5-img463.png~~|461x259px|Screenshot from 2023-03-03 14-31-20~~]]

</div></li>

<li>Then click Settings

[[File:~~media/image464~~plus5-img464.png~~|343x149px~~]]</li>

<li>Then select '''Player'''

[[File:~~media/image465~~plus5-img465.png~~|474x268px~~]]</li>

<li>Then select '''Videos''', and then click '''Standard''' in the lower left corner

[[File:~~media/image466~~plus5-img466.png~~|477x268px~~]]</li>

<li>After clicking twice, it will be switched to the '''Expert''' mode. The specific display is shown in the figure below

[[File:~~media/image467~~plus5-img467.png~~|441x249px~~]]</li>

<li>Then open the '''Allow using DRM PRIME decoder''' in the P'''rocessing''' settings

[[File:~~media/image468~~plus5-img468.png~~|442x250px~~]]</li>

<li>Then let's introduce a system's own test video test. You can also upload the video you want to play to the system, and then import and play

<li>First enter the main interface, then select '''Movies'''

[[File:~~media/image469~~plus5-img469.png~~|424x239px~~]]</li>

<li>Then choose '''Add videos...'''

[[File:~~media/image470~~plus5-img470.png~~|429x242px~~]]</li>

<li>Then choose '''Browse'''

[[File:~~media/image471~~plus5-img471.png~~|428x270px~~]]</li>

<li>Then choose '''Root filesystem'''

[[File:~~media/image472~~plus5-img472.png~~|414x169px~~]]</li>

<li>Then choose '''usr'''

[[File:~~media/image473~~plus5-img473.png~~|416x273px~~]]</li>

<li>Then choose '''local'''

[[File:~~media/image474~~plus5-img474.png~~|417x274px~~]]</li>

<li>Then choose '''OK'''

[[File:~~media/image475~~plus5-img475.png~~|425x278px~~]]</li>

<li>Then choose '''OK'''

[[File:~~media/image476~~plus5-img476.png~~|431x273px~~]]</li>

<li>Then choose OK

[[File:~~media/image477~~plus5-img477.png~~|454x260px~~]]</li>

<li>Then enter the Local folder

[[File:~~media/image478~~plus5-img478.png~~|456x258px~~]]</li>

<li>Then you can play '''test.mp4''' test video

[[File:~~media/image479~~plus5-img479.png~~|462x262px~~]]</li></ol>

</li>

<li>When playing the video, you can run the '''vpu_debug.sh''' script under the command line (via SSH or serial port). If there is a print output below, it means that there is a hardware to decode the video

</li>

<li>Play '''test.mp4''' video file CPU occupation rates of about '''20%~ 30%'''.

[[File:~~media/image480~~plus5-img480.png~~|577x126px~~]]</li></ol>

[[File:~~media/image481~~plus5-img481.png~~|576x324px|Screenshot from 2023-05-22 15-17-44~~]]

</div></li>

<li>Open the settings first

[[File:~~media/image448~~plus5-img448.png~~|243x181px~~]]</li>

<li>Then find the '''Region & Language''' option, and then click '''Manage Installed Languages''' options

[[File:~~media/image482~~plus5-img482.png~~|576x352px~~]]</li>

<li>Then use the left mouse button to select '''Chinese (China)''' and hold it down, and then drag it up to the beginning. The display after the dragging is shown in the figure below：

[[File:~~media/image483~~plus5-img483.png~~|575x428px~~]]</li>

<li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system

[[File:~~media/image484~~plus5-img484.png~~|576x427px~~]]</li>

<li>'''Then restart the linux system to make the configuration effective'''</li>

<li>After re -entering the system, please choose not to '''ask me again''' at the interface below, and then determine whether the standard folder should be updated to Chinese according to your preference

[[File:~~media/image485~~plus5-img485.png~~|340x276px~~]]</li>

<li>Then you can see that the desktop is displayed as Chinese

[[File:~~media/image486~~plus5-img486.png~~|576x324px|截图 2023-03-08 09-34-07~~]]

</div></li>

<li>Then open the Fcitx5 configuration program

[[File:~~media/image487~~plus5-img487.png|576x326px]]</li>

<li>Then choose to use Pinyin input method

[[File:~~media/image488.jpeg|576x429px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~plus5-6img488.~~jpg未标题-6~~png]]

</div></li>

<li>The interface after selecting is shown below, then click OK

[[File:~~media/image489~~plus5-img489.png~~|504x373px~~]]</li>

<li>Then we can open the Chinese input method of '''Geany''' test, and the way to open is shown in the figure below

[[File:~~media/image490~~plus5-img490.png~~|575x325px~~]]</li>

<li>After opening '''Geany''', the default is an English input method. We can switch into Chinese input method through the '''Ctrl+Space''' shortcut keys, and then we can enter Chinese

[[File:~~media/image491~~plus5-img491.png~~|576x364px~~]]</li></ol>

'''（PCIE+USB Port)'''

| [[File:~~media/image230~~plus5-img230.png]]

| '''Debian'''

'''（PCIE+USB Port)'''

| [[File:~~media%20/image231~~plus5-img231.png]]

| '''Debian'''

'''（PCIE+USB Port)'''

| [[File:~~media/image232~~plus5-img232.png]]

| '''Debian'''

'''OPi OS Droid'''

|}

::{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|

<big>'''Pay attention to RTL8852BE, please do not buy the module shown in the figure below, there will be problems after testing.'''</big>

[[File:plus5-img232-10.png|center]]

|}

<li>Then insert the WiFi module into the M.2 E-Key interface of the development board and fix it

[[File:~~media/image233~~plus5-img233.png~~|403x181px~~]]</li><li>~~Then open the configuration of~~ If everything is normal after the ~~WIFI module in the OPi OS Arch~~ systemstarts, ~~and~~ use the ~~steps are shown below：<ol style="list-style-type: lower-alpha;"><li>First add a line configuration~~ following command to see the ~~> '''/boot/extlinux/extlinux.conf'''.~~WIFI device nodea

{| class="wikitable" style="width:800px;"

|-

|

~~~~[orangepi@orangepi ~]$ '''~~sudo vim /boot/extlinux/extlinux.conf'''LABEL Orange PiLINUX /ImageFDT /dtbs/rockchip/rk3588-orangepi-5-plus.dtb'''FDTOVERLAYS /dtbs/rockchip/overlay/rk3588-wifi-pcie.dtbo #What needs to be added~~ip a'''~~~~|}~~</li><li>'''Then restart the OPi OS Arch system'''</li></ol></li>~~<li>If everything is normal after restarting the system, you can see the WiFi device node with the following command. If you can't see it, please check if there is a problem with the previous configuration.~~{| class="wikitable" style="width:800px;"~~ |-|~~[orangepi@orangepi ~]$ '''ip addr show wlan0'''~~......~~~~4: ~~'''~~wlan0~~'''~~: ~~<~~<BROADCAST,MULTICAST,UP,LOWER_UP~~>~~ > mtu 1500 qdisc noqueue state UP group default qlen 1000~~~~ :~~~~link/ether 38:7a:0e:e3:80:05 brd ff:ff:ff:ff:ff:ff~~~~ :~~~~inet 192.168.1.237/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0~~~~ ::~~~~valid_lft 42938sec preferred_lft 42938sec~~~~ :~~~~inet6 fe80::a098:5942:16e:e817/64 scope link noprefixroute~~~~ ::~~~~valid_lft forever preferred_lft forever~~~~

|}

</li>

<li>First click the area in the upper right corner of the desktop

[[File:~~media/image492~~plus5-img492.png~~|252x160px~~]]</li>

<li>Then choose Wi-Fi

[[File:~~media/image493~~plus5-img493.png~~|337x215px~~]]</li>

<li>Then select the WIFI you want to connect

[[File:~~media/image494~~plus5-img494.png~~|466x249px~~]]</li>

<li>Then enter the password of the wifi, and click '''Connect'''

[[File:~~media/image495~~plus5-img495.png~~|284x188px~~]]</li>

<li>Then enter the following interface to see the wifi connection

[[File:~~media/image496~~plus5-img496.png~~|544x383px~~]]</li></ol>

</li>

<li>Example of Bluetooth use：

<li>First click the area in the upper right corner of the desktop

[[File:~~media/image492~~plus5-img492.png~~|272x173px~~]]</li>

<li>Then open the settings

[[File:~~media/image497~~plus5-img497.png~~|288x238px~~]]</li><li>Then select Bluetooth in the settings, and make sure that the ~~>~~ switch button in the upper right corner of the Bluetooth is ~~>~~ opened[[File:~~media/image498~~plus5-img498.png~~|457x301px~~]]</li><li>Then choose the Bluetooth device you want to configure the ~~>~~ right, such as pairing with Android phones[[File:~~media/image499~~plus5-img499.png~~|451x296px~~]]</li><li>Then click '''Confirm''', the mobile phone also needs to confirm ~~>~~ the pairing[[File:~~media/image500~~plus5-img500.png~~|221x142px~~]]</li>

<li>The display of the Bluetooth and Android phone is shown below：

[[File:~~media/image501~~plus5-img501.png~~|451x296px~~]]</li><li>Then click the paired Bluetooth device to pop up the operating ~~>~~ interface shown in the figure below[[File:~~media/image502~~plus5-img502.png~~|480x315px~~]]</li><li>Click '''Send Files...'''you can send a file to the phone</li>

[[File:~~media/image503~~plus5-img503.png~~|525x297px~~]]

</ol>

<li>The schematic diagram of the Bluetooth sent pictures to the phone is ~~>~~ shown below：

[[File:~~media/image504~~plus5-img504.png~~|576x324px|Screenshot from 2023-04-21 04-17-07~~]]

</div></li></ol>

<li>10.1 -inch MIPI LCD display+touch screen (common to OPI5/OPI5B)

[[File:~~media/image417~~plus5-img417.png~~|308x237px~~]]</li>

<li>Screen divert+31pin to 40pin exhaust

[[File:~~media/image418~~plus5-img418.png~~|160x139px|DD9A8F44-0D8F-4f06-9473-B539DEED850C~~]]

</div></li>

[[File:~~media/image419~~plus5-img419.png~~|421x39px|C2164119-6EC3-49ae-9A95-BE323F51FAE1~~]]

</div></li>

<li>12pin touch screen line

[[File:~~media/image420~~plus5-img420.png~~|300x44px~~]]</li></ol>

</li>

<li>According to the figure below, the 12PIN touch screen row, 31PIN to 40Pin line, and 30Pin MIPI cables get on the screen dial board. Pay attention to '''the blue insulation of the touch screen row line face to down'''. If an error is connected, it will cause no display or unable to touch..[[File:~~media/image421~~plus5-img421.png~~|574x142px~~]]</li><li>Place the connected rotor connected to the puzzle on the MIPI LCD screen according to the figure below, and connect the MIPI LCD screen and the rotary board through 31PIN to 40Pin row</li>~~</ol>~~ ~~[[File:media/image422.png|382x563px]]~~

[[File:plus5-img422.png]]

</ol>

<li>Then connect the touch screen and the rotor board through the 12PIN touch screen line, pay attention to the orientation of the insulating surface

[[File:~~media/image423~~plus5-img423.png~~|246x156px~~]]</li>

<li>Finally connect to the LCD interface of the development board through the 30PIN MIPI duct.

[[File:~~media/image424~~plus5-img424.png~~|363x202px~~]]{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the touch interface below is not used for the LCD MIPI screen. It is currently a spare interface and cannot be used.'''</big> [[File:~~media/image425~~plus5-img425.png|~~334x70px~~center]]|}</li></ol>

=== How to open 10.1 -inch MIPI LCD screen configuration ===

<li>The position of the interface of the MIPI LCD screen on the development board is shown in the figure below

[[File:~~media/image426~~plus5-img426.png~~|575x103px~~]]</li>

<li>OPi OS Arch image default is not to open the mipi lcd screen configuration. If you need to use the mipi lcd screen, you need to open it manually. The method of opening the mipi lcd configuration is shown below：

<li>First add the following configuration ~~>~~ in'''/boot/extlinux/extlinux.conf'''{| class="wikitable" style="width:800px;" |-|

[orangepi@orangepi ~]$ '''sudo vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

FDT /dtbs/rockchip/rk3588-orangepi-5-plus.dtb

'''FDTOVERLAYS /dtbs/rockchip/overlay/rk3588-opi5plus-lcd.dtbo #The configuration that needs to be added'''|}</li><li>'''Then restart the OPi OS Arch system'''</li></ol>

</li>

<li>After restarting, you can see the display of the LCD screen as shown below (default vertical screen)：</li~~></ol~~>

[[File:~~media/image505~~plus5-img505.png~~|162x242px~~]]</ol>

~~~~

=== Method of rotating display and touch direction ===

<li>First click the area in the upper right corner of the desktop

[[File:~~media/image492~~plus5-img492.png~~|193x123px~~]]</li>

<li>Then open the settings

[[File:~~media/image497~~plus5-img497.png~~|193x159px~~]]</li>

<li>Then choose '''Displays'''

[[File:~~media/image506~~plus5-img506.png~~|424x279px~~]]</li>

<li>Then select the direction you want to rotate in the '''Orientation''' of '''Displays'''

[[File:~~media/image507~~plus5-img507.png~~|426x282px~~]]</li>

<li>Then choose '''Apply'''

[[File:~~media/image508~~plus5-img508.png~~|425x282px~~]]</li>

<li>Then you can see that the screen has been rotated. At this time, you need to choose '''Keep Changes''' to determine the rotation

[[File:~~media/image509~~plus5-img509.png~~|259x130px~~]]</li>

<li>The display of the LCD screen after 90 degrees is shown below：

[[File:~~media/image510~~plus5-img510.png~~|359x229px~~]]</li>

<li>'''The touch function of the OPi OS Arch system LCD screen will rotate with the rotation of the display direction without other settings.'''</li></ol>

<li>OV13850 camera of 13 million MIPI interface

[[File:~~media/image23~~plus5-img23.png~~|215x121px~~]]</li>

<li>13 million MIPI interface OV13855 camera

[[File:~~media/image24~~plus5-img24.png~~|189x112px~~]]</li></ol>The rotary board used by OV13850 and OV13855 cameras is the same as the FPC cable, but the two cameras are different from the position on the rotary board. The FPC lines are shown in the figure below. Please note that the FPC line is directed. It is marked that the '''TO MB''' must be inserted into the camera interface of the development board. It is marked that the end of '''TO CAMERA''' needs to be inserted on the camera transfer ~~board。~~board</p~~></li></ol~~>

[[File:~~media/image436~~plus5-img436.png~~|370x77px~~]]

There are a total of 3 cameras on the camera to connect to the board, which can only be used at the same time, as shown in the figure below, of which：

<li>'''No. 1 interface is connected to the OV13850 camera'''</li>

<li>'''No. 2 interface connected OV13855 camera'''</li>

<li>No. 3 interface is not used, just ignore it.</li>~~</ol>~~ ~~[[File:media/image437.png|288x172px]]~~

[[File:plus5-img437.png]]

</ol>

Orange Pi 5 Plus development board has a total of 1 camera interface, which is shown below：

[[File:~~media/image438~~plus5-img438.png~~|367x85px~~]]

The method of the camera inserted on the development board interface is shown below：

[[File:~~media/image439~~plus5-img439.png~~|332x154px~~]]

After connecting the camera to the development board, we can use the following method to test the next camera：

<li>First add the following configuration in ~~>~~ '''/boot/extlinux/extlinux.conf'''{| class="wikitable" style="width:800px;" |-|

[orangepi@orangepi ~]$ '''sudo vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

FDT /dtbs/rockchip/rk3588-orangepi-5-plus.dtb

'''FDTOVERLAYS /dtbs/rockchip/overlay/rk3588-opi5plus-ov13850.dtbo'''|}The red font demonstrates the configuration of the camera interface '''ov13850'''. The other configurations are shown in the table below, and the corresponding DTBO configuration can be added behind '''FDTOVERLAYS'''。.</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''Camera'''

| style="text-align: left;"| '''/dtbs/rockchip/overlay/rk3588-opi5plus-ov13855.dtbo'''

|}

</ol>

<li>'''Then restart the OPi OS Arch system'''</li>

<li>Then open a terminal in the desktop system and run the script below

{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''test_camera.sh'''|}</li>

<li>Then you can see the preview of the camera

[[File:~~media/image511~~plus5-img511.png~~|576x324px|Screenshot from 2023-04-20 17-16-08~~]]

</div></li></ol>

== Set the Chinese environment and the method of installing the Chinese input method ==

<li>First click the area in the upper right corner of the desktop

[[File:~~media/image492~~plus5-img492.png~~|217x138px~~]]</li>

<li>Then open the settings

[[File:~~media/image512~~plus5-img512.png~~|259x196px~~]]</li>

<li>Then find the '''Region & Language''' option

[[File:~~media/image513~~plus5-img513.png~~|394x260px~~]]</li>

<li>Then choose '''Language'''

[[File:~~media/image514~~plus5-img514.png~~|401x264px~~]]</li>

<li>Then select Chinese

[[File:~~media/image515~~plus5-img515.png~~|443x290px~~]]</li>

<li>then click '''Select'''

[[File:~~media/image516~~plus5-img516.png~~|443x292px~~]]</li>

<li>Then click '''Logout...''' log in to the system, and then log in to the system

[[File:~~media/image517~~plus5-img517.png~~|395x260px~~]]</li>

<li>Then you can see that the desktop is displayed as Chinese

[[File:~~media/image518~~plus5-img518.png~~|498x280px|截图 2023-04-20 20-20-06~~]]

</div></li>

<li>Then install '''fcitx-im''' and '''fcitx-configtool'''

{| class="wikitable" style="width:800px;"

|-

|

[orangepi@orangepi ~]$ '''sudo pacman -S fcitx-im fcitx-configtool'''

:: There are 3 members in the group fcitx-im：

:: Software warehouse Community

:1) fcitx 2) fcitx-qt5 3) fcitx-qt6 Enter a selection (default = all selected): '''1'''|}</li>

<li>Then open the Fcitx configuration program

[[File:~~media/image519~~plus5-img519.png~~|395x223px~~]][[File:~~media/image520~~plus5-img520.png~~|396x223px~~]]</li>

<li>Then add '''Google Pinyin''' input method

[[File:~~media/image521~~plus5-img521.png~~|248x228px~~]][[File:~~media/image522~~plus5-img522.png~~|372x252px~~]]</li>

<li>Then we can open a terminal test in the Chinese input method. After opening the terminal, if the English input method is still in English, we can switch to the Chinese input method through the '''Ctrl+Space''' shortcut keys, and then you can enter Chinese

[[File:~~media/image523~~plus5-img523.png~~|459x258px|截图 2023-04-20 20-38-24~~]]

</div></li></ol>

== HDMI IN test method ==

<li>The position of the development board HDMI In interface is shown below：

[[File:~~media/image265~~plus5-img265.png~~|351x112px~~]]</li>

<li>First use the HDMI to HDMI line shown below to output the HDMI output of other devices to the HDMI In interface of the development board

[[File:~~media/image11~~plus5-img11.png~~|199x129px~~]]</li>

<li>The OPi OS Arch system HDMI in function is closed by default, and the opening method is shown below：

<li>First add the following configuration in ~~>~~ '''/boot/extlinux/extlinux.conf'''{| class="wikitable" style="width:800px;" |-|

[orangepi@orangepi ~]$ '''sudo vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

FDT /dtbs/rockchip/rk3588-orangepi-5-plus.dtb

'''FDTOVERLAYS /dtbs/rockchip/overlay/rk3588-hdmirx.dtbo #The configuration that needs to be added'''|}</li><li>'''Then restart the OPi OS Arch system'''</li></ol>

</li>

<li>After restarting into the system, open a terminal on the desktop, and then run the '''test_hdmiin.sh''' script

{| class="wikitable" style="width:800px;" |-|[orangepi@orangepi ~]$ '''test_hdmiin.sh'''|}</li>

<li>Then you can see the input screen of the HDMI in (the HDMI in in the figure below shows the screen of the OPI5 development board HDMI output, and it is playing a video at this time). '''test_hdmiin.sh''' script defaults to the audio entered by HDMI in to the HDMI_TX1, HDMI_TX2 and ES8388 (representing speakers or headphones) of the development board.

[[File:~~media/image524~~plus5-img524.png~~|576x326px~~]]</li><li>In addition to testing HDMI IN using '''test_hdmiin.sh''', we can also use '''Qt V4L2 test Utility''' to test HDMI in video ('''this method cannot test audio at present'''). The detailed steps are shown below：

<li>Enter the application list first

[[File:~~media/image525~~plus5-img525.png~~|356x200px~~]]</li>

<li>Then find '''Qt V4L2 test Utility''' and open it

[[File:~~media/image526~~plus5-img526.png~~|367x205px~~]]</li><li>Then make sure '''Qt V4L2 test Utility''' recognizes the HDMI In ~~>~~ device[[File:~~media/image527~~plus5-img527.png~~|508x185px~~]]</li><li>Then click the location shown in the figure below to see the ~~>~~ video entered by HDMI In[[File:~~media/image528~~plus5-img528.png~~|508x359px~~]]</li>

<li>The video window entered by HDMI In is shown below：

[[File:~~media/image529~~plus5-img529.png~~|572x322px|Screenshot from 2023-05-22 18-12-56~~]]

</div></li></ol>

== How to install wiringOP ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that Wiringop has been pre -installed in the OPI OS Arch image released by Orange PI. Unless Wiringop's code is updated, it is not necessary to re -download and compile and install it,just use it directly.'''

'''After entering the system, you can run the gpio readall command. If you can see the output below, it means that wiringOP is pre -installed and can be used normally'''</big>

[[File:~~media/image530~~plus5-img530.png~~|434x308px~~]]

<big>'''wiringOP is currently adapted to set the GPIO port input output, set the GPIO port output high and low level, and set the function of pulling and down resistance. It is impossible to use functions like hardware PWM.。'''</big>|}

<li>Download the code of wiringOP

{| class="wikitable" style="width:800px;"

|-

|

[orangepi@orangepi ~]$ '''sudo pacman -Syy git'''

[orangepi@orangepi ~]$ '''git clone https://github.com/orangepi-xunlong/wiringOP.git -b next'''

|} {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that Orange Pi 5 Plus needs to download the code of the wiringOP next branch, please don't miss the parameter of -b ~~next。~~next.''''''If you have a problem with the download code from github, you can download the source code compression package of wiringOp.tar.gz in the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html '''official tools of the Orange Pi 5 Plus data download page''']'''</big> [[File:~~media/image531~~plus5-img531.png|~~356x88px~~center]]|}</li>

<li>Compile and install wiringOP

{| class="wikitable" style="width:800px;"

|-

|

[orangepi@orangepi ~]$ '''sudo pacman -Syy make gcc'''

[orangepi@orangepi ~]$ '''cd wiringOP'''

[orangepi@orangepi wiringOP]$ '''sudo ./build clean'''

[orangepi@orangepi wiringOP]$ '''sudo ./build'''|}</li>

<li>Test the output of the GPIO Readall command as follows

[[File:~~media/image530~~plus5-img530.png~~|568x403px~~]]</li></ol>

== 40 PIN interface GPIO, I2C, UART, SPI, CAN and PWM test ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that if you need to set FDT Overlays to open multiple configurations at the same time, please use a space to write in a line like the red font configuration below.'''</big>

[orangepi@orangepi ~]$ '''sudo vim /boot/extlinux/extlinux.conf'''

FDT /dtbs/rockchip/rk3588s-orangepi-5.dtb

'''FDTOVERLAYS /dtbs/rockchip/overlay/rk3588-i2c1-m2.dtbo /dtbs/rockchip/overlay/rk3588-uart0-m2.dtbo'''|}

<li>A total of 28 GPIO ports can be used in the development board 40 PIN. Below is No. 7 pins -corresponding to GPIO1_D6 -corresponding WPI serial number 2 -as an example to demonstrate how to set the high and low level of the GPIO port

[[File:~~media/image532~~plus5-img532.png~~|576x147px~~]]</li>

<li>First set the GPIO port as the output mode. The third parameter needs to enter the serial number of the wpi corresponding to the pins

{| class="wikitable" style="width:800px;" |-|[orangepi@orangepi ~]$ '''gpio mode 2 out'''|}</li>

<li>Then set the GPIO port output low level. After setting, you can use the value of the voltage of the pins with a multimeter. If it is 0V, it means that the low -power flat is set

{| class="wikitable" style="width:800px;" |-|[orangepi@orangepi ~]$ '''gpio write 2 0'''|}</li>

<li>Then set the GPIO port output high level. After setting, you can use the value of the voltage of the pins with a multimeter. If it is 3.3V, it means that the high -power flat is set to be successful

{| class="wikitable" style="width:800px;" |-|[orangepi@orangepi ~]$ '''gpio write 2 1'''|}</li~~></ol~~>

<~~!-- --~~li># The setting method of other pins is similar. Just modify the serial number of the wpi serial number as the corresponding serial number.</li></ol>

=== 40 PIN GPIO Port -to -Plattering resistance setting method ===

<li>Below the No. 7 pin — corresponding to GPIO1_D6 -corresponding WPI serial number 2 -to demonstrate how to set up and down pull -down resistance of the GPIO port

[[File:~~media/image532~~plus5-img532.png~~|576x147px~~]]</li>

<li>First of all, you need to set the GPIO port as the input mode. The third parameter needs to enter the serial number of the wpi corresponding to the pins

{| class="wikitable" style="width:800px;" |-|[orangepi@orangepi ~]$ '''gpio mode 2 in'''|}</li>

<li>After the setting is set to input mode, execute the following command to set the GPIO port as the pull -down mode

{| class="wikitable" style="width:800px;" |-|[orangepi@orangepi ~]$ '''gpio mode 2 up'''|}</li>

<li>Then enter the following command to read the level of the GPIO port. If the level is 1, it means that the drawing mode is successful

{| class="wikitable" style="width:800px;" |-|[orangepi@orangepi ~]$ '''gpio read 2''''''1'''|}</li>

<li>Then execute the following command to set the GPIO port as the drop-down mode

{| class="wikitable" style="width:800px;" |-|[orangepi@orangepi ~]$ '''gpio mode 2 down'''|}</li><li>Then enter the command below to read the level of the GPIO port. If the level is 0, it means that the drop -down mode is set successfully{| class="wikitable" style="width:800px;" |-|[orangepi@orangepi ~]$ '''gpio read 2''''''0'''|}</li></ol>

=== 40 PIN SPI test ===

<li>As can be seen from the figure below, the SPI available for Orange Pi 5 Plus is SPI0 and SPI4

[[File:~~media/image304~~plus5-img304.png~~|575x137px~~]]</li><li>The corresponding pins corresponding to SPI0 and SPI4 are shown in the table below. SPI4_M1 and SPI4_M2 can only be used at the same time, and they cannot be used at the same time. They are the same SPI4, but they are just getting different pins. Please don't think that they are two different SPI ~~bus。~~bus.</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

| '''No. 26 pins'''

| '''No. 38 pins'''

| style="text-align: left;"| '''None'''

|}

</ol>

<li>In the Linux system, the SPI in 40 PIN is closed by default, and it needs to be opened manually to use. The detailed steps are shown below：

<li>First add the following configuration to the ~~>~~ '''/boot/extlinux/extlinux.conf'''{| class="wikitable" style="width:800px;" |-|

[orangepi@orangepi ~]$ '''sudo vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

FDT /dtbs/rockchip/rk3588-orangepi-5-plus.dtb

'''FDTOVERLAYS /dtbs/rockchip/overlay/rk3588-spi0-m2-cs0-cs1-spidev.dtbo'''|}The red font demonstrated the configuration of opening the '''SPI0-M2 and using the CS0 and CS1 pin'''. The other configurations are shown in the table below, and the corresponding dtbo configuration can be added to '''FDTOVERLAYS'''</li~~></ol></li></ol~~>

{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''SPI bus'''

| style="text-align: left;"| '''/dtbs/rockchip/overlay/rk3588-spi4-m2-cs0-spidev.dtbo'''

|}

</ol>

<li>~~Then~~ '''Then restart the OPi OS Arch system'''</li></ol></li></ol>

~~~~

<li>After the restart, enter the system first to check whether there is a '''spidevx.x''' device node in the Linux system. If it exists, it means that the SPI has been set and can be used directly

{| class="wikitable" style="width:800px;"

|-

|

[orangepi@orangepi ~]$ '''ls /dev/spidev*'''

/dev/spidev0.0 /dev/spidev0.1 /dev/spidev4.0 /dev/spidev4.1

|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The above is the result displayed after opening the spi0-m2-cs0-cs1-spidev and spi4-m1-cs0-cs1-spidev'''</big>|}</li>

<li>Then do not connect the SPI0 or SPI4 MOSI and MISO pins, and run the output result of the spidev_teest as shown below. You can see that the data of TX and RX are inconsistent

{| class="wikitable" style="width:800px;"

|-

|

[orangepi@orangepi ~]$ '''sudo spidev_test -v -D /dev/spidev4.0'''

'''Or'''

bits per word: 8

max speed: 500000 Hz (500 KHz)

TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF | ............................….|}</li>

<li>Then the output of spidev_test, which is then connected to SPI0 or SPI4 MOSI and MISO, is as follows. You can see that the sending and receiving data can be seen, indicating that the SPI loop test is normal

{| class="wikitable" style="width:800px;"

|-

|

[orangepi@orangepi ~]$ '''sudo spidev_test -v -D /dev/spidev4.0'''

'''Or'''

bits per word: 8

max speed: 500000 Hz (500 KHz)

TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.RX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.|}</li></ol>

=== 40 pin I2C test ===

<li>From the table below, the I2C available for Orange Pi 5 Plus is I2C2, I2C4, I2C5, and I2C8. There are four groups of I2C bus

[[File:~~media/image304~~plus5-img304.png~~|575x137px~~]]</li><li>The corresponding pins corresponding to the 4 group I2C bus are shown below. I2C2_M0 and I2C2_M4 can only be used at the same time, and they cannot be used at the same time. They are the same I2C2, but they only receive different pins. Please don't think that they are two different I2C2 bus</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''I2C bus'''

| style="text-align: left;"| '''No. 7 pin'''

|}

</ol>

<li>In the Linux system, the I2C bus in 40 PIN is closed by default, and it needs to be opened manually to use. The detailed steps are shown below：

<li>First add the following configuration in ~~>~~ '''/boot/extlinux/extlinux.conf'''.{| class="wikitable" style="width:800px;" |-|

[orangepi@orangepi ~]$ '''sudo vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

FDT /dtbs/rockchip/rk3588-orangepi-5-plus.dtb

'''FDTOVERLAYS /dtbs/rockchip/overlay/rk3588-i2c2-m0.dtbo'''|}The red font on the above demonstrates the configuration of the '''i2c2-m0'''. The other configurations are shown in the table below, and the corresponding dtbo configuration can be added behind '''FDTOVERLAYS'''</li~~></ol></li></ol~~>

{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''I2C bus'''

| style="text-align: left;"| '''/dtbs/rockchip/overlay/rk3588-i2c8-m2.dtbo'''

|}

</ol>

<li>Then restart the '''OPi OS Arch''' system</li></ol></li></ol>

<li>After starting the linux system, first confirm that there is a device node that needs to be used under the'''/dev'''{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''ls /dev/i2c-*'''|}</li>

<li>Then connect a I2C device on the I2C pin corresponding to the 40 PIN interface</li>

<li>Then use the '''i2cdetect -y''' command to detect the address of the connected i2c device, which means that the i2c can be used normally

{| class="wikitable" style="width:800px;"

|-

|

[orangepi@orangepi ~]$ '''sudo pacman -S i2c-tools''' #First of all, I2C tools

[orangepi@orangepi ~]$ '''sudo i2cdetect -y 2''' #i2c2 test command

[orangepi@orangepi ~]$ '''sudo i2cdetect -y 4''' #i2c4 test command

[orangepi@orangepi ~]$ '''sudo i2cdetect -y 5''' #i2c5 test command

[orangepi@orangepi ~]$ '''sudo i2cdetect -y 8''' #i2c8 test command|}</li></ol>

=== 40 Pin's UART test ===

<li>As can be seen from the table below, the UART available for Orange Pi 5 Plus is UART1, UART3, UART4, UART6, UART7, and UART8. There are 6 sets of UART bus

[[File:~~media/image304~~plus5-img304.png~~|575x137px~~]]</li>

<li>In the Linux system, the UART in 40 pin is closed by default, and it needs to be opened manually to use. The detailed steps are shown below：

<li>First add the following configuration to ~~>~~ the'''/boot/extlinux/extlinux.conf'''{| class="wikitable" style="width:800px;" |-|

[orangepi@orangepi ~]$ '''sudo vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

FDT /dtbs/rockchip/rk3588-orangepi-5-plus.dtb

'''FDTOVERLAYS /dtbs/rockchip/overlay/rk3588-uart1-m1.dtbo'''|}The red font demonstrates the configuration of the '''uart1-m1'''. The other configurations are shown in the table below, and the corresponding dtbo configuration can be added behind '''FDTOVERLAYS'''</li~~></ol></li></ol~~>

{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''UART bus'''

| style="text-align: left;"| '''/dtbs/rockchip/overlay/rk3588-uart8-m1.dtbo'''

|}

</ol>

<li>~~Then~~ '''Then restart the OPI OS Arch system'''</li></ol></li></ol>

<li>After entering the Linux system, first confirm whether there is a device node corresponding to UART under the'''/dev'''{| class="wikitable" style="width:800px;" |-|[orangepi@orangepi ~]$ '''ls /dev/ttyS*'''|}</li><li>Then start testing the UART interface, and first use the RX and TX pins of the UART interface to be tested by DuPont</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''UART bus'''

| style="text-align: left;"| '''No. 35 pin'''

|}

</ol>

<li>Use the '''gpio serial''' command to test the loop function of the serial port as shown below. If you can see the printed below, it means that the serial port communication is normal (TTYSX needs to be replaced with a node name corresponding to UART, please do not copy it)

{| class="wikitable" style="width:800px;"

|-

|

[orangepi@orangepi ~]$ '''sudo gpio serial /dev/ttySX'''

[sudo] password for orangepi: #Enter the password here

Out: 0: -> 0

Out: 1: -> 1

Out: 3: -> 3

Out: 4: -> 4

Out: 5: -> 5^C|}</li></ol>

=== PWM test method ===

<li>From the table below, the PWMs available for Orange Pi 5 Plus include PWM0, PWM1, PWM11, PWM12, PWM13, and PWM14 a total of six PWM

[[File:~~media/image304~~plus5-img304.png~~|575x137px~~]]</li><li>The corresponding pins of PWM in 40pin are shown below. PWM0_M0 and PWM0_M2, PWM1_M0 and PWM1_M2, PWM14_M0 and PWM14_M2 can only be used at the same time. They cannot be used at the same time. They are the same PWM, but they only get different pins. Please think that they are two different PWM bus</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''PWM bus'''

| style="text-align: left;"| '''No. 7 pin'''

|}

</ol>

<li>In the Linux system, the PWM in 40 PIN is closed by default, and it needs to be opened manually to use. The detailed steps are shown below：

<li>First add the following configuration to ~~>~~ the'''/boot/extlinux/extlinux.conf'''{| class="wikitable" style="width:800px;" |-|

[orangepi@orangepi ~]$ '''sudo vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

FDT /dtbs/rockchip/rk3588-orangepi-5-plus.dtb

'''FDTOVERLAYS /dtbs/rockchip/overlay/rk3588-pwm0-m0.dtbo'''|}The red font demonstrates the configuration of the '''pwm0-m0'''. The other configurations are shown in the table below, and the corresponding dtbo configuration can be added behind '''FDTOVERLAYS'''</li~~></ol></li></ol~~>

{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''PWM bus'''

| style="text-align: left;"| '''/dtbs/rockchip/overlay/rk3588-pwm14-m2.dtbo'''

|}

</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then '''restart the OPi OS Arch system'''</li></ol></li></ol>

<li>After opening a pwm,In the'''/sys/class/pwm'''/, there will be an additional pwmchipX (x is a specific number). For example, after opening PWM14,viewing'''/sys/class/pwm/'''down Pwmchipx will change from two to three.{| class="wikitable" style="width:800px;" |-|

[orangepi@orangepi ~]$ '''ls /sys/class/pwm/'''

pwmchip0 pwmchip1 pwmchip2|}</li>

<li>Which pwmchip corresponds to pwm14 above? Let's first check out the output of '''ls /sys/class/pwm/ -l''' command, as shown below：

[[File:~~media/image533~~plus5-img533.png~~|575x78px|1010iring_001~~]]

</div></li>

<li>Then from the table below, the base address of the PWM14 register is FEBF0020, and then look at the output of the '''ls /sys/class/pwm/ -l''' command. You can see that the link in PWMCHIP2 is connected to Febf0020.PWM, so the PWM14 corresponds to PWMCHIP2

[[File:~~media/image318~~plus5-img318.png~~|575x287px~~]]</li><li>Then use the following command to allow the PWM14 to output a 50Hz square wave (please switch to the root user first, and then execute the following command)</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

[root@orangepi ~]# '''echo 0 > /sys/class/pwm/pwmchip2/export'''

[root@orangepi ~]# '''echo 1 > /sys/class/pwm/pwmchip2/pwm0/enable'''

|}

[[File:~~media/image319~~plus5-img319.png~~|575x346px~~]]</ol>

<li>The other pwm testing methods in the pwm14 demonstration above are ~~similar。~~similar.</li></ol>

=== CAN's test method ===

<li>As can be seen from the table below, the Canal bus available for Orange Pi 5 Plus is CAN0 and CAN1

[[File:~~media/image320~~plus5-img320.png~~|574x137px~~]]</li>

<li>In the Linux system, the Can in 40 PIN is closed by default and needs to be opened manually to use. The detailed steps are shown below：

<li>First add the following configuration to ~~>~~ the'''/boot/extlinux/extlinux.conf'''{| class="wikitable" style="width:800px;" |-|

[orangepi@orangepi ~]$ '''sudo vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

FDT /dtbs/rockchip/rk3588-orangepi-5-plus.dtb

'''FDTOVERLAYS /dtbs/rockchip/overlay/rk3588-can0-m0.dtbo'''|}The red font demonstrates the configuration of the '''can0-m0'''. The other configurations are shown in the table below, and the corresponding dtbo configuration can be added to '''FDTOVERLAYS'''</li~~></ol></li></ol~~>

{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''CAN bus'''

| style="text-align: left;"| '''/dtbs/rockchip/overlay/rk3588-can1-m0.dtbo'''

|}

</ol>

<li>Then '''restart the OPI OS Arch system'''</li></ol></li></ol>

<li>After entering the Linux system, using the '''sudo ifconfig -a''' command If you can see the CAN device node, it means that the CAN has been opened correctly

{| class="wikitable" style="width:800px;"

|-

|

[orangepi@orangepi ~]$ '''sudo pacman -Syy net-tools'''

[orangepi@orangepi ~]$ '''sudo ifconfig -a'''

can0: flags=128<NOARP> mtu 16

::unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10 (UNSPEC)::RX packets 0 bytes 0 (0.0 B)::RX errors 0 dropped 0 overruns 0 frame 0::TX packets 0 bytes 0 (0.0 B)::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0::device interrupt 94

can1: flags=128<NOARP> mtu 16

::unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10 (UNSPEC)::RX packets 0 bytes 0 (0.0 B)::RX errors 0 dropped 0 overruns 0 frame 0::TX packets 0 bytes 0 (0.0 B)::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0::device interrupt 95|}</li><li>The pins corresponding to the Can0 and Can1 are</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

| style="text-align: left;"| '''Corresponding to No. 16 pin in 40pin'''

|}

</ol>

<li>Use Canalyst-II analyzer to test CAN receiving messages, please refer to the content of the one-section of [[Orange Pi 5 Plus#Use the CANalyst-II analyzer to test sending and receiving messages|'''the Canalyst-II analyzer to test receive and send message''']]</li></ol>

== Compilation system requirements ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''We can cross-compile the Linux image of the development board on the x64 computer, or compile the Linux image of the development board on the Ubuntu22.04 system of the development board, please choose one according to your preference.'''

'''If you use orangepi-build to compile the Linux image in the Ubuntu22.04 system of the development board, please do a good job of cooling (especially when the SSD starts). If the heat dissipation is not done well, it is prone to the error of file system runaway.'''</big>|}

<li>The Linux SDK, namely '''orangepi-build''', supports running on the '''Ubuntu 22.04''' of the development board (other systems have not been tested), so before downloading orangepi-build, please first ensure that the Ubuntu version installed on the development board is Ubuntu 22.04. The command to check the Ubuntu version installed on the development board is as follows. If the Release field does not display '''22.04''', it means that the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operations.{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''lsb_release -a'''

No LSB modules are available.

Distributor ID: Ubuntu

Description: Ubuntu 22.04.1 LTS

Release: '''22.04'''Codename: jammy|}</li><li>'''Since the source codes such as the kernel and U-boot are stored on GitHub, it is very important to ensure that the development board can download codes from GitHub normally when compiling the image.'''</li></ol>

=== Compile with x64 Ubuntu22.04 computer ===

<li>The Linux SDK, '''orangepi-build''', supports running on computers with '''Ubuntu 22.04''' installed, so before downloading orangepi-build, please make sure that the Ubuntu version installed on your computer is Ubuntu 22.04. The command to check the Ubuntu version installed on the computer is as follows. If the Release field does not display '''22.04''', it means that the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operations.{| class="wikitable" style="width:800px;" |-|

test@test:~$ '''lsb_release -a'''

No LSB modules are available.

Distributor ID: Ubuntu

Description: Ubuntu 22.04 LTS

Release: '''22.04'''Codename: jammy|}</li>

<li>If the computer is installed with Windows system and there is no computer with Ubuntu 22.04 installed, you can consider using '''VirtualBox''' or '''VMware''' to install an Ubuntu 22.04 virtual machine in the Windows system. But please be careful not to compile orangepi-build on the WSL virtual machine, because orangepi-build has not been tested in the WSL virtual machine, so it cannot be guaranteed that orangepi-build can be used normally in WSL.</li>

<li>The download address of the installation image of Ubuntu 22.04 '''amd64''' version is：{| class="wikitable" style="width:800px;" |-|~~[https://repo.huaweicloud.com/ubuntu-releases/21.04/ubuntu-21.04-desktop-amd64.iso~~ '''https://mirrors.tuna.tsinghua.edu.cn/ubuntu-releases/22.04/ubuntu-22.04-desktop-amd64.iso''']

or

'''https://repo.huaweicloud.com/ubuntu-releases/22.04/ubuntu-22.04.1-desktop-amd64.iso'''|}</li>

<li>After installing Ubuntu 22.04 on the computer or virtual machine, please set the software source of Ubuntu 22.04 to Tsinghua source, otherwise it is easy to make mistakes due to network reasons when installing the software later

<li>For the method of replacing Tsinghua source, please refer to the ~~>~~ instructions on this web page</li>~~</ol></li></ol>~~ ~~[https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/ '''https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/''']~~

{| class="wikitable" style="width:800px;"

|-

|

'''https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/'''

|}

</ol>

<li>Note that the Ubuntu version needs to be switched to 22.04

[[File:~~media/image534~~plus5-img534.png~~|576x241px~~]]</li><li>The content of the '''/etc/apt/sources.~~lis~~list'''t file that ~~>~~ needs to be replaced is{| class="wikitable" style="width:800px;" |-|

test@test:~$ '''sudo mv /etc/apt/sources.list /etc/apt/sources.list.bak'''

test@test:~$ '''sudo vim /etc/apt/sources.list'''

deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-security main restricted universe multiverse

# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-security main restricted universe multiverse

# Pre-release software source, not recommended to enable

# deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse

# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse|}</li><li>After the replacement, you need to update the package information ~~>~~ and make sure there is no error{| class="wikitable" style="width:800px;" |-|test@test:~$ '''sudo apt update'''|}</li><li>'''In addition, since the source codes such as the kernel and U-boot ~~>~~ are stored on GitHub, it is very important to ensure that the ~~>~~ computer can download codes from GitHub normally when compiling ~~>~~ the image.'''</li></ol></li></ol>

~~~~

== Get the source code of linux sdk ==

# The linux sdk actually refers to the code of orangepi-build. orangepi-build is modified based on the armbian build system. Using orangepi-build, multiple versions of linux images can be compiled. First download the code of orangepi-build, the command is as follows：

::{| class="wikitable" style="width:800px;" |-|

test@test:~$ '''sudo apt-get update'''

test@test:~$ '''git clone https://github.com/orangepi-xunlong/orangepi-build.git -b next'''

|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the Orange Pi 5 Plus development board needs to download the source code of the next branch of orangepi-build. The above git clone command needs to specify the branch of the orangepi-build source code as next.'''</big>

[[File:~~media/image535~~plus5-img535.png|~~576x298px~~700px|~~图片6~~center]]

</div>

|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Downloading the orangepi-build code through the git clone command does not require entering the user name and password of the github account (the same is true for downloading other codes in this manual), if the Ubuntu PC prompts the user to enter the github account after entering the git clone command The name and password are usually entered incorrectly in the address of the orangepi-build warehouse behind the git clone. Please check the spelling of the command carefully, instead of thinking that we forgot to provide the username and password of the github account.'''</big>|}

<li>The u-boot and linux kernel versions currently used by the development board are as follows</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''branch'''

| style="text-align: left;"| '''linux5.10'''

|}

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|

<big>'''The branch mentioned here is not the same thing as the branch of the orangepi-build source code, please do not confuse it. This branch is mainly used to distinguish different kernel source code versions.'''

'''The branch mentioned here is not the same thing as the branch of the orangepi-build source code, please do not confuse it. This branch is mainly used to distinguish different kernel source code versions.''' '''Currently, the linux5.10 bsp kernel provided by RK is defined as the legacy branch. If the mainline kernel is supported in the future, a current branch will be added.'''</big>|}</ol>

<li>orangepi-build will contain the following files and folders after downloading

<li>'''build.sh''': Compile the startup script</li>

<li>'''external''': Contains the configuration files needed to compile ~~>~~ the image, specific scripts, and the source code of some ~~>~~ programs, etc.</li>

<li>'''LICENSE''': GPL 2 license file</li>

<li>'''README.md''': orangepi-build documentation</li>

<li>'''scripts''': General script for compiling linux images

{| class="wikitable" style="width:800px;"

|-

|

test@test:~/orangepi-build$ '''ls'''

'''build.sh external LICENSE README.md scripts'''

|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If you downloaded the code of orangepi-build from github, after downloading, you may find that orangepi-build does not contain the source code of u-boot and linux kernel, nor does u-boot and linux kernel need to use cross-compilation tools Chain, this is normal, because these things are stored in other separate github warehouses or some servers (the addresses will be detailed below). orangepi-build will specify the address of u-boot, linux kernel and cross-compilation toolchain in the script and configuration file. When running orangepi-build, when it finds that there are no such things locally, it will automatically go to the corresponding place to download them.'''</big>|}</li></ol>

</li></ol>

=== Download the cross-compilation toolchain ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The cross-compilation toolchain will only be downloaded when the orangepi-build compilation image is used on an x64 computer. Compiling the linux image of the development board in the Ubuntu22.04 of the development board will not download the cross-compilation toolchain. At this time, orangepi-build/toolchains will be an empty folder.'''</big>|}

[[File:~~media/image536~~plus5-img536.png|~~575x278px|选区_396~~1500px]]

</div></li>

<li>The image URL of the cross-compilation toolchain in China is the open source software image site of Tsinghua University

~~[https~~{| class="wikitable" style="width:~~//mirrors.tuna.tsinghua.edu.cn/armbian~~800px;" |-~~releases/_toolchain/~~ |'''https://mirrors.tuna.tsinghua.edu.cn/armbian-releases/_toolchain/'''~~]~~|}</li>

<li>After '''toolchains''' is downloaded, it will contain multiple versions of cross-compilation toolchains, and the development board will only use two of them

{| class="wikitable" style="width:800px;"

|-

|

test@test:~/orangepi-build$ '''ls toolchains/'''

gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu

gcc-linaro-aarch64-none-elf-4.8-2013.11_linux

gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux

gcc-linaro-arm-none-eabi-4.8-2014.04_linux|}</li>

<li>The cross-compilation toolchain used to compile the linux kernel source code is

<li>linux5.10

{| class="wikitable" style="width:800px;" |-|'''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''|}</li></ol>

</li>

<li>The cross-compilation tool chain used to compile the u-boot source code is

<li>v2017.09

{| class="wikitable" style="width:800px;" |-|'''gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu'''|}</li></ol>

</li></ol>

=== orangepi-build complete directory structure description ===

<li>The orangepi-build repository does not contain the source code of the linux kernel, u-boot, and cross-compilation toolchain after downloading. The source code of the linux kernel and u-boot is stored in an independent git repository

<li>The git warehouse where the linux kernel source code is stored ~~>~~ is as follows：{| class="wikitable" style="width:800px;" |-|'''https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-5.10-rk3588'''|}</li><li>The git warehouse where the u-boot source code is stored is as ~~>~~ follows：{| class="wikitable" style="width:800px;" |-|'''https://github.com/orangepi-xunlong/u-boot-orangepi/tree/v2017.09-rk3588'''|}</li></ol>

</li>

<li>When orangepi-build runs for the first time, it will download the cross-compilation toolchain, u-boot and linux kernel source code. After successfully compiling a linux image, the files and folders that can be seen in orangepi-build are:

a.'''build.sh''': compile startup scriptb.'''external''': Contains the configuration files needed to compile the image, scripts with specific functions, and the source code of some programs. The rootfs compressed package cached during the image compilation process is also stored in externalc.'''kerne'''l: stores the source code of the linux kernel. The folder named '''orange-pi-5.10-rk3588''' stores the kernel source code of the legacy branch of the RK3588/RK3588S series development boards. Please do not manually modify the name of the folder of the kernel source code. If it is modified, the kernel source code will be re-downloaded when the compilation system is runningd.'''LICENSE''': GPL 2 license filee.'''README.md''': orangepi-build documentationf.'''output''': Store compiled deb packages such as u-boot and linux, compilation logs, and compiled images and other filesg.'''scripts''': general scripts for compiling linux imagesh. '''.toolchains''': store cross-compilation toolchaini.'''u-boot''': Store the source code of u-boot. The folder named '''v2017.09-rk3588''' stores the u-boot source code of the legacy branch of the RK3588/RK3588S series development boards. Please do not name the folder name of the u-boot source code Manual modification, if modified, the u-boot source code will be re-downloaded when the compilation system is runningj.'''userpatches''': Store configuration files needed to compile scripts{| class="wikitable" style="width:800px;" |-|

test@test:~/orangepi-build$ '''ls'''

'''build.sh      external      kernel      LICENSE      output      README.md      scripts      toolchains      u-boot      userpatches'''|}</li></ol>

== Compile u-boot ==

<li>Run the build.sh script, remember to add sudo permission

{| class="wikitable" style="width:800px;" |-|test@test:~/orangepi-build$ '''sudo ./build.sh'''|}</li>

<li>Select '''U-boot package''', then press Enter

[[File:~~media/image537~~plus5-img537.png~~|576x132px|选区_238~~]]

</div></li>

[[File:~~media/image538~~plus5-img538.png~~|576x289px|6~~]]

</div></li>

<li>u-boot source code version

{| class="wikitable" style="width:800px;" |-|[ o.k. ] Compiling u-boot [ '''v2017.09''' ]|}</li>

<li>The version of the cross-compilation toolchain

{| class="wikitable" style="width:800px;" |-|[ o.k. ] Compiler version [ '''aarch64-linux-gnu-gcc 7.4.1''' ]|}</li>

<li>Path to the generated u-boot deb package

{| class="wikitable" style="width:800px;" |-|[ o.k. ] Target directory [ '''orangepi-build/output/debs/u-boot''' ]|}</li>

<li>The package name of the generated u-boot deb package

{| class="wikitable" style="width:800px;" |-|[ o.k. ] File name [ '''linux-u-boot-legacy-orangepi5plus_1.0.0_arm64.deb''' ]|}</li>

<li>Compilation time

{| class="wikitable" style="width:800px;" |-|[ o.k. ] Runtime [ '''1 min''' ]|}</li><li>Repeat the command to compile u-boot, use the following command ~~>~~ to start compiling u-boot directly without selecting through ~~>~~ the graphical interface{| class="wikitable" style="width:800px;" |-|[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi5plus BRANCH=legacy BUILD_OPT=u-boot KERNEL_CONFIGURE=no''' ]|}</li></ol>

</li>

<li>View the u-boot deb package generated by compilation

{| class="wikitable" style="width:800px;"

|-

|

test@test:~/orangepi-build$ '''ls output/debs/u-boot/'''

linux-u-boot-legacy-orangepi5plus_1.0.0_arm64.deb|}</li>

<li>The files contained in the generated u-boot deb package are as follows

<li>Use the following command to decompress the deb package

{| class="wikitable" style="width:800px;"

|-

|

test@test:~/orangepi-build$ '''cd output/debs/u-boot'''

test@test:~/orangepi_build/output/debs/u-boot$ $ '''sudo dpkg -x''' \

'''linux-u-boot-legacy-orangepi5plus_1.0.0_arm64.deb . (Note that there is a "." at the end of the command)'''

test@test:~/orangepi_build/output/debs/u-boot$ '''ls'''

linux-u-boot-legacy-orangepi5plus_1.0.0_arm64.deb '''usr'''|}</li>

<li>The decompressed file is as follows

{| class="wikitable" style="width:800px;"

|-

|

test@test:~/orangepi-build/output/debs/u-boot$ '''tree usr'''

usr

└── lib

:├── linux-u-boot-legacy-orangepi5plus_1.0.0_arm64:│ ├── idbloader.img:│ ├── rkspi_loader.img:│ └── u-boot.itb:└── u-boot::├── LICENSE::├── orangepi_5_plus_defconfig::└── platform_install.sh 3 directories, 6 files|}</li></ol></li>

<li>When the orangepi-bulid compilation system compiles the u-boot source code, it will first synchronize the u-boot source code with the u-boot source code of the github server, so if you want to modify the u-boot source code, you first need to turn off the download and update function of the source code '''(need This function can only be turned off after u-boot has been fully compiled, otherwise it will prompt that the source code of u-boot cannot be found. If the source code compressed package is downloaded from Google Drive, there is no such problem because the source code of u-boot cached)''', otherwise the changes made will be restored, the method is as follows：

Set the IGNORE_UPDATES variable in userpatches/config-default.conf to "yes"

{| class="wikitable" style="width:800px;"

|-

|

test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''

IGNORE_UPDATES="'''yes'''"|}</li>

<li>When debugging u-boot code, you can use the following method to update u-boot in the linux image for testing

<li>Upload the compiled u-boot deb package to the linux system of ~~>~~ the development board{| class="wikitable" style="width:800px;" |-|

test@test:~/orangepi-build$ '''cd output/debs/u-boot'''

test@test:~/orangepi_build/output/debs/u-boot$ '''scp \'''

'''linux-u-boot-legacy-orangepi5plus_1.0.0_arm64.deb [mailto:root@192.168.1.xxx:/root root@192.168.1.xxx:/root]'''|}</li><li>Then log in to the development board and uninstall the deb ~~>~~ package of u-boot installed{| class="wikitable" style="width:800px;" |-|root@orangepi:~# '''apt purge -y linux-u-boot-orangepi5plus-legacy'''|}</li>

<li>Install the new u-boot deb package just uploaded

{| class="wikitable" style="width:800px;" |-|root@orangepi:~# '''dpkg -i''' '''linux-u-boot-legacy-orangepi5plus_1.0.0_arm64.deb'''|}</li>

<li>Then run the nand-sata-install script

{| class="wikitable" style="width:800px;" |-|root@orangepi:~# '''nand-sata-install'''|}</li>

<li>Then select '''5 Install/Update the bootloader on SD/eMM''' to update the u-boot in the TF card or '''7 Install/Update the bootloader on SPI Flash''' to update the u-boot in the SPI Flash

[[File:~~media/image539~~plus5-img539.png~~|317x154px~~]]</li>

<li>After pressing the Enter key, a Warning will pop up first

[[File:~~media/image540~~plus5-img540.png~~|314x170px~~]]</li><li>Press the Enter key again to start updating u-boot, and the ~~>~~ following information will be displayed after the update is ~~>~~ completed[[File:~~media/image541~~plus5-img541.png~~|223x125px~~]]</li><li>Then you can restart the development board to test whether the ~~>~~ modification of u-boot takes effect</li></ol>

</li>

<li>Other useful information

<li>u-boot 2017.09 source code, the defconfig configuration file ~~>~~ used by the development board is</li>~~<li>~~{| class="wikitable" style="width:800px;" |-|[https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/configs/orangepi_5_plus_defconfig '''orangepi-build/u-boot/v2017.09-rk3588/configs/orangepi_5_plus_defconfig''']|}<li>u-boot ~~>~~ 2017.09 source code, the dts file used by the development ~~>~~ board is</li>{| class="wikitable" style="width:800px;" |-|[https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/arch/arm/dts/rk3588-orangepi-5-plus.dts '''orangepi-build/u-boot/v2017.09-rk3588/arch/arm/dts/rk3588-orangepi-5-plus.dts''']|}</ol>

</li></ol>

~~[https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/arch/arm/dts/rk3588-orangepi-5-plus.dts '''orangepi-build/u-boot/v2017.09-rk3588/arch/arm/dts/rk3588-orangepi-5-plus.dts'''~~]

== Compile the linux kernel ==

<li>Run the build.sh script, remember to add sudo permission

{| class="wikitable" style="width:800px;" |-|test@test:~/orangepi-build$ '''sudo ./build.sh'''|}</li>

<li>Select '''Kernel package''', then press Enter

[[File:~~media/image542~~plus5-img542.png~~|575x116px|选区_240~~]]

</div></li>

[[File:~~media/image538~~plus5-img538.png~~|576x289px|6~~]]

</div></li>

<li>Then it will prompt whether to display the kernel configuration interface. If you do not need to modify the kernel configuration, select the first one. If you need to modify the kernel configuration, select the second one.

[[File:~~media/image543~~plus5-img543.png~~|576x87px~~]]</li>

<li>If you choose to display the kernel configuration menu (the second option) in step 4), the kernel configuration interface opened by '''make menuconfig''' will pop up. At this time, you can directly modify the kernel configuration, save and exit after modification. Yes, after exiting, the kernel source code will be compiled

[[File:~~media/image544~~plus5-img544.png~~|575x400px~~]]</li></ol>

<li>If you do not need to modify the configuration options of the ~~>~~ kernel, when running the build.sh script, pass in ~~>~~ '''KERNEL_CONFIGURE=no''' to temporarily block the pop-up ~~>~~ kernel configuration interface{| class="wikitable" style="width:800px;" |-|test@test:~/orangepi-build$ '''sudo ./build.sh KERNEL_CONFIGURE=no'''|}</li><li>You can also set '''KERNEL_CONFIGURE=no''' in the ~~>~~ '''orangepi-build/userpatches/config-default.conf''' ~~>~~ configuration file, which can permanently disable this function</li><li>If the following error is displayed when compiling the kernel, it is ~~>~~ because the terminal interface of the Ubuntu PC is too small to ~~>~~ display the '''make menuconfig''' interface. Please ~~>~~ maximize the terminal of the Ubuntu PC and run the build.sh script ~~>~~ again[[File:~~media/image545~~plus5-img545.png~~|574x234px~~]]</li></ol>

<li>The version of the linux kernel source code

{| class="wikitable" style="width:800px;" |-|[ o.k. ] Compiling current kernel [ '''5.10.110''' ]|}</li>

<li>The version of the cross-compilation toolchain used

{| class="wikitable" style="width:800px;" |-|[ o.k. ] Compiler version [ '''aarch64-none-linux-gnu-gcc 11.2.1''' ]</p~~></li><li>The configuration file used by the kernel by default and the > path where it is stored[ o.k. ] Using kernel config file [ '''config/kernel/linux-rockchip-rk3588-legacy.config''' ]</li><li>The path of the deb package related to the kernel generated by > compiling[ o.k. ] Target directory [ '''orangepi-build/output/debs/''' ]</li~~>~~<li>The package name of the compiled kernel image deb package[ o.k. ] File name [ '''linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb''' ]</li><li>The time used for compilation[ o.k. ] Runtime [ '''5 min''' ]</li>~~<li>Finally, the compilation command to repeatedly compile the > kernel selected last time will be displayed. Use the following > command to start compiling the kernel source code directly > without selecting through the graphical interface~~[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi5plus BRANCH=legacy BUILD_OPT=kernel KERNEL_CONFIGURE=no''' ]</li></ol>~~|}

</li>

<li>~~View the deb package related to~~ The configuration file used by the kernel ~~generated~~ by ~~compilation~~default and the path where it is stored~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>'''linux-dtb-legacy~~|-~~rockchip-rk3588_1.0.0_arm64.deb''' Contains > dtb files used by the kernel</li><li>'''linux-headers-legacy-rockchip-rk3588_1.0.0_arm64.deb''' Include > kernel headers</li>~~|~~<li>~~~~'''linux-image-legacy-rockchip-rk3588_1~~[ o.0k.~~0_arm64.deb''' Contains >~~ ] Using kernel ~~images and kernel modulestest@test:~/orangepi-build$~~ config file [ '''~~ls output~~config/~~debs/linux-*'''output/debs~~kernel/linux~~-dtb-legacy~~-rockchip-~~rk3588_1.0.0_arm64.deb output/debs/linux-image~~rk3588-legacy~~-rockchip-rk3588_1~~.~~0.0_arm64.deb~~config''' ]~~output/debs/linux-headers-legacy-rockchip-rk3588_1.0.0_arm64.deb</li></ol>~~|}

</li>

<li>The ~~files contained in~~ path of the deb package related to the kernel generated by compiling{| class="wikitable" style="width:800px;" |-|[ o.k. ] Target directory [ '''orangepi-build/output/debs/''' ]|}</li><li>The package name of the compiled kernel image deb package{| class="wikitable" style="width:800px;" |-|[ o.k. ] File name [ '''linux-image -legacy-rockchip-rk3588_1.0.0_arm64.deb''' ]|}</li><li>The time used for compilation{| class="wikitable" style="width:800px;" |-|[ o.k. ] Runtime [ '''5 min''' ]|}</li><li>Finally, the compilation command to repeatedly compile the kernel selected last time will be displayed. Use the following command to start compiling the kernel source code directly without selecting through the graphical interface{| class="wikitable" style="width:800px;" |-|[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi5plus BRANCH=legacy BUILD_OPT=kernel KERNEL_CONFIGURE=no''' ]|}</li></ol></li><li>View the deb package ~~are as follows~~related to the kernel generated by compilation

<li>~~Use the following command to decompress~~ '''linux-dtb-legacy-rockchip-rk3588_1.0.0_arm64.deb''' Contains dtb files used by the kernel</li><li>'''linux-headers-legacy-rockchip-rk3588_1.0.0_arm64.deb''' Include kernel headers</li><li>'''linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb ~~package~~''' Contains kernel images and kernel modules{| class="wikitable" style="width:800px;" |-|test@test:~/orangepi-build$ '''cd ls output/debs/linux-*'''output/debs/linux-dtb-legacy-rockchip-rk3588_1.0.0_arm64.deb output/debs/linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb</lip>output/debs/linux-headers-legacy-rockchip-rk3588_1.0.0_arm64.deb</olp>|}

</li></ol>

</li>

<li>The files contained in the generated linux-image deb package are as follows

<li>Use the following command to decompress the deb package</li>

{| class="wikitable" style="width:800px;"

|-

|

test@test:~/orangepi-build$ '''cd output/debs'''

test@test:~/orangepi_build/output/debs$ '''mkdir test'''

'''boot etc lib''' linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb '''usr'''

|}</ol>

<li>The decompressed file is as follows

{| class="wikitable" style="width:800px;"

|-

|

test@test:~/orangepi-build/output/debs/test$ '''tree -L 2'''

.

├── linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb

└── usr

:├── lib:└── share|}</li></ol></li></ol>

<li>The orangepi-bulid compilation system will first synchronize the linux kernel source code with the linux kernel source code of the github server when compiling the linux kernel source code, so if you want to modify the linux kernel source code, you first need to turn off the update function of the source code '''(you need to compile it once This function can only be turned off after the linux kernel source code, otherwise it will prompt that the source code of the linux kernel cannot be found. If the source code compressed package downloaded from Google Drive, there is no such problem, because the source code of linux has been cached)''', otherwise the The changes made will be reverted as follows:

Set the IGNORE_UPDATES variable in '''userpatches/config-default.conf''' to "yes"

{| class="wikitable" style="width:800px;"

|-

|

test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''

IGNORE_UPDATES="'''yes'''"|}</li>

<li>If the kernel has been modified, the following method can be used to update the kernel and kernel modules of the development board linux system

<li>Upload the deb package of the compiled linux kernel to the linux ~~>~~ system of the development board{| class="wikitable" style="width:800px;" |-|

test@test:~/orangepi-build$ '''cd output/debs'''

test@test:~/orangepi-build/output/debs$ '''scp \'''

'''linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb root@192.168.1.xxx:/root'''|}</li><li>Then log in to the development board and uninstall the deb ~~>~~ package of the installed linux kernel{| class="wikitable" style="width:800px;" |-|root@orangepi:~# '''apt purge -y linux-image-legacy-rockchip-rk3588'''|}</li>

<li>Install the deb package of the new linux kernel just uploaded

{| class="wikitable" style="width:800px;" |-|root@orangepi:~# '''dpkg -i linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb'''|}</li><li>Then restart the development board, and then check whether the ~~>~~ kernel-related modifications have taken effect{| class="wikitable" style="width:800px;" |-|root@orangepi:~# '''reboot'''|}</li></ol></li></ol>

<li>Other useful information

<li>The storage location of the kernel configuration file is as ~~>~~ follows, please do not go to the kernel source code to find ~~>~~ the kernel configuration file used by the development board</li>~~<li>~~{| class="wikitable" style="width:800px;" |-|[https://github.com/orangepi-xunlong/orangepi-build/blob/next/external/config/kernel/linux-rockchip-rk3588-legacy.config '''orangepi-build/external/config/kernel/linux-rockchip-rk3588-legacy.config''']|}<li>The ~~>~~ location of the dts file used by the development board is</li>{| class="wikitable" style="width:800px;" |-|[https://github.com/orangepi-xunlong/linux-orangepi/blob/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts '''orangepi-build/kernel/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts''']|}</ol>

</li></ol>

~~~~ [https://github.com/orangepi-xunlong/linux-orangepi/blob/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts '''orangepi-build/kernel/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts''']

== Compile rootfs ==

<li>Run the build.sh script, remember to add sudo permission

{| class="wikitable" style="width:800px;" |-|test@test:~/orangepi-build$ '''sudo ./build.sh'''|}</li><li>Select '''Rootfs and all deb packages''', then press Enter</li~~></ol~~>

[[File:~~media/image546~~plus5-img546.png~~|576x119px|选区_241~~]]

</div></ol>

<li>Then select the model of the development board

[[File:~~media/image538~~plus5-img538.png~~|576x289px|6~~]]

</div></li>

[[File:~~media/image547~~plus5-img547.png~~|575x180px|7~~]]

</div></li>

<li>Then select the type of image

<li>'''Image with console interface (server)''' Indicates the image of ~~>~~ the server version, which is relatively small</li><li>'''Image with desktop environment''' Indicates a mirror image with ~~>~~ a desktop, which is relatively large

[[File:~~media/image548~~plus5-img548.png~~|576x75px|选区_245~~]]

</div></li></ol>

[[File:~~media/image549~~plus5-img549.png~~|576x78px|选区_397~~]]

</div></li>

[[File:~~media/image550~~plus5-img550.png~~|575x99px|Selection_001~~]]

</div>

[[File:~~media/image551~~plus5-img551.png~~|576x74px~~]]

You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.

[[File:~~media/image552~~plus5-img552.png~~|575x264px~~]]</li>

<li>Then it will start to compile rootfs, and some of the information prompted during compilation are as follows

<li>The type of rootfs

{| class="wikitable" style="width:800px;" |-|[ o.k. ] local not found [ Creating new rootfs cache for '''jammy''']|}</li>

<li>The storage path of the compiled rootfs compressed package

{| class="wikitable" style="width:800px;" |-|[ o.k. ] Target directory [ '''external/cache/rootfs''' ]|}</li><li>The name of the rootfs compressed package generated by ~~>~~ compilation{| class="wikitable" style="width:800px;" |-|[ o.k. ] File name [ '''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' ]|}</li>

<li>The time used for compilation

{| class="wikitable" style="width:800px;" |-|[ o.k. ] Runtime [ '''13 min''' ]|}</li></ol>

</li>

<li>View the rootfs compressed package generated by compilation

<li>'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' is ~~>~~ the rootfs compressed package, the meaning of each field of ~~>~~ the name is<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) '''jammy''' indicates the type of linux distribution of rootfs</li><li>b) '''xfce''' means rootfs is the type of desktop version, if it ~~>~~ is '''cli''', it means the type of server version</li><li>c) '''arm64''' represents the architecture type of rootfs</li><li>d) '''f930ff6ebbac1a72108a2e100762b18f''' is the MD5 hash value generated by the package names of all software packages installed by rootfs. As long as the list of software packages installed by rootfs is not modified, this value will not change. The compilation script will use this MD5 hash value to generate Determine whether rootfs needs to be recompiled</li></ol>

</li>

<li>'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.list''' ~~>~~ lists the package names of all packages installed by rootfs{| class="wikitable" style="width:800px;" |-|

test@test:~/orangepi-build$ '''ls external/cache/rootfs/'''

'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4'''

jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.current

jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.list|}</li></ol>

</li>

<li>If the required rootfs already exists under '''external/cache/rootfs''', then compiling rootfs again will directly skip the compilation process and will not restart the compilation. When compiling the image, it will also go to '''external/cache/rootfs''' to find out whether it has If there is rootfs available in the cache, use it directly, which can save a lot of download and compilation time.</li></ol>

<li>Run the build.sh script, remember to add sudo permission

{| class="wikitable" style="width:800px;" |-|test@test:~/orangepi-build$ '''sudo ./build.sh'''|}</li><li>Select '''Full OS image for flashing''', then press Enter</li~~></ol~~>

[[File:~~media/image553~~plus5-img553.png~~|576x128px|选区_242~~]]

</div></ol>

<li>Then select the model of the development board

[[File:~~media/image538~~plus5-img538.png~~|576x289px|6~~]]

</div></li>

[[File:~~media/image547~~plus5-img547.png~~|575x180px|7~~]]

</div></li>

<li>Then select the type of image

<li>'''Image with console interface (server)''' Indicates the image of ~~>~~ the server version, which is relatively small</li><li>'''Image with desktop environment''' Indicates a image with a ~~>~~ desktop, which is relatively large

[[File:~~media/image548~~plus5-img548.png~~|576x75px|选区_245~~]]

</div></li></ol>

[[File:~~media/image549~~plus5-img549.png~~|569x77px|选区_397~~]]

</div></li>

[[File:~~media/image550~~plus5-img550.png~~|575x99px|Selection_001~~]]

</div>

[[File:~~media/image551~~plus5-img551.png~~|576x74px~~]]

You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.

[[File:~~media/image552~~plus5-img552.png~~|575x264px~~]]</li>

<li>Then it will start to compile the linux image. The general process of compilation is as follows

a. Initialize the compilation environment of Ubuntu PC and install the software packages required for the compilation process

<li>The storage path of the compiled image

{| class="wikitable" style="width:800px;" |-|[ o.k. ] Done building [ '''[ output/images/orangepi5plus_1.0.0_debian_bullseye_linux5.10.110_xfce_desktop/orangepi5plus_1.0.0_debian_bullseye_linux5.10.110_xfce_desktop.img]''' ]|}</li><li>Compilation time</li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-|'''[ o.k. ] Runtime [ 19 min ]'''|}</ol>

<li>Repeat the command to compile the image, and use the following ~~>~~ command to start compiling the image directly without selecting ~~>~~ through the graphical interface{| class="wikitable" style="width:800px;" |-|[ o.k. ] Repeat Build Options [ '''[ sudo ./build.sh BOARD=orangepi5plus BRANCH=legacy BUILD_OPT=image RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=yes]''' ]|}</li></ol></li></ol>

<li>First download the Linux kernel source code of the development board

{| class="wikitable" style="width:800px;" |-|'''orangepi@orangepi:~$ git clone --depth=1 -b orange-pi-5.10-rk3588 https://github.com/orangepi-xunlong/linux-orangepi'''~~</li></ol>~~|}

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If you have problems downloading the code from github, you can go to the official tool of the development board to download the compressed kernel source code package, then upload it to the linux system of the development board, and then decompress it.'''</big>

[[File:~~media/image554~~plus5-img554.png~~|223x86px~~]] [[File:~~media/image555~~plus5-img555.png~~|305x87px~~]]

<big>'''The command to decompress the compressed kernel source code package is:'''</big>

orangepi@orangepi:~$ '''tar zxf orange-pi-5.10-rk3588.tar.gz'''

orangepi@orangepi:~$ '''mv orange-pi-5.10-rk3588 linux-orangepi'''

<big>'''After decompression, please execute the following command to synchronize the source code with github to ensure that the source code is in the latest state:'''</big>

orangepi@orangepi:~$ '''cd linux-orangepi'''

orangepi@orangepi:~/linux-orangepi$ '''git pull'''

|}</li></ol>

<li>Then configure the default kernel configuration

{| class="wikitable" style="width:800px;"

|-

|

orangepi@orangepi:~$ '''cd linux-orangepi'''

orangepi@orangepi:~/linux-orangepi$ '''make rockchip_linux_defconfig'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <~~/li~~big>~~</ol>~~ '''The path of rockchip_linux_defconfig in the kernel source code is arch/arm64/configs/'''</big>|}</li></ol>

<li>Then compile the kernel source code

{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~/linux-orangepi$ '''make -j10'''|}</li>

<li>Then install the kernel module

{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~/linux-orangepi$ '''sudo make modules_install'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <~~/li></ol~~big> '''The installation path of the kernel module is：/lib/modules'''

'''After executing the sudo make modules_install command, you can see that there will be an additional kernel module folder under /lib/modules/:'''</big>

orangepi@orangepi5plus:~$ '''ls /lib/modules'''

'''5.10.110+''' 5.10.110-rockchip-rk3588|}</li></ol>

<li>Then install the kernel image and uInitrd

{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~/linux-orangepi$ '''sudo make install'''~~</li></ol>~~|}

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The installation path of the kernel image and uInitrd is：/boot/'''

'''After executing the sudo make install command, you can see that there will be one more kernel file under /boot/：'''</big>

orangepi@orangepi5plus:~/orange-pi-5.10-rk3588$ '''ls /boot/vmlinuz*'''

'''/boot/vmlinuz-5.10.110+''' /boot/vmlinuz-5.10.110-rockchip-rk3588

<big>'''The file /boot/Image is actually loaded when the system starts, and Image is a copy of the vmlinuz file'''</big>|}</li></ol>

<li>Then install the dtb file into '''/boot/dtb'''

{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~/linux-orangepi$ '''sudo make dtbs_install INSTALL_DTBS_PATH=/boot/dtb/'''|}</li>

<li>Then restart the Linux system and the newly compiled kernel will be loaded

{| class="wikitable" style="width:800px;"

|-

|

orangepi@orangepi:~$ '''uname -r'''

'''5.10.110+'''|}</li></ol>

== OpenWRT version ==

{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''OpenWRT version'''

== OpenWRT Adaptation ==

{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''Function'''

== The first start to expand rootfs ==

<li>When the OpenWRT system is started for the first time, the '''resize-rootfs.sh''' script will be executed to expand the rootfs, and it will automatically restart after the expansion is completed</li>

<li>After logging in to the system, you can use the '''df -h''' command to view the size of rootfs. If it is consistent with the actual capacity of the storage device (TF card, eMMC or NVME SSD), it means that the automatic expansion is running correctly

{| class="wikitable" style="width:800px;"

|-

|

root@OpenWrt:~# df -h

<pspan style="margin-right: 80px;">Filesystem Size Used Available Use% Mounted on</pspan> <pspan style="margin-right: 80px;color:#FF0000">'''/dev/root ''''''14.8G ''''''14.7G ''''''91.6M ''''''99% /'''</pspan> <pspan style="margin-right: 100px;">tmpfs 495.5M 6.1M 489.4M 1% /tmp</pspan> <pspan style="margin-right: 100px;">tmpfs 512.0K 0 512.0K 0% /dev</pspan> <pspan style="margin-right: 80px;">/dev/root 14.8G 14.7G 91.6M 99% /opt/docker</pspan> |}</li></ol>

== How to log in to the system ==

[[File:~~media/image556~~plus5-img556.png~~|576x290px|9D229F96-887B-4c6b-8E6E-681C9994DFA0~~]]

</div></li></ol>

=== Log in to the system via SSH ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Please note that in the OpenWrt system of Orange Pi 5 Plus, the network port near the typeC power interface is configured as a WAN port by default, and the network port near the HDMI port is configured as a LAN port by default.'''</big>|}

<li>The LAN port IP of the default board is set to '''192.168.2.1''', so the computer can obtain the IP address starting with '''192.168.2''' at this time</li>

<li>If the computer is installed with an Ubuntu system, you can execute the following command to log in to the system through SSH. By default, you can log in directly without a password

{| class="wikitable" style="width:800px;" |-|test@ubuntu:~$ '''ssh root@192.168.2.1'''|}</li>

<li>After successfully logging in to the system, the display is as shown in the figure below

[[File:~~media/image557~~plus5-img557.png~~|553x330px~~]]</li>

<li>If the computer is installed with Windows system, you can log in by referring to the method introduced in the section of SSH remote login to the development board under Windows.</li></ol>

=== Log in to the LuCI management interface ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Please note that the OpenWRT system configures the network port near the Type-C power port as a WAN port by default, and the network port near the HDMI port as a LAN port by default.'''</big>

[[File:~~media/image558~~plus5-img558-1.png|~~357x139px~~center]]|}

# First connect the LAN port of the board to the network port of the computer with a network cable, so that the network port of the computer can obtain an IP address through DHCP

::[[File:~~media/image559~~plus5-img559.png|~~552x135px|2023-04-21 14-41-42 的屏幕截图~~1500px]]

</div>

<li>'''The OpenWrt system does not set a password by default''', so just click the '''login''' button. After successful login, the interface is displayed as shown in the figure below[[File:~~media/image560~~plus5-img560.png~~|552x295px~~]]</li></ol>

=== Log in to the terminal through the LuCI management interface ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Please note that the OpenWRT system configures the network port near the Type-C power port as a WAN port by default, and the network port near the HDMI port as a LAN port by default.'''</big>

[[File:~~media/image558~~plus5-img558-1.png|~~357x139px~~center]]|}

# First connect the LAN port of the board to the network port of the computer with a network cable, so that the network port of the computer can obtain an IP address through DHCP

::[[File:~~media/image559~~plus5-img559.png|~~552x135px|2023-04-21 14-41-42 的屏幕截图~~1500px]]

</div>

<li>Select "'''Terminal'''" in the "'''Service'''" column of the navigation bar and click to enter</li>~~</ol>~~ ~~[[File:media/image561.png|576x227px]]~~

[[File:plus5-img561.png]]

</ol>

<li>At this time, the terminal interface is as shown in the figure below

[[File:~~media/image562~~plus5-img562.png~~|576x407px~~]]</li>

<li>Enter the user name root to log in

[[File:~~media/image563~~plus5-img563.png~~|575x334px~~]]</li></ol>

=== Use IP address + port number to log in to the terminal ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Please note that the OpenWRT system configures the network port near the Type-C power port as a WAN port by default, and the network port near the HDMI port as a LAN port by default.'''</big>

[[File:~~media/image558~~plus5-img558-1.png|~~357x139px~~center]]|}

# First connect the LAN port of the board to the network port of the computer with a network cable, so that the network port of the computer can obtain an IP address through DHCP

# The LAN port IP of the default board is set to '''192.168.2.1''', so the computer can obtain the IP address starting with '''192.168.2''' at this time

# Then enter ~~[http://192.168.2.1:7681/~~ '''192.168.2.1:7681'''] in the browser to log in to the OpenWRT terminal

::[[File:~~media/image564~~plus5-img564.png~~|553x296px|2023-04-21 14-54-26 的屏幕截图~~]]

</div>

== How to modify the IP address of the LAN port through the command line ==

# First use the following command to obtain the network configuration, the corresponding configuration file is '''/etc/config/network''', you can see that the value of '''network.lan.ipaddr''' is '''192.168.2.1'''

::{| class="wikitable" style="width:800px;"

|-

|

root@OpenWrt:~# '''uci show network'''

network.lan.proto='static'

'''network.lan.ipaddr='192.168.2.1''''

network.lan.netmask='255.255.255.0'

.…

|}

<li>Then enter the following command to modify the item '''network.lan.ipaddr'''</li~~></ol~~>{| class="wikitable" style="width:800px;" |-|

root@OpenWrt:~# '''uci set network.lan.ipaddr='192.168.100.1''''

|}</ol>

<li>Then enter the following command to complete the submission, that is, write to the configuration file</li~~></ol~~>{| class="wikitable" style="width:800px;" |-|

root@OpenWrt:~# '''uci commit'''

|}

If the IP address in red font is consistent with the one to be set, it means that the modification is successful

{| class="wikitable" style="width:800px;" |-|

root@OpenWrt:~# '''cat /etc/config/network'''

config interface 'lan'

::option device 'br-lan'

::option proto 'static'

::option netmask '255.255.255.0'

::option ip6assign '60'

::'''option ipaddr '192.168.100.1''''

...

|}</ol>

<li>Restart the network through ubus, please refer to the official document for the usage instructions of ubus</li~~></ol~~>{| class="wikitable" style="width:800px;" |-|

root@OpenWrt:~# '''ubus call network restart'''

|}</ol>

<li>At this point, enter the command and you can see that the IP of the LAN port is '''192.168.100.1'''

{| class="wikitable" style="width:800px;"

|-

|

root@OpenWrt:~# '''ifconfig br-lan'''

br-lan Link encap:Ethernet HWaddr FE:55:13:A3:EF:E7

::inet addr:'''192.168.100.1''' Bcast:192.168.100.255 Mask:255.255.255.0::inet6 addr: fd60:c4cd:1033::1/60 Scope:Global::UP BROADCAST MULTICAST MTU:1500 Metric:1::RX packets:0 errors:0 dropped:0 overruns:0 frame:0::TX packets:3 errors:0 dropped:0 overruns:0 carrier:0::collisions:0 txqueuelen:1000::RX bytes:0 (0.0 B) TX bytes:370 (370.0 B)|}</li></ol>

== How to modify the root password ==

# First enter passwd root on the command line of the system, and the following prompt message will appear. At this time, you can enter the password you want to set, and press the Enter key to confirm

::{| class="wikitable" style="width:800px;"

|-

|

root@OpenWrt:/# '''passwd root'''

'''Enter new UNIX password:'''

|}

<li>Then you will be prompted to re-enter the password. At this time, enter the password again to confirm and press Enter</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

'''Retype password:'''

|}</ol>

<li>The display of successful modification is as follows</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

'''passwd: password for root changed by root'''

|}</ol>

=== Modify through the LuCI management interface ===

<li>Find the "'''System'''" option in the navigation bar and click</li>

<li>In the column options below the system, select "'''Management ~~>~~ Rights'''" and click[[File:~~media/image565~~plus5-img565.png~~|552x256px~~]]</li>

<li>Select the "'''Router Password'''" option on the Tab page

[[File:~~media/image566~~plus5-img566.png~~|552x211px~~]]</li></ol>

</li>

<li>Modify and save the router password

a. Enter the password you set in the "'''Password'''" and "'''Confirm Password'''" dialog boxes (if you are not sure whether the password is entered correctly, you can click the "*" icon behind the dialog box to display the input characters)

b. Click "'''Save'''" to save the newly modified password

[[File:~~media/image567~~plus5-img567.png~~|553x230px~~]]</li>~~</ol>~~ ~~'''Note: In the "Password" and "Confirm Password" dialog boxes, the passwords entered twice must be consistent.'''~~

{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|

<big>'''Note: In the "Password" and "Confirm Password" dialog boxes, the passwords entered twice must be consistent.'''</big>

|}

</ol>

<li>After the password is changed successfully, a pop-up box will pop up saying "'''The system password has been changed successfully'''". At this time, a password is required to log in to OpenWRT

[[File:~~media/image568~~plus5-img568.png~~|563x222px~~]]</li></ol>

== USB interface test ==

# Execute the following command, if you can see the output of sdX, it means that the U disk is recognized successfully

::{| class="wikitable" style="width:800px;"|-|root@OpenWrt:~# '''cat /proc/partitions | grep "sd*"''' major minor #blocks name 8 0 15126528 '''sda''' |}

<li>Use the mount command to mount the U disk to '''/mnt''', and then you can view the files in the U disk</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

root@OpenWrt:~# '''mount /dev/sda /mnt/'''

test.txt

|}</ol>

<li>After mounting, you can view the capacity usage and mount point of the U disk through the df -h command</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

root@OpenWrt:~# '''df -h | grep "sd"'''

/dev/sda 14.4G 187.2M 14.2G 1% /mnt |}</ol>

~~~~

=== Mount the USB storage device on the LuCI management interface ===

<li>Then follow the login LuCI management interface to enter the LuCI management interface</li>

<li>Then in the LuCI management interface, click "System -> Mount Point" to enter the configuration interface of the mount point

[[File:~~media/image569~~plus5-img569.png~~|553x256px~~]]</li>

<li>Then follow the steps below to add a mount point

<li>Find "'''Mount Point'''" at the bottom of the mount point ~~>~~ '''global setting interface'''</li><li>Under the mount point, select the "Add" button and click Enter</li>~~</ol></li></ol>~~ ~~[[File:media/image570.png|553x163px]]~~

[[File:plus5-img570.png]]

</ol>

<li>Then the following pop-up interface will pop up

[[File:~~media/image571~~plus5-img571.png~~|553x288px~~]]</li>

<li>Then you can start to mount the storage device

a) Check "'''Enabled'''"

b) Select the actual connected device /dev/sda in the UUID column of general settings (choose according to your own device)

c) Select "'''Custom'''" in the mount point column, and fill in the target directory to be mounted. Here, take the '''/mnt''' directory as an example, and press '''Enter''' to confirm

d) Then click the "'''Save'''" button in the lower right corner</li>~~</ol>~~ ~~[[File:media/image572.png|553x214px]]~~

[[File:plus5-img572.png]]

</ol></ol>

<li>Then you will return to the mount point global settings page, click "'''Save and Apply'''" in the lower left corner of the page to make the mount point take effect</li>~~</ol>~~ ~~[[File:media/image573.png|535x325px]]~~

[[File:plus5-img573.png]]

</ol>

<li>After saving, you can see the "'''mounted file system'''", the storage device has been mounted successfully</li~~></ol~~>

[[File:~~media/image574~~plus5-img574.png~~|553x201px~~]]</ol>

~~~~

== How to use E-Key PCIe wireless network card ==

# The PCIe wireless network card models currently compatible with the OpenWRT image are as follows：

::{| class="wikitable" style="width:800px;"

|-

| '''serial number'''

| '''AX200'''

'''（PCIE+ USB接口)'''

| [[File:~~med%20ia/image230~~plus5-img230.png]]

| '''Debian'''

'''Ubuntu'''

'''OpenWRT'''

'''OPi OS Arch'''

| '''AX210'''

'''（PCIE+ USB接口)'''

| [[File:~~media/i%20mage231~~plus5-img231.png]]~~{wi dth=“1.06875in” h eight=“1.45in”}~~

| '''Debian'''

'''Ubuntu'''

'''OpenWRT'''

'''OPi OS Arch'''

|-

| '''3'''

| '''~~R TL8852BE~~RTL8852BE'''

'''（PCIE+ USB接口)'''

| [[File:~~med%20ia/image232~~plus5-img232.png]]

| '''Debian'''

'''Ubuntu'''

'''Not Supported OpenWRT'''

'''Android12'''

=== How to create WIFI hotspot ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that AX200 and AX210 currently only support hotspots in the 2.4G frequency band. In the 5G frequency band mode, there will be an error that the modified configuration of the wireless network card cannot be applied.'''</big>|}

<li>First insert the PCIe wireless network card into the M.2 E-KEY port of the development board, and then connect the Type-C power supply to power up the development board.

[[File:~~media/image575~~plus5-img575.png~~|347x149px~~]]</li>

<li>After the system startup is complete, click '''Network -> Wireless''' to enter the wireless WiFi configuration interface.

[[File:~~media/image576~~plus5-img576.png~~|553x155px~~]]</li>

<li>The default wireless configuration of the OpenWRT system is '''Master''' mode. Here, for the convenience of the next operation, we will remove the default wireless connection.

[[File:~~media/image577~~plus5-img577.png~~|517x162px~~]]</li>

<li>Then click '''Save''' in the lower right corner of the page to make the configuration take effect.

[[File:~~media/image578~~plus5-img578.png~~|553x179px~~]]</li>

<li>Then click the '''Add''' button on the right.

[[File:~~media/image579~~plus5-img579.png~~|553x138px~~]]</li>

<li>In the pop-up tab page '''Device Configuration''', we set the parameters as shown in the figure below.

[[File:~~media/image580~~plus5-img580.png~~|552x268px~~]]</li>

<li>Then in '''Interface Configuration -> General Settings''', set the mode to '''Access Point AP''', set the '''ESSID''' (wireless network name) to '''OpenWrt''', and specify the network as '''lan'''

[[File:~~media/image581~~plus5-img581.png~~|553x234px~~]]</li>

<li>Then in '''Interface Configuration -> Wireless Security''', select ''' WPA2-PSK''' as the encryption algorithm; set the key (wireless password) to '''password'''

[[File:~~media/image582~~plus5-img582.png~~|534x224px~~]]</li>

<li>After the above settings are completed, click '''Save''' in the lower right corner of the page, and then exit the tab page

[[File:~~media/image583~~plus5-img583.png~~|553x303px~~]]</li>

<li>Then click '''Save and Apply''' in the lower right corner of the page and wait for the configuration to be applied.

[[File:~~media/image584~~plus5-img584.png~~|553x216px~~]]</li>

<li>The display interface of successfully creating a hotspot is shown in the figure below

[[File:~~media/image585~~plus5-img585.png~~|515x266px~~]]</li>

<li>Then use the mobile phone or computer to search for the WiFi corresponding to the SSID to connect. After the connection is successful, as shown in the figure below

[[File:~~media/image586~~plus5-img586.png~~|247x156px~~]]</li></ol>

=== How to connect to WIFI hotspot ===

<li>Insert the PCIe wireless network card into the M.2 E-KEY port of the development board, and then connect the Type-C power supply to power the development board.

[[File:~~media/image575~~plus5-img575.png~~|347x149px~~]]</li>

<li>After the system startup is complete, click '''Network -> Wireless''' to enter the configuration wireless WiFi interface.

[[File:~~media/image576~~plus5-img576.png~~|553x155px~~]]</li>

<li>The default wireless configuration of the OpenWRT system is '''Master''' mode. Here, for the convenience of the next operation, we will remove the default wireless connection.

[[File:~~media/image577~~plus5-img577.png~~|520x162px~~]]</li>

<li>Then click '''Save''' in the lower right corner of the page to make the configuration take effect.

[[File:~~media/image578~~plus5-img578.png~~|520x179px~~]]</li>

<li>Then click the '''Scan''' button to scan the surrounding WiFi hotspots.

[[File:~~media/image587~~plus5-img587.png~~|541x225px~~]]</li>

<li>Then the following window will pop up to display the available WiFi hotspots. At this time, click the '''Join Network''' button on the right side of the WiFi hotspot you want to connect to connect to the WiFi hotspot.

[[File:~~media/image588~~plus5-img588.png~~|553x89px~~]]</li>

<li>Then an interface for connecting to a WiFi hotspot will pop up. We enter the password of the hotspot as shown in the figure below, and then click the '''Submit''' button.

[[File:~~media/image589~~plus5-img589.png~~|552x135px~~]]</li>

<li>Then the following interface will pop up, click the '''Save''' button in the lower right corner.

[[File:~~media/image590~~plus5-img590.png~~|553x237px~~]]</li>

<li>Finally, you will return to the main interface of wireless configuration, click '''Save and Apply''' and wait for the configuration to be applied.

[[File:~~media/image591~~plus5-img591.png~~|544x252px~~]]</li>

<li>After successfully connecting to the WiFi hotspot, the interface is displayed as shown in the figure below.

[[File:~~media/image592~~plus5-img592.png~~|547x232px~~]]</li></ol>

== Installing packages via the command line ==

# Update the list of available packages

::{| class="wikitable" style="width:800px;" |-|

root@OpenWrt:/# '''opkg update'''

|}

<li>Get the software list</li~~></ol~~>{| class="wikitable" style="width:800px;" |-|

root@OpenWrt:/# '''opkg list'''

|}</ol>

<li>Install the specified package</li~~></ol~~>{| class="wikitable" style="width:800px;" |-|

root@OpenWrt:/# '''opkg install <package name>'''

|}</ol>

<li>Check the installed software</li~~></ol~~>{| class="wikitable" style="width:800px;" |-|

root@OpenWrt:/# '''opkg list-installed'''

|}</ol>

<li>Uninstall the software</li~~></ol~~>{| class="wikitable" style="width:800px;" |-|

root@OpenWrt:/# '''opkg remove <package name>'''

|}

</ol>

~~~~

== OpenWRT management interface installation software package ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If you need to add new software packages, you can install them through the OpenWRT management interface.'''</big>|}

<li>First enter the package management page

a. Find the "'''System'''" option in the navigation bar and click to enter

b. In the vertical column options below the system, select "'''software package'''" and click to enter</li>~~</ol>~~ ~~[[File:media/image593.png|552x227px]]~~

[[File:plus5-img593.png]]

</ol>

<li>Then the main page of the software package will appear, as shown in the figure below, to obtain the list of available software

b. On the Tab page, click "'''Available'''" to view the currently available software packages

c. View the number of currently available packages

[[File:~~media/image594~~plus5-img594.png~~|553x232px~~]]</li></ol>

=== Example of installing software packages ===

<li>Take the installation package “"'''luci-app-acl'''” " as an example

<li>In the OpenWRT software package management interface, click the ~~>~~ filter dialog box and ~~enter”~~enter "'''luci-app-acl'''”"</li><li>In the list of software packages, you can see the version, ~~>~~ package size and description information of the ~~> “~~"'''luci-app-acl'''~~”software~~ " software package, and then click the ~~>~~ '''"Install"''' button[[File:~~media/image595~~plus5-img595.png~~|552x259px~~]]</li><li>Then the following pop-up window will appear, click ~~>~~ '''"Install"'''[[File:~~media/image596~~plus5-img596.png~~|348x430px~~]]</li>

<li>Then wait for the installation to complete

[[File:~~media/image597~~plus5-img597.png~~|576x96px~~]]</li>

<li>The display after the installation is complete is as follows

[[File:~~media/image598~~plus5-img598.png~~|506x289px~~]]</li></ol>

</li>

<li>Check whether the software package is installed successfully

a. In the OpenWRT software package management interface, click the filter dialog box and ~~enter”~~enter "'''luci-app-acl'''”"

b. Select and click '''"Available"''' on the Tab page

c. The “"'''luci-app-acl'''” " package will be displayed in the package list, and the update status will be '''"installed"'''[[File:~~media/image599~~plus5-img599.png~~|576x196px~~]]</li></ol>

=== Remove package example ===

<li>Take the removal of the ~~package”~~package "'''luci-app-acl'''” " as an example

<li>In the OpenWRT software package management interface, click the ~~>~~ filter dialog box and ~~enter”~~enter "'''luci-app-acl'''”"</li><li>Select '''"Installed"''' on the Tab page to display the list of ~~>~~ installed software packages</li><li>Click '''"Remove"''' on the right to remove the corresponding ~~>~~ software package[[File:~~media/image600~~plus5-img600.png~~|461x164px~~]]</li><li>Then the following pop-up window will be displayed, click ~~>~~ '''"Remove"'''[[File:~~media/image601~~plus5-img601.png~~|415x129px~~]]</li><li>After the removal is successful, the display interface is as ~~>~~ follows[[File:~~media/image602~~plus5-img602.png~~|414x88px~~]]</li></ol>

</li>

<li>Check whether the software package is removed successfully

a. In the OpenWRT software package management interface, click the filter dialog box and enter “"'''luci-app-acl'''”"

b. Select and click '''"Installed"''' on the Tab page

c. The “"'''luci-app-acl'''~~”package~~ " package will not be displayed in the package list, and the “"'''luci-app-acl'''” " package has been removed successfully[[File:~~media/image603~~plus5-img603.png~~|493x187px~~]]</li></ol>

== Using Samba Network Shares ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''There are mainly two software options for OpenWRT LAN file sharing, Samba and NFS. The compatibility of the Samba system is better, while the performance of NFS is superior. For users who need to use Windows devices, it is recommended to choose Samba.'''</big>|}

<li>Enter the management page of the Samba network share

<li>Find the '''"Service"''' option in the navigation bar and click ~~>~~ to enter</li><li>In the vertical column options below the service, select ~~>~~ '''"network sharing"''' and click to enter[[File:~~media/image604~~plus5-img604.png~~|553x205px~~]]</li></ol>

</li>

<li>Select the interface that the Samba service needs to monitor

<li>Select '''"General Settings"''' in the navigation bar of network ~~>~~ sharing and click to enter</li><li>The interface is specified according to actual needs. If you ~~>~~ want to access through the "wan port", set it to '''"wan"'''[[File:~~media/image605~~plus5-img605.png~~|500x222px~~]]</li></ol>

</li>

<li>Set the shared directory of the network share

[[File:~~media/image606~~plus5-img606.png~~|575x217px|4~~]]

</div></li>

<li>window10 starts network discovery and sharing

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note: To access Samba under the Windows 10 system, you need to confirm whether Windows 10 has enabled network discovery and sharing for sharing. If it is not enabled, perform the following settings first.'''</libig>|}</olli>

c) Select "Turn Windows features on or off" in Programs and Features

d) Check "SMB 1.0/CIFS file sharing support" in the pop-up box of enabling or disabling Windows functions

e) Click "OK" to configure the application</li>~~</ol>~~ ~~[[File:media/image607.png|575x316px]]~~

[[File:plus5-img607.png]]

</ol>

<li>Turn on the network discovery of Windows 10

d) Click | "Advanced Sharing Settings"

e) Turn on '''"Enable Network Discovery"''' and '''"Enable File and Printer Sharing"'''

f) Click "Save Changes" to save the Windows 10 network discovery configuration</li>~~</ol>~~ ~~[[File:media/image608.png|575x323px]]~~

[[File:plus5-img608.png]]

</ol></ol>

<li>After the setting is completed, enter \\OpenWrt in the address bar of the resource manager to access the shared directory, the user name is root, and the password is the password set by the development board host</li~~></ol~~>

[[File:~~media/image609~~plus5-img609.png~~|575x323px~~]]</ol>

~~~~

== Zerotier Instructions ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The OpenWRT system has pre-installed the zerotier client. After creating a virtual LAN on the zerotier official website, the client can directly join it through the Network ID. The specific operation is as shown below.'''</big>|}

<li>Log in to zerotier official website [https://my.zerotier.com/network '''https://my.zerotier.com/network'''], register and log in and click Network->Create A Network to create a virtual local area network

[[File:~~media/image610~~plus5-img610.png|~~575x118px~~1500px]][[File:~~media/image611~~plus5-img611.png|~~574x166px~~1500px]]</li>

<li>Click to enter the network console page, you can set the privacy option to public, so that the added network nodes do not need to be verified

[[File:~~media/image612~~plus5-img612.png~~|353x257px~~]]</li>

<li>The following automatically assigns the address Here you can choose the network segment yourself, here is 172.27.*.*

[[File:~~media/image613~~plus5-img613.png~~|374x233px~~]]</li><li>Enter the following command in the OpenWRT terminal to join the virtual LAN created above, '''where 8286ac0e47d53bb5 is the Network ID of the virtual LAN created above'''</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

root@OpenWrt:/# '''zerotier-one -d''' #Start the zerotier client

root@OpenWrt:/# '''zerotier-cli join 8286ac0e47d53bb5''' #join the network

|}</ol>

<li>Enter ifconfig in the terminal and you can see that there is already a new '''ztks54inm2''' device with an IP address of '''172.27.214.213'''</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

root@OpenWrt:/# '''ifconfig'''

'''ztks54inm2''' Link encap:Ethernet HWaddr F6:4E:DE:BF:D8:52

::inet addr:'''172.27.214.213''' Bcast:172.27.255.255 Mask:255.255.0.0

::inet6 addr: fe80::e82f:d0ff:fe5a:867e/64 Scope:Link

::UP BROADCAST RUNNING MULTICAST MTU:2800 Metric:1

::RX packets:18 errors:0 dropped:0 overruns:0 frame:0

::TX packets:48 errors:0 dropped:0 overruns:0 carrier:0

::collisions:0 txqueuelen:1000

RX bytes:1720 (1.6 KiB) TX byte81 (8.2 KiB)

|}</ol>

<li>Install the zerotier client on another device (Ubuntu18.04 is used as an example here), execute the following command to install, and restart the computer after the installation is complete</li~~></ol~~>{| class="wikitable" style="width:800px;" |-|

test@ubuntu:~$ '''curl -s https://install.zerotier.com | sudo bash'''

|}</ol>

<li>After restarting, join the virtual LAN according to the Network ID, and you can also see that the ip address assigned by zerotier has been obtained. At this time, the Ubuntu PC and OrangePi R1 Plus LTS are in the same LAN, and the two can communicate freely</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

test@ubuntu:~$ '''sudo zerotier-cli join 8286ac0e47d53bb5'''

'''ztks54inm2''': flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 2800

::inet '''172.27.47.214''' netmask 255.255.0.0 broadcast 172.27.255.255

::inet6 fe80::5ce1:85ff:fe2b:6918 prefixlen 64 scopeid 0x20<link>

::ether f6:fd:87:68:12:cf txqueuelen 1000 (ethernet)

::RX packets 0 bytes 0 (0.0 B)

::RX errors 0 dropped 0 overruns 0 frame 0

::TX packets 46 bytes 10006 (10.0 KB) ~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~

::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

|}

</ol>

<li>Test whether the two terminals can communicate</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

root@OpenWrt:/# '''ping 172.27.47.214 -I ztks54inm2'''

round-trip min/avg/max = 1.136/1.195/1.235 ms

|}</ol>

<li>other common commands of zerotier</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

root@OpenWrt:/# '''zerotier-one -d''' #Start the zerotier client

OPENWRT_RELEASE="OpenWrt 22.03.4 r20123-38ccc47687"

|}</ol>

# First execute the following command to download the openwrt-22.03 branch code

::{| class="wikitable" style="width:800px;"

|-

|

test@test:~$ '''sudo apt update'''

test@test:~$ '''git clone https://github.com/orangepi-xunlong/openwrt.git -b openwrt-22.03'''

|}

<li>After the OpenWRT code is downloaded, the following files and folders will be included</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

test@test:~/openwrt$ '''ls'''

BSDmakefile     Config.in     include     Makefile     README.md     scripts     toolchain

Config     feeds.conf.default     LICENSE     package     rules.mk     target     tools|}</ol>

~~~~

== Compile OpenWRT source code ==

<li>First install the following dependent packages (currently only tested on Ubuntu 20.04 to compile the following dependent packages, if you compile on other versions of the system, please install the dependent packages by yourself according to the error message)

<li>Method 1: The command to install dependent packages using a > script is as follows:</li~~></ol></li></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

test@test:~/openwrt$ '''sudo ./install_dep.sh'''

|}

</ol>

<li>Method 2: Install the dependency package directly using the following command</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

test@test:~/openwrt$ '''sudo apt update'''

'''vim wget xmlto xxd zlib1g-dev'''

|}</ol></li></ol>

<li>Then execute '''./scripts/feeds update -a''' and '''./scripts/feeds install -a''' to download dependent packages</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

test@test:~/openwrt$ '''./scripts/feeds update -a'''

test@test:~/openwrt$ '''./scripts/feeds install -a'''

|}</ol>

<li>Then choose to use the configuration file of OrangePi 5 Plus

<li>Compile the image that supports TF card, eMMC, and NVMe startup, > and select the following configuration</li~~></ol~~>~~</li></ol>~~{| class="wikitable" style="width:800px;" |-|

test@test:~/openwrt$ '''cp configs/orangepi-5-plus-rk3588_defconfig .config'''

|}</ol>

<li>Compile the image that supports SPIFlash startup, and select the > following configuration</li~~></ol~~>{| class="wikitable" style="width:800px;" |-|

test@test:~/openwrt$ '''cp configs/orangepi-5-plus-rk3588-spi_defconfig .config'''

|}</ol></li></ol>

<li>Then execute the following command to make the configuration take effect</li~~></ol~~>{| class="wikitable" style="width:800px;" |-|

test@test:~/openwrt$ '''make defconfig'''

|}</ol>

<li>Execute the following command to start compiling the openwrt source code</li~~></ol~~>{| class="wikitable" style="width:800px;" |-|

test@test:~/openwrt$ '''make V=s'''

|}</ol>

<li>After the compilation is complete, the path where the image is generated is:</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

test@test:~/openwrt$ '''tree -L 1 bin/targets/rockchip/armv8/'''

└── version.buildinfo

1 directory, 9 files

|}</ol>

== Supported Android versions ==

{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''Android version'''

== Android function adaptation ==

{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''Function'''

|-

| style="text-align: left;"| '''AX200-WIFI'''

| style="text-align: left;"| '''NO'''| style="text-align: left;"| '''NO'''

|-

| style="text-align: left;"| '''AX200-BT'''

| style="text-align: left;"| '''NO'''| style="text-align: left;"| '''NO'''

|-

| style="text-align: left;"| '''AX210-WIFI'''

| style="text-align: left;"| '''NO'''| style="text-align: left;"| '''NO'''

|-

| style="text-align: left;"| '''AX210-BT'''

| style="text-align: left;"| '''NO'''| style="text-align: left;"| '''NO'''

|-

| style="text-align: left;"| '''RTL8852BE-WIFI'''

|-

| style="text-align: left;"| '''HDMI CEC function'''

| style="text-align: left;"| '''NO'''

| style="text-align: left;"| '''OK'''

|}

== How to use the USB wireless network card ==

# Currently, the USB wireless network card models compatible with the Android image are as follows：

::{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''Chip model'''

<li>The pictures of the above two USB wireless network cards are as follows：

<li>The picture of the RTL8723BU USB wireless network card module is ~~>~~ as follows：

[[File:~~media/image614~~plus5-img614.png~~|175x103px|C89CEA9A-B322-42d2-B476-2392A50E6FC4~~]]

</div></li>

<li>The picture of the RTL8811CU USB wireless network card module is ~~>~~ as follows：[[File:~~media/image615~~plus5-img615.png~~|124x107px~~]]</li></ol>

</li>

<li>The test methods of the above two types of USB wireless network cards are the same. First, the USB network card needs to be inserted into the USB interface of the development board.</li>

== M.2 How to use E-Key PCIe WIFI6+Bluetooth module ==

# The PCIe wireless network card models currently compatible with Android 12 are as follows：

::{| class="wikitable" style="width:800px;"

|-

| '''serial number'''

'''(PCIE+USB interface)'''

| [[File:~~media~~plus5-img616.png]]|} ::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Pay attention to RTL8852BE, please do not buy the module shown in the figure below, there will be problems after testing.'''</~~image6%2016~~big> [[File:plus5-img616-2.png|center]]

|}

<li>First insert the PCIe wireless network card into the M.2 E-KEY interface of the development board and fix it

[[File:~~media/image617~~plus5-img617.png~~|263x178px~~]]</li>

<li>Then connect the power supply of the Type-C interface to the development board, and power on</li>

<li>After the system starts, please refer to the section of WIFI connection test method for WIFI connection and test method</li>

== WIFI connection test method ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''First of all, please note that there is no WIFI module on the Orange Pi 5 Plus development board, and an external PCIe network card or USB network card is required to use the WIFI function.'''

'''For instructions on using the external PCIe network card, please refer to the section on how to use the M.2 E-Key PCIe WIFI6+Bluetooth module.'''

'''For instructions on using the external USB network card, please refer to the section on how to use the USB wireless network card.'''</big>|}

# First click to enter the '''Setting'''

::[[File:~~media/image618~~plus5-img618.png~~|553x182px~~]]

<li>Then select '''Network & internet'''</li>~~</ol>~~ ~~[[File:media/image619.png|553x154px]]~~

[[File:plus5-img619.png]]

</ol>

<li>Then select '''Internet'''</li>~~</ol>~~ ~~[[File:media/image620.png|553x103px]]~~

[[File:plus5-img620.png]]

</ol>

<li>Then turn on the '''Wi-Fi''' switch</li>~~</ol>~~ ~~[[File:media/image621.png|553x65px]]~~

[[File:plus5-img621.png]]

</ol>

<li>After turning on '''Wi-Fi''', if everything is normal, you can scan to nearby Wi-Fi hotspots

[[File:~~media/image622~~plus5-img622.png~~|549x172px~~]]</li>

<li>Then select the Wi-Fi you want to connect to, and the password input interface shown in the figure below will pop up

[[File:~~media/image623~~plus5-img623.png~~|553x237px~~]]</li>

<li>Then use the keyboard to enter the password corresponding to Wi-Fi, and then use the mouse to click the Enter button in the virtual keyboard to start connecting to Wi-Fi

[[File:~~media/image624~~plus5-img624.png~~|553x232px~~]]</li>

<li>The display after successful Wi-Fi connection is shown in the figure below：

[[File:~~media/image625~~plus5-img625.png~~|553x93px~~]]</li></ol>

== How to use Wi-Fi hotspot ==

<li>First, please make sure that the Ethernet port is connected to the network cable and can access the Internet normally</li>

<li>Then select '''Settings'''

[[File:~~media/image618~~plus5-img618.png~~|553x182px~~]]</li>

<li>Then select '''Network & internet'''

[[File:~~media/image619~~plus5-img619.png~~|553x154px~~]]</li>

<li>Then select '''Hotspot & tethering'''

[[File:~~media/image626~~plus5-img626.png~~|575x195px~~]]</li>

<li>Then select '''Wi-Fi hotspot'''

[[File:~~media/image627~~plus5-img627.png~~|575x96px~~]]</li>

<li>Then turn on the '''Wi-Fi hotspot''', you can also see the name and password of the generated hotspot in the figure below, remember them, and use them when connecting to the hotspot '''(if you need to modify the name and password of the hotspot, you need to turn off the Wi-Fi first -Fi hotspot before modification)'''

[[File:~~media/image628~~plus5-img628.png~~|575x187px~~]]</li><li>At this point, you can take out your mobile phone. If everything is normal, you can find the WIFI hotspot with the same name ('''here AndroidAP_6953''') displayed under the '''Hotspot name''' in the above picture in the WI-FI list searched by the mobile phone. Then you can click '''AndroidAP_6953''' to connect to the hotspot, and the password can be seen under the '''Hotspot password''' in the above picture</li>~~</ol>~~ ~~[[File:media/image629.png|342x260px]]~~

[[File:plus5-img629.png]]

</ol>

<li>After the connection is successful, it will be displayed as shown in the figure below (the interface of different mobile phones will be different, the specific interface is subject to the display of your mobile phone). At this point, you can open a webpage on your mobile phone to see if you can access the Internet. If you can open the webpage normally, it means that the '''WI-FI Hotspot''' of the development board can be used normally.</li~~></ol~~>

[[File:~~media/image630~~plus5-img630.png~~|347x175px~~]]</ol>

~~~~

== Bluetooth test method ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Please note that there is no Bluetooth module on the Orange Pi 5 Plus development board, and an external PCIe network card with Bluetooth or a USB network card with Bluetooth is required to use the Bluetooth function.'''

'''For instructions on using the external PCIe network card, please refer to the section on how to use the M.2 E-Key PCIe WIFI6+Bluetooth module.'''

'''For instructions on using the external USB network card, please refer to the section on how to use the USB wireless network card.'''</big>|}

<li>First click to enter the '''Setting'''

[[File:~~media/image618~~plus5-img618.png~~|553x182px~~]]</li>

<li>Then select '''Connected devices'''

[[File:~~media/image631~~plus5-img631.png~~|575x146px~~]]</li>

<li>Then click '''Pair new device''' to turn on Bluetooth and start scanning the surrounding Bluetooth devices

[[File:~~media/image632~~plus5-img632.png~~|575x144px~~]]</li>

<li>The searched Bluetooth devices will be displayed under '''Available devices'''

[[File:~~media/image633~~plus5-img633.png~~|575x200px~~]]</li>

<li>Then click the Bluetooth device you want to connect to start pairing. When the following interface pops up, please use the mouse to select the '''Pair''' option

[[File:~~media/image634~~plus5-img634.png~~|575x155px~~]]</li>

<li>The test here is the configuration process of the development board and the Bluetooth of the Android mobile phone. At this time, the following confirmation interface will pop up on the mobile phone. After clicking the pairing button on the mobile phone, the pairing process will start

[[File:~~media/image635~~plus5-img635.png~~|308x232px~~]]</li>

<li>After the pairing is completed, you can see the paired Bluetooth device as shown in the figure below

[[File:~~media/image636~~plus5-img636.png~~|575x170px~~]]</li>

<li>At this time, you can use the Bluetooth of your mobile phone to send a picture to the development board. After sending, you can see the following confirmation interface in the Android system of the development board, and then click '''Accept''' to start receiving the picture sent by the mobile phone.

[[File:~~media/image637~~plus5-img637.png~~|575x250px~~]]</li>

<li>You can open the '''Download''' directory in the file manager to view the pictures received by the Android system Bluetooth of the development board

[[File:~~media/image638~~plus5-img638.png~~|575x86px~~]]</li></ol>

== Test method of HDMI In ==

<li>The location of the HDMI In interface on the development board is as follows：

[[File:~~media/image265~~plus5-img265.png~~|351x112px~~]]</li>

<li>Then use the HDMI to HDMI cable shown in the figure below to connect the HDMI output of other devices to the HDMI In interface of the development board

[[File:~~media/image11~~plus5-img11.png~~|199x129px~~]]</li>

<li>Make sure that the HDMI output of the device connected to the HDMI In interface is normal, and then open the HDMI In test APP

[[File:~~media/image639~~plus5-img639.png~~|532x167px~~]]</li>

<li>Then you can see the video input of HDMI In, and the audio input of HDMI In will also be output from the HDMI TX interface or headphone interface of the development board. The figure below shows the desktop of the Linux system of the OPi5 development board input through HDMI In.

[[File:~~media/image640~~plus5-img640.png~~|533x301px~~]]</li></ol>

== How to use 10.9.10.1 inch MIPI screen ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Please make sure that the Android image used is the image of the following two versions：'''

'''OrangePi5Plus_RK3588_Android12_lcd_v1.x.x.img'''

'''OrangePi5Plus_RK3588_Android12_spi-nvme_lcd_v1.x.x.img'''</big>|}

<li>The screen needs to be assembled first, please refer to the assembly method of the 10.1-inch MIPI screen</li>

<li>The interface position of the LCD on the development board is shown in the figure below：

[[File:~~media/image641~~plus5-img641.png~~|317x80px~~]]{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the touch interface below is not for the LCD MIPI screen. It is currently a spare interface and cannot be used.'''</big> [[File:~~media/image425~~plus5-img425.png|~~334x70px~~center]]|}</li>

<li>Connect the assembled screen to the LCD interface, connect the Type-C power supply to the board, and power on. After the system starts, you can see the screen display as shown in the figure below

[[File:~~media/image642~~plus5-img642.png~~|517x345px~~]]</li></ol>

== OV13850 and OV13855 MIPI camera test method ==

<li>OV13850 camera with 13 million MIPI interface

[[File:~~media/image23~~plus5-img23.png~~|268x151px~~]]</li>

<li>OV13855 camera with 13 million MIPI interface

[[File:~~media/image24~~plus5-img24.png~~|253x150px~~]]</li></ol>The adapter boards and FPC cables used by the OV13850 and OV13855 cameras are the same, but the positions of the two cameras connected to the adapter boards are different. The FPC cable is shown in the figure below. Please note that the FPC cable has a direction. The end marked '''TO MB''' needs to be inserted into the camera interface of the development board, and the end marked '''TO CAMERA''' needs to be inserted into the camera adapter board.</p~~></li></ol~~>

[[File:~~media/image436~~plus5-img436.png~~|475x99px~~]]

There are a total of 3 camera interfaces on the camera adapter board, and only one can be used at a time, as shown in the figure below, of which:

<li>'''No.1 port is connected to OV13850 camera'''</li>

<li>'''No.2 interface is connected to OV13855 camera'''</li>

<li>No. 3 3 interface is not used, just ignore it</li~~></ol~~>

[[File:~~media/image643~~plus5-img643.png~~|333x199px|图片3~~]]

</div></ol>

The location of the camera interface on the Orange Pi 5 Plus development board is shown in the figure below:

[[File:~~media/image644~~plus5-img644.png~~|388x65px~~]]

The method of inserting the camera into the CAM interface of the development board is as follows:

[[File:~~media/image439~~plus5-img439.png~~|285x132px~~]]

After connecting the camera to the development board, we can use the following method to test the camera：

<li>Open the camera APP on the desktop

[[File:~~media/image645~~plus5-img645.png~~|491x279px~~]]</li>

<li>Then you can see the preview screen of the camera

[[File:~~media/image646~~plus5-img646.png~~|379x213px|Screenshot_20230317-073757~~]]

</div>

Press and hold the mouse in the area shown in the red box in the picture below of the camera APP and then drag to the right to call up the switching interface for taking pictures and recording

[[File:~~media/image647~~plus5-img647.png~~|391x222px~~]]

The switching interface of taking pictures and recording is as follows, click Video to switch to '''video''' recording mode

[[File:~~media/image648~~plus5-img648.png~~|386x217px|Screenshot_20230317-074419~~]]

</div>

Click the position shown in the figure below to enter the camera setting interface

[[File:~~media/image649~~plus5-img649.png~~|390x221px~~]]

The setting interface of the camera is as follows：

[[File:~~media/image650~~plus5-img650.png~~|429x241px|Screenshot_20230317-075325~~]]

</div></li></ol>

== ~~26pin~~ 40pin interface GPIO, UART, SPI and PWM test ==

<li>First click on the wiringOP icon to open the wiringOP APP

[[File:~~media/image651~~plus5-img651.png~~|552x183px~~]]</li>

<li>The main interface of wiringOP APP is displayed as shown in the figure below, and then click the '''GPIO_TEST''' button to open the GPIO test interface

[[File:~~media/image652~~plus5-img652.png~~|553x131px~~]]</li>

<li>The GPIO test interface is shown in the figure below. The two rows of '''CheckBox''' buttons on the left are in one-to-one correspondence with the 26pin pins. When the '''CheckBox''' button is checked, the corresponding GPIO pin will be set to '''OUT''' mode, and the pin level will be set to high level; when the checkbox is unchecked, the GPIO pin level will be set to low level; When the '''GPIO READALL''' button is pressed, information such as the wPi number, GPIO mode, and pin level can be obtained.

[[File:~~media/image653~~plus5-img653.png~~|553x288px~~]]</li>

<li>Then click the '''GPIO READALL''' button, the output information is as shown in the figure below：

[[File:~~media/image654~~plus5-img654.png~~|553x310px~~]]</li>

<li>There are a total of 28 GPIO ports in the 40pins of the development board that can be used. The following uses pin 11—the corresponding GPIO is GPIO1_A4—the corresponding wPi serial number is 5—as an example to demonstrate how to set the high and low levels of the GPIO port. First click the '''CheckBox''' button corresponding to pin 11. When the button is selected, pin 11 will be set to high level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is '''3.3v''', it means setting high level success

[[File:~~media/image655~~plus5-img655.png~~|204x392px~~]]</li>

<li>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is '''OUT''', and the pin level is high

[[File:~~media/image656~~plus5-img656.png~~|552x259px~~]]</li>

<li>Click the '''CheckBox''' button in the figure below again to cancel the check status. Pin 11 will be set to low level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is '''0v''', it means that the low level is set successfully.

[[File:~~media/image657~~plus5-img657.png~~|205x394px~~]]</li>

<li>Then click the '''GPIO READALL''' button, you can see that the current mode of pin 11 is OUT, and the pin level is low

[[File:~~media/image658~~plus5-img658.png~~|552x258px~~]]</li></ol>

<li>'''UART3''' and '''UART8''' are enabled by default in Android. The position of the 40pin is shown in the figure below, and the corresponding device nodes are /dev/ttyS3 and /dev/ttyS8 respectively

[[File:~~media/image659~~plus5-img659.png~~|508x139px~~]]</li>

<li>First click on the wiringOP icon to open the wiringOP APP

[[File:~~media/image651~~plus5-img651.png~~|552x183px~~]]</li>

<li>The main interface of wiringOP APP is displayed as shown in the figure below, and then click the '''UART_TEST''' button to open the UART test interface

[[File:~~media/image660~~plus5-img660.png~~|552x123px~~]]</li><li>The serial port test interface of the APP is shown in the figure below</li>~~</ol>~~ ~~[[File:media/image661.png|552x310px]]~~

[[File:plus5-img661.png]]

</ol>

<li>Take the test of '''UART3''' as an example below, select the '''/dev/ttyS3''' node in the selection box, enter the baud rate you want to set in the edit box, and then click the '''OPEN''' button to open the '''/dev/ttyS3''' node. After opening successfully, click the '''OPEN ''' button becomes unselectable, and the '''CLOSE''' button and '''SEND''' button become selectable</li>~~</ol>~~ ~~[[File:media/image662.png|552x154px]]~~

[[File:plus5-img662.png]]

</ol>

<li>Then use Dupont wire to short the RXD and TXD pins of uart3

[[File:~~media/image663~~plus5-img663.png~~|455x121px~~]]</li><li>Then you can enter a character in the send edit box below, and click the '''SEND''' button to start sending</li>~~</ol>~~ ~~[[File:media/image664.png|553x155px]]~~

[[File:plus5-img664.png]]

</ol>

<li>If everything is normal, the received string will be displayed in the receiving box</li~~></ol~~>

[[File:~~media/image665~~plus5-img665.png~~|553x290px~~]]</ol>

~~~~==~~= 26pin~~ 40pin SPI test ===

<li>From the table below, the available SPIs for Orange Pi 5 Plus are SPI0 and SPI4

[[File:~~media/image304~~plus5-img304.png~~|575x137px~~]]</li>

<li>The Android system opens the SPI0 configuration by default. Here is a demonstration to test the SPI0 interface through the w25q64 module. First, connect the w25q64 device to the SPI0 interface.

[[File:~~media/image666~~plus5-img666.png~~|195x164px~~]]</li>

<li>Then click the wiringOP icon to open the wiringOP APP

[[File:~~media/image651~~plus5-img651.png~~|552x183px~~]]</li>

<li>The main interface of wiringOP APP is displayed as shown in the figure below, click the '''SPI_TEST''' button to open the SPI test interface

[[File:~~media/image667~~plus5-img667.png~~|552x123px~~]]</li><li>Then click the '''OPEN''' button to initialize the SPI</li>~~</ol>~~ ~~[[File:media/image668.png|552x155px]]~~

[[File:plus5-img668.png]]

</ol>

<li>Then fill in the bytes that need to be sent, such as reading the ID information of w25q64, fill in the address 0x9f in data[0], and then click the '''TRANSFER''' button

[[File:~~media/image669~~plus5-img669.png|575x252px]]</li><li>Finally, the APP will display the read ID information</li>~~</ol>~~ ~~[[File:media/image670.png|552x206px]]~~

[[File:plus5-img670.png]]

</ol>

<li>The MANUFACTURER ID of the w25q64 module is EFh, and the Device ID is 4017h, corresponding to the value read above (h stands for hexadecimal)

[[File:~~media/image671~~plus5-img671.png~~|374x126px~~]]</li></ol>

=== ~~26pin~~ 40pin PWM test ===

<li>Android enables '''PWM10''' and '''PWM14''' by default, and the corresponding pins are located at 40pin as shown in the figure below：

[[File:~~media/image672~~plus5-img672.png~~|431x130px~~]]</li>

<li>First click on the wiringOP icon to open the wiringOP APP

[[File:~~media/image651~~plus5-img651.png~~|552x183px~~]]</li>

<li>Then click the '''PWM_TEST''' button on the main interface of wiringOP to enter the PWM test interface

[[File:~~media/image673~~plus5-img673.png~~|553x125px~~]]</li>

<li>The base address corresponding to PWM10 is '''febe0020''', and the base address corresponding to PWM14 is '''febf0020'''. Here, '''fd8b0020.pwm''' is displayed on the right of pwmchip0. At this time, you need to click the drop-down option to select other pwmchips until '''febe0020''' or '''febf0020''' is displayed on the right.

[[File:~~media/image674~~plus5-img674.png~~|553x111px~~]]</li>

<li>When the drop-down option menu selects '''pwmchip2''', the corresponding base address of '''PWM10''' is '''febe0020''' on the right

[[File:~~media/image675~~plus5-img675.png~~|553x102px~~]]</li>

<li>When the drop-down option menu selects '''pwmchip4''', the corresponding base address of '''PWM14''' is '''febe0020''' on the right

[[File:~~media/image676~~plus5-img676.png~~|553x102px~~]]</li>

<li>Take the test of PWM10 as an example, we need to select '''pwmchip2'''

[[File:~~media/image675~~plus5-img675.png~~|553x102px~~]]</li>

<li>Then confirm the PWM period, the default configuration is '''50000ns''', converted to PWM frequency is '''20KHz''', you can modify it yourself, click the open button to export '''PWM10'''

[[File:~~media/image677~~plus5-img677.png~~|552x101px~~]]</li><li>Then drag the drag bar below to change the PWM duty cycle, and then check Enable to output the PWM waveform</li>~~</ol>~~ ~~[[File:media/image678.png|575x116px]]~~

[[File:plus5-img678.png]]

</ol>

<li>Then use an oscilloscope to measure the 31st pin in the 40pin of the development board, and you can see the following waveform</li~~></ol~~>

[[File:~~media/image679~~plus5-img679.png~~|460x276px~~]]</ol>

~~~~

== How to use ADB ==

<li>First prepare a good quality Type-C data cable

[[File:~~media/image21~~plus5-img21.png~~|122x97px~~]]</li>

<li>Then connect the development board and Ubuntu PC through the Type-C data cable. The position of the Type-C interface of the development board is shown in the figure below:

[[File:~~media/image52.jpeg|319x90px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~plus5-2img52.~~jpg未标题-2~~png]]

</div></li>

<li>Then install the adb tool on the Ubuntu PC

{| class="wikitable" style="width:800px;"

|-

|

test@test:~$ '''sudo apt update'''

test@test:~$ '''sudo apt -y install adb'''|}</li>

<li>You can view the identified ADB devices through the following command

{| class="wikitable" style="width:800px;"

|-

|

test@test:~$ '''adb devices'''

List of devices attached

S63QCF54CJ device

test@test:~$ '''lsusb'''

Bus 003 Device 006: ID 2207:0006|}</li><li>Then you can log in to the android system through the adb shell on the Ubuntu PC</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

test@test:~$ '''adb shell'''

console:/ $

|}</ol>

<li>Execute the following command to remount the Android system</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

test@test:~$ '''adb root'''

test@test:~$ '''adb remount'''

|}</ol>

<li>Then you can transfer files to the Android system</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

test@test:~$ '''adb push example.txt /system/'''

|}

</ol>

~~~~

=== Use network connection adb debugging ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Using the network adb does not require a data cable of the Typc-C interface to connect the computer and the development board, but to communicate through the network, so first of all, please ensure that the wired or wireless network of the development board has been connected, and then obtain the IP address of the development board, and then to use.'''</big>|}

<li>Make sure that the '''service.adb.tcp.port''' of the Android system is set to port number 5555

{| class="wikitable" style="width:800px;"

|-

|

console:/ # '''getprop | grep "adb.tcp"'''

[service.adb.tcp.port]: ['''5555''']|}</li><li>If '''service.adb.tcp.port''' is not set, you can use the following command to set the port number of network adb</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

console:/ # '''setprop service.adb.tcp.port 5555'''

console:/ # '''start adbd'''

|}</ol>

<li>Install adb tool on Ubuntu PC

{| class="wikitable" style="width:800px;"

|-

|

test@test:~$ '''sudo apt update'''

test@test:~$ '''sudo apt install -y adb'''|}</li>

<li>Then connect network adb on Ubuntu PC

{| class="wikitable" style="width:800px;"

|-

|

test@test:~$ '''adb connect 192.168.1.xxx''' '''(The IP address needs to be changed to the IP address of the development board)'''

* daemon not running; starting now at tcp:5037

* daemon started successfully

connected to 192.168.1.xxx:5555

test@test:~$ '''adb devices'''

List of devices attached

192.168.1.xxx:5555 device|}</li><li>Then you can log in to the android system through the adb shell on the Ubuntu PC</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

test@test:~$ '''adb shell'''

console:/ #

|}

</ol>

~~~~

== 2.4G USB remote control tested by Android Box ==

<li>Contains a remote control

[[File:~~media/image680~~plus5-img680.png~~|199x149px~~]]</li>

<li>A USB wireless receiver

[[File:~~media/image681~~plus5-img681.png~~|110x119px~~]]</li></ol>

</li>

<li>The Android Box system does not require any configuration, it can be used after plugging it in</li></ol>

<li>The development board comes with an infrared receiver, and its location is shown in the figure below：

[[File:~~media/image682~~plus5-img682.png~~|435x124px~~]]</li>

<li>Before testing infrared reception, we need to prepare an infrared remote control

[[File:~~media/image683~~plus5-img683.png~~|141x127px|6FBFE2FA-31A4-4a26-AC63-9A3E4E359FFF~~]]

</div>

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note: The Android system provided by Orange Pi only supports the remote control provided by Orange Pi by default, and the remote control of TV or air conditioner cannot be used.'''</big>|}</li>

<li>The Android Box system has been adapted to this remote control, and it can be used directly without other settings.</li></ol>

== How to use HDMI CEC function in Android Box system ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''HDMI CEC allows users to control all connected devices through HDMI with only one remote control. Based on this function, we can control the development board with the remote control of the TV.'''

'''Before testing this function, please make sure your TV supports HDMI CEC.'''</big>|}

<li>First connect the development board to the TV through the HDMI cable, then power on and start</li>

<li>Then turn on the HDMI CEC function in the TV settings. Different TVs may have different ways to turn it on. Here we take Xiaomi TV as an example. Press the menu button on the remote control, then select CEC remote control and press the confirmation button

[[File:~~media/image684~~plus5-img684.png~~|575x323px~~]]</li>

<li>Then select '''"On"''' to open the HDMI CEC remote control

[[File:~~media/image685~~plus5-img685.png~~|576x257px~~]]</li>

<li>At this point, you can control the Android Box system of the development board through the remote control of the TV</li></ol>

<li>First download the Android 12 source code sub-volume compressed package from Google network disk

[[File:~~media/image686~~plus5-img686.png~~|575x138px~~]]</li>

<li>After downloading the sub-volume compression package of the Android 12 source code, please check whether the MD5 checksum is correct, if not, please download the source code again

{| class="wikitable" style="width:800px;"

|-

|

test@test:~$ '''md5sum -c Android_12.tar.gz.md5sum'''

<pstyle="color:#FF0000">'''Android_12.tar.gz00: confirm'''<pstyle="color:#FF0000">'''Android_12.tar.gz01: confirm'''<pstyle="color:#FF0000">'''Android_12.tar.gz02: confirm'''<pstyle="color:#FF0000">'''Android_12.tar.gz03: confirm'''<pstyle="color:#FF0000">'''Android_12.tar.gz04: confirm'''<pstyle="color:#FF0000">'''Android_12.tar.gz05: confirm'''<pstyle="color:#FF0000">'''Android_12.tar.gz06: confirm'''<pstyle="color:#FF0000">'''Android_12.tar.gz07: confirm'''|}</li><li>Then you need to merge multiple compressed files into one, and then decompress</li~~></ol~~>

{| class="wikitable" style="width:800px;"

|-

|

test@test:~$ '''cat Android_12.tar.gz0* > Android_12.tar.gz'''

test@test:~$ '''tar -xvf Android_12.tar.gz'''

|}

</ol>

~~~~

== Compile the source code of Android 12 ==

<li>First install the software packages required to compile the Android12 source code

{| class="wikitable" style="width:800px;"

|-

|

test@test:~$ '''sudo apt-get update'''

test@test:~$ '''sudo apt-get install -y git gnupg flex bison gperf build-essential \'''

'''lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z1-dev ccache \'''

'''libgl1-mesa-dev libxml2-utils xsltproc unzip'''

test@test:~$ '''sudo apt-get install -y u-boot-tools'''|}</li>

<li>There is a build.sh compilation script in the source code, and the compilation parameters are as follows

<ol style="list-style-type: lower-alpha;"><li>a.-'''U''': compile uboot</li><li>b.-'''K''': compile kernel</li><li>c.-'''A''': compile android</li><li>d.-'''u''': package and generate update.img and update_spi_nvme.img</li><li>e.-'''o''': Compile the OTA package</li><li>f.-'''d''': specify kernel dts</li></ol></li>

<li>Compile uboot, kernel, android and package them into update.img

<li>The command to compile and support HDMI 8K display image (LCD > off by default) is as follows：

{| class="wikitable" style="width:800px;"

|-

|

test@test:~$ '''cd Android_12'''

test@test:~/ Android_12$ '''source build/envsetup.sh'''

test@test:~/ Android_12$ '''lunch rk3588_s-userdebug'''

test@test:~/ Android_12$ '''./build.sh -AUKu'''|}</li>

<li>The command to compile and support LCD display image is as > follows：

{| class="wikitable" style="width:800px;"

|-

|

test@test:~$ '''cd Android_12'''

test@test:~/ Android_12$ '''export DUAL_LCD=true'''

test@test:~/ Android_12$ '''source build/envsetup.sh'''

test@test:~/ Android_12$ '''lunch rk3588_s-userdebug'''

test@test:~/ Android_12$ '''./build.sh -AUKu'''|}</li>

<li>The command to compile the image of the Box version is as > follows：

{| class="wikitable" style="width:800px;"

|-

|

test@test:~$ '''cd Android_12'''

test@test:~/ Android_12$ '''export BOARD=orangepi5plus'''

test@test:~/ Android_12$ '''source build/envsetup.sh'''

test@test:~/ Android_12$ '''lunch rk3588_box-userdebug'''

test@test:~/ Android_12$ '''./build.sh -AUKu'''|}</li></ol>

</li>

<li>After the compilation is complete, the following information will be printed

{| class="wikitable" style="width:800px;"

|-

|

********rkImageMaker ver 2.1********

Generating new image, please wait...

New image generated successfully!

Making update.img OK.

Make update image ok!|}</li>

<li>The final image file will be placed in the '''rockdev/Image-rk3588_s''' directory. Among them, '''update.img''' is the boot image that supports TF card and eMMC, and '''update_spi_nvme.img''' is the boot image of NVME SSD

{| class="wikitable" style="width:800px;" |-|~~[mailto:test@test:~OrangePi_4/rk3399-android-8.1$~~ test@test:~/Android_12$] '''cd rockdev/Image-rk3588s_s'''~~[mailto:test@test:~OrangePi_4/rk3399-android-8.1$~~ test@test:~/Android_12/rockdev/Image-rk3588s_s $] '''ls update*'''update.img update_spi_nvme.img|}</li>

<li>If you compile the image of the Box version, the final generated image file will be placed in the '''rockdev/Image-rk3588_box''' directory

{| class="wikitable" style="width:800px;" |-|~~[mailto:test@test:~OrangePi_4/rk3399-android-8.1$~~ test@test:~/Android_12$] '''cd rockdev/Image-rk3588_box'''~~[mailto:test@test:~OrangePi_4/rk3399-android-8.1$~~ test@test:~/Android_12/rockdev/Image-rk3588_box$] '''ls update*'''update.img update_spi_nvme.img|}</li></ol>

== Function adaptation of OPi OS Droid system ==

{| class="wikitable" style="width:800px;"

|-

| style="text-align: left;"| '''Function'''

|-

| style="text-align: left;"| '''AX200-WIFI'''

| style="text-align: left;"| '''NO'''

|-

| style="text-align: left;"| '''AX200-BT'''

| style="text-align: left;"| '''NO'''

|-

| style="text-align: left;"| '''AX210-WIFI'''

| style="text-align: left;"| '''NO'''

|-

| style="text-align: left;"| '''AX210-BT'''

| style="text-align: left;"| '''NO'''

|-

| style="text-align: left;"| '''RTL8852BE-WIFI'''

|-

| style="text-align: left;"| '''MIPI LCD'''

| style="text-align: left;"| '''NO'''

|-

| style="text-align: left;"| '''HDMI CEC'''

| style="text-align: left;"| '''NO'''

|}

== Test method of HDMI In ==

<li>The location of the HDMI In interface on the development board is as follows：

[[File:~~media/image265~~plus5-img265.png~~|282x90px~~]]</li>

<li>Then use the HDMI to HDMI cable shown in the figure below to connect the HDMI output of other devices to the HDMI In interface of the development board

[[File:~~media/image11~~plus5-img11.png~~|136x88px~~]]</li>

<li>Make sure that the HDMI output of the device connected to the HDMI In interface is normal, and then open the HDMI In test APP

[[File:~~media/image687~~plus5-img687.png~~|395x222px~~]]</li>

<li>Then the window shown in the figure below will appear. At this time, the video input of HDMI In cannot be seen. You need to click the position marked in the red box in the figure below to enlarge it to full screen

[[File:~~media/image688~~plus5-img688.png~~|384x229px~~]]</li>

<li>Then you can see the video input of HDMI In, and the audio input of HDMI In will also be output from the HDMI TX interface or headphone interface of the development board. The figure below shows the desktop of the Linux system of the OPi5 development board input through HDMI In.

[[File:~~media/image689~~plus5-img689.png~~|400x238px~~]]</li></ol>

{| class="wikitable"

|-

| ~~* *vers ion**~~'''version'''

| ~~* *~~'''Date**'''

| '''Updated Notes'''

|-

| v1.0

| ~~202 3~~2023-05-22

| initial version

|-

| v1.1

| ~~202 3~~2023-05-24| 1. How to use the infrared remote control of the Android Box system

2. Instructions for using the Orange Pi OS Droid system

|-

| v1.2

| ~~202 3~~2023-05-26| 1. Ubuntu/Debian: HDMI IN test method

2. Delete the instructions for using the RTL8821CU USB WIFI module, this module is not recommended

|-

| v1.3

| ~~202 3~~2023-05-29| 1. Update the method of using RKDevTool to burn the image to spiflash+ssd

2. Use RKDevTool to clear SPIFlash

|-

| v1.4

| 2023-05-31

|

1. Update the usage method of M.2 E-Key PCIe WIFI6+Bluetooth module

2. Ubuntu/Debian: How to use the ZFS file system

3. Ubuntu/Debian: Turn off the green light and blue light by default when booting

4. Add the instructions for using the Debian12 system (scattered in multiple sections)

5. Instructions for using the 5v pin in the 40pin interface of the development board to supply power

|-

| v1.5

| 2023-06-07

|

1. Add the picture of eMMC module

2. Correct the picture of the cooling fan interface

3. Add a method to check the temperature of nvme ssd

|}

== Image update history ==

{| class="wikitable"

|-

| ~~* *~~'''Date**'''

| '''Updated Notes'''

|-

| ~~202 3~~2023-05-19| Orangepi5plus_1.0.0_debian_bullseye_server_linux5.10.110.7z

~~Oran gepi5plus_1~~Orangepi5plus_1.0.0_debian_bullseye_desktop_xfce_linux5.10.110.7z

~~Orangepi5p lus_1~~Orangepi5plus_1.0.0_debian_bullseye_desktop_kde-plasma_linux5.10.110.7z

Orangepi5plus_1.0.0_ubuntu_focal_server_linux5.10.110.7z

~~O rangepi5plus_1~~Orangepi5plus_1.0.0_ubuntu_focal_desktop_xfce_linux5.10.110.7z Orangepi5plus_1.0.0_ubuntu_jammy_server_linux5.10.110.7z Orangepi5plus_1.0.0_ubuntu_jammy_desktop_xfce_linux5.10.110.7z Orangepi5plus_1.0.0_ubuntu_jammy_desktop_gnome_linux5.10.110.7z Opios-droid-aarch64-opi5plus-23.05-linux5.10.110.tar.gz Opios-droid-aarch64-opi5plus-23.05-linux5.10.110-spi-nvme.tar.gz OrangePi5Plus_RK3588_Android12_v1.0.0.tar.gz OrangePi5Plus_RK3588_Android12_lcd_v1.0.0.tar.gz OrangePi5Plus-RK3588_Android12-box_v1.0.0.tar.gz OrangePi5Plus_RK3588_Android12_spi-nvme_v1.0.0.tar.gz OrangePi5Plus_RK3588_Android12_spi-nvme_lcd_v1.0.0.tar.gz OrangePi5Plus-RK3588_Android12-box_spi-nvme_v1.0.0.tar.gz openwrt-aarch64-opi5plus-23.05-linux5.10.110-ext4.img.gz * initial version |-| 2023-05-22| Opios-arch-aarch64-gnome-opi5plus-23.05-linux5.10.110.img.xz openwrt-rockchip -armv8-xunlong_orangepi-5-plus-spi-squashfs-sysupgrade.bin * initial version |-| 2023-05-24| Orangepi5plus_1.0.2_debian_bullseye_desktop_kde-plasma_linux5.10.110 * Fix the problem that desktop audio cannot be used * Update the chromium browser to chromium-browser_110.0, which supports video playback in h264, h265, vp8, vp9 and av1 formats |-| 2023-05-26| Opios-arch-aarch64-gnome-opi5plus-23.05.1-linux5.10.110.img.xz * Taskbar: remove calendar and music, add shortcuts for command line terminal and browser * Support to open the command line terminal through the shortcut key of CTRL+ALT+T OrangePi5Plus_RK3588_Android12_v1.0.1.tar.gz OrangePi5Plus_RK3588_Android12_v1.0.1_lcd.tar.gz OrangePi5Plus_RK3588_Android12_v1.0.1_spi-nvme.tar.gz OrangePi5Plus_RK3588_Android12_v1.0.1_lcd_spi-nvme.tar.gz * pre-install google play store Orangepi5plus_1.0.4_debian_bullseye_desktop_kde-plasma_linux5.10.110.7z * Support CTRL+ALT+T shortcut to open the command line terminal * Added shortcuts for konsole terminal and chromium browser in the taskbar * Optimize the display name of the audio device * Optimize test_hdmiin.sh test script * Fix the problem that spiflash+nvme ssd cannot start Orangepi5plus_1.0.4_debian_bullseye_desktop_xfce_linux5.10.110.7z * Support CTRL+ALT+T shortcut to open the command line terminal * Optimize the display name of the audio device * Optimize test_hdmiin.sh test script * Update the chromium browser to chromium-browser_110.0, which supports video playback in h264, h265, vp8, vp9 and av1 formats * Fix the problem that spiflash+nvme ssd cannot start Orangepi5plus_1.0.4_ubuntu_focal_desktop_xfce_linux5.10.110.7z Orangepi5plus_1.0.4_ubuntu_jammy_desktop_xfce_linux5.10.110.7z Orangepi5plus_1.0.4_ubuntu_jammy_desktop_gnome_linux5.10.110.7z * Support CTRL+ALT+T shortcut to open the command line terminal * Optimize the display name of the audio device * Optimize test_hdmiin.sh test script * Fix the problem that spiflash+nvme ssd cannot start Orangepi5plus_1.0.4_debian_bullseye_server_linux5.10.110.7z Orangepi5plus_1.0.4_ubuntu_focal_server_linux5.10.110.7z Orangepi5plus_1.0.4_ubuntu_jammy_server_linux5.10.110.7z * Fix the problem that spiflash+nvme ssd cannot start |-| 2023-05-29| Opios-droid-aarch64-opi5plus-23.05.1-linux5.10.110-en.tar.gz Opios-droid-aarch64-opi5plus-23.05.1-linux5.10.110-en-spi-nvme.tar.gz * Pre-installed google play store (en in the above image name means English version, you need to go to Google network disk to download) |-| 2023-06-01| Orangepi5plus_1.0.6_ubuntu_jammy_desktop_xfce_linux5.10.110.7z * Fix the problem that the zfs file system cannot be installed * Add rk3588-opi5plus-disable-leds.dtbo, used to turn off blue and green lights * Update the chromium browser to chromium-browser_110.0, which supports video playback in h264, h265, vp8, vp9 and av1 formats

Orangepi5plus_1.0.~~0_ubuntu_jammy_server_linux5~~6_debian_bullseye_desktop_xfce_linux5.10.110.7z

~~O rangepi5plus_1~~Orangepi5plus_1.0.~~0_ubuntu_jammy_desktop_xfce_linux5~~6_debian_bullseye_desktop_kde-plasma_linux5.10.110.7z

~~Or angepi5plus_1.0.0_ubuntu_jammy_desktop_gnome_linux5.10.110~~* Update mpp package

~~Opios-droid-aarch64-opi5plus-23.05-linux5.10.110.tar.gz~~* Fix the problem that the zfs file system cannot be installed

~~Opios- droid-aarch64~~* Add rk3588-opi5plus-~~23.05-linux5.10.110-spi~~disable-~~nvme.tar~~leds.gzdtbo, used to turn off blue and green lights

~~OrangePi5Plus_RK3588_Android12_v1~~Orangepi5plus_1.0.06_ubuntu_focal_desktop_xfce_linux5.10.~~tar~~110.gz7z

~~OrangePi5Plus_RK3588_Android12_lcd_v1~~Orangepi5plus_1.0.06_ubuntu_jammy_desktop_gnome_linux5.10.~~tar~~110.gz7z

~~OrangePi5Plus-RK3588_Android12-box_v1~~Orangepi5plus_1.0.06_ubuntu_focal_server_linux5.10.~~tar~~110.gz7z

~~OrangePi5Plus_RK3588_Android12_spi-nvme_v1~~Orangepi5plus_1.0.06_debian_bullseye_server_linux5.10.~~tar~~110.gz7z

~~OrangePi5Plus_RK3588_Android12_spi-nvme_lcd_v1~~Orangepi5plus_1.0.06_ubuntu_jammy_server_linux5.10.~~tar~~110.gz7z

~~OrangePi5Plus~~* Add rk3588-~~RK3588_Android12~~opi5plus-~~box_spi~~disable-~~nvme_v1~~leds.~~0.0.tar.gz~~dtbo, used to turn off blue and green lights

~~openwrt-aarch64-opi5plus-23.05-linux5.10.110-ext4.img.gz~~* Fix the problem that the zfs file system cannot be installed

* initial versionOrangepi5plus_1.0.6_debian_bookworm_server_linux5.10.110

|-~~| 202 3-05-22| Op ios-arch-aarch64-gnome-opi5plus-23~~Orangepi5plus_1.~~05-linux5~~0.6_debian_bookworm_desktop_xfce_linux5.10.110~~.img.xz~~ ~~openwrt-rockchip -armv8-xunlong_orangepi-5-plus-spi-squashfs-sysupgrade.bin~~

* initial version

|-

~~| 202 3-05-24~~

~~| Orangepi5p lus_1.0.2_debian_bullseye_desktop_kde-plasma_linux5.10.110~~

* Fix the problem that desktop audio cannot be used

* Update the chromium browser to chromium-browser_110.0, which supports video playback in h264, h265, vp8, vp9 and av1 formats

|-

~~| 202 3-05-26~~

~~| Opio s-arch-aarch64-gnome-opi5plus-23.05.1-linux5.10.110.img.xz~~

* Taskbar: remove calendar and music, add shortcuts for command line terminal and browser

* Support to open the command line terminal through the shortcut key of CTRL+ALT+T

~~OrangePi5Plus_RK3588_Android12_v1.0.1.tar.gz~~

~~OrangePi5Plus_RK3588_Android12_v1.0.1_lcd.tar.gz~~

~~OrangePi5Plus_RK3588_Android12_v1.0.1_spi-nvme.tar.gz~~

~~OrangePi5Plus_RK3588_Android12_v1.0.1_lcd_spi-nvme.tar.gz~~

* pre-install google play store

~~Orangepi5p lus_1.0.4_debian_bullseye_desktop_kde-plasma_linux5.10.110~~

* Support CTRL+ALT+T shortcut to open the command line terminal

* Added shortcuts for konsole terminal and chromium browser in the taskbar

* Optimize the display name of the audio device

* Optimize test_hdmiin.sh test script

* Fix the problem that spiflash+nvme ssd cannot start

~~Oran gepi5plus_1.0.4_debian_bullseye_desktop_xfce_linux5.10.110~~

* Support CTRL+ALT+T shortcut to open the command line terminal

* Optimize the display name of the audio device

* Optimize test_hdmiin.sh test script

* Update the chromium browser to chromium-browser_110.0, which supports video playback in h264, h265, vp8, vp9 and av1 formats

* Fix the problem that spiflash+nvme ssd cannot start

~~Or angepi5plus_1.0.4_ubuntu_focal_desktop_xfce_linux5.10.110 ~~

~~Or angepi5plus_1.0.4_ubuntu_jammy_desktop_xfce_linux5.10.110 ~~

~~Or angepi5plus_1.0.4_ubuntu_jammy_desktop_gnome_linux5.10.110~~

* Support CTRL+ALT+T shortcut to open the command line terminal

* Optimize the display name of the audio device

* Optimize test_hdmiin.sh test script

* Fix the problem that spiflash+nvme ssd cannot start

~~Orangepi5plus_1.0.4_debian_bullseye_server_linux5.10.110 ~~

~~Orangepi5plus_1.0.4_ubuntu_focal_server_linux5.10.110 ~~

~~Orangepi5plus_1.0.4_ubuntu_jammy_server_linux5.10.110~~

* Fix the problem that spiflash+nvme ssd cannot start

|}

Admin

Bureaucrats, Administrators

6,556

edits

Wiki-Orange Pi β

Changes

Orange Pi 5 Plus

Wiki-Orange Pi ^β