Changes

← Older edit

Orange Pi 5 Plus

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

→‎Burn Orange Pi OS (Droid) image toeMMC

[[File:plus5-img75.png]]

</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:plus5-img76.png]]

</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:plus5-img77.png]]</li></ol>

</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>

# 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:plus5-img78-1.png]][[File:plus5-img78-2.png]] ::[[File:plus5-img78-3.png]]

<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;"

<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;"

</div></ol>

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

</div></ol>

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

<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'''|}

</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:plus5-img119.png]]

</ol>

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

[[File:plus5-img120.png]]

</ol>

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

</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>

</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>

</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:plus5-img124.png]]

</ol>

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

[[File:plus5-img125.png]]

</ol>

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

[[File:plus5-img126.png]]

</ol>

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

[[File:plus5-img127.png]]

</ol>

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

[[File:plus5-img128.png]]

<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>

</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:plus5-img57.png]]

[[File:plus5-img139.png]]

{| 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:plus5-img148.png]]

{| 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>

# 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:plus5-img78-1.png]][[File:plus5-img78-2.png]] ::[[File:plus5-img78-3.png]]

<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>

</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>

# 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:plus5-img78-1.png]][[File:plus5-img78-2.png]] ::[[File:plus5-img78-3.png]]

<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:plus5-img151.png]]

~~</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:plus5-img152.png]]

</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:plus5-img153.png]]

</ol>

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

</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:plus5-img161.png]]

~~</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:plus5-img162.png]]

~~</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:plus5-img163.png]]</li></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:plus5-img78-1.png]][[File:plus5-img78-2.png]] ::[[File:plus5-img78-3.png]]

<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

=== 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>|}

== 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?

|

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

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

|}

</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 ====

<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:plus5-img233.png]]</li>

<li>Then ~~open~~ use the ~~configuration~~ '''lspci''' command, if you can see the 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:~~plus5~~800px;" |-~~img234.png]]</li><li>Then select '''Hardware'''~~|~~[[File~~orangepi@orangepi:~~plus5-img235.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~~ ~$ '''~~wifi-pcie~~lspci | grep "Network"''' ~~configuration~~~~[[File~~0002:~~plus5-img236.png]]</li><li>Then select '''<Save>''' to save[[File~~21:~~plus5-img237~~00.~~png]]</li><li>Then select '''<Back>'''[[File~~0 Network controller:~~plus5~~Intel Corporation Wi-~~img238.png]]~~Fi 6 AX200 (rev 1a)</p~~></li~~>~~<li>Then select '''<Reboot>''' to restart the system to make the configuration take effect~~|}~~[[File:plus5-img239.png]]~~</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>

<big>'''An example using adb in Windows looks like this:'''</big>

[[File:plus5-img245.png|800px]]

|}

</li></ol>

<big>'''An example using adb in Windows looks like this:'''</big>

[[File:plus5-img246.png|800px]]

|}

</ol>

</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;"

|-

| '''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>

|-

|

~~~~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>

<li>As can be seen from the figure below, the SPIs available for Orange Pi 5 Plus are SPI0 and SPI4

[[File:plus5-img304.png]]</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>Then select '''<Back>'''

[[File:plus5-img264.png]]</li>

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

[[File:plus5-img239.png]]</li></ol>

</li>

[[File:plus5-img336.png|1200px]]

</div></ol>

[[File:plus5-img95.png|1200px]]

</div></li>

|-

|

'''Debian11 ~~>~~ > Ubuntu 22.04> Debian12'''

|}

</li>

[[File:plus5-img340.png]]</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:plus5-img341.png|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:plus5-img342.png|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:plus5-img343.png]]</li>

</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:plus5-img346.png|1500px]]</li>

<li>Pagoda command line tool test

</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:plus5-img348.png|1500px]]</li>

<li>Then set the default '''locale''' as '''zh_CN.UTF-8'''

[[File:plus5-img349.png|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;"

|-

|

<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:plus5-img379.png]]

</ol>

~~</li></ol>~~

<li>In addition, you can also download the installation package of '''NoMachine''' in the '''official tools'''

|}

</li></ol>

<li>Then download the NoMachine software Windows version of the installation package, the download address is shown below</li>

[[File:plus5-img386.png]]</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:plus5-img387-1.png]]</li>

<li>Then click OK in the next interface</li>

<li>Finally, you can see the desktop of the development board Linux system

<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>

<li>Then enter the password of the previously set VNC

[[File:plus5-img390.png]]</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:plus5-img391.png]]

<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;"

|-

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>The version of QT Creator is shown below

<li>The default version of QT Creator in '''Ubuntu20.04''' is shown ~~>~~ below

[[File:plus5-img394.png]]</li>

<li>The default version of QT Creator in '''Ubuntu22.04''' is shown ~~>~~ below

[[File:plus5-img395.png]]</li>

<li>The default version of QT Creator in '''Debian11''' is shown below

[[File:plus5-img396.png]]</li><li>The default version of QT Creator in '''Debian12''' is as follows[[File:plus5-img396-1.png]]</li></ol>

</li>

<li>Then set the QT

[[File:plus5-img398.png]]</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:plus5-img399.png]]

[[File:plus5-img400.png]]</li></ol>

|}

</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>The No. 3 interface is not used, just ignore it.</li>

[[File:plus5-img437-1.png]]

</ol>

Orange Pi 5 Plus development board has a total of 1 camera interface, which 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:plus5-img446.png]]</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:~~plus5~~800px;" |-~~img447~~|orangepi@orangepi:~$ '''sudo apt install .~~png|center]]~~/*.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:~~plus5-img446.png]]</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

~~'''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>~~|}zunicode             327680     1   zfs

~~== Ubuntu22.04 GNOME desktop system adaptation situation ==~~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|} In Debian12, the default version of zfs is 2.1.11, so we can install zfs directly through the following command. Again, please make sure that the system has installed the deb package of the kernel header file before installation. {| 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'''~~

|-

| <big>'''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="list-style-type: 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.{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''sudo''' '''reboot'''|}</li></ol> = '''Ubuntu22.04 Gnome Wayland Desktop system instructions''' = {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <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'''

|}

::{| 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]]|} <ol start="2" style="list-style-type: decimal;"><li>Then insert the WiFi module into the M.2 E-Key interface of the development board and fix it

[[File:plus5-img233.png]]</li>

<li>~~Then open~~ If everything is normal after the ~~configuration of 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>

|}

</ol>

<li>Then '''restart the OPi OS Arch system'''</li></ol>

</li></ol>

[[File:plus5-img536.png|1500px]]

</div></li>

<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

<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:plus5-img558-1.png|center]]

|}

::[[File:plus5-img559.png|1500px]]

</div>

<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:plus5-img558-1.png|center]]

|}

::[[File:plus5-img559.png|1500px]]

</div>

<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:plus5-img558-1.png|center]]

|}

<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>

[[File:plus5-img570.png]]

[[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>

=== 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>|}

=== How to connect to WIFI hotspot ===

<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:plus5-img604.png]]</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:plus5-img605.png]]</li></ol>

</li>

<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.'''</big>

|}

</li~~></ol~~>

[[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>

<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:plus5-img610.png|1500px]][[File:plus5-img611.png|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:plus5-img612.png]]</li>

| [[File: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.'''</big>

[[File:plus5-img616-2.png|center]]

|}

<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>

== ~~26pin~~ 40pin interface GPIO, UART, SPI and PWM test ==

</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>

[[File:plus5-img662.png]]

=== ~~26pin~~ 40pin SPI test ===

=== ~~26pin~~ 40pin PWM test ===

</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

| v1.1

| 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

| 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

| 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

|}

|-

| 2023-05-19

| Orangepi5plus_1.0.0_debian_bullseye_server_linux5.10.110.7z

Orangepi5plus_1.0.0_debian_bullseye_desktop_xfce_linux5.10.110.7z

Orangepi5plus_1.0.0_debian_bullseye_desktop_kde-plasma_linux5.10.110.7z

Orangepi5plus_1.0.0_ubuntu_focal_server_linux5.10.110.7z

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.6_debian_bullseye_desktop_xfce_linux5.10.110.7z Orangepi5plus_1.0.6_debian_bullseye_desktop_kde-plasma_linux5.10.110.7z * Update mpp package * Fix the problem that the zfs file system cannot be installed

~~OrangePi5Plus_RK3588_Android12_v1~~* Add rk3588-opi5plus-disable-leds.~~0.0.tar.gz~~dtbo, used to turn off blue and green lights

~~OrangePi5Plus_RK3588_Android12_lcd_v1~~Orangepi5plus_1.0.06_ubuntu_focal_desktop_xfce_linux5.10.~~tar~~110.gz7z

~~OrangePi5Plus-RK3588_Android12-box_v1~~Orangepi5plus_1.0.06_ubuntu_jammy_desktop_gnome_linux5.10.~~tar~~110.gz7z

~~OrangePi5Plus_RK3588_Android12_spi-nvme_v1~~Orangepi5plus_1.0.06_ubuntu_focal_server_linux5.10.~~tar~~110.gz7z

~~OrangePi5Plus_RK3588_Android12_spi-nvme_lcd_v1~~Orangepi5plus_1.0.06_debian_bullseye_server_linux5.10.~~tar~~110.gz7z

~~OrangePi5Plus-RK3588_Android12-box_spi-nvme_v1~~Orangepi5plus_1.0.06_ubuntu_jammy_server_linux5.10.~~tar~~110.gz7z

~~openwrt-aarch64~~* Add rk3588-opi5plus-~~23.05-linux5.10.110~~disable-~~ext4.img~~leds.gzdtbo, used to turn off blue and green lights

* ~~initial version~~Fix the problem that the zfs file system cannot be installed

|-~~| 2023-05-22| Opios-arch-aarch64-gnome-opi5plus-23~~Orangepi5plus_1.~~05-linux5~~0.6_debian_bookworm_server_linux5.10.110~~.img.xz~~

~~openwrt-rockchip -armv8-xunlong_orangepi-5-plus-spi-squashfs-sysupgrade~~Orangepi5plus_1.~~bin~~0.6_debian_bookworm_desktop_xfce_linux5.10.110

* 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~~

* 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~~

* 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 ~~

~~Orangepi5plus_1.0.4_ubuntu_jammy_desktop_xfce_linux5.10.110 ~~

~~Orangepi5plus_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 ^β