Changes

Orange Pi Zero 2W

525 bytes removed, 15:01, 25 September 2023

no edit summary

[[File:~~media/image3~~zero2w-img3.png]]

</div>

[[File:~~media/image4~~zero2w-img4.png]]

</div>

[[File:~~media/image5~~zero2w-img5.png]]

</div>

[[File:~~media/image6~~zero2w-img6.png]]

</div>

[[File:~~media/image7~~zero2w-img7.png]]

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

<li>TF card, high-speed SanDisk card with minimum capacity of 8GB, class 10 or above

[[File:~~media/image8~~zero2w-img8.png]]

'''When using other brands of TF cards (non-SanDisk TF cards), as shown in the picture below (including but not limited to these cards), some friends have reported that problems will occur during system startup, such as the system getting stuck halfway through startup. Or the reboot command cannot be used normally, and it was finally solved after replacing the SanDisk TF card. Therefore, if you are using a non-SanDisk TF card and find problems with system startup or use, please replace it with a SanDisk TF card and then test again.'''

[[File:~~media/image9~~zero2w-img9.png]][[File:~~media/image10~~zero2w-img10.png]][[File:~~media/image11~~zero2w-img11.png]][[File:~~media/image12~~zero2w-img12.png]]

'''There are currently reports that some TF cards have problems booting on Orange Pi Zero 2w.'''

'''In addition, TF cards that can be used normally on other types of development boards are not guaranteed to be able to start normally on Orange Pi Zero 2w. Please pay special attention to this point.'''</li>

<li>TF card reader, used to read and write TF cards

[[File:~~media/image13~~zero2w-img13.png]]</li>

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

[[File:~~media/image14~~zero2w-img14.png]]

</div>

<li>Power supply. If you have a 5V/2A or 5V/3A power supply, you only need to prepare a USB to Type C interface data cable as shown in the picture on the left below. You can also use a cable similar to the picture on the right below. 5V/2A or 5V/3A high-quality USB Type C interface power adapter integrated with the power head.

[[File:~~media/image15~~zero2w-img15.png]] [[File:~~media/image16~~zero2w-img16.png]]

'''Both Type-C interfaces on the development board can be used for power supply.'''

[[File:~~media/image17~~zero2w-img17.png]]

</div></li>

<li>24pin expansion board

[[File:~~media/image18~~zero2w-img18.png]]</li>

<li>USB interface mouse and keyboard, as long as it is a standard USB interface mouse and keyboard, 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

[[File:~~media/image19~~zero2w-img19.png]]

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

<li>Network cable to connect the development board to the Internet</li>

<li>AV video cable. If you want to display video through the TV-OUT interface instead of the HDMI interface, you need to connect the development board to the TV through the AV video cable.

[[File:~~media/image20~~zero2w-img20.png]]</li>

<li>Heat sink. If you are worried that the temperature of the development board is too high, you can add some heat sinks and stick the heat sinks on the H618 chip and memory chip.

[[File:~~media/image21~~zero2w-img21.png]] [[File:~~media/image22~~zero2w-img22.png]]</li>

<li>5V cooling fan, as shown in the figure below. There are 5V and GND pins on the 40pin interface of the development board that can be connected to the cooling fan. The spacing of the 40pin pins is 2.54mm. The power interface of the cooling fan can be purchased according to this specification.

[[File:~~media/image23~~zero2w-img23.png]]

'''Note that the 5V pin can be used directly after the development board is plugged in and no other settings are required. In addition, the voltage output by the 5V pin cannot be adjusted or turned off through software.'''

'''The pin headers on the 40pin interface are not soldered by default, and you need to solder them yourself before you can use them.'''</li>

<li>Type-C to USB cable for connecting USB devices

[[File:~~media/image24~~zero2w-img24.png]]</li>

<li>USB to TTL module and Dupont cable. When using the serial port debugging function, a USB to TTL module and Dupont cable are needed to connect the development board and the computer.

[[File:~~media/image25~~zero2w-img25.png]] [[File:~~media/image26~~zero2w-img26.png]]

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

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

<li>After entering the balenaEtcher download page, click the green download button to jump to the software download location.

[[File:~~media/image27~~zero2w-img27.png]]</li>

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

[[File:~~media/image28~~zero2w-img28.png]]</li>

<li>If you downloaded the version of balenaEtcher that needs to be installed, please install it first and then use it. If you downloaded the Portable version of balenaEtcher, just double-click to open it. The balenaEtcher interface after opening is as shown below.

[[File:~~media/image29~~zero2w-img29.png]]</li></ol>

'''If the following error is prompted when opening balenaEtcher:'''

[[File:~~media/image30~~zero2w-img30.png]]

'''Please select balenaEtcher, right-click, and select Run as administrator.'''

[[File:~~media/image31~~zero2w-img31.png]]

[[File:~~media/image32~~zero2w-img32.png]]

</div></li>

<li>The interface displayed during the process of burning the Linux image by balenaEtcher is as shown in the figure below. In addition, the progress bar displays purple to indicate that the Linux image is being burned into the TF card.

[[File:~~media/image33~~zero2w-img33.png]]</li>

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

[[File:~~media/image34~~zero2w-img34.png]]</li>

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

[[File:~~media/image35~~zero2w-img35.png]]

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

[[File:~~media/image36~~zero2w-img36.png]]

</div></li>

<li>Then click "'''Format'''". A warning box will pop up before formatting. After selecting "'''Yes (Y)'''", formatting will begin.</li></ol>

[[File:~~media/image37~~zero2w-img37.png]]

<li>After formatting the TF card, the information shown in the picture below will pop up, click OK.

[[File:~~media/image38~~zero2w-img38.png]]</li></ol>

[[File:~~media/image39~~zero2w-img39.png]]

</div></li>

<li>After entering the balenaEtcher download page, click the green download button to jump to the software download place.

[[File:~~media/image27~~zero2w-img27.png]]</li>

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

[[File:~~media/image40~~zero2w-img40.png]]</li>

<li>Download the compressed package of the Linux operating system image file you want to burn from the [http://www.orangepi.org/html/serviceAndSupport/index.html '''Orange Pi information download page'''], and then use the decompression software to decompress it. In the decompressed file, 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:

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

orangepizero2w_1.0.0_ubuntu_focal_desktop_linux6.1.31.img: '''successful'''</li>

<li>Then double-click '''balenaEtcher-1.14.3-x64.AppImage''' on the graphical interface of Ubuntu PC to open balenaEtcher '''(no installation required)'''. The interface after balenaEtcher is opened is as shown below

[[File:~~media/image41~~zero2w-img41.png]]</li>

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

a. First select the path of the Linux image file to be burned.

[[File:~~media/image32~~zero2w-img32.png]]

</div></li>

<li>The interface displayed during the process of burning the Linux image by balenaEtcher is as shown in the figure below. In addition, the progress bar displays purple to indicate that the Linux image is being burned into the TF card.

[[File:~~media/image42~~zero2w-img42.png]]</li>

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

[[File:~~media/image43~~zero2w-img43.png]]</li>

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

[[File:~~media/image44~~zero2w-img44.png]]</li></ol>

<li>First, please make sure that '''Microsoft Visual C++ 2008 Redistrbutable - x86'''

is installed on your Windows system.

[[File:~~media/image45~~zero2w-img45.png]]</li>

<li>If '''Microsoft Visual C++ 2008 Redistrbutable - x86''' is not installed

, using '''PhoenixCard''' to format the TF card or burn the Android image will prompt the following error

[[File:~~media/image46~~zero2w-img46.png]]

</div></li>

<li>'''Microsoft Visual C++ 2008 Redistrbutable - x86''' installation package can be downloaded from the [http://www.orangepi.org/html/serviceAndSupport/index.html '''official tool'''] of Orange Pi Zero 2w, or you can download it from [https://www.microsoft.com/zh-cn/download/details.aspx?id=26368 '''Microsoft's official website''']

[[File:~~media/image47~~zero2w-img47.png]] [[File:~~media/image48~~zero2w-img48.png]]</li>

<li>Then prepare a TF card with 8GB or larger capacity. The transmission speed of the TF card must be class10 or above. It is recommended to use TF cards from SanDisk and other brands.</li>

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

[[File:~~media/image49~~zero2w-img49.png]]

</div></li>

<li>Then use decompression software to decompress the compressed package of the downloaded Android image. In the decompressed file, the file ending with "'''.img'''" is the Android image file, with a size of more than 1GB. If you ~~don’t~~ don't know how to decompress the Android image compressed package, you can install a '''360 compression software''' to decompress the image.[[File:~~media/image50~~zero2w-img50.png]]</li>

<li>Then use decompression software to decompress '''PhonixCard4.2.8.zip'''. This software does not need to be installed. Just find PhoenixCard in the decompressed folder and open it.

[[File:~~media/image51~~zero2w-img51.png]]</li>

<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 If there is no display, you can try to remove the TF card, or click the "'''Refresh Drive Letter'''" button in PhoenixCard.</li></ol>

[[File:~~media/image52~~zero2w-img52.png]]

[[File:~~media/image53~~zero2w-img53.png]]

</div>

b. Select "'''Start Card'''" in "'''Card Type'''"

c. Then click the "'''Burn Card'''" button to start burning.

[[File:~~media/image54~~zero2w-img54.png]]</li>

<li>After burning, the display of PhoenixCard is as shown below. At this time, click the "'''Close'''" button to exit PhoenixCard, and then you can pull out the TF card from the computer and insert it into the development board to start.

[[File:~~media/image55~~zero2w-img55.png]]

</div>

'''After burning the Android system, you can only see a 128 MB partition on the TF card in Windows. The displayed partition is as shown below (some computers may pop up more than twenty disk partitions, but they can only open the 128 MB one. partition), please note that this is normal, please do not think that the TF card is burned out. The reason for this is that there are more than twenty partitions in the Android system, but most of them cannot be recognized normally in the Windows system. At this time, please feel free to unplug the TF card and insert it into the development board to start.'''

[[File:~~media/image56~~zero2w-img56.png]]

'''After the Android system starts, you can use the following command to see the twenty partitions in the TF card:'''

[[File:~~media/image57~~zero2w-img57.png]]

'''Using the df -h command, you can see that after burning the Android system on the 16GB TF card, there is about 11 GB of space available (not all of the more than twenty partitions will be mounted to the Android system, focus on these to see to the partition you want to reach).'''

[[File:~~media/image58~~zero2w-img58.png]]</li></ol>

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

[[File:~~media/image59~~zero2w-img59.png]]

A micro Linux system is programmed into SPI Flash by default. This system is mainly used to prove that the development board can start normally. After getting the development board, there is no need to burn the system into the TF 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:

[[File:~~media/image17~~zero2w-img17.png]]

</div>

[[File:~~media/image60~~zero2w-img60.png]]

</div></li>

<li>The corresponding relationship between the GND, TX and RX pins of the debugging serial port of the development board is shown in the figure below

[[File:~~media/image61~~zero2w-img61.png]]

'''Note: The pin header on the 40pin interface is not soldered by default, and you need to solder it yourself before it can be used.'''</li>

<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 Dupont lines.

</li>

<li>The schematic diagram of connecting the USB to TTL module to the computer and Orange Pi development board is as shown below

[[File:~~media/image62~~zero2w-img62.png]]'''The TX and RX of the serial port need to be cross-connected. If you ~~don’t~~ don't want to carefully distinguish the order of TX and RX, you can casually connect the TX and RX of the serial port first. If there is no output from the test serial port, then exchange the order of TX and RX, so that the There is a right order.'''</li></ol>

test@test:~$ '''sudo putty'''</li>

<li>After executing the putty command, the following interface will pop up

[[File:~~media/image63~~zero2w-img63.png]]</li>

<li>First select the serial port setting interface

[[File:~~media/image64~~zero2w-img64.png]]

</div></li>

[[File:~~media/image65~~zero2w-img65.png]]

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

[[File:~~media/image66~~zero2w-img66.png]]

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

</li>

<li>Then start the development board, and you can see the Log information output by the system from the open serial terminal.

[[File:~~media/image67~~zero2w-img67.png]]</li></ol>

[https://mobaxterm.mobatek.net/ '''https://mobaxterm.mobatek.net/''']</li>

<li>Enter the MobaXterm download webpage and click '''GET XOBATERM > NOW!'''

[[File:~~media/image68~~zero2w-img68.png]]</li>

<li>Then choose to download the Home version

[[File:~~media/image69~~zero2w-img69.png]]</li>

<li>Then select the Portable version. There is no need to install it after downloading. You can open it directly and use it.

[[File:~~media/image70~~zero2w-img70.png]]

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

</li>

<li>After downloading, use decompression software to decompress the downloaded compressed package to get the executable software of MobaXterm, and then double-click to open it.

[[File:~~media/image71~~zero2w-img71.png]]</li>

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

a. Open the session settings interface

[[File:~~media/image72~~zero2w-img72.png]]

</div>

[[File:~~media/image73~~zero2w-img73.png]]

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

[[File:~~media/image74~~zero2w-img74.png]]

</div>

c. The black DuPont wire needs to be plugged into the GND pin of the 40pin interface

d. The positions of the 5V pin and GND pin of the 40pin interface in the development board are as shown in the figure below. '''Remember not to connect them reversely.'''

[[File:~~media/image23~~zero2w-img23.png]]</li></ol>

[[File:~~media/image75~~zero2w-img75.png]]

</div>

'''console=serial'''</li>

<li>As shown below, some commands that cannot be written in one line > will be placed on the next line. As long as the black and bold > parts are the commands that need to be entered. When these > commands are entered into one line, the "\" at the end of > each line needs to be removed. This is not part of the > command. In addition, different parts of the command have > spaces, please ~~don’t~~ don't miss them.

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

'''"deb [arch=$(dpkg --print-architecture) \'''

<li>The Linux system automatically logs in to the terminal by default. The default login user name is '''orangepi'''

[[File:~~media/image76~~zero2w-img76.png]]</li>

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

orangepi@orangepi:~$ '''sudo auto_login_cli.sh root'''</li>

[[File:~~media/image77~~zero2w-img77.png]]

</div></li>

[[File:~~media/image78~~zero2w-img78.png]]

</div>

orangepi@orangepi:~$ '''sudo desktop_login.sh root'''</li>

<li>Then restart the system and you will automatically log in to the desktop as the root user.

[[File:~~media/image79~~zero2w-img79.png]]

'''Note that if you use the root user to log in to the desktop system, you cannot use pulseaudio in the upper right corner to manage audio devices.'''

'''Also please note that this is not a bug, because pulseaudio is not allowed to run under the root user.'''</li>

orangepi@orangepi:~$ '''sudo orangepi-config'''</li>

<li>Then select '''System'''

[[File:~~media/image80~~zero2w-img80.png]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image81~~zero2w-img81.png]]</li>

<li>Then use the keyboard's arrow keys to locate the position shown > in the picture below, and then use the space to select > '''disable-leds'''

[[File:~~media/image82~~zero2w-img82.png]]</li>

<li>Then select '''<Save>'''to save

[[File:~~media/image83~~zero2w-img83.png]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image84~~zero2w-img84.png]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the > configuration take effect.

[[File:~~media/image85~~zero2w-img85.png]]</li>

<li>After restarting and entering the system, you can see that the > green LED light on the development board will no longer light > up.</li></ol>

</li></ol>

test@test:~$ '''sudo gparted'''</li>

<li>After opening gparted, you can select the TF card in the upper > right corner, and then you can see the usage of the TF card > capacity.

[[File:~~media/image86~~zero2w-img86.png]]</li>

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

</li>

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

[[File:~~media/image87~~zero2w-img87.png]]</li></ol>

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

test@test:~$ '''sudo gparted'''</li>

<li>After opening gparted, you can select the TF card in the upper right corner, and then you can see the usage of the TF card capacity. The picture below shows the situation of the TF card after burning the Linux desktop system. It can be seen that although the total capacity of the TF card is 16GB (displayed as 14.84GiB in GParted), the rootfs partition (/dev/sdc1) Only 4.05GiB is actually allocated, leaving 10.79GiB unallocated

[[File:~~media/image86~~zero2w-img86.png]]</li>

<li>Then select the rootfs partition (/dev/sdc1)

[[File:~~media/image88~~zero2w-img88.png]]</li>

<li>Right-click the mouse again to see the operation options shown in the picture below. If the TF card has been mounted, you first need to Umount the rootfs partition of the TF card.

[[File:~~media/image89~~zero2w-img89.png]]</li>

<li>Then select the rootfs partition again, right-click, and select '''Resize/Move''' to start expanding the size of the rootfs partition.

[[File:~~media/image90~~zero2w-img90.png]]</li>

<li>After the '''Resize/Move''' option is turned on, the following setting interface will pop up.

[[File:~~media/image91~~zero2w-img91.png]]</li>

<li>Then you can directly drag the position 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 size(MiB)'''

[[File:~~media/image92~~zero2w-img92.png]]</li>

<li>After setting the capacity, click '''Resize/Move''' in the lower right corner.

[[File:~~media/image93~~zero2w-img93.png]]</li>

<li>After final confirmation, click the green '''√''' shown in the picture below.

[[File:~~media/image94~~zero2w-img94.png]]</li>

<li>Then select '''Apply''', and the capacity expansion of the rootfs partition will officially begin.

[[File:~~media/image95~~zero2w-img95.png]]</li>

<li>After the expansion is completed, click '''Close''' to close it.

[[File:~~media/image96~~zero2w-img96.png]]</li>

<li>Then you can unplug the TF card and insert it into the development board to start. After entering the Linux system of the development board, if you use the '''df -h''' command to see that the size of the rootfs partition is consistent with the size set previously, it means manual Expansion successful

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

test@test:~$ '''sudo gparted'''</li>

<li>After opening gparted, you can select the TF card in the upper right corner, and then you can see the usage of the TF card capacity.

[[File:~~media/image97~~zero2w-img97.png]]</li>

<li>Then select the rootfs partition (/dev/sdc1)

[[File:~~media/image98~~zero2w-img98.png]]</li>

<li>Right-click the mouse again to see the operation options shown in the picture below. If the TF card is already mounted, you first need to Umount the rootfs partition of the TF card.

[[File:~~media/image99~~zero2w-img99.png]]</li>

<li>Then select the rootfs partition again, right-click the mouse, and select '''Resize/Move''' to start setting the size of the rootfs partition.

[[File:~~media/image100~~zero2w-img100.png]]</li>

<li>After the '''Resize/Move''' option is turned on, the following setting interface will pop up.

[[File:~~media/image101~~zero2w-img101.png]]</li>

<li>Then you can directly drag the position 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(MiB)'''

[[File:~~media/image92~~zero2w-img92.png]]</li>

<li>After setting the capacity, click '''Resize/Move''' in the lower right corner.

[[File:~~media/image93~~zero2w-img93.png]]</li>

<li>After final confirmation, click the green '''√''' as shown in the picture below.

[[File:~~media/image94~~zero2w-img94.png]]</li>

<li>Then select '''Apply''', and the capacity expansion of the rootfs partition will officially begin.

[[File:~~media/image95~~zero2w-img95.png]]</li>

<li>After the expansion is completed, click '''Close''' to close it.

[[File:~~media/image96~~zero2w-img96.png]]</li>

<li>Then you can unplug the TF card and insert it into the development board to start. After entering the Linux system of the development board, if you use the '''df -h''' command, you can see that the size of the rootfs partition is consistent with the size set previously, which means it has been reduced capacity success

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

[[File:~~media/image102~~zero2w-img102.png]]

</div></li>

<li>The schematic diagram of the 24pin expansion board interface of the development board is as follows

[[File:~~media/image103~~zero2w-img103.png]]</li>

<li>The way to connect the expansion board to the development board is as follows. Please pay attention to the forward and reverse directions of the cable and do not plug it in backwards.

[[File:~~media/image104~~zero2w-img104.png]]

</div></li>

[[File:~~media/image105~~zero2w-img105.png]]

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

<li>There are two LRADC buttons on the 24pin expansion board, and their locations are as shown in the figure below:

[[File:~~media/image106~~zero2w-img106.png]]</li>

<li>In the Linux system, the default key values of KEY1 and KEY2 are</li></ol>

<li>There is no wired network interface on the main board of the development board. We can expand the 100M wired network interface through a 24pin expansion board.

[[File:~~media/image107~~zero2w-img107.png]]</li>

<li>Then plug one end of the network cable into the Ethernet interface of the expansion board, and the other end of the network cable into the router, and make sure the network is smooth.</li>

<li>After the system starts, it will automatically assign an IP address to the Ethernet card through '''DHCP''', '''and no other configuration is required.'''</li>

[[File:~~media/image108~~zero2w-img108.png]]

</div></li>

orangepi@orangepi:~$ '''sudo nmtui'''</li>

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

[[File:~~media/image109~~zero2w-img109.png]]</li>

<li>Select '''Activate a connect''' and press Enter

[[File:~~media/image110~~zero2w-img110.png]]</li>

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

[[File:~~media/image111~~zero2w-img111.png]]

</div></li>

[[File:~~media/image112~~zero2w-img112.png]]

</div></li>

[[File:~~media/image113~~zero2w-img113.png]]

</div></li>

[[File:~~media/image114~~zero2w-img114.png]]

</div></li>

<li>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/image115~~zero2w-img115.png]]</li>

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

[[File:~~media/image116~~zero2w-img116.png]]</li>

<li>Then enter the password of the WIFI hotspot and click '''Connect''' to start connecting to WIFI

[[File:~~media/image117~~zero2w-img117.png]]</li>

<li>After connecting to WIFI, you can open the browser to check whether you can access the Internet. The browser entrance is as shown below

[[File:~~media/image118~~zero2w-img118.png]]</li>

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

[[File:~~media/image119~~zero2w-img119.png]]</li></ol>

[[File:~~media/image120~~zero2w-img120.png]]

</div></li>

[[File:~~media/image121~~zero2w-img121.png]]

</div></li>

[[File:~~media/image121~~zero2w-img121.png]]

</div>

[[File:~~media/image122~~zero2w-img122.png]]

</div></li>

[[File:~~media/image121~~zero2w-img121.png]]

</div>

[[File:~~media/image122~~zero2w-img122.png]]

</div>

[[File:~~media/image123~~zero2w-img123.png]]

</div>

[[File:~~media/image120~~zero2w-img120.png]]

</div></li>

[[File:~~media/image121~~zero2w-img121.png]]

</div></li>

[[File:~~media/image121~~zero2w-img121.png]]

</div>

[[File:~~media/image122~~zero2w-img122.png]]

</div></li>

[[File:~~media/image123~~zero2w-img123.png]]

</div>

orangepi@orangepi:~$ '''sudo nmtui'''</li>

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

[[File:~~media/image124~~zero2w-img124.png]]</li>

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

[[File:~~media/image125~~zero2w-img125.png]]</li>

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

[[File:~~media/image126~~zero2w-img126.png]]</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/image127~~zero2w-img127.png]]</li>

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

[[File:~~media/image128~~zero2w-img128.png]]</li>

<li>The display after selection is as shown below

[[File:~~media/image129~~zero2w-img129.png]]</li>

<li>Then move the cursor to '''<Show>''' via the Tab key

[[File:~~media/image130~~zero2w-img130.png]]</li>

<li>Then press Enter. After pressing Enter, the following setting interface will pop up.

[[File:~~media/image131~~zero2w-img131.png]]</li>

<li>Then you can set the IP address (Addresses), gateway (Gateway) and DNS server address as shown in the figure below (there are many other setting options, please explore by yourself), please set according to your specific needs. The values set in the image below are just an example

[[File:~~media/image132~~zero2w-img132.png]]</li>

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

[[File:~~media/image133~~zero2w-img133.png]]</li>

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

[[File:~~media/image134~~zero2w-img134.png]]</li>

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

[[File:~~media/image135~~zero2w-img135.png]]</li>

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

[[File:~~media/image136~~zero2w-img136.png]]</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 previously will take effect.

[[File:~~media/image137~~zero2w-img137.png]]</li>

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

[[File:~~media/image138~~zero2w-img138.png]] [[File:~~media/image139~~zero2w-img139.png]]</li>

<li>Then through '''ip a s eth0''' you can see that the IP address of the network port has become the static IP address set previously.

'''Note that in the following command, Debian12 needs to modify eth0 to end0.'''

<li>After successfully logging into the system, the display is as shown below

[[File:~~media/image140~~zero2w-img140.png]]

'''If ssh cannot log in to the Linux system normally, first check whether the IP address of the development board can be pinged. If there is no problem with pinging, you can log in to the Linux system through the serial port or HDMI display and enter the following command on the development board before trying again. Can it be connected?: '''</li></ol>

[[File:~~media/image141~~zero2w-img141.png]]

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

[[File:~~media/image142~~zero2w-img142.png]]

</div></li>

<li>After successfully logging into the system, the display is as shown below

[[File:~~media/image143~~zero2w-img143.png]]</li></ol>

[[File:~~media/image14~~zero2w-img14.png]]

</div></li>

<li>HDMI to VGA converter

[[File:~~media/image144~~zero2w-img144.png]]</li>

<li>A VGA cable and a Mini HDMI male to HDMI female adapter

[[File:~~media/image145~~zero2w-img145.png]] [[File:~~media/image146~~zero2w-img146.png]]</li>

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

</li>

<li>HDMI to VGA display test is as follows

[[File:~~media/image147~~zero2w-img147.png]]

'''When using HDMI to VGA display, the development board and the Linux system of the development board do not need to make any settings. You only need the Mini HDMI interface of the development board to 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.'''</li></ol>

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

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

[[File:~~media/image148~~zero2w-img148.png]]</li></ol>

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

[[File:~~media/image149~~zero2w-img149.png]]</li>

<li>Then select the adapter

[[File:~~media/image150~~zero2w-img150.png]]</li>

<li>If prompted with the following interface, please select '''Yes'''.

[[File:~~media/image151~~zero2w-img151.png]]</li>

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

[[File:~~media/image152~~zero2w-img152.png]]</li>

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

[[File:~~media/image153~~zero2w-img153.png]]</li>

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

[[File:~~media/image154~~zero2w-img154.png]]</li>

<li>Then select the Bluetooth device you want to connect, and then right-click the mouse to pop up the operation interface for the Bluetooth device. Select '''Pair''' to start pairing. The demonstration here is pairing with an Android phone.

[[File:~~media/image155~~zero2w-img155.png]]</li>

<li>When pairing, a pairing confirmation box will pop up in the upper right corner of the desktop. Just select '''Confirm''' to confirm. At this time, you also need to confirm on the mobile phone.

[[File:~~media/image156~~zero2w-img156.png]]</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/image157~~zero2w-img157.png]]</li>

<li>The interface for sending pictures is as follows

[[File:~~media/image158~~zero2w-img158.png]]</li></ol>

[[File:~~media/image159~~zero2w-img159.png]]

</div></li>

[[File:~~media/image159~~zero2w-img159.png]]

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

As shown in the figure below, there are only two Type-C USB2.0 interfaces on the main board of the development board, which cannot directly connect USB Type-A mice, keyboards and other USB devices.

[[File:~~media/image160~~zero2w-img160.png]]

If you only purchased the motherboard and not the 24pin expansion board, you can prepare a Type-C to USB cable as shown in the figure below, plug one end of the Type-C interface into the Type-C interface of the motherboard, and then plug the other end into You can connect USB devices such as mouse and keyboard. If you feel that one USB interface is not enough, you can also expand multiple USB interfaces through USB Hub.

[[File:~~media/image24~~zero2w-img24.png]]

If you purchase a 24pin expansion board, you do not need a Type-C to USB cable, because the 24pin expansion board can expand two USB2.0 interfaces.

[[File:~~media/image107~~zero2w-img107.png]]

As shown in the figure below, there are two Type-C interfaces on the main board of the development board: USB0 and USB1. Both of these interfaces can be used to power the development board, and they can also be used as USB2.0 HOST interfaces. The difference between USB0 and USB1 is that in addition to being set to HOST mode, USB0 can also be set to Device mode, while USB1 only has HOST mode

[[File:~~media/image160~~zero2w-img160.png]]

USB0 of the Linux system released by Orange Pi is set to Device mode by default, so when there is no need to use USB0 Device mode, it is recommended to use USB0 for power supply, so that USB1 can be used directly to connect USB devices

orangepi@orangepi:~$ '''sudo orangepi-config'''</li>

<li>Then select '''System'''

[[File:~~media/image80~~zero2w-img80.png]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image81~~zero2w-img81.png]]</li><li>Then use the ~~keyboard’s~~ keyboard's arrow keys to locate the location shown in > the picture below, and then use the space to select '''usb0-host'''[[File:~~media/image161~~zero2w-img161.png]]</li>

<li>Then select '''<Save>'''to save

[[File:~~media/image83~~zero2w-img83.png]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image84~~zero2w-img84.png]]</li>

<li>Then select '''<Reboot>'''to restart the system to make the > configuration take effect.

[[File:~~media/image85~~zero2w-img85.png]]</li>

<li>After restarting, USB0 can use USB devices such as mouse and > keyboard normally.</li></ol>

[[File:~~media/image162~~zero2w-img162.png]]

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

<li>There is no headphone interface on the main board of the development board. We can expand it through a 24pin expansion board.

[[File:~~media/image107~~zero2w-img107.png]]</li>

<li>Use the '''aplay -l''' command to view the sound card devices supported by the Linux system

<li>First open the file manager

[[File:~~media/image163~~zero2w-img163.png]]</li>

<li>Then find the following file (if there is no such audio file in the system, you can upload an audio file to the system yourself)

[[File:~~media/image164~~zero2w-img164.png]]

</div></li>

<li>Then select the audio.wav file, right-click and select open with vlc to start playing.

[[File:~~media/image165~~zero2w-img165.png]]</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/image166~~zero2w-img166.png]]</li>

<li>When playing audio, the audio device options that can be used by > the '''Playback''' software will be displayed in '''Playback''', > as shown in the figure below. Here you can set which audio > device needs to be played.

[[File:~~media/image167~~zero2w-img167.png]]

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

<li>There is no infrared receiver on the main board of the development board. We can expand it through a 24pin expansion board.

[[File:~~media/image107~~zero2w-img107.png]]</li>

<li>Install ir-keytable infrared test software</li></ol>

[[File:~~media/image168~~zero2w-img168.png]]

</div></li>

orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone2/temp'''

'''59273'''</li>

<li>sensor3: ~~VE’s~~ VE's 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.

orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone3/type'''

'''ve'''_thermal_zone

[[File:~~media/image169~~zero2w-img169.png]]

</div></li>

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

[[File:~~media/image170~~zero2w-img170.png]]

'''WiringOP currently mainly adapts to the functions of setting GPIO port input and output, setting GPIO port output high and low levels, and setting pull-up and pull-down resistors. Functions such as hardware PWM cannot be used.'''

orangepi@orangepi:~$ '''sudo apt install -y git'''

orangepi@orangepi:~$ '''git clone https://github.com/orangepi-xunlong/wiringOP.git -b next'''

'''Note that the source code needs to download the code of wiringOP next branch. Please ~~don’t~~ don't miss the -b next parameter.'''

'''If there is a problem downloading the code from GitHub, you can directly use the wiringOP source code that comes with the Linux image. The storage location is: /usr/src/wiringOP.'''</li>

<li>Compile and install wiringOP

orangepi@orangepi:~/wiringOP$ '''sudo ./build'''</li>

<li>The output of the test gpio readall command is as follows

[[File:~~media/image170~~zero2w-img170.png]]</li></ol>

<li>The following uses pin No. 7 - corresponding to GPIO PI13 - corresponding to wPi serial number 2 - as an example to demonstrate how to set the high and low levels of the GPIO port.

[[File:~~media/image171~~zero2w-img171.png]]</li>

<li>First set the GPIO port to output mode, and the third parameter needs to be the serial number of the wPi corresponding to the input pin.

root@orangepi:~/wiringOP# '''gpio mode 2 out'''</li>

<li>The following uses pin No. 7—corresponding to GPIO PI13—corresponding to wPi serial number 2—as an example to demonstrate how to set the pull-up and pull-down resistors of the GPIO port.

[[File:~~media/image171~~zero2w-img171.png]]</li>

<li>First, you need to set the GPIO port to input mode, and the third parameter needs to be the serial number of the wPi corresponding to the input pin.

root@orangepi:~/wiringOP# '''gpio mode 2 in'''</li>

orangepi@orangepi:~$ '''sudo orangepi-config'''</li>

<li>Then select '''System'''

[[File:~~media/image80~~zero2w-img80.png]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image81~~zero2w-img81.png]]</li>

<li>Then use the keyboard's arrow keys to locate the position shown > in the figure below, and then use the '''space''' to select the > dtbo configuration of the SPI you want to open.</li></ol>

</li></ol>

|}

[[File:~~media/image172~~zero2w-img172.png]]

<li>Then select '''<Save>''' to save

[[File:~~media/image83~~zero2w-img83.png]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image84~~zero2w-img84.png]]</li>

<li>Then select '''<Reboot>'''to restart the system to make the > configuration take effect.

[[File:~~media/image85~~zero2w-img85.png]]</li></ol>

orangepi@orangepi:~$ '''sudo orangepi-config'''</li>

<li>Then select '''System'''

[[File:~~media/image80~~zero2w-img80.png]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image81~~zero2w-img81.png]]</li><li>Then use the ~~keyboard’s~~ keyboard's arrow keys to locate the position shown > in the picture below, and then use the '''space''' to select the > corresponding i2c configuration in the picture below.</li></ol>

</li></ol>

|}

[[File:~~media/image173~~zero2w-img173.png]]

<li>Then select <Save> to save

[[File:~~media/image83~~zero2w-img83.png]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image84~~zero2w-img84.png]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the > configuration take effect.

[[File:~~media/image85~~zero2w-img85.png]]</li></ol>

[[File:~~media/image174~~zero2w-img174.png]]

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

orangepi@orangepi:~$ '''sudo orangepi-config'''</li>

<li>Then select '''System'''

[[File:~~media/image80~~zero2w-img80.png]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image81~~zero2w-img81.png]]</li><li>Then use the ~~keyboard’s~~ keyboard's arrow keys to locate the position shown > in the picture below, and then use the '''space''' to select the > serial port you want to open.</li></ol>

</li></ol>

|}

[[File:~~media/image175~~zero2w-img175.png]]

<li>Then select '''<Save>''' to save

[[File:~~media/image83~~zero2w-img83.png]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image84~~zero2w-img84.png]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the > configuration take effect.

[[File:~~media/image85~~zero2w-img85.png]]</li></ol>

orangepi@orangepi:~$ '''sudo orangepi-config'''</li>

<li>Then select '''System'''

[[File:~~media/image80~~zero2w-img80.png]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image81~~zero2w-img81.png]]</li>

<li>Then use the keyboard's arrow keys to locate the position shown > in the figure below, and then use the '''space''' to select the > configuration corresponding to the pwm you want to open.

[[File:~~media/image176~~zero2w-img176.png]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image83~~zero2w-img83.png]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image84~~zero2w-img84.png]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the > configuration take effect.

[[File:~~media/image85~~zero2w-img85.png]]</li></ol>

</li>

<li>After restarting, you can start the PWM test

[[File:~~media/image177~~zero2w-img177.png]]

</div>

'''Like wiringOP, wiringOP-Python can also determine which GPIO pin to operate by specifying the wPi number. Because there is no command to view the wPi number in wiringOP-Python, you can only view the board's wPi number and physics through the gpio command in wiringOP Correspondence of pins.'''

[[File:~~media/image170~~zero2w-img170.png]]

<li>The following uses pin No. 7 - corresponding to GPIO PI13 - corresponding to wPi serial number 2 - as an example to demonstrate how to set the high and low levels of the GPIO port.

[[File:~~media/image171~~zero2w-img171.png]]</li>

<li>The steps for testing directly with commands are as follows:

orangepi@orangepi:~$ '''sudo orangepi-config'''</li>

<li>Then select '''System'''

[[File:~~media/image80~~zero2w-img80.png]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image81~~zero2w-img81.png]]</li>

<li>Then use the keyboard's arrow keys to locate the position shown > in the figure below, and then use the '''space''' to select the > dtbo configuration of the SPI you want to open.</li></ol>

</li></ol>

<li>Then select '''<Save>''' to save

[[File:~~media/image83~~zero2w-img83.png]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image84~~zero2w-img84.png]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the > configuration take effect.

[[File:~~media/image85~~zero2w-img85.png]]</li></ol>

orangepi@orangepi:~$ '''sudo orangepi-config'''</li>

<li>Then select '''System'''

[[File:~~media/image80~~zero2w-img80.png]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image81~~zero2w-img81.png]]</li><li>Then use the ~~keyboard’s~~ keyboard's arrow keys to locate the position shown > in the picture below, and then use the '''space''' to select the > corresponding i2c configuration in the picture below.</li></ol>

</li></ol>

|}

[[File:~~media/image173~~zero2w-img173.png]]

<li>Then select <Save> to save

[[File:~~media/image83~~zero2w-img83.png]]</li>

<li>Then select <Back>

[[File:~~media/image84~~zero2w-img84.png]]</li>

<li>Then select <Reboot> to restart the system to make the > configuration take effect.

[[File:~~media/image85~~zero2w-img85.png]]</li></ol>

orangepi@orangepi:~$ '''sudo''' '''apt-get install -y i2c-tools'''</li>

<li>Then connect an i2c device to the i2c pin of the 40pin connector. Here we take the DS1307 RTC module as an example.

[[File:~~media/image178~~zero2w-img178.png]]</li>

<li>Then use the '''i2cdetect -y x'''command. If the address of the connected i2c device can be detected, it means that the i2c device is connected correctly.

'''Note that x in the i2cdetect -y x command needs to be replaced with the serial number of the device node corresponding to the i2c bus.'''</li></ol>

[[File:~~media/image179~~zero2w-img179.png]]

orangepi@orangepi:~$ '''sudo orangepi-config'''</li>

<li>Then select '''System'''

[[File:~~media/image80~~zero2w-img80.png]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image81~~zero2w-img81.png]]</li><li>Then use the ~~keyboard’s~~ keyboard's arrow keys to locate the position shown > in the picture below, and then use the '''space''' to select the > serial port you want to open.</li></ol>

</li></ol>

|}

[[File:~~media/image175~~zero2w-img175.png]]

<li>Then select '''<Save>''' to save

[[File:~~media/image83~~zero2w-img83.png]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image84~~zero2w-img84.png]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the > configuration take effect.

[[File:~~media/image85~~zero2w-img85.png]]</li></ol>

[[File:~~media/image180~~zero2w-img180.png]]

</div></li>

[[File:~~media/image181~~zero2w-img181.png]]

</div></li>

[[File:~~media/image182~~zero2w-img182.png]]

</div></li>

[[File:~~media/image183~~zero2w-img183.png]]

</div></li>

[[File:~~media/image184~~zero2w-img184.png]]

</div></li>

<li>The main interface finally displayed by Home Assistant is as shown below

[[File:~~media/image185~~zero2w-img185.png]]</li>

<li>Method to stop Home Assistant container

[[File:~~media/image180~~zero2w-img180.png]]

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

orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''</li>

<li>Then select '''zh_CN.UTF-8 UTF-8''' in the pop-up interface (use > the up and down keys on the keyboard to move up and down, use > the space bar to select, and finally use the Tab key to move > the cursor to '''<OK>''', and then return Car can be used)

[[File:~~media/image186~~zero2w-img186.png]]</li>

<li>Then set the default '''locale''' to '''zh_CN.UTF-8'''

[[File:~~media/image187~~zero2w-img187.png]]</li>

<li>After exiting the interface, the '''locale''' setting will begin. > The output displayed on the command line is as follows:

orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''

</li>

<li>Then open '''Input Method'''

[[File:~~media/image188~~zero2w-img188.png]]</li>

<li>Then select '''OK'''

[[File:~~media/image189~~zero2w-img189.png]]</li>

<li>Then select '''Yes'''

[[File:~~media/image190~~zero2w-img190.png]]</li>

<li>Then select '''fcitx'''

[[File:~~media/image191~~zero2w-img191.png]]</li>

<li>Then select '''OK'''

[[File:~~media/image192~~zero2w-img192.png]]</li>

<li>'''Then restart the Linux system to make the configuration take effect.'''</li>

<li>Then open '''Fcitx configuration'''

[[File:~~media/image193~~zero2w-img193.png]]</li>

<li>Then click the + sign as shown in the picture below

[[File:~~media/image194~~zero2w-img194.png]]</li>

<li>Then search '''Google Pinyin''' and click '''OK'''

[[File:~~media/image195~~zero2w-img195.png]]

</div></li>

<li>Then put '''Google Pinyin''' on top

[[File:~~media/image196~~zero2w-img196.png]][[File:~~media/image197~~zero2w-img197.png]]</li>

<li>Then open the '''Geany''' editor to test the Chinese input method

[[File:~~media/image198~~zero2w-img198.png]]</li>

<li>The Chinese input method test is as follows

[[File:~~media/image199~~zero2w-img199.png]]</li>

<li>You can switch between Chinese and English input methods through the '''Ctrl+Space''' shortcut key</li>

<li>If you need the entire system to be displayed in Chinese, you can set all variables in '''/etc/default/locale''' to '''zh_CN.UTF-8'''

LANGUAGE='''zh_CN.UTF-8'''</li>

<li>Then '''restart the system''' and you will see that the system is displayed in Chinese.

[[File:~~media/image200~~zero2w-img200.png]]</li></ol>

<li>First open '''Language Support'''

[[File:~~media/image201~~zero2w-img201.png]]</li>

<li>Then find the '''Chinese (China)''' option

[[File:~~media/image202~~zero2w-img202.png]]</li>

<li>Then please use the left button of the mouse to select '''Chinese (China)''' and hold it down, then drag it up to the starting position. After dragging, the display will be as shown below:

[[File:~~media/image203~~zero2w-img203.png]]</li></ol>

'''Note that this step is not easy to drag, please be patient and try it a few times.'''

<li>Then select '''Apply System-Wide''' to apply the Chinese settings to the entire system

[[File:~~media/image204~~zero2w-img204.png]]</li>

<li>Then set the '''Keyboard input method system''' system to '''fcitx'''

[[File:~~media/image205~~zero2w-img205.png]]</li>

<li>'''Then restart the Linux system to make the configuration take effect'''</li>

<li>After re-entering the system, please select '''Do not ask me again''' in the following interface, and then please decide according to your own preferences whether the standard folder should also be updated to Chinese

[[File:~~media/image206~~zero2w-img206.png]]</li>

<li>Then you can see that the desktop is displayed in Chinese

[[File:~~media/image207~~zero2w-img207.png]]</li>

<li>Then we can open '''Geany''' to test the Chinese input method. The opening method is as shown in the figure below

[[File:~~media/image208~~zero2w-img208.png]]</li>

<li>After opening '''Geany''', the English input method is still the default. We can switch to the Chinese input method through the '''Ctrl+Space''' shortcut key, and then we can input Chinese.

[[File:~~media/image209~~zero2w-img209.png]]</li></ol>

<li>First open '''Language Support'''

[[File:~~media/image201~~zero2w-img201.png]]</li>

<li>Then find the '''Chinese (China)''' option

[[File:~~media/image210~~zero2w-img210.png]]</li>

<li>Then please use the left button of the mouse to select '''Chinese (China)''' and hold it down, then drag it up to the starting position. After dragging, the display will be as shown below:

[[File:~~media/image211~~zero2w-img211.png]]</li></ol>

'''Note that this step is not easy to drag, please be patient and try it a few times.'''

<li>Then select '''Apply System-Wide''' to apply the Chinese settings to the entire system

[[File:~~media/image212~~zero2w-img212.png]]</li>

<li>'''Then restart the Linux system to make the configuration take effect'''</li>

<li>After re-entering the system, please select '''Do not ask me again''' in the following interface, and then please decide whether the standard folder should also be updated to Chinese according to your own preferences.

[[File:~~media/image206~~zero2w-img206.png]]</li>

<li>Then you can see that the desktop is displayed in Chinese

[[File:~~media/image207~~zero2w-img207.png]]</li>

<li>Then open the Fcitx5 configuration program

[[File:~~media/image213~~zero2w-img213.png]]</li>

<li>Then choose to use Pinyin input method

[[File:~~media/image214~~zero2w-img214.png]]

</div></li>

<li>The interface after selection is as shown below, then click OK

[[File:~~media/image215~~zero2w-img215.png]]</li>

<li>Then we can open '''Geany''' to test the Chinese input method. The opening method is as shown in the figure below

[[File:~~media/image208~~zero2w-img208.png]]</li>

<li>After opening '''Geany''', the English input method is still the default. We can switch to the Chinese input method through the '''Ctrl+Space''' shortcut key, and then we can enter Chinese.

[[File:~~media/image216~~zero2w-img216.png]]</li></ol>

'''https://knowledgebase.nomachine.com/DT10R00166'''

'''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 ~~NoMachine’s~~ NoMachine's official documentation.'''

'''Before operating, please make sure that the Windwos computer and the development board are in the same LAN, and that you can log in to the Ubuntu or Debian system of the development board through ssh normally.'''

[https://www.nomachine.com/download/download&id=112&s=ARM '''https://downloads.nomachine.com/download/?id=118&distro=ARM''']

[[File:~~media/image217~~zero2w-img217.png]]

<li>In addition, you can also download the '''NoMachine''' installation > package from the official tool.

[[File:~~media/image218~~zero2w-img218.png]]

First enter the '''remote login software-NoMachine''' folder

[[File:~~media/image219~~zero2w-img219.png]]

Then download the arm64 version of the deb installation package

[[File:~~media/image220~~zero2w-img220.png]]</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

'''https://downloads.nomachine.com/download/?id=9'''

[[File:~~media/image221~~zero2w-img221.png]]

<li>Then install NoMachine in Windows. '''Please restart your computer after installation.'''</li>

<li>Then open '''NoMachine''' in Window

[[File:~~media/image222~~zero2w-img222.png]]</li>

<li>After NoMachine is started, it will automatically scan other devices with NoMachine installed on the LAN. After entering the main interface of NoMachine, you can see that the development board is already in the list of connectable devices, and then click on the location shown in the red box in the picture below You can now log in to the Linux system desktop of the development board.

[[File:~~media/image223~~zero2w-img223.png]]</li>

<li>Then click '''OK'''

[[File:~~media/image224~~zero2w-img224.png]]</li>

<li>Then enter the username and password of the development board Linux system in the corresponding positions in the figure below, and then click OK to start logging in.

[[File:~~media/image225~~zero2w-img225.png]]</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/image226~~zero2w-img226.png]]</li></ol>

[[File:~~media/image227~~zero2w-img227.png]]

</div>

<li>Then enter the VNC password set earlier

[[File:~~media/image228~~zero2w-img228.png]]</li>

<li>After successful login, the interface is displayed as shown below, > and then you can remotely operate the desktop of the development > board Linux system.</li></ol>

[[File:~~media/image229~~zero2w-img229.png]]

</li>

<li>Then you can see the QT Creator startup icon in '''Applications'''

[[File:~~media/image230~~zero2w-img230.png]]

You can also use the following command to open QT Creator

orangepi@orangepi:~$ '''qtcreator'''</li>

<li>The interface after QT Creator is opened is as follows

[[File:~~media/image231~~zero2w-img231.png]]</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/image232~~zero2w-img232.png]]</li>

<li>The default version of QT Creator in '''Ubuntu22.04''' is as > follows

[[File:~~media/image233~~zero2w-img233.png]]</li>

<li>The default version of QT Creator in '''Debian11''' is as follows

[[File:~~media/image234~~zero2w-img234.png]]</li>

<li>The default version of QT Creator in '''Debian12''' is as follows

[[File:~~media/image235~~zero2w-img235.png]]</li></ol>

</li>

<li>Then set up QT

<li>First open '''Help'''->'''About Plugins...'''.

[[File:~~media/image236~~zero2w-img236.png]]</li>

<li>Then remove the check mark of '''ClangCodeModel'''

[[File:~~media/image237~~zero2w-img237.png]]</li>

<li>'''After setting up, you need to restart QT Creator'''</li>

<li>Then make sure the GCC compiler used by QT Creator. If the > default is Clang, please change it to GCC.

'''Debian12 please skip this step.'''

[[File:~~media/image238~~zero2w-img238.png]][[File:~~media/image239~~zero2w-img239.png]]</li></ol>

</li>

<li>Then you can open a sample code

[[File:~~media/image240~~zero2w-img240.png]]</li>

<li>After clicking on the sample code, the corresponding instruction document will automatically open. You can read the instructions carefully.

[[File:~~media/image241~~zero2w-img241.png]]</li>

<li>Then click '''Configure Project'''

[[File:~~media/image242~~zero2w-img242.png]]</li>

<li>Then click the green triangle in the lower left corner to compile and run the sample code

[[File:~~media/image243~~zero2w-img243.png]]</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/image244~~zero2w-img244.png]]</li>

<li>References

[https://wiki.qt.io/Install_Qt_5_on_Ubuntu '''https://wiki.qt.io/Install_Qt_5_on_Ubuntu''']

# The currently active version of ROS 1 is as follows, the recommended version is '''Noetic Ninjemys'''

[[File:~~media/image245~~zero2w-img245.png]]

[[File:~~media/image246~~zero2w-img246.png]]

[http://docs.ros.org/ '''http://docs.ros.org''']

<li>In the official installation documentation of ROS '''Noetic Ninjemys''', Ubuntu recommends using Ubuntu20.04, so please ensure that the system used by the development board is '''Ubuntu20.04 desktop system'''.

[http://wiki.ros.org/noetic/Installation '''http://wiki.ros.org/noetic/Installation''']

[[File:~~media/image247~~zero2w-img247.png]]</li>

<li>Then use the script below to install ros1

orangepi@orangepi:~$ '''install_ros.sh ros1'''</li>

orangepi@orangepi:~$ '''test_ros.sh'''</li>

<li>After running the '''test_ros.sh''' script, a small turtle as shown in the picture below will pop up.

[[File:~~media/image248~~zero2w-img248.png]]</li>

<li>Then please keep the terminal window you just opened at the top</li></ol>

[[File:~~media/image249~~zero2w-img249.png]]

</div>

<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/image250~~zero2w-img250.png]]</li></ol>

<li>The currently active version of ROS 2 is as follows, the recommended version is '''Galactic Geochelone'''

[[File:~~media/image251~~zero2w-img251.png]][[File:~~media/image252~~zero2w-img252.png]]

[http://docs.ros.org/ '''http://docs.ros.org''']

'''http://docs.ros.org/en/galactic/Releases.html'''</li>

orangepi@orangepi:~$ '''source /opt/ros/galactic/setup.bash'''

orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''

[[File:~~media/image253~~zero2w-img253.png]]</li>

<li>For how to use ROS, please refer to the documentation of ROS 2.

[http://docs.ros.org/en/galactic/Tutorials.html '''http://docs.ros.org/en/galactic/Tutorials.html''']</li></ol>

orangepi@orangepi:~$ '''source /opt/ros/humble/setup.bash'''

orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''

[[File:~~media/image254~~zero2w-img254.png]]</li>

<li>Reference documentation

'''http://docs.ros.org/en/humble/index.html'''

[[File:~~media/image255~~zero2w-img255.png]]

</div></li>

[[File:~~media/image256~~zero2w-img256.png]]

</div>

<li>Then choose to '''save the password''' and click '''OK'''

[[File:~~media/image257~~zero2w-img257.png]]</li>

<li>Then select '''Always trust this host''' and click '''OK'''</li></ol>

[[File:~~media/image258~~zero2w-img258.png]]

</div>

[[File:~~media/image259~~zero2w-img259.png]]

</div>

[[File:~~media/image260~~zero2w-img260.png]]

</div>

<li>After the upload is completed, you can go to the corresponding path in the development board Linux system to view the uploaded file.</li>

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

[https://filezilla-project.org/download.php?type=client '''https://filezilla-project.org/download.php?type=client''']

[[File:~~media/image261~~zero2w-img261.png]]

[[File:~~media/image262~~zero2w-img262.png]]

</div>

[[File:~~media/image263~~zero2w-img263.png]]

</div>

[[File:~~media/image264~~zero2w-img264.png]]

</div>

[[File:~~media/image256~~zero2w-img256.png]]

</div>

[[File:~~media/image265~~zero2w-img265.png]]

</div>

[[File:~~media/image266~~zero2w-img266.png]]

</div>

[[File:~~media/image267~~zero2w-img267.png]]

</div>

[[File:~~media/image268~~zero2w-img268.png]]

</div>

<li>After the upload is completed, you can go to the corresponding path in the development board Linux system to view the uploaded file.</li>

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

There is no power on/off button on the main board of the development board. We can expand it through a 24pin expansion board. The location of the power on/off button on the expansion board is as follows:

[[File:~~media/image269~~zero2w-img269.png]]

The power on/off button of the Linux 6.1 image is turned on by default, but the power on/off button of the Linux 5.4 kernel image is turned off by default and needs to be turned on manually for normal use. The steps are as follows:

orangepi@orangepi:~$ '''sudo orangepi-config'''</li>

<li>Then select '''System'''

[[File:~~media/image80~~zero2w-img80.png]]</li>

<li>Then select '''Hardware'''

[[File:~~media/image81~~zero2w-img81.png]]</li>

<li>Then use the keyboard's arrow keys to locate the position shown in the picture below, and then use the '''space''' to select the dtbo configuration of the SPI you want to open.

[[File:~~media/image270~~zero2w-img270.png]]</li>

<li>Then select '''<Save>''' to save

[[File:~~media/image83~~zero2w-img83.png]]</li>

<li>Then select '''<Back>'''

[[File:~~media/image84~~zero2w-img84.png]]</li>

<li>Then select '''<Reboot>''' to restart the system to make the configuration take effect.

[[File:~~media/image85~~zero2w-img85.png]]</li></ol>

'''Note that after turning off the development board, you need to unplug and replug the power supply before it can be turned on.'''</li>

<li>In addition to using the poweroff command to shut down, you can also use the power on/off button on the expansion board to shut down.

[[File:~~media/image269~~zero2w-img269.png]]

'''Note that Linux 5.4 requires manual configuration of the power on/off button before it can be used. For the opening method, please refer to the method of opening the power button in Linux5.4.'''</li>

<li>Use the '''reboot''' command to restart the Linux system in the development board

<li>Note that the Ubuntu version needs to be switched to 22.04.</li></ol>

[[File:~~media/image271~~zero2w-img271.png]]

[[File:~~media/image272~~zero2w-img272.png]]

</div>

[[File:~~media/image273~~zero2w-img273.png]]

</div>

[[File:~~media/image274~~zero2w-img274.png]]

</div>

<li>Then select the model of the development board</li></ol>

[[File:~~media/image275~~zero2w-img275.png]]

<li>The current branch will compile the u-boot v2018.05 version code that needs to be used by the linux5.4 image.</li>

<li>The next branch will compile the u-boot v2021.07 version code that needs to be used by the linux6.1 image.

[[File:~~media/image276~~zero2w-img276.png]]</li></ol>

</li>

<li>If you select the next branch, you will also be prompted to select the memory size, and you do not need to select the current branch.</li></ol>

b. If the development board you purchased has 1GB or 2GB or 4GB memory size, please choose the second option.

</blockquote>

[[File:~~media/image277~~zero2w-img277.png]]

<li>Then select '''5 Install/Update the bootloader on SD/eMMC'''</li></ol>

[[File:~~media/image278~~zero2w-img278.png]]

<li>After pressing the Enter key, a Warning will pop up first.</li></ol>

[[File:~~media/image279~~zero2w-img279.png]]

<li>Press the Enter key again to start updating u-boot. After the update is completed, the following information will be displayed.</li></ol>

[[File:~~media/image280~~zero2w-img280.png]]

[[File:~~media/image281~~zero2w-img281.png]]

</div>

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

[[File:~~media/image282~~zero2w-img282.png]]

<li>Then select the model of the development board</li></ol>

[[File:~~media/image275~~zero2w-img275.png]]

b. The next branch will compile the linux6.1 kernel source code

</blockquote>

[[File:~~media/image276~~zero2w-img276.png]]

<li>If you choose to display the kernel configuration menu (the second option) in step 3), the kernel configuration interface opened through '''make menuconfig''' will pop up. At this time, you can directly modify the kernel configuration. After modification, save and exit. Yes, compilation of the kernel source code will begin after exiting.</li></ol>

[[File:~~media/image283~~zero2w-img283.png]]

<li>If the following error is prompted when compiling the kernel, it is because the Ubuntu PC terminal interface is too small, causing the make menuconfig interface to be unable to be displayed. Please increase the Ubuntu PC terminal to the maximum size, and then rerun the build.sh script.</li></ol>

[[File:~~media/image284~~zero2w-img284.png]]

[[File:~~media/image285~~zero2w-img285.png]]

</div>

<li>Then select the model of the development board</li></ol>

[[File:~~media/image275~~zero2w-img275.png]]

</li></ol>

[[File:~~media/image276~~zero2w-img276.png]]

<li>Then select the type of rootfs</li></ol>

[[File:~~media/image286~~zero2w-img286.png]]

[[File:~~media/image287~~zero2w-img287.png]]

</div>

[[File:~~media/image288~~zero2w-img288.png]]

</div>

<li>If you are compiling a desktop version of the image, you also need to select the type of desktop environment. Currently, only XFCE is maintained, so please select an XFCE type desktop.</li></ol>

[[File:~~media/image289~~zero2w-img289.png]]

[[File:~~media/image290~~zero2w-img290.png]]

You can then select additional packages that need to be installed. Please press the Enter key here to skip directly.

[[File:~~media/image291~~zero2w-img291.png]]

[[File:~~media/image292~~zero2w-img292.png]]

</div>

<li>Then select the model of the development board</li></ol>

[[File:~~media/image275~~zero2w-img275.png]]

</li></ol>

[[File:~~media/image276~~zero2w-img276.png]]

<li>If the development board you purchased has a memory size of 1.5GB, please select the first option.</li>

<li>If the development board you purchased has 1GB or 2GB or 4GB memory size, please choose the second option.

[[File:~~media/image277~~zero2w-img277.png]]</li></ol>

</li>

<li>Then select the type of rootfs</li></ol>

[[File:~~media/image286~~zero2w-img286.png]]

[[File:~~media/image287~~zero2w-img287.png]]

</div>

[[File:~~media/image288~~zero2w-img288.png]]

</div>

<li>If you are compiling a desktop version of the image, you also need to select the type of desktop environment. Currently, only XFCE is maintained, so please select an XFCE type desktop.</li></ol>

[[File:~~media/image289~~zero2w-img289.png]]

[[File:~~media/image290~~zero2w-img290.png]]

You can then select additional packages that need to be installed. Please press the Enter key here to skip directly.

[[File:~~media/image291~~zero2w-img291.png]]

[[File:~~media/image293~~zero2w-img293.png]]

</div></li>

[[File:~~media/image294~~zero2w-img294.png]]

</div></li>

[[File:~~media/image295~~zero2w-img295.png]]

</div></li>

[[File:~~media/image296~~zero2w-img296.png]]

</div></li>

[[File:~~media/image297~~zero2w-img297.png]]

</div></li>

[[File:~~media/image298~~zero2w-img298.png]]

</div></li>

[[File:~~media/image299~~zero2w-img299.png]]

</div></li>

[[File:~~media/image300~~zero2w-img300.png]]

</div></li>

[[File:~~media/image301~~zero2w-img301.png]]

</div></li>

[[File:~~media/image302~~zero2w-img302.png]]

</div>

If you have purchased the infrared remote control (other remote controls do not work) and a 24pin expansion board that come with the development board, after connecting the 24pin expansion board to the development board, you can also use the return key on the remote control to return to the previous menu. The location of the return key is as shown below. Shown:

[[File:~~media/image303~~zero2w-img303.png]]

# Prepare a USB Type C interface data cable, plug one end of the USB interface into the USB interface of the computer, and plug one end of the USB Type C interface into the USB0 interface of the development board (see the description of the picture on the right below for the location of USB0). In this case, the development board is powered by the computer's USB interface, so please ensure that the computer's USB interface can provide the most sufficient power to drive the development board.

[[File:~~media/image304~~zero2w-img304.png]] [[File:~~media/image305~~zero2w-img305.png]]

<li>Enter first '''Settings'''

[[File:~~media/image306~~zero2w-img306.png]]</li>

<li>Then select '''Device Preferences'''

[[File:~~media/image307~~zero2w-img307.png]]</li>

<li>Then select '''Display & Sound'''

[[File:~~media/image308~~zero2w-img308.png]]</li>

<li>Then select '''Advanced display settings'''

[[File:~~media/image309~~zero2w-img309.png]]</li>

<li>Then select '''HDMI output mode'''

[[File:~~media/image310~~zero2w-img310.png]]</li>

<li>Then you can see the list of resolutions supported by the monitor. At this time, clicking the corresponding option will switch to the corresponding resolution. Please note that different monitors may support different resolutions. If you connect it to a TV, you will generally see more resolution options than the picture below.

[[File:~~media/image311~~zero2w-img311.png]]</li>

<li>The HDMI output of the development board supports 4K display. When connected to a 4K TV, you can see the 4K resolution option.

[[File:~~media/image312~~zero2w-img312.png]]</li></ol>

</li></ol>

[[File:~~media/image144~~zero2w-img144.png]]

<li>A VGA cable and a Mini HDMI male to HDMI female adapter</li></ol>

[[File:~~media/image145~~zero2w-img145.png]] [[File:~~media/image146~~zero2w-img146.png]]

<li>HDMI to VGA display test is as follows</li></ol>

[[File:~~media/image313~~zero2w-img313.png]]

'''When using HDMI to VGA display, the development board and the Android system of the development board do not need to make any settings. You only need the Mini HDMI interface of the development board to 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.'''

# Choose first '''Settings'''

[[File:~~media/image306~~zero2w-img306.png]]

<li>Then select '''Network & Internet'''</li></ol>

[[File:~~media/image314~~zero2w-img314.png]]

[[File:~~media/image315~~zero2w-img315.png]]

<li>After turning on WI-FI, you can see the searched signals under '''Available networks'''.</li></ol>

[[File:~~media/image316~~zero2w-img316.png]]

[[File:~~media/image317~~zero2w-img317.png]]

</div>

[[File:~~media/image318~~zero2w-img318.png]]

</div>

<li>The display after successful WI-FI connection is as shown below</li></ol>

[[File:~~media/image319~~zero2w-img319.png]]

# Then select '''Settings'''

[[File:~~media/image306~~zero2w-img306.png]]

<li>Then select '''Network & Internet'''</li></ol>

[[File:~~media/image314~~zero2w-img314.png]]

<li>Then select '''WIFI hotspot'''</li></ol>

[[File:~~media/image320~~zero2w-img320.png]]

<li>Then open '''Hotspot Enable'''. You can also see the name and password of the generated hotspot in the picture 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 close Hotspot Enable first. Then you can modify it)</li></ol>

[[File:~~media/image321~~zero2w-img321.png]]

<li>At this time, you can take out your mobile phone. If everything is normal, you can find the WIFI hotspot with the same name ('''here AndroidAP_7132''') shown under the '''Hotspot name''' in the picture above in the WI-FI list searched by the mobile phone. Then you can click AndroidAP_7132 to connect to the hotspot. The password can be seen under the '''Hotspot password''' in the picture above.</li></ol>

[[File:~~media/image322~~zero2w-img322.png]]

<li>After the connection is successful, it will be displayed as shown below (the interface will be different on different mobile phones, the specific interface is subject to the one displayed on your mobile phone). At this time, you can open a web page on your mobile phone to see if you can access the Internet. If the web page can be opened normally, it means that the '''WI-FI Hotspot''' of the development board can be used normally.</li></ol>

[[File:~~media/image323~~zero2w-img323.png]]

# There is no wired network interface on the main board of the development board. We can expand the 100M Ethernet through a 24pin expansion board.

[[File:~~media/image107~~zero2w-img107.png]]

<li>Then make sure the network port of the expansion board is connected to the router or switch</li>

<li>Then open '''Settings'''

[[File:~~media/image324~~zero2w-img324.png]]</li>

<li>Then select '''Network & Internet'''

[[File:~~media/image325~~zero2w-img325.png]]</li><li>Then you can see the IP address of the development ~~board’s~~ board's wired network port at the location shown in the picture below.[[File:~~media/image326~~zero2w-img326.png]]</li></ol>

# Choose first '''Settings'''

[[File:~~media/image306~~zero2w-img306.png]]

<li>Then select '''Bluetooth'''</li></ol>

[[File:~~media/image327~~zero2w-img327.png]]

<li>Then Open '''Bluetooth Enable'''</li></ol>

[[File:~~media/image328~~zero2w-img328.png]]

<li>Then click '''Pair new device'''to start scanning for surrounding Bluetooth devices</li></ol>

[[File:~~media/image329~~zero2w-img329.png]]

<li>The searched Bluetooth devices will be displayed under '''Available devices'''</li></ol>

[[File:~~media/image330~~zero2w-img330.png]]

<li>Then click on the Bluetooth device you want to connect to start pairing. When the following interface pops up, please use the mouse to select the '''Pair'''option</li></ol>

[[File:~~media/image331~~zero2w-img331.png]]

<li>What is tested here is the Bluetooth configuration process between the development board and the Android phone. At this time, the following confirmation interface will pop up on the phone. Click the pairing button on the phone to start the pairing process.</li></ol>

[[File:~~media/image332~~zero2w-img332.png]]

<li>After pairing is completed, open '''Paired devices''' and you will see the paired Bluetooth devices.</li></ol>

[[File:~~media/image333~~zero2w-img333.png]]

<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 pictures sent by the mobile phone.</li></ol>

[[File:~~media/image334~~zero2w-img334.png]]

<li>Pictures received by the Bluetooth system of the development board Android system can be viewed in '''Received files'''.</li></ol>

[[File:~~media/image335~~zero2w-img335.png]]

As shown in the figure below, there are two Type-C interfaces on the motherboard of the development board: USB0 and USB1. Both of these interfaces can be used to power the development board, and they can also be used as USB2.0 HOST interfaces. The difference between USB0 and USB1 is that in addition to being set to HOST mode, USB0 can also be set to Device mode, while USB1 only has HOST mode.

[[File:~~media/image160~~zero2w-img160.png]]

USB0 of the Android12 TV system released by Orange Pi is set to Device mode by default, so when there is no need to use USB0 Device mode (ADB function needs to ensure that USB0 is in Device mode), it is recommended to use USB0 for power supply, so that USB1 can be directly used to connect USB devices .

[[File:~~media/image336~~zero2w-img336.png]]

</div>

[[File:~~media/image337~~zero2w-img337.png]]

</div>

<li>After installation, you can see the startup icon of the USB camera on the Android desktop.</li></ol>

[[File:~~media/image338~~zero2w-img338.png]]

[[File:~~media/image336~~zero2w-img336.png]]

</div>

[[File:~~media/image339~~zero2w-img339.png]]

</div>

<li>After installation, you can see the startup icon of the ROOT test tool on the Android desktop.</li></ol>

[[File:~~media/image340~~zero2w-img340.png]]

<li>The display interface after opening the '''ROOT test tool''' for the first time is as shown below</li></ol>

[[File:~~media/image341~~zero2w-img341.png]]

<li>Then you can click '''CHECK NOW''' to start checking the ROOT status of the Android system. After the check is completed, the display is as follows. You can see that the Android system has obtained ROOT permissions.</li></ol>

[[File:~~media/image342~~zero2w-img342.png]]

<li>First, please make sure that both 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 instructions in the WI-FI connection method.'''</li>

<li>Then open the '''MiracastReceiver'''application in the Android system of the development board

[[File:~~media/image343~~zero2w-img343.png]]</li>

<li>The interface after '''MiracastReceiver''' is opened is as follows

[[File:~~media/image344~~zero2w-img344.png]]

</div></li>

<li>Then find the screen mirroring function in the phone settings. Here we take '''Xiaomi 12S Pro mobile phone''' as an example. Please research other brands of mobile phones by yourself. As shown in the picture below, click the button in the red box to open the screen mirroring function of the phone.

[[File:~~media/image345~~zero2w-img345.png]]</li>

<li>After waiting for a period of time, you will be able to see the searched connectable devices on your mobile phone, and then we can select the device corresponding to the development board to connect.

[[File:~~media/image346~~zero2w-img346.png]]</li>

<li>Then the selection box shown in the figure below will pop up in the '''MiracastReceiver''' application interface of the development board. Here we can select '''Accept'''

[[File:~~media/image347~~zero2w-img347.png]]</li>

<li>Then you can see the content of the mobile phone screen on the HDMI screen connected to the development board

[[File:~~media/image348~~zero2w-img348.png]]</li></ol>

We can turn off or turn on the Android system of the development board through the power on/off button or infrared remote control. However, it should be noted that there is no power on/off button and infrared receiver on the main board of the development board, and it needs to be expanded through a 24pin expansion board.

[[File:~~media/image107~~zero2w-img107.png]]

The location of the power button on the 24pin expansion board is as shown in the figure below:

[[File:~~media/image269~~zero2w-img269.png]]

The location of the infrared remote control power button is as follows:

[[File:~~media/image349~~zero2w-img349.png]]

When shutting down, we need to press and hold the power button or the power button on the infrared remote control, and then the Android system will pop up the confirmation dialog box shown in the figure below, and then select '''OK''' to shut down the Android system.

[[File:~~media/image350~~zero2w-img350.png]]

After shutting down, press and hold the power button or the power button on the infrared remote control again to turn it on.

# First open wiringOP APP on the desktop

[[File:~~media/image351~~zero2w-img351.png]]

<li>Then click the '''GPIO_TEST''' button to open the GPIO test interface</li></ol>

[[File:~~media/image352~~zero2w-img352.png]]

<li>The GPIO test interface is as shown in the figure below. The two rows of '''CheckBox''' buttons on the left have a one-to-one correspondence with the 40pin pins. When the '''CheckBox''' button is checked, the corresponding GPIO pin will be set to '''OUT''' mode and the pin level is set to high level; when unchecked, the GPIO pin level will be set to low level; when the GPIO is clicked When you click the '''GPIO READALL''' button, you can get information such as wPi number, GPIO mode, pin level, etc.; when you click the'''BLINK ALL GPIO''' button, all GPIO ports will cycle through outputting high and low levels. This function can be used to test all the 40pin pins. GPIO port.</li></ol>

[[File:~~media/image353~~zero2w-img353.png]]

[[File:~~media/image354~~zero2w-img354.png]]

</div>

<li>There are a total of 28 GPIO ports available in the 40-pin development board. The following takes pin 12 - corresponding to GPIO PI01 - corresponding to wPi serial number 6 - 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 12. When the button is selected, pin 12 will be set to high level. After setting, you can use a multimeter to measure the value of the voltage of the pin. If it is '''3.3v''', it means the setting High level success.</li></ol>

[[File:~~media/image355~~zero2w-img355.png]]

<li>Then click the '''GPIO READALL''' button and you can see that the current pin 12 mode is '''OUT''' and the pin level is high level.</li></ol>

[[File:~~media/image356~~zero2w-img356.png]]

<li>Click the '''CheckBox''' button in the picture below again to uncheck it, and pin 12 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 the low level setting is successful.</li></ol>

[[File:~~media/image357~~zero2w-img357.png]]

<li>Then click the '''GPIO READALL''' button and you can see that the current pin 12 mode is OUT and the pin level is low level.</li></ol>

[[File:~~media/image358~~zero2w-img358.png]]

<li>First open wiringOP APP on the desktop</li></ol>

[[File:~~media/image351~~zero2w-img351.png]]

<li>Then click the '''UART_TEST'''button to open the UART test interface</li></ol>

[[File:~~media/image359~~zero2w-img359.png]]

<li>The serial port test interface of wiringOP is as shown in the figure below</li></ol>

[[File:~~media/image360~~zero2w-img360.png]]

<li>Then select the '''/dev/ttyAS2''' or'''/dev/ttyAS5''' node in the selection box

[[File:~~media/image361~~zero2w-img361.png]]</li>

<li>Enter the baud rate you want to set in the edit box, and then click the '''OPEN''' button to open the uart node. After the opening is successful, the '''OPEN''' button becomes unselectable, and the '''CLOSE''' button and '''SEND''' button become selectable.</li></ol>

[[File:~~media/image362~~zero2w-img362.png]]

<li>Then you can enter a paragraph of characters in the send edit box below and click the '''SEND''' button to start sending.</li></ol>

[[File:~~media/image363~~zero2w-img363.png]]

<li>If everything is normal, the received string will be displayed in the receiving box</li></ol>

[[File:~~media/image364~~zero2w-img364.png]]

<li>Then open wiringOP APP on the desktop</li></ol>

[[File:~~media/image351~~zero2w-img351.png]]

<li>Then click the '''SPI_TEST''' button to open the SPI test interface</li></ol>

[[File:~~media/image365~~zero2w-img365.png]]

[[File:~~media/image366~~zero2w-img366.png]]

</div></li>

<li>Then click the '''OPEN''' button to initialize the SPI</li></ol>

[[File:~~media/image367~~zero2w-img367.png]]

<li>Then fill in the bytes that need to be sent, such as reading the ID information of the onboard SPIFlash, filling in the address 0x9f in data[0], and then click the '''TRANSFER''' button</li></ol>

[[File:~~media/image368~~zero2w-img368.png]]

<li>Finally, the APP will display the read ID information of the onboard SPI Flash.</li></ol>

[[File:~~media/image369~~zero2w-img369.png]]

<li>First open wiringOP APP on the desktop</li></ol>

[[File:~~media/image351~~zero2w-img351.png]]

<li>Then click the '''I2C_TEST''' button to open the i2c test interface</li></ol>

[[File:~~media/image370~~zero2w-img370.png]]

<li>The i2c test interface of wiringOP is shown in the figure below</li></ol>

[[File:~~media/image371~~zero2w-img371.png]]

<li>Then click the device node selection box in the upper left corner to select the i2c you want to test</li></ol>

[[File:~~media/image372~~zero2w-img372.png]]

<li>Then connect an i2c device to the 40pin i2c pin. Here we take the ds1307 rtc module as an example.</li></ol>

[[File:~~media/image178~~zero2w-img178.png]]

'''Or'''

apollo-p2:/ # '''i2cdetect -y 2'''

[[File:~~media/image373~~zero2w-img373.png]]</li>

<li>Then set the i2c address to 0x68 in wiringOP, and then click the '''OPEN''' button to open i2c

[[File:~~media/image374~~zero2w-img374.png]]</li>

<li>After clicking the '''OPEN''' button to open i2c, the display is as follows

[[File:~~media/image375~~zero2w-img375.png]]</li>

<li>Then we test writing a value to the register of the rtc module, for example, writing 0x55 to the 0x1c address

<li>We first set the address of the register to be written to 0x1c

[[File:~~media/image376~~zero2w-img376.png]]</li>

<li>Then set the value to be written to 0x55

[[File:~~media/image377~~zero2w-img377.png]]</li>

<li>Then click the '''WRITE BYTE''' button to perform the writing action

[[File:~~media/image378~~zero2w-img378.png]]</li></ol>

</li>

<li>Then click the '''READ BYTE''' button to read the value of the 0x1c register. If it displays 0x55, it means that the i2c read and write test has passed.

[[File:~~media/image379~~zero2w-img379.png]]</li></ol>

<li>First click the wiringOP icon to open wiringOP APP</li></ol>

[[File:~~media/image351~~zero2w-img351.png]]

<li>Then click the '''PWM_TEST''' button on the main interface of wiringOP to enter the PWM test interface</li></ol>

[[File:~~media/image380~~zero2w-img380.png]]

[[File:~~media/image381~~zero2w-img381.png]]

</div>

<li>Then set which PWM you want to use in the Channel. The default is PWM1. If you want to set it to PWM2, just enter 2 in the Channel. PWM3 and PWM4 and so on.</li></ol>

[[File:~~media/image382~~zero2w-img382.png]]

<li>Then you can set the PWM period. The default configuration is '''50000ns'''. The converted PWM frequency is '''20KHz'''</li></ol>

[[File:~~media/image383~~zero2w-img383.png]]

<li>Then click the '''EXPORT'''button to export PWM</li></ol>

[[File:~~media/image384~~zero2w-img384.png]]

<li>Then drag the progress bar below to change the PWM duty cycle, and then check '''Enable''' to output the PWM waveform.</li></ol>

[[File:~~media/image385~~zero2w-img385.png]]

<li>Then use an oscilloscope to measure the corresponding pins in the 40pin development board and you can see the following waveform.</li></ol>

[[File:~~media/image386~~zero2w-img386.png]]

</li></ol>

[[File:~~media/image387~~zero2w-img387.png]]

{| class="wikitable"

|-

| ~~* *~~'''Date**'''

| '''Release Notes'''

Admin

Bureaucrats, Administrators

8,367

edits

Wiki-Orange Pi β

Changes

Orange Pi Zero 2W

Wiki-Orange Pi ^β