Changes

← Older edit

Orange Pi 3B

37,249 bytes added, 09:06, 24 August 2023

→‎Interface details of Orange Pi 3B

Orange Pi 3B brings out quite a lot of interfaces, including HDMI output, M.2 PCIe2.0x1, Gigabit Ethernet port, USB2.0, USB3.0 interface and 40pin expansion pin header, etc. It can be widely used in high-end tablet, edge computing, artificial intelligence, cloud computing, AR/VR, smart security, smart home and other fields, covering various AIoT industries.

Orange Pi 3B supports Android11, Ubuntu22.04, Ubuntu20.04, Debian11, Debian12, ~~open source Hongmeng~~ OpenHarmony 4.0 Beta1, Orange Pi OS (Arch), Orange Pi OS (OH) based on ~~open source Hongmeng~~ OpenHarmony and other operating systems.

== Purpose of Orange Pi 3B ==

• Integrated RKNN NPU AI accelerator, 0.8Tops@INT8 performance

• Supports one-click conversion of ~~C affe~~Caffe/TensorFlow/TFLite/ONNX/PyTorch/Keras/Darknet architecture models

|-

| storage

|

• Support eMMC module: 16GB/32GB/64GB/128GB/256GB

• SPI Flash: 16MB/32MB

| Wi-Fi+Bluetooth

|

Wi-Fi 5+BT 5.~~0，BLE（20U5622）~~0, BLE（20U5622）

|-

| ethernet transceiver

| Supported OS

|

Android11, Ubuntu22.04, Ubuntu20.04, Debian11, Debian12, ~~open source Hongmeng~~ OpenHarmony 4.0 Beta1, Orange Pi OS (Arch), Orange Pi OS (OH) based on ~~open source Hongmeng~~ OpenHarmony and other operating systems.

|-

|colspan=2|

[[File:pi3b-img3.png|800px]]

</div>

[[File:pi3b-img4.png|800px]]

</div>

== Interface details of Orange Pi 3B ==

[[File:pi3b-img5-1.png|800px]]

[[File:pi3b-img6.png|800px]]

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

|-

|

<big>'''The diameter of the four positioning holes is 32.~~0mm~~7mm, and the diameter of the M.2 PICE device fixing hole is 32.~~5mm~~9mm.'''</big>

|}

</ol>

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

[[File:pi3b-img11-1.png]]

</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:pi3b-img17.png|400px]] [[File:pi3b-img18.png|400px]]

</ol>

::[[File:pi3b-img19.png|800px]]

</div>

|-

|

'''https://www.balena.io/etcher/'''

|}

[[File:pi3b-img25.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:pi3b-img26.png~~|428x268px~~]]

</ol>

<li>After burning the Linux image, balenaEtcher will also verify the image burned into 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:pi3b-img27.png~~|427x267px~~]]

</ol>

<li>After ~~the~~ successful burning ~~is completed~~, the display interface of balenaEtcher is as shown in the figure below. If ~~the~~ 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 boardfor use. up</li>

[[File:pi3b-img28.png~~|523x324px|04~~]]

</div></ol>

::[[File:pi3b-img16.png~~|146x143px|D6BB9058-CDC3-42d7-A7FC-FBF630D886B7~~]]

</div>

[[File:pi3b-img29.png~~|283x90px|6d1c77df7eeb7e491e5f79e8d85cbdc~~]]

</div></ol>

[[File:pi3b-img30.png~~|290x130px|34acacded202b29eee42fd20f5b4c92~~]]

</div>

<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:pi3b-img31.png~~|464x136px~~]]

</ol>

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

[[File:pi3b-img32.png~~|245x129px~~]]

</ol>

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

[[File:pi3b-img33.png~~|254x132px~~]]

</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:pi3b-img34.png~~|448x132px~~]]

</ol>

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

[[File:pi3b-img35.png~~|402x189px~~]]

</ol>

[[File:pi3b-img36.png~~|271x115px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\1691131157154(1).jpg1691131157154(1)~~]]

</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:pi3b-img37.png~~|289x100px~~]]

</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:pi3b-img38.png~~|305x94px~~]]

</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:pi3b-img39.png~~|454x213px~~]]

</ol>

[[File:pi3b-img40.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:pi3b-img41.png~~|453x213px~~]]

</ol>

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

[[File:pi3b-img42.png~~|458x215px~~]]

</ol>

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

[[File:pi3b-img43.png~~|457x215px~~]]

</ol>

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

[[File:pi3b-img44.png~~|483x227px~~]]

</ol>

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

[[File:pi3b-img45.png~~|486x228px~~]]

</ol>

[[File:pi3b-img46.png~~|494x232px|[78~~Z7UFB@US@8P$QL%OM6~~]]

</div></ol>

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

[[File:pi3b-img47.png~~|493x232px~~]]

</ol>

|}

[[File:pi3b-img48.png~~|499x234px~~]]

</ol>

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

[[File:pi3b-img49.png~~|497x234px~~]]

</ol>

<li>Click the execute button again to start burning the Linux image to the tf card of the development board</li>

[[File:pi3b-img50.png~~|497x233px~~]]

</ol>

[[File:pi3b-img51.png~~|492x231px|%O4~FPPAT$0RH{3S~CGJ@@Q(1)~~]]

</div></ol>

|-

|

'''https://www.sdcard.org/downloads/formatter/eula_windows/SDCardFormatterv5_WinEN.zip'''

|}

</ol>

[[File:pi3b-img52.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:pi3b-img53.png~~|304x147px~~]]

</ol>

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

[[File:pi3b-img54.png~~|186x149px~~]]

</ol>

</li></ol>

|-

|

'''http://sourceforge.net/projects/win32diskimager/files/Archive/'''

|}

</ol>

[[File:pi3b-img55.png~~|297x206px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\a8fda8737c5b0b3b38fbb75ef68acfc.pnga8fda8737c5b0b3b38fbb75ef68acfc~~]]

</div></ol>

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

[[File:pi3b-img20.png~~|434x208px~~]]

</ol>

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

[[File:pi3b-img56.png~~|430x163px~~]]

</ol>

<li>Then double-click '''balenaEtcher-1.5.109-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:pi3b-img57.png~~|423x251px~~]]

</ol>

[[File:pi3b-img25.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:pi3b-img58.png~~|429x184px~~]]

</ol>

<li>After burning the Linux image, balenaEtcher will also verify the image burned into 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:pi3b-img59.png~~|436x190px~~]]

</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. up</li>

[[File:pi3b-img60.png~~|435x257px~~]]

</ol>

# The development board reserves the expansion interface of the eMMC module. Before burning 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 eMMC module and the method of plugging into the development board are as follows:

::[[File:pi3b-img61.png|~~115x84px~~400px]] [[File:pi3b-img62.png|~~120x87px~~400px]]

::[[File:pi3b-img63.png|~~277x129px~~800px]]

[[File:pi3b-img16.png~~|141x138px|D6BB9058-CDC3-42d7-A7FC-FBF630D886B7~~]]

</div></ol>

[[File:pi3b-img29.png~~|360x115px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\6d1c77df7eeb7e491e5f79e8d85cbdc.png6d1c77df7eeb7e491e5f79e8d85cbdc~~]]

</div></ol>

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

[[File:pi3b-img30.png~~|320x144px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\34acacded202b29eee42fd20f5b4c92.png34acacded202b29eee42fd20f5b4c92~~]]

</div>

<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:pi3b-img31.png~~|496x146px~~]]

</ol>

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

[[File:pi3b-img32.png~~|284x149px~~]]

</ol>

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

[[File:pi3b-img33.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:pi3b-img34.png~~|484x143px~~]]

</ol>

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

[[File:pi3b-img35.png~~|442x208px~~]]

</ol>

[[File:pi3b-img36.png~~|275x116px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\1691131157154(1).jpg1691131157154(1)~~]]

</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:pi3b-img37.png~~|289x100px~~]]

</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:pi3b-img38.png~~|305x94px~~]]

</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:pi3b-img39.png~~|457x215px~~]]

</ol>

[[File:pi3b-img64.png~~|458x215px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-4.jpg未标题-4~~]]

</div></ol>

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

[[File:pi3b-img41.png~~|460x216px~~]]

</ol>

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

[[File:pi3b-img42.png~~|458x215px~~]]

</ol>

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

[[File:pi3b-img65.png~~|466x219px~~]]

</ol>

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

[[File:pi3b-img66.png~~|468x220px~~]]

</ol>

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

[[File:pi3b-img67.png~~|462x217px~~]]

</ol>

[[File:pi3b-img68.png~~|459x216px|SIS5H0S2@F5M2D(6ANZEUPG~~]]

</div></ol>

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

[[File:pi3b-img69.png~~|459x216px~~]]

</ol>

|}

[[File:pi3b-img48.png~~|499x234px~~]]

</ol>

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

[[File:pi3b-img70.png~~|501x235px~~]]

</ol>

<li>Click the execute button again to start burning the Linux image to the eMMC of the development board</li>

[[File:pi3b-img71.png~~|502x236px~~]]

</ol>

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

[[File:pi3b-img72.png~~|500x235px~~]]

</ol>

|-

|

<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 [[Orange Pi 3B#~~the method of using~~ Using RKDevTool to clear SPIFlash|the method of using RKDevTool to clear SPIFlash]].'''</big>

|}

</ol>

=== Use the dd command to burn the Linux image into eMMC ===

{| class="wikitable" style="background-color:#ffffdc;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-3B.html Orange Pi data download page].'''</big>|}

# The development board reserves the expansion interface of the eMMC module. Before burning 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 eMMC module and the method of plugging into the development board are as follows:

::[[File:pi3b-img61.png|~~115x84px~~400px]] [[File:pi3b-img62.png|~~120x87px~~400px]]

::[[File:pi3b-img63.png|~~286x133px~~800px]]

<li>Using the dd command to burn the Linux image to eMMC needs to be completed with the help of 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 [[\lOrange Pi 3B#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 [[\lOrange Pi 3B#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 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 uploading the Linux image file to the development board, please refer to the description in the section of [[\lOrange Pi 3B#The method of uploading files to the Linux system of the development board|'''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~~></ol~~>

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

|-

|

orangepi@orangepi:~$ '''cd /home/orangepi/Desktop'''

Orangepi3b_x.x.x_debian_bullseye_desktop_xfce_Linux5.10.160.img

|}

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

|-

|

<big>'''How to enter the command line of the development board Linux system?'''

'''1. For the method of using the serial port to log in to the terminal, please refer to the instructions in the section on [[Orange Pi 3B#How to ~~enter~~ use the ~~command line of~~ debugging serial port|how to use the ~~development board Linux system?~~debugging serial port]].'''

# '''~~For the method of using the serial port to log in to the terminal, please refer to the instructions in the section on [[\l|how to use the debugging serial port]]~~2.~~'''# '''~~Use ssh to remotely log in to the Linux system, please refer to the instructions in the section of [[\lOrange Pi 3B#SSH remote login development board|SSH remote login to the development board]]~~.'''# '''If HDMI, LCD and other display screens are connected, you can open a command line terminal on the desktop~~.'''

'''3. If HDMI, LCD and other display screens are connected, you can open a command line terminal on the desktop.'''</big>

|}

</ol>

<li>Next, we first use the following command to confirm the device node of eMMC</li~~></ol~~>

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

|-

|

orangepi@orangepi:~/Desktop$ '''ls /dev/mmcblk*boot0 | cut -c1-12'''

'''/dev/mmcblk0'''|}</ol>

<li>Then we can use the dd command to clear the eMMC. Note that after the '''of=''' parameter, please fill in the output result of the above command</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~/Desktop$ '''sudo dd bs=1M if=/dev/zero of=/dev/mmcblk0 count=1000 status=progress'''

orangepi@orangepi:~/Desktop$ '''sudo sync'''

|}</ol>

<li>Then you can use the dd command to burn the Linux image of the development board into the eMMC

<li>In the following command, the '''if= ''' parameter is followed by the full path where the Linux image is stored + the name of the Linux image (such as '''the name of /home/orangepi/Desktop/Linux image'''). Because we have entered the path of the Linux image above, we only need to fill in the name of the Linux image.</li><li>Please do not copy the Linux image name in the following command, but replace it with the actual image name (because the version number of the image may be updated).</li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-| '''sudo dd bs=1M if=Orangepi3b_x.x.x_debian_bullseye_desktop_xfce_Linux5.10.160.img of=/dev/mmcblk0 status=progress'''

'''sudo''' '''sync'''

|}

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

|-

|

<big>'''Note, if you upload a .7z or .xz Linux image compressed file, please remember to decompress it before using the dd command to burn.'''

~~'''Note, if you upload a .7z or .xz Linux image compressed file, please remember to decompress it before using the dd command to burn.'''~~

~~'''The detailed description of all parameters of the dd command and more usage can be viewed by executing the man dd command in the Linux system.'''~~

'''The detailed description of all parameters of the dd command and more usage can be viewed by executing the man dd command in the Linux system.'''</big>

|}

</ol>

</li></ol>

<li>After successfully burning the Linux image of the development board to the eMMC, you can use the '''poweroff''' command to shut down. Then please pull out the TF card, and then short press the power button to turn on, and then the Linux system in the eMMC will be started.</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 [[Orange Pi 3B#Using RKDevTool to clear SPIFlash|the method of using RKDevTool to clear SPIFlash]].'''</big>|}</ol>

'''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 [[\l|the method of using RKDevTool to clear SPIFlash]].'''

~~~~

== How to write Linux image to SPIFlash+NVMe SSD ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the Linux image mentioned here specifically refers to the images of Linux distributions such as Debian and Ubuntu downloaded from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html Orange Pi data download page].'''</big>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that all the following operations are performed on a Windows computer.'''</big>|}

=== Using RKDevTool to burn ===

<li>First, you need to prepare an NVMe SSD. The PCIe supported by the M.2 slot of the development board is PCIe2.0x1, and the theoretical maximum speed is 500MB/s. PCIe3.0 and PCIe4.0 NVMe SSDs are also available, but the highest speed is only PCIe2.0x1.

<li>The M.2 2230 SSD is as follows</li>~~</ol></li></ol>~~ ~~[[File:pi3b-img73.png|157x112px]]~~

[[File:pi3b-img73.png]]

</ol>

<li>The M.2 2242 SSD is as follows</li>~~</ol>~~ ~~[[File:pi3b-img74.png|174x96px]]~~

[[File:pi3b-img74.png]]

</ol>

</li></ol>

<li>Then insert the NVMe SSD into the M.2 PCIe interface of the development board and fix it</li>~~</ol>~~ ~~[[File:pi3b-img75.png|283x63px]]~~

[[File:pi3b-img75.png]]

</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>~~</ol>~~ ~~[[File:pi3b-img76.png|266x211px]]~~

[[File:pi3b-img76.png]]

</ol>

<li>Then you need to prepare a good quality USB2.0 male-to-male data cable</li~~></ol~~>

[[File:pi3b-img16.png~~|141x138px|D6BB9058-CDC3-42d7-A7FC-FBF630D886B7~~]]

</div></ol>

<li>Then download the Rockchip driver '''DriverAssitant_v5.12.zip''' and '''MiniLoader''' and the burning tool '''RKDevTool_Release_v3.15.zip''' from the Orange Pi data download page

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

[[File:pi3b-img29.png~~|362x115px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\6d1c77df7eeb7e491e5f79e8d85cbdc.png6d1c77df7eeb7e491e5f79e8d85cbdc~~]]

</div></ol>

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

[[File:pi3b-img30.png~~|264x118px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\34acacded202b29eee42fd20f5b4c92.png34acacded202b29eee42fd20f5b4c92~~]]

</div>

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the "MiniLoader-things needed to burn the Linux image" folder is hereinafter referred to as the MiniLoader folder.'''</big>|}</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-3B.html '''Orange Pi data 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>

<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>~~</ol>~~ ~~[[File:pi3b-img31.png|446x131px]]~~

[[File:pi3b-img31.png]]

</ol>

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

<li>Click the "'''Driver Installation'''" button</li>~~</ol></li></ol>~~ ~~[[File:pi3b-img32.png|253x133px]]~~

[[File:pi3b-img32.png]]

</ol>

<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.</li>~~</ol>~~ ~~[[File:pi3b-img33.png|269x140px]]~~

[[File:pi3b-img33.png]]

</ol>

</li></ol>

<li>Then decompress '''RKDevTool_Release_v3.15.zizip'''p, this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li>~~</ol>~~ ~~[[File:pi3b-img34.png|402x119px]]~~

[[File:pi3b-img34.png]]

</ol>

<li>After opening the '''RKDevTool''' burning tool, because the computer is not connected to the development board through the USB2.0 male-to-male data cable at this time, the lower left corner will prompt "'''No device found'''"</li>~~</ol>~~ ~~[[File:pi3b-img35.png|402x189px]]~~

[[File:pi3b-img35.png]]

</ol>

<li>Then start burning the Linux image to the SSD

<li>First, connect the development board to the Windows computer through the USB2.0 male-to-male data cable. The position of the USB2.0 programming interface of the development board is shown in the figure below</li~~></ol></li></ol~~>

[[File:pi3b-img36.png~~|275x116px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\1691131157154(1).jpg1691131157154(1)~~]]

</div></ol>

<li>Make sure that the development board is not connected to the power supply and inserted into the TF card and eMMC</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:</li>~~</ol>~~ ~~[[File:pi3b-img37.png|289x100px]]~~

[[File:pi3b-img37.png]]

</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>~~</ol>~~ ~~[[File:pi3b-img38.png|305x94px]]~~

[[File:pi3b-img38.png]]

</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>~~</ol>~~ ~~[[File:pi3b-img39.png|457x215px]]~~

[[File:pi3b-img39.png]]

</ol>

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

[[File:pi3b-img64.png~~|458x215px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-4.jpg未标题-4~~]]

</div></ol>

<li>Then click the right mouse button and the selection interface shown in the figure below will pop up</li>~~</ol>~~ ~~[[File:pi3b-img41.png|453x213px]]~~

[[File:pi3b-img41.png]]

</ol>

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

[[File:pi3b-img42.png~~|458x215px~~]]</ol><ol start="9" style="list-style-type: lower-~~roman~~alpha;"><li>i. Then enter the '''MiniLoader''' folder downloaded earlier, then select the '''rk3588_Linux_pcie.cfg''' configuration file, and click '''Open'''</li>~~</ol>~~ ~~[[File:pi3b-img77.png|462x217px]]~~

[[File:pi3b-img77.png]]

</ol>

<li>Then click '''OK'''</li>~~</ol>~~ ~~[[File:pi3b-img78.png|468x220px]]~~

[[File:pi3b-img78.png]]

</ol>

<li>Then click the position shown in the figure below</li>~~</ol>~~ ~~[[File:pi3b-img79.png|475x223px]]~~

[[File:pi3b-img79.png]]

</ol>

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

[[File:pi3b-img68.png~~|459x216px|SIS5H0S2@F5M2D(6ANZEUPG~~]]

</div></ol>

<li>Then click the position shown in the figure below</li>~~</ol>~~ ~~[[File:pi3b-img80.png|486x228px]]~~

[[File:pi3b-img80.png]]

</ol>

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

[[File:pi3b-img81.png~~|488x228px|GGU}ZN)TL%P[INB(M%MNJV7~~]]

</div></ol>

<li>Then click the position shown in the figure below</li>~~</ol>~~ ~~[[File:pi3b-img82.png|493x231px]]~~

[[File:pi3b-img82.png]]

</ol>

<li>Then select the path of the Linux image you want to burn, and then click '''Open'''</li~~></ol~~>

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <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:pi3b-img48.png~~|~~499x234px]]~~}

[[File:pi3b-img48.png]]

</ol>

<li>Then please check ~~'''~~the ~~mandatory write~~ option to force writing by address~~''' option~~</li>~~</ol>~~ ~~[[File:pi3b-img83.png|498x234px]]~~

[[File:pi3b-img83.png]]

</ol>

<li>Click the Execute button again to start burning the Linux image to the SSD</li>~~</ol>~~ ~~[[File:pi3b-img84.png|500x235px]]~~

[[File:pi3b-img84.png]]

</ol>

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

[[File:pi3b-img85.png~~|504x240px~~]] '''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 description of [[\l|the method of using RKDevTool to clear SPIFlash]].'''

{| 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 description of [[Orange Pi 3B#Using RKDevTool to clear SPIFlash|the method of using RKDevTool to clear SPIFlash]].'''</big>

|}

</ol>

<li>After the image is burnt, it will automatically start the Linux system in SPIFlash+PCIe SSD. If it does not start normally, please power on and try again.</li></ol></li></ol>

~~~~

=== The method of using the dd command to burn ===

<li>First, you need to prepare an NVMe SSD. The PCIe supported by the M.2 slot of the development board is PCIe2.0x1, and the theoretical maximum speed is 500MB/s. PCIe3.0 and PCIe4.0 NVMe SSDs are also available, but the highest speed is only PCIe2.0x1.

<li>The M.2 2230 SSD is as follows</li>~~</ol></li></ol>~~ ~~[[File:pi3b-img73.png|158x114px]]~~

[[File:pi3b-img73.png]]

</ol>

<li>The M.2 2242 SSD is as follows</li>~~</ol>~~ ~~[[File:pi3b-img74.png|192x104px]]~~

[[File:pi3b-img74.png]]

</ol>

</li></ol>

<li>Then insert the NVMe SSD into the M.2 PCIe interface of the development board and fix it</li>~~</ol>~~ ~~[[File:pi3b-img75.png|283x63px]]~~

[[File:pi3b-img75.png]]

</ol>

<li>The position of SPI Flash on the development board is shown in the figure below, no other settings are required before starting to burn</li>~~</ol>~~ ~~[[File:pi3b-img76.png|261x198px]]~~

[[File:pi3b-img76.png]]

</ol>

<li>Burning the Linux image to SPIFlash+NVMe SSD requires 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 [[\lOrange Pi 3B#Method of burning Linux image to TF card based on Windows PC|'''Method of burning Linux image to TF card based on Windows PC''']] and [[\lOrange Pi 3B#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 using the TF card to start the Linux system, we first burn the u-boot image into the SPI Flash

<li>Run nand-sata-install first, '''ordinary users remember to add sudo permission'''</li~~></ol></li></ol~~>

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

|-

|

orangepi@orangepi:~$ '''sudo nand-sata-install'''

|}</ol>

<li>Then select '''7 Install/Update the bootloader on SPI Flash'''</li~~></ol~~>

[[File:pi3b-img86.png~~|355x174px|IMG_256~~]]

</div></ol>

<li>Then select '''<Yes>'''</li~~></ol~~>

[[File:pi3b-img87.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~~></ol~~>

[[File:pi3b-img88.png~~|358x161px|IMG_256~~]]

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

<li>Then upload the Linux image file (Debian or Ubuntu image downloaded from the official website) to the TF card. For the method of uploading the Linux image file to the development board, please refer to the description in the section of [[\lOrange Pi 3B#The method of uploading files to the Linux system of the development board|'''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>~~</ol>~~{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''cd /home/orangepi/Desktop'''

Orangepi3b_x.x.x_debian_bullseye_desktop_xfce_Linux5.10.160.img

|}

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

|-

|

<big>'''How to enter the command line of the development board Linux system?'''

'''1. For the method of using the serial port to log in to the terminal, please refer to the instructions in the section on [[Orange Pi 3B#How to ~~enter~~ use the ~~command line of~~ debugging serial port|how to use the ~~development board Linux system?~~debugging serial port]].'''

# '''~~For the method of using the serial port to log in to the terminal, please refer to the instructions in the section on [[\l|how to use the debugging serial port]]~~2.~~'''# '''~~Use ssh to remotely log in to the Linux system, please refer to the instructions in the section of [[\lOrange Pi 3B#SSH remote login development board|SSH remote login to the development board]]~~.'''# '''If HDMI, LCD and other display screens are connected, you can open a command line terminal on the desktop~~.'''

'''3. If HDMI, LCD and other display screens are connected, you can open a command line terminal on the desktop.'''</big>

|}

</ol>

<li>Next, let's confirm that the NVMe SSD has been recognized by the development board's Linux. If the NVMe SSD is recognized normally, use the '''sudo fdisk -l''' command to see '''nvme''' related information</li~~></ol~~>

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

|-

|

orangepi@orangepi:~/Desktop$ '''sudo fdisk -l | grep "nvme0n1"'''

Disk /dev/nvme0n1: 1.86 TiB, 2048408248320 bytes, 4000797360 sectors

|}

Use the '''lspci''' command to see an NVMe-related PCI device

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

|-

|

orangepi@orangepi:~/Desktop$ '''lspci'''

01:00.0 Non-Volatile memory controller: Realtek Semiconductor Co., Ltd. Device 5765 (rev 01)

|}</ol>

<li>Then we can use the dd command to clear the NVMe SSD (optional)</li~~></ol~~>

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

|-

|

orangepi@orangepi3b:~/Desktop$ '''sudo dd bs=1M if=/dev/zero of=/dev/nvme0n1 count=2000 status=progress'''

orangepi@orangepi3b:~/Desktop$ '''sudo sync'''

|}</ol>

<li>Then you can use the dd command to burn the Linux image of the development board to the NVMe SSD</li~~></ol~~>

<li>In the following command, the '''if= ''' parameter is followed by the full ~~>~~ path where the Linux image is stored + the name of the Linux image ~~>~~ (such as '''the name of /home/orangepi/Desktop/Linux image'''). ~~>~~ Because we have entered the path of the Linux image above, we only ~~>~~ need to fill in the name of the Linux image.</li><li>Please do not copy the Linux image name in the following command, ~~>~~ but replace it with the actual image name (because the version ~~>~~ number of the image may be updated).</li~~></ol~~>

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

|-

|

'''sudo dd bs=1M if=Orangepi3b_x.x.x_debian_bullseye_desktop_xfce_Linux5.10.160.img of=/dev/nvme0n1 status=progress'''

'''sudo''' '''sync'''

|}

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

|-

|

<big>'''Note, if you upload a .7z or .xz or .gz Linux image compressed file, please remember to decompress it before using the dd command to burn.'''

~~'''Note, if you upload a .7z or .xz or .gz Linux image compressed file, please remember to decompress it before using the dd command to burn.'''~~

~~'''The detailed description of all parameters of the dd command and more usage can be viewed by executing the man dd command in the Linux system.'''~~

'''The detailed description of all parameters of the dd command and more usage can be viewed by executing the man dd command in the Linux system.'''</big>

|}

</ol>

<li>After successfully burning the Linux image of the development board to the NVMe SSD, you can use the poweroff command to shut down. Then please pull out the TF card, and then short press the power button to turn on, then the Linux system in SPIFlash+NVMe SSD will be started.</li>

<li>After starting the system in the NVMe SSD, use the '''df -h''' command to see the actual hard disk capacity

<li>128GB NVMe SSD</li> {| class="wikitable" style="width:800px;"|-|orangepi@orangepi:~$ '''df -h'''Filesystem Size Used AvailUse% Mounted on udev3.8G 8.0K 3.8G 1% /dev tmpfs 769M 1.4M 768M 1% /run '''/dev/nvme0n1p2''''''118G ''''''5.8G ''''''111G ''''''5% /''' tmpfs 3.8G 03.8G 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 3.8G 16K 3.8G 1% /tmp '''/dev/nvme0n1p1''''''256M ''''''90M ''''''166M ''''''36% /boot''' /dev/zram1194M 9.9M 170M 6% /var/log tmpfs 769M 60K 769M 1% /run/user/1000 tmpfs 769M 48K 769M 1% /run/user/0 |}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>2TB NVMe SSD</li>{| class="wikitable" style="width:800px;"|-|orangepi@orangepi:~$ '''df -h'''Filesystem Size Used AvailUse% Mounted on udev3.8G 8.0K 3.8G 1% /dev tmpfs 769M 1.4M 768M 1% /run '''/dev/nvme0n1p2''''''1.9T ''''''4.1G ''''''1.8T ''''''1% /''' tmpfs 3.8G 03.8G 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/zram23.7G 76K 3.5G 1% /tmp '''/dev/nvme0n1p1''''''256M ''''''90M ''''''166M ''''''36% /boot''' /dev/zram1194M 9.9M 170M 6% /var/log tmpfs 769M 60K 769M 1% /run/user/1000 tmpfs 769M 48K 769M 1% /run/user/0 |}</ol>

</li></ol>

<li>When the same system is programmed in the TF card and NVMe SSD, '''if both the TF card and NVMe SSD are inserted into the development board, then power on and start the development board, and u-boot will give priority to starting the system in the TF card.''' However, since the systems in the TF card and the NVMe SSD are exactly the same, the UUIDs of the /'''boot''' partition and the '''rootfs''' partition in the two storage devices are also the same, which may cause the partition in the NVMe SSD to be loaded when the TF card starts. Running the script below resolves this issue.</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''df sudo fix_mmc_ssd.sh'''|}{| class="wikitable" style="background-hcolor:#ffffdc;width:800px;" |-| <big>'''Exactly the same system means that the image name is exactly the same. Even if they are all Debian11 systems, the versions are different.'''</big>|}</ol>

~~Filesystem Size Used Avail Use% Mounted on~~=== How to use balenaEtcher software to burn ===

~~udev 3~~<ol style="list-style-type: decimal;"><li>First, you need to prepare an NVMe SSD.~~8G 8~~The PCIe supported by the M.~~0K 3~~2 slot of the development board is PCIe2.~~8G 1%~~ 0x1, and the theoretical maximum speed is 500MB/~~dev~~s. PCIe3.0 and PCIe4.0 NVMe SSDs are also available, but the highest speed is only PCIe2.0x1.<ol style="list-style-type: lower-alpha;"><li>The M.2 2230 SSD is as follows</li>

~~tmpfs 769M 1~~[[File:pi3b-img73.~~4M 768M 1%~~ png]]</~~run~~ol><ol start="2" style="list-style-type: lower-alpha;"><li>The M.2 2242 SSD is as follows</li>

~~'''~~[[File:pi3b-img74.png]]</ol></~~dev~~li></~~nvme0n1p2 118G 5~~ol><ol start="2" style="list-style-type: decimal;"><li>Then insert the NVMe SSD into the M.~~8G 111G 5%~~ 2 PCIe interface of the development board and fix it</~~'''~~li>

~~tmpfs 3~~[[File:pi3b-img75.~~8G 0~~ png]]</ol><ol start="3~~.8G 0% /dev~~" style="list-style-type: decimal;"><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</~~shm~~li>

~~tmpfs 5~~[[File:pi3b-img76.0M png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Burning the Linux image to SPIFlash+NVMe SSD requires 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.~~0K 5~~For the method of burning the Linux image to the TF card, please refer to the instructions in the two sections of [[Orange Pi 3B#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 3B#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''']].~~0M 1%~~ </li><li>After booting into the Linux system in the TF card, please confirm that the NVMe SSD has been properly recognized by the Linux of the development board. If the NVMe SSD is recognized normally, use the '''sudo fdisk -l''' command to see '''nvme''' related information</~~run~~li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~/~~lock~~Desktop$ '''sudo fdisk -l | grep "nvme0n1"'''

~~tmpfs 3.8G 16K 3~~Disk /dev/nvme0n1: 1.~~8G 1% /tmp~~86 TiB, 2048408248320 bytes, 4000797360 sectors|}

Use the '''~~/dev/nvme0n1p1 256M 90M 166M 36% /boot~~lspci'''command to see an NVMe-related PCI device

~~/dev/zram1 194M 9.9M 170M 6% /var/log~~{| class="wikitable" style="width:800px;" |-| ~~tmpfs 769M 60K 769M 1% /run/user~~orangepi@orangepi:~/~~1000~~Desktop$ '''lspci'''

~~tmpfs 769M 48K 769M 1% /run/user/~~0:00.0 PCI bridge: Fuzhou Rockchip Electronics Co., Ltd Device 3566 (rev 01)

01:00.0 Non-Volatile memory controller: Realtek Semiconductor Co., Ltd. Device 5765 (rev 01)|}</ol><ol start="26" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~2TB NVMe SSD~~The balenaEtcher has been pre-installed in the Linux image, and the opening method is as follows:</li~~></ol~~>

~~orangepi@orangepi:~$ '''df -h'''~~<div class="figure">

~~Filesystem Size Used Avail Use% Mounted on~~[[File:pi3b-img89.png]]

~~udev 3~~</div>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If it is not pre-installed, for [[Orange Pi 3B#The method of downloading and installing the balenaEtcher version of arm64|how to download and install the arm64 version of balenaEtcher]], please refer to the instructions in the section on how to download and install the arm64 version of balenaEtcher.~~8G 8.0K 3.8G 1%~~ '''</big>|}</ol><ol start="7" style="list-style-type: decimal;"><li>The interface after balenaEtcher is opened is as follows:</~~dev~~li>

~~tmpfs 769M 1.4M 768M 1% /run~~<div class="figure">

~~'''/dev/nvme0n1p2 1~~[[File:pi3b-img90.~~9T 4.1G 1.8T 1% /'''~~png]]

~~tmpfs 3.8G 0 3.8G 0%~~ </~~dev~~div></~~shm~~ol><ol start="8" style="list-style-type: decimal;"><li>The method of using balenaEtcher to burn u-boot to the SPI Flash of the development board is as follows:<ol style="list-style-type: lower-alpha;"><li>First click on '''Flash from file'''</li>

~~tmpfs 5.0M 4.0K 5.0M 1% /run/lock~~<div class="figure">

~~/dev/zram2 3~~[[File:pi3b-img91.~~7G 76K 3.5G 1% /tmp~~png]]

</div></ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then enter the '''/~~dev~~usr/~~nvme0n1p1 256M 90M 166M 36%~~ lib/Linux-u-boot-legacy-orangepi3b_1.x.x_arm64''' directory, select '''rkspi_loader.img''', and click '''Open''' to open</li>

~~/dev/zram1 194M 15M 165M 9% /var/log~~<div class="figure">

~~tmpfs 769M 60K 769M 1% /run/user/1000~~[[File:pi3b-img92.png]]

~~tmpfs 769M 48K 769M 1%~~ </~~run~~div></~~user~~ol><ol start="3" style="list-style-type: lower-alpha;"><li>The interface after opening '''rkspi_loader.img''' is as follows:</0li>

[[File:pi3b-img93.png]]</ol><ol start="134" style="list-style-type: ~~decimal~~lower-alpha;"><li>When the same system is programmed in the TF card and NVMe SSD, '''if both the TF card and NVMe SSD are inserted into the development board, then power on and start the development board, and u-boot will give priority to starting the system in the TF card.''' However, since the systems in the TF card and the NVMe SSD are exactly the same, the UUIDs of the /'''boot''' partition and the Then click '''~~rootfs~~Select target''' ~~partition in the two storage devices are also the same, which may cause the partition in the NVMe SSD to be loaded when the TF card starts. Running the script below resolves this issue.~~</li~~></ol~~>

~~orangepi@orangepi:~$ '''sudo fix_mmc_ssd.sh'''~~<div class="figure">

~~'''Exactly the same system means that the image name is exactly the same~~[[File:pi3b-img94. ~~Even if they are all Debian11 systems, the versions are different.'''~~png]]

<~~span id~~/div></ol><ol start="5" style="~~how-to-use-balenaetcher~~list-~~software~~style-totype: lower-~~burn~~alpha;"><li>Then click '''Show 2 hidden''' to open more options for storage devices</~~span~~li>~~=== How to use balenaEtcher software to burn ===~~

<~~ol style~~div class="~~list-style-type: decimal;~~figure"><li>First, you need to prepare an NVMe SSD. The PCIe supported by the M.2 slot of the development board is PCIe2.0x1, and the theoretical maximum speed is 500MB/s. PCIe3.0 and PCIe4.0 NVMe SSDs are also available, but the highest speed is only PCIe2.0x1.~~<ol style="list-style-type: lower-alpha;"><li>The M.2 2230 SSD is as follows</li></ol></li></ol~~>

[[File:pi3b-~~img73~~img95.png~~|189x136px~~]]

</div></ol><ol start="26" style="list-style-type: lower-alpha;"><li>~~The M.2 2242 SSD is as follows~~Then select the device name of SPI Flash '''/dev/mtdblock0''', and click '''Select'''</li~~></ol~~>

~~[[File:pi3b-img74.png|238x129px]]~~<div class="figure">

~~<ol start="2" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Then insert the NVMe SSD into the M~~img96.~~2 PCIe interface of the development board and fix it</li></ol>~~png]]

~~[[File~~</div></ol><ol start="7" style="list-style-type:~~pi3b~~lower-~~img75.png|283x63px]]~~alpha;"><li>Then click '''Flash'''</li>

<~~ol start~~div class="3figure" ~~style="list-style-type: decimal;"><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></ol~~>

[[File:pi3b-~~img76~~img97.png~~|261x198px~~]]

</div></ol><ol start="48" style="list-style-type: ~~decimal~~lower-alpha;"><li>Burning the Linux image to SPIFlash+NVMe SSD requires 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 [[\l|''Then click '~~the method of burning the Linux image to the TF card based on the Windows PC~~''~~']] and [[\l|'''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~~Yes, ~~please confirm that the NVMe SSD has been properly recognized by the Linux of the development board. If the NVMe SSD is recognized normally, use the~~ I'm sure''~~sudo fdisk -l~~'~~'' command to see '''nvme''' related information~~</li~~></ol~~>

~~orangepi@orangepi:~/Desktop$ '''sudo fdisk -l | grep "nvme0n1"'''~~<div class="figure">

~~Disk /dev/nvme0n1~~[[File: 1pi3b-img98.~~86 TiB, 2048408248320 bytes, 4000797360 sectors~~png]]

~~Use~~ </div></ol><ol start="9" style="list-style-type: lower-alpha;"><li>Then enter the password '''~~lspci~~orangepi''' ~~command to see an NVMe~~of the development board Linux system, and it will start burning the u-~~related PCI device~~boot image into the SPI Flash</li>

~~orangepi@orangepi:~/Desktop$ '''lspci'''~~ ~~00:00.0 PCI bridge: Fuzhou Rockchip Electronics Co., Ltd Device 3566 (rev 01)~~<div class="figure">

01[[File:~~00.0 Non~~pi3b-~~Volatile memory controller: Realtek Semiconductor Co., Ltd~~img99. ~~Device 5765 (rev 01)~~png]]

</div></ol><ol start="610" style="list-style-type: ~~decimal~~lower-alpha;"><li>The ~~balenaEtcher has been pre-installed in the Linux image, and~~ display of the ~~opening method~~ burning process is as follows:</li~~></ol~~>

[[File:pi3b-~~img89~~img100.png~~|506x249px|IMG_256~~]]

</div>'''If it is not pre-installed, for [[\l|how to download and install the arm64 version of balenaEtcher]], please refer to the instructions in the section on how to download and install the arm64 version of balenaEtcher.'''</ol><ol start="711" style="list-style-type: ~~decimal~~lower-alpha;"><li>The ~~interface~~ display after ~~balenaEtcher is opened~~ burning is as follows:</li~~></ol~~>

[[File:pi3b-~~img90~~img101.png~~|406x207px|IMG_256~~]]

</div></ol></li></ol><ol start="89" style="list-style-type: decimal;"><li>The method of ~~using balenaEtcher~~ burning the Linux system in the TF card to ~~burn u-boot~~ the NVMe SSD (this method is equivalent to cloning the system in the ~~SPI Flash of~~ TF card to the ~~development board is as follows:~~NVMe SSD)

<li>First click on '''~~Flash from file~~Clone drive'''</li~~></ol></li></ol~~>

[[File:pi3b-~~img91~~img102.png~~|406x205px|IMG_256~~]]

</div></ol>

<li>Then ~~enter~~ select the device name of the TF card '''/~~usr~~dev/~~lib/Linux-u-boot-legacy-orangepi3b_1.x.x_arm64''' directory, select '''rkspi_loader.img~~mmcblk1'''~~, and click '''Open''' to open~~</li~~></ol~~>

[[File:pi3b-~~img92~~img103.png~~|563x110px|IMG_256~~]]

</div></ol>

<li>The interface after opening ~~'''rkspi_loader.img'''~~ the TF card is as follows:</li> <~~/ol~~div class="figure">

[[File:pi3b-~~img93~~img104.png~~|379x181px~~]]

</div></ol>

<li>Then click '''Select target'''</li~~></ol~~>

[[File:pi3b-img94.png~~|379x171px|IMG_256~~]]

</div></ol>

<li>Then click '''Show 2 hidden''' to open more options for storage devices</li~~></ol~~>

[[File:pi3b-img95.png~~|385x155px|IMG_256~~]]

</div></ol>

<li>Then select the device name of ~~SPI Flash~~ the NVMe SSD '''/dev/~~mtdblock0~~nvme0n1''', and click '''Select'''</li~~></ol~~>

~~<div class="figure">~~ [[File:pi3b-~~img96~~img105.png~~|389x264px|IMG_256~~]] </~~div~~ol>

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

[[File:pi3b-~~img97~~img106.png~~|394x268px|IMG_256~~]]

</div></ol>

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

[[File:pi3b-~~img98~~img107.png~~|396x269px|IMG_256~~]]

</div></ol><ol start="9" style="list-style-type: lower-~~roman~~alpha;"><li>Then enter the password ~~'''~~orangepi~~'''~~ of the Linux system on the development board ~~Linux system~~, and it will start burning the ~~u-boot~~ Linux image ~~into~~ to the ~~SPI Flash~~SSD</li~~></ol~~>

[[File:pi3b-~~img99~~img108.png~~|393x269px|IMG_256~~]]

</div></ol>

<li>The display of the burning process is as follows:</li>~~</ol>~~ [[File:pi3b-img109.png]]

[[File:pi3b-~~img100~~img110.png~~|397x272px|IMG_256~~]]

</div></ol>

<li>The display after burning is as follows:</li~~></ol~~>

~~<div class="figure">~~ [[File:pi3b-~~img101~~img111.png~~|395x225px|IMG_256~~]] </~~div~~ol><ol start="912" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~The method of burning the Linux system in the TF card~~ Then you need to expand the ~~NVMe SSD (this method is equivalent to cloning~~ capacity of the ~~system~~ rootfs partition in ~~the TF card to~~ the NVMe SSD). The steps are as follows:<ol style="list-style-type: ~~lower-alpha~~none;"><li>~~First click~~ a) Open '''~~Clone drive~~GParted'''first, if the system does not have Gparted pre-installed, please use the apt command to install it</lip>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt-get install -y gparted'''</olp>|}</li~~></ol~~>

[[File:pi3b-~~img102~~img112.png~~|386x204px|IMG_256~~]]

</div></ol><ol start="2" style="list-style-type: ~~lower-alpha~~none;"><li>b) Then ~~select~~ enter the ~~device name~~ password orangepi of the ~~TF card~~ Linux system, and click '''~~/dev/mmcblk1~~Authenticate'''</li~~></ol~~>

[[File:pi3b-img113.png]]<~~div class~~/ol><ol start="3" style="~~figure~~list-style-type: none;"><li>c) Then click '''Fix'''</li>

[[File:pi3b-~~img103~~img114.png~~|379x256px|IMG_256~~]] </~~div~~ol><ol start="34" style="list-style-type: ~~lower-alpha~~none;"><li>~~The interface after opening the TF card is as follows:~~d) Then select NVMe SSD</li~~></ol~~>

[[File:pi3b-~~img104~~img115.png~~|381x191px|IMG_256~~]]

</div></ol><ol start="45" style="list-style-type: ~~lower-alpha~~none;"><li>~~Then click '''Select target'''~~e) The display interface after selecting NVMe SSD is as follows:</li~~></ol~~>

[[File:pi3b-~~img94~~img116.png~~|379x171px|IMG_256~~]]

</div></ol><ol start="56" style="list-style-type: ~~lower-alpha~~none;"><li>f) Then select the '''/dev/nvme0n1p2''' partition, click the right button again, and then select '''~~Show 2 hidden~~Resize/Move''' ~~to open more options for storage devices~~</li~~></ol~~>

[[File:pi3b-~~img95~~img117.png~~|385x155px|IMG_256~~]]

</div></ol><ol start="67" style="list-style-type: ~~lower-alpha~~none;"><li>g) Then ~~select~~ drag the ~~device name of~~ capacity to the ~~NVMe SSD '''/dev/nvme0n1''', and click '''Select'''~~maximum at the position shown in the figure below</li~~></ol~~>

[[File:pi3b-~~img105~~img118.png~~|386x264px~~]]</ol><ol start="8" style="list-style-type: none;"><li>h) Then click '''Resize/Move'''</li>

[[File:pi3b-img119.png]]</ol><ol ~~start="7"~~ style="list-style-type: ~~lower-alpha~~none;"><li>i) Then click the green '''~~Flash~~√'''in the position below</li~~></ol~~>

[[File:pi3b-img120.png]]<~~div class~~/ol><ol start="10" style="~~figure~~list-style-type: none;"><li>j) Then click '''Apply'''</li>

[[File:pi3b-~~img106~~img121.png~~|389x264px|IMG_256~~]]</ol><ol start="11" style="list-style-type: none;"><li>k) Then click '''Close''' to close</li>

[[File:pi3b-img122.png]]</~~div~~ol></li></ol><ol start="813" style="list-style-type: lower-alpha;"><li>~~Then click~~ At this point, you can use the '''sudo poweroff'''~~Yes~~command to shut down. Then please pull out the TF card, Iand then short press the power button to turn on, then the Linux system in SPIFlash+NVMe SSD will be started.</li></ol></li></ol><ol start="10" style="list-style-type: decimal;"><li>Step '~~m sure~~''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:<ol style="list-style-type: lower-alpha;"><li>Upload the Linux image file to the Linux system of the development board</li><li>Then use balenaEtcher to burn</olp></li>

[[File:pi3b-~~img107~~img123.png~~|392x268px|IMG_256~~]]

</div></ol><ol start="3" style="list-style-type: lower-~~roman~~alpha;"><li>~~Then enter~~ '''After using this method to burn the ~~password orangepi of~~ image, there is no need to manually expand the ~~Linux system on the development board~~capacity, and it will ~~start burning~~ automatically expand the ~~Linux image to~~ capacity at the ~~SSD~~first startup.'''</li></ol></li></ol><~~div class~~span id="~~figure~~how-to-burn-android-image-to-tf-card">

~~[[File:pi3b-img108.png|390x267px|IMG_256]]~~== How to burn Android image to TF card ==

<~~/div><ol start~~span id="~~10" style="list~~method-of-burning-android-image-to-tf-card-through-~~style~~usb2.0-~~type: lower~~burning-~~alpha;~~port"><li/span>~~The display~~ === Method of ~~the~~ burning ~~process is as follows:</li></ol>~~Android image to TF card through USB2.0 burning port ===

~~[[File:pi3b~~# 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# You also need to prepare a good quality USB2.0 male-~~img109.png|393x212px]]~~to-male data cable

::[[File:pi3b-~~img110~~img16.png~~|395x205px|IMG_256~~]]

</div>

<ol start="113" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The display after~~ Then download Rockchip driver '''DriverAssitant_v5.12.zip''' and burning ~~is as follows~~tool '''RKDevTool_Release_v3.15.zip''' from [http:</~~li><~~/~~ol>~~ ~~[[File:pi3b~~www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-~~img111~~3B.~~png|398x227px~~html '''Orange Pi's data download page''']] <~~ol start="12" style="list-style-type: lower-alpha;"~~/p></li><li>Then ~~you need to expand~~ download the ~~capacity of the rootfs partition in the NVMe SSD~~Android image from [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi's download page''']. ~~The steps are as follows:~~

<li>~~Open '''GParted''' first~~After opening the download link of the Android image, if you can see the ~~system does not have Gparted pre-installed~~following two types of Android images, please ~~use~~ select the image in the ~~apt command to install itorangepi@orangepi:~$~~ '''~~sudo apt-get install -y gparted~~TF card and eMMC startup image'''~~</li></ol>~~folder to download</li~~></ol~~>

[[File:pi3b-~~img112~~img124.png~~|576x215px|IMG_256~~]]

</div>

</ol>

<li>~~Then enter~~ After entering the ~~password orangepi of the Linux system, and click~~ '''~~Authenticate~~TF card and eMMC startup image'''folder, you can see the following two images, the difference between them is:<ol style="list-style-type: none;"><li>a) The first image is dedicated to HDMI display and supports 4K display. If you don't use LCD screen, please download the image without lcd</olp></li><li>b) If you want to use lcd screen, please choose image with lcd</li>

[[File:pi3b-~~img113~~img125.png~~|356x173px~~]]</ol></li></ol></li></ol><ol start="5" style="list-style-type: decimal;"><li>Then use the 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 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:pi3b-img31.png]]</ol><ol start="37" style="list-style-type: decimal;" ><li>After opening '''DriverInstall.exe''', the steps to install the Rockchip driver are as follows<ol style="list-style-type: lower-alpha;"><li>~~Then click~~ Click the "'''~~Fix~~Driver Installation'''" button</li~~></ol~~>

[[File:pi3b-~~img114~~img32.png~~|355x261px~~]]</ol><ol start="2" style="list-style-type: lower-alpha;"><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.</li>

[[File:pi3b-img33.png]]</ol></li></ol><ol start="48" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~select NVMe SSD~~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~~></ol~~>

[[File:pi3b-img34.png]]<~~div class~~/ol><ol start="9" style="~~figure~~list-style-type: decimal;"><li>After opening the '''RKDevTool''' burning tool, because the computer has not connected to the development board through the USB2.0 male-to-male data cable at this time, the lower left corner will prompt "'''No device found'''"</li>

[[File:pi3b-~~img115~~img35.png~~|452x187px|IMG_256~~]] </~~div~~ol><ol start="510" style="list-style-type: decimal;"><li>Then start burning the Android image to the TF card<ol style="list-style-type: lower-alpha;"><li>First, connect the development board to the Windows computer through the USB2.0 male-to-male data cable. The ~~display~~ position of the USB2.0 programming interface ~~after selecting NVMe SSD~~ of the development board is ~~as follows:~~shown in the figure below</li~~></ol~~>

[[File:pi3b-~~img116~~img36.png~~|451x187px|IMG_256~~]]

</div></ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then make sure that the development board is not inserted into the TF card and 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:</li> [[File:pi3b-img37.png]]</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then connect the power supply of the Type-C interface to the development board, and power on</li> [[File:pi3b-img38.png]]</ol><ol start="5" style="list-style-type: lower-alpha;"><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:pi3b-img39.png]]</ol>

<li>Then insert the TF card into the development board</li><li>Then please select ~~the~~ '''advanced features'''</~~dev~~p>[[File:pi3b-img126.png]]</~~nvme0n1p2~~li><li>Then click the position shown in the figure below[[File:pi3b-img127.png]]</li><li>Then select ''' ~~partition, click~~ rk3566_MiniLoaderAll.bin''' in the ~~right button again, and then select~~ '''~~Resize/Move~~MiniLoader'''folder downloaded earlier, and click to open</lip></olli>

[[File:pi3b-~~img117~~img68.png~~|448x345px|IMG_256~~]] </div></ol><ol start="10" style="list-style-type: lower-alpha;"><li>Then click '''download'''[[File:pi3b-img128.png]]</li><li>The display after downloading '''rk3566_MiniLoaderAll.bin''' is shown in the figure below[[File:pi3b-img129.png]]</li><li>Then select the storage device as '''SD''', and then click '''Switch Storage'''<div class="figure">

~~</div><ol start="7" style="list-style-type~~[[File: ~~lower~~pi3b-~~alpha;"><li>Then drag the capacity to the maximum at the position shown in the figure below</li></ol>~~img130.png]]

~~[[File:pi3b-img118.png|339x210px]]~~</div></li><li>The display of successful switching is shown in the figure below</li>

<~~ol start~~div class="8figure" ~~style="list-style-type: lower-alpha;"><li>Then click '''Resize/Move'''</li></ol~~>

[[File:pi3b-~~img119~~img131.png~~|339x212px~~]]

</div></ol ><ol start="14" style="list-style-type: lower-~~roman~~alpha;"><li>Then click the ~~green~~ "'''√Upgrade Firmware''' in " column of the ~~position below~~burning tool</li~~></ol~~>

[[File:pi3b-~~img120~~img132.png~~|425x166px~~]]</ol><ol start="15" style="list-style-type: lower-alpha;"><li>Then click the "'''Firmware'''" button to select the path of the Android image that needs to be burned</li>

[[File:pi3b-img133.png]]</ol><ol start="1016" style="list-style-type: lower-alpha;"><li>~~Then~~ Finally, click the "'''~~Apply~~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.</li~~></ol~~>

~~[[File:pi3b-img121.png|378x276px]]~~<div class="figure">

~~<ol start="11" style="list-style-type~~[[File: ~~lower~~pi3b-~~alpha;"><li>Then click '''Close''' to close</li></ol>~~img134.png]]

~~[[File:pi3b~~</div></ol></li></ol>

~~<ol start~~=~~"13" style~~=~~"list-style-type: lower-alpha;"><li>At this point, you can~~ = How to use ~~the '''sudo poweroff''' command~~ SDDiskTool to burn Android image to ~~shut down. Then please pull out the~~ TF card~~, and then short press the power button to turn on, then the Linux system in SPIFlash+NVMe SSD will be started.</li></ol>~~===

~~~~<ol ~~start="10"~~ style="list-style-type: decimal;"><li>~~Step~~ 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</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-3B.html '''Orange Pi data download page'9)''], ' ~~is to clone~~ ''please make sure that the ~~system in~~ version of the ~~TF card to~~ SDDiskTool tool is the ~~NMVe SSD~~latest v1.72. ~~We can also directly burn~~ '''</li><li>Then download the ~~Linux~~ Android11 image ~~file to~~ from the ~~NVMe SSD~~[http://www.orangepi. ~~Here are the steps:~~org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page''']

<li>~~Upload~~ After opening the download link of the ~~Linux~~ Android image ~~file to~~ , you can see the ~~Linux system~~ following two types of Android images, please select the image in the ~~development board</li><li>Then use balenaEtcher~~ '''TF card and eMMC startup image''' folder to ~~burn</li></ol>~~download</li~~></ol~~>

[[File:pi3b-~~img123~~img124.png~~|529x333px|图片1~~]]

</div></ol><ol start="32" style="list-style-type: lower-alpha;"><li>After entering the '''~~After using this method to burn the~~ TF card and eMMC boot image''' folder, ~~there is no need to manually expand~~ you can see the ~~capacity~~following two images, ~~and it will automatically expand~~ the ~~capacity at the first startup.'''~~difference between them is:</li~~></ol~~>

<~~span id~~ol style="~~how~~list-~~to-burn-android~~style-type: none;"><li>a) The image without lcd is specially used for HDMI display and supports 4K display. If you do not use the LCD screen, please download the image~~-to-tf-card"~~without lcd</~~span~~li>~~== How~~ <li>b) If you want to ~~burn Android~~ use LCD screen, please choose image ~~to TF card ==~~with lcd</li>

~~=== Method of burning Android image to TF card through USB2.0 burning port ===~~ ~~# 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# You also need to prepare a good quality USB2.0 male-to-male data cable~~ ~~<div class="figure">~~ [[File:pi3b-~~img16~~img125.png~~|141x138px|D6BB9058-CDC3-42d7-A7FC-FBF630D886B7]]~~ ~~</div><ol start="3" style="list-style-type: decimal;">~~<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-3B.html '''Orange Pi's data download page''']~~</li><li>Then download the Android image from [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi's download page'''~~]~~.<ol style="list-style-type: lower-alpha;">~~<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></ol>

</li></ol>

~~<div class="figure">~~

~~[[File:pi3b-img124.png|340x108px|e6986fc9c8fc078e8cb6a9c39b76fb8]]~~

~~</div>~~

~~<ol start="2" style="list-style-type: lower-alpha;">~~

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

~~<ol style="list-style-type: lower-alpha;">~~

~~<li>The first image is dedicated to HDMI display and supports 4K 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></ol>~~

</li></ol>

~~[[File:pi3b-img125.png|264x58px]]~~

<li>Then use ~~the~~ 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 ~~the~~ decompression software to decompress '''~~DriverAssitant_v5~~SDDiskTool_v1.1272.zip''', ~~and then~~ this software does not need to be installed, just find ~~the~~ '''~~DriverInstall~~SD_Firmware_Tool.exe''' ~~executable file~~ in the decompressed folder and open it</li>~~</ol>~~ ~~[[File:pi3b-img31.png|575x169px]]~~

[[File:pi3b-img135.png]]

</ol>

<li~~><p~~>After opening '''~~DriverInstall.exe~~SDDiskTool''', if the ~~steps to install~~ TF card is recognized normally, the ~~Rockchip driver are as follows<ol style="list-style-type: lower-alpha;"><li>Click~~ inserted disk device will be displayed in the "'''~~Driver Installation~~Select Removable Disk Device'''" ~~button</li></ol></li></ol>~~ ~~[[File:pi3b-img32~~column.~~png|300x157px]]~~ '''<~~ol start="2"~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">Please make sure that the displayed disk device is consistent with the drive letter of the TF card you want to burn<li/span>~~After waiting for a period of time, a pop-up window will prompt "~~'''~~The driver~~ , if there is ~~installed successfully'''"~~no display, ~~and then click~~ you can try to unplug the ~~"'''OK'''" button.~~TF card</li>~~</ol>~~ ~~[[File:pi3b-img33.png|315x164px]]~~

[[File:pi3b-img136.png]]

</ol>

<li>~~Then decompress~~ After confirming the drive letter, you can format the TF card first, click the '''restore disk button'~~RKDevTool_Release_v3.15.zip~~''in '''SDDiskTool, ~~this software does not need to be installed, just find~~ '''~~RKDevTool~~or use the '''SD Card Formatter''' in mentioned above to format the ~~decompressed folder and open it~~TF card</li>~~</ol>~~ ~~[[File:pi3b-img34.png|454x134px]]~~

[[File:pi3b-img137.png]]

</ol>

<li>~~After opening the '''RKDevTool''' burning tool, because~~ Then start to write the ~~computer has not connected~~ Android image to the ~~development board through the USB2.0 male~~TF card<ol style="list-tostyle-~~male data cable at this time, the~~ type: lower ~~left corner will prompt~~ -alpha;"><li>First check "SD Boot"~~'''No device found'''~~in "Select Function Mode"</li><li>Then select the path of the Android image in the "Select to upgrade firmware" column</olli> ~~[[File:pi3b-img35.png|442x208px]]~~<li>Finally click the "Start Create" button to start burning the Android image to the TF card</li>

[[File:pi3b-img138.png]]

</ol>

</li></ol>

<li>~~Then start~~ After burning , you can exit the ~~Android image to~~ SDDiskTool software, and then you can pull out the TF card~~<ol style="list-style-type: lower-alpha;"><li>First, connect the development board to~~ from the ~~Windows~~ computer ~~through the USB2.0 male-to-male data cable. The position of the USB2.0 programming interface of~~ and insert it into the development board ~~is shown in the figure below~~to start</li~~></ol></li></ol~~>

[[File:pi3b-img139.png]]<~~div class~~/ol>

~~[[File:pi3b-img36.png|275x116px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\1691131157154(1).jpg1691131157154(1)]]~~== How to burn Android image to eMMC ==

~~</div><ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~Then make sure that~~ '''Note, after burning the ~~development board is not inserted~~ image into eMMC, if the ~~TF card and not connected to~~ test finds that it cannot be started, please clear the ~~power supply</li><li>Then press~~ SPIFlash and ~~hold~~ try again. For the ~~MaskROM button on the development board~~method of clearing SPIFlash, please refer to [[Orange Pi 3B#Using RKDevTool to clear SPIFlash|the ~~position~~ method of ~~the MaskROM button on the development board is shown in the figure below:~~using RKDevTool to clear SPIFlash]].'''</~~p></li></ol~~big>|}

~~[[File:pi3b~~=== Method of burning Android image into eMMC through USB2.~~png|289x100px]]~~0 burning port ===

~~<ol start~~{| class="4wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~Then connect the power supply of the Type-C interface to~~ '''Note that all the ~~development board, and power~~ following operations are performed ona Windows computer.'''</~~li></ol~~big>|}

~~[[File~~<ol style="list-style-type:~~pi3b-img38~~decimal;"><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.~~png|305x94px]]~~The eMMC module and the method of plugging into the development board are as follows:</li>

~~<ol start="5" style="list-style~~[[File:pi3b-~~type~~img61.png|400px]] [[File: ~~lower~~pi3b-~~alpha;">~~<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></ol>img62.png|400px]]

[[File:pi3b-~~img39~~img63.png|~~457x215px~~800px]]</ol><ol start="62" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then insert the TF card into the development board</li><li>Then please select '''advanced features'''[[File:pi3b-img126~~You also need to prepare a good quality USB2.~~png|458x138px]]</li><li>Then click the position shown in the figure below[[File:pi3b~~0 male-~~img127.png|459x216px]]</li><li>Then select '''rk3566_MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and click~~ to ~~open~~-male data cable</li~~></ol~~>

[[File:pi3b-~~img68~~img16.png~~|459x216px|SIS5H0S2@F5M2D(6ANZEUPG~~]]

</div></ol><ol start="103" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~click~~ download Rockchip driver '''DriverAssitant_v5.12.zip''' and burning tool '''~~download~~RKDevTool_Release_v3.15.zip'''~~~~from [~~[File~~http:~~pi3b-img128~~//www.orangepi.~~png|472x222px]]<~~org/html/hardWare/computerAndMicrocontrollers/~~p><~~service-and-support/~~li><li>The display after downloading~~ Orange-Pi-3B.html '''Orange Pi'~~rk3566_MiniLoaderAll.bin~~s data download page''' ~~is shown in the figure below[[File:pi3b-img129.png|474x227px]~~]</li><li>Then ~~select~~ download the ~~storage device as~~ Android image from '''~~SD''',~~ [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and ~~then click~~ -support/Orange-Pi-3B.html Orange Pi'~~''Switch Storage~~s download page].'''<~~div class~~ol style="~~figure">~~ ~~[[File~~list-style-type:~~pi3b~~lower-~~img130.png|477x222px|D~T2CO%X~K2@ELR98)BVP~2]]~~ ~~</div></li~~alpha;"><li>~~The display~~ After opening the download link of the Android image, you can see the following two types of ~~successful switching is shown~~ Android images, please select the image in the ~~figure below~~'''TF card and eMMC startup image folder''' to download</li~~></ol~~>

[[File:pi3b-~~img131~~img124.png~~|474x223px|QFVLTK~19N32OK2UGH{D{AK~~]]

</div></ol><ol start="142" style="list-style-type: lower-alpha;"><li>~~Then click~~ After entering the ~~"~~'''~~Upgrade Firmware~~TF card and eMMC startup image folder'''~~&quot~~, you can see the following two images, the difference between them is<ol style="list-style-type: none; ~~column of~~ "><li>a) The first image is dedicated to HDMI display and supports 4K display. If you don't use LCD screen, please download the ~~burning tool~~image without lcd</li><li>b) If you want to use lcd screen, please choose image with lcd</olp></li>

[[File:pi3b-~~img132~~img125.png~~|477x224px~~]]</ol></li></ol></li></ol><ol start="5" style="list-style-type: decimal;"><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 '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>

[[File:pi3b-img31.png]]</ol><ol start="157" style="list-style-type: decimal;"><li>After opening '''DriverInstall.exe''', the steps to install the Rockchip driver are as follows<ol style="list-style-type: lower-alpha;"><li>~~Then click~~ Click the "'''~~Firmware~~Driver Installation'''" button ~~to select the path of the Android image that needs to be burned~~</li~~></ol~~>

[[File:pi3b-~~img133~~img32.png~~|444x209px~~]]</ol><ol start="2" style="list-style-type: lower-alpha;"><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:pi3b-img33.png]]</ol></li></ol><ol start="168" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Finally, click the "~~Then decompress '''~~Upgrade~~RKDevTool_Release_v3.15.zip'''~~" button~~ , this software does not need to ~~start burning~~be installed, ~~and the log during the burning process is shown~~ just find '''RKDevTool''' in the ~~figure below. After burning is completed, the Android system will start automatically.~~decompressed folder and open it</li~~></ol~~>

[[File:pi3b-img34.png]]<~~div class~~/ol><ol start="9" style="~~figure~~list-style-type: decimal;"><li>After opening the '''RKDevTool''' burning tool, because the computer is not connected to the development board through the USB2.0 male-to-male data cable at this time, the lower left corner will prompt "'''No device found'''"</li>

[[File:pi3b-~~img134~~img35.png~~|455x214px|GO~ZSPN`B~~]~~JCQM`@_9UU8[R~~]] </~~div~~ol><~~span id~~ol start="~~how-to-use-sddisktool-to-burn-android-image-to-tf-card~~10"~~>=== How to use SDDiskTool to burn Android image to TF card ===~~ ~~<ol~~ style="list-style-type: decimal;">~~<li>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</li~~><li>Then ~~use~~ start burning the ~~card reader to insert the TF card~~ Android image 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-3B.html '''Orange Pi data download page'''], '''please make sure that the version of the SDDiskTool tool is the latest v1.72.'''</li>~~<li>Then download '''the Android11 image from the Orange Pi download''' '''page'''~~eMMC

<li>~~After opening~~ First, connect the development board to the Windows computer through the ~~download link~~ USB2.0 male-to-male data cable. The position of the ~~Android image, you can see the following two types~~ USB2.0 programming interface of ~~Android images, please select~~ the ~~image~~ development board is shown in the ~~'''TF card and eMMC startup image''' folder to download</li></ol>~~figure below</li~~></ol~~>

~~<blockquote>~~<div class="figure">

[[File:pi3b-~~img124~~img36.png~~|340x108px|e6986fc9c8fc078e8cb6a9c39b76fb8~~]]

</div></~~blockquote~~ol>

<li>~~After entering~~ Then make sure that the development board is not inserted into the ~~'''~~TF card and ~~eMMC boot image''' folder~~not connected to the power supply</li><li>Then press and hold the MaskROM button on the development board, ~~you can see~~ the ~~following two images,~~ position of the MaskROM button on the ~~difference between them~~ development board isshown in the figure below:</lip></olli>

[[File:pi3b-img37.png]]<~~!-- --~~/ol><ol start="4" style="list-style-type: lower-alpha;"><li>~~The image without lcd is specially used for HDMI display and supports 4K display. If you do not use~~ Then connect the ~~LCD screen, please download~~ power supply of the ~~image without lcd</li><li>If you want~~ Type-C interface to ~~use LCD screen, please choose image with lcd~~the development board</li~~></ol~~>

[[File:pi3b-~~img125~~img38.png~~|281x62px~~]]</ol><ol start="5" style="list-style-type: lower-alpha;"><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'''"[[File:pi3b-img39.png]]</li><li>Then please select '''Advanced Features'''[[File:pi3b-img126.png]]</li><li>Then click the position shown in the figure below[[File:pi3b-img127.png]]</li></ol>

<ol start="58" style="list-style-type: ~~decimal~~lower-alpha;"><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~~ Select '''~~SD_Firmware_Tool~~rk3566_MiniLoaderAll.~~exe~~bin''' in the ~~decompressed~~ MiniLoader folder downloaded earlier, and click to open ~~it~~.</li~~></ol~~>

~~[[File:pi3b-img135.png|415x99px]]~~<div class="figure">

~~<ol start="7" style="list~~[[File:pi3b-~~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~~img68. ~~P'''lease 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></ol>~~png]]

</div></ol><ol start="9" style="list-style-type: lower-alpha;"><li>Then click '''Download'''[[File:pi3b-img128.png]]</li><li>The display after downloading '''MiniLoaderAll.bin''' is shown in the figure below[[File:pi3b-img140.png]]</li><li>Then select the storage device as '''EMMC''', and then click Switch '''Storage'''[[File:pi3b-~~img136~~img141.png~~|267x228px~~]]</li><li>The display of successful switching is shown in the figure below</li>

[[File:pi3b-img142.png]]</ol><ol start="813" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~After confirming the drive letter, you can format the TF card first,~~ Then click the "'''~~restore disk button~~Upgrade Firmware''' ~~in '''SDDiskTool,''' or use~~ " column of the ~~'''SD Card Formatter''' mentioned above to format the TF card~~burning tool</li~~></ol~~>

[[File:pi3b-~~img137~~img132.png~~|264x226px~~]]</ol><ol start="14" style="list-style-type: lower-alpha;"><li>Then click the "'''Firmware'''" button to select the path of the Android image that needs to be burned</li>

~~<ol start="9" style="list~~[[File:pi3b-~~style-type: decimal;">~~img133.png]]~~<li>Then start to write the Android image to the TF card~~</pol><ol start="15" style="list-style-type: lower-alpha;"><li~~>First check "SD Boot" in "Select Function Mode"</li><li>Then select the path of the Android image in the "Select to upgrade firmware" column</li><li><p~~>Finally , click the "~~Start Create~~'''Upgrade'''" button to start burning , and the log during the burning process is shown in the figure below. After burning is completed, the Android ~~image to the TF card</li></ol>~~system will start automatically.</li~~></ol~~>

~~[[File:pi3b-img138.png|286x242px]]~~<div class="figure">

~~<ol start="10" style="list~~[[File:pi3b-~~style-type: decimal;"><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></ol>~~img134.png]]

~~[[File:pi3b~~</div></ol></li></ol>

~~~~== How to burn ~~Android~~ Android11 image to into eMMC via TF card ===

{| 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~~ all the ~~SPIFlash and try again~~following operations are performed on a Windows computer. ~~For the method of clearing SPIFlash, please refer to~~''' ~~[[\l~~</big>|~~the method of using RKDevTool to clear SPIFlash]]'''.'''~~}

~~=== Method of burning Android image into eMMC through USB2.0 burning port ===~~ ~~'''Note that all the following operations are performed on a Windows computer.'''~~ ~~<ol style="list-style-type: decimal;"><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 eMMC module and the method of plugging into the development board are as follows:~~</li></ol>~~

::[[File:pi3b-img61.png|~~115x84px~~400px]] [[File:pi3b-img62.png|~~120x87px~~400px]]

::[[File:pi3b-img63.png|~~286x133px~~800px]]

<li>You also need to prepare a ~~good quality USB2~~TF card with 8GB or larger capacity.~~0 male-~~The transmission speed of the TF card must be class10 or above. It is recommended to~~-male data cable~~use a TF card of SanDisk and other brands</lip></olli> <~~div class="figure"~~li> ~~[[File:pi3b-img16.png|141x138px|D6BB9058-CDC3-42d7-A7FC-FBF630D886B7]]~~ Then use the card reader to insert the TF card into the computer</~~div~~p><~~ol start="3" style="list-style-type: decimal;"~~/li><li>Then download ~~Rockchip driver '''DriverAssitant_v5.12.zip''' and burning~~ the SDDiskTool programming tool ~~'''RKDevTool_Release_v3.15.zip'''~~ from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi's data download page'''], '''please make sure that the version of the SDDiskTool tool is the latest v1.72'''</li><li>Then download the Android image from ~~'''~~[http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi'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~~ '''the TF card and eMMC startup image folder''' to download</li~~></ol></li></ol~~>

[[File:pi3b-img124.png~~|340x108px|e6986fc9c8fc078e8cb6a9c39b76fb8~~]]

</div></ol>

<li>After entering ~~the~~ '''the TF card and eMMC ~~startup~~ boot image folder''', you can see the following ~~two~~ tow images, the difference between them is:<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) The first image is dedicated to HDMI display and supports 4K display. If you ~~don’t~~ don't use LCD screen, please download the image without lcd</li><li>b) If you want to use lcd screen, please choose image with lcd</li> [[File:pi3b-img125.png]]</ol></li></ol>

</li></ol>

<li>Then use the 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.exe''' in the decompressed folder and open it</li>

[[File:pi3b-~~img125~~img135.png~~|264x58px~~]]</ol><ol start="8" 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:pi3b-img136.png]]</ol><ol start="59" style="list-style-type: decimal;"><li>~~Then use decompression software to decompress~~ After confirming the ~~compressed package of the downloaded Android image. Among the decompressed files~~drive letter, you can format the ~~file ending with ".img" is the Android image file~~TF card first, ~~and~~ click the ~~size is more than 1GB</li><li>Then use decompression software to decompress~~ '''~~DriverAssitant_v5.12.zip~~restore disk button'''in SDDiskTool, ~~and then find~~ or use the '''~~DriverInstall.exe~~SD Card Formatter''' ~~executable file in~~ mentioned above to format the ~~decompressed folder and open it~~TF card</li~~></ol~~>

[[File:pi3b-~~img31~~img137.png~~|575x169px~~]]</ol><ol start="10" style="list-style-type: decimal;"><li>Then start to write the Android image into the TF card<ol style="list-style-type: lower-alpha;"><li>First confirm that the displayed drive letter is the drive letter corresponding to the TF card under "'''Select Removable Disk Device'''"</li><li>Then select "'''Firmware Upgrade'''" in "'''Select Function Mode'''"</li><li>Then select the path of the Android firmware in the "'''Select Upgrade Firmware'''" column</li><li>Finally click the "'''Start Create'''" button to start burning</li>

~~<ol start="7" style="list~~[[File:pi3b-~~style-type: decimal;"><li>After opening '''DriverInstall~~img143.~~exe''', the steps to install the Rockchip driver are as follows<ol style="list-style-type: lower-alpha;">~~png]]~~<li>Click the "'''Driver Installation'''" button</li>~~</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>

[[File:pi3b-img144.png]]

</ol>

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

[[File:pi3b-img145.png]]

</ol>

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

[[File:pi3b-img146.png]]

</ol>

~~[[File:pi3b-img32.png|300x157px]]~~== How to burn Android image to SPIFlash+NVMe SSD ==

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

|-

|

<big>'''Note that all the following operations are performed on a Windows computer.'''</big>

|}

<li>First, you need to prepare an NVMe SSD solid state drive

<li>The M.2 2230 SSD is as follows</li>

[[File:pi3b-img73.png]]

</ol>

<li>~~After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button~~The M.2 2242 SSD is as follows</li~~></ol~~>

[[File:pi3b-~~img33~~img74.png~~|315x164px~~]]</ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>Then insert the NVMe SSD into the M.2 PCIe interface of the development board and fix it</li>

[[File:pi3b-img75.png]]</ol><ol start="83" style="list-style-type: decimal;"><li>~~Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed~~The position of the SPI Flash on the development board is shown in the figure below, ~~just find '''RKDevTool''' in~~ no other settings are required before starting the ~~decompressed folder and open it~~programming</li~~></ol~~>

[[File:pi3b-~~img34~~img76.png~~|454x134px~~]]</ol><ol start="4" style="list-style-type: decimal;"><li>You also need to prepare a good quality USB2.0 male-to-male data cable</li>

<~~ol start~~div class="9figure" ~~style="list-style-type: decimal;">~~<li>After opening the '''RKDevTool''' burning tool, because the computer is not connected to the development board through the USB2.0 male-to-male data cable at this time, the lower left corner will prompt "'''No device found'''"</li></ol>

[[File:pi3b-~~img35~~img16.png~~|442x208px~~]]

</div></ol><ol start="105" style="list-style-type: decimal;"><li>Then ~~start~~ download Rockchip driver '''DriverAssitant_v5.12.zip''' and burning tool '''RKDevTool_Release_v3.15.zip''' from '''Orange Pi's data download page'''</li><li>Then download the ~~Android~~ image ~~into eMMC~~of Android11

<li>~~First, connect~~ After opening the ~~development board to~~ download link of the ~~Windows computer through the USB2.0 male-to-male data cable. The position of~~ Android image, you can see the ~~USB2.0 programming interface~~ following two types of Android images, please select the ~~development board is shown~~ image in the ~~figure below~~S'''PIFlash-NVME SSD boot image folder''' to download</li~~></ol></li></ol~~>

[[File:pi3b-~~img36~~img124.png~~|275x116px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\1691131157154(1).jpg1691131157154(1)~~]]

</div>

</ol>

<li>~~Then make sure that~~ After entering the ~~development board is not inserted into~~ '''SPIFlash-NVME SSD boot image folder''', you can see the ~~TF card and not connected to the power supply~~following two images. Their differences are:<~~/li~~ol style="list-style-type: none;"><li>~~Then press~~ a) The image without lcd is specially used for HDMI display and ~~hold~~ supports 4K display. If you do not use the ~~MaskROM button on the development board~~LCD screen, please download the ~~position of the MaskROM button on the development board is shown in the figure below:~~image without lcd</li><li>b) If you want to use LCD screen, please choose image with lcd</olli> [[File:pi3b-~~img37~~img147.png~~|289x100px~~]]</ol></li></ol></li></ol><ol start="7" style="list-style-type: decimal;"><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:pi3b-img31.png]]</ol><ol start="48" style="list-style-type: decimal;"><li>After opening '''DriverInstall.exe''', the steps to install the Rockchip driver are as follows<ol style="list-style-type: lower-alpha;"><li>~~Then connect~~ Click the ~~power supply of the Type~~"'''Driver Installation'''" button</li> [[File:pi3b-~~C interface to the development board~~img32.png]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button.</olli>

[[File:pi3b-~~img38~~img33.png~~|305x94px~~]]</ol></li></ol><ol start="9" style="list-style-type: decimal;"><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:pi3b-img34.png]]</ol><ol start="510" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~If the previous steps are successful, the development board will enter~~ After opening the '''~~MASKROM~~RKDevTool''' ~~mode~~ burning tool, because the computer is not connected to the development board through the USB2.0 male-to-male data cable at this time, ~~and~~ the ~~interface of the burning tool~~ lower left corner will prompt "'''No device found ~~a MASKROM device~~'''"~~[[File:pi3b-img39.png|457x215px]]</li><li>Then please select '''Advanced Features'''[[File:pi3b-img126.png|458x138px]]~~</li>~~<li>Then click the position shown in the figure below[[File:pi3b-img127.png|459x216px]]</li></ol~~>

[[File:pi3b-img35.png]]</ol><~~!--~~ ol start="11" style="list-style-type: decimal;"><li>Then start burning the Android image to SPIFlash+NVMe SSD

<li>~~Select '''rk3566_MiniLoaderAll~~First, connect the development board to the Windows computer through the USB2.0 male-to-male data cable.~~bin'''~~ The position of the USB2.0 programming port of the development board is shown in the ~~MiniLoader folder downloaded earlier, and click to open.~~figure below</li~~></ol~~>

[[File:pi3b-~~img68~~img36.png~~|459x216px|SIS5H0S2@F5M2D(6ANZEUPG~~]]

</div></ol>

<li>~~Then click '''Download'''[[File:pi3b-img128.png|472x222px]]</li><li>The display after downloading '''MiniLoaderAll.bin'''~~ Make sure that the development board is ~~shown in~~ not inserted into the TF card and not connected to the ~~figure below[[File:pi3b-img140.png|474x223px]]~~power supply</li><li>Then ~~select~~ press and hold the MaskROM button on the ~~storage device as '''EMMC'''~~development board, ~~and then click Switch '''Storage'''[[File:pi3b-img141.png|468x225px]]</li><li>The display~~ the position of ~~successful switching~~ the MaskROM button on the development board is shown in the figure below:</li~~></ol~~>

[[File:pi3b-~~img142~~img37.png~~|472x227px~~]]</ol><ol start="4" style="list-style-type: lower-alpha;"><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:pi3b-img38.png]]</ol><ol start="85" style="list-style-type: lower-alpha;"><li>~~Then click~~ 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 "'''~~Upgrade Firmware~~found a MASKROM device'''" ~~column of the burning tool~~</li~~></ol~~>

[[File:pi3b-~~img132~~img39.png~~|442x208px~~]]</ol><ol start="6" style="list-style-type: lower-alpha;"><li>Then click the "'''Upgrade Firmware'''" column of the burning tool</li>

[[File:pi3b-img132.png]]</ol><ol start="7" style="list-style-type: lower-~~roman~~alpha;"><li>Then click the "'''Firmware'''" button to select ~~the path of~~ the Android image ~~that needs~~ to be burned</li~~></ol~~>

[[File:pi3b-img133.png~~|444x209px~~]]</ol><ol start="8" style="list-style-type: lower-alpha;"><li>Finally, click the "Upgrade" button to start burning. The burning process is shown in the figure below. You can see that the firmware will be burned to SPIFlash first, and then burned to PCIE. After burning is completed, the Android system will start automatically.</li>

[[File:pi3b-img148.png]]</ol ~~start="10" style="list-style-type: lower-alpha;"~~></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.</liol></olspan>

~~<div class~~=~~"figure">~~= Using RKDevTool to clear SPIFlash ==

~~[[File:pi3b-img134.png|455x214px|GO~ZSPN`B]JCQM`@_9UU8[R]]~~# The position of SPI Flash on the development board is shown in the figure below

~~</div>=== How to burn Android11 image into eMMC via TF card ===~~img76.png]]

~~'''Note that all the following operations are performed on~~ <ol start="2" style="list-style-type: decimal;"><li>First, you need to prepare a ~~Windows computer~~good quality USB2.~~'''~~0 male-to-male data cable</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 eMMC module and the method of plugging into the development board are as follows:<div class="figure">

[[File:pi3b-~~img61~~img16.png~~|115x84px]] [[File:pi3b-img62.png|120x87px~~]]

~~[[File:pi3b-img63.png|286x133px]]~~</div></ol><ol start="23" style="list-style-type: decimal;"><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-3B.html~~ Rockchip driver '''~~Orange Pi data download page~~DriverAssitant_v5.12.zip'''], and MiniLoader and the burning tool '''~~please make sure that the version of the SDDiskTool tool is the latest v1~~RKDevTool_Release_v3.15.72zip'''~~</li><li>Then download~~ from the ~~Android image from~~ [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi's data download page''']

<li>~~After opening~~ On the download ~~link~~ page of Orange Pi, first select the ~~Android image~~official tool, ~~you can see~~ and then enter the following ~~two types of Android images, please select the image in '''the TF card and eMMC startup image~~ folder~~''' to download</li></ol>~~</li~~></ol~~>

[[File:pi3b-~~img124~~img149.png~~|340x108px|e6986fc9c8fc078e8cb6a9c39b76fb8~~]]

</div></ol>

<li>~~After entering '''the TF card and eMMC boot image folder''', you can see the following tow images, the difference between them is:<ol style="list-style-type: lower-alpha;"><li>The first image is dedicated to HDMI display and supports 4K display. If you don’t use LCD screen, please~~ Then download all the ~~image without lcd~~files below</li>~~<li>If you want to use lcd screen, please choose image with lcd</li></ol></li></ol~~>

~~[[File:pi3b-img125.png|283x62px]]~~<div class="figure">

~~<ol start="6" style="list-style~~[[File:pi3b-~~type: decimal;">~~<li>Then use the 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~~img150.~~exe''' in the decompressed folder and open it</li></ol>~~png]]

~~[[File~~</div>{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-| <big>'''Note that the "MiniLoader-~~img135~~things needed to burn the Linux image" folder is hereinafter referred to as the MiniLoader folder.~~png~~'''</big>|~~429x103px]]~~}</ol></li></ol><ol start="4" style="list-style-type: decimal;"><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:pi3b-img31.png]]</ol><ol start="85" style="list-style-type: decimal;"><li>After opening ~~'''SDDiskTool'''~~DriverInstall.exe, if the ~~TF card is recognized normally,~~ steps to install the ~~inserted disk device will be displayed in~~ Rockchip driver are as follows<ol style="list-style-type: lower-alpha;"><li>Click the "'''~~Select Removable Disk Device~~Driver Installation'''" ~~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.~~button</li~~></ol~~>

[[File:pi3b-~~img136~~img32.png~~|267x228px~~]]</ol><ol start="2" style="list-style-type: lower-alpha;"><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:pi3b-img33.png]]</ol></li></ol><ol start="96" style="list-style-type: decimal;"><li>~~After confirming the drive letter, you can format the TF card first, click the~~ Then decompress '''~~restore disk button~~RKDevTool_Release_v3.15.zip''' ~~in SDDiskTool~~, ~~or use the~~ this software does not need to be installed, just find '''~~SD Card Formatter~~RKDevTool''' ~~mentioned above to format~~ in the ~~TF card~~decompressed folder and open it</li~~></ol~~>

[[File:pi3b-~~img137~~img34.png~~|247x212px~~]]</ol><ol start="7" style="list-style-type: decimal;"><li>After opening the '''RKDevTool''' burning tool, because the computer has not connected to the development board through the USB2.0 male-to-male data cable at this time, the lower left corner will prompt "'''No device found'''"</li>

[[File:pi3b-img35.png]]</ol><ol start="108" style="list-style-type: decimal;"><li>Then you can start to ~~write the Android image into~~ clear the ~~TF card~~content in SPI FLASH

<li~~><p~~>First ~~confirm that~~ , connect the development board to the ~~displayed drive letter is~~ Windows computer through the ~~drive letter corresponding~~ USB2.0 male-to -male data cable. The position of the ~~TF card under "'''Select Removable Disk Device'''"</li><li>Then select "'''Firmware Upgrade'''" in "'''Select Function Mode'''"</li><li>Then select the path~~ USB2.0 programming port of the ~~Android firmware~~ development board is shown in the ~~"'''Select Upgrade Firmware'''" column~~figure below</li>~~<li>Finally click the "'''Start Create'''" button to start burning</li></ol></li></ol~~>

~~[[File:pi3b-img143.png|290x246px]]~~<div class="figure">

~~<ol start="11" style="list~~[[File:pi3b-~~style-type: decimal;"><li>After the burning is completed, the display is as shown in the figure below, and then you can exit SDDiskTool</li></ol>~~img36.png]]

~~[[File~~</div></ol><ol start="2" style="list-style-type:~~pi3b~~lower-~~img144.png|285x243px]]~~alpha;"><li>Make sure that the development board is not inserted into the TF card and 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:</li>

[[File:pi3b-img37.png]]</ol><ol start="124" style="list-style-type: ~~decimal~~lower-alpha;"><li~~><p~~>Then ~~pull out~~ connect the ~~TF card from~~ power supply of the ~~computer and insert it into~~ Type-C interface to the development board~~. After the development board is powered~~ , and power on, ~~it will automatically start burning the Android image in the TF card to the eMMC of the development board.</li><li>If~~ and then release 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~~MaskROM button</li~~></ol~~>

[[File:pi3b-~~img145~~img38.png~~|430x247px~~]]</ol><ol start="5" style="list-style-type: lower-alpha;"><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:pi3b-img39.png]]</ol><ol start="146" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~When~~ Then please select '''Advanced Features'''[[File:pi3b-img126.png]]</li><li>Then click the ~~HDMI monitor displays~~ position shown in the ~~following information, it means that the burning of the Android image into the eMMC has been completed~~figure below[[File:pi3b-img127.png]]</li><li>Select '''rk3566_MiniLoaderAll. ~~At this time,~~ bin''' in the ~~TF card can be pulled out~~'''MiniLoader''' folder you downloaded earlier, and ~~then the Android system in the eMMC will start.~~click Open</lip></olli>

~~[[File:pi3b-img146.png|576x389px]]~~<div class="figure">

~~== How to burn Android image to SPIFlash+NVMe SSD ==~~img68.png]]

</div></ol><ol style="list-style-type: lower-roman;"><li>Then click '''~~Note that all the following operations are performed on a Windows computer.~~Download'''[[File:pi3b-img128.png]]</li></ol>

<ol start="10" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~First, you need to prepare an NVMe SSD solid state drive~~The display after downloading '''rk3566_MiniLoaderAll.bin''' is shown in the figure below[[File:pi3b-img140.png]]</li><li>Then select the storage device as '''SPINOR'''<~~ol style="list~~p>[[File:pi3b-~~style~~img151.png]]</li><li>Then click Switch '''Storage'''[[File:pi3b-~~type~~img152.png]]</li><li>Then click '''Erase All''' to start erasing SPIFlash[[File: ~~lower~~pi3b-~~alpha;"~~img153.png]]</li><li>The Mdisplay log after erasing SPIFlash is shown in the figure below[[File:pi3b-img154.~~2 2230 SSD is as follows~~png]]</li></ol>

</li></ol>

~~[[File:pi3b-img73.png|147x106px]]~~== Start the Orange Pi development board ==

~~<ol start="2" style="list~~# Insert the TF card with the burned image into the TF card slot of the Orange Pi development board. If the image of SPIFlash+NVMe SSD has been burnt, then there is no need to insert a TF card, just make sure that the NVMe SSD is inserted into the development board normally.# The development board has an HDMI interface, and the development board can be connected to a TV or HDMI display through an HDMI-~~style~~to-HDMI cable. If you have purchased an LCD screen, you can also use the LCD screen to display the system interface of the development board. If there is a Type-~~type: lower~~C to HDMI cable, the system interface of the development board can also be displayed through the Type-~~alpha;">~~C interface.# Connect a USB mouse and keyboard to control the Orange Pi development board.~~<li>~~# The Mdevelopment board has an Ethernet port, which can be plugged into a network cable for Internet access.~~2 2242 SSD is as follows<~~# Connect a high-quality power adapter with a 5V/~~li></ol>~~3A USB Type-C interface.

~~[[File~~:~~pi3b~~:{| class="wikitable" style="background-~~img74~~color:#ffffdc;width:800px;" |-| <big>'''Remember not to plug in a power adapter with a voltage output greater than 5V, as this will burn out the development board.~~png|216x119px]]~~'''

'''<~~ol start="2"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>Then insert~~ Many unstable phenomena during the ~~NVMe SSD into~~ power-on and start-up process of the Msystem are basically caused by power supply problems, so a reliable power adapter is very important.~~2 PCIe interface~~ If you find that there is a phenomenon of continuous restart during the startup process, please replace the power supply or the ~~development board~~ Type-C data cable and ~~fix it</li>~~try again.'''</olspan>

~~[[File~~'''The Type-~~img75~~C power port does not support PD negotiation.~~png|283x63px]]~~'''

'''<~~ol start="3"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>The position~~ In addition, please do not connect the USB interface of the ~~SPI Flash on~~ computer to power the development board ~~is shown in the figure below, no other settings are required before starting the programming~~.'''</lispan></olbig>|}

~~[[File~~<ol start="6" style="list-style-type:~~pi3b-img76~~decimal;"><li>Then turn on the switch of the power adapter. If everything is normal, you can see the startup screen of the system on the HDMI monitor or LCD screen.~~png|266x211px]]~~</li>

~~<ol start="4" style="list-style-type: decimal;">~~<li>~~You also need~~ If you want to ~~prepare a good quality USB2~~view the output information of the system through the debugging serial port, please use the serial cable to connect the development board to the computer.~~0 male-~~For the connection method of the serial port, please refer to '''[[Orange Pi 3B#How to use the debugging serial port|the section on how to~~-male data cable~~use the debugging serial port]].'''</li></ol>

~~<div class~~=~~"figure">~~= How to use the debugging serial port ==

~~[[File:pi3b~~=== Connection instruction of debugging serial port ===

~~</div>~~<ol ~~start="5"~~ style="list-style-type: decimal;"><li>~~Then download Rockchip driver '''DriverAssitant_v5~~First, you need to prepare a 3.~~12.zip'''~~ 3V USB-to-TTL module, and ~~burning tool '''RKDevTool_Release_v3.15.zip''' from '''Orange Pi's data download page'''</li><li>Then download~~ then insert the USB interface end of the USB-to-TTL module into the ~~image~~ USB interface of ~~Android11~~the computer.~~<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;"|-| <big><lip>~~After opening the download link of the Android image~~'''For better compatibility, ~~you can see the following two types of Android images~~it is recommended to use CH340 USB to TTL module, please ~~select the image in the S~~do not use CP2102, PL2303 USB to TTL module.'''~~PIFlash-NVME SSD boot image folder~~''' Before purchasing a USB to ~~download~~TTL module, please confirm that the module supports a baud rate of 1500000.'''</lip></olbig>~~</li></ol>~~|}

[[File:pi3b-~~img124~~img155.png~~|340x108px|e6986fc9c8fc078e8cb6a9c39b76fb8~~]]

</div>~~<ol start="2" style="list-style-type: lower-alpha;">~~</li>~~After entering the '''SPIFlash-NVME SSD boot image folder''', you can see the following two images. Their differences are:~~</pol><ol start="2" style="list-style-type: ~~lower-alpha~~decimal;"><li~~><p~~>The ~~image without lcd is specially used for HDMI display~~ corresponding relationship between GND, RXD and ~~supports 4K display. If you do not use~~ TXD pins of the debugging serial port of the ~~LCD screen, please download~~ development board is shown in the ~~image without lcd~~figure below</li>~~<li>If you want to use LCD screen, please choose image with lcd</li></ol></li></ol~~>

[[File:pi3b-~~img147~~img156.png~~|305x58px~~]]</ol><ol start="3" style="list-style-type: decimal;"><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</li>

~~<ol start="7" style="list-style-type~~: ~~decimal;"><li>Then use~~ a. Connect the ~~decompression software~~ GND of the USB to TTL module to ~~decompress '''DriverAssitant_v5.12.zip''', and then find~~ the ~~'''DriverInstall.exe''' executable file in~~ GND of the ~~decompressed folder and open it</li></ol>~~development board

~~[[File~~:~~pi3b-img31~~b.~~png|407x120px]]~~The '''RX of the USB to TTL module is connected to the TX''' of the development board

:c. The '''<~~ol start="8"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">TX of the USB to TTL module is connected to the TX<~~li><p~~/span>~~After opening~~ '''~~DriverInstall.exe''',~~ of the ~~steps to install the Rockchip driver are as follows~~development board</pol><ol start="4" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Click~~ The schematic diagram of connecting the ~~"'''Driver Installation'''" button~~USB to TTL module to the computer and the Orange Pi development board is as follows</li~~></ol></li></ol~~>

~~[[File:pi3b-img32.png|286x150px]]~~<div class="figure">

~~<ol start="2" style="list-style-type~~[[File: ~~lower-alpha;"><li>After waiting for a period of time, a pop~~pi3b-~~up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button~~img157.~~</li></ol>~~png]]

~~[[File~~</div>{| class="wikitable" style="background-color:~~pi3b~~#ffffdc;width:800px;" |-~~img33~~| <big>'''The TX and RX of the serial port need to be cross-connected. If you don't want to carefully distinguish the order of TX and RX, you can connect the TX and RX of the serial port casually first.~~png~~If there is no output in the test, then exchange the order of TX and RX, so there is always a the order is right'''</big>|~~296x154px]]~~}</ol>

~~<ol start~~=~~"9" style~~=~~"list-style-type: decimal;"><li>Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need~~ = How to ~~be installed, just find '''RKDevTool''' in~~ use the ~~decompressed folder and open it</li></ol>~~debugging serial port on the Ubuntu platform ===

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-~~img34~~| <big>'''There are many serial port debugging software that can be used under Linux, such as putty, minicom, etc. The following demonstrates how to use putty.~~png~~'''</big>|~~413x122px]]~~}

~~<ol start="10" style="list~~# First, insert the USB-~~style~~to-~~type: decimal;"><li>After opening~~ TTL module into the ~~'''RKDevTool''' burning tool, because~~ USB interface of the Ubuntu computer ~~is not connected to~~ . If the ~~development board through~~ connection and recognition of the ~~USB2.0 male~~USB-to-~~male data cable at this time~~TTL module is normal, you can see the ~~lower left corner will prompt "~~corresponding device node name under '''~~No device found~~/dev'''~~"</li></ol>~~on the Ubuntu PC. Remember this node name, and then set the serial port software will be used

~~[[File~~:~~pi3b-img35.png~~:{|~~402x189px]]~~ ~~<ol start~~class="11wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then start burning the Android image to SPIFlash+NVMe SSD<ol style="list~~|-~~style-type: lower-alpha;">~~<li>First, connect the development board to the Windows computer through the USB2.0 male-to-male data cable. The position of the USB2.0 programming port of the development board is shown in the figure below</li></ol>| <test@test:~$ '''ls /~~li><~~dev/~~ol>~~ttyUSB*'''

~~<div class="figure">~~/dev/ttyUSB0|}

~~[[File~~<ol start="2" style="list-style-type: decimal;"><li>Then use the following command to install putty on Ubuntu PC</li>{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img36.png~~|~~275x116px|C~~test@test:~~\Users\orangepi\Desktop\用户手册插图\pi 3b\1691131157154(1).jpg1691131157154(1)]]~~~$ '''sudo apt-get update'''

test@test:~$ '''sudo apt-get install -y putty'''|}</~~div~~ol><ol start="23" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then run putty, '''<pspan style="color:#FF0000">~~Make sure that the development board is not inserted into the TF card and not connected~~ remember to ~~the power supply~~add sudo permission</~~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:</p~~span>'''</li~~></ol~~>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img37.png~~| test@test:~$ '''sudo putty'''|~~289x100px]]~~}</ol><ol start="4" style="list-style-type: decimal;"><li>After executing the putty command, the following interface will pop up</li>

[[File:pi3b-img158.png]]</ol><ol start="45" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then connect~~ First select the ~~power supply~~ setting interface of the ~~Type-C interface to the development board, and power on, and then release the MaskROM button~~serial port</li~~></ol~~>

[[File:pi3b-~~img38~~img159.png~~|305x94px~~]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then set the parameters of the serial port<ol style="list-style-type: lower-alpha;"><li>Set Serial line to connect toas /dev/ttyUSB0（(Modified to the corresponding node name, generally /dev/ttyUSB0）</li><li>Set Speed(baud) as '''1500000'''（Serial port baud rate）</li><li>Set Flow control as None</li>

<~~ol start~~div class="5figure" ~~style="list-style-type: lower-alpha;">~~<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></ol>

[[File:pi3b-~~img39~~img160.png~~|443x208px~~]]

</div></ol></li></ol><ol start="67" style="list-style-type: decimal;"><li>After setting the setting interface of the serial port, return to the Session interface<ol style="list-style-type: lower-alpha;"><li>First select the Connection type as Serial</li><li>Then click the ~~"'''Upgrade Firmware'''" column of~~ Open button to connect to the ~~burning tool~~serial port</lip></olli>

~~[[File:pi3b-img132.png|442x208px]]~~<div class="figure">

~~<ol start="7" style="list-style-type~~[[File: ~~lower~~pi3b-~~alpha;"><li>Then click the "'''Firmware'''" button to select the Android image to be burned</li></ol>~~img161.png]]

~~[[File~~</div></ol></li></ol><ol start="8" style="list-style-type:~~pi3b-img133.png|444x209px]]~~decimal;"><li>After starting the development board, you can see the Log information output by the system from the opened serial port terminal</li>

[[File:pi3b-img162.png]]</ol ~~start~~><li>Finally, click the "Upgrade" button to start burning. The burning process is shown in the figure below. You can see that the firmware will be burned to SPIFlash first, and then burned to PCIE. After burning is completed, the Android system will start automatically.</~~li></ol~~span>

~~[[File:pi3b-img148.png|453x212px]]~~=== How to use the debugging serial port on Windows platform ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <~~span id~~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>|} <ol style="~~using~~list-~~rkdevtool~~style-type: decimal;"><li>Download MobaXterm<ol style="list-tostyle-~~clear~~type: lower-~~spiflash~~alpha;"><li>Download MobaXterm website as follows</~~span~~li>{| class="wikitable" style= ~~Using RKDevTool to clear SPIFlash~~ "width:800px;" |-| [https://mobaxterm.mobatek.net/ '''https://mobaxterm.mobatek.net''']|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>After entering the MobaXterm download page, click '''GET XOBATERM NOW!'''</li>

~~# The position of SPI Flash on~~ [[File:pi3b-img163.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then choose to download the ~~development board is shown in the figure below~~Home version</li>

[[File:pi3b-~~img76~~img164.png~~|263x193px~~]]</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then select the Portable version. After downloading, you don't need to install it, just open it and use it</li>

[[File:pi3b-img165.png]]

</ol>

</li></ol>

<li>~~First~~After downloading, use decompression software to decompress the downloaded compressed package, you ~~need to prepare a good quality USB2.0 male~~can get the executable software of MobaXterm, and then double-click to~~-male data cable~~open</li~~></ol~~>

~~<div class="figure">~~ [[File:pi3b-~~img16~~img166.png~~|141x138px|D6BB9058-CDC3-42d7-A7FC-FBF630D886B7~~]] </~~div~~ol>

<li>~~Then download~~ After opening the ~~Rockchip driver '''DriverAssitant_v5.12.zip''' and MiniLoader and~~ software, the ~~burning tool '''RKDevTool_Release_v3.15.zip''' from~~ steps to set up the ~~[http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page''']~~serial port connection are as follows

<li>On Open the session settings interface</li><li>Select the serial port type</li><li>Select the ~~download page~~ port number of ~~Orange Pi, first~~ the serial port (select the ~~official tool, and then enter~~ corresponding port number according to the ~~following folder~~actual situation)</li><li>Select the baud rate of the serial port as '''1500000'''</olli><li>Finally click the "'''OK'''" button to complete the setting</lip></olli>

[[File:pi3b-~~img149~~img167.png~~|342x56px|1691401357374~~]]

</div></ol></li></ol><ol start="24" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then download all~~ After clicking the "'''OK'''" button, you will enter the following interface. At this time, start the development board and you can see the ~~files below~~output information of the serial port</li~~></ol~~>

[[File:pi3b-~~img150~~img168.png~~|347x139px|1691401520573~~]]

</div></ol>~~'''Note that~~ <span id="instructions-for-using-the ~~"MiniLoader~~-~~things needed to burn~~ 5v-pin-in-the-40pin-interface-of-the ~~Linux image" folder is hereinafter referred~~ -development-board-to ~~as the MiniLoader folder.'''~~-supply-power">

~~<ol start~~=~~"4" style~~=~~"list-style-type: decimal;"><li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find~~ Instructions for using the ~~'''DriverInstall.exe''' executable file~~ 5v pin in the ~~decompressed folder and open it</li></ol>~~40pin interface of the development board to supply power ==

~~[[File~~{| class="wikitable" style="background-color:~~pi3b~~#ffffdc;width:800px;" |-| <big>'''The power supply method we recommend for the development board is to use the 5V/3A 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 cord 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-~~img31~~C power supply.~~png~~'''</big>|~~472x139px]]~~}

~~<ol start="5" style="list-style-type: decimal;"><li>After opening DriverInstall.exe~~# First, ~~the steps~~ you need to ~~install the Rockchip driver are~~ prepare a power cord as ~~follows<ol style="list-style-type: lower-alpha;"><li>Click~~ shown in the ~~"'''Driver Installation'''" button</li></ol></li></ol>~~figure below

~~[[File:pi3b-img32.png|276x145px]]~~<div class="figure">

~~<ol start="2" style="list-style-type~~: ~~lower-alpha;"><li>After waiting for a period of time, a pop~~:[[File:pi3b-~~up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button~~img169.~~</li></ol>~~png]]

~~[[File~~</div>:~~pi3b~~:{| class="wikitable" style="background-~~img33.png~~color:#ffffdc;width:800px;" |-| <big>'''Please purchase the power cord shown in the picture above by yourself'''</big>|~~292x151px]]~~}

<ol start="62" style="list-style-type: decimal;"><li>~~Then decompress~~ 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<ol style="list-style-type: lower-alpha;"><li>The USB A port of the power cord shown in the above picture needs to be plugged into the 5V/3A power adapter connector ('''please do not plug into the computer'~~RKDevTool_Release_v3.15.zip~~s USB port for power supply'''~~, this software does not need~~ )</li><li>The red DuPont line needs to be plugged into the 5V pin of the development board 40pin</li><li>The black Dupont wire needs to be ~~installed~~inserted into the GND pin of the 40pin interface</li><li>The position of the 5V pin and GND pin of the 40pin interface on the development board is shown in the figure below, ~~just find~~ '''~~RKDevTool~~remember not to reverse the connection''' ~~in the decompressed folder and open it~~</lip></olli>

[[File:pi3b-~~img34~~img170.png~~|467x138px~~]] ~~<ol start="7" style="list-style-type: decimal;">~~<li>After opening the '''RKDevTool''' burning tool, because the computer has not connected to the development board through the USB2.0 male-to-male data cable at this time, the lower left corner will prompt "'''No device found'''"</li></ol> ~~[[File:pi3b-img35.png|402x189px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>Then you can start to clear the content in SPI FLASH<ol style="list-style-type: lower-alpha;">~~<li>First, connect the development board to the Windows computer through the USB2.0 male-to-male data cable. The position of the USB2.0 programming port of the development board is shown in the figure below</li></ol>

</li></ol>

~~<div class~~=~~"figure">~~'''Instructions for use of Ubuntu/Debian Server and Xfce desktop system''' =

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-~~img36~~| <big>'''The content of this chapter is written based on the images of the Linux server version and the xfce desktop version.~~png|275x116px~~'''</big>|~~C:\Users\orangepi\Desktop\用户手册插图\pi 3b\1691131157154(1).jpg1691131157154(1)]]~~}

<~~/div><ol start~~span id="~~2" style="list~~supported-linux-image-~~style~~types-~~type: lower~~and-~~alpha;~~kernel-versions">~~<li>Make sure that the development board is not inserted into the TF card and not connected to the power supply~~</~~p></li~~span>~~<li>Then press~~ == Supported Linux image types 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></ol>~~kernel versions ==

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;text-~~img37~~align: center;"|-|'''Linux image type'''|'''kernel version'''|'''server version'''|'''desktop version'''|-|'''Debian 11 - Bullseye'''|'''Linux5.~~png~~10'''|'''support'''|'''support'''|-|'''Ubuntu 20.04 - Focal'''|'''Linux5.10'''|'''support'''|'''support'''|-|'''Ubuntu 22.04 - Jammy'''|'''Linux5.10'''|'''support'''|'''support'''|~~289x100px]]~~}

<~~ol start~~span id="~~4" style="list-style~~linux-~~type: lower~~system-~~alpha;~~adaptation">~~<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~~></olspan>== Linux System adaptation ==

~~[[File:pi3b-img38.png~~{|~~305x94px]]~~ ~~<ol start~~class="5wikitable" style="~~list-style~~width:800px;text-~~type~~align: ~~lower-alpha~~center;">~~<li>If the previous steps are successful, the development board will enter the~~ |-|'''~~MASKROM~~Function''' ~~mode at this time, and the interface of the burning tool will prompt "~~|'''~~found a MASKROM device~~Debian11'''~~"</li></ol>~~|'''Ubuntu20.04'''~~[[File:pi3b-img39~~|'''Ubuntu22.~~png~~04'''|~~457x215px]]~~-|'''USB2.0x3'''~~<ol start="6" style="list-style-type: lower-alpha;">~~|'''OK'''~~<li>Then please select~~ |'''~~Advanced Features~~OK'''~~[[File:pi3b-img126.png~~|~~458x138px]]</li>~~'''OK'''~~<li>Then click the position shown in the figure below~~|-~~[[File:pi3b-img127.png~~|~~459x216px]]</li><li>Select~~ '''~~rk3566_MiniLoaderAll~~USB3.~~bin~~0x1''' ~~in the~~ |'''~~MiniLoader~~OK''' ~~folder you downloaded earlier, and click Open</li></ol>~~|'''OK'''~~<div class="figure">~~|'''OK'''|-~~[[File:pi3b-img68~~|'''M.~~png~~2 NVMe SSD Start'''|~~459x216px~~'''OK'''|~~SIS5H0S2@F5M2D(6ANZEUPG]]~~'''OK'''|'''OK'''~~</div>~~|-~~<ol style="list-style-type: lower-roman;">~~|'''WIFI'''~~<li>Then click~~ |'''~~Download~~OK'''~~[[File:pi3b-img128.png~~|~~472x222px]]</li></ol>~~'''OK'''|'''OK'''~~<ol start="10" style="list~~|-~~style-type: lower-alpha;"><li>The display after downloading~~ |'''Bluetooth'''|'''~~rk3566_MiniLoaderAll.bin~~OK''' ~~is shown in the figure below[[File:pi3b-img140.png~~|~~474x223px]]</li>~~'''OK'''~~<li>Then select the storage device as~~ |'''~~SPINOR~~OK'''~~[[File:pi3b~~|-~~img151.png~~|~~467x220px]]</li>~~'''GPIO（40pin）'''~~<li>Then click Switch~~ |'''~~Storage~~OK'''~~[[File:pi3b-img152.png~~|~~464x218px]]</li>~~'''OK'''~~<li>Then click~~ |'''~~Erase All~~OK''' ~~to start erasing SPIFlash[[File:pi3b~~|-~~img153.png~~|~~467x220px]]</li>~~'''UART（40pin）'''~~<li>The display log after erasing SPIFlash is shown in the figure below~~|'''OK'''~~[[File:pi3b-img154.png~~|~~460x216px]]</li></ol>~~'''OK'''|'''OK'''~~== Start the Orange Pi development board ==~~|'''SPI（40pin）'''|'''OK'''# Insert the TF card with the burned image into the TF card slot of the Orange Pi development board. If the image of SPIFlash+NVMe SSD has been burnt, then there is no need to insert a TF card, just make sure that the NVMe SSD is inserted into the development board normally.|'''OK'''# The development board has an HDMI interface, and the development board can be connected to a TV or HDMI display through an HDMI-to-HDMI cable. If you have purchased an LCD screen, you can also use the LCD screen to display the system interface of the development board. If there is a Type-C to HDMI cable, the system interface of the development board can also be displayed through the Type-C interface.|'''OK'''~~# Connect a USB mouse and keyboard to control the Orange Pi development board.# The development board has an Ethernet port, which can be plugged into a network cable for Internet access.# Connect a high~~|-~~quality power adapter with a 5V/3A or 5V/4A USB Type-C interface.~~|'''I2C（40pin）'''|'''~~Remember not to plug in a power adapter with a voltage output greater than 5V, as this will burn out the development board.~~OK'''|'''OK'''|'''Many unstable phenomena during the power-on and start-up process of the system are basically caused by power supply problems, so a reliable power adapter is very important. If you find that there is a phenomenon of continuous restart during the startup process, please replace the power supply or the Type-C data cable and try again.OK'''|-|'''~~The Type-C power port does not support PD negotiation.~~PWM（40pin）'''|'''OK'''|'''~~In addition, please do not connect the USB interface of the computer to power the development board.~~OK'''|'''OK'''~~6) Then turn on the switch of the power adapter. If everything is normal, you can see the startup screen of the system on the HDMI monitor or LCD screen.~~|-|'''PWM fan interface'''7) If you want to view the output information of the system through the debugging serial port, please use the serial cable to connect the development board to the computer. For the connection method of the serial port, please refer to |'''OK'''~~[[\l~~|~~the section on how to use the debugging serial port]].~~'''OK'''|'''OK'''~~== How to use the debugging~~ |'''3pin Debug serial port =='''|'''OK'''~~~~|'''OK'''~~=== Connection instruction of debugging serial port ===~~|'''OK''' ~~<ol style="list-style~~|-~~type: decimal;"><li>First, you need to prepare a 3.3V USB-to-TTL module, and then insert the USB interface end of the USB-to-TTL module into the USB interface of the computer.~~|'''EMMC'''~~~~|'''~~For better compatibility, it is recommended to use CH340 USB to TTL module, please do not use CP2102, PL2303 USB to TTL module.~~OK'''~~~~|'''~~Before purchasing a USB to TTL module, please confirm that the module supports a baud rate of 1500000.~~OK'''~~</li></ol>~~|'''OK'''~~<div class="figure">~~|-|'''TF card start'''~~[[File:pi3b-img155.png~~|~~576x115px~~'''OK'''|~~07]]~~'''OK'''|'''OK'''~~</div><ol start="2" style="list~~|-~~style-type: decimal;"><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</li></ol>~~|'''HDMI Video'''|'''OK'''~~[[File:pi3b-img156.png~~|~~428x110px]]~~'''OK'''|'''OK'''~~<ol start="3" style="list-style~~|-~~type: decimal;"><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</li></ol>~~|'''HDMI Audio'''|'''OK'''~~<blockquote>a. Connect the GND of the USB to TTL module to the GND of the development board~~|'''OK'''|'''OK'''~~b. The~~ |-|'''~~RX of the USB to TTL module is connected to the TX~~Camera''' ~~of the development board~~|'''OK'''~~c. The~~ |'''~~TX of the USB to TTL module is connected to the TX~~OK''' ~~of the development board</blockquote>~~|'''OK'''~~<ol start="4" style="list-style~~|-~~type: decimal;"><li>The schematic diagram of connecting the USB to TTL module to the computer and the Orange Pi development board is as follows</li></ol>~~|'''LCD'''|'''OK'''~~<div class="figure">~~|'''OK'''|'''OK'''~~[[File:pi3b-img157.png~~|~~524x189px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\USB-to-TTL-module~~-~~to-the-computer.jpgUSB-to-TTL-module-to-the-computer]]~~|'''Edp Display'''~~</div>~~|'''OK'''|'''The TX and RX of the serial port need to be cross-connected. If you don’t want to carefully distinguish the order of TX and RX, you can connect the TX and RX of the serial port casually first. If there is no output in the test, then exchange the order of TX and RX, so there is always a the order is rightOK'''|'''OK'''~~=== How to use the debugging serial~~ |'''Gigabit Ethernet port ~~on the Ubuntu platform ===~~'''|'''OK'''|'''~~There are many serial port debugging software that can be used under Linux, such as putty, minicom, etc. The following demonstrates how to use putty.~~OK'''|'''OK'''~~# First, insert the USB~~|-~~to-TTL module into the USB interface of the Ubuntu computer. If the connection and recognition of the USB-to-TTL module is normal, you can see the corresponding device node name under~~ |'''~~/dev~~Network port status light''' ~~on the Ubuntu PC. Remember this node name, and then set the serial port software will be used~~|'''OK'''~~test@test:~$~~ |'''ls /dev/ttyUSB*OK'''|'''OK'''~~/dev/ttyUSB0~~ ~~<ol start="2" style="list~~|-~~style-type: decimal;"><li>Then use the following command to install putty on Ubuntu PC</li></ol>~~|'''headphone playback'''|'''OK'''~~test@test:~$~~ |'''~~sudo apt-get update~~OK''' ~~test@test:~$~~ |'''~~sudo apt-get install -y putty~~OK''' ~~<ol start="3" style="list-style~~|-~~type: decimal;"><li>Then run putty,~~ |'''~~remember to add sudo permission~~headphone recording'''~~</li></ol>~~|'''OK'''~~test@test:~$~~ |'''~~sudo putty~~OK'''|'''OK'''~~<ol start="4" style="list~~|-~~style-type: decimal;"><li>After executing the putty command, the following interface will pop up</li></ol>~~|'''LED Light'''|'''OK'''~~[[File:pi3b-img158.png~~|~~367x321px]]~~'''OK'''|'''OK'''~~<ol start="5" style="list~~|-~~style-type: decimal;"><li>First select the setting interface of the serial port</li></ol>~~|'''RTC'''|'''OK'''~~[[File:pi3b-img159.png~~|~~359x352px]]~~'''OK'''|'''OK'''~~<ol start="6" style="list~~|-~~style-type: decimal;"><li>Then set the parameters of the serial port~~|'''GPU'''~~<ol style="list-style-type: lower-alpha;">~~|'''OK'''~~<li>Set Serial line to connect toas /dev/ttyUSB0（(Modified to the corresponding node name, generally /dev/ttyUSB0）</li>~~|'''OK'''~~<li>Set Speed(baud) as~~ |'''~~1500000~~OK'''~~（Serial port baud rate）</li><li>Set Flow control as None</li></ol>~~|-~~</li></ol>~~|'''NPU'''|'''OK'''~~<div class="figure">~~|'''OK'''|'''OK'''~~[[File:pi3b~~|-~~img160.png~~|~~317x312px~~'''VPU'''|~~09]]~~'''OK'''|'''OK'''~~</div>~~|'''OK'''~~<ol start="7" style="list~~|-~~style-type: decimal;"><li>After setting the setting interface of the serial port, return to the Session interface~~|'''watchdog test'''~~<ol style="list-style-type: lower-alpha;">~~|'''OK'''~~<li>First select the Connection type as Serial</li>~~|'''OK'''~~<li>Then click the Open button to connect to the serial port</li></ol>~~|'''OK'''~~</li></ol>~~|-|'''Chromium Hard solution video'''~~<div class="figure">~~|'''OK'''|'''OK'''~~[[File:pi3b-img161.png~~|~~345x340px~~'''OK'''|~~10]]~~}

<~~/div><ol start~~span id="~~8" style="list~~the-format-of-linux-commands-in-~~style~~this-~~type: decimal;~~manual">~~<li>After starting the development board, you can see the Log information output by the system from the opened serial port terminal~~</~~li></ol~~span>== The format of Linux commands in this manual ==

~~[[File~~# In this manual, all commands that need to be entered in the Linux system will be marked with the following box:~~pi3b~~:{| class="wikitable" style="width:800px;height:40px;" |-~~img162.png~~|~~468x340px]]~~

~~<span id~~|}::As shown below, the content in the yellow box indicates the content that needs special attention, except for the commands in it.::{| class="wikitable" style="~~how~~background-tocolor:#ffffdc;width:800px;height:40px;" |-~~use-the-debugging-serial-port-on-windows-platform">=== How to use the debugging serial port on Windows platform ===~~|

|}<ol start="2" style="list-style-type: decimal;"><li>Description of the prompt type in front of the command<ol style="list-style-type: lower-alpha;"><li>The prompt in front of the command refers to the content of the red part in the box below, which is not part of the Linux command, so when entering the command in the Linux system, please do not enter the content of the red font part</li>{| class="wikitable" style="width:800px;" |-| '''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.orangepi@orangepi:~$ sudo apt update'''

'''<ol span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>Download MobaXterm<ol style="list-style-type~~root@orangepi: ~~lower-alpha;"><li>Download MobaXterm website as follows</li>~~~#</olspan><''' '''vim /~~li><~~boot/~~ol>~~boot.cmd'''

'''test@test:~$ ssh [~~https~~mailto:~~//mobaxterm~~root@192.168.1.~~mobatek~~36 root@192.~~net/ https://mobaxterm~~168.~~mobatek~~1.~~net~~]xxx'''

'''root@test:~# ls'''

|}

</ol>

<li>~~After entering~~ '''root@orangepi:~$''' The prompt indicates that this command is entered in '''the Linux system of the development board'''. The $ at the end of the prompt indicates that the current user of the system is a normal user. When executing a privileged command, you need to add '''sudo'''</li><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:~$''' The 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 ~~MobaXterm download page~~system is an ordinary user. When executing privileged commands, ~~click~~ sudo needs to be added '''sudo'''</li><li>'''~~GET XOBATERM NOW!~~root@test:~#'''The 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></ol><ol start="3" style="list-style-type: decimal;"><li>What are the commands that need to be entered?<olstyle="list-style-type: lower-alpha;"><li>As shown below, '''the black bold part''' is the command that needs to be input, and the content below the command is the output content (some commands have output, some may not), and this part of the content does not need to be input</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''cat /boot/orangepiEnv.txt'''

~~[[File~~'''verbosity=7'''

~~<ol start~~bootlogo=~~"3" style="list-style-type: lower-alpha;"><li>Then choose to download the Home version</li></ol>~~false

~~[[File~~'''console=serial'''|}</ol><ol start="2" style="list-style-type: lower-~~img164~~alpha;"><li>As shown below, some commands cannot be written in one line and will be placed on the next line.~~png~~As long as the black and bold parts are all commands that need to be input. When these commands are entered into one line, the last "\" of each line needs to be removed, this is not part of the command. In addition, there are spaces in different parts of the command, please don't miss it</li>{|~~353x231px]]~~class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''echo \'''

~~<ol start~~'''"deb [arch=~~"4" style="list~~$(dpkg -~~style~~-~~type: lower~~print-~~alpha;"><li>Then select the Portable version. After downloading, you don’t need to install it, just open it and use it</li></ol>~~architecture) \'''

~~[[File:pi3b~~'''signed-~~img165~~by=/usr/share/keyrings/docker-archive-keyring.~~png|575x259px]~~gpg]\'''

~~<ol start="2" style="list-style-type~~'''https: ~~decimal;"><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<~~/~~li><~~/~~ol>~~download.docker.com/Linux/debian \'''

~~[[File:pi3b~~'''$(lsb_release -~~img166~~cs) stable" | sudo tee /etc/apt/sources.~~png|576x81px]]~~ ~~<ol start="3" style="~~list~~-style-type: decimal;"><li>After opening the software, the steps to set up the serial port connection are as follows<~~.d/p>~~<ol style="~~docker.list~~-style-type: lower-alpha~~>">~~<li>Open the session settings interface<~~/~~p><~~dev/~~li><li>Select the serial port type</li><li>Select the port number of the serial port (select the corresponding port number according to the actual situation), if you can’t see the port number, please use '''Driver Master~~null''' ~~to scan and install the driver for the USB to TTL serial port chip</li><li>Select the baud rate of the serial port as '''1500000'''</li>~~|}~~<li>Finally click the "'''OK'''" button to complete the setting</li>~~</ol>

</li></ol>

~~<div class~~=~~"figure">~~= Linux system login instructions ==

~~[[File:pi3b~~=== Linux system default login account and password ===

~~</div><ol start~~{| class="4wikitable" style="~~list~~width:800px;text-align: center;"|-|'''Account'''|'''Passport'''|-|'''root'''|'''orangepi'''|-|'''orangepi'''|'''orangepi'''|} {| class="wikitable" style="background-~~type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~After clicking~~ '''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.'''OK</big>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~" button~~When the wrong password is prompted, ~~you will enter~~ or there is a problem with the ~~following interface. At this time~~ssh connection, ~~start the development board and~~ please note that as long as you ~~can see~~ are using the ~~output information of~~ Linux image provided by Orange Pi, please do not suspect that the ~~serial port~~above password is wrong</lispan>, but look for other reasons.'''</olbig>|} === How to set automatic terminal login in Linux system ===

# The Linux system automatically logs in to the terminal by default, and the default login user name is '''<~~div class~~span style="~~figure~~color:#FF0000">orangepi'''

::[[File:pi3b-~~img168~~img171.png~~|575x291px|12~~]]

<ol start="2" style="list-style-type: decimal;"><li>Use the following command to set the root user to automatically log in to the terminal</~~div~~li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo auto_login_cli.sh root'''|}<~~span id~~/ol><ol start="3" style="~~instructions~~list-~~for-using~~style-type: decimal;"><li>Use thefollowing command to disable automatic login terminal</li>{| class="wikitable" style="width:800px;" |-5v| orangepi@orangepi:~$ '''sudo auto_login_cli.sh -~~pin~~d'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Use the following command to set the orangepi user to automatically log in-to theterminal again</li>{| class="wikitable" style="width:800px;" |-~~40pin~~| orangepi@orangepi:~$ '''sudo auto_login_cli.sh orangepi'''|}</ol>~~== Instructions for using the 5v pin in the 40pin interface of the development board to supply power ==~~

~~'''The power supply method we recommend~~ === Instructions for ~~the development board is to use the 5V/3A or 5V/4A Type C interface power cord to plug into the Type-C power interface~~ automatic login 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 cord 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.'''Linux desktop version system ===

# ~~First~~After the desktop system starts, ~~you need~~ it will automatically log in to ~~prepare~~ the desktop without entering a ~~power cord as shown in the figure below~~password

::[[File:pi3b-~~img169~~img172.png~~|151x108px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-7.jpg未标题-7~~]]

</div>

~~'''Please purchase the power cord shown in the picture above by yourself'''~~

<li>~~Use the 5V pin in~~ Run the ~~40pin interface to supply power~~ following command to prohibit the ~~development board. The connection method of~~ desktop system from automatically logging into the ~~power line is as follows~~desktop</pli>~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>The USB A port of the power cord shown in the above picture needs to be plugged into the 5V/3A or 5V4A power adapter connector (~~|-| orangepi@orangepi:~$ '''~~please do not plug into the computer’s USB port for power supply~~sudo disable_desktop_autologin.sh'''~~)</li><li>The red DuPont line needs to be plugged into the 5V pin of the development board 40pin~~|}</~~p></li~~ol><~~li>The black Dupont wire needs to be inserted into the GND pin of the 40pin interface</li~~ol start="3" style="list-style-type: decimal;"><li>~~The position of~~ Then restart the ~~5V pin~~ system and ~~GND pin of the 40pin interface on the development board~~ a login dialog box will appear, at which point a [[\l|password]] is ~~shown in the figure below, remember not~~ required to ~~reverse~~ enter the ~~connection~~system</p~~></li></ol~~><~~/li></ol~~div class="figure">

[[File:pi3b-~~img170~~img173.png~~|365x71px~~]]

<~~span id="instructions-for-use-of-ubuntudebian-server-and-xfce-desktop-system"~~/div></li></~~span~~ol>

~~'''~~=== The ~~content~~ setting method of ~~this chapter is written based on the images of the~~ root user automatic login in Linux ~~server version and the xfce~~ desktop version~~.'''~~system ===

~~== Supported Linux image types and kernel versions ==~~# Execute the following command to set the desktop system to automatically log in as the root user

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

|-

|}

<~~span id~~ol start="~~linux~~2" style="list-~~system~~style-~~adaptation~~type: decimal;"><li>Then restart the system, and the root user will automatically log in to the desktop</~~span~~li>~~== Linux System adaptation ==~~[[File:pi3b-img174.png]]

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

|-

|<big>'''~~Function~~Note that if you log in to the desktop system as the root user, you cannot use pulseaudio in the upper right corner to manage audio devices.'''|'''~~Debian11~~Also note that this is not a bug, since pulseaudio is not allowed to run as root.'''</big>|~~'''Ubuntu20.04'''~~}</ol><ol start="3" style="list-style-type: decimal;"><li>Execute the following command to set the desktop system to log in automatically with the orangepi user again</li> {|~~'''Ubuntu22.04'''~~class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~USB2~~sudo desktop_login.~~0x3~~sh orangepi'''|}</ol> === The method of disabling the desktop in the Linux desktop version system === # First enter the following command on the command line, '''OKPlease remember to add sudo permission'''~~|'''OK'''~~::{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~USB3~~sudo systemctl disable lightdm.~~0x1~~service'''|~~'''OK'''~~} <ol start="2" style="list-style-type: decimal;"><li>Then restart the Linux system and you will find that the desktop will not be displayed</li>~~|'''OK'''~~{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~M.2 NVMe SSD Start~~sudo reboot'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>The steps to reopen the desktop are as follows:<ol style="list-style-type: lower-alpha;"><li>First enter the following command on the command line, '''OKPlease remember to add sudo permission'''</li>~~|'''OK'''~~{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~WIFI~~sudo systemctl start lightdm.service'''|~~'''OK'''~~}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>After the command is executed, the desktop will be displayed</li></ol></li></ol> == Onboard LED Light Test Instructions == # There are three LED lights on the development board, one green light, one red light, and one PCIe light. The location is shown in the figure below: <div class="figure"> ::[[File:pi3b-img175.png]]~~|'''OK'''|'''OK'''~~</div>|<ol start="2" style="list-style-type: decimal;">|<li>'''~~Bluetooth~~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'''</li><li>The green LED light will keep blinking after the kernel is started, which is controlled by software.</li>~~|'''OK'''~~<li>The PCIe indicator will flash when there is data transmission on the PCIe interface.</li>~~|'''OK'''~~<li>The method of setting the green light on and off and flashing is as follows{|~~'''OK'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|<big>'''~~GPIO（40pin）~~Note that the following operations should be performed under the root user.'''</big>|~~'''OK'''~~}<ol style="list-style-type: lower-alpha;">~~|'''OK'''~~<li>First enter the setting directory of the green light</li>{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|root@orangepi:~# '''~~UART（40pin）~~cd /sys/class/leds/status_led'''|~~'''OK'''~~}</ol><ol start="2" style="list-style-type: lower-alpha;">~~|'''OK'''~~<li>The command to set the green light to stop flashing is as follows</li>{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|root@orangepi:/sys/class/leds/status_led# '''~~SPI（40pin）~~echo none > trigger'''|~~'''OK'''~~}</ol><ol start="3" style="list-style-type: lower-alpha;">~~|'''OK'''~~<li>The command to set the green light to be on is as follows</li>{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|root@orangepi:/sys/class/leds/status_led# '''~~I2C（40pin）~~echo default-on > trigger'''|~~'''OK'''~~}</ol><ol start="4" style="list-style-type: lower-alpha;">~~|'''OK'''~~<li>The command to set the green light to flash is as follows</li>{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|root@orangepi:/sys/class/leds/status_led# '''~~PWM（40pin）~~echo heartbeat > trigger'''|}</ol></li></ol> == Network connection test == === Ethernet port test === # First, insert one end of the network cable into the Ethernet interface of the development board, and connect the other end of the network cable to the router, and ensure that the network is unblocked# After the system starts, it will automatically assign an IP address to the Ethernet card through DHCP, '''OKNo other configuration is required'''~~|'''OK'''~~# The command to view the IP address in the Linux system of the development board is as follows ::{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~PWM fan interface~~ip addr show eth0'''|2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 :link/ether 4a:fe:2b:3d:17:1c brd ff:ff:ff:ff:ff:ff :inet '''OK192.168.1.150'''/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0 ::valid_lft 43150sec preferred_lft 43150sec :inet6 fe80::9a04:3703:faed:23be/64 scope link noprefixroute ::valid_lft forever preferred_lft forever|~~'''OK'''~~} ::{|~~'''OK'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|<big>'''~~3pin Debug serial port~~When using ifconfig to view the IP address, if the following information is displayed, it is because sudo is not added. The correct command is: sudo ifconfig'''</big> |orangepi@orangepi:~$ '''OKifconfig'''|Command 'ifconfig'is available in the following places * /sbin/ifconfig * /usr/sbin/ifconfig The command could not be located because '~~OK''~~/sbin:/usr/sbin'is not included in the PATH environment variable. This is most likely caused by the lack of administrative privileges associated with your user account. ifconfig: command not found|} ::{|~~'''OK'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|<big>'''There are three ways to check the IP address after the development board starts:''' '''1. Connect the HDMI display, then log in to the system and use the ip addr show eth0 command to view the IP address''' '''~~EMMC~~2. Enter the ip addr show eth0 command in the debugging serial terminal to view the IP address'''|'''3. If there is no debugging serial port and no HDMI display, you can also check the IP address of the development board's network port through the router's management interface. However, in this method, some people often cannot see the IP address of the development board normally. If you can't see it, the debug method looks like this:''' <ol style="list-style-type: upper-alpha;"><li>'''First check whether the Linux system has started normally. If the green light of the development board is blinking, it is generally started normally. If only the red light is on, it means that the system has not started normally;'''</li><li>'''Check whether the network cable is plugged in tightly, or try another network cable;'''</li><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>'''OKIf there is no router to replace, you can only connect to an HDMI display or use the debugging serial port to view the IP address'''</li></ol> |'''OKIn addition, it should be noted that the development board DHCP automatically assigns an IP address without any settings.'''</big>|} <ol start="4" style="list-style-type: decimal;"><li>The command to test the network connectivity is as follows, the '''ping''' command can be interrupted through the shortcut key of '''OKCtrl+C'''</li> {| class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~TF card start~~ping www.baidu.com -I eth0''' PING www.a.shifen.com (14.215.177.38) from 192.168.1.12 eth0: 56(84) bytes of data. 64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq=1 ttl=56 time=6.74 ms 64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq=2 ttl=56 time=6.80 ms 64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq=3 ttl=56 time=6.26 ms 64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq=4 ttl=56 time=7.27 ms ^C --- www.a.shifen.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3002ms rtt min/avg/max/mdev = 6.260/6.770/7.275/0.373 ms|~~'''OK'''~~}</ol> === WIFI connection test ===~~|'''OK'''~~{|~~'''OK'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|<big>'''~~HDMI Video~~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>|~~'''OK'''~~} ==== The server image connects to WIFI through commands ====~~|'''OK'''~~{|~~'''OK'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|<big>'''When the development board is not connected to Ethernet, not connected to HDMI display, but only connected to the serial port, it is recommended to use the commands demonstrated in this section to connect to the WIFI network. Because nmtui can only display characters in some serial port software (such as minicom), and cannot display the graphical interface normally. Of course, if the development board is connected to an Ethernet or HDMI ~~Audio~~display, you can also use the commands demonstrated in this section to connect to the WIFI network.'''</big>|~~'''OK'''~~} <ol style="list-style-type: decimal;"><li>First log in to the Linux system, there are the following three ways<ol style="list-style-type: lower-alpha;"><li>If the development board is connected with a network cable, you can remotely log in to the Linux system through ssh</li><li>If the development board is connected to the debugging serial port, you can use the serial port terminal to log in to the Linux system</li><li>If the development board is connected to the HDMI display, you can log in to the Linux system through the terminal displayed on the HDMI</li></ol></li><li>First use the nmcli dev wifi command to scan the surrounding WIFI hotspots</li>~~|'''OK'''~~{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~Camera~~nmcli dev wifi'''|} <div class="figure"> [[File:pi3b-img176.png]] </div></ol><ol start="3" style="list-style-type: decimal;"><li>Then use the nmcli command to connect to the scanned WIFI hotspot, where:</li> :a. '''OKwifi_name'''needs to be replaced with the name of the WIFI hotspot you want to connect to|:b. '''OKwifi_passwd'''needs to be replaced with the password of the WIFI hotspot you want to connect to :{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~LCD~~nmcli dev wifi connect wifi_name password wifi_passwd'''~~|''~~Device 'OKwlan0'successfully activated with 'cf937f88-ca1e-4411-bb50-61f402eef293'.|}</ol><ol start="4" style="list-style-type: decimal;"><li>You can view the IP address of wifi through the '''OKip addr show wlan0'''command {|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~Edp Display~~ip addr show wlan0'''|11: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 :link/ether 23:8c:d6:ae:76:bb brd ff:ff:ff:ff:ff:ff :inet '''OK192.168.1.11'''/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0 ::valid_lft 259192sec preferred_lft 259192sec :inet6 240e:3b7:3240:c3a0:c401:a445:5002:ccdd/64 scope global dynamic noprefixroute ::valid_lft 259192sec preferred_lft 172792sec :inet6 fe80::42f1:6019:a80e:4c31/64 scope link noprefixroute ::valid_lft forever preferred_lft forever|}</ol><ol start="5" style="list-style-type: decimal;"><li>Use the '''ping'''OKcommand to test the connectivity of the wifi network, and the '''|ping''' command can be interrupted through the shortcut key '''OKCtrl+C'''</li> {| class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~Gigabit Ethernet port~~ping www.orangepi.org -I wlan0''' PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0: 56(84) bytes of data. 64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=1 ttl=52 time=43.5 ms 64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=2 ttl=52 time=41.3 ms 64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=3 ttl=52 time=44.9 ms 64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=4 ttl=52 time=45.6 ms 64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=5 ttl=52 time=48.8 ms ^C --- www.orangepi.org ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 41.321/44.864/48.834/2.484 ms|~~'''OK'''~~}</ol> ==== The server image connects to WIFI in a graphical way ==== <ol style="list-style-type: decimal;"><li>First log in to the Linux system, there are the following three ways</li><ol style="list-style-type: lower-alpha;"><li>If the development board is connected with a network cable, you can remotely log in to [[Orange Pi 3B#SSH remote login development board|'''OKthe Linux system through ssh''']]</li><li>If the development board is connected to the debugging serial port, you can use the serial port terminal to log in to the Linux system (please use MobaXterm for the serial port software, and the minicom cannot display the graphical interface)</li><li>If the development board is connected to the HDMI display, you can log in to the Linux system through the HDMI display terminal</li></ol> <li>Then enter the nmtui command in the command line to open the wifi connection interface</li>{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|~~'''Network port status light'''|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''headphone playback'''|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''headphone recording'''|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''LED Light'''|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''RTC'''|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''GPU'''|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''NPU'''|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''VPU'''|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''watchdog test'''|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''Chromium Hard solution video'''|'''OK'''|'''OK'''~~|orangepi@orangepi:~$ '''OKnmtui'''

|}

</ol>

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

[[File:pi3b-img177.png]]</ol><~~span id~~ol start="~~the-format-of-linux-commands-in~~4" style="list-~~this~~style-~~manual~~type: decimal;"><li>Select '''Activate a connect''' and press Enter</~~span~~li>~~== The format of Linux commands in this manual ==~~

~~# In this manual,~~ [[File:pi3b-img178.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then you can see all ~~commands that need to be entered in~~ the ~~Linux system will be marked with the following box~~searched WIFI hotspots</li>

~~As shown below, the content in the yellow box indicates the content that needs special attention, except for the commands in it.~~<div class="figure">

~~<ol start="2" style="list-style-type: decimal;"><li>Description of the prompt type in front of the command<ol style="list-style-type~~[[File: ~~lower~~pi3b-~~alpha;">~~<li>The prompt in front of the command refers to the content of the red part in the box below, which is not part of the Linux command, so when entering the command in the Linux system, please do not enter the content of the red font part</li></ol>~~</li></ol>~~img179.png]]

</div></ol><ol start="6" style="list-style-type: decimal;"><li>Select the WIFI hotspot you want to connect to, then use the Tab key to position the cursor on '''~~orangepi@orangepi:~$ sudo apt update~~Activate'''and press Enter</li>

~~'''root@orangepi:~#''' '''vim /boot/boot.cmd'''~~<div class="figure">

~~'''test@test:~$ ssh~~ [~~mailto~~[File:~~root@192.168.1.36 root@192.168.1~~pi3b-img180.png]]~~xxx'''~~

</div></ol><ol start="7" style="list-style-type: decimal;"><li>Then a dialog box for entering a password will pop up, enter the corresponding password in '''~~root@test:~# ls~~Password'''and press Enter to start connecting to WIFI</li>

<~~ol start~~div class="2figure" ~~style="list-style-type: lower-alpha;">~~<li>'''root@orangepi:~$''' The prompt indicates that this command is entered in '''the Linux system of the development board'''. The $ at the end of the prompt indicates that the current user of the system is a normal user. When executing a privileged command, you need to add '''sudo'''</li><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:~$''' The 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, sudo needs to be added '''sudo'''</li><li>'''root@test:~#''' The 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>

~~<ol start="3" style="list-style-type: decimal;"><li>What are the commands that need to be entered?<ol style="list-style-type~~[[File: ~~lower~~pi3b-~~alpha;">~~<li>As shown below, '''the black bold part''' is the command that needs to be input, and the content below the command is the output content (some commands have output, some may not), and this part of the content does not need to be input</li></ol>~~</li></ol>~~img181.png]]

~~root@orangepi~~</div></ol><ol start="8" style="list-style-type:~~~# '''cat /boot~~decimal;"><li>After the WIFI connection is successful, a "*" will be displayed in front of the connected WIFI name</~~orangepiEnv.txt'''~~li>

~~'''verbosity~~<div class=~~7'''~~"figure">

~~bootlogo=false~~[[File:pi3b-img182.png]]

</div></ol><ol start="9" style="list-style-type: decimal;"><li>You can view the IP address of wifi through the '''~~console~~ip addr show wlan0''' command</li>{| class=~~serial~~"wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ip addr show wlan0'''

~~<ol start="2" style="list-style-type~~11: ~~lower-alpha~~wlan0: <">~~<li>As shown below~~BROADCAST,MULTICAST, some commands cannot be written in one line and will be placed on the next line. As long as the black and bold parts are all commands that need to be input. When these commands are entered into one lineUP, ~~the last "\~~LOWER_UP&~~quot~~gt; ~~of each line needs to be removed, this is not part of the command. In addition, there are spaces in different parts of the command, please don’t miss it</li></ol>~~mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~orangepi@orangepi~~:~~~$ '''echo \'''~~link/ether 24:8c:d3:aa:76:bb brd ff:ff:ff:ff:ff:ff

:inet '''~~"deb [arch~~192.168.1.11'''/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0

~~'''signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] \'''~~::valid_lft 259069sec preferred_lft 259069sec

~~'''https~~:inet6 240e:3b7:3240:c4a0:c401:a445:5002:ccdd/~~/download.docker.com/Linux/debian \'''~~64 scope global dynamic noprefixroute

~~'''$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null'''~~::valid_lft 259071sec preferred_lft 172671sec

~~<~~:inet6 fe80::42f1:6019:a80e:4c31/~~span>== Linux system login instructions ==~~64 scope link noprefixroute

::valid_lft forever preferred_lft forever|}</ol><~~span id~~ol start="10" style="~~linux-system-default-login-account~~list-~~and~~style-~~password~~type: decimal;"><li>Use the '''ping''' command to test the connectivity of the wifi network, and the '''ping''' command can be interrupted through the shortcut key '''Ctrl+C'''</~~span~~li>{| class="wikitable" style=~~= Linux system default login account and password ===~~"width:800px;" |-| orangepi@orangepi:~$ '''ping www.orangepi.org -I wlan0'''

~~{| class="wikitable"~~|-~~|'''Account'''|'''Passport'''~~|-~~|'''root'''|'''~~PING www.orangepi~~'''~~|-~~|'''orangepi'''|'''orangepi'''~~|}.org (182.92.236.130) from 192.168.1.49 wlan0: 56(84) bytes of data.

~~'''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~~64 bytes from 182.~~'''~~92.236.130 (182.92.236.130): icmp_seq=1 ttl=52 time=43.5 ms

'''When the wrong password is prompted, or there is a problem with the ssh connection, please note that as long as you are using the Linux image provided by Orange Pi, please do not suspect that the above password is wrong, but look for other reasons64 bytes from 182.~~'''~~92.236.130 (182.92.236.130): icmp_seq=2 ttl=52 time=41.3 ms

~~=== How to set automatic terminal login in Linux system~~ 64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=3 ttl=52 time=44.9 ms

~~# The Linux system automatically logs in to the terminal by default, and the default login user name is orangepi '''orangepi'''~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=4 ttl=52 time=45.6 ms

~~[[File~~64 bytes from 182.92.236.130 (182.92.236.130):~~pi3b-img171~~icmp_seq=5 ttl=52 time=48.~~png|351x198px]]~~8 ms

~~<ol start="2" style="list-style-type: decimal;"><li>Use the following command to set the root user to automatically log in to the terminal</li></ol>~~^C

--- www.orangepi~~@orangepi:~$ '''sudo auto_login_cli~~.~~sh root'''~~org ping statistics ---

~~<ol start="3" style="list-style-type: decimal;"><li>Use the following command to disable automatic login terminal</li></ol>~~5 packets transmitted, 5 received, 0% packet loss, time 4006ms

~~orangepi@orangepi:~$ '''sudo auto_login_cli~~rtt min/avg/max/mdev = 41.sh 321/44.864/48.834/2.484 ms|}</ol>

~~<ol start~~=~~"4" style~~=~~"list-style-type: decimal;"><li>Use the following command to set the orangepi user to automatically log in to the terminal again</li></ol>~~== Test method of desktop image ====

~~orangepi@orangepi:~$ '''sudo auto_login_cli.sh orangepi'''~~# Click the network configuration icon in the upper right corner of the desktop (please do not connect the network cable when testing WIFI)

~~=== Instructions for automatic login of Linux desktop version system ===~~ ~~# After the desktop system starts, it will automatically log in to the desktop without entering a password~~img183.png]]

~~<div class="figure">~~

~~[[File:pi3b-img172.png|576x324px|1]]~~

~~</div>~~

<li>~~Run~~ Click '''More networks''' in the ~~following command~~ pop-up drop-down box to ~~prohibit~~ see all scanned WIFI hotspots, and then select the ~~desktop system from automatically logging into the desktop~~WIFI hotspot you want to connect to.</li>~~</ol>~~ ~~orangepi@orangepi:~$ '''sudo disable_desktop_autologin.sh'''~~

[[File:pi3b-img184.png]]

</ol>

<li~~><p~~>Then ~~restart~~ enter the password of the ~~system~~ WIFI hotspot, and ~~a login dialog box will appear, at which point a [[\l|password]] is required~~ then click '''Connect''' to start connecting to ~~enter the system~~WIFI~~<div class="figure"~~li>

[[File:pi3b-~~img173~~img185.png~~|569x320px|IMG_256~~]]</ol><ol start="4" style="list-style-type: decimal;"><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</li>

[[File:pi3b-img186.png]]</~~div~~ol><ol start="5" style="list-style-type: decimal;"></li>If you can open other web pages after opening the browser, it means that the WIFI connection is normal</olli>

[[File:pi3b-img187-1.png]]</ol>~~=== The setting method of root user automatic login in Linux desktop version system ===~~

~~# Execute the following command~~ === How to set ~~the desktop system to automatically log in as the root user~~a static IP address ===

~~orangepi@orangepi~~{| class="wikitable" style="background-color:~$ #ffffdc;width:800px;" |-| <big>'''~~sudo desktop_login~~Please do not set a static IP address by modifying the /etc/network/interfaces configuration file.~~sh root~~'''</big>|}

<~~ol start~~span id="~~2" style="list~~use-the-nmtui-command-to-set-a-static-~~style~~ip-~~type: decimal;~~address"><li/span>~~Then restart the system, and~~ ==== Use the ~~root user will automatically log in~~ nmtui command to ~~the desktop</li></ol>~~set a static IP address ====

~~[[File:pi3b-img174.png|448x187px]]~~# First run the '''nmtui''' command

::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~Note that if you log in to the desktop system as the root user, you cannot use pulseaudio in the upper right corner to manage audio devices.~~nmtui'''|}

<ol start="2" style="list-style-type: decimal;"><li>Then select '''~~Also note that this is not~~ Edit a ~~bug, since pulseaudio is not allowed to run as root.~~connection'''and press Enter</li>

[[File:pi3b-img188.png]]

</ol>

<li>~~Execute~~ Then select the ~~following command~~ network interface that needs to set a static IP address, for example, to set the ~~desktop system to log in automatically with~~ static IP address of the ~~orangepi user again~~'''Ethernet''' interface, select '''Wired connection 1'''.</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img189.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select '''~~sudo desktop_login.sh orangepi~~Edit''' with the '''Tab'''key and press the Enter key</li>

[[File:pi3b-img190.png]]<~~span id~~/ol><ol start="5" style="~~the-method-of-disabling-the-desktop-in-the~~list-~~linux~~style-~~desktop-version-system~~type: decimal;"><~~/span~~li>~~=== The method of disabling~~ Then use the Tab key to move the cursor to the ~~desktop~~ '''<Automatic>''' position shown in the ~~Linux desktop version system ===~~figure below to configure IPv4</li>

~~# First enter the following command on the command line，~~[[File:pi3b-img191.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then press Enter, select '''~~Please remember to add sudo permission~~Manual'''with the up and down arrow keys, and press Enter to confirm</li>

~~orangepi@orangepi~~[[File:~~~$ '''sudo systemctl disable lightdm~~pi3b-img192.~~service'''~~png]]</ol><ol start="7" style="list-style-type: decimal;"><li>The display after selection is shown in the figure below</li>

[[File:pi3b-img193.png]]</ol><ol start="28" style="list-style-type: decimal;"><li>Then ~~restart~~ move the ~~Linux system and you will find that~~ cursor to the ~~desktop will not be displayed~~'''<Show>'''</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''sudo reboot'''~~pi3b-img194.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then press Enter, the following setting interface will pop up after entering</li>

[[File:pi3b-img195.png]]</ol><ol start="310" style="list-style-type: decimal;"><li>~~The steps to reopen~~ Then you can set the IP address (Addresses), gateway (Gateway) and DNS server address in the position shown in the ~~desktop~~ figure below (there are ~~as follows:~~many other setting options in it, please explore by yourself), '''<ol span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">Please set it according to your specific needs, the value set in the figure below is just an example<li/span>~~First enter the following command on the command line，'''Please remember to add sudo permission~~'''</li~~></ol></li></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img196.png]]</ol><ol start="11" style="list-style-type: decimal;"><li>After setting, move the cursor to'''~~sudo systemctl start lightdm.service~~<OK>'''in the lower right corner, and press Enter to confirm</li>

[[File:pi3b-img197.png]]</ol><ol start="212" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~After the command is executed,~~ Then click'''<Back>''' to return to the ~~desktop will be displayed~~previous selection interface</li~~></ol~~>

[[File:pi3b-img198.png]]</ol><~~span id~~ol start="~~onboard~~13" style="list-~~led~~style-~~light-test-instructions~~type: decimal;"><li>Then select '''Activate a connection''', then move the cursor to'''<OK>''', and finally click Enter</~~span~~li>~~== Onboard LED Light Test Instructions ==~~

~~# There are three LED lights on~~ [[File:pi3b-img199.png]]</ol><ol start="14" style="list-style-type: decimal;"><li>Then select the ~~development board~~network interface that needs to be set, ~~one green light~~such as '''Wired connection 1''', ~~one red light~~then move the cursor to'''<Deactivate>''', and ~~one PCIe light. The location is shown in the figure below:~~press Enter to disable '''Wired connection 1'''</li>

[[File:pi3b-img200.png]]<~~div class~~/ol><ol start="15" style="~~figure~~list-style-type: decimal;"><li>Then please do not move the cursor, and then press the Enter key to re-enable '''Wired connection 1''', so that the static IP address set earlier will take effect</li>

[[File:pi3b-~~img175~~img201.png~~|425x115px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\3.5.Onboard~~]]</ol><ol start="16" style="list-~~LED~~style-~~Light-Test-Instructions(1).jpg3.5.Onboard-LED-Light-Test-Instructions(1)]]~~type: decimal;"><li>Then you can exit nmtui through the'''<Back>''' and '''Quit''' buttons</li>

[[File:pi3b-img202.png]] [[File:pi3b-img203.png]]</~~div~~ol><ol start="217" style="list-style-type: decimal;"><li>~~~~Then through '''~~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~~ip addr show eth0'''~~</li><li>The green LED light will keep blinking after the kernel is started~~, ~~which is controlled by software.</li><li>The PCIe indicator will flash when there is data transmission on~~ you can see that the ~~PCIe interface.</li><li>The method~~ IP address of ~~setting~~ the ~~green light on and off and flashing is as follows~~network port has changed to the static IP address set earlier</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~Note that the following operations should be performed under the root user.~~ip addr show eth0'''

~~<ol style="list-style-type~~3: ~~lower-alpha~~eth0: <BROADCAST,MULTICAST,UP,LOWER_UP>">~~<li>First enter the setting directory of the green light</li></ol>~~mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~root@orangepi~~:~~~# '''cd~~ link/~~sys/class/leds/status'''~~ether 5e:ac:14:a5:92:b3 brd ff:ff:ff:ff:ff:ff

:inet '''<~~ol start="2"~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<li>The command to set the green light to stop flashing is as follows~~192.168.1.177</lispan><'''/~~ol>~~24 brd 192.168.1.255 scope global noprefixroute eth0

~~root@orangepi~~:~~/sys/class/leds/work# '''echo none > trigger'''~~:valid_lft forever preferred_lft forever

~~<ol start="3" style="list-style-type~~: ~~lower-alpha;"><li>The command to set the green light to be on is as follows</li><~~inet6 241e:3b8:3240:c3a0:e269:8305:dc08:135e/~~ol>~~64 scope global dynamic noprefixroute

~~root@orangepi~~:~~/sys/class/leds/work# '''echo default-on > trigger'''~~:valid_lft 259149sec preferred_lft 172749sec

~~<ol start="4" style="list-style-type~~: ~~lower-alpha;"><li>The command to set the green light to flash is as follows</li><~~inet6 fe80::957d:bbbe:4928:3604/~~ol>~~64 scope link noprefixroute

~~root@orangepi~~::valid_lft forever preferred_lft forever|}</~~sys/class/leds/work#~~ ol><ol start="18" style="list-style-type: decimal;"><li>Then you can test the connectivity of the network to check whether the IP address is configured OK, and the '''ping''' command can be interrupted through the shortcut key '''~~echo heartbeat > trigger~~Ctrl+C'''</li>

~~== Network connection test ==~~I eth0'''

~~=== Ethernet port test ===~~PING 192.168.1.47 (192.168.1.47) from 192.168.1.188 eth0: 56(84) bytes of data.

# First, insert one end of the network cable into the Ethernet interface of the development board, and connect the other end of the network cable to the router, and ensure that the network is unblocked~~# After the system starts, it will automatically assign an IP address to the Ethernet card through DHCP, '''No other configuration is required'''# The command to view the IP address in the Linux system of the development board is as follows~~64 bytes from 192.168.1.47: icmp_seq=1 ttl=64 time=0.233 ms

~~orangepi@orangepi~~64 bytes from 192.168.1.47:~~~$ '''ip addr show eth0'''~~icmp_seq=2 ttl=64 time=0.263 ms

264 bytes from 192.168.1.47: ~~eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000~~icmp_seq=3 ttl=64 time=0.273 ms

~~link/ether 4a~~64 bytes from 192.168.1.47:~~fe:2b:3d:17:1c brd ff:ff:ff:ff:ff:ff~~icmp_seq=4 ttl=64 time=0.269 ms

~~inet '''~~64 bytes from 192.168.1.~~150'''/24 brd 192.168.1~~47: icmp_seq=5 ttl=64 time=0.~~255 scope global dynamic noprefixroute eth0~~275 ms

~~valid_lft 43150sec preferred_lft 43150sec~~^C

~~inet6 fe80::9a04:3703:faed:23be/64 scope link noprefixroute~~--- 192.168.1.47 ping statistics ---

~~valid_lft forever preferred_lft forever~~5 packets transmitted, 5 received, 0% packet loss, time 4042ms

~~'''When using ifconfig~~ rtt min/avg/max/mdev = 0.233/0.262/0.275/0.015 ms|}</ol>

~~orangepi@orangepi:~$ '''ifconfig'''~~==== Use the nmcli command to set a static IP address ====

~~Command~~ <ol style="list-style-type: decimal;"><li>If you want to set the static IP address of the network port, please insert the network cable into the development board first. '''If you need to set the static IP address of WIFI, please connect the WIFI first, and then start to set the static IP address'''</li><li>Then use the '''nmcli con show''' command to view the name of the network device, as shown below<ol style="list-style-type: lower-alpha;"><li>'''orangepi''' is the name of the WIFI network interface (the names are not necessarily the same)</li><li>'''Wired connection 1''~~ifconfig~~' is ~~available in~~ the ~~following places~~name of the Ethernet interface</li>{| class="wikitable" style="width:800px;"|-|orangepi@orangepi:~$ '''nmcli con show''' NAMEUUID TYPE DEVICE '''orangepi'''cfc4f922-ae48-46f1-84e1-2f19e9ec5e2awifi wlan0 '''Wired connection 1'''9db058b7-7701-37b8-9411-efc2ae8bfa30ethernet eth0 |}</ol></li></ol>

* <ol start="3" style="list-style-type: decimal;"><li>Then enter the following command, where</~~sbin/ifconfig~~li>

* /usr/sbin/ifconfig:a. '''"Wired connection 1"''' means to set the static IP address of the Ethernet port. If you need to set the static IP address of the WIFI, please change it to the corresponding name of the WIFI network interface (you can get it through the '''nmcli con show''' command)

~~The command could not be located because~~ :b. After '''ipv4.addresse''~~/sbin:/usr/sbin~~' is ~~not included in~~ the ~~PATH environment variable.~~static IP address to be set, which can be modified to the value you want to set

~~This is most likely caused by~~ :c. '''ipv4.gateway''' indicates the ~~lack~~ address of ~~administrative privileges associated with your user account.~~the gateway

~~ifconfig~~: ~~command not found~~:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''nmcli con mod "Wired connection 1" \'''

'''~~There are three ways to check the IP address after the development board starts:~~ipv4.addresses "192.168.1.110" \'''

# '''~~Connect the HDMI display, then log in to the system and use the ip addr show eth0 command to view the IP address'''# '''Enter the ip addr show eth0 command in the debugging serial terminal to view the IP address'''# '''If there is no debugging serial port and no HDMI display, you can also check the IP address of the development board’s network port through the router’s management interface~~ipv4.gateway "192.168. ~~However, in this method, some people often cannot see the IP address of the development board normally~~1. ~~If you can't see it, the debug method looks like this:~~1" \'''

~~<ol style="list-style-type: upper-alpha;"><li>~~'''~~First check whether the Linux system has started normally~~ipv4.dns "8.8. ~~If the green light of the development board is blinking, it is generally started normally~~8. ~~If only the red light is on, it means that the system has not started normally;'''</li><li>'''Check whether the network cable is plugged in tightly, or try another network cable~~8"~~'''</li>~~<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 view the IP address'''</li></ol>~~ ~~'''In addition, it should be noted that the development board DHCP automatically assigns an IP address without any settings.~~\'''

'''ipv4.method "manual"'''

|}

</ol>

<li>~~The command to test the network connectivity is as follows,~~ Then restart the Linux system</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~ping~~sudo reboot''' ~~command can be interrupted through~~ |}</ol><ol start="5" style="list-style-type: decimal;"><li>Then re-enter the Linux system and use the ~~shortcut key of~~ '''~~Ctrl+C~~ip addr show eth0'''command to see that the IP address has been set to the desired value</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ip addr show eth0'''

~~orangepi@orangepi~~3:~~~$ '''ping www.baidu.com -I~~ eth0~~'''~~: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~PING www.a.shifen.com (~~:link/ether 5e:ae:14~~.215.177.38) from 192.168.1.12 eth0~~: ~~56(84) bytes of data.~~a5:91:b3 brd ff:ff:ff:ff:ff:ff

~~64 bytes from 14~~:inet '''192.~~215~~168.~~177~~1.~~38 (14~~110'''/32 brd 192.~~215~~168.~~177.38): icmp_seq=~~1 ~~ttl=56 time=6~~.~~74 ms~~110 scope global noprefixroute eth0

~~64 bytes from 14.215.177.38 (14.215.177.38)~~: ~~icmp_seq=2 ttl=56 time=6.80 ms~~:valid_lft forever preferred_lft forever

:inet6 240e:3b7:3240:c3a0:97de:1d01:b290:fe3a/64 ~~bytes from 14.215.177.38 (14.215.177.38): icmp_seq=3 ttl=56 time=6.26 ms~~scope global dynamic noprefixroute

~~64 bytes from 14.215.177.38 (14.215.177.38)~~: ~~icmp_seq=4 ttl=56 time=7.27 ms~~:valid_lft 259183sec preferred_lft 172783sec

^C:inet6 fe80::3312:861a:a589:d3c/64 scope link noprefixroute

::valid_lft forever preferred_lft forever|}</ol>

~~4 packets transmitted, 4 received, 0% packet loss, time 3002ms~~== SSH remote login development board ==

~~rtt min/avg/max/mdev~~ {| class="wikitable" style= ~~6.260/6~~"background-color:#ffffdc;width:800px;" |-| <big>'''Linux systems enable ssh remote login by default and allow the root user to log in to the system.~~770/7~~Before logging in with ssh, you first need to ensure that the Ethernet or wifi network is connected, and then use the ip addr command or check the router to obtain the IP address of the development board.~~275~~'''</~~0.373 ms~~big>|}

=== ~~WIFI connection test~~ SSH remote login development board under Ubuntu ===

~~'''Please do not connect~~ # Obtain the IP address of the development board# Then you can remotely log in to ~~WIFI by modifying~~ the ~~/etc/network/interfaces configuration file. There will be problems connecting to~~ Linux system through the ~~WIFI network in this way.'''~~ssh command

~~==== WIFI The server image connects~~ | test@test:~$ '''ssh [mailto:root@192.168.1.36 root@192.168.1.]xxx'''        (Need to ~~WIFI through commands ====~~be replaced with the IP address of the development board)

root@192.168.1.xx's password:        (Enter the password here, the default password is orangepi)|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~When~~ Note that when entering the password, the specific content of the ~~development board is~~ entered password will not ~~connected to Ethernet~~be displayed on the screen, please do not ~~connected to HDMI display~~think that there is any fault, ~~but only connected~~ just press Enter after inputting.'''</big>|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If you are prompted to refuse the ~~serial port~~connection, ~~it is recommended to use the commands demonstrated in this section to connect to the WIFI network. Because nmtui can only display characters in some serial port software (such~~ as ~~minicom), and cannot display~~ long as you are using the ~~graphical interface normally. Of course~~image provided by Orange Pi, if please do not suspect that the ~~development board~~ password orangepi is ~~connected to an Ethernet or HDMI display~~wrong, ~~you can also use the commands demonstrated in this section to connect to the WIFI network~~but look for other reasons.'''</big>|}

<ol ~~style~~start="~~list-style-type: decimal;~~3">~~<li>First log in to the Linux system, there are the following three ways<ol~~ style="list-style-type: ~~lower-alpha~~decimal;"><li>~~If the development board is connected with a network cable, you can remotely log~~ After successfully logging in to the ~~Linux~~ system ~~through ssh</li><li>If the development board is connected to the debugging serial port~~, ~~you can use~~ the ~~serial port terminal to log in to the Linux system</li><li>If the development board~~ display is ~~connected to the HDMI display, you can log~~ as shown in ~~to the Linux system through the terminal displayed on the HDMI</li></ol></li><li>First use~~ the ~~nmcli dev wifi command to scan the surrounding WIFI hotspots~~figure below</li>~~</ol>~~ ~~orangepi@orangepi:~$ '''nmcli dev wifi'''~~

[[File:pi3b-~~img176~~img204.png~~|575x250px|选区_011~~]]

</div>

~~<ol start~~{| class="3wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Then use~~ '''If ssh cannot log in to the ~~nmcli~~ Linux system normally, please first check whether the IP address of the development board can be pinged. If the ping is ok, you can log in to the Linux system through the serial port or HDMI display and then enter the following command on the development board and try again. Is it possible to connect ~~to the scanned WIFI hotspot, where~~:~~</li></ol>~~'''

~~a. '''wifi_name''' needs to be replaced with the name of the WIFI hotspot you want to connect to~~

b. root@orangepi:~# '''~~wifi_passwd~~reset_ssh.sh''' ~~needs to be replaced with the password of the WIFI hotspot you want to connect to~~

~~orangepi@orangepi:~$ '''nmcli dev wifi connect wifi_name password wifi_passwd'''~~

~~Device~~ '~~wlan0~~' ~~successfully activated with~~ '~~cf937f88~~If it still doesn't work, try to reset the system.'''</big>|}</ol>

~~<ol start~~=~~"4" style~~=~~"list-style-type: decimal;"><li>You can view the IP address of wifi through the '''ip addr show wlan0''' command</li></ol>~~= SSH remote login development board under Windows ===

~~orangepi@orangepi:~$ '''ip addr show wlan0'''~~# First obtain the IP address of the development board# Under Windows, you can use MobaXterm to remotely log in to the development board, first create a new ssh session

11: ~~wlan0~~: ~~<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~a. Open '''Session'''

~~link/ether 23~~:8c:~~d6:ae:76:bb brd ff:ff:ff:ff:ff:ff~~b. Then select '''SSH''' in '''Session Setting'''

~~inet~~ ::c. Then enter the IP address of the development board in the '''~~192.168.1.11~~Remote host'''~~/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0~~

~~valid_lft 259192sec preferred_lft 259192sec~~::d. Then enter the user name '''root''' or '''orangepi''' of the Linux system in '''Specify username'''

~~inet6 240e~~:~~3b7~~:~~3240:c3a0:c401:a445:5002:ccdd/64 scope global dynamic noprefixroute~~e. Finally click '''OK'''

~~valid_lft 259192sec preferred_lft 172792sec~~<div class="figure">

~~inet6 fe80~~::~~42f1~~[[File:~~6019:a80e:4c31/64 scope link noprefixroute~~pi3b-img205.png]]

~~valid_lft forever preferred_lft forever~~</div><ol start="3" style="list-style-type: decimal;"><li>Then you will be prompted to enter a password. The default passwords for root and orangepi users are orangepi</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <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>|}

~~5) Use the '''ping''' command to test the connectivity of the wifi network, and the '''ping''' command can be interrupted through the shortcut key '''Ctrl+C'''~~<div class="figure">

~~orangepi@orangepi~~[[File:~~~$ '''ping www~~pi3b-img206.~~orangepi.org -I wlan0'''~~png]]

~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0~~</div></ol><ol start="4" style="list-style-type: ~~56(84) bytes of data.~~decimal;"><li>After successfully logging in to the system, the display is as shown in the figure below</li>

~~64 bytes from 182.92.236.130 (182.92.236~~[[File:pi3b-img207.~~130): icmp_seq~~png]]</ol>

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~=~~2 ttl~~=~~52 time~~The method of uploading files to the Linux system of the development board ==~~41.3 ms~~

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~=== How to upload files to the development board Linux system in Ubuntu PC === ==== How to upload files using the scp command ==~~3 ttl~~=~~52 time~~=44 # Use the scp command to upload files from the Ubuntu PC to the Linux system of the development board.~~9 ms~~The specific commands are as follows

~~64 bytes from 182.92.236.130 (182.92.236~~::a.~~130)~~'''file_path''': ~~icmp_seq=4 ttl=52 time=45.6 ms~~need to be replaced with the path of the file to be uploaded

~~64 bytes from 182.92.236.130 (182.92.236~~::b.~~130)~~'''orangepi''': ~~icmp_seq=5 ttl=52 time=48.8 ms~~It is the user name of the Linux system of the development board, and it can also be replaced with other ones, such as root

^C::c. '''192.168.xx.xx''': It is the IP address of the development board, please modify it according to the actual situation

~~--- www~~::d.'''/home/orangepi~~.org ping statistics ---~~''': The path in the Linux system of the development board, which can also be modified to other paths

~~5 packets transmitted, 5 received, 0% packet loss, time 4006ms~~::{| class="wikitable" style="width:800px;" |-| test@test:~$ '''scp file_path orangepi@192.168.xx.xx:/home/orangepi/'''|}

~~rtt min/avg/max/mdev~~ <ol start="2" style= ~~41.321/44.864/48.834~~"list-style-type: decimal;"><li>If you want to upload a folder, you need to add the -r parameter</~~2.484 ms~~li>

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''scp -~~server~~r dir_path orangepi@192.168.xx.xx:/home/orangepi/'''|}</ol><ol start="3" style="list-~~image~~style-~~connects~~type: decimal;"><li>There are more usages of scp, please use the following command to view the man manual</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''man scp'''|}</ol>~~==== The server image connects to WIFI in a graphical way ====~~

~~1) First log in~~ ==== How to ~~the Linux system, there are the following three ways~~upload files using filezilla ====

~~<ol style="list-style-type: lower-alpha;"><li>If the development board is connected with a network cable, you can remotely log~~ # First install filezilla in ~~to [[\l|the Linux system through ssh]]</li>~~<li>If the development board is connected to the debugging serial port, you can use the serial port terminal to log in to the Linux system (please use MobaXterm for the serial port software, and the minicom cannot display the graphical interface)</li>~~<li>If the development board is connected to the HDMI display, you can log in to the Linux system through the HDMI display terminal</li></ol>~~Ubuntu PC

~~<!-~~::{| class="wikitable" style="width:800px;" |- | test@test:~$ '''sudo apt install --># y filezilla'''~~# Then enter the nmtui command in the command line to open the wifi connection interface~~|}

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~~~$ '''nmtui'''~~decimal;"><li>Then use the following command to open filezilla</li>

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

|-

|

test@test:~$ '''filezilla'''

|}

</ol>

<li>~~Enter~~ The interface after filezilla is opened is as follows, and the display under the ~~nmtui command to open~~ remote site on the ~~interface as shown below~~right is empty</li~~></ol~~>

~~[[File:pi3b-img177.png|345x215px]]~~<div class="figure">

~~<ol start="4" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Select '''Activate a connect''' and press Enter</li></ol>~~img208.png]]

~~[[File~~</div></ol><ol start="4" style="list-style-type:~~pi3b-img178.png|349x216px]]~~decimal;"><li>The method of connecting the development board is shown in the figure below</li>

<~~ol start~~div class="5figure" ~~style="list-style-type: decimal;"><li>Then you can see all the searched WIFI hotspots</li></ol~~>

~~<div class="figure">~~[[File:pi3b-img209.png]]

~~[[File~~</div></ol><ol start="5" style="list-style-type:~~pi3b-img179.png|426x270px|16]]~~decimal;"><li>Then choose to '''save the password''', and then click '''OK'''</li>

[[File:pi3b-img210.png]]</~~div~~ol>

<li>~~Select the WIFI hotspot you want to connect~~ Then choose toalways '''trust this host''', and then ~~use the Tab key to position the cursor on~~ click '''~~Activate~~OK''' ~~and press Enter~~</li~~></ol~~>

[[File:pi3b-~~img180~~img211.png~~|474x298px|17~~]]

</div></ol>

<li>~~Then a dialog box for entering a password will pop up~~After the connection is successful, ~~enter~~ you can see the directory structure of the development board Linux file system on the right side of the ~~corresponding password in '''Password''' and press Enter to start connecting to WIFI~~filezilla software</li~~></ol~~>

[[File:pi3b-~~img181~~img212.png~~|480x308px|18~~]]

</div></ol>

<li>~~After~~ Then select the ~~WIFI connection is successful~~path to be uploaded to the development board on the right side of the filezilla software, ~~a "*" will~~ and then select the file to be ~~displayed in front~~ uploaded on the Ubuntu PC on the left side of the ~~connected WIFI name~~filezilla software, then click the right mouse button, and then click the upload option to start uploading the file to the development board.</li~~></ol~~>

[[File:pi3b-~~img182~~img213.png~~|443x283px|C:\Users\orangepi\Desktop\用户手册插图\Zero3\未标题-9.jpg未标题-9~~]]

</div></ol>

<li>~~You~~ After the upload is complete, you can ~~view~~ go to the corresponding path in the ~~IP address~~ Linux system of ~~wifi through~~ the ~~'''ip addr show wlan0''' command~~development board to view the uploaded file</li~~></ol~~>

~~orangepi@orangepi:~$ '''ip addr show wlan0''~~<li>The method of uploading a folder is the same as that of uploading a file, so I won't go into details here</li></ol>

~~11: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~=== The method of uploading files from Windows PC to the Linux system of the development board ===

~~link~~</~~ether 24:8c:d3:aa:76:bb brd ff:ff:ff:ff:ff:ff~~span>==== How to upload files using filezilla ====

~~inet '''192.168.1.11'''/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0~~# First download the installation file of the Windows version of the filezilla software, the download link is as follows

~~valid_lft 259069sec preferred_lft 259069sec~~::{| class="wikitable" style="width:800px;" |-| '''https://filezilla-project.org/download.php?type=client'''|}

~~inet6 240e:3b7:3240:c4a0:c401:a445:5002:ccdd/64 scope global dynamic noprefixroute~~<div class="figure">

~~valid_lft 259071sec preferred_lft 172671sec~~::[[File:pi3b-img214.png]]

~~inet6 fe80::42f1:6019:a80e:4c31~~</~~64 scope link noprefixroute~~div><div class="figure">

~~valid_lft forever preferred_lft forever~~::[[File:pi3b-img215.png]]

</div><ol start="102" style="list-style-type: decimal;"><li>~~Use the '''ping''' command to test the connectivity of the wifi network~~The downloaded installation package is as follows, and ~~the '''ping''' command can be interrupted through the shortcut key '''Ctrl+C'''~~then double-click to install directly</li~~></ol~~>

~~orangepi@orangepi~~{| class="wikitable" style="width:~$ 800px;" |-| '''~~ping www~~FileZilla_Server_1.~~orangepi~~5.~~org~~ 1_win64-~~I wlan0~~setup.exe'''|}

~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0: 56(84) bytes of data.~~During the installation process, please select '''Decline''' on the following installation interface, and then select '''Next>'''

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~<div class=~~1 ttl=52 time=43.5 ms~~"figure">

~~64 bytes from 182.92.236.130 (182.92.236.130)~~[[File: ~~icmp_seq=2 ttl=52 time=41~~pi3b-img216.~~3 ms~~png]]

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~</div></ol><ol start="3 ~~ttl~~" style=~~52 time=44.9 ms~~"list-style-type: decimal;"><li>The interface after filezilla is opened is as follows, and the display under the remote site on the right is empty</li>

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~<div class=~~4 ttl=52 time=45.6 ms~~"figure">

~~64 bytes from 182.92.236.130 (182.92.236.130)~~[[File: ~~icmp_seq=5 ttl=52 time=48~~pi3b-img217.~~8 ms~~png]]

^C</div></ol><ol start="4" style="list-style-type: decimal;"><li>The method of connecting the development board is shown in the figure below:</li>

~~--- www.orangepi.org ping statistics ---~~<div class="figure">

[[File:pi3b-img209.png]] </div></ol><ol start="5 ~~packets transmitted~~" style="list-style-type: decimal;"><li>Then choose to '''save the password''', ~~5 received, 0% packet loss, time 4006ms~~and then click '''OK'''</li>

~~rtt min/avg/max/mdev~~ <div class= ~~41.321/44.864/48.834/2.484 ms~~"figure">

~~==== Test method of desktop image ====~~img218.png]]

~~# Click the network configuration icon in the upper right corner of the desktop (please do not connect the network cable when testing WIFI)~~</div></ol><ol start="6" style="list-style-type: decimal;"><li>Then choose to always '''trust this host''', and then click '''OK'''</li>

~~[[File:pi3b-img183.png|377x166px]]~~<div class="figure">

~~<ol start="2" style="list-style-type~~[[File: ~~decimal;"><li>Click '''More networks''' in the pop-up drop~~pi3b-~~down box to see all scanned WIFI hotspots, and then select the WIFI hotspot you want to connect to~~img219.~~</li></ol>~~png]]

~~[[File~~</div></ol><ol start="7" style="list-style-type:~~pi3b-img184.png|576x353px]]~~decimal;"><li>After the connection is successful, you can see the directory structure of the development board Linux file system on the right side of the filezilla software</li>

<~~ol start~~div class="3figure" ~~style="list-style-type: decimal;"><li>Then enter the password of the WIFI hotspot, and then click '''Connect''' to start connecting to WIFI</li></ol~~>

[[File:pi3b-~~img185~~img220.png~~|320x163px~~]]

</div></ol><ol start="48" style="list-style-type: decimal;"><li>~~After connecting~~ Then select the path to be uploaded to ~~WIFI~~the development board on the right side of the filezilla software, ~~you can open~~ and then select the ~~browser~~ file to ~~check whether you can access~~ be uploaded on the ~~Internet. The entrance~~ Ubuntu PC on the left side of the ~~browser is shown in~~ filezilla software, then click the right mouse button, and then click the upload option to start uploading the file to the ~~figure below~~development board.</li~~></ol~~>

~~[[File:pi3b-img186.png|576x308px]]~~<div class="figure">

~~<ol start="5" style="list~~[[File:pi3b-~~style-type: decimal;"><li>If you can open other web pages after opening the browser, it means that the WIFI connection is normal</li></ol>~~img221.png]]

~~[[File~~</div></ol><ol start="9" style="list-style-type:~~pi3b-img187.png|576x222px]]~~decimal;"><li>After the upload is complete, you can go to the corresponding path in the Linux system of the development board to view the uploaded file</li><li>The method of uploading a folder is the same as that of uploading a file</li></ol>

~~=== How to set a static IP address ===~~

~~'''Please do not set a static IP address by modifying the /etc/network/interfaces configuration file.'''~~== HDMI test ==

===~~= Use the nmtui command to set a static IP address =~~HDMI display test ===

# ~~First run the '''nmtui''' command~~Use HDMI to HDMI cable to connect Orange Pi development board and HDMI monitor

~~orangepi@orangepi~~:~~~$ '''nmtui'''~~:[[File:pi3b-img10.png]]

<li>~~Then select '''Edit a connection''' and press Enter~~After starting the Linux system, if the HDMI monitor has image output, it means that the HDMI interface is in normal use</li~~></ol~~>

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-~~img188~~| <big>'''Note that although many notebook computers have an HDMI interface, the HDMI interface of the notebook generally only has the output function, and does not have the function of HDMI in, that is to say, the HDMI output of other devices cannot be displayed on the notebook screen.~~png|227x247px]]~~'''

'''When you want to connect the HDMI of the development board to the HDMI port of the laptop, please make sure that your laptop supports the HDMI in function.'''<~~ol start~~/big>|}{| class="3wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Then select~~ '''When the ~~network interface that needs to set a static IP address~~HDMI is not displayed, ~~for example, to set~~ please check whether the ~~static IP address of~~ HDMI cable is plugged in tightly. After confirming that there is no problem with the ~~'''Ethernet''' interface~~connection, ~~select '''Wired connection 1~~you can change a different screen and try to see if it is displayed.'''.</libig>|}</ol>

~~[[File:pi3b~~

~~<ol start~~=~~"4" style~~=~~"list-style-type: decimal;"><li>Then select '''Edit''' with the '''Tab''' key and press the Enter key</li></ol>~~= HDMI to VGA display test ===

~~[[File~~<ol style="list-style-type: decimal;"><li>First, you need to prepare the following accessories<ol style="list-style-type:~~pi3b~~lower-~~img190.png|316x144px]]~~alpha;"><li>HDMI to VGA converter</li>

[[File:pi3b-img222.png]]</ol><ol start="52" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then use the Tab key to move the cursor to the '''<Automatic>''' position shown in the figure below to configure IPv4~~A VGA cable</li~~></ol~~>

[[File:pi3b-~~img191~~img223.png~~|575x240px~~]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>A monitor or TV that supports VGA interface</li></ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>HDMI to VGA display test as shown below</li>

~~<ol start="6" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Then press Enter, select '''Manual''' with the up and down arrow keys, and press Enter to confirm</li></ol>~~img224.png]]

~~[[File~~{| class="wikitable" style="background-color:~~pi3b~~#ffffdc;width:800px;" |-~~img192~~| <big>'''When using HDMI to VGA display, the development board and the Linux system of the development board do not need to make any settings, only the HDMI interface of the development board can display normally.~~png~~So if there is a problem with the test, please check whether there is a problem with the HDMI to VGA converter, VGA cable and monitor.'''</big>|~~576x237px]]~~}</ol>

~~<ol start~~=~~"7" style~~=~~"list-style-type: decimal;"><li>The display after selection is shown in the figure below</li></ol>~~= HDMI resolution setting method ===

~~[[File:pi3b-img193.png|575x240px]]~~# First open '''Display''' in '''Settings'''

~~<ol start="8" style="list~~::[[File:pi3b-~~style-type: decimal;"><li>Then move the cursor to the '''<Show>'''</li></ol>~~img225.png]]

~~[[File~~<ol start="2" style="list-style-type:~~pi3b-img194.png|576x241px]]~~decimal;"><li>Then you can see the current resolution of the system</li>

[[File:pi3b-img226.png]]</ol><ol start="93" style="list-style-type: decimal;"><li>~~Then press Enter,~~ Click the drop-down box of Resolution to see all resolutions currently supported by the ~~following setting interface will pop up after entering~~monitor</li~~></ol~~>

[[File:pi3b-~~img195~~img227.png~~|575x450px~~]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select the resolution you want to set, and click Apply</li>

[[File:pi3b-img228.png]]</ol><ol start="105" style="list-style-type: decimal;"><li>~~Then you can~~ After the new resolution is 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)，~~select '''~~Please set it according to your specific needs,~~ Keep the ~~value set in the figure below is just an example~~configuration'''</li~~></ol~~>

[[File:pi3b-~~img196~~img229.png~~|576x233px~~]]</ol>

~~<ol start~~=~~"11" style~~=~~"list-style-type: decimal;"><li>After setting, move the cursor~~ How to~~'''<OK>''' in the lower right corner, and press Enter to confirm</li></ol>~~use Bluetooth ==

~~[[File:pi3b~~=== Test method of desktop image ===

~~<ol start="12" style="list-style-type: decimal;"><li>Then click'''<Back>''' to return to~~ # Click the ~~previous selection interface</li></ol>~~Bluetooth icon in the upper right corner of the desktop.

::[[File:pi3b-~~img198~~img230.png~~|330x325px~~]]

<ol start="132" style="list-style-type: decimal;"><li>Then select ~~'''Activate a connection''', then move~~ the ~~cursor to'''<OK>''', and finally click Enter~~adapter</li~~></ol~~>

[[File:pi3b-~~img199~~img231.png~~|331x248px~~]]</ol><ol start="3" style="list-style-type: decimal;"><li>If there is a prompt on the following interface, please select '''Yes'''</li>

[[File:pi3b-img232.png]]</ol><ol start="144" style="list-style-type: decimal;"><li>Then ~~select the network interface that needs to be~~ set~~, such as~~ '''~~Wired connection 1~~Visibility Setting'''~~, then move the cursor to~~as '''~~<Deactivate>~~Always visible'''in the Bluetooth adapter settings interface, and ~~press Enter to disable '''Wired connection 1'''~~then close it</li~~></ol~~>

[[File:pi3b-~~img200~~img233.png~~|576x224px~~]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then open the configuration interface of the Bluetooth device</li>

[[File:pi3b-img234.png]]</ol><ol start="156" style="list-style-type: decimal;"><li>~~Then please do not move the cursor, and then press the Enter key to re-enable~~ Click '''~~Wired connection 1~~Search'''~~, so that~~ to start scanning the ~~static IP address set earlier will take effect~~surrounding Bluetooth device</li~~></ol~~>

[[File:pi3b-~~img201~~img235.png~~|576x224px~~]]</ol><ol start="7" style="list-style-type: decimal;"><li>Then select the Bluetooth device you want to connect to, and then click the right button of the mouse 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</li>

[[File:pi3b-img236.png]]</ol><ol start="168" style="list-style-type: decimal;"><li>~~Then you can exit nmtui through~~ When pairing, the pairing confirmation box will pop up in the upper right corner of thedesktop. Select '''~~<Back>~~Confirm''' ~~and '''Quit''' buttons~~to confirm. At this time, the mobile phone also needs to be confirmed</li~~></ol~~>

[[File:pi3b-~~img202~~img237.png~~|300x253px~~]] ~~[[File~~</ol><ol start="9" style="list-style-type:~~pi3b~~decimal;"><li>After pairing with the mobile phone, you can choose the paired Bluetooth device, then right-~~img203.png|227x252px]]~~click and select '''Send a File''' to start sending a picture to the phone</li>

[[File:pi3b-img238.png]]</ol><ol start="1710" style="list-style-type: decimal;"><li>~~Then through '''ip addr show eth0''', you can see that the IP address~~ The interface of the ~~network port has changed to the static IP address set earlier~~sending picture is shown below</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''ip addr show eth0'''~~pi3b-img239.png]]</ol>

~~3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~== USB interface test ==

~~link/ether 5e~~{| class="wikitable" style="background-color:ac#ffffdc;width:~~14:a5:92:b3 brd ff:ff:ff:ff:ff:ff~~800px;" |-| <big>'''The USB interface can be connected to a USB hub to expand the number of USB interfaces.'''</big>|}

~~inet '''192.168.1.177'''~~</~~24 brd 192.168.1.255 scope global noprefixroute eth0~~span>=== Connect the USB mouse or keyboard test ===

~~valid_lft forever preferred_lft forever~~# Insert the USB interface keyboard into the USB interface of the Orange Pi development board# Connect Orange PI development board to HDMI display# If the mouse or keyboard can operate normally, it means that the USB interface is working normally (the mouse can only be used in the desktop version of the system)

~~inet6 241e:3b8:3240:c3a0:e269:8305:dc08:135e~~</~~64 scope global dynamic noprefixroute~~span>

~~valid_lft 259149sec preferred_lft 172749sec~~=== Connect the USB storage device test ===

~~inet6 fe80::957d:bbbe:4928:3604/64 scope link noprefixroute~~# First insert the U disk or USB mobile hard disk into the USB interface of the Orange Pi development board# Execute the following command, if you can see the output of sdX, it means that the U disk is recognized successfully

~~valid_lft forever preferred_lft forever~~::{| class="wikitable" style="width:800px;"|-|orangepi@orangepi:~$ '''cat /proc/partitions | grep "sd*"''' major minor #blocksname 8030044160 '''sda''' 8130043119 '''sda1''' |}

<ol start="183" style="list-style-type: decimal;"><li>~~Then you can test~~ Use the ~~connectivity of the network~~ mount command to ~~check whether the IP address is configured OK, and~~ mount the U disk into '''~~ping~~/mnt''' ~~command~~ , and then you can ~~be interrupted through~~ view the ~~shortcut key '''Ctrl+C'''~~file in the U disk</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~ping 192.168.1.47 -I eth0~~sudo mount /dev/sda1 /mnt/'''

~~PING 192.168.1.47 (192.168.1.47) from 192.168.1.188 eth0~~orangepi@orangepi: ~~56(84) bytes of data.~~~$ '''ls /mnt/'''

~~64 bytes from 192~~test.~~168.1.47~~txt|}</ol><ol start="4" style="list-style-type: ~~icmp_seq~~decimal;"><li>After the mounting, you can view the capacity usage and mount point of the U disk through the '''df -h''' command</li>{| class=~~1 ttl~~"wikitable" style=~~64 time=0.233 ms~~"width:800px;" |-|orangepi@orangepi:~$ '''df -h | grep "sd"'''

~~64 bytes from 192.168.~~/dev/sda1     29G    208K    29G    1~~.47: icmp_seq~~% /mnt|}</ol>

~~64 bytes from 192.168.1.47: icmp_seq~~=~~3 ttl~~=~~64 time~~=~~0.273 ms~~USB wireless network card test ===

~~64 bytes from 192~~The currently '''tested''' USB wireless network cards are shown below.~~168~~Please test it by yourself for other models of USB wireless network cards.~~1.47: icmp_seq=4 ttl=64 time=0.269 ms~~If you cannot use it, you need to transplant the corresponding USB wireless network card driver

~~64 bytes from 192.168.1.47: icmp_seq~~{| class=~~5 ttl~~"wikitable" style=~~64 time=0~~"width:800px;text-align: center;"|-| No.~~275 ms~~| Model||-| 1| RTL8723BU

^CSupport 2.4G WIFI+BT4.0

| [[File:pi3b-~~-- 192.168.1~~img240.~~47 ping statistics --~~png]]|-| 2| RTL8811

~~5 packets transmitted, 5 received, 0% packet loss, time 4042ms~~Support 2.4G +5G WIFI

~~rtt min/avg/max/mdev = 0~~| [[File:pi3b-img241.~~233/0.262/0.275/0.015 ms~~png]]|-| 3| RTL8821CU

~~==== Use the nmcli command to set a static IP address ====~~Support 2.4G +5G WIFI

~~<ol style="list-style-type: decimal;"><li>If you want to set the static IP address of the network port, please insert the network cable into the development board first~~Support BT 4. ~~'''If you need to set the static IP address of WIFI, please connect the WIFI first, and then start to set the static IP address'''</li><li>Then use the '''nmcli con show''' command to view the name of the network device, as shown below<ol style="list-style-type: lower-alpha;"><li>'''orangepi''' is the name of the WIFI network interface (the names are not necessarily the same)</li><li>'''Wired connection 1''' is the name of the Ethernet interface</li></ol></li></ol>~~2

~~orangepi@orangepi:~$ '''nmcli con show'''~~| <div class="figure">

~~NAME UUID TYPE DEVICE~~[[File:pi3b-img242.png]]

~~'''orangepi''' cfc4f922-ae48-46f1-84e1-2f19e9ec5e2a wifi wlan0~~</div>|}

==== RTL8723BU test ==== # First insert the RTL8723BU wireless network card module into the USB interface of the development board# Then the Linux system will automatically load the RTL8723BU bluetooth and WIFI-related kernel modules, through the lsmod command, you can see that the following kernel modules have been automatically loaded ::{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''~~Wired connection 1~~lsmod''' ~~9db058b7~~Module Size Used by rfcomm 5734416 rtl8xxxu 1064960 rtk_btusb 614400 |}

<li>~~Then enter~~ Through the ~~following~~ dmesg command, ~~where~~you can see the loading information of the RTL8723BU module</li~~></ol~~>

~~<blockquote>a. '''&quot~~{| class="wikitable" style="width:800px;Wired connection 1"''' means to set the static IP address of the Ethernet port. If you need to set the static IP address of the WIFI, please change it to the corresponding name of the WIFI network interface (you can get it through the " |-| orangepi@orangepi:~$ '''~~nmcli con show~~dmesg''' ~~command)~~

b. ~~After '''ipv4~~.~~addresse''' is the static IP address to be set, which can be modified to the value you want to set~~....

c[ 83. ~~'''ipv4.gateway''' indicates the address of the gateway</blockquote>orangepi@orangepi~~438901] usb 2-1:~~~$ '''nmcli con mod "Wired connection 1" \'''~~new high-speed USB device number 2 using ehci-platform

~~'''ipv4.addresses "192.168~~[ 83.588375] usb 2-1: New USB device found, idVendor=0bda, idProduct=b720, bcdDevice= 2.~~110" \'''~~00

~~'''ipv4.gateway "192.168~~[ 83.588403] usb 2-1.: New USB device strings: Mfr=1~~" \'''~~, Product=2, SerialNumber=3

~~'''ipv4~~[ 83.~~dns "8~~588422] usb 2-1: Product: 802.~~8.8.8" \'''~~11n WLAN Adapter

~~'''ipv4~~[ 83.~~method "manual"'''~~588443] usb 2-1: Manufacturer: Realtek

~~<ol start="4" style="list~~[ 83.588460] usb 2-~~style-type~~1: SerialNumber: ~~decimal;"><li>Then restart the Linux system</li></ol>~~00e04c000001

~~orangepi@orangepi~~[ 83.601974] Bluetooth:~~~$ '''sudo reboot'''~~hci0: RTL: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723

~~<ol start~~[ 83.603894] Bluetooth: hci0: RTL: rom_version status=~~"5" style~~0 version=~~"list-style-type: decimal;"><li>Then re-enter the Linux system and use the '''ip addr show eth0'''command to see that the IP address has been set to the desired value</li></ol>~~1

~~orangepi@orangepi~~[ 83.603920] Bluetooth:~~~$ '''ip addr show eth0'''~~hci0: RTL: loading rtl_bt/rtl8723b_fw.bin

3[ 83.610108] Bluetooth: ~~eth0~~hci0: ~~<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~RTL: loading rtl_bt/rtl8723b_config.bin

~~link/ether 5e~~[ 83.611274] Bluetooth:aehci0:14RTL:~~a5:91:b3 brd ff:ff:ff:ff:ff:ff~~cfg_sz 68, total sz 22564

~~inet '''192~~[ 83.~~168~~658494] rtk_btusb: Realtek Bluetooth USB driver ver 3.1.~~110'''/32 brd 192~~6d45ddf.~~168.1.110 scope global noprefixroute eth0~~20220519-142432

~~valid_lft forever preferred_lft forever~~[ 83.658651] usbcore: registered new interface driver rtk_btusb

~~inet6 240e~~[ 83.667124] usb 2-1:~~3b7~~This Realtek USB WiFi dongle (0x0bda:~~3240:c3a0:97de:1d01:b290:fe3a/64 scope global dynamic noprefixroute~~0xb720) is untested!

~~valid_lft 259183sec preferred_lft 172783sec~~[ 83.667137] usb 2-1: Please report results to Jes.Sorensen@gmail.com

~~inet6 fe80~~[ 83.890140] usb 2-1:Vendor:~~3312:861a:a589:d3c/64 scope link noprefixroute~~Realtek

~~valid_lft forever preferred_lft forever~~[ 83.890153] usb 2-1: Product: 802.11n WLAN Adapter

~~== SSH remote login development board; ==~~1: rtl8723bu_parse_efuse: dumping efuse (0x200 bytes):

~~'''Linux systems enable ssh remote login by default and allow the root user to log in to the system~~. Before logging in with ssh, you first need to ensure that the Ethernet or wifi network is connected, and then use the ip addr command or check the router to obtain the IP address of the development board.~~'''~~....

~~~~==1: RTL8723BU rev E (SMIC) 1T1R, TX queues 3, WiFi= ~~SSH remote login development board under Ubuntu~~ 1, BT=1, GPS=0, HI PA=0

~~# Obtain the IP address of the development board# Then you can remotely log in to the Linux system through the ssh command~~[ 83.890417] usb 2-1: RTL8723BU MAC: 00:13:ef:f4:58:ae

~~test@test:~$ '''ssh~~ [~~mailto:root@192.168~~83.890421] usb 2-1: rtl8xxxu: Loading firmware rtlwifi/rtl8723bu_nic.~~36 root@192.168.1.]xxx''' (Need to be replaced with the IP address of the development board)~~bin

~~root@192.168~~[ 83.895289] usb 2-1: Firmware revision 35.~~xx's password:~~ 0 (~~Enter the password here, the default password is orangepi~~signature 0x5301)

~~'''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~~[ 84.~~'''~~050893] Bluetooth: hci0: RTL: fw version 0x0e2f9f73

~~'''If you are prompted to refuse the connection, as long as you are using the image provided by Orange Pi, please do not suspect that the password orangepi is wrong, but look for other reasons~~[ 84.~~'''~~266905] Bluetooth: RFCOMM TTY layer initialized

~~<ol start="3" style="list-style-type~~[ 84.266949] Bluetooth: ~~decimal;"><li>After successfully logging in to the system, the display is as shown in the figure below</li></ol>~~RFCOMM socket layer initialized

~~<div class="figure">~~[ 84.266999] Bluetooth: RFCOMM ver 1.11

[~~[File:pi3b-img204~~84.~~png|405x207px|L467QDF65C(YR79U]TH[TND]~~884270]usbcore: registered new interface driver rtl8xxxu

[ 84.912046] rtl8xxxu 2-1:1.2 wlx0013eff458ae: renamed from wlan0|}</~~div~~ol>~~'''If ssh cannot log in to the Linux system normally, please first check whether the IP address of the development board can be pinged. If the ping is ok,~~ <ol start="4" style="list-style-type: decimal;"><li>Then you can ~~log in to~~ see the ~~Linux system~~ RTL8723BU WIFI device node through the ~~serial port or HDMI display and then enter the following~~ '''sudo ifconfig''' command on . Please refer to [[Orange Pi 3B#WIFI connection test|'''the ~~development board~~ WIFI connection test chapter''']] for WIFI connection and ~~try again. Is it possible to connect~~testing methods</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ifconfig wlx0013eff458ae'''

~~root@orangepi~~wlx0013eff458ae:~~~# '''reset_ssh.sh'''~~flags=4099<UP,BROADCAST,MULTICAST> mtu 1500

~~'''If it still doesn't work, try to reset the system.'''~~::ether 00:13:ef:f4:58:ae txqueuelen 1000 (Ethernet)

~~=== SSH remote login development board under Windows ===~~::RX packets 0 bytes 0 (0.0 B)

~~# First obtain the IP address of the development board~~::RX errors 0 dropped 0 overruns 0 frame 0

2::TX packets 0 bytes 0 (0.0 B) ~~Under Windows, you can use MobaXterm to remotely log in to the development board, first create a new ssh session~~

~~a. Open~~ ::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0|}</ol><ol start="5" style="list-style-type: decimal;"><li>Then you can see the USB Bluetooth device through the '''~~Session~~hciconfig''' command</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt update && sudo apt install bluez'''

~~b. Then select~~ orangepi@orangepi:~$ '''~~SSH''' in '''Session Setting~~hciconfig'''

~~c. Then enter the IP address of the development board in the~~ hci0: Type: Primary Bus: '''~~Remote host~~USB'''

~~d. Then enter the user name '''root''' or '''orangepi''' of the Linux system in '''Specify username'''~~::BD Address: 00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16

~~e. Finally click '''OK'''~~::DOWN

~~<div class="figure">~~::RX bytes:1252 acl:0 sco:0 events:125 errors:0

~~[[File~~:~~pi3b-img205.png|553x280px~~:TX bytes:23307 acl:0 sco:0 commands:125 errors:0|~~14]]~~}</~~div~~ol><ol start="26" style="list-style-type: decimal;"><li>You can also see the Bluetooth icon on the desktop. At this time, Bluetooth has not been opened, so a red '''<~~/li~~span style="color:#FF0000">x<li/span>~~Then you~~ ''' will be ~~prompted to enter a password. The default passwords for root and orangepi users are orangepi~~displayed</li~~></ol~~>

[[File:pi3b-img243.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Click '''~~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.~~Turn Bluetooth On'''to turn on Bluetooth</li>

[[File:pi3b-img244.png]]<~~div class~~/ol><ol start="8" style="~~figure~~list-style-type: decimal;"><li>The display after turning on Bluetooth is as follows</li>

[[File:pi3b-~~img206~~img245.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Please refer to the [[Orange Pi 3B#How to use Bluetooth|~~578x150px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\just press Enter after inputting..jpgjust press Enter after inputting.~~'''Bluetooth use method''']]for Bluetooth test method, so I won't go into details here.</li></ol>

<~~/div><ol start="4" style~~span id="~~list-style~~rtl8811-~~type: decimal;~~test">~~<li>After successfully logging in to the system, the display is as shown in the figure below</li~~></olspan>

~~[[File:pi3b-img207.png|576x334px]]~~==== RTL8811 test ====

~~~~.~~== The method of uploading files to~~ # Then the Linux system of will automatically load the kernel modules related to RTL8811 WIFI, and you can see that the following kernel modules have been automatically loaded through the ~~development board ==~~lsmod command

::{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''lsmod'''Module Size Used by 8821cu 1839104 0 ~~=== How to upload files to the development board Linux system in Ubuntu PC ===~~|}

<~~span id~~ol start="~~how~~3" style="list-~~to-upload-files-using~~style-type: decimal;"><li>Through the~~-scp-~~dmesg command">, you can see the loading information of the RTL8811 module</~~span~~li>{| class="wikitable" style=~~== How to upload files using the scp command ====~~"width:800px;" |-| orangepi@orangepi:~$ '''dmesg'''

~~# Use the scp command to upload files from the Ubuntu PC to the Linux system of the development board~~[ 118. ~~The specific commands are as follows~~618194] usb 2-1: new high-speed USB device number 2 using ehci-platform

~~<blockquote>a~~[ 118. ~~'''file_path'''~~767152] usb 2-1: ~~need to be replaced with the path of the file to be uploaded~~New USB device found, idVendor=0bda, idProduct=c811, bcdDevice= 2.00

b[ 118. ~~'''orangepi'''~~767181] usb 2-1: ~~It is the user name of the Linux system of the development board~~New USB device strings: Mfr=1, ~~and it can also be replaced with other ones~~Product=2, ~~such as root~~SerialNumber=3

c[ 118. ~~'''192~~767199] usb 2-1: Product: 802.~~168.xx.xx''': It is the IP address of the development board, please modify it according to the actual situation~~11ac NIC

d[ 118. ~~'''/home/orangepi'''~~767219] usb 2-1: ~~The path in the Linux system of the development board, which can also be modified to other paths</blockquote>test@test~~Manufacturer:~~~$ '''scp file_path orangepi@192.168.xx.xx:/home/orangepi/'''~~Realtek

~~<ol start="~~[ 118.767235] usb 2~~" style="list~~-~~style-type~~1: SerialNumber: ~~decimal;"><li>If you want to upload a folder, you need to add the -r parameter</li></ol>~~123456

~~test@test:~$ '''scp -r dir_path orangepi@192.168.xx~~[ 119.xx500530] usbcore:~~/home/orangepi/'''~~registered new interface driver rtl8821cu

[ 119.525498] rtl8821cu 2-1:1.0 wlx1cbfced9d260: renamed from wlan0|}</ol><ol start="34" style="list-style-type: decimal;"><li>~~There are more usages of scp, please use~~ Then you can see the WiFi device node through the ~~following~~ '''sudo ifconfig''' command . Please refer to ~~view~~ the ~~man manual~~[[Orange Pi 3B#WIFI connection test|'''WiFi connection test chapter''']] for WIFI connection and testing methods. I won't go into details her</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ifconfig wlx1cbfced9d260'''

~~test@test~~wlx1cbfced9d260:~~~$ '''man scp'''~~flags=4099<UP,BROADCAST,MULTICAST> mtu 1500

~~==== How to upload files using filezilla ====~~::ether 1c:bf:ce:d9:d2:60 txqueuelen 1000 (Ethernet)

~~# First install filezilla in Ubuntu PC~~::RX packets 0 bytes 0 (0.0 B)

~~test@test~~:~~~$ '''sudo apt install -y filezilla'''~~:RX errors 0 dropped 0 overruns 0 frame 0

~~<ol start="2" style="list-style-type~~: ~~decimal;"><li>Then use the following command to open filezilla</li></ol>~~:TX packets 0 bytes 0 (0.0 B)

::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0|}</ol>

~~<ol start~~=~~"3" style~~=~~"list-style-type: decimal;"><li>The interface after filezilla is opened is as follows, and the display under the remote site on the right is empty</li></ol>~~== RTL8821CU test ====

~~<div class="figure">~~# First insert the rtl8821cu wireless network card module into the USB interface of the development board# Then use the '''lsusb''' command to see the device information of the rtl8821cu usb wifi module, please make sure that the USB module is not in Driver CDROM Mode

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-~~img208.png~~|~~576x453px~~orangepi@orangepi:~$ '''lsusb |~~截图 2022-12-03 19-04-40]]~~grep "Realtek"'''

~~</div>~~Bus 002 Device 003: ID 0bda:c820 Realtek Semiconductor Corp. 802.11ac NIC|}~~<ol start~~::{| class="4wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">~~<li>The method of connecting the development board is shown in the figure below</li></ol>~~|-| orangepi@orangepi:~$ '''lsusb | grep "Realtek"'''

Bus 002 Device 002: ID 0bda:1a2b Realtek Semiconductor Corp. RTL8188GU 802.11n WLAN Adapter ('''<~~div class~~span style="~~figure~~color:blue">Driver CDROM Mode''')

~~[[File:pi3b-img209.png|575x128px|图片565]]~~

<~~/div><ol start="5" style="list-style-type: decimal;"><li~~big>~~Then choose to~~ '''~~save~~ If the USB WIFI module seen by the lsusb command is in Driver CDROM Mode, please unplug the ~~password'''~~USB WIFI module again. If not, ~~and then click '''OK~~please manually execute the following command to switch to the next mode:'''</~~li></ol~~big>

~~[[File:pi3b-img210.png|249x181px]]~~

~~<ol start="6" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>Then choose to always~~ ~$ '''~~trust this host~~sudo usb_modeswitch -KW -v 0bda -p 1a2b'''~~, and then click '''OK'''</li></ol>~~|}

<~~div~~ ol start="3" style="list-style-type: decimal;"><li>The Linux system will automatically load the rtl8821cu bluetooth and wifi-related kernel modules, through the lsmod command, you can see that the following kernel modules have been automatically loaded</li>{| class="~~figure~~wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''lsmod'''Module Size Used by 8821cu 1839104 0 rtk_btusb 614400 |}</ol><ol start="4" style="list-style-type: decimal;"><li>Through the dmesg command, you can see the loading information of the rtl8821cu module</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''dmesg'''

~~[[File:pi3b-img211~~.~~png|278x150px|IMG_256]]~~.....

~~</div><ol start="7" style="list~~[ 57.083693] usb 2-~~style~~1: new high-~~type: decimal;"><li>After the connection is successful, you can see the directory structure of the development board Linux file system on the right side of the filezilla software</li></ol>~~speed USB device number 2 using ehci-platform

~~<div class~~[ 57.231888] usb 2-1: New USB device found, idVendor=~~"figure">~~0bda, idProduct=1a2b, bcdDevice= 2.00

[~~[File:pi3b-img212~~57.~~png|533x330px|IMG_256]~~231916]usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

~~</div><ol start="8" style="list~~[ 57.231937] usb 2-~~style-type~~1: Product: ~~decimal;">~~<li>Then select the path to be uploaded to the development board on the right side of the filezilla software, and then select the file to be uploaded on the Ubuntu PC on the left side of the filezilla software, then click the right mouse button, and then click the upload option to start uploading the file to the development board bingo.</li></ol>DISK

~~<div class="figure">~~[ 57.231956] usb 2-1: Manufacturer: Realtek

[~~[File~~57.242594] usb-storage 2-1:~~pi3b-img213~~1.~~png|485x380px|IMG_256]]~~0: USB Mass Storage device detected

~~</div>9) After the upload is complete, you can go to the corresponding path in the Linux system of the development board to view the uploaded file~~[ 57.245674] scsi host0: usb-storage 2-1:1.0

~~10) The method of uploading a folder is the same as that of uploading a file~~[ 58.069172] usb 2-1: USB disconnect, ~~so I won’t go into details here~~device number 2

~~=== The method of uploading files from Windows PC to the Linux system of the development board ===~~platform

~~==== How to upload files using filezilla =~~: New USB device found, idVendor=0bda, idProduct=c820, bcdDevice=2.00

~~# First download the installation file of the Windows version of the filezilla software~~[ 58.587827] usb 2-1: New USB device strings: Mfr=1, ~~the download link is as follows~~Product=2, SerialNumber=3

~~https~~[ 58.587833] usb 2-1:~~//filezilla-project.org/download~~Product: 802.~~php?type=client~~11ac NIC

~~<div class="figure">~~[ 58.587838] usb 2-1: Manufacturer: Realtek

[~~[File~~58.587844] usb 2-1:~~pi3b-img214.png|472x171px|C~~SerialNumber:~~\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-15.jpg未标题-15]]~~123456

~~</div><div class="figure">~~[ 58.610463] rtk_btusb: Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-142432

[~~[File:pi3b-img215~~58.~~png|393x283px|图片5552]~~610656]usbcore: registered new interface driver rtk_btusb

~~</div><ol start~~[ 58.634631] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=~~"2" style~~000c lmp_ver=~~"list-style-type: decimal;"><li>The downloaded installation package is as follows, and then double-click to install directly</li></ol>~~08 lmp_subver=8821

~~'''FileZilla_Server_1~~[ 58.~~5.1_win64-setup.exe'''~~636729] Bluetooth: hci0: RTL: rom_version status=0 version=1

~~During the installation process, please select '''Decline''' on the following installation interface, and then select '''Next>'''~~[ 58.636740] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin

~~<div class="figure">~~[ 58.664190] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin

[~~[File:pi3b-img216~~58.~~png|319x251px|IMG_256]~~664746]Bluetooth: hci0: RTL: cfg_sz 10, total sz 31990

~~</div><ol start="3" style="list-style-type~~[ 59.122471] Bluetooth: ~~decimal;"><li>The interface after filezilla is opened is as follows, and the display under the remote site on the right is empty</li></ol>~~hci0: RTL: fw version 0x829a7644

~~<div class="figure">~~[ 59.265513] usbcore: registered new interface driver rtl8821cu

[~~[File~~59.280119] rtl8821cu 2-1:~~pi3b-img217~~1.~~png|451x357px~~2 wlx90de80521825: renamed from wlan0|~~IMG_256]]~~}</ol>

~~</div>~~<ol start="45" style="list-style-type: decimal;"><li>~~The method of connecting~~ Then you can see the ~~development board is shown in~~ RTL8821CU WiFi device node through the ~~figure below:~~'''sudo ifconfig''' command. Please refer to the [[Orange Pi 3B#WIFI connection test|'''WiFi connection test chapter''']] for WIFI connection and testing methods.</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ifconfig wlx90de80521825'''

~~<div class~~wlx90de80521825: flags=~~"figure">~~4099<UP,BROADCAST,MULTICAST> mtu 1500

~~[[File~~:~~pi3b-img209.png|575x128px|图片565]]~~:ether 00:13:ef:f4:58:ae txqueuelen 1000 (Ethernet)

~~</div><ol start="5" style="list-style-type~~: ~~decimal;"><li>Then choose to '''save the password''', and then click '''OK'''</li></ol>~~:RX packets 0 bytes 0 (0.0 B)

~~<div class="figure">~~::RX errors 0 dropped 0 overruns 0 frame 0

~~[[File~~:~~pi3b-img218~~:TX packets 0 bytes 0 (0.~~png|207x146px|IMG_256]]~~0 B)

::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0|}</~~div~~ol>

<li>Then ~~choose to always~~ you can see the USB Bluetooth device through the '''~~trust this host~~hciconfig'''~~, and then click~~ command</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''OKsudo apt-get update && sudo apt-get install -y bluez'''~~</li></ol>~~

~~<div class="figure">~~orangepi@orangepi:~$ '''hciconfig'''

~~[[File~~hci0:~~pi3b-img219.png|221x109px|IMG_256]]~~Type: Primary Bus: '''USB'''

~~</div>~~::BD Address: 00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16 ~~<ol start="7" style="list-style-type~~: ~~decimal;"><li>After the connection is successful, you can see the directory structure of the development board Linux file system on the right side of the filezilla software</li></ol>~~:DOWN

~~<div class="figure">~~::RX bytes:1252 acl:0 sco:0 events:125 errors:0

~~[[File~~:~~pi3b~~:TX bytes:23307 acl:0 sco:0 commands:125 errors:0|}</ol><ol start="7" style="list-~~img220~~style-type: decimal;"><li>Bluetooth icons can also be seen on the desktop.~~png|446x329px|图片3]]~~At this time, Bluetooth has not been turned on, so a red '''x''' will be displayed</li>

[[File:pi3b-img243.png]]</~~div~~ol>

<li>~~Then select the path~~ Click '''Turn Bluetooth On''' to ~~be uploaded to the development board on the right side of the filezilla software, and then select the file to be uploaded on the Windows PC~~ turn on ~~the left side of the filezilla software, then click the right mouse button, and then click the upload option to start uploading the file to the development board bingo~~Bluetooth</li~~></ol~~>

[[File:pi3b-img244.png]]<~~div class~~/ol><ol start="9" style="~~figure~~list-style-type: decimal;"><li>The display after turning on Bluetooth is as follows</li>

[[File:pi3b-~~img221~~img245.png]]</ol><ol start="10" style="list-style-type: decimal;"><li>Please refer to the [[Orange Pi 3B#How to use Bluetooth|~~501x369px|IMG_256~~'''Bluetooth use chapter''']]for the Bluetooth test method. I won't go into details here</li></ol>

<~~/div><ol start~~span id="~~9" style="list~~usb-~~style~~camera-~~type: decimal;~~test">~~<li>After the upload is complete, you can go to the corresponding path in the Linux system of the development board to view the uploaded file</li><li>The method of uploading a folder is the same as that of uploading a file</li~~></olspan>

~~~~== ~~HDMI test~~ USB Camera Test ===

~~=== HDMI display test ===~~# First, you need to prepare a USB camera that supports 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

~~# Use HDMI to HDMI cable to connect Orange Pi development board and HDMI monitor~~ ::[[File:pi3b-~~img10~~img13.png~~|199x129px~~]]

<li>~~After starting the Linux system, if the HDMI monitor has image output, it means~~ You can see that the ~~HDMI interface~~ USB camera's device node information is ~~in normal use~~/dev/video0 through the v4l2-ctl command</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''v4l2-ctl --list-devices'''

Q8 HD Webcam: Q8 HD Webcam ('''Note that although many notebook computers have an HDMI interface, the HDMI interface of the notebook generally only has the output function, and does not have the function of HDMI in, that is to say, the HDMI output of other devices cannot be displayed on the notebook screen.usb'''-fc880000.usb-1):

:'''~~When you want to connect the HDMI of the development board to the HDMI port of the laptop, please make sure that your laptop supports the HDMI in function.~~/dev/video0'''

'''When the HDMI is not displayed, please check whether the HDMI cable is plugged in tightly. After confirming that there is no problem with the connection, you can change a different screen and try to see if it is displayed.''':/dev/video1

~~~~| <~~/span~~big>~~=== HDMI to VGA display test ===~~'''Note that the l in v4l2 is a lowercase letter l, not the number 1.'''

~~<ol style="list-style-type: decimal;">~~

~~<li>First, you need to prepare the following accessories~~

~~<ol style="list-style-type: lower-alpha;">~~

~~<li>HDMI to VGA converter</li></ol>~~

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

~~[[File~~'''In addition, the serial number of the video is not necessarily video0, please refer to what you actually see.'''</big>|}</ol><ol start="3" style="list-style-type:~~pi3b-img222~~decimal;"><li>In the desktop system, Cheese can be used to directly open the USB camera.~~png|155x104px]]~~The method of opening Cheese is shown in the figure below:</li>

~~<ol start="2" style="list-style-type~~[[File: ~~lower~~pi3b-~~alpha;"><li>A VGA cable</li></ol>~~img246.png]]

~~[[File~~The interface after Cheese turns on the USB camera is shown in the figure below:~~pi3b-img223.png|148x133px]]~~

[[File:pi3b-img247.png]]</ol><ol start="34" style="list-style-type: decimal;"><li>How to test the USB camera using fswebcam<ol style="list-style-type: lower-alpha;"><li>~~A monitor or TV that supports VGA interface~~Install fswebcam</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo''' '''apt update'''

~~<!--~~ orangepi@orangepi:~$ '''sudo apt-get install -y fswebcam'''|}</ol><ol start="2" style="list-style-type: ~~decimal~~lower-alpha;"><li>After installing fswebcam, you can use the following command to take pictures<ol style="list-style-type: none;"><li>~~HDMI~~ a) -d The option is used to ~~VGA display test as shown below~~specify the device node of the USB camera</li><li>b) --no-banner Used to remove the watermark of photos</olp></li><li>c) -r The option is used to specify the resolution of the photo</li><li>d) -S The option is used to set the number of previous frames to skip</li><li>e) ./image.jpg The name and path for setting the generated photos</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo''' '''fswebcam -d /dev/video0 \'''

'''--no-banner -r 1280x720 -S 5 ./image.jpg'''|}</ol></li></ol><ol start="3" style="list-style-type: lower-alpha;"><li>In the desktop version of the Linux system, you can directly view the captured pictures through the HDMI display</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''scp image.jpg''' [~~[File~~mailto:test@192.168.1.55:~~pi3b-img224~~/home/test test@192.168.1.~~png~~55:/home/test] '''（Modify the IP address and path according to the actual situation）'''|~~576x339px]]~~}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>In the desktop version of the Linux system, you can directly view the captured pictures through the HDMI display</li></ol></li></ol>

'''When using HDMI to VGA display, the development board and the Linux system of the development board do not need to make any settings, only the HDMI interface of the development board can display normally. So if there is a problem with the test, please check whether there is a problem with the HDMI to VGA converter, VGA cable and monitor.'''== Audio Test ==

=== ~~HDMI resolution setting method~~ Test audio methods in the desktop system ===

# First open ~~'''Display''' in '''Settings'''~~the file manager

::[[File:pi3b-~~img225~~img248.png~~|576x370px~~]]

<li>Then find the following file (if there is no audio file in the system, you can ~~see the current resolution of~~ upload a audio file to the systemby yourself)</li~~></ol~~>

~~[[File:pi3b-img226.png|382x254px]]~~<div class="figure">

[[File:pi3b-img249.png]]

</div></ol>

<li>~~Click~~ Then select the ~~drop-down box of Resolution~~ audio.wav file, right click and select open with vlc to ~~see all resolutions currently supported by the monitor~~start playing</li>~~</ol>~~ ~~[[File:pi3b-img227.png|415x274px]]~~

[[File:pi3b-img250.png]]

</ol>

<li>~~Then select the resolution you want~~ Methods to ~~set,~~ switch different audio equipment such as HDMI playback and ~~click Apply~~headset playback<ol style="list-style-type: lower-alpha;"><li>First open the volume control interface</olli>

[[File:pi3b-~~img228~~img251.png~~|415x277px~~]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>When playing audio, the audio equipment options that play software can be used will be displayed in '''Playback'''. As shown in the figure below, which audio equipment you need to play here can be set.</li>

[[File:pi3b-img252.png]]</ol ~~start="5" style="list-style-type: decimal;"~~></li>~~After the new resolution is set, select '''Keep the configuration'''~~</liol></olspan>

~~[[File:pi3b-img229.png|447x243px]]~~=== How to play audio with commands ===

== ~~How to use Bluetooth~~ == Headphone interface play audio test ====

~~=== Test method of desktop image ===~~the development board

~~# Click the Bluetooth icon in the upper right corner of the desktop.~~ ::[[File:pi3b-~~img230~~img253.png~~|330x128px~~]]

<li>Then ~~select~~ you can check the ~~adapter~~sound card device supported by the Linux system through the '''aplay -l''' command. From the output below, it can be seen that '''card 0''' is the sound card device with RK809, which is the sound card device of the headset</li~~></ol~~>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img231.png~~|~~375x165px]]~~orangepi@orangepi:~$ '''aplay -l'''

<~~ol start="3" style="list-style-type: decimal;"><li>If there is a prompt below, select '''Yes'''</li~~p>**** List of PLAYBACK Hardware Devices ****</olp>

'''card 0: rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [~~File:pi3b~~dailink-multicodecs rk817-hifi-~~img232.png|248x85px]~~0]'''

~~<ol start="4" style="list-style-type~~: ~~decimal;"><li>Then set~~ '''~~Visibility Setting''' as '~~Subdevices: 0/1''~~Always visible~~'~~'' in the Bluetooth adapter settings interface, and then close it</li></ol>~~

~~[[File~~:~~pi3b-img233.png|243x229px]]~~'''Subdevice #0: subdevice #0'''

~~<ol start="5" style="list~~card 1: rockchiphdmi [rockchip,hdmi], device 0: fe400000.i2s-i2s-~~style~~hifi i2s-~~type: decimal;"><li>Then open the configuration interface of the Bluetooth device</li></ol>~~hifi-0 [fe400000.i2s-i2s-hifi i2s-hifi-0]

~~[[File~~:~~pi3b-img234.png|438x179px]]~~Subdevices: 0/1

~~<ol start="6" style="list-style-type~~: ~~decimal;"><li>Click '''Search''' to start scanning the surrounding Bluetooth device</li></ol>~~Subdevice #0: subdevice #0

~~[[File~~:~~pi3b~~Subdevice #0: subdevice #0|}</ol><ol start="3" style="list-~~img235~~style-type: decimal;"><li>Then use the '''aplay''' command to play the audio file that comes with the system.~~png|322x217px]]~~If the headset can hear the sound, it means that the hardware can be used normally</li>

~~<ol start~~{| class="7wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then select the Bluetooth device you want to connect. If you right~~ |-~~click the mouse, you will pop up the operating interface of this Bluetooth device. Select~~ | orangepi@orangepi:~$ '''~~Pair~~aplay -D hw:0,0 /usr/share/sounds/alsa/audio.wav''' ~~to start pairing. Here, it is demonstrated with the Android phone</li></ol>~~

~~[[File~~Playing WAVE 'audio.wav' :~~pi3b~~Signed 16 bit Little Endian, Rate 44100 Hz, Stereo|}</ol>

~~<ol start~~=~~"8" style~~=~~"list-style-type: decimal;">~~<li>When pairing, the pairing confirmation box will pop up in the upper right corner of the desktop. Select '''Confirm''' to confirm. At this time, the mobile phone also needs to be confirmed</li></ol>== HDMI Audio Play Test ====

~~[[File:pi3b-img237~~# First use the HDMI to HDMI cable to connect the Orange PI development board to the TV (other HDMI displays need to ensure that the audio can be played)# Then check the sound card serial number of HDMI.~~png|417x152px]]~~From the output below, you can know that the HDMI sound card is '''card 1'''

~~<ol start~~::{| class="9wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>After pairing with the mobile phone, you can choose the paired Bluetooth device, then right~~ |-~~click and select~~ | orangepi@orangepi:~$ '''~~Send a File~~aplay -l''' ~~to start sending a picture to the phone</li></ol>~~

~~[[File:pi3b-img238.png|439x259px]]~~**** List of PLAYBACK Hardware Devices ****

~~<ol start="10" style="list~~card 0: rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-~~style~~hifi-~~type: decimal;"><li>The interface of the sending picture is shown below</li></ol>~~0]

~~[[File~~:~~pi3b-img239.png|437x253px]]~~Subdevices: 0/1

~~== USB interface test ==~~:Subdevice #0: subdevice #0

'''~~The USB interface can connect USB Hub to expand the number of USB interfaces~~card 1: rockchiphdmi [rockchip,hdmi], device 0: fe400000.i2s-i2s-hifi i2s-hifi-0 [fe400000.i2s-i2s-hifi i2s-hifi-0]'''

~~<~~:'''Subdevices: 0/~~span>=== Connect the USB mouse or keyboard test ===~~1'''

:'''Subdevice # ~~Insert the keyboard of the USB interface into the USB interface of Orange PI development board~~0: subdevice # ~~Connect Orange PI development board to HDMI display# If the mouse or keyboard can normal operating systems, the USB interface is used normally (the mouse can only be used in the system of the desktop version)~~0'''

~~~~:'''Subdevice #0: subdevice #0'''~~=== Connect the USB storage device test ===~~|}

~~# First insert~~ <ol start="3" style="list-style-type: decimal;"><li>Then use the ~~U disk or USB mobile hard disk into~~ '''aplay''' command to play the ~~USB interface of Orange PI development board# Execute~~ audio file that comes with the ~~following command~~system. If ~~you~~ the HDMI display or television can ~~see~~ hear the ~~output of sdX~~sound indicates that the hardware can be used normally</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''aplay -D hw:1, 0 /usr/share/sounds/alsa/audio.wav'''|}</ol>

~~orangepi@orangepi:~$ '''cat /proc/partitions | grep "sd*"'''~~=== Use the command to test the recording method ===

~~major minor~~ #~~blocks name~~Orange Pi 3B development board does not have MICs, and can only record audio through headphones with MIC function. After inserting the headset with the MIC function into the development board, the command below will record a piece of audio through the headset

8 ::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''amixer -c 0 ~~30044160~~ cset name='Capture MIC Path''Main Mic'~~sda~~'''

~~8 1 30043119~~ orangepi@orangepi:~$ '''~~sda1~~arecord -D hw:0,0 -d 5 -f cd -t wav /tmp/test.wav'''|}

<~~ol start~~span id="~~3" style="list~~temperature-~~style-type: decimal;~~sensor">~~<li>Use the mount command to mount the U disk into '''/mnt''', and then you can view the file in the U disk</li~~></olspan>

~~orangepi@orangepi:~$ '''sudo mount /dev/sda1 /mnt/'''~~== Temperature Sensor ==

~~orangepi@orangepi~~# The command to view the system temperature sensor is:~~~$ '''ls /mnt/'''~~

~~test.txt~~::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sensors'''

~~<ol start="4" style="list~~soc_thermal-~~style~~virtual-~~type: decimal;"><li>After the mounting, you can view the capacity of the U disk through the '''df -h''' command and the mounting point</li></ol>~~0

~~orangepi@orangepi~~Adapter:~~~$ '''df -h | grep "sd"'''~~Virtual device

~~/dev/sda1 29G 208K 29G 1% /mnt~~temp1: +41.9°C (crit = +115.0°C)

~~~~

~~=== USB wireless network card test ===~~

The currently '''tested''' USB wireless network cards are shown below. Please test it by yourself for other models of USB wireless network cards. If you cannot use it, you need to transplant the corresponding USB wireless network card drivergpu_thermal-virtual-0

~~{| class="wikitable"~~|-~~| No.| Model~~||-~~| 1| RTL8723BU~~Adapter: Virtual device

~~Support 2.4G WIFI~~temp1: +~~BT4~~43.08°C|}

<ol start="2" style="list-style-type: decimal;"><li>The command to view the current temperature of the nvme ssd solid state drive is:{| ~~[[File~~class="wikitable" style="width:~~pi3b-img240.png]]~~800px;"

|-

| 2orangepi@orangepi:~$ '''sudo smartctl -a /dev/nvme0 | ~~RTL8811~~grep "Temperature:"'''Temperature: '''40 Celsius'''|}</li></ol>

~~Support 2.4G +5G WIFI~~

~~| [[File:pi3b-img241.png]]~~|-~~| 3| RTL8821CU~~== 40 Pin interface pin explanation ==

~~Support 2.4G +5G WIFI~~# Orange Pi 3B Development board 40 Pin interface pins, please refer to the figure below

~~Support BT 4.2~~<div class="figure">

~~| <div class="figure">~~ ::[[File:pi3b-~~img242~~img254.png~~|tb_imag e_share_1670833201 123~~]]

</div>

|}<ol start="2" style="list-style-type: decimal;"><li>The function of the Orange Pi 3B development board 40 PIN interface pins is shown in the table below.<ol style="list-style-type: lower-alpha;"><li>Below is a complete pins of 40pin</li>

[[File:pi3b-img255-1.png]]</ol><~~span id~~ol start="2" style="~~rtl8723bu~~list-style-type: lower-~~test~~alpha;"><li>The following form is a picture on the left half of the full table above, which can be seen clearly</~~span~~li>~~==== RTL8723BU test ====~~

~~# First insert~~ [[File:pi3b-img256-1.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The following form is a picture on the ~~RTL8723BU wireless network card module into the USB interface~~ right half of the ~~development board# Then the Linux system will automatically load the RTL8723BU Bluetooth and WiFi -related kernel modules. You~~ top table above, which can ~~see that the kernel module below is automatically loaded through the lsmod command~~be seen clearly</li>

~~orangepi@orangepi~~[[File:~$ pi3b-img257-1.png]]</ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>There are a total of '''~~lsmod~~28''' GPIO ports in the 40pin interface. The voltage of all GPIO ports is '''3.3v'''</li></ol>

~~Module Size Used by~~

~~rfcomm 57344 16~~== How to install wiringOP ==

~~rtl8xxxu 106496 0~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that wiringOP has been pre -installed in the Linux image released by Orange Pi. Unless wiringOP's code is updated, it is not necessary to re -download and install. Just use it directly.'''

~~rtk_btusb 61440 0~~

~~<ol start="3" style="list-style~~'''The storage path of the compiled wiringOP's Deb is wrapped in Orangepi-~~type~~Build: ~~decimal;"><li>You can see the loading information of the RTL8723BU module through the dmesg command</li></ol>~~'''

~~orangepi@orangepi:~$~~ '''~~dmesg~~orangepi-build/external/cache/debs/arm64/wiringpi_x.xx.deb'''

~~......~~

~~[ 83~~'''After entering the system, you can run the gpio readall command.~~438901] usb 2~~If you can see the output below, it means that wiringOP is pre -~~1: new high-speed USB device number 2 using ehci-platform~~installed and can be used normally.'''</big>

~~[ 83.588375] usb 2-1: New USB device found, idVendor~~<div class=~~0bda, idProduct=b720, bcdDevice= 2.00~~"figure">

[ 83[File:pi3b-img258-1.~~588403~~png]] ~~usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3~~

~~[ 83~~</div><big>'''wiringOP is currently mainly adapted to the functions of setting GPIO port input and output, setting GPIO port output high and low levels, and setting up and down pull-down resistors.~~588422] usb 2-1: Product: 802~~Functions such as hardware PWM are not available.~~11n WLAN Adapter~~'''</big>|}

~~[ 83.588443] usb 2-1: Manufacturer: Realtek~~# Download the code of wiringOP

~~[ 83.588460] usb 2~~::{| class="wikitable" style="width:800px;" |-~~1: SerialNumber~~| orangepi@orangepi: ~~00e04c000001~~~$ '''sudo apt update'''

~~[ 83.601974] Bluetooth~~orangepi@orangepi: ~~hci0: RTL: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723~~~$ '''sudo apt install -y git'''

~~[ 83.603894] Bluetooth~~orangepi@orangepi: ~~hci0~~~$ '''git clone https: ~~RTL: rom_version status=0 version=1~~//github.com/orangepi-xunlong/wiringOP.git -b next'''|}

~~[ 83.603920] Bluetooth~~: ~~hci0~~: ~~RTL~~{| class="wikitable" style="background-color:#ffffdc;width: ~~loading rtl_bt/rtl8723b_fw~~800px;" |-| <big>'''Note that Orange Pi 3B needs to download the code of the wiringOP next branch, please don't miss the parameter of -b next.~~bin~~'''

~~[ 83.610108] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_config.bin~~

~~[ 83.611274] Bluetooth~~'''If there is a problem with the download code from GitHub, you can use the wiringOP source code that comes with the Linux image directly, and the storage location is: ~~hci0: RTL: cfg_sz 68, total sz 22564~~/usr/src/wiringOP'''</big>|}

~~[ 83.658494] rtk_btusb~~<ol start="2" style="list-style-type: ~~Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-142432~~decimal;"><li>Compile and install wiringOP</li>

~~[ 83.658651] usbcore~~{| class="wikitable" style="width: ~~registered new interface driver rtk_btusb~~800px;" |-| orangepi@orangepi:~$ '''cd wiringOP'''

~~[ 83~~orangepi@orangepi:~/wiringOP$ '''sudo .~~667124] usb 2-1: This Realtek USB WiFi dongle (0x0bda:0xb720) is untested!~~/build clean'''

~~[ 83~~orangepi@orangepi:~/wiringOP$ '''sudo .~~667137] usb 2~~/build'''|}</ol><ol start="3" style="list-style-1type: ~~Please report results to Jes.Sorensen@gmail.com~~decimal;"><li>Test the output of the GPIO Readall command as follows</li>

~~[ 83.890140] usb 2-1: Vendor: Realtek~~<div class="figure">

[ ~~83.890153] usb 2~~[File:pi3b-img258-1~~: Product: 802~~.~~11n WLAN Adapter~~png]]

~~[ 83.890159] usb 2~~</div></ol>

~~......~~== 40Pin interface GPIO, I2C, UART, SPI, and PWM test ==

~~[ 83.890412] usb 2~~{| class="wikitable" style="background-1color: ~~RTL8723BU rev E (SMIC) 1T1R~~#ffffdc;width:800px;" |-| <big>'''Note that if you need to set overlays to open multiple configurations at the same time, ~~TX queues 3, WiFi=1, BT=1, GPS=0, HI PA=0~~please use a space to write in one line like the following space.'''</big>

~~[ 83~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.~~890417] usb 2-1: RTL8723BU MAC: 00:13:ef:f4:58:ae~~txt'''

~~[ 83.890421] usb 2~~'''overlays=spi3-m0-cs0-spidev i2c2-m1 i2c3-m0 uart7-~~1: rtl8xxxu: Loading firmware rtlwifi~~m2 uart9-m2 pwm11-m1</~~rtl8723bu_nic.bin~~span>'''|}

~~[ 83.895289] usb 2~~=== 40pin GPIO port test ===

~~[ 84.050893] Bluetooth~~{| class="wikitable" style="background-color: ~~hci0~~#ffffdc;width: ~~RTL: fw version 0x0e2f9f73~~800px;" |-| <big>'''The Linux system released by Orange Pi has a pre -installed blink_all_gpio program. This program will set up all 28 GPIO ports in 40pin to switch high and low levels.'''

~~[ 84.266905] Bluetooth: RFCOMM TTY layer initialized~~

~~[ 84~~'''After running the blink_all_gpio program, when using a multimeter to measure the level of the GPIO port, you will find that the GPIO pin will be switched between 0 and 3.~~266949] Bluetooth: RFCOMM socket layer initialized~~3v. Use this program to test whether the GPIO port can work normally'''

~~[ 84.266999] Bluetooth: RFCOMM ver 1.11~~

~~[ 84.884270] usbcore~~'''The method of running blink_all_gpio program is shown below: ~~registered new interface driver rtl8xxxu~~'''</big>

~~[ 84.912046] rtl8xxxu 2-1~~orangepi@orangepi3b:~~1.2 wlx0013eff458ae: renamed from wlan0~~~$ '''sudo blink_all_gpio'''         #Remember to add Sudo permissions

~~<ol start="4" style="list-style-type~~[sudo] password for orangepi: ~~decimal~~      ">~~<li>Then you can see the RTL8723BU WIFI device node through the~~ #You need to enter password here'''~~sudo ifconfig''' command. Please refer to the WIFI connection test a [[\l~~|~~'''section for WIFI connection''']] and testing methods</li></ol>~~}

~~orangepi@orangepi:~$~~ # There are a total of '''~~sudo ifconfig wlx0013eff458ae~~28'''GPIO ports in the 40pins of the development board that can be used. The following uses pin 7—the corresponding GPIO is GPIO4_C3——the corresponding wPi serial number is 2—as an example to demonstrate how to set the high and low levels of the GPIO port

~~wlx0013eff458ae~~: ~~flags=4099<UP,BROADCAST,MULTICAST> mtu 1500~~:[[File:pi3b-img259-1.png]]

~~ether 00~~<ol start="2" style="list-style-type:~~13:ef:f4:58:ae txqueuelen 1000 (Ethernet)~~decimal;"><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</li>

~~RX packets 0 bytes 0 (0~~{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio mode 2 out'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then set the GPIO port to output the low level.~~0 B)~~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 level flat is successful</li>

~~RX errors 0 dropped 0 overruns 0 frame~~ {| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio write 2 0'''|}

~~TX packets 0 bytes 0~~ Using GPIO Readall, you can see the value of the No. 7 pin (V) to 0~~.0 B)~~

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~[[File:pi3b-img260.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then set the GPIO port to output a high level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is 3.3v, it means that the high level is set successfully.</li>

~~<ol start~~{| class="5wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then you can see the USB Bluetooth device through the~~ |-| root@orangepi:~/wiringOP# '''~~hciconfig''' command~~gpio write 2 <~~/li~~span style="color:#FF0000">1</olspan>'''|}

~~orangepi@orangepi:~$ '''sudo apt update && sudo apt install bluez'''~~Using GPIO Readall, you can see the value of No. 7 pin (v) into 1

~~orangepi@orangepi~~[[File:~~~$ '''hciconfig'''~~pi3b-img261-1.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>The setting method of other pins is similar, just modify the serial number of wPi to the corresponding serial number of the pin</li></ol>

~~hci0: Type: Primary Bus: '''USB'''~~

~~BD Address: 00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16~~=== 40pin GPIO port pull-down resistance setting method ===

~~DOWN~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the 4 GPIO pins below Orange Pi 3B are invalid because there are 3.3V on the outside, so setting drop-down is invalid. Other pins can be set normally '''</big>

~~RX bytes~~[[File:~~1252 acl:0 sco:0 events:125 errors:0~~pi3b-img262-1.png|center]]|}

~~TX bytes:23307 acl:0 sco:0 commands:125 errors:0~~# Below the No. 11 pin—corresponding to GPIO 3_C6-corresponding wPi serial number 5—to demonstrate how to set up and down pull-down resistance of the GPIO port

~~<ol start="6" style="list~~::[[File:pi3b-~~style~~img263-~~type: decimal;"><li>You can also see the Bluetooth icon on the desktop~~1. ~~At this time, Bluetooth has not been opened, so a red '''x''' will be displayed</li></ol>~~png]]

~~[[File~~<ol start="2" style="list-style-type: decimal;"><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</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio mode 5 in'''|}</ol><ol start="3" style="list-style-type:~~pi3b~~decimal;"><li>After the setting is set to input mode, execute the following command to set the GPIO port as the pull-~~img243~~down mode</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio mode 5 up'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then enter the following command to read the level of the GPIO port.~~png~~If the level is 1, it means that the drawing mode is successful</li>{| class="wikitable" style="width:800px;" |~~576x157px]]~~-| root@orangepi:~/wiringOP# '''gpio read 5'''

'''1'''|}</ol><ol start="75" style="list-style-type: decimal;"><li>~~Click~~ Then execute the following command to set the GPIO port as the drop-down mode</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''~~Turn Bluetooth On~~gpio mode 5 down''' |}</ol><ol start="6" style="list-style-type: decimal;"><li>Then enter the following command to ~~open Bluetooth~~read the level of the GPIO port. If the level is 0, it means that the drop-down mode is set successfully</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio read 5</olspan>'''

~~[[File~~'''0'''|}</ol>

~~<ol start~~=~~"8" style~~=~~"list-style-type: decimal;"><li>The display after opening Bluetooth is shown below</li></ol>~~= 40pin SPI Test ===

~~[[File:pi3b-img245.png|576x164px]]~~# From the schematic diagram of the 40PIN interface, the SPI available for Orange Pi 3B is spi3

~~<ol start="9" style="list-style-type~~: ~~decimal;"><li>Please refer to the~~ :[[~~\l|'''Bluetooth use method'''~~File:pi3b-img264-1.png]] ~~for Bluetooth test method, so I won't go into details here.</li></ol>~~

<~~span id~~ol start="~~rtl8811~~2" style="list-~~test~~style-type: decimal;"><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:</~~span~~p><ol style="list-style-type: lower-alpha;"><li>First run '''orangepi-config''', normal users remember to add sudo permission{| class="wikitable" style=~~= RTL8811 test ====~~"width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li><li>Then select '''System'''[[File:pi3b-1.png]]</li><li>Then select '''Hardware'''[[File:pi3b-2.png]]</li>~~# First insert~~ <li>Then use the arrow keys on the keyboard to navigate to the position shown in the ~~RTL8811 wireless network card module into~~ figure below, and then use the ~~USB interface of~~ '''space''' to select the ~~development board~~SPI configuration you want to open[[File:pi3b-3.png]]</li># <li>Then ~~the Linux system will automatically load the RTL8811 WIFI~~ select '''<Save>''' to save[[File:pi3b-~~related kernel modules~~4. ~~You can see that the kernel module below is automatically loaded through the lsmod command~~png]]</li>~~orangepi@orangepi~~<li>Then select '''<Back>'''[[File:~$ pi3b-5.png]]</li><li>Then select '''~~lsmod~~<Reboot>'''to restart the system to make the configuration take effect[[File:pi3b-6.png]]~~Module Size Used by~~</li></ol>~~8821cu 1839104 0~~</li></ol>

<li>~~You can see~~ After restarting, enter the ~~loading information of~~ system to check whether there is a spidev3.0 device node in the ~~RTL8811 module through the dmesg command~~Linux system. If it exists, it means that SPI3 has been set up and can be used directly</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~dmesg~~ls /dev/spidev3.0'''

~~[ 118~~/dev/spidev3.~~618194] usb 2~~0|}</ol><ol start="4" style="list-1style-type: ~~new high-speed USB device number 2 using ehci~~decimal;"><li>Do not short-~~platform~~circuit the mosi and miso pins of SPI3, the output result of running spidev_test is as follows, you can see that the data of TX and RX are inconsistent</li>

~~[ 118.767152] usb 2~~{| class="wikitable" style="width:800px;" |-1| orangepi@orangepi: ~~New USB device found, idVendor=0bda, idProduct=c811, bcdDevice= 2~~~$ '''sudo spidev_test -v -D /dev/spidev3.000'''

~~[ 118.767181] usb 2-1~~spi mode: ~~New USB device strings: Mfr=1, Product=2, SerialNumber=3~~0x0

~~[ 118.767199] usb 2-1~~bits per word: ~~Product: 802.11ac NIC~~8

~~[ 118.767219] usb 2-1~~max speed: ~~Manufacturer: Realtek~~500000 Hz (500 KHz)

~~[ 118~~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 | ......@.…▒..................▒.~~767235] usb 2-1: SerialNumber: 123456~~

~~[ 119~~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 | ......................~~500530] usbcore~~......….|}</ol><ol start="5" style="list-style-type: ~~registered new~~ decimal;"><li>Then short-circuit the two pins of mosi (pin 19 in the 40pin interface) and miso (pin 21 in the 40pin interface ~~driver rtl8821cu~~) of SPI3, and then run the output of spidev_test as follows, you can see the sending and receiving same data</li>

[ ~~119~~[File:pi3b-img265.~~525498~~png]] ~~rtl8821cu 2~~{| class="wikitable" style="width:800px;" |-1| orangepi@orangepi:1~$ '''sudo spidev_test -v -D /dev/spidev3.0 ~~wlx1cbfced9d260: renamed from wlan0~~'''

~~<ol start="4" style="list-style-type~~spi mode: ~~decimal;">~~<li>Then you can see the WiFi device node through the '''sudo ifconfig''' command. Please refer to the [[\l|'''WiFi connection test a section''']] for WIFI connection and testing methods. I won't go into details her</li></ol>0x0

~~orangepi@orangepi~~bits per word:~~~$ '''sudo ifconfig wlx1cbfced9d260'''~~8

~~wlx1cbfced9d260~~max speed: ~~flags=4099<UP,BROADCAST,MULTICAST> mtu 1500~~500000 Hz (500 KHz)

~~ether 1c~~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 ~~packets 0 bytes 0 (0~~| 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 | .~~0 B)~~.....@.…▒..................▒.|}</ol>

~~RX errors 0 dropped 0 overruns 0 frame 0~~=== 40pin I2C Test ===

~~TX packets 0 bytes 0 (0~~# From the table below, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total of three groups of I2C bus.~~0 B)~~

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~::[[File:pi3b-img266-1.png]]

~~'''It can be seen from the above table that i2c4_m0 and spi3_m0 are pins. The two cannot be opened at the same time. i2c3_m0 and uart3_m0 are also reused. The two cannot be opened at the same time'''</~~span~~big>~~==== RTL8821CU test ====|}

~~# First insert~~ <ol start="2" style="list-style-type: decimal;"><li>In the ~~rtl8821cu wireless network card module into~~ linux system, the ~~USB interface of~~ I2C bus in the ~~development board~~40 pin is closed by default, and it needs to be opened manually to use it. The detailed steps are as follows:<ol style="list-style-type: lower-alpha;">~~# Then use the~~ <li>First run '''~~lsusb~~orangepi-config''' ~~command~~ , normal users remember to ~~see the device information of the rtl8821cu usb wifi module. Make sure the USB module is not in the Driver CDROM Mode~~ ~~orangepi@orangepi:~$~~ add '''~~lsusb | grep "Realtek"~~sudo'''permission{| class="wikitable" style="width:800px;" ~~Bus 002 Device 003: ID 0bda:c820 Realtek Semiconductor Corp. 802.11ac NIC~~|-| orangepi@orangepi:~$ '''~~lsusb | grep "Realtek"~~sudo orangepi-config'''|}</li>~~Bus 002 Device 002: ID 0bda:1a2b Realtek Semiconductor Corp. RTL8188GU 802.11n WLAN Adapter (~~<li>Then select '''~~Driver CDROM Mode~~System''')[[File:pi3b-1.png]]</li><li>Then select '''Hardware'''If [[File:pi3b-2.png]]</li><li>Then use the ~~USB WIFI module seen by~~ arrow keys on the keyboard to navigate to the ~~lsusb command is~~ position shown in ~~Driver CDROM Mode, re -insert~~ the ~~USB WiFi module. If not~~figure below, ~~please manually execute~~ and then use the ~~following command~~ '''space''' to ~~switch~~ select the ~~mode~~I2C configuration you want to open[[File: pi3b-3-2.png]]</li><li>Then select '''<Save>''' to save[[File:pi3b-4.png]]~~orangepi@orangepi:~$~~ </li><li>Then select '''<Back>'''~~sudo usb_modeswitch -KW -v 0bda~~ [[File:pi3b-5.png]]</li><li>Then select '''<Reboot>''' to restart the system to make the configuration take effect[[File:pi3b-6.png]]</li></ol></li></ol>

<li>~~The~~ After starting the Linux system ~~will automatically load the RTL8821CU Bluetooth and WIFI -related kernel modules. You can see~~ , first confirm that the ~~kernel module below is automatically loaded through the lsmod command~~i2c device node exists under/dev</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ # '''~~lsmod~~ls /dev/i2c-*''' ~~Module Size Used by~~ ~~8821cu 1839104 0~~ ~~rtk_btusb 61440 0~~

/dev/i2c-0      '''/dev/i2c-2'''      '''/dev/i2c-3'''      '''/dev/i2c-4'''      /dev/i2c-6

|}

</ol>

<li>~~You can see~~ Then connect a i2c device on the ~~loading information~~ i2c pin of the ~~rtl8821cu module through the dmesg command~~40Pin connector</li~~></ol~~>

~~orangepi@orangepi~~{| class="wikitable" style="width:800px;text-align:~~~$ '''dmesg'''~~center;"|-||i2c2-m1|i2c3-m0|i2c4-m0|-| Sda Pin|Corresponding to No. 3 pin|Corresponding to No. 27 pin|Corresponding to No.19 pin|-| Sck Pin|Corresponding to No. 5 pin|Corresponding to No. 28 pin|Corresponding to No.23 pin|-| Vcc Pin|Corresponding to No. 1 pin|Corresponding to No. 1 pin~~[ 57~~|Corresponding to No.~~083693] usb 2-~~1~~: new high~~pin|-~~speed USB device number 2 using ehci-platform~~| Gnd Pin|Corresponding to No. 6 pin~~[ 57~~|Corresponding to No.~~231888] usb 2-1: New USB device found, idVendor=0bda, idProduct=1a2b, bcdDevice= 2~~ 6 pin|Corresponding to No.006 pin|}</ol>~~[ 57.231916] usb 2~~<ol start="5" style="list-style-1type: ~~New USB~~ decimal;"><li>Then use the '''i2cdetect -y''' command if the address of the connected I2C device ~~strings: Mfr=1~~can be detected, ~~Product~~it means that the I2C can be used normally</li>{| class=~~2, SerialNumber~~"wikitable" style=0"width:800px;" |-~~[ 57.231937] usb~~ | orangepi@orangepi:~$ sudo i2cdetect -y 2~~-1: Product: DISK~~#i2c2 command

~~[ 57.231956] usb 2~~orangepi@orangepi:~$ sudo i2cdetect -~~1: Manufacturer: Realtek~~y 3 #i2c3 command

~~[ 57.242594] usb-storage 2~~orangepi@orangepi:~$ sudo i2cdetect -~~1:1.0: USB Mass Storage device detected~~y 4 #i2c4 command|}

~~[ 57.245674] scsi host0: usb-storage 2-1:1.0~~<div class="figure">

[ 58[File:pi3b-img267.~~069172~~png]] ~~usb 2-1: USB disconnect, device number 2~~

~~[ 58.440025] usb 2~~</div></ol>

~~[ 58.587819] usb 2-1: New USB device found, idVendor~~=~~0bda, idProduct~~=~~c820, bcdDevice~~= ~~2.00~~40pin UART test ===

~~[ 58.587827] usb 2-1: New USB device strings: Mfr=1~~# As can be seen from the table below, the uart available for Orange Pi 3B is uart3, ~~Product=2~~uart7, ~~SerialNumber=3~~and uart9. There are three sets of uart bus

::[[ ~~58.587833] usb 2~~File:pi3b-img268-1~~: Product: 802~~.~~11ac NIC~~png]]

~~[ 58.587838] usb 2~~::{| class="wikitable" style="background-1color: ~~Manufacturer~~#ffffdc;width: ~~Realtek~~800px;" |-| <big>'''As can be seen from the above table, i2c3_m0 and uart3_m0 are reused by pins, and the two cannot be opened at the same time'''</big>|}

~~[ 58~~<ol start="2" style="list-style-type: decimal;"><li>In the linux system, the UART in the 40 pins is closed by default, and it needs to be opened manually before it can be used.~~587844] usb 2~~The detailed steps are as follows:<ol style="list-style-type: lower-alpha;"><li>First run '''orangepi-1config''', normal users remember to add sudo permission{| class="wikitable" style="width: ~~SerialNumber~~800px;" |-| orangepi@orangepi: ~~123456~~~$ '''sudo orangepi-config'''|}</li><li>Then select '''System'''[[ 58File:pi3b-1.~~610463~~png] ~~rtk_btusb~~]</li><li>Then select '''Hardware'''[[File: ~~Realtek Bluetooth USB driver ver~~ pi3b-2.png]]</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:pi3b-3-3.1png]]</li><li>Then select '''<Save>''' to save[[File:pi3b-4.~~6d45ddf~~png]]</li><li>Then select '''<Back>'''[[File:pi3b-5.~~20220519-142432~~png]]</li><li>Then select '''<Reboot>''' to restart the system to make the configuration take effect[ 58[File:pi3b-6.~~610656~~png] ~~usbcore: registered new interface driver rtk_btusb~~]</li></ol></li></ol>

~~[ 58.634631] Bluetooth: hci0: RTL: examining hci_ver~~<ol start=~~08 hci_rev~~"3" style=~~000c lmp_ver=08 lmp_subver=8821~~"list-style-type: decimal;"><li>After entering the Linux system, first confirm whether there is a device node corresponding to uart under/dev</li>

~~[ 58.636729] Bluetooth~~{| class="wikitable" style="width: ~~hci0~~800px;" |-| orangepi@orangepi: ~~RTL: rom_version status=0 version=1~~~# '''ls /dev/ttyS*'''

~~[ 58.636740] Bluetooth: hci0: RTL~~/dev/ttyS1      '''/dev/ttyS3      /dev/ttyS7      /dev/ttyS9'''|}</ol><ol start="4" style="list-style-type: ~~loading rtl_bt~~decimal;"><li>Then start testing the uart interface, first use the rx and tx of the uart interface to be tested by DuPont</~~rtl8821c_fw.bin~~li>

~~[ 58.664190] Bluetooth~~{| class="wikitable" style="width: ~~hci0~~800px;text-align: ~~RTL: loading rtl_bt/rtl8821c_config.bin~~center;"|-||uart3|uart7|uart9|-| Tx pin|Corresponding to the 28 pin|Corresponding to the 16 pin|Corresponding to the 29 pin|-| Rx Pin|Corresponding to the 27 pin|Corresponding to the 15 pin|Corresponding to the 22 pin|}

[ 58[File:pi3b-img269-1.~~664746~~png] ~~Bluetooth~~]</ol><ol start="5" style="list-style-type: decimal;"><li>Use the '''gpio serial''' command to test the loop function of the serial port as shown below. If you can see the following printing, it means that the serial communication is normal<ol style="list-style-type: ~~hci0~~lower-alpha;"><li>Test UART3</li>{| class="wikitable" style="width: ~~RTL~~800px;" |-| orangepi@orangepi: ~~cfg_sz 10, total sz 31990~~~$ '''sudo gpio serial /dev/ttyS3'''

[ ~~59.122471~~sudo] ~~Bluetooth~~password for orangepi: ~~hci0: RTL: fw version 0x829a7644~~#Enter the password here.

~~[ 59.265513] usbcore: registered new interface driver rtl8821cu~~

~~[ 59.280119] rtl8821cu 2-1~~Out:~~1.2 wlx90de80521825~~0: ~~renamed from wlan0~~-> 0

~~<ol start="5" style="list-style~~Out: 1: -~~type: decimal~~>"><li>Then you can see the RTL8821CU WiFi device node through the '''sudo ifconfig''' command. Please refer to the [[\l|'''WiFi connection test''']] a section for WIFI connection and testing methods.</li></ol>1

~~orangepi@orangepi~~Out:~~~$ '''sudo ifconfig wlx90de80521825'''~~2: -> 2

~~wlx90de80521825~~Out: ~~flags=4099<UP,BROADCAST,MULTICAST~~3: -> ~~mtu 1500~~3

~~ether 00~~Out:134:~~ef:f4:58:ae txqueuelen 1000 (Ethernet)~~-> 4

~~RX packets 0 bytes 0 (0.0 B)~~Out: 5: -> 5^C|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Test UART7</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo gpio serial /dev/ttyS7'''

~~RX errors 0 dropped 0 overruns 0 frame 0~~[sudo] password for orangepi: #Enter the password here.

~~TX packets 0 bytes 0 (0.0 B)~~

~~TX errors~~ Out: 0 ~~dropped 0 overruns 0 carrier 0 collisions~~ : -> 0

~~<ol start="6" style="list-style~~Out: 1: -~~type: decimal~~>">~~<li>Then you can see the USB Bluetooth device through the '''hciconfig''' command</li></ol>~~1

~~orangepi@orangepi~~Out: 2:~~~$ '''sudo apt~~-~~get update~~ &~~amp~~gt;~~& sudo apt-get install -y bluez'''~~2

~~orangepi@orangepi~~Out:~~~$ '''hciconfig'''~~3: -> 3

~~hci0~~Out: ~~Type~~4: ~~Primary Bus: '''USB'''~~-> 4

~~BD Address~~Out: 005:13-> 5^C|}</ol><ol start="3" style="list-style-type:EFlower-alpha;"><li>Test UART9</li>{| class="wikitable" style="width:F4800px;" |-| orangepi@orangepi:~~58:AE ACL MTU: 820:8 SCO MTU: 255:16~~~$ '''sudo gpio serial /dev/ttyS9'''

~~DOWN~~[sudo] password for orangepi: #Enter the password here.

~~RX bytes:1252 acl:0 sco:0 events:125 errors:0~~

~~TX bytes:23307 acl:0 sco~~Out:0 ~~commands:125 errors~~:-> 0

~~<ol start="7" style="list-style~~Out: 1: -~~type: decimal~~>">~~<li>Bluetooth icons can also be seen on the desktop. At this time, Bluetooth has not been opened, so a red '''x''' will be displayed</li></ol>~~1

~~[[File~~Out: 2:~~pi3b~~-~~img243.png|576x157px]]~~> 2

~~<ol start="8" style="list-style~~Out: 3: -~~type: decimal~~>">~~<li>Click '''Turn Bluetooth On''' to open Bluetooth</li></ol>~~3

~~[[File~~Out: 4:~~pi3b~~-~~img244.png|576x262px]]~~> 4

Out: 5: -> 5^C|}</ol ~~start="9" style="list-style-type: decimal;"~~></li>~~The display after opening Bluetooth is shown below~~</liol></olspan>

~~[[File:pi3b-img245.png|576x164px]]~~=== PWM test method ===

~~<ol start="10" style="list-style-type: decimal;"><li>Please refer to~~ # From the ~~[[\l|'''Bluetooth use chapter''']]~~ table below, the pwm11 available for ~~the Bluetooth test method. I won't go into details her</li></ol>~~Orange Pi 3B

~~=== USB Camera Test ===~~ ~~# First, you need to prepare a USB camera that supports the UVC protocol in the figure below, and then insert the USB camera into the USB interface of the Orange PI development board~~ ::[[File:pi3b-~~img13~~img270-1.png~~|259x150px~~]]

<li>~~You can see that~~ In the linux system, the PWM in the ~~USB camera's device node information~~ 40 pin isturned off by default, and it needs to be turned on manually before it can be used. The detailed steps are as follows:</~~dev/video0 through the v4l2~~p><ol style="list-style-type: lower-~~ctl command~~alpha;"></li>First run '''orangepi-config''', normal users remember to add sudo permission</olp>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~v4l2~~sudo orangepi-config'''|}</li><li>Then select '''System'''[[File:pi3b-~~ctl~~ 1.png]]</li><li>Then select '''Hardware'''[[File:pi3b-2.png]]</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:pi3b-~~list~~3-~~devices~~4.png]]</li><li>Then select '''<Save>''' to save[[File:pi3b-4.png]]</li><li>Then select '''<Back>'''~~Q8 HD Webcam~~[[File: ~~Q8 HD Webcam (~~pi3b-5.png]]</li><li>Then select '''~~usb~~<Reboot>'''to restart the system to make the configuration take effect[[File:pi3b-~~fc880000~~6.~~usb-1):~~png]]</li></ol></li></ol>

<ol start="3" style="list-style-type: decimal;"><li>After opening a pwm, there will be an extra pwmchipX in '''/~~dev~~sys/class/pwm/''' (X is a specific number), for example, after opening pwm11, check the pwmchipX under '''/sys/class/pwm/''' one becomes two</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ls /sys/class/pwm/~~video0~~'''

pwmchip0 pwmchip1|}</~~dev~~ol><ol start="4" style="list-style-type: decimal;"><li>Which pwmchip above corresponds to pwm11, let's check the output of the '''ls /~~video1~~sys/class/pwm/ -l''' command first, as shown below:</li><li>Then it can be known from the table below that the base address of the pwm11 register is fe6f0030, and then look at the output of the '''ls /sys/class/pwm/ -l''' command, you can see that pwmchip1 is linked to fe6f0030.pwm, so pwm11 corresponds to pwmchip as pwmchip1</li>

~~/dev/media0~~<div class="figure">

~~'''Note that l in v4l2 is a lowercase letter l, not numbers 1~~[[File:pi3b-img271.~~'''~~png]]

</div></ol><ol start="6" style="list-style-type: decimal;"><li>Then use the following command to make pwm11 output a 50Hz square wave (please switch to the root user first, and then execute the following command)</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''~~In addition, Video's serial number is not necessarily Video0, please refer to what you see.~~echo 0 > /sys/class/pwm/pwmchip1/export'''

~~<ol start="3" style="list-style-type~~root@orangepi: ~~decimal~~~# '''echo 20000000 >">~~<li>In the desktop system, you can use Cheese to directly turn on the USB camera. The cheese opening method is shown in the figure below: <~~/~~li><~~sys/class/pwm/pwmchip1/pwm0/~~ol>~~period'''

~~[[File~~root@orangepi:~~pi3b-img246.png|474x302px]]~~~# '''echo 1000000 > /sys/class/pwm/pwmchip1/pwm0/duty_cycle'''

~~The interface after cheese opens the USB camera is shown in the figure below~~root@orangepi: ~# '''echo 1 > /sys/class/pwm/pwmchip1/pwm0/enable'''|}

[[File:pi3b-~~img247~~img272.png~~|473x277px~~]]

~~<ol start="4" style="list-style-type: decimal;">~~<li>~~How~~ The test method of pwm11 demonstrated above is similar to other pwm test ~~the USB camera using fswebcam~~methods.</pli></ol ~~style~~>~~<li>Install fswebcam~~</~~li></ol></li></ol~~span>

~~orangepi@orangepi:~$ '''sudo''' '''apt update'''~~== How to install and use wiringOP-Python ==

~~orangepi@orangepi~~{| class="wikitable" style="background-color:#ffffdc;width:~$ 800px;" |-| <big>'''~~sudo apt-get install~~ wiringOP-~~y fswebcam~~Python is the Python language version of wiringOP, which is used to operate the hardware resources of the development board, such as GPIO, I2C, SPI and UART, in the Python program.'''

~~<ol start="2" style="list-style-type: lower-alpha;">~~

~~<li>After installing fswebcam, you can use the following command to take pictures~~

~~<ol style="list-style-type: lower-alpha;">~~

~~<li>-d The option is used to specify the device node of the USB camera</li>~~

~~<li>--no-banner Used to remove the watermark of photos</li>~~

~~<li>-r The option is used to specify the resolution of the photo</li>~~

~~<li>-S The option is set to the number of frames before skipping</li>~~

~~<li>./image.jpg The name and path for setting the generated photos</li></ol>~~

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

~~orangepi@orangepi:~$~~ '''~~sudo~~In addition, please note that all the following commands are operated under the root user.''' ~~'''fswebcam -d~~ </~~dev/video0 \'''~~big>|}

~~'''~~=== wiringOP-~~r 1280x720 -S 5 ./image.jpg'''~~Python installation method ===

~~<ol start="3" style="list-style-type: lower-alpha;"><li>In~~ # First install the ~~service version of the Linux system, you can use the scp command to pass the picture to the Ubuntu PC to watch after taking the photo</li></ol>~~dependency package

~~orangepi@orangepi~~:~~~$ '''scp image.jpg''' [mailto~~:~~test@192.168.1.55~~{| class="wikitable" style="width:~~/home/test test~~800px;" |-| root@~~192.168.1.55~~orangepi:~~/home/test]~~ ~# '''~~（Modify the IP address and path according to the actual situation）~~sudo apt-get update'''

~~<ol start="4" style="list~~root@orangepi:~# '''sudo apt-~~style~~get -~~type: lower~~y install git swig python3-dev python3-~~alpha;">~~setuptools'''~~<li>In the desktop version of the Linux system, you can directly view the shot pictures through the HDMI display</li></ol>~~|}

<~~span id~~ol start="~~audio~~2" style="list-style-~~test~~type: decimal;"><li>Then use the following command to download the source code of wiringOP-Python</~~span~~li>{| class="wikitable" style= ~~Audio Test ==~~"background-color:#ffffdc;width:800px;" |-| <big>'''Note that the following git clone--recursivee command will automatically download the source code of wiringOP, because wiringOP-Python depends on wiringOP. Please make sure that the download process does not report an error due to network problems.'''

~~~~

~~=== Test audio methods in the desktop system ===~~

'''If there is a problem with the download code from GitHub, you can use the wiringOP-Python source code that comes with the Linux image directly, and the storage location is:/usr/src/wiringOP-Python'''</big>|}{| class="wikitable" style="width:800px;" |-| root@orangepi:~# ~~First open the file manager~~'''git clone --recursive https://github.com/orangepi-xunlong/wiringOP-Python -b next'''

~~[[File~~root@orangepi:~~pi3b~~~# '''cd wiringOP-~~img248.png|357x176px]]~~Python'''

root@orangepi:~/wiringOP-Python# '''git submodule update --init --remote'''|}</ol><ol start="23" style="list-style-type: decimal;"><li>Then ~~find~~ use the following ~~file (if there is no audio file in~~ command to compile wiringOP-Python and install it into the Linux system~~, you can upload a audio file to~~ of the ~~system by yourself)~~development board</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''cd wiringOP-Python'''

~~<div class="figure">~~root@orangepi:~/wiringOP-Python# '''python3 generate-bindings.py > bindings.i'''

~~[[File~~root@orangepi:~~pi3b~~~/wiringOP-~~img249~~Python# '''sudo python3 setup.~~png~~py install'''|~~236x186px|图片10]]~~}</ol><ol start="4" style="list-style-type: decimal;"><li>Then enter the following command. If there is a help information output, it means that Wiringop-Python is successfully installed. Press the '''q''' key to exit the interface of the help information</li>

~~</div><ol start~~{| class="3wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then select the audio.wav file, right~~ |-~~click and select VLC to open it to start playing<~~| root@orangepi:~/~~li></ol>~~wiringOP-Python# '''python3 -c "import wiringpi; help(wiringpi)"'''

~~[[File~~Help on module wiringpi:~~pi3b-img250.png|288x234px]]~~

~~<ol start="4" style="list-style-type: decimal;">~~

~~<li>Methods to switch different audio equipment such as HDMI playback and headset playback~~

~~<ol style="list-style-type: lower-alpha;">~~

~~<li>First open the volume control interface</li></ol>~~

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

~~[[File:pi3b-img251.png|308x169px]]~~NAME

~~<ol start="2" style="list-style-type~~: ~~lower-alpha;">~~<li>When playing audio, the audio equipment options that play software can be used will be displayed in '''Playback'''. As shown in the figure below, which audio equipment you need to play here can be set.</li></ol>wiringpi

~~[[File:pi3b-img252.png|576x282px]]~~

~~=== How to play audio with commands ===~~DESCRIPTION

~~<~~: # This file was automatically generated by SWIG (http:/~~span>==== Headphone interface play audio test ====~~/www.swig.org).

: # ~~First insert the headset into the headphone jack of the development board~~Version 4.0.2

~~[[File~~:~~pi3b-img253.png|395x112px]]~~#

~~<ol start="2" style="list-style-type~~: ~~decimal;"><li>Then~~ # Do not make changes to this file unless you know what you ~~can check the sound card device supported by the Linux system through the '''aplay~~ are doing--~~l''' command. From the output below, it can be seen that '''card 0''' is the sound card device with RK809, which is the sound card device of the headset</li></ol>~~modify

~~orangepi~~: # the SWIG interface file instead.|}</ol><ol start="5" style="list-style-type: decimal;"><li>Test whether the wiringOP-Python is installed successfully under the Python command line is shown below:<ol style="list-style-type: lower-alpha;"><li>First use the Python3 command to enter the command line mode of Python3</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ # '''python3''~~aplay~~ '|}</ol><ol start="2" style="list-lstyle-type: lower-alpha;"><li>Then import the Python module of WiringPi</li>{| class="wikitable" style="width:800px;" |-| >>> '''import wiringpi;'''|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Enter the following command to view the help information of wiringOP-Python, and press the '''q''' key to exit the interface of the help information</li>{| class="wikitable" style="width:800px;" |-| >>> '''help(wiringpi)'''

~~**** List of PLAYBACK Hardware Devices ****~~Help on module wiringpi:

~~'''card 0: rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]'''~~

~~'''Subdevices: 0/1'''~~NAME

~~'''Subdevice #0~~: ~~subdevice #0'''~~wiringpi

~~card 1: rockchiphdmi [rockchip,hdmi], device 0: fe400000.i2s-i2s-hifi i2s-hifi-0 [fe400000.i2s-i2s-hifi i2s-hifi-0]~~

~~Subdevices: 0/1~~DESCRIPTION

~~Subdevice~~ : #0This file was automatically generated by SWIG (http: ~~subdevice #0~~//www.swig.org).

~~Subdevice #0~~: ~~subdevice~~ #Version 4.0.2

~~<ol start="3" style="list-style-type~~: ~~decimal;"><li>Then use the '''aplay''' command to play the audio file that comes with the system. If the headset can hear the sound, it means that the hardware can be used normally</li></ol>~~#

~~orangepi@orangepi~~:~~~$ '''aplay~~ # Do not make changes to this file unless you know what you are doing-~~D hw:0,0 /usr/share/sounds/alsa/audio.wav'''~~-modify

~~Playing WAVE 'audio~~: # the SWIG interface file instead.~~wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo~~

~~~~

~~==== HDMI Audio Play Test ====~~

~~# First use the HDMI to HDMI cable to connect the Orange PI development board to the TV (other HDMI displays need to ensure that the audio can be played)# Then check the sound card serial number of HDMI. From the output below, you can know that the HDMI sound card is '''card 1'''~~CLASSES

~~orangepi@orangepi~~:~~~$ '''aplay -l'''~~builtins.object

~~**** List of PLAYBACK Hardware Devices ****~~::GPIO

~~card 0~~: ~~rockchiprk809 [rockchip-rk809], device 0~~: ~~dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]~~I2C

~~Subdevices~~: ~~0/1~~:Serial

~~Subdevice #0~~: ~~subdevice #0~~:nes

~~'''card 1: rockchiphdmi [rockchip,hdmi], device 0: fe400000.i2s-i2s-hifi i2s-hifi-0 [fe400000.i2s-i2s-hifi i2s-hifi-0]'''~~

~~'''Subdevices~~: ~~0/1'''~~class GPIO(builtins.object)

~~'''Subdevice #0~~: ~~subdevice #~~| GPIO(pinmode=0~~'''~~)

~~'''Subdevice #0~~: ~~subdevice #0'''~~|

~~<ol start="3" style="list-style-type: decimal;">~~

~~<li>Then use the '''aplay''' command to play the audio file that comes with the system. If the HDMI display or television can hear the sound indicates that the hardware can be used normally</li></ol>~~

~~orangepi@orangepi:~$ '''aplay -D hw:1,0~~ >>>|}</~~usr~~ol></~~share~~li></~~sounds/alsa~~ol></~~audio.wav'''~~span>

~~~~=== ~~Use the command to~~ 40pin GPIO port test ~~the recording method~~ ===

{| class="wikitable" style="background-color:# ~~Orange Pi 3B development board does not have MICs~~ffffdc;width:800px;" |-| <big>'''wiringOP-Python is the same as wiringOP, ~~and~~ you can ~~only record audio through headphones with MIC function. After inserting~~ also determine which GPIO pin to operate by specifying the ~~headset with~~ wPi number, because there is no command to check the ~~MIC function into~~ wPi number in wiringOP-Python, so you can only check the ~~development~~ board~~, the command below will record a piece of audio through the headset~~wPi number and physical Correspondence between pins.'''</big>

~~orangepi@orangepi:~$ '''amixer -c 0 cset name~~<div class=~~'Capture MIC Path' 'Main Mic''''~~"figure">

~~orangepi@orangepi~~[[File:~~~$ '''arecord~~ pi3b-~~D hw:0,0 -d 5 -f cd -t wav /tmp/test~~img258.~~wav'''~~png|center]]

~~~~</~~span~~div>~~== Temperature Sensor ==~~|}# ~~The command of~~ Below the ~~system temperature sensor is:~~ ~~orangepi@orangepi:~$ '''sensors'''~~ ~~soc_thermal-virtual-0~~ ~~Adapter: Virtual device~~ ~~temp1: +41.9°C (crit = +115~~No.~~0°C)~~ ~~gpu_thermal~~ 7 pin — corresponding to GPIO4_a4 -~~virtual~~corresponding WPI serial number 2 -0to demonstrate how to set the height of the GPIO port

~~Adapter~~: ~~Virtual device~~ ~~temp1~~: ~~+43~~[[File:pi3b-img259.~~8°C~~png]]

<li>The ~~command~~ steps of the ~~current temperature of the NVMe SSD solid -state hard disk is: orangepi@orangepi:~$ '''sudo smartctl -a /dev/nvme0 | grep "Temperature:"'''Temperature: '''40 Celsius'''</li></ol>~~ ~~== 40 Pin interface pin explanation ==~~ ~~# Orange Pi 3B Development board 40 Pin interface pins, please refer to the figure~~ command test are shown below ~~<div class="figure">~~ ~~[[File:pi3b-img254.png|400x124px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\Orange-Pi-3B-Development-board-40-Pin(1).jpgOrange-Pi-3B-Development-board-40-Pin(1)]]~~ ~~</div><ol start="2" style="list-style-type~~directly: ~~decimal;"><li>The function of the Orange Pi 3B development board 40 PIN interface pins is shown in the table below.~~

<li>~~Below~~ First set the GPIO port to the output mode. The first parameter of the '''pinMode''' function is ~~a complete pins~~ the serial number of ~~40pin~~the wpi corresponding to the pin, and the second parameter is the GPIO mode</li>~~</ol>~~<{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~li></ol>~~wiringOP-Python# '''python3 -c "import wiringpi; \'''

~~[[File:pi3b-img255~~'''from wiringpi import GPIO; wiringpi.~~png|575x160px]]~~wiringPiSetup() ; \'''

'''wiringpi.pinMode(2, GPIO.OUTPUT) ; "'''

|}

</ol>

<li>~~The following form is a picture on~~ Then set the GPIO port output low level. After setting, you can use the voltage of the ~~left half~~ voltage of the ~~full table above~~universal meter to measure the pins. If it is 0V, ~~which can be seen clearly~~it means that the low -power flat is successful</li><{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~ol>~~wiringOP-Python# '''python3 -c "import wiringpi; \'''

~~[[File:pi3b-img256~~'''from wiringpi import GPIO; wiringpi.~~png|478x267px]]~~wiringPiSetup() ;\'''

'''wiringpi.digitalWrite(2, GPIO.LOW)"'''

|}

</ol>

<li>~~The following form is a picture on~~ Then set the GPIO port output high level. After setting, you can use the value of the ~~right half~~ voltage of the ~~top table above~~pins with a multimeter. If it is 3.3V, ~~which can be seen clearly~~it means that the high -power flat is successful.</li><{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~ol>~~wiringOP-Python# '''python3 -c "import wiringpi; \'''

~~[[File:pi3b-img257~~'''from wiringpi import GPIO; wiringpi.~~png|479x266px]]~~wiringPiSetup() ;\'''

'''wiringpi.digitalWrite(2, GPIO.HIGH)"'''

|}

</ol>

</li></ol>

<li>~~There are a total~~ The steps of ~~'''28''' GPIO ports~~ testing in the ~~40pin interface. The voltage~~ command line of Python3 are shown below: <ol style="list-style-type: lower-alpha;"><li>First use the Python3 command to enter the command line mode of ~~all GPIO ports is~~ Python3</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''~~3.3v~~python3'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then import the Python module of WiringPi</olli>{| class="wikitable" style="width:800px;" |-| >>> '''import wiringpi'''

>>> '''from wiringpi import GPIO'''|}<~~span id~~/ol><ol start="~~how~~3" style="list-tostyle-~~install~~type: lower-~~wiringop~~alpha;"><li>Then set the GPIO port as the output mode. The first parameter of the '''pinMode''' function is the serial number of the wpi corresponding to the pin, and the second parameter is the GPIO mode.</~~span~~li>{| class="wikitable" style= ~~How to install Wiringop ==~~"width:800px;" |-| >>> '''wiringpi.wiringPiSetup()'''

~~'''Note that Wiringop has been pre -installed in the Linux image released by Orange Pi. Unless Wiringop's code is updated, it is not necessary to re -download and install. Just use it directly.'''~~0

>>> '''~~The storage path~~ wiringpi.pinMode(2, GPIO.OUTPUT)'''|}</ol><ol start="4" style="list-style-type: lower-alpha;"><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.</li>{| class="wikitable" style="width:800px;" |-| >>> '''wiringpi.digitalWrite(2, GPIO.LOW)'''|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then set the GPIO port output high level. After setting, you can use the value of the voltage of the ~~compiled~~ pins with a multimeter. If it is 3.3V, it means that the high -power flat is successful</li>{| class="wikitable" style="width:800px;" |-| >>> '''wiringpi.digitalWrite(2, GPIO.HIGH)'''|}</ol></li></ol><ol start="4" style="list-style-type: decimal;"><li>Wiringop-Python Sets GPIO high and low levels in the Python code. For reference to the ''~~s Deb is wrapped~~ 'blink.py''' test program in Examples, the voltage of the '''blink.py''' test program will set up the voltage of all GPIO ports in ~~Orangepi~~the development board 40 PIN</li>{| class="wikitable" style="width:800px;" |-~~Build~~| root@orangepi: ~/wiringOP-Python# '''cd examples'''

root@orangepi:~/wiringOP-Python/examples# '''~~orangepi-build/external/cache/debs/arm64/wiringpi_x.xx~~ls blink.~~deb~~py'''

'''~~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~~blink.py'''

root@orangepi:~/wiringOP-Python/examples'''# python3 blink.py'''|}<~~div class~~/ol>

~~[[File:pi3b-img258.png|575x355px|66AC(IBG%N8L@Y7(1BZPS`N]]~~=== 40pin SPI test ===

~~</div>'''wiringOP is currently adapted to set~~ # From the ~~GPIO port input output, set~~ schematic diagram of the ~~GPIO port output high and low level~~40pin interface, ~~and set~~ the ~~function of pulling and down resistance. It~~ SPI available for Orange Pi 3B is ~~impossible to use functions like hardware PWM.'''~~spi3

::[[File:pi3b-img264.png]] ::{| class="wikitable" style="background-color:# ~~Download~~ ffffdc;width:800px;" |-| <big>'''In the ~~code of Wiringop~~Linux system, the spi3 in 40pin is closed by default, and it needs to be opened manually to use.'''

~~orangepi@orangepi:~$ '''sudo apt update'''~~

~~orangepi@orangepi:~$~~ '''~~sudo apt install -y git~~Add the configuration of the red font part below to the /boot/orangepiEnv.txt, and then restart the Linux system to open the spi4.'''</big>

~~orangepi@orangepi:~$ '''git clone https://github.com/orangepi-xunlong/wiringOP.git -b next'''~~

orangepi@orangepi:~$ '''~~Note that Orange Pi 3B needs to download the code of the wiringOP next branch, please don't miss the parameter of -b next~~sudo vim /boot/orangepiEnv.txt'''

'''~~If there is a problem with the download code from GitHub, you can use the wiringOP source code that comes with the Linux image directly, and the storage location is~~overlays=spi3-m0-cs0-spidev</~~usr/src/wiringOP~~span>'''|}

<li>~~Compile~~ First check whether there is a '''spidev3.0''' device node in the Linux system. If it exists, it means that the SPI3 has been set and ~~install wiringOP~~can be used directly</li~~></ol~~>{| class="wikitable" style="width:800px;" ~~orangepi@orangepi:~$ '''cd wiringOP'''~~|-| orangepi@orangepi:~~~/wiringOP~~$ '''~~sudo .~~ls /~~build clean'''~~ ~~orangepi@orangepi:~~~dev/~~wiringOP$ '''sudo~~ spidev3.~~/build~~0'''

/dev/spidev3.0

|}

</ol>

<li>~~Test~~ You can then use the spi back function under the '''spidev_test.py''' program in Examples. The '''spidev_test.py''' program needs to specify the following two parameters: <ol style="list-style-type: lower-alpha;"><li>'''--channel''': Specify the channel number of SPI</li><li>'''--port''': Specify the port number of SPI</li></ol></li><li>Do not pick up the two pins of the SPI3 MOSI and MISO in short, and run the output result of the ~~GPIO Readall command~~ spidev_test.py as ~~follows~~shown below. You can see that the data of TX and RX are inconsistent</lip></olli>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''cd examples'''

~~<div class="figure">~~root@orangepi:~/wiringOP-Python/examples# '''python3 spidev_test.py \'''

~~[[File:pi3b~~'''-~~img258.png|575x355px|66AC(IBG%N8L@Y7(1BZPS`N]]~~-channel 3 --port 0'''

~~</div>== 40Pin interface GPIO, I2C, UART, SPI, and PWM test ==~~mode: 0x0

~~'''Note that if you need to set overlays to open multiple configurations at the same time, please use a space to write in one line like the following space.'''~~max speed: 500000 Hz (500 KHz)

~~orangepi@orangepi:~$ '''sudo vim~~ Opening device /~~boot~~dev/~~orangepiEnv~~spidev3.~~txt'''~~0

TX | FF FF FF FF FF FF '''~~overlays~~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 |.............….||}</ol><ol start="5" style== "list-style-type: decimal;"><li>Then use the TXD (No. 19 pins in the 40Pin interface) and RXD (No. 21 pins in the 40pin ~~GPIO port~~ interface) of the DuPont line short connection SPI3. Like sending and receiving data, it means that the SPI3 loop test is normal</li>{| class="wikitable" style=="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''cd examples'''

root@orangepi:~/wiringOP-Python/examples# '''~~The Linux system released by Orange Pi has a pre -installed blink_all_gpio program. This program will set up all 28 GPIO ports in 40pin to switch high and low levels~~python3 spidev_test.py \'''

'''~~After running the blink_all_gpio program, when using a multimeter to measure the level of the GPIO~~ --channel 3 --port~~, you will find that the GPIO pin will be switched between~~ 0 ~~and 3.3v. Use this program to test whether the GPIO port can work normally~~'''

~~'''The method of running blink_all_gpio program is shown below~~spi mode: ~~'''~~0x0

~~orangepi@orangepi3b~~max speed:~~~$ '''sudo blink_all_gpio''' #Remember to add Sudo permissions~~500000 Hz (500 KHz)

~~[sudo] password for orangepi: #You need to enter a password here~~Opening device /dev/spidev3.0

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 |. ~~Below is No~~. ~~7 pins -corresponding GPIO as GPIO4_A4 -corresponding WPI serial number 2 -as an example how to set the height of the GPIO port~~....@.......…|

~~[[File~~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 |......@.......~~png~~…|~~576x120px]]~~|}</ol>

~~<ol start~~=~~"2" style~~=~~"list-style-type: decimal;"><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</li></ol>~~= 40pin I2C test ===

~~root@orangepi~~<ol start="1" style="list-style-type:~decimal;"><li>As can be seen from the table below, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total of three groups of I2C bus</~~wiringOP# '''gpio mode 2 out'''~~li>

~~<ol start="3" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Then set the GPIO port to output the low level~~img266. ~~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 -electric flat is successful</li></ol>~~png]]

~~root@orangepi~~{| class="wikitable" style="background-color:~~~/wiringOP~~# ffffdc;width:800px;" |-| <big>'''~~gpio write 2 0~~It can be seen from the above table that I2C4_M0 and SPI3_M0 are pins. The two cannot be opened at the same time. I2C3_M0 and UART3_M0 are also reused. The two cannot be opened at the same time'''</big>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| ~~Using GPIO Readall~~<big>'''In the Linux system, ~~you can see~~ the ~~value of the No~~I2C in 40Pin is closed by default, and it needs to be opened manually to use. ~~7 pin (v) to 0~~'''

~~[[File:pi3b-img260.png|576x120px]]~~

~~<ol start="4" style="list-style-type: decimal;"><li>Then set~~ '''Add the configuration of the red font part below to the ~~GPIO port output high level~~/boot/orangepiEnv. ~~After setting~~txt, ~~you can use~~ and then restart the ~~voltage of~~ Linux system to open the ~~voltage of the permanent meter to measure~~ I2C2, i2C3, and I2C4 at the ~~voltage~~same time. If ~~it is 3~~you only need to open one, then fill in one.~~3V, it means that the high-electricity level is successful</li>~~'''</olbig>

~~root@orangepi:~/wiringOP# '''gpio write 2 1'''~~

~~Using GPIO Readall, you can see the value of No. 7 pin (v) into 1~~ ~~[[File:pi3b-img261.png|576x118px]]~~ ~~<ol start="5" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>The setting method of other pins is similar. Just modify the serial number of the wPi sequence number as the corresponding serial number corresponding to the pin</li></ol>~~ ~~=== 40Pin GPIO Port -down and downward pull -down resistance setting method ===~~ ~$ '''~~Note that the 4 GPIO pins below Orange Pi 3B are invalid because there are 3.3V on the outside, so setting drop -down is invalid~~sudo vim /boot/orangepiEnv. ~~Other pins can be set normally~~txt''' ~~[[File:pi3b-img262.png|575x353px]]~~ ~~# Below the No. 11 pin—corresponding to GPIO 3_C6-corresponding WPI serial number 5—to demonstrate how to set up and down pull-down resistance of the GPIO port~~ ~~[[File:pi3b-img263.png|576x147px]]~~

'''overlays=i2c2-m1 i2c3-m0 i2c4-m0'''

|}

</ol>

<li>~~First of all~~After starting the Linux system, ~~you need to set~~ first confirm the ~~GPIO port as the input mode~~I2C device node under/dev. ~~The third parameter needs to enter the serial number of the wpi corresponding to the pins~~</li~~></ol~~>

~~root~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~~~/wiringOP~~# '''~~gpio mode 5 in~~ls /dev/i2c-*'''

/dev/i2c-0      '''/dev/i2c-2'''      '''/dev/i2c-3'''      '''/dev/i2c-4'''      /dev/i2c-6

|}

</ol>

<li>~~After~~ Then connect a I2C device on the ~~setting~~ I2C pin of the 40PIN connector. Here is ~~set to input mode, execute~~ an example of the ~~following command to set the GPIO port as the pull -down mode~~DS1307 RTC module.</li~~></ol~~>

~~root@orangepi:~/wiringOP# '''gpio mode 5 up'''~~ ~~<ol start~~{| class="4wikitable" style="~~list-style~~width:800px;text-~~type~~align: ~~decimal~~center;">~~<li>Then enter the following command~~ |-||i2c2-m1|i2c3-m0|i2c4-m0|-| Sda Pin|Corresponding to ~~read the level of the GPIO port~~No. ~~If the level is 1, it means that the drawing mode is successful</li></ol>~~ 3 pin|Corresponding to No. 27 pin~~root@orangepi:~/wiringOP# '''gpio read 5'''~~|Corresponding to No. 19 pin|-~~'''1'''~~| Sck Pin|Corresponding to No. 5 pin~~<ol start="5" style="list-style-type: decimal;">~~|Corresponding to No. 28 pin~~<li>Then execute the following command~~ |Corresponding to ~~set the GPIO port as the drop~~No. 23 pin|-~~down mode</li></ol>~~| Vcc Pin~~root@orangepi:~/wiringOP# '''gpio mode 5 down'''~~|Corresponding to No. 1 pin|Corresponding to No. 1 pin|Corresponding to No. 1 pin~~<ol start="6" style="list~~|-~~style-type: decimal;"><li>Then enter the following command~~ | Gnd Pin|Corresponding to No. 6 pin|Corresponding to ~~read the level of the GPIO port~~No. ~~If the level is 0, it means that the drop -down mode is set successfully</li></ol>~~ 6 pin|Corresponding to No. 6 pin~~root@orangepi:~/wiringOP# '''gpio read 5'''~~|}

[[File:pi3b-img273.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then use the '''0i2cdetect -y'''command If the address of the connected I2C device can be detected, it means that the I2C can be used normally</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ sudo i2cdetect -y 2 #i2c2 command

~~=== 40pin SPI Test ===~~y 3 #i2c3 command

orangepi@orangepi:~$ sudo i2cdetect -y 4 # ~~From the schematic diagram of the 40PIN interface, the SPI available for Orange Pi 3B is spi3~~i2c4 command|}

~~[[File:pi3b-img264.png|577x193px]]~~<div class="figure">

~~'''In the Linux system, the SPI3 in 40pin is closed by default, and it needs to be opened manually to use~~[[File:pi3b-img274.~~'''~~png]]

</div></ol><ol start="5" style="list-style-type: decimal;"><li>You can then run the time of the ds '''ds1307.py''' test program in '''examples'''~~Add the configuration of the red font part below~~ to read the RTC time</~~boot~~li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~orangepiEnv.txt, and then restart the Linux system to open the spi3.~~wiringOP-Python# '''cd examples'''

~~orangepi~~root@orangepi:~$ /wiringOP-Python/examples# '''~~sudo vim /boot/orangepiEnv~~python3 ds1307.~~txt~~py --device \'''

'''~~overlays=spi3~~"/dev/i2c-~~m0-cs0-spidev~~4"'''

~~<ol start="2" style="list~~Thu 2023-~~style~~01-~~type~~05 14: ~~decimal;"><li>First check whether there is a '''spidev3.0''' device node in the Linux system. If it exists, it means that the SPI3 has been set. You can use it directly</li></ol>~~57:55

~~orangepi@orangepi~~Thu 2023-01-05 14:~~~$ '''ls /dev/spidev3.0'''~~57:56

~~/dev/spidev3.0~~Thu 2023-01-05 14:57:57

~~<ol start="3" style="list-style-type: decimal;"><li>Do not shorten the two pins of the SPI3 MOSI and MISO, and run the output result of the spidev_test as shown below. You can see that the data of TX and RX is inconsistent</li></ol>~~^C

~~orangepi@orangepi:~$ '''sudo spidev_test~~ exit|}</ol></~~spidev3.0'''~~span>

~~spi mode: 0x0~~=== 40pin's UART test ===

~~bits per word: 8~~# As can be seen from the table below, the UART available for Orange Pi 3B is UART3, UART7 and UART9. There are three sets of UART bus

~~max speed~~: ~~500000 Hz (500 KHz)~~:[[File:pi3b-img268.png]]

TX ::{| ~~FF FF FF FF FF FF~~ class="wikitable" style="width:800px;background-color:#ffffdc;" |-| <big>'''~~40 00 00 00 00 95~~As can be seen from the above table, I2C3_M0 and UART3_M0 are reused by pins, and the two cannot be opened at the same time''' ~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D~~ </big>| ~~......@.…▒..................▒.~~}

RX ::{| ~~FF FF FF FF FF FF~~ class="wikitable" style="width:800px;background-color:#ffffdc;" |-| <big>'''~~FF FF FF FF FF FF~~In the Linux system, the UART in 40pin is closed by default, and it needs to be opened manually to use.''' ~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF | ............................….~~

~~<ol start="4" style="list-style-type: decimal;"><li>Then~~ '''Add the ~~two pins~~ configuration of the ~~SPI3 MOSI (No~~red font part below to the /boot/orangepiEnv. ~~19 pins in the 40pin interface)~~ txt, and ~~MISO (No. 21 in~~ then restart the ~~40PIN interface) run~~ Linux system to open the ~~output of SPIDEV_TEST as follows.You can see that sending~~ UART3, UART7, and ~~receiving data is~~ UART9 at the sametime.If you only need to open one, you can fill in one'''</~~li></ol~~big>

~~[[File~~orangepi@orangepi:~~pi3b-img265~~~$ '''sudo vim /boot/orangepiEnv.~~png|577x83px]]~~txt'''

~~orangepi@orangepi:~$~~ '''~~sudo spidev_test~~ overlays=uart3-m0 uart7-v m2 uart9-~~D /dev~~m2</~~spidev3.0~~span>'''|}

~~spi mode~~<ol start="2" style="list-style-type: ~~0x0~~decimal;"><li>After entering the Linux system, first confirm whether there is a device node corresponding to UART under/dev</li>

~~bits per word~~{| class="wikitable" style="width: 8800px;" |-| orangepi@orangepi:~# '''ls /dev/ttyS*'''

~~max speed~~/dev/ttyS1      '''/dev/ttyS3      /dev/ttyS7      /dev/ttyS9'''|}</ol><ol start="3" style="list-style-type: ~~500000 Hz (500 KHz)~~decimal;"><li>Then start testing the UART interface, and first use the RX and TX of the UART interface to be tested by DuPont</li>

TX {| ~~FF FF FF FF FF FF~~ class="wikitable" style="width:800px;text-align: center;"|-||uart3|uart7|uart9|-| Tx Pin|Corresponding to the 28 pin|Corresponding to the 16 pin|Corresponding to the 29 pin|-| Rx Pin|Corresponding to the 27 pin|Corresponding to the 15 pin|Corresponding to the 7 pin|}</ol><ol start="4" style="list-style-type: decimal;"><li>Use the '''~~40 00 00 00 00 95~~serialTest.py''' ~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D~~ program in Examples to test the loop function of the serial port. If you can see the printing below, it means that the serial communication is normal<ol style="list-style-type: lower-alpha;"><li>Test UART3</li>{| ~~......~~class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python/examples# '''python3 serialTest.~~…▒..................▒.~~py --device \'''

~~RX | FF FF FF FF FF FF~~ '''~~40 00 00 00 00 95~~"/dev/ttyS3"''' ~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.~~

~~~~

~~=== 40pin I2C Test ===~~

~~# From the table below, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total of three groups of I2C bus.~~Out: 0: -> 0

~~[[File~~Out: 1:~~pi3b~~-~~img266.png|576x160px]]~~> 1

~~'''It can be seen from the above table that i2c4_m0 and spi3_m0 are pins. The two cannot be opened at the same time. i2c3_m0 and uart3_m0 are also reused. The two cannot be opened at the same time'''~~Out: 2: -> 2

~~'''In the Linux system, the i2c in 40Pin is closed by default, and it needs to be opened manually to use.'''~~Out: 3: -> 3

Out: 4:^C exit|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Test UART7</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python/examples# '''python3 serialTest.py --device \''' ''~~Add the configuration of the red font part below to the~~ '"/~~boot~~dev/~~orangepiEnv.txt, and then restart the Linux system to open the i2c2, i2c3, and i2c4 at the same time. If you only need to open one, then fill in one.~~ttyS7"'''

~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''~~

~~'''overlays=i2c2~~Out: 0: -~~m1 i2c3-m0 i2c4-m0'''~~> 0

~~<ol start="2" style="list-style~~Out: 1: -~~type: decimal~~>">~~<li>After starting the Linux system, first confirm that the i2c device node exists under/dev</li></ol>~~1

~~orangepi@orangepi~~Out: 2:~~~# '''ls /dev/i2c~~-*'''> 2

~~/dev/i2c-0 '''/dev/i2c-2''' '''/dev/i2c~~Out: 3: -> 3~~''' '''/dev/i2c-4''' /dev/i2c-6~~

~~<ol start="3" style="list-style-type~~Out: ~~decimal;"><li>Then connect a i2c device on the i2c pin of the 40Pin connector</li></ol>~~4:^C

exit|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Test UART9</li>{| class="wikitable" style="width:800px;"

|-

|~~|i2c2~~root@orangepi:~/wiringOP-m1~~|i2c3-m0|i2c4-m0~~|-~~| Sda Pin|Corresponding to No. 3 pin|Corresponding to No. 27 pin|Corresponding to No~~Python/examples# '''python3 serialTest. ~~19 pin~~|py -~~| Sck Pin|Corresponding to No. 5 pin|Corresponding to No. 28 pin|Corresponding to No. 23 pin~~|-~~| Vcc Pin|Corresponding to No. 1 pin|Corresponding to No. 1 pin|Corresponding to No. 1 pin~~|-~~| Gnd Pin|Corresponding to No. 6 pin|Corresponding to No. 6 pin|Corresponding to No. 6 pin~~|}device \'''

~~<ol start="4" style="list-style-type: decimal;"><li>Then use the~~ '''~~i2cdetect -y~~"/dev/ttyS9"''' ~~command if the address of the connected I2C device can be detected, it means that the I2C can be used normally</li></ol>~~

~~orangepi@orangepi:~$ sudo i2cdetect -y 2 #i2c2 command~~

~~orangepi@orangepi~~Out: 0:~~~$ sudo i2cdetect~~ -~~y 3 #i2c3 command~~> 0

~~orangepi@orangepi~~Out: 1:~~~$ sudo i2cdetect~~ -~~y 4 #i2c4 command~~> 1

~~<div class="figure">~~Out: 2: -> 2

~~[[File~~Out: 3:~~pi3b~~-~~img267.png|476x179px|UN}~]Q}T_70O%Z%RNO8R@YE]]~~> 3

~~</div>=== 40pin UART test ===~~Out: 4:^C

~~# As can be seen from~~ exit|}</ol></li></ol>

~~[[File:pi3b-img268.png|575x160px]]~~== Hardware watch the door dog test ==

~~'''As can be seen from~~ The WatchDog_test program is pre -installed in the ~~above table, i2c3_m0 and uart3_m0 are reused~~ Linux system released by ~~pins~~Orange PI, ~~and the two cannot~~ which can be ~~opened at the same time'''~~tested directly.

~~'''In~~ The method of running the ~~Linux system, the uart in 40pin~~ WatchDog_test program is ~~closed by default, and it needs to be opened manually to use.'''~~shown below:

~~'''Add~~ <ol style="list-style-type: lower-alpha;"><li>The second parameter 10 indicates the ~~configuration~~ counting time of the ~~red font part below to~~ door. If there is no dog feeding in this time, the system will restart.</~~boot~~p></~~orangepiEnv~~li><li>We can feed the dog by pressing any keys on the keyboard (except ESC).~~txt~~After the dog is fed, ~~and then restart~~ the ~~Linux system~~ program will print a line of Keep Alive to ~~open~~ indicate that the ~~uart3, uart7, and uart9 at the same time. If you only need to open one, you can fill in one..'''~~dog is successful</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ~~vim /boot/orangepiEnv.txt~~watchdog_test 10'''

~~'''overlays=uart3-m0 uart7-m2 uart9-m2'''~~open success

~~<ol start="2" style="list-style-type: decimal;"><li>After entering the Linux system~~options is 33152, ~~first confirm whether there~~ identity is ~~a device node corresponding to uart under/dev</li></ol>~~sunxi-wdt

~~orangepi@orangepi~~put_usr return,if 0,success:~~~# '''ls /dev/ttyS*'''~~0

~~/dev/ttyS1 '''/dev'''/'''ttyS3 /dev/ttyS7 /dev/ttyS9'''~~The old reset time is: 16

~~<ol start="3" style="list~~return ENOTTY,if -~~style-type~~1,success: ~~decimal;"><li>Then start testing the uart interface, first use the rx and tx of the uart interface to be tested by DuPont</li></ol>~~0

~~{| class="wikitable"~~|return ENOTTY,if -|~~|uart3|uart7|uart9~~|-~~| Tx pin|Corresponding to the 28 pin|Corresponding to the 16 pin|Corresponding to the 29 pin~~|-~~| Rx Pin|Corresponding to the 27 pin|Corresponding to the 15 pin|Corresponding to the 7 pin~~|}1,success:0

~~[[File~~put_user return,if 0,success:~~pi3b-img269.png|545x134px]]~~0

~~<ol start="4" style="list-style-type: decimal;"><li>Use the '''gpio serial''' command to test the loop function of the serial port as shown below. If you can see the following printing~~put_usr return,if 0, ~~it means that the serial communication is normal<ol style="list-style-type~~success: ~~lower-alpha;">~~0~~<li>Test UART3</li></ol></li></ol>~~keep alive

~~orangepi@orangepi:~$ '''sudo gpio serial /dev/ttyS3'''~~keep alive

~~[sudo] password for orangepi: #Enter~~ keep alive|}</ol>

~~Out: 0: -> 0~~== Check the serial number of the RK3566 chip ==

~~Out: 1: -> 1~~The commands of the RK3566 chip serial number are shown below. The serial number of each chip is different, so you can use the serial number to distinguish multiple development boards.

~~Out~~{| class="wikitable" style="width: 2800px;" |-| orangepi@orangepi: ~~-> 2~~~$ '''cat_serial.sh'''

~~Out~~Serial : ~~3: -> 3~~'''8fa18eaf489041f0'''|}

~~Out: 4:~~ 4method-of-downloading-and-installing-the-balenaetcher-version-of-arm64">

~~Out: 5: -> 5^C~~== The method of downloading and installing the balenaEtcher version of arm64 ==

<li>The download address of Balenaetcher ARM64 version is:

<li>The download address of the Deb installation package is shown below, and it needs to be installed to use</li>

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

|-

|

'''https://github.com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balena-etcher-electron_1.7.9+5945ab1f_arm64.deb'''

|}

</ol>

<li>~~Test UART7~~The download address of the Appimage version that does not need to be installed is shown below: </li><{| class="wikitable" style="width:800px;" |-| '''https://github.com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/~~ol>~~balenaEtcher-1.7.9+5945ab1f-arm64.AppImage'''|}

~~orangepi@orangepi:~$ '''sudo gpio serial /dev/ttyS7'''~~<div class="figure">

[~~sudo] password for orangepi~~[File: ~~#Enter the password here~~pi3b-img275.png]]

~~Out~~</div></ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>How to install and use the deb version of Balenaetcher: 0<ol style="list-style-type: lower-~~&gt~~alpha;"><li>deb version of Balenaetcher installation commands as shown below: </li>{| class="wikitable" style="width:800px; 0" |-| orangepi@orangepi:~$ '''sudo apt install -y \'''

~~Out: 1~~'''--fix-broken ./balena-etcher-electron_1.7.9+5945ab1f_arm64.deb'''|}</ol><ol start="2" style="list-style-type: lower-~~&gt~~alpha; 1"><li>After the deb version of Balenaetcher is installed, it can be opened in the Application</li>

~~Out: 2: -> 2~~<div class="figure">

~~Out: 3: -> 3~~ ~~Out: 4: -> 4~~ ~~Out: 5~~[[File: pi3b-~~> 5^C~~img89.png]]

</div></ol>

<li>~~Test UART9~~The interface after Balenaetcher is opened is shown below: </li~~></ol~~>

~~orangepi@orangepi:~$ '''sudo gpio serial /dev/ttyS9'''~~<div class="figure">

[~~sudo] password for orangepi~~[File: ~~#Enter the password here~~pi3b-img276.png]]

~~Out~~</div></ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>How to use the AppImage version of balenaEtcher: <ol style="list-style-type: lower-alpha;"><li>First add permissions to Balenaetcher</li>{| class="wikitable" style="width: 0800px;" |-| orangepi@orangepi: ~/Desktop$ '''chmod +x balenaEtcher-~~&gt~~1.7.9+5945ab1f-arm64.AppImage'''|}</ol><ol start="2" style="list-style-type: lower-alpha; 0"><li>Then select the AppImage version balenaEtcher right -click the mouse, and then click Execute to open balenaEtcher</li>

~~Out: 1~~[[File: pi3b-img277.png]]</ol></li></ol> 1panel">

~~Out: 2:~~ == The installation method of the Bt-~~> 2~~Panel Linux panel ==

~~Out~~{| class="wikitable" style="background-color:#ffffdc;width: 3800px;" |-| <big>'''Bt-Panel Linux panel is a server management software that improves operation and maintenance efficiency. It supports more than 100 server management functions such as one -click LAMP/LNMP/cluster/monitoring/website/FTP/database/Java (excerpted from the [https: //www.bt.cn/new/index.html official website of the Bt-~~> 3~~Panel])'''</big>|}

~~Out~~# First of all, the size of the'''/tmp''' space is needed. After setting, you need to '''restart the Linux system of the development board''', and the command is shown below: ~~-> 4~~

~~Out~~: 5: {| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo sed -i 's/nosuid/&gtamp; ~~5^C~~,size=2G/' /etc/fstab'''

~~~~orangepi@orangepi:~$ '''sudo reboot'''~~=== PWM test method ===~~|}

~~# From~~ <ol start="2" style="list-style-type: decimal;"><li>After restarting, you can see that the ~~table below,~~ size of the ~~pwm11 available for Orange Pi 3B~~'''/tmp''' space has become 2G.</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''df -h | grep "/tmp"'''

~~[[File~~tmpfs      2.0G      12K      '''2.0G'''      1% /tmp|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then enter the following command in the Linux system to start the installation of the Bt-Panel</li>{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img270~~| orangepi@orangepi:~$ '''sudo install_bt_panel.~~png~~sh'''|~~575x160px]]~~}</ol><ol start="4" style="list-style-type: decimal;"><li>Then the pagoda installation program reminds whether to install the '''Bt-Panel''' to the'''/www''' folder, and enter '''y''' at this time</li>{| class="wikitable" style="width:800px;" |-| +----------------------------------------------------------------------

~~'''In the Linux system, the pwm in 40pin is closed by default, and it needs to be opened manually to use..'''~~| Bt-WebPanel FOR CentOS/Ubuntu/Debian

~~'''Add the configuration of the red font part below to the /boot/orangepiEnv.txt, and then restart the Linux system to open the pwm11.'''~~+----------------------------------------------------------------------

~~'''overlays=pwm11~~+----------------------------------------------------------------------~~m1'''~~

<~~ol start="2" style="list-style-type: decimal;"~~p>~~<li>After opening a pwm, a pwmchipX (X is a specific number)~~ | The WebPanel URL will be ~~available in'''~~http:/~~sys~~/~~class/pwm/'''</li>~~SERVER_IP:8888 when installed.</olp>

~~orangepi@orangepi:~$ '''ls /sys/class/pwm/'''~~+----------------------------------------------------------------------

~~pwmchip0 pwmchip1~~

~~<ol start="3" style="list-style~~Do you want to install Bt-~~type: decimal;"><li>Which pwmchip corresponds~~ Panel to ~~pwm11 above? Let's first check out~~ the ~~output of '''ls~~ /~~sys~~www directory now?(y/~~class/pwm/ -l~~n): ''' ~~command, as shown below~~y</~~li><li><p~~span>~~The base address of the pwm11 register is Fe6F0030. Then see the output of '''ls /sys/class/pwm/ -l~~''' ~~command, you can see that the fe6f0030.pwm is connected to the pwmchip1, so the PWM11 corresponding pwmchip is pwmchip1</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img271.png~~|~~576x46px|RCUS$_~VYM{4ZS]_L~~}~~DNZQR]]~~ </~~div~~ol>

<li>Then ~~use~~ you have to wait patiently. When you see the ~~following command to allow pwm11 to~~ printing information below the terminal output ~~a 50Hz square wave (please switch~~ , it means that the pagoda has been installed. The entire installation process takes about 34 minutes. There may be some differences according to the ~~root user first, and then execute the following command)~~difference in network speed</li~~></ol~~>

~~root@orangepi~~[[File:~# pi3b-img278.png|800px]]</ol><ol start="6" style="list-style-type: decimal;"><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'''~~echo 0 >~~ displayed in the corresponding position to log in to the Bt-Panel [[File:pi3b-img279.png|1200px]]</~~class~~p></~~pwm~~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 Bt-Panel</~~pwmchip1~~p></~~export'''~~li>

~~root@orangepi~~[[File:~# pi3b-img280.png|1200px]]</ol><ol start="8" style="list-style-type: decimal;"><li>After entering the Bt-Panel, you will first prompt that you need to bind the account of the Bt-Panel official website. If you do n't have an account, you can go to the pagoda's official website (''~~echo 20000000 > /sys/class/pwm~~'https:/~~pwmchip1~~/~~pwm0/period~~www.bt.cn''') to register one.</li>

~~root@orangepi~~[[File:~~~# '''echo 1000000 &gt~~pi3b-img281.png|1200px]]</ol><ol start="9" style="list-style-type: decimal; "><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 state, CPU usage, memory usage and storage space usage</~~sys/class/pwm/pwmchip1/pwm0/duty_cycle'''~~li>

~~root@orangepi~~[[File:~~~# '''echo 1 &gt~~pi3b-img282.png|1200px]]</ol><ol start="10" style="list-style-type: decimal; "><li>More functions of the Bt-Panel can refer to the following information to explore by yourself</~~sys/class/pwm/pwmchip1/pwm0/enable'''~~li>

{| class="wikitable" style="width:800px;" |-| Manual: [~~[File~~http://docs.bt.cn '''http:~~pi3b-img272~~//docs.bt.~~png|575x346px]~~cn''']

~~<~~Forum address: [https:/~~span>== How to install and use Wiringop-Python ==~~/www.bt.cn/bbs '''https://www.bt.cn/bbs''']

GitHub Link: '''Wiringop-Python is the library of the Python language version of Wiringop. It is used to operate the development board's GPIO, I2C, SPI and UART hardware resources such as the development board in the Python programhttps://github.com/aaPanel/BaoTa'''|}</ol>

~~'''Please note that all~~ == Set the ~~following command below is operated under the root user.'''~~Chinese environment and install Chinese input method ==

~~'''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.'''</~~span~~big>~~=== Wiringop-Python installation method ===|}

~~# First install the dependency package~~=== Debian system installation method ===

~~root@orangepi~~<ol style="list-style-type:~# decimal;"><li>First set the default '''locale''~~sudo apt~~' as Chinese<ol style="list-~~get update~~style-type: lower-alpha;"><li>Enter the command below to start configured '''locale'''</li>

~~root~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~# $ '''sudo ~~apt~~dpkg-~~get~~ reconfigure locales'''|}</ol><ol start="2" style="list-~~y install git swig python3~~style-~~dev python3~~type: lower-~~setuptools~~alpha;"><li>Then select '''zh_CN.UTF-8 UTF-8''' in the pop-up interface (to move up and down through the upper and lower direction buttons on the keyboard, select it through the space key, and finally move the cursor to '''<OK>'''through the TAB key, then press the ENTER key )</li>

[[File:pi3b-img283.png|1200px]]</ol><ol start="23" style="list-style-type: ~~decimal~~lower-alpha;"><li>Then ~~use the following command to download~~ set the ~~source code of wiringOP~~default '''locale''' as '''zh_CN.UTF-~~Python~~8'''</li~~></ol~~>

[[File:pi3b-img284.png|1200px]]</ol><ol start="4" style="list-style-type: lower-alpha;"><li>After exiting the interface, the '''locale'''~~Note that~~ settings will be started. The output displayed by the ~~following git clone~~command line is shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg-recursivee command will automatically download the source code of Wiringop, because Wiringop-Python depends on Wiringop. Please make sure that the download process does not report an error due to network problems.reconfigure locales'''

~~'''If there is~~ Generating locales (this might take a ~~problem with the download code from GitHub, you can use the Wiringop-Python source code that comes with the Linux image directly, and the storage location is:/usr/src/wiringOP-Python'''~~while)...

~~root@orangepi~~:~~~# '''git clone~~ en_US.UTF-~~-recursive https://github~~8...~~com/orangepi-xunlong/wiringOP-Python -b next'''~~done

~~root@orangepi~~:~~~# '''cd wiringOP~~zh_CN.UTF-~~Python'''~~8... done

~~root@orangepi:~~~Generation complete.|}</ol></li></~~wiringOP~~ol><ol start="2" style="list-~~Python#~~ style-type: decimal;"><li>Then open '''~~git submodule update --init --remote~~Input Method'''</li>

[[File:pi3b-img285.png]]

</ol>

<li>Then ~~use the following command to compile wiringOP-Python and install it into the Linux system of the development board~~select '''OK'''</li~~></ol~~>

~~root@orangepi~~[[File:~# pi3b-img286.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select '''~~cd wiringOP-Python~~Yes'''</li>

~~root@orangepi~~[[File:~pi3b-img287.png]]</~~wiringOP~~ol><ol start="5" style="list-~~Python#~~ style-type: decimal;"><li>Then select '''~~python3 generate-bindings.py > bindings.i~~fcitx'''</li>

~~root@orangepi~~[[File:~pi3b-img288.png]]</~~wiringOP~~ol><ol start="6" style="list-style-~~Python#~~ type: decimal;"><li>Then select '''~~sudo python3 setup.py install~~OK'''</li>

[[File:pi3b-img289.png]]</ol><ol start="47" style="list-style-type: decimal;"><li>'''Then ~~enter~~ restart the ~~following command. If there is a help information output, it means that Wiringop-Python is successfully installed. Press~~ Linux system to make the configuration effective'''q</li><li>Then open '''Fcitx configuration''' ~~key to exit the interface of the help information~~</lip></olli>

~~root@orangepi~~[[File:~pi3b-img290.png]]</~~wiringOP~~ol><ol start="9" style="list-~~Python# '''python3~~ style-~~c &quot~~type: decimal;~~import wiringpi; help(wiringpi)"'''~~"><li>Then click the + of the position shown in the figure below</li>

~~Help on module wiringpi~~[[File:pi3b-img291.png]]</ol><ol start="10" style="list-style-type: decimal;"><li>Then search '''Google Pinyin''' and click '''OK'''</li>

~~NAME~~<div class="figure">

~~wiringpi~~[[File:pi3b-img292.png]]

~~DESCRIPTION~~</div></ol><ol start="11" style="list-style-type: decimal;"><li>Then put '''Google Pinyin''' to the front</li>

~~# This file was automatically generated by SWIG (http~~[[File:~~//www.swig.org)~~pi3b-img293.png]]

~~# Version 4~~[[File:pi3b-img294.~~0.2~~png]]</ol><ol start="12" style="list-style-type: decimal;"><li>Then open the '''Geany''' editor to test the Chinese input method</li>

#[[File:pi3b-img295.png]]</ol><ol start="13" style="list-style-type: decimal;"><li>The Chinese input method test is shown below</li>

~~# Do not make changes~~ [[File:pi3b-img296.png]]</ol><ol start="14" style="list-style-type: decimal;"><li>You can switch the Chinese and English input method through the '''Ctrl+Space''' shortcut</li><li>If the entire system is required as Chinese, the variables in '''/etc/default/locale''' can be set to ~~this file unless you know what you are doing~~'''zh_CN.UTF-8'''</li>{| class="wikitable" style="width:800px;" |-~~modify~~| orangepi@orangepi:~$ '''sudo vim /etc/default/locale'''

# ~~the SWIG interface file instead.~~File generated by update-locale

LC_MESSAGES='''<~~ol start="5"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>Test whether the Wiringop~~zh_CN.UTF-~~Python is installed successfully under the Python command line is shown below: <ol style="list-style-type: lower-alpha;"><li>First use the Python3 command to enter the command line mode of Python3</li></ol></li>~~8</olspan>'''

~~root@orangepi:~#~~ LANG='''~~python3~~zh_CN.UTF-8'''

LANGUAGE='''zh_CN.UTF-8'''|}</ol><ol start="216" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~import~~ '''restart the ~~Python module of WiringPi~~system</lispan>''' to see the system displayed as Chinese</olli>

~~>>> '''import wiringpi;'''~~[[File:pi3b-img297.png]]</ol>

~~<ol start~~=~~"3" style~~=~~"list-style-type: lower-alpha;"><li>Enter the following command to view the help information~~ = The installation method of ~~Wiringop-Python, and press the '''q''' key to exit the interface of the help information</li></ol>~~Ubuntu 20.04 system ===

~~>>>~~ # First open '''~~help(wiringpi)~~Language Support'''

~~Help on module wiringpi~~::[[File:pi3b-img298.png]]

~~NAME~~<ol start="2" style="list-style-type: decimal;"><li>Then find '''Chinese (China)''' option</li>

~~wiringpi~~[[File:pi3b-img299.png]]</ol><ol start="3" style="list-style-type: decimal;"><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 is shown below: </li>

~~DESCRIPTION~~[[File:pi3b-img300.png]]

{| class="wikitable" style="background-color:# ~~This file was automatically generated by SWIG (http~~ffffdc;width:800px;" |-| <big>'''Note that this step is not easy to drag, please try more patiently.'''</big>|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system</~~www.swig.org).~~li>

~~# Version 4~~[[File:pi3b-img301.~~0.2~~png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then set the '''Keyboard input method system''' to '''fcitx'''</li>

[[File:pi3b-img302.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>'''Then restart the Linux system to make the configuration effective'''</li><li>After re -entering the system, please do '''not ask me again''' at the interface below, and then determine whether the standard folder should be updated as Chinese based on your preference.</li>

~~# Do not make changes to this file unless you know what you are doing~~[[File:pi3b-img303.png]]</ol><ol start="8" style="list-style-~~modify~~type: decimal;"><li>Then you can see that the desktop is displayed as Chinese</li>

# [[File:pi3b-img304.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then we can open the '''Geany''' to test Chinese input method , and the way to open is shown in the ~~SWIG interface file instead.~~figure below</li>

~~CLASSES~~[[File:pi3b-img305.png]]</ol><ol start="10" style="list-style-type: decimal;"><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</li>

~~builtins~~[[File:pi3b-img306.~~object~~png]]</ol>

~~GPIO~~=== The installation method of ubuntu 22.04 system ===

~~I2C~~# First open '''Language Support'''

~~Serial~~::[[File:pi3b-img298.png]]

~~nes~~<ol start="2" style="list-style-type: decimal;"><li>Then find '''Chinese (China)''' option</li>

~~class GPIO~~[[File:pi3b-img307.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then use the left mouse button to select '''Chinese (~~builtins~~China)''' and hold it down, and then drag it up to the beginning.~~object)~~The display after dragging is shown in the figure below: </li>

[[File:pi3b-img308.png]] {| ~~GPIO(pinmode~~class=0)"wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that this step is not easy to drag, please try more patiently.'''</big>|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system</li>

|[[File:pi3b-img309.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>'''Then restart the Linux system to make the configuration effective'''</li><li>After re -entering the system, please '''do not ask me again''' at the interface below, and then determine whether the standard folder should be updated as Chinese based on your preference</li>

~~>>&gt~~[[File:pi3b-img303.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Then you can see that the desktop is displayed as Chinese</li>

[[File:pi3b-img304.png]]</ol><~~span id~~ol start="~~pin~~8" style="list-~~gpio~~style-~~port-test-1~~type: decimal;"><li>Then open the Fcitx5 configuration program</~~span~~li>~~=== 40pin GPIO port test ===~~

~~'''Wiringop~~[[File:pi3b-~~Python is the same as Wiringop~~img310. ~~You can also determine which GPIO pink can be determined by specifying the WPI number. Because there is no command~~ png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then choose to ~~check the WPI number in Wiringop-Python, you can only check the board WPI number and physical physical physics through the GPIO command in Wiringop. The corresponding relationship of the pin.'''~~use Pinyin input method</li>

[[File:pi3b-~~img258~~img311.png~~|575x355px|66AC(IBG%N8L@Y7(1BZPS`N~~]]

</div></ol>~~# Below the No. 7 pin — corresponding to GPIO4_a4~~ <ol start="10" style="list-~~corresponding WPI serial number 2~~ style-~~to demonstrate how to set the height of~~ type: decimal;"><li>The interface after the ~~GPIO port~~selection is shown below, then click OK</li>

[[File:pi3b-~~img259~~img312.png~~|576x120px~~]]</ol><ol start="11" style="list-style-type: decimal;"><li>Then we can open the '''Geany''' to test Chinese input method, and the way to open is shown in the figure below</li>

~~<ol start="2" style="list~~[[File:pi3b-~~style-type: decimal;">~~img305.png]]~~<li>The steps of the command test are shown below directly:~~ </pol><ol start="12" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~First set the GPIO port to the output mode~~After opening '''Geany''', it is still an English input method by default. ~~The first parameter of~~ We can switch into Chinese input methods through the '''~~pinMode~~Ctrl+Space''' ~~function is the serial number of the wpi corresponding to the pin~~shortcut keys, and ~~the second parameter is the GPIO mode</li></ol>~~then we can enter Chinese</li~~></ol~~>

~~root@orangepi~~[[File:~pi3b-img313.png]]</~~wiringOP~~ol>

~~'''from wiringpi import GPIO; wiringpi.wiringPiSetup() ; \'''~~== How to remotely log in to the Linux system desktop method ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~wiringpi~~Ubuntu Gnome Wayland image does not support Nomachine and VNCs introduced here to remotely log in to the desktop.~~pinMode(2, GPIO.OUTPUT) ; "~~'''</big>|}

<~~ol start~~span id="~~2" style="list~~use-~~style~~nomachine-~~type: lower~~remote-~~alpha;~~login"><li>Then set the GPIO port output low level. After setting, you can use the voltage of the voltage of the universal meter to measure the pins. If it is 0V, it means that the low -power flat is successful</~~li></ol~~span>=== Use nomachine remote login ===

~~root@orangepi~~{| class="wikitable" style="background-color:#ffffdc;width:~~~/wiringOP~~800px;" |-~~Python#~~ | <big>'''~~python3 -c "import wiringpi; \~~Make sure the Ubuntu or Debian system installed on the development board is a desktop version. In addition, nomachine also provides detailed documents. It is strongly recommended to read this document to be familiar with the use of nomachine. The document links are shown below: '''

'''~~from wiringpi import GPIO~~https://knowledgebase.nomachine.com/DT10R00166'''</big>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Nomachine supports Windows, Mac, Linux, iOS, and Android platforms, so we can remotely log in to control Orange PI development boards through Nomachine on multiple devices. The following demonstrates the Linux system desktop of the Orange PI development board through Nomachine in Windows. For installation methods for other platforms, please refer to the official documentation of Nomachine.'''</big>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Before operation, please ensure that the Windwos computer and the development board are in the same local area network, and can log in to the Ubuntu or Debian system that can log in to the development board normally.'''</big>|} <ol style="list-style-type: decimal; ~~wiringpi~~"><li>First download the nomachine software Linux '''ARM64''' DEB version of the installation package, and then install it in the Linux system of the development board<ol style="list-style-type: lower-alpha;"><li>Since RK3566 is a SOC of the ARMV8 architecture, the system we use is Ubuntu or Debian, so you need to download '''NoMachine for ARM ARMv8 DEB''' installation package here. The download link is shown below: </li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that this download link may change, please recognize the DEB package of the ARMV8/ARM64 version.'''</big>|}{| class="wikitable" style="width:800px;" |-| [https://www.nomachine.com/download/download&id=112&s=ARM '''https://downloads.nomachine.~~wiringPiSetup()~~ com/download/?id=118&\distro=ARM''']|}

[[File:pi3b-img314.png]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>In addition, you can also download the installation package to '''NoMachine''' in the '''~~wiringpi.digitalWrite(2, GPIO.LOW)"~~official tools'''.</li>

~~<ol start="3" style="list-style-type~~[[File: ~~lower-alpha;"><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~~ pi3b-~~power flat is successful~~img315.~~</li></ol>~~png]]

~~root@orangepi:~/wiringOP-Python#~~ First enter the '''~~python3~~ remote login software-~~c "import wiringpi; \~~Nomachine'''folder

~~'''from wiringpi import GPIO; wiringpi~~[[File:pi3b-img316.~~wiringPiSetup() ;\'''~~png]]

~~'''wiringpi.digitalWrite(2, GPIO.HIGH)"'''~~Then download the ARM64 version of the DEB installation package

[[File:pi3b-img317.png]]</ol><ol start="3" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~The steps~~ Then upload the downloaded '''nomachine_x.x.x_x_arm64.deb''' to the Linux system of ~~testing in~~ the ~~command line of Python3 are shown below:~~ development board.<~~ol style="list-style-type: lower-alpha;"~~/li><li>~~First~~ Then use the ~~Python3~~ following command to ~~enter~~ install '''NoMachine''' in the ~~command line mode~~ Linux system of ~~Python3~~the development board</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg -i nomachine_x.x.x_x_arm64_arm64.deb'''|}</ol>

</li></ol>

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

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

|-

|

<big>'''Note that this download link may change.'''</big>

|}

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

|-

|

'''https://downloads.nomachine.com/download/?id=9'''

|}

~~root@orangepi~~[[File:~# pi3b-img318.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then install nomachine in Windows. '''Please restart the computer after installation'''</li><li>Then open '''~~python3~~NoMachine'''in Window</li>

[[File:pi3b-img319.png]]</ol><ol start="25" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then import~~ After Nomachine starts, it will automatically scan other devices installed in the local area network. After entering the ~~Python module~~ main interface of ~~WiringPi~~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. Start log in to the Linux system desktop of the development board</li~~></ol~~>

~~>>&gt~~[[File:pi3b-img320.png]]</ol><ol start="6" style="list-style-type: decimal; "><li>Then click '''~~import wiringpi~~OK'''</li>

~~>>&gt~~[[File:pi3b-img321.png]]</ol><ol start="7" style="list-style-type: decimal; "><li>Then enter the username and password of the Linux system in the corresponding position in the figure below, and then click '''~~from wiringpi import GPIO~~OK'''to start logging in</li>

<~~ol start~~div class="3figure" ~~style="list-style-type: lower-alpha;">~~<li>Then set the GPIO port as the output mode. The first parameter of the '''pinMode''' function is the serial number of the wpi corresponding to the pin, and the second parameter is the GPIO mode.</li></ol>

~~>>> '''wiringpi~~[[File:pi3b-img322.~~wiringPiSetup()'''~~png]]

0</div></ol><ol start="8" style="list-style-type: decimal;"><li>Then click OK in the next interface</li><li>Finally, you can see the desktop of the development board Linux system[[File:pi3b-img323.png]]</li></ol>

~~>>> '''wiringpi.pinMode(2, GPIO.OUTPUT)'''~~

~~<ol start~~=~~"4" style~~=~~"list-style-type: lower-alpha;"><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.</li></ol>~~= Use VNC remote login ===

~~&gt~~{| class="wikitable" style="background-color:#ffffdc;~~>&gt~~width:800px; " |-| <big>'''~~wiringpi.digitalWrite(2~~Before operation, please ensure that the Windwos computer and the development board are in the same local area network, ~~GPIO~~and you can log in to the Ubuntu or Debian system of the development board normally.~~LOW)~~'''

'''<~~ol start="5"~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<li>Then set the GPIO port output high level~~Ubuntu 20. ~~After setting~~04 tests many problems with VNC, ~~you can~~ please do not use ~~the value of the voltage of the pins with a multimeter. If it is 3~~this method.~~3V, it means that the high -power flat is successful~~</lispan>'''</olbig>|}

~~>>>~~ # First run the '''~~wiringpi~~set_vnc.~~digitalWrite(2~~sh''' script settings, ~~GPIO.HIGH)~~and '''remember to add Sudo permissions'''

~~<ol start~~::{| class="4wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Wiringop~~|-~~Python Sets GPIO high and low levels in the Python code. For reference to the '''blink.py''' test program in Examples, the voltage of the~~ | orangepi@orangepi:~$ '''~~blink~~sudo set_vnc.pysh''' ~~test program will set up the voltage of all GPIO ports in the development board 40 PIN</li></ol>~~

~~root@orangepi:~/wiringOP-Python# '''cd examples'''~~You will require a password to access your desktops.

~~root@orangepi:~/wiringOP-Python/examples# '''ls blink.py'''~~

Password:        '''~~blink.py~~#Set the VNC password here, 8 -bit characters'''

~~root@orangepi~~Verify:~~~/wiringOP-Python/examples~~       '''#Set the VNC password here, 8 -bit characters'''

Would you like to enter a view-only password (y/n)? '''n~~=== 40pin SPI test ===~~'''

~~# From the schematic diagram of the 40pin interface, the SPI available for Orange Pi 3B is spi3~~xauth: file /root/.Xauthority does not exist

~~[[File:pi3b-img264.png|577x193px]]~~

New 'X'~~'In the Linux system, the spi3 in 40pin~~ desktop is ~~closed by default, and it needs to be opened manually to use.'''~~orangepi3b:1

~~'''Add the configuration of the red font part below to the /boot/orangepiEnv.txt, and then restart the Linux system to open the spi4.'''~~

~~orangepi@orangepi:~$ '''sudo vim~~ Creating default startup script /~~boot~~root/~~orangepiEnv~~.~~txt'''~~vnc/xstartup

~~'''overlays=spi3-m0-cs0-spidev'''~~Starting applications specified in /root/.vnc/xstartup

~~<ol start="2" style="list-style-type: decimal;"><li>First check whether there~~ Log file is ~~a '''spidev3~~/root/.~~0''' device node in the Linux system~~vnc/orangepi3b:1. ~~If it exists, it means that the SPI3 has been set and can be used directly</li></ol>~~log

~~orangepi@orangepi:~$ '''ls /dev/spidev3.0'''~~

~~/dev/spidev3.0~~Killing Xtightvnc process ID 3047

~~<ol start="3" style="list-style-type: decimal;">~~

~~<li>You can then use the spi back function under the '''spidev_test.py''' program in Examples. The '''spidev_test.py''' program needs to specify the following two parameters: ~~

~~<ol style="list-style-type: lower-alpha;">~~

~~<li>'''--channel''': Specify the channel number of SPI</li>~~

~~<li>'''--port''': Specify the port number of SPI</li></ol>~~

~~</li>~~

<li>Do not pick up the two pins of the SPI3 MOSI and MISO in short, and run the output result of the spidev_test.py as shown below. You can see that the data of TX and RX are inconsistent</li></ol>

~~root@orangepi:~/wiringOP-Python# '''cd examples'~~New 'X'desktop is orangepi3b:1

~~root@orangepi:~/wiringOP-Python/examples# '''python3 spidev_test.py \'''~~

~~'''--channel 3 --port 0'''~~Starting applications specified in /root/.vnc/xstartup

~~spi mode~~Log file is /root/.vnc/orangepi3b: ~~0x0~~1.log|}

~~max speed~~<ol start="2" style="list-style-type: ~~500000 Hz (500 KHz)~~decimal;"><li>The steps of using MobaxTerm software to connect the development board Linux system desktop are shown below: <ol style="list-style-type: lower-alpha;"><li>First click Session, then select VNC, then fill in the IP address and port of the development board, and finally click OK to confirm</li>

~~Opening device /dev/spidev3.0~~<div class="figure">

~~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 |~~[[File:pi3b-img324.~~.....@.......…|~~png]]

~~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 |.............….|~~</div></ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then enter the password of the previously set VNC</li>

[[File:pi3b-img325.png]]</ol><ol start="53" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then use~~ The interface after the ~~TXD (No. 19 pins~~ login is shown as shown in the ~~40Pin interface)~~ figure below, and ~~RXD (No. 21 pins in~~ then the ~~40pin interface)~~ desktop of the ~~DuPont line short connection SPI3~~Linux system can be remotely operated[[File:pi3b-img326. ~~Like sending and receiving data, it means that the SPI3 loop test is normal~~png]]</li></ol></li></ol>

~~root@orangepi:~~~</~~wiringOP-Python# '''cd examples'''~~span>

~~root@orangepi:~/wiringOP-Python/examples# '''python3 spidev_test.py \'''~~== Some programming language tests supported by Linux system ==

~~'''~~=== Debian Bullseye system ===

~~spi mode~~<ol style="list-style-type: ~~0x0~~decimal;"><li>Debian Bullseye is equipped with a gcc compilation tool chain by default, which can directly compile the C language program in the Linux system of the development board<ol style="list-style-type: lower-alpha;"><li>The version of the gcc is shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc --version'''

~~max speed: 500000 Hz~~ gcc (~~500 KHz~~Debian 10.2.1-6)10.2.1 20210110

~~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 |~~This is free software; see the source for copying conditions.~~.....@.......…|~~There is NO

RX warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.| ~~FF FF FF FF FF FF~~ }</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Write C language of '''~~40 00 00 00 00 95~~Hello_world.c''' ~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D~~ program</li>{| class="wikitable" style="width:800px;" |-|~~......~~orangepi@orangepi:~$ '''vim hello_world.~~......…|~~c'''

~~~~

~~=== 40pin I2C test ===~~

<~~ol start="5" style="list-style-type: decimal~~p>#include <stdio.h>">~~<li>As can be seen from the table below, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total of three groups of I2C bus</li>~~</olp>

~~[[File:pi3b-img266.png|576x160px]]~~int main(void)

~~'''It can be seen from the above table that I2C4_M0 and SPI3_M0 are pins. The two cannot be opened at the same time. I2C3_M0 and UART3_M0 are also reused. The two cannot be opened at the same time'''~~{

~~'''In the Linux system, the I2C in 40Pin is closed by default, and it needs to be opened manually to use.'''~~:printf("Hello World!\n");

'''Add the configuration of the red font part below to the/boot/orangepiEnv.txt, and then restart the Linux system to open the I2C2, i2C3, and I2C4 at the same time. If you only need to open one, then fill in one.'''

~~orangepi@orangepi~~:~~~$ '''sudo vim /boot/orangepiEnv.txt'''~~return 0;

~~'''overlays=i2c2-m1 i2c3-m0 i2c4-m0'''~~}|}</ol><ol start="63" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~After starting the Linux system, first confirm the I2C device node under/dev~~Then compile and run '''hello_world.c'''</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''

orangepi@orangepi:~# $ '''ls ./dev/i2c-*hello_world'''

Hello World!|}</~~dev~~ol></~~i2c-0 '''~~li></~~dev/i2c-2''' '''/dev/i2c-3''' '''/dev/i2c-4''' /dev/i2c-6~~ol><ol start="72" style="list-style-type: decimal;"><li>~~Then connect a I2C device on the I2C pin of the 40PIN connector. Here is an example of the DS1307 RTC module.~~Debian BullSeye Default with Python3<ol style="list-style-type: lower-alpha;"><li>The specific version of Python is shown below</olli> {| class="wikitable" style="width:800px;"

|-

|~~|i2c2-m1|i2c3-m0|i2c4-m0~~|-~~| Sda Pin|Corresponding to No. 3 pin|Corresponding to No. 27 pin|Corresponding to No. 19 pin~~|-~~| Sck Pin|Corresponding to No. 5 pin|Corresponding to No. 28 pin|Corresponding to No. 23 pin~~|-~~| Vcc Pin|Corresponding to No. 1 pin|Corresponding to No. 1 pin|Corresponding to No. 1 pin~~|-~~| Gnd Pin|Corresponding to No. 6 pin|Corresponding to No. 6 pin|Corresponding to No. 6 pin~~|}orangepi@orangepi:~$ '''python3'''

~~[[File~~'''Python 3.9.2''' (default, Feb 28 2021, 17:03:~~pi3b-img273.png|180x153px]]~~44)

~~<ol start="8" style="list-style-type: decimal;"><li>Then use the '''i2cdetect -y''' command If the address of the connected I2C device can be detected, it means that the I2C can be used normally</li></ol>~~[GCC 10.2.1 20210110] on linux

~~orangepi@orangepi:~$ sudo i2cdetect -y 2 #i2c2 command~~Type "help", "copyright", "credits" or "license" for more information.

~~orangepi@orangepi~~>>>|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>'''hello_world.py''' program in Python language</li>{| class="wikitable" style="width:~~~$ sudo i2cdetect~~ 800px;" |-~~y 3 #i2c3 command~~| orangepi@orangepi:~$ ~~sudo i2cdetect -y 4 #i2c4 command~~'''vim hello_world.py'''

print('Hello World!')|}<~~div~~ /ol><ol start="3" style="list-style-type: lower-alpha;"><li>The results of running '''hello_world.py''' are shown below</li>{| class="~~figure~~wikitable" style="width:800px;">|-| orangepi@orangepi:~$ '''python3 hello_world.py'''

~~[[File~~Hello World!|}</ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>Debian Bullseye's compilation tool and operating environment that is not installed in Java by default<ol style="list-style-type:~~pi3b~~lower-~~img274~~alpha;"><li>You can use the following command to install OpenJDK.~~png~~The latest version in Debian Bullseye is openjdk-17</li>{| class="wikitable" style="width:800px;" |~~464x174px~~-|Vorangepi@~~(61L~~orangepi:~0$ '''sudo apt install -y openjdk-17-jdk'''|}~~)Q`8VLBCAYEP[~~</ol><ol start="2]]" style="list-style-type: lower-alpha;"><li>After installation, you can check the version of Java</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''java --version'''|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Edit the '''hello_world.java''' of the Jave version</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''

~~</div><ol start="9" style="list-style-type: decimal;"><li>You can then run the time of the ds '''ds1307.py''' test program in '''examples''' to read the RTC time</li></ol>~~public class hello_world

~~root@orangepi:~/wiringOP-Python# '''cd examples'''~~{

~~root@orangepi~~:~~~/wiringOP-Python/examples# '''python3 ds1307.py --device \'''~~public static void main(String[] args)

~~'''"/dev/i2c-4"'''~~:{

~~Thu 2023-01-05 14~~:57:55System.out.println("Hello World!");

~~Thu 2023-01-05 14~~:~~57:56~~}

~~Thu 2023~~}|}</ol><ol start="4" style="list-01style-~~05 14~~type:57lower-alpha;"><li>Then compile and run '''hello_world.java'''</li>{| class="wikitable" style="width:57800px;" |-| ^Corangepi@orangepi:~$ '''javac hello_world.java'''

~~exit~~orangepi@orangepi:~$ '''java hello_world'''

Hello World!|}</ol></li></ol>~~=== 40pin's UART test ===~~

~~# As can be seen from the table below, the UART available for Orange Pi 3B is UART3, UART7 and UART9. There are three sets of UART bus~~=== Ubuntu Focal system ===

~~[[File~~<ol style="list-style-type: decimal;"><li>Ubuntu Focal has the GCC compilation tool chain by default, which can compile the C language program directly in the Linux system of the development board.<ol style="list-style-type: lower-alpha;"><li>The version of the gcc is shown below</li>{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img268.png~~|~~575x160px]]~~orangepi@orangepi:~$ '''gcc --version'''

~~'''As can be seen from the above table, I2C3_M0 and UART3_M0 are reused by pins, and the two cannot be opened at the same time'''~~gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0

This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>'''hello_world.c'''~~Add the configuration of the red font part below~~ program to ~~the~~ write C language</~~boot/orangepiEnv~~li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.~~txt, and then restart the Linux system to open the UART3, UART7, and UART9 at the same time. If you only need to open one, you can fill in one~~c''' #include <stdio.h>

~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''~~

~~'''overlays=uart3-m0 uart7-m2 uart9-m2'''~~int main(void)

~~<ol start="2" style="list-style-type: decimal;"><li>After entering the Linux system, first confirm whether there is a device node corresponding to UART under/dev</li></ol>~~{

~~orangepi@orangepi~~:~~~# '''ls /dev/ttyS*'''~~printf("Hello World!\n");

~~/dev/ttyS1 '''/dev'''/'''ttyS3 /dev/ttyS7 /dev/ttyS9'''~~

~~<ol start="3" style="list-style-type~~: ~~decimal~~return 0;">~~<li>Then start testing the UART interface, and first use the RX and TX of the UART interface to be tested by DuPont</li></ol>~~

}|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then compile and run '''hello_world.c'''</li>{| class="wikitable" style="width:800px;"

|-

|}

</ol></li></ol><ol start="42" style="list-style-type: decimal;"><li>~~Use the '''serialTest.py''' program in Examples~~ Ubuntu Focal defaults to ~~test the loop function of the serial port. If you can see the printing below, it means that the serial communication is normal~~install Python3

<li>~~Test UART3~~Python3 specific version is shown below</li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3'''

~~root@orangepi:~/wiringOP-~~Python~~/examples# '''python3 serialTest~~3.8.~~py --device \'''~~10 (default, Nov 14 2022, 12:59:47)

~~'''"/dev/ttyS3"'''~~[GCC 9.4.0] on linux

~~Out: 0: -~~Type &gtquot; 0 ~~Out: 1: -~~help&gtquot; 1 ~~Out: 2: -~~, &gtquot; 2 ~~Out: 3: -~~copyright&gtquot; 3 ~~Out: 4:^C~~ ~~exit~~, "credits" or "license" for more information.

>>>

|}

</ol>

<li>~~Test UART7~~'''hello_world.py''' program in Python language</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.py'''

~~root~~print('Hello World!')|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The results of running '''hello_world.py''' are shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~~~/wiringOP-Python/examples#~~ $ '''python3 ~~serialTest~~hello_world.py ~~--device \~~'''

Hello World!|}</ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>Ubuntu Focal's compilation tool and operating environment without the installation of Java default<ol style="list-style-type: lower-alpha;"><li>You can use the following command to install ''~~&quot~~'openjdk-17'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''|}</~~dev~~ol><ol start="2" style="list-style-type: lower-alpha;"><li>After installation, you can check the version of Java</~~ttyS7&quot~~li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''java --version'''

~~Out:~~ openjdk 17.0: .2 2022-~~> 0~~01-18

~~Out: 1:~~ OpenJDK Runtime Environment (build 17.0.2+8-~~> 1~~Ubuntu-120.04)

~~Out:~~ OpenJDK 64-Bit Server VM (build 17.0.2+8-Ubuntu-120.04, mixed mode, sharing)|}</ol><ol start="3" style="list-style-type: lower-~~&gt~~alpha; 2"><li>Edit the '''hello_world.java''' of Jave version</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''

~~Out: 3: -> 3~~public class hello_world

~~Out: 4:^C~~{

~~exit~~:public static void main(String[] args)

~~<ol start="3" style="list-style-type~~: ~~lower-alpha;"><li>Test UART9</li></ol>~~{

~~root@orangepi~~:~~~/wiringOP-Python/examples# '''python3 serialTest~~:System.out.~~py --device \'''~~println("Hello World!");

~~'''"/dev/ttyS9"'''~~:}

~~Out~~}|}</ol><ol start="4" style="list-style-type: 0lower-alpha;"><li>Then compile and run '''hello_world.java'''</li>{| class="wikitable" style="width: 800px;" |-~~> 0~~| orangepi@orangepi:~$ '''javac hello_world.java'''

~~Out~~orangepi@orangepi: ~~1: -> 1~~~$ '''java hello_world'''

~~Out: 2:~~ Hello World!|}</ol></li></ol> 2jammy-system">

~~Out: 3: -> 3~~=== Ubuntu jammy system ===

~~Out~~<ol style="list-style-type: 4decimal;"><li>Ubuntu Jammy is installed with the GCC compilation tool chain by default, which can directly compile the C language program in the Linux system of the development board<ol style="list-style-type: lower-alpha;"><li>The version of the gcc is shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:^C~$ '''gcc --version'''

~~exit~~gcc (Ubuntu 11.2.0-19ubuntu1) '''11.2.0'''

~~== Hardware watch~~ This is free software; see the ~~door dog test ==~~source for copying conditions. There is NO

~~The WatchDog_test~~ warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Write the '''hello_world.c''' program ~~is pre~~ of c language</li>{| class="wikitable" style="width:800px;" |-~~installed in the Linux system released by Orange PI, which can be tested directly~~| orangepi@orangepi:~$ '''vim hello_world.c'''

~~The method of running the WatchDog_test program is shown below:~~ #include <stdio.h>

~~<ol style="list-style-type: lower-alpha;">~~

~~<li>The second parameter 10 indicates the counting time of the door. If there is no dog feeding in this time, the system will restart.</li>~~

~~<li>We can feed the dog by pressing any keys on the keyboard (except ESC). After the dog is fed, the program will print a line of Keep Alive to indicate that the dog is successful</li></ol>~~

~~orangepi@orangepi:~$ '''sudo watchdog_test 10'''~~int main(void)

~~open success~~{

~~options is 33152,identity is sunxi-wdt~~:printf("Hello World!\n");

~~put_usr return,if 0,success:0~~

~~The old reset time is~~: 16return 0;

~~return ENOTTY,if~~ }|}</ol><ol start="3" style="list-~~1,success~~style-type: lower-alpha;"><li>Then compile and run '''hello_world.c'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:0~$ '''gcc -o hello_world hello_world.c'''

~~return ENOTTY,if -1,success~~orangepi@orangepi:0~$ '''./hello_world'''

~~put_user return,if 0,success:0~~Hello World!|}</ol></li></ol>

~~put_usr return,if 0,success~~<ol start="2" style="list-style-type:0decimal;"><li>Ubuntu jammy is installed with Python3 by default<ol style="list-style-type: lower-alpha;"><li>Python3 specific version is shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3'''

~~keep alive~~Python '''3.10.4''' (main, Apr 2 2022, 09:04:19) [GCC 11.2.0] on linux

~~keep alive~~Type "help", "copyright", "credits" or "license" for more information.

~~keep alive~~>>>|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Edit '''hello_world.py''' program in Python language</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.py'''

print('Hello World!')|}</ol><~~span id~~ol start="~~check-the-serial~~3" style="list-~~number~~style-oftype: lower-~~the-rk3566-chip~~alpha;"><li>The results of running '''hello_world.py''' are shown below</~~span~~li>{| class="wikitable" style= ~~Check the serial number of the RK3566 chip ==~~"width:800px;" |-| orangepi@orangepi:~$ '''python3 hello_world.py'''

~~The commands of~~ Hello World!|}</ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>Ubuntu jammy defaults to compile tools and operating environments that are not installed in Java<ol style="list-style-type: lower-alpha;"><li>You can use the ~~RK3566 chip serial number are shown below. The serial number of each chip is different~~following command to install openjdk-18</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-18-jdk'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>After installation, so you can ~~use~~ check the ~~serial number to distinguish multiple development boards.~~version of Java</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''java --version'''

~~orangepi@orangepi:~$ '''cat_serial.sh'''~~openjdk 18-ea 2022-03-22

~~Serial : '''8fa18eaf489041f0'''~~OpenJDK Runtime Environment (build 18-ea+36-Ubuntu-1)

~~<ol start="3" style="list-~~installing~~style-~~the-balenaetcher-version-of~~type: lower-~~arm64~~alpha;"><~~/span~~li>~~== The method~~ Edit the '''hello_world.java''' of ~~downloading and installing~~ the ~~balenaEtcher~~ Jave version ~~of arm64 </li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java''' public class hello_world {

~~<ol style="list-style-type~~: ~~decimal;"><li>The download address of Balenaetcher ARM64 version is: <ol style="list-style-type: lower-alpha;"><li>The download address of the Deb installation package is shown below, and it needs to be installed to use</li></ol></li></ol>~~public static void main(String[] args)

~~https~~:~~//github.com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balena-etcher-electron_1.7.9+5945ab1f_arm64.deb~~{

~~<ol start="2" style="list-style-type~~: ~~lower-alpha~~:System.out.println("Hello World!");">~~<li>The download address of the Appimage version that does not need to be installed is shown below: </li></ol>~~

~~https~~:~~//github.com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balenaEtcher-1.7.9+5945ab1f-arm64.AppImage~~}

}|}<~~div~~ /ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then compile and run '''hello_world.java'''</li>{| class="~~figure~~wikitable" style="width:800px;">|-| orangepi@orangepi:~$ '''javac hello_world.java'''

~~[[File~~orangepi@orangepi:~~pi3b-img275.png|527x211px|IMG_256]]~~~$ '''java hello_world'''

~~</div>~~Hello World!~~<ol start="2" style="list-style-type: decimal;">~~|}~~<li>How to install and use the deb version of Balenaetcher: <ol style="list-style-type: lower-alpha;"><li>deb version of Balenaetcher installation commands as shown below: </li>~~</ol>

</li></ol>

~~orangepi@orangepi:~$ '''sudo apt install -y \'''~~== QT installation method ==

~~'''--fix-broken ./balena-etcher-electron_1.7.9+5945ab1f_arm64.deb'''~~# Use the following script to install QT5 and QT Creator

~~<ol start~~::{| class="2wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>After the deb version of Balenaetcher is installed, it can be opened in the Application</li></ol>~~|-| orangepi@orangepi:~$ '''install_qt.sh'''|}

<~~div~~ ol start="2" style="list-style-type: decimal;"><li>The QT version number will be automatically printed after installation<ol style="list-style-type: lower-alpha;"><li>Ubuntu20.04 comes with QT version '''5.12.8'''</li>{| class="~~figure~~wikitable">style="width:800px;" |-| orangepi@orangepi:~$ '''install_qt.sh'''

~~[[File:pi3b-img89~~.~~png|507x249px|IMG_256]]~~.....

~~</div><ol start="~~QMake version 3~~" style="list-style-type: lower-alpha;"><li>The interface after Balenaetcher is opened is shown below: </li></ol>~~.1

Using Qt version '''<~~div~~ span style="color:#FF0000">5.12.8''' in /usr/lib/aarch64-linux-gnu|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Ubuntu22.04 comes with QT version '''5.15.3'''</li>{| class="~~figure~~wikitable" style="width:800px;">|-| orangepi@orangepi:~$ '''install_qt.sh'''

~~[[File:pi3b-img276~~.~~png|429x263px|IMG_256]]~~.....

~~</div><ol start="~~QMake version 3~~" style="list-style-type: decimal;"><li>How to use the AppImage version of balenaEtcher: <ol style="list-style-type: lower-alpha;"><li>First add permissions to Balenaetcher</li></ol></li></ol>~~.1

Using Qt version '''5.15.3''' in /usr/lib/aarch64-linux-gnu|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Debian11 comes with QT version '''5.15.2'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~~~/Desktop~~$ '''~~chmod +x balenaEtcher-1.7.9+5945ab1f-arm64~~install_qt.~~AppImage~~sh'''

~~<ol start="2" style="list-style-type: lower-alpha;"><li>Then select the AppImage version balenaEtcher right -click the mouse, and then click Execute to open balenaEtcher</li></ol>~~......

~~[[File:pi3b-img277~~QMake version 3.~~png|145x118px]]~~1

Using Qt version '''5.15.2''' in /usr/lib/aarch64-~~installation~~linux-~~method-of-the-bt~~gnu|}</ol><ol start="4" style="list-~~panel~~style-~~linux~~type: lower-~~panel~~alpha;"><li>Debian12 comes with QT version '''5.15.8'''</~~span~~li>{| class="wikitable" style= ~~The installation method of the Bt~~"width:800px;" |-~~Panel Linux panel ==~~| orangepi@orangepi:~$ '''install_qt.sh'''

~~'''Bt-Panel Linux panel is a server management software that improves operation and maintenance efficiency~~. ~~It supports more than 100 server management functions such as one -click LAMP/LNMP/cluster/monitoring/website/FTP/database/Java (excerpted from the [https://www~~.bt.~~cn/new/index~~.~~html official website of the Bt-Panel])'''~~..

~~# First of all, the size of the'''/tmp''' space is needed~~QMake version 3. ~~After setting, you need to '''restart the Linux system of the development board''', and the command is shown below:~~ 1

~~orangepi@orangepi~~Using Qt version '''5.15.8'''~~sudo sed~~ in /usr/lib/aarch64-linux-~~i 's~~gnu|}</ol></~~nosuid~~li></~~&amp~~ol><ol start="3" style="list-style-type: decimal;~~,size=2G/~~"><li>Then you can see the QT Creator launch icon in ''' ~~/etc/fstab~~Applications'''</li>

~~orangepi@orangepi~~[[File:~~~$ '''sudo reboot'''~~pi3b-img327.png]]

~~<ol start~~QT Creator can also be opened using the following command{| class="2wikitable" style="~~list~~width:800px;" |-| orangepi@orangepi:~$ '''qtcreator'''|}{| class="wikitable" style="background-~~type~~color: ~~decimal~~#ffffdc;width:800px;">|-| <libig>~~After restarting, you can see that~~ '''During the ~~size~~ startup of QT and QT applications, if thefollowing error is displayed, ignore it. This error has no impact on application running.'''~~/tmp''' space has become 2G.</li></ol>~~

~~orangepi@orangepi:~$ '''df -h | grep "/tmp"'''~~

~~tmpfs 2.0G 12K~~ '''~~2.0G~~libGL error: failed to create dri screen''' ~~1% /tmp~~

~~<ol start="3" style="list-style-type~~'''libGL error: ~~decimal;"><li>Then enter the following command in the Linux system~~ failed to ~~start the installation of the Bt-Panel</li></ol>~~load driver: rockchip'''

~~orangepi@orangepi:~$~~ '''~~sudo install_bt_panel.sh~~libGL error: failed to create dri screen'''

'''libGL error: failed to load driver: rockchip'''</big>

|}

</ol>

<li>~~Then the pagoda installation program reminds whether to install the '''Bt-Panel''' to the'''/www''' folder, and enter y at this time~~The interface after QT Creator is opened is as follows</li~~></ol~~>

~~+----------------------------------------------------------------~~[[File:pi3b-img328.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>The QT Creator version is shown below<ol style="list-style-type: lower-alpha;"><li>The default version of QT Creator in '''Ubuntu20.04''' is as follows</li>

~~| Bt~~[[File:pi3b-~~WebPanel FOR CentOS~~img329.png]]</~~Ubuntu~~ol><ol start="2" style="list-style-type: lower-alpha;"><li>The default version of QT Creator in '''Ubuntu22.04''' is as follows</~~Debian~~li>

~~+------------------------------------------------------------------~~[[File:pi3b-img330.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The default version of QT Creator in '''Debian11''' is as follows</li>

~~| Copyright © 2015~~[[File:pi3b-~~2099 BT~~img331.png]]</ol><ol start="4" style="list-~~SOFT(http~~style-type:lower-alpha;"><li>The default version of QT Creator in '''Debian12''' is as follows</~~/www.bt.cn) All rights reserved.~~li>

~~+---------------------------------------------------------------~~[[File:pi3b-img332.png]]</ol></li></ol><ol start="6" style="list-style-type: decimal;"><li>Then set QT<ol style="list-style-type: lower-alpha;"><li>First open '''Help'''->'''About Plugins...'''</li>

~~| The WebPanel URL will be http~~[[File:pi3b-img333.png]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then remove the check box for '''ClangCodeModel'''</~~SERVER_IP:8888 when installed.~~li>

~~+----------------------------------------------------------------~~[[File:pi3b-img334.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>'''Restart QT Creator after the Settings are complete'''</li><li>Then make sure that QT Creator uses the GCC compiler, if the default is Clang, change it to GCC</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Debian12 Please skip this step.'''</big>|}

~~Do you want to install Bt~~[[File:pi3b-~~Panel to the /www directory now?(y/n): '''y'''~~img335.png]]

[[File:pi3b-img336.png]]</ol ~~start="5" style="list-style-type: decimal;"~~><li>Then you have 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 34 minutes. There may be some differences according to the difference in network speed</li></ol> ~~[[File:pi3b-img278.png|576x233px]]~~ <ol start="67" style="list-style-type: decimal;"><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 in the corresponding position to log in to the Bt-Panel ~~[[File:pi3b-img279.png|575x281px]]</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~~ You can ~~choose "I have agreed and read" User Agreement ", and~~ then ~~click" Enter the panel " You can enter the Bt-Panel~~open a sample code</li>~~</ol>~~ ~~[[File:pi3b-img280.png|575x317px]]~~

[[File:pi3b-img337.png]]

</ol>

<li>~~After entering~~ Clicking on the ~~Bt-Panel, you~~ example code will ~~first prompt that you need to bind~~ automatically open the ~~account of the Bt-Panel official website. If you do n’t have an account~~corresponding instruction document, you can ~~go to~~ carefully read the ~~pagoda's official website ('''https://www.bt.cn''') to register one.~~instructions</li>~~</ol>~~ ~~[[File:pi3b-img281.png|576x300px]]~~

[[File:pi3b-img338.png]]

</ol>

<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 state, CPU usage, memory usage and storage space usageThen click '''Configure Project'''</li>~~</ol>~~ ~~[[File:pi3b-img282.png|575x306px]]~~

[[File:pi3b-img339.png]]

</ol>

<li>~~More functions of~~ Then click the ~~Bt-Panel can refer~~ green triangle in the lower left corner to compile and run the ~~following information to explore by yourself~~sample code</li~~></ol~~>

~~Manual:~~ [~~http~~[File:pi3b-img340.png]]</~~/docs.bt.cn '''http~~ol><ol start="11" style="list-style-type:decimal;"><li>After waiting for a period of time, the interface shown in the following figure will pop up, which indicates that QT can compile and run normally</~~/docs.bt.cn''']~~li>

~~Forum address:~~ [~~https~~[File:~~//www~~pi3b-img341.~~bt.cn~~png]]</~~bbs '''https~~ol><ol start="12" style="list-style-type:decimal;"><li>Reference documents</~~/www.bt.cn/bbs''']~~li>{| class="wikitable" style="width:800px;" |-| ~~GitHub Link:~~ '''https://~~github~~wiki.~~com/aaPanel~~qt.io/~~BaoTa~~Install_Qt_5_on_Ubuntu'''

~~<~~'''https:/~~span>== Set the Chinese environment and install Chinese input method ==~~/download.qt.io/archive/qtcreator'''

'''~~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~~https://download.qt.io/archive/qt'''|}</ol>

~~=== Debian system installation method~~ =ROS Installation Method ==

<~~ol style~~span id="~~list~~how-~~style~~to-~~type: decimal;"><li>First set the default '''locale''' as Chinese<ol style="list~~install-ros-1-noetic-~~style~~on-~~type: lower~~ubuntu-~~alpha;~~20.04">~~<li>Enter the command below to start configured '''locale'''</li~~></olspan>~~</li></ol>~~=== How to install ROS 1 Noetic on Ubuntu 20.04 ===

~~orangepi@orangepi:~$~~ # The current active version of ROS 1 is as follows, the recommended version is '''~~sudo dpkg-reconfigure locales~~Noetic Ninjemys'''

~~<ol start="2" style="list-style-type~~: ~~lower~~:[[File:pi3b-~~alpha;"><li>Then select '''zh_CN~~img342.UTF-8 UTF-8''' in the pop-up interface (to move up and down through the upper and lower direction buttons on the keyboard, select it through the space key, and finally move the cursor to '''<OK>''' through the TAB key, then press the ENTER key )</li></ol>png|800px]]

::[[File:pi3b-~~img283~~img343.png|~~575x296px~~800px]]

~~<ol start~~::{| class="3wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Then set the default~~ |-| [http://docs.ros.org/ '''~~locale''' as '''zh_CN~~http://docs.ros.~~UTF-8~~org'''~~</li></ol>~~]

~~[[File~~'''https:~~pi3b-img284~~//wiki.~~png~~ros.org/Distributions'''|~~575x160px]]~~}

<ol start="42" style="list-style-type: ~~lower~~decimal;"><li>The official installation document link of ROS 1 '''Noetic Ninjemys''' is as follows:</li>{| class="wikitable" style="width:800px;" |-~~alpha~~| [http://wiki.ros.org/noetic/Installation/Ubuntu '''http://wiki.ros.org/noetic/Installation/Ubuntu''']|}</ol><ol start="3" style="list-style-type: decimal;"><li>~~After exiting the interface,~~ In the official installation document of ROS '''~~locale~~Noetic Ninjemys''' ~~settings will be started~~, Ubuntu recommends using Ubuntu20. ~~The output displayed~~ 04, so please make sure that the system used by the ~~command line~~ development board is ~~shown below~~'''Ubuntu20.04 desktop system</lispan>'''</olli>{| class="wikitable" style="width:800px;" |-| http://wiki.ros.org/noetic/Installation|}

[[File:pi3b-img344.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then use the script below to install ros1</li>{| class="wikitable" style="width:800px;" |-| orangepi@~~orangepi~~orangepi3b:~$ '''~~sudo dpkg~~install_ros.sh ros1'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>Before using the ROS tool, you first need to initialize rosdep, and then you can quickly install some system dependencies and some core components in ROS when compiling the source code</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-~~reconfigure locales~~| <big>'''Note that running the following command needs to ensure that the development board can access github normally, otherwise an error will be reported due to network problems.'''

~~Generating locales (this might take a while)...~~

~~en_US~~'''The install_ros.~~UTF-8~~sh script will try to modify /etc/hosts and automatically run the following commands.However, this method cannot guarantee normal access to github every time.If the following error is displayed after installing ros1 in install_ros. ~~done~~sh, please find other ways to allow the Linux system of the development board to access github normally, and then manually run the following Order.'''

~~zh_CN.UTF-8... done~~

~~Generation complete~~'''https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml'''

~~<ol start="2" style="list-style-type: decimal;"><li>Then open~~ '''~~Input Method~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml'''~~</li></ol>~~

~~[[File~~'''ERROR:~~pi3b-img285.png|575x361px]]~~error loading sources list:'''

:'''The read operation timed out'''<~~ol start~~/big>|}{| class="3wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then select~~ |-| orangepi@orangepi:~$ '''OKsource /opt/ros/noetic/setup.bash'''~~</li></ol>~~

~~[[File~~orangepi@orangepi:~~pi3b-img286.png|295x212px]]~~~$ '''sudo rosdep init'''

~~<ol start="4" style="~~Wrote /etc/ros/rosdep/sources.list.d/20-~~style-type: decimal;"><li>Then select '''Yes'''</li></ol>~~default.list

~~[[File~~Recommended:~~pi3b-img287.png|303x192px]]~~please run

~~<ol start="5" style="list-style-type: decimal;">~~

~~<li>Then select '''fcitx'''</li></ol>~~

~~[[File~~:~~pi3b-img288.png|307x220px]]~~:rosdep update

~~<ol start="6" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>Then select~~ ~$ '''OKrosdep update'''~~</li></ol>~~

~~[[File:pi3b-img289~~reading in sources list data from /etc/ros/rosdep/sources.~~png|305x216px]]~~list.d

~~<ol start="7" style="list-style-type~~Hit https: ~~decimal;"><li>'''Then restart the Linux system to make the configuration effective'''<~~/~~p><~~/~~li><li>Then open '''Fcitx configuration'''<~~raw.githubusercontent.com/~~p><~~ros/~~li><~~rosdistro/~~ol>~~master/rosdep/osx-homebrew.yaml

~~[[File~~Hit https:~~pi3b-img290~~//raw.~~png|575x376px]]~~githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml

~~<ol start="9" style="list-style-type~~Hit https: ~~decimal;"><li>Then click the + of the position shown in the figure below<~~/~~li><~~/~~ol>~~raw.githubusercontent.com/ros/rosdistro/master/rosdep/python.yaml

~~[[File~~Hit https:~~pi3b-img291~~//raw.~~png|280x187px]]~~githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml

~~<ol start="10" style="list-style-type~~Hit https: ~~decimal;"><li>Then search '''Google Pinyin''' and click '''OK'''<~~/~~li><~~/~~ol>~~raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml

~~<div class="figure">~~Query rosdistro index https://raw.githubusercontent.com/ros/rosdistro/master/index-v4.yaml

~~[[File:pi3b~~Skip end-~~img292.png|291x196px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~of-~~10.jpg未标题-10]]~~life distro "ardent"

~~</div><ol start="11" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "bouncy"">~~<li>Then put '''Google Pinyin''' to the front</li></ol>~~

~~[[File:pi3b~~Skip end-~~img293.png|299x202px]]~~of-life distro "crystal"

~~[[File:pi3b~~Skip end-~~img294.png|300x202px]]~~of-life distro "dashing"

~~<ol start="12" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "eloquent"">~~<li>Then open the '''Geany''' editor to test the Chinese input method</li></ol>~~

~~[[File:pi3b-img295.png|349x212px]]~~Add distro "foxy"

~~<ol start="13" style="list-style-type: decimal~~Add distro "galactic"">~~<li>The Chinese input method test is shown below</li></ol>~~

~~[[File:pi3b~~Skip end-~~img296.png|575x325px]]~~of-life distro "groovy"

~~<ol start="14" style="list-style-type: decimal~~Add distro "humble"">~~<li>You can switch the Chinese and English input method through the '''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></ol>~~

~~orangepi@orangepi:~$ '''sudo vim /etc/default/locale'''~~Skip end-of-life distro "hydro"

~~# File generated by update~~Skip end-~~locale~~of-life distro "indigo"

~~LC_MESSAGES='''zh_CN.UTF~~Skip end-~~8'''~~of-life distro "jade"

~~LANG='''zh_CN.UTF~~Skip end-~~8'''~~of-life distro "kinetic"

~~LANGUAGE='''zh_CN.UTF~~Skip end-~~8'''~~of-life distro "lunar"

~~<ol start="16" style="list-style-type: decimal~~Add distro "melodic"">~~<li>Then '''restart the system''' to see the system displayed as Chinese</li></ol>~~

~~[[File:pi3b-img297.png|576x356px]]~~Add distro "noetic"

~~=== The installation method of Ubuntu 20.04 system ===~~Add distro "rolling"

~~# First~~ updated cache in /home/orangepi/.ros/rosdep/sources.cache|}</ol><ol start="6" style="list-style-type: decimal;"><li>Then open a command line terminal window on the desktop, and then use the test_ros.sh script to start a small turtle routine to test whether ROS can be used normally</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~Language Support~~test_ros.sh'''|}<li>After running the '''test_ros.sh''' script, a little turtle as shown in the figure below will pop up</li>

~~[[File:pi3b-img298.png|575x351px]]~~<div class="figure">

~~<ol start="2" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Then find '''Chinese (China)''' option</li></ol>~~img345.png]]

~~[[File~~</div></ol><ol start="8" style="list-style-type:~~pi3b-img299.png|318x311px]]~~decimal;"><li>Then please keep the terminal window just opened at the top</li>

<~~ol start~~div class="3figure" ~~style="list-style-type: decimal;"><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 is shown below: </li></ol~~>

[[File:pi3b-~~img300~~img346.png~~|324x320px~~]]

~~'''Note that~~ </div></ol><ol start="9" style="list-style-type: decimal;"><li>At this ~~step is not easy~~ time, press the direction keys on the keyboard to control the little turtle to ~~drag~~move up, down, left, ~~please try more patiently.'''~~and right</li>

[[File:pi3b-img347.png]]</ol ~~start~~>~~<li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system~~</~~li></ol~~span>

~~[[File:pi3b-img301~~=== How to install ROS 2 Galactic on Ubuntu 20.~~png|321x316px]]~~04 ===

~~<ol start="5" style="list-style-type: decimal;"><li>Then set~~ # The current active version of ROS 2 is as follows, the recommended version is '''~~Keyboard input method system~~Galactic Geochelone''' ~~to '''fcitx'''</li></ol>~~

::[[File:pi3b-~~img302~~img348.png~~|327x320px~~]]

~~<ol start="6" style="list-style-type~~: ~~decimal;"><li>'''hen restart the Linux system to make the configuration effective'''</li><li>After re~~ :[[File:pi3b-~~entering the system, please do '''not ask me again''' at the interface below, and then determine whether the standard folder should be updated as Chinese based on your preference~~img349.~~</li></ol>~~png]]

::{| class="wikitable" style="width:800px;" |-| [~~[File~~http://docs.ros.org/ '''http:~~pi3b-img303~~//docs.ros.~~png|303x247px]~~org''']

~~<ol start="8" style="list-style-type~~'''http: ~~decimal;"><li>Then you can see that the desktop is displayed as Chinese<~~/~~li><~~/~~ol>~~docs.ros.org/en/galactic/Releases.html'''|}

~~[[File~~<ol start="2" style="list-style-type: decimal;"><li>The link to the official ROS 2 '''Galactic Geochelone''' installation documentation is as follows:</li>{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img304~~| '''docs.~~png|575x383px]]~~ros.org/en/galactic/Installation.html'''

'''http://docs.ros.org/en/galactic/Installation/Ubuntu-Install-Debians.html'''|}</ol><ol start="93" style="list-style-type: decimal;"><li>~~Then we can open~~ It is recommended to use Ubuntu20.04 in the official installation document of ROS 2 '''~~Geany~~Galactic Geochelone''' ~~to test Chinese input method~~ , ~~and~~ so please ensure that the ~~way~~ system used by the development board is '''Ubuntu20.04 desktop version'''. There are several ways to install ROS 2. The following shows how to ~~open is shown in~~ install ROS 2 '''Galactic Geochelone''' using '''Debian packages'''</li><li>Use the ~~figure below~~'''install_ros.sh''' script to install ros2</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_ros.sh ros2'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>The '''install_ros.sh''' script will automatically run the '''ros2 -h''' command after installing ros2. If you can see the following print, it means that the ros2 installation is complete</li>{| class="wikitable" style="width:800px;" |-| usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...

~~[[File:pi3b-img305.png|576x292px]]~~

~~<ol start="10" style="list-style-type: decimal;"><li>After opening '''Geany''', the default~~ ros2 is an ~~English input method~~extensible command-line tool for ROS 2. ~~We can switch into Chinese input method through the '''Ctrl+Space''' shortcut keys, and then we can enter Chinese</li></ol>~~

~~[[File:pi3b-img306.png|575x308px]]~~

~~=== The installation method of ubuntu 22.04 system ===~~optional arguments:

~~# First open '''Language Support'''~~:-h, --help show this help message and exit

~~[[File:pi3b-img298.png|575x351px]]~~

~~<ol start="2" style="list-style-type~~Commands: ~~decimal;"><li>Then find '''Chinese (China)''' option</li></ol>~~

~~[[File~~:~~pi3b~~action Various action related sub-~~img307.png|335x326px]]~~commands

~~<ol start="3" style="list-style~~:bag Various rosbag related sub-~~type: decimal;"><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: </li></ol>~~commands

~~[[File~~:~~pi3b~~component Various component related sub-~~img308.png|337x331px]]~~commands

~~'''Note that this step is not easy to drag, please try more patiently.'''~~:daemon Various daemon related sub-commands

~~<ol start="4" style="list-style-type~~: ~~decimal;"><li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system</li></ol>~~doctor Check ROS setup and other potential issues

~~[[File~~:~~pi3b-img309.png|336x330px]]~~interface Show information about ROS interfaces

~~<ol start="5" style="list-style-type~~: ~~decimal;"><li>'''Then restart the Linux system to make the configuration effective'''</li>~~<li>After re -entering the system, please '''do not ask me again''' at the interface below, and then determine whether the standard folder should be updated as Chinese based on your preference</li></ol>launch Run a launch file

~~[[File~~:~~pi3b~~lifecycle Various lifecycle related sub-~~img303.png|303x247px]]~~commands

~~<ol start="7" style="list~~:multicast Various multicast related sub-~~style-type: decimal;"><li>Then you can see that the desktop is displayed as Chinese</li></ol>~~commands

~~[[File~~:~~pi3b~~node Various node related sub-~~img304.png|575x383px]]~~commands

~~<ol start="8" style="list~~:param Various param related sub-~~style-type: decimal;"><li>Then open the Fcitx5 configuration program</li></ol>~~commands

~~[[File~~:~~pi3b~~pkg Various package related sub-~~img310.png|575x349px]]~~commands

~~<ol start="9" style="list-style-type~~: ~~decimal;"><li>Then choose to use Pinyin input method</li></ol>~~run Run a package specific executable

~~<div class="figure">~~:security Various security related sub-commands

~~[[File~~:~~pi3b~~service Various service related sub-~~img311.png|338x267px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-11.jpg未标题-11]]~~commands

~~</div><ol start="10" style="list~~:topic Various topic related sub-~~style-type: decimal;"><li>The interface after the selection is shown below, then click OK</li></ol>~~commands

~~[[File~~:~~pi3b-img312.png|366x290px]]~~wtf Use `wtf` as alias to `doctor`

~~<ol start="11" style="list-style-type: decimal;">~~

~~<li>Then we can open the '''Geany''' to test Chinese input method, and the way to open is shown in the figure below</li></ol>~~

~~[[File~~:~~pi3b~~Call `ros2 <command> -~~img305~~h` for more detailed usage.~~png~~|~~576x292px]]~~}</ol><ol start="6" style="list-style-type: decimal;"><li>Then you can use the '''test_ros.sh''' script to test whether ROS 2 is installed successfully. If you can see the following print, it means that ROS 2 can run normally</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi3b:~$ '''test_ros.sh'''

~~<ol start="12" style="list-style-type~~[INFO] [1671174101.200091527] [talker]: Publishing: ~~decimal;"><li>After opening '''Geany''', it is still an English input method by default. We can switch into Chinese input methods through the '''Ctrl+Space'~~'Hello World: 1' ~~shortcut keys, and then we can enter Chinese</li></ol>~~

[INFO] [~~File:pi3b-img313~~1671174101.~~png|576x408px~~235661048] [listener]: I heard: [Hello World: 1]

~~== How to remotely log in to the Linux system desktop method ==~~[INFO] [1671174102.199572327] [talker]: Publishing: 'Hello World: 2'

~~'''Ubuntu Gnome Wayland image does not support Nomachine and VNCs introduced here to remotely log in to the desktop~~[INFO] [1671174102.~~'''~~204196299] [listener]: I heard: [Hello World: 2]

~~=== Use nomachine remote login ===~~[INFO] [1671174103.199580322] [talker]: Publishing: 'Hello World: 3'

[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]|}</ol><ol start="7" style="list-style-type: decimal;"><li>Run the following command to open rviz2</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''Make sure the Ubuntu or Debian system installed on the development board is a desktop version. In addition, nomachine also provides detailed documents. It is strongly recommended to read this document to be familiar with the use of nomachinesource /opt/ros/galactic/setup. ~~The document links are shown below:~~ bash'''

orangepi@orangepi:~$ '''~~https://knowledgebase.nomachine.com/DT10R00166~~ros2 run rviz2 rviz2'''|}

'''Nomachine supports Windows, Mac, Linux, iOS, and Android platforms, so we can remotely log in to control Orange PI development boards through Nomachine on multiple devices. The following demonstrates the Linux system desktop of the Orange PI development board through Nomachine in Windows. For installation methods for other platforms, please refer to the official documentation of Nomachine.'''<div class="figure">

'''Before operation, please ensure that the Windwos computer and the development board are in the same local area network, and can log in to the Ubuntu or Debian system that can log in to the development board normally[[File:pi3b-img350.~~'''~~png]]

</div></ol ><ol start="8" style="list-style-type: decimal;"><li>~~First download~~ For the ~~nomachine software Linux '''ARM64''' DEB version~~ usage of ~~the installation package~~ROS, ~~and then install it in~~ please refer to the ~~Linux system~~ documentation of ~~the development board~~ROS 2</pli>~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Since RK3566 is a SOC of the ARMV8 architecture, the system we use is Ubuntu or Debian, so you need to download~~ |-| '''~~NoMachine for ARM ARMv8 DEB~~http://docs.ros.org/en/galactic/Tutorials.html''' ~~installation package here. The download link is shown below: </li>~~|}</ol><~~/li~~span id="how-to-install-ros-2-humble-on-ubuntu-22.04"></olspan>

~~'''Note that this download link may change, please recognize the DEB package of the ARMV8/ARM64 version~~=== How to install ROS 2 Humble on Ubuntu 22.~~'''~~04 ===

~~[https://www.nomachine.com/download/download&id=112&s=ARM~~ # Use the '''~~https://downloads.nomachine~~install_ros.~~com/download/?id=118&distro=ARM~~sh''']script to install ros2

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-~~img314~~| orangepi@orangepi:~$ '''install_ros.~~png~~sh ros2'''|~~575x227px]]~~}

<ol start="2" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~In addition, you can also download the installation package to~~ The '''~~NoMachine~~install_ros.sh''' in script will automatically run the '''~~official tools~~ros2 -h'''command after installing ros2.If you can see the following print, it means that the ros2 installation is complete</li~~></ol~~>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img315.png~~|~~66x102px]~~usage: ros2 [-h]Call `ros2 <command> -h` for more detailed usage. ...

~~<blockquote>First enter the '''remote login software-Nomachine''' folder~~

~~</blockquote>~~

~~[[File:pi3b-img316.png|271x43px]]~~

~~<blockquote>Then download the ARM64 version of the DEB installation package</blockquote>[[File:pi3b~~ros2 is an extensible command-~~img317~~line tool for ROS 2.~~png|180x109px]]~~

~~<ol start="3" style="list-style-type: lower-alpha;">~~

~~<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 of the development board</li></ol>~~

~~orangepi@orangepi~~optional arguments:~~~$ '''sudo dpkg -i nomachine_x.x.x_x_arm64_arm64.deb'''~~

~~<ol start="2" style="list~~:-~~style~~h, -~~type: decimal;"><li>Then download the nomachine software Windows version of the installation package, the download address is shown below</li></ol>~~-help show this help message and exit

~~'''Note that this download link may change.'''~~

~~'''https~~Commands:~~//downloads.nomachine.com/download/?id=9'''~~

~~[[File~~:~~pi3b~~action Various action related sub-~~img318.png|575x163px]]~~commands

~~<ol start="3" style="list~~:bag Various rosbag related sub-~~style-type: decimal;"><li>Then install nomachine in Windows. '''Please restart the computer after installation'''</li><li>Then open '''NoMachine''' in Window</li></ol>~~commands

~~[[File~~:~~pi3b~~component Various component related sub-~~img319.png|76x66px]]~~commands

~~<ol start="5" style="list~~:daemon Various daemon related sub-~~style-type: decimal;">~~<li>After Nomachine starts, 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. Start log in to the Linux system desktop of the development board</li></ol>commands

~~[[File~~:~~pi3b-img320.png|321x92px]]~~doctor Check ROS setup and other potential issues

~~<ol start="6" style="list-style-type~~: ~~decimal;"><li>Then click '''OK'''</li></ol>~~interface Show information about ROS interfaces

~~[[File~~:~~pi3b-img321.png|402x275px]]~~launch Run a launch file

~~<ol start="7" style="list~~:lifecycle Various lifecycle related sub-~~style-type: decimal;"><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</li></ol>~~commands

~~<div class="figure">~~:multicast Various multicast related sub-commands

~~[[File~~:~~pi3b~~node Various node related sub-~~img322.png|303x204px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-12.jpg未标题-12]]~~commands

~~</div><ol start="8" style="list-style-type: decimal;"><li>Then click OK in the next interface</li><li>Finally, you can see the desktop of the development board Linux system[[File~~:~~pi3b~~param Various param related sub-~~img323.png|411x246px]]</li></ol>~~commands

~~=== Use VNC remote login ===~~commands

'''Before operation, please ensure that the Windwos computer and the development board are in the same local area network, and you can log in to the Ubuntu or Debian system of the development board normally.''':run Run a package specific executable

~~'''Ubuntu 20.04 tests many problems with VNC, please do not use this method.'''~~:security Various security related sub-commands

~~# First run the '''set_vnc.sh''' script settings, and '''remember to add Sudo permissions'''~~:service Various service related sub-commands

~~orangepi@orangepi~~:~~~$ '''sudo set_vnc.sh'''~~topic Various topic related sub-commands

~~You will require a password~~ :wtf Use `wtf` as alias to ~~access your desktops.~~`doctor`

~~Password: '''#Set the VNC password here, 8 -bit characters'''~~

~~Verify~~: Call `ros2 <command> -h` for more detailed usage.|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then you can use the '''~~#Set the VNC password here, 8 -bit characters~~test_ros.sh'''script to test whether ROS 2 is installed successfully. If you can see the following print, it means that ROS 2 can run normally</li>

~~Would you like to enter a view~~{| class="wikitable" style="width:800px;" |-~~only password (y/n)?~~ | orangepi@orangepi3b:~$ '''ntest_ros.sh'''

~~xauth~~[INFO] [1671174101.200091527] [talker]: Publishing: 'Hello World: ~~file /root/.Xauthority does not exist~~1'

~~New 'X' desktop is orangepi3b~~[INFO] [1671174101.235661048] [listener]: I heard: [Hello World:1]

~~Creating default startup script /root/~~[INFO] [1671174102.~~vnc/xstartup~~199572327] [talker]: Publishing: 'Hello World: 2'

~~Starting applications specified in /root/~~[INFO] [1671174102.~~vnc/xstartup~~204196299] [listener]: I heard: [Hello World: 2]

~~Log file is /root/~~[INFO] [1671174103.~~vnc/orangepi3b~~199580322] [talker]:~~1.log~~Publishing: 'Hello World: 3'

~~Killing Xtightvnc process ID 3047~~[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]|}</ol><ol start="4" style="list-style-type: decimal;"><li>Run the following command to open rviz2</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''source /opt/ros/humble/setup.bash'''

~~New~~ orangepi@orangepi:~$ '''ros2 run rviz2 rviz2''X' ~~desktop is orangepi3b:1~~ ~~Starting applications specified in /root/.vnc/xstartup~~ ~~Log file is /root/.vnc/orangepi3b:1.log~~ ~~<ol start="2" style="list-style-type: decimal;"><li>The steps of using MobaxTerm software to connect the development board Linux system desktop are shown below: <ol style="list-style-type: lower-alpha;"><li>First click Session, then select VNC, then fill in the IP address and port of the development board, and finally click OK to confirm</li></ol></li></ol>~~|}

[[File:pi3b-~~img324~~img351.png~~|490x349px|图片1208~~]]

</div></ol><ol start="25" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then enter the password of the previously set VNC~~Reference documents</li><{| class="wikitable" style="width:800px;" |-| '''http://docs.ros.org/en/humble/~~ol>~~index.html'''

[~~[File~~http:~~pi3b~~//docs.ros.org/en/galactic/Tutorials.html '''http://docs.ros.org/en/humble/Installation/Ubuntu-Install-~~img325~~Debians.~~png~~html''']|~~274x131px]]~~}</ol>

~~<ol start~~=~~"3" style~~=~~"list-style-type: lower-alpha;"><li>The interface after the login is shown as shown in the figure below, and then the desktop of the Linux system can be remotely operated[[File:pi3b-img326.png|405x293px]]</li></ol>~~How to install kernel header files ==

~~<~~OPi comes with the deb package of the kernel header file by default, and the storage location is '''/~~span>== Some programming language tests supported by Linux system ==~~opt/'''

~~=== Debian Bullseye system ===~~headers*'''

~~<ol style="list-style~~/opt/linux-~~type: decimal;"><li>Debian Bullseye is equipped with a gcc compilation tool chain by default, which can directly compile the C language program in the Linux system of the development board<ol style="list~~headers-~~style~~legacy-~~type: lower~~rockchip-~~alpha;">~~rk356x_x.x.x_arm64.deb~~<li>The version of the gcc is shown below</li></ol></li></ol>~~|}

<ol start="2" style="list-style-type: decimal;"><li>Use the following command to install the deb package of the kernel header file</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The name of the kernel header file deb package needs to be replaced with the actual name, please do not copy it.'''</big>|}{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~gcc~~ sudo dpkg -i /opt/linux-headers-legacy-rockchip-~~version~~rk356x_1.x.x_arm64.deb'''|}~~gcc (Debian 10.2.1~~</ol><ol start="3" style="list-style-type: decimal;"><li>After installation, you can see the folder where the kernel header files are located under '''/usr/src'''</li>{| class="wikitable" style="width:800px;" |-~~6) 10.2.1 20210110~~| orangepi@orangepi:~$ '''ls /usr/src'''

~~Copyright (C) 2020 Free Software Foundation~~linux-headers-5.10.160-rockchip-rk356x|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then you can write a hello kernel module to test the kernel header file<ol style="list-style-type: lower-alpha;"><li>First write the code of the hello kernel module, ~~Inc~~as follows:</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello.c'''

~~This is free software~~#include < ~~see the source for copying conditions~~linux/init. ~~There is NO~~h>

~~warranty~~#include < ~~not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE~~linux/module.h>

~~<ol start="2" style="list-style-type: lower-alpha;">~~

~~<li>Write C language of '''Hello_world.c''' program</li></ol>~~

~~orangepi@orangepi:~$ '''vim hello_world.c'''~~static int hello_init(void)

~~#include <stdio.h>~~ ~~int main(void)~~{

{:printk("Hello Orange Pi -- init\n");

~~printf("Hello World!\n");~~

:return 0;

}

~~<ol start="3" style="list-style-type: lower-alpha;"><li>Then compile and run '''hello_world.c'''</li></ol>~~static void hello_exit(void)

~~orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''~~{

~~orangepi@orangepi~~:~~~$ '''./hello_world'''~~printk("Hello Orange Pi -- exit\n");

~~Hello World!~~

~~<ol start="2" style="list-style-type~~: ~~decimal~~return;">~~<li>Debian BullSeye Default with Python3<ol style="list-style-type: lower-alpha;"><li>The specific version of Python is shown below</li></ol></li></ol>~~

~~orangepi@orangepi:~$ '''python3'''~~}

~~'''Python 3.9.2''' (default, Feb 28 2021, 17:03:44)~~

~~[GCC 10.2.1 20210110] on linux~~module_init(hello_init);

~~Type &quot~~module_exit(hello_exit);~~help", "copyright", "credits" or "license" for more information.~~

~~>>>~~

MODULE_LICENSE("GPL");

|}

</ol>

<li>~~'''hello_world.py''' program in Python language~~Then write the Makefile for compiling the hello kernel module, as follows:</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim ~~hello_world.py~~Makefile''' ifneq ($(KERNELRELEASE),)

~~print('Hello World!')~~obj-m:=hello.o

~~<ol start="3" style="list-style-type: lower-alpha;"><li>The results of running '''hello_world.py''' are shown below</li></ol>~~else

~~orangepi@orangepi~~KDIR :~=/lib/modules/$ ~~'''python3 hello_world.py'''~~(shell uname -r)/build

~~Hello World!~~PWD :=$(shell pwd)

~~<ol start="3" style="list-style-type~~all: ~~decimal;"><li>Debian Bullseye's compilation tool and operating environment that is not installed in Java by default<ol style="list-style-type: lower-alpha;"><li>You can use the following command to install OpenJDK. The latest version in Debian Bullseye is openjdk-17</li></ol></li></ol>~~

~~orangepi@orangepi~~:~make -C $ ~~'''sudo apt install -y openjdk-17-jdk'''~~(KDIR) M=$(PWD) modules

~~<ol start="2" style="list-style-type~~clean: ~~lower-alpha;"><li>After installation, you can check the version of Java</li></ol>~~

~~orangepi@orangepi~~:~~~$ '''java~~ rm -~~-version'''~~f *.ko *.o *.mod.o *.mod *.symvers *.cmd *.mod.c *.order

endif

|}

</ol>

<li>~~Edit~~ Then use the make command to compile the hello kernel module. The output of the compilation process is as follows:</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~hello_world~~If there is a problem with compiling the code you copied here, please go to the official tool to download the source code and upload it to the Linux system of the development board for testing.~~java~~''' ~~of the Jave version</li>~~</olbig>

[[File:pi3b-img352.png|center]]|}{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~vim hello_world.java~~make'''

~~public class hello_world~~make -C /lib/modules/5.10.160-rockchip-35xx/build M=/home/orangepi modules

{make[1]: Entering directory '/usr/src/linux-headers-5.10.160-rockchip-rk35xx'

~~public static void main(String~~:CC [M] ~~args)~~/home/orangepi/hello.o

{:MODPOST /home/orangepi/Module.symvers

~~System~~:CC [M] /home/orangepi/hello.~~out~~mod.~~println("Hello World!");~~o

} }:LD [M] /home/orangepi/hello.ko

make[1]: Leaving directory '/usr/src/linux-headers-5.10.160-rockchip-rk35xx'

|}

</ol>

<li>~~Then compile and run~~ After compiling, the '''~~hello_world~~hello.~~java~~ko'''kernel module will be generated</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ls *.ko'''

hello.ko|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Use the '''insmod''' command to insert the '''hello.ko''' kernel module into the kernel</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~javac hello_world~~sudo insmod hello.~~java~~ko'''|}~~orangepi@orangepi~~</ol><ol start="6" style="list-style-type:~$ lower-alpha;"><li>Then use the '''demsg''' command to view the output of the '''hello.ko''' kernel module. If you can see the output below, it means that the '''~~java hello_world~~hello.ko'''kernel module is loaded correctly.</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''dmesg | grep "Hello ~~World!~~"'''

[ 2871.893988] '''Hello Orange Pi -- init'''|}</ol><~~span id~~ol start="7" style="~~ubuntu~~list-~~focal~~style-~~system~~type: lower-alpha;"><li>Use the '''rmmod''' command to uninstall the '''hello.ko''' kernel module</~~span~~li>{| class="wikitable" style=~~= Ubuntu Focal system ===~~"width:800px;" |-| orangepi@orangepi:~$ '''sudo rmmod hello'''

~~<ol style="list-style-type~~orangepi@orangepi: ~~decimal~~~$ '''dmesg | grep "">~~<li>Ubuntu Focal has the GCC compilation tool chain by default, which can compile the C language program directly in the Linux system of the development board.<ol style="list-style-type: lower-alpha~~Hello"">~~<li>The version of the gcc is shown below</li></ol></li></ol>~~'''

~~orangepi@orangepi:~$ '''gcc~~ [ 2871.893988] Hello Orange Pi --~~version'''~~init

~~gcc (Ubuntu 9~~[ 3173.~~4.0~~800892] '''Hello Orange Pi -- exit'''|}</ol></li></ol>

~~This is free software; see the source for copying conditions. There is NO~~=== Assembly method of Raspberry PI 5-inch screen ===

~~warranty~~<ol style="list-style-type: decimal; ~~not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.~~"><li>First prepare the required accessories<ol style="list-style-type: lower-alpha;"><li>Raspberry PI 5-inch MIPI LCD display + touch screen</li>

[[File:pi3b-img353.png]]

</ol>

<li>~~'''hello_world.c''' program to write C language~~15pin MIPI cable</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''vim hello_world~~pi3b-img354.~~c'''~~png]]</ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>Then connect the 15pin MIPI cable to the Raspberry PI 5-inch screen in the way shown below (note the orientation of the insulation surface)</li>

~~#include <stdio~~[[File:pi3b-img355.~~h&gt~~png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Finally connect to the LCD interface of the Orange Pi 3B development board</li>

~~int main(void)~~[[File:pi3b-img356.png]]</ol>

{=== Open the Raspberry PI 5-inch screen configuration method ===

~~printf(&quot~~<ol style="list-style-type: decimal;~~Hello World!\n&quot~~"><li>The Linux image does not open the 5-inch screen of the Raspberry PI by default. If you need to use the 5-inch screen of the Raspberry PI, you need to open it manually.</li><li>The steps to open the mipi lcd configuration are as follows:<ol style="list-style-type: lower-alpha;)"><li>First run '''orangepi-config''', ordinary users remember to add '''sudo''' permission</li>{| class="wikitable" style="width:800px;" |-~~return 0;~~| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then select '''System'''</li>

[[File:pi3b-img357.png]]

</ol>

<li>Then ~~compile and run~~ select '''~~hello_world.c~~Hardware'''</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''gcc~~ pi3b-~~o hello_world hello_world~~img358.~~c'''~~png]]</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then use the arrow keys on the keyboard to locate the Rasp-7inch-touchscreen, and then use the space button to check</li>

~~orangepi@orangepi~~[[File:~$ pi3b-img359.png]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then select '''~~./hello_world~~<Save>'''to save</li>

~~Hello World!~~[[File:pi3b-img360.png]]</ol><ol start="6" style="list-style-type: lower-alpha;"><li>Then select '''<Back>'''</li>

~~<ol start="2" style="list~~[[File:pi3b-~~style-type: decimal;">~~img361.png]]~~<li>Ubuntu Focal defaults to install Python3~~</pol><ol start="7" style="list-style-type: lower-alpha;"><li>~~Python3 specific version is shown below~~Then select '''<Reboot>''' to restart the system for the configuration to take effect</li~~></ol></li></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''python3'''~~pi3b-img362.png]]

~~Python 3~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The above settings will eventually add the configuration of overlays=raspi-7inch-touchscreen to /boot/orangepiEnv.8txt.~~10 (default~~After setting, ~~Nov 14 2022~~you can check it first. If this configuration does not exist, ~~12:59:47)~~then there is a problem with the settings.'''

~~[GCC 9~~'''If you find it troublesome to use orangepi-config, you can also use the vim editor to open /boot/orangepiEnv.4txt, and then add the configuration of overlays=raspi-7inch-touchscreen is also possible.~~0] on linux~~'''</big>

~~Type "help", "copyright", "credits" or "license" for more information.~~

~~>>>~~orangepi@orangepi:~$ '''cat /boot/orangepiEnv.txt | grep "raspi"'''

'''overlays=raspi-7inch-touchscreen #Sample configuration'''|}</ol></li></ol><ol start="23" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~'''hello_world.py''' program in Python language~~After startup, you can see the lcd screen display as follows:</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''vim hello_world~~pi3b-img363.~~py'''~~png]]</ol>

~~print('Hello World!')~~=== The method of server version image rotation display direction ===

<ol start="31" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The results~~ Add '''extraargs=fbcon=rotate:the direction to rotate''' in '''/boot/orangepiEnv.txt''' This line configuration can set the direction displayed by the server version of ~~running~~ the Linux system, where the number after '''~~hello_world.py~~fbcon=rotate:''' ~~are shown below~~can be set as:</lip></olli>

<ol style="list-style-type: lower-alpha;"><li>0: normal screen (default is landscape)</li><li>1: Turn clockwise 90 degrees</li><li>2: Flip 180 degrees</li><li>3: Turn clockwise 270 degrees</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~python3 hello_world~~sudo vim /boot/orangepiEnv.pytxt'''

~~Hello World!~~overlays=lcd1

'''<~~ol start="3"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">extraargs=cma=64M fbcon=rotate:3<li/span>~~Ubuntu Focal~~'~~s compilation tool and operating environment without the installation of Java default~~''|}~~<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~You can use the following command to install~~ '''~~openjdk-17~~Note that if there is the line extraargs=cma=64M in /boot/orangepiEnv.txt by default, the configuration fbcon=rotate:3 can be added after extraargs=cma=64M (separated by spaces).'''</libig>|}</ol>

</li></ol>

<li>Then '''restart''' the Linux system and you can see that the direction displayed on the LCD screen has been rotated</li></ol>

~~orangepi@orangepi:~$ '''sudo apt install~~

~~<ol start~~=~~"2" style~~=~~"list-style-type: lower-alpha;"><li>After installation, you can check the~~ = Method of rotating display and touch direction of desktop version ~~of Java</li></ol>~~image ===

~~orangepi@orangepi:~$~~ # First open '''~~java --version~~Display'''Settings in Linux

~~openjdk 17.0~~::[[File:pi3b-img364.~~2 2022-01-18~~png]]

~~OpenJDK Runtime Environment (build 17.0.~~<ol start="2+8" style="list-~~Ubuntu~~style-~~120.04)~~type: decimal;"><li>Then select the direction you want to rotate in '''Rotation'''<ol style="list-style-type: lower-alpha;"><li>'''None''': no rotation</li><li>'''Left''': rotate left 90 degrees</li><li>'''Inverted''': Flip up and down, which is equivalent to rotating 180 degrees</li><li>'''Right''': rotate right 90 degrees</li>

~~OpenJDK 64~~[[File:pi3b-~~Bit Server VM (build 17~~img365.~~0.2+8~~png]]</ol></li></ol><ol start="3" style="list-~~Ubuntu~~style-~~120.04, mixed mode, sharing)~~type: decimal;"><li>Then click '''Apply'''</li>

[[File:pi3b-img366.png]]</ol><ol start="34" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Edit the~~ Then select '''~~hello_world.java~~Keep this configuration''' ~~of Jave version~~</li~~></ol~~>

[[File:pi3b-img367.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>At this point, the screen display has been rotated, and then close the '''Display''' program</li><li>The above steps will only select the display direction, and will not rotate the direction of the touch. Use the '''set_lcd_rotate.sh''' script to rotate the direction of the touch. After the script is set, it will automatically restart, and then you can test whether the touch has been used normally.<ol style="list-style-type: lower-alpha;"><li>'''None''': no rotation</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''set_lcd_rotate.sh none'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>'''Left''': rotate left 90 degrees</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~vim hello_world~~set_lcd_rotate.~~java~~sh left'''|}</ol><ol start="3" style="list-style-type: lower-alpha;">~~public~~ <li>'''Inverted''': Flip up and down, which is equivalent to rotating 180 degrees</li>{| class ~~hello_world~~="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''set_lcd_rotate.sh inverted'''|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>'''Right''': rotate right 90 degrees</li>{| class="wikitable" style="width:800px;" |-~~public static void main(String[] args)~~| orangepi@orangepi:~$ '''set_lcd_rotate.sh right'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The set_lcd_rotate.sh script mainly does four things:'''

~~System.out.println("Hello World!");~~

}'''1. Rotate the direction displayed by the framebuffer'''

}'''2. Rotate the direction of the touch'''

~~<ol start="4" style="list-style-type: lower-alpha;"><li>Then compile and run~~ '''~~hello_world~~3.~~java~~Turn off the boot logo'''~~</li></ol>~~

~~orangepi@orangepi:~$~~ '''~~javac hello_world~~4.~~java~~Restart the system'''

~~orangepi@orangepi:~$ '''java hello_world'''~~

~~Hello World!~~ ~~=== Ubuntu jammy system ===~~ ~~<ol style="list-style-type: decimal;"><li>Ubuntu Jammy~~ '''Rotating the touch direction is ~~installed with the GCC compilation tool chain~~ achieved by ~~default, which can directly compile~~ adding the ~~C language program in the Linux system of the development board<~~line Option "TransformationMatrix" "x x x x x x x x x" to /usr/share/X11/xorg.conf.d/p>~~<ol style="list~~40-~~style-type: lower-alpha~~libinput.conf Where "x x x x x x x x x"">~~<li>The version of the gcc~~ is ~~shown below~~configured differently for different directions.'''</libig>|}</ol>

</li></ol>

<li>Touch rotation reference</li>

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

|-

|

'''https://wiki.ubuntu.com/X/InputCoordinateTransformation'''

|}

</ol>

~~orangepi@orangepi:~$ '''gcc --version'''~~== Instructions for using the switch logo ==

~~gcc (Ubuntu 11.2.0-19ubuntu1)~~ # By default, the switch logo will only be displayed in the desktop version of the system# Set the '''bootlogo''' variable to '''false''' in '''~~11.2~~/boot/orangepiEnv.0txt'''to turn off the switch logo

~~This is free software; see the source for copying conditions. There is NO~~verbosity=1

~~warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.~~'''bootlogo=false'''|}

<ol start="23" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Write~~ Set the '''~~hello_world~~bootlogo''' variable to '''true''' in '''/boot/orangepiEnv.ctxt''' ~~program of c language~~to enable the switch logo</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim ~~hello_world~~/boot/orangepiEnv.ctxt'''

~~#include <stdio.h>~~verbosity=1

~~int main(void)~~'''bootlogo=true'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>The location of the boot logo image in the Linux system is</li>{| class="wikitable" style="width:800px;" |-| '''/usr/share/plymouth/themes/orangepi/watermark.png'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>After replacing the boot logo picture, you need to run the following command to take effect</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo update-initramfs -u'''|}</ol>

{== How to use the ZFS file system ==

~~printf(&quot~~{| class="wikitable" style="background-color:#ffffdc;~~Hello World!\n")~~width:800px;" |-| <big>'''The latest version of Ubuntu20.04, Ubuntu22.04, Debian11 and Debian12 desktop version systems have pre-installed zfs, you can use it directly.'''

~~return 0;~~'''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.'''

~~<ol start="3" style="list-style-type: lower-alpha;"><li>Then compile and run~~ '''~~hello_world~~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.c'''</~~li></ol~~big>

orangepi@orangepi:~$ '''~~gcc -o hello_world hello_world.c~~lsmod | grep "zfs"'''

~~orangepi@orangepi:~$ '''./hello_world'''~~zfs                     2801664     0

~~Hello World!~~zunicode             327680     1   zfs

~~<ol start="2" style="list-style-type: decimal~~zzstd  ">~~<li>Ubuntu jammy is installed with Python3 by default<ol style="list-style-type: lower-alpha~~ ">~~<li>Python3 specific version is shown below</li></ol></li></ol>~~               471040     1   zfs

~~orangepi@orangepi:~$ '''python3'''~~zlua                    139264     1   zfs

~~Python '''3.10.4''' (main, Apr 2 2022, 09:04:19) [GCC 11.2.0] on linux~~zcommon             69632     1   zfs

~~Type~~ znvpair &~~quot~~nbsp;~~help~~&~~quot~~nbsp;           , &~~quot~~nbsp;~~copyright~~&~~quot~~nbsp;, 61440 &~~quot~~nbsp;~~credits~~&~~quot~~nbsp; or &~~quot~~nbsp;~~license~~ 2 &~~quot~~nbsp; ~~for more information.~~zfs,zcommon

zavl &gtnbsp;&gtnbsp;&gtnbsp;                  16384     1   zfs

~~<ol start="2" style="list-style-type: lower-alpha~~icp  ">~~<li>Edit '''hello_world.py''' program in Python language</li></ol>~~                   221184     1   zfs

~~orangepi@orangepi:~$ '''vim hello_world.py'''~~spl                       77824     6   zfs,icp,zzstd,znvpair,zcommon,zavl|}

~~print('Hello World!')~~=== How to install ZFS ===

~~<ol start~~{| class="3wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~The results of running~~ '''~~hello_world~~Before installing zfs, please make sure that the Linux image used is the latest version. In addition, if zfs is already installed in the system, it needs to be installed again.py''' ~~are shown below~~</~~li></ol~~big>|}

~~orangepi@orangepi:~$~~ Before installing zfs, you need to install the kernel header file first. For the method of installing the kernel header file, please refer to the instructions in the [[Orange Pi 3B#How to install kernel header files|'''~~python3 hello_world.py~~section on the method of installing the kernel header file''']].

~~Hello World!~~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 [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''official tool'''] of the development board. Open the '''<~~ol start~~span class="~~3" style="list-style-type: decimal;~~mark">official tool<li/span>~~Ubuntu jammy defaults to compile tools~~ ''', and ~~operating environments that are not installed in Java~~enter the '''<~~ol style~~span class="~~list-style-type: lower-alpha;~~mark">zfs-related deb package folders used by Ubuntu and Debian systems<li/span>'''. You can ~~use~~ see three types of deb packages: Ubuntu20.04, Ubuntu22.04 and Debian11. Please download the ~~following command to install openjdk-18</li></ol></li></ol>~~required version.

~~orangepi@orangepi~~[[File:~~~$ '''sudo apt install~~ pi3b-~~y openjdk-18-jdk'''~~img368.png]]

~~<ol start="2" style="list-style-type: lower-alpha;"><li>~~After ~~installation~~downloading the zfs deb packages of the corresponding version, please upload them to the Linux system of the development board. For the upload method, ~~you can check~~ please refer to '''[[Orange Pi 3B#The method of uploading files to the Linux system of the development board|the description in the section of the ~~version~~ method of uploading files to the Linux system of ~~Java</li></ol>~~the development board]].'''

~~orangepi@orangepi:~$~~ After the upload is complete, use the '''~~java --version~~cd'''command in the command line of the development board Linux system to enter the directory of the deb package, and then use the following command to install the deb package of zfs.

~~openjdk 18~~{| class="wikitable" style="width:800px;" |-~~ea 2022-03-22~~| orangepi@orangepi:~$ '''sudo apt install ./*.deb'''|}

~~OpenJDK Runtime Environment (build 18~~After the installation is complete, use the following command to see the zfs-~~ea+36-Ubuntu-1)~~related kernel modules:

~~OpenJDK 64~~{| class="wikitable" style="width:800px;" |-~~Bit Server VM (build 18~~| orangepi@orangepi:~$ '''ls /lib/modules/5.10.160-~~ea+36~~rockchip-~~Ubuntu-1, mixed mode, sharing)~~rk356x/updates/dkms/'''

~~<ol start="3" style="list-style-type: lower-alpha;"><li>Edit the~~ '''~~hello_world~~icp.ko spl.ko zavl.ko zcommon.ko zfs.ko zlua.~~java~~ko znvpair.ko zunicode.ko zzstd.ko''' ~~of the Jave version</li></ol>~~|}

~~orangepi@orangepi~~Then restart the Linux system to see that the zfs kernel module will be automatically loaded:~~~$ '''vim hello_world.java'''~~

~~public~~ {| class ~~hello_world~~="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''lsmod | grep "zfs"'''

{zfs                     2801664     0

~~public static void main(String[] args)~~zunicode             327680     1   zfs

{zzstd                  471040     1   zfs

~~System.out.println(~~zlua &~~quot~~nbsp;~~Hello World!~~&~~quot~~nbsp;)                 139264     1  zfs

}zcommon             69632     1   zfs

}znvpair                 61440     2   zfs,zcommon

~~<ol start="4" style="list-style-type: lower-alpha~~zavl  ">~~<li>Then compile and run '''hello_world.java'''</li></ol>~~                    16384     1   zfs

~~orangepi@orangepi:~$ '''javac hello_world.java'''~~icp                     221184     1   zfs

~~orangepi@orangepi:~$ '''java hello_world'''~~spl                       77824     6   zfs,icp,zzstd,znvpair,zcommon,zavl|}

~~Hello World!~~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.

~~~~dkms'''~~== QT installation method ==~~|}

~~# Use the following script to install QT5 and QT Creator~~

~~orangepi@orangepi:~$ '''install_qt.sh'''~~=== Methods of creating ZFS pools ===

~~<ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">~~<li>The QT version number will be automatically printed after installation~~|-~~<ol style="list-style-type: lower-alpha;">~~| <libig>~~Ubuntu20.04 comes with QT version~~ '''~~5.12~~ZFS is based on storage pools, we can add multiple physical storage devices to the pool, and then allocate storage space from this pool.8'''~~</li></ol></li></ol>~~

~~orangepi@orangepi:~$~~ '''~~install_qt~~The following content is demonstrated based on the development board connected to an NVMe SSD and a USB flash drive.sh'''</big>|}

# First, we can use the '''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:

~~QMake version 3~~::[[File:pi3b-img369.1png]]

~~Using Qt version~~ <ol start="2" style="list-style-type: decimal;"><li>Then enter the following command to create a ZFS pool, including two storage devices, NVMe SSD and U disk</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~5.12.8~~sudo zpool create -f pool1 /dev/nvme0n1 /dev/sda''' ~~in /usr~~|}</~~lib/aarch64~~ol><ol start="3" style="list-~~linux~~style-~~gnu~~type: decimal;"><li>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</li>

[[File:pi3b-img370.png]]</ol><ol start="24" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Ubuntu22.04 comes with QT version~~ Then execute '''df -h''' to see that '''pool1''' is mounted to the '''~~5.15.3~~/pool1'''directory</li>{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''df -h''' <~~/ol~~br>

~~orangepi@orangepi:~$ '''install_qt.sh'''~~Filesystem                 Size     Used Avail Use% Mounted on

tmpfs                    1.6G     18M 1.~~....~~6G 2% /run

~~QMake version 3~~/dev/mmcblk0p2     29G     6.10G 22G 22% /

~~Using Qt version '''5~~tmpfs                    7.157G     46M 7.~~3''' in~~ 7G 1% /~~usr~~dev/~~lib/aarch64-linux-gnu~~shm

~~<ol start="3" style="list-style-type: lower-alpha~~tmpfs                   ">~~<li>Debian11 comes with QT version '''~~ 5.150M     4.0K 5.~~2'''<~~0M 1% /run/~~li>~~lock <~~/ol~~br>

~~orangepi@orangepi:~$ '''install_qt~~tmpfs                    7.~~sh'''~~7G     944K 7.7G 1% /tmp

~~......~~/dev/mmcblk0p1     1022M     115M 908M 12% /boot

~~QMake version~~ /dev/zram1                 188M     4.5M 169M 3.1% /var/log

~~Using Qt version '''5~~tmpfs                    1.156G     80K 1.~~2''' in~~ 6G 1% /~~usr~~run/~~lib~~user/~~aarch64-linux-gnu~~1000

'''pool1                    489G     9.3M 489G 1% /pool1''' |}</ol><ol start="45" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Debian12 comes with QT version '''5.15.8'''~~Use the following command to see that the file system type of pool1 is zfs</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~install_qt.sh~~mount | grep pool1'''

pool1 on /pool1 type '''zfs''' (rw,xattr,noacl)|}</ol><ol start="6" style="list-style-type: decimal;"><li>Then we can test copying a file to the ZFS pool</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo cp -v /usr/local/test.~~.....~~mp4 /pool1/'''

~~QMake version 3~~'/usr/local/test.1mp4' -> '/pool1/test.mp4'|}</ol>

~~Using Qt version '''5.15.8''' in /usr/lib/aarch64-linux-gnu~~=== Test the data deduplication function of ZFS ===

~~<ol start~~# The data deduplication function of ZFS is disabled by default, we need to execute the following command to enable it::{| class="3wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then you can see the QT Creator launch icon in~~ |-| orangepi@orangepi:~$ '''~~Applications~~sudo zfs set dedup=on pool1'''~~</li></ol>~~|}

~~[[File~~<ol start="2" style="list-style-type: decimal;"><li>Then do a simple test, first enter pool1, and then execute the following command to generate a random file with a size of 1G</li>{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img327.png~~|~~576x270px]]~~orangepi@orangepi:~$ '''cd /pool1/'''

~~QT Creator can also be opened using the following command~~root@orangepi:/pool1$ '''sudo dd if=/dev/urandom of=test.1g bs=1M count=1024'''

~~orangepi@orangepi:~$ '''qtcreator'''~~1024+0 records in

~~'''During the startup of QT and QT applications, if the following error is displayed, ignore it. This error has no impact on application running.'''~~1024+0 records out

1073741824 bytes (1.1 GB, 1.0 GiB) copied, 5.04367 s, 213 MB/s|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then use the following command to copy 1000 random files of size 1G</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/pool1$ '''for ((i=0; i<1000; i++)); do sudo cp test.1g $i.test.1g; done'''~~libGL error~~|}</ol><ol start="4" style="list-style-type: ~~failed~~ decimal;"><li>Then use '''du -lh''' to ~~create dri screen~~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</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/pool1$ '''du -lh'''

~~'''libGL error~~1002G|}</ol><ol start="5" style="list-style-type: ~~failed to load driver: rockchip~~decimal;"><li>Then use the ''' zpool list'''~~libGL error: failed~~ command to ~~create dri screen'''~~see that only 1.01G is actually occupied, because these 1001 files are all duplicates, indicating that the data deduplication function is effective.</li>

~~'''libGL error~~[[File: ~~failed to load driver: rockchip'''~~pi3b-img371.png]]</ol>

~~<ol start~~=~~"4" style~~=~~"list-style-type: decimal;"><li>The interface after QT Creator is opened is as follows</li></ol>~~= Test the data compression function of ZFS ===

~~[[File:pi3b-img328.png|418x222px]]~~# 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

~~<ol start~~::{| class="5wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>The QT Creator version is shown below~~|-| ~~<ol style="list-style-type~~orangepi@orangepi: ~~lower-alpha;"><li>The default version of QT Creator in~~ ~$ '''~~Ubuntu20.04~~cd /pool1/''' ~~is as follows</li></ol></li></ol>~~

~~[[File~~root@orangepi:~~pi3b~~/pool1$ '''sudo tar -~~img329~~cf text.~~png~~tar /var/log/ /etc/'''|~~419x224px]]~~}

<ol start="2" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The default version of QT Creator~~ Then the file size that can be seen through the '''ls -lh''' command and the space occupied in the ZFS pool are both '''~~Ubuntu22.04~~27M''' ~~is as follows~~</li~~></ol~~>

[[File:pi3b-~~img330~~img372.png~~|443x237px~~]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then we enable compression in the ZFS pool pool1</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/pool1$ '''sudo zfs set compression=lz4 pool1'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then execute the following command again to package the '''/var/log/''' and '''/etc/''' directories into a tar package</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/pool1$ '''sudo tar -cf text.tar /var/log/ /etc/'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>At this time, you can see that the size of the '''text.tar''' file is still 27M, but it only occupies 9.47M in the ZFS pool, indicating that the file is compressed</li>

[[File:pi3b-img373.png]]</ol ~~start~~>~~<li>The default version of QT Creator in '''Debian11''' is as follows~~</~~li></ol~~span>

~~[[File:pi3b-img331.png|444x238px]]~~== How to shut down and restart the development board ==

~~<ol start="4" style="list~~# During the running of the Linux system, if the Type-~~style-type: lower-alpha;"><li>The default version of QT Creator~~ C power supply is directly unplugged, some data may be lost or damaged in the file system, so please use the '''~~Debian12~~poweroff''' ~~is as follows</li></ol>~~command to shut down the Linux system of the development board before powering off. Then unplug the power again.

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-~~img332.png~~| orangepi@orangepi:~$ '''sudo poweroff'''|~~449x277px]]~~}

<ol start="62" style="list-style-type: decimal;"><li>~~Then set QT<ol style="list-style-type: lower-alpha;"><li>First open ''~~In addition, the development board is equipped with a switch button, and you can also '~~Help~~''short press'~~->~~''~~'About Plugins~~the switch button on the development board to shut down.~~..'''~~</li~~></ol></li></ol~~>

[[File:pi3b-~~img333~~img374.png~~|573x164px~~]]

~~<ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~Then remove the check box for~~ '''~~ClangCodeModel~~Note that the Linux desktop version system will pop up a confirmation box as shown in the figure below after pressing the switch button, and the system will shut down only after clicking the Shut Down option.'''</~~li></ol~~big>

[[File:pi3b-~~img334~~img375.png|~~408x254px~~center]]|}</ol><ol start="3" style="list-style-type: decimal;"><li>Short press the switch button on the development board after shutting down to start up.</li>

[[File:pi3b-img374.png]]</ol><ol start="34" style="list-style-type: ~~lower-alpha~~decimal;"><li>The command to restart the Linux system is<p/li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo''' '''~~Restart QT Creator after the Settings are complete~~reboot'''|}</~~p></li~~ol><~~li>Then make sure that QT Creator uses the GCC compiler, if the default is Clang, change it to GCC</li~~span id="linux-sdkorangepi-build-instructions"></olspan>

= '''~~Debian12 Please skip this step.~~Linux SDK——orangepi-build instructions'''=

~~[[File:pi3b~~== Compilation system requirements ==

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-| <big>'''We can cross-~~img336~~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.~~png|575x307px]]~~'''

~~<ol start="7" style="list-style-type: decimal;">~~

~~<li>You can then open a sample code</li></ol>~~

~~[[File:pi3b~~'''If you use orangepi-~~img337~~build to compile the Linux image in the Ubuntu22.~~png~~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>|~~575x312px]]~~}

<~~ol start~~span id="~~8" style="list~~compile-with-the-ubuntu22.04-system-of-the-~~style~~development-~~type: decimal;~~board"><li/span>~~Clicking on~~ === Compile with the ~~example code will automatically open~~ Ubuntu22.04 system of the ~~corresponding instruction document, you can carefully read the instructions</li></ol>~~development board ===

~~[[File:pi3b~~# The Linux SDK, namely '''orangepi-~~img338~~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.~~png|576x218px]]~~

~~<ol start~~::{| class="9wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then click~~ |-| orangepi@orangepi:~$ '''~~Configure Project~~lsb_release -a'''~~</li></ol>~~

~~[[File:pi3b-img339~~No LSB modules are available.~~png|575x304px]]~~

~~<ol start="10" style="list-style-type~~Distributor ID: ~~decimal;"><li>Then click the green triangle in the lower left corner to compile and run the sample code</li></ol>~~Ubuntu

~~[[File~~Description:~~pi3b-img340~~Ubuntu 22.~~png|575x312px]]~~04.1 LTS

Release: '''<~~ol start="11"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>After waiting for a period of time, the interface shown in the following figure will pop up, which indicates that QT can compile and run normally</li>~~22.04</olspan>'''

~~[[File~~Codename:~~pi3b-img341.png~~jammy|~~576x308px]]~~}

<ol start="122" style="list-style-type: decimal;"><li>~~Reference documents~~'''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>

~~https://wiki.qt~~</~~Install_Qt_5_on_Ubuntu~~span>

~~https://download~~=== Compile with x64 Ubuntu22.~~qt.io/archive/qtcreator~~04 computer ===

~~https://download~~# The Linux SDK, '''orangepi-build''', supports running on computers with '''Ubuntu 22.qt04''' 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.~~io/archive/qt~~

~~== ROS Installation Method ==~~a'''

~~=== How to install ROS 1 Noetic on Ubuntu 20.04 ===~~

~~# The current active version of ROS 1 is as follows, the recommended version is '''Noetic Ninjemys'''~~Distributor ID: Ubuntu

~~[[File~~Description:~~pi3b-img342~~Ubuntu 22.~~png|345x235px]]~~04 LTS

~~[[File~~Release:~~pi3b-img343~~'''22.~~png|576x210px]]~~04'''

~~[http~~Codename:~~//docs.ros.org/ http://docs.ros.org]~~jammy ~~'''https://wiki.ros.org/Distributions'''~~|}

<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 ~~official~~ download address of the installation ~~document link~~ image of ~~ROS 1~~ Ubuntu 22.04 '''~~Noetic Ninjemys~~amd64''' version is ~~as follows~~:</lip></olli>

{| class="wikitable" style="width:800px;" |-| [~~http~~https://~~wiki~~repo.~~ros~~huaweicloud.~~org~~com/~~noetic~~ubuntu-releases/~~Installation~~21.04/~~Ubuntu~~ ubuntu-21.04-desktop-amd64.iso '''~~http~~https://~~wiki~~mirrors.~~ros~~tuna.~~org~~tsinghua.edu.cn/~~noetic~~ubuntu-releases/~~Installation~~22.04/~~Ubuntu~~ubuntu-22.04-desktop-amd64.iso''']

~~<ol start="3" style="list-style-type: decimal;">~~<li>In the official installation document of ROS '''Noetic Ninjemys''', Ubuntu recommends using Ubuntu20.04, so please make sure that the system used by the development board is '''Ubuntu20.04 desktop system'''</li></ol> ~~http://wiki.ros.org/noetic/Installation~~ ~~[[File:pi3b-img344.png|312x176px]]~~Or

'''https://repo.huaweicloud.com/ubuntu-releases/22.04/ubuntu-22.04.1-desktop-amd64.iso'''

|}

</ol>

<li>~~Then use~~ After installing Ubuntu 22.04 on the computer or virtual machine, please set the ~~script below~~ software source of Ubuntu 22.04 to Tsinghua source, otherwise it is easy to make mistakes due to ~~install ros1~~network reasons when installing the software later<ol style="list-style-type: lower-alpha;"><li>For the method of replacing Tsinghua source, please refer to the instructions on this web page</olli>

~~orangepi@orangepi3b~~{| class="wikitable" style="width:~$ 800px;" |-| '''~~install_ros~~https://mirrors.tuna.tsinghua.edu.~~sh ros1~~cn/help/ubuntu/'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Note that the Ubuntu version needs to be switched to 22.04</li>

[[File:pi3b-img376.png]]</ol><ol start="53" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Before using~~ The content of the ~~ROS tool, you first need~~ '''/etc/apt/sources.list''' file that needs to ~~initialize rosdep, and then you can quickly install some system dependencies and some core components in ROS when compiling the source code~~be replaced is</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''~~Note that running the following command needs to ensure that the development board can access github normally, otherwise an error will be reported due to network problems~~sudo mv /etc/apt/sources.list /etc/apt/sources.list.bak'''

test@test:~$ '''~~The install_ros.sh script will try to modify~~ sudo vim /etc/hosts and automatically run the following commands. However, this method cannot guarantee normal access to github every time. If the following error is displayed after installing ros1 in install_ros.sh, please find other ways to allow the Linux system of the development board to access github normally, and then manually run the following Orderapt/sources.list'''

~~'''https:~~# By default, the source image is commented to improve the speed of apt update, you can uncomment it yourself if necessary</~~/raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml'''~~p>

~~'''Hit~~ deb https://~~raw~~mirrors.~~githubusercontent~~tuna.~~com/ros/rosdistro~~tsinghua.edu.cn/~~master~~ubuntu/~~rosdep/base.yaml'''~~jammy main restricted universe multiverse

~~'''ERROR~~# deb-src https: ~~error loading sources list:'''~~//mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse

~~'''The read operation timed out'''~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse

~~orangepi@orangepi~~# deb-src https:~~~$ '''source~~ /~~opt~~/~~ros~~mirrors.tuna.tsinghua.edu.cn/~~noetic~~ubuntu/~~setup.bash'''~~jammy-updates main restricted universe multiverse

~~orangepi@orangepi~~deb https:~~~$ '''sudo rosdep init'''~~//mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse

~~Wrote~~ # deb-src https:/~~etc~~/~~ros/rosdep/sources~~mirrors.tuna.tsinghua.~~list~~edu.dcn/ubuntu/20jammy-~~default.list~~backports main restricted universe multiverse

~~Recommended~~deb https: ~~please run~~//mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-security main restricted universe multiverse

~~rosdep update~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-security main restricted universe multiverse

~~orangepi@orangepi:~$ '''rosdep update'''~~

~~reading in sources list data from~~ # Pre-release software source, not recommended to enable</~~etc/ros/rosdep/sources.list.d~~p>

~~Hit~~ # deb https://~~raw~~mirrors.~~githubusercontent~~tuna.~~com~~tsinghua.edu.cn/~~ros~~ubuntu/~~rosdistro~~jammy-proposed main restricted universe multiverse</~~master/rosdep/osx-homebrew.yaml~~p>

~~Hit~~ # deb-src https://~~raw~~mirrors.~~githubusercontent~~tuna.~~com~~tsinghua.edu.cn/~~ros~~ubuntu/~~rosdistro~~jammy-proposed main restricted universe multiverse</~~master~~p>|}</~~rosdep~~ol><ol start="4" style="list-style-type: lower-alpha;"><li>After the replacement, you need to update the package information and make sure there is no error</~~base.yaml~~li>{| class="wikitable" style="width:800px;" |-| ~~Hit https~~test@test:~$ '''sudo apt update'''|}</ol><ol start="5" style="list-style-type: lower-alpha;"><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.</~~raw.githubusercontent.com~~span>'''</~~ros~~li></~~rosdistro~~ol></~~master~~li></~~rosdep~~ol></~~python.yaml~~span>

~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml~~== Get the source code of Linux sdk ==

~~Hit https:~~</~~/raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml~~span>=== Download orangepi-build from github ===

~~Query rosdistro index https://raw~~# The Linux sdk actually refers to the code of orangepi-build.~~githubusercontent~~orangepi-build is modified based on the armbian build system.~~com/ros/rosdistro/master/index~~Using orangepi-v4build, multiple versions of Linux images can be compiled.~~yaml~~First download the code of orangepi-build, the command is as follows:

~~Skip end~~::{| class="wikitable" style="width:800px;" |-of| test@test:~$ '''sudo apt-~~life distro "ardent"~~get update'''

~~Skip end~~test@test:~$ '''sudo apt-ofget install -~~life distro "bouncy"~~y git'''

~~Skip end~~test@test:~$ '''git clone https://github.com/orangepi-ofxunlong/orangepi-build.git -b next'''|}::{| class="wikitable" style="background-~~life distro &quot~~color:#ffffdc;~~crystal&quot~~width:800px;" |-| <big>'''Note that the Orange Pi 3B 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>

~~Skip end-of-life distro "dashing"~~<div class="figure">

~~Skip end~~[[File:pi3b-~~of-life distro "eloquent"~~img377.png|center]]

~~Add distro &quot~~</div>|}::{| class="wikitable" style="background-color:#ffffdc;~~foxy&quot~~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>|}

~~Add distro "galactic&quot~~<ol start="2" style="list-style-type: decimal;"><li>The u-boot and Linux kernel versions currently used by the development board are as follows</li>

~~Skip end~~{| class="wikitable" style="width:800px;text-align: center;"|-|'''branch'''|'''u-boot version'''|'''Linux Kernel version'''|-|'''legacy'''|'''u-ofboot 2017.09'''|'''Linux5.10'''|}{| class="wikitable" style="background-~~life distro &quot~~color:#ffffdc;~~groovy&quot~~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.'''

~~Add distro &quot~~'''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><ol start="3" style="list-style-type: decimal;~~humble&quot~~"><li>orangepi-build will contain the following files and folders after downloading<ol style="list-style-type: lower-alpha;"><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</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''ls'''

~~Skip end-of-life distro~~ '''build.sh      external      LICENSE      README.md   &~~quot~~nbsp;~~hydro~~&~~quot~~nbsp;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>|}</ol></li></ol>

~~Skip end~~=== Download the cross-~~of-life distro "indigo"~~compilation toolchain ===

~~Skip end~~{| 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 ofthe development board in the Ubuntu22.04 of the development board will not download the cross-compilation toolchain. At this time, orangepi-~~life distro "jade"~~build/toolchains will be an empty folder.'''</big>|}

~~Skip end~~# When orangepi-build runs for the first time, it will automatically download the cross-compilation toolchain and put it in the '''toolchains''' folder. Every time after running the build.sh script oforangepi-build, it will check whether the cross-~~life distro "kinetic"~~compilation toolchain in '''toolchains''' exists , if it does not exist, the download will be restarted, if it exists, it will be used directly, and the download will not be repeated.

~~Skip end-of-life distro "lunar"~~<div class="figure">

~~Add distro "melodic"~~::[[File:pi3b-img378.png]]

~~Add distro &quot~~</div><ol start="2" style="list-style-type: decimal;~~noetic&quot~~"><li>The image URL of the cross-compilation toolchain in China is the open source software image site of Tsinghua University</li>{| class="wikitable" style="width:800px;" |-| '''https://mirrors.tuna.tsinghua.edu.cn/armbian-releases/_toolchain/'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>After '''toolchains''' is downloaded, it will contain multiple versions of cross-compilation toolchains, and the development board will only use two of them</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''ls toolchains/'''

~~Add distro "rolling"~~gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu

~~updated cache in /home/orangepi/~~gcc-arm-11.~~ros/rosdep/sources~~2-2022.~~cache~~02-x86_64-arm-none-linux-gnueabihf

~~<ol start="6" style="list~~gcc-~~style~~arm-~~type: decimal;"><li>Then open a command line terminal window on the desktop, and then use the test_ros~~9.~~sh script to start a small turtle routine to test whether ROS can be used normallyorangepi@orangepi:~$ '''test_ros~~2-2019.~~sh'''</li><li>After running the '''test_ros.sh''' script, a little turtle as shown in the figure below will pop up</li></ol>~~12-x86_64-aarch64-none-linux-gnu

~~<div class="figure">~~gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf

~~[[File:pi3b~~gcc-~~img345~~linaro-4.9.4-2017.~~png|575x275px|图片4]]~~01-x86_64_arm-linux-gnueabi

~~</div><ol start="8" style="list~~gcc-~~style~~linaro-~~type: decimal;"><li>Then please keep the terminal window just opened at the top</li></ol>~~5.5.0-2017.10-x86_64_arm-linux-gnueabihf

~~<div class="figure">~~gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu

~~[[File:pi3b~~gcc-~~img346~~linaro-7.4.1-2019.~~png|576x275px|图片5]]~~02-x86_64_arm-linux-gnueabi

~~</div><ol start="9" style="list~~gcc-~~style~~linaro-~~type: decimal;"><li>At this time, press the direction keys on the keyboard to control the little turtle to move up, down, left, and right</li></ol>~~aarch64-none-elf-4.8-2013.11_linux

~~[[File:pi3b~~gcc-~~img347~~linaro-arm-linux-gnueabihf-4.8-2014.~~png|575x296px]]~~04_linux

gcc-linaro-arm-none-eabi-4.8-2014.04_linux|}<~~span id~~/ol><ol start="4" style="~~how~~list-style-type: decimal;"><li>The cross-compilation toolchain used tocompile the Linux kernel source code is<ol style="list-~~install~~style-~~ros~~type: lower-alpha;"><li>Linux5.10</li>{| class="wikitable" style="width:800px;" |-| '''gcc-arm-11.2-2022.2-~~galactic~~x86_64-onaarch64-~~ubuntu~~none-~~20.04"~~linux-gnu'''|}</ol></li></~~span~~ol><ol start="5" style="list-style-type: decimal;"><li>The cross-compilation tool chain used to compile the u-boot source code is<ol style= ~~How to install ROS 2 Galactic on Ubuntu 20~~"list-style-type: lower-alpha;"><li>v2017.04 09</li>{| class="wikitable" style="width:800px;" |-| '''gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu'''|}</ol></li></ol>

~~# The current active version of ROS 2 is as follows, the recommended version is '''Galactic Geochelone'''~~=== orangepi-build complete directory structure description ===

~~[[File~~<ol style="list-style-type:~~pi3b~~decimal;"><li>The orangepi-build repository does not contain the source code of the Linux kernel, u-boot, and cross-~~img348~~compilation toolchain after downloading.~~png|576x271px]]~~The source code of the Linux kernel and u-boot is stored in an independent git repository<ol style="list-style-type: lower-alpha;"><li>The git repository where the Linux kernel source code is stored is as follows:</li>~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img349.png~~|~~575x265px]]~~ ~~[http~~'''https://~~docs~~github.~~ros.org~~com/orangepi-xunlong/ ~~http:~~linux-orangepi/tree/~~docs~~orange-pi-5.~~ros~~10-rk35xx'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The git warehouse where the b.~~org]~~u-boot source code is stored is as follows:</li>{| class="wikitable" style="width:800px;" |-| '''~~http~~https://~~docs.ros~~github.~~org~~com/enorangepi-xunlong/~~galactic~~u-boot-orangepi/tree/~~Releases~~v2017.~~html~~09-rk3588'''|}</ol></li></ol><ol start="2" style="list-style-type: decimal;"><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 script:b. '''external''': Contains the configuration files needed to compile the image, scripts with specific functions, and the source code of some programs. The ~~link to~~ rootfs compressed package cached during the image compilation process is also stored in external:c. '''kernel''': stores the source code of the Linux kernel, and the folder named orange-pi-5.10-rk35xx stores the kernel source code of the legacy branch of the RK3588/RK3588S/RK3566 series development boards. Please do not manually name the folder name of the kernel source code Modify, if modified, the kernel source code will be re-downloaded when the ~~official ROS~~ compilation system is running:d. '''LICENSE''': GPL 2 license file:e. '''~~Galactic Geochelone~~README''' ~~installation~~ .md: orangepi-build documentation is :f. '''output''': Store compiled deb packages such as ~~follows~~u-boot and Linux, compilation logs, and compiled images and other files:g. '''scripts''':general scripts for compiling Linux images</lip>:h. '''toolchains''': store cross-compilation toolchain</olp> :i. '''u-boot'''~~docs~~: stores the source code of u-boot, the folder named v2017.~~ros~~09-rk3588 stores the u-boot source code of the legacy branch of the RK3588/RK3588S/RK3566 series development boards, the name of the folder of the u-boot source code Please do not modify it manually, if it is modified, the u-boot source code will be re-downloaded when the compiling system is running:j.~~org~~'''userpatches''': Store configuration files needed to compile scripts</enp></li>:{| class="wikitable" style="width:800px;" |-| test@test:~/~~galactic~~orangepi-build$ '''ls'''</~~Installation~~p>'''build.~~html~~sh     external     kernel     LICENSE     output     README.md     scripts     toolchains     u-boot     userpatches'''|}</ol>

~~'''http://docs.ros.org/en/galactic/Installation/Ubuntu~~== Compile u-~~Install-Debians.html'''~~boot ==

~~<ol start="3" style="list-style-type: decimal;">~~<li>It is recommended to use Ubuntu20.04 in the official installation document of ROS 2 '''Galactic Geochelone''', so please ensure that the system used by the development board is '''Ubuntu20.04 desktop version'''. There are several ways to install ROS 2. The following shows how to install ROS 2 '''Galactic Geochelone''' using '''Debian packages'''</li>~~<li>Use~~ # Run the ~~'''install_ros~~build.sh~~'''~~ script , remember to ~~install ros2</li></ol>~~add sudo permission

~~orangepi~~::{| class="wikitable" style="width:800px;" |-| test@~~orangepi~~test:~/orangepi-build$ '''~~install_ros~~sudo ./build.sh ~~ros2~~'''|}

<ol start="52" style="list-style-type: decimal;"><li>~~The~~ Select '''~~install_ros.sh''' script will automatically run the '''ros2~~ U-hboot package''' ~~command after installing ros2. If you can see the following print~~, ~~it means that the ros2 installation is complete~~then enter</li~~></ol~~>

~~usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...~~<div class="figure">

~~ros2 is an extensible command~~[[File:pi3b-~~line tool for ROS 2~~img379.png]]

~~optional arguments~~</div></ol><ol start="3" style="list-style-type:decimal;"><li>Then select the model of the development board</li>

~~-h, --help show this help message and exit~~<div class="figure">

~~Commands~~[[File:pi3b-img380.png]]

~~action Various action related sub~~</div></ol><ol start="4" style="list-style-type: decimal;"><li>Then it will start to compile u-boot, and some information prompted during compilation is explained as follows<ol style="list-style-type: lower-alpha;"><li>u-boot source code version</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Compiling u-boot [ '''v2017.09''' ]|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The version of the cross-compilation toolchain</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Compiler version [ '''aarch64-linux-gnu-gcc 7.4.1''' ]|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Path to the generated u-boot deb package</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Target directory [ '''orangepi-build/output/debs/u-boot''' ]|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>The package name of the generated u-~~commands~~boot deb package</li>{| class="wikitable" style="width:800px;" ~~bag Various rosbag related sub~~|-~~commands~~| ~~component Various component related sub~~[ o.k. ] File name [ '''linux-u-~~commands~~boot-legacy-orangepi3b_1.0.0_arm64.deb''' ]|}~~daemon Various daemon related sub~~</ol><ol start="5" style="list-~~commands~~style-type: lower-alpha;"><li>Compilation time</li>~~doctor Check ROS setup and other potential issues~~{| class="wikitable" style="width:800px;" |-| [ o.k. ] Runtime [ '''1 min''' ]|}</ol><ol start="6" style="list-style-type: lower-alpha;"><li>Repeat the command to compile u-boot, use the following command to start compiling u-boot directly without selecting through the graphical interface ~~Show information about ROS interfaces~~</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=u-boot KERNEL_CONFIGURE=no''' ]|}~~launch Run a launch file~~</ol></li></ol>~~lifecycle Various lifecycle related sub~~<ol start="5" style="list-~~commands~~style-type: decimal;"><li>View the u-boot deb package generated by compilation</li>~~multicast Various multicast related sub~~{| class="wikitable" style="width:800px;" |-~~commands~~| ~~node Various node related sub~~test@test:~/orangepi-build$ '''ls output/debs/u-~~commands~~boot/'''

~~param Various param related sub~~linux-~~commands~~u-boot-legacy-orangepi3b_1.0.0_arm64.deb|}</ol><ol start="6" style="list-style-type: decimal;"><li>The files contained in the generated u-boot deb package are as follows<ol style="list-style-type: lower-alpha;"><li>Use the following command to decompress the deb package</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''cd output/debs/u-boot'''

~~pkg Various package related sub~~test@test:~/orangepi_build/output/debs/u-~~commands~~boot$ $ '''dpkg -x''' \

~~run Run~~ '''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb . (Note that there is a ~~package specific executable~~"." at the end of the command)'''

~~security Various security related sub~~test@test:~/orangepi_build/output/debs/u-~~commands~~boot$ '''ls'''

~~service Various service related sub~~linux-~~commands~~u-boot-legacy-orangepi3b_1.0.0_arm64.deb '''usr'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The decompressed file is as follows</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build/output/debs/u-boot$ '''tree usr'''

~~topic Various topic related sub-commands~~usr

~~wtf Use `wtf` as alias to `doctor`~~└── lib

~~Call `ros2 <command>~~ :├── linux-~~h` for more detailed usage~~u-boot-legacy-orangepi3b_1.0.0_arm64

~~<ol start="6" style="list-style-type~~: ~~decimal;"><li>Then you can use the '''test_ros~~│ ├── idbloader.~~sh''' script to test whether ROS 2 is installed successfully. If you can see the following print, it means that ROS 2 can run normally</li></ol>~~img

~~orangepi@orangepi3b~~:~~~$ '''test_ros~~│ ├── rkspi_loader.~~sh'''~~img

~~[INFO] [1671174101~~:│ └── u-boot.~~200091527] [talker]: Publishing: 'Hello World: 1'~~itb

~~[INFO] [1671174101.235661048] [listener]~~: ~~I heard: [Hello World: 1]~~└── u-boot

~~[INFO] [1671174102.199572327] [talker]~~: ~~Publishing~~: ~~'Hello World: 2'~~├── LICENSE

~~[INFO] [1671174102.204196299] [listener]~~: ~~I heard~~: ~~[Hello World: 2]~~├── orangepi-3b-rk3566_defconfig

~~[INFO] [1671174103.199580322] [talker]~~: ~~Publishing~~: ~~'Hello World: 3'~~└── platform_install.sh

~~[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]~~

3 directories, 6 files

|}

</ol>

</li></ol>

<li>~~Run~~ When the ~~following command~~ 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 '''(This function needs to ~~open rviz2~~be fully compiled once u-boot, otherwise it will prompt that the source code of u-boot cannot be found. If the source code compressed package is downloaded from Google cloud disk, there is no such problem, because the source code of u-boot have been cached)''', otherwise the changes made will be reverted, the method is as follows:</li~~></ol~~>

~~orangepi@orangepi:~$ '''source~~ Set the IGNORE_UPDATES variable in userpatches/~~opt/ros/galactic/setup~~config-default.~~bash'''~~conf to "yes"

~~orangepi~~{| class="wikitable" style="width:800px;" |-| test@~~orangepi~~test:~/orangepi-build$ '''~~ros2 run rviz2 rviz2~~vim userpatches/config-default.conf'''

IGNORE_UPDATES="'''<~~div class~~span style="~~figure~~color:#FF0000">yes'''" ~~[[File:pi3b-img350.png|576x324px~~|~~1]]~~}</~~div~~ol>

<li>~~For~~ When debugging u-boot code, you can use the ~~usage of ROS, please refer~~ following method to update u-boot in the ~~documentation of ROS 2~~Linux image for testing<ol style="list-style-type: lower-alpha;"><li>Upload the compiled u-boot deb package to the Linux system of the development board</olli>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''cd output/debs/u-boot'''

~~http~~test@test:~/orangepi_build/~~docs.ros.org~~output/endebs/~~galactic/Tutorials.html~~u-boot$ '''scp \'''

'''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb root@192.168.1.xxx:/root'''|}<~~span id~~/ol><ol start="~~how~~2" style="list-style-type: lower-alpha;"><li>Then log in tothe development board and uninstall the deb package of u-~~install~~boot installed</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''apt purge -y linux-u-~~ros~~boot-2orangepi3b-~~humble~~legacy'''|}</ol><ol start="3" style="list-onstyle-~~ubuntu~~type: lower-~~22.04~~alpha;"><li>Install the new u-boot deb package just uploaded</~~span~~li>{| class="wikitable" style=~~= How to install ROS 2 Humble on Ubuntu 22.04 ===~~"width:800px;" |-| root@orangepi:~# ~~Use the~~ '''~~install_ros~~dpkg -i''' '''linux-u-boot-legacy-orangepi3b_1.sh0.0_arm64.deb''' |}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then run the nand-sata-install script ~~to install ros2~~</li>{| class="wikitable" style="width:800px;" |-| ~~orangepi~~root@orangepi:~$ # '''~~install_ros.sh ros2~~nand-sata-install'''|}</ol><ol start="25" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~The~~ Then select '''~~install_ros.sh~~5 Install/Update the bootloader on SD/eMM''' ~~script will automatically run~~ to update the u-boot in the TF card or '''~~ros2 -h~~7 Install/Update the bootloader on SPI Flash''' ~~command after installing ros2. If you can see~~ to update the ~~following print, it means that~~ u-boot in the ~~ros2 installation is complete~~SPI Flash</li~~></ol~~>

~~usage~~[[File: ~~ros2 [~~pi3b-himg381.png]] ~~Call `ros2 <command&gt~~</ol><ol start="6" style="list-style-type: lower-alpha; ~~-h` for more detailed usage. ...~~"><li>After pressing the Enter key, a Warning will pop up first</li>

~~ros2 is an extensible command~~[[File:pi3b-~~line tool for ROS 2~~img382.png]]</ol><ol start="7" style="list-style-type: lower-alpha;"><li>Press the Enter key again to start updating u-boot, and the following information will be displayed after the update is completed</li>

~~optional arguments~~[[File:pi3b-img383.png]]</ol><ol start="8" style="list-style-type: lower-alpha;"><li>Then you can restart the development board to test whether the modification of u-boot takes effect</li></ol></li></ol><ol start="9" style="list-style-type: decimal;"><li>Other useful information<ol style="list-style-type: lower-alpha;"><li>In the u-boot 2017.09 source code, the defconfig configuration 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/configs/orangepi_5_defconfig '''orangepi-build/u-boot/v2017.09-rk3588/configs/orangepi-3b-rk3566_defconfig''']|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>In the 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/rk3588s-orangepi-5.dts '''orangepi-build/u-boot/v2017.09-rk3588/arch/arm/dts/rk3566-orangepi-3b.dts''']|}</ol></li></ol>

~~-h, --help show this help message and exit~~== Compile the Linux kernel ==

~~Commands:~~# Run the build.sh script, remember to add sudo permission

~~action Various action related sub~~::{| class="wikitable" style="width:800px;" |-~~commands~~| test@test:~/orangepi-build$ '''sudo ./build.sh'''|}

~~bag Various rosbag related sub~~<ol start="2" style="list-~~commands~~style-type: decimal;"><li>Select '''Kernel package''', then enter</li>

~~component Various component related sub-commands~~<div class="figure">

~~daemon Various daemon related sub~~[[File:pi3b-~~commands~~ ~~doctor Check ROS setup and other potential issues~~ ~~interface Show information about ROS interfaces~~ ~~launch Run a launch file~~ ~~lifecycle Various lifecycle related sub-commands~~ ~~multicast Various multicast related sub-commands~~ ~~node Various node related sub-commands~~ ~~param Various param related sub-commands~~ ~~pkg Various package related sub-commands~~ ~~run Run a package specific executable~~ ~~security Various security related sub-commands~~ ~~service Various service related sub-commands~~ ~~topic Various topic related sub-commands~~ ~~wtf Use `wtf` as alias to `doctor`~~ ~~Call `ros2 <command> -h` for more detailed usage~~img384.png]]

</div></ol>

<li>Then ~~you can use~~ select the ~~'''test_ros.sh''' script to test whether ROS 2 is installed successfully. If you can see~~ model of the ~~following print, it means that ROS 2 can run normally~~development board</li~~></ol~~>

~~orangepi@orangepi3b:~$ '''test_ros.sh'''~~<div class="figure">

[~~INFO] [1671174101.200091527] [talker]: Publishing: 'Hello World: 1'~~ ~~[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: 1]~~ ~~[INFO] [1671174102.199572327] [talker]: Publishing: 'Hello World: 2'~~ ~~[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]~~ ~~[INFO] [1671174103.199580322]~~ [~~talker]: Publishing: 'Hello World~~File: 3' ~~[INFO] [1671174103~~pi3b-img380.~~204019965] [listener~~png]~~: I heard: [Hello World: 3~~]

</div></ol>

<li>~~Run~~ Then it will prompt whether to display the kernel configuration interface. If you do not need to modify the kernel configuration, select the ~~following command~~ first one. If you need to ~~open rviz2~~modify the kernel configuration, select the second one.</li~~></ol~~>

~~orangepi@orangepi:~$ '''source /opt/ros/humble/setup.bash'''~~ ~~orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''~~ ~~<div class="figure">~~ [[File:pi3b-~~img351~~img385.png~~|576x324px|1~~]] </~~div~~ol>

<li>~~Reference documents~~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</li~~></ol~~>

~~'''http~~[[File:~~//docs~~pi3b-img386.~~ros.org/en/humble/index.html'''~~png]]

~~[http~~<ol style="list-style-type:lower-alpha;"><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</li>{| class="wikitable" style="width:800px;" |-| test@test:~/~~docs~~orangepi-build$ '''sudo .~~ros.org~~/~~en/galactic/Tutorials~~build.~~html~~ sh KERNEL_CONFIGURE=no'''~~http~~|}</ol><ol start="2" style="list-style-type:lower-alpha;"><li>You can also set '''KERNEL_CONFIGURE=no''' in the '''orangepi-build/userpatches/~~docs~~config-default.~~ros.org/en/humble~~conf''' configuration file, which can permanently disable this function</~~Installation~~p></li><li>If the following error is displayed when compiling the kernel, it is because the terminal interface of the Ubuntu~~-Install-Debians.html~~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</li>

~~== How to install kernel header files ==~~ ~~# The Linux image released by OPi comes with the deb package of the kernel header file by default, and the storage location is '''/opt/'''~~ ~~orangepi@orangepi~~[[File:~~~$ '''ls /opt/linux-headers*'''~~ ~~/opt/linux-headers-legacy-rockchip~~pi3b-~~rk356x_x.x~~img387.~~x_arm64.deb~~png]] ~~<ol start="2" style="list-style-type: decimal;"><li>Use the following command to install the deb package of the kernel header file</li>~~</ol> ~~'''The name of the kernel header file deb package needs to be replaced with the actual name, please do not copy it.'''~~ ~~orangepi@orangepi:~$ '''sudo dpkg -i /opt/linux-headers-legacy-rockchip-rk356x_1.x.x_arm64.deb'''~~ ~~<ol start="3" style="list-style-type: decimal;"~~>~~<li>After installation, you can see the folder where the kernel header files are located under '''/usr/src'''</li>~~</ol> ~~orangepi@orangepi:~$ '''ls /usr/src'''~~ ~~linux-headers-5.10.160-rockchip-rk356x~~ <ol start="46" style="list-style-type: decimal;"><li>~~Then you can write a hello kernel module to test~~ Part of the information prompted when compiling the kernel ~~header file~~source code is as follows

<li>~~First write the code~~ The version of the ~~hello~~ Linux kernel ~~module, as follows:~~source code</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Compiling current kernel [ '''5.10.160''' ]|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The version of the cross-compilation toolchain used</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Compiler version [ '''aarch64-none-linux-gnu-gcc 11.2.1''' ]|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The configuration file used by the kernel by default and the path where it is stored</li>~~orangepi@orangepi~~{| class="wikitable" style="width:~$ 800px;" |-| [ o.k. ] Using kernel config file [ '''~~vim hello~~config/kernel/linux-rockchip-rk356x-legacy.cconfig''']|}</ol>~~#include &lt~~<ol start="4" style="list-style-type: lower-alpha;~~linux~~"><li>The path of the deb package related to the kernel generated by compiling</~~init~~li>{| class="wikitable" style="width:800px;" |-| [ o.~~h&gt~~k. ] Target directory [ '''orangepi-build/output/debs/''' ]|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>The package name of the compiled kernel image deb package</li>~~#include &lt~~{| class="wikitable" style="width:800px;" |-| [ o.k. ] File name [ '''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb''' ]|}</ol><ol start="6" style="list-style-type: lower-alpha;"><li>The time used for compilation</~~module.h&gt~~li>{| class="wikitable" style="width:800px;" |-~~static int hello_init(void)~~| [ o.k. ] Runtime [ '''5 min''' ]{|}</ol>~~printk("Hello Orange Pi~~ <ol start="7" style="list-style- ~~init\n&quot~~type: lower-alpha;)"><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</li>{| class="wikitable" style="width:800px;" |-| ~~return 0~~[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=kernel KERNEL_CONFIGURE=no''' ]|}</ol></li></ol><ol start="7" style="list-style-type: decimal;"><li>View the deb package related to the kernel generated by compilation}<ol style="list-style-type: lower-alpha;"><li>'''linux-dtb-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Contains dtb files used by the kernel</li>~~static void hello_exit(void)~~<li>'''linux-headers-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Include kernel header files</li><li>'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Contains kernel images and kernel modules</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''ls output/debs/linux-*'''

~~printk("Hello Orange Pi~~ output/debs/linux-dtb- ~~exit\n");~~legacy-rockchip-rk356x_1.0.0_arm64.deb output/debs/linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb

~~return~~output/debs/linux-headers-legacy-rockchip-rk356x_1.0.0_arm64.deb|}</ol></li></ol><ol start="8" style="list-style-type: decimal;"><li>The files contained in the generated Linux-image deb package are as follows<ol style="list-style-type: lower-alpha;"><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'''

~~module_init(hello_init);~~test@test:~/orangepi_build/output/debs$ '''cp \'''

~~module_exit(hello_exit);~~'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb test/'''

~~MODULE_LICENSE("GPL");~~test@test:~/orangepi_build/output/debs$ '''cd test'''

~~<ol start="2" style="list-style-type~~test@test: ~~lower-alpha;"><li>Then write the Makefile for compiling the hello kernel module, as follows:<~~~/orangepi_build/output/~~li><~~debs/~~ol>~~test$ '''dpkg -x \'''

~~orangepi@orangepi:~$~~ '''~~vim Makefile~~linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb .'''

~~ifneq (~~test@test:~/orangepi_build/output/debs/test$~~(KERNELRELEASE),)~~'''ls'''

~~obj~~'''boot etc lib''' linux-mimage-legacy-rockchip-rk356x_1.0.0_arm64.deb '''usr'''|}</ol><ol start="2" style="list-style-type:lower-alpha;"><li>The decompressed file is as follows</li>{| class=~~hello.o~~"wikitable" style="width:800px;" |-| test@test:~/orangepi-build/output/debs/test$ '''tree -L 2'''

~~else~~.

~~KDIR :=/lib/modules/$(shell uname -r)/build~~├── boot

~~PWD :=$(shell pwd)~~│ ├── config-5.10.160-rockchip-rk356x

~~all:~~│ ├── System.map-5.10.160-rockchip-rk356x

~~make~~ │ └── vmlinuz-~~C $(KDIR) M=$(PWD) modules~~5.10.160-rockchip-rk356x

~~clean:~~├── etc

~~rm -f *.ko *.o *.mod.o *.mod *.symvers *.cmd *.mod.c *.order~~│ └── kernel

~~endif~~├── lib

~~<ol start="3" style="list-style-type: lower-alpha;"><li>Then use the make command to compile the hello kernel module. The output of the compilation process is as follows:</li></ol>~~│ └── modules

~~'''If there is a problem with compiling the code you copied here, please go to the official tool to download the source code and upload it to the Linux system of the development board for testing~~├── linux-image-legacy-rockchip-rk356x_1.~~'''~~0.0_arm64.deb

~~[[File:pi3b-img352.png|337x52px]]~~└── usr

~~orangepi@orangepi~~:~~~$ '''make'''~~├── lib

~~make -C~~ :└── share|}</~~lib~~ol></~~modules~~li></~~5.10.160~~ol><ol start="9" style="list-style-~~rockchip~~type: decimal;"><li>The orangepi-~~35xx/build M=~~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 cloud disk, there is no such problem, because the source code of Linux has been cached)''', otherwise the The changes made will be reverted as follows:</~~home/orangepi modules~~li>

~~make[1]: Entering directory~~ Set the IGNORE_UPDATES variable in '''userpatches/~~usr/src/linux-headers~~config-5default.~~10.160-rockchip-rk35xx~~conf'''to "yes"

~~CC [M] /home~~{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''vim userpatches/~~hello~~config-default.oconf'''

~~MODPOST~~ IGNORE_UPDATES="'''yes</~~home~~span>'''"|}</~~orangepi~~ol><ol start="10" style="list-style-type: decimal;"><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</~~Module.symvers~~p><ol style="list-style-type: lower-alpha;">~~CC [M]~~ <li>Upload the deb package of the compiled Linux kernel to the Linux system of the development board</~~home/orangepi/hello.mod.o~~li>{| class="wikitable" style="width:800px;" |-| ~~LD [M] /home~~test@test:~/orangepi-build$ '''cd output/~~hello.ko~~debs'''

~~make[1]~~test@test: ~~Leaving directory '~~~/~~usr~~orangepi-build/~~src~~output/~~linux-headers-5.10.160-rockchip-rk35xx~~debs$ '''scp \'''

'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb root@192.168.1.xxx:/root'''

|}

</ol>

<li>Then log in to the development board and uninstall the deb package of the installed Linux kernel</li>

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

|-

|

root@orangepi:~# '''apt purge -y linux-image-legacy-rockchip-rk356x'''

|}

</ol>

<li>Install the deb package of the new Linux kernel just uploaded</li>

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

|-

|

root@orangepi:~# '''dpkg -i linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb'''

|}

</ol>

<li>~~After compiling~~Then restart the development board, and then check whether the kernel-related modifications have taken effect</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''reboot'''~~hello~~|}</ol></li></ol><ol start="11" style="list-style-type: decimal;"><li>Other useful information<ol style="list-style-type: lower-alpha;"><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>{| class="wikitable" style="width:800px;" |-| [https://github.com/orangepi-xunlong/orangepi-build/blob/next/external/config/kernel/linux-rockchip-rk3588-legacy.koconfig ''' orangepi-build/external/config/kernel ~~module will be generated~~/linux-rockchip-rk356x-legacy.config''']|}</ol><ol start="2" style="list-style-type: lower-alpha;"><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/rk3588s-orangepi-5.dts '''orangepi-build/kernel/orange-pi-5.10-rk35xx/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dts''']|}</ol></li></ol>

~~orangepi@orangepi:~$ '''ls *.ko'''~~== Compile rootfs ==

~~hello~~# Run the build.kosh script, remember to add sudo permission

~~<ol start~~::{| class="5wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Use the~~ |-| test@test:~/orangepi-build$ '''~~insmod''' command to insert the '''hello~~sudo ./build.kosh''' ~~kernel module into the kernel</li></ol>~~|}

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~$ decimal;"><li>Select '''~~sudo insmod hello.ko~~Rootfs and all deb packages''', then enter</li>

<~~ol start~~div class="6figure" ~~style="list-style-type: lower-alpha;">~~<li>Then use the '''demsg''' command to view the output of the '''hello.ko''' kernel module. If you can see the output below, it means that the '''hello.ko''' kernel module is loaded correctly.</li></ol>

~~orangepi@orangepi~~[[File:~~~$ '''dmesg | grep "Hello"'''~~pi3b-img388.png]]

~~[ 2871.893988] '''Hello Orange Pi~~ </div></ol><ol start="3" style="list-style- ~~init'''~~type: decimal;"><li>Then select the model of the development board</li>

<~~ol start~~div class="7figure" ~~style="list-style-type: lower-alpha;"><li>Use the '''rmmod''' command to uninstall the '''hello.ko''' kernel module</li></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''sudo rmmod hello'''~~pi3b-img380.png]]

~~orangepi@orangepi~~</div></ol><ol start="4" style="list-style-type:~~~$ '''dmesg | grep &quot~~decimal;~~Hello"'''~~"><li>Then select the type of rootfs</li>

[ ~~2871~~[File:pi3b-img389.~~893988~~png] ~~Hello Orange Pi~~ ]</ol><ol start="5" style="list-style-type: decimal;"><li>Then select the type of image<ol style="list-style-type: lower- ~~init~~alpha;"><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</li>

~~[ 3173.800892] '''Hello Orange Pi -- exit'''~~<div class="figure">

~~== Use of the Raspberry PI's 5-inch screen ==~~img390.png]]

~~~~</~~span>=== Assembly method of Raspberry PI 5-inch screen ===~~ ~~<ol style="list-style-type: decimal;"><li>First prepare the required accessories<ol style="list-style-type: lower-alpha;"><li>Raspberry PI 5-inch MIPI LCD display + touch screen</li~~div></ol>

</li></ol>

<li>If you are compiling the image of the server version, you can also choose to compile the Standard version or the Minimal version. The pre-installed software of the Minimal version will be much less than that of the Standard version '''(please do not choose the Minimal version if there is no special requirement, because many things are not pre-installed by default. Some functions may not be available)'''</li>

<~~blockquote>[[File:pi3b-img353.png|306x219px]]</blockquote><ol start~~div class="2figure" ~~style="list-style-type: lower-alpha;"><li>15pin MIPI cable</li></ol~~>

~~<blockquote>~~[[File:pi3b-~~img354~~img391.png~~|276x111px~~]]~~</blockquote><ol start="2" style="list-style-type: decimal;"><li>Then connect the 15pin MIPI cable to the Raspberry PI 5-inch screen in the way shown below (note the orientation of the insulation surface)</li></ol>~~

~~[[File~~</div></ol><ol start="7" style="list-style-type:~~pi3b-img355~~decimal;"><li>If you are compiling the image of the desktop version, you also need to select the type of desktop environment.~~png|294x160px]]~~Currently, Ubuntu Jammy mainly maintains XFCE and Gnome desktops, Ubuntu Focal only maintains XFCE desktops, and Debian Bullseye mainly maintains XFCE and KDE desktops</li>

<~~ol start~~div class="3figure" ~~style="list-style-type: decimal;"><li>Finally connect to the LCD interface of the Orange Pi 3B development board</li></ol~~>

[[File:pi3b-~~img356~~img392.png~~|333x199px~~]]

~~~~</~~span~~div>~~=== Open the Raspberry PI 5~~[[File:pi3b-~~inch screen configuration method ===~~img393.png]]

~~<ol style="list-style-type: decimal;"><li>The Linux image does not open the 5-inch screen of the Raspberry PI by default. If you~~ You can then select additional packages that need to ~~use~~ be installed. Please press the ~~5-inch screen of the Raspberry PI, you need~~ Enter key to ~~open it manually~~skip directly here.~~</li><li>The steps to open the mipi lcd configuration are as follows:<ol style="list-style-type: lower-alpha;"><li>First run '''orangepi-config''', ordinary users remember to add '''sudo''' permission</li></ol></li></ol>~~ ~~orangepi@orangepi:~$ '''sudo orangepi-config'''~~

[[File:pi3b-img394.png]]

</ol>

<li>Then it will start to compile rootfs, and some of the information prompted during compilation are as follows

<li>The type of rootfs</li>

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

|-

|

[ o.k. ] local not found [ Creating new rootfs cache for '''jammy''']

|}

</ol>

<li>~~Then select '''System'''~~The storage path of the compiled rootfs compressed package</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| [~~[File:pi3b-img357~~o.k.~~png|575x272px~~]Target directory [ '''external/cache/rootfs''' ]|}</ol>

<li>~~Then select '''Hardware'''~~The name of the rootfs compressed package generated by compilation</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| [o.k. ] File name [~~File:pi3b~~'''jammy-xfce-~~img358~~arm64.~~png~~f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' ]|~~576x266px]]~~}</ol>

<li>~~Then use~~ The time used for compilation</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Runtime [ '''13 min''' ]|}</ol></li></ol><ol start="9" style="list-style-type: decimal;"><li>View the rootfs compressed package generated by compilation<ol style="list-style-type: lower-alpha;"><li>'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' is the ~~arrow keys on~~ rootfs compressed package, the ~~keyboard to locate~~ meaning of each field of the ~~Rasp~~name is<ol style="list-~~7inch~~style-~~touchscreen~~type: 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, ~~and then~~ this value will not change. The compilation script will use ~~the space button~~ this MD5 hash value to generate Determine whether rootfs needs to ~~check~~be recompiled</li></ol></li><li>'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.list''' lists the package names of all packages installed by rootfs</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''ls external/cache/rootfs/'''

~~[[File:pi3b~~'''jammy-~~img359~~xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.~~png|408x310px]]~~lz4'''

~~<ol start="5" style="list~~jammy-~~style~~xfce-~~type: lower-alpha;"><li>Then select '''<Save>''' to save</li></ol>~~arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.current

~~[[File:pi3b~~jammy-xfce-~~img360~~arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.~~png~~list|~~404x133px]]~~}</ol></li></ol><ol start="10" style="list-style-type: decimal;"><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>

<~~ol start~~span id="~~6" style="list~~compile-~~style~~linux-~~type: lower-alpha;~~image">~~<li>Then select '''<Back>'''</li~~></olspan>

~~[[File:pi3b-img361.png|397x151px]]~~== Compile Linux image ==

~~<ol start="7" style="list-style-type: lower-alpha;"><li>Then select '''<Reboot>''' to restart the system for~~ # Run the ~~configuration~~ build.sh script, remember to ~~take effect</li></ol>~~add sudo permission

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-~~img362~~build$ '''sudo ./build.~~png~~sh'''|~~331x154px]]~~}

<ol start="2" style="list-style-type: decimal;"><li>Select '''The above settings will eventually add the configuration of overlays=raspi-7inch-touchscreen to /boot/orangepiEnv.txt. After setting, you can check it first. If this configuration does not exist, then there is a problem with the settings.Full OS image for flashing''', then enter</li>

~~'''If you find it troublesome to use orangepi-config, you can also use the vim editor to open /boot/orangepiEnv.txt, and then add the configuration of overlays~~<div class=~~raspi-7inch-touchscreen is also possible.'''~~ ~~orangepi@orangepi:~$ '''cat /boot/orangepiEnv.txt | grep~~ "~~raspi~~figure"~~'''~~>

~~'''overlays=raspi~~[[File:pi3b-~~7inch-touchscreen #Sample configuration'''~~img395.png]]

</div></ol>

<li>~~After startup, you can see~~ Then select the ~~lcd screen display as follows:~~model of the development board</li~~></ol~~>

~~[[File:pi3b-img363.png|381x262px]]~~<div class="figure">

~~=== The method of server version image rotation display direction ===~~img380.png]]

~~# Add '''extraargs~~</div></ol><ol start=~~fbcon~~"4" style=~~rotate~~"list-style-type:decimal;"><li>Then select the ~~direction to rotate''' in '''/boot~~type of rootfs</~~orangepiEnv.txt''' This line configuration can set the direction displayed by the server version of the Linux system, where the number after '''fbcon=rotate:''' can be set as:~~li>

[[File:pi3b-img389.png]]</ol><~~!--~~ ol start="5" style="list-style-type: decimal;"><li>Then select the type of image

<li>~~0: normal screen~~ '''Image with console interface (~~default~~ server)''' Indicates the image of the server version, which is ~~landscape)~~relatively small</li><li>~~1: Turn clockwise 90 degrees</li><li>2: Flip 180 degrees</li><li>3: Turn clockwise 270 degrees~~'''Image with desktop environment''' Indicates a image with a desktop, which is relatively large</li~~></ol~~>

~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''~~<div class="figure">

~~overlays=lcd1~~[[File:pi3b-img390.png]]

</div></ol></li></ol><ol start="6" style="list-style-type: decimal;"><li>If you are compiling the image of the server version, you can also choose to compile the Standard version or the Minimal version. The pre-installed software of the Minimal version will be much less than that of the Standard version '''~~extraargs=cma=64M fbcon=rotate:3~~(please do not choose the Minimal version if there is no special requirement, because many things are not pre-installed by default. Some functions may not be available)'''</li>

~~'''Note that if there is the line extraargs~~<div class=~~cma=64M in /boot/orangepiEnv.txt by default, the configuration fbcon=rotate:3 can be added after extraargs=cma=64M (separated by spaces).'''~~"figure">

~~<ol start="2" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Then '''restart''' the Linux system and you can see that the direction displayed on the LCD screen has been rotated</li></ol>~~img391.png]]

<~~span id~~/div></ol><ol start="7" style="~~method~~list-ofstyle-~~rotating-display-and-touch-direction-of-desktop-version-image~~type: decimal;"><~~/span~~li>~~=== Method~~ If you are compiling the image of ~~rotating display and touch direction~~ the desktop version, you also need to select the type of desktop ~~version image ===~~environment. Currently, Ubuntu Jammy mainly maintains XFCE and Gnome desktops, Ubuntu Focal only maintains XFCE desktops, and Debian Bullseye mainly maintains XFCE and KDE desktops</li>

~~# First open '''Display''' Settings in Linux~~<div class="figure">

[[File:pi3b-~~img364~~img392.png~~|298x206px~~]]

~~<ol start="2" style="list-style-type: decimal;"><li>Then select the direction you want to rotate in '''Rotation'''~~</pdiv>~~<ol style="list-style-type~~[[File: ~~lower~~pi3b-~~alpha;"><li>'''None''': no rotation</li><li>'''Left''': rotate left 90 degrees</li><li>'''Inverted''': Flip up and down, which is equivalent to rotating 180 degrees</li><li>'''Right''': rotate right 90 degrees</li></ol></li></ol>~~img393.png]]

~~[[File:pi3b-img365~~You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.~~png|286x180px]]~~

[[File:pi3b-img394.png]]</ol><ol start="38" style="list-style-type: decimal;"><li>~~Then click '''Apply'''~~<~~/li~~p>Then it will start to compile the Linux image. The general process of compilation is as follows</olp> ~~[[File:pi3b-img366.png|330x207px]]~~ <ol ~~start="4"~~ style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then select '''Keep this configuration'''~~Initialize the compilation environment of Ubuntu PC and install the software packages required for the compilation process</li><li>Download the source code of u-boot and Linux kernel (if cached, only update the code)</olli><li>Compile u-boot source code and generate u-boot deb package</li>~~[[File:pi3b~~<li>Compile the Linux source code and generate Linux-~~img367.png|374x210px]]~~related deb packages</li><li>Make the deb package of Linux firmware</li><~~ol start="5" style="list~~li>Make the deb package of the orangepi-~~style~~config tool</li><li>Create a deb package supported by the board</li><li>If you are compiling the desktop image, you will also create desktop-~~type: decimal;"~~related deb packages</li><li>~~At this point~~Check whether the rootfs has been cached, if not, recreate the ~~screen display~~ rootfs, if it has been ~~rotated~~cached, directly decompress and ~~then close~~ use</li><li>Install the ~~'''Display''' program~~previously generated deb package into rootfs</li><li>~~The above steps will only select the display direction~~Make some specific settings for different development boards and different types of images, such as pre-installing additional software packages, modifying system configuration, etc.</li><li>Then make an image file and ~~will not rotate~~ format the ~~direction of~~ partition, the ~~touch. Use~~ default type is ext4</li><li>Then copy the ~~'''set_lcd_rotate.sh''' script~~ configured rootfs to ~~rotate~~ the ~~direction~~ mirrored partition</li><li>Then update initramfs</li><li>Finally, write the bin file of u-boot into the ~~touch.~~ image through the dd command</li></ol></li><li>After compiling the ~~script is set~~image, it the following information will ~~automatically restart, and then you can test whether the touch has been used normally.~~be prompted

<li>~~'''None''': no rotation~~The storage path of the compiled image</li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-| ~~orangepi@orangepi:~$~~ [ o.k. ] Done building [ '''~~set_lcd_rotate~~output/images/Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160/Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160.~~sh none~~img''']|}</ol>

<li>~~'''Left''': rotate left 90 degrees~~Compilation time</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| ~~orangepi@orangepi:~$~~ '''~~set_lcd_rotate~~[ o.k.~~sh left~~] 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</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Repeat Build Options [ '''~~Inverted~~sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=image RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=yes'''~~: Flip up and down, which is equivalent to rotating 180 degrees~~]|}</ol></li></ol>

~~orangepi@orangepi:~$~~ = '''~~set_lcd_rotate.sh inverted~~Android 11 operating system instructions'''=

<~~ol start~~span id="~~4" style="list-style~~supported-~~type: lower~~android-~~alpha;~~versions">~~<li>'''Right''': rotate right 90 degrees~~</~~li></ol~~span>== Supported Android versions ==

~~orangepi@orangepi~~{| class="wikitable" style="width:~$ 800px;text-align: center;"|-|'''Android version'''|'''Kernel version'''|-|'''Android 11'''|'''~~set_lcd_rotate~~Linux4.~~sh right~~19'''|}

~~'''The set_lcd_rotate.sh script mainly does four things:'''~~

~~'''1. Rotate the direction displayed by the framebuffer'''~~== Android Function Adaptation ==

{| class="wikitable" style="width:800px;text-align: center;"|-|'''Functions'''|'~~2. Rotate the direction of the touch~~''Android 11'''|-|'''3USB2. ~~Turn off the boot logo~~0x3'''|'''OK'''|-|'''4USB3. ~~Restart the system~~0x1'''|'''OK'''|-|'''Rotating the touch direction is achieved by adding the line Option "TransformationMatrix" "x x x x x x x x x" to /usr/share/X11/xorg.conf.d/40-libinput.conf Where "x x x x x x x x x" is configured differently for different directionsM.2 NVMe SSD boot'''|'''OK'''~~<ol start="7" style="list~~|-~~style-type: decimal;"><li>Touch rotation reference</li></ol>~~|'''WIFI'''|'''OK'''|-~~https://wiki.ubuntu.com/X/InputCoordinateTransformation~~|'''Bluetooth'''|'''OK'''~~== Instructions for using the switch logo ==~~|'''GPIO（40pin）'''|'''OK'''~~# By default, the switch logo will only be displayed in the desktop version of the system~~|-~~# Set the~~ |'''~~bootlogo~~UART（40pin）''' ~~variable to~~ |'''~~false~~OK''' in |-|'''SPI（40pin）'''~~/boot/orangepiEnv.txt~~|'''OK''' ~~to turn off the switch logo~~|-~~orangepi@orangepi:~$~~ |'''~~vim /boot/orangepiEnv.txt~~I2C（40pin）'''|'''OK'''~~verbosity=1~~|-|'''PWM（40pin）'''|'''~~bootlogo=false~~OK''' ~~<ol start="3" style="list-style~~|-~~type: decimal;"><li>Set the~~ |'''~~bootlogo~~PWM fan interface''' ~~variable to~~ |'''~~true~~OK''' in |-|'''~~/boot/orangepiEnv.txt~~3pin Debugging serial port''' ~~to enable the switch logo</li></ol>~~ ~~orangepi@orangepi:~$~~ |'''~~vim /boot/orangepiEnv.txt~~OK'''|-~~verbosity=1~~|'''EMMC'''|'''~~bootlogo=true~~OK''' ~~<ol start="4" style="list~~|-~~style-type: decimal;"><li>The location of the~~ |'''TF card boot ~~logo image in the Linux system is</li></ol>~~'''|'''OK'''|-|'''~~/usr/share/plymouth/themes/orangepi/watermark.png~~HDMI video'''|'''OK'''~~<ol start="5" style="list~~|-~~style-type: decimal;"><li>After replacing the boot logo picture, you need to run the following command to take effect</li></ol>~~|'''HDMI Audio'''|'''OK'''|-~~orangepi@orangepi:~$~~ |'''~~sudo update-initramfs -u~~LCD'''|'''OK'''~~== How to use the ZFS file system ==~~|'''eDP display'''|'''OK'''|-|'''~~The latest version of Ubuntu20.04, Ubuntu22.04, Debian11 and Debian12 desktop version systems have pre-installed zfs, you can use it directly.~~Gigabit network port''' |'''~~The pre-installed zfs version in Ubuntu20.04 and Ubuntu22.04 desktop systems is 2.1.6.~~OK'''|-|'''~~The pre-installed zfs version in Debian11 and Debian12 desktop systems is 2.1.11.~~Network port status indicator''' |'''~~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.~~OK'''|-~~orangepi@orangepi:~$~~ |'''Headphone playback'''~~lsmod~~ | ~~grep "zfs"~~'''OK'''|-|'''Headphone recording'''~~zfs 2801664 0~~|'''OK'''|-~~zunicode 327680 1 zfs~~|'''LED Light'''|'''OK'''~~zzstd 471040 1 zfs~~|-|'''GPU'''~~zlua 139264 1 zfs~~|'''OK'''|-~~zcommon 69632 1 zfs~~|'''NPU'''|'''OK'''~~znvpair 61440 2 zfs,zcommon~~|-|'''VPU'''~~zavl 16384 1 zfs~~|'''OK'''|-~~icp 221184 1 zfs~~|'''RTC'''|'''OK'''~~spl 77824 6 zfs,icp,zzstd,znvpair,zcommon,zavl~~|}

~~=== How to install ZFS ===~~

~~'''Before installing zfs, please make sure that the Linux image used is the latest version. In addition, if zfs is already installed in the system, it needs to be installed again.'''~~== WIFI connection test method ==

~~Before installing zfs, you need to install the kernel header file first. For the method of installing the kernel header file, please refer to the instructions in the [[\l|~~# First click enter '''~~section on the method of installing the kernel header file~~Setting'''~~]].~~

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::[[File:pi3b-img396.png]]

To solve this problem, we provide a zfs deb package that can be installed normally, which can be downloaded from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''official tool'''] of the development board. Open the '''<~~span class~~ol start="2" style="~~mark~~list-style-type: decimal;">~~official tool~~<~~/span~~li>Then select '''~~, and enter the~~ Network & internet'''~~zfs-related deb package folders used by Ubuntu and Debian systems~~</~~span~~li>~~'''. You can see three types of deb packages: Ubuntu20.04, Ubuntu22.04 and Debian11. Please download the required version.~~

[[File:pi3b-~~img368~~img397.png~~|230x93px~~]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then select '''Wi-Fi'''</li>

~~After downloading the zfs deb packages of the corresponding version, please upload them to the Linux system of the development board~~[[File:pi3b-img398. ~~For~~ png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then turn on the ~~upload method, please refer to~~ '''~~[[\l|the description in the section of the method of uploading files to the Linux system of the development board]].~~Wi-Fi'''switch</li>

[[File:pi3b-img399.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>After ~~the upload is complete, use the~~ turning on '''cdWi-Fi''' ~~command in the command line of the development board Linux system to enter the directory of the deb package~~, ~~and then use the following command to install the deb package of zfs.~~if everything is normal, you can scan for nearby Wi-Fi hotspots</li>

~~orangepi@orangepi~~[[File:~~~$ '''sudo apt install~~ pi3b-img400.png]]</*.deb'''ol><ol start="6" style="list-style-type: decimal;"><li>Then select the Wi-Fi you want to connect to, and the password input interface shown in the figure below will pop up</li>

~~After~~ [[File:pi3b-img401.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Then use the keyboard to enter the ~~installation is complete~~password corresponding to Wi-Fi, and then use the ~~following command~~ mouse to ~~see~~ click the ~~zfs~~Enter button in the virtual keyboard to start connecting to Wi-~~related kernel modules:~~Fi</li>

~~orangepi@orangepi~~[[File:~~~$ '''ls~~ pi3b-img402.png]]</~~lib/modules/5.10.160~~ol><ol start="8" style="list-style-~~rockchip~~type: decimal;"><li>After the Wi-~~rk356x/updates/dkms~~Fi connection is successful, the display is as shown in the figure below:</~~'''~~li>

~~'''icp~~[[File:pi3b-img403.~~ko spl.ko zavl.ko zcommon.ko zfs.ko zlua.ko znvpair.ko zunicode.ko zzstd.ko'''~~png]]</ol>

~~Then restart the Linux system~~ == How to ~~see that the zfs kernel module will be automatically loaded:~~use Wi-Fi hotspot ==

~~orangepi@orangepi:~$~~ # First, please make sure that the Ethernet port is connected to the network cable and can access the Internet normally# Then select '''~~lsmod | grep "zfs"~~Settings'''

~~zfs 2801664 0~~::[[File:pi3b-img396.png]]

~~zunicode 327680 1 zfs~~<ol start="3" style="list-style-type: decimal;"><li>Then select '''Network & internet'''</li>

~~zzstd 471040 1 zfs~~[[File:pi3b-img397.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select '''Hotspot & tethering'''</li>

~~zlua 139264 1 zfs~~[[File:pi3b-img404.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then select '''Wi-Fi hotspot'''</li>

~~zcommon 69632 1 zfs~~[[File:pi3b-img405.png]]</ol><ol start="6" style="list-style-type: decimal;"><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)</li>

~~znvpair 61440 2 zfs~~[[File:pi3b-img406.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>At this time,~~zcommon~~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>

~~zavl 16384 1 zfs~~[[File:pi3b-img407.png]]</ol><ol start="8" style="list-style-type: decimal;"><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>

~~icp 221184 1 zfs~~[[File:pi3b-img408.png]]</ol>

~~spl 77824 6 zfs,icp,zzstd,znvpair,zcommon,zavl~~== Bluetooth test method ==

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. ~~orangepi@orangepi:~$~~ # First click enter '''~~sudo apt install -y zfsutils-linux zfs-dkms~~Setting'''

~~=== Methods of creating ZFS pools ===~~ ~~'''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.'''~~ ~~# First, we can use the '''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:pi3b-~~img369~~img396.png~~|379x227px~~]]

<li>Then ~~enter the following command to create a ZFS pool, including two storage devices, NVMe SSD and U disk</li></ol>~~ ~~orangepi@orangepi:~$~~ select '''~~sudo zpool create -f pool1 /dev/nvme0n1 /dev/sda~~Connected devices'''</li>

[[File:pi3b-img409.png]]

</ol>

<li>Then ~~use the~~ click '''~~zpool list~~Pair new device''' ~~command~~ to ~~see that the system has created a ZFS pool named '''pool1''',~~ turn on Bluetooth and start scanning the ~~size of the ZFS pool pool1 is the size of the NVME SSD plus the size of the U disk~~surrounding Bluetooth devices</li>~~</ol>~~ ~~[[File:pi3b-img370.png|576x37px]]~~

[[File:pi3b-img410.png]]

</ol>

<li>~~Then execute~~ The searched Bluetooth devices will be displayed under '''~~df -h~~Available devices''' ~~to see that '''pool1''' is mounted to the '''/pool1''' directory~~</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img411.png]]</ol><ol start="5" style="list-style-type: decimal;"><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 '''~~df -h~~Pair'''option</li>

~~Filesystem Size Used Avail Use% Mounted~~ [[File:pi3b-img412.png]]</ol><ol start="6" style="list-style-type: decimal;"><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 onthe mobile phone. After clicking the pairing button on the mobile phone, the pairing process will start</li>

~~tmpfs 1~~[[File:pi3b-img413.~~6G 18M 1.6G 2%~~ png]]</ol><ol start="7" style="list-style-type: decimal;"><li>After the pairing is completed, you can see the paired Bluetooth device as shown in the figure below</~~run~~li>

[[File:pi3b-img414.png]]</~~dev/mmcblk0p2 29G 6~~ol><ol start="8" style="list-style-type: decimal;"><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.~~0G 22G 22%~~ </li>

~~tmpfs 7~~[[File:pi3b-img415.~~7G 46M 7.7G 1%~~ png]]</~~dev~~ol><ol start="9" style="list-style-type: decimal;"><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</~~shm~~li>

~~tmpfs 5~~[[File:pi3b-img416.~~0M 4.0K~~ png]]</ol></~~lock~~span>

~~tmpfs 7.7G 944K 7.7G 1% /tmp~~== How to use Raspberry Pi 5-inch screen ==

~~/dev/mmcblk0p1 1022M 115M 908M 12% /boot~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Please make sure that the image used is the following two versions of the image:'''

~~/dev/zram1 188M 4~~'''OrangePi3B_RK3566_Android11_lcd_v1.~~5M 169M 3% /var/log~~x.x.img'''

~~tmpfs 1~~'''OrangePi3B_RK3566_Android11_spi-nvme_lcd_v1.~~6G 80K 1~~x.~~6G 1% /run/user~~x.img'''</~~1000~~big>|}

# The screen needs to be assembled first, please refer to [[Orange Pi 3B#Use of the Raspberry PI's 5-inch screen|''~~pool1 489G 9.3M 489G 1% /pool1~~'the assembly method of the Raspberry Pi 5-inch screen''']]# Connect the Type-C power supply to the board and power it on. After the system starts, you can see the screen display as shown in the figure below

~~<ol start="5" style="list~~::[[File:pi3b-~~style-type: decimal;"><li>Use the following command to see that the file system type of pool1 is zfs</li></ol>~~img417.png]]

~~orangepi@orangepi:~$ '''mount | grep pool1'''~~

~~pool1 on /pool1 type '''zfs''' (rw~~== 40pin interface GPIO,~~xattr~~UART,~~noacl)~~SPI and PWM test ==

<~~ol start~~span id="~~6" style="list~~pin-gpio-port-~~style~~test-~~type: decimal;~~2"><li/span>~~Then we can~~ === 40pin GPIO port test ~~copying a file to the ZFS pool</li></ol>~~===

~~orangepi@orangepi:~$ '''sudo cp -v /usr/local/test.mp4 /pool1/'''~~ ~~'/usr/local/test.mp4' -> '/pool1/test.mp4'~~ ~~=== Test~~ # First click on the ~~data deduplication function of ZFS ===~~ ~~# The data deduplication function of ZFS is disabled by default, we need~~ wiringOP icon to ~~execute~~ open the ~~following command to enable it~~wiringOP APP

~~orangepi@orangepi~~:~~~$ '''sudo zfs set dedup=on pool1'''~~:[[File:pi3b-img418.png]]

<li>~~Then do a simple test, first enter pool1~~The main interface of wiringOP APP is displayed as shown in the figure below, and then ~~execute~~ click the ~~following command to generate a random file with a size of 1G</li></ol>~~ ~~orangepi@orangepi:~$~~ '''~~cd /pool1/~~GPIO_TEST''' ~~root@orangepi:/pool1$ '''sudo dd if=/dev/urandom of=~~button to open the GPIO test~~.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~~interface</sli>

[[File:pi3b-img419.png]]

</ol>

<li>~~Then use~~ 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 40pin pins. When the '''CheckBox''' button is checked, the ~~following command~~ corresponding GPIO pin will be set to ~~copy 1000 random files of size 1G</li></ol>~~ ~~root@orangepi:/pool1$~~ '''~~for ((i=0~~OUT''' mode, and the pin level will be set to high level; ~~i&lt~~when the checkbox is unchecked, the GPIO pin level will be set to low level;~~1000~~When the '''GPIO READALL''' button is pressed, information such as wPi number, GPIO mode, and pin level can be obtained; ~~i++)); do sudo cp test.1g $i.test.1g; done~~when the '''BLINK ALL GPIO'''button is clicked, the program will control the 28 GPIO ports to continuously switch between high and low levels</li>

[[File:pi3b-img420.png]]

</ol>

<li>Then ~~use~~ click the '''~~du -lh~~GPIO READALL''' ~~to see that there are currently 1002G of data in the pool~~button, ~~but in fact the size of~~ the ~~ZFS pool~~ output information is ~~only '''504GB''' (~~as shown in the ~~total capacity of SSD+U disk), which cannot hold such a large amount of data~~figure below:</li~~></ol~~>

~~root@orangepi~~[[File:pi3b-img421.png]]</~~pool1$~~ ol><ol start="5" style="list-style-type: decimal;"><li>There are a total of 28 GPIO ports in the 40pins of the development board that can be used. The following uses pin 7—the corresponding GPIO is GPIO4_A4—the corresponding wPi serial number is 2—as an example to demonstrate how to set the high and low levels of the GPIO port. First click the '''~~du -lh~~CheckBox'''button corresponding to pin 7. When the button is selected, pin 7 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</li>

~~1002G~~[[File:pi3b-img422.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is '''OUT''', and the pin level is high</li>

[[File:pi3b-img423.png]]</ol><ol start="57" style="list-style-type: decimal;"><li>~~Then use~~ Click the '''~~zpool list~~CheckBox''' ~~command~~ button in the figure below again to cancel the check status. Pin 7 will be set to ~~see that only 1~~low level. After setting, you can use a multimeter to measure the voltage value of the pin.~~01G~~ If it is ~~actually occupied, because these 1001 files are all duplicates~~'''0v''', ~~indicating~~ it means that the ~~data deduplication function~~ low level is ~~effective~~set successfully.</li~~></ol~~>

[[File:pi3b-~~img371~~img424.png~~|576x36px~~]]</ol><ol start="8" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is OUT, and the pin level is low</li>

[[File:pi3b-img425.png]]</ol>~~=== Test the data compression function of ZFS ===~~

# 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=== 40pin UART test ===

~~orangepi@orangepi:~$~~ # UART7 and UART9 are enabled by default in Android. The position of the 40pin is shown in the figure below, and the corresponding device nodes are '''cd /~~pool1~~dev/ttyS7'''and '''/dev/ttyS9''' respectively

~~root@orangepi~~:~~/pool1$ '''sudo tar~~ :[[File:pi3b-~~cf text~~img269.~~tar /var/log/ /etc/'''~~png]]

<li>~~Then~~ First click on the ~~file size that can be seen through~~ wiringOP icon to open the ~~'''ls -lh''' command and the space occupied in the ZFS pool are both '''27M'''~~wiringOP APP</li>~~</ol>~~ ~~[[File:pi3b-img372.png|576x90px]]~~

[[File:pi3b-img418.png]]

</ol>

<li>~~Then we enable compression~~ The main interface of wiringOP APP is displayed as shown in the ~~ZFS pool pool1~~figure below, and then click the '''UART_TEST''' button to open the UART test interface</li~~></ol~~>

~~root@orangepi~~[[File:pi3b-img426.png]]</~~pool1$ '''sudo zfs set compression=lz4 pool1'''~~ol><ol start="4" style="list-style-type: decimal;"><li>~~Then execute~~ The serial port test interface of the ~~following command again to package~~ APP is shown in the ~~'''/var/log/''' and '''/etc/''' directories into a tar package~~figure below</li>~~</ol>~~ ~~root@orangepi:/pool1$ '''sudo tar -cf text.tar /var/log/ /etc/'''~~

[[File:pi3b-img427.png]]

</ol>

<li>~~At this time~~Take the test of '''UART7''' as an example below, select the '''/dev/ttyS7''' node in the selection box, enter the baud rate you ~~can see that~~ want to set in the ~~size of~~ edit box, and then click the '''~~text.tar~~OPEN''' ~~file~~ button to open the /dev/ttyS7 node. After the opening is ~~still 27M~~successful, ~~but it only occupies 9.47M in~~ the ~~ZFS pool~~'''OPEN''' button becomes unselectable, ~~indicating that~~ and the ~~file is compressed~~'''CLOSE''' button and '''SEND''' button become selectable</li~~></ol~~>

[[File:pi3b-~~img373~~img428.png~~|576x79px~~]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then use Dupont wire to short the RXD and TXD pins of uart7</li>

[[File:pi3b-img429.png]]</ol><~~span id~~ol start="7" style="~~how-to-shut-down-and~~list-~~restart~~style-~~the-development-board~~type: decimal;"><~~/span~~li>~~== How to shut down~~ Then you can enter a character in the send edit box below, and ~~restart~~ click the ~~development board ==~~'''SEND''' button to start sending</li>

~~# During the running of the Linux system, if the Type~~[[File:pi3b-img430.png]]</ol><ol start="8" style="list-style-~~C power supply~~ type: decimal;"><li>If everything is ~~directly unplugged~~normal, ~~some data may~~ the received string will be ~~lost or damaged~~ displayed in the ~~file system, so please use the '''poweroff''' command to shut down the Linux system of the development board before powering off. Then unplug the power again.~~receiving box</li>

~~orangepi@orangepi~~[[File:~~~$ '''sudo poweroff'''~~pi3b-img431.png]]</ol>

~~<ol start~~=~~"2" style~~=~~"list-style-type: decimal;"><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 shut down.</li></ol>~~= 40pin SPI test ===

~~[[File:pi3b-img374.png|294x80px]]~~# According to the schematic diagram of the 40pin interface, the spi available for Orange Pi 3B is spi3

'''Note that the Linux desktop version system will pop up a confirmation box as shown in the figure below after pressing the switch button, and the system will shut down only after clicking the Shut Down option::[[File:pi3b-img264.~~'''~~png]]

~~[[File~~<ol start="2" style="list-style-type:~~pi3b-img375~~decimal;"><li>Here, the SPI interface is tested through the w25q64 module.~~png|207x193px]]~~First, the w25q64 device is connected to the SPI3 interface</li>

[[File:pi3b-img432.png]]

</ol>

<li>~~Short press~~ Then click the ~~switch button on~~ wiringOP icon to open the ~~development board after shutting down to start up.~~wiringOP APP</li>~~</ol>~~ ~~[[File:pi3b-img374.png|294x80px]]~~

[[File:pi3b-img418.png]]

</ol>

<li>The ~~command~~ main interface of wiringOP APP is displayed as shown in the figure below, click the SPI_TEST button to ~~restart~~ open the ~~Linux system is~~SPI test interface</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''sudo'''~~ pi3b-img433.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then click the '''~~reboot~~OPEN'''button to initialize the SPI</li>

[[File:pi3b-img434.png]]<~~span id~~/ol><ol start="6" style="~~linux~~list-~~sdkorangepi~~style-~~build-instructions~~type: decimal;"><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</~~span~~li>

[[File:pi3b-img435.png]]</ol><ol start="7" style= ~~'''Linux SDK——orangepi~~"list-style-~~build instructions''' =~~type: decimal;"><li>Finally, the APP will display the read ID information</li>

[[File:pi3b-img436.png]]<~~span id~~/ol><ol start="8" style="~~compilation~~list-~~system~~style-~~requirements~~type: decimal;"><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)</~~span~~li>~~== Compilation system requirements ==~~

~~'''We can cross~~[[File:pi3b-~~compile the Linux image of the development board on the x64 computer, or compile the Linux image of the development board on the Ubuntu22~~img437.~~04 system of the development board, please choose one according to your preference.'''~~png]]</ol>

'''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.'''=== 40pin PWM test ===

~~=== Compile with the Ubuntu22.04 system of the development board ===~~figure below

~~# The Linux SDK, namely '''orangepi~~::[[File:pi3b-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 operationsimg438.png]]

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~~~$ '''lsb_release -a'''~~decimal;"><li>First click on the wiringOP icon to open the wiringOP APP</li>

~~No LSB modules are available~~[[File:pi3b-img418.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then click the '''PWM_TEST''' button on the main interface of wiringOP to enter the PWM test interface</li>

~~Distributor ID~~[[File: ~~Ubuntu~~pi3b-img439.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>The base address corresponding to PWM11 is '''fe6f0030''', here pwmchip0 shows '''fdd70020.pwm''' on the right, then you need to click the drop-down option to select other pwmchips until '''febf0030.pwm''' is displayed on the right</li>

~~Description~~[[File: ~~Ubuntu 22~~pi3b-img440.~~04.1 LTS~~png]]</ol><ol start="5" style="list-style-type: decimal;"><li>When the drop-down option selects '''pwmchip3''', the corresponding base address of PWM11 is '''fe6f0030''' on the right</li>

~~Release~~[[File: pi3b-img441.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then confirm the PWM channel, the default is channel 0, and confirm the PWM cycle, the default configuration is '''50000ns''~~22.04~~', converted to PWM frequency is '''20KHz''', you can modify it yourself, click the '''EXPORT''' button to export '''PWM11'''</li>

~~Codename~~[[File: ~~jammy~~pi3b-img442.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Then drag the drag bar below to change the PWM duty cycle, and then check Enable to output the PWM waveform</li>

[[File:pi3b-img443.png]]</ol><ol start="28" style="list-style-type: decimal;"><li>~~'''Since~~ Then use an oscilloscope to measure the ~~source codes such as~~ No. 32 pin in the ~~kernel and U-boot are stored on GitHub, it is very important to ensure that~~ 40pin of the development board , and you can ~~download codes from GitHub normally when compiling~~ see the ~~image.'''~~following waveform</li~~></ol~~>

[[File:pi3b-img444.png]]</ol>~~=== Compile with x64 Ubuntu22.04 computer ===~~

# 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 == How 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.use ADB ==

~~test@test:~$ '''lsb_release~~ === Use network connection adb debugging ===

~~No LSB modules are available~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Using the network adb does not require a data cable to connect the computer and the development board, but to communicate through the network, so first make sure that the wired or wireless network of the development board is connected, and then obtain the IP address of the development board, which will be used later.'''</big>|}

~~Distributor ID: Ubuntu~~# Make sure that the '''service.adb.tcp.port''' of the Android system is set to port number 5555

~~Description~~: ~~Ubuntu 22~~:{| class="wikitable" style="width:800px;" |-| console:/ # '''getprop | grep "adb.~~04 LTS~~tcp"'''

~~Release~~[service.adb.tcp.port]: ['''~~22.04~~5555''']|}

~~Codename~~<ol start="2" style="list-style-type: ~~jammy~~decimal;"><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 start~~{| class="2wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<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~~|-| console:/ # ''' ~~to install an Ubuntu 22.04 virtual machine in the Windows system~~setprop service. 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 WSLadb.~~</li><li>The download address of the installation image of Ubuntu 22~~tcp.~~04 '''amd64~~port 5555''' ~~version is:</li></ol>~~

~~[https~~console:/~~/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~~stop adbd''']

Orconsole:/ # '''start adbd'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Install adb tool on Ubuntu PC</li>

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''~~https://repo.huaweicloud.com/ubuntu-releases/22.04/ubuntu-22.04.1-desktop-amd64.iso~~sudo apt update'''

test@test:~$ '''sudo apt install -y adb'''

|}

</ol>

<li>~~After installing Ubuntu 22.04~~ Then connect network adb 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~~PC~~<ol style="list-style-type: lower-alpha;">~~<li~~>For the method of replacing Tsinghua source, please refer to the instructions on this web page</li></ol></li></ol~~>

~~https~~{| class="wikitable" style="width:~~//mirrors.tuna~~800px;" |-| test@test:~$ '''adb connect 192.~~tsinghua~~168.~~edu~~1.~~cn/help/ubuntu/~~xxx''' '''(The IP address needs to be changed to the IP address of the development board)'''

<~~ol start="2" style="list-style-type~~p>* daemon not running; starting now at tcp: ~~lower-alpha;"><li>Note that the Ubuntu version needs to be switched to 22.04</li>~~5037</olp>

~~[[File:pi3b-img376.png|576x241px]]~~* daemon started successfully

~~<ol start="3" style="list-style-type~~connected to 192.168.1.xxx: ~~lower-alpha;"><li>The content of the '''/etc/apt/sources.list''' file that needs to be replaced is</li></ol>~~5555

~~test@test:~$ '''sudo mv /etc/apt/sources.list /etc/apt/sources.list.bak'''~~

test@test:~$ '''~~sudo vim /etc/apt/sources.list~~adb devices'''

~~# By default, the source image is commented to improve the speed~~ List of ~~apt update, you can uncomment it yourself if necessary~~devices attached

~~deb https://mirrors~~192.~~tuna~~168.~~tsinghua~~1.~~edu.cn~~xxx:5555 device|}</~~ubuntu~~ol><ol start="5" style="list-style-type: decimal;"><li>Then you can log in to the android system through the adb shell on the Ubuntu PC</ ~~jammy main restricted universe multiverse~~li>

~~# deb~~{| class="wikitable" style="width:800px;" |-~~src https~~| test@test:~~//mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse~~~$ '''adb shell'''

~~deb https~~console:/#|}</~~mirrors.tuna.tsinghua.edu.cn~~ol></~~ubuntu/ jammy-updates main restricted universe multiverse~~span>

~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse~~= '''Appendix''' =

~~deb https:~~</~~/mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse~~span>== User Manual Update History ==

~~# deb~~{| class="wikitable" style="width:800px;text-~~src https~~align:~~//mirrors~~center;"|-|'''Version'''|'''Date'''|'''Update Notes'''|-|v0.~~tuna.tsinghua.edu.cn/ubuntu/ jammy~~1|2023-07-~~backports main restricted universe multiverse~~19|initial version|}

~~deb https://mirrors.tuna.tsinghua.edu.cn~~</~~ubuntu/ jammy-security main restricted universe multiverse~~span>== Image Update History ==

~~# deb~~{| class="wikitable" style="width:800px;"|-| style="text-align: center;" | '''Date'''| style="text-~~src https~~align:~~//mirrors~~center;" | '''Update Notes'''|-| style="text-align: center;" | 2023-07-19|Orangepi3b_1.~~tuna~~0.~~tsinghua~~0_debian_bullseye_desktop_xfce_linux5.~~edu~~10.~~cn/ubuntu/ jammy-security main restricted universe multiverse~~160.7z

~~# Pre-release software source, not recommended to enable~~Orangepi3b_1.0.0_ubuntu_jammy_desktop_xfce_linux5.10.160.7z

~~# deb https://mirrors~~Orangepi3b_1.~~tuna~~0.~~tsinghua~~0_ubuntu_focal_desktop_xfce_linux5.~~edu~~10.~~cn/ubuntu/ jammy-proposed main restricted universe multiverse~~160.7z

~~# deb-src https://mirrors~~OrangePi3B_RK3566_Android11_v1.~~tuna~~0.~~tsinghua~~0.~~edu~~tar.~~cn/ubuntu/ jammy-proposed main restricted universe multiverse~~gz

~~<ol start="4" style="list-style-type: lower-alpha;"><li>After the replacement, you need to update the package information and make sure there is no error</li></ol>~~OrangePi3B_RK3566_Android11_lcd_v1.0.0.tar.gz

~~test@test:~$ '''sudo apt update'''~~ ~~<ol start="5" style="list-style-type: lower-alpha;">~~<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> ~~== Get the source code of Linux sdk ==~~ ~~=== Download orangepi-build from github ===~~ # 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: ~~test@test:~$ '''sudo apt-get update'''~~ ~~test@test:~$ '''sudo apt-get install -y git'''~~ ~~test@test:~$ '''git clone https://github.com/orangepi-xunlong/orangepi-build.git -b next'''~~ '''Note that the Orange Pi 3B 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.''' ~~<div class="figure">~~ ~~[[File:pi3b-img377.png|576x298px|图片6]]~~ ~~</div>~~'''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.''' ~~<ol start="2" style="list-style-type: decimal;"><li>The u-boot and Linux kernel versions currently used by the development board are as follows</li></ol>~~ ~~{| class="wikitable"~~|-~~|'''branch'''|'''u-boot version'''|'''Linux Kernel version'''~~|-~~|'''legacy'''|'''u-boot 2017.09'''|'''Linux5.10'''~~|} '''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.'''~~ ~~<ol start="3" style="list-style-type: decimal;"><li>orangepi-build will contain the following files and folders after downloading<ol style="list-style-type: lower-alpha;"><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</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''ls'''~~ ~~'''build.sh external LICENSE''' README.md '''scripts'''~~ '''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.''' ~~=== Download the cross-compilation toolchain ===~~ '''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.''' # When orangepi-build runs for the first time, it will automatically download the cross-compilation toolchain and put it in the '''toolchains''' folder. Every time after running the build.sh script of orangepi-build, it will check whether the cross-compilation toolchain in '''toolchains''' exists , if it does not exist, the download will be restarted, if it exists, it will be used directly, and the download will not be repeated. ~~<div class="figure">~~ ~~[[File:pi3b-img378.png|575x278px|选区_396]]~~ ~~</div><ol start="2" style="list-style-type: decimal;"><li>The image URL of the cross-compilation toolchain in China is the open source software image site of Tsinghua University</li></ol>~~ ~~https://mirrors.tuna.tsinghua.edu.cn/armbian-releases/_toolchain/~~ ~~<ol start="3" style="list-style-type: decimal;"><li>After '''toolchains''' is downloaded, it will contain multiple versions of cross-compilation toolchains, and the development board will only use two of them</li></ol>~~ ~~test@test:~/orangepi-build$ '''ls toolchains/'''~~ ~~gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu~~ ~~gcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf~~ ~~gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu~~ ~~gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf~~ ~~gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabi~~ ~~gcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabihf~~ ~~gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu~~ ~~gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabi~~ ~~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~~ ~~<ol start="4" style="list-style-type: decimal;"><li>The cross-compilation toolchain used to compile the Linux kernel source code is<ol style="list-style-type: lower-alpha;"><li>Linux5.10</li></ol></li></ol>~~ ~~'''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''~~ ~~<ol start="5" style="list-style-type: decimal;"><li>The cross-compilation tool chain used to compile the u-boot source code is<ol style="list-style-type: lower-alpha;"><li>v2017.09</li></ol></li></ol>~~ ~~'''gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu'''~~ ~~=== orangepi-build complete directory structure description ===~~ ~~<ol style="list-style-type: decimal;">~~<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~~<ol style="list-style-type: lower-alpha;"><li>The git repository where the Linux kernel source code is stored is as follows:</li></ol></li></ol>~~ ~~'''https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-5.10-rk35xx'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The git warehouse where the b.u-boot source code is stored is as follows:</li></ol>~~ ~~'''https://github.com/orangepi-xunlong/u-boot-orangepi/tree/v2017.09-rk3588'''~~ ~~<ol start="2" style="list-style-type: decimal;">~~<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 script~~b. '''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. '''kernel''': stores the source code of the Linux kernel, and the folder named orange-pi-5.10-rk35xx stores the kernel source code of the legacy branch of the RK3588/RK3588S/RK3566 series development boards. Please do not manually name the folder name of the kernel source code Modify, if modified, the kernel source code will be re-downloaded when the compilation system is running~~d. '''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 toolchain~~i. '''u-boot''': stores 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/RK3566 series development boards, the name of the folder of the u-boot source code Please do not modify it manually, if it is modified, the u-boot source code will be re-downloaded when the compiling system is running~~j. '''userpatches''': Store configuration files needed to compile scripts</li></ol>~~ ~~test@test:~/orangepi-build$ '''ls'''~~ ~~'''build.sh external kernel LICENSE output''' README.md '''scripts toolchains u-boot userpatches'''~~ ~~== Compile u-boot ==~~ ~~# Run the build.sh script, remember to add sudo permission~~ ~~test@test:~/orangepi-build$ '''sudo ./build.sh'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Select '''U-boot package'''，then enter</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img379.png|576x132px|选区_238]]~~ ~~</div><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img380.png|576x197px|}4$_5F06}}0R4GU8]OVO}4E]]~~ ~~</div><ol start="4" style="list-style-type: decimal;"><li>Then it will start to compile u-boot, and some information prompted during compilation is explained as follows<ol style="list-style-type: lower-alpha;"><li>u-boot source code version</li></ol></li></ol>~~ ~~[ o.k. ] Compiling u-boot [ '''v2017.09''' ]~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The version of the cross-compilation toolchain</li></ol>~~ ~~[ o.k. ] Compiler version [ '''aarch64-linux-gnu-gcc 7.4.1''' ]~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>Path to the generated u-boot deb package</li></ol>~~ ~~[ o.k. ] Target directory [ '''orangepi-build/output/debs/u-boot''' ]~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>The package name of the generated u-boot deb package</li></ol>~~ ~~[ o.k. ] File name [ '''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb''' ]~~ ~~<ol start="5" style="list-style-type: lower-alpha;"><li>Compilation time</li></ol>~~ ~~[ o.k. ] Runtime [ '''1 min''' ]~~ ~~<ol start="6" style="list-style-type: lower-alpha;"><li>Repeat the command to compile u-boot, use the following command to start compiling u-boot directly without selecting through the graphical interface</li></ol>~~ ~~[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=u-boot KERNEL_CONFIGURE=no''' ]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>View the u-boot deb package generated by compilation</li></ol>~~ ~~test@test:~/orangepi-build$ '''ls output/debs/u-boot/'''~~ ~~linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb~~ ~~<ol start="6" style="list-style-type: decimal;"><li>The files contained in the generated u-boot deb package are as follows<ol style="list-style-type: lower-alpha;"><li>Use the following command to decompress the deb package</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''cd output/debs/u-boot'''~~ ~~test@test:~/orangepi_build/output/debs/u-boot$ $ '''dpkg -x''' \~~ ~~'''linux-u-boot-legacy-orangepi3b_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-orangepi3b_1.0.0_arm64.deb '''usr'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The decompressed file is as follows</li></ol>~~ ~~test@test:~/orangepi-build/output/debs/u-boot$ '''tree usr'''~~ ~~usr~~ ~~└── lib~~ ~~├── linux-u-boot-legacy-orangepi3b_1.0.0_arm64~~ ~~│ ├── idbloader.img~~ ~~│ ├── rkspi_loader.img~~ ~~│ └── u-boot.itb~~ ~~└── u-boot~~ ~~├── LICENSE~~ ~~├── orangepi-3b-rk3566_defconfig~~ ~~└── platform_install.sh~~ ~~3 directories, 6 files~~ ~~<ol start="7" style="list-style-type: decimal;">~~<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 '''(This function needs to be fully compiled once u-boot, otherwise it will prompt that the source code of u-boot cannot be found. If the source code compressed package is downloaded from Google cloud disk, there is no such problem, because the source code of u-boot have been cached)''', otherwise the changes made will be reverted, the method is as follows:</li></ol> ~~<blockquote>Set the IGNORE_UPDATES variable in userpatches/config-default.conf to "yes"</blockquote>test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''~~ ~~IGNORE_UPDATES="'''yes'''"~~ ~~<ol start="8" style="list-style-type: decimal;"><li>When debugging u-boot code, you can use the following method to update u-boot in the Linux image for testing<ol style="list-style-type: lower-alpha;"><li>Upload the compiled u-boot deb package to the Linux system of the development board</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''cd output/debs/u-boot'''~~ ~~test@test:~/orangepi_build/output/debs/u-boot$ '''scp \'''~~ ~~'''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb''' [mailto:root@192.168.1.xxx:/root root@192.168.1.xxx:/root]~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>Then log in to the development board and uninstall the deb package of u-boot installed</li></ol>~~ ~~root@orangepi:~# '''apt purge -y linux-u-boot-orangepi3b-legacy'''~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>Install the new u-boot deb package just uploaded</li></ol>~~ ~~root@orangepi:~# '''dpkg -i''' '''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb'''~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>Then run the nand-sata-install script</li></ol>~~ ~~root@orangepi:~# '''nand-sata-install'''~~ ~~<ol start="5" style="list-style-type: lower-alpha;">~~<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</li></ol> ~~[[File:pi3b-img381.png|312x152px]]~~ ~~<ol start="6" style="list-style-type: lower-alpha;"><li>After pressing the Enter key, a Warning will pop up first</li></ol>~~ ~~[[File:pi3b-img382.png|309x168px]]~~ ~~<ol start="7" style="list-style-type: lower-alpha;"><li>Press the Enter key again to start updating u-boot, and the following information will be displayed after the update is completed</li></ol>~~ ~~[[File:pi3b-img383.png|244x137px]]~~ ~~<ol start="8" style="list-style-type: lower-alpha;"><li>Then you can restart the development board to test whether the modification of u-boot takes effect</li></ol>~~ ~~<ol start="9" style="list-style-type: decimal;"><li>Other useful information<ol style="list-style-type: lower-alpha;"><li>In the u-boot 2017.09 source code, the defconfig configuration file used by the development board is</li></ol></li></ol>~~ ~~[https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/configs/orangepi_5_defconfig '''orangepi-build/u-boot/v2017.09-rk3588/configs/orangepi-3b-rk3566_defconfig''']~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>In the u-boot 2017.09 source code, the dts file used by the development board is</li></ol>~~ ~~[https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/arch/arm/dts/rk3588s-orangepi-5.dts orangepi-build/u-boot/v2017.09-rk3588/arch/arm/dts/rk3566-orangepi-3b.dts]~~ ~~== Compile the Linux kernel ==~~ ~~# Run the build.sh script, remember to add sudo permission~~ ~~test@test:~/orangepi-build$ '''sudo ./build.sh'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Select '''Kernel package'''，then enter</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img384.png|575x116px|选区_240]]~~ ~~</div><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img380.png|576x197px|}4$_5F06}}0R4GU8]OVO}4E]]~~ ~~</div><ol start="4" style="list-style-type: decimal;">~~<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.</li></ol> ~~[[File:pi3b-img385.png|576x87px]]~~ ~~<ol start="5" style="list-style-type: decimal;">~~<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</li></ol> ~~[[File:pi3b-img386.png|462x322px]]~~ ~~<ol style="list-style-type: lower-alpha;">~~<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</li></ol> ~~test@test:~/orangepi-build$ '''sudo ./build.sh KERNEL_CONFIGURE=no'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><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</li></ol> ~~[[File:pi3b-img387.png|574x234px]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Part of the information prompted when compiling the kernel source code is as follows<ol style="list-style-type: lower-alpha;"><li>The version of the Linux kernel source code</li></ol></li></ol>~~ ~~[ o.k. ] Compiling current kernel [ '''5.10.160''' ]~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The version of the cross-compilation toolchain used</li></ol>~~ ~~[ o.k. ] Compiler version [ '''aarch64-none-linux-gnu-gcc 11.2.1''' ]~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>The configuration file used by the kernel by default and the path where it is stored</li></ol>~~ ~~[ o.k. ] Using kernel config file [ '''config/kernel/linux-rockchip-rk356x-legacy.config''' ]~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>The path of the deb package related to the kernel generated by compiling</li></ol>~~ ~~[ o.k. ] Target directory [ '''orangepi-build/output/debs/''' ]~~ ~~<ol start="5" style="list-style-type: lower-alpha;"><li>The package name of the compiled kernel image deb package</li></ol>~~ ~~[ o.k. ] File name [ '''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb''' ]~~ ~~<ol start="6" style="list-style-type: lower-alpha;"><li>The time used for compilation</li></ol>~~ ~~[ o.k. ] Runtime [ '''5 min''' ]~~ ~~<ol start="7" style="list-style-type: lower-alpha;">~~<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</li></ol> ~~[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=kernel KERNEL_CONFIGURE=no''' ]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>View the deb package related to the kernel generated by compilation<ol style="list-style-type: lower-alpha;"><li>'''linux-dtb-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Contains dtb files used by the kernel</li><li>'''linux-headers-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Include kernel header files</li><li>'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Contains kernel images and kernel modules</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''ls output/debs/linux-*'''~~ ~~output/debs/linux-dtb-legacy-rockchip-rk356x_1.0.0_arm64.deb output/debs/linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb~~ ~~output/debs/linux-headers-legacy-rockchip-rk356x_1.0.0_arm64.deb~~ ~~<ol start="8" style="list-style-type: decimal;"><li>The files contained in the generated Linux-image deb package are as follows<ol style="list-style-type: lower-alpha;"><li>Use the following command to decompress the deb package</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''cd output/debs'''~~ ~~test@test:~/orangepi_build/output/debs$ '''mkdir test'''~~ ~~test@test:~/orangepi_build/output/debs$ '''cp \'''~~ ~~'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb test/'''~~ ~~test@test:~/orangepi_build/output/debs$ '''cd test'''~~ ~~test@test:~/orangepi_build/output/debs/test$ '''dpkg -x \'''~~ ~~'''linux-image-legacy-rockchip~~OrangePi3B_RK3566_Android11_spi-~~rk356x_1~~nvme_v1.0~~.0_arm64.deb .'''~~ ~~test@test:~/orangepi_build/output/debs/test$ '''ls'''~~ ~~'''boot etc lib''' linux-image-legacy-rockchip-rk356x_1~~.0~~.0_arm64.deb '''usr'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The decompressed file is as follows</li></ol>~~ ~~test@test:~/orangepi-build/output/debs/test$ '''tree -L 2'''~~ . ~~├── boot~~ ~~│ ├── config-5.10.160-rockchip-rk356x~~ ~~│ ├── System.map-5.10.160-rockchip-rk356x~~ ~~│ └── vmlinuz-5.10.160-rockchip-rk356x~~ ~~├── etc~~ ~~│ └── kernel~~ ~~├── lib~~ ~~│ └── modules~~ ~~├── linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb~~ ~~└── usr~~ ~~├── lib~~ ~~└── share~~ ~~<ol start="9" style="list-style-type: decimal;">~~<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 cloud disk, there is no such problem, because the source code of Linux has been cached)''', otherwise the The changes made will be reverted as follows:</li></ol> ~~<blockquote>Set the IGNORE_UPDATES variable in '''userpatches/config-default.conf''' to "yes"</blockquote>test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''~~ ~~IGNORE_UPDATES="'''yes'''"~~ ~~<ol start="10" style="list-style-type: decimal;"><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<ol style="list-style-type: lower-alpha;"><li>Upload the deb package of the compiled Linux kernel to the Linux system of the development board</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''cd output/debs'''~~ ~~test@test:~/orangepi-build/output/debs$ '''scp \'''~~ ~~'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb root@192.168.1.xxx:/root'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>Then log in to the development board and uninstall the deb package of the installed Linux kernel</li></ol>~~ ~~root@orangepi:~# '''apt purge -y linux-image-legacy-rockchip-rk356x'''~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>Install the deb package of the new Linux kernel just uploaded</li></ol>~~ ~~root@orangepi:~# '''dpkg -i linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb'''~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>Then restart the development board, and then check whether the kernel-related modifications have taken effect</li></ol>~~ ~~root@orangepi:~# '''reboot'''~~ ~~<ol start="11" style="list-style-type: decimal;"><li>Other useful information<ol style="list-style-type: lower-alpha;"><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></ol></li></ol>~~ ~~[https://github.com/orangepi-xunlong/orangepi-build/blob/next/external/config/kernel/linux-rockchip-rk3588-legacy.config orangepi-build/external/config/kernel/linux-rockchip-rk356x-legacy.config]~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The location of the dts file used by the development board is</li></ol>~~ [https://github.com/orangepi-xunlong/linux-orangepi/blob/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5.dts orangepi-build/kernel/orange-pi-5.10-rk35xx/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dts] ~~== Compile rootfs ==~~ ~~# Run the build.sh script, remember to add sudo permission~~ ~~test@test:~/orangepi-build$ '''sudo ./build.sh'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Select '''Rootfs and all deb packages'''，then enter</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img388.png|576x119px|选区_241]]~~ ~~</div><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img380.png|576x197px|}4$_5F06}}0R4GU8]OVO}4E]]~~ ~~</div><ol start="4" style="list-style-type: decimal;"><li>Then select the type of rootfs</li></ol>~~ ~~[[File:pi3b-img389.png|575x86px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>Then select the type of image<ol style="list-style-type: lower-alpha;"><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</li></ol></li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img390.png|576x75px|选区_245]]~~ ~~</div><ol start="6" style="list-style-type: decimal;">~~<li>If you are compiling the image of the server version, you can also choose to compile the Standard version or the Minimal version. The pre-installed software of the Minimal version will be much less than that of the Standard version '''(please do not choose the Minimal version if there is no special requirement, because many things are not pre-installed by default. Some functions may not be available)'''</li></ol> ~~<div class="figure">~~ ~~[[File:pi3b-img391.png|576x78px|选区_397]]~~ ~~</div><ol start="7" style="list-style-type: decimal;">~~<li>If you are compiling the image of the desktop version, you also need to select the type of desktop environment. Currently, Ubuntu Jammy mainly maintains XFCE and Gnome desktops, Ubuntu Focal only maintains XFCE desktops, and Debian Bullseye mainly maintains XFCE and KDE desktops</li></ol> ~~<div class="figure">~~ ~~[[File:pi3b-img392.png|575x99px|Selection_001]]~~ ~~</div>[[File:pi3b-img393.png|576x74px]]~~ ~~You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.~~ ~~[[File:pi3b-img394.png|575x264px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>Then it will start to compile rootfs, and some of the information prompted during compilation are as follows<ol style="list-style-type: lower-alpha;"><li>The type of rootfs</li></ol></li></ol>~~ ~~[ o.k. ] local not found [ Creating new rootfs cache for '''jammy''']~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The storage path of the compiled rootfs compressed package</li></ol>~~ ~~[ o.k. ] Target directory [ '''external/cache/rootfs''' ]~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>The name of the rootfs compressed package generated by compilation</li></ol>~~ ~~[ o.k. ] File name [ '''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' ]~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>The time used for compilation</li></ol>~~ ~~[ o.k. ] Runtime [ '''13 min''' ]~~ ~~<ol start="9" style="list-style-type: decimal;"><li>View the rootfs compressed package generated by compilation<ol style="list-style-type: lower-alpha;"><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;"><li>'''jammy''' indicates the type of Linux distribution of rootfs</li><li>'''xfce''' means rootfs is the type of desktop version, if it is '''cli''', it means the type of server version</li><li>'''arm64''' represents the architecture type of rootfs</li>~~<li>'''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</li></ol></li></ol>~~ ~~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~~ ~~<ol start="10" style="list-style-type: decimal;">~~<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> ~~== Compile Linux image ==~~ ~~# Run the build.sh script, remember to add sudo permission~~ ~~test@test:~/orangepi-build$ '''sudo ./build.sh'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Select '''Full OS image for flashing'''，then enter</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img395.png|576x128px|选区_242]]~~ ~~</div><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img380.png|576x197px|}4$_5F06}}0R4GU8]OVO}4E]]~~ ~~</div><ol start="4" style="list-style-type: decimal;"><li>Then select the type of rootfs</li></ol>~~ ~~[[File:pi3b-img389.png|575x86px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>Then select the type of image<ol style="list-style-type: lower-alpha;"><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</li></ol></li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img390.png|576x75px|选区_245]]~~ ~~</div><ol start="6" style="list-style-type: decimal;">~~<li>If you are compiling the image of the server version, you can also choose to compile the Standard version or the Minimal version. The pre-installed software of the Minimal version will be much less than that of the Standard version '''(please do not choose the Minimal version if there is no special requirement, because many things are not pre-installed by default. Some functions may not be available)'''</li></ol> ~~<div class="figure">~~ ~~[[File:pi3b-img391.png|569x77px|选区_397]]~~ ~~</div><ol start="7" style="list-style-type: decimal;">~~<li>If you are compiling the image of the desktop version, you also need to select the type of desktop environment. Currently, Ubuntu Jammy mainly maintains XFCE and Gnome desktops, Ubuntu Focal only maintains XFCE desktops, and Debian Bullseye mainly maintains XFCE and KDE desktops</li></ol> ~~<div class="figure">~~ ~~[[File:pi3b-img392.png|575x99px|Selection_001]]~~ ~~</div>[[File:pi3b-img393.png|576x74px]]~~ ~~You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.~~ ~~[[File:pi3b-img394.png|575x264px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>Then it will start to compile the Linux image. The general process of compilation is as followsa. Initialize the compilation environment of Ubuntu PC and install the software packages required for the compilation processb. Download the source code of u-boot and Linux kernel (if cached, only update the code)c. Compile u-boot source code and generate u-boot deb packaged. Compile the Linux source code and generate Linux-related deb packagese. Make the deb package of Linux firmwaref. Make the deb package of the orangepi-config toolg. Create a deb package supported by the boardh. If you are compiling the desktop image, you will also create desktop-related deb packagesi. Check whether the rootfs has been cached, if not, recreate the rootfs, if it has been cached, directly decompress and usej. Install the previously generated deb package into rootfsk. Make some specific settings for different development boards and different types of images, such as pre-installing additional software packages, modifying system configuration, etc.l. Then make an image file and format the partition, the default type is ext4m. Then copy the configured rootfs to the mirrored partitionn. Then update initramfso. Finally, write the bin file of u-boot into the image through the dd command</li><li>After compiling the image, the following information will be prompted<ol style="list-style-type: lower-alpha;"><li>The storage path of the compiled image</li></ol></li></ol>~~ ~~[ o.k. ] Done building [ '''output/images/Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160/Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160.img''' ]~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>Compilation time</li></ol>~~ ~~'''[ o.k. ] Runtime [ 19 min ]'''~~ ~~<ol style="list-style-type: lower-alpha;"><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</li></ol>~~ ~~[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=image RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=yes''' ]~~ ~~~~ ~~= '''Android 11 operating system instructions''' =~~ ~~== Supported Android versions ==~~ ~~{| class="wikitable"~~|-~~|'''Android version'''|'''Kernel version'''~~|-~~|'''Android 11'''|'''Linux4.19'''~~|} ~~== Android Function Adaptation ==~~ ~~{| class="wikitable"~~|-~~|'''Functions'''|'''Android 11'''~~|-~~|'''USB2.0x3'''|'''OK'''~~|-~~|'''USB3.0x1'''|'''OK'''~~|-~~|'''M.2 NVMe SSD boot'''|'''OK'''~~|-~~|'''WIFI'''|'''OK'''~~|-~~|'''Bluetooth'''|'''OK'''~~|-~~|'''GPIO（40pin）'''|'''OK'''~~|-~~|'''UART（40pin）'''|'''OK'''~~|-~~|'''SPI（40pin）'''|'''OK'''~~|-~~|'''I2C（40pin）'''|'''OK'''~~|-~~|'''PWM（40pin）'''|'''OK'''~~|-~~|'''PWM fan interface'''|'''OK'''~~|-~~|'''3pin Debugging serial port'''|'''OK'''~~|-~~|'''EMMC'''|'''OK'''~~|-~~|'''TF card boot'''|'''OK'''~~|-~~|'''HDMI video'''|'''OK'''~~|-~~|'''HDMI Audio'''|'''OK'''~~|-~~|'''LCD'''|'''OK'''~~|-~~|'''eDP display'''|'''OK'''~~|-~~|'''Gigabit network port'''|'''OK'''~~|-~~|'''Network port status indicator'''|'''OK'''~~|-~~|'''Headphone playback'''|'''OK'''~~|-~~|'''Headphone recording'''|'''OK'''~~|-~~|'''LED Light'''|'''OK'''~~|-~~|'''GPU'''|'''OK'''~~|-~~|'''NPU'''|'''OK'''~~|-~~|'''VPU'''|'''OK'''~~|-~~|'''RTC'''|'''OK'''~~|} ~~== WIFI connection test method ==~~ ~~# First click enter '''Setting'''~~ ~~[[File:pi3b-img396.png|549x228px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Then select '''Network & internet'''</li></ol>~~ ~~[[File:pi3b-img397.png|565x120px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then select '''Wi-Fi'''</li></ol>~~ ~~[[File:pi3b-img398.png|561x99px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then turn on the '''Wi-Fi''' switch</li></ol>~~ ~~[[File:pi3b-img399.png|560x167px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>After turning on '''Wi-Fi''', if everything is normal, you can scan for nearby Wi-Fi hotspots</li></ol>~~ ~~[[File:pi3b-img400.png|561x166px]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Then select the Wi-Fi you want to connect to, and the password input interface shown in the figure below will pop up</li></ol>~~ ~~[[File:pi3b-img401.png|553x237px]]~~ ~~<ol start="7" style="list-style-type: decimal;"><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</li></ol>~~ ~~[[File:pi3b-img402.png|553x232px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>After the Wi-Fi connection is successful, the display is as shown in the figure below:</li></ol>~~ ~~[[File:pi3b-img403.png|558x102px]]~~ ~~== How to use Wi-Fi hotspot ==~~ ~~# First, please make sure that the Ethernet port is connected to the network cable and can access the Internet normally# Then select '''Settings'''~~ ~~[[File:pi3b-img396.png|549x228px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then select '''Network & internet'''</li></ol>~~ ~~[[File:pi3b-img397.png|565x120px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then select '''Hotspot & tethering'''</li></ol>~~ ~~[[File:pi3b-img404.png|549x173px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>Then select '''Wi-Fi hotspot'''</li></ol>~~ ~~[[File:pi3b-img405.png|548x104px]]~~ ~~<ol start="6" style="list-style-type: decimal;">~~<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)</li></ol> ~~[[File:pi3b-img406.png|551x158px]]~~ ~~<ol start="7" style="list-style-type: decimal;">~~<li>At this time, 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:pi3b-img407.png|313x238px]]~~ ~~<ol start="8" style="list-style-type: decimal;">~~<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:pi3b-img408.png|327x165px]]~~ ~~== Bluetooth test method ==~~ ~~# First click enter '''Setting'''~~ ~~[[File:pi3b-img396.png|549x228px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Then select '''Connected devices'''</li></ol>~~ ~~[[File:pi3b-img409.png|547x115px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then click '''Pair new device''' to turn on Bluetooth and start scanning the surrounding Bluetooth devices</li></ol>~~ ~~[[File:pi3b-img410.png|547x126px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>The searched Bluetooth devices will be displayed under '''Available devices'''</li></ol>~~ ~~[[File:pi3b-img411.png|559x279px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><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</li></ol>~~ ~~[[File:pi3b-img412.png|522x212px]]~~ ~~<ol start="6" style="list-style-type: decimal;">~~<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</li></ol> ~~[[File:pi3b-img413.png|236x273px]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>After the pairing is completed, you can see the paired Bluetooth device as shown in the figure below</li></ol>~~ ~~[[File:pi3b-img414.png|545x178px]]~~ ~~<ol start="8" style="list-style-type: decimal;">~~<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.</li></ol> ~~[[File:pi3b-img415.png|559x238px]]~~ ~~<ol start="9" style="list-style-type: decimal;"><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</li></ol>~~ ~~[[File:pi3b-img416.png|573x97px]]~~ ~~== How to use Raspberry Pi 5-inch screen ==~~ ~~'''Please make sure that the image used is the following two versions of the image:'''~~ ~~'''OrangePi3B_RK3566_Android11_lcd_v1.x.x.img'''~~ ~~'''OrangePi3B_RK3566_Android11_spi-nvme_lcd_v1.x.x.img'''~~ ~~# The screen needs to be assembled first, please refer to [[\l|'''the assembly method of the Raspberry Pi 5-inch screen''']]# Connect the Type-C power supply to the board and power it on. After the system starts, you can see the screen display as shown in the figure below~~ ~~[[File:pi3b-img417.png|516x332px]]~~ ~~== 40pin interface GPIO, UART, SPI and PWM test ==~~ ~~=== 40pin GPIO port test ===~~ ~~# First click on the wiringOP icon to open the wiringOP APP~~ ~~[[File:pi3b-img418.png|576x210px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><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</li></ol>~~ ~~[[File:pi3b-img419.png|575x148px]]~~ ~~<ol start="3" style="list-style-type: decimal;">~~<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 40pin 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 wPi number, GPIO mode, and pin level can be obtained; when the '''BLINK ALL GPIO''' button is clicked, the program will control the 28 GPIO ports to continuously switch between high and low levels</li></ol> ~~[[File:pi3b-img420.png|576x303px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button, the output information is as shown in the figure below:</li></ol>~~ ~~[[File:pi3b-img421.png|575x323px]]~~ ~~<ol start="5" style="list-style-type: decimal;">~~<li>There are a total of 28 GPIO ports in the 40pins of the development board that can be used. The following uses pin 7—the corresponding GPIO is GPIO4_A4—the corresponding wPi serial number is 2—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 7. When the button is selected, pin 7 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</li></ol> ~~[[File:pi3b-img422.png|241x326px]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is '''OUT''', and the pin level is high</li></ol>~~ ~~[[File:pi3b-img423.png|574x301px]]~~ ~~<ol start="7" style="list-style-type: decimal;">~~<li>Click the '''CheckBox''' button in the figure below again to cancel the check status. Pin 7 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.</li></ol> ~~[[File:pi3b-img424.png|250x345px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is OUT, and the pin level is low</li></ol>~~ ~~[[File:pi3b-img425.png|576x300px]]~~ ~~=== 40pin UART test ===~~ ~~# UART7 and UART9 are enabled by default in Android. The position of the 40pin is shown in the figure below, and the corresponding device nodes are '''/dev/ttyS7''' and '''/dev/ttyS9''' respectively~~ ~~[[File:pi3b-img269.png|376x92px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>First click on the wiringOP icon to open the wiringOP APP</li></ol>~~ ~~[[File:pi3b-img418.png|576x210px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><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</li></ol>~~ ~~[[File:pi3b-img426.png|575x156px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>The serial port test interface of the APP is shown in the figure below</li></ol>~~ ~~[[File:pi3b-img427.png|576x324px]]~~ ~~<ol start="5" style="list-style-type: decimal;">~~<li>Take the test of '''UART7''' as an example below, select the '''/dev/ttyS7''' 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/ttyS7 node. After the opening is successful, the '''OPEN''' button becomes unselectable, and the '''CLOSE''' button and '''SEND''' button become selectable</li></ol> ~~[[File:pi3b-img428.png|574x166px]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Then use Dupont wire to short the RXD and TXD pins of uart7</li></ol>~~ ~~[[File:pi3b-img429.png|418x103px]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>Then you can enter a character in the send edit box below, and click the '''SEND''' button to start sending</li></ol>~~ ~~[[File:pi3b-img430.png|575x161px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>If everything is normal, the received string will be displayed in the receiving box</li></ol>~~ ~~[[File:pi3b-img431.png|574x164px]]~~ ~~=== 40pin SPI test ===~~ ~~# According to the schematic diagram of the 40pin interface, the spi available for Orange Pi 3B is spi3~~ ~~[[File:pi3b-img264.png|577x193px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Here, the SPI interface is tested through the w25q64 module. First, the w25q64 device is connected to the SPI3 interface</li></ol>~~ ~~[[File:pi3b-img432.png|373x215px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then click the wiringOP icon to open the wiringOP APP</li></ol>~~ ~~[[File:pi3b-img418.png|576x210px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><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</li></ol>~~ ~~[[File:pi3b-img433.png|574x149px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>Then click the '''OPEN''' button to initialize the SPI</li></ol>~~ ~~[[File:pi3b-img434.png|576x241px]]~~ ~~<ol start="6" style="list-style-type: decimal;"><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</li></ol>~~ ~~[[File:pi3b-img435.png|572x216px]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>Finally, the APP will display the read ID information</li></ol>~~ ~~[[File:pi3b-img436.png|575x296px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><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)</li></ol>~~ ~~[[File:pi3b-img437.png|374x126px]]~~ ~~=== 40pin PWM test ===~~ ~~# Android enables '''PWM11''' by default, and the corresponding pin is located at 40pin as shown in the figure below~~ ~~[[File:pi3b-img438.png|334x107px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>First click on the wiringOP icon to open the wiringOP APP</li></ol>~~ ~~[[File:pi3b-img418.png|576x210px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then click the '''PWM_TEST''' button on the main interface of wiringOP to enter the PWM test interface</li></ol>~~ ~~[[File:pi3b-img439.png|575x150px]]~~ ~~<ol start="4" style="list-style-type: decimal;">~~<li>The base address corresponding to PWM11 is '''fe6f0030''', here pwmchip0 shows '''fdd70020.pwm''' on the right, then you need to click the drop-down option to select other pwmchips until '''febf0030.pwm''' is displayed on the right</li></ol> ~~[[File:pi3b-img440.png|576x178px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>When the drop-down option selects '''pwmchip3''', the corresponding base address of PWM11 is '''fe6f0030''' on the right</li></ol>~~ ~~[[File:pi3b-img441.png|574x161px]]~~ ~~<ol start="6" style="list-style-type: decimal;">~~<li>Then confirm the PWM channel, the default is channel 0, and confirm the PWM cycle, the default configuration is '''50000ns''', converted to PWM frequency is '''20KHz''', you can modify it yourself, click the '''EXPORT''' button to export '''PWM11'''</li></ol> ~~[[File:pi3b-img442.png|575x160px]]~~ ~~<ol start="7" style="list-style-type: decimal;"><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:pi3b-img443.png|575x167px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>Then use an oscilloscope to measure the No. 32 pin in the 40pin of the development board, and you can see the following waveform</li></ol>~~ ~~[[File:pi3b-img444.png|460x276px]]~~ ~~== How to use ADB ==~~ ~~=== Use network connection adb debugging ===~~ '''Using the network adb does not require a data cable to connect the computer and the development board, but to communicate through the network, so first make sure that the wired or wireless network of the development board is connected, and then obtain the IP address of the development board, which will be used later.''' ~~# Make sure that the '''service.adb.tcp.port''' of the Android system is set to port number 5555~~ ~~console:/ # '''getprop | grep "adb.tcp"'''~~ ~~[service.adb.tcp.port]: ['''5555''']~~ ~~<ol start="2" style="list-style-type: decimal;"><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>~~ ~~console:/ # '''setprop service.adb.tcp.port 5555'''~~ ~~console:/ # '''stop adbd'''~~ ~~console:/ # '''start adbd'''~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Install adb tool on Ubuntu PC</li></ol>~~ ~~test@test:~$ '''sudo apt update'''~~ ~~test@test:~$ '''sudo apt install -y adb'''~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then connect network adb on Ubuntu PC</li></ol>~~ ~~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~~gz

~~<ol start="5" style="list-style-type: decimal;"><li>Then you can log in to the android system through the adb shell on the Ubuntu PC</li></ol>~~ ~~test@test:~$ '''adb shell'''~~ ~~console:/ #~~ ~~~~ ~~= '''Appendix''' =~~ ~~== User Manual Update History ==~~ ~~{| class="wikitable"~~|-~~|'''Version'''|'''Date'''|'''Update Notes'''~~|-~~|v0.1|2023-07-19|initial version~~|} ~~== Image Update History ==~~ ~~{| class="wikitable"~~|-~~| '''Date'''| '''Update Notes'''~~|-~~| 2023-07-19| Orangepi3 b_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160.7z~~ ~~Orange pi3b_1.0.0_ubuntu_jammy_desktop_xfce_linux5.10.160.7z~~ ~~Orange pi3b_1.0.0_ubuntu_focal_desktop_xfce_linux5.10.160.7z~~ ~~OrangePi3B_RK3566_Android11_v1.0.0.tar.gz~~ ~~OrangePi3B_RK3566_Android11_lcd_v1.0.0.tar.gz~~ ~~OrangePi3B_RK3566_Android11_spi~~OrangePi3B_RK3566_Android11_lcd_spi-nvme_v1.0.0.tar.gz

~~O rangePi3B_RK3566_Android11_lcd_spi-nvme_v1.0.0.tar.gz~~

* initial version

|}

Admin

Bureaucrats, Administrators

8,367

edits

Wiki-Orange Pi β

Changes

Orange Pi 3B

Wiki-Orange Pi ^β