Changes

← Older edit

Orange Pi 3B

32,456 bytes added, 09:06, 24 August 2023

→‎Interface details of Orange Pi 3B

= '''Basic features 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>|}

= '''Introduction to the use of the development board''' =

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

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

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

[[File:pi3b-img8.png]]

</ol>

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

[[File:pi3b-img9.png]]

</ol>

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

[[File:pi3b-img10.png]]

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

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

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

</ol>

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

[[File:pi3b-img12.png]]

</ol>

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

[[File:pi3b-img13.png]]

</ol>

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

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

[[File:pi3b-img14.png]]

</ol>

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

[[File:pi3b-img15.png]]

</ol>

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

[[File:pi3b-img16.png]]

</div></ol>

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

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

</ol>

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

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

|-

|-

|}

</ol>

~~~~

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

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

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

|-

|

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

|}

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

</div>

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

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

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

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

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

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

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

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

[[File:pi3b-img20.png]]

</ol>

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

[[File:pi3b-img21.png]]

</ol>

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

[[File:pi3b-img22.png]]

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

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

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

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

|}

</ol>

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

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

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

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

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

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

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

[[File:pi3b-img26.png]]

</ol>

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

[[File:pi3b-img27.png]]

</ol>

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

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

</div></ol>

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

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

</div>

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

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

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

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

</div></ol>

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

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

</div>

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

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

[[File:pi3b-img31.png]]

</ol>

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

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

[[File:pi3b-img32.png]]

</ol>

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

[[File:pi3b-img33.png]]

</ol>

</li></ol>

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

[[File:pi3b-img34.png]]

</ol>

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

[[File:pi3b-img35.png]]

</ol>

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

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

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

</div></ol>

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

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

[[File:pi3b-img37.png]]

</ol>

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

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

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

[[File:pi3b-img39.png]]

</ol>

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

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

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

</div></ol>

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

[[File:pi3b-img41.png]]

</ol>

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

[[File:pi3b-img42.png]]

</ol>

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

[[File:pi3b-img43.png]]

</ol>

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

[[File:pi3b-img44.png]]

</ol>

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

[[File:pi3b-img45.png]]

</ol>

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

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

</div></ol>

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

[[File:pi3b-img47.png]]

</ol>

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

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

[[File:pi3b-img48.png]]

</ol>

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

[[File:pi3b-img49.png]]

</ol>

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

[[File:pi3b-img50.png]]

</ol>

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

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

</div></ol>

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

</li></ol>

~~~~

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

<li>Then format the TF card

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

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

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

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

</div></ol>

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

[[File:pi3b-img53.png]]

</ol>

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

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

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

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

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

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

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

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

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

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

</li></ol>

~~~~

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

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

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

# Download the balenaEtcher software, the download address is

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

|-

|

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

|}

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

[[File:pi3b-img20.png]]

</ol>

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

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

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

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

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

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

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

Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_Linux5.10.160.img #mirror file

|}</ol>

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

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

|-

|

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

Orangepi3b_1.0.0_debian_bullseye_desktop_xfce_Linux5.10.160.img: OK

|}</ol>

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

[[File:pi3b-img57.png]]

</ol>

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

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

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

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

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

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

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

[[File:pi3b-img58.png]]

</ol>

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

[[File:pi3b-img59.png]]

</ol>

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

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

~~~~

== How to burn Linux image to eMMC ==

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

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

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

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

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

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

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

</div></ol>

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

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

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

</div></ol>

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

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

</div>

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

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

[[File:pi3b-img31.png]]

</ol>

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

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

[[File:pi3b-img32.png]]

</ol>

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

[[File:pi3b-img33.png]]

</ol>

</li></ol>

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

[[File:pi3b-img34.png]]

</ol>

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

[[File:pi3b-img35.png]]

</ol>

<li>Then start burning the Linux image into eMMC

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

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

</div></ol>

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

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

[[File:pi3b-img37.png]]

</ol>

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

[[File:pi3b-img38.png]]

</ol>

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

[[File:pi3b-img39.png]]

</ol>

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

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

</div></ol>

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

[[File:pi3b-img41.png]]

</ol>

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

[[File:pi3b-img42.png]]

</ol>

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

[[File:pi3b-img65.png]]

</ol>

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

[[File:pi3b-img66.png]]

</ol>

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

[[File:pi3b-img67.png]]

</ol>

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

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

</div></ol>

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

[[File:pi3b-img69.png]]

</ol>

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

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

[[File:pi3b-img48.png]]

</ol>

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

[[File:pi3b-img70.png]]

</ol>

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

[[File:pi3b-img71.png]]

</ol>

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

[[File:pi3b-img72.png]]

</ol>

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

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

~~~~

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

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

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

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

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

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

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

|-

|

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

Orangepi3b_x.x.x_debian_bullseye_desktop_xfce_Linux5.10.160.img

|}

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

|-

|

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

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

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

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

|}

</ol>

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

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

|-

|

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

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

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

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

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

|}</ol>

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

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

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

|}

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

|-

|

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

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

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

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

|}

</ol>

</li></ol>

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

~~~~

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

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

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

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

[[File:pi3b-img73.png]]

</ol>

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

[[File:pi3b-img74.png]]

</ol>

</li></ol>

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

[[File:pi3b-img75.png]]

</ol>

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

[[File:pi3b-img76.png]]

</ol>

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

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

</div></ol>

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

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

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

</div></ol>

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

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

</div>

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

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

[[File:pi3b-img31.png]]

</ol>

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

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

[[File:pi3b-img32.png]]

</ol>

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

[[File:pi3b-img33.png]]

</ol>

</li></ol>

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

[[File:pi3b-img34.png]]

</ol>

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

[[File:pi3b-img35.png]]

</ol>

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

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

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

</div></ol>

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

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

[[File:pi3b-img37.png]]

</ol>

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

[[File:pi3b-img38.png]]

</ol>

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

[[File:pi3b-img39.png]]

</ol>

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

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

</div></ol>

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

[[File:pi3b-img41.png]]

</ol>

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

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

[[File:pi3b-img77.png]]

</ol>

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

[[File:pi3b-img78.png]]

</ol>

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

[[File:pi3b-img79.png]]

</ol>

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

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

</div></ol>

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

[[File:pi3b-img80.png]]

</ol>

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

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

</div></ol>

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

[[File:pi3b-img82.png]]

</ol>

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

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

[[File:pi3b-img48.png]]

</ol>

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

[[File:pi3b-img83.png]]

</ol>

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

[[File:pi3b-img84.png]]

</ol>

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

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

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

|-

|

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

|}

</ol>

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

~~~~

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

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

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

[[File:pi3b-img73.png]]

</ol>

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

[[File:pi3b-img74.png]]

</ol>

</li></ol>

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

[[File:pi3b-img75.png]]

</ol>

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

[[File:pi3b-img76.png]]

</ol>

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

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

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

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

|-

|

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

|}</ol>

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

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

</div></ol>

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

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

</div></ol>

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

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

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

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

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

Orangepi3b_x.x.x_debian_bullseye_desktop_xfce_Linux5.10.160.img

|}

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

|-

|

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

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

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

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

|}

</ol>

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

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

|-

|

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

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

|}

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

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

|-

|

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

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

|}</ol>

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

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

|-

|

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

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

|}</ol>

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

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

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

|-

|

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

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

|}

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

|-

|

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

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

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

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

|}

</ol>

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

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

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

</li></ol>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

~~orangepi@orangepi:~/Desktop$ '''sudo fdisk -l | grep "nvme0n1"'''~~ ~~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~~img98.png]]

~~orangepi@orangepi~~</div></ol><ol start="9" style="list-style-type:~~~/Desktop$~~ lower-alpha;"><li>Then enter the password '''~~lspci~~orangepi'''of the development board Linux system, and it will start burning the u-boot image into the SPI Flash</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~~img99. ~~Device 5765 (rev 01)~~png]]

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

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

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

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

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

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

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

</div></ol>

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

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

</div></ol>

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

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

</div></ol>

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

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

</div></ol>

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

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

</div></ol>

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

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

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

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

</div></ol>

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

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

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

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

</div></ol>

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

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

</div></ol>

<li>The display after burning is as follows:</li> [[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~~>

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

[[File:pi3b-~~img102~~img114.png~~|386x204px|IMG_256~~]] </~~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="83" style="list-style-type: lower-alpha;"><li>~~Then click~~ '''~~Yes~~After using this method to burn the image, there is no need to manually expand the capacity, ~~I'm sure~~and it will automatically expand the capacity at the first startup.'''</li></ol></li></ol>

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

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

~~</div><ol style="list-style-type: lower-roman;"><li>Then enter~~ # First prepare a TF card with 8GB or larger capacity. The transmission speed of the ~~password orangepi~~ TF card must be class10 or above. It is recommended to use a TF card of ~~the Linux system on the development board,~~ SanDisk and ~~it will start burning the Linux image~~ other brands# You also need to prepare a good quality USB2.0 male-to ~~the SSD</li></ol>~~-male data cable

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

</div>

<ol start="103" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The display of the~~ Then download Rockchip driver '''DriverAssitant_v5.12.zip''' and burning ~~process is as follows~~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''']</lip></olli> <li>Then download the Android image from [~~[File~~http:~~pi3b~~//www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-~~img109~~Pi-3B.~~png|393x212px]~~html '''Orange Pi's download page'''].<ol style="list-style-type: lower-alpha;"><li>After opening the download link of the Android image, you can see the following two types of Android images, please select the image in the '''TF card and eMMC startup image''' folder to download</li>

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

</div>

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

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

[[File:pi3b-img31.png]]</ol><ol start="127" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then you need~~ After opening '''DriverInstall.exe''', the steps to ~~expand the capacity of the rootfs partition in~~ install the ~~NVMe SSD. The steps~~ Rockchip driver are as follows:

<li>~~Open '''GParted''' first, if~~ Click the ~~system does not have Gparted pre-installed, please use the apt command to install itorangepi@orangepi:~$~~ "'''~~sudo apt-get install -y gparted~~Driver Installation'''~~</li></ol>~~" button</li~~></ol~~>

~~<div class="figure">~~ [[File:pi3b-~~img112~~img32.png~~|576x215px|IMG_256~~]] </~~div~~ol>

<li>~~Then enter the password orangepi~~ After waiting for a period of ~~the Linux system~~time, a pop-up window will prompt "'''The driver is installed successfully'''", and then click the "'''~~Authenticate~~OK'''" button.</li~~></ol~~>

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

[[File:pi3b-img34.png]]</ol><ol start="39" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then click~~ After opening the '''~~Fix~~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-~~img114~~img35.png~~|355x261px~~]]</ol><ol start="410" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~select NVMe SSD~~start burning the Android image to the TF card<ol style="list-style-type: lower-alpha;"><li>First, connect the development board to the Windows computer through the USB2.0 male-to-male data cable. The position of the USB2.0 programming interface of the development board is shown in the figure below</olli>

[[File:pi3b-~~img115~~img36.png~~|452x187px|IMG_256~~]]

</div></ol><ol start="52" style="list-style-type: lower-alpha;"><li>~~The display interface after selecting NVMe SSD~~ Then make sure that the development board is ~~as follows~~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:</lip></olli>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

~~~~<ol ~~start="10"~~ style="list-style-type: decimal;"><li>~~Step~~ First prepare a TF card with 8GB or larger capacity. The transmission speed of the TF card must be class10 or above. It is recommended to use a TF card of SanDisk and other brands</li><li>Then use the card reader to insert the TF card into the computer</li><li>Then download the SDDiskTool programming tool from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page'9)''], ' ~~is to clone~~ ''please make sure that the ~~system in~~ version of the ~~TF card to~~ SDDiskTool tool is the ~~NMVe SSD~~latest v1.72. ~~We can also directly burn~~ '''</li><li>Then download the ~~Linux~~ Android11 image ~~file to~~ from the ~~NVMe SSD~~[http://www.orangepi. ~~Here are the steps:~~org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi data download page''']

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

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

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

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

[[File:pi3b-img125.png]]</ol><~~span id~~/li></ol></li></ol><ol start="~~method~~5" style="list-style-type: decimal;"><li>Then use decompression software to decompress the compressed package of~~-burning-android-~~the downloaded Android image~~-to-tf-card-through-usb2~~.~~0-burning-port"~~Among the decompressed files, the file ending with ".img" is the Android image file, and the size is more than 1GB</~~span~~li>~~=== Method of burning Android image~~ <li>Then use decompression software to decompress '''SDDiskTool_v1.72.zip''', this software does not need to ~~TF card through USB2~~be installed, just find '''SD_Firmware_Tool.~~0 burning port ===~~exe''' in the decompressed folder and open it</li>

~~# First prepare a~~ [[File:pi3b-img135.png]]</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. '''Please make sure that the displayed disk device is consistent with ~~8GB or larger capacity. The transmission speed~~ the drive letter of the TF card ~~must be class10 or above. It~~ you want to burn''', if there is ~~recommended~~ no display, you can try to ~~use a~~ unplug the TF card ~~of SanDisk and other brands# You also need to prepare a good quality USB2.0 male-to-male data cable~~</li>

[[File:pi3b-img136.png]]<~~div class~~/ol><ol start="8" style="~~figure~~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-~~img16~~img137.png~~|141x138px|D6BB9058~~]]</ol><ol start="9" style="list-~~CDC3~~style-~~42d7~~type: decimal;"><li>Then start to write the Android image to the TF card<ol style="list-~~A7FC~~style-~~FBF630D886B7]]~~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>

~~</div><ol start="3" style="list-style-type: decimal;"><li>Then download Rockchip driver '''DriverAssitant_v5.12.zip''' and burning tool '''RKDevTool_Release_v3.15.zip''' from~~ [~~http~~[File:~~//www~~pi3b-img138.~~orangepi.org/html/serviceAndSupport/index.html '''Orange Pi's data download page'''~~png]~~</li><li>Then download the Android image from [http://www.orangepi.org/html/serviceAndSupport/index.html '''Orange Pi's download page'''~~]~~.<ol style="list-style-type: lower-alpha;">~~<li>After opening the download link of the Android image, you can see the following two types of Android images, please select the image in the '''TF card and eMMC startup image''' folder to download</li></ol>

</li></ol>

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

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

~~[[File:pi3b-img124.png|340x108px|e6986fc9c8fc078e8cb6a9c39b76fb8]]~~== How to burn Android image to eMMC ==

~~</div><ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <~~li><p~~big>~~After entering the~~ '''~~TF card and~~ Note, after burning the image into eMMC ~~startup image''' folder~~, ~~you can see~~ if the ~~following two images~~test finds that it cannot be started, please clear the ~~difference between them is:<ol style="list-style-type: lower-alpha;"><li>The first image is dedicated to HDMI display~~ SPIFlash and ~~supports 4K display~~try again. ~~If you don’t use LCD screen~~For the method of clearing SPIFlash, please ~~download~~ refer to [[Orange Pi 3B#Using RKDevTool to clear SPIFlash|the ~~image without lcd</li><li>If you want~~ method of using RKDevTool to ~~use lcd screen, please choose image with lcd~~clear SPIFlash]].'''</~~p></li></ol~~big>~~</li></ol>~~|}

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

~~<ol start~~{| class="5wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;"><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><p~~big>~~Then use the decompression software to decompress '''DriverAssitant_v5.12.zip~~'''~~, and then find~~ Note that all the ~~'''DriverInstall~~following operations are performed on a Windows computer.~~exe~~''' ~~executable file in the decompressed folder and open it~~</~~p></li></ol~~big>|}

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

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

[[File:pi3b-~~img32~~img63.png|~~300x157px~~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>

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

[[File:pi3b-~~img33~~img16.png~~|315x164px~~]]

</div></ol><ol start="83" style="list-style-type: decimal;"><li>Then ~~decompress~~ download Rockchip driver '''DriverAssitant_v5.12.zip''' and burning tool '''RKDevTool_Release_v3.15.zip'''~~, this software does not need to be installed, just find~~ from [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''Orange Pi'~~RKDevTool~~s data download page''' in ]</li><li>Then download the ~~decompressed folder~~ Android image from '''[http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and ~~open it~~-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-img34.png|454x134px]]~~<div class="figure">

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

~~[[File~~</div></ol><ol start="2" style="list-style-type:~~pi3b~~lower-~~img35~~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 and supports 4K display.~~png|442x208px]]~~If you don't use LCD screen, please download the image without lcd</li><li>b) If you want to use lcd screen, please choose image with lcd</li>

[[File:pi3b-img125.png]]

</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 '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li>

[[File:pi3b-img31.png]]

</ol>

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

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

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

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

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

[[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'''"</~~li></ol~~p> [[File:pi3b-img39.png~~|457x215px~~]] ~~<ol start="6" style="list-style-type: lower-alpha;"><li>Then insert the TF card into the development board~~</li><li>Then please select '''~~advanced features~~Advanced Features'''[[File:pi3b-img126.png~~|458x138px~~]]</li>

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

[[File:pi3b-img127.png~~|459x216px~~]]~~</li><li>Then select '''rk3566_MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and click to open~~</li></ol>

<~~div class~~ol start="~~figure~~8"style="list-style-type: lower-alpha;"><li>Select '''rk3566_MiniLoaderAll.bin''' in the MiniLoader folder downloaded earlier, and click to open.</li>

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

~~</div>~~

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

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

~~[[File:pi3b-img128.png|472x222px]]</li>~~

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

~~[[File:pi3b-img129.png|474x227px]]</li>~~

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

[[File:pi3b-~~img130~~img68.png~~|477x222px|D~T2CO%X~K2@ELR98)BVP~2~~]]

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

~~<div class="figure">~~ [[File:pi3b-~~img131~~img142.png~~|474x223px|QFVLTK~19N32OK2UGH{D{AK~~]]</ol><ol start="13" style="list-style-type: lower-alpha;"><li>Then click the "'''Upgrade Firmware'''" column of the burning tool</li>

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

<li>Then click the "'''~~Upgrade~~ Firmware'''" ~~column~~ button to select the path of the ~~burning tool~~Android image that needs to be burned</li>~~</ol>~~ ~~[[File:pi3b-img132.png|477x224px]]~~

[[File:pi3b-img133.png]]

</ol>

<li>~~Then~~ Finally, click the "'''~~Firmware~~Upgrade'''" button to ~~select~~ start burning, and the ~~path of~~ log during the burning process is shown in the figure below. After burning is completed, the Android ~~image that needs to be burned~~system will start automatically.</li~~></ol~~>

~~[[File:pi3b-img133.png|444x209px]]~~<div class="figure">

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

</div ~~class~~></ol></li></ol>

~~[[File:pi3b-img134.png|455x214px|GO~ZSPN`B]JCQM`@_9UU8[R]]~~=== How to burn Android11 image into eMMC via TF card ===

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

~~<ol style="list-style-type: decimal;"><li>First prepare a TF card with 8GB or larger capacity.~~ # The ~~transmission speed of the TF card must be class10 or above~~development board reserves an eMMC expansion interface. ~~It is recommended to use a TF card of SanDisk and other brands</li><li>Then use~~ Before programming the ~~card reader~~ system 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''']~~eMMC, ~~'''please make sure~~ you first need to purchase an eMMC module that matches the ~~version~~ eMMC interface of the ~~SDDiskTool tool is the latest v1.72~~development board.~~'''</li><li>~~Then ~~download '''~~install the ~~Android11 image from~~ eMMC module to the ~~Orange Pi download''' '''page'''<ol style="list-style-type: lower-alpha;"><li>After opening~~ development board. The eMMC module and the ~~download link~~ method of plugging into 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>~~development board are as follows:

~~<blockquote><div class="figure">~~::[[File:pi3b-img61.png|400px]] [[File:pi3b-img62.png|400px]]

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

~~</div></blockquote>~~<ol start="2" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~After entering~~ 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 '''~~TF card and eMMC boot image~~Orange Pi data download page''' ~~folder~~], ~~you can see~~ '''please make sure that the ~~following two images,~~ version of the ~~difference between them~~ SDDiskTool tool is:the latest v1.72'''</lip></olli> <!li>Then download the Android image from [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and- support/Orange-Pi-3B.html '''Orange Pi's download page''']

<li>~~The~~ After opening the download link of the Android image ~~without lcd is specially used for HDMI display and supports 4K display. If~~ , you ~~do not use~~ can see the ~~LCD screen~~following two types of Android images, please ~~download~~ select the image in '''the TF card and eMMC startup image ~~without lcd</li><li>If you want~~ folder''' to ~~use LCD screen, please choose image with lcd~~download</li~~></ol~~>

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

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

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

[[File:pi3b-img125.png]]</ol></li></ol></li></ol><ol start="76" style="list-style-type: decimal;"><li>~~After opening '''SDDiskTool''', if~~ Then use the decompression software to decompress the compressed package of the downloaded Android image. Among the ~~TF card is recognized normally~~decompressed files, the ~~inserted disk device will be displayed in 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 '''~~Select Removable Disk Device~~SDDiskTool_v1.72.zip'''~~" column. P~~, this software does not need to be installed, just find '''~~lease make sure that the displayed disk device is consistent with the drive letter of the TF card you want to burn~~SD_Firmware_Tool.exe'''~~, if there is no display, you can try to unplug~~ in the ~~TF card~~decompressed folder and open it</lip></olli> ~~[[File:pi3b-img136.png|267x228px]]~~

[[File:pi3b-img135.png]]

</ol>

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

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

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

<li>First ~~check~~ confirm that the displayed drive letter is the drive letter corresponding to the TF card under "'''Select Removable Disk Device'''"</li><li>Then select "~~SD Boot~~'''Firmware Upgrade'''" in "'''Select Function Mode'''"</li><li>Then select the path of the Android ~~image~~ firmware in the "'''Select ~~to upgrade firmware~~Upgrade Firmware'''" column</li><li>Finally click the "'''Start Create'''" button to start burning ~~the Android image to the TF card~~</li> [[File:pi3b-img143.png]]</ol>

</li></ol>

<li>After the burning is completed, the display is as shown in the figure below, and then you can exit SDDiskTool</li>

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

[[File:pi3b-img145.png]]</ol><ol start="1014" style="list-style-type: decimal;"><li>~~After~~ When the HDMI monitor displays the following information, it means that the burningof the Android image into the eMMC has been completed. At this time, ~~you~~ the TF card can ~~exit the SDDiskTool software~~be pulled out, and then ~~you can pull out the TF card from~~ the ~~computer and insert it into~~ Android system in the ~~development board to~~ eMMC will start.</li~~></ol~~>

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

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

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note~~, after burning the image into eMMC, if the test finds~~ that ~~it cannot be started, please clear~~ all the ~~SPIFlash and try again. For the method of clearing SPIFlash, please refer to''' [[\l|the method of using RKDevTool to clear SPIFlash]]'''~~following operations are performed on a Windows computer.''' ~~~~</~~span~~big>~~=== 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>First, you need to prepare an NVMe SSD solid state drive<ol style="list-style-type: lower-alpha;"><li>The M.~~'''~~2 2230 SSD is as follows</li>

[[File:pi3b-img73.png]]</ol><ol start="2" style="list-style-type: ~~decimal~~lower-alpha;"><li~~><p~~>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 boardM.~~The eMMC module and the method of plugging into the development board are~~ 2 2242 SSD is as follows~~:~~</li~~></ol~~>

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

[[File:pi3b-~~img63~~img75.png~~|286x133px~~]]</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="24" style="list-style-type: decimal;"><li>You also need to prepare a good quality USB2.0 male-to-male data cable</li~~></ol~~>

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

</div></ol><ol start="35" style="list-style-type: decimal;"><li>Then download Rockchip driver '''DriverAssitant_v5.12.zip''' and burning tool '''RKDevTool_Release_v3.15.zip''' from ~~[http://www.orangepi.org/html/serviceAndSupport/index.html~~ '''Orange Pi's data download page''']</li><li>Then download the ~~Android~~ image ~~from '''[http://www.orangepi.org/html/serviceAndSupport/index.html Orange Pi's download page].'''~~of Android11

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

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

</div>

</ol>

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

</li></ol>

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

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

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

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

[[File:pi3b-img32.png]]

</ol>

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

[[File:pi3b-img33.png]]

</ol>

</li></ol>

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

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

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

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

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

</div></ol>

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

[[File:pi3b-img37.png]]

</ol>

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

[[File:pi3b-img38.png]]

</ol>

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

[[File:pi3b-img39.png]]<~~!-- --~~/ol><ol start="6" style="list-style-type: lower-alpha;"><li>~~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>

<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'''~~Then you can start to clear the content in SPI FLASH<ol style="list-style-type: lower-alpha;"><li>First, if connect the ~~TF card is recognized normally,~~ development board to the ~~inserted disk device will be displayed in~~ Windows computer through the ~~"'''Select Removable Disk Device'''" column~~USB2.0 male-to-male data cable. ~~'''Please make sure that~~ The position of the ~~displayed disk device is consistent with the drive letter~~ USB2.0 programming port of the ~~TF card you want to burn''', if there~~ development board is ~~no display, you can try to unplug~~ shown in the ~~TF card.~~figure below</li~~></ol~~>

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

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

~~[[File~~</div></ol><ol start="2" style="list-style-type:~~pi3b~~lower-~~img137.png|247x212px]]~~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>

~~<ol start="10" style="list~~[[File:pi3b-~~style-type: decimal;">~~img37.png]]~~<li>Then start to write the Android image into the TF card~~</pol><ol start="4" style="list-style-type: lower-alpha;"><li~~>First confirm that the displayed drive letter is the drive letter corresponding to the TF card under "'''Select Removable Disk Device'''"</li><li><p~~>Then ~~select "'''Firmware Upgrade'''" in "'''Select Function Mode'''"</li><li>Then select~~ connect the ~~path~~ power supply of the ~~Android firmware in~~ Type-C interface to the ~~"'''Select Upgrade Firmware'''" column</li><li>Finally click~~ development board, and power on, and then release the ~~"'''Start Create'''"~~ MaskROM button ~~to start burning~~</li~~></ol></li></ol~~>

[[File:pi3b-~~img143~~img38.png~~|290x246px~~]]</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="116" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~After the burning is completed,~~ Then please select '''Advanced Features'''[[File:pi3b-img126.png]]</li><li>Then click the ~~display is as~~ position shown in the figure below[[File:pi3b-img127.png]]</li><li>Select '''rk3566_MiniLoaderAll.bin''' in the '''MiniLoader''' folder you downloaded earlier, and ~~then you can exit SDDiskTool~~click Open</lip></olli>

~~[[File:pi3b-img144.png|285x243px]]~~<div class="figure">

~~<ol start="12" style="list-style~~[[File:pi3b-~~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 boardimg68.~~</li><li>If the development board is connected to an HDMI display, you can also see the progress bar of burning the Android image to eMMC from the HDMI display</li></ol>~~png]]

</div></ol><ol style="list-style-type: lower-roman;"><li>Then click '''Download'''[[File:pi3b-~~img145~~img128.png~~|430x247px~~]]</li></ol>

<ol start="1410" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~When~~ The display after downloading '''rk3566_MiniLoaderAll.bin''' is shown in the ~~HDMI monitor displays~~ figure below[[File:pi3b-img140.png]]</li><li>Then select the ~~following information, it means that the burning of the Android image into the eMMC has been completed~~storage device as '''SPINOR'''[[File:pi3b-img151.png]]</li><li>Then click Switch '''Storage'''[[File:pi3b-img152.png]]</li><li>Then click '''Erase All''' to start erasing SPIFlash[[File:pi3b-img153. ~~At this time, the TF card can be pulled out, and then the Android system~~ png]]</li><li>The display log after erasing SPIFlash is shown in the ~~eMMC will start~~figure below[[File:pi3b-img154.png]]</li></ol></li></ol>

~~[[File:pi3b-img146.png|576x389px]]~~== Start the Orange Pi development board ==

~~<span id="how~~# Insert the TF card with the burned image into the TF card slot of the Orange Pi development board. If the image of SPIFlash+NVMe SSD has been burnt, then there is no need to insert a TF card, just make sure that the NVMe SSD is inserted into the development board normally.# The development board has an HDMI interface, and the development board can be connected to a TV or HDMI display through an HDMI-to-~~burn~~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-~~android-image~~C to HDMI cable, the system interface of the development board can also be displayed through the Type-C interface.# Connect a USB mouse and keyboard tocontrol the Orange Pi development board.# The development board has an Ethernet port, which can be plugged into a network cable for Internet access.# Connect a high-~~spiflashnvme~~quality power adapter with a 5V/3A USB Type-~~ssd">== How to burn Android image to SPIFlash+NVMe SSD ==~~C interface.

::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~Note that all~~ Remember not to plug in a power adapter with a voltage output greater than 5V, as this will burn out the ~~following operations are performed on a Windows computer~~development board.'''

'''<ol span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>First~~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 ~~need to prepare an NVMe SSD solid state drive<ol style="list-style-type: lower~~find that there is a phenomenon of continuous restart during the startup process, please replace the power supply or the Type-~~alpha;"><li>The M~~C data cable and try again.~~2 2230 SSD is as follows</li></ol></li>~~'''</olspan>

~~[[File~~'''The Type-~~img73~~C power port does not support PD negotiation.~~png|147x106px]]~~'''

'''<~~ol start="2"~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<li>The M~~In addition, please do not connect the USB interface of the computer to power the development board.~~2 2242 SSD is as follows~~'''</lispan></olbig>|}

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

~~<ol start="2" style="list-style-type: decimal;">~~<li>~~Then insert~~ If you want to view the output information of the system through the ~~NVMe SSD into~~ debugging serial port, please use the Mserial cable to connect the development board to the computer.~~2 PCIe interface~~ For the connection method of the ~~development board and fix it~~serial port, please refer to '''[[Orange Pi 3B#How to use the debugging serial port|the section on how to use the debugging serial port]].'''</li></ol>

~~[[File:pi3b-img75.png|283x63px]]~~== How to use the debugging serial port ==

<~~ol start~~span id="~~3" style="list~~connection-instruction-of-debugging-~~style~~serial-~~type: decimal;~~port"><li/span>~~The position~~ === Connection instruction 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>~~debugging serial port ===

~~[[File:pi3b-img76.png|266x211px]]~~ <ol ~~start="4"~~ style="list-style-type: decimal;"><li>~~You also~~ First, you need to prepare a ~~good quality USB2~~3.~~0 male~~3V USB-to-~~male data cable~~TTL module, and then insert the USB interface end of the USB-to-TTL module into the USB interface of the computer.{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''For better compatibility, it is recommended to use CH340 USB to TTL module, please do not use CP2102, PL2303 USB to TTL module.'''</lip>'''Before purchasing a USB to TTL module, please confirm that the module supports a baud rate of 1500000.'''</olbig>|}

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

</div>~~<ol start="5" style="list-style-type: decimal;"><li>Then download Rockchip driver '''DriverAssitant_v5.12.zip''' and burning tool '''RKDevTool_Release_v3.15.zip''' from '''Orange Pi's data download page'''</p~~></li>~~<li>Then download the image of Android11~~</pol><ol start="2" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~After opening the download link~~ The corresponding relationship between GND, RXD and TXD pins of the ~~Android image, you can see the following two types~~ debugging serial port of ~~Android images, please select~~ the ~~image~~ development board is shown in the ~~S'''PIFlash-NVME SSD boot image folder''' to download</li></ol>~~figure below</li~~></ol~~>

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

~~[[File~~:~~pi3b-img124~~a.~~png|340x108px|e6986fc9c8fc078e8cb6a9c39b76fb8]]~~Connect the GND of the USB to TTL module to the GND of the development board

~~</div><ol start="2" style="list-style-type~~: ~~lower-alpha;"><li>After entering the~~ b. The '''~~SPIFlash-NVME SSD boot image folder''', you can see the following two images. Their differences are:~~<~~/p><ol~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<li>The image without lcd~~ RX of the USB to TTL module is ~~specially used for HDMI display and supports 4K display. If you do not use~~ connected to the ~~LCD screen, please download the image without lcd~~TX</~~p></li><li>If you want to use LCD screen, please choose image with lcd</li></ol></li></ol~~span>''' of the development board

~~[[File~~:~~pi3b~~c. The '''TX of the USB to TTL module is connected to the TX''' of the development board</ol><ol start="4" style="list-~~img147.png|305x58px]]~~style-type: decimal;"><li>The schematic diagram of connecting the USB to TTL module to the computer and the Orange Pi development board is as follows</li>

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

[[File:pi3b-~~img31~~img157.png~~|407x120px~~]]

<~~ol start~~/div>{| class="8wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~After opening~~ '''~~DriverInstall~~The TX and RX of the serial port need to be cross-connected.~~exe''~~If you don't want to carefully distinguish the order of TX and RX, you can connect the ~~steps to install~~ TX and RX of the serial port casually first. If there is no output in the test, then exchange the ~~Rockchip driver are as follows<ol style="list-style-type: lower-alpha;"><li>Click~~ order of TX and RX, so there is always a the ~~"~~order is right'''~~Driver Installation'''" button~~</libig>|}</ol><~~/li~~span id="how-to-use-the-debugging-serial-port-on-the-ubuntu-platform"></olspan>

~~[[File:pi3b-img32.png|286x150px]]~~=== How to use the debugging serial port on the Ubuntu platform ===

~~<ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~After waiting for a period of time, a pop-up window will prompt "~~'''~~driver installed successfully'''"~~There are many serial port debugging software that can be used under Linux, such as putty, minicom, ~~and then click the "'~~etc. The following demonstrates how to use putty.''OK'~~''" button.~~</~~li></ol~~big>|}

~~[[File:pi3b~~# First, insert the USB-~~img33~~to-TTL module into the USB interface of the Ubuntu computer. If the connection and recognition of the USB-to-TTL module is normal, you can see the corresponding device node name under '''/dev''' on the Ubuntu PC.~~png|296x154px]]~~Remember this node name, and then set the serial port software will be used

~~<ol start~~::{| class="9wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then decompress~~ |-| test@test:~$ '''~~RKDevTool_Release_v3.15.zip~~ls /dev/ttyUSB*'''~~, this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li></ol>~~

~~[[File~~/dev/ttyUSB0|} <ol start="2" style="list-style-type: decimal;"><li>Then use the following command to install putty on Ubuntu PC</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt-get update''' test@test:~~pi3b~~~$ '''sudo apt-get install -~~img34.png~~y putty'''|~~413x122px]]~~}</ol><ol start="3" style="list-style-type: decimal;"><li>Then run putty, '''remember to add sudo permission'''</li>

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo putty'''|}</ol><ol start="104" style="list-style-type: decimal;"><li>After ~~opening~~ executing the ~~'''RKDevTool''' burning tool~~putty command, ~~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~~ following interface will ~~prompt "'''No device found'''"~~pop up</li~~></ol~~>

[[File:pi3b-~~img35~~img158.png~~|402x189px~~]]</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="116" style="list-style-type: decimal;"><li>Then ~~start burning~~ set the parameters of the ~~Android image to SPIFlash+NVMe SSD~~serial port

<li>~~First,~~ Set Serial line to connect ~~the development board~~ toas /dev/ttyUSB0（(Modified to the ~~Windows computer through the USB2.0 male-to-male data cable. The position of the USB2.0 programming~~ corresponding node name, generally /dev/ttyUSB0）</li><li>Set Speed(baud) as '''1500000'''（Serial port ~~of the development board is shown in the figure below~~baud rate）</lip></olli><li>Set Flow control as None</lip></olli>

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

</div></ol></li></ol><ol start="27" style="list-style-type: decimal;"><li>After setting the setting interface of the serial port, return to the Session interface<ol style="list-style-type: lower-alpha;"><li>~~Make sure that~~ First select the ~~development board is not inserted into the TF card and not connected to the power supply~~Connection type as Serial</li><li>Then ~~press and hold~~ click the ~~MaskROM~~ Open button ~~on the development board, the position of~~ to connect to the ~~MaskROM button on the development board is shown in the figure below:~~serial port</li~~></ol~~>

~~[[File:pi3b-img37.png|289x100px]]~~<div class="figure">

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

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

[[File:pi3b-img162.png]]</ol ~~start~~><li>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~~span>

~~[[File:pi3b-img39.png|443x208px]]~~=== How to use the debugging serial port on Windows platform ===

~~<ol start~~{| class="6wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~Then click the "~~'''~~Upgrade Firmware~~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.'''~~" column of the burning tool~~</~~li></ol~~big>|}

<ol style="list-style-type: decimal;"><li>Download MobaXterm<ol style="list-style-type: lower-alpha;"><li>Download MobaXterm website as follows</li>{| class="wikitable" style="width:800px;" |-| [~~[File~~https://mobaxterm.mobatek.net/ '''https:~~pi3b-img132~~//mobaxterm.mobatek.~~png|442x208px]~~net''']|}</ol><ol start="72" style="list-style-type: lower-alpha;"><li>~~Then~~ After entering the MobaXterm download page, click ~~the "~~'''~~Firmware~~GET XOBATERM NOW!'''~~" button to select the Android image to be burned~~</li~~></ol~~>

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

[[File:pi3b-img164.png]]</ol><ol start="84" style="list-style-type: lower-alpha;"><li>~~Finally, click~~ Then select the ~~"Upgrade" button to start burning~~Portable version. ~~The burning process is shown in the figure below. You can see that the firmware will be burned~~ After downloading, you don't need to ~~SPIFlash first~~install it, just open it and ~~then burned to PCIE. After burning is completed, the Android system will start automatically.~~use it</li~~></ol~~>

[[File:pi3b-~~img148~~img165.png~~|453x212px~~]]</ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>After downloading, use decompression software to decompress the downloaded compressed package, you can get the executable software of MobaXterm, and then double-click to open</li>

[[File:pi3b-img166.png]]</ol><~~span id~~ol start="~~using~~3" style="list-~~rkdevtool~~style-type: decimal;"><li>After opening the software, the steps toset up the serial port connection are as follows<ol style="list-~~clear~~style-~~spiflash~~type: lower-alpha;"><li>Open the session settings interface</li><li>Select the serial port type</li><li>Select the port number of the serial port (select the corresponding port number according to the actual situation)</li><li>Select the baud rate of the serial port as '''1500000'''</~~span~~li>~~== Using RKDevTool~~ <li>Finally click the "'''OK'''" button to ~~clear SPIFlash ==~~complete the setting</li>

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

[[File:pi3b-~~img76~~img167.png~~|263x193px~~]]

</div></ol></li></ol><ol start="24" style="list-style-type: decimal;"><li>~~First~~After clicking the "'''OK'''" button, you ~~need to prepare a good quality USB2~~will enter the following interface.~~0 male-to-male data cable~~At this time, start the development board and you can see the output information of the serial port</li~~></ol~~>

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

</div></ol><~~ol start~~span id="~~3" style="list~~instructions-for-~~style~~using-~~type: decimal;"><li>Then download~~ the ~~Rockchip driver '''DriverAssitant_v5.12.zip''' and MiniLoader and~~ -5v-pin-in-the ~~burning tool '''RKDevTool_Release_v3.15.zip''' from~~ -40pin-interface-of-the ~~[http://www.orangepi.org/html/serviceAndSupport/index.html '''Orange Pi data download page''']<ol style="list~~-~~style~~development-board-to-~~type: lower~~supply-~~alpha;~~power">~~<li>On the download page of Orange Pi, first select the official tool, and then enter the following folder</li></ol>~~</~~li></ol~~span>

~~<div class~~=~~"figure">~~= Instructions for using the 5v pin in the 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-~~img149~~C power interface of the development board for power supply.~~png|342x56px~~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.'''</big>|~~1691401357374]]~~}

~~</div><ol start="2" style="list-style-type: lower-alpha;"><li>Then download all~~ # First, you need to prepare a power cord as shown in the ~~files~~ figure below~~</li></ol>~~

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

</div>

::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~Note that the "MiniLoader-things needed to burn~~ Please purchase the ~~Linux image" folder is hereinafter referred to as~~ power cord shown in the ~~MiniLoader folder.~~picture above by yourself'''</big>|}

<ol start="42" style="list-style-type: decimal;"><li>~~Then use decompression software~~ Use the 5V pin in the 40pin interface to ~~decompress~~ supply power to the development board. The connection method of the power line is as follows<ol style="list-style-type: lower-alpha;"><li>The USB A port of the power cord shown in the above picture needs to be plugged into the 5V/3A power adapter connector ('''please do not plug into the computer'~~DriverAssitant_v5.12.zip~~s USB port for power supply''', )</li><li>The red DuPont line needs to be plugged into the 5V pin of the development board 40pin</li><li>The black Dupont wire needs to be inserted into the GND pin of the 40pin interface</li><li>The position of the 5V pin and ~~then find~~ GND pin of the 40pin interface on the development board is shown in the figure below, '''~~DriverInstall.exe~~remember not to reverse the connection''' ~~executable file in the decompressed folder and open it~~</lip></olli> ~~[[File:pi3b-img31.png|472x139px]]~~

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

</li></ol>

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

~~<ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~After waiting for a period of time, a pop-up window will prompt "~~'''~~driver installed successfully'''",~~ The content of this chapter is written based on the images of the Linux server version and ~~then click~~ the ~~"'''OK~~xfce desktop version.'''~~" button.~~</~~li></ol~~big>|}

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

~~<ol start~~{| class="6wikitable" style="~~list-style~~width:800px;text-~~type~~align: ~~decimal~~center;">~~<li>Then decompress~~ |-|'''Linux image type'''|'''kernel version'''|'''server version'''|'''desktop version'''|-|'''Debian 11 - Bullseye'''|'''Linux5.10'''|'''support'''|'''support'''|-|'''Ubuntu 20.04 - Focal'''|'''Linux5.10'''|'''support'''|'''support'''~~RKDevTool_Release_v3~~|-|'''Ubuntu 22.1504 - Jammy'''|'''Linux5.~~zip~~10'''~~, this software does not need to be installed, just find~~ |'''~~RKDevTool~~support''' ~~in the decompressed folder and open it</li></ol>~~|'''support'''|}

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

~~<ol start~~{| class="7wikitable" style="~~list-style~~width:800px;text-~~type~~align: ~~decimal~~center;">~~<li>After opening the~~ |-|'''Function'''|'''Debian11'''|'''Ubuntu20.04'''|'''Ubuntu22.04'''~~RKDevTool~~|-|''' ~~burning tool, because the computer has not connected to the development board through the~~ USB2.~~0 male~~0x3'''|'''OK'''|'''OK'''|'''OK'''|-|'''USB3.0x1'''|'''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'''|'''OK'''|'''OK'''|'''OK'''|-|'''3pin Debug serial port'''|'''OK'''|'''OK'''|'''OK'''|-|'''EMMC'''|'''OK'''|'''OK'''|'''OK'''|-|'''TF card start'''|'''OK'''|'''OK'''|'''OK'''|-|'''HDMI Video'''|'''OK'''|'''OK'''|'''OK'''|-|'''HDMI Audio'''|'''OK'''|'''OK'''|'''OK'''|-|'''Camera'''|'''OK'''|'''OK'''|'''OK'''|-|'''LCD'''|'''OK'''|'''OK'''|'''OK'''|-|'''Edp Display'''|'''OK'''|'''OK'''|'''OK'''|-|'''Gigabit Ethernet port'''|'''OK'''|'''OK'''|'''OK'''|-|'''Network port status light'''|'''OK'''|'''OK'''|'''OK'''|-|'''headphone playback'''|'''OK'''|'''OK'''|'''OK'''|-|'''headphone recording'''|'''OK'''|'''OK'''|'''OK'''|-|'''LED Light'''|'''OK'''|'''OK'''|'''OK'''|-|'''RTC'''|'''OK'''|'''OK'''|'''OK'''|-|'''GPU'''|'''OK'''|'''OK'''|'''OK'''|-|'''NPU'''|'''OK'''|'''OK'''|'''OK'''|-|'''VPU'''|'''OK'''|'''OK'''|'''OK'''|-to|'''watchdog test'''|'''OK'''|'''OK'''|'''OK'''|-~~male data cable at this time, the lower left corner will prompt "~~|'''Chromium Hard solution video'''|'''OK'''|'''OK'''|'''~~No device found~~OK'''~~"</li></ol>~~|}

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

# In this manual, all commands that need to be entered in the Linux system will be marked with the following box::{| class="wikitable" style="width:800px;height:40px;" |-| |}::As shown below, the content in the yellow box indicates the content that needs special attention, except for the commands in it.::{| class="wikitable" style="background-color:#ffffdc;width:800px;height:40px;" |-| |}<ol start="82" style="list-style-type: decimal;"><li>~~Then you can start to clear~~ Description of the ~~content~~ prompt type in ~~SPI FLASH~~front of the command

<li>~~First, connect~~ The prompt in front of the ~~development board~~ command refers to the ~~Windows computer through~~ content of the red part in the ~~USB2.0 male-to-male data cable. The position~~ box below, which is not part of the ~~USB2.0 programming port of~~ Linux command, so when entering the ~~development board is shown~~ command in the ~~figure below~~Linux system, please do not enter the content of the red font part</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| '''<~~/li~~span style="color:#FF0000">orangepi@orangepi:~$</olspan>sudo apt update'''

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

'''test@test:~$ ssh [~~[File~~mailto:~~pi3b-img36~~root@192.168.~~png|275x116px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\1691131157154(~~1).~~jpg1691131157154(~~36 root@192.168.1)].]xxx'''

'''root@test:~# ls'''|}</~~div~~ol>

<li>~~Make sure~~ '''root@orangepi:~$''' The prompt indicates that this command is entered in '''the Linux system of the development board '''. The $ at the end of the prompt indicates that the current user of the system is a normal user. When executing a privileged command, you need to add '''sudo'''</li><li>'''root@orangepi:~#''' The prompt indicates that this command is ~~not inserted into~~ entered in the Linux system of the ~~TF card~~ development board, and ~~not connected to~~ the ~~power supply~~# 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>~~Then press and hold~~ '''test@test:~$''' The prompt indicates that this command is entered in the ~~MaskROM button on~~ Ubuntu PC or Ubuntu virtual machine, not in the Linux system of the development board. The $ at the end of the prompt indicates that the current user of the system is an ordinary user. When executing privileged commands, sudo needs to be added '''sudo'''</li><li>'''root@test:~#''' The prompt indicates that this command is entered in the Ubuntu PC or Ubuntu virtual machine, not in the ~~position~~ Linux system of ~~the MaskROM button on~~ the development board . The # at the end of the prompt indicates that the current user of the system is ~~shown in~~ the ~~figure below:~~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 output content (some commands have output, some may not), and this part of the content does not need to be input</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''cat /boot/orangepiEnv.txt'''

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

~~<ol start~~bootlogo=~~"4" style="list-style-type: lower-alpha;"><li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button</li></ol>~~false

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

~~<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~~ "deb [arch=$(dpkg --print-architecture) \'''~~found a MASKROM device'''"</li></ol>~~

~~[[File:pi3b~~'''signed-~~img39~~by=/usr/share/keyrings/docker-archive-keyring.~~png|457x215px]~~gpg]\'''

~~<ol start="6" style="list-style-type: lower-alpha;"><li>Then please select '''Advanced Features~~'''~~[[File~~https:~~pi3b-img126.png|458x138px]]<~~/~~p><~~/~~li><li>Then click the position shown in the figure below[[File:pi3b-img127~~download.docker.~~png|459x216px]]<~~com/~~p><~~Linux/~~li><li>Select '''rk3566_MiniLoaderAll.bin''~~debian \' ~~in the~~ ''~~'MiniLoader''' folder you downloaded earlier, and click Open</li></ol>~~

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

~~[[File:pi3b-img68.png|459x216px|SIS5H0S2@F5M2D(6ANZEUPG]]~~== Linux system login instructions ==

<~~/div><ol style~~span id="~~list~~linux-system-default-login-~~style~~account-~~type: lower~~and-~~roman;~~password">~~<li>Then click '''Download'''~~</pspan>~~[[File:pi3b-img128.png|472x222px]]</li></ol>~~=== Linux system default login account and password ===

~~<ol start~~{| class="10wikitable" style="~~list-style~~width:800px;text-~~type~~align: ~~lower-alpha~~center;">~~<li>The display after downloading~~ |-|'''~~rk3566_MiniLoaderAll.bin~~Account''' ~~is shown in the figure below[[File:pi3b-img140.png~~|~~474x223px]]</li><li>Then select the storage device as~~ '''~~SPINOR~~Passport'''~~[[File:pi3b~~|-~~img151.png~~|~~467x220px]]</li>~~'''root'''~~<li>Then click Switch~~ |'''~~Storage~~orangepi'''~~[[File:pi3b~~|-~~img152.png~~|~~464x218px]]</li><li>Then click~~ '''~~Erase All~~orangepi''' ~~to start erasing SPIFlash[[File:pi3b-img153.png~~|~~467x220px]]</li><li>The display log after erasing SPIFlash is shown in the figure below~~'''orangepi'''~~[[File:pi3b-img154.png~~|~~460x216px]]</li></ol>~~}

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that when entering the password, the specific content of the entered password will not be displayed on the screen, please do not think that there is any fault, just press Enter after inputting.'''</big>|}{| class="wikitable" style= ~~Start~~ "background-color:#ffffdc;width:800px;" |-| <big>'''When the wrong password is prompted, or there is a problem with the ssh connection, please note that as long as you are using the Linux image provided by Orange Pi ~~development board =~~, please do not suspect that the above password is wrong, but look for other reasons.'''</big>|}

~~# 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~~ <span id="how-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~~-toset-automatic-terminal-~~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~~login-~~C to HDMI cable, the system interface of the development board can also be displayed through the Type~~in-~~C interface.# Connect a USB mouse and keyboard to control the Orange Pi development board.# The development board has an Ethernet port, which can be plugged into a network cable for Internet access.# Connect a high~~linux-~~quality power adapter with a 5V~~system"></~~3A or 5V/4A USB Type-C interface.~~span>

~~'''Remember not~~ === How to ~~plug~~ set automatic terminal login in ~~a power adapter with a voltage output greater than 5V, as this will burn out the development board.'''~~Linux system ===

~~'''Many unstable phenomena during~~ # The Linux system automatically logs in to the ~~power-on~~ terminal by default, and ~~start-up process of~~ the ~~system are basically caused by power supply problems, so a reliable power adapter~~ default login user name is ~~very important. If you find that there is a phenomenon of continuous restart during the startup process, please replace the power supply or the Type-C data cable and try again.~~'''orangepi'''

~~'''The Type~~::[[File:pi3b-~~C power port does not support PD negotiation~~img171.~~'''~~png]]

<ol start="2" style="list-style-type: decimal;"><li>Use the following command to set the root user to automatically log in to the terminal</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo auto_login_cli.sh root'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Use the following command to disable automatic login terminal</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo auto_login_cli.sh -d'~~In addition, please do not connect~~ ''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Use the ~~USB interface of~~ following command to set the ~~computer~~ orangepi user to automatically log in to ~~power~~ the ~~development board~~terminal again</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo auto_login_cli.sh orangepi'''|}</ol>

~~6) Then turn on the switch~~ === Instructions for automatic login of ~~the power adapter. If everything is normal, you can see the startup screen of the~~ Linux desktop version system ~~on the HDMI monitor or LCD screen.~~===

~~7) If you want to view the output information of~~ # After the desktop 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]].''' ~~== How to use the debugging serial port ==~~ ~~=== Connection instruction of debugging serial port ===~~ ~~<ol style="list-style-type: decimal;"><li>First, you need to prepare a 3.3V USB-to-TTL module, and then insert the USB interface end of the USB-to-TTL module into the USB interface of the computer.'''For better compatibility~~starts, it ~~is recommended~~ will automatically log in 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~~ desktop without entering a ~~baud rate of 1500000.'''</li></ol>~~password

::[[File:pi3b-~~img155~~img172.png~~|576x115px|07~~]]

</div>

<li>~~The corresponding relationship between GND, RXD and TXD pins of~~ Run the ~~debugging serial port of~~ following command to prohibit the ~~development board is shown in~~ desktop system from automatically logging into the ~~figure below~~desktop</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| ~~[[File~~orangepi@orangepi:~~pi3b-img156~~~$ '''sudo disable_desktop_autologin.~~png~~sh'''|~~428x110px]]~~}</ol>

<li>~~The GND, TXD~~ Then restart the system and ~~RXD pins of the USB to TTL module need to be connected to the debugging serial port of the development board through~~ a ~~DuPont line</li></ol>~~ ~~<blockquote>~~login dialog box will appear, at which point a~~. Connect the GND of the USB to TTL module to the GND of the development board~~ ~~b. The '''RX of the USB to TTL module~~ [[\l|password]] is ~~connected~~ required to enter the ~~TX''' of the development board~~ ~~c. The '''TX of the USB to TTL module is connected to the TX''' of the development board</blockquote><ol start="4" style="list-style-type: decimal;"><li>The schematic diagram of connecting the USB to TTL module to the computer and the Orange Pi development board is as follows</li>~~system</olp>

[[File:pi3b-~~img157~~img173.png~~|524x189px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\USB-to-TTL-module-to-the-computer.jpgUSB-to-TTL-module-to-the-computer~~]]

</div>'''The TX and RX of the serial port need to be cross-connected. If you don’t want to carefully distinguish the order of TX and RX, you can connect the TX and RX of the serial port casually first. If there is no output in the test, then exchange the order of TX and RX, so there is always a the order is right'''</li></ol>

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

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

# ~~First, insert~~ Execute the ~~USB-~~following command to~~-TTL module into the USB interface of the Ubuntu computer. If~~ set the ~~connection and recognition of the USB-~~desktop system 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~~ automatically log in as the ~~serial port software will be used~~root user

~~test~~::{| class="wikitable" style="width:800px;" |-| orangepi@~~test~~orangepi:~$ '''ls /dev/ttyUSB*sudo desktop_login.sh root''' ~~/dev/ttyUSB0~~|}

<li>Then ~~use~~ restart the ~~following command~~ system, and the root user will automatically log in to ~~install putty on Ubuntu PC~~the desktop</li~~></ol~~>

~~test@test~~[[File:~~~$ '''sudo apt~~pi3b-~~get update'''~~img174.png]]

~~test@test~~{| class="wikitable" style="background-color:~$ #ffffdc;width:800px;" |-| <big>'''~~sudo apt-get install -y putty~~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.'''

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

|}

</ol>

<li>~~Then run putty, '''remember~~ Execute the following command to ~~add sudo permission'''~~set the desktop system to log in automatically with the orangepi user again</li~~></ol~~>

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

~~<ol start~~=~~"4" style~~=~~"list-style-type: decimal;"><li>After executing~~ = The method of disabling the ~~putty command,~~ desktop in the ~~following interface will pop up</li></ol>~~Linux desktop version system ===

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

~~<ol start~~::{| class="5wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>First select the setting interface of the serial port</li></ol>~~|-| orangepi@orangepi:~$ '''sudo systemctl disable lightdm.service'''|}

~~[[File~~<ol start="2" style="list-style-type:~~pi3b-img159.png|359x352px]]~~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'''|}</ol><ol start="63" style="list-style-type: decimal;"><li>~~Then set~~ The steps to reopen the ~~parameters of the serial port~~desktop are as follows:<ol style="list-style-type: lower-alpha;"><li>First enter the following command on the command line, '''<pspan style="color:#FF0000">~~Set Serial line to connect toas /dev/ttyUSB0（(Modified~~ Please remember to ~~the corresponding node name, generally /dev/ttyUSB0）~~add sudo permission</pspan>'''</li>~~<li>Set Speed(baud) as~~ {| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~1500000~~sudo systemctl start lightdm.service'''~~（Serial port baud rate）~~|}</pol><~~/li~~ol start="2" style="list-style-type: lower-alpha;"><li>~~Set Flow control as None~~After the command is executed, the desktop will be displayed</li></ol>

</li></ol>

<~~div class~~span id="~~figure~~onboard-led-light-test-instructions">

~~[[File:pi3b-img160.png|317x312px|09]]~~== Onboard LED Light Test Instructions ==

~~</div><ol start="7" style="list-style-type: decimal;"><li>After setting~~ # There are three LED lights on the ~~setting interface of the serial port~~development board, one green light, one red light, ~~return to~~ and one PCIe light. The location is shown in the ~~Session interface<ol style="list-style-type~~figure below: ~~lower-alpha;"><li>First select the Connection type as Serial</li><li>Then click the Open button to connect to the serial port</li></ol></li></ol>~~

::[[File:pi3b-~~img161~~img175.png~~|345x340px|10~~]]

</div>

<ol start="82" style="list-style-type: decimal;"><li>~~After starting~~ '''As long as the development boardis powered on, ~~you can see~~ the ~~Log information output~~ red LED light will always be on, which is controlled by the ~~system from~~ hardware and cannot be turned off by the ~~opened serial port terminal~~software'''</lip></olli> ~~[[File:pi3b-img162~~<li>The green LED light will keep blinking after the kernel is started, which is controlled by software.~~png|468x340px]]~~</li><~~span id="how-to-use-~~li>The PCIe indicator will flash when there is data transmission on the~~-debugging-serial-port-on-windows-platform"~~PCIe interface.</~~span~~li>~~=== How to use~~ <li>The method of setting the ~~debugging serial port~~ green light on ~~Windows platform =~~and off and flashing is as follows{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~There are many serial port debugging software~~ Note that ~~can~~ the following operations should be ~~used~~ performed 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~~the root user.''' <~~ol style="list-style-type: decimal;"~~/big>~~<li>Download MobaXterm~~|}

<li>~~Download MobaXterm website as follows~~First enter the setting directory of the green light</li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-| ~~[https~~root@orangepi:~# '''cd /sys/~~mobaxterm.mobatek.net~~class/ ~~https:~~leds/status_led'''|}</~~mobaxterm.mobatek.net]~~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'''~~</li>~~|}</ol> ~~[[File:pi3b-img163.png|576x334px]]~~

<li>~~Then choose~~ The command to ~~download~~ set the ~~Home version~~green light to be on is as follows</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-~~[[File~~| root@orangepi:~~pi3b~~/sys/class/leds/status_led# '''echo default-~~img164.png~~on > trigger'''|~~353x231px]]~~}</ol>

<li>~~Then select~~ The command to set the ~~Portable version. After downloading, you don’t need~~ green light to ~~install it, just open it and use it~~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-img165.png|575x259px]]~~== Network connection test ==

<~~ol start~~span id="~~2" style="list~~ethernet-~~style~~port-~~type: decimal;~~test">~~<li>After downloading, use decompression software to decompress the downloaded compressed package, you can get the executable software of MobaXterm, and then double-click to open~~</~~li></ol~~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="3wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>After opening the software, the steps to set up the serial port connection are as follows<ol style="list~~|-~~style-type: lower-alpha;"><li>Open the session settings interface</li>~~| ~~<li>Select the serial port type</li><li>Select the port number of the serial port (select the corresponding port number according to the actual situation), if you can’t see the port number, please use '~~orangepi@orangepi:~$ ''~~Driver Master~~'ip addr show eth0'' ~~to scan and install the driver for the USB to TTL serial port chip</li><li>Select the baud rate of the serial port as~~ '~~''1500000'''</li><li>Finally click the "'''OK'''" button to complete the setting</li></ol></li></ol>~~

~~<div class="figure">~~2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

~~[[File~~:~~pi3b-img167.png|575x438px|11]]~~link/ether 4a:fe:2b:3d:17:1c brd ff:ff:ff:ff:ff:ff

:inet '''<~~/div><ol start="4"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">192.168.1.150<li/span>~~After clicking the "~~'''~~OK'''" button, you will enter the following interface~~/24 brd 192.168.1. ~~At this time, start the development board and you can see the output information of the serial port</li></ol>~~255 scope global dynamic noprefixroute eth0

~~<div class="figure">~~::valid_lft 43150sec preferred_lft 43150sec

~~[[File~~:~~pi3b-img168.png|575x291px|12]]~~inet6 fe80::9a04:3703:faed:23be/64 scope link noprefixroute

~~</div>~~::valid_lft forever preferred_lft forever~~== Instructions for using the 5v pin in the 40pin interface of the development board to supply power ==~~|}

::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~The power supply method we recommend for the development board is~~ When using ifconfig to ~~use~~ view the 5V/3A or 5V/4A Type C interface power cord to plug into the Type-C power interface of the development board for power supply. If you need to use the 5V pin in the 40pin interface to power the development boardIP address, ~~please make sure that the power cord and power adapter used can meet~~ if the ~~power supply requirements of the development board. If the use~~ following information is ~~unstable~~displayed, ~~please switch back to the Type-C power supply~~it is because sudo is not added.The correct command is: sudo ifconfig'''</big>

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

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

~~[[File:pi3b-img169.png|151x108px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-7.jpg未标题-7]]~~Command 'ifconfig' is available in the following places

<* /~~div>'''Please purchase the power cord shown in the picture above by yourself'''~~sbin/ifconfig

~~<ol start="2" style="list-style-type: decimal;"><li>Use the 5V pin in the 40pin interface to supply power to the development board. The connection method of the power line is as follows<~~* /p>~~<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~~usr/~~3A or 5V4A power adapter connector ('''please do not plug into the computer’s USB port for power supply''')<~~sbin/~~p></li><li>The red DuPont line needs to be plugged into the 5V pin of the development board 40pin</li><li>The black Dupont wire needs to be inserted into the GND pin of the 40pin interface</li><li>The position of the 5V pin and GND pin of the 40pin interface on the development board is shown in the figure below, remember not to reverse the connection</li></ol></li></ol>~~ifconfig

~~[[File~~The command could not be located because '/sbin:~~pi3b-img170~~/usr/sbin' is not included in the PATH environment variable.~~png|365x71px]]~~

~~= Instructions for use of Ubuntu/Debian Server and Xfce desktop system =~~administrative privileges associated with your user account.

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

<~~span id~~ol start="~~supported-linux-image-types-and~~4" style="list-~~kernel~~style-~~versions~~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>~~== Supported Linux image types and kernel versions ==~~

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

|-

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

|-

|}

== ~~Linux System adaptation~~ == The server image connects to WIFI through commands ====

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

|-

| ~~style="text-align: left;"| '''Function'''| style="text-align: left;"|~~ <big>'''~~Debian11'''| style="text-align: left;"| '''Ubuntu20.04'''| style="text-align: left;"| '''Ubuntu22.04'''~~|-~~| style="text-align: left;"| '''USB2.0x3'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''USB3~~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.~~0x1'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''M.2 NVMe SSD Start'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''WIFI'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Bluetooth'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''GPIO（40pin）'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''UART（40pin）'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''SPI（40pin）'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''I2C（40pin）'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''PWM（40pin）'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''PWM fan interface'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''3pin Debug~~ Because nmtui can only display characters in some 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;"| '''~~software (such as minicom), and cannot display the graphical interface normally. Of course, if the development board is connected to an Ethernet or 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~~display, you can also use the commands demonstrated in this section to connect to the WIFI network.'''</big>

|}

<~~span id~~ol style="~~the~~list-~~format~~style-oftype: decimal;"><li>First log in to the Linux system, there are the following three ways<ol style="list-~~linux~~style-~~commands~~type: lower-alpha;"><li>If the development board is connected with a network cable, you can remotely log in~~-this-manual"~~to the Linux system through ssh</~~span~~li>~~== The format of~~ <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 ~~commands~~ system</li><li>If the development board is connected to the HDMI display, you can log in ~~this manual ==~~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>

~~# In this manual, all commands that need to be entered in the Linux system will be marked with the following box~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''nmcli dev wifi'''|}

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

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

~~'''orangepi@orangepi~~</div></ol><ol start="3" style="list-style-type:~~~$ sudo apt update'''~~decimal;"><li>Then use the nmcli command to connect to the scanned WIFI hotspot, where:</li>

~~'''root@orangepi~~:~~~#'''~~ a. '''~~vim /boot/boot.cmd~~wifi_name'''needs to be replaced with the name of the WIFI hotspot you want to connect to

:b. '''~~test@test:~$ ssh [mailto:root@192.168.1.36 root@192.168.1.]xxx~~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:~$ '''~~root@test~~nmcli dev wifi connect wifi_name password wifi_passwd'''

Device 'wlan0' successfully activated with 'cf937f88-ca1e-4411-bb50-61f402eef293'.|}</ol><ol start="24" style="list-style-type: ~~lower-alpha~~decimal;"><li>'''root@orangepi:~$''' The prompt indicates that this command is entered in '''the Linux system of the development board'''. The $ at the end of the prompt indicates that the current user of the system is a normal user. When executing a privileged command, you need to add '''sudo'''</li><li>'''root@orangepi:~#''' The prompt indicates that this command is entered in the Linux system of the development board, and the # at the end of the prompt indicates that the current user of the system is the root user, who You 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~~ view the ~~end~~ IP address of wifi through the ~~prompt indicates that the current user of the system is an ordinary user. When executing privileged commands, sudo needs to be added~~ '''~~sudo~~ip addr show wlan0'''~~</li><li>'''root@test:~#''' The prompt indicates that this~~ command is entered in the Ubuntu PC or Ubuntu virtual machine, not in the Linux system of the development board. The # at the end of the prompt indicates that the current user of the system is the root user and can execute any command you want</li></ol>

~~<ol start~~{| class="3wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>What are the commands that need to be entered?~~|-~~<ol style="list-style-type~~| orangepi@orangepi: ~~lower-alpha;"><li>As shown below,~~ ~$ '''~~the black bold part~~ip addr show wlan0''' is the command that needs to be input, and the content below the command is the output content (some commands have output, some may not), and this part of the content does not need to be input</li></ol>~~</li></ol>~~

~~root@orangepi~~11:~~~# '''cat /boot/orangepiEnv.txt'''~~wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~'''verbosity=7'''~~:link/ether 23:8c:d6:ae:76:bb brd ff:ff:ff:ff:ff:ff

~~bootlogo~~:inet '''192.168.1.11'''/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0

~~'''console=serial'''~~::valid_lft 259192sec preferred_lft 259192sec

~~<ol start="2" style="list-style-type~~: ~~lower-alpha;">~~<li>As shown below, some commands cannot be written in one line and will be placed on the next line. As long as the black and bold parts are all commands that need to be input. When these commands are entered into one line, the last "\" of each line needs to be removed, this is not part of the command. In addition, there are spaces in different parts of the command, please don’t miss it</li><inet6 240e:3b7:3240:c3a0:c401:a445:5002:ccdd/~~ol>~~64 scope global dynamic noprefixroute

~~orangepi@orangepi~~:~~~$ '''echo \'''~~:valid_lft 259192sec preferred_lft 172792sec

~~'''"deb [arch=$(dpkg --print-architecture) \'''~~:inet6 fe80::42f1:6019:a80e:4c31/64 scope link noprefixroute

::valid_lft forever preferred_lft forever|}</ol><ol start="5" style="list-style-type: decimal;"><li>Use the '''ping''' command to test the connectivity of the wifi network, and the '''ping'''command can be interrupted through the shortcut key ''~~signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] \~~'Ctrl+C'''</li>

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

~~'''$~~PING www.orangepi.org (~~lsb_release -cs~~182.92.236.130) ~~stable" | sudo tee /etc/apt/sources~~from 192.168.~~list~~1.~~d/docker~~49 wlan0: 56(84) bytes of data.~~list > /dev/null'''~~

~~== Linux system login instructions~~ 1 ttl=52 time=43.5 ms

~~=== Linux system default login account and password~~ 64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=2 ttl=52 time=41.3 ms

~~{| class="wikitable"~~|-~~| style="text-align~~64 bytes from 182.92.236.130 (182.92.236.130): ~~left;"| '''Account'''| style~~icmp_seq=~~"text-align: left;"| '''Passport'''~~|-~~| style~~3 ttl=~~"text-align: left;"| '''root'''| style~~52 time=~~"text-align: left;"| '''orangepi'''~~|-~~| style="text-align: left;"| '''orangepi'''| style="text-align: left;"| '''orangepi'''~~|}44.9 ms

~~'''Note that when entering the password, the specific content of the entered password will not be displayed on the screen, please do not think that there is any fault, just press Enter after inputting~~64 bytes from 182.~~'''~~92.236.130 (182.92.236.130): icmp_seq=4 ttl=52 time=45.6 ms

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

~~=== How to set automatic terminal login in Linux system ===~~^C

~~# The Linux system automatically logs in to the terminal by default, and the default login user name is~~ --- www.orangepi ~~'''orangepi'''~~.org ping statistics ---

~~[[File:pi3b-img171.png|351x198px]]~~5 packets transmitted, 5 received, 0% packet loss, time 4006ms

rtt min/avg/max/mdev = 41.321/44.864/48.834/2.484 ms|}</ol ~~start~~><li>Use the following command~~ to ~~set the root user to automatically log~~ -wifi-in ~~to the terminal</li-a-graphical-way"></olspan>

~~orangepi@orangepi~~==== The server image connects to WIFI in a graphical way ==== <ol style="list-style-type:~$ decimal;"><li>First log in to the Linux system, there are the following three ways</li><ol style="list-style-type: lower-alpha;"><li>If the development board is connected with a network cable, you can remotely log in to [[Orange Pi 3B#SSH remote login development board|'''~~sudo auto_login_cli.sh root~~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>~~Use~~ Enter the ~~following~~ nmtui command to ~~disable automatic login terminal~~open the interface as shown below</li~~></ol~~>

~~orangepi@orangepi~~[[File:~$ pi3b-img177.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Select '''~~sudo auto_login_cli.sh -d~~Activate a connect'''and press Enter</li>

[[File:pi3b-img178.png]]</ol><ol start="45" style="list-style-type: decimal;"><li>~~Use the following command to set the orangepi user to automatically log in to~~ Then you can see all the ~~terminal again~~searched WIFI hotspots</li~~></ol~~>

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

~~=== Instructions for automatic login of Linux desktop version system ===~~img179.png]]

~~# After~~ </div></ol><ol start="6" style="list-style-type: decimal;"><li>Select the ~~desktop system starts~~WIFI hotspot you want to connect to, ~~it will automatically log in~~ then use the Tab key to position the ~~desktop without entering a password~~cursor on '''Activate''' and press Enter</li>

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

</div></ol><ol start="27" style="list-style-type: decimal;"><li>~~Run~~ Then a dialog box for entering a password will pop up, enter the ~~following command to prohibit the desktop system from automatically logging into the desktop</li></ol>~~ ~~orangepi@orangepi:~$~~ corresponding password in '''~~sudo disable_desktop_autologin.sh~~Password'''and press Enter to start connecting to WIFI</li>

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

[[File:pi3b-~~img173~~img181.png~~|569x320px|IMG_256~~]]

</div></ol><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</olli>

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

~~# Execute the following command to set the desktop system to automatically log in as the root user~~[[File:pi3b-img182.png]]

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

~~<ol start="2" style="list-style-type~~11: ~~decimal~~wlan0: <">~~<li>Then restart the system~~BROADCAST,MULTICAST,UP, ~~and the root user will automatically log in to the desktop</li></ol>~~LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~[[File~~:~~pi3b-img174.png|448x187px]]~~link/ether 24:8c:d3:aa:76:bb brd ff:ff:ff:ff:ff:ff

:inet '''~~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~~192.168.1.11'''/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0

~~'''Also note that this is not a bug, since pulseaudio is not allowed to run as root.'''~~::valid_lft 259069sec preferred_lft 259069sec

~~<ol start="3" style="list-style-type~~: ~~decimal;"><li>Execute the following command to set the desktop system to log in automatically with the orangepi user again</li><~~inet6 240e:3b7:3240:c4a0:c401:a445:5002:ccdd/~~ol>~~64 scope global dynamic noprefixroute

~~orangepi@orangepi~~:~~~$ '''sudo desktop_login.sh orangepi'''~~:valid_lft 259071sec preferred_lft 172671sec

~~<~~:inet6 fe80::42f1:6019:a80e:4c31/~~span>=== The method of disabling the desktop in the Linux desktop version system ===~~64 scope link noprefixroute

~~# First enter~~ ::valid_lft forever preferred_lft forever|}</ol><ol start="10" style="list-style-type: decimal;"><li>Use the ~~following~~ '''ping''' command on to test the connectivity of the wifi network, and the '''ping''' command ~~line，~~can be interrupted through the shortcut key '''~~Please remember to add sudo permission~~Ctrl+C'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ping www.orangepi.org -I wlan0'''

PING www.orangepi~~@orangepi~~.org (182.92.236.130) from 192.168.1.49 wlan0:~~~$ '''sudo systemctl disable lightdm~~56(84) bytes of data.~~service'''~~

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

~~orangepi@orangepi~~64 bytes from 182.92.236.130 (182.92.236.130):~~~$ '''sudo reboot'''~~icmp_seq=2 ttl=52 time=41.3 ms

~~<ol start~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq="3~~" style~~ttl=~~"list-style-type: decimal;"><li>The steps to reopen the desktop are as follows:<ol style~~52 time=~~"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>~~44.9 ms

~~orangepi@orangepi~~64 bytes from 182.92.236.130 (182.92.236.130):~~~$ '''sudo systemctl start lightdm~~icmp_seq=4 ttl=52 time=45.~~service'''~~6 ms

~~<ol start~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=~~"2" style~~5 ttl=~~"list-style-type: lower-alpha;"><li>After the command is executed, the desktop will be displayed</li></ol>~~52 time=48.8 ms

~~== Onboard LED Light Test Instructions ==~~^C

~~# There are three LED lights on the development board, one green light, one red light, and one PCIe light~~--- www. ~~The location is shown in the figure below:~~orangepi.org ping statistics ---

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

~~[[File:pi3b-img175.png|425x115px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\3.5~~rtt min/avg/max/mdev = 41.~~Onboard-LED-Light-Test-Instructions(1)~~321/44.~~jpg3~~864/48.5834/2.~~Onboard~~484 ms|}</ol>

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

~~'''Note that~~ # Click the ~~following operations should be performed under~~ network configuration icon in the ~~root user.'''~~upper right corner of the desktop (please do not connect the network cable when testing WIFI)

~~<ol style="list-style-type~~: ~~lower~~:[[File:pi3b-~~alpha;"><li>First enter the setting directory of the green light</li></ol>~~img183.png]]

~~root@orangepi~~<ol start="2" style="list-style-type:~# decimal;"><li>Click '''~~cd /sys/class/leds/status~~More networks'''in the pop-up drop-down box to see all scanned WIFI hotspots, and then select the WIFI hotspot you want to connect to.</li>

[[File:pi3b-img184.png]]</ol><ol start="23" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The command~~ Then enter the password of the WIFI hotspot, and then click '''Connect''' to ~~set the green light~~ start connecting to ~~stop flashing is as follows~~WIFI</li~~></ol~~>

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

[[File:pi3b-img186.png]]</ol><ol start="35" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The command to set~~ If you can open other web pages after opening the browser, it means that the ~~green light to be on~~ WIFI connection is ~~as follows~~normal</li~~></ol~~>

~~root@orangepi~~[[File:pi3b-img187-1.png]]</~~sys~~ol></~~class/leds/work# '''echo default-on > trigger'''~~span>

~~<ol start~~=~~"4" style~~=~~"list-style-type: lower-alpha;"><li>The command~~ = How to set ~~the green light to flash is as follows</li></ol>~~a static IP address ===

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

== ~~Network connection test~~ == Use the nmtui command to set a static IP address ====

~~=== Ethernet port test ===~~# First run the '''nmtui''' command

# 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::{| class="wikitable" style="width:800px;" ~~# After the system starts, it will automatically assign an IP address to the Ethernet card through DHCP,~~ |-| orangepi@orangepi:~$ '''~~No other configuration is required~~nmtui'''~~# The command to view the IP address in the Linux system of the development board is as follows~~|}

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

2[[File: ~~eth0~~pi3b-img188.png]]</ol><ol start="3" style="list-style-type: ~~&lt~~decimal;~~BROADCAST~~"><li>Then select the network interface that needs to set a static IP address,~~MULTICAST~~for example,UPto set the static IP address of the '''Ethernet''' interface,~~LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000~~select '''Wired connection 1'''.</li>

~~link~~[[File:pi3b-img189.png]]</~~ether 4a~~ol><ol start="4" style="list-style-type:~~fe:2b:3d:17:1c brd ff:ff:ff:ff:ff:ff~~decimal;"><li>Then select '''Edit''' with the '''Tab''' key and press the Enter key</li>

~~inet~~ [[File:pi3b-img190.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then use the Tab key to move the cursor to the '''~~192.168.1.150~~<Automatic>'''position shown in the figure below to configure IPv4</~~24 brd 192.168.1.255 scope global dynamic noprefixroute eth0~~li>

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

~~inet6 fe80~~[[File:pi3b-img192.png]]</ol><ol start="7" style="list-style-type:~~9a04:3703:faed:23be~~decimal;"><li>The display after selection is shown in the figure below</~~64 scope link noprefixroute~~li>

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

~~'''When using ifconfig to view the IP address~~[[File:pi3b-img194.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then press Enter, if the following ~~information is displayed, it is because sudo is not added. The correct command is: sudo ifconfig'''~~setting interface will pop up after entering</li>

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

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

* [[File:pi3b-img197.png]]</~~sbin~~ol><ol start="12" style="list-style-type: decimal;"><li>Then click'''<Back>''' to return to the previous selection interface</~~ifconfig~~li>

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

~~The command could not~~ [[File:pi3b-img199.png]]</ol><ol start="14" style="list-style-type: decimal;"><li>Then select the network interface that needs to be ~~located because~~ set, such as '''Wired connection 1''~~/sbin:/usr/sbin~~' ~~is not included in~~ , then move the ~~PATH environment variable.~~cursor to'''<Deactivate>''', and press Enter to disable '''Wired connection 1'''</li>

~~This is most likely caused by~~ [[File:pi3b-img200.png]]</ol><ol start="15" style="list-style-type: decimal;"><li>Then please do not move the cursor, and then press the Enter key to re-enable '''Wired connection 1''', so that the ~~lack of administrative privileges associated with your user account.~~static IP address set earlier will take effect</li>

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

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

~~# '''Connect the HDMI display, then log in to the system and use the ip addr show eth0 command to view the IP address'''~~{| class="wikitable" style="width:800px;" |-| # orangepi@orangepi:~$ '''~~Enter the~~ ip addr show eth0 ~~command in the debugging serial terminal to view the IP address'''~~# '''If there is no debugging serial port and no HDMI display, you can also check the IP address of the development board’s network port through the router’s management interface. However, in this method, some people often cannot see the IP address of the development board normally. If you can't see it, the debug method looks like this:'''

~~<ol style="list-style-type~~3: ~~upper-alpha;">~~<li>'''First check whether the Linux system has started normally. If the green light of the development board is blinking, it is generally started normally. If only the red light is on, it means that the system has not started normallyeth0: <~~'''</li><li>'''Check whether the network cable is plugged in tightly~~BROADCAST, ~~or try another network cable;'''</li><li>'''Try another router (I have encountered many problems with the router~~MULTICAST, ~~such as the router cannot assign the IP address normally~~UP, ~~or the IP address has been assigned normally but cannot be seen in the router)~~LOWER_UP>~~'''</li><li>'''If there is no router to replace, you can only connect to an HDMI display or use the debugging serial port to view the IP address'''</li></ol>~~mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

~~'''In addition, it should be noted that the development board DHCP automatically assigns an IP address without any settings.'''~~:link/ether 5e:ac:14:a5:92:b3 brd ff:ff:ff:ff:ff:ff

:inet '''<~~ol start="4"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">192.168.1.177<li/span>~~The command to test the network connectivity is as follows, the '~~''~~ping~~'~~'' command can be interrupted through the shortcut key of '''Ctrl+C'''<~~/~~li></ol>~~24 brd 192.168.1.255 scope global noprefixroute eth0

~~orangepi@orangepi~~:~~~$ '''ping www.baidu.com -I eth0'''~~:valid_lft forever preferred_lft forever

~~PING www.a.shifen.com (14.215.177.38) from 192.168.1.12 eth0~~: ~~56(84) bytes of data.~~inet6 241e:3b8:3240:c3a0:e269:8305:dc08:135e/64 scope global dynamic noprefixroute

~~64 bytes from 14.215.177.38 (14.215.177.38)~~: ~~icmp_seq=1 ttl=56 time=6.74 ms~~:valid_lft 259149sec preferred_lft 172749sec

:inet6 fe80::957d:bbbe:4928:3604/64 ~~bytes from 14.215.177.38 (14.215.177.38): icmp_seq=2 ttl=56 time=6.80 ms~~scope link noprefixroute

~~64 bytes from 14.215.177.38 (14.215.177.38)~~: ~~icmp_seq~~:valid_lft forever preferred_lft forever|}</ol><ol start=~~3 ttl~~"18" style=~~56 time=6.26 ms~~"list-style-type: decimal;"><li>Then you can test the connectivity of the network to check whether the IP address is configured OK, and the '''ping''' command can be interrupted through the shortcut key '''Ctrl+C'''</li>

~~64 bytes from 14.215.177.38 (14~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ping 192.~~215~~168.~~177.38): icmp_seq=4 ttl=56 time=7~~1.~~27 ms~~47 -I eth0'''

^CPING 192.168.1.47 (192.168.1.47) from 192.168.1.188 eth0: 56(84) bytes of data.

~~--- www~~64 bytes from 192.a168.~~shifen~~1.~~com ping statistics ---~~47: icmp_seq=1 ttl=64 time=0.233 ms

~~4 packets transmitted, 4 received,~~ 64 bytes from 192.168.1.47: icmp_seq=2 ttl=64 time=0~~% packet loss, time 3002ms~~.263 ms

~~rtt min/avg/max/mdev = 6~~64 bytes from 192.~~260/6~~168.~~770/7~~1.~~275/~~47: icmp_seq=3 ttl=64 time=0.~~373~~ 273 ms

~~=== WIFI connection test~~ 64 bytes from 192.168.1.47: icmp_seq=4 ttl=64 time=0.269 ms

~~'''Please do not connect to WIFI by modifying the /etc/network/interfaces configuration file~~64 bytes from 192. ~~There will be problems connecting to the WIFI network in this way~~168.~~'''~~1.47: icmp_seq=5 ttl=64 time=0.275 ms

~~==== WIFI The server image connects to WIFI through commands ====~~^C

'''When the development board is not connected to Ethernet, not connected to HDMI display, but only connected to the serial port, it is recommended to use the commands demonstrated in this section to connect to the WIFI network--- 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 ping statistics ---

~~<ol style="list-style-type: decimal;"><li>First log in to the Linux system~~5 packets transmitted, ~~there are the following three ways<ol style="list-style-type: lower-alpha;"><li>If the development board is connected with a network cable~~5 received, ~~you can remotely log in to the Linux system through ssh</li><li>If the development board is connected to the debugging serial port~~0% packet loss, ~~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>~~time 4042ms

~~orangepi@orangepi:~$ '''~~rtt min/avg/max/mdev = 0.233/0.262/0.275/0.015 ms|}</ol>

~~<div class~~=~~"figure">~~=== Use the nmcli command to set a static IP address ====

~~[[File~~<ol style="list-style-type: decimal;"><li>If you want to set the static IP address of the network port, please insert the network cable into the development board first. '''If you need to set the static IP address of WIFI, please connect the WIFI first, and then start to set the static IP address'''</li><li>Then use the '''nmcli con show''' command to view the name of the network device, as shown below<ol style="list-style-type:~~pi3b~~lower-~~img176.png~~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;"|-|~~575x250px~~orangepi@orangepi:~$ '''nmcli con show''' NAMEUUID TYPE DEVICE '''orangepi'''cfc4f922-ae48-46f1-84e1-2f19e9ec5e2awifi wlan0 '''Wired connection 1'''9db058b7-7701-37b8-9411-efc2ae8bfa30ethernet eth0 |~~选区_011]]~~}</ol></li></ol>

~~</div>~~

<li>Then ~~use~~ enter the ~~nmcli~~ following command ~~to connect to the scanned WIFI hotspot~~, where:</li~~></ol~~>

:a. '''~~wifi_name~~"Wired connection 1"''' ~~needs~~ means to ~~be replaced with~~ set the static IP address of the Ethernet port. If you need to set the static IP address of the WIFI, please change it to the corresponding name of the WIFI ~~hotspot~~ network interface (you ~~want to connect to~~can get it through the '''nmcli con show''' command)

:b. After '''~~wifi_passwd~~ipv4.addresse''' ~~needs~~ is the static IP address to be ~~replaced with~~ set, which can be modified to the ~~password of the WIFI hotspot~~ value you want to ~~connect to~~set

~~orangepi@orangepi~~:~$ c. '''~~nmcli dev wifi connect wifi_name password wifi_passwd~~ipv4.gateway'''indicates the address of the gateway

~~Device~~ ::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~wlan0~~nmcli con mod "Wired connection 1" \' ~~successfully activated with~~ '~~cf937f88-ca1e-4411-bb50-61f402eef293~~'.

~~<ol start="4" style="list-style-type: decimal;"><li>You can view the IP address of wifi through the~~ '''~~ip addr show wlan0~~ipv4.addresses "192.168.1.110" \''' ~~command</li></ol>~~

~~orangepi@orangepi:~$~~ '''~~ip addr show wlan0~~ipv4.gateway "192.168.1.1" \'''

~~11: wlan0:~~ '''ipv4.dns &ltquot;~~BROADCAST,MULTICAST,UP,LOWER_UP~~8.8.8.8&gtquot; ~~mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~\'''

~~link~~'''ipv4.method "manual"'''|}</~~ether 23~~ol><ol start="4" style="list-style-type:8cdecimal;"><li>Then restart the Linux system</li>{| class="wikitable" style="width:d6800px;" |-| orangepi@orangepi:ae~$ '''sudo reboot'''|}</ol><ol start="5" style="list-style-type:76decimal;"><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:~~bb brd ff:ff:ff:ff:ff:ff~~800px;" |-| ~~inet~~ orangepi@orangepi:~$ '''~~192.168.1.11~~ip addr show eth0'''~~/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0~~

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

~~inet6 240e~~:~~3b7~~link/ether 5e:ae:14:a5:~~3240~~91:~~c3a0~~b3 brd ff:~~c401~~ff:~~a445~~ff:~~5002~~ff:~~ccdd/64 scope global dynamic noprefixroute~~ff:ff

~~valid_lft 259192sec preferred_lft 172792sec~~:inet '''192.168.1.110'''/32 brd 192.168.1.110 scope global noprefixroute eth0

~~inet6 fe80~~::~~42f1:6019:a80e:4c31/64 scope link noprefixroute~~valid_lft forever preferred_lft forever

~~valid_lft forever preferred_lft forever~~:inet6 240e:3b7:3240:c3a0:97de:1d01:b290:fe3a/64 scope global dynamic noprefixroute

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

~~orangepi@orangepi~~:~~~$ '''ping www.orangepi.org -I wlan0'''~~inet6 fe80::3312:861a:a589:d3c/64 scope link noprefixroute

~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0~~: ~~56(84) bytes of data.~~:valid_lft forever preferred_lft forever|}</ol>

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

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~{| class=~~2 ttl~~"wikitable" style=~~52 time=41~~"background-color:#ffffdc;width:800px;" |-| <big>'''Linux systems enable ssh remote login by default and allow the root user to log in to the system. Before logging in with ssh, you first need to ensure that the Ethernet or wifi network is connected, and then use the ip addr command or check the router to obtain the IP address of the development board.~~3 ms~~'''</big>|}

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~=== SSH remote login development board under Ubuntu =~~3 ttl~~=~~52 time~~=~~44.9 ms~~

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq=4 ttl=52 time=45.6 ms~~# Obtain the IP address of the development board# Then you can remotely log in to the Linux system through the ssh command

~~64 bytes from 182~~::{| class="wikitable" style="width:800px;" |-| test@test:~$ '''ssh [mailto:root@192.92168.~~236~~1.~~130 (182~~36 root@192.92168.~~236~~1.~~130~~]xxx'''        (Need to be replaced with the IP address of the development board)~~: icmp_seq=5 ttl=52 time=48.8 ms~~

^Croot@192.168.1.xx's password:        (Enter the password here, the default password is orangepi)|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that when entering the password, the specific content of the entered password will not be displayed on the screen, please do not think that there is any fault, just press Enter after inputting.'''</big>|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If you are prompted to refuse the connection, as long as you are using the image provided by Orange Pi, please do not suspect that the password orangepi is wrong, but look for other reasons.'''</big>|}

<ol start="3" style="list-style-~~- www.orangepi.org ping statistics ---~~type: decimal;"><li>After successfully logging in to the system, the display is as shown in the figure below</li>

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

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

<~~span id~~/div>{| class="~~the~~wikitable" style="background-~~server~~color:#ffffdc;width:800px;" |-~~image-connects-to-wifi-in-a-graphical-way">~~| <~~/span~~big>~~==== The server image connects~~ '''If ssh cannot log in to ~~WIFI~~ 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 ~~a graphical way ====~~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:'''

~~1) First log in to the Linux system, there are the following three ways~~

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

~~~~

#

~~# Then enter the nmtui command in the command line to open the wifi connection interface~~

~~orangepi@orangepi:~$~~ '''~~nmtui~~If it still doesn't work, try to reset the system.'''</big>|}</ol>

~~<ol start~~=~~"3" style~~=~~"list-style-type: decimal;"><li>Enter the nmtui command to open the interface as shown below</li></ol>~~= SSH remote login development board under Windows ===

~~[[File:pi3b-img177.png|345x215px]]~~# First obtain the IP address of the development board# Under Windows, you can use MobaXterm to remotely log in to the development board, first create a new ssh session

~~<ol start="4" style="list-style-type~~: ~~decimal;"><li>Select~~ :a. Open '''~~Activate a connect~~Session''' ~~and press Enter</li></ol>~~

~~[[File~~:~~pi3b-img178~~:b.~~png|349x216px]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>~~Then ~~you can see all the searched WIFI hotspots</li></ol>~~select '''SSH''' in '''Session Setting'''

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

~~[[File~~:~~pi3b-img179~~:d.~~png|426x270px|16]]~~Then enter the user name '''root''' or '''orangepi''' of the Linux system in '''Specify username'''

~~</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~~ :e. Finally click '''~~Activate~~OK''' ~~and press Enter</li></ol>~~

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

</div>

<ol start="73" style="list-style-type: decimal;"><li>Then you will be prompted to enter a ~~dialog box~~ 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 a the password ~~will pop up~~, ~~enter~~ the specific content of the ~~corresponding~~ entered password ~~in '''Password~~will not be displayed on the screen, please do not think that there is any fault, just press Enter after inputting.''' ~~and press Enter to start connecting to WIFI</li>~~</olbig>|}

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

</div></ol><ol start="84" style="list-style-type: decimal;"><li>After successfully logging in to the system, the ~~WIFI connection~~ display is ~~successful, a "*" will be displayed~~ as shown in ~~front of~~ the ~~connected WIFI name~~figure below</li~~></ol~~>

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

~~[[File:pi3b-img182.png|443x283px|C:\Users\orangepi\Desktop\用户手册插图\Zero3\未标题-9.jpg未标题-9]]~~== The method of uploading files to the Linux system of the development board ==

<~~/div><ol start~~span id="~~9" style="list~~how-to-upload-files-to-the-development-board-linux-system-in-~~style~~ubuntu-~~type: decimal;~~pc"><li/span>~~You can view~~ === How to upload files to the ~~IP address of wifi through the '''ip addr show wlan0''' command</li></ol>~~development board Linux system in Ubuntu PC ===

~~orangepi@orangepi:~$ '''ip addr show wlan0'''~~==== How to upload files using the scp command ====

~~11: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~# 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

~~link/ether 24~~:8c:d3a. '''file_path''':~~aa:76:bb brd ff:ff:ff:ff:ff:ff~~need to be replaced with the path of the file to be uploaded

~~inet~~ ::b. '''~~192.168.1.11~~orangepi'''~~/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0~~: It is the user name of the Linux system of the development board, and it can also be replaced with other ones, such as root

~~valid_lft 259069sec preferred_lft 259069sec~~::c. '''192.168.xx.xx''': It is the IP address of the development board, please modify it according to the actual situation

~~inet6 240e~~:~~3b7~~:~~3240:c4a0~~d. '''/home/orangepi''':~~c401:a445:5002:ccdd/64 scope global dynamic noprefixroute~~The path in the Linux system of the development board, which can also be modified to other paths

~~valid_lft 259071sec preferred_lft 172671sec~~::{| class="wikitable" style="width:800px;" |-| test@test:~$ '''scp file_path orangepi@192.168.xx.xx:/home/orangepi/'''|}

~~inet6 fe80~~<ol start="2" style="list-style-type:~~:42f1:6019:a80e:4c31~~decimal;"><li>If you want to upload a folder, you need to add the -r parameter</~~64 scope link noprefixroute~~li>

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

~~<ol start~~=~~"10" style~~=~~"list-style-type: decimal;"><li>Use the '''ping''' command~~ == How to ~~test the connectivity of the wifi network, and the '''ping''' command can be interrupted through the shortcut key '''Ctrl+C'''</li></ol>~~upload files using filezilla ====

~~orangepi@orangepi:~$ '''ping www.orangepi.org -I wlan0'''~~# First install filezilla in Ubuntu PC

~~PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0~~: ~~56(84) bytes of data.~~:{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt install -y filezilla'''|}

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~<ol start=~~1 ttl~~"2" style=~~52 time=43.5 ms~~"list-style-type: decimal;"><li>Then use the following command to open filezilla</li>

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~{| class=~~2 ttl~~"wikitable" style=~~52 time~~"width:800px;" |-| test@test:~$ '''filezilla'''|}</ol><ol start=~~41.~~"3 ms" style="list-style-type: decimal;"><li>The interface after filezilla is opened is as follows, and the display under the remote site on the right is empty</li>

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

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

~~64 bytes from 182.92.236.130 (182.92.236.130): icmp_seq~~</div></ol><ol start=~~5 ttl~~"4" style=~~52 time=48.8 ms~~"list-style-type: decimal;"><li>The method of connecting the development board is shown in the figure below</li>

^C<div class="figure">

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

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

~~rtt min~~[[File:pi3b-img210.png]]</~~avg/max/mdev~~ ol><ol start="6" style= ~~41.321/44.864~~"list-style-type: decimal;"><li>Then choose to always '''trust this host''', and then click '''OK'''</~~48.834/2.484 ms~~li>

<~~span id~~div class="~~test-method-of-desktop-image~~figure">~~==== Test method of desktop image ====~~

~~# Click the network configuration icon in the upper right corner of the desktop (please do not connect the network cable when testing WIFI)~~[[File:pi3b-img211.png]]

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

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

</div></ol><ol start="38" style="list-style-type: decimal;"><li>Then ~~enter~~ 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 ~~password~~ left side of the ~~WIFI hotspot~~filezilla software, then click the right mouse button, and then click ~~'''Connect'''~~ the upload option to start ~~connecting~~ uploading the file to ~~WIFI~~the development board.</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~~img213. ~~The entrance of the browser is shown in the figure below</li></ol>~~png]]

~~[[File~~</div></ol><ol start="9" style="list-style-type:~~pi3b-img186.png|576x308px]]~~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>

~~<ol start="5" style="list-style-type: decimal;">~~<li>~~If you can open other web pages after opening~~ The method of uploading a folder is the ~~browser~~same as that of uploading a file, ~~it means that the WIFI connection is normal~~so I won't go into details here</li></ol>

~~[[File:pi3b-img187.png|576x222px]]~~=== The method of uploading files from Windows PC to the Linux system of the development board ===

==== How to ~~set a static IP address~~ upload files using filezilla ====

~~'''Please do not set a static IP address by modifying~~ # First download the ~~/etc/network/interfaces configuration~~ installation file~~.'''~~of the Windows version of the filezilla software, the download link is as follows

~~<~~project.org/~~span>~~download.php?type=client'''~~==== Use the nmtui command to set a static IP address ====~~|}

~~# First run the '''nmtui''' command~~<div class="figure"> ::[[File:pi3b-img214.png]] </div><div class="figure">

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

</div>

<li>~~Then~~ The downloaded installation package is as follows, and then double-click to install directly</li> {| class="wikitable" style="width:800px;" |-| '''FileZilla_Server_1.5.1_win64-setup.exe'''|} During the installation process, please select '''~~Edit a connection~~Decline''' on the following installation interface, and ~~press Enter~~then select '''Next>''' <~~/li></ol~~div class="figure">

[[File:pi3b-~~img188~~img216.png~~|227x247px~~]]

</div></ol>

<li>~~Then select the network~~ The interface ~~that needs to set a static IP address~~after filezilla is opened is as follows, ~~for example, to set~~ and the display under the ~~static IP address of~~ remote site on the ~~'''Ethernet''' interface, select '''Wired connection 1'''.~~right is empty</li~~></ol~~>

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

[[File:pi3b-img217.png]]

</div></ol>

<li>~~Then select '''Edit''' with~~ The method of connecting the ~~'''Tab''' key and press~~ development board is shown in the ~~Enter key~~figure below:</li~~></ol~~>

~~[[File:pi3b-img190.png|316x144px]]~~<div class="figure">

[[File:pi3b-img209.png]]

</div></ol>

<li>Then ~~use the Tab key to move the cursor~~ choose to '''save the password''', and then click '''~~<Automatic>~~OK''' ~~position shown in the figure below to configure IPv4~~</li~~></ol~~>

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

[[File:pi3b-img218.png]]

</div></ol>

<li>Then ~~press Enter, select~~ choose to always '''~~Manual~~trust this host''' ~~with the up and down arrow keys~~, and ~~press Enter to confirm~~then click '''OK'''</li> <~~/ol~~div class="figure">

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

</div></ol>

<li>~~The display after selection~~ After the connection is ~~shown in~~ successful, you can see the directory structure of the development board Linux file system on the right side of the ~~figure below~~filezilla software</li~~></ol~~>

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

[[File:pi3b-img220.png]]

</div></ol>

<li>Then ~~move~~ select the ~~cursor~~ path to be uploaded to the development board on the right side of the filezilla software, and then select the file to be uploaded on the Ubuntu PC on the left side of the filezilla software, then click the right mouse button, and then click the upload option to start uploading the file to the ~~'''<Show>'''~~development board.</li~~></ol~~>

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

</div></ol>

<li>~~Then press Enter~~After the upload is complete, you can go to the corresponding path in the Linux system of the development board to view the uploaded file</li><li>The method of uploading a folder is the ~~following setting interface will pop up after entering~~same as that of uploading a file</li></ol>

~~[[File:pi3b~~

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

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

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

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

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

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

'''When you want to connect the HDMI of the development board to the HDMI port of the laptop, please make sure that your laptop supports the HDMI in function.'''<~~ol start~~/big>|}{| class="13wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Then select~~ '''~~Activate a~~ When the HDMI is not displayed, please check whether the HDMI cable is plugged in tightly. After confirming that there is no problem with the connection~~'''~~, ~~then move the cursor~~ you can change a different screen and try tosee if it is displayed.'''~~<OK>''', and finally click Enter~~</libig>|}</ol>

~~[[File:pi3b~~

~~<ol start~~=~~"14" style~~=~~"list-style-type: decimal;"><li>Then select the network interface that needs~~ = HDMI to ~~be set, such as '''Wired connection 1''', then move the cursor to'''<Deactivate>''', and press Enter to disable '''Wired connection 1'''</li></ol>~~VGA display test ===

~~[[File:pi3b-img200.png|576x224px]]~~ <ol ~~start="15"~~ style="list-style-type: decimal;"><li>~~Then please do not move the cursor~~First, ~~and then press the Enter key~~ you need to ~~re-enable '''Wired connection 1''', so that~~ prepare the ~~static IP address set earlier will take effect~~following accessories<ol style="list-style-type: lower-alpha;"><li>HDMI to VGA converter</olli>

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

[[File:pi3b-img223.png]]</ol><ol start="163" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then you can exit nmtui through the'''<Back>''' and '''Quit''' buttons~~A monitor or TV that supports VGA interface</li></ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>HDMI to VGA display test as shown below</li>

[[File:pi3b-~~img202~~img224.png~~|300x253px]] [[File:pi3b-img203.png|227x252px~~]]

~~<ol start~~{| class="17wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Then through '''ip addr show eth0~~'''When using HDMI to VGA display, ~~you can see that~~ the ~~IP address~~ development board and the Linux system of the ~~network port has changed~~ development board do not need to make any settings, only the HDMI interface of the development board can display normally. So if there is a problem with the test, please check whether there is a problem with the ~~static IP address set earlier~~HDMI to VGA converter, VGA cable and monitor.'''</libig>|}</ol>

~~orangepi@orangepi:~$ '''ip addr show eth0'''~~=== HDMI resolution setting method ===

~~3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000~~# First open '''Display''' in '''Settings'''

~~link/ether 5e~~:ac:14[[File:~~a5:92:b3 brd ff:ff:ff:ff:ff:ff~~pi3b-img225.png]]

~~inet '''192.168.1.177'''~~<ol start="2" style="list-style-type: decimal;"><li>Then you can see the current resolution of the system</~~24 brd 192.168.1.255 scope global noprefixroute eth0~~li>

~~valid_lft forever preferred_lft forever~~[[File:pi3b-img226.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Click the drop-down box of Resolution to see all resolutions currently supported by the monitor</li>

~~inet6 241e~~[[File:~~3b8:3240:c3a0:e269:8305:dc08~~pi3b-img227.png]]</ol><ol start="4" style="list-style-type:~~135e~~decimal;"><li>Then select the resolution you want to set, and click Apply</~~64 scope global dynamic noprefixroute~~li>

~~valid_lft 259149sec preferred_lft 172749sec~~[[File:pi3b-img228.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>After the new resolution is set, select '''Keep the configuration'''</li>

~~inet6 fe80~~[[File:~~:957d:bbbe:4928:3604~~pi3b-img229.png]]</ol></~~64 scope link noprefixroute~~span>

~~valid_lft forever preferred_lft forever~~== How to use Bluetooth ==

<~~ol start~~span id="~~18" style="list~~test-method-of-desktop-~~style~~image-~~type: decimal;~~1"><li/span>~~Then you can test the connectivity~~ === Test method of ~~the network to check whether the IP address is configured OK, and the '''ping''' command can be interrupted through the shortcut key '''Ctrl+C'''</li></ol>~~desktop image ===

~~orangepi@orangepi:~$ '''ping 192~~# Click the Bluetooth icon in the upper right corner of the desktop.~~168.1.47 -I eth0'''~~

~~PING 192.168.1.47 (192.168.1.47) from 192.168.1.188 eth0~~: ~~56(84) bytes of data~~:[[File:pi3b-img230.png]]

~~64 bytes from 192.168.1.47: icmp_seq~~<ol start=~~1 ttl~~"2" style=~~64 time=0.233 ms~~"list-style-type: decimal;"><li>Then select the adapter</li>

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

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

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

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

^C[[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 '''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- ~~192~~type: decimal;"><li>When pairing, the pairing confirmation box will pop up in the upper right corner of the desktop.~~168~~Select '''Confirm''' to confirm.~~1.47 ping statistics ---~~At this time, the mobile phone also needs to be confirmed</li>

~~5 packets transmitted~~[[File:pi3b-img237.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>After pairing with the mobile phone, ~~5 received~~you can choose the paired Bluetooth device, ~~0% packet loss, time 4042ms~~then right-click and select '''Send a File''' to start sending a picture to the phone</li>

~~rtt min~~[[File:pi3b-img238.png]]</~~avg/max/mdev~~ ol><ol start="10" style= ~~0.233/0.262~~"list-style-type: decimal;"><li>The interface of the sending picture is shown below</~~0.275/0.015 ms~~li>

[[File:pi3b-img239.png]]</ol>~~==== Use the nmcli command to set a static IP address ====~~

~~<ol style~~=~~"list-style-type: decimal;">~~<li>If you want to set the static IP address of the network port, please insert the network cable into the development board first. '''If you need to set the static IP address of WIFI, please connect the WIFI first, and then start to set the static IP address'''</li>~~<li>Then use the '''nmcli con show''' command to view the name of the network device, as shown below<ol style~~=~~"list-style-type: lower-alpha;"><li>'''orangepi''' is the name of the WIFI network~~ USB interface ~~(the names are not necessarily the same)</li><li>'''Wired connection 1''' is the name of the Ethernet interface</li></ol></li></ol>~~test ==

~~orangepi@orangepi~~{| class="wikitable" style="background-color:~$ #ffffdc;width:800px;" |-| <big>'''~~nmcli con show~~The USB interface can be connected to a USB hub to expand the number of USB interfaces.'''</big>|}

~~NAME UUID TYPE DEVICE~~=== Connect the USB mouse or keyboard test ===

~~'''orangepi''' cfc4f922-ae48-46f1-84e1-2f19e9ec5e2a wifi wlan0~~# 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)

~~'''Wired connection 1''' 9db058b7~~

~~<ol start~~=~~"3" style~~=~~"list-style-type: decimal;"><li>Then enter~~ = Connect the ~~following command, where</li></ol>~~USB storage device test ===

~~<blockquote>a. '''"Wired connection 1"''' means to set~~ # First insert the U disk or USB mobile hard disk into the ~~static IP address~~ USB interface of the ~~Ethernet port. If~~ Orange Pi development board# Execute the following command, if you ~~need to set~~ can see the ~~static IP address~~ output of ~~the WIFI~~sdX, ~~please change~~ it to means that the ~~corresponding name of the WIFI network interface (you can get it through the '''nmcli con show''' command)~~U disk is recognized successfully

~~b. After~~ ::{| class="wikitable" style="width:800px;"|-|orangepi@orangepi:~$ '''~~ipv4.addresse~~cat /proc/partitions | grep "sd*"''' ~~is the static IP address to be set, which can be modified to the value you want to set~~ major minor #blocksname 8030044160 '''sda''' 8130043119 '''sda1''' |}

c. <ol start="3" style="list-style-type: decimal;"><li>Use the mount command to mount the U disk into '''~~ipv4.gateway~~/mnt''' ~~indicates~~ , and then you can view the ~~address of~~ file in the ~~gateway~~U disk</~~blockquote~~li>~~orangepi@orangepi:~$ '''nmcli con mod "Wired connection 1" \'''~~

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~ipv4.addresses "192.168.1.110" \~~sudo mount /dev/sda1 /mnt/'''

orangepi@orangepi:~$ '''~~ipv4.gateway "192.168.1.1" \~~ls /mnt/'''

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

~~'''ipv4.method~~ /dev/sda1 &~~quot~~nbsp;~~manual~~&~~quot~~nbsp;~~'''~~  29G    208K    29G    1% /mnt|}</ol>

~~<ol start~~=~~"4" style~~=~~"list-style-type: decimal;"><li>Then restart the Linux system</li></ol>~~= USB wireless network card test ===

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

~~<ol start~~{| class="5wikitable" style="~~list-style~~width:800px;text-~~type~~align: ~~decimal~~center;">~~<li>Then re~~|-| No.| Model||-~~enter the Linux system and use the '''ip addr show eth0'''command to see that the IP address has been set to the desired value</li></ol>~~| 1| RTL8723BU

~~orangepi@orangepi:~$ '''ip addr show eth0'''~~Support 2.4G WIFI+BT4.0

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

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

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

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

~~inet6 240e:3b7:3240:c3a0:97de:1d01:b290:fe3a/64 scope global dynamic noprefixroute~~Support BT 4.2

~~valid_lft 259183sec preferred_lft 172783sec~~| <div class="figure">

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

~~valid_lft forever preferred_lft forever~~</div>|}

== ~~SSH remote login development board;~~ == RTL8723BU test ====

~~'''Linux systems enable ssh remote login by default and allow~~ # First insert the RTL8723BU wireless network card module into the USB interface of the ~~root user to log in to~~ development board# Then the Linux system~~. Before logging in with ssh, you first need to ensure that~~ will automatically load the ~~Ethernet or wifi network is connected~~RTL8723BU bluetooth and WIFI-related kernel modules, ~~and then use~~ through the ~~ip addr~~ lsmod command ~~or check~~ , you can see that the ~~router to obtain the IP address of the development board.'''~~following kernel modules have been automatically loaded

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

~~# Obtain~~ <ol start="3" style="list-style-type: decimal;"><li>Through the ~~IP address of the development board# Then~~ dmesg command, you can ~~remotely log in to~~ see the ~~Linux system through~~ loading information of the ~~ssh command~~RTL8723BU module</li>

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

~~root@192~~.~~168~~.1.~~xx's password: (Enter the password here, the default password is orangepi)~~...

~~'''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.~~'''~~438901] usb 2-1: new high-speed USB device number 2 using ehci-platform

~~'''If you are prompted to refuse the connection~~[ 83.588375] usb 2-1: New USB device found, ~~as long as you are using the image provided by Orange Pi~~idVendor=0bda, ~~please do not suspect that the password orangepi is wrong~~idProduct=b720, ~~but look for other reasons~~bcdDevice= 2.~~'''~~00

~~<ol start~~[ 83.588403] usb 2-1: New USB device strings: Mfr=~~"3" style~~1, Product=~~"list-style-type: decimal;"><li>After successfully logging in to the system~~2, ~~the display is as shown in the figure below</li></ol>~~SerialNumber=3

~~<div class="figure">~~[ 83.588422] usb 2-1: Product: 802.11n WLAN Adapter

[~~[File:pi3b-img204~~83.~~png|405x207px|L467QDF65C(YR79U]TH[TND]~~588443]usb 2-1: Manufacturer: Realtek

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

~~root@orangepi~~[ 83.601974] Bluetooth: hci0: RTL:~~~# '''reset_ssh.sh'''~~examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723

~~'''If it still doesn't work, try to reset the system~~[ 83.~~'''~~603894] Bluetooth: hci0: RTL: rom_version status=0 version=1

~~<~~[ 83.603920] Bluetooth: hci0: RTL: loading rtl_bt/~~span>=== SSH remote login development board under Windows ===~~rtl8723b_fw.bin

~~# First obtain the IP address of the development board~~[ 83.610108] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_config.bin

~~2) Under Windows~~[ 83.611274] Bluetooth: hci0: RTL: cfg_sz 68, ~~you can use MobaXterm to remotely log in to the development board, first create a new ssh session~~total sz 22564

a[ 83. ~~Open '''Session'''~~658494] rtk_btusb: Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519-142432

b[ 83. ~~Then select '''SSH''' in '''Session Setting'''~~658651] usbcore: registered new interface driver rtk_btusb

c[ 83. ~~Then enter the IP address of the development board in the '''Remote host'''~~667124] usb 2-1: This Realtek USB WiFi dongle (0x0bda:0xb720) is untested!

d[ 83. ~~Then enter the user name '''root''' or '''orangepi''' of the Linux system in '''Specify username'''~~667137] usb 2-1: Please report results to Jes.Sorensen@gmail.com

e[ 83. ~~Finally click '''OK'''~~890140] usb 2-1: Vendor: Realtek

~~<div class="figure">~~[ 83.890153] usb 2-1: Product: 802.11n WLAN Adapter

[~~[File:pi3b-img205~~83.~~png|553x280px|14]~~890159]usb 2-1: rtl8723bu_parse_efuse: dumping efuse (0x200 bytes):

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

~~'''Note that when entering the password~~[ 83.890412] usb 2-1: RTL8723BU rev E (SMIC) 1T1R, TX queues 3, WiFi=1, ~~the specific content of the entered password will not be displayed on the screen~~BT=1, ~~please do not think that there is any fault~~GPS=0, ~~just press Enter after inputting.'''~~HI PA=0

~~<div class="figure">~~[ 83.890417] usb 2-1: RTL8723BU MAC: 00:13:ef:f4:58:ae

[~~[File~~83.890421] usb 2-1:~~pi3b-img206.png|578x150px|C~~rtl8xxxu:~~\Users\orangepi\Desktop\用户手册插图\pi 3b\just press Enter after inputting~~Loading firmware rtlwifi/rtl8723bu_nic.~~.jpgjust press Enter after inputting.]]~~bin

~~</div><ol start="4" style="list~~[ 83.895289] usb 2-~~style-type~~1: ~~decimal;"><li>After successfully logging in to the system, the display is as shown in the figure below</li></ol>~~Firmware revision 35.0 (signature 0x5301)

[~~[File:pi3b-img207~~84.~~png|576x334px]~~050893]Bluetooth: hci0: RTL: fw version 0x0e2f9f73

~~== The method of uploading files to the Linux system of the development board ==~~[ 84.266905] Bluetooth: RFCOMM TTY layer initialized

~~=== How to upload files to the development board Linux system in Ubuntu PC ===~~[ 84.266949] Bluetooth: RFCOMM socket layer initialized

~~==== How to upload files using the scp command ====~~[ 84.266999] Bluetooth: RFCOMM ver 1.11

~~# Use the scp command to upload files from the Ubuntu PC to the Linux system of the development board~~[ 84. ~~The specific commands are as follows~~884270] usbcore: registered new interface driver rtl8xxxu

[ 84.912046] rtl8xxxu 2-1:1.2 wlx0013eff458ae: renamed from wlan0|}</ol><ol start="4" style="list-style-type: decimal;"><~~blockquote~~li>aThen you can see the RTL8723BU WIFI device node through the '''sudo ifconfig''' command. Please refer to [[Orange Pi 3B#WIFI connection test|'''~~file_path~~the WIFI connection test chapter''']] for WIFI connection and testing methods</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi: ~~need to be replaced with the path of the file to be uploaded~~~$ '''sudo ifconfig wlx0013eff458ae'''

~~b. '''orangepi'''~~wlx0013eff458ae: ~~It is the user name of the Linux system of the development board~~flags=4099<UP, ~~and it can also be replaced with other ones~~BROADCAST, ~~such as root~~MULTICAST> mtu 1500

~~c. '''192.168.xx.xx'''~~: ~~It is the IP address of the development board, please modify it according to the actual situation~~:ether 00:13:ef:f4:58:ae txqueuelen 1000 (Ethernet)

~~d. '''/home/orangepi'''~~: ~~The path in the Linux system of the development board, which can also be modified to other paths</blockquote>test@test~~:~~~$ '''scp file_path orangepi@192.168.xx~~RX packets 0 bytes 0 (0.~~xx:/home/orangepi/'''~~0 B)

~~<ol start="2" style="list-style-type~~: ~~decimal;"><li>If you want to upload a folder, you need to add the -r parameter</li></ol>~~:RX errors 0 dropped 0 overruns 0 frame 0

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

::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0|}</ol><ol start="35" style="list-style-type: decimal;"><li>~~There are more usages of scp, please use~~ Then you can see the USB Bluetooth device through the ~~following~~ '''hciconfig''' command ~~to view the man manual~~</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt update && sudo apt install bluez'''

~~test~~orangepi@~~test~~orangepi:~$ '''~~man scp~~hciconfig'''

hci0: Type: Primary Bus: '''USB~~==== How to upload files using filezilla ====~~'''

~~# First install filezilla in Ubuntu PC~~::BD Address: 00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16

~~test@test~~:~~~$ '''sudo apt install -y filezilla'''~~:DOWN

~~<ol start="2" style="list-style-type~~: ~~decimal;"><li>Then use the following command to open filezilla</li></ol>~~:RX bytes:1252 acl:0 sco:0 events:125 errors:0

~~test@test~~:~$ :TX bytes:23307 acl:0 sco:0 commands:125 errors:0|}</ol><ol start="6" style="list-style-type: decimal;"><li>You can also see the Bluetooth icon on the desktop. At this time, Bluetooth has not been opened, so a red '''~~filezilla~~x'''will be displayed</li>

[[File:pi3b-img243.png]]</ol><ol start="37" style="list-style-type: decimal;"><li>~~The interface after filezilla is opened is as follows, and the display under the remote site~~ Click '''Turn Bluetooth On''' to turn on ~~the right is empty~~Bluetooth</li~~></ol~~>

[[File:pi3b-img244.png]]<~~div class~~/ol><ol start="8" style="~~figure~~list-style-type: decimal;"><li>The display after turning on Bluetooth is as follows</li>

[[File:pi3b-~~img208~~img245.png~~|576x453px|截图 2022~~]]</ol><ol start="9" style="list-12style-~~03 19-04-40~~type: decimal;"><li>Please refer to the [[Orange Pi 3B#How to use Bluetooth|'''Bluetooth use method''']]for Bluetooth test method, so I won't go into details here.</li></ol>

<~~/div><ol start="4" style~~span id="~~list-style~~rtl8811-~~type: decimal;~~test">~~<li>The method of connecting the development board is shown in the figure below</li~~></olspan>

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

~~[[File:pi3b-img209~~# First insert the RTL8811 wireless network card module into the USB interface of the development board.~~png|575x128px|图片565]]~~# Then the Linux system will automatically load the kernel modules related to RTL8811 WIFI, and you can see that the following kernel modules have been automatically loaded through the lsmod command

::{| class="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''lsmod'''</~~div~~p><~~ol start~~span style="5margin-right: 100px;" >Module Size Used by <lispan style="margin-right: 100px;">8821cu ~~Then choose to '''save the password''', and then click '''OK'''~~1839104 </lispan>0</olspan> |}

~~[[File~~<ol start="3" style="list-style-type: decimal;"><li>Through the dmesg command, you can see the loading information of the RTL8811 module</li>{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img210.png~~|~~249x181px]]~~orangepi@orangepi:~$ '''dmesg'''

~~<ol start="6" style="list~~[ 118.618194] usb 2-~~style~~1: new high-~~type: decimal;"><li>Then choose to always '''trust this host''', and then click '''OK'''</li></ol>~~speed USB device number 2 using ehci-platform

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

[~~[File:pi3b-img211~~118.~~png|278x150px|IMG_256]~~767181]usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

~~</div><ol start="7" style="list~~[ 118.767199] usb 2-~~style-type~~1: Product: ~~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>~~802.11ac NIC

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

[~~[File:pi3b-img212~~118.~~png|533x330px|IMG_256]~~767235]usb 2-1: SerialNumber: 123456

~~</div><ol start="8" style="list-style-type~~[ 119.500530] usbcore: ~~decimal;">~~<li>Then select the path to be uploaded to the development board on the right side of the filezilla software, and then select the file to be uploaded on the 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>registered new interface driver rtl8821cu

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

~~[[File~~wlx1cbfced9d260:~~pi3b-img213.png|485x380px|IMG_256]]~~flags=4099<UP,BROADCAST,MULTICAST> mtu 1500

~~</div>~~9::ether 1c:bf:ce:d9:d2:60 txqueuelen 1000 (Ethernet) ~~After the upload is complete, you can go to the corresponding path in the Linux system of the development board to view the uploaded file~~

10::RX packets 0 bytes 0 (0.0 B) ~~The method of uploading a folder is the same as that of uploading a file, so I won’t go into details here~~

~~=== The method of uploading files from Windows PC to the Linux system of the development board ===~~::RX errors 0 dropped 0 overruns 0 frame 0

~~==== How to upload files using filezilla ====~~::TX packets 0 bytes 0 (0.0 B)

~~# First download the installation file of the Windows version of the filezilla software, the download link is as follows~~::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0|}</ol>

~~https://filezilla-project.org/download.php?type~~=~~client~~=== RTL8821CU test ====

~~<div class="figure">~~# First insert the rtl8821cu wireless network card module into the USB interface of the development board# Then use the '''lsusb''' command to see the device information of the rtl8821cu usb wifi module, please make sure that the USB module is not in Driver CDROM Mode

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-~~img214.png~~|~~472x171px~~orangepi@orangepi:~$ '''lsusb |~~C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-15.jpg未标题-15]]~~grep "Realtek"'''

~~</div>~~Bus 002 Device 003: ID 0bda:c820 Realtek Semiconductor Corp. 802.11ac NIC~~<div~~ |}::{| class="~~figure~~wikitable" style="background-color:#ffffdc;width:800px;">|-| orangepi@orangepi:~$ '''lsusb | grep "Realtek"'''

~~[[File~~Bus 002 Device 002:~~pi3b-img215~~ID 0bda:1a2b Realtek Semiconductor Corp.~~png|393x283px|图片5552]]~~ RTL8188GU 802.11n WLAN Adapter ('''Driver CDROM Mode''')

~~</div>~~

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

~~<li>The downloaded installation package is as follows, and then double-click to install directly</li></ol>~~

<big>'''~~FileZilla_Server_1~~If the USB WIFI module seen by the lsusb command is in Driver CDROM Mode, please unplug the USB WIFI module again.~~5.1_win64-setup.exe~~If not, please manually execute the following command to switch to the next mode:'''</big>

~~During the installation process, please select '''Decline''' on the following installation interface, and then select '''Next>'''~~

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

~~</div>~~

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

~~</div><ol start~~[ 58.634631] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=~~"9" style~~000c lmp_ver=~~"list-style-type: decimal;"><li>After the upload is complete, you can go to the corresponding path in the Linux system of the development board to view the uploaded file</li><li>The method of uploading a folder is the same as that of uploading a file</li></ol>~~08 lmp_subver=8821

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

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

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

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

~~<ol start="2" style="list-style-type~~[ 59.122471] Bluetooth: ~~decimal;"><li>After starting the Linux system, if the HDMI monitor has image output, it means that the HDMI interface is in normal use</li></ol>~~hci0: RTL: fw version 0x829a7644

~~'''Note that although many notebook computers have an HDMI~~ [ 59.265513] usbcore: registered new interface, the HDMI interface of the notebook generally only has the output function, and does not have the function of HDMI in, that is to say, the HDMI output of other devices cannot be displayed on the notebook screen.'''driver rtl8821cu

~~'''When you want to connect the HDMI of the development board to the HDMI port of the laptop, please make sure that your laptop supports the HDMI in function~~[ 59.~~'''~~280119] rtl8821cu 2-1:1.2 wlx90de80521825: renamed from wlan0|}</ol>

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

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

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

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

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

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

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

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

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

'''When using HDMI to VGA display, the development board and the Linux system of the development board do not need to make any settings, only the HDMI interface of the development board can display normally. So if there is a problem with the test, please check whether there is a problem with the HDMI to VGA converter, VGA cable and monitor.'''::BD Address: 00:13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16

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

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

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

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

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

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

~~[[File:pi3b~~

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

~~[[File:pi3b-img228.png|415x277px]]~~# First, you need to prepare a USB camera that supports UVC protocol as shown in the figure below or similar, and then insert the USB camera into the USB port of the Orange Pi development board

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

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

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

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

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

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

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

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

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

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

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

[[File:pi3b-img247.png]]

</ol>

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

~~[[File~~orangepi@orangepi:~~pi3b~~~$ '''sudo apt-~~img233~~get install -y fswebcam'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>After installing fswebcam, you can use the following command to take pictures<ol style="list-style-type: none;"><li>a) -d The option is used to specify the device node of the USB camera</li><li>b) --no-banner Used to remove the watermark of photos</li><li>c) -r The option is used to specify the resolution of the photo</li><li>d) -S The option is used to set the number of previous frames to skip</li><li>e) .~~png~~/image.jpg The name and path for setting the generated photos</li>{|~~243x229px]]~~class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo''' '''fswebcam -d /dev/video0 \'''

'''--no-banner -r 1280x720 -S 5 ./image.jpg'''|}</ol></li></ol><ol start="53" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then open~~ In the ~~configuration interface~~ desktop version of the ~~Bluetooth device~~Linux system, you can directly view the captured pictures through the HDMI display</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''scp image.jpg''' [~~[File~~mailto:test@192.168.1.55:~~pi3b-img234~~/home/test test@192.168.1.~~png~~55:/home/test] '''（Modify the IP address and path according to the actual situation）'''|~~438x179px]]~~}</ol><ol start="64" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Click '''Search''' to start scanning~~ In the desktop version of the Linux system, you can directly view the captured pictures through the ~~surrounding Bluetooth device~~HDMI display</li></ol></li></ol>

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

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

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

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

~~[[File~~<ol start="2" style="list-style-type:~~pi3b-img237.png|417x152px]]~~decimal;"><li>Then find the following file (if there is no audio file in the system, you can upload a audio file to the system by yourself)</li>

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

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

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

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

[[File:pi3b-img251.png]]<~~span id~~/ol><ol start="2" style="~~usb~~list-style-~~interface~~type: lower-~~test~~alpha;"><li>When playing audio, the audio equipment options that play software can be used will be displayed in '''Playback'''. As shown in the figure below, which audio equipment you need to play here can be set.</~~span~~li>~~== USB interface test ==~~

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

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

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

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

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

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

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

~~8 0 30044160 '''sda'''~~**** List of PLAYBACK Hardware Devices ****

~~8 1 30043119~~ '''~~sda1~~card 0: rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]'''

~~<ol start="3" style="list-style-type~~: ~~decimal;"><li>Use the mount command to mount the U disk into~~ '''Subdevices: 0/~~mnt~~1'''~~, and then you can view the file in the U disk</li></ol>~~

~~orangepi@orangepi~~:~$ '''~~sudo mount /dev/sda1 /mnt/~~Subdevice #0: subdevice #0'''

~~orangepi@orangepi~~card 1:~~~$ '''ls /mnt/'''~~rockchiphdmi [rockchip,hdmi], device 0: fe400000.i2s-i2s-hifi i2s-hifi-0 [fe400000.i2s-i2s-hifi i2s-hifi-0]

~~test.txt~~:Subdevices: 0/1

~~<ol start="4" style="list-style-type~~: ~~decimal;"><li>After the mounting, you can view the capacity of the U disk through the '''df -h''' command and the mounting point</li></ol>~~Subdevice #0: subdevice #0

~~orangepi@orangepi~~:~$ Subdevice #0: subdevice #0|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then use the '''~~df -h | grep "sd"~~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>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''aplay -D hw:0,0 /~~dev~~usr/~~sda1 29G 208K 29G 1%~~ share/~~mnt~~sounds/alsa/audio.wav'''

Playing WAVE 'audio.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo|}</ol> === ~~USB wireless network card test~~ = HDMI Audio Play Test ====

~~The currently '''tested''' USB wireless network cards are shown below. Please test it by yourself for~~ # First use the HDMI to HDMI cable to connect the Orange PI development board to the TV (other ~~models~~ HDMI displays need to ensure that the audio can be played)# Then check the sound card serial number of ~~USB wireless network cards~~HDMI. ~~If you cannot use it~~From the output below, you ~~need to transplant~~ can know that the ~~corresponding USB wireless network~~ HDMI sound card is '''card ~~driver~~1'''

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

|-

| ~~No.| Model~~||orangepi@orangepi:~$ '''aplay -~~| 1| RTL8723BU~~l'''

~~Support 2.4G WIFI+BT4.0~~**** List of PLAYBACK Hardware Devices ****

| card 0: rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [~~File:pi3b~~dailink-multicodecs rk817-hifi-~~img240.png~~0]]|-~~| 2| RTL8811~~

~~Support 2.4G +5G WIFI~~:Subdevices: 0/1

~~| [[File~~:~~pi3b-img241.png]]~~|-~~| 3| RTL8821CU~~Subdevice #0: subdevice #0

~~Support 2~~'''card 1: rockchiphdmi [rockchip,hdmi], device 0: fe400000.~~4G +5G WIFI~~i2s-i2s-hifi i2s-hifi-0 [fe400000.i2s-i2s-hifi i2s-hifi-0]'''

~~Support BT 4.2~~:'''Subdevices: 0/1'''

~~| <div class="figure">~~:'''Subdevice #0: subdevice #0'''

~~[[File~~:~~pi3b-img242.png~~'''Subdevice #0: subdevice #0'''|~~tb_imag e_share_1670833201 123]]~~}

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

|}

</ol>

~~~~==== ~~RTL8723BU~~ Use the command to test =the recording method ===

# ~~First insert~~ Orange Pi 3B development board does not have MICs, and can only record audio through headphones with MIC function. After inserting the ~~RTL8723BU wireless network card module~~ headset with the MIC function into ~~the USB interface of~~ the development board~~# Then~~ , the ~~Linux system~~ command below will ~~automatically load the RTL8723BU Bluetooth and WiFi -related kernel modules. You can see that the kernel module below is automatically loaded~~ record a piece of audio through the ~~lsmod command~~headset

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

~~Module Size Used by~~orangepi@orangepi:~$ '''arecord -D hw:0,0 -d 5 -f cd -t wav /tmp/test.wav'''|}

~~rfcomm 57344 16~~

~~rtl8xxxu 106496 0~~== Temperature Sensor ==

~~rtk_btusb 61440 0~~# The command to view the system temperature sensor is:

~~<ol start~~::{| class="3wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>You can see the loading information of the RTL8723BU module through the dmesg command</li></ol>~~|-| orangepi@orangepi:~$ '''sensors'''

~~orangepi@orangepi:~$ '''dmesg'''~~soc_thermal-virtual-0

~~......~~Adapter: Virtual device

~~[ 83~~temp1: +41.~~438901] usb 2-1: new high-speed USB device number 2 using ehci-platform~~9°C (crit = +115.0°C)

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

~~[ 83.588403] usb 2~~gpu_thermal-~~1: New USB device strings: Mfr=1, Product=2, SerialNumber=3~~virtual-0

~~[ 83.588422] usb 2-1~~Adapter: ~~Product: 802.11n WLAN Adapter~~Virtual device

~~[ 83~~temp1: +43.~~588443] usb 2-1: Manufacturer: Realtek~~8°C|}

~~[ 83.588460] usb~~ <ol start="2" style="list-1style-type: decimal;"><li>The command to view the current temperature of the nvme ssd solid state drive is:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo smartctl -a /dev/nvme0 | grep "Temperature:"'''Temperature: ~~SerialNumber~~'''40 Celsius'''|}</li></ol>

~~[ 83.601974] Bluetooth: hci0: RTL: examining hci_ver~~

~~[ 83.603894] Bluetooth: hci0: RTL: rom_version status~~=~~0 version~~=140 Pin interface pin explanation ==

~~[ 83.603920] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_fw.bin~~# Orange Pi 3B Development board 40 Pin interface pins, please refer to the figure below

~~[ 83.610108] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_config.bin~~<div class="figure">

::[[ 83File:pi3b-img254.~~611274~~png]] ~~Bluetooth: hci0: RTL: cfg_sz 68, total sz 22564~~

~~[ 83~~</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.~~658494] rtk_btusb~~<ol style="list-style-type: ~~Realtek Bluetooth USB driver ver 3.1.6d45ddf.20220519~~lower-~~142432~~alpha;"><li>Below is a complete pins of 40pin</li>

[ 83[File:pi3b-img255-1.~~658651~~png]] ~~usbcore~~</ol><ol start="2" style="list-style-type: ~~registered new interface driver rtk_btusb~~lower-alpha;"><li>The following form is a picture on the left half of the full table above, which can be seen clearly</li>

[ 83[File:pi3b-img256-1.~~667124~~png] ~~usb 2~~]</ol><ol start="3" style="list-1style-type: ~~This Realtek USB WiFi dongle (0x0bda:0xb720)~~ lower-alpha;"><li>The following form is ~~untested!~~a picture on the right half of the top table above, which can be seen clearly</li>

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

~~[ 83.890140] usb 2~~

~~[ 83.890153] usb 2-1: Product: 802.11n WLAN Adapter~~== How to install wiringOP ==

~~[ 83.890159] usb 2~~{| class="wikitable" style="background-1color: ~~rtl8723bu_parse_efuse: dumping efuse (0x200 bytes)~~#ffffdc;width:800px;" |-| <big>'''Note that wiringOP has been pre -installed in the Linux image released by Orange Pi. Unless wiringOP's code is updated, it is not necessary to re -download and install. Just use it directly.'''

~~......~~

~~[ 83.890412] usb 2~~'''The storage path of the compiled wiringOP's Deb is wrapped in Orangepi-1Build: ~~RTL8723BU rev E (SMIC) 1T1R, TX queues 3, WiFi=1, BT=1, GPS=0, HI PA=0~~'''

~~[ 83~~'''orangepi-build/external/cache/debs/arm64/wiringpi_x.xx.~~890417] usb 2-1: RTL8723BU MAC: 00:13:ef:f4:58:ae~~deb'''

~~[ 83.890421] usb 2-1: rtl8xxxu: Loading firmware rtlwifi/rtl8723bu_nic.bin~~

~~[ 83~~'''After entering the system, you can run the gpio readall command.~~895289] usb 2~~If you can see the output below, it means that wiringOP is pre -~~1: Firmware revision 35~~installed and can be used normally.~~0 (signature 0x5301)~~'''</big>

~~[ 84.050893] Bluetooth: hci0: RTL: fw version 0x0e2f9f73~~<div class="figure">

[ 84[File:pi3b-img258-1.~~266905~~png]] ~~Bluetooth: RFCOMM TTY layer initialized~~

~~[ 84~~</div><big>'''wiringOP is currently mainly adapted to the functions of setting GPIO port input and output, setting GPIO port output high and low levels, and setting up and down pull-down resistors.~~266949] Bluetooth: RFCOMM socket layer initialized~~Functions such as hardware PWM are not available.'''</big>|}

~~[ 84.266999] Bluetooth: RFCOMM ver 1.11~~# Download the code of wiringOP

~~[ 84.884270] usbcore~~: ~~registered new interface driver rtl8xxxu~~:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt update'''

~~[ 84.912046] rtl8xxxu 2~~orangepi@orangepi:~$ '''sudo apt install -~~1:1.2 wlx0013eff458ae: renamed from wlan0~~y git'''

~~<ol start="4" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>Then you can see the RTL8723BU WIFI device node through the~~ ~$ '''~~sudo ifconfig~~git clone https://github.com/orangepi-xunlong/wiringOP.git -b next''' ~~command. Please refer to the WIFI connection test a [[\l~~|~~'''section for WIFI connection''']] and testing methods</li></ol>~~}

~~orangepi@orangepi~~:~$ :{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that Orange Pi 3B needs to download the code of the wiringOP next branch, please don'~~sudo ifconfig wlx0013eff458ae~~t miss the parameter of -b next.'''

~~wlx0013eff458ae: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500~~

~~ether 00~~'''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:~~13:ef:f4:58:ae txqueuelen 1000 (Ethernet)~~/usr/src/wiringOP'''</big>|}

~~RX packets 0 bytes 0 (0.0 B)~~<ol start="2" style="list-style-type: decimal;"><li>Compile and install wiringOP</li>

~~RX errors 0 dropped 0 overruns 0 frame 0~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''cd wiringOP'''

~~TX packets 0 bytes 0 (0~~orangepi@orangepi:~/wiringOP$ '''sudo .~~0 B)~~/build clean'''

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~orangepi@orangepi:~/wiringOP$ '''sudo ./build'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Test the output of the GPIO Readall command as follows</li>

<~~ol start~~div class="5figure" ~~style="list-style-type: decimal;"><li>Then you can see the USB Bluetooth device through the '''hciconfig''' command</li></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''sudo apt update && sudo apt install bluez'''~~pi3b-img258-1.png]]

~~orangepi@orangepi:~$ '''hciconfig'''~~</div></ol>

~~hci0: Type: Primary Bus: '''USB'''~~== 40Pin interface GPIO, I2C, UART, SPI, and PWM test ==

~~BD Address~~{| class="wikitable" style="background-color: 00#ffffdc;width:~~13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16~~800px;" |-| <big>'''Note that if you need to set overlays to open multiple configurations at the same time, please use a space to write in one line like the following space.'''</big>

~~DOWN~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''

~~RX bytes~~'''overlays=spi3-m0-cs0-spidev i2c2-m1 i2c3-m0 uart7-m2 uart9-m2 pwm11-m1'''|}

~~TX bytes:23307 acl:0 sco:0 commands:125 errors:0~~=== 40pin GPIO port test ===

~~<ol start~~{| class="6wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~You can also see the Bluetooth icon on the desktop. At this time, Bluetooth has not been opened, so a red~~ '''xThe 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.''' ~~will be displayed</li></ol>~~

~~[[File:pi3b-img243.png|576x157px]]~~

~~<ol start="7" style="list-style-type: decimal;"><li>Click~~ '''~~Turn Bluetooth On~~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''' ~~to open Bluetooth</li></ol>~~

~~[[File:pi3b-img244.png|576x262px]]~~

~~<ol start="8" style="list-style-type: decimal;"><li>~~'''The ~~display after opening Bluetooth~~ method of running blink_all_gpio program is shown below: '''</~~li></ol~~big>

~~[[File~~orangepi@orangepi3b:~~pi3b-img245.png|576x164px]]~~~$ '''sudo blink_all_gpio'''         #Remember to add Sudo permissions

~~<ol start="9" style="list-style-type~~[sudo] password for orangepi: ~~decimal~~     ">~~<li>Please refer~~   #You need to ~~the [[\l|~~enter password here'''~~Bluetooth use method''']] for Bluetooth test method, so I won't go into details here.</li></ol>~~|}

~~==== RTL8811 test ====~~# There are a total of '''28''' GPIO ports in the 40pins of the development board that can be used. The following uses pin 7—the corresponding GPIO is GPIO4_C3——the corresponding wPi serial number is 2—as an example to demonstrate how to set the high and low levels of the GPIO port

~~# First insert the RTL8811 wireless network card module into the USB interface of the development board.# Then the Linux system will automatically load the RTL8811 WIFI~~ ::[[File:pi3b-img259-~~related kernel modules~~1. ~~You can see that the kernel module below is automatically loaded through the lsmod command~~png]]

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~~~$ '''lsmod'''~~decimal;"> ~~Module Size Used by~~ ~~8821cu 1839104 0~~<li>First set the GPIO port as the output mode, the third parameter needs to enter the serial number of the wPi corresponding to the pins</li>

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

|-

|

root@orangepi:~/wiringOP# '''gpio mode 2 out'''

|}

</ol>

<li>~~You~~ Then set the GPIO port to output the low level. After setting, you can ~~see~~ use the value of the ~~loading information~~ voltage of the ~~RTL8811 module through~~ pins with a multimeter. If it is 0v, it means that the ~~dmesg command~~low level flat is successful</li~~></ol~~>

~~orangepi~~{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ /wiringOP# '''~~dmesg~~gpio write 2 0''' ~~[ 118.618194] usb 2-1: new high-speed USB device number 2 using ehci-platform~~|}

~~[ 118.767152] usb 2-1: New USB device found, idVendor=0bda, idProduct=c811~~Using GPIO Readall, ~~bcdDevice= 2.00~~ ~~[ 118.767181] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3~~ ~~[ 118.767199] usb 2-1: Product: 802.11ac NIC~~ ~~[ 118.767219] usb 2-1: Manufacturer: Realtek~~ ~~[ 118.767235] usb 2-1: SerialNumber: 123456~~ ~~[ 119.500530] usbcore: registered new interface driver rtl8821cu~~ ~~[ 119.525498] rtl8821cu 2-1:1~~you can see the value of the No. 7 pin (V) to 0 ~~wlx1cbfced9d260: renamed from wlan0~~

[[File:pi3b-img260.png]]

</ol>

<li>Then set the GPIO port to output a high level. After setting, you can ~~see~~ use a multimeter to measure the ~~WiFi device node through~~ voltage value of the ~~'''sudo ifconfig''' command~~pin. ~~Please refer to~~ If it is 3.3v, it means that the ~~[[\l|'''WiFi connection test a section''']] for WIFI connection and testing methods~~high level is set successfully. ~~I won't go into details her~~</li~~></ol~~>

~~orangepi~~{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ /wiringOP# '''~~sudo ifconfig wlx1cbfced9d260~~gpio write 2 1'''|}

~~wlx1cbfced9d260: flags=4099<UP~~Using GPIO Readall,~~BROADCAST,MULTICAST> mtu 1500~~you can see the value of No. 7 pin (v) into 1

~~ether 1c~~[[File:bfpi3b-img261-1.png]]</ol><ol start="5" style="list-style-type:~~ce:d9:d2:60 txqueuelen 1000 (Ethernet)~~decimal;"><li>The setting method of other pins is similar, just modify the serial number of wPi to the corresponding serial number of the pin</li></ol>

~~RX packets 0 bytes 0 (0.0 B)~~

~~RX errors 0 dropped 0 overruns 0 frame 0~~=== 40pin GPIO port pull-down resistance setting method ===

~~TX packets 0 bytes 0 (0~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the 4 GPIO pins below Orange Pi 3B are invalid because there are 3.~~0 B)~~3V on the outside, so setting drop-down is invalid. Other pins can be set normally '''</big>

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~[[File:pi3b-img262-1.png|center]]|}

~~==== RTL8821CU test ====~~corresponding wPi serial number 5—to demonstrate how to set up and down pull-down resistance of the GPIO port

~~# First insert the rtl8821cu wireless network card module into the USB interface of the development board# Then use the '''lsusb''' command to see the device information of the rtl8821cu usb wifi module~~::[[File:pi3b-img263-1. ~~Make sure the USB module is not in the Driver CDROM Mode~~png]]

<ol start="2" style="list-style-type: decimal;"><li>First of all, you need to set the GPIO port as the input mode. The third parameter needs to enter the serial number of the wPi corresponding to the pins</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio mode 5 in'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>After the setting is set to input mode, execute the following command to set the GPIO port as the pull-down mode</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ /wiringOP# '''gpio mode 5 up'~~lsusb~~ ''| ~~grep &quot~~}</ol><ol start="4" style="list-style-type: decimal;~~Realtek&quot~~"><li>Then enter the following command to read the level of the GPIO port. If the level is 1, it means that the drawing mode is successful</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio read 5''' '''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# '''gpio read 5'''

~~Bus 002 Device 003~~'''0'''|}</ol>

~~orangepi@orangepi:~$ '''lsusb | grep "Realtek"'''~~=== 40pin SPI Test ===

~~Bus 002 Device 002: ID 0bda:1a2b Realtek Semiconductor Corp. RTL8188GU 802.11n WLAN Adapter ('''Driver CDROM Mode''')~~# From the schematic diagram of the 40PIN interface, the SPI available for Orange Pi 3B is spi3

~~'''If the USB WIFI module seen by the lsusb command is in Driver CDROM Mode, re~~ ::[[File:pi3b-~~insert the USB WiFi module~~img264-1. ~~If not, please manually execute the following command to switch the mode: '''~~png]]

<ol start="2" style="list-style-type: decimal;"><li>In the linux system, the SPI in the 40 pin is closed by default, and it needs to be opened manually before it can be used. The detailed steps are as follows:<ol style="list-style-type: lower-alpha;"><li>First run '''orangepi-config''', normal users remember to add sudo permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ~~usb_modeswitch~~ orangepi-KW config'''|}</li><li>Then select '''System'''[[File:pi3b-~~v 0bda~~ 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>

<li>~~The~~ After restarting, enter the system to check whether there is a spidev3.0 device node in the Linux system ~~will automatically load the RTL8821CU Bluetooth~~ . If it exists, it means that SPI3 has been set up and ~~WIFI -related kernel modules. You~~ can ~~see that the kernel module below is automatically loaded through the lsmod command~~be used directly</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~lsmod~~ls /dev/spidev3.0'''

~~Module Size Used by~~/dev/spidev3.0|}</ol><ol start="4" style="list-style-type: decimal;"><li>Do not short-circuit the mosi and miso pins of SPI3, the output result of running spidev_test is as follows, you can see that the data of TX and RX are inconsistent</li>

~~8821cu 1839104~~ {| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo spidev_test -v -D /dev/spidev3.0'''

~~rtk_btusb 61440 0~~spi mode: 0x0

~~<ol start="4" style="list-style-type~~bits per word: ~~decimal;"><li>You can see the loading information of the rtl8821cu module through the dmesg command</li></ol>~~8

~~orangepi@orangepi~~max speed:~~~$ '''dmesg'''~~500000 Hz (500 KHz)

TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.

~~[ 57~~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 | ...............~~083693] usb 2~~.............….|}</ol><ol start="5" style="list-1style-type: ~~new high-speed USB device number 2 using ehci~~decimal;"><li>Then short-~~platform~~circuit the two pins of mosi (pin 19 in the 40pin interface) and miso (pin 21 in the 40pin interface) of SPI3, and then run the output of spidev_test as follows, you can see the sending and receiving same data</li>

[ 57[File:pi3b-img265.~~231888~~png]] ~~usb 2~~{| class="wikitable" style="width:800px;" |-1| orangepi@orangepi: ~~New USB device found, idVendor=0bda, idProduct=1a2b, bcdDevice= 2~~~$ '''sudo spidev_test -v -D /dev/spidev3.000'''

~~[ 57.231916] usb 2-1~~spi mode: ~~New USB device strings: Mfr=1, Product=2, SerialNumber=0~~0x0

~~[ 57.231937] usb 2-1~~bits per word: ~~Product: DISK~~8

~~[ 57.231956] usb 2-1~~max speed: ~~Manufacturer: Realtek~~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 | ......@.…▒...~~242594] usb-storage 2-1:1~~.~~0: USB Mass Storage device detected~~..............▒.

~~[ 57~~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 | ......@.~~245674] scsi host0: usb~~…▒..................▒.|}</ol>

~~[ 58.069172] usb 2-1: USB disconnect, device number 2~~=== 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.~~440025] usb 2-1: new high-speed USB device number 3 using ehci-platform~~

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

~~[ 58.587827] usb 2-1~~: ~~New USB device strings~~: ~~Mfr~~{| class=~~1, Product~~"wikitable" style=~~2, SerialNumber=3~~"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>|}

<ol start="2" style="list-style-type: decimal;"><li>In the linux system, the I2C bus in the 40 pin is closed by default, and it needs to be opened manually to use it. The detailed steps are as follows:<ol style="list-style-type: lower-alpha;"><li>First run '''orangepi-config''', normal users remember to add '''sudo''' permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li><li>Then select '''System'''[[ 58File:pi3b-1.png]]</li><li>Then select '''Hardware'''[[File:pi3b-2.~~587833~~png]] ~~usb~~ </li><li>Then use the arrow keys on the keyboard to navigate to the position shown in the figure below, and then use the '''space''' to select the I2C configuration you want to open[[File:pi3b-3-2.png]]</li><li>Then select '''<Save>''' to save[[File:pi3b-14.png]]</li><li>Then select '''<Back>'''[[File: ~~Product~~pi3b-5.png]]</li><li>Then select '''<Reboot>''' to restart the system to make the configuration take effect[[File: ~~802~~pi3b-6.~~11ac NIC~~png]]</li></ol></li></ol>

~~[ 58.587838] usb 2~~<ol start="3" style="list-1style-type: decimal;"><li>After starting the Linux system, first confirm that the i2c device node exists under/dev</li>{| class="wikitable" style="width: ~~Manufacturer~~800px;" |-| orangepi@orangepi: ~~Realtek~~~# '''ls /dev/i2c-*'''

~~[ 58.587844] usb~~ /dev/i2c-0      '''/dev/i2c-2'''      '''/dev/i2c-3'''      '''/dev/i2c-~~1: SerialNumber~~4'''      /dev/i2c-6|}</ol><ol start="4" style="list-style-type: ~~123456~~decimal;"><li>Then connect a i2c device on the i2c pin of the 40Pin connector</li>

~~[ 58~~{| 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|Corresponding to No.~~610463] rtk_btusb: Realtek Bluetooth USB driver ver 3~~ 1 pin|Corresponding to No.1pin|-| Gnd Pin|Corresponding to No.~~6d45ddf~~ 6 pin|Corresponding to No.~~20220519~~ 6 pin|Corresponding to No. 6 pin|}</ol><ol start="5" style="list-style-~~142432~~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>~~[ 58.610656] usbcore~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi: ~~registered new interface driver rtk_btusb~~~$ sudo i2cdetect -y 2 #i2c2 command

~~[ 58.634631] Bluetooth~~orangepi@orangepi: ~~hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821~~~$ sudo i2cdetect -y 3 #i2c3 command

~~[ 58.636729] Bluetooth~~orangepi@orangepi: ~~hci0: RTL: rom_version status=0 version=1~~~$ sudo i2cdetect -y 4 #i2c4 command|}

~~[ 58.636740] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin~~<div class="figure">

[ 58[File:pi3b-img267.~~664190~~png]] ~~Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin~~

~~[ 58.664746] Bluetooth: hci0: RTL: cfg_sz 10, total sz 31990~~</div></ol>

~~[ 59.122471] Bluetooth: hci0: RTL: fw version 0x829a7644~~=== 40pin UART test ===

~~[ 59~~# As can be seen from the table below, the uart available for Orange Pi 3B is uart3, uart7, and uart9.~~265513] usbcore: registered new interface driver rtl8821cu~~There are three sets of uart bus

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

~~<ol start~~::{| class="5wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~Then you~~ '''As can ~~see~~ be seen from the ~~RTL8821CU WiFi device node through~~ above table, i2c3_m0 and uart3_m0 are reused by pins, and the ~~'''sudo ifconfig''' command. Please refer to~~ two cannot be opened at the ~~[[\l|~~same time'''~~WiFi connection test''']] a section for WIFI connection and testing methods.~~</~~li></ol~~big>|}

<ol start="2" style="list-style-type: decimal;"><li>In the linux system, the UART in the 40 pins is closed by default, and it needs to be opened manually before it can be used. The detailed steps are as follows:<ol style="list-style-type: lower-alpha;"><li>First run '''orangepi-config''', normal users remember to add sudo permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ~~ifconfig wlx90de80521825~~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>

~~wlx90de80521825~~<ol start="3" style="list-style-type: ~~flags=4099&lt~~decimal;UP"><li>After entering the Linux system,~~BROADCAST,MULTICAST> mtu 1500~~first confirm whether there is a device node corresponding to uart under/dev</li>

~~ether 00~~{| class="wikitable" style="width:13800px;" |-| orangepi@orangepi:~~ef:f4:58:ae txqueuelen 1000 (Ethernet)~~~# '''ls /dev/ttyS*'''

~~RX packets 0 bytes 0 (0.0 B)~~/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 errors 0 dropped 0 overruns 0 frame 0~~{| class="wikitable" style="width:800px;text-align: center;"|-||uart3|uart7|uart9|-| Tx pin|Corresponding to the 28 pin|Corresponding to the 16 pin|Corresponding to the 29 pin|-| Rx Pin|Corresponding to the 27 pin|Corresponding to the 15 pin|Corresponding to the 22 pin|}

~~TX packets 0 bytes 0 (0~~[[File:pi3b-img269-1.~~0 B)~~png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Use the '''gpio serial''' command to test the loop function of the serial port as shown below. If you can see the following printing, it means that the serial communication is normal<ol style="list-style-type: lower-alpha;"><li>Test UART3</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo gpio serial /dev/ttyS3'''

~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~[sudo] password for orangepi: #Enter the password here.

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

~~<li>Then you can see the USB Bluetooth device through the '''hciconfig''' command</li></ol>~~

~~orangepi@orangepi~~Out: 0:~~~$ '''sudo apt~~-~~get update~~ &~~amp~~gt;~~& sudo apt-get install -y bluez'''~~0

~~orangepi@orangepi~~Out:~~~$ '''hciconfig'''~~1: -> 1

~~hci0~~Out: ~~Type~~2: ~~Primary Bus: '''USB'''~~-> 2

~~BD Address~~Out: 003:~~13:EF:F4:58:AE ACL MTU: 820:8 SCO MTU: 255:16~~-> 3

~~DOWN~~Out: 4: -> 4

~~RX bytes~~Out:~~1252 acl~~5:~~0 sco~~-> 5^C|}</ol><ol start="2" style="list-style-type:~~0 events~~lower-alpha;"><li>Test UART7</li>{| class="wikitable" style="width:~~125 errors~~800px;" |-| orangepi@orangepi:0~$ '''sudo gpio serial /dev/ttyS7'''

~~TX bytes~~[sudo] password for orangepi:~~23307 acl:0 sco:0 commands:125 errors:0~~#Enter the password here.

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

~~<li>Bluetooth icons can also be seen on the desktop. At this time, Bluetooth has not been opened, so a red '''x''' will be displayed</li></ol>~~

~~[[File~~Out: 0:~~pi3b~~-~~img243.png|576x157px]]~~> 0

~~<ol start="8" style="list-style~~Out: 1: -~~type: decimal~~>">~~<li>Click '''Turn Bluetooth On''' to open Bluetooth</li></ol>~~1

~~[[File~~Out: 2:~~pi3b~~-~~img244.png|576x262px]]~~> 2

~~<ol start="9" style="list-style~~Out: 3: -~~type: decimal~~>">~~<li>The display after opening Bluetooth is shown below</li></ol>~~3

~~[[File~~Out: 4:~~pi3b~~-~~img245.png|576x164px]]~~> 4

Out: 5: -> 5^C|}</ol><ol start="103" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Please refer to the [[\l~~Test UART9</li>{|class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~Bluetooth use chapter'~~sudo gpio serial /dev/ttyS9''~~]] for the Bluetooth test method. I won~~'~~t go into details her</li></ol>~~

~~=== USB Camera Test ===~~[sudo] password for orangepi: #Enter the password here.

~~# First, you need to prepare a USB camera that supports the UVC protocol in the figure below, and then insert the USB camera into the USB interface of the Orange PI development board~~

~~[[File~~Out: 0:~~pi3b~~-~~img13.png|259x150px]]~~> 0

~~<ol start="2" style="list~~Out: 1: -~~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>~~1

~~orangepi@orangepi~~Out: 2:~~~$ '''v4l2-ctl --list~~-~~devices'''~~> 2

~~Q8 HD Webcam~~Out: 3: ~~Q8 HD Webcam ('''usb'''~~-~~fc880000.usb-1):~~> 3

~~'''/dev/video0'''~~Out: 4: -> 4

Out: 5: -> 5^C|}</~~dev~~ol></~~video1~~li></ol> === PWM test method ===

~~/dev/media0~~# From the table below, the pwm11 available for Orange Pi 3B

~~'''Note that l in v4l2 is a lowercase letter l, not numbers~~ ::[[File:pi3b-img270-1.~~'''~~png]]

<ol start="2" style="list-style-type: decimal;"><li>In the linux system, the PWM in the 40 pin is turned off by default, and it needs to be turned on manually before it can be used. The detailed steps are as follows:<ol style="list-style-type: lower-alpha;"><li>First run '''orangepi-config'''~~In addition~~, ~~Video~~normal users remember to add sudo permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config''~~s serial number is not necessarily Video0~~'|}</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, ~~please refer~~ and then use the '''space''' to ~~what~~ select the PWM configuration you ~~see~~want to open[[File:pi3b-3-4.png]]</li><li>Then select '''<Save>''' to save[[File:pi3b-4.png]]</li><li>Then select '''<Back>'''[[File:pi3b-5.png]]</li><li>Then select '''<Reboot>''' to restart the system to make the configuration take effect[[File:pi3b-6.png]]</li></ol></li></ol>

<li>~~In the desktop system~~After opening a pwm, there will be an extra pwmchipX in '''/sys/class/pwm/''' (X is a specific number), for example, ~~you can use Cheese to directly turn on the USB camera. The cheese~~ after opening ~~method is shown in~~ pwm11, check the ~~figure below:~~ pwmchipX under '''/sys/class/pwm/''' one becomes two</li><{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ls /sys/class/pwm/~~ol>~~'''

~~[[File~~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:~~pi3b~~</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/ -~~img246~~l''' command, you can see that pwmchip1 is linked to fe6f0030.~~png|474x302px]]~~pwm, so pwm11 corresponds to pwmchip as pwmchip1</li>

~~The interface after cheese opens the USB camera is shown in the~~ <div class="figure ~~below:~~ ">

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

</div></ol><ol start="46" style="list-style-type: decimal;"><li>~~How~~ Then use the following command to make pwm11 output a 50Hz square wave (please switch to ~~test~~ the ~~USB camera using fswebcam~~root user first, and then execute the following command)</pli>~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Install fswebcam<~~|-| root@orangepi:~# '''echo 0 > /sys/~~li><~~class/~~ol>~~<pwm/~~li><~~pwmchip1/~~ol>~~export'''

~~orangepi~~root@orangepi:~~~$ '''sudo'''~~ # '''~~apt update~~echo 20000000 > /sys/class/pwm/pwmchip1/pwm0/period'''

~~orangepi~~root@orangepi:~$ # '''~~sudo apt-get install -y fswebcam~~echo 1000000 > /sys/class/pwm/pwmchip1/pwm0/duty_cycle'''

~~<ol start="2" style="list-style-type~~root@orangepi: ~~lower-alpha~~~# '''echo 1 >">~~<li>After installing fswebcam, you can use the following command to take pictures<ol style="list-style-type: lower-alpha;"><li>-d The option is used to specify the device node of the USB camera</li><li>--no-banner Used to remove the watermark of photos<~~/~~p><~~sys/~~li><li>-r The option is used to specify the resolution of the photo<~~class/~~p><~~pwm/~~li><li>-S The option is set to the number of frames before skipping<~~pwmchip1/~~p><~~pwm0/~~li>~~enable'''~~<li>./image.jpg The name and path for setting the generated photos</li></ol></li></ol>~~|}

~~orangepi@orangepi~~[[File:~~~$ '''sudo''' '''fswebcam~~ pi3b-~~d /dev/video0 \'''~~img272.png]]

~~'''~~<li>The test method of pwm11 demonstrated above is similar to other pwm test methods.</li></ol></~~image.jpg'''~~span> == How to install and use wiringOP-Python ==

~~<ol start~~{| class="3wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>In '''wiringOP-Python is the ~~service~~ Python language version of ~~the Linux system~~wiringOP, ~~you can use the scp command~~ which is used to ~~pass~~ operate the ~~picture to~~ hardware resources of the ~~Ubuntu PC to watch after taking~~ development board, such as GPIO, I2C, SPI and UART, in the ~~photo</li></ol>~~Python program.'''

~~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 actual situation）'''~~

~~<ol start="4" style="list-style-type: lower-alpha;"><li>~~'''In ~~the desktop version of the Linux system~~addition, ~~you can directly view~~ please note that all the ~~shot pictures through~~ following commands are operated under the ~~HDMI display~~root user.'''</~~li></ol~~big>|}

== ~~Audio Test~~ = wiringOP-Python installation method ===

~~=== Test audio methods in the desktop system ===~~dependency package

::{| class="wikitable" style="width:800px;" |-| root@orangepi:~# ~~First open the file manager~~'''sudo apt-get update'''

~~[[File~~root@orangepi:~~pi3b~~~# '''sudo apt-~~img248.png~~get -y install git swig python3-dev python3-setuptools'''|~~357x176px]]~~}

<li>Then ~~find~~ use the following ~~file (if there is no audio file in the system, you can upload a audio file~~ command to download the ~~system by yourself)~~source code of wiringOP-Python</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <~~/ol~~big>'''Note that the following git clone--recursivee command will automatically download the source code of wiringOP, because wiringOP-Python depends on wiringOP. Please make sure that the download process does not report an error due to network problems.'''

'''If there is a problem with the download code from GitHub, you can use the wiringOP-Python source code that comes with the Linux image directly, and the storage location is:/usr/src/wiringOP-Python'''<~~div~~ /big>|}{| class="~~figure~~wikitable">style="width:800px;" |-| root@orangepi:~# '''git clone --recursive https://github.com/orangepi-xunlong/wiringOP-Python -b next'''

~~[[File~~root@orangepi:~~pi3b~~~# '''cd wiringOP-~~img249.png|236x186px|图片10]]~~Python'''

root@orangepi:~/wiringOP-Python# '''git submodule update --init --remote'''|}</~~div~~ol>

<li>Then ~~select~~ use the ~~audio.wav file, right~~ following command to compile wiringOP-~~click~~ Python and ~~select VLC to open~~ install it ~~to start playing~~into the Linux system of the development board</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''cd wiringOP-Python'''

~~[[File~~root@orangepi:~~pi3b~~~/wiringOP-~~img250~~Python# '''python3 generate-bindings.py > bindings.~~png|288x234px]]~~i'''

root@orangepi:~/wiringOP-Python# '''sudo python3 setup.py install'''

|}

</ol>

<li>~~Methods~~ Then enter the following command. If there is a help information output, it means that Wiringop-Python is successfully installed. Press the '''q''' key to ~~switch different audio equipment such as HDMI playback and headset playback<ol style="list-style-type: lower-alpha;"><li>First open~~ exit the ~~volume control~~ interfaceof the help information</li~~></ol></li></ol~~>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img251.png~~|~~308x169px]]~~root@orangepi:~/wiringOP-Python# '''python3 -c "import wiringpi; help(wiringpi)"'''

~~<ol start="2" style="list-style-type~~Help on module wiringpi: ~~lower-alpha;">~~<li>When playing audio, the audio equipment options that play software can be used will be displayed in '''Playback'''. As shown in the figure below, which audio equipment you need to play here can be set.</li></ol>

~~[[File:pi3b-img252.png|576x282px]]~~

~~=== How to play audio with commands ===~~NAME

~~==== Headphone interface play audio test ====~~:wiringpi

~~# First insert the headset into the headphone jack of the development board~~

~~[[File:pi3b-img253.png|395x112px]]~~DESCRIPTION

~~<ol start="2" style="list-style-type~~: ~~decimal;"><li>Then you can check the sound card device supported~~ # This file was automatically generated by ~~the Linux system through the '''aplay -l''' command. From the output below, it can be seen that '''card 0''' is the sound card device with RK809, which is the sound card device of the headset<~~SWIG (http:/~~li><~~/~~ol>~~www.swig.org).

~~orangepi@orangepi~~:~~~$ '''aplay -l'''~~# Version 4.0.2

~~**** List of PLAYBACK Hardware Devices ****~~: #

~~'''card 0~~: ~~rockchiprk809 [rockchip~~# Do not make changes to this file unless you know what you are doing-~~rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi~~-~~0]'''~~modify

: # the SWIG interface file instead.|}</ol><ol start="5" style="list-style-type: decimal;"><li>Test whether the wiringOP-Python is installed successfully under the Python command line is shown below:<ol style="list-style-type: lower-alpha;"><li>First use the Python3 command to enter the command line mode of Python3</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''~~Subdevices~~python3'''|}</ol><ol start="2" style="list-style-type: 0lower-alpha;"><li>Then import the Python module of WiringPi</1li>{| 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)'''

~~'''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@orangepi~~:~~~$ '''aplay -l'''~~# the SWIG interface file instead.

~~**** List of PLAYBACK Hardware Devices ****~~

~~card 0: rockchiprk809 [rockchip-rk809], device 0: dailink-multicodecs rk817-hifi-0 [dailink-multicodecs rk817-hifi-0]~~CLASSES

~~Subdevices~~: ~~0/1~~builtins.object

~~Subdevice #0~~: ~~subdevice #0~~:GPIO

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

~~'''Subdevices~~: ~~0/1'''~~:Serial

~~'''Subdevice #0~~: ~~subdevice #0'''~~:nes

~~'''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~~class GPIO(builtins. ~~If the HDMI display or television can hear the sound indicates that the hardware can be used normally</li></ol>~~object)

~~orangepi@orangepi~~:~~~$ '''aplay -D hw:1,~~| GPIO(pinmode=0 ~~/usr/share/sounds/alsa/audio.wav'''~~)

~~=== Use the command to test the recording method ===~~:|

# Orange Pi 3B development board does not have MICs, and can only record audio through headphones with MIC function. After inserting the headset with the MIC function into the development board, the command below will record a piece of audio through the headset

~~orangepi@orangepi:~$ '''amixer~~ >>>|}</ol></li></ol>

~~orangepi@orangepi:~$ '''arecord -D hw:0,0 -d 5 -f cd -t wav /tmp/~~=== 40pin GPIO port test~~.wav'''~~===

~~'''wiringOP-Python is the same as wiringOP, you can also determine which GPIO pin to operate by specifying the wPi number, because there is no command to check the wPi number in wiringOP-Python, so you can only check the board wPi number and physical Correspondence between pins.'''</~~span~~big>~~== Temperature Sensor ==

~~# The command of the system temperature sensor is:~~ <div class="figure">

~~orangepi@orangepi~~[[File:~~~$ '''sensors'''~~pi3b-img258.png|center]]

~~soc_thermal-virtual-0~~</div>|}~~Adapter: Virtual device~~ ~~temp1: +41~~# Below the No.~~9°C (crit = +115.0°C)~~ ~~gpu_thermal~~ 7 pin — corresponding to GPIO4_a4 -~~virtual~~corresponding WPI serial number 2 -0 ~~Adapter: Virtual device~~to demonstrate how to set the height of the GPIO port

~~temp1~~: ~~+43~~:[[File:pi3b-img259.~~8°C~~png]]

<li>The ~~command~~ steps of the ~~current temperature of the NVMe SSD solid -state hard disk is: orangepi@orangepi:~$ '''sudo smartctl -a /dev/nvme0 | grep "Temperature:"'''Temperature: '''40 Celsius'''</li></ol>~~ ~~== 40 Pin interface pin explanation ==~~ ~~# Orange Pi 3B Development board 40 Pin interface pins, please refer to the figure~~ command test are shown below ~~<div class="figure">~~ ~~[[File:pi3b-img254.png|400x124px|C:\Users\orangepi\Desktop\用户手册插图\pi 3b\Orange-Pi-3B-Development-board-40-Pin(1).jpgOrange-Pi-3B-Development-board-40-Pin(1)]]~~ ~~</div><ol start="2" style="list-style-type~~directly: ~~decimal;"><li>The function of the Orange Pi 3B development board 40 PIN interface pins is shown in the table below.~~

<li>~~Below~~ First set the GPIO port to the output mode. The first parameter of the '''pinMode''' function is ~~a complete pins~~ the serial number of ~~40pin~~the wpi corresponding to the pin, and the second parameter is the GPIO mode</li>~~</ol>~~<{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~li></ol>~~wiringOP-Python# '''python3 -c "import wiringpi; \'''

~~[[File:pi3b-img255~~'''from wiringpi import GPIO; wiringpi.~~png|575x160px]]~~wiringPiSetup() ; \'''

'''wiringpi.pinMode(2, GPIO.OUTPUT) ; "'''

|}

</ol>

<li>~~The following form is a picture on~~ Then set the GPIO port output low level. After setting, you can use the voltage of the ~~left half~~ voltage of the ~~full table above~~universal meter to measure the pins. If it is 0V, ~~which can be seen clearly~~it means that the low -power flat is successful</li><{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~ol>~~wiringOP-Python# '''python3 -c "import wiringpi; \'''

~~[[File:pi3b-img256~~'''from wiringpi import GPIO; wiringpi.~~png|478x267px]]~~wiringPiSetup() ;\'''

'''wiringpi.digitalWrite(2, GPIO.LOW)"'''

|}

</ol>

<li>~~The following form is a picture on~~ Then set the GPIO port output high level. After setting, you can use the value of the ~~right half~~ voltage of the ~~top table above~~pins with a multimeter. If it is 3.3V, ~~which can be seen clearly~~it means that the high -power flat is successful.</li><{| class="wikitable" style="width:800px;" |-| root@orangepi:~/~~ol>~~wiringOP-Python# '''python3 -c "import wiringpi; \'''

~~[[File:pi3b-img257~~'''from wiringpi import GPIO; wiringpi.~~png|479x266px]]~~wiringPiSetup() ;\'''

'''wiringpi.digitalWrite(2, GPIO.HIGH)"'''

|}

</ol>

</li></ol>

<li>~~There are a total~~ The steps of ~~'''28''' GPIO ports~~ testing in the ~~40pin interface. The voltage~~ command line of Python3 are shown below: <ol style="list-style-type: lower-alpha;"><li>First use the Python3 command to enter the command line mode of ~~all GPIO ports is~~ Python3</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''~~3.3v~~python3'''~~</li>~~|}</ol> <~~span id~~ol start="2" style="~~how~~list-tostyle-~~install~~type: lower-~~wiringop~~alpha;"><li>Then import the Python module of WiringPi</~~span~~li>{| class="wikitable" style= ~~How to install Wiringop ==~~"width:800px;" |-| >>> '''import wiringpi'''

>>> '''~~Note that Wiringop has been pre~~ from wiringpi import GPIO'''|}</ol><ol start="3" style="list-~~installed in~~ style-type: lower-alpha;"><li>Then set the ~~Linux image released by Orange Pi~~GPIO port as the output mode. ~~Unless Wiringop~~The first parameter of the '~~s code~~ ''pinMode''' function is ~~updated~~the serial number of the wpi corresponding to the pin, it and the second parameter is ~~not necessary to re~~ the GPIO mode.</li>{| class="wikitable" style="width:800px;" |-~~download and install. Just use it directly~~| >>> '''wiringpi.wiringPiSetup()'''

~~'''The storage path of the compiled Wiringop's Deb is wrapped in Orangepi-Build: '''~~0

>>> '''~~orangepi~~wiringpi.pinMode(2, GPIO.OUTPUT)'''|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then set the GPIO port output low level. After setting, you can use the value of the voltage of the pins with a multimeter. If it is 0V, it means that the low -power flat is set.</li>{| class="wikitable" style="width:800px;" |-| >>> '''wiringpi.digitalWrite(2, GPIO.LOW)'''|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then set the GPIO port output high level. After setting, you can use the value of the voltage of the pins with a multimeter. If it is 3.3V, it means that the high -~~build~~power flat is successful</~~external~~li>{| class="wikitable" style="width:800px;" |-| >>> '''wiringpi.digitalWrite(2, GPIO.HIGH</~~cache~~span>)'''|}</~~debs~~ol></~~arm64~~li></~~wiringpi_x~~ol><ol start="4" style="list-style-type: decimal;"><li>Wiringop-Python Sets GPIO high and low levels in the Python code.xxFor reference to the '''blink.~~deb~~py''' test program in Examples, the voltage of the '''blink.py''' test program will set up the voltage of all GPIO ports in the development board 40 PIN</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''cd examples'''

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~~ls blink.py'''

~~<div class="figure">~~'''blink.py'''

~~[[File~~root@orangepi:~~pi3b~~~/wiringOP-~~img258~~Python/examples'''# python3 blink.~~png~~py'''|~~575x355px|66AC(IBG%N8L@Y7(1BZPS`N]]~~}</ol>

~~</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. It is impossible to use functions like hardware PWM.'''=== 40pin SPI test ===

# ~~Download~~ From the ~~code~~ schematic diagram of ~~Wiringop~~the 40pin interface, the SPI available for Orange Pi 3B is spi3

~~orangepi@orangepi~~:~~~$ '''sudo apt update'''~~:[[File:pi3b-img264.png]]

~~orangepi@orangepi~~:~$ :{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~sudo apt install -y git~~In the Linux system, the spi3 in 40pin is closed by default, and it needs to be opened manually to use.'''

~~orangepi@orangepi:~$ '''git clone https://github.com/orangepi-xunlong/wiringOP.git -b next'''~~

'''~~Note that Orange Pi 3B needs to download~~ Add the ~~code~~ configuration of the ~~wiringOP next branch~~red font part below to the /boot/orangepiEnv.txt, ~~please don't miss~~ and then restart the Linux system to open the ~~parameter of -b next~~spi4.'''</big>

~~'''If there is a problem with the download code from GitHub, you can use the wiringOP source code that comes with the Linux image directly, and the storage location is:/usr/src/wiringOP'''~~

~~<ol start="2" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>Compile and install wiringOP<~~~$ '''sudo vim /~~li><~~boot/~~ol>~~orangepiEnv.txt'''

~~orangepi@orangepi:~$~~ '''~~cd wiringOP~~overlays=spi3-m0-cs0-spidev'''|}

~~orangepi@orangepi~~<ol start="2" style="list-style-type:~~~/wiringOP$~~ decimal;"><li>First check whether there is a '''~~sudo~~ spidev3.~~/build clean~~0'''device node in the Linux system. If it exists, it means that the SPI3 has been set and can be used directly</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~~~/wiringOP~~$ '''~~sudo~~ ls /dev/spidev3.~~/build~~0'''

/dev/spidev3.0

|}

</ol>

<li>~~Test~~ You can then use the spi back function under the '''spidev_test.py''' program in Examples. The '''spidev_test.py''' program needs to specify the following two parameters: <ol style="list-style-type: lower-alpha;"><li>'''--channel''': Specify the channel number of SPI</li><li>'''--port''': Specify the port number of SPI</li></ol></li><li>Do not pick up the two pins of the SPI3 MOSI and MISO in short, and run the output result of the ~~GPIO Readall command~~ spidev_test.py as ~~follows~~shown below. You can see that the data of TX and RX are inconsistent</lip></olli>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''cd examples'''

~~<div class="figure">~~root@orangepi:~/wiringOP-Python/examples# '''python3 spidev_test.py \'''

~~[[File:pi3b~~'''-~~img258.png|575x355px|66AC(IBG%N8L@Y7(1BZPS`N]]~~-channel 3 --port 0'''

~~</div>== 40Pin interface GPIO, I2C, UART, SPI, and PWM test ==~~mode: 0x0

~~'''Note that if you need to set overlays to open multiple configurations at the same time, please use a space to write in one line like the following space.'''~~max speed: 500000 Hz (500 KHz)

~~orangepi@orangepi:~$ '''sudo vim~~ Opening device /~~boot~~dev/~~orangepiEnv~~spidev3.~~txt'''~~0

TX | FF FF FF FF FF FF '''~~overlays~~40 00 00 00 00 95'''FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…|

RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |.............….||}</ol><ol start="5" style== "list-style-type: decimal;"><li>Then use the TXD (No. 19 pins in the 40Pin interface) and RXD (No. 21 pins in the 40pin ~~GPIO port~~ interface) of the DuPont line short connection SPI3. Like sending and receiving data, it means that the SPI3 loop test is normal</li>{| class="wikitable" style=="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''cd examples'''

root@orangepi:~/wiringOP-Python/examples# '''~~The Linux system released by Orange Pi has a pre -installed blink_all_gpio program. This program will set up all 28 GPIO ports in 40pin to switch high and low levels~~python3 spidev_test.py \'''

'''~~After running the blink_all_gpio program, when using a multimeter to measure the level of the GPIO~~ --channel 3 --port~~, you will find that the GPIO pin will be switched between~~ 0 ~~and 3.3v. Use this program to test whether the GPIO port can work normally~~'''

~~'''The method of running blink_all_gpio program is shown below~~spi mode: ~~'''~~0x0

~~orangepi@orangepi3b~~max speed:~~~$ '''sudo blink_all_gpio''' #Remember to add Sudo permissions~~500000 Hz (500 KHz)

~~[sudo] password for orangepi: #You need to enter a password here~~Opening device /dev/spidev3.0

TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |. ~~Below is No~~. ~~7 pins -corresponding GPIO as GPIO4_A4 -corresponding WPI serial number 2 -as an example how to set the height of the GPIO port~~....@.......…|

~~[[File~~RX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......~~png~~…|~~576x120px]]~~|}</ol>

~~<ol start~~=~~"2" style~~=~~"list-style-type: decimal;"><li>First set the GPIO port as the output mode, the third parameter needs to enter the serial number of the wPi corresponding to the pins</li></ol>~~= 40pin I2C test ===

~~root@orangepi~~<ol start="1" style="list-style-type:~decimal;"><li>As can be seen from the table below, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total of three groups of I2C bus</~~wiringOP# '''gpio mode 2 out'''~~li>

~~<ol start="3" style="list~~[[File:pi3b-~~style-type: decimal;"><li>Then set the GPIO port to output the low level~~img266. ~~After setting, you can use the value of the voltage of the pins with a multimeter. If it is 0v, it means that the low -electric flat is successful</li></ol>~~png]]

~~root@orangepi~~{| class="wikitable" style="background-color:~#ffffdc;width:800px;" |-| <big>'''It can be seen from the above table that I2C4_M0 and SPI3_M0 are pins. The two cannot be opened at the same time. I2C3_M0 and UART3_M0 are also reused. The two cannot be opened at the same time'''</~~wiringOP~~big>|}{| class="wikitable" style="background-color:# ffffdc;width:800px;" |-| <big>'''~~gpio write 2 0~~In the Linux system, the I2C in 40Pin is closed by default, and it needs to be opened manually to use.'''

~~Using GPIO Readall, you can see the value of the No. 7 pin (v) to 0~~

~~[[File:pi3b-img260~~'''Add the configuration of the red font part below to the/boot/orangepiEnv.~~png|576x120px]]~~txt, and then restart the Linux system to open the I2C2, i2C3, and I2C4 at the same time. If you only need to open one, then fill in one.'''</big>

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

<li>Then set the GPIO port output high level. After setting, you can use the voltage of the voltage of the permanent meter to measure the voltage. If it is 3.3V, it means that the high-electricity level is successful</li></ol>

~~root~~orangepi@orangepi:~~~/wiringOP#~~ $ '''~~gpio write 2 1~~sudo vim /boot/orangepiEnv.txt'''

~~Using GPIO Readall~~'''overlays=i2c2-m1 i2c3-m0 i2c4-m0'''|}</ol><ol start="2" style="list-style-type: decimal;"><li>After starting the Linux system, ~~you can see~~ first confirm the ~~value of No~~I2C device node under/dev. ~~7 pin (v) into 1~~</li>

~~[[File~~{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img261.png~~|~~576x118px]]~~orangepi@orangepi:~# '''ls /dev/i2c-*'''

/dev/i2c-0      '''/dev/i2c-2'''      '''/dev/i2c-3'''      '''/dev/i2c-4'''      /dev/i2c-6|}</ol><ol start="53" style="list-style-type: decimal;"><li>~~The setting method~~ Then connect a I2C device on the I2C pin of ~~other pins~~ the 40PIN connector. Here is ~~similar. Just modify the serial number~~ an example of the ~~wPi sequence number as the corresponding serial number corresponding to the pin~~DS1307 RTC module.</li~~></ol~~>

~~<span id~~{| class="~~pin~~wikitable" style="width:800px;text-~~gpio~~align: center;"|-~~port~~||i2c2-m1|i2c3-~~down~~m0|i2c4-~~and~~m0|-~~downward~~| Sda Pin|Corresponding to No. 3 pin|Corresponding to No. 27 pin|Corresponding to No. 19 pin|-~~pull~~| Sck Pin|Corresponding to No. 5 pin|Corresponding to No. 28 pin|Corresponding to No. 23 pin|-| Vcc Pin|Corresponding to No. 1 pin|Corresponding to No. 1 pin|Corresponding to No. 1 pin|-~~down-resistance-setting-method">=== 40Pin GPIO Port -down and downward pull -down resistance setting method ===~~| Gnd Pin|Corresponding to No. 6 pin|Corresponding to No. 6 pin|Corresponding to No. 6 pin|}

[[File:pi3b-img273.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then use the '''i2cdetect -y'''~~Note that~~ command If the ~~4 GPIO pins below Orange Pi 3B are invalid because there are 3.3V on~~ address of the ~~outside~~connected I2C device can be detected, ~~so setting drop -down is invalid. Other pins~~ it means that the I2C can be ~~set~~ used normally~~'''~~</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ sudo i2cdetect -y 2 #i2c2 command

~~[[File~~orangepi@orangepi:~~pi3b~~~$ sudo i2cdetect -~~img262.png|575x353px]]~~y 3 #i2c3 command

orangepi@orangepi:~$ sudo i2cdetect -y 4 # ~~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~~i2c4 command|}

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

~~<ol start="2" style="list~~[[File:pi3b-~~style-type: decimal;"><li>First of all, you need to set the GPIO port as the input mode~~img274. ~~The third parameter needs to enter the serial number of the wpi corresponding to the pins</li></ol>~~png]]

</div></ol><ol start="5" style="list-style-type: decimal;"><li>You can then run the time of the ds '''ds1307.py''' test program in '''examples''' to read the RTC time</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''~~gpio mode 5 in~~cd examples'''

~~<ol start="3" style="list~~root@orangepi:~/wiringOP-~~style~~Python/examples# '''python3 ds1307.py -~~type: decimal;"><li>After the setting is set to input mode, execute the following command to set the GPIO port as the pull~~ -~~down mode</li></ol>~~device \'''

~~root@orangepi:~/wiringOP#~~ '''~~gpio mode 5 up~~"/dev/i2c-4"'''

~~<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:55

~~root@orangepi~~Thu 2023-01-05 14:~~~/wiringOP# '''gpio read 5'''~~57:56

~~'''1'''~~Thu 2023-01-05 14:57:57

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

~~root@orangepi:~~~exit|}</~~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></ol>~~= 40pin's UART test ===

~~root@orangepi:~/wiringOP~~# ~~'''gpio read 5'''~~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

~~'''0'''~~::[[File:pi3b-img268.png]]

~~'''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'''</~~span~~big>~~=== 40pin SPI Test ===|}

::{| class="wikitable" style="width:800px;background-color:# ~~From the schematic diagram of the 40PIN interface, the SPI available for Orange Pi 3B is spi3~~ffffdc;" |-~~[[File:pi3b-img264.png~~|~~577x193px]]~~ <big>'''In the Linux system, the ~~SPI3~~ UART in 40pin is closed by default, and it needs to be opened manually to use.'''

'''Add the configuration of the red font part below to the /boot/orangepiEnv.txt, and then restart the Linux system to open the ~~spi3~~UART3, UART7, and UART9 at the same time.If you only need to open one, you can fill in one'''</big>

orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''

'''overlays=~~spi3~~uart3-m0uart7-~~cs0~~m2 uart9-~~spidev~~m2'''|}

<li>~~First check~~ After entering the Linux system, first confirm whether there is a ~~'''spidev3.0'''~~ device node ~~in the Linux system. If it exists, it means that the SPI3 has been set. You can use it directly~~corresponding to UART under/dev</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ # '''ls /dev/~~spidev3.0~~ttyS*''' ~~/dev/spidev3.0~~

/dev/ttyS1      '''/dev/ttyS3      /dev/ttyS7      /dev/ttyS9'''

|}

</ol>

<li>~~Do not shorten~~ Then start testing the ~~two pins of the SPI3 MOSI and MISO~~UART interface, and ~~run~~ first use the ~~output result~~ RX and TX of the ~~spidev_test as shown below. You can see that the data of TX and RX is inconsistent~~UART interface to be tested by DuPont</li~~></ol~~>

~~orangepi~~{| class="wikitable" style="width:800px;text-align: center;"|-||uart3|uart7|uart9|-| Tx Pin|Corresponding to the 28 pin|Corresponding to the 16 pin|Corresponding to the 29 pin|-| Rx Pin|Corresponding to the 27 pin|Corresponding to the 15 pin|Corresponding to the 7 pin|}</ol><ol start="4" style="list-style-type: decimal;"><li>Use the '''serialTest.py''' program in Examples to test the loop function of the serial port. If you can see the printing below, it means that the serial communication is normal<ol style="list-style-type: lower-alpha;"><li>Test UART3</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ /wiringOP-Python/examples# '''~~sudo spidev_test~~ python3 serialTest.py -v -~~D /dev/spidev3.0~~device \'''

~~spi mode: 0x0~~'''"/dev/ttyS3"'''

~~bits per word: 8~~

~~max speed~~Out: ~~500000 Hz (500 KHz)~~0: -> 0

~~TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.~~Out: 1: -> 1

~~RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF | ............................….~~Out: 2: -> 2

~~<ol start="4" style="list-style~~Out: 3: -~~type: decimal~~>"><li>Then the two pins of the SPI3 MOSI (No. 19 pins in the 40pin interface) and MISO (No. 21 in the 40PIN interface) run the output of SPIDEV_TEST as follows.You can see that sending and receiving data is the same.</li></ol>3

~~[[File~~Out:~~pi3b-img265.png|577x83px]]~~4:^C

~~orangepi~~exit|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Test UART7</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ /wiringOP-Python/examples# '''~~sudo spidev_test~~ python3 serialTest.py -v -~~D /dev/spidev3.0~~device \'''

~~spi mode: 0x0~~'''"/dev/ttyS7"'''

~~bits per word: 8~~

~~max speed~~Out: ~~500000 Hz (500 KHz)~~0: -> 0

~~TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.~~Out: 1: -> 1

~~RX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.~~Out: 2: -> 2

~~=== 40pin I2C Test ===~~> 3

~~# From the table below, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total of three groups of I2C bus.~~Out: 4:^C

~~[[File~~exit|}</ol><ol start="3" style="list-style-type:~~pi3b~~lower-~~img266~~alpha;"><li>Test UART9</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python/examples# '''python3 serialTest.~~png|576x160px]]~~py --device \'''

'''~~It can be seen from the above table that i2c4_m0 and spi3_m0 are pins. The two cannot be opened at the same time. i2c3_m0 and uart3_m0 are also reused. The two cannot be opened at the same time~~"/dev/ttyS9"'''

~~'''In the Linux system, the i2c in 40Pin is closed by default, and it needs to be opened manually to use.'''~~

'''Add the configuration of the red font part below to the /boot/orangepiEnv.txt, and then restart the Linux system to open the i2c2, i2c3, and i2c4 at the same time. If you only need to open one, then fill in one.'''Out: 0: -> 0

~~orangepi@orangepi~~Out:~~~$ '''sudo vim /boot/orangepiEnv.txt'''~~1: -> 1

~~'''overlays=i2c2~~Out: 2: -~~m1 i2c3-m0 i2c4-m0'''~~> 2

~~<ol start="2" style="list-style~~Out: 3: -~~type: decimal~~>">~~<li>After starting the Linux system, first confirm that the i2c device node exists under/dev</li></ol>~~3

~~orangepi@orangepi~~Out:~~~# '''ls /dev/i2c-*'''~~4:^C

exit|}</~~dev~~ol></~~i2c~~li></ol></~~dev/i2c-6~~span>

~~<ol start~~=~~"3" style~~=~~"list-style-type: decimal;"><li>Then connect a i2c device on~~ Hardware watch the ~~i2c pin of the 40Pin connector</li></ol>~~door dog test ==

~~{| class="wikitable"~~|The WatchDog_test program is pre -|~~| 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~~installed in the Linux system released by Orange PI, which can be tested directly. ~~6 pin~~|}

~~<ol start="4" style="list-style-type: decimal;"><li>Then use the '''i2cdetect -y''' command if the address~~ The method of running the ~~connected I2C device can be detected, it means that the I2C can be used normally</li></ol>~~WatchDog_test program is shown below:

~~orangepi@orangepi~~<ol style="list-style-type:~~~$ sudo i2cdetect~~ lower-~~y 2 #i2c2 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>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo ~~i2cdetect -y 3 #i2c3 command~~watchdog_test 10'''

~~orangepi@orangepi:~$ sudo i2cdetect -y 4 #i2c4 command~~open success

~~<div class="figure">~~options is 33152,identity is sunxi-wdt

~~[[File~~put_usr return,if 0,success:~~pi3b-img267.png|476x179px|UN}~]Q}T_70O%Z%RNO8R@YE]]~~0

~~</div>~~The old reset time is: 16~~=== 40pin UART test ===~~1,success:0

~~# As can be seen from the table below~~put_user 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~~put_usr return,if 0,success:~~pi3b-img268.png|575x160px]]~~0

~~'''As can be seen from the above table, i2c3_m0 and uart3_m0 are reused by pins, and the two cannot be opened at the same time'''~~keep alive

~~'''In the Linux system, the uart in 40pin is closed by default, and it needs to be opened manually to use.'''~~keep alive

~~'''Add~~ keep alive|}</ol></~~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..'''~~span>

~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''~~== Check the serial number of the RK3566 chip ==

~~'''overlays=uart3-m0 uart7-m2 uart9-m2'''~~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 start~~{| class="2wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>After entering the Linux system, first confirm whether there is a device node corresponding to uart under/dev</li></ol>~~|-| orangepi@orangepi:~$ '''cat_serial.sh'''

~~orangepi@orangepi~~Serial :~# '''ls /dev/ttyS*8fa18eaf489041f0'''|}

</~~dev/ttyS1 '''/dev'''/'''ttyS3 /dev/ttyS7 /dev/ttyS9'''~~span>

~~<ol start~~=~~"3" style~~=~~"list-style-type: decimal;"><li>Then start testing the uart interface, first use~~ The method of downloading and installing the ~~rx and tx~~ balenaEtcher version of ~~the uart interface to be tested by DuPont</li></ol>~~arm64 ==

<ol style="list-style-type: decimal;"><li>The download address of Balenaetcher ARM64 version is: <ol style="list-style-type: lower-alpha;"><li>The download address of the Deb installation package is shown below, and it needs to be installed to use</li>{| class="wikitable" style="width:800px;"

|-

|'''https://github.com/Itai-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balena-etcher-electron_1.7.9+5945ab1f_arm64.deb'''| }</ol><ol start="2" style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"~~| uart3~~><li>The download address of the Appimage version that does not need to be installed is shown below: </li>{| ~~style~~class="~~text-align: left;~~wikitable"~~| uart7~~| style="~~text-align~~width: ~~left~~800px;"~~| uart9~~

|-

|}

~~[[File:pi3b-img269.png|545x134px]]~~<div class="figure">

[[File:pi3b-img275.png]] </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'''    &gtnbsp; ~~5^C~~1% /tmp|}</ol><ol start="3" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Test UART9~~Then enter the following command in the Linux system to start the installation of the Bt-Panel</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo install_bt_panel.sh'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then the pagoda installation program reminds whether to install the '''Bt-Panel''' to the'''/www''' folder, and enter '''y''' at this time</li>{| class="wikitable" style="width:800px;" |-| +----------------------------------------------------------------------

~~orangepi@orangepi:~$ '''sudo gpio serial~~ | Bt-WebPanel FOR CentOS/~~dev~~Ubuntu/~~ttyS9'''~~Debian

~~[sudo] password for orangepi: #Enter the password here.~~+----------------------------------------------------------------------

~~Out: 1:~~ +----------------------------------------------------------------------~~> 1~~

~~Out~~| The WebPanel URL will be http: 2//SERVER_IP: ~~-> 2~~8888 when installed.

~~Out: 3:~~ +----------------------------------------------------------------------~~> 3~~

~~Out: 4: -> 4~~

~~Out~~Do you want to install Bt-Panel to the /www directory now?(y/n): '''y'''|}</ol><ol start="5" style="list-style-type: ~~-&gt~~decimal; ~~5^C~~"><li>Then you have to wait patiently. When you see the printing information below the terminal output, it means that the pagoda has been installed. The entire installation process takes about 34 minutes. There may be some differences according to the difference in network speed</li>

[[File:pi3b-img278.png|800px]]</ol><~~span id~~ol start="~~pwm~~6" style="list-~~test~~style-~~method~~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]]</~~span~~li>~~=== PWM test method ===~~<li>After successfully logging in to the pagoda, the following welcome interface will pop up. First, please take the intermediate user notice to read to the bottom, and then you can choose "I have agreed and read" User Agreement ", and then click" Enter the panel " You can enter the Bt-Panel</li>

~~# From~~ [[File:pi3b-img280.png|1200px]]</ol><ol start="8" style="list-style-type: decimal;"><li>After entering the ~~table below~~Bt-Panel, you will first prompt that you need to bind the ~~pwm11 available for Orange Pi 3B~~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>

[[File:pi3b-~~img270~~img281.png|~~575x160px~~1200px]]</ol><ol start="9" style="list-style-type: decimal;"><li>The final display interface is shown in the figure below. You can intuitively see some status information of the development board Linux system, such as load state, CPU usage, memory usage and storage space usage</li>

~~'''In~~ [[File:pi3b-img282.png|1200px]]</ol><ol start="10" style="list-style-type: decimal;"><li>More functions of the ~~Linux system,~~ Bt-Panel can refer to the ~~pwm in 40pin is closed~~ following information to explore by ~~default, and it needs to be opened manually to use..'''~~yourself</li>

{| class="wikitable" style="width:800px;" |-| Manual: [http://docs.bt.cn '''~~Add the configuration of the red font part below to the~~ http:/~~boot~~/~~orangepiEnv~~docs.~~txt, and then restart the Linux system to open the pwm11~~bt.cn''']

~~orangepi@orangepi~~Forum address:~$ [https://www.bt.cn/bbs '''~~sudo vim~~ https:/~~boot~~/~~orangepiEnv~~www.bt.~~txt~~cn/bbs''']

GitHub Link: '''~~overlays=pwm11-m1~~https://github.com/aaPanel/BaoTa'''|}</ol>

~~<ol start~~=~~"2" style~~=~~"list-style-type: decimal;"><li>After opening a pwm, a pwmchipX (X is a specific number) will be available in'''/sys/class/pwm/'''</li></ol>~~Set the Chinese environment and install Chinese input method ==

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

~~pwmchip0 pwmchip1~~=== Debian system installation method ===

<ol ~~start="3"~~ style="list-style-type: decimal;"><li>~~Which pwmchip corresponds to pwm11 above? Let's first check out~~ First set the ~~output of~~ default '''~~ls /sys/class/pwm/ -l~~locale''' ~~command,~~ as ~~shown below:~~ Chinese<~~/li~~ol style="list-style-type: lower-alpha;"><li>~~The base address of~~ Enter the ~~pwm11 register is Fe6F0030. Then see the output of~~ command below to start configured '''~~ls /sys/class/pwm/ -l~~locale''' ~~command, you can see that the fe6f0030.pwm is connected to the pwmchip1, so the PWM11 corresponding pwmchip is pwmchip1~~</li~~></ol~~>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''|}</ol><~~div class~~ol start="2" style="~~figure~~list-style-type: lower-alpha;"><li>Then select '''zh_CN.UTF-8 UTF-8''' in the pop-up interface (to move up and down through the upper and lower direction buttons on the keyboard, select it through the space key, and finally move the cursor to '''<OK>''' through the TAB key, then press the ENTER key )</li>

[[File:pi3b-~~img271~~img283.png|~~576x46px|RCUS$_~VYM{4ZS]_L}DNZQR~~1200px]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then set the default '''locale''' as '''zh_CN.UTF-8'''</li>

[[File:pi3b-img284.png|1200px]]</~~div~~ol><ol start="54" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then use~~ After exiting the interface, the ~~following command to allow pwm11 to~~ '''locale''' settings will be started. The output ~~a 50Hz square wave (please switch to~~ displayed by the ~~root user first, and then execute the following~~ command)line is shown below</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''

~~root@orangepi:~# '''echo 0 > /sys/class/pwm/pwmchip1/export'''~~Generating locales (this might take a while)...

~~root@orangepi~~:~~~# '''echo 20000000 > /sys/class/pwm/pwmchip1/pwm0/period'''~~en_US.UTF-8... done

~~root@orangepi~~:~~~# '''echo 1000000 > /sys/class/pwm/pwmchip1/pwm0/duty_cycle'''~~zh_CN.UTF-8... done

~~root@orangepi~~Generation complete.|}</ol></li></ol><ol start="2" style="list-style-type:~# decimal;"><li>Then open '''~~echo 1 > /sys/class/pwm/pwmchip1/pwm0/enable~~Input Method'''</li>

[[File:pi3b-~~img272~~img285.png~~|575x346px~~]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then select '''OK'''</li>

[[File:pi3b-img286.png]]</ol><~~span id~~ol start="~~how-to-install-and~~4" style="list-~~use~~style-~~wiringop-python~~type: decimal;"><li>Then select '''Yes'''</~~span~~li>~~== How to install and use Wiringop-Python ==~~

[[File:pi3b-img287.png]]</ol><ol start="5" 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.fcitx'''</li>

[[File:pi3b-img288.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then select '''~~Please note that all the following command below is operated under the root user.~~OK'''</li>

[[File:pi3b-img289.png]]</ol><~~span id~~ol start="7" style="~~wiringop~~list-~~python~~style-~~installation-method~~type: decimal;"><li>'''Then restart the Linux system to make the configuration effective'''</li>~~=== Wiringop-Python installation method ===~~<li>Then open '''Fcitx configuration'''</li>

~~# First install~~ [[File:pi3b-img290.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then click the ~~dependency package~~+ of the position shown in the figure below</li>

~~root@orangepi~~[[File:~# pi3b-img291.png]]</ol><ol start="10" style="list-style-type: decimal;"><li>Then search '''~~sudo apt-get update~~Google Pinyin''' and click '''OK'''</li>

~~root@orangepi:~# '''sudo apt-get -y install git swig python3-dev python3-setuptools'''~~<div class="figure">

~~<ol start="2" style="list-style-type~~[[File: ~~decimal;"><li>Then use the following command to download the source code of wiringOP~~pi3b-~~Python</li></ol>~~img292.png]]

</div></ol><ol start="11" style="list-style-type: decimal;"><li>Then put '''Note that the following git clone--recursivee command will automatically download the source code of Wiringop, because Wiringop-Python depends on Wiringop. Please make sure that the download process does not report an error due to network problems.Google Pinyin'''to the front</li>

~~'''If there is a problem with the download code from GitHub, you can use the Wiringop-Python source code that comes with the Linux image directly, and the storage location is~~[[File:~~/usr/src/wiringOP~~pi3b-~~Python'''~~img293.png]]

~~root@orangepi~~[[File:~~~# '''git clone~~ pi3b-~~-recursive https://github~~img294.~~com~~png]]</~~orangepi~~ol><ol start="12" style="list-~~xunlong/wiringOP~~style-~~Python -b next~~type: decimal;"><li>Then open the '''Geany'''editor to test the Chinese input method</li>

~~root@orangepi~~[[File:~~~# '''cd wiringOP~~pi3b-~~Python'''~~img295.png]]</ol><ol start="13" style="list-style-type: decimal;"><li>The Chinese input method test is shown below</li>

~~root@orangepi~~[[File:~pi3b-img296.png]]</~~wiringOP~~ol><ol start="14" style="list-~~Python#~~ 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 ''~~git submodule update~~ 'zh_CN.UTF-8'''</li>{| class="wikitable" style="width:800px;" |-~~init --remote~~| orangepi@orangepi:~$ '''sudo vim /etc/default/locale'''

<~~ol start="3" style="list-style-type: decimal;"><li~~p>~~Then use the following command to compile wiringOP~~# File generated by update-~~Python and install it into the Linux system of the development board</li>~~locale</olp>

~~root@orangepi:~#~~ LC_MESSAGES='''~~cd wiringOP~~zh_CN.UTF-~~Python~~8'''

~~root@orangepi:~/wiringOP-Python#~~ LANG='''~~python3 generate~~zh_CN.UTF-~~bindings.py > bindings.i~~8'''

~~root@orangepi~~LANGUAGE='''zh_CN.UTF-8'''|}</~~wiringOP~~ol><ol start="16" style="list-~~Python#~~ style-type: decimal;"><li>Then '''~~sudo python3 setup.py install~~restart the system'''to see the system displayed as Chinese</li>

[[File:pi3b-img297.png]]</ol ~~start~~><li>Then enter the following command~~20. ~~If there is a help information output, it means that Wiringop~~04-~~Python is successfully installed. Press the '''q''' key to exit the interface of the help information</lisystem"></olspan>

~~root@orangepi:~/wiringOP-Python# '''python3 -c "import wiringpi; help(wiringpi)"'''~~=== The installation method of Ubuntu 20.04 system ===

~~Help on module wiringpi:~~# First open '''Language Support'''

~~NAME~~::[[File:pi3b-img298.png]]

~~wiringpi~~<ol start="2" style="list-style-type: decimal;"><li>Then find '''Chinese (China)''' option</li>

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

~~# This file was automatically generated by SWIG (http~~[[File:~~//www.swig.org)~~pi3b-img300.png]]

{| class="wikitable" style="background-color:# ~~Version~~ ffffdc;width:800px;" |-| <big>'''Note that this step is not easy to drag, please try more patiently.'''</big>|}</ol><ol start="4~~.0.2~~" style="list-style-type: decimal;"><li>Then select the '''Apply System-Wide''' to apply the Chinese settings to the entire system</li>

#[[File:pi3b-img301.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 ~~changes to this file unless you know what you are doing~~the configuration effective'''</li><li>After re -~~-modify~~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>

# [[File:pi3b-img303.png]]</ol><ol start="8" style="list-style-type: decimal;"><li>Then you can see that the ~~SWIG interface file instead.~~desktop is displayed as Chinese</li>

[[File:pi3b-img304.png]]</ol><ol start="59" style="list-style-type: decimal;"><li>~~Test whether~~ Then we can open the ~~Wiringop-Python is installed successfully under~~ '''Geany''' to test Chinese input method , and the ~~Python command line~~ way to open is shown in the figure below: ~~<ol style="list-style-type: lower-alpha;">~~<li~~>First use the Python3 command to enter the command line mode of Python3</li></ol></li></ol~~>

~~root@orangepi~~[[File:~# pi3b-img305.png]]</ol><ol start="10" style="list-style-type: decimal;"><li>After opening '''Geany''', the default is an English input method. We can switch into Chinese input method through the '''~~python3~~Ctrl+Space'''shortcut keys, and then we can enter Chinese</li>

[[File:pi3b-img306.png]]</ol ~~start~~>~~<li>Then import the Python module of WiringPi</li~~></olspan>

~~>>> '''import wiringpi;'''~~=== The installation method of ubuntu 22.04 system ===

~~<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~~ # First open '''qLanguage Support''' ~~key to exit the interface of the help information</li></ol>~~

~~>>> '''help(wiringpi)'''~~::[[File:pi3b-img298.png]]

~~Help on module wiringpi~~<ol start="2" style="list-style-type:decimal;"><li>Then find '''Chinese (China)''' option</li>

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

~~wiringpi~~[[File:pi3b-img308.png]]

~~DESCRIPTION~~{| 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>

[[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</~~www.swig.org).~~li>

~~# Version 4~~[[File:pi3b-img303.~~0.2~~png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Then you can see that the desktop is displayed as Chinese</li>

#[[File:pi3b-img304.png]]</ol><ol start="8" style="list-style-type: decimal;"><li>Then open the Fcitx5 configuration program</li>

~~# Do not make changes to this file unless you know what you are doing~~[[File:pi3b-img310.png]]</ol><ol start="9" style="list-style-~~modify~~type: decimal;"><li>Then choose to use Pinyin input method</li>

~~# the SWIG interface file instead.~~ ~~CLASSES~~<div class="figure">

~~builtins~~[[File:pi3b-img311.~~object~~png]]

~~GPIO~~</div></ol><ol start="10" style="list-style-type: decimal;"><li>The interface after the selection is shown below, then click OK</li>

~~I2C~~[[File:pi3b-img312.png]]</ol><ol start="11" style="list-style-type: decimal;"><li>Then we can open the '''Geany''' to test Chinese input method, and the way to open is shown in the figure below</li>

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

~~nes~~[[File:pi3b-img313.png]]</ol>

~~class GPIO(builtins.object)~~== How to remotely log in to the Linux system desktop method ==

{| ~~GPIO(pinmode~~class=0)"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>|}

|=== Use nomachine remote login ===

~~&gt~~{| class="wikitable" style="background-color:#ffffdc;~~>&gt~~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'''<~~span id~~/big>|}{| class="~~pin~~wikitable" style="background-~~gpio~~color:#ffffdc;width:800px;" |-~~port~~| <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-~~test~~color:#ffffdc;width:800px;" |-1"| <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.'''</~~span~~big>~~=== 40pin GPIO port test ===~~|}

'''Wiringop-Python is the same as Wiringop. You can also determine which GPIO pink can be determined by specifying the WPI number. Because there is no command to check the WPI number in Wiringop-Python, you can only check the board WPI number and physical physical physics through the GPIO command in Wiringop. The corresponding relationship of the pin.''' ~~<div class="figure">~~ ~~[[File:pi3b-img258.png|575x355px|66AC(IBG%N8L@Y7(1BZPS`N]]~~ ~~</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|576x120px]]~~ <ol ~~start="2"~~ style="list-style-type: decimal;"><li>~~The steps~~ First download the nomachine software Linux '''ARM64''' DEB version of the ~~command test are shown below directly:~~ installation package, and then install it in the Linux system of the development board

<li>~~First set~~ Since RK3566 is a SOC of the ~~GPIO port~~ ARMV8 architecture, the system we use is Ubuntu or Debian, so you need to ~~the output mode. The first parameter of the~~ download '''~~pinMode~~NoMachine for ARM ARMv8 DEB''' ~~function~~ 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 ~~serial number~~ DEB package of the ~~wpi corresponding to the pin, and the second parameter is the GPIO mode<~~ARMV8/~~li>~~ARM64 version.'''</olbig><|}{| class="wikitable" style="width:800px;" |-| [https://www.nomachine.com/download/download&id=112&s=ARM '''https://downloads.nomachine.com/~~li><~~download/~~ol>~~?id=118&distro=ARM''']|}

~~root@orangepi~~[[File:~pi3b-img314.png]]</~~wiringOP~~ol><ol start="2" style="list-style-type: lower-~~Python#~~ alpha;"><li>In addition, you can also download the installation package to '''NoMachine''~~python3 -c "import wiringpi; \~~' in the '''official tools'''.</li>

~~'''from wiringpi import GPIO; wiringpi.wiringPiSetup() ; \'''~~ ~~'''wiringpi.pinMode(2, GPIO.OUTPUT) ; "'''~~ ~~<ol start="2" style="list-style-type~~[[File: ~~lower~~pi3b-~~alpha;"><li>Then set the GPIO port output low level~~img315. ~~After setting, you can use the voltage of the voltage of the universal meter to measure the pins. If it is 0V, it means that the low -power flat is successful</li></ol>~~png]]

~~root@orangepi:~/wiringOP-Python#~~ First enter the '''~~python3~~ remote login software-~~c "import wiringpi; \~~Nomachine'''folder

~~'''from wiringpi import GPIO; wiringpi~~[[File:pi3b-img316.~~wiringPiSetup() ;\'''~~png]]

~~'''wiringpi.digitalWrite(2, GPIO.LOW)"'''~~Then download the ARM64 version of the DEB installation package

[[File:pi3b-img317.png]]

</ol>

<li>Then ~~set~~ upload the ~~GPIO port output high level~~downloaded '''nomachine_x. ~~After setting, you can~~ x.x_x_arm64.deb''' to the Linux system of the development board.</li><li>Then use the ~~value of~~ following command to install '''NoMachine''' in the ~~voltage~~ Linux system of the ~~pins with a multimeter. If it is 3.3V, it means that the high -power flat is successful.~~development board</lip></olli>{| class="wikitable" style="width:800px;" ~~root~~|-| orangepi@orangepi:~~~/wiringOP~~$ '''sudo dpkg -~~Python#~~ i nomachine_x.x.x_x_arm64_arm64.deb'''~~python3~~ |}</ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>Then download the nomachine software Windows version of the installation package, the download address is shown below</li>{| class="wikitable" style="background-~~c &quot~~color:#ffffdc;~~import wiringpi~~width:800px; ~~\'''~~" |-| <big>'''~~from wiringpi import GPIO; wiringpi~~Note that this download link may change.~~wiringPiSetup() ;\~~'''</big>|}{| class="wikitable" style="width:800px;" |-| '''~~wiringpi~~https://downloads.~~digitalWrite(2, GPIO~~nomachine.~~HIGH)"~~com/download/?id=9'''|}

[[File:pi3b-img318.png]]

</ol>

<li>~~The steps of testing~~ Then install nomachine in Windows. '''Please restart the ~~command line of Python3 are shown below:~~ computer after installation'''<~~ol style="list-style-type: lower-alpha;"~~/li><li>~~First use the Python3 command to enter the command line mode of Python3~~<~~/li~~p>Then open '''NoMachine''' in Window</olp></li~~></ol~~>

~~root@orangepi~~[[File:~~~# '''python3'''~~pi3b-img319.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, and then click the location shown in the red box below in the figure below. Start log in to the Linux system desktop of the development board</li>

[[File:pi3b-img320.png]]</ol><ol start="26" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~import the Python module of WiringPi~~click '''OK'''</li~~></ol~~>

~~>>&gt~~[[File:pi3b-img321.png]]</ol><ol start="7" style="list-style-type: decimal; "><li>Then enter the username and password of the Linux system in the corresponding position in the figure below, and then click '''~~import wiringpi~~OK'''to start logging in</li>

~~>>> '''from wiringpi import GPIO'''~~<div class="figure">

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

~~&gt~~</div></ol><ol start="8" style="list-style-type: decimal;~~>> '''wiringpi~~"><li>Then click OK in the next interface</li><li>Finally, you can see the desktop of the development board Linux system[[File:pi3b-img323.~~wiringPiSetup()'''~~png]]</li></ol>

0

~~>>> '''wiringpi.pinMode(2, GPIO.OUTPUT)'''~~=== Use VNC remote login ===

~~<ol start~~{| class="4wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~Then set~~ '''Before operation, please ensure that the Windwos computer and the development board are in the ~~GPIO port output low level. After setting~~same local area network, and you can ~~use the value of~~ log in to the ~~voltage~~ Ubuntu or Debian system of the ~~pins with a multimeter~~development board normally. ~~If it is 0V, it means that the low -power flat is set.</li></ol>~~'''

~~>>>~~ '''~~wiringpi~~Ubuntu 20.~~digitalWrite(2~~04 tests many problems with VNC, ~~GPIO~~please do not use this method.~~LOW)~~'''</big>|}

# First run the '''set_vnc.sh''' script settings, and '''<~~ol start="5"~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<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>~~remember to add Sudo permissions</olspan>'''

~~>>&gt~~::{| class="wikitable" style="width:800px; " |-| orangepi@orangepi:~$ '''~~wiringpi.digitalWrite(2, GPIO~~sudo set_vnc.~~HIGH)~~sh'''

~~<ol start="4" style="list-style-type: decimal;"><li>Wiringop-Python Sets GPIO high and low levels in the Python code. For reference~~ You will require a password to ~~the '''blink.py''' test program in Examples, the voltage of the '''blink~~access your desktops.~~py''' test program will set up the voltage of all GPIO ports in the development board 40 PIN</li></ol>~~

~~root@orangepi:~/wiringOP-Python# '''cd examples'''~~

~~root@orangepi~~Password:~~~/wiringOP-Python/examples#~~        '''~~ls blink.py~~#Set the VNC password here, 8 -bit characters'''

Verify:        '''~~blink.py~~#Set the VNC password here, 8 -bit characters'''

~~root@orangepi:~/wiringOP~~Would you like to enter a view-~~Python~~only password (y/~~examples~~n)? '''n'''

~~<~~xauth: file /~~span>=== 40pin SPI test ===~~root/.Xauthority does not exist

~~# From the schematic diagram of the 40pin interface, the SPI available for Orange Pi 3B is spi3~~

~~[[File~~New 'X' desktop is orangepi3b:~~pi3b-img264.png|577x193px]]~~1

~~'''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~~ Creating default startup script /~~boot~~root/~~orangepiEnv~~.~~txt, and then restart the Linux system to open the spi4.'''~~vnc/xstartup

~~orangepi@orangepi:~$ '''sudo vim~~ Starting applications specified in /~~boot~~root/~~orangepiEnv~~.~~txt'''~~vnc/xstartup

~~'''overlays=spi3-m0-cs0-spidev'''~~Log file is /root/.vnc/orangepi3b:1.log

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

~~<li>First check whether there is a '''spidev3.0''' device node in the Linux system. If it exists, it means that the SPI3 has been set and can be used directly</li></ol>~~

~~orangepi@orangepi:~$ '''ls /dev/spidev3.0'''~~Killing Xtightvnc process ID 3047

~~/dev/spidev3.0~~

~~<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'~~New 'X'desktop is orangepi3b: ~~Specify the port number of SPI</li></ol></li>~~<li>Do not pick up the two pins of the SPI3 MOSI and MISO in short, and run the output result of the spidev_test.py as shown below. You can see that the data of TX and RX are inconsistent</li></ol>1

~~root@orangepi:~/wiringOP-Python# '''cd examples'''~~

Starting applications specified in /root~~@orangepi:~~~/~~wiringOP-Python~~.vnc/~~examples# '''python3 spidev_test.py \'''~~xstartup

~~'''--channel 3 --port 0'''~~Log file is /root/.vnc/orangepi3b:1.log|}

~~spi mode~~<ol start="2" style="list-style-type: ~~0x0~~decimal;"><li>The steps of using MobaxTerm software to connect the development board Linux system desktop are shown below: <ol style="list-style-type: lower-alpha;"><li>First click Session, then select VNC, then fill in the IP address and port of the development board, and finally click OK to confirm</li>

~~max speed: 500000 Hz (500 KHz)~~<div class="figure">

~~Opening device /dev/spidev3~~[[File:pi3b-img324.0png]]

~~TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…|~~</div></ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then enter the password of the previously set VNC</li>

~~RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |~~[[File:pi3b-img325.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The interface after the login is shown as shown in the figure below, and then the desktop of the Linux system can be remotely operated[[File:pi3b-img326.~~...........….|~~png]]</li></ol></li></ol>

<~~ol start~~span id="~~5" style="list~~some-programming-language-tests-supported-by-~~style~~linux-~~type: decimal;~~system"><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></olspan>

~~root@orangepi:~/wiringOP-Python# '''cd examples'''~~== Some programming language tests supported by Linux system ==

~~root@orangepi:~/wiringOP~~</~~examples# '''python3 spidev_test.py \'''~~span>=== 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>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc --~~channel 3 --port 0~~version'''

~~spi mode: 0x0~~gcc (Debian 10.2.1-6) 10.2.1 20210110

~~max speed: 500000 Hz~~ Copyright (~~500 KHz~~C)2020 Free Software Foundation, Inc.

~~Opening device /dev/spidev3~~This is free software; see the source for copying conditions.0There is NO

TX warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.| ~~FF FF FF FF FF FF~~ }</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Write C language of '''~~40 00 00 00 00 95~~Hello_world.c''' ~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D~~ program</li>{| class="wikitable" style="width:800px;" |-|~~......~~orangepi@orangepi:~$ '''vim hello_world.~~......…|~~c'''

~~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 |......@.......…|~~

<~~span id="pin-i2c-test-1"~~p>#include <stdio.h></~~span~~p>~~=== 40pin I2C test ===~~

~~<ol start="5" style="list-style-type: decimal;"><li>As can be seen from the table below, the I2C available for Orange Pi 3B is I2C2, I2C3, and I2C4 a total of three groups of I2C bus</li></ol>~~int main(void)

~~[[File:pi3b-img266.png|576x160px]]~~{

~~'''It can be seen from the above table that I2C4_M0 and SPI3_M0 are pins. The two cannot be opened at the same time. I2C3_M0 and UART3_M0 are also reused. The two cannot be opened at the same time'''~~:printf("Hello World!\n");

~~'''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.''':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=i2c2-m1 i2c3-m0 i2c4-m0~~./hello_world'''

Hello World!|}</ol></li></ol><ol start="62" style="list-style-type: decimal;"><li>~~After starting the Linux system, first confirm the I2C device node under~~Debian BullSeye Default with Python3</~~dev.~~p><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'''

~~orangepi@orangepi:~#~~ '''ls /dev/i2c-*Python 3.9.2'''(default, Feb 28 2021, 17:03:44)

~~/dev/i2c-0 '''/dev/i2c-~~[GCC 10.2~~''' '''/dev/i2c-3''' '''/dev/i2c-4''' /dev/i2c-6~~.1 20210110] on linux

~~<ol start="7" style="list-style-type: decimal~~Type "">~~<li>Then connect a I2C device on the I2C pin of the 40PIN connector. Here is an example of the DS1307 RTC module~~help", "copyright", "credits" or "license" for more information.~~</li></ol>~~

>>>|}</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;"~~| i2c2-m1~~><li>The results of running '''hello_world.py''' are shown below</li>{| ~~style~~class="~~text-align: left;~~wikitable"~~| i2c3-m0~~| style="~~text-align~~width: ~~left~~800px;"~~| i2c4-m0~~

|-

| ~~Sda Pin| style="text-align~~orangepi@orangepi: ~~left;"| Corresponding to No~~~$ '''python3 hello_world. ~~3 pin~~py''' Hello World!| ~~style~~}</ol></li></ol><ol start="~~text-align: left;~~3"~~| Corresponding to No. 27 pin~~| style="~~text~~list-style-~~align~~type: ~~left~~decimal;"~~| Corresponding to No. 19 pin~~>|-<li>Debian Bullseye's compilation tool and operating environment that is not installed in Java by default~~| Sck Pin~~| <ol style="~~text~~list-~~align~~style-type: ~~left~~lower-alpha;"~~| Corresponding~~ ><li>You can use the following command to Noinstall OpenJDK. ~~5 pin~~The latest version in Debian Bullseye is openjdk-17</li>{| ~~style~~class="~~text-align: left;~~wikitable"~~| Corresponding to No. 28 pin~~| style="~~text-align~~width: ~~left~~800px;"~~| Corresponding to No. 23 pin~~

|-

| ~~Vcc Pin~~orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''| }</ol><ol start="2" style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"~~| Corresponding to No. 1 pin~~><li>After installation, you can check the version of Java</li>{| ~~style~~class="~~text-align: left;~~wikitable"~~| Corresponding to No. 1 pin~~| style="~~text-align~~width: ~~left~~800px;"~~| Corresponding to No. 1 pin~~

|-

|}

</ol>

<li>Edit the '''hello_world.java''' of the Jave version</li>

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

|-

|

orangepi@orangepi:~$ '''vim hello_world.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;"

|-

|~~| style="text-align~~orangepi@orangepi: ~~left;"~~~$ '''vim hello_world.py''' print('Hello World!')| ~~uart3~~}</ol>~~| style~~<ol start="~~text-align: left;~~3"~~| uart7~~| style="~~text-align: left;"| uart9~~|list-~~| Tx Pin~~| style~~="text~~-~~align~~type: ~~left~~lower-alpha;"~~| Corresponding to the 28 pin~~><li>The results of running '''hello_world.py''' are 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-align~~orangepi@orangepi: ~~left;"| Corresponding to the 27 pin| style="text-align: left;"| Corresponding to the 15 pin| style="text-align: left;"| Corresponding to the 7 pin~~|}~$ '''python3 hello_world.py'''

Hello World!|}</ol></li></ol><ol start="43" style="list-style-type: decimal;"><li>~~Use the '~~Ubuntu Focal'~~'serialTest.py''' program in Examples to test~~ s compilation tool and operating environment without the ~~loop function~~ installation of ~~the serial port. If you can see the printing below, it means that the serial communication is normal~~Java default

<li>~~Test UART3~~You can use the following command to install '''openjdk-17'''</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''|}</ol></ol start="2" style="list-style-type: lower-alpha;"><li>After installation, you can check the version of Java</olli>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''java --version'''

~~root@orangepi:~/wiringOP-Python/examples# '''python3 serialTest~~openjdk 17.0.py 2 2022-01-~~device \'''~~18

~~'''"/dev/ttyS3"'''~~OpenJDK Runtime Environment (build 17.0.2+8-Ubuntu-120.04)

~~Out:~~ OpenJDK 64-Bit Server VM (build 17.0.2+8-Ubuntu-120.04, mixed mode, sharing)|}</ol><ol start="3" style="list-style-type: lower-~~&gt~~alpha; 0"><li>Edit the '''hello_world.java''' of Jave version</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''

~~Out: 1: -> 1~~public class hello_world

~~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-Nelken/BalenaEtcher-arm/releases/download/v1.7.9/balenaEtcher-1.7.9+5945ab1f-arm64.AppImage~~ ~~<div~~ :{| class="~~figure~~wikitable" style="width:800px;">|-| orangepi@orangepi:~$ '''install_qt.sh'''|}

~~[[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-~~----------------------------------------~~ ~~| The WebPanel URL will be http://SERVER_IP:8888 when installed~~img336.png]] ~~+----------------------------------------------------------------------~~ ~~Do you want to install Bt-Panel to the /www directory now?(y~~</~~n): '''y'''~~ <ol ~~start="5" style="list-style-type: decimal;"~~><li>Then you have to wait patiently. When you see the printing information below the terminal output, it means that the pagoda has been installed. The entire installation process takes about 34 minutes. There may be some differences according to the difference in network speed</li></ol> ~~[[File:pi3b-img278.png|576x233px]]~~ <ol start="67" style="list-style-type: decimal;"><li>At this time, enter the '''panel address''' displayed above in the browser to open the login interface of the pagoda Linux panel, and then enter the '''username''' and '''password''' displayed in the corresponding position to log in to the Bt-Panel ~~[[File:pi3b-img279.png|575x281px]]</li><li>After successfully logging in to the pagoda, the following welcome interface will pop up. First, please take the intermediate user notice to read to the bottom, and then you~~ You can ~~choose "I have agreed and read" User Agreement ", and~~ then ~~click" Enter the panel " You can enter the Bt-Panel~~open a sample code</li>~~</ol>~~ ~~[[File:pi3b-img280.png|575x317px]]~~

[[File:pi3b-img337.png]]

</ol>

<li>~~After entering~~ Clicking on the ~~Bt-Panel, you~~ example code will ~~first prompt that you need to bind~~ automatically open the ~~account of the Bt-Panel official website. If you do n’t have an account~~corresponding instruction document, you can ~~go to~~ carefully read the ~~pagoda's official website ('''https://www.bt.cn''') to register one.~~instructions</li>~~</ol>~~ ~~[[File:pi3b-img281.png|576x300px]]~~

[[File:pi3b-img338.png]]

</ol>

<li>The final display interface is shown in the figure below. You can intuitively see some status information of the development board Linux system, such as load state, CPU usage, memory usage and storage space usageThen click '''Configure Project'''</li>~~</ol>~~ ~~[[File:pi3b-img282.png|575x306px]]~~

[[File:pi3b-img339.png]]

</ol>

<li>~~More functions of~~ Then click the ~~Bt-Panel can refer~~ green triangle in the lower left corner to compile and run the ~~following information to explore by yourself~~sample code</li~~></ol~~>

~~Manual:~~ [~~http~~[File:pi3b-img340.png]]</~~/docs.bt.cn '''http~~ol><ol start="11" style="list-style-type:decimal;"><li>After waiting for a period of time, the interface shown in the following figure will pop up, which indicates that QT can compile and run normally</~~/docs.bt.cn''']~~li>

~~Forum address:~~ [~~https~~[File:pi3b-img341.png]]</ol><ol start="12" style="list-style-type: decimal;"><li>Reference documents</~~www.bt.cn/bbs~~ li>{| class="wikitable" style="width:800px;" |-| '''https://~~www~~wiki.btqt.cnio/~~bbs~~Install_Qt_5_on_Ubuntu''']

~~GitHub Link:~~ '''https://~~github~~download.qt.~~com~~io/~~aaPanel~~archive/~~BaoTa~~qtcreator'''

'''https://download.qt.io/archive/qt'''|}</ol>~~== Set the Chinese environment and install Chinese input method ==~~

~~'''Note that before installing the Chinese input method, please make sure that the Linux system used in the development board is the desktop version system.'''~~== ROS Installation Method ==

=== ~~Debian system installation method~~ How to install ROS 1 Noetic on Ubuntu 20.04 ===

~~<ol style="list-style-type: decimal;"><li>First set the default '''locale'''~~ # The current active version of ROS 1 is as ~~Chinese<ol style="list-style-type: lower-alpha;"><li>Enter~~ follows, the ~~command below to start configured~~ recommended version is '''~~locale~~Noetic Ninjemys'''~~</li></ol></li></ol>~~

~~orangepi@orangepi~~:~~~$ '''sudo dpkg~~:[[File:pi3b-~~reconfigure locales'''~~img342.png|800px]]

~~<ol start="2" style="list-style-type~~: ~~lower~~:[[File:pi3b-~~alpha;"><li>Then select '''zh_CN~~img343.UTF-8 UTF-8''' in the pop-up interface (to move up and down through the upper and lower direction buttons on the keyboard, select it through the space key, and finally move the cursor to '''<OK>''' through the TAB key, then press the ENTER key )</li></ol>png|800px]]

::{| class="wikitable" style="width:800px;" |-| [~~[File~~http://docs.ros.org/ '''http:~~pi3b-img283~~//docs.ros.~~png|575x296px]~~org''']

~~<ol start="3" style="list-style-type: lower-alpha;"><li>Then set the default~~ '''~~locale''' as '''zh_CN~~https://wiki.ros.~~UTF-8~~org/Distributions'''~~</li></ol>~~|}

<ol start="2" style="list-style-type: decimal;"><li>The official installation document link of ROS 1 '''Noetic Ninjemys''' is as follows:</li>{| class="wikitable" style="width:800px;" |-| [~~[File~~http://wiki.ros.org/noetic/Installation/Ubuntu '''http://wiki.ros.org/noetic/Installation/Ubuntu''']|}</ol><ol start="3" style="list-style-type: decimal;"><li>In the official installation document of ROS '''Noetic Ninjemys''', Ubuntu recommends using Ubuntu20.04, so please make sure that the system used by the development board is '''Ubuntu20.04 desktop system'''</li>{| class="wikitable" style="width:~~pi3b~~800px;" |-~~img284~~| http://wiki.~~png~~ros.org/noetic/Installation|~~575x160px]]~~}

[[File:pi3b-img344.png]]</ol><ol start="4" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~After exiting the interface,~~ Then use the script below to install ros1</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi3b:~$ '''~~locale~~install_ros.sh ros1''' ~~settings will be started. The output displayed by~~ |}</ol><ol start="5" style="list-style-type: decimal;"><li>Before using the ROS tool, you first need to initialize rosdep, and then you can quickly install some system dependencies and some core components in ROS when compiling the ~~command line is shown below~~source code</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <~~/ol~~big>'''Note that running the following command needs to ensure that the development board can access github normally, otherwise an error will be reported due to network problems.'''

~~orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''~~

~~Generating locales (~~'''The install_ros.sh script will try to modify /etc/hosts and automatically run the following commands. However, this ~~might take a while)~~method cannot guarantee normal access to github every time.If the following error is displayed after installing ros1 in install_ros.sh, please find other ways to allow the Linux system of the development board to access github normally, and then manually run the following Order.'''

~~en_US.UTF-8... done~~

~~zh_CN~~'''https://raw.~~UTF~~githubusercontent.com/ros/rosdistro/master/rosdep/osx-~~8..~~homebrew. ~~done~~yaml'''

~~Generation complete~~'''Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml'''

~~<ol start="2" style="list-style-type: decimal;"><li>Then open~~ '''~~Input Method~~ERROR: error loading sources list:'''~~</li></ol>~~

~~[[File~~:~~pi3b~~'''The read operation timed out'''</big>|}{| class="wikitable" style="width:800px;" |-~~img285~~| orangepi@orangepi:~$ '''source /opt/ros/noetic/setup.~~png|575x361px]]~~bash'''

~~<ol start="3" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>Then select~~ ~$ '''OKsudo rosdep init'''~~</li></ol>~~

~~[[File:pi3b~~Wrote /etc/ros/rosdep/sources.list.d/20-~~img286~~default.~~png|295x212px]]~~list

~~<ol start="4" style="list-style-type~~Recommended: ~~decimal;"><li>Then select '''Yes'''</li></ol>~~please run

~~[[File:pi3b-img287.png|303x192px]]~~

~~<ol start="5" style="list-style-type~~: ~~decimal;"><li>Then select '''fcitx'''</li></ol>~~:rosdep update

~~[[File~~orangepi@orangepi:~~pi3b-img288.png|307x220px]]~~~$ '''rosdep update'''

~~<ol start="6" style="~~reading in sources list~~-style-type: decimal;"><li>Then select '''OK'''<~~data from /~~li><~~etc/~~ol>~~ros/rosdep/sources.list.d

~~[[File~~Hit https:~~pi3b~~//raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-~~img289~~homebrew.~~png|305x216px]]~~yaml

~~<ol start="7" style="list-style-type~~Hit https: ~~decimal;"><li>'''Then restart the Linux system to make the configuration effective'''<~~/~~p><~~/~~li><li>Then open '''Fcitx configuration'''<~~raw.githubusercontent.com/~~p><~~ros/~~li><~~rosdistro/~~ol>~~master/rosdep/base.yaml

~~[[File~~Hit https:~~pi3b-img290~~//raw.~~png|575x376px]]~~githubusercontent.com/ros/rosdistro/master/rosdep/python.yaml

~~<ol start="9" style="list-style-type~~Hit https: ~~decimal;"><li>Then click the + of the position shown in the figure below<~~/~~li><~~/~~ol>~~raw.githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml

~~[[File~~Hit https:~~pi3b-img291~~//raw.~~png|280x187px]]~~githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml

~~<ol start="10" style="list-style-type~~Query rosdistro index https: ~~decimal;"><li>Then search '''Google Pinyin''' and click '''OK'''<~~/~~li><~~/~~ol>~~raw.githubusercontent.com/ros/rosdistro/master/index-v4.yaml

~~<div class="figure">~~Skip end-of-life distro "ardent"

~~[[File:pi3b~~Skip end-~~img292.png|291x196px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~of-~~10.jpg未标题-10]]~~life distro "bouncy"

~~</div><ol start="11" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "crystal"">~~<li>Then put '''Google Pinyin''' to the front</li></ol>~~

~~[[File:pi3b~~Skip end-~~img293.png|299x202px]]~~of-life distro "dashing"

~~[[File:pi3b~~Skip end-~~img294.png|300x202px]]~~of-life distro "eloquent"

~~<ol start="12" style="list-style-type: decimal~~Add distro "foxy"">~~<li>Then open the '''Geany''' editor to test the Chinese input method</li></ol>~~

~~[[File:pi3b-img295.png|349x212px]]~~Add distro "galactic"

~~<ol start="13" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "groovy"">~~<li>The Chinese input method test is shown below</li></ol>~~

~~[[File:pi3b-img296.png|575x325px]]~~Add distro "humble"

~~<ol start="14" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "hydro"">~~<li>You can switch the Chinese and English input method through the '''Ctrl+Space''' shortcut</li><li>If the entire system is required as Chinese, the variables in '''/etc/default/locale''' can be set to '''zh_CN.UTF-8'''</li></ol>~~

~~orangepi@orangepi:~$ '''sudo vim /etc/default/locale'''~~Skip end-of-life distro "indigo"

~~# File generated by update~~Skip end-~~locale~~of-life distro "jade"

~~LC_MESSAGES='''zh_CN.UTF~~Skip end-~~8'''~~of-life distro "kinetic"

~~LANG='''zh_CN.UTF~~Skip end-~~8'''~~of-life distro "lunar"

~~LANGUAGE='''zh_CN.UTF-8'''~~Add distro "melodic"

~~<ol start="16" style="list-style-type: decimal~~Add distro "noetic"">~~<li>Then '''restart the system''' to see the system displayed as Chinese</li></ol>~~

~~[[File:pi3b-img297.png|576x356px]]~~Add distro "rolling"

updated cache in /home/orangepi/.ros/rosdep/sources.cache|}<~~span id~~/ol><ol start="6" style="~~the~~list-~~installation~~style-~~method-of-ubuntu-20~~type: decimal;"><li>Then open a command line terminal window on the desktop, and then use the test_ros.~~04-system"~~sh script to start a small turtle routine to test whether ROS can be used normally</~~span~~li>{| class="wikitable" style=~~= The installation method of Ubuntu 20~~"width:800px;" |-| orangepi@orangepi:~$ '''test_ros.sh'''|}<li>After running the '''test_ros.~~04 system ===~~sh''' script, a little turtle as shown in the figure below will pop up</li>

~~# First open '''Language Support'''~~<div class="figure">

[[File:pi3b-~~img298~~img345.png~~|575x351px~~]]

</div></ol><ol start="28" style="list-style-type: decimal;"><li>Then ~~find '''Chinese (China)''' option~~please keep the terminal window just opened at the top</li~~></ol~~>

~~[[File:pi3b-img299.png|318x311px]]~~<div class="figure">

~~<ol start="3" style="list-style~~[[File:pi3b-~~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~~img346. ~~The display is shown below: </li></ol>~~png]]

~~[[File~~</div></ol><ol start="9" style="list-style-type:~~pi3b-img300.png|324x320px]]~~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>

~~'''Note that this step is not easy~~ [[File:pi3b-img347.png]]</ol>

~~<ol start~~=~~"4" style~~=~~"list-style-type: decimal;"><li>Then select the '''Apply System-Wide'''~~ = How to ~~apply the Chinese settings to the entire system</li></ol>~~install ROS 2 Galactic on Ubuntu 20.04 ===

~~[[File:pi3b-img301.png|321x316px]]~~# The current active version of ROS 2 is as follows, the recommended version is '''Galactic Geochelone'''

~~<ol start="5" style="list~~::[[File:pi3b-~~style-type: decimal;"><li>Then set the '''Keyboard input method system''' to '''fcitx'''</li></ol>~~img348.png]]

::[[File:pi3b-~~img302~~img349.png~~|327x320px~~]]

~~<ol start~~::{| class="6wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>~~|-| [http://docs.ros.org/ '''~~hen restart the Linux system to make the configuration effective'''<~~http:/~~p><~~/~~li><li>After re -entering the system, please do '''not ask me again~~docs.ros.org''' ~~at the interface below, and then determine whether the standard folder should be updated as Chinese based on your preference.</li></ol>~~]

~~[[File~~'''http:~~pi3b-img303~~//docs.~~png~~ros.org/en/galactic/Releases.html'''|~~303x247px]]~~}

<ol start="82" style="list-style-type: decimal;"><li>~~Then you can see that~~ The link to the ~~desktop~~ official ROS 2 '''Galactic Geochelone''' installation documentation is ~~displayed~~ as ~~Chinese~~follows:</li><{| class="wikitable" style="width:800px;" |-| '''docs.ros.org/en/galactic/~~ol>~~Installation.html'''

~~[[File~~'''http://docs.ros.org/en/galactic/Installation/Ubuntu-Install-Debians.html'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>It is recommended to use Ubuntu20.04 in the official installation document of ROS 2 '''Galactic Geochelone''', so please ensure that the system used by the development board is '''Ubuntu20.04 desktop version'''. There are several ways to install ROS 2. The following shows how to install ROS 2 '''Galactic Geochelone''' using '''Debian packages'''</li><li>Use the '''install_ros.sh''' script to install ros2</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_ros.sh ros2'''|}</ol><ol start="5" style="list-style-type:~~pi3b~~decimal;"><li>The '''install_ros.sh''' script will automatically run the '''ros2 -~~img304~~h''' command after installing ros2.~~png~~If you can see the following print, it means that the ros2 installation is complete</li>{|~~575x383px]~~class="wikitable" style="width:800px;" |-| usage: ros2 [-h]Call `ros2 <command> -h` for more detailed usage. ...

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

~~<li>Then we can open the '''Geany''' to test Chinese input method , and the way to open is shown in the figure below</li></ol>~~

~~[[File:pi3b~~ros2 is an extensible command-~~img305~~line tool for ROS 2.~~png|576x292px]]~~

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

~~<li>After opening '''Geany''', the default is an English input method. We can switch into Chinese input method through the '''Ctrl+Space''' shortcut keys, and then we can enter Chinese</li></ol>~~

~~[[File~~optional arguments:~~pi3b-img306.png|575x308px]]~~

~~=== The installation method of ubuntu 22.04 system ===~~help show this help message and exit

~~# First open '''Language Support'''~~

~~[[File~~Commands:~~pi3b-img298.png|575x351px]]~~

~~<ol start="2" style="list~~:action Various action related sub-~~style-type: decimal;"><li>Then find '''Chinese (China)''' option</li></ol>~~commands

~~[[File~~:~~pi3b~~bag Various rosbag related sub-~~img307.png|335x326px]]~~commands

~~<ol start="3" style="list-style~~:component Various component related sub-~~type: decimal;"><li>Then use the left mouse button to select '''Chinese (China)''' and hold it down, and then drag it up to the beginning. The display after dragging is shown in the figure below: </li></ol>~~commands

~~[[File~~:~~pi3b~~daemon Various daemon related sub-~~img308.png|337x331px]]~~commands

~~'''Note that this step is not easy to drag, please try more patiently.'''~~:doctor Check ROS setup and other potential issues

~~<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>~~interface Show information about ROS interfaces

~~[[File~~:~~pi3b-img309.png|336x330px]]~~launch Run a launch file

~~<ol start="5" style="list-style-type~~: ~~decimal;"><li>'''Then restart the Linux system to make the configuration effective'''</li><li>After re~~ lifecycle Various lifecycle related sub-~~entering the system, please '''do not ask me again''' at the interface below, and then determine whether the standard folder should be updated as Chinese based on your preference</li></ol>~~commands

~~[[File~~:~~pi3b~~multicast Various multicast related sub-~~img303.png|303x247px]]~~commands

~~<ol start="7" style="list~~:node Various node related sub-~~style-type: decimal;"><li>Then you can see that the desktop is displayed as Chinese</li></ol>~~commands

~~[[File~~:~~pi3b~~param Various param related sub-~~img304.png|575x383px]]~~commands

~~<ol start="8" style="list~~:pkg Various package related sub-~~style-type: decimal;"><li>Then open the Fcitx5 configuration program</li></ol>~~commands

~~[[File~~:~~pi3b-img310.png|575x349px]]~~run Run a package specific executable

~~<ol start="9" style="list~~:security Various security related sub-~~style-type: decimal;"><li>Then choose to use Pinyin input method</li></ol>~~commands

~~<div class="figure">~~:service Various service related sub-commands

~~[[File~~:~~pi3b~~topic Various topic related sub-~~img311.png|338x267px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-11.jpg未标题-11]]~~commands

~~</div><ol start="10" style="list-style-type~~: ~~decimal;"><li>The interface after the selection is shown below, then click OK</li></ol>~~wtf Use `wtf` as alias to `doctor`

~~[[File:pi3b-img312.png|366x290px]]~~

:Call `ros2 <command> -h` for more detailed usage.|}</ol><ol start="116" style="list-style-type: decimal;"><li>Then we you can ~~open~~ use the '''~~Geany~~test_ros.sh''' script to test ~~Chinese input method, and the way to open~~ whether ROS 2 is ~~shown in~~ installed successfully. If you can see the ~~figure below~~following print, it means that ROS 2 can run normally</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi3b:~$ '''test_ros.sh'''

[INFO] [~~File:pi3b-img305~~1671174101.~~png|576x292px~~200091527][talker]: Publishing: 'Hello World: 1'

~~<ol start="12" style="list-style-type~~[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: ~~decimal;">~~<li>After opening '''Geany''', it is still an English input method by default. We can switch into Chinese input methods through the '''Ctrl+Space''' shortcut keys, and then we can enter Chinese</li></ol>1]

[INFO] [~~File:pi3b-img313~~1671174102.~~png|576x408px~~199572327][talker]: Publishing: 'Hello World: 2'

~~== How to remotely log in to the Linux system desktop method ==~~[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]

~~'''Ubuntu Gnome Wayland image does not support Nomachine and VNCs introduced here to remotely log in to the desktop~~[INFO] [1671174103.199580322] [talker]: Publishing: ''Hello World: 3'

[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]|}</ol><~~span id~~ol start="~~use-nomachine~~7" style="list-~~remote~~style-~~login~~type: decimal;"><li>Run the following command to open rviz2</~~span~~li>{| class="wikitable" style=~~= Use nomachine remote login ===~~"width:800px;" |-| orangepi@orangepi:~$ '''source /opt/ros/galactic/setup.bash'''

orangepi@orangepi:~$ '''Make sure the Ubuntu or Debian system installed on the development board is a desktop version. In addition, nomachine also provides detailed documents. It is strongly recommended to read this document to be familiar with the use of nomachine. The document links are shown below: ros2 run rviz2 rviz2'''|}

~~'''https://knowledgebase.nomachine.com/DT10R00166'''~~<div class="figure">

~~'''Nomachine supports Windows, Mac, Linux, iOS, and Android platforms, so we can remotely log in to control Orange PI development boards through Nomachine on multiple devices~~[[File:pi3b-img350. The following demonstrates the Linux system desktop of the Orange PI development board through Nomachine in Windows. For installation methods for other platforms, please refer to the official documentation of Nomachine.'''png]]

~~'''Before operation~~</div></ol><ol start="8" style="list-style-type: decimal;"><li>For the usage of ROS, please ~~ensure that the Windwos computer and the development board are in the same local area network, and can log in~~ refer to the ~~Ubuntu or Debian system that can log in to the development board normally~~documentation of ROS 2</li>{| class="wikitable" style="width:800px;" |-| '''http://docs.ros.org/en/galactic/Tutorials.html'''|}</ol>

~~<ol style~~=~~"list-style-type: decimal;"><li>First download the nomachine software Linux '''ARM64''' DEB version of the installation package, and then~~ == How to 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~~ ROS 2 Humble on Ubuntu ~~or Debian, so you need to download '''NoMachine for ARM ARMv8 DEB''' installation package here~~22. ~~The download link is shown below: </li></ol></li></ol>~~04 ===

# Use the '''~~Note that this download link may change, please recognize the DEB package of the ARMV8/ARM64 version~~install_ros.sh'''script to install ros2

~~[https~~:~~//www.nomachine.com/download/download&id~~:{| class=~~112&s~~"wikitable" style=~~ARM~~ "width:800px;" |-| orangepi@orangepi:~$ '''~~https://downloads~~install_ros.~~nomachine.com/download/?id=118&distro=ARM~~sh ros2''']|}

~~[[File~~<ol start="2" style="list-style-type:~~pi3b~~decimal;"><li>The '''install_ros.sh''' script will automatically run the '''ros2 -~~img314~~h''' command after installing ros2.~~png|575x227px]]~~If you can see the following print, it means that the ros2 installation is complete</li>

~~<ol start~~{| class="2wikitable" style="~~list~~width:800px;" |-~~style-type~~| usage: ~~lower~~ros2 [-~~alpha~~h] Call `ros2 <">~~<li>In addition, you can also download the installation package to '''NoMachine''' in the '''official tools'''~~command> -h` for more detailed usage. ...~~</li></ol>~~

~~[[File:pi3b-img315.png|66x102px]]~~

~~<blockquote>First enter the '''remote login software~~ros2 is an extensible command-~~Nomachine''' folder</blockquote>[[File:pi3b-img316~~line tool for ROS 2.~~png|271x43px]]~~

~~<blockquote>Then download the ARM64 version of the DEB installation package~~

~~</blockquote>~~

~~[[File:pi3b-img317.png|180x109px]]~~

~~<ol start="3" style="list-style-type~~optional arguments: ~~lower-alpha;"><li>Then upload the downloaded '''nomachine_x.x.x_x_arm64.deb''' to the Linux system of the development board.</li><li>Then use the following command to install '''NoMachine''' in the Linux system of the development board</li></ol>~~

~~orangepi@orangepi~~:~~~$ '''sudo dpkg~~ -~~i nomachine_x.x.x_x_arm64_arm64.deb'''~~h, --help show this help message and exit

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

~~<li>Then download the nomachine software Windows version of the installation package, the download address is shown below</li></ol>~~

~~'''Note that this download link may change.'''~~Commands:

~~'''https~~:~~//downloads.nomachine.com/download/?id=9'''~~action Various action related sub-commands

~~[[File~~:~~pi3b~~bag Various rosbag related sub-~~img318.png|575x163px]]~~commands

~~<ol start="3" style="list~~:component Various component related sub-~~style-type: decimal;"><li>Then install nomachine in Windows. '''Please restart the computer after installation'''</li><li>Then open '''NoMachine''' in Window</li></ol>~~commands

~~[[File~~:~~pi3b~~daemon Various daemon related sub-~~img319.png|76x66px]]~~commands

~~<ol start="5" style="list-style-type~~: ~~decimal;"><li>After Nomachine starts, it will automatically scan~~ doctor Check ROS setup and 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>potential issues

~~[[File~~:~~pi3b-img320.png|321x92px]]~~interface Show information about ROS interfaces

~~<ol start="6" style="list-style-type~~: ~~decimal;"><li>Then click '''OK'''</li></ol>~~launch Run a launch file

~~[[File~~:~~pi3b~~lifecycle Various lifecycle related sub-~~img321.png|402x275px]]~~commands

~~<ol start="7" style="list~~:multicast Various multicast related sub-~~style-type: decimal;"><li>Then enter the username and password of the Linux system in the corresponding position in the figure below, and then click '''OK''' to start logging in</li></ol>~~commands

~~<div class="figure">~~:node Various node related sub-commands

~~[[File~~:~~pi3b~~param Various param related sub-~~img322.png|303x204px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-12.jpg未标题-12]]~~commands

~~</div><ol start="8" style="list-style-type: decimal;"><li>Then click OK in the next interface</li><li>Finally, you can see the desktop of the development board Linux system[[File~~:~~pi3b~~pkg Various package related sub-~~img323.png|411x246px]]</li></ol>~~commands

~~=== Use VNC remote login ===~~:run Run a package specific executable

'''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.''':security Various security related sub-commands

~~'''Ubuntu 20.04 tests many problems with VNC, please do not use this method.'''~~:service Various service related sub-commands

~~# First run the '''set_vnc.sh''' script settings, and '''remember to add Sudo permissions'''~~:topic Various topic related sub-commands

~~orangepi@orangepi~~:~~~$ '''sudo set_vnc.sh'''~~wtf Use `wtf` as alias to `doctor`

~~You will require a password to access your desktops.~~

~~Password~~: Call `ros2 <command> -h` for more detailed usage.|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then you can use the '''~~#Set the VNC password here, 8 -bit characters~~test_ros.sh'''script to test whether ROS 2 is installed successfully. If you can see the following print, it means that ROS 2 can run normally</li>

~~Verify~~{| class="wikitable" style="width: 800px;" |-| orangepi@orangepi3b:~$ '''~~#Set the VNC password here, 8 -bit characters~~test_ros.sh'''

~~Would you like to enter a view-only password (y/n)? '''n'~~[INFO] [1671174101.200091527] [talker]: Publishing: 'Hello World: 1'

~~xauth~~[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: ~~file /root/.Xauthority does not exist~~1]

~~New~~ [INFO] [1671174102.199572327] [talker]: Publishing: 'XHello World: 2' ~~desktop is orangepi3b:1~~

~~Creating default startup script /root/~~[INFO] [1671174102.~~vnc/xstartup~~204196299] [listener]: I heard: [Hello World: 2]

~~Starting applications specified in /root/~~[INFO] [1671174103.~~vnc/xstartup~~199580322] [talker]: Publishing: 'Hello World: 3'

~~Log file is~~ [INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]|}</ol><ol start="4" style="list-style-type: decimal;"><li>Run the following command to open rviz2</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''source /opt/~~root~~ros/~~.vnc~~humble/~~orangepi3b:1~~setup.~~log~~bash'''

~~Killing Xtightvnc process ID 3047~~orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''|}

~~New 'X' desktop is orangepi3b:1~~<div class="figure">

~~Starting applications specified in /root/~~[[File:pi3b-img351.~~vnc/xstartup~~png]]

~~Log file is~~ </~~root~~div></ol><ol start="5" style="list-style-type: decimal;"><li>Reference documents</li>{| class="wikitable" style="width:800px;" |-| '''http://docs.~~vnc~~ros.org/~~orangepi3b:1~~en/humble/index.~~log~~html'''

~~<ol start="2" style="list~~[http://docs.ros.org/en/galactic/Tutorials.html '''http://docs.ros.org/en/humble/Installation/Ubuntu-~~style~~Install-~~type: decimal;">~~Debians.html''']|}~~<li>The steps of using MobaxTerm software to connect the development board Linux system desktop are shown below:~~ </pol><~~ol style~~span id="~~list~~how-~~style~~to-~~type: lower~~install-kernel-header-~~alpha;~~files">~~<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~~span>

~~<div class~~=~~"figure">~~= How to install kernel header files ==

~~[[File:pi3b-img324.png|490x349px|图片1208]]~~# The Linux image released by OPi comes with the deb package of the kernel header file by default, and the storage location is '''/opt/'''

~~</div><ol start~~::{| class="2wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Then enter the password of the previously set VNC<~~|-| orangepi@orangepi:~$ '''ls /~~li><~~opt/~~ol>~~linux-headers*'''

~~[[File:pi3b~~/opt/linux-~~img325~~headers-legacy-rockchip-rk356x_x.x.x_arm64.~~png~~deb|~~274x131px]]~~}

<ol start="32" style="list-style-type: ~~lower-alpha~~decimal;"><li>Use the following command to install the deb package of the kernel header file</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <pbig>'''The ~~interface after~~ name of the ~~login is shown as shown in~~ kernel header file deb package needs to be replaced with the ~~figure below~~actual name, ~~and then the desktop of the Linux system can be remotely operated~~please do not copy it.'''</pbig>~~[[File~~|}{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~~pi3b~~~$ '''sudo dpkg -i /opt/linux-headers-legacy-rockchip-~~img326~~rk356x_1.x.x_arm64.~~png~~deb'''|~~405x293px]]~~}</pol><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'''</olli>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ls /usr/src'''

linux-headers-5.10.160-rockchip-rk356x|}</ol><~~span id~~ol start="4" style="~~some~~list-~~programming~~style-~~language~~type: decimal;"><li>Then you can write a hello kernel module to test the kernel header file<ol style="list-~~tests~~style-~~supported~~type: lower-~~by-linux-system~~alpha;"><li>First write the code of the hello kernel module, as follows:</~~span~~li>{| class="wikitable" style= ~~Some programming language tests supported by Linux system ==~~"width:800px;" |-| orangepi@orangepi:~$ '''vim hello.c'''

<~~span id="debian-bullseye-system"~~p>#include <linux/init.h></~~span~~p>~~=== 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<~~#include <linux/p>~~<ol style="list-style-type: lower-alpha~~module.h>">~~<li>The version of the gcc is shown below~~</~~li></ol></li></ol~~p>

~~orangepi@orangepi:~$ '''gcc --version'''~~

~~gcc~~ static int hello_init(~~Debian 10.2.1-6~~void) ~~10.2.1 20210110~~

~~This is free software~~:printk("Hello Orange Pi -- init\n"); ~~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~~return 0;">~~<li>Write C language of '''Hello_world.c''' program</li></ol>~~

~~orangepi@orangepi:~$ '''vim hello_world.c'''~~}

~~#include <stdio.h>~~static void hello_exit(void)

~~int main(void)~~{

{:printk("Hello Orange Pi -- exit\n");

~~printf("Hello World!\n");~~

:return 0;

}

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

~~<li>Then compile and run '''hello_world.c'''</li></ol>~~

~~orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''~~module_init(hello_init);

~~orangepi@orangepi:~$ '''./hello_world'''~~module_exit(hello_exit);

~~Hello World!~~

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

~~<li>Debian BullSeye Default with Python3~~

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

~~<li>The specific version of Python is shown below</li></ol>~~

~~</li></ol>~~

~~orangepi@orangepi:~$ '''python3'''~~

~~'''Python 3.9.2''' (default, Feb 28 2021, 17:03:44)~~

~~[GCC 10.2.1 20210110] on linux~~

~~Type "help", "copyright", "credits" or "license" for more information.~~

~~>>>~~

MODULE_LICENSE("GPL");

|}

</ol>

<li>Then write the Makefile for compiling the hello kernel module, as follows:</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~hello_world.py~~vim Makefile''' ~~program in Python language</li></ol>~~

~~orangepi@orangepi:~~~ifneq ($ ~~'''vim hello_world.py'''~~(KERNELRELEASE),)

~~print('Hello World!')~~obj-m:=hello.o

~~<ol start="3" style="list-style-type: lower-alpha;"><li>The results of running '''hello_world.py''' are shown below</li></ol>~~else

~~orangepi@orangepi~~KDIR :~=/lib/modules/$ ~~'''python3 hello_world.py'''~~(shell uname -r)/build

~~Hello World!~~PWD :=$(shell pwd)

~~<ol start="3" style="list-style-type~~all: ~~decimal;"><li>Debian Bullseye's compilation tool and operating environment that is not installed in Java by default<ol style="list-style-type: lower-alpha;"><li>You can use the following command to install OpenJDK. The latest version in Debian Bullseye is openjdk-17</li></ol></li></ol>~~

~~orangepi@orangepi~~:~make -C $ ~~'''sudo apt install -y openjdk-17-jdk'''~~(KDIR) M=$(PWD) modules

~~<ol start="2" style="list-style-type~~clean: ~~lower-alpha;"><li>After installation, you can check the version of Java</li></ol>~~

~~orangepi@orangepi~~:~~~$ '''java~~ rm -~~-version'''~~f *.ko *.o *.mod.o *.mod *.symvers *.cmd *.mod.c *.order

endif

|}

</ol>

<li>~~Edit~~ Then use the make command to compile the hello kernel module. The output of the compilation process is as follows:</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~hello_world~~If there is a problem with compiling the code you copied here, please go to the official tool to download the source code and upload it to the Linux system of the development board for testing.~~java~~''' ~~of the Jave version</li>~~</olbig>

[[File:pi3b-img352.png|center]]|}{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~vim hello_world.java~~make'''

~~public class hello_world~~make -C /lib/modules/5.10.160-rockchip-35xx/build M=/home/orangepi modules

{make[1]: Entering directory '/usr/src/linux-headers-5.10.160-rockchip-rk35xx'

~~public static void main(String~~:CC [M] ~~args)~~/home/orangepi/hello.o

{:MODPOST /home/orangepi/Module.symvers

~~System~~:CC [M] /home/orangepi/hello.~~out~~mod.~~println("Hello World!");~~o

}:LD [M] /home/orangepi/hello.ko

make[1]: Leaving directory '/usr/src/linux-headers-5.10.160-rockchip-rk35xx'|}</ol><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:~$ '''ls *.ko'''

hello.ko|}</ol><ol start="45" style="list-style-type: lower-alpha;"><li>~~Then compile and run~~ Use the '''insmod''' command to insert the '''~~hello_world~~hello.~~java~~ko'''kernel module into the kernel</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo insmod hello.ko'''|}</ol><ol start="6" style="list-style-type: lower-alpha;"><li>Then use the '''demsg''' command to view the output of the '''hello.ko''' kernel module. If you can see the output below, it means that the '''hello.ko''' kernel module is loaded correctly.</li>

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~javac hello_world.java~~dmesg | grep "Hello"'''

[ 2871.893988] '''Hello Orange Pi -- init'''|}</ol><ol start="7" style="list-style-type: lower-alpha;"><li>Use the '''rmmod''' command to uninstall the '''hello.ko''' kernel module</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~java hello_world~~sudo rmmod hello'''

orangepi@orangepi:~$ '''dmesg | grep "Hello ~~World!~~"'''

~~=== Ubuntu Focal system ===~~init

~~<ol style="list~~[ 3173.800892] '''Hello Orange Pi -~~style~~-~~type: decimal;"><li>Ubuntu Focal has the GCC compilation tool chain by default, which can compile the C language program directly in the Linux system of the development board.~~exit'''~~<ol style="list-style-type: lower-alpha;">~~|}~~<li>The version of the gcc is shown below</li>~~</ol>

</li></ol>

~~orangepi@orangepi:~$~~ == Use of the Raspberry PI'~~''gcc -~~s 5-~~version'''~~inch screen ==

~~gcc (Ubuntu 9.4.0~~=== Assembly method of Raspberry PI 5-inch screen ===

~~Copyright (C) 2019 Free Software Foundation, Inc.~~<ol style="list-style-type: decimal;"><li>First prepare the required accessories~~This is free software~~<ol style="list-style-type: lower-alpha; ~~see the source for copying conditions. There is NO~~"> ~~warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.~~<li>Raspberry PI 5-inch MIPI LCD display + touch screen</li>

[[File:pi3b-img353.png]]

</ol>

<li>~~'''hello_world.c''' program to write C language~~15pin MIPI cable</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''vim hello_world~~pi3b-img354.~~c'''~~png]]</ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>Then connect the 15pin MIPI cable to the Raspberry PI 5-inch screen in the way shown below (note the orientation of the insulation surface)</li>

~~#include <stdio~~[[File:pi3b-img355.~~h&gt~~png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Finally connect to the LCD interface of the Orange Pi 3B development board</li>

~~int main(void)~~[[File:pi3b-img356.png]]</ol>

{=== Open the Raspberry PI 5-inch screen configuration method ===

~~printf(&quot~~<ol style="list-style-type: decimal;~~Hello World!\n&quot~~"><li>The Linux image does not open the 5-inch screen of the Raspberry PI by default. If you need to use the 5-inch screen of the Raspberry PI, you need to open it manually.</li><li>The steps to open the mipi lcd configuration are as follows:<ol style="list-style-type: lower-alpha;)"><li>First run '''orangepi-config''', ordinary users remember to add '''sudo''' permission</li>{| class="wikitable" style="width:800px;" |-~~return 0;~~| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then select '''System'''</li>

[[File:pi3b-img357.png]]

</ol>

<li>Then ~~compile and run~~ select '''~~hello_world.c~~Hardware'''</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''gcc~~ pi3b-~~o hello_world hello_world~~img358.~~c'''~~png]]</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then use the arrow keys on the keyboard to locate the Rasp-7inch-touchscreen, and then use the space button to check</li>

~~orangepi@orangepi~~[[File:~$ pi3b-img359.png]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then select '''~~./hello_world~~<Save>'''to save</li>

~~Hello World!~~[[File:pi3b-img360.png]]</ol><ol start="6" style="list-style-type: lower-alpha;"><li>Then select '''<Back>'''</li>

~~<ol start="2" style="list~~[[File:pi3b-~~style-type: decimal;">~~img361.png]]~~<li>Ubuntu Focal defaults to install Python3~~</pol><ol start="7" style="list-style-type: lower-alpha;"><li>~~Python3 specific version is shown below~~Then select '''<Reboot>''' to restart the system for the configuration to take effect</li~~></ol></li></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''python3'''~~pi3b-img362.png]]

~~Python 3~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The above settings will eventually add the configuration of overlays=raspi-7inch-touchscreen to /boot/orangepiEnv.8txt.~~10 (default~~After setting, ~~Nov 14 2022~~you can check it first. If this configuration does not exist, ~~12:59:47)~~then there is a problem with the settings.'''

~~[GCC 9~~'''If you find it troublesome to use orangepi-config, you can also use the vim editor to open /boot/orangepiEnv.4txt, and then add the configuration of overlays=raspi-7inch-touchscreen is also possible.~~0] on linux~~'''</big>

~~Type "help", "copyright", "credits" or "license" for more information.~~

~~>>>~~orangepi@orangepi:~$ '''cat /boot/orangepiEnv.txt | grep "raspi"'''

'''overlays=raspi-7inch-touchscreen #Sample configuration'''|}</ol></li></ol><ol start="23" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~'''hello_world.py''' program in Python language~~After startup, you can see the lcd screen display as follows:</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''vim hello_world~~pi3b-img363.~~py'''~~png]]</ol>

~~print('Hello World!')~~=== The method of server version image rotation display direction ===

<ol start="31" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The results~~ Add '''extraargs=fbcon=rotate:the direction to rotate''' in '''/boot/orangepiEnv.txt''' This line configuration can set the direction displayed by the server version of ~~running~~ the Linux system, where the number after '''~~hello_world.py~~fbcon=rotate:''' ~~are shown below~~can be set as:</lip></olli>

<ol style="list-style-type: lower-alpha;"><li>0: normal screen (default is landscape)</li><li>1: Turn clockwise 90 degrees</li><li>2: Flip 180 degrees</li><li>3: Turn clockwise 270 degrees</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~python3 hello_world~~sudo vim /boot/orangepiEnv.pytxt'''

~~Hello World!~~overlays=lcd1

'''<~~ol start="3"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">extraargs=cma=64M fbcon=rotate:3<li/span>~~Ubuntu Focal~~'~~s compilation tool and operating environment without the installation of Java default~~''|}~~<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~You can use the following command to install~~ '''~~openjdk-17~~Note that if there is the line extraargs=cma=64M in /boot/orangepiEnv.txt by default, the configuration fbcon=rotate:3 can be added after extraargs=cma=64M (separated by spaces).'''</libig>|}</ol>

</li></ol>

<li>Then '''restart''' the Linux system and you can see that the direction displayed on the LCD screen has been rotated</li></ol>

~~orangepi@orangepi:~$ '''sudo apt install~~

~~<ol start~~=~~"2" style~~=~~"list-style-type: lower-alpha;"><li>After installation, you can check the~~ = Method of rotating display and touch direction of desktop version ~~of Java</li></ol>~~image ===

~~orangepi@orangepi:~$~~ # First open '''~~java --version~~Display'''Settings in Linux

~~openjdk 17.0~~::[[File:pi3b-img364.~~2 2022-01-18~~png]]

~~OpenJDK Runtime Environment (build 17.0.~~<ol start="2+8" style="list-~~Ubuntu~~style-~~120.04)~~type: decimal;"><li>Then select the direction you want to rotate in '''Rotation'''<ol style="list-style-type: lower-alpha;"><li>'''None''': no rotation</li><li>'''Left''': rotate left 90 degrees</li><li>'''Inverted''': Flip up and down, which is equivalent to rotating 180 degrees</li><li>'''Right''': rotate right 90 degrees</li>

~~OpenJDK 64~~[[File:pi3b-~~Bit Server VM (build 17~~img365.~~0.2+8~~png]]</ol></li></ol><ol start="3" style="list-~~Ubuntu~~style-~~120.04, mixed mode, sharing)~~type: decimal;"><li>Then click '''Apply'''</li>

[[File:pi3b-img366.png]]</ol><ol start="34" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Edit the~~ Then select '''~~hello_world.java~~Keep this configuration''' ~~of Jave version~~</li~~></ol~~>

[[File:pi3b-img367.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>At this point, the screen display has been rotated, and then close the '''Display''' program</li><li>The above steps will only select the display direction, and will not rotate the direction of the touch. Use the '''set_lcd_rotate.sh''' script to rotate the direction of the touch. After the script is set, it will automatically restart, and then you can test whether the touch has been used normally.<ol style="list-style-type: lower-alpha;"><li>'''None''': no rotation</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''set_lcd_rotate.sh none'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>'''Left''': rotate left 90 degrees</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~vim hello_world~~set_lcd_rotate.~~java~~sh left'''|}</ol><ol start="3" style="list-style-type: lower-alpha;">~~public~~ <li>'''Inverted''': Flip up and down, which is equivalent to rotating 180 degrees</li>{| class ~~hello_world~~="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''set_lcd_rotate.sh inverted'''|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>'''Right''': rotate right 90 degrees</li>{| class="wikitable" style="width:800px;" |-~~public static void main(String[] args)~~| orangepi@orangepi:~$ '''set_lcd_rotate.sh right'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The set_lcd_rotate.sh script mainly does four things:'''

~~System.out.println("Hello World!");~~

}'''1. Rotate the direction displayed by the framebuffer'''

}'''2. Rotate the direction of the touch'''

~~<ol start="4" style="list-style-type: lower-alpha;"><li>Then compile and run~~ '''~~hello_world~~3.~~java~~Turn off the boot logo'''~~</li></ol>~~

~~orangepi@orangepi:~$~~ '''~~javac hello_world~~4.~~java~~Restart the system'''

~~orangepi@orangepi:~$ '''java hello_world'''~~

~~Hello World!~~'''Rotating the touch direction is achieved by adding the line Option "TransformationMatrix" "x x x x x x x x x" to /usr/share/X11/xorg.conf.d/40-libinput.conf Where "x x x x x x x x x" is configured differently for different directions.'''</big>|}</ol></li></ol><ol start="7" style="list-style-type: decimal;"><li>Touch rotation reference</li>{| class="wikitable" style="width:800px;" |-| '''https://wiki.ubuntu.com/X/InputCoordinateTransformation'''|}</ol>

~~=== Ubuntu jammy system~~ =Instructions for using the switch logo ==

~~<ol style="list-style-type: decimal;"><li>Ubuntu Jammy is installed with the GCC compilation tool chain by~~ # By default, ~~which can directly compile~~ the ~~C language program~~ switch logo will only be displayed in the ~~Linux system~~ desktop version of the ~~development board<ol style="list-style-type: lower-alpha;">~~system~~<li>The version of~~ # Set the ~~gcc is shown below<~~'''bootlogo''' variable to '''false''' in '''/~~li><~~boot/~~ol></li></ol>~~orangepiEnv.txt''' to turn off the switch logo

::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~gcc --version~~vim /boot/orangepiEnv.txt'''

~~gcc (Ubuntu 11.2.0-19ubuntu1) '''11.2.0'''~~verbosity=1

~~This is free software~~<ol start="3" style="list-style-type: decimal; ~~see~~ "><li>Set the ~~source for copying conditions~~'''bootlogo''' variable to '''true''' in '''/boot/orangepiEnv. ~~There is NO~~txt''' to enable the switch logo</li>

~~warranty~~{| class="wikitable" style="width:800px; ~~not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE~~" |-| orangepi@orangepi:~$ '''vim /boot/orangepiEnv.txt'''

~~<ol start~~verbosity=~~"2" style="list-style-type: lower-alpha;"><li>Write the '''hello_world.c''' program of c language</li></ol>~~1

'''bootlogo=true'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>The location of the boot logo image in the Linux system is</li>{| class="wikitable" style="width:800px;" |-| '''/usr/share/plymouth/themes/orangepi/watermark.png'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>After replacing the boot logo picture, you need to run the following command to take effect</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~vim hello_world.c~~sudo update-initramfs -u'''|}</ol>

~~#include <stdio.h>~~== How to use the ZFS file system ==

~~int main(void)~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The latest version of Ubuntu20.04, Ubuntu22.04, Debian11 and Debian12 desktop version systems have pre-installed zfs, you can use it directly.'''

{'''The pre-installed zfs version in Ubuntu20.04 and Ubuntu22.04 desktop systems is 2.1.6.'''

~~printf("Hello World!\n");~~'''The pre-installed zfs version in Debian11 and Debian12 desktop systems is 2.1.11.'''

~~return 0;~~'''After the system starts, please first confirm whether the zfs kernel module has been loaded. If you can see zfs-related content using the lsmod command, it means that the system has pre-installed zfs.'''</big>

}orangepi@orangepi:~$ '''lsmod | grep "zfs"'''

~~<ol start="3" style="list-style-type: lower-alpha~~zfs  ">~~<li>Then compile and run '''hello_world.c'''</li></ol>~~                   2801664     0

~~orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''~~zunicode             327680     1   zfs

~~orangepi@orangepi:~$ '''./hello_world'''~~zzstd                  471040     1   zfs

~~Hello World!~~zlua                    139264     1   zfs

~~<ol start="2" style="list-style-type: decimal~~zcommon  ">~~<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>~~          69632     1   zfs

~~orangepi@orangepi:~$ '''python3'''~~znvpair                 61440     2   zfs,zcommon

~~Python '''3.10.4''' (main, Apr 2 2022, 09:04:19) [GCC 11.2.0] on linux~~zavl                      16384     1   zfs

~~Type~~ icp &~~quot~~nbsp;~~help~~&~~quot~~nbsp;, &~~quot~~nbsp;~~copyright~~&~~quot~~nbsp;, &~~quot~~nbsp;~~credits~~&~~quot~~nbsp; or &~~quot~~nbsp;~~license~~&~~quot~~nbsp; ~~for more information.~~            221184     1   zfs

spl &gtnbsp;&gtnbsp;&gtnbsp;                   77824     6   zfs,icp,zzstd,znvpair,zcommon,zavl|}

<~~ol start~~span id="~~2" style="list~~how-~~style~~to-~~type: lower~~install-~~alpha;~~zfs">~~<li>Edit '''hello_world.py''' program in Python 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.py'''</big>|}

~~print(~~Before installing zfs, you need to install the kernel header file first. For the method of installing the kernel header file, please refer to the instructions in the [[Orange Pi 3B#How to install kernel header files|'~~Hello World!~~')'section on the method of installing the kernel header file''']].

~~<ol start="3" style="list-style-type:~~ In Ubuntu20.04, Ubuntu22.04 and Debian11 systems, zfs cannot be installed directly through apt, because the default apt source zfs version is lower~~-alpha;"><li>The results~~ than 2.1.6, and there is a problem of ~~running '''hello_world~~incompatibility with rk Linux5.10 kernel. This problem is fixed in zfs version 2.1.6 and later.~~py''' are shown below</li></ol>~~

To solve this problem, we provide a zfs deb package that can be installed normally, which can be downloaded from the [http://www.orangepi~~@orangepi:~$~~ .org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''official tool'''~~python3 hello_world~~] of the development board.pyOpen 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.

~~Hello World!~~[[File:pi3b-img368.png]]

~~<ol start="3" style="list-style-type: decimal;"><li>Ubuntu jammy defaults~~ After downloading the zfs deb packages of the corresponding version, please upload them to ~~compile tools and operating environments that are not installed~~ 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 ~~Java<ol style="list-style-type: lower-alpha;"><li>You can use~~ the ~~following command~~ section of the method of uploading files to ~~install openjdk-18</li></ol></li></ol>~~the Linux system of the development board]].'''

~~orangepi@orangepi:~$~~ After the upload is complete, use the '''~~sudo apt install -y openjdk-18-jdk~~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="2wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>After installation, you can check the version of Java<~~|-| orangepi@orangepi:~$ '''sudo apt install ./~~li></ol>~~*.deb'''|}

~~orangepi@orangepi~~After the installation is complete, use the following command to see the zfs-related kernel modules:~~~$ '''java --version'''~~

~~openjdk 18~~{| class="wikitable" style="width:800px;" |-~~ea 2022~~| orangepi@orangepi:~$ '''ls /lib/modules/5.10.160-03rockchip-22rk356x/updates/dkms/'''

~~OpenJDK Runtime Environment (build 18-ea+36-Ubuntu-1)~~'''icp.ko spl.ko zavl.ko zcommon.ko zfs.ko zlua.ko znvpair.ko zunicode.ko zzstd.ko'''|}

~~OpenJDK 64-Bit Server VM (build 18-ea+36-Ubuntu-1, mixed mode, sharing)~~Then restart the Linux system to see that the zfs kernel module will be automatically loaded:

~~<ol start~~{| class="3wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>Edit the~~ |-| orangepi@orangepi:~$ '''~~hello_world.java~~lsmod | grep "zfs"''' ~~of the Jave version</li></ol>~~

~~orangepi@orangepi:~$ '''vim hello_world.java'''~~zfs                     2801664     0

~~public class hello_world~~zunicode             327680     1   zfs

{zzstd                  471040     1   zfs

~~public static void main(String[] args)~~zlua                    139264     1   zfs

{zcommon             69632     1   zfs

~~System.out.println(~~znvpair &~~quot~~nbsp;~~Hello World!~~&~~quot~~nbsp;)              61440     2  zfs,zcommon

}zavl                      16384     1   zfs

}icp                     221184     1   zfs

~~<ol start="4" style="list-style-type: lower-alpha~~spl  ">                     77824     6   zfs,icp,zzstd,znvpair,zcommon,zavl~~<li>Then compile and run '''hello_world.java'''</li></ol>~~|}

~~orangepi@orangepi:~$ '''javac hello_world~~In Debian12, the default version of zfs is 2.1.11, so we can install zfs directly through the following command. Again, please make sure that the system has installed the deb package of the kernel header file before installation.~~java'''~~

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~java hello_world~~sudo apt install -y zfsutils-linux zfs-dkms'''|}

~~Hello World!~~

~~~~== ~~QT installation method~~ Methods of creating ZFS pools ===

{| class="wikitable" style="background-color:# ~~Use~~ ffffdc;width:800px;" |-| <big>'''ZFS is based on storage pools, we can add multiple physical storage devices to the ~~following script to install QT5~~ pool, and ~~QT Creator~~then allocate storage space from this pool.'''

~~orangepi@orangepi:~$~~ '''~~install_qt~~The following content is demonstrated based on the development board connected to an NVMe SSD and a USB flash drive.sh'''</big>|}

~~<ol start="2" style="list-style-type: decimal;"><li>The QT version number will be automatically printed after installation<ol style="list-style-type: lower-alpha;"><li>Ubuntu20.04 comes with QT version~~ # First, we can use the '''~~5.12.8~~lsblk'''~~</li></ol></li></ol>~~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:

~~orangepi@orangepi~~:~~~$ '''install_qt~~:[[File:pi3b-img369.~~sh'''~~png]]

~~......~~<ol start="2" style="list-style-type: decimal;"><li>Then enter the following command to create a ZFS pool, including two storage devices, NVMe SSD and U disk</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo zpool create -f pool1 /dev/nvme0n1 /dev/sda'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then use the '''zpool list''' command to see that the system has created a ZFS pool named '''pool1''', and the size of the ZFS pool pool1 is the size of the NVME SSD plus the size of the U disk</li>

~~QMake version 3~~[[File:pi3b-img370.1png]]</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="wikitable" style="width:800px;" |-|orangepi@orangepi:~$ '''df -h'''

~~Using Qt version '''5.12.8''' in /usr/lib/aarch64-linux-gnu~~Filesystem                 Size     Used Avail Use% Mounted on

~~<ol start="2" style="list-style-type: lower-alpha~~tmpfs                   ">~~<li>Ubuntu22~~ 1.~~04 comes with QT version '''5~~6G     18M 1.~~15.3'''<~~6G 2% /~~li>~~run <~~/ol~~br>

~~orangepi@orangepi:~$ '''install_qt~~/dev/mmcblk0p2     29G     6.~~sh'''~~0G 22G 22% /

tmpfs                    7.7G     46M 7.~~....~~7G 1% /dev/shm

~~QMake version 3~~tmpfs                    5.0M     4.0K 5.0M 1% /run/lock

~~Using Qt version '''5~~tmpfs                    7.157G     944K 7.~~3''' in~~ 7G 1% /~~usr/lib/aarch64-linux-gnu~~tmp

~~<ol start="3" style="list-style-type: lower-alpha~~/dev/mmcblk0p1     1022M    ">~~<li>Debian11 comes with QT version '''5.15.2'''<~~115M 908M 12% /~~li>~~boot <~~/ol~~br>

~~orangepi@orangepi:~$ '''install_qt~~/dev/zram1                 188M     4.~~sh'''~~5M 169M 3% /var/log

tmpfs                    1.6G     80K 1.~~....~~6G 1% /run/user/1000

~~QMake version 3~~'''pool1                    489G     9.3M 489G 1% /pool1''' |}</ol><ol start="5" style="list-style-type: decimal;"><li>Use the following command to see that the file system type of pool1 is zfs</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''mount | grep pool1'''

~~Using Qt version~~ pool1 on /pool1 type '''zfs'''~~5.15.2~~(rw,xattr,noacl)|}</ol><ol start="6" style="list-style-type: decimal;"><li>Then we can test copying a file to the ZFS pool</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ ''' in sudo cp -v /usr/~~lib~~local/test.mp4 /pool1/~~aarch64-linux-gnu~~'''

'/usr/local/test.mp4' -> '/pool1/test.mp4'|}</ol ~~start~~>~~<li>Debian12 comes with QT version '''5.15.8'''</li~~></olspan>

~~orangepi@orangepi:~$ '''install_qt.sh'''~~=== Test the data deduplication function of ZFS ===

~~......~~# The data deduplication function of ZFS is disabled by default, we need to execute the following command to enable it::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo zfs set dedup=on pool1'''|}

~~QMake version 3~~<ol start="2" style="list-style-type: decimal;"><li>Then do a simple test, first enter pool1, and then execute the following command to generate a random file with a size of 1G</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''cd /pool1/''' root@orangepi:/pool1$ '''sudo dd if=/dev/urandom of=test.11g bs=1M count=1024''' 1024+0 records in

~~Using Qt version '''5.15.8''' in /usr/lib/aarch64-linux-gnu~~1024+0 records out

1073741824 bytes (1.1 GB, 1.0 GiB) copied, 5.04367 s, 213 MB/s

|}

</ol>

<li>Then ~~you can~~ use the following command to copy 1000 random files of size 1G</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/pool1$ '''for ((i=0; i<1000; i++)); do sudo cp test.1g $i.test.1g; done'''|}</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 ~~QT Creator launch icon~~ pool, but in fact the size of the ZFS pool is only '''~~Applications~~504GB'''(the total capacity of SSD+U disk), which cannot hold such a large amount of data</li><{| class="wikitable" style="width:800px;" |-| root@orangepi:/~~ol>~~pool1$ '''du -lh'''

~~[[File~~1002G|}</ol><ol start="5" style="list-style-type:~~pi3b-img327~~decimal;"><li>Then use the '''zpool list''' command to see that only 1.01G is actually occupied, because these 1001 files are all duplicates, indicating that the data deduplication function is effective.~~png|576x270px]]~~</li>

~~QT Creator can also be opened using~~ [[File:pi3b-img371.png]]</ol>

~~orangepi@orangepi:~$ '''qtcreator'''~~=== 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/'''~~During the startup of QT~~ and ~~QT applications, if the following error is displayed, ignore it. This error has no impact on application running.~~'''/etc/''' directories into a tarball

::{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~libGL error: failed to create dri screen~~cd /pool1/'''

root@orangepi:/pool1$ '''~~libGL error: failed to load driver: rockchip~~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 '''~~libGL error: failed to create dri screen~~ls -lh''' command and the space occupied in the ZFS pool are both '''~~libGL error: failed to load driver: rockchip~~27M'''</li>

[[File:pi3b-img372.png]]

</ol>

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

<li>~~The interface after QT Creator is opened is as follows~~Then execute the following command again to package the '''/var/log/''' and '''/etc/''' directories into a tar package</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:/pool1$ '''sudo tar -cf text.tar /var/log/ /etc/'''|}</ol><ol start="5" style="list-style-type: decimal;"><li>At this time, you can see that the size of the '''text.tar''' file is still 27M, but it only occupies 9.47M in the ZFS pool, indicating that the file is compressed</li>

[[File:pi3b-~~img328~~img373.png~~|418x222px~~]]</ol>

~~<ol start~~=~~"5" style~~=~~"list-style-type: decimal;"><li>The QT Creator version is shown below<ol style~~How to shut down and restart the development board ==~~"list-style-type: lower-alpha;"><li>The default version of QT Creator in '''Ubuntu20.04''' is as follows</li></ol></li></ol>~~

~~[[File:pi3b~~# During the running of the Linux system, if the Type-~~img329~~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.~~png|419x224px]]~~

~~<ol start~~::{| class="2wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>The default version of QT Creator in~~ |-| orangepi@orangepi:~$ '''~~Ubuntu22.04~~sudo poweroff''' ~~is as follows</li></ol>~~|}

~~[[File~~<ol start="2" style="list-style-type:~~pi3b-img330~~decimal;"><li>In addition, the development board is equipped with a switch button, and you can also '''short press''' the switch button on the development board to shut down.~~png|443x237px]]~~</li>

~~<ol start="3" style="list-style-type~~[[File: ~~lower~~pi3b-~~alpha;"><li>The default version of QT Creator in '''Debian11''' is as follows</li></ol>~~img374.png]]

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

[[File:pi3b-img375.png|center]]|}</ol><ol start="43" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The default version of QT Creator in '''Debian12''' is as follows~~Short press the switch button on the development board after shutting down to start up.</li~~></ol~~>

[[File:pi3b-~~img332~~img374.png~~|449x277px~~]]</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>

~~<ol start~~=~~"6" style="list-style-type: decimal;"><li>Then set QT<ol style="list-style-type: lower-alpha;"><li>First open '''Help~~'''Linux SDK——orangepi-~~>~~build instructions'''~~About Plugins...'''</li></ol></li></ol>~~=

~~[[File:pi3b~~== Compilation system requirements ==

~~<ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~Then remove the check box for~~ '''~~ClangCodeModel~~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.'''~~</li></ol>~~

~~[[File:pi3b-img334.png|408x254px]]~~

~~<ol start="3" style="list-style-type: lower-alpha;"><li>~~'''~~Restart QT Creator after~~ If you use orangepi-build to compile the ~~Settings are complete'''</li><li>Then make sure that QT Creator uses~~ Linux image in the Ubuntu22.04 system of the ~~GCC compiler~~development board, if please do a good job of cooling (especially when the ~~default~~ SSD starts). If the heat dissipation is ~~Clang~~not done well, ~~change~~ it is prone to ~~GCC~~the error of file system runaway.'''</~~p></li></ol~~big>|}

~~'''Debian12 Please skip this step~~=== Compile with the Ubuntu22.04 system of the development board ===

~~[[File:pi3b~~# The Linux SDK, namely '''orangepi-~~img335~~build''', supports running on the '''Ubuntu 22.04''' of the development board (other systems have not been tested), so before downloading orangepi-build, please first ensure that the Ubuntu version installed on the development board is Ubuntu 22.04. The command to check the Ubuntu version installed on the development board is as follows. If the Release field does not display '''22.04''', it means that the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operations.~~png|576x315px]]~~

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-~~img336.png~~|~~575x307px]]~~orangepi@orangepi:~$ '''lsb_release -a'''

~~<ol start="7" style="list-style-type: decimal;"><li>You can then open a sample code</li></ol>~~No LSB modules are available.

~~[[File~~Distributor ID:~~pi3b-img337.png|575x312px]]~~Ubuntu

~~<ol start="8" style="list-style-type~~Description: ~~decimal;"><li>Clicking on the example code will automatically open the corresponding instruction document, you can carefully read the instructions</li></ol>~~Ubuntu 22.04.1 LTS

~~[[File~~Release:~~pi3b-img338~~'''22.~~png|576x218px]]~~04'''

~~<ol start="9" style="list-style-type~~Codename: ~~decimal;">~~jammy~~<li>Then click '''Configure Project'''</li></ol>~~|}

~~[[File~~<ol start="2" style="list-style-type: decimal;"><li>'''Since the source codes such as the kernel and U-~~img339~~boot are stored on GitHub, it is very important to ensure that the development board can download codes from GitHub normally when compiling the image.~~png|575x304px]]~~'''</li></ol>

<~~ol start~~span id="~~10" style="list~~compile-with-x64-~~style~~ubuntu22.04-~~type: decimal;~~computer">~~<li>Then click the green triangle in the lower left corner to compile and run the sample code</li~~></olspan>

~~[[File:pi3b-img340~~=== Compile with x64 Ubuntu22.~~png|575x312px]]~~04 computer ===

~~<ol start="11" style="list~~# The Linux SDK, '''orangepi-~~style~~build''', supports running on computers with '''Ubuntu 22.04''' installed, so before downloading orangepi-~~type: decimal;"><li>After waiting for a period of time~~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 ~~interface shown in~~ computer is as follows. If the ~~following figure will pop up~~Release field does not display '''22.04''', ~~which indicates~~ it means that ~~QT can compile and run normally</li></ol>~~the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operations.

~~[[File~~:~~pi3b~~:{| class="wikitable" style="width:800px;" |-~~img341.png~~|~~576x308px]]~~test@test:~$ '''lsb_release -a'''

~~<ol start="12" style="list-style-type: decimal;"><li>Reference documents</li></ol>~~No LSB modules are available.

~~https~~Distributor ID:~~//wiki.qt.io/Install_Qt_5_on_Ubuntu~~Ubuntu

~~https~~Description:~~//download~~Ubuntu 22.~~qt.io/archive/qtcreator~~04 LTS

~~https~~Release:~~//download~~'''22.~~qt.io/archive~~04</qtspan>'''

~~~~Codename: jammy~~== ROS Installation Method ==~~|}

<~~span id~~ol start="2" style="~~how~~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-installan Ubuntu 22.04 virtual machine in the Windows system. But please be careful not to compile orangepi-~~ros-1-noetic-~~build onthe WSL virtual machine, because orangepi-~~ubuntu~~build has not been tested in the WSL virtual machine, so it cannot be guaranteed that orangepi-20build can be used normally in WSL.~~04"~~</~~span~~li>~~=== How to install ROS 1 Noetic on~~ <li>The download address of the installation image of Ubuntu 2022.04 '''amd64''' version is:</li>

~~# The current active version of ROS 1 is as follows, the recommended version is~~ {| class="wikitable" style="width:800px;" |-| [https://repo.huaweicloud.com/ubuntu-releases/21.04/ubuntu-21.04-desktop-amd64.iso '''~~Noetic Ninjemys~~https://mirrors.tuna.tsinghua.edu.cn/ubuntu-releases/22.04/ubuntu-22.04-desktop-amd64.iso''']

~~[[File:pi3b-img342.png|345x235px]]~~Or

~~[[File~~'''https:~~pi3b~~//repo.huaweicloud.com/ubuntu-~~img343~~releases/22.~~png~~04/ubuntu-22.04.1-desktop-amd64.iso'''|~~576x210px]]~~}</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>

~~[http~~{| class="wikitable" style="width:800px;" |-| '''https://~~docs~~mirrors.tuna.tsinghua.~~ros~~edu.~~org~~cn/help/ ~~http:~~ubuntu/'''|}</~~docs~~ol><ol start="2" style="list-style-type: lower-alpha;"><li>Note that the Ubuntu version needs to be switched to 22.~~ros.org]~~04</li>

[[File:pi3b-img376.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The content of the '''~~https:~~/etc/apt/~~wiki.ros~~sources.~~org/Distributions~~list'''file that needs to be replaced is</li>

~~<ol start~~{| class="2wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>The official installation document link of ROS 1~~ |-| test@test:~$ '''~~Noetic Ninjemys~~sudo mv /etc/apt/sources.list /etc/apt/sources.list.bak''' ~~is as follows:</li></ol>~~

~~[http~~test@test:~~//wiki.ros.org/noetic/Installation/Ubuntu~~ ~$ '''~~http:~~sudo vim /etc/apt/~~wiki.ros~~sources.~~org/noetic/Installation/Ubuntu~~list''']

<~~ol start="3" style="list-style-type: decimal;"~~p>~~<li>In~~ # By default, the source image is commented to improve the ~~official installation document~~ speed of ~~ROS '''Noetic Ninjemys''', Ubuntu recommends using Ubuntu20.04~~apt update, ~~so please make sure that the system used by the development board is '''Ubuntu20.04 desktop system'''</li>~~you can uncomment it yourself if necessary</olp>

~~http~~deb https://~~wiki~~mirrors.~~ros~~tuna.~~org~~tsinghua.edu.cn/~~noetic~~ubuntu/~~Installation~~jammy main restricted universe multiverse

~~[[File~~# deb-src https:~~pi3b-img344~~//mirrors.tuna.tsinghua.edu.~~png|312x176px]]~~cn/ubuntu/ jammy main restricted universe multiverse

~~<ol start="4" style="list-style-type~~deb https: ~~decimal;"><li>Then use the script below to install ros1<~~/~~li><~~/~~ol>~~mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse

~~orangepi@orangepi3b~~# deb-src https:~~~$ '''install_ros~~//mirrors.~~sh ros1'''~~tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse

~~<ol start="5" style="list-style-type~~deb https: ~~decimal;"><li>Before using the ROS tool, you first need to initialize rosdep, and then you can quickly install some system dependencies and some core components in ROS when compiling the source code<~~/~~li><~~/~~ol>~~mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse

~~'''Note that running the following command needs to ensure that the development board can access github normally, otherwise an error will be reported due to network problems~~# deb-src https://mirrors.~~'''~~tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse

~~'''The install_ros.sh script will try to modify~~ deb https:/~~etc~~/~~hosts and automatically run the following commands~~mirrors. ~~However, this method cannot guarantee normal access to github every time~~tuna. ~~If the following error is displayed after installing ros1 in install_ros~~tsinghua.~~sh, please find other ways to allow the Linux system of the development board to access github normally, and then manually run the following Order~~edu.~~'''~~cn/ubuntu/ jammy-security main restricted universe multiverse

~~'''~~# deb-src https://~~raw~~mirrors.tuna.tsinghua.~~githubusercontent~~edu.~~com~~cn/~~ros~~ubuntu/~~rosdistro/master/rosdep~~jammy-security main restricted universe multiverse</~~osx-homebrew.yaml'''~~p>

~~'''Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml'''~~

~~'''ERROR: error loading sources list:'''~~# Pre-release software source, not recommended to enable

~~'''The read operation timed out'''~~# deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse

~~orangepi~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>After the replacement, you need to update the package information and make sure there is no error</li>{| class="wikitable" style="width:800px;" |-| test@~~orangepi~~test:~$ '''sudo apt update'''|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>'''In addition, since the source codes such as the kernel and U-boot are stored on GitHub, it is very important to ensure that the computer can download codes from GitHub normally when compiling the image.</~~opt~~span>'''</li></ol></~~ros~~li></~~noetic~~ol></~~setup.bash'''~~span>

~~orangepi@orangepi:~$ '''sudo rosdep init'''~~== Get the source code of Linux sdk ==

~~Wrote /etc/ros/rosdep/sources.list.d~~</20span>=== Download orangepi-~~default.list~~build from github ===

~~Recommended~~# 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: ~~please run~~

~~rosdep~~ ::{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt-get update'''

~~orangepi~~test@~~orangepi~~test:~$ '''~~rosdep update~~sudo apt-get install -y git'''

~~reading in sources list data from~~ test@test:~$ '''git clone https:/~~etc~~/~~ros~~github.com/orangepi-xunlong/~~rosdep~~orangepi-build.git -b next'''|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the Orange Pi 3B development board needs to download the source code of the next</~~sources~~span> branch of orangepi-build.~~list~~The above git clone command needs to specify the branch of the orangepi-build source code as next.d'''</big>

~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml~~<div class="figure">

~~Hit https~~[[File:~~//raw~~pi3b-img377.~~githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml~~png|center]]

~~Hit https~~</div>|}::{| class="wikitable" style="background-color:#ffffdc;width:~~//raw~~800px;" |-| <big>'''Downloading the orangepi-build code through the git clone command does not require entering the user name and password of the github account (the same is true for downloading other codes in this manual), if the Ubuntu PC prompts the user to enter the github account after entering the git clone command The name and password are usually entered incorrectly in the address of the orangepi-build warehouse behind the git clone.~~githubusercontent~~Please check the spelling of the command carefully, instead of thinking that we forgot to provide the username and password of the github account.~~com~~'''</~~ros/rosdistro/master/rosdep/python.yaml~~big>|}

~~Hit https~~<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</~~/raw.githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml~~li>

~~Hit https~~{| class="wikitable" style="width:~~//raw~~800px;text-align: center;"|-|'''branch'''|'''u-boot version'''|'''Linux Kernel version'''|-|'''legacy'''|'''u-boot 2017.09'''|'''Linux5.~~githubusercontent~~10'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The branch mentioned here is not the same thing as the branch of the orangepi-build source code, please do not confuse it.~~com/ros/rosdistro/master/releases/fuerte~~This branch is mainly used to distinguish different kernel source code versions.~~yaml~~'''

~~Query rosdistro index https~~'''Currently, the Linux5.10 bsp kernel provided by RK is defined as the legacy branch. If the mainline kernel is supported in the future, a current branch will be added.'''</big>|}</ol><ol start="3" style="list-style-type: decimal;"><li>orangepi-build will contain the following files and folders after downloading<ol style="list-style-type: lower-alpha;"><li>'''build.sh''':Compile the startup script</~~raw~~li><li>'''external''': Contains the configuration files needed to compile the image, specific scripts, and the source code of some programs, etc.~~githubusercontent~~</li><li>'''LICENSE''': GPL 2 license file</li><li>README.~~com~~md: orangepi-build documentation</~~ros~~p></~~rosdistro~~li><li>'''scripts''': General script for compiling Linux images</~~master~~p></~~index~~li>{| class="wikitable" style="width:800px;" |-~~v4.yaml~~| ~~Skip end-of~~test@test:~/orangepi-~~life distro "ardent"~~build$ '''ls'''

~~Skip end-of-life distro~~ '''build.sh      external      LICENSE      README.md   &~~quot~~nbsp;~~bouncy~~&~~quot~~nbsp;scripts'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If you downloaded the code of orangepi-build from github, after downloading, you may find that orangepi-build does not contain the source code of u-boot and Linux kernel, nor does u-boot and Linux kernel need to use cross-compilation tools Chain, this is normal, because these things are stored in other separate github warehouses or some servers (the addresses will be detailed below). orangepi-build will specify the address of u-boot, Linux kernel and cross-compilation toolchain in the script and configuration file. When running orangepi-build, when it finds that there are no such things locally, it will automatically go to the corresponding place to download them.'''</big>|}</ol></li></ol>

~~Skip end~~=== Download the cross-~~of-life distro "crystal"~~compilation toolchain ===

~~Skip end~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The cross-compilation toolchain will only be downloaded when the orangepi-build compilation image is used on an x64 computer. Compiling the Linux image ofthe development board in the Ubuntu22.04 of the development board will not download the cross-compilation toolchain. At this time, orangepi-~~life distro "dashing"~~build/toolchains will be an empty folder.'''</big>|}

~~Skip end~~# When orangepi-build runs for the first time, it will automatically download the cross-compilation toolchain and put it in the '''toolchains''' folder. Every time after running the build.sh script oforangepi-build, it will check whether the cross-~~life distro "eloquent"~~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.

~~Add distro "foxy"~~<div class="figure">

~~Add distro "galactic"~~::[[File:pi3b-img378.png]]

~~Skip end~~</div><ol start="2" style="list-style-type: decimal;"><li>The image URL ofthe cross-~~life distro &quot~~compilation toolchain in China is the open source software image site of Tsinghua University</li>{| class="wikitable" style="width:800px;~~groovy&quot~~" |-| '''https://mirrors.tuna.tsinghua.edu.cn/armbian-releases/_toolchain/'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>After '''toolchains''' is downloaded, it will contain multiple versions of cross-compilation toolchains, and the development board will only use two of them</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''ls toolchains/'''

~~Add distro "humble"~~gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu

~~Skip end~~gcc-ofarm-~~life distro "hydro"~~11.2-2022.02-x86_64-arm-none-linux-gnueabihf

~~Skip end~~gcc-ofarm-~~life distro "indigo"~~9.2-2019.12-x86_64-aarch64-none-linux-gnu

~~Skip end~~gcc-ofarm-~~life distro "jade"~~9.2-2019.12-x86_64-arm-none-linux-gnueabihf

~~Skip end~~gcc-oflinaro-~~life distro "kinetic"~~4.9.4-2017.01-x86_64_arm-linux-gnueabi

~~Skip end~~gcc-oflinaro-~~life distro "lunar"~~5.5.0-2017.10-x86_64_arm-linux-gnueabihf

~~Add distro "melodic"~~gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu

~~Add distro "noetic"~~gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabi

~~Add distro "rolling"~~gcc-linaro-aarch64-none-elf-4.8-2013.11_linux

~~updated cache in /home/orangepi/~~gcc-linaro-arm-linux-gnueabihf-4.~~ros/rosdep/sources~~8-2014.~~cache~~04_linux

gcc-linaro-arm-none-eabi-4.8-2014.04_linux|}</ol><ol start="64" style="list-style-type: decimal;"><li>~~Then open a command line terminal window on~~ The cross-compilation toolchain used to compile the ~~desktop, and then use the test_ros~~Linux kernel source code is<ol style="list-style-type: lower-alpha;"><li>Linux5.~~sh script to start a small turtle routine to test whether ROS can be used normallyorangepi@orangepi~~10</li>{| class="wikitable" style="width:~$ 800px;" |-| '''~~test_ros~~gcc-arm-11.sh2-2022.02-x86_64-aarch64-none-linux-gnu'''|}</pol></li></ol><ol start="5" style="list-style-type: decimal;"><li>~~After running~~ 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;" |-| '''~~test_ros~~gcc-linaro-7.sh4.1-2019.02-x86_64_aarch64-linux-gnu''' ~~script, a little turtle as shown in the figure below will pop up~~|}</pol></li></ol>

~~<div class~~=~~"figure">~~== orangepi-build complete directory structure description ===

~~[[File~~<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:~~pi3b~~lower-~~img345~~alpha;"><li>The git warehouse where the b.~~png~~u-boot source code is stored is as follows:</li>{| class="wikitable" style="width:800px;" |~~575x275px~~-|~~图片4]]~~'''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     userpatches'''|}</ol>

~~</div><ol start~~=~~"8" style~~=~~"list~~Compile u-~~style-type: decimal;"><li>Then please keep the terminal window just opened at the top</li></ol>~~boot ==

~~<div class="figure">~~# Run the build.sh script, remember to add sudo permission

~~[[File~~:~~pi3b-img346.png~~:{|~~576x275px|图片5]]~~ ~~</div><ol start~~class="9wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>At this time, press the direction keys on the keyboard to control the little turtle to move up, down, left, and right</li></ol>~~ ~~[[File:pi3b-img347.png~~|~~575x296px]]~~ ~~=== How to install ROS 2 Galactic on Ubuntu 20.04 ===~~ ~~# The current active version of ROS 2 is as follows, the recommended version is '''Galactic Geochelone'''~~ ~~[[File:pi3b-img348.png~~|~~576x271px]]~~ ~~[[File~~test@test:~~pi3b~~~/orangepi-~~img349.png|575x265px]]~~ ~~[http://docs.ros.org/ http://docs.ros.org]~~ build$ '''~~http://docs~~sudo .~~ros.org~~/~~en/galactic/Releases~~build.~~html~~sh'''|}

<li>~~The link to the official ROS 2~~ Select '''~~Galactic Geochelone~~U-boot package''' ~~installation documentation is as follows:~~, then enter</li~~></ol~~>

~~'''docs.ros.org/en/galactic/Installation.html'''~~<div class="figure">

~~'''http~~[[File:~~//docs.ros.org/en/galactic/Installation/Ubuntu-Install~~pi3b-~~Debians~~img379.~~html'''~~png]]

</div></ol>

<li>~~It is recommended to use Ubuntu20.04 in~~ Then select the ~~official installation document~~ model of ~~ROS 2 '''Galactic Geochelone''', so please ensure that the system used by~~ the development board ~~is '''Ubuntu20.04 desktop version'''. There are several ways to install ROS 2. The following shows how to install ROS 2 '''Galactic Geochelone''' using '''Debian packages'''~~</li>~~<li>Use the '''install_ros.sh''' script to install ros2</li></ol~~>

~~orangepi@orangepi:~$ '''install_ros.sh ros2'''~~<div class="figure">

~~<ol start="5" style="list-style-type~~[[File: ~~decimal;"><li>The '''install_ros.sh''' script will automatically run the '''ros2~~ pi3b-~~h''' command after installing ros2~~img380. ~~If you can see the following print, it means that the ros2 installation is complete</li></ol>~~png]]

~~usage~~</div></ol><ol start="4" style="list-style-type: decimal;"><li>Then it will start to compile u-boot, and some information prompted during compilation is explained as follows<ol style="list-style-type: lower-alpha;"><li>u-boot source code version</li>{| class="wikitable" style="width: ~~ros2~~ 800px;" |-| [o.k. ] Compiling u-hboot [ '''v2017.09''' ] ~~Call `ros2 &lt~~|}</ol><ol start="2" style="list-style-type: lower-alpha;~~command&gt~~"><li>The version of the cross-compilation toolchain</li>{| class="wikitable" style="width:800px; " |-~~h` for more detailed usage~~| [ o. k.] Compiler version [ '''aarch64-linux-gnu-gcc 7.4.1''' ]|}</ol><ol start="3" style="list-style-type: lower-alpha;">~~ros2 is an extensible command~~<li>Path to the generated u-boot deb package</li>{| class="wikitable" style="width:800px;" |-~~line tool for ROS 2~~| [ o.k.] Target directory [ '''orangepi-build/output/debs/u-boot''' ]|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>The package name of the generated u-boot deb package</li>~~optional arguments~~{| class="wikitable" style="width:800px;" |-| [ o.k. ] File name [ '''linux-u-h, boot-legacy-orangepi3b_1.0.0_arm64.deb''' ]|}</ol><ol start="5" style="list-style-~~help show this help message and exit~~type: lower-alpha;"><li>Compilation time</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Runtime [ '''1 min''' ]|}</ol>~~Commands~~<ol start="6" style="list-style-type:lower-alpha;"><li>Repeat the command to compile u-boot, use the following command to start compiling u-boot directly without selecting through the graphical interface</li>{| class="wikitable" style="width:800px;" ~~action Various action related sub~~|-~~commands~~| ~~bag Various rosbag related sub~~[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=u-~~commands~~boot KERNEL_CONFIGURE=no''' ]|}~~component Various component related sub~~</ol></li></ol><ol start="5" style="list-~~commands~~style-type: decimal;"><li>View the u-boot deb package generated by compilation</li>~~daemon Various daemon related sub~~{| class="wikitable" style="width:800px;" |-~~commands~~| ~~doctor Check ROS setup and other potential issues~~test@test:~/orangepi-build$ '''ls output/debs/u-boot/'''

~~interface Show information about ROS interfaces~~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$ '''cd output/debs/u-boot'''

~~launch Run a launch file~~test@test:~/orangepi_build/output/debs/u-boot$ $ '''dpkg -x''' \

~~lifecycle Various lifecycle related sub~~'''linux-~~commands~~u-boot-legacy-orangepi3b_1.0.0_arm64.deb . (Note that there is a "." at the end of the command)'''

~~multicast Various multicast related sub~~test@test:~/orangepi_build/output/debs/u-~~commands~~boot$ '''ls'''

~~node Various node related sub~~linux-~~commands~~u-boot-legacy-orangepi3b_1.0.0_arm64.deb '''usr'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The decompressed file is as follows</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build/output/debs/u-boot$ '''tree usr'''

~~param Various param related sub-commands~~usr

~~pkg Various package related sub-commands~~└── lib

~~run Run a package specific executable~~:├── linux-u-boot-legacy-orangepi3b_1.0.0_arm64

~~security Various security related sub-commands~~:│ ├── idbloader.img

~~service Various service related sub-commands~~:│ ├── rkspi_loader.img

~~topic Various topic related sub~~:│ └── u-~~commands~~boot.itb

~~wtf Use `wtf` as alias to `doctor`~~:└── u-boot

~~Call `ros2 <command> -h` for more detailed usage.~~::├── LICENSE

~~<ol start="6" style="list~~::├── orangepi-~~style~~3b-~~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>~~rk3566_defconfig

~~orangepi@orangepi3b~~:~~~$ '''test_ros~~:└── platform_install.sh~~'''~~

~~[INFO] [1671174101.200091527] [talker]: Publishing: 'Hello World: 1'~~

~~[INFO] [1671174101~~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.~~235661048] [listener]: I heard: [Hello World~~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: 1]</li>

~~[INFO] [1671174102~~Set the IGNORE_UPDATES variable in userpatches/config-default.~~199572327] [talker]: Publishing: 'Hello World: 2'~~conf to "yes"

~~[INFO] [1671174102.204196299] [listener]~~{| class="wikitable" style="width: ~~I heard~~800px;" |-| test@test: ~~[Hello World: 2]~~~/orangepi-build$ '''vim userpatches/config-default.conf'''

~~[INFO] [1671174103.199580322] [talker]: Publishing:~~ IGNORE_UPDATES="''~~Hello World: 3~~' ~~[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]~~ <~~ol start="7"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">~~<li>Run the following command to open rviz2</li>~~yes</olspan> ~~orangepi@orangepi:~$ '''source /opt/ros/galactic/setup.bash~~'''" ~~orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''~~ ~~<div class="figure">~~ ~~[[File:pi3b-img350.png~~|~~576x324px|1]]~~}</~~div~~ol>

<li>~~For~~ When debugging u-boot code, you can use the ~~usage of ROS, please refer~~ following method to update u-boot in the ~~documentation of ROS 2~~Linux image for testing<ol style="list-style-type: lower-alpha;"><li>Upload the compiled u-boot deb package to the Linux system of the development board</olli>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''cd output/debs/u-boot'''

~~http~~test@test:~/orangepi_build/~~docs.ros.org~~output/endebs/~~galactic/Tutorials.html~~u-boot$ '''scp \'''

'''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb root@192.168.1.xxx:/root'''|}<~~span id~~/ol><ol start="2" style="~~how~~list-style-type: lower-alpha;"><li>Then log in tothe development board and uninstall the deb package of u-boot installed</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''apt purge -y linux-~~install~~u-~~ros~~boot-2orangepi3b-~~humble~~legacy'''|}</ol><ol start="3" style="list-onstyle-~~ubuntu~~type: lower-~~22.04~~alpha;"><li>Install the new u-boot deb package just uploaded</~~span~~li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''dpkg -i''' '''linux-u-boot-legacy-orangepi3b_1.0.0_arm64.deb'''|}</ol><ol start= ~~How to~~ "4" style="list-style-type: lower-alpha;"><li>Then run the nand-sata-install ~~ROS 2 Humble on Ubuntu 22.04~~ script</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''nand-sata-install'''|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then select '''5 Install/Update the bootloader on SD/eMM''' to update the u-boot in the TF card or '''7 Install/Update the bootloader on SPI Flash''' to update the u-boot in the SPI Flash</li>

~~# Use~~ [[File:pi3b-img381.png]]</ol><ol start="6" style="list-style-type: lower-alpha;"><li>After pressing the ~~'''install_ros.sh''' script to install ros2~~Enter key, a Warning will pop up first</li>

~~orangepi@orangepi~~[[File:~~~$ '''install_ros~~pi3b-img382.~~sh ros2'''~~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>

[[File:pi3b-img383.png]]</ol><ol start="8" style="list-style-type: lower-alpha;"><li>Then you can restart the development board to test whether the modification of u-boot takes effect</li></ol></li></ol><ol start="29" style="list-style-type: decimal;"><li>~~The~~ 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 '''~~install_ros~~orangepi-build/u-boot/v2017.sh09-rk3588/configs/orangepi-3b-rk3566_defconfig''' ~~script will automatically run~~ ]|}</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 '''~~ros2~~ orangepi-build/u-boot/v2017.09-hrk3588/arch/arm/dts/rk3566-orangepi-3b.dts''' ~~command after installing ros2. If you can see the following print, it means that the ros2 installation is complete~~]|}</ol></li></ol>

~~usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...~~== Compile the Linux kernel ==

~~ros2 is an extensible command-line tool for ROS 2~~# Run the build.sh script, remember to add sudo permission

~~optional arguments~~::{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''sudo ./build.sh'''|}

<ol start="2" style="list-hstyle-type: decimal;"><li>Select '''Kernel package''', ~~--help show this help message and exit~~then enter</li>

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

~~action Various action related sub~~[[File:pi3b-~~commands~~img384.png]]

~~bag Various rosbag related sub~~</div></ol><ol start="3" style="list-~~commands~~style-type: decimal;"><li>Then select the model of the development board</li>

~~component Various component related sub-commands~~<div class="figure">

~~daemon Various daemon related sub~~[[File:pi3b-~~commands~~img380.png]]

~~doctor Check ROS setup and other potential issues~~</div></ol><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>

[[File:pi3b-img385.png]]</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 ~~Show information about ROS interfaces~~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>

~~launch Run a launch file~~[[File:pi3b-img386.png]]

~~lifecycle Various lifecycle related sub~~<ol style="list-~~commands~~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$ '''sudo ./build.sh KERNEL_CONFIGURE=no'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>You can also set '''KERNEL_CONFIGURE=no''' in the '''orangepi-build/userpatches/config-default.conf''' configuration file, which can permanently disable this function</li><li>If the following error is displayed when compiling the kernel, it is because the terminal interface of the Ubuntu PC is too small to display the '''make menuconfig''' interface. Please maximize the terminal of the Ubuntu PC and run the build.sh script again</li>

~~multicast Various multicast related sub~~[[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 [ '''5.10.160''' ]|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>The version of the cross-compilation toolchain used</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Compiler version [ '''aarch64-none-linux-gnu-gcc 11.2.1''' ]|}</ol><ol start="3" style="list-style-type: lower-~~commands~~alpha;"><li>The configuration file used by the kernel by default and the path where it is stored</li>{| class="wikitable" style="width:800px;" ~~node Various node related sub~~|-~~commands~~| ~~param Various param related sub~~[ o.k. ] Using kernel config file [ '''config/kernel/linux-rockchip-rk356x-~~commands~~legacy.config''' ]|}</ol><ol start="4" style="list-style-type: lower-alpha;">~~pkg Various~~ <li>The path of the deb package related ~~sub~~to the kernel generated by compiling</li>{| class="wikitable" style="width:800px;" |-~~commands~~| [ o.k. ] Target directory [ '''orangepi-build/output/debs/''' ]~~run Run a~~ |}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>The package ~~specific executable~~name of the compiled kernel image deb package</li>{| class="wikitable" style="width:800px;" ~~security Various security~~ |-| [ 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;" |-| [ o.k. ] Runtime [ '''5 min''' ]|}</ol><ol start="7" style="list-style-type: lower-alpha;"><li>Finally, the compilation command to repeatedly compile the kernel selected last time will be displayed. Use the following command to start compiling the kernel source code directly without selecting through the graphical interface</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] 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 ~~sub~~to the kernel generated by compilation<ol style="list-style-type: lower-alpha;"><li>'''linux-dtb-legacy-rockchip-~~commands~~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>~~service Various service related sub~~<li>'''linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb''' Contains kernel images and kernel modules</li>{| class="wikitable" style="width:800px;" |-~~commands~~| ~~topic Various topic related sub~~test@test:~/orangepi-build$ '''ls output/debs/linux-~~commands~~*'''

~~wtf Use `wtf` as alias to `doctor`~~output/debs/linux-dtb-legacy-rockchip-rk356x_1.0.0_arm64.deb output/debs/linux-image-legacy-rockchip-rk356x_1.0.0_arm64.deb

~~Call `ros2 &lt~~output/debs/linux-headers-legacy-rockchip-rk356x_1.0.0_arm64.deb|}</ol></li></ol><ol start="8" style="list-style-type: decimal;"><li>The files contained in the generated Linux-image deb package are as follows<ol style="list-style-type: lower-alpha;"><li>Use the following command~~&gt~~to decompress the deb package</li>{| class="wikitable" style="width:800px; " |-| test@test:~/orangepi-~~h` for more detailed usage.~~build$ '''cd output/debs'''

~~<ol start="3" style="list-style-type~~test@test: ~~decimal;"><li>Then you can use the~~ ~/orangepi_build/output/debs$ '''~~test_ros.sh~~mkdir test''' ~~script to test whether ROS 2 is installed successfully. If you can see the following print, it means that ROS 2 can run normally</li></ol>~~

~~orangepi~~test@~~orangepi3b~~test:~/orangepi_build/output/debs$ '''~~test_ros.sh~~cp \'''

~~[INFO] [1671174101~~'''linux-image-legacy-rockchip-rk356x_1.0.~~200091527] [talker]: Publishing:~~ 0_arm64.deb test/''~~Hello World: 1~~'

~~[INFO] [1671174101.235661048] [listener]~~test@test: ~~I heard: [Hello World: 1]~~~/orangepi_build/output/debs$ '''cd test'''

~~[INFO] [1671174102.199572327] [talker]: Publishing~~test@test: ~/orangepi_build/output/debs/test$ '''dpkg -x \''~~Hello World: 2~~'

~~[INFO] [1671174102~~'''linux-image-legacy-rockchip-rk356x_1.~~204196299] [listener]: I heard: [Hello World: 2]~~0.0_arm64.deb .'''

~~[INFO] [1671174103.199580322] [talker]: Publishing~~test@test: ~/orangepi_build/output/debs/test$ '''ls''~~Hello World: 3~~'

~~[INFO] [1671174103~~'''boot etc lib''' linux-image-legacy-rockchip-rk356x_1.~~204019965] [listener]~~0.0_arm64.deb '''usr'''|}</ol><ol start="2" style="list-style-type: ~~I heard~~lower-alpha;"><li>The decompressed file is as follows</li>{| class="wikitable" style="width: ~~[Hello World~~800px;" |-| test@test: 3]~/orangepi-build/output/debs/test$ '''tree -L 2'''

~~<ol start="4" style="list-style-type: decimal;"><li>Run the following command to open rviz2</li></ol>~~.

~~orangepi@orangepi:~$ '''source /opt/ros/humble/setup.bash'''~~├── boot

~~orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''~~│ ├── config-5.10.160-rockchip-rk356x

~~<div class="figure">~~│ ├── System.map-5.10.160-rockchip-rk356x

~~[[File:pi3b~~│ └── vmlinuz-~~img351~~5.~~png|576x324px|1]]~~10.160-rockchip-rk356x

~~</div><ol start="5" style="list-style-type: decimal;"><li>Reference documents</li></ol>~~├── etc

~~'''http://docs.ros.org/en/humble/index.html'''~~│ └── kernel

~~[http://docs.ros.org/en/galactic/Tutorials.html '''http://docs.ros.org/en/humble/Installation/Ubuntu-Install-Debians.html''']~~├── lib

~~== How to install kernel header files ==~~│ └── modules

~~# The Linux~~ ├── linux-image ~~released by OPi comes with the~~ -legacy-rockchip-rk356x_1.0.0_arm64.deb ~~package of the kernel header file by default, and the storage location is '''/opt/'''~~

~~orangepi@orangepi:~$ '''ls /opt/linux-headers*'''~~└── usr

~~/opt/linux-headers-legacy-rockchip-rk356x_x.x.x_arm64.deb~~:├── lib

:└── share|}</ol></li></ol><ol start="29" style="list-style-type: decimal;"><li>~~Use~~ The orangepi-bulid compilation system will first synchronize the ~~following command~~ 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 ~~install~~ 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 ~~deb~~ 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 ~~kernel header file~~The changes made will be reverted as follows:</li~~></ol~~>

Set the IGNORE_UPDATES variable in '''~~The name of the kernel header file deb package needs to be replaced with the actual name, please do not copy it~~userpatches/config-default.conf'''to "yes"

~~orangepi~~{| class="wikitable" style="width:800px;" |-| test@~~orangepi~~test:~/orangepi-build$ '''~~sudo dpkg -i /opt~~vim userpatches/~~linux-headers~~config-~~legacy-rockchip-rk356x_1.x.x_arm64~~default.~~deb~~conf'''

IGNORE_UPDATES="'''yes'''"|}</ol><ol start="310" style="list-style-type: decimal;"><li>~~After installation~~If the kernel has been modified, ~~you~~ the following method can ~~see~~ 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 ~~folder where~~ deb package of the compiled Linux kernel ~~header files are located under~~ to the Linux system of the development board</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''cd output/~~usr/src~~debs'''~~</li></ol>~~

~~orangepi~~test@~~orangepi~~test:~/orangepi-build/output/debs$ '''~~ls /usr/src~~scp \'''

'''linux-~~headers~~image-5legacy-rockchip-rk356x_1.100.~~160~~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>~~Then you can write a hello kernel module to test the kernel header file~~Other useful information

<li>~~First write the code~~ The storage location of the ~~hello~~ kernel ~~module,~~ configuration file is as follows, please do not go to the kernel source code to find the kernel configuration file used by the development board</li>{| class="wikitable" style="width:800px;" |-| [https://github.com/orangepi-xunlong/orangepi-build/blob/next/external/config/kernel/linux-rockchip-rk3588-legacy.config '''orangepi-build/external/config/kernel/linux-rockchip-rk356x-legacy.config''']|}</ol><ol start="2" style="list-style-type:lower-alpha;"><li>The location of the dts file used by the development board is</li>{| class="wikitable" style="width:800px;" |-| [https://github.com/orangepi-xunlong/linux-orangepi/blob/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5.dts '''orangepi-build/kernel/orange-pi-5.10-rk35xx/arch/arm64/boot/dts/rockchip/rk3566-orangepi-3b.dts''']|}</ol>

</li></ol>

~~orangepi@orangepi:~$ '''vim hello.c'''~~== Compile rootfs ==

#~~include <linux/init~~Run the build.~~h>~~sh script, remember to add sudo permission

~~#include &lt~~::{| class="wikitable" style="width:800px;~~linux~~" |-| test@test:~/~~module~~orangepi-build$ '''sudo .~~h>~~/build.sh'''|}

~~static int hello_init(void)~~<ol start="2" style="list-style-type: decimal;"><li>Select '''Rootfs and all deb packages''', then enter</li>

{<div class="figure">

~~printk("Hello Orange Pi~~ [[File:pi3b-~~- init\n");~~img388.png]]

~~return 0~~</div></ol><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li>

}<div class="figure">

~~static void hello_exit(void)~~[[File:pi3b-img380.png]]

{</div></ol><ol start="4" style="list-style-type: decimal;"><li>Then select the type of rootfs</li>

~~printk(&quot~~[[File:pi3b-img389.png]]</ol><ol start="5" style="list-style-type: decimal;~~Hello Orange Pi~~ "><li>Then select the type of image<ol style="list-style- ~~exit\n&quot~~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>

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

}[[File:pi3b-img390.png]]

~~module_init~~</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 '''(~~hello_init~~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>

~~module_exit(hello_exit);~~<div class="figure">

~~MODULE_LICENSE("GPL");~~[[File:pi3b-img391.png]]

</div></ol><ol start="27" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then write~~ If you are compiling the ~~Makefile for compiling~~ image of the desktop version, you also need to select the ~~hello kernel module~~type of desktop environment. Currently, Ubuntu Jammy mainly maintains XFCE and Gnome desktops, Ubuntu Focal only maintains XFCE desktops, ~~as follows:~~and Debian Bullseye mainly maintains XFCE and KDE desktops</li~~></ol~~>

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

~~ifneq ($(KERNELRELEASE),)~~[[File:pi3b-img392.png]]

~~obj~~</div>[[File:pi3b-~~m:=hello~~img393.opng]]

~~else~~ ~~KDIR :=/lib/modules/$(shell uname -r)/build~~ ~~PWD :=$(shell pwd)~~ ~~all:~~ ~~make -C $(KDIR) M=$(PWD) modules~~ ~~clean:~~ rm -f *You can then select additional packages that need to be installed.ko *Please press the Enter key to skip directly here.~~o *.mod.o *.mod *.symvers *.cmd *.mod.c *.order~~ ~~endif~~

[[File:pi3b-img394.png]]

</ol>

<li>Then it will start to compile rootfs, and some of the information prompted during compilation are as follows

<li>The type of rootfs</li>

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

|-

|

[ o.k. ] local not found [ Creating new rootfs cache for '''jammy''']

|}

</ol>

<li>The storage path of the compiled rootfs compressed package</li>

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

|-

|

[ o.k. ] Target directory [ '''external/cache/rootfs''' ]

|}

</ol>

<li>~~Then use~~ The name of the ~~make command to compile~~ rootfs compressed package generated by compilation</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] File name [ '''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' ]|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>The time used for compilation</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Runtime [ '''13 min''' ]|}</ol></li></ol><ol start="9" style="list-style-type: decimal;"><li>View the ~~hello kernel module~~rootfs compressed package generated by compilation<ol style="list-style-type: lower-alpha;"><li>'''jammy-xfce-arm64. ~~The output~~ f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' is the rootfs compressed package, the meaning of each field of the name is<ol style="list-style-type: none;"><li>a) '''jammy''' indicates the type of Linux distribution of rootfs</li><li>b) '''xfce''' means rootfs is the type of desktop version, if it is '''cli''', it means the type of server version</li><li>c) '''arm64''' represents the ~~compilation process~~ architecture type of rootfs</li><li>d) '''f930ff6ebbac1a72108a2e100762b18f''' is the MD5 hash value generated by the package names of all software packages installed by rootfs. As long as ~~follows:~~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/'''

'''~~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~~jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4'''

~~[[File:pi3b~~jammy-~~img352~~xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.~~png|337x52px]]~~current

~~orangepi@orangepi~~jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.list|}</ol></li></ol><ol start="10" style="list-style-type:~$ decimal;"><li>If the required rootfs already exists under '''~~make~~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>

~~make -C /lib/modules/5.10.160~~</~~orangepi modules~~span>

~~make[1]: Entering directory '/usr/src/linux-headers-5.10.160-rockchip-rk35xx'~~== Compile Linux image ==

~~CC [M] /home/orangepi/hello~~# Run the build.osh script, remember to add sudo permission

~~MODPOST /home~~::{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''sudo ./~~Module~~build.~~symvers~~sh'''|}

~~CC [M]~~ <ol start="2" style="list-style-type: decimal;"><li>Select '''Full OS image for flashing''', then enter</~~home/orangepi/hello.mod.o~~li>

~~LD [M] /home/orangepi/hello.ko~~<div class="figure">

~~make~~[1][File: ~~Leaving directory '/usr/src/linux-headers~~pi3b-5img395.~~10.160-rockchip-rk35xx'~~png]]

</div></ol><ol start="43" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~After compiling,~~ Then select the model of the ~~'''hello.ko''' kernel module will be generated~~development board</li~~></ol~~>

~~orangepi@orangepi:~$ '''ls *.ko'''~~ ~~hello.ko~~<div class="figure">

~~<ol start="5" style="list-style-type~~[[File: ~~lower~~pi3b-~~alpha;"><li>Use the '''insmod''' command to insert the '''hello~~img380.~~ko''' kernel module into the kernel</li></ol>~~png]]

~~orangepi@orangepi~~</div></ol><ol start="4" style="list-style-type:~~~$ '''sudo insmod hello.ko'''~~decimal;"><li>Then select the type of rootfs</li>

[[File:pi3b-img389.png]]</ol><ol start="65" style="list-style-type: decimal;"><li>Then select the type of image<ol style="list-style-type: lower-alpha;"><li>~~Then use the~~ '''~~demsg~~Image with console interface (server)''' ~~command to view~~ Indicates the ~~output~~ image of the server version, which is relatively small</li><li>'''~~hello.ko~~Image with desktop environment''' ~~kernel module. If you can see the output below~~Indicates a image with a desktop, ~~it means that the '''hello.ko''' kernel module~~ which is ~~loaded correctly.~~relatively large</li> <~~/ol~~div class="figure">

~~orangepi@orangepi~~[[File:~~~$ '''dmesg | grep "Hello"'''~~pi3b-img390.png]]

~~[ 2871~~</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.~~893988]~~ The pre-installed software of the Minimal version will be much less than that of the Standard version '''~~Hello Orange Pi~~ (please do not choose the Minimal version if there is no special requirement, because many things are not pre-~~- init~~installed by default. Some functions may not be available)'''</li>

<~~ol start~~div class="7figure" ~~style="list-style-type: lower-alpha;"><li>Use the '''rmmod''' command to uninstall the '''hello.ko''' kernel module</li></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''sudo rmmod hello'''~~pi3b-img391.png]]

~~orangepi@orangepi~~</div></ol><ol start="7" style="list-style-type:~~~$ '''dmesg | grep &quot~~decimal;~~Hello"'''~~"><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>

~~[ 2871.893988] Hello Orange Pi -- init~~<div class="figure">

[ ~~3173~~[File:pi3b-img392.~~800892~~png]] ~~'''Hello Orange Pi -- exit'''~~

~~~~</~~span~~div>~~== Use of the Raspberry PI's 5~~[[File:pi3b-~~inch screen ==~~img393.png]]

~~=== Assembly method of Raspberry PI 5-inch screen ===~~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>~~First prepare~~ 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 ~~accessories~~for the compilation process</li><li>Download the source code of u-boot and Linux kernel (if cached, only update the code)</li><li>Compile u-boot source code and generate u-boot deb package</li><li>Compile the Linux source code and generate Linux-related deb packages</li><li>Make the deb package of Linux firmware</li><li>Make the deb package of the orangepi-config tool</li><li>Create a deb package supported by the board</li><li>If you are compiling the desktop image, you will also create desktop-related deb packages</li><li>Check whether the rootfs has been cached, if not, recreate the rootfs, if it has been cached, directly decompress and use</li><li>Install the previously generated deb package into rootfs</li><li>Make some specific settings for different development boards and different types of images, such as pre-installing additional software packages, modifying system configuration, etc.</li><li>Then make an image file and format the partition, the default type is ext4</li><li>Then copy the configured rootfs to the mirrored partition</li><li>Then update initramfs</li><li>Finally, write the bin file of u-boot into the image through the dd command</li></ol></li><li>After compiling the image, the following information will be prompted

<li>~~Raspberry PI 5~~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-~~inch MIPI LCD display + touch screen~~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 [ '''sudo ./build.sh BOARD=orangepi3b BRANCH=legacy BUILD_OPT=image RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=yes''' ]|}</ol>

</li></ol>

~~<blockquote>[[File:pi3b-img353.png|306x219px]]</blockquote><ol start~~=~~"2" style~~'''Android 11 operating system instructions''' =~~"list-style-type: lower-alpha;"><li>15pin MIPI cable</li></ol>~~

<~~blockquote>[[File:pi3b-img354.png|276x111px]]</blockquote><ol start="2" style~~span id="~~list~~supported-~~style~~android-~~type: decimal;~~versions">~~<li>Then connect the 15pin MIPI cable to the Raspberry PI 5-inch screen in the way shown below (note the orientation of the insulation surface)~~</~~li></ol~~span>== Supported Android versions ==

~~[[File:pi3b-img355.png~~{|~~294x160px]]~~ ~~<ol start~~class="3wikitable" style="~~list~~width:800px;text-~~style-type~~align: ~~decimal~~center;">~~<li>Finally connect to the LCD interface of the Orange Pi 3B development board</li></ol>~~|-|'''Android version'''|'''Kernel version'''|-|'''Android 11'''|'''Linux4.19'''|}

~~[[File:pi3b~~

~~=== Open the Raspberry PI 5-inch screen configuration method~~ =Android Function Adaptation ==

~~<ol~~ {| class="wikitable" style="~~list-style~~width:800px;text-~~type~~align: ~~decimal~~center;">~~<li>The Linux image does not open the 5~~|-|'''Functions'''|'''Android 11'''|-~~inch screen of the Raspberry PI by default~~|'''USB2. ~~If you need to use the 5~~0x3'''|'''OK'''|-~~inch screen of the Raspberry PI, you need to open it manually~~|'''USB3.~~</li>~~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'''~~<li>The steps to open the mipi lcd configuration are as follows:~~|'''OK'''|-|'''LCD'''|'''OK'''|-|'''eDP display'''|'''OK'''|-|'''Gigabit network port'''|'''OK'''|-|'''Network port status indicator'''|'''OK'''|-|'''Headphone playback'''|'''OK'''|-|'''Headphone recording'''|'''OK'''|-|'''LED Light'''|'''OK'''~~<ol style="list~~|-~~style~~|'''GPU'''|'''OK'''|-~~type: lower~~|'''NPU'''|'''OK'''|-~~alpha;"><li>First run~~ |'''VPU'''|'''~~orangepi~~OK'''|-~~config~~|'''RTC''~~, ordinary users remember to add~~ '|'''~~sudo~~OK''' ~~permission</li></ol></li></ol>~~|}

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

~~<ol start~~=~~"2" style~~=~~"list-style-type: lower-alpha;"><li>Then select '''System'''</li></ol>~~WIFI connection test method ==

~~[[File:pi3b-img357.png|575x272px]]~~# First click enter '''Setting'''

~~<ol start="3" style="list-style-type~~: ~~lower~~:[[File:pi3b-~~alpha;"><li>Then select '''Hardware'''</li></ol>~~img396.png]]

~~[[File~~<ol start="2" style="list-style-type:~~pi3b-img358.png|576x266px]]~~decimal;"><li>Then select '''Network & internet'''</li>

[[File:pi3b-img397.png]]</ol><ol start="43" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~use the arrow keys on the keyboard to locate the Rasp-7inch~~select '''Wi-~~touchscreen, and then use the space button to check~~Fi'''</li~~></ol~~>

[[File:pi3b-~~img359~~img398.png~~|408x310px~~]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then turn on the '''Wi-Fi''' switch</li>

[[File:pi3b-img399.png]]</ol><ol start="5" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Then select~~ After turning on '''~~<Save>~~Wi-Fi''' ~~to save~~, if everything is normal, you can scan for nearby Wi-Fi hotspots</li~~></ol~~>

[[File:pi3b-~~img360~~img400.png~~|404x133px~~]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then select the Wi-Fi you want to connect to, and the password input interface shown in the figure below will pop up</li>

[[File:pi3b-img401.png]]</ol><ol start="67" style="list-style-type: ~~lower-alpha~~decimal;"><li>Then ~~select '''<Back>'''~~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-~~img361~~img402.png~~|397x151px~~]]</ol><ol start="8" style="list-style-type: decimal;"><li>After the Wi-Fi connection is successful, the display is as shown in the figure below:</li>

[[File:pi3b-img403.png]]</ol ~~start~~>~~<li>Then select '''<Reboot>''' to restart the system for the configuration to take effect~~</~~li></ol~~span>

~~[[File:pi3b~~== How to use Wi-~~img362.png|331x154px]]~~Fi hotspot ==

~~'''The above settings will eventually add~~ # First, please make sure that the ~~configuration of overlays=raspi-7inch-touchscreen~~ Ethernet port is connected to ~~/boot/orangepiEnv.txt. After setting, you~~ the network cable and can ~~check it first. If this configuration does not exist, then there is a problem with~~ access the ~~settings.~~Internet normally# Then select '''Settings'''

~~'''If you find it troublesome to use orangepi~~::[[File:pi3b-~~config, you can also use the vim editor to open /boot/orangepiEnv~~img396.~~txt, and then add the configuration of overlays=raspi-7inch-touchscreen is also possible.'''~~png]]

~~orangepi@orangepi~~<ol start="3" style="list-style-type:~$ decimal;"><li>Then select '''~~cat /boot/orangepiEnv.txt | grep "raspi"~~Network & internet'''</li>

[[File:pi3b-img397.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select '''~~overlays=raspi-7inch-touchscreen #Sample configuration~~Hotspot & tethering'''</li>

[[File:pi3b-img404.png]]</ol><ol start="35" style="list-style-type: decimal;"><li>~~After startup, you can see the lcd screen display as follows:~~Then select '''Wi-Fi hotspot'''</li~~></ol~~>

[[File:pi3b-~~img363~~img405.png~~|381x262px~~]]</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><~~span id~~ol start="~~the~~7" style="list-~~method~~style-~~of-server-version-image-rotation-display-direction~~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</~~span~~li>~~=== The method of server version image rotation display direction ===~~

~~# Add '''extraargs~~[[File:pi3b-img407.png]]</ol><ol start=~~fbcon~~"8" style=~~rotate~~"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 ~~direction~~ specific interface is subject to ~~rotate''' in '''/boot/orangepiEnv~~the display of your mobile phone).~~txt''' This line configuration~~ At this point, you can open a webpage on your mobile phone to see if you can ~~set~~ access the ~~direction displayed by the server version of~~ Internet. If you can open the ~~Linux system~~webpage normally, ~~where~~ it means that the ~~number after~~ '''~~fbcon=rotate:~~WI-FI Hotspot''' of the development board can be ~~set as:~~used normally.</li>

[[File:pi3b-img408.png]]<~~!-- --~~/ol><~~ol style~~span id="~~list-style~~bluetooth-~~type: lower~~test-~~alpha;~~method">~~<li>0: normal screen (default is landscape)</p~~></~~li><li>1: Turn clockwise 90 degrees</li><li>2: Flip 180 degrees</li><li>3: Turn clockwise 270 degrees</li></ol~~span>

~~orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''~~== Bluetooth test method ==

~~overlays=lcd1~~# First click enter '''Setting'''

~~'''extraargs=cma=64M fbcon=rotate~~:~~3'''~~ ~~'''Note that if there is the line extraargs=cma=64M in /boot/orangepiEnv.txt by default, the configuration fbcon=rotate~~:~~3 can be added after extraargs=cma=64M (separated by spaces)~~[[File:pi3b-img396.~~'''~~png]]

<li>Then select '''~~restart~~Connected devices''' ~~the Linux system and you can see that the direction displayed on the LCD screen has been rotated~~</li~~></ol~~>

[[File:pi3b-img409.png]]</ol><~~span id~~ol start="~~method-of-rotating-display-and-touch-direction-of-desktop~~3" style="list-~~version~~style-~~image~~type: decimal;"><li>Then click '''Pair new device''' to turn on Bluetooth and start scanning the surrounding Bluetooth devices</~~span~~li>~~=== Method of rotating display and touch direction of desktop version image ===~~

~~# First open~~ [[File:pi3b-img410.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>The searched Bluetooth devices will be displayed under '''~~Display~~Available devices''' ~~Settings in Linux~~</li>

[[File:pi3b-~~img364~~img411.png~~|298x206px~~]]</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="26" style="list-style-type: decimal;"><li>~~Then select~~ The test here is the configuration process of the development board and the Bluetooth of the Android mobile phone. At this time, the ~~direction you want to rotate in '''Rotation'''<ol style="list-style-type: lower-alpha;"><li>'''None''': no rotation</li><li>'''Left''': rotate left 90 degrees</li><li>'''Inverted''': Flip~~ following confirmation interface will pop up ~~and down~~on the mobile phone. After clicking the pairing button on the mobile phone, ~~which is equivalent to rotating 180 degrees</li><li>'''Right''': rotate right 90 degrees~~the pairing process will start</li~~></ol></li></ol~~>

[[File:pi3b-~~img365~~img413.png~~|286x180px~~]]</ol><ol start="7" style="list-style-type: decimal;"><li>After the pairing is completed, you can see the paired Bluetooth device as shown in the figure below</li>

[[File:pi3b-img414.png]]</ol><ol start="38" style="list-style-type: decimal;"><li>~~Then~~ 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 '''~~Apply~~Accept'''to start receiving the picture sent by the mobile phone.</li~~></ol~~>

[[File:pi3b-~~img366~~img415.png~~|330x207px~~]]</ol><ol start="9" style="list-style-type: decimal;"><li>You can open the '''Download''' directory in the file manager to view the pictures received by the Android system Bluetooth of the development board</li>

[[File:pi3b-img416.png]]</ol ~~start~~>~~<li>Then select '''Keep this configuration'''~~</~~li></ol~~span>

~~[[File:pi3b~~== How to use Raspberry Pi 5-~~img367.png|374x210px]]~~inch screen ==

~~<ol start~~{| class="5wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <~~li><p~~big>~~At this point, the screen display has been rotated, and then close the~~ '''~~Display''' program</li><li>The above steps will only select~~ Please make sure that the ~~display direction, and will not rotate~~ image used is the ~~direction~~ following two versions of the ~~touch. Use the~~ image:'''~~set_lcd_rotate.sh~~ ''' ~~script to rotate the direction of the touch~~OrangePi3B_RK3566_Android11_lcd_v1.x. ~~After the script is set, it will automatically restart, and then you can test whether the touch has been used normally~~x.~~<ol style="list-style-type: lower-alpha;"><li>~~img'''~~None''': no rotation</li></ol></li></ol>~~

~~orangepi@orangepi:~$~~ '''~~set_lcd_rotate~~OrangePi3B_RK3566_Android11_spi-nvme_lcd_v1.~~sh none~~x.x.img'''</big>|}

~~<ol start="2" style="list-style-type: lower~~# The screen needs to be assembled first, please refer to [[Orange Pi 3B#Use of the Raspberry PI's 5-~~alpha;"><li>~~inch screen|'''~~Left~~the assembly method of the Raspberry Pi 5-inch screen'''~~: rotate left 90 degrees</li></ol>~~]]# 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

~~orangepi@orangepi~~:~~~$ '''set_lcd_rotate~~:[[File:pi3b-img417.~~sh left'''~~png]]

<~~ol start~~span id="~~3" style="list~~pin-interface-gpio-uart-spi-~~style~~and-~~type: lower~~pwm-~~alpha;~~test">~~<li>'''Inverted''': Flip up and down, which is equivalent to rotating 180 degrees</li~~></olspan>

~~orangepi@orangepi:~$ '''set_lcd_rotate.sh inverted'''~~== 40pin interface GPIO, UART, SPI and PWM test ==

<~~ol start~~span id="~~4" style="list~~pin-gpio-~~style~~port-~~type: lower~~test-~~alpha;~~2">~~<li>'''Right''': rotate right 90 degrees~~</~~li></ol~~span>=== 40pin GPIO port test ===

~~orangepi@orangepi:~$ '''set_lcd_rotate.sh right'''~~# First click on the wiringOP icon to open the wiringOP APP

~~'''The set_lcd_rotate~~::[[File:pi3b-img418.~~sh script mainly does four things:'''~~png]]

<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 '''~~1. Rotate the direction displayed by the framebuffer~~GPIO_TEST'''button to open the GPIO test interface</li>

[[File:pi3b-img419.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>The GPIO test interface is shown in the figure below. The two rows of '''CheckBox''2' buttons on the left are in one-to-one correspondence with the 40pin pins. ~~Rotate~~ 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 ~~direction of~~ 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 ~~touch~~'''BLINK ALL GPIO''' button is clicked, the program will control the 28 GPIO ports to continuously switch between high and low levels</li>

[[File:pi3b-img420.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then click the '''~~3. Turn off the boot logo~~GPIO READALL'''button, the output information is as shown in the figure below:</li>

[[File:pi3b-img421.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>There are a total of 28 GPIO ports in the 40pins of the development board that can be used. The following uses pin 7—the corresponding GPIO is GPIO4_A4—the corresponding wPi serial number is 2—as an example to demonstrate how to set the high and low levels of the GPIO port. First click the '''~~4. Restart the system~~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>

[[File:pi3b-img422.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL'~~Rotating~~ '' button, you can see that the ~~touch direction~~ current pin 7 mode is achieved by adding the line Option "TransformationMatrix" "x x x x x x x x x" to /usr/share/X11/xorg.conf.d/40-libinput.conf Where "x x x x x x x x x" is configured differently for different directions.'''OUT''', and the pin level is high</li>

[[File:pi3b-img423.png]]

</ol>

<li>~~Touch rotation reference~~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~~>

~~https~~[[File:~~//wiki.ubuntu~~pi3b-img424.~~com~~png]]</Xol><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</~~InputCoordinateTransformation~~li>

[[File:pi3b-img425.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 UART test ===

~~orangepi@orangepi:~$~~ # UART7 and UART9 are enabled by default in Android. The position of the 40pin is shown in the figure below, and the corresponding device nodes are '''/dev/ttyS7''' and '''~~vim~~ /~~boot~~dev/~~orangepiEnv.txt~~ttyS9'''respectively

~~verbosity=1~~::[[File:pi3b-img269.png]]

~~'''bootlogo~~<ol start=~~false'''~~"2" style="list-style-type: decimal;"><li>First click on the wiringOP icon to open the wiringOP APP</li>

[[File:pi3b-img418.png]]

</ol>

<li>~~Set~~ The main interface of wiringOP APP is displayed as shown in the figure below, and then click the '''~~bootlogo''' variable to '''true''' in '''/boot/orangepiEnv.txt~~UART_TEST''' button to ~~enable~~ open the ~~switch logo~~UART test interface</li~~></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''vim~~ pi3b-img426.png]]</~~boot~~ol><ol start="4" style="list-style-type: decimal;"><li>The serial port test interface of the APP is shown in the figure below</~~orangepiEnv.txt'''~~li>

~~verbosity~~[[File:pi3b-img427.png]]</ol><ol start=1"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>

~~'''bootlogo~~[[File:pi3b-img428.png]]</ol><ol start=~~true'''~~"6" style="list-style-type: decimal;"><li>Then use Dupont wire to short the RXD and TXD pins of uart7</li>

[[File:pi3b-img429.png]]</ol><ol start="47" style="list-style-type: decimal;"><li>~~The location of~~ Then you can enter a character in the ~~boot logo image in~~ send edit box below, and click the ~~Linux system is~~'''SEND''' button to start sending</li~~></ol~~>

~~'''/usr/share/plymouth/themes~~[[File:pi3b-img430.png]]</~~orangepi~~ol><ol start="8" style="list-style-type: decimal;"><li>If everything is normal, the received string will be displayed in the receiving box</~~watermark.png'''~~li>

[[File:pi3b-img431.png]]</ol ~~start~~>~~<li>After replacing the boot logo picture, you need to run the following command to take effect~~</~~li></ol~~span>

~~orangepi@orangepi:~$ '''sudo update-initramfs -u'''~~=== 40pin SPI test ===

~~== How to use~~ schematic diagram of the 40pin interface, the ~~ZFS file system ==~~spi available for Orange Pi 3B is spi3

~~'''The latest version of Ubuntu20.04, Ubuntu22.04, Debian11 and Debian12 desktop version systems have pre~~::[[File:pi3b-~~installed zfs, you can use it directly~~img264.~~'''~~png]]

~~'''The pre~~<ol start="2" style="list-style-~~installed zfs version in Ubuntu20.04 and Ubuntu22~~type: decimal;"><li>Here, the SPI interface is tested through the w25q64 module.~~04 desktop systems~~ First, the w25q64 device is ~~2.1.6.'''~~connected to the SPI3 interface</li>

~~'''The pre~~[[File:pi3b-~~installed zfs version in Debian11 and Debian12 desktop systems is 2~~img432.~~1.11.'''~~png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then click the wiringOP icon to open the wiringOP APP</li>

~~'''After the system starts, please first confirm whether the zfs kernel module has been loaded~~[[File:pi3b-img418. ~~If you can see zfs~~png]]</ol><ol start="4" style="list-style-~~related content using~~ type: decimal;"><li>The main interface of wiringOP APP is displayed as shown in the ~~lsmod command~~figure below, ~~it means that~~ click the SPI_TEST button to open the ~~system has pre-installed zfs.'''~~SPI test interface</li>

~~orangepi@orangepi~~[[File:~$ pi3b-img433.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then click the '''~~lsmod | grep "zfs"~~OPEN'''button to initialize the SPI</li>

~~zfs 2801664~~ [[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 '''TRANSFER''' button</li>

~~zunicode 327680 1 zfs~~[[File:pi3b-img435.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Finally, the APP will display the read ID information</li>

~~zzstd 471040 1 zfs~~[[File:pi3b-img436.png]]</ol><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>

~~zlua 139264 1 zfs~~[[File:pi3b-img437.png]]</ol>

~~zcommon 69632 1 zfs~~=== 40pin PWM test ===

~~znvpair 61440 2 zfs~~# Android enables '''PWM11''' by default,~~zcommon~~and the corresponding pin is located at 40pin as shown in the figure below

~~zavl 16384 1 zfs~~::[[File:pi3b-img438.png]]

~~icp 221184 1 zfs~~<ol start="2" style="list-style-type: decimal;"><li>First click on the wiringOP icon to open the wiringOP APP</li>

~~spl 77824 6 zfs,icp,zzstd,znvpair,zcommon,zavl~~[[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>

[[File:pi3b-img439.png]]<~~span id~~/ol><ol start="~~how-to~~4" style="list-~~install~~style-~~zfs~~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</~~span~~li>~~=== How to install ZFS ===~~

[[File:pi3b-img440.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>When the drop-down option selects '''pwmchip3'''~~Before installing zfs~~, ~~please make sure that~~ the ~~Linux image used~~ corresponding base address of PWM11 is ~~the latest version. In addition, if zfs is already installed in the system, it needs to be installed again.~~'''fe6f0030''' on the right</li>

~~Before installing zfs~~[[File:pi3b-img441.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then confirm the PWM channel, ~~you need to install~~ the ~~kernel header file first. For~~ default is channel 0, and confirm the ~~method of installing~~ PWM cycle, the ~~kernel header file~~default configuration is '''50000ns''', ~~please refer~~ converted to PWM frequency is '''20KHz''', you can modify it yourself, click the ~~instructions in the [[\l|~~'''~~section on the method of installing the kernel header file~~EXPORT''' button to export '''PWM11'''~~]].~~</li>

~~In Ubuntu20~~[[File:pi3b-img442.04png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Then drag the drag bar below to change the PWM duty cycle, ~~Ubuntu22.04~~ and ~~Debian11 systems, zfs cannot be installed directly through apt, because~~ then check Enable to output 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.~~PWM waveform</li>

~~To solve this problem, we provide a zfs deb package that can be installed normally, which can be downloaded from the~~ [~~http~~[File:~~//www~~pi3b-img443.~~orangepi.org~~png]]</~~html/serviceAndSupport/index.html '''official tool'''] of the development board. Open the '''~~ol><~~span class~~ol start="~~mark~~8"~~>official tool''', and enter the '''~~zfs-related deb package folders used by Ubuntu and Debian systems~~<~~/span~~li>~~'''~~Then use an oscilloscope to measure the No. ~~You can see three types~~ 32 pin in the 40pin of ~~deb packages: Ubuntu20.04~~the development board, ~~Ubuntu22.04~~ and ~~Debian11. Please download~~ you can see the ~~required version.following waveform</li>

[[File:pi3b-~~img368~~img444.png~~|230x93px~~]]</ol>

~~After downloading the zfs deb packages of the corresponding version, please upload them~~ == How to the Linux system of the development board. For the upload method, please refer to '''[[\l|the description in the section of the method of uploading files to the Linux system of the development board]].'''use ADB ==

~~After the upload is complete,~~ <span id="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.~~-network-connection-adb-debugging">=== Use network connection adb debugging ===

~~orangepi@orangepi~~{| class="wikitable" style="background-color:~$ #ffffdc;width:800px;" |-| <big>'''sudo apt install ./*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.~~deb~~'''</big>|}

~~After~~ # Make sure that the ~~installation~~ '''service.adb.tcp.port''' of the Android system is ~~complete, use the following command~~ set to ~~see the zfs-related kernel modules:~~port number 5555

~~orangepi@orangepi~~:~$ :{| class="wikitable" style="width:800px;" |-| console:/ # '''~~ls /lib/modules/5.10~~getprop | grep "adb.~~160-rockchip-rk356x/updates/dkms/~~tcp"'''

[service.adb.tcp.port]: ['''~~icp.ko spl.ko zavl.ko zcommon.ko zfs.ko zlua.ko znvpair.ko zunicode.ko zzstd.ko~~5555''']|}

~~Then restart~~ <ol start="2" style="list-style-type: decimal;"><li>If '''service.adb.tcp.port''' is not set, you can use the ~~Linux system~~ following command to ~~see that~~ set the ~~zfs kernel module will be automatically loaded:~~port number of network adb</li>

~~orangepi@orangepi~~{| class="wikitable" style="width:800px;" |-| console:~$ / # '''~~lsmod | grep "zfs"~~setprop service.adb.tcp.port 5555'''

~~zfs 2801664 0~~console:/ # '''stop adbd'''

~~zunicode 327680 1 zfs~~console:/ # '''start adbd'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Install adb tool on Ubuntu PC</li>

~~zzstd 471040 1 zfs~~{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt update'''

~~zlua 139264 1 zfs~~test@test:~$ '''sudo apt install -y adb'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then connect network adb on Ubuntu PC</li>

~~zcommon 69632~~ {| class="wikitable" style="width:800px;" |-| test@test:~$ '''adb connect 192.168.1 ~~zfs~~.xxx''' '''(The IP address needs to be changed to the IP address of the development board)'''

~~znvpair 61440 2 zfs,zcommon~~* daemon not running; starting now at tcp:5037

~~zavl 16384 1 zfs~~* daemon started successfully

~~icp 221184~~ connected to 192.168.1 ~~zfs~~.xxx:5555

~~spl 77824 6 zfs,icp,zzstd,znvpair,zcommon,zavl~~

In Debian12, the default version of zfs is 2.1.11, so we can install zfs directly through the following command. Again, please make sure that the system has installed the deb package of the kernel header file before installation.test@test:~$ '''adb devices'''

~~orangepi@orangepi:~$ '''sudo apt install -y zfsutils-linux zfs-dkms'''~~List of devices attached

192.168.1.xxx:5555 device|}</ol><~~span id~~ol start="~~methods~~5" style="list-ofstyle-~~creating-zfs-pools~~type: decimal;"><li>Then you can log in to the android system through the adb shell on the Ubuntu PC</~~span~~li>~~=== Methods of creating ZFS pools ===~~

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''~~ZFS is based on storage pools, we can add multiple physical storage devices to the pool, and then allocate storage space from this pool.~~adb shell'''

~~'''The following content is demonstrated based on the development board connected to an NVMe SSD and a USB flash drive.'''~~console:/ #|}</ol>

~~# First, we can use the~~ = '''~~lsblk~~Appendix''' ~~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~~== User Manual Update History ==

~~<ol start~~{| class="2wikitable" style="~~list-style~~width:800px;text-~~type~~align: ~~decimal~~center;">~~<li>Then enter the following command to create a ZFS pool, including two storage devices, NVMe SSD and U disk</li></ol>~~|-|'''Version'''|'''Date'''|'''Update Notes'''|-|v0.1|2023-07-19|initial version|}

~~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: left;"| '''u-boot version'''| style="text-align: left;"| '''Linux Kernel version'''~~|-~~| style="text-align: left;"| '''legacy'''| style="text-align: left;"| '''u-boot 2017.09'''| 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''': 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'''</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"~~|-~~| style="text-align: left;"| '''Version'''| style="text-align: left;"| '''Date'''| style="text-align: left;"| '''Update Notes'''~~|-~~| style="text-align: left;"| v0.1| style="text-align: left;"| 2023-07-19| style="text-align: left;"| initial version~~|}

== 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 ^β