Changes

← Older edit

Orange Pi 3B

32,434 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 ==

* Android game console, etc.

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Of course, there are more functions. Relying on a powerful ecosystem and a variety of expansion accessories, Orange Pi can help users easily realize the delivery from idea to prototype to mass production. It is a maker, dreamer, hobby The ideal creative platform for readers.'''</big>|}

== Hardware Features of Orange Pi 3B ==

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

|-

|colspan=2|

<div style="text-align:center"><big>'''Introduction to hardware features'''</big></div>

|-

| style="width: 200px" | Master chip

|

Rockchip RK3566

| GPU

|

~~·ARM~~ • ARM Mali G52 2EE graphics processor

~~·Support~~ • Support OpenGL ES 1.1/2.0/3.2, OpenCL 2.0, Vulkan 1.1

~~·Embedded~~ • Embedded high-performance 2D acceleration hardware

|-

| NPU

|

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

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

|-

| VPU

|

~~·4K~~• 4K@60fps H.265/H.264/VP9 video decoding

~~·1080P~~• 1080P@100fps H.265 video encoding

~~·1080P~~• 1080P@60fps H.264 video encoding

|-

| storage

|

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

~~·SPI~~ • SPI Flash: 16MB/32MB

·M• M.2 M-KEY slot: SATA3 or PCIe2.0 NVME SSD

~~·TF~~ • TF card slot

|-

| Wi-Fi+Bluetooth

|

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

|-

| ethernet transceiver

| show

|

~~·1x~~ • 1x HDMI TX 2.0, maximum support 4K@60FPS

~~·1xMIPI~~ • 1xMIPI DSI 2 Lane

~~·eDP1~~• eDP1.3

|-

| USB

|

~~·1xUSB~~ • 1xUSB 2.0 supports Device or HOST mode

~~·1xUSB~~ • 1xUSB 3.0 HOST

~~·2xUSB~~ • 2xUSB 2.0 HOST

|-

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

== Top view and bottom view of Orange Pi 3B ==

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

</div>

<big>'''Bottom view:'''</big>

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

</div>

== Interface details of Orange Pi 3B ==

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

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

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The diameter of the four positioning holes is 32.~~0mm~~7mm, and the diameter of the M.2 PICE device fixing hole is 32.~~5mm~~9mm.'''</big>|}

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

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

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

[[File:pi3b-img8.png]]

</ol>

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

[[File:pi3b-img9.png]]

</ol>

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

[[File:pi3b-img10.png]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note, if you want to connect a 4K monitor, please make sure that the HDMI cable supports 4K video output.'''</big>|}</ol>

<li>Power adapter, Orange Pi 3B is recommended to use 5V/3A ~~or 5V/4A~~ Type-C power supply for power supply</li>~~</ol>~~ ~~[[File:pi3b-img11.png]]~~

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

</ol>

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

[[File:pi3b-img12.png]]

</ol>

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

[[File:pi3b-img13.png]]

</ol>

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

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

[[File:pi3b-img14.png]]

</ol>

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

[[File:pi3b-img15.png]]

</ol>

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

[[File:pi3b-img16.png]]

</div></ol>

<li>'''3.3V''' USB to TTL module and DuPont line, when using serial port debugging function, need USB to TTL module and DuPont line to connect the development board and computer</li>~~</ol>~~ ~~[[File:pi3b-img17.png]] [[File:pi3b-img18.png]]~~

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

</ol>

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

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

|-

|-

|}

</ol>

~~~~

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

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

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

|-

|

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

|}

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

</div>

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

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

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

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

# Download the Linux operating system image file compression package that you want to burn from the [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/~~index~~computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page'''], and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system. The size is generally above 2GB.

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

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

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

[[File:pi3b-img20.png]]

</ol>

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

[[File:pi3b-img21.png]]

</ol>

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

[[File:pi3b-img22.png]]

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

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

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

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

|}

</ol>

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

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

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

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

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

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

<li>The interface displayed in the process of burning the Linux image by balenaEtcher is shown in the figure below, and the progress bar displays purple, indicating that the Linux image is being burned into the TF card</li>~~</ol>~~ ~~[[File:pi3b-img26.png|428x268px]]~~

[[File:pi3b-img26.png]]

</ol>

<li>After burning the Linux image, balenaEtcher will also verify the image burned into the TF card by default to ensure that there is no problem in the burning process. As shown in the figure below, a green progress bar indicates that the image has been burnt, and balenaEtcher is verifying the burnt image</li>~~</ol>~~ ~~[[File:pi3b-img27.png|427x267px]]~~

[[File:pi3b-img27.png]]

</ol>

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

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

</div></ol>

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

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

</div>

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

<li>Then download the Rockchip driver '''DriverAssitant_v5.12.zip''' and '''MiniLoader''' and the burning tool '''RKDevTool_Release_v3.15.zip''' from the [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/~~index~~computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page''']

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

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

</div></ol>

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

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

</div>

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the "MiniLoader-things needed to burn the Linux image" folder is hereinafter referred to as the MiniLoader folder.'''</big>|}</ol></li></ol>

<li>Then download the Linux operating system image file compression package that you want to burn from the [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/~~index~~computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page'''], and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system , the size is generally more than 2GB</li><li>Then use the decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>~~</ol>~~ ~~[[File:pi3b-img31.png|464x136px]]~~

[[File:pi3b-img31.png]]

</ol>

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

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

[[File:pi3b-img32.png]]

</ol>

<li>After waiting for a period of time, a pop-up window will prompt "'''The driver is installed successfully'''", and then click the "'''OK'''" button.</li>~~</ol>~~ ~~[[File:pi3b-img33.png|254x132px]]~~

[[File:pi3b-img33.png]]

</ol>

</li></ol>

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

[[File:pi3b-img34.png]]

</ol>

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

[[File:pi3b-img35.png]]

</ol>

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

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

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

</div></ol>

<li>Make sure the TF card slot is not inserted into the TF card</li>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:</li>~~</ol>~~ ~~[[File:pi3b-img37.png|289x100px]]~~

[[File:pi3b-img37.png]]

</ol>

<li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button</li~~></ol~~>

~~<blockquote>~~[[File:pi3b-img38.png~~|305x94px~~]]</~~blockquote~~ol>

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li>~~</ol>~~ ~~[[File:pi3b-img39.png|454x213px]]~~

[[File:pi3b-img39.png]]

</ol>

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

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

[[File:pi3b-img40.png~~|455x216px|图片1~~]]

</div></ol>

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

[[File:pi3b-img41.png]]

</ol>

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

[[File:pi3b-img42.png]]

</ol>

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

[[File:pi3b-img43.png]]

</ol>

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

[[File:pi3b-img44.png]]

</ol>

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

[[File:pi3b-img45.png]]

</ol>

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

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

</div></ol>

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

[[File:pi3b-img47.png]]

</ol>

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

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

[[File:pi3b-img48.png]]

</ol>

<li>Then please check the '''mandatory write by address''' option</li>~~</ol>~~ ~~[[File:pi3b-img49.png|497x234px]]~~

[[File:pi3b-img49.png]]

</ol>

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

[[File:pi3b-img50.png]]

</ol>

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

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

</div></ol>

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

</li></ol>

~~~~

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

<li>Then format the TF card

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

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

<li>If only a TF card is inserted into the computer, the drive letter of the TF card will be displayed in the "'''Select card'''" column. If multiple USB storage devices are inserted into the computer, you can select the corresponding drive letter of the TF card through the drop-down box</li~~></ol~~>

[[File:pi3b-img52.png~~|209x228px|选区_199~~]]

</div></ol>

<li>Then click "'''Format'''", a warning box will pop up before formatting, and formatting will start after selecting "'''Yes (Y)'''"</li>~~</ol>~~ ~~[[File:pi3b-img53.png|304x147px]]~~

[[File:pi3b-img53.png]]

</ol>

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

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

<li>Download the Linux operating system image file compression package that you want to burn from the [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/~~index~~computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page'''], and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system. The size is generally more than 2GB</li>

<li>Use '''Win32Diskimager''' to burn the Linux image to the TF card

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

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

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

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

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

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

</li></ol>

~~~~

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

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

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

# Download the balenaEtcher software, the download address is

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

|-

|

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

|}

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

[[File:pi3b-img20.png]]

</ol>

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

[[File:pi3b-img56.png~~|430x163px~~]]</ol><ol start="6" style="list-style-type: decimal;"><li>Download the Linux operating system image file compression package that you want to burn from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page'''], and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system. The size is generally more than 2GB</li>

~~<ol start="6" style="list-style-type: decimal;"><li>Download~~ The decompression command for the ~~Linux operating system image file compression~~ compressed package that you want to burn from the [http://www.orangepi.org/html/serviceAndSupport/index.html '''Orange Pi data download page'''], and then use the decompression software to decompress it. Among the decompressed files, the file ending ~~with "'''.img'''" is the image file of the operating system. The size~~ in 7z is ~~generally more than 2GB</li></ol>~~as follows

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

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

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

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

Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_Linux5.10.160.img #mirror file

|}</ol>

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

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

|-

|

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

Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_Linux5.10.160.img: OK

|}</ol>

<li>Then double-click '''balenaEtcher-1.5.109-x64.AppImage''' on the graphical interface of Ubuntu PC to open balenaEtcher (no installation required), and the interface after balenaEtcher is opened is shown in the figure below</li>~~</ol>~~ ~~[[File:pi3b-img57.png|423x251px]]~~

[[File:pi3b-img57.png]]

</ol>

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

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

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

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

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

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

<li>The interface displayed in the process of burning the Linux image by balenaEtcher is shown in the figure below, and the progress bar displays purple, indicating that the Linux image is being burned into the TF card</li>~~</ol>~~ ~~[[File:pi3b-img58.png|429x184px]]~~

[[File:pi3b-img58.png]]

</ol>

<li>After burning the Linux image, balenaEtcher will also verify the image burned into the TF card by default to ensure that there is no problem in the burning process. As shown in the figure below, a green progress bar indicates that the image has been burnt, and balenaEtcher is verifying the burnt image</li>~~</ol>~~ ~~[[File:pi3b-img59.png|436x190px]]~~

[[File:pi3b-img59.png]]

</ol>

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

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

~~~~

== How to burn Linux image to eMMC ==

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

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

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

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

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

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

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

</div></ol>

<li>Then download the Rockchip driver '''DriverAssitant_v5.12.zip''' and '''MiniLoader''' and the burning tool '''RKDevTool_Release_v3.15.zip''' from the [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/~~index~~computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page''']

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

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

</div></ol>

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

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

</div>

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the "MiniLoader-things needed to burn the Linux image" folder is hereinafter referred to as the MiniLoader folder.'''</big>|}</ol></li></ol>

<li>Then download the Linux operating system image file compression package that you want to burn from the [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/~~index~~computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page'''], and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system , the size is generally more than 2GB</li><li>Then use the decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>~~</ol>~~ ~~[[File:pi3b-img31.png|496x146px]]~~

[[File:pi3b-img31.png]]

</ol>

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

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

[[File:pi3b-img32.png]]

</ol>

<li>After waiting for a period of time, a pop-up window will prompt "'''The driver is installed successfully'''", and then click the "'''OK'''" button.</li>~~</ol>~~ ~~[[File:pi3b-img33.png|296x154px]]~~

[[File:pi3b-img33.png]]

</ol>

</li></ol>

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

[[File:pi3b-img34.png]]

</ol>

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

[[File:pi3b-img35.png]]

</ol>

<li>Then start burning the Linux image into eMMC

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

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

</div></ol>

<li>Make sure that the development board is not inserted into the TF card and not connected to the power supply</li>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:</li>~~</ol>~~ ~~[[File:pi3b-img37.png|289x100px]]~~

[[File:pi3b-img37.png]]

</ol>

<li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button</li>~~</ol>~~ ~~[[File:pi3b-img38.png|305x94px]]~~

[[File:pi3b-img38.png]]

</ol>

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li>~~</ol>~~ ~~[[File:pi3b-img39.png|457x215px]]~~

[[File:pi3b-img39.png]]

</ol>

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

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

</div></ol>

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

[[File:pi3b-img41.png]]

</ol>

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

[[File:pi3b-img42.png]]

</ol>

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

[[File:pi3b-img65.png]]

</ol>

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

[[File:pi3b-img66.png]]

</ol>

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

[[File:pi3b-img67.png]]

</ol>

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

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

</div></ol>

<li>Then click the position shown in the figure below</li>~~</ol>~~ ~~[[File:pi3b-img69.png|459x216px]]~~

[[File:pi3b-img69.png]]

</ol>

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

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

[[File:pi3b-img48.png]]

</ol>

<li>Then please check the option to '''force writing by address'''</li>~~</ol>~~ ~~[[File:pi3b-img70.png|501x235px]]~~

[[File:pi3b-img70.png]]

</ol>

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

[[File:pi3b-img71.png]]

</ol>

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

[[File:pi3b-img72.png]]

</ol>

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

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

~~~~

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

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

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

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

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

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

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

|-

|

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

Orangepi3b_x.x.x_debian_bullseye_desktop_xfce_Linux5.10.160.img

|}

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

|-

|

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

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

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

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

|}

</ol>

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

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

|-

|

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

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

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

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

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

|}</ol>

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

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

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

|}

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

|-

|

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

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

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

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

|}

</ol>

</li></ol>

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

~~~~

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

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

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

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

[[File:pi3b-img73.png]]

</ol>

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

[[File:pi3b-img74.png]]

</ol>

</li></ol>

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

[[File:pi3b-img75.png]]

</ol>

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

[[File:pi3b-img76.png]]

</ol>

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

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

</div></ol>

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

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

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

</div></ol>

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

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

</div>

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the "MiniLoader-things needed to burn the Linux image" folder is hereinafter referred to as the MiniLoader folder.'''</big>|}</ol></li></ol>

<li>Then download the Linux operating system image file compression package that you want to burn from the [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/~~index~~computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page'''], and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system , the size is generally more than 2GB</li><li>Then use the decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>~~</ol>~~ ~~[[File:pi3b-img31.png|446x131px]]~~

[[File:pi3b-img31.png]]

</ol>

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

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

[[File:pi3b-img32.png]]

</ol>

<li>After waiting for a period of time, a pop-up window will prompt "'''The driver is installed successfully'''", and then click the "'''OK'''" button.</li>~~</ol>~~ ~~[[File:pi3b-img33.png|269x140px]]~~

[[File:pi3b-img33.png]]

</ol>

</li></ol>

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

[[File:pi3b-img34.png]]

</ol>

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

[[File:pi3b-img35.png]]

</ol>

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

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

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

</div></ol>

<li>Make sure that the development board is not connected to the power supply and inserted into the TF card and eMMC</li>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:</li>~~</ol>~~ ~~[[File:pi3b-img37.png|289x100px]]~~

[[File:pi3b-img37.png]]

</ol>

<li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button</li>~~</ol>~~ ~~[[File:pi3b-img38.png|305x94px]]~~

[[File:pi3b-img38.png]]

</ol>

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li>~~</ol>~~ ~~[[File:pi3b-img39.png|457x215px]]~~

[[File:pi3b-img39.png]]

</ol>

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

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

</div></ol>

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

[[File:pi3b-img41.png]]

</ol>

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

[[File:pi3b-img42.png~~|458x215px~~]]</ol><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%~~ png]] </~~run~~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 '''Flash from file'''</li>

~~'''/dev/nvme0n1p2 1.9T 4.1G 1.8T 1% /'''~~<div class="figure">

~~tmpfs 3~~[[File:pi3b-img91.~~8G 0 3.8G 0% /dev/shm~~png]]

~~tmpfs 5~~</div></ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then enter the '''/usr/lib/Linux-u-boot-legacy-orangepi3b_1.~~0M 4~~x.~~0K 5~~x_arm64''' directory, select '''rkspi_loader.~~0M 1% /run~~img''', and click '''Open''' to open</~~lock~~li>

~~/dev/zram2 3.7G 76K 3.5G 1% /tmp~~<div class="figure">

~~'''/dev/nvme0n1p1 256M 90M 166M 36% /boot'''~~[[File:pi3b-img92.png]]

</~~dev~~div></~~zram1 194M 15M 165M 9%~~ ol><ol start="3" style="list-style-type: lower-alpha;"><li>The interface after opening '''rkspi_loader.img''' is as follows:</~~var/log~~li>

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

~~tmpfs 769M 48K 769M 1% /run/user/0~~<div class="figure">

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

~~orangepi@orangepi~~</div></ol><ol start="5" style="list-style-type:~$ lower-alpha;"><li>Then click '''~~sudo fix_mmc_ssd.sh~~Show 2 hidden'''to open more options for storage devices</li>

~~'''Exactly the same system means that the image name is exactly the same. Even if they are all Debian11 systems, the versions are different.'''~~<div class="figure">

~~=== How to use balenaEtcher software to burn ===~~img95.png]]

<~~ol style="list-style-type: decimal;"><li~~/div><~~p>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.</p~~ol><ol start="6" style="list-style-type: lower-alpha;"><li>~~The M.2 2230 SSD is as follows<~~Then select the device name of SPI Flash '''/~~li><~~dev/~~ol>~~mtdblock0''', and click '''Select'''</li~~></ol~~>

~~[[File:pi3b-img73.png|189x136px]]~~<div class="figure">

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

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

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

[[File:pi3b-~~img75~~img97.png~~|283x63px~~]]

</div></ol><ol start="38" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~The position of the SPI Flash on the development board is shown in the figure below~~Then click '''Yes, ~~no other settings are required before starting the programming~~I'm sure'''</li~~></ol~~>

~~[[File:pi3b-img76.png|261x198px]]~~<div class="figure">

~~<ol start="4" style="list~~[[File:pi3b-~~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 systemimg98. 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'''png]]~~.</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~~</div></ol><ol start="9" style="list-style-type:~~~/Desktop$~~ lower-alpha;"><li>Then enter the password '''~~sudo fdisk -l | grep "nvme0n1"~~orangepi'''of the development board Linux system, and it will start burning the u-boot image into the SPI Flash</li>

~~Disk /dev/nvme0n1: 1.86 TiB, 2048408248320 bytes, 4000797360 sectors~~<div class="figure">

~~Use the '''lspci''' command to see an NVMe~~[[File:pi3b-~~related PCI device~~img99.png]]

~~orangepi@orangepi~~</div></ol><ol start="10" style="list-style-type: lower-alpha;"><li>The display of the burning process is as follows:~</~~Desktop$ '''lspci'''~~li>

~~00:00.0 PCI bridge: Fuzhou Rockchip Electronics Co., Ltd Device 3566 (rev 01)~~<div class="figure">

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

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

[[File:pi3b-~~img89~~img101.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 ~~start="7" style="list-style-type: decimal;"~~>~~<li>The interface after balenaEtcher is opened is as follows:~~</li></ol> ~~<div class="figure">~~ ~~[[File:pi3b-img90.png|406x207px|IMG_256]]~~ ~~</div~~><ol start="89" style="list-style-type: decimal;"><li>The method of ~~using balenaEtcher~~ burning the Linux system in the TF card to ~~burn u-boot~~ the NVMe SSD (this method is equivalent to cloning the system in the ~~SPI Flash of~~ TF card to the ~~development board is as follows:~~NVMe SSD)

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

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

</div></ol>

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

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

</div></ol>

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

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

</div></ol>

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

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

</div></ol>

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

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

</div></ol>

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

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

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

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

</div></ol>

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

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

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

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

</div></ol>

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

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

</div></ol>

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

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

</div></ol><ol start="92" style="list-style-type: ~~decimal~~none;"><li>~~The method~~ b) Then enter the password orangepi of ~~burning~~ the Linux system ~~in the TF card to the NVMe SSD (this method is equivalent to cloning the system in the TF card to the NVMe SSD)<ol style="list-style-type: lower-alpha;"><li>First~~ , and click '''~~Clone drive~~Authenticate'''</li~~></ol></li></ol>~~ ~~<div class="figure"~~>

[[File:pi3b-~~img102~~img113.png~~|386x204px|IMG_256~~]]</ol><ol start="3" style="list-style-type: none;"><li>c) Then click '''Fix'''</li>

[[File:pi3b-img114.png]]</~~div~~ol><ol start="24" style="list-style-type: ~~lower-alpha~~none;"><li>d) Then select ~~the device name of the TF card '''/dev/mmcblk1'''~~NVMe SSD</li~~></ol~~>

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

</div></ol><ol start="35" style="list-style-type: ~~lower-alpha~~none;"><li>e) The display interface after ~~opening the TF card~~ selecting NVMe SSD is as follows:</li~~></ol~~>

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

</div></ol><ol start="46" style="list-style-type: ~~lower-alpha~~none;"><li>f) Then select the '''/dev/nvme0n1p2''' partition, click the right button again, and then select '''~~Select target~~Resize/Move'''</li~~></ol~~>

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

</div></ol><ol start="57" style="list-style-type: ~~lower-alpha~~none;"><li>g) Then ~~click '''Show 2 hidden'''~~ drag the capacity to ~~open more options for storage devices~~the maximum at the position shown in the figure below</li~~></ol~~>

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

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

[[File:pi3b-img120.png]]</~~div~~ol><ol start="610" style="list-style-type: ~~lower-alpha~~none;"><li>j) Then ~~select the device name of the NVMe SSD '''/dev/nvme0n1''', and~~ click '''~~Select~~Apply'''</li~~></ol~~>

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

[[File:pi3b-img122.png]]</ol></li></ol><ol start="713" style="list-style-type: lower-alpha;"><li>At this point, you can use the '''sudo poweroff''' command to shut down. Then ~~click~~ please pull out the TF card, and then short press the power button to turn on, then the Linux system in SPIFlash+NVMe SSD will be started.</li></ol></li></ol><ol start="10" style="list-style-type: decimal;"><li>Step '''~~Flash~~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-~~img106~~img123.png~~|389x264px|IMG_256~~]] </div></ol><ol start="3" style="list-style-type: lower-alpha;"><li>'''After using this method to burn the image, there is no need to manually expand the capacity, and it will automatically expand the capacity at the first startup.'''</li></ol></li></ol> == How to burn Android image to TF card ==

<~~/div><ol start~~span id="~~8" style="list~~method-of-burning-android-image-to-tf-card-through-~~style~~usb2.0-~~type: lower~~burning-~~alpha;~~port">~~<li>Then click '''Yes, I'm sure'''~~</~~li></ol~~span>=== Method of burning Android image to TF card through USB2.0 burning port === # First prepare a TF card with 8GB or larger capacity. The transmission speed of the TF card must be class10 or above. It is recommended to use a TF card of SanDisk and other brands# You also need to prepare a good quality USB2.0 male-to-male data cable

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

</div>

<ol start="3" style="list-style-type: decimal;"><li>Then download Rockchip driver '''DriverAssitant_v5.12.zip''' and burning tool '''RKDevTool_Release_v3.15.zip''' from [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi's data download page''']</li><li>Then download the Android image from [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi's download page'''].<ol style="list-style-type: lower-~~roman~~alpha;"><li>~~Then enter~~ After opening the ~~password orangepi~~ download link of the ~~Linux system on~~ Android image, you can see the ~~development board~~following two types of Android images, please select the image in the '''TF card and ~~it will start burning the Linux~~ eMMC startup image ''' folder to ~~the SSD~~download</li~~></ol~~>

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

</div>

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

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

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

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

[[File:pi3b-img33.png]]</~~div~~ol></li></ol><ol start="118" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The display after burning is as follows:~~Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li~~></ol~~>

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

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

<li>~~Open '''GParted''' first~~First, if connect the development board to the Windows computer through the ~~system does not have Gparted pre~~USB2.0 male-~~installed, please use the apt command~~ to ~~install itorangepi@orangepi:~$ '''sudo apt~~-~~get install -y gparted'''~~male data cable. The position of the USB2.0 programming interface of the development board is shown in the figure below</li~~></ol></li></ol~~>

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

</div></ol>

<li>Then ~~enter~~ make sure that the ~~password orangepi of~~ development board is not inserted into the ~~Linux system,~~ TF card and ~~click '''Authenticate'''~~not connected to the power supply</li><li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:</olli>

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

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

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

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

</div></ol>

<li>Then click '''download'''

[[File:pi3b-img128.png]]</li>

<li>The display after downloading '''rk3566_MiniLoaderAll.bin''' is shown in the figure below

[[File:pi3b-img129.png]]</li>

<li>Then select the storage device as '''SD''', and then click '''Switch Storage'''

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

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

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

</div></ol><ol start="714" style="list-style-type: lower-alpha;"><li>Then ~~drag~~ click the ~~capacity to~~ "'''Upgrade Firmware'''" column of the ~~maximum at the position shown in the figure below~~burning tool</li> [[File:pi3b-img132.png]]</ol><ol start="15" style="list-style-type: lower-alpha;"><li>Then click the "'''Firmware'''" button to select the path of the Android image that needs to be burned</li>

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

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

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

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

<ol ~~start~~style="list-style-type: decimal;"><li>First prepare a TF card with 8GB or larger capacity. The transmission speed of the TF card must be class10 or above. It is recommended to use a TF card of SanDisk and other brands</li><li>Then use the card reader to insert the TF card into the computer</li><li>Then download the SDDiskTool programming tool from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page'''], '''please make sure that the version of the SDDiskTool tool is the latest v1.72.'''</li><li>Then download the Android11 image from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page''']<ol style="list-style-type: lower-alpha;"><li>~~Then click~~ After opening the download link of the Android image, you can see the following two types of Android images, please select the image in the '''~~Apply~~TF card and eMMC startup image'''folder to download</li~~></ol~~>

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

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

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

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

<![[File:pi3b-~~- -->~~img125.png]]~~<ol start="10" style="list-style-type: decimal;"><li>Step '''9)''' is to clone the system in the TF card to the NMVe SSD. We can also directly burn the Linux image file to the NVMe SSD. Here are the steps:~~<ol ~~style="list-style-type: lower-alpha;"~~>~~<li>Upload the Linux image file to the Linux system of the development board</li><li>Then use balenaEtcher to burn~~</li></ol>

</li></ol>

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

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

[[File:pi3b-img135.png]]<~~div class~~/ol><ol start="7" 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-~~img123~~img136.png~~|529x333px|图片1~~]]</ol><ol start="8" style="list-style-type: decimal;"><li>After confirming the drive letter, you can format the TF card first, click the '''restore disk button''' in '''SDDiskTool,''' or use the '''SD Card Formatter''' mentioned above to format the TF card</li> [[File:pi3b-img137.png]]</ol><ol start="9" 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> [[File:pi3b-img138.png]]</ol></li></ol><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</li> [[File:pi3b-img139.png]]</ol> == How to burn Android image to eMMC ==

~~</div><ol start~~{| class="3wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>'''~~After using this method to burn~~ Note, after burning the imageinto eMMC, ~~there is no need to manually expand~~ if the ~~capacity~~test finds that it cannot be started, please clear the SPIFlash and ~~it will automatically expand~~ try again. For the ~~capacity at~~ method of clearing SPIFlash, please refer to [[Orange Pi 3B#Using RKDevTool to clear SPIFlash|the ~~first startup~~method of using RKDevTool to clear SPIFlash]].'''</libig>|} === Method of burning Android image into eMMC through USB2.0 burning port === {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that all the following operations are performed on a Windows computer.'''</olbig>|}

<~~span id~~ol style="~~how~~list-~~to-burn-android-image-to-tf~~style-~~card~~type: decimal;"><li>The development board reserves an eMMC expansion interface. Before programming the system to eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board.</~~span~~p>~~== How to burn Android image to TF card ==~~The eMMC module and the method of plugging into the development board are as follows:</li>

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

~~# First prepare a TF card with 8GB or larger capacity~~[[File:pi3b-img63. ~~The transmission speed of the TF card must be class10 or above. It is recommended to use a TF card of SanDisk and other brands~~png|800px]]</ol><ol start="2" style="list-style-type: decimal;"># <li>You also need to prepare a good quality USB2.0 male-to-male data cable</li>

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

</div></ol>

<li>Then download Rockchip driver '''DriverAssitant_v5.12.zip''' and burning tool '''RKDevTool_Release_v3.15.zip''' from [http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/~~index~~computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi's data download page''']</li><li>Then download the Android image from '''[http://www.orangepi.org/html/~~serviceAndSupport~~hardWare/computerAndMicrocontrollers/service-and-support/~~index~~Orange-Pi-3B.html ~~'''~~Orange Pi's download page].'''].

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

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

</div></ol>

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

</li></ol>

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

<li>Then use ~~the~~ decompression software to decompress the compressed package of the downloaded Android image. Among the decompressed files, the file ending with ".img" is the Android image file, and the size is more than 1GB</li><li>Then use ~~the~~ decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>~~</ol>~~ ~~[[File:pi3b-img31.png|575x169px]]~~

[[File:pi3b-img31.png]]

</ol>

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

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

[[File:pi3b-img32.png]]

</ol>

<li>After waiting for a period of time, a pop-up window will prompt "'''~~The~~ driver is installed successfully'''", and then click the "'''OK'''" button.</li>~~</ol>~~ ~~[[File:pi3b-img33.png|315x164px]]~~

[[File:pi3b-img33.png]]

</ol>

</li></ol>

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

[[File:pi3b-img34.png]]

</ol>

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

[[File:pi3b-img35.png]]

</ol>

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

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

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

</div></ol>

<li>Then make sure that the development board is not inserted into the TF card and not connected to the power supply</li>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:</li>~~</ol>~~ ~~[[File:pi3b-img37.png|289x100px]]~~

[[File:pi3b-img37.png]]

</ol>

<li>Then connect the power supply of the Type-C interface to the development board~~, and power on~~</li>~~</ol>~~ ~~[[File:pi3b-img38.png|305x94px]]~~

[[File:pi3b-img38.png]]

</ol>

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"[[File:pi3b-img39.png]]</li><li>Then please select '''Advanced Features'''[[File:pi3b-img126.png]]</li><li>Then click the position shown in the figure below[[File:pi3b-img127.png]]</li></ol>

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

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

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

[[File:pi3b-~~img130~~img132.png~~|477x222px|D~T2CO%X~K2@ELR98)BVP~2~~]]</ol><ol start="14" style="list-style-type: lower-alpha;"><li>Then click the "'''Firmware'''" button to select the path of the Android image that needs to be burned</li>

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

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

</div></ol></li></ol ~~start~~> === How to burn Android11 image into eMMC via TF card === {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~Then click the "~~'''~~Upgrade Firmware~~Note that all the following operations are performed on a Windows computer.'''~~" column of the burning tool~~</~~li></ol~~big>|}

~~[[File~~# The development board reserves an eMMC expansion interface. Before programming the system to eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The eMMC module and the method of plugging into the development board are as follows:~~pi3b-img132.png|477x224px]]~~

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

::[[File:pi3b-~~img133~~img63.png|~~444x209px~~800px]]

<ol start="162" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Finally, click~~ You also need to prepare a TF card with 8GB or larger capacity. The transmission speed of the TF card must be class10 or above. It is recommended to use a TF card of SanDisk and other brands</li><li>Then use the card reader to insert the TF card into the computer</li><li>Then download the SDDiskTool programming tool from the ~~"~~[http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''~~Upgrade~~Orange Pi data download page'''~~" button to start burning~~], ~~and~~ '''please make sure that the ~~log during~~ version of the ~~burning process~~ SDDiskTool tool is ~~shown in~~ the ~~figure below~~latest v1. ~~After burning is completed,~~ 72'''</li><li>Then download the Android ~~system will start automatically~~image from [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi's download page''']<ol style="list-style-type: lower-alpha;"><li>After opening the download link of the Android image, you can see the following two types of Android images, please select the image in '''the TF card and eMMC startup image folder''' to download</olli>

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

</div></ol><~~span id~~ol start="2" style="~~how~~list-tostyle-~~use~~type: lower-~~sddisktool~~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-~~to-burn-android~~style-type: none;"><li>a) The first image-is dedicated to~~-tf-card"~~HDMI display and supports 4K display. If you don't use LCD screen, please download the image without lcd</~~span~~li>~~=== How~~ <li>b) If you want to use ~~SDDiskTool to burn Android~~ lcd screen, please choose image ~~to TF card ===~~with lcd</li>

~~<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 the card reader to insert the TF card into the computer</li><li>Then download the SDDiskTool programming tool from the~~ [~~http~~[File:~~//www~~pi3b-img125.~~orangepi.org/html/serviceAndSupport/index.html '''Orange Pi data download page'''~~png]]~~, '''please make sure that the version of the SDDiskTool tool is the latest v1.72.'''</li><li>Then download '''the Android11 image from the Orange Pi 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]]<~~blockquote~~/ol><~~div class~~ol start="~~figure~~8"style="list-style-type: decimal;"><li>After opening '''SDDiskTool''', if the TF card is recognized normally, the inserted disk device will be displayed in the "'''Select Removable Disk Device'''" column. '''Please make sure that the displayed disk device is consistent with the drive letter of the TF card you want to burn''', if there is no display, you can try to unplug the TF card.</li>

[[File:pi3b-~~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></blockquote~~ol><ol start="210" style="list-style-type: decimal;"><li>Then start to write the Android image into the TF card<ol style="list-style-type: lower-alpha;"><li>~~After entering~~ First confirm that the displayed drive letter is the drive letter corresponding to the TF card under "'''Select Removable Disk Device'''"</li><li>Then select "'''Firmware Upgrade'''" in "'''~~TF card and eMMC boot image~~Select Function Mode''' ~~folder, you can see~~ "</li><li>Then select the path of the ~~following two images,~~ Android firmware in the ~~difference between them is:~~"'''Select Upgrade Firmware'''" column</li><li>Finally click the "'''Start Create'''" button to start burning</olp></li>

[[File:pi3b-img143.png]]</ol><~~!-- --~~/li></ol><ol start="11" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The image without lcd~~ After the burning is ~~specially used for HDMI~~ completed, the display ~~and supports 4K display. If you do not use~~ is as shown in the ~~LCD screen~~figure below, ~~please download the image without lcd</li><li>If~~ and then you ~~want to use LCD screen, please choose image with lcd~~can exit SDDiskTool</li~~></ol~~>

[[File:pi3b-~~img125~~img144.png~~|281x62px~~]]</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 ~~compressed package of the downloaded Android image. Among~~ HDMI monitor displays the ~~decompressed files~~following information, it means that the ~~file ending with ".img" is~~ burning of the Android image ~~file, and~~ into the ~~size is more than 1GB</li><li>Then use decompression software to decompress '''SDDiskTool_v1~~eMMC has been completed.~~72.zip'''~~At this time, ~~this software does not need to~~ the TF card can be ~~installed~~pulled out, ~~just find '''SD_Firmware_Tool.exe'''~~ and then the Android system in the ~~decompressed folder and open it~~eMMC will start.</li~~></ol~~>

[[File:pi3b-~~img135~~img146.png~~|415x99px~~]]</ol>

~~<ol start~~=~~"7" style~~=~~"list-style-type: decimal;">~~<li>After opening '''SDDiskTool''', if the TF card is recognized normally, the inserted disk device will be displayed in the "'''Select Removable Disk Device'''" column. P'''lease make sure that the displayed disk device is consistent with the drive letter of the TF card you want How to burn~~''', if there is no display, you can try~~ Android image to ~~unplug the TF card</li></ol>~~SPIFlash+NVMe SSD ==

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

<ol ~~start="8"~~ style="list-style-type: decimal;"><li>~~After confirming the drive letter~~First, you ~~can format the TF card first, click the '''restore disk button''' in '''SDDiskTool,''' or use the '''SD Card Formatter''' mentioned above~~ need to ~~format the TF card~~prepare an NVMe SSD solid state drive<ol style="list-style-type: lower-alpha;"><li>The M.2 2230 SSD is as follows</olli>

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

~~<ol start="9" style="list-style-type~~[[File: ~~decimal;"><li>Then start to write the Android image to the TF card<ol style="list~~pi3b-~~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>~~img74.png]]~~<li>Finally click the "Start Create" button to start burning the Android image to the TF card</li>~~</ol>

</li></ol>

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

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

[[File:pi3b-img76.png]]</ol><ol start="104" 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~~ You also need to prepare a good quality USB2.0 male-to ~~start~~-male data cable</li~~></ol~~>

~~[[File:pi3b-img139.png|288x244px]]~~<div class="figure">

~~== How to burn Android image to eMMC ==~~img16.png]]

'''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]]'''.''' ~~~~</~~span>=== Method of burning Android image into eMMC through USB2.0 burning port ===~~ ~~'''Note that all the following operations are performed on a Windows computer.'''~~ ~~<ol style="list-style-type: decimal;">~~<li>The development board reserves an eMMC expansion interface. Before programming the system to eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board.~~The eMMC module and the method of plugging into the development board are as follows:</li~~div></ol> ~~[[File:pi3b-img61.png|115x84px]] [[File:pi3b-img62.png|120x87px]]~~ ~~[[File:pi3b-img63.png|286x133px]]~~ <ol start="~~2" style="list-style-type: decimal;"><li>You also need to prepare a good quality USB2.0 male-to-male data cable</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img16.png|141x138px|D6BB9058-CDC3-42d7-A7FC-FBF630D886B7]]~~ ~~</div><ol start="3~~5" style="list-style-type: decimal;"><li>Then download Rockchip driver '''DriverAssitant_v5.12.zip''' and burning tool '''RKDevTool_Release_v3.15.zip''' from ~~[http://www.orangepi.org/html/serviceAndSupport/index.html~~ '''Orange Pi's data download page''']</li><li>Then download the ~~Android~~ image ~~from '''[http://www.orangepi.org/html/serviceAndSupport/index.html Orange Pi's download page].'''~~of Android11

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

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

</div>

</ol>

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

</li></ol>

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

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

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

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

[[File:pi3b-img32.png]]

</ol>

<li>After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button.</li>~~</ol>~~ ~~[[File:pi3b-img33.png|315x164px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li></ol>~~ ~~[[File:pi3b-img34.png|454x134px]]~~

[[File:pi3b-img33.png]]

</ol>

</li></ol>

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

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

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

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

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

</div></ol>

<li>~~Then make~~ Make sure that the development board is not inserted into the TF card and not connected to the power supply</li><li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:</li>~~</ol>~~ ~~[[File:pi3b-img37.png|289x100px]]~~

[[File:pi3b-img37.png]]

</ol>

<li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button</li>~~</ol>~~ ~~[[File:pi3b-img38.png|305x94px]]~~

[[File:pi3b-img38.png]]

</ol>

<li~~><p~~>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"~~[[File:pi3b-img39.png|457x215px]]~~</li>~~<li>Then please select '''Advanced Features'''[[File:pi3b-img126.png|458x138px]]</li><li>Then click the position shown in the figure below[[File:pi3b-img127.png|459x216px]]</li></ol~~>

[[File:pi3b-img39.png]]<~~!-- --~~/ol><ol start="6" style="list-style-type: lower-alpha;"><li>~~Select~~ Then click the "'''~~rk3566_MiniLoaderAll.bin~~Upgrade Firmware''' in " column of the ~~MiniLoader folder downloaded earlier, and click to open.~~burning tool</li~~></ol~~>

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

[[File:pi3b-~~img68~~img133.png~~|459x216px|SIS5H0S2@F5M2D(6ANZEUPG~~]]</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>

~~</div><ol start="2" style="list-style-type: lower-alpha;"><li>Then click '''Download'''~~[[File:pi3b-~~img128~~img148.png~~|472x222px~~]]~~</li><li>The display after downloading '''MiniLoaderAll.bin''' is shown in the figure below~~</pol>~~[[File:pi3b-img140.png|474x223px]]~~</~~li>~~<li>~~Then select the storage device as '''EMMC''', and then click Switch '''Storage'''~~</pol><~~p>[[File:pi3b~~span id="using-rkdevtool-to-clear-~~img141.png|468x225px]]</p~~spiflash"></~~li><li>The display of successful switching is shown in the figure below</li></ol~~span>

~~[[File:pi3b-img142.png|472x227px]]~~== Using RKDevTool to clear SPIFlash ==

~~<ol start="8" style="list-style-type: lower-alpha;"><li>Then click~~ # The position of SPI Flash on the ~~"'''Upgrade Firmware'''" column of~~ development board is shown in the ~~burning tool</li></ol>~~figure below

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

~~<ol style="list-style-type: lower-roman;"><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 start="102" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Finally~~First, ~~click the "'''Upgrade'''" button~~ you need 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~~prepare a good quality USB2.0 male-to-male data cable</li~~></ol~~>

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

</div></ol><~~span id~~ol start="3" style="~~how~~list-tostyle-~~burn~~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/hardWare/computerAndMicrocontrollers/service-~~android11~~and-~~image~~support/Orange-~~into~~Pi-~~emmc~~3B.html '''Orange Pi data download page''']<ol style="list-~~via~~style-tftype: lower-~~card~~alpha;"><li>On the download page of Orange Pi, first select the official tool, and then enter the following folder</~~span~~li>~~=== How to burn Android11 image into eMMC via TF card ===~~

~~'''Note that all the following operations are performed on a Windows computer.'''~~<div class="figure">

# 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[[File:pi3b-img149. ~~The eMMC module and the method of plugging into the development board are as follows:~~png]]

~~[[File:pi3b-img61.png|115x84px]] [[File:pi3b-img62.png|120x87px]]~~ ~~[[File:pi3b-img63.png|286x133px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>You also need to prepare a TF card with 8GB or larger capacity. The transmission speed of the TF card must be class10 or above. It is recommended to use a TF card of SanDisk and other brands~~</pdiv></~~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 '''Orange Pi data download page'''], '''please make sure that the version of the SDDiskTool tool is the latest v1.72'''</li>~~<li>Then download the Android image from [http://www.orangepi.org/html/serviceAndSupport/index.html '''Orange Pi's download page''']</p~~ol><ol start="2" style="list-style-type: lower-alpha;"><li>~~After opening the~~ Then download ~~link of the Android image, you can see~~ all the ~~following two types of Android images, please select the image in '''the TF card and eMMC startup image folder''' to download~~files below</li~~></ol></li></ol~~>

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

</div>

~~<ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <~~li><p~~big>~~After entering~~ '''Note that the "MiniLoader-things needed to burn the ~~TF card and eMMC boot~~ Linux image " folderis hereinafter referred to as the MiniLoader folder.'''~~, you can see the following tow images, the difference between them is:~~</pbig>~~<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>

<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-~~img125~~img31.png~~|283x62px~~]]</ol><ol start="5" style="list-style-type: decimal;"><li>After opening DriverInstall.exe, the steps to install the Rockchip driver are as follows<ol style="list-style-type: lower-alpha;"><li>Click the "'''Driver Installation'''" button</li> [[File:pi3b-img32.png]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button.</li> [[File:pi3b-img33.png]]</ol></li></ol>

<li~~><p~~>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~~RKDevTool_Release_v3.7215.zip''', this software does not need to be installed, just find '''~~SD_Firmware_Tool.exe~~RKDevTool''' in the decompressed folder and open it~~~~</li~~></ol~~>

[[File:pi3b-~~img135~~img34.png~~|429x103px~~]]</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>

<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~~p>~~</ol>~~ ~~[[File:pi3b-img136.png|267x228px]]~~ ~~<ol start="9" style="list-style-type: decimal;"><li>After confirming the drive letter,~~ Then you can ~~format the TF card first, click the '''restore disk button''' in SDDiskTool, or use the '''SD Card Formatter''' mentioned above to format the TF card</li></ol>~~ ~~[[File:pi3b-img137.png|247x212px]]~~ ~~<ol start="10" style="list-style-type: decimal;"><li>Then~~ start to ~~write~~ clear the ~~Android image into the TF card~~content in SPI FLASH

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

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

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

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

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

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

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

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

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

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

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

</li></ol>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<~~div~~ ol start="2" style="list-style-type: decimal;"><li>Then use the following command to install putty on Ubuntu PC</li>{| class="~~figure~~wikitable" style="width:800px;">|-| test@test:~$ '''sudo apt-get update'''

~~[[File~~test@test:~~pi3b~~~$ '''sudo apt-~~img36.png~~get install -y putty'''|~~275x116px|C~~}</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'''|}</~~div~~ol><ol start="24" style="list-style-type: ~~lower-alpha~~decimal;"><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~~ After executing the ~~development board~~putty command, the ~~position of the MaskROM button on the development board is shown in the figure below:~~following interface will pop up</li~~></ol~~>

[[File:pi3b-~~img37~~img158.png~~|289x100px~~]]</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="46" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~connect~~ set the ~~power supply~~ parameters of the ~~Type~~serial port<ol style="list-style-~~C interface~~ type: lower-alpha;"><li>Set Serial line to connect toas /dev/ttyUSB0（(Modified to the ~~development board~~corresponding node name, ~~and power on, and then release the MaskROM button~~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-img38.png|305x94px]]~~<div class="figure">

~~<ol start="5" style="list-style-type~~[[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>img160.png]]

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

<~~ol start~~div class="6figure" ~~style="list-style-type: lower-alpha;"><li>Then click the "'''Upgrade Firmware'''" column of the burning tool</li></ol~~>

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

</div></ol></li></ol><ol start="78" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then click~~ After starting the ~~"'''Firmware'''" button to select~~ development board, you can see the Log information output by the system from the ~~Android image to be burned~~opened serial port terminal</li~~></ol~~>

[[File:pi3b-~~img133~~img162.png~~|444x209px~~]]</ol>

~~<ol start~~=~~"8" style~~=~~"list-style-type: lower-alpha;"><li>Finally, click the "Upgrade" button~~ = How to ~~start burning. The burning process is shown in~~ use the ~~figure below. You can see that the firmware will be burned to SPIFlash first, and then burned to PCIE. After burning is completed, the Android system will start automatically.</li></ol>~~debugging serial port on Windows platform ===

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-~~img148~~| <big>'''There are many serial port debugging software that can be used under Windows, such as SecureCRT, MobaXterm, etc. The following demonstrates how to use MobaXterm.~~png~~This software has a free version and can be used without buying a serial number.'''</big>|~~453x212px]]~~} <~~span id~~ol style="~~using~~list-style-~~rkdevtool~~type: decimal;"><li>Download MobaXterm<ol style="list-tostyle-~~clear~~type: lower-~~spiflash~~alpha;"><li>Download MobaXterm website as follows</~~span~~li>{| class="wikitable" style= ~~Using RKDevTool to clear SPIFlash~~ "width:800px;" |-| [https://mobaxterm.mobatek.net/ '''https://mobaxterm.mobatek.net''']|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>After entering the MobaXterm download page, click '''GET XOBATERM NOW!'''</li>

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

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

[[File:pi3b-img165.png]]

</ol>

</li></ol>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

</li></ol>

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

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

<~~/div><ol start~~span id="~~2" style="list~~supported-linux-image-~~style~~types-~~type: lower~~and-~~alpha;~~kernel-versions">~~<li>Make sure that the development board is not inserted into the TF card and not connected to the power supply~~</~~p></li~~span>~~<li>Then press~~ == Supported Linux image types and ~~hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:</li></ol>~~kernel versions ==

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

<~~ol start~~span id="~~4" style="list-style~~linux-~~type: lower~~system-~~alpha;~~adaptation">~~<li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button</li~~></olspan>== Linux System adaptation ==

~~[[File:pi3b-img38.png~~{|~~305x94px]]~~ ~~<ol start~~class="5wikitable" style="~~list~~width:800px;text-~~style-type~~align: ~~lower-alpha~~center;">~~<li>If the previous steps are successful, the development board will enter the~~ |-|'''Function'''|'''Debian11'''|'''Ubuntu20.04'''|'''Ubuntu22.04'''|-|'''USB2.0x3'''|'''OK'''|'''OK'''|'''OK'''|-|'''~~MASKROM~~USB3.0x1'''|' ~~mode at this time, and the~~ ''OK'''|'''OK'''|'''OK'''|-|'''M.2 NVMe SSD Start'''|'''OK'''|'''OK'''|'''OK'''|-|'''WIFI'''|'''OK'''|'''OK'''|'''OK'''|-|'''Bluetooth'''|'''OK'''|'''OK'''|'''OK'''|-|'''GPIO（40pin）'''|'''OK'''|'''OK'''|'''OK'''|-|'''UART（40pin）'''|'''OK'''|'''OK'''|'''OK'''|-|'''SPI（40pin）'''|'''OK'''|'''OK'''|'''OK'''|-|'''I2C（40pin）'''|'''OK'''|'''OK'''|'''OK'''|-|'''PWM（40pin）'''|'''OK'''|'''OK'''|'''OK'''|-|'''PWM fan interface ~~of the burning tool will prompt "~~'''~~found a MASKROM device~~|'''OK'''|'''OK'''|'''OK'''|-|'''3pin Debug serial port'''|'''OK'''|'''OK'''~~"</li></ol>~~|'''OK'''~~[[File:pi3b~~|-~~img39.png~~|'''EMMC'''|'''OK'''|'''OK'''|~~457x215px]]~~'''OK'''|-~~<ol~~ |'''TF card start~~="6" style="list~~'''|'''OK'''|'''OK'''|'''OK'''|-|'''HDMI Video'''|'''OK'''|'''OK'''|'''OK'''|-|'''HDMI Audio'''|'''OK'''|'''OK'''|'''OK'''|-|'''Camera'''|'''OK'''|'''OK'''|'''OK'''|-|'''LCD'''|'''OK'''|'''OK'''|'''OK'''|-|'''Edp Display'''|'''OK'''|'''OK'''|'''OK'''|-~~style~~|'''Gigabit Ethernet port'''|'''OK'''|'''OK'''|'''OK'''|-~~type: lower~~|'''Network port status light'''|'''OK'''|'''OK'''|'''OK'''|-~~alpha;"><li>Then please select~~ |'''headphone playback'''|'''OK'''|'''OK'''|'''~~Advanced Features~~OK'''~~[[File:pi3b~~|-~~img126.png~~|'''headphone recording'''|~~458x138px]]</li>~~'''OK'''~~<li>Then click the position shown in the figure below~~|'''OK'''~~[[File:pi3b~~|'''OK'''|-~~img127.png~~|'''LED Light'''|'''OK'''|~~459x216px]]</li>~~'''OK'''~~<li>Select~~ |'''~~rk3566_MiniLoaderAll.bin~~OK''' ~~in the~~ |-|'''~~MiniLoader~~RTC''' ~~folder you downloaded earlier, and click Open</li></ol>~~|'''OK'''~~<div class="figure">~~|'''OK'''|'''OK'''~~[[File:pi3b~~|-~~img68.png~~|~~459x216px~~'''GPU'''|~~SIS5H0S2@F5M2D(6ANZEUPG]]~~'''OK'''|'''OK'''~~</div>~~|'''OK'''~~<ol style="list~~|-~~style~~|'''NPU'''|'''OK'''|'''OK'''|'''OK'''|-~~type: lower~~|'''VPU'''|'''OK'''|'''OK'''|'''OK'''|-~~roman;"><li>Then click~~ |'''watchdog test'''|'''OK'''|'''OK'''|'''~~Download~~OK'''~~[[File:pi3b~~|-~~img128.png~~|'''Chromium Hard solution video'''|'''OK'''|'''OK'''|'''OK'''|~~472x222px]]</li></ol>~~}

<~~ol start~~span id="~~10" style="list~~the-~~style~~format-~~type: lower~~of-~~alpha;"><li>The display after downloading '''rk3566_MiniLoaderAll.bin''' is shown in the figure below[[File:pi3b~~linux-~~img140.png|474x223px]]</li><li>Then select the storage device as '''SPINOR'''[[File:pi3b~~commands-~~img151.png|467x220px]]</li><li>Then click Switch '''Storage'''[[File:pi3b~~in-~~img152.png|464x218px]]</li><li>Then click '''Erase All''' to start erasing SPIFlash[[File:pi3b~~this-~~img153.png|467x220px]]</p~~manual"></lispan>~~<li>~~== The ~~display log after erasing SPIFlash is shown~~ format of Linux commands in ~~the figure below[[File:pi3b-img154.png|460x216px]]</li></ol>~~this manual ==

~~<span id~~# In this manual, all commands that need to be entered in the Linux system will be marked with the following box::{| class="wikitable" style="~~start~~width:800px;height:40px;" |-~~the-orange-pi-development-board">== Start the Orange Pi development board ==~~|

# Insert the TF card with the burned image into the TF card slot of the Orange Pi development board. If the image of SPIFlash+NVMe SSD has been burnt, then there is no need to insert a TF card, just make sure that the NVMe SSD is inserted into the development board normally.|}~~# The development board has an HDMI interface~~::As shown below, ~~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~~ content in the ~~LCD screen to display~~ yellow box indicates the ~~system interface of the development board. If there is a Type-C to HDMI cable~~content that needs special attention, except for the ~~system interface of the development board can also be displayed through the Type-C interface~~commands in it.::{| class="wikitable" style="background-color:# ~~Connect a USB mouse and keyboard to control the Orange Pi development board.~~ffffdc;width:800px;height:40px;" ~~# The development board has an Ethernet port, which can be plugged into a network cable for Internet access.~~|-~~# Connect a high-quality power adapter with a 5V/3A or 5V/4A USB Type-C interface.~~|

~~'''Remember~~ |}<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 ~~to plug~~ part of the Linux command, so when entering the command in ~~a power adapter with a voltage output greater than 5V~~the Linux system, ~~as this will burn out~~ please do not enter the content of the ~~development board.~~red font part</li>{| class="wikitable" style="width:800px;" |-| '''orangepi@orangepi:~$ sudo apt update'''

'''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 againroot@orangepi:~#''' '''vim /boot/boot.cmd'''

'''~~The Type-C power port does not support PD negotiation~~test@test:~$ ssh [mailto:root@192.168.1.36 root@192.168.1.]xxx'''

'''~~In addition, please do not connect~~ root@test:~# ls'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>'''root@orangepi:~$''' The prompt indicates that this command is entered in '''the ~~USB interface~~ Linux system of ~~the computer to power~~ 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>~~6) Then turn on~~ <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 ~~switch~~ current user of the ~~power adapter~~system is an ordinary user. ~~If everything~~ When executing privileged commands, sudo needs to be added '''sudo'''</li><li>'''root@test:~#''' The prompt indicates that this command is ~~normal~~entered in the Ubuntu PC or Ubuntu virtual machine, ~~you can see~~ not in the Linux system of the development board. The # at the end of the prompt indicates that the ~~startup screen~~ current user of the system on is the root user and can execute any command you want</li></ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>What are the commands that need to be entered?<ol style="list-style-type: lower-alpha;"><li>As shown below, '''the black bold part''' is the command that needs to be input, and the content below the command is the ~~HDMI monitor or LCD screen~~output content (some commands have output, some may not), and this part of the content does not need to be input</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''cat /boot/orangepiEnv.txt'''

7) If you want to view the output information of the system through the debugging serial port, please use the serial cable to connect the development board to the computer. For the connection method of the serial port, please refer to '''~~[[\l|the section on how to use the debugging serial port]].~~verbosity=7'''

~~== How to use the debugging serial port =~~bootlogo=false

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

~~<ol style~~'''"deb [arch=~~"list~~$(dpkg -~~style~~-~~type: decimal;"><li>First, you need to prepare a 3.3V USB~~print-~~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.''''''Before purchasing a USB to TTL module, please confirm that the module supports a baud rate of 1500000.~~architecture) \'''~~</li></ol>~~

~~<div class~~'''signed-by=~~"figure">~~/usr/share/keyrings/docker-archive-keyring.gpg] \'''

~~[[File~~'''https:~~pi3b-img155~~//download.~~png|576x115px|07]]~~docker.com/Linux/debian \'''

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

~~[[File:pi3b-img156.png|428x110px]]~~== Linux system login instructions ==

<~~ol start~~span id="~~3" style="list~~linux-system-default-login-account-~~style~~and-~~type: decimal;~~password"><li/span>~~The GND, TXD~~ === Linux system default login account 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>~~password ===

~~<blockquote>a. Connect the GND of the USB to TTL module to the GND of the development board~~{| class="wikitable" style="width:800px;text-align: center;"|-|'''Account'''|'''Passport'''|-|'''root'''|'''orangepi'''|-|'''orangepi'''|'''orangepi'''|}

b{| 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. ~~The~~ '''~~RX of~~ </big>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''When the ~~USB to TTL module~~ wrong password is ~~connected to~~ prompted, or there is a problem with the ssh connection, please note that as long as you are using the Linux image provided by Orange Pi, please do not suspect that the TXabove password is wrong, but look for other reasons.''' ~~of the development board~~</big>|}

~~c. The '''TX of the USB to TTL module is connected to the TX''' of the development board</blockquote>~~<~~ol start~~span id="~~4" style="list~~how-to-set-automatic-terminal-login-in-~~style~~linux-~~type: decimal;~~system">~~<li>The schematic diagram of connecting the USB to TTL module to the computer and the Orange Pi development board is as follows</li~~></olspan>

~~<div class~~=~~"figure">~~== How to set automatic terminal login in Linux system ===

~~[[File:pi3b-img157.png|524x189px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\USB-to-TTL-module-~~# The Linux system automatically logs in to-the~~-computer.jpgUSB-to-TTL-module-to-~~terminal by default, and the~~-computer]]~~default login user name is '''orangepi'''

~~</div>'''The TX and RX of the serial port need to be cross~~::[[File:pi3b-~~connected~~img171. 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 right'''png]]

<~~span id~~ol start="2" style="~~how~~list-style-type: decimal;"><li>Use the following command to set the root user to automatically log in to~~-use-~~theterminal</li>{| class="wikitable" style="width:800px;" |-~~debugging~~| orangepi@orangepi:~$ '''sudo auto_login_cli.sh root'''|}</ol><ol start="3" style="list-~~serial-port-on~~style-type: decimal;"><li>Use thefollowing command to disable automatic login terminal</li>{| class="wikitable" style="width:800px;" |-~~ubuntu~~| orangepi@orangepi:~$ '''sudo auto_login_cli.sh -~~platform">~~d'''|}</~~span~~ol><ol start="4" style=~~= How~~ "list-style-type: decimal;"><li>Use the following command to ~~use~~ set the ~~debugging serial port on~~ orangepi user to automatically log in to the ~~Ubuntu platform~~ terminal again</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo auto_login_cli.sh orangepi'''|}</ol>

~~'''There are many serial port debugging software that can be used under~~ === Instructions for automatic login of Linux~~, such as putty, minicom, etc. The following demonstrates how to use putty.'''~~desktop version system ===

# ~~First~~After the desktop system starts, ~~insert the USB-~~it will automatically log in to~~-TTL module into~~ the USB interface of the Ubuntu computer. If the connection and recognition of the USB-to-TTL module is normal, you can see the corresponding device node name under '''/dev''' on the Ubuntu PC. Remember this node name, and then set the serial port software will be useddesktop without entering a password

~~test@test:~$ '''ls /dev/ttyUSB*'''~~<div class="figure">

~~/dev/ttyUSB0~~::[[File:pi3b-img172.png]]

</div>

<li>~~Then use~~ Run the following command to ~~install putty on Ubuntu PC~~prohibit the desktop system from automatically logging into the desktop</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo disable_desktop_autologin.sh'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then restart the system and a login dialog box will appear, at which point a [[\l|password]] is required to enter the system<div class="figure">

~~test@test~~[[File:~~~$ '''sudo apt~~pi3b-~~get update'''~~img173.png]] </div></li></ol>

~~test@test:~$ '''sudo apt~~

~~<ol start~~=~~"3" style~~=~~"list-style-type: decimal;"><li>Then run putty, '''remember to add sudo permission'''</li></ol>~~= The setting method of root user automatic login in Linux desktop version system ===

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

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

~~[[File~~<ol start="2" style="list-style-type:~~pi3b-img158.png|367x321px]]~~decimal;"><li>Then restart the system, and the root user will automatically log in to the desktop</li>

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

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

'''Also note that this is not a bug, since pulseaudio is not allowed to run as root.'''<~~ol start="6" style="list-style-type: decimal;"~~/big>~~<li>Then set the parameters of the serial port~~|}</pol><ol start="3" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Set Serial line~~ Execute the following command to ~~connect toas /dev/ttyUSB0（(Modified~~ set the desktop system to log in automatically with the ~~corresponding node name, generally /dev/ttyUSB0）</li><li>Set Speed(baud) as '''1500000'''（Serial port baud rate）~~orangepi user again</li>~~<li>Set Flow control as None</li></ol></li></ol~~>

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

~~[[File:pi3b-img160.png|317x312px|09]]~~=== The method of disabling the desktop in the Linux desktop version system ===

~~</div><ol start="7" style="list-style-type: decimal;"><li>After setting~~ # First enter the ~~setting interface of~~ following command on the ~~serial port~~command line, ~~return to the Session interface~~'''<ol span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<li>First select the Connection type as Serial</li><li>Then click the Open button to connect~~ Please remember to ~~the serial port</li></ol></li>~~add sudo permission</olspan>'''

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

~~[[File~~<ol start="2" style="list-style-type:~~pi3b-img161.png|345x340px|10]]~~decimal;"><li>Then restart the Linux system and you will find that the desktop will not be displayed</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo reboot'''|}</~~div~~ol><ol start="83" style="list-style-type: decimal;"><li>~~After starting~~ The steps to reopen the ~~development board, you can see~~ desktop are as follows:<ol style="list-style-type: lower-alpha;"><li>First enter the ~~Log information output by~~ following command on the ~~system from the opened serial port terminal~~command line, '''Please remember to add sudo permission</lispan>'''</olli>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img162~~| orangepi@orangepi:~$ '''sudo systemctl start lightdm.~~png~~service'''|~~468x340px]]~~}</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>

~~=== How to use the debugging serial port on Windows platform ===~~

'''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.'''== Onboard LED Light Test Instructions ==

~~<ol style="list-style-type~~# 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: ~~decimal;"><li>Download MobaXterm<ol style="list-style-type: lower-alpha;"><li>Download MobaXterm website as follows</li></ol></li></ol>~~

~~[https://mobaxterm.mobatek.net/ https://mobaxterm.mobatek.net]~~<div class="figure">

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

</div>

<li>'''As long as the development board is powered on, the red LED light will always be on, which is controlled by the hardware and cannot be turned off by the software'''</li>

<li>The green LED light will keep blinking after the kernel is started, which is controlled by software.</li>

<li>The PCIe indicator will flash when there is data transmission on the PCIe interface.</li>

<li>The method of setting the green light on and off and flashing is as follows

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

|-

|

<big>'''Note that the following operations should be performed under the root user.'''</big>

|}

<li>First enter the setting directory of the green light</li>

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

|-

|

root@orangepi:~# '''cd /sys/class/leds/status_led'''

|}

</ol>

<li>~~After entering~~ The command to set the ~~MobaXterm download page, click~~ green light to stop flashing is as follows</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/sys/class/leds/status_led# '''~~GET XOBATERM NOW!~~echo none > trigger'''|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The command to set the green light to be on is as follows</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/sys/class/leds/status_led# '''echo default-on > trigger'''|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>The command to set the green light to flash is as follows</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/sys/class/leds/status_led# '''echo heartbeat > trigger'''|}</ol></li></ol>

~~[[File:pi3b-img163.png|576x334px]]~~== Network connection test ==

<~~ol start~~span id="~~3" style="list~~ethernet-~~style~~port-~~type: lower-alpha;~~test">~~<li>Then choose to download the Home version~~</~~li></ol~~span>=== Ethernet port test ===

~~[[File~~# First, insert one end of the network cable into the Ethernet interface of the development board, and connect the other end of the network cable to the router, and ensure that the network is unblocked# After the system starts, it will automatically assign an IP address to the Ethernet card through DHCP, '''No other configuration is required'''# The command to view the IP address in the Linux system of the development board is as follows

~~<ol start~~::{| class="4wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Then select the Portable version. After downloading, you don’t need to install it, just open it and use it</li></ol>~~|-| orangepi@orangepi:~$ '''ip addr show eth0'''

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

~~<ol start="2" style="list-style-type~~: ~~decimal;"><li>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<~~link/~~li></ol>~~ether 4a:fe:2b:3d:17:1c brd ff:ff:ff:ff:ff:ff

~~[[File~~:~~pi3b-img166~~inet '''192.168.1.150'''/24 brd 192.168.1.~~png|576x81px]]~~255 scope global dynamic noprefixroute eth0

~~<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), if you can’t see the port number, please use '''Driver Master''' to scan and install the driver for the USB to TTL serial port chip</li>~~<li>Select the baud rate of the serial port as '''1500000'''</li><li>Finally click the "'''OK'''" button to complete the setting</li></ol></li></ol>~~valid_lft 43150sec preferred_lft 43150sec

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

~~[[File~~:~~pi3b-img167.png|575x438px~~:valid_lft forever preferred_lft forever|~~11]]~~}

~~</div><ol start~~::{| class="4wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~After clicking the "~~'''~~OK'''" button~~When using ifconfig to view the IP address, ~~you will enter~~ if the following ~~interface~~information is displayed, it is because sudo is not added. ~~At this time, start the development board and you can see the output information of the serial port</li>~~The correct command is: sudo ifconfig'''</olbig>

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

~~[[File~~orangepi@orangepi:~~pi3b-img168.png|575x291px|12]]~~~$ '''ifconfig'''

~~</div>== Instructions for using the 5v pin~~ Command 'ifconfig' is available in the ~~40pin interface of the development board to supply power ==~~following places

~~'''The power supply method we recommend for the development board is to use the 5V~~* /~~3A or 5V~~sbin/4A Type C interface power cord to plug into the Type-C power interface of the development board for power supply. If you need to use the 5V pin in the 40pin interface to power the development board, please make sure that the power cord and power adapter used can meet the power supply requirements of the development board. If the use is unstable, please switch back to the Type-C power supply.'''ifconfig

~~# First, you need to prepare a power cord as shown in the figure below~~* /usr/sbin/ifconfig

~~<div class="figure">~~The command could not be located because '/sbin:/usr/sbin' is not included in the PATH environment variable.

~~[[File:pi3b-img169~~This is most likely caused by the lack of administrative privileges associated with your user account.~~png|151x108px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-7.jpg未标题-7]]~~

~~</div>~~ifconfig: command not found~~'''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;">~~<li>Use the 5V pin in the 40pin interface to supply power to the development board. The connection method of the power line is as follows~~|-~~<ol style="list-style-type: lower-alpha;">~~| <~~li><p~~big>~~The USB A port of the power cord shown in the above picture needs to be plugged into the 5V/3A or 5V4A power adapter connector ('''please do not plug into the computer’s USB port for power supply~~'''~~)</li><li>The red DuPont line needs~~ There are three ways to ~~be plugged into~~ check the ~~5V pin of~~ IP address after 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></ol></li></ol>~~starts:'''

~~[[File:pi3b-img170~~'''1.~~png|365x71px]]~~Connect the HDMI 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'''

= '''~~Instructions for use~~ 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 ~~Ubuntu/Debian Server and Xfce desktop system~~the development board normally. If you can't see it, the debug method looks like this:''' =

<ol style="list-style-type: upper-alpha;"><li>'''~~The content~~ First check whether the Linux system has started normally. If the green light of ~~this chapter~~ the development board is blinking, it is generally started normally. If only the red light is ~~written based~~ 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 ~~images of~~ 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 ~~Linux server version and~~ debugging serial port to view the ~~xfce desktop version.~~IP address'''</li></ol>

~~~~

~~== Supported Linux image types and kernel versions ==~~

~~{| class="wikitable"~~|-~~| style="text-align: left;"|~~ '''~~Linux image type'''| style="text-align: left;"| '''kernel version'''| style="text-align: left;"| '''server version'''| style="text-align: left;"| '''desktop version'''~~|-~~| style="text-align: left;"| '''Debian 11 - Bullseye'''| style="text-align: left;"| '''Linux5.10'''| style="text-align: left;"| '''support'''| style="text-align: left;"| '''support'''~~|-~~| style="text-align: left;"| '''Ubuntu 20.04 - Focal'''| style="text-align: left;"| '''Linux5~~In addition, it should be noted that the development board DHCP automatically assigns an IP address without any settings.~~10'''| style="text-align: left;"| '''support'''| style="text-align: left;"| '''support'''~~|-~~| style="text-align: left;"| '''Ubuntu 22.04 - Jammy'''| style="text-align: left;"| '''Linux5.10'''| style="text-align: left;"| '''support'''| style="text-align: left;"| '''support~~'''</big>

|}

<~~span id~~ol start="~~linux~~4" style="list-~~system~~style-~~adaptation~~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'''</~~span~~li>~~== Linux System adaptation ==~~

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

|-

| ~~style="text-align: left;"| '''Function'''| style="text-align~~orangepi@orangepi: ~~left;"|~~ ~$ '''~~Debian11'''| style="text-align: left;"| '''Ubuntu20~~ping www.baidu.~~04'''| style="text~~com -~~align: left;"| '''Ubuntu22.04~~I eth0'''|-~~| style="text-align~~PING www.a.shifen.com (14.215.177.38) from 192.168.1.12 eth0: ~~left;"| '''USB2~~56(84) bytes of data.~~0x3'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''USB3~~64 bytes from 14.215.177.38 (14.215.177.~~0x1'''| style="text-align~~38): ~~left;"| '''OK'''| style~~icmp_seq=~~"text-align: left;"| '''OK'''| style~~1 ttl=~~"text-align: left;"| '''OK'''~~|-~~| style~~56 time=~~"text-align: left;"| '''M~~6.~~2 NVMe SSD Start'''~~74 ms~~| style="text-align: left;"| '''OK'''| style="text-align~~64 bytes from 14.215.177.38 (14.215.177.38): ~~left;"| '''OK'''| style~~icmp_seq=~~"text-align: left;"| '''OK'''~~|-~~| style~~2 ttl=~~"text-align: left;"| '''WIFI'''| style~~56 time=~~"text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Bluetooth'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''GPIO（40pin）'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''UART（40pin）'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''SPI（40pin）'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''I2C（40pin）'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''PWM（40pin）'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''PWM fan interface'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''3pin Debug serial port'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''EMMC'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''TF card start'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI Video'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI Audio'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Camera'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''LCD'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Edp Display'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Gigabit Ethernet port'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Network port status light'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''headphone playback'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''headphone recording'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''LED Light'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''RTC'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''GPU'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''NPU'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''VPU'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''watchdog test'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Chromium Hard solution video'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|}6.80 ms

~~== The format of Linux commands in this manual~~ 3 ttl=56 time=6.26 ms

~~# In this manual, all commands that need to be entered in the Linux system will be marked with the following box~~64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq=4 ttl=56 time=7.27 ms

~~As shown below, the content in the yellow box indicates the content that needs special attention, except for the commands in it.~~^C

~~<ol start="2" style="list~~-~~style~~-~~type: decimal;"><li>Description of the prompt type in front of the command<ol style="list~~-~~style~~www.a.shifen.com ping statistics --~~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>~~

~~'''orangepi@orangepi:~$ sudo apt update'''~~4 packets transmitted, 4 received, 0% packet loss, time 3002ms

~~'''root@orangepi:~#''' '''vim~~ rtt min/~~boot~~avg/~~boot~~max/mdev = 6.~~cmd'''~~260/6.770/7.275/0.373 ms|}</ol>

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

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~root@test:~# ls~~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>|}

<~~ol start~~span id="~~2" style="list~~wifi-the-server-image-connects-to-~~style~~wifi-~~type: lower~~through-~~alpha;~~commands"><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'''</lispan>~~<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 server image connects to WIFI through 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>====

~~<!--~~ {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''When the development board is not connected to Ethernet, not connected to HDMI display, but only connected to the serial port, it is recommended to use the commands demonstrated in this section to connect to the WIFI network. Because nmtui can only display characters in some serial port software (such as minicom), and cannot display the graphical interface normally. Of course, if the development board is connected to an Ethernet or HDMI display, you can also use the commands demonstrated in this section to connect to the WIFI network.'''</big>|} <ol ~~start="3"~~ style="list-style-type: decimal;"><li>~~What~~ First log in to the Linux system, there are the ~~commands that need to be entered?~~following three ways

<li>~~As shown below~~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 ~~black bold part'''~~ development board is connected to the ~~command that needs to be input~~debugging serial port, ~~and~~ you can use the ~~content below~~ serial port terminal to log in to the ~~command~~ Linux system</li><li>If the development board is connected to the ~~output content (some commands have output~~HDMI display, ~~some may not), and this part of~~ you can log in to the Linux system through the terminal displayed on the ~~content does not need to be input~~HDMI</li></ol></li><li>First use the nmcli dev wifi command to scan the surrounding WIFI hotspots</olp></li>

~~root~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~# $ '''~~cat /boot/orangepiEnv.txt~~nmcli dev wifi'''|}

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

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

~~'''console~~</div></ol><ol start=~~serial'''~~"3" style="list-style-type: decimal;"><li>Then use the nmcli command to connect to the scanned WIFI hotspot, where:</li>

~~<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~~a. ~~As long as the black and bold parts are all commands that need to be input. When these commands are entered into one line, the last "\" of each line~~ '''wifi_name''' needs to be ~~removed, this is not part of~~ replaced with the ~~command. In addition, there are spaces in different parts~~ name of the ~~command, please don’t miss it</li></ol>~~WIFI hotspot you want to connect to

~~orangepi@orangepi~~:~$ b. '''~~echo \~~wifi_passwd'''needs to be replaced with the password of the WIFI hotspot you want to connect to

:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~"deb [arch~~nmcli dev wifi connect wifi_name password wifi_passwd'''

Device 'wlan0'successfully activated with '~~signed~~cf937f88-byca1e-4411-bb50-61f402eef293'.|}</ol><ol start="4" style=~~/usr/share/keyrings/docker~~"list-~~archive~~style-~~keyring.gpg] \~~type: decimal;"><li>You can view the IP address of wifi through the '''ip addr show wlan0'''command

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~https://download.docker.com/Linux/debian \~~ip addr show wlan0'''

~~'''$(lsb_release -cs) stable~~11: wlan0: &~~quot~~lt; ~~| sudo tee /etc/apt/sources.list.d/docker.list~~ BROADCAST,MULTICAST,UP,LOWER_UP> ~~/dev/null'''~~mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~<~~:link/~~span>== Linux system login instructions ==~~ether 23:8c:d6:ae:76:bb brd ff:ff:ff:ff:ff:ff

:inet '''192.168.1.11~~=== Linux system default login account and password ===~~'''/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0

~~{| class="wikitable"~~|-~~| style="text-align~~: ~~left;"| '''Account'''| style="text-align~~: ~~left;"| '''Passport'''~~|-~~| style="text-align: left;"| '''root'''| style="text-align: left;"| '''orangepi'''~~|-~~| style="text-align: left;"| '''orangepi'''| style="text-align: left;"| '''orangepi'''~~|}valid_lft 259192sec preferred_lft 259192sec

'''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.''':inet6 240e:3b7:3240:c3a0:c401:a445:5002:ccdd/64 scope global dynamic noprefixroute

'''When the wrong password is prompted, or there is a problem with the ssh connection, please note that as long as you are using the Linux image provided by Orange Pi, please do not suspect that the above password is wrong, but look for other reasons.'''::valid_lft 259192sec preferred_lft 172792sec

~~<~~:inet6 fe80::42f1:6019:a80e:4c31/~~span>=== How to set automatic terminal login in Linux system ===~~64 scope link noprefixroute

~~# The Linux system automatically logs in~~ ::valid_lft forever preferred_lft forever|}</ol><ol start="5" style="list-style-type: decimal;"><li>Use the '''ping''' command to test the ~~terminal by default~~connectivity of the wifi network, and the ~~default login user name is orangepi~~ '''~~orangepi~~ping''' command can be interrupted through the shortcut key '''Ctrl+C'''</li>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img171~~| orangepi@orangepi:~$ '''ping www.~~png|351x198px]]~~orangepi.org -I wlan0'''

~~<ol start="2" style="list-style-type~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0: ~~decimal;"><li>Use the following command to set the root user to automatically log in to the terminal</li></ol>~~56(84) bytes of data.

~~orangepi@orangepi~~64 bytes from 182.92.236.130 (182.92.236.130):~~~$ '''sudo auto_login_cli~~icmp_seq=1 ttl=52 time=43.~~sh root'''~~5 ms

~~<ol start~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq="2 ttl=52 time=41.3~~" style="list-style-type: decimal;"><li>Use the following command to disable automatic login terminal</li></ol>~~ms

~~orangepi@orangepi~~64 bytes from 182.92.236.130 (182.92.236.130):~~~$ '''sudo auto_login_cli~~icmp_seq=3 ttl=52 time=44.~~sh -d'''~~9 ms

~~<ol start~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq="4~~" style~~ttl=~~"list-style-type: decimal;"><li>Use the following command to set the orangepi user to automatically log in to the terminal again</li></ol>~~52 time=45.6 ms

~~orangepi@orangepi~~64 bytes from 182.92.236.130 (182.92.236.130):~~~$ '''sudo auto_login_cli~~icmp_seq=5 ttl=52 time=48.~~sh orangepi'''~~8 ms

~~=== Instructions for automatic login of Linux desktop version system ===~~^C

~~# After the desktop system starts, it will automatically log in to the desktop without entering a password~~--- www.orangepi.org ping statistics ---

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

~~[[File:pi3b-img172~~rtt min/avg/max/mdev = 41.321/44.864/48.834/2.~~png~~484 ms|~~576x324px|1]]~~}</ol>

~~</div><ol start~~=~~"2" style~~=~~"list-style-type: decimal;"><li>Run the following command~~ == The server image connects to ~~prohibit the desktop system from automatically logging into the desktop</li></ol>~~WIFI in a graphical way ====

~~orangepi@orangepi~~<ol style="list-style-type:~$ decimal;"><li>First log in to the Linux system, there are the following three ways</li><ol style="list-style-type: lower-alpha;"><li>If the development board is connected with a network cable, you can remotely log in to [[Orange Pi 3B#SSH remote login development board|'''~~sudo disable_desktop_autologin.sh~~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>

<li>Then enter the nmtui command in the command line to open the wifi connection interface</li>

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

|-

|

orangepi@orangepi:~$ '''nmtui'''

|}

</ol>

<li>Enter the nmtui command to open the interface as shown below<p/li>~~Then restart the system and a login dialog box will appear, at which point a~~ [[~~\l|password~~File:pi3b-img177.png]] ~~is required to enter the system~~</pol><~~div class~~ol start="4" style="~~figure~~list-style-type: decimal;"><li>Select '''Activate a connect''' and press Enter</li>

[[File:pi3b-~~img173~~img178.png~~|569x320px|IMG_256~~]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then you can see all the searched WIFI hotspots</li>

</div~~></li></ol~~class="figure">

~~=== The setting method of root user automatic login in Linux desktop version system ===~~img179.png]]

~~# Execute~~ </div></ol><ol start="6" style="list-style-type: decimal;"><li>Select the ~~following command~~ WIFI hotspot you want to ~~set~~ connect to, then use the ~~desktop system~~ Tab key to ~~automatically log in as~~ position the ~~root user~~cursor on '''Activate''' and press Enter</li>

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

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

~~[[File~~</div></ol><ol start="7" style="list-style-type:~~pi3b-img174.png|448x187px]]~~decimal;"><li>Then a dialog box for entering a password will pop up, enter the corresponding password in '''Password''' and press Enter to start connecting to WIFI</li>

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

~~'''Also note that this is not a bug, since pulseaudio is not allowed to run as root~~[[File:pi3b-img181.~~'''~~png]]

</div></ol><ol start="38" style="list-style-type: decimal;"><li>~~Execute~~ After the ~~following command to set the desktop system to log~~ WIFI connection is successful, a "*" will be displayed in ~~automatically with~~ front of the ~~orangepi user again~~connected WIFI name</li~~></ol~~>

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

~~=== The method of disabling the desktop in the Linux desktop version system ===~~img182.png]]

~~# First enter~~ </div></ol><ol start="9" style="list-style-type: decimal;"><li>You can view the ~~following command on~~ IP address of wifi through the '''ip addr show wlan0''' command ~~line，~~</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~Please remember to add sudo permission~~ip addr show wlan0'''

~~orangepi@orangepi~~11:~~~$ '''sudo systemctl disable lightdm.service'''~~wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~<ol start="2" style="list-style-type~~: ~~decimal;"><li>Then restart the Linux system and you will find that the desktop will not be displayed<~~link/~~li></ol>~~ether 24:8c:d3:aa:76:bb brd ff:ff:ff:ff:ff:ff

~~orangepi@orangepi~~:~$ inet '''~~sudo reboot~~192.168.1.11'''/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0

~~<ol start="3" style="list-style-type~~: ~~decimal;"><li>The steps to reopen the desktop are as follows~~:~~<ol style="list-style-type: lower-alpha;"><li>First enter the following command on the command line，'''Please remember to add sudo permission'''</li></ol></li></ol>~~valid_lft 259069sec preferred_lft 259069sec

~~orangepi@orangepi~~:~~~$ '''sudo systemctl start lightdm.service'''~~inet6 240e:3b7:3240:c4a0:c401:a445:5002:ccdd/64 scope global dynamic noprefixroute

~~<ol start="2" style="list-style-type~~: ~~lower-alpha;"><li>After the command is executed, the desktop will be displayed</li></ol>~~:valid_lft 259071sec preferred_lft 172671sec

~~<~~:inet6 fe80::42f1:6019:a80e:4c31/~~span>== Onboard LED Light Test Instructions ==~~64 scope link noprefixroute

~~# There are three LED lights on~~ ::valid_lft forever preferred_lft forever|}</ol><ol start="10" style="list-style-type: decimal;"><li>Use the '''ping''' command to test the ~~development board, one green light, one red light~~connectivity of the wifi network, and ~~one PCIe light. The location is shown in~~ the ~~figure below~~'''ping''' command can be interrupted through the shortcut key '''Ctrl+C'''</li>{| class="wikitable" style="width:800px;" |-| 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: 56(84) bytes of data.

~~[[File:pi3b-img175~~64 bytes from 182.~~png|425x115px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\3~~92.5236.~~Onboard-LED-Light-Test-Instructions~~130 (1)182.~~jpg3~~92.5236.~~Onboard-LED-Light-Test-Instructions(~~130): icmp_seq=1~~)]]~~ttl=52 time=43.5 ms

~~</div><ol start~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq="2~~" style~~ttl=~~"list-style-type: decimal;"><li>'''As long as the development board is powered on, the red LED light will always be on, which is controlled by the hardware and cannot be turned off by the software'''</li><li>The green LED light will keep blinking after the kernel is started, which is controlled by software.</li><li>The PCIe indicator will flash when there is data transmission on the PCIe interface~~52 time=41.~~</li><li>The method of setting the green light on and off and flashing is as follows</li></ol>~~3 ms

~~'''Note that the following operations should be performed under the root user~~64 bytes from 182.~~'''~~92.236.130 (182.92.236.130): icmp_seq=3 ttl=52 time=44.9 ms

~~<ol style~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=4 ttl=52 time=~~"list-style-type: lower-alpha;"><li>First enter the setting directory of the green light</li></ol>~~45.6 ms

~~root@orangepi~~64 bytes from 182.92.236.130 (182.92.236.130):~~~# '''cd /sys/class/leds/status'''~~icmp_seq=5 ttl=52 time=48.8 ms

~~<ol start="2" style="list-style-type: lower-alpha;"><li>The command to set the green light to stop flashing is as follows</li></ol>~~^C

~~root@~~--- www.orangepi~~:/sys/class/leds/work# '''echo none > trigger'''~~.org ping statistics ---

~~<ol start="3" style="list-style-type: lower-alpha;"><li>The command to set the green light to be on is as follows</li></ol>~~5 packets transmitted, 5 received, 0% packet loss, time 4006ms

~~root@orangepi:~~rtt min/~~sys~~avg/~~class~~max/~~leds~~mdev = 41.321/~~work# '''echo default~~44.864/48.834/2.484 ms|}</ol> trigger'''method-of-desktop-image">

~~<ol start~~=~~"4" style~~=~~"list-style-type: lower-alpha;"><li>The command to set the green light to flash is as follows</li></ol>~~== Test method of desktop image ====

~~root@orangepi:/sys/class/leds/work~~# ~~'''echo heartbeat > trigger'''~~Click the network configuration icon in the upper right corner of the desktop (please do not connect the network cable when testing WIFI)

~~== Network connection test ==~~img183.png]]

<~~span id~~ol start="~~ethernet~~2" style="list-~~port~~style-~~test~~type: decimal;"><li>Click '''More networks''' in the pop-up drop-down box to see all scanned WIFI hotspots, and then select the WIFI hotspot you want to connect to.</~~span~~li>~~=== Ethernet port test ===~~

~~# First, insert one end of~~ [[File:pi3b-img184.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then enter the ~~network cable into the Ethernet interface~~ password of the ~~development board, and connect the other end of the network cable to the router~~WIFI hotspot, and ~~ensure that the network is unblocked# After the system starts, it will automatically assign an IP address to the Ethernet card through DHCP,~~ then click '''~~No other configuration is required~~Connect'''~~# The command~~ to ~~view the IP address in the Linux system of the development board is as follows~~start connecting to WIFI</li>

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

2[[File: ~~eth0~~pi3b-img186.png]]</ol><ol start="5" style="list-style-type: ~~&lt~~decimal;~~BROADCAST~~"><li>If you can open other web pages after opening the browser,~~MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000~~it means that the WIFI connection is normal</li>

~~link~~[[File:pi3b-img187-1.png]]</~~ether 4a:fe:2b:3d:17:1c brd ff:ff:ff:ff:ff:ff~~ol>

~~inet '''192.168.1.150'''/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0~~=== How to set a static IP address ===

~~valid_lft 43150sec preferred_lft 43150sec~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Please do not set a static IP address by modifying the /etc/network/interfaces configuration file.'''</big>|}

~~inet6 fe80::9a04:3703:faed:23be~~</~~64 scope link noprefixroute~~span>==== Use the nmtui command to set a static IP address ====

~~valid_lft forever preferred_lft forever~~# First run the '''nmtui''' command

::{| 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~~nmtui'''|}

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~$ decimal;"><li>Then select '''~~ifconfig~~Edit a connection'''and press Enter</li>

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

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

* [[File:pi3b-img190.png]]</~~usr~~ol><ol start="5" style="list-style-type: decimal;"><li>Then use the Tab key to move the cursor to the '''<Automatic>''' position shown in the figure below to configure IPv4</~~sbin/ifconfig~~li>

~~The command could not be located because '~~[[File:pi3b-img191.png]]</~~sbin~~ol><ol start="6" style="list-style-type:~~/usr/sbin~~decimal;"><li>Then press Enter, select '''Manual''' ~~is not included in~~ with the ~~PATH environment variable.~~up and down arrow keys, and press Enter to confirm</li>

~~This~~ [[File:pi3b-img192.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>The display after selection is ~~most likely caused by~~ shown in the ~~lack of administrative privileges associated with your user account.~~figure below</li>

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

~~'''There are three ways to check~~ [[File:pi3b-img194.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then press Enter, the ~~IP address~~ following setting interface will pop up after ~~the development board starts:'''~~entering</li>

~~# '''Connect~~ [[File:pi3b-img195.png]]</ol><ol start="10" style="list-style-type: decimal;"><li>Then you can set the ~~HDMI display~~IP address (Addresses), ~~then log in to the system~~ gateway (Gateway) and ~~use the ip addr show eth0 command to view the IP~~ DNS server address~~'''# '''Enter~~ in the ~~ip addr show eth0 command~~ position shown in the ~~debugging serial terminal to view the IP address~~figure below (there are many other setting options in it, please explore by yourself), '''Please set it according to your specific needs, ~~you can also check~~ the ~~IP address of the development board’s network port through the router’s management interface. However,~~ value set 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:~~figure below is just an example'''</li>

[[File:pi3b-img196.png]]<~~!-- --~~/ol><ol start="11" style="list-style-type: ~~upper-alpha~~decimal;"><li>~~'''First check whether the Linux system has started normally. If the green light of the development board is blinking~~After setting, ~~it is generally started normally. If only~~ move the ~~red light is on, it means that the system has not started normally;~~cursor to'''~~</li><li>'''Check whether the network cable is plugged in tightly, or try another network cable~~<OK>'''~~</li>~~<li>'''Try another router (I have encountered many problems with the router, such as the router cannot assign the IP address normally, or the IP address has been assigned normally but cannot be seen in the ~~router);'''</li><li>'''If there is no router to replace~~lower right corner, ~~you can only connect to an HDMI display or use the debugging serial port~~ and press Enter to ~~view the IP address'''~~confirm</li~~></ol~~>

[[File:pi3b-img197.png]]</ol><ol start="12" style="list-style-type: decimal;"><li>Then click'''~~In addition, it should be noted that the development board DHCP automatically assigns an IP address without any settings.~~<Back>'''to return to the previous selection interface</li>

[[File:pi3b-img198.png]]</ol><ol start="413" style="list-style-type: decimal;"><li>~~The command to test the network connectivity is as follows, the~~ Then select '''~~ping~~Activate a connection''' ~~command can be interrupted through~~ , then move the ~~shortcut key of~~ cursor to'''~~Ctrl+C~~<OK>''', and finally click Enter</li~~></ol~~>

~~orangepi@orangepi~~[[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 ''~~ping www.baidu.com -I eth0~~'Wired connection 1'''</li>

~~PING www.a.shifen.com (14.215.177.38) from 192.168~~[[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~~.12 eth0: 56(84) bytes of data.~~''', so that the static IP address set earlier will take effect</li>

~~64 bytes from 14.215.177.38 (14.215.177~~[[File:pi3b-img201.~~38): icmp_seq~~png]]</ol><ol start=~~1 ttl~~"16" style=~~56 time=6.74 ms~~"list-style-type: decimal;"><li>Then you can exit nmtui through the'''<Back>''' and '''Quit''' buttons</li>

~~64 bytes from 14~~[[File:pi3b-img202.~~215.177.38 (14.215.177~~png]] [[File:pi3b-img203.~~38): icmp_seq~~png]]</ol><ol start=~~2 ttl~~"17" style=~~56 time=6.80 ms~~"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>

~~64 bytes from 14.215.177.38 (14.215.177.38): icmp_seq~~{| class=~~3 ttl~~"wikitable" style=~~56 time=6.26 ms~~"width:800px;" |-| orangepi@orangepi:~$ '''ip addr show eth0'''

~~64 bytes from 14.215.177.38 (14.215.177.38)~~3: ~~icmp_seq=4 ttl=56 time=7.27 ms~~eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

^C:link/ether 5e:ac:14:a5:92:b3 brd ff:ff:ff:ff:ff:ff

~~--- www~~:inet '''192.a168.~~shifen~~1.~~com ping statistics ---~~177'''/24 brd 192.168.1.255 scope global noprefixroute eth0

~~4 packets transmitted, 4 received, 0% packet loss, time 3002ms~~::valid_lft forever preferred_lft forever

~~rtt min~~:inet6 241e:3b8:3240:c3a0:e269:8305:dc08:135e/~~avg/max/mdev = 6.260/6.770/7.275/0.373 ms~~64 scope global dynamic noprefixroute

~~=== WIFI connection test ===~~::valid_lft 259149sec preferred_lft 172749sec

~~'''Please do not connect to WIFI by modifying the~~ :inet6 fe80::957d:bbbe:4928:3604/~~etc/network/interfaces configuration file. There will be problems connecting to the WIFI network in this way.'''~~64 scope link noprefixroute

::valid_lft forever preferred_lft forever|}</ol><~~span id~~ol start="~~wifi~~18" style="list-~~the~~style-~~server-image-connects-to-wifi-through-commands~~type: decimal;"><~~/span~~li>~~==== WIFI The server image connects~~ Then you can test the connectivity of the network to ~~WIFI~~ check whether the IP address is configured OK, and the '''ping''' command can be interrupted through ~~commands ====~~the shortcut key '''Ctrl+C'''</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''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 networkping 192. ~~Because nmtui can only display characters in some serial port software (such as minicom), and cannot display the graphical interface normally~~168. ~~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~~1.47 -I eth0'''

~~<ol style="list-style-type~~PING 192.168.1.47 (192.168.1.47) from 192.168.1.188 eth0: ~~decimal;"><li>First log in to the Linux system, there are the following three ways<ol style="list-style-type: lower-alpha;"><li>If the development board is connected with a network cable, you can remotely log in to the Linux system through ssh</li><li>If the development board is connected to the debugging serial port, you can use the serial port terminal to log in to the Linux system</li><li>If the development board is connected to the HDMI display, you can log in to the Linux system through the terminal displayed on the HDMI</li></ol></li><li>First use the nmcli dev wifi command to scan the surrounding WIFI hotspots</li></ol>~~56(84) bytes of data.

~~orangepi@orangepi~~64 bytes from 192.168.1.47:~~~$ '''nmcli dev wifi'''~~icmp_seq=1 ttl=64 time=0.233 ms

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

~~[[File~~64 bytes from 192.168.1.47:~~pi3b-img176~~icmp_seq=3 ttl=64 time=0.~~png|575x250px|选区_011]]~~273 ms

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

a64 bytes from 192. ~~'''wifi_name''' needs to be replaced with the name of the WIFI hotspot you want to connect to~~168.1.47: icmp_seq=5 ttl=64 time=0.275 ms

~~b. '''wifi_passwd''' needs to be replaced with the password of the WIFI hotspot you want to connect to~~^C

~~orangepi@orangepi:~$ '''nmcli dev wifi connect wifi_name password wifi_passwd'''~~--- 192.168.1.47 ping statistics ---

~~Device 'wlan0' successfully activated with 'cf937f88-ca1e-4411-bb50-61f402eef293'.~~5 packets transmitted, 5 received, 0% packet loss, time 4042ms

rtt min/avg/max/mdev = 0.233/0.262/0.275/0.015 ms|}</ol ~~start~~>~~<li>You can view the IP address of wifi through the '''ip addr show wlan0''' command~~</~~li></ol~~span>

~~orangepi@orangepi:~$ '''ip addr show wlan0'''~~==== Use the nmcli command to set a static IP address ====

11<ol style="list-style-type: ~~wlan0: &lt~~decimal;~~BROADCAST~~"><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,~~MULTICAST~~please connect the WIFI first,UPand 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,~~LOWER_UP&gt~~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 '''Wired connection 1'''9db058b7-7701-37b8-9411-efc2ae8bfa30ethernet eth0 |}</ol></li></ol>

~~link~~<ol start="3" style="list-style-type: decimal;"><li>Then enter the following command, where</~~ether 23:8c:d6:ae:76:bb brd ff:ff:ff:ff:ff:ff~~li>

~~inet~~ :a. '''~~192.168.~~"Wired connection 1"''' means to set the static IP address of the Ethernet port.11If you need to set the static IP address of the WIFI, please change it to the corresponding name of the WIFI network interface (you can get it through the '''~~/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0~~nmcli con show''' command)

~~valid_lft 259192sec preferred_lft 259192sec~~:b. After '''ipv4.addresse''' is the static IP address to be set, which can be modified to the value you want to set

~~inet6 240e~~:~~3b7:3240:c3a0:c401:a445:5002:ccdd/64 scope global dynamic noprefixroute~~c. '''ipv4.gateway''' indicates the address of the gateway

~~valid_lft 259192sec preferred_lft 172792sec~~::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''nmcli con mod "Wired connection 1" \'''

~~inet6 fe80::42f1:6019:a80e:4c31/64 scope link noprefixroute~~'''ipv4.addresses "192.168.1.110" \'''

~~valid_lft forever preferred_lft forever~~'''ipv4.gateway "192.168.1.1" \'''

~~5) Use the~~ '''~~ping''' command to test the connectivity of the wifi network, and the '''ping''' command can be interrupted through the shortcut key '''Ctrl+C~~ipv4.dns "8.8.8.8" \'''

'''ipv4.method "manual"'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then restart the Linux system</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~ping www.~~sudo reboot'''|}</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>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi~~.org -I wlan0~~:~$ '''ip addr show eth0'''

~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0~~3: ~~56(84) bytes of data.~~eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~64 bytes from 182.92.236.130 (182.92.236.130)~~: ~~icmp_seq=1 ttl=52 time=43.5 ms~~link/ether 5e:ae:14:a5:91:b3 brd ff:ff:ff:ff:ff:ff

~~64 bytes from 182.92~~:inet '''192.~~236~~168.~~130 (182~~1.92110'''/32 brd 192.~~236~~168.~~130): icmp_seq=2 ttl=52 time=41~~1.~~3 ms~~110 scope global noprefixroute eth0

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

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

~~64 bytes from 182.92.236.130 (182.92.236.130)~~: ~~icmp_seq=5 ttl=52 time=48.8 ms~~:valid_lft 259183sec preferred_lft 172783sec

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

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

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

~~rtt min/avg/max/mdev~~ {| class="wikitable" style= ~~41.321/44~~"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.~~864/48~~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.~~834~~'''</~~2.484 ms~~big>|}

===~~= The server image connects to WIFI in a graphical way =~~SSH remote login development board under Ubuntu ===

~~1) First~~ # Obtain the IP address of the development board# Then you can remotely log in to the Linux system~~, there are~~ through the ~~following three ways~~ssh command

~~<ol~~ ::{| class="wikitable" 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 [[\l~~|~~the Linux system through~~ -| test@test:~$ '''ssh[mailto:root@192.168.1.36 root@192.168.1.]~~]</li><li>If the development board is connected~~ xxx'''        (Need to be replaced with 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~~ IP address of the development board ~~is connected to the HDMI display, you can log in to the Linux system through the HDMI display terminal</li></ol>~~)

<!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 ~~nmtui command in~~ entered password will not be displayed on the ~~command line~~ 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 ~~open~~ refuse the ~~wifi~~ connection ~~interface~~, 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>|}

~~orangepi@orangepi~~<ol start="3" style="list-style-type:~~~$ '''nmtui'''~~decimal;"><li>After successfully logging in to the system, the display is as shown in the figure below</li>

<~~ol start~~div class="3figure" ~~style="list-style-type: decimal;"><li>Enter the nmtui command to open the interface as shown below</li></ol~~>

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

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

~~[[File:pi3b-img178.png|349x216px]]~~

~~<ol start="5" style="list-style-type~~root@orangepi: ~~decimal;"><li>Then you can see all the searched WIFI hotspots</li></ol>~~~# '''reset_ssh.sh'''

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

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

~~</div><ol start~~=~~"6" style~~=~~"list-style-type: decimal;"><li>Select the WIFI hotspot you want to connect to, then use the Tab key to position the cursor on '''Activate''' and press Enter</li></ol>~~= SSH remote login development board under Windows ===

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

~~[[File~~:~~pi3b-img180~~:a.~~png|474x298px|17]]~~Open '''Session'''

~~</div><ol start="7" style="list-style-type~~: ~~decimal;"><li>~~:b. Then ~~a dialog box for entering a password will pop up, enter the corresponding password~~ select '''SSH''' in '''~~Password~~Session Setting''' ~~and press Enter to start connecting to WIFI</li></ol>~~

~~<div class="figure">~~::c. Then enter the IP address of the development board in the '''Remote host'''

~~[[File~~:~~pi3b-img181~~:d.~~png|480x308px|18]]~~Then enter the user name '''root''' or '''orangepi''' of the Linux system in '''Specify username'''

~~</div><ol start="8" style="list-style-type~~: ~~decimal;"><li>After the WIFI connection is successful, a "*" will be displayed in front of the connected WIFI name</li></ol>~~:e. Finally click '''OK'''

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

</div>

<ol start="93" style="list-style-type: decimal;"><li>~~You can view~~ 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 ~~IP address~~ specific content of ~~wifi through~~ the entered password will not be displayed on the screen, please do not think that there is any fault, just press Enter after inputting.'''~~ip addr show wlan0''' command~~</~~li></ol~~big>|}

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

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

~~link~~</~~ether 24~~div></ol><ol start="4" style="list-style-type:~~8c:d3:aa:76:bb brd ff:ff:ff:ff:ff:ff~~decimal;"><li>After successfully logging in to the system, the display is as shown in the figure below</li>

~~inet '''192~~[[File:pi3b-img207.~~168.1.11'''~~png]]</ol></~~24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0~~span>

~~valid_lft 259069sec preferred_lft 259069sec~~== The method of uploading files to the Linux system of the development board ==

~~inet6 240e:3b7:3240:c4a0:c401:a445:5002:ccdd~~</~~64 scope global dynamic noprefixroute~~span>=== How to upload files to the development board Linux system in Ubuntu PC ===

~~valid_lft 259071sec preferred_lft 172671sec~~==== How to upload files using the scp command ====

~~inet6 fe80::42f1:6019:a80e:4c31/64 scope link noprefixroute~~# Use the scp command to upload files from the Ubuntu PC to the Linux system of the development board. The specific commands are as follows

~~valid_lft forever preferred_lft forever~~::a. '''file_path''': need to be replaced with the path of the file to be uploaded

~~<ol start="10" style="list-style-type~~: ~~decimal;"><li>Use the~~ :b. '''~~ping~~orangepi''' ~~command to test~~ : It is the user name of the ~~connectivity~~ Linux system of the ~~wifi network~~development board, and ~~the '''ping''' command~~ it can also be ~~interrupted through the shortcut key '''Ctrl+C'''</li></ol>~~replaced with other ones, such as root

~~orangepi@orangepi~~:~$ :c. '''~~ping www~~192.168.~~orangepi~~xx.~~org -I wlan0~~xx''': It is the IP address of the development board, please modify it according to the actual situation

~~PING www~~::d.'''/home/orangepi~~.org (182.92.236.130) from 192.168.1.49 wlan0~~''': ~~56(84) bytes~~ The path in the Linux system of ~~data.~~the development board, which can also be modified to other paths

~~64 bytes from 182~~::{| class="wikitable" style="width:800px;" |-| test@test:~$ '''scp file_path orangepi@192.92168.~~236~~xx.~~130 (182.92.236.130)~~xx: ~~icmp_seq=1 ttl=52 time=43.5 ms~~/home/orangepi/'''|}

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~<ol start="2 ~~ttl~~" style=~~52 time=41.3 ms~~"list-style-type: decimal;"><li>If you want to upload a folder, you need to add the -r parameter</li>

~~64 bytes from 182.92~~{| class="wikitable" style="width:800px;" |-| test@test:~$ '''scp -r dir_path orangepi@192.~~236~~168.~~130 (182~~xx.~~92.236.130)~~xx: ~~icmp_seq~~/home/orangepi/'''|}</ol><ol start="3 ~~ttl~~" style="list-style-type: decimal;"><li>There are more usages of scp, please use the following command to view the man manual</li>{| class=~~52 time~~"wikitable" style=~~44.9 ms~~"width:800px;" |-| test@test:~$ '''man scp'''|}</ol>

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

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=5 ttl=52 time=48.8 ms~~# First install filezilla in Ubuntu PC

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

<ol start="2" style="list-style-~~- www.orangepi.org ping statistics ---~~type: decimal;"><li>Then use the following command to open filezilla</li>

~~5 packets transmitted~~{| class="wikitable" style="width:800px;" |-| test@test:~$ '''filezilla'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>The interface after filezilla is opened is as follows, ~~5 received, 0% packet loss, time 4006ms~~and the display under the remote site on the right is empty</li>

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

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

~~# Click~~ </div></ol><ol start="4" style="list-style-type: decimal;"><li>The method of connecting the ~~network configuration icon~~ development board is shown in the ~~upper right corner of the desktop (please do not connect the network cable when testing WIFI)~~figure below</li>

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

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

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

[[File:pi3b-img210.png]]</ol><ol start="36" style="list-style-type: decimal;"><li>Then ~~enter the password of the WIFI hotspot~~choose to always '''trust this host''', and then click '''~~Connect~~OK''' ~~to start connecting to WIFI~~</li~~></ol~~>

~~[[File:pi3b-img185.png|320x163px]]~~<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~~img211. ~~The entrance of the browser is shown in the figure below</li></ol>~~png]]

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

[[File:pi3b-~~img187~~img212.png~~|576x222px~~]]

<~~span id~~/div></ol><ol start="8" style="~~how-to-set-a-static~~list-ipstyle-~~address~~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.</~~span~~li>~~=== How to set a static IP address ===~~

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

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

~~# First run~~ </div></ol><ol start="9" style="list-style-type: decimal;"><li>After the ~~'''nmtui''' command~~upload is complete, you can go to the corresponding path in the Linux system of the development board to view the uploaded file</li>

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

~~<ol start~~=~~"2" style~~=~~"list-style-type: decimal;"><li>Then select '''Edit a connection''' and press Enter</li></ol>~~= The method of uploading files from Windows PC to the Linux system of the development board ===

~~[[File:pi3b~~==== How to upload files using filezilla ====

~~<ol start="3" style="list-style-type: decimal;"><li>Then select~~ # First download the ~~network interface that needs to set a static IP address, for example, to set~~ installation file of the ~~static IP address~~ Windows version of the ~~'''Ethernet''' interface~~filezilla software, ~~select '''Wired connection 1'''.</li></ol>~~the download link is as follows

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-| '''https://filezilla-~~img189~~project.org/download.~~png~~php?type=client'''|~~310x149px]]~~}

<~~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~~img214.png~~|316x144px~~]]

<~~ol start="5" style="list-style-type: decimal;"~~/div><~~li>Then use the Tab key to move the cursor to the '''<Automatic>''' position shown in the~~ div class="figure ~~below to configure IPv4</li></ol~~">

::[[File:pi3b-~~img191~~img215.png~~|575x240px~~]]

</div><ol start="62" style="list-style-type: decimal;"><li>~~Then press Enter~~The downloaded installation package is as follows, ~~select '''Manual''' with the up~~ and ~~down arrow keys, and press Enter~~ then double-click to ~~confirm~~install directly</li~~></ol~~>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-| '''FileZilla_Server_1.5.1_win64-~~img192~~setup.~~png~~exe'''|~~576x237px]]~~}

~~<ol start="7" style="list-style-type: decimal~~During the installation process, please select '''Decline''' on the following installation interface, and then select '''Next>">~~<li>The display after selection is shown in the figure below</li></ol>~~'''

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

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

~~[[File~~</div></ol><ol start="3" style="list-style-type:~~pi3b-img194.png|576x241px]]~~decimal;"><li>The interface after filezilla is opened is as follows, and the display under the remote site on the right is empty</li>

<~~ol start~~div class="9figure" ~~style="list-style-type: decimal;"><li>Then press Enter, the following setting interface will pop up after entering</li></ol~~>

[[File:pi3b-~~img195~~img217.png~~|575x450px~~]]

</div></ol><ol start="104" style="list-style-type: decimal;"><li>~~Then you can set~~ The method of connecting the ~~IP address (Addresses), gateway (Gateway) and DNS server address in the position~~ development board is 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~~>

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

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

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

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

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

</div></ol><ol start="136" style="list-style-type: decimal;"><li>Then ~~select~~ choose to always '''~~Activate a connection~~trust this host''', and then ~~move the cursor to~~click '''~~<~~OK~~>~~'''~~, and finally click Enter~~</li~~></ol~~>

~~[[File:pi3b-img199.png|331x248px]]~~<div class="figure">

~~<ol start="14" style="list~~[[File:pi3b-~~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 '''Wired connection 1'''</li></ol>img219.png]]

~~[[File~~</div></ol><ol start="7" style="list-style-type:~~pi3b-img200.png|576x224px]]~~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="15figure" ~~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></ol~~>

[[File:pi3b-~~img201~~img220.png~~|576x224px~~]]

</div></ol><ol start="168" style="list-style-type: decimal;"><li>Then ~~you can exit nmtui through~~ select the path to be uploaded to the development board on the~~'''<Back>'''~~ 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 ~~'''Quit''' buttons~~then click the upload option to start uploading the file to the development board.</li~~></ol~~>

~~[[File:pi3b-img202.png|300x253px]] [[File:pi3b-img203.png|227x252px]]~~<div class="figure">

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

~~orangepi@orangepi~~</div></ol><ol start="9" style="list-style-type:~~~$ '''ip addr show eth0'''~~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>

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

~~link/ether 5e:ac:14:a5:92:b3 brd ff:ff:ff:ff:ff:ff~~== HDMI test ==

~~inet '''192.168.1.177'''~~</~~24 brd 192.168.1.255 scope global noprefixroute eth0~~span>=== HDMI display test ===

~~valid_lft forever preferred_lft forever~~# Use HDMI to HDMI cable to connect Orange Pi development board and HDMI monitor

~~inet6 241e~~:~~3b8~~:~~3240~~[[File:~~c3a0:e269:8305:dc08:135e/64 scope global dynamic noprefixroute~~pi3b-img10.png]]

~~valid_lft 259149sec preferred_lft 172749sec~~<ol start="2" style="list-style-type: decimal;"><li>After starting the Linux system, if the HDMI monitor has image output, it means that the HDMI interface is in normal use</li>

~~inet6 fe80~~{| class="wikitable" style="background-color:#ffffdc;width:~~957d:bbbe:4928:3604/64 scope link noprefixroute~~800px;" |-| <big>'''Note that although many notebook computers have an HDMI interface, the HDMI interface of the notebook generally only has the output function, and does not have the function of HDMI in, that is to say, the HDMI output of other devices cannot be displayed on the notebook screen.'''

~~valid_lft forever preferred_lft forever~~'''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.'''</big>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''When the HDMI is not displayed, please check whether the HDMI cable is plugged in tightly. After confirming that there is no problem with the connection, you can change a different screen and try to see if it is displayed.'''</big>|}</ol>

<~~ol start~~span id="~~18" style="list~~hdmi-to-vga-~~style~~display-~~type: decimal;~~test">~~<li>Then you can test the connectivity of the network to check whether the IP address is configured OK, and the '''ping''' command can be interrupted through the shortcut key '''Ctrl+C'''</li~~></olspan>

~~orangepi@orangepi:~$ '''ping 192.168.1.47 -I eth0'''~~=== HDMI to VGA display test ===

~~PING 192.168.1.47 (192.168.1.47) from 192.168.1.188 eth0~~<ol style="list-style-type: ~~56(84) bytes of data.~~decimal;"><li>First, you need to prepare the following accessories<ol style="list-style-type: lower-alpha;"><li>HDMI to VGA converter</li>

~~64 bytes from 192.168.1~~[[File:pi3b-img222.~~47: icmp_seq~~png]]</ol><ol start=~~1 ttl~~"2" style=~~64 time=0.233 ms~~"list-style-type: lower-alpha;"><li>A VGA cable</li>

~~64 bytes from 192~~[[File:pi3b-img223.~~168.1.47~~png]]</ol><ol start="3" style="list-style-type: ~~icmp_seq~~lower-alpha;"><li>A monitor or TV that supports VGA interface</li></ol></li></ol><ol start="2 ~~ttl~~" style=~~64 time=0.263 ms~~"list-style-type: decimal;"><li>HDMI to VGA display test as shown below</li>

~~64 bytes from 192.168.1.47~~[[File: ~~icmp_seq=3 ttl=64 time=0~~pi3b-img224.~~273 ms~~png]]

~~64 bytes from 192~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''When using HDMI to VGA display, the development board and the Linux system of the development board do not need to make any settings, only the HDMI interface of the development board can display normally.~~168~~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.~~1.47: icmp_seq=4 ttl=64 time~~'''</big>|}</ol>

~~64 bytes from 192.168.1.47: icmp_seq~~=~~5 ttl~~=~~64 time~~=~~0.275 ms~~HDMI resolution setting method ===

^C# First open '''Display''' in '''Settings'''

::[[File:pi3b-~~-- 192.168~~img225.~~1.47 ping statistics ---~~png]]

~~5 packets transmitted, 5 received, 0% packet loss, time 4042ms~~<ol start="2" style="list-style-type: decimal;"><li>Then you can see the current resolution of the system</li>

~~rtt min~~[[File:pi3b-img226.png]]</~~avg/max/mdev~~ ol><ol start="3" style= ~~0.233/0.262~~"list-style-type: decimal;"><li>Click the drop-down box of Resolution to see all resolutions currently supported by the monitor</~~0.275/0.015 ms~~li>

[[File:pi3b-img227.png]]<~~span id~~/ol><ol start="4" style="~~use~~list-~~the-nmcli-command-to-set~~style-~~a-static-ip-address~~type: decimal;"><~~/span~~li>~~==== Use~~ Then select the ~~nmcli command~~ resolution you want to set ~~a static IP address ====~~, and click Apply</li>

~~<ol style="list~~[[File:pi3b-~~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~~img228. ~~'''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>~~png]]~~<li>Then use the '''nmcli con show''' command to view the name of the network device, as shown below~~</pol><ol start="5" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~'''orangepi~~After the new resolution is set, select ''' ~~is the name of~~ Keep the ~~WIFI network interface (the names are not necessarily the same)</li><li>~~configuration'''~~Wired connection 1''' is the name of the Ethernet interface</li></ol>~~</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''nmcli con show'''~~pi3b-img229.png]]</ol>

~~NAME UUID TYPE DEVICE~~== How to use Bluetooth ==

~~'''orangepi''' cfc4f922~~=== Test method of desktop image ===

~~'''Wired connection 1''' 9db058b7-7701-37b8-9411-efc2ae8bfa30 ethernet eth0~~# Click the Bluetooth icon in the upper right corner of the desktop.

~~<ol start="3" style="list~~::[[File:pi3b-~~style-type: decimal;"><li>Then enter the following command, where</li></ol>~~img230.png]]

<~~blockquote~~ol start="2" style="list-style-type: decimal;">~~a. '''"Wired connection 1"''' means to set~~ <li>Then select the static IP address of the Ethernet port. If you need to set the static IP address of the WIFI, please change it to the corresponding name of the WIFI network interface (you can get it through the '''nmcli con show''' command)adapter</li>

b[[File:pi3b-img231. ~~After~~ png]]</ol><ol start="3" style="list-style-type: decimal;"><li>If there is a prompt on the following interface, please select '''~~ipv4.addresse~~Yes''' ~~is the static IP address to be set, which can be modified to the value you want to set~~</li>

c[[File:pi3b-img232. png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then set '''~~ipv4.gateway~~Visibility Setting''' ~~indicates the address of the gateway</blockquote>orangepi@orangepi:~$~~ as '''~~nmcli con mod "Wired connection 1" \~~Always visible'''in the Bluetooth adapter settings interface, and then close it</li>

~~'''ipv4~~[[File:pi3b-img233.~~addresses &quot~~png]]</ol><ol start="5" style="list-style-type: decimal;~~192.168.1.110" \'''~~"><li>Then open the configuration interface of the Bluetooth device</li>

[[File:pi3b-img234.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Click '''~~ipv4.gateway "192.168.1.1" \~~Search'''to start scanning the surrounding Bluetooth device</li>

[[File:pi3b-img235.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Then select the Bluetooth device you want to connect to, and then click the right button of the mouse to pop up the operation interface for this Bluetooth device, select '''~~ipv4.dns "8.8.8.8" \~~Pair'''to start pairing, and the demonstration here is to pair with an Android phone</li>

[[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 '''~~ipv4.method "manual"~~Confirm'''to confirm. At this time, the mobile phone also needs to be confirmed</li>

[[File:pi3b-img237.png]]</ol><ol start="49" style="list-style-type: decimal;"><li>~~Then restart~~ 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 ~~Linux system~~phone</li~~></ol~~>

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

[[File:pi3b-img239.png]]</ol ~~start~~>~~<li>Then re-enter the Linux system and use the '''ip addr show eth0'''command to see that the IP address has been set to the desired value~~</~~li></ol~~span>

~~orangepi@orangepi:~$ '''ip addr show eth0'''~~== USB interface test ==

3{| class="wikitable" style="background-color: ~~eth0~~#ffffdc;width: ~~<BROADCAST,MULTICAST,UP,LOWER_UP&gt~~800px; ~~mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~" |-| <big>'''The USB interface can be connected to a USB hub to expand the number of USB interfaces.'''</big>|}

~~link~~</~~ether 5e:ae:14:a5:91:b3 brd ff:ff:ff:ff:ff:ff~~span>=== Connect the USB mouse or keyboard test ===

~~inet '''192.168.1.110'''/32 brd 192.168.1.110 scope global noprefixroute eth0~~# 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)

~~valid_lft forever preferred_lft forever~~

~~inet6 240e:3b7:3240:c3a0:97de:1d01:b290:fe3a/64 scope global dynamic noprefixroute~~=== Connect the USB storage device test ===

~~valid_lft 259183sec preferred_lft 172783sec~~# First insert the U disk or USB mobile hard disk into the USB interface of the Orange Pi development board# Execute the following command, if you can see the output of sdX, it means that the U disk is recognized successfully

~~inet6 fe80~~::~~3312~~{| class="wikitable" style="width:~~861a~~800px;"|-|orangepi@orangepi:~~a589~~~$ '''cat /proc/partitions | grep "sd*"''' major minor #blocksname 8030044160 '''sda''' 8130043119 '''sda1'''</~~64 scope link noprefixroute~~span> |}

~~valid_lft forever preferred_lft forever~~<ol start="3" style="list-style-type: decimal;"><li>Use the mount command to mount the U disk into '''/mnt''', and then you can view the file in the U disk</li>

~~~~style=~~= SSH remote login development board~~"width:800px; ==" |-| orangepi@orangepi:~$ '''sudo mount /dev/sda1 /mnt/'''

orangepi@orangepi:~$ '''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.ls /mnt/'''

test.txt|}</ol><~~span id~~ol start="~~ssh-remote-login~~4" style="list-~~development~~style-~~board-under-ubuntu~~type: decimal;"><li>After the mounting, you can view the capacity usage and mount point of the U disk through the '''df -h''' command</~~span~~li>{| class="wikitable" style=~~= SSH remote login development board under Ubuntu ===~~"width:800px;" |-|orangepi@orangepi:~$ '''df -h | grep "sd"'''

~~# Obtain the IP address of the development board~~/dev/sda1     29G    208K    29G    1% /mnt~~# Then you can remotely log in to the Linux system through the ssh command~~|}</ol>

=== USB wireless network card test~~@test:~$ '''ssh [mailto:root@192.168.1.36 root@192.168.1.]xxx''' (Need to be replaced with the IP address of the development board)~~===

~~root@192.168~~The currently '''tested''' USB wireless network cards are shown below.1Please test it by yourself for other models of USB wireless network cards.~~xx's password: (Enter the password here~~If you cannot use it, you need to transplant the ~~default password is orangepi)~~corresponding USB wireless network card driver

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

~~'''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~~Support 2.~~'''~~4G WIFI+BT4.0

~~<ol start="3" style="list~~| [[File:pi3b-~~style~~img240.png]]|-~~type: decimal;"><li>After successfully logging in to the system, the display is as shown in the figure below</li></ol>~~| 2| RTL8811

~~<div class="figure">~~Support 2.4G +5G WIFI

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

~~</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~~Support 2. ~~If the ping is ok, you can log in to the Linux system through the serial port or HDMI display and then enter the following command on the development board and try again. Is it possible to connect:'''~~4G +5G WIFI

~~root@orangepi:~# '''reset_ssh~~Support BT 4.~~sh'''~~2

~~'''If it still doesn't work, try to reset the system.'''~~| <div class="figure">

~~=== SSH remote login development board under Windows ===~~img242.png]]

~~# First obtain the IP address of the development board~~</div>|}

~~2) Under Windows, you can use MobaXterm to remotely log in to the development board, first create a new ssh session~~==== RTL8723BU test ====

~~a. Open '''Session'''~~# First insert the RTL8723BU wireless network card module into the USB interface of the development board# Then the Linux system will automatically load the RTL8723BU bluetooth and WIFI-related kernel modules, through the lsmod command, you can see that the following kernel modules have been automatically loaded

~~b. Then select~~ ::{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''~~SSH''' in '''Session Setting~~lsmod'''Module Size Used by rfcomm 5734416 rtl8xxxu 1064960 rtk_btusb 614400 |}

~~c. Then enter~~ <ol start="3" style="list-style-type: decimal;"><li>Through the ~~IP address~~ dmesg command, you can see the loading information of the ~~development board in the '''Remote host'''~~RTL8723BU module</li>

~~d. Then enter the user name '''root''' or '''~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ ''' ~~of the Linux system in '''Specify username~~dmesg'''

e. ~~Finally click '''OK'''~~.....

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

[~~[File~~83.588375] usb 2-1:~~pi3b-img205~~New USB device found, idVendor=0bda, idProduct=b720, bcdDevice= 2.~~png|553x280px|14]]~~00

~~</div><ol start~~[ 83.588403] usb 2-1: New USB device strings: Mfr=1, Product="2~~" style~~, SerialNumber=~~"list-style-type: decimal;"><li></li><li>Then you will be prompted to enter a password. The default passwords for root and orangepi users are orangepi</li></ol>~~3

~~'''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.~~'''~~588422] usb 2-1: Product: 802.11n WLAN Adapter

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

[~~[File~~83.588460] usb 2-1:~~pi3b-img206.png|578x150px|C~~SerialNumber:~~\Users\orangepi\Desktop\用户手册插图\pi 3b\just press Enter after inputting..jpgjust press Enter after inputting.]]~~00e04c000001

~~</div><ol start~~[ 83.601974] Bluetooth: hci0: RTL: examining hci_ver=06 hci_rev=~~"4" style~~000b lmp_ver=~~"list-style-type: decimal;"><li>After successfully logging in to the system, the display is as shown in the figure below</li></ol>~~06 lmp_subver=8723

[~~[File:pi3b-img207~~83.~~png|576x334px]~~603894]Bluetooth: hci0: RTL: rom_version status=0 version=1

~~<~~[ 83.603920] Bluetooth: hci0: RTL: loading rtl_bt/~~span>== The method of uploading files to the Linux system of the development board ==~~rtl8723b_fw.bin

~~<~~[ 83.610108] Bluetooth: hci0: RTL: loading rtl_bt/~~span>=== How to upload files to the development board Linux system in Ubuntu PC ===~~rtl8723b_config.bin

~~==== How to upload files using the scp command ====~~[ 83.611274] Bluetooth: hci0: RTL: cfg_sz 68, total sz 22564

~~# Use the scp command to upload files from the Ubuntu PC to the Linux system of the development board~~[ 83. ~~The specific commands are as follows~~658494] rtk_btusb: Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-142432

~~<blockquote>a~~[ 83. ~~'''file_path'''~~658651] usbcore: ~~need to be replaced with the path of the file to be uploaded~~registered new interface driver rtk_btusb

b[ 83. ~~'''orangepi'''~~667124] usb 2-1: It This Realtek USB WiFi dongle (0x0bda:0xb720) is ~~the user name of the Linux system of the development board, and it can also be replaced with other ones, such as root~~untested!

c[ 83. ~~'''192~~667137] usb 2-1: Please report results to Jes.~~168~~Sorensen@gmail.~~xx.xx''': It is the IP address of the development board, please modify it according to the actual situation~~com

d[ 83. ~~'''/home/orangepi'''~~890140] usb 2-1: ~~The path in the Linux system of the development board, which can also be modified to other paths</blockquote>test@test~~Vendor:~~~$ '''scp file_path orangepi@192.168.xx.xx:/home/orangepi/'''~~Realtek

~~<ol start="~~[ 83.890153] usb 2~~" style="list~~-~~style-type~~1: Product: ~~decimal;"><li>If you want to upload a folder, you need to add the -r parameter</li></ol>~~802.11n WLAN Adapter

~~test@test~~[ 83.890159] usb 2-1: rtl8723bu_parse_efuse:~~~$ '''scp -r dir_path orangepi@192.168.xx.xx~~dumping efuse (0x200 bytes):~~/home/orangepi/'''~~

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

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

~~==== How to upload files using filezilla ====~~1: RTL8723BU MAC: 00:13:ef:f4:58:ae

~~# First install filezilla in Ubuntu PC~~[ 83.890421] usb 2-1: rtl8xxxu: Loading firmware rtlwifi/rtl8723bu_nic.bin

~~test@test~~[ 83.895289] usb 2-1:~~~$ '''sudo apt install -y filezilla'''~~Firmware revision 35.0 (signature 0x5301)

~~<ol start="2" style="list-style-type~~[ 84.050893] Bluetooth: ~~decimal;"><li>Then use the following command to open filezilla</li></ol>~~hci0: RTL: fw version 0x0e2f9f73

~~test@test~~[ 84.266905] Bluetooth:~~~$ '''filezilla'''~~RFCOMM TTY layer initialized

~~<ol start="3" style="list-style-type~~[ 84.266949] Bluetooth: ~~decimal;"><li>The interface after filezilla is opened is as follows, and the display under the remote site on the right is empty</li></ol>~~RFCOMM socket layer initialized

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

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

[ 84.912046] rtl8xxxu 2-1:1.2 wlx0013eff458ae: renamed from wlan0|}</~~div~~ol>

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

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

~~[[File~~:~~pi3b-img209.png|575x128px|图片565]]~~:ether 00:13:ef:f4:58:ae txqueuelen 1000 (Ethernet)

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

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

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

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

~~[[File~~orangepi@orangepi:~~pi3b-img211.png|278x150px|IMG_256]]~~~$ '''hciconfig'''

hci0: Type: Primary Bus: '''<~~/div><ol start="7"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<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>~~USB</olspan>'''

~~<div class="figure">~~::BD Address: 00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16

~~[[File~~:~~pi3b-img212.png|533x330px|IMG_256]]~~:DOWN

~~</div><ol start="8" style="list-style-type~~: ~~decimal;">~~<li>Then select the path to be uploaded to the development board on the right side of the filezilla software, and then select the file to be uploaded on the 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>:RX bytes:1252 acl:0 sco:0 events:125 errors:0

::TX bytes:23307 acl:0 sco:0 commands:125 errors:0|}<~~div class~~/ol><ol start="6" style="~~figure~~list-style-type: decimal;"><li>You can also see the Bluetooth icon on the desktop. At this time, Bluetooth has not been opened, so a red '''x''' will be displayed</li>

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

[[File:pi3b-img244.png]]</~~div~~ol>~~9) After the upload~~ <ol start="8" style="list-style-type: decimal;"><li>The display after turning on Bluetooth is ~~complete, you can go to the corresponding path in the Linux system of the development board to view the uploaded file~~as follows</li>

~~10) The~~ [[File:pi3b-img245.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Please refer to the [[Orange Pi 3B#How to use Bluetooth|'''Bluetooth use method''']] for Bluetooth test method ~~of uploading a folder is the same as that of uploading a file~~, so I ~~won’t~~ won't go into details here.</li></ol>

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

~~~~===~~= How to upload files using filezilla~~ RTL8811 test ====

# First ~~download~~ insert the ~~installation file~~ RTL8811 wireless network card module into the USB interface of the ~~Windows version of~~ development board.# Then the Linux system will automatically load the ~~filezilla software~~kernel modules related to RTL8811 WIFI, and you can see that the following kernel modules have been automatically loaded through the ~~download link is as follows~~lsmod command

~~https~~::{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''lsmod'''Module Size Used by</~~filezilla~~span> 8821cu </~~download.php?type~~span>1839104 0 |}

<~~div~~ ol start="3" style="list-style-type: decimal;"><li>Through the dmesg command, you can see the loading information of the RTL8811 module</li>{| class="~~figure~~wikitable" style="width:800px;">|-| orangepi@orangepi:~$ '''dmesg'''

[~~[File:pi3b~~118.618194] usb 2-~~img214.png|472x171px|C~~1:~~\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~new high-~~15.jpg未标题~~speed USB device number 2 using ehci-~~15]]~~platform

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

[~~[File:pi3b-img215~~118.~~png|393x283px|图片5552]~~767181]usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

~~</div><ol start="~~[ 118.767199] usb 2~~" style="list~~-~~style-type~~1: Product: ~~decimal;"><li>The downloaded installation package is as follows, and then double-click to install directly</li></ol>~~802.11ac NIC

~~'''FileZilla_Server_1~~[ 118.~~5.1_win64~~767219] usb 2-~~setup.exe'''~~1: Manufacturer: Realtek

~~During the installation process, please select '''Decline''' on the following installation interface, and then select '''Next>'''~~[ 118.767235] usb 2-1: SerialNumber: 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-~~img216~~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|~~319x251px|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><ol start~~wlx1cbfced9d260: flags=~~"3" style="list-style-type: decimal~~4099<UP,BROADCAST,MULTICAST>">mtu 1500 ~~<li>The interface after filezilla is opened is as follows, and the display under the remote site on the right is empty</li></ol>~~::ether 1c:bf:ce:d9:d2:60 txqueuelen 1000 (Ethernet)

~~<div class="figure">~~::RX packets 0 bytes 0 (0.0 B)

~~[[File~~:~~pi3b-img217.png|451x357px|IMG_256]]~~:RX errors 0 dropped 0 overruns 0 frame 0

~~</div><ol start="4" style="list-style-type~~: ~~decimal;"><li>The method of connecting the development board is shown in the figure below~~:~~</li></ol>~~TX packets 0 bytes 0 (0.0 B)

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

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

~~</div>~~# First insert the rtl8821cu wireless network card module into the USB interface of the development board~~<ol start="5" style="list-style-type: decimal;"><li>~~# Then ~~choose to~~ use the '''~~save the password~~lsusb'''command to see the device information of the rtl8821cu usb wifi module, ~~and then click '''OK'''</li></ol>~~please make sure that the USB module is not in Driver CDROM Mode

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

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

Bus 002 Device 002: ID 0bda:1a2b Realtek Semiconductor Corp. RTL8188GU 802.11n WLAN Adapter ('''<~~/div><ol start="6"~~ span style="~~list-style-type~~color: ~~decimal;~~blue">Driver CDROM Mode<li/span>~~Then choose to always '''trust this host''', and then click '''OK~~'''~~</li></ol>~~)

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

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

~~</div>~~

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

~~<li>After the connection is successful, you can see the directory structure of the development board Linux file system on the right side of the filezilla software</li></ol>~~

~~<div class="figure">~~orangepi@orangepi:~$ '''sudo usb_modeswitch -KW -v 0bda -p 1a2b'''|}

~~[[File~~<ol start="3" style="list-style-type: decimal;"><li>The Linux system will automatically load the rtl8821cu bluetooth and wifi-related kernel modules, through the lsmod command, you can see that the following kernel modules have been automatically loaded</li>{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''lsmod'''Module Size Used by 8821cu 1839104 0 rtk_btusb 614400 |~~446x329px~~}</ol><ol start="4" style="list-style-type: decimal;"><li>Through the dmesg command, you can see the loading information of the rtl8821cu module</li>{| class="wikitable" style="width:800px;" |-|~~图片3]]~~orangepi@orangepi:~$ '''dmesg'''

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

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

[~~[File~~57.231888] usb 2-1:~~pi3b-img221~~New USB device found, idVendor=0bda, idProduct=1a2b, bcdDevice= 2.~~png|501x369px|IMG_256]]~~00

~~</div><ol start~~[ 57.231916] usb 2-1: New USB device strings: Mfr=~~"9" style~~1, Product=~~"list-style-type: decimal;"><li>After the upload is complete~~2, ~~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>~~SerialNumber=0

~~== HDMI test ==~~1: Product: DISK

~~=== HDMI display test ===~~1: Manufacturer: Realtek

~~# Use HDMI to HDMI cable to connect Orange Pi development board and HDMI monitor~~[ 57.242594] usb-storage 2-1:1.0: USB Mass Storage device detected

[~~[File~~57.245674] scsi host0:~~pi3b~~usb-storage 2-~~img10~~1:1.~~png|199x129px]]~~0

~~<ol start="~~[ 58.069172] usb 2~~" style="list~~-~~style-type~~1: ~~decimal;"><li>After starting the Linux system~~USB disconnect, ~~if the HDMI monitor has image output, it means that the HDMI interface is in normal use</li></ol>~~device number 2

'''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[ 58.~~'''~~440025] usb 2-1: new high-speed USB device number 3 using ehci-platform

~~'''When you want to connect the HDMI of the development board to the HDMI port of the laptop~~[ 58.587819] usb 2-1: New USB device found, idVendor=0bda, idProduct=c820, ~~please make sure that your laptop supports the HDMI in function~~bcdDevice= 2.~~'''~~00

~~'''When the HDMI is not displayed~~[ 58.587827] usb 2-1: New USB device strings: Mfr=1, ~~please check whether the HDMI cable is plugged in tightly. After confirming that there is no problem with the connection~~Product=2, ~~you can change a different screen and try to see if it is displayed.'''~~SerialNumber=3

~~=== HDMI to VGA display test ===~~1: Product: 802.11ac NIC

~~<ol style="list~~[ 58.587838] usb 2-~~style-type~~1: ~~decimal;"><li>First, you need to prepare the following accessories<ol style="list-style-type~~Manufacturer: ~~lower-alpha;"><li>HDMI to VGA converter</li></ol></li></ol>~~Realtek

[~~[File:pi3b-img222~~58.~~png|155x104px]~~587844]usb 2-1: SerialNumber: 123456

~~<ol start="2" style="list-style-type~~[ 58.610463] rtk_btusb: ~~lower~~Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-~~alpha;"><li>A VGA cable</li></ol>~~142432

[~~[File:pi3b-img223~~58.~~png|148x133px]~~610656]usbcore: registered new interface driver rtk_btusb

~~<ol start~~[ 58.634631] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=~~"3" style~~000c lmp_ver=~~"list-style-type: lower-alpha;"><li>A monitor or TV that supports VGA interface</li></ol>~~08 lmp_subver=8821

~~<ol start~~[ 58.636729] Bluetooth: hci0: RTL: rom_version status=~~"2" style~~0 version=~~"list-style-type: decimal;"><li>HDMI to VGA display test as shown below</li></ol>~~1

[~~[File~~58.636740] Bluetooth: hci0: RTL:~~pi3b-img224~~loading rtl_bt/rtl8821c_fw.~~png|576x339px]]~~bin

'''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[ 58. ~~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~~664190] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.~~'''~~bin

~~=== HDMI resolution setting method ===~~[ 58.664746] Bluetooth: hci0: RTL: cfg_sz 10, total sz 31990

~~# First open '''Display''' in '''Settings'''~~[ 59.122471] Bluetooth: hci0: RTL: fw version 0x829a7644

[~~[File:pi3b-img225~~59.~~png|576x370px]~~265513]usbcore: registered new interface driver rtl8821cu

~~<ol start="~~[ 59.280119] rtl8821cu 2~~" style="list~~-~~style-type~~1:1.2 wlx90de80521825: ~~decimal;">~~renamed from wlan0|}~~<li>Then you can see the current resolution of the system</li>~~</ol>

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

~~<ol start~~wlx90de80521825: flags=~~"3" style="list-style-type: decimal~~4099<UP,BROADCAST,MULTICAST>">~~<li>Click the drop-down box of Resolution to see all resolutions currently supported by the monitor</li></ol>~~mtu 1500

~~[[File~~:~~pi3b-img227.png|415x274px]]~~:ether 00:13:ef:f4:58:ae txqueuelen 1000 (Ethernet)

~~<ol start="4" style="list-style-type~~: ~~decimal;"><li>Then select the resolution you want to set, and click Apply</li></ol>~~:RX packets 0 bytes 0 (0.0 B)

~~[[File~~:~~pi3b-img228.png|415x277px]]~~:RX errors 0 dropped 0 overruns 0 frame 0

~~<ol start="5" style="list-style-type~~: ~~decimal;"><li>After the new resolution is set, select '''Keep the configuration'''</li></ol>~~:TX packets 0 bytes 0 (0.0 B)

~~[[File~~:~~pi3b~~:TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0|}</ol><ol start="6" style="list-style-type: decimal;"><li>Then you can see the USB Bluetooth device through the '''hciconfig''' command</li>{| class="wikitable" style="width:800px;" |-~~img229.png~~|~~447x243px]]~~orangepi@orangepi:~$ '''sudo apt-get update && sudo apt-get install -y bluez'''

~~== How to use Bluetooth ==~~orangepi@orangepi:~$ '''hciconfig'''

hci0: Type: Primary Bus: '''USB~~=== Test method of desktop image ===~~'''

~~# Click the Bluetooth icon in the upper right corner of the desktop.~~::BD Address: 00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16

~~[[File~~:~~pi3b-img230.png|330x128px]]~~:DOWN

~~<ol start="2" style="list-style-type~~: ~~decimal;"><li>Then select the adapter</li></ol>~~: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-~~img231~~style-type: decimal;"><li>Bluetooth icons can also be seen on the desktop.~~png|375x165px]]~~At this time, Bluetooth has not been turned on, so a red '''x''' will be displayed</li>

[[File:pi3b-img243.png]]</ol><ol start="38" style="list-style-type: decimal;"><li>~~If there is a prompt below, select~~ Click '''~~Yes~~Turn Bluetooth On'''to turn on Bluetooth</li~~></ol~~>

[[File:pi3b-~~img232~~img244.png~~|248x85px~~]]</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="410" style="list-style-type: decimal;"><li>~~Then set~~ Please refer to the [[Orange Pi 3B#How to use Bluetooth|'''~~Visibility Setting''' as '''Always visible~~Bluetooth use chapter''' in ]] for the Bluetooth ~~adapter settings interface, and then close it~~test method. I won't go into details here</li></ol>

~~[[File:pi3b~~

~~<ol start~~=~~"5" style~~=~~"list-style-type: decimal;"><li>Then open the configuration interface of the Bluetooth device</li></ol>~~= USB Camera Test ===

~~[[File:pi3b-img234.png|438x179px]]~~# 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="6" style="list~~::[[File:pi3b-~~style-type: decimal;"><li>Click '''Search''' to start scanning the surrounding Bluetooth device</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;" |-~~img235.png~~|~~322x217px]]~~orangepi@orangepi:~$ '''v4l2-ctl --list-devices'''

Q8 HD Webcam: Q8 HD Webcam ('''<~~ol start="7"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">usb<li/span>~~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~~-fc880000. ~~Here, it is demonstrated with the Android phone</li></ol>~~usb-1):

~~[[File~~:~~pi3b-img236.png|338x263px]]~~'''/dev/video0'''

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

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

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

~~<li>After pairing with the mobile phone, you can choose the paired Bluetooth device, then right -click and select '''Send a File''' to start sending a picture to the phone</li></ol>~~

~~[[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-img238~~decimal;"><li>In the desktop system, Cheese can be used to directly open the USB camera.~~png|439x259px]]~~The method of opening Cheese is shown in the figure below:</li>

~~<ol start="10" style="list~~[[File:pi3b-~~style-type: decimal;"><li>The interface of the sending picture is shown below</li></ol>~~img246.png]]

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

[[File:pi3b-img247.png]]</ol><~~span id~~ol start="~~usb~~4" style="list-~~interface~~style-type: decimal;"><li>How to testthe USB camera using fswebcam<ol style="list-style-type: lower-alpha;"><li>Install fswebcam</~~span~~li>{| class="wikitable" style= ~~USB interface test ==~~"width:800px;" |-| orangepi@orangepi:~$ '''sudo''' '''apt update'''

orangepi@orangepi:~$ '''sudo apt-get install -y fswebcam'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>After installing fswebcam, you can use the following command to take pictures<ol style="list-style-type: none;"><li>a) -d The option is used to specify the device node of the USB ~~interface can connect USB Hub~~ camera</li><li>b) --no-banner Used to remove the watermark of photos</li><li>c) -r The option is used to specify the resolution of the photo</li><li>d) -S The option is used to ~~expand~~ set the number of ~~USB interfaces~~previous frames to skip</li><li>e) ./image.jpg The name and path for setting the generated photos</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo''' '''fswebcam -d /dev/video0 \'''

'''--no-banner -r 1280x720 -S 5 ./image.jpg'''|}</ol></li><~~span id~~/ol><ol start="3" style="~~connect-the-usb-mouse~~list-orstyle-~~keyboard~~type: lower-~~test~~alpha;"><li>In the desktop version of the Linux system, you can directly view the captured pictures through the HDMI display</~~span~~li>{| class="wikitable" style=~~= Connect~~ "width:800px;" |-| orangepi@orangepi:~$ '''scp image.jpg''' [mailto:test@192.168.1.55:/home/test test@192.168.1.55:/home/test] '''（Modify the IP address and path according to the ~~USB mouse or keyboard test~~ actual situation）'''|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>In the desktop version of the Linux system, you can directly view the captured pictures through the HDMI display</li></ol></li></ol>

~~# Insert the keyboard of the USB interface into the USB interface of Orange PI development board# Connect Orange PI development board to HDMI display# If the mouse or keyboard can normal operating systems, the USB interface is used normally (the mouse can only be used in the system of the desktop version)~~== Audio Test ==

=== ~~Connect~~ Test audio methods in the ~~USB storage device test~~ desktop system ===

# First ~~insert~~ open the ~~U disk or USB mobile hard disk into the USB interface of Orange PI development board# Execute the following command. If you can see the output of sdX, the U disk recognition is successful~~file manager

~~orangepi@orangepi~~:~~~$ '''cat /proc/partitions | grep "sd*"'''~~:[[File:pi3b-img248.png]]

~~major minor #blocks name~~<ol start="2" style="list-style-type: 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>

~~8 0 30044160 '''sda'''~~<div class="figure">

~~8 1 30043119 '''sda1'''~~[[File:pi3b-img249.png]]

</div></ol>

<li>~~Use~~ Then select the ~~mount command to mount the U disk into '''/mnt'''~~audio.wav file, right click and ~~then you can view the file in the U disk~~select open with vlc to start playing</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''sudo mount~~ pi3b-img250.png]]</~~dev~~ol><ol start="4" style="list-style-type: decimal;"><li>Methods to switch different audio equipment such as HDMI playback and headset playback</~~sda1 /mnt~~p><ol style="list-style-type: lower-alpha;"><li>First open the volume control interface</~~'''~~li>

~~orangepi@orangepi~~[[File:~$ pi3b-img251.png]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>When playing audio, the audio equipment options that play software can be used will be displayed in '''~~ls /mnt/~~Playback'''. As shown in the figure below, which audio equipment you need to play here can be set.</li>

~~test~~[[File:pi3b-img252.~~txt~~png]]</ol></li></ol>

~~<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></ol>~~= How to play audio with commands ===

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

~~/dev/sda1 29G 208K 29G 1% /mnt~~# First insert the headset into the headphone jack of the development board

~~=== USB wireless network card test ===~~img253.png]]

~~The currently~~ <ol start="2" style="list-style-type: decimal;"><li>Then you can check the sound card device supported by the Linux system through the '''~~tested~~aplay -l''' ~~USB wireless network cards are shown~~ command. From the output below~~. Please test it by yourself for other models of USB wireless network cards. If you cannot use~~ , itcan be seen that '''card 0''' is the sound card device with RK809, ~~you need to transplant~~ which is the ~~corresponding USB wireless network~~ sound card ~~driver~~device of the headset</li>

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

|-

| ~~No.| Model~~||orangepi@orangepi:~$ '''aplay -l'''~~| 1| RTL8723BU~~**** List of PLAYBACK Hardware Devices ****

~~Support 2.4G WIFI+BT4.~~'''card 0: rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]'''

~~| [[File~~:~~pi3b-img240.png]]~~|-~~| 2| RTL8811~~'''Subdevices: 0/1'''

~~Support 2.4G +5G WIFI~~:'''Subdevice #0: subdevice #0'''

| card 1: rockchiphdmi [~~[File~~rockchip,hdmi], device 0:~~pi3b~~fe400000.i2s-i2s-hifi i2s-hifi-~~img241~~0 [fe400000.~~png~~i2s-i2s-hifi i2s-hifi-0]]|-~~| 3| RTL8821CU~~

~~Support 2.4G +5G WIFI~~:Subdevices: 0/1

~~Support BT 4.2~~:Subdevice #0: subdevice #0

:Subdevice #0: subdevice #0| }<~~div class~~/ol><ol start="3" style="~~figure~~list-style-type: decimal;"><li>Then use the '''aplay''' command to play the audio file that comes with the system. If the headset can hear the sound, it means that the hardware can be used normally</li>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img242~~| orangepi@orangepi:~$ '''aplay -D hw:0,0 /usr/share/sounds/alsa/audio.~~png|tb_imag e_share_1670833201 123]]~~wav'''

~~</div>~~Playing WAVE 'audio.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo

|}

</ol>

~~~~===~~= RTL8723BU test~~ HDMI Audio Play Test ====

# First ~~insert~~ use the ~~RTL8723BU wireless network card module into the USB interface of~~ HDMI to HDMI cable to connect the Orange PI development boardto the TV (other HDMI displays need to ensure that the audio can be played)# Then check the ~~Linux system will automatically load~~ sound card serial number of HDMI. From the ~~RTL8723BU Bluetooth and WiFi -related kernel modules. You~~ output below, you can ~~see~~ know that the ~~kernel module below~~ HDMI sound card is ~~automatically loaded through the lsmod command~~'''card 1'''

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

~~Module Size Used by~~**** List of PLAYBACK Hardware Devices ****

~~rfcomm 57344 16~~card 0: rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]

~~rtl8xxxu 106496~~ :Subdevices: 0/1

~~rtk_btusb 61440~~ :Subdevice #0: subdevice #0

~~<ol start="3" style="list~~'''card 1: rockchiphdmi [rockchip,hdmi], device 0: fe400000.i2s-~~style~~i2s-~~type: decimal;"><li>You can see the loading information of the RTL8723BU module through the dmesg command</li></ol>~~hifi i2s-hifi-0 [fe400000.i2s-i2s-hifi i2s-hifi-0]'''

~~orangepi@orangepi~~:~$ '''~~dmesg~~Subdevices: 0/1'''

~~......~~:'''Subdevice #0: subdevice #0'''

~~[ 83.438901] usb 2-1~~: ~~new high-speed USB device number 2 using ehci-platform~~'''Subdevice #0: subdevice #0'''|}

~~[ 83~~<ol start="3" style="list-style-type: decimal;"><li>Then use the '''aplay''' command to play the audio file that comes with the system.~~588375] usb 2~~If the HDMI display or television can hear the sound indicates that the hardware can be used normally</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''aplay -1D hw: ~~New USB device found, idVendor~~1, ~~idProduct~~0 /usr/share/sounds/alsa/audio.wav'''|}</ol>

~~[ 83.588403] usb 2-1: New USB device strings: Mfr~~=~~1, Product~~=~~2, SerialNumber~~=3Use the command to test the recording method ===

~~[ 83~~# Orange Pi 3B development board does not have MICs, and can only record audio through headphones with MIC function.~~588422] usb 2-1: Product: 802.11n WLAN Adapter~~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.588443] usb 2~~::{| class="wikitable" style="width:800px;" |-1| orangepi@orangepi: ~~Manufacturer: Realtek~~~$ '''amixer -c 0 cset name='Capture MIC Path' 'Main Mic''''

~~[ 83.588460] usb 2~~orangepi@orangepi:~$ '''arecord -1D hw: ~~SerialNumber: 00e04c000001~~0,0 -d 5 -f cd -t wav /tmp/test.wav'''|}

~~[ 83.601974] Bluetooth: hci0: RTL: examining hci_ver~~

~~[ 83.603894] Bluetooth: hci0: RTL: rom_version status~~=~~0 version~~=1Temperature Sensor ==

~~[ 83.603920] Bluetooth~~# The command to view the system temperature sensor is: ~~hci0: RTL: loading rtl_bt/rtl8723b_fw.bin~~

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

~~[ 83.611274] Bluetooth: hci0: RTL: cfg_sz 68, total sz 22564~~soc_thermal-virtual-0

~~[ 83.658494] rtk_btusb~~Adapter: ~~Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-142432~~Virtual device

~~[ 83~~temp1: +41.~~658651] usbcore: registered new interface driver rtk_btusb~~9°C (crit = +115.0°C)

~~[ 83.667124] usb 2-1: This Realtek USB WiFi dongle (0x0bda:0xb720) is untested!~~

~~[ 83.667137] usb 2~~gpu_thermal-~~1: Please report results to Jes.Sorensen@gmail.com~~virtual-0

~~[ 83.890140] usb 2-1~~Adapter: ~~Vendor: Realtek~~Virtual device

~~[ 83.890153] usb 2-1: Product~~temp1: ~~802~~+43.~~11n WLAN Adapter~~8°C|}

~~[ 83.890159] 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: ~~rtl8723bu_parse_efuse~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo smartctl -a /dev/nvme0 | grep "Temperature:"'''Temperature: ~~dumping efuse (0x200 bytes)~~'''40 Celsius'''|}~~......~~</li></ol>

~~[ 83.890412] usb 2~~

~~[ 83.890417] usb 2-1: RTL8723BU MAC: 00:13:ef:f4:58:ae~~== 40 Pin interface pin explanation ==

~~[ 83.890421] usb 2-1: rtl8xxxu: Loading firmware rtlwifi/rtl8723bu_nic.bin~~# Orange Pi 3B Development board 40 Pin interface pins, please refer to the figure below

~~[ 83.895289] usb 2-1: Firmware revision 35.0 (signature 0x5301)~~<div class="figure">

::[[ 84File:pi3b-img254.~~050893~~png]] ~~Bluetooth: hci0: RTL: fw version 0x0e2f9f73~~

~~[ 84~~</div><ol start="2" style="list-style-type: decimal;"><li>The function of the Orange Pi 3B development board 40 PIN interface pins is shown in the table below.~~266905] Bluetooth~~<ol style="list-style-type: ~~RFCOMM TTY layer initialized~~lower-alpha;"><li>Below is a complete pins of 40pin</li>

[ 84[File:pi3b-img255-1.~~266949~~png]] ~~Bluetooth~~</ol><ol start="2" style="list-style-type: ~~RFCOMM socket layer initialized~~lower-alpha;"><li>The following form is a picture on the left half of the full table above, which can be seen clearly</li>

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

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

~~[ 84.912046] rtl8xxxu 2~~

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

~~orangepi@orangepi~~{| class="wikitable" style="background-color:~$ #ffffdc;width:800px;" |-| <big>'''Note that wiringOP has been pre -installed in the Linux image released by Orange Pi. Unless wiringOP'~~sudo ifconfig wlx0013eff458ae~~s code is updated, it is not necessary to re -download and install. Just use it directly.'''

~~wlx0013eff458ae: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500~~

~~ether 00~~'''The storage path of the compiled wiringOP's Deb is wrapped in Orangepi-Build:~~13:ef:f4:58:ae txqueuelen 1000 (Ethernet)~~'''

~~RX packets 0 bytes 0 (0~~'''orangepi-build/external/cache/debs/arm64/wiringpi_x.~~0 B)~~xx.deb'''

~~RX errors 0 dropped 0 overruns 0 frame 0~~

~~TX packets 0 bytes 0 (0~~'''After entering the system, you can run the gpio readall command.~~0 B)~~If you can see the output below, it means that wiringOP is pre -installed and can be used normally.'''</big>

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~<div class="figure">

~~<ol start="5" style="list~~[[File:pi3b-~~style~~img258-~~type: decimal;"><li>Then you can see the USB Bluetooth device through the '''hciconfig''' command</li></ol>~~1.png]]

~~orangepi@orangepi:~$~~ </div><big>'''~~sudo apt update && sudo apt install bluez~~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>|}

~~orangepi@orangepi:~$ '''hciconfig'''~~# Download the code of wiringOP

~~hci0~~: ~~Type~~: ~~Primary Bus~~{| class="wikitable" style="width: 800px;" |-| orangepi@orangepi:~$ '''~~USB~~sudo apt update'''

~~BD Address~~orangepi@orangepi: ~~00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16~~~$ '''sudo apt install -y git'''

~~DOWN~~orangepi@orangepi:~$ '''git clone https://github.com/orangepi-xunlong/wiringOP.git -b next'''|}

~~RX bytes~~:~~1252 acl~~:~~0 sco~~{| class="wikitable" style="background-color:~~0 events~~#ffffdc;width:~~125 errors:0~~800px;" |-| <big>'''Note that Orange Pi 3B needs to download the code of the wiringOP next branch, please don't miss the parameter of -b next.'''

~~TX bytes:23307 acl:0 sco:0 commands:125 errors:0~~

~~<ol start="6" style="list-style-type: decimal;"><li>You~~ '''If there is a problem with the download code from GitHub, you can ~~also see~~ use the ~~Bluetooth icon on~~ wiringOP source code that comes with the ~~desktop. At this time~~Linux image directly, ~~Bluetooth has not been opened, so a red~~ and the storage location is: /usr/src/wiringOP'''~~x''' will be displayed~~</~~li></ol~~big>|}

~~[[File~~<ol start="2" style="list-style-type:~~pi3b-img243.png|576x157px]]~~decimal;"><li>Compile and install wiringOP</li>

~~<ol start~~{| class="7wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Click~~ |-| orangepi@orangepi:~$ '''~~Turn Bluetooth On~~cd wiringOP''' ~~to open Bluetooth</li></ol>~~

~~[[File~~orangepi@orangepi:~~pi3b-img244~~~/wiringOP$ '''sudo .~~png|576x262px]]~~/build clean'''

orangepi@orangepi:~/wiringOP$ '''sudo ./build'''|}</ol><ol start="83" style="list-style-type: decimal;"><li>~~The display after opening Bluetooth is shown below~~Test the output of the GPIO Readall command as follows</li~~></ol~~>

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

~~<ol start="9" style="list~~[[File:pi3b-~~style~~img258-~~type: decimal;"><li>Please refer to the [[\l|'''Bluetooth use method'''~~1.png]] ~~for Bluetooth test method, so I won't go into details here.</li></ol>~~

</div></ol>~~==== RTL8811 test ====~~

~~# First insert the RTL8811 wireless network card module into the USB~~ == 40Pin 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~~GPIO, I2C, UART, SPI, and PWM test ==

~~orangepi@orangepi~~{| class="wikitable" style="background-color:~$ #ffffdc;width:800px;" |-| <big>'''~~lsmod~~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.'''</big>

~~Module Size Used by~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''

~~8821cu 1839104 0~~'''overlays=spi3-m0-cs0-spidev i2c2-m1 i2c3-m0 uart7-m2 uart9-m2 pwm11-m1'''|}

<~~ol start~~span id="~~3" style="list~~pin-gpio-~~style~~port-~~type: decimal;~~test">~~<li>You can see the loading information of the RTL8811 module through the dmesg command~~</~~li></ol~~span>=== 40pin GPIO port test ===

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

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

~~[ 118.767152] usb 2-1: New USB device found~~'''After running the blink_all_gpio program, ~~idVendor=0bda~~when using a multimeter to measure the level of the GPIO port, ~~idProduct=c811, bcdDevice= 2~~you will find that the GPIO pin will be switched between 0 and 3.3v.00Use this program to test whether the GPIO port can work normally'''

~~[ 118.767181] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3~~

~~[ 118.767199] usb 2-1~~'''The method of running blink_all_gpio program is shown below: ~~Product: 802.11ac NIC~~'''</big>

~~[ 118.767219] usb 2-1~~orangepi@orangepi3b: ~~Manufacturer: Realtek~~~$ '''sudo blink_all_gpio'''         #Remember to add Sudo permissions

[ ~~118.767235~~sudo] ~~usb 2-1~~password for orangepi: ~~SerialNumber: 123456~~       #You need to enter password here'''|}

~~[ 119~~# There are a total of '''28''' GPIO ports in the 40pins of the development board that can be used.~~500530] usbcore: registered new interface driver rtl8821cu~~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

::[[ ~~119.525498] rtl8821cu 2~~File:pi3b-img259-1:1.~~0 wlx1cbfced9d260: renamed from wlan0~~png]]

<ol start="42" style="list-style-type: decimal;"><li>~~Then you can see~~ First set the ~~WiFi device node through~~ GPIO port as the ~~'''sudo ifconfig''' command. Please refer~~ output mode, the third parameter needs to enter the serial number of the wPi corresponding to the ~~[[\l|'''WiFi connection test a section''']] for WIFI connection and testing methods. I won't go into details her~~pins</li~~></ol~~>

~~orangepi~~{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ /wiringOP# '''~~sudo ifconfig wlx1cbfced9d260~~gpio mode 2 out'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then set the GPIO port to output the low level. After setting, you can use the value of the voltage of the pins with a multimeter. If it is 0v, it means that the low level flat is successful</li>

~~wlx1cbfced9d260~~{| class="wikitable" style="width:800px;" |-| root@orangepi: ~~flags~~~/wiringOP# '''gpio write 2 mtu 1500"color:#FF0000">0'''|}

~~ether 1c:bf:ce:d9:d2:60 txqueuelen 1000~~ Using GPIO Readall, you can see the value of the No. 7 pin (~~Ethernet~~V)to 0

~~RX packets 0 bytes 0 (0~~[[File:pi3b-img260.~~0 B)~~png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then set the GPIO port to output a high level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is 3.3v, it means that the high level is set successfully.</li>

~~RX errors 0 dropped 0 overruns 0 frame 0~~{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio write 2 1'''|}

~~TX packets 0 bytes 0~~ Using GPIO Readall, you can see the value of No. 7 pin (~~0.0 B~~v)into 1

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~[[File:pi3b-img261-1.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>The setting method of other pins is similar, just modify the serial number of wPi to the corresponding serial number of the pin</li></ol>

~~==== RTL8821CU test ====~~

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

~~orangepi@orangepi~~{| class="wikitable" style="background-color:~$ #ffffdc;width:800px;" |-| <big>'''~~lsusb | grep "Realtek"~~Note that the 4 GPIO pins below Orange Pi 3B are invalid because there are 3.3V on the outside, so setting drop-down is invalid. Other pins can be set normally '''</big>

~~Bus 002 Device 003~~[[File: ~~ID 0bda:c820 Realtek Semiconductor Corp. 802~~pi3b-img262-1.~~11ac NIC~~png|center]]|}

~~orangepi@orangepi:~$ '''lsusb | grep "Realtek"'''~~# 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

~~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 -insert the USB WiFi module. If not, please manually execute the following command to switch the mode~~[[File: ~~'''~~ ~~orangepi@orangepi:~$ '''sudo usb_modeswitch~~ pi3b-KW img263-~~v 0bda -p 1a2b'''~~1.png]]

<li>First of all, you need to set the GPIO port as the input mode. The third parameter needs to enter the serial number of the wPi corresponding to the pins</li>

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

|-

|

root@orangepi:~/wiringOP# '''gpio mode 5 in'''

|}

</ol>

<li>~~The Linux system will automatically load~~ After the ~~RTL8821CU Bluetooth and WIFI~~ setting is set to input mode, execute the following command to set the GPIO port as the pull-~~related kernel modules~~down mode</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio mode 5 up'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then enter the following command to read the level of the GPIO port. ~~You can see~~ If the level is 1, it means that the ~~kernel module below~~ drawing mode is ~~automatically loaded through the lsmod command~~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# '''~~lsmod~~gpio read 5'''

~~Module Size Used by~~'''0'''|}</ol>

~~8821cu 1839104 0~~=== 40pin SPI Test ===

~~rtk_btusb 61440 0~~# From the schematic diagram of the 40PIN interface, the SPI available for Orange Pi 3B is spi3

~~<ol start="4" style="list~~::[[File:pi3b-~~style~~img264-~~type: decimal;"><li>You can see the loading information of the rtl8821cu module through the dmesg command</li></ol>~~1.png]]

<ol start="2" style="list-style-type: decimal;"><li>In the linux system, the SPI in the 40 pin is closed by default, and it needs to be opened manually before it can be used. The detailed steps are as follows:<ol style="list-style-type: lower-alpha;"><li>First run '''orangepi-config''', normal users remember to add sudo permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~dmesg~~sudo orangepi-config'''|}</li><li>Then select '''System'''[[File:pi3b-1.png]]</li><li>Then select '''Hardware'''[[File:pi3b-2.png]]</li><li>Then use the arrow keys on the keyboard to navigate to the position shown in the figure below, and then use the '''space''' to select the SPI configuration you want to open[[File:pi3b-3.png]]</li><li>Then select '''<Save>''' to save[[File:pi3b-4.png]]</li><li>Then select '''<Back>'''[[File:pi3b-5.png]]</li><li>Then select '''<Reboot>''' to restart the system to make the configuration take effect[[File:pi3b-6.png]]</li></ol></li></ol>

<ol start="3" style="list-style-type: 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.083693] usb 2~~{| class="wikitable" style="width:800px;" |-1| orangepi@orangepi: ~~new high-speed USB device number 2 using ehci-platform~~~$ '''ls /dev/spidev3.0'''

~~[ 57~~/dev/spidev3.~~231888] usb 2~~0|}</ol><ol start="4" style="list-1style-type: ~~New USB device found~~decimal;"><li>Do not short-circuit the mosi and miso pins of SPI3, ~~idVendor=0bda~~the output result of running spidev_test is as follows, ~~idProduct=1a2b, bcdDevice= 2.00~~you can see that the data of TX and RX are inconsistent</li>

~~[ 57.231916] usb 2~~{| class="wikitable" style="width:800px;" |-1| orangepi@orangepi: ~~New USB device strings: Mfr=1, Product=2, SerialNumber=~~~$ '''sudo spidev_test -v -D /dev/spidev3.0'''

~~[ 57.231937] usb 2-1~~spi mode: ~~Product: DISK~~0x0

~~[ 57.231956] usb 2-1~~bits per word: ~~Manufacturer: Realtek~~8

~~[ 57.242594] usb-storage 2-1~~max speed:~~1.0: USB Mass Storage device detected~~500000 Hz (500 KHz)

~~[ 57~~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 | ......@.…▒...~~245674] scsi host0: usb-storage 2-1:1~~.0..............▒.

~~[ 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 | ............................….~~069172] usb 2~~|}</ol><ol start="5" style="list-style-1type: ~~USB disconnect~~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, ~~device number 2~~you can see the sending and receiving same data</li>

[ 58[File:pi3b-img265.~~440025~~png] ~~usb 2~~]{| class="wikitable" style="width:800px;" |-1| orangepi@orangepi: ~~new high~~~$ '''sudo spidev_test -~~speed USB device number 3 using ehci~~v -~~platform~~D /dev/spidev3.0'''

~~[ 58.587819] usb 2-1~~spi mode: ~~New USB device found, idVendor=0bda, idProduct=c820, bcdDevice= 2.00~~0x0

~~[ 58.587827] usb 2-1~~bits per word: ~~New USB device strings: Mfr=1, Product=2, SerialNumber=3~~8

~~[ 58.587833] usb 2-1~~max speed: ~~Product: 802.11ac NIC~~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 | ......@.…▒..................▒.~~587838] usb 2-1: Manufacturer: Realtek~~

~~[ 58~~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 | ......@.~~587844] usb 2~~…▒..................▒.|}</ol>

~~[ 58.610463] rtk_btusb: Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-142432~~=== 40pin I2C Test ===

~~[ 58~~# From the table below, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total of three groups of I2C bus.~~610656] usbcore: registered new interface driver rtk_btusb~~

::[[ 58File:pi3b-img266-1.~~634631~~png]] ~~Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821~~

~~[ 58.636729] Bluetooth: hci0~~: ~~RTL~~: ~~rom_version status~~{| class=~~0 version~~"wikitable" style=1"background-color:#ffffdc;width:800px;" |-| <big>'''It can be seen from the above table that i2c4_m0 and spi3_m0 are pins. The two cannot be opened at the same time. i2c3_m0 and uart3_m0 are also reused. The two cannot be opened at the same time'''</big>|}

~~[ 58~~<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.~~636740] Bluetooth~~The detailed steps are as follows: ~~hci0~~<ol style="list-style-type: ~~RTL~~lower-alpha;"><li>First run '''orangepi-config''', normal users remember to add '''sudo''' permission{| class="wikitable" style="width: ~~loading rtl_bt~~800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li><li>Then select '''System'''</~~rtl8821c_fw~~p>[[File:pi3b-1.~~bin~~png]]</li><li>Then select '''Hardware'''[ 58[File:pi3b-2.~~664190~~png]] ~~Bluetooth~~</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: ~~hci0~~pi3b-3-2.png]]</li><li>Then select '''<Save>''' to save[[File: ~~RTL~~pi3b-4.png]]</li><li>Then select '''<Back>'''[[File: ~~loading rtl_bt~~pi3b-5.png]]</li><li>Then select '''<Reboot>''' to restart the system to make the configuration take effect</~~rtl8821c_config~~p>[[File:pi3b-6.~~bin~~png]]</li></ol></li></ol>

~~[ 58.664746] Bluetooth~~<ol start="3" style="list-style-type: ~~hci0~~decimal;"><li>After starting the Linux system, first confirm that the i2c device node exists under/dev</li>{| class="wikitable" style="width: ~~RTL~~800px;" |-| orangepi@orangepi: ~~cfg_sz 10, total sz 31990~~~# '''ls /dev/i2c-*'''

~~[ 59.122471] Bluetooth: hci0: RTL: fw version 0x829a7644~~/dev/i2c-0      '''/dev/i2c-2'''      '''/dev/i2c-3'''      '''/dev/i2c-4'''      /dev/i2c-6~~[ 59.265513] usbcore: registered new interface driver rtl8821cu~~|}</ol>~~[ 59.280119] rtl8821cu 2~~<ol start="4" style="list-style-1type:~~1.2 wlx90de80521825: renamed from wlan0~~decimal;"><li>Then connect a i2c device on the i2c pin of the 40Pin connector</li>

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

|-

|

|i2c2-m1

|i2c3-m0

|i2c4-m0

|-

|

Sda Pin

|Corresponding to No. 3 pin

|Corresponding to No. 27 pin

|Corresponding to No. 19 pin

|-

|

Sck Pin

|Corresponding to No. 5 pin

|Corresponding to No. 28 pin

|Corresponding to No. 23 pin

|-

|

Vcc Pin

|Corresponding to No. 1 pin

|-

|

Gnd Pin

|Corresponding to No. 6 pin

|}

</ol>

<li>Then ~~you can see the RTL8821CU WiFi device node through~~ use the '''~~sudo ifconfig~~i2cdetect -y''' command~~. Please refer to~~ if the address of the connected I2C device can be detected, it means that the ~~[[\l|'''WiFi connection test''']] a section for WIFI connection and testing methods.~~I2C can be used normally</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ sudo i2cdetect -y 2 #i2c2 command

orangepi@orangepi:~$ ~~'''~~sudo ~~ifconfig wlx90de80521825'''~~i2cdetect -y 3 #i2c3 command

~~wlx90de80521825~~orangepi@orangepi: ~~flags=4099<UP,BROADCAST,MULTICAST> mtu 1500~~~$ sudo i2cdetect -y 4 #i2c4 command|}

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

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

~~RX errors 0 dropped 0 overruns 0 frame 0~~</div></ol>

~~TX packets 0 bytes 0 (0.0 B)~~=== 40pin UART test ===

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~# 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

~~<ol start="6" style="list~~::[[File:pi3b-~~style~~img268-~~type: decimal;"><li>Then you can see the USB Bluetooth device through the '''hciconfig''' command</li></ol>~~1.png]]

~~orangepi@orangepi~~:~~~$ '''sudo apt~~:{| class="wikitable" style="background-~~get update &amp~~color:#ffffdc;~~&amp~~width:800px; ~~sudo apt~~" |-~~get install -y bluez~~| <big>'''As can be seen from the above table, i2c3_m0 and uart3_m0 are reused by pins, and the two cannot be opened at the same time'''</big>|}

<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:~$ '''~~hciconfig~~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-4.png]]</li><li>Then select '''<Back>'''[[File:pi3b-5.png]]</li><li>Then select '''<Reboot>''' to restart the system to make the configuration take effect[[File:pi3b-6.png]]</li></ol></li></ol>

~~hci0~~<ol start="3" style="list-style-type: ~~Type: Primary Bus: '''USB'''~~decimal;"><li>After entering the Linux system, first confirm whether there is a device node corresponding to uart under/dev</li>

~~BD Address~~{| class="wikitable" style="width: 00800px;" |-| orangepi@orangepi:~~13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16~~~# '''ls /dev/ttyS*'''

~~DOWN~~/dev/ttyS1      '''/dev/ttyS3      /dev/ttyS7      /dev/ttyS9'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then start testing the uart interface, first use the rx and tx of the uart interface to be tested by DuPont</li>

~~RX bytes~~{| class="wikitable" style="width:~~1252 acl~~800px;text-align:~~0 sco:0 events:125 errors:0~~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|}

~~TX bytes~~[[File:~~23307 acl~~pi3b-img269-1.png]]</ol><ol start="5" style="list-style-type:~~0 sco~~decimal;"><li>Use the '''gpio serial''' command to test the loop function of the serial port as shown below. If you can see the following printing, it means that the serial communication is normal<ol style="list-style-type:~~0 commands~~lower-alpha;"><li>Test UART3</li>{| class="wikitable" style="width:~~125 errors~~800px;" |-| orangepi@orangepi:0~$ '''sudo gpio serial /dev/ttyS3'''

~~<ol start="7" style="list-style-type~~[sudo] password for orangepi: ~~decimal;"><li>Bluetooth icons can also be seen on~~ #Enter the ~~desktop~~password here. ~~At this time, Bluetooth has not been opened, so a red '''x''' will be displayed</li></ol>~~

~~[[File:pi3b-img243.png|576x157px]]~~

~~<ol start="8" style="list-style~~Out: 0: -~~type: decimal~~>">~~<li>Click '''Turn Bluetooth On''' to open Bluetooth</li></ol>~~0

~~[[File~~Out: 1:~~pi3b~~-~~img244.png|576x262px]]~~> 1

~~<ol start="9" style="list-style~~Out: 2: -~~type: decimal~~>">~~<li>The display after opening Bluetooth is shown below</li></ol>~~2

~~[[File~~Out: 3:~~pi3b~~-~~img245.png|576x164px]]~~> 3

~~<ol start="10" style="list-style~~Out: 4: -~~type: decimal~~>">~~<li>Please refer to the [[\l|'''Bluetooth use chapter''']] for the Bluetooth test method. I won't go into details her</li></ol>~~4

Out: 5: -> 5^C|}</ol><~~span id~~ol start="~~usb~~2" style="list-style-~~camera~~type: lower-~~test~~alpha;"><li>Test UART7</~~span~~li>{| class="wikitable" style=~~= USB Camera Test ===~~"width:800px;" |-| orangepi@orangepi:~$ '''sudo gpio serial /dev/ttyS7'''

[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

Out: 4: -> 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 gpio serial /dev/~~video1~~ttyS9'''

~~/dev/media0~~[sudo] password for orangepi: #Enter the password here.

~~'''Note that l in v4l2 is a lowercase letter l, not numbers 1.'''~~

~~'''In addition, Video's serial number is not necessarily Video0, please refer to what you see.'''~~Out: 0: -> 0

~~<ol start="3" style="list~~Out: 1: -~~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>~~1

~~[[File~~Out: 2:~~pi3b~~-~~img246.png|474x302px]]~~> 2

~~The interface after cheese opens the USB camera is shown in the figure below~~Out: 3: -> 3

~~[[File~~Out: 4:~~pi3b~~-~~img247.png|473x277px]]~~> 4

~~<ol start="4" style="list-style-type~~Out: ~~decimal;"><li>How to test the USB camera using fswebcam<ol style="list-style-type~~5: ~~lower~~-~~alpha~~>">5^C|}~~<li>Install fswebcam</li>~~</ol>

</li></ol>

=== PWM test method ===

~~orangepi@orangepi:~$ '''sudo''' '''apt update'''~~# From the table below, the pwm11 available for Orange Pi 3B

~~orangepi@orangepi~~:~~~$ '''sudo apt~~:[[File:pi3b-~~get install~~ img270-~~y fswebcam'''~~1.png]]

<ol start="2" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~After installing fswebcam~~In the linux system, ~~you can use~~ the ~~following command~~ PWM in the 40 pin is turned off by default, and it needs to ~~take pictures~~be turned on manually before it can be used. The detailed steps are as follows:

<li>First run '''orangepi-~~d The option is used~~ config''', normal users remember to ~~specify the device node of the USB camera~~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-~~no-banner Used to remove the watermark of photos~~2.png]]</li><li>~~-r The option is used~~ Then use the arrow keys on the keyboard to navigate to ~~specify~~ the ~~resolution of~~ position shown in the ~~photo~~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-~~S The option is set to the number of frames before skipping~~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</~~image~~p>[[File:pi3b-6.~~jpg The name and path for setting the generated photos~~png]]</li></ol>

</li></ol>

~~orangepi@orangepi~~<ol start="3" style="list-style-type:~$ decimal;"><li>After opening a pwm, there will be an extra pwmchipX in '''/sys/class/pwm/'~~sudo~~''(X is a specific number), for example, after opening pwm11, check the pwmchipX under ' ''/sys/class/pwm/'~~fswebcam~~ '' one becomes two</li>{| class="wikitable" style="width:800px;" |-d | orangepi@orangepi:~$ '''ls /sys/class/~~dev~~pwm/~~video0 \~~'''

pwmchip0 pwmchip1|}</ol><ol start="4" style="list-style-type: decimal;"><li>Which pwmchip above corresponds to pwm11, let's check the output of the '''ls /sys/class/pwm/ -l''' command first, as shown below:</li><li>Then it can be known from the table below that the base address of the pwm11 register is fe6f0030, and then look at the output of the '''ls /sys/class/pwm/ -~~no-banner -r 1280x720 -S 5 ./image.jpg~~l'''command, you can see that pwmchip1 is linked to fe6f0030.pwm, so pwm11 corresponds to pwmchip as pwmchip1</li>

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

~~orangepi@orangepi:~$ '''scp image.jpg'''~~ [~~mailto~~[File:~~test@192~~pi3b-img271.~~168.1.55:/home/test test@192.168.1.55:/home/test~~png]] ~~'''（Modify the IP address and path according to the actual situation）'''~~

</div></ol><ol start="46" style="list-style-type: ~~lower-alpha~~decimal;"><li>In Then use the ~~desktop version of~~ following command to make pwm11 output a 50Hz square wave (please switch to the ~~Linux system~~root user first, ~~you can directly view~~ and then execute the ~~shot pictures through the HDMI display~~following command)</li><{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''echo 0 > /sys/class/pwm/pwmchip1/~~ol>~~export'''

~~<~~root@orangepi:~# '''echo 20000000 > /~~span>== Audio Test ==~~sys/class/pwm/pwmchip1/pwm0/period'''

~~<~~root@orangepi:~# '''echo 1000000 > /~~span>=== Test audio methods in the desktop system ===~~sys/class/pwm/pwmchip1/pwm0/duty_cycle'''

root@orangepi:~# ~~First open the file manager~~'''echo 1 > /sys/class/pwm/pwmchip1/pwm0/enable'''|}

[[File:pi3b-~~img248~~img272.png~~|357x176px~~]]

~~<ol start="2" style="list-style-type: decimal;">~~<li>~~Then find the following file (if there~~ The test method of pwm11 demonstrated above is ~~no audio file in the system, you can upload a audio file~~ similar to ~~the system by yourself)~~other pwm test methods.</li></ol>

~~<div class~~=~~"figure">~~= How to install and use wiringOP-Python ==

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~pi3b~~800px;" |-| <big>'''wiringOP-~~img249~~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.~~png|236x186px|图片10]]~~'''

~~</div>~~

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

~~<li>Then select the audio.wav file, right -click and select VLC to open it to start playing</li></ol>~~

~~[[File:pi3b-img250~~'''In addition, please note that all the following commands are operated under the root user.~~png~~'''</big>|~~288x234px]]~~}

<~~ol start~~span id="~~4" style="list~~wiringop-python-~~style~~installation-~~type: decimal;~~method">~~<li>Methods to switch different audio equipment such as HDMI playback and headset playback~~</pspan>~~<ol style~~=~~"list~~== wiringOP-~~style-type: lower-alpha;"><li>First open the volume control interface</li></ol></li></ol>~~Python installation method ===

~~[[File:pi3b-img251.png|308x169px]]~~# First install the dependency package

~~<ol start~~::{| class="2wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>When playing audio, the audio equipment options that play software can be used will be displayed in~~ |-| root@orangepi:~# '''~~Playback~~sudo apt-get update'''~~. As shown in the figure below, which audio equipment you need to play here can be set.</li></ol>~~

~~[[File~~root@orangepi:~~pi3b~~~# '''sudo apt-~~img252.png~~get -y install git swig python3-dev python3-setuptools'''|~~576x282px]]~~}

<~~span id~~ol start="~~how-to-play-audio~~2" style="list-~~with~~style-~~commands~~type: decimal;"><li>Then use the following command to download the source code of wiringOP-Python</~~span~~li>{| class="wikitable" style=~~= How~~ "background-color:#ffffdc;width:800px;" |-| <big>'''Note that the following git clone--recursivee command will automatically download the source code of wiringOP, because wiringOP-Python depends on wiringOP. Please make sure that the download process does not report an error due to ~~play audio with commands ===~~network problems.'''

~~~~

~~==== Headphone interface play audio test ====~~

~~# First insert~~ '''If there is a problem with the download code from GitHub, you can use the ~~headset into~~ wiringOP-Python source code that comes with the ~~headphone jack of~~ Linux image directly, and the ~~development board~~storage location is:/usr/src/wiringOP-Python'''</big>|}~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img253~~| root@orangepi:~# '''git clone --recursive https://github.~~png|395x112px]]~~com/orangepi-xunlong/wiringOP-Python -b next'''

~~<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~~ cd wiringOP-~~l''' command. From the output below, it can be seen that '''card 0~~Python''' ~~is the sound card device with RK809, which is the sound card device of the headset</li></ol>~~

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

root@orangepi:~/wiringOP-Python# '''~~card 0~~sudo python3 setup.py install'''|}</ol><ol start="4" style="list-style-type: ~~rockchiprk809 [rockchip-rk809]~~decimal;"><li>Then enter the following command. If there is a help information output, ~~device 0: dailink~~it means that Wiringop-~~multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]~~Python is successfully installed. Press the '''q'''key to exit the interface of the help information</li>

{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''~~Subdevices: 0/1~~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 headset can hear the sound, it means that the hardware can be used normally</li></ol>~~DESCRIPTION

~~orangepi@orangepi~~:~~~$ '''aplay -D hw~~# This file was automatically generated by SWIG (http:~~0,0~~ /~~usr~~/~~share/sounds/alsa/audio~~www.swig.org).~~wav'''~~

~~Playing WAVE 'audio~~: # Version 4.~~wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo~~0.2

~~==== HDMI Audio Play Test ====~~: #

: # ~~First use the HDMI~~ Do not make changes 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,~~ this file unless you ~~can~~ know ~~that the HDMI sound card is '''card 1'''~~what you are doing--modify

~~orangepi~~: # the SWIG interface file instead.|}</ol><ol start="5" style="list-style-type: decimal;"><li>Test whether the wiringOP-Python is installed successfully under the Python command line is shown below:<ol style="list-style-type: lower-alpha;"><li>First use the Python3 command to enter the command line mode of Python3</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ # '''python3''~~aplay~~ '|}</ol><ol start="2" style="list-lstyle-type: lower-alpha;"><li>Then import the Python module of WiringPi</li>{| class="wikitable" style="width:800px;" |-| >>> '''import wiringpi;'''|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Enter the following command to view the help information of wiringOP-Python, and press the '''q''' key to exit the interface of the help information</li>{| class="wikitable" style="width:800px;" |-| >>> '''help(wiringpi)'''

~~**** List of PLAYBACK Hardware Devices ****~~Help on module wiringpi:

~~card 0: rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]~~

~~Subdevices: 0/1~~NAME

~~Subdevice #0~~: ~~subdevice #0~~wiringpi

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

~~'''Subdevices: 0/1'''~~DESCRIPTION

~~'''Subdevice~~ : #0This file was automatically generated by SWIG (http: ~~subdevice #0'''~~//www.swig.org).

~~'''Subdevice #0~~: ~~subdevice~~ #Version 4.0~~'''~~.2

~~<ol start="3" style="list-style-type~~: ~~decimal;"><li>Then use the '''aplay''' command to play the audio file that comes with the system. If the HDMI display or television can hear the sound indicates that the hardware can be used normally</li></ol>~~#

~~orangepi@orangepi~~:~~~$ '''aplay~~ # Do not make changes to this file unless you know what you are doing-~~D hw:1,0 /usr/share/sounds/alsa/audio.wav'''~~-modify

~~=== Use the command to test the recording method ===~~SWIG interface file instead.

# 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 -c 0 cset name='Capture MIC Path' 'Main Mic''''~~CLASSES

~~orangepi@orangepi~~:~~~$ '''arecord -D hw:0,0 -d 5 -f cd -t wav /tmp/test~~builtins.~~wav'''~~object

~~== Temperature Sensor ==~~::GPIO

~~# The command of the system temperature sensor is~~: :I2C

~~orangepi@orangepi~~:~~~$ '''sensors'''~~:Serial

~~soc_thermal-virtual-0~~::nes

~~Adapter: Virtual device~~

~~temp1~~: ~~+41.9°C~~ class GPIO(~~crit = +115~~builtins.~~0°C~~object)

~~gpu_thermal-virtual-~~:| GPIO(pinmode=0)

~~Adapter~~: ~~Virtual device~~|

~~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~~ &~~quot~~gt;~~Temperature:~~&~~quot~~gt;~~'''~~|}</pol><p/li>~~Temperature: '''40 Celsius'''~~</pol><~~/li~~span id="pin-gpio-port-test-1"></olspan>

~~~~== ~~40 Pin interface pin explanation~~ 40pin GPIO port test ===

{| class="wikitable" style="background-color:# ~~Orange Pi 3B Development board 40 Pin interface pins~~ffffdc;width:800px;" |-| <big>'''wiringOP-Python is the same as wiringOP, you can also determine which GPIO pin to operate by specifying the wPi number, ~~please refer~~ because there is no command to check the ~~figure below~~wPi number in wiringOP-Python, so you can only check the board wPi number and physical Correspondence between pins.'''</big>

[[File:pi3b-~~img254~~img258.png|~~400x124px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\Orange-Pi-3B-Development-board-40-Pin(1).jpgOrange-Pi-3B-Development-board-40-Pin(1)~~center]]

</div>

|}

# Below the No. 7 pin — corresponding to GPIO4_a4 -corresponding WPI serial number 2 -to demonstrate how to set the height of the GPIO port

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

<li>The ~~function~~ steps of the ~~Orange Pi 3B development board 40 PIN interface pins is~~ command test are shown ~~in the table~~ below.directly:

<li>~~Below~~ First set the GPIO port to the output mode. The first parameter of the '''pinMode''' function is ~~a complete pins~~ the serial number of ~~40pin~~the wpi corresponding to the pin, and the second parameter is the GPIO mode</li>~~</ol>~~<{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~li></ol>~~wiringOP-Python# '''python3 -c "import wiringpi; \'''

~~[[File:pi3b-img255~~'''from wiringpi import GPIO; wiringpi.~~png|575x160px]]~~wiringPiSetup() ; \'''

'''wiringpi.pinMode(2, GPIO.OUTPUT) ; "'''

|}

</ol>

<li>~~The following form is a picture on~~ Then set the GPIO port output low level. After setting, you can use the voltage of the ~~left half~~ voltage of the ~~full table above~~universal meter to measure the pins. If it is 0V, ~~which can be seen clearly~~it means that the low -power flat is successful</li><{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~ol>~~wiringOP-Python# '''python3 -c "import wiringpi; \'''

~~[[File:pi3b-img256~~'''from wiringpi import GPIO; wiringpi.~~png|478x267px]]~~wiringPiSetup() ;\'''

'''wiringpi.digitalWrite(2, GPIO.LOW)"'''

|}

</ol>

<li>~~The following form is a picture on~~ Then set the GPIO port output high level. After setting, you can use the value of the ~~right half~~ voltage of the ~~top table above~~pins with a multimeter. If it is 3.3V, ~~which can be seen clearly~~it means that the high -power flat is successful.</li><{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~ol>~~wiringOP-Python# '''python3 -c "import wiringpi; \'''

~~[[File:pi3b-img257~~'''from wiringpi import GPIO; wiringpi.~~png|479x266px]]~~wiringPiSetup() ;\'''

'''wiringpi.digitalWrite(2, GPIO.HIGH)"'''

|}

</ol>

</li></ol>

<li>~~There are a total~~ The steps of ~~'''28''' GPIO ports~~ testing in the ~~40pin interface. The voltage~~ command line of Python3 are shown below: <ol style="list-style-type: lower-alpha;"><li>First use the Python3 command to enter the command line mode of ~~all GPIO ports is~~ Python3</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''~~3.3v~~python3'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then import the Python module of WiringPi</olli>{| class="wikitable" style="width:800px;" |-| >>> '''import wiringpi'''

>>> '''from wiringpi import GPIO'''|}<~~span id~~/ol><ol start="~~how~~3" style="list-tostyle-~~install~~type: lower-~~wiringop~~alpha;"><li>Then set the GPIO port as the output mode. The first parameter of the '''pinMode''' function is the serial number of the wpi corresponding to the pin, and the second parameter is the GPIO mode.</~~span~~li>{| class="wikitable" style= ~~How to install Wiringop ==~~"width:800px;" |-| >>> '''wiringpi.wiringPiSetup()'''

~~'''Note that Wiringop has been pre -installed in the Linux image released by Orange Pi. Unless Wiringop's code is updated, it is not necessary to re -download and install. Just use it directly.'''~~0

>>> '''~~The storage path~~ wiringpi.pinMode(2, GPIO.OUTPUT)'''|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then set the GPIO port output low level. After setting, you can use the value of the voltage of the pins with a multimeter. If it is 0V, it means that the low -power flat is set.</li>{| class="wikitable" style="width:800px;" |-| >>> '''wiringpi.digitalWrite(2, GPIO.LOW)'''|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then set the GPIO port output high level. After setting, you can use the value of the voltage of the ~~compiled~~ pins with a multimeter. If it is 3.3V, it means that the high -power flat is successful</li>{| class="wikitable" style="width:800px;" |-| >>> '''wiringpi.digitalWrite(2, GPIO.HIGH)'''|}</ol></li></ol><ol start="4" style="list-style-type: decimal;"><li>Wiringop-Python Sets GPIO high and low levels in the Python code. For reference to the ''~~s Deb is wrapped~~ 'blink.py''' test program in Examples, the voltage of the '''blink.py''' test program will set up the voltage of all GPIO ports in ~~Orangepi~~the development board 40 PIN</li>{| class="wikitable" style="width:800px;" |-~~Build~~| root@orangepi: ~/wiringOP-Python# '''cd examples'''

root@orangepi:~/wiringOP-Python/examples# '''~~orangepi-build/external/cache/debs/arm64/wiringpi_x~~ls blink.xxpy''' '''blink.~~deb~~py'''

root@orangepi:~/wiringOP-Python/examples'''~~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~~# python3 blink.py'''|}</ol>

~~<div class~~=~~"figure">~~== 40pin SPI test ===

~~[[File:pi3b-img258.png|575x355px|66AC(IBG%N8L@Y7(1BZPS`N]]~~# From the schematic diagram of the 40pin interface, the SPI available for Orange Pi 3B is spi3

~~</div>'''wiringOP is currently adapted to set the GPIO port input output, set the GPIO port output high and low level, and set the function of pulling and down resistance~~::[[File:pi3b-img264. ~~It is impossible to use functions like hardware PWM.'''~~png]]

::{| class="wikitable" style="background-color:# ~~Download~~ ffffdc;width:800px;" |-| <big>'''In the ~~code of Wiringop~~Linux system, the spi3 in 40pin is closed by default, and it needs to be opened manually to use.'''

~~orangepi@orangepi:~$ '''sudo apt update'''~~

~~orangepi@orangepi:~$~~ '''~~sudo apt install -y git~~Add the configuration of the red font part below to the /boot/orangepiEnv.txt, and then restart the Linux system to open the spi4.'''</big>

~~orangepi@orangepi:~$ '''git clone https://github.com/orangepi-xunlong/wiringOP.git -b next'''~~

orangepi@orangepi:~$ '''~~Note that Orange Pi 3B needs to download the code of the wiringOP next branch, please don't miss the parameter of -b next~~sudo vim /boot/orangepiEnv.txt'''

'''~~If there is a problem with the download code from GitHub, you can use the wiringOP source code that comes with the Linux image directly, and the storage location is~~overlays=spi3-m0-cs0-spidev</~~usr/src/wiringOP~~span>'''|}

<li>~~Compile~~ First check whether there is a '''spidev3.0''' device node in the Linux system. If it exists, it means that the SPI3 has been set and ~~install wiringOP~~can be used directly</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~cd wiringOP~~ls /dev/spidev3.0'''

~~orangepi~~/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, and run the output result of the spidev_test.py as shown below. You can see that the data of TX and RX are inconsistent</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP$ -Python# '''~~sudo ./build clean~~cd examples'''

~~orangepi~~root@orangepi:~/wiringOP$ -Python/examples# '''~~sudo~~ python3 spidev_test.~~/build~~py \'''

~~<ol start="~~'''--channel 3~~" style="list~~-~~style~~-~~type: decimal;"><li>Test the output of the GPIO Readall command as follows</li></ol>~~port 0'''

~~<div class="figure">~~spi mode: 0x0

~~[[File~~max speed:~~pi3b-img258.png|575x355px|66AC~~500000 Hz (~~IBG%N8L@Y7(1BZPS`N]]~~500 KHz)

<Opening device /~~div><~~dev/~~span>== 40Pin interface GPIO, I2C, UART, SPI, and PWM test ==~~spidev3.0

TX | FF FF FF FF FF FF '''~~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.~~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 |......@.......…|

~~orangepi~~RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |.............….||}</ol><ol start="5" style="list-style-type: decimal;"><li>Then use the TXD (No. 19 pins in the 40Pin interface) and RXD (No. 21 pins in the 40pin interface) of the DuPont line short connection SPI3. Like sending and receiving data, it means that the SPI3 loop test is normal</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ /wiringOP-Python# '''~~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~~python3 spidev_test.py \'''

~~=== 40pin GPIO~~ port ~~test ===~~0'''

~~'''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.'''~~spi mode: 0x0

'''After running the blink_all_gpio program, when using a multimeter to measure the level of the GPIO port, you will find that the GPIO pin will be switched between 0 and 3.3v. Use this program to test whether the GPIO port can work normally'''max speed: 500000 Hz (500 KHz)

~~'''The method of running blink_all_gpio program is shown below: '''~~Opening device /dev/spidev3.0

~~orangepi@orangepi3b:~$~~ TX | FF FF FF FF FF FF '''~~sudo blink_all_gpio~~40 00 00 00 00 95''' ~~#Remember to add Sudo permissions~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…|

~~[sudo] password for orangepi~~RX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…||}</ol>

~~# 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~~I2C test ===

~~[[File~~<ol start="1" style="list-style-type:~~pi3b-img259.png|576x120px]]~~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 start="2" style="list~~[[File:pi3b-~~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>~~img266.png]]

~~root@orangepi~~{| class="wikitable" style="background-color:~#ffffdc;width:800px;" |-| <big>'''It can be seen from the above table that I2C4_M0 and SPI3_M0 are pins. The two cannot be opened at the same time. I2C3_M0 and UART3_M0 are also reused. The two cannot be opened at the same time'''</~~wiringOP~~big>|}{| class="wikitable" style="background-color:# ffffdc;width:800px;" |-| <big>'''~~gpio mode 2 out~~In the Linux system, the I2C in 40Pin is closed by default, and it needs to be opened manually to use.'''

~~<ol start="3" style="list-style-type: 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 -electric flat is successful</li></ol>

~~root@orangepi:~/wiringOP#~~ '''~~gpio write 2 0~~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.'''</big>

~~Using GPIO Readall, you can see the value of the No. 7 pin (v) to 0~~

~~[[File~~orangepi@orangepi:~~pi3b-img260~~~$ '''sudo vim /boot/orangepiEnv.~~png|576x120px]]~~txt'''

'''overlays=i2c2-m1 i2c3-m0 i2c4-m0'''|}</ol><ol start="42" style="list-style-type: decimal;"><li>~~Then set~~ After starting the ~~GPIO port output high level. After setting~~Linux system, ~~you can use~~ first confirm the ~~voltage of the voltage of the permanent meter to measure the voltage~~I2C device node under/dev. ~~If it is 3.3V, it means that the high-electricity level is successful~~</li~~></ol~~>

~~root~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~~~/wiringOP~~# '''~~gpio write 2 1~~ls /dev/i2c-*'''

~~Using GPIO Readall, you can see~~ /dev/i2c-0      '''/dev/i2c-2'''      '''/dev/i2c-3'''      '''/dev/i2c-4'''      /dev/i2c-6|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then connect a I2C device on the ~~value~~ I2C pin of the 40PIN connector. Here is an example of Nothe DS1307 RTC module. ~~7 pin (v) into 1~~</li>

~~[[File~~{| class="wikitable" style="width:800px;text-align:~~pi3b~~center;"|-||i2c2-m1|i2c3-m0|i2c4-m0|-| Sda Pin|Corresponding to No. 3 pin|Corresponding to No. 27 pin|Corresponding to No. 19 pin|-| Sck Pin|Corresponding to No. 5 pin|Corresponding to No. 28 pin|Corresponding to No. 23 pin|-~~img261~~| Vcc Pin|Corresponding to No. 1 pin|Corresponding to No. 1 pin|Corresponding to No. 1 pin|-| Gnd Pin|Corresponding to No. 6 pin|Corresponding to No. 6 pin|Corresponding to No.~~png~~6 pin|~~576x118px]]~~}

[[File:pi3b-img273.png]]</ol><ol start="54" style="list-style-type: decimal;"><li>~~The setting method of other pins is similar. Just modify~~ Then use the '''i2cdetect -y''' command If the ~~serial number~~ address of the ~~wPi sequence number as the corresponding serial number corresponding to~~ connected I2C device can be detected, it means that the ~~pin~~I2C can be used normally</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ sudo i2cdetect -y 2 #i2c2 command

~~=== 40Pin GPIO Port -down and downward pull -down resistance setting method ===~~y 3 #i2c3 command

~~'''Note that the~~ orangepi@orangepi:~$ sudo i2cdetect -y 4 ~~GPIO pins below Orange Pi 3B are invalid because there are 3.3V on the outside, so setting drop -down is invalid. Other pins can be set normally'''~~#i2c4 command|}

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

~~# Below the No~~[[File:pi3b-img274. ~~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~~png]]

~~[[File~~</div></ol><ol start="5" style="list-style-type:~~pi3b~~decimal;"><li>You can then run the time of the ds '''ds1307.py''' test program in '''examples''' to read the RTC time</li>{| class="wikitable" style="width:800px;" |-~~img263.png~~|~~576x147px]]~~root@orangepi:~/wiringOP-Python# '''cd examples'''

~~<ol start="2" style="list-style-type~~root@orangepi: ~~decimal;"><li>First of all, you need to set the GPIO port as the input mode. The third parameter needs to enter the serial number of the wpi corresponding to the pins<~~~/~~li><~~wiringOP-Python/~~ol>~~examples# '''python3 ds1307.py --device \'''

~~root@orangepi:~/wiringOP#~~ '''~~gpio mode 5 in~~"/dev/i2c-4"'''

~~<ol start="3" style="list~~Thu 2023-~~style~~01-~~type~~05 14: ~~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>~~57:55

~~root@orangepi~~Thu 2023-01-05 14:~~~/wiringOP# '''gpio mode 5 up'''~~57:56

~~<ol start="4" style="list~~Thu 2023-~~style~~01-~~type~~05 14: ~~decimal;"><li>Then enter the following command to read the level of the GPIO port. If the level is 1, it means that the drawing mode is successful</li></ol>~~57:57

~~root@orangepi:~/wiringOP# '''gpio read 5'''~~^C

~~'''1'''~~exit|}</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></ol>~~= 40pin's UART test ===

~~root@orangepi:~/wiringOP~~# ~~'''gpio mode 5 down'''~~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

~~<ol start="6" style="list-style~~::[[File:pi3b-~~type: decimal;"><li>Then enter the following command to read the level of the GPIO port~~img268. ~~If the level is 0, it means that the drop -down mode is set successfully</li></ol>~~png]]

~~root@orangepi~~:~~~/wiringOP~~:{| class="wikitable" style="width:800px;background-color:# ffffdc;" |-| <big>'''~~gpio read 5~~As can be seen from the above table, I2C3_M0 and UART3_M0 are reused by pins, and the two cannot be opened at the same time'''</big>|}

::{| class="wikitable" style="width:800px;background-color:#ffffdc;" |-| <big>'''0In the Linux system, the UART in 40pin is closed by default, and it needs to be opened manually to use.'''

~~=== 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~~UART3, UART7, and UART9 at the same time.If you only need to open one, you can fill in one'''</big>

orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''

'''overlays=~~spi3~~uart3-m0uart7-~~cs0~~m2 uart9-~~spidev~~m2'''|}

<li>~~First check~~ After entering the Linux system, first confirm whether there is a ~~'''spidev3.0'''~~ device node ~~in the Linux system. If it exists, it means that the SPI3 has been set. You can use it directly~~corresponding to UART under/dev</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ # '''ls /dev/~~spidev3.0~~ttyS*''' ~~/dev/spidev3.0~~

/dev/ttyS1      '''/dev/ttyS3      /dev/ttyS7      /dev/ttyS9'''

|}

</ol>

<li>~~Do not shorten~~ Then start testing the ~~two pins of the SPI3 MOSI and MISO~~UART interface, and ~~run~~ first use the ~~output result~~ RX and TX of the ~~spidev_test as shown below. You can see that the data of TX and RX is inconsistent~~UART interface to be tested by DuPont</li~~></ol~~>

~~orangepi~~{| class="wikitable" style="width:800px;text-align: center;"|-||uart3|uart7|uart9|-| Tx Pin|Corresponding to the 28 pin|Corresponding to the 16 pin|Corresponding to the 29 pin|-| Rx Pin|Corresponding to the 27 pin|Corresponding to the 15 pin|Corresponding to the 7 pin|}</ol><ol start="4" style="list-style-type: decimal;"><li>Use the '''serialTest.py''' program in Examples to test the loop function of the serial port. If you can see the printing below, it means that the serial communication is normal<ol style="list-style-type: lower-alpha;"><li>Test UART3</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ /wiringOP-Python/examples# '''~~sudo spidev_test~~ python3 serialTest.py -v -~~D /dev/spidev3.0~~device \'''

~~spi mode: 0x0~~'''"/dev/ttyS3"'''

~~bits per word: 8~~

~~max speed~~Out: ~~500000 Hz (500 KHz)~~0: -> 0

~~TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.~~Out: 1: -> 1

~~RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF | ............................….~~Out: 2: -> 2

~~<ol start="4" style="list-style~~Out: 3: -~~type: decimal~~>"><li>Then the two pins of the SPI3 MOSI (No. 19 pins in the 40pin interface) and MISO (No. 21 in the 40PIN interface) run the output of SPIDEV_TEST as follows.You can see that sending and receiving data is the same.</li></ol>3

~~[[File~~Out:~~pi3b-img265.png|577x83px]]~~4:^C

~~orangepi~~exit|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Test UART7</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ /wiringOP-Python/examples# '''~~sudo spidev_test~~ python3 serialTest.py -v -~~D /dev/spidev3.0~~device \'''

~~spi mode: 0x0~~'''"/dev/ttyS7"'''

~~bits per word: 8~~

~~max speed~~Out: ~~500000 Hz (500 KHz)~~0: -> 0

~~TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.~~Out: 1: -> 1

~~RX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.~~Out: 2: -> 2

~~=== 40pin I2C Test ===~~> 3

~~# From the table below, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total of three groups of I2C bus.~~Out: 4:^C

~~[[File~~exit|}</ol><ol start="3" style="list-style-type:~~pi3b~~lower-~~img266~~alpha;"><li>Test UART9</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python/examples# '''python3 serialTest.~~png|576x160px]]~~py --device \'''

'''~~It can be seen from the above table that i2c4_m0 and spi3_m0 are pins. The two cannot be opened at the same time. i2c3_m0 and uart3_m0 are also reused. The two cannot be opened at the same time~~"/dev/ttyS9"'''

~~'''In the Linux system, the i2c in 40Pin is closed by default, and it needs to be opened manually to use.'''~~

'''Add the configuration of the red font part below to the /boot/orangepiEnv.txt, and then restart the Linux system to open the i2c2, i2c3, and i2c4 at the same time. If you only need to open one, then fill in one.'''Out: 0: -> 0

~~orangepi@orangepi~~Out:~~~$ '''sudo vim /boot/orangepiEnv.txt'''~~1: -> 1

~~'''overlays=i2c2~~Out: 2: -~~m1 i2c3-m0 i2c4-m0'''~~> 2

~~<ol start="2" style="list-style~~Out: 3: -~~type: decimal~~>">~~<li>After starting the Linux system, first confirm that the i2c device node exists under/dev</li></ol>~~3

~~orangepi@orangepi~~Out:~~~# '''ls /dev/i2c-*'''~~4:^C

~~/dev/i2c-0 '''/dev/i2c-2''' '''/dev/i2c-3''' '''/dev/i2c-4''' /dev/i2c-6~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then connect a i2c device on the i2c pin of the 40Pin connector</li></ol>~~ ~~{| class="wikitable"~~|-|~~| style="text-align: left;"| i2c2-m1| style="text-align: left;"| i2c3-m0| style="text-align: left;"| i2c4-m0~~|-~~| Sda Pin| style="text-align: left;"| Corresponding to No. 3 pin| style="text-align: left;"| Corresponding to No. 27 pin| style="text-align: left;"| Corresponding to No. 19 pin~~|-~~| Sck Pin| style="text-align: left;"| Corresponding to No. 5 pin| style="text-align: left;"| Corresponding to No. 28 pin| style="text-align: left;"| Corresponding to No. 23 pin~~|-~~| Vcc Pin| style="text-align: left;"| Corresponding to No. 1 pin| style="text-align: left;"| Corresponding to No. 1 pin| style="text-align: left;"| Corresponding to No. 1 pin~~|-~~| Gnd Pin| style="text-align: left;"| Corresponding to No. 6 pin| style="text-align: left;"| Corresponding to No. 6 pin| style="text-align: left;"| Corresponding to No. 6 pin~~exit

|}

</ol>

</li></ol>

~~<ol start~~=~~"4" style~~=~~"list-style-type: decimal;"><li>Then use~~ Hardware watch the ~~'''i2cdetect -y''' command if the address of the connected I2C device can be detected, it means that the I2C can be used normally</li></ol>~~door dog test ==

~~orangepi@orangepi:~$ sudo i2cdetect~~ The WatchDog_test program is pre -~~y 2 #i2c2 command~~installed in the Linux system released by Orange PI, which can be tested directly.

~~orangepi@orangepi~~The method of running the WatchDog_test program is shown below:~~~$ sudo i2cdetect -y 3 #i2c3 command~~

~~orangepi@orangepi~~<ol style="list-style-type:~~~$ sudo i2cdetect~~ lower-~~y 4 #i2c4 command~~alpha;"><li>The second parameter 10 indicates the counting time of the door. If there is no dog feeding in this time, the system will restart.</li><li>We can feed the dog by pressing any keys on the keyboard (except ESC). After the dog is fed, the program will print a line of Keep Alive to indicate that the dog is successful</li>

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

~~[[File:pi3b-img267.png|476x179px|UN}~]Q}T_70O%Z%RNO8R@YE]]~~open success

~~</div>=== 40pin UART test ===~~wdt

~~# As can be seen from the table below~~put_usr return, ~~the uart available for Orange Pi 3B is uart3~~if 0, ~~uart7, and uart9. There are three sets of uart bus~~success:0

~~[[File~~The old reset time is:~~pi3b-img268.png|575x160px]]~~16

~~'''As can be seen from the above table~~return ENOTTY, ~~i2c3_m0 and uart3_m0 are reused by pins~~if -1, ~~and the two cannot be opened at the same time'''~~success:0

~~'''In the Linux system~~return ENOTTY, ~~the uart in 40pin is closed by default~~if -1, ~~and it needs to be opened manually to use.'''~~success:0

~~'''Add the configuration of the red font part below to the /boot/orangepiEnv.txt~~put_user return, ~~and then restart the Linux system to open the uart3~~if 0, ~~uart7, and uart9 at the same time. If you only need to open one, you can fill in one..'''~~success:0

~~orangepi@orangepi~~put_usr return,if 0,success:~~~$ '''sudo vim /boot/orangepiEnv.txt'''~~0

~~'''overlays=uart3-m0 uart7-m2 uart9-m2'''~~keep alive

~~<ol start="2" style="list-style-type: decimal;"><li>After entering the Linux system, first confirm whether there is a device node corresponding to uart under/dev</li></ol>~~keep alive

~~orangepi@orangepi:~# '''ls~~ keep alive|}</~~dev~~ol></~~ttyS*'''~~span>

~~/dev/ttyS1 '''/dev'''/'''ttyS3 /dev/ttyS7 /dev/ttyS9'''~~== Check the serial number of the RK3566 chip ==

~~<ol start="3" style="list-style-type: decimal;"><li>Then start testing~~ The commands of the ~~uart interface~~RK3566 chip serial number are shown below. The serial number of each chip is different, ~~first~~ so you can use the ~~rx and tx of the uart interface~~ serial number to ~~be tested by DuPont</li></ol>~~distinguish multiple development boards.

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

|-

|orangepi@orangepi:~$ '''cat_serial.sh''' Serial : '''8fa18eaf489041f0'''| } == The method of downloading and installing the balenaEtcher version of arm64 == <ol style="~~text~~list-~~align~~style-type: ~~left~~decimal;"~~| uart3~~><li>The download address of Balenaetcher ARM64 version is: | <ol style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"~~| uart7~~><li>The download address of the Deb installation package is shown below, and it needs to be installed to use</li>{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"~~| uart9~~

|-

| ~~Tx pin~~'''https://github.com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balena-etcher-electron_1.7.9+5945ab1f_arm64.deb'''| }</ol><ol start="2" style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"~~| Corresponding~~ ><li>The download address of the Appimage version that does not need to ~~the 28 pin~~be installed is shown below: </li>{| ~~style~~class="~~text-align: left;~~wikitable"~~| Corresponding to the 16 pin~~| style="~~text-align~~width: ~~left~~800px;"~~| Corresponding to the 29 pin~~

|-

| ~~Rx Pin| style="text~~'''https://github.com/Itai-~~align: left;"| Corresponding to the 27 pin| style="text~~Nelken/BalenaEtcher-~~align: left;"| Corresponding to the 15 pin| style="text~~arm/releases/download/v1.7.9/balenaEtcher-~~align: left;"| Corresponding to the~~ 1.7 ~~pin~~.9+5945ab1f-arm64.AppImage'''

|}

<div class="figure"> [[File:pi3b-~~img269~~img275.png~~|545x134px~~]]

</div></ol></li></ol><ol start="42" style="list-style-type: decimal;"><li>~~Use the '''gpio serial''' command~~ How to ~~test~~ install and use the ~~loop function~~ deb version of ~~the serial port as shown below. If you can see the following printing, it means that the serial communication is normal~~Balenaetcher:

<li>~~Test UART3~~deb version of Balenaetcher installation commands as shown below: </li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y \'''

~~orangepi@orangepi:~$~~ '''~~sudo gpio serial~~ --fix-broken ./~~dev/ttyS3~~balena-etcher-electron_1.7.9+5945ab1f_arm64.deb'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>After the deb version of Balenaetcher is installed, it can be opened in the Application</li>

~~[sudo] password for orangepi: #Enter the password here.~~<div class="figure">

~~Out: 0~~[[File: pi3b-~~> 0~~img89.png]]

~~Out: 1~~</div></ol><ol start="3" style="list-style-type: lower-~~&gt~~alpha; 1"><li>The interface after Balenaetcher is opened is shown below: </li>

~~Out: 2: -> 2~~<div class="figure">

~~Out: 3: -> 3~~ ~~Out: 4: -> 4~~ ~~Out: 5~~[[File: pi3b-~~> 5^C~~img276.png]]

</div></ol>

</li></ol>

<li>How to use the AppImage version of balenaEtcher:

<li>First add permissions to Balenaetcher</li>

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

|-

|

orangepi@orangepi:~/Desktop$ '''chmod +x balenaEtcher-1.7.9+5945ab1f-arm64.AppImage'''

|}

</ol>

<li>~~Test UART7~~Then select the AppImage version balenaEtcher right -click the mouse, and then click Execute to open balenaEtcher</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''sudo gpio serial~~ pi3b-img277.png]]</~~dev~~ol></~~ttyS7'''~~li></ol>

~~[sudo] password for orangepi: #Enter~~ == The installation method of the ~~password here.~~Bt-Panel Linux panel ==

~~Out~~{| class="wikitable" style="background-color:#ffffdc;width: 0800px;" |-| <big>'''Bt-Panel Linux panel is a server management software that improves operation and maintenance efficiency. It supports more than 100 server management functions such as one -click LAMP/LNMP/cluster/monitoring/website/FTP/database/Java (excerpted from the [https: //www.bt.cn/new/index.html official website of the Bt-~~> 0~~Panel])'''</big>|}

~~Out~~# First of all, the size of the'''/tmp''' space is needed. After setting, you need to '''restart the Linux system of the development board''', and the command is shown below: ~~-> 1~~

~~Out~~: 2: {| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo sed -i 's/nosuid/&gtamp; 2,size=2G/' /etc/fstab'''

~~Out~~orangepi@orangepi: ~~3: -> 3~~~$ '''sudo reboot'''|}

~~Out~~<ol start="2" style="list-style-type: decimal;"><li>After restarting, you can see that the size of the'''/tmp''' space has become 2G.</li>{| class="wikitable" style="width: 4800px;" |-| orangepi@orangepi: ~$ '''df -h | grep "/tmp&gtquot; 4'''

~~Out~~tmpfs      2.0G      12K      '''2.0G'''      1% /tmp|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then enter the following command in the Linux system to start the installation of the Bt-Panel</li>{| class="wikitable" style="width: 800px;" |-~~&gt~~| orangepi@orangepi:~$ '''sudo install_bt_panel.sh'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then the pagoda installation program reminds whether to install the '''Bt-Panel''' to the'''/www''' folder, and enter '''y''' at this time</li>{| class="wikitable" style="width:800px; ~~5^C~~" |-| +----------------------------------------------------------------------

<~~ol start="3" style="list~~p>| Bt-~~style-type: lower-alpha;"><li>Test UART9<~~WebPanel FOR CentOS/Ubuntu/~~li>~~Debian</olp>

~~orangepi@orangepi:~$ '''sudo gpio serial /dev/ttyS9'''~~+----------------------------------------------------------------------

~~Out: 0:~~ +----------------------------------------------------------------------~~> 0~~

~~Out~~| The WebPanel URL will be http: 1//SERVER_IP: ~~-> 1~~8888 when installed.

~~Out: 2:~~ +----------------------------------------------------------------------~~> 2~~

~~Out: 3: -> 3~~

~~Out~~Do you want to install Bt-Panel to the /www directory now?(y/n): 4'''y'''|}</ol><ol start="5" style="list-~~&gt~~style-type: decimal; 4"><li>Then you have to wait patiently. When you see the printing information below the terminal output, it means that the pagoda has been installed. The entire installation process takes about 34 minutes. There may be some differences according to the difference in network speed</li>

~~Out~~[[File: 5pi3b-img278.png|800px]]</ol><ol start="6" style="list-style-type: decimal;"><li>At this time, enter the '''panel address''' displayed above in the browser to open the login interface of the pagoda Linux panel, and then enter the '''username''' and '''password''' displayed in the corresponding position to log in to the Bt-Panel [[File: pi3b-img279.png|1200px]]</li><li>After successfully logging in to the pagoda, the following welcome interface will pop up. First, please take the intermediate user notice to read to the bottom, and then you can choose "I have agreed and read&gtquot; ~~5^C~~User Agreement ", and then click" Enter the panel " You can enter the Bt-Panel</li>

[[File:pi3b-img280.png|1200px]]</ol><~~span id~~ol start="8" style="~~pwm~~list-~~test~~style-~~method~~type: decimal;"><li>After entering the Bt-Panel, you will first prompt that you need to bind the account of the Bt-Panel official website. If you do n't have an account, you can go to the pagoda's official website ('''https://www.bt.cn''') to register one.</~~span~~li>~~=== PWM test method ===~~

~~# From~~ [[File:pi3b-img281.png|1200px]]</ol><ol start="9" style="list-style-type: decimal;"><li>The final display interface is shown in the ~~table~~ figure below. You can intuitively see some status information of the development board Linux system, such as load state, CPU usage, ~~the pwm11 available for Orange Pi 3B~~memory usage and storage space usage</li>

[[File:pi3b-~~img270~~img282.png|~~575x160px~~1200px]]</ol><ol start="10" style="list-style-type: decimal;"><li>More functions of the Bt-Panel can refer to the following information to explore by yourself</li>

{| class="wikitable" style="width:800px;" |-| Manual: [http://docs.bt.cn '''~~In the Linux system, the pwm in 40pin is closed by default, and it needs to be opened manually to use~~http://docs.bt.cn''']

Forum address: [https://www.bt.cn/bbs '''~~Add the configuration of the red font part below to the~~ https:/~~boot~~/~~orangepiEnv~~www.~~txt, and then restart the Linux system to open the pwm11~~bt.cn/bbs''']

~~orangepi@orangepi~~GitHub Link:~$ '''~~sudo vim~~ https:/~~boot~~/~~orangepiEnv~~github.~~txt~~com/aaPanel/BaoTa'''|}</ol>

~~'''overlays~~=~~pwm11-m1'''~~= Set the Chinese environment and install Chinese input method ==

~~<ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~After opening a pwm, a pwmchipX (X is a specific number) will be available in~~'''~~/sys/class/pwm/~~Note that before installing the Chinese input method, please make sure that the Linux system used in the development board is the desktop version system.'''</~~li></ol~~big>|}

~~orangepi@orangepi:~$ '''ls~~ </~~sys/class/pwm/'''~~span>=== Debian system installation method ===

~~pwmchip0 pwmchip1~~<ol style="list-style-type: decimal;"><li>First set the default '''locale''' as Chinese<ol style="list-style-type: lower-alpha;"><li>Enter the command below to start configured '''locale'''</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''|}</ol><ol start="32" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Which pwmchip corresponds to pwm11 above? Let~~Then select '~~s first check out the output of~~ ''~~'ls /sys/class/pwm/~~ zh_CN.UTF-8 UTF-l8''' ~~command~~in the pop-up interface (to move up and down through the upper and lower direction buttons on the keyboard, ~~as shown below: </li><li>The base address of~~ select it through the ~~pwm11 register is Fe6F0030. Then see~~ space key, and finally move the ~~output of~~ cursor to '''~~ls /sys/class/pwm/ -l~~<OK>''' ~~command, you can see that~~ through the ~~fe6f0030.pwm is connected to the pwmchip1~~TAB key, so then press the ~~PWM11 corresponding pwmchip is pwmchip1~~ENTER key )</li~~></ol~~>

[[File:pi3b-img283.png|1200px]]<~~div class~~/ol><ol start="3" style="~~figure~~list-style-type: lower-alpha;"><li>Then set the default '''locale''' as '''zh_CN.UTF-8'''</li>

[[File:pi3b-~~img271~~img284.png|~~576x46px~~1200px]]</ol><ol start="4" style="list-style-type: lower-alpha;"><li>After exiting the interface, the '''locale''' settings will be started. The output displayed by the command line is shown below</li>{| class="wikitable" style="width:800px;" |-|~~RCUS~~orangepi@orangepi:~$~~_~VYM{4ZS]_L}DNZQR]]~~'''sudo dpkg-reconfigure locales'''

~~</div><ol start="5" style="list-style-type: decimal;"><li>Then use the following command to allow pwm11 to output~~ Generating locales (this might take a ~~50Hz square wave (please switch to the root user first, and then execute the following command~~while)~~</li></ol>~~...

~~root@orangepi~~:~~~# '''echo 0 > /sys/class/pwm/pwmchip1/export'''~~en_US.UTF-8... done

~~root@orangepi~~:~~~# '''echo 20000000 > /sys/class/pwm/pwmchip1/pwm0/period'''~~zh_CN.UTF-8... done

~~root@orangepi~~Generation complete.|}</ol></li></ol><ol start="2" style="list-style-type:~# decimal;"><li>Then open '''~~echo 1000000 > /sys/class/pwm/pwmchip1/pwm0/duty_cycle~~Input Method'''</li>

~~root@orangepi~~[[File:~# pi3b-img285.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then select '''~~echo 1 > /sys/class/pwm/pwmchip1/pwm0/enable~~OK'''</li>

[[File:pi3b-~~img272~~img286.png~~|575x346px~~]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select '''Yes'''</li>

[[File:pi3b-img287.png]]</ol><~~span id~~ol start="~~how-to-install-and~~5" style="list-~~use~~style-~~wiringop-python~~type: decimal;"><li>Then select '''fcitx'''</~~span~~li>~~== How to install and use Wiringop-Python ==~~

[[File:pi3b-img288.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then select '''Wiringop-Python is the library of the Python language version of Wiringop. It is used to operate the development board's GPIO, I2C, SPI and UART hardware resources such as the development board in the Python program.OK'''</li>

[[File:pi3b-img289.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>'''~~Please note that all~~ Then restart the ~~following command below is operated under~~ Linux system to make the ~~root user.~~configuration effective'''</li><li>Then open '''Fcitx configuration'''</li>

[[File:pi3b-img290.png]]</ol><~~span id~~ol start="~~wiringop~~9" style="list-~~python~~style-~~installation-method~~type: decimal;"><li>Then click the + of the position shown in the figure below</~~span~~li>~~=== Wiringop-Python installation method ===~~

~~# First install the dependency package~~[[File:pi3b-img291.png]]</ol><ol start="10" style="list-style-type: decimal;"><li>Then search '''Google Pinyin''' and click '''OK'''</li>

~~root@orangepi:~# '''sudo apt-get update'''~~<div class="figure">

~~root@orangepi~~[[File:~~~# '''sudo apt~~pi3b-~~get -y install git swig python3-dev python3-setuptools'''~~img292.png]]

</div></ol><ol start="211" style="list-style-type: decimal;"><li>Then ~~use the following command~~ put '''Google Pinyin''' to ~~download~~ the ~~source code of wiringOP-Python~~front</li~~></ol~~>

~~'''Note that the following git clone~~[[File:pi3b--recursivee command will automatically download the source code of Wiringop, because Wiringop-Python depends on Wiringop. Please make sure that the download process does not report an error due to network problemsimg293.~~'''~~png]]

[[File:pi3b-img294.png]]</ol><ol start="12" style="list-style-type: decimal;"><li>Then open the '''~~If there is a problem with the download code from GitHub, you can use the Wiringop-Python source code that comes with the Linux image directly, and the storage location is:/usr/src/wiringOP-Python~~Geany'''editor to test the Chinese input method</li>

~~root@orangepi~~[[File:~~~# '''git clone~~ pi3b-~~-recursive https://github~~img295.~~com~~png]]</~~orangepi~~ol><ol start="13" style="list-style-~~xunlong~~type: decimal;"><li>The Chinese input method test is shown below</~~wiringOP-Python -b next'''~~li>

~~root~~[[File:pi3b-img296.png]]</ol><ol start="14" style="list-style-type: decimal;"><li>You can switch the Chinese and English input method through the '''Ctrl+Space''' shortcut</li><li>If the entire system is required as Chinese, the variables in '''/etc/default/locale''' can be set to '''zh_CN.UTF-8'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~# $ '''~~cd wiringOP-Python~~sudo vim /etc/default/locale'''

~~root@orangepi:~/wiringOP-Python~~# ~~'''git submodule~~ File generated by update -~~-init --remote'''~~locale

LC_MESSAGES='''<~~ol start="3"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>Then use the following command to compile wiringOP~~zh_CN.UTF-~~Python and install it into the Linux system of the development board</li>~~8</olspan>'''

~~root@orangepi:~#~~ LANG='''~~cd wiringOP~~zh_CN.UTF-~~Python~~8'''

~~root@orangepi~~LANGUAGE='''zh_CN.UTF-8</~~wiringOP-Python#~~ span>'''~~python3 generate~~|}</ol><ol start="16" style="list-style-~~bindings.py &gt~~type: decimal; ~~bindings.i~~"><li>Then '''restart the system'''to see the system displayed as Chinese</li>

~~root@orangepi~~[[File:~pi3b-img297.png]]</~~wiringOP~~ol>

~~<ol start~~=~~"4" style~~=~~"list-style-type: decimal;"><li>Then enter the following command~~= The installation method of Ubuntu 20. ~~If there is a help information output, it means that Wiringop-Python is successfully installed. Press the '''q''' key to exit the interface of the help information</li></ol>~~04 system ===

~~root@orangepi:~/wiringOP-Python~~# First open '''~~python3 -c "import wiringpi; help(wiringpi)"~~Language Support'''

~~Help on module wiringpi~~::[[File:pi3b-img298.png]]

~~NAME~~<ol start="2" style="list-style-type: decimal;"><li>Then find '''Chinese (China)''' option</li>

~~wiringpi~~[[File:pi3b-img299.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then use the left mouse button to select '''Chinese (China)''' and hold it down, and then drag it up to the beginning. The display is shown below: </li>

~~DESCRIPTION~~[[File:pi3b-img300.png]]

{| class="wikitable" style="background-color:# ~~This file was automatically generated by SWIG (http~~ffffdc;width:800px;" |-| <big>'''Note that this step is not easy to drag, please try more patiently.'''</big>|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system</~~www.swig.org).~~li>

~~# Version 4~~[[File:pi3b-img301.~~0.2~~png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then set the '''Keyboard input method system''' to '''fcitx'''</li>

[[File:pi3b-img302.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>'''Then restart the Linux system to make the configuration effective'''</li><li>After re -entering the system, please do '''not ask me again''' at the interface below, and then determine whether the standard folder should be updated as Chinese based on your preference.</li>

~~# Do not make changes to this file unless you know what you are doing~~[[File:pi3b-img303.png]]</ol><ol start="8" style="list-style-~~modify~~type: decimal;"><li>Then you can see that the desktop is displayed as Chinese</li>

# [[File:pi3b-img304.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then we can open the '''Geany''' to test Chinese input method , and the way to open is shown in the ~~SWIG interface file instead.~~figure below</li>

[[File:pi3b-img305.png]]</ol><ol start="510" style="list-style-type: decimal;"><li>~~Test whether~~ After opening '''Geany''', the ~~Wiringop-Python~~ default is ~~installed successfully under~~ an English input method. We can switch into Chinese input method through the ~~Python command line is shown below: <ol style="list-style-type: lower-alpha;"><li>First use the Python3 command to~~ '''Ctrl+Space''' shortcut keys, and then we can enter ~~the command line mode of Python3~~Chinese</li~~></ol></li></ol~~>

~~root@orangepi~~[[File:~~~# '''python3'''~~pi3b-img306.png]]</ol>

~~<ol start~~=~~"2" style~~=~~"list-style-type: lower-alpha;"><li>Then import the Python module~~ = The installation method of ~~WiringPi</li></ol>~~ubuntu 22.04 system ===

~~>>>~~ # First open '''~~import wiringpi;~~Language Support'''

~~<ol start="3" style="list-style-type~~: ~~lower-alpha;"><li>Enter the following command to view the help information of Wiringop~~:[[File:pi3b-~~Python, and press the '''q''' key to exit the interface of the help information</li></ol>~~img298.png]]

~~>>&gt~~<ol start="2" style="list-style-type: decimal; "><li>Then find '''~~help~~Chinese (~~wiringpi~~China)'''option</li>

~~Help on module wiringpi~~[[File:pi3b-img307.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then use the left mouse button to select '''Chinese (China)''' and hold it down, and then drag it up to the beginning. The display after dragging is shown in the figure below: </li>

~~NAME~~[[File:pi3b-img308.png]]

~~wiringpi~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that this step is not easy to drag, please try more patiently.'''</big>|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system</li>

~~DESCRIPTION~~[[File:pi3b-img309.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>'''Then restart the Linux system to make the configuration effective'''</li><li>After re -entering the system, please '''do not ask me again''' at the interface below, and then determine whether the standard folder should be updated as Chinese based on your preference</li>

~~# This file was automatically generated by SWIG (http~~[[File:pi3b-img303.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Then you can see that the desktop is displayed as Chinese</~~www.swig.org).~~li>

~~# Version 4~~[[File:pi3b-img304.~~0.2~~png]]</ol><ol start="8" style="list-style-type: decimal;"><li>Then open the Fcitx5 configuration program</li>

#[[File:pi3b-img310.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then choose to use Pinyin input method</li>

~~# Do not make changes to this file unless you know what you are doing--modify~~<div class="figure">

~~# the SWIG interface file instead~~[[File:pi3b-img311.png]]

~~CLASSES~~</div></ol><ol start="10" style="list-style-type: decimal;"><li>The interface after the selection is shown below, then click OK</li>

~~builtins~~[[File:pi3b-img312.~~object~~png]]</ol><ol start="11" style="list-style-type: decimal;"><li>Then we can open the '''Geany''' to test Chinese input method, and the way to open is shown in the figure below</li>

~~GPIO~~[[File:pi3b-img305.png]]</ol><ol start="12" style="list-style-type: decimal;"><li>After opening '''Geany''', it is still an English input method by default. We can switch into Chinese input methods through the '''Ctrl+Space''' shortcut keys, and then we can enter Chinese</li>

~~I2C~~[[File:pi3b-img313.png]]</ol>

~~Serial~~== How to remotely log in to the Linux system desktop method ==

~~nes~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Ubuntu Gnome Wayland image does not support Nomachine and VNCs introduced here to remotely log in to the desktop.'''</big>|}

~~class GPIO(builtins.object)~~=== Use nomachine remote login ===

{| ~~GPIO(pinmode~~class=0)"wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Make sure the Ubuntu or Debian system installed on the development board is a desktop version. In addition, nomachine also provides detailed documents. It is strongly recommended to read this document to be familiar with the use of nomachine. The document links are shown below: '''

'''https://knowledgebase.nomachine.com/DT10R00166'''</big>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Nomachine supports Windows, Mac, Linux, iOS, and Android platforms, so we can remotely log in to control Orange PI development boards through Nomachine on multiple devices. The following demonstrates the Linux system desktop of the Orange PI development board through Nomachine in Windows. For installation methods for other platforms, please refer to the official documentation of Nomachine.'''</big>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Before operation, please ensure that the Windwos computer and the development board are in the same local area network, and can log in to the Ubuntu or Debian system that can log in to the development board normally.'''</big>|}

<ol style="list-style-type: decimal;"><li>First download the nomachine software Linux '''ARM64''' DEB version of the installation package, and then install it in the Linux system of the development board<ol style="list-style-type: lower-alpha;"><li>Since RK3566 is a SOC of the ARMV8 architecture, the system we use is Ubuntu or Debian, so you need to download '''NoMachine for ARM ARMv8 DEB''' installation package here. The download link is shown below: </li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that this download link may change, please recognize the DEB package of the ARMV8/ARM64 version.'''</big>|}{| class="wikitable" style="width:800px;" |-| [https://www.nomachine.com/download/download&~~gt;~~id=112&~~gt;~~s=ARM '''https://downloads.nomachine.com/download/?id=118&gtamp;distro=ARM''']|}

[[File:pi3b-img314.png]]</ol><~~span id~~ol start="~~pin-gpio~~2" style="list-~~port~~style-~~test~~type: lower-1alpha;"><li>In addition, you can also download the installation package to '''NoMachine''' in the '''official tools'''.</~~span~~li>~~=== 40pin GPIO port test ===~~

~~'''Wiringop~~[[File:pi3b-~~Python is the same as Wiringop~~img315. 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.'''png]]

~~<div class="figure">~~First enter the '''remote login software-Nomachine''' folder

[[File:pi3b-~~img258~~img316.png~~|575x355px|66AC(IBG%N8L@Y7(1BZPS`N~~]]

~~</div># Below~~ Then download the ~~No. 7 pin — corresponding to GPIO4_a4 -corresponding WPI serial number 2 -to demonstrate how to set the height~~ ARM64 version of the ~~GPIO port~~ ~~[[File:pi3b-img259.png|576x120px]]~~DEB installation package

[[File:pi3b-img317.png]]

</ol>

<li>Then upload the downloaded '''nomachine_x.x.x_x_arm64.deb''' to the Linux system of the development board.</li>

<li>Then use the following command to install '''NoMachine''' in the Linux system of the development board</li>

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

|-

|

orangepi@orangepi:~$ '''sudo dpkg -i nomachine_x.x.x_x_arm64_arm64.deb'''

|}

</ol>

</li></ol>

<li>~~The steps~~ Then download the nomachine software Windows version of the ~~command test are~~ installation package, the download address is shown below ~~directly:~~ </pli>~~<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~First set the GPIO port to the output mode. The first parameter of the~~ '''~~pinMode~~Note that this download link may change.''' ~~function is the serial number of the wpi corresponding to the pin, and the second parameter is the GPIO mode~~</~~li></ol~~big>~~</li></ol>~~|}{| class="wikitable" style="width:800px;" ~~root@orangepi:~/wiringOP~~|-~~Python#~~ | '''~~python3 -c "import wiringpi; \~~https://downloads.nomachine.com/download/?id=9'''|}

[[File:pi3b-img318.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then install nomachine in Windows. '''Please restart the computer after installation'''</li><li>Then open '''~~from wiringpi import GPIO; wiringpi.wiringPiSetup() ; \~~NoMachine'''in Window</li>

~~'''wiringpi~~[[File:pi3b-img319.~~pinMode(2~~png]]</ol><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, ~~GPIO~~and then click the location shown in the red box below in the figure below.~~OUTPUT) ; "'''~~Start log in to the Linux system desktop of the development board</li>

[[File:pi3b-img320.png]]</ol><ol start="26" style="list-style-type: ~~lower-alpha~~decimal;"><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~~click '''OK'''</li~~></ol~~>

~~root@orangepi~~[[File:~pi3b-img321.png]]</~~wiringOP~~ol><ol start="7" style="list-style-~~Python#~~ type: decimal;"><li>Then enter the username and password of the Linux system in the corresponding position in the figure below, and then click '''~~python3 -c "import wiringpi; \~~OK'''to start logging in</li>

~~'''from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\'''~~<div class="figure">

~~'''wiringpi~~[[File:pi3b-img322.~~digitalWrite(2, GPIO.LOW)"'''~~png]]

</div></ol><ol start="38" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~set~~ click OK in the ~~GPIO port output high level. After setting~~next interface</li><li>Finally, you can ~~use~~ see the ~~value~~ desktop of the ~~voltage of the pins with a multimeter. If it is 3.3V, it means that the high~~ development board Linux system[[File:pi3b-~~power flat is successful~~img323.png]]</li></ol>

~~root@orangepi:~/wiringOP~~

~~'''from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\'''~~=== Use VNC remote login ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~wiringpi.digitalWrite(2~~Before operation, please ensure that the Windwos computer and the development board are in the same local area network, ~~GPIO~~and you can log in to the Ubuntu or Debian system of the development board normally.~~HIGH)"~~'''

'''<~~ol start="3"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>The steps of testing in the command line of Python3 are shown below: <ol style="list-style-type: lower-alpha;"><li>First~~ Ubuntu 20.04 tests many problems with VNC, please do not use ~~the Python3 command to enter the command line mode of Python3~~this method.</lispan>'''</olbig>~~</li></ol>~~|}

~~root@orangepi:~~~# First run the '''~~python3~~set_vnc.sh''' script settings, and '''remember to add Sudo permissions'''

~~<ol start~~::{| class="2wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Then import the Python module of WiringPi</li></ol>~~|-| orangepi@orangepi:~$ '''sudo set_vnc.sh'''

~~>>> '''import wiringpi'''~~You will require a password to access your desktops.

~~>>> '''from wiringpi import GPIO'''~~

Password:        '''<~~ol start="3"~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">#Set the VNC password here, 8 -bit characters<li/span>~~Then set the GPIO port as the output mode. The first parameter of the '~~''~~pinMode~~'~~'' function is the serial number of the wpi corresponding to the pin, and the second parameter is the GPIO mode.</li></ol>~~

Verify: &gtnbsp;&gtnbsp;&gtnbsp;    '''~~wiringpi.wiringPiSetup()~~#Set the VNC password here, 8 -bit characters'''

0Would you like to enter a view-only password (y/n)? '''n'''

~~>>> '''wiringpi~~xauth: file /root/.~~pinMode(2, GPIO.OUTPUT)'''~~Xauthority does not exist

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

~~<li>Then set the GPIO port output low level. After setting, you can use the value of the voltage of the pins with a multimeter. If it is 0V, it means that the low -power flat is set.</li></ol>~~

~~>>> '''wiringpi.digitalWrite(2, GPIO.LOW)'~~New 'X'desktop is orangepi3b:1

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

<li>Then set the GPIO port output high level. After setting, you can use the value of the voltage of the pins with a multimeter. If it is 3.3V, it means that the high -power flat is successful</li></ol>

~~>>> '''wiringpi~~Creating default startup script /root/.~~digitalWrite(2, GPIO.HIGH)'''~~vnc/xstartup

~~<ol start="4" style="list-style-type: decimal;"><li>Wiringop-Python Sets GPIO high and low levels~~ Starting applications specified in ~~the Python code. For reference to the '''blink~~/root/.~~py''' test program in Examples, the voltage of the '''blink.py''' test program will set up the voltage of all GPIO ports in the development board 40 PIN</li><~~vnc/~~ol>~~xstartup

Log file is /root~~@orangepi~~/.vnc/orangepi3b:~~~/wiringOP-Python# '''cd examples'''~~1.log

~~root@orangepi:~/wiringOP-Python/examples# '''ls blink.py'''~~

~~'''blink.py'''~~Killing Xtightvnc process ID 3047

~~root@orangepi:~/wiringOP-Python/examples'''# python3 blink.py'''~~

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

~~# From the schematic diagram of the 40pin interface, the SPI available for Orange Pi 3B is spi3~~

~~[[File:pi3b-img264~~Starting applications specified in /root/.~~png|577x193px]]~~vnc/xstartup

~~'''In the Linux system, the spi3 in 40pin~~ Log file is ~~closed by default, and it needs to be opened manually to use.'''~~ ~~'''Add the configuration of the red font part below to the~~ /~~boot~~root/~~orangepiEnv~~.~~txt, and then restart the Linux system to open the spi4.'''~~ ~~orangepi@orangepi~~vnc/orangepi3b:~~~$ '''sudo vim /boot/orangepiEnv~~1.~~txt'''~~log~~'''overlays=spi3-m0-cs0-spidev'''~~|}

<li>~~First check whether there is a '''spidev3.0''' device node in~~ The steps of using MobaxTerm software to connect the development board Linux system~~. If it exists~~desktop are shown below: <ol style="list-style-type: lower-alpha;"><li>First click Session, then select VNC, ~~it means that~~ then fill in the ~~SPI3 has been set~~ IP address and ~~can be used directly~~port of the development board, and finally click OK to confirm</li~~></ol~~>

~~orangepi@orangepi:~$ '''ls /dev/spidev3.0'''~~<div class="figure">

~~/dev/spidev3~~[[File:pi3b-img324.0png]]

<~~ol start="3" style="list-style-type: decimal;"><li><p~~/div>~~You can then use the spi back function under the '''spidev_test.py''' program in Examples. The '''spidev_test.py''' program needs to specify the following two parameters:~~ </pol><ol start="2" style="list-style-type: lower-alpha;"><li>~~'''--channel''': Specify~~ Then enter the ~~channel number~~ password of ~~SPI</li><li>'''--port''': Specify~~ the ~~port number of SPI~~previously set VNC</li~~></ol></li>~~<li>Do not pick up the two pins of the SPI3 MOSI and MISO in short, and run the output result of the spidev_test.py as shown below. You can see that the data of TX and RX are inconsistent</li></ol>

~~root@orangepi~~[[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</~~wiringOP~~p>[[File:pi3b-~~Python# '''cd examples'''~~img326.png]]</li></ol></li></ol>

~~root@orangepi:~/wiringOP~~</~~examples# '''python3 spidev_test.py \'''~~span>

~~'''--channel 3 --port 0'''~~== Some programming language tests supported by Linux system ==

~~spi mode: 0x0~~=== Debian Bullseye system ===

~~max speed~~<ol style="list-style-type: ~~500000 Hz (500 KHz)~~decimal;"><li>Debian Bullseye is equipped with a gcc compilation tool chain by default, which can directly compile the C language program in the Linux system of the development board<ol style="list-style-type: lower-alpha;"><li>The version of the gcc is shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc --version'''

~~Opening device /dev/spidev3~~gcc (Debian 10.02.1-6) 10.2.1 20210110

~~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 |~~This is free software; see the source for copying conditions.~~............….|~~There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</ol><ol start="52" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then use the TXD (No. 19 pins in the 40Pin interface) and RXD (No. 21 pins in the 40pin interface)~~ Write C language of ~~the DuPont line short connection SPI3~~'''Hello_world. ~~Like sending and receiving data, it means that the SPI3 loop test is normal~~c''' program</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.c'''

~~root@orangepi:~/wiringOP-Python# '''cd examples'''~~

~~root@orangepi:~/wiringOP-Python/examples~~# ~~'''python3 spidev_test~~include <stdio.~~py \'''~~h>

~~'''--channel 3 --port 0'''~~int main(void)

~~spi mode: 0x0~~{

~~max speed~~: ~~500000 Hz~~ printf(~~500 KHz~~"Hello World!\n");

~~Opening device /dev/spidev3.0~~

~~TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…|~~:return 0;

RX }| ~~FF FF FF FF FF FF~~ }</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then compile and run '''~~40 00 00 00 00 95~~hello_world.c''' ~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D~~ </li>{| class="wikitable" style="width:800px;" |-|~~......~~orangepi@orangepi:~$ '''gcc -o hello_world hello_world.~~......…|~~c'''

~~<~~orangepi@orangepi:~$ '''./~~span>=== 40pin I2C test ===~~hello_world'''

Hello World!|}</ol></li></ol><ol start="52" 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~~Debian BullSeye Default with Python3<ol style="list-style-type: lower-alpha;"><li>The specific version of Python is shown below</olli>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3'''

~~[[File~~'''Python 3.9.2''' (default, Feb 28 2021, 17:03:~~pi3b-img266.png|576x160px]]~~44)

~~'''It can be seen from the above table that I2C4_M0 and SPI3_M0 are pins~~[GCC 10. ~~The two cannot be opened at the same time~~2. ~~I2C3_M0 and UART3_M0 are also reused. The two cannot be opened at the same time'''~~1 20210110] on linux

~~'''In the Linux system~~Type "help", ~~the I2C in 40Pin is closed by default~~"copyright", ~~and it needs to be opened manually to use~~"credits" or "license" for more information.~~'''~~

>>>|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>'''~~Add the configuration of the red font part below to the/boot/orangepiEnv~~hello_world.~~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~~ py''' program in ~~one~~Python language</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;" |-| orangepi@orangepi:~$ '''~~sudo vim /boot/orangepiEnv~~python3 hello_world.~~txt~~py'''

~~'''overlays=i2c2-m1 i2c3-m0 i2c4-m0'''~~Hello World!|}</ol></li></ol><ol start="63" style="list-style-type: decimal;"><li>~~After starting the Linux system, first confirm the I2C device node under/dev.~~<~~/li~~p>Debian Bullseye's compilation tool and operating environment that is not installed in Java by default</olp> ~~orangepi@orangepi:~# '''ls /dev/i2c-*'''~~ ~~/dev/i2c-0 '''/dev/i2c-2''' '''/dev/i2c-3''' '''/dev/i2c-4''' /dev/i2c-6~~ <ol ~~start="7"~~ style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then connect a I2C device on~~ You can use the ~~I2C pin of the 40PIN connector~~following command to install OpenJDK. ~~Here~~ The latest version in Debian Bullseye is ~~an example of the DS1307 RTC module.~~openjdk-17</li~~></ol~~> {| class="wikitable" style="width:800px;"

|-

|orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''| }</ol><ol start="2" style="~~text~~list-~~align~~style-type: ~~left~~lower-alpha;"~~| i2c2-m1~~><li>After installation, you can check the version of Java</li>{| ~~style~~class="~~text-align: left;~~wikitable"~~| i2c3-m0~~| style="~~text-align~~width: ~~left~~800px;"~~| i2c4-m0~~

|-

| ~~Sda Pin~~orangepi@orangepi:~$ '''java --version'''| }</ol><ol start="3" style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"~~| Corresponding to No~~><li>Edit the '''hello_world. ~~3 pin~~java''' of the Jave version</li>{| ~~style~~class="~~text-align: left;~~wikitable"~~| Corresponding to No. 27 pin~~| style="~~text-align~~width: ~~left~~800px;"~~| Corresponding to No. 19 pin~~

|-

| ~~Sck Pin| style="text-align~~orangepi@orangepi: ~~left;"| Corresponding to No~~~$ '''vim hello_world. ~~5 pin| style="text-align: left;"| Corresponding to No. 28 pin| style="text-align: left;"| Corresponding to No. 23 pin~~|-~~| Vcc Pin| style="text-align: left;"| Corresponding to No. 1 pin| style="text-align: left;"| Corresponding to No. 1 pin| style="text-align: left;"| Corresponding to No. 1 pin~~|-~~| Gnd Pin| style="text-align: left;"| Corresponding to No. 6 pin| style="text-align: left;"| Corresponding to No. 6 pin| style="text-align: left;"| Corresponding to No. 6 pin~~|}java'''

~~[[File:pi3b-img273.png|180x153px]]~~public class hello_world

~~<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~~public static void main(String[] args)

~~orangepi@orangepi~~:~~~$ sudo i2cdetect -y 3 #i2c3 command~~{

~~orangepi@orangepi~~:~~~$ sudo i2cdetect -y 4 #i2c4 command~~:System.out.println("Hello World!");

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

~~[[File~~}|}</ol><ol start="4" style="list-style-type:~~pi3b~~lower-~~img274~~alpha;"><li>Then compile and run '''hello_world.~~png~~java'''</li>{|~~464x174px~~class="wikitable" style="width:800px;" |V-| orangepi@~~(61L~~orangepi:~~~0})Q`8VLBCAYEP[2]]~~$ '''javac hello_world.java'''

~~</div><ol start="9" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>You can then run the time of the ds~~ ~$ '''~~ds1307.py~~java hello_world''' ~~test program in '''examples''' to read the RTC time</li></ol>~~

~~root@orangepi:~~~Hello World!|}</~~wiringOP~~ol></li></ol>

~~root@orangepi:~/wiringOP-Python/examples# '''python3 ds1307.py --device \'''~~=== 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>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~"/dev/i2c~~gcc --~~4"~~version'''

~~Thu 2023~~gcc (Ubuntu 9.4.0-~~01-05 14:57:55~~1ubuntu1~20.04.1) 9.4.0

~~Thu 2023-01-05 14:57:57~~This is free software; see the source for copying conditions. There is NO

^warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>'''hello_world.c''' program to write Clanguage</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.c'''

~~exit~~#include <stdio.h>

~~~~

~~=== 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~~int main(void)

~~[[File:pi3b-img268.png|575x160px]]~~{

~~'''As can be seen from the above table, I2C3_M0 and UART3_M0 are reused by pins, and the two cannot be opened at the same time'''~~:printf("Hello World!\n");

~~'''In the Linux system, the UART in 40pin is closed by default, and it needs to be opened manually to use.'''~~

'''Add the configuration of the red font part below to the /boot/orangepiEnv.txt, and then restart the Linux system to open the UART3, UART7, and UART9 at the same time. If you only need to open one, you can fill in one''':return 0;

}|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then compile and run '''hello_world.c'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~sudo vim /boot/orangepiEnv~~gcc -o hello_world hello_world.~~txt~~c'''

orangepi@orangepi:~$ '''~~overlays=uart3-m0 uart7-m2 uart9-m2~~./hello_world'''

Hello World!

|}

</ol>

</li></ol>

<li>~~After entering the Linux system, first confirm whether there is a device node corresponding~~ Ubuntu Focal defaults to ~~UART under~~install Python3</~~dev~~p><ol style="list-style-type: lower-alpha;"></li>Python3 specific version is shown below</olli>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3'''

~~orangepi@orangepi~~Python 3.8.10 (default, Nov 14 2022, 12:~~~# '''ls /dev/ttyS*'''~~59:47)

~~/dev/ttyS1 '''/dev'''/'''ttyS3 /dev/ttyS7 /dev/ttyS9'''~~[GCC 9.4.0] on linux

~~<ol start="3" style="list-style-type: decimal~~Type "help", "copyright"">~~<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>~~"credits" or "license" for more information.

>>>|}</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><ol start="3" style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"~~| uart3~~><li>The results of running '''hello_world.py''' are shown below</li>{| ~~style~~class="~~text-align: left;~~wikitable"~~| uart7~~| style="~~text-align~~width: ~~left~~800px;"~~| uart9~~

|-

| ~~Tx Pin~~orangepi@orangepi:~$ '''python3 hello_world.py''' Hello World!| }</ol></li></ol><ol start="3" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"~~| Corresponding to~~ ><li>Ubuntu Focal's compilation tool and operating environment without the ~~28 pin~~installation of Java default| <ol style="~~text~~list-~~align~~style-type: ~~left~~lower-alpha;"~~| Corresponding~~ ><li>You can use the following command to ~~the 16 pin~~install '''openjdk-17'''</li>{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"~~| Corresponding to the 29 pin~~

|-

|}

</ol>

<li>After installation, you can check the version of Java</li>

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

|-

|

orangepi@orangepi:~$ '''java --version'''

~~<ol start="4" style="list-style-type: decimal;"><li>Use the '''serialTest~~openjdk 17.~~py''' program in Examples to test the loop function of the serial port~~0. ~~If you can see the printing below, it means that the serial communication is normal<ol style="list-style~~2 2022-~~type: lower~~01-~~alpha;"><li>Test UART3</li></ol></li></ol>~~18

~~root@orangepi:~/wiringOP-Python/examples# '''python3 serialTest~~OpenJDK Runtime Environment (build 17.0.py 2+8-Ubuntu-~~device \'''~~120.04)

OpenJDK 64-Bit Server VM (build 17.0.2+8-Ubuntu-120.04, mixed mode, sharing)|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Edit the '''hello_world.java'''~~"~~of Jave version</~~dev/ttyS3&quot~~li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''

~~Out: 0: -> 0~~public class hello_world

~~Out: 1: -> 1~~ ~~Out: 2: -> 2~~{

~~Out~~: ~~3: -> 3~~public static void main(String[] args)

~~Out~~: ~~4:^C~~{

~~exit~~::System.out.println("Hello World!");

~~<ol start="2" style="list-style-type~~: ~~lower-alpha;"><li>Test UART7</li></ol>~~}

~~root~~}|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then compile and run '''hello_world.java'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~~~/wiringOP-Python/examples#~~ $ '''~~python3 serialTest~~javac hello_world.~~py --device \~~java'''

orangepi@orangepi:~$ '''~~"/dev/ttyS7"~~java hello_world'''

~~Out: 0:~~ Hello World!|}</ol></li></ol> 0jammy-system">

~~Out: 1: -> 1~~=== Ubuntu jammy system ===

~~Out~~<ol style="list-style-type: 2decimal;"><li>Ubuntu Jammy is installed with the GCC compilation tool chain by default, which can directly compile the C language program in the Linux system of the development board<ol style="list-style-type: lower-~~&gt~~alpha; 2"><li>The version of the gcc is shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc --version'''

~~Out: 3:~~ gcc (Ubuntu 11.2.0-~~> 3~~19ubuntu1) '''11.2.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.|}</ol><ol start="32" style="list-style-type: lower-alpha;"><li>~~Test UART9~~Write the '''hello_world.c''' program of c language</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.c'''

~~root@orangepi:~/wiringOP-Python/examples~~# ~~'''python3 serialTest~~include <stdio.~~py --device \'''~~h>

~~'''"/dev/ttyS9"'''~~

~~Out: 0: -> 0~~int main(void)

~~Out: 1: -> 1~~{

~~Out~~: ~~2: -~~printf("Hello World!\n&gtquot;); 2

~~Out: 3: -> 3~~

~~Out~~: ~~4:^C~~return 0;

~~exit~~}|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then compile and run '''hello_world.c'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''

~~<~~orangepi@orangepi:~$ '''./~~span>== Hardware watch the door dog test ==~~hello_world'''

~~The WatchDog_test program is pre -installed in the Linux system released by Orange PI, which can be tested directly.~~Hello World!|}</ol>~~The method of running the WatchDog_test program is shown below:~~ </li></ol>

<li>Ubuntu jammy is installed with Python3 by default

<li>~~The second parameter 10 indicates the counting time of the door. If there~~ Python3 specific version is ~~no dog feeding in this time, the system will restart.~~shown below</li>~~<li>We can feed the dog by pressing any keys on the keyboard (except ESC). After the dog is fed, the program will print a line of Keep Alive to indicate that the dog is successful</li></ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3'''

~~orangepi@orangepi:~$~~ Python '''~~sudo watchdog_test~~ 3.10.4'''(main, Apr 2 2022, 09:04:19) [GCC 11.2.0] on linux

~~open success~~Type "help", "copyright", "credits" or "license" for more information.

~~options is 33152,identity is sunxi~~>>>|}</ol><ol start="2" style="list-~~wdt~~style-type: lower-alpha;"><li>Edit '''hello_world.py''' program in Python language</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.py'''

~~put_usr return,if 0,success~~print('Hello World!')|}</ol><ol start="3" style="list-style-type:0lower-alpha;"><li>The results of running '''hello_world.py''' are shown below</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3 hello_world.py'''

~~The old reset time is~~Hello World!|}</ol></li></ol><ol start="3" style="list-style-type: 16decimal;"><li>Ubuntu jammy defaults to compile tools and operating environments that are not installed in Java<ol style="list-style-type: lower-alpha;"><li>You can use the following command to install openjdk-18</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-18-jdk'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>After installation, you can check the version of Java</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''java --version'''

~~return ENOTTY,if~~ openjdk 18-~~1,success:0~~ea 2022-03-22

~~return ENOTTY,if~~ OpenJDK Runtime Environment (build 18-ea+36-Ubuntu-1~~,success:0~~)

~~put_user return~~OpenJDK 64-Bit Server VM (build 18-ea+36-Ubuntu-1,~~if 0~~mixed mode,~~success~~sharing)|}</ol><ol start="3" style="list-style-type:0lower-alpha;"><li>Edit the '''hello_world.java''' of the Jave version</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''

~~put_usr return,if 0,success:0~~public class hello_world

~~keep alive~~{

~~keep alive~~:public static void main(String[] args)

~~keep alive~~:{

~~== Check the serial number of the RK3566 chip ==~~::System.out.println("Hello World!");

~~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.~~:}

}|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then compile and run '''hello_world.java'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~cat_serial~~javac hello_world.shjava'''

~~Serial~~ orangepi@orangepi: ~$ '''~~8fa18eaf489041f0~~java hello_world'''

~~~~Hello World!~~== The method of downloading and installing the balenaEtcher version of arm64 ==~~|} ~~<ol style="list-style-type: decimal;"><li>The download address of Balenaetcher ARM64 version is: <ol style="list-style-type: lower-alpha;"><li>The download address of the Deb installation package is shown below, and it needs to be installed to use</li>~~</ol>

</li></ol>

~~https://github.com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balena-etcher-electron_1.7.9+5945ab1f_arm64.deb~~== QT installation method ==

~~<ol start="2" style="list-style-type: lower-alpha;"><li>The download address of~~ # Use the ~~Appimage version that does not need~~ following script to ~~be installed is shown below: </li></ol>~~install QT5 and QT Creator

~~https~~:~~//github.com/Itai~~:{| class="wikitable" style="width:800px;" |-~~Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balenaEtcher-1.7.9+5945ab1f-arm64~~| orangepi@orangepi:~$ '''install_qt.~~AppImage~~sh'''|}

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

~~[[File:pi3b-img275.png|527x211px|IMG_256]]~~

~~</div>~~

<li>~~How to install and use the deb~~ The QT version ~~of Balenaetcher:~~ number will be automatically printed after installation

<li>~~deb~~ Ubuntu20.04 comes with QT version ~~of Balenaetcher installation commands as shown below:~~ '''5.12.8'''</li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_qt.sh'''

~~orangepi@orangepi:~$ '''sudo apt install -y \'''~~......

~~'''--fix-broken~~ QMake version 3.~~/balena-etcher-electron_1.7.9+5945ab1f_arm64.deb'''~~1

Using Qt version '''5.12.8''' in /usr/lib/aarch64-linux-gnu

|}

</ol>

<li>~~After the deb~~ Ubuntu22.04 comes with QT version ~~of Balenaetcher is installed, it can be opened in the Application~~'''5.15.3'''</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_qt.sh'''

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

~~[[File:pi3b-img89~~QMake version 3.~~png|507x249px|IMG_256]]~~1

Using Qt version '''5.15.3''' in /usr/lib/aarch64-linux-gnu|}</~~div~~ol>

<li>~~The interface after Balenaetcher is opened is shown below:~~ Debian11 comes with QT version '''5.15.2'''</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_qt.sh'''

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

~~[[File:pi3b-img276~~QMake version 3.~~png|429x263px|IMG_256]]~~1

Using Qt version '''5.15.2</~~div~~span>''' in /usr/lib/aarch64-linux-gnu|}</ol><ol start="34" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~How to use the AppImage~~ Debian12 comes with QT version ~~of balenaEtcher:~~ '''5.15.8'''</pli>~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>First add permissions to Balenaetcher</li></ol>~~|-| ~~</li></ol>~~orangepi@orangepi:~$ '''install_qt.sh'''

~~orangepi@orangepi:~/Desktop$ '''chmod +x balenaEtcher-1~~.7.~~9+5945ab1f-arm64~~.~~AppImage'''~~...

~~<ol start="2" style="list-style-type: lower-alpha;"><li>Then select the AppImage~~ QMake version ~~balenaEtcher right -click the mouse, and then click Execute to open balenaEtcher</li></ol>~~3.1

~~[[File~~Using Qt version '''5.15.8''' in /usr/lib/aarch64-linux-~~img277.png~~gnu|~~145x118px]]~~}</ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>Then you can see the QT Creator launch icon in '''Applications'''</li>

~~== The installation method of the Bt-Panel Linux panel ==~~img327.png]]

QT Creator can also be opened using the following command{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''qtcreator'''Bt|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-~~Panel Linux panel is a server management software that improves operation~~ | <big>'''During the startup of QT and ~~maintenance efficiency. It supports more than 100 server management functions such as one -click LAMP/LNMP/cluster/monitoring/website/FTP/database/Java (excerpted from~~ QT applications, if the ~~[https://www.bt~~following error is displayed, ignore it.~~cn/new/index~~This error has no impact on application running.~~html official website of the Bt-Panel])~~'''

~~# First of all, the size of the'''/tmp''' space is needed. After setting, you need to '''restart the Linux system of the development board''', and the command is shown below:~~

~~orangepi@orangepi:~$~~ '''~~sudo sed -i 's/nosuid/&,size=2G/' /etc/fstab~~libGL error: failed to create dri screen'''

~~orangepi@orangepi:~$~~ '''~~sudo reboot~~libGL error: failed to load driver: rockchip'''

~~<ol start="2" style="list-style-type: decimal;"><li>After restarting, you can see that the size of the~~'''~~/tmp~~libGL error: failed to create dri screen''' ~~space has become 2G.</li></ol>~~

~~orangepi@orangepi~~'''libGL error:~$ failed to load driver: rockchip'''df </big>|}</ol><ol start="4" style="list-style-~~h | grep &quot~~type: decimal;"><li>The interface after QT Creator is opened is as follows</~~tmp"'''~~li>

~~tmpfs 2~~[[File:pi3b-img328.~~0G 12K~~ png]]</ol><ol start="5" style="list-style-type: decimal;"><li>The QT Creator version is shown below<ol style="list-style-type: lower-alpha;"><li>The default version of QT Creator in '''2Ubuntu20.0G04''' 1% is as follows</~~tmp~~li>

[[File:pi3b-img329.png]]</ol><ol start="32" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then enter the following command~~ The default version of QT Creator in ~~the Linux system to start the installation of the Bt-Panel~~'''Ubuntu22.04''' is as follows</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img330.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The default version of QT Creator in '''~~sudo install_bt_panel.sh~~Debian11'''is as follows</li>

[[File:pi3b-img331.png]]</ol><ol start="4" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then the pagoda installation program reminds whether to install the~~ The default version of QT Creator in '''~~Bt-Panel~~Debian12''' ~~to the'''/www''' folder, and enter y at this time~~is as follows</li~~></ol~~>

~~+---------------------------------------------------------------~~[[File:pi3b-img332.png]]</ol></li></ol><ol start="6" style="list-style-type: decimal;"><li>Then set QT<ol style="list-style-type: lower-alpha;"><li>First open '''Help'''->'''About Plugins...'''</li>

~~| Bt~~[[File:pi3b-~~WebPanel FOR CentOS~~img333.png]]</~~Ubuntu~~ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then remove the check box for '''ClangCodeModel'''</~~Debian~~li>

~~+----------------------------------------------------------------~~[[File:pi3b-img334.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>'''Restart QT Creator after the Settings are complete'''</li><li>Then make sure that QT Creator uses the GCC compiler, if the default is Clang, change it to GCC</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Debian12 Please skip this step.'''</big>|}

~~+-------------------------------------------------------------------~~[[File:pi3b-img336.png]]</ol></li></ol><ol start="7" style="list-style-type: decimal;"><li>You can then open a sample code</li>

~~| The WebPanel URL will be http~~[[File:pi3b-img337.png]]</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</~~SERVER_IP:8888 when installed.~~li>

~~+-------------------------------------------------------------------~~[[File:pi3b-img338.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then click '''Configure Project'''</li>

~~Do you want to install Bt~~[[File:pi3b-img339.png]]</ol><ol start="10" style="list-style-~~Panel~~ type: decimal;"><li>Then click the green triangle in the lower left corner to compile and run the sample code</~~www directory now?(y/n): '''y'''~~li>

[[File:pi3b-img340.png]]</ol><ol start="511" style="list-style-type: decimal;"><li>~~Then you have to wait patiently. When you see~~ After waiting for a period of time, the ~~printing information below~~ interface shown in the ~~terminal output~~following figure will pop up, ~~it means~~ which indicates that ~~the pagoda has been installed. The entire installation process takes about 34 minutes. There may be some differences according to the difference in network speed~~QT can compile and run normally</li~~></ol~~>

[[File:pi3b-~~img278~~img341.png~~|576x233px~~]]</ol><ol start="12" style="list-style-type: decimal;"><li>Reference documents</li>{| class="wikitable" style="width:800px;" |-| '''https://wiki.qt.io/Install_Qt_5_on_Ubuntu'''

~~<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~~https:~~pi3b-img279.png|575x281px]]<~~/~~p><~~/~~li><li>After successfully logging in to the pagoda, the following welcome interface will pop up~~download. 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<qt.io/~~p><~~archive/~~li></ol>~~qtcreator'''

~~[[File~~'''https:~~pi3b-img280~~//download.qt.~~png~~io/archive/qt'''|~~575x317px]]~~}</ol>

~~<ol start~~=~~"8" style~~=~~"list-style-type: decimal;">~~<li>After entering the Bt-Panel, you will first prompt that you need to bind the account of the Bt-Panel official website. If you do n’t have an account, you can go to the pagoda's official website ('''https://www.bt.cn''') to register one.</li></ol>ROS Installation Method ==

~~[[File:pi3b~~=== How to install ROS 1 Noetic on Ubuntu 20.~~png|576x300px]]~~04 ===

~~<ol start="9" style="list-style-type: decimal;"><li>~~# The ~~final display interface~~ current active version of ROS 1 is ~~shown in the figure below. You can intuitively see some status information of the development board Linux system, such~~ as ~~load state~~follows, ~~CPU usage, memory usage and storage space usage</li></ol>~~the recommended version is '''Noetic Ninjemys'''

::[[File:pi3b-~~img282~~img342.png|~~575x306px~~800px]]

~~<ol start="10" style="list-style-type~~: ~~decimal;"><li>More functions of the Bt~~:[[File:pi3b-~~Panel can refer to the following information to explore by yourself</li></ol>~~img343.png|800px]]

~~Manual~~: :{| class="wikitable" style="width:800px;" |-| [http://docs.btros.cn org/ '''http://docs.btros.cnorg''']

~~Forum address: [https://www.bt.cn/bbs~~ '''https://~~www~~wiki.btros.cnorg/~~bbs~~Distributions''']|}

~~GitHub Link~~<ol start="2" style="list-style-type: decimal;"><li>The official installation document link of ROS 1 '''~~https~~Noetic Ninjemys''' is as follows:</li>{| class="wikitable" style="width:800px;" |-| [http://~~github~~wiki.ros.~~com~~org/noetic/Installation/Ubuntu '''http://wiki.ros.org/noetic/Installation/Ubuntu''']|}</~~aaPanel~~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 system used by the development board is '''Ubuntu20.04 desktop system</~~BaoTa~~span>'''</li>{| class="wikitable" style="width:800px;" |-| http://wiki.ros.org/noetic/Installation|}

[[File:pi3b-img344.png]]<~~span id~~/ol><ol start="4" style="~~set~~list-style-type: decimal;"><li>Then use the~~-chinese-environment-and-~~script below to installros1</li>{| class="wikitable" style="width:800px;" |-~~chinese~~| orangepi@orangepi3b:~$ '''install_ros.sh ros1'''|}</ol><ol start="5" style="list-~~input~~style-~~method~~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</~~span~~li>{| class="wikitable" style= ~~Set~~ "background-color:#ffffdc;width:800px;" |-| <big>'''Note that running the following command needs to ensure that the ~~Chinese environment and install Chinese input method ==~~development board can access github normally, otherwise an error will be reported due to network problems.'''

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

~~=== Debian~~ 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 ~~installation method ===~~of the development board to access github normally, and then manually run the following Order.'''

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

~~orangepi@orangepi:~$~~ '''~~sudo dpkg~~https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-~~reconfigure locales~~homebrew.yaml'''

~~<ol start="2" style="list-style-type: lower-alpha;"><li>Then select~~ '''~~zh_CN~~Hit https://raw.githubusercontent.~~UTF-8 UTF-8~~com/ros/rosdistro/master/rosdep/base.yaml''' 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~~'''ERROR:~~pi3b-img283.png|575x296px]]~~error loading sources list:'''

:'''The read operation timed out'''<~~ol start~~/big>|}{| class="3wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Then set the default~~ |-| orangepi@orangepi:~$ '''~~locale''' as '''zh_CN~~source /opt/ros/noetic/setup.~~UTF-8~~bash'''~~</li></ol>~~

~~[[File~~orangepi@orangepi:~~pi3b-img284.png|575x160px]]~~~$ '''sudo rosdep init'''

~~<ol start="4" style="~~Wrote /etc/ros/rosdep/sources.list.d/20-~~style-type: lower-alpha;"><li>After exiting the interface, the '''locale''' settings will be started~~default. ~~The output displayed by the command line is shown below</li></ol>~~list

~~orangepi@orangepi~~Recommended:~~~$ '''sudo dpkg-reconfigure locales'''~~please run

~~Generating locales (this might take a while)...~~

~~en_US.UTF-8... done~~::rosdep update

~~zh_CN.UTF-8... done~~orangepi@orangepi:~$ '''rosdep update'''

~~Generation complete~~reading in sources list data from /etc/ros/rosdep/sources.list.d

~~<ol start="2" style="list-style-type~~Hit https: ~~decimal;"><li>Then open '''Input Method'''<~~/~~li><~~/~~ol>~~raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml

~~[[File~~Hit https:~~pi3b-img285~~//raw.~~png|575x361px]]~~githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml

~~<ol start="3" style="list-style-type~~Hit https: ~~decimal;"><li>Then select '''OK'''<~~/~~li><~~/~~ol>~~raw.githubusercontent.com/ros/rosdistro/master/rosdep/python.yaml

~~[[File~~Hit https:~~pi3b-img286~~//raw.~~png|295x212px]]~~githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml

~~<ol start="4" style="list-style-type~~Hit https: ~~decimal;"><li>Then select '''Yes'''<~~/~~li><~~/~~ol>~~raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml

~~[[File~~Query rosdistro index https:~~pi3b~~//raw.githubusercontent.com/ros/rosdistro/master/index-~~img287~~v4.~~png|303x192px]]~~yaml

~~<ol start="5" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "ardent"">~~<li>Then select '''fcitx'''</li></ol>~~

~~[[File:pi3b~~Skip end-~~img288.png|307x220px]]~~of-life distro "bouncy"

~~<ol start="6" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "crystal"">~~<li>Then select '''OK'''</li></ol>~~

~~[[File:pi3b~~Skip end-~~img289.png|305x216px]]~~of-life distro "dashing"

~~<ol start="7" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "eloquent"">~~<li>'''Then restart the Linux system to make the configuration effective'''</li><li>Then open '''Fcitx configuration'''</li></ol>~~

~~[[File:pi3b-img290.png|575x376px]]~~Add distro "foxy"

~~<ol start="9" style="list-style-type: decimal~~Add distro "galactic"">~~<li>Then click the + of the position shown in the figure below</li></ol>~~

~~[[File:pi3b~~Skip end-~~img291.png|280x187px]]~~of-life distro "groovy"

~~<ol start="10" style="list-style-type: decimal~~Add distro "humble"">~~<li>Then search '''Google Pinyin''' and click '''OK'''</li></ol>~~

~~<div class="figure">~~Skip end-of-life distro "hydro"

~~[[File:pi3b~~Skip end-~~img292.png|291x196px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~of-~~10.jpg未标题-10]]~~life distro "indigo"

~~</div><ol start="11" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "jade"">~~<li>Then put '''Google Pinyin''' to the front</li></ol>~~

~~[[File:pi3b~~Skip end-~~img293.png|299x202px]]~~of-life distro "kinetic"

~~[[File:pi3b~~Skip end-~~img294.png|300x202px]]~~of-life distro "lunar"

~~<ol start="12" style="list-style-type: decimal~~Add distro "melodic"">~~<li>Then open the '''Geany''' editor to test the Chinese input method</li></ol>~~

~~[[File:pi3b-img295.png|349x212px]]~~Add distro "noetic"

~~<ol start="13" style="list-style-type: decimal~~Add distro "rolling"">~~<li>The Chinese input method test is shown below</li></ol>~~

~~[[File~~updated cache in /home/orangepi/.ros/rosdep/sources.cache|}</ol><ol start="6" style="list-style-type: decimal;"><li>Then open a command line terminal window on the desktop, and then use the test_ros.sh script to start a small turtle routine to test whether ROS can be used normally</li>{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img296~~| orangepi@orangepi:~$ '''test_ros.~~png~~sh'''|~~575x325px]]~~}<li>After running the '''test_ros.sh''' script, a little turtle as shown in the figure below will pop up</li>

<~~ol start~~div class="14figure" ~~style="list-style-type: decimal;"><li>You can switch the Chinese and English input method through the '''Ctrl+Space''' shortcut</li><li>If the entire system is required as Chinese, the variables in '''/etc/default/locale''' can be set to '''zh_CN.UTF-8'''</li></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''sudo vim /etc/default/locale'''~~pi3b-img345.png]]

~~# File generated by update~~</div></ol><ol start="8" style="list-~~locale~~style-type: decimal;"><li>Then please keep the terminal window just opened at the top</li>

~~LC_MESSAGES~~<div class=~~'''zh_CN.UTF-8'''~~"figure">

~~LANG='''zh_CN~~[[File:pi3b-img346.~~UTF-8'''~~png]]

~~LANGUAGE~~</div></ol><ol start=~~'''zh_CN.UTF~~"9" style="list-style-~~8'''~~type: decimal;"><li>At this time, press the direction keys on the keyboard to control the little turtle to move up, down, left, and right</li>

[[File:pi3b-img347.png]]</ol ~~start~~>~~<li>Then '''restart the system''' to see the system displayed as Chinese</li~~></olspan>

~~[[File:pi3b-img297~~=== How to install ROS 2 Galactic on Ubuntu 20.~~png|576x356px]]~~04 ===

~~===~~ # The ~~installation method~~ current active version of ~~Ubuntu 20.04 system ===~~ROS 2 is as follows, the recommended version is '''Galactic Geochelone'''

~~# First open '''Language Support'''~~::[[File:pi3b-img348.png]]

::[[File:pi3b-~~img298~~img349.png]] ::{| class="wikitable" style="width:800px;" |-|~~575x351px]~~[http://docs.ros.org/ '''http://docs.ros.org'''] '''http://docs.ros.org/en/galactic/Releases.html'''|}

<li>~~Then find~~ The link to the official ROS 2 '''~~Chinese (China)~~Galactic Geochelone''' ~~option~~installation documentation is as follows:</li~~></ol~~>{| class="wikitable" style="width:800px;" ~~[[File:pi3b~~|-~~img299~~| '''docs.ros.~~png|318x311px]]~~org/en/galactic/Installation.html'''

'''http://docs.ros.org/en/galactic/Installation/Ubuntu-Install-Debians.html'''

|}

</ol>

<li>~~Then~~ It is recommended to use Ubuntu20.04 in the ~~left mouse button to select~~ official installation document of ROS 2 '''~~Chinese (China)~~Galactic Geochelone''' ~~and hold it down~~, ~~and then drag it up~~ so please ensure that the system used by the development board is '''Ubuntu20.04 desktop version'''. There are several ways to install ROS 2. The following shows how to install ROS 2 '''Galactic Geochelone''' using '''Debian packages'''</li><li>Use the ~~beginning~~'''install_ros. ~~The display is shown below~~sh''' script to install ros2</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi: ~$ '''install_ros.sh ros2'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>The '''install_ros.sh''' script will automatically run the '''ros2 -h''' command after installing ros2. If you can see the following print, it means that the ros2 installation is complete</olli>{| class="wikitable" style="width:800px;" |-| usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...

~~[[File:pi3b-img300.png|324x320px]]~~

~~'''Note that this step~~ ros2 is ~~not easy to drag, please try more patiently~~an extensible command-line tool for ROS 2.~~'''~~

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

~~<li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system</li></ol>~~

~~[[File~~optional arguments:~~pi3b-img301.png|321x316px]]~~

~~<ol start="5" style="list~~:-~~style~~h, -~~type: decimal;"><li>Then set the '''Keyboard input method system''' to '''fcitx'''</li></ol>~~-help show this help message and exit

~~[[File:pi3b-img302.png|327x320px]]~~

~~<ol start="6" style="list-style-type~~Commands: ~~decimal;"><li>'''hen 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~~action Various action related sub-~~img303.png|303x247px]]~~commands

~~<ol start="8" style="list~~:bag Various rosbag related sub-~~style-type: decimal;"><li>Then you can see that the desktop is displayed as Chinese</li></ol>~~commands

~~[[File~~:~~pi3b~~component Various component related sub-~~img304.png|575x383px]]~~commands

~~<ol start="9" style="list~~:daemon Various daemon related sub-~~style-type: decimal;"><li>Then we can open the '''Geany''' to test Chinese input method , and the way to open is shown in the figure below</li></ol>~~commands

~~[[File~~:~~pi3b-img305.png|576x292px]]~~doctor Check ROS setup and other potential issues

~~<ol start="10" style="list-style-type~~: ~~decimal;"><li>After opening '''Geany''', the default is an English input method. We can switch into Chinese input method through the '''Ctrl+Space''' shortcut keys, and then we can enter Chinese</li></ol>~~interface Show information about ROS interfaces

~~[[File~~:~~pi3b-img306.png|575x308px]]~~launch Run a launch file

~~=== The installation method of ubuntu 22.04 system ===~~commands

~~# First open '''Language Support'''~~:multicast Various multicast related sub-commands

~~[[File~~:~~pi3b~~node Various node related sub-~~img298.png|575x351px]]~~commands

~~<ol start="2" style="list~~:param Various param related sub-~~style-type: decimal;"><li>Then find '''Chinese (China)''' option</li></ol>~~commands

~~[[File~~:~~pi3b~~pkg Various package related sub-~~img307.png|335x326px]]~~commands

~~<ol start="3" style="list-style-type~~: ~~decimal;"><li>Then use the left mouse button to select '''Chinese (China)''' and hold it down, and then drag it up to the beginning. The display after dragging is shown in the figure below: </li></ol>~~run Run a package specific executable

~~[[File~~:~~pi3b~~security Various security related sub-~~img308.png|337x331px]]~~commands

~~'''Note that this step is not easy to drag, please try more patiently.'''~~:service Various service related sub-commands

~~<ol start="4" style="list-style-type~~: ~~decimal;"><li>Then select the '''Apply System~~topic Various topic related sub-~~Wide''' to apply the Chinese settings to the entire system</li></ol>~~commands

~~[[File~~:~~pi3b-img309.png|336x330px]]~~wtf Use `wtf` as alias to `doctor`

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

~~<li>'''Then restart the Linux system to make the configuration effective'''</li>~~

<li>After re -entering the system, please '''do not ask me again''' at the interface below, and then determine whether the standard folder should be updated as Chinese based on your preference</li></ol>

~~[[File~~:~~pi3b~~Call `ros2 <command> -~~img303~~h` for more detailed usage.~~png~~|~~303x247px]]~~}</ol><ol start="6" style="list-style-type: decimal;"><li>Then you can use the '''test_ros.sh''' script to test whether ROS 2 is installed successfully. If you can see the following print, it means that ROS 2 can run normally</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi3b:~$ '''test_ros.sh'''

~~<ol start="7" style="list-style-type~~[INFO] [1671174101.200091527] [talker]: ~~decimal;"><li>Then you can see that the desktop is displayed as Chinese</li></ol>~~Publishing: 'Hello World: 1'

[INFO] [~~File:pi3b-img304~~1671174101.~~png|575x383px~~235661048] [listener]: I heard: [Hello World: 1]

~~<ol start="8" style="list-style-type~~[INFO] [1671174102.199572327] [talker]: ~~decimal;"><li>Then open the Fcitx5 configuration program</li></ol>~~Publishing: 'Hello World: 2'

[INFO] [~~File:pi3b-img310~~1671174102.~~png|575x349px~~204196299] [listener]: I heard: [Hello World: 2]

~~<ol start="9" style="list-style-type~~[INFO] [1671174103.199580322] [talker]: ~~decimal;"><li>Then choose to use Pinyin input method</li></ol>~~Publishing: 'Hello World: 3'

[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]|}<~~div~~ /ol><ol start="7" style="list-style-type: decimal;"><li>Run the following command to open rviz2</li>{| class="~~figure~~wikitable" style="width:800px;">|-| orangepi@orangepi:~$ '''source /opt/ros/galactic/setup.bash'''

~~[[File~~orangepi@orangepi:~~pi3b-img311.png~~~$ '''ros2 run rviz2 rviz2'''|~~338x267px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-11.jpg未标题-11]]~~}

</div>~~<ol start~~class="10figure" ~~style="list-style-type: decimal;"><li>The interface after the selection is shown below, then click OK</li></ol~~>

[[File:pi3b-~~img312~~img350.png~~|366x290px~~]]

</div></ol><ol start="118" style="list-style-type: decimal;"><li>~~Then we can open~~ For the usage of ROS, please refer to the documentation of ROS 2</li>{| class="wikitable" style="width:800px;" |-| '''~~Geany~~http://docs.ros.org/en/galactic/Tutorials.html''' ~~to test Chinese input method, and the way to open is shown in the figure below~~|}</liol></olspan>

~~[[File:pi3b-img305~~=== How to install ROS 2 Humble on Ubuntu 22.~~png|576x292px]]~~04 ===

~~<ol start="12" style="list-style-type: decimal;"><li>After opening '''Geany~~# Use the '''~~, it is still an English input method by default~~install_ros. ~~We can switch into Chinese input methods through the '''Ctrl+Space~~sh''' ~~shortcut keys, and then we can enter Chinese</li></ol>~~script to install ros2

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-~~img313~~| orangepi@orangepi:~$ '''install_ros.~~png~~sh ros2'''|~~576x408px]]~~}

<~~span id~~ol start="~~how~~2" style="list-tostyle-~~remotely-log-in-to~~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~~-linux-system-desktop-method">~~ros2 installation is complete</~~span~~li>~~== How to remotely log in to the Linux system desktop method ==~~

~~'''Ubuntu Gnome Wayland image does not support Nomachine and VNCs introduced here to remotely log in to the desktop~~{| class="wikitable" style="width:800px;" |-| usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...~~'''~~

~~~~

~~=== Use nomachine remote login ===~~

~~'''Make sure the Ubuntu or Debian system installed on the development board~~ ros2 is ~~a desktop version~~an extensible command-line tool for ROS 2. ~~In addition, nomachine also provides detailed documents. It is strongly recommended to read this document to be familiar with the use of nomachine. The document links are shown below: '''~~

~~'''https://knowledgebase.nomachine.com/DT10R00166'''~~

'''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.'''optional arguments:

~~'''Before operation~~:-h, ~~please ensure that the Windwos computer~~ --help show this help message 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.'''~~exit

~~<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-type: lower-alpha;">~~

<li>Since RK3566 is a SOC of the ARMV8 architecture, the system we use is Ubuntu or Debian, so you need to download '''NoMachine for ARM ARMv8 DEB''' installation package here. The download link is shown below: </li></ol>

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

~~'''Note that this download link may change, please recognize the DEB package of the ARMV8/ARM64 version.'''~~Commands:

~~[https~~:~~//www.nomachine.com/download/download&id=112&s=ARM '''https://downloads.nomachine.com/download/?id=118&distro=ARM''']~~action Various action related sub-commands

~~[[File~~:~~pi3b~~bag Various rosbag related sub-~~img314.png|575x227px]]~~commands

~~<ol start="2" style="list-style-type~~: ~~lower~~component Various component related sub-~~alpha;"><li>In addition, you can also download the installation package to '''NoMachine''' in the '''official tools'''.</li></ol>~~commands

~~[[File~~:~~pi3b~~daemon Various daemon related sub-~~img315.png|66x102px]]~~commands

~~<blockquote>First enter the '''remote login software-Nomachine''' folder</blockquote>[[File~~:~~pi3b-img316.png|271x43px]]~~doctor Check ROS setup and other potential issues

~~<blockquote>Then download the ARM64 version of the DEB installation package</blockquote>[[File~~:~~pi3b-img317.png|180x109px]]~~interface Show information about ROS interfaces

~~<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>~~launch Run a launch file

~~orangepi@orangepi~~:~~~$ '''sudo dpkg~~ lifecycle Various lifecycle related sub-~~i nomachine_x.x.x_x_arm64_arm64.deb'''~~commands

~~<ol start="2" style="list~~:multicast Various multicast 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.'''~~:node Various node related sub-commands

~~'''https~~:~~//downloads.nomachine.com/download/?id=9'''~~param Various param related sub-commands

~~[[File~~:~~pi3b~~pkg Various package 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>~~run Run a package specific executable

~~[[File~~:~~pi3b~~security Various security related sub-~~img319.png|76x66px]]~~commands

~~<ol start="5" style="list~~:service Various service related sub-~~style-type: decimal;">~~<li>After Nomachine starts, it will automatically scan other devices installed in the local area network. After entering the main interface of Nomachine, you can see that the development board is already in the connected device list, and then click the location shown in the red box below in the figure below. Start log in to the Linux system desktop of the development board</li></ol>commands

~~[[File~~:~~pi3b~~topic Various topic related sub-~~img320.png|321x92px]]~~commands

~~<ol start="6" style="list-style-type~~: ~~decimal;"><li>Then click '''OK'''</li></ol>~~wtf Use `wtf` as alias to `doctor`

~~[[File:pi3b-img321.png|402x275px]]~~

:Call `ros2 <command> -h` for more detailed usage.|}</ol><ol start="73" style="list-style-type: decimal;"><li>Then ~~enter the username and password of the Linux system in the corresponding position in~~ you can use the ~~figure below, and then click~~ '''OKtest_ros.sh''' script to ~~start logging in~~test whether ROS 2 is installed successfully. If you can see the following print, it means that ROS 2 can run normally</li~~></ol~~>

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

[INFO] [~~File:pi3b-img322.png|303x204px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-12~~1671174101.~~jpg未标题-12~~200091527][talker]: Publishing: 'Hello World: 1'

~~</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~~[INFO] [~~File:pi3b-img323~~1671174101.~~png|411x246px~~235661048][listener]: I heard: [Hello World: 1]~~</li></ol>~~

~~=== Use VNC remote login ===~~[INFO] [1671174102.199572327] [talker]: Publishing: 'Hello World: 2'

'''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[INFO] [1671174102.~~'''~~204196299] [listener]: I heard: [Hello World: 2]

~~'''Ubuntu 20~~[INFO] [1671174103.~~04 tests many problems with VNC, please do not use this method.'~~199580322] [talker]: Publishing: 'Hello World: 3'

~~# First run~~ [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:~$ '''~~set_vnc~~source /opt/ros/humble/setup.~~sh''' script settings, and '''remember to add Sudo permissions~~bash'''

orangepi@orangepi:~$ '''~~sudo set_vnc.sh~~ros2 run rviz2 rviz2'''|}

~~You will require a password to access your desktops.~~<div class="figure">

~~Password~~[[File: ~~'''#Set the VNC password here, 8~~ pi3b-~~bit characters'''~~img351.png]]

~~Verify~~</div></ol><ol start="5" style="list-style-type: decimal;"><li>Reference documents</li>{| class="wikitable" style="width: 800px;" |-| '''~~#Set the VNC password here, 8 -bit characters~~http://docs.ros.org/en/humble/index.html'''

~~Would you like to enter a view-only password (y~~[http://docs.ros.org/en/galactic/~~n)?~~ Tutorials.html '''nhttp://docs.ros.org/en/humble/Installation/Ubuntu-Install-Debians.html''']|}</ol>

~~xauth: file /root/.Xauthority does not exist~~== How to install kernel header files ==

~~New~~ # The Linux image released by OPi comes with the deb package of the kernel header file by default, and the storage location is '''/opt/''X' ~~desktop is orangepi3b:1~~

~~Creating default startup script~~ ::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ls /~~root~~opt/~~.vnc/xstartup~~linux-headers*'''

~~Starting applications specified in~~ /~~root~~opt/linux-headers-legacy-rockchip-rk356x_x.~~vnc/xstartup~~x.x_arm64.deb|}

~~Log~~ <ol start="2" style="list-style-type: decimal;"><li>Use the following command to install the deb package of the kernel header file ~~is /root~~</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.~~vnc~~'''</~~orangepi3b~~big>|}{| class="wikitable" style="width:1800px;" |-| orangepi@orangepi:~$ '''sudo dpkg -i /opt/linux-headers-legacy-rockchip-rk356x_1.x.x_arm64.~~log~~deb'''|}~~Killing Xtightvnc process ID 3047~~</ol><ol start="3" style="list-style-type: decimal;">~~New~~ <li>After installation, you can see the folder where the kernel header files are located under '''X/usr/src' ~~desktop is orangepi3b~~''</li>{| class="wikitable" style="width:1800px;" |-| orangepi@orangepi:~$ '''ls /usr/src'''

~~Starting applications specified in~~ 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</~~root~~p><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.~~vnc/xstartup~~c'''

~~Log file is /root~~#include <linux/init.~~vnc~~h></~~orangepi3b:1.log~~p>

~~<ol start="2" style="list-style-type: decimal;"><li>~~~~The steps of using MobaxTerm software to connect the development board Linux system desktop are shown below: <~~#include <linux/p>~~<ol style="list-style-type: lower-alpha~~module.h>">~~<li>First click Session, then select VNC, then fill in the IP address and port of the development board, and finally click OK to confirm~~</~~li></ol></li></ol~~p>

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

~~[[File:pi3b-img324.png|490x349px|图片1208]]~~static int hello_init(void)

~~</div><ol start="2" style="list-style-type: lower-alpha;"><li>Then enter the password of the previously set VNC</li></ol>~~{

~~[[File~~:~~pi3b~~printk("Hello Orange Pi -~~img325.png|274x131px]]~~- init\n");

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

~~<li>The interface after the login is shown as shown in the figure below, and then the desktop of the Linux system can be remotely operated~~

~~[[File:pi3b-img326.png|405x293px]]</li></ol>~~

~~== Some programming language tests supported by Linux system ==~~:return 0;

~~=== Debian Bullseye system ===~~}

~~<ol style="list-style-type: decimal;"><li>Debian Bullseye is equipped with a gcc compilation tool chain by default, which can directly compile the C language program in the Linux system of 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(~~Debian 10.2.1~~"Hello Orange Pi -6- exit\n") ~~10.2.1 20210110~~;

~~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>Write C language of '''Hello_world.c''' program</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>Debian BullSeye Default with Python3<ol style="list-style-type: lower-alpha;"><li>The specific version of Python is shown below</li></ol></li></ol>~~

~~orangepi@orangepi~~:~~~$ '''python3'''~~rm -f *.ko *.o *.mod.o *.mod *.symvers *.cmd *.mod.c *.order

endif|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then use the make command to compile the hello kernel module. The output of the compilation process is as follows:</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~Python 3~~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.~~9.2~~''' ~~(default, Feb 28 2021, 17:03:44)~~</big>

[~~GCC 10~~[File:pi3b-img352.~~2.1 20210110~~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>Debian Bullseye's compilation tool and operating environment that is not installed in Java by default~~|-| ~~<ol style="list-style-type~~orangepi@orangepi: ~~lower-alpha~~~$ '''dmesg | grep "Hello"">~~<li>You can use the following command to install OpenJDK. The latest version in Debian Bullseye is openjdk-17</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

~~<ol start="3" style="list-style-type: lower-alpha;"><li>Edit the~~ [ 3173.800892] '''~~hello_world.java~~Hello Orange Pi -- exit''' ~~of the Jave version~~|}</ol></li></ol>

~~orangepi@orangepi:~$ '''vim hello_world.java''~~== Use of the Raspberry PI's 5-inch screen ==

~~public class hello_world~~=== Assembly method of Raspberry PI 5-inch screen ===

{<ol style="list-style-type: decimal;"><li>First prepare the required accessories<ol style="list-style-type: lower-alpha;"><li>Raspberry PI 5-inch MIPI LCD display + touch screen</li>

~~public static void main(String~~[[File:pi3b-img353.png]] ~~args)~~</ol><ol start="2" style="list-style-type: lower-alpha;"><li>15pin MIPI cable</li>

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

~~System~~[[File:pi3b-img355.~~out.println("Hello World!")~~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>

}[[File:pi3b-img356.png]]</ol>

}=== Open the Raspberry PI 5-inch screen configuration method ===

<ol ~~start~~style="4list-style-type: decimal;" ><li>The Linux image does not open the 5-inch screen of the Raspberry PI by default. If you need to use the 5-inch screen of the Raspberry PI, you need to open it manually.</li><li>The steps to open the mipi lcd configuration are as follows:<ol style="list-style-type: lower-alpha;"><li>~~Then compile and~~ First run '''~~hello_world.java~~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>

~~orangepi@orangepi~~[[File:~$ pi3b-img357.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then select '''~~javac hello_world.java~~Hardware'''</li>

~~orangepi@orangepi~~[[File:~~~$ '''java hello_world'''~~pi3b-img358.png]]</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then use the arrow keys on the keyboard to locate the Rasp-7inch-touchscreen, and then use the space button to check</li>

~~Hello World!~~[[File:pi3b-img359.png]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then select '''<Save>''' to save</li>

[[File:pi3b-img360.png]]</ol><~~span id~~ol start="~~ubuntu~~6" style="list-style-~~focal~~type: lower-~~system~~alpha;"><li>Then select '''<Back>'''</~~span~~li>~~=== Ubuntu Focal system ===~~

~~<ol style="list~~[[File:pi3b-~~style-type: decimal;">~~img361.png]]~~<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.~~</pol><ol start="7" style="list-style-type: lower-alpha;"><li>~~The version of~~ Then select '''<Reboot>''' to restart the system for the ~~gcc is shown below~~configuration to take effect</li~~></ol></li></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''gcc~~ pi3b-~~-version'''~~img362.png]]

~~gcc (Ubuntu 9.4.0~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The above settings will eventually add the configuration of overlays=raspi-7inch-~~1ubuntu1~20~~touchscreen to /boot/orangepiEnv.04txt.~~1) 9~~After setting, you can check it first.4If this configuration does not exist, then there is a problem with the settings.0'''

~~Copyright (C) 2019 Free Software Foundation~~'''If you find it troublesome to use orangepi-config, ~~Inc~~you can also use the vim editor to open /boot/orangepiEnv.txt, and then add the configuration of overlays=raspi-7inch-touchscreen is also possible.'''</big>

~~This is free software; see the source for copying conditions. There is NO~~

~~warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE~~orangepi@orangepi:~$ '''cat /boot/orangepiEnv.txt | grep "raspi"'''

'''overlays=raspi-7inch-touchscreen #Sample configuration'''|}</ol></li></ol><ol start="23" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~'''hello_world.c''' program to write C language~~After startup, you can see the lcd screen display as follows:</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''vim hello_world~~pi3b-img363.~~c'''~~png]]</ol>

~~#include <stdio.h>~~=== The method of server version image rotation display direction ===

~~int main(void)~~<ol start="1" style="list-style-type: decimal;"><li>Add '''extraargs=fbcon=rotate:the direction to rotate''' in '''/boot/orangepiEnv.txt''' This line configuration can set the direction displayed by the server version of the Linux system, where the number after '''fbcon=rotate:''' can be set as:</li>

<ol style="list-style-type: lower-alpha;"><li>0: normal screen (default is landscape)</li><li>1: Turn clockwise 90 degrees</li><li>2: Flip 180 degrees</li><li>3: Turn clockwise 270 degrees</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''

~~printf("Hello World!\n");~~overlays=lcd1

~~return 0~~'''extraargs=cma=64M fbcon=rotate:3'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that if there is the line extraargs=cma=64M in /boot/orangepiEnv.txt by default, the configuration fbcon=rotate:3 can be added after extraargs=cma=64M (separated by spaces).'''</big>|}</ol></li></ol><ol start="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>

<~~ol start~~span id="~~3" style="list~~method-of-rotating-display-and-touch-direction-of-~~style~~desktop-~~type: lower~~version-~~alpha;~~image">~~<li>Then compile and run '''hello_world.c'''</li~~></olspan>

~~orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''~~=== Method of rotating display and touch direction of desktop version image ===

~~orangepi@orangepi:~$~~ # First open '''~~./hello_world~~Display'''Settings in Linux

~~Hello World!~~::[[File:pi3b-img364.png]]

<li>~~Ubuntu Focal defaults~~ Then select the direction you want to ~~install Python3~~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:~$ pi3b-img366.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select '''~~python3~~Keep this configuration'''</li>

~~Python 3~~[[File:pi3b-img367.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>At this point, the screen display has been rotated, and then close the '''Display''' program</li><li>The above steps will only select the display direction, and will not rotate the direction of the touch. Use the '''set_lcd_rotate.8sh''' script to rotate the direction of the touch.~~10 (default~~After the script is set, ~~Nov 14 2022~~it will automatically restart, 12and then you can test whether the touch has been used normally.<ol style="list-style-type:59lower-alpha;"><li>'''None''': no rotation</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''set_lcd_rotate.sh none'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>'''Left''': rotate left 90 degrees</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''set_lcd_rotate.sh left'''|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>'''Inverted''': Flip up and down, which is equivalent to rotating 180 degrees</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''set_lcd_rotate.sh inverted'''|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>'''Right''': rotate right 90 degrees</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''set_lcd_rotate.sh right'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The set_lcd_rotate.sh script mainly does four things:~~47)~~'''

~~[GCC 9.4.0] on linux~~

~~Type "help", "copyright", "credits" or "license" for more information~~'''1.Rotate the direction displayed by the framebuffer'''

~~>>>~~'''2. Rotate the direction of the touch'''

~~<ol start="2" style="list-style-type: lower-alpha;"><li>~~'''~~hello_world~~3.pyTurn off the boot logo''' ~~program in Python language</li></ol>~~

~~orangepi@orangepi:~$~~ '''~~vim hello_world~~4.pyRestart the system'''

~~print('Hello World!')~~

~~<ol start="3" style="list-style-type: lower-alpha;"><li>The results of running~~ '''~~hello_world.py''' are shown below<~~Rotating the touch direction is achieved by adding the line Option "TransformationMatrix" "x x x x x x x x x" to /usr/share/~~li><~~X11/~~ol>~~ ~~orangepi@orangepi:~$ '''python3 hello_world~~xorg.conf.~~py'''~~ ~~Hello World!~~ ~~<ol start="3" style="list~~d/40-~~style-type: decimal~~libinput.conf Where "">~~<li>Ubuntu Focal's compilation tool and operating environment without the installation of Java default<ol style="list-style-type: lower-alpha~~x x x x x x x x x"">~~<li>You can use the following command to install '''openjdk-17~~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-17-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 17.0.2 2022-01-18~~verbosity=1

~~OpenJDK Runtime Environment (build 17.0.2+8-Ubuntu-120.04)~~'''bootlogo=false'''|}

~~OpenJDK 64~~<ol start="3" style="list-~~Bit Server VM (build 17.0.2+8-Ubuntu~~style-~~120~~type: decimal;"><li>Set the '''bootlogo''' variable to '''true''' in '''/boot/orangepiEnv.~~04, mixed mode, sharing)~~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 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>~~public static void main(String[] args)~~

{== How to use the ZFS file system ==

~~System~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The latest version of Ubuntu20.04, Ubuntu22.~~out~~04, Debian11 and Debian12 desktop version systems have pre-installed zfs, you can use it directly.~~println("Hello World!");~~'''

}'''The pre-installed zfs version in Ubuntu20.04 and Ubuntu22.04 desktop systems is 2.1.6.'''

}'''The pre-installed zfs version in Debian11 and Debian12 desktop systems is 2.1.11.'''

~~<ol start="4" style="list-style-type: lower-alpha;"><li>Then compile and run~~ '''~~hello_world~~After the system starts, please first confirm whether the zfs kernel module has been loaded. If you can see zfs-related content using the lsmod command, it means that the system has pre-installed zfs.~~java~~'''</~~li></ol~~big>

orangepi@orangepi:~$ '''~~javac hello_world.java~~lsmod | grep "zfs"'''

~~orangepi@orangepi:~$ '''java hello_world'''~~zfs                     2801664     0

~~Hello World!~~zunicode             327680     1   zfs

~~=== Ubuntu jammy system ===~~zzstd                  471040     1   zfs

~~<ol style="list-style-type: decimal~~zlua  ">~~<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></ol></li></ol>~~                 139264     1   zfs

~~orangepi@orangepi:~$ '''gcc --version'''~~zcommon             69632     1   zfs

~~gcc (Ubuntu 11.~~znvpair                 61440     2~~.0-19ubuntu1) '''11.2.0'''~~  zfs,zcommon

~~This is free software~~icp   ~~see the source for copying conditions. There is NO~~                   221184     1   zfs

~~warranty~~spl   ~~not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.~~                     77824     6   zfs,icp,zzstd,znvpair,zcommon,zavl|}

<~~ol start~~span id="~~2" style="list~~how-~~style~~to-~~type: lower~~install-~~alpha;~~zfs">~~<li>Write the '''hello_world.c''' program of c language~~</~~li></ol~~span>=== How to install ZFS ===

~~orangepi@orangepi~~{| class="wikitable" style="background-color:~$ #ffffdc;width:800px;" |-| <big>'''~~vim hello_world~~Before installing zfs, please make sure that the Linux image used is the latest version. In addition, if zfs is already installed in the system, it needs to be installed again.c'''</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#~~include <stdio~~How to install kernel header files|'''section on the method of installing the kernel header file''']].~~h>~~

~~int main(void)~~In Ubuntu20.04, Ubuntu22.04 and Debian11 systems, zfs cannot be installed directly through apt, because the default apt source zfs version is lower than 2.1.6, and there is a problem of incompatibility with rk Linux5.10 kernel. This problem is fixed in zfs version 2.1.6 and later.

{To solve this problem, we provide a zfs deb package that can be installed normally, which can be downloaded from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''official tool'''] of the development board. Open the '''official tool''', and enter the '''zfs-related deb package folders used by Ubuntu and Debian systems'''. You can see three types of deb packages: Ubuntu20.04, Ubuntu22.04 and Debian11. Please download the required version.

~~printf("Hello World!\n");~~[[File:pi3b-img368.png]]

~~return 0;~~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]].'''

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

~~<ol start~~{| class="3wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Then compile and run~~ |-| orangepi@orangepi:~$ '''~~hello_world~~sudo apt install ./*.cdeb'''~~</li></ol>~~|}

~~orangepi@orangepi~~After the installation is complete, use the following command to see the zfs-related kernel modules:~~~$ '''gcc -o hello_world hello_world.c'''~~

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ls /lib/modules/5.10.160-rockchip-rk356x/updates/dkms/~~hello_world~~'''

~~Hello World!~~'''icp.ko spl.ko zavl.ko zcommon.ko zfs.ko zlua.ko znvpair.ko zunicode.ko zzstd.ko'''|}

~~<ol start="2" style="list-style-type~~Then restart the Linux system to see that the zfs kernel module will be automatically loaded: ~~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></ol></li></ol>~~

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~python3~~lsmod | grep "zfs"'''

~~Python '''3.10.4''' (main, Apr 2 2022, 09:04:19) [GCC 11.2.~~zfs                     2801664     0~~] on linux~~

~~Type~~ zunicode &~~quot~~nbsp;~~help~~&~~quot~~nbsp;, &~~quot~~nbsp;~~copyright~~&~~quot~~nbsp;, &~~quot~~nbsp;~~credits~~&~~quot~~nbsp; or &~~quot~~nbsp;~~license~~&~~quot~~nbsp; ~~for more information.~~    327680     1   zfs

zzstd &gtnbsp;&gtnbsp;&gtnbsp;              471040     1   zfs

~~<ol start="2" style="list-style-type: lower-alpha~~zlua  ">~~<li>Edit '''hello_world.py''' program in Python language</li></ol>~~                  139264     1   zfs

~~orangepi@orangepi:~$ '''vim hello_world.py'''~~zcommon             69632     1   zfs

~~print('Hello World!')~~znvpair                 61440     2   zfs,zcommon

~~<ol start="3" style="list-style-type: lower-alpha~~zavl  ">~~<li>The results of running '''hello_world.py''' are shown below</li></ol>~~                    16384     1   zfs

~~orangepi@orangepi:~$ '''python3 hello_world.py'''~~icp                     221184     1   zfs

~~Hello World!~~spl                       77824     6   zfs,icp,zzstd,znvpair,zcommon,zavl|}

~~<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~~ In Debian12, the default version of zfs is 2.1.11, so we can ~~use~~ install zfs directly through the following command ~~to install openjdk-18</li></ol></li></ol>~~. Again, please make sure that the system has installed the deb package of the kernel header file before installation.

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y ~~openjdk~~zfsutils-18linux zfs-~~jdk~~dkms'''|}

<~~ol start~~span id="~~2" style="list~~methods-of-~~style~~creating-~~type: lower~~zfs-~~alpha;~~pools">~~<li>After installation, you can check the version of Java</li~~></olspan>

~~orangepi@orangepi:~$ '''java --version'''~~=== Methods of creating ZFS pools ===

~~openjdk 18~~{| class="wikitable" style="background-~~ea 2022~~color:#ffffdc;width:800px;" |-~~03-22~~| <big>'''ZFS is based on storage pools, we can add multiple physical storage devices to the pool, and then allocate storage space from this pool.'''

~~OpenJDK Runtime Environment (build 18-ea+36-Ubuntu-1)~~'''The following content is demonstrated based on the development board connected to an NVMe SSD and a USB flash drive.'''</big>|}

~~OpenJDK 64-Bit Server VM (build 18-ea+36-Ubuntu-1~~# First, ~~mixed mode, sharing)~~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:

~~<ol start="3" style="list-style-type~~: ~~lower~~:[[File:pi3b-~~alpha;"><li>Edit the '''hello_world~~img369.~~java''' of the Jave version</li></ol>~~png]]

<ol start="2" style="list-style-type: decimal;"><li>Then enter the following command to create a ZFS pool, including two storage devices, NVMe SSD and U disk</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~vim hello_world.java~~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>

~~public~~ [[File:pi3b-img370.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then execute '''df -h''' to see that '''pool1''' is mounted to the '''/pool1''' directory</li>{| class ~~hello_world~~="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''df -h''' Filesystem                 Size     Used Avail Use% Mounted on

{tmpfs                    1.6G     18M 1.6G 2% /run

~~public static void main(String[] args)~~/dev/mmcblk0p2     29G     6.0G 22G 22% /

{tmpfs                    7.7G     46M 7.7G 1% /dev/shm

~~System~~tmpfs                    5.~~out.println(~~0M &~~quot~~nbsp;~~Hello World!~~&~~quot~~nbsp;) 4.0K 5.0M 1% /run/lock

}tmpfs                    7.7G     944K 7.7G 1% /tmp

}/dev/mmcblk0p1     1022M     115M 908M 12% /boot

~~<ol start="~~/dev/zram1                 188M     4~~" style="list-style-type: lower-alpha;"><li>Then compile and run '''hello_world~~.~~java'''<~~5M 169M 3% /var/~~li>~~log <~~/ol~~br>

~~orangepi@orangepi:~$ '''javac hello_world~~tmpfs                    1.~~java'''~~6G     80K 1.6G 1% /run/user/1000

'''pool1                    489G     9.3M 489G 1% /pool1''' |}</ol><ol start="5" style="list-style-type: decimal;"><li>Use the following command to see that the file system type of pool1 is zfs</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~java hello_world~~mount | grep pool1'''

~~Hello World!~~pool1 on /pool1 type '''zfs''' (rw,xattr,noacl)|}</ol><ol start="6" style="list-style-type: decimal;"><li>Then we can test copying a file to the ZFS pool</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo cp -v /usr/local/test.mp4 /pool1/'''

'/usr/local/test.mp4' -> '/pool1/test.mp4'|}</ol>~~== QT installation method ==~~

~~# Use~~ === Test the ~~following script to install QT5 and QT Creator~~data deduplication function of ZFS ===

# The data deduplication function of ZFS is disabled by default, we need to execute the following command to enable it::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~install_qt.sh~~sudo zfs set dedup=on pool1'''|}

<li>~~The QT version number will be automatically printed after installation~~Then do a simple test, first enter pool1, and then execute the following command to generate a random file with a size of 1G</pli>~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Ubuntu20.04 comes with QT version~~ |-| orangepi@orangepi:~$ '''~~5.12.8~~cd /pool1/'''~~</li></ol></li></ol>~~

~~orangepi~~root@orangepi:~/pool1$ '''~~install_qt~~sudo dd if=/dev/urandom of=test.sh1g bs=1M count=1024'''

~~......~~1024+0 records in

~~QMake version 3.1~~1024+0 records out

~~Using Qt version~~ 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 5.04367 s, 213 MB/s|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then use the following command to copy 1000 random files of size 1G</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/pool1$ '''5for ((i=0; i<1000; i++)); do sudo cp test.1g $i.12test.81g; 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</~~usr~~li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/~~lib/aarch64~~pool1$ '''du -~~linux-gnu~~lh'''

1002G|}</ol><ol start="25" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Ubuntu22.04 comes with QT version~~ Then use the '''~~5.15.3~~zpool list'''command to see that only 1.01G is actually occupied, because these 1001 files are all duplicates, indicating that the data deduplication function is effective.</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''install_qt~~pi3b-img371.~~sh'''~~png]]</ol>

~~......~~=== Test the data compression function of ZFS ===

~~QMake version 3.1~~# Because the stored data is different, the disk space saved by compression will also be different, so we choose to compress relatively large plain text files for compression testing, and execute the following commands to pack the '''/var/log/''' and '''/etc/''' directories into a tarball

~~Using Qt version~~ ::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~5.15.3~~cd /pool1/''' ~~in /usr/lib/aarch64-linux-gnu~~

~~<ol start="3" style="list-style-type~~root@orangepi: ~~lower-alpha;"><li>Debian11 comes with QT version~~ /pool1$ '''5sudo tar -cf text.~~15.2~~tar /var/log/ /etc/'''~~</li></ol>~~|}

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~$ decimal;"><li>Then the file size that can be seen through the '''~~install_qt.sh~~ls -lh'''command and the space occupied in the ZFS pool are both '''27M'''</li>

[[File:pi3b-img372.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then we enable compression in the ZFS pool pool1</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/pool1$ '''sudo zfs set compression=lz4 pool1'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then execute the following command again to package the '''/var/log/''' and '''/etc/''' directories into a tar package</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/pool1$ '''sudo tar -cf text.tar /var/log/ /etc/'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>At this time, you can see that the size of the '''text.tar''' file is still 27M, but it only occupies 9...47M in the ZFS pool, indicating that the file is compressed</li>

~~QMake version 3~~[[File:pi3b-img373.1png]]</ol>

~~Using Qt version '''5.15.2''' in /usr/lib/aarch64-linux-gnu~~== How to shut down and restart the development board ==

~~<ol start="4" style="list~~# During the running of the Linux system, if the Type-~~style-type: lower-alpha;"><li>Debian12 comes with QT version~~ C power supply is directly unplugged, some data may be lost or damaged in the file system, so please use the '''~~5.15.8~~poweroff'''~~</li></ol>~~command to shut down the Linux system of the development board before powering off. Then unplug the power again.

::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~install_qt.sh~~sudo poweroff''' ~~......~~|}

~~QMake version 3~~<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.1</li>

~~Using Qt version '''5.15~~[[File:pi3b-img374.~~8''' in /usr/lib/aarch64-linux-gnu~~png]]

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

|-

|

<big>'''Note that the Linux desktop version system will pop up a confirmation box as shown in the figure below after pressing the switch button, and the system will shut down only after clicking the Shut Down option.'''</big>

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

|}

</ol>

<li>~~Then you can see~~ Short press the ~~QT Creator launch icon in '''Applications'''~~switch button on the development board after shutting down to start up.</li~~></ol~~>

[[File:pi3b-~~img327~~img374.png~~|576x270px~~]]</ol><ol start="4" style="list-style-type: decimal;"><li>The command to restart the Linux system is</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo''' '''reboot'''|}</ol>

~~QT Creator can also be opened using the following command~~= '''Linux SDK——orangepi-build instructions''' =

~~orangepi@orangepi:~$ '''qtcreator'''~~== Compilation system requirements ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~During~~ We can cross-compile the ~~startup~~ Linux image of ~~QT and QT applications~~the development board on the x64 computer, if or compile the Linux image of the development board on the Ubuntu22.04 system of the ~~following error is displayed~~development board, ~~ignore it. This error has no impact on application running~~please choose one according to your preference.'''

~~'''libGL error: failed to create dri screen'''~~

'''~~libGL~~ 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~~: failed to load driver: rockchip~~of file system runaway.'''</big>|}

~~'''libGL error: failed to create dri screen'''~~=== Compile with the Ubuntu22.04 system of the development board ===

# The Linux SDK, namely '''~~libGL error: failed~~ 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 ~~load driver: rockchip~~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.

~~<ol start~~::{| class="4wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>The interface after QT Creator is opened is as follows</li></ol>~~|-| orangepi@orangepi:~$ '''lsb_release -a'''

~~[[File:pi3b-img328~~No LSB modules are available.~~png|418x222px]]~~

~~<ol start="5" style="list-style-type~~Distributor ID: ~~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></ol></li></ol>~~Ubuntu

~~[[File~~Description:~~pi3b-img329~~Ubuntu 22.~~png|419x224px]]~~04.1 LTS

Release: '''<~~ol start="2"~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">22.04<li/span>~~The default version of QT Creator in '''Ubuntu22.04~~''' ~~is as follows</li></ol>~~

~~[[File~~Codename:~~pi3b-img330.png~~jammy|~~443x237px]]~~}

<ol start="32" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The default version of QT Creator in~~ '''~~Debian11~~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.''' ~~is as follows~~</li></ol>

~~[[File:pi3b~~

~~<ol start~~=~~"4" style~~=~~"list-style-type: lower-alpha;"><li>The default version of QT Creator in '''Debian12''' is as follows</li></ol>~~= Compile with x64 Ubuntu22.04 computer ===

~~[[File:pi3b~~# The Linux SDK, '''orangepi-~~img332~~build''', supports running on computers with '''Ubuntu 22.04''' installed, so before downloading orangepi-build, please make sure that the Ubuntu version installed on your computer is Ubuntu 22.04. The command to check the Ubuntu version installed on the computer is as follows. If the Release field does not display '''22.04''', it means that the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operations.~~png|449x277px]]~~

~~<ol start~~::{| class="6wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then set QT~~|-~~<ol style="list-style-type~~| test@test: ~~lower-alpha;"><li>First open '''Help~~~$ '''lsb_release -~~>''~~a'~~About Plugins...~~''~~'</li></ol></li></ol>~~

~~[[File:pi3b-img333~~No LSB modules are available.~~png|573x164px]]~~

~~<ol start="2" style="list-style-type~~Distributor ID: ~~lower-alpha;"><li>Then remove the check box for '''ClangCodeModel'''</li></ol>~~Ubuntu

~~[[File~~Description:~~pi3b-img334~~Ubuntu 22.~~png|408x254px]]~~04 LTS

Release: '''<~~ol start="3"~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">22.04<li/span>~~'''Restart QT Creator after the Settings are complete~~'''~~</li><li>Then make sure that QT Creator uses the GCC compiler, if the default is Clang, change it to GCC</li></ol>~~

~~'''Debian12 Please skip this step.'''~~Codename: jammy|}

~~[[File~~<ol start="2" style="list-style-type:~~pi3b~~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-~~img335~~build has not been tested in the WSL virtual machine, so it cannot be guaranteed that orangepi-build can be used normally in WSL.~~png|576x315px]]~~</li><li>The download address of the installation image of Ubuntu 22.04 '''amd64''' version is:</li>

{| class="wikitable" style="width:800px;" |-| [~~[File~~https://repo.huaweicloud.com/ubuntu-releases/21.04/ubuntu-21.04-desktop-amd64.iso '''https:~~pi3b~~//mirrors.tuna.tsinghua.edu.cn/ubuntu-~~img336~~releases/22.~~png|575x307px]~~04/ubuntu-22.04-desktop-amd64.iso''']

~~<ol start="7" style="list-style-type: decimal;"><li>You can then open a sample code</li></ol>~~Or

~~[[File~~'''https:~~pi3b~~//repo.huaweicloud.com/ubuntu-~~img337~~releases/22.~~png~~04/ubuntu-22.04.1-desktop-amd64.iso'''|~~575x312px]]~~}</ol><ol start="4" style="list-style-type: decimal;"><li>After installing Ubuntu 22.04 on the computer or virtual machine, please set the software source of Ubuntu 22.04 to Tsinghua source, otherwise it is easy to make mistakes due to network reasons when installing the software later<ol style="list-style-type: lower-alpha;"><li>For the method of replacing Tsinghua source, please refer to the instructions on this web page</li>

{| class="wikitable" style="width:800px;" |-| '''https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/'''|}</ol><ol start="82" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Clicking on the example code will automatically open the corresponding instruction document, you can carefully read~~ Note that the ~~instructions~~Ubuntu version needs to be switched to 22.04</li~~></ol~~>

[[File:pi3b-~~img338~~img376.png~~|576x218px~~]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The content of the '''/etc/apt/sources.list''' file that needs to be replaced is</li>

~~<ol start~~{| class="9wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then click~~ |-| test@test:~$ '''~~Configure Project~~sudo mv /etc/apt/sources.list /etc/apt/sources.list.bak'''~~</li></ol>~~

~~[[File~~test@test:~~pi3b-img339~~~$ '''sudo vim /etc/apt/sources.~~png|575x304px]]~~list'''

<~~ol start="10" style="list-style-type: decimal;"~~p>~~<li>Then click the green triangle in~~ # By default, the ~~lower left corner~~ source image is commented to ~~compile and run~~ improve the ~~sample code</li>~~speed of apt update, you can uncomment it yourself if necessary</olp>

~~[[File~~deb https:~~pi3b-img340~~//mirrors.~~png|575x312px]]~~tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse

<~~ol start="11" style="list~~p># deb-~~style-type~~src https: ~~decimal;"><li>After waiting for a period of time, the interface shown in the following figure will pop up, which indicates that QT can compile and run normally<~~/~~li>~~/mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse</olp>

~~[[File~~deb https:~~pi3b~~//mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-~~img341.png|576x308px]]~~updates main restricted universe multiverse

<~~ol start="12" style="list~~p># deb-~~style-type~~src https: ~~decimal;"><li>Reference documents<~~/~~li>~~/mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse</olp>

deb https://~~wiki~~mirrors.qttuna.iotsinghua.edu.cn/ubuntu/~~Install_Qt_5_on_Ubuntu~~jammy-backports main restricted universe multiverse

# deb-src https://~~download~~mirrors.qttuna.iotsinghua.edu.cn/ubuntu/~~archive~~jammy-backports main restricted universe multiverse</~~qtcreator~~p>

deb https://~~download~~mirrors.qttuna.iotsinghua.edu.cn/~~archive~~ubuntu/qt ~~== ROS Installation Method ==~~security main restricted universe multiverse

<~~span id="how-to-install-ros-1-noetic-on~~p># deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-~~20.04">~~security main restricted universe multiverse</~~span~~p>~~=== How to install ROS 1 Noetic on Ubuntu 20.04 ===~~

~~# The current active version of ROS 1 is as follows, the recommended version is '''Noetic Ninjemys'''~~

~~[[File:pi3b~~# Pre-~~img342.png|345x235px]]~~release software source, not recommended to enable

~~[[File~~# deb https:~~pi3b~~//mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-~~img343.png|576x210px]]~~proposed main restricted universe multiverse

~~[http~~# deb-src https://~~docs~~mirrors.~~ros~~tuna.~~org~~tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse|}</ ~~http~~ol><ol start="4" style="list-style-type:lower-alpha;"><li>After the replacement, you need to update the package information and make sure there is no error</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt update'''|}</~~docs~~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.~~ros.org]~~'''</li></ol></li></ol>

~~'''https://wiki.ros.org/Distributions'''~~== Get the source code of Linux sdk ==

<~~ol start~~span id="~~2" style="list~~download-orangepi-build-~~style~~from-~~type: decimal;~~github">~~<li>The official installation document link of ROS 1 '''Noetic Ninjemys''' is as follows:~~</~~li></ol~~span>=== Download orangepi-build from github ===

~~[http://wiki~~# The Linux sdk actually refers to the code of orangepi-build. orangepi-build is modified based on the armbian build system.~~ros~~Using orangepi-build, multiple versions of Linux images can be compiled.~~org/noetic/Installation/Ubuntu '''http~~First download the code of orangepi-build, the command is as follows:~~//wiki.ros.org/noetic/Installation/Ubuntu''']~~

~~<ol start~~::{| class="3wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>In the official installation document of ROS~~ |-| test@test:~$ '''~~Noetic Ninjemys''', Ubuntu recommends using Ubuntu20.04, so please make sure that the system used by the development board is '''Ubuntu20.04 desktop system~~sudo apt-get update'''~~</li></ol>~~

~~http~~test@test:~~//wiki.ros.org/noetic/Installation~~~$ '''sudo apt-get install -y git'''

~~[[File~~test@test:~~pi3b~~~$ '''git clone https://github.com/orangepi-~~img344~~xunlong/orangepi-build.~~png~~git -b next'''|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |~~312x176px]]~~-| <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>

<~~ol start~~div class="4figure" ~~style="list-style-type: decimal;"><li>Then use the script below to install ros1</li></ol~~>

~~orangepi@orangepi3b~~[[File:~~~$ '''install_ros~~pi3b-img377.~~sh ros1'''~~png|center]]

<~~ol start~~/div>|}::{| class="5wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Before using~~ '''Downloading the ~~ROS tool~~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), ~~you first need~~ if the Ubuntu PC prompts the user to ~~initialize rosdep~~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 ~~then you can quickly install some system dependencies and some core components in ROS when compiling~~ password of the ~~source code~~github account.'''</~~li></ol~~big>|}

~~'''Note that running the following command needs to ensure that~~ <ol start="2" style="list-style-type: decimal;"><li>The u-boot and Linux kernel versions currently used by the development board ~~can access github normally, otherwise an error will be reported due to network problems.'''~~are as follows</li>

{| class="wikitable" style="width:800px;text-align: center;"|-|'''~~The install_ros~~branch'''|'''u-boot version'''|'''Linux Kernel version'''|-|'''legacy'''|'''u-boot 2017.~~sh script will try to modify /etc/hosts and automatically run the following commands~~09'''|'''Linux5. ~~However, this method cannot guarantee normal access to github every time. If~~ 10'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The branch mentioned here is not the ~~following error is displayed after installing ros1 in install_ros.sh, please find other ways to allow~~ same thing as the ~~Linux system~~ branch of the ~~development board~~ orangepi-build source code, please do not confuse it. This branch is mainly used to ~~access github normally, and then manually run the following Order~~distinguish different kernel source code versions.'''

'''~~https://raw~~Currently, the Linux5.10 bsp kernel provided by RK is defined as the legacy branch.~~githubusercontent~~If the mainline kernel is supported in the future, a current branch will be added.~~com~~'''</~~ros~~big>|}</~~rosdistro~~ol><ol start="3" style="list-style-type: decimal;"><li>orangepi-build will contain the following files and folders after downloading</~~master/rosdep/osx~~p><ol style="list-style-type: lower-~~homebrew~~alpha;"><li>'''build.~~yaml~~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'''~~Hit https~~:GPL 2 license file</~~raw~~li><li>README.~~githubusercontent.com~~md: orangepi-build documentation</~~ros~~p></~~rosdistro/master/rosdep/base.yaml~~li><li>'''scripts''': General script for compiling Linux images</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''~~ERROR: error loading sources list:~~ls'''

'''~~The read operation timed out~~build.sh      external      LICENSE      README.md      scripts'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If you downloaded the code of orangepi-build from github, after downloading, you may find that orangepi-build does not contain the source code of u-boot and Linux kernel, nor does u-boot and Linux kernel need to use cross-compilation tools Chain, this is normal, because these things are stored in other separate github warehouses or some servers (the addresses will be detailed below). orangepi-build will specify the address of u-boot, Linux kernel and cross-compilation toolchain in the script and configuration file. When running orangepi-build, when it finds that there are no such things locally, it will automatically go to the corresponding place to download them.'''</big>|}</ol></li></ol>

~~orangepi@orangepi:~$ '''source /opt/ros/noetic/setup.bash'''~~=== Download the cross-compilation toolchain ===

~~orangepi@orangepi~~{| class="wikitable" style="background-color:#ffffdc;width:~$ 800px;" |-| <big>'''~~sudo rosdep init~~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>|}

~~Wrote /etc/ros/rosdep/sources~~# When orangepi-build runs for the first time, it will automatically download the cross-compilation toolchain and put it in the '''toolchains''' folder.~~list~~Every time after running the build.~~d/20~~sh script of orangepi-build, it will check whether the cross-~~default~~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.~~list~~

~~Recommended: please run~~<div class="figure">

~~rosdep update~~::[[File:pi3b-img378.png]]

~~orangepi~~</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>{| class="wikitable" style="width:800px;" |-| test@~~orangepi~~test:~/orangepi-build$ '''~~rosdep update~~ls toolchains/'''

~~reading in sources list data from /etc/ros/rosdep/sources~~gcc-arm-11.~~list~~2-2022.d02-x86_64-aarch64-none-linux-gnu

~~Hit https://raw~~gcc-arm-11.~~githubusercontent~~2-2022.~~com/ros/rosdistro/master/rosdep/osx~~02-x86_64-arm-none-linux-~~homebrew.yaml~~gnueabihf

~~Hit https://raw~~gcc-arm-9.~~githubusercontent~~2-2019.~~com/ros/rosdistro/master/rosdep/base.yaml~~12-x86_64-aarch64-none-linux-gnu

~~Hit https://raw~~gcc-arm-9.~~githubusercontent~~2-2019.~~com/ros/rosdistro/master/rosdep/python.yaml~~12-x86_64-arm-none-linux-gnueabihf

~~Hit https://raw~~gcc-linaro-4.~~githubusercontent~~9.~~com/ros/rosdistro/master/rosdep/ruby~~4-2017.~~yaml~~01-x86_64_arm-linux-gnueabi

~~Hit https://raw~~gcc-linaro-5.~~githubusercontent~~5.~~com/ros/rosdistro/master/releases/fuerte~~0-2017.~~yaml~~10-x86_64_arm-linux-gnueabihf

~~Query rosdistro index https://raw~~gcc-linaro-7.~~githubusercontent~~4.~~com/ros/rosdistro/master/index~~1-v42019.~~yaml~~02-x86_64_aarch64-linux-gnu

~~Skip end~~gcc-oflinaro-~~life distro "ardent"~~7.4.1-2019.02-x86_64_arm-linux-gnueabi

~~Skip end~~gcc-oflinaro-~~life distro "bouncy"~~aarch64-none-elf-4.8-2013.11_linux

~~Skip end~~gcc-oflinaro-~~life distro "crystal"~~arm-linux-gnueabihf-4.8-2014.04_linux

~~Skip end~~gcc-oflinaro-~~life distro &quot~~arm-none-eabi-4.8-2014.04_linux|}</ol><ol start="4" style="list-style-type: decimal;"><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;~~dashing&quot~~"><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>

~~Skip end~~=== orangepi-~~of-life distro "eloquent"~~build complete directory structure description ===

~~Add distro~~ <ol style="list-style-type: decimal;"><li>The orangepi-build repository does not contain the source code of the Linux kernel, u-boot, and cross-compilation toolchain after downloading. The source code of the Linux kernel and u-boot is stored in an independent git repository<ol style="list-style-type: lower-alpha;"><li>The git repository where the Linux kernel source code is stored is as follows:</li>{| class="wikitable" style="width:800px;" |-| '''https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-5.10-rk35xx'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The git warehouse where the b.u-boot source code is stored is as follows:</li>{| class="wikitable" style="width:800px;" |-| '''https://github.com/orangepi-xunlong/u-boot-orangepi/tree/v2017.09-rk3588'''|}</ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>When orangepi-build runs for the first time, it will download the cross-compilation toolchain, u-boot and Linux kernel source code. After successfully compiling a Linux image, the files and folders that can be seen in orangepi-build are::a. '''build.sh''': compile startup script:b. '''external''': Contains the configuration files needed to compile the image, scripts with specific functions, and the source code of some programs. The rootfs compressed package cached during the image compilation process is also stored in external:c. '''kernel''': stores the source code of the Linux kernel, and the folder named orange-pi-5.10-rk35xx stores the kernel source code of the legacy branch of the RK3588/RK3588S/RK3566 series development boards. Please do not manually name the folder name of the kernel source code Modify, if modified, the kernel source code will be re-downloaded when the compilation system is running:d. '''LICENSE''': GPL 2 license file:e. '''README'''.md: orangepi-build documentation:f. '''output''': Store compiled deb packages such as u-boot and Linux, compilation logs, and compiled images and other files:g. '''scripts''': general scripts for compiling Linux images:h. '''toolchains''': store cross-compilation toolchain:i. '''u-boot''': stores the source code of u-boot, the folder named v2017.09-rk3588 stores the u-boot source code of the legacy branch of the RK3588/RK3588S/RK3566 series development boards, the name of the folder of the u-boot source code Please do not modify it manually, if it is modified, the u-boot source code will be re-downloaded when the compiling system is running:j. '''userpatches''': Store configuration files needed to compile scripts</li>:{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''ls''''''build.sh     external     kernel     LICENSE     output     README.md     scripts     toolchains     u-boot  &~~quot~~nbsp;~~foxy~~&~~quot~~nbsp;userpatches'''|}</ol>

~~Add distro "galactic"~~== Compile u-boot ==

~~Skip end-of-life distro "groovy"~~# Run the build.sh script, remember to add sudo permission

~~Add distro "humble&quot~~::{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''sudo ./build.sh'''|}

~~Skip end-of-life distro "hydro"~~ ~~Skip end-of-life distro "indigo"~~ ~~Skip end-of-life distro "jade"~~ ~~Skip end-of-life distro "kinetic"~~ ~~Skip end-of-life distro "lunar"~~ ~~Add distro "melodic"~~ ~~Add distro "noetic"~~ ~~Add distro "rolling"~~ ~~updated cache in /home/orangepi/.ros/rosdep/sources.cache~~ <ol start="62" style="list-style-type: decimal;"><li>~~Then open a command line terminal window on the desktop, and then use the test_ros.sh script to start a small turtle routine to test whether ROS can be used normallyorangepi@orangepi:~$~~ Select '''~~test_ros.sh~~U-boot package'''~~</li><li>After running the '''test_ros.sh''' script~~, ~~a little turtle as shown in the figure below will pop up~~then enter</li~~></ol~~>

[[File:pi3b-~~img345~~img379.png~~|575x275px|图片4~~]]

</div></ol><ol start="83" style="list-style-type: decimal;"><li>Then ~~please keep~~ select the ~~terminal window just opened at~~ model of the ~~top~~development board</li~~></ol~~>

[[File:pi3b-~~img346~~img380.png~~|576x275px|图片5~~]]

</div></ol><ol start="94" style="list-style-type: decimal;"><li>~~At this time, press the direction keys on the keyboard~~ Then it will start to ~~control the little turtle to move up, down, left~~compile u-boot, and ~~right~~some information prompted during compilation is explained as follows<ol style="list-style-type: lower-alpha;"><li>u-boot source code version</olli>{| class="wikitable" style="width:800px;" |-| [o.k. ] Compiling u-boot [~~File:pi3b-img347~~'''v2017.~~png~~09''' ]|~~575x296px]]~~}</ol><~~span id~~ol start="~~how~~2" style="list-tostyle-~~install~~type: lower-~~ros~~alpha;"><li>The version of the cross-2compilation toolchain</li>{| class="wikitable" style="width:800px;" |-~~galactic~~| [ o.k. ] Compiler version [ '''aarch64-onlinux-~~ubuntu~~gnu-20gcc 7.~~04">~~4.1''' ]|}</~~span~~ol><ol start="3" style=~~= How~~ "list-style-type: lower-alpha;"><li>Path to ~~install ROS 2 Galactic on Ubuntu 20.04 =~~the generated u-boot deb package</li>{| class="wikitable" style="width:800px;" |-| ~~# The current active version of ROS 2 is as follows, the recommended version is~~ [ o.k. ] Target directory [ '''~~Galactic Geochelone~~orangepi-build/output/debs/u-boot''']|}~~[[File~~</ol><ol start="4" style="list-style-type:~~pi3b~~lower-alpha;"><li>The package name of the generated u-~~img348.png~~boot deb package</li>{| class="wikitable" style="width:800px;" |~~576x271px]]~~-| [o.k. ] File name [~~File:pi3b~~'''linux-u-boot-legacy-~~img349~~orangepi3b_1.~~png~~0.0_arm64.deb''' ]|~~575x265px]]~~}</ol>~~[http~~<ol start="5" style="list-style-type:lower-alpha;"><li>Compilation time</~~/docs.ros.org/ http~~li>{| class="wikitable" style="width:~~//docs~~800px;" |-| [ o.~~ros~~k.~~org~~] Runtime [ '''~~http://docs.ros.org/en/galactic/Releases.html~~1 min''']|}</ol><ol start="26" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~The link~~ Repeat the command to compile u-boot, use the following command to start compiling u-boot directly without selecting through the ~~official ROS 2~~ graphical interface</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Repeat Build Options [ '''~~Galactic Geochelone~~sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=u-boot KERNEL_CONFIGURE=no''' ~~installation documentation is as follows:~~]|}</ol></li></ol><ol start="5" style="list-style-type: decimal;"><li>View the u-boot deb package generated by compilation</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''ls output/debs/u-boot/'''

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@test:~/orangepi-build$ '''~~docs.ros.org~~cd output/endebs/~~galactic/Installation.html~~u-boot'''

~~'''http~~test@test:~/orangepi_build/~~docs.ros.org/en/galactic~~output/~~Installation~~debs/~~Ubuntu~~u-~~Install~~boot$ $ '''dpkg -~~Debians.html~~x'''\

~~<ol start="3" style="list~~'''linux-u-~~style~~boot-~~type: decimal~~legacy-orangepi3b_1.0.0_arm64.deb . (Note that there is a "">~~<li>It is recommended to use Ubuntu20~~.~~04 in~~ " at the ~~official installation document~~ end of ROS 2 '''Galactic Geochelone''', so please ensure that the system used by the development board is '''Ubuntu20.04 desktop version'''. There are several ways to install ROS 2. The following shows how to install ROS 2 '''Galactic Geochelone''' using '''Debian packages'''</li>~~<li>Use~~ the command)'''~~install_ros.sh''' script to install ros2</li></ol>~~

~~orangepi~~test@~~orangepi~~test:~/orangepi_build/output/debs/u-boot$ '''~~install_ros.sh ros2~~ls'''

linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb '''usr'''|}</ol><ol start="52" style="list-style-type: ~~decimal~~lower-alpha;"><li>The decompressed file is as follows</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build/output/debs/u-boot$ '''~~install_ros.sh''' script will automatically run the '''ros2 -h~~tree usr''' ~~command after installing ros2. If you can see the following print, it means that the ros2 installation is complete</li></ol>~~

~~usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...~~usr

~~ros2 is an extensible command-line tool for ROS 2.~~└── lib

~~optional arguments~~:├── linux-u-boot-legacy-orangepi3b_1.0.0_arm64

~~-h, --help show this help message and exit~~:│ ├── idbloader.img

~~Commands~~:│ ├── rkspi_loader.img

~~action Various action related sub~~:│ └── u-~~commands~~boot.itb

~~bag Various rosbag related sub~~:└── u-~~commands~~boot

~~component Various component related sub-commands~~::├── LICENSE

~~daemon Various daemon related sub~~::├── orangepi-~~commands~~3b-rk3566_defconfig

~~doctor Check ROS setup and other potential issues~~::└── platform_install.sh

~~interface Show information about ROS interfaces~~

~~launch Run a launch file~~3 directories, 6 files|}</ol></li></ol><ol start="7" style="list-style-type: decimal;"><li>When the orangepi-bulid compilation system compiles the u-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>

~~lifecycle Various lifecycle related sub~~Set the IGNORE_UPDATES variable in userpatches/config-~~commands~~default.conf to "yes"

~~multicast Various multicast related sub~~{| class="wikitable" style="width:800px;" |-~~commands~~| test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''

~~node Various node related sub~~IGNORE_UPDATES="'''yes'''"|}</ol><ol start="8" style="list-~~commands~~style-type: decimal;"><li>When debugging u-boot code, you can use the following method to update u-boot in the Linux image for testing<ol style="list-style-type: lower-alpha;"><li>Upload the compiled u-boot deb package to the Linux system of the development board</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''cd output/debs/u-boot'''

~~param Various param related sub~~test@test:~/orangepi_build/output/debs/u-~~commands~~boot$ '''scp \'''

~~pkg Various~~ '''linux-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 ~~related sub~~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-~~commands~~boot in the SPI Flash</li>

~~run Run~~ [[File:pi3b-img381.png]]</ol><ol start="6" style="list-style-type: lower-alpha;"><li>After pressing the Enter key, a ~~package specific executable~~Warning will pop up first</li>

~~security Various security related sub~~[[File:pi3b-~~commands~~img382.png]]</ol><ol start="7" style="list-style-type: lower-alpha;"><li>Press the Enter key again to start updating u-boot, and the following information will be displayed after the update is completed</li>

~~service Various service related sub~~[[File:pi3b-~~commands~~img383.png]]</ol><ol start="8" style="list-style-type: lower-alpha;"><li>Then you can restart the development board to test whether the modification of u-boot takes effect</li></ol></li></ol><ol start="9" style="list-style-type: decimal;"><li>Other useful information<ol style="list-style-type: lower-alpha;"><li>In the u-boot 2017.09 source code, the defconfig configuration file used by the development board is</li>{| class="wikitable" style="width:800px;" |-| [https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/configs/orangepi_5_defconfig '''orangepi-build/u-boot/v2017.09-rk3588/configs/orangepi-3b-rk3566_defconfig''']|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>In the u-boot 2017.09 source code, the dts file used by the development board is</li>{| class="wikitable" style="width:800px;" |-| [https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/arch/arm/dts/rk3588s-orangepi-5.dts '''orangepi-build/u-boot/v2017.09-rk3588/arch/arm/dts/rk3566-orangepi-3b.dts''']|}</ol></li></ol>

~~topic Various topic related sub-commands~~== Compile the Linux kernel ==

~~wtf Use `wtf` as alias~~ # Run the build.sh script, remember to ~~`doctor`~~add sudo permission

~~Call `ros2 <command&gt~~::{| class="wikitable" style="width:800px; " |-| test@test:~/orangepi-~~h` for more detailed usage~~build$ '''sudo ./build.sh'''|}

<ol start="62" style="list-style-type: decimal;"><li>~~Then you can use the~~ Select '''~~test_ros.sh~~Kernel package''' ~~script to test whether ROS 2 is installed successfully. If you can see the following print~~, ~~it means that ROS 2 can run normally~~then enter</li~~></ol~~>

~~orangepi@orangepi3b:~$ '''test_ros.sh'''~~<div class="figure">

[~~INFO]~~ [~~1671174101~~File:pi3b-img384.~~200091527~~png] ~~[talker~~]~~: Publishing: 'Hello World: 1'~~

~~[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: 1]~~ ~~[INFO] [1671174102.199572327] [talker]: Publishing: 'Hello World: 2'~~ ~~[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]~~ ~~[INFO] [1671174103.199580322] [talker]: Publishing: 'Hello World: 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~~ Then it will prompt whether to display the kernel configuration interface. If you do not need to modify the ~~usage of ROS~~kernel configuration, ~~please refer~~ select the first one. If you need to modify the kernel configuration, select the ~~documentation of ROS 2~~second one.</li~~></ol~~>

~~http~~[[File:pi3b-img385.png]]</~~/docs~~ol><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.~~ros~~At this time, you can directly modify the kernel configuration, save and exit after modification.~~org/en~~Yes, after exiting, the kernel source code will be compiled</~~galactic/Tutorials.html~~li>

~~=== How to install ROS 2 Humble on Ubuntu 22~~img386.~~04 ===~~png]]

~~# Use~~ <ol style="list-style-type: lower-alpha;"><li>If you do not need to modify the configuration options of the kernel, when running the build.sh script, pass in '''KERNEL_CONFIGURE=no''' to temporarily block the pop-up kernel configuration interface</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''~~install_ros~~sudo ./build.shKERNEL_CONFIGURE=no'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>You can also set '''KERNEL_CONFIGURE=no''' in the '''orangepi-build/userpatches/config-default.conf''' configuration file, which can permanently disable this function</li><li>If the following error is displayed when compiling the kernel, it is because the terminal interface of the Ubuntu PC is too small to display the '''make menuconfig'' ' interface. Please maximize the terminal of the Ubuntu PC and run the build.sh script ~~to install ros2~~again</li>

~~orangepi@orangepi~~[[File:pi3b-img387.png]]</ol></ol><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>{| class="wikitable" style="width:~$ 800px;" |-| [ o.k. ] Compiling current kernel [ '''~~install_ros~~5.~~sh ros2~~10.160''']|}</ol><ol start="2" style="list-style-type: ~~decimal~~lower-alpha;"><li>The version of the cross-compilation toolchain used</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Compiler version [ '''~~install_ros~~aarch64-none-linux-gnu-gcc 11.sh2.1''' ~~script will automatically run~~ ]|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The configuration file used by the kernel by default and the path where it is stored</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Using kernel config file [ '''~~ros2~~ config/kernel/linux-hrockchip-rk356x-legacy.config''' ~~command after installing ros2. If you can see~~ ]|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>The path of the ~~following print, it means that~~ deb package related to the ~~ros2 installation is complete~~kernel generated by compiling</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Target directory [ '''orangepi-build/output/debs/''' ]|}</ol><ol start="5" style="list-style-type: lower-alpha;">~~usage~~<li>The package name of the compiled kernel image deb package</li>{| class="wikitable" style="width: ~~ros2~~ 800px;" |-| [ o.k. ] File name ['''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb''' ]|}</ol><ol start="6" style="list-style-type: lower-alpha;"><li>The time used for compilation</li>{| class="wikitable" style="width:800px;" |-h| [ o.k. ] Runtime [ '''5 min''' ] ~~Call `ros2 &lt~~|}</ol><ol start="7" style="list-style-type: lower-alpha;"><li>Finally, the compilation command to repeatedly compile the kernel selected last time will be displayed. Use the following command~~&gt~~to start compiling the kernel source code directly without selecting through the graphical interface</li>{| class="wikitable" style="width:800px; " |-~~h` for more detailed usage~~| [ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=kernel KERNEL_CONFIGURE=no''' ]|}</ol></li></ol><ol start="7" style="list-style-type: decimal;"><li>View the deb package related to the kernel generated by compilation<ol style="list-style-type: lower-alpha;"><li>'''linux-dtb-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Contains dtb files used by the kernel</li><li>'''linux-headers-legacy-rockchip-rk356x_1.0.0_arm64. deb''' Include kernel header files</li><li>'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Contains kernel images and kernel modules</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''ls output/debs/linux-*'''

~~ros2 is an extensible command~~output/debs/linux-~~line tool for ROS 2~~dtb-legacy-rockchip-rk356x_1.0.0_arm64.deb output/debs/linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb

~~optional arguments~~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-h, style-type: lower-~~help show this help message and exit~~alpha;"><li>Use the following command to decompress the deb package</li>~~Commands~~{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''cd output/debs'''

~~action Various action related sub-commands~~test@test:~/orangepi_build/output/debs$ '''mkdir test'''

~~bag Various rosbag related sub-commands~~test@test:~/orangepi_build/output/debs$ '''cp \'''

~~component Various component related sub~~'''linux-~~commands~~image-legacy-rockchip-rk356x_1.0.0_arm64.deb test/'''

~~daemon Various daemon related sub-commands~~test@test:~/orangepi_build/output/debs$ '''cd test'''

~~doctor Check ROS setup and other potential issues~~test@test:~/orangepi_build/output/debs/test$ '''dpkg -x \'''

~~interface Show information about ROS interfaces~~'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb .'''

~~launch Run a launch file~~test@test:~/orangepi_build/output/debs/test$ '''ls'''

~~lifecycle Various lifecycle related sub~~'''boot etc lib''' linux-~~commands~~image-legacy-rockchip-rk356x_1.0.0_arm64.deb '''usr'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The decompressed file is as follows</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build/output/debs/test$ '''tree -L 2'''

~~multicast Various multicast related sub-commands~~.

~~node Various node related sub-commands~~├── boot

~~param Various param related sub~~│ ├── config-~~commands~~5.10.160-rockchip-rk356x

~~pkg Various package related sub~~│ ├── System.map-~~commands~~5.10.160-rockchip-rk356x

~~run Run a package specific executable~~│ └── vmlinuz-5.10.160-rockchip-rk356x

~~security Various security related sub-commands~~├── etc

~~service Various service related sub-commands~~│ └── kernel

~~topic Various topic related sub-commands~~├── lib

~~wtf Use `wtf` as alias to `doctor`~~│ └── modules

~~Call `ros2 <command>~~ ├── linux-~~h` for more detailed usage~~image-legacy-rockchip-rk356x_1.0.0_arm64.deb

~~<ol start="3" style="list-style-type: decimal;"><li>Then you can use the '''test_ros.sh''' script to test whether ROS 2 is installed successfully. If you can see the following print, it means that ROS 2 can run normally</li></ol>~~└── usr

~~orangepi@orangepi3b~~:~~~$ '''test_ros.sh'''~~├── lib

~~[INFO] [1671174101.200091527] [talker]~~: ~~Publishing~~└── share|}</ol></li></ol><ol start="9" style="list-style-type: decimal;"><li>The orangepi-bulid compilation system will first synchronize the Linux kernel source code with the Linux kernel source code of the github server when compiling the Linux kernel source code, so if you want to modify the Linux kernel source code, you first need to turn off the update function of the source code '''(you need to compile it once This function can only be turned off after the Linux kernel source code, otherwise it will prompt that the source code of the Linux kernel cannot be found. If the source code compressed package downloaded from Google cloud disk, there is no such problem, because the source code of Linux has been cached)'''~~Hello World~~, otherwise the The changes made will be reverted as follows: 1'</li>

~~[INFO] [1671174101~~Set the IGNORE_UPDATES variable in '''userpatches/config-default.~~235661048] [listener]: I heard: [Hello World: 1]~~conf''' to "yes"

~~[INFO] [1671174102.199572327] [talker]~~{| class="wikitable" style="width: ~~Publishing~~800px;" |-| test@test: ~/orangepi-build$ '''vim userpatches/config-default.conf''~~Hello World: 2~~'

~~[INFO] [1671174102.204196299] [listener]~~IGNORE_UPDATES="'''yes'''"|}</ol><ol start="10" style="list-style-type: ~~[Hello World~~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: 2]lower-alpha;"><li>Upload the deb package of the compiled Linux kernel to the Linux system of the development board</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''cd output/debs'''

~~[INFO] [1671174103.199580322] [talker]: Publishing~~test@test: ~/orangepi-build/output/debs$ '''scp \''~~Hello World: 3~~'

'''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;" |-| [~~INFO] [1671174103~~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.~~204019965] [listener~~config''']|}</ol><ol start="2" style="list-style-type: ~~I heard~~lower-alpha;"><li>The location of the dts file used by the development board is</li>{| class="wikitable" style="width: 800px;" |-| [~~Hello World~~https: 3//github.com/orangepi-xunlong/linux-orangepi/blob/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5.dts '''orangepi-build/kernel/orange-pi-5.10-rk35xx/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dts''']|}</ol></li></ol> == Compile rootfs ==

~~<ol start="4" style="list-style-type: decimal;"><li>~~# Run the ~~following command~~ build.sh script, remember to ~~open rviz2</li></ol>~~add sudo permission

~~orangepi~~::{| class="wikitable" style="width:800px;" |-| test@~~orangepi~~test:~/orangepi-build$ '''~~source /opt/ros/humble~~sudo ./~~setup~~build.~~bash~~sh'''|}

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~$ decimal;"><li>Select '''~~ros2 run rviz2 rviz2~~Rootfs and all deb packages''', then enter</li>

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

</div></ol><ol start="53" style="list-style-type: decimal;"><li>~~Reference documents~~Then select the model of the development board</li~~></ol~~>

~~'''http://docs.ros.org/en/humble/index.html'''~~<div class="figure">

[~~http~~[File:~~//docs.ros.org/en/galactic/Tutorials.html '''http://docs.ros.org/en/humble/Installation/Ubuntu-Install~~pi3b-~~Debians~~img380.~~html'''~~png]]

<~~span id~~/div></ol><ol start="~~how~~4" style="list-tostyle-~~install-kernel-header-files~~type: decimal;"><li>Then select the type of rootfs</~~span~~li>~~== How to install kernel header files ==~~

~~# The Linux~~ [[File:pi3b-img389.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then select the type of image ~~released by OPi comes~~ <ol style="list-style-type: lower-alpha;"><li>'''Image with console interface (server)''' Indicates the ~~deb package~~ image of the ~~kernel header file by default~~server version, ~~and the storage location~~ which is relatively small</li><li>'''~~/opt/~~Image with desktop environment'''Indicates a image with a desktop, which is relatively large</li>

~~orangepi@orangepi:~$ '''ls /opt/linux-headers*'''~~ ~~/opt/linux-headers-legacy-rockchip-rk356x_x.x.x_arm64.deb~~ <~~ol start~~div class="2figure" ~~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~~[[File:~~~$ '''ls /usr/src'''~~pi3b-img390.png]]

~~linux-headers-5.10.160-rockchip-rk356x~~ ~~<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:~~</lidiv></ol>

</li></ol>

<li>If you are compiling the image of the server version, you can also choose to compile the Standard version or the Minimal version. The pre-installed software of the Minimal version will be much less than that of the Standard version '''(please do not choose the Minimal version if there is no special requirement, because many things are not pre-installed by default. Some functions may not be available)'''</li>

~~orangepi@orangepi:~$ '''vim hello.c'''~~<div class="figure">

~~#include <linux/init~~[[File:pi3b-img391.~~h>~~png]]

~~#include &lt~~</div></ol><ol start="7" style="list-style-type: decimal;~~linux~~"><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</~~module.h>~~li>

~~static int hello_init(void)~~<div class="figure">

{[[File:pi3b-img392.png]]

~~printk("Hello Orange Pi~~ </div>[[File:pi3b-~~- init\n");~~img393.png]]

~~return 0;~~You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.

[[File:pi3b-img394.png]]</ol><ol start="8" style="list-style-type: decimal;"><li>Then it will start to compile rootfs, and some of the information prompted during compilation are as follows<ol style="list-style-type: lower-alpha;"><li>The type of rootfs</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] local not found [ Creating new rootfs cache for '''jammy''']|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The storage path of the compiled rootfs compressed package</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Target directory [ '''external/cache/rootfs''' ]|}</ol>~~static void hello_exit(void)~~<ol start="3" style="list-style-type: lower-alpha;"><li>The name of the rootfs compressed package generated by compilation</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] File name [ '''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' ]|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>The time used for compilation</li>~~printk(&quot~~{| class="wikitable" style="width:800px;~~Hello Orange Pi~~ " |-| [ o.k. ] Runtime [ '''13 min''' ]|}</ol></li></ol><ol start="9" style="list- ~~exit\n&quot~~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~~return~~<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>~~module_init(hello_init~~<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/'''

~~module_exit(hello_exit);~~'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4'''

~~MODULE_LICENSE("GPL");~~jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.current

jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.list|}</ol></li></ol><ol start="210" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then write~~ If the required rootfs already exists under '''external/cache/rootfs''', then compiling rootfs again will directly skip the ~~Makefile for~~ compilation process and will not restart the compilation. When compiling the ~~hello kernel module~~image, it will also go to '''external/cache/rootfs''' to find out whether it has If there is rootfs available in the cache, ~~as follows:~~use it directly, which can save a lot of download and compilation time.</li></ol>

~~orangepi@orangepi:~$ '''vim Makefile'''~~

~~ifneq ($(KERNELRELEASE),)~~== Compile Linux image ==

~~obj-m:=hello~~# Run the build.osh script, remember to add sudo permission

~~else~~::{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''sudo ./build.sh'''|}

~~KDIR :~~<ol start="2" style=~~/lib/modules/$(shell uname~~ "list-style-r)type: decimal;"><li>Select '''Full OS image for flashing''', then enter</~~build~~li>

~~PWD :~~<div class=~~$(shell pwd)~~"figure">

~~all~~[[File:pi3b-img395.png]]

~~make~~ </div></ol><ol start="3" style="list-style-~~C $(KDIR) M=$(PWD) modules~~type: decimal;"><li>Then select the model of the development board</li>

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

rm [[File:pi3b-f *img380.~~ko *.o *.mod.o *.mod *.symvers *.cmd *.mod.c *.order~~png]]

~~endif~~</div></ol><ol start="4" style="list-style-type: decimal;"><li>Then select the type of rootfs</li>

[[File:pi3b-img389.png]]</ol><ol start="35" style=" list-style-type: decimal;"><li>Then select the type of image<ol style="list-style-type: lower-alpha;"><li>~~Then use~~ '''Image with console interface (server)''' Indicates the ~~make command to compile the hello kernel module. The output~~ image of the ~~compilation process~~ server version, which is ~~as follows:~~relatively small</li><li>'''Image with desktop environment''' Indicates a image with a desktop, which is relatively large</olp></li>

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

[[File:pi3b-~~img352~~img390.png~~|337x52px~~]]

~~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 '''~~make~~(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>

~~make -C /lib/modules/5.10.160-rockchip-35xx/build M~~<div class=~~/home/orangepi modules~~"figure">

~~make~~[1][File: ~~Entering directory '/usr/src/linux-headers~~pi3b-5img391.~~10.160-rockchip-rk35xx'~~png]]

~~CC [M]~~ </~~home~~div></~~orangepi~~ol><ol start="7" style="list-style-type: decimal;"><li>If you are compiling the image of the desktop version, you also need to select the type of desktop environment. Currently, Ubuntu Jammy mainly maintains XFCE and Gnome desktops, Ubuntu Focal only maintains XFCE desktops, and Debian Bullseye mainly maintains XFCE and KDE desktops</~~hello.o~~li>

~~MODPOST /home/orangepi/Module.symvers~~<div class="figure">

CC [M[File:pi3b-img392.png]] ~~/home/orangepi/hello.mod.o~~

LD </div>[[MFile:pi3b-img393.png]] ~~/home/orangepi/hello.ko~~

~~make[1]: Leaving directory '/usr/src/linux-headers-5~~You can then select additional packages that need to be installed.10Please press the Enter key to skip directly here.~~160-rockchip-rk35xx'~~

[[File:pi3b-img394.png]]</ol><ol start="48" style="list-style-type: decimal;" ><li>Then it will start to compile the Linux image. The general process of compilation is as follows<ol style="list-style-type: lower-alpha;"><li>Initialize the compilation environment of Ubuntu PC and install the software packages required for the compilation process</li><li>Download the source code of u-boot and Linux kernel (if cached, only update the code)</li><li>Compile u-boot source code and generate u-boot deb package</li><li>Compile the Linux source code and generate Linux-related deb packages</li><li>Make the deb package of Linux firmware</li><li>Make the deb package of the orangepi-config tool</li><li>Create a deb package supported by the board</li><li>If you are compiling the desktop image, you 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 compilingthe image, the following information will be prompted<ol style="list-style-type: lower-alpha;"><li>The storage path of the compiled image</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Done building [ '''output/images/Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160/Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160.img''' ]|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Compilation time</li>{| class="wikitable" style="width:800px;" |-| '''[ o.k. ] Runtime [ 19 min ]'''|}</ol><ol start="3" 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>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Repeat Build Options [ '''~~hello~~sudo ./build.kosh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=image RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=yes''' ~~kernel module will be generated~~]|}</ol></li></ol>

~~orangepi@orangepi:~$~~ = '''~~ls *.ko~~Android 11 operating system instructions'''=

~~hello.ko~~== Supported Android versions ==

~~<ol start~~{| class="5wikitable" style="~~list-style~~width:800px;text-~~type~~align: ~~lower-alpha~~center;">~~<li>Use the~~ |-|'''~~insmod~~Android version''' ~~command to insert the~~ |'''Kernel version'''~~hello~~|-|'''Android 11'''|'''Linux4.ko19''' ~~kernel module into the kernel</li></ol>~~|}

~~orangepi@orangepi:~$ '''sudo insmod hello.ko'''~~

~~<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>Android Function Adaptation ==

~~orangepi@orangepi~~{| class="wikitable" style="width:800px;text-align:~$ center;"|-|'''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'''~~dmesg~~ | ~~grep "Hello"~~'''OK'''|-|'''Headphone recording'''|'''OK'''|-|'''LED Light'''|'''OK'''|-|'''GPU'''|'''OK'''|-|'''NPU'''|'''OK'''|-|'''VPU'''|'''OK'''|-|'''RTC'''|'''OK'''|}

~~[ 2871.893988] '''Hello Orange Pi~~

~~<ol start~~=~~"7" style~~=~~"list-style-type: lower-alpha;"><li>Use the '''rmmod''' command to uninstall the '''hello.ko''' kernel module</li></ol>~~WIFI connection test method ==

~~orangepi@orangepi:~$~~ # First click enter '''~~sudo rmmod hello~~Setting'''

~~orangepi@orangepi~~:~~~$ '''dmesg | grep "Hello"'''~~:[[File:pi3b-img396.png]]

~~[ 2871.893988] Hello Orange Pi~~ <ol start="2" style="list-style- ~~init~~type: decimal;"><li>Then select '''Network & internet'''</li>

[ ~~3173~~[File:pi3b-img397.~~800892~~png] ]</ol><ol start="3" style="list-style-type: decimal;"><li>Then select '''~~Hello Orange Pi -~~Wi- ~~exit~~Fi'''</li>

[[File:pi3b-img398.png]]</ol><~~span id~~ol start="~~use-of-the-raspberry-pis-5~~4" style="list-~~inch~~style-~~screen~~type: decimal;"><~~/span~~li>~~== Use of~~ Then turn on the ~~Raspberry PI~~'~~s 5~~''Wi-~~inch screen ==~~Fi''' switch</li>

[[File:pi3b-img399.png]]<~~span id~~/ol><ol start="~~assembly-method-of-raspberry-pi-~~5" style="list-~~inch~~style-~~screen~~type: decimal;"><li>After turning on '''Wi-Fi''', if everything is normal, you can scan for nearby Wi-Fi hotspots</~~span~~li>~~=== Assembly method of Raspberry PI 5-inch screen ===~~

~~<ol style="list~~[[File:pi3b-~~style-type: decimal;">~~img400.png]]~~<li>First prepare the required accessories~~</pol><ol start="6" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Raspberry PI 5~~Then select the Wi-~~inch MIPI LCD display + touch screen~~Fi you want to connect to, and the password input interface shown in the figure below will pop up</li~~></ol></li></ol~~>

~~<blockquote>~~[[File:pi3b-~~img353~~img401.png~~|306x219px~~]]</~~blockquote~~ol><ol start="27" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~15pin MIPI cable~~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~~>

~~<blockquote>~~[[File:pi3b-~~img354~~img402.png~~|276x111px~~]]</~~blockquote~~ol><ol start="28" style="list-style-type: decimal;"><li>~~Then connect~~ After the ~~15pin MIPI cable to~~ Wi-Fi connection is successful, the ~~Raspberry PI 5-inch screen~~ display is as shown in the ~~way shown~~ figure below ~~(note the orientation of the insulation surface)~~:</li~~></ol~~>

[[File:pi3b-~~img355~~img403.png~~|294x160px~~]]</ol>

~~<ol start~~=~~"3" style~~=~~"list~~How to use Wi-~~style-type: decimal;"><li>Finally connect to the LCD interface of the Orange Pi 3B development board</li></ol>~~Fi hotspot ==

~~[[File:pi3b-img356.png|333x199px]]~~# First, please make sure that the Ethernet port is connected to the network cable and can access the Internet normally# Then select '''Settings'''

~~=== Open the Raspberry PI 5-inch screen configuration method ===~~img396.png]]

<ol ~~style~~start="~~list-style-type: decimal;~~3">~~<li>The Linux image does not open the 5-inch screen of the Raspberry PI by default. If you need to use the 5-inch screen of the Raspberry PI, you need to open it manually.</li><li>The steps to open the mipi lcd configuration are as follows:<ol~~ style="list-style-type: ~~lower-alpha~~decimal;"><li>~~First run~~ Then select '''~~orangepi-config~~Network & internet'''~~, ordinary users remember to add '''sudo''' permission</li></ol>~~</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img397.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select '''~~sudo orangepi-config~~Hotspot & tethering'''</li>

[[File:pi3b-img404.png]]</ol><ol start="25" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then select '''~~System~~Wi-Fi hotspot'''</li~~></ol~~>

[[File:pi3b-~~img357~~img405.png~~|575x272px~~]]</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>

[[File:pi3b-img406.png]]</ol><ol start="37" style="list-style-type: ~~lower-alpha~~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 ~~select~~ you can click '''AndroidAP_6953''' to connect to the hotspot, and the password can be seen under the '''~~Hardware~~Hotspot password'''in the above picture</li~~></ol~~>

[[File:pi3b-~~img358~~img407.png~~|576x266px~~]]</ol><ol start="8" style="list-style-type: decimal;"><li>After the connection is successful, it will be displayed as shown in the figure below (the interface of different mobile phones will be different, the specific interface is subject to the display of your mobile phone). At this point, you can open a webpage on your mobile phone to see if you can access the Internet. If you can open the webpage normally, it means that the '''WI-FI Hotspot''' of the development board can be used normally.</li>

[[File:pi3b-img408.png]]</ol ~~start~~>~~<li>Then use the arrow keys on the keyboard to locate the Rasp-7inch-touchscreen, and then use the space button to check</li~~></olspan>

~~[[File:pi3b-img359.png|408x310px]]~~== Bluetooth test method ==

~~<ol start="5" style="list-style-type: lower-alpha;"><li>Then select~~ # First click enter '''~~<Save>~~Setting''' ~~to save</li></ol>~~

::[[File:pi3b-~~img360~~img396.png~~|404x133px~~]]

<ol start="62" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then select '''~~<Back>~~Connected devices'''</li~~></ol~~>

[[File:pi3b-~~img361~~img409.png~~|397x151px~~]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then click '''Pair new device''' to turn on Bluetooth and start scanning the surrounding Bluetooth devices</li>

[[File:pi3b-img410.png]]</ol><ol start="74" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then select~~ The searched Bluetooth devices will be displayed under '''~~<Reboot>~~Available devices''' ~~to restart the system for the configuration to take effect~~</li~~></ol~~>

[[File:pi3b-~~img362~~img411.png~~|331x154px~~]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then click the Bluetooth device you want to connect to start pairing. When the following interface pops up, please use the mouse to select the '''Pair''' option</li>

~~'''~~[[File:pi3b-img412.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>The ~~above settings will eventually add~~ test here is the configuration process of ~~overlays=raspi-7inch-touchscreen to /boot/orangepiEnv~~the development board and the Bluetooth of the Android mobile phone.~~txt~~At this time, the following confirmation interface will pop up on the mobile phone. After ~~setting, you can check it first. If this configuration does not exist~~clicking the pairing button on the mobile phone, ~~then there is a problem with~~ the ~~settings.'''~~pairing process will start</li>

~~'''If you find it troublesome to use orangepi~~[[File:pi3b-img413.png]]</ol><ol start="7" style="list-style-~~config~~type: decimal;"><li>After the pairing is completed, you can ~~also use~~ see the ~~vim editor to open~~ paired Bluetooth device as shown in the figure below</~~boot/orangepiEnv.txt, and then add the configuration of overlays=raspi-7inch-touchscreen is also possible.'''~~li>

~~orangepi@orangepi~~[[File:~$ pi3b-img414.png]]</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 '''~~cat /boot/orangepiEnv.txt | grep "raspi"~~Accept'''to start receiving the picture sent by the mobile phone.</li>

[[File:pi3b-img415.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>You can open the '''~~overlays=raspi-7inch-touchscreen #Sample configuration~~Download'''directory in the file manager to view the pictures received by the Android system Bluetooth of the development board</li>

[[File:pi3b-img416.png]]</ol ~~start~~>~~<li>After startup, you can see the lcd screen display as follows:</li~~></olspan>

~~[[File:pi3b~~== How to use Raspberry Pi 5-~~img363.png|381x262px]]~~inch screen ==

~~~~| <~~/span~~big>~~=== The method~~ '''Please make sure that the image used is the following two versions of ~~server version~~ the image ~~rotation display direction ===~~:'''

~~# Add~~ '''~~extraargs=fbcon=rotate:the direction to rotate''' in '''/boot/orangepiEnv~~OrangePi3B_RK3566_Android11_lcd_v1.x.x.~~txt''' This line configuration can set the direction displayed by the server version of the Linux system, where the number after '''fbcon=rotate:~~img''' ~~can be set as:~~

~~<ol style="list-style-type: lower~~'''OrangePi3B_RK3566_Android11_spi-~~alpha;"><li>0: normal screen (default is landscape)</li><li>1: Turn clockwise 90 degrees</li><li>2: Flip 180 degrees~~nvme_lcd_v1.x.x.img'''</~~p></li~~big>~~<li>3: Turn clockwise 270 degrees</li></ol>~~|}

~~orangepi@orangepi:~$~~ # The screen needs to be assembled first, please refer to [[Orange Pi 3B#Use of the Raspberry PI's 5-inch screen|''~~sudo vim /boot/orangepiEnv.txt~~'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

~~overlays=lcd1~~::[[File:pi3b-img417.png]]

~~'''extraargs~~

~~'''Note that if there is the line extraargs~~=~~cma~~=~~64M in /boot/orangepiEnv.txt by default~~40pin interface GPIO, ~~the configuration fbcon=rotate:3 can be added after extraargs~~UART, SPI and PWM test =~~cma~~=~~64M (separated by spaces).'''~~

<~~ol start~~span id="~~2" style="list~~pin-gpio-port-~~style~~test-~~type: decimal;~~2">~~<li>Then '''restart''' the Linux system and you can see that the direction displayed on the LCD screen has been rotated~~</~~li></ol~~span>=== 40pin GPIO port test ===

~~=== Method of rotating display and touch direction of desktop version image ===~~# First click on the wiringOP icon to open the wiringOP APP

~~# First open '''Display''' Settings in Linux~~ ::[[File:pi3b-~~img364~~img418.png~~|298x206px~~]]

<li>~~Then select~~ The main interface of wiringOP APP is displayed as shown in the figure below, and then click the ~~direction you want to rotate in '''Rotation'''<ol style="list-style-type: lower-alpha;"><li>'''None''': no rotation</li><li>'''Left''': rotate left 90 degrees</li><li>~~'''~~Inverted~~GPIO_TEST'''~~: Flip up and down, which is equivalent~~ button to ~~rotating 180 degrees</li><li>'''Right''': rotate right 90 degrees</li></ol>~~open the GPIO test interface</li>~~</ol>~~ ~~[[File:pi3b-img365.png|286x180px]]~~

[[File:pi3b-img419.png]]

</ol>

<li>~~Then click~~ The GPIO test interface is shown in the figure below. The two rows of '''~~Apply~~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-img366.png|330x207px]]~~

[[File:pi3b-img420.png]]

</ol>

<li>Then ~~select~~ click the '''~~Keep this configuration~~GPIO READALL'''button, the output information is as shown in the figure below:</li>~~</ol>~~ ~~[[File:pi3b-img367.png|374x210px]]~~

[[File:pi3b-img421.png]]

</ol>

<li>~~At this point,~~ There are a total of 28 GPIO ports in the ~~screen display has been rotated, and then close~~ 40pins of the ~~'''Display''' program</li><li>~~development board that can be used. The ~~above steps will only select~~ 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 ~~display direction,~~ high and ~~will not rotate the direction~~ low levels of the ~~touch~~GPIO port. ~~Use~~ First click the '''~~set_lcd_rotate.sh~~CheckBox''' ~~script~~ button corresponding to ~~rotate the direction of the touch~~pin 7. ~~After~~ When the ~~script~~ button is ~~set~~selected, it pin 7 will ~~automatically restart~~be set to high level. After setting, ~~and then~~ you can ~~test whether~~ use a multimeter to measure the voltage value of the ~~touch has been used normally~~pin. If it is 3.3v, it means setting high level success~~<ol style="list-style-type: lower-alpha;">~~<li~~>'''None''': no rotation</li></ol></li></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img422.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then click the '''~~set_lcd_rotate.sh none~~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="27" style="list-style-type: ~~lower-alpha~~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 '''~~Left~~0v'''~~: rotate left 90 degrees~~, it means that the low level is set successfully.</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img424.png]]</ol><ol start="8" style="list-style-type: decimal;"><li>Then click the '''~~set_lcd_rotate.sh left~~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 ~~start~~>~~<li>'''Inverted''': Flip up and down, which is equivalent to rotating 180 degrees~~</~~li></ol~~span>

~~orangepi@orangepi:~$ '''set_lcd_rotate.sh inverted'''~~=== 40pin UART test ===

~~<ol start="4" style="list-style-type: lower-alpha;"><li>~~# 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 '''~~Right~~/dev/ttyS7''' and '''~~: rotate right 90 degrees<~~/~~li><~~dev/~~ol>~~ttyS9''' respectively

~~orangepi@orangepi~~:~~~$ '''set_lcd_rotate~~:[[File:pi3b-img269.~~sh right'''~~png]]

~~'''The set_lcd_rotate.sh script mainly does four things~~<ol start="2" style="list-style-type:~~'''~~decimal;"><li>First click on the wiringOP icon to open the wiringOP APP</li>

[[File:pi3b-img418.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>The main interface of wiringOP APP is displayed as shown in the figure below, and then click the '''~~1. Rotate the direction displayed by the framebuffer~~UART_TEST'''button to open the UART test interface</li>

~~'''2~~[[File:pi3b-img426. ~~Rotate~~ png]]</ol><ol start="4" style="list-style-type: decimal;"><li>The serial port test interface of the ~~direction of~~ APP is shown in the ~~touch'''~~figure below</li>

[[File:pi3b-img427.png]]</ol><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''3' button to open the /dev/ttyS7 node. ~~Turn off~~ After the opening is successful, the '''OPEN''' button becomes unselectable, and the ~~boot logo~~'''CLOSE''' button and '''SEND''' button become selectable</li>

~~'''4~~[[File:pi3b-img428. ~~Restart the system'''~~png]]</ol>~~'''Rotating the touch direction is achieved by adding the line Option "TransformationMatrix" "x x x x x x x x x&quot~~<ol start="6" style="list-style-type: decimal; "><li>Then use Dupont wire to short the RXD and TXD pins of uart7</~~usr/share/X11/xorg.conf.d/40-libinput.conf Where "x x x x x x x x x" is configured differently for different directions.'''~~li>

[[File:pi3b-img429.png]]

</ol>

<li>~~Touch rotation reference~~Then you can enter a character in the send edit box below, and click the '''SEND''' button to start sending</li~~></ol~~>

~~https~~[[File:~~//wiki.ubuntu~~pi3b-img430.~~com~~png]]</Xol><ol start="8" style="list-style-type: decimal;"><li>If everything is normal, the received string will be displayed in the receiving box</~~InputCoordinateTransformation~~li>

[[File:pi3b-img431.png]]</ol>~~== Instructions for using the switch logo ==~~

~~# By default, the switch logo will only be displayed in the desktop version of the system# Set the '''bootlogo''' variable to '''false''' in '''/boot/orangepiEnv.txt''' to turn off the switch logo~~=== 40pin SPI test ===

~~orangepi@orangepi:~$ '''vim /boot/orangepiEnv.txt'''~~# According to the schematic diagram of the 40pin interface, the spi available for Orange Pi 3B is spi3

~~verbosity=1~~::[[File:pi3b-img264.png]]

~~'''bootlogo~~<ol start=~~false'''~~"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>

[[File:pi3b-img432.png]]

</ol>

<li>~~Set~~ Then click the ~~'''bootlogo''' variable~~ wiringOP icon to ~~'''true''' in '''/boot/orangepiEnv.txt''' to enable~~ open the ~~switch logo~~wiringOP APP</li>~~</ol>~~ ~~orangepi@orangepi:~$ '''vim /boot/orangepiEnv.txt'''~~ ~~verbosity=1~~ ~~'''bootlogo=true'''~~

[[File:pi3b-img418.png]]

</ol>

<li>The ~~location~~ main interface of wiringOP APP is displayed as shown in the figure below, click the ~~boot logo image in~~ SPI_TEST button to open the ~~Linux system is~~SPI test interface</li>~~</ol>~~ ~~'''/usr/share/plymouth/themes/orangepi/watermark.png'''~~

[[File:pi3b-img433.png]]

</ol>

<li>~~After replacing~~ Then click the ~~boot logo picture, you need~~ '''OPEN''' button to ~~run~~ initialize the ~~following command to take effect~~SPI</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img434.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then fill in the bytes that need to be sent, such as reading the ID information of w25q64, fill in the address 0x9f in data[0], and then click the '''~~sudo update-initramfs -u~~TRANSFER'''button</li>

[[File:pi3b-img435.png]]<~~span id~~/ol><ol start="~~how-to-use~~7" style="list-~~the~~style-~~zfs-file-system~~type: decimal;"><li>Finally, the APP will display the read ID information</~~span~~li>~~== How to use the ZFS file system ==~~

~~'''~~[[File:pi3b-img436.png]]</ol><ol start="8" style="list-style-type: decimal;"><li>The ~~latest version~~ MANUFACTURER ID of ~~Ubuntu20.04~~the w25q64 module is EFh, ~~Ubuntu22.04, Debian11~~ and ~~Debian12 desktop version systems have pre-installed zfs~~the Device ID is 4017h, ~~you can use it directly.'''~~corresponding to the value read above (h stands for hexadecimal)</li>

~~'''The pre~~[[File:pi3b-~~installed zfs version in Ubuntu20~~img437.~~04 and Ubuntu22.04 desktop systems is 2.1.6.'''~~png]]</ol>

~~'''The pre-installed zfs version in Debian11 and Debian12 desktop systems is 2.1.11.'''~~=== 40pin PWM test ===

# Android enables '''~~After the system starts~~PWM11''' by default, ~~please first confirm whether~~ and the ~~zfs kernel module has been loaded. If you can see zfs-related content using~~ corresponding pin is located at 40pin as shown in the ~~lsmod command, it means that the system has pre-installed zfs.'''~~figure below

~~orangepi@orangepi~~:~~~$ '''lsmod | grep "zfs"'''~~:[[File:pi3b-img438.png]]

~~zfs 2801664 0~~<ol start="2" style="list-style-type: decimal;"><li>First click on the wiringOP icon to open the wiringOP APP</li>

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

~~zzstd 471040 1 zfs~~[[File: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>

~~zlua 139264 1 zfs~~[[File:pi3b-img440.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>

~~zcommon 69632 1 zfs~~[[File:pi3b-img441.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then confirm the PWM channel, the default is channel 0, and confirm the PWM cycle, the default configuration is '''50000ns''', converted to PWM frequency is '''20KHz''', you can modify it yourself, click the '''EXPORT''' button to export '''PWM11'''</li>

~~znvpair 61440 2 zfs~~[[File: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,~~zcommon~~and then check Enable to output the PWM waveform</li>

~~zavl 16384 1 zfs~~[[File:pi3b-img443.png]]</ol><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>

~~icp 221184 1 zfs~~[[File:pi3b-img444.png]]</ol>

~~spl 77824 6 zfs,icp,zzstd,znvpair,zcommon,zavl~~== How to use ADB ==

=== ~~How to install ZFS~~ Use network connection adb debugging ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~Before installing zfs~~Using the network adb does not require a data cable to connect the computer and the development board, but to communicate through the network, ~~please~~ so first make sure that the ~~Linux image used~~ wired or wireless network of the development board is connected, and then obtain the ~~latest version. In addition, if zfs is already installed in~~ IP address of the ~~system~~development board, ~~it needs to~~ which will be ~~installed again~~used later.'''</big>|}

~~Before installing zfs, you need to install~~ # Make sure that the ~~kernel header file first~~'''service. ~~For the method of installing the kernel header file, please refer to the instructions in the [[\l|~~adb.tcp.port'''~~section on the method~~ of ~~installing~~ the ~~kernel header file''']].~~Android system is set to port number 5555

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::{| class="wikitable" style="width:800px;" |-| console:/ # '''getprop | grep "adb.tcp"'''

~~To solve this problem, we provide a zfs deb package that can be installed normally, which can be downloaded from the~~ [~~http://www~~service.~~orangepi~~adb.~~org/html/serviceAndSupport/index~~tcp.~~html~~ port]: ['''~~official tool~~5555'''] of the development board. Open the '''official tool''', and enter the '''zfs-related deb package folders used by Ubuntu and Debian systems'''. You can see three types of deb packages: Ubuntu20.04, Ubuntu22.04 and Debian11. Please download the required version.|}

~~[[File~~<ol start="2" style="list-style-type:~~pi3b-img368~~decimal;"><li>If '''service.adb.tcp.~~png|230x93px]]~~port''' is not set, you can use the following command to set the port number of network adb</li>

~~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~~ {| class="wikitable" style="width:800px;" |-| console:/ # '''~~[[\l|the description in the section of the method of uploading files to the Linux system of the development board]]~~setprop service.adb.tcp.port 5555'''

~~After the upload is complete, use the~~ console:/ # '''cdstop adbd''' ~~command in the command line of the development board Linux system to enter the directory of the deb package, and then use the following command to install the deb package of zfs.~~

~~orangepi@orangepi~~console:~$ / # '''~~sudo apt install ./*.deb~~start adbd'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Install adb tool on Ubuntu PC</li>

~~After the installation is complete, use the following command to see the zfs~~{| class="wikitable" style="width:800px;" |-~~related kernel modules~~| test@test:~$ '''sudo apt update'''

~~orangepi~~test@~~orangepi~~test:~$ '''~~ls /lib/modules~~sudo apt install -y adb'''|}</~~5.10.160~~ol><ol start="4" style="list-~~rockchip~~style-~~rk356x/updates/dkms~~type: decimal;"><li>Then connect network adb on Ubuntu PC</~~'''~~li>

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''~~icp~~adb connect 192.~~ko spl~~168.~~ko zavl~~1.~~ko zcommon.ko zfs.ko zlua.ko znvpair.ko zunicode.ko zzstd.ko~~xxx''' '''(The IP address needs to be changed to the IP address of the development board)'''

~~Then restart the Linux system to see that the zfs kernel module will be automatically loaded~~* daemon not running; starting now at tcp:5037

~~orangepi@orangepi:~$ '''lsmod | grep "zfs"'''~~* daemon started successfully

~~zfs 2801664 0~~connected to 192.168.1.xxx:5555

~~zunicode 327680 1 zfs~~

~~zzstd 471040 1 zfs~~test@test:~$ '''adb devices'''

~~zlua 139264 1 zfs~~List of devices attached

~~zcommon 69632~~ 192.168.1 ~~zfs~~.xxx:5555 device|}</ol><ol start="5" style="list-style-type: decimal;"><li>Then you can log in to the android system through the adb shell on the Ubuntu PC</li>

~~znvpair 61440 2 zfs,zcommon~~{| class="wikitable" style="width:800px;" |-| test@test:~$ '''adb shell'''

~~zavl 16384 1 zfs~~console:/ #|}</ol>

~~icp 221184 1 zfs~~= '''Appendix''' =

~~spl 77824 6 zfs,icp,zzstd,znvpair,zcommon,zavl~~== User Manual Update History ==

In Debian12, the default version of zfs is 2.1.11, so we can install zfs directly through the following command. Again, please make sure that the system has installed the deb package of the kernel header file before installation. ~~orangepi@orangepi:~$ '''sudo apt install -y zfsutils-linux zfs-dkms'''~~ ~~=== Methods of creating ZFS pools ===~~ ~~'''ZFS is based on storage pools, we can add multiple physical storage devices to the pool, and then allocate storage space from this pool.'''~~ ~~'''The following content is demonstrated based on the development board connected to an NVMe SSD and a USB flash drive.'''~~ ~~# First, we can use the '''lsblk''' command to view all storage devices on the development board. The current development board is connected to an NVMe SSD and a U disk. The output is as follows:~~ ~~[[File:pi3b-img369.png|379x227px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Then enter the following command to create a ZFS pool, including two storage devices, NVMe SSD and U disk</li></ol>~~ ~~orangepi@orangepi:~$ '''sudo zpool create -f pool1 /dev/nvme0n1 /dev/sda'''~~ ~~<ol start="3" style="list-style-type: decimal;">~~<li>Then use the '''zpool list''' command to see that the system has created a ZFS pool named '''pool1''', and the size of the ZFS pool pool1 is the size of the NVME SSD plus the size of the U disk</li></ol> ~~[[File:pi3b-img370.png|576x37px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then execute '''df -h''' to see that '''pool1''' is mounted to the '''/pool1''' directory</li></ol>~~ ~~orangepi@orangepi:~$ '''df -h'''~~ ~~Filesystem Size Used Avail Use% Mounted on~~ ~~tmpfs 1.6G 18M 1.6G 2% /run~~ ~~/dev/mmcblk0p2 29G 6.0G 22G 22% /~~ ~~tmpfs 7.7G 46M 7.7G 1% /dev/shm~~ ~~tmpfs 5.0M 4.0K 5.0M 1% /run/lock~~ ~~tmpfs 7.7G 944K 7.7G 1% /tmp~~ ~~/dev/mmcblk0p1 1022M 115M 908M 12% /boot~~ ~~/dev/zram1 188M 4.5M 169M 3% /var/log~~ ~~tmpfs 1.6G 80K 1.6G 1% /run/user/1000~~ ~~'''pool1 489G 9.3M 489G 1% /pool1'''~~ ~~<ol start="5" style="list-style-type: decimal;"><li>Use the following command to see that the file system type of pool1 is zfs</li></ol>~~ ~~orangepi@orangepi:~$ '''mount | grep pool1'''~~ ~~pool1 on /pool1 type '''zfs''' (rw,xattr,noacl)~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Then we can test copying a file to the ZFS pool</li></ol>~~ ~~orangepi@orangepi:~$ '''sudo cp -v /usr/local/test.mp4 /pool1/'''~~ ~~'/usr/local/test.mp4' -> '/pool1/test.mp4'~~ ~~=== Test the data deduplication function of ZFS ===~~ ~~# The data deduplication function of ZFS is disabled by default, we need to execute the following command to enable it~~ ~~orangepi@orangepi:~$ '''sudo zfs set dedup=on pool1'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Then do a simple test, first enter pool1, and then execute the following command to generate a random file with a size of 1G</li></ol>~~ ~~orangepi@orangepi:~$ '''cd /pool1/'''~~ ~~root@orangepi:/pool1$ '''sudo dd if=/dev/urandom of=test.1g bs=1M count=1024'''~~ ~~1024+0 records in~~ ~~1024+0 records out~~ ~~1073741824 bytes (1.1 GB, 1.0 GiB) copied, 5.04367 s, 213 MB/s~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then use the following command to copy 1000 random files of size 1G</li></ol>~~ ~~root@orangepi:/pool1$ '''for ((i=0; i<1000; i++)); do sudo cp test.1g $i.test.1g; done'''~~ ~~<ol start="4" style="list-style-type: decimal;">~~<li>Then use '''du -lh''' to see that there are currently 1002G of data in the pool, but in fact the size of the ZFS pool is only '''504GB''' (the total capacity of SSD+U disk), which cannot hold such a large amount of data</li></ol> ~~root@orangepi:/pool1$ '''du -lh'''~~ ~~1002G~~ ~~<ol start="5" style="list-style-type: decimal;">~~<li>Then use the '''zpool list''' command to see that only 1.01G is actually occupied, because these 1001 files are all duplicates, indicating that the data deduplication function is effective.</li></ol> ~~[[File:pi3b-img371.png|576x36px]]~~ ~~=== Test the data compression function of ZFS ===~~ # Because the stored data is different, the disk space saved by compression will also be different, so we choose to compress relatively large plain text files for compression testing, and execute the following commands to pack the '''/var/log/''' and '''/etc/''' directories into a tarball ~~orangepi@orangepi:~$ '''cd /pool1/'''~~ ~~root@orangepi:/pool1$ '''sudo tar -cf text.tar /var/log/ /etc/'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Then the file size that can be seen through the '''ls -lh''' command and the space occupied in the ZFS pool are both '''27M'''</li></ol>~~ ~~[[File:pi3b-img372.png|576x90px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then we enable compression in the ZFS pool pool1</li></ol>~~ ~~root@orangepi:/pool1$ '''sudo zfs set compression=lz4 pool1'''~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then execute the following command again to package the '''/var/log/''' and '''/etc/''' directories into a tar package</li></ol>~~ ~~root@orangepi:/pool1$ '''sudo tar -cf text.tar /var/log/ /etc/'''~~ ~~<ol start="5" style="list-style-type: decimal;"><li>At this time, you can see that the size of the '''text.tar''' file is still 27M, but it only occupies 9.47M in the ZFS pool, indicating that the file is compressed</li></ol>~~ ~~[[File:pi3b-img373.png|576x79px]]~~ ~~== How to shut down and restart the development board ==~~ # During the running of the Linux system, if the Type-C power supply is directly unplugged, some data may be lost or damaged in the file system, so please use the '''poweroff''' command to shut down the Linux system of the development board before powering off. Then unplug the power again. ~~orangepi@orangepi:~$ '''sudo poweroff'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>In addition, the development board is equipped with a switch button, and you can also '''short press''' the switch button on the development board to shut down.</li></ol>~~ ~~[[File:pi3b-img374.png|294x80px]]~~ '''Note that the Linux desktop version system will pop up a confirmation box as shown in the figure below after pressing the switch button, and the system will shut down only after clicking the Shut Down option.''' ~~[[File:pi3b-img375.png|207x193px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Short press the switch button on the development board after shutting down to start up.</li></ol>~~ ~~[[File:pi3b-img374.png|294x80px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>The command to restart the Linux system is</li></ol>~~ ~~orangepi@orangepi:~$ '''sudo''' '''reboot'''~~ ~~~~ ~~= '''Linux SDK——orangepi-build instructions''' =~~ ~~== Compilation system requirements ==~~ '''We can cross-compile the Linux image of the development board on the x64 computer, or compile the Linux image of the development board on the Ubuntu22.04 system of the development board, please choose one according to your preference.''' '''If you use orangepi-build to compile the Linux image in the Ubuntu22.04 system of the development board, please do a good job of cooling (especially when the SSD starts). If the heat dissipation is not done well, it is prone to the error of file system runaway.''' ~~=== Compile with the Ubuntu22.04 system of the development board ===~~ # The Linux SDK, namely '''orangepi-build''', supports running on the '''Ubuntu 22.04''' of the development board (other systems have not been tested), so before downloading orangepi-build, please first ensure that the Ubuntu version installed on the development board is Ubuntu 22.04. The command to check the Ubuntu version installed on the development board is as follows. If the Release field does not display '''22.04''', it means that the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operations. ~~orangepi@orangepi:~$ '''lsb_release -a'''~~ ~~No LSB modules are available.~~ ~~Distributor ID: Ubuntu~~ ~~Description: Ubuntu 22.04.1 LTS~~ ~~Release: '''22.04'''~~ ~~Codename: jammy~~ ~~<ol start="2" style="list-style-type: decimal;">~~<li>'''Since the source codes such as the kernel and U-boot are stored on GitHub, it is very important to ensure that the development board can download codes from GitHub normally when compiling the image.'''</li></ol> ~~=== Compile with x64 Ubuntu22.04 computer ===~~ # The Linux SDK, '''orangepi-build''', supports running on computers with '''Ubuntu 22.04''' installed, so before downloading orangepi-build, please make sure that the Ubuntu version installed on your computer is Ubuntu 22.04. The command to check the Ubuntu version installed on the computer is as follows. If the Release field does not display '''22.04''', it means that the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operations. ~~test@test:~$ '''lsb_release -a'''~~ ~~No LSB modules are available.~~ ~~Distributor ID: Ubuntu~~ ~~Description: Ubuntu 22.04 LTS~~ ~~Release: '''22.04'''~~ ~~Codename: jammy~~ ~~<ol start="2" style="list-style-type: decimal;">~~<li>If the computer is installed with Windows system and there is no computer with Ubuntu 22.04 installed, you can consider using '''VirtualBox''' or '''VMware''' to install an Ubuntu 22.04 virtual machine in the Windows system. But please be careful not to compile orangepi-build on the WSL virtual machine, because orangepi-build has not been tested in the WSL virtual machine, so it cannot be guaranteed that orangepi-build can be used normally in WSL.</li>~~<li>The download address of the installation image of Ubuntu 22.04 '''amd64''' version is:</li></ol>~~ ~~[https://repo.huaweicloud.com/ubuntu-releases/21.04/ubuntu-21.04-desktop-amd64.iso '''https://mirrors.tuna.tsinghua.edu.cn/ubuntu-releases/22.04/ubuntu-22.04-desktop-amd64.iso''']~~ Or ~~'''https://repo.huaweicloud.com/ubuntu-releases/22.04/ubuntu-22.04.1-desktop-amd64.iso'''~~ ~~<ol start="4" style="list-style-type: decimal;">~~<li>After installing Ubuntu 22.04 on the computer or virtual machine, please set the software source of Ubuntu 22.04 to Tsinghua source, otherwise it is easy to make mistakes due to network reasons when installing the software later~~<ol style="list-style-type: lower-alpha;"><li>For the method of replacing Tsinghua source, please refer to the instructions on this web page</li></ol></li></ol>~~ ~~https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>Note that the Ubuntu version needs to be switched to 22.04</li></ol>~~ ~~[[File:pi3b-img376.png|576x241px]]~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>The content of the '''/etc/apt/sources.list''' file that needs to be replaced is</li></ol>~~ ~~test@test:~$ '''sudo mv /etc/apt/sources.list /etc/apt/sources.list.bak'''~~ ~~test@test:~$ '''sudo vim /etc/apt/sources.list'''~~ ~~# By default, the source image is commented to improve the speed of apt update, you can uncomment it yourself if necessary~~ ~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse~~ ~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse~~ ~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse~~ ~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse~~ ~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse~~ ~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse~~ ~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-security main restricted universe multiverse~~ ~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-security main restricted universe multiverse~~ ~~# Pre-release software source, not recommended to enable~~ ~~# deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse~~ ~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>After the replacement, you need to update the package information and make sure there is no error</li></ol>~~ ~~test@test:~$ '''sudo apt update'''~~ ~~<ol start="5" style="list-style-type: lower-alpha;">~~<li>'''In addition, since the source codes such as the kernel and U-boot are stored on GitHub, it is very important to ensure that the computer can download codes from GitHub normally when compiling the image.'''</li></ol> ~~== Get the source code of Linux sdk ==~~ ~~=== Download orangepi-build from github ===~~ # The Linux sdk actually refers to the code of orangepi-build. orangepi-build is modified based on the armbian build system. Using orangepi-build, multiple versions of Linux images can be compiled. First download the code of orangepi-build, the command is as follows: ~~test@test:~$ '''sudo apt-get update'''~~ ~~test@test:~$ '''sudo apt-get install -y git'''~~ ~~test@test:~$ '''git clone https://github.com/orangepi-xunlong/orangepi-build.git -b next'''~~ '''Note that the Orange Pi 3B development board needs to download the source code of the next branch of orangepi-build. The above git clone command needs to specify the branch of the orangepi-build source code as next.''' ~~<div class="figure">~~ ~~[[File:pi3b-img377.png|576x298px|图片6]]~~ ~~</div>~~'''Downloading the orangepi-build code through the git clone command does not require entering the user name and password of the github account (the same is true for downloading other codes in this manual), if the Ubuntu PC prompts the user to enter the github account after entering the git clone command The name and password are usually entered incorrectly in the address of the orangepi-build warehouse behind the git clone. Please check the spelling of the command carefully, instead of thinking that we forgot to provide the username and password of the github account.''' ~~<ol start="2" style="list-style-type: decimal;"><li>The u-boot and Linux kernel versions currently used by the development board are as follows</li></ol>~~ {| class="wikitable"|-~~| style="text-align: left;"| '''branch'''~~| style="~~text-align~~width: ~~left~~800px;~~"| '''u-boot version'''| style="~~text-align: ~~left~~center;"~~| '''Linux Kernel version'''~~|-| ~~style="text-align: left;"| '''legacy'''| style="text-align: left;"|~~ '''~~u-boot 2017.09~~Version'''| ~~style="text-align: left;"| '''Linux5.10'''~~|} '''The branch mentioned here is not the same thing as the branch of the orangepi-build source code, please do not confuse it. This branch is mainly used to distinguish different kernel source code versions.''' ~~'''Currently, the Linux5.10 bsp kernel provided by RK is defined as the legacy branch. If the mainline kernel is supported in the future, a current branch will be added.'''~~ ~~<ol start="3" style="list-style-type: decimal;"><li>orangepi-build will contain the following files and folders after downloading<ol style="list-style-type: lower-alpha;"><li>'''build.sh''': Compile the startup script</li><li>'''external''': Contains the configuration files needed to compile the image, specific scripts, and the source code of some programs, etc.</li><li>'''LICENSE''': GPL 2 license file</li><li>README.md: orangepi-build documentation</li><li>'''scripts''': General script for compiling Linux images</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''ls'''~~ ~~'''build.sh external LICENSE''' README.md '''scripts'''~~ '''If you downloaded the code of orangepi-build from github, after downloading, you may find that orangepi-build does not contain the source code of u-boot and Linux kernel, nor does u-boot and Linux kernel need to use cross-compilation tools Chain, this is normal, because these things are stored in other separate github warehouses or some servers (the addresses will be detailed below). orangepi-build will specify the address of u-boot, Linux kernel and cross-compilation toolchain in the script and configuration file. When running orangepi-build, when it finds that there are no such things locally, it will automatically go to the corresponding place to download them.''' ~~=== Download the cross-compilation toolchain ===~~ '''The cross-compilation toolchain will only be downloaded when the orangepi-build compilation image is used on an x64 computer. Compiling the Linux image of the development board in the Ubuntu22.04 of the development board will not download the cross-compilation toolchain. At this time, orangepi-build/toolchains will be an empty folder.''' # When orangepi-build runs for the first time, it will automatically download the cross-compilation toolchain and put it in the '''toolchains''' folder. Every time after running the build.sh script of orangepi-build, it will check whether the cross-compilation toolchain in '''toolchains''' exists , if it does not exist, the download will be restarted, if it exists, it will be used directly, and the download will not be repeated. ~~<div class="figure">~~ ~~[[File:pi3b-img378.png|575x278px|选区_396]]~~ ~~</div><ol start="2" style="list-style-type: decimal;"><li>The image URL of the cross-compilation toolchain in China is the open source software image site of Tsinghua University</li></ol>~~ ~~https://mirrors.tuna.tsinghua.edu.cn/armbian-releases/_toolchain/~~ ~~<ol start="3" style="list-style-type: decimal;"><li>After '''toolchains''' is downloaded, it will contain multiple versions of cross-compilation toolchains, and the development board will only use two of them</li></ol>~~ ~~test@test:~/orangepi-build$ '''ls toolchains/'''~~ ~~gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu~~ ~~gcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf~~ ~~gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu~~ ~~gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf~~ ~~gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabi~~ ~~gcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabihf~~ ~~gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu~~ ~~gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabi~~ ~~gcc-linaro-aarch64-none-elf-4.8-2013.11_linux~~ ~~gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux~~ ~~gcc-linaro-arm-none-eabi-4.8-2014.04_linux~~ ~~<ol start="4" style="list-style-type: decimal;"><li>The cross-compilation toolchain used to compile the Linux kernel source code is<ol style="list-style-type: lower-alpha;"><li>Linux5.10</li></ol></li></ol>~~ ~~'''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''~~ ~~<ol start="5" style="list-style-type: decimal;"><li>The cross-compilation tool chain used to compile the u-boot source code is<ol style="list-style-type: lower-alpha;"><li>v2017.09</li></ol></li></ol>~~ ~~'''gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu'''~~ ~~=== orangepi-build complete directory structure description ===~~ ~~<ol style="list-style-type: decimal;">~~<li>The orangepi-build repository does not contain the source code of the Linux kernel, u-boot, and cross-compilation toolchain after downloading. The source code of the Linux kernel and u-boot is stored in an independent git repository~~<ol style="list-style-type: lower-alpha;"><li>The git repository where the Linux kernel source code is stored is as follows:</li></ol></li></ol>~~ ~~'''https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-5.10-rk35xx'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The git warehouse where the b.u-boot source code is stored is as follows:</li></ol>~~ ~~'''https://github.com/orangepi-xunlong/u-boot-orangepi/tree/v2017.09-rk3588'''~~ ~~<ol start="2" style="list-style-type: decimal;">~~<li>When orangepi-build runs for the first time, it will download the cross-compilation toolchain, u-boot and Linux kernel source code. After successfully compiling a Linux image, the files and folders that can be seen in orangepi-build are:~~a. '''build.sh''': compile startup script~~b. '''external''': Contains the configuration files needed to compile the image, scripts with specific functions, and the source code of some programs. The rootfs compressed package cached during the image compilation process is also stored in externalc. '''kernel''': stores the source code of the Linux kernel, and the folder named orange-pi-5.10-rk35xx stores the kernel source code of the legacy branch of the RK3588/RK3588S/RK3566 series development boards. Please do not manually name the folder name of the kernel source code Modify, if modified, the kernel source code will be re-downloaded when the compilation system is running~~d. '''LICENSE''': GPL 2 license filee. '''README'''.md: orangepi-build documentationf. '''output''': Store compiled deb packages such as u-boot and Linux, compilation logs, and compiled images and other filesg. '''scripts''': general scripts for compiling Linux imagesh.~~ '''~~toolchains~~Date'''~~: store cross-compilation toolchain~~i. '''u-boot''': stores the source code of u-boot, the folder named v2017.09-rk3588 stores the u-boot source code of the legacy branch of the RK3588/RK3588S/RK3566 series development boards, the name of the folder of the u-boot source code Please do not modify it manually, if it is modified, the u-boot source code will be re-downloaded when the compiling system is running~~j. '''userpatches''': Store configuration files needed to compile scripts</li></ol>~~ ~~test@test:~/orangepi-build$ '''ls'''~~ ~~'''build.sh external kernel LICENSE output''' README.md '''scripts toolchains u-boot userpatches'''~~ ~~== Compile u-boot ==~~ ~~# Run the build.sh script, remember to add sudo permission~~ ~~test@test:~/orangepi-build$ '''sudo ./build.sh'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Select '''U-boot package'''，then enter</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img379.png|576x132px~~|~~选区_238]]~~ ~~</div><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img380.png|576x197px|}4$_5F06}}0R4GU8]OVO}4E]]~~ ~~</div><ol start="4" style="list-style-type: decimal;"><li>Then it will start to compile u-boot, and some information prompted during compilation is explained as follows<ol style="list-style-type: lower-alpha;"><li>u-boot source code version</li></ol></li></ol>~~ ~~[ o.k. ] Compiling u-boot [ '''v2017.09''' ]~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The version of the cross-compilation toolchain</li></ol>~~ ~~[ o.k. ] Compiler version [ '''aarch64-linux-gnu-gcc 7.4.1''' ]~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>Path to the generated u-boot deb package</li></ol>~~ ~~[ o.k. ] Target directory [ '''orangepi-build/output/debs/u-boot''' ]~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>The package name of the generated u-boot deb package</li></ol>~~ ~~[ o.k. ] File name [ '''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb''' ]~~ ~~<ol start="5" style="list-style-type: lower-alpha;"><li>Compilation time</li></ol>~~ ~~[ o.k. ] Runtime [ '''1 min''' ]~~ ~~<ol start="6" style="list-style-type: lower-alpha;"><li>Repeat the command to compile u-boot, use the following command to start compiling u-boot directly without selecting through the graphical interface</li></ol>~~ ~~[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=u-boot KERNEL_CONFIGURE=no''' ]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>View the u-boot deb package generated by compilation</li></ol>~~ ~~test@test:~/orangepi-build$ '''ls output/debs/u-boot/'''~~ ~~linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb~~ ~~<ol start="6" style="list-style-type: decimal;"><li>The files contained in the generated u-boot deb package are as follows<ol style="list-style-type: lower-alpha;"><li>Use the following command to decompress the deb package</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''cd output/debs/u-boot'''~~ ~~test@test:~/orangepi_build/output/debs/u-boot$ $ '''dpkg -x''' \~~ ~~'''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb . (Note that there is a "." at the end of the command)'''~~ ~~test@test:~/orangepi_build/output/debs/u-boot$ '''ls'''~~ ~~linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb '''usr'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The decompressed file is as follows</li></ol>~~ ~~test@test:~/orangepi-build/output/debs/u-boot$ '''tree usr'''~~ ~~usr~~ ~~└── lib~~ ~~├── linux-u-boot-legacy-orangepi3b_1.0.0_arm64~~ ~~│ ├── idbloader.img~~ ~~│ ├── rkspi_loader.img~~ ~~│ └── u-boot.itb~~ ~~└── u-boot~~ ~~├── LICENSE~~ ~~├── orangepi-3b-rk3566_defconfig~~ ~~└── platform_install.sh~~ ~~3 directories, 6 files~~ ~~<ol start="7" style="list-style-type: decimal;">~~<li>When the orangepi-bulid compilation system compiles the u-boot source code, it will first synchronize the u-boot source code with the u-boot source code of the github server, so if you want to modify the u-boot source code, you first need to turn off the download and update function of the source code '''(This function needs to be fully compiled once u-boot, otherwise it will prompt that the source code of u-boot cannot be found. If the source code compressed package is downloaded from Google cloud disk, there is no such problem, because the source code of u-boot have been cached)''', otherwise the changes made will be reverted, the method is as follows:</li></ol> ~~<blockquote>Set the IGNORE_UPDATES variable in userpatches/config-default.conf to "yes"</blockquote>test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''~~ ~~IGNORE_UPDATES="'''yes'''"~~ ~~<ol start="8" style="list-style-type: decimal;"><li>When debugging u-boot code, you can use the following method to update u-boot in the Linux image for testing<ol style="list-style-type: lower-alpha;"><li>Upload the compiled u-boot deb package to the Linux system of the development board</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''cd output/debs/u-boot'''~~ ~~test@test:~/orangepi_build/output/debs/u-boot$ '''scp \'''~~ ~~'''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb''' [mailto:root@192.168.1.xxx:/root root@192.168.1.xxx:/root]~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>Then log in to the development board and uninstall the deb package of u-boot installed</li></ol>~~ ~~root@orangepi:~# '''apt purge -y linux-u-boot-orangepi3b-legacy'''~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>Install the new u-boot deb package just uploaded</li></ol>~~ ~~root@orangepi:~# '''dpkg -i''' '''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb'''~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>Then run the nand-sata-install script</li></ol>~~ ~~root@orangepi:~# '''nand-sata-install'''~~ ~~<ol start="5" style="list-style-type: lower-alpha;"><li>Then select '''5 Install/~~Update ~~the bootloader on SD/eMM''' to update the u-boot in the TF card or '''7 Install/Update the bootloader on SPI Flash''' to update the u-boot in the SPI Flash</li></ol>~~ ~~[[File:pi3b-img381.png|312x152px]]~~ ~~<ol start="6" style="list-style-type: lower-alpha;"><li>After pressing the Enter key, a Warning will pop up first</li></ol>~~ ~~[[File:pi3b-img382.png|309x168px]]~~ ~~<ol start="7" style="list-style-type: lower-alpha;"><li>Press the Enter key again to start updating u-boot, and the following information will be displayed after the update is completed</li></ol>~~ ~~[[File:pi3b-img383.png|244x137px]]~~ ~~<ol start="8" style="list-style-type: lower-alpha;"><li>Then you can restart the development board to test whether the modification of u-boot takes effect</li></ol>~~ ~~<ol start="9" style="list-style-type: decimal;"><li>Other useful information<ol style="list-style-type: lower-alpha;"><li>In the u-boot 2017.09 source code, the defconfig configuration file used by the development board is</li></ol></li></ol>~~ ~~[https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/configs/orangepi_5_defconfig '''orangepi-build/u-boot/v2017.09-rk3588/configs/orangepi-3b-rk3566_defconfig''']~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>In the u-boot 2017.09 source code, the dts file used by the development board is</li></ol>~~ ~~[https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/arch/arm/dts/rk3588s-orangepi-5.dts orangepi-build/u-boot/v2017.09-rk3588/arch/arm/dts/rk3566-orangepi-3b.dts]~~ ~~== Compile the Linux kernel ==~~ ~~# Run the build.sh script, remember to add sudo permission~~ ~~test@test:~/orangepi-build$ '''sudo ./build.sh'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Select '''Kernel package'''，then enter</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img384.png|575x116px|选区_240]]~~ ~~</div><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img380.png|576x197px|}4$_5F06}}0R4GU8]OVO}4E]]~~ ~~</div><ol start="4" style="list-style-type: decimal;">~~<li>Then it will prompt whether to display the kernel configuration interface. If you do not need to modify the kernel configuration, select the first one. If you need to modify the kernel configuration, select the second one.</li></ol> ~~[[File:pi3b-img385.png|576x87px]]~~ ~~<ol start="5" style="list-style-type: decimal;">~~<li>If you choose to display the kernel configuration menu (the second option) in step 4), the kernel configuration interface opened by '''make menuconfig''' will pop up. At this time, you can directly modify the kernel configuration, save and exit after modification. Yes, after exiting, the kernel source code will be compiled</li></ol> ~~[[File:pi3b-img386.png|462x322px]]~~ ~~<ol style="list-style-type: lower-alpha;">~~<li>If you do not need to modify the configuration options of the kernel, when running the build.sh script, pass in '''KERNEL_CONFIGURE=no''' to temporarily block the pop-up kernel configuration interface</li></ol> ~~test@test:~/orangepi-build$ '''sudo ./build.sh KERNEL_CONFIGURE=no'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>You can also set '''KERNEL_CONFIGURE=no''' in the '''orangepi-build/userpatches/config-default.conf''' configuration file, which can permanently disable this function</li>~~<li>If the following error is displayed when compiling the kernel, it is because the terminal interface of the Ubuntu PC is too small to display the '''make menuconfig''' interface. Please maximize the terminal of the Ubuntu PC and run the build.sh script again</li></ol> ~~[[File:pi3b-img387.png|574x234px]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Part of the information prompted when compiling the kernel source code is as follows<ol style="list-style-type: lower-alpha;"><li>The version of the Linux kernel source code</li></ol></li></ol>~~ ~~[ o.k. ] Compiling current kernel [ '''5.10.160''' ]~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The version of the cross-compilation toolchain used</li></ol>~~ ~~[ o.k. ] Compiler version [ '''aarch64-none-linux-gnu-gcc 11.2.1''' ]~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>The configuration file used by the kernel by default and the path where it is stored</li></ol>~~ ~~[ o.k. ] Using kernel config file [ '''config/kernel/linux-rockchip-rk356x-legacy.config''' ]~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>The path of the deb package related to the kernel generated by compiling</li></ol>~~ ~~[ o.k. ] Target directory [ '''orangepi-build/output/debs/''' ]~~ ~~<ol start="5" style="list-style-type: lower-alpha;"><li>The package name of the compiled kernel image deb package</li></ol>~~ ~~[ o.k. ] File name [ '''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb''' ]~~ ~~<ol start="6" style="list-style-type: lower-alpha;"><li>The time used for compilation</li></ol>~~ ~~[ o.k. ] Runtime [ '''5 min''' ]~~ ~~<ol start="7" style="list-style-type: lower-alpha;">~~<li>Finally, the compilation command to repeatedly compile the kernel selected last time will be displayed. Use the following command to start compiling the kernel source code directly without selecting through the graphical interface</li></ol> ~~[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=kernel KERNEL_CONFIGURE=no''' ]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>View the deb package related to the kernel generated by compilation<ol style="list-style-type: lower-alpha;"><li>'''linux-dtb-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Contains dtb files used by the kernel</li><li>'''linux-headers-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Include kernel header files</li><li>'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Contains kernel images and kernel modules</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''ls output/debs/linux-*'''~~ ~~output/debs/linux-dtb-legacy-rockchip-rk356x_1.0.0_arm64.deb output/debs/linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb~~ ~~output/debs/linux-headers-legacy-rockchip-rk356x_1.0.0_arm64.deb~~ ~~<ol start="8" style="list-style-type: decimal;"><li>The files contained in the generated Linux-image deb package are as follows<ol style="list-style-type: lower-alpha;"><li>Use the following command to decompress the deb package</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''cd output/debs'''~~ ~~test@test:~/orangepi_build/output/debs$ '''mkdir test'''~~ ~~test@test:~/orangepi_build/output/debs$ '''cp \'''~~ ~~'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb test/'''~~ ~~test@test:~/orangepi_build/output/debs$ '''cd test'''~~ ~~test@test:~/orangepi_build/output/debs/test$ '''dpkg -x \'''~~ ~~'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb .'''~~ ~~test@test:~/orangepi_build/output/debs/test$ '''ls'''~~ ~~'''boot etc lib''' linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb '''usr'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The decompressed file is as follows</li></ol>~~ ~~test@test:~/orangepi-build/output/debs/test$ '''tree -L 2'''~~ . ~~├── boot~~ ~~│ ├── config-5.10.160-rockchip-rk356x~~ ~~│ ├── System.map-5.10.160-rockchip-rk356x~~ ~~│ └── vmlinuz-5.10.160-rockchip-rk356x~~ ~~├── etc~~ ~~│ └── kernel~~ ~~├── lib~~ ~~│ └── modules~~ ~~├── linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb~~ ~~└── usr~~ ~~├── lib~~ ~~└── share~~ ~~<ol start="9" style="list-style-type: decimal;">~~<li>The orangepi-bulid compilation system will first synchronize the Linux kernel source code with the Linux kernel source code of the github server when compiling the Linux kernel source code, so if you want to modify the Linux kernel source code, you first need to turn off the update function of the source code '''(you need to compile it once This function can only be turned off after the Linux kernel source code, otherwise it will prompt that the source code of the Linux kernel cannot be found. If the source code compressed package downloaded from Google cloud disk, there is no such problem, because the source code of Linux has been cached)''', otherwise the The changes made will be reverted as follows:</li></ol> ~~<blockquote>Set the IGNORE_UPDATES variable in '''userpatches/config-default.conf''' to "yes"</blockquote>test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''~~ ~~IGNORE_UPDATES="'''yes'''"~~ ~~<ol start="10" style="list-style-type: decimal;"><li>If the kernel has been modified, the following method can be used to update the kernel and kernel modules of the development board Linux system<ol style="list-style-type: lower-alpha;"><li>Upload the deb package of the compiled Linux kernel to the Linux system of the development board</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''cd output/debs'''~~ ~~test@test:~/orangepi-build/output/debs$ '''scp \'''~~ ~~'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb root@192.168.1.xxx:/root'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>Then log in to the development board and uninstall the deb package of the installed Linux kernel</li></ol>~~ ~~root@orangepi:~# '''apt purge -y linux-image-legacy-rockchip-rk356x'''~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>Install the deb package of the new Linux kernel just uploaded</li></ol>~~ ~~root@orangepi:~# '''dpkg -i linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb'''~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>Then restart the development board, and then check whether the kernel-related modifications have taken effect</li></ol>~~ ~~root@orangepi:~# '''reboot'''~~ ~~<ol start="11" style="list-style-type: decimal;"><li>Other useful information<ol style="list-style-type: lower-alpha;"><li>The storage location of the kernel configuration file is as follows, please do not go to the kernel source code to find the kernel configuration file used by the development board</li></ol></li></ol>~~ ~~[https://github.com/orangepi-xunlong/orangepi-build/blob/next/external/config/kernel/linux-rockchip-rk3588-legacy.config orangepi-build/external/config/kernel/linux-rockchip-rk356x-legacy.config]~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The location of the dts file used by the development board is</li></ol>~~ [https://github.com/orangepi-xunlong/linux-orangepi/blob/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5.dts orangepi-build/kernel/orange-pi-5.10-rk35xx/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dts] ~~== Compile rootfs ==~~ ~~# Run the build.sh script, remember to add sudo permission~~ ~~test@test:~/orangepi-build$ '''sudo ./build.sh'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Select '''Rootfs and all deb packages'''，then enter</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img388.png|576x119px|选区_241]]~~ ~~</div><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img380.png|576x197px|}4$_5F06}}0R4GU8]OVO}4E]]~~ ~~</div><ol start="4" style="list-style-type: decimal;"><li>Then select the type of rootfs</li></ol>~~ ~~[[File:pi3b-img389.png|575x86px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>Then select the type of image<ol style="list-style-type: lower-alpha;"><li>'''Image with console interface (server)''' Indicates the image of the server version, which is relatively small</li><li>'''Image with desktop environment''' Indicates a image with a desktop, which is relatively large</li></ol></li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img390.png|576x75px|选区_245]]~~ ~~</div><ol start="6" style="list-style-type: decimal;">~~<li>If you are compiling the image of the server version, you can also choose to compile the Standard version or the Minimal version. The pre-installed software of the Minimal version will be much less than that of the Standard version '''(please do not choose the Minimal version if there is no special requirement, because many things are not pre-installed by default. Some functions may not be available)'''</li></ol> ~~<div class="figure">~~ ~~[[File:pi3b-img391.png|576x78px|选区_397]]~~ ~~</div><ol start="7" style="list-style-type: decimal;">~~<li>If you are compiling the image of the desktop version, you also need to select the type of desktop environment. Currently, Ubuntu Jammy mainly maintains XFCE and Gnome desktops, Ubuntu Focal only maintains XFCE desktops, and Debian Bullseye mainly maintains XFCE and KDE desktops</li></ol> ~~<div class="figure">~~ ~~[[File:pi3b-img392.png|575x99px|Selection_001]]~~ ~~</div>[[File:pi3b-img393.png|576x74px]]~~ ~~You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.~~ ~~[[File:pi3b-img394.png|575x264px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>Then it will start to compile rootfs, and some of the information prompted during compilation are as follows<ol style="list-style-type: lower-alpha;"><li>The type of rootfs</li></ol></li></ol>~~ ~~[ o.k. ] local not found [ Creating new rootfs cache for '''jammy''']~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>The storage path of the compiled rootfs compressed package</li></ol>~~ ~~[ o.k. ] Target directory [ '''external/cache/rootfs''' ]~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>The name of the rootfs compressed package generated by compilation</li></ol>~~ ~~[ o.k. ] File name [ '''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' ]~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>The time used for compilation</li></ol>~~ ~~[ o.k. ] Runtime [ '''13 min''' ]~~ ~~<ol start="9" style="list-style-type: decimal;"><li>View the rootfs compressed package generated by compilation<ol style="list-style-type: lower-alpha;"><li>'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' is the rootfs compressed package, the meaning of each field of the name is<ol style="list-style-type: lower-alpha;"><li>'''jammy''' indicates the type of Linux distribution of rootfs</li><li>'''xfce''' means rootfs is the type of desktop version, if it is '''cli''', it means the type of server version</li><li>'''arm64''' represents the architecture type of rootfs</li>~~<li>'''f930ff6ebbac1a72108a2e100762b18f''' is the MD5 hash value generated by the package names of all software packages installed by rootfs. As long as the list of software packages installed by rootfs is not modified, this value will not change. The compilation script will use this MD5 hash value to generate Determine whether rootfs needs to be recompiled</li></ol>~~</li><li>'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.list''' lists the package names of all packages installed by rootfs</li></ol></li></ol>~~ ~~test@test:~/orangepi-build$ '''ls external/cache/rootfs/'''~~ ~~'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4'''~~ ~~jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.current~~ ~~jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.list~~ ~~<ol start="10" style="list-style-type: decimal;">~~<li>If the required rootfs already exists under '''external/cache/rootfs''', then compiling rootfs again will directly skip the compilation process and will not restart the compilation. When compiling the image, it will also go to '''external/cache/rootfs''' to find out whether it has If there is rootfs available in the cache, use it directly, which can save a lot of download and compilation time.</li></ol> ~~== Compile Linux image ==~~ ~~# Run the build.sh script, remember to add sudo permission~~ ~~test@test:~/orangepi-build$ '''sudo ./build.sh'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Select '''Full OS image for flashing'''，then enter</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img395.png|576x128px|选区_242]]~~ ~~</div><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img380.png|576x197px|}4$_5F06}}0R4GU8]OVO}4E]]~~ ~~</div><ol start="4" style="list-style-type: decimal;"><li>Then select the type of rootfs</li></ol>~~ ~~[[File:pi3b-img389.png|575x86px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>Then select the type of image<ol style="list-style-type: lower-alpha;"><li>'''Image with console interface (server)''' Indicates the image of the server version, which is relatively small</li><li>'''Image with desktop environment''' Indicates a image with a desktop, which is relatively large</li></ol></li></ol>~~ ~~<div class="figure">~~ ~~[[File:pi3b-img390.png|576x75px|选区_245]]~~ ~~</div><ol start="6" style="list-style-type: decimal;">~~<li>If you are compiling the image of the server version, you can also choose to compile the Standard version or the Minimal version. The pre-installed software of the Minimal version will be much less than that of the Standard version '''(please do not choose the Minimal version if there is no special requirement, because many things are not pre-installed by default. Some functions may not be available)'''</li></ol> ~~<div class="figure">~~ ~~[[File:pi3b-img391.png|569x77px|选区_397]]~~ ~~</div><ol start="7" style="list-style-type: decimal;">~~<li>If you are compiling the image of the desktop version, you also need to select the type of desktop environment. Currently, Ubuntu Jammy mainly maintains XFCE and Gnome desktops, Ubuntu Focal only maintains XFCE desktops, and Debian Bullseye mainly maintains XFCE and KDE desktops</li></ol> ~~<div class="figure">~~ ~~[[File:pi3b-img392.png|575x99px|Selection_001]]~~ ~~</div>[[File:pi3b-img393.png|576x74px]]~~ ~~You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.~~ ~~[[File:pi3b-img394.png|575x264px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>Then it will start to compile the Linux image. The general process of compilation is as followsa. Initialize the compilation environment of Ubuntu PC and install the software packages required for the compilation processb. Download the source code of u-boot and Linux kernel (if cached, only update the code)c. Compile u-boot source code and generate u-boot deb packaged. Compile the Linux source code and generate Linux-related deb packagese. Make the deb package of Linux firmwaref. Make the deb package of the orangepi-config toolg. Create a deb package supported by the boardh. If you are compiling the desktop image, you will also create desktop-related deb packagesi. Check whether the rootfs has been cached, if not, recreate the rootfs, if it has been cached, directly decompress and usej. Install the previously generated deb package into rootfsk. Make some specific settings for different development boards and different types of images, such as pre-installing additional software packages, modifying system configuration, etc.l. Then make an image file and format the partition, the default type is ext4m. Then copy the configured rootfs to the mirrored partitionn. Then update initramfso. Finally, write the bin file of u-boot into the image through the dd command</li><li>After compiling the image, the following information will be prompted<ol style="list-style-type: lower-alpha;"><li>The storage path of the compiled image</li></ol></li></ol>~~ ~~[ o.k. ] Done building [ '''output/images/Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160/Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160.img''' ]~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>Compilation time</li></ol>~~ ~~'''[ o.k. ] Runtime [ 19 min ]'''~~ ~~<ol style="list-style-type: lower-alpha;"><li>Repeat the command to compile the image, and use the following command to start compiling the image directly without selecting through the graphical interface</li></ol>~~ ~~[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=image RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=yes''' ]~~ ~~~~ ~~= Android 11 operating system instructions =~~ ~~== Supported Android versions ==~~ ~~{| class="wikitable"~~|-~~| style="text-align: left;"| '''Android version'''| style="text-align: left;"| '''Kernel version'''~~|-~~| style="text-align: left;"| '''Android 11'''| style="text-align: left;"| '''Linux4.19'''~~|} ~~== Android Function Adaptation ==~~ ~~{| class="wikitable"~~|-~~| style="text-align: left;"| '''Functions'''| style="text-align: left;"| '''Android 11'''~~|-~~| style="text-align: left;"| '''USB2.0x3'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''USB3.0x1'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''M.2 NVMe SSD boot'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''WIFI'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Bluetooth'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''GPIO（40pin）'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''UART（40pin）'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''SPI（40pin）'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''I2C（40pin）'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''PWM（40pin）'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''PWM fan interface'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''3pin Debugging serial port'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''EMMC'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''TF card boot'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI video'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI Audio'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''LCD'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''eDP display'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Gigabit network port'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Network port status indicator'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Headphone playback'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Headphone recording'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''LED Light'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''GPU'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''NPU'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''VPU'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''RTC'''| style="text-align: left;"| '''OK'''~~|} ~~== WIFI connection test method ==~~ ~~# First click enter '''Setting'''~~ ~~[[File:pi3b-img396.png|549x228px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Then select '''Network & internet'''</li></ol>~~ ~~[[File:pi3b-img397.png|565x120px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then select '''Wi-Fi'''</li></ol>~~ ~~[[File:pi3b-img398.png|561x99px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then turn on the '''Wi-Fi''' switch</li></ol>~~ ~~[[File:pi3b-img399.png|560x167px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>After turning on '''Wi-Fi''', if everything is normal, you can scan for nearby Wi-Fi hotspots</li></ol>~~ ~~[[File:pi3b-img400.png|561x166px]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Then select the Wi-Fi you want to connect to, and the password input interface shown in the figure below will pop up</li></ol>~~ ~~[[File:pi3b-img401.png|553x237px]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>Then use the keyboard to enter the password corresponding to Wi-Fi, and then use the mouse to click the Enter button in the virtual keyboard to start connecting to Wi-Fi</li></ol>~~ ~~[[File:pi3b-img402.png|553x232px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>After the Wi-Fi connection is successful, the display is as shown in the figure below:</li></ol>~~ ~~[[File:pi3b-img403.png|558x102px]]~~ ~~== How to use Wi-Fi hotspot ==~~ ~~# First, please make sure that the Ethernet port is connected to the network cable and can access the Internet normally# Then select '''Settings'''~~ ~~[[File:pi3b-img396.png|549x228px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then select '''Network & internet'''</li></ol>~~ ~~[[File:pi3b-img397.png|565x120px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then select '''Hotspot & tethering'''</li></ol>~~ ~~[[File:pi3b-img404.png|549x173px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>Then select '''Wi-Fi hotspot'''</li></ol>~~ ~~[[File:pi3b-img405.png|548x104px]]~~ ~~<ol start="6" style="list-style-type: decimal;">~~<li>Then turn on the '''Wi-Fi hotspot''', you can also see the name and password of the generated hotspot in the figure below, remember them, and use them when connecting to the hotspot (if you need to modify the name and password of the hotspot, you need to turn off the Wi-Fi first -Fi hotspot before modification)</li></ol> ~~[[File:pi3b-img406.png|551x158px]]~~ ~~<ol start="7" style="list-style-type: decimal;">~~<li>At this time, you can take out your mobile phone. If everything is normal, you can find the WIFI hotspot with the same name ('''here AndroidAP_6953''') displayed under the '''Hotspot name''' in the above picture in the WI-FI list searched by the mobile phone. Then you can click '''AndroidAP_6953''' to connect to the hotspot, and the password can be seen under the '''Hotspot password''' in the above picture</li></ol> ~~[[File:pi3b-img407.png|313x238px]]~~ ~~<ol start="8" style="list-style-type: decimal;">~~<li>After the connection is successful, it will be displayed as shown in the figure below (the interface of different mobile phones will be different, the specific interface is subject to the display of your mobile phone). At this point, you can open a webpage on your mobile phone to see if you can access the Internet. If you can open the webpage normally, it means that the '''WI-FI Hotspot''' of the development board can be used normally.</li></ol> ~~[[File:pi3b-img408.png|327x165px]]~~ ~~== Bluetooth test method ==~~ ~~# First click enter '''Setting'''~~ ~~[[File:pi3b-img396.png|549x228px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Then select '''Connected devices~~Notes'''~~</li></ol>~~ ~~[[File:pi3b-img409.png|547x115px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then click '''Pair new device''' to turn on Bluetooth and start scanning the surrounding Bluetooth devices</li></ol>~~ ~~[[File:pi3b-img410.png|547x126px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>The searched Bluetooth devices will be displayed under '''Available devices'''</li></ol>~~ ~~[[File:pi3b-img411.png|559x279px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>Then click the Bluetooth device you want to connect to start pairing. When the following interface pops up, please use the mouse to select the '''Pair''' option</li></ol>~~ ~~[[File:pi3b-img412.png|522x212px]]~~ ~~<ol start="6" style="list-style-type: decimal;">~~<li>The test here is the configuration process of the development board and the Bluetooth of the Android mobile phone. At this time, the following confirmation interface will pop up on the mobile phone. After clicking the pairing button on the mobile phone, the pairing process will start</li></ol> ~~[[File:pi3b-img413.png|236x273px]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>After the pairing is completed, you can see the paired Bluetooth device as shown in the figure below</li></ol>~~ ~~[[File:pi3b-img414.png|545x178px]]~~ ~~<ol start="8" style="list-style-type: decimal;">~~<li>At this time, you can use the Bluetooth of your mobile phone to send a picture to the development board. After sending, you can see the following confirmation interface in the Android system of the development board, and then click '''Accept''' to start receiving the picture sent by the mobile phone.</li></ol> ~~[[File:pi3b-img415.png|559x238px]]~~ ~~<ol start="9" style="list-style-type: decimal;"><li>You can open the '''Download''' directory in the file manager to view the pictures received by the Android system Bluetooth of the development board</li></ol>~~ ~~[[File:pi3b-img416.png|573x97px]]~~ ~~== How to use Raspberry Pi 5-inch screen ==~~ ~~'''Please make sure that the image used is the following two versions of the image:'''~~ ~~'''OrangePi3B_RK3566_Android11_lcd_v1.x.x.img'''~~ ~~'''OrangePi3B_RK3566_Android11_spi-nvme_lcd_v1.x.x.img'''~~ ~~# The screen needs to be assembled first, please refer to [[\l|'''the assembly method of the Raspberry Pi 5-inch screen''']]# Connect the Type-C power supply to the board and power it on. After the system starts, you can see the screen display as shown in the figure below~~ ~~[[File:pi3b-img417.png|516x332px]]~~ ~~== 40pin interface GPIO, UART, SPI and PWM test ==~~ ~~=== 40pin GPIO port test ===~~ ~~# First click on the wiringOP icon to open the wiringOP APP~~ ~~[[File:pi3b-img418.png|576x210px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>The main interface of wiringOP APP is displayed as shown in the figure below, and then click the '''GPIO_TEST''' button to open the GPIO test interface</li></ol>~~ ~~[[File:pi3b-img419.png|575x148px]]~~ ~~<ol start="3" style="list-style-type: decimal;">~~<li>The GPIO test interface is shown in the figure below. The two rows of '''CheckBox''' buttons on the left are in one-to-one correspondence with the 40pin pins. When the '''CheckBox''' button is checked, the corresponding GPIO pin will be set to '''OUT''' mode, and the pin level will be set to high level; when the checkbox is unchecked, the GPIO pin level will be set to low level; When the '''GPIO READALL''' button is pressed, information such as wPi number, GPIO mode, and pin level can be obtained; when the '''BLINK ALL GPIO''' button is clicked, the program will control the 28 GPIO ports to continuously switch between high and low levels</li></ol> ~~[[File:pi3b-img420.png|576x303px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button, the output information is as shown in the figure below:</li></ol>~~ ~~[[File:pi3b-img421.png|575x323px]]~~ ~~<ol start="5" style="list-style-type: decimal;">~~<li>There are a total of 28 GPIO ports in the 40pins of the development board that can be used. The following uses pin 7—the corresponding GPIO is GPIO4_A4—the corresponding wPi serial number is 2—as an example to demonstrate how to set the high and low levels of the GPIO port. First click the '''CheckBox''' button corresponding to pin 7. When the button is selected, pin 7 will be set to high level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is 3.3v, it means setting high level success</li></ol> ~~[[File:pi3b-img422.png|241x326px]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is '''OUT''', and the pin level is high</li></ol>~~ ~~[[File:pi3b-img423.png|574x301px]]~~ ~~<ol start="7" style="list-style-type: decimal;">~~<li>Click the '''CheckBox''' button in the figure below again to cancel the check status. Pin 7 will be set to low level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is '''0v''', it means that the low level is set successfully.</li></ol> ~~[[File:pi3b-img424.png|250x345px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is OUT, and the pin level is low</li></ol>~~ ~~[[File:pi3b-img425.png|576x300px]]~~ ~~=== 40pin UART test ===~~ ~~# UART7 and UART9 are enabled by default in Android. The position of the 40pin is shown in the figure below, and the corresponding device nodes are '''/dev/ttyS7''' and '''/dev/ttyS9''' respectively~~ ~~[[File:pi3b-img269.png|376x92px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>First click on the wiringOP icon to open the wiringOP APP</li></ol>~~ ~~[[File:pi3b-img418.png|576x210px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>The main interface of wiringOP APP is displayed as shown in the figure below, and then click the '''UART_TEST''' button to open the UART test interface</li></ol>~~ ~~[[File:pi3b-img426.png|575x156px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>The serial port test interface of the APP is shown in the figure below</li></ol>~~ ~~[[File:pi3b-img427.png|576x324px]]~~ ~~<ol start="5" style="list-style-type: decimal;">~~<li>Take the test of '''UART7''' as an example below, select the '''/dev/ttyS7''' node in the selection box, enter the baud rate you want to set in the edit box, and then click the '''OPEN''' button to open the /dev/ttyS7 node. After the opening is successful, the '''OPEN''' button becomes unselectable, and the '''CLOSE''' button and '''SEND''' button become selectable</li></ol> ~~[[File:pi3b-img428.png|574x166px]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Then use Dupont wire to short the RXD and TXD pins of uart7</li></ol>~~ ~~[[File:pi3b-img429.png|418x103px]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>Then you can enter a character in the send edit box below, and click the '''SEND''' button to start sending</li></ol>~~ ~~[[File:pi3b-img430.png|575x161px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>If everything is normal, the received string will be displayed in the receiving box</li></ol>~~ ~~[[File:pi3b-img431.png|574x164px]]~~ ~~=== 40pin SPI test ===~~ ~~# According to the schematic diagram of the 40pin interface, the spi available for Orange Pi 3B is spi3~~ ~~[[File:pi3b-img264.png|577x193px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>Here, the SPI interface is tested through the w25q64 module. First, the w25q64 device is connected to the SPI3 interface</li></ol>~~ ~~[[File:pi3b-img432.png|373x215px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then click the wiringOP icon to open the wiringOP APP</li></ol>~~ ~~[[File:pi3b-img418.png|576x210px]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>The main interface of wiringOP APP is displayed as shown in the figure below, click the SPI_TEST button to open the SPI test interface</li></ol>~~ ~~[[File:pi3b-img433.png|574x149px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>Then click the '''OPEN''' button to initialize the SPI</li></ol>~~ ~~[[File:pi3b-img434.png|576x241px]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Then fill in the bytes that need to be sent, such as reading the ID information of w25q64, fill in the address 0x9f in data[0], and then click the '''TRANSFER''' button</li></ol>~~ ~~[[File:pi3b-img435.png|572x216px]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>Finally, the APP will display the read ID information</li></ol>~~ ~~[[File:pi3b-img436.png|575x296px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>The MANUFACTURER ID of the w25q64 module is EFh, and the Device ID is 4017h, corresponding to the value read above (h stands for hexadecimal)</li></ol>~~ ~~[[File:pi3b-img437.png|374x126px]]~~ ~~=== 40pin PWM test ===~~ ~~# Android enables '''PWM11''' by default, and the corresponding pin is located at 40pin as shown in the figure below~~ ~~[[File:pi3b-img438.png|334x107px]]~~ ~~<ol start="2" style="list-style-type: decimal;"><li>First click on the wiringOP icon to open the wiringOP APP</li></ol>~~ ~~[[File:pi3b-img418.png|576x210px]]~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Then click the '''PWM_TEST''' button on the main interface of wiringOP to enter the PWM test interface</li></ol>~~ ~~[[File:pi3b-img439.png|575x150px]]~~ ~~<ol start="4" style="list-style-type: decimal;">~~<li>The base address corresponding to PWM11 is '''fe6f0030''', here pwmchip0 shows '''fdd70020.pwm''' on the right, then you need to click the drop-down option to select other pwmchips until '''febf0030.pwm''' is displayed on the right</li></ol> ~~[[File:pi3b-img440.png|576x178px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>When the drop-down option selects '''pwmchip3''', the corresponding base address of PWM11 is '''fe6f0030''' on the right</li></ol>~~ ~~[[File:pi3b-img441.png|574x161px]]~~ ~~<ol start="6" style="list-style-type: decimal;">~~<li>Then confirm the PWM channel, the default is channel 0, and confirm the PWM cycle, the default configuration is '''50000ns''', converted to PWM frequency is '''20KHz''', you can modify it yourself, click the '''EXPORT''' button to export '''PWM11'''</li></ol> ~~[[File:pi3b-img442.png|575x160px]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>Then drag the drag bar below to change the PWM duty cycle, and then check Enable to output the PWM waveform</li></ol>~~ ~~[[File:pi3b-img443.png|575x167px]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>Then use an oscilloscope to measure the No. 32 pin in the 40pin of the development board, and you can see the following waveform</li></ol>~~ ~~[[File:pi3b-img444.png|460x276px]]~~ ~~== How to use ADB ==~~ ~~=== Use network connection adb debugging ===~~ '''Using the network adb does not require a data cable to connect the computer and the development board, but to communicate through the network, so first make sure that the wired or wireless network of the development board is connected, and then obtain the IP address of the development board, which will be used later.''' ~~# Make sure that the '''service.adb.tcp.port''' of the Android system is set to port number 5555~~ ~~console:/ # '''getprop | grep "adb.tcp"'''~~ ~~[service.adb.tcp.port]: ['''5555''']~~ ~~<ol start="2" style="list-style-type: decimal;"><li>If '''service.adb.tcp.port''' is not set, you can use the following command to set the port number of network adb</li></ol>~~ ~~console:/ # '''setprop service.adb.tcp.port 5555'''~~ ~~console:/ # '''stop adbd'''~~ ~~console:/ # '''start adbd'''~~ ~~<ol start="3" style="list-style-type: decimal;"><li>Install adb tool on Ubuntu PC</li></ol>~~ ~~test@test:~$ '''sudo apt update'''~~ ~~test@test:~$ '''sudo apt install -y adb'''~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then connect network adb on Ubuntu PC</li></ol>~~ ~~test@test:~$ '''adb connect 192.168.1.xxx''' '''(The IP address needs to be changed to the IP address of the development board)'''~~ * daemon not running; starting now at tcp:5037 * daemon started successfully ~~connected to 192.168.1.xxx:5555~~ ~~test@test:~$ '''adb devices'''~~ ~~List of devices attached~~ ~~192.168.1.xxx:5555 device~~ ~~<ol start="5" style="list-style-type: decimal;"><li>Then you can log in to the android system through the adb shell on the Ubuntu PC</li></ol>~~ ~~test@test:~$ '''adb shell'''~~ ~~console:/ #~~ ~~= Appendix =~~ ~~== User Manual Update History ==~~ ~~{| class="wikitable"~~

|-

|}

== Image Update History ==

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

|-

| style="text-align: center;" | '''Date'''| style="text-align: center;" | '''Update Notes'''

|-

| style="text-align: center;" | 2023-07-19| ~~Orangepi3 b_1~~Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160.7z

~~Orange pi3b_1~~Orangepi3b_1.0.0_ubuntu_jammy_desktop_xfce_linux5.10.160.7z

~~Orange pi3b_1~~Orangepi3b_1.0.0_ubuntu_focal_desktop_xfce_linux5.10.160.7z

OrangePi3B_RK3566_Android11_v1.0.0.tar.gz

OrangePi3B_RK3566_Android11_spi-nvme_v1.0.0.tar.gz

~~O rangePi3B_RK3566_Android11_lcd_spi~~OrangePi3B_RK3566_Android11_lcd_spi-nvme_v1.0.0.tar.gz

* initial version

|}

Admin

Bureaucrats, Administrators

8,367

edits

Wiki-Orange Pi β

Changes

Orange Pi 3B

Wiki-Orange Pi ^β