Changes

← Older edit

Orange Pi 3B

36,023 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>

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

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

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

<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

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~/~~dev/zram1 194M 9.9M 170M 6% /var/log~~Desktop$ '''lspci'''

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

~~tmpfs 769M 48K 769M 1%~~ 01:00.0 Non-Volatile memory controller: Realtek Semiconductor Co., Ltd. Device 5765 (rev 01)|}</~~run~~ol><ol start="6" style="list-style-type: decimal;"><li>The balenaEtcher has been pre-installed in the Linux image, and the opening method is as follows:</~~user/0~~li>

<~~ol start~~div class="2figure" ~~style="list-style-type: lower-alpha;"><li>2TB NVMe SSD</li></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''df~~ pi3b-~~h'''~~img89.png]]

~~Filesystem Size Used Avail Use% Mounted~~ </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 onhow to download and install the arm64 version of balenaEtcher.'''</big>|}</ol><ol start="7" style="list-style-type: decimal;"><li>The interface after balenaEtcher is opened is as follows:</li>

~~udev 3.8G 8.0K 3.8G 1% /dev~~<div class="figure">

~~tmpfs 769M 1~~[[File:pi3b-img90.~~4M 768M 1% /run~~png]]

</div></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 '''~~/dev/nvme0n1p2 1.9T 4.1G 1.8T 1% /~~Flash from file'''</li>

~~tmpfs 3.8G 0 3.8G 0% /dev/shm~~<div class="figure">

~~tmpfs 5~~[[File:pi3b-img91.~~0M 4.0K 5.0M 1% /run/lock~~png]]

</~~dev~~div></~~zram2 3~~ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then enter the '''/usr/lib/Linux-u-boot-legacy-orangepi3b_1.x.~~7G 76K 3~~x_arm64''' directory, select '''rkspi_loader.~~5G 1%~~ img''', and click '''Open''' to open</~~tmp~~li>

~~'''/dev/nvme0n1p1 256M 90M 166M 36% /boot'''~~<div class="figure">

~~/dev/zram1 194M 15M 165M 9% /var/log~~[[File:pi3b-img92.png]]

~~tmpfs 769M 60K 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:</~~1000~~li>

~~tmpfs 769M 48K 769M 1%~~ [[File:pi3b-img93.png]]</~~run~~ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then click '''Select target'''</~~user/0~~li>

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

~~orangepi@orangepi~~[[File:~~~$ '''sudo fix_mmc_ssd~~pi3b-img94.~~sh'''~~png]]

</div></ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then click '''~~Exactly the same system means that the image name is exactly the same. Even if they are all Debian11 systems, the versions are different.~~Show 2 hidden'''to open more options for storage devices</li>

<~~span id~~div class="~~how-to-use-balenaetcher-software-to-burn~~figure">~~=== How to use balenaEtcher software to burn ===~~

~~<ol style="list-style-type: decimal;">~~<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~~[[File: ~~lower~~pi3b-~~alpha;"><li>The M~~img95.~~2 2230 SSD is as follows</li></ol></li></ol>~~png]]

~~[[File~~</div></ol><ol start="6" style="list-style-type:~~pi3b~~lower-~~img73.png|189x136px]]~~alpha;"><li>Then select the device name of SPI Flash '''/dev/mtdblock0''', and click '''Select'''</li>

<~~ol start~~div class="2figure" ~~style="list-style-type: lower-alpha;"><li>The M.2 2242 SSD is as follows</li></ol~~>

[[File:pi3b-~~img74~~img96.png~~|238x129px~~]]

</div></ol><ol start="27" style="list-style-type: ~~decimal~~lower-alpha;"><li>Then ~~insert the NVMe SSD into the M.2 PCIe interface of the development board and fix it~~click '''Flash'''</li~~></ol~~>

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

~~<ol start="3" style="list~~[[File:pi3b-~~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>~~img97.png]]

~~[[File~~</div></ol><ol start="8" style="list-style-type:~~pi3b~~lower-~~img76.png|261x198px]]~~alpha;"><li>Then click '''Yes, I'm sure'''</li>

<~~ol start~~div class="4figure" ~~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. For the method of burning the Linux image to the TF card, please refer to the instructions in the two sections of [[\l|'''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, 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</li></ol>

~~orangepi@orangepi~~[[File:~~~/Desktop$ '''sudo fdisk~~ pi3b-~~l | grep "nvme0n1"'''~~img98.png]]

~~Disk~~ </~~dev~~div></~~nvme0n1~~ol><ol start="9" style="list-style-type: ~~1.86 TiB~~lower-alpha;"><li>Then enter the password '''orangepi''' of the development board Linux system, ~~2048408248320 bytes, 4000797360 sectors~~and it will start burning the u-boot image into the SPI Flash</li>

~~Use the '''lspci''' command to see an NVMe-related PCI device~~ ~~orangepi@orangepi:~/Desktop$ '''lspci'''~~<div class="figure">

00[[File:00pi3b-img99.~~0 PCI bridge: Fuzhou Rockchip Electronics Co., Ltd Device 3566 (rev 01)~~png]]

~~01:00.0 Non-Volatile memory controller: Realtek Semiconductor Co., Ltd. Device 5765 (rev 01)~~</div></ol><ol start="610" style="list-style-type: ~~decimal~~lower-alpha;"><li>The ~~balenaEtcher has been pre-installed in~~ display of the ~~Linux image, and 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~~>

~~[[File:pi3b-img93.png|379x181px]]~~<div class="figure">

[[File:pi3b-img104.png]]

</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~~=~~"figure">~~= How to burn Android image to TF card ==

~~[[File:pi3b~~=== Method of burning Android image to TF card through USB2.~~png|390x267px|IMG_256]]~~0 burning port ===

~~</div><ol start="10" style="list-style-type: lower-alpha;"><li>~~# First prepare a TF card with 8GB or larger capacity. The ~~display~~ transmission speed of the ~~burning process~~ TF card must be class10 or above. It is ~~as follows:</li></ol>~~recommended to use a TF card of SanDisk and other brands ~~[[File:pi3b~~# You also need to prepare a good quality USB2.0 male-to-~~img109.png|393x212px]]~~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-without lcd</li><li>b) If you want to~~-tf-card"~~use LCD screen, please choose image with lcd</~~span~~li>

~~== How to burn Android image to TF card ==~~ ~~=== 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]]'''.'''~~}

~~<span id="method-~~# 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~~-burning-android-image-into-emmc-through-usb2~~the development board. Then install the eMMC module to the development board.~~0-burning-port">=== Method~~ The eMMC module and the method of ~~burning Android image~~ plugging into ~~eMMC through USB2.0 burning port ===~~the development board are as follows:

~~'''Note that all the following operations are performed on a Windows computer~~::[[File:pi3b-img61.~~'''~~png|400px]] [[File:pi3b-img62.png|400px]]

~~<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]] [[File:pi3b-img62.png|120x87px]]~~ [[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-~~img32~~img144.png~~|300x157px~~]]</ol><ol start="12" style="list-style-type: decimal;"><li>Then pull out the TF card from the computer and insert it into the development board. After the development board is powered on, it will automatically start burning the Android image in the TF card to the eMMC of the development board.</li><li>If the development board is connected to an HDMI display, you can also see the progress bar of burning the Android image to eMMC from the HDMI display</li>

[[File:pi3b-img145.png]]</ol><ol start="214" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~After waiting for a period~~ 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, ~~a pop-up window will prompt "'''driver installed successfully'''"~~the TF card can be pulled out, and then ~~click~~ the ~~"'''OK'''" button~~Android system in the eMMC will start.</li~~></ol~~>

[[File:pi3b-~~img33~~img146.png~~|315x164px~~]]</ol>

~~<ol start~~=~~"8" 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 the decompressed folder and open it</li></ol>~~burn Android image to SPIFlash+NVMe SSD ==

~~[[File~~{| class="wikitable" style="background-color:~~pi3b~~#ffffdc;width:800px;" |-~~img34~~| <big>'''Note that all the following operations are performed on a Windows computer.~~png~~'''</big>|~~454x134px]]~~}

<ol ~~start="9"~~ style="list-style-type: decimal;"><li>~~After opening the '''RKDevTool''' burning tool~~First, ~~because the computer is not connected~~ you need to ~~the development board through the USB2.0 male~~prepare an NVMe SSD solid state drive<ol style="list-tostyle-~~male data cable at this time, the~~ type: lower ~~left corner will prompt "'''No device found'''&quot~~-alpha;"></li>The M.2 2230 SSD is as follows</olli>

[[File:pi3b-~~img35~~img73.png~~|442x208px~~]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The M.2 2242 SSD is as follows</li>

~~<ol start="10" style="list-style-type~~[[File: ~~decimal;"><li>Then start burning the Android image into eMMC<ol style="list~~pi3b-~~style-type: lower-alpha;">~~img74.png]]<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>

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

[[File:pi3b-img75.png]]<~~div class~~/ol><ol start="3" 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>

[[File:pi3b-~~img36~~img76.png~~|275x116px|C~~]]</ol><ol start="4" style="list-style-type:~~\Users\orangepi\Desktop\用户手册插图\pi 3b\1691131157154(1)~~decimal;"><li>You also need to prepare a good quality USB2.~~jpg1691131157154(1)]]~~0 male-to-male data cable</li>

</div>~~<ol start~~class="2figure" ~~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></ol~~>

[[File:pi3b-~~img37~~img16.png~~|289x100px~~]]

~~<ol start="4" style="list-style-type: lower-alpha;"><li>Then connect the power supply of the Type-C interface to the development board~~</lidiv></ol> ~~[[File:pi3b-img38.png|305x94px]]~~ <ol start="5" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~If the previous steps are successful, the development board will enter the~~ Then download Rockchip driver '''~~MASKROM~~DriverAssitant_v5.12.zip''' ~~mode at this time,~~ and ~~the interface of the~~ burning tool ~~will prompt "~~'''~~found a MASKROM device~~RKDevTool_Release_v3.15.zip'''~~"[[File:pi3b-img39.png|457x215px]]</li><li>Then please select~~ from '''Orange Pi'~~Advanced Features~~s data download page'''~~[[File:pi3b-img126.png|458x138px]]~~</li><li>Then ~~click~~ download the ~~position shown in the figure below~~image of Android11~~[[File:pi3b-img127.png|459x216px]]</li></ol>~~ ~~<!-- --~~>

<li>~~Select~~ 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 S'''~~rk3566_MiniLoaderAll.bin~~PIFlash-NVME SSD boot image folder''' ~~in the MiniLoader folder downloaded earlier, and click~~ to ~~open.~~download</li~~></ol~~>

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

</div>

</ol>

<li>~~Then click~~ After entering the '''~~Download~~SPIFlash-NVME SSD boot image folder''', you can see the following two images. Their differences are:<~~p>[[File~~ol style="list-style-type:~~pi3b-img128.png|472x222px]]</li~~none;"><li>a) The image without lcd is specially used for HDMI display and supports 4K display ~~after downloading '''MiniLoaderAll~~.~~bin''' is shown in~~ If you do not use the LCD screen, please download the ~~figure below[[File:pi3b-img140.png|474x223px]]~~image without lcd</li><li>~~Then select the storage device as '''EMMC'''~~b) If you want to use LCD screen, ~~and then click Switch '''Storage'''[[File:pi3b-img141.png|468x225px]]~~please choose image with lcd</li>~~<li>The display of successful switching is shown in the figure below</li></ol~~>

[[File:pi3b-~~img142~~img147.png~~|472x227px~~]]</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="8" 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 "'''~~Upgrade Firmware~~Driver Installation'''" ~~column of the burning tool~~button</li~~></ol~~>

[[File:pi3b-~~img132~~img32.png~~|442x208px~~]]</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="9" style="list-style-type: ~~lower-roman~~decimal;"><li>Then ~~click the "~~decompress '''~~Firmware~~RKDevTool_Release_v3.15.zip'''~~" button~~ , this software does not need to ~~select~~ be installed, just find '''RKDevTool''' in the ~~path of the Android image that needs to be burned~~decompressed folder and open it</li~~></ol~~>

[[File:pi3b-~~img133~~img34.png~~|444x209px~~]]</ol><ol start="10" 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>

[[File:pi3b-img35.png]]</ol><ol start="1011" style="list-style-type: decimal;" ><li>Then start burning the Android image to SPIFlash+NVMe SSD<ol style="list-style-type: lower-alpha;"><li>~~Finally~~First, ~~click~~ connect the development board to the Windows computer through the ~~"'''Upgrade'''" button~~ USB2.0 male-to ~~start burning, and~~ -male data cable. The position of the ~~log during~~ USB2.0 programming port of the ~~burning process~~ development board is shown in the figure below~~. After burning is completed, the Android system will start automatically.~~</li~~></ol~~>

[[File:pi3b-~~img134~~img36.png~~|455x214px|GO~ZSPN`B]JCQM`@_9UU8[R~~]]

</div></ol><~~span id~~ol start="2" style="~~how~~list-tostyle-~~burn-android11-image~~type: lower-alpha;"><li>Make sure that the development board is not inserted into~~-emmc-via-tf-~~the TF card"and not connected to the power supply</~~span~~li>~~=== How to burn Android11 image into eMMC via TF card ===~~<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>

~~'''Note that all~~ [[File:pi3b-img37.png]]</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then connect the ~~following operations are performed~~ power supply of the Type-C interface to the development board, and power on ~~a Windows computer.'''~~, and then release the MaskROM button</li>

~~# The development board reserves an eMMC expansion interface~~[[File:pi3b-img38. ~~Before programming~~ png]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li>If the ~~system to eMMC~~previous steps are successful, ~~you first need to purchase an eMMC module that matches the eMMC interface of~~ the development board~~. Then install~~ will enter the ~~eMMC module to the development board. The eMMC module~~ '''MASKROM''' mode at this time, and the ~~method~~ interface of ~~plugging into~~ the ~~development board are as follows:~~burning tool will prompt "'''found a MASKROM device'''"</li>

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

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

~~<ol start="2" 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~~[File:~~//www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi~~pi3b-3Bimg133.~~html '''Orange Pi data download page'''~~png]]~~, '''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''']</p~~ol><ol start="8" style="list-style-type: lower-alpha;"><li>~~After opening~~ Finally, click the ~~download link of~~ "Upgrade" button to start burning. The burning process is shown in the ~~Android image, you~~ figure below. You can see that the ~~following two types of Android images~~firmware will be burned to SPIFlash first, ~~please select the image in '''the TF card~~ and ~~eMMC startup image folder'''~~ then burned to ~~download</li></ol>~~PCIE. After burning is completed, the Android system will start automatically.</li~~></ol~~>

~~<div class="figure">~~ [[File:pi3b-~~img124~~img148.png~~|340x108px|e6986fc9c8fc078e8cb6a9c39b76fb8~~]] ~~</div><ol start="2" style="list-style-type: lower-alpha;"><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 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|283x62px]]~~== Using RKDevTool to clear SPIFlash ==

~~<ol start="6" style="list-style-type: decimal;"><li>Then use the decompression software to decompress the compressed package~~ # The position of SPI Flash on the ~~downloaded Android image. Among the decompressed files, the file ending with ".img" is the Android image file, and the size~~ development board 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'''~~ shown in the ~~decompressed folder and open it</li></ol>~~figure below

::[[File:pi3b-~~img135~~img76.png~~|429x103px~~]]

<ol start="82" style="list-style-type: decimal;"><li>~~After opening '''SDDiskTool'''~~First, 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~~ need to ~~burn''', if there is no display, you can try~~ prepare a good quality USB2.0 male-to ~~unplug the TF card.~~-male data cable</li~~></ol~~>

~~[[File:pi3b-img136.png|267x228px]]~~<div class="figure">

~~<ol start="9" style="list~~[[File:pi3b-~~style-type: decimal;">~~<li>After confirming the drive letter, you can format the TF card first, click the '''restore disk button''' in SDDiskTool, or use the '''SD Card Formatter''' mentioned above to format the TF card</li></ol>img16.png]]

~~[[File:pi3b-img137.png|247x212px]]~~</div></ol><ol start="103" style="list-style-type: decimal;"><li>Then ~~start to write~~ download the Rockchip driver '''DriverAssitant_v5.12.zip''' and MiniLoader and the ~~Android image into~~ burning tool '''RKDevTool_Release_v3.15.zip''' from the ~~TF card~~[http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page''']

<li>~~First confirm that~~ On 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~~ download page of Orange Pi, first select the ~~path of the Android firmware in the "'''Select Upgrade Firmware'''" column</li><li>Finally click~~ official tool, and then enter the ~~"'''Start Create'''" button to start burning</li></ol>~~following folder</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>~~img149.png]]

~~[[File~~</div></ol><ol start="2" style="list-style-type:~~pi3b~~lower-~~img144.png|285x243px]]~~alpha;"><li>Then download all the files below</li>

<~~ol start~~div class="12figure" ~~style="list-style-type: decimal;">~~<li>Then pull out the TF card from the computer and insert it into the development board. After the development board is powered on, it will automatically start burning the Android image in the TF card to the eMMC of the development board.</li>~~<li>If the development board is connected to an HDMI display, you can also see the progress bar of burning the Android image to eMMC from the HDMI display</li></ol~~>

[[File:pi3b-~~img145~~img150.png~~|430x247px~~]]

<~~ol start~~/div>{| class="14wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~When the HDMI monitor displays the following information, it means~~ '''Note that the ~~burning of~~ "MiniLoader-things needed to burn the ~~Android~~ Linux image ~~into~~ " folder is hereinafter referred to as 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~~MiniLoader folder.'''</big>|}</ol></li></ol> ~~[[File:pi3b-img146.png|576x389px]]~~ <~~span id~~ol start="~~how~~4" style="list-tostyle-~~burn-android-image-to-spiflashnvme-ssd~~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</~~span~~li>~~== How to burn Android image to SPIFlash+NVMe SSD ==~~

~~'''Note that all the following operations are performed on a Windows computer~~[[File:pi3b-img31.~~'''~~png]]</ol><ol start="5" style="list-style-type: decimal;"><li>~~First~~After opening DriverInstall.exe, ~~you need~~ the steps to ~~prepare an NVMe SSD solid state drive~~install the Rockchip driver are as follows

<li>~~The M.2 2230 SSD is as follows~~Click the "'''Driver Installation'''" button</li>~~</ol></li></ol>~~ ~~[[File:pi3b-img73.png|147x106px]]~~

[[File:pi3b-img32.png]]

</ol>

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

[[File:pi3b-~~img74~~img33.png~~|216x119px~~]]</ol></li></ol><ol start="6" 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="27" style="list-style-type: decimal;"><li>~~Then insert~~ After opening the ~~NVMe SSD into~~ '''RKDevTool''' burning tool, because the ~~M.2 PCIe interface of~~ computer has not connected to the development board ~~and fix it~~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-~~img75~~img35.png~~|283x63px~~]]</ol><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 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~~img36.png~~|266x211px~~]]

</div></ol><ol start="42" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~You also need~~ Make sure that the development board is not inserted into the TF card and not connected to ~~prepare a good quality USB2.0 male-to-male data cable~~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:</olp></li>

[[File:pi3b-img37.png]]<~~div class~~/ol><ol start="4" style="~~figure~~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-~~img16~~img38.png~~|141x138px|D6BB9058~~]]</ol><ol start="5" style="list-~~CDC3~~style-~~42d7~~type: lower-~~A7FC-FBF630D886B7]]~~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]]</~~div~~ol><ol start="56" style="list-style-type: ~~decimal~~lower-alpha;"><li>Then ~~download Rockchip driver~~ please select '''~~DriverAssitant_v5.12.zip~~Advanced Features''' ~~and burning tool '''RKDevTool_Release_v3~~[[File:pi3b-img126.~~15.zip''' from '''Orange Pi's data download page'''~~png]]</li><li>Then ~~download~~ click the position shown in the ~~image of Android11~~figure below<~~ol style="list-style-type~~p>[[File: ~~lower~~pi3b-~~alpha;"~~img127.png]]</li><li>~~After opening the download link of the Android image, you can see the following two types of Android images, please select the image~~ Select '''rk3566_MiniLoaderAll.bin''' in the S'''~~PIFlash-NVME SSD boot image folder~~MiniLoader''' ~~to download~~folder you downloaded earlier, and click Open</~~li></ol~~p></li~~></ol~~>

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

</div></ol><ol ~~start="2"~~ style="list-style-type: lower-~~alpha~~roman;"><li>~~After entering the~~ Then click '''~~SPIFlash-NVME SSD boot image folder~~Download'''~~, you can see the following two images~~[[File:pi3b-img128. ~~Their differences are:~~png]]</li></ol> <ol start="10" style="list-style-type: lower-alpha;"><li>The ~~image without lcd is specially used for HDMI display and supports 4K~~ displayafter downloading '''rk3566_MiniLoaderAll. ~~If you do not use~~ bin''' is shown in the ~~LCD screen, please download~~ figure below[[File:pi3b-img140.png]]</li><li>Then select the ~~image without lcd~~storage device as '''SPINOR'''[[File:pi3b-img151.png]]</li><li>~~If you want~~ Then click Switch '''Storage'''[[File:pi3b-img152.png]]</li><li>Then click '''Erase All''' to ~~use LCD screen, please choose image with lcd~~start erasing SPIFlash[[File:pi3b-img153.png]]</li><li>The display log after erasing SPIFlash is shown in the figure below[[File:pi3b-img154.png]]</li></ol>

</li></ol>

~~[[File:pi3b-img147.png|305x58px]]~~== Start the Orange Pi development board ==

~~<ol start="7" 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-~~type: decimal;"><li>Then~~ HDMI cable. If you have purchased an LCD screen, you can also use the ~~decompression software~~ LCD screen to ~~decompress '''DriverAssitant_v5~~display the system interface of the development board.12If there is a Type-C to HDMI cable, the system interface of the development board can also be displayed through the Type-C interface.~~zip''',~~ # Connect a USB mouse and ~~then find~~ keyboard to control the ~~'''DriverInstall~~Orange Pi development board.# The development board has an Ethernet port, which can be plugged into a network cable for Internet access.~~exe''' executable file in the decompressed folder and open it<~~# Connect a high-quality power adapter with a 5V/~~li></ol>~~3A USB Type-C interface.

~~[[File~~:~~pi3b~~:{| class="wikitable" style="background-~~img31~~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|407x120px]]~~'''

'''<~~ol start="8"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>After opening '''DriverInstall~~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.~~exe'''~~If you find that there is a phenomenon of continuous restart during the startup process, please replace the ~~steps to install~~ power supply or the ~~Rockchip driver are as follows<ol style="list~~Type-~~style-type: lower-alpha;"><li>Click the "'~~C data cable and try again.''~~Driver Installation~~'~~''" button</li></ol></li>~~</olspan>

~~[[File~~'''The Type-~~img32~~C power port does not support PD negotiation.~~png|286x150px]]~~'''

'''<~~ol start="2"~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<li>After waiting for a period~~ In addition, please do not connect the USB interface of ~~time, a pop-up window will prompt "'''driver installed successfully'''", and then click~~ the ~~"'''OK~~computer to power the development board.'''~~" button.~~</lispan></olbig>|}

~~[[File~~<ol start="6" style="list-style-type:~~pi3b-img33~~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|296x154px]]~~</li>

~~<ol start="9" style="list-style-type: decimal;">~~<li>~~Then decompress '''RKDevTool_Release_v3~~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.~~15.zip'''~~For the connection method of the serial port, ~~this software does not need~~ please refer to ~~be installed, just find~~ '''~~RKDevTool~~[[Orange Pi 3B#How to use the debugging serial port|the section on how to use the debugging serial port]].''' ~~in the decompressed folder and open it~~</li></ol>

~~[[File:pi3b-img34.png|413x122px]]~~== How to use the debugging serial port ==

<~~ol start~~span id="~~10" style="list~~connection-instruction-~~style~~of-~~type: decimal;"><li>After opening the '''RKDevTool''' burning tool, because the computer is not connected to the development board through the USB2.0 male~~debugging-toserial-~~male data cable at this time, the lower left corner will prompt "'''No device found'''"</li~~port"></olspan>=== Connection instruction of debugging serial port ===

~~[[File:pi3b-img35.png|402x189px]]~~ <ol ~~start="11"~~ style="list-style-type: decimal;"><li>~~Then start burning~~ First, you need to prepare a 3.3V USB-to-TTL module, and then insert the ~~Android image~~ USB interface end of the USB-to ~~SPIFlash+NVMe SSD~~-TTL module into the USB interface of the computer.~~<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;"|-| <big><lip>~~First~~'''For better compatibility, ~~connect the development board~~ it is recommended to use CH340 USB to ~~the Windows computer through the USB2.0 male-~~TTL module, please do not use CP2102, PL2303 USB to~~-male data cable. The position of the USB2~~TTL module.~~0 programming port of the development board is shown in the figure below~~'''</lip><~~/ol~~p>'''Before purchasing a USB to TTL module, please confirm that the module supports a baud rate of 1500000.'''</lip></olbig>|}

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

</div></li></ol><ol start="2" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Make sure that the development board is not inserted into the TF card~~ The corresponding relationship between GND, RXD and ~~not connected to~~ TXD pins of the ~~power supply</li><li>Then press and hold the MaskROM button on the development board, the position~~ debugging serial port of ~~the MaskROM button on~~ the development board is shown in the figure below~~:~~</li~~></ol~~>

[[File:pi3b-~~img37~~img156.png~~|289x100px~~]]</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="4" style="list-style-type~~: ~~lower-alpha;"><li>Then connect~~ a. Connect the ~~power supply~~ GND of the ~~Type-C interface~~ USB to TTL module to the GND of the development board~~, and power on, and then release the MaskROM button</li></ol>~~

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

:c. The '''TX of the USB to TTL module is connected to the TX''' of the development board</ol><ol start="54" style="list-style-type: ~~lower-alpha~~decimal;"><li>If The schematic diagram of connecting the ~~previous steps are successful,~~ USB to TTL module to the computer and the Orange Pi development board ~~will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"~~is as follows</li~~></ol~~>

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

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

~~[[File~~</div>{| class="wikitable" style="background-color:~~pi3b~~#ffffdc;width:800px;" |-~~img132~~| <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>|~~442x208px]]~~}</ol>

~~<ol start~~=~~"7" style~~=~~"list-style-type: lower-alpha;"><li>Then click~~ = How to use the ~~"'''Firmware'''" button to select~~ debugging serial port on the ~~Android image to be burned</li></ol>~~Ubuntu platform ===

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-~~img133~~| <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>|~~444x209px]]~~}

~~<ol start="8" style="list~~# First, insert the USB-~~style~~to-~~type: lower~~TTL module into the USB interface of the Ubuntu computer. If the connection and recognition of the USB-~~alpha;"><li>Finally, click the "Upgrade" button~~ to ~~start burning. The burning process~~ -TTL module is ~~shown in the figure below. You~~ normal, you can see ~~that~~ the ~~firmware will be burned to SPIFlash first~~corresponding device node name under '''/dev''' on the Ubuntu PC. Remember this node name, and then ~~burned to PCIE. After burning is completed,~~ set the ~~Android system~~ serial port software will ~~start automatically.</li></ol>~~be used

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-~~img148.png~~|~~453x212px]]~~test@test:~$ '''ls /dev/ttyUSB*'''

~~<~~/~~span>== Using RKDevTool to clear SPIFlash ==~~ ~~# The position of SPI Flash on the development board is shown in the figure below~~dev/ttyUSB0~~[[File:pi3b-img76.png~~|~~263x193px]]~~}

<li>~~First, you need~~ Then use the following command to ~~prepare a good quality USB2.0 male-to-male data cable~~install putty on Ubuntu PC</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt-get update'''

~~<div class="figure">~~ ~~[[File~~test@test:~~pi3b~~~$ '''sudo apt-~~img16.png|141x138px|D6BB9058~~get install -~~CDC3-42d7-A7FC-FBF630D886B7]]~~y putty'''|}</~~div~~ol>

<li~~><p~~>Then ~~download the Rockchip driver '''DriverAssitant_v5.12.zip''' and MiniLoader and the burning tool '~~run putty, ''~~RKDevTool_Release_v3.15.zip~~'~~'' from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page''']~~<~~/p><ol~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<li>On the download page of Orange Pi, first select the official tool, and then enter the following folder</li>~~remember to add sudo permission</olspan>'''</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo putty'''|}</ol><~~div class~~ol start="4" style="~~figure~~list-style-type: decimal;"><li>After executing the putty command, the following interface will pop up</li>

[[File:pi3b-~~img149~~img158.png~~|342x56px|1691401357374~~]]</ol><ol start="5" style="list-style-type: decimal;"><li>First select the setting interface of the serial port</li>

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

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

</div></ol>~~'''Note that~~ </li></ol><ol start="7" style="list-style-type: decimal;"><li>After setting the setting interface of the ~~"MiniLoader-things needed~~ serial port, return to ~~burn~~ the ~~Linux image&quot~~Session interface<ol style="list-style-type: lower-alpha; ~~folder is hereinafter referred~~ "><li>First select the Connection type as Serial</li><li>Then click the Open button to connect to as the ~~MiniLoader folder.'''~~serial port</li>

<~~ol start~~div class="4figure" ~~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></ol~~>

[[File:pi3b-~~img31~~img161.png~~|472x139px~~]]

~~<ol start="5" 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>Click the "'''Driver Installation'''" button</li~~div></ol>

</li></ol>

<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-~~img32~~img162.png~~|276x145px~~]]</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~~ = How to use the ~~"'''OK'''" button.</li></ol>~~debugging serial port on Windows platform ===

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-~~img33~~| <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.~~png~~'''</big>|~~292x151px]]~~}

<ol ~~start="6" 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></ol>~~ ~~[[File:pi3b-img34.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~~Download MobaXterm

<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 belowDownload MobaXterm website as follows</li~~></ol~~>~~</li></ol>~~ ~~<div~~ {| class="~~figure~~wikitable" style="width:800px;">|-| [~~[File~~https:~~pi3b-img36~~//mobaxterm.mobatek.~~png|275x116px|C~~net/ '''https:~~\Users\orangepi\Desktop\用户手册插图\pi 3b\1691131157154(1)~~//mobaxterm.~~jpg1691131157154(1)]~~mobatek.net''']|}</~~div~~ol>

<li>~~Make sure that the development board is not inserted into the TF card and not connected to~~ After entering the ~~power supply</li><li>Then press and hold the MaskROM button on the development board~~MobaXterm download page, ~~the position of the MaskROM button on the development board is shown in the figure below:~~click '''GET XOBATERM NOW!'''</li~~></ol~~>

[[File:pi3b-~~img37~~img163.png~~|289x100px~~]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then choose to download the Home version</li>

[[File:pi3b-img164.png]]

</ol>

<li>Then ~~connect~~ select the ~~power supply of the Type-C interface~~ Portable version. After downloading, you don't need to ~~the development board, and power on~~install it, just open it and ~~then release the MaskROM button~~use it</li~~></ol~~>

[[File:pi3b-~~img38~~img165.png~~|305x94px~~]]</ol></li></ol><ol start="2" style="list-style-type: 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> [[File:pi3b-img166.png]]</ol><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<ol style="list-style-type: lower-alpha;"><li>Open the session settings interface</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)</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 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~~img167.png~~|457x215px~~]]

</div></ol></li></ol><ol start="64" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then please select~~ After clicking the "'''~~Advanced Features~~OK'''~~[[File:pi3b-img126~~" button, you will enter the following interface.~~png|458x138px]]</li><li>Then click~~ At this time, start the ~~position shown in~~ development board and you can see the ~~figure below[[File:pi3b-img127.png|459x216px]]</li><li>Select '''rk3566_MiniLoaderAll.bin''' in~~ output information of the ~~'''MiniLoader''' folder you downloaded earlier, and click Open~~serial port</li~~></ol~~>

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

</div></ol><~~ol style~~span id="~~list~~instructions-for-~~style~~using-~~type: lower~~the-~~roman;~~5v-pin-in-the-40pin-interface-of-the-development-board-to-supply-power">~~<li>Then click '''Download'''[[File:pi3b-img128.png|472x222px]]~~</~~p></li></ol~~span>

~~<ol start~~=~~"10" style~~=~~"list-style-type: lower-alpha;"><li>The display after downloading '''rk3566_MiniLoaderAll.bin''' is shown~~ Instructions for using the 5v pin in the ~~figure below[[File:pi3b-img140.png|474x223px]]</li><li>Then select~~ 40pin interface of the ~~storage device as '''SPINOR'''[[File:pi3b-img151.png|467x220px]]</li><li>Then click Switch '''Storage'''[[File:pi3b-img152.png|464x218px]]</li><li>Then click '''Erase All'''~~ development board to ~~start erasing SPIFlash[[File:pi3b-img153.png|467x220px]]</li><li>The display log after erasing SPIFlash is shown in the figure below[[File:pi3b-img154.png|460x216px]]</li></ol>~~supply power ==

~~'''The power supply method we recommend for thedevelopment board is to use the 5V/3A Type C interface power cord to plug into the Type-~~orange-pi-~~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 developmentboard. If the use is unstable, please switch back to the Type-~~board">~~C power supply.'''</~~span~~big>~~== Start the Orange Pi development board ==|}

# ~~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~~First, ~~then there is no~~ you need to ~~insert~~ prepare 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~~ power cord as shown in 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.~~# 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.~~figure below

~~'''Remember not to plug in a power adapter with a voltage output greater than 5V, as this will burn out the development board.'''~~<div class="figure">

~~'''Many unstable phenomena during the power~~::[[File:pi3b-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 againimg169.~~'''~~png]]

</div>::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~The Type-C~~ Please purchase the power ~~port does not support PD negotiation.~~cord shown in the picture above by yourself'''</big>|}

<ol start="2" style="list-style-type: decimal;"><li>Use the 5V pin in the 40pin interface to supply power to the development board. The connection method of the power line is as follows<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 ('''~~In addition,~~ please do not ~~connect~~ plug into the computer's USB port for power supply''')</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 inserted into the GND pin of the 40pin interface </li><li>The position of the 5V pin and GND pin of the ~~computer to power~~ 40pin interface on the development board.is shown in the figure below, '''remember not to reverse the connection'''</li>

~~6) Then turn on the switch of the power adapter~~[[File:pi3b-img170. ~~If everything is normal, you can see the startup screen~~ png]]</ol></li></ol>

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 = '''~~[[\l|the section on how to~~ Instructions for use ~~the debugging serial port]].~~of Ubuntu/Debian Server and Xfce desktop system'''=

~~'''The content of this chapter is written based on the images of the Linux server version and the~~-debugging-serial-port">~~xfce desktop version.'''</~~span~~big>~~== How to use the debugging serial port ==|}

==~~= Connection instruction of debugging serial port =~~Supported Linux image types and kernel versions ==

~~<ol~~ {| class="wikitable" style="~~list-style~~width:800px;text-~~type~~align: ~~decimal~~center;">~~<li>First, you need to prepare a 3.3V USB~~|-to|'''Linux image type'''|'''kernel version'''|'''server version'''|'''desktop version'''|-~~TTL module, and then insert the USB interface end of the USB~~|'''Debian 11 -toBullseye'''|'''Linux5.10'''|'''support'''|'''support'''|-~~TTL module into the USB interface of the computer~~|'''Ubuntu 20.~~~~04 - Focal'''|'''Linux5.10'''|'''support'''~~~~|'''support'''~~For better compatibility, it is recommended to use CH340 USB to TTL module, please do not use CP2102, PL2303 USB to TTL module~~|-|'''Ubuntu 22.04 - Jammy'''~~~~|'''~~Before purchasing a USB to TTL module, please confirm that the module supports a baud rate of 1500000~~Linux5.10'''~~</li></ol>~~|'''support'''|'''support'''|}

<~~div class~~span id="~~figure~~linux-system-adaptation">== Linux System adaptation ==

~~[[File:pi3b-img155.png~~{|~~576x115px|07]]~~ ~~</div><ol start~~class="2wikitable" style="~~list~~width:800px;text-~~style-type~~align: ~~decimal~~center;">~~<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>~~ ~~[[File:pi3b-img156.png~~|~~428x110px]]~~ ~~<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>~~ ~~<blockquote>a. Connect the GND of the USB to TTL module to the GND of the development board~~ ~~b. The~~ |'''~~RX of the USB to TTL module is connected to the TX~~Function''' ~~of the development board~~ ~~c. The~~ |'''~~TX of the USB to TTL module is connected to the TX~~Debian11''' ~~of the development board</blockquote><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>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img157.png~~|~~524x189px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\USB-to-TTL-module-to-the-computer~~'''Ubuntu20.~~jpgUSB-to-TTL-module-to-the-computer]]~~ ~~</div>~~04'''|'''~~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~~Ubuntu22. ~~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~~04''' ~~=== How to use the debugging serial port on the Ubuntu platform ===~~ |'''~~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~~USB2.0x3'''|'''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~~OK''' ~~on the Ubuntu PC. Remember this node name, and then set the serial port software will be used~~ ~~test@test:~$~~ |'''ls /dev/ttyUSB*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>~~|'''USB3.0x1'''|'''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~~M.2 NVMe SSD Start'''~~</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>~~|'''WIFI'''|'''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>~~|'''Bluetooth'''|'''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~~|'''GPIO（40pin）'''~~<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>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img160.png|317x312px~~|~~09]]~~ ~~</div><ol start="7" style="list-style~~-~~type: decimal;"><li>After setting the setting interface of the serial port, return to the Session interface~~|'''UART（40pin）'''~~<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></li></ol>~~|'''OK''' ~~<div class="figure">~~ ~~[[File:pi3b-img161.png~~|~~345x340px|10]]~~ ~~</div><ol start="8" style="list-style~~-~~type: decimal;"><li>After starting the development board, you can see the Log information output by the system from the opened serial port terminal</li></ol>~~|'''SPI（40pin）'''|'''OK'''~~[[File:pi3b-img162.png~~|~~468x340px]]~~'''OK'''|'''OK'''~~=== How to use the debugging serial port on Windows platform ===~~|'''I2C（40pin）'''|'''OK'''|'''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.OK'''|'''OK'''~~<ol style="list~~|-~~style-type: decimal;"><li>Download MobaXterm~~|'''PWM（40pin）'''~~<ol style="list-style-type: lower-alpha;">~~|'''OK'''~~<li>Download MobaXterm website as follows</li></ol>~~|'''OK'''~~</li></ol>~~|'''OK''' ~~[https://mobaxterm.mobatek.net/ https://mobaxterm.mobatek.net]~~ ~~<ol start="2" style="list~~|-~~style-type: lower-alpha;"><li>After entering the MobaXterm download page, click~~ |'''~~GET XOBATERM NOW!~~PWM fan interface'''~~</li></ol>~~|'''OK'''~~[[File:pi3b-img163.png~~|~~576x334px]]~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>Then choose to download the Home version</li></ol>~~'''OK''' ~~[[File:pi3b-img164.png~~|~~353x231px]]~~ ~~<ol start="4" style="list-style-type: lower-alpha;">~~'''OK'''~~<li>Then select the Portable version. After downloading, you don’t need to install it, just open it and use it</li></ol>~~ ~~[[File:pi3b-img165.png~~|~~575x259px]]~~ ~~<ol start="2" style="list~~-~~style-type: 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>~~ ~~[[File:pi3b-img166.png~~|~~576x81px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>After opening the software, the steps to set up the~~ '''3pin Debug serial port ~~connection are as follows~~'''~~<ol style="list-style-type: lower-alpha;"><li>Open the session settings interface</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~~OK''' ~~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~~OK'''~~</li><li>Finally click the "~~|'''OK'''~~" button to complete the setting</li></ol></li></ol>~~|-|'''EMMC'''~~<div class="figure">~~|'''OK'''|'''OK'''~~[[File:pi3b-img167.png~~|~~575x438px~~'''OK'''|~~11]]~~- ~~</div><ol~~ |'''TF card start~~="4" style="list-style-type: decimal;">~~'''~~<li>After clicking the "~~|'''OK'''~~" button, you will enter the following interface. At this time, start the development board and you can see the output information of the serial port</li></ol>~~|'''OK'''~~<div class="figure">~~|'''OK'''~~[[File:pi3b-img168.png~~|~~575x291px|12]]~~ ~~</div>== Instructions for using the 5v pin in the 40pin interface of the development board to supply power ==~~|'''HDMI Video'''|'''OK'''|'''The power supply method we recommend 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 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.OK'''|'''OK'''~~# First, you need to prepare a power cord as shown in the figure below~~ ~~<div class="figure">~~ ~~[[File:pi3b-img169.png|151x108px~~|~~C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~-~~7.jpg未标题-7]]~~|'''HDMI Audio'''~~</div>~~|'''OK'''|'''~~Please purchase the power cord shown in the picture above by yourself~~OK'''|'''OK'''~~<ol start="2" style="list~~|-~~style-type: decimal;"><li>Use the 5V pin in the 40pin interface to supply power to the development board. The connection method of the power line is as follows~~|'''Camera'''~~<ol style="list-style-type: lower-alpha;">~~|'''OK'''~~<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 (~~|'''~~please do not plug into the computer’s USB port for power supply~~OK'''~~)</li><li>The red DuPont line needs to be plugged into the 5V pin of the development board 40pin</li>~~|'''OK'''~~<li>The black Dupont wire needs to be 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, remember not to reverse the connection</li></ol></li></ol>~~ ~~[[File:pi3b-img170.png~~|~~365x71px]]~~ ~~~~|'''LCD'''= |'''~~Instructions for use of Ubuntu/Debian Server and Xfce desktop system~~OK''' = |'''~~The content of this chapter is written based on the images of the Linux server version and the xfce desktop version.~~OK''' ~~== Supported Linux image types and kernel versions ==~~ {| ~~class="wikitable"~~'''OK'''

|-

|'''~~Linux image type~~Edp Display'''|'''~~kernel version~~OK'''|'''~~server version~~OK'''|'''~~desktop version~~OK'''

|-

|'''~~Debian 11 - Bullseye'''|'''Linux5.10'''|'''support'''|'''support'''~~|-~~|'''Ubuntu 20.04 - Focal'''|'''Linux5.10'''|'''support'''|'''support'''~~|-~~|'''Ubuntu 22.04 - Jammy'''|'''Linux5.10'''|'''support'''|'''support'''~~|} ~~== Linux System adaptation ==~~ ~~{| class="wikitable"~~|-~~|'''Function'''|'''Debian11'''|'''Ubuntu20.04'''|'''Ubuntu22.04'''~~|-~~|'''USB2.0x3~~Gigabit Ethernet port'''

|'''OK'''

|-

|'''~~USB3.0x1~~Network port status light'''

|'''OK'''

|-

|'''~~M.2 NVMe SSD Start~~headphone playback'''

|'''OK'''

|-

|'''~~WIFI~~headphone recording'''

|'''OK'''

|-

|'''~~Bluetooth~~LED Light'''

|'''OK'''

|-

|'''~~GPIO（40pin）~~RTC'''

|'''OK'''

|-

|'''~~UART（40pin）~~GPU'''

|'''OK'''

|-

|'''~~SPI（40pin）~~NPU'''

|'''OK'''

|-

|'''~~I2C（40pin）~~VPU'''

|'''OK'''

|-

|'''~~PWM（40pin）~~watchdog test'''

|'''OK'''

|-

|'''~~PWM fan interface~~Chromium Hard solution video'''

|'''OK'''

|}

== The format of Linux commands in this manual ==

# In this manual, all commands that need to be entered in the Linux system will be marked with the following box

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

|-

|~~'''3pin Debug serial port'''~~ |~~'''OK'''~~}~~|'''OK'''~~::As shown below, the content in the yellow box indicates the content that needs special attention, except for the commands in it.::{|~~'''OK'''~~class="wikitable" style="background-color:#ffffdc;width:800px;height:40px;"

|-

|~~'''EMMC'''~~ |~~'''OK'''~~}~~|'''OK'''~~<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>{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|'''orangepi@orangepi:~$ sudo apt update''' '''root@orangepi:~#''' '''vim /boot/boot.cmd'~~TF card~~ '' '''test@test:~$ ssh [mailto:root@192.168.1.36 root@192.168.1.]xxx''' '''root@test:~# ls'''|}</ol><ol start="2" 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 '''OKsudo'''</li>|<li>'''OKroot@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?<ol style="list-style-type: lower-alpha;"><li>As shown below, '''OKthe 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:~# '''~~HDMI Video~~cat /boot/orangepiEnv.txt'''|'''OKverbosity=7'''|bootlogo=false '''OKconsole=serial'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>As shown below, 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 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'~~''OK'''~~t miss it</li>{| class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~HDMI Audio~~echo \'''|'''OK"deb [arch=$(dpkg --print-architecture) \'''|'''OKsigned-by=/usr/share/keyrings/docker-archive-keyring.gpg] \'''|'''https://download.docker.com/Linux/debian \'''OK '''$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null'''|}</ol></li></ol> == Linux system login instructions == === Linux system default login account and password === {| class="wikitable" style="width:800px;text-align: center;"

|-

|'''~~Camera~~Account'''|'''~~OK'''|'''OK'''|'''OK~~Passport'''

|-

|'''~~LCD~~root'''|'''~~OK'''|'''OK'''|'''OK~~orangepi'''

|-

|'''~~Edp Display~~orangepi'''|'''OKorangepi'''|~~'''OK'''~~} {|~~'''OK'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|~~'''Gigabit Ethernet port'''~~|<big>'''OKNote 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>|~~'''OK'''~~}{|~~'''OK'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|<big>'''~~Network port status light~~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 reasons.'''</big>|~~'''OK'''~~} === 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 '''OKorangepi'''~~|'''OK'''~~|::[[File:pi3b-img171.png]]~~|'''headphone playback'''|'''OK'''~~<ol start="2" style="list-style-type: decimal;">~~|'''OK'''~~<li>Use the following command to set the root user to automatically log in to the terminal</li>{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~headphone recording~~sudo auto_login_cli.sh root'''|~~'''OK'''~~}</ol><ol start="3" style="list-style-type: decimal;">~~|'''OK'''~~<li>Use the following command to disable automatic login terminal</li>{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~LED Light~~sudo auto_login_cli.sh -d'''|~~'''OK'''~~}</ol><ol start="4" style="list-style-type: decimal;">~~|'''OK'''~~<li>Use the following command to set the orangepi user to automatically log in to the terminal again</li>{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~RTC~~sudo auto_login_cli.sh orangepi'''|~~'''OK'''~~}</ol> === 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 <div class="figure"> ::[[File:pi3b-img172.png]] </div><ol start="2" style="list-style-type: decimal;">~~|'''OK'''~~<li>Run the following command to prohibit the desktop system from automatically logging into the desktop</li>{|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

|~~'''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:~$ '''OKsudo disable_desktop_autologin.sh'''

|}

</ol>

<li>Then restart the system and a login dialog box will appear, at which point a [[\l|password]] is required to enter the system

~~== The format of Linux commands in this manual ==~~img173.png]]

~~# In this manual, all commands that need to be entered in the Linux system will be marked with the following box~~</div></li></ol>

~~As shown below,~~

~~<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~~ setting method of ~~the Linux command, so when entering the command~~ root user automatic login in ~~the~~ Linux desktop version system~~, please do not enter the content of the red font part</li></ol></li></ol>~~===

~~'''orangepi@orangepi:~$ sudo apt update'''~~# Execute the following command to set the desktop system to automatically log in as the root user

~~'''root~~::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~~~#''~~$ ' ''~~'vim /boot/boot~~sudo desktop_login.~~cmd~~sh root'''|}

~~'''test@test~~<ol start="2" style="list-style-type:~~~$ ssh [mailto:root@192.168.1.36~~ decimal;"><li>Then restart the system, and the root~~@192.168.1.]xxx'''~~user will automatically log in to the desktop</li>

~~'''root@test~~[[File:~~~# ls'''~~pi3b-img174.png]]

~~<ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~''~~'~~root@orangepi:~$~~''~~' The prompt indicates~~ Note that ~~this command is entered~~ if you log 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 desktop system is as the root user, ~~who can execute any desired command</li><li>'''test@test:~$''' The prompt indicates that this command is entered~~ you cannot use pulseaudio 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~~upper right corner to manage audio devices. ~~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>

'''Also note that this is not a bug, since pulseaudio is not allowed to run as root.'''<~~!-- --~~/big>|}</ol>

<li>~~What are~~ Execute the ~~commands that need~~ following command to ~~be entered?<ol style="list-style-type: lower-alpha;"><li>As shown below, '''~~set the ~~black bold part''' is the command that needs~~ desktop system to ~~be input, and~~ log in automatically with 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>~~orangepi user again</li~~></ol~~>

~~root~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~# $ '''~~cat /boot/orangepiEnv~~sudo desktop_login.~~txt~~sh orangepi'''|}~~'''verbosity~~</ol> === The method of disabling the desktop in the Linux desktop version system ===~~7'''~~

~~bootlogo~~# First enter the following command on the command line, '''Please remember to add sudo permission'''

::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~console=serial~~sudo systemctl disable lightdm.service'''|}

<ol start="2" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~As shown below, some commands cannot be written in one line~~ Then restart the Linux system and you will ~~be placed on the next line. As long as the black and bold parts are all commands~~ find that ~~need to be input. When these commands are entered into one line,~~ the ~~last "\" of each line needs to~~ desktop will not 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~~displayed</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~echo \~~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, '''Please remember to add sudo permission'''</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo systemctl start lightdm.service''~~"deb [arch~~'|}</ol><ol start="2" style=~~$(dpkg~~ "list-style-~~print~~type: lower-~~architecture) \'''~~alpha;"><li>After the command is executed, the desktop will be displayed</li></ol></li></ol>

~~'''signed~~

~~'''https://download.docker.com/Linux/debian \'''~~== Onboard LED Light Test Instructions ==

~~'''$(lsb_release -cs) stable" | sudo tee /etc/apt/sources~~# There are three LED lights on the development board, one green light, one red light, and one PCIe light.~~list.d/docker.list > /dev/null'''~~The location is shown in the figure below:

<~~span id~~div class="~~linux-system-login-instructions~~figure">~~== Linux system login instructions ==~~

~~=== Linux system default login account and password ===~~img175.png]]

</div><ol start="2" style="list-style-type: decimal;"><li>'''As long as the development board is powered on, the red LED light will always be on, which is controlled by the hardware and cannot be turned off by the software'''</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 the PCIe interface.</li><li>The method of setting the green light on and off and flashing is as follows{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|<big>'''~~Account~~Note that the following operations should be performed under the root user.'''</big>|}<ol style="list-style-type: lower-alpha;"><li>First enter the setting directory of the green light</li>{| class="wikitable" style="width:800px;" |-|root@orangepi:~# '''~~Passport~~cd /sys/class/leds/status_led'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The command to set the green light to stop flashing is as follows</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/sys/class/leds/status_led# '''echo none > trigger'''|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The command to set the green light to be on is as follows</li>{| class="wikitable" style="width:800px;"

|-

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

|-

|~~'''~~root@orangepi:/sys/class/leds/status_led# '''~~|'''orangepi~~echo heartbeat > trigger'''

|}

</ol>

</li></ol>

'''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.'''== Network connection test ==

'''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 reasons.'''=== 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, '''No other configuration is required'''~~=== How~~ # The command to ~~set automatic terminal login~~ view the IP address in the Linux system ~~===~~of the development board is as follows

~~# The Linux system automatically logs in to the terminal by default, and the default login user name is~~ ::{| class="wikitable" style="width:800px;" |-| orangepi @orangepi:~$ '''~~orangepi~~ip addr show eth0'''

~~[[File~~2:~~pi3b-img171.png|351x198px]]~~eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

~~<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<~~link/~~li></ol>~~ether 4a:fe:2b:3d:17:1c brd ff:ff:ff:ff:ff:ff

~~orangepi@orangepi~~:~$ inet '''~~sudo auto_login_cli~~192.168.1.~~sh root~~150'''/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0

~~<ol start="3" style="list-style-type~~: ~~decimal;"><li>Use the following command to disable automatic login terminal</li></ol>~~:valid_lft 43150sec preferred_lft 43150sec

~~orangepi@orangepi~~:~~~$ '''sudo auto_login_cli.sh -d'''~~inet6 fe80::9a04:3703:faed:23be/64 scope link noprefixroute

~~<ol start="4" style="list-style-type~~: ~~decimal;">~~:valid_lft forever preferred_lft forever~~<li>Use the following command to set the orangepi user to automatically log in to the terminal again</li></ol>~~|}

~~orangepi@orangepi~~:~$ :{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''When using ifconfig to view the IP address, if the following information is displayed, it is because sudo ~~auto_login_cli~~is not added.~~sh orangepi~~The correct command is: sudo ifconfig'''</big>

~~~~

~~=== 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~~orangepi@orangepi:~$ '''ifconfig'''

~~<div class="figure">~~Command 'ifconfig' is available in the following places

~~[[File:pi3b-img172.png|576x324px|1]]~~* /sbin/ifconfig

<* /~~div><ol start="2" style="list-style-type: decimal;"><li>Run the following command to prohibit the desktop system from automatically logging into the desktop<~~usr/~~li><~~sbin/~~ol>~~ifconfig

~~orangepi@orangepi~~The command could not be located because '/sbin:~~~$ ''~~/usr/sbin'~~sudo disable_desktop_autologin~~is not included in the PATH environment variable.~~sh'''~~

~~<ol start="3" style="list-style-type: decimal;"><li>Then restart the system and a login dialog box will appear, at which point a [[\l|password]]~~ This is ~~required to enter~~ most likely caused by the ~~system<div class="figure">~~lack of administrative privileges associated with your user account.

~~[[File~~ifconfig:~~pi3b-img173.png~~command not found|~~569x320px|IMG_256]]~~}

::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <~~/div></li></ol~~big>'''There are three ways to check the IP address after the development board starts:'''

~~=== The setting method of root user automatic login in Linux desktop version system ===~~and use the ip addr show eth0 command to view the IP address'''

~~# Execute~~ '''2. Enter the ~~following~~ ip addr show eth0 command ~~to set~~ in the ~~desktop system~~ debugging serial terminal to ~~automatically log in as~~ view the ~~root user~~IP address'''

~~orangepi@orangepi:~$~~ '''~~sudo desktop_login~~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.~~sh root~~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 ~~start="2"~~ style="list-style-type: ~~decimal~~upper-alpha;"><li>~~Then restart~~ '''First check whether the Linux systemhas started normally. If the green light of the development board is blinking, it is generally started normally. If only the red light is on, ~~and~~ it means that the system has not started normally;'''</li><li>'''Check whether the ~~root user will automatically log~~ 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>'''If there is no router to replace, you can only connect to an HDMI display or use the ~~desktop~~debugging serial port to view the IP address'''</li></ol>

~~[[File:pi3b-img174.png|448x187px]]~~

'''~~Note~~ In addition, it should be noted 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~~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'''~~Also note that this is not a bug, since pulseaudio is not allowed to run as root.~~command can be interrupted through the shortcut key of '''Ctrl+C'''</li>

~~<ol start~~{| class="3wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Execute the following command to set the desktop system to log in automatically with the~~ |-| orangepi@orangepi ~~user again</li></ol>~~:~$ '''ping www.baidu.com -I eth0'''

~~orangepi@orangepi~~PING www.a.shifen.com (14.215.177.38) from 192.168.1.12 eth0:~~~$ '''sudo desktop_login~~56(84) bytes of data.~~sh orangepi'''~~

~~=== The method of disabling the desktop in the Linux desktop version system~~ 64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq=1 ttl=56 time=6.74 ms

~~# First enter the following command on the command line，'''Please remember to add sudo permission'''~~64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq=2 ttl=56 time=6.80 ms

~~orangepi@orangepi~~64 bytes from 14.215.177.38 (14.215.177.38):~~~$ '''sudo systemctl disable lightdm~~icmp_seq=3 ttl=56 time=6.~~service'''~~26 ms

~~<ol start~~64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq=~~"2" style~~4 ttl=~~"list-style-type: decimal;"><li>Then restart the Linux system and you will find that the desktop will not be displayed</li></ol>~~56 time=7.27 ms

~~orangepi@orangepi:~$ '''sudo reboot'''~~^C

~~<ol start="3" style="list~~-~~style~~-~~type: decimal;"><li>The steps to reopen the desktop are as follows:<ol style="list~~-~~style~~www.a.shifen.com ping statistics --~~type: lower~~-~~alpha;"><li>First enter the following command on the command line，'''Please remember to add sudo permission'''</li></ol></li></ol>~~

~~orangepi@orangepi:~$ '''sudo systemctl start lightdm.service'''~~4 packets transmitted, 4 received, 0% packet loss, time 3002ms

rtt min/avg/max/mdev = 6.260/6.770/7.275/0.373 ms|}</ol ~~start~~> === WIFI connection test === {| class="2wikitable" style="~~list~~background-color:#ffffdc;width:800px;" |-| <big>'''Please do not connect to WIFI by modifying the /etc/network/interfaces configuration file. There will be problems connecting to the WIFI network in this way.'''</big>|} ==== The server image connects to WIFI through commands ==== {| class="wikitable" style="background-~~type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~After~~ '''When the ~~command~~ development board is ~~executed~~not connected to Ethernet, not connected to HDMI display, but only connected to the ~~desktop will be displayed~~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 display, you can also use the commands demonstrated in this section to connect to the WIFI network.'''</~~li></ol~~big>|}

<~~span id~~ol style="~~onboard~~list-~~led~~style-~~light~~type: decimal;"><li>First log in to the Linux system, there are the following three ways<ol style="list-style-~~test~~type: lower-~~instructions~~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</~~span~~li>~~== Onboard LED Light Test Instructions ==~~<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>

~~# 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~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''nmcli dev wifi'''|}

[[File:pi3b-~~img175~~img176.png~~|425x115px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\3.5.Onboard-LED-Light-Test-Instructions(1).jpg3.5.Onboard-LED-Light-Test-Instructions(1)~~]]

</div></ol><ol start="23" style="list-style-type: decimal;"><li>~~'''As long as~~ Then use the ~~development board is powered on,~~ nmcli command to connect to the ~~red LED light will always be on~~scanned WIFI hotspot, ~~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><li>The PCIe indicator will flash when there is data transmission on the PCIe interface.</li><li>The method of setting the green light on and off and flashing is as follows~~where:</li~~></ol~~>

:a. '''~~Note that the following operations should be performed under the root user.~~wifi_name'''needs to be replaced with the name of the WIFI hotspot you want to connect to

~~<ol style="list-style-type~~: ~~lower-alpha;"><li>First enter~~ b. '''wifi_passwd''' needs to be replaced with the ~~setting directory~~ password of the ~~green light</li></ol>~~WIFI hotspot you want to connect to

~~root~~:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~# $ '''cd nmcli dev wifi connect wifi_name</~~sys/class/leds~~span> password wifi_passwd</~~status~~span>'''

Device 'wlan0' successfully activated with 'cf937f88-ca1e-4411-bb50-61f402eef293'.|}</ol><ol start="24" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The~~ You can view the IP address of wifi through the '''ip addr show wlan0''' command ~~to set the green light to stop flashing is as follows</li></ol>~~

~~root~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~~/sys/class/leds/work#~~ ~$ '''~~echo none > trigger~~ip addr show wlan0'''

~~<ol start="3" style="list-style-type~~11: ~~lower-alpha~~wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP>">~~<li>The command to set the green light to be on is as follows</li></ol>~~mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~root@orangepi~~:link/~~sys/class/leds/work# '''echo default-on > trigger'''~~ether 23:8c:d6:ae:76:bb brd ff:ff:ff:ff:ff:ff

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

~~root@orangepi~~:~~/sys/class/leds/work# '''echo heartbeat > trigger'''~~:valid_lft 259192sec preferred_lft 259192sec

~~<~~:inet6 240e:3b7:3240:c3a0:c401:a445:5002:ccdd/~~span>== Network connection test ==~~64 scope global dynamic noprefixroute

~~=== Ethernet port test ===~~::valid_lft 259192sec preferred_lft 172792sec

# 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~~:inet6 fe80::42f1:6019:a80e:4c31/64 scope link noprefixroute

~~orangepi@orangepi~~:~$ :valid_lft forever preferred_lft forever|}</ol><ol start="5" style="list-style-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 '''~~ip addr show eth0~~Ctrl+C'''</li>

2{| class="wikitable" style="width: ~~eth0~~800px;" |-| orangepi@orangepi: ~~<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000~~~$ '''ping www.orangepi.org -I wlan0'''

~~link/ether 4a~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0:~~fe:2b:3d:17:1c brd ff:ff:ff:ff:ff:ff~~56(84) bytes of data.

~~inet '''192~~64 bytes from 182.~~168~~92.1236.130 (182.~~150'''/24 brd 192~~92.~~168~~236.130): icmp_seq=1ttl=52 time=43.~~255 scope global dynamic noprefixroute eth0~~5 ms

~~valid_lft 43150sec preferred_lft 43150sec~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=2 ttl=52 time=41.3 ms

~~inet6 fe80::9a04:3703~~64 bytes from 182.92.236.130 (182.92.236.130):~~faed:23be/64 scope link noprefixroute~~icmp_seq=3 ttl=52 time=44.9 ms

~~valid_lft forever preferred_lft forever~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=4 ttl=52 time=45.6 ms

~~'''When using ifconfig to view the IP address, if the following information is displayed, it is because sudo is not added~~64 bytes from 182. ~~The correct command is~~92.236.130 (182.92.236.130): ~~sudo ifconfig'''~~icmp_seq=5 ttl=52 time=48.8 ms

~~orangepi@orangepi:~$ '''ifconfig'''~~^C

~~Command 'ifconfig' is available in the following places~~--- www.orangepi.org ping statistics ---

* /sbin/ifconfig5 packets transmitted, 5 received, 0% packet loss, time 4006ms

* rtt min/~~usr~~avg/~~sbin~~max/~~ifconfig~~mdev = 41.321/44.864/48.834/2.484 ms|}</ol>

==== The ~~command could not be located because '/sbin:/usr/sbin' is not included~~ server image connects to WIFI in ~~the PATH environment variable.~~a graphical way ====

~~This~~ <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|'''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 ~~most likely caused by~~ connected to the HDMI display, you can log in to the Linux system through the ~~lack of administrative privileges associated with your user account.~~HDMI display terminal</li></ol>

~~ifconfig~~<li>Then enter the nmtui command in the command line to open the wifi connection interface</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''nmtui'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Enter the nmtui command ~~not found~~to open the interface as shown below</li>

[[File:pi3b-img177.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Select '''~~There are three ways to check the IP address after the development board starts:~~Activate a connect'''and press Enter</li>

~~# '''Connect the HDMI display, then log in to the system and use the ip addr show eth0 command to view the IP address'''~~[[File:pi3b-img178.png]]</ol>~~# '''Enter the ip addr show eth0 command in the debugging serial terminal to view the IP address'''~~<ol start="5" style="list-style-type: decimal;">~~# '''If there is no debugging serial port and no HDMI display,~~ <li>Then 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 all the ~~IP address of the development board normally. If you can't see it, the debug method looks like this:'''~~searched WIFI hotspots</li>

<~~!-- --><ol style~~div class="~~list-style-type: upper-alpha;~~figure"><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>'''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~~[[File:pi3b-img179.~~'''~~png]]

</div></ol><ol start="46" style="list-style-type: decimal;"><li>~~The command~~ Select the WIFI hotspot you want to connect to ~~test the network connectivity is as follows~~, then use the ~~'''ping''' command can be interrupted through~~ Tab key to position the ~~shortcut key of~~ cursor on '''~~Ctrl+C~~Activate'''and press Enter</li~~></ol~~>

~~orangepi@orangepi:~$ '''ping www.baidu.com -I eth0'''~~<div class="figure">

~~PING www.a.shifen.com (14.215.177.38) from 192.168.1.12 eth0~~[[File: ~~56(84) bytes of data~~pi3b-img180.png]]

~~64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq~~</div></ol><ol start=~~1 ttl~~"7" style=~~56 time=6.74 ms~~"list-style-type: decimal;"><li>Then a dialog box for entering a password will pop up, enter the corresponding password in '''Password''' and press Enter to start connecting to WIFI</li>

~~64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq~~<div class=~~2 ttl=56 time=6.80 ms~~"figure">

~~64 bytes from 14.215.177.38 (14.215.177.38)~~[[File: ~~icmp_seq=3 ttl=56 time=6~~pi3b-img181.~~26 ms~~png]]

~~64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq~~</div></ol><ol start=~~4 ttl~~"8" style=~~56 time=7.27 ms~~"list-style-type: decimal;"><li>After the WIFI connection is successful, a "*" will be displayed in front of the connected WIFI name</li>

^C<div class="figure">

[[File:pi3b-~~-- www.a~~img182.~~shifen.com ping statistics ---~~png]]

~~4 packets transmitted, 4 received, 0% packet loss, time 3002ms~~</div></ol><ol start="9" style="list-style-type: decimal;"><li>You can view the IP address of wifi through the '''ip addr show wlan0''' command</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ip addr show wlan0'''

~~rtt min/avg/max/mdev = 6.260/6.770/7.275/0.373 ms~~11: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~<~~:link/~~span>=== WIFI connection test ===~~ether 24:8c:d3:aa:76:bb brd ff:ff:ff:ff:ff:ff

:inet '''~~Please do not connect to WIFI by modifying the /etc/network/interfaces configuration file~~192.168. ~~There will be problems connecting to the WIFI network in this way~~1.11'''/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0

~~==== WIFI The server image connects to WIFI through commands ====~~::valid_lft 259069sec preferred_lft 259069sec

'''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 display, you can also use the commands demonstrated in this section to connect to the WIFI network.''':inet6 240e:3b7:3240:c4a0:c401:a445:5002:ccdd/64 scope global dynamic noprefixroute

~~<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></ol>~~valid_lft 259071sec preferred_lft 172671sec

~~orangepi@orangepi~~:~~~$ '''nmcli dev wifi'''~~inet6 fe80::42f1:6019:a80e:4c31/64 scope link noprefixroute

::valid_lft forever preferred_lft forever|}<~~div~~ /ol><ol start="10" style="list-style-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'''</li>{| class="~~figure~~wikitable" style="width:800px;">|-| orangepi@orangepi:~$ '''ping www.orangepi.org -I wlan0'''

~~[[File~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0:~~pi3b-img176~~56(84) bytes of data.~~png|575x250px|选区_011]]~~

~~</div><ol start~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=1 ttl=~~"3" style~~52 time=~~"list-style-type: decimal;"><li>Then use the nmcli command to connect to the scanned WIFI hotspot, where:</li></ol>~~43.5 ms

a64 bytes from 182. ~~'''wifi_name''' needs to be replaced with the name of the WIFI hotspot you want to connect to~~92.236.130 (182.92.236.130): icmp_seq=2 ttl=52 time=41.3 ms

b64 bytes from 182. ~~'''wifi_passwd''' needs to be replaced with the password of the WIFI hotspot you want to connect to~~92.236.130 (182.92.236.130): icmp_seq=3 ttl=52 time=44.9 ms

~~orangepi@orangepi~~64 bytes from 182.92.236.130 (182.92.236.130):~~~$ '''nmcli dev wifi connect wifi_name password wifi_passwd'''~~icmp_seq=4 ttl=52 time=45.6 ms

~~Device 'wlan0' successfully activated with 'cf937f88-ca1e-4411-bb50-61f402eef293'~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=5 ttl=52 time=48.8 ms

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

--- www.orangepi~~@orangepi:~$ '''ip addr show wlan0'''~~.org ping statistics ---

~~11: wlan0: <BROADCAST~~5 packets transmitted,~~MULTICAST~~5 received,UP0% packet loss,~~LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~time 4006ms

~~link~~rtt min/~~ether 23:8c:d6:ae:76:bb brd ff:ff:ff:ff:ff:ff~~avg/max/mdev = 41.321/44.864/48.834/2.484 ms|}</ol>

~~inet '''192.168.1.11'''/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0~~==== Test method of desktop image ====

~~valid_lft 259192sec preferred_lft 259192sec~~# Click the network configuration icon in the upper right corner of the desktop (please do not connect the network cable when testing WIFI)

~~inet6 240e~~:~~3b7~~:~~3240~~[[File:~~c3a0:c401:a445:5002:ccdd/64 scope global dynamic noprefixroute~~pi3b-img183.png]]

~~valid_lft 259192sec preferred_lft 172792sec~~<ol start="2" style="list-style-type: decimal;"><li>Click '''More networks''' in the pop-up drop-down box to see all scanned WIFI hotspots, and then select the WIFI hotspot you want to connect to.</li>

~~inet6 fe80~~[[File:pi3b-img184.png]]</ol><ol start="3" style="list-style-type:~~42f1:6019:a80e:4c31~~decimal;"><li>Then enter the password of the WIFI hotspot, and then click '''Connect''' to start connecting to WIFI</~~64 scope link noprefixroute~~li>

~~valid_lft forever preferred_lft forever~~[[File:pi3b-img185.png]]</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]]</ol><ol start="5~~) Use~~ " style="list-style-type: decimal;"><li>If you can open other web pages after opening the ~~'''ping''' command to test the connectivity of the wifi network~~browser, ~~and the '''ping''' command can be interrupted through~~ it means that the ~~shortcut key '''Ctrl+C'''~~WIFI connection is normal</li>

~~orangepi@orangepi~~[[File:~~~$ '''ping www~~pi3b-img187-1.~~orangepi.org~~ png]]</ol>

~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0: 56(84) bytes of data.~~=== How to set a static IP address ===

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~{| class=~~1 ttl~~"wikitable" style=~~52 time=43~~"background-color:#ffffdc;width:800px;" |-| <big>'''Please do not set a static IP address by modifying the /etc/network/interfaces configuration file.~~5 ms~~'''</big>|}

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~==== Use the nmtui command to set a static IP address ==~~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~~# First run the '''nmtui''' command

~~64 bytes from 182.92.236.130 (182.92.236.130)~~: ~~icmp_seq~~:{| class=~~4 ttl~~"wikitable" style=~~52 time=45.6 ms~~"width:800px;" |-| orangepi@orangepi:~$ '''nmtui'''|}

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~<ol start=~~5 ttl~~"2" style=~~52 time=48.8 ms~~"list-style-type: decimal;"><li>Then select '''Edit a connection''' and press Enter</li>

^C[[File:pi3b-img188.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then select the network interface that needs to set a static IP address, for example, to set the static IP address of the '''Ethernet''' interface, select '''Wired connection 1'''.</li>

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

[[File:pi3b-img190.png]]</ol><ol start="5 ~~packets transmitted, 5 received, 0% packet loss, time 4006ms~~" style="list-style-type: decimal;"><li>Then use the Tab key to move the cursor to the '''<Automatic>''' position shown in the figure below to configure IPv4</li>

~~rtt min~~[[File:pi3b-img191.png]]</~~avg/max/mdev~~ ol><ol start="6" style= ~~41.321/44.864~~"list-style-type: decimal;"><li>Then press Enter, select '''Manual''' with the up and down arrow keys, and press Enter to confirm</~~48.834/2.484 ms~~li>

[[File:pi3b-img192.png]]<~~span id~~/ol><ol start="7" style="~~the-server-image-connects-to-wifi-in~~list-astyle-~~graphical-way~~type: decimal;"><~~/span~~li>~~====~~ The ~~server image connects to WIFI~~ display after selection is shown in ~~a graphical way ====~~the figure below</li>

~~1) First log in~~ [[File:pi3b-img193.png]]</ol><ol start="8" style="list-style-type: decimal;"><li>Then move the cursor to the ~~Linux system, there are the following three ways~~'''<Show>'''</li>

[[File:pi3b-img194.png]]</ol><ol start="9" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~If the development board is connected with a network cable, you can remotely log 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~~Then press Enter, ~~and the minicom cannot display~~ the ~~graphical~~ following setting interface~~)~~will pop up after entering</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~~>

[[File:pi3b-img195.png]]</ol><~~!--~~ ol start="10" style="list-style-type: decimal;"># # <li>Then ~~enter~~ you can set the IP address (Addresses), gateway (Gateway) and DNS server address in the ~~nmtui command~~ position shown in the ~~command line~~ figure below (there are many other setting options in it, please explore by yourself), '''Please set it according to ~~open~~ your specific needs, the value set in the ~~wifi connection interface~~figure below is just an example'''</li>

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

[[File:pi3b-img197.png]]</ol><ol start="312" style="list-style-type: decimal;"><li>~~Enter the nmtui command~~ Then click'''<Back>''' to return to ~~open~~ the previous selection interface ~~as shown below~~</li~~></ol~~>

[[File:pi3b-~~img177~~img198.png~~|345x215px~~]]</ol><ol start="13" style="list-style-type: decimal;"><li>Then select '''Activate a connection''', then move the cursor to'''<OK>''', and finally click Enter</li>

[[File:pi3b-img199.png]]</ol><ol start="414" style="list-style-type: decimal;"><li>~~Select~~ Then select the network interface that needs to be set, such as '''Wired connection 1''', then move the cursor to'''~~Activate a connect~~<Deactivate>''' , and press Enterto disable '''Wired connection 1'''</li~~></ol~~>

[[File:pi3b-~~img178~~img200.png~~|349x216px~~]]</ol><ol start="15" style="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-img201.png]]</ol><ol start="516" style="list-style-type: decimal;"><li>Then you can ~~see all~~ exit nmtui through the ~~searched WIFI hotspots~~'''<Back>''' and '''Quit''' buttons</li~~></ol~~>

[[File:pi3b-img202.png]] [[File:pi3b-img203.png]]<~~div class~~/ol><ol start="17" style="~~figure~~list-style-type: decimal;"><li>Then through '''ip addr show eth0''', you can see that the IP address of the network port has changed to the static IP address set earlier</li>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img179.png~~|~~426x270px|16]]~~orangepi@orangepi:~$ '''ip addr show eth0'''

~~</div><ol start="6" style="list-style-type~~3: ~~decimal~~eth0: <">~~<li>Select the WIFI hotspot you want to connect to~~BROADCAST,MULTICAST,UP, ~~then use the Tab key to position the cursor on '''Activate''' and press Enter</li></ol>~~LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~<div class="figure">~~:link/ether 5e:ac:14:a5:92:b3 brd ff:ff:ff:ff:ff:ff

~~[[File~~:~~pi3b-img180~~inet '''192.168.1.177'''/24 brd 192.168.1.~~png|474x298px|17]]~~255 scope global noprefixroute eth0

~~</div><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 '''Password''' and press Enter to start connecting to WIFI</li></ol>~~:valid_lft forever preferred_lft forever

~~<div class="figure">~~:inet6 241e:3b8:3240:c3a0:e269:8305:dc08:135e/64 scope global dynamic noprefixroute

~~[[File~~:~~pi3b-img181.png|480x308px|18]]~~:valid_lft 259149sec preferred_lft 172749sec

~~</div><ol start="8" style="list-style-type~~: ~~decimal;"><li>After the WIFI connection is successful, a "*" will be displayed in front of the connected WIFI name</li><~~inet6 fe80::957d:bbbe:4928:3604/~~ol>~~64 scope link noprefixroute

::valid_lft forever preferred_lft forever|}<~~div class~~/ol><ol start="18" style="~~figure~~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 '''Ctrl+C'''</li>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img182.png~~|~~443x283px|C~~orangepi@orangepi:~~\Users\orangepi\Desktop\用户手册插图\Zero3\未标题-9~~~$ '''ping 192.168.1.~~jpg未标题~~47 -~~9]]~~I eth0'''

~~</div><ol start="9" style="list-style-type~~PING 192.168.1.47 (192.168.1.47) from 192.168.1.188 eth0: ~~decimal;"><li>You can view the IP address~~ 56(84) bytes of ~~wifi through the '''ip addr show wlan0''' command</li></ol>~~data.

~~orangepi@orangepi~~64 bytes from 192.168.1.47:~~~$ '''ip addr show wlan0'''~~icmp_seq=1 ttl=64 time=0.233 ms

1164 bytes from 192.168.1.47: ~~wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~icmp_seq=2 ttl=64 time=0.263 ms

~~link/ether 24~~64 bytes from 192.168.1.47:~~8c:d3:aa:76:bb brd ff:ff:ff:ff:ff:ff~~icmp_seq=3 ttl=64 time=0.273 ms

~~inet '''~~64 bytes from 192.168.1.~~11'''/24 brd 192.168.1~~47: icmp_seq=4 ttl=64 time=0.~~255 scope global dynamic noprefixroute wlan0~~269 ms

~~valid_lft 259069sec preferred_lft 259069sec~~64 bytes from 192.168.1.47: icmp_seq=5 ttl=64 time=0.275 ms

~~inet6 240e:3b7:3240:c4a0:c401:a445:5002:ccdd/64 scope global dynamic noprefixroute~~^C

~~valid_lft 259071sec preferred_lft 172671sec~~--- 192.168.1.47 ping statistics ---

~~inet6 fe80::42f1:6019:a80e:4c31/64 scope link noprefixroute~~5 packets transmitted, 5 received, 0% packet loss, time 4042ms

~~valid_lft forever preferred_lft forever~~rtt min/avg/max/mdev = 0.233/0.262/0.275/0.015 ms|}</ol>

~~<ol start~~=~~"10" style~~=~~"list-style-type: decimal;"><li>~~== Use the ~~'''ping'''~~ nmcli command to ~~test the connectivity of the wifi network, and the '''ping''' command can be interrupted through the shortcut key '''Ctrl+C'''</li></ol>~~set a static IP address ====

<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''' is the name of the Ethernet interface</li>{| class="wikitable" style="width:800px;"|-|orangepi@orangepi:~$ '''~~ping www.~~nmcli con show''' NAMEUUID TYPE DEVICE '''orangepi~~.org~~ '''cfc4f922-ae48-46f1-84e1-2f19e9ec5e2awifi wlan0 '''Wired connection 1'''9db058b7-7701-37b8-9411-efc2ae8bfa30ethernet eth0 |}</ol></li></ol>

~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0~~<ol start="3" style="list-style-type: ~~56(84) bytes of data.~~decimal;"><li>Then enter the following command, where</li>

~~64 bytes from 182~~:a.92'''"Wired connection 1"''' means to set the static IP address of the Ethernet port.~~236.130~~ If you need to set the static IP address of the WIFI, please change it to the corresponding name of the WIFI network interface (~~182.92.236.130~~you can get it through the '''nmcli con show''' command)~~: icmp_seq=1 ttl=52 time=43.5 ms~~

~~64 bytes from 182.92.236~~:b.~~130 (182.92.236.130): icmp_seq=2 ttl=52 time=41~~After '''ipv4.~~3 ms~~addresse''' is the static IP address to be set, which can be modified to the value you want to set

~~64 bytes from 182.92.236~~:c.~~130 (182.92.236.130): icmp_seq=3 ttl=52 time=44~~'''ipv4.~~9 ms~~gateway''' indicates the address of the gateway

~~64 bytes from 182.92.236.130 (182.92.236.130)~~: ~~icmp_seq~~:{| class=~~4 ttl~~"wikitable" style=~~52 time=45.6 ms~~"width:800px;" |-| orangepi@orangepi:~$ '''nmcli con mod "Wired connection 1" \'''

~~64 bytes from 182~~'''ipv4.92addresses "192.~~236~~168.~~130 (182~~1.~~92.236.130): icmp_seq=5 ttl=52 time=48.8 ms~~110" \'''

^C'''ipv4.gateway "192.168.1.1" \'''

~~--- www~~'''ipv4.~~orangepi~~dns "8.~~org ping statistics ---~~8.8.8" \'''

~~5 packets transmitted, 5 received, 0% packet loss, time 4006ms~~'''ipv4.method "manual"'''|}~~rtt min~~</~~avg/max/mdev = 41.321/44.864/48.834/2.484 ms~~ol><~~span id~~ol start="~~test~~4" style="list-~~method~~style-~~of-desktop-image~~type: decimal;"><li>Then restart the Linux system</~~span~~li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo reboot'''|}</ol><ol start="5" style= ~~Test method of desktop image ====~~"list-style-type: decimal;"> ~~# Click~~ <li>Then re-enter the ~~network configuration icon in~~ Linux system and use the ~~upper right corner of~~ '''ip addr show eth0''' command to see that the ~~desktop (please do not connect~~ IP address has been set to the ~~network cable when testing WIFI)~~desired value</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ip addr show eth0'''

~~[[File~~3:~~pi3b-img183.png|377x166px]]~~eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~<ol start="2" style="list-style-type~~: ~~decimal;"><li>Click '''More networks''' in the pop-up drop-down box to see all scanned WIFI hotspots, and then select the WIFI hotspot you want to connect to.<~~link/~~li></ol>~~ether 5e:ae:14:a5:91:b3 brd ff:ff:ff:ff:ff:ff

~~[[File~~:~~pi3b-img184~~inet '''192.168.1.110'''/32 brd 192.168.1.~~png|576x353px]]~~110 scope global noprefixroute eth0

~~<ol start="3" 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>~~:valid_lft forever preferred_lft forever

~~[[File~~:~~pi3b-img185.png|320x163px]]~~inet6 240e:3b7:3240:c3a0:97de:1d01:b290:fe3a/64 scope global dynamic noprefixroute

~~<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></ol>~~:valid_lft 259183sec preferred_lft 172783sec

~~[[File~~:~~pi3b-img186.png|576x308px]]~~inet6 fe80::3312:861a:a589:d3c/64 scope link noprefixroute

::valid_lft forever preferred_lft forever|}</ol ~~start~~>~~<li>If you can open other web pages after opening the browser, it means that the WIFI connection is normal~~</~~li></ol~~span>

~~[[File:pi3b-img187.png|576x222px]]~~== SSH remote login development board ==

~~'''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~~-set-a-static-~~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.'''</~~span~~big>~~=== How to set a static IP address ===|}

~~'''Please do not set a static IP address by modifying the~~ </~~etc/network/interfaces configuration file.'''~~span>=== SSH remote login development board under Ubuntu ===

~~~~of the development board~~==== Use~~ # Then you can remotely log in to the ~~nmtui~~ Linux system through the ssh command ~~to set a static IP address ====~~

~~# First run the~~ ::{| class="wikitable" style="width:800px;" |-| test@test:~$ '''~~nmtui~~ssh [mailto:root@192.168.1.36 root@192.168.1.]xxx''' ~~command~~       (Need to be replaced with the IP address of the development board)

~~orangepi~~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>'''~~nmtui~~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>|}~~<ol start~~::{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Then select~~ '''~~Edit a~~ 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.''' ~~and press Enter~~</~~li></ol~~big> ~~[[File:pi3b-img188.png~~|~~227x247px]]~~}

<li>~~Then select~~ After successfully logging in to the ~~network interface that needs to set a static IP address, for example~~system, ~~to set~~ the ~~static IP address of~~ display is as shown in the ~~'''Ethernet''' interface, select '''Wired connection 1'''.~~figure below</li~~></ol~~>

~~[[File:pi3b-img189.png|310x149px]]~~<div class="figure">

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

~~[[File~~</div>{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-~~img190~~| <big>'''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, 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.~~png|316x144px]]~~Is it possible to connect:'''

~~<ol start="5" style="list-style-type: decimal;">~~

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

~~[[File~~root@orangepi:~~pi3b-img191~~~# '''reset_ssh.~~png|575x240px]]~~sh'''

~~<ol start="6" style="list-style-type: decimal;">~~

~~<li>Then press Enter, select '''Manual''' with the up and down arrow keys, and press Enter to confirm</li></ol>~~

~~[[File:pi3b-img192~~'''If it still doesn't work, try to reset the system.~~png~~'''</big>|~~576x237px]]~~}</ol>

~~<ol start~~=~~"7" style~~=~~"list-style-type: decimal;"><li>The display after selection is shown in the figure below</li></ol>~~= SSH remote login development board under Windows ===

~~[[File:pi3b-img193.png|575x240px]]~~# 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

~~<ol start="8" style="list-style-type~~: ~~decimal;"><li>Then move the cursor to the~~ :a. Open '''~~<Show>~~Session'''~~</li></ol>~~

~~[[File~~:~~pi3b-img194~~:b.~~png|576x241px]]~~Then select '''SSH''' in '''Session Setting'''

~~<ol start="9" style="list-style-type~~: ~~decimal;"><li>~~:c. Then ~~press Enter,~~ enter the IP address of the development board in the ~~following setting interface will pop up after entering</li></ol>~~'''Remote host'''

~~[[File~~:~~pi3b-img195~~:d.~~png|575x450px]]~~Then enter the user name '''root''' or '''orangepi''' of the Linux system in '''Specify username'''

~~<ol start="10" style="list-style-type~~: ~~decimal;">~~<li>Then you can set the IP address (Addresses), gateway (Gateway) and DNS server address in the position shown in the figure below (there are many other setting options in it, please explore by yourself)，:e. Finally click '''~~Please set it according to your specific needs, the value set in the figure below is just an example~~OK'''~~</li></ol>~~

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

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

~~[[File~~</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:~~pi3b~~#ffffdc;width:800px;" |-~~img197~~| <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.~~png~~'''</big>|~~576x116px]]~~}

<~~ol start~~div class="12figure" ~~style="list-style-type: decimal;"><li>Then click'''<Back>''' to return to the previous selection interface</li></ol~~>

[[File:pi3b-~~img198~~img206.png~~|330x325px~~]]

</div></ol><ol start="134" style="list-style-type: decimal;"><li>~~Then select '''Activate a connection'''~~After successfully logging in to the system, ~~then move~~ the ~~cursor to'''<OK>''', and finally click Enter~~display is as shown in the figure below</li~~></ol~~>

[[File:pi3b-~~img199~~img207.png~~|331x248px~~]]</ol>

~~<ol start~~=~~"14" style~~=~~"list-style-type: decimal;"><li>Then select~~ The method of uploading files to the ~~network interface that needs to be set, such as '''Wired connection 1''', then move~~ Linux system of the ~~cursor to'''<Deactivate>''', and press Enter to disable '''Wired connection 1'''</li></ol>~~development board ==

~~[[File:pi3b~~=== How to upload files to the development board Linux system in Ubuntu PC ===

<~~ol start~~span id="~~15" style="list~~how-to-upload-files-using-the-~~style~~scp-~~type: decimal;~~command"><li/span>~~Then please do not move the cursor, and then press the Enter key~~ ==== How to ~~re-enable '''Wired connection 1''', so that~~ upload files using the ~~static IP address set earlier will take effect</li></ol>~~scp command ====

~~[[File:pi3b-img201~~# Use the scp command to upload files from the Ubuntu PC to the Linux system of the development board.~~png|576x224px]]~~The specific commands are as follows

~~<ol start="16" style="list-style-type~~: ~~decimal;"><li>Then you can exit nmtui through the~~:a. '''~~<Back>~~file_path''' ~~and '''Quit''' buttons</li></ol>~~: need to be replaced with the path of the file to be uploaded

~~[[File~~:~~pi3b-img202~~:b.~~png|300x253px]] [[File~~'''orangepi''':~~pi3b-img203.png|227x252px]]~~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

~~<ol start="17" style="list-style-type~~: ~~decimal;"><li>Then through~~ :c. '''~~ip addr show eth0~~192.168.xx.xx'''~~, you can see that~~ : It is the IP address of the ~~network port has changed~~ development board, please modify it according to the ~~static IP address set earlier</li></ol>~~actual situation

~~orangepi@orangepi~~:~$ :d. '''~~ip addr show eth0~~/home/orangepi''': The path in the Linux system of the development board, which can also be modified to other paths

3: ~~eth0~~: ~~&lt~~{| class="wikitable" style="width:800px;~~BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~" |-| test@test:~$ '''scp file_path orangepi@192.168.xx.xx:/home/orangepi/'''|}

~~link~~<ol start="2" style="list-style-type: decimal;"><li>If you want to upload a folder, you need to add the -r parameter</~~ether 5e:ac:14:a5:92:b3 brd ff:ff:ff:ff:ff:ff~~li>

~~inet~~ {| class="wikitable" style="width:800px;" |-| test@test:~$ '''scp -r dir_path orangepi@192.168.1xx.~~177~~xx:/home/orangepi/'''|}</ol><ol start="3" style="list-style-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'''|}</~~24 brd 192.168.1.255 scope global noprefixroute eth0~~ol>

~~valid_lft forever preferred_lft forever~~==== How to upload files using filezilla ====

~~inet6 241e:3b8:3240:c3a0:e269:8305:dc08:135e/64 scope global dynamic noprefixroute~~# First install filezilla in Ubuntu PC

~~valid_lft 259149sec preferred_lft 172749sec~~::{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt install -y filezilla'''|}

~~inet6 fe80~~<ol start="2" style="list-style-type:~~:957d:bbbe:4928:3604~~decimal;"><li>Then use the following command to open filezilla</~~64 scope link noprefixroute~~li>

~~valid_lft forever preferred_lft forever~~{| class="wikitable" style="width:800px;" |-| test@test:~$ '''filezilla'''|}</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 start~~div class="18figure" ~~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 '''Ctrl+C'''</li></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''ping 192.168.1~~pi3b-img208.~~47 -I eth0'''~~png]]

~~PING 192.168.1.47 (192.168.1.47) from 192.168.1.188 eth0~~</div></ol><ol start="4" style="list-style-type: ~~56(84) bytes~~ decimal;"><li>The method of ~~data.~~connecting the development board is shown in the figure below</li>

~~64 bytes from 192.168.1.47: icmp_seq~~<div class=~~1 ttl=64 time=0.233 ms~~"figure">

~~64 bytes from 192.168.1.47~~[[File: ~~icmp_seq=2 ttl=64 time=0~~pi3b-img209.~~263 ms~~png]]

~~64 bytes from 192.168.1.47: icmp_seq~~</div></ol><ol start=~~3 ttl~~"5" style=~~64 time=0.273 ms~~"list-style-type: decimal;"><li>Then choose to '''save the password''', and then click '''OK'''</li>

~~64 bytes from 192.168.1~~[[File:pi3b-img210.~~47: icmp_seq~~png]]</ol><ol start=~~4 ttl~~"6" style=~~64 time=0.269 ms~~"list-style-type: decimal;"><li>Then choose to always '''trust this host''', and then click '''OK'''</li>

~~64 bytes from 192.168.1.47: icmp_seq~~<div class=~~5 ttl=64 time=0.275 ms~~"figure">

^C[[File:pi3b-img211.png]]

</div></ol><ol start="7" style="list-style-~~- 192.168.1.47 ping statistics ---~~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>

~~5 packets transmitted, 5 received, 0% packet loss, time 4042ms~~<div class="figure">

~~rtt min/avg/max/mdev = 0~~[[File:pi3b-img212.~~233/0.262/0.275/0.015 ms~~png]]

<~~span id~~/div></ol><ol start="8" style="~~use-the-nmcli-command-to-set-a-static~~list-ipstyle-~~address~~type: decimal;"><~~/span~~li>~~==== Use~~ 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 ~~nmcli command~~ file to ~~set a static IP address ====~~the development board.</li>

<~~ol style~~div class="~~list-style-type: decimal;~~figure"><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''' is the name of the Ethernet interface</li></ol></li></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''nmcli con show'''~~pi3b-img213.png]]

~~NAME UUID TYPE DEVICE~~</div></ol><ol start="9" style="list-style-type: 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, so I won'~~''orangepi''' cfc4f922~~t go into details here</li></ol>

~~'''Wired connection 1''' 9db058b7-7701-37b8-9411-efc2ae8bfa30 ethernet eth0~~=== The method of uploading files from Windows PC to the Linux system of the development board ===

<~~ol start~~span id="~~3" style="list~~how-to-upload-files-using-~~style~~filezilla-~~type: decimal;~~1">~~<li>Then enter the following command, where~~</~~li></ol~~span>==== How to upload files using filezilla ====

~~<blockquote>a. '''"Wired connection 1"''' means to set~~ # First download the ~~static IP address~~ installation file of the ~~Ethernet port. If you need to set the static IP address~~ Windows version of the ~~WIFI~~filezilla software, ~~please change it to the corresponding name of the WIFI network interface (you can get it through~~ the ~~'''nmcli con show''' command)~~download link is as follows

~~b. After~~ ::{| class="wikitable" style="width:800px;" |-| '''~~ipv4~~https://filezilla-project.org/download.~~addresse~~php?type=client''' ~~is the static IP address to be set, which can be modified to the value you want to set~~|}

~~c. '''ipv4.gateway''' indicates the address of the gateway~~<~~/blockquote~~div class="figure">~~orangepi@orangepi:~$ '''nmcli con mod "Wired connection 1" \'''~~

~~'''ipv4~~::[[File:pi3b-img214.~~addresses "192.168.1.110" \'''~~png]]

~~'''ipv4.gateway "192.168.1.1" \'''~~</div><div class="figure">

~~'''ipv4~~::[[File:pi3b-img215.~~dns "8.8.8.8" \'''~~png]]

~~'''ipv4.method &quot~~</div><ol start="2" style="list-style-type: decimal;~~manual"'''~~"><li>The downloaded installation package is as follows, and then double-click to install directly</li>

~~<ol start~~{| class="4wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then restart the Linux system</li></ol>~~|-| '''FileZilla_Server_1.5.1_win64-setup.exe'''|}

~~orangepi@orangepi:~$~~ During the installation process, please select '''~~sudo reboot~~Decline''' on the following installation interface, and then select '''Next>'''

<~~ol start~~div class="5figure" ~~style="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~~>

~~orangepi@orangepi~~[[File:~~~$ '''ip addr show eth0'''~~pi3b-img216.png]]

</div></ol><ol start="3" style="list-style-type: ~~eth0: &lt~~decimal;~~BROADCAST,MULTICAST,UP~~"><li>The interface after filezilla is opened is as follows,~~LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~and the display under the remote site on the right is empty</li>

~~link/ether 5e:ae:14:a5:91:b3 brd ff:ff:ff:ff:ff:ff~~<div class="figure">

~~inet '''192~~[[File:pi3b-img217.~~168.1.110'''/32 brd 192.168.1.110 scope global noprefixroute eth0~~png]]

~~valid_lft forever preferred_lft forever~~</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>

~~inet6 240e:3b7:3240:c3a0:97de:1d01:b290:fe3a/64 scope global dynamic noprefixroute~~<div class="figure">

~~valid_lft 259183sec preferred_lft 172783sec~~[[File:pi3b-img209.png]]

~~inet6 fe80::3312:861a:a589~~</div></ol><ol start="5" style="list-style-type:~~d3c~~decimal;"><li>Then choose to '''save the password''', and then click '''OK'''</~~64 scope link noprefixroute~~li>

~~valid_lft forever preferred_lft forever~~<div class="figure">

~~== SSH remote login development board ==~~img218.png]]

</div></ol><ol start="6" style="list-style-type: decimal;"><li>Then choose to always '''trust this host'''~~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.~~click '''OK'''</li>

<~~span id~~div class="~~ssh-remote-login-development-board-under-ubuntu~~figure">~~=== SSH remote login development board under Ubuntu ===~~

~~# Obtain the IP address of the development board# Then you can remotely log in to the Linux system through the ssh command~~[[File:pi3b-img219.png]]

~~test@test~~</div></ol><ol start="7" style="list-style-type:~~~$ '''ssh [mailto:root@192.168.1.36 root@192.168.1.]xxx''' (Need to be replaced with~~ decimal;"><li>After the connection is successful, you can see the ~~IP address~~ directory structure of the development board)Linux file system on the right side of the filezilla software</li>

~~root@192.168.1.xx's password: (Enter the password here, the default password is orangepi)~~<div class="figure">

~~'''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~~[[File:pi3b-img220.~~'''~~png]]

~~'''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.'''~~</div></ol><ol start="38" style="list-style-type: decimal;"><li>~~After successfully logging in~~ Then select the path to be uploaded to the ~~system~~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 ~~display is as shown in~~ upload option to start uploading the ~~figure below~~file to the development board.</li~~></ol~~>

[[File:pi3b-~~img204~~img221.png~~|405x207px|L467QDF65C(YR79U]TH[TND~~]]

</div></ol>~~'''If ssh cannot log in to the Linux system normally, please first check whether the IP address of~~ <ol start="9" style="list-style-type: decimal;"><li>After the ~~development board can be pinged. If the ping~~ upload is okcomplete, you can ~~log~~ go to the corresponding path in to the Linux system ~~through the serial port or HDMI display and then enter the following command on~~ of the development board ~~and try again. Is it possible~~ to ~~connect:'''~~view the uploaded file</li><li>The method of uploading a folder is the same as that of uploading a file</li></ol>

~~root@orangepi:~# '''reset_ssh.sh'''~~

~~'''If it still doesn't work, try to reset the system.'''~~== HDMI test ==

=== ~~SSH remote login development board under Windows~~ HDMI display test ===

# ~~First obtain the IP address of the~~ Use HDMI to HDMI cable to connect Orange Pi development boardand HDMI monitor

~~2) Under Windows, you can use MobaXterm to remotely log in to the development board, first create a new ssh session~~::[[File:pi3b-img10.png]]

~~a. Open '''Session'''~~<ol start="2" style="list-style-type: decimal;"><li>After starting the Linux system, if the HDMI monitor has image output, it means that the HDMI interface is in normal use</li>

~~b. Then select '''SSH~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <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 ~~'''Session Setting~~, that is to say, the HDMI output of other devices cannot be displayed on the notebook screen.'''

~~c. Then enter~~ '''When you want to connect the ~~IP address~~ HDMI of the development board to the HDMI port of the laptop, please make sure that your laptop supports the HDMI in ~~the~~ function.'''</big>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~Remote host~~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.'''</big>|}</ol>

~~d. Then enter the user name '''root''' or '''orangepi''' of the Linux system in '''Specify username'''~~

~~e. Finally click '''OK'''~~=== HDMI to VGA display test ===

<~~div class~~ol style="~~figure~~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>

[[File:pi3b-~~img205~~img222.png~~|553x280px|14~~]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>A VGA cable</li>

[[File:pi3b-img223.png]]</~~div~~ol><ol start="3" style="list-style-type: lower-alpha;"><li>A monitor or TV that supports VGA interface</li></ol></li></ol>

<li>~~</li><li>Then you will be prompted~~ HDMI to ~~enter a password. The default passwords for root and orangepi users are orangepi~~VGA display test as shown below</li~~></ol~~>

~~'''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~~[[File:pi3b-img224.~~'''~~png]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <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. 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>|}</ol><~~div class~~span id="~~figure~~hdmi-resolution-setting-method">

~~[[File:pi3b-img206.png|578x150px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\just press Enter after inputting..jpgjust press Enter after inputting.]]~~=== HDMI resolution setting method ===

~~</div><ol start="4" style="list-style-type: decimal;"><li>After successfully logging~~ # First open '''Display''' in ~~to the system, the display is as shown in the figure below</li></ol>~~'''Settings'''

::[[File:pi3b-~~img207~~img225.png~~|576x334px~~]]

<~~span id~~ol start="~~the~~2" style="list-~~method~~style-type: decimal;"><li>Then you can see the current resolution of~~-uploading-files-to-~~the~~-linux-~~system~~-of-the-development-board">~~</~~span~~li>

[[File:pi3b-img226.png]]</ol><ol start="3" style= ~~The method~~ "list-style-type: decimal;"><li>Click the drop-down box of ~~uploading files~~ Resolution to see all resolutions currently supported by the ~~Linux system of the development board ==~~monitor</li>

[[File:pi3b-img227.png]]</ol><~~span id~~ol start="~~how~~4" style="list-tostyle-~~upload-files-to-the-development-board-linux-system-in-ubuntu-pc~~type: decimal;"><li>Then select the resolution you want to set, and click Apply</~~span~~li>~~=== How to upload files to the development board Linux system in Ubuntu PC ===~~

[[File:pi3b-img228.png]]</ol><~~span id~~ol start="~~how-to-upload-files-using-the~~5" style="list-~~scp~~style-~~command~~type: decimal;"><li>After the new resolution is set, select '''Keep the configuration'''</~~span~~li>~~==== How to upload files using the scp command ====~~

~~# Use the scp command~~ [[File:pi3b-img229.png]]</ol>

~~<blockquote>a. '''file_path''': need~~ == How to ~~be replaced with the path of the file to be uploaded~~use Bluetooth ==

~~b. '''orangepi''': It is the user name~~ === Test method of ~~the development board, and it can also be replaced with other ones, such as root~~desktop image ===

~~c. '''192.168.xx.xx''': It is~~ # Click the Bluetooth icon in the ~~IP address~~ upper right corner of the ~~development board, please modify it according to the actual situation~~desktop.

~~d. '''/home/orangepi'''~~: ~~The path in the Linux system of the development board, which can also be modified to other paths</blockquote>test@test~~:~~~$ '''scp file_path orangepi@192~~[[File:pi3b-img230.~~168.xx.xx:/home/orangepi/'''~~png]]

<li>~~If you want to upload a folder, you need to add~~ Then select the ~~-r parameter~~adapter</li>~~</ol>~~ ~~test@test:~$ '''scp -r dir_path orangepi@192.168.xx.xx:/home/orangepi/'''~~

[[File:pi3b-img231.png]]

</ol>

<li>~~There are more usages of scp~~If there is a prompt on the following interface, please ~~use the following command to view the man manual~~select '''Yes'''</li~~></ol~~>

~~test@test~~[[File:~$ pi3b-img232.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then set '''Visibility Setting''' as '''~~man scp~~Always visible'''in the Bluetooth adapter settings interface, and then close it</li>

[[File:pi3b-img233.png]]</ol><~~span id~~ol start="5" style="~~how-to-upload-files~~list-~~using~~style-~~filezilla~~type: decimal;"><li>Then open the configuration interface of the Bluetooth device</~~span~~li>~~==== How to upload files using filezilla ====~~

~~# First install filezilla in Ubuntu PC~~[[File:pi3b-img234.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Click '''Search''' to start scanning the surrounding Bluetooth device</li>

~~test@test~~[[File:~$ pi3b-img235.png]]</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 '''~~sudo apt install -y filezilla~~Pair'''to start pairing, and the demonstration here is to pair with an Android phone</li>

[[File:pi3b-img236.png]]</ol><ol start="28" style="list-style-type: decimal;"><li>~~Then use~~ 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 ~~following command~~ mobile phone also needs to ~~open filezilla~~be confirmed</li~~></ol~~>

~~test@test~~[[File:~$ pi3b-img237.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>After pairing with the mobile phone, you can choose the paired Bluetooth device, then right-click and select '''~~filezilla~~Send a File'''to start sending a picture to the phone</li>

[[File:pi3b-img238.png]]</ol><ol start="310" style="list-style-type: decimal;"><li>The interface ~~after filezilla is opened is as follows, and the display under the remote site on~~ of the ~~right~~ sending picture is ~~empty~~shown below</li~~></ol~~>

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

~~[[File:pi3b-img208.png|576x453px|截图 2022-12-03 19-04-40]]~~== USB interface test ==

~~</div><ol start~~{| class="4wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>'''The ~~method~~ USB interface can be connected to a USB hub to expand the number of ~~connecting the development board is shown in the figure below~~USB interfaces.'''</~~li></ol~~big>|}

<~~div class~~span id="~~figure~~connect-the-usb-mouse-or-keyboard-test">=== Connect the USB mouse or keyboard test ===

~~[[File:pi3b-img209.png|575x128px|图片565]]~~# 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)

<~~/div><ol start~~span id="~~5" style="list~~connect-the-usb-storage-~~style~~device-~~type: decimal;~~test">~~<li>Then choose to '''save the password''', and then click '''OK'''</li~~></olspan>

~~[[File:pi3b-img210.png|249x181px]]~~=== Connect the USB storage device test ===

~~<ol start="6" style="list-style-type: decimal;">~~# First insert the U disk or USB mobile hard disk into the USB interface of the Orange Pi development board~~<li>Then choose to always '''trust this host'''~~# Execute the following command, ~~and then click '''OK'''</li></ol>~~if you can see the output of sdX, it means that the U disk is recognized successfully

::{| class="wikitable" style="width:800px;"|-|orangepi@orangepi:~$ '''cat /proc/partitions | grep "sd*"''' major minor #blocksname 8<~~div class~~span style="margin-right: 60px;">030044160 '''sda''' 8130043119 '''sda1''' |}

~~[[File~~<ol start="3" style="list-style-type:~~pi3b-img211.png|278x150px|IMG_256]]~~decimal;"><li>Use the mount command to mount the U disk into '''/mnt''', and then you can view the file in the U disk</li>

~~</div><ol start~~{| class="7wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<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<~~|-| orangepi@orangepi:~$ '''sudo mount /dev/sda1 /~~li><~~mnt/~~ol>~~'''

~~<div class="figure">~~orangepi@orangepi:~$ '''ls /mnt/'''

~~[[File~~test.txt|}</ol><ol start="4" style="list-style-type:~~pi3b~~decimal;"><li>After the mounting, you can view the capacity usage and mount point of the U disk through the '''df -~~img212.png~~h''' command</li>{| class="wikitable" style="width:800px;" |-|~~533x330px~~orangepi@orangepi:~$ '''df -h |~~IMG_256]]~~grep "sd"'''

/dev/sda1     29G    208K    29G    1% /mnt|}</~~div~~ol><~~ol start~~span id="~~8" style="list~~usb-wireless-network-~~style~~card-~~type: decimal;~~test"><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~~span>

~~<div class~~=~~"figure">~~== USB wireless network card test ===

~~[[File:pi3b-img213~~The currently '''tested''' USB wireless network cards are shown below.~~png|485x380px|IMG_256]]~~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 driver

~~</div>~~{| class="wikitable" style="width:800px;text-align: center;"~~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~~|-| No.| Model||-| 1| RTL8723BU

~~10) The method of uploading a folder is the same as that of uploading a file, so I won’t go into details here~~Support 2.4G WIFI+BT4.0

~~=== The method of uploading files from Windows PC to the Linux system of the development board ===~~| 2| RTL8811

~~==== How to upload files using filezilla ====~~Support 2.4G +5G WIFI

~~# First download the installation file of the Windows version of the filezilla software, the download link is as follows~~| [[File:pi3b-img241.png]]|-| 3| RTL8821CU

~~https://filezilla-project~~Support 2.~~org/download.php?type=client~~4G +5G WIFI

~~<div class="figure">~~Support BT 4.2

~~[[File:pi3b-img214.png~~|~~472x171px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-15.jpg未标题-15]]~~ ~~</div>~~

[[File:pi3b-~~img215~~img242.png~~|393x283px|图片5552~~]]

</div>

~~<ol start="2" style="list-style-type: decimal;"><li>The downloaded installation package is as follows, and then double-click to install directly</li></ol>~~|}

~~'''FileZilla_Server_1.5.1_win64~~==== RTL8723BU test ====

~~During~~ # First insert the ~~installation process~~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, ~~please select '''Decline''' on~~ through the lsmod command, you can see that the following ~~installation interface, and then select '''Next>'''~~kernel modules have been automatically loaded

::{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''lsmod'''Module Size <~~div class~~span style="margin-right: 45px;">Used by rfcomm 5734416 rtl8xxxu 1064960 rtk_btusb 614400 |}

~~[[File:pi3b-img216.png|319x251px|IMG_256]]~~

~~</div>~~

<li>~~The interface after filezilla is opened is as follows~~Through the dmesg command, ~~and the display under~~ you can see the ~~remote site on~~ loading information of the ~~right is empty~~RTL8723BU module</li~~></ol~~>

~~<div~~ {| class="~~figure~~wikitable">style="width:800px;" |-| orangepi@orangepi:~$ '''dmesg'''

~~[[File:pi3b-img217~~.~~png|451x357px|IMG_256]]~~.....

~~</div><ol start="4" style="list~~[ 83.438901] usb 2-~~style~~1: new high-speed USB device number 2 using ehci-~~type: decimal;"><li>The method of connecting the development board is shown in the figure below:</li></ol>~~platform

~~<div class~~[ 83.588375] usb 2-1: New USB device found, idVendor=~~"figure">~~0bda, idProduct=b720, bcdDevice= 2.00

[~~[File:pi3b-img209~~83.~~png|575x128px|图片565]~~588403]usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

~~</div><ol start="5" style="list~~[ 83.588422] usb 2-~~style-type~~1: Product: ~~decimal;"><li>Then choose to '''save the password''', and then click '''OK'''</li></ol>~~802.11n WLAN Adapter

~~<div class="figure">~~[ 83.588443] usb 2-1: Manufacturer: Realtek

[~~[File:pi3b-img218~~83.~~png|207x146px|IMG_256]~~588460]usb 2-1: SerialNumber: 00e04c000001

~~</div><ol start~~[ 83.601974] Bluetooth: hci0: RTL: examining hci_ver=06 hci_rev=~~"6" style~~000b lmp_ver=~~"list-style-type: decimal;"><li>Then choose to always '''trust this host''', and then click '''OK'''</li></ol>~~06 lmp_subver=8723

~~<div class~~[ 83.603894] Bluetooth: hci0: RTL: rom_version status=~~"figure">~~0 version=1

[~~[File~~83.603920] Bluetooth: hci0: RTL:~~pi3b-img219~~loading rtl_bt/rtl8723b_fw.~~png|221x109px|IMG_256]]~~bin

~~</div><ol start="7" style="list-style-type~~[ 83.610108] Bluetooth: hci0: RTL: ~~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><~~loading rtl_bt/~~ol>~~rtl8723b_config.bin

~~<div class="figure">~~[ 83.611274] Bluetooth: hci0: RTL: cfg_sz 68, total sz 22564

[~~[File~~83.658494] rtk_btusb:~~pi3b~~Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-~~img220.png|446x329px|图片3]]~~142432

~~</div><ol start="8" style="list-style-type~~[ 83.658651] usbcore: ~~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 Windows 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>registered new interface driver rtk_btusb

~~<div class="figure">~~[ 83.667124] usb 2-1: This Realtek USB WiFi dongle (0x0bda:0xb720) is untested!

[~~[File~~83.667137] usb 2-1:~~pi3b-img221~~Please report results to Jes.Sorensen@gmail.~~png|501x369px|IMG_256]]~~com

~~</div><ol start="9" style="list~~[ 83.890140] usb 2-~~style-type~~1: Vendor: ~~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>~~Realtek

~~== HDMI test ==~~1: Product: 802.11n WLAN Adapter

~~=== HDMI display test ===~~1: rtl8723bu_parse_efuse: dumping efuse (0x200 bytes):

~~# Use HDMI to HDMI cable to connect Orange Pi development board and HDMI monitor~~......

[~~[File:pi3b-img10~~83.~~png|199x129px]~~890412]usb 2-1: RTL8723BU rev E (SMIC) 1T1R, TX queues 3, WiFi=1, BT=1, GPS=0, HI PA=0

~~<ol start="~~[ 83.890417] usb 2~~" style="list~~-~~style-type~~1: RTL8723BU MAC: 00:13:ef:f4:58: ~~decimal;"><li>After starting the Linux system, if the HDMI monitor has image output, it means that the HDMI interface is in normal use</li></ol>~~ae

'''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[ 83.~~'''~~890421] usb 2-1: rtl8xxxu: Loading firmware rtlwifi/rtl8723bu_nic.bin

~~'''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~~[ 83.~~'''~~895289] usb 2-1: Firmware revision 35.0 (signature 0x5301)

~~'''When the HDMI is not displayed, please check whether the HDMI cable is plugged in tightly~~[ 84. ~~After confirming that there is no problem with the connection, you can change a different screen and try to see if it is displayed.'''~~050893] Bluetooth: hci0: RTL: fw version 0x0e2f9f73

~~=== HDMI to VGA display test ===~~[ 84.266905] Bluetooth: RFCOMM TTY layer initialized

~~<ol style="list-style-type~~[ 84.266949] Bluetooth: ~~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>~~RFCOMM socket layer initialized

[~~[File~~84.266999] Bluetooth:~~pi3b-img222~~RFCOMM ver 1.~~png|155x104px]]~~11

~~<ol start="2" style="list-style-type~~[ 84.884270] usbcore: ~~lower-alpha;"><li>A VGA cable</li></ol>~~registered new interface driver rtl8xxxu

[~~[File~~84.912046] rtl8xxxu 2-1:1.2 wlx0013eff458ae:~~pi3b~~renamed from wlan0|}</ol><ol start="4" style="list-style-~~img223~~type: decimal;"><li>Then you can see the RTL8723BU WIFI device node through the '''sudo ifconfig''' command.~~png~~Please refer to [[Orange Pi 3B#WIFI connection test|~~148x133px~~'''the WIFI connection test chapter''']]for WIFI connection and testing methods</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ifconfig wlx0013eff458ae'''

~~<ol start~~wlx0013eff458ae: flags=~~"3" style="list-style-type: lower-alpha~~4099<UP,BROADCAST,MULTICAST>">~~<li>A monitor or TV that supports VGA interface</li></ol>~~mtu 1500

~~<ol start="2" style="list-style-type~~: ~~decimal;"><li>HDMI to VGA display test as shown below</li></ol>~~:ether 00:13:ef:f4:58:ae txqueuelen 1000 (Ethernet)

~~[[File~~:~~pi3b-img224~~:RX packets 0 bytes 0 (0.~~png|576x339px]]~~0 B)

'''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.'''::RX errors 0 dropped 0 overruns 0 frame 0

~~=== HDMI resolution setting method ===~~::TX packets 0 bytes 0 (0.0 B)

~~# First 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 '''~~Display~~hciconfig''' in command</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~Settings~~sudo apt update && sudo apt install bluez'''

~~[[File~~orangepi@orangepi:~~pi3b-img225.png|576x370px]]~~~$ '''hciconfig'''

hci0: Type: Primary Bus: '''<~~ol start="2"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>Then you can see the current resolution of the system</li>~~USB</olspan>'''

~~[[File~~:~~pi3b-img226.png|382x254px]]~~:BD Address: 00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16

~~<ol start="3" style="list-style-type~~: ~~decimal;"><li>Click the drop-down box of Resolution to see all resolutions currently supported by the monitor</li></ol>~~:DOWN

~~[[File~~:~~pi3b-img227.png|415x274px]]~~:RX bytes:1252 acl:0 sco:0 events:125 errors:0

::TX bytes:23307 acl:0 sco:0 commands:125 errors:0|}</ol><ol start="46" style="list-style-type: decimal;"><li>~~Then select~~ You can also see the Bluetooth icon on the ~~resolution you want to set~~desktop. At this time, Bluetooth has not been opened, ~~and click Apply~~so a red '''x</lispan>''' will be displayed</olli>

[[File:pi3b-~~img228~~img243.png~~|415x277px~~]]</ol><ol start="7" style="list-style-type: decimal;"><li>Click '''Turn Bluetooth On''' to turn on Bluetooth</li>

[[File:pi3b-img244.png]]</ol><ol start="58" style="list-style-type: decimal;"><li>~~After the new resolution~~ The display after turning on Bluetooth is ~~set, select '''Keep the configuration'''~~as follows</li~~></ol~~>

[[File:pi3b-~~img229~~img245.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Please refer to the [[Orange Pi 3B#How to use Bluetooth|~~447x243px~~'''Bluetooth use method''']]for Bluetooth test method, so I won't go into details here.</li></ol>

~~== How to use Bluetooth ==~~

~~~~=== ~~Test method of desktop image~~ RTL8811 test ====

# ~~Click~~ First insert the ~~Bluetooth icon in~~ RTL8811 wireless network card module into the ~~upper right corner~~ USB interface of the ~~desktop~~development board.# Then the Linux system 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 lsmod command

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-~~img230.png~~|~~330x128px]]~~orangepi@orangepi:~$ '''lsmod'''<~~ol start~~span style="2margin-right: 100px;" >Module Size Used by <lispan style="margin-right: 100px;">8821cu ~~Then select the adapter~~1839104 </lispan>0</olspan> ~~[[File:pi3b-img231.png~~|~~375x165px]]~~}

<li>~~If there is a prompt below~~Through the dmesg command, ~~select~~ you can see the loading information of the RTL8811 module</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~Yes~~dmesg'''~~</li></ol>~~

[~~[File~~118.618194] usb 2-1:~~pi3b~~new high-~~img232.png|248x85px]]~~speed USB device number 2 using ehci-platform

~~<ol start~~[ 118.767152] usb 2-1: New USB device found, idVendor=~~"4" style~~0bda, idProduct=~~"list-style-type: decimal;"><li>Then set '''Visibility Setting''' as '''Always visible''' in the Bluetooth adapter settings interface~~c811, ~~and then close it</li></ol>~~bcdDevice= 2.00

[~~[File:pi3b-img233~~118.~~png|243x229px]~~767181]usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

~~<ol start="5" style="list~~[ 118.767199] usb 2-~~style-type~~1: Product: ~~decimal;"><li>Then open the configuration interface of the Bluetooth device</li></ol>~~802.11ac NIC

[~~[File:pi3b-img234~~118.~~png|438x179px]~~767219]usb 2-1: Manufacturer: Realtek

~~<ol start="6" style="list~~[ 118.767235] usb 2-~~style-type~~1: SerialNumber: ~~decimal;"><li>Click '''Search''' to start scanning the surrounding Bluetooth device</li></ol>~~123456

[~~[File:pi3b-img235~~119.~~png|322x217px]~~500530]usbcore: registered new interface driver rtl8821cu

[ 119.525498] rtl8821cu 2-1:1.0 wlx1cbfced9d260: renamed from wlan0|}</ol><ol start="74" style="list-style-type: decimal;"><li>Then ~~select~~ you can see the ~~Bluetooth~~ WiFi device ~~you want~~ node through the '''sudo ifconfig''' command. Please refer to ~~connect. If you right -click~~ the ~~mouse, you will pop up the operating interface of this Bluetooth device. Select~~ [[Orange Pi 3B#WIFI connection test|'''~~Pair~~WiFi connection test chapter''' ~~to start pairing~~]] for WIFI connection and testing methods. ~~Here, it is demonstrated with the Android phone~~I won't go into details her</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ifconfig wlx1cbfced9d260'''

~~[[File~~wlx1cbfced9d260:~~pi3b-img236.png|338x263px]]~~flags=4099<UP,BROADCAST,MULTICAST> mtu 1500

~~<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>:ether 1c:bf:ce:d9:d2:60 txqueuelen 1000 (Ethernet)

~~[[File~~:~~pi3b-img237~~:RX packets 0 bytes 0 (0.~~png|417x152px]]~~0 B)

~~<ol start="9" style="list-style-type~~: ~~decimal;"><li>After pairing with the mobile phone, you can choose the paired Bluetooth device, then right -click and select '''Send a File''' to start sending a picture to the phone</li></ol>~~:RX errors 0 dropped 0 overruns 0 frame 0

~~[[File~~:~~pi3b-img238~~:TX packets 0 bytes 0 (0.~~png|439x259px]]~~0 B)

::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0|}</ol ~~start="10" style~~>~~<li>The interface of the sending picture is shown below~~</~~li></ol~~span>

~~[[File:pi3b-img239.png|437x253px]]~~==== RTL8821CU test ====

~~~~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 ~~interface test ==~~module is not in Driver CDROM Mode

::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~The USB interface can connect USB Hub to expand the number of USB interfaces.~~lsusb | grep "Realtek"'''

~~=== Connect the USB mouse or keyboard test ===~~| orangepi@orangepi:~$ '''lsusb | grep "Realtek"'''

~~# Insert the keyboard of the USB interface into the USB interface of Orange PI development board# Connect Orange PI development board to HDMI display# If the mouse or keyboard can normal operating systems, the USB interface is used normally~~ Bus 002 Device 002: ID 0bda:1a2b Realtek Semiconductor Corp. RTL8188GU 802.11n WLAN Adapter (~~the mouse can only be used in the system of the desktop version~~'''Driver CDROM Mode''')

~~~~

~~=== Connect the USB storage device test ===~~

~~# First insert~~ <big>'''If the ~~U disk or~~ USB ~~mobile hard disk into~~ WIFI module seen by the lsusb command is in Driver CDROM Mode, please unplug the USB ~~interface of Orange PI development board# Execute~~ WIFI module again. If not, please manually execute the following command~~. If you can see the output of sdX,~~ to switch to the ~~U disk recognition is successful~~next mode:'''</big>

~~orangepi@orangepi:~$ '''cat /proc/partitions | grep "sd*"'''~~

~~major minor #blocks name~~orangepi@orangepi:~$ '''sudo usb_modeswitch -KW -v 0bda -p 1a2b'''|}

8 <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="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''lsmod'''Module Size Used by 8821cu 1839104 0 rtk_btusb 614400 ~~30044160~~ |}</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:~$ '''~~sda~~dmesg''' ......

8 [ 57.083693] usb 2-1 ~~30043119 '''sda1'''~~: new high-speed USB device number 2 using ehci-platform

~~<ol start~~[ 57.231888] usb 2-1: New USB device found, idVendor=~~"3" style~~0bda, idProduct=~~"list-style-type: decimal;"><li>Use the mount command to mount the U disk into '''/mnt'''~~1a2b, ~~and then you can view the file in the U disk</li></ol>~~bcdDevice= 2.00

~~orangepi@orangepi~~[ 57.231916] usb 2-1:~~~$ '''sudo mount /dev/sda1 /mnt/'''~~New USB device strings: Mfr=1, Product=2, SerialNumber=0

~~orangepi@orangepi~~[ 57.231937] usb 2-1:~~~$ '''ls /mnt/'''~~Product: DISK

~~test~~[ 57.~~txt~~231956] usb 2-1: Manufacturer: Realtek

~~<ol start="4" style="list~~[ 57.242594] usb-~~style~~storage 2-~~type~~1: ~~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>~~1.0: USB Mass Storage device detected

~~orangepi@orangepi~~[ 57.245674] scsi host0:~~~$ '''df~~ usb-~~h | grep "sd"'''~~storage 2-1:1.0

~~/dev/sda1 29G 208K 29G~~ [ 58.069172] usb 2-1~~% /mnt~~: USB disconnect, device number 2

~~=== USB wireless network card test ===~~platform

~~The currently '''tested''' USB wireless network cards are shown below~~[ 58. ~~Please test it by yourself for other models of~~ 587819] usb 2-1: New USB ~~wireless network cards~~device found, idVendor=0bda, idProduct=c820, bcdDevice= 2. ~~If you cannot use it, you need to transplant the corresponding USB wireless network card driver~~00

~~{| class="wikitable"~~|-~~| No~~[ 58.~~| Model~~||587827] usb 2-| 1~~| RTL8723BU~~: New USB device strings: Mfr=1, Product=2, SerialNumber=3

~~Support~~ [ 58.587833] usb 2-1: Product: 802.~~4G WIFI+BT4.0~~11ac NIC

| [~~[File:pi3b-img240~~58.~~png~~587838]]|usb 2-~~| 2| RTL8811~~1: Manufacturer: Realtek

~~Support~~ [ 58.587844] usb 2~~.4G +5G WIFI~~-1: SerialNumber: 123456

| [~~[File~~58.610463] rtk_btusb:~~pi3b-img241~~Realtek Bluetooth USB driver ver 3.1.6d45ddf.~~png]]~~|20220519-~~| 3| RTL8821CU~~142432

~~Support 2~~[ 58.~~4G +5G WIFI~~610656] usbcore: registered new interface driver rtk_btusb

~~Support BT 4~~[ 58.2634631] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821

~~| <div class~~[ 58.636729] Bluetooth: hci0: RTL: rom_version status=~~"figure">~~0 version=1

[~~[File~~58.636740] Bluetooth: hci0: RTL:~~pi3b-img242~~loading rtl_bt/rtl8821c_fw.~~png|tb_imag e_share_1670833201 123]]~~bin

<[ 58.664190] Bluetooth: hci0: RTL: loading rtl_bt/~~div>~~|}rtl8821c_config.bin

~~==== RTL8723BU test ====~~[ 58.664746] Bluetooth: hci0: RTL: cfg_sz 10, total sz 31990

~~# 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~~ [ 59.122471] Bluetooth ~~and WiFi -related kernel modules. You can see that the kernel module below is automatically loaded through the lsmod command~~: hci0: RTL: fw version 0x829a7644

~~orangepi@orangepi~~[ 59.265513] usbcore:~~~$ '''lsmod'''~~registered new interface driver rtl8821cu

~~Module Size Used by~~[ 59.280119] rtl8821cu 2-1:1.2 wlx90de80521825: renamed from wlan0|}</ol>

~~rfcomm 57344 16~~<ol start="5" style="list-style-type: decimal;"><li>Then you can see the RTL8821CU WiFi device node through the '''sudo ifconfig''' command. Please refer to the [[Orange Pi 3B#WIFI connection test|'''WiFi connection test chapter''']] for WIFI connection and testing methods.</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ifconfig wlx90de80521825'''

~~rtl8xxxu 106496 0~~wlx90de80521825: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500

~~rtk_btusb 61440 0~~::ether 00:13:ef:f4:58:ae txqueuelen 1000 (Ethernet)

~~<ol start="3" style="list-style-type~~: ~~decimal;"><li>You can see the loading information of the RTL8723BU module through the dmesg command</li></ol>~~:RX packets 0 bytes 0 (0.0 B)

~~orangepi@orangepi~~:~~~$ '''dmesg'''~~:RX errors 0 dropped 0 overruns 0 frame 0

::TX packets 0 bytes 0 (0.~~.....~~0 B)

~~[ 83.438901] usb 2~~::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0|}</ol><ol start="6" style="list-1style-type: ~~new high-speed~~ decimal;"><li>Then you can see the USB Bluetooth device ~~number 2 using ehci~~through the '''hciconfig''' command</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt-get update && sudo apt-get install -~~platform~~y bluez'''

~~[ 83.588375] usb 2-1~~orangepi@orangepi: ~~New USB device found, idVendor=0bda, idProduct=b720, bcdDevice= 2.00~~~$ '''hciconfig'''

~~[ 83.588403] usb 2-1~~hci0: ~~New USB device strings~~Type: Primary Bus: ~~Mfr~~'''USB'''

~~[ 83.588422] usb 2-1~~: ~~Product~~: ~~802.11n WLAN Adapter~~BD Address: 00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16

~~[ 83.588443] usb 2-1~~: ~~Manufacturer~~: ~~Realtek~~DOWN

~~[ 83.588460] usb 2-1~~: ~~SerialNumber~~: ~~00e04c000001~~RX bytes:1252 acl:0 sco:0 events:125 errors:0

~~[ 83.601974] Bluetooth~~: ~~hci0~~: ~~RTL~~TX bytes:23307 acl:0 sco:0 commands:125 errors: ~~examining hci_ver~~0|}</ol><ol start=~~06 hci_rev~~"7" style=~~000b lmp_ver~~"list-style-type: decimal;"><li>Bluetooth icons can also be seen on the desktop. At this time, Bluetooth has not been turned on, so a red '''x''' will be displayed</li>

[ 83[File:pi3b-img243.~~603894~~png] ~~Bluetooth: hci0: RTL: rom_version status~~]</ol><ol start=~~0 version~~"8" style=1"list-style-type: decimal;"><li>Click '''Turn Bluetooth On''' to turn on Bluetooth</li>

[ 83[File:pi3b-img244.~~603920~~png]] </ol><ol start="9" style="list-style-type: decimal;"><li>The display after turning on Bluetooth~~: hci0: RTL: loading rtl_bt~~is as follows</~~rtl8723b_fw.bin~~li>

[ 83[File:pi3b-img245.~~610108~~png]]</ol><ol start="10" style="list-style-type: decimal;"><li>Please refer to the [[Orange Pi 3B#How to use Bluetooth|'''Bluetooth use chapter''']] for the Bluetooth~~: hci0: RTL: loading rtl_bt~~test method. I won't go into details here</li></~~rtl8723b_config.bin~~ol>

~~[ 83.611274] Bluetooth: hci0: RTL: cfg_sz 68, total sz 22564~~

~~[ 83.658494] rtk_btusb: Realtek Bluetooth~~ === USB ~~driver ver 3.1.6d45ddf.20220519-142432~~Camera Test ===

~~[ 83.658651] usbcore: registered new interface driver rtk_btusb~~# 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

::[ 83[File:pi3b-img13.~~667124~~png]] ~~usb 2-1: This Realtek USB WiFi dongle (0x0bda:0xb720) is untested!~~

~~[ 83.667137] usb~~ <ol start="2" style="list-1style-type: ~~Please report results to Jes.Sorensen~~decimal;"><li>You can see that the USB camera's device node information is/dev/video0 through the v4l2-ctl command</li>{| class="wikitable" style="width:800px;" |-| orangepi@~~gmail.com~~orangepi:~$ '''v4l2-ctl --list-devices'''

~~[ 83~~Q8 HD Webcam: Q8 HD Webcam ('''usb'''-fc880000.~~890140]~~ usb 2-1): ~~Vendor: Realtek~~

~~[ 83.890153] usb 2-1~~: ~~Product~~'''/dev/video0'''

~~[ 83.890159] usb 2-1: rtl8723bu_parse_efuse: dumping efuse (0x200 bytes)~~:/dev/video1

:/dev/media0|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the l in v4l2 is a lowercase letter l, not the number 1.~~.....~~'''

~~[ 83.890412] usb 2-1: RTL8723BU rev E (SMIC) 1T1R, TX queues 3, WiFi=1, BT=1, GPS=0, HI PA=0~~

~~[ 83~~'''In addition, the serial number of the video is not necessarily video0, please refer to what you actually see.~~890417] usb 2~~'''</big>|}</ol><ol start="3" style="list-1style-type: ~~RTL8723BU MAC: 00:13:ef:f4:58~~decimal;"><li>In the desktop system, Cheese can be used to directly open the USB camera. The method of opening Cheese is shown in the figure below:ae</li>

[ 83[File:pi3b-img246.~~890421~~png]] ~~usb 2-1: rtl8xxxu: Loading firmware rtlwifi/rtl8723bu_nic.bin~~

~~[ 83.895289] usb 2-1~~The interface after Cheese turns on the USB camera is shown in the figure below: ~~Firmware revision 35.0 (signature 0x5301)~~

[ 84[File:pi3b-img247.~~050893~~png] ~~Bluetooth~~]</ol><ol start="4" style="list-style-type: decimal;"><li>How to test the USB camera using fswebcam<ol style="list-style-type: ~~hci0~~lower-alpha;"><li>Install fswebcam</li>{| class="wikitable" style="width: ~~RTL~~800px;" |-| orangepi@orangepi: ~~fw version 0x0e2f9f73~~~$ '''sudo''' '''apt update'''

~~[ 84~~orangepi@orangepi:~$ '''sudo apt-get install -y fswebcam'''|}</ol><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: none;"><li>a) -d The option is used to specify the device node of the USB camera</li><li>b) --no-banner Used to remove the watermark of photos</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.~~266905] Bluetooth~~jpg The name and path for setting the generated photos</li>{| class="wikitable" style="width: ~~RFCOMM TTY layer initialized~~800px;" |-| ~~[ 84.266949] Bluetooth~~orangepi@orangepi: ~~RFCOMM socket layer initialized~~~$ '''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''' [ 84mailto:test@192.168.1.~~266999] Bluetooth~~55: ~~RFCOMM ver~~ /home/test test@192.168.1.1155:/home/test] '''（Modify the IP address and path according to the actual situation）'''|}</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>

~~[ 84.884270] usbcore: registered new interface driver rtl8xxxu~~== Audio Test ==

~~[ 84.912046] rtl8xxxu 2~~=== Test audio methods in the desktop system ===

~~<ol start="4" style="list-style-type: decimal;"><li>Then you can see~~ # First open the ~~RTL8723BU WIFI device node through the '''sudo ifconfig''' command. Please refer to the WIFI connection test a [[\l|'''section for WIFI connection''']] and testing methods</li></ol>~~file manager

~~orangepi@orangepi~~:~~~$ '''sudo ifconfig wlx0013eff458ae'''~~:[[File:pi3b-img248.png]]

~~wlx0013eff458ae~~<ol start="2" style="list-style-type: ~~flags=4099&lt~~decimal;UP"><li>Then find the following file (if there is no audio file in the system,~~BROADCAST,MULTICAST> mtu 1500~~you can upload a audio file to the system by yourself)</li>

~~ether 00:13:ef:f4:58:ae txqueuelen 1000 (Ethernet)~~<div class="figure">

~~RX packets 0 bytes 0 (0~~[[File:pi3b-img249.~~0 B)~~png]]

~~RX errors 0 dropped 0 overruns 0 frame 0~~</div></ol><ol start="3" style="list-style-type: decimal;"><li>Then select the audio.wav file, right click and select open with vlc to start playing</li>

~~TX packets 0 bytes 0 (0~~[[File:pi3b-img250.~~0 B)~~png]]</ol><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>

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~[[File:pi3b-img251.png]]</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>~~Then you can see the USB Bluetooth device through the '''hciconfig''' command~~</liol></olspan>

~~orangepi@orangepi:~$ '''sudo apt update && sudo apt install bluez'''~~=== How to play audio with commands ===

~~orangepi@orangepi:~$ '''hciconfig'''~~==== Headphone interface play audio test ====

~~hci0: Type: Primary Bus: '''USB'''~~# First insert the headset into the headphone jack of the development board

~~BD Address~~: 00:13[[File:~~EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16~~pi3b-img253.png]]

~~DOWN~~<ol start="2" style="list-style-type: decimal;"><li>Then you can check the 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>

~~RX bytes~~{| class="wikitable" style="width:~~1252 acl~~800px;" |-| orangepi@orangepi:~~0 sco:0 events:125 errors:0~~~$ '''aplay -l'''

~~TX bytes:23307 acl:0 sco:0 commands:125 errors:0~~**** List of PLAYBACK Hardware Devices ****

~~<ol start="6" 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~~ '''xcard 0: rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]''' ~~will be displayed</li></ol>~~

~~[[File~~:~~pi3b-img243.png|576x157px]]~~'''Subdevices: 0/1'''

~~<ol start="7" style="list-style-type~~: ~~decimal;"><li>Click~~ '''~~Turn Bluetooth On~~Subdevice #0: subdevice #0''' ~~to open Bluetooth</li></ol>~~

card 1: rockchiphdmi [~~[File~~rockchip,hdmi], device 0:~~pi3b~~fe400000.i2s-~~img244~~i2s-hifi i2s-hifi-0 [fe400000.~~png|576x262px]~~i2s-i2s-hifi i2s-hifi-0]

~~<ol start="8" style="list-style-type~~: ~~decimal;"><li>The display after opening Bluetooth is shown below</li><~~Subdevices: 0/~~ol>~~1

~~[[File~~:~~pi3b-img245.png|576x164px]]~~Subdevice #0: subdevice #0

:Subdevice #0: subdevice #0|}</ol><ol start="93" style="list-style-type: decimal;"><li>~~Please refer to~~ Then use the ~~[[\l|~~'''~~Bluetooth use method~~aplay'''~~]] for Bluetooth test method~~command to play the audio file that comes with the system. If the headset can hear the sound, ~~so I won't go into details here.~~it means that the hardware can be used normally</li~~></ol~~>

~~<~~| orangepi@orangepi:~$ '''aplay -D hw:0,0 /usr/share/sounds/alsa/~~span>==== RTL8811 test ====~~audio.wav'''

~~# First insert the RTL8811 wireless network card module into the USB interface of the development board~~Playing WAVE 'audio.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo~~# Then the Linux system will automatically load the RTL8811 WIFI~~ |}</ol>

~~orangepi@orangepi:~$ '''lsmod'''~~==== HDMI Audio Play Test ====

~~Module Size Used by~~# 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'''

~~8821cu 1839104 0~~::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''aplay -l'''

<~~ol start="3" style="list-style-type: decimal;"~~p>~~<li>You can see the loading information~~ **** List of ~~the RTL8811 module through the dmesg command</li>~~PLAYBACK Hardware Devices ****</olp>

~~orangepi@orangepi~~card 0:~~~$ '''dmesg'''~~rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]

~~[ 118.618194] usb 2-~~:Subdevices: 0/1~~: new high-speed USB device number 2 using ehci-platform~~

~~[ 118.767152] usb 2-1~~: ~~New USB device found, idVendor=0bda, idProduct=c811, bcdDevice= 2.00~~Subdevice #0: subdevice #0

'''card 1: rockchiphdmi [ ~~118.767181~~rockchip,hdmi] ~~usb 2-1: New USB~~ , device ~~strings~~0: ~~Mfr=1, Product=2, SerialNumber=3~~fe400000.i2s-i2s-hifi i2s-hifi-0 [fe400000.i2s-i2s-hifi i2s-hifi-0]'''

~~[ 118.767199] usb 2-1~~: ~~Product~~'''Subdevices: ~~802.11ac NIC~~0/1'''

~~[ 118.767219] usb 2-1~~: ~~Manufacturer~~'''Subdevice #0: ~~Realtek~~subdevice #0'''

~~[ 118.767235] usb 2-1~~: ~~SerialNumber~~'''Subdevice #0: ~~123456~~subdevice #0'''|}

~~[ 119~~<ol start="3" style="list-style-type: decimal;"><li>Then use the '''aplay''' command to play the audio file that comes with the system.~~500530] usbcore~~If the HDMI display or television can hear the sound indicates that the hardware can be used normally</li>{| class="wikitable" style="width: ~~registered new interface driver rtl8821cu~~800px;" |-| orangepi@orangepi:~$ '''aplay -D hw:1,0 /usr/share/sounds/alsa/audio.wav'''|}</ol>

~~[ 119.525498] rtl8821cu 2-1:1.0 wlx1cbfced9d260: renamed from wlan0~~=== Use the command to test the recording method ===

~~<ol start="4" style="list-style-type: decimal;"><li>Then you~~ # Orange Pi 3B development board does not have MICs, and can ~~see~~ only record audio through headphones with MIC function. After inserting the ~~WiFi device node through~~ headset with the MIC function into the development board, the ~~'''sudo ifconfig'''~~ command~~. Please refer to~~ below will record a piece of audio through the ~~[[\l|'''WiFi connection test a section''']] for WIFI connection and testing methods. I won't go into details her</li></ol>~~headset

::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~sudo ifconfig wlx1cbfced9d260~~amixer -c 0 cset name='Capture MIC Path' 'Main Mic''''

~~wlx1cbfced9d260~~orangepi@orangepi: ~~flags=4099<UP,BROADCAST~~~$ '''arecord -D hw:0,~~MULTICAST> mtu 1500~~0 -d 5 -f cd -t wav /tmp/test.wav'''|}

~~ether 1c:bf:ce:d9:d2:60 txqueuelen 1000 (Ethernet)~~

~~RX packets 0 bytes 0 (0.0 B)~~== Temperature Sensor ==

~~RX errors 0 dropped 0 overruns 0 frame 0~~# The command to view the system temperature sensor is:

~~TX packets 0 bytes 0 (0.0 B)~~::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sensors'''

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions~~ soc_thermal-virtual-0

~~==== RTL8821CU test ====~~Adapter: Virtual device

~~# 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~~temp1: +41. ~~Make sure the USB module is not in the Driver CDROM Mode~~9°C (crit = +115.0°C)

~~orangepi@orangepi:~$ '''lsusb | grep "Realtek"'''~~

~~Bus 002 Device 003: ID 0bda:c820 Realtek Semiconductor Corp. 802.11ac NIC~~gpu_thermal-virtual-0

~~orangepi@orangepi~~Adapter:~~~$ '''lsusb | grep "Realtek"'''~~Virtual device

~~Bus 002 Device 002~~temp1: ~~ID 0bda:1a2b Realtek Semiconductor Corp. RTL8188GU 802~~+43.~~11n WLAN Adapter ('''Driver CDROM Mode''')~~8°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:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~If the USB WIFI module seen by the lsusb command is in Driver CDROM Mode, re~~ sudo smartctl -~~insert the USB WiFi module. If not, please manually execute the following command to switch the mode~~a /dev/nvme0 | grep "Temperature:"'''Temperature: '''40 Celsius'''|}</li></ol>

~~orangepi@orangepi:~$ '''sudo usb_modeswitch~~

~~<ol start~~=~~"3" style~~=~~"list-style-type: decimal;">~~<li>The Linux system will automatically load the RTL8821CU Bluetooth and WIFI -related kernel modules. You can see that the kernel module below is automatically loaded through the lsmod command</li></ol>40 Pin interface pin explanation ==

~~orangepi@orangepi:~$ '''lsmod'''~~# Orange Pi 3B Development board 40 Pin interface pins, please refer to the figure below

~~Module Size Used by~~<div class="figure">

~~8821cu 1839104 0~~::[[File:pi3b-img254.png]]

~~rtk_btusb 61440 0~~</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><ol start="42" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~You can see~~ The following form is a picture on the ~~loading information~~ left half of the ~~rtl8821cu module through the dmesg command~~full table above, which can be seen clearly</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''dmesg'''~~pi3b-img256-1.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The following form is a picture on the right half of the top table above, which can be seen clearly</li>

[[File:pi3b-img257-1.png]]</ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>There are a total of '''28''' GPIO ports in the 40pin interface.The voltage of all GPIO ports is '''3.~~...~~3v'''</li></ol>

~~[ 57.083693] usb 2~~

~~[ 57.231888] usb 2-1: New USB device found, idVendor~~=~~0bda, idProduct~~=~~1a2b, bcdDevice~~How to install wiringOP == ~~2.00~~

~~[ 57.231916] usb 2~~{| class="wikitable" style="background-1color: ~~New USB device strings~~#ffffdc;width: ~~Mfr=1~~800px;" |-| <big>'''Note that wiringOP has been pre -installed in the Linux image released by Orange Pi. Unless wiringOP's code is updated, ~~Product=2, SerialNumber=0~~it is not necessary to re -download and install. Just use it directly.'''

~~[ 57.231937] usb 2-1: Product: DISK~~

~~[ 57.231956] usb 2~~'''The storage path of the compiled wiringOP's Deb is wrapped in Orangepi-1Build: ~~Manufacturer: Realtek~~'''

~~[ 57~~'''orangepi-build/external/cache/debs/arm64/wiringpi_x.~~242594] usb-storage 2-1:1~~xx.~~0: USB Mass Storage device detected~~deb'''

~~[ 57.245674] scsi host0: usb-storage 2-1:1.0~~

~~[ 58~~'''After entering the system, you can run the gpio readall command.~~069172] usb 2~~If you can see the output below, it means that wiringOP is pre -~~1: USB disconnect, device number 2~~installed and can be used normally.'''</big>

~~[ 58.440025] usb 2-1: new high-speed USB device number 3 using ehci-platform~~<div class="figure">

[ ~~58.587819] usb 2~~[File:pi3b-img258-1~~: New USB device found, idVendor=0bda, idProduct=c820, bcdDevice= 2~~.00png]]

~~[ 58.587827] usb 2-1: New USB device strings: Mfr=1~~</div><big>'''wiringOP is currently mainly adapted to the functions of setting GPIO port input and output, ~~Product=2~~setting GPIO port output high and low levels, ~~SerialNumber=3~~and setting up and down pull-down resistors. Functions such as hardware PWM are not available.'''</big>|}

~~[ 58.587833] usb 2-1: Product: 802.11ac NIC~~# Download the code of wiringOP

~~[ 58.587838] usb 2~~::{| class="wikitable" style="width:800px;" |-~~1: Manufacturer~~| orangepi@orangepi: ~~Realtek~~~$ '''sudo apt update'''

~~[ 58.587844] usb 2~~orangepi@orangepi:~$ '''sudo apt install -~~1: SerialNumber: 123456~~y git'''

~~[ 58.610463] rtk_btusb~~orangepi@orangepi:~$ '''git clone https: ~~Realtek Bluetooth USB driver ver 3~~//github.~~1.6d45ddf~~com/orangepi-xunlong/wiringOP.~~20220519~~git -~~142432~~b next'''|}

~~[ 58~~::{| class="wikitable" style="background-color:#ffffdc;width: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.~~610656] usbcore: registered new interface driver rtk_btusb~~'''

~~[ 58.634631] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821~~

~~[ 58.636729] 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: rom_version status=0 version=1~~/usr/src/wiringOP'''</big>|}

~~[ 58.636740] Bluetooth~~<ol start="2" style="list-style-type: ~~hci0: RTL: loading rtl_bt~~decimal;"><li>Compile and install wiringOP</~~rtl8821c_fw.bin~~li>

~~[ 58.664190] Bluetooth~~{| class="wikitable" style="width: ~~hci0~~800px;" |-| orangepi@orangepi: ~~RTL: loading rtl_bt/rtl8821c_config.bin~~~$ '''cd wiringOP'''

~~[ 58~~orangepi@orangepi:~/wiringOP$ '''sudo .~~664746] Bluetooth: hci0: RTL: cfg_sz 10, total sz 31990~~/build clean'''

~~[ 59~~orangepi@orangepi:~/wiringOP$ '''sudo .~~122471] Bluetooth: hci0: RTL~~/build'''|}</ol><ol start="3" style="list-style-type: ~~fw version 0x829a7644~~decimal;"><li>Test the output of the GPIO Readall command as follows</li>

~~[ 59.265513] usbcore: registered new interface driver rtl8821cu~~<div class="figure">

[ ~~59.280119] rtl8821cu 2~~[File:pi3b-img258-1:1.~~2 wlx90de80521825: renamed from wlan0~~png]]

</div></ol ~~start~~><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></olspan>

~~orangepi@orangepi:~$ '''sudo ifconfig wlx90de80521825'''~~== 40Pin interface GPIO, I2C, UART, SPI, and PWM test ==

~~wlx90de80521825~~{| class="wikitable" style="background-color:#ffffdc;width: ~~flags=4099&lt~~800px;UP" |-| <big>'''Note that if you need to set overlays to open multiple configurations at the same time,~~BROADCAST,MULTICAST> mtu 1500~~please use a space to write in one line like the following space.'''</big>

~~ether 00~~orangepi@orangepi:~~13:ef:f4:58:ae txqueuelen 1000 (Ethernet)~~~$ '''sudo vim /boot/orangepiEnv.txt'''

~~RX packets 0 bytes 0 (0.0 B)~~'''overlays=spi3-m0-cs0-spidev i2c2-m1 i2c3-m0 uart7-m2 uart9-m2 pwm11-m1'''|}

~~RX errors 0 dropped 0 overruns 0 frame 0~~=== 40pin GPIO port test ===

~~TX packets 0 bytes 0 (0~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The Linux system released by Orange Pi has a pre -installed blink_all_gpio program.~~0 B)~~This program will set up all 28 GPIO ports in 40pin to switch high and low levels.'''

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~

~~<ol start="6" style="list-style-type: decimal;"><li>Then~~ '''After running the blink_all_gpio program, when using a multimeter to measure the level of the GPIO port, you ~~can see~~ will find that the ~~USB Bluetooth device through~~ GPIO pin will be switched between 0 and 3.3v. Use this program to test whether the GPIO port can work normally'''~~hciconfig''' command</li></ol>~~

~~orangepi@orangepi:~$ '''sudo apt-get update && sudo apt-get install -y bluez'''~~

~~orangepi@orangepi:~$~~ '''~~hciconfig~~The method of running blink_all_gpio program is shown below: '''</big>

~~hci0: Type: Primary Bus~~orangepi@orangepi3b: ~$ '''~~USB~~sudo blink_all_gpio'''        #Remember to add Sudo permissions

~~BD Address~~[sudo] password for orangepi: ~~00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16~~       #You need to enter password here'''|}

~~DOWN~~# 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_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

~~RX bytes~~:~~1252 acl~~:~~0 sco~~[[File:~~0 events:125 errors:0~~pi3b-img259-1.png]]

~~TX bytes~~<ol start="2" style="list-style-type:~~23307 acl:0 sco:0 commands:125 errors:0~~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>

{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio mode 2 out'''|}</ol><ol start="73" style="list-style-type: decimal;"><li>~~Bluetooth icons~~ Then set the GPIO port to output the low level. After setting, you can ~~also be seen on~~ use the ~~desktop~~value of the voltage of the pins with a multimeter. ~~At this time~~If it is 0v, ~~Bluetooth has not been opened, so a red '''x''' will be displayed~~it means that the low level flat is successful</li~~></ol~~>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img243.png~~| root@orangepi:~/wiringOP# '''gpio write 2 0'''|~~576x157px]]~~}

~~<ol start="8" style="list-style-type: decimal;"><li>Click '''Turn Bluetooth On'''~~ Using GPIO Readall, you can see the value of the No. 7 pin (V) to ~~open Bluetooth</li></ol>~~0

[[File:pi3b-~~img244~~img260.png~~|576x262px~~]]</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="9wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">|-| root@orangepi:~/wiringOP# '''gpio write 2 <lispan style="color:#FF0000">~~The display after opening Bluetooth is shown below~~1</~~li></ol~~span>'''|}

~~[[File:pi3b-img245~~Using GPIO Readall, you can see the value of No.~~png|576x164px]]~~ 7 pin (v) into 1

[[File:pi3b-img261-1.png]]</ol><ol start="105" style="list-style-type: decimal;"><li>~~Please refer~~ The setting method of other pins is similar, just modify the serial number of wPi to the ~~[[\l|'''Bluetooth use chapter''']] for~~ corresponding serial number of the ~~Bluetooth test method. I won't go into details her~~pin</li></ol>

~~=== 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~~=== 40pin GPIO port pull-down resistance setting method ===

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~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-~~img13~~down is invalid.~~png|259x150px]]~~Other pins can be set normally '''</big>

~~<ol start="2" style="list~~[[File:pi3b-~~style~~img262-~~type: decimal;">~~1.png|center]]~~<li>You can see that the USB camera's device node information is/dev/video0 through the v4l2-ctl command</li></ol>~~|}

~~orangepi@orangepi:~$ '''v4l2~~# Below the No. 11 pin—corresponding to GPIO 3_C6-~~ctl~~ corresponding wPi serial number 5—to demonstrate how to set up and down pull-~~-list-devices'''~~down resistance of the GPIO port

~~Q8 HD Webcam~~: ~~Q8 HD Webcam ('''usb'''~~:[[File:pi3b-~~fc880000.usb~~img263-1):.png]]

<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</~~dev/video0~~span> in'''|}</~~dev~~ol><ol start="3" style="list-style-type: decimal;"><li>After the setting is set to input mode, execute the following command to set the GPIO port as the pull-down mode</~~video1~~li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~dev~~wiringOP# '''gpio mode 5</~~media0~~span> up'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then enter the following command to read the level of the GPIO port. If the level is 1, it means that the drawing mode is successful</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''~~Note that l in v4l2 is a lowercase letter l, not numbers 1.~~gpio read 5'''

'''~~In addition, Video~~1'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>Then execute the following command to set the GPIO port as the drop-down mode</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio mode 5 down'''~~s serial number~~ |}</ol><ol start="6" style="list-style-type: decimal;"><li>Then enter the following command to read the level of the GPIO port. If the level is ~~not necessarily Video0~~0, ~~please refer to what you see.~~it means that the drop-down mode is set successfully</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio read 5'''

'''<~~ol start="3"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">0'''|}<li/ol>~~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~~span id="pin-spi-test"></olspan>

~~[[File:pi3b-img246.png|474x302px]]~~=== 40pin SPI Test ===

~~The~~ # From the schematic diagram of the 40PIN interface ~~after cheese opens~~ , the ~~USB camera~~ SPI available for Orange Pi 3B is ~~shown in the figure below:~~ spi3

::[[File:pi3b-~~img247~~img264-1.png~~|473x277px~~]]

<ol start="42" style="list-style-type: decimal;"><li>~~How~~ In the linux system, the SPI in the 40 pin is closed by default, and it needs to ~~test the USB camera using fswebcam~~be opened manually before it can be used. The detailed steps are as follows:

<li>~~Install fswebcam~~First run '''orangepi-config''', normal users remember to add sudo permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li><li>Then select '''System'''[[File:pi3b-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 SPI configuration you want to open[[File:pi3b-3.png]]</li><li>Then select '''<Save>''' to save[[File:pi3b-4.png]]</li><li>Then select '''<Back>'''[[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>

~~orangepi@orangepi~~<ol start="3" style="list-style-type:~~~$ '''sudo''' '''apt update'''~~decimal;"><li>After restarting, enter the system to check whether there is a spidev3.0 device node in the Linux system. If it exists, it means that SPI3 has been set up and can be used directly</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~sudo apt-get install -y fswebcam~~ls /dev/spidev3.0'''

~~<ol start="2" style="list-style-type: lower-alpha;">~~/dev/spidev3.0|}~~<li>After installing fswebcam, you can use the following command to take pictures~~</pol><ol start="4" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~~~Do not short-~~d The option is used to specify~~ circuit the ~~device node~~ mosi and miso pins of SPI3, 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~~ output result of ~~the photo</li><li>-S The option~~ running spidev_test is ~~set to~~ as follows, you can see that the ~~number~~ data of ~~frames before skipping</li><li>./image.jpg The name~~ TX and ~~path for setting the generated photos</li></ol>~~RX are inconsistent</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo~~''' '''fswebcam~~ spidev_test -v -d D /dev/~~video0 \~~spidev3.0'''

~~'''--no-banner -r 1280x720 -S 5 ./image.jpg'''~~spi mode: 0x0

~~<ol start="3" style="list-style-type~~bits per word: ~~lower-alpha;"><li>In 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>~~8

~~orangepi@orangepi~~max speed:~~~$ '''scp image.jpg''' [mailto:test@192.168.1.55:/home/test test@192.168.1.55:/home/test] '''（Modify the IP address and path according to the actual situation）'''~~500000 Hz (500 KHz)

TX | FF FF FF FF FF FF '''<~~ol start="4"~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<li>In the desktop version of the Linux system, you can directly view the shot pictures through the HDMI display</li>~~40 00 00 00 00 95</olspan>''' 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= ~~Audio Test ==~~"list-style-type: decimal;"><li>Then short-circuit the two pins of mosi (pin 19 in the 40pin interface) and miso (pin 21 in the 40pin interface) of SPI3, and then run the output of spidev_test as follows, you can see the sending and receiving same data</li>

~~<~~D /dev/~~span>=== Test audio methods in the desktop system ===~~spidev3.0'''

~~# First open the file manager~~spi mode: 0x0

~~[[File~~bits per word:~~pi3b-img248.png|357x176px]]~~8

~~<ol start="2" style="list-style-type~~max speed: ~~decimal;"><li>Then find the following file~~ 500000 Hz (~~if there is no audio file in the system, you can upload a audio file to the system by yourself~~500 KHz)~~</li></ol>~~

TX | FF FF FF FF FF FF '''<~~div class~~span style="~~figure~~color:#FF0000">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~~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~~|~~236x186px|图片10]]~~}</ol>

~~</div><ol start~~=~~"3" style~~=~~"list-style-type: decimal;"><li>Then select the audio.wav file, right -click and select VLC to open it to start playing</li></ol>~~= 40pin I2C Test ===

~~[[File:pi3b-img250~~# From the table below, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total of three groups of I2C bus.~~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~~:[[File:pi3b-~~style-type: lower~~img266-~~alpha;"><li>First open the volume control interface</li></ol></li></ol>~~1.png]]

~~[[File~~:~~pi3b~~:{| class="wikitable" style="background-~~img251~~color:#ffffdc;width:800px;" |-| <big>'''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.~~png~~The two cannot be opened at the same time'''</big>|~~308x169px]]~~}

<ol start="2" style="list-style-type: decimal;"><li>In the linux system, the I2C bus in the 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;"><li>~~When playing audio, the audio equipment options that play software can be used will be displayed in~~ First run '''~~Playback~~orangepi-config'''~~. As shown in the figure below~~, ~~which audio equipment you need~~ normal users remember to ~~play here can be set.~~add '''sudo''' permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li><li>Then select '''System'''</olp> [[File:pi3b-~~img252~~1.png~~|576x282px~~]] <~~span id="how-to-play-audio-with-commands"~~/p></~~span~~li>~~=== How to play audio with commands ===~~ <~~span id="headphone-interface-play-audio-test"~~li>Then select '''Hardware'''</~~span~~p>~~==== Headphone interface play audio test ====~~ ~~# First insert the headset into the headphone jack of the development board~~ [[File:pi3b-~~img253~~2.png~~|395x112px~~]]<~~ol start="2" style="list-style-type: decimal;"~~/li><li>Then ~~you can check~~ use the ~~sound card device supported by~~ arrow keys on the ~~Linux system through~~ keyboard to navigate to the ~~'''aplay -l''' command. From~~ position shown in the ~~output~~ figure below, ~~it can be seen that~~ and then use the '''~~card 0~~space''' is to select the ~~sound card device with RK809, which is the sound card device of the headset~~I2C configuration you want to open</lip>[[File:pi3b-3-2.png]]</olp></li>~~orangepi@orangepi:~$~~ <li>Then select '''~~aplay -l~~<Save>'''to save ~~**** List of PLAYBACK Hardware Devices ****~~ ~~'''card 0~~[[File: ~~rockchiprk809 [rockchip~~pi3b-~~rk809~~4.png]~~, device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0~~]</li><li>Then select ''' <Back>'''~~Subdevices~~[[File: 0pi3b-5.png]]</~~1'''~~p></li><li>Then select '''~~Subdevice #0: subdevice #0~~<Reboot>'''to restart the system to make the configuration take effect ~~card 1: rockchiphdmi~~ [[~~rockchip,hdmi], device 0~~File: ~~fe400000.i2s~~pi3b-~~i2s-hifi i2s-hifi-0 [fe400000~~6.~~i2s-i2s-hifi i2s-hifi-0~~png]]</li>~~Subdevices: 0~~</1ol> ~~Subdevice #0: subdevice #0~~ ~~Subdevice #0: subdevice #0~~</li></ol>

<li>~~Then use the '''aplay''' command to play the audio file that comes with~~ After starting the Linux system~~. If the headset can hear the sound~~, ~~it means~~ first confirm that the ~~hardware can be used normally~~i2c device node exists under/dev</li><{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~# '''ls /dev/~~ol>~~i2c-*'''

~~orangepi@orangepi:~$~~ /dev/i2c-0      '''~~aplay~~ /dev/i2c-~~D hw:0,0~~ 2'''      '''/~~usr~~dev/~~share~~i2c-3'''      '''/~~sounds~~dev/~~alsa/audio.wav~~i2c-4'''     /dev/i2c-6|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then connect a i2c device on the i2c pin of the 40Pin connector</li>

~~Playing WAVE 'audio~~{| class="wikitable" style="width:800px;text-align: center;"|-||i2c2-m1|i2c3-m0|i2c4-m0|-| Sda Pin|Corresponding to No. 3 pin|Corresponding to No.~~wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo~~ 27 pin|Corresponding to No. 19 pin~~<span id="hdmi~~|-~~audio~~| Sck Pin|Corresponding to No. 5 pin|Corresponding to No. 28 pin|Corresponding to No. 23 pin|-~~play~~| Vcc Pin|Corresponding to No. 1 pin|Corresponding to No. 1 pin|Corresponding to No. 1 pin|-~~test">~~| Gnd Pin|Corresponding to No. 6 pin|Corresponding to No. 6 pin|Corresponding to No. 6 pin|}</~~span~~ol><ol start="5" style=~~== HDMI Audio Play Test ====~~"list-style-type: decimal;"> ~~# First~~ <li>Then use the ~~HDMI to HDMI cable to connect~~ '''i2cdetect -y''' command if the ~~Orange PI development board to~~ address of the ~~TV (other HDMI displays need to ensure~~ connected I2C device can be detected, it means that the ~~audio~~ I2C can be ~~played)~~used normally</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ sudo i2cdetect -y 2 # ~~Then check the sound card serial number of HDMI. From the output below, you can know that the HDMI sound card is '''card 1'''~~i2c2 command

orangepi@orangepi:~$ ~~'''aplay~~ sudo i2cdetect -~~l'''~~y 3 #i2c3 command

~~**** List of PLAYBACK Hardware Devices ****~~orangepi@orangepi:~$ sudo i2cdetect -y 4 #i2c4 command|}

~~card 0: rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]~~<div class="figure">

~~Subdevices~~[[File: ~~0/1~~pi3b-img267.png]]

~~Subdevice #0: subdevice #0~~</div></ol>

~~'''card 1: rockchiphdmi [rockchip,hdmi], device 0: fe400000.i2s-i2s-hifi i2s-hifi-0 [fe400000.i2s-i2s-hifi i2s-hifi-0]'''~~=== 40pin UART test ===

~~'''Subdevices: 0/1'''~~# 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

~~'''Subdevice #0~~: ~~subdevice #0'''~~:[[File:pi3b-img268-1.png]]

::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~Subdevice #0: subdevice #0~~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>|}

<ol start="32" style="list-style-type: decimal;"><li>~~Then use the '''aplay''' command to play the audio file that comes with~~ In the linux system~~. If~~ , the ~~HDMI display or television can hear~~ UART in the ~~sound indicates that the hardware~~ 40 pins is closed by default, and it needs to be opened manually before it can be used ~~normally~~. The detailed steps are as follows:<ol style="list-style-type: lower-alpha;"><li>First run '''orangepi-config''', normal users remember to add sudo permission</olp>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~aplay~~ sudo orangepi-~~D hw:1,0~~ config'''</~~usr~~p>|}</~~share~~li><li>Then select '''System'''</~~sounds~~p>[[File:pi3b-1.png]]</~~alsa~~p></~~audio.wav~~li><li>Then select '''Hardware'''[[File:pi3b-2.png]]</li><~~span id="~~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-~~command~~3-3.png]]</li><li>Then select '''<Save>''' tosave[[File:pi3b-~~test~~4.png]]</li><li>Then select '''<Back>'''[[File:pi3b-~~the-recording-method"~~5.png]]</~~span~~li>~~=== Use~~ <li>Then select '''<Reboot>''' to restart the ~~command~~ system to ~~test~~ make the ~~recording method ===~~configuration take effect[[File:pi3b-6.png]]</li></ol># 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</li></ol>

~~orangepi@orangepi~~<ol start="3" style="list-style-type:~~~$ '''amixer -c 0 cset name='Capture MIC Path' 'Main Mic''''~~decimal;"><li>After entering the Linux system, first confirm whether there is a device node corresponding to uart under/dev</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ # '''~~arecord -D hw:0,0 -d 5 -f cd -t wav~~ ls /~~tmp~~dev/~~test.wav~~ttyS*'''

/dev/ttyS1      '''/dev/ttyS3      /dev/ttyS7      /dev/ttyS9'''|}</ol><~~span id~~ol start="4" style="~~temperature~~list-~~sensor~~style-type: decimal;"><li>Then start testing the uart interface, first use the rx and tx of the uart interface to be tested by DuPont</~~span~~li>~~== Temperature Sensor ==~~

~~# The command of~~ {| 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 ~~system temperature sensor is:~~ 22 pin|}

[[File:pi3b-img269-1.png]]</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: lower-alpha;"><li>Test UART3</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~sensors~~sudo gpio serial /dev/ttyS3'''

~~soc_thermal-virtual-0~~[sudo] password for orangepi: #Enter the password here.

~~Adapter: Virtual device~~

~~temp1~~Out: ~~+41.9°C (crit = +115.0°C)~~0: -> 0

~~gpu_thermal~~Out: 1: -~~virtual-0~~> 1

~~Adapter~~Out: ~~Virtual device~~2: -> 2

~~temp1~~Out: ~~+43.8°C~~3: -> 3

~~<ol start="2" style="list-style-type~~Out: ~~decimal;"><li>The command of the current temperature of the NVMe SSD solid -state hard disk is~~4: ~~orangepi@orangepi:~$ '''sudo smartctl~~ -~~a /dev/nvme0 | grep~~ &~~quot~~gt;~~Temperature:"'''Temperature: '''40 Celsius'''</li></ol>~~4

Out: 5: -> 5^C|}<~~span id~~/ol><ol start="~~pin~~2" style="list-~~interface~~style-~~pin~~type: lower-~~explanation~~alpha;"><li>Test UART7</~~span~~li>{| class="wikitable" style= ~~40 Pin interface pin explanation ==~~"width:800px;" |-| orangepi@orangepi:~$ '''sudo gpio serial /dev/ttyS7'''

[sudo] password for orangepi: # ~~Orange Pi 3B Development board 40 Pin interface pins, please refer to~~ Enter the ~~figure below~~password here.

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

~~[[File~~Out:~~pi3b-img254.png|400x124px|C~~0:~~\Users\orangepi\Desktop\用户手册插图\pi 3b\Orange-Pi-3B-Development-board-40-Pin(1).jpgOrange-Pi-3B-Development-board-40~~-~~Pin(1)]]~~> 0

~~</div><ol start="2" style="list-style-type~~Out: ~~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~~1: ~~lower~~-~~alpha~~>">~~<li>Below is a complete pins of 40pin</li></ol></li></ol>~~1

~~[[File~~Out: 2:~~pi3b~~-~~img255.png|575x160px]]~~> 2

~~<ol start="2" style="list-style-type~~Out: 3: ~~lower~~-~~alpha~~>">~~<li>The following form is a picture on the left half of the full table above, which can be seen clearly</li></ol>~~3

~~[[File~~Out: 4:~~pi3b~~-~~img256.png|478x267px]]~~> 4

Out: 5: -> 5^C

|}

</ol>

<li>~~The following form is a picture on the right half of the top table above, which can be seen clearly~~Test UART9</li><{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo gpio serial /dev/~~ol>~~ttyS9'''

[~~[File~~sudo] password for orangepi:~~pi3b-img257~~#Enter the password here.~~png|479x266px]]~~

~~<ol start="3" style="list-style-type: decimal;">~~

~~<li>There are a total of '''28''' GPIO ports in the 40pin interface. The voltage of all GPIO ports is '''3.3v'''</li></ol>~~

~~== How to install Wiringop ==~~> 0

~~'''Note that Wiringop has been pre~~ Out: 1: -~~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.'''~~> 1

~~'''The storage path of the compiled Wiringop's Deb is wrapped in Orangepi~~Out: 2: -~~Build: '''~~> 2

~~'''orangepi~~Out: 3: -~~build/external/cache/debs/arm64/wiringpi_x.xx.deb'''~~> 3

~~'''After entering the system, you can run the gpio readall command. If you can see the output below, it means that wiringOP is pre~~ Out: 4: -~~installed and can be used normally.'''~~> 4

Out: 5: -> 5^C|}<~~div class~~/ol></li></ol>

~~[[File:pi3b-img258.png|575x355px|66AC(IBG%N8L@Y7(1BZPS`N]]~~=== PWM test method ===

~~</div>'''wiringOP is currently adapted to set~~ # From the ~~GPIO port input output~~table below, ~~set~~ the ~~GPIO port output high and low level, and set the function of pulling and down resistance. It is impossible to use functions like hardware PWM.'''~~pwm11 available for Orange Pi 3B

~~# Download the code of Wiringop~~::[[File:pi3b-img270-1.png]]

<ol start="2" style="list-style-type: decimal;"><li>In the linux system, the PWM in the 40 pin is turned off by default, and it needs to be turned on manually before it can be used. The detailed steps are as follows:<ol style="list-style-type: lower-alpha;"><li>First run '''orangepi-config''', normal users remember to add sudo permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ~~apt update~~orangepi-config'''|}</li><li>Then select '''System'''[[File:pi3b-1.png]]</li><li>Then select '''Hardware'''~~orangepi@orangepi~~[[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-3-4.png]]</li><li>Then select '''<Save>''' to save[[File:~$ pi3b-4.png]]</li><li>Then select '''<Back>'''~~sudo apt install~~ [[File:pi3b-~~y git~~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>

<ol start="3" style="list-style-type: decimal;"><li>After opening a pwm, there will be an extra pwmchipX in '''/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:~$ '''~~git clone https:~~ls /sys/~~github.com~~class/~~orangepi-xunlong~~pwm/~~wiringOP.git -b next~~'''

pwmchip0 pwmchip1|}</ol><ol start="4" style="list-style-type: decimal;"><li>Which pwmchip above corresponds to pwm11, let's check the output of the '''ls /sys/class/pwm/ -l''~~Note~~ ' command first, as shown below:</li><li>Then it can be known from the table below that ~~Orange Pi 3B needs to download~~ the ~~code~~ base address of the ~~wiringOP next branch~~pwm11 register is fe6f0030, ~~please don't miss~~ and then look at the ~~parameter~~ output of the '''ls /sys/class/pwm/ -~~b next.~~l'''command, you can see that pwmchip1 is linked to fe6f0030.pwm, so pwm11 corresponds to pwmchip as pwmchip1</li>

~~'''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:/usr/src/wiringOP'''~~<div class="figure">

~~<ol start="2" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Compile and install wiringOP</li></ol>~~img271.png]]

~~orangepi~~</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:~$ # '''~~cd wiringOP~~echo 0 > /sys/class/pwm/pwmchip1/export'''

~~orangepi~~root@orangepi:~~~/wiringOP$~~ # '''~~sudo .~~echo 20000000 > /sys/class/pwm/pwmchip1/pwm0/~~build clean~~period'''

~~orangepi~~root@orangepi:~~~/wiringOP$~~ # '''~~sudo .~~echo 1000000 > /sys/class/pwm/pwmchip1/pwm0/~~build~~duty_cycle'''

~~<ol start="3" style="list-style-type~~root@orangepi: ~~decimal~~~# '''echo 1 >">~~<li>Test the output of the GPIO Readall command as follows<~~/~~li><~~sys/class/pwm/pwmchip1/pwm0/~~ol>~~enable'''|}

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

~~[[File:pi3b~~<li>The test method of pwm11 demonstrated above is similar to other pwm test methods.</li></ol>

~~</div>== 40Pin interface GPIO, I2C, UART, SPI, and PWM test~~ Python ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~Note that if you need~~ wiringOP-Python is the Python language version of wiringOP, which is used to ~~set overlays to open multiple configurations at~~ operate the hardware resources of the ~~same time~~development board, such as GPIO, I2C, SPI and UART, ~~please use a space to write~~ in ~~one line like~~ the ~~following space~~Python program.'''

~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''~~

'''~~overlays=spi3-m0-cs0-spidev i2c2-m1 i2c3-m0 uart7-m2 uart9-m2 pwm11-m1~~In addition, please note that all the following commands are operated under the root user.'''</big>|}

=== ~~40pin GPIO port test~~ wiringOP-Python installation method ===

~~'''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.'''~~# First install the dependency package

::{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''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.3v. Use this program to test whether the GPIO port can work normallysudo apt-get update'''

root@orangepi:~# '''~~The method of running blink_all_gpio program is shown below:~~ sudo apt-get -y install git swig python3-dev python3-setuptools'''|}

~~orangepi@orangepi3b~~<ol start="2" style="list-style-type:~$ decimal;"><li>Then use the following command to download the source code of wiringOP-Python</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~sudo blink_all_gpio~~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.''' ~~#Remember to add Sudo permissions~~

~~[sudo] password for orangepi: #You need to enter a password here~~

~~# A total of 28 GPIO ports~~ '''If there is a problem with the download code from GitHub, you can ~~be used in~~ use the ~~development board 40pin. Below~~ wiringOP-Python source code that comes with the Linux image directly, and the storage location is No:/usr/src/wiringOP-Python'''</big>|}{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''git clone --recursive https://github. ~~7 pins~~ com/orangepi-~~corresponding GPIO as GPIO4_A4~~ xunlong/wiringOP-~~corresponding WPI serial number 2~~ Python -~~as an example how to set the height of the GPIO port~~b next'''

~~[[File:pi3b-img259.png|576x120px]]~~ ~~<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>~~ root@orangepi:~~~/wiringOP~~# '''~~gpio mode 2 out~~cd wiringOP-Python'''

root@orangepi:~/wiringOP-Python# '''git submodule update --init --remote'''

|}

</ol>

<li>Then ~~set~~ use the ~~GPIO port~~ following command to ~~output the low level. After setting, you can use the value of~~ compile wiringOP-Python and install it into the ~~voltage~~ Linux system of the ~~pins with a multimeter. If it is 0v, it means that the low -electric flat is successful~~development board</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''cd wiringOP-Python'''

root@orangepi:~/wiringOP-Python# '''~~gpio write 2 0~~python3 generate-bindings.py > bindings.i''' ~~Using GPIO Readall, you can see the value of the No. 7 pin (v) to 0~~ ~~[[File:pi3b-img260.png|576x120px]]~~

root@orangepi:~/wiringOP-Python# '''sudo python3 setup.py install'''

|}

</ol>

<li>Then ~~set~~ enter the ~~GPIO port output high level. After setting, you can use the voltage of the voltage of the permanent meter to measure the voltage~~following command. If it there is ~~3.3V~~a help information output, it means that ~~the high~~Wiringop-~~electricity level~~ Python is ~~successful~~successfully installed. Press the '''q''' key to exit the interface of the help information</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''~~gpio write 2 1~~python3 -c "import wiringpi; help(wiringpi)"'''

~~Using GPIO Readall, you can see the value of No. 7 pin (v) into 1~~Help on module wiringpi:

~~[[File:pi3b-img261.png|576x118px]]~~

~~<ol start="5" style="list-style-type: 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>~~NAME

~~=== 40Pin GPIO Port -down and downward pull -down resistance setting method ===~~:wiringpi

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

~~[[File:pi3b-img262.png|575x353px]]~~DESCRIPTION

: # ~~Below the No~~This file was automatically generated by SWIG (http://www.swig.org). ~~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~~# Version 4.~~png|576x147px]]~~0.2

~~<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></ol>~~#

~~root@orangepi~~:~~~/wiringOP~~# ~~'''gpio mode 5 in'''~~ ~~<ol start="3" style="list-style-type: decimal;"><li>After the setting is set to input mode, execute the following command~~ Do not make changes to ~~set the GPIO port as the pull~~ this file unless you know what you are doing-~~down mode</li></ol>~~ ~~root@orangepi:~/wiringOP# '''gpio mode 5 up'''~~ ~~<ol start="4" style="list~~-~~style-type: decimal;"><li>Then enter the following command to read the level of the GPIO port. If the level is 1, it means that the drawing mode is successful</li></ol>~~ ~~root@orangepi:~/wiringOP# '''gpio read 5'''~~ ~~'''1'''~~modify

: # the SWIG interface file instead.

|}

</ol>

<li>~~Then execute~~ 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 ~~following~~ Python3 command to ~~set~~ enter the ~~GPIO port as the drop-down~~ command line modeof Python3</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''python3'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then import the Python module of WiringPi</li>~~root@orangepi~~{| 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;" |-| >>> '''~~gpio mode 5 down~~help(wiringpi)'''

~~<ol start="6" style="list-style-type~~Help on module wiringpi: ~~decimal;"><li>Then enter the following command to read the level of the GPIO port. If the level is 0, it means that the drop -down mode is set successfully</li></ol>~~

~~root@orangepi:~/wiringOP# '''gpio read 5'''~~

~~'''0'''~~NAME

~~=== 40pin SPI Test ===~~:wiringpi

~~# From the schematic diagram of the 40PIN interface, the SPI available for Orange Pi 3B is spi3~~

~~[[File:pi3b-img264.png|577x193px]]~~DESCRIPTION

~~'''In the Linux system, the SPI3 in 40pin is closed~~ : # This file was automatically generated by ~~default, and it needs to be opened manually to use~~SWIG (http://www.swig.org).~~'''~~

~~'''Add the configuration of the red font part below to the /boot/orangepiEnv~~: # Version 4.~~txt, and then restart the Linux system to open the spi3~~0.~~'''~~2

~~orangepi@orangepi~~:~~~$ '''sudo vim /boot/orangepiEnv.txt'''~~#

~~'''overlays=spi3~~: # Do not make changes to this file unless you know what you are doing-m0-~~cs0-spidev'''~~modify

~~<ol start="2" style="list-style-type~~: ~~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~~SWIG interface file instead. ~~You can use it directly</li></ol>~~

~~orangepi@orangepi:~$ '''ls /dev/spidev3.0'''~~

~~/dev/spidev3.0~~CLASSES

~~<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~~builtins. ~~You can see that the data of TX and RX is inconsistent</li></ol>~~object

~~orangepi@orangepi~~:~~~$ '''sudo spidev_test -v -D /dev/spidev3.0'''~~:GPIO

~~spi mode~~: ~~0x0~~:I2C

~~bits per word~~: 8:Serial

~~max speed~~: ~~500000 Hz (500 KHz)~~:nes

~~TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.~~

~~RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF | ............................…~~:class GPIO(builtins.object)

~~<ol start="4" style="list-style-type~~: ~~decimal;"><li>Then the two pins of the SPI3 MOSI~~ | GPIO(~~No. 19 pins in the 40pin interface) and MISO (No. 21 in the 40PIN interface~~pinmode=0) ~~run the output of SPIDEV_TEST as follows.You can see that sending and receiving data is the same.</li></ol>~~

~~[[File~~:~~pi3b-img265.png~~|~~577x83px]]~~

~~orangepi@orangepi:~$ '''sudo spidev_test -v -D /dev/spidev3.0'''~~

~~spi mode: 0x0~~>>>|}</ol></li></ol>

~~bits per word: 8~~=== 40pin GPIO port test ===

~~max speed~~{| class="wikitable" style="background-color: ~~500000 Hz (500 KHz)~~#ffffdc;width:800px;" |-| <big>'''wiringOP-Python is the same as wiringOP, you can also determine which GPIO pin to operate by specifying the wPi number, because there is no command to check the wPi number in wiringOP-Python, so you can only check the board wPi number and physical Correspondence between pins.'''</big>

~~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 | ......@.…▒..................▒.~~<div class="figure">

~~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~~ [[File:pi3b-img258.png| ~~......@.…▒..................▒.~~center]]

<~~span id="~~/div>|}# Below the No. 7 pin— corresponding to GPIO4_a4 -~~i2c~~corresponding WPI serial number 2 -~~test">=== 40pin I2C Test ===~~to demonstrate how to set the height of the GPIO port

~~# From the table below, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total of three groups of I2C bus~~::[[File:pi3b-img259.png]]

~~[[File~~<ol start="2" style="list-style-type: decimal;"><li>The steps of the command test are shown below directly:~~pi3b~~<ol style="list-~~img266~~style-type: lower-alpha;"><li>First set the GPIO port to the output mode.~~png~~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>{|~~576x160px]]~~class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''python3 -c "import wiringpi; \'''

'''~~It can be seen~~ from ~~the above table that i2c4_m0 and spi3_m0 are pins~~wiringpi import GPIO; wiringpi. ~~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~~wiringPiSetup() ; \'''

'''In wiringpi.pinMode(2, GPIO.OUTPUT) ; "'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then set the ~~Linux system~~GPIO port output low level. After setting, you can use the ~~i2c in 40Pin~~ voltage of the voltage of the universal meter to measure the pins. If it is ~~closed by default~~0V, ~~and~~ it ~~needs to be opened manually to use.~~means that the low -power flat is successful</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''python3 -c "import wiringpi; \'''

'''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 onefrom wiringpi import GPIO; wiringpi.wiringPiSetup() ;\'''

~~orangepi~~'''wiringpi.digitalWrite(2, GPIO.LOW)"'''|}</ol><ol start="3" 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 pins with a multimeter. If it is 3.3V, it means that the high -power flat is successful.</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ /wiringOP-Python# '''~~sudo vim /boot/orangepiEnv.txt~~python3 -c "import wiringpi; \'''

'''~~overlays=i2c2-m1 i2c3-m0 i2c4-m0'''~~ ~~<ol start="2" style="list-style-type: decimal~~from wiringpi import GPIO; wiringpi.wiringPiSetup() ;">~~<li>After starting the Linux system, first confirm that the i2c device node exists under/dev</li></ol>~~ ~~orangepi@orangepi:~# '''ls /dev/i2c-*'''~~ ~~/dev/i2c-0 '''/dev/i2c-2''' '''/dev/i2c-3''' '''/dev/i2c-4~~\''' ~~/dev/i2c-6~~

'''wiringpi.digitalWrite(2, GPIO.HIGH)"'''

|}

</ol>

</li></ol>

<li>~~Then connect a i2c device on~~ The steps of testing in the ~~i2c pin~~ command line of ~~the 40Pin connector~~Python3 are shown below: <ol style="list-style-type: lower-alpha;"><li>First use the Python3 command to enter the command line mode of Python3</olli> {| class="wikitable" style="width:800px;"

|-

|root@orangepi:~# '''python3'''|~~i2c2~~}</ol><ol start="2" style="list-style-type: lower-m1alpha;">~~|i2c3-m0~~<li>Then import the Python module of WiringPi</li>{|~~i2c4-m0~~class="wikitable" style="width:800px;"

|-

| ~~Sda Pin~~>>> '''import wiringpi''' >>> '''from wiringpi import GPIO'''|~~Corresponding~~ }</ol><ol start="3" 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 ~~No. 3~~ the pin~~|Corresponding to No~~, and the second parameter is the GPIO mode. ~~27 pin~~</li>{|~~Corresponding to No. 19 pin~~class="wikitable" style="width:800px;"

|-

| ~~Sck Pin|Corresponding to No~~>>> '''wiringpi.wiringPiSetup()''' 0 >>> '''wiringpi.pinMode(2, GPIO. ~~5 pin~~OUTPUT)'''|~~Corresponding to No~~}</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. ~~28 pin~~If it is 0V, it means that the low -power flat is set.</li>{|~~Corresponding to No. 23 pin~~class="wikitable" style="width:800px;"

|-

| ~~Vcc Pin|Corresponding to No~~>>> '''wiringpi.digitalWrite(2, GPIO. ~~1 pin~~LOW)'''|~~Corresponding to No~~}</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 pins with a multimeter. If it is 3. ~~1 pin~~3V, it means that the high -power flat is successful</li>{|~~Corresponding to No. 1 pin~~class="wikitable" style="width:800px;"

|-

| ~~Gnd Pin|Corresponding to No~~>>> '''wiringpi. ~~6 pin|Corresponding to No. 6 pin|Corresponding to No~~digitalWrite(2, GPIO. ~~6 pin~~HIGH)'''

|}

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

<li>~~Then use~~ Wiringop-Python Sets GPIO high and low levels in the Python code. For reference to the '''~~i2cdetect -y~~blink.py''' ~~command if~~ test program in Examples, the ~~address~~ voltage of the ~~connected I2C device can be detected, it means that~~ '''blink.py''' test program will set up the voltage of all GPIO ports in the ~~I2C can be used normally~~development board 40 PIN</li><{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~ol>~~wiringOP-Python# '''cd examples'''

~~orangepi~~root@orangepi:~~~$ sudo i2cdetect~~ /wiringOP-~~y 2~~ Python/examples#~~i2c2 command~~'''ls blink.py'''

~~orangepi@orangepi:~$ sudo i2cdetect -y 3 #i2c3 command~~'''blink.py'''

~~orangepi~~root@orangepi:~~~$ sudo i2cdetect~~ /wiringOP-~~y 4~~ Python/examples'''#~~i2c4 command~~python3 blink.py'''|}</ol>

~~<div class~~=~~"figure">~~== 40pin SPI test ===

~~[[File:pi3b-img267.png|476x179px|UN}~]Q}T_70O%Z%RNO8R@YE]]~~# From the schematic diagram of the 40pin interface, the SPI available for Orange Pi 3B is spi3

~~</div>=== 40pin UART test ===~~img264.png]]

::{| class="wikitable" style="background-color:# ~~As can be seen from~~ ffffdc;width:800px;" |-| <big>'''In the ~~table below~~Linux system, the ~~uart available for Orange Pi 3B~~ spi3 in 40pin is ~~uart3, uart7~~closed by default, and ~~uart9. There are three sets of uart bus~~ ~~[[File:pi3b-img268~~it needs to be opened manually to use.~~png|575x160px]]~~'''

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

'''In Add the ~~Linux system,~~ configuration of the red font part below to the ~~uart in 40pin is closed by default~~/boot/orangepiEnv.txt, and ~~it needs~~ then restart the Linux system to ~~be opened manually to use~~open the spi4.'''</big>

'''Add the configuration of the red font part below to the /boot/orangepiEnv.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..'''

orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''

'''overlays=~~uart3~~spi3-m0 ~~uart7~~-~~m2 uart9~~cs0-m2spidev'''|}

<li>~~After entering the Linux system, first confirm~~ First check whether there is a '''spidev3.0''' device node ~~corresponding to uart under/dev~~in the Linux system. If it exists, it means that the SPI3 has been set and can be used directly</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~# $ '''ls /dev/~~ttyS*'''~~ ~~/dev/ttyS1 '''/dev'''/'''ttyS3 /dev/ttyS7 /dev/ttyS9~~spidev3.0'''

/dev/spidev3.0

|}

</ol>

<li>~~Then start testing~~ 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 ~~uart interface, first use~~ following two parameters: <ol style="list-style-type: lower-alpha;"><li>'''--channel''': Specify the ~~rx and tx~~ channel number of SPI</li><li>'''--port''': Specify the ~~uart interface to be tested by DuPont~~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>{| class="wikitable" style="width:800px;"

|-

|~~|uart3|uart7|uart9~~|root@orangepi:~/wiringOP-~~| 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~~|}Python# '''cd examples'''

~~[[File~~root@orangepi:~~pi3b~~~/wiringOP-~~img269~~Python/examples# '''python3 spidev_test.~~png|545x134px]]~~py \'''

~~<ol start="4" style="list-style-type: decimal;"><li>Use the~~ '''~~gpio serial~~--channel 3 --port 0''' ~~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: lower-alpha;"><li>Test UART3</li></ol></li></ol>~~

~~orangepi@orangepi~~spi mode:~~~$ '''sudo gpio serial /dev/ttyS3'''~~0x0

~~[sudo] password for orangepi~~max speed: ~~#Enter the password here.~~500000 Hz (500 KHz)

~~Out: 0: ->~~ Opening device /dev/spidev3.0

~~Out~~TX | FF FF FF FF FF FF ''' 1#FF0000">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 |......@.......…|

~~Out~~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: ~~-&gt~~decimal; 2"><li>Then use the TXD (No. 19 pins in the 40Pin interface) and RXD (No. 21 pins in the 40pin interface) of the DuPont line short connection SPI3. Like sending and receiving data, it means that the SPI3 loop test is normal</li>~~Out~~{| class="wikitable" style="width: 3800px;" |-| root@orangepi: ~/wiringOP-~~> 3~~Python# '''cd examples'''

~~Out: 4~~root@orangepi: ~/wiringOP-~~> 4~~Python/examples# '''python3 spidev_test.py \'''

~~Out: 5:~~ '''-~~> 5^C~~-channel 3 --port 0'''

~~<ol start="2" style="list-style-type~~spi mode: ~~lower-alpha;"><li>Test UART7</li></ol>~~0x0

~~orangepi@orangepi~~max speed:~~~$ '''sudo gpio serial /dev/ttyS7'''~~500000 Hz (500 KHz)

~~[sudo] password for orangepi: #Enter the password here~~Opening device /dev/spidev3.0

~~Out~~TX | FF FF FF FF FF FF ''' 0#FF0000">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 |......@.......…|

~~Out: 1~~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 |......@.......…||}</ol> 1">

~~Out: 2: -> 2~~=== 40pin I2C test ===

~~Out: 3~~<ol start="1" style="list-style-type: ~~-&gt~~decimal; 3"><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>

~~Out: 4~~[[File: pi3b-~~> 4~~img266.png]]

~~Out~~{| class="wikitable" style="background-color: 5#ffffdc;width: 800px;" |-| <big>'''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-~~&gt~~color:#ffffdc;width:800px; ~~5^C~~" |-| <big>'''In the Linux system, the I2C in 40Pin is closed by default, and it needs to be opened manually to use.'''

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

~~<li>Test UART9</li></ol>~~

~~orangepi@orangepi:~$~~ '''~~sudo gpio serial~~ Add the configuration of the red font part below to the/~~dev~~boot/~~ttyS9~~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.'''</big>

~~[sudo] password for orangepi: #Enter the password here.~~

~~Out~~orangepi@orangepi: ~~0: -> 0~~~$ '''sudo vim /boot/orangepiEnv.txt'''

~~Out~~'''overlays=i2c2-m1 i2c3-m0 i2c4-m0'''|}</ol><ol start="2" style="list-style-type: ~~-&gt~~decimal; 1"><li>After starting the Linux system, first confirm the I2C device node under/dev.</li>

~~Out~~{| class="wikitable" style="width: 2800px;" |-| orangepi@orangepi: ~# '''ls /dev/i2c-~~> 2~~*'''

~~Out:~~ /dev/i2c-0      '''/dev/i2c-2'''      '''/dev/i2c-3: '''      '''/dev/i2c-4'''    &gtnbsp; /dev/i2c-6|}</ol><ol start="3" 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.</li>

~~Out~~{| class="wikitable" style="width: 4800px;text-align: center;"|-||i2c2-~~> 4~~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~~Out: 5:~~ |-~~> 5^C~~| Gnd Pin|Corresponding to No. 6 pin|Corresponding to No. 6 pin|Corresponding to No. 6 pin|}

[[File:pi3b-img273.png]]<~~span id~~/ol><ol start="~~pwm~~4" style="list-~~test~~style-~~method~~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</~~span~~li>{| class="wikitable" style=~~= PWM test method ===~~"width:800px;" |-| orangepi@orangepi:~$ sudo i2cdetect -y 2 #i2c2 command

orangepi@orangepi:~$ sudo i2cdetect -y 3 # ~~From the table below, the pwm11 available for Orange Pi 3B~~i2c3 command

~~[[File~~orangepi@orangepi:~~pi3b~~~$ sudo i2cdetect -~~img270.png~~y 4 #i2c4 command|~~575x160px]]~~}

~~'''In the Linux system, the pwm in 40pin is closed by default, and it needs to be opened manually to use..'''~~<div class="figure">

~~'''Add the configuration of the red font part below to the /boot/orangepiEnv~~[[File:pi3b-img274.~~txt, and then restart the Linux system to open the pwm11.'''~~png]]

~~orangepi~~</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''' to read the RTC time</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ /wiringOP-Python# '''~~sudo vim /boot/orangepiEnv.txt~~cd examples'''

root@orangepi:~/wiringOP-Python/examples# '''~~overlays=pwm11~~python3 ds1307.py --m1device \'''

~~<ol start="2" style="list-style-type: decimal;"><li>After opening a pwm, a pwmchipX (X is a specific number) will be available in~~'''"/~~sys/class/pwm~~dev/i2c-4"'''~~</li></ol>~~

~~orangepi@orangepi~~Thu 2023-01-05 14:~~~$ '''ls /sys/class/pwm/'''~~57:55

~~pwmchip0 pwmchip1~~Thu 2023-01-05 14:57:56

~~<ol start="3" style="list~~Thu 2023-~~style~~01-~~type~~05 14: ~~decimal;"><li>Which pwmchip corresponds to pwm11 above? Let's first check out the output of '''ls /sys/class/pwm/ -l''' command, as shown below~~57: ~~</li>~~<li>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>57

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

~~[[File:pi3b~~exit|}</ol>

~~</div><ol start~~=~~"5" style~~=~~"list-style-type: decimal;"><li>Then use the following command to allow pwm11 to output a 50Hz square wave (please switch to the root user first, and then execute the following command)</li></ol>~~= 40pin's UART test ===

~~root@orangepi:~~~# ~~'''echo 0 > /sys/class/pwm/pwmchip1/export'''~~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

~~root@orangepi~~:~~~# '''echo 20000000 > /sys/class/pwm/pwmchip1/pwm0/period'''~~:[[File:pi3b-img268.png]]

~~root@orangepi~~:~:{| class="wikitable" style="width:800px;background-color:# ffffdc;" |-| <big>'''~~echo 1000000 > /sys/class/pwm/pwmchip1/pwm0/duty_cycle~~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>|}

~~root@orangepi~~:~:{| class="wikitable" style="width:800px;background-color:# ffffdc;" |-| <big>'''~~echo 1 > /sys/class/pwm/pwmchip1/pwm0/enable~~In the Linux system, the UART in 40pin is closed by default, and it needs to be opened manually to use.'''

~~[[File:pi3b-img272~~'''Add the configuration of the red font part below to the /boot/orangepiEnv.~~png|575x346px]]~~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'''</big>

~~<~~orangepi@orangepi:~$ '''sudo vim /~~span>== How to install and use Wiringop-Python ==~~boot/orangepiEnv.txt'''

'''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 program.''' ~~'''Please note that all the following command below is operated under the root user.'''~~ overlays=uart3-~~python~~m0 uart7-~~installation~~m2 uart9-~~method">~~m2~~=== Wiringop-Python installation method ===~~ ~~# First install the dependency package~~ ~~root@orangepi:~# '''sudo apt-get update~~''' ~~root@orangepi:~# '''sudo apt-get -y install git swig python3-dev python3-setuptools'''~~|}

<li>~~Then use~~ After entering the ~~following command~~ Linux system, first confirm whether there is a device node corresponding to ~~download the source code of wiringOP-Python~~UART under/dev</li~~></ol~~>

'''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.'''{| class="wikitable" style="width:800px;" ~~'''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'''~~| ~~root~~orangepi@orangepi:~# '''~~git clone --recursive https://github.com~~ls /~~orangepi-xunlong~~dev/~~wiringOP-Python -b next'''~~ ~~root@orangepi:~# '''cd wiringOP-Python'''~~ ~~root@orangepi:~/wiringOP-Python# '''git submodule update --init --remote~~ttyS*'''

/dev/ttyS1      '''/dev/ttyS3      /dev/ttyS7      /dev/ttyS9'''

|}

</ol>

<li>Then start testing the UART interface, and first use the ~~following command to compile wiringOP-Python~~ RX and ~~install it into the Linux system~~ TX of the ~~development board~~UART interface to be tested by DuPont</li>~~</ol>~~ ~~root@orangepi:~# '''cd wiringOP-Python'''~~ ~~root@orangepi:~/wiringOP-Python# '''python3 generate-bindings.py > bindings.i'''~~ ~~root@orangepi:~/wiringOP-Python# '''sudo python3 setup.py install'''~~

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

<li>~~Then enter the following command. If there is a help information output, it means that Wiringop-Python is successfully installed. Press~~ Use the '''qserialTest.py''' ~~key~~ program in Examples to ~~exit~~ test the ~~interface~~ loop function of the ~~help information~~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</olli>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python/examples# '''python3 serialTest.py --device \'''

~~root@orangepi:~/wiringOP-Python#~~ '''~~python3 -c~~ "~~import wiringpi; help(wiringpi)~~/dev/ttyS3"'''

~~Help on module wiringpi:~~

~~NAME~~Out: 0: -> 0

~~wiringpi~~Out: 1: -> 1

~~DESCRIPTION~~Out: 2: -> 2

~~# This file was automatically generated by SWIG (http~~Out:~~//www.swig.org).~~3: -> 3

~~# Version~~ Out: 4~~.0.2~~:^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 \'''

~~# Do not make changes to this file unless you know what you are doing--modify~~'''"/dev/ttyS7"'''

~~# the SWIG interface file instead.~~

~~<ol start="5" style="list-style-type~~Out: ~~decimal;"><li>Test whether the Wiringop-Python is installed successfully under the Python command line is shown below: <ol style="list-style-type~~0: ~~lower~~-~~alpha~~>">~~<li>First use the Python3 command to enter the command line mode of Python3</li></ol></li></ol>~~0

~~root@orangepi~~Out:~~~# '''python3'''~~1: -> 1

~~<ol start="~~Out: 2~~" style="list-style-type~~: ~~lower~~-~~alpha~~>">~~<li>Then import the Python module of WiringPi</li></ol>~~2

Out: 3: ->~~>> '''import wiringpi;'''~~3

~~<ol start="3" style="list-style-type~~Out: ~~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></ol>~~4:^C

~~&gt~~exit|}</ol><ol start="3" style="list-style-type: lower-alpha;~~>&gt~~"><li>Test UART9</li>{| class="wikitable" style="width:800px; " |-| root@orangepi:~/wiringOP-Python/examples# '''~~help(wiringpi)~~python3 serialTest.py --device \''' ~~Help on module wiringpi:~~

~~NAME~~'''"/dev/ttyS9"'''

~~wiringpi~~

~~DESCRIPTION~~Out: 0: -> 0

~~# This file was automatically generated by SWIG (http~~Out:~~//www.swig.org).~~1: -> 1

~~# Version 4.0.~~Out: 2: -> 2

#Out: 3: -> 3

~~# Do not make changes to this file unless you know what you are doing--modify~~Out: 4:^C

# exit|}</ol></li></ol>

~~CLASSES~~== Hardware watch the door dog test ==

~~builtins~~The WatchDog_test program is pre -installed in the Linux system released by Orange PI, which can be tested directly.~~object~~

~~GPIO~~The method of running the WatchDog_test program is shown below:

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

~~Serial~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo watchdog_test 10'''

~~nes~~open success

~~class GPIO(builtins.object)~~options is 33152,identity is sunxi-wdt

~~| GPIO(pinmode=~~put_usr return,if 0,success:0)

|The old reset time is: 16

~~>>>~~return ENOTTY,if -1,success:0

~~=== 40pin GPIO port test ===~~,success:0

'''Wiringop-Python is the same as Wiringop. You can also determine which GPIO pink can be determined by specifying the WPI number. Because there is no command to check the WPI number in Wiringop-Pythonput_user return, ~~you can only check the board WPI number and physical physical physics through the GPIO command in Wiringop. The corresponding relationship of the pin.'''~~if 0,success:0

~~<div class="figure">~~put_usr return,if 0,success:0

~~[[File:pi3b-img258.png|575x355px|66AC(IBG%N8L@Y7(1BZPS`N]]~~keep alive

~~</div># Below the No. 7 pin — corresponding to GPIO4_a4 -corresponding WPI serial number 2 -to demonstrate how to set the height of the GPIO port~~keep alive

~~[[File:pi3b~~keep alive|}</ol>

~~<ol start~~=~~"2" style~~=~~"list-style-type: decimal;"><li>The steps of the command test are shown below directly: <ol style="list-style-type: lower-alpha;"><li>First set the GPIO port to the output mode. The first parameter of the '''pinMode''' function is~~ Check the serial number of the ~~wpi corresponding to the pin, and the second parameter is the GPIO mode</li></ol></li></ol>~~RK3566 chip ==

~~root@orangepi:~/wiringOP-Python# '''python3 -c "import wiringpi; \'''~~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.

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~from wiringpi import GPIO; wiringpi~~cat_serial.~~wiringPiSetup() ; \~~sh'''

Serial : '''~~wiringpi.pinMode(2, GPIO.OUTPUT) ; "~~8fa18eaf489041f0'''|}

<~~ol start~~span id="~~2" style="list~~the-method-of-downloading-~~style~~and-~~type: lower~~installing-~~alpha;"><li>Then set~~ the ~~GPIO port output low level. After setting, you can use the voltage of the voltage~~ -balenaetcher-version-of ~~the universal meter to measure the pins. If it is 0V, it means that the low~~ -~~power flat is successful</li~~arm64"></olspan>

~~root@orangepi:~/wiringOP-Python# '''python3 -c "import wiringpi; \'''~~== The method of downloading and installing the balenaEtcher version of arm64 ==

<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>{| 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'''~~from wiringpi import GPIO~~|}</ol><ol start="2" style="list-style-type: lower-alpha; ~~wiringpi~~"><li>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.~~wiringPiSetup() ;\~~com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balenaEtcher-1.7.9+5945ab1f-arm64.AppImage'''|}

~~'''wiringpi.digitalWrite(2, GPIO.LOW)"'''~~<div class="figure">

~~<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~~img275.~~</li></ol>~~png]]

~~root@orangepi:~~~</div></~~wiringOP-Python# '''python3 -c "import wiringpi; \'''~~ ~~'''from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\'''~~ ~~'''wiringpi.digitalWrite(2, GPIO.HIGH)"'''~~ol></li></ol><ol start="32" style="list-style-type: decimal;"><li>~~The steps of testing in~~ How to install and use the ~~command line~~ deb version of ~~Python3 are shown below~~Balenaetcher:

<li>~~First use the Python3 command to enter the command line mode~~ deb version of ~~Python3~~Balenaetcher installation commands as shown below: </li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-| ~~root~~orangepi@orangepi:~# $ '''~~python3~~sudo apt install -y \'''

'''--fix-broken ./balena-etcher-electron_1.7.9+5945ab1f_arm64.deb'''

|}

</ol>

<li>~~Then import~~ After the ~~Python module~~ deb version of ~~WiringPi~~Balenaetcher is installed, it can be opened in the Application</li~~></ol~~>

~~>>> '''import wiringpi'''~~<div class="figure">

~~>>> '''from wiringpi import GPIO'''~~[[File:pi3b-img89.png]]

</div></ol>

<li>~~Then set the GPIO port as the output mode.~~ The ~~first parameter of the '''pinMode''' function~~ interface after Balenaetcher is ~~the serial number of the wpi corresponding to the pin, and the second parameter~~ opened is ~~the GPIO mode.~~shown below: </li~~></ol~~>

~~>>> '''wiringpi.wiringPiSetup()'''~~<div class="figure">

0[[File:pi3b-img276.png]]

~~&gt~~</div></ol></li></ol><ol start="3" style="list-style-type: decimal;~~&gt~~"><li>How to use the AppImage version of balenaEtcher: <ol style="list-style-type: lower-alpha;~~&gt~~"><li>First add permissions to Balenaetcher</li>{| class="wikitable" style="width:800px; " |-| orangepi@orangepi:~/Desktop$ '''~~wiringpi~~chmod +x balenaEtcher-1.~~pinMode(2, GPIO~~7.9+5945ab1f-arm64.~~OUTPUT)~~AppImage'''|}</ol><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>

[[File:pi3b-img277.png]]</ol ~~start="4" style="list-style-type: lower-alpha;"~~></li>~~Then set~~ </ol><span id="the ~~GPIO port output low level. After setting, you can use the value~~ -installation-method-of -the ~~voltage of the pins with a multimeter. If it is 0V, it means that the low~~ -~~power flat is set.</li~~bt-panel-linux-panel"></olspan>

~~>>> '''wiringpi.digitalWrite(2, GPIO.LOW)'''~~== The installation method of the Bt-Panel Linux panel ==

~~<ol start~~{| class="5wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~Then set~~ '''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 ~~GPIO port output high level~~[https://www. ~~After setting, you can use the value of the voltage of the pins with a multimeter~~bt. ~~If it is 3~~cn/new/index.~~3V, it means that~~ html official website of the ~~high~~ Bt-~~power flat is successful~~Panel])'''</~~li></ol~~big>|}

~~>>>~~ # First of all, the size of the'''~~wiringpi~~/tmp''' space is needed.~~digitalWrite(2~~After setting, ~~GPIO.HIGH)~~you need to '''restart the Linux system of the development board''', and the command is shown below:

~~<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~~ | orangepi@orangepi:~$ '''~~blink.py~~sudo sed -i '~~'' test program in Examples~~s/nosuid/&, ~~the voltage of the~~ size=2G/'/etc/fstab''~~blink.py~~'~~'' test program will set up the voltage of all GPIO ports in the development board 40 PIN</li></ol>~~

~~root~~orangepi@orangepi:~~~/wiringOP-Python#~~ $ '''~~cd examples~~sudo reboot'''|}

~~root~~<ol start="2" style="list-style-type: decimal;"><li>After restarting, you can see that the size of the'''/tmp''' space has become 2G.</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~~~/wiringOP-Python/examples#~~ $ '''~~ls blink.py~~df -h | grep "/tmp"'''

tmpfs      2.0G      12K      '''~~blink~~2.py0G'''      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:800px;" |-| orangepi@orangepi:~$ '''sudo install_bt_panel.sh'''|}</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;" |-| +----------------------------------------------------------------------

~~root@orangepi:~~~| Bt-WebPanel FOR CentOS/~~wiringOP-Python~~Ubuntu/Debian</~~examples'''# python3 blink.py'''~~p>

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

~~[[File:pi3b~~+----------------------------------------------------------------------~~img264.png|577x193px]]~~

~~'''In the Linux system, the spi3 in 40pin is closed by default, and it needs to~~ | The WebPanel URL will be ~~opened manually to use~~http://SERVER_IP:8888 when installed.~~'''~~

~~'''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 /boot/orangepiEnv.txt'''~~

Do you want to install Bt-Panel to the /www directory now?(y/n): '''~~overlays~~y'''|}</ol><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>

[[File:pi3b-img278.png|800px]]</ol><ol start="26" style="list-style-type: decimal;"><li>~~First check whether there is a~~ At this time, enter the '''~~spidev3.0~~panel address''' ~~device node~~ displayed above in the browser to open the login interface of the pagoda Linux ~~system~~panel, and then enter the '''username''' and '''password''' displayed in the corresponding position to log in to the Bt-Panel [[File:pi3b-img279.png|1200px]]</li><li>After successfully logging in to the pagoda, the following welcome interface will pop up. ~~If it exists~~First, ~~it means that~~ please take the ~~SPI3 has been set~~ 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 ~~be used directly~~enter the Bt-Panel</lip></olli>

~~orangepi@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 ('''ls https:/~~dev~~/~~spidev3~~www.0bt.cn''') to register one.</li>

[[File:pi3b-img281.png|1200px]]</~~dev~~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</~~spidev3.0~~li>

~~<ol start="3" style="list~~[[File:pi3b-~~style-type: decimal;">~~img282.png|1200px]]~~<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:~~ </pol><ol start="10" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~'''--channel''': Specify~~ More functions of the ~~channel number of SPI</li><li>'''-~~Bt-~~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~~ Panel can ~~see that~~ refer to the ~~data of TX and RX are inconsistent~~following information to explore by yourself</li~~></ol~~>

~~root@orangepi~~{| class="wikitable" style="width:~800px;" |-| Manual: [http://~~wiringOP-Python#~~ docs.bt.cn '''~~cd examples~~http://docs.bt.cn''']

~~root@orangepi~~Forum address: [https:~/~~wiringOP-Python~~/~~examples#~~ www.bt.cn/bbs '''~~python3 spidev_test~~https://www.bt.~~py \~~cn/bbs''']

GitHub Link: '''https://github.com/aaPanel/BaoTa'''|}</ol>

~~spi mode: 0x0~~== Set the Chinese environment and install Chinese input method ==

~~max speed~~{| class="wikitable" style="background-color: ~~500000 Hz (500 KHz)~~#ffffdc;width:800px;" |-| <big>'''Note that before installing the Chinese input method, please make sure that the Linux system used in the development board is the desktop version system.'''</big>|}

~~Opening device~~ </~~dev/spidev3.0~~span>=== Debian system installation method ===

~~TX | FF FF FF FF FF FF~~ <ol style="list-style-type: decimal;"><li>First set the default '''~~40 00 00 00 00 95~~locale''' ~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…|~~as Chinese<ol style="list-style-type: lower-alpha;"><li>Enter the command below to start configured '''locale'''</li>

RX {| ~~FF FF FF FF FF FF~~ class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~FF FF FF FF FF FF~~sudo dpkg-reconfigure locales''' ~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |.............….~~|}</ol><ol start="52" style="list-style-type: ~~decimal~~lower-alpha;"><li>Then ~~use the TXD (No~~select '''zh_CN. ~~19 pins~~ UTF-8 UTF-8''' in the ~~40Pin~~ pop-up interface) (to move up and down through the upper and ~~RXD (No. 21 pins in~~ lower direction buttons on the ~~40pin interface) of~~ keyboard, select it through the ~~DuPont line short connection SPI3. Like sending~~ space key, and ~~receiving data~~finally move the cursor to '''<OK>''' through the TAB key, ~~it means that~~ then press the ~~SPI3 loop test is normal~~ENTER key )</li~~></ol~~>

~~root@orangepi~~[[File:~pi3b-img283.png|1200px]]</~~wiringOP~~ol><ol start="3" style="list-style-type: lower-~~Python#~~ alpha;"><li>Then set the default '''locale''' as '''~~cd examples~~zh_CN.UTF-8'''</li>

~~root~~[[File:pi3b-img284.png|1200px]]</ol><ol start="4" style="list-style-type: lower-alpha;"><li>After exiting the interface, the '''locale''' settings will be started. The output displayed by the command line is shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~~~/wiringOP-Python/examples#~~ $ '''~~python3 spidev_test.py \~~sudo dpkg-reconfigure locales'''

~~'''--channel 3 --port 0'''~~Generating locales (this might take a while)...

~~spi mode~~: ~~0x0~~en_US.UTF-8... done

~~max speed~~: ~~500000 Hz (500 KHz)~~zh_CN.UTF-8... done

~~Opening device~~ Generation complete.|}</ol></li></~~dev~~ol><ol start="2" style="list-style-type: decimal;"><li>Then open '''Input Method'''</~~spidev3.0~~li>

~~TX | FF FF FF FF FF FF~~ [[File:pi3b-img285.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then select '''~~40 00 00 00 00 95~~OK''' ~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…|~~</li>

~~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 |~~[[File:pi3b-img286.~~.....@.......…|~~png]]</ol><~~span id~~ol start="4" style="~~pin~~list-~~i2c~~style-~~test-1~~type: decimal;"><li>Then select '''Yes'''</~~span~~li>~~=== 40pin I2C test ===~~

[[File:pi3b-img287.png]]

</ol>

<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~~Then select '''fcitx'''</li~~></ol~~>

[[File:pi3b-~~img266~~img288.png~~|576x160px~~]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then select '''OK'''</li>

[[File:pi3b-img289.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>'''~~It can be seen from~~ Then restart the ~~above table that I2C4_M0 and SPI3_M0 are pins. The two cannot be opened at~~ Linux system to make the ~~same time. I2C3_M0 and UART3_M0 are also reused. The two cannot be opened at the same time~~configuration effective'''</li><li>Then open '''Fcitx configuration'''</li>

~~'''In~~ [[File:pi3b-img290.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then click the ~~Linux system,~~ + of the ~~I2C~~ position shown in ~~40Pin is closed by default, and it needs to be opened manually to use.'''~~the figure below</li>

[[File:pi3b-img291.png]]</ol><ol start="10" style="list-style-type: decimal;"><li>Then search '''Google Pinyin'''~~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.~~click '''OK'''</li>

~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''~~<div class="figure">

~~'''overlays=i2c2~~[[File:pi3b-~~m1 i2c3-m0 i2c4-m0'''~~img292.png]]

</div></ol><ol start="611" style="list-style-type: decimal;"><li>~~After starting the Linux system, first confirm~~ Then put '''Google Pinyin''' to the ~~I2C device node under/dev.~~front</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~# '''ls /dev/i2c~~pi3b-*'''img293.png]]

~~/dev/i2c~~[[File:pi3b-~~0 '''~~img294.png]]</~~dev/i2c~~ol><ol start="12" style="list-~~2''' '''/dev/i2c~~style-3type: decimal;"><li>Then open the ''' Geany'''editor to test the Chinese input method</~~dev/i2c-4''' /dev/i2c-6~~li>

[[File:pi3b-img295.png]]</ol><ol start="713" style="list-style-type: decimal;"><li>~~Then connect a I2C device on the I2C pin of the 40PIN connector. Here~~ The Chinese input method test is ~~an example of the DS1307 RTC module.~~shown below</li~~></ol~~>

~~{| class~~[[File:pi3b-img296.png]]</ol><ol start="~~wikitable~~14" style="|list-style-type: decimal;">|~~|i2c2-m1~~<li>You can switch the Chinese and English input method through the '''Ctrl+Space''' shortcut</li>~~|i2c3~~<li>If the entire system is required as Chinese, the variables in '''/etc/default/locale''' can be set to '''zh_CN.UTF-m08'''</li>{|~~i2c4-m0~~class="wikitable" style="width:800px;"

|-

| ~~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:~$ '''sudo vim /etc/default/locale'''

[[# File~~:pi3b~~generated by update-~~img273.png|180x153px]]~~locale

LC_MESSAGES='''<~~ol start="8"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">zh_CN.UTF-8<li/span>~~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>~~

~~orangepi@orangepi~~LANG='''zh_CN.UTF-~~y 2 #i2c2 command~~8'''

~~orangepi@orangepi~~LANGUAGE='''zh_CN.UTF-~~y 3~~ 8'''|}</ol><ol start="16" style="list-style-type: decimal;"><li>Then '''restart the system''' to see the system displayed as Chinese</li>

~~orangepi@orangepi~~[[File:~~~$ sudo i2cdetect~~ pi3b-~~y 4 #i2c4 command~~img297.png]]</ol>

~~<div class~~=~~"figure">~~== The installation method of Ubuntu 20.04 system ===

~~[[File:pi3b-img274.png|464x174px|V@(61L~0})Q`8VLBCAYEP[2]]~~# First open '''Language Support'''

~~</div><ol start="9" style="list~~::[[File:pi3b-~~style-type: decimal;"><li>You can then run the time of the ds '''ds1307~~img298.~~py''' test program in '''examples''' to read the RTC time</li></ol>~~png]]

~~root@orangepi~~<ol start="2" style="list-style-type:~~~/wiringOP-Python#~~ decimal;"><li>Then find '''~~cd examples~~Chinese (China)'''option</li>

~~root@orangepi~~[[File:~pi3b-img299.png]]</~~wiringOP~~ol><ol start="3" style="list-style-~~Python/examples#~~ type: decimal;"><li>Then use the left mouse button to select '''~~python3 ds1307.py --device \~~Chinese (China)'''and hold it down, and then drag it up to the beginning. The display is shown below: </li>

~~'''"/dev/i2c~~[[File:pi3b-~~4"'''~~img300.png]]

~~Thu 2023~~{| class="wikitable" style="background-~~01-05 14~~color:57#ffffdc;width:55800px;" |-~~Thu 2023~~| <big>'''Note that this step is not easy to drag, please try more patiently.'''</big>|}</ol><ol start="4" style="list-01style-~~05 14~~type:~~57:56~~decimal;"><li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system</li>

~~Thu 2023~~[[File:pi3b-01img301.png]]</ol><ol start="5" style="list-~~05 14:57~~style-type:57decimal;"><li>Then set the '''Keyboard input method system''' to '''fcitx'''</li>

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

~~exit~~[[File:pi3b-img303.png]]</ol><ol start="8" 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="~~pins~~9" style="list-~~uart~~style-~~test.~~type: decimal;"><~~/span~~li>~~=== 40pin~~Then we can open the '''Geany'''~~s UART~~ to test ~~===~~Chinese input method , and the way to open is shown in the figure below</li>

~~# As can be seen from the table below~~[[File:pi3b-img305.png]]</ol><ol start="10" style="list-style-type: decimal;"><li>After opening '''Geany''', the ~~UART available for Orange Pi 3B~~ default is ~~UART3~~an English input method. We can switch into Chinese input method through the '''Ctrl+Space''' shortcut keys, ~~UART7~~ and ~~UART9. There are three sets of UART bus~~then we can enter Chinese</li>

[[File:pi3b-~~img268~~img306.png~~|575x160px~~]]</ol>

~~'''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'''~~=== The installation method of ubuntu 22.04 system ===

# First open '''~~In the Linux system, the UART in 40pin is closed by default, and it needs to be opened manually to use.'''~~ '''Add the configuration of the red font part below to the /boot/orangepiEnv.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 oneLanguage Support'''

~~orangepi@orangepi~~:~~~$ '''sudo vim /boot/orangepiEnv~~:[[File:pi3b-img298.~~txt'''~~ ~~'''overlays=uart3-m0 uart7-m2 uart9-m2'''~~png]]

<li>~~After entering the Linux system, first confirm whether there is a device node corresponding to UART under/dev~~Then find '''Chinese (China)''' option</li~~></ol~~>

~~orangepi@orangepi~~[[File:~# pi3b-img307.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then use the left mouse button to select '''ls /dev/ttyS*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>

~~/dev/ttyS1 '''/dev'''/'''ttyS3 /dev/ttyS7 /dev/ttyS9'''~~[[File:pi3b-img308.png]]

~~<ol start~~{| class="3wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">~~<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>~~ ~~{| class="wikitable~~"

|-

|}

</ol>

<li>~~Use~~ Then select the '''~~serialTest.py~~Apply System-Wide''' ~~program in Examples~~ to ~~test~~ apply the ~~loop function of the serial port. If you can see the printing below, it means that~~ Chinese settings to the ~~serial communication is normal<ol style="list-style-type: lower-alpha;"><li>Test UART3</li></ol>~~entire system</li~~></ol~~>

~~root@orangepi~~[[File:~pi3b-img309.png]]</~~wiringOP~~ol><ol start="5" style="list-~~Python~~style-type: decimal;"><li>'''Then restart the Linux system to make the configuration effective</~~examples#~~ span>'''~~python3 serialTest.py~~ </li><li>After re -~~-device \~~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>

~~'''&quot~~[[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</~~dev/ttyS3"'''~~li>

~~Out~~[[File: 0pi3b-img304.png]]</ol><ol start="8" style="list-style-type: ~~-&gt~~decimal; 0"><li>Then open the Fcitx5 configuration program</li>

~~Out~~[[File: 1pi3b-img310.png]]</ol><ol start="9" style="list-style-type: ~~-&gt~~decimal; 1"><li>Then choose to use Pinyin input method</li>

~~Out: 2: -> 2~~<div class="figure">

~~Out: 3~~[[File: pi3b-~~> 3~~img311.png]]

~~Out~~</div></ol><ol start="10" style="list-style-type: ~~4:^C~~decimal;"><li>The interface after the selection is shown below, then click OK</li>

~~exit~~[[File:pi3b-img312.png]]</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>

[[File:pi3b-img305.png]]</ol><ol start="212" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Test UART7~~After opening '''Geany''', it is still an English input method by default. We can switch into Chinese input methods through the '''Ctrl+Space''' shortcut keys, and then we can enter Chinese</li~~></ol~~>

~~root@orangepi~~[[File:~pi3b-img313.png]]</~~wiringOP~~ol>

~~'''"/dev/ttyS7"'''~~== How to remotely log in to the Linux system desktop method ==

~~Out~~{| class="wikitable" style="background-color: 0#ffffdc;width: 800px;" |-~~> 0~~| <big>'''Ubuntu Gnome Wayland image does not support Nomachine and VNCs introduced here to remotely log in to the desktop.'''</big>|}

~~Out: 1:~~ 1nomachine-remote-login">=== Use nomachine remote login ===

~~Out~~{| class="wikitable" style="background-color: 2#ffffdc;width: 800px;" |-~~> 2~~| <big>'''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: '''

~~Out~~'''https: 3//knowledgebase.nomachine.com/DT10R00166'''</big>|}{| class="wikitable" style="background-color: #ffffdc;width:800px;" |-~~&gt~~| <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; 3" |-| <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>|}

~~Out~~<ol style="list-style-type: 4decimal;"><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:^C800px;" |-| [https://www.nomachine.com/download/download&id=112&s=ARM '''https://downloads.nomachine.com/download/?id=118&distro=ARM''']~~exit~~|}

[[File:pi3b-img314.png]]</ol><ol start="32" style="list-style-type: lower-alpha;"><li>~~Test UART9~~In addition, you can also download the installation package to '''NoMachine''' in the '''official tools'''.</li~~></ol~~>

~~root@orangepi~~[[File:~~~/wiringOP~~pi3b-~~Python/examples# '''python3 serialTest~~img315.~~py --device \'''~~png]]

First enter the '''~~"/dev/ttyS9"~~remote login software-Nomachine'''folder

~~Out: 0~~[[File: pi3b-~~> 0~~img316.png]]

~~Out: 1: -> 1~~Then download the ARM64 version of the DEB installation package

~~Out~~[[File: pi3b-img317.png]]</ol><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>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg -i nomachine_x.x.x_x_arm64_arm64.deb'''|}</ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>Then download the nomachine software Windows version of the installation package, the download address is shown below</li>{| class="wikitable" style="background-~~&gt~~color:#ffffdc;width:800px; 2" |-| <big>'''Note that this download link may change.'''</big>|}{| class="wikitable" style="width:800px;" |-| '''https://downloads.nomachine.com/download/?id=9'''|}

~~Out~~[[File: pi3b-img318.png]]</ol><ol start="3" style="list-style-type: ~~-&gt~~decimal; 3"><li>Then install nomachine in Windows. '''Please restart the computer after installation'''</li><li>Then open '''NoMachine''' in Window</li>

~~Out~~[[File: 4pi3b-img319.png]]</ol><ol start="5" style="list-style-type:^Cdecimal;"><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>

~~exit~~[[File:pi3b-img320.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then click '''OK'''</li>

[[File:pi3b-img321.png]]<~~span id~~/ol><ol start="~~hardware-watch~~7" style="list-~~the~~style-~~door-dog-test~~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</~~span~~li>

~~The WatchDog_test program is pre~~ [[File:pi3b-~~installed in the Linux system released by Orange PI, which can be tested directly~~img322.png]]

~~The method~~ </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 ~~running~~ the ~~WatchDog_test program is shown below~~development board Linux system[[File: pi3b-img323.png]]</li></ol>

~~<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>~~== Use VNC remote login ===

~~orangepi@orangepi~~{| class="wikitable" style="background-color:~$ #ffffdc;width:800px;" |-| <big>'''~~sudo watchdog_test 10~~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.'''

~~open success~~'''Ubuntu 20.04 tests many problems with VNC, please do not use this method.'''</big>|}

~~options is 33152~~# First run the '''set_vnc.sh''' script settings,~~identity is sunxi-wdt~~and '''remember to add Sudo permissions'''

~~put_usr return,if 0,success~~:0:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo set_vnc.sh'''

~~The old reset time is: 16~~You will require a password to access your desktops.

~~return ENOTTY,if -1,success:0~~

~~return ENOTTY~~Password:        '''#Set the VNC password here,if 8 -~~1,success:0~~bit characters'''

~~put_user return,if 0~~Verify:        '''#Set the VNC password here,~~success:0~~8 -bit characters'''

~~put_usr return,if 0,success~~Would you like to enter a view-only password (y/n)? '''n'''

~~keep alive~~xauth: file /root/.Xauthority does not exist

~~keep alive~~

~~keep alive~~New 'X' desktop is orangepi3b:1

~~~~

~~== Check the serial number of the RK3566 chip ==~~

~~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~~Creating default startup script /root/.vnc/xstartup

~~orangepi@orangepi:~$ '''cat_serial~~Starting applications specified in /root/.~~sh'''~~vnc/xstartup

~~Serial~~ Log file is /root/.vnc/orangepi3b: ~~'''8fa18eaf489041f0'''~~1.log

~~~~

~~== The method of downloading and installing the balenaEtcher version of arm64 ==~~

~~<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>~~Killing Xtightvnc process ID 3047

~~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;"><li>The download address of the Appimage version that does not need to be installed~~ New 'X' desktop is ~~shown below~~orangepi3b: ~~</li></ol>~~1

~~https://github.com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balenaEtcher-1.7.9+5945ab1f-arm64.AppImage~~

~~<div class="figure">~~Starting applications specified in /root/.vnc/xstartup

~~[[File~~Log file is /root/.vnc/orangepi3b:~~pi3b-img275~~1.~~png|527x211px~~log|~~IMG_256]]~~}

~~</div>~~

<li>~~How~~ The steps of using MobaxTerm software to ~~install and use~~ connect the ~~deb version of Balenaetcher~~development board Linux system desktop are shown below:

<li>~~deb version~~ First click Session, then select VNC, then fill in the IP address and port of ~~Balenaetcher installation commands as shown below:~~ the development board, and finally click OK to confirm</li~~></ol></li></ol~~>

~~orangepi@orangepi:~$ '''sudo apt install -y \'''~~<div class="figure">

~~'''~~[[File:pi3b-~~-fix-broken ./balena-etcher-electron_1.7.9+5945ab1f_arm64~~img324.~~deb'''~~png]]

</div></ol>

<li>~~After~~ Then enter the ~~deb version~~ password of ~~Balenaetcher is installed, it can be opened in~~ the ~~Application~~previously set VNC</li~~></ol~~>

~~<div class="figure">~~ [[File:pi3b-~~img89~~img325.png~~|507x249px|IMG_256~~]] </~~div~~ol>

<li>The interface after ~~Balenaetcher is opened~~ the login is shown as shown in the figure below: , and then the desktop of the Linux system can be remotely operated</~~li></ol~~p> <~~div class="figure"~~p> [[File:pi3b-~~img276~~img326.png~~|429x263px|IMG_256~~]] </~~div><ol start="3" style="list-style-type: decimal;"><li><~~p>~~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>

~~orangepi@orangepi:~/Desktop$ '''chmod +x balenaEtcher~~

~~<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>~~Some programming language tests supported by Linux system ==

~~[[File:pi3b~~=== Debian Bullseye system ===

<~~span id~~ol style="~~the~~list-~~installation-method~~style-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-thedevelopment board<ol style="list-~~bt-panel~~style-~~linux~~type: lower-~~panel~~alpha;"><li>The version of the gcc is shown below</~~span~~li>{| class="wikitable" style= ~~The installation method of the Bt~~"width:800px;" |-| orangepi@orangepi:~$ '''gcc --~~Panel Linux panel ==~~version'''

'''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 gcc (~~excerpted from the [https://www.bt~~Debian 10.~~cn/new/index~~2.~~html official website of the Bt~~1-~~Panel]~~6)~~'''~~10.2.1 20210110

~~# First of all~~Copyright (C) 2020 Free Software Foundation, ~~the size of the'''/tmp''' space is needed~~Inc. ~~After setting, you need to '''restart the Linux system of the development board''', and the command is shown below:~~

~~orangepi@orangepi:~$ '''sudo sed -i 's/nosuid/&amp~~This is free software;~~,size=2G/' /etc/fstab'''~~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>Write C language of '''Hello_world.c''' program</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~sudo reboot~~vim hello_world.c'''

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

~~<li>After restarting, you can see that the size of the'''/tmp''' space has become 2G.</li></ol>~~

~~orangepi@orangepi:~$ '''df -~~#include <stdio.h ~~| grep~~ &~~quot~~gt;</~~tmp"'''~~p>

~~tmpfs 2.0G 12K '''2.0G''' 1% /tmp~~int main(void)

~~<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></ol>~~{

~~orangepi@orangepi~~:~~~$ '''sudo install_bt_panel.sh'''~~printf("Hello World!\n");

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

~~+----------------------------------------------------------------------~~:return 0;

}| Bt}</ol><ol start="3" style="list-~~WebPanel FOR CentOS~~style-type: lower-alpha;"><li>Then compile and run '''hello_world.c'''</~~Ubuntu/Debian~~li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''

~~+----------------------------------------------------------------------~~orangepi@orangepi:~$ '''./hello_world'''

Hello World!| ~~Copyright © 2015~~}</ol></li></ol><ol start="2" style="list-~~2099 BT~~style-~~SOFT(http~~type:decimal;"><li>Debian BullSeye Default with Python3<ol style="list-style-type: lower-alpha;"><li>The specific version of Python is shown below</~~www.bt.cn) All rights reserved.~~li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3'''

~~+----------------------------------------------------------------------~~'''Python 3.9.2''' (default, Feb 28 2021, 17:03:44)

~~| The WebPanel URL will be http://SERVER_IP:8888 when installed~~[GCC 10.2.1 20210110] on linux

~~+----------------------------------------------------------------------~~Type "help", "copyright", "credits" or "license" for more information.

~~Do you want to install Bt~~>>>|}</ol><ol start="2" style="list-style-type: lower-~~Panel to the~~ alpha;"><li>'''hello_world.py''' program in Python language</~~www directory now?(y/n)~~li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi: ~$ '''yvim hello_world.py'''

print('Hello World!')|}</ol><ol start="53" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then you have to wait patiently~~The results of running '''hello_world. ~~When you see the printing information~~ py''' are shown 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>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3 hello_world.py'''

~~[[File:pi3b-img278.png~~Hello World!|~~576x233px]]~~}</ol></li></ol><ol start="63" style="list-style-type: decimal;"><li>~~At this time, enter the~~ Debian Bullseye'~~''panel address''' displayed above in the browser to open the login interface of the pagoda Linux panel,~~ s compilation tool and ~~then enter the '''username''' and '''password''' displayed~~ operating environment that is not installed in Java by default<ol style="list-style-type: lower-alpha;"><li>You can use the ~~corresponding position~~ following command to ~~log~~ install OpenJDK. The latest version in ~~to the Bt~~Debian Bullseye is openjdk-~~Panel~~17 ~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img279.png~~| orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''|~~575x281px]]~~}</pol><~~/li~~ol start="2" style="list-style-type: lower-alpha;"><li~~><p~~>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~~installation, ~~and then~~ you can ~~choose "I have agreed and read" User Agreement ", and then click" Enter the panel " You can enter~~ check the ~~Bt-Panel~~version of Java</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| ~~[[File~~orangepi@orangepi:~~pi3b~~~$ '''java -~~img280.png~~-version'''|~~575x317px]]~~}</ol><ol start="83" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~After entering the Bt-Panel, you will first prompt that you need to bind the account of~~ Edit the ~~Bt-Panel official website. If you do n’t have an account, you can go to the pagoda~~'~~s official website (~~''~~'https://www~~hello_world.~~bt.cn~~java'''~~) to register one.~~of the Jave version</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''

~~[[File:pi3b-img281.png|576x300px]]~~public class hello_world

~~<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</li></ol>{

:public static void main(String[~~[File:pi3b-img282.png|575x306px]~~]args)

~~<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</li></ol>~~{

~~Manual~~: ~~[http~~:~~//docs~~System.btout.~~cn '''http://docs.bt.cn''']~~println("Hello World!");

~~Forum address~~: ~~[https://www.bt.cn/bbs '''https://www.bt.cn/bbs''']~~}

~~GitHub Link~~}|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then compile and run '''hello_world.java''~~https~~'</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~~//github~~~$ '''javac hello_world.~~com/aaPanel/BaoTa~~java'''

~~== Set the Chinese environment and install Chinese input method ==~~orangepi@orangepi:~$ '''java hello_world'''

~~'''Note that before installing the Chinese input method, please make sure that the Linux~~ Hello World!|}</ol></li></ol>

~~~~=== ~~Debian~~ Ubuntu Focal system ~~installation method~~ ===

<li>~~First set~~ Ubuntu Focal has the GCC compilation tool chain by default ~~'''locale''' as Chinese~~, which can compile the C language program directly in the Linux system of the development board.

<li>~~Enter~~ The version of the ~~command~~ gcc is shown below ~~to start configured~~ </li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~locale~~gcc --version'''~~</li></ol></li></ol>~~

~~orangepi@orangepi:~~gcc (Ubuntu 9.4.0-1ubuntu1~~~$ '''sudo dpkg-reconfigure locales'''~~20.04.1) 9.4.0

~~<ol start="2" style="list-style-type: lower-alpha;"><li>Then select '''zh_CN.UTF-8 UTF-8''' in the pop-up interface~~ Copyright (~~to move up and down through the upper and lower direction buttons on the keyboard~~C) 2019 Free Software Foundation, ~~select it through the space key, and finally move the cursor to '''<OK>''' through the TAB key, then press the ENTER key )</li></ol>~~Inc.

~~[[File:pi3b-img283~~This is free software; see the source for copying conditions.~~png|575x296px]]~~There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</ol><ol start="32" style="list-style-type: lower-alpha;"><li>~~Then set the default~~ '''~~locale~~hello_world.c''' as program to write C language</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~zh_CN~~vim hello_world.~~UTF-8~~c'''~~</li></ol>~~

~~[[File:pi3b-img284~~#include <stdio.~~png|575x160px]]~~h>

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

~~<li>After exiting the interface, the '''locale''' settings will be started. The output displayed by the command line is shown below</li></ol>~~

~~orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''~~int main(void)

~~Generating locales (this might take a while)...~~{

~~en_US.UTF-8... done~~:printf("Hello World!\n");

~~zh_CN.UTF-8... done~~

~~Generation complete.~~:return 0;

}|}</ol><ol start="23" style="list-style-type: ~~decimal~~lower-alpha;"><li>Then ~~open~~ compile and run '''~~Input Method~~hello_world.c'''</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''

~~[[File~~orangepi@orangepi:~~pi3b-img285~~~$ '''.~~png|575x361px]]~~/hello_world'''

Hello World!|}</ol></li></ol><ol start="32" style="list-style-type: decimal;"><li>~~Then select '''OK'''~~Ubuntu Focal defaults to install Python3<ol style="list-style-type: lower-alpha;"><li>Python3 specific version is shown below</olli>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3'''

~~[[File~~Python 3.8.10 (default, Nov 14 2022, 12:59:~~pi3b-img286.png|295x212px]]~~47)

~~<ol start="~~[GCC 9.4~~" style="list-style-type: decimal;"><li>Then select '''Yes'''</li></ol>~~.0] on linux

~~[[File:pi3b-img287~~Type "help", "copyright", "credits" or "license" for more information.~~png|303x192px]]~~

>>>|}</ol><ol start="52" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then select~~ '''~~fcitx~~hello_world.py'''program in Python language</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.py'''

~~[[File:pi3b-img288.png~~print('Hello World!')|~~307x220px]]~~}</ol><ol start="63" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then select~~ The results of running '''OKhello_world.py'''are shown below</li>~~</ol>~~{| class="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>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 '''openjdk-17'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''|}</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:~~pi3b~~800px;" |-~~img289.png~~|~~305x216px]]~~orangepi@orangepi:~$ '''java --version'''

~~<ol start="7" style="list~~openjdk 17.0.2 2022-~~style~~01-~~type: decimal;"><li>'''Then restart the Linux system to make the configuration effective'''</li><li>Then open '''Fcitx configuration'''</li></ol>~~18

~~[[File:pi3b~~OpenJDK Runtime Environment (build 17.0.2+8-Ubuntu-~~img290~~120.~~png|575x376px]]~~04)

OpenJDK 64-Bit Server VM (build 17.0.2+8-Ubuntu-120.04, mixed mode, sharing)|}</ol><ol start="93" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then click~~ Edit the + '''hello_world.java''' of ~~the position shown in the figure below~~Jave version</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''

~~[[File:pi3b-img291.png|280x187px]]~~public class hello_world

~~<ol start="10" style="list-style-type: decimal;"><li>Then search '''Google Pinyin''' and click '''OK'''</li></ol>~~{

~~<div class="figure">~~:public static void main(String[] args)

~~[[File~~:~~pi3b-img292.png|291x196px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-10.jpg未标题-10]]~~{

~~</div><ol start="11" style="list-style-type~~: ~~decimal~~:System.out.println("Hello World!");">~~<li>Then put '''Google Pinyin''' to the front</li></ol>~~

~~[[File~~:~~pi3b-img293.png|299x202px]]~~}

~~[[File~~}|}</ol><ol start="4" style="list-style-type:~~pi3b~~lower-~~img294~~alpha;"><li>Then compile and run '''hello_world.~~png~~java'''</li>{|~~300x202px]]~~class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''javac hello_world.java'''

~~<ol start="12" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>Then open the~~ ~$ '''~~Geany~~java hello_world''' ~~editor to test the Chinese input method</li></ol>~~

~~[[File:pi3b-img295.png~~Hello World!|~~349x212px]]~~}</ol ~~start="13" style="list-style-type: decimal;"~~></li>~~The Chinese input method test is shown below~~</liol></olspan>

~~[[File:pi3b-img296.png|575x325px]]~~=== Ubuntu jammy system ===

<ol ~~start="14"~~ style="list-style-type: decimal;"><li>~~You~~ Ubuntu Jammy is installed with the GCC compilation tool chain by default, which can ~~switch~~ directly compile the ~~Chinese and English input method through~~ C language program in the Linux system of the ~~'''Ctrl+Space''' shortcut~~development board<~~/li~~ol style="list-style-type: lower-alpha;"><li>~~If~~ The version of the ~~entire system~~ gcc is ~~required as Chinese, the variables in '''~~shown below</~~etc/default/locale~~li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ ''' ~~can be set to '''zh_CN.UTF~~gcc --8version'''~~</li></ol>~~

~~orangepi@orangepi:~$~~ gcc (Ubuntu 11.2.0-19ubuntu1) '''~~sudo vim /etc/default/locale~~11.2.0'''

~~LC_MESSAGES='''zh_CN~~This is free software; see the source for copying conditions.~~UTF-8'''~~There is NO

~~LANG~~warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Write the '''~~zh_CN~~hello_world.~~UTF~~c''' program of c language</li>{| class="wikitable" style="width:800px;" |-8| orangepi@orangepi:~$ '''vim hello_world.c'''

~~LANGUAGE='''zh_CN~~#include <stdio.~~UTF-8'''~~h>

~~<ol start="16" style="list-style-type: decimal;">~~

~~<li>Then '''restart the system''' to see the system displayed as Chinese</li></ol>~~

~~[[File:pi3b-img297.png|576x356px]]~~int main(void)

~~=== The installation method of Ubuntu 20.04 system ===~~{

~~# First open '''Language Support'''~~:printf("Hello World!\n");

~~[[File:pi3b-img298.png|575x351px]]~~

~~<ol start="2" style="list-style-type~~: ~~decimal~~return 0;">~~<li>Then find '''Chinese (China)''' option</li></ol>~~

~~[[File~~}|}</ol><ol start="3" style="list-style-type:~~pi3b~~lower-~~img299~~alpha;"><li>Then compile and run '''hello_world.~~png~~c'''</li>{| class="wikitable" style="width:800px;" |-|~~318x311px]]~~orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''

~~<ol start="3" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>Then use the left mouse button to select~~ ~$ '''~~Chinese (China)~~./hello_world''' ~~and hold it down, and then drag it up to the beginning. The display is shown below: </li></ol>~~

~~[[File:pi3b-img300.png~~Hello World!|~~324x320px]]~~}</ol></li></ol>

<ol start="2" style="list-style-type: decimal;"><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:~$ '''~~Note that this step is not easy to drag, please try more patiently.~~python3'''

~~<ol start="4" style="list-style-type: decimal;"><li>Then select the~~ Python '''~~Apply System-Wide~~3.10.4''' ~~to apply the Chinese settings to the entire system</li></ol>~~(main, Apr 2 2022, 09:04:19) [GCC 11.2.0] on linux

~~[[File:pi3b-img301~~Type "help", "copyright", "credits" or "license" for more information.~~png|321x316px]]~~

>>>|}</ol><ol start="52" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then set the~~ Edit '''~~Keyboard input method system~~hello_world.py''' to program in Python language</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~fcitx~~vim hello_world.py'''~~</li></ol>~~

~~[[File~~print('Hello World!')|}</ol><ol start="3" style="list-style-type:~~pi3b~~lower-~~img302~~alpha;"><li>The results of running '''hello_world.~~png~~py''' are shown below</li>{|~~327x320px]]~~class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3 hello_world.py'''

Hello World!|}</ol></li></ol><ol start="63" style="list-style-type: decimal;"><li>~~'''hen restart the Linux system~~ Ubuntu jammy defaults to ~~make the configuration effective'''~~compile tools and operating environments that are not installed in Java<~~/li~~ol style="list-style-type: lower-alpha;"><li>You can use the following command to install openjdk-18<p/li>~~After re~~ {| class="wikitable" style="width:800px;" |-~~entering the system, please do~~ | orangepi@orangepi:~$ '''~~not ask me again~~sudo apt install -y openjdk-18-jdk''' ~~at the interface below, and then determine whether the standard folder should be updated as Chinese based on your preference.~~|}</pol><ol start="2" style="list-style-type: lower-alpha;"></li>After installation, you can check the version of Java</olli>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''java --version'''

~~[[File:pi3b~~openjdk 18-~~img303.png|303x247px]]~~ea 2022-03-22

~~<ol start="8" style="list~~OpenJDK Runtime Environment (build 18-~~style~~ea+36-~~type: decimal;"><li>Then you can see that the desktop is displayed as Chinese</li></ol>~~Ubuntu-1)

~~[[File~~OpenJDK 64-Bit Server VM (build 18-ea+36-Ubuntu-1, mixed mode, sharing)|}</ol><ol start="3" style="list-style-type:~~pi3b~~lower-~~img304~~alpha;"><li>Edit the '''hello_world.~~png~~java''' of the Jave version</li>{|~~575x383px]]~~class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''

~~<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 figure below</li></ol>~~public class hello_world

~~[[File:pi3b-img305.png|576x292px]]~~{

~~<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></ol>~~public static void main(String[] args)

~~[[File~~:~~pi3b-img306.png|575x308px]]~~{

~~=== The installation method of ubuntu 22~~out.~~04 system ===~~println("Hello World!");

~~# First open '''Language Support'''~~:}

~~[[File~~}|}</ol><ol start="4" style="list-style-type:~~pi3b~~lower-~~img298~~alpha;"><li>Then compile and run '''hello_world.~~png~~java'''</li>{|~~575x351px]]~~class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''javac hello_world.java'''

~~<ol start="2" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>Then find~~ ~$ '''~~Chinese (China)~~java hello_world''' ~~option</li></ol>~~

~~[[File:pi3b~~Hello World!|}</ol></li></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 after dragging is shown in the figure below: </li></ol>~~QT installation method ==

~~[[File:pi3b-img308.png|337x331px]]~~# Use the following script to install QT5 and QT Creator

::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~Note that this step is not easy to drag, please try more patiently~~install_qt.sh'''|}

<ol start="42" style="list-style-type: decimal;"><li>~~Then select the~~ The QT version number will be automatically printed after installation<ol style="list-style-type: lower-alpha;"><li>Ubuntu20.04 comes with QT version '''~~Apply System-Wide~~5.12.8''' ~~to apply the Chinese settings to the entire system~~</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_qt.sh'''

~~[[File:pi3b-img309~~.~~png|336x330px]]~~.....

~~<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>QMake version 3.1

~~[[File~~Using Qt version '''5.12.8''' in /usr/lib/aarch64-linux-gnu|}</ol><ol start="2" style="list-style-type: lower-~~img303~~alpha;"><li>Ubuntu22.04 comes with QT version '''5.15.~~png~~3'''</li>{| class="wikitable" style="width:800px;" |-|~~303x247px]]~~orangepi@orangepi:~$ '''install_qt.sh'''

~~<ol start="7" style="list-style-type: decimal;"><li>Then you can see that the desktop is displayed as Chinese</li></ol>~~......

~~[[File:pi3b-img304~~QMake version 3.~~png|575x383px]]~~1

Using Qt version '''5.15.3''' in /usr/lib/aarch64-linux-gnu|}</ol><ol start="83" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then open the Fcitx5 configuration program~~Debian11 comes with QT version '''5.15.2'''</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_qt.sh'''

~~[[File:pi3b-img310~~.~~png|575x349px]]~~.....

~~<ol start="9" style="list-style-type: decimal;"><li>Then choose to use Pinyin input method</li></ol>~~QMake version 3.1

Using Qt version '''<~~div~~ span style="color:#FF0000">5.15.2''' in /usr/lib/aarch64-linux-gnu|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Debian12 comes with QT version '''5.15.8'''</li>{| class="~~figure~~wikitable" style="width:800px;">|-| orangepi@orangepi:~$ '''install_qt.sh'''

~~[[File:pi3b-img311~~.~~png|338x267px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-11~~.~~jpg未标题-11]]~~....

~~</div><ol start="10" style="list-style-type: decimal;"><li>The interface after the selection is shown below, then click OK</li></ol>~~QMake version 3.1

~~[[File~~Using Qt version '''5.15.8''' in /usr/lib/aarch64-linux-~~img312.png~~gnu|~~366x290px]]~~}</ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>Then you can see the QT Creator launch icon in '''Applications'''</li>

~~<ol start="11" style="list~~[[File:pi3b-~~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>~~img327.png]]

~~[[File~~QT Creator can also be opened using the following command{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''qtcreator'''|}{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-~~img305~~| <big>'''During the startup of QT and QT applications, if the following error is displayed, ignore it.~~png|576x292px]]~~This error has no impact on application running.'''

~~<ol start="12" style="list-style-type: 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''' shortcut keys, and then we can enter Chinese</li></ol>

~~[[File~~'''libGL error:~~pi3b-img313.png|576x408px]]~~failed to create dri screen'''

~~== How to remotely log in to the Linux system desktop method ==~~load driver: rockchip'''

'''~~Ubuntu Gnome Wayland image does not support Nomachine and VNCs introduced here~~ libGL error: failed to ~~remotely log in to the desktop.~~create dri screen'''

'''libGL error: failed to load driver: rockchip'''<~~span id~~/big>|}</ol><ol start="~~use~~4" style="list-~~nomachine~~style-~~remote-login~~type: decimal;"><li>The interface after QT Creator is opened is as follows</~~span~~li>~~=== Use nomachine remote login ===~~

~~'''Make sure the Ubuntu or Debian system installed on the development board is a desktop~~ [[File:pi3b-img328.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>The QT Creator 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<ol style="list-style-type: lower-alpha;"><li>The default version of QT Creator in '''Ubuntu20.04''' is as follows</li>

[[File:pi3b-img329.png]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The default version of QT Creator in '''~~https://knowledgebase~~Ubuntu22.~~nomachine.com/DT10R00166~~04'''is as follows</li>

~~'''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~~[[File:pi3b-img330. png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The ~~following demonstrates the Linux system desktop~~ default version of ~~the Orange PI development board through Nomachine~~ QT Creator in ~~Windows. For installation methods for other platforms, please refer to the official documentation of Nomachine.~~'''Debian11''' is as follows</li>

[[File:pi3b-img331.png]]</ol><ol start="4" style="list-style-type: lower-alpha;"><li>The default version of QT Creator in '''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.Debian12'''is as follows</li>

[[File:pi3b-img332.png]]</ol ></li></ol><ol start="6" style="list-style-type: decimal;"><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~~Then set QT

<li>~~Since RK3566 is a SOC of the ARMV8 architecture, the system we use is Ubuntu or Debian, so you need to download~~ First open '''~~NoMachine for ARM ARMv8 DEB~~Help''' ~~installation package here~~->'''About Plugins... ~~The download link is shown below:~~ '''</li~~></ol></li></ol~~>

[[File:pi3b-img333.png]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then remove the check box for '''~~Note that this download link may change, please recognize the DEB package of the ARMV8/ARM64 version.~~ClangCodeModel'''</li>

[~~https~~[File:~~//www~~pi3b-img334.~~nomachine.com~~png]]</~~download/download&id~~ol><ol start=~~112&s~~"3" style=~~ARM~~ "list-style-type: lower-alpha;"><li>'''~~https~~Restart QT Creator after the Settings are complete'''</~~downloads.nomachine.com~~li><li>Then make sure that QT Creator uses the GCC compiler, if the default is Clang, change it to GCC</~~download~~p></~~?id~~li>{| class="wikitable" style=~~118&amp~~"background-color:#ffffdc;~~distro=ARM~~width:800px;" |-| <big>'''Debian12 Please skip this step.''']</big>|}

[[File:pi3b-~~img314~~img335.png~~|575x227px~~]]

[[File:pi3b-img336.png]]</ol></li></ol><ol start="27" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~In addition, you~~ You can ~~also download the installation package to '''NoMachine''' in the '''official tools'''.~~then open a sample code</li~~></ol~~>

[[File:pi3b-~~img315~~img337.png~~|66x102px~~]]</ol><ol start="8" style="list-style-type: decimal;"><li>Clicking on the example code will automatically open the corresponding instruction document, you can carefully read the instructions</li>

[[File:pi3b-img338.png]]</ol><ol start="9" style="list-style-type: decimal;"><~~blockquote~~li>~~First enter the~~ Then click '''~~remote login software-Nomachine~~Configure Project''' ~~folder~~</~~blockquote~~li>~~[[File:pi3b-img316.png|271x43px]]~~

~~<blockquote>Then download the ARM64 version of the DEB installation package</blockquote>~~[[File:pi3b-~~img317~~img339.png~~|180x109px~~]]</ol><ol start="10" style="list-style-type: decimal;"><li>Then click the green triangle in the lower left corner to compile and run the sample code</li>

[[File:pi3b-img340.png]]</ol><ol start="311" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then upload the downloaded '''nomachine_x.x.x_x_arm64.deb''' to the Linux system~~ After waiting for a period of time, the ~~development board.</li><li>Then use~~ interface shown in the following ~~command to install '''NoMachine''' in the Linux system of the development board~~figure will pop up, which indicates that QT can compile and run normally</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img341.png]]</ol><ol start="12" style="list-style-type: decimal;"><li>Reference documents</li>{| class="wikitable" style="width:800px;" |-| '''~~sudo dpkg -i nomachine_x.x~~https://wiki.~~x_x_arm64_arm64~~qt.~~deb~~io/Install_Qt_5_on_Ubuntu'''

~~<ol start="2" style="list-style-type~~'''https: ~~decimal;"><li>Then download the nomachine software Windows version of the installation package, the~~ //download ~~address is shown below<~~.qt.io/~~li><~~archive/~~ol>~~qtcreator'''

'''~~Note that this~~ https://download ~~link may change~~.qt.io/archive/qt'''|}</ol>

~~'''https://downloads.nomachine.com/download/?id~~=~~9'''~~= ROS Installation Method ==

~~[[File:pi3b~~=== How to install ROS 1 Noetic on Ubuntu 20.~~png|575x163px]]~~04 ===

~~<ol start="3" style="list-style-type: decimal;"><li>Then install nomachine in Windows. '''Please restart~~ # The current active version of ROS 1 is as follows, the ~~computer after installation'''</li><li>Then open~~ recommended version is '''~~NoMachine~~Noetic Ninjemys''' ~~in Window</li></ol>~~

::[[File:pi3b-~~img319~~img342.png|~~76x66px~~800px]]

~~<ol start="5" style="list-style~~::[[File:pi3b-~~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 belowimg343. ~~Start log in to the Linux system desktop of the development board</li></ol>~~png|800px]]

::{| class="wikitable" style="width:800px;" |-| [~~[File~~http://docs.ros.org/ '''http:~~pi3b-img320~~//docs.ros.~~png|321x92px]~~org''']

~~<ol start="6" style="list-style-type: decimal;"><li>Then click~~ '''OKhttps://wiki.ros.org/Distributions'''~~</li></ol>~~|}

~~[[File:pi3b-img321.png|402x275px]]~~ <ol start="72" style="list-style-type: decimal;"><li>~~Then enter the username and password~~ The official installation document link of ~~the Linux system in the corresponding position in the figure below, and then click~~ ROS 1 '''OKNoetic Ninjemys''' ~~to start logging in~~is as follows:</li~~></ol~~> ~~<div~~ {| class="~~figure~~wikitable" style="width:800px;">|-| [~~[File~~http:~~pi3b-img322~~//wiki.ros.~~png|303x204px|C~~org/noetic/Installation/Ubuntu '''http:~~\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-12~~//wiki.ros.~~jpg未标题-12]~~org/noetic/Installation/Ubuntu''']|}</~~div~~ol><ol start="83" style="list-style-type: decimal;"><li>~~Then click OK in~~ In the ~~next interface</li><li>Finally~~official installation document of ROS '''Noetic Ninjemys''', Ubuntu recommends using Ubuntu20.04, ~~you can see~~ so please make sure that the ~~desktop of~~ system used by the development board ~~Linux~~ is '''Ubuntu20.04 desktop system</pspan>'''<p/li>~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img323.png~~|~~411x246px]]<~~http://~~p><~~wiki.ros.org/~~li><~~noetic/~~ol>~~Installation|}

[[File:pi3b-img344.png]]<~~span id~~/ol><ol start="4" style="~~use~~list-~~vnc~~style-~~remote-login~~type: decimal;"><li>Then use the script below to install ros1</~~span~~li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi3b:~$ '''install_ros.sh ros1'''|}</ol><ol start= ~~Use VNC remote login~~ "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;" |-| <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.'''

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

'''~~Ubuntu 20~~The install_ros.~~04 tests many problems with VNC~~sh script will try to modify /etc/hosts and automatically run the following commands. However, ~~please do not use~~ this methodcannot 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 Order.'''

~~# First run the '''set_vnc.sh''' script settings, and '''remember to add Sudo permissions'''~~

~~orangepi@orangepi:~$~~ '''~~sudo set_vnc~~https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.shyaml'''

~~You will require a password to access your desktops~~'''Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml'''

~~Password:~~ '''~~#Set the VNC password here, 8 -bit characters~~ERROR: error loading sources list:'''

~~Verify~~: '''~~#Set the VNC password here, 8~~ The read operation timed out'''</big>|}{| class="wikitable" style="width:800px;" |-~~bit characters~~| orangepi@orangepi:~$ '''source /opt/ros/noetic/setup.bash'''

~~Would you like to enter a view-only password (y/n)?~~ orangepi@orangepi:~$ '''nsudo rosdep init'''

~~xauth: file~~ Wrote /~~root~~etc/ros/rosdep/sources.list.d/20-default.~~Xauthority does not exist~~list

~~New 'X' desktop is orangepi3b~~Recommended:1please run

~~Creating default startup script /root/.vnc/xstartup~~

~~Starting applications specified in /root/.vnc/xstartup~~::rosdep update

~~Log file is /root/.vnc/orangepi3b~~orangepi@orangepi:~~1.log~~~$ '''rosdep update'''

~~Killing Xtightvnc process ID 3047~~reading in sources list data from /etc/ros/rosdep/sources.list.d

~~New 'X' desktop is orangepi3b~~Hit https:1//raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml

~~Starting applications specified in~~ Hit https:/~~root~~/raw.~~vnc~~githubusercontent.com/ros/rosdistro/master/~~xstartup~~rosdep/base.yaml

~~Log file is~~ Hit https:/~~root~~/raw.githubusercontent.~~vnc~~com/ros/~~orangepi3b:1~~rosdistro/master/rosdep/python.~~log~~yaml

~~<ol start="2" style="list-style-type~~Hit https: ~~decimal;"><li>The steps of using MobaxTerm software to connect the development board Linux system desktop are shown below: <~~/p>~~<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><~~raw.githubusercontent.com/ros/rosdistro/~~ol>~~<master/~~li><~~rosdep/~~ol>~~ruby.yaml

~~<div class="figure">~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml

~~[[File~~Query rosdistro index https:~~pi3b~~//raw.githubusercontent.com/ros/rosdistro/master/index-~~img324~~v4.~~png|490x349px|图片1208]]~~yaml

~~</div><ol start="2" style="list~~Skip end-~~style~~of-~~type: lower-alpha~~life distro "ardent"">~~<li>Then enter the password of the previously set VNC</li></ol>~~

~~[[File:pi3b~~Skip end-~~img325.png|274x131px]]~~of-life distro "bouncy"

~~<ol start="3" style="list~~Skip end-~~style~~of-~~type: lower-alpha~~life distro "crystal"">~~<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>~~

~~== Some programming language tests supported by Linux system ==~~life distro "dashing"

~~=== Debian Bullseye system ===~~life distro "eloquent"

~~<ol style="list-style-type: decimal~~Add distro "">~~<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~~foxy"">~~<li>The version of the gcc is shown below</li></ol></li></ol>~~

~~orangepi@orangepi:~$ '''gcc --version'''~~Add distro "galactic"

~~gcc (Debian 10.2.1~~Skip end-~~6) 10.2.1 20210110~~of-life distro "groovy"

~~This is free software~~Skip end-of-life distro "hydro" ~~see the source for copying conditions. There is NO~~

~~warranty~~Skip end-of-life distro "indigo" ~~not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.~~

~~<ol start="2" style="list~~Skip end-~~style~~of-~~type: lower-alpha~~life distro "jade"">~~<li>Write C language of '''Hello_world.c''' program</li></ol>~~

~~orangepi@orangepi:~$ '''vim hello_world.c'''~~Skip end-of-life distro "kinetic"

~~#include~~ Skip end-of-life distro &ltquot;~~stdio.h~~lunar&gtquot;

~~int main(void)~~Add distro "melodic"

{Add distro "noetic"

~~printf(~~Add distro "~~Hello World!\n~~rolling");

~~return 0~~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:~$ '''test_ros.sh'''|}<li>After running the '''test_ros.sh''' script, a little turtle as shown in the figure below will pop up</li>

}<div class="figure">

[[File:pi3b-img345.png]] </div></ol><ol start="38" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~compile and run '''hello_world.c'''~~please keep the terminal window just opened at the top</li~~></ol~~>

~~orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''~~<div class="figure">

~~orangepi@orangepi~~[[File:~~~$ '''~~pi3b-img346.~~/hello_world'''~~png]]

~~Hello World!~~</div></ol><ol start="9" style="list-style-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 start="2" style="list~~[[File:pi3b-~~style-type: decimal;">~~img347.png]]~~<li>Debian BullSeye Default with Python3~~</pol><~~ol style~~span id="~~list~~how-~~style~~to-~~type: lower~~install-ros-2-galactic-on-ubuntu-~~alpha;~~20.04">~~<li>The specific version of Python is shown below</li></ol>~~</~~li></ol~~span>

~~orangepi@orangepi:~$ '''python3'''~~=== How to install ROS 2 Galactic on Ubuntu 20.04 ===

# The current active version of ROS 2 is as follows, the recommended version is '''~~Python 3.9.2~~Galactic Geochelone''' ~~(default, Feb 28 2021, 17:03:44)~~

::[~~GCC 10~~[File:pi3b-img348.~~2.1 20210110~~png]] ~~on linux~~

~~Type "help", "copyright", "credits" or "license" for more information~~::[[File:pi3b-img349.png]]

~~>>&gt~~::{| class="wikitable" style="width:800px;" |-| [http://docs.ros.org/ '''http://docs.ros.org''']

~~<ol start="2" style="list-style-type: lower-alpha;"><li>~~'''~~hello_world~~http://docs.pyros.org/en/galactic/Releases.html''' ~~program in Python language</li></ol>~~|}

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~$ decimal;"><li>The link to the official ROS 2 '''~~vim hello_world~~Galactic Geochelone''' installation documentation is as follows:</li>{| class="wikitable" style="width:800px;" |-| '''docs.ros.org/en/galactic/Installation.pyhtml'''

~~print(~~'~~Hello World!~~')'http://docs.ros.org/en/galactic/Installation/Ubuntu-Install-Debians.html'''|}</ol><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 the '''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. ...

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

~~<li>The results of running '''hello_world.py''' are shown below</li></ol>~~

~~orangepi@orangepi:~$ '''python3 hello_world~~ros2 is an extensible command-line tool for ROS 2.~~py'''~~

~~Hello World!~~

~~<ol start="3" style="list-style-type~~optional arguments: ~~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~~:~~~$ '''sudo apt install~~ -~~y openjdk~~h, -17-~~jdk'''~~help show this help message and exit

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

~~<li>After installation, you can check the version of Java</li></ol>~~

~~orangepi@orangepi~~Commands:~~~$ '''java --version'''~~

~~<ol start="3" style="list-style-type~~: ~~lower~~action Various action related sub-~~alpha;"><li>Edit the '''hello_world.java''' of the Jave version</li></ol>~~commands

~~orangepi@orangepi~~:~~~$ '''vim hello_world.java'''~~bag Various rosbag related sub-commands

~~public class hello_world~~:component Various component related sub-commands

{:daemon Various daemon related sub-commands

~~public static void main(String[] args)~~:doctor Check ROS setup and other potential issues

{:interface Show information about ROS interfaces

~~System.out.println("Hello World!");~~:launch Run a launch file

}:lifecycle Various lifecycle related sub-commands

}:multicast Various multicast related sub-commands

~~<ol start="4" style="list-style-type~~: ~~lower~~node Various node related sub-~~alpha;"><li>Then compile and run '''hello_world.java'''</li></ol>~~commands

~~orangepi@orangepi~~:~~~$ '''javac hello_world.java'''~~param Various param related sub-commands

~~orangepi@orangepi~~:~~~$ '''java hello_world'''~~pkg Various package related sub-commands

~~Hello World!~~:run Run a package specific executable

~~=== Ubuntu Focal system ===~~commands

~~<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~~service Various service related sub-~~alpha;"><li>The version of the gcc is shown below</li></ol></li></ol>~~commands

~~orangepi@orangepi~~:~~~$ '''gcc~~ topic Various topic related sub-~~-version'''~~commands

~~gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0~~:wtf Use `wtf` as alias to `doctor`

~~This~~ :Call `ros2 <command> -h` for more detailed usage.|}</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 ~~free software;~~ installed successfully. If you can see the ~~source for copying conditions~~following print, it means that ROS 2 can run normally</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi3b:~$ '''test_ros. ~~There is NO~~sh'''

~~warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE~~[INFO] [1671174101.200091527] [talker]: Publishing: 'Hello World: 1'

~~<ol start="2" style="list-style-type~~[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: ~~lower-alpha;"><li>'''hello_world.c''' program to write C language</li></ol>~~1]

~~orangepi@orangepi~~[INFO] [1671174102.199572327] [talker]: Publishing:~~~$ '''vim hello_world.c'~~'Hello World: 2'

~~#include <stdio~~[INFO] [1671174102.~~h>~~204196299] [listener]: I heard: [Hello World: 2]

~~int main(void)~~[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:~$ '''source /opt/ros/galactic/setup.bash'''

~~printf("Hello World!\n");~~orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''|}

~~return 0;~~<div class="figure">

}[[File:pi3b-img350.png]]

</div></ol><ol start="38" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then compile and run~~ For the usage of ROS, please refer to the documentation of ROS 2</li>{| class="wikitable" style="width:800px;" |-| '''~~hello_world~~http://docs.ros.org/en/galactic/Tutorials.chtml'''|}</liol></olspan>

~~orangepi@orangepi:~$ '''gcc -o hello_world hello_world~~=== How to install ROS 2 Humble on Ubuntu 22.~~c'''~~04 ===

~~orangepi@orangepi:~$~~ # Use the '''install_ros.~~/hello_world~~sh'''script to install ros2

~~Hello World!~~::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_ros.sh ros2'''|}

<li>~~Ubuntu Focal defaults to install Python3<ol style="list-style-type: lower~~The '''install_ros.sh''' script will automatically run the '''ros2 -~~alpha;"><li>Python3 specific version~~ h''' command after installing ros2. If you can see the following print, it means that the ros2 installation is ~~shown below~~complete</li~~></ol></li></ol~~>

~~orangepi@orangepi~~{| class="wikitable" style="width:~~~$ '''python3'''~~800px;" |-| usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...

~~Python 3.8.10 (default, Nov 14 2022, 12:59:47)~~

~~[GCC 9~~ros2 is an extensible command-line tool for ROS 2.~~4.0] on linux~~

~~Type "help", "copyright", "credits" or "license" for more information.~~

~~>>>~~optional arguments:

~~<ol start="2" style="list~~:-~~style~~h, -~~type: lower~~-~~alpha;"><li>'''hello_world.py''' program in Python language</li></ol>~~help show this help message and exit

~~orangepi@orangepi:~$ '''vim hello_world.py'''~~

~~print('Hello World!')~~Commands:

~~<ol start="3" style="list-style-type~~: ~~lower~~action Various action related sub-~~alpha;"><li>The results of running '''hello_world.py''' are shown below</li></ol>~~commands

~~orangepi@orangepi~~:~~~$ '''python3 hello_world.py'''~~bag Various rosbag related sub-commands

~~Hello World!~~:component Various component related sub-commands

~~<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 '''openjdk~~daemon Various daemon related sub-~~17'''</li></ol></li></ol>~~commands

~~orangepi@orangepi~~:~~~$ '''sudo apt install -y openjdk-17-jdk'''~~doctor Check ROS setup and other potential issues

~~<ol start="2" style="list-style-type~~: ~~lower-alpha;"><li>After installation, you can check the version of Java</li></ol>~~interface Show information about ROS interfaces

~~orangepi@orangepi~~:~~~$ '''java --version'''~~launch Run a launch file

~~openjdk 17.0.2 2022~~:lifecycle Various lifecycle related sub-~~01-18~~commands

~~OpenJDK Runtime Environment (build 17.0.2+8~~:multicast Various multicast related sub-~~Ubuntu-120.04)~~commands

~~OpenJDK 64~~:node Various node related sub-~~Bit Server VM (build 17.0.2+8-Ubuntu-120.04, mixed mode, sharing)~~commands

~~<ol start="3" style="list-style-type~~: ~~lower~~param Various param related sub-~~alpha;"><li>Edit the '''hello_world.java''' of Jave version</li></ol>~~commands

~~orangepi@orangepi~~:~~~$ '''vim hello_world.java'''~~pkg Various package related sub-commands

~~public class hello_world~~:run Run a package specific executable

{:security Various security related sub-commands

~~public static void main(String[] args)~~:service Various service related sub-commands

{:topic Various topic related sub-commands

~~System.out.println("Hello World!");~~:wtf Use `wtf` as alias to `doctor`

}

:Call `ros2 <command> -h` for more detailed usage.|}</ol><ol start="3" 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>

~~<ol start~~{| class="4wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Then compile and run~~ |-| orangepi@orangepi3b:~$ '''~~hello_world~~test_ros.~~java~~sh'''~~</li></ol>~~

~~orangepi@orangepi~~[INFO] [1671174101.200091527] [talker]: Publishing:~~~$ '''javac hello_world.java'~~'Hello World: 1'

~~orangepi@orangepi~~[INFO] [1671174101.235661048] [listener]:~~~$ '''java hello_world'''~~I heard: [Hello World: 1]

[INFO] [1671174102.199572327] [talker]: Publishing: 'Hello World!: 2'

~~=== Ubuntu jammy system ===~~[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]

~~<ol style="list-style-type~~[INFO] [1671174103.199580322] [talker]: ~~decimal;"><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~~Publishing: ~~lower-alpha;"><li>The version of the gcc is shown below</li></ol></li></ol>~~'Hello World: 3'

[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:~$ '''~~gcc --version~~source /opt/ros/humble/setup.bash'''

~~gcc (Ubuntu 11.2.0-19ubuntu1)~~ orangepi@orangepi:~$ '''~~11.2.0~~ros2 run rviz2 rviz2'''|}

~~This is free software; see the source for copying conditions~~[[File:pi3b-img351. ~~There is NO~~png]]

~~warranty~~</div></ol><ol start="5" style="list-style-type: decimal; ~~not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE~~"><li>Reference documents</li>{| class="wikitable" style="width:800px;" |-| '''http://docs.ros.org/en/humble/index.html'''

~~<ol start="2" style="list-style-type~~[http: ~~lower-alpha;"><li>Write the~~ //docs.ros.org/en/galactic/Tutorials.html '''~~hello_world~~http://docs.ros.org/en/humble/Installation/Ubuntu-Install-Debians.chtml''' ~~program of c language~~]|}</liol></olspan>

~~orangepi@orangepi:~$ '''vim hello_world.c'''~~== How to install kernel header files ==

#~~include <stdio.h>~~The Linux image released by OPi comes with the deb package of the kernel header file by default, and the storage location is '''/opt/'''

~~int main(void)~~::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ls /opt/linux-headers*'''

{/opt/linux-headers-legacy-rockchip-rk356x_x.x.x_arm64.deb|}

~~printf(&quot~~<ol start="2" style="list-style-type: decimal;~~Hello World!\n&quot~~"><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:~$ '''sudo dpkg -i /opt/linux-headers-legacy-rockchip-rk356x_1.x.x_arm64.deb'''|}</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;" |-| orangepi@orangepi:~$ '''ls /usr/src'''

~~return 0~~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, as follows:</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello.c'''

}#include <linux/init.h>

<~~ol start="3" style="list-style-type: lower-alpha~~p>#include <">~~<li>Then compile and run '''hello_world~~linux/module.~~c'''</li>~~h></olp>

~~orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''~~

~~orangepi@orangepi:~$ '''./hello_world'''~~static int hello_init(void)

~~Hello World!~~{

~~<ol start="2" style="list-style-type~~: ~~decimal~~printk("">~~<li>Ubuntu jammy is installed with Python3 by default<ol style="list~~Hello Orange Pi -~~style~~-~~type: lower-alpha~~init\n");">~~<li>Python3 specific version is shown below</li></ol></li></ol>~~

~~orangepi@orangepi:~$ '''python3'''~~

~~Python '''3.10.4''' (main, Apr 2 2022, 09~~:~~04:19) [GCC 11.2.~~return 0~~] on linux~~;

~~Type "help", "copyright", "credits" or "license" for more information.~~}

~~>>>~~static void hello_exit(void)

~~<ol start="2" style="list~~{ :printk("Hello Orange Pi -~~style~~-~~type: lower-alpha~~exit\n");">~~<li>Edit '''hello_world.py''' program in Python language</li></ol>~~

~~orangepi@orangepi:~$ '''vim hello_world.py'''~~

~~print('Hello World!')~~:return;

~~<ol start="3" style="list-style-type: lower-alpha;"><li>The results of running '''hello_world.py''' are shown below</li></ol>~~}

~~orangepi@orangepi:~$ '''python3 hello_world.py'''~~

~~Hello World!~~module_init(hello_init);

~~<ol start="3" style="list-style-type: decimal~~module_exit(hello_exit);">~~<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 following command to install openjdk-18</li></ol></li></ol>~~

~~orangepi@orangepi:~$ '''sudo apt install -y openjdk-18-jdk'''~~

MODULE_LICENSE("GPL");

|}

</ol>

<li>~~After installation~~Then write the Makefile for compiling the hello kernel module, ~~you can check the version of Java~~as follows:</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim Makefile'''

~~orangepi@orangepi:~~~ifneq ($ ~~'''java --version'''~~(KERNELRELEASE),)

~~openjdk 18~~obj-~~ea 2022-03-22~~m:=hello.o

~~OpenJDK Runtime Environment (build 18-ea+36-Ubuntu-1)~~else

~~OpenJDK 64-Bit Server VM~~ KDIR :=/lib/modules/$(~~build 18~~shell uname -~~ea+36-Ubuntu-1, mixed mode, sharing~~r)/build

~~<ol start~~PWD :=~~"3" style="list-style-type: lower-alpha;"><li>Edit the '''hello_world.java''' of the Jave version</li></ol>~~$(shell pwd)

~~orangepi@orangepi~~all:~~~$ '''vim hello_world.java'''~~

~~public class hello_world~~:make -C $(KDIR) M=$(PWD) modules

{clean:

~~public static void main(String[] args)~~:rm -f *.ko *.o *.mod.o *.mod *.symvers *.cmd *.mod.c *.order

endif|}</ol><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>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''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.'''</big>

~~System~~[[File:pi3b-img352.~~out.println("Hello World!")~~png|center]]|}{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''make'''

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

~~<ol start="4" style="list-style-type~~: ~~lower-alpha;"><li>Then compile and run '''hello_world.java'''<~~CC [M] /home/~~li><~~orangepi/~~ol>~~hello.o

:MODPOST /home/orangepi~~@orangepi:~$ '''javac hello_world~~/Module.~~java'''~~symvers

:CC [M] /home/orangepi~~@orangepi:~$ '''java hello_world'''~~/hello.mod.o

~~Hello World!~~:LD [M] /home/orangepi/hello.ko

make[1]: Leaving directory '/usr/src/linux-headers-5.10.160-rockchip-rk35xx'|}<~~span id~~/ol><ol start="4" style="qtlist-style-~~installation~~type: lower-~~method~~alpha;"><li>After compiling, the '''hello.ko''' kernel module will be generated</~~span~~li>{| class="wikitable" style= ~~QT installation method ==~~"width:800px;" |-| orangepi@orangepi:~$ '''ls *.ko'''

# hello.ko|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Use the ~~following script~~ '''insmod''' command to ~~install QT5 and QT Creator~~insert the '''hello.ko''' kernel module into the kernel</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo insmod hello.ko'''|}</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 '''hello.ko''' kernel module is loaded correctly.</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~install_qt.sh~~dmesg | grep "Hello"'''

~~<ol start="2" style="list~~[ 2871.893988] '''Hello Orange Pi -~~style~~-~~type: decimal;">~~init'''|}~~<li>The QT version number will be automatically printed after installation~~</pol><ol start="7" style="list-style-type: lower-alpha;"><li>~~Ubuntu20.04 comes with QT version~~ Use the '''rmmod''' command to uninstall the '''~~5.12~~hello.8ko'''kernel module</li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo rmmod hello'''

orangepi@orangepi:~$ '''~~install_qt.sh~~dmesg | grep "Hello"'''

[ 2871.~~.....~~893988] Hello Orange Pi -- init

~~QMake version 3~~[ 3173.1800892] '''Hello Orange Pi -- exit'''|}</ol></li></ol>

~~Using Qt version ''~~== Use of the Raspberry PI's 5~~.12.8''' in /usr/lib/aarch64-linux~~-~~gnu~~inch screen ==

<~~ol start~~span id="~~2" style="list~~assembly-method-of-raspberry-pi-~~style~~5-~~type: lower~~inch-~~alpha;~~screen"><li/span>~~Ubuntu22.04 comes with QT version '''~~=== Assembly method of Raspberry PI 5~~.15.3'''</li></ol>~~-inch screen ===

~~orangepi@orangepi~~<ol style="list-style-type:~~~$ '''install_qt.sh'''~~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>

[[File:pi3b-img353.~~.....~~png]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>15pin MIPI cable</li>

~~QMake version 3~~[[File:pi3b-img354.1png]]</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>

~~Using Qt version '''5.15~~[[File:pi3b-img355.png]]</ol><ol start="3~~''' in /usr/lib/aarch64~~" style="list-~~linux~~style-~~gnu~~type: decimal;"><li>Finally connect to the LCD interface of the Orange Pi 3B development board</li>

[[File:pi3b-img356.png]]</ol ~~start~~>~~<li>Debian11 comes with QT version '''5.15.2'''~~</~~li></ol~~span>

~~orangepi@orangepi:~$ '''install_qt.sh'''~~=== Open the Raspberry PI 5-inch screen configuration method ===

<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 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;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then select '''System'''</li>

~~QMake version 3~~[[File:pi3b-img357.1png]]</ol><ol start="3" style="list-style-type: lower-alpha;">~~Using Qt version~~ <li>Then select '''~~5.15.2~~Hardware''' in </~~usr/lib/aarch64-linux-gnu~~li>

[[File:pi3b-img358.png]]

</ol>

<li>~~Debian12 comes with QT version '''5.15.8'''~~Then use the arrow keys on the keyboard to locate the Rasp-7inch-touchscreen, and then use the space button to check</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img359.png]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then select '''~~install_qt.sh~~<Save>'''to save</li>

[[File:pi3b-img360.~~.....~~png]]</ol><ol start="6" style="list-style-type: lower-alpha;"><li>Then select '''<Back>'''</li>

~~QMake version 3~~[[File:pi3b-img361.1png]]</ol><ol start="7" style="list-style-type: lower-alpha;"><li>Then select '''<Reboot>''' to restart the system for the configuration to take effect</li>

~~Using Qt version '''5.15~~[[File:pi3b-img362.~~8''' in /usr/lib/aarch64-linux-gnu~~png]]

~~<ol start~~{| class="3wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Then you can see the QT Creator launch icon in '''Applications~~'''The above settings will eventually add the configuration of <~~/li~~span style="color:#FF0000">overlays=raspi-7inch-touchscreen</olspan>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.'''

~~[[File~~'''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=raspi-7inch-~~img327~~touchscreen is also possible.~~png|576x270px]]~~'''</big>

~~QT Creator can also be opened using the following command~~

orangepi@orangepi:~$ '''~~qtcreator~~cat /boot/orangepiEnv.txt | grep "raspi"'''

'''~~During the startup of QT and QT applications, if the following error is displayed, ignore it. This error has no impact on application running.~~overlays=raspi-7inch-touchscreen #Sample configuration'''|}~~'''libGL error~~</ol></li></ol><ol start="3" style="list-style-type: ~~failed to create dri~~ decimal;"><li>After startup, you can see the lcd screen~~'''~~display as follows:</li>

~~'''libGL error~~[[File: ~~failed to load driver: rockchip'''~~pi3b-img363.png]]</ol>

~~'''libGL error: failed to create dri screen'''~~=== The method of server version image rotation display direction ===

<ol start="1" style="list-style-type: decimal;"><li>Add '''~~libGL error~~extraargs=fbcon=rotate: ~~failed~~ the direction to ~~load driver~~rotate''' in '''/boot/orangepiEnv.txt''' This line configuration can set the direction displayed by the server version of the Linux system, where the number after '''fbcon=rotate: ~~rockchip~~'''can be set as:</li>

<ol ~~start="4"~~ style="list-style-type: ~~decimal~~lower-alpha;"><li>~~The interface after QT Creator~~ 0: normal screen (default is ~~opened is as follows~~landscape)</li><li>1: Turn clockwise 90 degrees</li><li>2: Flip 180 degrees</li><li>3: Turn clockwise 270 degrees</olli>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''

~~[[File:pi3b-img328.png|418x222px]]~~overlays=lcd1

'''<~~ol start="5"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>The QT Creator version is shown below~~extraargs=cma=64M fbcon=rotate:3</pspan>'''|}~~<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~The default version of QT Creator in~~ '''~~Ubuntu20~~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).04''' ~~is as follows~~</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>

~~[[File:pi3b~~

~~<ol start~~=~~"2" style~~=~~"list-style-type: lower-alpha;"><li>The default~~ = Method of rotating display and touch direction of desktop version ~~of QT Creator in '''Ubuntu22.04''' is as follows</li></ol>~~image ===

~~[[File:pi3b-img330.png|443x237px]]~~# First open '''Display''' Settings in Linux

~~<ol start="3" style="list-style-type~~: ~~lower~~:[[File:pi3b-~~alpha;"><li>The default version of QT Creator in '''Debian11''' is as follows</li></ol>~~img364.png]]

~~[[File~~<ol start="2" style="list-style-type:~~pi3b~~decimal;"><li>Then select the direction you want to rotate in '''Rotation'''<ol style="list-~~img331.png|444x238px]]~~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>

~~<ol start="4" style="list-style-type: lower-alpha;"><li>The default version of QT Creator in '''Debian12''' is as follows</li></ol>~~ [[File:pi3b-~~img332~~img365.png~~|449x277px~~]] ~~<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>~~</ol>

</li></ol>

<li>Then click '''Apply'''</li>

[[File:pi3b-~~img333~~img366.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select '''Keep this configuration'''</li> [[File:pi3b-img367.png~~|573x164px~~]]</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:~$ '''set_lcd_rotate.sh left'''|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>'''Inverted''': Flip up and down, which is equivalent to rotating 180 degrees</li>{| class="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;" |-| 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:'''

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

~~<li>Then remove the check box for '''ClangCodeModel'''</li></ol>~~

~~[[File:pi3b-img334~~'''1.~~png|408x254px]]~~Rotate the direction displayed by the framebuffer'''

~~<ol start="3" style="list-style-type: lower-alpha;"><li>~~'''~~Restart QT Creator after~~ 2. Rotate the ~~Settings are complete~~direction of the touch'''~~</li><li>Then make sure that QT Creator uses the GCC compiler, if the default is Clang, change it to GCC</li></ol>~~

'''~~Debian12 Please skip this step~~3.Turn off the boot logo'''

~~[[File:pi3b-img335~~'''4.~~png|576x315px]]~~Restart the system'''

~~[[File:pi3b-img336.png|575x307px]]~~

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

|}

</ol>

</li></ol>

<li>~~You can then open a sample code~~Touch rotation reference</li>{| class="wikitable" style="width:800px;" |-| '''https://wiki.ubuntu.com/X/InputCoordinateTransformation'''|}</ol>

~~[[File:pi3b-img337.png|575x312px]]~~== Instructions for using the switch logo ==

~~<ol start="8" style="list-style-type: decimal;"><li>Clicking on~~ # By default, the ~~example code~~ switch logo will ~~automatically open~~ only be displayed in the desktop version of the ~~corresponding instruction document, you can carefully read~~ system# Set the ~~instructions<~~'''bootlogo''' variable to '''false''' in '''/~~li><~~boot/~~ol>~~orangepiEnv.txt''' to turn off the switch logo

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-~~img338~~| orangepi@orangepi:~$ '''vim /boot/orangepiEnv.~~png|576x218px]]~~txt'''

~~<ol start~~verbosity=~~"9" style="list-style-type: decimal;"><li>Then click '''Configure Project'''</li></ol>~~1

~~[[File~~'''bootlogo=false'''|~~575x304px]]~~}

<ol start="103" style="list-style-type: decimal;"><li>~~Then click~~ Set the ~~green triangle~~ '''bootlogo''' variable to '''true''' in ~~the lower left corner~~ '''/boot/orangepiEnv.txt''' to ~~compile and run~~ enable the ~~sample code~~switch logo</li~~></ol~~>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img340~~| orangepi@orangepi:~$ '''vim /boot/orangepiEnv.~~png|575x312px]]~~txt'''

~~<ol start~~verbosity=~~"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</li></ol>~~1

~~[[File~~'''bootlogo=true'''|}</ol><ol start="4" style="list-style-~~img341~~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;" |-|~~576x308px]]~~orangepi@orangepi:~$ '''sudo update-initramfs -u'''|}</ol>

~~<ol start~~=~~"12" style~~=~~"list-style-type: decimal;"><li>Reference documents</li></ol>~~How to use the ZFS file system ==

~~https~~{| class="wikitable" style="background-color:~~//wiki~~#ffffdc;width:800px;" |-| <big>'''The latest version of Ubuntu20.qt04, Ubuntu22.io04, Debian11 and Debian12 desktop version systems</~~Install_Qt_5_on_Ubuntu~~span> have pre-installed zfs, you can use it directly.'''

~~https://download~~'''The pre-installed zfs version in Ubuntu20.qt04 and Ubuntu22.~~io/archive/qtcreator~~04 desktop systems is 2.1.6.'''

~~https://download~~'''The pre-installed zfs version in Debian11 and Debian12 desktop systems is 2.qt1.~~io/archive/qt~~11.'''

~~<span id="ros~~'''After the system starts, please first confirm whether the zfs kernel module has been loaded. If you can see zfs-~~installation~~related content using the lsmod command, it means that the system has pre-~~method">~~installed zfs.'''</~~span~~big>~~== ROS Installation Method ==~~

~~=== How to install ROS 1 Noetic on Ubuntu 20.04 ===~~orangepi@orangepi:~$ '''lsmod | grep "zfs"'''

~~# The current active version of ROS 1 is as follows, the recommended version is '''Noetic Ninjemys'''~~zfs                     2801664     0

~~[[File:pi3b-img342.png|345x235px]]~~zunicode             327680     1   zfs

~~[[File:pi3b-img343.png|576x210px]]~~zzstd                  471040     1   zfs

~~[http://docs.ros.org/ http://docs.ros.org]~~zlua                    139264     1   zfs

~~'''https://wiki.ros.org/Distributions'''~~zcommon             69632     1   zfs

~~<ol start="~~znvpair                 61440     2~~" style="list-style-type: decimal~~ ">~~<li>The official installation document link of ROS 1 '''Noetic Ninjemys''' is as follows:</li></ol>~~zfs,zcommon

~~[http://wiki.ros.org/noetic/Installation/Ubuntu '''http://wiki.ros.org/noetic/Installation/Ubuntu''']~~zavl                      16384     1   zfs

~~<ol start="3" style="list-style-type: decimal~~icp  "><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>                   221184     1   zfs

~~http://wiki.ros.org/noetic/Installation~~spl                       77824     6   zfs,icp,zzstd,znvpair,zcommon,zavl|}

~~[[File:pi3b~~=== How to install ZFS ===

~~<ol start~~{| class="4wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Then use~~ '''Before installing zfs, please make sure that the Linux image used is the latest version. In addition, if zfs is already installed in the ~~script below~~ system, it needs to ~~install ros1~~be installed again.'''</~~li></ol~~big>|}

~~orangepi@orangepi3b:~$~~ 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|'''~~install_ros.sh ros1~~section on the method of installing the kernel header file''']].

~~<ol start="5" style="list-style-type: decimal;"><li>Before using~~ In Ubuntu20.04, Ubuntu22.04 and Debian11 systems, zfs cannot be installed directly through apt, because the ~~ROS tool, you first need to initialize rosdep~~default apt source zfs version is lower than 2.1.6, and ~~then you can quickly install some system dependencies~~ there is a problem of incompatibility with rk Linux5.10 kernel. This problem is fixed in zfs version 2.1.6 and ~~some core components in ROS when compiling the source code</li></ol>~~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 '''~~Note that running the following command needs to ensure that~~ official tool'''] of the development board ~~can access github normally~~. Open the '''official tool''', ~~otherwise an error will be reported due to network problems.~~and enter the '''zfs-related deb package folders used by Ubuntu and Debian systems'''. You can see three types of deb packages: Ubuntu20.04, Ubuntu22.04 and Debian11. Please download the required version.

~~'''The install_ros~~[[File:pi3b-img368.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.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.'''png]]

After downloading the zfs deb packages of the corresponding version, please upload them to the Linux system of the development board. For the upload method, please refer to '''~~https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew~~[[Orange Pi 3B#The method of uploading files to the Linux system of the development board|the description in the section of the method of uploading files to the Linux system of the development board]].~~yaml~~'''

After the upload is complete, use the '''~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml~~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.

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~ERROR: error loading sources list:~~sudo apt install ./*.deb'''|}

~~'''The read operation timed out'''~~After the installation is complete, use the following command to see the zfs-related kernel modules:

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~source~~ ls /lib/modules/~~opt~~5.10.160-rockchip-rk356x/~~ros~~updates/~~noetic~~dkms/~~setup.bash~~'''

~~orangepi@orangepi:~$~~ '''~~sudo rosdep init~~icp.ko spl.ko zavl.ko zcommon.ko zfs.ko zlua.ko znvpair.ko zunicode.ko zzstd.ko'''|}

~~Wrote /etc/ros/rosdep/sources.list.d/20-default.list~~Then restart the Linux system to see that the zfs kernel module will be automatically loaded:

~~Recommended~~{| class="wikitable" style="width: ~~please run~~800px;" |-| orangepi@orangepi:~$ '''lsmod | grep "zfs"'''

~~rosdep update~~zfs                     2801664     0

~~orangepi@orangepi:~$ '''rosdep update'''~~zunicode             327680     1   zfs

~~reading in sources list data from /etc/ros/rosdep/sources.list.d~~zzstd                  471040     1   zfs

~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml~~zlua                    139264     1   zfs

~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml~~zcommon             69632     1   zfs

~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/python.yaml~~znvpair                 61440     2   zfs,zcommon

~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml~~zavl                      16384     1   zfs

~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml~~icp                     221184     1   zfs

~~Query rosdistro index https://raw.githubusercontent.com/ros/rosdistro/master/index-v4.yaml~~spl                       77824     6   zfs,icp,zzstd,znvpair,zcommon,zavl|}

~~Skip end-~~In Debian12, the default version of~~-life distro "ardent"~~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.

~~Skip end~~{| class="wikitable" style="width:800px;" |-of| orangepi@orangepi:~$ '''sudo apt install -~~life distro "bouncy"~~y zfsutils-linux zfs-dkms'''|}

~~Skip end~~

~~Skip end-~~=== Methods of~~-life distro "dashing"~~creating ZFS pools ===

~~Skip end~~{| class="wikitable" style="background-~~of-life distro &quot~~color:#ffffdc;~~eloquent&quot~~width:800px;" |-| <big>'''ZFS is based on storage pools, we can add multiple physical storage devices to the pool, and then allocate storage space from this pool.'''

~~Add distro "foxy"~~'''The following content is demonstrated based on the development board connected to an NVMe SSD and a USB flash drive.'''</big>|}

~~Add distro "galactic"~~# 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:

~~Skip end~~::[[File:pi3b-~~of-life distro "groovy"~~img369.png]]

~~Add distro &quot~~<ol start="2" style="list-style-type: decimal;~~humble&quot~~"><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:~$ '''sudo zpool create -f pool1 /dev/nvme0n1 /dev/sda'''|}</ol><ol start="3" style="list-style-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>

~~Skip end~~[[File:pi3b-ofimg370.png]]</ol><ol start="4" style="list-~~life distro &quot~~style-type: decimal;~~hydro&quot~~"><li>Then execute '''df -h''' to see that '''pool1''' is mounted to the '''/pool1''' directory</li>{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''df -h'''

~~Skip end-of-life distro~~ Filesystem &~~quot~~nbsp;~~indigo~~&~~quot~~nbsp;              Size     Used Avail Use% Mounted on

~~Skip end-of-life distro~~ tmpfs &~~quot~~nbsp;~~jade~~&~~quot~~nbsp;                 1.6G     18M 1.6G 2% /run

~~Skip end-of-life distro~~ /dev/mmcblk0p2 &~~quot~~nbsp;~~kinetic~~&~~quot~~nbsp;  29G     6.0G 22G 22% /

~~Skip end-of-life distro~~ tmpfs &~~quot~~nbsp;~~lunar~~&~~quot~~nbsp;                 7.7G     46M 7.7G 1% /dev/shm

~~Add distro~~ tmpfs &~~quot~~nbsp;~~melodic~~&~~quot~~nbsp;                 5.0M     4.0K 5.0M 1% /run/lock

~~Add distro~~ tmpfs &~~quot~~nbsp;~~noetic~~&~~quot~~nbsp;                 7.7G     944K 7.7G 1% /tmp

~~Add distro~~ /dev/mmcblk0p1 &~~quot~~nbsp;~~rolling~~&~~quot~~nbsp;  1022M     115M 908M 12% /boot

~~updated cache in~~ /~~home/orangepi~~dev/zram1                 188M     4.~~ros~~5M 169M 3% /~~rosdep~~var/~~sources.cache~~log

~~<ol start="6" style="list-style-type: decimal~~tmpfs                   ">~~<li>Then open a command line terminal window on the desktop, and then use the test_ros~~ 1.~~sh script to start a small turtle routine to test whether ROS can be used normallyorangepi@orangepi:~$ '''test_ros~~6G     80K 1.~~sh'''<~~6G 1% /~~li><li>After running the '''test_ros.sh''' script, a little turtle as shown in the figure below will pop up<~~run/~~p><~~user/~~li>~~1000 <~~/ol~~br>

'''pool1                    489G     9.3M 489G 1% <~~div~~ span style="color:#FF0000">/pool1''' |}</ol><ol start="5" style="list-style-type: decimal;"><li>Use the following command to see that the file system type of pool1 is zfs</li>{| class="~~figure~~wikitable" style="width:800px;">|-| orangepi@orangepi:~$ '''mount | grep pool1'''

~~[[File~~pool1 on /pool1 type '''zfs''' (rw,xattr,noacl)|}</ol><ol start="6" style="list-~~img345.png~~style-type: decimal;"><li>Then we can test copying a file to the ZFS pool</li>{| class="wikitable" style="width:800px;" |~~575x275px~~-|~~图片4]]~~orangepi@orangepi:~$ '''sudo cp -v /usr/local/test.mp4 /pool1/'''

'/usr/local/test.mp4' -> '/pool1/test.mp4'|}</~~div~~ol><~~ol start~~span id="~~8" style="list~~test-the-data-deduplication-function-~~style~~of-~~type: decimal;~~zfs">~~<li>Then please keep the terminal window just opened at the top~~</~~li></ol~~span>

~~<div class~~=~~"figure">~~== Test the data deduplication function of ZFS ===

~~[[File~~# The data deduplication function of ZFS is disabled by default, we need to execute the following command to enable it:~~pi3b~~:{| class="wikitable" style="width:800px;" |-~~img346.png~~|~~576x275px~~orangepi@orangepi:~$ '''sudo zfs set dedup=on pool1'''|~~图片5]]~~}

~~</div>~~<ol start="92" style="list-style-type: decimal;"><li>~~At this time~~Then do a simple test, ~~press~~ first enter pool1, and then execute the ~~direction keys on the keyboard~~ following command to ~~control the little turtle to move up, down, left, and right~~generate a random file with a size of 1G</li><{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''cd /pool1/''' root@orangepi:/pool1$ '''sudo dd if=/dev/~~ol>~~urandom of=test.1g bs=1M count=1024'''

~~[[File:pi3b-img347.png|575x296px]]~~1024+0 records in

~~=== How to install ROS 2 Galactic on Ubuntu 20.04 ===~~1024+0 records out

~~# The current active version~~ 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 ~~ROS 2 is as follows~~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'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then use '''du -lh''' to see that there are currently 1002G of data in the pool, but in fact the size of the ~~recommended version~~ 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$ '''~~Galactic Geochelone~~du -lh'''

~~[[File~~1002G|}</ol><ol start="5" style="list-style-type:~~pi3b-img348~~decimal;"><li>Then use the '''zpool list''' command to see that only 1.01G is actually occupied, because these 1001 files are all duplicates, indicating that the data deduplication function is effective.~~png|576x271px]]~~</li>

[[File:pi3b-~~img349~~img371.png~~|575x265px~~]]</ol>

~~[http://docs.ros.org/ http://docs.ros.org]~~=== 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 '''~~http:~~/var/~~docs.ros.org~~log/en''' and '''/~~galactic~~etc/~~Releases.html~~'''directories into a tarball

~~<ol start~~::{| class="2wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>The link to the official ROS 2~~ |-| orangepi@orangepi:~$ '''~~Galactic Geochelone~~cd /pool1/''' ~~installation documentation is as follows:</li></ol>~~

root@orangepi:/pool1$ '''~~docs~~sudo tar -cf text.~~ros.org~~tar /var/log/en/~~galactic~~etc/~~Installation.html~~'''|}

<ol start="2" style="list-style-type: decimal;"><li>Then the file size that can be seen through the '''~~http://docs.ros.org/en/galactic/Installation/Ubuntu~~ls -~~Install-Debians.html~~lh''' command and the space occupied in the ZFS pool are both '''27M'''</li>

[[File:pi3b-img372.png]]

</ol>

<li>Then we enable compression in the ZFS pool pool1<p/li>~~It is recommended to use Ubuntu20.04 in the official installation document of ROS 2~~ {| class="wikitable" style="width:800px;" |-| root@orangepi:/pool1$ '''~~Galactic Geochelone~~sudo zfs set compression=lz4 pool1'''~~, so please ensure that~~ |}</ol><ol start="4" style="list-style-type: decimal;"><li>Then execute the ~~system used by the development board is '''Ubuntu20.04 desktop version'''. There are several ways to install ROS 2. The~~ following ~~shows how~~ command again to ~~install ROS 2~~ package the '''~~Galactic Geochelone''' using~~ /var/log/'''~~Debian packages~~and '''</~~p><~~etc/~~li><li>Use the '''install_ros.sh~~''' ~~script to install ros2~~directories into a tar package</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| ~~orangepi~~root@orangepi:~/pool1$ '''~~install_ros~~sudo tar -cf text.~~sh ros2~~tar /var/log/ /etc/'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>~~The~~ At this time, you can see that the size of the '''~~install_ros~~text.shtar''' ~~script will automatically run the '''ros2 -h''' command after installing ros2~~file is still 27M, but it only occupies 9. ~~If you can see~~ 47M in the ~~following print~~ZFS pool, ~~it means~~ indicating that the ~~ros2 installation~~ file is ~~complete~~compressed</li>~~</ol>~~ ~~usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...~~

~~ros2 is an extensible command~~[[File:pi3b-~~line tool for ROS 2~~img373.png]]</ol>

~~optional arguments:~~== How to shut down and restart the development board ==

# During the running of the Linux system, if the Type-hC power supply is directly unplugged, some data may be lost or damaged in the file system, ~~--help show this help message and exit~~so please use the '''poweroff''' command to shut down the Linux system of the development board before powering off. Then unplug the power again.

~~Commands~~::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo poweroff'''|}

~~action Various action related sub~~<ol start="2" style="list-~~commands~~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>

~~bag Various rosbag related sub~~[[File:pi3b-~~commands~~img374.png]]

~~component Various component related sub~~{| class="wikitable" style="background-~~commands~~color:#ffffdc;width:800px;" |-| <big>'''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.'''</big>

~~daemon Various daemon related sub~~[[File:pi3b-~~commands~~img375.png|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>

~~doctor Check ROS setup and other potential issues~~[[File:pi3b-img374.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>The command to restart the Linux system is</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo''' '''reboot'''|}</ol>

~~interface Show information about ROS interfaces~~= '''Linux SDK——orangepi-build instructions''' =

~~launch Run a launch file~~== Compilation system requirements ==

~~lifecycle Various lifecycle related sub~~{| class="wikitable" style="background-~~commands~~color:#ffffdc;width:800px;" |-| <big>'''We can cross-compile the Linux image of the development board on the x64 computer, or compile the Linux image of the development board on the Ubuntu22.04 system of the development board, please choose one according to your preference.'''

~~multicast Various multicast related sub-commands~~

~~node Various node related sub~~'''If you use orangepi-~~commands~~build to compile the Linux image in the Ubuntu22.04 system of the development board, please do a good job of cooling (especially when the SSD starts). If the heat dissipation is not done well, it is prone to the error of file system runaway.'''</big>|}

~~param Various param related sub~~=== Compile with the Ubuntu22.04 system of the development board ===

~~pkg Various package related sub~~# The Linux SDK, namely '''orangepi-~~commands~~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.

~~run Run a package specific executable~~::{| class="wikitable" style="width:800px;" |-| ~~security Various security related sub~~orangepi@orangepi:~$ '''lsb_release -~~commands~~a'''

~~service Various service related sub-commands~~No LSB modules are available.

~~topic Various topic related sub-commands~~Distributor ID: Ubuntu

~~wtf Use `wtf` as alias to `doctor`~~Description: Ubuntu 22.04.1 LTS

~~Call `ros2 <command> -h` for more detailed usage~~Release: '''22.04'''

~~<ol start="6" style="list-style-type~~Codename: ~~decimal;">~~jammy~~<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></ol>~~|}

~~orangepi@orangepi3b~~<ol start="2" style="list-style-type:~$ decimal;"><li>'''~~test_ros~~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.sh'''</li></ol>

~~[INFO] [1671174101~~

~~[INFO] [1671174101~~=== Compile with x64 Ubuntu22.~~235661048] [listener]: I heard: [Hello World: 1]~~04 computer ===

~~[INFO] [1671174102~~# The Linux SDK, '''orangepi-build''', supports running on computers with '''Ubuntu 22.04''' installed, so before downloading orangepi-build, please make sure that the Ubuntu version installed on your computer is Ubuntu 22.04. The command to check the Ubuntu version installed on the computer is as follows.~~199572327] [talker]: Publishing:~~ If the Release field does not display '~~Hello World: 2~~''22.04''', it means that the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operations.

~~[INFO] [1671174102.204196299] [listener]~~: ~~I heard~~: ~~[Hello World~~{| class="wikitable" style="width: 2]800px;" |-| test@test:~$ '''lsb_release -a'''

~~[INFO] [1671174103~~No LSB modules are available.~~199580322] [talker]: Publishing: 'Hello World: 3'~~

~~[INFO] [1671174103.204019965] [listener]~~Distributor ID: ~~I heard: [Hello World: 3]~~Ubuntu

~~<ol start="7" style="list-style-type~~Description: ~~decimal;"><li>Run the following command to open rviz2</li></ol>~~Ubuntu 22.04 LTS

~~orangepi@orangepi~~Release:~$ '''~~source /opt/ros~~22.04</~~galactic/setup.bash~~span>'''

~~orangepi@orangepi~~Codename:~~~$ '''ros2 run rviz2 rviz2'''~~jammy|}

<~~div class~~ol start="~~figure~~2"style="list-style-type: decimal;"><li>If the computer is installed with Windows system and there is no computer with Ubuntu 22.04 installed, you can consider using '''VirtualBox''' or '''VMware''' to install an Ubuntu 22.04 virtual machine in the Windows system. But please be careful not to compile orangepi-build on the WSL virtual machine, because orangepi-build has not been tested in the WSL virtual machine, so it cannot be guaranteed that orangepi-build can be used normally in WSL.</li><li>The download address of the installation image of Ubuntu 22.04 '''amd64''' version is:</li>

{| class="wikitable" style="width:800px;" |-| [~~[File~~https://repo.huaweicloud.com/ubuntu-releases/21.04/ubuntu-21.04-desktop-amd64.iso '''https:~~pi3b~~//mirrors.tuna.tsinghua.edu.cn/ubuntu-~~img350~~releases/22.~~png|576x324px|1]~~04/ubuntu-22.04-desktop-amd64.iso''']

~~</div><ol start="8" style="list-style-type: decimal;"><li>For the usage of ROS, please refer to the documentation of ROS 2</li></ol>~~Or

~~http~~'''https://~~docs~~repo.~~ros~~huaweicloud.~~org~~com/enubuntu-releases/~~galactic~~22.04/ubuntu-22.04.1-desktop-amd64.iso'''|}</~~Tutorials~~ol><ol start="4" style="list-style-type: decimal;"><li>After installing Ubuntu 22.~~html~~04 on the computer or virtual machine, please set the software source of Ubuntu 22.04 to Tsinghua source, otherwise it is easy to make mistakes due to network reasons when installing the software later<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>

{| class="wikitable" style="width:800px;" |-| '''https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/'''|}<~~span id~~/ol><ol start="~~how-to-install-ros-~~2" style="list-~~humble-on~~style-~~ubuntu~~type: lower-~~22.04~~alpha;"><~~/span~~li>~~=== How~~ Note that the Ubuntu version needs to be switched to ~~install ROS 2 Humble on Ubuntu~~ 22.04 ~~===~~</li>

~~# Use~~ [[File:pi3b-img376.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The content of the '''~~install_ros~~/etc/apt/sources.shlist''' ~~script~~ file that needs to ~~install ros2~~be replaced is</li>

~~orangepi~~{| class="wikitable" style="width:800px;" |-| test@~~orangepi~~test:~$ '''~~install_ros~~sudo mv /etc/apt/sources.list /etc/apt/sources.list.~~sh ros2~~bak'''

~~<ol start="2" style="list-style-type~~test@test: ~~decimal;"><li>The~~ ~$ '''~~install_ros~~sudo vim /etc/apt/sources.~~sh''' script will automatically run the ''~~list'~~ros2 -h~~''~~' command after installing ros2. If you can see the following print, it means that the ros2 installation is complete</li></ol>~~

~~usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...~~# By default, the source image is commented to improve the speed of apt update, you can uncomment it yourself if necessary

~~ros2 is an extensible command-line tool for ROS 2~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse

~~optional arguments~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse

deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-~~h, --help show this help message and exit~~updates main restricted universe multiverse

~~Commands~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse

~~action Various action related sub~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-~~commands~~backports main restricted universe multiverse

~~bag Various rosbag related sub~~# deb-~~commands~~src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse

~~component Various component related sub~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-~~commands~~security main restricted universe multiverse

~~daemon Various daemon related sub~~# deb-~~commands~~src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-security main restricted universe multiverse

~~doctor Check ROS setup and other potential issues~~

~~interface Show information about ROS interfaces~~# Pre-release software source, not recommended to enable

~~launch Run a launch file~~# deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse

~~lifecycle Various lifecycle related sub~~# deb-~~commands~~src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse|}</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</li>{| class="wikitable" style="width:800px;" |-| 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.'''</li></ol></li></ol>

~~multicast Various multicast related sub-commands~~== Get the source code of Linux sdk ==

~~node Various node related sub~~=== Download orangepi-build from github ===

~~param Various param related sub~~# The Linux sdk actually refers to the code of orangepi-~~commands~~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:

~~pkg Various package related sub~~::{| class="wikitable" style="width:800px;" |-~~commands~~| test@test:~$ '''sudo apt-get update'''

~~run Run a package specific executable~~test@test:~$ '''sudo apt-get install -y git'''

~~security Various security related sub~~test@test:~$ '''git clone https://github.com/orangepi-~~commands~~xunlong/orangepi-build.git -b next'''|}::{| class="wikitable" style="background-color:#ffffdc;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>

~~service Various service related sub-commands~~<div class="figure">

~~topic Various topic related sub~~[[File:pi3b-~~commands~~img377.png|center]]

~~wtf Use `wtf` as alias~~ </div>|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Downloading the orangepi-build code through the git clone command does not require entering the user name and password of the github account (the same is true for downloading other codes in this manual), if the Ubuntu PC prompts the user to ~~`doctor`~~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>|}

~~Call `ros2 <command&gt~~<ol start="2" style="list-style-type: decimal; "><li>The u-~~h` for more detailed usage.~~boot and Linux kernel versions currently used by the development board are as follows</li>

~~<ol start~~{| class="3wikitable" style="~~list-style~~width:800px;text-~~type~~align: ~~decimal~~center;">~~<li>Then you can use the~~ |-|'''branch'''|'''u-boot version'''|'''Linux Kernel version'''|-|'''legacy'''|'''~~test_ros~~u-boot 2017.sh09'''|''' ~~script to test whether ROS 2 is installed successfully~~Linux5. ~~If you can see the following print, it means that ROS 2 can run normally</li></ol>~~10'''|}~~orangepi@orangepi3b~~{| class="wikitable" style="background-color:#ffffdc;width:~$ 800px;" |-| <big>'''~~test_ros~~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.sh'''

~~[INFO] [1671174101~~'''Currently, the Linux5.10 bsp kernel provided by RK is defined as the legacy branch.~~200091527] [talker]~~If the mainline kernel is supported in the future, a current branch will be added.'''</big>|}</ol><ol start="3" style="list-style-type: ~~Publishing~~decimal;"><li>orangepi-build will contain the following files and folders after downloading<ol style="list-style-type: lower-alpha;"><li>'''build.sh'''~~Hello World~~: 1Compile 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'''

~~[INFO] [1671174101~~'''build.~~235661048] [listener]~~sh      external      LICENSE      README.md      scripts'''|}{| class="wikitable" style="background-color: ~~I heard~~#ffffdc;width: ~~[Hello World: 1]~~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>

~~[INFO] [1671174102.199572327] [talker]: Publishing: 'Hello World: 2'~~=== Download the cross-compilation toolchain ===

~~[INFO] [1671174102.204196299] [listener]~~{| class="wikitable" style="background-color: ~~I heard~~#ffffdc;width: ~~[Hello World: 2]~~800px;" |-| <big>'''The cross-compilation toolchain will only be downloaded when the orangepi-build compilation image is used on an x64 computer. Compiling the Linux image of the development board in the Ubuntu22.04 of the development board will not download the cross-compilation toolchain. At this time, orangepi-build/toolchains will be an empty folder.'''</big>|}

~~[INFO] [1671174103.199580322] [talker]: Publishing: 'Hello World: 3'~~ ~~[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]~~ ~~<ol start="4" style="list~~# When orangepi-~~style~~build runs for the first time, it will automatically download the cross-~~type: decimal;"><li>Run~~ compilation toolchain and put it in the ~~following command to open rviz2</li></ol>~~ ~~orangepi@orangepi:~$~~ '''~~source /opt/ros/humble/setup.bash~~toolchains''' folder. Every time after running the build.sh script of orangepi~~@orangepi:~$~~ -build, it will check whether the cross-compilation toolchain in '''~~ros2 run rviz2 rviz2~~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.

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

</div>

<ol start="52" style="list-style-type: decimal;"><li>~~Reference documents~~The image URL of the cross-compilation toolchain in China is the open source software image site of Tsinghua University</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| '''~~http~~https://~~docs~~mirrors.~~ros~~tuna.~~org~~tsinghua.edu.cn/enarmbian-releases/~~humble~~_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/~~index.html~~'''

~~[http://docs~~gcc-arm-11.~~ros~~2-2022.~~org/en/galactic/Tutorials.html '''http://docs.ros.org/en/humble/Installation/Ubuntu~~02-x86_64-aarch64-none-~~Install~~linux-~~Debians.html''']~~gnu

~~== How to install kernel header files ==~~arm-none-linux-gnueabihf

~~# The Linux image released by OPi comes with the deb package of the kernel header file by default, and the storage location is '''/opt/'''~~gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu

~~orangepi@orangepi:~$ '''ls /opt/~~gcc-arm-9.2-2019.12-x86_64-arm-none-linux-~~headers*'''~~gnueabihf

~~/opt/linux-headers-legacy~~gcc-~~rockchip~~linaro-~~rk356x_x~~4.x9.~~x_arm64~~4-2017.~~deb~~01-x86_64_arm-linux-gnueabi

~~<ol start="2" style="list~~gcc-~~style~~linaro-~~type: decimal;"><li>Use the following command to install the deb package of the kernel header file</li></ol>~~5.5.0-2017.10-x86_64_arm-linux-gnueabihf

~~'''The name of the kernel header file deb package needs to be replaced with the actual name, please do not copy it~~gcc-linaro-7.~~'''~~4.1-2019.02-x86_64_aarch64-linux-gnu

~~orangepi@orangepi:~$ '''sudo dpkg~~ gcc-~~i /opt/linux~~linaro-~~headers~~7.4.1-~~legacy~~2019.02-~~rockchip~~x86_64_arm-~~rk356x_1.x.x_arm64.deb'''~~linux-gnueabi

~~<ol start="3" style="list~~gcc-~~style~~linaro-~~type: decimal;"><li>After installation, you can see the folder where the kernel header files are located under '''/usr/src'''</li></ol>~~aarch64-none-elf-4.8-2013.11_linux

~~orangepi@orangepi:~$ '''ls /usr/src'''~~ gcc-linaro-arm-linux-~~headers~~gnueabihf-54.108-2014.~~160-rockchip-rk356x~~04_linux

gcc-linaro-arm-none-eabi-4.8-2014.04_linux

|}

</ol>

<li>~~Then you can write a hello~~ The cross-compilation toolchain used to compile the Linux kernel ~~module~~ source code is<ol style="list-style-type: lower-alpha;"><li>Linux5.10</li>{| class="wikitable" style="width:800px;" |-| '''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''|}</ol></li></ol><ol start="5" style="list-style-type: decimal;"><li>The cross-compilation tool chain used to ~~test~~ compile the ~~kernel header file~~u-boot source code is

<li>~~First write the code of the hello kernel module, as follows:~~v2017.09</li>{| class="wikitable" style="width:800px;" |-| '''gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu'''|}</ol>

</li></ol>

=== orangepi~~@orangepi:~$ '''vim hello.c'''~~-build complete directory structure description ===

~~#include &lt~~<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>{| class="wikitable" style="width:800px;" |-| '''https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-5.10-rk35xx'''|}</~~init~~ol><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>{| class="wikitable" style="width:800px;" |-| '''https://github.com/orangepi-xunlong/u-boot-orangepi/tree/v2017.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 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 compilation system is running:d. '''LICENSE''': GPL 2 license file:e. '''README'''.md: orangepi-build documentation:f. '''output''': Store compiled deb packages such as u-boot and Linux, compilation logs, and compiled images and other files:g. '''scripts''': general scripts for compiling Linux images:h. '''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>:{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''ls''''''build.sh     external   &gtnbsp;kernel     LICENSE     output     README.md     scripts     toolchains     u-boot     userpatches'''|}</ol>

~~#include <linux/module.h>~~== Compile u-boot ==

~~static int hello_init(void)~~# Run the build.sh script, remember to add sudo permission

::{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''sudo ./build.sh'''|}

~~printk("Hello Orange Pi~~ <ol start="2" style="list-style- ~~init\n")~~type: decimal;"><li>Select '''U-boot package''', then enter</li>

~~return 0;~~<div class="figure">

}[[File:pi3b-img379.png]]

~~static void hello_exit(void)~~</div></ol><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li>

{<div class="figure">

~~printk("Hello Orange Pi~~ [[File:pi3b-~~- exit\n");~~ ~~return;~~ } ~~module_init(hello_init);~~ ~~module_exit(hello_exit);~~ ~~MODULE_LICENSE("GPL");~~img380.png]]

</div></ol>

<li>Then it will start to compile u-boot, and some information prompted during compilation is explained as follows

<li>u-boot source code version</li>

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

|-

|

[ o.k. ] Compiling u-boot [ '''v2017.09''' ]

|}

</ol>

<li>~~Then write~~ The version of the ~~Makefile for compiling the hello kernel module, as follows:~~cross-compilation toolchain</li>~~</ol>~~ ~~orangepi@orangepi:~$ '''vim Makefile'''~~ ~~ifneq ($(KERNELRELEASE),)~~ ~~obj-m:=hello.o~~ ~~else~~ ~~KDIR :~~{| class=~~/lib/modules/$(shell uname -r)/build~~ ~~PWD :~~"wikitable" style=~~$(shell pwd)~~ ~~all~~"width:800px;" ~~make~~ |-~~C $(KDIR) M=$(PWD) modules~~| ~~clean:~~ ~~rm -f *.ko *.~~[ o *.~~mod~~k.o *] Compiler version [ '''aarch64-linux-gnu-gcc 7.mod *4.~~symvers *.cmd *.mod.c *.order~~1''' ]|}~~endif~~</ol>

<li>~~Then use the make command~~ Path to ~~compile~~ the ~~hello kernel module. The output of the compilation process is as follows:~~generated u-boot deb package</li~~></ol~~>{| class="wikitable" style="width:800px;" ~~'''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.'''~~|-| [~~[File:pi3b-img352~~o.k.~~png|337x52px~~]] ~~orangepi@orangepi:~$~~ Target directory [ '''~~make'''~~ ~~make~~ orangepi-C build/~~lib~~output/~~modules~~debs/~~5.10.160~~u-~~rockchip-35xx/build M=/home/orangepi modules~~ ~~make[1]: Entering directory~~ boot''~~/usr/src/linux-headers-5.10.160-rockchip-rk35xx~~' ~~CC [M~~] ~~/home/orangepi/hello.o~~|}~~MODPOST~~ </~~home/orangepi/Module.symvers~~ ~~CC [M] /home/orangepi/hello.mod.o~~ ~~LD [M] /home/orangepi/hello.ko~~ ~~make[1]: Leaving directory '/usr/src/linux-headers-5.10.160-rockchip-rk35xx'~~ol>

<li>~~After~~ The package name of the generated u-boot deb package</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] File name [ '''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb''' ]|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Compilation time</li>{| 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</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Repeat Build Options [ '''~~hello~~sudo .ko/build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=u-boot KERNEL_CONFIGURE=no''' ~~kernel module will be generated~~]|}</ol></li></ol><ol start="5" style="list-style-type: decimal;"><li>View the u-boot deb package generated by compilation</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''ls output/debs/u-boot/'''

~~orangepi~~linux-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@~~orangepi~~test:~/orangepi-build$ '''~~ls *.ko~~cd output/debs/u-boot'''

~~hello.ko~~test@test:~/orangepi_build/output/debs/u-boot$ $ '''dpkg -x''' \

~~<ol start="5" style="list~~'''linux-u-~~style~~boot-~~type: lower~~legacy-~~alpha~~orangepi3b_1.0.0_arm64.deb . (Note that there is a "."">~~<li>Use~~ at the end of the ~~'''insmod'''~~ command ~~to insert the~~ )'''~~hello.ko''' kernel module into the kernel</li></ol>~~

~~orangepi~~test@~~orangepi~~test:~/orangepi_build/output/debs/u-boot$ '''~~sudo insmod hello.ko~~ls'''

linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb '''usr'''|}</ol><ol start="62" style="list-style-type: lower-alpha;"><li>~~Then use the '''demsg''' command to view the~~ The decompressed file is as follows</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build/output ~~of the ''~~/debs/u-boot$ '~~hello.ko~~''tree usr' ~~kernel module. If you can see the output below, it means that the~~ ''~~'hello.ko''' kernel module is loaded correctly.</li></ol>~~

~~orangepi@orangepi:~$ '''dmesg | grep "Hello"'''~~usr

~~[ 2871.893988] '''Hello Orange Pi -- init'''~~└── lib

~~<ol start="7" style="list~~:├── linux-u-~~style~~boot-~~type: lower~~legacy-~~alpha;"><li>Use the '''rmmod''' command to uninstall the '''hello~~orangepi3b_1.0.~~ko''' kernel module</li></ol>~~0_arm64

~~orangepi@orangepi~~:~~~$ '''sudo rmmod hello'''~~│ ├── idbloader.img

~~orangepi@orangepi~~:~~~$ '''dmesg | grep "Hello"'''~~│ ├── rkspi_loader.img

~~[ 2871~~:│ └── u-boot.~~893988] Hello Orange Pi -- init~~itb

~~[ 3173.800892] '''Hello Orange Pi~~ :└── u-~~- exit'''~~boot

~~== Use of the Raspberry PI's 5-inch screen ==~~::├── LICENSE

~~=== Assembly method of Raspberry PI 5-inch screen ===~~rk3566_defconfig

~~<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></ol></li></ol>~~└── platform_install.sh

~~<blockquote>[[File:pi3b-img353.png|306x219px]]~~

~~</blockquote>~~

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

~~<li>15pin MIPI cable</li></ol>~~

3 directories, 6 files|}<~~blockquote~~/ol>~~[[File:pi3b-img354.png|276x111px]]~~</~~blockquote~~li></ol><ol start="27" style="list-style-type: decimal;"><li>~~Then connect~~ When the orangepi-bulid compilation system compiles the u-boot source code, it will first synchronize the u-boot source code with the ~~15pin MIPI cable~~ u-boot source code of the github server, so if you want to modify the ~~Raspberry PI 5~~u-~~inch screen in~~ boot source code, you first need to turn off the download and update function of the ~~way shown below~~ source code '''(~~note~~ This function needs to be fully compiled once u-boot, otherwise it will prompt that the ~~orientation~~ 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 ~~insulation surface~~source code of u-boot have been cached)''', otherwise the changes made will be reverted, the method is as follows:</li~~></ol~~>

~~[[File:pi3b~~Set the IGNORE_UPDATES variable in userpatches/config-~~img355~~default.~~png|294x160px]]~~conf to "yes"

~~<ol start~~{| class="3wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Finally connect to the LCD interface of the Orange Pi 3B development board<~~|-| test@test:~/~~li><~~orangepi-build$ '''vim userpatches/~~ol>~~config-default.conf'''

~~[[File:pi3b-img356.png|333x199px]]~~ IGNORE_UPDATES="'''yes'''"~~=== Open the Raspberry PI 5-inch screen configuration method ===~~|}</ol><ol start="8" style="list-style-type: decimal;"><li>~~The Linux image does not open the 5~~When debugging u-~~inch screen of the Raspberry PI by default. If~~ boot code, you ~~need to~~ can use the 5following method to update u-~~inch screen of~~ boot in the ~~Raspberry PI, you need to open it manually.</li><li>The steps to open the mipi lcd configuration are as follows:~~Linux image for testing

<li>~~First run '''orangepi~~Upload the compiled u-~~config''', ordinary users remember~~ boot deb package to ~~add '''sudo''' permission~~the Linux system of the development board</li><{| class="wikitable" style="width:800px;" |-| test@test:~/~~ol>~~<orangepi-build$ '''cd output/~~li><~~debs/~~ol>~~u-boot'''

~~orangepi~~test@~~orangepi~~test:~/orangepi_build/output/debs/u-boot$ '''~~sudo orangepi-config~~scp \'''

'''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb root@192.168.1.xxx:/root'''

|}

</ol>

<li>Then ~~select~~ log in to the development board and uninstall the deb package of u-boot installed</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''~~System~~apt purge -y linux-u-boot-orangepi3b-legacy'''~~</li>~~|}</ol> ~~[[File:pi3b-img357.png|575x272px]]~~

<li>~~Then select '''Hardware'''~~Install the new u-boot deb package just uploaded</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| ~~[[File~~root@orangepi:~~pi3b~~~# '''dpkg -~~img358~~i''' '''linux-u-boot-legacy-orangepi3b_1.0.~~png~~0_arm64.deb'''|~~576x266px]]~~}</ol>

<li>Then ~~use~~ run the ~~arrow keys on the keyboard to locate the Rasp~~nand-~~7inch~~sata-~~touchscreen, and then use the space button to check~~install script</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| ~~[[File~~root@orangepi:~~pi3b~~~# '''nand-sata-~~img359.png~~install'''|~~408x310px]]~~}</ol>

<li>Then select '''~~<Save>~~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 ~~save~~update the u-boot in the SPI Flash</li>~~</ol>~~ ~~[[File:pi3b-img360.png|404x133px]]~~

[[File:pi3b-img381.png]]

</ol>

<li>~~Then select '''<Back>'''~~After pressing the Enter key, a Warning will pop up first</li~~></ol~~>

[[File:pi3b-~~img361~~img382.png~~|397x151px~~]]</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>

[[File:pi3b-img383.png]]</ol><ol start="78" style="list-style-type: lower-alpha;"><li>Then ~~select~~ 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'''~~&lt~~]|}</ol><ol start="2" style="list-style-type: lower-alpha;~~Reboot&gt~~"><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''' ~~to restart the system for the configuration to take effect~~]|}</ol></li></ol> == Compile the Linux kernel ==

~~[[File:pi3b-img362~~# Run the build.~~png|331x154px]]~~sh script, remember to add sudo permission

::{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''~~The above settings will eventually add the configuration of overlays=raspi-7inch-touchscreen to /boot~~sudo ./~~orangepiEnv.txt. After setting, you can check it first. If this configuration does not exist, then there is a problem with the settings~~build.sh'''|}

<ol start="2" style="list-style-type: decimal;"><li>Select '''~~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=raspi-7inch-touchscreen is also possible.~~Kernel package''', then enter</li>

~~orangepi@orangepi:~$ '''cat /boot/orangepiEnv.txt | grep~~ <div class="~~raspi~~figure"~~'''~~>

~~'''overlays=raspi~~[[File:pi3b-~~7inch-touchscreen #Sample configuration'''~~img384.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 ===~~ # 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 the Linux system, where the number after '''fbcon=rotate:''' can be set as: ~~<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></ol>~~ ~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''~~ ~~overlays=lcd1~~ ~~'''extraargs=cma=64M fbcon=rotate:3'''~~ ~~'''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).'''~~ ~~<ol start="2" style="list-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>~~ ~~=== Method of rotating display and touch direction of desktop version image ===~~ ~~# First open '''Display''' Settings in Linux~~ ~~[[File:pi3b-img364.png|298x206px]]~~ ~~<ol start="2" style="list-style-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></ol></li></ol>~~ ~~[[File:pi3b-img365.png|286x180px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then click '''Apply'''</li></ol>~~ [[File:pi3b-~~img366~~img380.png~~|330x207px~~]]

</div></ol>

<li>Then it will prompt whether to display the kernel configuration interface. If you do not need to modify the kernel configuration, select ~~'''Keep this~~ the first one. If you need to modify the kernel configuration~~'''~~, select the second one.</li>~~</ol>~~ ~~[[File:pi3b-img367.png|374x210px]]~~

[[File:pi3b-img385.png]]

</ol>

<li>~~At this point,~~ If you choose to display the kernel configuration menu (the ~~screen display has been rotated~~second option) in step 4), ~~and then close~~ the kernel configuration interface opened by '''~~Display~~make menuconfig''' ~~program</li><li>The above steps~~ will ~~only select~~ pop up. At this time, you can directly modify the ~~display direction~~kernel configuration, save and ~~will not rotate the direction of the touch. Use the '''set_lcd_rotate~~exit after modification.~~sh''' script to rotate the direction of the touch. After the script is set~~Yes, ~~it will automatically restart~~after exiting, ~~and then you can test whether~~ the ~~touch has been used normally.<ol style="list-style-type: lower-alpha;"><li>'''None''': no rotation</li></ol>~~kernel source code will be compiled</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''set_lcd_rotate~~pi3b-img386.~~sh none'''~~png]]

<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:~/orangepi-build$ '''sudo ./build.sh KERNEL_CONFIGURE=no'''

|}

</ol>

<li>You can also set '''~~Left~~KERNEL_CONFIGURE=no'''~~: rotate left 90 degrees~~in the '''orangepi-build/userpatches/config-default.conf''' configuration file, which can permanently disable this function</lip></olli> ~~orangepi@orangepi:~$~~ <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 '''~~set_lcd_rotate.sh left~~make menuconfig'''interface. Please maximize the terminal of the Ubuntu PC and run the build.sh script again</li>

[[File:pi3b-img387.png]]

</ol>

<li>Part of the information prompted when compiling the kernel source code is as follows

<li>The version of the Linux kernel source code</li>

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

|-

|

[ o.k. ] Compiling current kernel [ '''5.10.160''' ]

|}

</ol>

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

<li>~~'''Inverted''': Flip up~~ The configuration file used by the kernel by default and ~~down, which~~ the path where it is ~~equivalent to rotating 180 degrees~~stored</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| ~~orangepi@orangepi:~$~~ [ o.k. ] Using kernel config file [ '''~~set_lcd_rotate~~config/kernel/linux-rockchip-rk356x-legacy.~~sh inverted~~config''']|}</ol>

<li>The path of the deb package related to the kernel generated by compiling</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Target directory [ '''~~Right~~orangepi-build/output/debs/''']|}</ol><ol start="5" style="list-style-type: ~~rotate right 90 degrees~~lower-alpha;"></li>The package name of the compiled kernel image deb package</olli>{| class="wikitable" style="width:800px;" |-| ~~orangepi@orangepi:~$~~ [ o.k. ] File name [ '''~~set_lcd_rotate~~linux-image-legacy-rockchip-rk356x_1.0.~~sh right~~0_arm64.deb''']|}</ol><ol start="6" style="list-style-type: lower-alpha;">~~'''~~<li>The ~~set_lcd_rotate.sh script mainly does four things~~time used for compilation</li>{| class="wikitable" style="width:~~'''~~800px;" |-| [ o.k. ] Runtime [ '''~~1. Rotate the direction displayed by the framebuffer~~5 min''']|}</ol><ol start="7" style="list-style-type: lower-alpha;">~~'''2~~<li>Finally, the compilation command to repeatedly compile the kernel selected last time will be displayed. ~~Rotate~~ Use the following command to start compiling the ~~direction of~~ kernel source code directly without selecting through the ~~touch'''~~graphical interface</li>{| class="wikitable" style="width:800px;" ~~'''3. Turn off the boot logo'''~~|-| [ o.k. ] Repeat Build Options [ '''4sudo ./build. ~~Restart the system~~sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=kernel KERNEL_CONFIGURE=no''']|}~~'''Rotating the touch direction is achieved by adding the line Option "TransformationMatrix" "x x x x x x x x x" to~~ </~~usr~~ol></~~share~~li></~~X11/xorg.conf.d/40-libinput.conf Where "x x x x x x x x x" is configured differently for different directions.'''~~ol><ol start="7" style="list-style-type: decimal;"><li>~~Touch rotation reference~~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</olli> ~~https:~~<li>'''linux-headers-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Include kernel header files</~~wiki~~li><li>'''linux-image-legacy-rockchip-rk356x_1.0.~~ubuntu~~0_arm64.~~com~~deb''' Contains kernel images and kernel modules</Xp></~~InputCoordinateTransformation~~li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''ls output/debs/linux-*'''

~~== Instructions for using the switch logo ==~~rk356x_1.0.0_arm64.deb

~~# By default, the switch logo will only be displayed~~ 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 ~~desktop version of the system~~generated Linux-image deb package are as follows<ol style="list-style-type: lower-alpha;">~~# Set~~ <li>Use the ~~'''bootlogo''' variable~~ following command to decompress the deb package</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''~~false''' in '''~~cd output/~~boot/orangepiEnv.txt~~debs''' ~~to turn off the switch logo~~

~~orangepi~~test@~~orangepi~~test:~/orangepi_build/output/debs$ '''~~vim /boot/orangepiEnv.txt~~mkdir test'''

~~verbosity=1~~test@test:~/orangepi_build/output/debs$ '''cp \'''

'''~~bootlogo=false~~linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb test/'''

~~<ol start="3" style="list-style-type~~test@test: ~~decimal;"><li>Set the '''bootlogo~~~/orangepi_build/output/debs$ ''' ~~variable to~~ cd test'''~~true''' in '''/boot/orangepiEnv.txt''' to enable the switch logo</li></ol>~~

~~orangepi~~test@~~orangepi~~test:~/orangepi_build/output/debs/test$ '''~~vim /boot/orangepiEnv.txt~~dpkg -x \'''

~~verbosity=1~~'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb .'''

test@test:~/orangepi_build/output/debs/test$ '''~~bootlogo=true~~ls'''

'''boot etc lib''' linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb '''usr'''|}</ol><ol start="42" style="list-style-type: ~~decimal~~lower-alpha;"><li>The ~~location of the boot logo image in the Linux system~~ decompressed file isas follows</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| ~~'''~~test@test:~/~~usr~~orangepi-build/~~share~~output/~~plymouth~~debs/~~themes/orangepi/watermark.png~~test$ '''tree -L 2'''

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

~~orangepi@orangepi:~$ '''sudo update-initramfs -u'''~~├── boot

~~== How to use the ZFS file system ==~~rk356x

~~'''The latest version of Ubuntu20~~│ ├── System.~~04, Ubuntu22~~map-5.10.~~04, Debian11 and Debian12 desktop version systems have pre~~160-rockchip-~~installed zfs, you can use it directly.'''~~rk356x

~~'''The pre~~│ └── vmlinuz-~~installed zfs version in Ubuntu20~~5.~~04 and Ubuntu22~~10.~~04 desktop systems is 2.1.6.'''~~160-rockchip-rk356x

~~'''The pre-installed zfs version in Debian11 and Debian12 desktop systems is 2.1.11.'''~~├── etc

~~'''After the system starts, please first confirm whether the zfs~~ │ └── kernel ~~module has been loaded. If you can see zfs-related content using the lsmod command, it means that the system has pre-installed zfs.'''~~

~~orangepi@orangepi:~$ '''lsmod | grep "zfs"'''~~├── lib

~~zfs 2801664 0~~│ └── modules

~~zunicode 327680 1 zfs~~├── linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb

~~zzstd 471040 1 zfs~~└── usr

~~zlua 139264 1 zfs~~:├── lib

~~zcommon 69632 1 zfs~~:└── share|}</ol></li></ol><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>

~~znvpair 61440 2 zfs,zcommon~~Set the IGNORE_UPDATES variable in '''userpatches/config-default.conf''' to "yes"

~~zavl 16384 1 zfs~~{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''

~~icp 221184 1 zfs~~IGNORE_UPDATES="'''yes'''"|}</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<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>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''cd output/debs'''

~~spl 77824 6 zfs,icp,zzstd,znvpair,zcommon,zavl~~test@test:~/orangepi-build/output/debs$ '''scp \'''

'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb root@192.168.1.xxx:/root'''|}</ol><~~span id~~ol start="2" style="~~how~~list-tostyle-~~install~~type: lower-~~zfs~~alpha;"><li>Then log in to the development board and uninstall the deb package of the installed Linux kernel</~~span~~li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''apt purge -y linux-image-legacy-rockchip-rk356x'''|}</ol><ol start= ~~How to install ZFS~~ "3" style="list-style-type: lower-alpha;"><li>Install the deb package of the new Linux kernel just uploaded</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''~~Before installing zfs, please make sure that the Linux~~ dpkg -i linux-image ~~used is the latest version~~-legacy-rockchip-rk356x_1.0. ~~In addition, if zfs is already installed in the system, it needs to be installed again~~0_arm64.deb'''|}</ol>~~Before installing zfs~~<ol start="4" style="list-style-type: lower-alpha;"><li>Then restart the development board, ~~you need to install~~ and then check whether the kernel ~~header file first. For the method~~ -related modifications have taken effect</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''reboot'''|}</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 ~~installing~~ the kernel ~~header~~ configuration fileis as follows, please ~~refer~~ do not go to the kernel source code to find the ~~instructions in~~ kernel configuration file used by the development board</li>{| class="wikitable" style="width:800px;" |-| [~~[\l|~~https://github.com/orangepi-xunlong/orangepi-build/blob/next/external/config/kernel/linux-rockchip-rk3588-legacy.config '''~~section on the method of installing the~~ orangepi-build/external/config/kernel ~~header file~~/linux-rockchip-rk356x-legacy.config''']].|}~~In Ubuntu20.04, Ubuntu22.04 and Debian11 systems, zfs cannot be installed directly through apt, because the default apt source zfs version is~~ </ol><ol start="2" style="list-style-type: lower ~~than 2.1.6, and there is a problem~~ -alpha;"><li>The location of ~~incompatibility with rk Linux5.10 kernel. This problem~~ the dts file used by the development board is ~~fixed in zfs version 2.1.6 and later.~~</li>{| class="wikitable" style="width:800px;" |-| ~~To solve this problem, we provide a zfs deb package that can be installed normally, which can be downloaded from the~~ [~~http~~https://~~www~~github.com/orangepi-xunlong/linux-orangepi/blob/orange-pi-5.~~org~~10-rk3588/arch/~~html~~arm64/~~hardWare~~boot/~~computerAndMicrocontrollers~~dts/~~service-and-support~~rockchip/~~Orange~~rk3588s-Piorangepi-3B5.~~html~~ dts '''~~official tool~~orangepi-build/kernel/orange-pi-5.10-rk35xx/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dts'''] ~~of the development board. Open the '''~~|}</ol><~~span class="mark"~~/li>~~official tool~~</~~span~~ol>~~''', and enter the '''~~~~zfs-related deb package folders used by Ubuntu and Debian systems~~~~'''. You can see three types of deb packages: Ubuntu20.04, Ubuntu22.04 and Debian11. Please download the required version.~~

~~[[File:pi3b-img368.png|230x93px]]~~== Compile rootfs ==

~~After downloading~~ # Run the ~~zfs deb packages of the corresponding version, please upload them to the Linux system of the development board~~build. ~~For the upload method~~sh script, ~~please refer~~ remember to ~~'''[[\l|the description in the section of the method of uploading files to the Linux system of the development board]].'''~~add sudo permission

~~After the upload is complete, use the~~ ::{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''cdsudo ./build.sh''' ~~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.~~|}

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~$ decimal;"><li>Select '''~~sudo apt install ./*.~~Rootfs and all debpackages''', then enter</li>

~~After the installation is complete, use the following command to see the zfs-related kernel modules:~~<div class="figure">

~~orangepi@orangepi~~[[File:~~~$ '''ls /lib/modules/5.10~~pi3b-img388.~~160-rockchip-rk356x/updates/dkms/'''~~png]]

~~'''icp.ko spl.ko zavl.ko zcommon.ko zfs.ko zlua.ko znvpair.ko zunicode.ko zzstd.ko'''~~</div></ol><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li>

~~Then restart the Linux system to see that the zfs kernel module will be automatically loaded:~~<div class="figure">

~~orangepi@orangepi:~$ '''lsmod | grep "zfs"'''~~ ~~zfs 2801664 0~~ ~~zunicode 327680 1 zfs~~ ~~zzstd 471040 1 zfs~~ ~~zlua 139264 1 zfs~~ ~~zcommon 69632 1 zfs~~ ~~znvpair 61440 2 zfs,zcommon~~ ~~zavl 16384 1 zfs~~ ~~icp 221184 1 zfs~~ ~~spl 77824 6 zfs,icp,zzstd,znvpair,zcommon,zavl~~ In Debian12, the default version of zfs is 2.1.11, so we can install zfs directly through the following command. Again, please make sure that the system has installed the deb package of the kernel header file before installation. ~~orangepi@orangepi:~$ '''sudo apt install -y zfsutils-linux zfs-dkms'''~~ ~~=== 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.png|379x227px]]~~ ~~<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></ol>~~ ~~orangepi@orangepi:~$ '''sudo zpool create -f pool1 /dev/nvme0n1 /dev/sda'''~~ ~~<ol start="3" style="list-style-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></ol> [[File:pi3b-~~img370~~img380.png~~|576x37px~~]]

</div></ol>

<li>Then ~~execute '''df -h''' to see that '''pool1''' is mounted to~~ select the ~~'''/pool1''' directory~~type of rootfs</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img389.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then select the type of image<ol style="list-style-type: lower-alpha;"><li>'''~~df -h~~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>

~~Filesystem Size Used Avail Use% Mounted on~~<div class="figure">

~~tmpfs 1~~[[File:pi3b-img390.~~6G 18M 1.6G 2% /run~~png]]

</~~dev~~div></~~mmcblk0p2 29G~~ 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 '''(please do not choose the Minimal version if there is no special requirement, because many things are not pre-installed by default.~~0G 22G 22%~~ Some functions may not be available)'''</li>

~~tmpfs 7.7G 46M 7.7G 1% /dev/shm~~<div class="figure">

~~tmpfs 5~~[[File:pi3b-img391.~~0M 4.0K 5.0M 1% /run/lock~~png]]

~~tmpfs 7.7G 944K~~ </div></ol><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.~~7G 1%~~ Currently, Ubuntu Jammy mainly maintains XFCE and Gnome desktops, Ubuntu Focal only maintains XFCE desktops, and Debian Bullseye mainly maintains XFCE and KDE desktops</~~tmp~~li>

~~/dev/mmcblk0p1 1022M 115M 908M 12% /boot~~<div class="figure">

~~/dev/zram1 188M 4~~[[File:pi3b-img392.~~5M 169M 3% /var/log~~png]]

~~tmpfs 1~~</div>[[File:pi3b-img393.~~6G 80K 1.6G 1% /run/user/1000~~png]]

~~'''pool1 489G 9~~You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.~~3M 489G 1% /pool1'''~~

[[File:pi3b-img394.png]]</ol><ol start="58" style="list-style-type: decimal;"><li>~~Use the following command~~ Then it will start to ~~see that~~ compile rootfs, and some of the ~~file system~~ information prompted during compilation are as follows<ol style="list-style-type: lower-alpha;"><li>The type of ~~pool1 is zfs~~rootfs</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] local not found [ Creating new rootfs cache for '''jammy''']|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The storage path of the compiled rootfs compressed package</li>~~orangepi@orangepi~~{| class="wikitable" style="width:~$ 800px;" |-| [ o.k. ] Target directory [ '''external/cache/rootfs'''~~mount~~ ]| ~~grep pool1~~}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The name of the rootfs compressed package generated by compilation</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] File name [ '''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' ]|}~~pool1 on~~ </~~pool1~~ ol><ol start="4" style="list-style-type : lower-alpha;"><li>The time used for compilation</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Runtime [ '''~~zfs~~13 min''' ~~(rw,xattr,noacl)~~]|}</ol></li></ol><ol start="69" style="list-style-type: decimal;"><li>~~Then we can test copying~~ 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: none;"><li>a ~~file~~ ) '''jammy''' indicates the type of Linux distribution of rootfs</li><li>b) '''xfce''' means rootfs is the type of desktop version, if it is '''cli''', it means the type of server version</li><li>c) '''arm64''' represents the architecture type of rootfs</li><li>d) '''f930ff6ebbac1a72108a2e100762b18f''' is the MD5 hash value generated by the package names of all software packages installed by rootfs. As long as the list of software packages installed by rootfs is not modified, this value will not change. The compilation script will use this MD5 hash value to generate Determine whether rootfs needs to ~~the ZFS pool~~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/'''

~~orangepi@orangepi:~$~~ '''~~sudo cp~~ jammy-~~v /usr/local/test~~xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.~~mp4 /pool1/~~lz4'''

~~'/usr/local/test~~jammy-xfce-arm64.~~mp4' -> '/pool1/test~~f930ff6ebbac1a72108a2e100762b18f.tar.lz4.~~mp4'~~current

jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.list|}</ol></li></ol><~~span id~~ol start="10" style="~~test-the-data-deduplication~~list-~~function~~style-~~of-zfs~~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/~~span>=== Test~~ rootfs''' to find out whether it has If there is rootfs available in the ~~data deduplication function~~ cache, use it directly, which can save a lot of ~~ZFS ===~~download and compilation time.</li></ol>

~~# The data deduplication function of ZFS is disabled by default, we need to execute the following command to enable it~~

~~orangepi@orangepi:~$ '''sudo zfs set dedup~~=~~on pool1'''~~= Compile Linux image ==

~~<ol start="2" style="list-style-type: decimal;"><li>Then do a simple test~~# Run the build.sh script, ~~first enter pool1, and then execute the following command~~ remember to ~~generate a random file with a size of 1G</li></ol>~~add sudo permission

~~orangepi~~::{| class="wikitable" style="width:800px;" |-| test@~~orangepi~~test:~/orangepi-build$ '''~~cd /pool1~~sudo ./build.sh'''|}

~~root@orangepi~~<ol start="2" style="list-style-type:~~/pool1$~~ decimal;"><li>Select '''~~sudo dd if=/dev/urandom of=test.1g bs=1M count=1024~~Full OS image for flashing''', then enter</li>

~~1024+0 records in~~<div class="figure">

~~1024+0 records out~~[[File:pi3b-img395.png]]

~~1073741824 bytes (1.1 GB, 1.0 GiB) copied, 5.04367 s, 213 MB~~</sdiv></ol><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li>

<~~ol start~~div class="3figure" ~~style="list-style-type: decimal;"><li>Then use the following command to copy 1000 random files of size 1G</li></ol~~>

~~root@orangepi~~[[File:~~/pool1$ '''for ((i=0; i<1000; i++)); do sudo cp test~~pi3b-img380.~~1g $i.test.1g; done'''~~png]]

</div></ol>

<li>Then ~~use '''du -lh''' to see that there are currently 1002G of data in the pool, but in fact the size of the ZFS pool is only '''504GB''' (~~select the ~~total capacity of SSD+U disk), which cannot hold such a large amount~~ type of ~~data~~rootfs</li>~~</ol>~~ ~~root@orangepi:/pool1$ '''du -lh'''~~ ~~1002G~~

[[File:pi3b-img389.png]]

</ol>

<li>Then ~~use~~ select the type of image<ol style="list-style-type: lower-alpha;"><li>'''~~zpool list~~Image with console interface (server)''' ~~command to see that only 1.01G~~ Indicates the image of the server version, which is ~~actually occupied, because these 1001 files are all duplicates~~relatively small</li><li>'''Image with desktop environment''' Indicates a image with a desktop, ~~indicating that the data deduplication function~~ which is ~~effective.~~relatively large</lip></olli>

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

~~=== Test the data compression function of ZFS ===~~img390.png]]

~~# Because~~ </div></ol></li></ol><ol start="6" style="list-style-type: decimal;"><li>If you are compiling the ~~stored data is different~~image of the server version, ~~the disk space saved by compression will~~ you can also ~~be different, so we~~ choose to ~~compress relatively large plain text files for compression testing, and execute~~ compile the Standard version or the Minimal version. The pre-installed software of the ~~following commands to pack~~ Minimal version will be much less than that of the Standard version '''~~/var/log/''' and~~ (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)'''</~~etc/''' directories into a tarball~~li>

~~orangepi@orangepi:~$ '''cd /pool1/'''~~<div class="figure">

~~root@orangepi~~[[File:~~/pool1$ '''sudo tar~~ pi3b-~~cf text~~img391.~~tar /var/log/ /etc/'''~~png]]

</div></ol><ol start="27" style="list-style-type: decimal;"><li>~~Then~~ If you are compiling the ~~file size that can be seen through~~ image of the ~~'''ls -lh''' command~~ 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 ~~the space occupied in the ZFS pool are both '''27M'''~~KDE desktops</li~~></ol~~>

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

~~<ol start="3" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Then we enable compression in the ZFS pool pool1</li></ol>~~img392.png]]

~~root@orangepi~~</div>[[File:~~/pool1$ '''sudo zfs set compression=lz4 pool1'''~~pi3b-img393.png]]

~~<ol start="4" style="list-style-type: decimal;"><li>Then execute~~ You can then select additional packages that need to be installed. Please press the ~~following command again~~ Enter key to ~~package the '''/var/log/''' and '''/etc/''' directories into a tar package</li></ol>~~skip directly here.

~~root@orangepi~~[[File:~~/pool1$ '''sudo tar~~ pi3b-~~cf text~~img394.~~tar~~ png]]</~~var/log/ /etc/'''~~ol><ol start="58" style="list-style-type: decimal;"><li>~~At this time~~Then it will start to compile the Linux image. The general process of compilation is as follows<ol style="list-style-type: lower-alpha;"><li>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)</li><li>Compile u-boot source code and generate u-boot deb package</li><li>Compile the Linux source code and generate Linux-related deb packages</li><li>Make the deb package of Linux firmware</li><li>Make the deb package of the orangepi-config tool</li><li>Create a deb package supported by the board</li><li>If you are compiling the desktop image, you ~~can see that~~ will also create desktop-related deb packages</li><li>Check whether the rootfs has been cached, if not, recreate the ~~size~~ rootfs, if it has been cached, directly decompress and use</li><li>Install the previously generated deb package into rootfs</li><li>Make some specific settings for different development boards and different types of ~~the '''text~~images, such as pre-installing additional software packages, modifying system configuration, etc.~~tar'''~~ </li><li>Then make an image file and format the partition, the default type is ~~still 27M, but it only occupies 9.47M in~~ ext4</li><li>Then copy the configured rootfs to the ~~ZFS pool~~mirrored partition</li><li>Then update initramfs</li><li>Finally, ~~indicating that~~ write the bin file ~~is compressed~~of u-boot into the image through the dd command</li></ol></li><li>After compiling the image, the following information will be prompted<olstyle="list-style-type: lower-alpha;"><li>The storage path of the compiled image</li>~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img373~~| [ o.k.~~png|576x79px~~]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><~~span id~~ol start="2" style="~~how~~list-tostyle-~~shut~~type: lower-~~down~~alpha;"><li>Compilation time</li>{| class="wikitable" style="width:800px;" |-~~and~~| '''[ o.k. ] Runtime [ 19 min ]'''|}</ol><ol start="3" style="list-~~restart~~style-~~the~~type: lower-~~development-board~~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</~~span~~li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT= ~~How to shut down and restart the development board~~ image RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=yes''' ]|}</ol></li></ol>

~~# During the running of the Linux system, if the Type-C power supply is directly unplugged, some data may be lost or damaged in the file system, so please use the~~ = '''~~poweroff~~Android 11 operating system instructions''' ~~command to shut down the Linux system of the development board before powering off. Then unplug the power again.~~=

~~orangepi@orangepi:~$ '''sudo poweroff'''~~== Supported Android versions ==

~~<ol start~~{| class="2wikitable" style="~~list-style~~width:800px;text-~~type~~align: ~~decimal~~center;">~~<li>In addition, the development board is equipped with a switch button, and you can also~~ |-|'''Android version'''|'''Kernel version'''|-|'''~~short press~~Android 11''' ~~the switch button on the development board to shut down~~|'''Linux4.~~</li></ol>~~19'''|}

~~[[File:pi3b~~

'''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.'''== Android Function Adaptation ==

~~[[File:pi3b-img375.png~~{|~~207x193px]]~~ ~~<ol start~~class="3wikitable" style="~~list-style~~width:800px;text-~~type~~align: ~~decimal~~center;">~~<li>Short press the switch button on the development board after shutting down to start up~~|-|'''Functions'''|'''Android 11'''|-|'''USB2.~~</li></ol>~~0x3'''|'''OK'''~~[[File:pi3b~~|-~~img374~~|'''USB3.~~png~~0x1'''|~~294x80px]]~~'''OK'''|-~~<ol start="4" style="list~~|'''M.2 NVMe SSD boot'''|'''OK'''|-~~style~~|'''WIFI'''|'''OK'''|-~~type: decimal;"><li>The command to restart the Linux system is</li></ol>~~|'''Bluetooth'''|'''OK'''|-|'''GPIO（40pin）'''~~orangepi@orangepi:~$~~ |'''~~sudo~~OK''' |-|'''~~reboot~~UART（40pin）'''|'''OK'''~~~~|'''PWM（40pin）'''= |'''OK'''~~Linux SDK——orangepi~~|-~~build instructions~~|'''PWM fan interface''' =|'''OK'''~~== Compilation system requirements ==~~|'''EMMC'''|'''OK'''|-|'''TF card boot'''|'''We can cross-compile the Linux image of the development board on the x64 computer, or compile the Linux image of the development board on the Ubuntu22.04 system of the development board, please choose one according to your preference.OK'''|-|'''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.HDMI video'''|'''OK'''~~=== Compile with the Ubuntu22.04 system of the development board ===~~|'''HDMI Audio'''|'''OK'''|-~~# The Linux SDK, namely~~ |'''~~orangepi-build~~LCD'''~~, supports running on the~~ |'''~~Ubuntu 22.04~~OK''' ~~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 |'''eDP display '''~~22.04~~|'''OK'''~~, it means that the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operations.~~|-|'''Gigabit network port'''~~orangepi@orangepi:~$~~ |'''OK'''~~lsb_release~~ |-a|'''Network port status indicator'''|'''OK'''~~No LSB modules are available.~~|-|'''Headphone playback'''|'''OK'''~~Distributor ID: Ubuntu~~|-|'''Headphone recording'''~~Description: Ubuntu 22.04.1 LTS~~|'''OK'''|-~~Release:~~ |'''~~22.04~~LED Light'''|'''OK'''~~Codename: jammy~~|-|'''GPU'''|'''OK'''~~<ol start="2" style="list~~|-~~style~~|'''NPU'''|'''OK'''|-~~type: decimal;"><li>~~|'''VPU'''|'''OK'''~~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.~~|'''RTC'''|'''OK'''~~</li></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 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.== WIFI connection test method ==

~~test@test:~$~~ # First click enter '''~~lsb_release -a~~Setting'''

~~No LSB modules are available~~::[[File:pi3b-img396.png]]

~~Distributor ID~~<ol start="2" style="list-style-type: ~~Ubuntu~~decimal;"><li>Then select '''Network & internet'''</li>

~~Description~~[[File: ~~Ubuntu 22~~pi3b-img397.~~04 LTS~~png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then select '''Wi-Fi'''</li>

~~Release~~[[File: pi3b-img398.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then turn on the '''~~22.04~~Wi-Fi'''switch</li>

~~Codename~~[[File: ~~jammy~~pi3b-img399.png]]</ol><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>

[[File:pi3b-img400.png]]</ol><ol start="26" style="list-style-type: decimal;"><li>~~If~~ Then select the ~~computer is installed with Windows system and there is no computer with Ubuntu 22.04 installed,~~ Wi-Fi you ~~can consider using '''VirtualBox''' or '''VMware'''~~ want to ~~install an Ubuntu 22.04 virtual machine in the Windows system. But please be careful not~~ connect to ~~compile orangepi-build on the WSL virtual machine~~, ~~because orangepi-build has not been tested in~~ and the ~~WSL virtual machine, so it cannot be guaranteed that orangepi-build can be used normally~~ password input interface shown in ~~WSL.</li><li>The download address of~~ the ~~installation image of Ubuntu 22.04 '''amd64''' version is:~~figure below will pop up</li~~></ol~~>

[~~https~~[File:~~//repo.huaweicloud.com/ubuntu~~pi3b-~~releases/21~~img401.04png]]</~~ubuntu~~ol><ol start="7" style="list-~~21.04~~style-~~desktop~~type: decimal;"><li>Then use the keyboard to enter the password corresponding to Wi-~~amd64.iso '''https://mirrors.tuna.tsinghua.edu.cn/ubuntu~~Fi, and then use the mouse to click the Enter button in the virtual keyboard to start connecting to Wi-~~releases~~Fi</~~22.04/ubuntu-22.04-desktop-amd64.iso''']~~li>

Or[[File:pi3b-img402.png]]</ol><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>

~~'''https~~[[File:~~//repo.huaweicloud~~pi3b-img403.~~com~~png]]</~~ubuntu~~ol>

~~<ol start~~=~~"4" style~~=~~"list~~How to use Wi-~~style-type: decimal;">~~<li>After installing Ubuntu 22.04 on the computer or virtual machine, please set the software source of Ubuntu 22.04 to Tsinghua source, otherwise it is easy to make mistakes due to network reasons when installing the software later~~<ol style~~Fi hotspot ==~~"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://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/~~# First, please make sure that the Ethernet port is connected to the network cable and can access the Internet normally# Then select '''Settings'''

~~<ol start="2" style="list-style-type~~: ~~lower~~:[[File:pi3b-~~alpha;"><li>Note that the Ubuntu version needs to be switched to 22~~img396.~~04</li></ol>~~png]]

~~[[File~~<ol start="3" style="list-style-type:~~pi3b-img376.png|576x241px]]~~decimal;"><li>Then select '''Network & internet'''</li>

[[File:pi3b-img397.png]]</ol><ol start="34" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The content of the~~ Then select '''~~/etc/apt/sources.list~~Hotspot & tethering''' ~~file that needs to be replaced is~~</li~~></ol~~>

~~test@test~~[[File:~$ pi3b-img404.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then select '''~~sudo mv /etc/apt/sources.list /etc/apt/sources.list.bak~~Wi-Fi hotspot'''</li>

~~test@test~~[[File:~$ pi3b-img405.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then turn on the '''~~sudo vim /etc/apt/sources.list~~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>

~~# By default~~[[File:pi3b-img406.png]]</ol><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 ~~source image is commented~~ 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 ~~improve~~ the ~~speed of apt update~~hotspot, ~~you~~ and the password can ~~uncomment it yourself if necessary~~be seen under the '''Hotspot password''' in the above picture</li>

~~deb https~~[[File:pi3b-img407.png]]</~~/mirrors~~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).~~tuna~~At this point, you can open a webpage on your mobile phone to see if you can access the Internet.~~tsinghua~~If you can open the webpage normally, it means that the '''WI-FI Hotspot''' of the development board can be used normally.~~edu.cn/ubuntu~~</ ~~jammy main restricted universe multiverse~~li>

~~# deb~~[[File:pi3b-~~src https://mirrors~~img408.~~tuna.tsinghua.edu.cn~~png]]</~~ubuntu~~ol></ ~~jammy main restricted universe multiverse~~span>

~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse~~== Bluetooth test method == # First click enter '''Setting'''

~~# deb~~::[[File:pi3b-~~src https://mirrors.tuna.tsinghua.edu~~img396.~~cn/ubuntu/ jammy-updates main restricted universe multiverse~~png]]

~~deb https~~<ol start="2" style="list-style-type:decimal;"><li>Then select '''Connected devices'''</~~/mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse~~li>

~~# deb~~[[File:pi3b-~~src https://mirrors~~img409.~~tuna.tsinghua.edu.cn~~png]]</~~ubuntu~~ol><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</ ~~jammy-backports main restricted universe multiverse~~li>

~~deb https~~[[File:~~//mirrors.tuna.tsinghua.edu~~pi3b-img410.cnpng]]</~~ubuntu~~ol><ol start="4" style="list-style-type: decimal;"><li>The searched Bluetooth devices will be displayed under '''Available devices'''</ ~~jammy-security main restricted universe multiverse~~li>

~~# deb~~[[File:pi3b-img411.png]]</ol><ol start="5" style="list-~~src https~~style-type:~~//mirrors.tuna.tsinghua.edu~~decimal;"><li>Then click the Bluetooth device you want to connect to start pairing.cnWhen the following interface pops up, please use the mouse to select the '''Pair''' option</~~ubuntu/ jammy-security main restricted universe multiverse~~li>

~~# Pre~~[[File:pi3b-~~release software source~~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 on the mobile phone. After clicking the pairing button on the mobile phone, ~~not recommended to enable~~the pairing process will start</li>

~~# deb https~~[[File:~~//mirrors.tuna.tsinghua.edu~~pi3b-img413.cnpng]]</~~ubuntu~~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</ ~~jammy-proposed main restricted universe multiverse~~li>

~~# deb~~[[File:pi3b-img414.png]]</ol><ol start="8" style="list-~~src https~~style-type:~~//mirrors~~decimal;"><li>At this time, you can use the Bluetooth of your mobile phone to send a picture to the development board.~~tuna~~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.~~tsinghua.edu.cn~~</~~ubuntu/ jammy-proposed main restricted universe multiverse~~li>

[[File:pi3b-img415.png]]</ol><ol start="49" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~After~~ You can open the '''Download''' directory in the ~~replacement, you need~~ file manager to ~~update~~ view the pictures received by the Android system Bluetooth of the ~~package information and make sure there is no error~~development board</li~~></ol~~>

~~test@test~~[[File:~~~$ '''sudo apt update'''~~pi3b-img416.png]]</ol>

~~<ol start~~="= How to use Raspberry Pi 5~~" style~~-inch screen ==~~"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>

~~~~| <~~/span~~big>~~== Get~~ '''Please make sure that the image used is the ~~source code~~ following two versions of ~~Linux sdk ==~~the image:'''

~~=== Download orangepi-build from github ===~~'''OrangePi3B_RK3566_Android11_lcd_v1.x.x.img'''

~~# The Linux sdk actually refers to the code of orangepi~~'''OrangePi3B_RK3566_Android11_spi-~~build~~nvme_lcd_v1. ~~orangepi-build is modified based on the armbian build system~~x. ~~Using orangepi-build, multiple versions of Linux images can be compiled~~x. ~~First download the code of orangepi-build, the command is as follows:~~img'''</big>|}

~~test@test:~$~~ # The screen needs to be assembled first, please refer to [[Orange Pi 3B#Use of the Raspberry PI's 5-inch screen|''~~sudo apt~~'the assembly method of the Raspberry Pi 5-~~get update~~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

~~test@test~~:~~~$ '''sudo apt-get install~~ :[[File:pi3b-~~y git'''~~img417.png]]

~~test@test:~$ '''git clone https://github.com/orangepi~~

'''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.'''== 40pin interface GPIO, UART, SPI and PWM test ==

<~~div class~~span id="~~figure~~pin-gpio-port-test-2">=== 40pin GPIO port test ===

~~[[File:pi3b-img377.png|576x298px|图片6]]~~# First click on the wiringOP icon to open the wiringOP APP

~~</div>'''Downloading the orangepi~~::[[File:pi3b-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 accountimg418.~~'''~~png]]

<li>The ~~u-boot~~ main interface of wiringOP APP is displayed as shown in the figure below, and ~~Linux kernel versions currently used by~~ then click the '''GPIO_TEST''' button to open the ~~development board are as follows~~GPIO test interface</li~~></ol~~>

~~{| class~~[[File:pi3b-img419.png]]</ol><ol start="~~wikitable~~3" style="|list-style-type: decimal;">|<li>The GPIO test interface is shown in the figure below. The two rows of '''~~branch~~CheckBox'''|buttons on the left are in one-to-one correspondence with the 40pin pins. When the '''~~u-boot version~~CheckBox'''|button is checked, the corresponding GPIO pin will be set to '''~~Linux Kernel version~~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 '''~~legacy~~GPIO READALL'''|button is pressed, information such as wPi number, GPIO mode, and pin level can be obtained; when the '''~~u-boot 2017.09~~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><ol start="4" style="list-style-type: decimal;"><li>Then click the '''~~Linux5.10~~GPIO READALL'''|}button, the output information is as shown in the figure below:</li>

[[File:pi3b-img421.png]]</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 '''CheckBox'''~~The branch mentioned here~~ button corresponding to pin 7. When the button is ~~not the same thing as~~ selected, pin 7 will be set to high level. After setting, you can use a multimeter to measure the ~~branch~~ voltage value of the ~~orangepi-build source code, please do not confuse~~ pin. If it~~. This branch~~ is ~~mainly used to distinguish different kernel source code versions~~3.~~'''~~3v, it means setting high level success</li>

[[File:pi3b-img422.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''~~Currently~~' button, you can see that the ~~Linux5.10 bsp kernel provided by RK~~ current pin 7 mode is ~~defined as the legacy branch. If the mainline kernel is supported in the future, a current branch will be added.~~'''OUT''', and the pin level is high</li>

~~<ol start="3" style="list~~[[File:pi3b-~~style-type: decimal;">~~img423.png]]~~<li>orangepi-build will contain the following files and folders after downloading~~</pol><ol start="7" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~'''build.sh''': Compile~~ Click the ~~startup script</li><li>~~'''~~external~~CheckBox'''~~: Contains~~ button in the ~~configuration files needed~~ figure below again to ~~compile~~ cancel the ~~image~~check status. Pin 7 will be set to low level. After setting, ~~specific scripts, and~~ you can use a multimeter to measure the ~~source code~~ voltage value of ~~some programs, etc~~the pin.~~</li><li>~~If it is '''~~LICENSE~~0v'''~~: GPL 2 license file</li><li>README~~, it means that the low level is set successfully.~~md: orangepi-build documentation~~</li>~~<li>'''scripts''': General script for compiling Linux images</li></ol></li></ol~~>

~~test@test~~[[File:~pi3b-img424.png]]</~~orangepi~~ol><ol start="8" style="list-style-~~build$~~ type: decimal;"><li>Then click the '''lsGPIO READALL'''button, you can see that the current pin 7 mode is OUT, and the pin level is low</li>

~~'''build~~[[File:pi3b-img425.~~sh external LICENSE''' README.md '''scripts'''~~png]]</ol>

'''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.'''=== 40pin UART test ===

~~<~~40pin is shown in the figure below, and the corresponding device nodes are '''/dev/ttyS7''' and '''/~~span>=== Download the cross-compilation toolchain ===~~dev/ttyS9''' respectively

~~'''The cross~~::[[File:pi3b-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 folderimg269.~~'''~~png]]

~~# When orangepi~~<ol start="2" style="list-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 crossstyle-~~compilation toolchain in '''toolchains''' exists , if it does not exist,~~ type: decimal;"><li>First click on the ~~download will be restarted, if it exists, it will be used directly, and~~ wiringOP icon to open the ~~download will not be repeated.~~wiringOP APP</li>

[[File:pi3b-img418.png]]<~~div class~~/ol><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>

[[File:pi3b-~~img378~~img426.png~~|575x278px|选区_396~~]]</ol><ol start="4" style="list-style-type: decimal;"><li>The serial port test interface of the APP is shown in the figure below</li>

[[File:pi3b-img427.png]]</~~div~~ol><ol start="25" style="list-style-type: decimal;"><li>~~The image URL~~ Take the test of '''UART7''' as an example below, select the ~~cross-compilation toolchain~~ '''/dev/ttyS7''' node in the selection box, enter the baud rate you want to set in ~~China~~ 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 ~~open source software image site of Tsinghua University~~'''CLOSE''' button and '''SEND''' button become selectable</li~~></ol~~>

~~https~~[[File:~~//mirrors~~pi3b-img428.~~tuna.tsinghua.edu.cn~~png]]</~~armbian~~ol><ol start="6" style="list-style-~~releases/_toolchain~~type: decimal;"><li>Then use Dupont wire to short the RXD and TXD pins of uart7</li>

[[File:pi3b-img429.png]]</ol><ol start="37" style="list-style-type: decimal;"><li>~~After~~ Then you can enter a character in the send edit box below, and click the '''~~toolchains~~SEND''' ~~is downloaded, it will contain multiple versions of cross-compilation toolchains, and the development board will only use two of them~~button to start sending</li~~></ol~~>

~~test@test~~[[File:~pi3b-img430.png]]</~~orangepi~~ol><ol start="8" style="list-~~build$ '''ls toolchains~~style-type: decimal;"><li>If everything is normal, the received string will be displayed in the receiving box</~~'''~~li>

~~gcc~~[[File:pi3b-~~arm-11~~img431.2png]]</ol>

~~gcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf~~=== 40pin SPI test ===

~~gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu~~# According to the schematic diagram of the 40pin interface, the spi available for Orange Pi 3B is spi3

~~gcc~~::[[File:pi3b-~~arm-9.2-2019~~img264.~~12-x86_64-arm-none-linux-gnueabihf~~png]]

~~gcc~~<ol start="2" style="list-~~linaro~~style-4type: decimal;"><li>Here, the SPI interface is tested through the w25q64 module.~~9.4-2017.01-x86_64_arm-linux-gnueabi~~First, the w25q64 device is connected to the SPI3 interface</li>

~~gcc~~[[File:pi3b-~~linaro-5~~img432.~~5.0-2017.10-x86_64_arm~~png]]</ol><ol start="3" style="list-~~linux~~style-~~gnueabihf~~type: decimal;"><li>Then click the wiringOP icon to open the wiringOP APP</li>

~~gcc~~[[File:pi3b-~~linaro-7~~img418.png]]</ol><ol start="4~~.1-2019.02-x86_64_aarch64~~" style="list-~~linux~~style-~~gnu~~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>

~~gcc~~[[File:pi3b-~~linaro-7~~img433.~~4.1-2019.02-x86_64_arm~~png]]</ol><ol start="5" style="list-~~linux~~style-~~gnueabi~~type: decimal;"><li>Then click the '''OPEN''' button to initialize the SPI</li>

~~gcc~~[[File:pi3b-~~linaro-aarch64-none-elf~~img434.png]]</ol><ol start="6" style="list-~~4.8~~style-~~2013.11_linux~~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>

~~gcc~~[[File:pi3b-~~linaro-arm-linux-gnueabihf~~img435.png]]</ol><ol start="7" style="list-~~4.8~~style-~~2014.04_linux~~type: decimal;"><li>Finally, the APP will display the read ID information</li>

~~gcc~~[[File:pi3b-~~linaro-arm-none-eabi-4~~img436.png]]</ol><ol start="8" style="list-~~2014.04_linux~~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 start="4" style="list~~[[File:pi3b-~~style-type: decimal;">~~img437.png]]~~<li>The cross-compilation toolchain used to compile the Linux kernel source code is~~</pol><~~ol style~~span id="~~list~~pin-~~style~~pwm-~~type: lower-alpha;~~test">~~<li>Linux5.10~~</~~li></ol></li></ol~~span>

~~'''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''~~=== 40pin PWM test ===

~~<ol start="5" style="list-style-type: decimal;"><li>The cross-compilation tool chain used to compile~~ # Android enables '''PWM11''' by default, and the ~~u-boot source code~~ corresponding pin is~~<ol style="list-style-type: lower-alpha;"><li>v2017.09</li></ol></li></ol>~~located at 40pin as shown in the figure below

~~'''gcc~~::[[File:pi3b-~~linaro-7.4.1-2019~~img438.~~02-x86_64_aarch64-linux-gnu'''~~png]]

<~~span id~~ol start="~~orangepi~~2" style="list-~~build~~style-~~complete-directory-structure-description~~type: decimal;"><li>First click on the wiringOP icon to open the wiringOP APP</~~span~~li>~~=== orangepi-build complete directory structure description ===~~

~~<ol style="list-style-type~~[[File: ~~decimal;"><li>The orangepi~~pi3b-~~build repository does not contain the source code of the Linux kernel, u-boot, and cross-compilation toolchain after downloading~~img418. ~~The source code of the Linux kernel and u-boot is stored in an independent git repository~~png]]</pol><ol start="3" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The git repository where~~ Then click the '''PWM_TEST''' button on the main interface of wiringOP to enter the ~~Linux kernel source code is stored is as follows:~~PWM test interface</li~~></ol></li></ol~~>

~~'''https~~[[File:~~//github~~pi3b-img439.~~com~~png]]</~~orangepi~~ol><ol start="4" style="list-~~xunlong/linux~~style-~~orangepi/tree/orange~~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-~~pi-5~~down option to select other pwmchips until '''febf0030.~~10-rk35xx~~pwm'''is displayed on the right</li>

[[File:pi3b-img440.png]]</ol><ol start="25" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The git warehouse where~~ When the ~~b.u~~drop-~~boot source code~~ down option selects '''pwmchip3''', the corresponding base address of PWM11 is ~~stored is as follows:~~'''fe6f0030''' on the right</li~~></ol~~>

~~'''https~~[[File:~~//github~~pi3b-img441.~~com~~png]]</~~orangepi~~ol><ol start="6" style="list-~~xunlong/u~~style-~~boot-orangepi/tree/v2017.09-rk3588~~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>

[[File:pi3b-img442.png]]</ol><ol start="27" style="list-style-type: decimal;"><li>~~When orangepi-build runs for~~ Then drag the ~~first time, it will download~~ drag bar below to change the ~~cross-compilation toolchain~~PWM duty cycle, ~~u-boot~~ and ~~Linux kernel source code. After successfully compiling a Linux image,~~ then check Enable to output the ~~files and folders that can be seen in orangepi-build are:~~PWM waveform</pli>~~a~~[[File:pi3b-img443. ~~'''build.sh''': compile startup script~~png]]</pol><~~p>b. '''external'''~~ol start="8" style="list-style-type: 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 external</pdecimal;"><pli>~~c. '''kernel''': stores~~ Then use an oscilloscope to measure the ~~source code of the Linux kernel, and the folder named orange-pi-5~~No.~~10-rk35xx stores the kernel source code of~~ 32 pin in the ~~legacy branch~~ 40pin of the ~~RK3588/RK3588S/RK3566 series~~ development ~~boards. Please do not manually name the folder name of the kernel source code Modify, if modified~~board, and you can see the ~~kernel source code will be re-downloaded when the compilation system is running~~following waveform~~d. '''LICENSE''': GPL 2 license file</p~~li>~~e. '''README'''.md: orangepi-build documentationf. '''output'''~~[[File: ~~Store compiled deb packages such as u~~pi3b-~~boot and Linux, compilation logs, and compiled images and other filesg~~img444. ~~'''scripts''': general scripts for compiling Linux images~~png]]~~h. '''toolchains''': store cross-compilation toolchain~~</pol><~~p>i. '''u~~span id="how-~~boot''': stores the source code of u~~to-~~boot, the folder named v2017.09~~use-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 runningadb"></pspan>~~j. '''userpatches''': Store configuration files needed~~ == How to ~~compile scripts</li></ol>~~use ADB ==

~~test@test:~~~</~~orangepi-build$ '''ls'''~~span>=== Use network connection adb debugging ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~build.sh external kernel LICENSE output''' README~~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.~~md '''scripts toolchains u-boot userpatches~~'''</big>|}

~~== Compile u-boot ==~~# Make sure that the '''service.adb.tcp.port''' of the Android system is set to port number 5555

::{| class="wikitable" style="width:800px;" |-| console:/ # ~~Run the build~~'''getprop | grep "adb.~~sh script, remember to add sudo permission~~tcp"'''

~~test@test~~[service.adb.tcp.port]:~~~/orangepi-build$~~ ['''~~sudo ./build.sh~~5555''']|}

<li>~~Select~~ If '''~~U-boot package~~service.adb.tcp.port'''~~，then enter~~is not set, you can use the following command to set the port number of network adb</li~~></ol~~>

~~<div~~ {| class="~~figure~~wikitable">style="width:800px;" |-| console:/ # '''setprop service.adb.tcp.port 5555'''

~~[[File~~console:~~pi3b-img379.png|576x132px|选区_238]]~~/ # '''stop adbd'''

console:/ # '''start adbd'''|}</~~div~~ol>

<li>~~Then select the model of the development board~~Install adb tool on Ubuntu PC</li~~></ol~~>

~~<div~~ {| class="~~figure~~wikitable">style="width:800px;" |-| test@test:~$ '''sudo apt update'''

~~[[File~~test@test:~~pi3b~~~$ '''sudo apt install -~~img380.png|576x197px~~y adb'''|}~~4$_5F06}}0R4GU8]OVO}4E]]~~ </~~div~~ol>

<li~~><p~~>Then ~~it will start to compile u-boot, and some information prompted during compilation is explained as follows~~connect network adb on Ubuntu PC~~<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~~{| class="2wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>~~|-| test@test:~$ '''adb connect 192.168.1.xxx''' '''(The ~~version~~ IP address needs to be changed to the IP address of the ~~cross-compilation toolchain</li></ol>~~development board)'''

~~[ o.k. ] Compiler version [ '''aarch64-linux-gnu-gcc 7.4.1''' ]~~* daemon not running; starting now at tcp:5037

<~~ol start="3" style="list-style-type: lower-alpha;"><li>Path to the generated u-boot deb package</li~~p>* daemon started successfully</olp>

~~[ o~~connected to 192.k168. ~~] Target directory [ '''orangepi-build/output/debs/u-boot''' ]~~1.xxx:5555

~~<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 [~~ test@test:~$ '''~~linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb~~adb devices''' ]

~~<ol start="5" style="list-style-type: lower-alpha;"><li>Compilation time</li></ol>~~List of devices attached

~~[ o~~192.k168. ~~] Runtime [ '''~~1 ~~min''' ]~~.xxx:5555 device|}</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</li>

~~<ol start~~{| class="6wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<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>~~| test@test:~$ '''adb shell'''

~~[ o.k. ] Repeat Build Options [ '''sudo .~~console:/~~build.sh BOARD~~#|}</ol>

~~<ol start~~=~~"5" style~~'''Appendix''' =~~"list-style-type: decimal;"><li>View the u-boot deb package generated by compilation</li></ol>~~

~~test@test:~/orangepi~~</~~'''~~span>== User Manual Update History ==

~~linux~~{| class="wikitable" style="width:800px;text-ualign: center;"|-~~boot~~|'''Version'''|'''Date'''|'''Update Notes'''|-~~legacy~~|v0.1|2023-~~orangepi3b_1.0.0_arm64.deb~~07-19|initial version|}

<~~ol start~~span id="~~6" style="list~~image-~~style~~update-~~type: decimal;~~history">~~<li>The files contained in the generated u-boot deb package are as follows~~</pspan>~~<ol style~~=~~"list-style-type: lower-alpha;"><li>Use the following command to decompress the deb package</li></ol></li></ol>~~= Image Update History ==

~~test@test~~{| class="wikitable" style="width:~~~/orangepi~~800px;"|-~~build$~~ | style="text-align: center;" | '''Date'~~cd output/debs/u~~''| style="text-~~boot~~align: center;" | '''Update Notes'''|-| style="text-align: center;" | 2023-07-19|Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160.7z

~~test@test:~/orangepi_build/output/debs/u-boot$ $ '''dpkg -x''' \~~Orangepi3b_1.0.0_ubuntu_jammy_desktop_xfce_linux5.10.160.7z

~~'''linux-u-boot-legacy-orangepi3b_1~~Orangepi3b_1.0.~~0_arm64~~0_ubuntu_focal_desktop_xfce_linux5.~~deb~~ 10. ~~(Note that there is a "~~160.~~" at the end of the command)'''~~7z

~~test@test:~/orangepi_build/output/debs/u-boot$ '''ls'''~~OrangePi3B_RK3566_Android11_v1.0.0.tar.gz

~~linux-u-boot-legacy-orangepi3b_1~~OrangePi3B_RK3566_Android11_lcd_v1.0.~~0_arm64~~0.tar.~~deb '''usr'''~~gz

~~<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~~OrangePi3B_RK3566_Android11_spi-~~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~~nvme_v1.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-rk356x_1.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 ^β