Changes

← Older edit

Orange Pi Zero 3

39,519 bytes added, 10:19, 19 July 2023

→‎How to install Debian system

== Hardware Features of Orange Pi Zero 3 ==

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

|-

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

|-

| Onboard storage

| TF micro SD card slot, 16MB SPI Flash

|-

| Ethernet

| WIFI+Bluetooth

|

* AW859A chip, support IEEE 802.11 a/b/g/n/ac, BT5.0

|-

| Video Output

|

* Micro HDMI 2.0a

* TV CVBS output, support PAL/NTSC (via 13pin expansion board)

|-

| Audio output

|

* Micro HDMI output

* 3.5mm audio port (via 13pin expansion board)

|-

| USB 2.0 port

| 3 * USB 2.0 HOST (two of them are through 13pin expansion board)

|-

| 26pin connector

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

[[File:~~media/image3~~zero3-img3-1.png~~|390x329px~~]]

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

[[File:~~media/image4~~zero3-img4.png~~|494x292px~~]]

== Interface details of Orange Pi Zero 3 ==

[[File:~~media/image5~~zero3-img5.png~~|485x787px~~]]

[[File:~~media/image6~~zero3-img6.png~~|575x227px~~]]

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

== Prepare the required accessories ==

# TF Micro SD card, a high-speed SanDisk card of class 10 or above with a minimum capacity of 8GB

::[[File:~~media/image7~~zero3-img7.png~~|124x96px~~]]

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

|-

|

<big>'''Using other brands of TF micro SD cards (non-SanDisk TF micro SD cards), as shown in the picture below (including but not limited to these cards), some friends have reported that there will be problems during the system startup process, such as the system is stuck halfway through startup, Or the reboot command cannot be used normally, and it was finally resolved after changing the SanDisk TF micro SD card. So if you use a non-SanDisk TF micro SD card and find that there is a problem with the system startup or use, please replace the SanDisk TF micro SD card and then test.'''</big>

[[File:~~media/image8~~zero3-img8.png|~~103x85px~~180px]][[File:~~media/image9~~zero3-img9.png|~~112x85px~~195px]][[File:~~media/image10~~zero3-img10.png|~~114x85px~~198px]][[File:~~media/image11~~zero3-img11-1.png|~~86x109px~~190px]]

'''Current feedback is that there are some TF micro SD cards that have problems starting on Orange Pi Zero 3'''

<big>'''In addition, the TF micro SD card that can be used normally on other types of development boards does not guarantee that it can be started normally on Orange Pi Zero 3, please pay special attention to this point.'''</big>

|}

<li>TF micro SD card reader, used to read and write TF micro SD card</li>~~</ol>~~ ~~[[File:media/image12.png|139x96px]]~~

[[File:zero3-img12.png]]

</ol>

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

[[File:~~media/image13~~zero3-img13.png~~|215x222px~~]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note, please do not use the relatively wide Micro HDMI adapter as shown in the figure below, because the distance between the Micro HDMI interface of the development board and the Type-C power interface is relatively small, it may cause that the two cannot be inserted into the development board at the same time. plate.''' ~~[[File:media~~</~~image14.png|151x120px]]~~big>

[[File:zero3-img14.png|center]]

|}

</ol>

<li>Power supply, if you have a 5V/2A or 5V/3A power head, you only need to prepare a USB-to-Type C interface data cable as shown in the picture on the left below, and you can also use a cable similar to the picture on the right below A 5V/2A or 5V/3A high-quality USB Typc C interface power adapter integrated with the power head.</li>~~</ol>~~ ~~[[File:media/image15.png|217x223px]] [[File:media/image16.png|218x218px]]~~

[[File:zero3-img15.png]] [[File:zero3-img16.png]]

</ol>

<li>13pin expansion board

<li>The physical object of the expansion board is as follows</li>~~</ol></li></ol>~~ ~~[[File:media/image17.png|252x154px]]~~

[[File:zero3-img17-1.png]]

</ol>

<li>The way to insert the expansion board into the development board is as follows, remember not to insert it backwards</li>~~</ol>~~ ~~[[File:media/image18.png|246x162px]]~~

[[File:zero3-img18.png]]

</ol>

<li>The 13pin pin header on the Orange Pi Zero 3 development board can be connected to the expansion board to expand the functions that are not on the development board. The functions that the expansion board can use are as follows</li~~></ol~~>

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

|-

'''The 13pin expansion board is a general-purpose expansion board, which is suitable for various development boards of Orange Pi, but the 13pin interface of Orange Pi Zero3 has no Mic function, so although there is a Mic on the 13pin expansion board, it is on the Orange Pi Zero 3. Unusable, the 13pin expansion board is mainly used to expand functions other than Mic on Orange Pi Zero 3.

|-

| style="text-align: ~~left~~center;"| 2| style="text-align: ~~left~~center;"| Analog audio and video output interface| style="text-align: ~~left~~center;"| Supported, it can be used to connect headphones to play music, or connect to TV through AV cable to output analog audio and video signals '''(Android system only).'''

|-

|-

|}

</ol>

<li>The schematic diagram of the 13pin header of the Orange Pi Zero 3 development board is shown below</li>~~</ol>~~ ~~[[File:media/image19.png|264x142px]]~~

[[File:zero3-img19.png]]

</ol>

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

<li>Infrared remote control, mainly used to control Android TV system</li~~></ol~~>

[[File:~~media/image20~~zero3-img20.png~~|170x173px~~]] ~~'''Note that the remote control of the air conditioner or the remote control of the TV cannot control the Orange Pi development board. By default, only the remote control provided by Orange Pi can.'''~~

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

|-

|

<big>'''Note that the remote control of the air conditioner or the remote control of the TV cannot control the Orange Pi development board. By default, only the remote control provided by Orange Pi can.'''</big>

|}

</ol>

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

<li>AV video cable, if you want to display video through the AV interface instead of the HDMI interface, then you need to connect the development board to the TV through the AV video cable</li>~~</ol>~~ ~~[[File:media/image21.png|217x218px]]~~

[[File:zero3-img21.png]]

</ol>

<li>Heat sink, if you are worried that the temperature of the development board is too high, you can add a heat sink, and the heat sink can be pasted on the H618 chip</li>~~</ol>~~ ~~[[File:media/image22.png|171x140px]] [[File:media/image23.png|151x147px]]~~

[[File:zero3-img22.png]] [[File:zero3-img23-1.png]]

</ol>

<li>5V cooling fan, as shown in the figure below, both 5V and GND pins on the 26pin and 13pin interfaces of the development board can be connected to the cooling fan. The spacing between the 26pin and 13pin headers is 2.54mm. Refer to this Specifications can be purchased.</li~~></ol~~>

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the 5V pin can be used directly after the development board is plugged in without other settings, and the output voltage of the 5V pin cannot be adjusted or turned off by software.'''</big> ~~[[File:media/image24.png~~|~~212x226px]]~~}

[[File:zero3-img24-1.png]]

</ol>

<li>Matching shell '''(pictures to be added)'''</li>

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

[[File:~~media/image25~~zero3-img25-1.png~~|176x118px~~]] [[File:~~media/image26~~zero3-img26.png~~|305x110px~~]] ~~'''Note that the TTL level used by the development board is 3.3v. In addition to the USB to TTL module shown in the above figure, other similar 3.3v USB to TTL modules are generally available.'''~~

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

|-

|

<big>'''Note that the TTL level used by the development board is 3.3v. In addition to the USB to TTL module shown in the above figure, other similar 3.3v USB to TTL modules are generally available.'''</big>

|}

</ol>

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

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

|-

|-

|}

</ol>

# The website for downloading the English version is

::{| class="wikitable" style="width:800px;" |-| [http://www.orangepi.org/~~downloadresources~~html/hardWare/computerAndMicrocontrollers/service-and-support/ Orange-Pi-Zero-3.html '''http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Zero-3.html''']|}

<li>The information mainly includes

<li>'''Android''' '''source code'''： : Save on Google Drive</li><li>'''Linux''' '''source code'''~~：Save~~ :Save on Github</li><li>'''Android''' '''source code'''~~：Save~~ :Save on Google Drive</li><li>'''Ubuntu''' '''source code'''~~：Save~~ :Save on Google Drive</li><li>'''Debian''' '''source code'''~~：Save~~ :Save on Google Drive</li><li>'''User Manual and ~~Schematic：~~Schematic:'''Chip-related data sheets will also be placed here</li><li>'''Official ~~tool：~~tool:'''It mainly includes the software that needs to be used during the use of the development board</li></ol>

</li></ol>

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

== Method of burning Linux image to micro SD 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 image of Linux distributions such as Debian or Ubuntu downloaded from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Zero-3.html Orange Pi data download page].'''</big>|}

=== How to use balenaEtcher to burn Linux image ===

# First prepare a TF micro SD card with a capacity of 8GB or more. The transmission speed of the TF micro SD card must be '''class 10 or above'''. It is recommended to use a TF micro SD card of SanDisk and other brands# Then use the card reader to insert the TF micro SD 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/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Zero-3.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 1GB

# Then download the burning software of Linux image——'''balenaEtcher,''' 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:media/image27.png|456x219px]]~~

[[File:zero3-img27.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:media/image28.png|468x173px]]~~

[[File:zero3-img28.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 opened balenaEtcher interface is shown in the figure below</li~~></ol~~>

[[File:~~media/image29~~zero3-img29.png~~|335x211px~~]]

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

[[File:~~media/image30~~zero3-img30.png|~~206x162px~~center]]

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

[[File:zero3-img31-1.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 micro SD card</li><li>Finally click Flash to start burning the Linux image to the TF micro SD card[[File:~~media/image32~~zero3-img32.png~~|501x281px|03~~]]~~~~</li></ol>

</li>

<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 micro SD card</li>~~</ol>~~ ~~[[File:media/image33.png|506x317px]]~~

[[File:zero3-img33.png]]

</ol>

<li>After burning the Linux image, balenaEtcher will also verify the image burned to the TF micro SD 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:media/image34.png|519x325px]]~~

[[File:zero3-img34.png]]

</ol>

<li>After successful burning, the display interface of balenaEtcher is as shown in the figure below. If the 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 micro SD card and insert it into the TF micro SD card slot of the development board. .</li~~></ol~~>

[[File:~~media/image35~~zero3-img35.png~~|523x324px|04~~]]

</div></ol>

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

<li>First prepare a TF micro SD card with a capacity of 8GB or more. The transmission speed of the TF micro SD card must be '''class 10 or above'''. It is recommended to use a TF micro SD card of SanDisk and other brands</li><li>Then use the card reader to insert the TF micro SD card into the computer</li><li>Then format the TF micro SD card

<li>'''SD Card Formatter'''can be used to format the TF micro SD card. The download link is</li~~></ol></li></ol~~>

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

|-

|

[https://www.sdcard.org/downloads/formatter/eula_windows/SDCardFormatterv5_WinEN.zip '''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 micro SD card is inserted into the computer, the drive letter of the TF micro SD 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 micro SD card through the drop-down box</li~~></ol~~>

[[File:~~media/image36~~zero3-img36.png~~|209x228px|选区_199~~]]

</div></ol>

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

[[File:zero3-img37.png]]

</ol>

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

~~<blockquote>~~[[File:~~media/image38~~zero3-img38.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/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Zero-3.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 1GB</li><li>Use Win32Diskimager to burn the Linux image to the TF micro SD card

<li>The download page of Win32Diskimager is</li~~></ol></li></ol~~>

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

|-

|

[http://sourceforge.net/projects/win32diskimager/files/Archive/ '''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 micro SD card is consistent with that displayed in the "'''Device'''" column</li><li>c) Finally click "'''Write'''" to start burning</li>~~</ol></li></ol>~~

[[File:~~media/image39~~zero3-img39.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 micro SD 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 ==~~

~~'''Note that the~~ == Method of burning Linux image ~~mentioned here specifically refers~~ to ~~the image of Linux distributions such as Debian or Ubuntu downloaded from the Orange Pi data download page, and the~~ micro SD card based on Ubuntu PC ~~refers to the personal computer with the Ubuntu system installed.'''~~==

{| 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 or Ubuntu downloaded from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Zero-3.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 micro SD card with a capacity of 8GB or more. The transmission speed of the TF micro SD card must be '''class 10 or above'''. It is recommended to use a TF micro SD card of SanDisk and other brands# Then use the card reader to insert the TF micro SD card into the computer

# 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:media/image27.png|489x235px]]~~

[[File:zero3-img27.png]]

</ol>

<li>Then choose to download the Linux version of the software</li>~~</ol>~~ ~~[[File:media/image40.png|485x184px]]~~

[[File:zero3-img40.png]]

</ol>

<li>Download the image file compression package of the Linux operating system that you want to burn from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Zero-3.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 1GB. The decompression command for the compressed package ending in 7z is as follows:</li~~></ol~~>

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

|-

|

test@test:~$ '''7z x orangepizero3_1.0.0_ubuntu_focal_desktop_linux6.1.31.7z'''

'''orangepizero3_1.0.0_ubuntu_focal_desktop_linux6.1.31.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 micro SD card. '''If it prompts that the checksum does not match''', it means ~~There~~ 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'''

orangepizero3_1.0.0_ubuntu_focal_desktop_linux6.1.31.img: '''success'''

|}</ol>

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

[[File:zero3-img41.png]]

</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 micro SD card</li><li>Finally click Flash to start burning the Linux image to the TF micro SD card</li~~></ol></li></ol~~>

[[File:~~media/image32~~zero3-img32.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 micro SD card</li> [[File:zero3-img42.png]]</ol><ol start="11" style="list-style-type: decimal;"><li>After burning the Linux image, balenaEtcher will also verify the image burned into the micro SD card by default to ensure that there is no problem in the burning process. As shown in the figure below, a green progress bar indicates that the image has been burnt, and balenaEtcher is verifying the burnt image</li>

[[File:~~media/image42~~zero3-img43.png~~|576x247px~~]]</ol><ol start="12" style="list-style-type: decimal;"><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 micro SD card and insert it into the micro SD card slot of the development board for use</li>

~~11)After burning the Linux~~ [[File:zero3-img44.png]]</ol><span id="how-to-burn-android-image~~, balenaEtcher will also verify the image burned into the TF~~ -to-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">

~~[[File:media/image43.png|576x252px]]~~== How to burn Android image to micro SD card ==

~~<ol start~~{| class="12wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~After successful burning, the display interface~~ '''The Android image 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~~ development board can ~~exit balenaEtcher, and then pull out~~ only be burned into the TF micro SD card under the Windows platform using the PhoenixCard software, and ~~insert it into~~ the ~~TF card slot~~ version of the ~~development board for use~~PhoenixCard software must be <~~/li~~span style="color:#FF0000">PhonixCard-4.2.8</olspan>.'''

~~[[File:media/image44~~'''Please do not use software for burning Linux images, such as Win32Diskimager or balenaEtcher, to burn Android images.~~png|576x340px]]~~'''

~~~~micro SD cards under Linux and Mac platforms.'''</~~span~~big>~~== How to burn Android image to TF card ==~~|}

# First, please make sure that the Windows system has installed '''~~The Android image of the development board can only be burned into the TF card under the Windows platform using the PhoenixCard software, and the version of the PhoenixCard software must be PhonixCard~~Microsoft Visual C++ 2008 Redistrbutable -~~4.2.8. Please do not use software for burning Linux images, such as Win32Diskimager or balenaEtcher, to burn Android images.~~x86'''

~~'''In addition, the PhoenixCard software does not have versions for Linux and Mac platforms, so it is impossible to burn Android images to TF cards under Linux and Mac platforms~~::[[File:zero3-img45.~~'''~~png]]

~~# First, please make sure that the Windows system has installed '''Microsoft Visual C++ 2008 Redistrbutable~~ <ol start="2" style="list-style- ~~x86'''[[File~~type:~~media/image45.png|449x293px]]~~decimal;"># <li>If not installed '''Microsoft Visual C++ 2008 Redistrbutable - x86''', Using PhoenixCard to format TF micro SD card or burn Android image will prompt the following error</li>

[[File:~~media/image46~~zero3-img46.png~~|522x395px|NUQB$Q%(){1CV6M6WK4N`5J~~]]

</div></ol>

<li>'''Microsoft Visual C++ 2008 Redistrbutable - x86''' the installation package can be downloaded from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Zero-3.html '''official tool''' ] of Orange Pi Zero 3, or you can go to the [https://www.microsoft.com/zh-cn/download/details.aspx?id=26368 '''official website of Microsoft''' ] to download</li>~~</ol>~~ ~~[[File:media/image47.png|242x52px]] [[File:media/image48.png|200x95px]]~~

[[File:zero3-img47.png]] [[File:zero3-img48.png]]

</ol>

<li>Then prepare a TF micro SD card with 8GB or larger capacity. The transmission speed of the TF micro SD card must be '''class 10 or above'''. It is recommended to use a TF micro SD card of SanDisk and other brands</li><li>Then use the card reader to insert the TF micro SD card into the computer</li><li>Download the Android image and PhoenixCard programming tool from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Zero-3.html '''Orange Pi data download page''']. '''Please ensure that the version of the PhonenixCrad tool is PhonixCard-4.2.8.''' Please do not use the PhonixCard software version lower than 4.2.8 to burn the Android image. There may be problems with the Android image flashed by this version of the PhonixCard tool</li>~~</ol>~~ ~~[[File:media/image49.png|575x169px]]~~

[[File:zero3-img49-1.png]]

</ol>

<li>Then use ~~the~~ decompression software to decompress ~~the compressed package of the downloaded Android image~~'''PhonixCard4. ~~Among the decompressed files, the file ending with "~~2.~~img" is the Android image file, and the size is more than 1GB~~8. ~~If you don't know how to decompress the compressed package of the Android image, you can install a~~ zip'''~~compression~~ , this software~~'''~~ does not need to ~~decompress~~ be installed, just find PhoenixCard in the ~~image.~~decompressed folder and open it</li>~~</ol>~~ ~~[[File:media/image50.png|438x158px]]~~

[[File:zero3-img51.png]]

</ol>

<li>~~Then use decompression software to decompress~~ After opening PhoenixCard, if the micro SD card is recognized normally, the drive letter and capacity of the micro SD card will be displayed in the middle list. '''~~PhonixCard4.2.8.zip~~Please make sure that the displayed drive letter is consistent with the drive letter of the micro SD card you want to burn'''. If there is no display, ~~this software does not need~~ you can try to ~~be installed~~unplug the micro SD card, ~~just find~~ or click the "'''Refresh Drive Letter'''" button in PhoenixCard ~~in the decompressed folder and open it~~</li>~~</ol>~~ ~~[[File:media/image51.png|576x113px]]~~

[[File:zero3-img52-1.png]]

</ol>

<li>After opening PhoenixCard, if the TF card is recognized normally, the drive letter and capacity of the TF card will be displayed in the middle list. '''Please make sure that the displayed drive letter is consistent with the drive letter of the TF card you want to burn'''. If there is no display, you can try to unplug the TF card, or click the "'''Refresh Drive Letter'''" button in PhoenixCard</li></ol> ~~[[File:media/image52.png|575x137px]]~~ ~~<ol start="10" style="list-style-type: decimal;">~~<li>After confirming the drive letter, format the TF micro SD card first, and click the "'''Recover Card'''" button in PhoenixCard (if the "'''Recover Card'''" button is gray and cannot be pressed, you can first click the "'''Refresh Drive Letter'''" button)</li~~></ol~~>

[[File:~~media/image53.jpeg|575x316px|C:\Users\orangepi\Desktop\用户手册插图\Zero3\未标题~~zero3-1img53.~~jpg未标题-1~~png]]

</div>

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If there is a problem with formatting, please try to unplug and insert the TF micro SD card and then test again. If the problem still exists after re-plugging and inserting the TF micro SD card, you can restart the Windows computer or try another computer.'''</big>|}</ol><ol start="1110" style="list-style-type: decimal;"><li>Then start to write the Android image into the TF micro SD card

<li>First select the path of the Android image in the "'''Firmware'''" column</li>

<li>Select "'''Activation Card'''" in "Card Type"</li>

<li>Then click the "'''burn card'''" button to start burning</li> [[File:zero3-img54-1.png]]</ol>

</li></ol>

~~[[File:media/image54.png|576x431px]]~~ <ol start="1211" style="list-style-type: decimal;"><li>After burning, the display of PhoenixCard is as shown in the figure below. At this time, click the "'''Close'''" button to exit PhoenixCard, and then you can pull out the TF micro SD card from the computer and insert it into the development board to start</li~~></ol~~>

[[File:~~media/image55~~zero3-img55-1.~~jpeg|575x358px|1~~png]]

</div>

'''After burning the Android system, the TF card can only see a 128 MB partition in Windows, and the displayed partition is as shown in the figure below (some computers may pop up more than 20 disk partitions, but only the 128 MB partition can be opened. partition), please note that this is normal, please do not think that the TF card is burned out. The reason for this is that the Android system has a total of more than 20 partitions, but most of them cannot be recognized normally in the Windows system. At this point, please safely unplug the TF card and insert it into the development board to start it.'''

~~[[File~~{| class="wikitable" style="background-color:~~media~~#ffffdc;width:800px;" |-| <big>'''After burning the Android system, the micro SD card can only see a 128 MB partition in Windows, and the displayed partition is as shown in the figure below (some computers may pop up more than 20 disk partitions, but only the 128 MB partition can be opened. partition), please note that this is normal, please do not think that the micro SD card is burned out. The reason for this is that the Android system has a total of more than 20 partitions, but most of them cannot be recognized normally in the Windows system. At this point, please safely unplug the micro SD card and insert it into the development board to start it.'''</~~image56.png|193x45px]]~~big>

~~'''After the Android system starts, use the following command to see the twenty or so partitions in the TF card~~[[File:~~'''~~zero3-img56.png|center]]

~~[[File~~<big>'''After the Android system starts, use the following command to see the twenty or so partitions in the micro SD card:~~media~~'''</~~image57.png|368x131px]]~~big>

~~'''Use the df~~ [[File:zero3-h command to see that the 16GB TF card has about 11 GB of space available after burning the Android system (more than 20 partitions will not be mounted to the Android system, focus on these to the partition)img57.~~'''~~png|center]]

~~[[File:media~~<big>'''Use the df -h command to see that the 16GB micro SD card has about 11 GB of space available after burning the Android system (more than 20 partitions will not be mounted to the Android system, focus on these to the partition).'''</~~image58.png|391x220px]]~~big>

[[File:zero3-img58.png|center]]

|}

</ol>

== Instructions for using the micro linux system in the onboard SPI Flash ==

There is a 16MB SPI Flash on the development board, and its location is shown in the figure below:

[[File:~~media/image59~~zero3-img59-1.png~~|285x185px~~]]

There is a tiny linux system programmed into SPI Flash by default, which is mainly used to prove that the development board can start normally. When you get the development board, you don't need to burn the system into the TF micro SD card, you only need to connect the Type-C power supply to the development board to start the micro linux system in the SPI Flash. The main functions of this system are:

<li>During the u-boot start-up phase, the red LED light will be lit, and after entering the kernel, the red LED light will be turned off and the green LED light will be set to flash;</li>

<li>If the development board is connected to an HDMI screen, after the system starts up, the command line interface of the micro-linux system can be seen on the HDMI screen;</li>

<li>If the development board is connected with a USB keyboard, some simple linux commands can be run on the command line, such as ls, cd, etc.</li></ol> Due to the limited functions of the tiny linux system in SPI Flash, if you want to use all the functions of the development board normally, please burn the linux image or Android image to the TF micro SD card, and then use it.</p~~></li></ol~~>

== Start the Orange Pi development board ==

# Insert the TF micro SD card with the burned image into the TF micro SD card slot of the Orange Pi development board

# The development board has a Micro HDMI interface, and the development board can be connected to a TV or HDMI display through a Micro HDMI to HDMI cable

# If you have purchased a 13pin expansion board, you can plug the 13pin expansion board into the 13pin interface of the development board

# Connect a high-quality power adapter with a 5V/2A (5V/3A is also available) USB Type C interface

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

'''Many unstable phenomena during the power-on and start-up process of the system are basically caused by power supply problems, so a reliable power adapter is very important. If you find that there is a phenomenon of continuous restart during the startup process, please replace the power supply or Type C data cable and try again.'''</big>|}

<li>Then turn on the switch of the power adapter, if everything is normal, the HDMI monitor can see the system startup screen at this time</li>

<li>If you want to view the output information of the system through the debugging serial port, please use the serial cable to connect the development board to the computer. For the connection method of the serial port, please refer to [[Orange Pi Zero 3#How to use the debugging serial port|'''the section on how to use the debugging serial port''']]</li></ol>

== How to use the debugging serial port ==

::[[File:~~media/image60~~zero3-img60-1.~~jpeg|552x110px|7~~png]]

</div>

<li>The corresponding relationship between GND, TX and RX pins of the debugging serial port of the development board is shown in the figure below</li>~~</ol>~~ ~~[[File:media/image61.png|328x185px]]~~

[[File:zero3-img61-1.png]]

</ol>

<li>The GND, TX and RX 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>Connect the GND of the USB to TTL module to the GND of the development board</li>

<li>The RX of the USB to TTL module is '''connected to the TX of the development board'''</li><li>Connect the TX of the USB '''to TTL module to the RX of the development board'''</li></ol>

</li>

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

[[File:~~media/image62~~zero3-img62.png~~|553x204px~~]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The TX and RX of the serial port need to be cross-connected. If you don’t want to carefully distinguish the order of TX and RX, you can connect the TX and RX of the serial port casually first. If there is no output from the test serial port, then exchange the order of TX and RX. One order is right.'''</big>|}</ol>

~~~~

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

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

# First, insert the USB-to-TTL module into the USB port of the Ubuntu computer. If the connection and identification of the USB-to-TTL module is normal, you can see the corresponding device node name under '''/dev''' on the Ubuntu PC. Remember this node name, and then set the serial port software will be used

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

|-

|

test@test:~$ '''ls /dev/ttyUSB*'''

'''/dev/ttyUSB0'''

|}

<li>Then use the following command to install putty on Ubuntu PC</li~~></ol~~>

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

|-

|

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

test@test:~$ '''sudo apt install -y putty'''

|}</ol>

<li>Then run putty, '''remember to add sudo permission'''</li~~></ol~~>

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

|-

|

test@test:~$ '''sudo putty'''

|}</ol>

<li>After executing the putty command, the following interface will pop up</li>~~</ol>~~ ~~[[File:media/image63.png|332x290px]]~~

[[File:zero3-img63.png]]

</ol>

<li>First select the setting interface of the serial port</li~~></ol~~>

[[File:~~media/image64~~zero3-img64.~~jpeg|337x297px|9~~png]]

</div></ol>

<li>Then set the parameters of the serial port

<li>Set '''Serial line to connect to'''to as '''dev/ttyUSB0''' (modify to the corresponding node name, usually /dev/ttyUSB0)</li>

<li>Set '''Speed(baud)''' to 115200 (the baud rate of the serial port)</li>

<li>Set '''Flow control''' as '''None'''</li~~></ol></li></ol~~>

[[File:~~media/image65~~zero3-img65-1.~~jpeg|398x352px|10~~png]]

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

<li>After setting the setting interface of the serial port, return to the Session interface

<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:~~media/image66~~zero3-img66.~~jpeg|375x333px|11~~png]]

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

<li>Then start the development board, and you can see the Log information output by the system from the opened serial port terminal</li~~></ol~~>

[[File:~~media/image67~~zero3-img67.png~~|376x249px~~]]</ol>

~~~~

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

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

<li>Download MobaXterm

<li>Download MobaXterm website as follows</li~~></ol></li></ol~~>

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

|-

|

[https://mobaxterm.mobatek.net/ '''https://mobaxterm.mobatek.net/''']

|}</ol>

<li>After entering the MobaXterm download page, click'''GET XOBATERM NOW!'''</li>~~</ol>~~ ~~[[File:media/image68.png|382x233px]]~~

[[File:zero3-img68.png]]

</ol>

<li>Then choose to download the Home version</li>~~</ol>~~ ~~[[File:media/image69.png|353x231px]]~~

[[File:zero3-img69.png]]

</ol>

<li>Then select the Portable version. After downloading, you don’t need to install it, just open it and use it</li~~></ol~~>

[[File:~~media/image70~~zero3-img70.png~~|322x175px|选区_232~~]]

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

<li>After downloading, use decompression software to decompress the downloaded compressed package, you can get the executable software of MobaXterm, and then double-click to open</li>~~</ol>~~ ~~[[File:media/image71.png|576x83px]]~~

[[File:zero3-img71.png]]

</ol>

<li>After opening the software, the steps to set up the serial port connection are as follows

<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 cannot see the port number, please use [http://weishi.360 .cn/qudongdashi/ '''360 Driver Master''' ] to scan and install the driver for the USB-to-TTL serial port chip</li>

<li>Select the baud rate of the serial port as '''115200'''</li>

<li>Finally click the "'''OK'''" button to complete the setup</li~~></ol></li></ol~~>

[[File:~~media/image72~~zero3-img72.~~jpeg|553x280px|12~~png]]

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

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

[[File:~~media/image73~~zero3-img73.~~jpeg|628x318px|13~~png]]

</div></ol>

== Instructions for using the 5v pin in the 26pin or 13pin 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 to use the 5V/2A or 5V/3A Type C interface power cord to plug into the Type C power interface of the development board for power supply. If you need to use the 5V pin in the 26pin or 13pin interface to power the development board, please make sure that the power cable 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>|}

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

::[[File:~~media/image74~~zero3-img74.~~jpeg|223x160px|图片4~~png]]

</div>

::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The power cord shown in the picture above can be bought on Amazon, please search and buy by yourself.'''</big>|}

<li>The USB A port of the power cord shown in the above figure needs to be plugged into the 5V/2A or 5V/3A power adapter connector ('''it is not recommended to plug into the USB port of the computer for power supply. If there are too many peripherals connected to the development board, use will be unstable''')</li>

<li>The red DuPont ~~line~~ wire needs to be plugged into the 5V pin of the 26pin or 13pin interface of the development board</li>

<li>The black Dupont wire needs to be inserted into the GND pin of the 26pin or 13pin interface</li>

<li>The positions of the 5V pin and GND pin of the 26pin and 13pin interfaces in the development board are shown in the figure below''', remember not to reverse the connection.'''</li> [[File:zero3-img24-1.png]]</ol>

</li></ol>

~~[[File:media/image24.png|163x174px]]~~

~~~~

== The method of using the 13pin interface of the development board to expand the USB interface ==

# If you have purchased a 13pin expansion board for Orange Pi, insert the expansion board into the 13pin interface of the development board to expand 2 USB interfaces

::[[File:~~media/image18~~zero3-img18.png~~|246x162px~~]]

<li>If there is no 13pin expansion board, you can use a 4pin 2.54mm DuPont to USB2.0 female cable to expand the USB interface. The specific method is as follows:

<li>First, you need to prepare a 4pin 2.54mm Dupont to USB2.0 female cable (this cable can be bought on ~~Taobao~~Amazon, please search and buy by yourself), as shown in the figure below:</li>~~</ol></li></ol>~~ ~~[[File:media/image75.png|208x162px]] [[File:media/image76.jpeg|237x165px|C:\Users\orangepi\Desktop\用户手册插图\Zero3\未标题-2.jpg未标题-2]]~~

[[File:zero3-img75-1.png]] [[File:zero3-img76.png]]

</ol>

<li>The schematic diagram of the 13pin interface is shown below</li>~~</ol>~~ ~~[[File:media/image19.png|265x142px]] [[File:media/image77.jpeg|219x152px|C:\Users\orangepi\Desktop\用户手册插图\Zero3\未标题-3.jpg未标题-3]]~~

[[File:zero3-img19.png]] [[File:zero3-img77.png]]

</ol>

<li>The wiring of USB2 is as follows</li>~~</ol>~~ ~~[[File:media/image78.png|256x189px]]~~

[[File:zero3-img78.png]]

</ol>

<li>The wiring of USB3 is as follows</li>~~</ol>~~ ~~[[File:media/image79.png|255x195px]]~~

[[File:zero3-img79.png]]

</ol>

<li>If you need to connect two USB devices to the 13pin interface at the same time, you will find that the 5V and GND pins on the 13pin interface are not enough. At this time, one of the USB devices can use the 5V and GND pins in the 26pin interface. The location is as shown in the figure below Shown:</li~~></ol~~>

[[File:~~media/image24~~zero3-img24-1.png~~|243x260px~~]]</ol></li></ol>

~~~~

= '''Instructions for use of Debian/Ubuntu Server and Xfce desktop system''' =

== Supported linux image types and kernel versions ==

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

|-

|-

|-

|-

|-

|-

|-

|}

After entering the download page of the corresponding development board on [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Zero-3.html '''the Orange Pi data download page'''], you can see the following download options. In the description below, the Ubuntu image and the Debian image are generally referred to as the Linux image.

[[File:~~media/image80~~zero3-img80.png~~|207x123px~~]]

The naming rules of Linux images are as follows:

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

|-

|

'''Development board model_version number_Linux distribution type_release code name_server or desktop_kernel version'''

|}

<li>'''The model of the development board'''~~：Both~~ :Both are '''orangepizero3'''. The model names of different development boards are generally different. Before burning the image, please make sure that the model name of the selected image matches the development board.</li><li>'''Version number'''~~：For~~ :For example, '''1.x.x''', this version number will increase with the update of the image function, and the last number of the version number of the Linux image on the development board is an even number.</li><li>'''Types of Linux distributions'''： : '''Ubuntu''' and '''Debian''' are currently supported. Since Ubuntu is derived from Debian, there is not much difference between the two systems in terms of usage. However, there are still some differences in the default configuration of some software and the use of commands. In addition, both Ubuntu and Debian have their own software warehouses supported by maintenance, and there are also some differences in the supported and installable software packages. These need to be experienced in person to have a deeper understanding. For more details, you can refer to the official documentation provided by Ubuntu and Debian.</li><li>'''Release code name'''： : Used to distinguish between different versions of a specific Linux distribution such as Ubuntu or Debian. Among them, both '''focal''' and '''jammy''' are Ubuntu distributions, focal means Ubuntu20.04, and jammy means Ubuntu22.04. The biggest difference between different versions is that the software in the software warehouse maintained by the new version of Ubuntu system is much better than that of the old version of Ubuntu system. The ones in it should be new, such as Python and GCC compilation tool chains. '''bullseye''' is the specific version code of Debian, bullseye means Debian11, and bookworm means Debian12.</li><li>'''Server or Desktop'''~~：It~~ :It is used to indicate whether the system has a desktop environment. If it is server, it means that the system does not have a desktop environment. The storage space and resources occupied by the image are relatively small, and the command line is mainly used to operate and control the system. If it is '''desktop_xfce''', it means that the system is installed with the XFCE desktop environment by default. The storage space and resources occupied by the image are relatively large. You can connect the monitor, mouse and keyboard to operate the system through the interface. Of course, the desktop version of the system can also be operated through the command line like the server version of the system.</li><li>'''Kernel version'''~~：Used~~ :Used to indicate the version number of the linux kernel, currently supports '''linux5.4''' and '''linux6.1.'''</li></ol>

== Linux kernel driver adaptation ==

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

|-

|-

|-

|-

|-

|-

|-

|-

|-

|-

|-

|-

|-

|-

|-

|-

|-

| style="text-align: ~~left~~center;"| '''PWM'''| style="text-align: ~~left~~center;"| '''OK'''| style="text-align: ~~left~~center;"| '''OK'''

|-

|-

|-

|-

|-

|}

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

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

~~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="width:800px;height: 50px;" |-|

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

~~'''orangepi@orangepi~~:~~~$ sudo apt update'''~~: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: 50px;" |-| |}<ol start="2" style="list-style-type: decimal;"><li>Description of the prompt type in front of the command<ol style="list-style-type: lower-alpha;"><li>The prompt in front of the command refers to the content of the red part in the box below, which is not part of the linux command, so when entering the command in the linux system, please do not enter the content of the red font part.</li> {| class="wikitable" style="width:800px;" |-| '''~~root~~orangepi@orangepi:~~~#''' '''vim~~ $</~~boot/boot.cmd~~span> sudo apt update'''

'''~~test~~root@~~test~~orangepi:~~~$ ssh [mailto:root@192.168.1.36 root@192.168.1~~#''' '''vim /boot/boot.~~]xxx~~cmd'''

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

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

|}

</ol>

<li>'''root@orangepi:~$''' The prompt indicates that this command is entered in the '''linux system of the development board'''. The '''$''' at the end of the prompt indicates that the current user of the system is a normal user. When executing a privileged command, you need to add '''sudo'''</li><li>'''root@orangepi:~#''' The prompt indicates that this command is entered in the linux system of the development board, and the '''#''' at the end of the prompt indicates that the current user of the system is the root user, who can execute any desired command</li><li>'''test@test:~$''' The prompt indicates that this command is entered in the Ubuntu PC or Ubuntu virtual machine, not in the linux system of the development board. The '''$ ''' at the end of the prompt indicates that the current user of the system is an ordinary user. When executing privileged commands, '''sudo''' needs to be added</li><li>'''root@test:~#''' The prompt indicates that this command is entered in the Ubuntu PC or Ubuntu virtual machine, not in the linux system of the development board. The '''#''' at the end of the prompt indicates that the current user of the system is the root user and can execute any command you want</li></ol></li></ol>

<li>What are the commands that need to be entered?

<li>As shown below, '''the black bold part''' is the command that needs to be input, and the content below the command is the output content (some commands have output, some may not), and this part of the content does not need to be input</li~~></ol~~>~~</li></ol>~~{| class="wikitable" style="width:800px;" |-|

root@orangepi:~# '''cat /boot/orangepiEnv.txt'''

'''verbosity=7'''

bootlogo=false

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

<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~~ don't miss it</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-|

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

'''$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null'''

|}

</ol>

</li></ol>

~~~~

== Linux system login instructions ==

=== Linux system default login account and password ===

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

|-

| style="text-align: ~~left~~center;"| '''Account'''| style="text-align: ~~left~~center;"| '''password'''

|-

| style="text-align: ~~left~~center;"| '''root'''| style="text-align: ~~left~~center;"| '''orangepi'''

|-

| style="text-align: ~~left~~center;"| '''orangepi'''| style="text-align: ~~left~~center;"| '''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>'''When the wrong password is prompted, or there is a problem with the ssh connection, please note that as long as you are using the Linux image provided by Orange Pi, please do not suspect that the above password is wrong, but look for other reasons.'''</big>|}

=== How to set automatic terminal login in linux system ===

# The Linux system automatically logs in to the terminal by default, and the default login user name is '''orangepi'''

::[[File:~~media/image81~~zero3-img81.png~~|475x240px~~]]

<li>Use the following command to set the root user to automatically log in to the terminal</li~~></ol~~>

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

|-

|

orangepi@orangepi:~$ '''sudo auto_login_cli.sh root'''

|}</ol>

<li>Use the following command to disable automatic login terminal</li~~></ol~~>

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

|-

|

orangepi@orangepi:~$ '''sudo auto_login_cli.sh -d'''

|}</ol>

<li>Use the following command to set the orangepi user to automatically log in to the terminal again</li~~></ol~~>

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

|-

|

orangepi@orangepi:~$ '''sudo auto_login_cli.sh orangepi'''

|}

</ol>

~~~~

=== Instructions for automatic login of linux desktop version system ===

::[[File:~~media/image82~~zero3-img82.png~~|576x324px|1~~]]

</div>

<li>Run the following command to prohibit the desktop system from automatically logging into the desktop</li~~></ol~~>

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

|-

|

orangepi@orangepi:~$ '''sudo disable_desktop_autologin.sh'''

|}</ol>

<li>Then restart the system and a login dialog box will appear, at which point a [[Orange Pi Zero 3#Linux system default login account and password|'''Linux system default login account and password''' ]] is required to enter the system</li~~></ol~~>

[[File:~~media/image83~~zero3-img83.png~~|569x320px|IMG_256~~]]

</div></ol>

=== The setting method of root user automatic login in Linux desktop version system ===

# Execute the following command to set the desktop system to automatically log in as the root user

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

|-

|

orangepi@orangepi:~$ '''sudo desktop_login.sh root'''

|}

<li>Then restart the system, and the root user will automatically log in to the desktop</li~~></ol~~>

[[File:~~media/image84~~zero3-img84.png~~|294x123px~~]]

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

~~'''Also note that this is not a bug, since pulseaudio is not allowed to run as root.'''~~

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

|}

</ol>

<li>Execute the following command to set the desktop system to log in automatically with the orangepi user again</li~~></ol~~>

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

|-

|

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

|}

</ol>

~~~~

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

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

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

|-

|

orangepi@orangepi:~$ '''sudo systemctl disable lightdm.service'''

|}

<li>Then restart the Linux system and you will find that the desktop will not be displayed</li~~></ol~~>

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

|-

|

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

|}</ol>

<li>The command to reopen the desktop is as follows，'''Please remember to add sudo permission'''</li~~></ol~~>

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

|-

|

orangepi@orangepi:~$ '''sudo systemctl start lightdm.service'''

orangepi@orangepi:~$ '''sudo systemctl enable lightdm.service'''

|}

</ol>

~~~~

== Onboard LED Light Test Instructions ==

# There are two LED lights on the development board, one is green and the other is red. When the system starts, the default display of the LED lights is as follows:

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

|-

|

| style="text-align: ~~left~~center;"| '''Green light'''| style="text-align: ~~left~~center;"| '''Red light'''

|-

| '''u-boot startup phase'''

| style="text-align: ~~left~~center;"| '''off'''| style="text-align: ~~left~~center;"| '''on'''

|-

| '''The kernel boots into the system'''

| style="text-align: ~~left~~center;"| '''闪烁flashing'''| style="text-align: ~~left~~center;"| '''off'''

|-

| '''GPIO interface'''

| style="text-align: ~~left~~center;"| '''PC13'''| style="text-align: ~~left~~center;"| '''PC12'''

|}

::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The two LED lights on the development board are controlled by software.'''

'''When you get the development board, you may find that even if the TF micro SD card with the system programmed is not inserted into the development board, the two LED lights will be on after the development board is connected to the power supply. This is because the 16MB on the development board SPI Flash will burn a miniature linux system by default when leaving the factory. This system will light up the red light during the u-boot startup phase. After entering the kernel, it will turn off the red light and set the green light to flash.'''

'''If the linux system in the SPI Flash is cleared, then the two LED lights on the development board will not light up after the power is turned on without inserting the TF micro SD card with the system programmed'''</big>|}

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

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the following operations should be performed under the root user.'''</big>|}

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

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

|-

|

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

|}</ol>

<li>The command to set the green light to stop flashing is as follows</li~~></ol~~>

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

|-

|

root@orangepi:/sys/class/leds/green_led# '''echo none > trigger'''

|}</ol>

<li>The command to set the green light to be on is as follows</li~~></ol~~>

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

|-

|

root@orangepi:/sys/class/leds/green_led# '''echo default-on > trigger'''

|}</ol>

<li>The command to set the green light to flash is as follows</li~~></ol~~>

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

|-

|

root@orangepi:/sys/class/leds/green_led# '''echo heartbeat > trigger'''

|}</ol></ol>

<li>The method of setting the red light on ~~and~~ /off and flashing is as follows:</li~~></ol~~>

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the following operations should be performed under the root user.'''</big>|}

<li>First enter the setting directory of the red light</li~~></ol~~>

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

|-

|

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

|}</ol>

<li>The command to set the red light to be on is as follows</li~~></ol~~>

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

|-

|

root@orangepi:/sys/class/leds/red_led# '''echo default-on > trigger'''

|}</ol>

<li>The command to set the flashing red light is as follows</li~~></ol~~>

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

|-

|

root@orangepi:/sys/class/leds/red_led# '''echo heartbeat > trigger'''

|}</ol>

<li>The command to set the red light to stop flashing is as follows</li~~></ol~~>

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

|-

|

root@orangepi:/sys/class/leds/red_led# '''echo none > trigger'''

|}</ol></ol>

<li>If you do not need the LED light to flash after booting, you can use the following method to turn off the green light flashing

<li>First run '''orangepi-config''', common users remember to add '''sudo''' permission</li~~></ol></li></ol~~>

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

|-

|

orangepi@orangepi:~$ '''sudo orangepi-config'''

|}</ol>

<li>Then select '''System'''</li>~~</ol>~~ ~~[[File:media/image85.png|398x194px]]~~

[[File:zero3-img85.png]]

</ol>

<li>Then select '''Hardware'''</li>~~</ol>~~ ~~[[File:media/image86.png|393x202px]]~~

[[File:zero3-img86.png]]

</ol>

<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 '''disable-leds'''</li>~~</ol>~~ ~~[[File:media/image87.png|397x35px]]~~

[[File:zero3-img87.png]]

</ol>

<li>Then selec '''<Save>'''</li>~~</ol>~~ ~~[[File:media/image88.png|397x92px]]~~

[[File:zero3-img88.png]]

</ol>

<li>Then select '''<Back>'''</li>~~</ol>~~ ~~[[File:media/image89.png|395x91px]]~~

[[File:zero3-img89.png]]

</ol>

<li>Then select '''<Reboot>'''to restart the system for the configuration to take effect</li>~~</ol>~~ ~~[[File:media/image90.png|374x187px]]~~

[[File:zero3-img90.png]]

</ol>

<li>After restarting and fully entering the system, you can see that the two LED lights on the development board will not light up</li></ol>

</li></ol>

~~~~== Instructions for operating the rootfs partition capacity of the linux system in the TF micro SD card ==

=== The first startup will automatically expand the capacity of the rootfs partition in the TF micro SD card ===

# <ol start="1" style="list-style-type: decimal;"><li>After burning the Linux image of the development board into the TF micro SD card, you can check the capacity usage of the TF micro SD card on the '''Ubuntu computer''', the steps are as follows:

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that this step does not affect the automatic expansion of the Linux system of the development board. Here I just want to explain how to check the capacity of the TF micro SD card after burning the Linux image on the TF micro SD card.'''</big>|}

<li>First install the gparted software on the Ubuntu computer</li~~></ol~~>

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

|-

|

test@test:~$ '''sudo apt install -y gparted'''

|}</ol>

<li>Then open gparted</li~~></ol~~>

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

|-

|

test@test:~$ '''sudo gparted'''

|}</ol>

<li>After opening gparted, you can select the TF micro SD card in the upper right corner, and then you can see the usage of the TF micro SD card capacity</li>~~</ol>~~ ~~[[File:media/image91.png|575x210px]]~~

[[File:zero3-img91.png]]

</ol>

<li>The figure above shows the situation of the TF micro SD card after burning the Linux desktop version system. It can be seen that although the total capacity of the TF micro SD card is 16GB (displayed as 14.84GiB in GParted), the rootfs partition (/dev/ sdc1) actually allocated only 4.05GiB, leaving 10.79GiB unallocated</li></ol></li></ol>

<li>Then you can insert the TF micro SD card that has burned the Linux system into the development board to start. When the TF micro SD card starts the Linux system for the first time, it will call the '''orangepi-resize-filesystem''' script automatically through the systemd service '''orangepi-resize-filesystem.service''' The expansion of the rootfs partition, '''so there is no need to manually expand the capacity'''</li><li>After logging in to the system, you can use the '''df -h''' command to check the size of the rootfs. If it is consistent with the actual capacity of the TF micro SD card, it means that the automatic expansion is running correctly.~~</li></ol>~~ ~~orangepi@orangepi:~$ '''df -h'''~~ ~~Filesystem Size Used Avail Use% Mounted on~~ ~~udev 430M 0 430M 0% /dev~~ ~~tmpfs 100M 5.6M 95M 6% /run~~ ~~'''/dev/mmcblk0p1 15G 915M 14G 7% /'''~~ ~~tmpfs 500M 0 500M 0% /dev/shm~~

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

|-

|

orangepi@orangepi:~$ '''df -h'''

Filesystem Size Used AvailUse% Mounted on

udev430M0430M 0% /dev

tmpfs 100M 5.6M 95M 6% /run

'''/dev/mmcblk0p1''''''15G''''''915M''''''14G''''''7% /'''

tmpfs 500M 0500M 0% /dev/shm

|}

</li></ol>

<li>After starting the Linux system for the first time, we can also remove the TF micro SD card from the development board and reinsert it into the '''Ubuntu computer''', and then use gparted to check the status of the TF micro SD card again, as shown in the figure below, the rootfs partition (/dev/ The capacity of sdc1) has been expanded to 14.69GiB</li~~></ol~~>

[[File:~~media/image92~~zero3-img92.png~~|575x211px~~]] '''It should be noted that the Linux system has only one partition in ext4 format, and does not use a separate BOOT partition to store files such as the kernel image, so there is no problem of expanding the BOOT partition.'''

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

|-

|

<big>'''It should be noted that the Linux system has only one partition in ext4 format, and does not use a separate BOOT partition to store files such as the kernel image, so there is no problem of expanding the BOOT partition.'''</big>

|}

</ol>

~~=== The method of prohibiting automatic expansion of the capacity of the rootfs partition in the TF card ===~~

~~# First burn~~ === The method of prohibiting automatic expansion of the ~~linux image~~ capacity of the ~~development board to the TF card on the '''Ubuntu computer''' (Windows not available), '''and then re-plug and insert the TF card'''# Then the Ubuntu computer will automatically mount the~~ rootfs partition of in the TF micro SD card~~. If the automatic mounting is normal, use the ls command to see the following output~~===

~~test@test~~# First burn the linux image of the development board to the micro SD card on the '''Ubuntu computer'''~~ls /media/test/opi_root~~(Windows not available), '''and then re-plug and insert the micro SD card'''# Then the Ubuntu computer will automatically mount the partition of the micro SD card. If the automatic mounting is normal, use the ls command to see the following output

::{| class="wikitable" style="width:800px;" |-| test@test:~$ '''ls /media/test/opi_root/'''bin    boot    dev    etc    home    lib    lost+found    media    mnt    opt    proc    root    run sbin    selinux    srv    sys    tmp    usr    var|}

<li>Then switch the current user to the root user on the Ubuntu computer</li~~></ol~~>

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

|-

|

test@test:~$ '''sudo -i'''

[sudo] ~~test 的密码：~~ ~~root@~~password for test:~~~'''#'''~~

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

|}

</ol>

<li>Then enter the root directory of the linux system in the TF micro SD card and create a new file named '''.no_rootfs_resize'''</li~~></ol~~>

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

|-

|

root@test:~# '''cd /media/test/opi_root/'''

'''.no_rootfs_resize'''

|}</ol>

<li>Then you can uninstall the TF micro SD card, and then pull out the TF micro SD card and insert it into the development board to start. When the linux system starts, when the file'''.no_rootfs_resize''' is detected in the '''/root''' directory, the rootfs will not be automatically expanded.</li><li>After entering the Linux system after prohibiting automatic expansion of rootfs, you can see that the total capacity of the rootfs partition is only 4GB (the image of the desktop version is tested here), which is much smaller than the actual capacity of the TF micro SD card, indicating that the automatic expansion of rootfs is prohibited.</li~~></ol~~>

{| class="wikitable" style="width:800px;"|-|orangepi@orangepi:~$ '''df -h'''Filesystem Size Used AvailUse% Mounted on udev925M 0925M 0% /dev tmpfs 199M 3.2M 196M 2% /run '''/dev/mmcblk0p1''''''4.0G ''''''3.2G ''''''686M ''''''83% /''' |}</ol><ol start="7" style="list-style-type: decimal;"><li>If you need to re-expand the capacity of the rootfs partition in the micro SD card, just execute the following command, and then restart the Linux system of the development board.</li>

~~Filesystem Size Used Avail Use% Mounted on~~ ~~udev 925M 0 925M 0% /dev~~ ~~tmpfs 199M 3.2M 196M 2% /run~~ ~~'''/dev/mmcblk0p1 4.0G 3.2G 686M 83% /'''~~ ~~<ol start~~{| class="7wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">~~<li>If you need to re~~|-~~expand the capacity of the rootfs partition in the TF card, just execute the following command, and then restart the Linux system of the development board.~~| <~~/li~~big>~~</ol>~~ '''Note, please execute the following commands under the root user.'''</big>|}

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

|-

|

root@orangepi:~# '''rm /root/.no_rootfs_resize'''

root@orangepi:~# '''sudo reboot'''

|}

After restarting, enter the Linux system of the development board again, and you can see that the rootfs partition has been expanded to the actual capacity of the TF micro SD card ~~root@orangepi:~# '''df -h'''~~ ~~Filesystem Size Used Avail Use% Mounted on~~ ~~udev 925M 0 925M 0% /dev~~ ~~tmpfs 199M 3.2M 196M 2% /run~~ ~~'''/dev/mmcblk0p1 15G 3.2G 12G 23% /'''~~

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

|-

|

root@orangepi:~$ '''df -h'''

Filesystem Size Used AvailUse% Mounted on

udev925M 0925M 0% /dev

tmpfs 199M 3.2M 196M 2% /run

'''/dev/mmcblk0p1''''''15G''''''3.2G ''''''12G ''''''23% /'''

|}

</ol>

~~=== The method of manually expanding the capacity of the rootfs partition in the TF card ===~~

~~'''If the total capacity of the TF card is large, such as 128GB, you do not want the rootfs partition~~ === The method of the Linux system to use all the capacity of the TF card, but only want to allocate a part of the capacity, such as 16GB, to the Linux system, and then the remaining capacity of the TF card can be used for other use. Then you can use the content introduced in this section to manually ~~expand~~ expanding the capacity of the rootfs partition in ~~TF.'''~~the micro SD card ===

{| class="wikitable" style="background-color:# ~~First burn~~ ffffdc;width:800px;" |-| <big>'''If the total capacity of the micro SD card is large, such as 128GB, you do not want the ~~linux image~~ rootfs partition of the ~~development board~~ Linux system to use all the TF capacity of the micro SD card on , but only want to allocate a part of the ~~'''Ubuntu computer''' (Windows not available)~~capacity, such as 16GB, to the Linux system, ~~'''~~and then ~~re-plug and insert~~ the TF remaining capacity of the micro SD card~~'''~~# can be used for other use. Then you can use the ~~Ubuntu computer will automatically mount~~ content introduced in this section to manually expand the ~~partition~~ capacity of the rootfs partition in TF ~~card~~. ~~If the automatic mounting is normal, use the ls command to see the following output~~'''</big>|}

~~test@test~~# First burn the linux image of the development board to the micro SD card on the '''Ubuntu computer'''~~ls /media/test/opi_root~~(Windows not available), '''and then re-plug and insert the micro SD card'''# Then the Ubuntu computer will automatically mount the partition of the micro SD card. If the automatic mounting is normal, use the ls command to see the following output

::{| class="wikitable" style="width:800px;" |-| test@test:~$ '''ls /media/test/opi_root/'''bin    boot    dev    etc    home    lib    lost+found    media    mnt    opt    proc    root    run sbin    selinux    srv    sys    tmp    usr    var|}

<li>Then switch the current user to the root user on the Ubuntu computer</li~~></ol~~>

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

|-

|

test@test:~$ '''sudo -i'''

[sudo] ~~test 的密码：~~ ~~root@~~password for test:~~~'''#'''~~

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

|}

</ol>

<li>Then enter the root directory of the linux system in the TF micro SD card and create a new file named '''.no_rootfs_resize'''</li~~></ol~~>

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

|-

|

root@test:~# '''cd /media/test/opi_root/'''

'''.no_rootfs_resize'''

|}</ol>

<li>Then install the gparted software on the Ubuntu computer</li~~></ol~~>

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

|-

|

test@test:~$ '''sudo apt install -y gparted'''

|}</ol>

<li>Then open gparted</li~~></ol~~>

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

|-

|

test@test:~$ '''sudo gparted'''

|}</ol>

<li>After opening gparted, you can select the TF micro SD card in the upper right corner, and then you can see the usage of the TF micro SD card capacity. The figure below shows the situation of the TF micro SD card after burning the Linux desktop version system. It can be seen that although the total capacity of the TF micro SD card is 16GB (displayed as 14.84GiB in GParted), the rootfs partition (/dev/sdc1) Only 4.05GiB were actually allocated, leaving 10.79GiB unallocated</li>~~</ol>~~ ~~[[File:media/image91.png|575x210px]]~~

[[File:zero3-img91.png]]

</ol>

<li>Then select the rootfs partition (/dev/sdc1)</li>~~</ol>~~ ~~[[File:media/image93.png|575x211px]]~~

[[File:zero3-img93.png]]

</ol>

<li>Click the right mouse button again to see the operation options shown in the figure below. If the TF micro SD card has been mounted, first you need to Umount the rootfs partition of the TF micro SD card</li>~~</ol>~~ ~~[[File:media/image94.png|436x298px]]~~

[[File:zero3-img94.png]]

</ol>

<li>Then select the rootfs partition again, click the right mouse button, and select '''Resize/Move''' to start expanding the size of the rootfs partition</li>~~</ol>~~ ~~[[File:media/image95.png|444x302px]]~~

[[File:zero3-img95.png]]

</ol>

<li>After the '''Resize/Move''' option is turned on, the following setting interface will pop up</li>~~</ol>~~ ~~[[File:media/image96.png|315x193px]]~~

[[File:zero3-img96.png]]

</ol>

<li>Then you can directly drag the location shown in the figure below to set the size of the capacity, or you can set the size of the rootfs partition by setting the number in '''New ~~sieze~~size(MiB)'''</li>~~</ol>~~ ~~[[File:media/image97.png|320x191px]]~~

[[File:zero3-img97.png]]

</ol>

<li>After setting the capacity, click '''Resize/Move''' in the lower right corner</li>~~</ol>~~ ~~[[File:media/image98.png|327x196px]]~~

[[File:zero3-img98.png]]

</ol>

<li>~~14)~~ After confirming that it is correct, click the green button shown in the figure below'''√'''</li>~~</ol>~~ ~~[[File:media/image99.png|392x270px]]~~

[[File:zero3-img99.png]]

</ol>

<li>~~15)~~ Then select'''Apply''', It it will officially start to expand the capacity of the rootfs partition</li>~~</ol>~~ ~~[[File:media/image100.png|399x116px]]~~

[[File:zero3-img100.png]]

</ol>

<li>After the expansion is completed, click '''Close''' to close</li>~~</ol>~~ ~~[[File:media/image101.png|399x172px]]~~

[[File:zero3-img101.png]]

</ol>

<li>Then you can pull out the TF micro SD card, insert it into the development board and start it up. After entering the Linux system of the development board, if you can see that the size of the rootfs partition is the same as the size set before, it means manual Expansion succeeded</li~~></ol~~>

{| class="wikitable" style="width:800px;"|-|root@orangepi:~# '''df -h'''Filesystem Size Used AvailUse% Mounted on udev925M 0925M 0% /dev tmpfs 199M 3.2M 196M 2% /run '''/dev/mmcblk0p1''''''7.7G ''''''3.2G ''''''4.4G ''''''42% /''' |}</ol>

~~Filesystem Size Used Avail Use% Mounted on~~=== How to reduce the capacity of the rootfs partition in the micro SD card ===

~~udev 925M 0 925M 0% /dev~~ ~~tmpfs 199M 3.2M 196M 2% /run~~ ~~'''/dev/mmcblk0p1 7.7G 3.2G 4.4G 42% /'''~~ ~~=== How to reduce the capacity of the rootfs partition in the TF card ===~~|-| <big>'''After configuring the application program or other development environment in the Linux system of the TF micro SD card, if you want to back up the Linux system in the TF micro SD card, you can use the method in this section to reduce the size of the rootfs partition first, and then start the backup.'''</big>|}

# First insert the TF micro SD card you want to operate in the '''Ubuntu computer''' (Windows not available)

# Then install the gparted software on the Ubuntu computer

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

|-

|

test@test:~$ '''sudo apt install -y gparted'''

|}

<li>Then ~~opengparted~~open gparted</li~~></ol~~>

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

|-

|

test@test:~$ '''sudo gparted'''

|}</ol>

<li>After opening gparted, you can select the TF micro SD card in the upper right corner, and then you can see the usage of the TF micro SD card capacity</li>~~</ol>~~ ~~[[File:media/image102.png|575x217px]]~~

[[File:zero3-img102.png]]

</ol>

<li>Then select the rootfs partition (/dev/sdc1)</li>~~</ol>~~ ~~[[File:media/image103.png|575x217px]]~~

[[File:zero3-img103.png]]

</ol>

<li>Click the right mouse button again to see the operation options shown in the figure below. If the TF micro SD card has been mounted, first you need to Umount the rootfs partition of the TF micro SD card</li>~~</ol>~~ ~~[[File:media/image104.png|400x274px]]~~

[[File:zero3-img104.png]]

</ol>

<li>Then select the rootfs partition again, click the right mouse button, and select '''Resize/Move''' to start setting the size of the rootfs partition</li>~~</ol>~~ ~~[[File:media/image105.png|399x273px]]~~

[[File:zero3-img105.png]]

</ol>

<li>After the'''Resize/Move''' option is turned on, the following setting interface will pop up</li>~~</ol>~~ ~~[[File:media/image106.png|315x188px]]~~

[[File:zero3-img106.png]]

</ol>

<li>Then you can directly drag the location shown in the figure below to set the size of the capacity, or you can set the size of the rootfs partition by setting the number in '''New ~~sieze~~size(MiB)'''</li>~~</ol>~~ ~~[[File:media/image97.png|318x190px]]~~

[[File:zero3-img97.png]]

</ol>

<li>After setting the capacity, click'''Resize/Move''' in the lower right corner</li>~~</ol>~~ ~~[[File:media/image98.png|327x196px]]~~

[[File:zero3-img98.png]]

</ol>

<li>After confirming that it is correct, click the green button shown in the figure below'''√'''</li>~~</ol>~~ ~~[[File:media/image99.png|392x270px]]~~

[[File:zero3-img99.png]]

</ol>

<li>Then select '''Apply''', and the expansion of the rootfs partition will officially start</li>~~</ol>~~ ~~[[File:media/image100.png|365x106px]]~~

[[File:zero3-img100.png]]

</ol>

<li>After the expansion is completed, click '''Close''' to close</li>~~</ol>~~ ~~[[File:media/image101.png|379x164px]]~~

[[File:zero3-img101.png]]

</ol>

<li>Then you can pull out the TF micro SD card, insert it into the development board and start it up. After entering the Linux system of the development board, if you can use the '''df -h''' command to see that the size of the rootfs partition is the same as the size set before, it means that the size has been reduced. capacity success</li~~></ol~~>

{| class="wikitable" style="width:800px;"|-|root@orangepi:~# '''df -h'''Filesystem Size Used AvailUse% Mounted on udev925M 0925M 0% /dev tmpfs 199M 3.2M 196M 2% /run '''/dev/mmcblk0p1''''''7.7G ''''''3.2G ''''''4.4G ''''''42% /''' |}</ol>

~~Filesystem Size Used Avail Use% Mounted on~~ ~~udev 925M 0 925M 0% /dev~~ ~~tmpfs 199M 3.2M 196M 2% /run~~ ~~'''/dev/mmcblk0p1 7.7G 3.2G 4.4G 42% /'''~~ ~~~~== Network connection test ==

<li>After the system starts, it will automatically assign an IP address to the Ethernet card through DHCP, without any other configuration</li>

<li>The command to view the IP address in the Linux system of the development board is as follows:

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Please do not copy the following commands. For example, the network node name in debian12 is end0, and the following commands need to be changed to ip a s end0.'''</~~li></ol~~big>|}

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

|-

|

orangepi@orangepi:~$ '''ip a s eth0'''

3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

:link/ether 5e:ac:14:a5:93:b3 brd ff:ff:ff:ff:ff:ff

:inet '''192.168.1.16'''/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0

::valid_lft 259174sec preferred_lft 259174sec

:inet6 240e:3b7:3240:c3a0:e269:8305:dc08:135e/64 scope global dynamic noprefixroute

::valid_lft 259176sec preferred_lft 172776sec

:inet6 fe80::957d:bbbd:4928:3604/64 scope link noprefixroute

::valid_lft forever preferred_lft forever|} {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''There are three ways to check the IP address after the development board starts:'''

'''~~There are three ways~~ 1. Connect the HDMI monitor, then log in to ~~check~~ the system and use the ip a s eth0 command to view the IP address ~~after the development board starts:~~'''

~~# '''Connect the HDMI monitor, then log in to the system and use the ip a s eth0 command to view the IP address'''~~# '''2. Enter the ip a s 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:'''

~~~~

<li>'''First check whether the Linux system has started normally. If the green light of the development board is flashing, it is generally started normally. If only the red light is on, or the red and green lights are not on, it means that the system has not started normally;'''</li>

<li>'''If there is no router to replace, you can only connect to an HDMI display or use the debugging serial port to check the IP address.'''</li></ol>

~~'''In addition, it should be noted that the development board DHCP automatically assigns an IP address without any settings.'''~~

'''In addition, it should be noted that the development board DHCP automatically assigns an IP address without any settings.'''</big>

|}

</li></ol>

<li>The command to test the network connectivity is as follows, the ping command can be interrupted through the shortcut key of '''Ctrl+C'''

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Please do not copy the following commands. For example, the network node name in debian12 is end0, and the following command needs to be changed to ping www.baidu.com -I end0, I is capital i,.'''</~~li></ol~~big>|}

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

|-

|

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

rtt min/avg/max/mdev = 6.260/6.770/7.275/0.373 ms

|}

</li></ol>

~~~~

=== WIFI connection test ===

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

==== The server image connects to WIFI through commands ====

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''When the development board is not connected to Ethernet, not connected to HDMI display, but only connected to the serial port, it is recommended to use the commands demonstrated in this section to connect to the WIFI network. Because nmtui can only display characters in some serial port software (such as minicom), and cannot display the graphical interface normally. Of course, if the development board is connected to an Ethernet or HDMI display, you can also use the commands demonstrated in this section to connect to the WIFI network.'''</big>|}

<li>First log in to the linux system, there are the following three ways

<li>If the development board is connected with a network cable, [[Orange Pi Zero 3#SSH remote login development board under Ubuntu|'''~~you can remotely log in to the Linux system through ssh~~SSH remote login development board under Ubuntu''']]</li></ol>

<li>If the development board is connected to the debugging serial port, you can use the serial port terminal to log in to the Linux system</li>

<li>If the development board is connected to the HDMI display, you can log in to the linux system through the terminal displayed on the HDMI</li></ol>

# <ol start="2" style="list-style-type: decimal;"><li>First use the '''nmcli dev wifi'''command to scan the surrounding WIFI hotspots

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

|-

|

orangepi@orangepi:~$ '''nmcli dev wifi'''

|}

[[File:~~media/image107~~zero3-img107.png~~|575x250px|选区_011~~]]

</div>

</li></ol><ol start="23" style="list-style-type: decimal;">

<li>Then use the '''nmcli''' command to connect to the scanned WIFI hotspot, where:

<li>'''wifi_name''' Need to replace it with the name of the WIFI hotspot you want to connect to</li>

<li>'''wifi_passwd'''Need to change to the password of the WIFI hotspot you want to connect to</li~~></ol></li></ol~~>

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

Device 'wlan0' successfully activated with 'cf937f88-ca1e-4411-bb50-61f402eef293'.

|}</ol></li></ol>

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

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

|-

|

orangepi@orangepi:~$ '''ip a s wlan0'''

11: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

:link/ether 23:8c:d6:ae:76:bb brd ff:ff:ff:ff:ff:ff

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

::valid_lft 259192sec preferred_lft 259192sec

:inet6 240e:3b7:3240:c3a0:c401:a445:5002:ccdd/64 scope global dynamic noprefixroute

::valid_lft 259192sec preferred_lft 172792sec

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

::valid_lft forever preferred_lft forever

|}

</ol>

<li>Use the '''ping''' command to test the connectivity of the wifi network, and the '''ping''' command can be interrupted through the shortcut key '''Ctrl+C'''</li~~></ol~~>

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

|-

|

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

rtt min/avg/max/mdev = 41.321/44.864/48.834/2.484 ms

|}

</ol>

~~~~

==== The server image connects to WIFI in a graphical way ====

<li>First log in to the linux system, there are the following three ways

<li>If the development board is connected with a network cable''', ~~you can remotely log in to the Linux system through ssh~~[[Orange Pi Zero 3#SSH remote login development board under Ubuntu|'''SSH remote login development board under Ubuntu''']]'''</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>

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

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

|-

|

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

|}</li></ol>

<li>Enter the nmtui command to open the interface as shown below</li>~~</ol>~~ ~~[[File:media/image108.png|345x215px]]~~

[[File:zero3-img108.png]]

</ol>

<li>Select '''Activate a connect''' and press Enter</li>~~</ol>~~ ~~[[File:media/image109.png|349x216px]]~~

[[File:zero3-img109.png]]

</ol>

<li>Then you can see all the searched WIFI hotspots</li~~></ol~~>

[[File:~~media/image110~~zero3-img110.~~jpeg|426x270px|16~~png]]

</div></ol>

<li>Select the WIFI hotspot you want to connect to, then use the Tab key to position the cursor on '''Activate''' and press Enter</li~~></ol~~>

[[File:~~media/image111~~zero3-img111.~~jpeg|474x298px|17~~png]]

</div></ol>

<li>Then a dialog box for entering a password will pop up, enter the corresponding password in '''Password''' and press Enter to start connecting to WIFI</li~~></ol~~>

[[File:~~media/image112~~zero3-img112.~~jpeg|480x308px|18~~png]]

</div></ol>

<li>After the WIFI connection is successful, a "*" will be displayed in front of the connected WIFI name</li~~></ol~~>

[[File:~~media/image113~~zero3-img113-2.~~jpeg|443x283px|19~~png]]

</div></ol>

<li>You can view the IP address of wifi through the '''ip a s wlan0''' command</li~~></ol~~>

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

|-

|

orangepi@orangepi:~$ '''ip a s wlan0'''

11: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

:link/ether 24:8c:d3:aa:76:bb brd ff:ff:ff:ff:ff:ff

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

::valid_lft 259069sec preferred_lft 259069sec

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

::valid_lft 259071sec preferred_lft 172671sec

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

::valid_lft forever preferred_lft forever

|}

</ol>

<li>Use the '''ping''' command to test the connectivity of the wifi network, and the '''ping''' command can be interrupted through the shortcut key '''Ctrl+C'''</li~~></ol~~>

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

|-

|

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

rtt min/avg/max/mdev = 41.321/44.864/48.834/2.484 ms

|}

</ol>

~~~~

==== 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:~~media/image114~~zero3-img114.png~~|275x121px~~]]

<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:media/image115.png|576x353px]]~~

[[File:zero3-img115.png]]

</ol>

<li>Then enter the password of the WIFI hotspot, and then click '''Connect'''to start connecting to WIFI</li>~~</ol>~~ ~~[[File:media/image116.png|288x147px]]~~

[[File:zero3-img116.png]]

</ol>

<li>After connecting to WIFI, you can open the browser to check whether you can access the Internet. The entrance of the browser is shown in the figure below</li>~~</ol>~~ ~~[[File:media/image117.png|465x249px]]~~

[[File:zero3-img117.png]]

</ol>

<li>If you can open other web pages after opening the browser, it means that the WIFI connection is normal</li~~></ol~~>

[[File:~~media/image118~~zero3-img118.png~~|576x222px~~]]</ol>

~~~~

=== The method of creating WIFI hotspot through create_ap ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''create_ap is a script that helps quickly create WIFI hotspots on Linux, and supports bridge and NAT modes. It can automatically combine hostapd, dnsmasq and iptables to complete the setting of WIFI hotspots, avoiding complex configuration for users. The github address is as follows:'''

[https://github.com/oblique/create_ap '''https://github.com/oblique/create_ap''']</big>|} {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The Linux image released by OPi has pre-installed the create_ap script. You can create a WIFI hotspot through the create_ap command. The basic command format of create_ap is as follows:'''

~~'''The Linux image released by OPi has pre-installed the create_ap script. You can create a WIFI hotspot through the create_ap command. The basic command format of create_ap is as follows:'''~~

'''create_ap [options] <wifi-interface> [<interface-with-internet>] [<access-point-name> [<passphrase>]]'''

'''* options：''' '''You can use this parameter to specify the encryption method, the frequency band of the WIFI hotspot, the bandwidth mode, the network sharing method, etc. You can get the options through create_ap -h'''

'''* ~~wifi-interface：The name~~ options:''' '''You can use this parameter to specify the encryption method, the frequency band of the ~~wireless~~ WIFI hotspot, the bandwidth mode, the network ~~card~~sharing method, etc. You can get the options through create_ap -h'''

'''* wifi-interface~~-with-internet：''' '''~~:The name of the wireless network card ~~that can be connected to the Internet, generally eth0~~'''

'''* ~~access~~interface-~~point~~with-~~name： hotspot~~ internet:''' '''The nameof the network card that can be connected to the Internet, generally eth0'''

'''* ~~passphrase：hotspot~~ access-point-name: hotspot name''' '''* passphrase:hotspot password'''</big>|}

<li>Enter the following command to create a WIFI hotspot named '''orangepi''' and password '''orangepi''' in NAT mode

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that in the following commands, Debian12 needs to change eth0 to end0.'''</~~li></ol~~big>|}

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

|-

|

orangepi@orangepi:~$ '''sudo create_ap -m nat wlan0 eth0 orangepi orangepi --no-virt'''

|}</li></ol>

<li>If the following information is output, it means that the WIFI hotspot is created successfully</li~~></ol~~>

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

|-

|

orangepi@orangepi:~$ '''sudo create_ap -m nat wlan0 eth0 orangepi orangepi --no-virt'''

wlan0: EAPOL-4WAY-HS-COMPLETED ce:bd:9a:dd:a5:86

|}</ol>

<li>Take out the mobile phone at this time, you can find the WIFI hotspot named '''orangepi''' created by the development board in the searched WIFI list, and then you can click '''orangepi''' to connect to the hotspot, the password is set above '''orangepi'''</li>~~</ol>~~ ~~[[File:media/image119.png|230x183px]]~~

[[File:zero3-img119-1.png]]

</ol>

<li>After the connection is successful, the display is as shown in the figure below</li>~~</ol>~~ ~~[[File:media/image120.png|233x111px]]~~

[[File:zero3-img120-1.png]]

</ol>

<li>In NAT mode, the wireless device connected to the hotspot of the development board requests an IP address from the DHCP service of the development board, so there will be two different network segments, for example, the IP of the development board is 192.168.1.X

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that in the following commands, Debian12 needs to change eth0 to end0.'''</~~li></ol~~big>|}

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

|-

|

orangepi@orangepi:~$ '''sudo ifconfig eth0'''

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

::inet '''192.168.1.150''' netmask 255.255.255.0 broadcast 192.168.1.255

::inet6 fe80::938f:8776:5783:afa2 prefixlen 64 scopeid 0x20<link>

::ether 4a:a0:c8:25:42:82 txqueuelen 1000 (Ethernet)

::RX packets 25370 bytes 2709590 (2.7 MB)

::RX errors 0 dropped 50 overruns 0 frame 0

::TX packets 3798 bytes 1519493 (1.5 MB)

::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

::device interrupt 83|}

By default, the DHCP service of the development board will assign an IP address of '''192.168.12.0/24''' to the device connected to the hotspot. At this time, click on the connected WIFI hotspot '''orangepi''', and then you can see that the IP address of the mobile phone is '''192.168.12.X'''

[[File:~~media/image120~~zero3-img120-1.png~~|271x129px]]~~ ~~[[File:media/image121.png|274x155px~~]]

[[File:zero3-img121-2.png]]

</li></ol>

<li>If you want to specify a different network segment for the connected device, you can specify it through the -g parameter, such as specifying the network segment of the access point AP through the -g parameter as 192.168.2.1</li~~></ol~~>

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that in the following commands, Debian12 needs to change eth0 to end0.'''</big>|}

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

|-

|

orangepi@orangepi:~$ '''sudo create_ap -m nat wlan0 eth0 orangepi orangepi -g 192.168.2.1 --no-virt'''

|}

At this time, after connecting to the hotspot through the mobile phone, click on the connected WIFI hotspot '''orangepi''', and then you can see that the IP address of the mobile phone is '''192.168.2.X'''.

[[File:~~media/image120~~zero3-img120-1.png~~|286x137px]]~~ ~~[[File:media/image122.png|302x174px~~]]

[[File:zero3-img122-2.png]]

</ol>

<li>If the '''--freq-band''' parameter is not specified, the hotspot created by default is in the 2.4G frequency band. If you want to create a hotspot in the 5G frequency band, you can specify the'''--freq-band 5''' parameter. The specific command is as follows

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that in the following commands, Debian12 needs to change eth0 to end0.'''</~~li></ol~~big>|}

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

|-

|

orangepi@orangepi:~$ '''sudo create_ap -m nat wlan0 eth0 orangepi orangepi --freq-band 5 --no-virt'''

|}</li></ol>

<li>If you need to hide the SSID, you can specify the '''--hidden''' parameter, the specific command is as follows

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that in the following commands, Debian12 needs to change eth0 to end0.'''</~~li></ol~~big>|}

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

|-

|

orangepi@orangepi:~$ '''sudo create_ap -m nat wlan0 eth0 orangepi orangepi --hidden --no-virt'''

|}

At this time, the mobile phone cannot search for the WIFI hotspot. You need to manually specify the name of the WIFI hotspot and enter the password to connect to the WIFI hotspot.

[[File:~~media/image123~~zero3-img123-1.png~~|237x198px~~]]</li></ol>

~~~~

==== create_ap method to create WIFI hotspot in bridge mode ====

<li>Enter the following command to create a WIFI hotspot named '''orangepi''' and password '''orangepi''' in bridge mode

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that in the following commands, Debian12 needs to change eth0 to end0.'''</~~li></ol~~big>|}

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

|-

|

orangepi@orangepi:~$ '''sudo create_ap -m bridge wlan0 eth0 orangepi orangepi --no-virt'''

|}</li></ol>

<li>If the following information is output, it means that the WIFI hotspot is created successfully</li~~></ol~~>

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

|-

|

orangepi@orangepi:~$ '''sudo create_ap -m bridge wlan0 eth0 orangepi orangepi --no-virt'''

wlan0: EAPOL-4WAY-HS-COMPLETED ce:bd:9a:dd:a5:86

|}</ol>

<li>Take out the mobile phone at this time, and you can find the WIFI hotspot named orangepi created by the development board in the searched WIFI list, and then you can click '''orangepi''' to connect to the hotspot, and the password is the '''orangepi''' set above</li>~~</ol>~~ ~~[[File:media/image119.png|265x211px]]~~

[[File:zero3-img119-1.png]]

</ol>

<li>After the connection is successful, the display is as shown in the figure below</li>~~</ol>~~ ~~[[File:media/image120.png|273x130px]]~~

[[File:zero3-img120-1.png]]

</ol>

<li>In bridge mode, the wireless device connected to the hotspot of the development board also requests an IP address from the DHCP service of the main router (the router connected to the development board), for example, the IP of the development board is '''192.168.1.X'''</li~~></ol~~>

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

|-

|

orangepi@orangepi:~$ '''sudo ifconfig eth0'''

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

::inet '''192.168.1.150''' netmask 255.255.255.0 broadcast 192.168.1.255

::inet6 fe80::938f:8776:5783:afa2 prefixlen 64 scopeid 0x20<link>

::ether 4a:a0:c8:25:42:82 txqueuelen 1000 (Ethernet)

::RX packets 25370 bytes 2709590 (2.7 MB)

::RX errors 0 dropped 50 overruns 0 frame 0

::TX packets 3798 bytes 1519493 (1.5 MB)

::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

::device interrupt 83 The IP of the device connected to the WIFI hotspot is also assigned by the main router, so the mobile phone connected to the WIFI hotspot and the development board are in the same network segment. At this time, click on the connected WIFI hotspot orangepi, and then you can see the IP address of the mobile phone Also '''192.168.1.X'''。|}

~~[[File:media/image120~~The IP of the device connected to the WIFI hotspot is also assigned by the main router, so the mobile phone connected to the WIFI hotspot and the development board are in the same network segment. At this time, click on the connected WIFI hotspot orangepi, and then you can see the IP address of the mobile phone also '''192.168.1.X'''.~~png|284x136px]]~~

[[File:~~media/image124~~zero3-img120-1.png~~|282x159px~~]]

[[File:zero3-img124-1.png]]

</ol>

<li>If the '''--freq-band''' y band. If you want to create a hotspot in the 5G frequency band, you can specify the '''--freq-band 5''' parameter. The specific command is as follows

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that in the following commands, Debian12 needs to change eth0 to end0.'''</~~li></ol~~big>|}

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

|-

|

orangepi@orangepi:~$ '''sudo create_ap -m bridge wlan0 eth0 orangepi orangepi --freq-band 5 --no-virt'''

|}</li></ol>

<li>If you need to hide the SSID, you can specify the '''--hidden''' parameter, the specific command is as follows

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that in the following commands, Debian12 needs to change eth0 to end0.'''</~~li></ol~~big>|}

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

|-

|

orangepi@orangepi:~$ '''sudo create_ap -m bridge wlan0 eth0 orangepi orangepi --hidden --no-virt'''

|}

At this time, the mobile phone cannot search for the WIFI hotspot. You need to manually specify the name of the WIFI hotspot and enter the password to connect to the WIFI hotspot.

[[File:~~media/image123~~zero3-img123-1.png~~|228x191px~~]]</li></ol>

~~~~

=== How to set static IP address ===

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

<li>First run the '''nmtui''' command

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo nmtui'''|}</li>

<li>Then select '''Edit a connection''' and press Enter

[[File:~~media/image125~~zero3-img125.png~~|227x247px~~]]</li>

<li>Then select the network interface that needs to set a static IP address, for example, to set the static IP address of the '''Ethernet''' interface, select '''Wired connection 1'''.

[[File:~~media/image126~~zero3-img126.png~~|310x149px~~]]</li>

<li>Then select '''Edit''' with the '''Tab''' key and press the Enter key

[[File:~~media/image127~~zero3-img127.png~~|316x144px~~]]</li>

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

[[File:~~media/image128~~zero3-img128.png~~|575x240px~~]]</li>

<li>Then press Enter, select '''Manual''' through the up and down arrow keys, and press Enter to confirm

[[File:~~media/image129~~zero3-img129.png~~|576x237px~~]]</li>

<li>The display after selection is shown in the figure below

[[File:~~media/image130~~zero3-img130.png~~|575x240px~~]]</li><li>8) Then move the cursor to '''<Show>''' via the Tab key[[File:~~media/image131~~zero3-img131.png~~|576x241px~~]]</li>

<li>Then press Enter, the following setting interface will pop up after entering

[[File:~~media/image132~~zero3-img132.png~~|575x450px~~]]</li><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 according to your specific needs, The values set in the image below are just an example'''[[File:~~media/image133~~zero3-img133.png~~|576x233px~~]]</li>

<li>After setting, move the cursor to '''<OK>''' in the lower right corner, and press Enter to confirm

[[File:~~media/image134~~zero3-img134.png~~|576x116px~~]]</li>

<li>Then click '''<Back>''' to return to the previous selection interface

[[File:~~media/image135~~zero3-img135.png~~|330x325px~~]]</li>

<li>Then select '''Activate a connection''', then move the cursor to '''<OK>''', and finally click Enter

[[File:~~media/image136~~zero3-img136.png~~|331x248px~~]]</li>

<li>Then select the network interface that needs to be set, such as '''Wired connection 1''', then move the cursor to <Deactivate>, and press the Enter key to disable '''Wired connection 1'''

[[File:~~media/image137~~zero3-img137.png~~|576x224px~~]]</li>

<li>Then please do not move the cursor, and then press the Enter key to re-enable '''Wired connection 1''', so that the static IP address set earlier will take effect

[[File:~~media/image138~~zero3-img138.png~~|576x224px~~]]</li>

<li>Then you can exit nmtui through the '''<Back>''' and '''Quit''' buttons

[[File:~~media/image139~~zero3-img139.png~~|300x253px~~]] [[File:~~media/image140~~zero3-img140.png~~|227x252px~~]]</li>

<li>Then through '''ip a s eth0''', you can see that the IP address of the network port has changed to the static IP address set earlier

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that in the following commands, Debian12 needs to change eth0 to end0.'''</big>|}{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''ip a s eth0'''

3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

:link/ether 5e:ac:14:a5:92:b3 brd ff:ff:ff:ff:ff:ff:inet '''192.168.1.177'''/24 brd 192.168.1.255 scope global noprefixroute eth0::valid_lft forever preferred_lft forever:inet6 241e:3b8:3240:c3a0:e269:8305:dc08:135e/64 scope global dynamic noprefixroute::valid_lft 259149sec preferred_lft 172749sec:inet6 fe80::957d:bbbe:4928:3604/64 scope link noprefixroute::valid_lft forever preferred_lft forever|}</li>

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

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that in the following commands, I is capital i, Debian12 needs to change eth0 to end0.'''</big>|}{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''ping 192.168.1.177 -I eth0'''

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

--- 192.168.1.47 ping statistics ---

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

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

==== Use the nmcli command to set a static IP address ====

<li>Then you can view the name of the network device through the '''nmcli con show''' command, as shown below

<li>'''orangepi''' is the name of the WIFI network interface (the name ~~>~~ is not necessarily the same)</li>

<li>'''Wired connection 1''' is the name of the Ethernet interface

~~~~{| class="wikitable" style="width:800px;"|-|orangepi@orangepi:~$ '''nmcli con show'''</pbr><pspan style="margin-right: 180px;">NAME UUID TYPE DEVICE</pspan> <pspan style="margin-right: 125px;">'''orangepi''' cfc4f922-ae48-46f1-84e1-2f19e9ec5e2a wifi wlan0</pspan> <pspan style="margin-right: 50px;">'''Wired connection 1''' 9db058b7-7701-37b8-9411-efc2ae8bfa30 ethernet eth0</pspan> |}</li></ol>

</li>

<li>Then enter the following command, where

<li>'''"Wired connection 1"''' means to set the static IP address of ~~>~~ the Ethernet port. If you need to set the static IP address of ~~>~~ the WIFI, please modify it to the corresponding name of the ~~>~~ WIFI network interface (you can get it through the '''nmcli con ~~>~~ show''' command)</li><li>'''ipv4.addresses''' is followed by the static IP address to be ~~>~~ set, which can be modified to the value you want to set</li>

<li>'''ipv4.gateway''' represents the address of the gateway

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo nmcli con mod "Wired connection 1" \ ipv4.addresses "192.168.1.110" \'''

'''ipv4.gateway "192.168.1.1" \'''

'''ipv4.dns "8.8.8.8" \'''

'''ipv4.method "manual"'''|}</li></ol>

</li>

<li>Then restart the linux system

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo reboot'''|}</li>

<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

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

|-

|

orangepi@orangepi:~$ '''ip addr show eth0'''

3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

:link/ether 5e:ae:14:a5:91:b3 brd ff:ff:ff:ff:ff:ff:inet '''192.168.1.110'''/32 brd 192.168.1.110 scope global noprefixroute eth0::valid_lft forever preferred_lft forever:inet6 240e:3b7:3240:c3a0:97de:1d01:b290:fe3a/64 scope global dynamic noprefixroute::valid_lft 259183sec preferred_lft 172783sec:inet6 fe80::3312:861a:a589:d3c/64 scope link noprefixroute::valid_lft forever preferred_lft forever|}</li></ol>

=== The method of setting the Linux system to automatically connect to the network for the first time ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The development board has an Ethernet port. If you want to remotely log in to the Linux system of the development board through the Ethernet port, you only need to plug in a network cable that can access the Internet normally to the Ethernet port. Assign an IP address, and then we can obtain the IP address of the Ethernet port through the HDMI screen, serial port or view the background of the router, and then we can log in to the Linux system remotely.'''

'''The development board also has wireless WIFI. If you want to remotely log in to the Linux system of the development board through WIFI, you need to remotely log in to the Linux system through the IP address of the Ethernet port ssh and then connect to WIFI through commands, or through commands on the HDMI screen or serial port. Connect to WIFI.'''

'''But if there is no HDMI screen and serial port module, although there is a network cable, the IP address of the development board cannot be checked through the background of the router. Or there is no HDMI screen, serial port module and network cable, and only WIFI can be connected, then you can use the method introduced in this section to automatically connect to WIFI and also set the static IP address of WIFI or automatically set the static IP address of the Ethernet port.'''</big>|}

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''To use the method in this section, you first need to prepare a Linux system machine. For example, a computer or a virtual machine with Ubuntu system installed.'''

'''Why do you need a Linux system machine, because the root file system of the development board Linux system burned in the TF micro SD card is in ext4 format, and the Linux system machine can mount it normally, and then modify the configuration files in it.'''</big>|}

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If you want to modify it in the Windows system, you can use the software Paragon ExtFS for Windows. Since this software needs to be paid, and there is no similar free software that is easy to use, I will not demonstrate it here.'''

'''In addition, if you have any problems with Paragon ExtFS for Windows software, please solve it yourself, we will not answer questions.'''</big>|}

<li>First burn the Linux image of the development board you want to use into the TF micro SD card, and then use a card reader to insert the TF micro SD card that has burned the Linux image of the development board into a machine with a Linux system (such as a machine with an Ubuntu system installed) computer, the following uses Ubuntu computer as an example to demonstrate)</li><li>When the TF micro SD card is inserted into the Ubuntu computer, the Ubuntu computer will generally automatically mount the partition of the Linux root file system in the TF micro SD card. You can know from the following command that '''/media/test/opi_root''' is the Linux root file in the TF micro SD card The path where the system is mounted{| class="wikitable" style="width:800px;" |-|

test@test:~$ '''df -h | grep "media"'''

/dev/sdd1    1.4G    1.2G    167M    88% '''/media/test/opi_root'''

test@test:~$ '''ls /media/test/opi_root'''

bin    boot    dev    etc    home    lib    lost+found    media    mnt    opt    proc    root    run sbin    selinux    srv    sys    tmp    usr    var|}</li><li>Then enter the '''/boot''' directory of the Linux system burned in the TF micro SD card{| class="wikitable" style="width:800px;" |-| test@test:~$ '''cd /media/test/opi_root/boot/'''|}</li>

<li>Then copy the '''orangepi_first_run.txt.template''' to '''orangepi_first_run.txt'''. Through the orangepi_first_run.txt configuration file, you can set the Linux system on the development board to automatically connect to a WIFI hotspot when it starts for the first time, and you can also set the WIFI or Ethernet port. static IP address

{| class="wikitable" style="width:800px;" |-| test@test:/media/test/opi_root/boot$ '''sudo cp orangepi_first_run.txt.template orangepi_first_run.txt'''|}</li>

<li>You can open the orangepi_first_run.txt file with the following command, and then you can view and modify the contents

{| class="wikitable" style="width:800px;" |-| test@test:/media/test/opi_root/boot$ '''sudo vim orangepi_first_run.txt'''|}</li>

<li>Instructions for using variables in the orangepi_first_run.txt file

<li>'''FR_general_delete_this_file_after_completion''' variable is ~~>~~ used to set whether to delete the orangepi_first_run.txt file ~~>~~ after the first startup. The default is 1, that is, delete. If ~~>~~ it is set to 0, orangepi_first_run.txt will be renamed to ~~>~~ orangepi_first_run.txt after the first startup .old, generally ~~>~~ keep the default value</li><li>'''FR_net_change_defaults''' variable is used to set whether to ~~>~~ change the default network settings, this must be set to 1, ~~>~~ otherwise all network settings will not take effect</li><li>'''FR_net_ethernet_enabled''' variable is used to control whether ~~>~~ to enable the configuration of the Ethernet port. If you need ~~>~~ to set the static IP address of the Ethernet port, please set ~~>~~ it to 1</li><li>'''FR_net_wifi_enabled''' variable is used to control whether to ~~>~~ enable WIFI configuration. If you need to set the development ~~>~~ board to automatically connect to WIFI hotspots, you must set ~~>~~ it to 1. In addition, please note that if this variable is set ~~>~~ to 1, the setting of the Ethernet port will be will fail. That ~~>~~ is to say, the WIFI and Ethernet ports cannot be set at the ~~>~~ same time (why, because it is not necessary...)</li><li>'''FR_net_wifi_ssid''' variable is used to set the name of the ~~>~~ WIFI hotspot you want to connect to</li><li>'''FR_net_wifi_key''' variable is used to set the password of the ~~>~~ WIFI hotspot you want to connect to</li><li>'''FR_net_use_static''' variable is used to set whether to set the ~~>~~ static IP address of WIFI or Ethernet port</li><li>'''FR_net_static_ip''' variable is used to set static IP address, ~~>~~ please set according to your actual situation</li><li>'''FR_net_static_gateway''' variable is used to set the gateway, ~~>~~ please set it according to your actual situation</li></ol>

</li>

<li>The following demonstrates several specific setting examples:

<li>For example, if you want the Linux system of the development ~~>~~ board to automatically connect to the WIFI hotspot after the ~~>~~ first startup, you can set it like this:<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) Set '''FR_net_change_defaults''' to '''1'''</li><li>b) Set '''FR_net_wifi_enabled''' to '''1'''</li><li>c) Set '''FR_net_wifi_ssid''' to the name of the WIFI hotspot you ~~>~~ want to connect to</li><li>d) Set '''FR_net_wifi_key''' to the password of the WIFI hotspot ~~>~~ you want to connect to</li></ol>

</li>

<li>For example, if you want the Linux system of the development ~~>~~ board to automatically connect to the WIFI hotspot after the ~~>~~ first startup, and set the IP address of the WIFI to a ~~>~~ specific static IP address (so that when the Linux system is ~~>~~ started, you can directly use the set static IP address to ssh ~~>~~ remotely Log in to the development board without checking the ~~>~~ IP address of the development board through the background of ~~>~~ the router), you can set it like this:<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) Set '''FR_net_change_defaults''' to '''1'''</li><li>b) Set '''FR_net_wifi_enabled''' to '''1'''</li><li>c) Set '''FR_net_wifi_ssid''' to the name of the WIFI hotspot you ~~>~~ want to connect to</li><li>d) Set '''FR_net_wifi_key''' to the password of the WIFI hotspot ~~>~~ you want to connect to</li><li>e) Set '''FR_net_use_static''' to '''1'''</li><li>f) Set '''FR_net_static_ip''' to the desired IP address</li><li>g) Set '''FR_net_static_gateway''' to the corresponding gateway ~~>~~ address</li></ol>

</li>

<li>For example, if you want to automatically set the IP address of ~~>~~ the Ethernet port to the desired static IP address after the ~~>~~ Linux system of the development board starts for the first ~~>~~ time, you can set it like this:<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) Set '''FR_net_change_defaults''' to '''1'''</li><li>b) Set '''FR_net_ethernet_enabled''' to '''1'''</li><li>c) Set '''FR_net_use_static''' to '''1'''</li><li>d) Set '''FR_net_static_ip''' to the desired IP address</li><li>e) Set '''FR_net_static_gateway''' to the corresponding gateway ~~>~~ address</li></ol>

</li></ol>

</li>

<li>After modifying the orangepi_first_run.txt file, you can exit the /boot directory of the development board Linux system in the TF micro SD card, uninstall the TF micro SD card, and then insert the TF micro SD card into the development board to start</li><li>If you have not set a static IP address, you still need to check the IP address through the background of the router. If you have set a static IP address, you can ping the set static IP address on the computer. If you can ping, it means that the system has started normally, and The network has also been set correctly, and then you can use the set IP address ssh to remotely log in to the Linux system of the development board</p~~></li></ol~~>

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''After the Linux system of the development board is started for the first time, orangepi_first_run.txt will be deleted or renamed to orangepi_first_run.txt.old. At this time, the orangepi_first_run.txt configuration file will be reset, and then the Linux system of the development board will be restarted, orangepi_first_run. The configuration in txt will not take effect again, because this configuration will only be effective when the Linux system is started for the first time after burning, please pay special attention to this point.'''</big>|}</li></ol>

~~~~

== SSH remote login development board ==

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

# Then you can remotely log in to the linux system through the ssh command

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

orangepi@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.'''

'''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 find other reasons.'''</big>|}

<li>After successfully logging in to the system, the display is as shown in the figure below

[[File:~~media/image141~~zero3-img141.png~~|575x273px~~]]{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If ssh fails to log in to the linux system normally, first check whether the IP address of the development board can be pinged. If the ping is ok, you can log in to the linux system through the serial port or HDMI display and then enter the following command on the development board and try again. Is it possible to connect:'''</p~~></li></ol~~>

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

'''If it still doesn't work, try to reset the system.'''</big>|}</li></ol>

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

<li>Open '''Session'''</li>

<li>Then select '''SSH''' in '''Session Setting'''</li>

<li>Then enter the IP address of the development board in the ~~>~~ '''Remote host'''</li><li>Then enter the user name root or orangepi of the linux system in ~~>~~ '''Specify username'''</li>

<li>Finally click '''OK'''

[[File:~~media/image142~~zero3-img142.~~jpeg|553x280px|14~~png]]

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

</li>

<li>Then you will be prompted to enter a password. The default passwords for root and orangepi users are 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>|}

[[File:~~media/image143~~zero3-img143.~~jpeg|553x151px|15~~png]]

</div></li>

<li>The display after successfully logging in to the system is shown in the figure below

[[File:~~media/image144~~zero3-img144.png~~|559x388px~~]]</li></ol>

== HDMI test ==

<li>Use a Micro HDMI to HDMI cable to connect the Orange Pi development board and HDMI display

[[File:~~media/image13~~zero3-img13.png~~|167x172px~~]]</li><li>After starting the linux system, if the HDMI monitor has image output, it means that the HDMI interface is working normally</p~~></li></ol~~>

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

'''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 IN function.'''</big>|}

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''When the HDMI is not displayed, please check whether the HDMI cable is plugged in tightly. After confirming that there is no problem with the connection, you can change a different screen and try to see if it is displayed.'''</big>|}</li></ol>

~~~~

=== HDMI to VGA display test ===

<li>HDMI to VGA converter

[[File:~~media/image145~~zero3-img145.png~~|155x104px~~]]</li><li>A VGA cable and a Micro HDMI male to HDMI female conversion ~~>~~ cable[[File:~~media/image146~~zero3-img146-1.png|~~148x133px~~300px]] [[File:~~media/image147~~zero3-img147.~~jpeg~~png|~~157x139px|IMG_6140(20220104-134930)~~300px]]</li>

<li>A monitor or TV that supports VGA interface</li></ol>

</li>

<li>HDMI to VGA display test as shown below

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

=== How to set HDMI resolution in Linux5.4 system ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note: This method is only applicable to systems with linux5.4 kernel.'''</big>|}

<li>There is a disp_mode variable in '''/boot/orangepiEnv.txt''' of the linux system, which can be used to set the resolution of the HDMI output. The default resolution of the linux system is 1080p60

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

|-

|

orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''

verbosity=1

console=both

disp_mode='''1080p60'''

fb0_width=1920

fb0_height=1080|}</li><li>The values supported by the disp_mode variable are shown in the table below</p~~></li></ol~~>

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

|-

|-

| style="text-align: ~~left~~center;"| '''480i'''| style="text-align: ~~left~~center;"| '''720x480'''| style="text-align: ~~left~~center;"| '''60'''

|-

| style="text-align: ~~left~~center;"| '''576i'''| style="text-align: ~~left~~center;"| '''720x480'''| style="text-align: ~~left~~center;"| '''50'''

|-

| style="text-align: ~~left~~center;"| '''480p'''| style="text-align: ~~left~~center;"| '''720x480'''| style="text-align: ~~left~~center;"| '''60'''

|-

| style="text-align: ~~left~~center;"| '''576p'''| style="text-align: ~~left~~center;"| '''720x576'''| style="text-align: ~~left~~center;"| '''60'''

|-

| style="text-align: ~~left~~center;"| '''720p50'''| style="text-align: ~~left~~center;"| '''1280x720'''| style="text-align: ~~left~~center;"| '''50'''

|-

| style="text-align: ~~left~~center;"| '''720p60'''| style="text-align: ~~left~~center;"| '''1280x720'''| style="text-align: ~~left~~center;"| '''60'''

|-

| style="text-align: ~~left~~center;"| '''1080i50'''| style="text-align: ~~left~~center;"| '''1920x1080'''| style="text-align: ~~left~~center;"| '''50'''

|-

| style="text-align: ~~left~~center;"| '''1080i60'''| style="text-align: ~~left~~center;"| '''1920x1080'''| style="text-align: ~~left~~center;"| '''60'''

|-

| style="text-align: ~~left~~center;"| '''1080p24'''| style="text-align: ~~left~~center;"| '''1920x1080'''| style="text-align: ~~left~~center;"| '''24'''

|-

| style="text-align: ~~left~~center;"| '''1080p50'''| style="text-align: ~~left~~center;"| '''1920x1080'''| style="text-align: ~~left~~center;"| '''50'''

|-

| style="text-align: ~~left~~center;"| '''1080p60'''| style="text-align: ~~left~~center;"| '''1920x1080'''| style="text-align: ~~left~~center;"| '''60'''

|}

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note: Linux systems currently do not support 4K resolution.'''</big>|}</li></ol>

<li>Change the value of the disp_mode variable to the desired output resolution, and then restart the system, HDMI will output the set resolution</li>

<li>The method of viewing the HDMI output resolution is as follows. If the displayed resolution is the same as the set resolution, it means that the setting of the development board is correct.

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

|-

|

orangepi@orangepi:~$ '''sudo cat /sys/class/disp/disp/attr/sys'''

|}[[File:~~media/image149~~zero3-img149.png~~|575x84px~~]]</li></ol>

=== How to Modify the Framebuffer Width and Height of Linux5.4 System ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note: This method is only applicable to systems with linux5.4 kernel.'''</big>|}

There are two variables fb0_width and fb0_height in the '''/boot/orangepiEnv.txt''' of the linux system, which can be used to set the width and height of the Framebuffer. The default setting of the linux system is fb0_width=1920 and fb0_height=1080.

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

|-

|

orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''

disp_mode=1080p60

'''fb0_width=1920'''

'''fb0_height=1080'''|}

The '''reference''' values corresponding to different resolutions of fb0_width and fb0_height are as follows:

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

|-

|-

| style="text-align: ~~left~~center;"| '''480p'''| style="text-align: ~~left~~center;"| '''720'''| style="text-align: ~~left~~center;"| '''480'''

|-

| style="text-align: ~~left~~center;"| '''576p'''| style="text-align: ~~left~~center;"| '''720'''| style="text-align: ~~left~~center;"| '''576'''

|-

| style="text-align: ~~left~~center;"| '''720p'''| style="text-align: ~~left~~center;"| '''1280'''| style="text-align: ~~left~~center;"| '''720'''

|-

| style="text-align: ~~left~~center;"| '''1080p'''| style="text-align: ~~left~~center;"| '''1920'''| style="text-align: ~~left~~center;"| '''1080'''

|}

=== Framebuffer Cursor Setting ===

<li>The softcursor used by Framebuffer, the method of setting the cursor to blink or not is as follows

{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''echo 1 > /sys/class/graphics/fbcon/cursor_blink        #cursor blinking'''root@orangepi:~# '''echo 0 > /sys/class/graphics/fbcon/cursor_blink        #cursor not blinking'''|}</li>

<li>If you need to hide the cursor, you can add '''vt.global_cursor_default=0''' in the '''extraargs''' variable of '''/boot/orangepiEnv.txt''' (the value of extraargs will be assigned to the '''bootargs''' environment variable and finally passed to the kernel) (if '''vt.global_cursor_default=1''', the cursor will be displayed) , and then restart the system to see that the cursor has disappeared

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

|-

|

orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''

verbosity=1

fb0_width=1920

fb0_height=1080

'''extraargs=vt.global_cursor_default=0'''|}</li></ol>

== How to use Bluetooth ==

<li>Click the Bluetooth icon in the upper right corner of the desktop

[[File:~~media/image150~~zero3-img150.png~~|314x122px~~]]</li>

<li>Then select the adapter

[[File:~~media/image151~~zero3-img151.png~~|318x140px~~]]</li>

<li>If there is a prompt on the following interface, please select '''Yes'''

[[File:~~media/image152~~zero3-img152.png~~|248x85px~~]]</li>

<li>Then set the '''Visibility Setting''' to '''Always visible''' in the Bluetooth adapter setting interface, and then close it

[[File:~~media/image153~~zero3-img153.png~~|196x183px~~]]</li>

<li>Then open the configuration interface of the Bluetooth device

[[File:~~media/image154~~zero3-img154.png~~|438x179px~~]]</li>

<li>Click '''Search''' to start scanning the surrounding Bluetooth devices

[[File:~~media/image155~~zero3-img155.png~~|311x210px~~]]</li>

<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

[[File:~~media/image156~~zero3-img156.png~~|311x242px~~]]</li>

<li>When pairing, a pairing confirmation box will pop up in the upper right corner of the desktop, just select '''Confirm''' to confirm, and the phone also needs to confirm at this time

[[File:~~media/image157~~zero3-img157.png~~|411x150px~~]]</li>

<li>After pairing with the mobile phone, you can select the paired Bluetooth device, then right click and select '''Send a File''' to start sending a picture to the mobile phone

[[File:~~media/image158~~zero3-img158.png~~|405x239px~~]]</li>

<li>The interface for sending pictures is as follows

[[File:~~media/image159~~zero3-img159.png~~|399x231px~~]]</li></ol>

<li>After entering the system, you can first check whether there is a Bluetooth device node through the '''hciconfig''' command. If it exists, it means that the Bluetooth initialization is normal.

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

|-

|

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

orangepi@orangepi:~$ '''hciconfig -a'''

hci0: Type: Primary Bus: UART

:BD Address: 3E:61:3D:19:0E:52 ACL MTU: 1021:8 SCO MTU: 240:3:UP RUNNING:RX bytes:925 acl:0 sco:0 events:72 errors:0:TX bytes:5498 acl:0 sco:0 commands:72 errors:0:Features: 0xbf 0xff 0x8d 0xfe 0xdb 0x3d 0x7b 0xc7:Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3:Link policy: RSWITCH SNIFF:Link mode: SLAVE ACCEPT:Name: 'orangepi':Class: 0x3c0000:Service Classes: Rendering, Capturing, Object Transfer, Audio:Device Class: Miscellaneous,:HCI Version: 5.0 (0x9) Revision: 0x400:LMP Version: 5.0 (0x9) Subversion: 0x400:Manufacturer: Spreadtrum Communications Shanghai Ltd (492)|}</li>

<li>Use '''bluetoothctl''' to scan bluetooth devices

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

|-

|

orangepi@orangepi:~$ '''sudo bluetoothctl'''

[NEW] Controller 10:11:12:13:14:15 orangepizero3 [default]

Discovery stopped

[CHG] Controller 10:11:12:13:14:15 Discovering: no

[CHG] Device DC:72:9B:4C:F4:CF RSSI is nil|}</li>

<li>After scanning to the device you want to pair, you can pair it. You need to use the MAC address of the device for pairing

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

|-

|

[bluetooth]# '''pair DC:72:9B:4C:F4:CF''' '''#Use the MAC address of the scanned Bluetooth device for pairing'''

Attempting to pair with DC:72:9B:4C:F4:CF

'''Pairing successful #Prompt that the pairing is successful'''

[CHG] Device DC:72:9B:4C:F4:CF ServicesResolved: no

[CHG] Device DC:72:9B:4C:F4:CF Connected: no|}</li>

<li>After the pairing is successful, the Bluetooth interface of the mobile phone will be displayed as follows

[[File:~~media/image160~~zero3-img160.png~~|189x167px~~]]</li>

<li>To connect a Bluetooth device, you need to install the '''pulseaudio-module-bluetooth''' package, and then start the '''pulseaudio''' service

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

|-

|

orangepi@orangepi:~$ '''sudo apt update'''

orangepi@orangepi:~$ '''sudo''' '''apt -y install pulseaudio-module-bluetooth'''

orangepi@orangepi:~$ '''pulseaudio --start'''|}</li>

<li>How to connect to a Bluetooth device

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

|-

|

orangepi@orangepi:~$ '''sudo bluetoothctl'''

Agent registered

[CHG] Device DC:72:9B:4C:F4:CF ServicesResolved: yes

[CHG] Controller 10:11:12:13:14:15 Discoverable: no

'''[orangepi]# #This prompt appears to indicate that the connection is successful'''|}</li>

<li>After connecting the bluetooth device, the bluetooth configuration interface of the Android mobile phone can see '''the prompt that the audio has been connected for calls and media'''

[[File:~~media/image161~~zero3-img161.~~jpeg|223x232px|Screenshot_20201205_142413~~png]]

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

== USB interface test ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The USB interface can be connected to a USB hub to expand the number of USB interfaces.'''</big>|}

# Execute the following command, if you can see the output of sdX, it means that the U disk is recognized successfully

::{| class="wikitable" style="width:800px;"|-|orangepi@orangepi:~$ '''cat /proc/partitions | grep "sd*"''' major minor #blocks name 8 0 30044160 '''sda''' 8 1 30043119 '''sda1''' |}

<li>Use the mount command to mount the U disk to '''/mnt''', and then you can view the files in the U disk</li~~></ol~~>

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

|-

|

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

test.txt

|}</ol>

<li>After mounting, you can view the capacity usage and mount point of the U disk through the '''df -h''' command</li~~></ol~~>

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

|-

|

orangepi@orangepi:~$ '''df -h | grep "sd"'''

/dev/sda1     29G    208K    29G    1% /mnt|}</ol>

~~~~

=== USB Ethernet card test ===

# The usable USB Ethernet cards that '''have been tested''' so far are as follows. Among them, the RTL8153 USB Gigabit network card can be used normally when it is inserted into the USB 2.0 Host interface of the development board, but the speed cannot reach Gigabit. Please note that

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

|-

| style="text-align: ~~left~~center;"| serial number| style="text-align: ~~left~~center;"| model

|-

| style="text-align: ~~left~~center;"| 1| style="text-align: ~~left~~center;"| RTL8152B USB 100M network card

|-

| style="text-align: ~~left~~center;"| 2| style="text-align: ~~left~~center;"| RTL8153 USB Gigabit LAN

|}

<li>First insert the USB network card into the USB interface of the development board, and then insert the network cable into the USB network card to ensure that the network cable can access the Internet normally. If you can see the following log information through the '''dmesg''' command, it means that the USB network card is recognized normally.

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

|-

|

orangepi@orangepi:~$ '''dmesg | tail'''

[ 121.985016] usb 3-1: USB disconnect, device number 2

[ 127.763031] IPv6: ADDRCONF(NETDEV_UP): enx00e04c362017: link is not ready

[ 129.892465] r8152 3-1:1.0 enx00e04c362017: carrier on

[ 129.892583] IPv6: ADDRCONF(NETDEV_CHANGE): enx00e04c362017: link becomes ready|}</li>

<li>Then you can see the device node of the USB network card and the automatically assigned IP address through the ifconfig command

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

|-

|

orangepi@orangepi:~$ '''sudo ifconfig'''

'''enx00e04c362017''': flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

::inet '''192.168.1.177''' netmask 255.255.255.0 broadcast 192.168.1.255::inet6 fe80::681f:d293:4bc5:e9fd prefixlen 64 scopeid 0x20<link>::ether 00:e0:4c:36:20:17 txqueuelen 1000 (Ethernet)::RX packets 1849 bytes 134590 (134.5 KB)::RX errors 0 dropped 125 overruns 0 frame 0::TX packets 33 bytes 2834 (2.8 KB)::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0|}</li>

<li>The command to test network connectivity is as follows

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

|-

|

orangepi@orangepi:~$ '''ping www.baidu.com -I enx00e04c362017'''

PING www.a.shifen.com (14.215.177.38) from 192.168.1.12 eth0: 56(84) bytes of data.

--- 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|}</li></ol>

=== USB camera test ===

<li>First insert the USB camera into the USB port of the Orange Pi development board</li>

<li>Then through the lsmod command, you can see that the kernel has automatically loaded the following modules

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

|-

|

orangepi@orangepi:~$ '''lsmod'''

<pspan style="margin-right: 100px;">Module Size Used by</pspan> <pspan style="margin-right: 80px;">~~'''~~uvcvideo 106496 0~~'''~~</pspan> |}</li><li>3) Through the v4l2-ctl command, you can see that the device node information of the USB camera is /dev/video0{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''sudo apt update'''

orangepi@orangepi:~$ '''sudo''' '''apt install -y v4l-utils'''

orangepi@orangepi:~$ '''v4l2-ctl --list-devices'''

USB 2.0 Camera (usb-sunxi-ehci-1):

:/dev/video0|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the l in v4l2 is a lowercase letter l, not the number 1.''''''In addition, the serial number of the video is not necessarily video0, please refer to what you actually see.'''</big>|}</li>

<li>Use fswebcam to test the USB camera

<li>Install fswebcam

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

|-

|

orangepi@orangepi:~$ '''sudo''' '''apt update'''

orangepi@orangepi:~$ '''sudo apt-get install -y fswebcam'''|}</li><li>After installing fswebcam, you can use the following command to ~~>~~ take pictures<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) -d option is used to specify the device node of the USB ~~>~~ camera</li><li>b) --no-banner is used to remove the watermark of the photo</li><li>c) -r option is used to specify the resolution of the photo</li><li>d) -S option is used to set the number of previous frames to ~~>~~ skip</li><li>e) ./image.jpg is used to set the name and path of the ~~>~~ generated photo{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''sudo''' '''fswebcam -d /dev/video0 \'''

'''--no-banner -r 1280x720 -S 5 ./image.jpg'''|}</li></ol></li><li>In the server version of the linux system, you can use the scp command to transfer the taken pictures to the Ubuntu PC for mirror viewing after taking pictures{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''scp image.jpg [mailto:test@192.168.1.55:/home/test test@192.168.1.55:/home/test] (Modify the IP address and path according to the actual situation)'''|}

</li>

~~<li>In the server version of the linux system, you can use the scp > command to transfer the taken pictures to the Ubuntu PC for > mirror viewing after taking picturesorangepi@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)'''</li>~~<li>In the desktop version of the linux system, you can directly ~~>~~ view the captured pictures through the HDMI display</li></ol>

</li>

<li>Use mjpg-streamer to test USB camera

<li>Download mjpg-streamer

<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) Github download address:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''git clone https://github.com/jacksonliam/mjpg-streamer'''|}</li><li>b) The image download address of Gitee is:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''git clone https://gitee.com/leeboby/mjpg-streamer'''|}</li></ol>

</li>

<li>Install dependent packages

<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) Ubuntu system{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt-get install -y cmake libjpeg8-dev'''|}</li><li>b) Debian system{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt-get install -y cmake libjpeg62-turbo-dev'''|}</li></ol>

</li>

<li>Compile and install mjpg-streamer

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

|-

|

orangepi@orangepi:~$ '''cd mjpg-streamer/mjpg-streamer-experimental'''

orangepi@orangepi:~/mjpg-streamer/mjpg-streamer-experimental$ '''make -j4'''

orangepi@orangepi:~/mjpg-streamer/mjpg-streamer-experimental$ '''sudo make install'''|}</li>

<li>Then enter the following command to start mjpg_streamer

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the serial number of the video is not necessarily video0, please refer to what you actually see.'''</big>|} {| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~/mjpg-streamer/mjpg-streamer-experimental$ '''export LD_LIBRARY_PATH=.'''

orangepi@orangepi:~/mjpg-streamer/mjpg-streamer-experimental$ '''sudo ./mjpg_streamer -i "./input_uvc.so -d \'''

'''/dev/video0 -u -f 30" -o "./output_http.so -w ./www"'''|}</li><li>Then enter '''[the IP address of the development board: 8080]''' ~~>~~ in the browser of the Ubuntu PC or Windows PC or mobile phone ~~>~~ on the same LAN as the development board to see the video ~~>~~ output by the camera

[[File:~~media/image162~~zero3-img162.~~jpeg|575x278px|图片9~~png]]

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

== Audio Test ==

[[File:~~media/image163~~zero3-img163.~~jpeg|126x125px|IMG_256~~png]]

</div></li>

<li>Through the '''aplay -l''' command, you can view the sound card devices supported by the Linux system

<li>The output of the linux5.4 system is as follows, where '''card 0: ~~>~~ audiocodec''' is the sound card device required for earphone ~~>~~ playback{| class="wikitable" style="width:800px;" |-|

root@orangepi:~# '''aplay -l'''

**** List of PLAYBACK Hardware Devices ****

'''card 0: audiocodec [audiocodec], device 0: SUNXI-CODEC sun50iw9-codec-0 []'''

:'''Subdevices: 1/1''':'''Subdevice #0: subdevice #0'''|}</li><li>The output of the linux6.1 system is as follows, where ~~>~~ '''audiocodec''' is the sound card device required for earphone ~~>~~ playback{| class="wikitable" style="width:800px;" |-|

root@orangepi:~# '''aplay -l'''

**** List of PLAYBACK Hardware Devices ****

'''card 0: audiocodec [audiocodec], device 0: CDC PCM Codec-0 [CDC PCM Codec-0]'''

:'''Subdevices: 1/1''':'''Subdevice #0: subdevice #0'''|}</li></ol>

</li>

<li>Then use the '''aplay''' command to play the audio, and the headset can hear the sound

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

|-

|

root@orangepi:~# '''aplay -D hw:0,0 /usr/share/sounds/alsa/audio.wav'''

Playing WAVE 'audio.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If there is noise in the earphone test, please pull out some earphones, do not insert all the earphones.'''</big>|}</li></ol>

~~'''If there is noise in the earphone~~

~~~~

==== HDMI audio playback test ====

<li>First use the Micro HDMI to HDMI cable to connect the Orange Pi development board to the TV (other HDMI monitors need to ensure that they can play audio)</li>

<li>HDMI audio playback does not require other settings, just use the '''aplay''' command to play directly

{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''aplay -D hw:2,0 /usr/share/sounds/alsa/audio.wav'''|}</li></ol>

=== Testing audio methods on desktop systems ===

<li>First open the file manager

[[File:~~media/image164~~zero3-img164.png~~|257x126px~~]]</li>

<li>Then find the following file (if there is no audio file in the system, you can upload an audio file to the system yourself)

[[File:~~media/image165~~zero3-img165.~~jpeg|236x186px|图片10~~png]]

</div></li>

<li>Then select the audio.wav file, right click and select open with vlc to start playing

[[File:~~media/image166~~zero3-img166.png~~|241x195px~~]]</li>

<li>How to switch between different audio devices such as HDMI playback and headphone playback

<li>First open the volume control interface

[[File:~~media/image167~~zero3-img167.png~~|294x161px~~]]</li><li>When playing audio, the audio device options that the playback ~~>~~ software can use will be displayed in '''Playback''', as shown ~~>~~ in the figure below, where you can set which audio device to ~~>~~ play to

[[File:~~media/image168~~zero3-img168.png~~|576x324px|4~~]]

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

== Infrared receiving test ==

[[File:~~media/image163~~zero3-img163.~~jpeg|164x163px|IMG_256~~png]]

</div></li>

<li>Install ir-keytable infrared testing software</li~~></ol~~>

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

|-

|

orangepi@orangepi:~$ '''sudo''' '''apt update'''

orangepi@orangepi:~$ '''sudo''' '''apt-get install -y ir-keytable'''

|}</ol>

<li>Then execute ir-keytable to view the information of the infrared device

<li>linux5.4 system output is as follows</li~~></ol></li></ol~~>

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

|-

|

orangepi@orangepi:~$ '''ir-keytable'''

Found /sys/class/rc/rc0/ (/dev/input/event1) with:

::Driver: sunxi-rc-recv, table: rc_map_sunxi

::lirc device: /dev/lirc0

::Supported protocols: lirc nec

::Enabled protocols: lirc nec

::Name: sunxi_ir_recv

::bus: 25, vendor/product: 0001:0001, version: 0x0100 ~~Repeat delay = 500 ms, repeat period = 125 ms~~

::Repeat delay = 500 ms, repeat period = 125 ms

|}

</ol>

<li>The output of the linux6.1 system is as follows

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

|-

|

orangepi@orangepi:~$ '''ir-keytable'''

Found /sys/class/rc/rc0/ with:

:Name: sunxi-ir:Driver: sunxi-ir:Default keymap: rc-empty:Input device: /dev/input/event5:LIRC device: /dev/lirc0:Attached BPF protocols: Operation not permitted:Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm:Enabled kernel protocols: lirc:bus: 25, vendor/product: 0001:0001, version: 0x0100:Repeat delay = 500 ms, repeat period = 125 ms|}</li></ol></li></ol>

<li>Before testing the infrared receiving function, you need to prepare an infrared remote controller dedicated to Orange Pi, '''other remote controllers do not support it'''

[[File:~~media/image169~~zero3-img169.~~jpeg|140x131px|IMG_256~~png]]

</div></li>

<li>Then enter the '''ir-keytable -t''' command in the terminal, and then use the infrared remote control to press the button against the infrared receiver of the Orange Pi development board to see the received key code in the terminal

<li>linux5.4 system output is as follows</li~~></ol></li></ol~~>

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

|-

|

orangepi@orangepi:~$ '''sudo ir-keytable -t'''

1598339152.914715: event type EV_MSC(0x04): scancode = 0xfb0410

|}</ol>

<li>linux6.1 system output is as follows

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

|-

|

orangepi@orangepi:~$ '''sudo ir-keytable -c -p NEC -t'''

Old keytable cleared

202.063219: lirc protocol(nec): scancode = 0x45c

202.063249: event type EV_MSC(0x04): scancode = 0x45c

202.063249: event type EV_SYN(0x00).|}</li></ol></li></ol>

== Temperature sensor ==

# <ol start="1" style="list-style-type: decimal;"><li>H618 has a total of 4 temperature sensors, the command to view the temperature is as follows: ~~'''The displayed temperature value needs to be divided by 1000, the unit is Celsius.'''~~

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

|-

|

<big>'''The displayed temperature value needs to be divided by 1000, the unit is Celsius.'''</big>

|}

</li>

<li>sensor0: CPU temperature sensor, the first command is used to view ~~>~~ the type of temperature sensor, and the second command is used to ~~>~~ view the value of the temperature sensor</li~~></ol~~>

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

|-

|

orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone0/type'''

'''57734'''

|}</ol>

<li>sensor1: DDR temperature sensor, the first command is used to view ~~>~~ the type of temperature sensor, and the second command is used to ~~>~~ view the value of the temperature sensor{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone1/type'''

'''ddr'''_thermal_zone

orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone1/temp'''

'''57410'''|}</li><li>sensor2: GPU temperature sensor, the first command is used to view ~~>~~ the type of temperature sensor, the second command is used to view ~~>~~ the value of the temperature sensor{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone2/type'''

'''gpu'''_thermal_zone

orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone2/temp'''

'''59273'''|}</li><li>sensor3: VE temperature sensor, the first command is used to view ~~>~~ the type of temperature sensor, and the second command is used to ~~>~~ view the value of the temperature sensor{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone3/type'''

'''ve'''_thermal_zone

orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone3/temp'''

'''58949'''|}</li></ol></ol>

<li>The system with Linux6.1 kernel can also use the '''sensors''' command to view the current temperature of the system</li~~></ol~~>

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

|-

|

orangepi@orangepi:~$ '''sensors'''

Adapter: Virtual device

temp1: +'''47.4°C''' (crit = +110.0°C)

gpu_thermal-virtual-0

Adapter: Virtual device

temp1: +'''48.7°C''' (crit = +110.0°C)

ddr_thermal-virtual-0

Adapter: Virtual device

temp1: +'''47.8°C''' (crit = +110.0°C)

ve_thermal-virtual-0

Adapter: Virtual device

temp1: +'''47.2°C''' (crit = +110.0°C)|}</ol>

== 13 Pin Description of the Pin Expansion Board Interface ==

[[File:~~media/image170.jpeg|245x133px|C:\Users\orangepi\Desktop\用户手册插图\Zero3\未标题~~zero3-3img170.~~jpg未标题-3~~png]]

</div></li>

<li>The schematic diagram of the 13pin interface of the development board is as follows

[[File:~~media/image19~~zero3-img19.png~~|359x193px~~]]</li>

<li>The function description of the 13 pin expansion board interface pins of the development board is as follows

<li>When the 13pin pin is connected to the expansion board, it can ~~>~~ be provided additionally<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) 2个USB 2.0 Host</li><li>b) Audio output of the left and right audio channels of the ~~>~~ earphones</li><li>c) TV-OUT video output</li><li>d) Infrared receiving function</li><li>e) After the expansion board is connected, pins 10, 11 and 12 ~~>~~ of the 13pin interface cannot be used</li><li>f) '''In addition, it should be noted that the MIC on the 13pin expansion board cannot be used on the Orange Pi Zero 3'''</li></ol>

</li>

<li>When pin 13 is not connected to the expansion board, pins 10, ~~>~~ 11, 12 and 13 can be used as ordinary GPIO ports</li~~></ol></li></ol~~>

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

|-

|-

| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"| '''5V'''| style="text-align: ~~left~~center;"| '''1'''

|-

| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"| '''GND'''| style="text-align: ~~left~~center;"| '''2'''

|-

| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"| '''USB2-DM'''| style="text-align: ~~left~~center;"| '''3'''

|-

| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"| '''USB2-DP'''| style="text-align: ~~left~~center;"| '''4'''

|-

| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"| '''USB3-DM'''| style="text-align: ~~left~~center;"| '''5'''

|-

| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"| '''USB3-DP'''| style="text-align: ~~left~~center;"| '''6'''

|-

| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"| '''LINEOUTR'''| style="text-align: ~~left~~center;"| '''7'''

|-

| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"| '''LINEOUTL'''| style="text-align: ~~left~~center;"| '''8'''

|-

| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"| '''TV-OUT'''| style="text-align: ~~left~~center;"| '''9'''

|-

| style="text-align: ~~left~~center;"| '''65'''| style="text-align: ~~left~~center;"| '''PC1'''| style="text-align: ~~left~~center;"| '''10'''

|-

| style="text-align: ~~left~~center;"| '''272'''| style="text-align: ~~left~~center;"| '''PI16'''| style="text-align: ~~left~~center;"| '''11'''

|-

| style="text-align: ~~left~~center;"| '''262'''| style="text-align: ~~left~~center;"| '''PI6'''| style="text-align: ~~left~~center;"| '''12'''

|-

|}

</ol>

</li></ol>

~~~~

== 26 Pin Interface Pin Description ==

<li>For the order of the 26-pin interface pins on the Orange Pi Zero 3 development board, please refer to the silkscreen diagram on the development board

[[File:~~media/image171~~zero3-img171-2.png~~|389x125px~~]]</li><li>The functions of the 26 pin interface pins on the development board are shown in the table below</p~~></li></ol~~>

<div style="display: flex;">{| class="wikitable" style="width:380px;margin-right: 20px;"

|-

|-

| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"| '''3.3V'''| style="text-align: ~~left~~center;"| '''1'''|~~| style="text-align: left;"| '''2'''| style="text-align: left;"| '''5V'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| style="text-align: ~~left~~center;"| '''229'''| style="text-align: ~~left~~center;"| '''PH5'''| style="text-align: ~~left~~center;"| '''TWI3-SDA'''| style="text-align: ~~left~~center;"| '''3'''|~~| style="text-align: left;"| '''4'''| style="text-align: left;"| '''5V'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| style="text-align: ~~left~~center;"| '''228'''| style="text-align: ~~left~~center;"| '''PH4'''| style="text-align: ~~left~~center;"| '''TWI3-SCK'''| style="text-align: ~~left~~center;"| '''5'''|~~| style="text-align: left;"| '''6'''| style="text-align: left;"| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| style="text-align: ~~left~~center;"| '''73'''| style="text-align: ~~left~~center;"| '''PC9'''| style="text-align: ~~left~~center;"| '''PC9'''| style="text-align: ~~left~~center;"| '''7~~'''~~|~~| style="text-align: left;"| '''8'''| style="text-align: left;"| '''UART5_TX'''| style="text-align: left;"| '''PH2'''| style="text-align: left;"| '''226~~'''

|-

| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"| '''GND'''| style="text-align: ~~left~~center;"| '''9~~'''~~|~~| style="text-align: left;"| '''10'''| style="text-align: left;"| '''UART5_RX'''| style="text-align: left;"| '''PH3'''| style="text-align: left;"| '''227~~'''

|-

| style="text-align: ~~left~~center;"| '''70'''| style="text-align: ~~left~~center;"| '''PC6'''| style="text-align: ~~left~~center;"| '''PC6'''| style="text-align: ~~left~~center;"| '''11~~'''~~|~~| style="text-align: left;"| '''12'''| style="text-align: left;"| '''PC11'''| style="text-align: left;"| '''PC11'''| style="text-align: left;"| '''75~~'''

|-

| style="text-align: ~~left~~center;"| '''69'''| style="text-align: ~~left~~center;"| '''PC5'''| style="text-align: ~~left~~center;"| '''PC5'''| style="text-align: ~~left~~center;"| '''13'''|~~| style="text-align: left;"| '''14'''| style="text-align: left;"| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| style="text-align: ~~left~~center;"| '''72'''| style="text-align: ~~left~~center;"| '''PC8'''| style="text-align: ~~left~~center;"| '''PC8'''| style="text-align: ~~left~~center;"| '''15~~'''~~|~~| style="text-align: left;"| '''16'''| style="text-align: left;"| '''PC15'''| style="text-align: left;"| '''PC15'''| style="text-align: left;"| '''79~~'''

|-

| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"| '''3.3V'''| style="text-align: ~~left~~center;"| '''17'''|-| style="text-align: center;"| '''231'''| style="text-align: center;"| '''PH7'''| style="text-align: center;"| '''SPI1_MOSI'''| style="text-align: center;"| '''19'''|-| style="text-align: center;"| '''232'''| style="text-align: center;"| '''PH8'''| style="text-align: center;"| '''SPI1_MISO'''| style="text-align: center;"| '''21'''|-| style="text-align: center;"| '''230'''| style="text-align: center;"| '''PH6'''| style="text-align: center;"| '''SPI1_CLK'''| style="text-align: center;"| '''23'''|-| style="text-align: center;"|| style="text-align: center;"|| style="text-align: center;"| '''GND'''| style="text-align: center;"| '''25'''|}{| class="wikitable" style="width:380px;"|-| style="text-align: center;"| '''Pin'''| style="text-align: center;"| '''Function'''| style="text-align: center;"| '''GPIO'''| style="text-align: center;"| '''GPIO S/N'''|-| style="text-align: center;"| '''2'''| style="text-align: center;"| '''5V'''| style="text-align: center;"|| style="text-align: center;"||-| style="text-align: center;"| '''4'''| style="text-align: center;"| '''5V'''| style="text-align: center;"|| style="text-align: center;"||-| style="text-align: center;"| '''6'''| style="text-align: center;"| '''GND'''| style="text-align: center;"|| style="text-align: center;"||-| style="text-align: center;"| '''8'''| style="text-align: center;"| '''UART5_TX'''| style="text-align: center;"| '''PH2'''| style="text-align: center;"| '''226'''|-| style="text-align: center;"| '''10'''| style="text-align: center;"| '''UART5_RX'''| style="text-align: center;"| '''PH3'''| style="text-align: center;"| '''227'''|-| style="text-align: center;"| '''12'''| style="text-align: center;"| '''PC11'''| style="text-align: center;"| '''PC11'''| style="text-align: center;"| '''75'''|-| style="text-align: center;"| '''14'''| style="text-align: center;"| '''GND'''| style="text-align: center;"|| style="text-align: center;"||-| style="text-align: center;"| '''16'''| style="text-align: center;"| '''PC15'''| style="text-align: center;"| '''PC15'''| style="text-align: center;"| '''79'''|-| style="text-align: ~~left~~center;"| '''18'''| style="text-align: ~~left~~center;"| '''PC14'''| style="text-align: ~~left~~center;"| '''PC14'''| style="text-align: ~~left~~center;"| '''78'''

|-

| style="text-align: ~~left;"| '''231'''| style="text-align: left;"| '''PH7'''| style="text-align: left;"| '''SPI1_MOSI'''| style="text-align: left;"| '''19'''~~|~~| style="text-align: left~~center;"| '''20'''| style="text-align: ~~left~~center;"| '''GND'''| style="text-align: ~~left~~center;"|| style="text-align: ~~left~~center;"|

|-

| style="text-align: ~~left;"| '''232'''| style="text-align: left;"| '''PH8'''| style="text-align: left;"| '''SPI1_MISO'''| style="text-align: left;"| '''21'''~~|~~| style="text-align: left~~center;"| '''22'''| style="text-align: ~~left~~center;"| '''PC7'''| style="text-align: ~~left~~center;"| '''PC7'''| style="text-align: ~~left~~center;"| '''71'''

|-

| style="text-align: ~~left;"| '''230'''| style="text-align: left;"| '''PH6'''| style="text-align: left;"| '''SPI1_CLK'''| style="text-align: left;"| '''23'''~~|~~| style="text-align: left~~center;"| '''24'''| style="text-align: ~~left~~center;"| '''SPI1_CS'''| style="text-align: ~~left~~center;"| '''PH9'''| style="text-align: ~~left~~center;"| '''233'''

|-

| style="text-align: ~~left;"|| style="text-align: left;"|| style="text-align: left;"| '''GND'''| style="text-align: left;"| '''25'''~~|~~| style="text-align: left~~center;"| '''26'''| style="text-align: ~~left~~center;"| '''PC10'''| style="text-align: ~~left~~center;"| '''PC10'''| style="text-align: ~~left~~center;"| '''74'''

|}

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

<li>3) There are a total of 17 GPIO ports in the 26pin interface, and the voltage of all GPIO ports is '''3.3v'''</li></ol>

== How to install wiringOP ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that wiringOP has been pre-installed in the linux image released by Orange Pi. Unless the code of wiringOP is updated, there is no need to re-download, compile and install, just use it directly.'''

'''The storage path of the compiled wiringOP deb package in orangepi-build is:'''

'''orangepi-build/external/cache/debs/arm64/wiringpi_x.xx.deb'''

'''After entering the system, you can run the gpio readall command. If you can see the following output, it means that wiringOP has been pre-installed and can be used normally.'''</big>

[[File:~~media/image172~~zero3-img172.png|~~575x365px~~780px|center]]

<big>'''wiringOP is currently mainly adapted to the functions of setting GPIO port input and output, setting GPIO port output high and low levels, and setting up and down pull-down resistors. Functions such as hardware PWM are not available.'''</big>|}

<li>Download the code of wiringOP

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

|-

|

orangepi@orangepi:~$ '''sudo apt update'''

orangepi@orangepi:~$ '''sudo apt install -y git'''

orangepi@orangepi:~$ '''git clone https://github.com/orangepi-xunlong/wiringOP.git -b next'''

|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the source code needs to download the code of the wiringOP next branch, please don't miss the -b next parameter.''''''If you have problems downloading the code from GitHub, you can directly use the wiringOP source code that comes with the Linux image, and the storage location is: /usr/src/wiringOP.'''</big>|}</li>

<li>Compile and install wiringOP

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

|-

|

orangepi@orangepi:~$ '''cd wiringOP'''

orangepi@orangepi:~/wiringOP$ '''sudo ./build clean'''

orangepi@orangepi:~/wiringOP$ '''sudo ./build'''|}</li>

<li>Test the output of the gpio readall command as follows

<li>There is a one-to-one correspondence between pins 1 to 26 and 26 ~~>~~ Pins on the development board</li>

<li>Pin 27 corresponds to pin 10 of 13pin on the development board</li>

<li>Pin 29 corresponds to pin 11 of 13pin on the development board</li>

<li>Pin 31 corresponds to pin 12 of 13pin on the development board</li>

<li>Pin 33 corresponds to pin 13 of 13pin on the development board</li>

<li>'''Pins 28, 30, 32, and 34 are empty, please ignore them'''[[File:~~media/image172~~zero3-img172.png~~|575x365px~~]]</li></ol>

</li></ol>

== 26pin interface GPIO, I2C, UART, SPI and PWM test ==

<li>The following takes pin 7—corresponding to GPIO as PC9—corresponding to wPi number 2—as an example to demonstrate how to set the high and low levels of the GPIO port

[[File:~~media/image173~~zero3-img173.png~~|576x128px~~]]</li>

<li>First set the GPIO port to output mode, where the third parameter requires the serial number of the wPi corresponding to the input pin

{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio mode 2 out'''|}</li><li>Then set the GPIO port to output a 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{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio write 2 0'''|}

Use gpio readall to see that the value (V) of pin 7 has changed to 0

[[File:~~media/image174~~zero3-img174.png~~|575x128px~~]]</li>

<li>Then set the GPIO port to output a high level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is 3.3v, it means that the high level is set successfully.

{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio write 2 1'''|}

Use gpio readall to see that the value (V) of pin 7 has changed to 1

[[File:~~media/image175~~zero3-img175.png~~|575x130px~~]]</li>

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

=== 26 How to set ~~the~~ pull-up and pull-down ~~resistance of~~ resistors on 26 pin GPIO ~~port~~ ports ===

<li>The following takes pin 7—the corresponding GPIO is PC9—the corresponding wPi number is 2—as an example to demonstrate how to set the pull-up and pull-down resistors of the GPIO port

[[File:~~media/image173~~zero3-img173.png~~|576x128px~~]]</li>

<li>First, you need to set the GPIO port to the input mode, and the third parameter needs to be the serial number of the wPi corresponding to the input pin

{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio mode 2 in'''|}</li>

<li>After setting to input mode, execute the following command to set the GPIO port to pull-up mode

{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio mode 2 up'''|}</li>

<li>Then enter the following command to read the level of the GPIO port, if the level is 1, it means that the pull-up mode is set successfully

{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio read 2''''''1'''|}</li>

<li>Then execute the following command to set the GPIO port to pull-down mode

{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio mode 2 down'''|}</li>

<li>Then enter the following command to read the level of the GPIO port, if the level is 0, the pull-down mode is set successfully

{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio read 2''''''0'''|}</li></ol>

=== 26pin SPI test ===

<li>According to the schematic diagram of the 26pin interface, the available spi is spi1

[[File:~~media/image176~~zero3-img176.png~~|565x209px~~]]</li>

<li>The spi1 is disabled by default in the Linux system and needs to be manually enabled before it can be used. The steps to open are as follows:

<li>First run '''orangepi-config''', normal users remember to add ~~>~~ '''sudo''' permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li>

<li>Then select '''System'''

[[File:~~media/image85~~zero3-img85.png~~|398x194px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image86~~zero3-img86.png~~|393x202px~~]]</li><li>d. 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 '''spi1-cs1-spidev'''[[File:~~media/image177~~zero3-img177.png~~|392x57px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image88~~zero3-img88.png~~|397x92px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image89~~zero3-img89.png~~|395x91px~~]]</li><li>Then select '''<Reboot>''' to restart the system to make the ~~>~~ configuration take effect[[File:~~media/image90~~zero3-img90.png~~|374x187px~~]]</li></ol>

</li>

<li>Then check whether there is a '''spidev1.1''' device node in the Linux system. If it exists, it means that the configuration of SPI1 has taken effect

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

|-

|

orangepi@orangepi:~$ '''ls /dev/spidev1*'''

/dev/spidev1.1|}</li>

<li>Do not short-circuit the mosi and miso pins of SPI1 first, the output result of running spidev_test is as follows, you can see that the data of TX and RX are inconsistent

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

|-

|

orangepi@orangepi:~$ '''sudo spidev_test -v -D /dev/spidev1.1'''

spi mode: 0x0

bits per word: 8

max speed: 500000 Hz (500 KHz)

TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF | ............................….|}</li>

<li>Then short the two pins of mosi (the 19th pin in the 26pin interface) and miso (the 21st pin in the 26pin interface) of SPI1, and then run the output of spidev_test as follows, you can see the sending and receiving same data

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

|-

|

orangepi@orangepi:~$ '''sudo spidev_test -v -D /dev/spidev1.1'''

spi mode: 0x0

bits per word: 8

max speed: 500000 Hz (500 KHz)

TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.RX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.|}</li></ol>

=== 26pin I2C test ===

<li>According to the schematic diagram of 26pin, the available i2c is i2c3

[[File:~~media/image178~~zero3-img178.png~~|575x204px~~]]</li>

<li>i2c3 is disabled by default in the Linux system, and it needs to be manually enabled before it can be used. The steps to open are as follows:

<li>First run '''orangepi-config''', normal users remember to add ~~>~~ '''sudo''' permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li>

<li>Then select '''System'''

[[File:~~media/image85~~zero3-img85.png~~|390x190px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image86~~zero3-img86.png~~|393x202px~~]]</li><li>d. 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 '''ph-i2c3'''[[File:~~media/image179~~zero3-img179.png~~|392x57px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image88~~zero3-img88.png~~|395x91px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image89~~zero3-img89.png~~|395x91px~~]]</li><li>Then select '''<Reboot>''' to restart the system to make the ~~>~~ configuration take effect[[File:~~media/image90~~zero3-img90.png~~|374x187px~~]]</li></ol>

</li>

<li>After starting the linux system, first confirm that there is an i2c3 device node under /dev

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

|-

|

orangepi@orangepi:~$ '''ls /dev/i2c-3'''

'''/dev/i2c-3'''|}</li>

<li>Then start testing i2c, first install i2c-tools

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

|-

|

orangepi@orangepi:~$ '''sudo apt-get update'''

orangepi@orangepi:~$ '''sudo apt-get install -y i2c-tools'''|}</li>

<li>Then connect an i2c device to the i2c3 pin of the 26pin connector

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Please select the 5V and 3.3V pins according to the specific i2c device, and the voltage value required by different i2c devices may be different.'''</~~li></ol~~big>|}

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

|-

| style="text-align: ~~left~~center;"| '''sda pin'''| style="text-align: ~~left~~center;"| '''Corresponding to pin 3 in 26pin'''

|-

| style="text-align: ~~left~~center;"| '''sck pin'''| style="text-align: ~~left~~center;"| '''Corresponding to pin 5 in 26pin'''

|-

| style="text-align: ~~left~~center;"| '''5v pin'''| style="text-align: ~~left~~center;"| '''Corresponding to pin 2 in 26pin'''

|-

| style="text-align: ~~left~~center;"| '''3.3v pin'''| style="text-align: ~~left~~center;"| '''Corresponding to pin 1 in 26pin'''

|-

| style="text-align: ~~left~~center;"| '''gnd pin'''| style="text-align: ~~left~~center;"| '''Corresponding to pin 6 in 26pin'''

|}

</li></ol>

<li>Then use the '''i2cdetect -y 3''' command, if the address of the connected i2c device can be detected, it means that i2c can be used normally

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Different i2c device addresses are different, the address 0x50 in the figure below is just an example. Please refer to what you actually see.'''</big>|}

[[File:~~media/image180~~zero3-img180.png~~|383x151px|选区_460~~]]

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

=== 26pin UART test ===

<li>According to the schematic diagram of the 26pin interface, the available uart is uart5

[[File:~~media/image181~~zero3-img181.png~~|575x203px~~]]</li><li>~~uart5~~ Uart5 is disabled by default in the Linux system, and it needs to be opened manually to use it. The steps to open are as follows:

<li>First run '''orangepi-config''', normal users remember to add ~~>~~ '''sudo''' permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li>

<li>Then select '''System'''

[[File:~~media/image85~~zero3-img85.png~~|398x194px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image86~~zero3-img86.png~~|393x202px~~]]</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 '''ph-uart5'''[[File:~~media/image182~~zero3-img182.png~~|400x60px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image88~~zero3-img88.png~~|397x92px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image89~~zero3-img89.png~~|395x91px~~]]</li><li>Then select '''<Reboot>''' to restart the system to make the ~~>~~ configuration take effect[[File:~~media/image90~~zero3-img90.png~~|374x187px~~]]</li></ol>

</li>

<li>After entering the linux system, first confirm whether there is a uart5 device node under '''/dev'''

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the linux5.4 system is /dev/ttyAS5.'''</big>|}{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''ls /dev/ttyS5'''

/dev/ttyS5|}</li><li>Then start to test the uart5 interface, first use the DuPont line to short the rx and tx of the uart5 interface to be tested</li~~></ol~~>

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

|-

|

| style="text-align: ~~left~~center;"| uart5

|-

| tx pin

| style="text-align: ~~left~~center;"| Corresponding to pin 8 of 26pin

|-

| rx pin

| style="text-align: ~~left~~center;"| Corresponding to pin 10 of 26pin

|}

</ol>

<li>Use the '''gpio''' command in wiringOP to test the loopback function of the serial port as shown below. If you can see the following print, it means that the serial port communication is normal

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gpio serial /dev/ttyS5       # linux-6.1 test command'''orangepi@orangepi:~$ '''gpio serial /dev/ttyAS5       # linux-5.4 test command'''

Out: 0: -> 0

Out: 1: -> 1

Out: 2: -> 2

Out: 3: -> 3^C|}</li></ol>

=== PWM test method ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The development board can use up to 4 channels of PWM, and the positions of their pins are shown in the figure below:'''</big>

[[File:~~media/image183~~zero3-img183-1.png|~~388x180px~~center]]|}

<li>In the Linux system, the pwm is closed by default, and it needs to be opened manually to use it. The steps to open are as follows:

<li>First run '''orangepi-config''', normal users remember to add ~~>~~ '''sudo''' permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li>

<li>Then select '''System'''

[[File:~~media/image85~~zero3-img85.png~~|398x194px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image86~~zero3-img86.png~~|393x202px~~]]</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 configuration corresponding to pwm{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Since the RX and TX pins of UART5 in the PWM1, PWM2 and 26pin interfaces are multiplexed, please make sure that the UART5 configuration is not selected (do not check ph-uart5) when turning on PWM1 and PWM2 (you need to select ph-pwm12).''''''PWM3, PWM4 and the TX and RX pins in the debug serial port are multiplexed, so when using PWM3 and PWM4 (need to select ph-pwm34), please turn off the configuration of UART0 (need to select disable-uart0), after turning off UART0 The debug serial port cannot be used.'''</big>|}[[File:~~media/image184~~zero3-img184.png~~|402x156px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image88~~zero3-img88.png~~|397x92px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image89~~zero3-img89.png~~|395x91px~~]]</li><li>Then select '''<Reboot>''' to restart the system to make the ~~>~~ configuration take effect[[File:~~media/image90~~zero3-img90.png~~|374x187px~~]]</li></ol>

</li>

<li>After restarting, the PWM test can be started

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Please execute the following commands under the root user.'''</big>|}

<li>Enter the following command on the command line to make pwm1 ~~>~~ output a 50Hz ~~rectangular~~ square wave{| class="wikitable" style="width:800px;" |-|

root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip0/export'''

root@orangepi:~# '''echo 20000000 > /sys/class/pwm/pwmchip0/pwm1/period'''

root@orangepi:~# '''echo 1000000 > /sys/class/pwm/pwmchip0/pwm1/duty_cycle'''

root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip0/pwm1/enable'''|}</li><li>Enter the following command on the command line to make pwm2 ~~>~~ output a 50Hz square wave</li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-|

root@orangepi:~# '''echo 2 > /sys/class/pwm/pwmchip0/export'''

root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip0/pwm2/enable'''

|}</ol>

<li>Enter the following command on the command line to make pwm3 output ~~>~~ a 50Hz ~~rectangular~~ square wave</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-|

root@orangepi:~# '''echo 3 > /sys/class/pwm/pwmchip0/export'''

root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip0/pwm3/enable'''

|}</ol>

<li>Enter the following command on the command line to make pwm4 output ~~>~~ a 50Hz square wave</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-|

root@orangepi:~# '''echo 4 > /sys/class/pwm/pwmchip0/export'''

root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip0/pwm4/enable'''

|}

[[File:~~media/image185~~zero3-img185.~~jpeg|574x344px|69D96433378187B10005CDD2A52881B0~~png]]

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

== How to install and use wiringOP-Python ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''wiringOP-Python is the Python language version of wiringOP, which is used to operate the hardware resources of the development board, such as GPIO, I2C, SPI and UART, in the Python program.'''

'''In addition, please note that all the following commands are operated under the root user.'''</big>|}

<li>First install the dependency package

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

|-

|

root@orangepi:~# '''sudo apt-get update'''

root@orangepi:~# '''sudo apt-get -y install git swig python3-dev python3-setuptools'''|}</li>

<li>Then use the following command to download the source code of wiringOP-Python

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the following git clone --recursive 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 errors due to network problems.''' '''If you have problems downloading the code from GitHub, you can directly use the wiringOP-Python source code that comes with the Linux image, and the storage location is: /usr/src/wiringOP-Python'''</big>|}{| class="wikitable" style="width:800px;" |-|

root@orangepi:~# '''git clone --recursive https://github.com/orangepi-xunlong/wiringOP-Python -b next'''

root@orangepi:~# '''cd wiringOP-Python'''

root@orangepi:~/wiringOP-Python# '''git submodule update --init --remote'''|}</li>

<li>Then use the following command to compile wiringOP-Python and install it into the Linux system of the development board

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

|-

|

root@orangepi:~# '''cd wiringOP-Python'''

root@orangepi:~/wiringOP-Python# '''python3 generate-bindings.py > bindings.i'''

root@orangepi:~/wiringOP-Python# '''sudo python3 setup.py install'''|}</li><li>Then enter the following command, if there is help information output, it means that wiringOP-Python is installed successfully, press the '''q''' key to exit the help information interface</li~~></ol~~>

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

|-

|

root@orangepi:~/wiringOP-Python# '''python3 -c "import wiringpi; help(wiringpi)"'''

Help on module wiringpi:

NAME

:wiringpi

DESCRIPTION

: # This file was automatically generated by SWIG (http://www.swig.org).

: # Version 4.0.2

: #

: # Do not make changes to this file unless you know what you are doing--modify ~~# the SWIG interface file instead.~~

: # the SWIG interface file instead.

|}

</ol>

<li>The steps to test whether wiringOP-Python is successfully installed under the python command line are as follows:

<li>First use the python3 command to enter the command line mode of ~~>~~ python3</li~~></ol></li></ol~~>

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

|-

|

root@orangepi:~# '''python3'''

|}

<li>Then import the python module of wiringpi</li></ol>

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

|-

|

>>> '''import wiringpi;'''

|}</ol>

<li>Finally, enter the following command to view the help information of ~~>~~ wiringOP-Python, and press the q key to exit the help information ~~>~~ interface</li~~></ol~~>

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

|-

|

>>> '''help(wiringpi)'''

Help on module wiringpi:

NAME

:wiringpi

DESCRIPTION

: # This file was automatically generated by SWIG (http://www.swig.org). : # Version 4.0.2

: # ~~Version 4.0.2~~

: #Do not make changes to this file unless you know what you are doing--modify

: # ~~Do not make changes to this~~ the SWIG interface file ~~unless you know what you are doing--modify~~instead.

~~# the SWIG interface file instead.~~

CLASSES

:builtins.object

::GPIO

::I2C

::Serial

::nes

~~class GPIO(builtins.object)~~

:class GPIO(builtins.object) :| GPIO(pinmode=0) :|

|

>>>

|}

</ol>

</li></ol>

~~~~

=== 26pin GPIO port test ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''wiringOP-Python is the same as wiringOP, you can also determine which GPIO pin to operate by specifying the wPi number, because there is no command to check the wPi number in wiringOP-Python, so you can only check the board wPi number and physical Correspondence between pins.'''</big>[[File:~~media/image172~~zero3-img172.png~~|575x365px~~]]|}

<li>The following takes pin 7—the corresponding GPIO is PC9—the corresponding wPi number is 2—as an example to demonstrate how to set the high and low levels of the GPIO port

[[File:~~media/image173~~zero3-img173.png~~|576x128px~~]]</li>

<li>The steps to test directly with the command are as follows:

<li>First set the GPIO port to output mode, where 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{| class="wikitable" style="width:800px;" |-|

root@orangepi:~/wiringOP-Python# '''python3 -c "import wiringpi; \'''

'''from wiringpi import GPIO; wiringpi.wiringPiSetup() ; \'''

'''wiringpi.pinMode(2, GPIO.OUTPUT) ; "'''|}</li><li>Then set the GPIO port to output 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.{| class="wikitable" style="width:800px;" |-|

root@orangepi:~/wiringOP-Python# '''python3 -c "import wiringpi; \'''

'''from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\'''

'''wiringpi.digitalWrite(2, GPIO.LOW)"'''|}</li><li>Then set the GPIO port to output a high level. After setting, ~~>~~ you can use a multimeter to measure the voltage value of the ~~>~~ pin. If it is 3.3v, it means that the high level is set ~~>~~ successfully.{| class="wikitable" style="width:800px;" |-|

root@orangepi:~/wiringOP-Python# '''python3 -c "import wiringpi; \'''

'''from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\'''

'''wiringpi.digitalWrite(2, GPIO.HIGH)"'''|}</li></ol>

</li>

<li>The steps to test in the command line of python3 are as follows:

<li>First use the python3 command to enter the command line mode of ~~>~~ python3{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''python3'''|}</li>

<li>Then import the python module of wiringpi

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

|-

|

>>> '''import wiringpi'''

>>> '''from wiringpi import GPIO'''|}</li><li>Then set the GPIO port to output mode, where 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{| class="wikitable" style="width:800px;" |-|

>>> '''wiringpi.wiringPiSetup()'''

0

>>> '''wiringpi.pinMode(2, GPIO.OUTPUT)'''|}</li><li>Then set the GPIO port to output 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.{| class="wikitable" style="width:800px;" |-| >>> '''wiringpi.digitalWrite(2, GPIO.LOW)'''|}</li><li>Then set the GPIO port to output a high level. After setting, ~~>~~ you can use a multimeter to measure the voltage value of the ~~>~~ pin. If it is 3.3v, it means that the high level is set ~~>~~ successfully.{| class="wikitable" style="width:800px;" |-| >>> '''wiringpi.digitalWrite(2, GPIO.HIGH)'''|}</li></ol>

</li>

<li>The method of wiringOP-Python to set GPIO high and low levels in python code can refer to the '''blink.py''' test program in the examples below. The '''blink.py''' test program will set the voltage of all GPIO ports in the 26 pins of the development board to change continuously.

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

|-

|

root@orangepi:~/wiringOP-Python# '''cd examples'''

root@orangepi:~/wiringOP-Python/examples# '''ls blink.py'''

'''blink.py'''

root@orangepi:~/wiringOP-Python/examples'''# python3 blink.py'''|}</li></ol>

=== 26pin SPI test ===

<li>According to the schematic diagram of the 26pin interface, the available spi is spi1

[[File:~~media/image176~~zero3-img176.png~~|565x209px~~]]</li>

<li>The spi1 is disabled by default in the Linux system and needs to be manually enabled before it can be used. The steps to open are as follows:

<li>First run '''orangepi-config''', normal users remember to add ~~>~~ '''sudo''' permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li>

<li>Then select '''System'''

[[File:~~media/image85~~zero3-img85.png~~|398x194px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image86~~zero3-img86.png~~|393x202px~~]]</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 '''spi1-cs1-spidev'''[[File:~~media/image177~~zero3-img177.png~~|392x57px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image88~~zero3-img88.png~~|397x92px~~]]</li>

<li>Then select '''<Back>'''然后选择'''<Back>'''

[[File:~~media/image89~~zero3-img89.png~~|395x91px~~]]</li><li>Then select '''<Reboot>''' to restart the system to make the ~~>~~ configuration take effect[[File:~~media/image90~~zero3-img90.png~~|374x187px~~]]</li></ol>

</li>

<li>Then check whether there is a '''spidev1.1''' device node in the Linux system. If it exists, it means that the configuration of SPI1 has taken effect

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

|-

|

orangepi@orangepi:~$ '''ls /dev/spidev1*'''

/dev/spidev1.1|}</li>

<li>Then you can use the '''spidev_test.py''' program in the examples to test the loopback function of the SPI. The '''spidev_test.py''' program needs to specify the following two parameters:

<li>'''--channel''': Specify the channel number of SPI</li>

<li>'''--port''': ~~specify~~ Specify the port number of SPI</li></ol>

</li>

<li>Do not short-circuit the mosi and miso pins of SPI1, the output result of running spidev_test.py is as follows, you can see that the data of TX and RX are inconsistent

</li> {| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''cd examples'''</p~~></li></ol~~>

root@orangepi:~/wiringOP-Python/examples# '''python3 spidev_test.py \'''

Opening device /dev/spidev1.1

TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…| ~~RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |.............….~~|

RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |.............….|

|}

</ol>

<li>Then use the Dupont wire to short-circuit the two pins of txd (pin 19 in the 26pin interface) and rxd (pin 21 in the 26pin interface) of SPI1 and then run the output of spidev_test.py as follows, you can see The data sent and received are the same, indicating that the SPI1 loopback test is normal

</li> {| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''cd examples'''</p~~></li></ol~~>

root@orangepi:~/wiringOP-Python/examples# '''python3 spidev_test.py \'''

Opening device /dev/spidev1.1

TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…|

RX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…||}</ol>

~~~~

=== 26pin I2C test ===

<li>According to the schematic diagram of 26pin, the available i2c is i2c3

[[File:~~media/image178~~zero3-img178.png~~|575x204px~~]]</li>

<li>i2c3 is disabled by default in the Linux system, and it needs to be manually enabled before it can be used. The steps to open are as follows:

<li>First run '''orangepi-config''', normal users remember to add ~~>~~ '''sudo''' permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li>

<li>Then select '''System'''

[[File:~~media/image85~~zero3-img85.png~~|398x194px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image86~~zero3-img86.png~~|393x202px~~]]</li><li>d. 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 '''ph-i2c3'''[[File:~~media/image179~~zero3-img179.png~~|401x59px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image88~~zero3-img88.png~~|397x92px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image89~~zero3-img89.png~~|395x91px~~]]</li><li>Then select '''<Reboot>''' to restart the system to make the ~~>~~ configuration take effect[[File:~~media/image90~~zero3-img90.png~~|374x187px~~]]</li></ol>

</li>

<li>After starting the linux system, first confirm that there is an i2c3 device node under /dev

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

|-

|

orangepi@orangepi:~$ '''ls /dev/i2c-3'''

'''/dev/i2c-3'''|}</li>

<li>Then start testing i2c, first install i2c-tools

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

|-

|

orangepi@orangepi:~$ '''sudo apt-get update'''

orangepi@orangepi:~$ '''sudo''' '''apt-get install -y i2c-tools'''|}</li>

<li>Then connect an i2c device to the i2c3 pin of the 26pin connector, here we take the DS1307 RTC module as an example

[[File:~~media/image186~~zero3-img186.png~~|180x153px~~]]</p~~></li></ol~~>

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

|-

| style="text-align: ~~left~~center;"| '''Pins of the RTC module'''| style="text-align: ~~left~~center;"| '''The pin corresponding to the 26pin of the development board'''

|-

| style="text-align: ~~left~~center;"| '''5V'''| style="text-align: ~~left~~center;"| '''Pin 2'''

|-

| style="text-align: ~~left~~center;"| '''GND'''| style="text-align: ~~left~~center;"| '''Pin 6'''

|-

| style="text-align: ~~left~~center;"| '''SDA'''| style="text-align: ~~left~~center;"| '''Pin 3'''

|-

| style="text-align: ~~left~~center;"| '''SCL'''| style="text-align: ~~left~~center;"| '''Pin 5'''

|}

</li></ol>

<li>Then use the '''i2cdetect -y 3''' command, if the address of the connected i2c device can be detected, it means that the i2c device is connected correctly</li>~~</ol>~~ ~~[[File:media/image187.png|388x203px]]~~

[[File:zero3-img187.png]]

</ol>

<li>Then you can run the '''ds1307.py''' test program in the '''examples''' to read the RTC time

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

|-

|

root@orangepi:~/wiringOP-Python# '''cd examples'''

root@orangepi:~/wiringOP-Python/examples# '''python3 ds1307.py --device \'''

Thu 2022-06-16 04:35:48

^C

exit|}</li></ol>

=== 26pin UART test ===

<li>According to the schematic diagram of the 26pin interface, the available uart is uart5

[[File:~~media/image181~~zero3-img181.png~~|575x203px~~]]</li>

<li>uart5 is disabled by default in the Linux system, and it needs to be opened manually to use it. The steps to open are as follows:

<li>First run '''orangepi-config''', normal users remember to add ~~>~~ '''sudo''' permission{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li>

<li>Then select '''System'''

[[File:~~media/image85~~zero3-img85.png~~|398x194px~~]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image86~~zero3-img86.png~~|393x202px~~]]</li><li>d. 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 '''ph-uart5'''[[File:~~media/image182~~zero3-img182.png~~|400x60px~~]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image88~~zero3-img88.png~~|397x92px~~]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image89~~zero3-img89.png~~|395x91px~~]]</li><li>Then select '''<Reboot>''' to restart the system to make the ~~>~~ configuration take effect[[File:~~media/image90~~zero3-img90.png~~|374x187px~~]]</li></ol>

</li>

<li>After entering the linux system, first confirm whether there is a uart5 device node under '''/dev'''

~~'''Note that the linux5.4 system is /dev/ttyAS5.'''orangepi@orangepi:~$ '''ls /dev/ttyS5'''/dev/ttyS5</li><li>Then start to test the uart5 interface, first use the DuPont line to short the rx and tx of the uart5 interface to be tested</li></ol>~~ {| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

| <big>'''Note that the linux5.4 system is /dev/ttyAS5.'''</big>|}{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ls /dev/ttyS5'''/dev/ttyS5|}</li><li>Then start to test the uart5 interface, first use the DuPont line to short the rx and tx of the uart5 interface to be tested {| class="wikitable" style="width:800px;text-align: center;"|-|| style="text-align: ~~left~~center;"| '''uart5'''

|-

| '''tx pin'''

| style="text-align: ~~left~~center;"| '''Corresponding to pin 8 in 26pin'''

|-

| '''rx pin'''

| style="text-align: ~~left~~center;"| '''Corresponding to pin 10 in 26pin'''

|}

</li></ol>

<li>Finally, you can run the '''serialTest.py''' program in the examples to test the loopback function of the serial port. If you can see the following print, it means that the loopback test of the serial port is normal

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

|-

|

root@orangepi:~/wiringOP-Python# '''cd examples'''

root@orangepi:~/wiringOP-Python/examples# '''python3 serialTest.py --device "/dev/ttyS5" # linux6.1使用'''

Out: 3: -> 3

Out: 4:^C

exit|}</li></ol>

== Hardware Watchdog Test ==

The watchdog_test program is pre-installed in the linux system released by Orange PI, which can be tested directly.。

The method of running the watchdog_test program is shown ~~below：~~below:

<li>The second parameter 10 indicates the counting of the door dog. If the dog is not fed in this time, the system will restart</li>

<li>We can feed the dog by pressing any key (except ESC) on the keyboard. After the dog is fed, the program will print a line of Keep Alive to indicate that the dog is successful.

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

|-

|

orangepi@orangepi:~$ '''sudo watchdog_test 10'''

open success

keep alive

keep alive|}</li></ol>

== Check the chipid of the H618 chip ==

The command of the H618 chip Chipid is shown below. The chipid of each chip is different, so you can use Chipid to distinguish multiple development boards.

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

|-

|

orangepi@orangepi:~$ '''cat /sys/class/sunxi_info/sys_info | grep "chipid"'''

sunxi_chipid : 338020004c0048080147478824681ed1

|}

== Python related instructions ==

=== Python source code compilation and installation method ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If the Python version in the Ubuntu or Debian system software warehouse does not meet the requirements of development, if you want to use the latest version of Python, you can use the following method to download the source code package of Python to compile and install the latest version of Python.'''

'''The following demonstration is the latest version of the compilation and installation of Python3.9. If you want to compile and install other versions of Python, the method is the same (need to download the source code corresponding to the Python you want to install).'''</big>|}

<li>First install the dependency package required to compile Python

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

|-

|

orangepi@orangepi:~$ '''sudo apt-get update'''

orangepi@orangepi:~$ '''sudo apt-get install -y build-essential zlib1g-dev \'''

'''libncurses5-dev libgdbm-dev libnss3-dev libssl-dev libsqlite3-dev \'''

'''libreadline-dev libffi-dev curl libbz2-dev'''|}</li>

<li>Then download the latest version of the Python3.9 source code and decompress it

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

|-

|

orangepi@orangepi:~$ '''wget \'''

[https://www.python.org/ftp/python/3.9.10/Python-3.9.10.tgz '''https://www.python.org/ftp/python/3.9.10/Python-3.9.10.tgz''']

orangepi@orangepi:~$ '''tar xvf Python-3.9.10.tgz'''|}</li>

<li>Then run the configuration command

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

|-

|

orangepi@orangepi:~$ '''cd Python-3.9.10'''

orangepi@orangepi:~$ '''./configure --enable-optimizations'''|}</li>

<li>Then compile and install python3.9, the compilation time takes about half an hour

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

|-

|

orangepi@orangepi:~$ '''make -j4'''

orangepi@orangepi:~$ '''sudo make altinstall'''|}</li>

<li>After installation, you can use the following command to view the Python version number just installed

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

|-

|

orangepi@orangepi:~$ '''python3.9 --version'''

'''Python 3.9.10'''|}</li>

<li>Then update pip

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''/usr/local/bin/python3.9 -m pip install --upgrade pip'''|}</li></ol>

=== Python to replace the pip source method ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The Linux system PIP's default source is the official source of Python, but the source of the official Python official visits is very slow, and the Python software packaging failure is often caused by network reasons. So when installing the Python library with PIP, remember to replace the pip source'''</big>|}

<li>First install '''python3-pip'''

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

|-

|

orangepi@orangepi:~$ '''sudo apt-get update'''

orangepi@orangepi:~$ '''sudo apt-get install -y python3-pip'''|}</li>

<li>Method of permanent replacement of pip source under Linux

<li>Create a new'''~/.pip''' directory first, then add the ~~>~~ '''pip.conf''' configuration file, and set the source of the pip ~~>~~ as Tsinghua source{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''mkdir -p ~/.pip'''

orangepi@orangepi:~$ '''cat <<EOF > ~/.pip/pip.conf'''

'''index-url = https://pypi.tuna.tsinghua.edu.cn/simple'''

'''trusted-host = pypi.tuna.tsinghua.edu.cn'''

'''EOF'''|}</li>

<li>Then install the Python library with pip3, it will be fast</li></ol>

</li>

<li>The method of temporarily replacing the pip source under Linux, the '''<packagename>''' needs to be replaced with a specific package name

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

|-

|

orangepi@orangepi:~$ '''pip3 install <packagename> -i \'''

'''https://pypi.tuna.tsinghua.edu.cn/simple --trusted-host pypi.tuna.tsinghua.edu.cn'''|}</li></ol>

== The Method Of Installing The Docker ==

Orange Pi's Linux image has been pre-installed with Docker, but the Docker service has not been opened by default. Use E'''enable_docker.sh''' script to enable the docker service, and then you can start using the docker command, and the docker service will be automatically activated at the next start of the system.

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

|-

|

orangepi@orangepi:~$ '''enable_docker.sh'''

|}

You can use the following command to test the docker,If you can run '''hello-world''' to indicate that docker can be used normally.。.

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

|-

|

orangepi@orangepi:~$ '''docker run hello-world'''

Status: Downloaded newer image for hello-world:latest

~~'''Hello from Docker!'''~~

'''Hello from Docker!''' '''This message shows that your installation appears to be working correctly.'''

'''.….'''

|}

When using the docker command, if it prompts '''permission denied''', please add the current user to the docker user group, so that the docker command can be run without ~~sudo。~~sudo.

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

|-

|

orangepi@orangepi:~$ '''sudo usermod -aG docker $USER'''

|}

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note: You need to log out of the system and log in again to take effect, and restarting the system is also OK.'''</big>|}

== How to install Home Assistant ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that only the method of installing Home Assistant in Ubuntu or Debian system will be provided here. For detailed usage of Home Assistant, please refer to official documents or corresponding ~~books。~~books.'''</big>|}

<li>First of all, please install docker and make sure that docker can run normally. ~~'''For the installation steps of docker'''~~The Method Of Installing The Docker, please refer to the instructions in the section on [[Orange Pi Zero 3#The Method Of Installing The Docker|'''how to install ~~Docker。~~Docker''']].</li>

<li>Then you can search for the docker image of Home Assistant

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''docker search homeassistant'''|}</li><li>Then use the following command to download the docker image of Home Assistant to the local. The size of the image is about 1GB, and the download time will be relatively long. Please wait patiently for the download to complete{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''docker pull homeassistant/home-assistant'''

Using default tag: latest

Digest: sha256:81d381f5008c082a37da97d8b08dd8b358dae7ecf49e62ce3ef1eeaefc4381bb

Status: Downloaded newer image for homeassistant/home-assistant:latest

docker.io/homeassistant/home-assistant:latest|}</li>

<li>Then you can use the following command to view the docker image of Home Assistant just downloaded

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

|-

|

orangepi@orangepi:~$ '''docker images homeassistant/home-assistant'''

REPOSITORY                                    TAG       IMAGE       ID       CREATED       SIZEhomeassistant/home-assistant       latest       bfa0ab9e1cf5       2 months ago       '''1.17GB'''|}</li>

<li>Now you can run the docker container of Home Assistant

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

|-

|

orangepi@orangepi:~$ '''docker run -d \'''

:'''--name homeassistant \''':'''--privileged \''':'''--restart=unless-stopped \''':'''-e TZ=Asia/Shanghai \''':'''-v /home/orangepi/home-assistant:/config \''':'''--network=host \''':'''homeassistant/home-assistant:latest'''|}</li>

<li>Then enter【IP address of the development board: 8123】in the browser to see the Home Assistant interface

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''It takes a while for the Home Assistant container to start. If the following interface is not displayed normally, please wait for a few seconds and then refresh. If the following interface is not displayed normally after waiting for more than one minute, it means that there is a problem with the installation of Home Assistant. At this time, you need to check whether there is a problem with the previous installation and setting ~~process。~~process.'''</big>|}[[File:~~media/image188~~zero3-img188-1.png~~|576x209px~~]]</li>

<li>Then enter '''your name''', '''user name''' and '''password''' and click '''Create Account'''

[[File:~~media/image189~~zero3-img189-1.png~~|220x279px~~]]</li>

<li>Then follow the interface prompts to set according to your preferences, and then click Next

[[File:~~media/image190~~zero3-img190-1.png~~|575x297px~~]]</li>

<li>Then click Next

[[File:~~media/image191~~zero3-img191-1.png~~|576x185px~~]]</li>

<li>Then click Finish

[[File:~~media/image192~~zero3-img192-1.png~~|576x117px~~]]</li>

<li>The final main interface displayed by Home Assistant is shown in the figure below

[[File:~~media/image193~~zero3-img193-1.png~~|574x294px~~]]</li>

<li>How to stop the Home Assistant container

<li>The command to view the docker container is as follows

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''docker ps -a'''|}</li>

<li>The command to stop the Home Assistant container is as follows

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''docker stop homeassistant'''|}</li>

<li>The command to delete the Home Assistant container is as follows

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''docker rm homeassistant'''|}</li></ol>

</li></ol>

=== Install via python ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Before installation, please replace the source of pip with a domestic source to speed up the installation of the Python package. For the configuration method, see the instructions in the section on [[Orange Pi Zero 3#Python to replace the pip source method|'''how to replace the pip source with Python''']].。'''</big>|}

<li>First install the dependency package

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

|-

|

orangepi@orangepi:~$ '''sudo apt-get update'''

orangepi@orangepi:~$ '''sudo apt-get install -y python3 python3-dev python3-venv \'''

'''python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential \'''

'''libopenjp2-7 libtiff5 libturbojpeg0-dev tzdata'''

|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If it is debian12, please use the following ~~command：~~command:'''</big>

orangepi@orangepi:~$ '''sudo apt-get update'''

orangepi@orangepi:~$ '''sudo apt-get install -y python3 python3-dev python3-venv \'''

'''python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential \'''

'''libopenjp2-7 libturbojpeg0-dev tzdata'''|}</li><li>Then you need to compile and install Python3.9. For the method, please refer to the section on [[Orange Pi Zero 3#Python source code compilation and installation method|'''how to compile and install Python source code''']]{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The default Python version of Debian Bullseye is Python3.9, so there is no need to compile and ~~install。~~install.''''''The default Python version of Ubuntu Jammy is Python3.10, so there is no need to compile and ~~install。~~install.''''''The default Python version of Debian Bookworm is Python3.11, so there is no need to compile and ~~install。~~install.'''</big>|}</li>

<li>Then create a Python virtual environment

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Debian Bookworm is python3.11, please remember to replace the corresponding ~~command。~~command.'''</big>|}{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''sudo mkdir /srv/homeassistant'''

orangepi@orangepi:~$ '''sudo chown orangepi:orangepi /srv/homeassistant'''

orangepi@orangepi:~$ '''python3.9 -m venv .'''

orangepi@orangepi:~$ '''source bin/activate'''

(homeassistant) orangepi@orangepi:/srv/homeassistant$|}</li>

<li>Then install the required Python package

{| class="wikitable" style="width:800px;" |-| (homeassistant) orangepi@orangepi:/srv/homeassistant$ '''python3 -m pip install wheel'''|}</li>

<li>Then you can install Home Assistant Core

{| class="wikitable" style="width:800px;" |-| (homeassistant) orangepi@orangepi:/srv/homeassistant$ '''pip3 install homeassistant'''|}</li>

<li>Then enter the following command to run Home Assistant Core

{| class="wikitable" style="width:800px;" |-| (homeassistant) orangepi@orangepi:/srv/homeassistant$ '''hass'''|}</li>

<li>Then enter '''[IP address of the development board: 8123]''' in the browser to see the interface of Home Assistant

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''When running the hass command for the first time, you will download and install and cache some necessary libraries and dependencies to run. This process may take a few minutes. Note that at this time, the interface of Home Assistant cannot be seen in the browser. Please wait for a while before ~~refreshing。~~refreshing.'''</big>|}[[File:~~media/image194~~zero3-img194-1.png~~|576x203px~~]]</li></ol>

== OpenCV installation method ==

<li>The installation command is shown below

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

|-

|

orangepi@orangepi:~$ '''sudo apt-get update'''

orangepi@orangepi:~$ '''sudo apt-get install -y libopencv-dev python3-opencv'''|}</li>

<li>Then use the following command to print the output of the version number of OpenCV, indicating that the installation of OpenCV is successful

<li>The version of OpenCV in ubuntu22.04 is shown ~~below：~~below:{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''python3 -c "import cv2; print(cv2.__version__)"'''

'''4.5.4'''|}</li><li>The version of OpenCV in Ubuntu 20.04 is shown ~~below：~~below:{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''python3 -c "import cv2; print(cv2.__version__)"'''

'''4.2.0'''|}</li><li>The version of OpenCV in Debian11 is shown ~~below：~~below:{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''python3 -c "import cv2; print(cv2.__version__)"'''

'''4.5.1'''|}</li><li>The version of OpenCV in Debian12 is shown ~~below：~~below:{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''python3 -c "import cv2; print(cv2.__version__)"'''

'''4.6.0'''|}</li></ol>

</li></ol>

== The installation method of the aapanel Linux panel ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''aapanel 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 (~~extracted~~ excerpted from ~~the~~ [https://www.bt.cn/new/index.html Baota official website ~~of the aapanel~~])'''</big>|}

<li>First of all, you need to expand the'''/tmp''' memory. After setting, you need to '''restart the linux system of the development board，'''and the command is shown below：:{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''sudo sed -i 's/nosuid/&,size=2G/' /etc/fstab'''

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

<li>After restarting, you can see that the size of the'''/tmp''' space has become 2G

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

|-

|

orangepi@orangepi:~$ '''df -h | grep "/tmp"'''

tmpfs     2.0G     12K     '''2.0G'''     1% /tmp|}</li>

<li>Then enter the following command in the Linux system to start the installation of the aapanel

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo install_bt_panel.sh'''|}</li><li>Then the aapanel installation program reminds whether to install the '''Bt-Panel''' to the'''/www''' folder, and enter Y at this time{| class="wikitable" style="width:800px;" |-|

+----------------------------------------------------------------------

| Bt-WebPanel FOR CentOS/Ubuntu/Debian

| The WebPanel URL will be http://SERVER_IP:8888 when installed.

+----------------------------------------------------------------------

Do you want to install Bt-Panel to the /www directory now?(y/n): '''y'''|}</li>

<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

[[File:~~media/image195~~zero3-img195.png~~|576x233px~~]]</li>

<li>At this time, enter the '''panel address''' displayed above in the browser to open the login interface of the aapanel Linux panel, and then enter the '''username''' and '''password''' displayed in the corresponding position to log in to the aapanel

[[File:~~media/image196~~zero3-img196.png|~~575x281px~~1200px]]</li>

<li>After successfully logging in to the aapanel, 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 aapanel

[[File:~~media/image197~~zero3-img197.png|~~575x317px~~1200px]]</li><li>After entering the aapanel, you will first prompt that you need to bind the account of the aapanel official website. If you do n’t have an account, you can go to the aapanel ’s 's official website ('''https://www.bt.cn''') to register one[[File:~~media/image198~~zero3-img198.png|~~576x300px~~1200px]]</li>

<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

[[File:~~media/image199~~zero3-img199.png|~~575x306px~~1200px]]</li>

<li>For more functions of the aapanel, please refer to the following information to explore by yourself

{| class="wikitable" style="width:800px;" |-| Use ~~manual：~~manual: [http://docs.bt.cn '''http://docs.bt.cn''']Forum ~~website：~~website: [https://www.bt.cn/bbs '''https://www.bt.cn/bbs''']GitHub ~~Link：~~Link: '''https://github.com/aaPanel/BaoTa'''|}</li></ol>

~~== face_recognition The installation and testing method of the face recognition library ==~~

== "face_recognition" The installation and testing method of the face recognition library == {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the contents of this section are tested in the Linux system of the desktop version, so please make sure that the system used by the development board is a desktop version ~~system。~~system.'''

'''In addition, the installation test below is performed under OrangePi users. Please keep the environment consistent.'''

~~'''Debian12 is currently not adapted.'''~~

'''Debian12 is currently not adapted.'''</big>|} {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The address of the source code warehouse of Face_recognition ~~is：~~is:'''

[https://github.com/ageitgey/face_recognition '''https://github.com/ageitgey/face_recognition''']

'''Face_recognition Chinese version of the explanation document ~~is：~~is:'''

'''https://github.com/ageitgey/face_recognition/blob/master/README_Simplified_Chinese.md'''</big>|}

<li>First open a terminal on the desktop''', then download face_recognition_install.sh'''

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

|-

|

orangepi@orangepi:~/Desktop$ '''wget \'''

'''https://gitee.com/leeboby/face_recognition_install/raw/master/face_recognition_install.sh'''|}</li>

<li>Then execute the following command to start the installation '''face_recognition'''

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~/Desktop$ '''bash face_recognition_install.sh'''|}</li><li>After face_recognition is installed, it will automatically download the source code of face_recognition, and then automatically run some examples in face_recognition. If you can finally see the following pictures popping up on the desktop, it means that the face_recognition installation test is successful.[[File:~~media/image200~~zero3-img200.png~~|576x324px~~]]</li></ol>

=== Manually install face_recognition ===

<li>First create a new '''~/.pip''' directory, then add the '''pip.conf''' configuration file, and set the mirror source of pip to Tsinghua source in it, the commands to be executed are as ~~follows：~~follows:{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''mkdir -p ~/.pip'''

orangepi@orangepi:~$ '''cat <<EOF > ~/.pip/pip.conf'''

'''index-url = https://pypi.tuna.tsinghua.edu.cn/simple'''

'''trusted-host = pypi.tuna.tsinghua.edu.cn'''

'''EOF'''|}</li>

<li>Then install dependencies

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

|-

|

orangepi@orangepi:~$ '''sudo apt update'''

orangepi@orangepi:~$ '''sudo apt install -y python3-pip libopencv-dev \'''

'''python3-opencv imagemagick python3-scipy python3-setuptools python3-wheel \'''

'''python3-dev cmake python3-testresources'''|}</li>

<li>Then update pip3

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3 -m pip install -U pip setuptools wheel'''|}</li><li>Before installing '''face_recognition''', you first need to install the '''dlib''' library. Since the compilation and installation of the dlib library on the development board is relatively slow, I saved a compiled dlib whl file on '''gitee''', and you can install it directly after downloading. The download address of the dlib whl file is as ~~follows：~~follows:{| class="wikitable" style="width:800px;" |-|

'''https://gitee.com/leeboby/python_whl'''

|}

<li>First download the python_whl warehouse to the Linux system of ~~>~~ the development board{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''git clone --depth=1 https://gitee.com/leeboby/python_whl'''|}</li><li>In the python_whl folder, you can see that there are multiple ~~>~~ versions of dlib installation packages. The Linux systems ~~>~~ corresponding to different versions of dlib are as ~~follows：~~follows:</p~~></li></ol></li></ol~~>

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

|-

| style="text-align: ~~left~~center;"| '''Ubuntu20.04'''| style="text-align: ~~left~~center;"| '''dlib-19.24.0-cp38-cp38-linux_aarch64.whl'''

|-

| style="text-align: ~~left~~center;"| '''Ubuntu22.04'''| style="text-align: ~~left~~center;"| '''dlib-19.24.0-cp310-cp310-linux_aarch64.whl'''

|-

| style="text-align: ~~left~~center;"| '''Debian11'''| style="text-align: ~~left~~center;"| '''dlib-19.24.0-cp39-cp39-linux_aarch64.whl'''

|}

</li></ol>

<li>Then you can start installing dlib, the command is as follows

<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) Ubuntu20.04{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''cd python_whl'''

orangepi@orangepi:~/python_whl$ '''python3 -m pip install dlib-19.24.0-cp38-cp38-linux_aarch64.whl'''|}</li><li>b) Ubuntu22.04{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''cd python_whl'''

orangepi@orangepi:~/python_whl$ '''python3 -m pip install dlib-19.24.0-cp310-cp310-linux_aarch64.whl'''|}</li><li>c) Debian11{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''cd python_whl'''

orangepi@orangepi:~/python_whl$ '''python3 -m pip install dlib-19.24.0-cp39-cp39-linux_aarch64.whl'''|}</li></ol>

</li>

<li>After installation, if the version number of dlib can be printed ~~>~~ normally by using the following command, it means that dlib is ~~>~~ installed correctly{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~/python_whl$ '''python3 -c "import dlib; print(dlib.__version__)"'''

'''19.24.0'''|}</li></ol></li></ol>

<li>Then install '''face_recognition_models-0.3.0-py2.py3-none-any.whl'''

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~/python_whl$ '''python3 -m pip install face_recognition_models-0.3.0-py2.py3-none-any.whl'''|}</li>

<li>Then install '''face_recognition'''

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3 -m pip install face_recognition'''|}</li><li>Then you need to '''reopen a terminal''' to find and run the two commands '''face_detection''' and '''face_recognition'''<ol style="list-style-type: ~~lower-alpha~~none;"><li>a. The face_recognition command is used to recognize whose face is ~~>~~ in a single image or a folder of images.</li><li>b. The face_detection command is used to locate the face in a ~~>~~ single picture or a picture folder{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''which face_detection'''

/usr/local/bin/face_detection

orangepi@orangepi:~$ '''which face_recognition'''

/usr/local/bin/face_recognition</p~~></li></ol~~>~~</li></ol>~~|}

<li>If you can't find the above two commands after reopening the terminal, please try to manually import environment variables, and then test again

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

|-

|

orangepi@orangepi:~$ '''export PATH=/home/orangepi/.local/bin:$PATH'''

|}

</li>

</li></ol>

~~~~

=== The test method of face_recognition ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the following operations are demonstrated on the desktop, so please connect the HDMI monitor first, or use NoMachine/VNC to remotely log in to the Linux desktop to ~~test。~~test.'''</big>|}

<li>There are some sample codes in the source code of '''face_recognition''', which we can use directly for testing. The download address of the source code of face_recognition is as ~~follows：~~follows:

<li>GitHub official download address

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''git clone https://github.com/ageitgey/face_recognition.git'''|}</li>

<li>Gitee image download address

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''git clone [https://github.com/ageitgey/face_recognition https://gitee.com/leeboby/face_recognition.git]'''|}</li></ol>

</li>

<li>The path to the face_recognition sample code is as follows

{| class="wikitable" style="width:800px;" |-| '''face_recognition/examples'''|}</li>

<li>The Chinese description document link of face_recognition is as follows, please read it carefully before using face_recognition

{| class="wikitable" style="width:800px;" |-| [https://github.com/ageitgey/face_recognition/blob/master/README_Simplified_Chinese.md '''https://github.com/ageitgey/face_recognition/blob/master/README_Simplified_Chinese.md''']|}</li>

<li>'''find_faces_in_picture.py''' is used to locate the position of the face in the picture, the test steps are as follows

<li>Open a terminal on the desktop, then enter the ~~>~~ '''face_recognition/examples''' directory, and then execute the ~~>~~ following command{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''cd face_recognition/examples'''

orangepi@orangepi:~/face_recognition/examples$ '''python3 find_faces_in_picture.py'''

'''I found 1 face(s) in this photograph.'''

'''A face is located at pixel location Top: 241, Left: 419, Bottom: 562, Right: 740'''|}</li><li>Wait for a while and the following picture will pop up, which is ~~>~~ the face located in the test picture[[File:~~media/image201~~zero3-img201.png~~|575x311px~~]]</li></ol>

</li>

<li>'''find_facial_features_in_picture.py''' is used to identify the key points of the face in a single picture, and the test steps are as follows

<li>Open a terminal on the desktop, then enter the ~~>~~ '''face_recognition/examples''' directory, and then execute the ~~>~~ following command{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''cd face_recognition/examples'''

orangepi@orangepi:~/face_recognition/examples$ '''python3 find_facial_features_in_picture.py'''|}</li><li>After waiting for a while, the following picture will pop up, ~~>~~ and you can see that the outline of the face is marked[[File:~~media/image202~~zero3-img202.png~~|575x302px~~]]</li></ol>

</li>

<li>'''identify_and_draw_boxes_on_faces.py''' is used to identify faces and mark them with boxes. The test steps are as follows

<li>Open a terminal on the desktop, then enter the ~~>~~ '''face_recognition/examples''' directory, and then execute the ~~>~~ following command{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''cd face_recognition/examples'''

orangepi@orangepi:~/face_recognition/examples$ '''python3 identify_and_draw_boxes_on_faces.py'''|}</li><li>After waiting for a while, the following picture will pop up. ~~>~~ You can see that the faces in the picture are marked with ~~>~~ boxes, and the names of the characters are displayed correctly[[File:~~media/image203~~zero3-img203.png~~|461x250px~~]]</li></ol>

</li>

<li>'''face_distance.py''' is used to compare whether two faces belong to the same person at different precisions. First open a terminal, then enter the '''face_recognition/examples''' directory, and then execute the following command to see the output of the test

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

|-

|

orangepi@orangepi:~$ '''cd face_recognition/examples'''

orangepi@orangepi:~/face_recognition/examples$ '''python3 face_distance.py'''

'''- With a normal cutoff of 0.6, would the test image match the known image? True'''

'''- With a very strict cutoff of 0.5, would the test image match the known image? True'''

'''The test image has a distance of 0.82 from known image #1'''

'''- With a normal cutoff of 0.6, would the test image match the known image? False'''

'''- With a very strict cutoff of 0.5, would the test image match the known image? False'''|}</li>

<li>'''recognize_faces_in_pictures.py''' is used to identify who the face in the unknown picture is. First open a terminal, then enter the '''face_recognition/examples''' directory, and then execute the following command, and you can see the test results after waiting for a while

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

|-

|

orangepi@orangepi:~$ '''cd face_recognition/examples'''

orangepi@orangepi:~/face_recognition/examples$ '''python3 recognize_faces_in_pictures.py'''

'''Is the unknown face a picture of Biden? False'''

'''Is the unknown face a picture of Obama? True'''

'''Is the unknown face a new person that we've never seen before? False'''|}</li><li>'''facerec_from_webcam_faster.py''' is used to recognize the face in the USB camera, the test steps are as ~~follows：~~follows:

<li>First, please insert the USB camera into the USB interface of ~~>~~ the development board, and then use the '''v4l2-ctl''' ('''note ~~>~~ that l in v4l2 is a lowercase letter l, not the number 1''') ~~>~~ command to check the serial number of the device node of the ~~>~~ USB camera{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''sudo apt update'''

orangepi@orangepi:~$ '''sudo apt install -y v4l-utils'''

orangepi@orangepi:~$ '''v4l2-ctl --list-devices'''

cedrus (platform:cedrus):

::/dev/video0

USB2.0 UVC PC Camera: USB2.0 UV (usb-5311000.usb-1):

::'''/dev/video1'''::/dev/video2|}</li><li>Then open a terminal on the desktop, enter the ~~>~~ '''face_recognition/examples''' directory, and first modify the ~~>~~ device serial number of the camera used in ~~>~~ '''facerec_from_webcam_faster.py.''' For example, through the ~~>~~ '''v4l2-ctl --list-devices''' command above, you can see that ~~>~~ the USB camera is '''/dev/video1''', then modify the '''0''' in ~~>~~ '''cv2.VideoCapture(0)''' to '''1'''{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''cd face_recognition/examples'''

orangepi@orangepi:~/face_recognition/examples$ '''vim facerec_from_webcam_faster.py'''

'''video_capture = cv2.VideoCapture(1)'''|}</li><li>Then execute the following command to run ~~>~~ '''facerec_from_webcam_faster.py'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~/face_recognition/examples$ '''python3 facerec_from_webcam_faster.py'''|}</li>

<li>Wait for a while and the camera display screen will pop up

[[File:~~media/image204~~zero3-img204.png~~|314x245px~~]]</li><li>At this point, you can point the camera at yourself. When the ~~>~~ camera detects a face, it will frame the detected face with a ~~>~~ square. '''Note that when detecting a face, the image displayed ~~>~~ by the camera will be relatively slow, please do not move too ~~>~~ fast'''</li><li>You can also open a picture of Obama, and then use the camera to ~~>~~ point at the opened picture. You can see that not only the ~~>~~ face can be marked, but also the name of the detected face can ~~>~~ be displayed correctly. '''Note that when detecting a face, the ~~>~~ image displayed by the camera will be relatively slow, please ~~>~~ do not move too fast'''[[File:~~media/image205~~zero3-img205.png~~|358x284px~~]]</li></ol>

</li>

<li>'''web_service_example.py''' is a very simple case of using a web service to upload a picture to run face recognition. The backend server will identify whether the picture is Obama, and output the recognition result as a json key-value pair. The test steps are as ~~follows：~~follows:

<li>Open a terminal on the desktop, then enter the ~~>~~ '''face_recognition/examples''' directory, and then execute the ~~>~~ following command ('''if face_recognition is automatically ~~>~~ installed using a script, then there is no need to install ~~>~~ flask'''){| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''python3 -m pip install flask'''

orangepi@orangepi:~$ '''cd face_recognition/examples'''

* Serving Flask app 'web_service_example' (lazy loading)

* Environment: production

:WARNING: This is a development server. Do not use it in a production deployment.:Use a production WSGI server instead.

* Debug mode: on

* Running on all addresses (0.0.0.0)

:WARNING: This is a development server. Do not use it in a production deployment.

* Running on http://127.0.0.1:5001

* Running on http://192.168.1.79:5001 (Press CTRL+C to quit)

* Restarting with stat

* Debugger is active!

* Debugger PIN: 500-161-390|}</li><li>Then open another terminal and run the following command to ~~>~~ return the result of image recognition (note that the ~~>~~ execution path of the following command is ~~>~~ '''face_recognition/examples'''){| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~/face_recognition/examples$ '''curl -XPOST -F \'''

'''"file=@obama2.jpg" http://127.0.0.1:5001'''

'''{'''

:'''"face_found_in_image": true,''':'''"is_picture_of_obama": true''''''}'''|}</li><li>We can also copy the picture ~~>~~ '''face_recognition/examples/obama2.jpg''' to other Linux ~~>~~ computers. Of course, we can also prepare a picture named ~~>~~ '''obama2.jpg''' by ourselves, and then use the following ~~>~~ command on the Linux computer to remotely Use the service ~~>~~ running on the development board to recognize faces ('''note ~~>~~ that the IP address in the command needs to be replaced with ~~>~~ the IP address of the development board, and the file name ~~>~~ after file needs to be replaced with the name of the picture ~~>~~ you want to test''').{| class="wikitable" style="width:800px;" |-|

test@test:~$ '''curl -XPOST -F "file=@obama2.jpg" http://192.168.1.79:5001'''

'''{'''

:'''"face_found_in_image": true,''':'''"is_picture_of_obama": true''''''}'''|}</li><li>The method to test using the browser is as ~~follows：~~follows:<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) First open the browser, then enter the '''IP address of the ~~>~~ development board: 5001''' in the address bar of ~~>~~ the browser, and then you can see the following page[[File:~~media/image206~~zero3-img206.png~~|575x150px~~]]</li><li>b) Then copy obama2.jpg to the desktop{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~/face_recognition/examples$ '''cp obama2.jpg /home/orangepi/Desktop/'''|}</li><li>c) Then select the picture you just copied in your browser[[File:~~media/image207~~zero3-img207.png~~|575x217px~~]]</li><li>d) Then click '''Upload''' to upload the picture you just ~~>~~ selected for face recognition[[File:~~media/image208~~zero3-img208.png~~|575x145px~~]]</li><li>e) After waiting for a while, the detection result will be ~~>~~ displayed[[File:~~media/image209~~zero3-img209.png~~|314x149px~~]]</li></ol></li></ol>

</li>

<li>'''face_detection''' command test example

<li>The face_detection command-line tool can locate the face ~~>~~ position (output pixel coordinates) in a single picture or a ~~>~~ picture folder. Use '''face_detection --help''' to view the ~~>~~ help information of the face_detection command{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''face_detection --help'''

Usage: face_detection [OPTIONS] IMAGE_TO_CHECK

Options:

:--cpus INTEGER number of CPU cores to use in parallel. -1 means "use all in~~~~system" :--model TEXT Which face detection model to use. Options are "hog" or~~~~"cnn". :--help Show this message and exit.|}</li><li>An example of detecting a single image is shown ~~below：~~below:{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''cd face_recognition/examples'''

orangepi@orangepi:~/face_recognition/examples$ '''face_detection obama2.jpg'''

obama2.jpg,302,474,611,164|}</li><li>An example of using multiple cores to detect multiple images in ~~>~~ parallel is shown ~~below：~~below:<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) First enter the '''face_recognition/examples''' folder</li><li>b) Then create a new test folder</li><li>c) Then copy the jpg images to the test folder</li><li>d) Then use all cpus to run '''face_detection''' in parallel to ~~>~~ check the pictures in the test folder, where '''--cpus ~~>~~ -1''' means to use all cpus{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''cd face_recognition/examples'''

orangepi@orangepi:~/face_recognition/examples$ '''mkdir test'''

test/obama-720p.jpg,94,751,273,572

test/obama-1080p.jpg,136,1140,394,882

test/biden.jpg,233,749,542,439|}</li></ol>

</li></ol>

</li>

<li>'''face_recognition''' command test example

<li>'''face_recognition''' command-line tool can recognize whose face ~~>~~ is in a single picture or a picture folder. Use ~~>~~ '''face_recognition --help''' to view the help information of ~~>~~ the face_recognition command{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''face_recognition --help'''

Usage: face_recognition [OPTIONS] KNOWN_PEOPLE_FOLDER IMAGE_TO_CHECK

Options:

:--cpus INTEGER            number of CPU cores to use in parallel (can speed~~~~up processing lots of images). -1 means "use all in~~~~system" :--tolerance FLOAT          Tolerance for face comparisons. Default is 0.6.~~~~Lower this if you get multiple matches for the same~~~~person. :--show-distance BOOLEAN    Output face distance. Useful for tweaking tolerance~~~~setting. :--help                  Show this message and exit.|}</li><li>First create a new face picture folder '''known_people''' with a ~~>~~ known name, then copy two pictures to '''known_people''', and ~~>~~ then copy '''obama2.jpg''' to '''unknown.jpg''', which is the ~~>~~ picture we want to identify{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''cd face_recognition/examples'''

orangepi@orangepi:~/face_recognition/examples$ '''mkdir known_people'''

orangepi@orangepi:~/face_recognition/examples$ '''cp biden.jpg obama.jpg known_people'''

orangepi@orangepi:~/face_recognition/examples$ '''cp obama2.jpg unkown.jpg'''|}</li><li>Then you can use the following command to identify the name of ~~>~~ the person in the '''unknown.jpg''' picture, and you can see ~~>~~ that the unknown.jpg picture is recognized as obama{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~/face_recognition/examples$ '''face_recognition known_people \'''

'''unkown.jpg'''

unkown.jpg,obama|}</li><li>If we identify an irrelevant image, unknown_person will be ~~>~~ displayed{| class="wikitable" style="width:800px;" |-|

root@orangepi:~/face_recognition/examples$ '''face_recognition known_people \'''

'''alex-lacamoire.png'''

alex-lacamoire.png,unknown_person|}</li><li>We can also create a new test folder and put multiple pictures ~~>~~ in it, and then we can use all the CPUs to recognize all the ~~>~~ pictures in parallel{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~/face_recognition/examples$ '''mkdir test'''

orangepi@orangepi:~/face_recognition/examples$ '''cp *.jpg *.png test'''

orangepi@orangepi:~/face_recognition/examples$ '''face_recognition --cpus -1 \'''

test/obama-480p.jpg,obama

test/biden.jpg,biden

test/obama-1080p.jpg,obama|}</li></ol>

</li></ol>

== Setting Chinese environment and installing Chinese input method ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note, please make sure that the Linux system used by the development board is a desktop system before installing the Chinese input ~~method。~~method.'''</big>|}

<li>Enter the following command to start configuring the '''locale'''

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''|}</li><li>Then select '''zh_CN.UTF-8 UTF-8''' in the pop-up interface (move ~~>~~ up and down through the up and down direction keys on the ~~>~~ keyboard, select through the space bar, and finally move the ~~>~~ cursor to '''<OK>'''through the Tab key, and then press ~~>~~ Enter.)[[File:~~media/image210~~zero3-img210.png|~~575x296px~~1200px]]</li>

<li>Then set the default '''locale''' to '''zh_CN.UTF-8'''

[[File:~~media/image211~~zero3-img211.png|~~575x160px~~1200px]]</li><li>After exiting the interface, the '''locale''' setting will start, ~~>~~ and the output displayed on the command line is as follows{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''

Generating locales (this might take a while)...

:en_US.UTF-8... done:zh_CN.UTF-8... doneGeneration complete.|}</li></ol>

</li>

<li>Then open the '''Input Method'''

[[File:~~media/image212~~zero3-img212.png~~|575x361px~~]]</li>

<li>Then choose '''OK'''

[[File:~~media/image213~~zero3-img213.png~~|295x212px~~]]</li><li>Then choose'''Yes'''[[File:~~media/image214~~zero3-img214.png~~|303x192px~~]]</li><li>Then choose'''fcitx'''[[File:~~media/image215~~zero3-img215.png~~|307x220px~~]]</li><li>Then choose'''OK'''[[File:~~media/image216~~zero3-img216.png~~|305x216px~~]]</li><li>'''Then restart the Linux system to make the configuration take effect'''</li>

<li>Then open '''Fcitx configuration'''

[[File:~~media/image217~~zero3-img217.png~~|575x376px~~]]</li>

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

[[File:~~media/image218~~zero3-img218.png~~|280x187px~~]]</li>

<li>Then search '''Google Pinyin''' and click '''OK'''

[[File:~~media/image219~~zero3-img219-1.png~~|291x196px~~]]</li>

<li>Then bring '''Google Pinyin''' to the front

[[File:~~media/image220~~zero3-img220.png~~|299x202px~~]][[File:~~media/image221~~zero3-img221.png~~|300x202px~~]]</li>

<li>Then open the '''Geany''' editor to test the Chinese input method

[[File:~~media/image222~~zero3-img222.png~~|349x212px~~]]</li>

<li>The Chinese input method test is as follows

[[File:~~media/image223~~zero3-img223.png~~|575x325px~~]]</li>

<li>The Chinese and English input methods can be switched through the '''Ctrl+Space''' shortcut key</li>

<li>If the entire system needs to be displayed in Chinese, you can set the variables in '''/etc/default/locale''' to '''zh_CN.UTF-8'''

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

|-

|

orangepi@orangepi:~$ '''sudo vim /etc/default/locale'''

# File generated by update-locale

LC_MESSAGES='''zh_CN.UTF-8'''LANG='''zh_CN.UTF-8'''LANGUAGE='''zh_CN.UTF-8'''|}</li><li>Then '''restart the system''' and you can see that the system is displayed in Chinese[[File:~~media/image224~~zero3-img224.png~~|576x356px~~]]</li></ol>

=== How to install Ubuntu 20.04 system ===

<li>First open '''Language Support'''

[[File:~~media/image225~~zero3-img225.png~~|575x351px~~]]</li>

<li>Then find the '''Chinese (China''') option

[[File:~~media/image226~~zero3-img226.png~~|318x311px~~]]</li><li>Then please use the left mouse button to select '''Chinese (China)''' and hold it down, then drag it up to the initial position, the display after dragging is as shown in the figure ~~below：~~below:[[File:~~media/image227~~zero3-img227.png~~|324x320px~~]]~~</li></ol>~~ ~~'''Note that this step is not easy to drag, please be patient and try a few more times.'''~~

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

|-

|

<big>'''Note that this step is not easy to drag, please be patient and try a few more times.'''</big>

|}

</li></ol>

<li>Then select '''Apply System-Wide''' to apply the Chinese settings to the entire system

[[File:~~media/image228~~zero3-img228.png~~|321x316px~~]]</li>

<li>Then set'''Keyboard input method system''' to '''fcitx'''

[[File:~~media/image229~~zero3-img229.png~~|327x320px~~]]</li><li>'''Then restart the Linux system to make the configuration take effect'''</li>

<li>After re-entering the system, '''please choose not to ask me again''' in the following interface, and then please decide whether the standard folder should also be updated to Chinese according to your preferences

[[File:~~media/image230~~zero3-img230.png~~|303x247px~~]]</li>

<li>Then you can see that the desktop is displayed in Chinese

[[File:~~media/image231~~zero3-img231.png~~|575x383px~~]]</li>

<li>Then we can open '''Geany''' to test the Chinese input method, as shown in the figure below

[[File:~~media/image232~~zero3-img232.png~~|576x292px~~]]</li>

<li>After opening '''Geany''', the default is English input method, we can switch to Chinese input method through '''Ctrl+Space''' shortcut key, and then we can input Chinese

[[File:~~media/image233~~zero3-img233.png~~|575x308px~~]]</li></ol>

=== How to install Ubuntu 22.04 system ===

<li>First open '''Language Support'''

[[File:~~media/image225~~zero3-img225.png~~|575x351px~~]]</li>

<li>Then find the '''Chinese (China)''' option

[[File:~~media/image234~~zero3-img234.png~~|249x242px~~]]</li><li>Then please use the left mouse button to select '''Chinese (China)''' and hold it down, then drag it up to the initial position, the display after dragging is as shown in the figure ~~below：~~below:[[File:~~media/image235~~zero3-img235.png~~|267x262px~~]]~~</li></ol>~~ ~~'''Note that this step is not easy to drag, please be patient and try a few more times。'''~~

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

|-

|

<big>'''Note that this step is not easy to drag, please be patient and try a few more times.'''</big>

|}

</li></ol>

<li>Then select '''Apply System-Wide''' to apply the Chinese settings to the entire system

[[File:~~media/image236~~zero3-img236.png~~|287x282px~~]]</li><li>'''Then restart the Linux system to make the configuration take effect'''</li>

<li>After re-entering the system, please choose '''not to ask me again''' in the following interface, and then please decide whether the standard folder should also be updated to Chinese according to your preferences

[[File:~~media/image230~~zero3-img230.png~~|303x247px~~]]</li>

<li>Then you can see that the desktop is displayed in Chinese

[[File:~~media/image231~~zero3-img231.png~~|575x383px~~]]</li>

<li>Then open the Fcitx5 configuration program

[[File:~~media/image237~~zero3-img237.png~~|575x349px~~]]</li>

<li>Then choose to use Pinyin input method

[[File:~~media/image238.jpeg|338x267px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~zero3-11img238.~~jpg未标题-11~~png]]

</div></li>

<li>The interface after selection is as shown below, and then click OK

[[File:~~media/image239~~zero3-img239.png~~|366x290px~~]]</li>

<li>Then we can open '''Geany''' to test the Chinese input method, the opening method is shown in the figure below

[[File:~~media/image232~~zero3-img232.png~~|576x292px~~]]</li>

<li>After opening '''Geany''', the default is English input method, we can switch to Chinese input method through '''Ctrl+Space''' shortcut key, and then we can input Chinese

[[File:~~media/image240~~zero3-img240.png~~|434x308px~~]]</li></ol>

== How to Remotely Log In to the Desktop of Linux System ==

=== Remote login using NoMachine ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Make sure the Ubuntu or Debian system installed on the development board is a desktop system 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 link is shown ~~below：~~below:'''

'''https://knowledgebase.nomachine.com/DT10R00166'''</big>|}

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''NoMachine supports Windows, Mac, Linux, iOS and Android platforms, so we can remotely log in and control the Orange Pi development board through NoMachine on a variety of devices. The following demonstrates how to remotely log in to the Linux system desktop of the Orange Pi development board through NoMachine in Windows. For installation methods on other platforms, please refer to the official documentation of NoMachine'''</big>|} {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Before operation, please make sure that the Windows computer and the development board are in the same LAN, and can log in to the Ubuntu or Debian system of the development board through ssh'''</big>|}

<li>First download the installation package of the NoMachine software Linux '''arm64''' deb version, and then install it into the Linux system of the development board

<li>Since H618 is a SOC of the ARMV8 architecture, the system we use ~~>~~ is Ubuntu or Debian, so you need to download the '''NoMachine ~~>~~ for ARM ARMv8 DEB''' installation package. The download link is ~~>~~ shown ~~below：~~below:</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <~~/ol~~big><'''Note that this download link may change, please look for the deb package of the Armv8/~~li>~~Arm64 version.'''</olbig>|}

~~'''Note that this download link may change, please look for the deb package of the Armv8/Arm64 version。'''~~{| class="wikitable" style="width:800px;" |-| ~~[https://www.nomachine.com/download/download&id=112&s=ARM~~ '''https://downloads.nomachine.com/download/?id=118&distro=ARM'''] ~~[[File:media/image241.png~~|~~575x227px]]~~}

[[File:zero3-img241.png]]

</ol>

<li>In addition, the installation package of '''NoMachine''' can also be ~~>~~ downloaded in the '''official tool'''[[File:~~media/image242~~zero3-img242.png~~|66x102px~~]]

First enter the '''remote login software-NoMachine''' folder

[[File:~~media/image243~~zero3-img243.png~~|271x43px~~]]

Then download the arm64 version of the deb installation package

[[File:~~media/image244~~zero3-img244.png~~|180x109px~~]]</li><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{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg -i nomachine_x.x.x_x_arm64_arm64.deb'''|}</li></ol></li></ol>

<li>Then download the installation package of the Windows version of the NoMachine software, the download address is as follows</li~~></ol~~>

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that this download link may ~~change。~~change.'''</big>|}

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

|-

|

'''https://downloads.nomachine.com/download/?id=9'''

|}

[[File:~~media/image245~~zero3-img245.png~~|575x163px~~]]</ol>

<li>Then install NoMachine in Windows, '''please restart the computer after installation'''</li>

<li>Then open '''NoMachine''' in Window

[[File:~~media/image246~~zero3-img246.png~~|76x66px~~]]</li>

<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. Start log in to the linux system desktop of the development board

[[File:~~media/image247~~zero3-img247.png~~|321x92px~~]]</li>

<li>Then click '''OK'''

[[File:~~media/image248~~zero3-img248.png~~|318x217px~~]]</li>

<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

[[File:~~media/image249.jpeg|303x204px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~zero3-12img249.~~jpg未标题-12~~png]]

</div></li>

<li>Then click OK in the next interface</li>

<li>Finally, you can see the desktop of the development board Linux system

[[File:~~media/image250~~zero3-img250.png~~|411x246px~~]]</li></ol>

=== Log in remotely using VNC ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Before operation, please make sure that the Windows computer and the development board are in the same local area network, and can log in to the Ubuntu or Debian system of the development board normally with ssh.'''

'''Ubuntu20.04 has many problems testing VNC, please do not use this method'''</big>|}

<li>First run the '''set_vnc.sh''' script to set up vnc, remember to '''add sudo permission'''{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''sudo set_vnc.sh'''

You will require a password to access your desktops.

Password:        '''#Set the vnc password here, 8 -bit characters'''Verify:              '''#Set the vnc password here, 8 characters'''Would you like to enter a view-only password (y/n)? '''n'''

xauth: file /root/.Xauthority does not exist

New 'X' desktop is orangepi:1

Creating default startup script /root/.vnc/xstartup

Starting applications specified in /root/.vnc/xstartup

Log file is /root/.vnc/orangepi:1.log

Killing Xtightvnc process ID 3047

New 'X' desktop is orangepi:1

Starting applications specified in /root/.vnc/xstartup

Log file is /root/.vnc/orangepi:1.log|}</li><li>The steps to use the MobaXterm software to connect to the desktop of the Linux system of the development board are as ~~follows：~~follows:

<li>First click on Session, then select VNC, then fill in the IP ~~>~~ address and port of the development board, and finally click ~~>~~ OK to confirm</li~~></ol></li></ol~~>

[[File:~~media/image251~~zero3-img251.png~~|490x349px|图片1208~~]]

</div></ol>

<li>Then enter the VNC password set earlier

[[File:~~media/image252~~zero3-img252.png~~|221x105px~~]]</li><li>After successful login, the interface is displayed as shown in the ~~>~~ figure below, and then you can remotely operate the desktop of the ~~>~~ development board linux system</li~~></ol~~>

[[File:~~media/image253~~zero3-img253.png~~|405x293px~~]]</ol></li></ol>

~~~~

== How to install QT ==

<li>Use the script below to install QT5 and QT Creator

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

<li>After installation, the version number of QT will be automatically printed

<li>The qt version that comes with Ubuntu 20.04 is '''5.12.8'''

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

|-

|

orangepi@orangepi:~$ '''install_qt.sh'''

......

QMake version 3.1

Using Qt version '''5.12.8''' in /usr/lib/aarch64-linux-gnu|}</li>

<li>The QT version that comes with Ubuntu 22.04 is '''5.15.3'''

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

|-

|

orangepi@orangepi:~$ '''install_qt.sh'''

......

QMake version 3.1

Using Qt version '''5.15.3''' in /usr/lib/aarch64-linux-gnu|}</li>

<li>The QT version that comes with Debian11 is '''5.15.2'''

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

|-

|

orangepi@orangepi:~$ '''install_qt.sh'''

......

QMake version 3.1

Using Qt version '''5.15.2''' in /usr/lib/aarch64-linux-gnu|}</li>

<li>The QT version that comes with Debian12 is '''5.15.8'''

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

|-

|

orangepi@orangepi:~$ '''install_qt.sh'''

......

QMake version 3.1

Using Qt version '''5.15.8''' in /usr/lib/aarch64-linux-gnu|}</li></ol>

</li>

<li>Then you can see the QT Creator startup icon in '''Applications'''

[[File:~~media/image254~~zero3-img254.png~~|576x270px~~]]

You can also use the following command to open QT Creator

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''qtcreator'''|}</li>

<li>The interface after QT Creator is opened is as follows

[[File:~~media/image255~~zero3-img255.png~~|576x342px~~]]</li>

<li>The version of QT Creator is as follows

<li>The default version of QT Creator in '''Ubuntu20.04''' is as ~~>~~ follows[[File:~~media/image256~~zero3-img256.png~~|419x224px~~]]</li><li>The default version of QT Creator in '''Ubuntu22.04''' is as ~~>~~ follows[[File:~~media/image257~~zero3-img257.png~~|443x237px~~]]</li>

<li>The default version of QT Creator in '''Debian11''' is as follows

[[File:~~media/image258~~zero3-img258.png~~|444x238px~~]]</li>

<li>The default version of QT Creator in '''Debian12''' is as follows

[[File:~~media/image259~~zero3-img259.png~~|449x277px~~]]</li></ol>

</li>

<li>Then set up QT

<li>First open '''Help'''->'''About Plugins.…'''

[[File:~~media/image260~~zero3-img260.png~~|573x164px~~]]</li>

<li>Then remove the tick of '''ClangCodeModel'''

[[File:~~media/image261~~zero3-img261.png~~|408x254px~~]]</li><li>'''After setting, you need to restart QT Creator'''</li><li>Then make sure the GCC compiler used by QT Creator, if the ~~>~~ default is Clang, please modify it to GCC{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Debian12 please skip this step.'''</big>|}[[File:~~media/image262~~zero3-img262.png~~|576x315px~~]][[File:~~media/image263~~zero3-img263.png~~|575x307px~~]]</li></ol>

</li>

<li>Then you can open a sample code

[[File:~~media/image264~~zero3-img264.png~~|575x312px~~]]</li>

<li>After clicking the sample code, the corresponding instruction document will be opened automatically, you can read the instructions carefully

[[File:~~media/image265~~zero3-img265.png~~|576x218px~~]]</li>

<li>Then click '''Configure Project'''

[[File:~~media/image266~~zero3-img266.png~~|575x304px~~]]</li>

<li>Then click the green triangle in the lower left corner to compile and run the sample code

[[File:~~media/image267~~zero3-img267.png~~|575x312px~~]]</li>

<li>After waiting for a period of time, the interface shown in the figure below will pop up, which means that QT can compile and run normally

[[File:~~media/image268~~zero3-img268.png~~|576x308px~~]]</li>

<li>References

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

|-

|

[https://wiki.qt.io/Install_Qt_5_on_Ubuntu '''https://wiki.qt.io/Install_Qt_5_on_Ubuntu''']

[https://download.qt.io/archive/qtcreator '''https://download.qt.io/archive/qtcreator''']

[https://download.qt.io/archive/qt '''https://download.qt.io/archive/qt''']|}</li></ol>

== How to install ROS ==

# The currently active version of ROS 1 is shown below, and the recommended version is '''Noetic Ninjemys'''

:[[File:~~media/image269~~zero3-img269.png~~|345x235px~~]]

:[[File:~~media/image270~~zero3-img270.png~~|576x210px~~]]

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

|-

|

[http://docs.ros.org/ '''http://docs.ros.org''']

'''https://wiki.ros.org/Distributions'''

|}

<li>ROS 1 '''Noetic Ninjemys''' official installation documentation link is as ~~follows：~~follows:{| class="wikitable" style="width:800px;" |-| [http://wiki.ros.org/noetic/Installation/Ubuntu '''http://wiki.ros.org/noetic/Installation/Ubuntu''']|}</li><li>In the ROS '''Noetic Ninjemys''' official installation document, Ubuntu recommends using Ubuntu20.04, so please make sure that the system used by the development board is the '''Ubuntu20.04 desktop system'''{| class="wikitable" style="width:800px;" |-|

[http://wiki.ros.org/noetic/Installation '''http://wiki.ros.org/noetic/Installation''']

|}[[File:~~media/image271~~zero3-img271.png~~|312x176px~~]]</li>

<li>Then use the script below to install ros1

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_ros.sh ros1'''|}</li><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 {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''<~~/li~~span style="color:#FF0000">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</olspan>'''

~~'''Note that running the following command needs to ensure that the development board can access github normally, otherwise an error will be reported due to network problems'''~~

'''The install_ros.sh script will try to modify /etc/hosts and run the following commands automatically. However, this method cannot guarantee that github can be accessed normally every time. If install_ros.sh prompts the following error after installing ros1, please find other ways to allow the linux system of the development board to access github normally, and then manually run the following ~~command。~~command.'''

'''https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml'''

'''Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml'''

'''ERROR: error loading sources list:'''

::'''The read operation timed out'''</big>|}

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

|-

|

orangepi@orangepi:~$ '''source /opt/ros/noetic/setup.bash'''

Recommended: please run

::rosdep update

orangepi@orangepi:~$ '''rosdep update'''

updated cache in /home/orangepi/.ros/rosdep/sources.cache

|}</li></ol>

<li>Then open a command line terminal window on the '''desktop''', and use the '''test_ros.sh''' script to start a small turtle routine to test whether ROS can be used normally

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

<li>After running the '''test_ros.sh''' script, a little turtle as shown in the figure below will pop up

[[File:~~media/image272~~zero3-img272.png~~|575x291px~~]]</li><li>Then please keep the terminal window you just opened on top</li~~></ol~~>

[[File:~~media/image273.jpeg|575x269px|C:\Users\orangepi\Desktop\用户手册插图\Zero3\未标题~~zero3-5img273.~~jpg未标题-5~~png]]

</div></ol>

<li>At this time, press the direction keys on the keyboard to control the little turtle to move up, down, left, and right

[[File:~~media/image274~~zero3-img274.png~~|575x250px~~]]</li></ol>

=== How to install ROS 2 Galactic on Ubuntu 20.04 ===

<li>The currently active version of ROS 2 is shown below, and the recommended version is '''Galactic Geochelone'''

[[File:~~media/image275~~zero3-img275.png~~|576x271px~~]][[File:~~media/image276~~zero3-img276.png~~|575x265px~~]]{| class="wikitable" style="width:800px;" |-|

[http://docs.ros.org/ '''http://docs.ros.org''']

'''http://docs.ros.org/en/galactic/Releases.html'''|}</li><li>The link to the official ROS 2 '''Galactic Geochelone''' installation documentation is as ~~follows：~~follows:{| class="wikitable" style="width:800px;" |-|

'''docs.ros.org/en/galactic/Installation.html'''

'''http://docs.ros.org/en/galactic/Installation/Ubuntu-Install-Debians.html'''|}</li><li>In the official ROS 2 '''Galactic Geochelone''' installation document, Ubuntu Linux recommends using Ubuntu 20.04, so please make sure that the system used by the development board is the '''Ubuntu 20.04 desktop system'''. There are several ways to install ROS 2. The following demonstrates how to install ROS 2 '''Galactic Geochelone''' through '''Debian packages'''.</li>

<li>Ros2 can be installed using the '''install_ros.sh''' script

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_ros.sh ros2'''|}</li>

<li>The '''install_ros.sh''' script will automatically run the '''ros2 -h''' command after installing ros2. If you can see the following print, it means that the ros2 installation is complete

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

|-

|

usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...

ros2 is an extensible command-line tool for ROS 2.

optional arguments:

:-h, --help show this help message and exit

Commands:

:action Various action related sub-commands:bag Various rosbag related sub-commands:component Various component related sub-commands:daemon Various daemon related sub-commands:doctor Check ROS setup and other potential issues:interface Show information about ROS interfaces:launch Run a launch file:lifecycle Various lifecycle related sub-commands:multicast Various multicast related sub-commands:node Various node related sub-commands:param Various param related sub-commands:pkg Various package related sub-commands:run Run a package specific executable:security Various security related sub-commands:service Various service related sub-commands:topic Various topic related sub-commands:wtf Use `wtf` as alias to `doctor` :Call `ros2 <command> -h` for more detailed usage.|}</li>

<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

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

|-

|

orangepi@orangepi:~$ '''test_ros.sh'''

[INFO] [1671174101.200091527] [talker]: Publishing: 'Hello World: 1'

[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]

[INFO] [1671174103.199580322] [talker]: Publishing: 'Hello World: 3'

[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]|}</li>

<li>Run the following command to open rviz2

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

|-

|

orangepi@orangepi:~$ '''source /opt/ros/galactic/setup.bash'''

orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''

|}[[File:~~media/image277~~zero3-img277.png~~|576x324px~~]]</li>

<li>For how to use ROS, please refer to the documentation of ROS 2

{| class="wikitable" style="width:800px;" |-| [http://docs.ros.org/en/galactic/Tutorials.html '''http://docs.ros.org/en/galactic/Tutorials.html''']|}</li></ol>

=== How to install ROS 2 Humble on Ubuntu 22.04 ===

<li>Ros2 can be installed using the '''install_ros.sh''' script

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_ros.sh ros2'''|}</li>

<li>The '''install_ros.sh''' script will automatically run the '''ros2 -h''' command after installing ros2. If you can see the following print, it means that the ros2 installation is complete

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

|-

|

usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...

ros2 is an extensible command-line tool for ROS 2.

optional arguments:

:-h, --help show this help message and exit

Commands:

:action Various action related sub-commands:bag Various rosbag related sub-commands:component Various component related sub-commands:daemon Various daemon related sub-commands:doctor Check ROS setup and other potential issues:interface Show information about ROS interfaces:launch Run a launch file:lifecycle Various lifecycle related sub-commands:multicast Various multicast related sub-commands:node Various node related sub-commands:param Various param related sub-commands:pkg Various package related sub-commands:run Run a package specific executable:security Various security related sub-commands:service Various service related sub-commands:topic Various topic related sub-commands:wtf Use `wtf` as alias to `doctor` :Call `ros2 <command> -h` for more detailed usage.|}</li>

<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

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

|-

|

orangepi@orangepi:~$ '''test_ros.sh'''

[INFO] [1671174101.200091527] [talker]: Publishing: 'Hello World: 1'

[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]

[INFO] [1671174103.199580322] [talker]: Publishing: 'Hello World: 3'

[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]|}</li>

<li>Run the following command to open rviz2

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

|-

|

orangepi@orangepi:~$ '''source /opt/ros/humble/setup.bash'''

orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''

|}[[File:~~media/image278~~zero3-img278.png~~|575x323px~~]]</li>

<li>Reference documents

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

|-

|

'''http://docs.ros.org/en/humble/index.html'''

~~[http://docs.ros.org/en/galactic/Tutorials.html~~ '''http://docs.ros.org/en/humble/Installation/Ubuntu-Install-Debians.html''']|}</li></ol>

== How to install the kernel header file ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The Debian 11 system with the Linux6.1 kernel will report a GCC error when compiling the kernel module. So if you want to compile the kernel module, please use Debian12 or Ubuntu22.04'''</big>|}

<li>The Linux image released by OPi comes with the deb package of the kernel header file by default, and the storage location is '''/opt/'''

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

|-

|

orangepi@orangepi:~$ '''ls /opt/linux-headers*'''

/opt/linux-headers-xxx-sun50iw9_x.x.x_arm64.deb|}</li>

<li>Use the following command to install the deb package of the kernel header file

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg -i /opt/linux-headers*.deb'''|}</li>

<li>After installation, you can see the folder where the kernel header files are located under '''/usr/src'''

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

|-

|

orangepi@orangepi:~$ '''ls /usr/src'''

linux-headers-x.x.x|}</li><li>Then you can compile the source code of the hello kernel module that comes with the Linux image. The source code of the hello module is in '''/usr/src/hello'''. After entering this directory, use the make command to ~~compile。~~compile.{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''cd /usr/src/hello/'''

orangepi@orangepi:/usr/src/hello$ '''sudo make'''

make -C /lib/modules/5.4.125/build M=/usr/src/hello modules

make[1]: Entering directory '/usr/src/linux-headers-5.4.125'

:CC [M] /usr/src/hello/hello.o:Building modules, stage 2.:MODPOST 1 modules:CC [M] /usr/src/hello/hello.mod.o:LD [M] /usr/src/hello/hello.komake[1]: Leaving directory '/usr/src/linux-headers-5.4.125'|}</li>

<li>After compiling, the '''hello.ko''' kernel module will be generated

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

|-

|

orangepi@orangepi:/usr/src/hello$ '''ls *.ko'''

hello.ko|}</li>

<li>Using the '''insmod''' command, you can insert the '''hello.ko''' kernel module into the kernel

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:/usr/src/hello$ '''sudo insmod hello.ko'''|}</li>

<li>Then use the '''demsg''' command to view the output of the '''hello.ko''' kernel module. If you can see the output instructions below, the '''hello.ko''' kernel module is loaded correctly

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

|-

|

orangepi@orangepi:/usr/src/hello$ '''dmesg | grep "Hello"'''

[ 2871.893988] '''Hello Orange Pi -- init'''|}</li>

<li>Use the '''rmmod''' command to uninstall the '''hello.ko''' kernel module

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

|-

|

orangepi@orangepi:/usr/src/hello$ '''sudo rmmod hello'''

orangepi@orangepi:/usr/src/hello$ '''dmesg | grep "Hello"'''

[ 2871.893988] Hello Orange Pi -- init

[ 3173.800892] '''Hello Orange Pi -- exit'''|}</li></ol>

== Some programming language tests supported by Linux system ==

<li>The version of gcc is as follows

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

|-

|

orangepi@orangepi:~$ '''gcc --version'''

gcc (Debian 10.2.1-6) 10.2.1 20210110

This is free software; see the source for copying conditions. There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</li>

<li>Write the '''hello_world.c''' program in C language

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

|-

|

orangepi@orangepi:~$ '''vim hello_world.c'''

#include <stdio.h>

int main(void)

{

:printf("Hello World!\n"); :return 0;}|}</li>

<li>Then compile and run '''hello_world.c'''

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

|-

|

orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''

orangepi@orangepi:~$ '''./hello_world'''

Hello World!|}</li></ol>

</li>

<li>Debian Bullseye comes with Python3 installed by default

<li>The specific version of Python is as follows

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

|-

|

orangepi@orangepi:~$ '''python3'''

'''Python 3.9.2''' (default, Feb 28 2021, 17:03:44)

Type "help", "copyright", "credits" or "license" for more information.

>>>

|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| '''Use the Ctrl+D shortcut to exit python's interactive ~~mode。~~mode.'''|}</li>

<li>Write '''hello_world.py''' program in Python language

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

|-

|

orangepi@orangepi:~$ '''vim hello_world.py'''

print('Hello World!')|}</li>

<li>The result of running '''hello_world.py''' is as follows

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

|-

|

orangepi@orangepi:~$ '''python3 hello_world.py'''

Hello World!|}</li></ol>

</li>

<li>Debian Bullseye does not install Java compilation tools and runtime environment by default

<li>You can use the following command to install openjdk, the latest ~~>~~ version in Debian Bullseye is openjdk-17{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''|}</li>

<li>After installation, you can check the version of Java

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''java --version'''|}</li>

<li>Edit '''hello_world.java of java version'''

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

|-

|

orangepi@orangepi:~$ '''vim hello_world.java'''

public class hello_world

{

:public static void main(String[] args):{::System.out.println("Hello World!");:}

}

~~~~|}~~~~</li>

<li>Then compile and run'''hello_world.java'''

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

|-

|

orangepi@orangepi:~$ '''javac hello_world.java'''

orangepi@orangepi:~$ '''java hello_world'''

Hello World!|}</li></ol>

</li></ol>

=== Debian Bookworm System ===

<li>The version of gcc is as follows

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

|-

|

orangepi@orangepi:~$ '''gcc --version'''

gcc (Debian 12.2.0-14) 12.2.0

This is free software; see the source for copying conditions. There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</li>

<li>Write the '''hello_world.c''' program in C language

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

|-

|

orangepi@orangepi:~$ '''vim hello_world.c'''

#include <stdio.h>

int main(void)

{

:printf("Hello World!\n"); :return 0;}|}</li>

<li>Then compile and run '''hello_world.c'''

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

|-

|

orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''

orangepi@orangepi:~$ '''./hello_world'''

Hello World!|}</li></ol>

</li>

<li>Debian Bookworm has Python3 installed by default

<li>The specific version of Python is as follows

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

|-

|

orangepi@orangepi:~$ '''python3'''

Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] on linux

Type "help", "copyright", "credits" or "license" for more information.

>>>

|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Use the Ctrl+D shortcut to exit python's interactive ~~mode。~~mode.'''</big>|}</li>

<li>Write '''hello_world.py''' program in Python language

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

|-

|

orangepi@orangepi:~$ '''vim hello_world.py'''

print('Hello World!')|}</li>

<li>The result of running '''hello_world.py''' is as follows

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

|-

|

orangepi@orangepi:~$ '''python3 hello_world.py'''

Hello World!|}</li></ol>

</li>

<li>Debian Bookworm does not install Java compilation tools and operating environment by default

<li>You can use the following command to install openjdk, the latest ~~>~~ version in Debian Bookworm is openjdk-17{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''|}</li>

<li>After installation, you can check the version of Java

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''java --version'''|}</li>

<li>Edit the Javaverison’s '''hello_world.java'''

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

|-

|

orangepi@orangepi:~$ '''vim hello_world.java'''

public class hello_world

{

:public static void main(String[] args):{::System.out.println("Hello World!");:}

}

~~~~|}~~~~</li>

<li>Then compile and run'''hello_world.java'''

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

|-

|

orangepi@orangepi:~$ '''javac hello_world.java'''

orangepi@orangepi:~$ '''java hello_world'''

Hello World!|}</li></ol>

</li></ol>

=== Ubuntu Focal System ===

<li>The version of a.gcc is as follows

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

|-

|

orangepi@orangepi:~$ '''gcc --version'''

gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0

This is free software; see the source for copying conditions. There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</li>

<li>Write the '''hello_world.c''' program in C language

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

|-

|

orangepi@orangepi:~$ '''vim hello_world.c'''

#include <stdio.h>

int main(void)

{

:printf("Hello World!\n"); :return 0;}|}</li>

<li>Then compile and run '''hello_world.c'''

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

|-

|

orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''

orangepi@orangepi:~$ '''./hello_world'''

Hello World!|}</li></ol>

</li>

<li>Ubuntu Focal has Python3 installed by default

<li>The specific version of Python3 is as follows

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

|-

|

orangepi@orangepi:~$ '''python3'''

Python 3.8.10 (default, Nov 14 2022, 12:59:47)

Type "help", "copyright", "credits" or "license" for more information.

>>>

|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Use the Ctrl+D shortcut to exit python's interactive mode.'''</big>|}</li>

<li>Write the '''hello_world.py''' program in Python language

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

|-

|

orangepi@orangepi:~$ '''vim hello_world.py'''

print('Hello World!')|}</li>

<li>The result of running '''hello_world.py''' is as follows

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

|-

|

orangepi@orangepi:~$ '''python3 hello_world.py'''

Hello World!|}</li></ol>

</li>

<li>Ubuntu Focal does not install Java compilation tools and operating environment by default

<li>You can use the following command to install openjdk-17

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''|}</li>

<li>After installation, you can check the version of Java

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

|-

|

orangepi@orangepi:~$ '''java --version'''

openjdk 17.0.2 2022-01-18

OpenJDK Runtime Environment (build 17.0.2+8-Ubuntu-120.04)

OpenJDK 64-Bit Server VM (build 17.0.2+8-Ubuntu-120.04, mixed mode, sharing)|}</li>

<li>Write the Java version of '''hello_world.java'''

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

|-

|

orangepi@orangepi:~$ '''vim hello_world.java'''

public class hello_world

{

:public static void main(String[] args):{::System.out.println("Hello World!");:}

}

~~~~|}~~~~</li>

<li>Then compile and run '''hello_world.java'''

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

|-

|

orangepi@orangepi:~$ '''javac hello_world.java'''

orangepi@orangepi:~$ '''java hello_world'''

Hello World!|}</li></ol>

</li></ol>

=== Ubuntu Jammy System ===

<li>The version of a.gcc is as follows

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

|-

|

orangepi@orangepi:~$ '''gcc --version'''

gcc (Ubuntu 11.3.0-1ubuntu1~22.04.1) '''11.3.0'''

This is free software; see the source for copying conditions. There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</li>

<li>Write the '''hello_world.c''' program in C language

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

|-

|

orangepi@orangepi:~$ '''vim hello_world.c'''

#include <stdio.h>

int main(void)

{

:printf("Hello World!\n"); :return 0;}|}</li>

<li>Then compile and run '''hello_world.c'''

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

|-

|

orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''

orangepi@orangepi:~$ '''./hello_world'''

Hello World!|}</li></ol>

</li>

<li>Ubuntu Jammy has Python3 installed by default

<li>The specific version of Python3 is as follows

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

|-

|

orangepi@orangepi:~$ '''python3'''

Python 3.10.6 (main, May 29 2023, 11:10:38) [GCC 11.3.0] on linux

Type "help", "copyright", "credits" or "license" for more information.

>>>

|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Use the Ctrl+D shortcut to exit python's interactive mode.'''</big>|}</li>

<li>Write the '''hello_world.py''' program in Python language

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

|-

|

orangepi@orangepi:~$ '''vim hello_world.py'''

print('Hello World!')|}</li>

<li>The result of running '''hello_world.py''' is as follows

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

|-

|

orangepi@orangepi:~$ '''python3 hello_world.py'''

Hello World!|}</li></ol>

</li>

<li>Ubuntu Jammy does not install Java compilation tools and operating environment by default

<li>You can use the following command to install openjdk-18

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-18-jdk'''|}</li>

<li>After installation, you can check the version of Java

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

|-

|

orangepi@orangepi:~$ '''java --version'''

openjdk 18.0.2-ea 2022-07-19

OpenJDK Runtime Environment (build 18.0.2-ea+9-Ubuntu-222.04)

OpenJDK 64-Bit Server VM (build 18.0.2-ea+9-Ubuntu-222.04, mixed mode, sharing)|}</li>

<li>Write the Java version of '''hello_world.java'''

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

|-

|

orangepi@orangepi:~$ '''vim hello_world.java'''

public class hello_world

{

:public static void main(String[] args):{::System.out.println("Hello World!");:}

}

~~~~|}~~~~</li>

<li>Then compile and run '''hello_world.java'''

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

|-

|

orangepi@orangepi:~$ '''javac hello_world.java'''

orangepi@orangepi:~$ '''java hello_world'''

Hello World!|}</li></ol>

</li></ol>

== The method of uploading files to the Linux system of the development board ==

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

<li>'''~~file_path：~~file_path:'''Need to be replaced with the path of the file to ~~>~~ be uploaded</li><li>'''~~orangepi：~~orangepi:''' It is the user name of the Linux system of the ~~>~~ development board, and it can also be replaced with other ~~>~~ ones, such as root</li><li>'''192.168.xx.xx:''' It is the IP address of the development ~~>~~ board, please modify it according to the actual situation</li><li>'''/home/orangepi:''' The path in the Linux system of the ~~>~~ development board can also be modified to other paths{| class="wikitable" style="width:800px;" |-| test@test:~$ '''scp file_path orangepi@192.168.xx.xx:/home/orangepi/'''|}</li></ol>

</li>

<li>If you want to upload a folder, you need to add the -r parameter

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''scp -r dir_path orangepi@192.168.xx.xx:/home/orangepi/'''|}</li><li>There are more usages of scp, please use the following command to view the man manual</li~~></ol~~>

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

|-

|

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

|}

</ol>

~~~~

==== How to upload files using filezilla ====

<li>First install filezilla in Ubuntu PC

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

<li>Then use the following command to open filezilla

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''filezilla'''|}</li>

<li>The interface after filezilla is opened is as follows, at this time, the display under the remote site on the right is empty

[[File:~~media/image279~~zero3-img279.png~~|576x453px|截图 2022-12-03 19-04-40~~]]

</div></li>

<li>The method of connecting the development board is shown in the figure below</p~~></li></ol~~>

[[File:~~media/image280~~zero3-img280.png~~|575x128px|图片565~~]]

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

<li>Then choose to '''save the password''', and then click '''OK'''

[[File:~~media/image281~~zero3-img281.png~~|249x181px~~]]</li><li>Then choose to '''always trust this host''', and then click '''OK'''</p~~></li></ol~~>

[[File:~~media/image282~~zero3-img282.png~~|278x150px|IMG_256~~]]

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

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

[[File:~~media/image283~~zero3-img283.png~~|533x330px|IMG_256~~]]

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

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

[[File:~~media/image284~~zero3-img284.png~~|529x414px|IMG_256~~]]

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

<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 files</li>

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

=== How to upload files to the development board Linux system in Windows PC ===

# First download the installation file of the Windows version of the filezilla software, the download link is as follows

~~[https~~:~~//filezilla~~:{| class="wikitable" style="width:800px;" |-~~project.org/download.php?type=client~~ | '''https://filezilla-project.org/download.php?type=client''']|} ::[[File:~~media/image285.jpeg|472x171px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~zero3-15img285.~~jpg未标题-15~~png]]

::[[File:~~media/image286~~zero3-img286-1.png~~|384x276px~~]]

<li>The downloaded installation package is as follows, and then double-click to install directly

{| class="wikitable" style="width:800px;" |-| '''FileZilla_Server_1.5.1_win64-setup.exe'''|}</li><li>During the installation process, please select Decline on the following installation interface, and then select Next></p~~></li></ol~~>

[[File:~~media/image287~~zero3-img287.png~~|355x279px|IMG_256~~]]

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

<li>The interface after filezilla is opened is as follows, and the display under the remote site on the right is empty~~</li></ol>~~

[[File:~~media/image288~~zero3-img288.png~~|451x357px|IMG_256~~]]

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

<li>The method of connecting the development board is shown in the figure below:~~</li></ol>~~

[[File:~~media/image280~~zero3-img280.png~~|575x128px|图片565~~]]

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

<li>Then choose to '''save the password''', and then click '''OK'''~~</li></ol>~~

[[File:~~media/image289~~zero3-img289.png~~|207x146px|IMG_256~~]]

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

<li>Then select '''Always trust this host''', and click '''OK'''~~</li></ol>~~

[[File:~~media/image290~~zero3-img290.png~~|221x109px|IMG_256~~]]

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

<li>~~After~~ Then select the ~~connection is successful, you can see~~ path to be uploaded to the development board on the ~~directory structure~~ right side of the ~~development board linux~~ filezilla software, and then select the file ~~system~~ to be uploaded on the Windows PC on the ~~right~~ left side of the filezilla software~~</li></ol>~~, then click the right mouse button, and then click the upload option to start uploading the file to the development board.

[[File:~~media/image291~~zero3-img291.~~jpeg|446x329px|图片3~~png]]

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

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

[[File:~~media/image292~~zero3-img292.png~~|461x340px|IMG_256~~]]

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

<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 files</li>

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

== Instructions for using the switch logo ==

<li>By default, the switch logo will only be displayed in the desktop version of the system</li>

<li>Set the '''bootlogo''' variable to '''false''' in '''/boot/orangepiEnv.txt''' to turn off the switch logo

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

|-

|

orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''

verbosity=1

'''bootlogo=false'''|}</li>

<li>Set the '''bootlogo''' variable to '''true''' in '''/boot/orangepiEnv.txt''' to enable the switch logo

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

|-

|

orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''

verbosity=1

'''bootlogo=true'''|}</li>

<li>The location of the boot logo image in the Linux system is

{| class="wikitable" style="width:800px;" |-| '''/usr/share/plymouth/themes/orangepi/watermark.png'''|}</li>

<li>After replacing the boot logo picture, you need to run the following command to take effect

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo update-initramfs -u'''|}</li></ol>

== How to shut down and restart the development board ==

<li>During the running of the Linux system, if the power is directly unplugged, the file system may lose some data. It is recommended to use the '''poweroff''' command to shut down the Linux system of the development board before power off, and then unplug the power

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

|-

|

orangepi@orangepi:~$ '''sudo poweroff'''

|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that after the development board is turned off, the power supply needs to be re-plugged to turn it on.'''</big>|}</li><li>Use the '''reboot''' command to restart the Linux system on the development board{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo''' '''reboot'''|}</li></ol>

== Compilation system requirements ==

The Linux SDK, '''orangepi-build''', only supports running on X64 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.

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

|-

|

test@test:~$ '''lsb_release -a'''

Description: Ubuntu 22.04 LTS

Release: '''22.04'''

Codename: '''jammy'''

|}

If the computer is installed with a 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 note, do not 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, and please do not compile it on the Linux system of the development board Use orangepi-build in. The download address of the installation image of Ubuntu 22.04 '''amd64''' version is:

~~[https~~{| class="wikitable" style="width:~~//repo.huaweicloud.com/ubuntu~~800px;" |-~~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''']|}

~~After installing Ubuntu 22.04 on~~ <span id="get-the ~~computer or virtual machine, please set the software~~ -source -code-of Ubuntu 22.04 to Tsinghua source (or other domestic sources that you think is fast), otherwise it is easy to make mistakes due to network reasons when installing software later. The steps to replace Tsinghua source are as follows:-linux-sdk">

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

~~[https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/ '''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.~~

~~[[File:media/image293.png|576x241px]]</li>~~

~~<li>The content of the '''/etc/apt/sources.list''' file that needs to be > replaced is:~~

~~test@test:~$ '''sudo mv /etc/apt/sources.list cat /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</li>~~

~~<li>After the replacement, you need to update the download information > and make sure that there is no error.~~

~~test@test:~$ '''sudo apt-get update'''</li>~~

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

The linux sdk 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. Use the following command to download the orangepi-build code:

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

|-

|

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

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the development board using the H618 Soc needs to download the source code of the next branch of orangepi-build. The above git clone command needs to specify the branch of the orangepi-build source code as next.'''</big>

[[File:~~media/image294~~zero3-img294.png|~~576x298px~~780px|~~图片6~~center]]

</div>

|} {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Downloading the orangepi-build code through the git clone command does not require entering the user name and password of the github account (the same is true for downloading other codes in this manual), if the Ubuntu PC prompts the user to enter the github account after entering the git clone command The name and password are usually entered incorrectly in the address of the orangepi-build warehouse behind the git clone. Please check the spelling of the command carefully, instead of thinking that we forgot to provide the username and password of the github account.'''</big>|}

The u-boot and linux kernel versions currently used by the H618 series development boards are as follows:

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

|-

|-

|-

|}

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The branch mentioned here is not the same thing as the branch of the orangepi-build source code, please do not confuse it. This branch is mainly used to distinguish different kernel source code versions.'''

'''We currently define the linux5.4 bsp kernel provided by Allwinner as the current branch. The latest linux6.1 LTS kernel is defined as the next branch.'''</big>|}

After orangepi-build is downloaded, it will contain the following files and folders:

<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

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

|-

|

test@test:~/orangepi-build$ '''ls'''

'''build.sh     external     LICENSE     README.md     scripts'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If you downloaded the code of orangepi-build from github, after downloading, you may find that orangepi-build does not contain the source code of u-boot and linux kernel, nor does u-boot and linux kernel need to use cross-compilation tools Chain, this is normal, because these things are stored in other separate github warehouses or some servers (the addresses will be detailed below). orangepi-build will specify the address of u-boot, linux kernel and cross-compilation toolchain in the script and configuration file. When running orangepi-build, when it finds that there are no such things locally, it will automatically go to the corresponding place to download them.'''</big>|}</li></ol>

=== Download the cross-compilation toolchain ===

[[File:~~media/image295~~zero3-img295.png|~~575x278px|选区_396~~1200px]]

</div>

The mirror URL of the cross-compilation toolchain in China is the open source software mirror site of Tsinghua University:

~~[https~~{| class="wikitable" style="width:~~//mirrors.tuna.tsinghua.edu.cn/armbian~~800px;" |-~~releases/_toolchain/~~ | '''https://~~mirrors~~imola.~~tuna.tsinghua.edu~~armbian.cncom/~~armbian-releases~~dl/_toolchain/''']|}

After the '''toolchains''' are downloaded, it will contain multiple versions of the cross-compilation toolchain:

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

|-

|

test@test:~/orangepi-build$ '''ls toolchains/'''

gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu ~~gcc-linaro-4.9.4-2017.01-x86_64_aarch64-linux-gnu gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabi~~

~~gcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf~~ gcc-linaro-4.9.4-2017.01-~~x86_64_arm~~x86_64_aarch64-linux-~~gnueabi gcc-linaro-aarch64-none-elf-4.8-2013.11_linux~~gnu

~~gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu~~ gcc-linaro-57.54.01-~~2017~~2019.1002-x86_64_arm-linux-~~gnueabihf gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux~~gnueabi

gcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabi gcc-linaro-aarch64-none-elf-4.8-2013.11_linux gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu gcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabihf gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu gcc-linaro-arm-none-eabi-4.8-2014.04_linux|}

The cross-compilation toolchain used to compile the H618 Linux kernel source code is:

<li>linux5.4

{| class="wikitable" style="width:800px;" |-| '''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''|}</li>

<li>linux6.1

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

|-

|

'''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''

|}</li></ol>The cross-compilation toolchain used to compile the H618 u-boot source code is:~~</li></ol>~~

<li>v2018.05

{| class="wikitable" style="width:800px;" |-| '''gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabi'''|}</li>

<li>v2021.07

{| class="wikitable" style="width:800px;" |-| '''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''|}</li></ol>

=== orangepi-build complete directory structure description ===

<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

<li>The git warehouse where the linux kernel source code is stored ~~>~~ is as follows, pay attention to switch the branch of the ~~>~~ linux-orangepi warehouse to<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) Linux5.4~~https~~{| class="wikitable" style="width:~~//github.com/orangepi-xunlong/linux-orangepi/tree/'''orange-pi~~800px;" |-~~5.4-sun50iw9'''</li><li>Linux6.1~~| https://github.com/orangepi-xunlong/linux-orangepi/tree/~~'''~~orange-pi-65.14-sun50iw9~~'''~~~~</li></ol>~~|}

</li>

<li>b) Linux6.1{| class="wikitable" style="width:800px;" |-| https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-6.1-sun50iw9|}</li></ol></li><li>The git warehouse where the u-boot source code is stored is as ~~>~~ follows, pay attention to switch the branch of the ~~>~~ u-boot-orangepi warehouse to<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) v2018.05{| class="wikitable" style="width:800px;" |-| https://github.com/orangepi-xunlong/u-boot-orangepi/tree/~~'''~~v2018.05-h618~~'''~~|}</li><li>b) v2021.07{| class="wikitable" style="width:800px;" |-| https://github.com/orangepi-xunlong/u-boot-orangepi/tree/v2021.07-sunxi|}</li></ol>

</li></ol>

~~https://github.com/orangepi-xunlong/u-boot-orangepi/tree/'''v2021.07-sunxi'''~~

<li>'''build.sh''': Compile the startup script</li>

<li>'''external''': Contains the configuration files needed for ~~>~~ compiling the image, scripts for specific functions, and the ~~>~~ source code of some programs. The rootfs compressed package ~~>~~ cached during the compiling process is also stored in external</li>

<li>'''kernel''': Store the source code of the linux kernel</li>

<li>'''LICENSE''': GPL 2 license file</li>

<li>'''README.md''': orangepi-build documentation</li>

<li>'''output''': Store compiled u-boot, linux and other deb packages, ~~>~~ compilation logs, and compiled images and other files</li>

<li>'''scripts''': General script for compiling linux images</li>

<li>'''toolchains''': Store the cross-compilation toolchain</li>

<li>'''u-boot''': Store the source code of u-boot</li>

<li>'''userpatches''': Store the configuration files needed to compile ~~>~~ the script{| class="wikitable" style="width:800px;" |-|

test@test:~/orangepi-build$ '''ls'''

'''build.sh     external     kernel     LICENSE     output     README.md     scripts     toolchains     u-boot     userpatches'''|}</li></ol>

</li></ol>

== Compile u-boot ==

<li>Run the build.sh script, remember to add sudo permission

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

<li>Select '''U-boot package''', then press Enter

[[File:~~media/image296~~zero3-img296.png~~|576x132px|选区_238~~]]

</div></li>

<li>Then select the model of the development board

[[File:~~media/image297~~zero3-img297.png~~|576x123px~~]]</li>

<li>Then select the branch type of u-boot

<li>The current branch will compile the u-boot v2018.05 code that ~~>~~ needs to be used in the linux5.4 image</li><li>The next branch will compile the u-boot v2021.07 version code ~~>~~ that needs to be used in the linux6.1 image[[File:~~media/image298~~zero3-img298.png~~|576x77px~~]]</li></ol>

</li>

<li>Then it will start to compile u-boot, and part of the information prompted when compiling the next branch is as follows:

<li>u-boot source code version

{| class="wikitable" style="width:800px;" |-| [ o.k. ] Compiling u-boot [ '''v2021.07''' ]|}</li>

<li>The version of the cross-compilation toolchain

{| class="wikitable" style="width:800px;" |-| [ o.k. ] Compiler version [ '''aarch64-linux-gnu-gcc 11''' ]|}</li>

<li>Path to the generated u-boot deb package

{| class="wikitable" style="width:800px;" |-| [ o.k. ] Target directory [ '''orangepi-build/output/debs/u-boot''' ]|}</li>

<li>The package name of the generated u-boot deb package

{| class="wikitable" style="width:800px;" |-| [ o.k. ] File name [ '''linux-u-boot-next-orangepizero3_x.x.x_arm64.deb''' ]|}</li>

<li>Compilation time

{| class="wikitable" style="width:800px;" |-| [ o.k. ] Runtime [ '''1 min''' ]</p~~></li~~>~~<li>Repeat the command to compile u-boot, use the following command > to start compiling u-boot directly without selecting through > the graphical interface[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepizero3 BRANCH=next BUILD_OPT=u-boot''' ]</li></ol>~~|}

</li>

<li>Repeat the command to compile u-boot, use the following command to start compiling u-boot directly without selecting through the graphical interface{| class="wikitable" style="width:800px;" |-| [ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepizero3 BRANCH=next BUILD_OPT=u-boot''' ]|}</li></ol></li><li>View the u-boot deb package generated by compilation{| class="wikitable" style="width:800px;" |-|

test@test:~/orangepi-build$ '''ls output/debs/u-boot/'''

'''linux-u-boot-next-orangepizero3_x.x.x_arm64.deb'''|}</li>

<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)''', otherwise the changes made will be restored, the method is as follows:

Set the IGNORE_UPDATES variable in '''userpatches/config-default.conf''' to "yes"

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

|-

|

test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''

......

IGNORE_UPDATES="'''yes'''"......|}</li>

<li>When debugging u-boot code, you can use the following method to update u-boot in the linux image for testing

<li>First upload the compiled u-boot deb package to the linux system ~~>~~ of the development board{| class="wikitable" style="width:800px;" |-|

test@test:~/orangepi-build$ '''cd output/debs/u-boot'''

test@test:~/orangepi_build/output/debs/u-boot$ '''scp \'''

'''linux-u-boot-next-orangepizero3_x.x.x_arm64.deb ~~[mailto:root@192.168.1.xxx:/root~~ root@192.168.1.xxx:/root]'''|}</li>

<li>Install the new u-boot deb package just uploaded

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg -i''' '''linux-u-boot-next-orangepizero3_x.x.x_arm64.deb'''|}</li>

<li>Then run the nand-sata-install script

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo nand-sata-install'''|}</li>

<li>Then select '''5 Install/Update the bootloader on SD/eMMC'''

[[File:~~media/image299~~zero3-img299.png~~|320x174px~~]]</li>

<li>After pressing the Enter key, a Warning will pop up first

[[File:~~media/image300~~zero3-img300.png~~|314x170px~~]]</li><li>Press the Enter key again to start updating u-boot, and the ~~>~~ following information will be displayed after the update[[File:~~media/image301~~zero3-img301.png~~|292x164px~~]]</li><li>Then you can restart the development board to test whether the ~~>~~ modification of u-boot takes effect</li></ol>

</li></ol>

== Compile the linux kernel ==

<li>Run the '''build.sh''' script, remember to add sudo permission

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

<li>Select '''Kernel package''', then press Enter

[[File:~~media/image302~~zero3-img302.png~~|575x116px|选区_240~~]]

</div></li>

<li>Then you will be prompted whether you need 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.

[[File:~~media/image303~~zero3-img303.png~~|576x87px~~]]</li>

<li>Then select the model of the development board

[[File:~~media/image297~~zero3-img297.png~~|576x123px~~]]</li>

<li>Then select the branch type of the kernel source code

<li>current branch will compile linux5.4 kernel source code</li>

<li>The next branch will compile the linux6.1 kernel source code

[[File:~~media/image298~~zero3-img298.png~~|576x77px~~]]</li></ol>

</li>

<li>If you choose to display the kernel configuration menu (the second option) in step 3), 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, it will start compiling the kernel source code.

[[File:~~media/image304~~zero3-img304.png~~|575x357px~~]]</p~~></li></ol~~>

~~~~

<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{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''sudo ./build.sh KERNEL_CONFIGURE=no'''|}</li><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[[File:~~media/image305~~zero3-img305.png~~|574x234px~~]]</li></ol></li></ol>

<li>Part of the information prompted when compiling the next branch kernel source code is as ~~follows：~~follows:

<li>The version of the linux kernel source code

{| class="wikitable" style="width:800px;" |-| [ o.k. ] Compiling current kernel [ '''6.1.31''' ]|}</li>

<li>The version of the cross-compilation toolchain used

{| class="wikitable" style="width:800px;" |-| [ o.k. ] Compiler version [ '''aarch64-linux-gnu-gcc 11''' ]|}</li><li>The configuration file used by the kernel by default and the ~~>~~ path where it is stored are as follows{| class="wikitable" style="width:800px;" |-| [ o.k. ] Using kernel config file [ '''orangepi-build/external/config/kernel/linux-6.1-sun50iw9-next.config''' ]|}</li><li>The path of the deb package related to the kernel generated by ~~>~~ compiling{| class="wikitable" style="width:800px;" |-| [ o.k. ] Target directory [ '''output/debs/''' ]|}</li><li>The package name of the compiled kernel image deb package{| class="wikitable" style="width:800px;" |-| [ o.k. ] File name [ '''linux-image-next-sun50iw9_x.x.x_arm64.deb''' ]|}</li><li>The time used for compilation{| class="wikitable" style="width:800px;" |-| [ o.k. ] Runtime [ '''10 min''' ]|}</li><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{| class="wikitable" style="width:800px;" |-| [ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepizero3 BRANCH=next BUILD_OPT=kernel KERNEL_CONFIGURE=no''' ]|}</li></ol>

</li>

<li>View the deb package related to the kernel generated by compilation

<li>'''linux-dtb-next-sun50iw9_x.x.x_arm64.deb''' Contains dtb files ~~>~~ used by the kernel</li><li>'''linux-headers-next-sun50iw9_x.x.x_arm64.deb''' Include kernel ~~>~~ headers</li><li>'''linux-image-next-sun50iw9_x.x.x_arm64.deb''' Contains kernel ~~>~~ images and kernel modules{| class="wikitable" style="width:800px;" |-|

test@test:~/orangepi-build$ '''ls output/debs/linux-*'''

output/debs/linux-dtb-next-sun50iw9_x.x.x_arm64.deb

output/debs/linux-headers-next-sun50iw9_x.x.x_arm64.deb

output/debs/linux-image-next-sun50iw9_x.x.x_arm64.deb|}</li></ol>

</li>

<li>When the orangepi-bulid compilation system compiles the linux kernel source code, it first synchronizes the linux kernel source code with the linux kernel source code of the github server, so if you want to modify the linux kernel source code, you first need to turn off the update function of the source code '''(the linux kernel needs to be fully compiled once This function can only be turned off after the source code, otherwise it will prompt that the source code of the linux kernel cannot be found)''', otherwise the changes made will be restored, the method is as ~~follows：~~follows:

Set the IGNORE_UPDATES variable in '''userpatches/config-default.conf''' to "yes"

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

|-

|

test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''

IGNORE_UPDATES="'''yes'''"|}</li>

<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

<li>Upload the deb package of the compiled linux kernel to the linux ~~>~~ system of the development board{| class="wikitable" style="width:800px;" |-|

test@test:~/orangepi-build$ '''cd output/debs'''

test@test:~/orangepi-build/output/debs$ '''scp \'''

'''linux-image-next-sun50iw9_x.x.x_arm64.deb root@192.168.1.xxx:/root'''|}</li>

<li>Install the deb package of the new linux kernel just uploaded

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg -i linux-image-next-sun50iw9_x.x.x_arm64.deb'''|}</li><li>Then restart the development board, and then check whether the ~~>~~ kernel-related modifications have taken effect{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo''' '''reboot'''|}</li></ol>

</li></ol>

== Compile rootfs ==

<li>Run the build.sh script, remember to add sudo permission

{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''sudo ./build.sh'''|}</li><li>Select '''Rootfs and all deb packages''', then press Enter</p~~></li></ol~~>

[[File:~~media/image306~~zero3-img306.png~~|576x119px|选区_241~~]]

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

<li>Then select the model of the development board

[[File:~~media/image297~~zero3-img297.png~~|576x123px~~]]</li>

<li>Then select the branch type of the kernel source code, the type of rootfs maintained by different versions of the kernel source code is different

<li>The current branch can see debian11, ubuntu20.04, ubuntu22.04 ~~>~~ three options</li><li>The next branch can see debian11, debian12, ubuntu22.04 three ~~>~~ options[[File:~~media/image298~~zero3-img298.png~~|576x77px~~]]</li></ol>

</li>

<li>Then select the type of rootfs

[[File:~~media/image307~~zero3-img307.png~~|576x79px~~]]</li>

<li>Then select the type of image

<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 mirror image with ~~>~~ a desktop, which is relatively large

[[File:~~media/image308~~zero3-img308.png~~|576x75px|选区_245~~]]

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

[[File:~~media/image309~~zero3-img309.png~~|576x78px|选区_397~~]]

</div></li>

<li>If you are compiling the image of the desktop version, you also need to select the type of desktop environment. Currently only XFCE is maintained, so please choose the XFCE type desktop

[[File:~~media/image310~~zero3-img310.png~~|576x76px~~]][[File:~~media/image311~~zero3-img311.png~~|576x74px~~]]

You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.

[[File:~~media/image312~~zero3-img312.png~~|575x264px~~]]</li>

<li>Then it will start to compile rootfs, and some information prompted during compilation is explained as follows

<li>The type of rootfs

{| class="wikitable" style="width:800px;" |-| [ o.k. ] local not found [ Creating new rootfs cache for '''bullseye''' ]|}</li>

<li>The storage path of the compiled rootfs compressed package

{| class="wikitable" style="width:800px;" |-| [ o.k. ] Target directory [ '''orangepi-build/external/cache/rootfs''' ]|}</li><li>The name of the rootfs compressed package generated by ~~>~~ compilation{| class="wikitable" style="width:800px;" |-| [ o.k. ] File name [ '''bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4''' ]|}</li></ol>

</li>

<li>View the rootfs compressed package generated by compilation

<li>'''bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4''' ~~>~~ is the rootfs compressed package, the meaning of each field of ~~>~~ the name is<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) '''bullseye''' indicates the type of linux distribution of ~~>~~ rootfs</li><li>b) '''xfce''' means rootfs is the type of desktop version, if it ~~>~~ is '''cli''', it means the type of server version</li><li>c) '''arm64''' represents the architecture type of rootfs</li><li>d) '''25250ec7002de9e81a41de169f1f89721''' 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>'''bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4.list''' ~~>~~ lists the package names of all packages installed by rootfs{| class="wikitable" style="width:800px;" |-|

test@test:~/orangepi-build$ '''ls external/cache/rootfs/'''

bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4

bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4.current

bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4.list|}</li></ol>

</li>

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

<li>Run the '''build.sh''' script, remember to add sudo permission

{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''sudo ./build.sh'''|}</li><li>Select '''Full OS image for flashing''', then press Enter</p~~></li></ol~~>

[[File:~~media/image313~~zero3-img313.png~~|576x128px|选区_242~~]]

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

<li>Then select the model of the development board

[[File:~~media/image297~~zero3-img297.png~~|576x123px~~]]</li>

<li>Then select the branch type of the kernel source code, the type of rootfs maintained by different versions of the kernel source code is different

<li>The current branch can see debian11, ubuntu20.04, ubuntu22.04 ~~>~~ three options</li><li>The next branch can see debian11, debian12, ubuntu22.04 three ~~>~~ options[[File:~~media/image298~~zero3-img298.png~~|576x77px~~]]</li></ol>

</li>

<li>Then select the type of rootfs

[[File:~~media/image307~~zero3-img307.png~~|576x79px~~]]</li>

<li>Then select the type of image

<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 mirror image with ~~>~~ a desktop, which is relatively large

[[File:~~media/image308~~zero3-img308.png~~|576x75px|选区_245~~]]

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

[[File:~~media/image309~~zero3-img309.png~~|576x78px|选区_397~~]]

</div></li>

<li>If you are compiling the image of the desktop version, you also need to select the type of desktop environment. Currently only XFCE is maintained, so please select the XFCE type desktop

[[File:~~media/image310~~zero3-img310.png~~|576x76px~~]][[File:~~media/image311~~zero3-img311.png~~|576x74px~~]]

You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.

[[File:~~media/image312~~zero3-img312.png~~|575x264px~~]]</li>

<li>Then it will start to compile the linux image. The general process of compilation is as follows

<ol style="list-style-type: lower-alpha;"><li>a. Initialize the compilation environment of Ubuntu PC and install the software packages required for the compilation process</li><li>b. Download the source code of u-boot and linux kernel (if cached, only update the code)</li><li>c. Compile u-boot source code and generate u-boot deb package</li><li>d. Compile the linux source code and generate linux-related deb packages</li><li>e. Make the deb package of linux firmware</li><li>f. Make the deb package of the orangepi-config tool</li><li>g. Create a deb package supported by the board</li><li>h. If you are compiling the desktop image, you will also create desktop-related deb packages</li><li>i. Check whether the rootfs has been cached, if not, recreate the rootfs, if it has been cached, directly decompress and use</li><li>j. Install the previously generated deb package into rootfs</li><li>k. 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>l. Then make an image file and format the partition, the default type is ext4</li><li>m. Then copy the configured rootfs to the mirrored partition</li><li>n. Then update initramfs</li><li>o. Finally, write the bin file of u-boot into the image through the dd command</li></ol></li>

<li>After compiling the image, the following information will be prompted

<li>The storage path of the compiled image

{| class="wikitable" style="width:800px;" |-| [ o.k. ] Done building [ '''output/images/orangepizero3_x.x.x_debian_bullseye_linux6.1.xx_xfce_desktop/orangepizero3_x.x.x_debian_bullseye_linux6.1.xx_xfce_desktop.img''' ]|}</li><li>Compilation time</li>~~</ol></li></ol>~~{| class="wikitable" style="width:800px;" |-|

'''[ o.k. ] Runtime [ 19 min ]'''

|}</ol>

<li>Repeat the command to compile the image, and use the following ~~>~~ command to start compiling the image directly without selecting ~~>~~ through the graphical interface{| class="wikitable" style="width:800px;" |-| [ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepizero3 BRANCH=next BUILD_OPT=image RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=yes''' ]|}</li></ol></li></ol>

= '''Android 12 TV system instructions''' =

== Supported Android versions ==

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

|-

| style="text-align: ~~left~~center;"| Android version| style="text-align: ~~left~~center;"| kernel version

|-

| style="text-align: ~~left~~center;"| '''Android 12 TV version'''| style="text-align: ~~left~~center;"| '''linux5.4'''

|}

== Android 12 TV function adaptation ==

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

|-

| style="text-align: ~~left~~center;"| Function| style="text-align: ~~left~~center;"| Android12

|-

| style="text-align: ~~left~~center;"| HDMI Video| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| HDMI Audio| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| USB2.0 x 3| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| TFcard boot| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| network card| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| infrared| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| WIFI| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| WIFI hotsport| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| Bluetooth| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| BLE Bluetooth| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| headphone audio| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| TV-OUT| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| USB camera| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| LED light| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| Temperature Sensor| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| Mali GPU| style="text-align: ~~left~~center;"| OK

|-

| style="text-align: ~~left~~center;"| video codec| style="text-align: ~~left~~center;"| OK

|}

== Onboard LED light display instructions ==

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

|-

|

| style="text-align: ~~left~~center;"| '''Green Light'''| style="text-align: ~~left~~center;"| '''Red Light'''

|-

| '''u-boot startup phase'''

| style="text-align: ~~left~~center;"| '''Off'''| style="text-align: ~~left~~center;"| '''Bright'''

|-

| '''The kernel boots into the system'''

| style="text-align: ~~left~~center;"| '''Bright'''| style="text-align: ~~left~~center;"| '''Off'''

|}

== Android method to return to the previous interface ==

<li>We generally use the mouse and keyboard to control the Android system of the development board. When entering certain interfaces and need to return to the previous interface or desktop, we can only return through the '''right mouse button''', and the keyboard cannot return.</li>

<li>If you have purchased the infrared remote control (other remote control does not work) and the expansion board that match the development board, after inserting the expansion board into the development board, you can return to the previous menu through the return key in the remote control. The position of the return key is shown in the figure below shown:

[[File:~~media/image314~~zero3-img314.png~~|231x199px~~]]</li></ol>

== How to use ADB ==

=== Use network connection adb debugging ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Using the network adb does not require a USB Type C interface 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 has been connected, and then obtain the IP address of the development board, and then to use.'''</big>|}

<li>Make sure that the '''service.adb.tcp.port''' of the Android system is set to port number 5555

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

|-

|

apollo-p2:/ # '''getprop | grep "adb.tcp"'''

[service.adb.tcp.port]: [5555]|}</li><li>If '''service.adb.tcp.port''' is not set, you can use the following command to set the port number of network adb in the serial port</li>< {| class="wikitable" style="width:800px;" |-| apollo-p2:/~~ol>~~# '''setprop service.adb.tcp.port 5555'''

~~apollo-p2:/ # '''setprop service.adb.tcp.port 5555''' ~~

apollo-p2:/ # '''stop adbd'''

apollo-p2:/ # '''start adbd'''

|}</ol>

<li>Install adb tool on Ubuntu PC

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

|-

|

test@test:~$ '''sudo apt-get update'''

test@test:~$ '''sudo apt-get install -y adb'''|}</li>

<li>Then connect network adb on Ubuntu PC

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

|-

|

test@test:~$ '''adb connect 192.168.1.xxx:5555''' '''(It needs to be modified 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|}</li><li>Then you can log in to the android system through the adb shell on the Ubuntu PC</p~~></li></ol~~>

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

|-

|

test@test:~$ '''adb shell'''

apollo-p2:/ #

|}

</li></ol>

~~~~

=== Use the data cable to connect to adb debugging ===

<li>Prepare a data cable with USB Type C interface, plug one end of the USB interface into the USB interface of the computer, and insert one end of the USB Type C interface into the power interface of the development board. In this case, the development board is powered by the USB interface of the computer, so please make sure that the USB interface of the computer can provide the most power to drive the development board

[[File:~~media/image315~~zero3-img315.png~~|178x178px~~]]</li>

<li>Install adb tool on Ubuntu PC

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

|-

|

test@test:~$ '''sudo apt-get update'''

test@test:~$ '''sudo apt-get install -y adb'''|}</li>

<li>View the identified ADB device

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

|-

|

test@test:~$ '''adb devices'''

List of devices attached

4c00146473c28651dd0        device|}</li><li>Then you can log in to the android system through the adb shell on the Ubuntu PC</p~~></li></ol~~>

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

|-

|

test@test:~$ '''adb shell'''

apollo-p2:/ $

|}

</li></ol>

~~~~

== View the method of setting HDMI display resolution ==

<li>First enter '''Settings'''

[[File:~~media/image316~~zero3-img316.png~~|234x83px~~]]</li>

<li>Then select '''Device Preferences'''

[[File:~~media/image317~~zero3-img317.png~~|415x170px~~]]</li>

<li>Then select '''Display & Sound'''

[[File:~~media/image318~~zero3-img318.png~~|420x133px~~]]</li>

<li>Then select '''Advanced display settings'''

[[File:~~media/image319~~zero3-img319.png~~|423x96px~~]]</li>

<li>Then select '''HDMI outpu mode'''

[[File:~~media/image320~~zero3-img320.png~~|423x101px~~]]</li>

<li>Then you can see the list of resolutions supported by the display. At this time, click the corresponding option to switch to the corresponding resolution. Please note that the resolutions supported by different monitors may be different. If you connect to a TV, you will generally see more resolution options than the picture below.

[[File:~~media/image321~~zero3-img321.png~~|429x136px~~]]</li>

<li>The HDMI output of the development board supports 4K display. When connected to a 4K TV, you can see the option of 4K resolution

[[File:~~media/image322~~zero3-img322.png~~|429x242px~~]]</li></ol>

<li>HDMI to VGA Converter

[[File:~~media/image145~~zero3-img145.png~~|155x104px~~]]</li><li>A VGA cable and a Micro HDMI male to HDMI female conversion ~~>~~ cable[[File:~~media/image146~~zero3-img146-1.png|~~148x133px~~300px]] [[File:~~media/image147~~zero3-img147.~~jpeg~~png|~~157x139px|IMG_6140(20220104-134930)~~300px]]</li>

<li>A monitor or TV that supports VGA interface</li></ol>

</li>

<li>HDMI to VGA display test as shown below

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

== WI-FI connection method ==

<li>First select '''Settings'''

[[File:~~media/image316~~zero3-img316.png~~|234x83px~~]]</li>

<li>Then select '''Network & Internet'''

[[File:~~media/image324~~zero3-img324.png~~|373x103px~~]]</li>

<li>Then open WI-FI

[[File:~~media/image325~~zero3-img325.png~~|381x50px~~]]</li>

<li>After turning on WI-FI, you can see the searched signal under '''Available networks'''

[[File:~~media/image326~~zero3-img326.png~~|381x187px~~]]</li>

<li>After selecting the WI-FI you want to connect to, the password input interface shown in the figure below will pop up

[[File:~~media/image327~~zero3-img327.png~~|386x180px|Screenshot_20220104-164114~~]]

</div></li>

<li>Then use the keyboard to enter the password corresponding to the WI-FI, and then use the '''mouse''' to click the Enter button in the virtual keyboard to start connecting to the WI-FI

[[File:~~media/image328~~zero3-img328.png~~|401x165px|图片1~~]]

</div></li>

<li>After the WI-FI connection is successful, the display is as shown in the figure below

[[File:~~media/image329~~zero3-img329.png~~|402x141px~~]]</li></ol>

== How to use WI-FI hotspot ==

<li>First, please make sure that the Ethernet port is connected to the network cable and can access the Internet normally</li>

<li>Then select '''Settings'''

[[File:~~media/image316~~zero3-img316.png~~|234x83px~~]]</li>

<li>Then select '''Network & Internet'''

[[File:~~media/image324~~zero3-img324.png~~|373x103px~~]]</li>

<li>Then select '''WIFI hotspot'''

[[File:~~media/image330~~zero3-img330.png~~|378x104px~~]]</li>

<li>Then turn on '''Hotspot Enable''', 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 '''Hotspot Enable''' first, before modifying)

[[File:~~media/image331~~zero3-img331.png~~|402x174px~~]]</li>

<li>At this point, you can take out your mobile phone. If everything is normal, you can find the WIFI hotspot with the same name '''(here AndroidAP_7132)''' displayed under the '''Hotspot name''' in the above picture in the WI-FI list searched by the mobile phone. Then you can click '''AndroidAP_7132''' to connect to the hotspot, and the password can be seen under the '''Hotspot password''' in the above picture

[[File:~~media/image332~~zero3-img332.png~~|269x191px~~]]</li>

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

[[File:~~media/image333~~zero3-img333.png~~|269x125px~~]]</li></ol>

<li>First, please make sure that the Gigabit Ethernet port of the development board is connected to a router or switch</li>

<li>Then open '''Settings'''

[[File:~~media/image334~~zero3-img334.png~~|431x161px~~]]</li>

<li>Then select '''Network & Internet'''

[[File:~~media/image335~~zero3-img335.png~~|576x186px~~]]</li>

<li>Then you can see the IP address of the development board's wired network port at the position shown in the figure below

[[File:~~media/image336~~zero3-img336.png~~|576x200px~~]]</li></ol>

<li>First select '''Settings'''

[[File:~~media/image316~~zero3-img316.png~~|234x83px~~]]</li>

<li>Then select '''Bluetooth'''

[[File:~~media/image337~~zero3-img337.png~~|377x111px~~]]</li>

<li>Then open '''Bluetooth Enable'''

[[File:~~media/image338~~zero3-img338.png~~|384x180px~~]]</li>

<li>Then click '''Pair new device''' to start scanning the surrounding Bluetooth devices

[[File:~~media/image339~~zero3-img339.png~~|389x129px~~]]</li>

<li>The searched Bluetooth devices will be displayed under '''Available devices'''

[[File:~~media/image340~~zero3-img340.png~~|407x181px~~]]</li>

<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

[[File:~~media/image341~~zero3-img341.png~~|420x115px~~]]</li><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[[File:~~media/image342~~zero3-img342.png~~|178x200px~~]]</li>

<li>After the pairing is complete, open '''Paired devices''' and you can see the paired Bluetooth devices

[[File:~~media/image343~~zero3-img343.png~~|430x136px~~]]</li>

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

[[File:~~media/image344~~zero3-img344.png~~|433x113px~~]]</li>

<li>The pictures received by the Android system Bluetooth of the development board can be viewed in '''Received files'''

[[File:~~media/image345~~zero3-img345.png~~|432x209px~~]]</li></ol>

== How to use the USB camera ==

<li>First insert the USB (UVC protocol) camera into the USB interface of the development board</li>

<li>If the USB camera is recognized normally, a corresponding video device node will be generated under /dev

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

|-

|

console:/ # '''ls /dev/video0'''

/dev/video0|}</li><li>Then make sure that the adb connection between the Ubuntu PC and the development board is normal. For how to use adb, please refer to the instructions in the section on [[Orange Pi Zero 3#How to use ADB|'''how to use ADB''']]</li>

<li>Download the USB camera test APP in the official tool on the development board data download page

[[File:~~media/image346~~zero3-img346.png~~|344x183px~~]][[File:~~media/image347~~zero3-img347.png~~|575x145px~~]]</li>

<li>Then use the adb command to install the USB camera test APP to the Android system, of course, you can also use the U disk to copy the installation

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''adb install usbcamera.apk'''|}</li>

<li>After installation, you can see the startup icon of the USB camera on the Android desktop

[[File:~~media/image348~~zero3-img348.png~~|576x132px~~]]</li>

<li>Then double-click to open the USB camera APP and you can see the output video of the USB camera</li></ol>

== Android system ROOT instructions ==

~~'''<span~~ {| class="~~mark~~wikitable"style="background-color:#ffffdc;width:800px;" |-| <big>'''The Android system released by Orange Pi has been ROOT, you can use the following method to test.'''</~~span~~big>~~'''~~|}

<li>Download '''rootcheck.apk''' from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Zero-3.html '''official tool'''] on the development board data download page[[File:~~media/image349~~zero3-img349.png|~~576x172px~~1200px]][[File:~~media/image350~~zero3-img350.png|~~575x124px~~1200px]]</li><li>Then make sure that the adb connection between the Ubuntu PC and the development board is normal. For how to use adb, please refer to the instructions in the section on [[Orange Pi Zero 3#How to use ADB|'''how to use ADB''']]</li>

<li>Then use the adb command to install rootcheck.apk to the Android system, of course, you can also use the U disk to copy the installation

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''adb install rootcheck.apk'''|}</li>

<li>After installation, you can see the startup icon of the ROOT test tool on the Android desktop

[[File:~~media/image351~~zero3-img351.png~~|575x119px~~]]</li>

<li>The display interface after opening the '''ROOT test tool''' for the first time is shown in the figure below

[[File:~~media/image352~~zero3-img352.png~~|575x162px~~]]</li>

<li>Then you can click '''CHECK NOW''' to start checking the ROOT status of the Android system. After the check, the display is as follows, and you can see that the Android system has obtained the ROOT permission

[[File:~~media/image353~~zero3-img353.png~~|575x161px~~]]</li></ol>

== The method of using MiracastReceiver to cast the mobile phone screen to the development board ==

<li>First, please make sure that the development board and the mobile phone are connected to the same WIFI hotspot. For the method of connecting the development board to WIFI, please refer to the description in the section of [[Orange Pi Zero 3#WI-FI connection method|'''WI-FI connection method''']]</li>

<li>Then open the '''MiracastReceiver''' application in the Android system of the development board

[[File:~~media/image354~~zero3-img354.png~~|576x124px~~]]</li>

<li>The interface after '''MiracastReceiver''' is opened is as follows

[[File:~~media/image355~~zero3-img355.png~~|420x236px|Screenshot_20230625-193535~~]]

</div></li>

<li>Then find the screen projection function in the mobile phone settings. '''Here we take the Mi 12S Pro mobile phone as an example'''. Please research other brands of mobile phones by yourself. As shown in the figure below, click the button in the red box to open the screen projection function of the mobile phone

[[File:~~media/image356~~zero3-img356-1.png~~|167x266px~~]]</li>

<li>After waiting for a while, you can see the searched and connectable devices on the mobile phone, and then we can select the device corresponding to the development board to connect

[[File:~~media/image357~~zero3-img357-1.png~~|146x308px~~]]</li>

<li>Then the selection box shown in the figure below will pop up on the '''MiracastReceiver''' application interface of the development board, here we can select '''Accept'''

[[File:~~media/image358~~zero3-img358.png~~|468x265px~~]]</li>

<li>Then you can see the content of the mobile phone screen on the HDMI screen connected to the development board

[[File:~~media/image359~~zero3-img359-1.png~~|576x352px~~]]</li></ol>

== 26pin interface GPIO, UART, SPI test ==

<li>First open the wiringOP APP on the desktop

[[File:~~media/image360~~zero3-img360.png~~|576x133px~~]]</li>

<li>Then click the '''GPIO_TEST''' button to open the GPIO test interface

[[File:~~media/image361~~zero3-img361.png~~|413x77px~~]]</li>

<li>The GPIO test interface is shown in the figure below. There is a one-to-one correspondence between the two rows of '''CheckBox''' buttons on the left and the 26pin pins '''(PC1/PI16/PI6/PH10 in the lower left corner are GPIO ports in the 13pin 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 the wPi number, GPIO mode, and pin level can be obtained.

[[File:~~media/image362~~zero3-img362.png~~|425x236px~~]]</li><li>Then click the '''GPIO READALL''' button, the output information is as shown in the figure ~~below：~~below:

[[File:~~media/image363~~zero3-img363.png~~|444x249px|Screenshot_20230609-155643~~]]

</div></li>

<li>There are a total of 17 GPIO ports in the 26pin of the development board that can be used '''(if you add 4 GPIO ports in the 13pin, then there are 21 in total)''', and the following pin No. 7 - corresponding to GPIO is PC9 - corresponding to wPi The 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

[[File:~~media/image364~~zero3-img364.png~~|432x210px~~]]</li>

<li>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is '''OUT''', and the pin level is high

[[File:~~media/image365~~zero3-img365.png~~|430x207px~~]]</li>

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

[[File:~~media/image366~~zero3-img366.png~~|434x212px~~]]</li>

<li>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is OUT, and the pin level is low

[[File:~~media/image367~~zero3-img367.png~~|438x217px~~]]</li></ol>

<li>'''UART5''' is enabled by default in Android, and the corresponding device node is '''/dev/ttyAS5'''

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

|-

|

apollo-p2:/ # '''ls /dev/ttyAS5'''

/dev/ttyAS5|}</li>

<li>First open the wiringOP APP on the desktop

[[File:~~media/image360~~zero3-img360.png~~|576x133px~~]]</li>

<li>Then click the '''UART_TEST''' button to open the UART test interface

[[File:~~media/image368~~zero3-img368.png~~|505x94px~~]]</li><li>The serial port test interface of wiringOP is shown in the figure below</li>~~</ol>~~ ~~[[File:media/image369.png|511x133px]]~~

[[File:zero3-img369.png]]

</ol>

<li>Then select the '''/dev/ttyAS5''' node in the selection box

[[File:~~media/image370~~zero3-img370.png~~|499x269px~~]]</li><li>Enter the baud rate you want to set in the edit box, and then click the '''OPEN''' button to open the '''/dev/ttyAS5''' node. After the opening is successful, the '''OPEN''' button becomes unselectable, and the '''CLOSE''' button and '''SEND''' button become selectable.</li>~~</ol>~~ ~~[[File:media/image371.png|334x107px]]~~

[[File:zero3-img371.png]]

</ol>

<li>Then use Dupont wire to short the rx and tx pins of uart5~~</li></ol>~~

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

|-

|

| style="text-align: ~~left~~center;"| uart5

|-

| Tx pin

| style="text-align: ~~left~~center;"| Corresponding to pin 8 of 26pin

|-

| Rx pin

| style="text-align: ~~left~~center;"| Corresponding to pin 10 of 26pin

|}

</li></ol>

<li>Then you can enter a character in the send edit box below, click the '''SEND''' button to start sending</li>~~</ol>~~ ~~[[File:media/image372.png|376x189px]]~~

[[File:zero3-img372.png]]

</ol>

<li>If everything is normal, the received string will be displayed in the receiving box</li~~></ol~~>

[[File:~~media/image373~~zero3-img373.png~~|382x196px~~]]</ol>

~~~~

=== 26pin SPI test method ===

<li>The SPI that can be used in 26pin is SPI1, and the corresponding device node is '''/dev/spidev1.1'''

[[File:~~media/image360~~zero3-img360.png~~|576x133px~~]]</li><li>Here is a demonstration to test the SPI1 interface through the '''w25q64''' module, first connect the w25q64 module to the SPI1 interface~~</li></ol>~~ '''It doesn’t matter if there is no w25q64 module, because there is a SPIFlash connected to SPI0 on the development board, and the configuration of SPI0 is also enabled by default in Android, so we can also directly use the onboard SPIFlash test.'''

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

|-

|

<big>'''It doesn't matter if there is no w25q64 module, because there is a SPIFlash connected to SPI0 on the development board, and the configuration of SPI0 is also enabled by default in Android, so we can also directly use the onboard SPIFlash test.'''</big>

|}

</li></ol>

<li>Then open the wiringOP APP on the desktop</li>

<li>Then click the '''SPI_TEST''' button to open the SPI test interface

[[File:~~media/image374~~zero3-img374.png~~|518x96px~~]]</li>

<li>Then select the spi device node in the upper left corner. If you directly test the onboard SPIFlash, then keep the default '''/dev/spidev0.0'''. If you connect the '''w25q64''' module to the 26pin spi1, then please select /dev '''/dev/spidev1.1'''

[[File:~~media/image375.jpeg|296x135px|C:\Users\orangepi\Desktop\用户手册插图\Zero3\未标题~~zero3-7img375.~~jpg未标题-7~~png]]

</div></li>

<li>Then click the '''OPEN''' button to initialize the SPI</li>~~</ol>~~ ~~[[File:media/image376.png|295x168px]]~~

[[File:zero3-img376.png]]

</ol>

<li>Then fill in the bytes that need to be sent, such as reading the ID information of the onboard SPIFlash, fill in the address 0x9f in data[0], and then click the '''TRANSFER''' button

[[File:~~media/image377~~zero3-img377.png~~|294x169px~~]]</li><li>Finally, the APP will display the read ID information of the onboard SPI Flash</li>~~</ol>~~ ~~[[File:media/image378.png|299x217px]]~~

[[File:zero3-img378.png]]

</ol>

<li>If it is to read the w25q64 module connected to 26pin SPI1, then the read ID information is shown in the figure below

[[File:~~media/image379~~zero3-img379.png~~|302x201px~~]]</li>

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

[[File:~~media/image380~~zero3-img380.png~~|336x113px~~]]</li></ol>

=== 26pin I2C test method ===

<li>The i2c3 in 26pin is enabled by default in Android, and the corresponding device node is '''/dev/i2c-3'''

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

|-

|

apollo-p2:/ # '''ls /dev/i2c-3'''

/dev/i2c-3|}</li>

<li>First open the wiringOP APP on the desktop

[[File:~~media/image360~~zero3-img360.png~~|576x133px~~]]</li>

<li>Then click the '''I2C_TEST''' button to open the i2c test interface

[[File:~~media/image381~~zero3-img381.png~~|506x110px~~]]</li><li>The i2c test interface of wiringOP is shown in the figure below. You can see that the default i2c is '''/dev/i2c-3''', so we ~~don’t~~ don't need to re-select</li>~~</ol>~~ ~~[[File:media/image382.png|353x159px]]~~

[[File:zero3-img382.png]]

</ol>

<li>Then connect an i2c device to the 26pin i2c3 pin, here we take the ds1307 rtc module as an example

[[File:~~media/image186~~zero3-img186.png~~|121x103px~~]]</li~~></ol~~>

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

|-

| style="text-align: ~~left~~center;"| '''Pins of the RTC module'''| style="text-align: ~~left~~center;"| '''The pin corresponding to the 26pin of the development board'''

|-

| style="text-align: ~~left~~center;"| '''5V'''| style="text-align: ~~left~~center;"| '''pin 2'''

|-

| style="text-align: ~~left~~center;"| '''GND'''| style="text-align: ~~left~~center;"| '''pin 6'''

|-

| style="text-align: ~~left~~center;"| '''SDA'''| style="text-align: ~~left~~center;"| '''pin 3'''

|-

| style="text-align: ~~left~~center;"| '''SCL'''| style="text-align: ~~left~~center;"| '''pin 5'''

|}

</ol>

<li>The i2c address of the ds1307 rtc module is 0x68. After connecting the wires, we can use the '''i2cdetect -y 3''' command in the serial port command line to check whether the i2c address of the ds1307 rtc module can be scanned. As shown in the figure below, if you can see the address 0x68, it means that the wiring of the ds1307 rtc module is correct.

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

|-

|

apollo-p2:/ # '''i2cdetect -y 3'''

|}[[File:~~media/image383~~zero3-img383.png~~|424x186px~~]]</li>

<li>Then set the address of i2c to 0x68 in wiringOP, and then click the '''OPEN''' button to open i2c3

[[File:~~media/image384~~zero3-img384.png~~|354x177px~~]]</li><li>The display after clicking the '''OPEN''' button to open i2c3 is as ~~follows：~~follows:[[File:~~media/image385~~zero3-img385.png~~|355x171px~~]]</li>

<li>Then we test to write a value into the register of the rtc module, for example, write 0x55 to the 0x1c address

<li>We first set the address of the register to be written to 0x1c

[[File:~~media/image386~~zero3-img386.png~~|322x152px~~]]</li>

<li>Then set the value to be written to 0x55

[[File:~~media/image387~~zero3-img387.png~~|315x177px~~]]</li>

<li>Then click the '''WRITE BYTE''' button to execute the write action

[[File:~~media/image388~~zero3-img388.png~~|314x173px~~]]</li></ol>

</li>

<li>Then click the '''READ BYTE''' button to read the value of the 0x1c register, if it is displayed as 0x55, it means that the i2c read and write test has passed

[[File:~~media/image389~~zero3-img389.png~~|316x170px~~]]</li></ol>

== User Manual Update History ==

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

|-

|-

|}

== Image update history ==

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

|-

| ~~* *~~'''Date**'''

| '''Update Notes'''

|-

| ~~202 3~~2023-07-05

| Orangepizero3_1.0.0_ubuntu_jammy_server_linux5.4.125.7z

Orangepizero3_1.0.0_debian_bullseye_server_linux5.4.125.7z

~~Ora ngepizero3_1~~Orangepizero3_1.0.0_ubuntu_focal_desktop_xfce_linux5.4.125.7z

~~Ora ngepizero3_1~~Orangepizero3_1.0.0_ubuntu_jammy_desktop_xfce_linux5.4.125.7z Orangepizero3_1.0.0_debian_bullseye_desktop_xfce_linux5.4.125.7z

~~Orange pizero3_1.0.0_debian_bullseye_desktop_xfce_linux5.4.125.7z~~

Orangepizero3_1.0.0_ubuntu_jammy_server_linux6.1.31.7z

Orangepizero3_1.0.0_debian_bullseye_server_linux6.1.31.7z

~~Or angepizero3_1~~Orangepizero3_1.0.0_ubuntu_jammy_desktop_xfce_linux6.1.31.7z

~~Orang epizero3_1~~Orangepizero3_1.0.0_debian_bookworm_desktop_xfce_linux6.1.31.7z Orangepizero3_1.0.0_debian_bullseye_desktop_xfce_linux6.1.31.7z

~~Orang epizero3_1.0.0_debian_bullseye_desktop_xfce_linux6.1.31.7z~~

OrangePi_Zero3_Android12_v1.0.tar.gz

*initial version

: *initial version

|-

| 2023-07-13

|

Opios-arch-aarch64-xfce-opizero3-23.07-linux6.1.31.img.xz

: *initial version

|}

Admin

Bureaucrats, Administrators

8,367

edits

Wiki-Orange Pi β

Changes

Orange Pi Zero 3

Wiki-Orange Pi ^β