Changes

← Older edit

Orange Pi 3B

39,130 bytes added, 09:06, 24 August 2023

→‎Interface details of Orange Pi 3B

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

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

== Purpose of Orange Pi 3B ==

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

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

|-

| storage

|

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

• SPI Flash: 16MB/32MB

| Wi-Fi+Bluetooth

|

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

|-

| ethernet transceiver

| Supported OS

|

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

|-

|colspan=2|

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

</div>

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

</div>

== Interface details of Orange Pi 3B ==

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

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

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

|-

|

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

|}

</ol>

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

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

</ol>

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

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

</ol>

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

</div>

|-

|

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

|}

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

</div></ol>

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

[[File:pi3b-img26.png~~|428x268px~~]]

</ol>

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

[[File:pi3b-img27.png~~|427x267px~~]]

</ol>

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

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

</div></ol>

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

</div>

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

[[File:pi3b-img77.png]]

</ol>

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

[[File:pi3b-img78.png]]

</ol>

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

[[File:pi3b-img79.png]]

</ol>

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

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

</div></ol>

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

[[File:pi3b-img80.png]]

</ol>

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

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

</div></ol>

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

[[File:pi3b-img82.png]]

</ol>

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

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Before burning the image, it is recommended to rename the Linux image to be burned to orangepi.img or other shorter names, so that you can see the percentage value of the burning progress when burning the image.'''</big> ~~[[File:pi3b-img48.png~~|~~499x234px]]~~}

[[File:pi3b-img48.png]]

</ol>

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

[[File:pi3b-img83.png]]

</ol>

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

[[File:pi3b-img84.png]]

</ol>

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

[[File:pi3b-img85.png~~|504x240px~~]] '''If there is a problem with burning, please clear the SPIFlash first and then try burning again. For the method of clearing SPIFlash, please refer to the description of [[\l|the method of using RKDevTool to clear SPIFlash]].'''

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

|-

|

<big>'''If there is a problem with burning, please clear the SPIFlash first and then try burning again. For the method of clearing SPIFlash, please refer to the description of [[Orange Pi 3B#Using RKDevTool to clear SPIFlash|the method of using RKDevTool to clear SPIFlash]].'''</big>

|}

</ol>

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

~~~~

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

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

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

[[File:pi3b-img73.png]]

</ol>

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

[[File:pi3b-img74.png]]

</ol>

</li></ol>

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

[[File:pi3b-img75.png]]

</ol>

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

[[File:pi3b-img76.png]]

</ol>

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

<li>After using the TF card to start the Linux system, we first burn the u-boot image into the SPI Flash

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

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

|-

|

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

|}</ol>

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

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

</div></ol>

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

[[File:pi3b-img87.png~~|356x179px|IMG_256~~]]

</div></ol>

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

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

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

<li>Then upload the Linux image file (Debian or Ubuntu image downloaded from the official website) to the TF card. For the method of uploading the Linux image file to the development board, please refer to the description in the section of [[\lOrange Pi 3B#The method of uploading files to the Linux system of the development board|'''the method of uploading files to the development board Linux system''']].</li><li>After uploading the image to the Linux system of the development board, we enter the storage path of the image file in the command line of the Linux system of the development board. For example, I store the Linux image of the development board in the '''/home/orangepi/Desktop''' directory Download it, and then enter the '''/home/orangepi/Desktop''' directory to see the uploaded image file.</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-|

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

Orangepi3b_x.x.x_debian_bullseye_desktop_xfce_Linux5.10.160.img

|}

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

|-

|

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

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

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

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

|}

</ol>

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

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

|-

|

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

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

|}

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

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

|-

|

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

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

|}</ol>

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

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

|-

|

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

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

|}</ol>

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

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

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

|-

|

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

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

|}

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

|-

|

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

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

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

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

|}

</ol>

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

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

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

</li></ol>

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

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

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

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

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

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

~~tmpfs 3~~[[File:pi3b-img75.~~8G 0~~ png]]</ol><ol start="3~~.8G 0% /dev~~" style="list-style-type: decimal;"><li>The position of the SPI Flash on the development board is shown in the figure below, no other settings are required before starting the programming</~~shm~~li>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

~~<ol start="3" style="list~~[[File:pi3b-~~style-type: decimal;"><li>The position of the SPI Flash on the development board is shown in the figure below, no other settings are required before starting the programming</li></ol>~~img97.png]]

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

<~~ol start~~div class="4figure" ~~style="list-style-type: decimal;">~~<li>Burning the Linux image to SPIFlash+NVMe SSD requires a TF card, so first you need to burn the Linux image to the TF card, and then use the TF card to start the development board to enter the Linux system. For the method of burning the Linux image to the TF card, please refer to the instructions in the two sections of [[\l|'''the method of burning the Linux image to the TF card based on the Windows PC''']] and [[\l|'''the method of burning the Linux image to the TF card based on the Ubuntu PC''']].</li><li>After booting into the Linux system in the TF card, please confirm that the NVMe SSD has been properly recognized by the Linux of the development board. If the NVMe SSD is recognized normally, use the '''sudo fdisk -l''' command to see '''nvme''' related information</li></ol>

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

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

~~Use the '''lspci''' command to see an NVMe-related PCI device~~<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> [[File:pi3b-img105.png]]</ol><ol start="7" style="list-style-type: lower-alpha;"><li>Then click '''Flash'''</li>

[[File:pi3b-~~img96~~img106.png~~|389x264px|IMG_256~~]]

</div>~~<ol start="7" style="list-style-type: lower-alpha;"><li>Then click '''Flash'''</li~~></ol> ~~<div class="figure">~~ ~~[[File:pi3b-img97.png|394x268px|IMG_256]]~~ ~~</div~~>

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

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

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

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

</div></ol>

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

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

</div></ol>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

~~<div class~~=~~"figure">~~= How to burn Android image to TF card ==

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

~~</div><ol start="10" style="list-style-type: lower-alpha;"><li>~~# First prepare a TF card with 8GB or larger capacity. The ~~display~~ transmission speed of the ~~burning process~~ TF card must be class10 or above. It is ~~as follows:</li></ol>~~recommended to use a TF card of SanDisk and other brands ~~[[File:pi3b~~# You also need to prepare a good quality USB2.0 male-to-~~img109.png|393x212px]]~~male data cable

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

</div>

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

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

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

</div>

</ol>

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

[[File:pi3b-~~img113~~img125.png~~|356x173px~~]]</ol></li></ol></li></ol><ol start="5" style="list-style-type: decimal;"><li>Then use the decompression software to decompress the compressed package of the downloaded Android image. Among the decompressed files, the file ending with ".img" is the Android image file, and the size is more than 1GB</li><li>Then use the decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>

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

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

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

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

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

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

</div></ol><ol start="62" style="list-style-type: lower-alpha;"><li>Then ~~select~~ make sure that the development board is not inserted into the TF card and not connected to the ~~'''~~power supply</~~dev~~p></~~nvme0n1p2''' partition~~li><li>Then press and hold the MaskROM button on the development board, ~~click~~ the ~~right~~ position of the MaskROM button ~~again, and then select '''Resize/Move'''~~on the development board is shown in the figure below:</lip></olli>

[[File:pi3b-img37.png]]<~~div class~~/ol><ol start="4" style="~~figure~~list-style-type: lower-alpha;"><li>Then connect the power supply of the Type-C interface to the development board, and power on</li>

[[File:pi3b-~~img117~~img38.png~~|448x345px|IMG_256~~]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li>

[[File:pi3b-img39.png]]</~~div~~ol><ol start="76" style="list-style-type: lower-alpha;"><li>Then ~~drag~~ insert the ~~capacity to~~ TF card into the ~~maximum at~~ development board</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><li>Then select '''rk3566_MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and click to open</olli>

~~[[File:pi3b-img118.png|339x210px]]~~ <~~ol start~~div class="8figure" ~~style="list-style-type: lower-alpha;"><li>Then click '''Resize/Move'''</li></ol~~>

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

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

[[File:pi3b-~~img120~~img130.png~~|425x166px~~]]

<~~ol start="10" style="list-style-type: lower-alpha;"~~/div></li><li>~~Then click '''Apply'''~~The display of successful switching is shown in the figure below</lip></olli>

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

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

[[File:pi3b-img132.png]]</ol><ol start="1315" style="list-style-type: lower-alpha;"><li>~~At this point, you can use~~ Then click the "'''~~sudo poweroff~~Firmware''' ~~command~~ " button to ~~shut down. Then please pull out~~ select the ~~TF card, and then short press~~ path of the ~~power button~~ Android image that needs to ~~turn on, then the Linux system in SPIFlash+NVMe SSD will~~ be ~~started.~~burned</li~~></ol~~>

[[File:pi3b-img133.png]]<~~!-- --~~/ol><ol start="1016" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Step~~ Finally, click the "'''9)Upgrade''' is " button to ~~clone~~ start burning, and the log during the ~~system~~ burning process is shown in the ~~TF card to the NMVe SSD~~figure below. ~~We can also directly burn~~ After burning is completed, the ~~Linux image file to the NVMe SSD~~Android system will start automatically. ~~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></ol></li></ol~~>

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

</div></ol></li></ol ~~start~~><li>'''After using this method~~ to -burn ~~the~~ -android-image~~, there is no need~~ -to ~~manually expand the capacity, and it will automatically expand the capacity at the first startup.'''</li-tf-card"></olspan>

~~~~== How to use SDDiskTool to burn Android image to TF card ===

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

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

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

</div></ol>

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

~~[[File~~<ol style="list-style-type:~~pi3b-img125~~none;"><li>a) The image without lcd is specially used for HDMI display and supports 4K display.~~png|264x58px]]~~If you do not use the 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>Then use ~~the~~ decompression software to decompress the compressed package of the downloaded Android image. Among the decompressed files, the file ending with ".img" is the Android image file, and the size is more than 1GB</li><li>Then use ~~the~~ decompression software to decompress '''~~DriverAssitant_v5~~SDDiskTool_v1.1272.zip''', ~~and then~~ this software does not need to be installed, just find ~~the~~ '''~~DriverInstall~~SD_Firmware_Tool.exe''' ~~executable file~~ in the decompressed folder and open it</li>~~</ol>~~ ~~[[File:pi3b-img31.png|575x169px]]~~

[[File:pi3b-img135.png]]

</ol>

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

[[File:pi3b-img136.png]]

</ol>

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

[[File:pi3b-img137.png]]

</ol>

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

[[File:pi3b-img138.png]]

</ol>

</li></ol>

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

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

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

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

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

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

~~[[File~~<ol style="list-style-type:~~pi3b-img38~~decimal;"><li>The development board reserves an eMMC expansion interface. Before programming the system to eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board.~~png|305x94px]]~~The eMMC module and the method of plugging into the development board are as follows:</li>

~~<ol start="5" style="list-style~~[[File:pi3b-~~type~~img61.png|400px]] [[File: ~~lower~~pi3b-~~alpha;">~~<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li></ol>img62.png|400px]]

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

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

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

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

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

[[File:pi3b-~~img132~~img125.png~~|477x224px~~]]</ol></li></ol></li></ol><ol start="5" style="list-style-type: decimal;"><li>Then use decompression software to decompress the compressed package of the downloaded Android image. Among the decompressed files, the file ending with ".img" is the Android image file, and the size is more than 1GB</li><li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>

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

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

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

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

[[File:pi3b-~~img134~~img35.png~~|455x214px|GO~ZSPN`B~~]~~JCQM`@_9UU8[R~~]] </~~div~~ol><~~span id~~ol start="~~how-to-use-sddisktool-to-burn-android-image-to-tf-card~~10"~~>=== How to use SDDiskTool to burn Android image to TF card ===~~ ~~<ol~~ style="list-style-type: decimal;">~~<li>First prepare a TF card with 8GB or larger capacity. The transmission speed of the TF card must be class10 or above. It is recommended to use a TF card of SanDisk and other brands</li~~><li>Then ~~use~~ start burning the ~~card reader to insert the TF card~~ Android image into ~~the computer</li>~~<li>Then download the SDDiskTool programming tool from the [http://www.orangepi.org/html/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 Android11 image from the Orange Pi download''' '''page'''~~eMMC

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

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

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

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

<li>~~After entering~~ Then make sure that the development board is not inserted into the ~~'''~~TF card and ~~eMMC boot image''' folder~~not connected to the power supply</li><li>Then press and hold the MaskROM button on the development board, ~~you can see~~ the ~~following two images,~~ position of the MaskROM button on the ~~difference between them~~ development board isshown in the figure below:</li> [[File:pi3b-img37.png]]</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then connect the power supply of the Type-C interface to the development board</li>

[[File:pi3b-img38.png]]<~~!-- --~~/ol><ol start="5" 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~~previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, ~~please download~~ and the interface of the ~~image without lcd~~burning tool will prompt "'''found a MASKROM device'''"[[File:pi3b-img39.png]]</li><li>~~If you want to use LCD screen,~~ Then please ~~choose image with lcd~~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-~~img125~~alpha;"><li>Select '''rk3566_MiniLoaderAll.bin''' in the MiniLoader folder downloaded earlier, and click to open.~~png|281x62px]]~~</li>

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

[[File:pi3b-~~img135~~img68.png~~|415x99px~~]]

</div></ol><ol start="79" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~After opening~~ Then click '''Download'''[[File:pi3b-img128.png]]</li><li>The display after downloading '''~~SDDiskTool~~MiniLoaderAll.bin'''~~, if~~ is shown in the ~~TF card is recognized normally,~~ figure below[[File:pi3b-img140.png]]</li><li>Then select the ~~inserted disk~~ storage device ~~will be displayed in the "~~as '''~~Select Removable Disk Device~~EMMC'''~~" column. P~~, and then click Switch '''~~lease make sure that the displayed disk device is consistent with the drive letter of the TF card you want to burn~~Storage'''~~, if there~~ [[File:pi3b-img141.png]]</li><li>The display of successful switching is ~~no display, you can try to unplug~~ shown in the ~~TF card~~figure below</lip></olli>

[[File:pi3b-~~img136~~img142.png~~|267x228px~~]]</ol><ol start="13" 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="814" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~After confirming the drive letter, you can format the TF card first,~~ Then click the "'''~~restore disk button~~Firmware''' ~~in '''SDDiskTool,''' or use~~ " button to select the path of the ~~'''SD Card Formatter''' mentioned above~~ Android image that needs to ~~format the TF card~~be burned</li~~></ol~~>

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

<~~ol start~~div class="9figure" ~~style="list-style-type: decimal;"><li>Then start to write the Android image to the TF card<ol style="list-style-type: lower-alpha;"><li>First check "SD Boot" in "Select Function Mode"</li><li>Then select the path of the Android image in the "Select to upgrade firmware" column</li><li>Finally click the "Start Create" button to start burning the Android image to the TF card</li></ol></li></ol~~>

[[File:pi3b-~~img138~~img134.png~~|286x242px~~]]

</div></ol ~~start="10" style="list-style-type: decimal;"~~></li>~~After burning, you can exit the SDDiskTool software, and then you can pull out the TF card from the computer and insert it into the development board to start~~</liol></olspan>

~~[[File:pi3b-img139.png|288x244px]]~~=== How to burn Android11 image into eMMC via TF card ===

~~'''Note that all the following operations are performed on a Windows computer.'''</~~span~~big>~~== How to burn Android image to eMMC ==|}

~~'''Note, after burning~~ # The development board reserves an eMMC expansion interface. Before programming the ~~image into~~ system to eMMC, if you first need to purchase an eMMC module that matches the ~~test finds that it cannot be started, please clear~~ eMMC interface of the ~~SPIFlash and try again~~development board. ~~For~~ Then install the ~~method of clearing SPIFlash, please refer~~ eMMC module to~~''' [[\l|~~the development board. The eMMC module and the method of ~~using RKDevTool to clear SPIFlash]]'''.'''~~plugging into the development board are as follows:

~~=== Method of burning Android image into eMMC through USB2~~img62.~~0 burning port ===~~png|400px]]

~~'''Note that all the following operations are performed on a Windows computer.'''~~ ~~<ol style="list-style-type: decimal;">~~<li>The development board reserves an eMMC expansion interface. Before programming the system to eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board.~~The eMMC module and the method of plugging into the development board are as follows:</li></ol>~~ ~~[[File~~:~~pi3b-img61.png|115x84px]] [[File~~:~~pi3b-img62.png|120x87px]]~~ [[File:pi3b-img63.png|~~286x133px~~800px]]

<li>You also need to prepare a ~~good quality USB2~~TF card with 8GB or larger capacity. 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.~~0 male~~orangepi.org/html/hardWare/computerAndMicrocontrollers/service-toand-support/Orange-Pi-~~male~~ 3B.html '''Orange Pi data ~~cable~~download page'''], '''please make sure that the version of the SDDiskTool tool is the latest v1.72'''</li><li>Then download the Android image from [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi's download page''']<olstyle="list-style-type: lower-alpha;"><li>After opening the download link of the Android image, you can see the following two types of Android images, please select the image in '''the TF card and eMMC startup image folder''' to download</li>

[[File:pi3b-~~img16~~img124.png~~|141x138px|D6BB9058~~]] </div></ol><ol start="2" style="list-style-~~CDC3~~type: lower-~~42d7~~alpha;"><li>After entering '''the TF card and eMMC boot image folder''', you can see the following tow images, the difference between them is:<ol style="list-~~A7FC~~style-~~FBF630D886B7]]~~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</li>

~~</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~~[File:~~//www~~pi3b-img125.~~orangepi.org/html/serviceAndSupport/index.html '''Orange Pi's data download page'''~~png]]~~</li><li>Then download the Android image from '''[http://www.orangepi.org/html/serviceAndSupport/index.html Orange Pi's download page].'''~~<ol ~~style="list-style-type: lower-alpha;"~~>~~<li>After opening the download link of the Android image, you can see the following two types of Android images, please select the image in the '''TF card and eMMC startup image folder''' to download~~</li></ol>

</li></ol>

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

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

[[File:pi3b-img135.png]]<~~div class~~/ol><ol start="8" style="~~figure~~list-style-type: decimal;"><li>After opening '''SDDiskTool''', if the TF card is recognized normally, the inserted disk device will be displayed in the "'''Select Removable Disk Device'''" column. '''Please make sure that the displayed disk device is consistent with the drive letter of the TF card you want to burn''', if there is no display, you can try to unplug the TF card.</li>

[[File:pi3b-~~img124~~img136.png~~|340x108px|e6986fc9c8fc078e8cb6a9c39b76fb8~~]]</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]]</~~div~~ol><ol start="210" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~After entering~~ Then start to write the Android image into the ~~'''~~TF card ~~and eMMC startup image folder''', you can see the following two images, the difference between them is~~

<li>~~The first image~~ First confirm that the displayed drive letter is ~~dedicated~~ the drive letter corresponding to ~~HDMI display and supports 4K display. If you don’t use LCD screen, please download~~ the ~~image without lcd~~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>~~If you want~~ Finally click the "'''Start Create'''" button to ~~use lcd screen, please choose image with lcd~~start burning</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-~~img125~~img144.png~~|264x58px~~]]</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="514" style="list-style-type: decimal;"><li>~~Then use decompression software to decompress~~ When the HDMI monitor displays the following information, it means that the ~~compressed package~~ burning of the ~~downloaded~~ Android imageinto the eMMC has been completed. ~~Among~~ At this time, the ~~decompressed files~~TF card can be pulled out, ~~the file ending with ".img" is~~ and then the Android ~~image file, and~~ system in the ~~size is more than 1GB~~eMMC will start.</li>~~<li>Then use decompression software to decompress '''DriverAssitant_v5~~[[File:pi3b-img146.~~12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it~~png]]</pol><~~/li~~span id="how-to-burn-android-image-to-spiflashnvme-ssd"></olspan>

~~[[File:pi3b-img31.png|575x169px]]~~== How to burn Android image to SPIFlash+NVMe SSD ==

~~<ol start~~{| class="7wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that all the following operations are performed on a Windows computer.'''</big>|} <ol style="list-style-type: decimal;"><li>~~After opening '''DriverInstall.exe'''~~First, ~~the steps~~ you need to ~~install the Rockchip driver are as follows~~prepare an NVMe SSD solid state drive

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

[[File:pi3b-img73.png]]

</ol>

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

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

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

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

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

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

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

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

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

</div>

</ol>

<li>~~Then make sure that~~ After entering the ~~development board is not inserted into~~ '''SPIFlash-NVME SSD boot image folder''', you can see the ~~TF card and not connected to the power supply~~following two images. Their differences are:<~~/li~~ol style="list-style-type: none;"><li>~~Then press~~ a) The image without lcd is specially used for HDMI display and ~~hold the MaskROM button on~~ supports 4K display. If you do not use the ~~development board~~LCD screen, please download the ~~position of the MaskROM button on the development board is shown in the figure below:~~image without lcd</li><li>b) If you want to use LCD screen, please choose image with lcd</olp></li>

[[File:pi3b-~~img37~~img147.png~~|289x100px~~]]</ol></li></ol></li></ol><ol start="7" style="list-style-type: decimal;"><li>Then use the decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>

[[File:pi3b-img31.png]]</ol><ol start="48" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then connect~~ After opening '''DriverInstall.exe''', the ~~power supply of the Type-C interface~~ steps to install the ~~development board~~Rockchip driver are as follows<ol style="list-style-type: lower-alpha;"><li>Click the "'''Driver Installation'''" button</olli>

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

[[File:pi3b-img33.png]]</ol></li></ol><ol start="59" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~If the previous steps are successful, the development board will enter the~~ Then decompress '''~~MASKROM~~RKDevTool_Release_v3.15.zip''' ~~mode at~~ , this ~~time~~software does not need to be installed, ~~and the interface of the burning tool will prompt "~~just find '''~~found a MASKROM device~~RKDevTool'''~~"~~in the decompressed folder and open it</li> [[File:pi3b-~~img39~~img34.png~~|457x215px~~]]</pol><~~/li~~ol start="10" style="list-style-type: decimal;"><li>~~Then please select~~ After opening the '''~~Advanced Features~~RKDevTool'''~~[[File:pi3b-img126.png|458x138px]]</li><li>Then click~~ burning tool, because the computer is not connected to the ~~position shown in~~ development board through the ~~figure below[[File:pi3b~~USB2.0 male-to-~~img127.png|459x216px]]~~male data cable at this time, the lower left corner will prompt "'''No device found'''"</li~~></ol~~>

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

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

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

</div></ol>

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

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

[[File:pi3b-img38.png]]</ol><ol start="85" style="list-style-type: lower-alpha;"><li>~~Then click~~ If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''~~Upgrade Firmware~~found a MASKROM device'''" ~~column of the burning tool~~</li~~></ol~~>

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

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

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

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

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

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

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

~~'''Note that all the following operations are performed on~~ <ol start="2" style="list-style-type: decimal;"><li>First, you need to prepare a ~~Windows computer~~good quality USB2.~~'''~~0 male-to-male data cable</li>

# The development board reserves an eMMC expansion interface. Before programming the system to eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The eMMC module and the method of plugging into the development board are as follows:<div class="figure">

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

~~[[File:pi3b-img63.png|286x133px]]~~</div></ol><ol start="23" style="list-style-type: decimal;"><li>You also need to prepare a TF card with 8GB or larger capacity. The transmission speed of the TF card must be class10 or above. It is recommended to use a TF card of SanDisk and other brands</li>~~<li>Then use the card reader to insert the TF card into the computer</li~~><li>Then download the ~~SDDiskTool programming tool from the [http://www.orangepi.org/html/serviceAndSupport/index.html~~ Rockchip driver '''~~Orange Pi data download page~~DriverAssitant_v5.12.zip'''], and MiniLoader and the burning tool '''~~please make sure that the version of the SDDiskTool tool is the latest v1~~RKDevTool_Release_v3.15.72zip'''~~</li><li>Then download~~ from the ~~Android image from~~ [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/computerAndMicrocontrollers/service-and-support/~~index~~Orange-Pi-3B.html '''Orange Pi's data download page''']

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

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

</div></ol>

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

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

~~<ol start="6" style="list-style~~[[File:pi3b-~~type: decimal;">~~<li>Then use the decompression software to decompress the compressed package of the downloaded Android image. Among the decompressed files, the file ending with ".img" is the Android image file, and the size is more than 1GB</li>~~<li>Then use decompression software to decompress '''SDDiskTool_v1.72.zip''', this software does not need to be installed, just find '''SD_Firmware_Tool~~img150.~~exe''' in the decompressed folder and open it</li></ol>~~png]]

~~[[File~~</div>{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-| <big>'''Note that the "MiniLoader-~~img135~~things needed to burn the Linux image" folder is hereinafter referred to as the MiniLoader folder.~~png~~'''</big>|~~429x103px]]~~}</ol></li></ol><ol start="4" style="list-style-type: decimal;"><li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>

[[File:pi3b-img31.png]]</ol><ol start="85" style="list-style-type: decimal;"><li>After opening ~~'''SDDiskTool'''~~DriverInstall.exe, if the ~~TF card is recognized normally,~~ steps to install the ~~inserted disk device will be displayed in~~ Rockchip driver are as follows<ol style="list-style-type: lower-alpha;"><li>Click the "'''~~Select Removable Disk Device~~Driver Installation'''" ~~column. '''Please make sure that the displayed disk device is consistent with the drive letter of the TF card you want to burn''', if there is no display, you can try to unplug the TF card.~~button</li~~></ol~~>

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

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

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

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

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

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

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

~~[[File~~</div></ol><ol start="2" style="list-style-type:~~pi3b~~lower-~~img144.png|285x243px]]~~alpha;"><li>Make sure that the development board is not inserted into the TF card and not connected to the power supply</li><li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:</li>

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

[[File:pi3b-~~img145~~img38.png~~|430x247px~~]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li>

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

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

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

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

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

</li></ol>

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

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

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

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

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

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

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

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

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

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

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

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

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

[[File:pi3b-~~img147~~img156.png~~|305x58px~~]]</ol><ol start="3" style="list-style-type: decimal;"><li>The GND, TXD and RXD pins of the USB to TTL module need to be connected to the debugging serial port of the development board through a DuPont line</li>

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

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

~~<ol start="8" style="list-style-type~~: ~~decimal;"><li>After opening '''DriverInstall~~c.~~exe~~The '''~~, the steps to install the Rockchip driver are as follows~~<~~/p><ol~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<li>Click the "'''Driver Installation'''" button</li></ol></li></ol>~~ ~~[[File:pi3b-img32.png|286x150px]]~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>After waiting for a period~~ TX of ~~time, a pop-up window will prompt "'''driver installed successfully'''", and then click~~ the ~~"'''OK'''" button.</li></ol>~~ ~~[[File:pi3b-img33.png|296x154px]]~~ ~~<ol start="9" style="list-style-type: decimal;"><li>Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need~~ USB to TTL module is connected to ~~be installed, just find '''RKDevTool''' in~~ the ~~decompressed folder and open it~~TX</lispan>~~</ol>~~ ~~[[File:pi3b-img34.png|413x122px]]~~ ~~<ol start="10" style="list-style-type: decimal;"><li>After opening the~~ '''~~RKDevTool''' burning tool, because the computer is not connected to~~ of the development board ~~through the USB2.0 male-to-male data cable at this time, the lower left corner will prompt "'''No device found'''"</li>~~</ol> ~~[[File:pi3b-img35.png|402x189px]]~~ <ol start="114" style="list-style-type: decimal;"><li>~~Then start burning~~ The schematic diagram of connecting the ~~Android image~~ USB to ~~SPIFlash+NVMe SSD<ol style="list-style-type: lower-alpha;"><li>First, connect the development board~~ TTL module to the ~~Windows~~ computer ~~through the USB2.0 male-to-male data cable. The position of the USB2.0 programming port of~~ and the Orange Pi development board is ~~shown in the figure below~~as follows</li~~></ol></li></ol~~>

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

</div>

~~<ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~Make sure that~~ '''The TX and RX of the ~~development board is not inserted into~~ serial port need to be cross-connected. If you don't want to carefully distinguish the ~~TF card~~ order of TX and ~~not connected to~~ RX, you can connect the ~~power supply</li><li>Then press~~ TX and ~~hold~~ RX of the ~~MaskROM button on~~ serial port casually first. If there is no output in the ~~development board~~test, then exchange the ~~position~~ order of TX and RX, so there is always a the ~~MaskROM button on the development board~~ order is ~~shown in the figure below:~~right'''</pbig>|}</liol></olspan>

~~[[File:pi3b-img37.png|289x100px]]~~=== How to use the debugging serial port on the Ubuntu platform ===

~~<ol start~~{| class="4wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~Then connect the power supply of the Type-C interface to the development board~~'''There are many serial port debugging software that can be used under Linux, such as putty, ~~and power on~~minicom, ~~and then release the MaskROM button~~etc. The following demonstrates how to use putty.'''</~~li></ol~~big>|}

~~[[File:pi3b~~# First, insert the USB-~~img38~~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.~~png|305x94px]]~~Remember this node name, and then set the serial port software will be used

~~<ol start~~::{| class="5wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>If the previous steps are successful, the development board will enter the~~ |-| test@test:~$ '''~~MASKROM''' mode at this time, and the interface of the burning tool will prompt "~~ls /dev/ttyUSB*'''~~found a MASKROM device'''"</li></ol>~~

~~[[File:pi3b-img39.png~~/dev/ttyUSB0|~~443x208px]]~~}

<ol start="62" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~click~~ use the ~~&quot~~following command to install putty on Ubuntu PC</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''~~Upgrade Firmware~~sudo apt-get update'''~~" column of the burning tool</li></ol>~~

~~[[File~~test@test:~~pi3b~~~$ '''sudo apt-~~img132.png~~get install -y putty'''|~~442x208px]]~~}</ol><ol start="3" style="list-style-type: decimal;"><li>Then run putty, '''remember to add sudo permission'''</li>

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo putty'''|}</ol><ol start="74" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then click~~ After executing the ~~"'''Firmware'''" button to select~~ putty command, the ~~Android image to be burned~~following interface will pop up</li~~></ol~~>

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

[[File:pi3b-img159.png]]</ol><ol start="86" style="list-style-type: decimal;"><li>Then set the parameters of the serial port<ol style="list-style-type: lower-alpha;"><li>~~Finally, click the "Upgrade" button~~ Set Serial line to connect toas /dev/ttyUSB0（(Modified to ~~start burning. The burning process is shown in~~ the ~~figure below. You can see that the firmware will be burned to SPIFlash first~~corresponding node name, ~~and then burned to PCIE. After burning is completed, the Android system will start automatically.~~generally /dev/ttyUSB0）</li><li>Set Speed(baud) as '''1500000'''（Serial port baud rate）</li><li>Set Flow control as None</olp></li>

~~[[File:pi3b-img148.png|453x212px]]~~<div class="figure">

~~== Using RKDevTool to clear SPIFlash ==~~img160.png]]

~~# The position of SPI Flash on the development board is shown in the figure below~~ ~~[[File:pi3b-img76.png|263x193px]]~~</div></ol></li></ol><ol start="27" style="list-style-type: decimal;"><li>~~First~~After setting the setting interface of the serial port, ~~you need~~ return to ~~prepare a good quality USB2.0 male~~the Session interface<ol style="list-tostyle-type: lower-~~male data cable~~alpha;"><li>First select the Connection type as Serial</li><li>Then click the Open button to connect to the serial port</olp></li>

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

</div>~~<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 [http://www.orangepi.org/html/serviceAndSupport/index.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>

</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]]<~~div class~~/ol>

~~[[File:pi3b-img149.png|342x56px|1691401357374]]~~=== How to use the debugging serial port on Windows platform ===

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

<li>~~Then~~ After entering the MobaXterm download ~~all the files below~~page, click '''GET XOBATERM NOW!'''</li~~></ol~~>

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

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

[[File:pi3b-img165.png]]</ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>After downloading, use decompression software to decompress the downloaded compressed package, you can get the executable software of MobaXterm, and then double-click to open</li> [[File:pi3b-img166.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>After opening the software, the steps to set up the serial port connection are as follows<ol style="list-style-type: lower-alpha;"><li>Open the session settings interface</li><li>Select the serial port type</li><li>Select the port number of the serial port (select the corresponding port number according to the actual situation)</~~div~~p></li><li>Select the baud rate of the serial port as '''~~Note that~~ 1500000'''</li><li>Finally click the "~~MiniLoader-things needed to burn the Linux image~~'''OK'''" ~~folder is hereinafter referred~~ button to as complete the ~~MiniLoader folder.'''~~setting</li>

<~~ol start~~div class="4figure" ~~style="list-style-type: decimal;"><li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li></ol~~>

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

~~<ol start="5" style="list-style-type: decimal;"><li>After opening DriverInstall.exe, the steps to install the Rockchip driver are as follows~~~~<ol style="list-style-type: lower-alpha;"><li>Click the "'''Driver Installation'''" button</li~~div></ol>

</li></ol>

<li>After clicking the "'''OK'''" button, you will enter the following interface. At this time, start the development board and you can see the output information of the serial port</li>

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

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

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

~~<ol start~~=~~"6" style~~=~~"list-style-type: decimal;"><li>Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool'''~~ Instructions for using the 5v pin in the ~~decompressed folder and open it</li></ol>~~40pin interface of the development board to supply power ==

~~[[File~~{| class="wikitable" style="background-color:~~pi3b~~#ffffdc;width:800px;" |-| <big>'''The power supply method we recommend for the development board is to use the 5V/3A Type C interface power cord to plug into the Type-C power interface of the development board for power supply. If you need to use the 5V pin in the 40pin interface to power the development board, please make sure that the power cord and power adapter used can meet the power supply requirements of the development board. If the use is unstable, please switch back to the Type-~~img34~~C power supply.~~png~~'''</big>|~~467x138px]]~~}

~~<ol start="7" style="list-style-type: decimal;"><li>After opening the '''RKDevTool''' burning tool, because the computer has not connected to the development board through the USB2.0 male-to-male data cable at this time~~# First, ~~the lower left corner will prompt "'''No device found'''"</li></ol>~~ ~~[[File:pi3b-img35.png|402x189px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>Then~~ you ~~can start to clear the content in SPI FLASH<ol style="list-style-type: lower-alpha;"><li>First, connect the development board~~ need 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~~ prepare a power cord as shown in the figure below~~</li></ol></li></ol>~~

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

</div>

~~<ol start~~::{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~Make sure that the development board is not inserted into the TF card and not connected to~~ '''Please purchase 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~~ cord shown in the ~~figure below:~~picture above by yourself'''</~~p></li></ol~~big>|}

~~[[File~~<ol start="2" style="list-style-type:~~pi3b~~decimal;"><li>Use the 5V pin in the 40pin interface to supply power to the development board. The connection method of the power line is as follows<ol style="list-~~img37.png|289x100px]]~~style-type: lower-alpha;"><li>The USB A port of the power cord shown in the above picture needs to be plugged into the 5V/3A power adapter connector ('''please do not plug into the computer's USB port for power supply''')</li><li>The red DuPont line needs to be plugged into the 5V pin of the development board 40pin</li><li>The black Dupont wire needs to be inserted into the GND pin of the 40pin interface</li><li>The position of the 5V pin and GND pin of the 40pin interface on the development board is shown in the figure below, '''remember not to reverse the connection'''</li>

[[File:pi3b-img170.png]]</ol ~~start="4" style~~></li></ol><li>Then connect the power supply~~ of ~~the Type~~-~~C interface to the development board,~~ ubuntudebian-server-and ~~power on, and then release the MaskROM button</li-xfce-desktop-system"></olspan>

~~[[File:pi3b-img38.png|305x94px]]~~= '''Instructions for use of Ubuntu/Debian Server and Xfce desktop system''' =

~~<ol start~~{| class="5wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~If the previous steps are successful, the development board will enter the~~ '''~~MASKROM''' mode at~~ The content of this ~~time, and~~ chapter is written based on the ~~interface~~ images of the ~~burning tool will prompt "'''found a MASKROM device~~Linux server version and the xfce desktop version.'''~~"~~</~~li></ol~~big>|}

~~[[File:pi3b~~== Supported Linux image types and kernel versions ==

~~<ol start~~{| class="6wikitable" style="~~list~~width:800px;text-~~style-type~~align: ~~lower-alpha~~center;">~~<li>Then please select~~ |-|'''~~Advanced Features~~Linux image type'''~~[[File:pi3b~~|'''kernel version'''|'''server version'''|'''desktop version'''|-|'''Debian 11 -~~img126~~Bullseye'''|'''Linux5.~~png~~10'''|'''support'''|~~458x138px]]</li>~~'''support'''~~<li>Then click the position shown in the figure below~~|-~~[[File:pi3b~~|'''Ubuntu 20.04 -~~img127~~Focal'''|'''Linux5.~~png~~10'''|~~459x216px]]</li>~~'''support'''~~<li>Select~~ |'''~~rk3566_MiniLoaderAll~~support'''|-|'''Ubuntu 22.04 - Jammy'''|'''Linux5.~~bin~~10'''|'''support''' ~~in the~~ |'''~~MiniLoader~~support''' ~~folder you downloaded earlier, and click Open</li></ol>~~|}

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

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

|}

<li>~~After downloading~~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, ~~use decompression software to decompress~~ which is not part of the Linux command, so when entering the command in the ~~downloaded compressed package~~Linux system, ~~you can get~~ please do not enter the ~~executable software~~ content of ~~MobaXterm, and then double-click to open~~the red font part</li>{| class="wikitable" style="width:800px;" |-| '''orangepi@orangepi:~$</olspan>sudo apt update'''

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

'''test@test:~$ ssh [mailto:root@192.168.1.36 root@192.168.1.]xxx'''

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

|}

</ol>

<li>'''root@orangepi:~$''' The prompt indicates that this command is entered in '''the Linux system of the development board'''. The $ at the end of the prompt indicates that the current user of the system is a normal user. When executing a privileged command, you need to add '''sudo'''</li>

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

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

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

</li></ol>

<li>~~After opening the software,~~ What are the ~~steps~~ commands that need to ~~set up the serial port connection are as follows~~be entered?

<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~~As shown below, ~~please use~~ '''~~Driver Master~~the black bold part''' is the command that needs to ~~scan~~ be input, and ~~install~~ the ~~driver for~~ content below the ~~USB to TTL serial port chip</li><li>Select~~ command is the ~~baud rate~~ output content (some commands have output, some may not), and this part of the ~~serial port as '''1500000'''~~content does not need to be input</li>~~<li>Finally click the &quot~~{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''OKcat /boot/orangepiEnv.txt'''~~" button to complete the setting</li></ol></li></ol>~~

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

~~[[File:pi3b-img167.png|575x438px|11]]~~bootlogo=false

'''console=serial</~~div~~span>'''|}</ol><ol start="42" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~After clicking~~ 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 "~~'''OK'''~~\" ~~button~~of each line needs to be removed, ~~you will enter~~ this is not part of the ~~following interface~~command. ~~At this time~~In addition, ~~start the development board and you can see the output information~~ there are spaces in different parts of the ~~serial port~~command, please don't miss it</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''echo \'''

~~<div class~~'''"deb [arch=~~"figure">~~$(dpkg --print-architecture) \'''

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

<'''https:/~~div><~~/~~span>== Instructions for using the 5v pin in the 40pin interface of the development board to supply power ==~~download.docker.com/Linux/debian \'''

'''~~The power supply method we recommend for the development board is to use the 5V~~$(lsb_release -cs) stable" | sudo tee /etc/~~3A or 5V~~apt/~~4A Type C interface power cord to plug into the Type-C power interface of the development board for power supply~~sources. 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 boardlist. ~~If the use is unstable, please switch back to the Type-C power supply~~d/docker.list > /dev/null'''|}</ol></li></ol>

~~# First, you need to prepare a power cord as shown in the figure below~~== Linux system login instructions ==

<~~div class~~span id="~~figure~~linux-system-default-login-account-and-password">=== Linux system default login account and password ===

~~[[File~~{| class="wikitable" style="width:800px;text-align:~~pi3b~~center;"|-|'''Account'''|'''Passport'''|-~~img169.png~~|~~151x108px~~'''root'''|~~C:\Users\~~'''orangepi~~\Desktop\用户手册插图\Pi5 Plus\未标题~~'''|-~~7.jpg未标题-7]]~~|'''orangepi'''|'''orangepi'''|}

~~</div>'''Please purchase the power cord shown in the picture above by yourself'''~~ ~~<ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Use~~ '''Note that when entering the ~~5V pin in the 40pin interface to supply power to the development board. The connection method of the power line is as follows~~password, <~~/p><ol~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<li>The USB A port~~ the specific content of the ~~power cord shown in the above picture needs to~~ entered password will not be ~~plugged into~~ displayed on the 5Vscreen</~~3A or 5V4A power adapter connector ('''~~span>, please do not ~~plug into the computer’s USB port for power supply~~think that there is any fault, just press Enter after inputting.''')</~~p></li~~big>~~<li>The red DuPont line needs to be plugged into the 5V pin of the development board 40pin</li>~~|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-~~<li>The black Dupont wire needs to be inserted into the GND pin of the 40pin interface</li>~~| <libig>~~The position of~~ '''When the ~~5V pin and GND pin of the 40pin interface on the development board~~ wrong password is prompted, or there is ~~shown in~~ a problem with the ~~figure below~~ssh connection, ~~remember not to reverse~~ please note that as long as you are using the ~~connection~~Linux image provided by Orange Pi, </pspan style="color:#FF0000">please do not suspect that the above password is wrong</lispan>, but look for other reasons.'''</olbig>~~</li></ol>~~|}

~~[[File:pi3b~~

~~~~===

= # The Linux system automatically logs in to the terminal by default, and the default login user name is '''~~Instructions for use of Ubuntu~~orangepi</~~Debian Server and Xfce desktop system~~span>''' =

~~'''The content of this chapter is written based on the images of the Linux server version and the xfce desktop version~~::[[File:pi3b-img171.~~'''~~png]]

<~~span id~~ol start="~~supported-linux-image-types~~2" style="list-~~and~~style-~~kernel-versions~~type: decimal;"><li>Use the following command to set the root user to automatically log in to the terminal</~~span~~li>~~== Supported Linux image types and kernel versions ==~~ {| class="wikitable" style="width:800px;"

|-

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

|-

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

|-

|}

</ol>

=== Instructions for automatic login of Linux desktop version system === # After the desktop system starts, it will automatically log in to the desktop without entering a password <~~span id~~div class="~~linux-system-adaptation~~figure">~~== Linux System adaptation ==~~::[[File:pi3b-img172.png]]

</div><ol start="2" style="list-style-type: decimal;"><li>Run the following command to prohibit the desktop system from automatically logging into the desktop</li>{| class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~Function~~sudo disable_desktop_autologin.sh'''|~~'''Debian11'''~~}</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|~~'''Ubuntu20~~password]] is required to enter the system<div class="figure"> [[File:pi3b-img173.~~04'''~~png]] </div></li></ol> === The setting method of root user automatic login in Linux desktop version system === # Execute the following command to set the desktop system to automatically log in as the root user ::{|~~'''Ubuntu22.04'''~~class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''~~USB2~~sudo desktop_login.~~0x3~~sh root'''|~~'''OK'''~~} <ol start="2" style="list-style-type: decimal;"><li>Then restart the system, and the root user will automatically log in to the desktop</li> [[File:pi3b-img174.png]]~~|'''OK'''~~{|~~'''OK'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

|<big>'''~~USB3~~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.~~0x1~~'''|'''OKAlso note that this is not a bug, since pulseaudio is not allowed to run as root.'''</big>|~~'''OK'''~~}</ol><ol start="3" style="list-style-type: decimal;"><li>Execute the following command to set the desktop system to log in automatically with the orangepi user again</li> {|~~'''OK'''~~class="wikitable" style="width:800px;"

|-

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

|-

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

|-

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

|-

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

|-

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

|-

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

|-

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

|-

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

|-

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

|-

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

|-

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

|-

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

|-

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

|-

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

|-

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

|-

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

|-

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

|-

|~~'''headphone playback'''|'''OK'''|'''OK'''~~|orangepi@orangepi:~$ '''OKip addr show wlan0'''|-~~|'''headphone recording'''~~11: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''LED Light'''|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''RTC'''|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''GPU'''|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''NPU'''|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''VPU'''|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''watchdog test'''|'''OK'''|'''OK'''|'''OK'''~~|-~~|'''Chromium Hard solution video'''|'''OK'''|'''OK'''|'''OK'''~~|}:link/ether 23:8c:d6:ae:76:bb brd ff:ff:ff:ff:ff:ff

:inet '''192.168.1.11~~== The format of Linux commands in this manual ==~~'''/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0

~~# In this manual, all commands that need to be entered in the Linux system will be marked with the following box~~::valid_lft 259192sec preferred_lft 259192sec

~~As shown below, the content in the yellow box indicates the content that needs special attention, except for the commands in it.~~:inet6 240e:3b7:3240:c3a0:c401:a445:5002:ccdd/64 scope global dynamic noprefixroute

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

~~'''orangepi@orangepi~~:~~~$ sudo apt update'''~~inet6 fe80::42f1:6019:a80e:4c31/64 scope link noprefixroute

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

~~'''test~~{| class="wikitable" style="width:800px;" |-| orangepi@~~test~~orangepi:~$ ~~ssh [mailto:root@192.168.1.36 root@192.168~~'''ping www.1orangepi.~~]xxx~~org -I wlan0'''

~~'''root@test~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0:~~~# ls'''~~56(84) bytes of data.

~~<ol start="2" style="list-style-type: lower-alpha;"><li>'''root@orangepi:~$''' The prompt indicates that this command is entered in '''the Linux system of the development board'''~~64 bytes from 182.92.236. ~~The $ at the end of the prompt indicates that the current user of the system is a normal user~~130 (182. ~~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~~92. ~~The $ at the end of the prompt indicates that the current user of the system is an ordinary user~~236. ~~When executing privileged commands, sudo needs to be added '''sudo'''</li><li>'''root@test~~130):~~~#''' 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~~icmp_seq=1 ttl=52 time=43. ~~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>~~5 ms

~~<ol start~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=~~"3" style~~2 ttl=~~"list-style-type: decimal;"><li>What are the commands that need to be entered?<ol style~~52 time=~~"list-style-type: lower-alpha;">~~<li>As shown below, '''the black bold part''' is the command that needs to be input, and the content below the command is the output content (some commands have output, some may not), and this part of the content does not need to be input</li></ol>~~</li></ol>~~41.3 ms

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

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

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

~~'''console=serial'''~~^C

~~<ol start="2" style="list~~-~~style~~-~~type: lower~~-~~alpha;"><li>As shown below, some commands cannot be written in one line and will be placed on the next line~~www. ~~As long as the black and bold parts are all commands that need to be input~~orangepi. When these commands are entered into one line, the last "\" of each line needs to be removed, this is not part of the command. In addition, there are spaces in different parts of the command, please don’t miss it</li></ol>org ping statistics ---

~~orangepi@orangepi:~$ '''echo \'''~~5 packets transmitted, 5 received, 0% packet loss, time 4006ms

~~'''"deb [arch~~rtt min/avg/max/mdev =~~$(dpkg~~ 41.321/44.864/48.834/2.484 ms|}</ol>

~~'''signed-by~~=~~/usr/share/keyrings/docker-archive-keyring.gpg] \'''~~=== The server image connects to WIFI in a graphical way ====

~~'''https~~<ol style="list-style-type:~~//download.docker.com/~~decimal;"><li>First log in to the Linuxsystem, there are the following three ways</~~debian \~~li><ol style="list-style-type: lower-alpha;"><li>If the development board is connected with a network cable, you can remotely log in to [[Orange Pi 3B#SSH remote login development board|''' the Linux system through ssh'''~~$(lsb_release -cs) stable" | sudo tee~~ ]]</~~etc~~p></~~apt/sources.list.d/docker.list > /dev/null'''~~li><~~span id="linux-~~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~~-login-instructions"~~(please use MobaXterm for the serial port software, and the minicom cannot display the graphical interface)</~~span~~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:~$ '''sudo reboot'''~~# Click the network configuration icon in the upper right corner of the desktop (please do not connect the network cable when testing WIFI)

~~<ol start="3" style="list-style-type~~: ~~decimal;"><li>The steps to reopen the desktop are as follows~~:~~<ol style="list-style-type~~[[File: ~~lower~~pi3b-~~alpha;"><li>First enter the following command on the command line，'''Please remember to add sudo permission'''</li></ol></li></ol>~~img183.png]]

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~$ decimal;"><li>Click '''~~sudo systemctl start lightdm.service~~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><ol start="23" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~After~~ Then enter the password of the ~~command is executed~~WIFI hotspot, ~~the desktop will be displayed~~and then click '''Connect''' to start connecting to WIFI</li~~></ol~~>

[[File:pi3b-img185.png]]</ol><~~span id~~ol start="~~onboard~~4" style="list-~~led~~style-~~light-test-instructions~~type: decimal;"><li>After connecting to WIFI, you can open the browser to check whether you can access the Internet. The entrance of the browser is shown in the figure below</~~span~~li>~~== Onboard LED Light Test Instructions ==~~

~~# There are three LED lights on~~ [[File:pi3b-img186.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>If you can open other web pages after opening the ~~development board~~browser, ~~one green light, one red light, and one PCIe light. The location~~ it means that the WIFI connection is ~~shown in the figure below:~~normal</li>

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

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

~~</div><ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <~~li><p~~big>'''~~As long as the development board is powered on, the red LED light will always be on, which is controlled~~ Please do not set a static IP address by modifying the ~~hardware and cannot be turned off by the software'''<~~/~~p><~~etc/~~li><li>The green LED light will keep blinking after the kernel is started, which is controlled by software.<~~network/~~li><li>The PCIe indicator will flash when there is data transmission on the PCIe interface~~interfaces configuration file.'''</~~p></li~~big>~~<li>The method of setting the green light on and off and flashing is as follows</li></ol>~~|}

~~'''Note that~~ ==== Use the ~~root user.'''~~nmtui command to set a static IP address ====

~~<ol style="list-style-type: lower-alpha;"><li>~~# First ~~enter~~ run the ~~setting directory of the green light</li></ol>~~'''nmtui''' command

~~root~~::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~# $ '''~~cd /sys/class/leds/status~~nmtui'''|}

<ol start="2" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The command to set the green light to stop flashing is as follows~~Then select '''Edit a connection''' and press Enter</li~~></ol~~>

~~root@orangepi~~[[File:pi3b-img188.png]]</~~sys/class/leds/work#~~ 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 '''~~echo none > trigger~~Wired connection 1'''.</li>

[[File:pi3b-img189.png]]</ol><ol start="34" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The command to set~~ Then select '''Edit''' with the '''Tab''' key and press the ~~green light to be on is as follows~~Enter key</li~~></ol~~>

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

[[File:pi3b-img191.png]]</ol><ol start="46" 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 ~~flash 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 heartbeat > trigger'''~~li>

[[File:pi3b-img193.png]]<~~span id~~/ol><ol start="8" style="~~network~~list-~~connection~~style-~~test~~type: decimal;"><li>Then move the cursor to the '''<Show>'''</~~span~~li>~~== Network connection test ==~~

[[File:pi3b-img194.png]]</ol><~~span id~~ol start="~~ethernet~~9" style="list-~~port~~style-~~test~~type: decimal;"><li>Then press Enter, the following setting interface will pop up after entering</~~span~~li>~~=== Ethernet port test ===~~

~~# First, insert one end of~~ [[File:pi3b-img195.png]]</ol><ol start="10" style="list-style-type: decimal;"><li>Then you can set the ~~network cable into the Ethernet interface of the development board~~IP address (Addresses), gateway (Gateway) and ~~connect~~ DNS server address in the position shown in the figure below (there are many other ~~end of the network cable to the router, and ensure that the network is unblocked# After the system starts~~setting options in it, ~~it will automatically assign an IP address to the Ethernet card through DHCP~~please explore by yourself), '''~~No other configuration is required'''~~Please set it according to ~~view~~ your specific needs, the ~~IP address~~ value set in the ~~Linux system of the development board~~ figure below is ~~as follows~~just an example'''</li>

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

2[[File: ~~eth0~~pi3b-img197.png]]</ol><ol start="12" style="list-style-type: decimal;"><li>Then click'''<~~BROADCAST,MULTICAST,UP,LOWER_UP~~Back> ~~mtu 1500 qdisc mq state UP group default qlen 1000~~''' to return to the previous selection interface</li>

~~link~~[[File:pi3b-img198.png]]</~~ether 4a~~ol><ol start="13" style="list-style-type:~~fe:2b:3d:17:1c brd ff:ff:ff:ff:ff:ff~~decimal;"><li>Then select '''Activate a connection''', then move the cursor to'''<OK>''', and finally click Enter</li>

~~inet~~ [[File:pi3b-img199.png]]</ol><ol start="14" style="list-style-type: decimal;"><li>Then select the network interface that needs to be set, such as '''Wired connection 1''', then move the cursor to'''<Deactivate>''', and press Enter to disable '''~~192.168.~~Wired connection 1~~.150~~'''</~~24 brd 192.168.1.255 scope global dynamic noprefixroute eth0~~li>

~~valid_lft 43150sec preferred_lft 43150sec~~[[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 '''Wired connection 1''', so that the static IP address set earlier will take effect</li>

~~inet6 fe80~~[[File:pi3b-img201.png]]</ol><ol start="16" style="list-style-type:~~9a04:3703:faed:23be~~decimal;"><li>Then you can exit nmtui through the'''<Back>''' and '''Quit''' buttons</~~64 scope link noprefixroute~~li>

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

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~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~~ip addr show eth0'''

~~orangepi@orangepi~~3:~~~$ '''ifconfig'''~~eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~Command 'ifconfig' is available in the following places~~:link/ether 5e:ac:14:a5:92:b3 brd ff:ff:ff:ff:ff:ff

* :inet '''192.168.1.177</~~sbin~~span>'''/~~ifconfig~~24 brd 192.168.1.255 scope global noprefixroute eth0

* /usr/sbin/ifconfig ~~The command could not be located because '/sbin~~:~~/usr/sbin' is not included in the PATH environment variable.~~:valid_lft forever preferred_lft forever

~~This is most likely caused by the lack of administrative privileges associated with your user account.~~:inet6 241e:3b8:3240:c3a0:e269:8305:dc08:135e/64 scope global dynamic noprefixroute

~~ifconfig~~: ~~command not found~~:valid_lft 259149sec preferred_lft 172749sec

~~'''There are three ways to check the IP address after the development board starts~~:~~'''~~inet6 fe80::957d:bbbe:4928:3604/64 scope link noprefixroute

~~# '''Connect~~ ::valid_lft forever preferred_lft forever|}</ol><ol start="18" style="list-style-type: decimal;"><li>Then you can test the ~~HDMI display, then log in to~~ connectivity of the ~~system and use the ip addr show eth0 command~~ network to ~~view~~ check whether the IP addressis configured OK, and the '''# ping'''~~Enter the ip addr show eth0~~ command ~~in the debugging serial terminal to view~~ can be interrupted through the ~~IP address~~shortcut key '''# '''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:Ctrl+C'''</li>

~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~upper-alpha~~800px;">~~<li>~~|-| orangepi@orangepi:~$ '''~~First check whether the Linux system has started normally~~ping 192.168. ~~If the green light of the development board is blinking, it is generally started normally~~1. ~~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 (~~47 -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~~eth0'''~~</li></ol>~~

~~'''In addition, it should be noted that the development board DHCP automatically assigns an IP address without any settings~~PING 192.168.1.47 (192.168.1.47) from 192.168.1.188 eth0: 56(84) bytes of data.~~'''~~

~~<ol start~~64 bytes from 192.168.1.47: icmp_seq=~~"4" style~~1 ttl=~~"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>~~64 time=0.233 ms

~~orangepi@orangepi~~64 bytes from 192.168.1.47:~~~$ '''ping www.baidu~~icmp_seq=2 ttl=64 time=0.~~com -I eth0'''~~263 ms

~~PING www.a.shifen.com (14.215.177.38)~~ 64 bytes from 192.168.1.~~12 eth0~~47: ~~56(84) bytes of data~~icmp_seq=3 ttl=64 time=0.273 ms

64 bytes from 14192.~~215~~168.~~177~~1.~~38 (14.215.177.38)~~47: icmp_seq=1 4 ttl=56 64 time=60.74 269 ms

64 bytes from 14192.~~215~~168.~~177~~1.~~38 (14.215.177.38)~~47: icmp_seq=2 5 ttl=56 64 time=60.80 275 ms

~~64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq=3 ttl=56 time=6.26 ms~~^C

~~64 bytes from 14~~--- 192.~~215~~168.~~177~~1.~~38 (14.215.177.38): icmp_seq=4 ttl=56 time=7.27 ms~~47 ping statistics ---

^C5 packets transmitted, 5 received, 0% packet loss, time 4042ms

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

~~4 packets transmitted, 4 received, 0% packet loss, time 3002ms~~==== Use the nmcli command to set a static IP address ====

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

<~~span id~~ol start="~~wifi~~3" style="list-~~connection~~style-~~test~~type: decimal;"><li>Then enter the following command, where</~~span~~li>~~=== WIFI connection test ===~~

:a. '''~~Please do not connect~~ "Wired connection 1"''' means to ~~WIFI by modifying~~ set the static IP address of the ~~/etc/network/interfaces configuration file~~Ethernet port. ~~There will be problems connecting~~ If you need to set the static IP address of the WIFI, please change it to the corresponding name of the WIFI network ~~in this way.~~interface (you can get it through the '''nmcli con show'''command)

~~==== WIFI The server image connects~~ be set, which can be modified to ~~WIFI through commands ====~~the value you want to set

:c. '''When the development board is not connected to Ethernet, not connected to HDMI display, but only connected to the serial port, it is recommended to use the commands demonstrated in this section to connect to the WIFI network. Because nmtui can only display characters in some serial port software (such as minicom), and cannot display the graphical interface normally. Of course, if the development board is connected to an Ethernet or HDMI display, you can also use the commands demonstrated in this section to connect to the WIFI networkipv4.gateway'''indicates the address of the gateway

~~<ol style~~::{| class="~~list-style-type: decimal;~~wikitable">~~<li>First log in to the Linux system, there are the following three ways<ol~~ style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>If the development board is connected with a network cable, you can remotely log in to the Linux system through ssh</li>~~|-~~<li>If the development board is connected to the debugging serial port, you can use the serial port terminal to log in to the Linux system</li>~~| ~~<li>If the development board is connected to the HDMI display, you can log in to the Linux system through the terminal displayed on the HDMI</li></ol></li><li>First use the~~ orangepi@orangepi:~$ '''nmcli ~~dev wifi command to scan the surrounding WIFI hotspots</li></ol>~~con mod "Wired connection 1" \'''

~~orangepi@orangepi:~$~~ '''~~nmcli dev wifi~~ipv4.addresses "192.168.1.110" \'''

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

~~[[File:pi3b-img176~~'''ipv4.~~png|575x250px|选区_011]]~~dns "8.8.8.8" \'''

'''ipv4.method "manual"'''|}</~~div~~ol><ol start="34" style="list-style-type: decimal;"><li>Then restart the 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 Linux system and use the ~~nmcli~~ '''ip addr show eth0''' command to ~~connect~~ see that the IP address has been set to the ~~scanned WIFI hotspot, where:~~desired value</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ip addr show eth0'''

~~a. '''wifi_name''' needs to be replaced with the name of the WIFI hotspot you want to connect to~~3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~b. '''wifi_passwd''' needs to be replaced with the password of the WIFI hotspot you want to connect to~~:link/ether 5e:ae:14:a5:91:b3 brd ff:ff:ff:ff:ff:ff

~~orangepi@orangepi~~:~$ inet '''~~nmcli dev wifi connect wifi_name password wifi_passwd~~192.168.1.110'''/32 brd 192.168.1.110 scope global noprefixroute eth0

~~Device 'wlan0' successfully activated with 'cf937f88-ca1e-4411-bb50-61f402eef293'.~~::valid_lft forever preferred_lft forever

~~<ol start="4" style="list-style-type~~: ~~decimal;"><li>You can view the IP address of wifi through the '''ip addr show wlan0''' command</li><~~inet6 240e:3b7:3240:c3a0:97de:1d01:b290:fe3a/~~ol>~~64 scope global dynamic noprefixroute

~~orangepi@orangepi~~:~~~$ '''ip addr show wlan0'''~~:valid_lft 259183sec preferred_lft 172783sec

11: ~~wlan0~~inet6 fe80: ~~<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~:3312:861a:a589:d3c/64 scope link noprefixroute

~~link/ether 23~~:8c:~~d6:ae:76:bb brd ff:ff:ff:ff:ff:ff~~valid_lft forever preferred_lft forever|}</ol>

~~inet '''192.168.1.11'''/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0~~== SSH remote login development board ==

~~valid_lft 259192sec preferred_lft 259192sec~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Linux systems enable ssh remote login by default and allow the root user to log in to the system. 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.'''</big>|}

~~inet6 240e:3b7:3240:c3a0:c401:a445:5002:ccdd~~</~~64 scope global dynamic noprefixroute~~span>=== SSH remote login development board under Ubuntu ===

~~valid_lft 259192sec preferred_lft 172792sec~~# Obtain the IP address of the development board# Then you can remotely log in to the Linux system through the ssh command

~~inet6 fe80~~::~~42f1~~{| class="wikitable" style="width:~~6019~~800px;" |-| test@test:~~a80e~~~$ '''ssh [mailto:~~4c31/64 scope link noprefixroute~~root@192.168.1.36 root@192.168.1.]xxx'''        (Need to be replaced with the IP address of the development board)

~~valid_lft forever preferred_lft forever~~root@192.168.1.xx's password:        (Enter the password here, the default password is orangepi)|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''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>|}::{| 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.'''</big>|}

~~5) Use the '''ping''' command~~ <ol start="3" style="list-style-type: decimal;"><li>After successfully logging in to ~~test the connectivity of~~ the ~~wifi network~~system, ~~and~~ the ~~'''ping''' command can be interrupted through~~ display is as shown in the ~~shortcut key '''Ctrl+C'''~~figure below</li>

~~orangepi@orangepi:~$ '''ping www.orangepi.org -I wlan0'''~~<div class="figure">

~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0~~[[File: ~~56(84) bytes of data~~pi3b-img204.png]]

~~64 bytes from 182.92.236.130 (182~~</div>{| class="wikitable" style="background-color:#ffffdc;width: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.92If 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.~~236.130)~~Is it possible to connect: ~~icmp_seq=1 ttl=52 time=43.5 ms~~'''

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

~~64 bytes from 182.92.236.130 (182.92.236.130)~~root@orangepi: ~~icmp_seq=3 ttl=52 time=44~~~# '''reset_ssh.~~9 ms~~sh'''

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

~~64 bytes from 182~~'''If it still doesn't work, try to reset the system.~~92.236.130 (182.92.236.130): icmp_seq=5 ttl=52 time~~'''</big>|}</ol>

^C=== SSH remote login development board under Windows ===

~~--- www.orangepi.org ping statistics ---~~# 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

~~5 packets transmitted, 5 received, 0% packet loss, time 4006ms~~::a. Open '''Session'''

~~rtt min/avg/max/mdev = 41~~::b.~~321/44.864/48.834/2.484 ms~~Then select '''SSH''' in '''Session Setting'''

~~==== The server image connects to WIFI in a graphical way ====~~the '''Remote host'''

~~1) First log in to~~ ::d. Then enter the user name '''root''' or '''orangepi''' of the Linux system~~, there are the following three ways~~in '''Specify username'''

~~<ol style="list-style-type~~: ~~lower-alpha;"><li>If the development board is connected with a network cable, you can remotely log in to [[\l|the Linux system through ssh]]</li>~~<li>If the development board is connected to the debugging serial port, you can use the serial port terminal to log in to the Linux system (please use MobaXterm for the serial port software, 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>~~:e. Finally click '''OK'''

<~~!-- --~~div class="figure"># ~~# Then enter the nmtui command in the command line to open the wifi connection interface~~

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

</div>

<li>~~Enter~~ Then you will be prompted to enter a password. The default passwords for root and orangepi users are orangepi</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that when entering the password, the specific content of the ~~nmtui command to open~~ entered password will not be displayed on the ~~interface as shown below~~screen</lispan>, please do not think that there is any fault, just press Enter after inputting.'''</olbig>|} <div class="figure">

[[File:pi3b-~~img177~~img206.png~~|345x215px~~]]

</div></ol>

<li>~~Select '''Activate a connect''' and press Enter~~After successfully logging in to the system, the display is as shown in the figure below</li~~></ol~~>

[[File:pi3b-~~img178~~img207.png~~|349x216px~~]]</ol>

~~<ol start~~=~~"5" style~~=~~"list-style-type: decimal;"><li>Then you can see all~~ The method of uploading files to the ~~searched WIFI hotspots</li></ol>~~Linux system of the development board ==

<~~div class~~span id="~~figure~~how-to-upload-files-to-the-development-board-linux-system-in-ubuntu-pc">=== How to upload files to the development board Linux system in Ubuntu PC ===

~~[[File:pi3b~~==== How to upload files using the scp command ====

~~</div><ol start="6" style="list-style-type: decimal;"><li>Select~~ # Use the ~~WIFI hotspot you want~~ scp command to ~~connect~~ upload files from the Ubuntu PC to~~, then use~~ the ~~Tab key to position~~ Linux system of the ~~cursor on '''Activate''' and press Enter</li></ol>~~development board. The specific commands are as follows

~~<div class="figure">~~::a. '''file_path''': need to be replaced with the path of the file to be uploaded

~~[[File~~:~~pi3b-img180~~:b.~~png|474x298px|17]]~~ ~~</div><ol start="7" style="list-style-type: decimal;"><li>Then a dialog box for entering a password will pop up, enter the corresponding password in~~ '''~~Password~~orangepi''' : It is the user name of the Linux system of the development board, and ~~press Enter to start connecting to WIFI</li></ol>~~it can also be replaced with other ones, such as root

~~<div class="figure">~~::c. '''192.168.xx.xx''': It is the IP address of the development board, please modify it according to the actual situation

~~[[File~~:~~pi3b-img181~~:d.~~png|480x308px|18]]~~'''/home/orangepi''': The path in the Linux system of the development board, which can also be modified to other paths

~~</div><ol start~~::{| class="8wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>After the WIFI connection is successful, a "*" will be displayed in front of the connected WIFI name<~~|-| test@test:~$ '''scp file_path orangepi@192.168.xx.xx:/home/~~li><~~orangepi/~~ol>~~'''|}

<~~div class~~ol start="~~figure~~2"style="list-style-type: decimal;"><li>If you want to upload a folder, you need to add the -r parameter</li>

~~[[File~~{| class="wikitable" style="width:800px;" |-| test@test:~$ '''scp -~~img182~~r dir_path orangepi@192.168.xx.~~png~~xx:/home/orangepi/'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>There are more usages of scp, please use the following command to view the man manual</li>{| class="wikitable" style="width:800px;" |~~443x283px~~-|Ctest@test:~~\Users\orangepi\Desktop\用户手册插图\Zero3\未标题~~~$ '''man scp'''|}</ol>

~~</div><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></ol>~~== How to upload files using filezilla ====

~~orangepi@orangepi:~$ '''ip addr show wlan0'''~~# First install filezilla in Ubuntu PC

11: ~~wlan0~~: ~~&lt~~{| class="wikitable" style="width:800px;~~BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~" |-| test@test:~$ '''sudo apt install -y filezilla'''|}

~~link~~<ol start="2" style="list-style-type: decimal;"><li>Then use the following command to open filezilla</~~ether 24:8c:d3:aa:76:bb brd ff:ff:ff:ff:ff:ff~~li>

~~inet~~ {| class="wikitable" style="width:800px;" |-| test@test:~$ '''~~192.168.1.11~~filezilla'''|}</~~24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0~~ol><ol start="3" style="list-style-type: decimal;"><li>The interface after filezilla is opened is as follows, and the display under the remote site on the right is empty</li>

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

~~valid_lft 259071sec preferred_lft 172671sec~~</div></ol><ol start="4" style="list-style-type: decimal;"><li>The method of connecting the development board is shown in the figure below</li>

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

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

</div></ol><ol start="105" style="list-style-type: decimal;"><li>~~Use the~~ Then choose to '''~~ping~~save the password''' ~~command to test the connectivity of the wifi network~~, and ~~the '~~then click ''~~ping~~'~~'' command can be interrupted through the shortcut key '''Ctrl+C~~OK'''</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img210.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then choose to always '''trust this host''', and then click ''~~ping www.orangepi.org -I wlan0~~'OK'''</li>

~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0: 56(84) bytes of data.~~<div class="figure">

~~64 bytes from 182.92.236.130 (182.92.236.130)~~[[File: ~~icmp_seq=1 ttl=52 time=43~~pi3b-img211.~~5 ms~~png]]

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~</div></ol><ol start=~~2 ttl~~"7" style=~~52 time=41.3 ms~~"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>

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

~~64 bytes from 182.92.236.130 (182.92.236.130)~~[[File: ~~icmp_seq=4 ttl=52 time=45~~pi3b-img212.~~6 ms~~png]]

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~</div></ol><ol start=~~5 ttl~~"8" style=~~52 time=48~~"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 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.~~8 ms~~</li>

^C<div class="figure">

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

~~5 packets transmitted~~</div></ol><ol start="9" style="list-style-type: decimal;"><li>After the upload is complete, ~~5 received, 0% packet loss, time 4006ms~~you can go to the corresponding path in the Linux system of the development board to view the uploaded file</li>

~~rtt min~~<li>The method of uploading a folder is the same as that of uploading a file, so I won't go into details here</~~avg~~li></~~max/mdev~~ ol></~~2.484 ms~~span>

~~~~==== ~~Test~~ The method of ~~desktop image =~~uploading files from Windows PC to the Linux system of the development board ===

~~# Click the network configuration icon in the upper right corner of the desktop (please do not connect the network cable when testing WIFI)~~==== How to upload files using filezilla ====

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

~~<ol start~~::{| class="2wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Click~~ |-| '''~~More networks~~https://filezilla-project.org/download.php?type=client''' ~~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.png|576x353px]]~~<div class="figure">

~~<ol start="3" style="list~~::[[File:pi3b-~~style-type: decimal;"><li>Then enter the password of the WIFI hotspot, and then click '''Connect''' to start connecting to WIFI</li></ol>~~img214.png]]

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

~~<ol start="4" style="list~~::[[File:pi3b-~~style-type: decimal;"><li>After connecting to WIFI, you can open the browser to check whether you can access the Internet~~img215. ~~The entrance of the browser is shown in the figure below</li></ol>~~png]]

~~[[File~~</div><ol start="2" style="list-style-type:~~pi3b~~decimal;"><li>The downloaded installation package is as follows, and then double-~~img186.png|576x308px]]~~click to install directly</li>

~~<ol start~~{| class="5wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>If you can open other web pages after opening the browser, it means that the WIFI connection is normal</li></ol>~~|-| '''FileZilla_Server_1.5.1_win64-setup.exe'''|}

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

<~~span id~~div class="~~how-to-set-a-static-ip-address~~figure">~~=== How to set a static IP address ===~~

~~'''Please do not set a static IP address by modifying the /etc/network/interfaces configuration file~~[[File:pi3b-img216.~~'''~~png]]

<~~span id~~/div></ol><ol start="~~use-the-nmtui-command-to-set-a-static~~3" style="list-ipstyle-~~address~~type: decimal;"><li>The interface after filezilla is opened is as follows, and the display under the remote site on the right is empty</~~span~~li>~~==== Use the nmtui command to set a static IP address ====~~

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

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

</div></ol><ol start="24" style="list-style-type: decimal;"><li>~~Then select '''Edit a connection''' and press Enter~~The method of connecting the development board is shown in the figure below:</li~~></ol~~>

~~[[File:pi3b-img188.png|227x247px]]~~<div class="figure">

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

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

<~~ol start~~div class="4figure" ~~style="list-style-type: decimal;"><li>Then select '''Edit''' with the '''Tab''' key and press the Enter key</li></ol~~>

[[File:pi3b-~~img190~~img218.png~~|316x144px~~]]

</div></ol><ol start="56" style="list-style-type: decimal;"><li>Then ~~use the Tab key~~ choose to ~~move the cursor to the~~ always '''trust this host''', and then click '''~~<Automatic>~~OK''' ~~position shown in the figure below to configure IPv4~~</li~~></ol~~>

~~[[File:pi3b-img191.png|575x240px]]~~<div class="figure">

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

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

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

[[File:pi3b-~~img193~~img220.png~~|575x240px~~]]

</div></ol>

<li>Then ~~move~~ select the ~~cursor~~ 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 ~~'''<Show>'''~~development board.</li~~></ol~~>

<div class="figure"> [[File:pi3b-~~img194~~img221.png~~|576x241px~~]]

</div></ol>

<li>~~Then press Enter~~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 ~~following setting interface will pop up after entering~~same as that of uploading a file</li></ol>

~~[[File:pi3b~~

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

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

~~<ol start="11" style="list-style-type: decimal;"><li>After setting, move the cursor~~ # Use HDMI to~~'''<OK>''' in the lower right corner,~~ HDMI cable to connect Orange Pi development board and ~~press Enter to confirm</li></ol>~~HDMI monitor

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

<ol start="122" style="list-style-type: decimal;"><li>~~Then click'''<Back>''' to return to~~ After starting the Linux system, if the HDMI monitor has image output, it means that the ~~previous selection~~ HDMI interfaceis in normal use</li~~></ol~~>

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-~~img198~~| <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|330x325px]]~~'''

'''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="13wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Then select~~ '''~~Activate a~~ 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~~'''~~, ~~then move the cursor~~ you can change a different screen and try tosee if it is displayed.'''~~<OK>''', and finally click Enter~~</libig>|}</ol>

~~[[File:pi3b~~

~~<ol start~~=~~"14" style~~=~~"list-style-type: decimal;"><li>Then select the network interface that needs~~ = HDMI to ~~be set, such as '''Wired connection 1''', then move the cursor to'''<Deactivate>''', and press Enter to disable '''Wired connection 1'''</li></ol>~~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-~~img200.png|576x224px]]~~alpha;"><li>HDMI to VGA converter</li>

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

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

~~<ol start="16" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Then you can exit nmtui through the'''<Back>''' and '''Quit''' buttons</li></ol>~~img224.png]]

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

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

~~orangepi@orangepi:~$~~ # First open '''~~ip addr show eth0~~Display''' in '''Settings'''

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

~~link~~<ol start="2" style="list-style-type: decimal;"><li>Then you can see the current resolution of the system</~~ether 5e:ac:14:a5:92:b3 brd ff:ff:ff:ff:ff:ff~~li>

~~inet '''192~~[[File:pi3b-img226.~~168.1.177'''~~png]]</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</~~24 brd 192.168.1.255 scope global noprefixroute eth0~~li>

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

~~inet6 241e~~[[File:~~3b8:3240:c3a0:e269:8305:dc08~~pi3b-img228.png]]</ol><ol start="5" style="list-style-type:~~135e~~decimal;"><li>After the new resolution is set, select '''Keep the configuration'''</~~64 scope global dynamic noprefixroute~~li>

~~valid_lft 259149sec preferred_lft 172749sec~~[[File:pi3b-img229.png]]</ol>

~~inet6 fe80::957d:bbbe:4928:3604/64 scope link noprefixroute~~== How to use Bluetooth ==

~~valid_lft forever preferred_lft forever~~=== Test method of desktop image ===

~~<ol start="18" style="list-style-type: decimal;"><li>Then you can test~~ # Click the ~~connectivity~~ Bluetooth icon in the upper right corner of the ~~network to check whether the IP address is configured OK, and the '''ping''' command can be interrupted through the shortcut key '''Ctrl+C'''</li></ol>~~desktop.

~~orangepi@orangepi~~:~~~$ '''ping 192.168~~:[[File:pi3b-img230.~~1.47 -I eth0'''~~png]]

~~PING 192.168.1.47 (192.168.1.47) from 192.168.1.188 eth0~~<ol start="2" style="list-style-type: ~~56(84) bytes of data.~~decimal;"><li>Then select the adapter</li>

~~64 bytes from 192.168.1~~[[File:pi3b-img231.~~47: icmp_seq~~png]]</ol><ol start=~~1 ttl~~"3" style=~~64 time=0.233 ms~~"list-style-type: decimal;"><li>If there is a prompt on the following interface, please select '''Yes'''</li>

~~64 bytes from 192.168.1~~[[File:pi3b-img232.~~47: icmp_seq~~png]]</ol><ol start=~~2 ttl~~"4" style=~~64 time=0.263 ms~~"list-style-type: decimal;"><li>Then set '''Visibility Setting''' as '''Always visible''' in the Bluetooth adapter settings interface, and then close it</li>

~~64 bytes from 192.168.1~~[[File:pi3b-img233.~~47: icmp_seq~~png]]</ol><ol start=~~3 ttl~~"5" style=~~64 time=0.273 ms~~"list-style-type: decimal;"><li>Then open the configuration interface of the Bluetooth device</li>

~~64 bytes from 192.168.1~~[[File:pi3b-img234.~~47: icmp_seq~~png]]</ol><ol start=~~4 ttl~~"6" style=~~64 time=0.269 ms~~"list-style-type: decimal;"><li>Click '''Search''' to start scanning the surrounding Bluetooth device</li>

~~64 bytes from 192.168.1~~[[File:pi3b-img235.~~47: icmp_seq~~png]]</ol><ol start=~~5 ttl~~"7" style=~~64 time=0.275 ms~~"list-style-type: decimal;"><li>Then select the Bluetooth device you want to connect to, and then click the right button of the mouse to pop up the operation interface for this Bluetooth device, select '''Pair''' to start pairing, and the demonstration here is to pair with an Android phone</li>

^C[[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-~~-- 192.168.1~~img237.~~47 ping statistics~~ png]]</ol><ol start="9" style="list-style-type: decimal;"><li>After pairing with the mobile phone, you can choose the paired Bluetooth device, then right-click and select '''Send a File''' to start sending a picture to the phone</li>

~~5 packets transmitted, 5 received, 0% packet loss, time 4042ms~~[[File:pi3b-img238.png]]</ol><ol start="10" style="list-style-type: decimal;"><li>The interface of the sending picture is shown below</li>

~~rtt min~~[[File:pi3b-img239.png]]</~~avg/max/mdev~~ ol></~~0.262/0.275/0.015 ms~~span>

~~==== Use the nmcli command to set a static IP address~~ ==USB interface test ==

~~<ol style~~{| class="~~list-style-type: decimal;~~wikitable"><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~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <~~li><p~~big>'''~~orangepi''' is~~ The USB interface can be connected to a USB hub to expand the ~~name~~ number of ~~the WIFI network interface (the names are not necessarily the same)</li><li>''~~USB interfaces.'~~Wired connection 1~~''~~' is the name of the Ethernet interface~~</~~li></ol~~big>~~</li></ol>~~|}

~~orangepi@orangepi:~$ '''nmcli con show'''~~=== Connect the USB mouse or keyboard test ===

~~NAME UUID TYPE DEVICE~~# 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)

~~'''orangepi''' cfc4f922~~

~~'''Wired connection 1''' 9db058b7-7701-37b8-9411-efc2ae8bfa30 ethernet eth0~~=== Connect the USB storage device test ===

~~<ol start="3" style="list-style-type: decimal;">~~# First insert the U disk or USB mobile hard disk into the USB interface of the Orange Pi development board~~<li>Then enter~~ # Execute the following command, ~~where</li></ol>~~if you can see the output of sdX, it means that the U disk is recognized successfully

~~<blockquote>a.~~ ::{| class="wikitable" style="width:800px;"|-|orangepi@orangepi:~$ '''cat /proc/partitions | grep "~~Wired connection 1~~sd*"''' ~~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~~ major minor #blocksname ~~of the WIFI network interface (you can get it through the~~ 8030044160 '''~~nmcli con show~~sda''' ~~command)~~ 8130043119 '''sda1''' |}

~~b. After~~ <ol start="3" style="list-style-type: decimal;"><li>Use the mount command to mount the U disk into '''~~ipv4.addresse~~/mnt''' ~~is the static IP address to be set~~, ~~which~~ and then you can ~~be modified to~~ view the file in the ~~value you want to set~~U disk</li>

~~c. '''ipv4.gateway''' indicates the address of the gateway~~{| class="wikitable" style="width:800px;" |-~~</blockquote>~~| orangepi@orangepi:~$ '''~~nmcli con mod "Wired connection 1" \~~sudo mount /dev/sda1 /mnt/'''

orangepi@orangepi:~$ '''~~ipv4.addresses "192.168.1.110" \'''~~ ~~'''ipv4.gateway "192.168.1.1" \'''~~ ~~'''ipv4.dns "8.8.8.8" \'''~~ ~~'''ipv4.method "manual"~~ls /mnt/'''

test.txt

|}

</ol>

<li>~~Then restart~~ After the ~~Linux system~~mounting, you can view the capacity usage and mount point of the U disk through the '''df -h''' command</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''df -h | grep "sd"'''

~~orangepi@orangepi:~$ '''sudo reboot'''~~/dev/sda1     29G    208K    29G    1% /mnt|}</ol>

~~<ol start~~=~~"5" style~~=~~"list-style-type: decimal;"><li>Then re-enter the Linux system and use the '''ip addr show eth0'''command to see that the IP address has been set to the desired value</li></ol>~~= USB wireless network card test ===

~~orangepi@orangepi:~$~~ The currently '''~~ip addr show eth0~~tested'''USB wireless network cards are shown below. Please test it by yourself for other models of USB wireless network cards. If you cannot use it, you need to transplant the corresponding USB wireless network card driver

3{| class="wikitable" style="width: ~~eth0~~800px;text-align: ~~<BROADCAST,MULTICAST,UP,LOWER_UP&gt~~center; ~~mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~"|-| No.| Model||-| 1| RTL8723BU

~~link/ether 5e:ae:14:a5:91:b3 brd ff:ff:ff:ff:ff:ff~~Support 2.4G WIFI+BT4.0

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

~~valid_lft forever preferred_lft forever~~Support 2.4G +5G WIFI

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

~~valid_lft 259183sec preferred_lft 172783sec~~Support 2.4G +5G WIFI

~~inet6 fe80::3312:861a:a589:d3c/64 scope link noprefixroute~~Support BT 4.2

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

~~== SSH remote login development board; ==~~img242.png]]

'''Linux systems enable ssh remote login by default and allow the root user to log in to the system. Before logging in with ssh, you first need to ensure that the Ethernet or wifi network is connected, and then use the ip addr command or check the router to obtain the IP address of the development board.'''</div>|}

=== ~~SSH remote login development board under Ubuntu~~ = RTL8723BU test ====

# ~~Obtain~~ First insert the ~~IP address~~ RTL8723BU wireless network card module into the USB interface of the development board# Then ~~you can remotely log in to~~ the Linux system will automatically load the RTL8723BU bluetooth and WIFI-related kernel modules, through the ~~ssh~~ lsmod command, you can see that the following kernel modules have been automatically loaded

~~test~~::{| class="wikitable" style="width:800px;" |-|orangepi@~~test~~orangepi:~$ '''~~ssh [mailto:root@192.168.1.36 root@192.168.1.]xxx~~lsmod''' ~~(Need to be replaced with the IP address of the development board)~~Module Size Used by rfcomm 5734416 rtl8xxxu 1064960 rtk_btusb 614400 |}

~~root@192.168.1.xx's password~~<ol start="3" style="list-style-type: ~~(Enter~~ decimal;"><li>Through the ~~password here~~dmesg command, you can see the ~~default password is orangepi)~~loading information of the RTL8723BU module</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~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.~~dmesg'''

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

~~<ol start="3" style="list~~[ 83.438901] usb 2-~~style~~1: new high-~~type: decimal;"><li>After successfully logging in to the system, the display is as shown in the figure below</li></ol>~~speed USB device number 2 using ehci-platform

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

[~~[File:pi3b-img204~~83.~~png|405x207px|L467QDF65C(YR79U]TH[TND]~~588403]usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

~~</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~~588422] usb 2-1: Product: 802. ~~Is it possible to connect:'''~~11n WLAN Adapter

~~root@orangepi~~[ 83.588443] usb 2-1:~~~# '''reset_ssh.sh'''~~Manufacturer: Realtek

~~'''If it still doesn't work, try to reset the system~~[ 83.~~'''~~588460] usb 2-1: SerialNumber: 00e04c000001

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

~~# First obtain the IP address of the development board~~[ 83.603894] Bluetooth: hci0: RTL: rom_version status=0 version=1

~~2) Under Windows, you can use MobaXterm to remotely log in to the development board, first create a new ssh session~~[ 83.603920] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_fw.bin

a[ 83. ~~Open '''Session'''~~610108] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_config.bin

b[ 83. ~~Then select '''SSH''' in '''Session Setting'''~~611274] Bluetooth: hci0: RTL: cfg_sz 68, total sz 22564

c[ 83. ~~Then enter the IP address of the development board in the '''Remote host'''~~658494] rtk_btusb: Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-142432

d[ 83. ~~Then enter the user name '''root''' or '''orangepi''' of the Linux system in '''Specify username'''~~658651] usbcore: registered new interface driver rtk_btusb

e[ 83. ~~Finally click '''OK'''~~667124] usb 2-1: This Realtek USB WiFi dongle (0x0bda:0xb720) is untested!

~~<div class="figure">~~[ 83.667137] usb 2-1: Please report results to Jes.Sorensen@gmail.com

[~~[File:pi3b-img205~~83.~~png|553x280px|14]~~890140]usb 2-1: Vendor: Realtek

~~</div><ol start="~~[ 83.890153] usb 2~~" style="list~~-~~style-type~~1: Product: ~~decimal;"><li></li><li>Then you will be prompted to enter a password~~802. ~~The default passwords for root and orangepi users are orangepi</li></ol>~~11n WLAN Adapter

~~'''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~~[ 83.~~'''~~890159] usb 2-1: rtl8723bu_parse_efuse: dumping efuse (0x200 bytes):

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

[~~[File:pi3b~~83.890412] usb 2-~~img206.png|578x150px|C~~1:~~\Users\orangepi\Desktop\用户手册插图\pi 3b\just press Enter after inputting..jpgjust press Enter after inputting.]]~~RTL8723BU rev E (SMIC) 1T1R, TX queues 3, WiFi=1, BT=1, GPS=0, HI PA=0

~~</div><ol start="4" style="list~~[ 83.890417] usb 2-~~style-type~~1: RTL8723BU MAC: 00:13:ef:f4:58: ~~decimal;"><li>After successfully logging in to the system, the display is as shown in the figure below</li></ol>~~ae

[~~[File~~83.890421] usb 2-1:~~pi3b-img207~~rtl8xxxu: Loading firmware rtlwifi/rtl8723bu_nic.~~png|576x334px]]~~bin

~~== The method of uploading files to the Linux system of the development board ==~~1: Firmware revision 35.0 (signature 0x5301)

~~=== How to upload files to the development board Linux system in Ubuntu PC ===~~[ 84.050893] Bluetooth: hci0: RTL: fw version 0x0e2f9f73

~~==== How to upload files using the scp command ====~~[ 84.266905] Bluetooth: RFCOMM TTY layer initialized

~~# Use the scp command to upload files from the Ubuntu PC to the Linux system of the development board~~[ 84. ~~The specific commands are as follows~~266949] Bluetooth: RFCOMM socket layer initialized

~~<blockquote>a~~[ 84. ~~'''file_path'''~~266999] Bluetooth: ~~need to be replaced with the path of the file to be uploaded~~RFCOMM ver 1.11

b[ 84. ~~'''orangepi'''~~884270] usbcore: ~~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~~registered new interface driver rtl8xxxu

c[ 84. 912046] rtl8xxxu 2-1:1.2 wlx0013eff458ae: renamed from wlan0|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then you can see the RTL8723BU WIFI device node through the '''sudo ifconfig'''~~192~~command.~~168.xx.xx~~Please refer to [[Orange Pi 3B#WIFI connection test|'''the WIFI connection test chapter''']] for WIFI connection and testing methods</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi: ~~It is the IP address of the development board, please modify it according to the actual situation~~~$ '''sudo ifconfig wlx0013eff458ae'''

~~d. '''/home/orangepi'''~~wlx0013eff458ae: ~~The path in the Linux system of the development board~~flags=4099<UP, ~~which can also be modified to other paths</blockquote>test@test:~$ '''scp file_path orangepi@192.168.xx.xx:/home/orangepi/'''~~BROADCAST,MULTICAST> mtu 1500

~~<ol start="2" style="list-style-type~~: ~~decimal;"><li>If you want to upload a folder, you need to add the -r parameter</li></ol>~~:ether 00:13:ef:f4:58:ae txqueuelen 1000 (Ethernet)

~~test@test~~:~~~$ '''scp -r dir_path orangepi@192.168.xx~~:RX packets 0 bytes 0 (0.~~xx:/home/orangepi/'''~~0 B)

~~<ol start="3" style="list-style-type~~: ~~decimal;"><li>There are more usages of scp, please use the following command to view the man manual</li></ol>~~:RX errors 0 dropped 0 overruns 0 frame 0

~~test@test~~:~~~$ '''man scp'''~~:TX packets 0 bytes 0 (0.0 B)

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

~~# First install filezilla in Ubuntu PC~~orangepi@orangepi:~$ '''hciconfig'''

~~test@test~~hci0: Type: Primary Bus:~$ '''~~sudo apt install -y filezilla~~USB'''

~~<ol start="2" style="list-style-type~~: ~~decimal;">~~:BD Address: 00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16~~<li>Then use the following command to open filezilla</li></ol>~~::DOWN

~~test@test~~:~~~$ '''filezilla'''~~: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="36" style="list-style-type: decimal;"><li>~~The interface after filezilla is opened is as follows, and the display under~~ You can also see the ~~remote site~~ Bluetooth icon on the ~~right is empty~~desktop. At this time, Bluetooth has not been opened, so a red '''x</lispan>''' will be displayed</olli>

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

[[File:pi3b-~~img208~~img244.png~~|576x453px|截图 2022-12-03 19~~]]</ol><ol start="8" style="list-04style-~~40]]~~type: decimal;"><li>The display after turning on Bluetooth is as follows</li>

[[File:pi3b-img245.png]]</~~div~~ol><ol start="49" style="list-style-type: decimal;"><li>~~The~~ Please refer to the [[Orange Pi 3B#How to use Bluetooth|'''Bluetooth use method''']] for Bluetooth test method ~~of connecting the development board is shown in the figure below~~, so I won't go into details here.</li></ol>

<~~div class~~span id="~~figure~~rtl8811-test">

~~[[File:pi3b-img209.png|575x128px|图片565]]~~==== RTL8811 test ====

~~</div>~~# First insert the RTL8811 wireless network card module into the USB interface of the development board.~~<ol start="5" style="list-style-type: decimal;"><li>~~# Then ~~choose~~ the Linux system will automatically load the kernel modules related to ~~'''save the password'''~~RTL8811 WIFI, and ~~then click '''OK'''</li></ol>~~you can see that the following kernel modules have been automatically loaded through the lsmod command

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''lsmod'''Module Size Used by 8821cu 1839104 0 |~~249x181px]]~~}

<ol start="63" style="list-style-type: decimal;"><li>~~Then choose to always '''trust this host'''~~Through the dmesg command, ~~and then click~~ you can see the loading information of the RTL8811 module</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''OKdmesg'''~~</li></ol>~~

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

[~~[File~~118.767152] usb 2-1:~~pi3b-img211~~New USB device found, idVendor=0bda, idProduct=c811, bcdDevice= 2.~~png|278x150px|IMG_256]]~~00

~~</div><ol start~~[ 118.767181] usb 2-1: New USB device strings: Mfr=~~"7" style~~1, Product=~~"list-style-type: decimal;"><li>After the connection is successful~~2, ~~you can see the directory structure of the development board Linux file system on the right side of the filezilla software</li></ol>~~SerialNumber=3

~~<div class="figure">~~[ 118.767199] usb 2-1: Product: 802.11ac NIC

[~~[File:pi3b-img212~~118.~~png|533x330px|IMG_256]~~767219]usb 2-1: Manufacturer: Realtek

~~</div><ol start="8" style="list~~[ 118.767235] usb 2-~~style-type~~1: SerialNumber: ~~decimal;">~~<li>Then select the path to be uploaded to the development board on the right side of the filezilla software, and then select the file to be uploaded on the Ubuntu PC on the left side of the filezilla software, then click the right mouse button, and then click the upload option to start uploading the file to the development board bingo.</li></ol>123456

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

[~~[File~~119.525498] rtl8821cu 2-1:1.0 wlx1cbfced9d260:~~pi3b~~renamed from wlan0|}</ol><ol start="4" style="list-~~img213~~style-type: decimal;"><li>Then you can see the WiFi device node through the '''sudo ifconfig''' command.~~png~~Please refer to the [[Orange Pi 3B#WIFI connection test|~~485x380px|IMG_256~~'''WiFi connection test chapter''']]for WIFI connection and testing methods. I won't go into details her</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ifconfig wlx1cbfced9d260'''

~~</div>9) After the upload is complete~~wlx1cbfced9d260: flags=4099<UP, ~~you can go to the corresponding path in the Linux system of the development board to view the uploaded file~~BROADCAST,MULTICAST> mtu 1500

10::ether 1c:bf:ce:d9:d2:60 txqueuelen 1000 (Ethernet) ~~The method of uploading a folder is the same as that of uploading a file, so I won’t go into details here~~

~~=== The method of uploading files from Windows PC to the Linux system of the development board ===~~::RX packets 0 bytes 0 (0.0 B)

~~==== How to upload files using filezilla ====~~::RX errors 0 dropped 0 overruns 0 frame 0

~~# First download the installation file of the Windows version of the filezilla software, the download link is as follows~~::TX packets 0 bytes 0 (0.0 B)

~~https~~::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0|}</~~/filezilla~~ol></~~download.php?type=client~~span>

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

~~[[File:pi3b-img214.png|472x171px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-15.jpg未标题-15]]~~# First insert the rtl8821cu wireless network card module into the USB interface of the development board# Then use the '''lsusb''' command to see the device information of the rtl8821cu usb wifi module, please make sure that the USB module is not in Driver CDROM Mode

~~</div><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-~~img215.png~~color:#ffffdc;width:800px;" |-|~~393x283px~~orangepi@orangepi:~$ '''lsusb |~~图片5552]]~~grep "Realtek"'''

Bus 002 Device 002: ID 0bda:1a2b Realtek Semiconductor Corp. RTL8188GU 802.11n WLAN Adapter ('''<~~/div><ol start="2"~~ span style="~~list-style-type~~color: ~~decimal;~~blue">~~<li>The downloaded installation package is as follows, and then double-click to install directly</li>~~Driver CDROM Mode</olspan>''')

~~'''FileZilla_Server_1.5.1_win64-setup.exe'''~~

~~During~~ <big>'''If the ~~installation process~~USB WIFI module seen by the lsusb command is in Driver CDROM Mode, please ~~select '''Decline''' on~~ unplug the USB WIFI module again. If not, please manually execute the following ~~installation interface, and then select '''Next>~~command to switch to the next mode:'''</big>

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

~~[[File~~orangepi@orangepi:~~pi3b~~~$ '''sudo usb_modeswitch -~~img216.png|319x251px~~KW -v 0bda -p 1a2b'''|~~IMG_256]]~~}

~~</div>~~

<li>The ~~interface after filezilla is opened is as follows~~Linux system will automatically load the rtl8821cu bluetooth and wifi-related kernel modules, ~~and~~ through the ~~display under the remote site on~~ lsmod command, you can see that the following kernel modules have been automatically loaded</li>{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''lsmod'''Module Size Used by 8821cu 1839104 0 rtk_btusb 614400 |}</ol><ol start="4" style="list-style-type: decimal;"><li>Through the dmesg command, you can see the loading information of the rtl8821cu module</olli>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''dmesg'''

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

[~~[File~~57.083693] usb 2-1:~~pi3b~~new high-~~img217.png|451x357px|IMG_256]]~~speed USB device number 2 using ehci-platform

~~</div><ol start~~[ 57.231888] usb 2-1: New USB device found, idVendor=0bda, idProduct=~~"4" style~~1a2b, bcdDevice=~~"list-style-type: decimal;"><li>The method of connecting the development board is shown in the figure below:</li></ol>~~2.00

~~<div class~~[ 57.231916] usb 2-1: New USB device strings: Mfr=~~"figure">~~1, Product=2, SerialNumber=0

[~~[File:pi3b-img209~~57.~~png|575x128px|图片565]~~231937]usb 2-1: Product: DISK

~~</div><ol start="5" style="list~~[ 57.231956] usb 2-~~style-type~~1: Manufacturer: ~~decimal;"><li>Then choose to '''save the password''', and then click '''OK'''</li></ol>~~Realtek

~~<div class="figure">~~[ 57.242594] usb-storage 2-1:1.0: USB Mass Storage device detected

[~~[File~~57.245674] scsi host0:~~pi3b~~usb-storage 2-~~img218~~1:1.~~png|207x146px|IMG_256]]~~0

~~</div><ol start="6" style="list~~[ 58.069172] usb 2-~~style-type~~1: ~~decimal;"><li>Then choose to always '''trust this host'''~~USB disconnect, ~~and then click '''OK'''</li></ol>~~device number 2

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

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

~~</div><ol start~~[ 58.587827] usb 2-1: New USB device strings: Mfr=~~"7" style~~1, Product=~~"list-style-type: decimal;"><li>After the connection is successful~~2, ~~you can see the directory structure of the development board Linux file system on the right side of the filezilla software</li></ol>~~SerialNumber=3

~~<div class="figure">~~[ 58.587833] usb 2-1: Product: 802.11ac NIC

[~~[File:pi3b-img220~~58.~~png|446x329px|图片3]~~587838]usb 2-1: Manufacturer: Realtek

~~</div><ol start="8" style="list~~[ 58.587844] usb 2-~~style-type~~1: SerialNumber: ~~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>123456

~~<div class="figure">~~[ 58.610463] rtk_btusb: Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-142432

[~~[File:pi3b-img221~~58.~~png|501x369px|IMG_256]~~610656]usbcore: registered new interface driver rtk_btusb

~~</div><ol start~~[ 58.634631] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=~~"9" style~~000c lmp_ver=~~"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>~~08 lmp_subver=8821

~~== HDMI test~~ [ 58.636729] Bluetooth: hci0: RTL: rom_version status=0 version=1

~~<~~[ 58.636740] Bluetooth: hci0: RTL: loading rtl_bt/~~span>=== HDMI display test ===~~rtl8821c_fw.bin

~~# Use HDMI to HDMI cable to connect Orange Pi development board and HDMI monitor~~[ 58.664190] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin

[~~[File:pi3b-img10~~58.~~png|199x129px]~~664746]Bluetooth: hci0: RTL: cfg_sz 10, total sz 31990

~~<ol start="2" style="list-style-type~~[ 59.122471] Bluetooth: ~~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>~~hci0: RTL: fw version 0x829a7644

~~'''Note that although many notebook computers have an HDMI~~ [ 59.265513] usbcore: registered new 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.'''driver rtl8821cu

~~'''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~~[ 59.~~'''~~280119] rtl8821cu 2-1:1.2 wlx90de80521825: renamed from wlan0|}</ol>

<ol start="5" style="list-style-type: decimal;"><li>Then you can see the RTL8821CU WiFi device node through the '''~~When the HDMI is not displayed, please check whether the HDMI cable is plugged in tightly~~sudo ifconfig''' command. ~~After confirming that there is no problem with~~ Please refer to the [[Orange Pi 3B#WIFI connection test|'''WiFi connection test chapter''']] for WIFI connection~~, you can change a different screen~~ and ~~try to see if it is displayed~~testing methods.</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ifconfig wlx90de80521825'''

~~=== HDMI to VGA display test ==~~wlx90de80521825: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500

~~<ol style="list-style-type~~: ~~decimal;"><li>First, you need to prepare the following accessories<ol style="list-style-type~~: ~~lower-alpha;"><li>HDMI to VGA converter</li></ol></li></ol>~~ether 00:13:ef:f4:58:ae txqueuelen 1000 (Ethernet)

~~[[File~~:~~pi3b-img222~~:RX packets 0 bytes 0 (0.~~png|155x104px]]~~0 B)

~~<ol start="2" style="list-style-type~~: ~~lower-alpha;"><li>A VGA cable</li></ol>~~:RX errors 0 dropped 0 overruns 0 frame 0

~~[[File~~:~~pi3b-img223~~:TX packets 0 bytes 0 (0.~~png|148x133px]]~~0 B)

::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0|}</ol><ol start="36" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~A monitor or TV that supports VGA interface~~Then you can see the USB Bluetooth device through the '''hciconfig''' command</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt-get update && sudo apt-get install -y bluez'''

~~<ol start="2" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>HDMI to VGA display test as shown below</li></ol>~~~$ '''hciconfig'''

~~[[File~~hci0:~~pi3b-img224.png|576x339px]]~~Type: Primary Bus: '''USB'''

'''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.'''::BD Address: 00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16

~~=== HDMI resolution setting method ===~~::DOWN

~~# First open '''Display''' in '''Settings'''~~::RX bytes:1252 acl:0 sco:0 events:125 errors:0

~~[[File~~:~~pi3b~~:TX bytes:23307 acl:0 sco:0 commands:125 errors:0|}</ol><ol start="7" style="list-~~img225~~style-type: decimal;"><li>Bluetooth icons can also be seen on the desktop.~~png|576x370px]]~~At this time, Bluetooth has not been turned on, so a red '''x''' will be displayed</li>

[[File:pi3b-img243.png]]</ol><ol start="28" style="list-style-type: decimal;"><li>~~Then you can see the current resolution of the system~~Click '''Turn Bluetooth On''' to turn on Bluetooth</li~~></ol~~>

[[File:pi3b-~~img226~~img244.png~~|382x254px~~]]</ol><ol start="9" style="list-style-type: decimal;"><li>The display after turning on Bluetooth is as follows</li>

[[File:pi3b-img245.png]]</ol><ol start="310" style="list-style-type: decimal;"><li>~~Click~~ Please refer to the ~~drop-down box of Resolution~~ [[Orange Pi 3B#How to ~~see all resolutions currently supported by~~ use Bluetooth|'''Bluetooth use chapter''']] for the ~~monitor~~Bluetooth test method. I won't go into details here</li></ol>

~~[[File:pi3b~~

~~<ol start~~=~~"4" style~~=~~"list-style-type: decimal;"><li>Then select the resolution you want to set, and click Apply</li></ol>~~= USB Camera Test ===

~~[[File:pi3b-img228.png|415x277px]]~~# 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="5" style="list~~::[[File:pi3b-~~style-type: decimal;"><li>After the new resolution is set, select '''Keep the configuration'''</li></ol>~~img13.png]]

~~[[File~~<ol start="2" style="list-style-type: decimal;"><li>You can see that the USB camera's device node information is/dev/video0 through the v4l2-ctl command</li>{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img229.png~~|~~447x243px]]~~orangepi@orangepi:~$ '''v4l2-ctl --list-devices'''

Q8 HD Webcam: Q8 HD Webcam ('''usb~~== How to use Bluetooth ==~~'''-fc880000.usb-1):

:'''/dev/video0~~=== Test method of desktop image ===~~'''

~~# Click the Bluetooth icon in the upper right corner of the desktop.~~:/dev/video1

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

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

~~<li>Then select the adapter</li></ol>~~

~~[[File~~'''In addition, the serial number of the video is not necessarily video0, please refer to what you actually see.'''</big>|}</ol><ol start="3" style="list-style-type:~~pi3b-img231~~decimal;"><li>In the desktop system, Cheese can be used to directly open the USB camera.~~png|375x165px]]~~The method of opening Cheese is shown in the figure below:</li>

~~<ol start="3" style="list~~[[File:pi3b-~~style-type: decimal;"><li>If there is a prompt below, select '''Yes'''</li></ol>~~img246.png]]

~~[[File~~The interface after Cheese turns on the USB camera is shown in the figure below:~~pi3b-img232.png|248x85px]]~~

[[File:pi3b-img247.png]]

</ol>

<li>~~Then set~~ How to test the USB camera using fswebcam<ol style="list-style-type: lower-alpha;"><li>Install fswebcam</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~Visibility Setting~~sudo''' as '''~~Always visible~~apt update''' ~~in the Bluetooth adapter settings interface, and then close it</li></ol>~~

~~[[File~~orangepi@orangepi:~~pi3b~~~$ '''sudo apt-~~img233.png~~get install -y fswebcam'''|~~243x229px]]~~}</ol><ol start="52" style=" list-style-type: lower-alpha;"><li>After installing fswebcam, you can use the following command to take pictures<ol style="list-style-type: ~~decimal~~none;"><li>~~Then open~~ 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 ~~configuration interface~~ resolution of the ~~Bluetooth device~~photo</li><li>d) -S The option is used to set the number of previous frames to skip</olp></li><li>e) ./image.jpg The name and path for setting the generated photos</li>~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img234.png~~|~~438x179px]]~~orangepi@orangepi:~$ '''sudo''' '''fswebcam -d /dev/video0 \'''

'''--no-banner -r 1280x720 -S 5 ./image.jpg'''|}</ol></li></ol><ol start="63" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Click~~ In the desktop version of the Linux system, you can directly view the captured pictures through the HDMI display</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''scp image.jpg'''~~Search~~[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）'''|}</ol><ol start ~~scanning~~ ="4" style="list-style-type: lower-alpha;"><li>In the ~~surrounding Bluetooth device~~desktop version of the Linux system, you can directly view the captured pictures through the HDMI display</li></ol></li></ol>

~~[[File:pi3b-img235.png|322x217px]]~~== Audio Test ==

<~~ol start~~span id="~~7" style="list~~test-audio-methods-~~style~~in-~~type: decimal;"><li>Then select~~ the ~~Bluetooth device you want to connect. If you right~~ -~~click the mouse, you will pop up the operating interface of this Bluetooth device. Select '''Pair''' to start pairing. Here, it is demonstrated with the Android phone</li~~desktop-system"></olspan>=== Test audio methods in the desktop system ===

~~[[File:pi3b-img236.png|338x263px]]~~# First open the file manager

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

~~[[File~~<ol start="2" style="list-style-type:~~pi3b-img237.png|417x152px]]~~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="9figure" ~~style="list-style-type: decimal;"><li>After pairing with the mobile phone, you can choose the paired Bluetooth device, then right -click and select '''Send a File''' to start sending a picture to the phone</li></ol~~>

[[File:pi3b-~~img238~~img249.png~~|439x259px~~]]

</div></ol><ol start="103" style="list-style-type: decimal;"><li>~~The interface of~~ Then select the ~~sending picture is shown below~~audio.wav file, right click and select open with vlc to start playing</li~~></ol~~>

[[File:pi3b-~~img239~~img250.png~~|437x253px~~]]</ol><ol start="4" style="list-style-type: decimal;"><li>Methods to switch different audio equipment such as HDMI playback and headset playback<ol style="list-style-type: lower-alpha;"><li>First open the volume control interface</li>

[[File:pi3b-img251.png]]<~~span id~~/ol><ol start="2" style="~~usb~~list-style-~~interface~~type: lower-~~test~~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.</~~span~~li>~~== USB interface test ==~~

~~'''The USB interface can connect USB Hub~~ [[File:pi3b-img252.png]]</ol></li></ol>

~~~~==~~= Connect the USB mouse or keyboard test~~ How to play audio with commands ===

~~# Insert the keyboard of the USB~~ ~~# If the mouse or keyboard can normal operating systems, the USB~~ ==== Headphone interface ~~is used normally (the mouse can only be used in the system of the desktop version)~~play audio test ====

~~=== Connect~~ headset into the ~~USB storage device test ===~~headphone jack of the development board

~~# First insert the U disk or USB mobile hard disk into the USB interface of Orange PI development board# Execute the following command~~::[[File:pi3b-img253. ~~If you can see the output of sdX, the U disk recognition is successful~~png]]

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~$ decimal;"><li>Then you can check the sound card device supported by the Linux system through the '''aplay -l''' command. From the output below, it can be seen that '''~~cat /proc/partitions | grep "sd*"~~card 0'''is the sound card device with RK809, which is the sound card device of the headset</li>

~~major minor #blocks name~~{| class="wikitable" style="width:800px;" |-~~8 0 30044160~~ | orangepi@orangepi:~$ '''~~sda~~aplay -l'''

~~8 1 30043119 '''sda1'''~~**** List of PLAYBACK Hardware Devices ****

~~<ol start="3" style="list-style-type: decimal;"><li>Use the mount command to mount the U disk into~~ '''~~/mnt~~card 0: rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]'''~~, and then you can view the file in the U disk</li></ol>~~

~~orangepi@orangepi~~:~$ '''~~sudo mount /dev/sda1 /mnt~~Subdevices: 0/1'''

~~orangepi@orangepi~~:~$ '''~~ls /mnt/~~Subdevice #0: subdevice #0'''

~~test~~card 1: rockchiphdmi [rockchip,hdmi], device 0: fe400000.~~txt~~i2s-i2s-hifi i2s-hifi-0 [fe400000.i2s-i2s-hifi i2s-hifi-0]

~~<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''' command and the mounting point</li><~~Subdevices: 0/~~ol>~~1

~~orangepi@orangepi~~:~~~$ '''df -h | grep "sd"'''~~Subdevice #0: subdevice #0

:Subdevice #0: subdevice #0|}</~~dev~~ol><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</~~sda1 29G 208K 29G 1% /mnt~~li>

~~=== USB wireless network card test ===~~ The currently '''tested''' USB wireless network cards are shown below. Please test it by yourself for other models of USB wireless network cards. If you cannot use it, you need to transplant the corresponding USB wireless network card driver {| class="wikitable" style="width:800px;"

|-

~~| No.| Model~~||orangepi@orangepi:~$ '''aplay -~~| 1| RTL8723BU~~D hw:0,0 /usr/share/sounds/alsa/audio.wav'''

~~Support 2~~Playing WAVE 'audio.~~4G WIFI+BT4.0~~wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo|}</ol>

~~| [[File:pi3b-img240.png]]~~|-~~| 2| RTL8811~~==== HDMI Audio Play Test ====

~~Support 2~~# 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.~~4G +5G WIFI~~From the output below, you can know that the HDMI sound card is '''card 1'''

::{| ~~[[File~~class="wikitable" style="width:~~pi3b-img241.png]]~~800px;"

|-

| 3~~| RTL8821CU~~orangepi@orangepi:~$ '''aplay -l'''

~~Support 2.4G +5G WIFI~~**** List of PLAYBACK Hardware Devices ****

~~Support BT 4.2~~card 0: rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]

~~| <div class="figure">~~:Subdevices: 0/1

~~[[File~~:~~pi3b-img242.png|tb_imag e_share_1670833201 123]]~~Subdevice #0: subdevice #0

~~</div>~~|}'''card 1: rockchiphdmi [rockchip,hdmi], device 0: fe400000.i2s-i2s-hifi i2s-hifi-0 [fe400000.i2s-i2s-hifi i2s-hifi-0]'''

~~<~~:'''Subdevices: 0/~~span>==== RTL8723BU test ====~~1'''

:'''Subdevice # ~~First insert the RTL8723BU wireless network card module into the USB interface of the development board~~0: subdevice # ~~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~~0'''

~~orangepi@orangepi~~:~$ '''~~lsmod~~Subdevice #0: subdevice #0''' ~~Module Size Used by~~ ~~rfcomm 57344 16~~ ~~rtl8xxxu 106496 0~~ ~~rtk_btusb 61440 0~~|}

<li>~~You~~ Then use the '''aplay''' command to play the audio file that comes with the system. If the HDMI display or television can ~~see~~ hear the ~~loading information of~~ sound indicates that the ~~RTL8723BU module through the dmesg command~~hardware can be used normally</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''aplay -D hw:1,0 /usr/share/sounds/alsa/audio.wav'''|}</ol>

~~orangepi@orangepi:~$ '''dmesg'''~~=== Use the command to test the recording method ===

# 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

~~[ 83.438901] usb 2~~::{| class="wikitable" style="width:800px;" |-1| orangepi@orangepi: ~~new high-speed USB device number 2 using ehci~~~$ '''amixer -~~platform~~c 0 cset name='Capture MIC Path' 'Main Mic''''

~~[ 83.588375] usb 2~~orangepi@orangepi:~$ '''arecord -1D hw: ~~New USB device found~~0, ~~idVendor=0bda, idProduct=b720, bcdDevice= 2~~0 -d 5 -f cd -t wav /tmp/test.00wav'''|}

~~[ 83.588403] usb 2~~

~~[ 83.588422] usb 2-1: Product: 802.11n WLAN Adapter~~== Temperature Sensor ==

~~[ 83.588443] usb 2-1~~# The command to view the system temperature sensor is: ~~Manufacturer: Realtek~~

~~[ 83.588460] usb 2~~::{| class="wikitable" style="width:800px;" |-~~1: SerialNumber~~| orangepi@orangepi: ~~00e04c000001~~~$ '''sensors'''

~~[ 83.601974] Bluetooth: hci0: RTL: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723~~soc_thermal-virtual-0

~~[ 83.603894] Bluetooth~~Adapter: ~~hci0: RTL: rom_version status=0 version=1~~Virtual device

~~[ 83~~temp1: +41.~~603920] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_fw~~9°C (crit = +115.~~bin~~0°C)

~~[ 83.610108] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_config.bin~~

~~[ 83.611274] Bluetooth: hci0: RTL: cfg_sz 68, total sz 22564~~gpu_thermal-virtual-0

~~[ 83.658494] rtk_btusb~~Adapter: ~~Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-142432~~Virtual device

~~[ 83~~temp1: +43.~~658651] usbcore: registered new interface driver rtk_btusb~~8°C|}

~~[ 83.667124] usb~~ <ol start="2" style="list-1style-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: ~~This Realtek USB WiFi dongle (0x0bda~~~$ '''sudo smartctl -a /dev/nvme0 | grep "Temperature:~~0xb720) is untested!~~"'''Temperature: '''40 Celsius'''|}</li></ol>

~~[ 83.667137] usb 2~~

~~[ 83.890140] usb 2-1: Vendor: Realtek~~== 40 Pin interface pin explanation ==

~~[ 83.890153] usb 2-1: Product: 802.11n WLAN Adapter~~# Orange Pi 3B Development board 40 Pin interface pins, please refer to the figure below

~~[ 83.890159] usb 2-1: rtl8723bu_parse_efuse: dumping efuse (0x200 bytes):~~<div class="figure">

::[[File:pi3b-img254.~~.....~~png]]

~~[ 83.890412] usb~~ </div><ol start="2" style="list-style-1type: ~~RTL8723BU rev E (SMIC) 1T1R, TX queues 3, WiFi~~decimal;"><li>The function of the Orange Pi 3B development board 40 PIN interface pins is shown in the table below.<ol style=~~1, BT=1, GPS=0, HI PA=0~~"list-style-type: lower-alpha;"><li>Below is a complete pins of 40pin</li>

[ 83[File:pi3b-img255-1.~~890417~~png] ~~usb~~ ]</ol><ol start="2" style="list-1style-type: ~~RTL8723BU MAC: 00:13:ef:f4:58:ae~~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.~~890421~~png] ~~usb 2~~]</ol><ol start="3" style="list-1style-type: ~~rtl8xxxu: Loading firmware rtlwifi~~lower-alpha;"><li>The following form is a picture on the right half of the top table above, which can be seen clearly</~~rtl8723bu_nic.bin~~li>

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

~~[ 84.050893] Bluetooth: hci0: RTL: fw version 0x0e2f9f73~~

~~[ 84.266905] Bluetooth: RFCOMM TTY layer initialized~~== How to install wiringOP ==

~~[ 84.266949] Bluetooth~~{| class="wikitable" style="background-color:#ffffdc;width: ~~RFCOMM socket layer initialized~~800px;" |-~~[ 84~~| <big>'''Note that wiringOP has been pre -installed in the Linux image released by Orange Pi.~~266999] Bluetooth: RFCOMM ver 1~~Unless wiringOP's code is updated, it is not necessary to re -download and install. Just use it directly.11'''

~~[ 84.884270] usbcore: registered new interface driver rtl8xxxu~~

~~[ 84.912046] rtl8xxxu 2~~'''The storage path of the compiled wiringOP's Deb is wrapped in Orangepi-1Build:~~1.2 wlx0013eff458ae: renamed from wlan0~~'''

'''<~~ol start="4"~~ span style="~~list-style-type~~color: ~~decimal;~~blue">orangepi-build/external/cache/debs/arm64/wiringpi_x.xx.deb<li/span>~~Then you can see the RTL8723BU WIFI device node through the~~ '''~~sudo ifconfig''' command. Please refer to the WIFI connection test a [[\l|'''section for WIFI connection''']] and testing methods</li></ol>~~

~~orangepi@orangepi:~$ '''sudo ifconfig wlx0013eff458ae'''~~

~~wlx0013eff458ae: flags=4099<UP~~'''After entering the system,~~BROADCAST~~you can run the gpio readall command. If you can see the output below,~~MULTICAST> mtu 1500~~it means that wiringOP is pre -installed and can be used normally.'''</big>

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

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

~~RX errors 0 dropped 0 overruns 0 frame 0~~</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. Functions such as hardware PWM are not available.'''</big>|}

~~TX packets 0 bytes 0 (0.0 B)~~# Download the code of wiringOP

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt update'''

~~<ol start="5" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>Then you can see the USB Bluetooth device through the~~ ~$ '''~~hciconfig~~sudo apt install -y git''' ~~command</li></ol>~~

orangepi@orangepi:~$ '''~~sudo apt update && sudo apt install bluez~~git clone https://github.com/orangepi-xunlong/wiringOP.git -b next'''|}

~~orangepi@orangepi~~:~$ :{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that Orange Pi 3B needs to download the code of the wiringOP next branch, please don'~~hciconfig~~t miss the parameter of -b next.'''

~~hci0: Type: Primary Bus: '''USB'''~~

~~BD Address~~'''If there is a problem with the download code from GitHub, you can use the wiringOP source code that comes with the Linux image directly, and the storage location is: ~~00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16~~/usr/src/wiringOP'''</big>|}

~~DOWN~~<ol start="2" style="list-style-type: decimal;"><li>Compile and install wiringOP</li>

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

~~TX bytes~~orangepi@orangepi:~~23307 acl:0 sco:0 commands:125 errors:0~~~/wiringOP$ '''sudo ./build clean'''

orangepi@orangepi:~/wiringOP$ '''sudo ./build'''|}</ol><ol start="63" style="list-style-type: decimal;"><li>~~You can also see~~ Test the ~~Bluetooth icon on~~ output of the ~~desktop. At this time, Bluetooth has not been opened, so a red '''x''' will be displayed~~GPIO Readall command as follows</li~~></ol~~>

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

~~<ol start="7" style="list~~[[File:pi3b-~~style~~img258-~~type: decimal;"><li>Click '''Turn Bluetooth On''' to open Bluetooth</li></ol>~~1.png]]

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

~~<ol start~~=~~"8" style~~=~~"list-style-type: decimal;"><li>The display after opening Bluetooth is shown below</li></ol>~~40Pin interface GPIO, I2C, UART, SPI, and PWM test ==

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

~~<ol start="9" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>Please refer to the [[\l|~~~$ '''~~Bluetooth use method~~sudo vim /boot/orangepiEnv.txt'''~~]] for Bluetooth test method, so I won't go into details here.</li></ol>~~

'''overlays=spi3-m0-cs0-spidev i2c2-m1 i2c3-m0 uart7-m2 uart9-m2 pwm11-m1'''~~==== RTL8811 test ====~~|}

~~# First insert the RTL8811 wireless network card module into the USB interface of the development board.~~~~# Then the Linux system will automatically load the RTL8811 WIFI -related kernel modules. You can see that the kernel module below is automatically loaded through the lsmod command~~=== 40pin GPIO port test ===

~~orangepi@orangepi~~{| class="wikitable" style="background-color:~$ #ffffdc;width:800px;" |-| <big>'''~~lsmod~~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.'''

~~Module Size Used by~~

~~8821cu 1839104~~ '''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'''

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

~~<li>You can see the loading information of the RTL8811 module through the dmesg command</li></ol>~~

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

~~[ 118.618194] usb 2-1~~orangepi@orangepi3b: ~~new high-speed USB device number 2 using ehci-platform~~~$ '''sudo blink_all_gpio'''         #Remember to add Sudo permissions

[ ~~118.767152~~sudo] ~~usb 2-1~~password for orangepi: ~~New USB device found, idVendor=0bda, idProduct=c811, bcdDevice= 2.00~~       #You need to enter password here'''|}

~~[ 118~~# There are a total of '''28''' GPIO ports in the 40pins of the development board that can be used.~~767181] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3~~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

::[[ ~~118.767199] usb 2~~File:pi3b-img259-1~~: Product: 802~~.~~11ac NIC~~png]]

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

~~[ 118.767235] usb~~ {| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio mode 2 out'''|}</ol><ol start="3" style="list-1style-type: ~~SerialNumber: 123456~~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>

~~[ 119.500530] usbcore~~{| class="wikitable" style="width: ~~registered new interface driver rtl8821cu~~800px;" |-| root@orangepi:~/wiringOP# '''gpio write 2 0'''|}

~~[ 119.525498] rtl8821cu 2-1:1~~Using GPIO Readall, you can see the value of the No. 7 pin (V) to 0 ~~wlx1cbfced9d260: renamed from wlan0~~

[[File:pi3b-img260.png]]

</ol>

<li>Then set the GPIO port to output a high level. After setting, you can ~~see~~ use a multimeter to measure the ~~WiFi device node through~~ voltage value of the ~~'''sudo ifconfig''' command~~pin. ~~Please refer to~~ If it is 3.3v, it means that the ~~[[\l|'''WiFi connection test a section''']] for WIFI connection and testing methods~~high level is set successfully. ~~I won't go into details her~~</li~~></ol~~>

~~orangepi~~{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ /wiringOP# '''~~sudo ifconfig wlx1cbfced9d260~~gpio write 2 1'''|}

~~wlx1cbfced9d260: flags=4099<UP~~Using GPIO Readall,~~BROADCAST,MULTICAST> mtu 1500~~you can see the value of No. 7 pin (v) into 1

~~ether 1c~~[[File:bfpi3b-img261-1.png]]</ol><ol start="5" style="list-style-type:~~ce:d9:d2:60 txqueuelen 1000 (Ethernet)~~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>

~~RX packets 0 bytes 0 (0.0 B)~~

~~RX errors 0 dropped 0 overruns 0 frame 0~~=== 40pin GPIO port pull-down resistance setting method ===

~~TX packets 0 bytes 0 (0~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the 4 GPIO pins below Orange Pi 3B are invalid because there are 3.~~0 B)~~3V on the outside, so setting drop-down is invalid. Other pins can be set normally '''</big>

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~[[File:pi3b-img262-1.png|center]]|}

~~==== RTL8821CU test ====~~corresponding wPi serial number 5—to demonstrate how to set up and down pull-down resistance of the GPIO port

~~# 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~~ ~~orangepi@orangepi~~:~~~$ '''lsusb | grep "Realtek"'''~~ ~~Bus 002 Device 003~~: ~~ID 0bda~~[[File:~~c820 Realtek Semiconductor Corp. 802.11ac NIC~~ ~~orangepi@orangepi:~$ '''lsusb | grep "Realtek"'''~~ ~~Bus 002 Device 002: ID 0bda:1a2b Realtek Semiconductor Corp. RTL8188GU 802.11n WLAN Adapter ('''Driver CDROM Mode''')~~ ~~'''If the USB WIFI module seen by the lsusb command is in Driver CDROM Mode, re~~ pi3b-img263-~~insert the USB WiFi module~~1. ~~If not, please manually execute the following command to switch the mode: '''~~ ~~orangepi@orangepi:~$ '''sudo usb_modeswitch -KW -v 0bda -p 1a2b'''~~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>~~The Linux system will automatically load~~ After the ~~RTL8821CU Bluetooth and WIFI -related kernel modules. You can see that the kernel module below~~ setting is ~~automatically loaded through~~ set to input mode, execute the ~~lsmod~~ following commandto set the GPIO port as the pull-down mode</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| ~~orangepi~~root@orangepi:~$ /wiringOP# '''~~lsmod~~gpio mode 5 up'''|}~~Module Size Used by~~ ~~8821cu 1839104 0~~ ~~rtk_btusb 61440 0~~</ol>

<li>~~You can see~~ Then enter the ~~loading information~~ following command to read the level of the ~~rtl8821cu 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'''

~~......~~'''0'''|}</ol>

~~[ 57.083693] usb 2-1: new high-speed USB device number 2 using ehci-platform~~=== 40pin SPI Test ===

~~[ 57.231888] usb 2-1: New USB device found~~# From the schematic diagram of the 40PIN interface, ~~idVendor=0bda, idProduct=1a2b, bcdDevice= 2.00~~the SPI available for Orange Pi 3B is spi3

::[[ 57File:pi3b-img264-1.~~231916~~png]] ~~usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0~~

<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'''[[ 57File:pi3b-1.~~231937~~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: ~~Product~~pi3b-5.png]]</li><li>Then select '''<Reboot>''' to restart the system to make the configuration take effect[[File: ~~DISK~~pi3b-6.png]]</li></ol></li></ol>

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

~~[ 57.242594] usb-storage 2~~{| class="wikitable" style="width:800px;" |-1| orangepi@orangepi:1~$ '''ls /dev/spidev3.0~~: USB Mass Storage device detected~~'''

~~[ 57~~/dev/spidev3.~~245674] scsi host0: usb~~0|}</ol><ol start="4" style="list-~~storage 2~~style-1type:~~1.0~~decimal;"><li>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 data of TX and RX are inconsistent</li>

~~[ 58.069172] usb 2~~{| class="wikitable" style="width:800px;" |-1| orangepi@orangepi: ~~USB disconnect, device number 2~~~$ '''sudo spidev_test -v -D /dev/spidev3.0'''

~~[ 58.440025] usb 2-1~~spi mode: ~~new high-speed USB device number 3 using ehci-platform~~0x0

~~[ 58.587819] usb 2-1~~bits per word: ~~New USB device found, idVendor=0bda, idProduct=c820, bcdDevice= 2.00~~8

~~[ 58.587827] usb 2-1~~max speed: ~~New USB device strings: Mfr=1, Product=2, SerialNumber=3~~500000 Hz (500 KHz)

~~[ 58~~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 | ......@.…▒...~~587833] usb 2-1: Product: 802~~.~~11ac NIC~~..............▒.

~~[ 58~~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 | ............................….~~587838] usb 2~~|}</ol><ol start="5" style="list-style-1type: ~~Manufacturer: Realtek~~decimal;"><li>Then short-circuit the two pins of mosi (pin 19 in the 40pin interface) and miso (pin 21 in the 40pin interface) of SPI3, and then run the output of spidev_test as follows, you can see the sending and receiving same data</li>

[ 58[File:pi3b-img265.~~587844~~png]] ~~usb 2~~{| class="wikitable" style="width:800px;" |-1| orangepi@orangepi: ~~SerialNumber: 123456~~~$ '''sudo spidev_test -v -D /dev/spidev3.0'''

~~[ 58.610463] rtk_btusb~~spi mode: ~~Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-142432~~0x0

~~[ 58.610656] usbcore~~bits per word: ~~registered new interface driver rtk_btusb~~8

~~[ 58.634631] Bluetooth~~max speed: ~~hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821~~500000 Hz (500 KHz)

~~[ 58~~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 | ......@.…▒..................▒.~~636729] Bluetooth: hci0: RTL: rom_version status=0 version=1~~

~~[ 58.636740] Bluetooth: hci0: RTL~~RX | FF FF FF FF FF FF '''40 00 00 00 00 95</~~rtl8821c_fw~~span>''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒.............~~bin~~.....▒.|}</ol>

~~[ 58.664190] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin~~=== 40pin I2C Test ===

~~[ 58.664746] Bluetooth: hci0: RTL: cfg_sz 10~~# From the table below, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total ~~sz 31990~~of three groups of I2C bus.

::[[ 59File:pi3b-img266-1.~~122471~~png]] ~~Bluetooth: hci0: RTL: fw version 0x829a7644~~

~~[ 59~~::{| 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.~~265513] usbcore: registered new interface driver rtl8821cu~~The two cannot be opened at the same time. i2c3_m0 and uart3_m0 are also reused. The two cannot be opened at the same time'''</big>|}

<ol start="2" style="list-style-type: decimal;"><li>In the linux system, the I2C bus in the 40 pin is closed by default, and it needs to be opened manually to use it. The detailed steps are as follows:<ol style="list-style-type: lower-alpha;"><li>First run '''orangepi-config''', normal users remember to add '''sudo''' permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li><li>Then select '''System'''[[File:pi3b-1.png]]</li><li>Then select '''Hardware'''[[ 59File:pi3b-2.~~280119~~png]] ~~rtl8821cu~~ </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-14.png]]</li><li>Then select '''<Back>'''[[File:1pi3b-5.~~2 wlx90de80521825~~png]]</li><li>Then select '''<Reboot>''' to restart the system to make the configuration take effect[[File: ~~renamed from wlan0~~pi3b-6.png]]</li></ol></li></ol>

<ol start="53" style="list-style-type: decimal;"><li>~~Then you can see~~ After starting the ~~RTL8821CU WiFi~~ Linux system, first confirm that the i2c device node ~~through the '''sudo ifconfig''' command. Please refer to the [[\l~~exists under/dev</li>{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~# '''~~WiFi connection test~~ls /dev/i2c-*'''~~]] a section for WIFI connection and testing methods.</li></ol>~~

~~orangepi@orangepi:~$~~ /dev/i2c-0      '''/dev/i2c-2'''      '''/dev/i2c-3'''      '''~~sudo ifconfig wlx90de80521825~~/dev/i2c-4'''     /dev/i2c-6|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then connect a i2c device on the i2c pin of the 40Pin connector</li>

~~wlx90de80521825~~{| class="wikitable" style="width: ~~flags=4099&lt~~800px;~~UP,BROADCAST,MULTICAST&gt~~text-align: center; ~~mtu 1500~~"|-||i2c2-m1~~ether 00:13:ef:f4:58:ae txqueuelen 1000 (Ethernet)~~|i2c3-m0|i2c4-m0|-| Sda Pin|Corresponding to No. 3 pin|Corresponding to No. 27 pin|Corresponding to No. 19 pin|-| Sck Pin|Corresponding to No. 5 pin|Corresponding to No. 28 pin~~RX packets 0 bytes 0 (0~~|Corresponding to No.~~0 B)~~23 pin|-| ~~RX errors 0 dropped 0 overruns 0 frame 0~~Vcc Pin|Corresponding to No. 1 pin|Corresponding to No. 1 pin~~TX packets 0 bytes 0 (0~~|Corresponding to No.~~0 B)~~1 pin|-| ~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~Gnd Pin|Corresponding to No. 6 pin|Corresponding to No. 6 pin|Corresponding to No. 6 pin|}</ol><ol start="65" style="list-style-type: decimal;"><li>Then ~~you can see the USB Bluetooth device through~~ use the '''~~hciconfig~~i2cdetect -y''' commandif the address of the connected I2C device can be detected, it means that the I2C can be used normally</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ ~~'''sudo apt-get update &&~~ sudo ~~apt-get install~~ i2cdetect -y ~~bluez'''~~2 #i2c2 command

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

~~hci0~~orangepi@orangepi: ~~Type: Primary Bus: '''USB'''~~~$ sudo i2cdetect -y 4 #i2c4 command|}

~~BD Address: 00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16~~<div class="figure">

~~DOWN~~[[File:pi3b-img267.png]]

~~RX bytes:1252 acl:0 sco:0 events:125 errors:0~~</div></ol>

~~TX bytes:23307 acl:0 sco:0 commands:125 errors:0~~=== 40pin UART test ===

~~<ol start="7" style="list-style-type: decimal;"><li>Bluetooth icons~~ # As can ~~also~~ be seen on from the ~~desktop. At this time~~table below, the uart available for Orange Pi 3B is uart3, ~~Bluetooth has not been opened~~uart7, ~~so a red '''x''' will be displayed</li></ol>~~and uart9. There are three sets of uart bus

::[[File:pi3b-~~img243~~img268-1.png~~|576x157px~~]]

~~<ol start~~::{| class="8wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Click~~ '''~~Turn Bluetooth On~~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''' ~~to open Bluetooth~~</~~li></ol~~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'''[[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 UART configuration you want to open[[File:pi3b-3-3.png]]</li><li>Then select '''<Save>''' to save[[File:pi3b-~~img244~~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~~|576x262px~~]]</li></ol></li></ol>

<ol start="93" style="list-style-type: decimal;"><li>~~The display after opening Bluetooth~~ After entering the Linux system, first confirm whether there is ~~shown below~~a device node corresponding to uart under/dev</li~~></ol~~>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img245.png~~|~~576x164px]]~~orangepi@orangepi:~# '''ls /dev/ttyS*'''

/dev/ttyS1      '''/dev/ttyS3      /dev/ttyS7      /dev/ttyS9'''|}</ol><ol start="104" style="list-style-type: decimal;"><li>~~Please refer to~~ Then start testing the ~~[[\l|'''Bluetooth~~ uart interface, first use ~~chapter''']] for~~ the ~~Bluetooth test method. I won't go into details her~~rx and tx of the uart interface to be tested by DuPont</li>~~</ol>~~ {| 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 22 pin|}

[[File:pi3b-img269-1.png]]<~~span id~~/ol><ol start="~~usb~~5" style="list-~~camera~~style-~~test~~type: decimal;"><li>Use the '''gpio serial''' command to test the loop function of the serial port as shown below. If you can see the following printing, it means that the serial communication is normal</~~span~~p><ol style=~~== USB Camera~~ "list-style-type: lower-alpha;"><li>Test UART3</li>{| class="wikitable" style=="width:800px;" |-| orangepi@orangepi:~$ '''sudo gpio serial /dev/ttyS3'''

[sudo] password for orangepi: # ~~First, you need to prepare a USB camera that supports~~ Enter the ~~UVC protocol in the figure below, and then insert the USB camera into the USB interface of the Orange PI development board~~password here.

~~[[File:pi3b-img13.png|259x150px]]~~

~~<ol start="2" style="list~~Out: 0: -~~style-type: decimal~~>">~~<li>You can see that the USB camera's device node information is/dev/video0 through the v4l2-ctl command</li></ol>~~0

~~orangepi@orangepi~~Out: 1:~~~$ '''v4l2-ctl --list~~-~~devices'''~~> 1

~~Q8 HD Webcam~~Out: 2: ~~Q8 HD Webcam ('''usb'''~~-~~fc880000.usb-1):~~> 2

~~'''/dev/video0'''~~Out: 3: -> 3

~~/dev/video1~~Out: 4: -> 4

Out: 5: -> 5^C|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Test UART7</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo gpio serial /dev/~~media0~~ttyS7'''

~~'''Note that l in v4l2 is a lowercase letter l, not numbers 1~~[sudo] password for orangepi: #Enter the password here.~~'''~~

~~'''In addition, Video's serial number is not necessarily Video0, please refer to what you see.'''~~

~~<ol start="3" style="list~~Out: 0: -~~style-type: decimal~~>">~~<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></ol>~~0

~~[[File~~Out: 1:~~pi3b~~-~~img246.png|474x302px]]~~> 1

~~The interface after cheese opens the USB camera is shown in the figure below~~Out: 2: -> 2

~~[[File~~Out: 3:~~pi3b~~-~~img247.png|473x277px]]~~> 3

~~<ol start="~~Out: 4~~" style="list-style-type: decimal;"><li>How to test the USB camera using fswebcam<ol style="list-style-type~~: ~~lower~~-~~alpha~~>">~~<li>Install fswebcam</li></ol></li></ol>~~4

Out: 5: -> 5^C|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Test UART9</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo~~''' '''apt update~~gpio serial /dev/ttyS9'''

~~orangepi@~~[sudo] password for orangepi:~~~$ '''sudo apt-get install -y fswebcam'''~~#Enter the password here.

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

~~<li>After installing fswebcam, you can use the following command to take pictures~~

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

~~<li>-d The option is used to specify the device node of the USB camera</li>~~

~~<li>--no-banner Used to remove the watermark of photos</li>~~

~~<li>-r The option is used to specify the resolution of the photo</li>~~

~~<li>-S The option is set to the number of frames before skipping</li>~~

~~<li>./image.jpg The name and path for setting the generated photos</li></ol>~~

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

~~orangepi@orangepi~~Out: 0:~~~$ '''sudo''' '''fswebcam~~ -~~d /dev/video0 \'''~~> 0

~~'''~~Out: 1: -~~-no-banner -r 1280x720 -S 5 ./image.jpg'''~~> 1

~~<ol start="3" style="list-style-type~~Out: 2: ~~lower~~-~~alpha~~>">~~<li>In the service version of the Linux system, you can use the scp command to pass the picture to the Ubuntu PC to watch after taking the photo</li></ol>~~2

~~orangepi@orangepi~~Out:~~~$ '''scp image.jpg''' [mailto~~3:~~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）'''~~-> 3

~~<ol start="~~Out: 4~~" style="list-style-type~~: ~~lower~~-~~alpha~~>">~~<li>In the desktop version of the Linux system, you can directly view the shot pictures through the HDMI display</li></ol>~~4

Out: 5: -> 5^C|}</ol></li></ol>~~== Audio Test ==~~

~~~~==~~= Test audio methods in the desktop system~~ PWM test method ===

# ~~First open~~ From the ~~file manager~~table below, the pwm11 available for Orange Pi 3B

::[[File:pi3b-~~img248~~img270-1.png~~|357x176px~~]]

<li>~~Then find the following file (if there is no audio file in~~ In the linux system, ~~you can upload a audio file to~~ the ~~system~~ PWM in the 40 pin is turned off by ~~yourself)</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img249.png|236x186px|图片10]]~~ ~~</div><ol start="3" style="list-style-type: decimal;"><li>Then select the audio.wav file~~default, ~~right -click~~ and ~~select VLC~~ it needs to ~~open~~ be turned on manually before it ~~to start playing</li></ol>~~ ~~[[File:pi3b-img250~~can be used.~~png|288x234px]]~~ ~~<ol start="4" style="list-style-type~~The detailed steps are as follows: ~~decimal;"><li>Methods to switch different audio equipment such as HDMI playback and headset playback~~

<li>First run '''orangepi-config''', normal users remember to add sudo permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li><li>Then select '''System'''[[File: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-3-4.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 ~~volume control interface~~configuration take effect[[File:pi3b-6.png]]</li></ol></li></ol>

~~[[File~~<ol start="3" style="list-style-type: decimal;"><li>After opening a pwm, there will be an extra pwmchipX in '''/sys/class/pwm/''' (X is a specific number), for example, after opening pwm11, check the pwmchipX under '''/sys/class/pwm/''' one becomes two</li>{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img251.png~~|~~308x169px]]~~orangepi@orangepi:~$ '''ls /sys/class/pwm/'''

pwmchip0 pwmchip1|}</ol><ol start="24" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~When playing audio~~Which pwmchip above corresponds to pwm11, let's check the output of the ~~audio equipment options that play software can be used will be displayed in~~ '''~~Playback~~ls /sys/class/pwm/ -l'''~~. As~~ command first, as shown in below:</li><li>Then it can be known from the ~~figure~~ table belowthat the base address of the pwm11 register is fe6f0030, and then look at the output of the '''ls /sys/class/pwm/ -l''' command, ~~which audio equipment~~ you ~~need~~ can see that pwmchip1 is linked to ~~play here can be set~~fe6f0030.pwm, so pwm11 corresponds to pwmchip as pwmchip1</lip></olli>

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

~~=== How to play audio with commands ===~~img271.png]]

<~~span id~~/div></ol><ol start="~~headphone-interface-play~~6" style="list-~~audio~~style-~~test~~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)</~~span~~li>{| class="wikitable" style=~~== Headphone interface play audio test ====~~"width:800px;" |-| root@orangepi:~# '''echo 0 > /sys/class/pwm/pwmchip1/export'''

root@orangepi:~# ~~First insert the headset into the headphone jack of the development board~~'''echo 20000000 > /sys/class/pwm/pwmchip1/pwm0/period'''

~~[[File~~root@orangepi:~~pi3b-img253.png|395x112px]]~~~# '''echo 1000000 > /sys/class/pwm/pwmchip1/pwm0/duty_cycle'''

~~<ol start="2" style="list-style-type~~root@orangepi: ~~decimal;"><li>Then you can check the sound card device supported by the Linux system through the~~ ~# '''~~aplay -l~~echo 1 > /sys/class/pwm/pwmchip1/pwm0/enable''' ~~command. From the output below, it can be seen that '''card 0''' is the sound card device with RK809, which is the sound card device of the headset</li></ol>~~|}

~~orangepi@orangepi~~[[File:~~~$ '''aplay~~ pi3b-~~l'''~~img272.png]]

**** List <li>The test method of PLAYBACK Hardware Devices ****pwm11 demonstrated above is similar to other pwm test methods.</li></ol>

~~'''card 0: rockchiprk809 [rockchip~~== How to install and use wiringOP-~~rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]'''~~Python ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~Subdevices: 0/1~~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.'''

~~'''Subdevice #0: subdevice #0'''~~

~~card 1: rockchiphdmi [rockchip~~'''In addition,~~hdmi], device 0: fe400000.i2s-i2s-hifi i2s-hifi-0 [fe400000~~please note that all the following commands are operated under the root user.~~i2s-i2s-hifi i2s-hifi-0]~~'''</big>|}

~~Subdevices: 0~~</1span>=== wiringOP-Python installation method ===

~~Subdevice~~ #~~0: subdevice #0~~First install the dependency package

~~Subdevice #0~~: ~~subdevice~~ :{| class="wikitable" style="width:800px;" |-| root@orangepi:~#0'''sudo apt-get update'''

~~<ol start="3" style="list-style-type~~root@orangepi: ~~decimal;"><li>Then use the~~ ~# '''~~aplay~~sudo apt-get -y install git swig python3-dev python3-setuptools''' ~~command to play the audio file that comes with the system. If the headset can hear the sound, it means that the hardware can be used normally</li></ol>~~|}

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~$ decimal;"><li>Then use the following command to download the source code of wiringOP-Python</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~aplay~~ Note that the following git clone-~~D hw:0~~-recursivee command will automatically download the source code of wiringOP,~~0 /usr/share/sounds/alsa/audio~~because wiringOP-Python depends on wiringOP. Please make sure that the download process does not report an error due to network problems.~~wav~~'''

~~Playing WAVE 'audio.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo~~

~~<span id="hdmi~~'''If there is a problem with the download code from GitHub, you can use the wiringOP-~~audio-play~~Python source code that comes with the Linux image directly, and the storage location is:/usr/src/wiringOP-~~test">~~Python'''</~~span~~big>|}{| class="wikitable" style=~~== HDMI Audio Play Test ====~~"width:800px;" |-| root@orangepi:~# '''git clone --recursive https://github.com/orangepi-xunlong/wiringOP-Python -b next'''

root@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~~ '''~~card 1~~cd wiringOP-Python'''

root@orangepi:~/wiringOP-Python# '''git submodule update --init --remote'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then use the following command to compile wiringOP-Python and install it into the Linux system of the development board</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ # '''~~aplay~~ cd wiringOP-lPython'''

~~**** List of PLAYBACK Hardware Devices ****~~root@orangepi:~/wiringOP-Python# '''python3 generate-bindings.py > bindings.i'''

~~card 0~~root@orangepi: ~~rockchiprk809 [rockchip~~~/wiringOP-~~rk809], device 0: dailink~~Python# '''sudo python3 setup.py install'''|}</ol><ol start="4" style="list-~~multicodecs rk817~~style-~~hifi-0 [dailink-multicodecs rk817-hifi~~type: decimal;"><li>Then enter the following command. If there is a help information output, it means that Wiringop-0]Python is successfully installed. Press the '''q''' key to exit the interface of the help information</li>

~~Subdevices~~{| class="wikitable" style="width: 0800px;" |-| root@orangepi:~/1wiringOP-Python# '''python3 -c "import wiringpi; help(wiringpi)"'''

~~Subdevice #0~~Help on module wiringpi: ~~subdevice #0~~

~~'''card 1: rockchiphdmi [rockchip,hdmi], device 0: fe400000.i2s-i2s-hifi i2s-hifi-0 [fe400000.i2s-i2s-hifi i2s-hifi-0]'''~~

~~'''Subdevices: 0/1'''~~NAME

~~'''Subdevice #0~~: ~~subdevice #0'''~~wiringpi

~~'''Subdevice #0: subdevice #0'''~~

~~<ol start="3" style="list-style-type: decimal;"><li>Then use the '''aplay''' command to play the audio file that comes with the system. If the HDMI display or television can hear the sound indicates that the hardware can be used normally</li></ol>~~DESCRIPTION

~~orangepi@orangepi~~:~~~$ '''aplay -D hw~~# This file was automatically generated by SWIG (http:~~1,0~~ /~~usr~~/~~share/sounds/alsa/audio~~www.swig.org).~~wav'''~~

~~=== Use the command to test the recording method ===~~: # Version 4.0.2

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

~~orangepi@orangepi~~:~~~$ '''amixer~~ # Do not make changes to this file unless you know what you are doing-~~c 0 cset name='Capture MIC Path' 'Main Mic''''~~-modify

~~orangepi~~: # the SWIG interface file instead.|}</ol><ol start="5" style="list-style-type: decimal;"><li>Test whether the wiringOP-Python is installed successfully under the Python command line is shown below:<ol style="list-style-type: lower-alpha;"><li>First use the Python3 command to enter the command line mode of Python3</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ # '''~~arecord -D hw:0,0 -d 5 -f cd -t wav /tmp/test.wav~~python3'''|}<~~span id~~/ol><ol start="2" style="~~temperature~~list-~~sensor~~style-type: lower-alpha;"><li>Then import the Python module of WiringPi</~~span~~li>{| class="wikitable" style= ~~Temperature Sensor~~ "width:800px;" |-| >>> '''import wiringpi;'''|}</ol><ol start="3" style="list-style-type: lower-alpha;"> ~~# The~~ <li>Enter the following command to view the help information of wiringOP-Python, and press the ~~system temperature sensor is~~'''q''' key to exit the interface of the help information</li>{| class="wikitable" style="width: 800px;" |-| ~~orangepi@orangepi:~$~~ >>> '''~~sensors~~help(wiringpi)''' ~~soc_thermal-virtual-0~~

~~Adapter~~Help on module wiringpi: ~~Virtual device~~

~~temp1: +41.9°C (crit = +115.0°C)~~

~~gpu_thermal-virtual-0~~NAME

~~Adapter~~: ~~Virtual device~~wiringpi

~~temp1: +43.8°C~~

~~<ol start="2" style="list-style-type: decimal;"><li>The command 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>~~DESCRIPTION

~~<~~: # This file was automatically generated by SWIG (http:/~~span>== 40 Pin interface pin explanation ==~~/www.swig.org).

: # ~~Orange Pi 3B Development board 40 Pin interface pins, please refer to the figure below~~Version 4.0.2

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

~~[[File~~:~~pi3b~~# Do not make changes to this file unless you know what you are doing-~~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)]]~~modify

~~</div><ol start="2" style="list-style-type~~: ~~decimal;"><li>The function of~~ # the ~~Orange Pi 3B development board 40 PIN~~ SWIG interface ~~pins is shown in the table below~~file instead.~~<ol style="list-style-type: lower-alpha;"><li>Below is a complete pins of 40pin</li></ol></li></ol>~~

~~[[File:pi3b-img255.png|575x160px]]~~

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

~~[[File~~:~~pi3b-img256~~builtins.~~png|478x267px]]~~object

~~<ol start="3" style="list-style-type~~: ~~lower-alpha;"><li>The following form is a picture on the right half of the top table above, which can be seen clearly</li></ol>~~:GPIO

~~[[File~~:~~pi3b-img257.png|479x266px]]~~:I2C

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

~~== How to install Wiringop ==~~::nes

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

~~'''The storage path of the compiled Wiringop's Deb is wrapped in Orangepi-Build~~: ~~'''~~class GPIO(builtins.object)

~~'''orangepi-build/external/cache/debs/arm64/wiringpi_x.xx.deb'''~~:| GPIO(pinmode=0)

~~'''After entering the system, you can run the gpio readall command. If you can see the output below, it means that wiringOP is pre -installed and can be used normally.'''~~:|

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

~~[[File:pi3b~~>>>|}</ol></li></ol>

~~</div>'''wiringOP is currently adapted to set the~~ === 40pin 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.'''~~test ===

{| class="wikitable" style="background-color:# ~~Download~~ ffffdc;width:800px;" |-| <big>'''wiringOP-Python is the ~~code of Wiringop~~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>

~~orangepi@orangepi:~$ '''sudo apt update'''~~<div class="figure">

~~orangepi@orangepi~~[[File:~~~$ '''sudo apt install~~ pi3b-~~y git'''~~img258.png|center]]

~~orangepi@orangepi:~$ '''git clone https:~~</~~/github~~div>|}# Below the No.~~com/orangepi~~ 7 pin — corresponding to GPIO4_a4 -~~xunlong/wiringOP.git~~ corresponding WPI serial number 2 -~~b next'''~~ ~~'''Note that Orange Pi 3B needs~~ to ~~download~~ demonstrate how to set the ~~code~~ height of the ~~wiringOP next branch, please don't miss the parameter of -b next.'''~~GPIO port

~~'''If there is a problem with the download code from GitHub, you can use the wiringOP source code that comes with the Linux image directly, and the storage location is~~:~~/usr/src/wiringOP'''~~:[[File:pi3b-img259.png]]

<li>~~Compile and install wiringOP~~The steps of the command test are shown below directly: <ol style="list-style-type: lower-alpha;"><li>First set the GPIO port to the output mode. The first parameter of the '''pinMode''' function is the serial number of the wpi corresponding to the pin, and the second parameter is the GPIO mode</olli>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''python3 -c "import wiringpi; \'''

~~orangepi@orangepi:~$~~ '''~~cd wiringOP~~from wiringpi import GPIO; wiringpi.wiringPiSetup() ; \'''

~~orangepi~~'''wiringpi.pinMode(2, GPIO.OUTPUT) ; "'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then set the GPIO port output low level. After setting, you can use the voltage of the voltage of the universal meter to measure the pins. If it is 0V, it means that the low -power flat is successful</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP$ -Python# '''~~sudo ./build clean~~python3 -c "import wiringpi; \'''

~~orangepi@orangepi:~/wiringOP$~~ '''~~sudo~~ from wiringpi import GPIO; wiringpi.~~/build~~wiringPiSetup() ;\'''

'''wiringpi.digitalWrite(2, GPIO.LOW)"'''|}</ol><ol start="3" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Test~~ Then set the GPIO port output high level. After setting, you can use the value of the voltage of the ~~GPIO Readall command as follows~~pins with a multimeter. If it is 3.3V, it means that the high -power flat is successful.</li><{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~ol>~~wiringOP-Python# '''python3 -c "import wiringpi; \'''

~~<div class="figure">~~'''from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\'''

~~[[File~~'''wiringpi.digitalWrite(2, GPIO.HIGH)"'''|}</ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>The steps of testing in the command line of Python3 are shown below: <ol style="list-style-type:~~pi3b~~lower-~~img258.png~~alpha;"><li>First use the Python3 command to enter the command line mode of Python3</li>{| class="wikitable" style="width:800px;" |~~575x355px~~-|~~66AC(IBG%N8L~~root@~~Y7(1BZPS`N]]~~orangepi:~# '''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;" |-| >>> '''import wiringpi'''

>>> '''from wiringpi import GPIO'''|}</~~div~~ol><~~span id~~ol start="~~pin-interface-gpio-i2c~~3" style="list-~~uart~~style-~~spi~~type: lower-~~and-pwm-test~~alpha;"><~~/span~~li>~~== 40Pin interface~~ Then set the GPIO~~, I2C, UART, SPI~~port as the output mode. The first parameter of the '''pinMode''' function is the serial number of the wpi corresponding to the pin, and ~~PWM test~~ the second parameter is the GPIO mode.</li>{| class="wikitable" style="width:800px;" |-| >>> '''wiringpi.wiringPiSetup()'''

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

~~orangepi~~>>> '''wiringpi.pinMode(2, GPIO.OUTPUT)'''|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then set the GPIO port output low level. After setting, you can use the value of the voltage of the pins with a multimeter. If it is 0V, it means that the low -power flat is set.</li>{| class="wikitable" style="width:800px;" |-| >>> '''wiringpi.digitalWrite(2, GPIO.LOW)'''|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then set the GPIO port output high level. After setting, you can use the value of the voltage of the pins with a multimeter. If it is 3.3V, it means that the high -power flat is successful</li>{| class="wikitable" style="width:800px;" |-| >>> '''wiringpi.digitalWrite(2, GPIO.HIGH)'''|}</ol></li></ol><ol start="4" style="list-style-type: decimal;"><li>Wiringop-Python Sets GPIO high and low levels in the Python code. For reference to the '''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# '''~~sudo vim /boot/orangepiEnv.txt~~cd examples'''

root@orangepi:~/wiringOP-Python/examples# '''~~overlays=spi3-m0-cs0-spidev i2c2-m1 i2c3-m0 uart7-m2 uart9-m2 pwm11-m1~~ls blink.py'''

~~=== 40pin GPIO port test ===~~'''blink.py'''

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 blink.py'''|}</ol>

~~'''After running the blink_all_gpio program, when using a multimeter to measure the level of the GPIO port, you will find that the GPIO pin will be switched between 0 and 3.3v. Use this program to~~ === 40pin SPI test ~~whether the GPIO port can work normally'''~~===

~~'''The method~~ # From the schematic diagram of ~~running blink_all_gpio program~~ the 40pin interface, the SPI available for Orange Pi 3B is ~~shown below: '''~~spi3

~~orangepi@orangepi3b~~:~~~$ '''sudo blink_all_gpio''' #Remember to add Sudo permissions~~:[[File:pi3b-img264.png]]

~~[sudo] password for orangepi~~::{| class="wikitable" style="background-color: #~~You need~~ ffffdc;width:800px;" |-| <big>'''In the Linux system, the spi3 in 40pin is closed by default, and it needs to be opened manually to ~~enter a password here~~use.'''

# A total of 28 GPIO ports can be used in the development board 40pin. 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:pi3b-img259~~'''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 spi4.'''</big>

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

~~<li>First set the GPIO port as the output mode, the third parameter needs to enter the serial number of the wPi corresponding to the pins</li></ol>~~

~~root~~orangepi@orangepi:~~~/wiringOP#~~ $ '''~~gpio mode 2 out~~sudo vim /boot/orangepiEnv.txt'''

'''<~~ol start~~span style="3color:#FF0000" ~~style~~>overlays=~~"list~~spi3-~~style~~m0-~~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~~ cs0-~~electric flat is successful~~spidev</~~li></ol~~span>'''|}

~~root~~<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#~~ $ '''~~gpio write 2~~ ls /dev/spidev3.0'''

~~Using GPIO Readall~~/dev/spidev3.0|}</ol><ol start="3" style="list-style-type: decimal;"><li>You can then use the spi back function under the '''spidev_test.py''' program in Examples. The '''spidev_test.py''' program needs to specify the following two parameters: <ol style="list-style-type: lower-alpha;"><li>'''--channel''': Specify the channel number of SPI</li><li>'''--port''': Specify the port number of SPI</li></ol></li><li>Do not pick up the two pins of the SPI3 MOSI and MISO in short, ~~you~~ and run the output result of the spidev_test.py as shown below. You can see that the ~~value~~ data of ~~the No. 7 pin (v) to 0~~TX and RX are inconsistent</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''cd examples'''

~~[[File~~root@orangepi:~~pi3b~~~/wiringOP-~~img260~~Python/examples# '''python3 spidev_test.~~png|576x120px]]~~py \'''

~~<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~~ channel 3~~.3V, it means that the high~~-~~electricity level is successful</li></ol>~~-port 0'''

~~root@orangepi~~spi mode:~~~/wiringOP# '''gpio write 2 1'''~~0x0

~~Using GPIO Readall, you can see the value of No. 7 pin~~ max speed: 500000 Hz (v500 KHz) ~~into 1~~ Opening device /dev/spidev3.0

~~[[File~~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 |......@.......~~png~~…|~~576x118px]]~~

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>

<li>~~The setting method of other~~ Then use the TXD (No. 19 pins ~~is similar~~in the 40Pin interface) and RXD (No. ~~Just modify~~ 21 pins in the ~~serial number~~ 40pin interface) of the ~~wPi sequence number as~~ DuPont line short connection SPI3. Like sending and receiving data, it means that the ~~corresponding serial number corresponding to the pin~~SPI3 loop test is normal</li><{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~ol>~~wiringOP-Python# '''cd examples'''

~~<~~Python/~~span>=== 40Pin GPIO Port -down and downward pull -down resistance setting method ===~~examples# '''python3 spidev_test.py \'''

'''~~Note that the 4 GPIO pins below Orange Pi 3B are invalid because there are~~ --channel 3~~.3V on the outside, so setting drop~~ -~~down is invalid. Other pins can be set normally~~-port 0'''

~~[[File~~spi mode:~~pi3b-img262.png|575x353px]]~~0x0

~~# Below the No. 11 pin—corresponding to GPIO 3_C6-corresponding WPI serial number 5—to demonstrate how to set up and down pull-down resistance of the GPIO port~~max speed: 500000 Hz (500 KHz)

~~[[File:pi3b-img263~~Opening device /dev/spidev3.~~png|576x147px]]~~0

TX | FF FF FF FF FF FF '''<~~ol start="2"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">40 00 00 00 00 95<li/span>~~First of all, you need to set the GPIO port as the input mode~~''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |...... ~~The third parameter needs to enter the serial number of the wpi corresponding to the pins</li></ol>~~@.......…|

~~root@orangepi:~/wiringOP#~~ RX | FF FF FF FF FF FF '''~~gpio mode 5 in~~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>

~~<ol start~~=~~"3" style~~=~~"list-style-type: decimal;"><li>After the setting is set to input mode, execute the following command to set the GPIO port as the pull -down mode</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 5 up'''~~li>

~~<ol start="4" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Then enter the following command to read the level of the GPIO port~~img266. ~~If the level is 1, it means that the drawing mode is successful</li></ol>~~png]]

~~root@orangepi:~/wiringOP# '''gpio read 5'''~~ ~~'''1'''~~ ~~<ol start~~{| class="5wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">~~<li>Then execute the following command to set the GPIO port as the drop~~|-~~down mode</li>~~| <~~/ol~~big> ~~root@orangepi:~/wiringOP#~~ '''~~gpio mode 5 down~~It can be seen from the above table that I2C4_M0 and SPI3_M0 are pins. The two cannot be opened at the same time. I2C3_M0 and UART3_M0 are also reused. The two cannot be opened at the same time'''</big>|}~~<ol start~~{| class="6wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Then enter~~ '''In the ~~following command to read the level of the GPIO port. If~~ Linux system, the ~~level~~ I2C in 40Pin is 0closed by default, and it ~~means that the drop -down mode is set successfully</li></ol>~~needs to be opened manually to use.'''

~~root@orangepi:~/wiringOP# '''gpio read 5'''~~

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

~~~~

~~=== 40pin SPI Test ===~~

~~# From the schematic diagram of the 40PIN interface, the SPI available for Orange Pi 3B is spi3~~

~~[[File:pi3b-img264.png|577x193px]]~~

~~'''In the Linux system, the SPI3 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.'''~~

orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''

'''overlays=~~spi3~~i2c2-m1 i2c3-m0i2c4-~~cs0-spidev~~m0'''|}</ol>

<li>~~First check whether there is a '''spidev3.0''' device node in~~ After starting the Linux system~~. If it exists~~, ~~it means that~~ first confirm the ~~SPI3 has been set~~I2C device node under/dev. ~~You can use it directly~~</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ # '''ls /dev/~~spidev3.0~~i2c-*''' ~~/dev/spidev3.0~~

/dev/i2c-0      '''/dev/i2c-2'''      '''/dev/i2c-3'''      '''/dev/i2c-4'''      /dev/i2c-6

|}

</ol>

<li>~~Do not shorten~~ Then connect a I2C device on the ~~two pins~~ I2C pin of the ~~SPI3 MOSI and MISO, and run the output result~~ 40PIN connector. Here is an example of the ~~spidev_test as shown below~~DS1307 RTC module. ~~You can see that the data of TX and RX is inconsistent~~</li~~></ol~~>

~~orangepi@orangepi:~$ '''sudo spidev_test -v -D /dev/spidev3.0'''~~ ~~spi mode: 0x0~~ ~~bits per word: 8~~ ~~max speed: 500000 Hz (500 KHz)~~ TX {| ~~FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.~~ ~~RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF | ............................….~~ ~~<ol start~~class="~~4" style="list-style-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> ~~[[File:pi3b-img265.png|577x83px]]~~ ~~orangepi@orangepi:~$ '''sudo spidev_test -v -D /dev/spidev3.0'''~~ ~~spi mode: 0x0~~ ~~bits per word: 8~~ ~~max speed: 500000 Hz (500 KHz)~~ ~~TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.~~ ~~RX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.~~ ~~=== 40pin I2C Test ===~~ ~~# From the table below, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total of three groups of I2C bus.~~ ~~[[File:pi3b-img266.png|576x160px]]~~ ~~'''It can be seen from the above table that i2c4_m0 and spi3_m0 are pins. The two cannot be opened at the same time. i2c3_m0 and uart3_m0 are also reused. The two cannot be opened at the same time'''~~ ~~'''In the Linux system, the i2c in 40Pin is closed by default, and it needs to be opened manually to use.'''~~ '''Add the configuration of the red font part below to the /boot/orangepiEnv.txt, and then restart the Linux system to open the i2c2, i2c3, and i2c4 at the same time. If you only need to open one, then fill in one.''' ~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''~~ ~~'''overlays=i2c2-m1 i2c3-m0 i2c4-m0'''~~ ~~<ol start="2~~wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>After starting the Linux system, first confirm that the i2c device node exists under/dev</li></ol>~~ ~~orangepi@orangepi:~# '''ls /dev/i2c~~text-*''' ~~/dev/i2c-0 '''/dev/i2c-2''' '''/dev/i2c-3''' '''/dev/i2c-4''' /dev/i2c-6~~ ~~<ol start="3" style="list-style-type~~align: ~~decimal~~center;">~~<li>Then connect a i2c device on the i2c pin of the 40Pin connector</li></ol>~~ ~~{| class="wikitable~~"

|-

|

|}

[[File:pi3b-img273.png]]

</ol>

<li>Then use the '''i2cdetect -y''' command if If the address of the connected I2C device can be detected, it means that the I2C can be used normally</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ sudo i2cdetect -y 2 #i2c2 command

orangepi@orangepi:~$ sudo i2cdetect -y 4 #i2c4 command

|}

[[File:pi3b-~~img267~~img274.png~~|476x179px|UN}~]Q}T_70O%Z%RNO8R@YE~~]]

</div></ol><~~span id~~ol start="~~pin~~5" style="list-~~uart~~style-~~test~~type: decimal;"><li>You can then run the time of the ds '''ds1307.py''' test program in '''examples''' to read the RTC time</~~span~~li>{| class="wikitable" style=~~= 40pin UART test ===~~"width:800px;" |-| root@orangepi:~/wiringOP-Python# '''cd examples''' root@orangepi:~/wiringOP-Python/examples# '''python3 ds1307.py --device \''' '''"/dev/i2c-4"''' Thu 2023-01-05 14:57:55 Thu 2023-01-05 14:57:56 Thu 2023-01-05 14:57:57

^C exit|}</ol> === 40pin's UART test === # As can be seen from the table below, the ~~uart~~ UART available for Orange Pi 3B is ~~uart3, uart7~~UART3, UART7 and ~~uart9~~UART9. There are three sets of ~~uart~~ UART bus

::[[File:pi3b-img268.png~~|575x160px~~]]

::{| class="wikitable" style="width:800px;background-color:#ffffdc;" |-| <big>'''As can be seen from the above table, ~~i2c3_m0~~ I2C3_M0 and ~~uart3_m0~~ UART3_M0 are reused by pins, and the two cannot be opened at the same time'''</big>|}

::{| class="wikitable" style="width:800px;background-color:#ffffdc;" |-| <big>'''In the Linux system, the ~~uart~~ 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~~UART3, ~~uart7~~UART7, and ~~uart9~~ 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=uart3-m0 uart7-m2 uart9-m2'''|}

<li>After entering the Linux system, first confirm whether there is a device node corresponding to ~~uart~~ UART under/dev</li~~></ol~~>

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

|-

|

orangepi@orangepi:~# '''ls /dev/ttyS*'''

/dev/ttyS1      '''/dev~~'''~~/~~'''~~ttyS3      /dev/ttyS7      /dev/ttyS9'''|}</ol>

<li>Then start testing the ~~uart~~ UART interface, and first use the rx RX and tx TX of the ~~uart~~ UART interface to be tested by DuPont</li~~></ol~~>

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

|-

|

|uart9

|-

| Tx ~~pin~~Pin

|Corresponding to the 28 pin

|Corresponding to the 16 pin

|Corresponding to the 7 pin

|}

~~[[File:pi3b-img269.png|545x134px]]~~</ol>

<li>Use the '''~~gpio serial~~serialTest.py''' ~~command~~ program in Examples to test the loop function of the serial port ~~as shown below~~. If you can see the ~~following~~ printingbelow, it means that the serial communication is normal

<li>Test UART3</li>~~</ol>~~<{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~li><~~wiringOP-Python/~~ol>~~examples# '''python3 serialTest.py --device \'''

~~orangepi@orangepi:~$~~ '''~~sudo gpio serial~~ "/dev/ttyS3"'''

~~[sudo] password for orangepi: #Enter the password here.~~

Out: 0: -> 0

Out: 3: -> 3

Out: 4: ~~-> 4~~ ~~Out: 5: -> 5~~^C

exit

|}

</ol>

<li>Test UART7</li><{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~ol>~~wiringOP-Python/examples# '''python3 serialTest.py --device \'''

~~orangepi@orangepi:~$~~ '''~~sudo gpio serial~~ "/dev/ttyS7"'''

~~[sudo] password for orangepi: #Enter the password here.~~

Out: 0: -> 0

Out: 3: -> 3

Out: 4: ~~-> 4~~ ~~Out: 5: -> 5~~^C

exit

|}

</ol>

<li>Test UART9</li><{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~ol>~~wiringOP-Python/examples# '''python3 serialTest.py --device \'''

~~orangepi@orangepi:~$~~ '''~~sudo gpio serial~~ "/dev/ttyS9"'''

~~[sudo] password for orangepi: #Enter the password here.~~

Out: 0: -> 0

Out: 3: -> 3

Out: 4: ~~-> 4~~^C

~~Out: 5:~~ exit|}</ol></li></ol> 5^Cwatch-the-door-dog-test">

~~~~=== ~~PWM~~ Hardware watch the door dog test ~~method =~~==

~~# From~~ The WatchDog_test program is pre -installed in the ~~table below~~Linux system released by Orange PI, ~~the pwm11 available for Orange Pi 3B~~which can be tested directly.

~~[[File~~The method of running the WatchDog_test program is shown below:~~pi3b-img270.png|575x160px]]~~

~~'''In~~ <ol style="list-style-type: lower-alpha;"><li>The second parameter 10 indicates the counting time of the door. If there is no dog feeding in this time, the ~~Linux~~ system, will restart.</li><li>We can feed the dog by pressing any keys on the keyboard (except ESC). After the ~~pwm in 40pin~~ dog is ~~closed by default~~fed, ~~and it needs~~ the program will print a line of Keep Alive to ~~be opened manually to use..'''~~indicate that the dog is successful</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~Add the configuration of the red font part below to the /boot/orangepiEnv.txt, and then restart the Linux system to open the pwm11.~~sudo watchdog_test 10'''

~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''~~open success

~~'''overlays=pwm11~~options is 33152,identity is sunxi-~~m1'''~~wdt

~~<ol start="2" style="list-style-type~~put_usr return,if 0,success: ~~decimal;"><li>After opening a pwm, a pwmchipX (X is a specific number) will be available in'''/sys/class/pwm/'''</li></ol>~~0

~~orangepi@orangepi~~The old reset time is:~~~$ '''ls /sys/class/pwm/'''~~16

~~pwmchip0 pwmchip1~~return ENOTTY,if -1,success:0

~~<ol start="3" style="list-style-type: decimal;"><li>Which pwmchip corresponds to pwm11 above? Let's first check out the output of '''ls /sys/class/pwm/~~ return ENOTTY,if -~~l''' command~~1, ~~as shown below~~success: ~~</li>~~<li>The base address of the pwm11 register is Fe6F0030. Then see the output of '''ls /sys/class/pwm/ -l''' command, you can see that the fe6f0030.pwm is connected to the pwmchip1, so the PWM11 corresponding pwmchip is pwmchip1</li></ol>0

~~<div class="figure">~~put_user return,if 0,success:0

~~[[File~~put_usr return,if 0,success:~~pi3b-img271.png|576x46px|RCUS$_~VYM{4ZS]_L}DNZQR]]~~0

~~</div><ol start="5" style="list-style-type: decimal;"><li>Then use the following command to allow pwm11 to output a 50Hz square wave (please switch to the root user first, and then execute the following command)</li></ol>~~keep alive

~~root@orangepi:~# '''echo 0 > /sys/class/pwm/pwmchip1/export'''~~keep alive

~~root@orangepi:~# '''echo 20000000 >~~ keep alive|}</~~sys~~ol></~~class/pwm/pwmchip1/pwm0/period'''~~span>

~~root@orangepi:~# '''echo 1000000 > /sys/class/pwm/pwmchip1/pwm0/duty_cycle'''~~== Check the serial number of the RK3566 chip ==

~~root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip1/pwm0/enable'''~~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.

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img272~~| orangepi@orangepi:~$ '''cat_serial.~~png|575x346px]]~~sh'''

~~~~Serial : '''8fa18eaf489041f0'''~~== How to install and use Wiringop-Python ==~~|}

~~'''Wiringop~~<span id="the-method-~~Python is the library~~ of -downloading-and-installing-the ~~Python language~~ -balenaetcher-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.'''~~-arm64">

~~'''Please note that all~~ == The method of downloading and installing the ~~following command below is operated under the root user.'''~~balenaEtcher version of arm64 ==

<~~span id~~ol style="~~wiringop~~list-~~python~~style-~~installation~~type: decimal;"><li>The download address of Balenaetcher ARM64 version is: <ol style="list-style-type: lower-~~method~~alpha;"><li>The download address of the Deb installation package is shown below, and it needs to be installed to use</~~span~~li>{| class="wikitable" style="width:800px;" |-| '''https://github.com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balena-etcher-electron_1.7.9+5945ab1f_arm64.deb'''|}</ol><ol start="2" style= ~~Wiringop~~"list-style-type: lower-~~Python installation method =~~alpha;"><li>The download address of the Appimage version that does not need to be installed is shown below: </li>{| class="wikitable" style="width:800px;" |-| '''https://github.com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balenaEtcher-1.7.9+5945ab1f-arm64.AppImage'''|}

~~# First install the dependency package~~<div class="figure">

~~root@orangepi~~[[File:~~~# '''sudo apt~~pi3b-~~get update'''~~ ~~root@orangepi:~# '''sudo apt-get -y install git swig python3-dev python3-setuptools'''~~img275.png]]

</div></ol>

</li></ol>

<li>~~Then~~ How to install and use the ~~following command to download the source code~~ deb version of ~~wiringOP~~Balenaetcher: <ol style="list-~~Python~~style-type: lower-alpha;"></li>deb version of Balenaetcher installation commands as shown below: </olli>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y \'''

'''~~Note that the following git clone~~--~~recursivee command will automatically download the source code of Wiringop, because Wiringop~~fix-broken ./balena-etcher-~~Python depends on Wiringop~~electron_1.7. ~~Please make sure that the download process does not report an error due to network problems~~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>

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

~~root@orangepi~~[[File:~~~# '''git clone~~ pi3b-~~-recursive https://github~~img89.~~com/orangepi-xunlong/wiringOP-Python -b next'''~~png]]

~~root@orangepi~~</div></ol><ol start="3" style="list-style-type:~~~# '''cd wiringOP~~lower-~~Python'''~~alpha;"><li>The interface after Balenaetcher is opened is shown below: </li>

~~root@orangepi~~<div class="figure"> [[File:~~~/wiringOP~~pi3b-~~Python# '''git submodule update --init --remote'''~~img276.png]]

</div></ol>

</li></ol>

<li>~~Then~~ How to use the ~~following command~~ AppImage version of balenaEtcher: <ol style="list-style-type: lower-alpha;"><li>First add permissions to ~~compile wiringOP~~Balenaetcher</li>{| class="wikitable" style="width:800px;" |-~~Python and install it into the Linux system of the development board~~| orangepi@orangepi:~/Desktop$ '''chmod +x balenaEtcher-1.7.9+5945ab1f-arm64.AppImage'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then select the AppImage version balenaEtcher right -click the mouse, and then click Execute to open balenaEtcher</olli>

~~root@orangepi~~[[File:~~~# '''cd wiringOP~~pi3b-~~Python'''~~img277.png]]</ol></li></ol>

~~root@orangepi:~/wiringOP~~== The installation method of the Bt-~~Python# '''python3 generate-bindings.py > bindings.i'''~~Panel Linux panel ==

~~root@orangepi~~{| class="wikitable" style="background-color:#ffffdc;width:~~~/wiringOP~~800px;" |-~~Python#~~ | <big>'''~~sudo python3 setup~~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.~~py install~~html official website of the Bt-Panel])'''</big>|}

~~<ol start="4" style="list-style-type: decimal;"><li>Then enter~~ # First of all, the ~~following command. If there is a help information output, it means that Wiringop-Python is successfully installed. Press~~ size of the '''q/tmp''' ~~key~~ space is needed. After setting, you need to ~~exit~~ '''restart the ~~interface~~ Linux system of the ~~help information~~development board</~~li></ol~~span>''', and the command is shown below:

~~root~~::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~~~/wiringOP-Python#~~ $ '''~~python3~~ sudo sed -c i 's/nosuid/&~~quot;import wiringpi; help(wiringpi)&quot~~amp;,size=2G/' /etc/fstab'''

~~Help on module wiringpi~~orangepi@orangepi:~$ '''sudo reboot'''|}

~~NAME~~<ol start="2" style="list-style-type: decimal;"><li>After restarting, you can see that the size of the'''/tmp''' space has become 2G.</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''df -h | grep "/tmp"'''

~~wiringpi~~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;" |-| 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;" |-| +----------------------------------------------------------------------

~~DESCRIPTION~~| Bt-WebPanel FOR CentOS/Ubuntu/Debian

~~# This file was automatically generated by SWIG (http://www.swig.org).~~+----------------------------------------------------------------------

#+----------------------------------------------------------------------

~~# Do not make changes to this file unless you know what you are doing--modify~~| The WebPanel URL will be http://SERVER_IP:8888 when installed.

~~# the SWIG interface file instead.~~+----------------------------------------------------------------------

Do you want to install Bt-Panel to the /www directory now?(y/n): '''y'''

|}

</ol>

<li>~~Test whether~~ Then you have to wait patiently. When you see the ~~Wiringop-Python is installed successfully under~~ printing information below the ~~Python command line is shown below: <ol style="list-style-type: lower-alpha;"><li>First use~~ terminal output, it means that the ~~Python3 command~~ pagoda has been installed. The entire installation process takes about 34 minutes. There may be some differences according to ~~enter~~ the ~~command line mode of Python3~~difference in network speed</li~~></ol></li></ol~~>

~~root@orangepi~~[[File:~# pi3b-img278.png|800px]]</ol><ol start="6" style="list-style-type: decimal;"><li>At this time, enter the '''panel address''' displayed above in the browser to open the login interface of the pagoda Linux panel, and then enter the '''username'''~~python3~~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" User Agreement ", and then click" Enter the panel " You can enter the Bt-Panel</li>

[[File:pi3b-img280.png|1200px]]</ol><ol start="28" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then import~~ After entering the ~~Python module~~ Bt-Panel, you will first prompt that you need to bind the account of ~~WiringPi~~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.</li~~></ol~~>

~~&gt~~[[File:pi3b-img281.png|1200px]]</ol><ol start="9" style="list-style-type: decimal;~~>> '''import wiringpi;'''~~"><li>The final display interface is shown in the figure below. You can intuitively see some status information of the development board Linux system, such as load state, CPU usage, memory usage and storage space usage</li>

[[File:pi3b-img282.png|1200px]]</ol><ol start="310" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Enter~~ More functions of the ~~following command~~ Bt-Panel can refer to ~~view~~ the ~~help~~ following information ~~of Wiringop-Python, and press the '''q''' key~~ to ~~exit the interface of the help information~~explore by yourself</li~~></ol~~>

~~>>&gt~~{| class="wikitable" style="width:800px; " |-| Manual: [http://docs.bt.cn '''~~help(wiringpi)~~http://docs.bt.cn''']

~~Help on module wiringpi~~Forum address:[https://www.bt.cn/bbs '''https://www.bt.cn/bbs''']

~~NAME~~GitHub Link: '''https://github.com/aaPanel/BaoTa'''|}</ol>

~~wiringpi~~== Set the Chinese environment and install Chinese input method ==

~~DESCRIPTION~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that before installing the Chinese input method, please make sure that the Linux system used in the development board is the desktop version system.'''</big>|}

~~# This file was automatically generated by SWIG (http:~~</~~/www.swig.org).~~span>=== Debian system installation method ===

~~# Version 4.0.2~~<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="2" style="list-style-type: lower-alpha;"><li>Then select '''zh_CN.UTF-8 UTF-8''' in the pop-up interface (to move up and down through the upper and lower direction buttons on the keyboard, select it through the space key, and finally move the cursor to '''<OK>''' through the TAB key, then press the ENTER key )</li>

~~# Do not make changes to this file unless you know what you are doing~~[[File:pi3b-img283.png|1200px]]</ol><ol start="3" style="list-~~modify~~style-type: lower-alpha;"><li>Then set the default '''locale''' as '''zh_CN.UTF-8'''</li>

# [[File:pi3b-img284.png|1200px]]</ol><ol start="4" style="list-style-type: lower-alpha;"><li>After exiting the ~~SWIG~~ interface ~~file instead~~, the '''locale''' settings will be started.The output displayed by the command line is shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''

~~CLASSES~~Generating locales (this might take a while)...

~~builtins~~:en_US.~~object~~UTF-8... done

~~GPIO~~:zh_CN.UTF-8... done

~~I2C~~Generation complete.|}</ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>Then open '''Input Method'''</li>

~~Serial~~[[File:pi3b-img285.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then select '''OK'''</li>

~~nes~~[[File:pi3b-img286.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select '''Yes'''</li>

~~class GPIO(builtins~~[[File:pi3b-img287.~~object)~~png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then select '''fcitx'''</li>

~~| GPIO(pinmode~~[[File:pi3b-img288.png]]</ol><ol start=0)"6" style="list-style-type: decimal;"><li>Then select '''OK'''</li>

|[[File:pi3b-img289.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>'''Then restart the Linux system to make the configuration effective'''</li><li>Then open '''Fcitx configuration'''</li>

~~>>&gt~~[[File:pi3b-img290.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then click the + of the position shown in the figure below</li>

[[File:pi3b-img291.png]]</ol><~~span id~~ol start="~~pin~~10" style="list-~~gpio~~style-~~port-test-1~~type: decimal;"><~~/span~~li>~~=== 40pin GPIO port test ===~~ Then search '''Google Pinyin'''Wiringop-Python is the same as Wiringop. You can also determine which GPIO pink can be determined by specifying the WPI number. Because there is no command to check the WPI number in Wiringop-Python, you can only check the board WPI number and ~~physical physical physics through the GPIO command in Wiringop. The corresponding relationship of the pin.~~click '''OK'''</li>

[[File:pi3b-~~img258~~img292.png~~|575x355px|66AC(IBG%N8L@Y7(1BZPS`N~~]]

</div></ol>~~# Below the No. 7 pin — corresponding to GPIO4_a4~~ <ol start="11" style="list-~~corresponding WPI serial number 2~~ style-type: decimal;"><li>Then put '''Google Pinyin''' to ~~demonstrate how to set the height of~~ the ~~GPIO port~~front</li>

[[File:pi3b-~~img259~~img293.png~~|576x120px~~]]

~~<ol start="2" style="list~~[[File:pi3b-~~style-type: decimal;">~~img294.png]]~~<li>The steps of the command test are shown below directly:~~ </pol><ol start="12" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~First set the GPIO port to the output mode. The first parameter of~~ Then open the '''~~pinMode~~Geany''' ~~function is the serial number of the wpi corresponding~~ editor to test the ~~pin, and the second parameter is the GPIO mode</li></ol>~~Chinese input method</li~~></ol~~>

~~root@orangepi~~[[File:~pi3b-img295.png]]</~~wiringOP~~ol><ol start="13" style="list-~~Python# '''python3~~ style-~~c &quot~~type: decimal;~~import wiringpi; \'''~~"><li>The Chinese input method test is shown below</li>

[[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''~~from wiringpi import GPIO; wiringpi~~' shortcut</li><li>If the entire system is required as Chinese, the variables in '''/etc/default/locale''' can be set to '''zh_CN.~~wiringPiSetup()~~ UTF-8'''</li>{| class="wikitable" style="width:800px; \" |-| orangepi@orangepi:~$ '''sudo vim /etc/default/locale'''

~~'''wiringpi.pinMode(2, GPIO.OUTPUT) ; "'''~~# File generated by update-locale

LC_MESSAGES='''<~~ol start="2"~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<li>Then set the GPIO port output low level~~zh_CN. ~~After setting, you can use the voltage of the voltage of the universal meter to measure the pins. If it is 0V, it means that the low~~ UTF-~~power flat is successful</li>~~8</olspan>'''

~~root@orangepi:~/wiringOP-Python#~~ LANG='''~~python3~~ zh_CN.UTF-~~c "import wiringpi; \~~8'''

LANGUAGE='''~~from wiringpi import GPIO; wiringpi~~zh_CN.~~wiringPiSetup()~~ UTF-8'''|}</ol><ol start="16" style="list-style-type: decimal;\"><li>Then '''restart the system'''to see the system displayed as Chinese</li>

~~'''wiringpi~~[[File:pi3b-img297.~~digitalWrite(2, GPIO~~png]]</ol>

~~<ol start~~=~~"3" style~~=~~"list-style-type: lower-alpha;"><li>Then set the GPIO port output high level. After setting, you can use the value of the voltage~~ = The installation method of ~~the pins with a multimeter~~Ubuntu 20. ~~If it is 3.3V, it means that the high -power flat is successful.</li></ol>~~04 system ===

~~root@orangepi:~/wiringOP-Python~~# First open '''~~python3 -c "import wiringpi; \~~Language Support'''

~~'''from wiringpi import GPIO; wiringpi~~::[[File:pi3b-img298.~~wiringPiSetup() ;\'''~~png]]

<ol start="2" style="list-style-type: decimal;"><li>Then find '''~~wiringpi.digitalWrite~~Chinese (~~2, GPIO.HIGH~~China)~~"~~'''option</li>

[[File:pi3b-img299.png]]

</ol>

<li>~~~~Then use the left mouse button to select '''Chinese (China)''' and hold it down, and then drag it up to the beginning. The ~~steps of testing in the command line of Python3 are~~ display is shown below: ~~<ol style="list-style-type: lower-alpha;"><li>First use the Python3 command to enter the command line mode of Python3</li></ol>~~</li~~></ol~~>

~~root@orangepi~~[[File:~~~# '''python3'''~~pi3b-img300.png]]

{| 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="24" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~import~~ select the ~~Python module of WiringPi~~'''Apply System-Wide''' to apply the Chinese settings to the entire system</li~~></ol~~>

~~>>&gt~~[[File:pi3b-img301.png]]</ol><ol start="5" style="list-style-type: decimal; "><li>Then set the '''Keyboard input method system''' to '''~~import wiringpi~~fcitx'''</li>

~~>>&gt~~[[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 '''~~from wiringpi import GPIO~~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>

[[File:pi3b-img303.png]]</ol><ol start="38" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~set~~ you can see that the ~~GPIO port~~ desktop is displayed 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.~~Chinese</li~~></ol~~>

~~>>&gt~~[[File:pi3b-img304.png]]</ol><ol start="9" style="list-style-type: decimal; "><li>Then we can open the '''~~wiringpi.wiringPiSetup()~~Geany'''to test Chinese input method , and the way to open is shown in the figure below</li>

0[[File:pi3b-img305.png]]</ol><ol start="10" style="list-style-type: decimal;"><li>After opening '''Geany''', the default is an English input method. We can switch into Chinese input method through the '''Ctrl+Space''' shortcut keys, and then we can enter Chinese</li>

~~>>> '''wiringpi~~[[File:pi3b-img306.~~pinMode(2, GPIO~~png]]</ol>

~~<ol start~~=~~"4" style~~=~~"list-style-type: lower-alpha;"><li>Then set the GPIO port output low level. After setting, you can use the value of the voltage~~ = The installation method of ~~the pins with a multimeter~~ubuntu 22. ~~If it is 0V, it means that the low -power flat is set.</li></ol>~~04 system ===

~~>>>~~ # First open '''~~wiringpi.digitalWrite(2, GPIO.LOW)~~Language Support'''

~~<ol start="5" style="list-style-type~~: ~~lower~~:[[File:pi3b-~~alpha;"><li>Then set the GPIO port output high level~~img298. ~~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>~~png]]

~~>>&gt~~<ol start="2" style="list-style-type: decimal; "><li>Then find '''~~wiringpi.digitalWrite~~Chinese (~~2, GPIO.HIGH~~China)'''option</li>

[[File:pi3b-img307.png]]</ol><ol start="43" style="list-style-type: decimal;"><li>~~Wiringop-Python Sets GPIO high and low levels in~~ Then use the ~~Python code. For reference~~ left mouse button to ~~the~~ select '''~~blink.py~~Chinese (China)''' ~~test program in Examples~~and hold it down, and then drag it up to the ~~voltage of the '''blink~~beginning.~~py''' test program will set up the voltage of all GPIO ports~~ The display after dragging is shown in the ~~development board 40 PIN~~figure below: </li~~></ol~~>

~~root@orangepi~~[[File:~~~/wiringOP~~pi3b-~~Python# '''cd examples'''~~img308.png]]

~~root@orangepi~~{| class="wikitable" style="background-color:~#ffffdc;width:800px;" |-| <big>'''Note that this step is not easy to drag, please try more patiently.'''</~~wiringOP~~big>|}</ol><ol start="4" style="list-~~Python/examples#~~ style-type: decimal;"><li>Then select the '''~~ls blink.py~~Apply System-Wide'''to apply the Chinese settings to the entire system</li>

[[File:pi3b-img309.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>'''Then restart the Linux system to make the configuration effective'''</li><li>After re -entering the system, please '''~~blink.py~~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>

~~root@orangepi~~[[File:~pi3b-img303.png]]</~~wiringOP~~ol><ol start="7" style="list-~~Python~~style-type: decimal;"><li>Then you can see that the desktop is displayed as Chinese</~~examples'''# python3 blink.py'''~~li>

[[File:pi3b-img304.png]]</ol><~~span id~~ol start="~~pin-spi~~8" style="list-~~test~~style-1type: decimal;"><li>Then open the Fcitx5 configuration program</~~span~~li>~~=== 40pin SPI test ===~~

~~# From the schematic diagram of the 40pin interface, the SPI available for Orange Pi 3B is spi3~~[[File:pi3b-img310.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then choose to use Pinyin input method</li>

~~[[File:pi3b-img264.png|577x193px]]~~<div class="figure">

~~'''In the Linux system, the spi3 in 40pin is closed by default, and it needs to be opened manually to use~~[[File:pi3b-img311.~~'''~~png]]

~~'''Add~~ </div></ol><ol start="10" style="list-style-type: decimal;"><li>The interface after the ~~configuration of the red font part~~ selection is shown below ~~to the /boot/orangepiEnv.txt~~, ~~and~~ then ~~restart the Linux system to open the spi4.'''~~click OK</li>

~~orangepi@orangepi~~[[File:~$ pi3b-img312.png]]</ol><ol start="11" style="list-style-type: decimal;"><li>Then we can open the '''~~sudo vim /boot/orangepiEnv.txt~~Geany'''to test Chinese input method, and the way to open is shown in the figure below</li>

[[File:pi3b-img305.png]]</ol><ol start="12" style="list-style-type: decimal;"><li>After opening '''Geany''~~overlays=spi3-m0-cs0-spidev~~', 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>

[[File:pi3b-img313.png]]</ol ~~start~~><li>First check whether there is a '''spidev3.0''' device node~~ in -to-the ~~Linux~~ -linux-system~~. If it exists, it means that the SPI3 has been set and can be used directly</li-desktop-method"></olspan>

~~orangepi@orangepi:~$ '''ls /dev/spidev3.0'''~~== How to remotely log in to the Linux system desktop method ==

{| 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.'''</~~dev/spidev3.0~~big>|}

<~~ol start~~span id="~~3" style="list-style-type: decimal;"><li>You can then~~ use ~~the spi back function under the '''spidev_test.py''' program in Examples. The '''spidev_test.py''' program needs to specify the following two parameters: <ol style="list~~-~~style~~nomachine-~~type: lower~~remote-~~alpha;~~login">~~<li>'''--channel''': Specify the channel number of SPI~~</~~p></li~~span>~~<li>'''--port''': Specify the port number of SPI</li></ol></li>~~<li>Do not pick up the two pins of the SPI3 MOSI and MISO in short, and run the output result of the spidev_test.py as shown below. You can see that the data of TX and RX are inconsistent</li></ol>=== Use nomachine remote login ===

~~root@orangepi~~{| class="wikitable" style="background-color:~~~/wiringOP~~#ffffdc;width:800px;" |-~~Python#~~ | <big>'''~~cd examples~~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: '''

~~root@orangepi~~'''https:~/~~wiringOP~~/knowledgebase.nomachine.com/DT10R00166'''</big>|}{| class="wikitable" style="background-~~Python~~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.'''</~~examples~~big>|}{| class="wikitable" style="background-color:# ffffdc;width:800px;" |-| <big>'''~~python3 spidev_test~~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.~~py \~~'''</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="list-style-~~channel 3~~ type: lower-alpha;"><li>Since RK3566 is a SOC of the ARMV8 architecture, the system we use is Ubuntu or Debian, so you need to download '''NoMachine for ARM ARMv8 DEB''' installation package here. The download link is shown below: </li>{| class="wikitable" style="background-~~port 0~~color:#ffffdc;width:800px;" |-| <big>'''Note that this download link may change, please recognize the DEB package of the ARMV8/ARM64 version.'''</big>|}{| class="wikitable" style="width:800px;" |-| ~~spi mode~~[https://www.nomachine.com/download/download&id=112&s=ARM '''https: ~~0x0~~//downloads.nomachine.com/download/?id=118&distro=ARM''']|}

~~max speed~~[[File: ~~500000 Hz (500 KHz)~~pi3b-img314.png]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>In addition, you can also download the installation package to '''NoMachine''' in the '''official tools'''.</li>

~~Opening device /dev/spidev3~~[[File:pi3b-img315.0png]]

~~TX | FF FF FF FF FF FF~~ First enter the '''~~40 00 00 00 00 95~~remote login software-Nomachine''' ~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…|~~folder

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

~~<ol start="5" style="list-style-type: decimal;"><li>~~Then ~~use~~ download the ~~TXD (No. 19 pins in the 40Pin interface) and RXD (No. 21 pins in the 40pin interface)~~ ARM64 version of the ~~DuPont line short connection SPI3. Like sending and receiving data, it means that the SPI3 loop test is normal</li></ol>~~DEB installation package

~~root~~[[File:pi3b-img317.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then upload the downloaded '''nomachine_x.x.x_x_arm64.deb''' to the Linux system of the development board.</li><li>Then use the following command to install '''NoMachine''' in the Linux system of the development board</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg -i nomachine_x.x.x_x_arm64_arm64.deb'''|}</ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>Then download the nomachine software Windows version of the installation package, the download address is shown below</~~wiringOP~~li>{| class="wikitable" style="background-~~Python~~color:# ffffdc;width:800px;" |-| <big>'''Note that this download link may change.'''</big>|}{| class="wikitable" style="width:800px;" |-| '''~~cd examples~~https://downloads.nomachine.com/download/?id=9'''|}

~~root@orangepi~~[[File:~pi3b-img318.png]]</~~wiringOP~~ol><ol start="3" style="list-style-~~Python~~type: decimal;"><li>Then install nomachine in Windows. '''Please restart the computer after installation'''</~~examples#~~ p></li><li>Then open '''~~python3 spidev_test.py \~~NoMachine'''in Window</li>

~~'''~~[[File:pi3b-img319.png]]</ol><ol start="5" style="list-~~channel 3~~ style-~~-port 0'''~~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>

~~spi mode~~[[File: ~~0x0~~pi3b-img320.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then click '''OK'''</li>

~~max speed~~[[File: ~~500000 Hz (500 KHz)~~pi3b-img321.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Then enter the username and password of the Linux system in the corresponding position in the figure below, and then click '''OK''' to start logging in</li>

~~Opening device /dev/spidev3.0~~<div class="figure">

~~TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |~~[[File:pi3b-img322.~~.....@.......…|~~png]]

~~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 |~~</div></ol><ol start="8" style="list-style-type: decimal;"><li>Then click OK in the next interface</li><li>Finally, you can see the desktop of the development board Linux system[[File:pi3b-img323.~~.....@.......…|~~png]]</li></ol>

~~=== 40pin I2C test ===~~

~~<ol start~~=~~"5" 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</li></ol>~~= Use VNC remote login ===

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

'''~~It can be seen from the above table that I2C4_M0 and SPI3_M0 are pins~~Ubuntu 20. ~~The two cannot be opened at the same time~~04 tests many problems with VNC, please do not use this method. ~~I2C3_M0 and UART3_M0 are also reused. The two cannot be opened at the same time~~'''</big>|}

# First run the '''set_vnc.sh''~~In the Linux system, the I2C in 40Pin is closed by default~~' script settings, and ~~it needs~~ '''remember to ~~be opened manually to use.~~add Sudo permissions'''

::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''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 onesudo set_vnc.sh'''

~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv~~You will require a password to access your desktops.~~txt'''~~

~~'''overlays=i2c2-m1 i2c3-m0 i2c4-m0'''~~

Password:        '''<~~ol start="6"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>After starting~~ #Set the ~~Linux system~~VNC password here, ~~first confirm the I2C device node under/dev.</li>~~8 -bit characters</olspan>'''

~~orangepi@orangepi~~Verify:~#        '''ls #Set the VNC password here, 8 -bit characters</dev/i2c-*span>'''

~~/dev/i2c-0 '''/dev/i2c~~Would you like to enter a view-~~2''' '''/dev~~only password (y/~~i2c-3'''~~ n)? '''n</~~dev/i2c-4~~span>''' ~~/dev/i2c-6~~

~~<ol start="7" style="list-style-type~~xauth: ~~decimal;"><li>Then connect a I2C device on the I2C pin of the 40PIN connector. Here is an example of the DS1307 RTC module.<~~file /~~li><~~root/~~ol>~~.Xauthority does not exist

~~{| class="wikitable"~~

|-

|

~~|i2c2-m1~~

~~|i2c3-m0~~

~~|i2c4-m0~~

|-

~~| Sda Pin~~

~~|Corresponding to No. 3 pin~~

~~|Corresponding to No. 27 pin~~

~~|Corresponding to No. 19 pin~~

|-

~~| Sck Pin~~

~~|Corresponding to No. 5 pin~~

~~|Corresponding to No. 28 pin~~

~~|Corresponding to No. 23 pin~~

|-

~~| Vcc Pin~~

~~|Corresponding to No. 1 pin~~

|-

~~| Gnd Pin~~

~~|Corresponding to No. 6 pin~~

|}

~~[[File~~New 'X' desktop is orangepi3b:~~pi3b-img273.png|180x153px]]~~1

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

~~<li>Then use the '''i2cdetect -y''' command If the address of the connected I2C device can be detected, it means that the I2C can be used normally</li></ol>~~

~~orangepi@orangepi:~$ sudo i2cdetect -y 2 #i2c2 command~~Creating default startup script /root/.vnc/xstartup

~~orangepi@orangepi:~$ sudo i2cdetect -y 3 #i2c3 command~~Starting applications specified in /root/.vnc/xstartup

~~orangepi@orangepi~~Log file is /root/.vnc/orangepi3b:~~~$ sudo i2cdetect -y 4 #i2c4 command~~1.log

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

~~[[File:pi3b-img274.png|464x174px|V@(61L~0})Q`8VLBCAYEP[2]]~~Killing Xtightvnc process ID 3047

~~</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'~~New 'X'desktop is orangepi3b:1

Starting applications specified in /root~~@orangepi:~~~/~~wiringOP-Python~~.vnc/~~examples# '''python3 ds1307.py --device \'''~~xstartup

~~'''"~~Log file is /~~dev~~root/~~i2c-4"'''~~.vnc/orangepi3b:1.log|}

~~Thu 2023~~<ol start="2" style="list-01style-~~05 14~~type:57decimal;"><li>The steps of using MobaxTerm software to connect the development board Linux system desktop are shown below:55<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>

~~Thu 2023-01-05 14:57:56~~<div class="figure">

~~Thu 2023-01~~[[File:pi3b-~~05 14:57:57~~img324.png]]

^C</div></ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then enter the password of the previously set VNC</li>

~~exit~~[[File:pi3b-img325.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The interface after the login is shown as shown in the figure below, and then the desktop of the Linux system can be remotely operated[[File:pi3b-img326.png]]</li></ol></li></ol>

~~=== 40pin's UART test ===~~

~~# As can be seen from the table below, the UART available for Orange Pi 3B is UART3, UART7 and UART9. There are three sets of UART bus~~== Some programming language tests supported by Linux system ==

~~[[File:pi3b~~=== Debian Bullseye system ===

~~'''As~~ <ol style="list-style-type: decimal;"><li>Debian Bullseye is equipped with a gcc compilation tool chain by default, which can ~~be seen from~~ directly compile the C language program in the ~~above table, I2C3_M0 and UART3_M0 are reused by pins, and~~ Linux system of the ~~two cannot be opened at~~ development board<ol style="list-style-type: lower-alpha;"><li>The version of the ~~same time~~gcc is shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc --version'''

~~'''In the Linux system, the UART in 40pin is closed by default, and it needs to be opened manually to use~~gcc (Debian 10.~~'''~~2.1-6) 10.2.1 20210110

~~'''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~~Copyright (C) 2020 Free Software Foundation, ~~and UART9 at the same time~~Inc. ~~If you only need to open one, you can fill in one'''~~

~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv~~This is free software; see the source for copying conditions.~~txt'''~~There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Write C language of '''Hello_world.c'''~~overlays~~program</li>{| class="wikitable" style=~~uart3~~"width:800px;" |-~~m0 uart7-m2 uart9-m2~~| orangepi@orangepi:~$ '''vim hello_world.c'''

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

~~<li>After entering the Linux system, first confirm whether there is a device node corresponding to UART under/dev</li></ol>~~

~~orangepi@orangepi:~~~# ~~'''ls~~ include <stdio.h></~~dev/ttyS*'''~~p>

~~/dev/ttyS1 '''/dev'''/'''ttyS3 /dev/ttyS7 /dev/ttyS9'''~~int main(void)

~~<ol start="3" style="list-style-type: decimal;"><li>Then start testing the UART interface, and first use the RX and TX of the UART interface to be tested by DuPont</li></ol>~~{

~~{| class="wikitable"~~|-|~~|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~~|}:printf("Hello World!\n");

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

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

~~root@orangepi~~:~~~/wiringOP-Python/examples# '''python3 serialTest.py --device \'''~~return 0;

}|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then compile and run '''hello_world.c'''~~"~~</~~dev/ttyS3&quot~~li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''

~~Out~~orangepi@orangepi: ~~0: -> 0~~~$ '''./hello_world'''

~~Out~~Hello World!|}</ol></li></ol><ol start="2" style="list-style-type: 1decimal;"><li>Debian BullSeye Default with Python3<ol style="list-style-type: lower-~~&gt~~alpha; 1"><li>The specific version of Python is shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3'''

~~Out~~'''Python 3.9.2''' (default, Feb 28 2021, 17: 203: ~~-> 2~~44)

~~Out: 3: -> 3~~[GCC 10.2.1 20210110] on linux

~~Out: 4:^C~~ ~~exit~~Type "help", "copyright", "credits" or "license" for more information.

>>>

|}

</ol>

<li>~~Test UART7~~'''hello_world.py''' program in Python language</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.py'''

~~root~~print('Hello World!')|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The results of running '''hello_world.py''' are shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~~~/wiringOP-Python/examples#~~ $ '''python3 ~~serialTest~~hello_world.py ~~--device \~~'''

Hello World!|}</ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>Debian Bullseye's compilation tool and operating environment that is not installed in Java by default<ol style="list-style-type: lower-alpha;"><li>You can use the following command to install OpenJDK. The latest version in Debian Bullseye is openjdk-17</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''~~&quot~~|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>After installation, you can check the version of Java</~~dev~~li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''java --version'''|}</~~ttyS7&quot~~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'''

~~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="34" style="list-style-type: lower-alpha;"><li>~~Test UART9~~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!|}</ol></~~dev~~li></~~ttyS9"'''~~ol> ~~Out: 0:~~ 0system">

~~Out: 1: -> 1~~=== Ubuntu Focal system ===

~~Out~~<ol style="list-style-type: 2decimal;"><li>Ubuntu Focal has the GCC compilation tool chain by default, which can compile the C language program directly in the Linux system of the development board.<ol style="list-style-type: lower-~~&gt~~alpha; 2"><li>The version of the gcc is shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc --version'''

~~Out: 3:~~ gcc (Ubuntu 9.4.0-~~> 3~~1ubuntu1~20.04.1) 9.4.0

~~exit~~This is free software; see the source for copying conditions. There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}<~~span id~~/ol><ol start="~~hardware-watch-the~~2" style="list-~~door~~style-~~dog~~type: lower-~~test~~alpha;"><li>'''hello_world.c''' program to write C language</~~span~~li> ~~== Hardware watch the door dog test~~ {| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.c'''

~~The WatchDog_test program is pre -installed in the Linux system released by Orange PI, which can be tested directly~~#include <stdio.h>

~~The method of running the WatchDog_test program is shown below:~~

~~<ol style="list-style-type: lower-alpha;"><li>The second parameter 10 indicates the counting time of the door. If there is no dog feeding in this time, the system will restart.</li><li>We can feed the dog by pressing any keys on the keyboard~~ int main(~~except ESC~~void)~~. After the dog is fed, the program will print a line of Keep Alive to indicate that the dog is successful</li></ol>~~

~~orangepi@orangepi:~$ '''sudo watchdog_test 10'''~~{

~~open success~~:printf("Hello World!\n");

~~options is 33152,identity is sunxi-wdt~~

~~put_usr~~ :return~~,if 0,success:~~0;

~~The old reset time is~~}|}</ol><ol start="3" style="list-style-type: 16lower-alpha;"><li>Then compile and run '''hello_world.c'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''

~~return ENOTTY,if -1,success~~orangepi@orangepi:0~$ '''./hello_world'''

~~return ENOTTY,if~~ 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-~~1,success~~alpha;"><li>Python3 specific version is shown below</li>{| class="wikitable" style="width:0800px;" |-| ~~put_user return,if 0,success~~orangepi@orangepi:0~$ '''python3'''

~~put_usr return~~Python 3.8.10 (default,~~if 0~~Nov 14 2022,~~success~~12:059:47)

~~keep alive~~[GCC 9.4.0] on linux

~~keep alive~~Type "help", "copyright", "credits" or "license" for more information.

~~keep alive~~>>>|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>'''hello_world.py''' program in Python language</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.py'''

print('Hello World!')|}</ol><~~span id~~ol start="~~check-the-serial~~3" style="list-~~number~~style-oftype: lower-~~the-rk3566-chip~~alpha;"><li>The results of running '''hello_world.py''' are shown below</~~span~~li>{| class="wikitable" style= ~~Check the serial number of the RK3566 chip ==~~"width:800px;" |-| orangepi@orangepi:~$ '''python3 hello_world.py'''

~~The commands~~ Hello World!|}</ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>Ubuntu Focal's compilation tool and operating environment without the installation of Java default<ol style="list-style-type: lower-alpha;"><li>You can use the ~~RK3566 chip serial number are shown below. The serial number of each chip is different~~following command to install '''openjdk-17'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>After installation, so you can ~~use~~ check the ~~serial number to distinguish multiple development boards.~~version of Java</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''java --version'''

~~orangepi@orangepi:~$ '''cat_serial~~openjdk 17.~~sh'''~~0.2 2022-01-18

~~Serial : '''8fa18eaf489041f0'''~~OpenJDK Runtime Environment (build 17.0.2+8-Ubuntu-120.04)

OpenJDK 64-Bit Server VM (build 17.0.2+8-Ubuntu-120.04, mixed mode, sharing)|}<~~span id~~/ol><ol start="3" style="~~the~~list-~~method~~style-~~of-downloading-and-installing~~type: lower-alpha;"><li>Edit the~~-balenaetcher-~~'''hello_world.java''' of Jave version~~-of-arm64">~~</~~span~~li>{| class="wikitable" style= ~~The method of downloading and installing the balenaEtcher version of arm64 ==~~"width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''

~~<ol style="list-style-type: decimal;"><li>The download address of Balenaetcher ARM64 version is: <ol style="list-style-type: lower-alpha;"><li>The download address of the Deb installation package is shown below, and it needs to be installed to use</li></ol></li></ol>~~public class hello_world

~~https://github.com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balena-etcher-electron_1.7.9+5945ab1f_arm64.deb~~{

~~<ol start="2" style="list-style-type~~: ~~lower-alpha;"><li>The download address of the Appimage version that does not need to be installed is shown below: </li></ol>~~public static void main(String[] args)

~~https~~:~~//github.com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balenaEtcher-1.7.9+5945ab1f-arm64.AppImage~~{

~~<div class="figure">~~::System.out.println("Hello World!");

~~[[File~~:~~pi3b-img275.png|527x211px|IMG_256]]~~}

}|}</~~div~~ol><ol start="24" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~How to install~~ Then compile and ~~use the deb version of Balenaetcher:~~ run '''hello_world.java'''</pli>~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>deb version of Balenaetcher installation commands as shown below~~|-| orangepi@orangepi: ~~</li></ol></li></ol>~~~$ '''javac hello_world.java'''

orangepi@orangepi:~$ '''~~sudo apt install -y \~~java hello_world'''

~~'''-~~Hello World!|}</ol></li></ol></~~balena-etcher-electron_1.7.9+5945ab1f_arm64.deb'''~~span>

~~<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></ol>~~= Ubuntu jammy system ===

<~~div~~ ol style="list-style-type: decimal;"><li>Ubuntu Jammy is installed with the GCC compilation tool chain by default, which can directly compile the C language program in the Linux system of the development board<ol style="list-style-type: lower-alpha;"><li>The version of the gcc is shown below</li>{| class="~~figure~~wikitable" style="width:800px;">|-| orangepi@orangepi:~$ '''gcc --version'''

~~[[File:pi3b~~gcc (Ubuntu 11.2.0-~~img89~~19ubuntu1) '''11.2.~~png|507x249px|IMG_256]]~~0'''

~~<div class="figure">~~ ~~[[File:pi3b-img276.png|429x263px|IMG_256]]~~ ~~</div><ol start="3" style="list-style-type: decimal~~This is free software;">~~<li>How to use~~ see the ~~AppImage version of balenaEtcher: <ol style="list-style-type: lower-alpha;"><li>First add permissions to Balenaetcher</li></ol></li></ol>~~ ~~orangepi@orangepi:~/Desktop$ '''chmod +x balenaEtcher-1.7.9+5945ab1f-arm64~~source for copying conditions.~~AppImage'''~~There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

|}

</ol>

<li>~~Then select~~ Write the ~~AppImage version balenaEtcher right -click the mouse, and then click Execute to open balenaEtcher~~'''hello_world.c''' program of c language</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.c'''

~~[[File:pi3b-img277~~#include <stdio.~~png|145x118px]]~~h>

~~~~

~~== The installation method of the Bt-Panel Linux panel ==~~

'''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 int main(~~excerpted from the [https://www.bt.cn/new/index.html official website of the Bt-Panel]~~void)~~'''~~

~~# 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/~~printf(&~~amp~~quot;Hello World!\n");~~,size=2G/' /etc/fstab'''~~

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

~~<ol start="2" style="list-style-type~~: ~~decimal~~return 0;">~~<li>After restarting, you can see that the size of the'''/tmp''' space has become 2G.</li></ol>~~

}|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then compile and run '''hello_world.c'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''df gcc -~~h | grep "/tmp"~~o hello_world hello_world.c'''

~~tmpfs 2.0G 12K~~ orangepi@orangepi:~$ '''2.0G/hello_world''' ~~1% /tmp~~

Hello World!|}</ol ~~start="3" style="list-style-type: decimal;"~~>~~<li>Then enter the following command in the Linux system to start the installation of the Bt-Panel~~</li></ol>

<ol start="2" style="list-style-type: decimal;"><li>Ubuntu jammy is installed with Python3 by default<ol style="list-style-type: lower-alpha;"><li>Python3 specific version is shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~sudo install_bt_panel.sh~~python3'''

~~<ol start="4" style="list-style-type: decimal;"><li>Then the pagoda installation program reminds whether to install the~~ Python '''~~Bt-Panel~~3.10.4''' ~~to the'''/www''' folder~~(main, Apr 2 2022, ~~and enter y at this time</li></ol>~~09:04:19) [GCC 11.2.0] on linux

~~+----------------------------------------------------------------------~~Type "help", "copyright", "credits" or "license" for more information.

>>>| Bt}</ol><ol start="2" style="list-style-type: lower-~~WebPanel FOR CentOS~~alpha;"><li>Edit '''hello_world.py''' program in Python language</~~Ubuntu/Debian~~li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.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;" | ~~Copyright © 2015~~-~~2099 BT-SOFT(http~~| orangepi@orangepi:~~//www~~~$ '''python3 hello_world.~~bt.cn) All rights reserved.~~ ~~+----------------------------------------------------------------------~~py'''

Hello World!| ~~The WebPanel URL will be http~~}</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</~~SERVER_IP~~li>{| class="wikitable" style="width:~~8888 when installed.~~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'''

~~+-------------------------------------------------------------------~~openjdk 18-ea 2022-03-22

~~Do you want to install Bt~~OpenJDK Runtime Environment (build 18-ea+36-Ubuntu-~~Panel to the /www directory now?(y/n~~1)~~: '''y'''~~

OpenJDK 64-Bit Server VM (build 18-ea+36-Ubuntu-1, mixed mode, sharing)|}</ol><ol start="53" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then you have to wait patiently. When you see the printing information below~~ Edit the ~~terminal output, it means that the pagoda has been installed~~'''hello_world. ~~The entire installation process takes about 34 minutes. There may be some differences according to~~ java''' of the ~~difference in network speed~~Jave version</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''

~~[[File:pi3b-img278.png|576x233px]]~~public class hello_world

~~<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|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 can choose "I have agreed and read" User Agreement ", and then click" Enter the panel " You can enter the Bt-Panel</li></ol>{

:public static void main(String[~~[File:pi3b-img280.png|575x317px]~~]args)

~~<ol start="8" style="list-style-type~~: ~~decimal;">~~<li>After entering the Bt-Panel, you will first prompt that you need to bind the account of the Bt-Panel official website. If you do n’t have an account, you can go to the pagoda's official website ('''https://www.bt.cn''') to register one.</li></ol>{

~~[[File~~:~~pi3b-img281~~:System.out.~~png|576x300px]]~~println("Hello World!");

~~<ol start="9" style="list-style-type~~: ~~decimal;">~~<li>The final display interface is shown in the figure below. You can intuitively see some status information of the development board Linux system, such as load state, CPU usage, memory usage and storage space usage</li></ol>}

~~[[File~~}|}</ol><ol start="4" style="list-style-type:~~pi3b~~lower-~~img282~~alpha;"><li>Then compile and run '''hello_world.~~png~~java'''</li>{|~~575x306px]]~~class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''javac hello_world.java'''

~~<ol start="10" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>More functions of the Bt-Panel can refer to the following information to explore by yourself</li></ol>~~~$ '''java hello_world'''

~~Manual: [http:~~Hello World!|}</ol></~~docs.bt.cn '''http:~~li></ol></~~docs.bt.cn''']~~span>

~~Forum address: [https://www.bt.cn/bbs '''https://www.bt.cn/bbs''']~~== QT installation method ==

~~GitHub Link: '''https://github.com/aaPanel/BaoTa'''~~# Use the following script to install QT5 and QT Creator

~~== Set the Chinese environment and install Chinese input method ==~~| orangepi@orangepi:~$ '''install_qt.sh'''|}

<ol start="2" style="list-style-type: decimal;"><li>The QT version number will be automatically printed after installation<ol style="list-style-type: lower-alpha;"><li>Ubuntu20.04 comes with QT version '''5.12.8'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ ''~~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~~'install_qt.sh'''

~~=== Debian system installation method ===~~......

~~<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></ol></li></ol>~~QMake version 3.1

Using Qt version '''5.12.8''' in /usr/lib/aarch64-linux-gnu|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Ubuntu22.04 comes with QT version '''5.15.3'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~sudo dpkg-reconfigure locales~~install_qt.sh'''

~~<ol start="2" style="list-style-type: lower-alpha;"><li>Then select '''zh_CN~~.UTF-8 UTF-8''' in the pop-up interface (to move up and down through the upper and lower direction buttons on the keyboard, select it through the space key, and finally move the cursor to '''<OK>''' through the TAB key, then press the ENTER key )</li></ol>.....

~~[[File:pi3b-img283~~QMake version 3.~~png|575x296px]]~~1

Using Qt version '''5.15.3''' in /usr/lib/aarch64-linux-gnu

|}

</ol>

<li>~~Then set the default~~ Debian11 comes with QT version '''~~locale~~5.15.2''' as </li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~zh_CN~~install_qt.~~UTF-8~~sh'''~~</li></ol>~~

~~[[File:pi3b-img284~~.~~png|575x160px]]~~.....

QMake version 3.1

Using Qt version '''5.15.2''' in /usr/lib/aarch64-linux-gnu

|}

</ol>

<li>~~After exiting the interface, the~~ Debian12 comes with QT version '''~~locale~~5.15.8''' ~~settings will be started. The output displayed by the command line is shown below~~</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_qt.sh'''

~~orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''~~......

~~Generating locales (this might take a while)..~~QMake version 3.1

~~en_US~~Using Qt version '''5.~~UTF~~15.8''' in /usr/lib/aarch64-~~8... done~~linux-gnu|}</ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>Then you can see the QT Creator launch icon in '''Applications'''</li>

~~zh_CN.UTF~~[[File:pi3b-~~8..~~img327. ~~done~~png]]

~~Generation complete~~QT Creator can also be opened using the following command{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''qtcreator'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''During the startup of QT and QT applications, if the following error is displayed, ignore it.This error has no impact on application running.'''

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

~~<li>Then open '''Input Method'''</li></ol>~~

~~[[File~~'''libGL error:~~pi3b-img285.png|575x361px]]~~failed to create dri screen'''

~~<ol start="3" style="list-style-type: decimal;"><li>Then select~~ '''OKlibGL error: failed to load driver: rockchip'''~~</li></ol>~~

~~[[File~~'''libGL error:~~pi3b-img286.png|295x212px]]~~failed to create dri screen'''

'''libGL error: failed to load driver: rockchip'''</big>

|}

</ol>

<li>~~Then select '''Yes'''~~The interface after QT Creator is opened is as follows</li~~></ol~~>

[[File:pi3b-~~img287~~img328.png~~|303x192px~~]]</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>

[[File:pi3b-img329.png]]</ol><ol start="52" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then select~~ The default version of QT Creator in '''~~fcitx~~Ubuntu22.04'''is as follows</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>

[[File:pi3b-~~img288~~img331.png~~|307x220px~~]]</ol><ol start="4" style="list-style-type: lower-alpha;"><li>The default version of QT Creator in '''Debian12''' is as follows</li>

[[File:pi3b-img332.png]]

</ol>

</li></ol>

<li>Then ~~select~~ set QT<ol style="list-style-type: lower-alpha;"><li>First open '''Help'''->'''OKAbout Plugins...'''</li> [[File:pi3b-img333.png]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then remove the check box for '''ClangCodeModel'''</li>

[[File:pi3b-~~img289~~img334.png~~|305x216px~~]]</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>|}

[[File:pi3b-img335.png]]

[[File:pi3b-img336.png]]

</ol>

</li></ol>

<li>~~'''Then restart the Linux system to make the configuration effective'''</li><li>Then~~ You can then open ~~'''Fcitx configuration'''~~a sample code</li~~></ol~~>

[[File:pi3b-~~img290~~img337.png~~|575x376px~~]]</ol><ol start="8" style="list-style-type: decimal;"><li>Clicking on the example code will automatically open the corresponding instruction document, you can carefully read the instructions</li>

[[File:pi3b-img338.png]]

</ol>

<li>Then click ~~the + of the position shown in the figure below~~'''Configure Project'''</li>~~</ol>~~ ~~[[File:pi3b-img291.png|280x187px]]~~

[[File:pi3b-img339.png]]

</ol>

<li>Then ~~search '''Google Pinyin'''~~ click the green triangle in the lower left corner to compile and ~~click '''OK'''~~run the sample code</li~~></ol~~>

~~<div class="figure">~~ [[File:pi3b-~~img292~~img340.png~~|291x196px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-10.jpg未标题-10~~]] </~~div~~ol>

<li>~~Then put '''Google Pinyin''' to~~ After waiting for a period of time, the ~~front~~interface shown in the following figure will pop up, which indicates that QT can compile and run normally</li>~~</ol>~~ ~~[[File:pi3b-img293.png|299x202px]]~~ ~~[[File:pi3b-img294.png|300x202px]]~~

[[File:pi3b-img341.png]]

</ol>

<li>~~Then open the~~ Reference documents</li>{| class="wikitable" style="width:800px;" |-| '''~~Geany~~https://wiki.qt.io/Install_Qt_5_on_Ubuntu''' ~~editor to test the Chinese input method</li></ol>~~

~~[[File~~'''https:~~pi3b-img295~~//download.~~png|349x212px]]~~qt.io/archive/qtcreator'''

'''https://download.qt.io/archive/qt'''|}</ol ~~start="13" style~~>~~<li>The Chinese input method test is shown below</li~~></olspan>

~~[[File:pi3b-img296.png|575x325px]]~~== ROS Installation Method ==

<~~ol start~~span id="~~14" style="list~~how-to-install-ros-1-noetic-on-~~style~~ubuntu-~~type: decimal;~~20.04">~~<li>You can switch the Chinese and English input method through the '''Ctrl+Space''' shortcut~~</~~p></li~~span>~~<li>If the entire system is required as Chinese, the variables in '''/etc/default/locale''' can be set~~ === How to ~~'''zh_CN~~install ROS 1 Noetic on Ubuntu 20.~~UTF-8'''</li></ol>~~04 ===

~~orangepi@orangepi:~$~~ # The current active version of ROS 1 is as follows, the recommended version is '''~~sudo vim /etc/default/locale~~Noetic Ninjemys'''

# ::[[File ~~generated by update~~:pi3b-~~locale~~img342.png|800px]]

~~LC_MESSAGES='''zh_CN~~::[[File:pi3b-img343.~~UTF-8'''~~png|800px]]

~~LANG~~::{| class="wikitable" style="width:800px;" |-| [http://docs.ros.org/ '''~~zh_CN~~http://docs.~~UTF-8~~ros.org''']

~~LANGUAGE=~~'''~~zh_CN~~https://wiki.~~UTF-8~~ros.org/Distributions'''|}

<ol start="162" style="list-style-type: decimal;"><li>~~Then~~ The official installation document link of ROS 1 '''~~restart~~ Noetic Ninjemys''' is as follows:</li>{| class="wikitable" style="width:800px;" |-| [http://wiki.ros.org/noetic/Installation/Ubuntu '''http://wiki.ros.org/noetic/Installation/Ubuntu''']|}</ol><ol start="3" style="list-style-type: decimal;"><li>In the official installation document of ROS '''Noetic Ninjemys''', Ubuntu recommends using Ubuntu20.04, so please make sure that the systemused by the development board is ''' ~~to see the~~ Ubuntu20.04 desktop system ~~displayed as Chinese~~</lispan>'''</olli>{| class="wikitable" style="width:800px;" |-| http://wiki.ros.org/noetic/Installation|}

[[File:pi3b-~~img297~~img344.png~~|576x356px~~]]</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@orangepi3b:~$ '''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;" |-| <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.'''

~~~~

~~=== The installation method of Ubuntu 20.04 system ===~~

~~# First open~~ '''~~Language Support~~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 github normally, and then manually run the following Order.'''

~~[[File:pi3b-img298.png|575x351px]]~~

~~<ol start="2" style="list-style-type: decimal;"><li>Then find~~ '''~~Chinese (China)~~https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml''' ~~option</li></ol>~~

~~[[File~~'''Hit https:~~pi3b-img299~~//raw.~~png|318x311px]]~~githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml'''

~~<ol start="3" style="list-style-type: decimal;"><li>Then use the left mouse button to select~~ '''~~Chinese (China)~~ERROR: error loading sources list:''' ~~and hold it down, and then drag it up to the beginning. The display is shown below: </li></ol>~~

~~[[File~~:~~pi3b~~'''The read operation timed out'''</big>|}{| class="wikitable" style="width:800px;" |-~~img300~~| orangepi@orangepi:~$ '''source /opt/ros/noetic/setup.~~png|324x320px]]~~bash'''

orangepi@orangepi:~$ '''~~Note that this step is not easy to drag, please try more patiently.~~sudo rosdep init'''

~~<ol start="4" style="~~Wrote /etc/ros/rosdep/sources.list.d/20-~~style-type: decimal;"><li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system</li></ol>~~default.list

~~[[File~~Recommended:~~pi3b-img301.png|321x316px]]~~please run

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

~~<li>Then set the '''Keyboard input method system''' to '''fcitx'''</li></ol>~~

~~[[File~~:~~pi3b-img302.png|327x320px]]~~:rosdep update

~~<ol start="6" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>~~~$ '''~~hen restart the Linux system to make the configuration effective~~rosdep update'''~~</li>~~<li>After re -entering the system, please do '''not ask me again''' at the interface below, and then determine whether the standard folder should be updated as Chinese based on your preference.</li></ol>

~~[[File:pi3b-img303~~reading in sources list data from /etc/ros/rosdep/sources.~~png|303x247px]]~~list.d

~~<ol start="8" style="list-style-type~~Hit https: ~~decimal;"><li>Then you can see that the desktop is displayed as Chinese<~~/~~li><~~/~~ol>~~raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml

~~[[File~~Hit https:~~pi3b-img304~~//raw.~~png|575x383px]]~~githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml

~~<ol start="9" style="list-style-type~~Hit https: ~~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>~~raw.githubusercontent.com/ros/rosdistro/master/rosdep/python.yaml

~~[[File~~Hit https:~~pi3b-img305~~//raw.~~png|576x292px]]~~githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml

~~<ol start="10" style="list-style-type~~Hit https: ~~decimal;"><li>After opening '''Geany''', the default is an English input method~~//raw.githubusercontent. ~~We can switch into Chinese input method through the '''Ctrl+Space''' shortcut keys, and then we can enter Chinese<~~com/~~li><~~ros/~~ol>~~rosdistro/master/releases/fuerte.yaml

~~[[File~~Query rosdistro index https:~~pi3b~~//raw.githubusercontent.com/ros/rosdistro/master/index-~~img306~~v4.~~png|575x308px]]~~yaml

~~=== The installation method of ubuntu 22.04 system ===~~life distro "ardent"

~~# First open '''Language Support'''~~Skip end-of-life distro "bouncy"

~~[[File:pi3b~~Skip end-~~img298.png|575x351px]]~~of-life distro "crystal"

~~<ol start="2" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "dashing"">~~<li>Then find '''Chinese (China)''' option</li></ol>~~

~~[[File:pi3b~~Skip end-~~img307.png|335x326px]]~~of-life distro "eloquent"

~~<ol start="3" style="list-style-type: decimal~~Add distro "foxy"">~~<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-img308.png|337x331px]]~~Add distro "galactic"

~~'''Note that this step is not easy to drag, please try more patiently.'''~~Skip end-of-life distro "groovy"

~~<ol start="4" style="list-style-type: decimal~~Add distro "humble"">~~<li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system</li></ol>~~

~~[[File:pi3b~~Skip end-~~img309.png|336x330px]]~~of-life distro "hydro"

~~<ol start="5" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "indigo"">~~<li>'''Then restart the Linux system to make the configuration effective'''</li>~~<li>After re -entering the system, please '''do not ask me again''' at the interface below, and then determine whether the standard folder should be updated as Chinese based on your preference</li></ol>

~~[[File:pi3b~~Skip end-~~img303.png|303x247px]]~~of-life distro "jade"

~~<ol start="7" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "kinetic"">~~<li>Then you can see that the desktop is displayed as Chinese</li></ol>~~

~~[[File:pi3b~~Skip end-~~img304.png|575x383px]]~~of-life distro "lunar"

~~<ol start="8" style="list-style-type: decimal~~Add distro "melodic"">~~<li>Then open the Fcitx5 configuration program</li></ol>~~

~~[[File:pi3b-img310.png|575x349px]]~~Add distro "noetic"

~~<ol start="9" style="list-style-type: decimal~~Add distro "rolling"">~~<li>Then choose to use Pinyin input method</li></ol>~~

~~<div class="figure">~~ ~~[[File:pi3b-img311~~updated cache in /home/orangepi/.~~png|338x267px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-11~~ros/rosdep/sources.~~jpg未标题-11]]~~cache|}</~~div~~ol><ol start="106" style="list-style-type: decimal;"><li>~~The interface after~~ Then open a command line terminal window on the ~~selection is shown below~~desktop, and then ~~click OK~~use the test_ros.sh script to start a small turtle routine to test whether ROS can be used normally</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''test_ros.sh'''|}<li>After running the '''test_ros.sh''' script, a little turtle as shown in the figure below will pop up</olli>

~~[[File:pi3b-img312.png|366x290px]]~~<div class="figure">

~~<ol start="11" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Then we can open the '''Geany''' to test Chinese input method, and the way to open is shown in the figure below</li></ol>~~img345.png]]

~~[[File~~</div></ol><ol start="8" style="list-style-type:~~pi3b-img305.png|576x292px]]~~decimal;"><li>Then please keep the terminal window just opened at the top</li>

<~~ol start~~div class="12figure" ~~style="list-style-type: decimal;">~~<li>After opening '''Geany''', it is still an English input method by default. We can switch into Chinese input methods through the '''Ctrl+Space''' shortcut keys, and then we can enter Chinese</li></ol>

[[File:pi3b-~~img313~~img346.png~~|576x408px~~]]

<~~span id~~/div></ol><ol start="9" style="~~how~~list-tostyle-~~remotely-log-in-to-the-linux-system-desktop-method~~type: decimal;"><~~/span~~li>~~== How~~ At this time, press the direction keys on the keyboard to ~~remotely log in~~ control the little turtle to ~~the Linux system desktop method ==~~move up, down, left, and right</li>

~~'''Ubuntu Gnome Wayland image does not support Nomachine and VNCs introduced here to remotely log in~~ [[File:pi3b-img347.png]]</ol>

~~~~==~~= Use nomachine remote login~~ How to install ROS 2 Galactic on Ubuntu 20.04 ===

# The current active version of ROS 2 is as follows, the recommended version is '''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: Galactic Geochelone'''

~~'''https~~:~~//knowledgebase.nomachine~~:[[File:pi3b-img348.~~com/DT10R00166'''~~png]]

~~'''Nomachine supports Windows, Mac, Linux, iOS, and Android platforms, so we can remotely log in to control Orange PI development boards through Nomachine on multiple devices~~::[[File:pi3b-img349. 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.'''png]]

::{| class="wikitable" style="width:800px;" |-| [http://docs.ros.org/ '''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 normallyhttp://docs.ros.org''']

~~<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<~~http://docs.ros.org/en/galactic/p>~~<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~~Releases.html''' ~~installation package here. The download link is shown below: </li></ol></li></ol>~~|}

<ol start="2" style="list-style-type: decimal;"><li>The link to the official ROS 2 '''Galactic Geochelone''' installation documentation is as follows:</li>{| class="wikitable" style="width:800px;" |-| '''~~Note that this download link may change, please recognize the DEB package of the ARMV8~~docs.ros.org/en/galactic/~~ARM64 version~~Installation.html'''

~~[https~~'''http://~~www~~docs.~~nomachine~~ros.~~com~~org/en/galactic/Installation/~~download~~Ubuntu-Install-Debians.html'''|}</~~download&id~~ol><ol start=~~112&s~~"3" style=~~ARM~~ "list-style-type: decimal;"><li>It is recommended to use Ubuntu20.04 in the official installation document of ROS 2 '''~~https~~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'''</~~downloads~~li><li>Use the '''install_ros.~~nomachine.com~~sh''' script to install ros2</~~download~~p></~~?id~~li>{| class=~~118&amp~~"wikitable" style="width:800px;~~distro~~" |-| orangepi@orangepi:~$ '''install_ros.sh ros2'''|}</ol><ol start=~~ARM~~"5" style="list-style-type: decimal;"><li>The '''install_ros.sh''' script will automatically run the '''ros2 -h''' command after installing ros2. If you can see the following print, it means that the ros2 installation is complete</li>{| class="wikitable" style="width:800px;" |-| usage: ros2 [-h]Call `ros2 <command> -h` for more detailed usage. ...

~~[[File:pi3b-img314.png|575x227px]]~~

~~<ol start="~~ros2 is an extensible command-line tool for ROS 2~~" style="list-style-type: lower-alpha;"><li>In addition, you can also download the installation package to '''NoMachine''' in the '''official tools'''~~.~~</li></ol>~~

~~[[File:pi3b-img315.png|66x102px]]~~

~~<blockquote>First enter the '''remote login software-Nomachine''' folder</blockquote>[[File~~optional arguments:~~pi3b-img316.png|271x43px]]~~

~~<blockquote>Then download the ARM64 version of the DEB installation package</blockquote>[[File~~:~~pi3b~~-~~img317.png|180x109px]]~~h, --help show this help message and exit

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

~~<li>Then upload the downloaded '''nomachine_x.x.x_x_arm64.deb''' to the Linux system of the development board.</li>~~

~~<li>Then use the following command to install '''NoMachine''' in the Linux system of the development board</li></ol>~~

~~orangepi@orangepi~~Commands:~~~$ '''sudo dpkg -i nomachine_x.x.x_x_arm64_arm64.deb'''~~

~~<ol start="2" style="list~~:action Various action related sub-~~style-type: decimal;"><li>Then download the nomachine software Windows version of the installation package, the download address is shown below</li></ol>~~commands

~~'''Note that this download link may change.'''~~:bag Various rosbag related sub-commands

~~'''https~~:~~//downloads.nomachine.com/download/?id=9'''~~component Various component related sub-commands

~~[[File~~:~~pi3b~~daemon Various daemon related sub-~~img318.png|575x163px]]~~commands

~~<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>~~doctor Check ROS setup and other potential issues

~~[[File~~:~~pi3b-img319.png|76x66px]]~~interface Show information about ROS interfaces

~~<ol start="5" style="list-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>launch Run a launch file

~~[[File~~:~~pi3b~~lifecycle Various lifecycle related sub-~~img320.png|321x92px]]~~commands

~~<ol start="6" style="list~~:multicast Various multicast related sub-~~style-type: decimal;"><li>Then click '''OK'''</li></ol>~~commands

~~[[File~~:~~pi3b~~node Various node related sub-~~img321.png|402x275px]]~~commands

~~<ol start="7" style="list~~:param Various param related sub-~~style-type: decimal;"><li>Then enter the username and password of the Linux system in the corresponding position in the figure below, and then click '''OK''' to start logging in</li></ol>~~commands

~~<div class="figure">~~:pkg Various package related sub-commands

~~[[File~~:~~pi3b-img322.png|303x204px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-12.jpg未标题-12]]~~run Run a package specific executable

~~</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~~security Various security 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.''':topic Various topic related sub-commands

~~'''Ubuntu 20.04 tests many problems with VNC, please do not use this method.'''~~:wtf Use `wtf` as alias to `doctor`

~~# First run the '''set_vnc.sh''' script settings, and '''remember to add Sudo permissions'''~~

:Call `ros2 <command> -h` for more detailed usage.|}</ol><ol start="6" style="list-style-type: decimal;"><li>Then you can use the '''test_ros.sh''' script to test whether ROS 2 is installed successfully. If you can see the following print, it means that ROS 2 can run normally</li>{| class="wikitable" style="width:800px;" |-| orangepi@~~orangepi~~orangepi3b:~$ '''~~sudo set_vnc~~test_ros.sh'''

~~You will require a password to access your desktops~~[INFO] [1671174101.200091527] [talker]: Publishing: 'Hello World: 1'

~~Password~~[INFO] [1671174101.235661048] [listener]: ~~'''#Set the VNC password here, 8 -bit characters'''~~I heard: [Hello World: 1]

~~Verify~~[INFO] [1671174102.199572327] [talker]: Publishing: '~~''#Set the VNC password here, 8 -bit characters''~~Hello World: 2'

~~Would you like to enter a view-only password (y/n)? '''n'''~~[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]

~~xauth~~[INFO] [1671174103.199580322] [talker]: Publishing: 'Hello World: ~~file /root/.Xauthority does not exist~~3'

~~New~~ [INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]|}</ol><ol start="7" style="list-style-type: decimal;"><li>Run the following command to open rviz2</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''source /opt/ros/galactic/setup.bash''X' ~~desktop is orangepi3b:1~~

~~Creating default startup script /root/.vnc/xstartup~~orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''|}

~~Starting applications specified in /root/.vnc/xstartup~~<div class="figure">

~~Log file is /root/.vnc/orangepi3b~~[[File:1pi3b-img350.~~log~~png]]

~~Killing Xtightvnc process ID 3047~~</div></ol><ol start="8" style="list-style-type: decimal;"><li>For the usage of ROS, please refer to the documentation of ROS 2</li>{| class="wikitable" style="width:800px;" |-| '''http://docs.ros.org/en/galactic/Tutorials.html'''|}</ol>

~~New 'X' desktop is orangepi3b:1~~=== How to install ROS 2 Humble on Ubuntu 22.04 ===

~~Starting applications specified in /root/~~# Use the '''install_ros.~~vnc/xstartup~~sh''' script to install ros2

~~Log file is /root/.vnc/orangepi3b~~:1:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_ros.~~log~~sh ros2'''|}

<li~~><p~~>The ~~steps of using MobaxTerm software to connect~~ '''install_ros.sh''' script will automatically run the ~~development board Linux system desktop are shown below: <ol style="list~~'''ros2 -~~style-type: lower-alpha;"><li>First click Session~~h''' command after installing ros2. If you can see the following print, ~~then select VNC, then fill in~~ it means that the ~~IP address and port of the development board, and finally click OK to confirm~~ros2 installation is complete</li~~></ol></li></ol~~>

~~<div~~ {| class="~~figure~~wikitable">style="width:800px;" |-| usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...

~~[[File:pi3b-img324.png|490x349px|图片1208]]~~

~~</div><ol start="~~ros2 is an extensible command-line tool for ROS 2~~" style="list-style-type: lower-alpha;"><li>Then enter the password of the previously set VNC</li></ol>~~.

~~[[File:pi3b-img325.png|274x131px]]~~

~~<ol start="3" style="list-style-type~~optional arguments: ~~lower-alpha;"><li>The interface after the login is shown as shown in the figure below, and then the desktop of the Linux system can be remotely operated[[File:pi3b-img326.png|405x293px]]</li></ol>~~

~~== Some programming language tests supported by Linux system ==~~help show this help message and exit

~~~~

~~=== Debian Bullseye system ===~~

~~<ol style="list-style-type~~Commands: ~~decimal;"><li>Debian Bullseye is equipped with a gcc compilation tool chain by default, which can directly compile the C language program in the Linux system of the development board<ol style="list-style-type: lower-alpha;"><li>The version of the gcc is shown below</li></ol></li></ol>~~

~~orangepi@orangepi~~:~~~$ '''gcc~~ action Various action related sub-~~-version'''~~commands

~~gcc (Debian 10.2.1~~:bag Various rosbag related sub-~~6) 10.2.1 20210110~~commands

~~This is free software; see the source for copying conditions. There is NO~~:daemon Various daemon related sub-commands

~~warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.~~:doctor Check ROS setup and other potential issues

~~<ol start="2" style="list-style-type~~: ~~lower-alpha;"><li>Write C language of '''Hello_world.c''' program</li></ol>~~interface Show information about ROS interfaces

~~orangepi@orangepi~~:~~~$ '''vim hello_world.c'''~~launch Run a launch file

~~#include <stdio.h>~~:lifecycle Various lifecycle related sub-commands

~~int main(void)~~:multicast Various multicast related sub-commands

{:node Various node related sub-commands

~~printf("Hello World!\n");~~:param Various param related sub-commands

~~return 0;~~:pkg Various package related sub-commands

}:run Run a package specific executable

~~<ol start="3" style="list-style-type~~: ~~lower~~security Various security related sub-~~alpha;"><li>Then compile and run '''hello_world.c'''</li></ol>~~commands

~~orangepi@orangepi~~:~~~$ '''gcc~~ service Various service related sub-~~o hello_world hello_world.c'''~~commands

~~orangepi@orangepi~~:~~~$ '''./hello_world'''~~topic Various topic related sub-commands

~~Hello World!~~:wtf Use `wtf` as alias to `doctor`

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

~~<li>Debian BullSeye Default with Python3~~

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

~~<li>The specific version of Python is shown below</li></ol>~~

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

~~orangepi@orangepi~~:~$ Call `ros2 <command> -h` for more detailed usage.|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then you can use the '''~~python3~~test_ros.sh'''script to test whether ROS 2 is installed successfully. If you can see the following print, it means that ROS 2 can run normally</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi3b:~$ '''~~Python 3~~test_ros.~~9.2~~sh''' ~~(default, Feb 28 2021, 17:03:44)~~

[~~GCC 10.2~~INFO] [1671174101.200091527] [talker]: Publishing: 'Hello World: 1 ~~20210110] on linux~~'

~~Type "help", "copyright", "credits" or "license" for more information~~[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: 1]

~~>>>~~[INFO] [1671174102.199572327] [talker]: Publishing: 'Hello World: 2'

~~<ol start="~~[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2~~" style="list-style-type: lower-alpha;"><li>'''hello_world.py''' program in Python language</li></ol>~~]

~~orangepi@orangepi~~[INFO] [1671174103.199580322] [talker]: Publishing:~~~$ '''vim hello_world.py'~~'Hello World: 3'

~~print('~~[INFO] [1671174103.204019965] [listener]: I heard: [Hello World!: 3]|}</ol><ol start="4" style="list-style-type: decimal;"><li>Run the following command to open rviz2</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''source /opt/ros/humble/setup.bash''')

~~<ol start="3" style="list-style-type~~orangepi@orangepi: ~~lower-alpha;"><li>The results of running~~ ~$ '''~~hello_world.py~~ros2 run rviz2 rviz2''' ~~are shown below</li></ol>~~|}

~~orangepi@orangepi:~$ '''python3 hello_world.py'''~~<div class="figure">

~~Hello World!~~[[File:pi3b-img351.png]]

</div></ol><ol start="35" style="list-style-type: decimal;"><li>~~Debian Bullseye's compilation tool and operating environment that is not installed in Java by default~~Reference documents</pli>~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>You can use the following command to install OpenJDK. The latest version in Debian Bullseye is openjdk~~|-~~17<~~| '''http://~~li><~~docs.ros.org/~~ol>~~<en/~~li><~~humble/~~ol>~~index.html'''

~~orangepi@orangepi~~[http:~$ //docs.ros.org/en/galactic/Tutorials.html '''~~sudo apt install~~ http://docs.ros.org/en/humble/Installation/Ubuntu-~~y openjdk~~Install-~~17-jdk~~Debians.html''']|}</ol>

~~<ol start~~=~~"2" style~~=~~"list-style-type: lower-alpha;"><li>After installation, you can check the version of Java</li></ol>~~How to install kernel header files ==

~~orangepi@orangepi:~$~~ # The Linux image released by OPi comes with the deb package of the kernel header file by default, and the storage location is '''~~java --version~~/opt/'''

~~<ol start~~::{| class="3wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Edit the~~ |-| orangepi@orangepi:~$ '''~~hello_world.java~~ls /opt/linux-headers*''' ~~of the Jave version</li></ol>~~

~~orangepi@orangepi:~$ '''vim hello_world~~/opt/linux-headers-legacy-rockchip-rk356x_x.~~java'''~~x.x_arm64.deb|}

~~public~~ <ol start="2" style="list-style-type: decimal;"><li>Use the following command to install the deb package of the kernel header file</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The name of the kernel header file deb package needs to be replaced with the actual name, please do not copy it.'''</big>|}{| class ~~hello_world~~="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg -i /opt/linux-headers-legacy-rockchip-rk356x_1.x.x_arm64.deb'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>After installation, you can see the folder where the kernel header files are located under '''/usr/src'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ls /usr/src'''

~~public static void main(String[] args)~~linux-headers-5.10.160-rockchip-rk356x|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then you can write a hello kernel module to test the kernel header file<ol style="list-style-type: lower-alpha;"><li>First write the code of the hello kernel module, as follows:</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello.c'''

{#include <linux/init.h>

~~System.out.println(~~#include &~~quot~~lt;~~Hello World!~~linux/module.h&~~quot;)~~gt;

}

}static int hello_init(void)

~~<ol start="4" style="list-style-type: lower-alpha;"><li>Then compile and run '''hello_world.java'''</li></ol>~~{

~~orangepi@orangepi~~:~~~$ '''javac hello_world.java'''~~printk("Hello Orange Pi -- init\n");

~~orangepi@orangepi:~$ '''java hello_world'''~~

~~Hello World!~~:return 0;

~~=== Ubuntu Focal system ===~~}

~~<ol style="list-style-type: decimal;"><li>Ubuntu Focal has the GCC compilation tool chain by default, which can compile the C language program directly in the Linux system of the development board.<ol style="list-style-type: lower-alpha;"><li>The version of the gcc is shown below</li></ol></li></ol>~~static void hello_exit(void)

~~orangepi@orangepi:~$ '''gcc --version'''~~{

~~gcc~~ :printk(~~Ubuntu 9.4.0~~"Hello Orange Pi -~~1ubuntu1~20.04.1~~- exit\n") ~~9.4.0~~;

~~This is free software~~:return; ~~see the source for copying conditions. There is NO~~

~~warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.~~}

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

~~<li>'''hello_world.c''' program to write C language</li></ol>~~

~~orangepi@orangepi:~$ '''vim hello_world.c'''~~module_init(hello_init);

~~#include <stdio.h&gt~~module_exit(hello_exit);

~~int main(void)~~

MODULE_LICENSE("GPL");|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then write the Makefile for compiling the hello kernel module, as follows:</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim Makefile'''

~~printf~~ifneq (~~"Hello World!\n"~~$(KERNELRELEASE),);

~~return 0;~~obj-m:=hello.o

}else

~~<ol start~~KDIR :=~~"3" style="list~~/lib/modules/$(shell uname -~~style-type: lower-alpha;"><li>Then compile and run '''hello_world.c'''</li><~~r)/~~ol>~~build

~~orangepi@orangepi~~PWD :~=$ ~~'''gcc -o hello_world hello_world.c'''~~(shell pwd)

~~orangepi@orangepi~~all:~~~$ '''./hello_world'''~~

~~Hello World!~~:make -C $(KDIR) M=$(PWD) modules

~~<ol start="2" style="list-style-type~~clean: ~~decimal;"><li>Ubuntu Focal defaults to install Python3<ol style="list-style-type: lower-alpha;"><li>Python3 specific version is shown below</li></ol></li></ol>~~

~~orangepi@orangepi~~:~~~$ '''python3'''~~rm -f *.ko *.o *.mod.o *.mod *.symvers *.cmd *.mod.c *.order

~~Python~~ endif|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then use the make command to compile the hello kernel module.~~8.10 (default, Nov 14 2022, 12~~The output of the compilation process is as follows:</li>{| class="wikitable" style="background-color:59#ffffdc;width:~~47)~~800px;" |-| <big>'''If there is a problem with compiling the code you copied here, please go to the official tool to download the source code and upload it to the Linux system of the development board for testing.'''</big>

[~~GCC 9~~[File:pi3b-img352.~~4.0~~png|center]] ~~on linux~~|}{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''make'''

~~Type "help", "copyright", "credits" or "license" for more information~~make -C /lib/modules/5.10.160-rockchip-35xx/build M=/home/orangepi modules

~~>>>~~make[1]: Entering directory '/usr/src/linux-headers-5.10.160-rockchip-rk35xx'

~~<ol start="2" style="list-style-type~~: ~~lower-alpha;"><li>'''hello_world.py''' program in Python language<~~CC [M] /home/~~li><~~orangepi/~~ol>~~hello.o

:MODPOST /home/orangepi~~@orangepi:~$ '''vim hello_world~~/Module.~~py'''~~symvers

~~print('Hello World!')~~:CC [M] /home/orangepi/hello.mod.o

~~<ol start="3" style="list-style-type~~: ~~lower-alpha;"><li>The results of running '''hello_world.py''' are shown below<~~LD [M] /home/~~li><~~orangepi/~~ol>~~hello.ko

make[1]: Leaving directory '/usr/src/linux-headers-5.10.160-rockchip-rk35xx'|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>After compiling, the '''hello.ko''' kernel module will be generated</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~python3 hello_world~~ls *.pyko'''

~~Hello World!~~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:~$ '''sudo insmod hello.ko'''|}</ol><ol start="6" style="list-style-type: lower-alpha;"><li>Then use the '''demsg''' command to view the output of the '''hello.ko''' kernel module. If you can see the output below, it means that the '''hello.ko''' kernel module is loaded correctly.</li>

~~<ol start~~{| class="3wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Ubuntu Focal's compilation tool and operating environment without the installation of Java default~~|-| ~~<ol style="list-style-type~~orangepi@orangepi: ~~lower-alpha;"><li>You can use the following command to install~~ ~$ '''~~openjdk-17~~dmesg | grep "Hello"'''~~</li></ol></li></ol>~~

[ 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:~$ '''sudo ~~apt install -y openjdk-17-jdk~~rmmod hello'''

~~<ol start="2" style="list-style-type~~orangepi@orangepi: ~~lower-alpha~~~$ '''dmesg | grep "">~~<li>After installation, you can check the version of Java</li></ol>~~Hello"'''

~~orangepi@orangepi:~$ '''java~~ [ 2871.893988] Hello Orange Pi --~~version'''~~init

~~openjdk 17~~[ 3173.~~0.2 2022~~800892] '''Hello Orange Pi -- exit'''|}</ol></li></ol>

~~OpenJDK Runtime Environment (build 17.0.2+8~~== Use of the Raspberry PI's 5-~~Ubuntu-120.04)~~inch screen ==

~~OpenJDK 64~~=== Assembly method of Raspberry PI 5-inch screen ===

<ol ~~start~~style="3list-style-type: decimal;" ><li>First prepare the required accessories<ol style="list-style-type: lower-alpha;"><li>~~Edit the '''hello_world.java''' of Jave version~~Raspberry PI 5-inch MIPI LCD display + touch screen</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''vim hello_world~~pi3b-img353.~~java'''~~png]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>15pin MIPI cable</li>

~~public class hello_world~~[[File:pi3b-img354.png]]</ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>Then connect the 15pin MIPI cable to the Raspberry PI 5-inch screen in the way shown below (note the orientation of the insulation surface)</li>

{[[File:pi3b-img355.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Finally connect to the LCD interface of the Orange Pi 3B development board</li>

~~public static void main(String~~[[File:pi3b-img356.png]] ~~args)~~</ol>

{=== Open the Raspberry PI 5-inch screen configuration method ===

~~System~~<ol style="list-style-type: decimal;"><li>The Linux image does not open the 5-inch screen of the Raspberry PI by default.~~out~~If you need to use the 5-inch screen of the Raspberry PI, you need to open it manually.~~println(&quot~~</li><li>The steps to open the mipi lcd configuration are as follows:<ol style="list-style-type: lower-alpha;~~Hello World!&quot~~"><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>

[[File:pi3b-img358.png]]

</ol>

<li>Then ~~compile~~ use the arrow keys on the keyboard to locate the Rasp-7inch-touchscreen, and ~~run '''hello_world.java'''~~then use the space button to check</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img359.png]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then select '''~~javac hello_world.java~~<Save>'''to save</li>

~~orangepi@orangepi~~[[File:~$ pi3b-img360.png]]</ol><ol start="6" style="list-style-type: lower-alpha;"><li>Then select '''~~java hello_world~~<Back>'''</li>

~~Hello World!~~[[File:pi3b-img361.png]]</ol><ol start="7" style="list-style-type: lower-alpha;"><li>Then select '''<Reboot>''' to restart the system for the configuration to take effect</li>

~~=== Ubuntu jammy system ===~~img362.png]]

~~<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Ubuntu Jammy is installed with the GCC compilation tool chain by default, which can directly compile the C language program in~~ '''The above settings will eventually add the ~~Linux system~~ configuration of ~~the development board~~<~~/p><ol~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<li>The version of the gcc is shown below~~overlays=raspi-7inch-touchscreen</lispan><to /~~ol>~~<boot/~~li></ol>~~orangepiEnv.txt. After setting, you can check it first. If this configuration does not exist, then there is a problem with the settings.'''

~~orangepi@orangepi:~$~~ '''~~gcc~~ If you find it troublesome to use orangepi-config, you can also use the vim editor to open /boot/orangepiEnv.txt, and then add the configuration of overlays=raspi-7inch-~~version~~touchscreen is also possible.'''</big>

~~gcc (Ubuntu 11.2.0-19ubuntu1) '''11.2.0'''~~

~~This is free software~~'''overlays=raspi-7inch-touchscreen #Sample configuration'''|}</ol></li></ol><ol start="3" style="list-style-type: decimal; "><li>After startup, you can see the ~~source for copying conditions. There is NO~~lcd screen display as follows:</li>

~~warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE~~[[File:pi3b-img363.png]]</ol>

~~<ol start~~=~~"2" style~~=~~"list-style-type: lower-alpha;"><li>Write the '''hello_world.c''' program~~ = The method of ~~c language</li></ol>~~ ~~orangepi@orangepi:~$ '''vim hello_world.c'''~~server version image rotation display direction ===

~~#include &lt~~<ol start="1" style="list-style-type: decimal;~~stdio~~"><li>Add '''extraargs=fbcon=rotate:the direction to rotate''' in '''/boot/orangepiEnv.~~h>~~txt''' This line configuration can set the direction displayed by the server version of the Linux system, where the number after '''fbcon=rotate:''' can be set as:</li>

~~int main~~<ol style="list-style-type: lower-alpha;"><li>0: normal screen (~~void~~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 /boot/orangepiEnv.txt'''

{overlays=lcd1

~~printf(&quot~~'''extraargs=cma=64M fbcon=rotate:3'''|}{| class="wikitable" style="background-color:#ffffdc;~~Hello World!\n&quot~~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="2" style="list-style-type: decimal;"><li>Then '''restart''' the Linux system and you can see that the direction displayed on the LCD screen has been rotated</li></ol>

~~return 0;~~

}=== Method of rotating display and touch direction of desktop version image ===

~~<ol start="3" style="list-style-type: lower-alpha;"><li>Then compile and run~~ # First open '''~~hello_world.c~~Display'''~~</li></ol>~~Settings in Linux

~~orangepi@orangepi~~:~~~$ '''gcc~~ :[[File:pi3b-~~o hello_world hello_world.c'''~~ ~~orangepi@orangepi:~$ '''~~img364.~~/hello_world'''~~ ~~Hello World!~~png]]

<li>~~Ubuntu jammy is installed with Python3 by default~~Then select the direction you want to rotate in '''Rotation'''

<li>~~Python3 specific version~~ '''None''': no rotation</li><li>'''Left''': rotate left 90 degrees</li><li>'''Inverted''': Flip up and down, which is ~~shown below~~equivalent to rotating 180 degrees</li><li>'''Right''': rotate right 90 degrees</li> [[File:pi3b-img365.png]]</ol>

</li></ol>

<li>Then click '''Apply'''</li>

~~orangepi@orangepi~~[[File:~~~$ '''python3'''~~pi3b-img366.png]]</ol><ol start="4" style="list-style-type: decimal;">~~Python~~ <li>Then select '''~~3.10.4~~Keep this configuration''' ~~(main, Apr 2 2022, 09:04:19) [GCC 11.2.0] on linux~~ ~~Type "help", "copyright", "credits" or "license" for more information.~~ ~~>>>~~</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>~~Edit~~ '''~~hello_world~~Left''': rotate left 90 degrees</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''set_lcd_rotate.pysh left''' ~~program in Python language~~|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>'''Inverted''': Flip up and down, which is equivalent to rotating 180 degrees</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''set_lcd_rotate.sh inverted'''|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>'''Right''': rotate right 90 degrees</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''set_lcd_rotate.sh right'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The set_lcd_rotate.sh script mainly does four things:'''

~~orangepi@orangepi:~$ '''vim hello_world.py'''~~

~~print(~~'~~Hello World!~~')'1. Rotate the direction displayed by the framebuffer''' '''2. Rotate the direction of the touch'''

~~<ol start="3" style="list-style-type: lower-alpha;"><li>The results of running~~ '''~~hello_world~~3.pyTurn off the boot logo''' ~~are shown below</li></ol>~~

~~orangepi@orangepi:~$~~ '''~~python3 hello_world~~4.pyRestart the system'''

~~Hello World!~~

~~<ol start="3" style="list-style-type: decimal~~'''Rotating the touch direction is achieved by adding the line Option "TransformationMatrix" "x x x x x x x x x"">~~<li>Ubuntu jammy defaults~~ to ~~compile tools and operating environments that are not installed in Java<~~/p>~~<ol style="list~~usr/share/X11/xorg.conf.d/40-~~style-type: lower-alpha~~libinput.conf Where "x x x x x x x x x"">~~<li>You can use the following command to install openjdk-18~~is configured differently for different directions.'''</libig>|}</ol>

</li></ol>

<li>Touch rotation reference</li>

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

|-

|

'''https://wiki.ubuntu.com/X/InputCoordinateTransformation'''

|}

</ol>

~~orangepi@orangepi:~$ '''sudo apt install -y openjdk-18-jdk'''~~== Instructions for using the switch logo ==

~~<ol start="2" style="list-style-type: lower-alpha;"><li>After installation~~# By default, ~~you can check~~ the switch logo will only be displayed in the desktop version of ~~Java<~~the system# Set the '''bootlogo''' variable to '''false''' in '''/~~li><~~boot/~~ol>~~orangepiEnv.txt''' to turn off the switch logo

::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~java --version~~vim /boot/orangepiEnv.txt'''

~~openjdk 18-ea 2022-03-22~~verbosity=1

~~OpenJDK Runtime Environment (build 18-ea+36-Ubuntu-1)~~'''bootlogo=false'''|}

~~OpenJDK 64~~<ol start="3" style="list-~~Bit Server VM (build 18~~style-~~ea+36-Ubuntu-1, mixed mode, sharing)~~type: decimal;"><li>Set the '''bootlogo''' variable to '''true''' in '''/boot/orangepiEnv.txt''' to enable the switch logo</li>

~~<ol start~~{| class="3wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Edit the~~ |-| orangepi@orangepi:~$ '''~~hello_world~~vim /boot/orangepiEnv.~~java~~txt''' ~~of the Jave version</li></ol>~~

~~orangepi@orangepi:~$ '''vim hello_world.java'''~~verbosity=1

~~public~~ '''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 ~~hello_world~~="wikitable" style="width:800px;" |-| '''/usr/share/plymouth/themes/orangepi/watermark.png'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>After replacing the boot logo picture, you need to run the following command to take effect</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo update-initramfs -u'''|}</ol>

{== How to use the ZFS file system ==

~~public static void main(String[] args)~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The latest version of Ubuntu20.04, Ubuntu22.04, Debian11 and Debian12 desktop version systems have pre-installed zfs, you can use it directly.'''

{'''The pre-installed zfs version in Ubuntu20.04 and Ubuntu22.04 desktop systems is 2.1.6.'''

~~System~~'''The pre-installed zfs version in Debian11 and Debian12 desktop systems is 2.~~out~~1.~~println("Hello World!");~~11.'''

}'''After the system starts, please first confirm whether the zfs kernel module has been loaded. If you can see zfs-related content using the lsmod command, it means that the system has pre-installed zfs.'''</big>

}orangepi@orangepi:~$ '''lsmod | grep "zfs"'''

~~<ol start="4" style="list-style-type: lower-alpha~~zfs  ">~~<li>Then compile and run '''hello_world.java'''</li></ol>~~                   2801664     0

~~orangepi@orangepi:~$ '''javac hello_world.java'''~~zunicode             327680     1   zfs

~~orangepi@orangepi:~$ '''java hello_world'''~~zzstd                  471040     1   zfs

~~Hello World!~~zlua                    139264     1   zfs

~~== QT installation method ==~~zcommon             69632     1   zfs

~~# Use the following script to install QT5 and QT Creator~~znvpair                 61440     2   zfs,zcommon

~~orangepi@orangepi:~$ '''install_qt.sh'''~~zavl                      16384     1   zfs

~~<ol start="2" style="list-style-type: decimal~~icp  ">~~<li>The QT version number will be automatically printed after installation<ol style="list-style-type: lower-alpha~~ ">~~<li>Ubuntu20.04 comes with QT version '''5.12.8'''</li></ol></li></ol>~~                  221184     1   zfs

~~orangepi@orangepi:~$ '''install_qt.sh'''~~spl                       77824     6   zfs,icp,zzstd,znvpair,zcommon,zavl|}

~~......~~=== How to install ZFS ===

~~QMake~~ {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Before installing zfs, please make sure that the Linux image used is the latest version 3.1In addition, if zfs is already installed in the system, it needs to be installed again.'''</big>|} 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|'''section on the method of installing the kernel header file''']].

~~Using Qt~~ In Ubuntu20.04, Ubuntu22.04 and Debian11 systems, zfs cannot be installed directly through apt, because the default apt source zfs version ~~'''5~~is lower than 2.1.6, and there is a problem of incompatibility with rk Linux5.1210 kernel.~~8'''~~ This problem is fixed in ~~/usr/lib/aarch64-linux-gnu~~zfs version 2.1.6 and later.

To solve this problem, we provide a zfs deb package that can be installed normally, which can be downloaded from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''official tool'''] of the development board. Open the '''<~~ol start~~span class="~~2" style="list-style-type: lower-alpha;~~mark">official tool<li/span>~~Ubuntu22.04 comes with QT version~~ '''~~5.15.3~~, and enter the '''<~~/li~~span class="mark">zfs-related deb package folders used by Ubuntu and Debian systems</olspan>'''. You can see three types of deb packages: Ubuntu20.04, Ubuntu22.04 and Debian11. Please download the required version.

~~orangepi@orangepi~~[[File:~~~$ '''install_qt~~pi3b-img368.~~sh'''~~png]]

After downloading the zfs deb packages of the corresponding version, please upload them to the Linux system of the development board.For the upload method, please refer to '''[[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]].~~....~~'''

~~QMake version 3~~After the upload is complete, use the '''cd''' command in the command line of the development board Linux system to enter the directory of the deb package, and then use the following command to install the deb package of zfs.1

~~Using Qt version~~ {| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''5sudo apt install .15/*.3deb''' ~~in /usr/lib/aarch64-linux-gnu~~|}

~~<ol start="3" style="list~~After the installation is complete, use the following command to see the zfs-~~style-type~~related kernel modules: ~~lower-alpha;"><li>Debian11 comes with QT version '''5.15.2'''</li></ol>~~

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~install_qt~~ls /lib/modules/5.10.sh160-rockchip-rk356x/updates/dkms/'''

'''icp.ko spl.ko zavl.ko zcommon.ko zfs.ko zlua.ko znvpair.ko zunicode.ko zzstd.ko'''|}

~~QMake version 3.1~~Then restart the Linux system to see that the zfs kernel module will be automatically loaded:

~~Using Qt version~~ {| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~5.15.2~~lsmod | grep "zfs"''' ~~in /usr/lib/aarch64-linux-gnu~~

~~<ol start="4" style="list-style-type: lower-alpha~~zfs  ">~~<li>Debian12 comes with QT version '''5.15.8'''</li></ol>~~                   2801664     0

~~orangepi@orangepi:~$ '''install_qt.sh'''~~zunicode             327680     1   zfs

~~......~~zzstd                  471040     1   zfs

~~QMake version 3.~~zlua                    139264     1  zfs

~~Using Qt version '''5.15.8''' in /usr/lib/aarch64-linux-gnu~~zcommon             69632     1   zfs

~~<ol start="3" style="list-style-type: decimal~~znvpair  ">~~<li>Then you can see the QT Creator launch icon in '''Applications'''</li></ol>~~               61440     2   zfs,zcommon

~~[[File:pi3b-img327.png|576x270px]]~~zavl                      16384     1   zfs

~~QT Creator can also be opened using the following command~~icp                     221184     1   zfs

~~orangepi@orangepi:~$ '''qtcreator'''~~spl                       77824     6   zfs,icp,zzstd,znvpair,zcommon,zavl|}

~~'''During~~ In Debian12, the ~~startup~~ default version of ~~QT and QT applications~~zfs is 2.1.11, if so we can install zfs directly through the following ~~error is displayed~~command. Again, ~~ignore it. This error~~ please make sure that the system has ~~no impact on application running~~installed the deb package of the kernel header file before installation.~~'''~~

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~libGL error: failed to create dri screen~~sudo apt install -y zfsutils-linux zfs-dkms'''|}

~~'''libGL error: failed to load driver: rockchip'''~~

~~'''libGL error: failed to create dri screen'''~~=== Methods of creating ZFS pools ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~libGL error: failed~~ ZFS is based on storage pools, we can add multiple physical storage devices to ~~load driver: rockchip~~the pool, and then allocate storage space from this pool.'''

~~<ol start="4" style="list-style-type: decimal;"><li>~~'''The ~~interface after QT Creator~~ following content is ~~opened is as follows~~demonstrated based on the development board connected to an NVMe SSD and a USB flash drive.'''</~~li></ol~~big>|}

~~[[File~~# 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:~~pi3b-img328.png|418x222px]]~~

~~<ol start="5" style="list-style-type~~: ~~decimal;"><li>The QT Creator version is shown below<ol style="list-style-type~~: ~~lower~~[[File:pi3b-~~alpha;"><li>The default version of QT Creator in '''Ubuntu20~~img369.~~04''' is as follows</li></ol></li></ol>~~png]]

~~[[File~~<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:~~pi3b~~800px;" |-~~img329.png~~|~~419x224px]]~~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="24" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The default version of QT Creator in~~ Then execute '''df -h'~~Ubuntu22.04~~'' to see that '''pool1''' is ~~as follows~~mounted to the '''/pool1''' directory</li>{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''df -h''' <~~/ol~~br>

~~[[File:pi3b-img330.png|443x237px]]~~Filesystem                 Size     Used Avail Use% Mounted on

~~<ol start="3" style="list-style-type: lower-alpha~~tmpfs                    1.6G    ">~~<li>The default version of QT Creator in '''Debian11''' is as follows<~~18M 1.6G 2% /~~li>~~run <~~/ol~~br>

~~[[File:pi3b-img331~~/dev/mmcblk0p2     29G     6.~~png|444x238px]]~~0G 22G 22% /

~~<ol start="4" style="list-style-type: lower-alpha~~tmpfs                    7.7G    ">~~<li>The default version of QT Creator in '''Debian12''' is as follows<~~ 46M 7.7G 1% /dev/~~li>~~shm <~~/ol~~br>

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

~~<ol start="6" style="list-style-type: decimal~~tmpfs                 ">~~<li>Then set QT<ol style="list-style-type: lower-alpha~~ ">~~<li>First open '''Help'''-~~&gtnbsp;~~'''About Plugins~~ 7.7G     944K 7.~~.'''</li></ol>~~<7G 1% /~~li>~~tmp <~~/ol~~br>

~~[[File:pi3b-img333.png|573x164px]]~~/dev/mmcblk0p1     1022M     115M 908M 12% /boot

~~<ol start="2" style="list-style-type: lower-alpha~~/dev/zram1                 188M    ">~~<li>Then remove the check box for '''ClangCodeModel'''<~~4.5M 169M 3% /var/~~li>~~log <~~/ol~~br>

~~[[File:pi3b-img334~~tmpfs                    1.~~png|408x254px]]~~6G     80K 1.6G 1% /run/user/1000

'''pool1                    489G     9.3M 489G 1% /pool1''' |}</ol><ol start="35" style="list-style-type: ~~lower-alpha~~decimal;"><li>Use the following command to see that the file system type of pool1 is zfs<p/li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~Restart QT Creator after the Settings are complete~~mount | grep pool1'''~~</li><li>Then make sure that QT Creator uses the GCC compiler, if the default is Clang, change it to GCC</li></ol>~~

pool1 on /pool1 type '''~~Debian12 Please skip this step~~zfs''' (rw,xattr,noacl)|}</ol><ol start="6" style="list-style-type: decimal;"><li>Then we can test copying a file to the ZFS pool</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo cp -v /usr/local/test.mp4 /pool1/'''

~~[[File:pi3b~~'/usr/local/test.mp4' -~~img335~~> '/pool1/test.~~png~~mp4'|~~576x315px]]~~}</ol>

~~[[File:pi3b-img336.png|575x307px]]~~=== Test the data deduplication function of ZFS ===

~~<ol start~~# The data deduplication function of ZFS is disabled by default, we need to execute the following command to enable it::{| class="7wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>You can then open a sample code</li></ol>~~|-| orangepi@orangepi:~$ '''sudo zfs set dedup=on pool1'''|}

~~[[File~~<ol start="2" style="list-style-type: decimal;"><li>Then do a simple test, first enter pool1, and then execute the following command to generate a random file with a size of 1G</li>{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img337.png~~|~~575x312px]]~~orangepi@orangepi:~$ '''cd /pool1/'''

~~<ol start="8" style~~root@orangepi:/pool1$ '''sudo dd if=~~"list-style-type: decimal;"><li>Clicking on the example code will automatically open the corresponding instruction document, you can carefully read the instructions<~~/~~li><~~dev/~~ol>~~urandom of=test.1g bs=1M count=1024'''

~~[[File:pi3b-img338.png|576x218px]]~~1024+0 records in

~~<ol start="9" style="list-style-type: decimal;"><li>Then click '''Configure Project'''</li></ol>~~1024+0 records out

~~[[File~~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:~~pi3b~~800px;" |-~~img339~~| root@orangepi:/pool1$ '''for ((i=0; i<1000; i++)); do sudo cp test.1g $i.test.~~png~~1g; done'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then use '''du -lh''' to see that there are currently 1002G of data in the pool, but in fact the size of the ZFS pool is only '''504GB''' (the total capacity of SSD+U disk), which cannot hold such a large amount of data</li>{| class="wikitable" style="width:800px;" |-|~~575x304px]]~~root@orangepi:/pool1$ '''du -lh'''

1002G|}</ol><ol start="105" style="list-style-type: decimal;"><li>Then ~~click~~ use the ~~green triangle in the lower left corner~~ '''zpool list''' command to ~~compile and run~~ see that only 1.01G is actually occupied, because these 1001 files are all duplicates, indicating that the ~~sample code~~data deduplication function is effective.</li~~></ol~~>

[[File:pi3b-~~img340~~img371.png~~|575x312px~~]]</ol>

~~<ol start~~=~~"11" style~~=~~"list-style-type: decimal;"><li>After waiting for a period~~ = Test the data compression function of ~~time, the interface shown in the following figure will pop up, which indicates that QT can compile and run normally</li></ol>~~ZFS ===

~~[[File:pi3b-img341.png|576x308px]]~~# Because the stored data is different, the disk space saved by compression will also be different, so we choose to compress relatively large plain text files for compression testing, and execute the following commands to pack the '''/var/log/''' and '''/etc/''' directories into a tarball

~~<ol start~~::{| class="12wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Reference documents<~~|-| orangepi@orangepi:~$ '''cd /~~li><~~pool1/~~ol>~~'''

~~https~~root@orangepi:/pool1$ '''sudo tar -cf text.tar /var/log//~~wiki.qt.io~~etc/~~Install_Qt_5_on_Ubuntu~~'''|}

~~https~~<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'''</~~/download.qt.io/archive/qtcreator~~li>

~~https~~[[File:pi3b-img372.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then we enable compression in the ZFS pool pool1</~~download~~li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/pool1$ '''sudo zfs set compression=lz4 pool1'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then execute the following command again to package the '''/var/log/''' and '''/etc/''' directories into a tar package</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/pool1$ '''sudo tar -cf text.tar /var/log/ /etc/'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>At this time, you can see that the size of the '''text.qttar''' file is still 27M, but it only occupies 9.~~io/archive~~47M in the ZFS pool, indicating that the file is compressed</qtli>

[[File:pi3b-img373.png]]</ol>~~== ROS Installation Method ==~~

~~~~=== How to ~~install ROS 1 Noetic on Ubuntu 20.04 =~~shut down and restart the development board ==

# ~~The current active version~~ During the running of ~~ROS 1~~ the Linux system, if the Type-C power supply is ~~as follows~~directly unplugged, some data may be lost or damaged in the file system, so please use the ~~recommended version is~~ '''~~Noetic Ninjemys~~poweroff'''command to shut down the Linux system of the development board before powering off. Then unplug the power again.

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-~~img342.png~~| orangepi@orangepi:~$ '''sudo poweroff'''|~~345x235px]]~~}

~~[[File~~<ol start="2" style="list-style-type:~~pi3b-img343~~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.~~png|576x210px]]~~</li>

[~~http~~[File:~~//docs~~pi3b-img374.~~ros.org/ http://docs.ros.org~~png]]

~~'''https://wiki.ros.org/Distributions'''~~ ~~<ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~The official installation document link of ROS 1~~ '''~~Noetic Ninjemys~~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.''' ~~is as follows:</li>~~</olbig> ~~[http://wiki.ros.org/noetic/Installation/Ubuntu '''http://wiki.ros.org/noetic/Installation/Ubuntu''']~~

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

|}

</ol>

<li>In Short press the ~~official installation document of ROS '''Noetic Ninjemys''', Ubuntu recommends using Ubuntu20.04, so please make sure that the system used by~~ switch button on the development board ~~is '''Ubuntu20~~after shutting down to start up.~~04 desktop system'''~~</li>~~</ol>~~ ~~http://wiki.ros.org/noetic/Installation~~ ~~[[File:pi3b-img344.png|312x176px]]~~

[[File:pi3b-img374.png]]

</ol>

<li>~~Then use~~ The command to restart the ~~script below to install ros1~~Linux system is</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo''' '''reboot'''|}</ol>

~~orangepi@orangepi3b:~$~~ = '''~~install_ros.sh ros1~~Linux SDK——orangepi-build instructions'''=

<~~ol start~~span id="~~5" style="list~~compilation-~~style~~system-~~type: decimal;~~requirements"><li/span>~~Before using the ROS tool, you first need to initialize rosdep, and then you can quickly install some~~ == Compilation system ~~dependencies and some core components in ROS when compiling the source code</li></ol>~~requirements ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~Note that running~~ We can cross-compile the Linux image of the ~~following command needs to ensure that~~ development board on the x64 computer, or compile the Linux image of the development board on the Ubuntu22.04 system of the development board ~~can access github normally~~, ~~otherwise an error will be reported due~~ please choose one according to ~~network problems~~your preference.'''

'''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 github normally, and then manually run the following Order.'''

'''~~https://raw~~If you use orangepi-build to compile the Linux image in the Ubuntu22.~~githubusercontent~~04 system of the development board, please do a good job of cooling (especially when the SSD starts).~~com/ros/rosdistro/master/rosdep/osx-homebrew~~If the heat dissipation is not done well, it is prone to the error of file system runaway.~~yaml~~'''</big>|}

~~'''Hit https://raw.githubusercontent~~</~~base~~span>=== Compile with the Ubuntu22.~~yaml'''~~04 system of the development board ===

# The Linux SDK, namely '''~~ERROR: error loading sources list:~~orangepi-build''', supports running on the '''Ubuntu 22.04''' of the development board (other systems have not been tested), so before downloading orangepi-build, please first ensure that the Ubuntu version installed on the development board is Ubuntu 22.04. The command to check the Ubuntu version installed on the development board is as follows. If the Release field does not display '''22.04''', it means that the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operations.

::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~The read operation timed out~~lsb_release -a'''

~~orangepi@orangepi:~$ '''source /opt/ros/noetic/setup~~No LSB modules are available.~~bash'''~~

~~orangepi@orangepi~~Distributor ID:~~~$ '''sudo rosdep init'''~~Ubuntu

~~Wrote /etc/ros/rosdep/sources~~Description: Ubuntu 22.~~list~~04.~~d/20-default.list~~1 LTS

~~Recommended~~Release: ~~please run~~'''22.04'''

~~rosdep update~~Codename: jammy|}

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~$ decimal;"><li>'''~~rosdep update~~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>

~~reading in sources list data from /etc/ros/rosdep~~</~~sources.list.d~~span>

~~Hit https://raw~~=== Compile with x64 Ubuntu22.~~githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml~~04 computer ===

~~Hit https://raw~~# The Linux SDK, '''orangepi-build''', supports running on computers with '''Ubuntu 22.~~githubusercontent~~04''' installed, so before downloading orangepi-build, please make sure that the Ubuntu version installed on your computer is Ubuntu 22.~~com/ros/rosdistro/master/rosdep/base~~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.~~yaml~~

~~Hit https~~:~~//raw.githubusercontent.com/ros/rosdistro/master/rosdep/python.yaml~~:{| class="wikitable" style="width:800px;" |-| test@test:~$ '''lsb_release -a'''

~~Hit https://raw~~No LSB modules are available.~~githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml~~

~~Hit https~~Distributor ID:~~//raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml~~Ubuntu

~~Query rosdistro index https~~Description:~~//raw~~Ubuntu 22.~~githubusercontent.com/ros/rosdistro/master/index-v4.yaml~~04 LTS

~~Skip end-of-life distro "ardent"~~Release: '''22.04'''

~~Skip end-of-life distro "bouncy"~~Codename: jammy|}

~~Skip end~~<ol start="2" style="list-ofstyle-~~life distro "crystal&quot~~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>

~~Skip end~~{| class="wikitable" style="width:800px;" |-| [https://repo.huaweicloud.com/ubuntu-releases/21.04/ubuntu-21.04-desktop-amd64.iso '''https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ofreleases/22.04/ubuntu-~~life distro "dashing"~~22.04-desktop-amd64.iso''']

~~Skip end-of-life distro "eloquent"~~Or

~~Add distro &quot~~'''https://repo.huaweicloud.com/ubuntu-releases/22.04/ubuntu-22.04.1-desktop-amd64.iso'''|}</ol><ol start="4" style="list-style-type: decimal;~~foxy&quot~~"><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>

~~Add distro &quot~~{| class="wikitable" style="width:800px;~~galactic&quot~~" |-| '''https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Note that the Ubuntu version needs to be switched to 22.04</li>

~~Skip end~~[[File:pi3b-ofimg376.png]]</ol><ol start="3" style="list-style-type: lower-~~life distro "groovy&quot~~alpha;"><li>The content of the '''/etc/apt/sources.list''' file that needs to be replaced is</li>

~~Add distro "humble&quot~~{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo mv /etc/apt/sources.list /etc/apt/sources.list.bak'''

~~Skip end-of-life distro "hydro"~~test@test:~$ '''sudo vim /etc/apt/sources.list'''

~~Skip end-~~# By default, the source image is commented to improve the speed of~~-life distro "indigo"~~apt update, you can uncomment it yourself if necessary

~~Skip end-of-life distro "jade"~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse

~~Skip end~~# deb-~~of-life distro "kinetic"~~src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse

~~Skip end~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-~~of-life distro "lunar"~~updates main restricted universe multiverse

~~Add distro "melodic"~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse

~~Add distro "noetic"~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse

~~Add distro "rolling"~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse

~~updated cache in~~ deb https:/~~home/orangepi~~/mirrors.tuna.tsinghua.edu.~~ros~~cn/~~rosdep~~ubuntu/~~sources.cache~~jammy-security main restricted universe multiverse

~~<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 normallyorangepi@orangepi~~# deb-src https:~~~$ '''test_ros.sh'''<~~/~~p><~~/~~li><li>After running the '''test_ros~~mirrors.tuna.tsinghua.edu.~~sh''' script, a little turtle as shown in the figure below will pop up<~~cn/~~p><~~ubuntu/~~li>~~jammy-security main restricted universe multiverse</olp>

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

~~[[File:pi3b~~# Pre-~~img345.png|575x275px|图片4]]~~release software source, not recommended to enable

<~~/div~~p>~~<ol start="8" style="list-style-type~~# deb https: ~~decimal;"><li>Then please keep the terminal window just opened at the top<~~/~~li>~~/mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse</olp>

<~~div~~ p># deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>After the replacement, you need to update the package information and make sure there is no error</li>{| class="~~figure~~wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt update'''|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>'''In addition, since the source codes such as the kernel and U-boot are stored on GitHub, it is very important to ensure that the computer can download codes from GitHub normally when compiling the image.'''</li></ol></li></ol>

~~[[File:pi3b-img346.png|576x275px|图片5]]~~== Get the source code of Linux sdk ==

<~~/div><ol start~~span id="~~9" style="list~~download-orangepi-build-~~style~~from-~~type: decimal;~~github">~~<li>At this time, press the direction keys on the keyboard to control the little turtle to move up, down, left, and right~~</~~li></ol~~span>=== Download orangepi-build from github ===

~~[[File:pi3b~~# The Linux sdk actually refers to the code of orangepi-build. orangepi-build is modified based on the armbian build system. Using orangepi-~~img347~~build, multiple versions of Linux images can be compiled.~~png|575x296px]]~~First download the code of orangepi-build, the command is as follows:

~~=== How to install ROS 2 Galactic on Ubuntu 20.04 ===~~get update'''

~~# The current active version of ROS 2 is as follows, the recommended version is~~ test@test:~$ '''~~Galactic Geochelone~~sudo apt-get install -y git'''

~~[[File~~test@test:~~pi3b~~~$ '''git clone https://github.com/orangepi-~~img348~~xunlong/orangepi-build.~~png~~git -b next'''|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |~~576x271px]]~~-| <big>'''Note that the Orange Pi 3B development board needs to download the source code of the next branch of orangepi-build. The above git clone command needs to specify the branch of the orangepi-build source code as next.'''</big>

~~[[File:pi3b-img349.png|575x265px]]~~<div class="figure">

[~~http~~[File:~~//docs~~pi3b-img377.~~ros.org~~png|center]] </ ~~http~~div>|}::~~//docs.ros.org]~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~http://docs~~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.~~ros~~Please check the spelling of the command carefully, instead of thinking that we forgot to provide the username and password of the github account.~~org/en/galactic/Releases.html~~'''</big>|}

<li>The ~~link to~~ u-boot and Linux kernel versions currently used by the ~~official ROS 2 '''Galactic Geochelone''' installation documentation is~~ development board are as follows:</li~~></ol~~>

{| class="wikitable" style="width:800px;text-align: center;"|-|'''branch'''|'''u-boot version'''|'''~~docs.ros.org/en/galactic/Installation.html~~Linux Kernel version'''|-|'''legacy'''|'''~~http://docs~~u-boot 2017.~~ros~~09'''|'''Linux5.~~org/en/galactic/Installation/Ubuntu~~10'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-~~Install~~| <big>'''The branch mentioned here is not the same thing as the branch of the orangepi-~~Debians~~build source code, please do not confuse it. This branch is mainly used to distinguish different kernel source code versions.~~html~~'''

'''Currently, the Linux5.10 bsp kernel provided by RK is defined as the legacy branch. If the mainline kernel is supported in the future, a current branch will be added.'''</big>

|}

</ol>

<li>~~It is recommended to use Ubuntu20.04 in~~ orangepi-build will contain the ~~official installation document of ROS 2~~ following files and folders after downloading<ol style="list-style-type: lower-alpha;"><li>'''~~Galactic Geochelone~~build.sh'''~~, so please ensure that~~ : Compile the ~~system used by the development board is~~ startup script</li><li>'''~~Ubuntu20.04 desktop version~~external'''~~. There are several ways~~ : Contains the configuration files needed to ~~install ROS 2~~compile the image, specific scripts, and the source code of some programs, etc. ~~The following shows how to install ROS 2~~ </li><li>'''~~Galactic Geochelone''' using '''Debian packages~~LICENSE''': GPL 2 license file</li><li>README.md: orangepi-build documentation</li><li>~~Use the~~ '''~~install_ros.sh~~scripts''' : General script ~~to install ros2~~for compiling Linux images</li><{| class="wikitable" style="width:800px;" |-| test@test:~/~~ol>~~orangepi-build$ '''ls'''

~~orangepi@orangepi~~'''build.sh      external      LICENSE      README.md      scripts'''|}{| class="wikitable" style="background-color:#ffffdc;width:~$ 800px;" |-| <big>'''~~install_ros~~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.~~sh ros2~~'''</big>|}</ol></li></ol>

~~<ol start~~=~~"5" style~~=~~"list-style-type: decimal;"><li>The '''install_ros.sh''' script will automatically run~~ = Download the ~~'''ros2~~ cross-~~h''' command after installing ros2. If you can see the following print, it means that the ros2 installation is complete</li></ol>~~compilation toolchain ===

~~usage~~{| class="wikitable" style="background-color: ~~ros2 [-h] Call `ros2 &lt~~#ffffdc;~~command&gt~~width:800px; " |-~~h` for more detailed usage~~| <big>'''The cross-compilation toolchain will only be downloaded when the orangepi-build compilation image is used on an x64 computer. Compiling the Linux image of the development board in the Ubuntu22.04 of the development board will not download the cross-compilation toolchain.At this time, orangepi-build/toolchains will be an empty folder.'''</big>|}

~~ros2 is an extensible command~~# When orangepi-~~line tool~~ build runs for ~~ROS 2~~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.

~~optional arguments:~~<div class="figure">

::[[File:pi3b-~~h, --help show this help message and exit~~img378.png]]

~~Commands~~</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://mirrors.tuna.tsinghua.edu.cn/armbian-releases/_toolchain/'''|}</ol><ol start="3" style="list-style-type:decimal;"><li>After '''toolchains''' is downloaded, it will contain multiple versions of cross-compilation toolchains, and the development board will only use two of them</li>~~action Various action related sub~~{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-~~commands~~build$ '''ls toolchains/'''

~~bag Various rosbag related sub~~gcc-~~commands~~arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu

~~component Various component related sub~~gcc-~~commands~~arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf

~~daemon Various daemon related sub~~gcc-~~commands~~arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu

~~doctor Check ROS setup and other potential issues~~gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf

~~interface Show information about ROS interfaces~~gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabi

~~launch Run a launch file~~gcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabihf

~~lifecycle Various lifecycle related sub~~gcc-~~commands~~linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu

~~multicast Various multicast related sub~~gcc-~~commands~~linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabi

~~node Various node related sub~~gcc-~~commands~~linaro-aarch64-none-elf-4.8-2013.11_linux

~~param Various param related sub~~gcc-~~commands~~linaro-arm-linux-gnueabihf-4.8-2014.04_linux

~~pkg Various package related sub~~gcc-~~commands~~linaro-arm-none-eabi-4.8-2014.04_linux|}</ol><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>{| class="wikitable" style="width:800px;" |-| '''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''|}</ol></li></ol><ol start="5" style="list-style-type: decimal;"><li>The cross-compilation tool chain used to compile the u-boot source code is<ol style="list-style-type: lower-alpha;"><li>v2017.09</li>{| class="wikitable" style="width:800px;" |-| '''gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu'''|}</ol></li></ol>

~~run Run a package specific executable~~=== orangepi-build complete directory structure description ===

~~security Various security related sub~~<ol style="list-style-~~commands~~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~~service Various service related sub~~<ol style="list-~~commands~~style-type: lower-alpha;"><li>The git repository where the Linux kernel source code is stored is as follows:</li>~~topic Various topic related sub~~{| class="wikitable" style="width:800px;" |-~~commands~~| ~~wtf Use `wtf` as alias to `doctor`~~'''https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-5.10-rk35xx'''|}</ol>~~Call `ros2 &lt~~<ol start="2" style="list-style-type: lower-alpha;~~command&gt~~"><li>The git warehouse where the b.u-boot source code is stored is as follows:</li>{| class="wikitable" style="width:800px; " |-~~h` for more detailed usage~~| '''https://github.com/orangepi-xunlong/u-boot-orangepi/tree/v2017.09-rk3588'''|}</ol></li></ol><ol start="62" style="list-style-type: decimal;"><li>~~Then you~~ 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 ~~use the~~ be seen in orangepi-build are::a. '''~~test_ros~~build.sh''' : compile startup script :b. '''external''': Contains the configuration files needed to ~~test whether ROS~~ 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 ~~is installed successfully~~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. ~~If you can see~~ 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 ~~following print~~u-boot source code Please do not modify it manually, if it ~~means that ROS 2 can run normally~~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     userpatches'''|}</ol>

~~orangepi@orangepi3b:~$ '''test_ros.sh'''~~== Compile u-boot ==

~~[INFO] [1671174101~~# Run the build.~~200091527] [talker]: Publishing: 'Hello World: 1'~~sh script, remember to add sudo permission

~~[INFO] [1671174101.235661048] [listener]~~: ~~I heard~~: ~~[Hello World~~{| class="wikitable" style="width:800px;" |-| test@test: 1]~/orangepi-build$ '''sudo ./build.sh'''|}

~~[INFO] [1671174102.199572327] [talker]: Publishing~~<ol start="2" style="list-style-type: decimal;"><li>Select '''U-boot package''~~Hello World: 2~~', then enter</li>

~~[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]~~<div class="figure">

[~~INFO]~~ [~~1671174103~~File:pi3b-img379.~~199580322~~png] ~~[talker~~]~~: Publishing: 'Hello World: 3'~~

~~[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]~~</div></ol><ol start="73" style="list-style-type: decimal;"><li>~~Run~~ Then select the model of the ~~following command to open rviz2~~development board</li>~~</ol>~~ ~~orangepi@orangepi:~$ '''source /opt/ros/galactic/setup.bash'''~~ ~~orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''~~

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

</div></ol><ol start="84" style="list-style-type: decimal;"><li>~~For the usage of ROS~~Then it will start to compile u-boot, ~~please refer to the documentation of ROS 2~~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>~~http~~{| 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</~~docs~~li>{| class="wikitable" style="width:800px;" |-| [ o.~~ros~~k.~~org~~] Target directory [ '''orangepi-build/enoutput/~~galactic~~debs/~~Tutorials.html~~u-boot''' ]|}</ol><~~span id~~ol start="~~how~~4" style="list-style-totype: lower-~~install~~alpha;"><li>The package name of the generated u-~~ros~~boot deb package</li>{| class="wikitable" style="width:800px;" |-2| [ o.k. ] File name [ '''linux-~~humble~~u-onboot-~~ubuntu~~legacy-22orangepi3b_1.040.0_arm64.deb''' ]|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Compilation time</~~span~~li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Runtime [ '''1 min''' ]|}</ol><ol start="6" style= ~~How~~ "list-style-type: lower-alpha;"><li>Repeat the command to compile u-boot, use the following command to ~~install ROS 2 Humble on Ubuntu 22~~start compiling u-boot directly without selecting through the graphical interface</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Repeat Build Options [ '''sudo ./build.04 sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=u-boot KERNEL_CONFIGURE=no''' ]|}</ol></li></ol><ol start="5" style="list-style-type: decimal;">~~# Use~~ <li>View the u-boot deb package generated by compilation</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''~~install_ros.sh~~ls output/debs/u-boot/''' ~~script to install ros2~~

~~orangepi~~linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb|}</ol><ol start="6" style="list-style-type: decimal;"><li>The files contained in the generated u-boot deb package are as follows<ol style="list-style-type: lower-alpha;"><li>Use the following command to decompress the deb package</li>{| class="wikitable" style="width:800px;" |-| test@~~orangepi~~test:~/orangepi-build$ '''~~install_ros.sh ros2~~cd output/debs/u-boot'''

~~<ol start="2" style="list-style~~test@test:~/orangepi_build/output/debs/u-~~type: decimal;"><li>The~~ boot$ $ '''~~install_ros.sh''' script will automatically run the '''ros2~~ dpkg -hx''' ~~command after installing ros2. If you can see the following print, it means that the ros2 installation is complete</li></ol>~~\

~~usage: ros2 [~~'''linux-~~h] Call `ros2 <command>~~ u-boot-legacy-~~h` for more detailed usage~~orangepi3b_1. 0.0_arm64.deb .(Note that there is a "." at the end of the command)'''

~~ros2 is an extensible command~~test@test:~/orangepi_build/output/debs/u-~~line tool for ROS 2.~~boot$ '''ls'''

~~optional arguments~~linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb '''usr'''|}</ol><ol start="2" style="list-style-type:lower-alpha;"><li>The decompressed file is as follows</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build/output/debs/u-boot$ '''tree usr'''

~~-h, --help show this help message and exit~~usr

~~Commands:~~└── lib

~~action Various action related sub~~:├── linux-~~commands~~u-boot-legacy-orangepi3b_1.0.0_arm64

~~bag Various rosbag related sub-commands~~:│ ├── idbloader.img

~~component Various component related sub-commands~~:│ ├── rkspi_loader.img

~~daemon Various daemon related sub~~:│ └── u-~~commands~~boot.itb

~~doctor Check ROS setup and other potential issues~~:└── u-boot

~~interface Show information about ROS interfaces~~::├── LICENSE

~~launch Run a launch file~~::├── orangepi-3b-rk3566_defconfig

~~lifecycle Various lifecycle related sub-commands~~::└── platform_install.sh

~~multicast Various multicast related sub-commands~~

~~node Various node related sub~~3 directories, 6 files|}</ol></li></ol><ol start="7" style="list-~~commands~~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>

~~param Various param related sub~~Set the IGNORE_UPDATES variable in userpatches/config-~~commands~~default.conf to "yes"

~~pkg Various package related sub~~{| class="wikitable" style="width:800px;" |-~~commands~~| test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''

~~run Run a~~ IGNORE_UPDATES="'''yes'''"|}</ol><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 ~~specific executable~~to the Linux system of the development board</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''cd output/debs/u-boot'''

~~security Various security related sub~~test@test:~/orangepi_build/output/debs/u-~~commands~~boot$ '''scp \'''

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

~~topic Various topic related sub~~[[File:pi3b-~~commands~~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>

~~wtf Use `wtf` as alias~~ [[File:pi3b-img382.png]]</ol><ol start="7" style="list-style-type: lower-alpha;"><li>Press the Enter key again to ~~`doctor`~~start updating u-boot, and the following information will be displayed after the update is completed</li>

~~Call `ros2 <command>~~ [[File:pi3b-~~h` for more detailed usage~~img383.png]]</ol><ol start="38" style="list-style-type: ~~decimal~~lower-alpha;"><li>Then you can ~~use~~ restart the development board to test whether the modification of u-boot takes effect</li></ol></li></ol><ol start="9" style="list-style-type: decimal;"><li>Other useful information<ol style="list-style-type: lower-alpha;"><li>In the u-boot 2017.09 source code, the defconfig configuration file used by the development board is</li>{| class="wikitable" style="width:800px;" |-| [https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/configs/orangepi_5_defconfig '''~~test_ros~~orangepi-build/u-boot/v2017.sh09-rk3588/configs/orangepi-3b-rk3566_defconfig''' ~~script to test whether ROS~~ ]|}</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 ~~installed successfully~~</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. ~~If you can see the following print, it means that ROS 2 can run normally~~dts''']|}</ol></li></ol>

~~orangepi@orangepi3b:~$ '''test_ros.sh'''~~== Compile the Linux kernel ==

~~[INFO] [1671174101~~# Run the build.~~200091527] [talker]: Publishing: 'Hello World: 1'~~sh script, remember to add sudo permission

~~[INFO] [1671174101.235661048] [listener]~~: ~~I heard~~: ~~[Hello World~~{| class="wikitable" style="width:800px;" |-| test@test: 1]~/orangepi-build$ '''sudo ./build.sh'''|}

~~[INFO] [1671174102.199572327] [talker]: Publishing~~<ol start="2" style="list-style-type: decimal;"><li>Select '''Kernel package''~~Hello World: 2~~', then enter</li>

~~[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]~~<div class="figure">

[~~INFO]~~ [~~1671174103~~File:pi3b-img384.~~199580322~~png] ~~[talker~~]~~: Publishing: 'Hello World: 3'~~

~~[INFO] [1671174103.204019965] [listener]: I heard: [Hello World~~</div></ol><ol start="3" style="list-style-type: 3]decimal;"><li>Then select the model of the development board</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-img380.~~bash'''~~png]]

~~orangepi@orangepi~~</div></ol><ol start="4" style="list-style-type:~~~$ '''ros2 run rviz2 rviz2'''~~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>

~~<div class="figure">~~ [[File:pi3b-~~img351~~img385.png~~|576x324px|1~~]] </~~div~~ol>

<li>~~Reference documents~~If you choose to display the kernel configuration menu (the second option) in step 4), the kernel configuration interface opened by '''make menuconfig''' will pop up. At this time, you can directly modify the kernel configuration, save and exit after modification. Yes, after exiting, the kernel source code will be compiled</li~~></ol~~>

~~'''http~~[[File:~~//docs~~pi3b-img386.~~ros.org/en/humble/index.html'''~~png]]

~~[http~~<ol style="list-style-type:~~//docs~~lower-alpha;"><li>If you do not need to modify the configuration options of the kernel, when running the build.~~ros.org~~sh script, pass in '''KERNEL_CONFIGURE=no''' to temporarily block the pop-up kernel configuration interface</enli>{| class="wikitable" style="width:800px;" |-| test@test:~/~~galactic/Tutorials.html~~ orangepi-build$ '''~~http://docs.ros~~sudo .~~org~~/~~en/humble/Installation/Ubuntu-Install-Debians~~build.~~html~~sh KERNEL_CONFIGURE=no''']|}<~~span id~~/ol><ol start="~~how~~2" style="list-tostyle-~~install~~type: lower-~~kernel~~alpha;"><li>You can also set '''KERNEL_CONFIGURE=no''' in the '''orangepi-~~header~~build/userpatches/config-~~files"~~default.conf''' configuration file, which can permanently disable this function</~~span~~li>~~== How~~ <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 ~~install kernel header files ==~~display the '''make menuconfig''' interface. Please maximize the terminal of the Ubuntu PC and run the build.sh script again</li>

~~# The Linux image released by OPi comes with the deb package of the kernel header file by default, and the storage location is '''/opt/'''~~ ~~orangepi@orangepi~~[[File:~~~$ '''ls /opt/linux-headers*'''~~ ~~/opt/linux-headers-legacy-rockchip~~pi3b-~~rk356x_x.x.x_arm64~~img387.~~deb~~png]]<~~ol start="2" style="list-style-type: decimal;"><li>Use the following command to install the deb package of the kernel header file</li></ol>~~ ~~'''The name of the kernel header file deb package needs to be replaced with the actual name, please do not copy it.'''~~ ~~orangepi@orangepi:~$ '''sudo dpkg -i /opt~~/~~linux-headers-legacy-rockchip-rk356x_1.x.x_arm64.deb'''~~ <ol ~~start="3" style="list-style-type: decimal;"~~>~~<li>After installation, you can see the folder where the kernel header files are located under '''/usr/src'''</li>~~</ol> ~~orangepi@orangepi:~$ '''ls /usr/src'''~~ ~~linux-headers-5.10.160-rockchip-rk356x~~ <ol start="46" style="list-style-type: decimal;"><li>~~Then you can write a hello kernel module to test~~ Part of the information prompted when compiling the kernel ~~header file~~source code is as follows

<li>~~First write the code~~ The version of the ~~hello~~ Linux kernel ~~module, as follows:~~source code</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Compiling current kernel [ '''5.10.160''' ]|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The version of the cross-compilation toolchain used</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Compiler version [ '''aarch64-none-linux-gnu-gcc 11.2.1''' ]|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The configuration file used by the kernel by default and the path where it is stored</li>~~orangepi@orangepi~~{| class="wikitable" style="width:~$ 800px;" |-| [ o.k. ] Using kernel config file [ '''~~vim hello~~config/kernel/linux-rockchip-rk356x-legacy.cconfig''']|}</ol>~~#include &lt~~<ol start="4" style="list-style-type: lower-alpha;~~linux~~"><li>The path of the deb package related to the kernel generated by compiling</~~init~~li>{| class="wikitable" style="width:800px;" |-| [ o.~~h&gt~~k. ] Target directory [ '''orangepi-build/output/debs/''' ]|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>The package name of the compiled kernel image deb package</li>~~#include &lt~~{| class="wikitable" style="width:800px;" |-| [ o.k. ] File name [ '''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb''' ]|}</~~module~~ol><ol start="6" style="list-style-type: lower-alpha;"><li>The time used for compilation</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Runtime [ '''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.~~h&gt~~Use the following command to start compiling the kernel source code directly without selecting through the graphical interface</li>{| class="wikitable" style="width:800px;" |-| ~~static int hello_init(void)~~[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=kernel KERNEL_CONFIGURE=no''' ]|}{</ol></li></ol>~~printk(&quot~~<ol start="7" style="list-style-type: decimal;~~Hello Orange Pi~~ "><li>View the deb package related to the kernel generated by compilation<ol style="list-style- ~~init\n")~~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>~~return~~ <li>'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Contains kernel images and kernel modules</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''ls output/debs/linux-*'''

}output/debs/linux-dtb-legacy-rockchip-rk356x_1.0.0_arm64.deb output/debs/linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb

~~static void hello_exit(void)~~output/debs/linux-headers-legacy-rockchip-rk356x_1.0.0_arm64.deb|}</ol></li></ol><ol start="8" style="list-style-type: decimal;"><li>The files contained in the generated Linux-image deb package are as follows<ol style="list-style-type: lower-alpha;"><li>Use the following command to decompress the deb package</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''cd output/debs'''

{test@test:~/orangepi_build/output/debs$ '''mkdir test'''

~~printk("Hello Orange Pi -- exit~~test@test:~/orangepi_build/output/debs$ '''cp \~~n");~~'''

~~return;~~'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb test/'''

}test@test:~/orangepi_build/output/debs$ '''cd test'''

~~module_init(hello_init);~~test@test:~/orangepi_build/output/debs/test$ '''dpkg -x \'''

~~module_exit(hello_exit);~~'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb .'''

~~MODULE_LICENSE("GPL");~~test@test:~/orangepi_build/output/debs/test$ '''ls'''

'''boot etc lib''' linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb '''usr'''

|}

</ol>

<li>~~Then write the Makefile for compiling the hello kernel module,~~ The decompressed file is as follows:</li><{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build/output/debs/~~ol>~~test$ '''tree -L 2'''

~~orangepi@orangepi:~$ '''vim Makefile'''~~.

~~ifneq ($(KERNELRELEASE),)~~├── boot

~~obj~~│ ├── config-~~m:=hello~~5.o10.160-rockchip-rk356x

~~else~~│ ├── System.map-5.10.160-rockchip-rk356x

~~KDIR :=/lib/modules/$(shell uname~~ │ └── vmlinuz-~~r)/build~~5.10.160-rockchip-rk356x

~~PWD :=$(shell pwd)~~├── etc

~~all:~~│ └── kernel

~~make -C $(KDIR) M=$(PWD) modules~~├── lib

~~clean:~~│ └── modules

rm ├── linux-f *.ko *.o *.mod.o *.mod *.symvers *.cmd *image-legacy-rockchip-rk356x_1.~~mod~~0.c *0_arm64.~~order~~deb

~~endif~~└── usr

~~<ol start="3" style="list-style-type~~: ~~lower-alpha;"><li>Then use the make command to compile the hello kernel module. The output of the compilation process is as follows:</li></ol>~~├── lib

~~'''If there is a problem~~ :└── 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 ~~copied here~~want to modify the Linux kernel source code, ~~please go~~ you first need to turn off the ~~official tool~~ update function of the source code '''(you need to ~~download~~ compile it once This function can only be turned off after the Linux kernel source code ~~and upload~~ , otherwise it to will prompt that the ~~Linux system~~ source code of the ~~development board for testing~~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>

~~[[File:pi3b~~Set the IGNORE_UPDATES variable in '''userpatches/config-~~img352~~default.~~png|337x52px]]~~conf''' to "yes"

~~orangepi~~{| class="wikitable" style="width:800px;" |-| test@~~orangepi~~test:~/orangepi-build$ '''~~make~~vim userpatches/config-default.conf'''

~~make -C~~ IGNORE_UPDATES="'''yes</~~lib~~span>'''"|}</ol><ol start="10" style="list-style-type: decimal;"><li>If the kernel has been modified, the following method can be used to update the kernel and kernel modulesof the development board Linux system</~~5.10.160~~p><ol style="list-style-~~rockchip~~type: lower-~~35xx~~alpha;"><li>Upload the deb package of the compiled Linux kernel to the Linux system of the development board</~~build M~~li>{| class="wikitable" style="width:800px;" |-| test@test:~/~~home~~orangepi-build$ '''cd output/~~orangepi modules~~debs'''

~~make[1]~~test@test: ~~Entering directory '~~~/~~usr~~orangepi-build/~~src~~output/~~linux-headers-5.10.160-rockchip-rk35xx~~debs$ '''scp \'''

CC '''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 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;" |-| [Mhttps://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/~~home~~boot/dts/rockchip/rk3588s-orangepi-5.dts '''orangepi-build/kernel/~~hello~~orange-pi-5.o10-rk35xx/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dts''']|}</ol></li></ol>

~~MODPOST /home/orangepi/Module.symvers~~== Compile rootfs ==

~~CC [M] /home/orangepi/hello~~# Run the build.~~mod.o~~sh script, remember to add sudo permission

~~LD [M] /home~~::{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''sudo ./~~hello~~build.kosh'''|}

~~make[1]~~<ol start="2" style="list-style-type: ~~Leaving directory~~ decimal;"><li>Select '''Rootfs and all deb packages''', then enter</~~usr/src/linux-headers-5.10.160-rockchip-rk35xx'~~li>

<~~ol start~~div class="4figure" ~~style="list-style-type: lower-alpha;"><li>After compiling, the '''hello.ko''' kernel module will be generated</li></ol~~>

~~orangepi@orangepi~~[[File:~$ '''ls *pi3b-img388.~~ko'''~~png]]

~~hello.ko~~</div></ol><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li>

<~~ol start~~div class="5figure" ~~style="list-style-type: lower-alpha;"><li>Use the '''insmod''' command to insert the '''hello.ko''' kernel module into the kernel</li></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''sudo insmod hello~~pi3b-img380.~~ko'''~~png]]

</div></ol><ol start="64" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~use~~ select the ~~'''demsg''' command to view the output~~ type of ~~the '''hello.ko''' kernel module. If you can see the output below, it means that the '''hello.ko''' kernel module is loaded correctly.~~rootfs</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img389.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then select the type of image<ol style="list-style-type: lower-alpha;"><li>'''Image with console interface (server)''' Indicates the image of the server version, which is relatively small</li><li>'''~~dmesg | grep "Hello"~~Image with desktop environment'''Indicates a image with a desktop, which is relatively large</li>

~~[ 2871.893988] '''Hello Orange Pi -- init'''~~<div class="figure">

~~<ol start="7" style="list-style-type~~[[File: ~~lower~~pi3b-~~alpha;"><li>Use the '''rmmod''' command to uninstall the '''hello~~img390.~~ko''' kernel module</li></ol>~~png]]

~~orangepi@orangepi~~</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 '''~~sudo rmmod hello~~(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>

~~orangepi@orangepi:~$ '''dmesg | grep "Hello"'''~~<div class="figure">

[ ~~2871~~[File:pi3b-img391.~~893988~~png]] ~~Hello Orange Pi -- init~~

~~[ 3173.800892] '''Hello Orange Pi~~ </div></ol><ol start="7" style="list-style- ~~exit'''~~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>

<~~span id~~div class="~~use-of-the-raspberry-pis-5-inch-screen~~figure">~~== Use of the Raspberry PI's 5-inch screen ==~~ ~~=== Assembly method of Raspberry PI 5-inch screen ===~~

~~<ol style="list-style-type: decimal;"><li>First prepare the required accessories<ol style="list-style-type~~[[File: ~~lower-alpha;"><li>Raspberry PI 5~~pi3b-~~inch MIPI LCD display + touch screen</li></ol></li></ol>~~img392.png]]

<~~blockquote~~/div>[[File:pi3b-~~img353~~img393.png~~|306x219px~~]]~~</blockquote><ol start="2" style="list-style-type: lower-alpha;"><li>15pin MIPI cable</li></ol>~~

~~<blockquote>[[File:pi3b-img354~~You can then select additional packages that need to be installed.~~png|276x111px]]</blockquote><ol start="2" style="list-style-type: decimal;"><li>Then connect~~ Please press the ~~15pin MIPI cable~~ Enter key to ~~the Raspberry PI 5-inch screen in the way shown below (note the orientation of the insulation surface)</li></ol>~~skip directly here.

[[File:pi3b-~~img355~~img394.png~~|294x160px~~]] </ol ~~start="3" style="list-style-type: decimal;"~~><~~li>Finally connect to the LCD interface of the Orange Pi 3B development board</li></~~ol> ~~[[File:pi3b-img356.png|333x199px]]~~ ~~=== Open the Raspberry PI 5-inch screen configuration method ===~~ ~~<ol~~ style="list-style-type: decimal;"><li>~~The Linux image does not open the 5-inch screen of the Raspberry PI by default. If you need~~ Then it will start to ~~use the 5-inch screen~~ compile rootfs, and some of the ~~Raspberry PI, you need to open it manually.</li><li>The steps to open the mipi lcd configuration~~ information prompted during compilation are as follows:

<li>~~First run '''orangepi-config''', ordinary users remember to add '''sudo''' permission~~The type of rootfs</li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-| ~~orangepi@orangepi:~$~~ [ o.k. ] local not found [ Creating new rootfs cache for '''~~sudo orangepi-config~~jammy''']|}</ol>

<li>~~Then select '''System'''~~The storage path of the compiled rootfs compressed package</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| [~~[File:pi3b-img357~~o.k.~~png|575x272px~~]Target directory [ '''external/cache/rootfs''' ]|}</ol>

<li>~~Then select~~ 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 [ '''~~Hardware~~13 min''']|}</ol></li></ol><ol start="9" style="list-style-type: decimal;"><li>View the rootfs compressed package generated by compilation<ol style="list-style-type: lower-alpha;"><li>'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' is the 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</li><li>b) '''xfce''' means rootfs is the type of desktop version, if it is '''cli''', it means the type of server version</li><li>c) '''arm64''' represents the architecture type of rootfs</li><li>d) '''f930ff6ebbac1a72108a2e100762b18f''' is the MD5 hash value generated by the package names of all software packages installed by rootfs. As long as the list of software packages installed by rootfs is not modified, this value will not change. The compilation script will use this MD5 hash value to generate Determine whether rootfs needs to be recompiled</li></ol></li><li>'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.list''' lists the package names of all packages installed by rootfs</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''ls external/cache/rootfs/'''

~~[[File:pi3b~~'''jammy-~~img358~~xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.~~png|576x266px]]~~lz4'''

~~<ol start="4" style="list~~jammy-~~style~~xfce-~~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></ol>~~arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.current

~~[[File:pi3b~~jammy-xfce-~~img359~~arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.~~png~~list|~~408x310px]]~~}</ol></li></ol><ol start="10" style="list-style-type: decimal;"><li>If the required rootfs already exists under '''external/cache/rootfs''', then compiling rootfs again will directly skip the compilation process and will not restart the compilation. When compiling the image, it will also go to '''external/cache/rootfs''' to find out whether it has If there is rootfs available in the cache, use it directly, which can save a lot of download and compilation time.</li></ol>

<~~ol start~~span id="~~5" style="list~~compile-~~style~~linux-~~type: lower-alpha;~~image">~~<li>Then select '''<Save>''' to save</li~~></olspan>

~~[[File:pi3b-img360.png|404x133px]]~~== Compile Linux image ==

~~<ol start="6" style="list-style-type: lower-alpha;"><li>Then select '''<Back>'''</li></ol>~~# Run the build.sh script, remember to add sudo permission

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-~~img361~~build$ '''sudo ./build.~~png~~sh'''|~~397x151px]]~~}

<ol start="72" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then select~~ Select '''~~<Reboot>~~Full OS image for flashing''' ~~to restart the system for the configuration to take effect~~, then enter</li~~></ol~~>

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

'''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.''' ~~'''If you find it troublesome to use orangepi-config, you can also use the vim editor to open /boot/orangepiEnv.txt, and then add the configuration of overlays=raspi-7inch~~[[File:pi3b-~~touchscreen is also possible~~img395.~~'''~~ ~~orangepi@orangepi:~$ '''cat /boot/orangepiEnv.txt | grep "raspi"'''~~ ~~'''overlays=raspi-7inch-touchscreen #Sample configuration'''~~png]]

</div></ol>

<li>~~After startup, you can see~~ Then select the ~~lcd screen display as follows:~~model of the development board</li~~></ol~~>

~~[[File:pi3b-img363.png|381x262px]]~~<div class="figure">

~~=== The method of server version image rotation display direction ===~~img380.png]]

~~# Add '''extraargs~~</div></ol><ol start=~~fbcon~~"4" style=~~rotate~~"list-style-type:decimal;"><li>Then select the ~~direction to rotate''' in '''/boot~~type of rootfs</~~orangepiEnv.txt''' This line configuration can set the direction displayed by the server version of the Linux system, where the number after '''fbcon=rotate:''' can be set as:~~li>

[[File:pi3b-img389.png]]</ol><~~!--~~ ol start="5" style="list-style-type: decimal;"><li>Then select the type of image

<li>~~0: normal screen~~ '''Image with console interface (~~default~~ server)''' Indicates the image of the server version, which is ~~landscape)~~relatively small</li><li>~~1: Turn clockwise 90 degrees</li><li>2: Flip 180 degrees</li><li>3: Turn clockwise 270 degrees~~'''Image with desktop environment''' Indicates a image with a desktop, which is relatively large</li~~></ol~~>

~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''~~<div class="figure">

~~overlays=lcd1~~[[File:pi3b-img390.png]]

</div></ol></li></ol><ol start="6" style="list-style-type: decimal;"><li>If you are compiling the image of the server version, you can also choose to compile the Standard version or the Minimal version. The pre-installed software of the Minimal version will be much less than that of the Standard version '''~~extraargs=cma=64M fbcon=rotate:3~~(please do not choose the Minimal version if there is no special requirement, because many things are not pre-installed by default. Some functions may not be available)'''</li>

~~'''Note that if there is the line extraargs~~<div class=~~cma=64M in /boot/orangepiEnv.txt by default, the configuration fbcon=rotate:3 can be added after extraargs=cma=64M (separated by spaces).'''~~"figure">

~~<ol start="2" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Then '''restart''' the Linux system and you can see that the direction displayed on the LCD screen has been rotated</li></ol>~~img391.png]]

<~~span id~~/div></ol><ol start="7" style="~~method~~list-ofstyle-~~rotating-display-and-touch-direction-of-desktop-version-image~~type: decimal;"><~~/span~~li>~~=== Method~~ If you are compiling the image of ~~rotating display and touch direction~~ the desktop version, you also need to select the type of desktop ~~version image ===~~environment. Currently, Ubuntu Jammy mainly maintains XFCE and Gnome desktops, Ubuntu Focal only maintains XFCE desktops, and Debian Bullseye mainly maintains XFCE and KDE desktops</li>

~~# First open '''Display''' Settings in Linux~~<div class="figure">

[[File:pi3b-~~img364~~img392.png~~|298x206px~~]]

~~<ol start="2" style="list-style-type: decimal;"><li>Then select the direction you want to rotate in '''Rotation'''~~</pdiv>~~<ol style="list-style-type~~[[File: ~~lower~~pi3b-~~alpha;"><li>'''None''': no rotation</li><li>'''Left''': rotate left 90 degrees</li><li>'''Inverted''': Flip up and down, which is equivalent to rotating 180 degrees</li><li>'''Right''': rotate right 90 degrees</li></ol></li></ol>~~img393.png]]

~~[[File:pi3b-img365~~You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.~~png|286x180px]]~~

~~<ol start="3" style="list-style-type: decimal;"><li>Then click '''Apply'''</li></ol>~~ [[File:pi3b-~~img366~~img394.png~~|330x207px~~]] ~~<ol start="4" style="list-style-type: decimal;"><li>Then select '''Keep this configuration'''</li>~~</ol> ~~[[File:pi3b-img367.png|374x210px]]~~ <ol start="58" style="list-style-type: decimal;"><li>~~At this point, the screen display has been rotated, and then close the '''Display''' program</li><li>The above steps~~ Then it will ~~only select the display direction, and will not rotate the direction of~~ start to compile the ~~touch~~Linux image. ~~Use the '''set_lcd_rotate.sh''' script to rotate the direction~~ The general process of ~~the touch. After the script~~ compilation is ~~set, it will automatically restart, and then you can test whether the touch has been used normally.~~as follows

<li>~~'''None''': no rotation~~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<olstyle="list-style-type: lower-alpha;"><li>The storage path of the compiled image</li>~~orangepi@orangepi~~{| class="wikitable" style="width:~$ 800px;" |-| [ o.k. ] Done building [ '''~~set_lcd_rotate~~output/images/Orangepi3b_1.~~sh none~~0.0_debian_bullseye_desktop_xfce_linux5.10.160/Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160.img''']|}</ol>

<li>~~'''Left''': rotate left 90 degrees~~Compilation time</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| ~~orangepi@orangepi:~$~~ '''~~set_lcd_rotate~~[ o.k.~~sh left~~] Runtime [ 19 min ]'''|}</ol>

<li>Repeat the command to compile the image, and use the following command to start compiling the image directly without selecting through the graphical interface</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Repeat Build Options [ '''~~Inverted~~sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=image RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=yes'''~~: Flip up and down, which is equivalent to rotating 180 degrees~~]|}</ol></li></ol>

~~orangepi@orangepi:~$~~ = '''~~set_lcd_rotate.sh inverted~~Android 11 operating system instructions'''=

<~~ol start~~span id="~~4" style="list-style~~supported-~~type: lower~~android-~~alpha;~~versions">~~<li>'''Right''': rotate right 90 degrees~~</~~li></ol~~span>== Supported Android versions ==

~~orangepi@orangepi~~{| class="wikitable" style="width:~$ 800px;text-align: center;"|-|'''Android version'''|'''Kernel version'''|-|'''Android 11'''|'''~~set_lcd_rotate~~Linux4.~~sh right~~19'''|}

~~'''The set_lcd_rotate.sh script mainly does four things:'''~~

~~'''1. Rotate the direction displayed by the framebuffer'''~~== Android Function Adaptation ==

{| class="wikitable" style="width:800px;text-align: center;"|-|'''Functions'''|'~~2. Rotate the direction of the touch~~''Android 11'''|-|'''3USB2. ~~Turn off the boot logo~~0x3'''|'''OK'''|-|'''4USB3. ~~Restart the system~~0x1'''|'''OK'''|-|'''Rotating the touch direction is achieved by adding the line Option "TransformationMatrix" "x x x x x x x x x" to /usr/share/X11/xorg.conf.d/40-libinput.conf Where "x x x x x x x x x" is configured differently for different directionsM.2 NVMe SSD boot'''|'''OK'''~~<ol start="7" style="list~~|-~~style-type: decimal;"><li>Touch rotation reference</li></ol>~~|'''WIFI'''|'''OK'''|-~~https://wiki.ubuntu.com/X/InputCoordinateTransformation~~|'''Bluetooth'''|'''OK'''~~== Instructions for using the switch logo ==~~|'''GPIO（40pin）'''|'''OK'''|-~~# By default, the switch logo will only be displayed in the desktop version of the system~~|'''UART（40pin）'''~~# Set the~~ |'''~~bootlogo~~OK''' ~~variable to~~ |-|'''~~false~~SPI（40pin）''' in |'''~~/boot/orangepiEnv.txt~~OK''' ~~to turn off the switch logo~~|-~~orangepi@orangepi:~$~~ |'''~~vim /boot/orangepiEnv.txt~~I2C（40pin）'''|'''OK'''~~verbosity=1~~|-|'''PWM（40pin）'''|'''~~bootlogo=false~~OK''' ~~<ol start="3" style="list-style~~|-~~type: decimal;"><li>Set the~~ |'''~~bootlogo~~PWM fan interface''' ~~variable to~~ |'''~~true~~OK''' in |-|'''~~/boot/orangepiEnv.txt~~3pin Debugging serial port''' ~~to enable the switch logo</li></ol>~~ ~~orangepi@orangepi:~$~~ |'''~~vim /boot/orangepiEnv.txt~~OK'''|-~~verbosity=1~~|'''EMMC'''|'''~~bootlogo=true~~OK''' ~~<ol start="4" style="list-style~~|-~~type: decimal;"><li>The location of the~~ |'''TF card boot ~~logo image in the Linux system is</li></ol>~~'''|'''OK'''|-|'''~~/usr/share/plymouth/themes/orangepi/watermark.png~~HDMI video'''|'''OK'''~~<ol start="5" style="list~~|-~~style-type: decimal;"><li>After replacing the boot logo picture, you need to run the following command to take effect</li></ol>~~|'''HDMI Audio'''|'''OK'''|-~~orangepi@orangepi:~$~~ |'''~~sudo update-initramfs -u~~LCD'''|'''OK'''~~== How to use the ZFS file system ==~~|'''eDP display'''|'''~~The latest version of Ubuntu20.04, Ubuntu22.04, Debian11 and Debian12 desktop version systems have pre-installed zfs, you can use it directly.~~OK'''|-|'''~~The pre-installed zfs version in Ubuntu20.04 and Ubuntu22.04 desktop systems is 2.1.6.~~Gigabit network port''' |'''~~The pre-installed zfs version in Debian11 and Debian12 desktop systems is 2.1.11.~~OK'''|-|'''~~After the system starts, please first confirm whether the zfs kernel module has been loaded. If you can see zfs-related content using the lsmod command, it means that the system has pre-installed zfs.~~Network port status indicator''' ~~orangepi@orangepi:~$~~ |'''~~lsmod | grep "zfs"~~OK'''|-~~zfs 2801664 0~~|'''Headphone playback'''|'''OK'''~~zunicode 327680 1 zfs~~|-|'''Headphone recording'''~~zzstd 471040 1 zfs~~|'''OK'''|-~~zlua 139264 1 zfs~~|'''LED Light'''|'''OK'''~~zcommon 69632 1 zfs~~|-|'''GPU'''~~znvpair 61440 2 zfs,zcommon~~|'''OK'''|-~~zavl 16384 1 zfs~~|'''NPU'''|'''OK'''~~icp 221184 1 zfs~~|-|'''VPU'''~~spl 77824 6 zfs,icp,zzstd,znvpair,zcommon,zavl~~|'''OK''' ~~=== How to install ZFS ===~~|'''RTC'''|'''~~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.~~OK'''|}

~~Before installing zfs, you need to install the kernel header file first. For the~~

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.== WIFI connection test method ==

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 # First click enter ~~the~~ '''~~zfs-related deb package folders used by Ubuntu and Debian systems~~Setting'''~~. You can see three types of deb packages: Ubuntu20.04, Ubuntu22.04 and Debian11. Please download the required version.~~

::[[File:pi3b-~~img368~~img396.png~~|230x93px~~]]

~~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~~ <ol start="2" style="list-style-type: decimal;"><li>Then select '''~~[[\l|the description in the section of the method of uploading files to the Linux system of the development board]].~~Network & internet'''</li>

~~After the upload is complete, use the~~ [[File:pi3b-img397.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then select '''cdWi-Fi''' ~~command in the command line of the development board Linux system to enter the directory of the deb package, and then use the following command to install the deb package of zfs.~~</li>

~~orangepi@orangepi~~[[File:~$ pi3b-img398.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then turn on the '''~~sudo apt install ./*.deb~~Wi-Fi'''switch</li>

[[File:pi3b-img399.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>After ~~the installation~~ turning on '''Wi-Fi''', if everything is ~~complete~~normal, ~~use the following command to see the zfs~~you can scan for nearby Wi-~~related kernel modules:~~Fi hotspots</li>

~~orangepi@orangepi~~[[File:~~~$ '''ls~~ pi3b-img400.png]]</~~lib/modules/5.10.160~~ol><ol start="6" style="list-style-~~rockchip~~type: decimal;"><li>Then select the Wi-~~rk356x/updates/dkms~~Fi you want to connect to, and the password input interface shown in the figure below will pop up</~~'''~~li>

~~'''icp~~[[File:pi3b-img401.~~ko spl.ko zavl.ko zcommon.ko zfs.ko zlua.ko znvpair.ko zunicode.ko zzstd.ko'''~~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>

~~Then restart~~ [[File:pi3b-img402.png]]</ol><ol start="8" style="list-style-type: decimal;"><li>After the Wi-Fi connection is successful, the ~~Linux system to see that~~ display is as shown in the ~~zfs kernel module will be automatically loaded~~figure below:</li>

~~orangepi@orangepi~~[[File:~~~$ '''lsmod | grep "zfs"'''~~pi3b-img403.png]]</ol>

~~zfs 2801664 0~~== How to use Wi-Fi hotspot ==

~~zunicode 327680 1 zfs~~# First, please make sure that the Ethernet port is connected to the network cable and can access the Internet normally# Then select '''Settings'''

~~zzstd 471040 1 zfs~~::[[File:pi3b-img396.png]]

~~zlua 139264 1 zfs~~<ol start="3" style="list-style-type: decimal;"><li>Then select '''Network & internet'''</li>

~~zcommon 69632 1 zfs~~[[File:pi3b-img397.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select '''Hotspot & tethering'''</li>

~~znvpair 61440 2 zfs,zcommon~~[[File:pi3b-img404.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then select '''Wi-Fi hotspot'''</li>

~~zavl 16384 1 zfs~~[[File:pi3b-img405.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then turn on the '''Wi-Fi hotspot''', you can also see the name and password of the generated hotspot in the figure below, remember them, and use them when connecting to the hotspot (if you need to modify the name and password of the hotspot, you need to turn off the Wi-Fi first -Fi hotspot before modification)</li>

~~icp 221184 1 zfs~~[[File:pi3b-img406.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>At this time, you can take out your mobile phone. If everything is normal, you can find the 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>

~~spl 77824 6 zfs~~[[File:pi3b-img407.png]]</ol><ol start="8" style="list-style-type: decimal;"><li>After the connection is successful,~~icp~~it will be displayed as shown in the figure below (the interface of different mobile phones will be different,~~zzstd~~the specific interface is subject to the display of your mobile phone). At this point,~~znvpair~~you can open a webpage on your mobile phone to see if you can access the Internet. If you can open the webpage normally,~~zcommon,zavl~~it means that the '''WI-FI Hotspot''' of the development board can be used normally.</li>

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[[File:pi3b-img408.png]]</ol>

~~orangepi@orangepi:~$ '''sudo apt install -y zfsutils-linux zfs-dkms'''~~== Bluetooth test method ==

~~=== Methods of creating ZFS pools ===~~# First click enter '''Setting'''

~~'''ZFS is based on storage pools, we can add multiple physical storage devices to the pool, and then allocate storage space from this pool.'''~~ ~~'''The following content is demonstrated based on the development board connected to an NVMe SSD and a USB flash drive.'''~~ ~~# First, we can use the '''lsblk''' command to view all storage devices on the development board. The current development board is connected to an NVMe SSD and a U disk. The output is as follows~~: :[[File:pi3b-~~img369~~img396.png~~|379x227px~~]]

<li>Then ~~enter the following command to create a ZFS pool, including two storage devices, NVMe SSD and U disk</li></ol>~~ ~~orangepi@orangepi:~$~~ select '''~~sudo zpool create -f pool1 /dev/nvme0n1 /dev/sda~~Connected devices'''</li>

[[File:pi3b-img409.png]]

</ol>

<li>Then ~~use the~~ click '''~~zpool list~~Pair new device''' ~~command~~ to ~~see that the system has created a ZFS pool named '''pool1''',~~ turn on Bluetooth and start scanning the ~~size of the ZFS pool pool1 is the size of the NVME SSD plus the size of the U disk~~surrounding Bluetooth devices</li>~~</ol>~~ ~~[[File:pi3b-img370.png|576x37px]]~~

[[File:pi3b-img410.png]]

</ol>

<li>~~Then execute~~ The searched Bluetooth devices will be displayed under '''~~df -h~~Available devices''' ~~to see that '''pool1''' is mounted to the '''/pool1''' directory~~</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img411.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then click the Bluetooth device you want to connect to start pairing. When the following interface pops up, please use the mouse to select the '''~~df -h~~Pair'''option</li>

~~Filesystem Size Used Avail Use% Mounted~~ [[File:pi3b-img412.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>The test here is the configuration process of the development board and the Bluetooth of the Android mobile phone. At this time, the following confirmation interface will pop up onthe mobile phone. After clicking the pairing button on the mobile phone, the pairing process will start</li>

~~tmpfs 1~~[[File:pi3b-img413.~~6G 18M 1.6G 2%~~ png]]</ol><ol start="7" style="list-style-type: decimal;"><li>After the pairing is completed, you can see the paired Bluetooth device as shown in the figure below</~~run~~li>

[[File:pi3b-img414.png]]</~~dev/mmcblk0p2 29G 6~~ol><ol start="8" style="list-style-type: decimal;"><li>At this time, you can use the Bluetooth of your mobile phone to send a picture to the development board. After sending, you can see the following confirmation interface in the Android system of the development board, and then click '''Accept''' to start receiving the picture sent by the mobile phone.~~0G 22G 22%~~ </li>

~~tmpfs 7~~[[File:pi3b-img415.~~7G 46M 7.7G 1%~~ png]]</~~dev~~ol><ol start="9" style="list-style-type: decimal;"><li>You can open the '''Download''' directory in the file manager to view the pictures received by the Android system Bluetooth of the development board</~~shm~~li>

~~tmpfs 5~~[[File:pi3b-img416.~~0M 4.0K~~ png]]</ol></~~lock~~span>

~~tmpfs 7.7G 944K 7.7G 1% /tmp~~== How to use Raspberry Pi 5-inch screen ==

~~/dev/mmcblk0p1 1022M 115M 908M 12% /boot~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Please make sure that the image used is the following two versions of the image:'''

~~/dev/zram1 188M 4~~'''OrangePi3B_RK3566_Android11_lcd_v1.~~5M 169M 3% /var/log~~x.x.img'''

~~tmpfs 1~~'''OrangePi3B_RK3566_Android11_spi-nvme_lcd_v1.~~6G 80K 1~~x.~~6G 1% /run/user~~x.img'''</~~1000~~big>|}

# The screen needs to be assembled first, please refer to [[Orange Pi 3B#Use of the Raspberry PI's 5-inch screen|''~~pool1 489G 9.3M 489G 1% /pool1~~'the assembly method of the Raspberry Pi 5-inch screen''']]# Connect the Type-C power supply to the board and power it on. After the system starts, you can see the screen display as shown in the figure below

~~<ol start="5" style="list~~::[[File:pi3b-~~style-type: decimal;"><li>Use the following command to see that the file system type of pool1 is zfs</li></ol>~~img417.png]]

~~orangepi@orangepi:~$ '''mount | grep pool1'''~~

~~pool1 on /pool1 type '''zfs''' (rw~~== 40pin interface GPIO,~~xattr~~UART,~~noacl)~~SPI and PWM test ==

<~~ol start~~span id="~~6" style="list~~pin-gpio-port-~~style~~test-~~type: decimal;~~2"><li/span>~~Then we can~~ === 40pin GPIO port test ~~copying a file to the ZFS pool</li></ol>~~===

~~orangepi@orangepi:~$ '''sudo cp -v /usr/local/test.mp4 /pool1/'''~~ ~~'/usr/local/test.mp4' -> '/pool1/test.mp4'~~ ~~=== Test~~ wiringOP icon to open the ~~data deduplication function of ZFS ===~~wiringOP APP

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

<li>~~Then do a simple test, first enter pool1~~The main interface of wiringOP APP is displayed as shown in the figure below, and then ~~execute~~ click the ~~following command to generate a random file with a size of 1G</li></ol>~~ ~~orangepi@orangepi:~$~~ '''~~cd /pool1/~~GPIO_TEST''' ~~root@orangepi:/pool1$ '''sudo dd if=/dev/urandom of=~~button to open the GPIO test~~.1g bs=1M count=1024'''~~ ~~1024+0 records in~~ ~~1024+0 records out~~ ~~1073741824 bytes (1.1 GB, 1.0 GiB) copied, 5.04367 s, 213 MB~~interface</sli>

[[File:pi3b-img419.png]]

</ol>

<li>~~Then use~~ The GPIO test interface is shown in the figure below. The two rows of '''CheckBox''' buttons on the left are in one-to-one correspondence with the 40pin pins. When the '''CheckBox''' button is checked, the ~~following command~~ corresponding GPIO pin will be set to ~~copy 1000 random files of size 1G</li></ol>~~ ~~root@orangepi:/pool1$~~ '''~~for ((i=0~~OUT''' mode, and the pin level will be set to high level; ~~i&lt~~when the checkbox is unchecked, the GPIO pin level will be set to low level;~~1000~~When the '''GPIO READALL''' button is pressed, information such as wPi number, GPIO mode, and pin level can be obtained; ~~i++)); do sudo cp test.1g $i.test.1g; done~~when the '''BLINK ALL GPIO'''button is clicked, the program will control the 28 GPIO ports to continuously switch between high and low levels</li>

[[File:pi3b-img420.png]]

</ol>

<li>Then ~~use~~ click the '''~~du -lh~~GPIO READALL''' ~~to see that there are currently 1002G of data in the pool~~button, ~~but in fact the size of~~ the ~~ZFS pool~~ output information is ~~only '''504GB''' (~~as shown in the ~~total capacity of SSD+U disk), which cannot hold such a large amount of data~~figure below:</li~~></ol~~>

~~root@orangepi~~[[File:pi3b-img421.png]]</~~pool1$~~ ol><ol start="5" style="list-style-type: decimal;"><li>There are a total of 28 GPIO ports in the 40pins of the development board that can be used. The following uses pin 7—the corresponding GPIO is GPIO4_A4—the corresponding wPi serial number is 2—as an example to demonstrate how to set the high and low levels of the GPIO port. First click the '''~~du -lh~~CheckBox'''button corresponding to pin 7. When the button is selected, pin 7 will be set to high level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is 3.3v, it means setting high level success</li>

~~1002G~~[[File:pi3b-img422.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is '''OUT''', and the pin level is high</li>

[[File:pi3b-img423.png]]</ol><ol start="57" style="list-style-type: decimal;"><li>~~Then use~~ Click the '''~~zpool list~~CheckBox''' ~~command~~ button in the figure below again to cancel the check status. Pin 7 will be set to ~~see that only 1~~low level. After setting, you can use a multimeter to measure the voltage value of the pin.~~01G~~ If it is ~~actually occupied, because these 1001 files are all duplicates~~'''0v''', ~~indicating~~ it means that the ~~data deduplication function~~ low level is ~~effective~~set successfully.</li~~></ol~~>

[[File:pi3b-~~img371~~img424.png~~|576x36px~~]]</ol><ol start="8" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is OUT, and the pin level is low</li>

[[File:pi3b-img425.png]]</ol>~~=== Test the data compression function of ZFS ===~~

# Because the stored data is different, the disk space saved by compression will also be different, so we choose to compress relatively large plain text files for compression testing, and execute the following commands to pack the '''/var/log/''' and '''/etc/''' directories into a tarball=== 40pin UART test ===

~~orangepi@orangepi:~$~~ # UART7 and UART9 are enabled by default in Android. The position of the 40pin is shown in the figure below, and the corresponding device nodes are '''cd /~~pool1~~dev/ttyS7'''and '''/dev/ttyS9''' respectively

~~root@orangepi~~:~~/pool1$ '''sudo tar~~ :[[File:pi3b-~~cf text~~img269.~~tar /var/log/ /etc/'''~~png]]

<li>~~Then~~ First click on the ~~file size that can be seen through~~ wiringOP icon to open the ~~'''ls -lh''' command and the space occupied in the ZFS pool are both '''27M'''~~wiringOP APP</li>~~</ol>~~ ~~[[File:pi3b-img372.png|576x90px]]~~

[[File:pi3b-img418.png]]

</ol>

<li>~~Then we enable compression~~ The main interface of wiringOP APP is displayed as shown in the ~~ZFS pool pool1</li></ol>~~ ~~root@orangepi:/pool1$~~ figure below, and then click the '''~~sudo zfs set compression=lz4 pool1~~UART_TEST'''button to open the UART test interface</li>

[[File:pi3b-img426.png]]

</ol>

<li>~~Then execute~~ The serial port test interface of the ~~following command again to package~~ APP is shown in the ~~'''/var/log/''' and '''/etc/''' directories into a tar package~~figure below</li>~~</ol>~~ ~~root@orangepi:/pool1$ '''sudo tar -cf text.tar /var/log/ /etc/'''~~

[[File:pi3b-img427.png]]

</ol>

<li>~~At this time~~Take the test of '''UART7''' as an example below, select the '''/dev/ttyS7''' node in the selection box, enter the baud rate you ~~can see that~~ want to set in the ~~size of~~ edit box, and then click the '''~~text.tar~~OPEN''' ~~file~~ button to open the /dev/ttyS7 node. After the opening is ~~still 27M~~successful, ~~but it only occupies 9.47M in~~ the ~~ZFS pool~~'''OPEN''' button becomes unselectable, ~~indicating that~~ and the ~~file is compressed~~'''CLOSE''' button and '''SEND''' button become selectable</li~~></ol~~>

[[File:pi3b-~~img373~~img428.png~~|576x79px~~]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then use Dupont wire to short the RXD and TXD pins of uart7</li>

[[File:pi3b-img429.png]]</ol><~~span id~~ol start="7" style="~~how-to-shut-down-and~~list-~~restart~~style-~~the-development-board~~type: decimal;"><~~/span~~li>~~== How to shut down~~ Then you can enter a character in the send edit box below, and ~~restart~~ click the ~~development board ==~~'''SEND''' button to start sending</li>

~~# During the running of the Linux system, if the Type~~[[File:pi3b-img430.png]]</ol><ol start="8" style="list-style-~~C power supply~~ type: decimal;"><li>If everything is ~~directly unplugged~~normal, ~~some data may~~ the received string will be ~~lost or damaged~~ displayed in the ~~file system, so please use the '''poweroff''' command to shut down the Linux system of the development board before powering off. Then unplug the power again.~~receiving box</li>

~~orangepi@orangepi~~[[File:~~~$ '''sudo poweroff'''~~pi3b-img431.png]]</ol>

~~<ol start~~=~~"2" style~~=~~"list-style-type: decimal;"><li>In addition, the development board is equipped with a switch button, and you can also '''short press''' the switch button on the development board to shut down.</li></ol>~~= 40pin SPI test ===

~~[[File:pi3b-img374.png|294x80px]]~~# According to the schematic diagram of the 40pin interface, the spi available for Orange Pi 3B is spi3

'''Note that the Linux desktop version system will pop up a confirmation box as shown in the figure below after pressing the switch button, and the system will shut down only after clicking the Shut Down option::[[File:pi3b-img264.~~'''~~png]]

~~[[File~~<ol start="2" style="list-style-type:~~pi3b-img375~~decimal;"><li>Here, the SPI interface is tested through the w25q64 module.~~png|207x193px]]~~First, the w25q64 device is connected to the SPI3 interface</li>

[[File:pi3b-img432.png]]

</ol>

<li>~~Short press~~ Then click the ~~switch button on~~ wiringOP icon to open the ~~development board after shutting down to start up.~~wiringOP APP</li>~~</ol>~~ ~~[[File:pi3b-img374.png|294x80px]]~~

[[File:pi3b-img418.png]]

</ol>

<li>The ~~command~~ main interface of wiringOP APP is displayed as shown in the figure below, click the SPI_TEST button to ~~restart~~ open the ~~Linux system is~~SPI test interface</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''sudo'''~~ pi3b-img433.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then click the '''~~reboot~~OPEN'''button to initialize the SPI</li>

[[File:pi3b-img434.png]]<~~span id~~/ol><ol start="6" style="~~linux~~list-~~sdkorangepi~~style-~~build-instructions~~type: decimal;"><li>Then fill in the bytes that need to be sent, such as reading the ID information of w25q64, fill in the address 0x9f in data[0], and then click the '''TRANSFER''' button</~~span~~li>

[[File:pi3b-img435.png]]</ol><ol start="7" style= ~~'''Linux SDK——orangepi~~"list-style-~~build instructions''' =~~type: decimal;"><li>Finally, the APP will display the read ID information</li>

[[File:pi3b-img436.png]]<~~span id~~/ol><ol start="8" style="~~compilation~~list-~~system~~style-~~requirements~~type: decimal;"><li>The MANUFACTURER ID of the w25q64 module is EFh, and the Device ID is 4017h, corresponding to the value read above (h stands for hexadecimal)</~~span~~li>~~== Compilation system requirements ==~~

~~'''We can cross~~[[File:pi3b-~~compile the Linux image of the development board on the x64 computer, or compile the Linux image of the development board on the Ubuntu22~~img437.~~04 system of the development board, please choose one according to your preference.'''~~png]]</ol>

'''If you use orangepi-build to compile the Linux image in the Ubuntu22.04 system of the development board, please do a good job of cooling (especially when the SSD starts). If the heat dissipation is not done well, it is prone to the error of file system runaway.'''=== 40pin PWM test ===

~~=== Compile with the Ubuntu22.04 system of the development board ===~~figure below

~~# The Linux SDK, namely '''orangepi~~::[[File:pi3b-build''', supports running on the '''Ubuntu 22.04''' of the development board (other systems have not been tested), so before downloading orangepi-build, please first ensure that the Ubuntu version installed on the development board is Ubuntu 22.04. The command to check the Ubuntu version installed on the development board is as follows. If the Release field does not display '''22.04''', it means that the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operationsimg438.png]]

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~~~$ '''lsb_release -a'''~~decimal;"><li>First click on the wiringOP icon to open the wiringOP APP</li>

~~No LSB modules are available~~[[File:pi3b-img418.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then click the '''PWM_TEST''' button on the main interface of wiringOP to enter the PWM test interface</li>

~~Distributor ID~~[[File: ~~Ubuntu~~pi3b-img439.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>The base address corresponding to PWM11 is '''fe6f0030''', here pwmchip0 shows '''fdd70020.pwm''' on the right, then you need to click the drop-down option to select other pwmchips until '''febf0030.pwm''' is displayed on the right</li>

~~Description~~[[File: ~~Ubuntu 22~~pi3b-img440.~~04.1 LTS~~png]]</ol><ol start="5" style="list-style-type: decimal;"><li>When the drop-down option selects '''pwmchip3''', the corresponding base address of PWM11 is '''fe6f0030''' on the right</li>

~~Release~~[[File: pi3b-img441.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then confirm the PWM channel, the default is channel 0, and confirm the PWM cycle, the default configuration is '''50000ns''~~22.04~~', converted to PWM frequency is '''20KHz''', you can modify it yourself, click the '''EXPORT''' button to export '''PWM11'''</li>

~~Codename~~[[File: ~~jammy~~pi3b-img442.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Then drag the drag bar below to change the PWM duty cycle, and then check Enable to output the PWM waveform</li>

[[File:pi3b-img443.png]]</ol><ol start="28" style="list-style-type: decimal;"><li>~~'''Since~~ Then use an oscilloscope to measure the ~~source codes such as~~ No. 32 pin in the ~~kernel and U-boot are stored on GitHub, it is very important to ensure that~~ 40pin of the development board , and you can ~~download codes from GitHub normally when compiling~~ see the ~~image.'''~~following waveform</li~~></ol~~>

[[File:pi3b-img444.png]]</ol>~~=== Compile with x64 Ubuntu22.04 computer ===~~

# The Linux SDK, '''orangepi-build''', supports running on computers with '''Ubuntu 22.04''' installed, so before downloading orangepi-build, please make sure that the Ubuntu version installed on your computer is Ubuntu 22.04. The command == How to check the Ubuntu version installed on the computer is as follows. If the Release field does not display '''22.04''', it means that the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operations.use ADB ==

~~test@test:~$ '''lsb_release~~ === Use network connection adb debugging ===

~~No LSB modules are available~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Using the network adb does not require a data cable to connect the computer and the development board, but to communicate through the network, so first make sure that the wired or wireless network of the development board is connected, and then obtain the IP address of the development board, which will be used later.'''</big>|}

~~Distributor ID: Ubuntu~~# Make sure that the '''service.adb.tcp.port''' of the Android system is set to port number 5555

~~Description~~: ~~Ubuntu 22~~:{| class="wikitable" style="width:800px;" |-| console:/ # '''getprop | grep "adb.~~04 LTS~~tcp"'''

~~Release~~[service.adb.tcp.port]: ['''~~22.04~~5555''']|}

~~Codename~~<ol start="2" style="list-style-type: ~~jammy~~decimal;"><li>If '''service.adb.tcp.port''' is not set, you can use the following command to set the port number of network adb</li>

~~<ol start~~{| class="2wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>If the computer is installed with Windows system and there is no computer with Ubuntu 22.04 installed, you can consider using '''VirtualBox''' or '''VMware~~|-| console:/ # ''' ~~to install an Ubuntu 22.04 virtual machine in the Windows system~~setprop service. But please be careful not to compile orangepi-build on the WSL virtual machine, because orangepi-build has not been tested in the WSL virtual machine, so it cannot be guaranteed that orangepi-build can be used normally in WSLadb.~~</li><li>The download address of the installation image of Ubuntu 22~~tcp.~~04 '''amd64~~port 5555''' ~~version is:</li></ol>~~

~~[https~~console:/~~/repo.huaweicloud.com/ubuntu-releases/21.04/ubuntu-21.04-desktop-amd64.iso~~ # '''~~https://mirrors.tuna.tsinghua.edu.cn/ubuntu-releases/22.04/ubuntu-22.04-desktop-amd64.iso~~stop adbd''']

Orconsole:/ # '''start adbd'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Install adb tool on Ubuntu PC</li>

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''~~https://repo.huaweicloud.com/ubuntu-releases/22.04/ubuntu-22.04.1-desktop-amd64.iso~~sudo apt update'''

test@test:~$ '''sudo apt install -y adb'''

|}

</ol>

<li>~~After installing Ubuntu 22.04~~ Then connect network adb on ~~the computer or virtual machine, please set the software source of~~ Ubuntu ~~22.04 to Tsinghua source, otherwise it is easy to make mistakes due to network reasons when installing the software later~~PC~~<ol style="list-style-type: lower-alpha;">~~<li~~>For the method of replacing Tsinghua source, please refer to the instructions on this web page</li></ol></li></ol~~>

~~https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/~~ ~~<ol start~~{| class="2wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Note that the Ubuntu version~~ |-| test@test:~$ '''adb connect 192.168.1.xxx''' '''(The IP address needs to be ~~switched~~ changed to ~~22.04</li></ol>~~the IP address of the development board)'''

~~[[File~~* daemon not running; starting now at tcp:~~pi3b-img376.png|576x241px]]~~5037

<~~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~~p>* daemon started successfully</olp>

~~test@test:~$ '''sudo mv /etc/apt/sources~~connected to 192.~~list /etc/apt/sources~~168.~~list~~1.~~bak'''~~xxx:5555

~~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~~test@test:~$ '''adb devices'''

~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse~~List of devices attached

~~# deb-src https://mirrors~~192.~~tuna~~168.~~tsinghua~~1.~~edu.cn~~xxx:5555 device|}</~~ubuntu~~ol><ol start="5" style="list-style-type: decimal;"><li>Then you can log in to the android system through the adb shell on the Ubuntu PC</ ~~jammy main restricted universe multiverse~~li>

~~deb https~~{| class="wikitable" style="width:~~//mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy~~800px;" |-~~updates main restricted universe multiverse~~| test@test:~$ '''adb shell'''

~~# deb-src https~~console:/#|}</~~mirrors.tuna.tsinghua.edu.cn/ubuntu~~ol></ ~~jammy-updates main restricted universe multiverse~~span>

~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse~~= '''Appendix''' =

~~# deb~~</~~ubuntu/ jammy-backports main restricted universe multiverse~~span>== User Manual Update History ==

~~deb https~~{| class="wikitable" style="width:~~//mirrors~~800px;text-align: center;"|-|'''Version'''|'''Date'''|'''Update Notes'''|-|v0.~~tuna.tsinghua.edu.cn/ubuntu/ jammy~~1|2023-07-~~security main restricted universe multiverse~~19|initial version|}

~~# deb~~</~~/mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-security main restricted universe multiverse~~span>== Image Update History ==

~~# Pre~~{| class="wikitable" style="width:800px;"|-~~release software source, not recommended to enable~~| style="text-align: center;" | '''Date'''| style="text-align: center;" | '''Update Notes'''|-| style="text-align: center;" | 2023-07-19|Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160.7z

~~# deb https://mirrors~~Orangepi3b_1.~~tuna~~0.~~tsinghua~~0_ubuntu_jammy_desktop_xfce_linux5.~~edu~~10.~~cn/ubuntu/ jammy-proposed main restricted universe multiverse~~160.7z

~~# deb-src https://mirrors~~Orangepi3b_1.~~tuna~~0.~~tsinghua~~0_ubuntu_focal_desktop_xfce_linux5.~~edu~~10.~~cn/ubuntu/ jammy-proposed main restricted universe multiverse~~160.7z

~~<ol start="4" style="list-style-type: lower-alpha;"><li>After the replacement, you need to update the package information and make sure there is no error</li></ol>~~OrangePi3B_RK3566_Android11_v1.0.0.tar.gz

~~test@test:~$ '''sudo apt update'''~~OrangePi3B_RK3566_Android11_lcd_v1.0.0.tar.gz

~~<ol start="5" style="list-style-type: lower-alpha;">~~<li>'''In addition, since the source codes such as the kernel and U-boot are stored on GitHub, it is very important to ensure that the computer can download codes from GitHub normally when compiling the image.'''</li></ol> ~~== Get the source code of Linux sdk ==~~ ~~=== Download orangepi-build from github ===~~ # The Linux sdk actually refers to the code of orangepi-build. orangepi-build is modified based on the armbian build system. Using orangepi-build, multiple versions of Linux images can be compiled. First download the code of orangepi-build, the command is as follows: ~~test@test:~$ '''sudo apt-get update'''~~ ~~test@test:~$ '''sudo apt-get install -y git'''~~ ~~test@test:~$ '''git clone https://github.com/orangepi-xunlong/orangepi-build.git -b next'''~~ '''Note that the Orange Pi 3B development board needs to download the source code of the next branch of orangepi-build. The above git clone command needs to specify the branch of the orangepi-build source code as next.''' ~~<div class="figure">~~ ~~[[File:pi3b-img377.png|576x298px|图片6]]~~ ~~</div>~~'''Downloading the orangepi-build code through the git clone command does not require entering the user name and password of the github account (the same is true for downloading other codes in this manual), if the Ubuntu PC prompts the user to enter the github account after entering the git clone command The name and password are usually entered incorrectly in the address of the orangepi-build warehouse behind the git clone. Please check the spelling of the command carefully, instead of thinking that we forgot to provide the username and password of the github account.''' ~~<ol start="2" style="list-style-type: decimal;"><li>The u-boot and Linux kernel versions currently used by the development board are as follows</li></ol>~~ ~~{| class="wikitable"~~|-~~|'''branch'''|'''u-boot version'''|'''Linux Kernel version'''~~|-~~|'''legacy'''|'''u-boot 2017.09'''|'''Linux5.10'''~~|} '''The branch mentioned here is not the same thing as the branch of the orangepi-build source code, please do not confuse it. This branch is mainly used to distinguish different kernel source code versions.''' ~~'''Currently, the Linux5.10 bsp kernel provided by RK is defined as the legacy branch. If the mainline kernel is supported in the future, a current branch will be added.'''~~ ~~<ol start="3" style="list-style-type: decimal;"><li>orangepi-build will contain the following files and folders after downloading<ol style="list-style-type: lower-alpha;"><li>'''build.sh''': Compile the startup script</li><li>'''external''': Contains the configuration files needed to compile the image, specific scripts, and the source code of some programs, etc.</li><li>'''LICENSE''': GPL 2 license file</li><li>README.md: orangepi-build documentation</li><li>'''scripts''': General script for compiling Linux images</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''ls'''~~ ~~'''build.sh external LICENSE''' README.md '''scripts'''~~ '''If you downloaded the code of orangepi-build from github, after downloading, you may find that orangepi-build does not contain the source code of u-boot and Linux kernel, nor does u-boot and Linux kernel need to use cross-compilation tools Chain, this is normal, because these things are stored in other separate github warehouses or some servers (the addresses will be detailed below). orangepi-build will specify the address of u-boot, Linux kernel and cross-compilation toolchain in the script and configuration file. When running orangepi-build, when it finds that there are no such things locally, it will automatically go to the corresponding place to download them.''' ~~=== Download the cross-compilation toolchain ===~~ '''The cross-compilation toolchain will only be downloaded when the orangepi-build compilation image is used on an x64 computer. Compiling the Linux image of the development board in the Ubuntu22.04 of the development board will not download the cross-compilation toolchain. At this time, orangepi-build/toolchains will be an empty folder.''' # When orangepi-build runs for the first time, it will automatically download the cross-compilation toolchain and put it in the '''toolchains''' folder. Every time after running the build.sh script of orangepi-build, it will check whether the cross-compilation toolchain in '''toolchains''' exists , if it does not exist, the download will be restarted, if it exists, it will be used directly, and the download will not be repeated. ~~<div class="figure">~~ ~~[[File:pi3b-img378.png|575x278px|选区_396]]~~ ~~</div><ol start="2" style="list-style-type: decimal;"><li>The image URL of the cross-compilation toolchain in China is the open source software image site of Tsinghua University</li></ol>~~ ~~https://mirrors.tuna.tsinghua.edu.cn/armbian-releases/_toolchain/~~ ~~<ol start="3" style="list-style-type: decimal;"><li>After '''toolchains''' is downloaded, it will contain multiple versions of cross-compilation toolchains, and the development board will only use two of them</li></ol>~~ ~~test@test:~/orangepi-build$ '''ls toolchains/'''~~ ~~gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu~~ ~~gcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf~~ ~~gcc-arm-9.2~~OrangePi3B_RK3566_Android11_spi-~~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~~nvme_v1.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"~~|-~~|'''Android version'''|'''Kernel version'''~~|-~~|'''Android 11'''|'''Linux4.19'''~~|} ~~== Android Function Adaptation ==~~ ~~{| class="wikitable"~~|-~~|'''Functions'''|'''Android 11'''~~|-~~|'''USB2.0x3'''|'''OK'''~~|-~~|'''USB3.0x1'''|'''OK'''~~|-~~|'''M.2 NVMe SSD boot'''|'''OK'''~~|-~~|'''WIFI'''|'''OK'''~~|-~~|'''Bluetooth'''|'''OK'''~~|-~~|'''GPIO（40pin）'''|'''OK'''~~|-~~|'''UART（40pin）'''|'''OK'''~~|-~~|'''SPI（40pin）'''|'''OK'''~~|-~~|'''I2C（40pin）'''|'''OK'''~~|-~~|'''PWM（40pin）'''|'''OK'''~~|-~~|'''PWM fan interface'''|'''OK'''~~|-~~|'''3pin Debugging serial port'''|'''OK'''~~|-~~|'''EMMC'''|'''OK'''~~|-~~|'''TF card boot'''|'''OK'''~~|-~~|'''HDMI video'''|'''OK'''~~|-~~|'''HDMI Audio'''|'''OK'''~~|-~~|'''LCD'''|'''OK'''~~|-~~|'''eDP display'''|'''OK'''~~|-~~|'''Gigabit network port'''|'''OK'''~~|-~~|'''Network port status indicator'''|'''OK'''~~|-~~|'''Headphone playback'''|'''OK'''~~|-~~|'''Headphone recording'''|'''OK'''~~|-~~|'''LED Light'''|'''OK'''~~|-~~|'''GPU'''|'''OK'''~~|-~~|'''NPU'''|'''OK'''~~|-~~|'''VPU'''|'''OK'''~~|-~~|'''RTC'''|'''OK'''~~|} ~~== WIFI connection test method ==~~ ~~# First click enter '''Setting'''~~ ~~[[File:pi3b-img396.png|549x228px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Then select '''Network & internet'''</li></ol>~~ ~~[[File:pi3b-img397.png|565x120px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then select '''Wi-Fi'''</li></ol>~~ ~~[[File:pi3b-img398.png|561x99px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then turn on the '''Wi-Fi''' switch</li></ol>~~ ~~[[File:pi3b-img399.png|560x167px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>After turning on '''Wi-Fi''', if everything is normal, you can scan for nearby Wi-Fi hotspots</li></ol>~~ ~~[[File:pi3b-img400.png|561x166px]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Then select the Wi-Fi you want to connect to, and the password input interface shown in the figure below will pop up</li></ol>~~ ~~[[File:pi3b-img401.png|553x237px]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>Then use the keyboard to enter the password corresponding to Wi-Fi, and then use the mouse to click the Enter button in the virtual keyboard to start connecting to Wi-Fi</li></ol>~~ ~~[[File:pi3b-img402.png|553x232px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>After the Wi-Fi connection is successful, the display is as shown in the figure below:</li></ol>~~ ~~[[File:pi3b-img403.png|558x102px]]~~ ~~== How to use Wi-Fi hotspot ==~~ ~~# First, please make sure that the Ethernet port is connected to the network cable and can access the Internet normally# Then select '''Settings'''~~ ~~[[File:pi3b-img396.png|549x228px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then select '''Network & internet'''</li></ol>~~ ~~[[File:pi3b-img397.png|565x120px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then select '''Hotspot & tethering'''</li></ol>~~ ~~[[File:pi3b-img404.png|549x173px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>Then select '''Wi-Fi hotspot'''</li></ol>~~ ~~[[File:pi3b-img405.png|548x104px]]~~ ~~<ol start="6" style="list-style-type: decimal;">~~<li>Then turn on the '''Wi-Fi hotspot''', you can also see the name and password of the generated hotspot in the figure below, remember them, and use them when connecting to the hotspot (if you need to modify the name and password of the hotspot, you need to turn off the Wi-Fi first -Fi hotspot before modification)</li></ol> ~~[[File:pi3b-img406.png|551x158px]]~~ ~~<ol start="7" style="list-style-type: decimal;">~~<li>At this time, you can take out your mobile phone. If everything is normal, you can find the WIFI hotspot with the same name ('''here AndroidAP_6953''') displayed under the '''Hotspot name''' in the above picture in the WI-FI list searched by the mobile phone. Then you can click '''AndroidAP_6953''' to connect to the hotspot, and the password can be seen under the '''Hotspot password''' in the above picture</li></ol> ~~[[File:pi3b-img407.png|313x238px]]~~ ~~<ol start="8" style="list-style-type: decimal;">~~<li>After the connection is successful, it will be displayed as shown in the figure below (the interface of different mobile phones will be different, the specific interface is subject to the display of your mobile phone). At this point, you can open a webpage on your mobile phone to see if you can access the Internet. If you can open the webpage normally, it means that the '''WI-FI Hotspot''' of the development board can be used normally.</li></ol> ~~[[File:pi3b-img408.png|327x165px]]~~ ~~== Bluetooth test method ==~~ ~~# First click enter '''Setting'''~~ ~~[[File:pi3b-img396.png|549x228px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Then select '''Connected devices'''</li></ol>~~ ~~[[File:pi3b-img409.png|547x115px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then click '''Pair new device''' to turn on Bluetooth and start scanning the surrounding Bluetooth devices</li></ol>~~ ~~[[File:pi3b-img410.png|547x126px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>The searched Bluetooth devices will be displayed under '''Available devices'''</li></ol>~~ ~~[[File:pi3b-img411.png|559x279px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>Then click the Bluetooth device you want to connect to start pairing. When the following interface pops up, please use the mouse to select the '''Pair''' option</li></ol>~~ ~~[[File:pi3b-img412.png|522x212px]]~~ ~~<ol start="6" style="list-style-type: decimal;">~~<li>The test here is the configuration process of the development board and the Bluetooth of the Android mobile phone. At this time, the following confirmation interface will pop up on the mobile phone. After clicking the pairing button on the mobile phone, the pairing process will start</li></ol> ~~[[File:pi3b-img413.png|236x273px]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>After the pairing is completed, you can see the paired Bluetooth device as shown in the figure below</li></ol>~~ ~~[[File:pi3b-img414.png|545x178px]]~~ ~~<ol start="8" style="list-style-type: decimal;">~~<li>At this time, you can use the Bluetooth of your mobile phone to send a picture to the development board. After sending, you can see the following confirmation interface in the Android system of the development board, and then click '''Accept''' to start receiving the picture sent by the mobile phone.</li></ol> ~~[[File:pi3b-img415.png|559x238px]]~~ ~~<ol start="9" style="list-style-type: decimal;"><li>You can open the '''Download''' directory in the file manager to view the pictures received by the Android system Bluetooth of the development board</li></ol>~~ ~~[[File:pi3b-img416.png|573x97px]]~~ ~~== How to use Raspberry Pi 5-inch screen ==~~ ~~'''Please make sure that the image used is the following two versions of the image:'''~~ ~~'''OrangePi3B_RK3566_Android11_lcd_v1.x.x.img'''~~ ~~'''OrangePi3B_RK3566_Android11_spi-nvme_lcd_v1.x.x.img'''~~ ~~# The screen needs to be assembled first, please refer to [[\l|'''the assembly method of the Raspberry Pi 5-inch screen''']]# Connect the Type-C power supply to the board and power it on. After the system starts, you can see the screen display as shown in the figure below~~ ~~[[File:pi3b-img417.png|516x332px]]~~ ~~== 40pin interface GPIO, UART, SPI and PWM test ==~~ ~~=== 40pin GPIO port test ===~~ ~~# First click on the wiringOP icon to open the wiringOP APP~~ ~~[[File:pi3b-img418.png|576x210px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>The main interface of wiringOP APP is displayed as shown in the figure below, and then click the '''GPIO_TEST''' button to open the GPIO test interface</li></ol>~~ ~~[[File:pi3b-img419.png|575x148px]]~~ ~~<ol start="3" style="list-style-type: decimal;">~~<li>The GPIO test interface is shown in the figure below. The two rows of '''CheckBox''' buttons on the left are in one-to-one correspondence with the 40pin pins. When the '''CheckBox''' button is checked, the corresponding GPIO pin will be set to '''OUT''' mode, and the pin level will be set to high level; when the checkbox is unchecked, the GPIO pin level will be set to low level; When the '''GPIO READALL''' button is pressed, information such as wPi number, GPIO mode, and pin level can be obtained; when the '''BLINK ALL GPIO''' button is clicked, the program will control the 28 GPIO ports to continuously switch between high and low levels</li></ol> ~~[[File:pi3b-img420.png|576x303px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button, the output information is as shown in the figure below:</li></ol>~~ ~~[[File:pi3b-img421.png|575x323px]]~~ ~~<ol start="5" style="list-style-type: decimal;">~~<li>There are a total of 28 GPIO ports in the 40pins of the development board that can be used. The following uses pin 7—the corresponding GPIO is GPIO4_A4—the corresponding wPi serial number is 2—as an example to demonstrate how to set the high and low levels of the GPIO port. First click the '''CheckBox''' button corresponding to pin 7. When the button is selected, pin 7 will be set to high level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is 3.3v, it means setting high level success</li></ol> ~~[[File:pi3b-img422.png|241x326px]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is '''OUT''', and the pin level is high</li></ol>~~ ~~[[File:pi3b-img423.png|574x301px]]~~ ~~<ol start="7" style="list-style-type: decimal;">~~<li>Click the '''CheckBox''' button in the figure below again to cancel the check status. Pin 7 will be set to low level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is '''0v''', it means that the low level is set successfully.</li></ol> ~~[[File:pi3b-img424.png|250x345px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is OUT, and the pin level is low</li></ol>~~ ~~[[File:pi3b-img425.png|576x300px]]~~ ~~=== 40pin UART test ===~~ ~~# UART7 and UART9 are enabled by default in Android. The position of the 40pin is shown in the figure below, and the corresponding device nodes are '''/dev/ttyS7''' and '''/dev/ttyS9''' respectively~~ ~~[[File:pi3b-img269.png|376x92px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>First click on the wiringOP icon to open the wiringOP APP</li></ol>~~ ~~[[File:pi3b-img418.png|576x210px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>The main interface of wiringOP APP is displayed as shown in the figure below, and then click the '''UART_TEST''' button to open the UART test interface</li></ol>~~ ~~[[File:pi3b-img426.png|575x156px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>The serial port test interface of the APP is shown in the figure below</li></ol>~~ ~~[[File:pi3b-img427.png|576x324px]]~~ ~~<ol start="5" style="list-style-type: decimal;">~~<li>Take the test of '''UART7''' as an example below, select the '''/dev/ttyS7''' node in the selection box, enter the baud rate you want to set in the edit box, and then click the '''OPEN''' button to open the /dev/ttyS7 node. After the opening is successful, the '''OPEN''' button becomes unselectable, and the '''CLOSE''' button and '''SEND''' button become selectable</li></ol> ~~[[File:pi3b-img428.png|574x166px]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Then use Dupont wire to short the RXD and TXD pins of uart7</li></ol>~~ ~~[[File:pi3b-img429.png|418x103px]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>Then you can enter a character in the send edit box below, and click the '''SEND''' button to start sending</li></ol>~~ ~~[[File:pi3b-img430.png|575x161px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>If everything is normal, the received string will be displayed in the receiving box</li></ol>~~ ~~[[File:pi3b-img431.png|574x164px]]~~ ~~=== 40pin SPI test ===~~ ~~# According to the schematic diagram of the 40pin interface, the spi available for Orange Pi 3B is spi3~~ ~~[[File:pi3b-img264.png|577x193px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Here, the SPI interface is tested through the w25q64 module. First, the w25q64 device is connected to the SPI3 interface</li></ol>~~ ~~[[File:pi3b-img432.png|373x215px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then click the wiringOP icon to open the wiringOP APP</li></ol>~~ ~~[[File:pi3b-img418.png|576x210px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>The main interface of wiringOP APP is displayed as shown in the figure below, click the SPI_TEST button to open the SPI test interface</li></ol>~~ ~~[[File:pi3b-img433.png|574x149px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>Then click the '''OPEN''' button to initialize the SPI</li></ol>~~ ~~[[File:pi3b-img434.png|576x241px]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Then fill in the bytes that need to be sent, such as reading the ID information of w25q64, fill in the address 0x9f in data[0], and then click the '''TRANSFER''' button</li></ol>~~ ~~[[File:pi3b-img435.png|572x216px]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>Finally, the APP will display the read ID information</li></ol>~~ ~~[[File:pi3b-img436.png|575x296px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>The MANUFACTURER ID of the w25q64 module is EFh, and the Device ID is 4017h, corresponding to the value read above (h stands for hexadecimal)</li></ol>~~ ~~[[File:pi3b-img437.png|374x126px]]~~ ~~=== 40pin PWM test ===~~ ~~# Android enables '''PWM11''' by default, and the corresponding pin is located at 40pin as shown in the figure below~~ ~~[[File:pi3b-img438.png|334x107px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>First click on the wiringOP icon to open the wiringOP APP</li></ol>~~ ~~[[File:pi3b-img418.png|576x210px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then click the '''PWM_TEST''' button on the main interface of wiringOP to enter the PWM test interface</li></ol>~~ ~~[[File:pi3b-img439.png|575x150px]]~~ ~~<ol start="4" style="list-style-type: decimal;">~~<li>The base address corresponding to PWM11 is '''fe6f0030''', here pwmchip0 shows '''fdd70020.pwm''' on the right, then you need to click the drop-down option to select other pwmchips until '''febf0030.pwm''' is displayed on the right</li></ol> ~~[[File:pi3b-img440.png|576x178px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>When the drop-down option selects '''pwmchip3''', the corresponding base address of PWM11 is '''fe6f0030''' on the right</li></ol>~~ ~~[[File:pi3b-img441.png|574x161px]]~~ ~~<ol start="6" style="list-style-type: decimal;">~~<li>Then confirm the PWM channel, the default is channel 0, and confirm the PWM cycle, the default configuration is '''50000ns''', converted to PWM frequency is '''20KHz''', you can modify it yourself, click the '''EXPORT''' button to export '''PWM11'''</li></ol> ~~[[File:pi3b-img442.png|575x160px]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>Then drag the drag bar below to change the PWM duty cycle, and then check Enable to output the PWM waveform</li></ol>~~ ~~[[File:pi3b-img443.png|575x167px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>Then use an oscilloscope to measure the No. 32 pin in the 40pin of the development board, and you can see the following waveform</li></ol>~~ ~~[[File:pi3b-img444.png|460x276px]]~~ ~~== How to use ADB ==~~ ~~=== Use network connection adb debugging ===~~ '''Using the network adb does not require a data cable to connect the computer and the development board, but to communicate through the network, so first make sure that the wired or wireless network of the development board is connected, and then obtain the IP address of the development board, which will be used later.''' ~~# Make sure that the '''service.adb.tcp.port''' of the Android system is set to port number 5555~~ ~~console:/ # '''getprop | grep "adb.tcp"'''~~ ~~[service.adb.tcp.port]: ['''5555''']~~ ~~<ol start="2" style="list-style-type: decimal;"><li>If '''service.adb.tcp.port''' is not set, you can use the following command to set the port number of network adb</li></ol>~~ ~~console:/ # '''setprop service.adb.tcp.port 5555'''~~ ~~console:/ # '''stop adbd'''~~ ~~console:/ # '''start adbd'''~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Install adb tool on Ubuntu PC</li></ol>~~ ~~test@test:~$ '''sudo apt update'''~~ ~~test@test:~$ '''sudo apt install -y adb'''~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then connect network adb on Ubuntu PC</li></ol>~~ ~~test@test:~$ '''adb connect 192.168.1.xxx''' '''(The IP address needs to be changed to the IP address of the development board)'''~~ * daemon not running; starting now at tcp:5037 * daemon started successfully ~~connected to 192.168.1.xxx:5555~~ ~~test@test:~$ '''adb devices'''~~ ~~List of devices attached~~ ~~192.168.1.xxx:5555 device~~ ~~<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 ==~~gz

~~{| class="wikitable"~~|-~~|'''Version'''|'''Date'''|'''Update Notes'''~~|-~~|v0.1|2023-07-19|initial version~~|} ~~== Image Update History ==~~ ~~{| class="wikitable"~~|-~~| '''Date'''| '''Update Notes'''~~|-~~| 2023-07-19| Orangepi3 b_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160.7z~~ ~~Orange pi3b_1.0.0_ubuntu_jammy_desktop_xfce_linux5.10.160.7z~~ ~~Orange pi3b_1.0.0_ubuntu_focal_desktop_xfce_linux5.10.160.7z~~ ~~OrangePi3B_RK3566_Android11_v1.0.0.tar.gz~~ ~~OrangePi3B_RK3566_Android11_lcd_v1.0.0.tar.gz~~ ~~OrangePi3B_RK3566_Android11_spi~~OrangePi3B_RK3566_Android11_lcd_spi-nvme_v1.0.0.tar.gz

~~O rangePi3B_RK3566_Android11_lcd_spi-nvme_v1.0.0.tar.gz~~

* initial version

|}

Admin

Bureaucrats, Administrators

8,367

edits

Wiki-Orange Pi β

Changes

Orange Pi 3B

Wiki-Orange Pi ^β