Changes

← Older edit

Orange Pi 3B

32,202 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>|}

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

::[[File:pi3b-img7.png]]

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

[[File:pi3b-img8.png]]

</ol>

<li>Display with HDMI interface</li~~></ol~~>

[[File:pi3b-img9.png]]

</ol>

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

[[File:pi3b-img10.png]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note, if you want to connect a 4K monitor, please make sure that the HDMI cable supports 4K video output.'''</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>~~</ol>~~ ~~[[File:pi3b-img11.png]]~~

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

</ol>

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

[[File:pi3b-img12.png]]

</ol>

<li>USB camera</li~~></ol~~>

[[File:pi3b-img13.png]]

</ol>

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

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The fan on the development board can adjust the speed and switch through PWM.'''</big>|}

[[File:pi3b-img14.png]]

</ol>

<li>100M or 1000M network cable, used to connect the development board to the Internet</li~~></ol~~>

[[File:pi3b-img15.png]]

</ol>

<li>USB2.0 male-to-male data cable, used to burn images to eMMC, NVMe SSD and other functions</li~~></ol~~>

[[File:pi3b-img16.png]]

</div></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>~~</ol>~~ ~~[[File:pi3b-img17.png]] [[File:pi3b-img18.png]]~~

[[File:pi3b-img17.png|400px]] [[File:pi3b-img18.png|400px]]

</ol>

<li>A personal computer with Ubuntu and Windows operating systems installed</li~~></ol~~>

{| class="wikitable" style="width:800px;text-align: center;"

|-

|-

|}

</ol>

~~~~

== Download the image of the development board and related materials ==

# The website for downloading the English version of materials is:

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

|-

|

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

|}

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

</div>

== Method of burning Linux image to TF card based on Windows PC ==

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

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

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

# Download the Linux operating system image file compression package that you want to burn from the [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/~~index~~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 above 2GB.

# Then download the burning software of Linux image—'''balenaEtcher''', the download address is:

::{| class="wikitable" style="width:800px;" |-| '''https://www.balena.io/etcher/'''|}

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

[[File:pi3b-img20.png]]

</ol>

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

[[File:pi3b-img21.png]]

</ol>

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

[[File:pi3b-img22.png]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''When opening balenaEtcher, if the following error is prompted:'''</big>

[[File:pi3b-img23.png|~~209x164px~~center]]

<big>'''Please select balenaEtcher, right-click, and select Run as administrator.''' ~~[[File:pi3b-img24.png|273x37px]]~~</big>

[[File:pi3b-img24.png|center]]

|}

</ol>

<li>The specific steps to use balenaEtcher to burn the Linux image are as follows

<li>First select the path of the Linux image file to be burned</li>

<li>Then select the drive letter of the TF card</li>

<li>Finally click Flash to start burning the Linux image to the TF card</li~~></ol></li></ol~~>

[[File:pi3b-img25.png~~|501x281px|03~~]]

</div></ol></li></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>~~</ol>~~ ~~[[File:pi3b-img26.png|428x268px]]~~

[[File:pi3b-img26.png]]

</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>~~</ol>~~ ~~[[File:pi3b-img27.png|427x267px]]~~

[[File:pi3b-img27.png]]

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

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

</div></ol>

=== How to use RKDevTool to burn Linux image to TF card ===

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

</div>

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

<li>Then download the Rockchip driver '''DriverAssitant_v5.12.zip''' and '''MiniLoader''' and the burning tool '''RKDevTool_Release_v3.15.zip''' from the [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/~~index~~computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''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~~|283x90px|6d1c77df7eeb7e491e5f79e8d85cbdc~~]]

</div></ol>

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

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

</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/~~serviceAndSupport~~hardWare/~~index~~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|464x136px]]~~

[[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|245x129px]]~~

[[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|254x132px]]~~

[[File:pi3b-img33.png]]

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

[[File:pi3b-img34.png]]

</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>~~</ol>~~ ~~[[File:pi3b-img35.png|402x189px]]~~

[[File:pi3b-img35.png]]

</ol>

<li>Then start burning the Linux image to the TF card

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

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

</div></ol>

<li>Make sure the TF card slot is not inserted into the TF card</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~~>

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

[[File:pi3b-img39.png]]

</ol>

<li>At this time, please insert the TF card into the TF card slot</li>

<li>Then place the mouse cursor in the area below</li~~></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>~~</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]]~~

[[File:pi3b-img42.png]]

</ol>

<li>Then select the '''rk3588_Linux_tfcard.cfg''' configuration file in the '''MiniLoader''' folder downloaded earlier, and click '''Open'''</li>~~</ol>~~ ~~[[File:pi3b-img43.png|457x215px]]~~

[[File:pi3b-img43.png]]

</ol>

<li>Then click '''OK'''</li>~~</ol>~~ ~~[[File:pi3b-img44.png|483x227px]]~~

[[File:pi3b-img44.png]]

</ol>

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

[[File:pi3b-img45.png]]

</ol>

<li>Then select '''rk3566_MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and click to '''open'''</li~~></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>~~</ol>~~ ~~[[File:pi3b-img47.png|493x232px]]~~

[[File:pi3b-img47.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 by address''' option</li>~~</ol>~~ ~~[[File:pi3b-img49.png|497x234px]]~~

[[File:pi3b-img49.png]]

</ol>

<li>Click the execute button again to start burning the Linux image to the tf card of the development board</li>~~</ol>~~ ~~[[File:pi3b-img50.png|497x233px]]~~

[[File:pi3b-img50.png]]

</ol>

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

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

</div></ol>

<li>After burning the Linux image to the TF card, the Linux system will start automatically.</li></ol>

</li></ol>

~~~~

=== How to use Win32Diskimager to burn Linux image ===

<li>Then format the TF card

<li>'''SD Card Formatter''' can be used to format the TF card. The download address is:</li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-| '''https://www.sdcard.org/downloads/formatter/eula_windows/SDCardFormatterv5_WinEN.zip'''|}</ol>

<li>After downloading, unzip and install directly, and then open the software</li>

<li>If only a TF card is inserted into the computer, the drive letter of the TF card will be displayed in the "'''Select card'''" column. If multiple USB storage devices are inserted into the computer, you can select the corresponding drive letter of the TF card through the drop-down box</li~~></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>~~</ol>~~ ~~[[File:pi3b-img53.png|304x147px]]~~

[[File:pi3b-img53.png]]

</ol>

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

~~<blockquote>~~[[File:pi3b-img54.png~~|186x149px~~]]</~~blockquote~~ol></li></ol>

<li>Download the Linux operating system image file compression package that you want to burn from the [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/~~index~~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>Use '''Win32Diskimager''' to burn the Linux image to the TF card

<li>The download page of Win32Diskimager is</li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-| '''http://sourceforge.net/projects/win32diskimager/files/Archive/'''|}</ol>

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

<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) First select the path of the image file</li><li>b) Then confirm that the drive letter of the TF card is consistent with that displayed in the "'''Device'''" column</li><li>c) Finally click "'''Write'''" to start burning</li~~></ol></li></ol~~>

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

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

<li>After the image writing is completed, click the "'''Exit'''" button to exit, and then you can pull out the TF card and insert it into the development board to start</li></ol>

</li></ol>

~~~~

== Method of burning Linux image to TF card based on Ubuntu PC ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the Linux image mentioned here specifically refers to the images of Linux distributions such as Debian and Ubuntu downloaded from the [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/computerAndMicrocontrollers/service-and-support/~~index~~Orange-Pi-3B.html Orange Pi data download page], and the Ubuntu PC refers to the personal computer with the Ubuntu system installed.'''</big>|}

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

# Download the balenaEtcher software, the download address is

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

|-

|

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

|}

<li>After entering the balenaEtcher download page, click the green download button to jump to the place where the software is downloaded</li>~~</ol>~~ ~~[[File:pi3b-img20.png|434x208px]]~~

[[File:pi3b-img20.png]]

</ol>

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

[[File:pi3b-img56.png~~|430x163px~~]]</ol><ol start="6" style="list-style-type: decimal;"><li>Download the Linux operating system image file compression package that you want to burn from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-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>

~~<ol start="6" style="list-style-type: decimal;"><li>Download~~ The decompression command for the ~~Linux operating system image file compression~~ compressed package that you want to burn from the [http://www.orangepi.org/html/serviceAndSupport/index.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~~ in 7z is ~~generally more than 2GB</li></ol>~~as follows

~~<blockquote>The decompression command for the compressed package ending in 7z is as follows~~{| class="wikitable" style="width:800px;" ~~</blockquote>~~|-|

test@test:~$ '''7z x Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_Linux5.10.160.7z'''

test@test:~$ '''ls Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_Linux5.10.160.*'''

Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_Linux5.10.160.7z Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_Linux5.10.160.sha #checksum file

Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_Linux5.10.160.img #mirror file

|}</ol>

<li>After decompressing the image, you can first use the '''sha256sum -c *.sha''' command to calculate whether the checksum is correct. If the prompt is successful, it means that the downloaded image is '''correct''', and you can safely burn it to the TF card. If it prompts that the '''checksum does not match''', it means There is a problem with the downloaded image, please try to download again</li~~></ol~~>

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

|-

|

test@test:~$ '''sha256sum -c *.sha'''

Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_Linux5.10.160.img: OK

|}</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>~~</ol>~~ ~~[[File:pi3b-img57.png|423x251px]]~~

[[File:pi3b-img57.png]]

</ol>

<li>The specific steps of using balenaEtcher to burn the Linux image are as follows

<li>First select the path of the Linux image file to be burned</li>

<li>Then select the drive letter of the TF card</li>

<li>Finally, click Flash to start burning the Linux image to the TF card</li~~></ol></li></ol~~>

[[File:pi3b-img25.png~~|501x281px|03~~]]

</div></ol></li></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>~~</ol>~~ ~~[[File:pi3b-img58.png|429x184px]]~~

[[File:pi3b-img58.png]]

</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>~~</ol>~~ ~~[[File:pi3b-img59.png|436x190px]]~~

[[File:pi3b-img59.png]]

</ol>

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

[[File:pi3b-img60.png~~|435x257px~~]]</ol>

~~~~

== How to burn Linux image to eMMC ==

=== Using RKDevTool to burn the Linux image into eMMC ===

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

# The development board reserves the expansion interface of the eMMC module. Before burning the system to the eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The eMMC module and the method of plugging into the development board are as follows:

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

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

<li>You also 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 [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/~~index~~computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''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~~|360x115px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\6d1c77df7eeb7e491e5f79e8d85cbdc.png6d1c77df7eeb7e491e5f79e8d85cbdc~~]]

</div></ol>

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

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

</div>

{| 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/~~serviceAndSupport~~hardWare/~~index~~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|496x146px]]~~

[[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|284x149px]]~~

[[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|296x154px]]~~

[[File:pi3b-img33.png]]

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

[[File:pi3b-img34.png]]

</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>~~</ol>~~ ~~[[File:pi3b-img35.png|442x208px]]~~

[[File:pi3b-img35.png]]

</ol>

<li>Then start burning the Linux image into eMMC

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

[[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 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.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|460x216px]]~~

[[File:pi3b-img41.png]]

</ol>

<li>Then select the '''import configuration''' option</li>~~</ol>~~ ~~[[File:pi3b-img42.png|458x215px]]~~

[[File:pi3b-img42.png]]

</ol>

<li>Then select the '''rk3588_Linux_emmc.cfg''' configuration file in the '''MiniLoader''' folder downloaded earlier, and click '''Open'''</li>~~</ol>~~ ~~[[File:pi3b-img65.png|466x219px]]~~

[[File:pi3b-img65.png]]

</ol>

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

[[File:pi3b-img66.png]]

</ol>

<li>Then click the position shown in the figure below</li>~~</ol>~~ ~~[[File:pi3b-img67.png|462x217px]]~~

[[File:pi3b-img67.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-img69.png|459x216px]]~~

[[File:pi3b-img69.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 option to '''force writing by address'''</li>~~</ol>~~ ~~[[File:pi3b-img70.png|501x235px]]~~

[[File:pi3b-img70.png]]

</ol>

<li>Click the execute button again to start burning the Linux image to the eMMC of the development board</li>~~</ol>~~ ~~[[File:pi3b-img71.png|502x236px]]~~

[[File:pi3b-img71.png]]

</ol>

<li>The log displayed after burning the Linux image is shown in the figure below</li>~~</ol>~~ ~~[[File:pi3b-img72.png|500x235px]]~~

[[File:pi3b-img72.png]]

</ol>

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

'''Note, after burning the image into eMMC, if the test finds that it cannot be started, please clear the SPIFlash and try again. For the method of clearing SPIFlash, please refer to [[\l|the method of using RKDevTool to clear SPIFlash]].'''

~~~~

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

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the Linux image mentioned here specifically refers to the image of Linux distributions such as Debian, Ubuntu, OpenWRT or OPi OS Arch downloaded from the [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/computerAndMicrocontrollers/~~index~~service-and-support/Orange-Pi-3B.html Orange Pi data download page].'''</big>|}

# The development board reserves the expansion interface of the eMMC module. Before burning the system to the eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The eMMC module and the method of plugging into the development board are as follows:

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

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

<li>Using the dd command to burn the Linux image to eMMC needs to be completed with the help of a TF card, so first you need to burn the Linux image to the TF card, and then use the TF card to start the development board to enter the Linux system. For the method of burning the Linux image to the TF card, please refer to the instructions in the two sections of [[\lOrange Pi 3B#Method of burning Linux image to TF card based on Windows PC|'''the method of burning the Linux image to the TF card based on the Windows PC''']] and [[\lOrange Pi 3B#Method of burning Linux image to TF card based on Ubuntu PC|'''the method of burning the Linux image to the TF card based on the Ubuntu PC''']].</li><li>After using the TF card to start the Linux system, we first upload the decompressed Linux image file (Debian, Ubuntu image or OPi Arch image downloaded from the official website) to the TF card. For the method of uploading the Linux image file to the development board, please refer to the description in the section of [[\lOrange Pi 3B#The method of uploading files to the Linux system of the development board|'''the method of uploading files to the development board Linux system''']].</li><li>After uploading the image to the Linux system of the development board, we enter the storage path of the image file in the command line of the Linux system of the development board. For example, I store the Linux image of the development board in the '''/home/orangepi/Desktop''' directory Download it, and then enter the '''/home/orangepi/Desktop''' directory to see the uploaded image file.</li~~></ol~~>

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

|-

|

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

Orangepi3b_x.x.x_debian_bullseye_desktop_xfce_Linux5.10.160.img

|}

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

|-

|

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

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

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

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

|}

</ol>

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

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

|-

|

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

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

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

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

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

|}</ol>

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

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

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

|}

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

|-

|

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

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

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

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

|}

</ol>

</li></ol>

<li>After successfully burning the Linux image of the development board to the eMMC, you can use the '''poweroff''' command to shut down. Then please pull out the TF card, and then short press the power button to turn on, and then the Linux system in the eMMC will be started.</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <~~/ol~~big> '''Note, after burning the image into eMMC, if the test finds that it cannot be started, please clear the SPIFlash and try again. For the method of clearing SPIFlash, please refer to [[\lOrange Pi 3B#Using RKDevTool to clear SPIFlash|the method of using RKDevTool to clear SPIFlash]].'''</big>|}</ol>

~~~~

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

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

<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/~~serviceAndSupport~~hardWare/~~index~~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 style="list-style-type: lower-roman;"><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~~img42.png~~|462x217px~~]]</ol><ol start="9" style="list-style-type: lower-alpha;"><li>Then enter the '''MiniLoader''' folder downloaded earlier, then select the '''rk3588_Linux_pcie.cfg''' configuration file, and click '''Open'''</li>

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

~~orangepi@orangepi~~[[File:~~~/Desktop$ '''lspci'''~~pi3b-img99.png]]

~~00:00.0 PCI bridge: Fuzhou Rockchip Electronics Co., Ltd Device 3566 (rev 01)~~ ~~01:00.0 Non-Volatile memory controller: Realtek Semiconductor Co., Ltd. Device 5765 (rev 01)~~</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~~div class="figure">

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

</div></ol>

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

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

</div></ol>

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

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

</div></ol>

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

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

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

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

</div></ol>

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

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

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

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

</div></ol>

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

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

</div></ol>

<li>The display after burning is as follows:</li> [[File:pi3b-img111.png]]</ol><ol start="12" style="list-style-type: lower-alpha;"><li>Then you need to expand the capacity of the rootfs partition in the NVMe SSD. The steps are as follows:<ol style="list-style-type: none;"><li>a) Open '''GParted''' first, if the system does not have Gparted pre-installed, please use the apt command to install it{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt-get install -y gparted'''|}</li>

[[File:pi3b-~~img101~~img112.png~~|395x225px|IMG_256~~]]

</div></ol><ol start="92" style="list-style-type: ~~decimal~~none;"><li>~~The method~~ b) Then enter the password orangepi of ~~burning~~ the Linux system ~~in the TF card to the NVMe SSD (this method is equivalent to cloning the system in the TF card to the NVMe SSD)~~, and click '''Authenticate'''</li> [[File:pi3b-img113.png]]</pol><ol start="3" style="list-style-type: ~~lower-alpha~~none;"><li>~~First~~ c) Then click '''~~Clone drive~~Fix'''</li> [[File:pi3b-img114.png]]</ol></ol start="4" style="list-style-type: none;"><li>d) Then select NVMe SSD</olli>

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

</div></ol><ol start="25" style="list-style-type: ~~lower-alpha~~none;"><li>~~Then select the device name of the TF card '''/dev/mmcblk1'''~~e) The display interface after selecting NVMe SSD is as follows:</li~~></ol~~>

[[File:pi3b-~~img103~~img116.png~~|379x256px|IMG_256~~]]

</div></ol><ol start="36" style="list-style-type: ~~lower-alpha~~none;"><li>~~The interface after opening~~ f) Then select the '''/dev/nvme0n1p2''' partition, click the ~~TF card is as follows:~~right button again, and then select '''Resize/Move'''</li~~></ol~~>

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

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

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

[[File:pi3b-~~img94~~img119.png~~|379x171px|IMG_256~~]]</ol><ol style="list-style-type: none;"><li>i) Then click the green '''√''' in the position below</li>

[[File:pi3b-img120.png]]</~~div~~ol><ol start="510" style="list-style-type: ~~lower-alpha~~none;"><li>j) Then click '''~~Show 2 hidden~~Apply''' ~~to open more options for storage devices~~</li~~></ol~~>

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

[[File:pi3b-~~img95~~img122.png~~|385x155px|IMG_256~~]]</ol></li></ol><ol start="13" style="list-style-type: lower-alpha;"><li>At this point, you can use the '''sudo 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></ol></li></ol><ol start="10" style="list-style-type: decimal;"><li>Step '''9''' is to clone the system in the TF card to the NMVe SSD. We can also directly burn the Linux image file to the NVMe SSD. Here are the steps:<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</li>

</div>~~<ol start~~class="6figure" ~~style="list-style-type: lower-alpha;"><li>Then select the device name of the NVMe SSD '''/dev/nvme0n1''', and click '''Select'''</li></ol~~>

[[File:pi3b-~~img105~~img123.png~~|386x264px~~]]

</div></ol><ol start="73" style="list-style-type: lower-alpha;"><li>~~Then click~~ '''~~Flash~~After using this method to burn the image, there is no need to manually expand the capacity, and it will automatically expand the capacity at the 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|389x264px|IMG_256]]~~0 burning port ===

~~</div>~~# 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~~<ol start="8" style="list~~# You also need to prepare a good quality USB2.0 male-~~style~~to-~~type: lower-alpha;"><li>Then click '''Yes, I'm sure'''</li></ol>~~male data cable

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

</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-~~roman~~alpha;"><li>~~Then enter~~ After opening the ~~password orangepi~~ download link of the ~~Linux system on~~ Android image, you can see the ~~development board~~following two types of Android images, please select the image in the '''TF card and ~~it will start burning the Linux~~ eMMC startup image ''' folder to ~~the SSD~~download</li~~></ol~~>

[[File:pi3b-~~img108~~img124.png~~|390x267px|IMG_256~~]]

</div>

</ol><ol start="102" 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: none;"><li>a) The first image is dedicated to HDMI display of and supports 4K display. If you don't use LCD screen, please download the ~~burning process is as follows:~~image without lcd</li><li>b) If you want to use lcd screen, please choose image with lcd</olli>

[[File:pi3b-~~img109~~img125.png~~|393x212px~~]]</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]]<~~div class~~/ol><ol start="7" style="~~figure~~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>

[[File:pi3b-~~img110~~img32.png~~|395x205px|IMG_256~~]]</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]]</~~div~~ol></li></ol><ol start="118" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The display after burning is as follows:~~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-~~img111~~img34.png~~|398x227px~~]]</ol><ol start="9" style="list-style-type: decimal;"><li>After opening the '''RKDevTool''' burning tool, because the computer has not connected to the development board through the USB2.0 male-to-male data cable at this time, the lower left corner will prompt "'''No device found'''"</li>

[[File:pi3b-img35.png]]</ol><ol start="1210" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~you need~~ start burning the Android image to ~~expand~~ the ~~capacity of the rootfs partition in the NVMe SSD. The steps are as follows:~~TF card

<li>~~Open '''GParted''' first~~First, if connect the development board to the Windows computer through the ~~system does not have Gparted pre~~USB2.0 male-~~installed, please use the apt command~~ to ~~install itorangepi@orangepi:~$ '''sudo apt~~-~~get install -y gparted'''~~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-~~img112~~img36.png~~|576x215px|IMG_256~~]]

</div></ol>

<li>Then ~~enter~~ make sure that the ~~password orangepi of~~ development board is not inserted into the ~~Linux system,~~ TF card and ~~click '''Authenticate'''~~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:</olli>

[[File:pi3b-~~img113~~img37.png~~|356x173px~~]]</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="35" style="list-style-type: lower-alpha;"><li>~~Then click~~ If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''~~Fix~~found a MASKROM device'''"</li~~></ol~~>

[[File:pi3b-~~img114~~img39.png~~|355x261px~~]]</ol><ol start="46" style="list-style-type: lower-alpha;"><li>Then insert the TF card into the development board</li><li>Then please select ~~NVMe SSD~~'''advanced features'''[[File:pi3b-img126.png]]</li><li>Then click the position shown in the figure below</olp>[[File:pi3b-img127.png]]</li><li>Then select '''rk3566_MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and click to open</li>

[[File:pi3b-~~img115~~img68.png~~|452x187px|IMG_256~~]] ~~</div><ol start="5" style="list-style-type: lower-alpha;"><li>The display interface after selecting NVMe SSD is as follows:</li></ol>~~

</div></ol>

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

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

</div><~~ol start="6" style="list-style-type: lower-alpha;"~~/li><li>~~Then select~~ The display of successful switching is shown in the ~~'''/dev/nvme0n1p2''' partition, click the right button again, and then select '''Resize/Move'''~~figure below</lip></olli>

[[File:pi3b-~~img117~~img131.png~~|448x345px|IMG_256~~]]

</div></ol><ol start="714" style="list-style-type: lower-alpha;"><li>Then ~~drag~~ click the ~~capacity to the maximum at~~ "'''Upgrade Firmware'''" column of the ~~position shown in the figure below~~burning tool</li~~></ol~~>

[[File:pi3b-~~img118~~img132.png~~|339x210px~~]]</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="816" style="list-style-type: lower-alpha;"><li>~~Then~~ Finally, click the "'''~~Resize/Move~~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~~div class="figure">

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

</div></ol ~~style="list-style-type: lower-roman;"~~></li>~~Then click the green '''√''' in the position below~~</liol></olspan>

~~[[File:pi3b-img120.png|425x166px]]~~=== How to use SDDiskTool to burn Android image to TF card ===

<ol ~~start~~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 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'''], '''please make sure that the version of the SDDiskTool tool is the latest v1.72.'''</li><li>Then download the Android11 image from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page''']<ol style="list-style-type: lower-alpha;"><li>~~Then click~~ 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 '''~~Apply~~TF card and eMMC startup image'''folder to download</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>~~img124.png]]

~~[[File~~</div></ol><ol start="2" style="list-style-type:~~pi3b~~lower-~~img122.png|383x234px]]~~alpha;"><li>After entering the '''TF card and eMMC boot image''' folder, you can see the following two images, the difference between them is:</li>

<ol ~~start="13"~~ style="list-style-type: ~~lower-alpha~~none;"><li>~~At this point,~~ a) The image without lcd is specially used for HDMI display and supports 4K display. If you ~~can~~ do not use the ~~'''sudo poweroff''' command to shut down. Then~~ LCD screen, please ~~pull out~~ download the ~~TF card, and then short press the power button~~ image without lcd</li><li>b) If you want to ~~turn on~~use LCD screen, ~~then the Linux system in SPIFlash+NVMe SSD will be started.~~please choose image with lcd</lip></olli>

[[File:pi3b-img125.png]]<!-/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 '''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-img135.png]]</ol><ol start="107" style="list-style-type: decimal;"><li>~~Step~~ After opening '''9)SDDiskTool''' , if the TF card is ~~to clone~~ recognized normally, the ~~system~~ 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 ~~NMVe SSD~~TF card</li> [[File:pi3b-img136. We png]]</ol><ol start="8" style="list-style-type: decimal;"><li>After confirming the drive letter, you can ~~also directly burn~~ format the TF card first, click the '''restore disk button''' in '''SDDiskTool,''' or use the ~~Linux image file~~ '''SD Card Formatter''' mentioned above to format the ~~NVMe SSD~~TF card</li> [[File:pi3b-img137. ~~Here are~~ png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then start to write the Android image to the ~~steps:~~TF card

<li>~~Upload~~ First check "SD Boot" in "Select Function Mode"</li><li>Then select the ~~Linux~~ path of the Android image ~~file~~ in the "Select to ~~the Linux system of the development board~~upgrade firmware" column</li><li>~~Then use balenaEtcher~~ Finally click the "Start Create" button to start burning the Android image to ~~burn~~the TF card</li> [[File:pi3b-img138.png]]</ol>

</li></ol>

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

[[File:pi3b-img139.png]]<~~div~~ /ol> == How to burn Android image to eMMC == {| class="~~figure~~wikitable"style="background-color:#ffffdc;width:800px;" |-| <big>'''Note, after burning the image into eMMC, if the test finds that it cannot be started, please clear the SPIFlash and try again. For the method of clearing SPIFlash, please refer to [[Orange Pi 3B#Using RKDevTool to clear SPIFlash|the method of using RKDevTool to clear SPIFlash]].'''</big>|}

~~[[File:pi3b~~=== Method of burning Android image into eMMC through USB2.~~png|529x333px|图片1]]~~0 burning port ===

~~</div><ol start~~{| class="3wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>'''~~After using this method to burn the image, there is no need to manually expand the capacity, and it will automatically expand the capacity at~~ Note that all the ~~first startup~~following operations are performed on a Windows computer.'''</~~li></ol~~big>|}

<~~span id~~ol style="~~how~~list-~~to-burn-android-image-to-tf~~style-~~card~~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.</~~span~~p>~~== How to burn Android image to TF card ==~~The eMMC module and the method of plugging into the development board are as follows:</li>

~~=== Method of burning Android image to TF card through USB2~~img62.~~0 burning port ===~~png|400px]]

~~# First prepare a TF card with 8GB or larger capacity~~[[File:pi3b-img63. ~~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~~png|800px]]</ol><ol start="2" style="list-style-type: decimal;"># <li>You also need to prepare a good quality USB2.0 male-to-male data cable</li>

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

</div></ol>

<li>Then download Rockchip driver '''DriverAssitant_v5.12.zip''' and burning tool '''RKDevTool_Release_v3.15.zip''' from [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/~~index~~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/~~serviceAndSupport~~hardWare/computerAndMicrocontrollers/service-and-support/~~index~~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 '''TF card and eMMC startup imagefolder''' ~~folder~~ to download</li~~></ol></li></ol~~>

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

</div></ol>

<li>After entering the '''TF card and eMMC startup imagefolder''' ~~folder~~, you can see the following two 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>

~~[[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.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>~~</ol>~~ ~~[[File:pi3b-img31.png|575x169px]]~~

[[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|300x157px]]~~

[[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|315x164px]]~~

[[File:pi3b-img33.png]]

</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>~~</ol>~~ ~~[[File:pi3b-img34.png|454x134px]]~~

[[File:pi3b-img34.png]]

</ol>

<li>After opening the '''RKDevTool''' burning tool, because the computer ~~has~~ 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|442x208px]]~~

[[File:pi3b-img35.png]]

</ol>

<li>Then start burning the Android image ~~to the TF card~~into eMMC

<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>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.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~~</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'''"[[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>

~~[[File~~<ol start="8" style="list-style-type:~~pi3b~~lower-~~img39~~alpha;"><li>Select '''rk3566_MiniLoaderAll.bin''' in the MiniLoader folder downloaded earlier, and click to open.~~png|457x215px]]~~</li>

<~~ol start~~div class="6figure" ~~style="list-style-type: lower-alpha;"><li>Then insert the TF card into the development board</li><li>Then please select '''advanced features'''[[File:pi3b-img126.png|458x138px]]</li><li>Then click the position shown in the figure below[[File:pi3b-img127.png|459x216px]]</li><li>Then select '''rk3566_MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and click to open</li></ol~~>

~~<div class="figure">~~[[File:pi3b-img68.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-~~img68~~img141.png~~|459x216px|SIS5H0S2@F5M2D(6ANZEUPG~~]]</li><li>The display of successful switching is shown in the figure below</li>

[[File:pi3b-img142.png]]</~~div~~ol><ol start="1013" style="list-style-type: lower-alpha;"><li~~><p~~>Then click the "'''~~download~~Upgrade Firmware'''~~[[File:pi3b-img128.png|472x222px]]</li><li>The display after downloading '''rk3566_MiniLoaderAll.bin''' is shown in~~ " column of the ~~figure below[[File:pi3b-img129.png|474x227px]]~~burning tool</~~p></li>~~<li~~>Then select the storage device as '''SD''', and then click '''Switch Storage'''<div class="figure"~~>

[[File:pi3b-~~img130~~img132.png~~|477x222px|D~T2CO%X~K2@ELR98)BVP~2~~]]</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>

[[File:pi3b-img133.png]]</~~div~~ol><~~/li~~ol start="15" style="list-style-type: lower-alpha;"><li>~~The display of successful switching~~ Finally, click the "'''Upgrade'''" button to start burning, and the log during the burning process is shown in the figure below~~~~. After burning is completed, the Android system will start automatically.</li~~></ol~~>

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

</div></ol></li></ol ~~start~~>~~<li>Then click the "'''Upgrade Firmware'''" column of the burning tool~~</~~li></ol~~span>

~~[[File:pi3b-img132.png|477x224px]]~~=== How to burn Android11 image into eMMC via TF card ===

~~<ol start~~{| class="15wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~Then click the "~~'''~~Firmware~~Note that all the following operations are performed on a Windows computer.'''~~" button to select the path of the Android image that needs to be burned~~</~~li></ol~~big>|}

~~[[File~~# 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:~~pi3b-img133.png|444x209px]]~~

~~<ol start="16" style="list~~::[[File:pi3b-~~style-type~~img61.png|400px]] [[File: ~~lower~~pi3b-~~alpha;">~~<li>Finally, click the "'''Upgrade'''" button to start burning, and the log during the burning process is shown in the figure below. After burning is completed, the Android system will start automaticallyimg62.~~</li></ol>~~png|400px]]

~~<div class="figure">~~::[[File:pi3b-img63.png|800px]]

~~[[File:pi3b-img134.png|455x214px|GO~ZSPN`B]JCQM`@_9UU8[R]]~~ <~~/div>=== How to use SDDiskTool to burn Android image to TF card ===~~ ~~<ol~~ style="list-style-type: decimal;"><li>~~First~~ You also need to prepare a TF card with 8GB or larger capacity. The transmission speed of the TF card must be class10 or above. It is recommended to use a TF card of SanDisk and other brands</li>

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

<li>Then download the SDDiskTool programming tool from the [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/~~index~~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~~ Android image from ~~the~~ [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange -Pi ~~download''~~-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 imagefolder''' ~~folder~~ to download</li~~></ol></li></ol~~>

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

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

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

<li>After entering ~~the~~ '''the TF card and eMMC boot imagefolder''' ~~folder~~, you can see the following ~~two~~ tow 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</li><li>b) If you want to use lcd screen, please choose image with lcd</olp></li>

<![[File:pi3b-~~- -->~~img125.png]]</ol ~~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 the LCD screen, please download the image without lcd~~</~~p></li~~ol>~~<li>If you want to use LCD screen, please choose image with lcd~~</li></ol> ~~[[File:pi3b-img125.png|281x62px]]~~ <ol start="56" 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 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>~~</ol>~~ ~~[[File:pi3b-img135.png|415x99px]]~~ ~~<ol start="7" 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. 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> ~~[[File:pi3b-img136.png|267x228px]]~~

[[File:pi3b-img135.png]]

</ol>

<li>After ~~confirming the drive letter~~opening '''SDDiskTool''', ~~you can format~~ if the TF card ~~first~~is recognized normally, ~~click~~ the ~~'''restore~~ inserted disk ~~button~~device will be displayed in the "''' in Select Removable Disk Device'''~~SDDiskTool,~~" column. ''' ~~or use~~ Please make sure that the displayed disk device is consistent with the drive letter of the TF card you want to burn'''~~SD Card Formatter''' mentioned above~~ , if there is no display, you can try to ~~format~~ unplug the TF card.</li~~></ol~~>

[[File:pi3b-~~img137~~img136.png~~|264x226px~~]]</ol><ol start="9" style="list-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>

[[File:pi3b-img137.png]]</ol><ol start="910" style="list-style-type: decimal;"><li>Then start to write the Android image to into the TF card

<li>First ~~check~~ confirm that the displayed drive letter is the drive letter corresponding to the TF card under "'''Select Removable Disk Device'''"</li><li>Then select "~~SD Boot~~'''Firmware Upgrade'''" in "'''Select Function Mode'''"</li><li>Then select the path of the Android ~~image~~ firmware in the "'''Select ~~to upgrade firmware~~Upgrade Firmware'''" column</li><li>Finally click the "'''Start Create'''" button to start burning ~~the Android image to the TF card~~</li> [[File:pi3b-img143.png]]</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-~~img138~~img144.png~~|286x242px~~]]</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="1014" style="list-style-type: decimal;"><li>~~After~~ When the HDMI monitor displays the following information, it means that the burningof the Android image into the eMMC has been completed. At this time, ~~you~~ the TF card can ~~exit the SDDiskTool software~~be pulled out, and then ~~you can pull out the TF card from~~ the ~~computer and insert it into~~ Android system in the ~~development board to~~ eMMC will start.</li~~></ol~~>

[[File:pi3b-~~img139~~img146.png~~|288x244px~~]]</ol>

~~~~== How to burn Android image to ~~eMMC~~ SPIFlash+NVMe SSD ==

{| 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~~ol style="~~method~~list-ofstyle-~~burning-android-image-into-emmc-through~~type: decimal;"><li>First, you need to prepare an NVMe SSD solid state drive<ol style="list-~~usb2.0~~style-~~burning~~type: lower-~~port~~alpha;"><li>The M.2 2230 SSD is as follows</~~span~~li>~~=== Method of burning Android image into eMMC through USB2.0 burning port ===~~

~~'''Note that all the following operations are performed on a Windows computer~~[[File:pi3b-img73.~~'''~~png]]</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 ></li></ol><ol start="2" style="list-style-type: decimal;"><li>~~The development board reserves an eMMC expansion interface. Before programming~~ Then insert the ~~system to eMMC, you first need to purchase an eMMC module that matches~~ NVMe SSD into the ~~eMMC~~ M.2 PCIe 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:~~fix it</li~~></ol~~>

[[File:pi3b-~~img61~~img75.png~~|115x84px~~]] ~~[[File~~</ol><ol start="3" style="list-style-type:~~pi3b-img62.png|120x87px]]~~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-~~img63~~img76.png~~|286x133px~~]]</ol><ol start="24" style="list-style-type: decimal;"><li>You also 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><ol start="35" 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/serviceAndSupport/index.html~~ '''Orange Pi's data download page''']</li><li>Then download the ~~Android~~ image ~~from '''[http://www.orangepi.org/html/serviceAndSupport/index.html Orange Pi's download page].'''~~of Android11

<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 S'''~~TF card and eMMC startup~~ PIFlash-NVME SSD boot image folder''' to download</li~~></ol></li></ol~~>

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

</div>

</ol>

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

</li></ol>

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

[[File:pi3b-~~img125~~img31.png~~|264x58px~~]] ~~<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>~~</ol> ~~[[File:pi3b-img31.png|575x169px]]~~ <ol start="78" style="list-style-type: decimal;">

<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|300x157px]]~~

[[File:pi3b-img32.png]]

</ol>

<li>After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button.</li>~~</ol>~~ ~~[[File:pi3b-img33.png|315x164px]]~~ ~~<ol start="8" 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|454x134px]]~~

[[File:pi3b-img33.png]]

</ol>

</li></ol>

<li>~~After opening the~~ Then decompress '''~~RKDevTool~~RKDevTool_Release_v3.15.zip''' ~~burning tool~~, ~~because the computer is~~ this software does not ~~connected to the development board through the USB2.0 male-~~need to~~-male data cable at this time~~be installed, ~~the lower left corner will prompt "~~just find '''~~No device found~~RKDevTool'''~~"~~in the decompressed folder and open it</li~~></ol~~>

[[File:pi3b-~~img35~~img34.png~~|442x208px~~]]</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 ~~into eMMC~~to SPIFlash+NVMe 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~~ port 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>~~Then make~~ 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.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~~><p~~>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|457x215px]]~~</li>~~<li>Then please select '''Advanced Features'''[[File:pi3b-img126.png|458x138px]]</li><li>Then click the position shown in the figure below[[File:pi3b-img127.png|459x216px]]</li></ol~~>

[[File:pi3b-img39.png]]</ol><!ol start="6" style="list-style- type: lower-alpha;"><li>Then click the "'''Upgrade Firmware'''" column of the burning tool</li> [[File:pi3b-img132.png]]</ol><ol start="7" style="list-style-type: lower-alpha;"><li>~~Select~~ Then click the "'''~~rk3566_MiniLoaderAll.bin~~Firmware''' " button to select the Android image to be burned</li> [[File:pi3b-img133.png]]</ol><ol start="8" style="list-style-type: lower-alpha;"><li>Finally, click the "Upgrade" button to start burning. The burning process is shown in the ~~MiniLoader folder downloaded earlier~~figure below. You can see that the firmware will be burned to SPIFlash first, and ~~click~~ then burned to ~~open~~PCIE. After burning is completed, the Android system will start automatically.</li> [[File:pi3b-img148.png]]</ol></li></ol> == Using RKDevTool to clear SPIFlash ==

~~<div class="~~# The position of SPI Flash on the development board is shown in the figure">below

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

~~</div>~~<ol start="2" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then click '''Download'''[[File:pi3b-img128.png|472x222px]]</li><li>The display after downloading '''MiniLoaderAll~~First, you need to prepare a good quality USB2.~~bin''' is shown in the figure below[[File:pi3b~~0 male-~~img140.png|474x223px]]</li><li>Then select the storage device as '''EMMC''', and then click Switch '''Storage'''[[File:pi3b~~to-~~img141.png|468x225px]]</li><li>The display of successful switching is shown in the figure below~~male data cable</li~~></ol~~>

~~[[File:pi3b-img142.png|472x227px]]~~<div class="figure">

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

</div></ol><ol start="3" style="list-style-type: decimal;"><li>Then download the Rockchip driver '''DriverAssitant_v5.12.zip''' and MiniLoader and the burning tool '''RKDevTool_Release_v3.15.zip''' from the [~~[File~~http:~~pi3b~~//www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-~~img132~~and-support/Orange-Pi-3B.~~png|442x208px]~~html '''Orange Pi data download page''']<ol style="list-style-type: lower-alpha;"><li>On the download page of Orange Pi, first select the official tool, and then enter the following folder</li>

<~~ol style~~div class="~~list-style-type: lower-roman;~~figure">~~<li>Then click the "'''Firmware'''" button to select the path of the Android image that needs to be burned</li></ol~~>

[[File:pi3b-~~img133~~img149.png~~|444x209px~~]]

</div></ol><ol start="102" style="list-style-type: lower-alpha;"><li>~~Finally, click the "'''Upgrade'''" button to start burning, and~~ Then download all the ~~log during the burning process is shown in the figure~~ files below~~. After burning is completed, the Android system will start automatically.~~</li~~></ol~~>

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

</div>

~~'''Note that the "MiniLoader-things needed to-burn~~-android11-~~the Linux image~~-into-emmc-via-tf-card"~~" folder is hereinafter referred to as the MiniLoader folder.'''</big>|}</ol></li></~~span~~ol><ol start="4" style=~~= How~~ "list-style-type: decimal;"><li>Then use decompression software to ~~burn Android11 image into eMMC via TF card ===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="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 "'''~~Note that all the following operations are performed on a Windows computer.~~Driver Installation'''" button</li>

~~# The development board reserves an eMMC expansion interface~~[[File:pi3b-img32. ~~Before programming the system to eMMC~~png]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", ~~you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to~~ and then click the ~~development board~~"'''OK'''" button. ~~The eMMC module and the method of plugging into the development board are as follows:~~</li>

[[File:pi3b-~~img61~~img33.png~~|115x84px~~]] ~~[[File~~</ol></li></ol><ol start="6" style="list-style-type:~~pi3b-img62~~decimal;"><li>Then decompress '''RKDevTool_Release_v3.15.~~png|120x87px]]~~zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li>

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

[[File:pi3b-img35.png]]</ol><ol start="28" 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~~ you can start to ~~insert~~ clear the ~~TF card into the computer</li>~~<li>Then download the SDDiskTool programming tool from the [http://www.orangepi.org/html/serviceAndSupport/index.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 Android image from [http://www.orangepi.org/html/serviceAndSupport/index.html '''Orange Pi's download page''']~~content in SPI FLASH

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

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

</div></ol>

<li>~~After entering '''~~Make sure that the development board is not inserted into 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~~ not connected to ~~HDMI display and supports 4K display. If you don’t use LCD screen, please download~~ the ~~image without lcd~~power supply</li><li>~~If you want to use lcd screen~~Then press and hold the MaskROM button on the development board, ~~please choose image with lcd~~the position of the MaskROM button on the development board is shown in the figure below:</li~~></ol></li></ol~~>

[[File:pi3b-~~img125~~img37.png~~|283x62px~~]]</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button</li>

[[File:pi3b-img38.png]]</ol><ol start="65" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then use the decompression software to decompress the compressed package of the downloaded Android image. Among~~ If the ~~decompressed files~~previous steps are successful, the ~~file ending with ".img" is the Android image file, and~~ development board will enter the ~~size is more than 1GB</li><li>Then use decompression software to decompress~~ '''~~SDDiskTool_v1.72.zip~~MASKROM''', mode at this ~~software does not need to be installed~~time, ~~just find~~ and the interface of the burning tool will prompt "'''~~SD_Firmware_Tool.exe~~found a MASKROM device''' ~~in the decompressed folder and open it~~"</li~~></ol~~>

[[File:pi3b-~~img135~~img39.png~~|429x103px~~]]</ol><ol start="6" style="list-style-type: lower-alpha;"><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><li>Select '''rk3566_MiniLoaderAll.bin''' in the '''MiniLoader''' folder you downloaded earlier, and click Open</li>

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

[[File:pi3b-~~img136~~img68.png~~|267x228px~~]]

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

<ol start="10" style="list-style-type: lower-alpha;"><li>The display after downloading '''rk3566_MiniLoaderAll.bin''' is shown in the figure below[[File:pi3b-img140.png]]</li><li>Then select the storage device as '''SPINOR'''[[File:pi3b-img151.png]]</li><li>Then click Switch '''Storage'''[[File:pi3b-~~img137~~img152.png~~|247x212px~~]]</li><li>Then click '''Erase All''' to 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>

~~<ol start~~=~~"10" style~~=~~"list-style-type: decimal;"><li>Then start to write~~ Start the ~~Android image into the TF card<ol style~~Orange Pi development board ==~~"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></li></ol>~~

~~[[File:pi3b~~# 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-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 USB Type-~~img143~~C interface.~~png|290x246px]]~~

~~<ol start~~::{| class="11wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;"|-| <big>'''<lispan style="color:#FF0000">~~After the burning is completed~~Remember not to plug in a power adapter with a voltage output greater than 5V, ~~the display is~~ as ~~shown in~~ this will burn out the ~~figure below, and then you can exit SDDiskTool</li>~~development board.'''</olspan>

~~[[File~~'''Many unstable phenomena during the power-~~img144~~on and start-up process of the system are basically caused by power supply problems, so a reliable power adapter is very important. If you find that there is a phenomenon of continuous restart during the startup process, please replace the power supply or the Type-C data cable and try again.~~png|285x243px]]~~'''

'''<~~ol start="12"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>Then pull out the TF card from the computer and insert it into the development board~~The Type-C power port does not support PD negotiation. ~~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>~~'''</olspan>

~~[[File~~'''In addition, please do not connect the USB interface of the computer to power the development board.~~png~~'''</big>|~~430x247px]]~~}

<ol start="146" style="list-style-type: decimal;"><li>~~When~~ Then turn on the ~~HDMI monitor displays the following information, it means that the burning~~ switch of the ~~Android image into the eMMC has been completed~~power adapter. ~~At this time~~If everything is normal, you can see the ~~TF card can be pulled out, and then~~ startup screen of the ~~Android~~ system in on the ~~eMMC will start~~HDMI monitor or LCD screen.</li~~></ol~~>

<li>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 '''[[~~File:pi3b-img146.png~~Orange Pi 3B#How to use the debugging serial port|~~576x389px~~the section on how to use the debugging serial port]].'''</li></ol>

~~~~== How to ~~burn Android image to SPIFlash+NVMe SSD~~ use the debugging serial port ==

~~'''Note that all the following operations are performed on a Windows computer.'''~~=== Connection instruction of debugging serial port ===

<li>First, you need to prepare ~~an NVMe SSD solid state drive~~a 3.3V USB-to-TTL module, and then insert the USB interface end of the USB-to-TTL module into the USB interface of the computer.~~<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;"|-| <big><lip>~~The M~~'''For better compatibility, it is recommended to use CH340 USB to TTL module, please do not use CP2102, PL2303 USB to TTL module.~~2 2230 SSD is as follows~~'''</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-img73.png|147x106px]]~~<div class="figure">

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

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

<li>~~Then insert the NVMe SSD into~~ The corresponding relationship between GND, RXD and TXD pins of the ~~M.2 PCIe interface~~ debugging serial port of the development board ~~and fix it~~is shown in the figure below</li~~></ol~~>

[[File:pi3b-~~img75~~img156.png~~|283x63px~~]]</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="3" style="list-style-type~~: ~~decimal;"><li>The position~~ a. Connect the GND of the ~~SPI Flash on~~ USB to TTL module to the GND of the development board ~~is shown in the figure below, no other settings are required before starting the programming</li></ol>~~

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

<li>~~You also need~~ The schematic diagram of connecting the USB to ~~prepare a good quality USB2.0 male-~~TTL module to~~-male data cable~~the computer and the Orange Pi development board is as follows</li~~></ol~~>

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

</div>

~~<ol start~~{| class="5wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Then download Rockchip driver '''DriverAssitant_v5.12.zip~~''' The TX and ~~burning tool '''RKDevTool_Release_v3~~RX of the serial port need to be cross-connected.~~15.zip~~If you don'~~'' from '''Orange Pi's data download page'''</li><li>Then download~~ t want to carefully distinguish the ~~image~~ order of ~~Android11<ol style="list-style-type: lower-alpha;"><li>After opening~~ TX and RX, you can connect the ~~download link~~ TX and RX of the ~~Android image~~serial port casually first. If there is no output in the test, ~~you can see~~ then exchange the ~~following two types~~ order of ~~Android images~~TX and RX, ~~please select the image in~~ so there is always a the ~~S''~~order is right'~~PIFlash-NVME SSD boot image folder~~''~~' to download~~</libig>|}</ol><~~/li~~span id="how-to-use-the-debugging-serial-port-on-the-ubuntu-platform"></olspan>

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

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

~~</div><ol start="2" style="list~~# First, insert the USB-to-~~style~~TTL module into the USB interface of the Ubuntu computer. If the connection and recognition of the USB-~~type: lower~~to-~~alpha;"><li>After entering~~ TTL module is normal, you can see the corresponding device node name under '''~~SPIFlash-NVME SSD boot image folder~~/dev'''~~, you can see~~ on the ~~following two images~~Ubuntu PC. ~~Their differences are:<ol style="list-style-type: lower-alpha;"><li>The image without lcd is specially used for HDMI display~~ Remember this node name, and ~~supports 4K display. If you do not use~~ then set the ~~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>~~serial port software will be used

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

~~<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><~~dev/~~ol>~~ttyUSB0|}

~~[[File~~<ol start="2" style="list-style-type: decimal;"><li>Then use the following command to install putty on Ubuntu PC</li>{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img31.png~~|~~407x120px]]~~test@test:~$ '''sudo apt-get update'''

test@test:~$ '''sudo apt-get install -y putty'''|}</ol><ol start="83" style="list-style-type: decimal;"><li>~~After opening ''~~Then run putty, '~~DriverInstall.exe~~''~~', the steps to install the Rockchip driver are as follows~~<ol span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">remember to add sudo permission<li/span>~~Click the "'''Driver Installation~~'''~~" button~~</li~~></ol></li></ol~~>

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

[[File:pi3b-img158.png]]</ol><ol start="25" style="list-style-type: ~~lower~~decimal;"><li>First select the setting interface of the serial port</li> [[File:pi3b-img159.png]]</ol><ol start="6" style="list-style-~~alpha~~type: decimal;"><li>~~After waiting for a period~~ Then set the parameters of ~~time, a pop~~the serial port<ol style="list-style-type: lower-~~up window will prompt "'''driver installed successfully'''&quot~~alpha;"><li>Set Serial line to connect toas /dev/ttyUSB0（(Modified to the corresponding node name, ~~and then click the "~~generally /dev/ttyUSB0）</li><li>Set Speed(baud) as '''OK1500000'''~~" button.~~（Serial port baud rate）</li><li>Set Flow control as None</olp></li>

~~[[File:pi3b-img33.png|296x154px]]~~<div class="figure">

~~<ol start="9" style="list-style~~[[File:pi3b-~~type: decimal;"><li>Then decompress '''RKDevTool_Release_v3.15~~img160.~~zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li></ol>~~png]]

~~[[File~~</div></ol></li></ol><ol start="7" style="list-style-type: decimal;"><li>After setting the setting interface of the serial port, return to the Session interface<ol style="list-style-type:~~pi3b~~lower-~~img34.png|413x122px]]~~alpha;"><li>First select the Connection type as Serial</li><li>Then click the Open button to connect to the serial port</li>

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

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

~~<ol start="11" style="list-style-type: decimal;"><li>Then start burning the Android image to SPIFlash+NVMe SSD~~~~<ol style="list-style-type: lower-alpha;">~~<li>First, connect the development board to the Windows computer through the USB2.0 male-to-male data cable. The position of the USB2.0 programming port of the development board is shown in the figure below</lidiv></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-img162.png]]

</ol>

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

~~[[File~~{| class="wikitable" style="background-color:~~pi3b~~#ffffdc;width:800px;" |-~~img36~~| <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.~~png~~This software has a free version and can be used without buying a serial number.'''</big>|~~275x116px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\1691131157154(1).jpg1691131157154(1)]]~~}

<ol style="list-style-type: decimal;"><li>Download MobaXterm</~~div~~p><ol style="list-style-type: lower-alpha;"><li>Download MobaXterm website as follows</li>{| class="wikitable" style="width:800px;" |-| [https://mobaxterm.mobatek.net/ '''https://mobaxterm.mobatek.net''']|}</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="53" 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>If Open the session settings interface</li><li>Select the serial port type</li><li>Select the port number of the serial port (select the ~~previous steps are successful,~~ corresponding port number according to the actual situation)</li><li>Select the ~~development board will enter~~ baud rate of the serial port as '''~~MASKROM~~1500000''' ~~mode at this time, and the interface of~~ </li><li>Finally click the ~~burning tool will prompt~~ "'''~~found a MASKROM device~~OK'''"button to complete the setting</lip></olli>

~~[[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>~~img167.png]]

~~[[File~~</div></ol></li></ol><ol start="4" style="list-style-type:~~pi3b-img132~~decimal;"><li>After clicking the "'''OK'''" button, you will enter the following interface.~~png|442x208px]]~~At this time, start the development board and you can see the output information of the serial port</li>

<~~ol start~~div class="7figure" ~~style="list-style-type: lower-alpha;"><li>Then click the "'''Firmware'''" button to select the Android image to be burned</li></ol~~>

[[File:pi3b-~~img133~~img168.png~~|444x209px~~]]

</div></ol ~~start="8" style~~><li>Finally, click~~ the ~~"Upgrade" button to start burning. The burning process is shown~~ -5v-pin-in -the ~~figure below. You can see that~~ -40pin-interface-of-the ~~firmware will be burned~~ -development-board-to ~~SPIFlash first, and then burned to PCIE. After burning is completed, the Android system will start automatically.</li-supply-power"></olspan>

~~[[File:pi3b-img148.png|453x212px]]~~== Instructions for using the 5v pin in the 40pin interface of the development board to supply power ==

~~'''The power supply method we recommend for the development board is to use the 5V/3A Type C interface power cord toplug into the Type-~~clear~~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-~~spiflash">~~C power supply.'''</~~span~~big>~~== Using RKDevTool to clear SPIFlash ==|}

# ~~The position of SPI Flash on the development board is shown in the figure below~~ ~~[[File:pi3b-img76.png|263x193px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>~~First, you need to prepare a ~~good quality USB2.0 male-to-male data cable</li></ol>~~power cord as shown in the figure below

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

</div>

::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Please purchase the power cord shown in the picture above by yourself'''</big>|} <ol start="32" style="list-style-type: decimal;"><li>~~Then download~~ Use the 5V pin in the ~~Rockchip driver '''DriverAssitant_v5.12.zip''' and MiniLoader and~~ 40pin interface to supply power to the ~~burning tool '''RKDevTool_Release_v3.15~~development board.~~zip''' from~~ The connection method of the ~~[http://www.orangepi.org/html/serviceAndSupport/index.html '''Orange Pi data download page''']~~power line is as follows

<li>On The USB A port of the power cord shown in the above picture needs to be plugged into the 5V/3A power adapter connector ('''please do not plug into the ~~download page~~ computer's USB port for power supply''')</li><li>The red DuPont line needs to be plugged into the 5V pin of ~~Orange Pi, first select~~ the ~~official tool~~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 40pin interface on the development board is shown in the figure below, ~~and then enter~~ '''remember not to reverse the ~~following folder~~connection'''</li> [[File:pi3b-img170.png]]</ol>

</li></ol>

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

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-~~img149~~| <big>'''The content of this chapter is written based on the images of the Linux server version and the xfce desktop version.~~png|342x56px~~'''</big>|~~1691401357374]]~~}

<~~/div><ol start~~span id="~~2" style="list~~supported-linux-image-types-~~style~~and-~~type: lower~~kernel-~~alpha;~~versions">~~<li>Then download all the files below~~</~~li></ol~~span>== Supported Linux image types and kernel versions ==

~~<div~~ {| class="~~figure~~wikitable">style="width:800px;text-align: center;"|-|'''Linux image type'''|'''kernel version'''|'''server version'''|'''desktop version'''|-|'''Debian 11 - Bullseye'''|'''Linux5.10'''|'''support'''|'''support'''|-|'''Ubuntu 20.04 - Focal'''|'''Linux5.10'''|'''support'''|'''support'''|-|'''Ubuntu 22.04 - Jammy'''|'''Linux5.10'''|'''support'''|'''support'''|}

~~[[File:pi3b~~== Linux System adaptation ==

~~</div>~~{| class="wikitable" style="width:800px;text-align: center;"|-|'''Function'''|'''Debian11'''|'''Ubuntu20.04'''|'''Ubuntu22.04'''|-|'''USB2.0x3'''|'''OK'''|'''OK'''|'''OK'''|-|'''USB3.0x1'''~~Note that the "MiniLoader~~|'''OK'''|'''OK'''|'''OK'''|-~~things needed to burn the Linux image" folder is hereinafter referred to as the MiniLoader folder~~|'''M.2 NVMe SSD Start'''|'''OK'''~~<ol~~ |'''OK'''|'''OK'''|-|'''WIFI'''|'''OK'''|'''OK'''|'''OK'''|-|'''Bluetooth'''|'''OK'''|'''OK'''|'''OK'''|-|'''GPIO（40pin）'''|'''OK'''|'''OK'''|'''OK'''|-|'''UART（40pin）'''|'''OK'''|'''OK'''|'''OK'''|-|'''SPI（40pin）'''|'''OK'''|'''OK'''|'''OK'''|-|'''I2C（40pin）'''|'''OK'''|'''OK'''|'''OK'''|-|'''PWM（40pin）'''|'''OK'''|'''OK'''|'''OK'''|-|'''PWM fan interface'''|'''OK'''|'''OK'''|'''OK'''|-|'''3pin Debug serial port'''|'''OK'''|'''OK'''|'''OK'''|-|'''EMMC'''|'''OK'''|'''OK'''|'''OK'''|-|'''TF card start~~="4" style="list~~'''|'''OK'''|'''OK'''|'''OK'''|-|'''HDMI Video'''|'''OK'''|'''OK'''|'''OK'''|-|'''HDMI Audio'''|'''OK'''|'''OK'''|'''OK'''|-|'''Camera'''|'''OK'''|'''OK'''|'''OK'''|-|'''LCD'''|'''OK'''|'''OK'''|'''OK'''|-|'''Edp Display'''|'''OK'''|'''OK'''|'''OK'''|-|'''Gigabit Ethernet port'''|'''OK'''|'''OK'''|'''OK'''|-|'''Network port status light'''|'''OK'''|'''OK'''|'''OK'''|-|'''headphone playback'''|'''OK'''|'''OK'''|'''OK'''|-|'''headphone recording'''|'''OK'''|'''OK'''|'''OK'''|-|'''LED Light'''|'''OK'''|'''OK'''|'''OK'''|-|'''RTC'''|'''OK'''|'''OK'''|'''OK'''|-|'''GPU'''|'''OK'''|'''OK'''|'''OK'''|-|'''NPU'''|'''OK'''|'''OK'''|'''OK'''|-|'''VPU'''|'''OK'''|'''OK'''|'''OK'''|-~~style~~|'''watchdog test'''|'''OK'''|'''OK'''|'''OK'''|-~~type: decimal;"><li>Then use decompression software to decompress~~ |'''Chromium Hard solution video'''|'''OK'''|'''~~DriverAssitant_v5.12.zip~~OK'''~~, and then find the~~ |'''~~DriverInstall.exe~~OK''' ~~executable file in the decompressed folder and open it</li></ol>~~|}

~~[[File:pi3b~~== The format of Linux commands in this manual ==

~~<ol start~~# In this manual, all commands that need to be entered in the Linux system will be marked with the following box::{| class="5wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>After opening DriverInstall.exe, the steps to install the Rockchip driver are as follows<ol style="list-style-type~~height: ~~lower-alpha~~40px;">~~<li>Click the "'''Driver Installation'''" button</li></ol>~~|-~~</li></ol>~~|

~~[[File~~|}::As shown below, the content in the yellow box indicates the content that needs special attention, except for the commands in it.::{| class="wikitable" style="background-color:#ffffdc;width:800px;height:~~pi3b~~40px;" |-~~img32.png~~|~~276x145px]]~~

|}<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>~~After waiting for a period~~ The prompt in front of the command refers to the content of ~~time~~the red part in the box below, ~~a pop-up window will prompt "'''driver installed successfully'''"~~which is not part of the Linux command, so when entering the command in the Linux system, ~~and then click~~ please do not enter the ~~&quot~~content of the red font part</li>{| class="wikitable" style="width:800px;" |-| '''~~OK'''" button.~~<~~/li~~span style="color:#FF0000">orangepi@orangepi:~$</olspan>sudo apt update'''

~~[[File~~'''root@orangepi:~#''' '''vim /boot/boot.~~png|292x151px]]~~cmd'''

'''<~~ol start="6"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">test@test:~$<li/span>~~Then decompress '''RKDevTool_Release_v3~~ssh [mailto:root@192.168.1.36 root@192.168.151.~~zip''', this software does not need to be installed, just find '''RKDevTool~~]xxx''' ~~in the decompressed folder and open it</li></ol>~~

~~[[File~~'''root@test:~~pi3b-img34.png~~~# ls'''|~~467x138px]]~~}</ol><ol start="72" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~After opening the~~ '''root@orangepi:~$'''~~RKDevTool~~The prompt indicates that this command is entered in ''' ~~burning tool, because~~ the ~~computer has not connected to~~ Linux system of the development board ~~through~~ '''. The $ at the ~~USB2~~end of the prompt indicates that the current user of the system is a normal user.~~0 male-~~When executing a privileged command, you need to~~-male data cable~~ 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 ~~time~~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 ~~lower left corner will~~ prompt ~~"~~indicates that the current user of the system is an ordinary user. When executing privileged commands, sudo needs to be added '''sudo'''</li><li>'''~~No device found~~root@test:~#'''~~"~~The prompt indicates that this command is entered in the Ubuntu PC or Ubuntu virtual machine, not in the Linux system of the development board. The # at the end of the prompt indicates that the current user of the system is the root user and can execute any command you want</li></ol></li></ol>~~[[File:pi3b~~<!-- --~~img35.png|402x189px]]~~><ol start="83" style="list-style-type: decimal;"><li>~~Then you can start~~ What are the commands that need to ~~clear the content in SPI FLASH~~be entered?

<li>~~First~~As shown below, ~~connect~~ '''the ~~development board~~ black bold part''' is the command that needs to be input, and the ~~Windows computer through~~ content below the ~~USB2.0 male-to-male data cable. The position of~~ command is the ~~USB2.0 programming port~~ output content (some commands have output, some may not), and this part of the ~~development board is shown in the figure below~~content does not need to be input</li>~~</ol>~~<{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''cat /~~li><~~boot/~~ol>~~orangepiEnv.txt'''

'''<~~div class~~span style="~~figure~~color:#FF0000">verbosity=7'''

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

'''console=serial'''|}</~~div~~ol>

<li>~~Make sure that~~ As shown below, some commands cannot be written in one line and will be placed on the ~~development board is not inserted into~~ next line. As long as the ~~TF card~~ black and ~~not connected~~ bold parts are all commands that need to be input. When these commands are entered into one line, the ~~power supply</li><li>Then press and hold the MaskROM button on the development board~~last "\" of each line needs to be removed, ~~the position~~ this is not part of the ~~MaskROM button on the development board is shown~~ command. In addition, there are spaces in different parts of the ~~figure below:~~command, please don't miss it</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''echo \'''

'''"deb [~~[File:pi3b~~arch=$(dpkg --print-~~img37.png|289x100px]]~~architecture) \'''

~~<ol start~~'''signed-by=~~"4" style="list~~/usr/share/keyrings/docker-~~style~~archive-~~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></ol>~~keyring.gpg] \'''

~~[[File~~'''https:~~pi3b-img38~~//download.~~png|305x94px]]~~docker.com/Linux/debian \'''

~~<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~~ $(lsb_release -cs) stable"| sudo tee /etc/apt/sources.list.d/docker.list > /dev/null'''~~found a MASKROM device'''"~~|}</ol></li></ol>

~~[[File:pi3b-img39.png|457x215px]]~~== Linux system login instructions ==

<~~ol start~~span id="~~6" style="list~~linux-system-~~style~~default-~~type: lower~~login-~~alpha;"><li>Then please select '''Advanced Features'''[[File:pi3b~~account-~~img126.png|458x138px]]</li><li>Then click the position shown in the figure below[[File:pi3b~~and-~~img127.png|459x216px]]</p~~password"></lispan>~~<li>Select '''rk3566_MiniLoaderAll.bin''' in the '''MiniLoader''' folder you downloaded earlier,~~ === Linux system default login account and ~~click Open</li></ol>~~password ===

~~<div~~ {| class="~~figure~~wikitable">style="width:800px;text-align: center;"|-|'''Account'''|'''Passport'''|-|'''root'''|'''orangepi'''|-|'''orangepi'''|'''orangepi'''|}

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-~~img68~~| <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>|}{|~~459x216px~~class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''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>|~~SIS5H0S2@F5M2D(6ANZEUPG]]~~}

<~~/div><ol style~~span id="~~list~~how-to-set-automatic-terminal-~~style~~login-~~type: lower~~in-~~roman;~~linux-system">~~<li>Then click '''Download'''[[File:pi3b-img128.png|472x222px]]</li~~></olspan>

~~<ol start~~=~~"10" style~~=~~"list-style-type: lower-alpha;"><li>The display after downloading '''rk3566_MiniLoaderAll.bin''' is shown in the figure below[[File:pi3b-img140.png|474x223px]]</li><li>Then select 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'''~~ = How to ~~start erasing SPIFlash[[File:pi3b-img153.png|467x220px]]</li><li>The display log after erasing SPIFlash is shown~~ set automatic terminal login in ~~the figure below[[File:pi3b-img154.png|460x216px]]</li></ol>~~Linux system ===

# The Linux system automatically logs in to the terminal by default, and the default login user name is '''orangepi~~== 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, 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-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~~::[[File:pi3b-~~C interface~~img171.png]]

<ol start="2" style="list-style-type: decimal;"><li>Use the following command to set the root user to automatically log in to the terminal</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo auto_login_cli.sh root'''~~Remember not~~ |}</ol><ol start="3" style="list-style-type: decimal;"><li>Use the following command to ~~plug~~ disable automatic login terminal</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo auto_login_cli.sh -d'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Use the following command to set the orangepi user to automatically log in ~~a power adapter with a voltage output greater than 5V, as this will burn out~~ to the ~~development board~~terminal again</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo auto_login_cli.sh orangepi'''|}</ol>

~~'''Many unstable phenomena during the power-on and start-up process~~ === Instructions for automatic login of ~~the~~ Linux desktop version system are basically caused by power supply problems, so a reliable power adapter is very important. If you find that there is a phenomenon of continuous restart during the startup process, please replace the power supply or the Type-C data cable and try again.'''===

~~'''The Type-C power port does not support PD negotiation.'''~~# After the desktop system starts, it will automatically log in to the desktop without entering a password

~~'''In addition, please do not connect the USB interface of the computer to power the development board.'''~~<div class="figure">

~~6) Then turn on the switch of the power adapter. If everything is normal, you can see the startup screen of the system on the HDMI monitor or LCD screen~~::[[File:pi3b-img172.png]]

~~7) If you want~~ </div><ol start="2" style="list-style-type: decimal;"><li>Run the following command to ~~view the output information of~~ prohibit the desktop system ~~through~~ from automatically logging into the ~~debugging serial port, please use the serial cable to connect the development board to the computer~~desktop</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo disable_desktop_autologin. ~~For the connection method of the serial port, please refer to~~ sh'''|}</ol><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|~~the section on how~~ password]] is required to ~~use~~ enter the ~~debugging serial port]].'''~~system<div class="figure">

~~== How to use the debugging serial port ==~~img173.png]]

<~~span id="connection-instruction-of-debugging-serial-port"~~/div></li></~~span~~ol>~~=== Connection instruction of debugging serial port ===~~

<~~ol style~~span id="~~list~~the-setting-method-of-root-~~style~~user-~~type: decimal;"><li>First, you need to prepare a 3.3V USB~~automatic-login-in-tolinux-~~TTL module, and then insert the USB interface end of the USB~~desktop-toversion-~~TTL module into the USB interface of the computer.'''For better compatibility, it is recommended to use CH340 USB to TTL module, please do not use CP2102, PL2303 USB to TTL module.''''''Before purchasing a USB to TTL module, please confirm that the module supports a baud rate of 1500000.'''</li~~system"></olspan>

~~<div class~~=~~"figure">~~== The setting method of root user automatic login in Linux desktop version system ===

~~[[File~~# Execute the following command to set the desktop system to automatically log in as the root user :~~pi3b~~:{| class="wikitable" style="width:800px;" |-~~img155~~| orangepi@orangepi:~$ '''sudo desktop_login.~~png|576x115px~~sh root'''|~~07]]~~}

~~</div>~~

<li>~~The corresponding relationship between GND~~Then restart the system, ~~RXD~~ and ~~TXD pins of~~ the ~~debugging serial port of the development board is shown~~ root user will automatically log in to the ~~figure below~~desktop</li>~~</ol>~~ [[File:pi3b-img174.png]]

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-~~img156~~| <big>'''Note that if you log in to the desktop system as the root user, you cannot use pulseaudio in the upper right corner to manage audio devices.~~png|428x110px]]~~'''

'''Also note that this is not a bug, since pulseaudio is not allowed to run as root.'''</big>

|}

</ol>

<li>~~The GND, TXD and RXD pins of~~ Execute the ~~USB~~ following command to ~~TTL module need to be connected~~ set the desktop system to log in automatically with the ~~debugging serial port of the development board through a DuPont line~~orangepi user again</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo desktop_login.sh orangepi'''|}<~~blockquote~~/ol>~~a. Connect~~

b. === The ~~'''RX~~ method of disabling the ~~USB to TTL module is connected to~~ desktop in the ~~TX''' of the development board~~Linux desktop version system ===

~~c. The '''TX of~~ # First enter the ~~USB to TTL module is connected to~~ following command on the TXcommand line, ''' ~~of the development board~~<~~/blockquote><ol start="4"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>The schematic diagram of connecting the USB to TTL module~~ Please remember to ~~the computer and the Orange Pi development board is as follows~~add sudo permission</~~li></ol~~span>'''

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

~~[[File:pi3b~~<ol start="2" style="list-style-~~img157.png|524x189px|C~~type:~~\Users\orangepi\Desktop\用户手册插图\pi 3b\USB-to-TTL-module-to-~~decimal;"><li>Then restart the~~-computer.jpgUSB-to-TTL-module-to-~~Linux system and you will find that the~~-computer]]~~desktop will not be displayed</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo reboot'''|}</~~div~~ol><ol start="3" style="list-style-type: decimal;">~~'''~~<li>The ~~TX and RX of~~ steps to reopen the ~~serial port need to be cross~~desktop are as follows:<ol style="list-style-type: lower-~~connected. If you don’t want to carefully distinguish~~ alpha;"><li>First enter the ~~order of TX and RX, you can connect~~ following command on the ~~TX and RX of the serial port casually first. If there is no output in the test~~command line, ~~then exchange the order of TX and RX, so there is always a the order is right~~'''Please remember to add sudo permission'''</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo systemctl start lightdm.service'''|}</ol><~~span id~~ol start="2" style="~~how~~list-tostyle-~~use~~type: lower-alpha;"><li>After the~~-debugging-serial-port-on-~~command is executed, the~~-ubuntu-platform"~~desktop will be displayed</li></~~span~~ol>~~=== How to use the debugging serial port on the Ubuntu platform ===~~</li></ol>

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

# 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''' on the Ubuntu PC. Remember this node name, and then set the serial port software will be used== Onboard LED Light Test Instructions ==

~~test@test~~# 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:~~~$ '''ls /dev/ttyUSB*'''~~

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

~~<ol start="2" style="list~~::[[File:pi3b-~~style-type: decimal;"><li>Then use the following command to install putty on Ubuntu PC</li></ol>~~img175.png]]

~~test~~</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>'''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@~~test~~orangepi:~$ # '''cd /sys/class/leds/status_led'~~sudo apt~~''|}</ol><ol start="2" style="list-~~get update~~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# '''echo default-on > trigger'''|}</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# '''echo heartbeat > trigger'''|}</ol></li></ol>

== Network connection test~~@test:~$ '''sudo apt-get install -y putty'''~~==

<~~ol start~~span id="~~3" style="list~~ethernet-~~style~~port-~~type: decimal;~~test">~~<li>Then run putty, '''remember to add sudo permission'''~~</~~li></ol~~span>=== Ethernet port test ===

~~test@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, '''~~sudo putty~~No other configuration is required'''# The command to view the IP address in the Linux system of the development board is as follows

~~<ol start~~::{| class="4wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>After executing the putty command, the following interface will pop up</li></ol>~~|-| orangepi@orangepi:~$ '''ip addr show eth0'''

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

~~<ol start="5" style="list-style-type~~: ~~decimal;"><li>First select the setting interface of the serial port<~~link/~~li></ol>~~ether 4a:fe:2b:3d:17:1c brd ff:ff:ff:ff:ff:ff

~~[[File~~:~~pi3b-img159~~inet '''192.168.1.150'''/24 brd 192.168.1.~~png|359x352px]]~~255 scope global dynamic noprefixroute eth0

~~<ol start="6" style="list-style-type~~: ~~decimal;"><li>Then set the parameters of the serial port<ol style="list-style-type~~: ~~lower-alpha;"><li>Set Serial line to connect toas /dev/ttyUSB0（(Modified to the corresponding node name, generally /dev/ttyUSB0）</li><li>Set Speed(baud) as '''1500000'''（Serial port baud rate）</li><li>Set Flow control as None</li></ol></li></ol>~~valid_lft 43150sec preferred_lft 43150sec

~~<div class="figure">~~:inet6 fe80::9a04:3703:faed:23be/64 scope link noprefixroute

~~[[File~~:~~pi3b-img160.png|317x312px~~:valid_lft forever preferred_lft forever|~~09]]~~}

~~</div><ol start~~::{| class="7wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">~~<li>After setting the setting interface of the serial port, return to the Session interface<ol style="list-style-type: lower~~|-~~alpha;"><li>First select the Connection type as Serial</li>~~| <libig>~~Then click~~ '''When using ifconfig to view the ~~Open button to connect to~~ IP address, if the ~~serial port</li></ol></li>~~following information is displayed, it is because sudo is not added. The correct command is: sudo ifconfig'''</olbig>

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

~~[[File~~orangepi@orangepi:~~pi3b-img161.png|345x340px|10]]~~~$ '''ifconfig'''

~~</div><ol start="8" style="list-style-type: decimal;"><li>After starting~~ Command 'ifconfig' is available in the ~~development board, you can see the Log information output by the system from the opened serial port terminal</li></ol>~~following places

~~[[File:pi3b-img162.png|468x340px]]~~* /sbin/ifconfig

~~<~~* /~~span>=== How to use the debugging serial port on Windows platform ===~~usr/sbin/ifconfig

~~'''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~~ command could not be ~~used without buying a serial number.'~~located because '/sbin:/usr/sbin'is not included in the PATH environment variable.

~~<ol style="list-style-type: decimal;"><li>Download MobaXterm<ol style="list-style-type: lower-alpha;"><li>Download MobaXterm website as follows</li></ol></li></ol>~~This is most likely caused by the lack of administrative privileges associated with your user account.

~~[https~~ifconfig:~~//mobaxterm.mobatek.net/ https://mobaxterm.mobatek.net]~~command not found|}

~~<ol start~~::{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~After entering the MobaXterm download page, click~~ '''~~GET XOBATERM NOW!~~There are three ways to check the IP address after the development board starts:'''~~</li></ol>~~

~~[[File:pi3b-img163~~'''1.~~png|576x334px]]~~Connect the HDMI display, then log in to the system and use the ip addr show eth0 command to view the IP address'''

~~<ol start="3" style="list-style-type: lower-alpha;"><li>Then choose~~ '''2. Enter the ip addr show eth0 command in the debugging serial terminal to ~~download~~ view the ~~Home version</li></ol>~~IP address'''

~~[[File~~'''3. If there is no debugging serial port and no HDMI display, you can also check the IP address of the development board's network port through the router's management interface. However, in this method, some people often cannot see the IP address of the development board normally. If you can't see it, the debug method looks like this:~~pi3b-img164.png|353x231px]]~~'''

<ol ~~start="4"~~ style="list-style-type: ~~lower~~upper-alpha;"><li>~~Then select~~ '''First check whether the ~~Portable version~~Linux system has started normally. ~~After downloading~~If the green light of the development board is blinking, ~~you don’t need to install~~ itis generally started normally. If only the red light is on, ~~just open~~ it ~~and~~ 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 itthe debugging serial port to view the IP address'''</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~~'''In addition, ~~you can get~~ it should be noted that the ~~executable software of MobaXterm, and then double-click to open~~development board DHCP automatically assigns an IP address without any settings.'''</~~li></ol~~big>|}

~~[[File~~<ol start="4" style="list-style-type:~~pi3b-img166.png|576x81px]]~~decimal;"><li>The command to test the network connectivity is as follows, the '''ping''' command can be interrupted through the shortcut key of '''Ctrl+C'''</li>

~~<ol start~~{| class="3wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<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), if you can’t see the port number, please use~~ orangepi@orangepi:~$ '''~~Driver Master~~ping www.baidu.com -I eth0''' ~~to scan and install the driver for the USB to TTL serial port chip</li><li>Select the baud rate of the serial port as '''1500000'''</li><li>Finally click the "'''OK'''" button to complete the setting</li></ol></li></ol>~~

~~<div class="figure">~~PING www.a.shifen.com (14.215.177.38) from 192.168.1.12 eth0: 56(84) bytes of data.

~~[[File~~64 bytes from 14.215.177.38 (14.215.177.38):~~pi3b-img167~~icmp_seq=1 ttl=56 time=6.~~png|575x438px|11]]~~74 ms

~~</div><ol start~~64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq=~~"4" style~~2 ttl=~~"list-style-type: decimal;"><li>After clicking the "'''OK'''" button, you will enter the following interface~~56 time=6. ~~At this time, start the development board and you can see the output information of the serial port</li></ol>~~80 ms

~~<div class~~64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq=~~"figure">~~3 ttl=56 time=6.26 ms 64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq=4 ttl=56 time=7.27 ms ^C

~~[[File:pi3b~~-~~img168~~-- www.a.~~png|575x291px|12]]~~shifen.com ping statistics ---

~~</div>== Instructions for using the 5v pin in the 40pin interface of the development board to supply power ==~~4 packets transmitted, 4 received, 0% packet loss, time 3002ms

~~'''The power supply method we recommend for the development board is to use the 5V~~rtt min/~~3A or 5V~~avg/~~4A Type C interface power cord to plug into the Type-C power interface of the development board for power supply~~max/mdev = 6.260/6. 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 board770/7. ~~If the use is unstable, please switch back to the Type~~275/0.373 ms|}</ol>

~~# First, you need to prepare a power cord as shown in the figure below~~=== WIFI connection test ===

~~<div~~ {| class="~~figure~~wikitable" style="background-color:#ffffdc;width:800px;"|-| <big>'''Please do not connect to WIFI by modifying the /etc/network/interfaces configuration file. There will be problems connecting to the WIFI network in this way.'''</big>|}

~~[[File:pi3b~~==== The server image connects to WIFI through commands ====

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <~~/div~~big>'''~~Please purchase~~ When the ~~power cord shown~~ 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 ~~picture above by yourself~~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.'''</big>|}

<ol ~~start="2"~~ style="list-style-type: decimal;"><li>~~Use the 5V pin~~ First log in ~~the 40pin interface to supply power~~ to the ~~development board. The connection method of~~ Linux system, there are the ~~power line is as follows~~following three ways

<li>~~The USB A port of~~ If the ~~power cord shown~~ development board is connected with a network cable, you can remotely log 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''')~~Linux system through ssh</li><li>~~The red DuPont line needs to be plugged into the 5V pin of~~ If the development board ~~40pin</li><li>The black Dupont wire needs~~ is connected to ~~be inserted into~~ the ~~GND pin of~~ debugging serial port, you can use the ~~40pin interface~~serial port terminal to log in to the Linux system</li><li>~~The position of the 5V pin and GND pin of the 40pin interface on~~ If the development board is ~~shown in~~ connected to the ~~figure below~~HDMI display, ~~remember not~~ you can log in to ~~reverse~~ the ~~connection~~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</olli> {| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''nmcli dev wifi'''|}

~~[[File:pi3b-img170.png|365x71px]]~~<div class="figure">

~~~~img176.png]]

</div></ol><ol start="3" style= ~~'''Instructions for~~ "list-style-type: decimal;"><li>Then use ~~of Ubuntu~~the nmcli command to connect to the scanned WIFI hotspot, where:</~~Debian Server and Xfce desktop system''' =~~li>

:a. '''~~The content of this chapter is written based on~~ wifi_name''' needs to be replaced with the ~~images~~ name of the ~~Linux server version and the xfce desktop version.'''~~WIFI hotspot you want to connect to

~~== Supported Linux image types and kernel versions ==~~:b. '''wifi_passwd''' needs to be replaced with the password of the WIFI hotspot you want to connect to

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

|-

|}

</ol>

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

~~== Linux System adaptation ==~~ {| class="wikitable" style="width:800px;"

|-

| ~~style="text-align: left;"| '''Function'''| style="text-align: left;"| '''Debian11'''| style="text-align: left;"| '''Ubuntu20.04'''| style="text-align: left;"| '''Ubuntu22.04'''~~|-~~| style="text-align: left;"| '''USB2.0x3'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''USB3.0x1'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''M.2 NVMe SSD Start'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''WIFI'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Bluetooth'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''GPIO（40pin）'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''UART（40pin）'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''SPI（40pin）'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''I2C（40pin）'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''PWM（40pin）'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''PWM fan interface'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''3pin Debug serial port'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''EMMC'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''TF card start'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI Video'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI Audio'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Camera'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''LCD'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Edp Display'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Gigabit Ethernet port'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align~~orangepi@orangepi: ~~left;"| '''Network port status light'~~~$ ''~~| style="text-align: left;"|~~ 'ip addr show wlan0''OK'''~~| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''headphone playback'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''headphone recording'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''LED Light'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''RTC'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''GPU'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''NPU'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''VPU'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''watchdog test'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Chromium Hard solution video'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|}

~~== The format of Linux commands in this manual ==~~11: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~# In this manual, all commands that need to be entered in the Linux system will be marked with the following box~~:link/ether 23:8c:d6:ae:76:bb brd ff:ff:ff:ff:ff:ff

~~As shown below, the content in the yellow box indicates the content that needs special attention, except for the commands in it~~:inet '''192.168.1.11'''/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0

~~<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></ol>~~</li></ol>~~valid_lft 259192sec preferred_lft 259192sec

~~'''orangepi@orangepi~~:~~~$ sudo apt update'''~~inet6 240e:3b7:3240:c3a0:c401:a445:5002:ccdd/64 scope global dynamic noprefixroute

~~'''root@orangepi~~:~~~#''' '''vim /boot/boot.cmd'''~~:valid_lft 259192sec preferred_lft 172792sec

~~'''test@test~~:~~~$ ssh [mailto~~inet6 fe80:~~root@192.168.1.36 root@192.168.1.]xxx'''~~:42f1:6019:a80e:4c31/64 scope link noprefixroute

::valid_lft forever preferred_lft forever|}</ol><ol start="5" style="list-style-type: decimal;"><li>Use the '''ping'''~~root@~~command to test~~:~# ls~~the connectivity of the wifi network, and the '''ping''' command can be interrupted through the shortcut key '''Ctrl+C'''</li>

~~<ol start~~{| class="2wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>'''root~~|-| orangepi@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~~ping www. ~~When executing a privileged command, you need to add '''sudo'''</li><li>'''root@~~orangepi:~#''' The prompt indicates that this command is entered in the Linux system of the development board, and the # at the end of the prompt indicates that the current user of the system is the root user, who can execute any desired command</li>~~<li>'''test@test:~$''' The prompt indicates that this command is entered in the Ubuntu PC or Ubuntu virtual machine, not in the Linux system of the development board~~. ~~The $ at the end of the prompt indicates that the current user of the system is an ordinary user. When executing privileged commands, sudo needs to be added '''sudo'''</li><li>~~org -I wlan0'''root@test:~#''' The prompt indicates that this command is entered in the Ubuntu PC or Ubuntu virtual machine, not in the Linux system of the development board. The # at the end of the prompt indicates that the current user of the system is the root user and can execute any command you want</li></ol>

~~<ol start="3" style="list-style-type: decimal;"><li>What are the commands that need to be entered?<ol style="list-style-type~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0: ~~lower-alpha;"><li>As shown below, '''the black bold part''' is the command that needs to be input, and the content below the command is the output content~~ 56(~~some commands have output, some may not~~84)~~, and this part~~ bytes of ~~the content does not need to be input</li></ol></li></ol>~~data.

~~root@orangepi~~64 bytes from 182.92.236.130 (182.92.236.130):~~~# '''cat /boot/orangepiEnv~~icmp_seq=1 ttl=52 time=43.~~txt'''~~5 ms

~~'''verbosity~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=~~7'''~~2 ttl=52 time=41.3 ms

~~bootlogo~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=~~false~~3 ttl=52 time=44.9 ms

~~'''console~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=~~serial'''~~4 ttl=52 time=45.6 ms

~~<ol start~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=~~"2" style~~5 ttl=~~"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 command52 time=48. ~~In addition, there are spaces in different parts of the command, please don’t miss it</li></ol>~~8 ms

~~orangepi@orangepi:~$ '''echo \'''~~^C

~~'''"deb [arch=$(dpkg~~ --~~print~~-~~architecture) \'''~~www.orangepi.org ping statistics ---

~~'''signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] \'''~~5 packets transmitted, 5 received, 0% packet loss, time 4006ms

~~'''https:~~rtt min/avg/~~download~~max/mdev = 41.321/44.864/48.~~docker~~834/2.~~com~~484 ms|}</~~Linux~~ol></~~debian \'''~~span>

~~'''$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null'''~~==== The server image connects to WIFI in a graphical way ====

<~~span id~~ol style="~~linux~~list-style-type: decimal;"><li>First log in to the Linux system, there are the following three ways</li><ol style="list-~~login~~style-type: lower-~~instructions~~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)</~~span~~p></li>== <li>If the development board is connected to the HDMI display, you can log in to the Linux system ~~login instructions ==~~through the HDMI display terminal</li></ol>

<~~span id="linux-system-default-login-account-and-password"~~li>Then enter the nmtui command in the command line to open the wifi connection interface</~~span~~li>~~=== Linux system default login account and password ===~~ {| class="wikitable" style="width:800px;"

|-

|}

</ol>

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

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

~~'''When the wrong password is prompted, or there is a problem with the ssh connection, please note that as long as~~ [[File:pi3b-img178.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then you ~~are using~~ can see all the ~~Linux image provided by Orange Pi, please do not suspect that the above password is wrong, but look for other reasons.'''~~searched WIFI hotspots</li>

<~~span id~~div class="~~how-to-set-automatic-terminal-login-in-linux-system~~figure">~~=== 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 orangepi '''orangepi'''~~[[File:pi3b-img179.png]]

~~[[File~~</div></ol><ol start="6" style="list-style-type:~~pi3b-img171.png|351x198px]]~~decimal;"><li>Select the WIFI hotspot you want to connect to, then use the Tab key to position the cursor on '''Activate''' and press Enter</li>

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

~~orangepi@orangepi~~[[File:~~~$ '''sudo auto_login_cli~~pi3b-img180.~~sh root'''~~png]]

</div></ol><ol start="37" style="list-style-type: decimal;"><li>~~Use~~ Then a dialog box for entering a password will pop up, enter the ~~following command~~ corresponding password in '''Password''' and press Enter to start connecting to ~~disable automatic login terminal~~WIFI</li~~></ol~~>

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

~~<ol start="4" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Use the following command to set the orangepi user to automatically log in to the terminal again</li></ol>~~img181.png]]

~~orangepi@orangepi~~</div></ol><ol start="8" style="list-style-type:~~~$ '''sudo auto_login_cli.sh orangepi'''~~decimal;"><li>After the WIFI connection is successful, a "*" will be displayed in front of the connected WIFI name</li>

<~~span id~~div class="~~instructions-for-automatic-login-of-linux-desktop-version-system~~figure">~~=== 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~~[[File:pi3b-img182.png]]

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

~~[[File~~11:~~pi3b-img172.png|576x324px|1]]~~wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

<:link/~~div><ol start="2" style="list-style-type~~ether 24:8c:d3:aa:76:bb brd ff:ff:ff:ff:ff: ~~decimal;"><li>Run the following command to prohibit the desktop system from automatically logging into the desktop</li></ol>~~ff

~~orangepi@orangepi~~:~$ inet '''~~sudo disable_desktop_autologin~~192.168.1.sh11'''/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0

~~<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]] is required to enter the system<div class="figure">~~:valid_lft 259069sec preferred_lft 259069sec

~~[[File~~:~~pi3b-img173.png|569x320px|IMG_256]]~~inet6 240e:3b7:3240:c4a0:c401:a445:5002:ccdd/64 scope global dynamic noprefixroute

~~</div></li></ol>~~::valid_lft 259071sec preferred_lft 172671sec

~~<~~:inet6 fe80::42f1:6019:a80e:4c31/~~span>=== The setting method of root user automatic login in Linux desktop version system ===~~64 scope link noprefixroute

~~# Execute~~ ::valid_lft forever preferred_lft forever|}</ol><ol start="10" style="list-style-type: decimal;"><li>Use the ~~following~~ '''ping''' command to ~~set~~ test the ~~desktop system to automatically log in as~~ connectivity of the wifi network, and the '''ping''' command can be interrupted through the ~~root user~~shortcut key '''Ctrl+C'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ping www.orangepi.org -I wlan0'''

PING www.orangepi~~@orangepi~~.org (182.92.236.130) from 192.168.1.49 wlan0:~~~$ '''sudo desktop_login~~56(84) bytes of data.~~sh root'''~~

~~<ol start~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=~~"2" style~~1 ttl=~~"list-style-type: decimal;"><li>Then restart the system, and the root user will automatically log in to the desktop</li></ol>~~52 time=43.5 ms

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

~~'''Note that if you log in to the desktop system as the root user, you cannot use pulseaudio in the upper right corner to manage audio devices~~64 bytes from 182.~~'''~~92.236.130 (182.92.236.130): icmp_seq=3 ttl=52 time=44.9 ms

~~'''Also note that this is not a bug, since pulseaudio is not allowed to run as root~~64 bytes from 182.~~'''~~92.236.130 (182.92.236.130): icmp_seq=4 ttl=52 time=45.6 ms

~~<ol start~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=~~"3" style~~5 ttl=~~"list-style-type: decimal;"><li>Execute the following command to set the desktop system to log in automatically with the orangepi user again</li></ol>~~52 time=48.8 ms

~~orangepi@orangepi:~$ '''sudo desktop_login.sh orangepi'''~~^C

~~=== The method of disabling the desktop in the Linux desktop version system ===~~

~~# First enter the following command on the command line，'''Please remember to add sudo permission'''~~5 packets transmitted, 5 received, 0% packet loss, time 4006ms

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

~~<ol start~~=~~"2" style~~=~~"list-style-type: decimal;"><li>Then restart the Linux system and you will find that the~~ == Test method of desktop ~~will not be displayed</li></ol>~~image ====

~~orangepi@orangepi~~# Click the network configuration icon in the upper right corner of the desktop (please do not connect the network cable when testing WIFI) :~$ :[[File:pi3b-img183.png]] <ol start="2" style="list-style-type: decimal;"><li>Click '''~~sudo reboot~~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>

[[File:pi3b-img184.png]]

</ol>

<li>Then enter the password of the WIFI hotspot, and then click '''Connect''' to start connecting to WIFI<p/li>~~The steps to reopen the desktop are as follows~~ [[File:pi3b-img185.png]]</pol><ol start="4" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~First enter~~ After connecting to WIFI, you can open the browser to check whether you can access the Internet. The entrance of the ~~following command on~~ browser is shown in the ~~command line，'''Please remember to add sudo permission'''~~figure below</li> [[File:pi3b-img186.png]]</ol></ol start="5" style="list-style-type: decimal;"><li>If you can open other web pages after opening the browser, it means that the WIFI connection is normal</olli>

~~orangepi@orangepi~~[[File:~~~$ '''sudo systemctl start lightdm~~pi3b-img187-1.~~service'''~~png]]</ol>

~~<ol start~~=~~"2" style~~=~~"list-style-type: lower-alpha;"><li>After the command is executed, the desktop will be displayed</li></ol>~~= How to set a static IP address ===

~~'''Please do not set a static IP address by modifying the /etc/network/interfaces configuration file.'''</~~span~~big>~~== Onboard LED Light Test Instructions ==|}

~~# There are three LED lights on~~ ==== Use the ~~figure below:~~nmtui command to set a static IP address ====

~~<div class="figure">~~# First run the '''nmtui''' command

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-~~img175.png~~|~~425x115px~~orangepi@orangepi:~$ '''nmtui'''|~~C:\Users\orangepi\Desktop\用户手册插图\pi 3b\3.5.Onboard-LED-Light-Test-Instructions(1).jpg3.5.Onboard-LED-Light-Test-Instructions(1)]]~~}

~~</div>~~

<li>~~~~Then select '''~~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~~Edit a connection'''~~</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~~press Enter</li~~></ol~~>

[[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 '''~~Note that the following operations should be performed under the root user.~~Wired connection 1'''.</li>

[[File:pi3b-img189.png]]</ol><ol start="4" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~First enter~~ Then select '''Edit''' with the ~~setting directory of~~ '''Tab''' key and press the ~~green light~~Enter key</li~~></ol~~>

~~root@orangepi~~[[File:~# pi3b-img190.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then use the Tab key to move the cursor to the '''~~cd /sys/class/leds/status~~<Automatic>'''position shown in the figure below to configure IPv4</li>

[[File:pi3b-img191.png]]</ol><ol start="26" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The command to set~~ Then press Enter, select '''Manual''' with the ~~green light~~ up and down arrow keys, and press Enter to ~~stop flashing is as follows~~confirm</li~~></ol~~>

~~root@orangepi~~[[File:pi3b-img192.png]]</~~sys~~ol><ol start="7" style="list-style-type: decimal;"><li>The display after selection is shown in the figure below</~~class/leds/work# '''echo none > trigger'''~~li>

[[File:pi3b-img193.png]]</ol><ol start="38" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The command~~ Then move the cursor to ~~set~~ the ~~green light to be on is as follows~~'''<Show>'''</li~~></ol~~>

~~root@orangepi~~[[File:pi3b-img194.png]]</~~sys/class/leds/work# '''echo default~~ol><ol start="9" style="list-style-~~on &gt~~type: decimal; ~~trigger'''~~"><li>Then press Enter, the following setting interface will pop up after entering</li>

[[File:pi3b-img195.png]]</ol><ol start="410" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The command~~ Then you can set the IP address (Addresses), gateway (Gateway) and DNS server address in the position shown in the figure below (there are many other setting options in it, please explore by yourself), '''Please set it according to your specific needs, the value set in the ~~green light to flash~~ figure below is ~~as follows~~just an example</lispan>'''</olli>

~~root@orangepi~~[[File:pi3b-img196.png]]</~~sys/class/leds/work#~~ ol><ol start="11" style="list-style-type: decimal;"><li>After setting, move the cursor to'''~~echo heartbeat~~ <OK> ~~trigger~~'''in the lower right corner, and press Enter to confirm</li>

[[File:pi3b-img197.png]]<~~span id~~/ol><ol start="12" style="~~network~~list-~~connection~~style-~~test~~type: decimal;"><li>Then click'''<Back>''' to return to the previous selection interface</~~span~~li>~~== Network connection test ==~~

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

~~# First, insert one end of~~ [[File:pi3b-img199.png]]</ol><ol start="14" style="list-style-type: decimal;"><li>Then select the network ~~cable into the Ethernet~~ interface ~~of the development board~~that needs to be set, such as '''Wired connection 1''', ~~and connect~~ then move the ~~other end of the network cable~~ cursor to ~~the router~~'''<Deactivate>''', and ~~ensure that the network is unblocked# After the system starts, it will automatically assign an IP address~~ press Enter to ~~the Ethernet card through DHCP,~~ disable '''~~No other configuration is required~~Wired connection 1'''~~# The command to view the IP address in the Linux system of the development board is as follows~~</li>

~~orangepi@orangepi~~[[File:~$ pi3b-img200.png]]</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 '''~~ip addr show eth0~~Wired connection 1''', so that the static IP address set earlier will take effect</li>

2[[File: ~~eth0~~pi3b-img201.png]]</ol><ol start="16" style="list-style-type: decimal;"><li>Then you can exit nmtui through the'''<~~BROADCAST,MULTICAST,UP,LOWER_UP~~Back> ~~mtu 1500 qdisc mq state UP group default qlen 1000~~''' and '''Quit''' buttons</li>

~~link/ether 4a~~[[File:~~fe:2b:3d~~pi3b-img202.png]] [[File:pi3b-img203.png]]</ol><ol start="17" style="list-style-type:~~1c brd ff:ff:ff:ff:ff:ff~~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>

~~inet~~ {| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~192.168.1.150~~ip addr show eth0'''~~/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0~~

~~valid_lft 43150sec preferred_lft 43150sec~~3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~inet6 fe80~~:link/ether 5e:ac:14:a5:92:~~9a04~~b3 brd ff:~~3703~~ff:~~faed~~ff:~~23be/64 scope link noprefixroute~~ff:ff:ff

~~valid_lft forever preferred_lft forever~~:inet '''192.168.1.177'''/24 brd 192.168.1.255 scope global noprefixroute eth0

~~'''When using ifconfig to view the IP address, if the following information is displayed, it is because sudo is not added. The correct command is~~: ~~sudo ifconfig'''~~:valid_lft forever preferred_lft forever

~~orangepi@orangepi~~:~~~$ '''ifconfig'''~~inet6 241e:3b8:3240:c3a0:e269:8305:dc08:135e/64 scope global dynamic noprefixroute

~~Command 'ifconfig' is available in the following places~~::valid_lft 259149sec preferred_lft 172749sec

* :inet6 fe80::957d:bbbe:4928:3604/~~sbin/ifconfig~~64 scope link noprefixroute

* ::valid_lft forever preferred_lft forever|}</~~usr~~ol><ol start="18" style="list-style-type: decimal;"><li>Then you can test the connectivity of the network to check whether the IP address is configured OK, and the '''ping''' command can be interrupted through the shortcut key '''Ctrl+C'''</~~sbin/ifconfig~~li>

~~The command could not be located because~~ {| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ ''~~/sbin:/usr/sbin~~' ~~is not included in the PATH environment variable~~ping 192.168.1.47 -I eth0'''

~~This is most likely caused by the lack~~ PING 192.168.1.47 (192.168.1.47) from 192.168.1.188 eth0: 56(84) bytes of ~~administrative privileges associated with your user account~~data.

~~ifconfig~~64 bytes from 192.168.1.47: ~~command not found~~icmp_seq=1 ttl=64 time=0.233 ms

~~'''There are three ways to check the IP address after the development board starts~~64 bytes from 192.168.1.47:~~'''~~icmp_seq=2 ttl=64 time=0.263 ms

~~# '''Connect the HDMI display, then log in to the system and use the ip addr show eth0 command to view the IP address'''# '''Enter the ip addr show eth0 command in the debugging serial terminal to view the IP address'''# '''If there is no debugging serial port and no HDMI display, you can also check the IP address of the development board’s network port through the router’s management interface~~64 bytes from 192. ~~However, in this method, some people often cannot see the IP address of the development board normally~~168. ~~If you can't see it, the debug method looks like this~~1.47:~~'''~~icmp_seq=3 ttl=64 time=0.273 ms

~~<ol style~~64 bytes from 192.168.1.47: icmp_seq=4 ttl=64 time=~~"list-style-type: upper-alpha;"><li>'''First check whether the Linux system has started normally. If the green light of the development board is blinking, it is generally started normally~~0. ~~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>~~269 ms

~~'''In addition, it should be noted that the development board DHCP automatically assigns an IP address without any settings~~64 bytes from 192.~~'''~~168.1.47: icmp_seq=5 ttl=64 time=0.275 ms

~~<ol start="4" style="list-style-type: decimal;"><li>The command to test the network connectivity is as follows, the '''ping''' command can be interrupted through the shortcut key of '''Ctrl+~~^C~~'''</li></ol>~~

~~orangepi@orangepi:~$ '''ping www~~--- 192.168.~~baidu~~1.~~com~~ 47 ping statistics ---~~I eth0'''~~

~~PING www.a.shifen.com (14.215.177.38) from 192.168.1.12 eth0: 56(84) bytes of data.~~5 packets transmitted, 5 received, 0% packet loss, time 4042ms

~~64 bytes from 14~~rtt min/avg/max/mdev = 0.~~215~~233/0.~~177~~262/0.~~38 (14~~275/0.~~215.177.38): icmp_seq=1 ttl=56 time~~015 ms|}</ol>

~~64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq~~=~~2 ttl~~=~~56 time~~=~~6.80 ms~~= Use the nmcli command to set a static IP address ====

~~64 bytes from 14~~<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.~~215.177.38~~ '''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 (~~14.215.177.38~~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:~$ '''nmcli con show''' NAMEUUID TYPE DEVICE '''orangepi'''cfc4f922-ae48-46f1-84e1-2f19e9ec5e2awifi wlan0 '''Wired connection 1'''9db058b7-7701-37b8-9411-efc2ae8bfa30ethernet eth0 |}</ol></li></ol>

~~64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq~~<ol start=~~4 ttl~~"3" style=~~56 time=7.27 ms~~"list-style-type: decimal;"><li>Then enter the following command, where</li>

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

~~--- www~~:b.aAfter '''ipv4.~~shifen.com ping statistics ---~~addresse''' is the static IP address to be set, which can be modified to the value you want to set

~~4 packets transmitted, 4 received, 0% packet loss, time 3002ms~~:c. '''ipv4.gateway''' indicates the address of the gateway

~~rtt min/avg/max/mdev~~ ::{| class= ~~6.260/6.770/7.275/0.373 ms~~"wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''nmcli con mod "Wired connection 1" \'''

~~=== WIFI connection test ===~~'''ipv4.addresses "192.168.1.110" \'''

'''~~Please do not connect to WIFI by modifying the /etc/network/interfaces configuration file~~ipv4. ~~There will be problems connecting to the WIFI network in this way~~gateway "192.168.1.1" \'''

~~==== WIFI The server image connects to WIFI through commands ====~~'''ipv4.dns "8.8.8.8" \'''

'''~~When~~ ipv4.method "manual"'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then restart the ~~development board is not connected to Ethernet, not connected to HDMI display, but only connected to~~ Linux system</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo reboot'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>Then re-enter the ~~serial port, it is recommended to~~ Linux system and use the ~~commands demonstrated in this section to connect~~ '''ip addr show eth0''' command to see that 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 IP address has been set to the ~~WIFI network.~~desired value</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ip addr show eth0'''

~~<ol style="list-style-type~~3: ~~decimal;"><li>First log in to the Linux system, there are the following three ways<ol style="list-style-type~~eth0: ~~lower-alpha~~<">~~<li>If the development board is connected with a network cable~~BROADCAST, ~~you can remotely log in to the Linux system through ssh</li><li>If the development board is connected to the debugging serial port~~MULTICAST, ~~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~~UP, ~~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>~~LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~orangepi@orangepi~~:~~~$ '''nmcli dev wifi'''~~link/ether 5e:ae:14:a5:91:b3 brd ff:ff:ff:ff:ff:ff

:inet '''<~~div class~~span style="~~figure~~color:#FF0000">192.168.1.110'''/32 brd 192.168.1.110 scope global noprefixroute eth0

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

~~</div><ol start="3" style="list-style-type~~: ~~decimal;"><li>Then use the nmcli command to connect to the scanned WIFI hotspot, where~~inet6 240e:3b7:3240:c3a0:97de:1d01:b290:~~</li><~~fe3a/~~ol>~~64 scope global dynamic noprefixroute

~~a. '''wifi_name''' needs to be replaced with the name of the WIFI hotspot you want to connect to~~::valid_lft 259183sec preferred_lft 172783sec

~~b. '''wifi_passwd''' needs to be replaced with the password of the WIFI hotspot you want to connect to~~:inet6 fe80::3312:861a:a589:d3c/64 scope link noprefixroute

~~orangepi@orangepi~~:~~~$ '''nmcli dev wifi connect wifi_name password wifi_passwd'''~~:valid_lft forever preferred_lft forever|}</ol>

~~Device 'wlan0' successfully activated with 'cf937f88-ca1e-4411-bb50-61f402eef293'.~~== SSH remote login development board ==

~~<ol start~~{| class="4wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~You can view~~ '''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 ~~wifi through~~ the development board.'''~~ip addr show wlan0''' command~~</~~li></ol~~big>|}

~~orangepi@orangepi:~$ '''ip addr show wlan0'''~~=== SSH remote login development board under Ubuntu ===

~~11: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~# Obtain the IP address of the development board# Then you can remotely log in to the Linux system through the ssh command

~~link/ether 23~~:8c:d6{| class="wikitable" style="width:ae800px;" |-| test@test:76~$ '''ssh [mailto:~~bb brd ff:ff:ff:ff:ff:ff~~root@192.168.1.36 root@192.168.1.]xxx'''        (Need to be replaced with the IP address of the development board)

~~inet '''~~root@192.168.1.11xx's password:        (Enter the password here, the default password is orangepi)|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that when entering the password, the specific content of the entered password will not be displayed on the screen</~~24 brd 192~~span>, please do not think that there is any fault, just press Enter after inputting.~~168~~'''</big>|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''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.~~1.255 scope global dynamic noprefixroute wlan0~~'''</big>|}

~~valid_lft 259192sec preferred_lft 259192sec~~<ol start="3" style="list-style-type: decimal;"><li>After successfully logging in to the system, the display is as shown in the figure below</li>

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

~~valid_lft 259192sec preferred_lft 172792sec~~[[File:pi3b-img204.png]]

~~inet6 fe80::42f1~~</div>{| class="wikitable" style="background-color:~~6019~~#ffffdc;width:~~a80e~~800px;" |-| <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. Is it possible to connect:~~4c31/64 scope link noprefixroute~~'''

~~valid_lft forever preferred_lft forever~~

~~5) Use the~~ root@orangepi:~# '''~~ping''' command to test the connectivity of the wifi network, and the '''ping''' command can be interrupted through the shortcut key '''Ctrl+C~~reset_ssh.sh'''

~~orangepi@orangepi:~$ '''ping www.orangepi.org -I wlan0'''~~

~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0: 56(84) bytes of data~~'''If it still doesn't work, try to reset the system.'''</big>|}</ol>

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~=~~1 ttl~~=~~52 time~~=~~43.5 ms~~SSH remote login development board under Windows ===

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=2 ttl=52 time=41.3 ms~~# 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

~~64 bytes from 182.92.236.130 (182.92.236.130)~~: ~~icmp_seq=3 ttl=52 time=44~~:a.~~9 ms~~Open '''Session'''

~~64 bytes from 182.92.236.130 (182.92.236.130)~~: ~~icmp_seq=4 ttl=52 time=45~~:b.~~6 ms~~Then select '''SSH''' in '''Session Setting'''

~~64 bytes from 182.92.236.130 (182.92.236.130)~~: ~~icmp_seq=5 ttl=52 time=48~~:c.~~8 ms~~Then enter the IP address of the development board in the '''Remote host'''

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

~~--- www~~::e.~~orangepi.org ping statistics ---~~Finally click '''OK'''

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

~~rtt min/avg/max/mdev = 41~~::[[File:pi3b-img205.~~321/44.864/48.834/2.484 ms~~png]]

<~~span id~~/div><ol start="3" style="~~the~~list-~~server-image-connects~~style-type: decimal;"><li>Then you will be prompted to~~-wifi-in-~~enter apassword. The default passwords for root and orangepi users are orangepi</li>{| class="wikitable" style="background-~~graphical~~color:#ffffdc;width:800px;" |-~~way~~| <big>'''Note that when entering the password, the specific content of the entered password will not be displayed on the screen, please do not think that there is any fault, just press Enter after inputting.'''</big>~~==== The server image connects to WIFI in a graphical way ====~~|}

~~1) First log in to the Linux system, there are the following three ways~~<div class="figure">

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

<~~!--~~ /div></ol><ol start="4" style="list-style-type: decimal;"># ~~# Then enter~~ <li>After successfully logging in to the system, the ~~nmtui command~~ display is as shown in the ~~command line to open the wifi connection interface~~figure below</li>

~~orangepi@orangepi~~[[File:~~~$ '''nmtui'''~~pi3b-img207.png]]</ol> == The method of uploading files to the Linux system of the development board == === How to upload files to the development board Linux system in Ubuntu PC ===

<~~ol start~~span id="~~3" style="list~~how-to-upload-files-using-the-~~style~~scp-~~type: decimal;~~command"><li/span>~~Enter~~ ==== How to upload files using the ~~nmtui~~ scp command ~~to open the interface as shown below</li></ol>~~====

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

~~<ol start="4" style="list-style-type~~: ~~decimal;"><li>Select~~ :a. '''~~Activate a connect~~file_path''' ~~and press Enter</li></ol>~~: need to be replaced with the path of the file to be uploaded

~~[[File~~:~~pi3b-img178~~:b.~~png|349x216px]]~~'''orangepi''': 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="5" style="list-style-type~~: ~~decimal;"><li>Then you can see all~~ :c. '''192.168.xx.xx''': It is the IP address of the development board, please modify it according to the ~~searched WIFI hotspots</li></ol>~~actual situation

~~<div class="figure">~~::d. '''/home/orangepi''': The path in the Linux system of the development board, which can also be modified to other paths

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-~~img179~~| test@test:~$ '''scp file_path orangepi@192.~~png|426x270px~~168.xx.xx:/home/orangepi/'''|~~16]]~~}

~~</div>~~<ol start="62" style="list-style-type: decimal;"><li>~~Select the WIFI hotspot~~ If you want to ~~connect to~~upload a folder, ~~then use the Tab key~~ you need to ~~position~~ add the ~~cursor on '''Activate''' and press Enter~~-r parameter</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''scp -r dir_path orangepi@192.168.xx.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<~~div~~ /li>{| class="~~figure~~wikitable" style="width:800px;" |-| test@test:~$ '''man scp'''|}</ol>

~~[[File:pi3b-img180.png|474x298px|17]]~~==== How to upload files using filezilla ====

~~</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~~ # First install filezilla in ~~'''Password''' and press Enter to start connecting to WIFI</li></ol>~~Ubuntu PC

~~<div~~ ::{| class="~~figure~~wikitable">style="width:800px;" |-| test@test:~$ '''sudo apt install -y filezilla'''|}

~~[[File~~<ol start="2" style="list-style-type:~~pi3b-img181.png|480x308px|18]]~~decimal;"><li>Then use the following command to open filezilla</li>

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''filezilla'''|}</~~div~~ol><ol start="83" style="list-style-type: decimal;"><li>~~After the WIFI connection~~ The interface after filezilla is opened is ~~successful~~as follows, ~~a "*" will be displayed in front of~~ and the display under the remote site on the ~~connected WIFI name~~right is empty</li~~></ol~~>

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

</div></ol><ol start="94" style="list-style-type: decimal;"><li>~~You can view~~ The method of connecting the ~~IP address of wifi through~~ development board is shown in the ~~'''ip addr show wlan0''' command~~figure below</li~~></ol~~>

~~orangepi@orangepi:~$ '''ip addr show wlan0'''~~<div class="figure">

11[[File: ~~wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~pi3b-img209.png]]

~~link~~</~~ether 24~~div></ol><ol start="5" style="list-style-type:~~8c:d3:aa:76:bb brd ff:ff:ff:ff:ff:ff~~decimal;"><li>Then choose to '''save the password''', and then click '''OK'''</li>

~~inet~~ [[File:pi3b-img210.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then choose to always '''trust this host''', and then click '''~~192.168.1.11~~OK'''</~~24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0~~li>

~~valid_lft 259069sec preferred_lft 259069sec~~<div class="figure">

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

~~valid_lft 259071sec preferred_lft 172671sec~~</div></ol><ol start="7" style="list-style-type: decimal;"><li>After the connection is successful, you can see the directory structure of the development board Linux file system on the right side of the filezilla software</li>

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

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

</div></ol><ol start="108" style="list-style-type: decimal;"><li>~~Use~~ Then select the ~~'''ping''' command~~ path to be uploaded to ~~test~~ the ~~connectivity~~ development board on the right side of the ~~wifi network~~filezilla software, and then select the ~~'''ping''' command can~~ file to be ~~interrupted through~~ 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 ~~shortcut key '''Ctrl+C'''~~development board.</li> <~~/ol~~div class="figure">

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

~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0~~</div></ol><ol start="9" style="list-style-type: ~~56(84) bytes~~ decimal;"><li>After the upload is complete, you can go to the corresponding path in the Linux system of ~~data.~~the development board to view the uploaded file</li>

~~64 bytes~~ <li>The method of uploading a folder is the same as that of uploading a file, so I won't go into details here</li></ol>

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

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~==== How to upload files using filezilla ==~~3 ttl~~=~~52 time~~=~~44.9 ms~~

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=4 ttl=52 time=45.6 ms~~# First download the installation file of the Windows version of the filezilla software, the download link is as follows

~~64 bytes from 182.92.236.130 (182.92.236.130)~~: ~~icmp_seq~~:{| class=~~5 ttl~~"wikitable" style=~~52 time~~"width:800px;" |-| '''https://filezilla-project.org/download.php?type=~~48.8 ms~~client'''|}

^C<div class="figure">

::[[File:pi3b-~~-- www.orangepi~~img214.~~org ping statistics ---~~png]]

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

~~rtt min/avg/max/mdev = 41~~::[[File:pi3b-img215.~~321/44.864/48.834/2.484 ms~~png]]

<~~span id~~/div><ol start="~~test~~2" style="list-~~method~~style-~~of-desktop-image~~type: decimal;"><li>The downloaded installation package is as follows, and then double-click to install directly</~~span~~li>~~==== Test method of desktop image ====~~

~~# Click the network configuration icon in the upper right corner of the desktop (please do not connect the network cable when testing WIFI)~~{| class="wikitable" style="width:800px;" |-| '''FileZilla_Server_1.5.1_win64-setup.exe'''|}

~~[[File:pi3b-img183.png|377x166px]]~~During the installation process, please select '''Decline''' on the following installation interface, and then select '''Next>'''

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

[[File:pi3b-~~img184~~img216.png~~|576x353px~~]]

</div></ol>

<li>~~Then enter~~ The interface after filezilla is opened is as follows, and the display under the ~~password of~~ remote site on the ~~WIFI hotspot, and then click '''Connect''' to start connecting to WIFI~~right is empty</li~~></ol~~>

~~[[File:pi3b-img185.png|320x163px]]~~<div class="figure">

[[File:pi3b-img217.png]]

</div></ol>

<li>~~After connecting to WIFI, you can open the browser to check whether you can access the Internet.~~ The ~~entrance~~ method of connecting the ~~browser~~ development board is shown in the figure below:</li> <~~/ol~~div class="figure">

[[File:pi3b-~~img186~~img209.png~~|576x308px~~]]

</div></ol>

<li>~~If you can open other web pages after opening~~ Then choose to '''save the ~~browser~~password''', ~~it means that the WIFI connection is normal~~and then click '''OK'''</li~~></ol~~>

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

[[File:pi3b-img218.png]] </div><~~span id~~/ol><ol start="~~how-to-set-a-static~~6" style="list-ipstyle-~~address~~type: decimal;"><li>Then choose to always '''trust this host''', and then click '''OK'''</~~span~~li>~~=== How to set a static IP address ===~~

~~'''Please do not set a static IP address by modifying the /etc/network/interfaces configuration file.'''~~<div class="figure">

~~==== Use the nmtui command to set a static IP address ====~~img219.png]]

~~# First run~~ </div></ol><ol start="7" style="list-style-type: decimal;"><li>After the ~~'''nmtui''' command~~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>

~~orangepi@orangepi:~$ '''nmtui'''~~<div class="figure">

~~<ol start="2" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Then select '''Edit a connection''' and press Enter</li></ol>~~img220.png]]

~~[[File~~</div></ol><ol start="8" style="list-style-type:~~pi3b-img188~~decimal;"><li>Then select the path to be uploaded to the development board on the right side of the filezilla software, and then select the file to be uploaded on the Ubuntu PC on the left side of the filezilla software, then click the right mouse button, and then click the upload option to start uploading the file to the development board.~~png|227x247px]]~~</li>

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

[[File:pi3b-~~img189~~img221.png~~|310x149px~~]]

</div></ol><ol start="49" style="list-style-type: decimal;"><li>~~Then select '''Edit''' with~~ After the upload is complete, you can go to the corresponding path in the Linux system of the ~~'''Tab''' key and press~~ development board to view the ~~Enter key~~uploaded file</li><li>The method of uploading a folder is the same as that of uploading a file</li></ol>

~~[[File:pi3b~~

~~<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>~~HDMI test ==

~~[[File:pi3b~~=== HDMI display test ===

~~<ol start="6" style="list-style-type: decimal;"><li>Then press Enter, select '''Manual''' with the up and down arrow keys,~~ # Use HDMI to HDMI cable to connect Orange Pi development board and ~~press Enter to confirm</li></ol>~~HDMI monitor

::[[File:pi3b-~~img192~~img10.png~~|576x237px~~]]

<ol start="72" style="list-style-type: decimal;"><li>~~The display after selection~~ After starting the Linux system, if the HDMI monitor has image output, it means that the HDMI interface is ~~shown~~ in ~~the figure below~~normal use</li~~></ol~~>

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

'''When you want to connect the HDMI of the development board to the HDMI port of the laptop, please make sure that your laptop supports the HDMI in function.'''<~~ol start~~/big>|}{| class="8wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Then move the cursor to the~~ '''~~<Show>~~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.'''</libig>|}</ol>

~~[[File:pi3b~~

~~<ol start~~=~~"9" style~~=~~"list-style-type: decimal;"><li>Then press Enter, the following setting interface will pop up after entering</li></ol>~~= HDMI to VGA display test ===

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

[[File:pi3b-img222.png]]</ol><ol start="102" style="list-style-type: ~~decimal~~lower-alpha;"><li>Then you can set the IP address (Addresses), gateway (Gateway) and DNS server address in the position shown in the figure below (there are many other setting options in it, please explore by yourself)，'''Please set it according to your specific needs, the value set in the figure below is just an example'''A VGA cable</li~~></ol~~>

[[File:pi3b-~~img196~~img223.png~~|576x233px~~]]</ol><ol start="113" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~After setting, move the cursor to'''<OK>''' in the lower right corner, and press Enter to confirm~~A monitor or TV that supports VGA interface</li></ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>HDMI to VGA display test as shown below</li>

[[File:pi3b-~~img197~~img224.png~~|576x116px~~]]

~~<ol start~~{| class="12wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Then click'''<Back>~~''' When using HDMI to ~~return~~ VGA display, the development board and the Linux system of the development board do not need to make any settings, only the ~~previous selection~~ HDMI interfaceof 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.'''</libig>|}</ol>

~~[[File:pi3b-img198.png|330x325px]]~~=== HDMI resolution setting method ===

~~<ol start="13" style="list-style-type: decimal;"><li>Then select~~ # First open '''~~Activate a connection~~Display'''~~, then move the cursor to~~in '''~~<OK>~~Settings'''~~, and finally click Enter</li></ol>~~

::[[File:pi3b-~~img199~~img225.png~~|331x248px~~]]

<ol start="142" style="list-style-type: decimal;"><li>Then ~~select~~ you can see the ~~network interface that needs to be set, such as '''Wired connection 1''', then move~~ current resolution of the ~~cursor to'''<Deactivate>''', and press Enter to disable '''Wired connection 1'''~~system</li~~></ol~~>

[[File:pi3b-~~img200~~img226.png~~|576x224px~~]]</ol><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>

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

[[File:pi3b-~~img201~~img228.png~~|576x224px~~]]</ol><ol start="5" style="list-style-type: decimal;"><li>After the new resolution is set, select '''Keep the configuration'''</li>

[[File:pi3b-img229.png]]</ol ~~start~~>~~<li>Then you can exit nmtui through the'''<Back>''' and '''Quit''' buttons~~</~~li></ol~~span>

~~[[File:pi3b-img202.png|300x253px]] [[File:pi3b-img203.png|227x252px]]~~== How to use Bluetooth ==

<~~ol start~~span id="~~17" style="list~~test-method-of-desktop-~~style~~image-~~type: decimal;~~1"><li/span>~~Then through '''ip addr show eth0''', you can see that the IP address~~ === Test method of ~~the network port has changed to the static IP address set earlier</li></ol>~~desktop image ===

~~orangepi@orangepi:~$ '''ip addr show eth0'''~~# Click the Bluetooth icon in the upper right corner of the desktop.

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

~~link~~<ol start="2" style="list-style-type: decimal;"><li>Then select the adapter</~~ether 5e:ac:14:a5:92:b3 brd ff:ff:ff:ff:ff:ff~~li>

~~inet~~ [[File:pi3b-img231.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>If there is a prompt on the following interface, please select '''~~192.168.1.177~~Yes'''</~~24 brd 192.168.1.255 scope global noprefixroute eth0~~li>

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

~~inet6 241e~~[[File:~~3b8:3240:c3a0:e269:8305:dc08~~pi3b-img233.png]]</ol><ol start="5" style="list-style-type:~~135e~~decimal;"><li>Then open the configuration interface of the Bluetooth device</~~64 scope global dynamic noprefixroute~~li>

~~valid_lft 259149sec preferred_lft 172749sec~~[[File:pi3b-img234.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Click '''Search''' to start scanning the surrounding Bluetooth device</li>

~~inet6 fe80~~[[File:pi3b-img235.png]]</ol><ol start="7" style="list-style-type:~~957d:bbbe:4928:3604~~decimal;"><li>Then select the Bluetooth device you want to connect to, and then click the right button of the mouse to pop up the operation interface for this Bluetooth device, select '''Pair''' to start pairing, and the demonstration here is to pair with an Android phone</~~64 scope link noprefixroute~~li>

~~valid_lft forever preferred_lft forever~~[[File:pi3b-img236.png]]</ol><ol start="8" style="list-style-type: decimal;"><li>When pairing, the pairing confirmation box will pop up in the upper right corner of the desktop. Select '''Confirm''' to confirm. At this time, the mobile phone also needs to be confirmed</li>

[[File:pi3b-img237.png]]</ol><ol start="189" style="list-style-type: decimal;"><li>~~Then~~ After pairing with the mobile phone, you can ~~test the connectivity of~~ choose the ~~network to check whether the IP address is configured OK~~paired Bluetooth device, then right-click and ~~the~~ select '''~~ping~~Send a File''' ~~command can be interrupted through~~ to start sending a picture to the ~~shortcut key '''Ctrl+C'''~~phone</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''ping 192~~pi3b-img238.~~168.1.47~~ png]]</ol><ol start="10" style="list-style-~~I eth0'''~~type: decimal;"><li>The interface of the sending picture is shown below</li>

~~PING 192.168.1.47 (192.168.1.47) from 192.168.1.188 eth0~~[[File: ~~56(84) bytes of data~~pi3b-img239.png]]</ol>

~~64 bytes from 192.168.1.47: icmp_seq~~=~~1 ttl~~=~~64 time~~USB interface test ==~~0.233 ms~~

~~64 bytes from 192.168.1.47: icmp_seq~~{| class=~~2 ttl~~"wikitable" style=~~64 time=0~~"background-color:#ffffdc;width:800px;" |-| <big>'''The USB interface can be connected to a USB hub to expand the number of USB interfaces.~~263 ms~~'''</big>|}

~~64 bytes from 192.168.1.47: icmp_seq~~=== Connect the USB mouse or keyboard test =~~3 ttl~~=~~64 time~~=~~0.273 ms~~

~~64 bytes from 192.168.1.47: icmp_seq=4 ttl=64 time=0.269 ms~~# 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)

~~64 bytes from 192.168.1.47: icmp_seq~~

^C=== Connect the USB storage device test ===

~~--- 192.168.1.47 ping statistics ---~~# First insert the U disk or USB mobile hard disk into the USB interface of the Orange Pi development board# Execute the following command, if you can see the output of sdX, it means that the U disk is recognized successfully

~~5 packets transmitted, 5 received,~~ ::{| class="wikitable" style="width:800px;"|-|orangepi@orangepi:~$ '''cat /proc/partitions | grep "sd*"''' major minor #blocksname 80~~% packet loss, time 4042ms~~30044160 '''sda''' 8130043119 '''sda1''' |}

~~rtt min/avg/max/mdev~~ <ol start="3" style= ~~0.233/0.262~~"list-style-type: decimal;"><li>Use the mount command to mount the U disk into '''/~~0.275~~mnt''', and then you can view the file in the U disk</~~0.015 ms~~li>

~~<~~| orangepi@orangepi:~$ '''sudo mount /dev/sda1 /mnt/~~span>==== Use the nmcli command to 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~~orangepi@orangepi: ~~lower-alpha;"><li>'''orangepi~~~$ ''' ~~is the name of the WIFI network interface (the names are not necessarily the same)<~~ls /~~p><~~mnt/~~li><li>~~'''~~Wired connection 1''' is the name of the Ethernet interface</li></ol></li></ol>~~

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

~~NAME UUID TYPE DEVICE~~/dev/sda1     29G    208K    29G    1% /mnt|}</ol>

~~'''orangepi''' cfc4f922-ae48-46f1-84e1-2f19e9ec5e2a wifi wlan0~~=== USB wireless network card test ===

The currently '''~~Wired connection 1~~tested''' ~~9db058b7-7701-37b8-9411-efc2ae8bfa30 ethernet eth0~~USB wireless network cards are shown below. Please test it by yourself for other models of USB wireless network cards. If you cannot use it, you need to transplant the corresponding USB wireless network card driver

~~<ol start~~{| class="3wikitable" style="~~list-style~~width:800px;text-~~type~~align: ~~decimal~~center;">~~<li>Then enter the following command, where</li></ol>~~|-| No.| Model||-| 1| RTL8723BU

~~<blockquote>a~~Support 2. ~~'''"Wired connection 1"''' means to set the static IP address of the Ethernet port~~4G WIFI+BT4. ~~If you need to set the static IP address of the WIFI, please change it to the corresponding name of the WIFI network interface (you can get it through the '''nmcli con show''' command)~~0

b| [[File:pi3b-img240. ~~After '''ipv4.addresse''' is the static IP address to be set, which can be modified to the value you want to set~~png]]|-| 2| RTL8811

cSupport 2. ~~'''ipv4.gateway''' indicates the address of the gateway</blockquote>orangepi@orangepi:~$ '''nmcli con mod "Wired connection 1" \'''~~4G +5G WIFI

~~'''ipv4~~| [[File:pi3b-img241.~~addresses "192.168.1.110" \'''~~png]]|-| 3| RTL8821CU

~~'''ipv4~~Support 2.~~gateway "192.168.1.1" \'''~~4G +5G WIFI

~~'''ipv4~~Support BT 4.~~dns "8.8.8.8" \'''~~2

~~'''ipv4.method "manual"'''~~| <div class="figure">

~~<ol start="4" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Then restart the Linux system</li></ol>~~img242.png]]

~~orangepi@orangepi:~$ '''sudo reboot'''~~</div>|}

<~~ol start~~span id="~~5" style="list~~rtl8723bu-~~style-type: decimal;~~test">~~<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~~span>==== RTL8723BU test ====

~~orangepi@orangepi:~$ '''ip addr show eth0'''~~# First insert the RTL8723BU wireless network card module into the USB interface of the development board# Then the Linux system will automatically load the RTL8723BU bluetooth and WIFI-related kernel modules, through the lsmod command, you can see that the following kernel modules have been automatically loaded

3: ~~eth0~~: ~~&lt~~{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''lsmod'''Module Size Used by rfcomm 5734416 rtl8xxxu 1064960 rtk_btusb 614400 |}

~~link~~<ol start="3" style="list-style-type: decimal;"><li>Through the dmesg command, you can see the loading information of the RTL8723BU module</~~ether 5e:ae:14:a5:91:b3 brd ff:ff:ff:ff:ff:ff~~li>

~~inet~~ {| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~192.168.1.110~~dmesg'''~~/32 brd 192.168.1.110 scope global noprefixroute eth0~~

~~valid_lft forever preferred_lft forever~~......

~~inet6 240e~~[ 83.438901] usb 2-1:~~3b7:3240:c3a0:97de:1d01:b290:fe3a/64 scope global dynamic noprefixroute~~new high-speed USB device number 2 using ehci-platform

~~valid_lft 259183sec preferred_lft 172783sec~~[ 83.588375] usb 2-1: New USB device found, idVendor=0bda, idProduct=b720, bcdDevice= 2.00

~~inet6 fe80~~[ 83.588403] usb 2-1:New USB device strings:~~3312:861a:a589:d3c/64 scope link noprefixroute~~Mfr=1, Product=2, SerialNumber=3

~~valid_lft forever preferred_lft forever~~[ 83.588422] usb 2-1: Product: 802.11n WLAN Adapter

~~== SSH remote login development board; ==~~1: Manufacturer: Realtek

~~'''Linux systems enable ssh remote login by default and allow the root user to log in to the system~~[ 83. 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.'''588460] usb 2-1: SerialNumber: 00e04c000001

~~=== SSH remote login development board under Ubuntu~~ 06 hci_rev=000b lmp_ver=06 lmp_subver=8723

~~# Obtain the IP address of the development board# Then you can remotely log in to the Linux system through the ssh command~~[ 83.603894] Bluetooth: hci0: RTL: rom_version status=0 version=1

~~test@test~~[ 83.603920] Bluetooth: hci0:~~~$ '''ssh [mailto~~RTL:~~root@192~~loading rtl_bt/rtl8723b_fw.~~168.1.36 root@192.168.1.]xxx''' (Need to be replaced with the IP address of the development board)~~bin

~~root@192~~[ 83.~~168~~610108] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_config.~~1.xx's password: (Enter the password here, the default password is orangepi)~~bin

~~'''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~~[ 83.611274] Bluetooth: hci0: RTL: cfg_sz 68, ~~just press Enter after inputting.'''~~total sz 22564

~~'''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~~[ 83.~~'''~~658494] rtk_btusb: Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-142432

~~<ol start="3" style="list-style-type~~[ 83.658651] usbcore: ~~decimal;"><li>After successfully logging in to the system, the display is as shown in the figure below</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-img204~~Please report results to Jes.Sorensen@gmail.~~png|405x207px|L467QDF65C(YR79U]TH[TND]]~~com

~~</div>'''If ssh cannot log in to the Linux system normally, please first check whether the IP address of the development board can be pinged~~[ 83. ~~If the ping is ok, you can log in to the Linux system through the serial port or HDMI display and then enter the following command on the development board and try again. Is it possible to connect~~890140] usb 2-1: Vendor:~~'''~~Realtek

~~root@orangepi~~[ 83.890153] usb 2-1: Product:~~~# '''reset_ssh~~802.~~sh'''~~11n WLAN Adapter

~~'''If it still doesn't work, try to reset the system~~[ 83.~~'''~~890159] usb 2-1: rtl8723bu_parse_efuse: dumping efuse (0x200 bytes):

~~=== SSH remote login development board under Windows ===~~......

~~# First obtain the IP address of the development board~~[ 83.890412] usb 2-1: RTL8723BU rev E (SMIC) 1T1R, TX queues 3, WiFi=1, BT=1, GPS=0, HI PA=0

[ 83.890417] usb 2~~) Under Windows, you can use MobaXterm to remotely log in to the development board, first create a new ssh session~~-1: RTL8723BU MAC: 00:13:ef:f4:58:ae

a[ 83. ~~Open '''Session'''~~890421] usb 2-1: rtl8xxxu: Loading firmware rtlwifi/rtl8723bu_nic.bin

b[ 83. ~~Then select '''SSH''' in '''Session Setting'''~~895289] usb 2-1: Firmware revision 35.0 (signature 0x5301)

c[ 84. ~~Then enter the IP address of the development board in the '''Remote host'''~~050893] Bluetooth: hci0: RTL: fw version 0x0e2f9f73

d[ 84. ~~Then enter the user name '''root''' or '''orangepi''' of the Linux system in '''Specify username'''~~266905] Bluetooth: RFCOMM TTY layer initialized

e[ 84. ~~Finally click '''OK'''~~266949] Bluetooth: RFCOMM socket layer initialized

~~<div class="figure">~~[ 84.266999] Bluetooth: RFCOMM ver 1.11

[~~[File:pi3b-img205~~84.~~png|553x280px|14]~~884270]usbcore: registered new interface driver rtl8xxxu

[ 84.912046] rtl8xxxu 2-1:1.2 wlx0013eff458ae: renamed from wlan0|}</~~div~~ol><ol start="24" style="list-style-type: decimal;">~~<li></li~~><li>Then you ~~will be prompted~~ can see the RTL8723BU WIFI device node through the '''sudo ifconfig''' command. Please refer to ~~enter a password. The default passwords~~ [[Orange Pi 3B#WIFI connection test|'''the WIFI connection test chapter''']] for ~~root~~ WIFI connection and ~~orangepi users are orangepi~~testing methods</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ifconfig wlx0013eff458ae'''

~~'''Note that when entering the password~~wlx0013eff458ae: flags=4099<UP, ~~the specific content of the entered password will not be displayed on the screen~~BROADCAST, ~~please do not think that there is any fault, just press Enter after inputting.'''~~MULTICAST> mtu 1500

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

~~[[File~~:~~pi3b-img206.png|578x150px|C~~:~~\Users\orangepi\Desktop\用户手册插图\pi 3b\just press Enter after inputting..jpgjust press Enter after inputting~~RX packets 0 bytes 0 (0.]]0 B)

~~</div><ol start="4" style="list-style-type~~: ~~decimal;"><li>After successfully logging in to the system, the display is as shown in the figure below</li></ol>~~:RX errors 0 dropped 0 overruns 0 frame 0

~~[[File~~:~~pi3b-img207~~:TX packets 0 bytes 0 (0.~~png|576x334px]]~~0 B)

::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0|}</ol><~~span id~~ol start="~~the~~5" style="list-~~method-of-uploading-files-to~~style-type: decimal;"><li>Then you can see the~~-linux-system-of-~~USB Bluetooth device through the~~-development-board">~~'''hciconfig''' command</~~span~~li>{| class="wikitable" style= ~~The method of uploading files to the Linux system of the development board ==~~"width:800px;" |-| orangepi@orangepi:~$ '''sudo apt update && sudo apt install bluez'''

~~=== How to upload files to the development board Linux system in Ubuntu PC ===~~orangepi@orangepi:~$ '''hciconfig'''

hci0: Type: Primary Bus: '''USB~~==== How to upload files using the scp command ====~~'''

~~# Use the scp command to upload files from the Ubuntu PC to the Linux system of the development board. The specific commands are as follows~~::BD Address: 00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16

~~<blockquote>a. '''file_path'''~~: ~~need to be replaced with the path of the file to be uploaded~~:DOWN

~~b. '''orangepi'''~~: ~~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~~:RX bytes:1252 acl:0 sco:0 events:125 errors:0

c::TX bytes:23307 acl:0 sco:0 commands:125 errors:0|}</ol><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 '''~~192.168.xx.xx~~x'''~~: It is the IP address of the development board, please modify it according to the actual situation~~will be displayed</li>

d[[File:pi3b-img243. ~~'''/home/orangepi''': The path in the Linux system of the development board, which can also be modified to other paths~~png]]</~~blockquote~~ol>~~test@test~~<ol start="7" style="list-style-type:~$ decimal;"><li>Click '''~~scp file_path orangepi@192.168.xx.xx:/home/orangepi/~~Turn Bluetooth On'''to turn on Bluetooth</li>

[[File:pi3b-img244.png]]</ol><ol start="28" style="list-style-type: decimal;"><li>~~If you want to upload a folder, you need to add the -r parameter~~The display after turning on Bluetooth is as follows</li~~></ol~~>

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

<~~ol start~~span id="~~3" style="list~~rtl8811-~~style-type: decimal;~~test">~~<li>There are more usages of scp, please use the following command to view the man manual</li~~></olspan>

==== RTL8811 test~~@test:~$ '''man scp'''~~====

~~~~# First insert the RTL8811 wireless network card module into the USB interface of the development board.~~==== How~~ # Then the Linux system will automatically load the kernel modules related to ~~upload files using filezilla ====~~RTL8811 WIFI, and you can see that the following kernel modules have been automatically loaded through the lsmod command

~~# First install filezilla in Ubuntu PC~~::{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''lsmod'''Module Size Used by 8821cu 1839104 0 |}

~~test~~<ol start="3" style="list-style-type: decimal;"><li>Through the dmesg command, you can see the loading information of the RTL8811 module</li>{| class="wikitable" style="width:800px;" |-| orangepi@~~test~~orangepi:~$ '''~~sudo apt install -y filezilla~~dmesg''' [ 118.618194] usb 2-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

~~<ol start~~[ 118.767181] usb 2-1: New USB device strings: Mfr=1, Product="2~~" style~~, SerialNumber=~~"list-style-type: decimal;"><li>Then use the following command to open filezilla</li></ol>~~3

~~test@test~~[ 118.767199] usb 2-1:~~~$ '''filezilla'''~~Product: 802.11ac NIC

~~<ol start="3" style="list~~[ 118.767219] usb 2-~~style-type~~1: Manufacturer: ~~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>~~Realtek

~~<div class="figure">~~[ 118.767235] usb 2-1: SerialNumber: 123456

[~~[File:pi3b-img208~~119.~~png|576x453px|截图 2022-12-03 19-04-40]~~500530]usbcore: registered new interface driver rtl8821cu

[ 119.525498] rtl8821cu 2-1:1.0 wlx1cbfced9d260: renamed from wlan0|}</~~div~~ol>

<li>~~The method of connecting~~ Then you can see the ~~development board is shown in~~ WiFi device node through the ~~figure below~~'''sudo ifconfig''' command. Please refer to the [[Orange Pi 3B#WIFI connection test|'''WiFi connection test chapter''']] for WIFI connection and testing methods. I won't go into details her</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ifconfig wlx1cbfced9d260'''

~~<div class~~wlx1cbfced9d260: flags=~~"figure">~~4099<UP,BROADCAST,MULTICAST> mtu 1500

~~[[File~~:~~pi3b-img209.png|575x128px|图片565]]~~:ether 1c:bf:ce:d9:d2:60 txqueuelen 1000 (Ethernet)

~~</div><ol start="5" style="list-style-type~~: ~~decimal;"><li>Then choose to '''save the password''', and then click '''OK'''</li></ol>~~:RX packets 0 bytes 0 (0.0 B)

~~[[File~~:~~pi3b-img210.png|249x181px]]~~:RX errors 0 dropped 0 overruns 0 frame 0

~~<ol start="6" style="list-style-type~~: ~~decimal;"><li>Then choose to always '''trust this host''', and then click '''OK'''</li></ol>~~:TX packets 0 bytes 0 (0.0 B)

::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0|}<~~div class~~/ol>

~~[[File:pi3b-img211.png|278x150px|IMG_256]]~~==== RTL8821CU test ====

~~</div><ol start="7" style="list-style-type: decimal;"><li>After~~ # First insert the ~~connection is successful, you can see~~ rtl8821cu wireless network card module into the ~~directory structure~~ USB interface of the development board ~~Linux file system on~~ # Then use the ~~right side~~ '''lsusb''' command to see the device information of the ~~filezilla software</li></ol>~~rtl8821cu usb wifi module, please make sure that the USB module is not in Driver CDROM Mode

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

~~[[File~~Bus 002 Device 003:~~pi3b~~ID 0bda:c820 Realtek Semiconductor Corp. 802.11ac NIC|}::{| class="wikitable" style="background-~~img212.png~~color:#ffffdc;width:800px;" |-|~~533x330px~~orangepi@orangepi:~$ '''lsusb |~~IMG_256]]~~grep "Realtek"'''

Bus 002 Device 002: ID 0bda:1a2b Realtek Semiconductor Corp. RTL8188GU 802.11n WLAN Adapter ('''<~~/div><ol start="8"~~ span style="~~list-style-type~~color: ~~decimal;~~blue"><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>Driver CDROM Mode</olspan>''')

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

~~[[File~~<big>'''If the USB WIFI module seen by the lsusb command is in Driver CDROM Mode, please unplug the USB WIFI module again. If not, please manually execute the following command to switch to the next mode:~~pi3b-img213.png|485x380px|IMG_256]]~~'''</big>

~~</div>~~

~~9) After the upload is complete, you can go to the corresponding path in the Linux system of the development board to view the uploaded file~~

~~10) The method of uploading a folder is the same as that of uploading a file, so I won’t go into details here~~orangepi@orangepi:~$ '''sudo usb_modeswitch -KW -v 0bda -p 1a2b'''|}

<~~span id~~ol start="3" style="~~the~~list-~~method~~style-oftype: decimal;"><li>The Linux system will automatically load the rtl8821cu bluetooth and wifi-~~uploading~~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;" |-~~files~~|orangepi@orangepi:~$ '''lsmod'''Module Size Used by 8821cu 1839104 0 rtk_btusb 614400 |}</ol><ol start="4" style=~~= The method of uploading files from Windows PC to~~ "list-style-type: decimal;"><li>Through the dmesg command, you can see the ~~Linux system~~ loading information of the ~~development board =~~rtl8821cu module</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''dmesg'''

~~==== How to upload files using filezilla ====~~......

~~# First download the installation file of the Windows version of the filezilla software, the download link is as follows~~[ 57.083693] usb 2-1: new high-speed USB device number 2 using ehci-platform

~~https~~[ 57.231888] usb 2-1:~~//filezilla-project.org/download~~New USB device found, idVendor=0bda, idProduct=1a2b, bcdDevice= 2.~~php?type=client~~00

~~<div class~~[ 57.231916] usb 2-1: New USB device strings: Mfr=~~"figure">~~1, Product=2, SerialNumber=0

[~~[File~~57.231937] usb 2-1:~~pi3b-img214.png|472x171px|C~~Product:~~\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-15.jpg未标题-15]]~~DISK

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

[~~[File~~57.242594] usb-storage 2-1:~~pi3b-img215~~1.~~png|393x283px|图片5552]]~~0: USB Mass Storage device detected

~~</div><ol start="~~[ 57.245674] scsi host0: usb-storage 2~~" style="list-style~~-~~type~~1: ~~decimal;"><li>The downloaded installation package is as follows, and then double-click to install directly</li></ol>~~1.0

~~'''FileZilla_Server_1~~[ 58.~~5.1_win64~~069172] usb 2-~~setup.exe'''~~1: USB disconnect, device number 2

~~During the installation process, please select '''Decline''' on the following installation interface, and then select '''Next>'''~~[ 58.440025] usb 2-1: new high-speed USB device number 3 using ehci-platform

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

[~~[File:pi3b-img216~~58.~~png|319x251px|IMG_256]~~587827]usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

~~</div><ol start="3" style="list~~[ 58.587833] usb 2-~~style-type~~1: Product: ~~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>~~802.11ac NIC

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

[~~[File:pi3b-img217~~58.~~png|451x357px|IMG_256]~~587844]usb 2-1: SerialNumber: 123456

~~</div><ol start="4" style="list-style~~[ 58.610463] rtk_btusb: Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-~~type: decimal;"><li>The method of connecting the development board is shown in the figure below:</li></ol>~~142432

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

[~~[File:pi3b-img209~~58.~~png|575x128px|图片565]~~634631]Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821

~~</div><ol start~~[ 58.636729] Bluetooth: hci0: RTL: rom_version status=~~"5" style~~0 version=~~"list-style-type: decimal;"><li>Then choose to '''save the password''', and then click '''OK'''</li></ol>~~1

~~<div class="figure">~~[ 58.636740] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin

[~~[File~~58.664190] Bluetooth: hci0: RTL:~~pi3b-img218~~loading rtl_bt/rtl8821c_config.~~png|207x146px|IMG_256]]~~bin

~~</div><ol start="6" style="list-style-type~~[ 58.664746] Bluetooth: ~~decimal;"><li>Then choose to always '''trust this host'''~~hci0: RTL: cfg_sz 10, ~~and then click '''OK'''</li></ol>~~total sz 31990

~~<div class="figure">~~[ 59.122471] Bluetooth: hci0: RTL: fw version 0x829a7644

[~~[File:pi3b-img219~~59.~~png|221x109px|IMG_256]~~265513]usbcore: registered new interface driver rtl8821cu

~~</div><ol start="7" style="list~~[ 59.280119] rtl8821cu 2-~~style-type~~1:1.2 wlx90de80521825: ~~decimal;">~~renamed from wlan0|}~~<li>After the connection is successful, you can see the directory structure of the development board Linux file system on the right side of the filezilla software</li>~~</ol>

<~~div~~ 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="~~figure~~wikitable" style="width:800px;">|-| orangepi@orangepi:~$ '''sudo ifconfig wlx90de80521825'''

~~[[File~~wlx90de80521825:~~pi3b-img220.png|446x329px|图片3]]~~flags=4099<UP,BROADCAST,MULTICAST> mtu 1500

~~</div><ol start="8" style="list-style-type~~: ~~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>:ether 00:13:ef:f4:58:ae txqueuelen 1000 (Ethernet)

~~<div class="figure">~~::RX packets 0 bytes 0 (0.0 B)

~~[[File~~:~~pi3b-img221.png|501x369px|IMG_256]]~~:RX errors 0 dropped 0 overruns 0 frame 0

~~</div><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</li></ol>~~:TX packets 0 bytes 0 (0.0 B)

::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0|}<~~span id~~/ol><ol start="~~hdmi~~6" style="list-style-~~test~~type: decimal;"><li>Then you can see the USB Bluetooth device through the '''hciconfig''' command</~~span~~li>{| class="wikitable" style= ~~HDMI test ==~~"width:800px;" |-| orangepi@orangepi:~$ '''sudo apt-get update && sudo apt-get install -y bluez'''

~~=== HDMI display test ===~~orangepi@orangepi:~$ '''hciconfig'''

hci0: Type: Primary Bus: '''USB'''

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

~~<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></ol>~~:DOWN

'''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.'''::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="7" style="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 '''~~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.~~x'''will be displayed</li>

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

[[File:pi3b-img244.png]]</ol><~~span id~~ol start="9" style="~~hdmi-to~~list-~~vga-display~~style-~~test~~type: decimal;"><li>The display after turning on Bluetooth is as follows</~~span~~li>~~=== HDMI to VGA display test ===~~

~~<ol style="list~~[[File:pi3b-~~style-type: decimal;">~~img245.png]]~~<li>First, you need to prepare the following accessories~~</pol><ol start="10" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~HDMI~~ Please refer to the [[Orange Pi 3B#How to ~~VGA converter</li></ol>~~use Bluetooth|'''Bluetooth use chapter''']] for the Bluetooth test method. I won't go into details here</li></ol>

~~[[File:pi3b~~

~~<ol start~~=~~"2" style~~=~~"list-style-type: lower-alpha;"><li>A VGA cable</li></ol>~~= USB Camera Test ===

~~[[File:pi3b-img223.png|148x133px]]~~# 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

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

~~~~

<li>~~HDMI to VGA display test as shown below~~You can see that the USB camera's device node information is/dev/video0 through the v4l2-ctl command</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''v4l2-ctl --list-devices'''

~~[[File~~Q8 HD Webcam:~~pi3b~~Q8 HD Webcam ('''usb'''-~~img224~~fc880000.~~png|576x339px]]~~usb-1):

:'''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./dev/video0'''

~~<~~:/~~span>=== HDMI resolution setting method ===~~dev/video1

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

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

'''In addition, the serial number of the video is not necessarily video0, please refer to what you actually see.'''</big>|}</ol><ol start="23" style="list-style-type: decimal;"><li>~~Then you~~ In the desktop system, Cheese can ~~see~~ be used to directly open the ~~current resolution~~ USB camera. The method of opening Cheese is shown in the ~~system~~figure below:</li>~~</ol>~~ ~~[[File:pi3b-img226.png|382x254px]]~~

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

~~[[File~~The interface after Cheese turns on the USB camera is shown in the figure below:~~pi3b-img227.png|415x274px]]~~

[[File:pi3b-img247.png]]

</ol>

<li>~~Then select~~ How to test the ~~resolution you want to set, and click Apply~~USB camera using fswebcam<ol style="list-style-type: lower-alpha;"><li>Install fswebcam</olli>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo''' '''apt update'''

~~[[File~~orangepi@orangepi:~~pi3b~~~$ '''sudo apt-~~img228~~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) .~~png~~/image.jpg The name and path for setting the generated photos</li>{|~~415x277px]]~~class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo''' '''fswebcam -d /dev/video0 \'''

'''--no-banner -r 1280x720 -S 5 ./image.jpg'''|}</ol></li></ol><ol start="53" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~After~~ In the ~~new resolution is set~~desktop version of the Linux system, ~~select~~ you can directly view the captured pictures through the HDMI display</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~Keep~~ 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 ~~configuration~~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>

~~[[File:pi3b-img229.png|447x243px]]~~== Audio Test ==

== ~~How to use Bluetooth~~ = Test audio methods in the desktop system ===

~~=== Test method of desktop image ===~~# First open the file manager

~~# Click the Bluetooth icon in the upper right corner of the desktop~~::[[File:pi3b-img248.png]]

~~[[File~~<ol start="2" style="list-style-type:~~pi3b-img230.png|330x128px]]~~decimal;"><li>Then find the following file (if there is no audio file in the system, you can upload a audio file to the system by yourself)</li>

<~~ol start~~div class="2figure" ~~style="list-style-type: decimal;"><li>Then select the adapter</li></ol~~>

[[File:pi3b-~~img231~~img249.png~~|375x165px~~]]

</div></ol>

<li>~~If there is a prompt below~~Then select the audio.wav file, right click and select ~~'''Yes'''~~open with vlc to start playing</li>~~</ol>~~ ~~[[File:pi3b-img232.png|248x85px]]~~

[[File:pi3b-img250.png]]

</ol>

<li>~~Then set '''Visibility Setting'''~~ Methods to switch different audio equipment such as ~~'''Always visible''' in the Bluetooth adapter settings interface,~~ HDMI playback and ~~then close it~~headset playback<ol style="list-style-type: lower-alpha;"><li>First open the volume control interface</olli>

[[File:pi3b-~~img233~~img251.png~~|243x229px~~]]</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 open the configuration interface of the Bluetooth device~~</liol></olspan>

~~[[File:pi3b-img234.png|438x179px]]~~=== How to play audio with commands ===

<~~ol start~~span id="~~6" style="list~~headphone-interface-play-~~style~~audio-~~type: decimal;~~test">~~<li>Click '''Search''' to start scanning the surrounding Bluetooth device~~</~~li></ol~~span>==== Headphone interface play audio test ====

~~[[File:pi3b-img235.png|322x217px]]~~# First insert the headset into the headphone jack of the development board

~~<ol start="7" style="list-style-type~~: ~~decimal;"><li>Then select the Bluetooth device you want to connect. If you right~~ :[[File:pi3b-~~click the mouse, you will pop up the operating interface of this Bluetooth device. Select '''Pair''' to start pairing~~img253. ~~Here, it is demonstrated with the Android phone</li></ol>~~png]]

~~[[File~~<ol start="2" style="list-style-type:~~pi3b~~decimal;"><li>Then you can check the sound card device supported by the Linux system through the '''aplay -~~img236~~l''' command.~~png|338x263px]]~~From the output below, it can be seen that '''card 0''' is the sound card device with RK809, which is the sound card device of the headset</li>

~~<ol start~~{| class="8wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>When pairing, the pairing confirmation box will pop up in the upper right corner of the desktop. Select~~ |-| orangepi@orangepi:~$ '''~~Confirm~~aplay -l''' ~~to confirm. At this time, the mobile phone also needs to be confirmed</li></ol>~~

~~[[File:pi3b-img237.png|417x152px]]~~**** List of PLAYBACK Hardware Devices ****

~~<ol start="9" style="list-style~~'''card 0: rockchiprk809 [rockchip-~~type: decimal;"><li>After pairing with the mobile phone~~rk809], ~~you can choose the paired Bluetooth~~ device~~, then right~~ 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-~~click and select '''Send a File~~0]''' ~~to start sending a picture to the phone</li></ol>~~

~~[[File~~:~~pi3b-img238.png|439x259px]]~~'''Subdevices: 0/1'''

~~<ol start="10" style="list-style-type~~: ~~decimal;"><li>The interface of the sending picture is shown below</li></ol>~~'''Subdevice #0: subdevice #0'''

card 1: rockchiphdmi [~~[File~~rockchip,hdmi], device 0:~~pi3b~~fe400000.i2s-~~img239~~i2s-hifi i2s-hifi-0 [fe400000.~~png|437x253px]~~i2s-i2s-hifi i2s-hifi-0]

~~<~~:Subdevices: 0/~~span>== USB interface test ==~~1

~~'''The USB interface can connect USB Hub to expand the number of USB interfaces.'''~~:Subdevice #0: subdevice #0

:Subdevice #0: subdevice #0|}</ol><~~span id~~ol start="3" style="~~connect-the-usb-mouse-or~~list-~~keyboard~~style-~~test~~type: decimal;"><li>Then use the '''aplay''' command to play the audio file that comes with the system. If the headset can hear the sound, it means that the hardware can be used normally</~~span~~li>~~=== Connect the USB mouse or keyboard test ===~~

~~# Insert the keyboard of the USB interface into the USB interface of Orange PI development board~~{| class="wikitable" style="width:800px;" ~~# Connect Orange PI development board to HDMI display~~|-~~# If the mouse or keyboard can normal operating systems~~| orangepi@orangepi:~$ '''aplay -D hw:0, ~~the USB interface is used normally (the mouse can only be used in the system of the desktop version)~~0 /usr/share/sounds/alsa/audio.wav'''

Playing WAVE 'audio.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo|}</ol>~~=== Connect the USB storage device test ===~~

~~# First insert the U disk or USB mobile hard disk into the USB interface of Orange PI development board# Execute the following command. If you can see the output of sdX, the U disk recognition is successful~~==== HDMI Audio Play Test ====

~~orangepi@orangepi:~$~~ # 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 '''~~cat /proc/partitions | grep "sd*"~~card 1'''

~~major minor #blocks name~~::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''aplay -l'''

~~8 0 30044160 '''sda'''~~**** List of PLAYBACK Hardware Devices ****

~~8 1 30043119 '''sda1'''~~card 0: rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]

~~<ol start="3" style="list-style-type~~: ~~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><~~Subdevices: 0/~~ol>~~1

~~orangepi@orangepi~~:~~~$ '''sudo mount /dev/sda1 /mnt/'''~~Subdevice #0: subdevice #0

~~orangepi@orangepi:~$~~ '''~~ls /mnt/~~card 1: rockchiphdmi [rockchip,hdmi], device 0: fe400000.i2s-i2s-hifi i2s-hifi-0 [fe400000.i2s-i2s-hifi i2s-hifi-0]'''

~~test.txt~~:'''Subdevices: 0/1'''

~~<ol start="4" style="list-style-type~~: ~~decimal;"><li>After the mounting, you can view the capacity of the U disk through the~~ '''~~df -h~~Subdevice #0: subdevice #0''' ~~command and the mounting point</li></ol>~~

~~orangepi@orangepi~~:~$ '''~~df -h | grep "sd"~~Subdevice #0: subdevice #0'''|}

<ol start="3" style="list-style-type: decimal;"><li>Then use the '''aplay''' command to play the audio file that comes with the system. If the HDMI display or television can hear the sound indicates that the hardware can be used normally</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''aplay -D hw:1</~~dev~~span>,0 /~~sda1 29G 208K 29G 1%~~ usr/share/sounds/alsa/~~mnt~~audio.wav'''|}</ol> === ~~USB wireless network card~~ Use the command to test the recording method ===

~~The currently '''tested''' USB wireless network cards are shown~~ # 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~~. Please test it by yourself for other models~~ will record a piece of ~~USB wireless network cards. If you cannot use it, you need to transplant~~ audio through the ~~corresponding USB wireless network card driver~~headset

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

|-

| ~~No.| Model~~orangepi@orangepi:~$ '''amixer -c 0 cset name='Capture MIC Path' 'Main Mic''''||orangepi@orangepi:~$ '''arecord -D hw:0,0 -d 5 -f cd -t wav /tmp/test.wav'''| 1~~| RTL8723BU~~}

~~Support 2.4G WIFI+BT4.0~~

~~| [[File:pi3b-img240.png]]~~|-~~| 2| RTL8811~~== Temperature Sensor ==

~~Support 2.4G +5G WIFI~~# The command to view the system temperature sensor is:

::{| ~~[[File~~class="wikitable" style="width:~~pi3b-img241.png]]~~800px;"

|-

| 3~~| RTL8821CU~~orangepi@orangepi:~$ '''sensors'''

~~Support 2.4G +5G WIFI~~soc_thermal-virtual-0

~~Support BT 4.2~~Adapter: Virtual device

~~| <div class~~temp1: +41.9°C (crit =~~"figure">~~+115.0°C)

~~[[File:pi3b-img242.png|tb_imag e_share_1670833201 123]]~~

~~</div>~~|}gpu_thermal-virtual-0

~~==== RTL8723BU test ====~~Adapter: Virtual device

~~# First insert the RTL8723BU wireless network card module into the USB interface of the development board~~temp1: +43.8°C~~# Then the Linux system will automatically load the RTL8723BU Bluetooth and WiFi -related kernel modules. You can see that the kernel module below is automatically loaded through the lsmod command~~|}

<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:~$ '''~~lsmod~~sudo smartctl -a /dev/nvme0 | grep "Temperature:"'''Temperature: '''40 Celsius'''|}</li></ol>

~~Module Size Used by~~

~~rfcomm 57344 16~~== 40 Pin interface pin explanation ==

~~rtl8xxxu 106496 0~~# Orange Pi 3B Development board 40 Pin interface pins, please refer to the figure below

~~rtk_btusb 61440 0~~<div class="figure">

~~<ol start="3" style="list~~::[[File:pi3b-~~style-type: decimal;"><li>You can see the loading information of the RTL8723BU module through the dmesg command</li></ol>~~img254.png]]

~~orangepi@orangepi~~</div><ol start="2" style="list-style-type:~~~$ '''dmesg'''~~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="2" style="list-style-type: lower-alpha;"><li>The following form is a picture on the left half of the full table above, which can be seen clearly</li>

[ 83[File:pi3b-img256-1.~~438901~~png]] ~~usb 2~~</ol><ol start="3" style="list-style-1type: ~~new high-speed USB device number 2 using ehci~~lower-~~platform~~alpha;"><li>The following form is a picture on the right half of the top table above, which can be seen clearly</li>

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

~~[ 83.588403] usb 2~~

~~[ 83.588422] usb 2-1: Product: 802.11n WLAN Adapter~~== How to install wiringOP ==

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

~~[ 83.588460] usb 2-1: SerialNumber: 00e04c000001~~

~~[ 83.601974] Bluetooth~~'''The storage path of the compiled wiringOP's Deb is wrapped in Orangepi-Build: ~~hci0: RTL: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723~~'''

~~[ 83~~'''orangepi-build/external/cache/debs/arm64/wiringpi_x.xx.~~603894] Bluetooth: hci0: RTL: rom_version status=0 version=1~~deb'''

~~[ 83.603920] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_fw.bin~~

~~[ 83~~'''After entering the system, you can run the gpio readall command.~~610108] Bluetooth: hci0: RTL: loading rtl_bt~~If you can see the output below, it means that wiringOP is pre -installed and can be used normally.'''</~~rtl8723b_config.bin~~big>

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

[ ~~83.658494] rtk_btusb~~[File: ~~Realtek Bluetooth USB driver ver 3.~~pi3b-img258-1.~~6d45ddf.20220519-142432~~png]]

~~[ 83~~</div><big>'''wiringOP is currently mainly adapted to the functions of setting GPIO port input and output, setting GPIO port output high and low levels, and setting up and down pull-down resistors.~~658651] usbcore: registered new interface driver rtk_btusb~~Functions such as hardware PWM are not available.'''</big>|}

~~[ 83.667124] usb 2-1: This Realtek USB WiFi dongle (0x0bda:0xb720) is untested!~~# Download the code of wiringOP

~~[ 83.667137] usb 2~~::{| class="wikitable" style="width:800px;" |-1| orangepi@orangepi: ~~Please report results to Jes.Sorensen@gmail.com~~~$ '''sudo apt update'''

~~[ 83.890140] usb 2~~orangepi@orangepi:~$ '''sudo apt install -~~1: Vendor: Realtek~~y git'''

~~[ 83~~orangepi@orangepi:~$ '''git clone https://github.~~890153] usb 2~~com/orangepi-~~1: Product: 802~~xunlong/wiringOP.~~11n WLAN Adapter~~git -b next'''|}

~~[ 83.890159] usb 2~~::{| class="wikitable" style="background-1color: ~~rtl8723bu_parse_efuse: dumping efuse (0x200 bytes)~~#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.'''

~~......~~

~~[ 83.890412] usb 2-1: RTL8723BU rev E (SMIC) 1T1R~~'''If there is a problem with the download code from GitHub, ~~TX queues 3~~you can use the wiringOP source code that comes with the Linux image directly, ~~WiFi=1, BT=1, GPS=0, HI PA=0~~and the storage location is: /usr/src/wiringOP'''</big>|}

~~[ 83.890417] usb~~ <ol start="2" style="list-~~1: RTL8723BU MAC: 00:13:ef:f4:58~~style-type:aedecimal;"><li>Compile and install wiringOP</li>

~~[ 83.890421] usb 2~~{| class="wikitable" style="width:800px;" |-~~1: rtl8xxxu~~| orangepi@orangepi: ~~Loading firmware rtlwifi/rtl8723bu_nic.bin~~~$ '''cd wiringOP'''

~~[ 83.895289] usb 2-1~~orangepi@orangepi: ~~Firmware revision 35~~~/wiringOP$ '''sudo .~~0 (signature 0x5301)~~/build clean'''

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

~~[ 84.266905] Bluetooth: RFCOMM TTY layer initialized~~<div class="figure">

[ 84[File:pi3b-img258-1.~~266949~~png]] ~~Bluetooth: RFCOMM socket layer initialized~~

~~[ 84.266999] Bluetooth: RFCOMM ver 1.11~~</div></ol>

~~[ 84.884270] usbcore: registered new~~ == 40Pin interface ~~driver rtl8xxxu~~GPIO, I2C, UART, SPI, and PWM test ==

~~[ 84.912046] rtl8xxxu 2~~{| class="wikitable" style="background-1color:#ffffdc;width:1800px;" |-| <big>'''Note that if you need to set overlays to open multiple configurations at the same time, please use a space to write in one line like the following space.~~2 wlx0013eff458ae: renamed from wlan0~~'''</big>

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

~~orangepi@orangepi:~$~~ '''~~sudo ifconfig wlx0013eff458ae~~overlays=spi3-m0-cs0-spidev i2c2-m1 i2c3-m0 uart7-m2 uart9-m2 pwm11-m1'''|}

~~wlx0013eff458ae: flags~~=== 40pin GPIO port test ===~~4099<UP,BROADCAST,MULTICAST> mtu 1500~~

~~ether 00~~{| class="wikitable" style="background-color:13#ffffdc;width:~~ef:f4:58:ae txqueuelen 1000 (Ethernet)~~800px;" |-| <big>'''The Linux system released by Orange Pi has a pre -installed blink_all_gpio program. This program will set up all 28 GPIO ports in 40pin to switch high and low levels.'''

~~RX packets 0 bytes 0 (0.0 B)~~

~~RX errors 0 dropped 0 overruns 0 frame~~ '''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 0and 3.3v. Use this program to test whether the GPIO port can work normally'''

~~TX packets 0 bytes 0 (0.0 B)~~

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~'''The method of running blink_all_gpio program is shown below: '''</big>

~~<ol start="5" style="list-style-type~~orangepi@orangepi3b: ~~decimal;"><li>Then you can see the USB Bluetooth device through the~~ ~$ '''~~hciconfig~~sudo blink_all_gpio''' ~~command</li></ol>~~        #Remember to add Sudo permissions

~~orangepi@~~[sudo] password for orangepi:~~~$ '''sudo apt update~~ &~~amp~~nbsp;    &~~amp~~nbsp; ~~sudo apt install bluez~~#You need to enter password here'''|}

~~orangepi@orangepi:~$~~ # There are a total of '''~~hciconfig~~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

~~hci0~~: ~~Type~~: ~~Primary Bus~~[[File: ~~'''USB'''~~pi3b-img259-1.png]]

~~BD Address~~<ol start="2" style="list-style-type: ~~00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16~~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>

~~DOWN~~{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio mode 2 out'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then set the GPIO port to output the low level. After setting, you can use the value of the voltage of the pins with a multimeter. If it is 0v, it means that the low level flat is successful</li>

~~RX bytes~~{| class="wikitable" style="width:~~1252 acl~~800px;" |-| root@orangepi:~~0 sco:0 events:125 errors~~~/wiringOP# '''gpio write 2 0'''|}

~~TX bytes:23307 acl:0 sco:0 commands:125 errors:~~Using GPIO Readall, you can see the value of the No. 7 pin (V) to 0

[[File:pi3b-img260.png]]</ol><ol start="64" style="list-style-type: decimal;"><li>~~You~~ Then set the GPIO port to output a high level. After setting, you can ~~also see~~ use a multimeter to measure the ~~Bluetooth icon on~~ voltage value of the ~~desktop~~pin. If it is 3. ~~At this time~~3v, ~~Bluetooth has not been opened, so a red '''x''' will be displayed~~it means that the high level is set successfully.</li~~></ol~~>

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

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

[[File:pi3b-~~img244~~img261-1.png~~|576x262px~~]]</ol><ol start="5" style="list-style-type: decimal;"><li>The setting method of other pins is similar, just modify the serial number of wPi to the corresponding serial number of the pin</li></ol>

<~~ol start~~span id="~~8" style="list~~pin-gpio-port--down-and-downward-pull--down-resistance-~~style~~setting-~~type: decimal;~~method">~~<li>The display after opening Bluetooth is shown below</li~~></olspan>

~~[[File:pi3b~~=== 40pin GPIO port pull-~~img245.png|576x164px]]~~down resistance setting method ===

~~<ol start~~{| class="9wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Please refer to the [[\l|~~'''~~Bluetooth use method'~~Note that the 4 GPIO pins below Orange Pi 3B are invalid because there are 3.3V on the outside, so setting drop-down is invalid. Other pins can be set normally ''~~]] for Bluetooth test method, so I won~~'~~t go into details here.</li>~~</olbig>

~~~~img262-1.png|center]]~~==== RTL8811 test ====~~|}

# ~~First insert~~ Below the ~~RTL8811 wireless network card module into the USB interface of the development board~~No.~~# Then the Linux system will automatically load the RTL8811 WIFI~~ 11 pin—corresponding to GPIO 3_C6-corresponding wPi serial number 5—to demonstrate how to set up and down pull-~~related kernel modules. You can see that the kernel module below is automatically loaded through~~ down resistance of the ~~lsmod command~~GPIO port

~~orangepi@orangepi~~:~~~$ '''lsmod'''~~ ~~Module Size Used by~~ ~~8821cu 1839104 0~~:[[File:pi3b-img263-1.png]]

<li>First of all, you need to set the GPIO port as the input mode. The third parameter needs to enter the serial number of the wPi corresponding to the pins</li>

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

|-

|

root@orangepi:~/wiringOP# '''gpio mode 5 in'''

|}

</ol>

<li>~~You can see~~ After the ~~loading information~~ setting is set to input mode, execute the following command to set the GPIO port as the pull-down mode</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio mode 5 up'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then enter the following command to read the level of the ~~RTL8811 module through~~ GPIO port. If the level is 1, it means that the ~~dmesg command~~drawing mode is successful</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio read 5</olspan>'''

'''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'''|}</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 0, it means that the drop-down mode is set successfully</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ /wiringOP# '''~~dmesg~~gpio read 5'''

~~[ 118.618194] usb 2-1~~'''0'''|}</ol>

~~[ 118.767152] usb 2-1: New USB device found, idVendor~~=~~0bda, idProduct~~=~~c811, bcdDevice~~= ~~2.00~~40pin SPI Test ===

~~[ 118.767181] usb 2-1: New USB device strings: Mfr=1~~# From the schematic diagram of the 40PIN interface, ~~Product=2, SerialNumber=3~~the SPI available for Orange Pi 3B is spi3

::[[ ~~118.767199] usb 2~~File:pi3b-img264-1~~: Product: 802~~.~~11ac NIC~~png]]

<ol start="2" style="list-style-type: decimal;"><li>In the linux system, the SPI in the 40 pin is closed by default, and it needs to be opened manually before it can be used. The detailed steps are as follows:<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 orangepi-config'''|}</li><li>Then select '''System'''[[ ~~118~~File:pi3b-1.~~767219~~png] ~~usb~~ ]</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-13.png]]</li><li>Then select '''<Save>''' to save[[File:pi3b-4.png]]</li><li>Then select '''<Back>'''[[File: ~~Manufacturer~~pi3b-5.png]]</li><li>Then select '''<Reboot>''' to restart the system to make the configuration take effect[[File: ~~Realtek~~pi3b-6.png]]</li></ol></li></ol>

~~[ 118.767235] usb 2~~<ol start="3" style="list-style-1type: ~~SerialNumber: 123456~~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>

~~[ 119.500530] usbcore~~{| class="wikitable" style="width: ~~registered new interface driver rtl8821cu~~800px;" |-| ~~[ 119.525498] rtl8821cu 2-1~~orangepi@orangepi:1~$ '''ls /dev/spidev3.0 ~~wlx1cbfced9d260: renamed from wlan0~~'''

/dev/spidev3.0

|}

</ol>

<li>~~Then~~ Do not short-circuit the mosi and miso pins of SPI3, the output result of running spidev_test is as follows, you can see that the ~~WiFi device node through the '''sudo ifconfig''' command. Please refer to the [[\l|'''WiFi connection test a section''']] for WIFI connection~~ data of TX and ~~testing methods. I won't go into details her~~RX are inconsistent</li~~></ol~~>

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

~~wlx1cbfced9d260~~spi mode: ~~flags=4099<UP,BROADCAST,MULTICAST> mtu 1500~~0x0

~~ether 1c~~bits per word:~~bf:ce:d9:d2:60 txqueuelen 1000 (Ethernet)~~8

~~RX packets 0 bytes 0~~ max speed: 500000 Hz (~~0.0 B~~500 KHz)

~~RX errors 0 dropped 0 overruns 0 frame 0~~TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.

~~TX packets 0 bytes 0~~ RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF | ............................….|}</ol><ol start="5" style="list-style-type: decimal;"><li>Then short-circuit the two pins of mosi (pin 19 in the 40pin interface) and miso (~~0.0 B~~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>

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions~~ [[File:pi3b-img265.png]]{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo spidev_test -v -D /dev/spidev3.0'''

~~==== RTL8821CU test ====~~spi mode: 0x0

~~# 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. Make sure the USB module is not in the Driver CDROM Mode~~bits per word: 8

~~orangepi@orangepi~~max speed:~~~$ '''lsusb | grep "Realtek"'''~~500000 Hz (500 KHz)

~~Bus 002 Device 003~~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 | ......@.…▒.................. ~~802~~▒.~~11ac NIC~~

~~orangepi@orangepi:~$~~ RX | FF FF FF FF FF FF '''~~lsusb | grep "Realtek"~~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>

~~Bus 002 Device 002: ID 0bda:1a2b Realtek Semiconductor Corp. RTL8188GU 802.11n WLAN Adapter ('''Driver CDROM Mode''')~~=== 40pin I2C Test ===

~~'''If~~ # From the ~~USB WIFI module seen by~~ table below, the ~~lsusb command~~ I2C available for Orange Pi 3B is ~~in Driver CDROM Mode~~I2C2, ~~re -insert the USB WiFi module~~I2C3, and I2C4 a total of three groups of I2C bus. ~~If not, please manually execute the following command to switch the mode: '''~~

~~orangepi@orangepi~~:~~~$ '''sudo usb_modeswitch -KW~~ :[[File:pi3b-~~v 0bda~~ img266-~~p 1a2b'''~~1.png]]

~~<ol start~~::{| class="3wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>'''It can be seen from the above table that i2c4_m0 and spi3_m0 are pins. The ~~Linux system will automatically load~~ two cannot be opened at the ~~RTL8821CU Bluetooth~~ same time. i2c3_m0 and ~~WIFI -related kernel modules~~uart3_m0 are also reused. ~~You can see that~~ The two cannot be opened at the ~~kernel module below is automatically loaded through the lsmod command~~same time'''</~~li></ol~~big>|}

~~orangepi@orangepi:~$ '''lsmod'''~~ ~~Module Size Used by~~ ~~8821cu 1839104 0~~ ~~rtk_btusb 61440 0~~ <ol start="42" style="list-style-type: decimal;"><li>~~You can see~~ In the ~~loading information of~~ linux system, the ~~rtl8821cu module through~~ I2C bus in the ~~dmesg command~~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>First run '''orangepi-config''', normal users remember to add '''sudo''' permission</olp>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~dmesg~~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 I2C configuration you want to open[[File:pi3b-3-2.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>

~~......~~<ol start="3" style="list-style-type: decimal;"><li>After starting the Linux system, first confirm that the i2c device node exists under/dev</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~# '''ls /dev/i2c-*'''

~~[ 57.083693] usb~~ /dev/i2c-0      '''/dev/i2c-2'''      '''/dev/i2c-13'''      '''/dev/i2c-4'''      /dev/i2c-6|}</ol><ol start="4" style="list-style-type: ~~new high-speed USB~~ decimal;"><li>Then connect a i2c device ~~number 2 using ehci-platform~~on the i2c pin of the 40Pin connector</li>

~~[ 57~~{| class="wikitable" style="width:800px;text-align: center;"|-||i2c2-m1|i2c3-m0|i2c4-m0|-| Sda Pin|Corresponding to No.~~231888] usb 2~~ 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. 1pin|-| Gnd Pin|Corresponding to No. 6 pin|Corresponding to No. 6 pin|Corresponding to No. 6 pin|}</ol><ol start="5" style="list-style-type: ~~New USB~~ decimal;"><li>Then use the '''i2cdetect -y''' command if the address of the connected I2C device ~~found~~can be detected, ~~idVendor~~it means that the I2C can be used normally</li>{| class=~~0bda, idProduct=1a2b, bcdDevice~~"wikitable" style= "width:800px;" |-| orangepi@orangepi:~$ sudo i2cdetect -y 2~~.00~~#i2c2 command

~~[ 57.231916] usb 2~~orangepi@orangepi:~$ sudo i2cdetect -~~1: New USB device strings: Mfr=1, Product=2, SerialNumber=0~~y 3 #i2c3 command

~~[ 57.231937] usb 2~~orangepi@orangepi:~$ sudo i2cdetect -~~1: Product: DISK~~y 4 #i2c4 command|}

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

[ 57[File:pi3b-img267.~~242594~~png]] ~~usb-storage 2-1:1.0: USB Mass Storage device detected~~

~~[ 57.245674] scsi host0: usb~~</div></ol>

~~[ 58.069172] usb 2-1: USB disconnect, device number 2~~=== 40pin UART test ===

~~[ 58~~# As can be seen from the table below, the uart available for Orange Pi 3B is uart3, uart7, and uart9.~~440025] usb 2-1: new high-speed USB device number 3 using ehci-platform~~There are three sets of uart bus

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

~~[ 58.587827] usb 2~~::{| class="wikitable" style="background-1color: ~~New USB device strings~~#ffffdc;width: ~~Mfr=1~~800px;" |-| <big>'''As can be seen from the above table, ~~Product=2~~i2c3_m0 and uart3_m0 are reused by pins, ~~SerialNumber=3~~and the two cannot be opened at the same time'''</big>|}

<ol start="2" style="list-style-type: decimal;"><li>In the linux system, the UART in the 40 pins is closed by default, and it needs to be opened manually before it can be used. 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 orangepi-config'''|}</li><li>Then select '''System'''[[ 58File:pi3b-1.~~587833~~png] ~~usb~~ ]</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 UART configuration you want to open[[File:pi3b-13-3.png]]</li><li>Then select '''<Save>''' to save[[File:pi3b-4.png]]</li><li>Then select '''<Back>'''[[File: ~~Product~~pi3b-5.png]]</li><li>Then select '''<Reboot>''' to restart the system to make the configuration take effect[[File: ~~802~~pi3b-6.~~11ac NIC~~png]]</li></ol></li></ol>

~~[ 58.587838] usb 2~~<ol start="3" style="list-~~1: Manufacturer~~style-type: ~~Realtek~~decimal;"><li>After entering the Linux system, first confirm whether there is a device node corresponding to uart under/dev</li>

~~[ 58.587844] usb 2~~{| class="wikitable" style="width:800px;" |-~~1: SerialNumber~~| orangepi@orangepi: ~~123456~~~# '''ls /dev/ttyS*'''

~~[ 58.610463] rtk_btusb~~/dev/ttyS1      '''/dev/ttyS3      /dev/ttyS7      /dev/ttyS9'''|}</ol><ol start="4" style="list-style-type: ~~Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-142432~~decimal;"><li>Then start testing the uart interface, first use the rx and tx of the uart interface to be tested by DuPont</li>

~~[ 58.610656] usbcore~~{| class="wikitable" style="width: ~~registered new interface driver rtk_btusb~~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 22 pin|}

[ 58[File:pi3b-img269-1.~~634631~~png] ~~Bluetooth~~]</ol><ol start="5" style="list-style-type: ~~hci0~~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: ~~RTL: examining hci_ver~~lower-alpha;"><li>Test UART3</li>{| class=~~08 hci_rev~~"wikitable" style=~~000c lmp_ver=08 lmp_subver=8821~~"width:800px;" |-| orangepi@orangepi:~$ '''sudo gpio serial /dev/ttyS3'''

[ ~~58.636729~~sudo] ~~Bluetooth~~password for orangepi: ~~hci0: RTL: rom_version status=0 version=1~~#Enter the password here.

~~[ 58.636740] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin~~

~~[ 58.664190] Bluetooth~~Out: ~~hci0~~0: ~~RTL: loading rtl_bt/rtl8821c_config.bin~~-> 0

~~[ 58.664746] Bluetooth~~Out: ~~hci0~~1: ~~RTL: cfg_sz 10, total sz 31990~~-> 1

~~[ 59.122471] Bluetooth~~Out: ~~hci0~~2: ~~RTL: fw version 0x829a7644~~-> 2

~~[ 59.265513] usbcore~~Out: ~~registered new interface driver rtl8821cu~~3: -> 3

~~[ 59.280119] rtl8821cu 2-1~~Out:~~1.2 wlx90de80521825~~4: ~~renamed from wlan0~~-> 4

Out: 5: -> 5^C|}</ol><ol start="52" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then you can see the RTL8821CU WiFi device node through the~~ Test UART7</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ~~ifconfig~~gpio serial /dev/ttyS7''' ~~command. Please refer to the [[\l|'''WiFi connection test''']] a section for WIFI connection and testing methods.</li></ol>~~

~~orangepi@~~[sudo] password for orangepi:~~~$ '''sudo ifconfig wlx90de80521825'''~~#Enter the password here.

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

~~ether 00~~Out:130:~~ef:f4:58:ae txqueuelen 1000 (Ethernet)~~-> 0

~~RX packets 0 bytes 0 (0.0 B)~~Out: 1: -> 1

~~RX errors 0 dropped 0 overruns 0 frame 0~~Out: 2: -> 2

~~TX packets 0 bytes 0 (0.0 B)~~Out: 3: -> 3

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~Out: 4: -> 4

Out: 5: -> 5^C|}</ol><ol start="63" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then you can see the USB Bluetooth device through the~~ Test UART9</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~hciconfig~~sudo gpio serial /dev/ttyS9''' ~~command</li></ol>~~

~~orangepi@~~[sudo] password for orangepi:~~~$ '''sudo apt-get update && sudo apt-get install -y bluez'''~~#Enter the password here.

~~orangepi@orangepi:~$ '''hciconfig'''~~

~~hci0~~Out: ~~Type~~0: ~~Primary Bus: '''USB'''~~-> 0

~~BD Address~~Out: 001:~~13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16~~-> 1

~~DOWN~~Out: 2: -> 2

~~RX bytes~~Out:~~1252 acl~~3:~~0 sco:0 events:125 errors:0~~-> 3

~~TX bytes~~Out:~~23307 acl~~4:~~0 sco:0 commands:125 errors:0~~-> 4

Out: 5: -> 5^C|}</ol ~~start="7" style="list-style-type: decimal;"~~></li>~~Bluetooth icons can also be seen on the desktop. At this time, Bluetooth has not been opened, so a red '''x''' will be displayed~~</liol></olspan>

~~[[File:pi3b-img243.png|576x157px]]~~=== PWM test method ===

~~<ol start="8" style="list-style-type: decimal;"><li>Click '''Turn Bluetooth On''' to open Bluetooth</li></ol>~~ ~~[[File:pi3b-img244.png|576x262px]]~~ ~~<ol start="9" style="list-style-type: decimal;"><li>The display after opening Bluetooth is shown~~ # From the table below~~</li></ol>~~ ~~[[File:pi3b-img245.png|576x164px]]~~, the pwm11 available for Orange Pi 3B

~~<ol start="10" style="list-style-type~~: ~~decimal;"><li>Please refer to the [[\l|'''Bluetooth use chapter''']] for the Bluetooth test method. I won't go into details her</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~~ :[[File:pi3b-~~img13~~img270-1.png~~|259x150px~~]]

<li>~~You can see that~~ In the linux system, the PWM in the ~~USB camera's device node information~~ 40 pin isturned off by default, and it needs to be turned on manually before it can be used. The detailed steps are as follows:</~~dev/video0 through the v4l2~~p><ol style="list-style-type: lower-~~ctl command~~alpha;"></li>First run '''orangepi-config''', normal users remember to add sudo permission</olp>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~v4l2~~sudo orangepi-config'''|}</li><li>Then select '''System'''[[File:pi3b-1.png]]</li><li>Then select '''Hardware'''[[File:pi3b-2.png]]</li><li>Then use the arrow keys on the keyboard to navigate to the position shown in the figure below, and then use the '''space''' to select the PWM configuration you want to open[[File:pi3b-~~ctl~~ 3-4.png]]</li><li>Then select '''<Save>''' to save[[File:pi3b-~~list~~4.png]]</li><li>Then select '''<Back>'''[[File:pi3b-~~devices~~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>

~~Q8 HD Webcam~~<ol start="3" style="list-style-type: ~~Q8 HD Webcam~~ 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 '''~~usb~~/sys/class/pwm/'''one becomes two</li>{| class="wikitable" style="width:800px;" |-~~fc880000.usb-1)~~| orangepi@orangepi:~$ '''ls /sys/class/pwm/'''

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'''command first, as shown below:</~~dev~~p></~~video0~~li><li>Then it can be known from the table below that the base address of the pwm11 register is fe6f0030, and then look at the output of the '''ls /sys/class/pwm/ -l''' command, you can see that pwmchip1 is linked to fe6f0030.pwm, so pwm11 corresponds to pwmchip as pwmchip1</li>

~~/dev/video1~~<div class="figure">

~~/dev/media0~~[[File:pi3b-img271.png]]

</div></ol><ol start="6" style="list-style-type: decimal;"><li>Then use the following command to make pwm11 output a 50Hz square wave (please switch to the root user first, and then execute the following command)</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''~~Note that l in v4l2 is a lowercase letter l, not numbers 1.~~echo 0 > /sys/class/pwm/pwmchip1/export'''

root@orangepi:~# '''~~In addition, Video's serial number is not necessarily Video0, please refer to what you see.~~echo 20000000 > /sys/class/pwm/pwmchip1/pwm0/period'''

~~<ol start="3" style="list-style-type~~root@orangepi: ~~decimal~~~# '''echo 1000000 >">~~<li>In the desktop system, you can use Cheese to directly turn on the USB camera. The cheese opening method is shown in the figure below: <~~/~~li><~~sys/class/pwm/pwmchip1/pwm0/~~ol>~~duty_cycle'''

~~[[File~~root@orangepi:~~pi3b-img246.png~~~# '''echo 1 > /sys/class/pwm/pwmchip1/pwm0/enable'''|~~474x302px]]~~}

~~The interface after cheese opens the USB camera is shown in the figure below~~[[File: pi3b-img272.png]]

~~[[File:pi3b~~<li>The test method of pwm11 demonstrated above is similar to other pwm test methods.</li></ol>

~~<ol start~~=~~"4" style~~=~~"list-style-type: decimal;"><li>~~How to ~~test the USB camera using fswebcam<ol style~~install and use wiringOP-Python ==~~"list-style-type: lower-alpha;"><li>Install fswebcam</li></ol></li></ol>~~

~~orangepi@orangepi~~{| class="wikitable" style="background-color:~~~$ '''sudo'''~~ #ffffdc;width:800px;" |-| <big>'''~~apt update~~wiringOP-Python is the Python language version of wiringOP, which is used to operate the hardware resources of the development board, such as GPIO, I2C, SPI and UART, in the Python program.'''

~~orangepi@orangepi:~$ '''sudo apt-get install -y fswebcam'''~~

~~<ol start="2" style="list-style-type: lower-alpha;"><li>After installing fswebcam~~'''In addition, ~~you can use~~ please note that all the following ~~command to take pictures<ol style="list-style-type: lower-alpha;"><li>-d The option is used to specify the device node of the USB camera</li><li>--no-banner Used to remove the watermark of photos</li><li>-r The option is used to specify the resolution of~~ commands are operated under the ~~photo</li><li>-S The option is set to the number of frames before skipping</li><li>./image~~root user.~~jpg The name and path for setting the generated photos~~'''</~~li></ol~~big>~~</li></ol>~~|}

~~orangepi@orangepi:~$ '''sudo''' '''fswebcam~~ </~~dev/video0 \'''~~span>=== wiringOP-Python installation method ===

~~'''--no-banner -r 1280x720 -S 5 ./image.jpg'''~~# First install the dependency package

~~<ol start~~::{| class="3wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<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>~~|-| root@orangepi:~# '''sudo apt-get update'''

~~orangepi~~root@orangepi:~~~$ '''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）~~sudo apt-get -y install git swig python3-dev python3-setuptools'''|}

<ol start="42" style="list-style-type: ~~lower-alpha~~decimal;"><li>In Then use the ~~desktop version~~ following command to download the source code of ~~the Linux system, you can directly view the shot pictures through the HDMI display~~wiringOP-Python</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <~~/ol~~big>'''Note that the following git clone--recursivee command will automatically download the source code of wiringOP, because wiringOP-Python depends on wiringOP. Please make sure that the download process does not report an error due to network problems.'''

~~~~

~~== Audio Test ==~~

'''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'''<~~span id~~/big>|}{| class="~~test~~wikitable" style="width:800px;" |-~~audio~~| root@orangepi:~# '''git clone -~~methods~~-inrecursive https://github.com/orangepi-~~the~~xunlong/wiringOP-~~desktop~~Python -~~system">=== Test audio methods in the desktop system ===~~b next'''

root@orangepi:~# ~~First open the file manager~~'''cd wiringOP-Python'''

~~[[File~~root@orangepi:~~pi3b~~~/wiringOP-Python# '''git submodule update --~~img248.png|357x176px]]~~ ~~<ol start="2" style="list~~init -~~style~~-~~type: decimal;">~~remote'''~~<li>Then find the following file (if there is no audio file in the system, you can upload a audio file to the system by yourself)</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img249.png|236x186px~~|~~图片10]]~~}</~~div~~ol>

<li>Then ~~select~~ use the ~~audio.wav file, right~~ following command to compile wiringOP-~~click~~ Python and ~~select VLC to open~~ install it ~~to start playing~~into the Linux system of the development board</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''cd wiringOP-Python'''

~~[[File~~root@orangepi:~~pi3b~~~/wiringOP-~~img250~~Python# '''python3 generate-bindings.py > bindings.~~png|288x234px]]~~i'''

root@orangepi:~/wiringOP-Python# '''sudo python3 setup.py install'''

|}

</ol>

<li>~~Methods~~ Then enter the following command. If there is a help information output, it means that Wiringop-Python is successfully installed. Press the '''q''' key to ~~switch different audio equipment such as HDMI playback and headset playback<ol style="list-style-type: lower-alpha;"><li>First open~~ exit the ~~volume control~~ interfaceof the help information</li~~></ol></li></ol~~>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img251.png~~|~~308x169px]]~~root@orangepi:~/wiringOP-Python# '''python3 -c "import wiringpi; help(wiringpi)"'''

~~<ol start="2" style="list-style-type~~Help on module wiringpi: ~~lower-alpha;">~~<li>When playing audio, the audio equipment options that play software can be used will be displayed in '''Playback'''. As shown in the figure below, which audio equipment you need to play here can be set.</li></ol>

~~[[File:pi3b-img252.png|576x282px]]~~

~~=== How to play audio with commands ===~~NAME

~~==== Headphone interface play audio test ====~~:wiringpi

~~# First insert the headset into the headphone jack of the development board~~

~~[[File:pi3b-img253.png|395x112px]]~~DESCRIPTION

~~<ol start="2" style="list-style-type~~: ~~decimal;"><li>Then you can check the sound card device supported~~ # This file was automatically generated 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<~~SWIG (http:/~~li><~~/~~ol>~~www.swig.org).

~~orangepi@orangepi~~:~~~$ '''aplay -l'''~~# Version 4.0.2

~~**** List of PLAYBACK Hardware Devices ****~~: #

~~'''card 0~~: ~~rockchiprk809 [rockchip~~# Do not make changes to this file unless you know what you are doing-~~rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi~~-~~0]'''~~modify

: # the SWIG interface file instead.|}</ol><ol start="5" style="list-style-type: decimal;"><li>Test whether the wiringOP-Python is installed successfully under the Python command line is shown below:<ol style="list-style-type: lower-alpha;"><li>First use the Python3 command to enter the command line mode of Python3</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''~~Subdevices: 0/1~~python3'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then import the Python module of WiringPi</li>{| class="wikitable" style="width:800px;" |-| >>> '''~~Subdevice #0: subdevice #0~~import wiringpi;'''|}</ol>~~card 1: rockchiphdmi [rockchip,hdmi], device 0: fe400000.i2s~~<ol start="3" style="list-~~i2s~~style-~~hifi i2s~~type: lower-~~hifi~~alpha;"><li>Enter the following command to view the help information of wiringOP-~~0 [fe400000.i2s~~Python, and press the '''q''' key to exit the interface of the help information</li>{| class="wikitable" style="width:800px;" |-~~i2s-hifi i2s-hifi-0]~~| >>> '''help(wiringpi)'''

~~Subdevices~~Help on module wiringpi: ~~0/1~~

~~Subdevice #0: subdevice #0~~

~~Subdevice #0: subdevice #0~~NAME

~~<ol start="3" style="list-style-type~~: ~~decimal;"><li>Then use the '''aplay''' command to play the audio file that comes with the system. If the headset can hear the sound, it means that the hardware can be used normally</li></ol>~~wiringpi

~~orangepi@orangepi:~$ '''aplay -D hw:0,0 /usr/share/sounds/alsa/audio.wav'''~~

~~Playing WAVE 'audio.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo~~DESCRIPTION

~~<~~: # This file was automatically generated by SWIG (http:/~~span>==== HDMI Audio Play Test ====~~/www.swig.org).

: # ~~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~~Version 4.0. ~~From the output below, you can know that the HDMI sound card is '''card 1'''~~2

~~orangepi@orangepi~~:~~~$ '''aplay -l'''~~#

~~**** List of PLAYBACK Hardware Devices ****~~: # Do not make changes to this file unless you know what you are doing--modify

~~card 0~~: ~~rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]~~# the SWIG interface file instead.

~~Subdevices: 0/1~~

~~Subdevice #0: subdevice #0~~CLASSES

~~'''card 1~~: ~~rockchiphdmi [rockchip,hdmi], device 0: fe400000.i2s-i2s-hifi i2s-hifi-0 [fe400000~~builtins.~~i2s-i2s-hifi i2s-hifi-0]'''~~object

~~'''Subdevices~~: ~~0/1'''~~:GPIO

~~'''Subdevice #0~~: ~~subdevice #0'''~~:I2C

~~'''Subdevice #0~~: ~~subdevice #0'''~~:Serial

~~<ol start="3" style="list-style-type~~: ~~decimal;"><li>Then use the '''aplay''' command to play the audio file that comes with the system. If the HDMI display or television can hear the sound indicates that the hardware can be used normally</li></ol>~~:nes

~~orangepi@orangepi:~$ '''aplay -D hw:1,0 /usr/share/sounds/alsa/audio.wav'''~~

~~=== Use the command to test the recording method ===~~:class GPIO(builtins.object)

# 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:| GPIO(pinmode=0)

~~orangepi@orangepi~~:~~~$ '''amixer -c 0 cset name='Capture MIC Path' 'Main Mic''''~~|

~~orangepi@orangepi:~$ '''arecord -D hw:0,0 -d 5 -f cd -t wav /tmp/test.wav'''~~

>>>|}</ol></li></ol>~~== Temperature Sensor ==~~

~~# The command of the system temperature sensor is:~~ === 40pin GPIO port test ===

~~orangepi@orangepi~~{| class="wikitable" style="background-color:~$ #ffffdc;width:800px;" |-| <big>'''~~sensors~~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>

~~soc_thermal-virtual-0~~<div class="figure">

~~Adapter~~[[File: ~~Virtual device~~pi3b-img258.png|center]]

~~temp1: +41~~</div>|}# Below the No.~~9°C (crit = +115.0°C)~~ 7 pin — corresponding to GPIO4_a4 -corresponding WPI serial number 2 -to demonstrate how to set the height of the GPIO port

~~gpu_thermal-virtual-0~~ ~~Adapter~~: ~~Virtual device~~ ~~temp1~~: ~~+43~~[[File:pi3b-img259.~~8°C~~png]]

<li>The ~~command~~ steps of the ~~current temperature of the NVMe SSD solid -state hard disk is: orangepi@orangepi:~$ '''sudo smartctl -a /dev/nvme0 | grep "Temperature:"'''Temperature: '''40 Celsius'''</li></ol>~~ ~~== 40 Pin interface pin explanation ==~~ ~~# Orange Pi 3B Development board 40 Pin interface pins, please refer to the figure~~ command test are shown below ~~<div class="figure">~~ ~~[[File:pi3b-img254.png|400x124px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\Orange-Pi-3B-Development-board-40-Pin(1).jpgOrange-Pi-3B-Development-board-40-Pin(1)]]~~ ~~</div><ol start="2" style="list-style-type~~directly: ~~decimal;"><li>The function of the Orange Pi 3B development board 40 PIN interface pins is shown in the table below.~~

<li>~~Below~~ First set the GPIO port to the output mode. The first parameter of the '''pinMode''' function is ~~a complete pins~~ the serial number of ~~40pin~~the wpi corresponding to the pin, and the second parameter is the GPIO mode</li>~~</ol>~~<{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~li></ol>~~wiringOP-Python# '''python3 -c "import wiringpi; \'''

~~[[File:pi3b-img255~~'''from wiringpi import GPIO; wiringpi.~~png|575x160px]]~~wiringPiSetup() ; \'''

'''wiringpi.pinMode(2, GPIO.OUTPUT) ; "'''

|}

</ol>

<li>~~The following form is a picture on~~ Then set the GPIO port output low level. After setting, you can use the voltage of the ~~left half~~ voltage of the ~~full table above~~universal meter to measure the pins. If it is 0V, ~~which can be seen clearly~~it means that the low -power flat is successful</li><{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~ol>~~wiringOP-Python# '''python3 -c "import wiringpi; \'''

~~[[File:pi3b-img256~~'''from wiringpi import GPIO; wiringpi.~~png|478x267px]]~~wiringPiSetup() ;\'''

'''wiringpi.digitalWrite(2, GPIO.LOW)"'''

|}

</ol>

<li>~~The following form is a picture on~~ Then set the GPIO port output high level. After setting, you can use the value of the ~~right half~~ voltage of the ~~top table above~~pins with a multimeter. If it is 3.3V, ~~which can be seen clearly~~it means that the high -power flat is successful.</li><{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~ol>~~wiringOP-Python# '''python3 -c "import wiringpi; \'''

~~[[File:pi3b-img257~~'''from wiringpi import GPIO; wiringpi.~~png|479x266px]]~~wiringPiSetup() ;\'''

'''wiringpi.digitalWrite(2, GPIO.HIGH)"'''

|}

</ol>

</li></ol>

<li>~~There are a total~~ The steps of ~~'''28''' GPIO ports~~ testing in the ~~40pin interface. The voltage~~ command line of Python3 are shown below: <ol style="list-style-type: lower-alpha;"><li>First use the Python3 command to enter the command line mode of ~~all GPIO ports is~~ Python3</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''~~3.3v~~python3'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then import the Python module of WiringPi</olli>{| class="wikitable" style="width:800px;" |-| >>> '''import wiringpi'''

>>> '''from wiringpi import GPIO'''|}<~~span id~~/ol><ol start="~~how~~3" style="list-tostyle-~~install~~type: lower-~~wiringop~~alpha;"><~~/span~~li>~~== How to install Wiringop ==~~ Then set the GPIO port as the output mode. The first parameter of the '''pinMode''~~Note that Wiringop has been pre -installed in the Linux image released by Orange Pi. Unless Wiringop~~'~~s code~~ function is ~~updated~~the serial number of the wpi corresponding to the pin, it and the second parameter is ~~not necessary to re~~ the GPIO mode.</li>{| class="wikitable" style="width:800px;" |-~~download and install. Just use it directly.'''~~| >>> '''~~The storage path of the compiled Wiringop's Deb is wrapped in Orangepi-Build:~~ wiringpi.wiringPiSetup()'''

~~'''orangepi-build/external/cache/debs/arm64/wiringpi_x.xx.deb'''~~0

>>> '''wiringpi.pinMode(2, GPIO.OUTPUT)'''|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then set the GPIO port output low level. After ~~entering the system~~setting, you can ~~run~~ use the value of the voltage of the ~~gpio readall command~~pins with a multimeter. If it is 0V, it means that the low -power flat is set.</li>{| class="wikitable" style="width:800px;" |-| >>> '''wiringpi.digitalWrite(2, GPIO.LOW)'''|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then set the GPIO port output high level. After setting, you can ~~see~~ use the ~~output below~~value of the voltage of the pins with a multimeter. If it is 3.3V, it means that ~~wiringOP~~ the high -power flat is ~~pre~~ successful</li>{| class="wikitable" style="width:800px;" |-| >>> '''wiringpi.digitalWrite(2, GPIO.HIGH)'''|}</ol></li></ol><ol start="4" style="list-style-type: decimal;"><li>Wiringop-~~installed~~ Python Sets GPIO high and ~~can be used normally~~low levels in the Python code. For reference to the '''blink.py''' test program in Examples, the voltage of the '''blink.py''' test program will set up the voltage of all GPIO ports in the development board 40 PIN</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''cd examples'''

~~<div class="figure">~~root@orangepi:~/wiringOP-Python/examples# '''ls blink.py'''

~~[[File:pi3b-img258~~'''blink.~~png|575x355px|66AC(IBG%N8L@Y7(1BZPS`N]]~~py'''

<root@orangepi:~/wiringOP-Python/~~div>~~examples'''wiringOP is currently adapted to set the GPIO port input output, set the GPIO port output high and low level, and set the function of pulling and down resistance. It is impossible to use functions like hardware PWM# python3 blink.py'''|}</ol>

~~# Download the code of Wiringop~~=== 40pin SPI test ===

~~orangepi@orangepi:~$ '''sudo apt update'''~~# From the schematic diagram of the 40pin interface, the SPI available for Orange Pi 3B is spi3

~~orangepi@orangepi~~:~~~$ '''sudo apt install~~ :[[File:pi3b-~~y git'''~~img264.png]]

~~orangepi@orangepi~~:~$ :{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~git clone https://github.com/orangepi-xunlong/wiringOP~~In the Linux system, the spi3 in 40pin is closed by default, and it needs to be opened manually to use.~~git -b next~~'''

~~'''Note that Orange Pi 3B needs to download the code of the wiringOP next branch, please don't miss the parameter of -b next.'''~~

'''~~If there is a problem with~~ Add the ~~download code from GitHub, you can use~~ configuration of the ~~wiringOP source code that comes with~~ red font part below to the ~~Linux image directly~~/boot/orangepiEnv.txt, and then restart the Linux system to open the ~~storage location is:/usr/src/wiringOP~~spi4.'''</big>

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

~~<li>Compile and install wiringOP</li></ol>~~

orangepi@orangepi:~$ '''~~cd wiringOP~~sudo vim /boot/orangepiEnv.txt'''

~~orangepi@orangepi:~/wiringOP$~~ '''~~sudo .~~overlays=spi3-m0-cs0-spidev</~~build clean~~span>'''|}

<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 and can be used directly</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~~~/wiringOP~~$ '''~~sudo~~ ls /dev/spidev3.~~/build~~0'''

/dev/spidev3.0

|}

</ol>

<li>~~Test~~ You can then use the spi back function under the '''spidev_test.py''' program in Examples. The '''spidev_test.py''' program needs to specify the following two parameters: <ol style="list-style-type: lower-alpha;"><li>'''--channel''': Specify the channel number of SPI</li><li>'''--port''': Specify the port number of SPI</li></ol></li><li>Do not pick up the two pins of the SPI3 MOSI and MISO in short, and run the output result of the ~~GPIO Readall command~~ spidev_test.py as ~~follows~~shown below. You can see that the data of TX and RX are inconsistent</lip></olli>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''cd examples'''

~~<div class="figure">~~root@orangepi:~/wiringOP-Python/examples# '''python3 spidev_test.py \'''

~~[[File:pi3b~~'''-~~img258.png|575x355px|66AC(IBG%N8L@Y7(1BZPS`N]]~~-channel 3 --port 0'''

~~</div>== 40Pin interface GPIO, I2C, UART, SPI, and PWM test ==~~mode: 0x0

~~'''Note that if you need to set overlays to open multiple configurations at the same time, please use a space to write in one line like the following space.'''~~max speed: 500000 Hz (500 KHz)

~~orangepi@orangepi:~$ '''sudo vim~~ Opening device /~~boot~~dev/~~orangepiEnv~~spidev3.~~txt'''~~0

TX | FF FF FF FF FF FF '''~~overlays~~40 00 00 00 00 95'''FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…|

RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |.............….||}</ol><ol start="5" style== "list-style-type: decimal;"><li>Then use the TXD (No. 19 pins in the 40Pin interface) and RXD (No. 21 pins in the 40pin ~~GPIO port~~ interface) of the DuPont line short connection SPI3. Like sending and receiving data, it means that the SPI3 loop test is normal</li>{| class="wikitable" style=="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''cd examples'''

root@orangepi:~/wiringOP-Python/examples# '''~~The Linux system released by Orange Pi has a pre -installed blink_all_gpio program. This program will set up all 28 GPIO ports in 40pin to switch high and low levels~~python3 spidev_test.py \'''

'''~~After running the blink_all_gpio program, when using a multimeter to measure the level of the GPIO~~ --channel 3 --port~~, you will find that the GPIO pin will be switched between~~ 0 ~~and 3.3v. Use this program to test whether the GPIO port can work normally~~'''

~~'''The method of running blink_all_gpio program is shown below~~spi mode: ~~'''~~0x0

~~orangepi@orangepi3b~~max speed:~~~$ '''sudo blink_all_gpio''' #Remember to add Sudo permissions~~500000 Hz (500 KHz)

~~[sudo] password for orangepi: #You need to enter a password here~~Opening device /dev/spidev3.0

TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |. ~~Below is No~~. ~~7 pins -corresponding GPIO as GPIO4_A4 -corresponding WPI serial number 2 -as an example how to set the height of the GPIO port~~....@.......…|

~~[[File~~RX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......~~png~~…|~~576x120px]]~~|}</ol>

~~<ol start~~=~~"2" style~~=~~"list-style-type: decimal;"><li>First set the GPIO port as the output mode, the third parameter needs to enter the serial number of the wPi corresponding to the pins</li></ol>~~= 40pin I2C test ===

~~root@orangepi~~<ol start="1" style="list-style-type:~decimal;"><li>As can be seen from the table below, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total of three groups of I2C bus</~~wiringOP# '''gpio mode 2 out'''~~li>

~~<ol start="3" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Then set the GPIO port to output the low level~~img266. ~~After setting, you can use the value of the voltage of the pins with a multimeter. If it is 0v, it means that the low -electric flat is successful</li></ol>~~png]]

~~root@orangepi~~{| class="wikitable" style="background-color:~#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'''</~~wiringOP~~big>|}{| class="wikitable" style="background-color:# ffffdc;width:800px;" |-| <big>'''~~gpio write 2 0~~In the Linux system, the I2C in 40Pin is closed by default, and it needs to be opened manually to use.'''

~~Using GPIO Readall, you can see the value of the No. 7 pin (v) to 0~~

~~[[File:pi3b-img260~~'''Add the configuration of the red font part below to the/boot/orangepiEnv.~~png|576x120px]]~~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>

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

<li>Then set the GPIO port output high level. After setting, you can use the voltage of the voltage of the permanent meter to measure the voltage. If it is 3.3V, it means that the high-electricity level is successful</li></ol>

~~root~~orangepi@orangepi:~~~/wiringOP#~~ $ '''~~gpio write 2 1~~sudo vim /boot/orangepiEnv.txt'''

~~Using GPIO Readall~~'''overlays=i2c2-m1 i2c3-m0 i2c4-m0'''|}</ol><ol start="2" style="list-style-type: decimal;"><li>After starting the Linux system, ~~you can see~~ first confirm the ~~value of No~~I2C device node under/dev. ~~7 pin (v) into 1~~</li>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img261.png~~|~~576x118px]]~~orangepi@orangepi:~# '''ls /dev/i2c-*'''

/dev/i2c-0      '''/dev/i2c-2'''      '''/dev/i2c-3'''      '''/dev/i2c-4'''      /dev/i2c-6|}</ol><ol start="53" style="list-style-type: decimal;"><li>~~The setting method~~ Then connect a I2C device on the I2C pin of ~~other pins~~ the 40PIN connector. Here is ~~similar. Just modify the serial number~~ an example of the ~~wPi sequence number as the corresponding serial number corresponding to the pin~~DS1307 RTC module.</li~~></ol~~>

~~<span id~~{| class="wikitable" style="~~pin~~width:800px;text-~~gpio~~align: center;"|-~~port~~||i2c2-m1|i2c3-~~down~~m0|i2c4-~~and~~m0|-~~downward~~| Sda Pin|Corresponding to No. 3 pin|Corresponding to No. 27 pin|Corresponding to No. 19 pin|-~~pull~~| Sck Pin|Corresponding to No. 5 pin|Corresponding to No. 28 pin|Corresponding to No. 23 pin|-~~-down-resistance-setting-method">=== 40Pin GPIO Port -down and downward pull -down resistance setting method ===~~| Vcc Pin|Corresponding to No. 1 pin|Corresponding to No. 1 pin~~'''Note that the 4 GPIO pins below Orange Pi 3B are invalid because there are 3~~|Corresponding to No.~~3V on the outside, so setting drop~~ 1 pin|-~~down is invalid~~| Gnd Pin|Corresponding to No. ~~Other pins can be set normally'''~~ 6 pin|Corresponding to No. 6 pin~~[[File:pi3b-img262~~|Corresponding to No.~~png~~6 pin|~~575x353px]]~~}

~~# Below the No~~[[File:pi3b-img273. ~~11 pin—corresponding to GPIO 3_C6~~png]]</ol><ol start="4" style="list-~~corresponding WPI serial number 5—to demonstrate how to set up and down pull~~style-type: decimal;"><li>Then use the '''i2cdetect -~~down resistance~~ y''' command If the address of the ~~GPIO port~~connected I2C device can be detected, it means that the I2C can be used normally</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ sudo i2cdetect -y 2 #i2c2 command

~~[[File~~orangepi@orangepi:~~pi3b~~~$ sudo i2cdetect -~~img263.png|576x147px]]~~y 3 #i2c3 command

~~<ol start="2" style="list~~orangepi@orangepi:~$ sudo i2cdetect -~~style-type: decimal;">~~y 4 #i2c4 command~~<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'''~~<div class="figure">

~~<ol start="3" style="list-style-type~~[[File: ~~decimal;"><li>After the setting is set to input mode, execute the following command to set the GPIO port as the pull~~ pi3b-~~down mode</li></ol>~~img274.png]]

</div></ol><ol start="5" style="list-style-type: decimal;"><li>You can then run the time of the ds '''ds1307.py''' test program in '''examples''' to read the RTC time</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''~~gpio mode 5 up~~cd examples'''

~~<ol start="4" style="list-style-type~~root@orangepi: ~~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><~~wiringOP-Python/~~ol>~~examples# '''python3 ds1307.py --device \'''

~~root@orangepi:~/wiringOP#~~ '''~~gpio read 5~~"/dev/i2c-4"'''

~~'''1'''~~Thu 2023-01-05 14:57:55

~~<ol start="5" style="list~~Thu 2023-~~style~~01-~~type~~05 14: ~~decimal;"><li>Then execute the following command to set the GPIO port as the drop-down mode</li></ol>~~57:56

~~root@orangepi~~Thu 2023-01-05 14:~~~/wiringOP# '''gpio mode 5 down'''~~57:57

~~<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 0, it means that the drop -down mode is set successfully</li></ol>~~^C

~~root@orangepi:~~~exit|}</~~wiringOP# '''gpio read 5'''~~ol>

=== 40pin'~~''0'''~~s UART test ===

~~=== 40pin SPI Test ===~~# As can be seen from the table below, the UART available for Orange Pi 3B is UART3, UART7 and UART9. There are three sets of UART bus

~~# From the schematic diagram of the 40PIN interface, the SPI available for Orange Pi 3B is spi3~~::[[File:pi3b-img268.png]]

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;background-~~img264.png~~color:#ffffdc;" |-| <big>'''As can be seen from the above table, I2C3_M0 and UART3_M0 are reused by pins, and the two cannot be opened at the same time'''</big>|~~577x193px]]~~}

::{| class="wikitable" style="width:800px;background-color:#ffffdc;" |-| <big>'''In the Linux system, the ~~SPI3~~ 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 ~~spi3~~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 /boot/orangepiEnv.txt'''

'''overlays=~~spi3~~uart3-m0uart7-~~cs0~~m2 uart9-~~spidev~~m2'''|}

<li>~~First check~~ After entering the Linux system, first confirm whether there is a ~~'''spidev3.0'''~~ device node ~~in the Linux system. If it exists, it means that the SPI3 has been set. You can use it directly~~corresponding to UART under/dev</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ # '''ls /dev/~~spidev3.0~~ttyS*''' ~~/dev/spidev3.0~~

/dev/ttyS1      '''/dev/ttyS3      /dev/ttyS7      /dev/ttyS9'''

|}

</ol>

<li>~~Do not shorten~~ Then start testing the ~~two pins of the SPI3 MOSI and MISO~~UART interface, and ~~run~~ first use the ~~output result~~ RX and TX of the ~~spidev_test as shown below. You can see that the data of TX and RX is inconsistent~~UART interface to be tested by DuPont</li~~></ol~~>

~~orangepi~~{| class="wikitable" style="width:800px;text-align: center;"|-||uart3|uart7|uart9|-| Tx Pin|Corresponding to the 28 pin|Corresponding to the 16 pin|Corresponding to the 29 pin|-| Rx Pin|Corresponding to the 27 pin|Corresponding to the 15 pin|Corresponding to the 7 pin|}</ol><ol start="4" style="list-style-type: decimal;"><li>Use the '''serialTest.py''' program in Examples to test the loop function of the serial port. If you can see the printing below, it means that the serial communication is normal<ol style="list-style-type: lower-alpha;"><li>Test UART3</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ /wiringOP-Python/examples# '''~~sudo spidev_test~~ python3 serialTest.py -v -~~D /dev/spidev3.0~~device \'''

~~spi mode: 0x0~~'''"/dev/ttyS3"'''

~~bits per word: 8~~

~~max speed~~Out: ~~500000 Hz (500 KHz)~~0: -> 0

~~TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.~~Out: 1: -> 1

~~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 | ............................….~~Out: 2: -> 2

~~<ol start="4" style="list-style~~Out: 3: -~~type: decimal~~>"><li>Then the two pins of the SPI3 MOSI (No. 19 pins in the 40pin interface) and MISO (No. 21 in the 40PIN interface) run the output of SPIDEV_TEST as follows.You can see that sending and receiving data is the same.</li></ol>3

~~[[File~~Out:~~pi3b-img265.png|577x83px]]~~4:^C

~~orangepi~~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# '''~~sudo spidev_test~~ python3 serialTest.py -v -~~D /dev/spidev3.0~~device \'''

~~spi mode: 0x0~~'''"/dev/ttyS7"'''

~~bits per word: 8~~

~~max speed~~Out: ~~500000 Hz (500 KHz)~~0: -> 0

~~TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.~~Out: 1: -> 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 | ......@.…▒..................▒.~~Out: 2: -> 2

~~=== 40pin I2C Test ===~~> 3

~~# From the table below, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total of three groups of I2C bus.~~Out: 4:^C

~~[[File~~exit|}</ol><ol start="3" style="list-style-type:~~pi3b~~lower-~~img266~~alpha;"><li>Test UART9</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python/examples# '''python3 serialTest.~~png|576x160px]]~~py --device \'''

'''~~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~~"/dev/ttyS9"'''

~~'''In the Linux system, the i2c 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 i2c2, i2c3, and i2c4 at the same time. If you only need to open one, then fill in one.'''Out: 0: -> 0

~~orangepi@orangepi~~Out:~~~$ '''sudo vim /boot/orangepiEnv.txt'''~~1: -> 1

~~'''overlays=i2c2~~Out: 2: -~~m1 i2c3-m0 i2c4-m0'''~~> 2

~~<ol start="2" style="list-style~~Out: 3: -~~type: decimal~~>">~~<li>After starting the Linux system, first confirm that the i2c device node exists under/dev</li></ol>~~3

~~orangepi@orangepi~~Out:~~~# '''ls /dev/i2c-*'''~~4:^C

~~/dev/i2c-0 '''/dev/i2c-2''' '''/dev/i2c-3''' '''/dev/i2c-4''' /dev/i2c-6~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then connect a i2c device on the i2c pin of the 40Pin connector</li></ol>~~ ~~{| class="wikitable"~~|-|~~| style="text-align: left;"| i2c2-m1| style="text-align: left;"| i2c3-m0| style="text-align: left;"| i2c4-m0~~|-~~| Sda Pin| style="text-align: left;"| Corresponding to No. 3 pin| style="text-align: left;"| Corresponding to No. 27 pin| style="text-align: left;"| Corresponding to No. 19 pin~~|-~~| Sck Pin| style="text-align: left;"| Corresponding to No. 5 pin| style="text-align: left;"| Corresponding to No. 28 pin| style="text-align: left;"| Corresponding to No. 23 pin~~|-~~| Vcc Pin| style="text-align: left;"| Corresponding to No. 1 pin| style="text-align: left;"| Corresponding to No. 1 pin| style="text-align: left;"| Corresponding to No. 1 pin~~|-~~| Gnd Pin| style="text-align: left;"| Corresponding to No. 6 pin| style="text-align: left;"| Corresponding to No. 6 pin| style="text-align: left;"| Corresponding to No. 6 pin~~exit

|}

</ol>

</li></ol>

~~<ol start~~=~~"4" style~~=~~"list-style-type: decimal;"><li>Then use~~ Hardware watch 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>~~door dog test ==

~~orangepi@orangepi:~$ sudo i2cdetect~~ The WatchDog_test program is pre -~~y 2 #i2c2 command~~installed in the Linux system released by Orange PI, which can be tested directly.

~~orangepi@orangepi~~The method of running the WatchDog_test program is shown below:~~~$ sudo i2cdetect -y 3 #i2c3 command~~

~~orangepi@orangepi~~<ol style="list-style-type:~~~$ sudo i2cdetect~~ lower-~~y 4 #i2c4 command~~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>

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

~~[[File:pi3b-img267.png|476x179px|UN}~]Q}T_70O%Z%RNO8R@YE]]~~open success

~~</div>=== 40pin UART test ===~~wdt

~~# As can be seen from the table below~~put_usr return, ~~the uart available for Orange Pi 3B is uart3~~if 0, ~~uart7, and uart9. There are three sets of uart bus~~success:0

~~[[File~~The old reset time is:~~pi3b-img268.png|575x160px]]~~16

~~'''As can be seen from the above table~~return ENOTTY, ~~i2c3_m0 and uart3_m0 are reused by pins~~if -1, ~~and the two cannot be opened at the same time'''~~success:0

~~'''In the Linux system~~return ENOTTY, ~~the uart in 40pin is closed by default~~if -1, ~~and it needs to be opened manually to use.'''~~success:0

~~'''Add the configuration of the red font part below to the /boot/orangepiEnv.txt~~put_user return, ~~and then restart the Linux system to open the uart3~~if 0, ~~uart7, and uart9 at the same time. If you only need to open one, you can fill in one..'''~~success:0

~~orangepi@orangepi~~put_usr return,if 0,success:~~~$ '''sudo vim /boot/orangepiEnv.txt'''~~0

~~'''overlays=uart3-m0 uart7-m2 uart9-m2'''~~keep alive

~~<ol start="2" style="list-style-type: decimal;"><li>After entering the Linux system, first confirm whether there is a device node corresponding to uart under/dev</li></ol>~~keep alive

~~orangepi@orangepi:~# '''ls~~ keep alive|}</~~dev~~ol></~~ttyS*'''~~span>

~~/dev/ttyS1 '''/dev'''/'''ttyS3 /dev/ttyS7 /dev/ttyS9'''~~== Check the serial number of the RK3566 chip ==

~~<ol start="3" style="list-style-type: decimal;"><li>Then start testing~~ The commands of the ~~uart interface~~RK3566 chip serial number are shown below. The serial number of each chip is different, ~~first~~ so you can use the ~~rx and tx of the uart interface~~ serial number to ~~be tested by DuPont</li></ol>~~distinguish multiple development boards.

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

|-

|orangepi@orangepi:~$ '''cat_serial.sh''' Serial : '''8fa18eaf489041f0'''| } == The method of downloading and installing the balenaEtcher version of arm64 == <ol style="~~text~~list-~~align~~style-type: ~~left~~decimal;"~~| uart3~~><li>The download address of Balenaetcher ARM64 version is: | <ol style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"~~| uart7~~><li>The download address of the Deb installation package is shown below, and it needs to be installed to use</li>{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"~~| uart9~~

|-

| ~~Tx pin~~'''https://github.com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balena-etcher-electron_1.7.9+5945ab1f_arm64.deb'''| }</ol><ol start="2" style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"~~| Corresponding~~ ><li>The download address of the Appimage version that does not need to ~~the 28 pin~~be installed is shown below: </li>{| ~~style~~class="~~text-align: left;~~wikitable"~~| Corresponding to the 16 pin~~| style="~~text-align~~width: ~~left~~800px;"~~| Corresponding to the 29 pin~~

|-

| ~~Rx Pin| style="text~~'''https://github.com/Itai-~~align: left;"| Corresponding to the 27 pin| style="text~~Nelken/BalenaEtcher-~~align: left;"| Corresponding to the 15 pin| style="text~~arm/releases/download/v1.7.9/balenaEtcher-~~align: left;"| Corresponding to the~~ 1.7 ~~pin~~.9+5945ab1f-arm64.AppImage'''

|}

<div class="figure"> [[File:pi3b-~~img269~~img275.png~~|545x134px~~]]

</div></ol></li></ol><ol start="42" style="list-style-type: decimal;"><li>~~Use the '''gpio serial''' command~~ How to ~~test~~ install and use the ~~loop function~~ deb version of ~~the serial port as shown below. If you can see the following printing, it means that the serial communication is normal~~Balenaetcher:

<li>~~Test UART3~~deb version of Balenaetcher installation commands as shown below: </li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y \'''

~~orangepi@orangepi:~$~~ '''~~sudo gpio serial~~ --fix-broken ./~~dev/ttyS3~~balena-etcher-electron_1.7.9+5945ab1f_arm64.deb'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>After the deb version of Balenaetcher is installed, it can be opened in the Application</li>

~~[sudo] password for orangepi: #Enter the password here.~~<div class="figure">

~~Out: 0~~[[File: pi3b-~~> 0~~img89.png]]

~~Out: 1~~</div></ol><ol start="3" style="list-style-type: lower-~~&gt~~alpha; 1"><li>The interface after Balenaetcher is opened is shown below: </li>

~~Out: 2: -> 2~~ ~~Out: 3: -> 3~~<div class="figure">

~~Out: 4: -> 4~~ ~~Out: 5~~[[File: pi3b-~~> 5^C~~img276.png]]

</div></ol>

</li></ol>

<li>How to use the AppImage version of balenaEtcher:

<li>First add permissions to Balenaetcher</li>

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

|-

|

orangepi@orangepi:~/Desktop$ '''chmod +x balenaEtcher-1.7.9+5945ab1f-arm64.AppImage'''

|}

</ol>

<li>~~Test UART7~~Then select the AppImage version balenaEtcher right -click the mouse, and then click Execute to open balenaEtcher</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''sudo gpio serial~~ pi3b-img277.png]]</~~dev~~ol></~~ttyS7'''~~li></ol>

~~[sudo] password for orangepi: #Enter~~ == The installation method of the ~~password here.~~Bt-Panel Linux panel ==

~~Out~~{| class="wikitable" style="background-color:#ffffdc;width: 0800px;" |-| <big>'''Bt-Panel Linux panel is a server management software that improves operation and maintenance efficiency. It supports more than 100 server management functions such as one -click LAMP/LNMP/cluster/monitoring/website/FTP/database/Java (excerpted from the [https: //www.bt.cn/new/index.html official website of the Bt-~~> 0~~Panel])'''</big>|}

~~Out~~# First of all, the size of the'''/tmp''' space is needed. After setting, you need to '''restart the Linux system of the development board''', and the command is shown below: ~~-> 1~~

~~Out~~: 2: {| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo sed -i 's/nosuid/&gtamp; 2,size=2G/' /etc/fstab'''

~~Out~~orangepi@orangepi: ~~3: -> 3~~~$ '''sudo reboot'''|}

~~Out~~<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: 4800px;" |-| orangepi@orangepi: ~$ '''df -h | grep "/tmp&gtquot; 4'''

~~Out~~tmpfs      2.0G      12K      '''2.0G'''      1% /tmp|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then enter the following command in the Linux system to start the installation of the Bt-Panel</li>{| class="wikitable" style="width: 800px;" |-~~&gt~~| 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; ~~5^C~~" |-| +----------------------------------------------------------------------

<~~ol start="3" style="list~~p>| Bt-~~style-type: lower-alpha;"><li>Test UART9<~~WebPanel FOR CentOS/Ubuntu/~~li>~~Debian</olp>

~~orangepi@orangepi:~$ '''sudo gpio serial /dev/ttyS9'''~~+----------------------------------------------------------------------

~~Out: 0:~~ +----------------------------------------------------------------------~~> 0~~

~~Out~~| The WebPanel URL will be http: 1//SERVER_IP: ~~-> 1~~8888 when installed.

~~Out: 2:~~ +----------------------------------------------------------------------~~> 2~~

~~Out: 3: -> 3~~

~~Out~~Do you want to install Bt-Panel to the /www directory now?(y/n): 4'''y'''|}</ol><ol start="5" style="list-~~&gt~~style-type: decimal; 4"><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>

~~Out~~[[File: 5pi3b-img278.png|800px]]</ol><ol start="6" style="list-style-type: decimal;"><li>At this time, enter the '''panel address''' displayed above in the browser to open the login interface of the pagoda Linux panel, and then enter the '''username''' and '''password''' 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. First, please take the intermediate user notice to read to the bottom, and then you can choose "I have agreed and read&gtquot; ~~5^C~~User Agreement ", and then click" Enter the panel " You can enter the Bt-Panel</li>

[[File:pi3b-img280.png|1200px]]</ol><~~span id~~ol start="8" style="~~pwm~~list-~~test~~style-~~method~~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 ('''https://www.bt.cn''') to register one.</~~span~~li>~~=== PWM test method ===~~

~~# From~~ [[File:pi3b-img281.png|1200px]]</ol><ol start="9" style="list-style-type: decimal;"><li>The final display interface is shown in the ~~table~~ figure below. You can intuitively see some status information of the development board Linux system, such as load state, CPU usage, ~~the pwm11 available for Orange Pi 3B~~memory usage and storage space usage</li>

[[File:pi3b-~~img270~~img282.png|~~575x160px~~1200px]]</ol><ol start="10" style="list-style-type: decimal;"><li>More functions of the Bt-Panel can refer to the following information to explore by yourself</li>

{| class="wikitable" style="width:800px;" |-| Manual: [http://docs.bt.cn '''~~In the Linux system, the pwm in 40pin is closed by default, and it needs to be opened manually to use~~http://docs.bt.cn''']

Forum address: [https://www.bt.cn/bbs '''~~Add the configuration of the red font part below to the~~ https:/~~boot~~/~~orangepiEnv~~www.~~txt, and then restart the Linux system to open the pwm11~~bt.cn/bbs''']

~~orangepi@orangepi~~GitHub Link:~$ '''~~sudo vim~~ https:/~~boot~~/~~orangepiEnv~~github.~~txt~~com/aaPanel/BaoTa'''|}</ol>

~~'''overlays~~=~~pwm11-m1'''~~= Set the Chinese environment and install Chinese input method ==

~~<ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~After opening a pwm, a pwmchipX (X is a specific number) will be available in~~'''~~/sys/class/pwm/~~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.'''</~~li></ol~~big>|}

~~orangepi@orangepi:~$ '''ls~~ </~~sys/class/pwm/'''~~span>=== Debian system installation method ===

~~pwmchip0 pwmchip1~~<ol style="list-style-type: decimal;"><li>First set the default '''locale''' as Chinese<ol style="list-style-type: lower-alpha;"><li>Enter the command below to start configured '''locale'''</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''|}</ol><ol start="32" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Which pwmchip corresponds to pwm11 above? Let~~Then select '~~s first check out the output of~~ ''~~'ls /sys/class/pwm/~~ zh_CN.UTF-8 UTF-l8''' ~~command~~in the pop-up interface (to move up and down through the upper and lower direction buttons on the keyboard, ~~as shown below: </li><li>The base address of~~ select it through the ~~pwm11 register is Fe6F0030. Then see~~ space key, and finally move the ~~output of~~ cursor to '''~~ls /sys/class/pwm/ -l~~<OK>''' ~~command, you can see that~~ through the ~~fe6f0030.pwm is connected to the pwmchip1~~TAB key, so then press the ~~PWM11 corresponding pwmchip is pwmchip1~~ENTER key )</li~~></ol~~>

[[File:pi3b-img283.png|1200px]]<~~div class~~/ol><ol start="3" style="~~figure~~list-style-type: lower-alpha;"><li>Then set the default '''locale''' as '''zh_CN.UTF-8'''</li>

[[File:pi3b-~~img271~~img284.png|~~576x46px~~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;" |-|~~RCUS~~orangepi@orangepi:~$~~_~VYM{4ZS]_L}DNZQR]]~~'''sudo dpkg-reconfigure locales'''

~~</div><ol start="5" style="list-style-type: decimal;"><li>Then use the following command to allow pwm11 to output~~ Generating locales (this might take a ~~50Hz square wave (please switch to the root user first, and then execute the following command~~while)~~</li></ol>~~...

~~root@orangepi~~:~~~# '''echo 0 > /sys/class/pwm/pwmchip1/export'''~~en_US.UTF-8... done

~~root@orangepi~~:~~~# '''echo 20000000 > /sys/class/pwm/pwmchip1/pwm0/period'''~~zh_CN.UTF-8... done

~~root@orangepi~~Generation complete.|}</ol></li></ol><ol start="2" style="list-style-type:~# decimal;"><li>Then open '''~~echo 1000000 > /sys/class/pwm/pwmchip1/pwm0/duty_cycle~~Input Method'''</li>

~~root@orangepi~~[[File:~# pi3b-img285.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then select '''~~echo 1 > /sys/class/pwm/pwmchip1/pwm0/enable~~OK'''</li>

[[File:pi3b-~~img272~~img286.png~~|575x346px~~]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select '''Yes'''</li>

[[File:pi3b-img287.png]]</ol><~~span id~~ol start="~~how-to-install-and~~5" style="list-~~use~~style-~~wiringop-python~~type: decimal;"><li>Then select '''fcitx'''</~~span~~li>~~== How to install and use Wiringop-Python ==~~

[[File:pi3b-img288.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then select '''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.OK'''</li>

[[File:pi3b-img289.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>'''~~Please note that all~~ Then restart the ~~following command below is operated under~~ Linux system to make the ~~root user.~~configuration effective'''</li><li>Then open '''Fcitx configuration'''</li>

[[File:pi3b-img290.png]]</ol><~~span id~~ol start="~~wiringop~~9" style="list-~~python~~style-~~installation-method~~type: decimal;"><li>Then click the + of the position shown in the figure below</~~span~~li>~~=== Wiringop-Python installation method ===~~

~~# First install the dependency package~~[[File:pi3b-img291.png]]</ol><ol start="10" style="list-style-type: decimal;"><li>Then search '''Google Pinyin''' and click '''OK'''</li>

~~root@orangepi:~# '''sudo apt-get update'''~~<div class="figure">

~~root@orangepi~~[[File:~~~# '''sudo apt~~pi3b-~~get -y install git swig python3-dev python3-setuptools'''~~img292.png]]

</div></ol><ol start="211" style="list-style-type: decimal;"><li>Then ~~use the following command~~ put '''Google Pinyin''' to ~~download~~ the ~~source code of wiringOP-Python~~front</li~~></ol~~>

~~'''Note that the following git clone~~[[File:pi3b--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 problemsimg293.~~'''~~png]]

[[File:pi3b-img294.png]]</ol><ol start="12" style="list-style-type: decimal;"><li>Then open the '''~~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~~Geany'''editor to test the Chinese input method</li>

~~root@orangepi~~[[File:~~~# '''git clone~~ pi3b-~~-recursive https://github~~img295.~~com~~png]]</~~orangepi~~ol><ol start="13" style="list-style-~~xunlong~~type: decimal;"><li>The Chinese input method test is shown below</~~wiringOP-Python -b next'''~~li>

~~root~~[[File:pi3b-img296.png]]</ol><ol start="14" style="list-style-type: decimal;"><li>You can switch the Chinese and English input method through the '''Ctrl+Space''' shortcut</li><li>If the entire system is required as Chinese, the variables in '''/etc/default/locale''' can be set to '''zh_CN.UTF-8'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~# $ '''~~cd wiringOP-Python~~sudo vim /etc/default/locale'''

~~root@orangepi:~/wiringOP-Python~~# ~~'''git submodule~~ File generated by update -~~-init --remote'''~~locale

LC_MESSAGES='''<~~ol start="3"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>Then use the following command to compile wiringOP~~zh_CN.UTF-~~Python and install it into the Linux system of the development board</li>~~8</olspan>'''

~~root@orangepi:~#~~ LANG='''~~cd wiringOP~~zh_CN.UTF-~~Python~~8'''

~~root@orangepi~~LANGUAGE='''zh_CN.UTF-8</~~wiringOP-Python#~~ span>'''~~python3 generate~~|}</ol><ol start="16" style="list-style-~~bindings.py &gt~~type: decimal; ~~bindings.i~~"><li>Then '''restart the system'''to see the system displayed as Chinese</li>

~~root@orangepi~~[[File:~pi3b-img297.png]]</~~wiringOP~~ol>

~~<ol start~~=~~"4" style~~=~~"list-style-type: decimal;"><li>Then enter the following command~~= The installation method of Ubuntu 20. ~~If there is a help information output, it means that Wiringop-Python is successfully installed. Press the '''q''' key to exit the interface of the help information</li></ol>~~04 system ===

~~root@orangepi:~/wiringOP-Python~~# First open '''~~python3 -c "import wiringpi; help(wiringpi)"~~Language Support'''

~~Help on module wiringpi~~::[[File:pi3b-img298.png]]

~~NAME~~<ol start="2" style="list-style-type: decimal;"><li>Then find '''Chinese (China)''' option</li>

~~wiringpi~~[[File:pi3b-img299.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then use the left mouse button to select '''Chinese (China)''' and hold it down, and then drag it up to the beginning. The display is shown below: </li>

~~DESCRIPTION~~[[File:pi3b-img300.png]]

{| class="wikitable" style="background-color:# ~~This file was automatically generated by SWIG (http~~ffffdc;width:800px;" |-| <big>'''Note that this step is not easy to drag, please try more patiently.'''</big>|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system</~~www.swig.org).~~li>

~~# Version 4~~[[File:pi3b-img301.~~0.2~~png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then set the '''Keyboard input method system''' to '''fcitx'''</li>

[[File:pi3b-img302.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>'''Then restart the Linux system to make the configuration effective'''</li><li>After re -entering the system, please do '''not ask me again''' at the interface below, and then determine whether the standard folder should be updated as Chinese based on your preference.</li>

~~# Do not make changes to this file unless you know what you are doing~~[[File:pi3b-img303.png]]</ol><ol start="8" style="list-style-~~modify~~type: decimal;"><li>Then you can see that the desktop is displayed as Chinese</li>

# [[File:pi3b-img304.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then we can open the '''Geany''' to test Chinese input method , and the way to open is shown in the ~~SWIG interface file instead.~~figure below</li>

[[File:pi3b-img305.png]]</ol><ol start="510" style="list-style-type: decimal;"><li>~~Test whether~~ After opening '''Geany''', the ~~Wiringop-Python~~ default is ~~installed successfully under~~ an English input method. We can switch into Chinese input method through the ~~Python command line is shown below: <ol style="list-style-type: lower-alpha;"><li>First use the Python3 command to~~ '''Ctrl+Space''' shortcut keys, and then we can enter ~~the command line mode of Python3~~Chinese</li~~></ol></li></ol~~>

~~root@orangepi~~[[File:~~~# '''python3'''~~pi3b-img306.png]]</ol>

~~<ol start~~=~~"2" style~~=~~"list-style-type: lower-alpha;"><li>Then import the Python module~~ = The installation method of ~~WiringPi</li></ol>~~ubuntu 22.04 system ===

~~>>>~~ # First open '''~~import wiringpi;~~Language Support'''

~~<ol start="3" style="list-style-type~~: ~~lower-alpha;"><li>Enter the following command to view the help information of Wiringop~~:[[File:pi3b-~~Python, and press the '''q''' key to exit the interface of the help information</li></ol>~~img298.png]]

~~>>&gt~~<ol start="2" style="list-style-type: decimal; "><li>Then find '''~~help~~Chinese (~~wiringpi~~China)'''option</li>

~~Help on module wiringpi~~[[File:pi3b-img307.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then use the left mouse button to select '''Chinese (China)''' and hold it down, and then drag it up to the beginning. The display after dragging is shown in the figure below: </li>

~~NAME~~[[File:pi3b-img308.png]]

~~wiringpi~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that this step is not easy to drag, please try more patiently.'''</big>|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system</li>

~~DESCRIPTION~~[[File:pi3b-img309.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>'''Then restart the Linux system to make the configuration effective'''</li><li>After re -entering the system, please '''do not ask me again''' at the interface below, and then determine whether the standard folder should be updated as Chinese based on your preference</li>

~~# This file was automatically generated by SWIG (http~~[[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</~~www.swig.org).~~li>

~~# Version 4~~[[File:pi3b-img304.~~0.2~~png]]</ol><ol start="8" style="list-style-type: decimal;"><li>Then open the Fcitx5 configuration program</li>

#[[File:pi3b-img310.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then choose to use Pinyin input method</li>

~~# Do not make changes to this file unless you know what you are doing--modify~~<div class="figure">

~~# the SWIG interface file instead~~[[File:pi3b-img311.png]]

~~CLASSES~~</div></ol><ol start="10" style="list-style-type: decimal;"><li>The interface after the selection is shown below, then click OK</li>

~~builtins~~[[File:pi3b-img312.~~object~~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>

~~GPIO~~[[File:pi3b-img305.png]]</ol><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>

~~I2C~~[[File:pi3b-img313.png]]</ol>

~~Serial~~== How to remotely log in to the Linux system desktop method ==

~~nes~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Ubuntu Gnome Wayland image does not support Nomachine and VNCs introduced here to remotely log in to the desktop.'''</big>|}

~~class GPIO(builtins.object)~~=== Use nomachine remote login ===

{| ~~GPIO(pinmode~~class=0)"wikitable" style="background-color:#ffffdc;width:800px;" |-| <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: '''

'''https://knowledgebase.nomachine.com/DT10R00166'''</big>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Nomachine supports Windows, Mac, Linux, iOS, and Android platforms, so we can remotely log in to control Orange PI development boards through Nomachine on multiple devices. The following demonstrates the Linux system desktop of the Orange PI development board through Nomachine in Windows. For installation methods for other platforms, please refer to the official documentation of Nomachine.'''</big>|}~~&gt~~{| class="wikitable" style="background-color:#ffffdc;~~>&gt~~width:800px;" |-| <big>'''Before operation, please ensure that the Windwos computer and the development board are in the same local area network, and can log in to the Ubuntu or Debian system that can log in to the development board normally.'''</big>|}

<ol style="list-style-type: decimal;"><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="~~pin~~list-~~gpio~~style-~~port~~type: lower-~~test~~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-1color:#ffffdc;width:800px;"|-| <big>'''Note that this download link may change, please recognize the DEB package of the ARMV8/ARM64 version.'''</~~span~~big>|}{| class="wikitable" style="width:800px;" |-| [https://www.nomachine.com/download/download&id= ~~40pin GPIO port test~~ 112&s=ARM '''https://downloads.nomachine.com/download/?id=118&distro=ARM''']|}

~~'''Wiringop~~[[File:pi3b-~~Python is the same as Wiringop~~img314. ~~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~~png]]</ol><ol start="2" style="list-style-type: lower-~~Python~~alpha;"><li>In addition, you can ~~only check~~ also download the ~~board WPI number and physical physical physics through the GPIO command~~ installation package to '''NoMachine''' in ~~Wiringop. The corresponding relationship of~~ the ~~pin.~~'''official tools'''.</li>

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

~~[[File:pi3b~~First enter the '''remote login software-~~img258.png|575x355px|66AC(IBG%N8L@Y7(1BZPS`N]]~~Nomachine''' folder

~~</div># Below the No~~[[File:pi3b-img316. ~~7 pin — corresponding to GPIO4_a4 -corresponding WPI serial number 2 -to demonstrate how to set the height of the GPIO port~~png]]

~~[[File:pi3b-img259.png|576x120px]]~~Then download the ARM64 version of the DEB installation package

[[File:pi3b-img317.png]]

</ol>

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

<li>~~The steps~~ Then download the nomachine software Windows version of the ~~command test are~~ installation package, the download address is shown below ~~directly:~~ </pli>~~<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~First set the GPIO port to the output mode. The first parameter of the~~ '''~~pinMode~~Note that this download link may change.''' ~~function is the serial number of the wpi corresponding to the pin, and the second parameter is the GPIO mode~~</libig><|}{| class="wikitable" style="width:800px;" |-| '''https://~~ol>~~<downloads.nomachine.com/~~li><~~download/~~ol>~~?id=9'''|}

~~root@orangepi~~[[File:~pi3b-img318.png]]</~~wiringOP~~ol><ol start="3" style="list-~~Python#~~ style-type: decimal;"><li>Then install nomachine in Windows. '''~~python3 -c "import wiringpi; \~~Please restart the computer after installation'''</li><li>Then open '''NoMachine'''in Window</li>

~~'''from wiringpi import GPIO~~[[File:pi3b-img319.png]]</ol><ol start="5" style="list-style-type: decimal; ~~wiringpi~~"><li>After Nomachine starts, it will automatically scan other devices installed in the local area network.~~wiringPiSetup() ; \'''~~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>

[[File:pi3b-img320.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then click '''~~wiringpi.pinMode(2, GPIO.OUTPUT) ; "~~OK'''</li>

[[File:pi3b-img321.png]]</ol><ol start="27" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~set the GPIO port output low level. After setting, you can use~~ enter the ~~voltage~~ username and password of the ~~voltage of~~ Linux system in the ~~universal meter to measure~~ corresponding position in the ~~pins. If it is 0V~~figure below, ~~it means that the low -power flat is successful~~and then click '''OK''' to start logging in</li~~></ol~~>

~~root@orangepi:~/wiringOP-Python# '''python3 -c "import wiringpi; \'''~~<div class="figure">

~~'''from wiringpi import GPIO; wiringpi~~[[File:pi3b-img322.~~wiringPiSetup() ;\'''~~png]]

~~'''wiringpi.digitalWrite(2, GPIO.LOW)"'''~~</div></ol><ol start="38" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~set~~ click OK in the ~~GPIO port output high level. After setting~~next interface</li><li>Finally, you can ~~use~~ see the ~~value~~ desktop of the ~~voltage of the pins with a multimeter. If it is 3.3V, it means that the high~~ development board Linux system[[File:pi3b-~~power flat is successful~~img323.png]]</li></ol>

~~root@orangepi:~/wiringOP~~

~~'''from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\'''~~=== Use VNC remote login ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~wiringpi.digitalWrite(2~~Before operation, please ensure that the Windwos computer and the development board are in the same local area network, ~~GPIO~~and you can log in to the Ubuntu or Debian system of the development board normally.~~HIGH)"~~'''

'''<~~ol start="3"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>The steps of testing in the command line of Python3 are shown below: <ol style="list-style-type: lower-alpha;"><li>First~~ Ubuntu 20.04 tests many problems with VNC, please do not use ~~the Python3 command to enter the command line mode of Python3~~this method.</lispan>'''</olbig>~~</li></ol>~~|}

~~root@orangepi:~~~# First run the '''~~python3~~set_vnc.sh''' script settings, and '''remember to add Sudo permissions'''

~~<ol start~~::{| class="2wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Then import the Python module of WiringPi</li></ol>~~|-| orangepi@orangepi:~$ '''sudo set_vnc.sh'''

~~>>> '''import wiringpi'''~~You will require a password to access your desktops.

~~>>> '''from wiringpi import GPIO'''~~

Password:        '''<~~ol start="3"~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">#Set the VNC password here, 8 -bit characters<li/span>~~Then set the GPIO port as the output mode. The first parameter of the '~~''~~pinMode~~'~~'' function is the serial number of the wpi corresponding to the pin, and the second parameter is the GPIO mode.</li></ol>~~

Verify: &gtnbsp;&gtnbsp;&gtnbsp;    '''~~wiringpi.wiringPiSetup()~~#Set the VNC password here, 8 -bit characters'''

0Would you like to enter a view-only password (y/n)? '''n'''

~~>>> '''wiringpi~~xauth: file /root/.~~pinMode(2, GPIO.OUTPUT)'''~~Xauthority does not exist

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

~~<li>Then set the GPIO port output low level. After setting, you can use the value of the voltage of the pins with a multimeter. If it is 0V, it means that the low -power flat is set.</li></ol>~~

~~>>> '''wiringpi.digitalWrite(2, GPIO.LOW)'~~New 'X'desktop is orangepi3b:1

~~<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.3V, it means that the high -power flat is successful</li></ol>

~~>>> '''wiringpi~~Creating default startup script /root/.~~digitalWrite(2, GPIO.HIGH)'''~~vnc/xstartup

~~<ol start="4" style="list-style-type: decimal;"><li>Wiringop-Python Sets GPIO high and low levels~~ Starting applications specified in ~~the Python code. For reference to the '''blink~~/root/.~~py''' test program in Examples, the voltage of the '''blink.py''' test program will set up the voltage of all GPIO ports in the development board 40 PIN</li><~~vnc/~~ol>~~xstartup

Log file is /root~~@orangepi~~/.vnc/orangepi3b:~~~/wiringOP-Python# '''cd examples'''~~1.log

~~root@orangepi:~/wiringOP-Python/examples# '''ls blink.py'''~~

~~'''blink.py'''~~Killing Xtightvnc process ID 3047

~~root@orangepi:~/wiringOP-Python/examples'''# python3 blink.py'''~~

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

~~# From the schematic diagram of the 40pin interface, the SPI available for Orange Pi 3B is spi3~~

~~[[File:pi3b-img264~~Starting applications specified in /root/.~~png|577x193px]]~~vnc/xstartup

~~'''In the Linux system, the spi3 in 40pin~~ Log file is ~~closed by default, and it needs to be opened manually to use~~/root/.~~'''~~vnc/orangepi3b:1.log|}

~~'''Add the configuration~~ <ol start="2" style="list-style-type: decimal;"><li>The steps of using MobaxTerm software to connect the ~~red font part~~ development board Linux system desktop are shown below ~~to the~~ : </~~boot/orangepiEnv.txt~~p><ol style="list-style-type: lower-alpha;"><li>First click Session, then select VNC, then fill in the IP address and ~~then restart~~ port of the ~~Linux system~~ development board, and finally click OK to ~~open the spi4.'''~~confirm</li>

~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''~~<div class="figure">

~~'''overlays=spi3~~[[File:pi3b-~~m0-cs0-spidev'''~~img324.png]]

</div></ol><ol start="2" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~First check whether there~~ Then enter the password of the previously set VNC</li> [[File:pi3b-img325.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The interface after the login is ~~a '''spidev3.0''' device node~~ shown as shown in the figure below, and then the desktop of the Linux system~~. If it exists, it means that the SPI3 has been set and~~ can be ~~used directly~~remotely operated[[File:pi3b-img326.png]]</li></ol></li></ol>

~~orangepi@orangepi:~$ '''ls /dev/spidev3.0'''~~== Some programming language tests supported by Linux system ==

</~~dev/spidev3.0~~span>=== Debian Bullseye system ===

<ol ~~start="3"~~ style="list-style-type: decimal;"><li>~~You~~ Debian Bullseye is equipped with a gcc compilation tool chain by default, which can ~~then use~~ directly compile the ~~spi back function under the '''spidev_test.py'''~~ C language program in ~~Examples. The '''spidev_test.py''' program needs to specify~~ the ~~following two parameters:~~ Linux system of the development board

<li>~~'''--channel''': Specify~~ The version of the ~~channel number of SPI~~gcc is shown below</li>~~<li>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc --~~port~~version'''~~: Specify the port number of SPI</li></ol></li>~~<li>Do not pick up the two pins of the SPI3 MOSI and MISO in short, and run the output result of the spidev_test.py as shown below. You can see that the data of TX and RX are inconsistent</li></ol>

~~root@orangepi:~/wiringOP~~gcc (Debian 10.2.1-~~Python# '''cd examples'''~~6) 10.2.1 20210110

~~'''--channel 3 --port 0'''~~This is free software; see the source for copying conditions. There is NO

~~spi mode~~warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</ol><ol start="2" style="list-style-type: ~~0x0~~lower-alpha;"><li>Write C language of '''Hello_world.c''' program</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.c'''

~~max speed: 500000 Hz (500 KHz)~~

~~Opening device~~ #include <stdio.h></~~dev/spidev3.0~~p>

~~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 |......@.......…|~~int main(void)

~~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 start="5" style="list-style-type~~: ~~decimal~~printf("Hello World!\n"">~~<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></ol>~~;

~~root@orangepi:~/wiringOP-Python# '''cd examples'''~~

~~root@orangepi~~:~~~/wiringOP-Python/examples# '''python3 spidev_test.py \'''~~return 0;

}|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then compile and run '''hello_world.c'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc -~~channel 3 --port 0~~o hello_world hello_world.c'''

~~spi mode~~orangepi@orangepi: ~~0x0~~~$ '''./hello_world'''

~~max speed~~Hello World!|}</ol></li></ol><ol start="2" style="list-style-type: ~~500000 Hz (500 KHz)~~decimal;"><li>Debian BullSeye Default with Python3<ol style="list-style-type: lower-alpha;"><li>The specific version of Python is shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3'''

~~Opening device /dev/spidev3~~'''Python 3.09.2''' (default, Feb 28 2021, 17:03:44)

~~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 |~~[GCC 10.2.~~....@.......…|~~1 20210110] on linux

~~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 |~~Type "help", "copyright", "credits" or "license" for more information.~~.....@.......…|~~

>>>|}</ol><~~span id~~ol start="2" style="~~pin~~list-~~i2c~~style-~~test~~type: lower-1alpha;"><li>'''hello_world.py''' program in Python language</~~span~~li>{| class="wikitable" style=~~= 40pin I2C test ===~~"width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.py'''

print('Hello World!')|}</ol><ol start="53" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~As can be seen from the table~~ The results of running '''hello_world.py''' are shown below~~, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total of three groups of I2C bus~~</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:~~pi3b~~decimal;"><li>Debian Bullseye's compilation tool and operating environment that is not installed in Java by default<ol style="list-style-~~img266~~type: lower-alpha;"><li>You can use the following command to install OpenJDK.~~png~~The latest version in Debian Bullseye is openjdk-17</li>{|~~576x160px]]~~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:800px;" |-| orangepi@orangepi:~$ '''java --version'''|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Edit the '''hello_world.java''' of the Jave version</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''

~~'''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'''~~public class hello_world

~~'''In the Linux system, the I2C 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 I2C2, i2C3, and I2C4 at the same time. If you only need to open one, then fill in one.''':public static void main(String[] args)

~~orangepi@orangepi~~:~~~$ '''sudo vim /boot/orangepiEnv.txt'''~~{

~~'''overlays=i2c2-m1 i2c3-m0 i2c4-m0'''~~::System.out.println("Hello World!");

~~<ol start="6" style="list-style-type~~: ~~decimal;"><li>After starting the Linux system, first confirm the I2C device node under/dev.</li></ol>~~}

}|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then compile and run '''hello_world.java'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~# $ '''ls /dev/i2c-*javac hello_world.java'''

~~/dev/i2c-0~~ orangepi@orangepi:~$ '''~~/dev/i2c-2~~java hello_world''' ~~'''/dev/i2c-3''' '''/dev/i2c-4''' /dev/i2c-6~~

~~<ol start="7" 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></ol>~~ ~~{| class="wikitable"~~|-|~~| style="text-align: left;"| i2c2-m1| style="text-align: left;"| i2c3-m0| style="text-align: left;"| i2c4-m0~~|-~~| Sda Pin| style="text-align: left;"| Corresponding to No. 3 pin| style="text-align: left;"| Corresponding to No. 27 pin| style="text-align: left;"| Corresponding to No. 19 pin~~|-~~| Sck Pin| style="text-align: left;"| Corresponding to No. 5 pin| style="text-align: left;"| Corresponding to No. 28 pin| style="text-align: left;"| Corresponding to No. 23 pin~~|-~~| Vcc Pin| style="text-align: left;"| Corresponding to No. 1 pin| style="text-align: left;"| Corresponding to No. 1 pin| style="text-align: left;"| Corresponding to No. 1 pin~~|-~~| Gnd Pin| style="text-align: left;"| Corresponding to No. 6 pin| style="text-align: left;"| Corresponding to No. 6 pin| style="text-align: left;"| Corresponding to No. 6 pin~~Hello World!

|}

</ol>

</li></ol>

~~[[File:pi3b-img273.png|180x153px]]~~=== Ubuntu Focal system ===

<ol ~~start="8"~~ style="list-style-type: decimal;"><li>~~Then use~~ Ubuntu Focal has the ~~'''i2cdetect -y''' command If~~ GCC compilation tool chain by default, which can compile the C language program directly in the ~~address~~ Linux system of the ~~connected I2C device can be detected, it means that the I2C can be used normally~~development board.<ol style="list-style-type: lower-alpha;"><li>The version of the gcc is shown below</olli>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc --version'''

~~orangepi@orangepi:~~gcc (Ubuntu 9.4.0-1ubuntu1~~~$ sudo i2cdetect -y 2 #i2c2 command~~20.04.1) 9.4.0

~~orangepi@orangepi:~$ sudo i2cdetect -y 4 #i2c4 command~~This is free software; see the source for copying conditions. There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}<~~div~~ /ol><ol start="2" style="list-style-type: lower-alpha;"><li>'''hello_world.c''' program to write C language</li>{| class="~~figure~~wikitable" style="width:800px;">|-| orangepi@orangepi:~$ '''vim hello_world.c'''

~~[[File:pi3b-img274~~#include <stdio.~~png|464x174px|V@(61L~0})Q`8VLBCAYEP[2]]~~h>

~~</div>~~

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

~~<li>You can then run the time of the ds '''ds1307.py''' test program in '''examples''' to read the RTC time</li></ol>~~

~~root@orangepi:~/wiringOP-Python# '''cd examples'''~~int main(void)

~~root@orangepi:~/wiringOP-Python/examples# '''python3 ds1307.py --device \'''~~{

~~'''~~:printf("~~/dev/i2c-4~~Hello World!\n"~~'''~~);

~~Thu 2023-01-05 14:57:55~~

~~Thu 2023-01-05 14~~:~~57:56~~return 0;

~~Thu 2023~~}|}</ol><ol start="3" style="list-01style-~~05 14~~type:57lower-alpha;"><li>Then compile and run '''hello_world.c'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:57~$ '''gcc -o hello_world hello_world.c'''

^Corangepi@orangepi:~$ '''./hello_world'''

~~exit~~Hello World!|}</ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>Ubuntu Focal defaults to install Python3<ol style="list-style-type: lower-alpha;"><li>Python3 specific version is shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3'''

~~=== 40pin's UART test ===~~8.10 (default, Nov 14 2022, 12:59:47)

~~# As can be seen from the table below, the UART available for Orange Pi 3B is UART3, UART7 and UART9~~[GCC 9. ~~There are three sets of UART bus~~4.0] on linux

~~[[File:pi3b-img268~~Type "help", "copyright", "credits" or "license" for more information.~~png|575x160px]]~~

>>>|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>'''~~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~~hello_world.py''' program in Python language</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.py'''

print('Hello World!'~~'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 one'''~~ ~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''~~ ~~'''overlays=uart3-m0 uart7-m2 uart9-m2'''~~ol><ol start="23" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~After entering the Linux system, first confirm whether there is a device node corresponding to UART under/dev~~The results of running '''hello_world.py''' are shown below</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~# $ '''~~ls /dev/ttyS*'''~~ ~~/dev/ttyS1 '''/dev'''/'''ttyS3 /dev/ttyS7 /dev/ttyS9~~python3 hello_world.py'''

Hello World!

|}

</ol>

</li></ol>

<li>~~Then start testing the UART interface,~~ Ubuntu Focal's compilation tool and ~~first use~~ operating environment without the ~~RX and TX~~ installation of ~~the UART interface to be tested by DuPont~~Java default<ol style="list-style-type: lower-alpha;"><li>You can use the following command to install '''openjdk-17'''</olli> {| class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''| }</ol><ol start="2" style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"~~| uart3~~><li>After installation, you can check the version of Java</li>{| ~~style~~class="~~text-align: left;~~wikitable"~~| uart7~~| style="~~text-align~~width: ~~left~~800px;"~~| uart9~~

|-

| ~~Tx Pin| style="text-align: left;"| Corresponding to the 28 pin| style="text-align: left;"| Corresponding to the 16 pin| style="text-align: left;"| Corresponding to the 29 pin~~|-~~| Rx Pin| style="text-align~~orangepi@orangepi: ~~left;"| Corresponding to the 27 pin| style="text~~~$ '''java -~~align: left;"| Corresponding to the 15 pin| style="text~~-~~align: left;"| Corresponding to the 7 pin~~|}version'''

~~<ol start="4" style="list-style-type: decimal;"><li>Use the '''serialTest~~openjdk 17.~~py''' program in Examples to test the loop function of the serial port~~0. ~~If you can see the printing below, it means that the serial communication is normal<ol style="list-style~~2 2022-~~type: lower~~01-~~alpha;"><li>Test UART3</li></ol></li></ol>~~18

~~root@orangepi:~/wiringOP-Python/examples# '''python3 serialTest~~OpenJDK Runtime Environment (build 17.0.py 2+8-Ubuntu-~~device \'''~~120.04)

OpenJDK 64-Bit Server VM (build 17.0.2+8-Ubuntu-120.04, mixed mode, sharing)|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Edit the '''hello_world.java'''~~"~~of Jave version</~~dev/ttyS3&quot~~li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''

~~Out: 0: -> 0~~public class hello_world

~~Out: 1: -> 1~~{

~~Out~~: ~~2: -> 2~~public static void main(String[] args)

~~Out~~: ~~3: -> 3~~{

~~Out~~: 4:^CSystem.out.println("Hello World!");

~~exit~~:}

}|}</ol><ol start="24" style="list-style-type: lower-alpha;"><li>~~Test UART7~~Then compile and run '''hello_world.java'''</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''javac hello_world.java'''

~~root~~orangepi@orangepi:~~~/wiringOP-Python/examples#~~ $ '''~~python3 serialTest.py --device \~~java hello_world'''

~~'''"~~Hello World!|}</~~dev~~ol></~~ttyS7"'''~~li></ol>

~~Out: 0: -> 0~~=== Ubuntu jammy system ===

~~Out~~<ol style="list-style-type: 1decimal;"><li>Ubuntu Jammy is installed with the GCC compilation tool chain by default, which can directly compile the C language program in the Linux system of the development board<ol style="list-style-type: lower-~~&gt~~alpha; 1"><li>The version of the gcc is shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc --version'''

~~Out:~~ gcc (Ubuntu 11.2: .0-~~>~~ 19ubuntu1) '''11.2.0'''

~~Out: 4:^C~~This is free software; see the source for copying conditions. There is NO

~~exit~~warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Write the '''hello_world.c''' program of c language</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.c'''

<~~ol start="3" style="list-style-type: lower-alpha~~p>#include <stdio.h>">~~<li>Test UART9</li>~~</olp>

~~root@orangepi:~/wiringOP-Python/examples# '''python3 serialTest.py --device \'''~~

~~'''"/dev/ttyS9"'''~~int main(void)

~~Out: 0: -> 0~~{

~~Out~~: ~~1: -~~printf("Hello World!\n&gtquot;); 1

~~Out: 2: -> 2~~

~~Out~~: ~~3: -&gt~~return 0; 3

~~Out~~}|}</ol><ol start="3" style="list-style-type: 4lower-alpha;"><li>Then compile and run '''hello_world.c'''</li>{| class="wikitable" style="width:^C800px;" |-| orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''

~~exit~~orangepi@orangepi:~$ '''./hello_world'''

Hello World!|}<~~span id="hardware-watch-the-door-dog-test"~~/ol></li></~~span~~ol>

<ol start="2" style= ~~Hardware watch the door dog test~~ "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:~$ '''python3'''

~~The WatchDog_test program is pre -installed in the Linux system released by Orange PI~~Python '''3.10.4''' (main, Apr 2 2022, ~~which can be tested directly~~09:04:19) [GCC 11.2.0] on linux

~~The method of running the WatchDog_test program is shown below:~~ Type "help", "copyright", "credits" or "license" for more information.

>>>|}</ol ><ol start="2" style="list-style-type: lower-alpha;"><li>~~The second parameter 10 indicates the counting time of the door~~Edit '''hello_world. ~~If there is no dog feeding~~ py''' program in ~~this time, the system will restart.~~Python language</li>~~<li>We can feed the dog by pressing any keys on the keyboard (except ESC)~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world. ~~After the dog is fed, the program will print a line of Keep Alive to indicate that the dog is successful</li></ol>~~py'''

print('Hello World!')|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The results of running '''hello_world.py''' are shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~sudo watchdog_test 10~~python3 hello_world.py'''

~~open success~~Hello World!|}</ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>Ubuntu jammy defaults to compile tools and operating environments that are not installed in Java<ol style="list-style-type: lower-alpha;"><li>You can use the following command to install openjdk-18</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-18-jdk'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>After installation, you can check the version of Java</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''java --version'''

~~options is 33152,identity is sunxi~~openjdk 18-~~wdt~~ea 2022-03-22

~~put_usr return,if 0,success:0~~OpenJDK Runtime Environment (build 18-ea+36-Ubuntu-1)

~~The old reset time is~~OpenJDK 64-Bit Server VM (build 18-ea+36-Ubuntu-1, mixed mode, sharing)|}</ol><ol start="3" style="list-style-type: 16lower-alpha;"><li>Edit the '''hello_world.java''' of the Jave version</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''

~~return ENOTTY,if -1,success:0~~public class hello_world

~~return ENOTTY,if -1,success:0~~{

~~put_user return,if 0,success~~:0public static void main(String[] args)

~~put_usr return,if 0,success~~:0{

~~keep alive~~::System.out.println("Hello World!");

~~keep alive~~:}

~~keep alive~~}|}<~~span id~~/ol><ol start="4" style="~~check-the-serial-number~~list-ofstyle-~~the~~type: lower-~~rk3566-chip~~alpha;"><li>Then compile and run '''hello_world.java'''</~~span~~li>{| class="wikitable" style= ~~Check the serial number of the RK3566 chip ==~~"width:800px;" |-| orangepi@orangepi:~$ '''javac hello_world.java'''

~~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.~~orangepi@orangepi:~$ '''java hello_world'''

~~orangepi@orangepi:~$ '''cat_serial.sh'''~~Hello World!|}~~Serial : '''8fa18eaf489041f0'''~~ ~~== 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>

~~https://github.com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balena-etcher-electron_1.7.9+5945ab1f_arm64.deb~~== QT installation method ==

~~<ol start="2" style="list-style-type: lower-alpha;"><li>The download address of~~ # Use the ~~Appimage version that does not need~~ following script to ~~be installed is shown below: </li></ol>~~install QT5 and QT Creator

~~https~~:~~//github.com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balenaEtcher-1.7.9+5945ab1f-arm64.AppImage~~ ~~<div~~ :{| class="~~figure~~wikitable" style="width:800px;">|-| ~~[[File~~orangepi@orangepi:~~pi3b-img275~~~$ '''install_qt.~~png|527x211px~~sh'''|~~IMG_256]]~~}

~~</div>~~

<li>~~How to install and use the deb~~ The QT version ~~of Balenaetcher:~~ number will be automatically printed after installation

<li>~~deb~~ Ubuntu20.04 comes with QT version ~~of Balenaetcher installation commands as shown below:~~ '''5.12.8'''</li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_qt.sh'''

~~orangepi@orangepi:~$ '''sudo apt install -y \'''~~......

~~'''--fix-broken~~ QMake version 3.~~/balena-etcher-electron_1.7.9+5945ab1f_arm64.deb'''~~1

Using Qt version '''5.12.8''' in /usr/lib/aarch64-linux-gnu

|}

</ol>

<li>~~After the deb~~ Ubuntu22.04 comes with QT version ~~of Balenaetcher is installed, it can be opened in the Application~~'''5.15.3'''</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_qt.sh'''

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

~~[[File:pi3b-img89~~QMake version 3.~~png|507x249px|IMG_256]]~~1

Using Qt version '''5.15.3''' in /usr/lib/aarch64-linux-gnu|}</~~div~~ol>

<li>~~The interface after Balenaetcher is opened is shown below:~~ Debian11 comes with QT version '''5.15.2'''</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_qt.sh'''

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

~~[[File:pi3b-img276~~QMake version 3.~~png|429x263px|IMG_256]]~~1

Using Qt version '''5.15.2</~~div~~span>''' in /usr/lib/aarch64-linux-gnu|}</ol><ol start="34" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~How to use the AppImage~~ Debian12 comes with QT version ~~of balenaEtcher:~~ '''5.15.8'''</pli>~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>First add permissions to Balenaetcher</li></ol>~~|-| ~~</li></ol>~~orangepi@orangepi:~$ '''install_qt.sh'''

~~orangepi@orangepi:~/Desktop$ '''chmod +x balenaEtcher-1~~.7.~~9+5945ab1f-arm64~~.~~AppImage'''~~...

~~<ol start="2" style="list-style-type: lower-alpha;"><li>Then select the AppImage~~ QMake version ~~balenaEtcher right -click the mouse, and then click Execute to open balenaEtcher</li></ol>~~3.1

~~[[File~~Using Qt version '''5.15.8''' in /usr/lib/aarch64-linux-~~img277.png~~gnu|~~145x118px]]~~}</ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>Then you can see the QT Creator launch icon in '''Applications'''</li>

~~== The installation method of the Bt-Panel Linux panel ==~~img327.png]]

QT Creator can also be opened using the following command{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''qtcreator'''Bt|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-~~Panel Linux panel is a server management software that improves operation~~ | <big>'''During the startup of QT 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~~ QT applications, if the ~~[https://www.bt~~following error is displayed, ignore it.~~cn/new/index~~This error has no impact on application running.~~html official website of the Bt-Panel])~~'''

~~# First of all, the size of the'''/tmp''' space is needed. After setting, you need to '''restart the Linux system of the development board''', and the command is shown below:~~

~~orangepi@orangepi:~$~~ '''~~sudo sed -i 's/nosuid/&,size=2G/' /etc/fstab~~libGL error: failed to create dri screen'''

~~orangepi@orangepi:~$~~ '''~~sudo reboot~~libGL error: failed to load driver: rockchip'''

~~<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~~libGL error:~~~$ '''df -h | grep "/tmp"'''~~ ~~tmpfs 2.0G 12K '''2.0G''' 1% /tmp~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then enter the following command in the Linux system~~ failed to ~~start the installation of the Bt-Panel</li></ol>~~ ~~orangepi@orangepi:~$ '''sudo install_bt_panel.sh~~create dri screen'''

'''libGL error: failed to load driver: rockchip'''</big>

|}

</ol>

<li>~~Then the pagoda installation program reminds whether to install the '''Bt-Panel''' to the'''/www''' folder, and enter y at this time~~The interface after QT Creator is opened is as follows</li~~></ol~~>

~~+----------------------------------------------------------------~~[[File:pi3b-img328.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>The QT Creator version is shown below<ol style="list-style-type: lower-alpha;"><li>The default version of QT Creator in '''Ubuntu20.04''' is as follows</li>

~~| Bt~~[[File:pi3b-~~WebPanel FOR CentOS~~img329.png]]</~~Ubuntu~~ol><ol start="2" style="list-style-type: lower-alpha;"><li>The default version of QT Creator in '''Ubuntu22.04''' is as follows</~~Debian~~li>

~~+------------------------------------------------------------------~~[[File:pi3b-img330.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The default version of QT Creator in '''Debian11''' is as follows</li>

~~| Copyright © 2015~~[[File:pi3b-~~2099 BT~~img331.png]]</ol><ol start="4" style="list-~~SOFT(http~~style-type:lower-alpha;"><li>The default version of QT Creator in '''Debian12''' is as follows</~~/www.bt.cn) All rights reserved.~~li>

~~+---------------------------------------------------------------~~[[File:pi3b-img332.png]]</ol></li></ol><ol start="6" style="list-style-type: decimal;"><li>Then set QT<ol style="list-style-type: lower-alpha;"><li>First open '''Help'''->'''About Plugins...'''</li>

~~| The WebPanel URL will be http~~[[File:pi3b-img333.png]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then remove the check box for '''ClangCodeModel'''</~~SERVER_IP:8888 when installed.~~li>

~~+----------------------------------------------------------------~~[[File:pi3b-img334.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>'''Restart QT Creator after the Settings are complete'''</li><li>Then make sure that QT Creator uses the GCC compiler, if the default is Clang, change it to GCC</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Debian12 Please skip this step.'''</big>|}

~~Do you want to install Bt~~[[File:pi3b-~~Panel to the /www directory now?(y/n): '''y'''~~img335.png]]

[[File:pi3b-img336.png]]</ol ~~start="5" style="list-style-type: decimal;"~~><li>Then you have to wait patiently. When you see the printing information below the terminal output, it means that the pagoda has been installed. The entire installation process takes about 34 minutes. There may be some differences according to the difference in network speed</li></ol> ~~[[File:pi3b-img278.png|576x233px]]~~ <ol start="67" style="list-style-type: decimal;"><li>At this time, enter the '''panel address''' displayed above in the browser to open the login interface of the pagoda Linux panel, and then enter the '''username''' and '''password''' displayed in the corresponding position to log in to the Bt-Panel ~~[[File:pi3b-img279.png|575x281px]]</li><li>After successfully logging in to the pagoda, the following welcome interface will pop up. First, please take the intermediate user notice to read to the bottom, and then you~~ You can ~~choose "I have agreed and read" User Agreement ", and~~ then ~~click" Enter the panel " You can enter the Bt-Panel~~open a sample code</li>~~</ol>~~ ~~[[File:pi3b-img280.png|575x317px]]~~

[[File:pi3b-img337.png]]

</ol>

<li>~~After entering~~ Clicking on the ~~Bt-Panel, you~~ example code will ~~first prompt that you need to bind~~ automatically open the ~~account of the Bt-Panel official website. If you do n’t have an account~~corresponding instruction document, you can ~~go to~~ carefully read the ~~pagoda's official website ('''https://www.bt.cn''') to register one.~~instructions</li>~~</ol>~~ ~~[[File:pi3b-img281.png|576x300px]]~~

[[File:pi3b-img338.png]]

</ol>

<li>The final display interface is shown in the figure below. You can intuitively see some status information of the development board Linux system, such as load state, CPU usage, memory usage and storage space usageThen click '''Configure Project'''</li>~~</ol>~~ ~~[[File:pi3b-img282.png|575x306px]]~~

[[File:pi3b-img339.png]]

</ol>

<li>~~More functions of~~ Then click the ~~Bt-Panel can refer~~ green triangle in the lower left corner to compile and run the ~~following information to explore by yourself~~sample code</li~~></ol~~>

~~Manual:~~ [~~http~~[File:pi3b-img340.png]]</~~/docs.bt.cn '''http~~ol><ol start="11" style="list-style-type:decimal;"><li>After waiting for a period of time, the interface shown in the following figure will pop up, which indicates that QT can compile and run normally</~~/docs.bt.cn''']~~li>

~~Forum address:~~ [~~https~~[File:pi3b-img341.png]]</ol><ol start="12" style="list-style-type: decimal;"><li>Reference documents</~~www.bt.cn/bbs~~ li>{| class="wikitable" style="width:800px;" |-| '''https://~~www~~wiki.btqt.cnio/~~bbs~~Install_Qt_5_on_Ubuntu''']

~~GitHub Link:~~ '''https://~~github~~download.qt.~~com~~io/~~aaPanel~~archive/~~BaoTa~~qtcreator'''

'''https://download.qt.io/archive/qt'''|}</ol>~~== Set the Chinese environment and install Chinese input method ==~~

~~'''Note that before installing the Chinese input method, please make sure that the Linux system used in the development board is the desktop version system.'''~~== ROS Installation Method ==

=== ~~Debian system installation method~~ How to install ROS 1 Noetic on Ubuntu 20.04 ===

~~<ol style="list-style-type: decimal;"><li>First set the default '''locale'''~~ # The current active version of ROS 1 is as ~~Chinese<ol style="list-style-type: lower-alpha;"><li>Enter~~ follows, the ~~command below to start configured~~ recommended version is '''~~locale~~Noetic Ninjemys'''~~</li></ol></li></ol>~~

~~orangepi@orangepi~~:~~~$ '''sudo dpkg~~:[[File:pi3b-~~reconfigure locales'''~~img342.png|800px]]

~~<ol start="2" style="list-style-type~~: ~~lower~~:[[File:pi3b-~~alpha;"><li>Then select '''zh_CN~~img343.UTF-8 UTF-8''' in the pop-up interface (to move up and down through the upper and lower direction buttons on the keyboard, select it through the space key, and finally move the cursor to '''<OK>''' through the TAB key, then press the ENTER key )</li></ol>png|800px]]

::{| class="wikitable" style="width:800px;" |-| [~~[File~~http://docs.ros.org/ '''http:~~pi3b-img283~~//docs.ros.~~png|575x296px]~~org''']

~~<ol start="3" style="list-style-type: lower-alpha;"><li>Then set the default~~ '''~~locale''' as '''zh_CN~~https://wiki.ros.~~UTF-8~~org/Distributions'''~~</li></ol>~~|}

<ol start="2" style="list-style-type: decimal;"><li>The official installation document link of ROS 1 '''Noetic Ninjemys''' is as follows:</li>{| class="wikitable" style="width:800px;" |-| [~~[File~~http://wiki.ros.org/noetic/Installation/Ubuntu '''http:~~pi3b-img284~~//wiki.ros.~~png~~org/noetic/Installation/Ubuntu''']|~~575x160px]]~~}</ol><ol start="43" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~After exiting the interface,~~ In the official installation document of ROS '''~~locale~~Noetic Ninjemys''' ~~settings will be started~~, Ubuntu recommends using Ubuntu20. ~~The output displayed~~ 04, so please make sure that the system used by the ~~command line~~ development board is ~~shown below~~'''Ubuntu20.04 desktop system</lispan>'''</olli>{| class="wikitable" style="width:800px;" |-| http://wiki.ros.org/noetic/Installation|}

[[File:pi3b-img344.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then use the script below to install ros1</li>{| class="wikitable" style="width:800px;" |-| orangepi@~~orangepi~~orangepi3b:~$ '''~~sudo dpkg~~install_ros.sh ros1'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>Before using the ROS tool, you first need to initialize rosdep, and then you can quickly install some system dependencies and some core components in ROS when compiling the source code</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-~~reconfigure locales~~| <big>'''Note that running the following command needs to ensure that the development board can access github normally, otherwise an error will be reported due to network problems.'''

~~Generating locales (this might take a while)...~~

~~en_US~~'''The install_ros.~~UTF-8~~sh script will try to modify /etc/hosts and automatically run the following commands.However, this method cannot guarantee normal access to github every time.If the following error is displayed after installing ros1 in install_ros. ~~done~~sh, please find other ways to allow the Linux system of the development board to access github normally, and then manually run the following Order.'''

~~zh_CN.UTF-8... done~~

~~Generation complete~~'''https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml'''

~~<ol start="2" style="list-style-type: decimal;"><li>Then open~~ '''~~Input Method~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml'''~~</li></ol>~~

~~[[File~~'''ERROR:~~pi3b-img285.png|575x361px]]~~error loading sources list:'''

:'''The read operation timed out'''<~~ol start~~/big>|}{| class="3wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then select~~ |-| orangepi@orangepi:~$ '''OKsource /opt/ros/noetic/setup.bash'''~~</li></ol>~~

~~[[File~~orangepi@orangepi:~~pi3b-img286.png|295x212px]]~~~$ '''sudo rosdep init'''

~~<ol start="4" style="~~Wrote /etc/ros/rosdep/sources.list.d/20-~~style-type: decimal;"><li>Then select '''Yes'''</li></ol>~~default.list

~~[[File~~Recommended:~~pi3b-img287.png|303x192px]]~~please run

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

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

~~[[File~~:~~pi3b-img288.png|307x220px]]~~:rosdep update

~~<ol start="6" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>Then select~~ ~$ '''OKrosdep update'''~~</li></ol>~~

~~[[File:pi3b-img289~~reading in sources list data from /etc/ros/rosdep/sources.~~png|305x216px]]~~list.d

~~<ol start="7" style="list-style-type~~Hit https: ~~decimal;"><li>'''Then restart the Linux system to make the configuration effective'''<~~/~~p><~~/~~li><li>Then open '''Fcitx configuration'''<~~raw.githubusercontent.com/~~p><~~ros/~~li><~~rosdistro/~~ol>~~master/rosdep/osx-homebrew.yaml

~~[[File~~Hit https:~~pi3b-img290~~//raw.~~png|575x376px]]~~githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml

~~<ol start="9" style="list-style-type~~Hit https: ~~decimal;"><li>Then click the + of the position shown in the figure below<~~/~~li><~~/~~ol>~~raw.githubusercontent.com/ros/rosdistro/master/rosdep/python.yaml

~~[[File~~Hit https:~~pi3b-img291~~//raw.~~png|280x187px]]~~githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml

~~<ol start="10" style="list-style-type~~Hit https: ~~decimal;"><li>Then search '''Google Pinyin''' and click '''OK'''<~~/~~li><~~/~~ol>~~raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml

~~<div class="figure">~~Query rosdistro index https://raw.githubusercontent.com/ros/rosdistro/master/index-v4.yaml

~~[[File:pi3b~~Skip end-~~img292.png|291x196px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~of-~~10.jpg未标题-10]]~~life distro "ardent"

~~</div><ol start="11" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "bouncy"">~~<li>Then put '''Google Pinyin''' to the front</li></ol>~~

~~[[File:pi3b~~Skip end-~~img293.png|299x202px]]~~of-life distro "crystal"

~~[[File:pi3b~~Skip end-~~img294.png|300x202px]]~~of-life distro "dashing"

~~<ol start="12" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "eloquent"">~~<li>Then open the '''Geany''' editor to test the Chinese input method</li></ol>~~

~~[[File:pi3b-img295.png|349x212px]]~~Add distro "foxy"

~~<ol start="13" style="list-style-type: decimal~~Add distro "galactic"">~~<li>The Chinese input method test is shown below</li></ol>~~

~~[[File:pi3b~~Skip end-~~img296.png|575x325px]]~~of-life distro "groovy"

~~<ol start="14" style="list-style-type: decimal~~Add distro "humble"">~~<li>You can switch the Chinese and English input method through the '''Ctrl+Space''' shortcut</li><li>If the entire system is required as Chinese, the variables in '''/etc/default/locale''' can be set to '''zh_CN.UTF-8'''</li></ol>~~

~~orangepi@orangepi:~$ '''sudo vim /etc/default/locale'''~~Skip end-of-life distro "hydro"

~~# File generated by update~~Skip end-~~locale~~of-life distro "indigo"

~~LC_MESSAGES='''zh_CN.UTF~~Skip end-~~8'''~~of-life distro "jade"

~~LANG='''zh_CN.UTF~~Skip end-~~8'''~~of-life distro "kinetic"

~~LANGUAGE='''zh_CN.UTF~~Skip end-~~8'''~~of-life distro "lunar"

~~<ol start="16" style="list-style-type: decimal~~Add distro "melodic"">~~<li>Then '''restart the system''' to see the system displayed as Chinese</li></ol>~~

~~[[File:pi3b-img297.png|576x356px]]~~Add distro "noetic"

~~=== The installation method of Ubuntu 20.04 system ===~~Add distro "rolling"

~~# First~~ updated cache in /home/orangepi/.ros/rosdep/sources.cache|}</ol><ol start="6" style="list-style-type: decimal;"><li>Then open a command line terminal window on the desktop, and then use the test_ros.sh script to start a small turtle routine to test whether ROS can be used normally</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~Language Support~~test_ros.sh'''|}<li>After running the '''test_ros.sh''' script, a little turtle as shown in the figure below will pop up</li>

~~[[File:pi3b-img298.png|575x351px]]~~<div class="figure">

~~<ol start="2" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Then find '''Chinese (China)''' option</li></ol>~~img345.png]]

~~[[File~~</div></ol><ol start="8" style="list-style-type:~~pi3b-img299.png|318x311px]]~~decimal;"><li>Then please keep the terminal window just opened at the top</li>

<~~ol start~~div class="3figure" ~~style="list-style-type: decimal;"><li>Then use the left mouse button to select '''Chinese (China)''' and hold it down, and then drag it up to the beginning. The display is shown below: </li></ol~~>

[[File:pi3b-~~img300~~img346.png~~|324x320px~~]]

~~'''Note that~~ </div></ol><ol start="9" style="list-style-type: decimal;"><li>At this ~~step is not easy~~ time, press the direction keys on the keyboard to control the little turtle to ~~drag~~move up, down, left, ~~please try more patiently.'''~~and right</li>

[[File:pi3b-img347.png]]</ol ~~start~~>~~<li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system~~</~~li></ol~~span>

~~[[File:pi3b-img301~~=== How to install ROS 2 Galactic on Ubuntu 20.~~png|321x316px]]~~04 ===

~~<ol start="5" style="list-style-type: decimal;"><li>Then set~~ # The current active version of ROS 2 is as follows, the recommended version is '''~~Keyboard input method system~~Galactic Geochelone''' ~~to '''fcitx'''</li></ol>~~

::[[File:pi3b-~~img302~~img348.png~~|327x320px~~]]

~~<ol start="6" style="list-style-type~~: ~~decimal;"><li>'''hen restart the Linux system to make the configuration effective'''</li><li>After re~~ :[[File:pi3b-~~entering the system, please do '''not ask me again''' at the interface below, and then determine whether the standard folder should be updated as Chinese based on your preference~~img349.~~</li></ol>~~png]]

::{| class="wikitable" style="width:800px;" |-| [~~[File~~http://docs.ros.org/ '''http:~~pi3b-img303~~//docs.ros.~~png|303x247px]~~org''']

~~<ol start="8" style="list-style-type~~'''http: ~~decimal;"><li>Then you can see that the desktop is displayed as Chinese<~~/~~li><~~/~~ol>~~docs.ros.org/en/galactic/Releases.html'''|}

~~[[File:pi3b-img304.png|575x383px]]~~ <ol start="92" style="list-style-type: decimal;"><li>~~Then we can open~~ The link to the official ROS 2 '''~~Geany~~Galactic Geochelone''' ~~to test Chinese input method , and the way to open~~ installation documentation is ~~shown in the figure below~~as follows:</li><{| class="wikitable" style="width:800px;" |-| '''docs.ros.org/en/galactic/~~ol>~~Installation.html'''

~~[[File~~'''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:~~pi3b~~decimal;"><li>The '''install_ros.sh''' script will automatically run the '''ros2 -~~img305~~h''' command after installing ros2.~~png~~If you can see the following print, it means that the ros2 installation is complete</li>{|~~576x292px]~~class="wikitable" style="width:800px;" |-| usage: ros2 [-h]Call `ros2 <command> -h` for more detailed usage. ...

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

~~[[File:pi3b~~ros2 is an extensible command-~~img306~~line tool for ROS 2.~~png|575x308px]]~~

~~~~

~~=== The installation method of ubuntu 22.04 system ===~~

~~# First open '''Language Support'''~~optional arguments:

~~[[File~~:~~pi3b~~-~~img298.png|575x351px]]~~h, --help show this help message and exit

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

~~<li>Then find '''Chinese (China)''' option</li></ol>~~

~~[[File~~Commands:~~pi3b-img307.png|335x326px]]~~ ~~<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>~~

~~[[File~~:~~pi3b~~action Various action related sub-~~img308.png|337x331px]]~~commands

~~'''Note that this step is not easy to drag, please try more patiently.'''~~ ~~<ol start="4" style="list-style-type~~: ~~decimal;"><li>Then select the '''Apply System~~bag Various rosbag related sub-~~Wide''' to apply the Chinese settings to the entire system</li></ol>~~commands

~~[[File~~:~~pi3b~~component Various component related sub-~~img309.png|336x330px]]~~commands

~~<ol start="5" style="list-style-type~~: ~~decimal;"><li>'''Then restart the Linux system to make the configuration effective'''</li><li>After re~~ daemon Various daemon related sub-~~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>~~commands

~~[[File~~:~~pi3b-img303.png|303x247px]]~~doctor Check ROS setup and other potential issues

~~<ol start="7" style="list-style-type~~: ~~decimal;"><li>Then you can see that the desktop is displayed as Chinese</li></ol>~~interface Show information about ROS interfaces

~~[[File~~:~~pi3b-img304.png|575x383px]]~~launch Run a launch file

~~<ol start="8" style="list~~:lifecycle Various lifecycle related sub-~~style-type: decimal;"><li>Then open the Fcitx5 configuration program</li></ol>~~commands

~~[[File~~:~~pi3b~~multicast Various multicast related sub-~~img310.png|575x349px]]~~commands

~~<ol start="9" style="list~~:node Various node related sub-~~style-type: decimal;"><li>Then choose to use Pinyin input method</li></ol>~~commands

~~<div class="figure">~~:param Various param related sub-commands

~~[[File~~:~~pi3b~~pkg Various package related sub-~~img311.png|338x267px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-11.jpg未标题-11]]~~commands

~~</div><ol start="10" style="list-style-type~~: ~~decimal;"><li>The interface after the selection is shown below, then click OK</li></ol>~~run Run a package specific executable

~~[[File~~:~~pi3b~~security Various security related sub-~~img312.png|366x290px]]~~commands

~~<ol start="11" style="list~~:service Various service related sub-~~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>~~commands

~~[[File~~:~~pi3b~~topic Various topic related sub-~~img305.png|576x292px]]~~commands

~~<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>wtf Use `wtf` as alias to `doctor`

~~[[File:pi3b-img313.png|576x408px]]~~

:Call `ros2 <command> -h` for more detailed usage.|}</ol><~~span id~~ol start="6" style="~~how~~list-~~to-remotely-log-in~~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~~-linux-system-desktop-method">~~following print, it means that ROS 2 can run normally</~~span~~li>{| class="wikitable" style= ~~How to remotely log in to the Linux system desktop method ==~~"width:800px;" |-| orangepi@orangepi3b:~$ '''test_ros.sh'''

~~'''Ubuntu Gnome Wayland image does not support Nomachine and VNCs introduced here to remotely log in to the desktop~~[INFO] [1671174101.200091527] [talker]: Publishing: ''Hello World: 1'

~~=== Use nomachine remote login ===~~[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: 1]

~~'''Make sure the Ubuntu or Debian system installed on the development board is a desktop version~~[INFO] [1671174102. ~~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~~199572327] [talker]: Publishing: ''Hello World: 2'

~~'''https~~[INFO] [1671174102.204196299] [listener]:~~//knowledgebase.nomachine.com/DT10R00166'''~~I heard: [Hello World: 2]

'''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[INFO] [1671174103. ~~For installation methods for other platforms, please refer to the official documentation of Nomachine.'~~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:~$ '''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 normallysource /opt/ros/galactic/setup.bash'''

~~<ol style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>First download the nomachine software Linux ''~~~$ '~~ARM64~~''ros2 run rviz2 rviz2' ~~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></ol></li></ol>~~|}

~~'''Note that this download link may change, please recognize the DEB package of the ARMV8/ARM64 version.'''~~<div class="figure">

[~~https~~[File:~~//www~~pi3b-img350.~~nomachine.com/download/download&id=112&s=ARM '''https://downloads.nomachine.com/download/?id=118&distro=ARM'''~~png]]

~~[[File~~</div></ol><ol start="8" style="list-style-type:~~pi3b~~decimal;"><li>For the usage of ROS, please refer to the documentation of ROS 2</li>{| class="wikitable" style="width:800px;" |-~~img314~~| '''http://docs.ros.org/en/galactic/Tutorials.~~png~~html'''|~~575x227px]]~~}</ol>

~~<ol start~~=~~"2" style~~=~~"list-style-type: lower-alpha;"><li>In addition, you can also download the installation package~~ = How to ~~'''NoMachine''' in the '''official tools'''~~install ROS 2 Humble on Ubuntu 22.~~</li></ol>~~04 ===

~~[[File:pi3b-img315~~# Use the '''install_ros.~~png|66x102px]]~~sh''' script to install ros2

~~<blockquote>First enter the~~ ::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~remote login software-Nomachine~~install_ros.sh ros2''' ~~folder</blockquote>[[File:pi3b-img316.png~~|~~271x43px]]~~}

<~~blockquote~~ol start="2" style="list-style-type: decimal;"><li>~~Then download~~ The '''install_ros.sh''' script will automatically run the ~~ARM64 version of~~ '''ros2 -h''' command after installing ros2. If you can see the following print, it means that the ~~DEB~~ ros2 installation ~~package~~is complete</~~blockquote~~li>~~[[File:pi3b-img317.png|180x109px]]~~

~~<ol start~~{| class="3wikitable" style="~~list~~width:800px;" |-~~style-type~~| usage: ~~lower~~ros2 [-~~alpha~~h] Call `ros2 <">~~<li>Then upload the downloaded '''nomachine_x~~command> -h` for more detailed usage.x.~~x_x_arm64~~.~~deb''' to the Linux system of the development board~~.~~</li><li>Then use the following command to install '''NoMachine''' in the Linux system of the development board</li></ol>~~

~~orangepi@orangepi:~$ '''sudo dpkg -i nomachine_x.x.x_x_arm64_arm64.deb'''~~

~~<ol start="~~ros2 is an extensible command-line tool for ROS 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></ol>~~.

~~'''Note that this download link may change.'''~~

~~'''https~~optional arguments:~~//downloads.nomachine.com/download/?id=9'''~~

~~[[File~~:~~pi3b~~-~~img318.png|575x163px]]~~h, --help show this help message and exit

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

~~<li>Then install nomachine in Windows. '''Please restart the computer after installation'''</li>~~

~~<li>Then open '''NoMachine''' in Window</li></ol>~~

~~[[File~~Commands:~~pi3b-img319.png|76x66px]]~~

~~<ol start="5" style="list~~:action Various action related sub-~~style-type: decimal;">~~<li>After Nomachine starts, it will automatically scan other devices installed in the local area network. After entering the main interface of Nomachine, you can see that the development board is already in the connected device list, and then click the location shown in the red box below in the figure below. Start log in to the Linux system desktop of the development board</li></ol>commands

~~[[File~~:~~pi3b~~bag Various rosbag related sub-~~img320.png|321x92px]]~~commands

~~<ol start="6" style="list~~:component Various component related sub-~~style-type: decimal;"><li>Then click '''OK'''</li></ol>~~commands

~~[[File~~:~~pi3b~~daemon Various daemon related sub-~~img321.png|402x275px]]~~commands

~~<ol start="7" style="list-style-type~~: ~~decimal;"><li>Then enter the username~~ doctor Check ROS setup and ~~password of the Linux system in the corresponding position in the figure below, and then click '''OK''' to start logging in</li></ol>~~other potential issues

~~<div class="figure">~~:interface Show information about ROS interfaces

~~[[File~~:~~pi3b-img322.png|303x204px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-12.jpg未标题-12]]~~launch Run a launch file

~~</div><ol start="8" style="list-style-type: decimal;"><li>Then click OK in the next interface</li><li>Finally, you can see the desktop of the development board Linux system[[File~~:~~pi3b~~lifecycle Various lifecycle related sub-~~img323.png|411x246px]]</li></ol>~~commands

~~=== Use VNC remote login ===~~commands

'''Before operation, please ensure that the Windwos computer and the development board are in the same local area network, and you can log in to the Ubuntu or Debian system of the development board normally.''':node Various node related sub-commands

~~'''Ubuntu 20.04 tests many problems with VNC, please do not use this method.'''~~:param Various param related sub-commands

~~# First run the '''set_vnc.sh''' script settings, and '''remember to add Sudo permissions'''~~:pkg Various package related sub-commands

~~orangepi@orangepi~~:~~~$ '''sudo set_vnc.sh'''~~run Run a package specific executable

~~You will require a password to access your desktops.~~:security Various security related sub-commands

~~Password~~: ~~'''#Set the VNC password here, 8~~ service Various service related sub-~~bit characters'''~~commands

~~Verify~~: ~~'''#Set the VNC password here, 8~~ topic Various topic related sub-~~bit characters'''~~commands

~~Would you like~~ :wtf Use `wtf` as alias to ~~enter a view-only password (y/n)? '''n'''~~`doctor`

~~xauth: file /root/.Xauthority does not exist~~

~~New~~ :Call `ros2 <command> -h` for more detailed usage.|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then you can use the ''X' ~~desktop~~ test_ros.sh''' script to test whether ROS 2 is ~~orangepi3b:1~~installed successfully. If you can see the following print, it means that ROS 2 can run normally</li>

~~Creating default startup script /root/~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi3b:~$ '''test_ros.~~vnc/xstartup~~sh'''

~~Starting applications specified in /root/~~[INFO] [1671174101.~~vnc/xstartup~~200091527] [talker]: Publishing: 'Hello World: 1'

~~Log file is /root/~~[INFO] [1671174101.~~vnc/orangepi3b~~235661048] [listener]: I heard: [Hello World:1~~.log~~]

~~Killing Xtightvnc process ID 3047~~[INFO] [1671174102.199572327] [talker]: Publishing: 'Hello World: 2'

~~New 'X' desktop is orangepi3b~~[INFO] [1671174102.204196299] [listener]:1I heard: [Hello World: 2]

~~Starting applications specified in /root/~~[INFO] [1671174103.~~vnc/xstartup~~199580322] [talker]: Publishing: 'Hello World: 3'

~~Log file is~~ [INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]|}</ol><ol start="4" style="list-style-type: decimal;"><li>Run the following command to open rviz2</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''source /opt/~~root~~ros/~~.vnc~~humble/~~orangepi3b:1~~setup.~~log~~bash'''

~~<ol start="2" style="list-style-type~~orangepi@orangepi: ~~decimal;">~~~$ '''ros2 run rviz2 rviz2'''~~<li>The steps of using MobaxTerm software to connect the development board Linux system desktop are shown below: <ol style="list-style-type: lower-alpha;"><li>First click Session, then select VNC, then fill in the IP address and port of the development board, and finally click OK to confirm</li></ol></li></ol>~~|}

[[File:pi3b-~~img324~~img351.png~~|490x349px|图片1208~~]]

</div></ol><ol start="25" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then enter the password of the previously set VNC~~Reference documents</li>{| class="wikitable" style="width:800px;" |-| '''http://docs.ros.org/en/humble/index.html''' [http://docs.ros.org/en/galactic/Tutorials.html '''http://docs.ros.org/en/humble/Installation/Ubuntu-Install-Debians.html''']|}</ol>

~~[[File:pi3b-img325.png|274x131px]]~~== How to install kernel header files ==

~~<ol start="3" style="list-style-type: lower-alpha;"><li>~~# The ~~interface after~~ Linux image released by OPi comes with the ~~login is shown as shown in~~ deb package of the ~~figure below~~kernel header file by default, and ~~then~~ the ~~desktop of the Linux system can be remotely operated[[File:pi3b-img326.png|405x293px]]<~~storage location is '''/~~li><~~opt/~~ol>~~'''

~~== Some programming language tests supported by Linux system ==~~headers*'''

~~~~legacy-rockchip-rk356x_x.x.x_arm64.deb~~=== Debian Bullseye system ===~~|}

<ol start="2" style="list-style-type: decimal;"><li>Use the following command to install the deb package of the kernel header file<p/li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>~~Debian Bullseye is equipped~~ '''The name of the kernel header file deb package needs to be replaced with ~~a gcc compilation tool chain by default~~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, ~~which~~ you can ~~directly compile~~ see the ~~C language program in~~ folder where the ~~Linux system of~~ kernel header files are located under '''/usr/src'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ls /usr/src''' 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 ~~development board~~kernel header file

<li>~~The version~~ First write the code of the ~~gcc is shown below~~hello kernel module, as follows:</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello.c''' <~~/ol~~p><#include <linux/~~li>~~init.h></olp>

~~orangepi@orangepi:~$ '''gcc --version'''~~#include <linux/module.h>

~~gcc (Debian 10.2.1-6) 10.2.1 20210110~~

~~Copyright~~ static int hello_init(Cvoid) ~~2020 Free Software Foundation, Inc.~~

~~This is free software; see the source for copying conditions. There is NO~~{

~~warranty~~:printk("Hello Orange Pi -- init\n"); ~~not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.~~

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

~~<li>Write C language of '''Hello_world.c''' program</li></ol>~~

~~orangepi@orangepi~~:~~~$ '''vim hello_world.c'''~~return 0;

~~#include <stdio.h>~~}

~~int main~~static void hello_exit(void)

{

~~printf~~:printk("Hello ~~World!~~Orange Pi -- exit\n");

:return 0;

}

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

~~<li>Then compile and run '''hello_world.c'''</li></ol>~~

~~orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''~~module_init(hello_init);

~~orangepi@orangepi:~$ '''./hello_world'''~~module_exit(hello_exit);

~~Hello World!~~

MODULE_LICENSE("GPL");|}</ol><ol start="2" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Debian BullSeye Default with Python3~~Then write the Makefile for compiling the hello kernel module, as follows:</pli>~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>The specific version of Python is shown below</li></ol>~~|-| ~~</li></ol>~~orangepi@orangepi:~$ '''vim Makefile'''

~~orangepi@orangepi:~~~ifneq ($ ~~'''python3'''~~(KERNELRELEASE),)

~~'''Python 3.9~~obj-m:=hello.~~2''' (default, Feb 28 2021, 17:03:44)~~o

~~[GCC 10.2.1 20210110] on linux~~else

~~Type "help", "copyright", "credits" or "license" for more information.~~KDIR :=/lib/modules/$(shell uname -r)/build

~~>>>~~PWD :=$(shell pwd)

~~<ol start="2" style="list-style-type~~all: ~~lower-alpha;"><li>'''hello_world.py''' program in Python language</li></ol>~~ ~~orangepi@orangepi:~$ '''vim hello_world.py'''~~

~~print~~:make -C $(~~'Hello World!'~~KDIR)M=$(PWD) modules

~~<ol start="3" style="list-style-type~~clean: ~~lower-alpha;"><li>The results of running '''hello_world.py''' are shown below</li></ol>~~

~~orangepi@orangepi~~:~~~$ '''python3 hello_world~~rm -f *.ko *.o *.mod.o *.mod *.symvers *.cmd *.mod.~~py'''~~ ~~Hello World!~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Debian Bullseye's compilation tool and operating environment that is not installed in Java by default<ol style="list-style-type: lower-alpha;"><li>You can use the following command to install OpenJDK~~c *. ~~The latest version in Debian Bullseye is openjdk-17</li></ol></li></ol>~~ ~~orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>After installation, you can check the version of Java</li></ol>~~ ~~orangepi@orangepi:~$ '''java --version'''~~order

endif

|}

</ol>

<li>~~Edit~~ Then use the make command to compile the hello kernel module. The output of the compilation process is as follows:</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~hello_world~~If there is a problem with compiling the code you copied here, please go to the official tool to download the source code and upload it to the Linux system of the development board for testing.~~java~~''' ~~of the Jave version</li>~~</olbig>

[[File:pi3b-img352.png|center]]|}{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~vim hello_world.java~~make'''

~~public class hello_world~~make -C /lib/modules/5.10.160-rockchip-35xx/build M=/home/orangepi modules

{make[1]: Entering directory '/usr/src/linux-headers-5.10.160-rockchip-rk35xx'

~~public static void main(String~~:CC [M] ~~args)~~/home/orangepi/hello.o

{:MODPOST /home/orangepi/Module.symvers

~~System~~:CC [M] /home/orangepi/hello.~~out~~mod.~~println("Hello World!");~~o

} }:LD [M] /home/orangepi/hello.ko

make[1]: Leaving directory '/usr/src/linux-headers-5.10.160-rockchip-rk35xx'

|}

</ol>

<li>~~Then compile and run~~ After compiling, the '''~~hello_world~~hello.~~java~~ko'''kernel module will be generated</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ls *.ko'''

hello.ko|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Use the '''insmod''' command to insert the '''hello.ko''' kernel module into the kernel</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~javac hello_world~~sudo insmod hello.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.~~java~~</li> {| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''dmesg | grep "Hello"'''

[ 2871.893988] '''Hello Orange Pi -- init'''|}</ol><ol start="7" style="list-style-type: lower-alpha;"><li>Use the '''rmmod''' command to uninstall the '''hello.ko''' kernel module</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~java hello_world~~sudo rmmod hello'''

orangepi@orangepi:~$ '''dmesg | grep "Hello ~~World!~~"'''

~~=== Ubuntu Focal system ===~~init

~~<ol style="list~~[ 3173.800892] '''Hello Orange Pi -~~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.~~exit'''~~<ol style="list-style-type: lower-alpha;">~~|}~~<li>The version of the gcc is shown below</li>~~</ol>

</li></ol>

~~orangepi@orangepi:~$~~ == Use of the Raspberry PI'~~''gcc -~~s 5-~~version'''~~inch screen ==

~~gcc (Ubuntu 9.4.0~~=== Assembly method of Raspberry PI 5-inch screen ===

~~Copyright (C) 2019 Free Software Foundation, Inc.~~<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>

~~This is free software~~[[File:pi3b-img353.png]]</ol><ol start="2" style="list-style-type: lower-alpha; ~~see the source for copying conditions. There is NO~~"><li>15pin MIPI cable</li>

~~warranty~~[[File:pi3b-img354.png]]</ol></li></ol><ol start="2" style="list-style-type: decimal; ~~not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.~~"><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>

[[File:pi3b-img355.png]]</ol><ol start="23" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~'''hello_world.c''' program~~ Finally connect to ~~write C language~~the LCD interface of the Orange Pi 3B development board</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''vim hello_world~~pi3b-img356.~~c'''~~png]]</ol>

~~#include <stdio.h>~~=== Open the Raspberry PI 5-inch screen configuration method ===

~~int main(void)~~<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>

{[[File:pi3b-img357.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then select '''Hardware'''</li>

~~printf("Hello World!\n")~~[[File:pi3b-img358.png]]</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then use the arrow keys on the keyboard to locate the Rasp-7inch-touchscreen, and then use the space button to check</li>

~~return 0~~[[File:pi3b-img359.png]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then select '''<Save>''' to save</li>

}[[File:pi3b-img360.png]]</ol><ol start="6" style="list-style-type: lower-alpha;"><li>Then select '''<Back>'''</li>

[[File:pi3b-img361.png]]</ol><ol start="37" style="list-style-type: lower-alpha;"><li>Then ~~compile and run~~ select '''~~hello_world.c~~<Reboot>'''to restart the system for the configuration to take effect</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''gcc~~ pi3b-~~o hello_world hello_world~~img362.~~c'''~~png]]

~~orangepi@orangepi~~{| class="wikitable" style="background-color:~$ #ffffdc;width:800px;" |-| <big>'''The above settings will eventually add the configuration of overlays=raspi-7inch-touchscreen to /boot/orangepiEnv.txt. After setting, you can check it first. If this configuration does not exist, then there is a problem with the settings.~~/hello_world~~''' ~~Hello World!~~

'''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 <~~ol start="2"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>Ubuntu Focal defaults to install Python3<ol style~~overlays=~~"list~~raspi-~~style~~7inch-~~type: lower-alpha;">~~touchscreen<li/span>~~Python3 specific version~~ is ~~shown below</li></ol></li>~~also possible.'''</olbig>

~~orangepi@orangepi:~$ '''python3'''~~

~~Python 3.8~~orangepi@orangepi:~$ '''cat /boot/orangepiEnv.~~10 (default, Nov 14 2022, 12:59:47)~~txt | grep "raspi"'''

~~[GCC 9.4.0] on linux~~'''overlays=raspi-7inch-touchscreen #Sample configuration'''|}</ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>After startup, you can see the lcd screen display as follows:</li>

~~Type "help", "copyright", "credits" or "license" for more information~~[[File:pi3b-img363.png]]</ol>

~~>>>~~=== The method of server version image rotation display direction ===

<ol start="21" style="list-style-type: ~~lower-alpha~~decimal;"><li>Add '''extraargs=fbcon=rotate:the direction to rotate'''in '~~hello_world~~''/boot/orangepiEnv.pytxt'''This line configuration can set the direction displayed by the server version of the Linux system, where the number after '' ~~program in Python language~~'fbcon=rotate:''' can be set as:</lip></olli>

<ol style="list-style-type: lower-alpha;"><li>0: normal screen (default is landscape)</li><li>1: Turn clockwise 90 degrees</li><li>2: Flip 180 degrees</li><li>3: Turn clockwise 270 degrees</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo vim ~~hello_world~~/boot/orangepiEnv.pytxt'''

~~print('Hello World!')~~overlays=lcd1

'''extraargs=cma=64M fbcon=rotate:3'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''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).'''</big>|}</ol></li></ol><ol start="32" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The results of running~~ Then '''~~hello_world.py~~restart''' ~~are shown below~~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 ===

~~orangepi@orangepi:~$~~ # First open '''~~python3 hello_world.py~~Display'''Settings in Linux

~~Hello World!~~::[[File:pi3b-img364.png]]

<ol start="32" style="list-style-type: decimal;"><li>~~Ubuntu Focal~~Then select the direction you want to rotate in '''Rotation'''~~s compilation tool and operating environment without the installation of Java default~~

<li>~~You can use the following command~~ '''None''': no rotation</li><li>'''Left''': rotate left 90 degrees</li><li>'''Inverted''': Flip up and down, which is equivalent to ~~install~~ rotating 180 degrees</li><li>'''~~openjdk-17~~Right''': rotate right 90 degrees</li> [[File:pi3b-img365.png]]</ol>

</li></ol>

<li>Then click '''Apply'''</li>

~~orangepi@orangepi~~[[File:~$ pi3b-img366.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select '''~~sudo apt install -y openjdk-17-jdk~~Keep this configuration'''</li>

[[File:pi3b-img367.png]]

</ol>

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

<li>'''None''': no rotation</li>

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

|-

|

orangepi@orangepi:~$ '''set_lcd_rotate.sh none'''

|}

</ol>

<li>~~After installation~~'''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, ~~you can check the version of Java~~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:'''

~~orangepi@orangepi:~$ '''java --version'''~~

~~openjdk 17~~'''1.~~0.2 2022-01-18~~Rotate the direction displayed by the framebuffer'''

~~OpenJDK Runtime Environment (build 17.0.~~'''2~~+8-Ubuntu-120~~.~~04)~~Rotate the direction of the touch'''

~~OpenJDK 64-Bit Server VM (build 17~~'''3.~~0.2+8-Ubuntu-120.04, mixed mode, sharing)~~Turn off the boot logo'''

~~<ol start="3" style="list-style-type: lower-alpha;"><li>Edit the~~ '''~~hello_world~~4.~~java~~Restart the system''' ~~of Jave version</li></ol>~~

~~orangepi@orangepi:~$ '''vim hello_world.java'''~~

~~public~~ '''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><ol start="7" style="list-style-type: decimal;"><li>Touch rotation reference</li>{| class ~~hello_world~~="wikitable" style="width:800px;" |-| '''https://wiki.ubuntu.com/X/InputCoordinateTransformation'''|}</ol>

{== Instructions for using the switch logo ==

~~public static void main(String[] args)~~# By default, the switch logo will only be displayed in the desktop version of the system# Set the '''bootlogo''' variable to '''false''' in '''/boot/orangepiEnv.txt''' to turn off the switch logo

::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim /boot/orangepiEnv.txt'''

~~System.out.println("Hello World!");~~verbosity=1

'''bootlogo=false'''|}

}<ol start="3" style="list-style-type: decimal;"><li>Set the '''bootlogo''' variable to '''true''' in '''/boot/orangepiEnv.txt''' to enable the switch logo</li>

~~<ol start~~{| class="4wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Then compile and run~~ |-| orangepi@orangepi:~$ '''~~hello_world~~vim /boot/orangepiEnv.~~java~~txt'''~~</li></ol>~~

~~orangepi@orangepi:~$ '''javac hello_world.java'''~~verbosity=1

'''bootlogo=true'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>The location of the boot logo image in the Linux system is</li>{| class="wikitable" style="width:800px;" |-| '''/usr/share/plymouth/themes/orangepi/watermark.png'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>After replacing the boot logo picture, you need to run the following command to take effect</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~java hello_world~~sudo update-initramfs -u'''|}</ol>

~~Hello World!~~== How to use the ZFS file system ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The latest version of Ubuntu20.04, Ubuntu22.04, Debian11 and Debian12 desktop version systems~~=== Ubuntu jammy system ===~~have pre-installed zfs, you can use it directly.'''

~~<ol style="list~~'''The pre-~~style-type: decimal;"><li>Ubuntu Jammy is~~ installed ~~with the GCC compilation tool chain by default, which can directly compile the C language program~~ zfs version in ~~the Linux system of the development board<ol style="list-style-type: lower-alpha;"><li>The version of the gcc~~ Ubuntu20.04 and Ubuntu22.04 desktop systems is ~~shown below</li></ol></li></ol>~~2.1.6.'''

~~orangepi@orangepi:~$~~ '''~~gcc -~~The pre-installed zfs versionin Debian11 and Debian12 desktop systems is 2.1.11.'''

~~gcc (Ubuntu 11.2.0-19ubuntu1)~~ '''11After the system starts, please first confirm whether the zfs kernel module has been loaded.2If you can see zfs-related content using the lsmod command, it means that the system has pre-installed zfs.0'''</big>

~~This is free software~~zfs   ~~see the source for copying conditions. There is NO~~                   2801664     0

~~warranty~~zunicode   ~~not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.~~           327680     1   zfs

~~<ol start="2" style="list-style-type: lower-alpha~~zzstd  ">~~<li>Write the '''hello_world.c''' program of c language</li></ol>~~                471040     1   zfs

~~orangepi@orangepi:~$ '''vim hello_world.c'''~~zlua                    139264     1   zfs

~~#include~~ zcommon &ltnbsp;~~stdio.h~~&gtnbsp;          69632     1   zfs

~~int main(void)~~znvpair                 61440     2   zfs,zcommon

{zavl                      16384     1   zfs

~~printf(~~icp &~~quot~~nbsp;~~Hello World!\n~~&~~quot~~nbsp;)                  221184     1  zfs

~~return 0~~spl                       77824     6   zfs,icp,zzstd,znvpair,zcommon,zavl|}

}=== How to install ZFS ===

~~<ol start~~{| class="3wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~Then compile and run~~ '''~~hello_world~~Before installing zfs, please make sure that the Linux image used is the latest version. In addition, if zfs is already installed in the system, it needs to be installed again.c'''</~~li></ol~~big>|}

~~orangepi@orangepi:~$~~ Before installing zfs, you need to install the kernel header file first. For the method of installing the kernel header file, please refer to the instructions in the [[Orange Pi 3B#How to install kernel header files|'''~~gcc -o hello_world hello_world.c~~section on the method of installing the kernel header file''']].

~~orangepi@orangepi:~$ '''~~In Ubuntu20.04, Ubuntu22.04 and Debian11 systems, zfs cannot be installed directly through apt, because the default apt source zfs version is lower than 2.1.6, and there is a problem of incompatibility with rk Linux5.10 kernel. This problem is fixed in zfs version 2.1.6 and later.~~/hello_world'''~~

~~Hello World!~~To solve this problem, we provide a zfs deb package that can be installed normally, which can be downloaded from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''official tool'''] of the development board. Open the '''official tool''', 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.

~~<ol start="2" style="list-style-type: decimal;"><li>Ubuntu jammy is installed with Python3 by default<ol style="list-style-type~~[[File: ~~lower~~pi3b-~~alpha;"><li>Python3 specific version is shown below</li></ol></li></ol>~~img368.png]]

~~orangepi@orangepi:~$~~ 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 '''~~python3~~[[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]].'''

~~Python~~ After the upload is complete, use the '''~~3.10.4~~cd''' ~~(main~~command in the command line of the development board Linux system to enter the directory of the deb package, ~~Apr 2 2022, 09:04:19) [GCC 11.2~~and then use the following command to install the deb package of zfs.~~0] on linux~~

~~Type &quot~~{| class="wikitable" style="width:800px;~~help", "copyright", "credits" or "license" for more information~~" |-| orangepi@orangepi:~$ '''sudo apt install ./*.deb'''|}

~~>>>~~After the installation is complete, use the following command to see the zfs-related kernel modules:

~~<ol start~~{| class="2wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Edit~~ |-| orangepi@orangepi:~$ '''~~hello_world~~ls /lib/modules/5.py10.160-rockchip-rk356x/updates/dkms/''' ~~program in Python language</li></ol>~~

~~orangepi@orangepi:~$~~ '''~~vim hello_world~~icp.pyko spl.ko zavl.ko zcommon.ko zfs.ko zlua.ko znvpair.ko zunicode.ko zzstd.ko'''|}

~~print('Hello World!')~~Then restart the Linux system to see that the zfs kernel module will be automatically loaded:

~~<ol start~~{| class="3wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>The results of running~~ |-| orangepi@orangepi:~$ '''~~hello_world.py~~lsmod | grep "zfs"''' ~~are shown below</li></ol>~~

~~orangepi@orangepi:~$ '''python3 hello_world.py'''~~zfs                     2801664     0

~~Hello World!~~zunicode             327680     1   zfs

~~<ol start="3" style="list-style-type: decimal~~zzstd  ">~~<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>~~               471040     1   zfs

~~orangepi@orangepi:~$ '''sudo apt install -y openjdk-18-jdk'''~~zlua                    139264     1   zfs

~~<ol start="2" style="list-style-type: lower-alpha~~zcommon  ">~~<li>After installation, you can check the version of Java</li></ol>~~           69632     1   zfs

~~orangepi@orangepi:~$ '''java --version'''~~znvpair                 61440     2   zfs,zcommon

~~openjdk 18-ea 2022-03-22~~zavl                      16384     1   zfs

~~OpenJDK Runtime Environment (build 18-ea+36-Ubuntu-~~icp                     221184     1)  zfs

~~OpenJDK 64-Bit Server VM (build 18-ea+36-Ubuntu-1~~spl                       77824     6   zfs, ~~mixed mode~~icp, ~~sharing)~~zzstd,znvpair,zcommon,zavl|}

~~<ol start="3" style="list-style-type: lower-alpha;"><li>Edit~~ In Debian12, the ~~'''hello_world~~default version of zfs is 2.~~java'''~~ 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 ~~Jave version</li></ol>~~kernel header file before installation.

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~vim hello_world.java~~sudo apt install -y zfsutils-linux zfs-dkms'''|}

~~public class hello_world~~

{=== Methods of creating ZFS pools ===

~~public static void main(String[] args)~~{| class="wikitable" style="background-color:#ffffdc;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.'''

{'''The following content is demonstrated based on the development board connected to an NVMe SSD and a USB flash drive.'''</big>|}

~~System~~# First, we can use the '''lsblk''' command to view all storage devices on the development board.~~out~~The current development board is connected to an NVMe SSD and a U disk.~~println("Hello World!");~~The output is as follows:

}::[[File:pi3b-img369.png]]

<ol start="2" style="list-style-type: decimal;"><li>Then enter the following command to create a ZFS pool, including two storage devices, NVMe SSD and U disk</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''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>

[[File:pi3b-img370.png]]</ol><ol start="4" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~compile and run~~ execute '''df -h'~~hello_world.java~~'' to see that '''pool1''' is mounted to the '''/pool1'''directory</li>{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''df -h''' <~~/ol~~br>

~~orangepi@orangepi:~$ '''javac hello_world.java'''~~Filesystem                 Size     Used Avail Use% Mounted on

~~orangepi@orangepi:~$ '''java hello_world'''~~tmpfs                    1.6G     18M 1.6G 2% /run

~~Hello World!~~/dev/mmcblk0p2     29G     6.0G 22G 22% /

tmpfs                    7.7G     46M 7.7G 1% /dev/shm <~~span id="qt-installation-method"></span~~br>~~== QT installation method ==~~

~~# Use the following script to install QT5 and QT Creator~~tmpfs                    5.0M     4.0K 5.0M 1% /run/lock

~~orangepi@orangepi:~$ '''install_qt~~tmpfs                    7.~~sh'''~~7G     944K 7.7G 1% /tmp

~~<ol start="2" style="list-style-type: decimal~~/dev/mmcblk0p1     1022M   ">~~<li>The QT version number will be automatically printed after installation<ol style="list-style-type: lower-alpha~~ ">~~<li>Ubuntu20.04 comes with QT version '''5.~~115M 908M 12~~.8'''<~~% /~~li>~~boot <~~/ol></li></ol~~br>

~~orangepi@orangepi:~$ '''install_qt~~/dev/zram1                 188M     4.~~sh'''~~5M 169M 3% /var/log

tmpfs                    1.6G     80K 1.~~....~~6G 1% /run/user/1000

~~QMake version 3~~'''pool1                    489G     9.3M 489G 1% /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="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''mount | grep pool1'''

~~Using Qt version~~ pool1 on /pool1 type '''zfs'''~~5.12.8~~(rw,xattr,noacl)|}</ol><ol start="6" style="list-style-type: decimal;"><li>Then we can test copying a file to the ZFS pool</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ ''' in sudo cp -v /usr/~~lib~~local/test.mp4 /pool1/~~aarch64-linux-gnu~~'''

'/usr/local/test.mp4' -> '/pool1/test.mp4'|}</ol ~~start~~>~~<li>Ubuntu22.04 comes with QT version '''5.15.3'''~~</~~li></ol~~span>

~~orangepi@orangepi:~$ '''install_qt.sh'''~~=== Test the data deduplication function of ZFS ===

~~......~~# The data deduplication function of ZFS is disabled by default, we need to execute the following command to enable it::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo zfs set dedup=on pool1'''|}

~~QMake version 3.1~~<ol start="2" style="list-style-type: decimal;"><li>Then do a simple test, first enter pool1, and then execute the following command to generate a random file with a size of 1G</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''cd /pool1/'''

~~Using Qt version~~ root@orangepi:/pool1$ '''5sudo dd if=/dev/urandom of=test.~~15.3~~1g bs=1M count=1024''' ~~in /usr/lib/aarch64-linux-gnu~~

~~<ol start="3" style="list-style-type: lower-alpha;"><li>Debian11 comes with QT version '''5.15.2'''</li></ol>~~1024+0 records in

~~orangepi@orangepi:~$ '''install_qt.sh'''~~1024+0 records out

1073741824 bytes (1.1 GB, 1.0 GiB) copied, 5.04367 s, 213 MB/s|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then use the following command to copy 1000 random files of size 1G</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/pool1$ '''for ((i=0; i<1000; i++)); do sudo cp test.1g $i.test.1g; done'''|}~~QMake version 3.1~~</ol><ol start="4" style="list-style-type: decimal;">~~Using Qt version~~ <li>Then use '''~~5.15.2~~du -lh''' to see that there are currently 1002G of data in the pool, but in fact the size of the ZFS pool is only '''504GB''' (the total capacity of SSD+U disk), which cannot hold such a large amount of data</~~usr~~li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/~~lib/aarch64~~pool1$ '''du -~~linux-gnu~~lh'''

1002G|}</ol><ol start="45" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Debian12 comes with QT version~~ Then use the '''~~5.15.8~~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.</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''install_qt~~pi3b-img371.~~sh'''~~png]]</ol>

~~......~~=== Test the data compression function of ZFS ===

~~QMake version 3.1~~# Because the stored data is different, the disk space saved by compression will also be different, so we choose to compress relatively large plain text files for compression testing, and execute the following commands to pack the '''/var/log/''' and '''/etc/''' directories into a tarball

~~Using Qt version~~ ::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~5.15.8~~cd /pool1/''' ~~in /usr/lib/aarch64-linux-gnu~~

~~<ol start="3" style="list-style-type~~root@orangepi: ~~decimal;"><li>Then you can see the QT Creator launch icon in~~ /pool1$ '''~~Applications~~sudo tar -cf text.tar /var/log/ /etc/'''~~</li></ol>~~|}

~~[[File~~<ol start="2" style="list-style-type:~~pi3b~~decimal;"><li>Then the file size that can be seen through the '''ls -~~img327.png|576x270px]]~~lh''' command and the space occupied in the ZFS pool are both '''27M'''</li>

~~QT Creator can also be opened using~~ [[File:pi3b-img372.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then we enable compression in the ZFS pool pool1</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/pool1$ '''sudo zfs set compression=lz4 pool1'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then execute the following commandagain to package the '''/var/log/''' and '''/etc/''' directories into a tar package</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/pool1$ '''sudo tar -cf text.tar /var/log/ /etc/'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>At this time, you can see that the size of the '''text.tar''' file is still 27M, but it only occupies 9.47M in the ZFS pool, indicating that the file is compressed</li>

~~orangepi@orangepi~~[[File:~~~$ '''qtcreator'''~~pi3b-img373.png]]</ol>

~~'''During the startup of QT~~ == How to shut down and ~~QT applications, if~~ restart the ~~following error is displayed, ignore it. This error has no impact on application running.'''~~development board ==

# 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 '''~~libGL error: failed to create dri screen~~poweroff'''command to shut down the Linux system of the development board before powering off. Then unplug the power again.

::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~libGL error: failed to load driver: rockchip~~sudo poweroff'''|}

<ol start="2" style="list-style-type: decimal;"><li>In addition, the development board is equipped with a switch button, and you can also '''~~libGL error: failed to create dri screen~~short press'''the switch button on the development board to shut down.</li>

~~'''libGL error~~[[File: ~~failed to load driver: rockchip'''~~pi3b-img374.png]]

~~<ol start~~{| class="4wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~The interface~~ '''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 ~~QT Creator is opened is as follows</li>~~clicking the Shut Down option.'''</olbig>

[[File:pi3b-~~img328~~img375.png|~~418x222px~~center]]|}</ol><ol start="3" style="list-style-type: decimal;"><li>Short press the switch button on the development board after shutting down to start up.</li>

[[File:pi3b-img374.png]]</ol><ol start="54" style="list-style-type: decimal;"><li~~><p~~>The ~~QT Creator version~~ command to restart the Linux system is ~~shown below~~</pli>~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>The default version of QT Creator in~~ |-| orangepi@orangepi:~$ '''sudo''' '''~~Ubuntu20.04~~reboot''' ~~is as follows</li>~~|}</ol><~~/li~~span id="linux-sdkorangepi-build-instructions"></olspan>

~~[[File:pi3b~~= '''Linux SDK——orangepi-~~img329.png|419x224px]]~~build instructions''' =

<~~ol start~~span id="~~2" style="list-style~~compilation-~~type: lower~~system-~~alpha;~~requirements">~~<li>The default version of QT Creator in '''Ubuntu22.04''' is as follows~~</~~li></ol~~span>== Compilation system requirements ==

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-| <big>'''We can cross-~~img330~~compile the Linux image of the development board on the x64 computer, or compile the Linux image of the development board on the Ubuntu22.04 system of the development board, please choose one according to your preference.~~png|443x237px]]~~'''

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

~~<li>The default version of QT Creator in '''Debian11''' is as follows</li></ol>~~

~~[[File:pi3b~~'''If you use orangepi-~~img331~~build to compile the Linux image in the Ubuntu22.~~png~~04 system of the development board, please do a good job of cooling (especially when the SSD starts). If the heat dissipation is not done well, it is prone to the error of file system runaway.'''</big>|~~444x238px]]~~}

<~~ol start~~span id="~~4" style="list~~compile-with-the-ubuntu22.04-system-of-~~style~~the-~~type: lower~~development-~~alpha;~~board"><li/span>~~The default version~~ === Compile with the Ubuntu22.04 system of ~~QT Creator in '''Debian12''' is as follows</li></ol>~~the development board ===

~~[[File:pi3b~~# The Linux SDK, namely '''orangepi-~~img332~~build''', supports running on the '''Ubuntu 22.04''' of the development board (other systems have not been tested), so before downloading orangepi-build, please first ensure that the Ubuntu version installed on the development board is Ubuntu 22.04. The command to check the Ubuntu version installed on the development board is as follows. If the Release field does not display '''22.04''', it means that the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operations.~~png|449x277px]]~~

~~<ol start~~::{| class="6wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then set QT~~|-~~<ol style="list-style-type~~| orangepi@orangepi: ~~lower-alpha;"><li>First open '''Help~~~$ '''lsb_release -~~>''~~a'~~About Plugins...~~''~~'</li></ol></li></ol>~~

~~[[File:pi3b-img333~~No LSB modules are available.~~png|573x164px]]~~

~~<ol start="2" style="list-style-type~~Distributor ID: ~~lower-alpha;"><li>Then remove the check box for '''ClangCodeModel'''</li></ol>~~Ubuntu

~~[[File~~Description:~~pi3b-img334~~Ubuntu 22.~~png|408x254px]]~~04.1 LTS

Release: '''<~~ol start="3"~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">22.04<li/span>~~'''Restart QT Creator after the Settings are complete~~'''~~</li><li>Then make sure that QT Creator uses the GCC compiler, if the default is Clang, change it to GCC</li></ol>~~

~~'''Debian12 Please skip this step.'''~~Codename: jammy|}

~~[[File~~<ol start="2" style="list-style-type: decimal;"><li>'''Since the source codes such as the kernel and U-~~img335~~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.~~png|576x315px]]~~'''</li></ol>

~~[[File:pi3b~~

~~<ol start~~=~~"7" style~~=~~"list-style-type: decimal;"><li>You can then open a sample code</li></ol>~~= Compile with x64 Ubuntu22.04 computer ===

~~[[File:pi3b~~# The Linux SDK, '''orangepi-~~img337~~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.~~png|575x312px]]~~

~~<ol start~~::{| class="8wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Clicking on the example code will automatically open the corresponding instruction document, you can carefully read the instructions</li></ol>~~|-| test@test:~$ '''lsb_release -a'''

~~[[File:pi3b-img338~~No LSB modules are available.~~png|576x218px]]~~

~~<ol start="9" style="list-style-type~~Distributor ID: ~~decimal;"><li>Then click '''Configure Project'''</li></ol>~~Ubuntu

~~[[File~~Description:~~pi3b-img339~~Ubuntu 22.~~png|575x304px]]~~04 LTS

Release: '''<~~ol start="10"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>Then click the green triangle in the lower left corner to compile and run the sample code</li>~~22.04</olspan>'''

~~[[File~~Codename:~~pi3b-img340.png~~jammy|~~575x312px]]~~}

<ol start="112" style="list-style-type: decimal;"><li>~~After waiting for a period of time~~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 ~~interface shown~~ 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 ~~following figure will pop up~~WSL virtual machine, ~~which indicates~~ so it cannot be guaranteed that QT orangepi-build can ~~compile and run~~ be used normallyin WSL.</li><li>The download address of the installation image of Ubuntu 22.04 '''amd64''' version is:</olp></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-~~img341~~releases/22.~~png|576x308px]~~04/ubuntu-22.04-desktop-amd64.iso''']

~~<ol start="12" style="list-style-type: decimal;"><li>Reference documents</li></ol>~~Or

'''https://~~wiki~~repo.qthuaweicloud.iocom/~~Install_Qt_5_on_Ubuntu~~ubuntu-releases/22.04/ubuntu-22.04.1-desktop-amd64.iso'''|}</ol><ol start="4" style="list-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="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://~~download~~mirrors.tuna.tsinghua.qtedu.iocn/help/ubuntu/'''|}</~~archive~~ol><ol start="2" style="list-style-type: lower-alpha;"><li>Note that the Ubuntu version needs to be switched to 22.04</~~qtcreator~~li>

~~https~~[[File:pi3b-img376.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The content of the '''/etc/apt/~~download~~sources.~~qt.io/archive~~list''' file that needs to be replaced is</qtli>

~~<~~| test@test:~$ '''sudo mv /etc/apt/sources.list /etc/apt/~~span>== ROS Installation Method ==~~sources.list.bak'''

~~<~~test@test:~$ '''sudo vim /etc/apt/~~span>=== How to install ROS 1 Noetic on Ubuntu 20~~sources.~~04 ===~~list'''

# ~~The current active version of ROS 1 is as follows~~By default, the ~~recommended version~~ source image is ~~'''Noetic Ninjemys'''~~commented to improve the speed of apt update, you can uncomment it yourself if necessary

~~[[File~~deb https:~~pi3b-img342~~//mirrors.~~png|345x235px]]~~tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse

~~[[File~~# deb-src https:~~pi3b-img343~~//mirrors.tuna.tsinghua.edu.~~png|576x210px]]~~cn/ubuntu/ jammy main restricted universe multiverse

~~[http~~deb https://~~docs~~mirrors.~~ros~~tuna.~~org/ http:~~tsinghua.edu.cn/ubuntu/~~docs.ros.org]~~jammy-updates main restricted universe multiverse

~~'''~~# deb-src https://~~wiki~~mirrors.~~ros~~tuna.~~org~~tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse</~~Distributions'''~~p>

~~<ol start="2" style="list-style-type~~deb https: ~~decimal;"><li>The official installation document link of ROS 1 '''Noetic Ninjemys''' is as follows:<~~/~~li><~~/~~ol>~~mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse

~~[http~~# deb-src https://~~wiki~~mirrors.~~ros~~tuna.~~org/noetic/Installation/Ubuntu '''http://wiki~~tsinghua.~~ros~~edu.~~org~~cn/~~noetic~~ubuntu/~~Installation~~jammy-backports main restricted universe multiverse</~~Ubuntu''']~~p>

~~<ol start="3" style="list-style-type~~deb https: ~~decimal;"><li>In the official installation document of ROS '''Noetic Ninjemys''', Ubuntu recommends using Ubuntu20~~//mirrors.~~04, so please make sure that the system used by the development board is '''Ubuntu20~~tuna.~~04 desktop system'''<~~tsinghua.edu.cn/~~li><~~ubuntu/~~ol>~~jammy-security main restricted universe multiverse

~~http~~# deb-src https://~~wiki~~mirrors.~~ros~~tuna.~~org~~tsinghua.edu.cn/ubuntu/~~noetic~~jammy-security main restricted universe multiverse</~~Installation~~p>

~~[[File:pi3b-img344.png|312x176px]]~~

<~~ol start="4" style="list-style~~p># Pre-~~type: decimal;"><li>Then use the script below~~ release software source, not recommended to ~~install ros1</li>~~enable</olp>

~~orangepi@orangepi3b~~# deb https:~~~$ '''install_ros~~//mirrors.~~sh ros1'''~~tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse

# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse|}</ol><ol start="54" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Before using~~ After the ~~ROS tool~~replacement, you ~~first~~ need to ~~initialize rosdep~~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 ~~then you~~ U-boot are stored on GitHub, it is very important to ensure that the computer can ~~quickly install some system dependencies and some core components in ROS~~ download codes from GitHub normally when compiling the ~~source code~~image.'''</li></ol></li></ol>

~~'''Note that running~~ == Get the ~~following command needs to ensure that the development board can access github normally, otherwise an error will be reported due to network problems.'''~~source code of Linux sdk ==

~~'''The install_ros.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 span>=== Download orangepi-build from github ~~normally, and then manually run the following Order.'''~~===

~~'''https://raw~~# The Linux sdk actually refers to the code of orangepi-build.~~githubusercontent~~orangepi-build is modified based on the armbian build system.~~com/ros/rosdistro/master/rosdep/osx~~Using orangepi-~~homebrew~~build, multiple versions of Linux images can be compiled.~~yaml'''~~First download the code of orangepi-build, the command is as follows:

::{| class="wikitable" style="width:800px;" |-| test@test:~$ '''~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml~~sudo apt-get update'''

test@test:~$ '''~~ERROR: error loading sources list:~~sudo apt-get install -y git'''

test@test:~$ '''git clone https://github.com/orangepi-xunlong/orangepi-build.git -b next'''|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the Orange Pi 3B development board needs to download the source code of the next branch of orangepi-build. The ~~read operation timed out~~above git clone command needs to specify the branch of the orangepi-build source code as next.'''</big>

~~orangepi@orangepi:~$ '''source /opt/ros/noetic/setup.bash'''~~<div class="figure">

~~orangepi@orangepi~~[[File:~~~$ '''sudo rosdep init'''~~pi3b-img377.png|center]]

~~Wrote~~ </~~etc/ros/rosdep/sources~~div>|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Downloading the orangepi-build code through the git clone command does not require entering the user name and password of the github account (the same is true for downloading other codes in this manual), if the Ubuntu PC prompts the user to enter the github account after entering the git clone command The name and password are usually entered incorrectly in the address of the orangepi-build warehouse behind the git clone.~~list~~Please check the spelling of the command carefully, instead of thinking that we forgot to provide the username and password of the github account.d'''</~~20-default.list~~big>|}

~~Recommended~~<ol start="2" style="list-style-type: ~~please run~~decimal;"><li>The u-boot and Linux kernel versions currently used by the development board are as follows</li>

~~rosdep update~~{| class="wikitable" style="width:800px;text-align: center;"|-|'''branch'''|'''u-boot version'''|'''Linux Kernel version'''|-|'''legacy'''|'''u-boot 2017.09'''|'''Linux5.10'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The branch mentioned here is not the same thing as the branch of the orangepi-build source code, please do not confuse it. This branch is mainly used to distinguish different kernel source code versions.'''

'''Currently, the Linux5.10 bsp kernel provided by RK is defined as the legacy branch. If the mainline kernel is supported in the future, a current branch will be added.'''</big>|}</ol><ol start="3" style="list-style-type: decimal;"><li>orangepi-build will contain the following files and folders after downloading<ol style="list-style-type: lower-alpha;"><li>'''build.sh''': Compile the startup script</li><li>'''external''': Contains the configuration files needed to compile the image, specific scripts, and the source code of some programs, etc.</li><li>'''LICENSE''': GPL 2 license file</li><li>README.md: orangepi-build documentation</li><li>'''scripts''': General script for compiling Linux images</li>{| class="wikitable" style="width:800px;" |-| test@~~orangepi~~test:~/orangepi-build$ '''~~rosdep update~~ls'''

~~reading~~ '''build.sh      external      LICENSE      README.md      scripts'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If you downloaded the code of orangepi-build from github, after downloading, you may find that orangepi-build does not contain the source code of u-boot and Linux kernel, nor does u-boot and Linux kernel need to use cross-compilation tools Chain, this is normal, because these things are stored in other separate github warehouses or some servers (the addresses will be detailed below). orangepi-build will specify the address of u-boot, Linux kernel and cross-compilation toolchain in ~~sources list data from~~ 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>|}</~~etc~~ol></~~ros~~li></~~rosdep~~ol></~~sources.list.d~~span>

~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx~~=== Download the cross-~~homebrew.yaml~~compilation toolchain ===

~~Hit https~~{| class="wikitable" style="background-color:~~//raw~~#ffffdc;width:800px;" |-| <big>'''The cross-compilation toolchain will only be downloaded when the orangepi-build compilation image is used on an x64 computer. Compiling the Linux image of the development board in the Ubuntu22.~~githubusercontent~~04 of the development board will not download the cross-compilation toolchain.~~com~~At this time, orangepi-build/~~ros~~toolchains will be an empty folder.'''</~~rosdistro/master/rosdep/base.yaml~~big>|}

~~Hit https://raw~~# When orangepi-build runs for the first time, it will automatically download the cross-compilation toolchain and put it in the '''toolchains''' folder.~~githubusercontent~~Every time after running the build.~~com/ros/rosdistro/master/rosdep/python~~sh script of orangepi-build, it will check whether the cross-compilation toolchain in '''toolchains''' exists , if it does not exist, the download will be restarted, if it exists, it will be used directly, and the download will not be repeated.~~yaml~~

~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml~~<div class="figure">

~~Hit https~~:~~//raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte~~:[[File:pi3b-img378.~~yaml~~png]]

~~Query rosdistro index~~ </div><ol start="2" style="list-style-type: decimal;"><li>The image URL of the cross-compilation toolchain in China is the open source software image site of Tsinghua University</li>{| class="wikitable" style="width:800px;" |-| '''https://~~raw~~mirrors.~~githubusercontent~~tuna.~~com~~tsinghua.edu.cn/armbian-releases/~~ros~~_toolchain/~~rosdistro~~'''|}</~~master~~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</~~index~~li>{| class="wikitable" style="width:800px;" |-~~v4.yaml~~| test@test:~/orangepi-build$ '''ls toolchains/'''

~~Skip end~~gcc-ofarm-~~life distro "ardent"~~11.2-2022.02-x86_64-aarch64-none-linux-gnu

~~Skip end~~gcc-ofarm-~~life distro "bouncy"~~11.2-2022.02-x86_64-arm-none-linux-gnueabihf

~~Skip end~~gcc-ofarm-~~life distro "crystal"~~9.2-2019.12-x86_64-aarch64-none-linux-gnu

~~Skip end~~gcc-ofarm-~~life distro "dashing"~~9.2-2019.12-x86_64-arm-none-linux-gnueabihf

~~Skip end~~gcc-oflinaro-~~life distro "eloquent"~~4.9.4-2017.01-x86_64_arm-linux-gnueabi

~~Add distro "foxy"~~gcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabihf

~~Add distro "galactic"~~gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu

~~Skip end~~gcc-oflinaro-~~life distro "groovy"~~7.4.1-2019.02-x86_64_arm-linux-gnueabi

~~Add distro "humble"~~gcc-linaro-aarch64-none-elf-4.8-2013.11_linux

~~Skip end~~gcc-oflinaro-~~life distro "hydro"~~arm-linux-gnueabihf-4.8-2014.04_linux

~~Skip end~~gcc-oflinaro-~~life distro &quot~~arm-none-eabi-4.8-2014.04_linux|}</ol><ol start="4" style="list-style-type: decimal;~~indigo&quot~~"><li>The cross-compilation toolchain used to compile the Linux kernel source code is<ol style="list-style-type: lower-alpha;"><li>Linux5.10</li>~~Skip end~~{| class="wikitable" style="width:800px;" |-| '''gcc-arm-11.2-2022.02-x86_64-aarch64-ofnone-~~life distro "jade&quot~~linux-gnu'''|}</ol></li></ol><ol start="5" style="list-style-type: decimal;"><li>The cross-compilation tool chain used to compile the u-boot source code is~~Skip end~~<ol style="list-style-oftype: lower-~~life distro &quot~~alpha;~~kinetic&quot~~"><li>v2017.09</li>{| class="wikitable" style="width:800px;" |-| '''gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu'''|}</ol></li></ol>

~~Skip end~~=== orangepi-~~of-life distro "lunar"~~build complete directory structure description ===

~~Add distro~~ <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'''|}</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     kernel     LICENSE     output     README.md     scripts     toolchains     u-boot  &~~quot~~nbsp;~~melodic~~&~~quot~~nbsp;userpatches'''|}</ol>

~~Add distro "noetic"~~== Compile u-boot ==

~~Add distro "rolling"~~# Run the build.sh script, remember to add sudo permission

~~updated cache in /home~~::{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi/-build$ '''sudo .~~ros/rosdep~~/~~sources~~build.~~cache~~sh'''|}

<ol start="62" 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 normallyorangepi@orangepi:~$~~ Select '''~~test_ros.sh'''</li><li>After running the '''test_ros.sh~~U-boot package''' ~~script~~, ~~a little turtle as shown in the figure below will pop up~~then enter</li~~></ol~~>

[[File:pi3b-~~img345~~img379.png~~|575x275px|图片4~~]]

</div></ol><ol start="83" style="list-style-type: decimal;"><li>Then ~~please keep~~ select the ~~terminal window just opened at~~ model of the ~~top~~development board</li~~></ol~~>

[[File:pi3b-~~img346~~img380.png~~|576x275px|图片5~~]]

</div></ol><ol start="94" style="list-style-type: decimal;"><li>~~At this time~~Then it will start to compile u-boot, ~~press~~ and some information prompted during compilation is explained as follows<ol style="list-style-type: lower-alpha;"><li>u-boot source code version</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Compiling u-boot [ '''v2017.09''' ]|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The version of the cross-compilation toolchain</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Compiler version [ '''aarch64-linux-gnu-gcc 7.4.1''' ]|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Path to the generated u-boot deb package</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Target directory [ '''orangepi-build/output/debs/u-boot''' ]|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>The package name of the ~~direction keys on~~ 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 ~~keyboard~~ command to ~~control~~ compile u-boot, use the ~~little turtle~~ following command to ~~move up, down, left, and right~~start compiling u-boot directly without selecting through the graphical interface</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=u-boot KERNEL_CONFIGURE=no''' ]|}</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/'''

~~[[File~~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:~~pi3b~~lower-~~img347.png~~alpha;"><li>Use the following command to decompress the deb package</li>{| class="wikitable" style="width:800px;" |-|~~575x296px]]~~test@test:~/orangepi-build$ '''cd output/debs/u-boot'''

~~=== How to install ROS 2 Galactic on Ubuntu 20.04 ===~~x''' \

~~# The current active version of ROS 2 is as follows, the recommended version is~~ '''~~Galactic Geochelone~~linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb . (Note that there is a "." at the end of the command)'''

~~[[File~~test@test:~~pi3b~~~/orangepi_build/output/debs/u-~~img348.png|576x271px]]~~boot$ '''ls'''

~~[[File~~linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb '''usr'''|}</ol><ol start="2" style="list-style-type:~~pi3b~~lower-~~img349.png~~alpha;"><li>The decompressed file is as follows</li>{| class="wikitable" style="width:800px;" |-|~~575x265px]]~~test@test:~/orangepi-build/output/debs/u-boot$ '''tree usr'''

~~[http://docs.ros.org/ http://docs.ros.org]~~usr

~~'''http://docs.ros.org/en/galactic/Releases.html'''~~└── lib

~~<ol start="2" style="list~~:├── linux-~~style~~u-~~type: decimal;"><li>The link to the official ROS 2 '''Galactic Geochelone''' installation documentation is as follows:</li></ol>~~boot-legacy-orangepi3b_1.0.0_arm64

~~'''docs~~:│ ├── idbloader.~~ros.org/en/galactic/Installation.html'''~~img

~~'''http~~:~~//docs~~│ ├── rkspi_loader.~~ros.org/en/galactic/Installation/Ubuntu-Install-Debians.html'''~~img

~~<ol start="3" style="list-style~~:│ └── u-~~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~~boot.~~sh''' script to install ros2</li></ol>~~itb

~~orangepi@orangepi~~:~~~$ '''install_ros.sh ros2'''~~└── u-boot

~~<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></ol>:├── LICENSE

~~usage~~: ~~ros2 [~~:├── orangepi-~~h] Call `ros2 <command>~~ 3b-~~h` for more detailed usage. ...~~rk3566_defconfig

~~ros2 is an extensible command-line tool for ROS 2~~::└── platform_install.sh

~~optional arguments:~~

3 directories, 6 files|}</ol></li></ol><ol start="7" style="list-style-type: decimal;"><li>When the orangepi-bulid compilation system compiles the u-hboot 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-~~help show this help message~~ boot source code, you first need to turn off the download and ~~exit~~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>

~~Commands:~~Set the IGNORE_UPDATES variable in userpatches/config-default.conf to "yes"

~~action Various action related sub~~{| class="wikitable" style="width:800px;" |-~~commands~~| test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''

~~bag Various rosbag related sub~~IGNORE_UPDATES="'''yes'''"|}</ol><ol start="8" style="list-~~commands~~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>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''cd output/debs/u-boot'''

~~component Various component related sub~~test@test:~/orangepi_build/output/debs/u-~~commands~~boot$ '''scp \'''

~~daemon Various daemon related sub~~'''linux-~~commands~~u-boot-legacy-orangepi3b_1.0.0_arm64.deb root@192.168.1.xxx:/root'''|}</ol><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>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''apt purge -y linux-u-boot-orangepi3b-legacy'''|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Install the new u-boot deb package just uploaded</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''dpkg -i''' '''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb'''|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then run the nand-sata-install script</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''nand-sata-install'''|}</ol><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>

~~doctor Check ROS setup and other potential issues~~[[File:pi3b-img381.png]]</ol><ol start="6" style="list-style-type: lower-alpha;"><li>After pressing the Enter key, a Warning will pop up first</li>

~~interface Show~~ [[File:pi3b-img382.png]]</ol><ol start="7" style="list-style-type: lower-alpha;"><li>Press the Enter key again to start updating u-boot, and the following information ~~about ROS interfaces~~will be displayed after the update is completed</li>

~~launch Run a launch~~ [[File:pi3b-img383.png]]</ol><ol start="8" style="list-style-type: lower-alpha;"><li>Then you can restart the development board to test whether the modification of u-boot takes effect</li></ol></li></ol><ol start="9" style="list-style-type: decimal;"><li>Other useful information<ol style="list-style-type: lower-alpha;"><li>In the u-boot 2017.09 source code, the defconfig configuration fileused by the development board is</li>{| class="wikitable" style="width:800px;" |-| [https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/configs/orangepi_5_defconfig '''orangepi-build/u-boot/v2017.09-rk3588/configs/orangepi-3b-rk3566_defconfig''']|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>In the u-boot 2017.09 source code, the dts file used by the development board is</li>{| class="wikitable" style="width:800px;" |-| [https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/arch/arm/dts/rk3588s-orangepi-5.dts '''orangepi-build/u-boot/v2017.09-rk3588/arch/arm/dts/rk3566-orangepi-3b.dts''']|}</ol></li></ol>

~~lifecycle Various lifecycle related sub-commands~~== Compile the Linux kernel ==

~~multicast Various multicast related sub-commands~~# Run the build.sh script, remember to add sudo permission

~~node Various node related sub~~::{| class="wikitable" style="width:800px;" |-~~commands~~| test@test:~/orangepi-build$ '''sudo ./build.sh'''|}

~~param Various param related sub~~<ol start="2" style="list-~~commands~~style-type: decimal;"><li>Select '''Kernel package''', then enter</li>

~~pkg Various package related sub-commands~~<div class="figure">

~~run Run a package specific executable~~[[File:pi3b-img384.png]]

~~security Various security related sub~~</div></ol><ol start="3" style="list-~~commands~~style-type: decimal;"><li>Then select the model of the development board</li>

~~service Various service related sub-commands~~<div class="figure">

~~topic Various topic related sub~~[[File:pi3b-~~commands~~img380.png]]

~~wtf Use `wtf` as alias~~ </div></ol><ol start="4" style="list-style-type: decimal;"><li>Then it will prompt whether to ~~`doctor`~~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>

~~Call `ros2 &lt~~[[File:pi3b-img385.png]]</ol><ol start="5" style="list-style-type: decimal;~~command> -h` for more detailed usage~~"><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 start="6" style="list-style~~[[File:pi3b-~~type: decimal;"><li>Then you can use the '''test_ros.sh''' script to test whether ROS 2 is installed successfully~~img386. ~~If you can see the following print, it means that ROS 2 can run normally</li></ol>~~png]]

~~orangepi~~<ol style="list-style-type: lower-alpha;"><li>If you do not need to modify the configuration options of the kernel, when running the build.sh script, pass in '''KERNEL_CONFIGURE=no''' to temporarily block the pop-up kernel configuration interface</li>{| class="wikitable" style="width:800px;" |-| test@~~orangepi3b~~test:~/orangepi-build$ '''~~test_ros~~sudo ./build.shKERNEL_CONFIGURE=no'''|}</ol><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>

[~~INFO]~~ [~~1671174101~~File:pi3b-img387.~~200091527~~png] ~~[talker~~]</ol></ol><ol start="6" style="list-style-type: ~~Publishing~~decimal;"><li>Part of the information prompted when compiling the kernel source code is as follows<ol style="list-style-type: ~~'Hello World~~lower-alpha;"><li>The version of the Linux kernel source code</li>{| class="wikitable" style="width: 1'800px;" |-| [~~INFO~~o.k. ] Compiling current kernel [~~1671174101~~'''5.10.~~235661048~~160''' ] |}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The version of the cross-compilation toolchain used</li>{| class="wikitable" style="width:800px;" |-| [~~listener~~o.k. ]~~: I heard:~~ Compiler version [~~Hello World:~~ '''aarch64-none-linux-gnu-gcc 11.2.1''' ]|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The configuration file used by the kernel by default and the path where it is stored</li>{| class="wikitable" style="width:800px;" |-| [~~INFO~~o.k. ] Using kernel config file [~~1671174102~~'''config/kernel/linux-rockchip-rk356x-legacy.~~199572327~~config''' ] |}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>The path of the deb package related to the kernel generated by compiling</li>{| class="wikitable" style="width:800px;" |-| [~~talker~~o.k. ] Target directory [ '''orangepi-build/output/debs/''' ]|}</ol><ol start="5" style="list-style-type: ~~Publishing~~lower-alpha;"><li>The package name of the compiled kernel image deb package</li>{| class="wikitable" style="width: 800px;" |-| [ o.k. ] File name [ '~~Hello World~~''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb''' ]|}</ol><ol start="6" style="list-style-type: 2'lower-alpha;"><li>The time used for compilation</li>{| class="wikitable" style="width:800px;" |-| [~~INFO~~o.k. ] Runtime [~~1671174102~~'''5 min''' ]|}</ol><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>{| class="wikitable" style="width:800px;" |-| [ o.k.~~204196299~~] Repeat Build Options [~~listener~~'''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=kernel KERNEL_CONFIGURE=no''' ]|}</ol></li></ol><ol start="7" style="list-style-type: decimal;"><li>View the deb package related to the kernel generated by compilation<ol style="list-style-type: ~~I heard~~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>{| class="wikitable" style="width: ~~[Hello World~~800px;" |-| test@test: 2]~/orangepi-build$ '''ls output/debs/linux-*'''

~~[INFO] [1671174103~~output/debs/linux-dtb-legacy-rockchip-rk356x_1.~~199580322] [talker]: Publishing: 'Hello World: 3'~~0.0_arm64.deb output/debs/linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb

~~[INFO] [1671174103~~output/debs/linux-headers-legacy-rockchip-rk356x_1.~~204019965] [listener]~~0.0_arm64.deb|}</ol></li></ol><ol start="8" style="list-style-type: decimal;"><li>The files contained in the generated Linux-image deb package are as follows<ol style="list-style-type: ~~I heard~~lower-alpha;"><li>Use the following command to decompress the deb package</li>{| class="wikitable" style="width: ~~[Hello World~~800px;" |-| test@test: 3]~/orangepi-build$ '''cd output/debs'''

~~<ol start="7" style="list-style-type~~test@test: ~~decimal;"><li>Run the following command to open rviz2<~~~/~~li><~~orangepi_build/~~ol>~~output/debs$ '''mkdir test'''

~~orangepi~~test@~~orangepi~~test:~/orangepi_build/output/debs$ '''~~source /opt/ros/galactic/setup.bash~~cp \'''

~~orangepi@orangepi:~$~~ '''~~ros2 run rviz2 rviz2~~linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb test/'''

~~<div class="figure">~~test@test:~/orangepi_build/output/debs$ '''cd test'''

~~[[File~~test@test:~~pi3b~~~/orangepi_build/output/debs/test$ '''dpkg -~~img350.png|576x324px|1]]~~x \'''

~~</div><ol start="8" style="list~~'''linux-~~style~~image-~~type: decimal;"><li>For the usage of ROS, please refer to the documentation of ROS 2</li></ol>~~legacy-rockchip-rk356x_1.0.0_arm64.deb .'''

~~http~~test@test:~/orangepi_build/~~docs.ros.org~~output/endebs/~~galactic/Tutorials.html~~test$ '''ls'''

~~<ol start="2" style="list-~~humble~~style-ontype: lower-~~ubuntu-22.04~~alpha;"><li>The decompressed file is as follows</~~span~~li>{| class="wikitable" style=~~= How to install ROS~~ "width:800px;" |-| test@test:~/orangepi-build/output/debs/test$ '''tree -L 2 ~~Humble on Ubuntu 22.04 ==='''

~~# Use the '''install_ros~~.~~sh''' script to install ros2~~

~~orangepi@orangepi:~$ '''install_ros.sh ros2'''~~├── boot

~~<ol start="2" style="list~~│ ├── config-~~style~~5.10.160-~~type: decimal;"><li>The '''install_ros.sh''' script will automatically run the '''ros2~~ rockchip-~~h''' command after installing ros2. If you can see the following print, it means that the ros2 installation is complete</li></ol>~~rk356x

~~usage: ros2 [~~│ ├── System.map-~~h] Call `ros2 <command> -h` for more detailed usage. .~~5.10.160-rockchip-rk356x

~~ros2 is an extensible command~~│ └── vmlinuz-~~line tool for ROS 2~~5.10.160-rockchip-rk356x

~~optional arguments:~~├── etc

~~-h, --help show this help message and exit~~│ └── kernel

~~Commands:~~├── lib

~~action Various action related sub-commands~~│ └── modules

~~bag Various rosbag related sub~~├── linux-~~commands~~image-legacy-rockchip-rk356x_1.0.0_arm64.deb

~~component Various component related sub-commands~~└── usr

~~daemon Various daemon related sub-commands~~:├── lib

~~doctor Check ROS setup and other potential issues~~:└── 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>

~~interface Show information about ROS interfaces~~Set the IGNORE_UPDATES variable in '''userpatches/config-default.conf''' to "yes"

~~launch Run a launch file~~{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''

~~lifecycle Various lifecycle related sub~~IGNORE_UPDATES="'''yes'''"|}</ol><ol start="10" style="list-~~commands~~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'''

~~multicast Various multicast related sub~~test@test:~/orangepi-~~commands~~build/output/debs$ '''scp \'''

~~node Various node~~ '''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb root@192.168.1.xxx:/root'''|}</ol><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>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''apt purge -y linux-image-legacy-rockchip-rk356x'''|}</ol><ol start="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:~# '''dpkg -i linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb'''|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then restart the development board, and then check whether the kernel-related ~~sub~~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 the kernel configuration file is as follows, please do not go to the kernel source code to find the kernel configuration file used by the development board</li>{| class="wikitable" style="width:800px;" |-| [https://github.com/orangepi-xunlong/orangepi-build/blob/next/external/config/kernel/linux-rockchip-rk3588-legacy.config '''orangepi-build/external/config/kernel/linux-rockchip-rk356x-legacy.config''']|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The location of the dts file used by the development board is</li>{| class="wikitable" style="width:800px;" |-| [https://github.com/orangepi-xunlong/linux-orangepi/blob/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5.dts '''orangepi-build/kernel/orange-pi-5.10-rk35xx/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dts''']|}</ol></li></ol>

~~param Various param related sub-commands~~== Compile rootfs ==

~~pkg Various package related sub-commands~~# Run the build.sh script, remember to add sudo permission

~~run Run a package specific executable~~::{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''sudo ./build.sh'''|}

~~security Various security related sub~~<ol start="2" style="list-~~commands~~style-type: decimal;"><li>Select '''Rootfs and all deb packages''', then enter</li>

~~service Various service related sub-commands~~ ~~topic Various topic related sub-commands~~ ~~wtf Use `wtf` as alias to `doctor`~~<div class="figure">

~~Call `ros2 <command>~~ [[File:pi3b-~~h` for more detailed usage~~img388.png]]

</div></ol>

<li>Then ~~you can use~~ select the ~~'''test_ros.sh''' script to test whether ROS 2 is installed successfully. If you can see~~ model of the ~~following print, it means that ROS 2 can run normally~~development board</li~~></ol~~>

~~orangepi@orangepi3b:~$ '''test_ros.sh'''~~<div class="figure">

[~~INFO]~~ [~~1671174101~~File:pi3b-img380.~~200091527~~png] ~~[talker~~]~~: Publishing: 'Hello World: 1'~~

~~[INFO] [1671174101.235661048] [listener]~~</div></ol><ol start="4" style="list-style-type: ~~I heard: [Hello World: 1]~~decimal;"><li>Then select the type of rootfs</li>

[~~INFO]~~ [~~1671174102~~File:pi3b-img389.~~199572327~~png] ~~[talker~~]</ol><ol start="5" style="list-style-type: ~~Publishing~~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''~~Hello World: 2~~'Indicates a image with a desktop, which is relatively large</li>

~~[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]~~<div class="figure">

[~~INFO]~~ [~~1671174103~~File:pi3b-img390.~~199580322~~png] ~~[talker~~]~~: Publishing: 'Hello World: 3'~~

~~[INFO] [1671174103~~</div></ol></li></ol><ol start="6" style="list-style-type: decimal;"><li>If you are compiling the image of the server version, you can also choose to compile the Standard version or the Minimal version.~~204019965] [listener]: I heard: [Hello World: 3]~~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 start~~div class="4figure" ~~style="list-style-type: decimal;"><li>Run the following command to open rviz2</li></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''source /opt/ros/humble/setup~~pi3b-img391.~~bash'''~~png]]

~~orangepi@orangepi~~</div></ol><ol start="7" style="list-style-type:~~~$ '''ros2 run rviz2 rviz2'''~~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>

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

</div>

~~<ol start="5" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Reference documents</li></ol>~~img393.png]]

~~'''http://docs~~You can then select additional packages that need to be installed.~~ros~~Please press the Enter key to skip directly here.~~org/en/humble/index.html'''~~

[~~http~~[File:pi3b-img394.png]]</ol><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>{| 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</~~docs~~li>{| class="wikitable" style="width:800px;" |-| [ o.~~ros~~k.~~org~~] Target directory [ '''external/cache/rootfs''' ]|}</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''' ]|}</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 [ '''13 min''' ]|}</ol></enli></~~galactic~~ol><ol start="9" style="list-style-type: decimal;"><li>View the rootfs compressed package generated by compilation</~~Tutorials~~p><ol style="list-style-type: lower-alpha;"><li>'''jammy-xfce-arm64.~~html~~ f930ff6ebbac1a72108a2e100762b18f.tar.lz4'''~~http~~is the rootfs compressed package, the meaning of each field of the name is<ol style="list-style-type:none;"><li>a) '''jammy''' indicates the type of Linux distribution of rootfs</~~docs~~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.~~ros~~As long as the list of software packages installed by rootfs is not modified, this value will not change.~~org~~The compilation script will use this MD5 hash value to generate Determine whether rootfs needs to be recompiled</enp></~~humble~~li></~~Installation~~ol></~~Ubuntu~~li><li>'''jammy-~~Install~~xfce-~~Debians~~arm64.~~html~~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/''']

~~== How to install kernel header files ==~~arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4'''

~~# The Linux image released by OPi comes with the deb package of the kernel header file by default, and the storage location is '''/opt/'''~~jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.current

~~orangepi@orangepi~~jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.list|}</ol></li></ol><ol start="10" style="list-style-type:~$ decimal;"><li>If the required rootfs already exists under '''ls external/~~opt~~cache/linux-headers*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/~~opt~~cache/~~linux-headers-legacy-rockchip-rk356x_x~~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.~~x.x_arm64.deb~~</li></ol>

<~~ol start~~span id="~~2" style="list~~compile-~~style~~linux-~~type: decimal;~~image">~~<li>Use the following command to install the deb package of the kernel header file</li~~></olspan>

~~'''The name of the kernel header file deb package needs to be replaced with the actual name, please do not copy it.'''~~== Compile Linux image ==

~~orangepi@orangepi:~$ '''~~# Run the build.sh script, remember to add sudo ~~dpkg -i /opt/linux-headers-legacy-rockchip-rk356x_1.x.x_arm64.deb'''~~permission

~~<ol start~~::{| class="3wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>After installation, you can see the folder where the kernel header files are located under~~ |-| test@test:~/orangepi-build$ '''sudo ./~~usr/src~~build.sh'''~~</li></ol>~~|}

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~$ decimal;"><li>Select '''~~ls /usr/src~~Full OS image for flashing''', then enter</li>

~~linux-headers-5.10.160-rockchip-rk356x~~<div class="figure">

~~<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~~[[File: ~~lower~~pi3b-~~alpha;"><li>First write the code of the hello kernel module, as follows:</li></ol></li></ol>~~img395.png]]

~~orangepi@orangepi~~</div></ol><ol start="3" style="list-style-type:~~~$ '''vim hello.c'''~~decimal;"><li>Then select the model of the development board</li>

~~#include <linux/init.h>~~<div class="figure">

~~#include <linux/module~~[[File:pi3b-img380.~~h>~~png]]

~~static int hello_init(void)~~</div></ol><ol start="4" style="list-style-type: decimal;"><li>Then select the type of rootfs</li>

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

~~printk("Hello Orange Pi -- init\n");~~<div class="figure">

~~return 0;~~[[File:pi3b-img390.png]]

}</div></ol></li></ol><ol start="6" style="list-style-type: decimal;"><li>If you are compiling the image of the server version, you can also choose to compile the Standard version or the Minimal version. The pre-installed software of the Minimal version will be much less than that of the Standard version '''(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>

~~static void hello_exit(void)~~ {<div class="figure">

~~printk("Hello Orange Pi~~ [[File:pi3b-~~- exit\n");~~img391.png]]

~~return~~</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. 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>

}<div class="figure">

~~module_init(hello_init);~~[[File:pi3b-img392.png]]

~~module_exit(hello_exit);~~</div>[[File:pi3b-img393.png]]

~~MODULE_LICENSE("GPL");~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>Then write~~ You can then select additional packages that need to be installed. Please press the ~~Makefile for compiling the hello kernel module, as follows:</li></ol>~~ ~~orangepi@orangepi:~$ '''vim Makefile'''~~ ~~ifneq ($(KERNELRELEASE),)~~ ~~obj-m:=hello.o~~ ~~else~~ ~~KDIR :=/lib/modules/$(shell uname -r)/build~~ ~~PWD :=$(shell pwd)~~ ~~all:~~ ~~make -C $(KDIR) M=$(PWD) modules~~ ~~clean:~~ rm -f *.ko *.o *.mod.o *.mod *.symvers *.cmd *.mod.c *Enter key to skip directly here.~~order~~ ~~endif~~

[[File:pi3b-img394.png]]

</ol>

<li>Then it will start to compile the Linux image. The general process of compilation is as follows

<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 will also create desktop-related deb packages</li>

<li>Check whether the rootfs has been cached, if not, recreate the 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 images, such as pre-installing additional software packages, modifying system configuration, etc.</li>

<li>Then make an image file and format the partition, the default type is ext4</li>

<li>Then copy the configured rootfs to the mirrored partition</li>

<li>Then update initramfs</li>

<li>Finally, write the bin file of u-boot into the image through the dd command</li>

</ol>

</li>

<li>After compiling the image, the following information will be prompted

<li>The storage path of the compiled image</li>

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

|-

|

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

<li>Compilation time</li>

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

|-

|

'''[ o.k. ] Runtime [ 19 min ]'''

|}

</ol>

<li>~~Then~~ Repeat the command to compile the image, and use the ~~make~~ following command to ~~compile~~ start compiling the ~~hello kernel module. The output of~~ image directly without selecting through the ~~compilation process is as follows~~graphical interface</li>{| class="wikitable" style="width:800px;" |-| [ 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''' ]|}</ol></li></ol>

= '''~~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~~ Android 11 operating system ~~of the development board for testing.~~instructions'''=

~~[[File:pi3b~~== Supported Android versions ==

~~orangepi@orangepi~~{| class="wikitable" style="width:~$ 800px;text-align: center;"|-|'''Android version'''|'''Kernel version'''|-|'''Android 11'''|'''~~make~~Linux4.19'''|}

~~make -C /lib/modules/5.10.160~~</~~orangepi modules~~span>

~~make[1]: Entering directory '/usr/src/linux-headers-5.10.160-rockchip-rk35xx'~~== Android Function Adaptation ==

~~CC [~~{| class="wikitable" style="width:800px;text-align: center;"|-|'''Functions'''|'''Android 11'''|-|'''USB2.0x3'''|'''OK'''|-|'''USB3.0x1'''|'''OK'''|-|'''M~~] /home/orangepi/hello~~.o2 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'''~~MODPOST /home/orangepi/Module.symvers~~|-|'''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'''|}

~~CC [M]~~ </~~home/orangepi/hello.mod.o~~span>

~~LD [M] /home/orangepi/hello.ko~~== WIFI connection test method ==

~~make[1]: Leaving directory~~ # First click enter '''Setting''~~/usr/src/linux-headers-5.10.160-rockchip-rk35xx~~'

~~<ol start="4" style="list-style-type~~: ~~lower~~:[[File:pi3b-~~alpha;"><li>After compiling, the '''hello~~img396.~~ko''' kernel module will be generated</li></ol>~~png]]

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~$ decimal;"><li>Then select '''~~ls *.ko~~Network & internet'''</li>

~~hello~~[[File:pi3b-img397.kopng]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then select '''Wi-Fi'''</li>

[[File:pi3b-img398.png]]</ol><ol start="54" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Use~~ Then turn on the '''~~insmod''' command to insert the '''hello.ko~~Wi-Fi''' ~~kernel module into the kernel~~switch</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img399.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>After turning on '''~~sudo insmod hello.ko~~Wi-Fi''', if everything is normal, you can scan for nearby Wi-Fi hotspots</li>

[[File:pi3b-img400.png]]</ol><ol start="6" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~use~~ select the ~~'''demsg''' command~~ Wi-Fi you want to connect to ~~view~~ , and the ~~output of~~ password input interface shown in the ~~'''hello.ko''' kernel module. If you can see the output~~ figure below~~, it means that the '''hello.ko''' kernel module is loaded correctly.~~will pop up</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''dmesg | grep "Hello&quot~~pi3b-img401.png]]</ol><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>

[ ~~2871~~[File:pi3b-img402.~~893988~~png] ~~'''Hello Orange Pi~~ ]</ol><ol start="8" style="list-style-type: decimal;"><li>After the Wi- ~~init'''~~Fi connection is successful, the display is as shown in the figure below:</li>

[[File:pi3b-img403.png]]</ol ~~start~~>~~<li>Use the '''rmmod''' command to uninstall the '''hello.ko''' kernel module</li~~></olspan>

~~orangepi@orangepi:~$ '''sudo rmmod hello'''~~== How to use Wi-Fi hotspot ==

~~orangepi@orangepi:~$~~ # First, please make sure that the Ethernet port is connected to the network cable and can access the Internet normally# Then select '''~~dmesg | grep "Hello"~~Settings'''

::[ ~~2871~~[File:pi3b-img396.~~893988~~png]] ~~Hello Orange Pi -- init~~

~~[ 3173.800892]~~ <ol start="3" style="list-style-type: decimal;"><li>Then select '''~~Hello Orange Pi -- exit~~Network & internet'''</li>

[[File:pi3b-img397.png]]</ol><~~span id~~ol start="~~use-of-the~~4" style="list-~~raspberry~~style-~~pis-5-inch-screen~~type: decimal;"><li>Then select '''Hotspot & tethering'''</~~span~~li>~~== Use of the Raspberry PI's 5-inch screen ==~~

[[File:pi3b-img404.png]]<~~span id~~/ol><ol start="~~assembly-method-of-raspberry-pi-~~5" style="list-~~inch~~style-~~screen~~type: decimal;"><li>Then select '''Wi-Fi hotspot'''</~~span~~li>~~=== Assembly method of Raspberry PI 5-inch screen ===~~

[[File:pi3b-img405.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>~~First prepare~~ 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 ~~required accessories~~hotspot (<ol span style="~~list-style-type~~color: ~~lower-alpha;~~blue">~~<li>Raspberry PI 5~~if you need to modify the name and password of the hotspot, you need to turn off the Wi-Fi first -~~inch MIPI LCD display + touch screen</li>~~Fi hotspot before modification</olspan>)</li~~></ol~~>

~~<blockquote>~~[[File:pi3b-~~img353~~img406.png~~|306x219px~~]]</~~blockquote~~ol><ol start="27" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~15pin MIPI cable~~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~~>

~~<blockquote>~~[[File:pi3b-~~img354~~img407.png~~|276x111px~~]]</~~blockquote~~ol><ol start="28" style="list-style-type: decimal;"><li>~~Then connect~~ After the ~~15pin MIPI cable to the Raspberry PI 5-inch screen~~ connection is successful, it will be displayed as shown in the ~~way shown~~ figure below (~~note~~ the ~~orientation~~ interface of different mobile phones will be different, the specific interface is subject to the ~~insulation surface~~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-~~img355~~img408.png~~|294x160px~~]]</ol>

~~<ol start~~=~~"3" style~~=~~"list-style-type: decimal;"><li>Finally connect to the LCD interface of the Orange Pi 3B development board</li></ol>~~Bluetooth test method ==

~~[[File:pi3b-img356.png|333x199px]]~~# First click enter '''Setting'''

~~=== Open the Raspberry PI 5-inch screen configuration method ===~~img396.png]]

<ol ~~style~~start="~~list-style-type: decimal;~~2">~~<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~~decimal;"><li>~~First run '''orangepi-config''', ordinary users remember to add~~ Then select '''~~sudo~~Connected devices''' ~~permission</li></ol>~~</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img409.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then click '''~~sudo orangepi-config~~Pair new device'''to turn on Bluetooth and start scanning the surrounding Bluetooth devices</li>

[[File:pi3b-img410.png]]</ol><ol start="24" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then select~~ The searched Bluetooth devices will be displayed under '''~~System~~Available devices'''</li~~></ol~~>

[[File:pi3b-~~img357~~img411.png~~|575x272px~~]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then click the Bluetooth device you want to connect to start pairing. When the following interface pops up, please use the mouse to select the '''Pair''' option</li>

[[File:pi3b-img412.png]]</ol><ol start="36" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then select '''Hardware'''~~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-~~img358~~img413.png~~|576x266px~~]]</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</li>

[[File:pi3b-img414.png]]</ol><ol start="48" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then~~ At this time, you can use the ~~arrow keys on~~ Bluetooth of your mobile phone to send a picture to the ~~keyboard to locate~~ development board. After sending, you can see the following confirmation interface in the Android system of the ~~Rasp-7inch-touchscreen~~development board, and then ~~use~~ click '''Accept''' to start receiving the picture sent by the ~~space button to check~~mobile phone.</li~~></ol~~>

[[File:pi3b-~~img359~~img415.png~~|408x310px~~]]</ol><ol start="9" style="list-style-type: decimal;"><li>You can open the '''Download''' directory in the file manager to view the pictures received by the Android system Bluetooth of the development board</li>

[[File:pi3b-img416.png]]</ol ~~start~~>~~<li>Then select '''<Save>''' to save</li~~></olspan>

~~[[File:pi3b~~== How to use Raspberry Pi 5-~~img360.png|404x133px]]~~inch screen ==

~~<ol start~~{| class="6wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~Then select~~ '''~~<Back>~~Please make sure that the image used is the following two versions of the image:'''~~</li></ol>~~

~~[[File:pi3b-img361~~'''OrangePi3B_RK3566_Android11_lcd_v1.~~png|397x151px]]~~x.x.img'''

~~<ol start="7" style="list-style-type: lower-alpha;"><li>Then select~~ '''~~<Reboot>~~OrangePi3B_RK3566_Android11_spi-nvme_lcd_v1.x.x.img''' ~~to restart the system for the configuration to take effect~~</~~li></ol~~big>|}

# The screen needs to be assembled first, please refer to [[~~File:pi3b~~Orange Pi 3B#Use of the Raspberry PI's 5-~~img362.png~~inch screen|~~331x154px~~'''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

~~'''The above settings will eventually add the configuration of overlays=raspi~~::[[File:pi3b-~~7inch-touchscreen to /boot/orangepiEnv.txt. After setting, you can check it first. If this configuration does not exist, then there is a problem with the settings~~img417.~~'''~~png]]

~~'''If you find it troublesome to use orangepi~~<span id="pin-interface-gpio-uart-spi-~~config, you can also use the vim editor to open /boot/orangepiEnv.txt,~~ and ~~then add the configuration of overlays=raspi~~-~~7inch~~pwm-~~touchscreen is also possible.'''~~test">

~~orangepi@orangepi:~$ '''cat /boot/orangepiEnv.txt | grep "raspi"'''~~== 40pin interface GPIO, UART, SPI and PWM test ==

~~'''overlays~~=== 40pin GPIO port test ===

~~<ol start="3" style="list-style-type: decimal;"><li>After startup, you can see~~ # First click on the ~~lcd screen display as follows:</li></ol>~~wiringOP icon to open the wiringOP APP

::[[File:pi3b-~~img363~~img418.png~~|381x262px~~]]

<~~span id~~ol start="~~the~~2" style="list-~~method~~style-~~of-server-version-image-rotation-display-direction~~type: decimal;"><~~/span~~li>~~===~~ The ~~method~~ main interface of ~~server version image rotation display direction ===~~wiringOP APP is displayed as shown in the figure below, and then click the '''GPIO_TEST''' button to open the GPIO test interface</li>

~~# Add '''extraargs~~[[File:pi3b-img419.png]]</ol><ol start=~~fbcon~~"3" style=~~rotate~~"list-style-type:decimal;"><li>The GPIO test interface is shown in the ~~direction to rotate~~figure below. The two rows of '''CheckBox''' buttons on the left are in one-to-one correspondence with the 40pin pins. When the '''~~/boot/orangepiEnv.txt~~CheckBox''' ~~This line configuration can~~ button is checked, the corresponding GPIO pin will be set to '''OUT''' mode, and the ~~direction displayed by~~ pin level will be set to high level; when the ~~server version of~~ checkbox is unchecked, the ~~Linux system, where~~ GPIO pin level will be set to low level; When the ~~number after~~ '''~~fbcon=rotate:~~GPIO READALL''' button is pressed, information such as wPi number, GPIO mode, and pin level can be ~~set as:~~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>

[[File:pi3b-img420.png]]<~~!-- --~~/ol><ol start="4" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~0: normal screen (default~~ Then click the '''GPIO READALL''' button, the output information is ~~landscape)</li><li>1: Turn clockwise 90 degrees</li><li>2: Flip 180 degrees</li><li>3~~as shown in the figure below: ~~Turn clockwise 270 degrees~~</li~~></ol~~>

~~orangepi@orangepi~~[[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 '''~~sudo vim /boot/orangepiEnv.txt~~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>

~~overlays~~[[File:pi3b-img422.png]]</ol><ol start=~~lcd1~~"6" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is '''OUT''', and the pin level is high</li>

[[File:pi3b-img423.png]]</ol><ol start="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 '''~~extraargs=cma=64M fbcon=rotate:3~~0v''', it means that the low level is set successfully.</li>

[[File:pi3b-img424.png]]</ol><ol start="8" style="list-style-type: decimal;"><li>Then click the '''~~Note~~ GPIO READALL''' button, you can see that ~~if there~~ the current pin 7 mode is OUT, and the ~~line extraargs=cma=64M in /boot~~pin level is low</~~orangepiEnv.txt by default, the configuration fbcon=rotate:3 can be added after extraargs=cma=64M (separated by spaces).'''~~li>

[[File:pi3b-img425.png]]</ol ~~start~~>~~<li>Then '''restart''' the Linux system and you can see that the direction displayed on the LCD screen has been rotated~~</~~li></ol~~span>

~~~~==~~= Method of rotating display and touch direction of desktop version image~~ 40pin UART test ===

# ~~First open~~ 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 '''~~Display~~/dev/ttyS7''' ~~Settings in Linux~~and '''/dev/ttyS9''' respectively

::[[File:pi3b-~~img364~~img269.png~~|298x206px~~]]

<li>~~Then select~~ First click on the ~~direction you want~~ wiringOP icon to ~~rotate in '''Rotation'''<ol style="list-style-type: lower-alpha;"><li>'''None''': no rotation</li><li>'''Left''': rotate left 90 degrees~~open the wiringOP APP</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]]~~

[[File:pi3b-img418.png]]

</ol>

<li>~~Then~~ The main interface of wiringOP APP is displayed as shown in the figure below, and then click the '''~~Apply~~UART_TEST'''button to open the UART test interface</li>~~</ol>~~ ~~[[File:pi3b-img366.png|330x207px]]~~

[[File:pi3b-img426.png]]

</ol>

<li>~~Then select '''Keep this configuration'''~~The serial port test interface of the APP is shown in the figure below</li>~~</ol>~~ ~~[[File:pi3b-img367.png|374x210px]]~~

[[File:pi3b-img427.png]]

</ol>

<li>~~At this point,~~ Take the ~~screen display has been rotated~~test of '''UART7''' as an example below, ~~and then close~~ select the '''~~Display~~/dev/ttyS7''' ~~program</li><li>The above steps will only select~~ node in the ~~display direction~~selection box, ~~and will not rotate~~ enter the ~~direction of~~ baud rate you want to set in the ~~touch. Use~~ edit box, and then click the '''~~set_lcd_rotate.sh~~OPEN''' ~~script~~ button to ~~rotate~~ open the ~~direction of the touch~~/dev/ttyS7 node. After the ~~script~~ opening is ~~set~~successful, ~~it will automatically restart~~the '''OPEN''' button becomes unselectable, and ~~then you can test whether~~ the ~~touch has been used normally.<ol style="list-style-type: lower-alpha;"><li>~~'''~~None~~CLOSE''' button and '''SEND'''~~: no rotation</li></ol>~~button become selectable</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''set_lcd_rotate~~pi3b-img428.~~sh none'''~~png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then use Dupont wire to short the RXD and TXD pins of uart7</li>

[[File:pi3b-img429.png]]</ol><ol start="27" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then you can enter a character in the send edit box below, and click the '''~~Left~~SEND'''~~: rotate left 90 degrees~~button to start sending</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''set_lcd_rotate~~pi3b-img430.~~sh left'''~~png]]</ol><ol start="8" style="list-style-type: decimal;"><li>If everything is normal, the received string will be displayed in the receiving box</li>

[[File:pi3b-img431.png]]</ol ~~start~~>~~<li>'''Inverted''': Flip up and down, which is equivalent to rotating 180 degrees~~</~~li></ol~~span>

~~orangepi@orangepi:~$ '''set_lcd_rotate.sh inverted'''~~=== 40pin SPI test ===

~~<ol start="4" style="list-style-type: lower-alpha;"><li>'''Right''': rotate right 90 degrees</li></ol>~~# According to the schematic diagram of the 40pin interface, the spi available for Orange Pi 3B is spi3

~~orangepi@orangepi~~:~~~$ '''set_lcd_rotate~~:[[File:pi3b-img264.~~sh right'''~~png]]

~~'''The set_lcd_rotate~~<ol start="2" style="list-style-type: decimal;"><li>Here, the SPI interface is tested through the w25q64 module.~~sh script mainly does four things:'''~~First, the w25q64 device is connected to the SPI3 interface</li>

~~'''1~~[[File:pi3b-img432. ~~Rotate~~ png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then click the ~~direction displayed by~~ wiringOP icon to open the ~~framebuffer'''~~wiringOP APP</li>

~~'''2~~[[File:pi3b-img418. ~~Rotate~~ png]]</ol><ol start="4" style="list-style-type: decimal;"><li>The main interface of wiringOP APP is displayed as shown in the ~~direction of~~ figure below, click the SPI_TEST button to open the ~~touch'''~~SPI test interface</li>

[[File:pi3b-img433.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then click the '''~~3. Turn off the boot logo~~OPEN'''button to initialize the SPI</li>

~~'''4~~[[File:pi3b-img434. ~~Restart~~ png]]</ol><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 ~~system~~''' TRANSFER'''~~Rotating the touch direction is achieved by adding the line Option "TransformationMatrix" "x x x x x x x x x" to /usr~~button</~~share/X11/xorg.conf.d/40-libinput.conf Where "x x x x x x x x x" is configured differently for different directions.'''~~li>

[[File:pi3b-img435.png]]

</ol>

<li>~~Touch rotation reference~~Finally, the APP will display the read ID information</li~~></ol~~>

~~https~~[[File:~~//wiki.ubuntu~~pi3b-img436.~~com~~png]]</Xol><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)</~~InputCoordinateTransformation~~li>

[[File:pi3b-img437.png]]</ol>~~== Instructions for using the switch logo ==~~

~~# By default, the switch logo will only be displayed in the desktop version of the system# Set the '''bootlogo''' variable to '''false''' in '''/boot/orangepiEnv.txt''' to turn off the switch logo~~=== 40pin PWM test ===

~~orangepi@orangepi:~$~~ # Android enables '''~~vim /boot/orangepiEnv.txt~~PWM11'''by default, and the corresponding pin is located at 40pin as shown in the figure below

~~verbosity=1~~::[[File:pi3b-img438.png]]

~~'''bootlogo~~<ol start=~~false'''~~"2" style="list-style-type: decimal;"><li>First click on the wiringOP icon to open the wiringOP APP</li>

[[File:pi3b-img418.png]]

</ol>

<li>~~Set~~ Then click the '''~~bootlogo~~PWM_TEST''' ~~variable~~ button on the main interface of wiringOP to ~~'''true''' in '''/boot/orangepiEnv.txt''' to enable~~ enter the ~~switch logo~~PWM test interface</li>~~</ol>~~ ~~orangepi@orangepi:~$ '''vim /boot/orangepiEnv.txt'''~~ ~~verbosity=1~~ ~~'''bootlogo=true'''~~

[[File:pi3b-img439.png]]

</ol>

<li>The ~~location of~~ base address corresponding to PWM11 is '''fe6f0030''', here pwmchip0 shows '''fdd70020.pwm''' on the ~~boot logo image in~~ right, then you need to click the ~~Linux system is</li></ol>~~ drop-down option to select other pwmchips until '''~~/usr/share/plymouth/themes/orangepi/watermark~~febf0030.~~png~~pwm'''is displayed on the right</li>

[[File:pi3b-img440.png]]

</ol>

<li>~~After replacing~~ When the ~~boot logo picture~~drop-down option selects '''pwmchip3''', ~~you need to run~~ the ~~following command to take effect~~corresponding base address of PWM11 is '''fe6f0030''' on the right</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img441.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then confirm the PWM channel, the default is channel 0, and confirm the PWM cycle, the default configuration is '''50000ns''', converted to PWM frequency is '''20KHz''', you can modify it yourself, click the '''EXPORT''' button to export '''~~sudo update-initramfs -u~~PWM11'''</li>

[[File:pi3b-img442.png]]<~~span id~~/ol><ol start="7" style="~~how-to-use-the-zfs~~list-~~file~~style-~~system~~type: decimal;"><~~/span~~li>~~== How~~ Then drag the drag bar below to change the PWM duty cycle, and then check Enable to ~~use~~ output the ~~ZFS file system ==~~PWM waveform</li>

~~'''The latest version of Ubuntu20~~[[File:pi3b-img443.~~04, Ubuntu22~~png]]</ol><ol start="8" style="list-style-type: decimal;"><li>Then use an oscilloscope to measure the No.04 32 pin in the 40pin of the development board, ~~Debian11~~ and ~~Debian12 desktop version systems have pre-installed zfs,~~ you can ~~use it directly.'''~~see the following waveform</li>

~~'''The pre~~[[File:pi3b-~~installed zfs version in Ubuntu20~~img444.~~04 and Ubuntu22.04 desktop systems is 2.1.6.'''~~png]]</ol>

~~'''The pre-installed zfs version in Debian11 and Debian12 desktop systems is 2.1.11.'''~~== How to use ADB ==

~~'''After the system starts, please first confirm whether the zfs kernel module has been loaded. If you can see zfs~~=== Use network connection adb debugging ===

~~orangepi@orangepi~~{| class="wikitable" style="background-color:~$ #ffffdc;width:800px;" |-| <big>'''~~lsmod | grep "zfs"~~Using the network adb does not require a data cable to connect the computer and the development board, but to communicate through the network, so first make sure that the wired or wireless network of the development board is connected, and then obtain the IP address of the development board, which will be used later.'''</big>|}

~~zfs 2801664 0~~# Make sure that the '''service.adb.tcp.port''' of the Android system is set to port number 5555

~~zunicode 327680 1 zfs~~::{| class="wikitable" style="width:800px;" |-| console:/ # '''getprop | grep "adb.tcp"'''

~~zzstd 471040 1 zfs~~[service.adb.tcp.port]: ['''5555''']|}

~~zlua 139264 1 zfs~~<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>

~~zcommon 69632 1 zfs~~{| class="wikitable" style="width:800px;" |-| console:/ # '''setprop service.adb.tcp.port 5555'''

~~znvpair 61440 2 zfs,zcommon~~console:/ # '''stop adbd'''

~~zavl 16384 1 zfs~~console:/ # '''start adbd'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Install adb tool on Ubuntu PC</li>

~~icp 221184 1 zfs~~{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt update'''

~~spl 77824 6 zfs,icp,zzstd,znvpair,zcommon,zavl~~test@test:~$ '''sudo apt install -y adb'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then connect network adb on Ubuntu PC</li>

~~=== How~~ be changed to ~~install ZFS ===~~the IP address of the development board)'''

~~'''Before installing zfs, please make sure that the Linux image used is the latest version. In addition, if zfs is already installed in the system, it needs to be installed again.'''~~* daemon not running; starting now at tcp:5037

Before installing zfs, you need to install the kernel header file first. For the method of installing the kernel header file, please refer to the instructions in the [[\l|'''section on the method of installing the kernel header file''']].* daemon started successfully

~~In Ubuntu20~~connected to 192.~~04, Ubuntu22.04 and Debian11 systems, zfs cannot be installed directly through apt, because the default apt source zfs version is lower than 2~~168.1.~~6, and there is a problem of incompatibility with rk Linux5.10 kernel. This problem is fixed in zfs version 2.1.6 and later.~~xxx:5555

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/serviceAndSupport/index.html '''official tool'''] of the development board. Open the '''official tool''', 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~~test@test:~~pi3b-img368.png|230x93px]]~~~$ '''adb devices'''

~~After downloading the zfs deb packages~~ List of the corresponding version, please upload them to the Linux system of the development board. For the upload method, please refer to '''[[\l|the description in the section of the method of uploading files to the Linux system of the development board]].'''devices attached

~~After the upload is complete, use the '''cd''' command~~ 192.168.1.xxx:5555 device|}</ol><ol start="5" style="list-style-type: decimal;"><li>Then you can log in to the ~~command line of the development board Linux~~ android system ~~to enter the directory of the deb package, and then use~~ through the ~~following command to install~~ adb shell on the ~~deb package of zfs.~~Ubuntu PC</li>

~~orangepi~~{| class="wikitable" style="width:800px;" |-| test@~~orangepi~~test:~$ '''~~sudo apt install ./*.deb~~adb shell'''

~~After the installation is complete, use the following command to see the zfs-related kernel modules~~console:/ #|}</ol>

~~orangepi@orangepi:~$~~ = '''~~ls /lib/modules/5.10.160-rockchip-rk356x/updates/dkms/~~Appendix'''=

~~'''icp.ko spl.ko zavl.ko zcommon.ko zfs.ko zlua.ko znvpair.ko zunicode.ko zzstd.ko'''~~== User Manual Update History ==

~~Then restart the Linux system to see that the zfs kernel module will be automatically loaded:~~ ~~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.png|576x37px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then execute '''df -h''' to see that '''pool1''' is mounted to the '''/pool1''' directory</li></ol>~~ ~~orangepi@orangepi:~$ '''df -h'''~~ ~~Filesystem Size Used Avail Use% Mounted on~~ ~~tmpfs 1.6G 18M 1.6G 2% /run~~ ~~/dev/mmcblk0p2 29G 6.0G 22G 22% /~~ ~~tmpfs 7.7G 46M 7.7G 1% /dev/shm~~ ~~tmpfs 5.0M 4.0K 5.0M 1% /run/lock~~ ~~tmpfs 7.7G 944K 7.7G 1% /tmp~~ ~~/dev/mmcblk0p1 1022M 115M 908M 12% /boot~~ ~~/dev/zram1 188M 4.5M 169M 3% /var/log~~ ~~tmpfs 1.6G 80K 1.6G 1% /run/user/1000~~ ~~'''pool1 489G 9.3M 489G 1% /pool1'''~~ ~~<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></ol>~~ ~~orangepi@orangepi:~$ '''mount | grep pool1'''~~ ~~pool1 on /pool1 type '''zfs''' (rw,xattr,noacl)~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Then we can test copying a file to the ZFS pool</li></ol>~~ ~~orangepi@orangepi:~$ '''sudo cp -v /usr/local/test.mp4 /pool1/'''~~ ~~'/usr/local/test.mp4' -> '/pool1/test.mp4'~~ ~~=== Test the data deduplication function of ZFS ===~~ ~~# 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'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Then do a simple test, first enter pool1, and then execute the following command to generate a random file with a size of 1G</li></ol>~~ ~~orangepi@orangepi:~$ '''cd /pool1/'''~~ ~~root@orangepi:/pool1$ '''sudo dd if=/dev/urandom of=test.1g bs=1M count=1024'''~~ ~~1024+0 records in~~ ~~1024+0 records out~~ ~~1073741824 bytes (1.1 GB, 1.0 GiB) copied, 5.04367 s, 213 MB/s~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then use the following command to copy 1000 random files of size 1G</li></ol>~~ ~~root@orangepi:/pool1$ '''for ((i=0; i<1000; i++)); do sudo cp test.1g $i.test.1g; done'''~~ ~~<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 ZFS pool is only '''504GB''' (the total capacity of SSD+U disk), which cannot hold such a large amount of data</li></ol> ~~root@orangepi:/pool1$ '''du -lh'''~~ ~~1002G~~ ~~<ol start="5" style="list-style-type: 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.</li></ol> ~~[[File:pi3b-img371.png|576x36px]]~~ ~~=== Test the data compression function of ZFS ===~~ # Because the stored data is different, the disk space saved by compression will also be different, so we choose to compress relatively large plain text files for compression testing, and execute the following commands to pack the '''/var/log/''' and '''/etc/''' directories into a tarball ~~orangepi@orangepi:~$ '''cd /pool1/'''~~ ~~root@orangepi:/pool1$ '''sudo tar -cf text.tar /var/log/ /etc/'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Then the file size that can be seen through the '''ls -lh''' command and the space occupied in the ZFS pool are both '''27M'''</li></ol>~~ ~~[[File:pi3b-img372.png|576x90px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then we enable compression in the ZFS pool pool1</li></ol>~~ ~~root@orangepi:/pool1$ '''sudo zfs set compression=lz4 pool1'''~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then execute the following command again to package the '''/var/log/''' and '''/etc/''' directories into a tar package</li></ol>~~ ~~root@orangepi:/pool1$ '''sudo tar -cf text.tar /var/log/ /etc/'''~~ ~~<ol start="5" style="list-style-type: decimal;"><li>At this time, you can see that the size of the '''text.tar''' file is still 27M, but it only occupies 9.47M in the ZFS pool, indicating that the file is compressed</li></ol>~~ ~~[[File:pi3b-img373.png|576x79px]]~~ ~~== How to shut down and restart the development board ==~~ # 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''' command to shut down the Linux system of the development board before powering off. Then unplug the power again. ~~orangepi@orangepi:~$ '''sudo poweroff'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>In addition, the development board is equipped with a switch button, and you can also '''short press''' the switch button on the development board to shut down.</li></ol>~~ ~~[[File:pi3b-img374.png|294x80px]]~~ '''Note that the Linux desktop version system will pop up a confirmation box as shown in the figure below after pressing the switch button, and the system will shut down only after clicking the Shut Down option.''' ~~[[File:pi3b-img375.png|207x193px]]~~ ~~<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></ol>~~ ~~[[File:pi3b-img374.png|294x80px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>The command to restart the Linux system is</li></ol>~~ ~~orangepi@orangepi:~$ '''sudo''' '''reboot'''~~ ~~~~ ~~= '''Linux SDK——orangepi-build instructions''' =~~ ~~== Compilation system requirements ==~~ '''We can cross-compile the Linux image of the development board on the x64 computer, or compile the Linux image of the development board on the Ubuntu22.04 system of the development board, please choose one according to your preference.''' '''If you use orangepi-build to compile the Linux image in the Ubuntu22.04 system of the development board, please do a good job of cooling (especially when the SSD starts). If the heat dissipation is not done well, it is prone to the error of file system runaway.''' ~~=== Compile with the Ubuntu22.04 system of the development board ===~~ # The Linux SDK, namely '''orangepi-build''', supports running on the '''Ubuntu 22.04''' of the development board (other systems have not been tested), so before downloading orangepi-build, please first ensure that the Ubuntu version installed on the development board is Ubuntu 22.04. The command to check the Ubuntu version installed on the development board is as follows. If the Release field does not display '''22.04''', it means that the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operations. ~~orangepi@orangepi:~$ '''lsb_release -a'''~~ ~~No LSB modules are available.~~ ~~Distributor ID: Ubuntu~~ ~~Description: Ubuntu 22.04.1 LTS~~ ~~Release: '''22.04'''~~ ~~Codename: jammy~~ ~~<ol start="2" style="list-style-type: decimal;">~~<li>'''Since the source codes such as the kernel and U-boot are stored on GitHub, it is very important to ensure that the development board can download codes from GitHub normally when compiling the image.'''</li></ol> ~~=== Compile with x64 Ubuntu22.04 computer ===~~ # 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. ~~test@test:~$ '''lsb_release -a'''~~ ~~No LSB modules are available.~~ ~~Distributor ID: Ubuntu~~ ~~Description: Ubuntu 22.04 LTS~~ ~~Release: '''22.04'''~~ ~~Codename: jammy~~ ~~<ol start="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></ol>~~ ~~[https://repo.huaweicloud.com/ubuntu-releases/21.04/ubuntu-21.04-desktop-amd64.iso '''https://mirrors.tuna.tsinghua.edu.cn/ubuntu-releases/22.04/ubuntu-22.04-desktop-amd64.iso''']~~ Or ~~'''https://repo.huaweicloud.com/ubuntu-releases/22.04/ubuntu-22.04.1-desktop-amd64.iso'''~~ ~~<ol start="4" style="list-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="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/~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>Note that the Ubuntu version needs to be switched to 22.04</li></ol>~~ ~~[[File:pi3b-img376.png|576x241px]]~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>The content of the '''/etc/apt/sources.list''' file that needs to be replaced is</li></ol>~~ ~~test@test:~$ '''sudo mv /etc/apt/sources.list /etc/apt/sources.list.bak'''~~ ~~test@test:~$ '''sudo vim /etc/apt/sources.list'''~~ ~~# By default, the source image is commented to improve the speed of apt update, you can uncomment it yourself if necessary~~ ~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse~~ ~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse~~ ~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse~~ ~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse~~ ~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse~~ ~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse~~ ~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-security main restricted universe multiverse~~ ~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-security main restricted universe multiverse~~ ~~# Pre-release software source, not recommended to enable~~ ~~# deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse~~ ~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>After the replacement, you need to update the package information and make sure there is no error</li></ol>~~ ~~test@test:~$ '''sudo apt update'''~~ ~~<ol start="5" style="list-style-type: lower-alpha;">~~<li>'''In addition, since the source codes such as the kernel and U-boot are stored on GitHub, it is very important to ensure that the computer can download codes from GitHub normally when compiling the image.'''</li></ol> ~~== Get the source code of Linux sdk ==~~ ~~=== Download orangepi-build from github ===~~ # The Linux sdk actually refers to the code of orangepi-build. orangepi-build is modified based on the armbian build system. Using orangepi-build, multiple versions of Linux images can be compiled. First download the code of orangepi-build, the command is as follows: ~~test@test:~$ '''sudo apt-get update'''~~ ~~test@test:~$ '''sudo apt-get install -y git'''~~ ~~test@test:~$ '''git clone https://github.com/orangepi-xunlong/orangepi-build.git -b next'''~~ '''Note that the Orange Pi 3B development board needs to download the source code of the next branch of orangepi-build. The above git clone command needs to specify the branch of the orangepi-build source code as next.''' ~~<div class="figure">~~ ~~[[File:pi3b-img377.png|576x298px|图片6]]~~ ~~</div>~~'''Downloading the orangepi-build code through the git clone command does not require entering the user name and password of the github account (the same is true for downloading other codes in this manual), if the Ubuntu PC prompts the user to enter the github account after entering the git clone command The name and password are usually entered incorrectly in the address of the orangepi-build warehouse behind the git clone. Please check the spelling of the command carefully, instead of thinking that we forgot to provide the username and password of the github account.''' ~~<ol start="2" style="list-style-type: decimal;"><li>The u-boot and Linux kernel versions currently used by the development board are as follows</li></ol>~~ {| class="wikitable"|-| style="~~text-align~~width: ~~left~~800px;~~"| '''branch'''| style="~~text-align: ~~left~~center;"~~| '''u-boot version'''~~| ~~style="text~~-~~align: left;"| '''Linux Kernel version'''~~|-~~| style="text-align: left;"|~~ '''~~legacy~~Version'''| ~~style="text-align: left;"| '''u-boot 2017.09'''| style="text-align: left;"|~~ '''~~Linux5.10~~Date'''|} '''The branch mentioned here is not the same thing as the branch of the orangepi-build source code, please do not confuse it. This branch is mainly used to distinguish different kernel source code versions.''' ~~'''Currently, the Linux5.10 bsp kernel provided by RK is defined as the legacy branch. If the mainline kernel is supported in the future, a current branch will be added.'''~~ ~~<ol start="3" style="list-style-type: decimal;"><li>orangepi-build will contain the following files and folders after downloading<ol style="list-style-type: lower-alpha;"><li>'''build.sh''': Compile the startup script</li><li>'''external''': Contains the configuration files needed to compile the image, specific scripts, and the source code of some programs, etc.</li><li>'''LICENSE''': GPL 2 license file</li><li>README.md: orangepi-build documentation</li><li>'''scripts''': General script for compiling Linux images</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''ls'''~~ ~~'''build.sh external LICENSE''' README.md '''scripts'''~~ '''If you downloaded the code of orangepi-build from github, after downloading, you may find that orangepi-build does not contain the source code of u-boot and Linux kernel, nor does u-boot and Linux kernel need to use cross-compilation tools Chain, this is normal, because these things are stored in other separate github warehouses or some servers (the addresses will be detailed below). orangepi-build will specify the address of u-boot, Linux kernel and cross-compilation toolchain in the script and configuration file. When running orangepi-build, when it finds that there are no such things locally, it will automatically go to the corresponding place to download them.''' ~~=== Download the cross-compilation toolchain ===~~ '''The cross-compilation toolchain will only be downloaded when the orangepi-build compilation image is used on an x64 computer. Compiling the Linux image of the development board in the Ubuntu22.04 of the development board will not download the cross-compilation toolchain. At this time, orangepi-build/toolchains will be an empty folder.''' # When orangepi-build runs for the first time, it will automatically download the cross-compilation toolchain and put it in the '''toolchains''' folder. Every time after running the build.sh script of orangepi-build, it will check whether the cross-compilation toolchain in '''toolchains''' exists , if it does not exist, the download will be restarted, if it exists, it will be used directly, and the download will not be repeated. ~~<div class="figure">~~ ~~[[File:pi3b-img378.png|575x278px|选区_396]]~~ ~~</div><ol start="2" style="list-style-type: decimal;"><li>The image URL of the cross-compilation toolchain in China is the open source software image site of Tsinghua University</li></ol>~~ ~~https://mirrors.tuna.tsinghua.edu.cn/armbian-releases/_toolchain/~~ ~~<ol start="3" style="list-style-type: decimal;"><li>After '''toolchains''' is downloaded, it will contain multiple versions of cross-compilation toolchains, and the development board will only use two of them</li></ol>~~ ~~test@test:~/orangepi-build$ '''ls toolchains/'''~~ ~~gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu~~ ~~gcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf~~ ~~gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu~~ ~~gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf~~ ~~gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabi~~ ~~gcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabihf~~ ~~gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu~~ ~~gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabi~~ ~~gcc-linaro-aarch64-none-elf-4.8-2013.11_linux~~ ~~gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux~~ ~~gcc-linaro-arm-none-eabi-4.8-2014.04_linux~~ ~~<ol start="4" style="list-style-type: decimal;"><li>The cross-compilation toolchain used to compile the Linux kernel source code is<ol style="list-style-type: lower-alpha;"><li>Linux5.10</li></ol></li></ol>~~ ~~'''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''~~ ~~<ol start="5" style="list-style-type: decimal;"><li>The cross-compilation tool chain used to compile the u-boot source code is<ol style="list-style-type: lower-alpha;"><li>v2017.09</li></ol></li></ol>~~ ~~'''gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu'''~~ ~~=== orangepi-build complete directory structure description ===~~ ~~<ol style="list-style-type: decimal;">~~<li>The orangepi-build repository does not contain the source code of the Linux kernel, u-boot, and cross-compilation toolchain after downloading. The source code of the Linux kernel and u-boot is stored in an independent git repository~~<ol style="list-style-type: lower-alpha;"><li>The git repository where the Linux kernel source code is stored is as follows:</li></ol></li></ol>~~ ~~'''https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-5.10-rk35xx'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The git warehouse where the b.u-boot source code is stored is as follows:</li></ol>~~ ~~'''https://github.com/orangepi-xunlong/u-boot-orangepi/tree/v2017.09-rk3588'''~~ ~~<ol start="2" style="list-style-type: decimal;">~~<li>When orangepi-build runs for the first time, it will download the cross-compilation toolchain, u-boot and Linux kernel source code. After successfully compiling a Linux image, the files and folders that can be seen in orangepi-build are:~~a. '''build.sh''': compile startup script~~b. '''external''': Contains the configuration files needed to compile the image, scripts with specific functions, and the source code of some programs. The rootfs compressed package cached during the image compilation process is also stored in externalc. '''kernel''': stores the source code of the Linux kernel, and the folder named orange-pi-5.10-rk35xx stores the kernel source code of the legacy branch of the RK3588/RK3588S/RK3566 series development boards. Please do not manually name the folder name of the kernel source code Modify, if modified, the kernel source code will be re-downloaded when the compilation system is running~~d. '''LICENSE''': GPL 2 license filee. '''README'''.md: orangepi-build documentationf. '''output''': Store compiled deb packages such as u-boot and Linux, compilation logs, and compiled images and other filesg. '''scripts''': general scripts for compiling Linux imagesh. '''toolchains''': store cross-compilation toolchain~~i. '''u-boot''': stores the source code of u-boot, the folder named v2017.09-rk3588 stores the u-boot source code of the legacy branch of the RK3588/RK3588S/RK3566 series development boards, the name of the folder of the u-boot source code Please do not modify it manually, if it is modified, the u-boot source code will be re-downloaded when the compiling system is running~~j. '''userpatches''': Store configuration files needed to compile scripts</li></ol>~~ ~~test@test:~/orangepi-build$ '''ls'''~~ ~~'''build.sh external kernel LICENSE output''' README.md '''scripts toolchains u-boot userpatches'''~~ ~~== Compile u-boot ==~~ ~~# Run the build.sh script, remember to add sudo permission~~ ~~test@test:~/orangepi-build$ '''sudo ./build.sh'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Select '''U-boot package'''，then enter</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img379.png|576x132px|选区_238]]~~ ~~</div><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img380.png|576x197px|}4$_5F06}}0R4GU8]OVO}4E]]~~ ~~</div><ol start="4" style="list-style-type: decimal;"><li>Then it will start to compile u-boot, and some information prompted during compilation is explained as follows<ol style="list-style-type: lower-alpha;"><li>u-boot source code version</li></ol></li></ol>~~ ~~[ o.k. ] Compiling u-boot [ '''v2017.09''' ]~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The version of the cross-compilation toolchain</li></ol>~~ ~~[ o.k. ] Compiler version [ '''aarch64-linux-gnu-gcc 7.4.1''' ]~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>Path to the generated u-boot deb package</li></ol>~~ ~~[ o.k. ] Target directory [ '''orangepi-build/output/debs/u-boot''' ]~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>The package name of the generated u-boot deb package</li></ol>~~ ~~[ o.k. ] File name [ '''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb''' ]~~ ~~<ol start="5" style="list-style-type: lower-alpha;"><li>Compilation time</li></ol>~~ ~~[ o.k. ] Runtime [ '''1 min''' ]~~ ~~<ol start="6" style="list-style-type: lower-alpha;"><li>Repeat the command to compile u-boot, use the following command to start compiling u-boot directly without selecting through the graphical interface</li></ol>~~ ~~[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=u-boot KERNEL_CONFIGURE=no''' ]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>View the u-boot deb package generated by compilation</li></ol>~~ ~~test@test:~/orangepi-build$ '''ls output/debs/u-boot/'''~~ ~~linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb~~ ~~<ol start="6" style="list-style-type: decimal;"><li>The files contained in the generated u-boot deb package are as follows<ol style="list-style-type: lower-alpha;"><li>Use the following command to decompress the deb package</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''cd output/debs/u-boot'''~~ ~~test@test:~/orangepi_build/output/debs/u-boot$ $ '''dpkg -x''' \~~ ~~'''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb . (Note that there is a "." at the end of the command)'''~~ ~~test@test:~/orangepi_build/output/debs/u-boot$ '''ls'''~~ ~~linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb '''usr'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The decompressed file is as follows</li></ol>~~ ~~test@test:~/orangepi-build/output/debs/u-boot$ '''tree usr'''~~ ~~usr~~ ~~└── lib~~ ~~├── linux-u-boot-legacy-orangepi3b_1.0.0_arm64~~ ~~│ ├── idbloader.img~~ ~~│ ├── rkspi_loader.img~~ ~~│ └── u-boot.itb~~ ~~└── u-boot~~ ~~├── LICENSE~~ ~~├── orangepi-3b-rk3566_defconfig~~ ~~└── platform_install.sh~~ ~~3 directories, 6 files~~ ~~<ol start="7" style="list-style-type: decimal;">~~<li>When the orangepi-bulid compilation system compiles the u-boot source code, it will first synchronize the u-boot source code with the u-boot source code of the github server, so if you want to modify the u-boot source code, you first need to turn off the download and update function of the source code '''(This function needs to be fully compiled once u-boot, otherwise it will prompt that the source code of u-boot cannot be found. If the source code compressed package is downloaded from Google cloud disk, there is no such problem, because the source code of u-boot have been cached)''', otherwise the changes made will be reverted, the method is as follows:</li></ol> ~~<blockquote>Set the IGNORE_UPDATES variable in userpatches/config-default.conf to "yes"</blockquote>test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''~~ ~~IGNORE_UPDATES="'''yes'''"~~ ~~<ol start="8" style="list-style-type: decimal;"><li>When debugging u-boot code, you can use the following method to update u-boot in the Linux image for testing<ol style="list-style-type: lower-alpha;"><li>Upload the compiled u-boot deb package to the Linux system of the development board</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''cd output/debs/u-boot'''~~ ~~test@test:~/orangepi_build/output/debs/u-boot$ '''scp \'''~~ ~~'''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb''' [mailto:root@192.168.1.xxx:/root root@192.168.1.xxx:/root]~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>Then log in to the development board and uninstall the deb package of u-boot installed</li></ol>~~ ~~root@orangepi:~# '''apt purge -y linux-u-boot-orangepi3b-legacy'''~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>Install the new u-boot deb package just uploaded</li></ol>~~ ~~root@orangepi:~# '''dpkg -i''' '''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb'''~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>Then run the nand-sata-install script</li></ol>~~ ~~root@orangepi:~# '''nand-sata-install'''~~ ~~<ol start="5" style="list-style-type: lower-alpha;"><li>Then select '''5 Install/~~Update ~~the bootloader on SD/eMM''' to update the u-boot in the TF card or '''7 Install/Update the bootloader on SPI Flash''' to update the u-boot in the SPI Flash</li></ol>~~ ~~[[File:pi3b-img381.png|312x152px]]~~ ~~<ol start="6" style="list-style-type: lower-alpha;"><li>After pressing the Enter key, a Warning will pop up first</li></ol>~~ ~~[[File:pi3b-img382.png|309x168px]]~~ ~~<ol start="7" style="list-style-type: lower-alpha;"><li>Press the Enter key again to start updating u-boot, and the following information will be displayed after the update is completed</li></ol>~~ ~~[[File:pi3b-img383.png|244x137px]]~~ ~~<ol start="8" style="list-style-type: lower-alpha;"><li>Then you can restart the development board to test whether the modification of u-boot takes effect</li></ol>~~ ~~<ol start="9" style="list-style-type: decimal;"><li>Other useful information<ol style="list-style-type: lower-alpha;"><li>In the u-boot 2017.09 source code, the defconfig configuration file used by the development board is</li></ol></li></ol>~~ ~~[https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/configs/orangepi_5_defconfig '''orangepi-build/u-boot/v2017.09-rk3588/configs/orangepi-3b-rk3566_defconfig''']~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>In the u-boot 2017.09 source code, the dts file used by the development board is</li></ol>~~ ~~[https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/arch/arm/dts/rk3588s-orangepi-5.dts orangepi-build/u-boot/v2017.09-rk3588/arch/arm/dts/rk3566-orangepi-3b.dts]~~ ~~== Compile the Linux kernel ==~~ ~~# Run the build.sh script, remember to add sudo permission~~ ~~test@test:~/orangepi-build$ '''sudo ./build.sh'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Select '''Kernel package'''，then enter</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img384.png|575x116px|选区_240]]~~ ~~</div><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img380.png|576x197px|}4$_5F06}}0R4GU8]OVO}4E]]~~ ~~</div><ol start="4" style="list-style-type: decimal;">~~<li>Then it will prompt whether to display the kernel configuration interface. If you do not need to modify the kernel configuration, select the first one. If you need to modify the kernel configuration, select the second one.</li></ol> ~~[[File:pi3b-img385.png|576x87px]]~~ ~~<ol start="5" style="list-style-type: decimal;">~~<li>If you choose to display the kernel configuration menu (the second option) in step 4), the kernel configuration interface opened by '''make menuconfig''' will pop up. At this time, you can directly modify the kernel configuration, save and exit after modification. Yes, after exiting, the kernel source code will be compiled</li></ol> ~~[[File:pi3b-img386.png|462x322px]]~~ ~~<ol style="list-style-type: lower-alpha;">~~<li>If you do not need to modify the configuration options of the kernel, when running the build.sh script, pass in '''KERNEL_CONFIGURE=no''' to temporarily block the pop-up kernel configuration interface</li></ol> ~~test@test:~/orangepi-build$ '''sudo ./build.sh KERNEL_CONFIGURE=no'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>You can also set '''KERNEL_CONFIGURE=no''' in the '''orangepi-build/userpatches/config-default.conf''' configuration file, which can permanently disable this function</li>~~<li>If the following error is displayed when compiling the kernel, it is because the terminal interface of the Ubuntu PC is too small to display the '''make menuconfig''' interface. Please maximize the terminal of the Ubuntu PC and run the build.sh script again</li></ol> ~~[[File:pi3b-img387.png|574x234px]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Part of the information prompted when compiling the kernel source code is as follows<ol style="list-style-type: lower-alpha;"><li>The version of the Linux kernel source code</li></ol></li></ol>~~ ~~[ o.k. ] Compiling current kernel [ '''5.10.160''' ]~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The version of the cross-compilation toolchain used</li></ol>~~ ~~[ o.k. ] Compiler version [ '''aarch64-none-linux-gnu-gcc 11.2.1''' ]~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>The configuration file used by the kernel by default and the path where it is stored</li></ol>~~ ~~[ o.k. ] Using kernel config file [ '''config/kernel/linux-rockchip-rk356x-legacy.config''' ]~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>The path of the deb package related to the kernel generated by compiling</li></ol>~~ ~~[ o.k. ] Target directory [ '''orangepi-build/output/debs/''' ]~~ ~~<ol start="5" style="list-style-type: lower-alpha;"><li>The package name of the compiled kernel image deb package</li></ol>~~ ~~[ o.k. ] File name [ '''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb''' ]~~ ~~<ol start="6" style="list-style-type: lower-alpha;"><li>The time used for compilation</li></ol>~~ ~~[ o.k. ] Runtime [ '''5 min''' ]~~ ~~<ol start="7" style="list-style-type: lower-alpha;">~~<li>Finally, the compilation command to repeatedly compile the kernel selected last time will be displayed. Use the following command to start compiling the kernel source code directly without selecting through the graphical interface</li></ol> ~~[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=kernel KERNEL_CONFIGURE=no''' ]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>View the deb package related to the kernel generated by compilation<ol style="list-style-type: lower-alpha;"><li>'''linux-dtb-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Contains dtb files used by the kernel</li><li>'''linux-headers-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Include kernel header files</li><li>'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Contains kernel images and kernel modules</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''ls output/debs/linux-*'''~~ ~~output/debs/linux-dtb-legacy-rockchip-rk356x_1.0.0_arm64.deb output/debs/linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb~~ ~~output/debs/linux-headers-legacy-rockchip-rk356x_1.0.0_arm64.deb~~ ~~<ol start="8" style="list-style-type: decimal;"><li>The files contained in the generated Linux-image deb package are as follows<ol style="list-style-type: lower-alpha;"><li>Use the following command to decompress the deb package</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''cd output/debs'''~~ ~~test@test:~/orangepi_build/output/debs$ '''mkdir test'''~~ ~~test@test:~/orangepi_build/output/debs$ '''cp \'''~~ ~~'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb test/'''~~ ~~test@test:~/orangepi_build/output/debs$ '''cd test'''~~ ~~test@test:~/orangepi_build/output/debs/test$ '''dpkg -x \'''~~ ~~'''linux-image-legacy-rockchip-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"~~|-~~| style="text-align: left;"| '''Android version'''| style="text-align: left;"| '''Kernel version'''~~|-~~| style="text-align: left;"| '''Android 11''~~Notes'~~| style="text-align: left;"|~~ ''~~'Linux4.19'''~~|} ~~== Android Function Adaptation ==~~ ~~{| class="wikitable"~~|-~~| style="text-align: left;"| '''Functions'''| style="text-align: left;"| '''Android 11'''~~|-~~| style="text-align: left;"| '''USB2.0x3'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''USB3.0x1'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''M.2 NVMe SSD boot'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''WIFI'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Bluetooth'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''GPIO（40pin）'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''UART（40pin）'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''SPI（40pin）'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''I2C（40pin）'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''PWM（40pin）'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''PWM fan interface'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''3pin Debugging serial port'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''EMMC'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''TF card boot'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI video'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI Audio'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''LCD'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''eDP display'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Gigabit network port'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Network port status indicator'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Headphone playback'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Headphone recording'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''LED Light'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''GPU'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''NPU'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''VPU'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''RTC'''| style="text-align: left;"| '''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~~ ~~<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"~~

|-

|}

== Image Update History ==

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

|-

| style="text-align: center;" | '''Date'''| style="text-align: center;" | '''Update Notes'''

|-

| style="text-align: center;" | 2023-07-19| ~~Orangepi3 b_1~~Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160.7z

~~Orange pi3b_1~~Orangepi3b_1.0.0_ubuntu_jammy_desktop_xfce_linux5.10.160.7z

~~Orange pi3b_1~~Orangepi3b_1.0.0_ubuntu_focal_desktop_xfce_linux5.10.160.7z

OrangePi3B_RK3566_Android11_v1.0.0.tar.gz

OrangePi3B_RK3566_Android11_spi-nvme_v1.0.0.tar.gz

~~O rangePi3B_RK3566_Android11_lcd_spi~~OrangePi3B_RK3566_Android11_lcd_spi-nvme_v1.0.0.tar.gz

* initial version

|}

Admin

Bureaucrats, Administrators

8,367

edits

Changes

Orange Pi 3B

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Products

FAQ

Images Resources

Support

Tools