8,367
edits
Changes
→Download orangepi-build from github
<div class="figure">
[[File:zero2w-img3.png|800px]]
</div>
<div class="figure">
[[File:zero2w-img4.png|800px]]
</div>
<div class="figure">
[[File:zero2w-img5.png|800px]]
</div>
<span id="orange-pi-zero-2w-24pin-expansion-board-interface-details"></span>
== Orange Pi Zero 2w 24pin expansion board interface details ==
<div class="figure">
[[File:zero2w-img6.png|800px]]
</div>
[[File:zero2w-img7.png|800px]]
{| class="wikitable" style="background-color:#ffffdc;width:800px;"
=== How to set up 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. After starting the Linux system, it will automatically connect to the Ethernet port through DHCP. 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 router's background, and then 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 ssh through the IP address of the Ethernet port and then use commands to connect to WIFI, or use 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 viewed through the router background. Or if there is no HDMI screen, serial port module and network cable, and only WIFI can be connected, you can use the method introduced in this section to automatically connect to WIFI and 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 virtual machine with Ubuntu system installed.'''
'''To use the method in this section, Why do you first need to prepare a Linux system machine? Because the root file system of the Linux system of the development board burned in the TF card is in ext4 format. For example, The Linux system machine can mount it normally and then modify the configuration file in it.'''</big>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If you want to modify it in a computer or virtual machine with Ubuntu Windows system installed, you can use the software Paragon ExtFS for Windows. Since this software requires payment, and there is currently no similar free software that is easy to use, I will not demonstrate it in detail here.'''
<ol style="list-style-type: decimal;">
<li><p>First burn the Linux image of the development board you want to use into a TF card, and then use a card reader to insert the TF card with the Linux image of the development board into a machine with a Linux system (such as a machine with Ubuntu system Computer, the following uses Ubuntu computer as an example for demonstration)</p></li>
<li><p>When the TF card is inserted into the Ubuntu computer, the Ubuntu computer will generally automatically mount the Linux root file system partition in the TF card. From the following command, we can know that '''/media/test/opi_root''' is the Linux root file in the TF card. System mounting path</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>test@test:~$ '''df -h | grep "media"'''</p>
<p>/dev/sdd1 1.4G 1.2G 167M 88% '''<span style="color:#FF0000">/media/test/opi_root</span>'''</p>
<p>test@test:~$ '''ls /media/test/opi_root'''</p>
<p>bin boot dev etc home lib lost+found media mnt opt proc root run <br> sbin selinux srv sys tmp usr var</p>|}</li>
<li><p>Then enter the '''/boot''' directory of the Linux system burned in the TF card</p>
{| class="wikitable" style="width:800px;" |-| <p>test@test:~$ '''cd /media/test/opi_root/boot/'''</p>|}</li>
<li><p>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 development board to automatically connect to a WIFI hotspot when the Linux system starts for the first time. You can also set the WIFI or Ethernet port Static IP address.</p>
{| class="wikitable" style="width:800px;" |-| <p>test@test:/media/test/opi_root/boot$ '''sudo cp orangepi_first_run.txt.template orangepi_first_run.txt'''</p>|}</li>
<li><p>You can open the orangepi_first_run.txt file through the following command, and then you can view and modify the contents.</p>
{| class="wikitable" style="width:800px;" |-| <p>test@test:/media/test/opi_root/boot$ '''sudo vim orangepi_first_run.txt'''</p>|}</li>
<li><p>Variable usage instructions in the orangepi_first_run.txt file</p>
<ol style="list-style-type: lower-alpha;">
<li><p>'''FR_general_delete_this_file_after_completion''' The variable is > used to set whether to delete the orangepi_first_run.txt file > after the first startup. The default is 1, which means > deletion. If set to 0, orangepi_first_run.txt will be renamed > after the first startup.orangepi_first_run.txt.old, Generally, > just keep the default value</p></li><li><p>'''FR_net_change_defaults''' The 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.</p></li><li><p>'''FR_net_ethernet_enabled''' The 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</p></li><li><p>'''FR_net_wifi_enabled''' The 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. Also please note that if this variable > is set to 1, the Ethernet port settings will be invalid. That > is to say, the WIFI and Ethernet ports cannot be set at the > same time (why, because it is not necessary...)</p></li><li><p>'''FR_net_wifi_ssid''' Variable is used to set the name of the > WIFI hotspot you want to connect to</p></li><li><p>'''FR_net_wifi_key''' Variable is used to set the password of the > WIFI hotspot you want to connect to</p></li><li><p>'''FR_net_use_static''' Variables are used to set whether the > static IP address of the WIFI or Ethernet port needs to be > set.</p></li><li><p>'''FR_net_static_ip''' The variable is used to set the static IP > address. Please set it according to your actual situation.</p></li><li><p>'''FR_net_static_gateway''' Variables are used to set the gateway. > Please set according to your actual situation.</p></li></ol>
</li>
<li><p>Here are some specific setting examples:</p>
<ol style="list-style-type: lower-alpha;">
<li><p>For example, if you want the Linux system of the development > board to automatically connect to the WIFI hotspot after it is > started for the first time, you can set it like this: </p><ol style="list-style-type: lower-alphanone;"><li><p>a) Set '''FR_net_change_defaults''' to 1</p></li><li><p>b) Set '''FR_net_wifi_enabled''' to '''1'''</p></li><li><p>c) Set '''FR_net_wifi_ssid''' to the name of the WIFI hotspot you > want to connect to</p></li><li><p>d) Set '''FR_net_wifi_key''' to the password of the WIFI hotspot > you want to connect to</p></li></ol>
</li>
<li><p>For example, you want the Linux system of the development board > to automatically connect to the WIFI hotspot after the first > startup, and set the WIFI IP address to a specific static IP > address (so that when the Linux system starts, you can > directly use the set static IP address to ssh remotely Log in > to the development board, there is no need to check the IP > address of the development board through the router > background), you can set it like this:</p><ol style="list-style-type: lower-alphanone;"><li><p>a) Set '''FR_net_change_defaults''' to '''1'''</p></li><li><p>b) Set '''FR_net_wifi_enabled''' to '''1'''</p></li><li><p>c) Set '''FR_net_wifi_ssid''' to the name of the WIFI hotspot you > want to connect to</p></li><li><p>d) Set '''FR_net_wifi_key''' to the password of the WIFI hotspot > you want to connect to</p></li><li><p>e) Set '''FR_net_use_static''' to '''1'''</p></li><li><p>f) Set '''FR_net_static_ip''' to the desired IP address</p></li><li><p>g) Set '''R_net_static_gateway''' to the corresponding gateway > address</p></li></ol>
</li>
<li><p>For example, if you want the development board's Linux system > to automatically set the IP address of the Ethernet port to > the desired static IP address after it is started for the > first time, you can set it like this</p><ol style="list-style-type: lower-alphanone;"><li><p>a) Set '''FR_net_change_default''' to '''1'''</p></li><li><p>b) Set '''FR_net_ethernet_enabled''' to '''1'''</p></li><li><p>c) Set '''FR_net_use_static''' to '''1'''</p></li><li><p>d) Set '''FR_net_static_ip''' to the desired IP address</p></li><li><p>e) Set '''FR_net_static_gateway''' to the corresponding gateway > address</p></li></ol>
</li></ol>
</li>
<li><p>After modifying the orangepi_first_run.txt file, you can exit the /boot directory of the development board Linux system in the TF card, uninstall the TF card, and then insert the TF card into the development board to start.</p></li>
<li><p>If a static IP address is not set, you still need to check the IP address through the router background. If a static IP address is set, 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 been set up correctly, and then you can use the set IP address to ssh to remotely log in to the Linux system of the development board.</p>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| </libig></ol> '''After the development board's Linux system is started for the first time, orangepi_first_run.txt will be deleted or renamed to orangepi_first_run.txt.old. At this time, even if the orangepi_first_run.txt configuration file is reset, and then the development board's Linux system is restarted, orangepi_first_run. The configuration in txt will not take effect again, because this configuration will only take effect when the Linux system is started for the first time after burning it. Please pay special attention to this point.'''</big>|}</li></ol><span id="ssh-remote-login-development-board"></span>
== SSH remote login development board ==
{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Linux systems enable ssh remote login by default and allow root users to log in to the system. Before ssh login, you first need to ensure that the Ethernet or wifi network is connected, and then use the ip addr command or obtain the IP address of the development board by checking the router'''</big>|}
<span id="ssh-remote-login-development-board-under-ubuntu"></span>
# 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: （iEnter （Enter your password here, the default password is orangepi）|}::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that when entering a password, <span style="color:#FF0000">the specific content of the entered password will not be displayed on the screen</span>. Please do not think that there is something wrong. Just press Enter after entering it.'''
'''Note that when entering a password, the specific content of the entered password will not be displayed on the screen. Please do not think that there is something wrong. Just press Enter after entering it.''' '''f If you are prompted to refuse the connection, as long as you are using the image provided by Orange Pi, <span style="color:#FF0000">please do not doubt whether the orangepi password is incorrect</span>, but look for other reasons.'''</big>|}
<ol start="3" style="list-style-type: decimal;">
<li><p>After successfully logging into the system, the display is as shown below</p>
<p>[[File:zero2w-img140.png]]</p>
{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>'''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?: '''</p></li></ol>
root@orangepi:~# '''reset_ssh.sh'''
'''If it still doesn't work, please try restarting the system.'''</big>
|}
</li></ol>
<span id="ssh-remote-login-development-board-under-windows"></span>
=== SSH remote login development board under Windows ===
<li><p>Open '''Session'''</p></li>
<li><p>Then select '''SSH''' in '''Session Setting'''</p></li>
<li><p>Then enter the IP address of the development board in '''Remote > host'''</p></li><li><p>Then enter the username '''root''' or '''orangepi''' of the linux > system in '''Specify username'''.</p></li>
<li><p>Finally click '''OK'''</p>
<div class="figure">
</li>
<li><p>You will then be prompted to enter a password. The default passwords for both root and orangepi users are orangepi.</p>
{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>'''Note that when entering a password, <span style="color:#FF0000">the specific content of the entered password will not be displayed on the screen</span>. Please do not think that there is any malfunction. Just press Enter after entering the password.'''</p></big>|}
<div class="figure">
<span id="hdmi-test"></span>
== HDMI test ==
</div></li>
<li><p>After starting the Linux system, if there is image output on the HDMI display, it means that the HDMI interface is working normally.</p>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| </li></olbig>'''Note that although many laptops have HDMI interfaces, the HDMI interface of the laptop generally only has the output function and does not have the HDMI in function, which means that the HDMI output of other devices cannot be displayed on the laptop screen'''
'''Note that although many laptops have When you want to connect the HDMI interfaces, of the development board to the HDMI interface of the your laptop, please first confirm that your laptop generally only has supports the output HDMI in function and '''</big>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''When HDMI does not have display, please first check whether the HDMI cable is plugged in function, which means tightly. After confirming that the HDMI output of other devices cannot be displayed on the laptop wiring is OK, you can try a different screento see if there is any display.'''</big>|}</li></ol><span id="hdmi-to-vga-display-test"></span>
=== HDMI to VGA display test ===
<li><p>HDMI to VGA display test is as follows</p>
<p>[[File:zero2w-img147.png]]</p>
{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>'''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.'''</p></big>|}</li></ol>
<span id="how-to-set-hdmi-resolution-in-linux5.4-system"></span>
=== 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 Linux 5.4 kernel.'''</big>|}
<ol style="list-style-type: decimal;">
<li><p>There is a disp_mode variable in '''/boot/orangepiEnv.txt''' of the Linux system, which can be used to set the resolution of HDMI output. The default resolution of the Linux system is 1080p60</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''</p>
<p>verbosity=1</p>
<p>console=both</p>
<p>disp_mode='''<span style="color:#FF0000">1080p60</span>'''</p>
<p>fb0_width=1920</p>
<p>fb0_height=1080</p>|}</li><li><p>The disp_mode variable supports setting values as shown in the table below</p></li></ol>
{| class="wikitable" style="width:800px;text-align: center;"
|-
| '''disp_mode supported values'''
| '''60'''
|}
{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note: Linux systems currently do not support 4K resolution.'''</big>|}</ol>
<ol start="3" style="list-style-type: decimal;">
<li><p>Change the value of the disp_mode variable to the resolution you want to output, then restart the system, and HDMI will output the set resolution.</p></li>
<li><p>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.</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''sudo cat /sys/class/disp/disp/attr/sys'''</p>
|}
<p>[[File:zero2w-img148.png]]</p></li></ol>
<span id="how-to-modify-the-width-and-height-of-framebuffer-in-linux5.4-system"></span>
=== How to modify the width and height of Framebuffer in Linux5.4 system ===
{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note: This method is only applicable to systems with Linux 5.4 kernel.'''</big>|}
There are two variables, fb0_width and fb0_height, in '''/boot/orangepiEnv.txt''' of the Linux system. You can use them to set the width and height of the Framebuffer. The Linux system defaults to fb0_width=1920 and fb0_height=1080.
{| class="wikitable" style="width:800px;"
|-
|
orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''
disp_mode=1080p60
'''<span style="color:#FF0000">fb0_width=1920</span>'''
'''<span style="color:#FF0000">fb0_height=1080</span>'''|}
The reference values corresponding to different resolutions of fb0_width and fb0_height are as follows::
{| class="wikitable" style="width:800px;text-align: center;"
|-
| '''HDMI resolution'''
<span id="framebuffer-cursor-setting"></span>
=== Framebuffer cursor setting ===
<ol style="list-style-type: decimal;">
<li><p>The softcursor used by Framebuffer, the method to set the cursor to blink or not to blink is as follows</p>
{| class="wikitable" style="width:800px;" |-| <p>root@orangepi:~# '''echo <span style="color:#FF0000">1 </span> > /sys/class/graphics/fbcon/cursor_blink #Cursor flashes'''</p><p>root@orangepi:~# '''echo <span style="color:#FF0000">0 </span> > /sys/class/graphics/fbcon/cursor_blink #Cursor does not flash'''</p>|}</li>
<li><p>If you need to hide the cursor, you can add vt.global_cursor_default=0 to the '''extraargs''' variable in '''/boot/orangepiEnv.txt''' (the value of extraargs will be assigned to the '''bootargs''' environment variable and eventually passed to the kernel) (if '''<span class="mark">vt.global_cursor_default=1</span>''', it will be displayed cursor), then restart the system and you will see that the cursor has disappeared.</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''</p>
<p>verbosity=1</p>
<p>fb0_width=1920</p>
<p>fb0_height=1080</p>
<p>'''<span style="color:#FF0000">extraargs=vt.global_cursor_default=0</span>'''</p>|}</li></ol>
<span id="how-to-use-bluetooth"></span>
== How to use Bluetooth ==
<ol style="list-style-type: decimal;">
<li><p>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.</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''sudo apt update && sudo apt install -y bluez'''</p>
<p>orangepi@orangepi:~$ '''hciconfig -a'''</p>
<p>hci0: Type: Primary Bus: UART</p>
:<p>BD Address: 3E:61:3D:19:0E:52 ACL MTU: 1021:8 SCO MTU: 240:3</p>:<p>UP RUNNING</p>:<p>RX bytes:925 acl:0 sco:0 events:72 errors:0</p>:<p>TX bytes:5498 acl:0 sco:0 commands:72 errors:0</p>:<p>Features: 0xbf 0xff 0x8d 0xfe 0xdb 0x3d 0x7b 0xc7</p>:<p>Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3</p>:<p>Link policy: RSWITCH SNIFF</p>:<p>Link mode: SLAVE ACCEPT</p>:<p>Name: 'orangepi'</p>:<p>Class: 0x3c0000</p>:<p>Service Classes: Rendering, Capturing, Object Transfer, Audio</p>:<p>Device Class: Miscellaneous,</p>:<p>HCI Version: 5.0 (0x9) Revision: 0x400</p>:<p>LMP Version: 5.0 (0x9) Subversion: 0x400</p>:<p>Manufacturer: Spreadtrum Communications Shanghai Ltd (492)</p>|}</li>
<li><p>Use '''bluetoothctl''' to scan for Bluetooth devices</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''sudo bluetoothctl'''</p>
<p>[NEW] Controller 10:11:12:13:14:15 orangepizero2w [default]</p>
<p>Discovery stopped</p>
<p>[CHG] Controller 10:11:12:13:14:15 Discovering: no</p>
<p>[CHG] Device DC:72:9B:4C:F4:CF RSSI is nil</p>|}</li>
<li><p>After scanning the device you want to pair, you can pair it. For pairing, you need to use the MAC address of the device.</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>[bluetooth]# '''pair DC:72:9B:4C:F4:CF''' '''#Pair using the MAC address of the scanned Bluetooth device'''</p>
<p>Attempting to pair with DC:72:9B:4C:F4:CF</p>
<p>'''Pairing successful #Prompt pairing successful'''</p>
<p>[CHG] Device DC:72:9B:4C:F4:CF ServicesResolved: no</p>
<p>[CHG] Device DC:72:9B:4C:F4:CF Connected: no</p>|}</li>
<li><p>After successful pairing, the Bluetooth interface of the mobile phone will appear as follows:</p>
<div class="figure">
</div></li>
<li><p>To connect to a Bluetooth device, you need to install the '''pulseaudio-module-bluetooth''' software package, and then start the '''pulseaudio''' service</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''sudo apt update'''</p>
<p>orangepi@orangepi:~$ '''sudo''' '''apt -y install pulseaudio-module-bluetooth'''</p>
<p>orangepi@orangepi:~$ '''pulseaudio --start'''</p>|}</li>
<li><p>How to connect Bluetooth devices</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''sudo bluetoothctl'''</p>
<p>Agent registered</p>
<p>[CHG] Device DC:72:9B:4C:F4:CF ServicesResolved: yes</p>
<p>[CHG] Controller 10:11:12:13:14:15 Discoverable: no</p>
<p>'''[orangepi]# #If this prompt appears, the connection is successful.'''</p>|}</li>
<li><p>After connecting the Bluetooth device, you can see the prompt that the audio for calls and media has been '''connected in the Bluetooth configuration interface of the Android phone'''.</p>
<div class="figure">
<span id="usb-interface-test"></span>
== 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>|}
<span id="usb-interface-extension-description"></span>
<ol style="list-style-type: lower-alpha;">
<li><p>First run '''orangepi-config'''. Ordinary users remember to add > '''sudo''' permissions.</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''sudo orangepi-config'''</p>|}</li>
<li><p>Then select '''System'''</p>
<p>[[File:zero2w-img80.png]]</p></li>
<li><p>Then select '''Hardware'''</p>
<p>[[File:zero2w-img81.png]]</p></li>
<li><p>Then use the keyboard's arrow keys to locate the location shown in > the picture below, and then use the space to select '''usb0-host'''</p>
<p>[[File:zero2w-img161.png]]</p></li>
<li><p>Then select '''<Save>'''to save</p>
<li><p>Then select '''<Back>'''</p>
<p>[[File:zero2w-img84.png]]</p></li>
<li><p>Then select '''<Reboot>'''to restart the system to make the > configuration take effect.</p>
<p>[[File:zero2w-img85.png]]</p></li>
<li><p>After restarting, USB0 can use USB devices such as mouse and > keyboard normally.</p></li></ol>
<span id="connect-usb-mouse-or-keyboard-to-test"></span>
=== Connect USB mouse or keyboard to test ===
# Execute the following command. If you can see the output of sdX, it means the USB disk is successfully recognized.
::{| class="wikitable" style="width:800px;"|-|orangepi@orangepi:~$ '''cat /proc/partitions | grep "sd*"'''<br> <span style="margin-right: 30px;">major </span><span style="margin-right: 40px;">minor </span><span style="margin-right: 30px;">#blocks </span><span style="margin-right: 50px;">name</span><br> <span style="margin-right: 70px;">8 </span><span style="margin-right: 60px;">0 </span><span style="margin-right: 50px;">30044160 </span><span style="margin-right: 50px;color:#FF0000">'''sda'''</span><br> <span style="margin-right: 70px;">8 </span><span style="margin-right: 60px;">1 </span><span style="margin-right: 50px;">30043119 </span><span style="margin-right: 50px;color:#FF0000">'''sda1'''</span><br>|}
<ol start="3" style="list-style-type: decimal;">
<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>
<ol start="4" style="list-style-type: decimal;">
<li>After mounting, you can check 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><span id="usb-ethernet-card-test"></span>
=== USB Ethernet card test ===
# The '''currently tested''' and usable USB Ethernet cards are as follows. Among them, the RTL8153 USB Gigabit network card can be used normally when inserted into the USB 2.0 Host interface of the development board for testing, but the speed cannot reach Gigabit. Please note this.
::{| class="wikitable" style="width:800px;text-align: center;"
|-
| serial number
<ol start="2" style="list-style-type: decimal;">
<li><p>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.</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''dmesg | tail'''</p>
<p>[ 121.985016] usb 3-1: USB disconnect, device number 2</p>
<p>[ 127.763031] IPv6: ADDRCONF(NETDEV_UP): enx00e04c362017: link is not ready</p>
<p>[ 129.892465] r8152 3-1:1.0 enx00e04c362017: carrier on</p>
<p>[ 129.892583] IPv6: ADDRCONF(NETDEV_CHANGE): enx00e04c362017: link becomes ready</p>|}</li>
<li><p>Then you can see the device node of the USB network card and the automatically assigned IP address through the ifconfig command</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''sudo ifconfig'''</p>
<p>'''enx00e04c362017''': flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500</p>
::<p>inet '''192.168.1.177''' netmask 255.255.255.0 broadcast 192.168.1.255</p>::<p>inet6 fe80::681f:d293:4bc5:e9fd prefixlen 64 scopeid 0x20<link></p>::<p>ether 00:e0:4c:36:20:17 txqueuelen 1000 (Ethernet)</p>::<p>RX packets 1849 bytes 134590 (134.5 KB)</p>::<p>RX errors 0 dropped 125 overruns 0 frame 0</p>::<p>TX packets 33 bytes 2834 (2.8 KB)</p>::<p>TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0</p>|}</li>
<li><p>The command to test network connectivity is as follows</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''ping www.baidu.com -I enx00e04c362017'''</p>
<p>PING www.a.shifen.com (14.215.177.38) from 192.168.1.12 eth0: 56(84) bytes of data.</p>
<p>--- www.a.shifen.com ping statistics ---</p>
<p>4 packets transmitted, 4 received, 0% packet loss, time 3002ms</p>
<p>rtt min/avg/max/mdev = 6.260/6.770/7.275/0.373 ms</p>|}</li></ol>
<span id="usb-camera-test"></span>
=== USB camera test ===
<li><p>First insert the USB camera into the USB interface of the Orange Pi development board</p></li>
<li><p>Then you can see through the lsmod command that the kernel automatically loads the following modules</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''lsmod'''</p>
<pspan style="margin-right: 100px;">Module </span><span style="margin-right: 50px;">Size </span><span style="margin-right: 45px;">Used by</pspan><br><pspan style="margin-right: 100px;">'''uvcvideo </span><span style="margin-right: 50px;">106496 </span><span style="margin-right: 50px;">0'''</pspan><br>|}</li>
<li><p>Through the v4l2-ctl command, you can see that the device node information of the USB camera is/dev/video0</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''sudo apt update'''</p>
<p>orangepi@orangepi:~$ '''sudo''' '''apt install -y v4l-utils'''</p>
<p>orangepi@orangepi:~$ '''v4l2-ctl --list-devices'''</p>
<p>USB 2.0 Camera (usb-sunxi-ehci-1):</p>
::<p>/dev/video0</p>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>'''Note that the l in v4l2 is the lowercase letter l, not the number 1.'''</p><p>'''In addition, the serial number of the video may not always be video0, please refer to what you actually see.'''</p></big>|}</li>
<li><p>Use fswebcam to test the USB camera</p>
<ol style="list-style-type: lower-alpha;">
<li><p>Install fswebcam</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''sudo''' '''apt update'''</p>
<p>orangepi@orangepi:~$ '''sudo apt-get install -y fswebcam'''</p>|}</li><li><p>After installing fswebcam, you can use the following command to > take pictures</p><ol style="list-style-type: lower-alphanone;"><li><p>a) -d Option to specify the device node of the USB camera</p></li><li><p>b) --no-banner Used to remove watermarks from photos</p></li><li><p>c) -r option is used to specify the resolution of the photo</p></li><li><p>d) -S Option to skip previous frames</p></li><li><p>e) ./image.jpg Used to set the name and path of the generated > photo</p>{| class="wikitable" style="width:800px;" |-|
<p>orangepi@orangepi:~$ '''sudo''' '''fswebcam -d /dev/video0 \'''</p>
<p>'''--no-banner -r 1280x720 -S 5 ./image.jpg'''</p>|}</li></ol>
</li>
<li><p>In the server version of Linux system, after taking the picture, > you can use the scp command to transfer the taken picture to > the Ubuntu PC for mirror viewing.</p>{| class="wikitable" style="width:800px;" |-| <p>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）'''</p>|}</li><li><p>In the desktop version of Linux system, you can directly view > the captured pictures through the HDMI display</p></li></ol>
</li>
<li><p>Use mjpg-streamer to test the USB camera</p>
<ol style="list-style-type: lower-alpha;">
<li><p>Download mjpg-streamer</p>
<ol style="list-style-type: lower-alphanone;"><li><p>a) Github download address:</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''git clone https://github.com/jacksonliam/mjpg-streamer'''</p>|}</li><li><p>b) The image download address of Gitee is:</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''git clone https://gitee.com/leeboby/mjpg-streamer'''</p>|}</li></ol>
</li>
<li><p>Install dependent software packages</p>
<ol style="list-style-type: lower-alphanone;"><li><p>a) Ubuntu system</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''sudo apt-get install -y cmake libjpeg8-dev'''</p>|}</li><li><p>b) Debian system</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''sudo apt-get install -y cmake libjpeg62-turbo-dev'''</p>|}</li></ol>
</li>
<li><p>Compile and install mjpg-streamer</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''cd mjpg-streamer/mjpg-streamer-experimental'''</p>
<p>orangepi@orangepi:~/mjpg-streamer/mjpg-streamer-experimental$ '''make -j4'''</p>
<p>orangepi@orangepi:~/mjpg-streamer/mjpg-streamer-experimental$ '''sudo make install'''</p>|}</li>
<li><p>Then enter the following command to start mjpg_streamer</p>
{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>'''Note that the serial number of the video is not always video0, please refer to what you actually see.'''</p></big>|}{| class="wikitable" style="width:800px;" |-|
<p>orangepi@orangepi:~/mjpg-streamer/mjpg-streamer-experimental$ '''export LD_LIBRARY_PATH=.'''</p>
<p>orangepi@orangepi:~/mjpg-streamer/mjpg-streamer-experimental$ '''sudo ./mjpg_streamer -i "./input_uvc.so -d \'''</p>
<p>'''/dev/video0 -u -f 30" -o "./output_http.so -w ./www"'''</p>|}</li><li><p>Then enter ['''the IP address of the development board: 8080'''] > in the Ubuntu PC or Windows PC or mobile phone browser on the > same LAN as the development board to see the video output by > the camera.</p>
<div class="figure">
<span id="audio-test"></span>
== Audio test ==
<li><p>Use the '''aplay -l''' command to view the sound card devices supported by the Linux system</p>
<ol style="list-style-type: lower-alpha;">
<li><p>The output of the linux5.4 system is as follows, where '''card 0: > audiocodec''' is the sound card device required for headphone > playback</p>{| class="wikitable" style="width:800px;" |-|
<p>root@orangepi:~# '''aplay -l'''</p>
<p>**** List of PLAYBACK Hardware Devices ****</p>
<p>'''card 0: audiocodec [audiocodec], device 0: soc@3000000:codec_plat-5096000.codec 5096000.codec-0 []'''</p>
:<p>'''Subdevices: 1/1'''</p>:<p>'''Subdevice #0: subdevice #0'''</p>|}</li><li><p>The output of the b.linux6.1 system is as follows, where > '''audiocodec''' is the sound card device required for headphone > playback.</p>{| class="wikitable" style="width:800px;" |-|
<p>root@orangepi:~# '''aplay -l'''</p>
<p>**** List of PLAYBACK Hardware Devices ****</p>
<p>'''card 0: audiocodec [audiocodec], device 0: CDC PCM Codec-0 [CDC PCM Codec-0]'''</p>
:<p>'''Subdevices: 1/1'''</p>:<p>'''Subdevice #0: subdevice #0'''</p>|}</li></ol>
</li>
<li><p>Then use the '''aplay''' command to play the audio, and the sound can be heard through the headphones</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>root@orangepi:~# '''aplay -D hw:0,0 /usr/share/sounds/alsa/audio.wav'''</p>
<p>Playing WAVE 'audio.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo</p>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| </libig></ol> '''If there is noise during the headphone test, please pull out some of the headphones and do not plug them all the way in.'''</big>|}</li></ol><span id="hdmi-audio-playback-test"></span>
==== HDMI audio playback test ====
<li><p>First use the Mini HDMI to HDMI cable to connect the Orange Pi development board to the TV (other HDMI displays need to ensure that they can play audio)</p></li>
<li><p>HDMI audio playback does not require other settings, just use the '''aplay''' command to play directly</p>
{| class="wikitable" style="width:800px;" |-| <p>root@orangepi:~# '''aplay -D hw:2,0 /usr/share/sounds/alsa/audio.wav'''</p>|}</li></ol>
<span id="test-audio-methods-on-desktop-systems"></span>
=== Test audio methods on desktop systems ===
<li><p>First open the volume control interface</p>
<p>[[File:zero2w-img166.png]]</p></li>
<li><p>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.</p>
<div class="figure">
<span id="infrared-reception-test"></span>
== Infrared reception test ==
<li><p>There is no infrared receiver on the main board of the development board. We can expand it through a 24pin expansion board.</p>
<p>[[File:zero2w-img107.png]]</p></li>
<li><p>Install ir-keytable infrared test software</p></li></ol>{| class="wikitable" style="width:800px;" |-|
orangepi@orangepi:~$ '''sudo''' '''apt update'''
orangepi@orangepi:~$ '''sudo''' '''apt-get install -y ir-keytable'''
|}</ol>
<ol start="3" style="list-style-type: decimal;">
<li><p>Then execute ir-keytable to view the information of the infrared device</p>
<ol style="list-style-type: lower-alpha;">
<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/ with:
::Name: sunxi-ir
::Driver: sunxi-rc-recv
::Default keymap: rc_map_sunxi
::Input device: /dev/input/event1
::LIRC device: /dev/lirc0
::Attached BPF protocols: Operation not permitted
::Supported kernel protocols: lirc nec
::Enabled kernel protocols: lirc nec
::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>
<ol start="2" style="list-style-type: lower-alpha;">
<li><p>The output of the linux6.1 system is as follows</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''ir-keytable'''</p>
<p>Found /sys/class/rc/rc0/ with:</p>
::<p>Name: sunxi-ir</p>::<p>Driver: sunxi-ir</p>::<p>Default keymap: rc-empty</p>::<p>Input device: /dev/input/event5</p>::<p>LIRC device: /dev/lirc0</p>::<p>Attached BPF protocols: Operation not permitted</p>::<p>Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm</p>::<p>Enabled kernel protocols: lirc</p>::<p>bus: 25, vendor/product: 0001:0001, version: 0x0100</p>::<p>Repeat delay = 500 ms, repeat period = 125 ms</p>|}</li></ol> <!-- --/li></ol>
<ol start="4" style="list-style-type: decimal;">
<li><p>Before testing the infrared reception function, you need to prepare an Orange Pi-specific infrared remote control. '''<span classstyle="markcolor:#FF0000">Other remote controls do not support it</span>'''.</p>
<div class="figure">
<li><p>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.</p>
<ol style="list-style-type: lower-alpha;">
<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>
<ol start="2" style="list-style-type: lower-alpha;">
<li><p>linux6.1 system output is as follows</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''sudo ir-keytable -c -p NEC -t'''</p>
<p>Old keytable cleared</p>
<p>202.063219: lirc protocol(nec): scancode = 0x45c</p>
<p>202.063249: event type EV_MSC(0x04): scancode = 0x45c</p>
<p>202.063249: event type EV_SYN(0x00).</p>|}</li></ol></li></ol><span id="temperature-sensor"></span>
== Temperature sensor ==
H618 has a total of 4 temperature sensors. The command to view the temperature is as follows:
{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The displayed temperature value needs to be divided by 1000, and the unit is Celsius.'''</big>|}
<ol style="list-style-type: lower-alpha;">
<li>sensor0: CPU 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</li></ol>{| class="wikitable" style="width:800px;" |-|
orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone0/type'''
'''57734'''
|}</ol>
<ol start="2" style="list-style-type: lower-alpha;">
<li><p>sensor1: DDR 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</p>{| class="wikitable" style="width:800px;" |-|
<p>orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone1/type'''</p>
<p>'''ddr'''_thermal_zone</p>
<p>orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone1/temp'''</p>
<p>'''57410'''</p>|}</li><li><p>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</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone2/type'''</p>
<p>'''gpu'''_thermal_zone</p>
<p>orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone2/temp'''</p>
<p>'''59273'''</p>|}</li><li><p>sensor3: 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.</p>{| class="wikitable" style="width:800px;" |-|
<p>orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone3/type'''</p>
<p>'''ve'''_thermal_zone</p>
<p>orangepi@orangepi:~$ '''cat /sys/class/thermal/thermal_zone3/temp'''</p>
<p>'''58949'''</p>|}</li></ol>
<span id="how-to-check-the-temperature-in-linux6.1-system"></span>
=== How to check the temperature in linux6.1 system ===
{| class="wikitable" style="width:800px;"
|-
|
orangepi@orangepi:~$ '''sensors'''
Adapter: Virtual device
temp1: +'''<span style="color:#FF0000">47.4°C</span>''' (crit = +110.0°C)
gpu_thermal-virtual-0
Adapter: Virtual device
temp1: +'''<span style="color:#FF0000">48.7°C</span>''' (crit = +110.0°C)
ddr_thermal-virtual-0
Adapter: Virtual device
temp1: +'''<span style="color:#FF0000">47.8°C</span>''' (crit = +110.0°C)
ve_thermal-virtual-0
Adapter: Virtual device
temp1: +'''<span style="color:#FF0000">47.2°C</span>''' (crit = +110.0°C)|}
<span id="pin-interface-pin-description"></span>
== 40 Pin Interface pin description ==
{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''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.'''</big>|}
<ol style="list-style-type: decimal;">
</div></li>
<li><p>The functions of the 40 Pin interface pins on the development board are as shown in the table below</p></li></ol>
<div style="display: flex;">{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"
|-
| '''GPIO序号GPIO NO.'''
| '''GPIO'''
| '''Function'''
| '''pin'''
|-
| style="text-align: left;"|
| '''3.3V'''
| '''1'''
|-
| '''264'''
| '''TWI1-SDA'''
| '''3'''
|-
| '''263'''
| '''TWI1-SCL'''
| '''5'''
|-
| '''269'''
| '''PWM3/UART4_TX'''
| '''7'''
|-
| style="text-align: left;"|
| '''GND'''
| '''9'''
|-
| '''226'''
| '''UART5_TX'''
| '''11'''
|-
| '''227'''
| '''UART5_RX'''
| '''13'''
| '''261'''
| '''PI5'''
| '''TWI0_SCL/UART2_TX'''
| '''15'''
|-
| style="text-align: left;"|
| '''3.3V'''
| '''17'''
|-
| '''231'''
| '''SPI1_MOSI'''
| '''19'''
|-
| '''232'''
| '''SPI1_MISO'''
| '''21'''
|-
| '''230'''
| '''SPI1_CLK'''
| '''23'''
|-
| style="text-align: left;"|
| '''GND'''
| '''25'''
|-
| '''266'''
| '''TWI2-SDA/UART3_RX'''
| '''27'''
|-
| '''256'''
| style="text-align: left;"|
| '''29'''
|-
| '''271'''
| style="text-align: left;"|
| '''31'''
|-
| '''268'''
| '''PWM2'''
| '''33'''
|-
| '''258'''
| style="text-align: left;"|
| '''35'''
|-
| '''272'''
| style="text-align: left;"|
| '''37'''
|-| style="text-align: left;"|| style="text-align: left;"|| '''38GND'''| '''39'''|}{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''pin'''| '''Function'''| '''GPIO'''| '''GPIO NO.'''|-| '''2'''| '''5V'''| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''4'''
| '''5V'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''6'''
| '''GND'''
| style="text-align: left;"|
| '''PI3'''| '''259'''|} <ol start="3" style="list-styletext-typealign: decimalleft;">|<li>There are a total of 28 GPIO ports in the 40pin interface. The high|-level voltage of all GPIO ports is '''3.3v'''</li></ol> <span id="how-to-install-wiringop"></span>== How to install wiringOP == | '''Note that wiringOP is already pre-installed in the linux image released by Orange Pi. Unless the wiringOP code is updated, there is no need to re-download, compile and install, you can just use it directly.8''' | '''The storage path of the compiled wiringOP deb package in orangepi-build is: UART0_TX''' | '''orangepi-build/external/cache/debs/arm64/wiringpi_x.xx.debPH0''' | '''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.224''' [[File: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.10''' <ol style="list-style-type: decimal;"><li><p>Download the code of wiringOP</p><p>orangepi@orangepi:~$ | '''sudo apt updateUART0_RX'''</p><p>orangepi@orangepi:~$ | '''sudo apt install -y gitPH1'''</p><p>orangepi@orangepi:~$ | '''git clone https://github.com/orangepi-xunlong/wiringOP.git -b next225'''</p><p>'''Note that the source code needs to download the code of wiringOP next branch. Please don't miss the |-b next parameter.'''</p><p>'''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.'| ''</p></li><li><p>Compile and install wiringOP</p><p>orangepi@orangepi:~$ '12''cd wiringOP'''</p><p>orangepi@orangepi:~/wiringOP$ '''sudo ./build clean'''</p><p>orangepi@orangepi:~/wiringOP$ '''sudo ./build'''</p></li><li><p>The output of the test gpio readall command is as follows</p><p>[[File:zero2w-img170.png]]</p></li></ol> <span id| style="pintext-interface-gpio-i2c-uart-spi-and-pwm-testingalign: left;"></span>== 40pin interface GPIO, I2C, UART, SPI and PWM testing ==|| '''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.PI1''' <span id="pin-gpio-port-test"></span>=== 40pin GPIO port test === <ol style="list-style-type: decimal;"><li><p>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.</p><p>[[File:zero2w-img171.png]]</p></li><li><p>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.</p><p>root@orangepi:~/wiringOP# | '''gpio mode 2 out257'''</p></li><li><p>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 the low level is set successfully.</p>|-<p>root@orangepi:~/wiringOP# | '''gpio write 2 014'''</p></li><li><p>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 the setting of the high level is successful.</p><p>root@orangepi:~/wiringOP# | '''gpio write 2 1GND'''</p></li><li><p>The setting method for other pins is similar. You only need to modify the serial number of wPi to the serial number corresponding to the pin.</p></li></ol> <span id| style="howtext-to-set-the-pull-down-resistor-of-40-pin-gpio-portalign: left;"></span>|=== How to set the pull-down resistor of 40 Pin GPIO port === <ol | style="listtext-style-typealign: decimalleft;">|<li><p>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.</p><p>[[File:zero2w-img171.png]]</p></li><li><p>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.</p><p>root@orangepi:~/wiringOP# | '''gpio mode 2 in16'''</p></li><li><p>After setting to input mode, execute the following command to set the GPIO port to pull-up mode.</p><p>root@orangepi:~/wiringOP# '''gpio mode 2 up| '''</p></li><li><p>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.</p><p>root@orangepi:~PWM4/wiringOP# ''UART4_RX'gpio read 2'''</p><p>| '''1PI14'''</p></li><li><p>Then execute the following command to set the GPIO port to pull-down mode</p><p>root@orangepi:~/wiringOP# '''gpio mode 2 down'''</p></li><li><p>Then enter the following command to read the level of the GPIO port. If the level is 0, it means that the pull-down mode is set successfully.</p><p>root@orangepi:~/wiringOP# | '''gpio read 2270'''</p><p>'''0'''</p></li></ol> <span id="pin-spi-test"></span>=== 40pin SPI test === # As can be seen from the table below, the spi available for the 40pin interface is spi1, and there are two chip select pins cs0 and cs1 {| class="wikitable"
|-
| '''GPIO序号18'''| '''GPIO'''| '''Function'''style="text-align: left;"| '''pin'''|| '''pin'''| '''Function'''| '''GPIOPH4'''| '''GPIO序号228'''
|-
| '''20'''
| '''GND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-| '''22'''| '''TWI0_SDA/UART2_RX'''| '''PI6'''| '''262'''|-| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229'''|-| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''233'''|-| '''28'''| '''TWI2-SCL/UART3_TX'''| '''3.3VPI9'''| '''1265'''|-| '''230'''| '''5VGND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''26432'''| '''PI8PWM1'''| '''TWI1-SDAPI11'''| '''3267'''|| '''4'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''263'''| '''PI7'''| '''TWI1-SCL'''| '''5'''|| '''634'''
| '''GND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''26936'''| '''PI13'''| '''PWM3/UART4_TX'''style="text-align: left;"| '''7'''|| '''8'''| '''UART0_TX'''| '''PH0PC12'''| '''22476'''
|-
| '''38'''
| style="text-align: left;"|
|-
| '''226'''| '''PH2'''| '''UART5_TX'''| '''11'''|| '''1240'''
| style="text-align: left;"|
| '''PI1PI3'''| '''257259'''|}</div></ol><ol start="3" style="list-style-type: decimal;"><li>There are a total of 28 GPIO ports in the 40pin interface. The high-level voltage of all GPIO ports is '''<span style="color:#FF0000">3.3v</span>'''</li></ol> <span id="how-to-install-wiringop"></span> == How to install wiringOP == {| class="wikitable" style="background-color:#ffffdc;width:800px;"
|-
| <big>'''227Note that wiringOP is already pre-installed in the linux image released by Orange Pi. Unless the wiringOP code is updated, there is no need to re-download, compile and install, you can just use it directly.'''| '''PH3The storage path of the compiled wiringOP deb package in orangepi-build is: '''| '''UART5_RX<span style="color:blue">orangepi-build/external/cache/debs/arm64/wiringpi_x.xx.deb</span>'''| '''13After 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:zero2w-img170.png|center]]| <big>'''14WiringOP 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.'''</big>| '''GND'''} | <ol style="textlist-style-aligntype: leftdecimal;"|><li><p>Download the code of wiringOP</p>{| class="wikitable" style="text-alignwidth: left800px;"|
|-
| '''261'''| <p>orangepi@orangepi:~$ '''PI5'''| sudo apt update'''TWI0_SCL</UART2_TX'''p>| <p>orangepi@orangepi:~$ '''15sudo apt install -y git'''</p>|| <p>orangepi@orangepi:~$ '''16'git clone https://github.com/orangepi-xunlong/wiringOP.git -b next''| '''PWM4</UART4_RX'''p>| '''PI14'''}{| '''270'''class="wikitable" style="background-color:#ffffdc;width:800px;"
|-
|-
| <p>orangepi@orangepi:~$ '''231cd wiringOP'''</p>| <p>orangepi@orangepi:~/wiringOP$ '''PH7sudo ./build clean'''</p>| <p>orangepi@orangepi:~/wiringOP$ '''SPI1_MOSIsudo ./build'''</p>| '''19'''}</li>|<li><p>The output of the test gpio readall command is as follows</p>| '''20'''<p>[[File:zero2w-img170.png]]</p></li></ol>| '''GND'''| style<span id="textpin-interface-gpio-i2c-uart-spi-and-align: left;pwm-testing"|></span> == 40pin interface GPIO, I2C, UART, SPI and PWM testing == {| class="wikitable" style="textbackground-aligncolor:#ffffdc;width: left800px;"|
|-
| <big>'''232Note: The pin header on the 40pin interface is not soldered by default, and you need to solder it yourself before it can be used.'''</big>| '''PH8'''} <span id="pin-gpio-port-test"></span>| '''SPI1_MISO'''=== 40pin GPIO port test ===| '''21'''|<ol style="list-style-type: decimal;">| '''22'''<li><p>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.</p>| '''TWI0_SDA<p>[[File:zero2w-img171.png]]</p></UART2_RX'''li>| '''PI6'''<li><p>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.</p>{| '''262'''class="wikitable" style="width:800px;"
|-
| <p>root@orangepi:~/wiringOP# '''230gpio mode <span style="color:#FF0000">2</span> out'''</p>| '''PH6'''}</li><li><p>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 the low level is set successfully.</p>{| '''SPI1_CLK'''class="wikitable" style="width:800px;" | '''23'''-|| <p>root@orangepi:~/wiringOP# '''24gpio write 2 <span style="color:#FF0000">0</span>'''</p>| '''SPI1_CS0'''}</li>| '''PH5'''<li><p>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 the setting of the high level is successful.</p>{| '''229'''class="wikitable" style="width:800px;"
|-
| <p>root@orangepi:~/wiringOP# '''gpio write 2 <span style="text-aligncolor: left;#FF0000">1</span>'''</p>|}</li><li><p>The setting method for other pins is similar. You only need to modify the serial number of wPi to the serial number corresponding to the pin.</p></li></ol> | <span id="how-to-set-the-pull-down-resistor-of-40-pin-gpio-port"></span> === How to set the pull-down resistor of 40 Pin GPIO port === <ol style="textlist-style-aligntype: leftdecimal;"|>| '''GND'''<li><p>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.</p>| '''25'''<p>[[File:zero2w-img171.png]]</p></li>|<li><p>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.</p>{| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''233'''class="wikitable" style="width:800px;"
|-
| '''266'''| <p>root@orangepi:~/wiringOP# '''PI10'''| gpio mode <span style="color:#FF0000">2</span> in'''TWI2-SDA</UART3_RX'''p>| '''27'''}|</li>| '''28'''| '''TWI2<li><p>After setting to input mode, execute the following command to set the GPIO port to pull-SCLup mode.</UART3_TX'''p>{| '''PI9'''| '''265'''class="wikitable" style="width:800px;"
|-
| <p>root@orangepi:~/wiringOP# '''256gpio mode <span style="color:#FF0000">2</span> up'''</p>| '''PI0'''}</li><li><p>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.</p>{| class="wikitable" style="text-alignwidth: left800px;"|-| <p>root@orangepi:~/wiringOP# '''29gpio read <span style="color:#FF0000">2</span>'''</p>|| <p>'''30<span style="color:#FF0000">1</span>'''</p>| '''GND'''}</li><li><p>Then execute the following command to set the GPIO port to pull-down mode</p>{| class="wikitable" style="text-alignwidth: left800px;"|-| <p>root@orangepi:~/wiringOP# '''gpio mode <span style="textcolor:#FF0000">2</span> down'''</p>|}</li><li><p>Then enter the following command to read the level of the GPIO port. If the level is 0, it means that the pull-aligndown mode is set successfully.</p>{| class="wikitable" style="width: left800px;"|
|-
| <p>root@orangepi:~/wiringOP# '''271gpio read <span style="color:#FF0000">2</span>'''</p>| <p>'''PI15<span style="color:#FF0000">0</span>'''</p>| style}</li></ol> <span id="textpin-spi-align: left;test"|></span> | '''31'''=== 40pin SPI test ===|| '''32'''# As can be seen from the table below, the spi available for the 40pin interface is spi1, and there are two chip select pins cs0 and cs1| '''PWM1'''| '''PI11'''<div style="display: flex;">::{| '''267'''class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"
|-
| '''268GPIO NO.'''| '''PI12GPIO'''| '''PWM2Function'''| '''33pin'''|| '''34'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|
|-
| style="text-align: left;"|
| style="text-align: left;"|
| '''PC123.3V'''| '''761'''
|-
| '''272264'''| '''PI16PI8'''| style="text'''TWI1-align: left;"SDA'''|'''3'''|-| '''263'''| '''37PI7'''|'''TWI1-SCL'''| '''385'''| style="text-align: left;"|'''269'''| '''PI13'''| '''PI4PWM3/UART4_TX'''| '''2607'''
|-
| style="text-align: left;"|
| style="text-align: left;"|
| '''GND'''
| '''399'''|| '''40'''| style="text-align: left;"|| '''PI3'''| '''259'''|} <ol style="list-style-type: decimal;"><li><p>In Linux systems, spi1 is turned off by default and needs to be turned on manually before it can be used. The opening steps are as follows:</p><ol style="list-style-type: lower-alpha;"><li><p>First run '''orangepi-config'''. Ordinary users remember to add > '''sudo''' permissions.</p><p>orangepi@orangepi:~$ '''sudo orangepi-config'''</p></li><li><p>Then select '''System'''</p><p>[[File:zero2w-img80.png]]</p></li><li><p>Then select '''Hardware'''</p><p>[[File:zero2w-img81.png]]</p></li><li><p>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.</p></li></ol></li></ol> {| class="wikitable"
|-
| '''dtbo configuration226'''| '''illustratePH2'''| '''UART5_TX'''| '''11'''
|-
| '''spi1-cs0-cs1-spidev227'''| '''Open cs0 and cs1 of spi1 at the same timePH3'''| '''UART5_RX'''| '''13'''
|-
| '''spi1-cs0-spidev261'''| '''Only open cs0 of spi1PI5'''| '''TWI0_SCL/UART2_TX'''| '''15'''
|-
| '''spi1style="text-cs1-spidev'''align: left;"| '''Only open cs1 of spi1'''|} [[File:zero2w-img172.png]] <ol start="5" style="list-styletext-typealign: lower-alphaleft;">|<li><p>Then select | '''<Save>3.3V''' to save</p><p>[[File:zero2w-img83.png]]</p></li><li><p>Then select | '''<Back>17'''</p><p>[[File:zero2w|-img84.png]]</p></li><li><p>Then select '''<Reboot>| '''to restart the system to make the > configuration take effect.</p><p>[[File:zero2w-img85.png]]</p></li></ol> <!-- --><ol start="2" span style="list-style-typecolor: decimal;#FF0000">231<li/span><p>Then check whether there is a '''spidev1.x| ''' device node in the Linux system. If it exists, it means that the SPI1 configuration has taken effect.</pspan style="color:#FF0000">PH7<p/span>orangepi@orangepi:~$ '''ls /dev/spidev1*| '''</pspan style="color:#FF0000">SPI1_MOSI<p>/dev/spidev1.0 /dev/spidev1.1</p><pspan>'''Note that only when you open spi1-cs0-cs1-spidev, you will see the device nodes of the two spi.| '''</pspan style="color:#FF0000">19</li><li><pspan>Next, start the spi loopback test. 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.</p><p>orangepi@orangepi:~$ '''sudo spidev_test |-v -D /dev/spidev1.0| '''</p><p>spi modespan style="color: 0x0</p><p#FF0000">bits per word: 8232</pspan><p>max speed: 500000 Hz (500 KHz)</p><p>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 | ......@.…▒..................▒.</p><p>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 | ............................….</pspan style="color:#FF0000">PH8</lispan><li><p>Then short-circuit the two pins of SPI1 mosi (pin 19 in the 40pin interface) and miso (pin 21 in the 40pin interface) and then run spidev_test. The output is as follows. You can see the sending and receiving The data is the same, indicating that the loopback test passed.</p><p>orangepi@orangepi:~$ '''sudo spidev_test -v -D /dev/spidev1.0| '''</p><p>spi modespan style="color: 0x0</p><p#FF0000">bits per word: 8SPI1_MISO</p><p>max speed: 500000 Hz (500 KHz)</p><pspan>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 | ......@.…▒..................▒.</p><p>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 | ......@.…▒..................▒.</p></li></ol> <span idstyle="pin-i2c-testcolor:#FF0000">21</span>=== 40pin I2C test === # As can be seen from the table below, the i2c available for the 40pin interface are i2c0, i2c1 and i2c2 {| class="wikitable"'''
|-
| '''GPIO序号<span style="color:#FF0000">230</span>'''| '''GPIO<span style="color:#FF0000">PH6</span>'''| '''Function<span style="color:#FF0000">SPI1_CLK</span>'''| '''pin'''|| '''pin'''| '''Function'''| '''GPIO'''| '''GPIO NO.<span style="color:#FF0000">23</span>'''
|-
| style="text-align: left;"|
| style="text-align: left;"|
| '''3.3VGND'''| '''25'''|-| '''266'''| '''PI10'''| '''TWI2-SDA/UART3_RX'''| '''27'''|-| '''256'''| '''PI0'''| style="text-align: left;"|| '''29'''|-| '''271'''| '''PI15'''| style="text-align: left;"|| '''31'''|-| '''268'''| '''PI12'''| '''PWM2'''| '''33'''|-| '''258'''| '''PI2'''| style="text-align: left;"|| '''35'''|-| '''272'''| '''PI16'''| style="text-align: left;"|| '''37'''|-| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''39'''|}{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''pin'''| '''Function'''| '''GPIO'''| '''1GPIO NO.'''|-| '''2'''| '''5V'''| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''4'''
| '''5V'''
| style="text-align: left;"|
|-
| '''6'''
| '''GND'''
| style="text-align: left;"|
|-
| '''8'''
| '''UART0_TX'''
| '''224'''
|-
| '''10'''
| '''UART0_RX'''
| '''225'''
|-
| '''12'''
| style="text-align: left;"|
| '''257'''
|-
| '''GND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''16'''
| '''PWM4/UART4_RX'''
| '''270'''
|-
| '''18'''
| style="text-align: left;"|
| '''228'''
|-
| '''20'''
| '''GND'''
| style="text-align: left;"|
|-
| '''22'''
| '''TWI0_SDA/UART2_RX'''
| '''262'''
|-
| '''230'''| '''PH6'''| '''SPI1_CLK'''| '''23'''|| '''<span style="color:#FF0000">24</span>'''| '''<span style="color:#FF0000">SPI1_CS0</span>'''| '''<span style="color:#FF0000">PH5</span>'''| '''<span style="color:#FF0000">229</span>'''
|-
| '''<span style="text-aligncolor: left;#FF0000"|| style="text-align: left;"|| '''GND'''| '''25'''|| '''>26</span>'''| '''<span style="color:#FF0000">SPI1_CS1</span>'''| '''<span style="color:#FF0000">PH9</span>'''| '''<span style="color:#FF0000">233</span>'''
|-
| '''28'''
| '''TWI2-SCL/UART3_TX'''
| '''265'''
|-
| '''30'''
| '''GND'''
| style="text-align: left;"|
|-
| '''32'''
| '''PWM1'''
| '''267'''
|-
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''36'''
| style="text-align: left;"|
| '''76'''
|-
| '''38'''
| style="text-align: left;"|
| '''260'''
|-
| '''40'''
| style="text-align: left;"|
| '''259'''
|}
</div>
<ol start="2" style="list-style-type: decimal;"><li><p>i2c In Linux systems, spi1 is turned off by default in Linux systems and needs to be turned on manually to use before itcan be used. The opening steps are as follows: </p>
<ol style="list-style-type: lower-alpha;">
<li><p>First run '''orangepi-config'''. Ordinary users remember to add > '''sudo''' permissions.</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''sudo orangepi-config'''</p>|}</li>
<li><p>Then select '''System'''</p>
<p>[[File:zero2w-img80.png]]</p></li>
<li><p>Then select '''Hardware'''</p>
<p>[[File:zero2w-img81.png]]</p></li>
<li><p>Then use the keyboard's arrow keys to locate the position shown > in the picture figure below, and then use the '''space''' to select the > corresponding i2c dtbo configuration in of the picture belowSPI you want to open.</p></li></ol></li></ol>
{| class="wikitable" style="width:800px;text-align: center;"
|-
| '''Multiplexing function in 40pindtbo configuration'''| '''Corresponding dtbo configurationillustrate'''
|-
| '''40pin spi1- i2c0cs0-cs1-spidev'''| '''pi-i2c0Open cs0 and cs1 of spi1 at the same time'''
|-
| '''40pin spi1- i2c1cs0-spidev'''| '''pi-i2c1Only open cs0 of spi1'''
|-
| '''40pin spi1- i2c2cs1-spidev'''| '''pi-i2c2Only open cs1 of spi1'''
|}
[[File:zero2w-img173img172.png]]</ol>
<ol start="5" style="list-style-type: lower-alpha;">
<li><p>Then select <span class="mark">'''<Save></span> ''' to save</p>
<p>[[File:zero2w-img83.png]]</p></li>
<li><p>Then select '''<Back>'''</p>
<p>[[File:zero2w-img84.png]]</p></li>
<li><p>Then select '''<Reboot>''' to restart the system to make the > configuration take effect.</p>
<p>[[File:zero2w-img85.png]]</p></li></ol>
</li></ol>
<ol start="2" style="list-style-type: decimal;">
<li><p>Then check whether there is a '''spidev1.x''' device node in the Linux system. If it exists, it means that the SPI1 configuration has taken effect.</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''ls /dev/spidev1*'''</p>
<p>/dev/spidev1.0 /dev/spidev1.1</p>
|}
{| class="wikitable" style="background-color:#ffffdc;width:800px;"
|-
|
<big><p>'''Note that only when you open spi1-cs0-cs1-spidev, you will see the device nodes of the two spi.'''</p></big>
|}
</li>
<li><p>Next, start the spi loopback test. 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.</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''sudo spidev_test -v -D /dev/spidev1.0'''</p>
<p>spi mode: 0x0</p>
<p>bits per word: 8</p>
<p>max speed: 500000 Hz (500 KHz)</p>
<p>TX | FF FF FF FF FF FF '''<span style="color:#FF0000">40 00 00 00 00 95</span>''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.</p>
<p>RX | FF FF FF FF FF FF '''<span style="color:#FF0000">FF FF FF FF FF FF</span>''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF | ............................….</p>
|}
</li>
<li><p>Then short-circuit the two pins of SPI1 mosi (pin 19 in the 40pin interface) and miso (pin 21 in the 40pin interface) and then run spidev_test. The output is as follows. You can see the sending and receiving The data is the same, indicating that the loopback test passed.</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''sudo spidev_test -v -D /dev/spidev1.0'''</p>
<p>spi mode: 0x0</p>
<p>bits per word: 8</p>
<p>max speed: 500000 Hz (500 KHz)</p>
<p>TX | FF FF FF FF FF FF '''<span style="color:#FF0000">40 00 00 00 00 95</span>''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.</p>
<p>RX | FF FF FF FF FF FF '''<span style="color:#FF0000">40 00 00 00 00 95</span>''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.</p>
|}
</li></ol>
<!-- --><ol startspan id="3" style="list-stylepin-type: decimal;"><li><p>After starting the Linux system, first confirm that there is an open i2c device node under /dev</p><p>orangepi@orangepi:~$ '''ls /dev/i2c-*'''</p><p>'''/dev/i2c-*'''</p><p>'''Sometimes the i2c device node and the i2c bus serial number do not correspond one to one. For example, the i2c device node of the i2c1 bus may be /dev/i2c-3.'''</p><p>'''The method to accurately confirm the device node under /dev corresponding to the i2c bus is: '''</p></li></ol> <!-- --><ol style="list-style-type: lower-alpha;test"><li><p>'''First run the following command to check the corresponding relationship of i2c'''</p><p>orangepi@orangepizero2w:~$ '''ls /sys/devices/platform/soc*/*/i2c-* | grep "i2c-[0-9]"'''</p><p>/sys/devices/platform/soc/5002000.i2c/i2c-0:</p><p>/sys/devices/platform/soc/5002400.i2c/i2c-3:</p><p>/sys/devices/platform/soc/5002800.i2c/i2c-4:</p><p>/sys/devices/platform/soc/5002c00.i2c/i2c-5:</p><p>/sys/devices/platform/soc/6000000.hdmi/i2c-2:</p><p>/sys/devices/platform/soc/7081400.i2c/i2c-1:</p></li><li><p>'''In the above output'''</p></li></olspan>
| '''Function'''
| '''pin'''
|-
| style="text-align: left;"|
| '''3.3V'''
| '''1'''
|-
| '''<span style="color:#FF0000">264</span>'''| '''<span style="color:#FF0000">PI8</span>'''| '''<span style="color:#FF0000">TWI1-SDA</span>'''| '''3'''|| '''4'''| '''5V'''| <span style="text-aligncolor: left;#FF0000"|| style="text-align: left;"|>3</span>'''
|-
| '''<span style="color:#FF0000">263</span>'''| '''PI7<span style="color:#FF0000">v</span>'''| '''<span style="color:#FF0000">TWI1-SCL</span>'''| '''5'''|| '''6'''| '''GND'''| <span style="text-aligncolor: left;#FF0000"|| style="text-align: left;"|>5</span>'''
|-
| '''269'''
| '''PWM3/UART4_TX'''
| '''7'''
|-
| style="text-align: left;"|
| '''GND'''
| '''9'''
|-
| '''226'''
| '''UART5_TX'''
| '''11'''
|-
| '''227'''
| '''UART5_RX'''
| '''13'''
|-| '''14<span style="color:#FF0000">261</span>'''| '''GND<span style="color:#FF0000">PI5</span>'''| '''<span style="color:#FF0000">TWI0_SCL</span>/UART2_TX'''| '''<span style="color:#FF0000">15</span>'''|-
| style="text-align: left;"|
| style="text-align: left;"|
| '''3.3V'''
| '''17'''
|-
| '''PH7'''
| '''SPI1_MOSI'''
| '''19'''
|-
| '''232'''
| '''SPI1_MISO'''
| '''21'''
|-
| '''230'''
| '''SPI1_CLK'''
| '''23'''
|-
| style="text-align: left;"|
| '''GND'''
| '''25'''
|-
| '''<span style="color:#FF0000">266</span>'''| '''<span style="color:#FF0000">PI10</span>'''| '''<span style="color:#FF0000">TWI2-SDA</span>/UART3_RX'''| '''<span style="color:#FF0000">27'''|| '''28'''| '''TWI2-SCL</UART3_TX'''| '''PI9'''| '''265span>'''
|-
| '''256'''
| style="text-align: left;"|
| '''29'''
|-
| '''271'''
| style="text-align: left;"|
| '''31'''
|-
| '''268'''
| '''PWM2'''
| '''33'''
| '''PI2'''
| style="text-align: left;"|
| '''35'''
|-
| '''272'''
| style="text-align: left;"|
| '''37'''
|-
| style="text-align: left;"|
| '''GND'''
| '''39'''
|}
|-
| '''Multiplexing function in 40pinpin'''| '''Corresponding dtbo configurationFunction'''| '''GPIO'''| '''GPIO NO.'''
|-
| '''40pin - uart22'''| '''pi-uart25V'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''40pin - uart34'''| '''pi-uart35V'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''40pin - uart46'''| '''pi-uart4GND'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''40pin - uart58'''| '''ph-uart5UART0_TX'''|} [[File:zero2w-img175.png]] <ol start="5" style="list-style-type: lower-alpha;"><li><p>Then select '''<Save>PH0''' to save</p><p>[[File:zero2w-img83.png]]</p></li><li><p>Then select '''<Back>'''</p><p>[[File:zero2w-img84.png]]</p></li><li><p>Then select '''<Reboot>''' to restart the system to make the > configuration take effect.</p><p>[[File:zero2w-img85.png]]</p></li></ol> <!-- --><ol start="3" style="list-style-type: decimal;"><li><p>After entering the Linux system, first confirm whether there is a uart5 device node under '''/dev'''</p><p>'''Note that the linux5.4 system is /dev/ttyASx.'''</p><p>orangepi@orangepi:~$ '''ls /dev/ttyS*'| ''</p><p>/dev/ttySx</p></li><li><p>Then start testing the uart interface. First use Dupont wire to short-circuit the rx and tx pins of the uart interface to be tested.</p></li><li><p>Use the '224''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 the serial port communication is normal.</p><p>'''Note that the last x in the gpio serial /dev/ttySx command needs to be replaced with the serial number of the corresponding uart device node.'''</p><p>orangepi@orangepi:~$ '''gpio serial /dev/ttySx # linux-6.1 test command'''</p><p>orangepi@orangepi:~$ '''gpio serial /dev/ttyASx # linux-5.4 test command'''</p><p>Out: 0: -> 0</p><p>Out: 1: -> 1</p><p>Out: 2: -> 2</p><p>Out: 3: -> 3^C</p></li></ol> <span id="pwm-test-method"></span>=== PWM test method === # As can be seen from the following table, the available pwm are pwm1, pwm2, pwm3 and pwm4. {| class="wikitable"
|-
| '''GPIO NO.10'''| '''GPIOUART0_RX'''| '''FunctionPH1'''| '''Pin'''|| '''Pin'''| '''Function'''| '''GPIO'''| '''GPIO NO.225'''
|-
| '''12'''
| style="text-align: left;"|
| '''PI1'''
| '''257'''
|-
| '''14'''
| '''GND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''16'''
| '''PWM4/UART4_RX'''
| '''PI14'''
| '''270'''
|-
| '''18'''
| style="text-align: left;"|
| '''PH4'''
| '''228'''
|-
| '''26420'''| '''PI8'''| '''TWI1-SDA'''| '''3'''|| '''4'''| '''5VGND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''263<span style="color:#FF0000">22</span>'''| '''PI7<span style="color:#FF0000">TWI0_SDA</span>/UART2_RX'''| '''TWI1<span style="color:#FF0000">PI6</span>'''| '''<span style="color:#FF0000">262</span>'''|-| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229'''|-| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''233'''|-| '''<span style="color:#FF0000">28</span>'''| '''<span style="color:#FF0000">TWI2-SCL</span>/UART3_TX'''| '''5<span style="color:#FF0000">PI9</span>'''|'''<span style="color:#FF0000">265</span>'''|-| '''630'''
| '''GND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''26932'''| '''PI13PWM1'''| '''PWM3/UART4_TXPI11'''| '''7'''|| '''8'''| '''UART0_TX'''| '''PH0'''| '''224267'''
|-
| '''34'''
| '''GND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''226'''| '''PH2'''| '''UART5_TX'''| '''11'''|| '''1236'''
| style="text-align: left;"|
| '''PI1PC12'''| '''25776'''
|-
| '''22738'''| '''PH3'''style="text-align: left;"|| '''UART5_RXPI4'''| '''13260'''|-| '''1440'''| '''GND'''| style="text-align: left;"|
| style="text-align: left;"|
| '''PI3'''
| '''259'''
|}
</div>
<ol start="2" style="list-style-type: decimal;">
<li><p>i2c is turned off by default in Linux systems and needs to be turned on manually to use it. The opening steps are as follows: </p>
<ol style="list-style-type: lower-alpha;">
<li><p>First run '''orangepi-config'''. Ordinary users remember to add '''sudo''' permissions.</p>
{| class="wikitable" style="width:800px;"
|-
| <p>orangepi@orangepi:~$ '''261sudo orangepi-config'''</p>| }</li><li><p>Then select '''PI5System'''</p>| '''TWI0_SCL<p>[[File:zero2w-img80.png]]</p></UART2_TX'''li>| <li><p>Then select '''15Hardware'''</p>|<p>[[File:zero2w-img81.png]]</p></li>| <li><p>Then use the keyboard's arrow keys to locate the position shown in the picture below, and then use the ''16'space''| '''PWM4to select the corresponding i2c configuration in the picture below.</p></UART4_RX'''li>| '''PI14'''{| '''270'''class="wikitable" style="width:800px;text-align: center;"
|-
|-
| '''23140pin - i2c0'''| '''PH7'''| '''SPI1_MOSI'''| '''19'''|| '''20'''| '''GNDpi-i2c0'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''23240pin - i2c1'''| '''PH8'''| '''SPI1_MISO'''| '''21'''|| '''22'''| '''TWI0_SDA/UART2_RX'''| '''PI6'''| '''262pi-i2c1'''
|-
| '''23040pin - i2c2'''| '''PH6pi-i2c2'''| } [[File:zero2w-img173.png]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li><p>Then select <span class="mark"><Save></span> to save</p><p>[[File:zero2w-img83.png]]</p></li><li><p>Then select '''SPI1_CLK<Back>'''</p>| <p>[[File:zero2w-img84.png]]</p></li><li><p>Then select '''23<Reboot>'''to restart the system to make the configuration take effect.</p>|<p>[[File:zero2w-img85.png]]</p></li></ol>| '''24'''</li></ol>| '''SPI1_CS0'''<ol start="3" style="list-style-type: decimal;">| '''PH5'''<li><p>After starting the Linux system, first confirm that there is an open i2c device node under /dev</p>{| '''229'''class="wikitable" style="width:800px;"
|-
|-
| <big><p>'''266Sometimes the i2c device node and the i2c bus serial number do not correspond one to one. For example, the i2c device node of the i2c1 bus may be /dev/i2c-3.'''</p><p>'''The method to accurately confirm the device node under /dev corresponding to the i2c bus is: '''</p></big> <ol style="list-style-type: lower-alpha;"><li><p>'''First run the following command to check the corresponding relationship of i2c'''</p><p>orangepi@orangepizero2w:~$ '''ls /sys/devices/platform/soc*/*/i2c-* | grep "i2c-[0-9]"'''</p><p>/sys/devices/platform/soc/5002000.i2c/i2c-0:</p><p>/sys/devices/platform/soc/5002400.i2c/i2c-3:</p><p>/sys/devices/platform/soc/5002800.i2c/i2c-4:</p><p>/sys/devices/platform/soc/5002c00.i2c/i2c-5:</p><p>/sys/devices/platform/soc/6000000.hdmi/i2c-2:</p><p>/sys/devices/platform/soc/7081400.i2c/i2c-1:</p></li> <li><p>'''PI10In the above output'''</p><ol style="list-style-type: none;"><li><p>a) 5002000 is the register base address of the i2c0 bus, and i2c-0 shown behind it is its corresponding i2c device node</p></li><li><p>b) 5002400 is the register base address of the i2c1 bus, and i2c-3 shown behind it is its corresponding i2c device node</p></li><li><p>c) 5002800 is the register base address of the i2c2 bus, and i2c-4 shown behind it is its corresponding i2c device node</p></li></ol></li></ol>| }</li></ol><ol start="4" style="list-style-type: decimal;"><li><p>Then start testing i2c, first install i2c-tools</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''TWI2sudo apt-SDAget update'''</UART3_RXp><p>orangepi@orangepi:~$ '''sudo apt-get install -y i2c-tools'''</p>| }</li><li><p>Then connect an i2c device to the i2c pin of the 40pin connector</p></li><li><p>Then use the '''27i2cdetect -y x'''x command. If the address of the connected i2c device can be detected, it means that i2c can be used normally.</p>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>'''28Note 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.'''</p>| <p>'''Different i2c device addresses are different. The 0x50 address in the picture below is just an example. Please refer to what you actually see.'''TWI2</p></big>|}<div class="figure"> [[File:zero2w-SCLimg174.png]] </UART3_TXdiv></li></ol> <span id="pin-uart-test"></span> === 40pin UART test === # As can be seen from the table below, the available uarts are uart2, uart3, uart4 and uart5. Please note that uart0 is set as a debugging serial port by default. Please do not use uart0 as a normal serial port. <div style="display: flex;">::{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''GPIO NO.'''| '''GPIO'''| '''PI9Function'''| '''265pin'''
|-
| style="text-align: left;"|
| style="text-align: left;"|
| '''3.3V'''
| '''1'''
|-
| '''271264'''| '''PI15PI8'''| style="text'''TWI1-align: left;"SDA'''| '''3'''|-| '''263'''|'''PI7'''| '''31TWI1-SCL'''| '''5'''|-| '''32269'''| '''PWM1PI13'''| '''PI11PWM3/UART4_TX'''| '''2677'''
|-
| style="text-align: left;"|
| style="text-align: left;"|
| '''GND'''
| '''9'''
|-
| '''226'''
| '''PH2'''
| '''UART5_TX'''
| '''11'''
|-
| '''227'''
| '''PH3'''
| '''UART5_RX'''
| '''13'''
|-
| '''258261'''| '''PI2PI5'''| style="text-align: left;"|| '''35'''|| '''36'''| style="text-align: left;"|| '''PC12TWI0_SCL/UART2_TX'''| '''7615'''
|-
| style="text-align: left;"|
| style="text-align: left;"|
| '''PI43.3V'''| '''26017'''
|-
| '''231'''| '''PH7'''| '''SPI1_MOSI'''| '''19'''|-| '''232'''| '''PH8'''| '''SPI1_MISO'''| '''21'''|-| '''230'''| '''PH6'''| '''SPI1_CLK'''| '''23'''|-| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''25'''|-| '''266'''| '''PI10'''| '''TWI2-SDA/UART3_RX'''| '''27'''|-| '''256'''| '''PI0'''| style="text-align: left;"|| '''29'''|-| '''271'''| '''PI15'''| style="text-align: left;"|| '''31'''|-| '''268'''| '''PI12'''| '''PWM2'''| '''33'''|-| '''258'''| '''PI2'''| style="text-align: left;"|| '''35'''|-| '''272'''| '''PI16'''| style="text-align: left;"|| '''37'''|-| style="text-align: left;"|| style="text-align: left;"|| '''GND'''
| '''39'''
|}
{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"
|-
| '''pin'''
| '''Function'''
| '''GPIO'''
| '''GPIO NO.'''
|-
| '''2'''
| '''5V'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''4'''
| '''5V'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''6'''
| '''GND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''8'''
| '''UART0_TX'''
| '''PH0'''
| '''224'''
|-
| '''10'''
| '''UART0_RX'''
| '''PH1'''
| '''225'''
|-
| '''12'''
| style="text-align: left;"|
| '''PI1'''
| '''257'''
|-
| '''14'''
| '''GND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''16'''
| '''PWM4/UART4_RX'''
| '''PI14'''
| '''270'''
|-
| '''18'''
| style="text-align: left;"|
| '''PH4'''
| '''228'''
|-
| '''20'''
| '''GND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''22'''
| '''TWI0_SDA/UART2_RX'''
| '''PI6'''
| '''262'''
|-
| '''24'''
| '''SPI1_CS0'''
| '''PH5'''
| '''229'''
|-
| '''26'''
| '''SPI1_CS1'''
| '''PH9'''
| '''233'''
|-
| '''28'''
| '''TWI2-SCL/UART3_TX'''
| '''PI9'''
| '''265'''
|-
| '''30'''
| '''GND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''32'''
| '''PWM1'''
| '''PI11'''
| '''267'''
|-
| '''34'''
| '''GND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''36'''
| style="text-align: left;"|
| '''PC12'''
| '''76'''
|-
| '''38'''
| style="text-align: left;"|
| '''PI4'''
| '''260'''
|-
| '''40'''
| style="text-align: left;"|
| '''PI3'''
| '''259'''
|}
</div>
<ol start="2" style="list-style-type: decimal;"><li><p>pwm In Linux systems, uart is turned off by default in Linux systems and needs to be turned on manually to use before itcan be used. The opening steps are as follows:</p><ol style="list-style-type: lower-alpha;"><li><p>First run '''orangepi-config'''. Ordinary users remember to add > '''sudo''' permissions.</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''sudo orangepi-config'''</p>|}</li><li><p>Then select '''System'''</p><p>[[File:zero2w-img80.png]]</p></li><li><p>Then select '''Hardware'''</p><p>[[File:zero2w-img81.png]]</p></li><li><p>Then use the keyboard's arrow keys to locate the position shown > in the figure picture below, and then use the '''space''' to select the > configuration corresponding to the pwm serial port you want to open.</p><p>[[File:zero2w-img176.png]]</p></li><li><p>Then select '''<Save>''' to save</p><p>[[File:zero2w-img83.png]]</p></li><li><p>Then select '''<Back>'''</p><p>[[File:zero2w-img84.png]]</p></li><li><p>Then select '''<Reboot>''' to restart the system to make the > configuration take effect.</p><p>[[File:zero2w-img85.png]]</p></li></ol></li><li><p>After restarting, you can start the PWM test</p><p>'''Please execute the following commands under the root user.'''</p><ol style="list-style-type: lower-alpha;"><li><p>Enter the following command on the command line to make pwm1 > output a 50Hz square wave</p><p>root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip0/export'''</p><p>root@orangepi:~# '''echo 20000000 > /sys/class/pwm/pwmchip0/pwm1/period'''</p><p>root@orangepi:~# '''echo 1000000 > /sys/class/pwm/pwmchip0/pwm1/duty_cycle'''</p><p>root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip0/pwm1/enable'''</p></li><li><p>Enter the following command on the command line to make pwm2 > output a 50Hz square wave</p></li></ol></li></ol> root@orangepi:~# '''echo 2 > /sys/class/pwm/pwmchip0/export''' root@orangepi:~# '''echo 20000000 > /sys/class/pwm/pwmchip0/pwm2/period''' root@orangepi:~# '''echo 1000000 > /sys/class/pwm/pwmchip0/pwm2/duty_cycle''' root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip0/pwm2/enable''' <ol start="3" style="list-style-type: lower-alpha;"><li>Enter the following command on the command line to make pwm3 output > a 50Hz square wave</li></ol> root@orangepi:~# '''echo 3 > /sys/class/pwm/pwmchip0/export''' root@orangepi:~# '''echo 20000000 > /sys/class/pwm/pwmchip0/pwm3/period''' root@orangepi:~# '''echo 1000000 > /sys/class/pwm/pwmchip0/pwm3/duty_cycle''' root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip0/pwm3/enable''' <ol start="4" style="list-style-type: lower-alpha;"><li>Enter the following command on the command line to make pwm4 output > a 50Hz square wave</li></ol> root@orangepi:~# '''echo 4 > /sys/class/pwm/pwmchip0/export''' root@orangepi:~# '''echo 20000000 > /sys/class/pwm/pwmchip0/pwm4/period''' root@orangepi:~# '''echo 1000000 > /sys/class/pwm/pwmchip0/pwm4/duty_cycle''' root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip0/pwm4/enable''' <div class="figure"> [[File:zero2w-img177.png]] </div><span id="how-to-install-and-use-wiringop-python"></span>== How to install and use wiringOP-Python == '''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.''' '''wiringOP-Python is the Python language version of wiringOP library, used to operate the development board's GPIO, I2C, SPI, UART and other hardware resources in the Python program''' '''Also please note that all the following commands are operated under the root user.''' <span id="how-to-install-wiringop-python"></span>=== How to install wiringOP-Python === <ol style="list-style-type: decimal;"><li><p>First install dependency packages</p><p>root@orangepi:~# '''sudo apt-get update'''</p><p>root@orangepi:~# '''sudo apt-get -y install git swig python3-dev python3-setuptools'''</p></li><li><p>Then use the following command to download the source code of wiringOP-Python</p></li></ol> '''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 there are no errors during the download process due to network problems.'''
[[File:zero2w-img175.png]]
</ol>
<ol start="5" style="list-style-type: lower-alpha;">
<li><p>Then select '''<Save>''' to save</p>
<p>[[File:zero2w-img83.png]]</p></li>
<li><p>Then select '''<Back>'''</p>
<p>[[File:zero2w-img84.png]]</p></li>
<li><p>Then select '''<Reboot>''' to restart the system to make the configuration take effect.</p>
<p>[[File:zero2w-img85.png]]</p></li></ol>
</li></ol>
<!-- -->
<ol start="3" style="list-style-type: decimal;">
<li><p>Then use the following command to compile wiringOP-Python and install it into After entering the Linux system of the development board, first confirm whether there is a uart5 device node under '''/dev'''</p>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>root@orangepi:~# '''cd wiringOP-PythonNote that the linux5.4 system is /dev/ttyASx.'''</p></big>|}{| class="wikitable" style="width:800px;" |-| <p>rootorangepi@orangepi:~/wiringOP-Python# $ '''python3 generate-bindings.py > bindings.ils /dev/ttyS*'''</p><p>root@orangepi:~/wiringOPdev/ttySx</p>|}</li><li><p>Then start testing the uart interface. First use Dupont wire to short-Python# '''sudo python3 setupcircuit the rx and tx pins of the uart interface to be tested.py install'''</p></li><li><p>Then enter Use the following '''gpio''' commandin wiringOP to test the loopback function of the serial port as shown below. If helpful information is outputyou can see the following print, it means wiringOP-Python the serial port communication is successfully installednormal. Press </p>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>'''Note that the last x in the gpio serial /dev/ttySx command needs to be replaced with the serial number of the corresponding uart device node.'''q</p></big>|}{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ ''' key to exit the help information interfacegpio serial /dev/ttySx # linux-6.1 test command'''</p><p>orangepi@orangepi:~$ '''gpio serial /dev/li>ttyASx # linux-5.4 test command'''</olp>
</li></ol>
<ol start="3" div style="list-style-typedisplay: lower-alphaflex;"><li>Finally, enter the following command to view the help information of > wiringOP-Python. Press the q key to exit the help information > interface.</li></ol> >>> '''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. CLASSES builtins.object GPIO I2C Serial nes {| class GPIO(builtins.object) | GPIO(pinmode=0) | >>> <span id="pin-gpio-port-test-1wikitable"></span>=== 40pin GPIO port test === '''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:zero2w-img170.png]] <ol style="list-style-typewidth: decimal390px;"><li><p>The following uses pin No. 7 - corresponding to GPIO PI13 margin- corresponding to wPi serial number 2 - as an example to demonstrate how to set the high and low levels of the GPIO port.</p><p>[[Fileright:zero2w-img171.png]]</p></li><li><p>The steps for testing directly with commands are as follows:</p><ol style="list-style20px;text-typealign: lower-alphacenter;"><li><p>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.</p><p>root@orangepi:~/wiringOP|-Python# '''python3 -c "import wiringpi; \'''</p><p>| '''from wiringpi import GPIO; wiringpiNO.wiringPiSetup() ; \'''</p><p>| '''wiringpi.pinMode(2, GPIO.OUTPUT) ; "'''</p></li><li><p>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 the low level is set successfully.</p><p>root@orangepi:~/wiringOP-Python# | '''python3 -c "import wiringpi; \Function'''</p><p>| '''from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\Pin'''</p><p>'''wiringpi.digitalWrite(2, GPIO.LOW)"'''</p></li>|-<li><p>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 the setting of the high level is > successful.</p><p>root@orangepi| style="text-align:~/wiringOP-Python# '''python3 -c "left;import wiringpi; \'''</p>"|<p>'''from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\'''</p><p>'''wiringpi.digitalWrite(2, GPIO.HIGH)"'''</p></li></ol></li><li><p>The steps for testing in the command line of python3 are as follows:</p><ol | style="list-styletext-typealign: lower-alphaleft;">|<li><p>First use the python3 command to enter the command line mode of > python3</p><p>root@orangepi:~# | '''python33.3V'''</p></li><li><p>Then import the python module of wiringpi</p><p>>>> | '''import wiringpi1'''</p><p>>>> |-| '''from wiringpi import GPIO264'''</p></li><li><p>Then set the GPIO port to output mode, where the first parameter > of the | '''pinModePI8'''function is the serial number of the wPi > corresponding to the pin, and the second parameter is the GPIO > mode.</p><p>>>> | '''wiringpi.wiringPiSetup()TWI1-SDA'''</p><p>0</p><p>>>> | '''wiringpi.pinMode(2, GPIO.OUTPUT)3'''</p></li><li><p>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 the low level is set successfully.</p>|-<p>>>> | '''wiringpi.digitalWrite(2, GPIO.LOW)263'''</p></li><li><p>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 the setting of the high level is > successful.</p><p>>>> | '''wiringpi.digitalWrite(2, GPIO.HIGH)PI7'''</p></li></ol></li><li><p>For wiringOP-Python to set the GPIO high and low levels in the python code, you can refer to the | '''blink.pyTWI1-SCL''' test program in the examples. The | '''blink.py5''' test program will set the voltage of all GPIO ports in the 40 Pin of the development board to continuously change high and low.</p><p>root@orangepi:~/wiringOP|-Python# '''cd examples| '''</pspan style="color:#FF0000">269<p/span>root@orangepi:~/wiringOP-Python/examples# '''ls blink.py| '''</pspan style="color:#FF0000">PI13<p/span>'''blink.py| '''</pspan style="color:#FF0000">PWM3<p/span>root@orangepi:~/wiringOP-Python/examplesUART4_TX'''# python3 blink.py| '''</p></li></ol> <span idstyle="pin-spi-test-1color:#FF0000">7</span>=== 40pin SPI test === # As can be seen from the table below, the spi available for the 40pin interface is spi1, and there are two chip select pins cs0 and cs1 {| class="wikitable"|-| '''GPIO NO.'''| '''GPIO'''| '''Function'''| '''Pin'''|| '''Pin'''| '''Function'''| '''GPIO'''| '''GPIO NO.'''
|-
| style="text-align: left;"|
| style="text-align: left;"|
| '''3.3VGND'''| '''19'''|| '''2'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''PH2'''
| '''UART5_TX'''
| '''11'''
|-
| '''227'''
| '''UART5_RX'''
| '''13'''
|-
| '''261'''
| '''TWI0_SCL/UART2_TX'''
| '''15'''
|-
| style="text-align: left;"|
| '''3.3V'''
| '''17'''
|-
| '''231'''
| '''SPI1_MOSI'''
| '''19'''
| '''232'''
| '''PH8'''
| '''SPI1_MISO'''
| '''21'''
|-
| '''230'''
| '''SPI1_CLK'''
| '''23'''
|-
| style="text-align: left;"|
| '''GND'''
| '''25'''
|-
| '''266'''
| '''TWI2-SDA/UART3_RX'''
| '''27'''
|-
| '''256'''
| style="text-align: left;"|
| '''29'''
|-
| '''271'''
| style="text-align: left;"|
| '''31'''
|-
| '''<span style="color:#FF0000">268</span>'''| '''<span style="color:#FF0000">PI12</span>'''| '''<span style="color:#FF0000">PWM2</span>'''| '''33'''|| '''34'''| '''GND'''| <span style="text-aligncolor: left;#FF0000"|| style="text-align: left;"|>33</span>'''
|-
| '''258'''
| style="text-align: left;"|
| '''35'''
|-
| '''272'''
| style="text-align: left;"|
| '''37'''
|-
| style="text-align: left;"|
| '''GND'''
| '''39'''
|}
|-
| '''dtbo configuration8'''| '''illustrateUART0_TX'''| '''PH0'''| '''224'''
|-
| '''spi1-cs0-cs1-spidev10'''| '''Open cs0 and cs1 of spi1 at the same timeUART0_RX'''| '''PH1'''| '''225'''
|-
| '''spi112'''| style="text-cs0-spidevalign: left;"|| '''PI1'''| '''Only open cs0 of spi1257'''
|-
| '''spi1-cs1-spidev14'''| '''Only open cs1 of spi1GND'''|} <ol start="5" style="list-styletext-typealign: lower-alphaleft;">|<li><p>Then select '''<Save>''' to save</p><p>[[File:zero2w-img83.png]]</p></li><li><p>Then select '''<Back>'''</p><p>[[File:zero2w-img84.png]]</p></li><li><p>Then select '''<Reboot>''' to restart the system to make the > configuration take effect.</p><p>[[File:zero2w-img85.png]]</p></li></ol> <!-- --><ol start="3" | style="listtext-style-typealign: decimalleft;">|<li><p>Then check whether there is a '''spidev1.x''' device node in the Linux system. If it exists, it means that the SPI1 configuration has taken effect.</p><p>orangepi@orangepi:~$ '''ls /dev/spidev1*'''</p><p>/dev/spidev1.0 /dev/spidev1.1</p><p>'''Note that only when you open spi1-cs0-cs1|-spidev, you will see the device nodes of the two spi.'''</p></li><li><p>Then you can use the | '''spidev_test.py''' program in examples to test the SPI loopback function. The '''spidev_test.py''' program needs to specify the following two parameters:</p><ol span style="list-style-typecolor: lower-alpha;#FF0000">16<li><p/span>'''--channel''': Specify the channel number of SPI</p></li><li><p>'''--port| ''': Specify the port number of the SPI</p></li></ol></li><li><p>Without shorting 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.</p><p>root@orangepispan style="color:~/wiringOP-Python# '''cd examples'''</pFF0000">PWM4</lispan></ol> root@orangepi:~/wiringOP-Python/examples# '''python3 spidev_test.py \''' '''--channel 1 --port 0''' spi mode: 0x0 max speed: 500000 Hz (500 KHz) Opening device /dev/spidev1.1 TX | FF FF FF FF FF FF '''40 00 00 00 00 95UART4_RX''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…| RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |.............….| <ol start="6" span style="list-style-typecolor: decimal;#FF0000"><li><p>Then use Dupont wire to short-circuit the txd (pin 19 in the 40pin interface) and rxd (pin 21 in the 40pin interface) of SPI1 and then run spidev_test.py. The output is as follows, you can see If the data sent and received are the same, it means that the SPI1 loopback test is normal.PI14</p><p>root@orangepi:~/wiringOP-Python# '''cd examples'''</p></li></olspan> root@orangepi:~/wiringOP-Python/examples# '''python3 spidev_test.py \''' '''--channel 1 --port 0''' spi mode: 0x0 max speed: 500000 Hz (500 KHz) 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 |......@.......…| <span idstyle="pin-i2c-test-1color:#FF0000">270</span>=== 40pin I2C test === # As can be seen from the table below, the i2c available for the 40pin interface are i2c0, i2c1 and i2c2 {| class="wikitable"'''
|-
| '''GPIO NO.18'''| '''GPIO'''| '''Function'''style="text-align: left;"| '''Pin'''|| '''Pin'''| '''Function'''| '''GPIOPH4'''| '''GPIO NO.228'''
|-
| '''20'''
| '''GND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-| '''22'''| '''TWI0_SDA/UART2_RX'''| '''PI6'''| '''262'''|-| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229'''|-| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''233'''|-| '''28'''| '''TWI2-SCL/UART3_TX'''| '''3.3VPI9'''| '''1265'''|-| '''230'''| '''5VGND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''264<span style="color:#FF0000">32</span>'''| '''PI8<span style="color:#FF0000">PWM1</span>'''| '''TWI1-SDA'''| '''3'''|| '''4<span style="color:#FF0000">PI11</span>'''| '''5V'''| <span style="text-aligncolor: left;#FF0000"|| style="text-align: left;"|>267</span>'''
|-
| '''263'''| '''PI7'''| '''TWI1-SCL'''| '''5'''|| '''634'''
| '''GND'''
| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''26936'''| '''PI13'''| '''PWM3/UART4_TX'''style="text-align: left;"| '''7'''|| '''8'''| '''UART0_TX'''| '''PH0PC12'''| '''22476'''
|-
| '''38'''
| style="text-align: left;"|
| '''PI4'''
| '''260'''
|-
| '''40'''
| style="text-align: left;"|
| '''GNDPI3'''| '''9259'''|}| '''10'''</div> <ol start="2" style="list-style-type: decimal;"><li><p>pwm is turned off by default in Linux systems and needs to be turned on manually to use it. The opening steps are as follows:</p><ol style="list-style-type: lower-alpha;">| <li><p>First run '''UART0_RXorangepi-config'''| . Ordinary users remember to add '''PH1sudo'''permissions.</p>{| '''225'''class="wikitable" style="width:800px;"
|-
| <p>orangepi@orangepi:~$ '''226sudo orangepi-config'''</p>| }</li><li><p>Then select '''PH2System'''</p><p>[[File:zero2w-img80.png]]</p></li>| <li><p>Then select '''UART5_TXHardware'''</p><p>[[File:zero2w-img81.png]]</p></li>| <li><p>Then use the keyboard's arrow keys to locate the position shown in the figure below, and then use the '''11space'''to select the configuration corresponding to the pwm you want to open.</p>|<p>[[File:zero2w-img176.png]]</p></li>| <li><p>Then select '''12<Save>'''to save</p>| style="text<p>[[File:zero2w-align: left;"|img83.png]]</p></li>| <li><p>Then select '''PI1<Back>'''</p>| <p>[[File:zero2w-img84.png]]</p></li><li><p>Then select '''257<Reboot>'''to restart the system to make the configuration take effect.</p><p>[[File:zero2w-img85.png]]</p></li></ol></li><li><p>After restarting, you can start the PWM test</p>{| class="wikitable" style="background-color:#ffffdc;width:800px;"
|-
| '''227'''| '''PH3'''| '''UART5_RX'''| '''13'''|| <big><p>'''14Please execute the following commands under the root user.'''</p></big>| '''GND'''}| <ol style="textlist-style-aligntype: leftlower-alpha;"|><li><p>Enter the following command on the command line to make pwm1 output a 50Hz square wave</p>{| class="wikitable" style="text-alignwidth: left800px;"|
|-
| <p>root@orangepi:~# '''261echo 1 > /sys/class/pwm/pwmchip0/export'''</p>| <p>root@orangepi:~# '''PI5echo 20000000 > /sys/class/pwm/pwmchip0/pwm1/period'''</p>| <p>root@orangepi:~# '''TWI0_SCLecho 1000000 > /sys/class/pwm/pwmchip0/pwm1/UART2_TXduty_cycle'''</p>| <p>root@orangepi:~# '''15echo 1 > /sys/class/pwm/pwmchip0/pwm1/enable'''</p>|}| '''16'''</li>| '''PWM4<li><p>Enter the following command on the command line to make pwm2 output a 50Hz square wave</p></UART4_RX'''li>{| '''PI14'''| '''270'''class="wikitable" style="width:800px;"
|-
| style="text-alignroot@orangepi: left~# '''echo 2 >"|/sys/class/pwm/pwmchip0/export''' | style="text-alignroot@orangepi: left;"|| ~# '''3.3Vecho 20000000 > /sys/class/pwm/pwmchip0/pwm2/period'''| root@orangepi:~# '''17echo 1000000 > /sys/class/pwm/pwmchip0/pwm2/duty_cycle'''|| root@orangepi:~# '''18echo 1 > /sys/class/pwm/pwmchip0/pwm2/enable'''| }</ol><ol start="3" style="textlist-style-aligntype: leftlower-alpha;"|>| '''PH4'''<li>Enter the following command on the command line to make pwm3 output a 50Hz square wave</li>{| '''228'''class="wikitable" style="width:800px;"
|-
| root@orangepi:~# '''231echo 3 > /sys/class/pwm/pwmchip0/export'''| root@orangepi:~# '''PH7echo 20000000 > /sys/class/pwm/pwmchip0/pwm3/period'''| '''SPI1_MOSI'''| root@orangepi:~# '''19echo 1000000 > /sys/class/pwm/pwmchip0/pwm3/duty_cycle'''|| root@orangepi:~# '''20echo 1 > /sys/class/pwm/pwmchip0/pwm3/enable'''| '''GND'''}</ol>| <ol start="4" style="textlist-alignstyle-type: leftlower-alpha;"|><li>Enter the following command on the command line to make pwm4 output a 50Hz square wave</li>{| class="wikitable" style="text-alignwidth: left800px;"|
|-
| root@orangepi:~# '''232echo 4 > /sys/class/pwm/pwmchip0/export'''| root@orangepi:~# '''PH8echo 20000000 > /sys/class/pwm/pwmchip0/pwm4/period'''| root@orangepi:~# '''SPI1_MISOecho 1000000 > /sys/class/pwm/pwmchip0/pwm4/duty_cycle'''| root@orangepi:~# '''21echo 1 > /sys/class/pwm/pwmchip0/pwm4/enable'''|} <div class="figure"> [[File:zero2w-img177.png]] </div></ol></li></ol><span id="how-to-install-and-use-wiringop-python"></span> == How to install and use wiringOP-Python == {| class="wikitable" style="background-color:#ffffdc;width:800px;" | '''22'''-| <big>'''TWI0_SDA/UART2_RXNote: The pin header on the 40pin interface is not soldered by default, and you need to solder it yourself before it can be used.'''</big>| '''PI6'''}{| '''262'''class="wikitable" style="background-color:#ffffdc;width:800px;"
|-
| <big>'''230wiringOP-Python is the Python language version of wiringOP library, used to operate the development board's GPIO, I2C, SPI, UART and other hardware resources in the Python program''' | '''PH6Also please note that all the following commands are operated under the root user.'''</big>| '''SPI1_CLK'''} | '''23'''<span id="how-to-install-wiringop-python"></span>|=== How to install wiringOP-Python ===| '''24'''| '''SPI1_CS0'''<ol style="list-style-type: decimal;">| '''PH5'''<li><p>First install dependency packages</p>{| '''229'''class="wikitable" style="width:800px;"
|-
|-
| '''266'''| <big>'''PI10'''| '''TWI2Note that the following git clone--recursive command will automatically download the source code of wiringOP, because wiringOP-SDA/UART3_RX'''| '''27Python depends on wiringOP. Please make sure there are no errors during the download process due to network problems.'''|| '''28'''| '''TWI2If there is a problem downloading the code from GitHub, you can directly use the wiringOP-SCLPython source code that comes with the Linux image. The storage location is: /usr/UART3_TXsrc/wiringOP-Python'''</big>| '''PI9'''}{| '''265'''class="wikitable" style="width:800px;"
|-
| root@orangepi:~# '''256git clone --recursive https://github.com/orangepi-xunlong/wiringOP-Python -b next'''| '''PI0'''| style="text-alignroot@orangepi: left;"|| ~# '''29cd wiringOP-Python'''|| root@orangepi:~/wiringOP-Python# '''30git submodule update --init --remote'''| '''GND'''}</ol>| <ol start="3" style="textlist-alignstyle-type: leftdecimal;"|><li><p>Then use the following command to compile wiringOP-Python and install it into the Linux system of the development board</p>{| class="wikitable" style="text-alignwidth: left800px;"|
|-
| <p>root@orangepi:~# '''271cd wiringOP-Python'''</p>| <p>root@orangepi:~/wiringOP-Python# '''PI15python3 generate-bindings.py > bindings.i'''</p>| style="text<p>root@orangepi:~/wiringOP-align: left;"|| Python# '''31sudo python3 setup.py install'''</p>|}| '''32'''</li>| <li><p>Then enter the following command. If helpful information is output, it means wiringOP-Python is successfully installed. Press the '''PWM1q'''key to exit the help information interface.</p></li>{| '''PI11'''| '''267'''class="wikitable" style="width:800px;"
|-
| '''268'''| '''PI12'''| '''PWM2'''| '''33'''|| '''34'''| '''GND'''| style="text-alignroot@orangepi: left;"|| style="text~/wiringOP-align: left;"||-| '''258'''| Python# '''PI2'''| style="textpython3 -align: leftc ""|| '''35'''|| '''36'''| style="text-align: left;"|| '''PC12'''| '''76'''|-| '''272'''| '''PI16'''| style="text-align: leftimport wiringpi;"|| '''37'''|| '''38'''| style="text-align: lefthelp(wiringpi)""|| '''PI4'''| '''260'''|-| style="text-alignHelp on module wiringpi: left;"|| style="text-align: left;"|| '''GND'''| '''39'''NAME|| '''40'''| style="text-align: left;"|wiringpi| '''PI3'''| '''259'''|}DESCRIPTION
: # the SWIG interface file instead.|}<!-- --/ol><ol start="35" style="list-style-type: decimal;"><li><p>After starting the Linux system, first confirm that there The steps to test whether wiringOP-Python is an open i2c device node installed successfully under the python command line are as follows:<span class/p><ol style="marklist-style-type: lower-alpha;">/dev</spanli>First use the python3 command to enter the command line mode of > python3</pli><p>orangepi{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ # '''ls /dev/i2c-*python3'''|}</pol><ol start="2" style="list-style-type: lower-alpha;"><pli>Then import the python module of wiringpi</li>{| class="wikitable" style="width:800px;" |-| >>> '''/dev/i2c-*import wiringpi;'''|}</pol><ol start="3" style="list-style-type: lower-alpha;"><pli>'''Sometimes Finally, enter the i2c device node and following command to view the i2c bus serial number do not correspond one to onehelp information of > wiringOP-Python. For example, Press the i2c device node of q key to exit the i2c1 bus may be /dev/i2c-3help information > interface.'''</pli><p>{| class="wikitable" style="width:800px;" |-| >>> '''The method to accurately confirm the device node under /dev corresponding to the i2c bus is:help(wiringpi)'''</p></li></ol> Help on module wiringpi:
: # As can be seen from the table below, the available uarts are uart2, uart3, uart4 and uart5Version 4. Please note that uart0 is set as a debugging serial port by default. Please do not use uart0 as a normal serial port0.2
|-
| style="text<big>'''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-alignPython, you can only view the board's wPi number and physics through the gpio command in wiringOP Correspondence of pins.'''</big> [[File: left;"zero2w-img170.png|center]]| } <ol style="textlist-alignstyle-type: leftdecimal;"|>| '''3<li><p>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.3V'''</p>| '''1'''<p>[[File:zero2w-img171.png]]</p></li>|<li><p>The steps for testing directly with commands are as follows:</p>| '''2'''<ol style="list-style-type: lower-alpha;">| <li><p>First set the GPIO port to output mode, where the first parameter of the '''5VpinMode'''function is the serial number of the wPi corresponding to the pin, and the second parameter is the GPIO mode.</p>{| styleclass="text-align: left;wikitable"|| style="text-alignwidth: left800px;"|
|-
| '''264'''| <p>root@orangepi:~/wiringOP-Python# '''PI8python3 -c "import wiringpi; \'''</p>| <p>'''TWI1-SDAfrom wiringpi import GPIO; wiringpi.wiringPiSetup() ; \'''</p>| <p>'''3wiringpi.pinMode(<span style="color:#FF0000">2, GPIO.OUTPUT</span>) ; "'''</p>|}| '''4'''</li>| '''5V'''<li><p>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 the low level is set successfully.</p>{| styleclass="text-align: left;wikitable"|| style="text-alignwidth: left800px;"|
|-
| '''263'''| <p>root@orangepi:~/wiringOP-Python# '''PI7python3 -c "import wiringpi; \'''</p>| <p>'''TWI1-SCLfrom wiringpi import GPIO; wiringpi.wiringPiSetup() ;\'''</p>| <p>'''5wiringpi.digitalWrite(2, <span style="color:#FF0000">GPIO.LOW</span>)"'''</p>|}| '''6'''</li>| '''GND'''<li><p>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 the setting of the high level is successful.</p>{| styleclass="text-align: left;wikitable"|| style="text-alignwidth: left800px;"|
|-
| <p>root@orangepi:~/wiringOP-Python# '''269python3 -c "import wiringpi; \'''</p>| <p>'''PI13from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\'''</p>| <p>'''PWM3wiringpi.digitalWrite(2, <span style="color:#FF0000">GPIO.HIGH</UART4_TXspan>)"'''</p>| '''7'''}</li></ol>|</li>| '''8'''<li><p>The steps for testing in the command line of python3 are as follows:</p>| '''UART0_TX'''<ol style="list-style-type: lower-alpha;">| '''PH0'''<li><p>First use the python3 command to enter the command line mode of python3</p>{| '''224'''class="wikitable" style="width:800px;"
|-
|-
| '''226'''| <p>>>> '''PH2import wiringpi'''</p>| <p>>>> '''UART5_TXfrom wiringpi import GPIO'''</p>| '''11'''}|</li>| <li><p>Then set the GPIO port to output mode, where the first parameter of the '''12pinMode'''function is the serial number of the wPi corresponding to the pin, and the second parameter is the GPIO mode.</p>{| class="wikitable" style="text-alignwidth: left800px;"|| '''PI1'''| '''257'''
|-
| '''227'''| <p>>>> '''PH3wiringpi.wiringPiSetup()'''</p>| '''UART5_RX'''<p>0</p>| <p>>>> '''13wiringpi.pinMode(<span style="color:#FF0000">2, GPIO.OUTPUT</span>)'''</p>|}| '''14'''</li>| '''GND'''<li><p>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 the low level is set successfully.</p>{| styleclass="text-align: left;wikitable"|| style="text-alignwidth: left800px;"|
|-
| '''261'''| <p>>>> '''PI5'wiringpi.digitalWrite(2, <span style="color:#FF0000">GPIO.LOW</span>)''| '''TWI0_SCL</UART2_TX'''p>| '''15'''}|</li>| '''16'''| '''PWM4<li><p>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 the setting of the high level is successful.</UART4_RX'''| '''PI14'''p>{| '''270'''class="wikitable" style="width:800px;"
|-
| <p>>>> '''wiringpi.digitalWrite(2, <span style="text-aligncolor: left;#FF0000">GPIO.HIGH</span>)'''</p>|}</li></ol></li><li><p>For wiringOP-Python to set the GPIO high and low levels in the python code, you can refer to the '''blink.py''' test program in the examples. The '''blink.py''' test program will set the voltage of all GPIO ports in the 40 Pin of the development board to continuously change high and low.</p>{| class="wikitable" style="text-alignwidth: left800px;"|-| <p>root@orangepi:~/wiringOP-Python# '''cd examples'''</p><p>root@orangepi:~/wiringOP-Python/examples# '3''ls blink.3Vpy'''</p>| <p>'''17blink.py'''</p>|| <p>root@orangepi:~/wiringOP-Python/examples'''18# python3 blink.py'''</p>| }</li></ol> <span id="pin-spi-test-1"></span> === 40pin SPI test === # As can be seen from the table below, the spi available for the 40pin interface is spi1, and there are two chip select pins cs0 and cs1 <div style="display: flex;">::{| class="wikitable" style="width:390px;margin-right: 20px;text-align: leftcenter;"|-|'''GPIO NO.'''| '''GPIO'''| '''PH4Function'''| '''228Pin'''
|-
| style="text-align: left;"|
| style="text-align: left;"|
| '''3.3V'''
| '''1'''
|-
| '''264'''
| '''PI8'''
| '''TWI1-SDA'''
| '''3'''
|-
| '''232263'''| '''PH8PI7'''| '''SPI1_MISOTWI1-SCL'''| '''21'''|| '''22'''| '''TWI0_SDA/UART2_RX'''| '''PI6'''| '''2625'''
|-
| '''230269'''| '''PH6PI13'''| '''SPI1_CLKPWM3/UART4_TX'''| '''23'''|| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''2297'''
|-
| style="text-align: left;"|
| style="text-align: left;"|
| '''GND'''
| '''25'''|| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''2339'''
|-
| '''226'''| '''PH2'''| '''UART5_TX'''| '''11'''|-| '''227'''| '''PH3'''| '''UART5_RX'''| '''13'''|-| '''261'''| '''PI5'''| '''TWI0_SCL/UART2_TX'''| '''15'''|-| style="text-align: left;"|| style="text-align: left;"|| '''3.3V'''| '''17'''|-| '''<span style="color:#FF0000">231</span>'''| '''<span style="color:#FF0000">PH7</span>'''| '''<span style="color:#FF0000">SPI1_MOSI</span>'''| '''<span style="color:#FF0000">19</span>'''|-| '''<span style="color:#FF0000">232</span>'''| '''<span style="color:#FF0000">PH8</span>'''| '''<span style="color:#FF0000">SPI1_MISO</span>'''| '''<span style="color:#FF0000">21</span>'''|-| '''<span style="color:#FF0000">230</span>'''| '''<span style="color:#FF0000">PH6</span>'''| '''<span style="color:#FF0000">SPI1_CLK</span>'''| '''<span style="color:#FF0000">23</span>'''|-| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''25'''|-| '''266'''| '''PI10'''| '''TWI2-SDA/UART3_RX'''
| '''27'''
|-
| '''256'''
| style="text-align: left;"|
| '''29'''
|-
| '''271'''
| style="text-align: left;"|
| '''31'''
|-
| '''268'''
| '''PWM2'''
| '''33'''
|-
| '''258'''
| style="text-align: left;"|
| '''35'''
|-
| '''272'''
| style="text-align: left;"|
| '''37'''
|-
| style="text-align: left;"|
| '''GND'''
| '''39'''
|}{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''Pin'40''| '''Function'''| '''GPIO'''| '''GPIO NO.'''|-| '''2'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"||-| '''4'''| '''5V'''| style="text-align: left;"|
| style="text-align: left;"|
|-
| '''Multiplexing function in 40pin6'''| '''Corresponding dtbo configurationGND'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''40pin - uart28'''| '''pi-uart2UART0_TX'''| '''PH0'''| '''224'''
|-
| '''40pin - uart310'''| '''pi-uart3UART0_RX'''| '''PH1'''| '''225'''
|-
| '''40pin 12'''| style="text- uart4align: left;"|| '''PI1'''| '''pi-uart4257'''
|-
| '''40pin 14'''| '''GND'''| style="text- uart5align: left;"|| style="text-align: left;"||-| '''16'''| '''ph-uart5PWM4/UART4_RX'''|}'''PI14'''| '''270'''[[File:zero2w|-img175.png]]| '''18'''<ol start| style="5text-align: left;" || '''PH4'''| '''228'''|-| '''20'''| '''GND'''| style="listtext-align: left;"|| style="text-typealign: lower-alphaleft;">||-<li><p>Then select | '''22'''<Save>| ''' to save<TWI0_SDA/p>UART2_RX'''| '''PI6'''| '''262'''|-| '''<p>[[Filespan style="color:zero2w-img83.png]]</p#FF0000">24</lispan>'''| '''<lispan style="color:#FF0000">SPI1_CS0<p/span>Then select '''<Back>| '''</p><p>[[Filespan style="color:zero2w-img84.png]]</p#FF0000">PH5</li><lispan><p>Then select '''<Reboot>| ''' to restart the system to make the > configuration take effect.</p><p>[[Filespan style="color:zero2w-img85.png]]</p#FF0000">229</li></olspan>''' <!|-- -->| '''<ol start="3" span style="list-style-typecolor: decimal;#FF0000">26<li/span><p>After entering the Linux system, first confirm whether there is a uart5 device node under '''| '''<span classstyle="markcolor:#FF0000">/devSPI1_CS1</span>'''| '''</pspan style="color:#FF0000">PH9<p/span>'''注意, linux5.4系统为/dev/ttyASx.| '''<span style="color:#FF0000">233</pspan>'''<p>orangepi@orangepi:~$ |-| '''ls /dev/ttyS*28'''</p><p>/dev/ttySx</p></li><li><p>Then start testing the uart interface. First use Dupont wire to short| '''TWI2-circuit the rx and tx pins of the uart interface to be tested.<SCL/p></li>UART3_TX'''<li><p>Use the | '''gpioPI9''' command in wiringOP to test the loopback function of the serial port as shown below. If you can see the following print, it means the serial port communication is normal.</p><p>| '''Note that the last x in the gpio serial /dev/ttySx command needs to be replaced with the serial number of the corresponding uart device node.265'''</p><p>orangepi@orangepi:~$ |-| '''gpio serial /dev/ttySx # linux-6.1 test command30'''</p><p>orangepi@orangepi:~$ | '''gpio serial /dev/ttyASx # linux-5.4 test commandGND'''</p><p>Out| style="text-align: 0: ->left; 0</p>"|<p>Out: 1| style="text-align: ->left; 1</p>"|<p>Out: 2: |-> 2</p><p>Out: 3: -> 3^C</p></li>| '''32'''<li><p>Finally, you can run the | '''serialTest.pyPWM1''' program in examples to test the loopback function of the serial port. If you can see the following print, it means that the serial port loopback test is normal.</p><p>| '''Note that the x in /dev/ttySx or /dev/ttyASx in the command needs to be replaced with the serial number of the corresponding uart device node.PI11'''</p><p>root@orangepi:~/wiringOP-Python# | '''cd examples267'''</p><p>root@orangepi:~/wiringOP|-Python/examples# | '''python3 serialTest.py --device "/dev/ttySx" # linux6.1 use34'''</p><p>root@orangepi:~/wiringOP-Python/examples# | '''python3 serialTest.py --device "/dev/ttyASx" # linux5.4 useGND'''</p><p>Out| style="text-align: 0: ->left; 0</p>"|<p>Out| style="text-align: 1: ->left; 1</p>"|<p>Out: 2: |-> 2</p><p>Out| '''36'''| style="text-align: 3: ->left; 3</p>"|| '''PC12'''<p>Out: 4:^C</p>| '''76'''<p>exit</p></li></ol>|-| '''38'''<span id| style="hardwaretext-watchdog-testalign: left;"></span>|== Hardware watchdog test ==| '''PI4'''| '''260'''The watchdog_test program is pre|-installed in the Linux system released by Orange Pi and can be tested directly.| '''40'''The method to run the watchdog_test program is as follows| style="text-align:left;"|| '''PI3'''| '''259'''|}</div>
<ol start="2" style="list-style-type: decimal;">
<li><p>In Linux systems, spi1 is turned off by default and needs to be turned on manually before it can be used. The opening steps are as follows:</p>
<ol style="list-style-type: lower-alpha;">
<li><p>The second parameter 10 represents the counting time of the watchdogFirst run '''orangepi-config'''. If the dog is not fed within this time, the system will restartOrdinary users remember to add '''sudo''' permissions.</p></li><li><p>We can feed the dog by pressing any key on the keyboard (except ESC). After feeding the dog, the program will print a line "{| class="wikitable" style="width:800px;keep alive" to indicate that the dog feeding is successful.</p>" |-| <p>orangepi@orangepi:~$ '''sudo watchdog_test 10orangepi-config'''</p><p>open success|}</pli><pli>options is 33152,identity is sunxi-wdt</p><p>put_usr return,if 0,success:0Then select '''System'''</p><p>The old reset time is[[File: 16zero2w-img80.png]]</p><p>return ENOTTY,if -1,success:0</pli><p>return ENOTTY,if -1,success:0</pli><p>put_user return,if 0,success:0Then select '''Hardware'''</p><p>put_usr return,if 0,success[[File:0zero2w-img81.png]]</p><p>keep alive</pli><pli>keep alive</p><p>keep aliveThen 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.</p></li></ol>
TX | FF FF FF FF FF FF '''The following demonstration is to compile and install the latest version of Python 3<span style="color:#FF0000">40 00 00 00 00 95</span>''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.....9. If you want to compile and install other versions of Python, the method is the same (you need to download the source code corresponding to the Python you want to install).'''…|
RX | FF FF FF FF FF FF '''<ol span style="list-style-typecolor: decimal;#FF0000"><li><p>First install the dependency packages needed to compile Python</p><p>orangepi@orangepi:~$ '''sudo apt-get update'''</p><p>orangepi@orangepi:~$ '''sudo apt-get install -y build-essential zlib1g-dev \'''</p><p>'''libncurses5-dev libgdbm-dev libnss3-dev libssl-dev libsqlite3-dev \'''</p><p>'''libreadline-dev libffi-dev curl libbz2-dev'''</p></li><li><p>Then download the latest version of Python3.9 source code and unzip itFF FF FF FF FF FF</pspan><p>orangepi@orangepi:~$ '''wget \'''</p><p>[https://wwwFF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |.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''']</p>||}<p>orangepi@orangepi:~$ '''tar xvf Python-3.9.10.tgz'''</p></li><li><p>Then run the configuration command</pol><p>orangepi@orangepi:~$ '''cd Pythonol start="6" style="list-style-3.9.10'''</p><p>orangepi@orangepitype:~$ '''./configure --enable-optimizations'''</p></lidecimal;"><li><p>Then compile use Dupont wire to short-circuit the txd (pin 19 in the 40pin interface) and rxd (pin 21 in the 40pin interface) of SPI1 and install Python3then run spidev_test.9py. The compilation time takes about half an hour.</p><p>orangepi@orangepi:~$ '''make -j4'''</p><p>orangepi@orangepi:~$ '''sudo make altinstall'''</p></li><li><p>After installationoutput is as follows, you can use see If the following command to check data sent and received are the version number of same, it means that the Python you just installedSPI1 loopback test is normal.</p><p>orangepi@orangepi{| class="wikitable" style="width:~$ '''python3.9 800px;" |--version'''</p><p>'''Python 3.9.10'''</p></li><li><p>Then update pip</p>| <p>orangepiroot@orangepi:~$ /wiringOP-Python# '''/usr/local/bin/python3.9 -m pip install --upgrade pipcd examples'''</p></li></ol>
'''The default source used by Linux system pip is the official source of Python. However, accessing the official source of Python in China is very slow, and the installation of Python software packages often fails due to network reasons. So when using pip to install the Python library, please remember to change the pip source.--channel 1 --port 0'''
<span idol start="set-up-the-chinese-environment-and-install-the-chinese-input-method2"></span>== Set up the Chinese environment and install the Chinese input method == '''Note, before installing the Chinese input method, please make sure that the Linux system used by the development board is a desktop version.''' <span id="debian-system-installation-method"></span>=== Debian system installation method === <ol style="list-style-type: decimal;"><li><p>First set the i2c is turned off by default '''locale''' in Linux systems and needs to Chinesebe turned on manually to use it. The opening steps are as follows:</p>
<ol style="list-style-type: lower-alpha;">
<li><p>Enter the following command to start configuring '''localeFirst run '''</p><p>orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''</p></li><li><p>Then select config'''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 Ordinary users remember to add '''<OK>sudo''', and then return Car can be used)permissions.</p><p>[[File{| class="wikitable" style="width:zero2w-img186.png]]</p></li>800px;" <li><p>Then set the default '''locale''' to '''zh_CN.UTF|-8'''</p><p>[[File:zero2w-img187.png]]</p></li><li><p>After exiting the interface, the '''locale''' setting will begin. > The output displayed on the command line is as follows:</p>| <p>orangepi@orangepi:~$ '''sudo dpkgorangepi-reconfigure localesconfig'''</p><p>Generating locales (this might take a while)...</p><p>en_US.UTF-8... done</p><p>zh_CN.UTF-8... done</p><p>Generation complete.</p></li></ol>|}
</li>
[[File:zero2w-img173.png]]</divol></liol start="5" style="list-style-type: lower-alpha;"><li><p>Then put '''Google Pinyin''' on topselect </pspan class="mark"><Save><p/span>[[File:zero2w-img196.png]]to save</p><p>[[File:zero2w-img197img83.png]]</p></li><li><p>Then open the '''Geany''' editor to test the Chinese input methodselect <span class="mark"><Back></span></p><p>[[File:zero2w-img198img84.png]]</p></li><li><p>The Chinese input method test is as followsThen select <span class="mark"><Reboot></span> to restart the system to make the configuration take effect.</p><p>[[File:zero2w-img199img85.png]]</p></li></ol></li><p/ol>You can switch between Chinese and English input methods through the '''Ctrl+Space''' shortcut key</p!-- --></liol start="3" style="list-style-type: decimal;"><li><p>If you need After starting the entire Linux system to be displayed in Chinese, you can set all variables in '''first confirm that there is an open i2c device node under <span class="mark">/etcdev</default/locale''' to '''zh_CN.UTF-8'''span></p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''sudo vim ls /etcdev/default/localei2c-*'''</p><p># File generated by update-locale</p><p>LC_MESSAGES='''zh_CN.UTF/dev/i2c-8*'''</p>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <pbig>LANG='''zh_CN.UTF-8注意，这里说的Linux镜像具体指的是从Orange Pi资料下载页面下载的Debian或者Ubuntu这样的Linux发行版镜像。'''</pbig>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>LANGUAGE='''zh_CNSometimes the i2c device node and the i2c bus serial number do not correspond one to one.UTFFor example, the i2c device node of the i2c1 bus may be /dev/i2c-83.'''</p></li><li><p>Then '''restart The method to accurately confirm the device node under /dev corresponding to the systemi2c bus is: ''' and you will see that the system is displayed in Chinese.</p><p>[[File:zero2w-img200.png]]</p></li></olbig>
<ol style="list-style-type: decimallower-alpha;"><li><p>First open '''Language SupportFirst run the following command to check the corresponding relationship of i2c'''</p><p>orangepi@orangepizero2w:~$ '''ls /sys/devices/platform/soc*/*/i2c-* | grep "i2c-[[File:zero2w0-img201.png]9]"'''</p><p>/sys/devices/platform/soc/5002000.i2c/i2c-0:</lip><li><p>Then find the '''Chinese (China)''' option/sys/devices/platform/soc/5002400.i2c/i2c-3:</p><p>[[File/sys/devices/platform/soc/5002800.i2c/i2c-4:zero2w-img202.png]]</p><p>/sys/devices/platform/lisoc/5002c00.i2c/i2c-5:</p><li><p>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/sys/devices/platform/soc/6000000. After dragging, the display will be as shown belowhdmi/i2c-2:</p><p>[[File/sys/devices/platform/soc/7081400.i2c/i2c-1:zero2w-img203.png]]</p></li></ol>
<li><p>'''In the above output'''</p>
<ol style="list-style-type: none;">
<li><p>a) 5002000 is the register base address of the i2c0 bus, and i2c-0 shown behind it is its corresponding i2c device node</p></li>
<li><p>b) 5002400 is the register base address of the i2c1 bus, and i2c-3 shown behind it is its corresponding i2c device node</p></li>
<li><p>c) 5002800 is the register base address of the i2c2 bus, and i2c-4 shown behind it is its corresponding i2c device node</p></li></ol>
</li></ol>
|}
</li></ol>
<ol start="4" style="list-style-type: decimal;">
<li><p>Then select '''Apply Systemstart testing i2c, first install i2c-Wide''' to apply the Chinese settings to the entire systemtools</p><p>[[File{| class="wikitable" style="width:zero2w800px;" |-img204.png]]</p></li><li>| <p>Then set the orangepi@orangepi:~$ '''Keyboard input method system''' system to '''fcitxsudo apt-get update'''</p><p>[[Fileorangepi@orangepi:zero2w-img205.png]]</p></li><li><p>~$ '''Then restart the Linux system to make the configuration take effectsudo'''</p></li><li><p>After re-entering the system, please select '''Do not ask me againapt-get install -y i2c-tools''' in the following interface, and then please decide according to your own preferences whether the standard folder should also be updated to Chinese</p><p>[[File:zero2w-img206.png]]</p>|}</li><li><p>Then you can see that connect an i2c device to the i2c pin of the 40pin connector. Here we take the desktop is displayed in ChineseDS1307 RTC module as an example.</p><p>[[File:zero2w-img207img178.png]]</p></li><li><p>Then we can open use the '''Geanyi2cdetect -y x''' to test command. If the address of the connected i2c device can be detected, it means that the Chinese input methodi2c device is connected correctly. The opening method is as shown in the figure below</p><p>[[File{| class="wikitable" style="background-color:#ffffdc;width:zero2w800px;" |-img208.png]]</p></li>| <libig>'''<p>After opening '''Geany''', Note that x in the i2cdetect -y x command needs to be replaced with the English input method is still serial number of the default. We can switch device node corresponding to the Chinese input method through the i2c bus.'''Ctrl+Space</p>''' shortcut key, and then we can input Chinese.</pbig><p>[[File:zero2w-img209.png]]</p></li></ol>|}
[[File:zero2w-img179.png]]<span id/li></ol><ol start="7" style="installationlist-methodstyle-oftype: decimal;"><li><p>Then you can run the '''ds1307.py''' test program in '''examples''' to read the RTC time</p>{| class="wikitable" style="background-ubuntucolor:#ffffdc;width:800px;" |-22| <big><p>'''Note that the x in i2c-x in the following command needs to be replaced with the serial number of the device node corresponding to the i2c bus.04-system"'''</p></spanbig>|}{| class="wikitable" style== Installation method of Ubuntu 22"width:800px;" |-| <p>root@orangepi:~/wiringOP-Python# '''cd examples'''</p><p>root@orangepi:~/wiringOP-Python/examples# '''python3 ds1307.py --device \'''</p><p>'''"/dev/i2c-x"'''</p><p>Thu 2022-06-16 04:35:46</p><p>Thu 2022-06-16 04:35:47</p><p>Thu 2022-06-16 04 system ===:35:48</p><p>^C</p><p>exit</p>|}</li></ol>
<ol stylespan id="listpin-styleuart-type: decimal;test-1"><li><p>First open '''Language Support'''</p><p>[[File:zero2w-img201.png]]</p></li><li><p>Then find the '''Chinese (China)''' option</p><p>[[File:zero2w-img210.png]]</p></li><li><p>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:</p><p>[[File:zero2w-img211.png]]</p></li></olspan>
<ol start="2" style="list-style-type: decimal;">
<li><p>In Linux systems, uart is turned off by default and needs to be turned on manually before it can be used. The link to the official installation documentation of ROS 1 '''Noetic Ninjemys''' is opening steps are as follows::</p><p>[httpol style="list-style-type://wiki.ros.org/noetic/Installation/Ubuntu '''http://wiki.ros.org/noetic/Installation/Ubuntu''']</p></lilower-alpha;"><li><p>In the official installation documentation of ROS First run '''Noetic Ninjemysorangepi-config''', Ubuntu recommends using Ubuntu20.04, so please ensure that the system used by the development board is Ordinary users remember to add '''Ubuntu20.04 desktop systemsudo'''permissions.</p>{| class="wikitable" style="width:800px;" |-| <p>[httporangepi@orangepi:~$ '''sudo orangepi-config'''</p>|}</wiki.ros.org/noetic/Installation li><li><p>Then select '''http://wiki.ros.org/noetic/InstallationSystem''']</p><p>[[File:zero2w-img247img80.png]]</p></li><li><p>Then use the script below to install ros1select '''Hardware'''</p><p>orangepi@orangepi[[File:~$ '''install_roszero2w-img81.sh ros1'''png]]</p></li><li><p>Before using Then use the ROS toolkeyboard's arrow keys to locate the position shown in the picture below, you first need and then use the '''space''' to initialize rosdep. Then when compiling select the source code, serial port you can quickly install some system dependencies and some core components in ROSwant to open.</p></li></ol>
{| class="wikitable" style="width:800px;text-align: center;"|-| '''Note that when running the following command, you need to ensure that the development board can access github normally, otherwise an error will be reported due to network problems.Multiplexing function in 40pin'''| '''Corresponding dtbo configuration'''|-| '''40pin - uart2'''| '''pi-uart2'''|-| '''40pin - uart3'''| '''pi-uart3'''|-| '''40pin - uart4'''| '''pi-uart4'''|-| '''40pin - uart5'''| '''ph-uart5'''|}
[[File:zero2w-img175.png]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li><p>Then select '''The install_ros<Save>''' to save</p><p>[[File:zero2w-img83.sh script will try to modify png]]</etcp></hosts and automatically run the following commandsli><li><p>Then select '''<Back>'''</p><p>[[File:zero2w-img84. 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 png]]</p></li><li><p>Then select '''<Reboot>''' to allow restart the linux system of the development board to access github normally, and then manually run make the following Orderconfiguration take effect.</p><p>[[File:zero2w-img85.png]]</p></li></ol></li></ol><!-- --><ol start="3" style="list-style-type: decimal;"><li><p>After entering the Linux system, first confirm whether there is a uart5 device node under '''<span class="mark">/dev</span>'''</p>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>'''https://raw.githubusercontent注意, linux5.com/ros/rosdistro/master4系统为/rosdepdev/osx-homebrewttyASx.yaml'''</p></big>|}{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''Hit https:ls /dev/raw.githubusercontent.comttyS*'''</rosp><p>/rosdistrodev/masterttySx</rosdepp>|}</baseli><li><p>Then start testing the uart interface.yamlFirst use Dupont wire to short-circuit the rx and tx pins of the uart interface to be tested.</p></li><li><p>Use the ''' gpio'''ERRORcommand in wiringOP to test the loopback function of the serial port as shown below. If you can see the following print, it means the serial port communication is normal.</p>{| class="wikitable" style="background-color: error loading sources list#ffffdc;width:'''800px;" |-| <big><p>'''The read operation timed outNote that the last x in the gpio serial /dev/ttySx command needs to be replaced with the serial number of the corresponding uart device node.'''</p></big>|}{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''source gpio serial /optdev/ros/noetic/setupttySx # linux-6.bash1 test command'''</p> <p>orangepi@orangepi:~$ '''sudo rosdep initgpio serial /dev/ttyASx # linux-5.4 test command''' Wrote /etc/ros/rosdep</sources.list.d/20-default.list Recommended: please runp>
<p>Out: 0: -> 0</p><p>Out: 1: -> 1</p><p>Out: 2: -> 2</p><p>Out: 3: -> 3^C</p>|}</li><li><p>Finally, you can run the '''serialTest.py''' program in examples to test the loopback function of the serial port. If you can see the following print, it means that the serial port loopback test is normal.</p>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>'''Note that the x in /dev/ttySx or /dev/ttyASx in the command needs to be replaced with the serial number of the corresponding uart device node.'''</p></big>|}{| class="wikitable" style="width:800px;" |-| <p>root@orangepi:~/wiringOP-Python# '''cd examples'''</p><p>root@orangepi:~/wiringOP-Python/examples# '''python3 serialTest.py --device "/dev/ttySx" # linux6.1 use'''</p><p>root@orangepi:~$ /wiringOP-Python/examples# '''rosdep updatepython3 serialTest.py --device "/dev/ttyASx" # linux5.4 use'''</p>
<ol startspan id="6" style="listhow-to-replace-pip-stylesource-type: decimal;"><li><p>Then open a command line terminal window on the '''desktop''', and then use the '''test_ros.sh''' script to start a small turtle routine to test whether ROS can be used normally.</p><p>orangepi@orangepi:~$ '''test_ros.sh'''</p></li><li><p>After running the '''test_ros.sh''' script, a small turtle as shown in the picture below will pop up.</p><p>[[File:zero2w-img248.png]]</p></li><li><p>Then please keep the terminal window you just opened at the top</p></lipython"></olspan>
<ol style="list-style-type: decimal;">
<li><p>The currently active version of ROS 2 is as follows, the recommended version is First install '''Galactic Geochelonepython3-pip'''</p><p>[[File{| class="wikitable" style="width:zero2w800px;" |-img251.png]]</p><p>[[File:zero2w-img252.png]]</p>| <p>[httporangepi@orangepi://docs.ros.org/ ~$ '''http://docs.ros.orgsudo apt-get update''']</p><p>orangepi@orangepi:~$ '''http://docs.ros.org/en/galactic/Releases.htmlsudo apt-get install -y python3-pip'''</p>|}</li><li><p>The link How to permanently change the official installation documentation of ROS 2 '''Galactic Geochelone''' is as follows:pip source under Linux</p><p>'''docs.ros.org/en/galactic/Installation.html'''</p><p>'''httpol style="list-style-type://docs.ros.org/en/galactic/Installation/Ubuntulower-Install-Debians.html'''</p></lialpha;"><li><p>In the official installation documentation of ROS 2 First create a new '''Galactic Geochelone~/.pip'''directory, Ubuntu Linux recommends using Ubuntu20.04, so please ensure that the system used by the development board is then add the '''Ubuntu20pip.04 desktop systemconf'''. There are several ways configuration file, and set the pip source in it to install ROS 2. The following demonstrates how to install ROS 2 '''Galactic Geochelone''' through '''Debian packages'''Tsinghua source.</p></li><li>{| class="wikitable" style="width:800px;" |-| <p>Use the orangepi@orangepi:~$ '''install_rosmkdir -p ~/.shpip''' script to install ros2</p><p>orangepi@orangepi:~$ '''install_roscat <<EOF > ~/.sh ros2pip/pip.conf'''</p></li><li><p>The '''install_ros.sh''' script will automatically run the '[global]''ros2 -h''' command after installing ros2. If you can see the following print, it means that the ros2 installation is complete.</p><p>usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...'''timeout = 6000'''</p><p>ros2 is an extensible command'''index-line tool for ROS 2.</p><p>optional argumentsurl = https:</p><p>-h, --help show this help message and exit</p><p>Commands:<pypi.tuna.tsinghua.edu.cn/p><p>action Various action related sub-commands</p><p>bag Various rosbag related sub-commands</p><p>component Various component related sub-commands</p><p>daemon Various daemon related sub-commands</p><p>doctor Check ROS setup and other potential issues</p><p>interface Show information about ROS interfaces</p><p>launch Run a launch file</p><p>lifecycle Various lifecycle related sub-commands</p><p>multicast Various multicast related sub-commands</p><p>node Various node related sub-commands</p><p>param Various param related sub-commands</p><p>pkg Various package related sub-commands</p><p>run Run a package specific executable</p><p>security Various security related sub-commands</p><p>service Various service related sub-commands</p><p>topic Various topic related sub-commands</p><p>wtf Use `wtf` as alias to `doctor`</p><p>Call `ros2 <command> -h` for more detailed usage.simple'''</p></li><li><p>Then you can use the '''test_rostrusted-host = pypi.shtuna.tsinghua.edu.cn''' script to test whether ROS 2 is installed successfully. If you can see the following print, it means ROS 2 can run normally.</p><p>orangepi@orangepi:~$ '''test_ros.shEOF'''</p><p>[INFO] [1671174101.200091527] [talker]: Publishing: 'Hello World: 1'|}</pli><pli>[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: 1]</p><p>[INFO] [1671174102.199572327] [talker]: Publishing: 'Hello World: 2'Then use pip3 to install the Python library very quickly</p><p>[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]</pli><p>[INFO] [1671174103.199580322] [talker]: Publishing: 'Hello World: 3'</pol><p>[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]</p></li><li><p>Run How to temporarily change the following command to open rviz2</p><p>orangepi@orangepi:~$ pip source under Linux, where '''source /opt/ros/galactic/setup.bash<packagename>'''needs to be replaced with a specific package name</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''ros2 run rviz2 rviz2pip3 install <packagename> -i \'''</p><p>[[File'''https:zero2w-img253.png]]</p></li><li><p>For how to use ROS, please refer to the documentation of ROS 2pypi.tuna.</p><p>[http://docstsinghua.rosedu.orgcn/en/galactic/Tutorialssimple --trusted-host pypi.html '''http://docstuna.rostsinghua.org/en/galactic/Tutorialsedu.htmlcn''']</p>|}</li></ol> <span id="how-to-install-docker"></span> == How to install Docker ==
'''<span idstyle="testing-of-some-programming-languages-supported-by-linux-systemcolor:#FF0000">Hello from Docker!</span>== Testing of some programming languages supported by Linux system =='''
'''<span idstyle="debian-bullseye-systemcolor:#FF0000">This message shows that your installation appears to be working correctly.</span>=== Debian Bullseye system ==='''
<span id="ubuntuinstallation-focalvia-systemdocker"></span>=== Ubuntu Focal system Installation via docker ===
<ol style="list-style-type: decimal;">
<li><p>Ubuntu Focal is installed with the gcc compilation tool chain by defaultFirst, which please install docker and ensure that docker can directly compile C language programs in run normally. For the Linux system installation steps of docker, please refer to the instructions in the development board[[Orange Pi Zero 2W#How to install Docker|'''How to Install Docker''']] section.</p><ol style="list-style-type: lower-alpha;"/li><li><p>The version Then you can search for the docker image of a.gcc is as followsHome Assistant</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''gcc --versiondocker search homeassistant'''</p>|}</li><li><p>gcc (Ubuntu 9Then use the following command to download the Docker image of Home Assistant to your local computer.4The image size is about 1GB, and the download time will be relatively long.0-1ubuntu1~20.04.1) 9Please be patient and wait for the download to complete.4.0</p>{| class="wikitable" style="width:800px;" |-| <p>Copyright (C) 2019 Free Software Foundation, Inc.orangepi@orangepi:~$ '''docker pull homeassistant/home-assistant'''</p><p>This is free software; see the source for copying conditions. There is NOUsing default tag: latest</p><p>warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.latest: Pulling from homeassistant/home-assistant</p><p>be307f383ecc: Downloading</lip><li><p>Write the '''hello_world.c''' program in C language5fbc4c07ac88: Download complete</p><p>orangepi@orangepi:~$ '''vim hello_world.c..... (Omit some output)'''</p><p>#include <stdio.h>3cc6a1510c9f: Pull complete</p><p>int main(void)7a4e4d5b979f: Pull complete</p><p>{Digest: sha256:81d381f5008c082a37da97d8b08dd8b358dae7ecf49e62ce3ef1eeaefc4381bb</p><p>printf("Hello World!\n");Status: Downloaded newer image for homeassistant/home-assistant:latest</p><p>return 0;docker.io/homeassistant/home-assistant:latest</p><p>|}</p></li><li><p>Then compile and run '''hello_world.c'''you can use the following command to view the docker image of Home Assistant you just downloaded</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''gcc docker images homeassistant/home-o hello_world hello_world.cassistant'''</p><p>orangepi@orangepi:~$ '''./hello_world'''REPOSITORY TAG IMAGE ID CREATED SIZE</p><p>Hello World!homeassistant/home-assistant latest bfa0ab9e1cf5 2 months ago '''</pspan style="color:#FF0000">1.17GB</lispan>'''</olp>|}
</li>
<li><p>Ubuntu Focal has Python3 installed by defaultAt this point you can run the Home Assistant docker container</p><ol {| class="wikitable" style="list-style-typewidth: lower-alpha800px;"><li><p>The specific version of Python3 is as follows</p>|-| <p>orangepi@orangepi:~$ '''python3docker run -d \'''</p><p>Python 3.8.10 (default, Nov 14 2022, 12:59:47)</p><p>[GCC 9.4.0] on linux</p><p>Type "help", "copyright", "credits" or "license" for more information.</p><p>>>>'''--name homeassistant \'''</p>:<p>'''Use the Ctrl+D shortcut key to exit python's interactive mode.--privileged \'''</p></li><li>:<p>Write the '''hello_world.py--restart=unless-stopped \''' program in Python language</p>:<p>orangepi@orangepi:~$ '''vim hello_world.py-e TZ=Asia/Shanghai \'''</p>:<p>print('Hello World!')'-v /home/orangepi/home-assistant:/config \'''</p></li><li>:<p>The result of running '''hello_world.py--network=host \''' is as follows</p>:<p>orangepi@orangepi:~$ '''python3 hello_world.pyhomeassistant/home-assistant:latest'''</p><p>Hello World!</p></li></ol>|}
</li>
<li><p>Ubuntu Focal does not have Java compilation tools and running environment installed by default.Then enter【the IP address of the development board: 8123】in the browser to see the Home Assistant interface</p><ol {| class="wikitable" style="listbackground-style-typecolor:#ffffdc;width: lower-alpha800px;"><li><p>You can use the following command to install openjdk|-17| </pbig><p>orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''</p></li><li><p>After It takes a while for the Home Assistant container to start. If the interface below does not display normally, please wait a few seconds before refreshing it. If the following interface is not displayed normally after waiting for more than a minute, it means there is a problem with the Home Assistant installation. At this time, you can need to check whether there is a problem with the Java versionprevious installation and setting process.</p><p>orangepi@orangepi:~$ '''java --version'''</p><p>openjdk 17.0.2 2022-01-18</pbig>|}<pdiv class="figure">OpenJDK Runtime Environment (build 17.0.2+8 [[File:zero2w-Ubuntu-120img180.04)</p>png]] <p>OpenJDK 64-Bit Server VM (build 17.0.2+8-Ubuntu-120.04, mixed mode, sharing)</pdiv></li><li><p>Write the Java version of Then enter your '''name, username''' and '''hello_world.javapassword'''</p><p>orangepi@orangepi:~$ and click '''vim hello_world.javaCreate Account'''</p><p>public div class hello_world</p="figure"><p>{</p><p>public static void main(String[[File:zero2w-img181.png]] args) </pdiv><p>{</pli><p>System.out.println("Hello World!");</pli><p>}Then follow the interface prompts to set according to your own preferences, and then click Next</p><pdiv class="figure">} [[File:zero2w-img182.png]] </pdiv></li><li><p>Then compile and run '''hello_world.java'''click Next</p><pdiv class="figure">orangepi@orangepi [[File:~$ '''javac hello_worldzero2w-img183.java'''png]] </pdiv><p>orangepi@orangepi:~$ '''java hello_world'''</pli><pli>Hello World!</p>Then click Finish</li></olp></li></oldiv class="figure">
<ol style="list-style-type: decimal;"/div></li><li><p>Ubuntu Jammy The main interface finally displayed by Home Assistant is installed with the gcc compilation tool chain by default, which can directly compile C language programs in the Linux system of the development boardas shown below</p><p>[[File:zero2w-img185.png]]</p></li><li><p>Method to stop Home Assistant container</p>
<ol style="list-style-type: lower-alpha;">
<li><p>The version of a.gcc command to view the docker container is as follows</p><p>orangepi@orangepi{| class="wikitable" style="width:~$ '''gcc --version'''</p>800px;" <p>gcc (Ubuntu 11.3.0|-1ubuntu1~22.04.1) '''11.3.0'''</p><p>Copyright (C) 2021 Free Software Foundation, Inc.</p><p>This is free software; see the source for copying conditions. There is NO</p><p>warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</p></li><li><p>Write the '''hello_world.c''' program in C language</p>| <p>orangepi@orangepi:~$ '''vim hello_world.cdocker ps -a'''</p><p>#include <stdio.h></p><p>int main(void)</p><p>{</p><p>printf("Hello World!\n");</p><p>return 0;</p><p>|}</p></li><li><p>Then compile and run '''hello_world.c'''</p><p>orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''</p><p>orangepi@orangepi:~$ '''./hello_world'''</p><p>Hello World!</p></li></ol>
</li>
<li><p>Ubuntu Jammy has Python3 installed by defaultThe command to stop the Home Assistant container is as follows</p><ol {| class="wikitable" style="list-style-typewidth: lower-alpha800px;"><li><p>The specific version of Python3 is as follows</p><p>orangepi@orangepi:~$ '''python3'''</p><p>Python 3.10.6 (main, May 29 2023, 11:10:38) [GCC 11.3.0] on linux</p><p>Type "help", "copyright", "credits" or "license" for more information.</p><p>>>></p><p>'''Use the Ctrl+D shortcut key to exit python's interactive mode.'''</p></li><li><p>Write the '''hello_world.py''' program in Python language</p><p>orangepi@orangepi:~$ '''vim hello_world.py'''</p>|-<p>print('Hello World!')</p></li><li><p>The result of running '''hello_world.py''' is as follows</p>| <p>orangepi@orangepi:~$ '''python3 hello_world.pydocker stop homeassistant'''</p><p>Hello World!</p></li></ol>|}
</li>
<li><p>Ubuntu Jammy does not install Java compilation tools and operating environment by default.The command to delete the Home Assistant container is as follows</p><ol {| class="wikitable" style="list-style-typewidth: lower-alpha800px;"><li><p>You can use the following command to install openjdk|-18</p><p>orangepi@orangepi:~$ '''sudo apt install -y openjdk-18-jdk'''</p></li><li><p>After installation, you can check the Java version.</p><p>orangepi@orangepi:~$ '''java --version'''</p><p>openjdk 18.0.2-ea 2022-07-19</p><p>OpenJDK Runtime Environment (build 18.0.2-ea+9-Ubuntu-222.04)</p><p>OpenJDK 64-Bit Server VM (build 18.0.2-ea+9-Ubuntu-222.04, mixed mode, sharing)</p></li><li><p>Write the Java version of '''hello_world.java'''</p>| <p>orangepi@orangepi:~$ '''vim hello_world.javadocker rm homeassistant'''</p><p>public class hello_world</p><p>{</p><p>public static void main(String[] args)</p><p>{</p><p>System.out.println("Hello World!");</p><p>|}</p><p>}</p></li><li><p>Then compile and run '''hello_world.java'''</p><p>orangepi@orangepi:~$ '''javac hello_world.java'''</p><p>orangepi@orangepi:~$ '''java hello_world'''</p><p>Hello World!</p></li></ol>
</li></ol>
<span id="methodinstallation-ofvia-uploading-files-to-the-development-board-linux-systempython"></span>== Method of uploading files to the development board Linux system ==
<ol style="list-style-type: decimal;">
<li><p>Use the scp command to upload files to the Linux system of the development board in Ubuntu PC. The specific command is as followsFirst install dependency packages</p><ol {| class="wikitable" style="list-style-typewidth: lower-alpha800px;"><li>|-| <p>orangepi@orangepi:~$ '''file_path: sudo apt-get update'''Needs to be replaced with the path of the file to > be uploaded</p><p>orangepi@orangepi:~$ '''sudo apt-get install -y python3 python3-dev python3-venv \'''</lip><li><p>'''orangepi: python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential \'''This is the user name of the development board's > Linux system. It can also be replaced with something else, > such as root.</p><p>'''libopenjp2-7 libtiff5 libturbojpeg0-dev tzdata'''</lip>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <libig><p>'''192.168.xx.xxIf it is debian12, please use the following command:''' This is the IP address of the development > board. Please modify it according to the actual situation.</p></libig><li><p>orangepi@orangepi:~$ '''/home/orangepi:sudo apt-get update''' The path in the development board Linux > system can also be modified to other paths.</p><p>testorangepi@testorangepi:~$ '''scp file_path orangepi@192.168.xx.xx:/home/orangepisudo apt-get install -y python3 python3-dev python3-venv \'''</p><p>'''python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential \'''</p></lip>'''libopenjp2-7 libturbojpeg0-dev tzdata'''</olp>|}
</li>
<li><p>If Then you want need to compile and install Python3.9. For the method, please refer to the [[Orange Pi Zero 2W#Python related instructions|'''Python source code compilation and installation method''']] section.</p>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>'''The default Python version of Debian Bullseye is Python3.9, so there is no need to compile and install it.'''</p><p>'''The default Python version of Ubuntu Jammy is Python3.10, so there is no need to upload compile and install it.'''</p><p>'''The default Python version of Debian Bookworm is Python3.11, so there is no need to compile and install it.'''</p></big>|}</li><li><p>Then create a folderPython virtual environment</p>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>'''Debian Bookworm is python3.11, you need please remember to add replace the corresponding command.'''</p></big>|}{| class="wikitable" style="width:800px;" |-r parameter| <p>orangepi@orangepi:~$ '''sudo mkdir /srv/homeassistant'''</p><p>testorangepi@testorangepi:~$ '''scp -r dir_path sudo chown orangepi:orangepi /srv/homeassistant'''</p><p>orangepi@orangepi:~$ '''cd /srv/homeassistant'''</p><p>orangepi@192orangepi:~$ '''python3.1689 -m venv .xx.xx'''</p><p>orangepi@orangepi:~$ '''source bin/activate'''</p><p>(homeassistant) orangepi@orangepi:/srv/homeassistant$</p>|}</li><li><p>Then install the required Python packages</p>{| class="wikitable" style="width:800px;" |-| <p>(homeassistant) orangepi@orangepi:/homesrv/homeassistant$ '''python3 -m pip install wheel'''</p>|}</li><li><p>Then you can install Home Assistant Core</p>{| class="wikitable" style="width:800px;" |-| <p>(homeassistant) orangepi@orangepi:/srv/homeassistant$ '''pip3 install homeassistant'''</p>|}</li><li><p>There are more usages of scp, please use Then enter the following command to view run Home Assistant Core</p>{| class="wikitable" style="width:800px;" |-| <p>(homeassistant) orangepi@orangepi:/srv/homeassistant$ '''hass'''</p>|}</li><li><p>Then enter【'''development board IP address: 8123'''】 in the man manualbrowser to see the Home Assistant interface</p>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>'''When you run the hass command for the first time, some libraries and dependency packages necessary for operation will be downloaded, installed and cached. This process may take several minutes. Note that you cannot see the Home Assistant interface in the browser at this time. Please wait for a while and then refresh it.'''</lip></olbig>|}<div class="figure">
<span id="how-to-upload-files-using-filezilla"/div></li></spanol>==== How to upload files using filezilla ====
<ol stylespan id="listopencv-styleinstallation-type: decimal;method"><li><p>First install filezilla in Ubuntu PC</p><p>test@test:~$ '''sudo apt install -y filezilla'''</p></li><li><p>Then use the following command to open filezilla</p><p>test@test:~$ '''filezilla'''</p></li><li><p>The interface after opening filezilla is as shown below. At this time, the remote site on the right is empty.</p><div class="figure"span>
</divspan id="use-apt-to-install-opencv"></lispan><li><p>The method of connecting the development board is as shown in the figure below</p></li></ol>=== Use apt to install OpenCV ===
<div ol style="list-style-type: decimal;"><li><p>The installation command is as follows</p>{| class="figurewikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''sudo apt-get update'''</p><p>orangepi@orangepi:~$ '''sudo apt-get install -y libopencv-dev python3-opencv'''</p>|}</li><li><p>Then use the following command to print the version number of OpenCV. The output is normal, indicating that the OpenCV installation is successful.</p><ol style="list-style-type: lower-alpha;"><li><p>The version of OpenCV in Ubuntu22.04 is as follows:</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''python3 -c "import cv2; print(cv2.__version__)"'''</p><p>'''4.5.4'''</p>|}</li><li><p>The version of OpenCV in Ubuntu20.04 is as follows:</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''python3 -c "import cv2; print(cv2.__version__)"'''</p><p>'''4.2.0'''</p>|}</li><li><p>The version of OpenCV in Debian11 is as follows:</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''python3 -c "import cv2; print(cv2.__version__)"'''</p><p>'''4.5.1'''</p>|}</li><li><p>The version of OpenCV in Debian12 is as follows:</p>{| class="wikitable" style="width:800px;"|-| <p>orangepi@orangepi:~$ '''python3 -c "import cv2; print(cv2.__version__)"'''</p><p>'''4.6.0'''</p>|}</li></ol></li></ol>
<ol style="list-style-type: decimal;">
<li><p>First set the default '''locale''' to Chinese</p>
<ol style="list-style-type: lower-alpha;">
<li><p>Enter the following command to start configuring '''locale'''</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''</p>
|}
</li>
<li><p>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)</p>
<p>[[File:zero2w-img186.png]]</p></li>
<li><p>Then set the default '''locale''' to '''zh_CN.UTF-8'''</p>
<p>[[File:zero2w-img187.png]]</p></li>
<li><p>After exiting the interface, the '''locale''' setting will begin. The output displayed on the command line is as follows:</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''</p>
<p>Generating locales (this might take a while)...</p>
:<p>en_US.UTF-8... done</p>
:<p>zh_CN.UTF-8... done</p>
<p>Generation complete.</p>
|}
</li></ol>
</li>
<li><p>Then open '''Input Method'''</p>
<p>[[File:zero2w-img188.png]]</p></li>
<li><p>Then select '''OK'''</p>
<p>[[File:zero2w-img189.png]]</p></li>
<li><p>Then select '''Yes'''</p>
<p>[[File:zero2w-img190.png]]</p></li>
<li><p>Then select '''fcitx'''</p>
<p>[[File:zero2w-img191.png]]</p></li>
<li><p>Then select '''OK'''</p>
<p>[[File:zero2w-img192.png]]</p></li>
<li><p>'''<span style="color:#FF0000">Then restart the Linux system to make the configuration take effect.</span>'''</p></li>
<li><p>Then open '''Fcitx configuration'''</p>
<p>[[File:zero2w-img193.png]]</p></li>
<li><p>Then click the + sign as shown in the picture below</p>
<p>[[File:zero2w-img194.png]]</p></li>
<li><p>Then search '''Google Pinyin''' and click '''OK'''</p>
<div class="figure">
[[File:zero2w-img259img195.png]]
</div></li><li><p>Then put '''Google Pinyin''' on top</p><p>[[File:zero2w-img196.png]]</p><p>[[File:zero2w-img197.png]]</p></li><li><p>Then open the '''Geany''' editor to test the Chinese input method</p><p>[[File:zero2w-img198.png]]</p></li><li><p>The Chinese input method test is as follows</p><p>[[File:zero2w-img199.png]]</p></li><ol startli><p>You can switch between Chinese and English input methods through the '''Ctrl+Space''' shortcut key</p></li><li><p>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'''</p>{| class="8wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''sudo vim /etc/default/locale'''</p><p># File generated by update-locale</p><p>LC_MESSAGES='''<span style="listcolor:#FF0000">zh_CN.UTF-8</span>'''</p><p>LANG='''<span style="color:#FF0000">zh_CN.UTF-type8</span>'''</p><p>LANGUAGE='''<span style="color: decimal;#FF0000">zh_CN.UTF-8</span>'''</p>|}</li><li><p>Then select '''<span style="color:#FF0000">restart the path to be uploaded to system</span>''' and you will see that the development board on the right side of the filezilla software, select the file to be uploaded system is displayed in Ubuntu PC on the left side of the filezilla software, rightChinese.</p><p>[[File:zero2w-click the mouse, and then click the upload option to start uploading the file to the development boardimg200.png]]</p></li></ol>
<div classspan id="figureinstallation-method-of-ubuntu-20.04-system"></span>
<ol style="list-style-type: decimal;"><li><p>First open '''Language Support'''</p><p>[[File:zero2w-img201.png]]</p></li><li><p>Then find the '''Chinese (China)''' option</p><p>[[File:zero2w-img202.png]]</p></li><li><p>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:</p><p>[[File:zero2w-img203.png]]</p></li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that this step is not easy to drag, please be patient and try it a few times.'''</big>|}</divol><ol start="94" style="list-style-type: decimal;"><li><p>Then select '''Apply System-Wide''' to apply the Chinese settings to the entire system</p><p>[[File:zero2w-img204.png]]</p></li><li><p>Then set the '''Keyboard input method system''' system to '''fcitx'''</p><p>[[File:zero2w-img205.png]]</p></li><li><p>'''<span style="color:#FF0000">Then restart the Linux system to make the configuration take effect</span>'''</p></li><li><p>After re-entering the system, please select '''Do not ask me again''' in the upload is completedfollowing interface, and then please decide according to your own preferences whether the standard folder should also be updated to Chinese</p><p>[[File:zero2w-img206.png]]</p></li><li><p>Then you can go see that the desktop is displayed in Chinese</p><p>[[File:zero2w-img207.png]]</p></li><li><p>Then we can open '''Geany''' to test the corresponding path Chinese input method. The opening method is as shown in the development board Linux system to view the uploaded filefigure below</p><p>[[File:zero2w-img208.png]]</p></li><li><p>The After opening '''Geany''', the English input method of uploading a folder is still the same as default. We can switch to the Chinese input method of uploading a filethrough the '''Ctrl+Space''' shortcut key, so I won't go into details hereand then we can input Chinese.</p><p>[[File:zero2w-img209.png]]</p></li></ol>
<span id="installation-method-toof-uploadubuntu-files-from-windows-pc-to-development-board-linux22.04-system"></span>=== Method to upload files from Windows PC to development board Linux system ===
<ol style="list-style-type: decimal;">
<li><p>First open '''Language Support'''</p>
<p>[[File:zero2w-img201.png]]</p></li>
<li><p>Then find the '''Chinese (China)''' option</p>
<p>[[File:zero2w-img210.png]]</p></li>
<li><p>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:</p>
<p>[[File:zero2w-img211.png]]</p></li>
{| class="wikitable" style="background-color:#ffffdc;width:800px;"
|-
|
<big>'''Note that this step is not easy to drag, please be patient and try it a few times.'''</big>
|}
</ol>
<ol start="4" style="list-style-type: decimal;">
<li><p>Then select '''Apply System-Wide''' to apply the Chinese settings to the entire system</p>
<p>[[File:zero2w-img212.png]]</p></li>
<li><p>'''<span style="color:#FF0000">Then restart the Linux system to make the configuration take effect</span>'''</p></li>
<li><p>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.</p>
<p>[[File:zero2w-img206.png]]</p></li>
<li><p>Then you can see that the desktop is displayed in Chinese</p>
<p>[[File:zero2w-img207.png]]</p></li>
<li><p>Then open the Fcitx5 configuration program</p>
<p>[[File:zero2w-img213.png]]</p></li>
<li><p>Then choose to use Pinyin input method</p>
<div class="figure">
[[File:zero2w-img262img214.png]]
</div><ol start="2" style="list-style-type: decimal;"/li><li><p>The downloaded installation package interface after selection is as shown below, then doubleclick OK</p><p>[[File:zero2w-click to install it directlyimg215.png]]</p></li><li><p>Then we can open '''FileZilla_Server_1Geany''' to test the Chinese input method.5The opening method is as shown in the figure below</p><p>[[File:zero2w-img208.1_win64-setuppng]]</p></li><li><p>After opening '''Geany''', the English input method is still the default.exeWe can switch to the Chinese input method through the '''Ctrl+Space''' shortcut key, and then we can enter Chinese.</p><p>[[File:zero2w-img216.png]]</p></li></ol>
'''https://knowledgebase.nomachine.com/DT10R00166'''<div /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 NoMachine's official documentation.'''</big>|}{| class="figurewikitable"style="background-color:#ffffdc;width:800px;" |-| <big>'''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.'''</big>|}
<ol style="list-style-type: decimal;"><li><p>First download the installation package of the NoMachine software Linux '''<span style="color:#FF0000">arm64</span>''' deb version, and then install it into the Linux system of the development board</p><ol style="list-style-type: lower-alpha;"><li>Since H618 is an ARMv8 architecture SOC and the system we use is Ubuntu or Debian, we need to download the '''NoMachine for ARM ARMv8 DEB''' installation package. The download link is as follows:</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that this download link may change, please look for the Armv8/Arm64 version of the deb package.'''</big>|}{| class="wikitable" style="width:800px;" |-| [[Filehttps://www.nomachine.com/download/download&id=112&s=ARM '''https:zero2w-img264//downloads.nomachine.png]com/download/?id=118&distro=ARM''']|}
[[File:zero2w-img217.png]]</divol><ol start="42" style="list-style-type: decimallower-alpha;"><li>The method of connecting <p>In addition, you can also download the development board is as shown in '''NoMachine''' installation package from the figure belowofficial tool.</p><p>[[File:zero2w-img218.png]]</lip><p>First enter the '''remote login software-NoMachine''' folder</olp><p>[[File:zero2w-img219.png]]</p><div class="figure"p>Then download the arm64 version of the deb installation package</p> <p>[[File:zero2w-img256img220.png]]</p></li><li><p>Then upload the downloaded '''nomachine_x.x.x_x_arm64.deb''' to the Linux system of the development board</p></li><li><p>Then use the following command to install '''NoMachine''' in the Linux system of the development board</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''sudo dpkg -i nomachine_x.x.x_x_arm64_arm64.deb'''</divp>|}</li></ol></li></ol><ol start="52" style="list-style-type: decimal;"><li>Then choose to '''save download the installation package of the Windows version of the passwordNoMachine software. The download address is as follows</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>''' and click '''OKNote that this download link may change.'''</li></olbig>|}<div {| class="figurewikitable">style="width:800px;" |-| '''https://downloads.nomachine.com/download/?id=9'''|}
[[File:zero2w-img265img221.png]]</ol><ol start="3" style="list-style-type: decimal;"><li><p>Then install NoMachine in Windows. '''Please restart your computer after installation.'''</p></li><li><p>Then open '''NoMachine''' in Window</p><p>[[File:zero2w-img222.png]]</p></li><li><p>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.</p><p>[[File:zero2w-img223.png]]</p></li><li><p>Then click '''OK'''</p><p>[[File:zero2w-img224.png]]</p></li><li><p>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.</p><p>[[File:zero2w-img225.png]]</p></li><li><p>Then click OK in the next interface.</p></li><li><p>Finally you can see the desktop of the development board Linux system</p><p>[[File:zero2w-img226.png]]</p></li></ol>
</div><ol startspan id="6" style="listremote-login-styleusing-type: decimal;vnc"><li>Then select '''Always trust this host''' and click '''OK'''</li></olspan>
'''</div><ol start="7" span style="list-style-typecolor: decimal;#FF0000"><li>After the connection is successfulThere are many problems with VNC testing in Ubuntu20.04, you can see the directory structure of the development board's Linux file system on the right side of the filezilla softwareplease do not use this method.</lispan>'''</olbig>|}
<div ol style="list-style-type: decimal;"><li><p>First run the '''set_vnc.sh''' script to set up vnc, '''remember to add sudo permission'''s</p>{| class="figurewikitable" style="width:800px;"|-| <p>orangepi@orangepi:~$ '''sudo set_vnc.sh'''</p><p>You will require a password to access your desktops.</p>
</divp>Password: '''<ol startspan style="color:#FF0000">#Set the vnc password here, 8" characters</span>'''</p><p>Verify: '''<span style="list-style-typecolor: decimal;#FF0000">#Set the vnc password here, 8 characters</span>'''</p><lip>Then select the path to be uploaded to the development board on the right side of the filezilla software, select the file Would you like to be uploaded on the Windows PC on the left side of the filezilla software, rightenter a view-click the mouse, and then click the upload option to start uploading the file to the development board.only password (y/n)? '''<span style="color:#FF0000">n</span>'''</lip><p>xauth: file /root/.Xauthority does not exist</olp>
<span id="instructions-for-using-the-logo-on-and-off-the-machine"p>Creating default startup script /root/.vnc/xstartup</p><p>Starting applications specified in /root/.vnc/xstartup</spanp>== Instructions for using the logo on and off the machine ==<p>Log file is /root/.vnc/orangepi:1.log</p>
<span id="how-to-turn-on-the-power-button-in-linux5.4"p>Killing Xtightvnc process ID 3047</spanp>== How to turn on the power button in Linux5.4 ==
<span iddiv class="how-to-shut-down-and-restart-the-development-boardfigure"></span>== How to shut down and restart the development board ==
<span id/div></ol><ol start="2" style="linuxlist-sdkorangepistyle-buildtype: lower-usagealpha;"><li><p>Then enter the VNC password set earlier</p><p>[[File:zero2w-instructions"img228.png]]</p></li><li><p>After successful login, the interface is displayed as shown below, and then you can remotely operate the desktop of the development board Linux system.</p></spanli>
[[File:zero2w-img229.png]]</ol></li></ol><span id= '''Linux SDK——orangepi"qt-build usage instructions''' =installation-method"></span>
<ol style="list-style-type: decimal;">
<li><p>Use the following script to install QT5 and QT Creator</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>orangepi@orangepi:~$ '''install_qt.sh'''</p>
|}
</li>
<li><p>After installation, the QT version number will be automatically printed.</p>
<ol style="list-style-type: lower-alpha;">
<li>For the method of replacing Tsinghua Source, please refer to the instructions on this page.</lip></ol> [https://mirrorsThe qt version that comes with Ubuntu20.tuna.tsinghua.edu.cn/help/ubuntu/ 04 is '''https://mirrors5.tuna12.tsinghua.edu.cn/help/ubuntu/8''']</p> <ol start{| class="2wikitable" style="list-style-typewidth: lower-alpha800px;"><li>Note that the Ubuntu version needs to be switched to 22.04.</li></ol> [[File:zero2w|-img271.png]]| <ol start="3" style="list-style-type: lower-alpha;"><lip>The contents of the '''/etc/apt/sources.list''' file that need to be replaced are:</li></ol> testorangepi@testorangepi:~$ '''sudo mv /etc/apt/sources.list cat /etc/apt/sources.listinstall_qt.baksh''' test@test:~$ '''sudo vim </etc/apt/sources.list'''p> # The source code image is commented by default to improve apt update speed<p>. You can uncomment it yourself if necessary. deb https://mirrors.tuna.tsinghua.edu.cn</ubuntu/ jammy main restricted universe multiversep> # deb-src https://mirrors<p>QMake version 3.tuna.tsinghua.edu.cn1</ubuntu/ jammy main restricted universe multiversep> deb https<p>Using Qt version '''<span style="color://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse # deb-src https://mirrorsFF0000">5.tuna12.tsinghua.edu.cn8</ubuntuspan>''' in / jammy-updates main restricted universe multiverse deb https:usr/lib/mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammyaarch64-backports main restricted universe multiverse # deblinux-src https:gnu<//mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiversep>|}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 be enabled # 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 multiverseli><ol start="4" style="list-style-type: lower-alpha;"li><lip>After the replacement, you need to update the package information and ensure The QT version that no errors are reportedcomes with Ubuntu22.</li></ol> test@test:~$ 04 is '''sudo apt-get update5.15.3'''</p> <ol start{| class="5wikitable" style="list-style-typewidth: lower-alpha800px;">|-| <lip>orangepi@orangepi:~$ '''In addition, since the source code of the kernel and Uboot are stored on GitHub, it is very important to ensure that the computer can download the code from GitHub normally when compiling the imageinstall_qt.sh'''</lip><p>......</olp> <span id="obtain-the-source-code-of-linux-sdk"p>QMake version 3.1</spanp>== Obtain the source code of linux sdk == <p>Using Qt version '''<span idstyle="download-orangepi-build-from-githubcolor:#FF0000">5.15.3</span>=== Download orangepi-build from github === Linux sdk refers to the orangepi-build set of codes. Orangepi-build is modified based on the armbian build compilation system. Multiple versions of Linux images can be compiled using orangepi-build. Use the following command to download the orangepi-build code: test@test:~$ '''sudo apt-get update''' test@test:~$ '''sudo apt-get install -y git''' test@test:~$ '''git clone https:in /usr/github.comlib/orangepiaarch64-xunlong/orangepi-build.git linux-b next''' '''Note that when using the H618 Soc development board, you need 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.''' gnu<div class="figure"/p> [[File:zero2w-img272.png]]|}</divli><li><p>The QT version that comes with Debian11 is '''When downloading the orangepi-build code through the git clone command, you do not need to enter the user name and password of the github account (the same is true for downloading other codes in this manual)5. If after entering the git clone command, Ubuntu PC prompts you to enter the user name of the github account. The name and password are usually entered incorrectly in the address of the orangepi-build warehouse behind git clone. Please carefully check whether there are any errors in the spelling of the command, rather than thinking that we have forgotten to provide the username and password of the github account15.2''' The u-boot and linux kernel versions currently used by the H618 series development boards are as follows:</p>{| class="wikitable" style="width:800px;"
|-
| <p>orangepi@orangepi:~$ '''branchinstall_qt.sh'''</p>| <p>......</p><p>QMake version 3.1</p><p>Using Qt version '''u-boot Version<span style="color:#FF0000">5.15.2</span>'''in /usr/lib/aarch64-linux-gnu</p>| }</li><li><p>The QT version that comes with Debian12 is '''linux Kernel version5.15.8'''</p>{| class="wikitable" style="width:800px;"
|-
| <p>orangepi@orangepi:~$ '''install_qt.sh'''</p><p>......</p><p>QMake version 3.1</p><p>Using Qt version '''current<span style="color:#FF0000">5.15.8</span>'''in /usr/lib/aarch64-linux-gnu</p>| }</li></ol></li><li><p>Then you can see the QT Creator startup icon in '''uApplications'''</p><p>[[File:zero2w-boot v2018img230.05png]]</p><p>You can also use the following command to open QT Creator</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''qtcreator'''</p>| }</li><li><p>The interface after QT Creator is opened is as follows</p><p>[[File:zero2w-img231.png]]</p></li><li><p>The version of QT Creator is as follows</p><ol style="list-style-type: lower-alpha;"><li><p>The default version of QT Creator in '''Ubuntu20.04''' is as follows</p><p>[[File:zero2w-img232.png]]</p></li><li><p>The default version of QT Creator in '''Ubuntu22.04''' is as follows</p><p>[[File:zero2w-img233.png]]</p></li><li><p>The default version of QT Creator in '''Debian11''' is as follows</p><p>[[File:zero2w-img234.png]]</p></li><li><p>The default version of QT Creator in '''Debian12''' is as follows</p><p>[[File:zero2w-img235.png]]</p></li></ol></li><li><p>Then set up QT</p><ol style="list-style-type: lower-alpha;"><li><p>First open '''Help'''->'''About Plugins...'''linux5.4</p><p>[[File:zero2w-img236.png]]</p></li><li><p>Then remove the check mark of '''ClangCodeModel'''</p><p>[[File:zero2w-img237.png]]</p></li><li><p>'''<span style="color:#FF0000">After setting up, you need to restart QT Creator</span>'''</p></li><li><p>Then make sure the GCC compiler used by QT Creator. If the default is Clang, please change it to GCC.</p>{|class="wikitable" style="background-color:#ffffdc;width:800px;" | -| <big><p>'''nextDebian12 please skip this step.'''</p></big>| }<p>[[File:zero2w-img238.png]]</p><p>[[File:zero2w-img239.png]]</p></li></ol></li><li><p>Then you can open a sample code</p><p>[[File:zero2w-img240.png]]</p></li><li><p>After clicking on the sample code, the corresponding instruction document will automatically open. You can read the instructions carefully.</p><p>[[File:zero2w-img241.png]]</p></li><li><p>Then click '''uConfigure Project'''</p><p>[[File:zero2w-img242.png]]</p></li><li><p>Then click the green triangle in the lower left corner to compile and run the sample code</p><p>[[File:zero2w-img243.png]]</p></li><li><p>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.</p><p>[[File:zero2w-img244.png]]</p></li><li><p>References</p>{| class="wikitable" style="width:800px;" |-boot v2021| <p>[https://wiki.07qt.io/Install_Qt_5_on_Ubuntu '''https://wiki.qt.io/Install_Qt_5_on_Ubuntu''']</p>| <p>[https://download.qt.io/archive/qtcreator '''https://download.qt.io/archive/qtcreator''']</p><p>[https://download.qt.io/archive/qt '''linux6https://download.1qt.io/archive/qt''']</p>
|}
</li></ol>
::{| class="wikitable" style="width:800px;" |-| [http://docs.ros.org/ '''buildhttp://docs.sh external LICENSE READMEros.md scriptsorg''']
'''If you downloaded the orangepi-build code from github, after downloading, you may find that orangepi-build does not contain the source code of u-boot and linux kernel, and there is no cross-compilation tool required to compile u-boot and linux kernelhttps://wiki. chain, this is normal, because these things are stored in other separate github repositories or some servers (their addresses will be detailed below). Orangepi-build will specify the addresses of u-boot, Linux kernel and cross-compilation tool chain in the script and configuration file. When running orangepi-build, when it finds that these things are not available locally, it will automatically download them from the corresponding placesros.org/Distributions'''|}
<span idol start="2" style="downloadlist-style-type: decimal;"><li><p>The link to theofficial installation documentation of ROS 1 '''Noetic Ninjemys''' is as follows:</p>{| class="wikitable" style="width:800px;" |-cross-compilation-tool-chain| <p>[http://wiki.ros.org/noetic/Installation/Ubuntu '''http://wiki.ros.org/noetic/Installation/Ubuntu''']</p>|}</li><li><p>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 '''<span style="color:#FF0000">Ubuntu20.04 desktop system</span>'''.</p>{| class="wikitable" style="width:800px;" |-| <p>[http://wiki.ros.org/noetic/Installation '''http://wiki.ros.org/noetic/Installation''']</p><p>[[File:zero2w-img247.png]]</p>|}</li><li><p>Then use the script below to install ros1</p>{| class="wikitable" style= Download "width:800px;" |-| <p>orangepi@orangepi:~$ '''install_ros.sh ros1'''</p>|}</li><li><p>Before using the cross-compilation ROS tool chain , you first need to initialize rosdep. Then when compiling the source code, you can quickly install some system dependencies and some core components in ROS.</p></li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''<span style="color:#FF0000">Note that when running the following command, you need to ensure that the development board can access github normally, otherwise an error will be reported due to network problems.</span>'''
updated cache in /home/orangepi/.ros/rosdep/sources.cache|}</ol><ol start="26" style="list-style-type: decimal;"><li>Select <p>Then open a command line terminal window on the '''desktop''', and then use the '''test_ros.sh'''Uscript to start a small turtle routine to test whether ROS can be used normally.</p>{| class="wikitable" style="width:800px;" |-boot package| <p>orangepi@orangepi:~$ ''' and press Entertest_ros.sh'''</p>|}</li><li><p>After running the '''test_ros.sh''' script, a small turtle as shown in the picture below will pop up.</p><p>[[File:zero2w-img248.png]]</p></li><li><p>Then please keep the terminal window you just opened at the top</olp></li>
<div class="figure">
[[File:zero2w-img274img249.png]] </div></ol><ol start="9" style="list-style-type: decimal;"><li><p>At this time, press the direction keys on the keyboard to control the little turtle to move up, down, left, and right.</p><p>[[File:zero2w-img250.png]]</p></li></ol>
</div><ol startspan id="3" style="listhow-to-install-ros-2-galactic-styleon-type: decimal;ubuntu20.04"><li>Then select the model of the development board</li></olspan>
<ol start="4" style="list-style-type: decimal;"><li><p>Then select The currently active version of ROS 2 is as follows, the branch type of urecommended version is '''Galactic Geochelone'''</p><p>[[File:zero2w-bootimg251.png]]</p><ol p>[[File:zero2w-img252.png]]</p>{| class="wikitable" style="list-style-typewidth: lower-alpha800px;"|-| <p>[http://docs.ros.org/ '''http://docs.ros.org''']</p><p>'''http://docs.ros.org/en/galactic/Releases.html'''</p>|}</li><li><p>The current branch will compile link to the uofficial installation documentation of ROS 2 '''Galactic Geochelone''' is as follows:</p>{| class="wikitable" style="width:800px;" |-boot v2018| <p>'''docs.05 version code that needs to be used by the linux5ros.org/en/galactic/Installation.html'''</p><p>'''http://docs.ros.4 imageorg/en/galactic/Installation/Ubuntu-Install-Debians.html'''</p>|}</li><li><p>The next branch will compile In the u-boot v2021official installation documentation of ROS 2 '''Galactic Geochelone''', Ubuntu Linux recommends using Ubuntu20.07 version code 04, so please ensure that needs to be the system used by the linux6development board is the '''<span style="color:#FF0000">Ubuntu20.04 desktop system</span>'''.1 imageThere are several ways to install ROS 2. The following demonstrates how to install ROS 2 '''Galactic Geochelone''' through '''Debian packages'''.</p></li><li><p>[[File:zero2w-img276Use the '''install_ros.png]]sh''' script to install ros2</p>{| class="wikitable" style="width:800px;" |-| </lip>orangepi@orangepi:~$ '''install_ros.sh ros2'''</olp>|}
</li>
<li><p>The '''install_ros.sh''' script will automatically run the '''ros2 -h''' command after installing ros2. If you select the next branch, you will also be prompted to select can see the memory sizefollowing print, and you do not need to select it means that the current branchros2 installation is complete.</p>{| class="wikitable" style="width:800px;" |-| </lip>usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...</olp>
:<p>Call `ros2 <command> -h` for more detailed usage.</p>|}</li><li><p>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 ROS 2 can run normally.</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''test_ros.sh'''</p><p>[INFO] [1671174101.200091527] [talker]: Publishing: 'Hello World: 1'</p><p>[ oINFO] [1671174101.k235661048] [listener]: I heard: [Hello World: 1]</p><p>[INFO] [1671174102. 199572327] Target directory [ talker]: Publishing: 'Hello World: 2'</p><p>[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]</p><p>[INFO] [1671174103.199580322] [talker]: Publishing: 'Hello World: 3'</p><p>[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]</p>|}</li><li><p>Run the following command to open rviz2</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''source /opt/ros/galactic/setup.bash'''</p><p>orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''</p>|}<p>[[File:zero2w-buildimg253.png]]</outputp></debsli><li><p>For how to use ROS, please refer to the documentation of ROS 2.</up>{| class="wikitable" style="width:800px;" |-boot| <p>[http://docs.ros.org/en/galactic/Tutorials.html '''http://docs.ros.org/en/galactic/Tutorials.html''' ]</p>|}</li></ol>
<ol startspan id="4" style="listhow-to-install-ros-2-stylehumble-type: loweron-alpha;ubuntu22.04"><li>The package name of the compiled u-boot deb package</li></olspan>
<ol start="5" style="list-style-type: lower-alphadecimal;"><li>Compilation time<p>Use the install_ros.sh script to '''install_ros.sh'''</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''install_ros.sh ros2'''</p>|}</li><li><p>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.</p>{| class="wikitable" style="width:800px;" |-| <p>usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...</olp>
<ol start="6" style="list-style-type: lower-alpha;"><lip>Repeat the command to compile u-boot. Use the following ros2 is an extensible command without selecting through the graphical interface. You can start compiling u-boot directlyline tool for ROS 2.</li></olp>
<ol start="7" style="list-style-typep>optional arguments: decimal;"</p>:<lip>View the compiled u-boot deb package</li>h, --help show this help message and exit</olp>
:<blockquotep>Set Call `ros2 <command> -h` for more detailed usage.</p>|}</li><li><p>Then you can use the IGNORE_UPDATES variable in u'''userpatches/config-defaulttest_ros.confsh''' script to "yes"test whether ROS 2 is successfully installed. If you can see the following print, it means ROS 2 can run normally.</p>{| class="wikitable" style="width:800px;" |-| </blockquotep>testorangepi@testorangepi:~/orangepi-build$ '''vim userpatches/config-defaulttest_ros.confsh'''</p><p>[INFO] [1671174101.200091527] [talker]: Publishing: 'Hello World: 1'</p><p>[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: 1]</p><p>[INFO] [1671174102.199572327] [talker]: Publishing: 'Hello World: 2'</p><p>[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]</p><p>[INFO] [1671174103.199580322] [talker]: Publishing: 'Hello World: 3'</p><p>[INFO] [1671174103..204019965] [listener]: I heard: [Hello World: 3]</p>|}</li><li><p>Run the following command to open rviz2</p>IGNORE_UPDATES{| class=""wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''yessource /opt/ros/humble/setup.bash'''"</p><p>orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''</p><p>[[File:zero2w-img254......png]]</p>|}<ol start="9" style="list-style-type: decimal;"/li><li><p>When debugging u-boot code, you can use the following method to update u-boot in the linux image for testingReference documentation</p><ol {| class="wikitable" style="list-style-typewidth: lower-alpha800px;">|-| <lip>First upload the compiled deb package of u-boot to the Linux system of the development board'''http://docs.ros.org/en/humble/index.html'''</lip><p>[http://docs.ros.org/en/galactic/Tutorials.html '''http://docs.ros.org/en/humble/Installation/Ubuntu-Install-Debians.html''']</olp>|}
</li></ol>
{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''linux-u-boot-next-orangepizero2w_x.x.x_arm64.deb [mailtoDebian11 system with <span style="color:root@192.168#FF0000">Linux6.1.xxx:</root root@192span> kernel will report GCC error when compiling kernel module.168So if you want to compile the kernel module, please use Debian12 or Ubuntu22.104.xxx:/root]'''</big>|}
<ol start="2" style="list-style-type: lower-alphadecimal;"><li>Install <p>The Linux image released by OPi comes with the deb package of the kernel header file by default, and the new ustorage location is '''/opt/'''</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''ls /opt/linux-headers*'''</p><p>/opt/linux-boot headers-xxx-sun50iw9_x.x.x_arm64.deb package just uploaded</p>|}</li><li><p>Use the following command to install the deb package of the kernel header file</olp>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''sudo dpkg -i/opt/linux-headers*.deb''' </p>|}</li><li><p>After installation, you can see the folder where the kernel header file is located under '''/usr/src'''.</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''ls /usr/src'''</p><p>linux-uheaders-bootx.x.x</p>|}</li><li><p>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, then use the make command to compile.</p>{| class="wikitable" style="width:800px;" |-next| <p>orangepi@orangepi:~$ '''cd /usr/src/hello/'''</p><p>orangepi@orangepi:/usr/src/hello$ '''sudo make'''</p><p>make -orangepizero2w_xC /lib/modules/5.x4.125/build M=/usr/src/hello modules</p><p>make[1]: Entering directory '/usr/src/linux-headers-5.x_arm644.deb125'</p>:<p>CC [M] /usr/src/hello/hello.o</p>:<p>Building modules, stage 2.</p>:<p>MODPOST 1 modules</p>:<p>CC [M] /usr/src/hello/hello.mod.o</p>:<p>LD [M] /usr/src/hello/hello.ko</p><p>make[1]: Leaving directory '/usr/src/linux-headers-5.4.125'</p>|}<ol start/li><li><p>After compilation, the '''hello.ko''' kernel module will be generated</p>{| class="3wikitable" style="listwidth:800px;" |-| <p>orangepi@orangepi:/usr/src/hello$ '''ls *.ko'''</p><p>hello.ko</p>|}</li><li><p>Use the '''insmod''' command to insert the '''hello.ko''' kernel module into the kernel</p>{| class="wikitable" style="width:800px;" |-type| <p>orangepi@orangepi:/usr/src/hello$ '''sudo insmod hello.ko'''</p>|}</li><li><p>Then use the '''demsg''' command to view the output of the '''hello.ko''' kernel module. If you can see the following output, it means that the '''hello.ko''' kernel module is loaded correctly.</p>{| class="wikitable" style="width: lower800px;" |-alpha| <p>orangepi@orangepi:/usr/src/hello$ '''dmesg | grep ""Hello"'''</p><p>[ 2871.893988] '''Hello Orange Pi -- init'''</p>|}</li><li>Then run <p>Use the '''rmmod''' command to uninstall the nand'''hello.ko''' kernel module</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:/usr/src/hello$ '''sudo rmmod hello'''</p><p>orangepi@orangepi:/usr/src/hello$ '''dmesg | grep "Hello"'''</p><p>[ 2871.893988] Hello Orange Pi -sata-install scriptinit</p><p>[ 3173.800892] '''Hello Orange Pi -- exit'''</p>|}</li></ol>
<ol startstyle="5list-style-type: decimal;" ><li><p>Debian Bullseye is installed with the gcc compilation tool chain by default, which can directly compile C language programs in the Linux system of the development board.</p><ol style="list-style-type: lower-alpha;"><li>After pressing <p>The version of a.gcc is as follows</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''gcc --version'''</p><p>gcc (Debian 10.2.1-6) 10.2.1 20210110</p><p>Copyright (C) 2020 Free Software Foundation, Inc.</p><p>This is free software; see the Enter key, a Warning will pop up firstsource for copying conditions. There is NO</p><p>warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</p>|}</li><li><p>Write the '''hello_world.c''' program in C language</olp>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''vim hello_world.c'''</p><p>#include <stdio.h></p>
<ol start="6" style="list-style-type: lower-alpha;"p>int main(void)</p><lip>Press the Enter key again to start updating u-boot. After the update is completed, the following information will be displayed.{</lip>:<p>printf("Hello World!\n");</olp>
:<p>return 0;</p><p>}</p>|}<ol start/li><li><p>Then compile and run '''hello_world.c'''</p>{| class="wikitable" style="7width:800px;" |-| <p>orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''</p><p>orangepi@orangepi:~$ '''./hello_world'''</p><p>Hello World!</p>|}</li></ol></li><li><p>Debian Bullseye has Python3 installed by default</p><ol style="list-style-type: lower-alpha;"><li>Then you can restart the development board to test whether the u<p>The specific version of Python is as follows</p>{| class="wikitable" style="width:800px;" |-boot modification has taken effect| <p>orangepi@orangepi:~$ '''python3'''</p><p>'''Python 3.9.2''' (default, Feb 28 2021, 17:03:44)</lip><p>[GCC 10.2.1 20210110] on linux</olp><p>Type "help", "copyright", "credits" or "license" for more information.</p><span idp>>>></p>|}{| class="compilewikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>'''Use the-linux-kernel"Ctrl+D shortcut key to exit python's interactive mode.'''</p></big>|}</spanli>== Compile <li><p>Write the linux kernel '''hello_world.py''' program in Python language</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''vim hello_world.py'''</p><p>print('Hello World!')</p>|}# Run the </li><li><p>The result of running '''buildhello_world.shpy''' script, remember to add sudo permissionsis as follows</p>{| class="wikitable" style="width:800px;" |-| test<p>orangepi@testorangepi:~/orangepi-build$ '''sudo ./buildpython3 hello_world.shpy'''</p><p>Hello World!</p>|}</li></ol></li><li><p>Debian Bullseye does not install Java compilation tools and operating environment by default.</p><ol start="2" style="list-style-type: decimallower-alpha;"><li>Select <p>You can use the following command to install openjdk. The latest version in Debian Bullseye is openjdk-17</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''Kernel packagesudo apt install -y openjdk-17-jdk''' and press Enter</p>|}</li><li><p>After installation, you can check the Java version.</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''java --version'''</olp>|}<div /li><li><p>Write the Java version of '''hello_world.java'''</p>{| class="figurewikitable" style="width:800px;"|-| <p>orangepi@orangepi:~$ '''vim hello_world.java'''</p><p>public class hello_world</p><p>{</p>:<p>public static void main(String[[File] args)</p>:<p>{</p>::zero2w-img281<p>System.out.png]]println("Hello World!");</p>:<p>}</p><p>}</p>|}</divli><ol startli><p>Then compile and run '''hello_world.java'''</p>{| class="3wikitable" style="list-style-typewidth: decimal800px;"|-| <p>orangepi@orangepi:~$ '''javac hello_world.java'''</p><p>orangepi@orangepi:~$ '''java hello_world'''</p><p>Hello World!</p>|}</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.</ol></li></ol>
<ol style="list-style-type: decimal;">
<li><p>Debian Bookworm is installed with the gcc compilation tool chain by default, which can directly compile C language programs in the Linux system of the development board.</p>
<ol style="list-style-type: lower-alpha;">
<li>If you do <p>The version of a.gcc is as follows</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''gcc --version'''</p><p>gcc (Debian 12.2.0-14) 12.2.0</p><p>Copyright (C) 2022 Free Software Foundation, Inc.</p><p>This is free software; see the source for copying conditions. There is NO</p><p>warranty; not need to modify even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</p>|}</li><li><p>Write the kernel configuration options, when running the build'''hello_world.sh script, pass c'''KERNEL_CONFIGUREprogram in C language</p>{| class=no"wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ ''' to temporarily block the pop-up of the kernel configuration interfacevim hello_world.c'''</lip><p>#include <stdio.h></olp>
:<p>return 0;<ol start/p><p>}</p>|}</li><li><p>Then compile and run '''hello_world.c'''</p>{| class="7wikitable" style="listwidth:800px;" |-style| <p>orangepi@orangepi:~$ '''gcc -typeo hello_world hello_world.c'''</p><p>orangepi@orangepi: decimal;"~$ '''./hello_world'''</p><p>Hello World!</p>|}</li></ol></li><li><p>Part of the information prompted when compiling the next branch kernel source code is explained as follows:Debian Bookworm has Python3 installed by default</p>
<ol style="list-style-type: lower-alpha;">
<li>Version <p>The specific version of Python is as follows</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''python3'''</p><p>Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] on linux</p><p>Type "help", "copyright", "credits" or "license" for more information.</p><p>>>></p>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>'''Use the linux kernel source codeCtrl+D shortcut key to exit python's interactive mode.'''</lip></olbig>|}</li><li><p>Write the '''hello_world.py''' program in Python language</olp>{| class="wikitable" style="width:800px;" |-| [ o<p>orangepi@orangepi:~$ '''vim hello_world.kpy'''</p><p>print('Hello World!')</p>|}</li><li><p>The result of running '''hello_world. ] Compiling current kernel [ py''' is as follows</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''6.1python3 hello_world.31py''' ]</p><p>Hello World!</p>|}</li></ol></li><li><p>Debian Bookworm does not install Java compilation tools and operating environment by default.</p><ol start="2" style="list-style-type: lower-alpha;"><li><p>You can use the following command to install openjdk. The latest version of in Debian Bookworm is openjdk-17</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''</p>|}</li><li><p>After installation, you can check the crossJava version.</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''java --compilation tool chain usedversion'''</p>|}</li><li><p>Write the Java version of '''hello_world.java'''</olp>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''vim hello_world.java'''</p><p>public class hello_world</p><p>{</p>:<p>public static void main(String[ o] args)</p>:<p>{</p>::<p>System.kout. ] Compiler version [ println("Hello World!");</p>:<p>}</p><p>}</p>|}</li><li><p>Then compile and run '''hello_world.java'''aarch64</p>{| class="wikitable" style="width:800px;" |-linux-gnu-gcc 11| <p>orangepi@orangepi:~$ '''javac hello_world.java'''</p><p>orangepi@orangepi:~$ '''java hello_world''' ]</p><p>Hello World!</p>|}</li></ol></li></ol>
<ol startspan id="3" style="listubuntu-stylefocal-type: lower-alpha;system"><li>The default configuration file used by the kernel and the path where it is stored are as follows</li></olspan>
<ol startstyle="4list-style-type: decimal;" ><li><p>Ubuntu Focal is installed with the gcc compilation tool chain by default, which can directly compile C language programs in the Linux system of the development board.</p><ol style="list-style-type: lower-alpha;"><li><p>The path to version of a.gcc is as follows</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''gcc --version'''</p><p>gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0</p><p>Copyright (C) 2019 Free Software Foundation, Inc.</p><p>This is free software; see the source for copying conditions. There is NO</p><p>warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</p>|}</li><li><p>Write the kernel'''hello_world.c''' program in C language</p>{| class="wikitable" style="width:800px;" |-related deb package generated by compilation| <p>orangepi@orangepi:~$ '''vim hello_world.c'''</lip><p>#include <stdio.h></olp>
<ol start="5" style="list-style-type: lower-alpha;"p>int main(void)</p><lip>The package name of the kernel image deb package generated by compilation{</lip>:<p>printf("Hello World!\n");</olp>
:<ol start="6" style="list-style-type: lower-alphap>return 0;"</p><lip>Compilation time}</lip>|}</olli> [ o.k. ] Runtime [ <li><p>Then compile and run '''10 minhello_world.c''' ]</p> <ol start{| class="7wikitable" style="list-style-typewidth: lower-alpha800px;">|-| <lip>Finally, the compilation command to repeatedly compile the last selected kernel will be displayed. Use the following command without selecting through the graphical interface, and you can directly start compiling the kernel source codeorangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''</lip></olp> [ o.k. ] Repeat Build Options [ orangepi@orangepi:~$ '''sudo ./build.sh BOARD=orangepizero2w BRANCH=next BUILD_OPT=kernel KERNEL_CONFIGURE=nohello_world''' ]</p><p>Hello World!</p>|}</li></ol start="8" style="list-style-type: decimal;"></li><li><p>View the kernel-related deb package generated Ubuntu Focal has Python3 installed by compilationdefault</p>
<ol style="list-style-type: lower-alpha;">
<li><p>The specific version of Python3 is as follows</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''linux-dtb-next-sun50iw9_x.x.x_arm64.debpython3''' Contains dtb files used by the kernel</p><p>Python 3.8.10 (default, Nov 14 2022, 12:59:47)</lip><lip>[GCC 9.4.0] on linux</p><p>'''linux-headers-next-sun50iw9_xType "help", "copyright", "credits" or "license" for more information.x.x_arm64.deb''' Contains kernel header files</p><p>>>></lip>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <libig><p>'''linux-image-next-sun50iw9_x.x.x_arm64Use the Ctrl+D shortcut key to exit python's interactive mode.deb''' Contains kernel images and kernel modules</p></libig>|}</olli></li></olp> test@test:~/orangepi-build$ Write the '''ls output/debs/linux-*hello_world.py''' outputprogram in Python language</debs/linux-dtb-next-sun50iw9_x.x.x_arm64.deb output/debs/linux-headers-next-sun50iw9_x.x.x_arm64.debp> output/debs/linux-image-next-sun50iw9_x.x.x_arm64.deb <ol start{| class="9wikitable" style="list-style-typewidth: decimal800px;">|-| <lip>When the orangepi-bulid compilation system compiles the linux kernel source code, it will first synchronize the linux kernel source code with the linux kernel source code of the github server@orangepi:~$ '''vim hello_world. Therefore, if you want to modify the linux kernel source code, you first need to turn off the update function of the source code (py'''it needs to be completely compiled once This function can only be turned off after obtaining the Linux kernel source code, otherwise it will prompt that the source code of the Linux kernel cannot be found'</p><p>print('Hello World!'), otherwise the modifications will be restored. The method is as follows:</lip>|}</olli> <blockquoteli><p>Set the IGNORE_UPDATES variable in The result of running '''userpatches/config-defaulthello_world.confpy''' to "yes"is as follows</p>{| class="wikitable" style="width:800px;" |-| </blockquotep>testorangepi@testorangepi:~/orangepi-build$ '''vim userpatches/config-defaultpython3 hello_world.confpy'''</p><p>Hello World!</p>IGNORE_UPDATES="'''yes'''"|}</li></ol><ol start="10" style="list-style-type: decimal;"/li><li><p>If the kernel is modified, you can use the following method to update the kernel Ubuntu Focal does not have Java compilation tools and kernel module of the development board Linux systemrunning environment installed by default.</p>
<ol style="list-style-type: lower-alpha;">
<li>Upload the compiled deb package of <p>You can use the Linux kernel following command to the Linux system of the development boardinstall openjdk-17</lip>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''</olp>|}</li><li><p>After installation, you can check the Java version.</olp>{| class="wikitable" style="width:800px;" |-test| <p>orangepi@testorangepi:~/orangepi-build$ '''cd output/debsjava --version'''</p><p>openjdk 17.0.2 2022-01-18</p>test@test:~<p>OpenJDK Runtime Environment (build 17.0.2+8-Ubuntu-120.04)</orangepip><p>OpenJDK 64-Bit Server VM (build17.0.2+8-Ubuntu-120.04, mixed mode, sharing)</outputp>|}</debs$ li><li><p>Write the Java version of '''scp \hello_world.java'''</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''linux-image-next-sun50iw9_x.xvim hello_world.x_arm64.deb root@192.168.1.xxx:/rootjava'''</p><p>public class hello_world</p><p>{</p>:<p>public static void main(String[] args)</p>:<p>{<ol start="2" style="list-style-type/p>:: lower-alpha<p>System.out.println("Hello World!");"</p>:<lip>Install the deb package of the new linux kernel just uploaded.}</lip><p>}</olp>|}</li>orangepi@orangepi:~$ <li><p>Then compile and run '''sudo dpkg -i linux-image-next-sun50iw9_xhello_world.x.x_arm64.debjava'''</p> <ol start{| class="3wikitable" style="list-style-typewidth: lower-alpha800px;"><li>Then restart the development board and check whether the kernel|-related modifications have taken effect.| </li></olp> orangepi@orangepi:~$ '''sudojavac hello_world.java''' </p><p>orangepi@orangepi:~$ '''rebootjava hello_world'''</p><p>Hello World!</p>|}</li></ol></li></ol>
<span id="compileubuntu-rootfsjammy-system"></span>== Compile rootfs ==
<div class="figure"p>int main(void)</p><p>{</p>:<p>printf("Hello World!\n");</p>
:<p>return 0;</p><p>}</p>|}</divli><ol startli><p>Then compile and run '''hello_world.c'''</p>{| class="3wikitable" style="listwidth:800px;" |-style| <p>orangepi@orangepi:~$ '''gcc -typeo hello_world hello_world.c'''</p><p>orangepi@orangepi: decimal;"~$ '''./hello_world'''</p><lip>Hello World!</p>Then select the model of the development board|}</li></ol> [[File:zero2w-img275.png]] <ol start="4" style="list-style-type: decimal;"/li><li><p>Then select the branch type of the kernel source code. Different versions of the kernel source code maintain different rootfs types.Ubuntu Jammy has Python3 installed by default</p>
<ol style="list-style-type: lower-alpha;">
<li><p>In the current branchThe specific version of Python3 is as follows</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''python3'''</p><p>Python 3.10.6 (main, May 29 2023, you can see three options11:10: debian1138) [GCC 11.3.0] on linux</p><p>Type "help", ubuntu20.04"copyright", and ubuntu22"credits" or "license" for more information.04</p><p>>>></p>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big><p>'''Use the Ctrl+D shortcut key to exit python's interactive mode.'''</p></big>|}</li><li><p>In Write the next branch, you can see three options'''hello_world.py''' program in Python language</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi: debian11, debian12, and ubuntu22~$ '''vim hello_world.04py'''</p><p>print('Hello World!')</p>|}</li><li><p>The result of running '''hello_world.py''' is as follows</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''python3 hello_world.py'''</lip><p>Hello World!</olp>|}
</li></ol>
<ol style="list-style-type: lower-alpha;">
<li><p>You can use the following command to install openjdk-18</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''Image with console interface (server)sudo apt install -y openjdk-18-jdk''' Represents the image of the server version, which is relatively small in size.</p>|}</li><li><p>After installation, you can check the Java version.</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''Image with desktop environmentjava --version''' Represents an image with a desktop, which is relatively large in size</p><p>openjdk 18.0.2-ea 2022-07-19</p><p>OpenJDK Runtime Environment (build 18.0.2-ea+9-Ubuntu-222.04)</lip><p>OpenJDK 64-Bit Server VM (build 18.0.2-ea+9-Ubuntu-222.04, mixed mode, sharing)</olp>|}</li><li><p>Write the Java version of '''hello_world.java'''</olp> <div {| class="figurewikitable" style="width:800px;"|-| <p>orangepi@orangepi:~$ '''vim hello_world.java'''</p><p>public class hello_world</p><p>{</p>:<p>public static void main(String[[File] args)</p>:<p>{</p>::zero2w-img287<p>System.out.png]]println("Hello World!");</p>:<p>}</p><p>}</p>|}</divli><ol startli><p>Then compile and run '''hello_world.java'''</p>{| class="7wikitable" style="list-style-typewidth: decimal800px;"|-| <p>orangepi@orangepi:~$ '''javac hello_world.java'''</p><lip>If you are compiling the server version of the image, you can also choose to compile the Standard version or the Minimal version. The Minimal version will have much less pre-installed software than the Standard version (orangepi@orangepi:~$ '''please do not choose the Minimal version without special needs, because many things are not pre-installed by default. Some functions may not be availablejava hello_world''')</p><p>Hello World!</p>|}</li></ol></li></ol>
<div classspan id="figuremethod-of-uploading-files-to-the-development-board-linux-system"></span>
</div><ol startspan id="8" style="listmethod-to-upload-files-to-the-development-board-linux-system-in-styleubuntu-type: decimal;pc"><li/span>If you are compiling a desktop version of the image, you also need === Method to upload files to select the type of desktop environment. Currently, only XFCE is maintained, so please select an XFCE type desktop.</li></ol>development board Linux system in Ubuntu PC ===
<ol style="list-style-type: lower-alpha;">
<li>Type <p>'''file_path: '''Needs to be replaced with the path of the file to be uploaded</p></li><li><p>'''orangepi: '''This is the user name of the development board's Linux system. It can also be replaced with something else, such as root.</p></li><li><p>'''192.168.xx.xx:''' This is the IP address of rootfsthe development board. Please modify it according to the actual situation.</p></li><li><p>'''/home/orangepi:''' The path in the development board Linux system can also be modified to other paths.</p>{| class="wikitable" style="width:800px;" |-| <p>test@test:~$ '''scp file_path orangepi@192.168.xx.xx:/home/orangepi/'''</olp>|}
</li></ol>
</li>
<li><p>If you want to upload a folder, you need to add the -r parameter</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>test@test:~$ '''scp <span style="color:#FF0000">-r</span> dir_path orangepi@192.168.xx.xx:/home/orangepi/'''</p>
|}
</li>
<li><p>There are more usages of scp, please use the following command to view the man manual</p></li>
{| class="wikitable" style="width:800px;"
|-
|
test@test:~$ '''man scp'''
|}
</ol>
<span id="how-to-upload-files-using-filezilla"></span>
<ol start="3" style="list-style-type: lowerdecimal;"><li><p>First install filezilla in Ubuntu PC</p>{| class="wikitable" style="width:800px;" |-alpha| <p>test@test:~$ '''sudo apt install -y filezilla'''</p>|}</li><li><p>Then use the following command to open filezilla</p>{| class="wikitable" style="width:800px;"|-| <p>test@test:~$ '''filezilla'''</p>|}</li><li><p>The name of interface after opening filezilla is as shown below. At this time, the rootfs compressed package generated by compilationremote site on the right is empty.</lip></oldiv class="figure">
[ o.k. ] [File name [ '''bullseye:zero2w-xfce-arm64img255.5250ec7002de9e81a41de169f1f89721.tar.lz4''' png]]
<ol start="10" style="list-style-type: decimal;"/div></li><pli>View the compiled rootfs compressed package</p><ol style="list-style-type: lower-alpha;"><li>'''bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4''' It is a compressed package of rootfs. The meaning method of each field connecting the development board is as shown in the name isfigure below</li></olp></li></ol>
<blockquotediv class="figure">a) '''bullseye''' represents the type of Linux distribution of rootfs
</div></ol><ol start="118" style="list-style-type: decimal;"><li>If Then select the required rootfs already exists under '''external/cache/rootfs'''path to be uploaded to the development board on the right side of the filezilla software, then compiling select the rootfs again will directly skip file to be uploaded in Ubuntu PC on the compilation process and will not restart left side of the compilation. When compiling filezilla software, right-click the imagemouse, it will also go and then click the upload option to '''external/cache/rootfs''' start uploading the file to check whether it already exists. There is a cached rootfs available. If it is available, use it directly. This can save a lot of download and compilation timethe development board.</li></ol>
<span iddiv class="compile-linux-imagefigure"></span>== Compile linux image ==
<ol startspan id="2" style="listmethod-to-upload-files-from-windows-pc-to-development-board-stylelinux-type: decimal;system"><li>Select '''Full OS image for flashing''' and press Enter</li></olspan>
::{| class="wikitable" style="width:800px;" |-| [[Filehttps://filezilla-project.org/download.php?type=client '''https:zero2w//filezilla-img275project.png]org/download.php?type=client''']|}
::[[File:zero2w-img286img262.png]]
</div><ol start="72" style="list-style-type: decimal;"><li><p>Then select the type of imageThe downloaded installation package is as shown below, then double-click to install it directly</p><ol {| class="wikitable" style="list-style-typewidth: lower-alpha800px;"><li>|-| <p>'''Image with console interface (server)FileZilla_Server_1.5.1_win64-setup.exe''' Represents the image of the server version, which is relatively small in size.</p></li><li><p>|}During the installation process, please select '''Image with desktop environmentDecline'''Represents an image with a desktopon the following installation interface, which is relatively large in size.</p></li></ol></li></ol>and then select '''Next>'''
<div class="figure">
[[File:zero2w-img287img263.png]]
</div>
</li></ol><ol start="83" style="list-style-type: decimal;"><li>If you are compiling the server version of the imageThe interface after opening filezilla is as shown below. At this time, you can also choose to compile the Standard version or the Minimal version. The Minimal version will have much less pre-installed software than the Standard version ('''please do not choose remote site on the Minimal version without special needs, because many things are not pre-installed by defaultright is empty. Some functions may not be available''')</li></ol>
<div class="figure">
[[File:zero2w-img288img264.png]]
</div></ol><ol start="94" style="list-style-type: decimal;"><li>If you are compiling a desktop version The method of connecting the image, you also need to select development board is as shown in the type of desktop environment. Currently, only XFCE is maintained, so please select an XFCE type desktop.figure below:</li></ol>
[[File:zero2w-img290img256.png]]
[ o.k[File:zero2w-img269. png] Done building [ '''output/images/orangepizero2w_x.x.x_debian_bullseye_linux6.1.xx_xfce_desktop/orangepizero2w_x.x.x_debian_bullseye_linux6.1.xx_xfce_desktop.img''' ]
<ol style="list-style-type: decimal;"><li><p>First run '''orangepi-config'''. Ordinary users remember to add '''sudo''' permissions.</p>{| class="wikitable" style="width:800px;" |-| <p>orangepi@orangepi:~$ '''sudo orangepi-config'''</p>|}</li><li><p>Then select '''System'''</p><p>[ o[File:zero2w-img80.kpng]]</p></li><li><p>Then select '''Hardware'''</p><p>[[File:zero2w-img81. png] Runtime ]</p></li><li><p>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.</p><p>[[File:zero2w-img270.png]]</p></li><li><p>Then select '''<Save>''' to save</p><p>[[File:zero2w-img83.png]]</p></li><li><p>Then select '''<Back>'''</p><p>[ 19 min [File:zero2w-img84.png]]</p></li><li><p>Then select '''<Reboot>''' to restart the system to make the configuration take effect.</p><p>[[File:zero2w-img85.png]]</p></li></ol>
<ol startspan id="3" style="listhow-to-shut-down-and-restart-stylethe-type: lowerdevelopment-alpha;board"><li>Repeat the command to compile the image. Use the following command to start compiling the image directly without selecting it through the graphical interface.</li></olspan>
<span idol style="instructionslist-forstyle-using-the-orange-pi-os-arch-systemtype: decimal;"><li></spanp> = During the running of the Linux system, if you directly unplug the power supply, it may cause the file system to lose some data. It is recommended to use the '''Instructions for using the Orange Pi OS Arch systempoweroff''' = <span id="orange-pi-os-arch-command to shut down the Linux system-function-adaptation-status">of the development board before powering off, and then unplug the power supply.</spanp>== Orange Pi OS Arch system function adaptation status == {| class="wikitable" style="width:800px;"
|-
| <p>orangepi@orangepi:~$ '''Motherboard functionssudo poweroff'''</p>| '''OPi OS Arch'''}{| class="wikitable" style="background-color:#ffffdc;width:800px;"
|-
| <big><p>'''HDMI videoNote that after turning off the development board, you need to unplug and replug the power supply before it can be turned on.'''</p></big>|}</li><li><p>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.</p><p>[[File:zero2w-img269.png]]</p>{| '''OK'''class="wikitable" style="background-color:#ffffdc;width:800px;"
|-
| <big><p>'''HDMI AudioNote 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 [[Orange Pi Zero 2W#How to turn on the power button in Linux5.4|the method of opening the power button in Linux5.4]].'''</p></big>| '''OK'''}|-</li>| <li><p>Use the '''Type-C USB2.0 x 2reboot'''command to restart the Linux system in the development board</p>{| '''OK'''class="wikitable" style="width:800px;"
|-
| <p>orangepi@orangepi:~$ '''sudo'''''TF Card Startup'reboot'''</p>| }</li></ol> <span id="linux-sdkorangepi-build-usage-instructions"></span> = '''Linux SDK——orangepi-build usage instructions''' = <span id="compilation-system-requirements"></span>== Compilation system requirements == The Linux SDK, '''orangepi-build''OK', only supports running on X64 computers with '''<span style="color:#FF0000">Ubuntu 22.04</span>''' installed. Therefore, before downloading orangepi-build, please first ensure 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 '''<span style="color:#FF0000">22.04</span>''', it means that the Ubuntu version currently used does not meet the requirements. Please change the system before performing the following operations. {| class="wikitable" style="width:800px;"
|-
| test@test:~$ '''lsb_release -a''' No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04 LTS Release: '''<span style="color:#FF0000">22.04</span>''WIFI' Codename: '''jammy'''| } If the computer is installed with a Windows system and does not have Ubuntu 22.04 installed on it, you can consider using'''OKVirtualBox'''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 there is no guarantee that orangepi-build can be used normally in WSL. In addition, please do not compile the Linux system on the development board. Use orangepi-build. The installation image download address of Ubuntu 22.04 amd64 version is: {| class="wikitable" style="width:800px;"
|-
| [https://repo.huaweicloud.com/ubuntu-releases/21.04/ubuntu-21.04-desktop-amd64.iso '''Bluetoothhttps://mirrors.tuna.tsinghua.edu.cn/ubuntu-releases/22.04/ubuntu-22.04-desktop-amd64.iso''']| '''OK'''} After installing Ubuntu 22.04 on your computer or virtual machine, please first set the software source of Ubuntu 22.04 to Tsinghua source (or other domestic sources that you think is fast), otherwise it is easy to make errors due to network reasons when installing the software later. The steps to replace Tsinghua Source are as follows: <ol style="list-style-type: lower-alpha;"><li>For the method of replacing Tsinghua Source, please refer to the instructions on this page.</li> {| class="wikitable" style="width:800px;"
|-
| [https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/ '''LED Lighthttps://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/''']| }</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Note that the Ubuntu version needs to be switched to 22.04.</li> [[File:zero2w-img271.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The contents of the '''OK/etc/apt/sources.list'''file that need to be replaced are:</li>{| class="wikitable" style="width:800px;"
|-
| '''40pin GPIO'''| '''OK'''|-| '''40pin I2C'''| '''OK'''|-| '''40pin SPI'''| '''OK'''|-| '''40pin UART'''| '''OK'''|-| '''40pin PWM'test@test:~$ ''| 'sudo mv /etc/apt/sources.list cat /etc/apt/sources.list.bak''OK'''|-| '''Temperature Sensor'''| '''OK'''|-| '''Hardware watchdog'''| '''OK'''|-| '''Mali GPU'''| '''NO'''|-| '''Video codec'''| '''NO'''|}
'''#''' deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse|}</divol></liol start="4" style="list-style-type: lower-alpha;"><li>After the replacement, you need to update the package information and ensure that no errors are reported.<p/li>Then select the keyboard model{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt-get update'''|}</pol><div classol start="5" style="list-style-type: lower-alpha;"><li>'''<span style="figurecolor:#FF0000">In addition, since the source code of the kernel and Uboot are stored on GitHub, it is very important to ensure that the computer can download the code from GitHub normally when compiling the image.</span>'''</li></ol>
<div class="figure">
[[File:zero2w-img301img272.png|center|800px]]
</div></li>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <libig><p>The Orange Pi Hello program will automatically start after restarting. At this time'''When downloading the orangepi-build code through the git clone command, you do not need to remove enter the check '''mark user name and password of Start on startup''' the github account (the same is true for downloading other codes in this manual). If after entering the lower right cornergit clone command, otherwise Ubuntu PC prompts you need to manually close enter the user name of the github account. The name and password are usually entered incorrectly in the address of the orangepi-build warehouse behind git clone. Please carefully check whether there are any errors in the spelling of the command, rather than thinking that we have forgotten to provide the username and password of the Orange Pi Hello program every time you start itgithub account.'''</pbig><div class="figure">|}
<ol startspan id="2" style="listdownload-the-cross-compilation-styletool-type: decimal;chain"><li>Then open the corresponding configuration by adding '''FDTOVERLAYS''' '''/dtbs/allwinner/overlay/xxx.dtbo''' in '''/boot/extlinux/extlinux.conf'''</li></olspan>
{| class="wikitable" style="width:800px;" |-| [https://mirrors.tuna.tsinghua.edu.cn/armbian-releases/_toolchain/ '''FDTOVERLAYS https:/dtbs/allwinnermirrors.tuna.tsinghua.edu.cn/overlayarmbian-releases/_toolchain/xxx.dtbo''' #Configuration that needs to be added]|}
{| class="wikitable" style="width:800px;"
|-
| test@test:~/orangepi-build$ '''Functions on the development boardls 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-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 tool chain used to compile the H618 Linux kernel source code is: <ol style="list-style-type: lower-alpha;"><li>linux5.4</li>{| '''Corresponding DT overlays configuration'''class="wikitable" style="width:800px;"
|-
| '''40pin gcc-arm-11.2- i2c02022.02-x86_64-aarch64-none-linux-gnu'''| '''sun50i}</ol><ol start="2" style="list-h616style-pitype: lower-i2c0alpha;"><li>linux6.dtbo'''1</li>{| class="wikitable" style="width:800px;"
|-
| '''40pin gcc-arm-11.2- i2c12022.02-x86_64-aarch64-none-linux-gnu'''| '''sun50i}</ol>The cross-compilation tool chain used to compile the H618 u-boot source code is: <ol style="list-h616style-pitype: lower-i2c1alpha;"><li>v2018.dtbo'''05</li>{| class="wikitable" style="width:800px;"
|-
| '''40pin gcc-linaro-7.4.1-2019.02- i2c2x86_64_arm-linux-gnueabi'''| '''sun50i}</ol><ol start="2" style="list-h616style-pitype: lower-i2c2alpha;"><li>v2021.dtbo'''07</li>{| class="wikitable" style="width:800px;"
|-
| '''40pin gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux- uart2gnu'''| '''sun50i}</ol><span id="orangepi-build-complete-directory-structure-description"></span> === orangepi-build complete directory structure description === <ol style="list-style-type: decimal;"><li><p>After downloading, the orangepi-build warehouse does not contain the source code of the linux kernel, u-boot and cross-compilation tool chain. The source code of the linux kernel and u-boot is stored in an independent git warehouse.</p><ol style="list-style-type: lower-alpha;"><li><p>The git warehouse where the linux kernel source code is stored is as follows. Please note that the branch of the linux-h616orangepi warehouse is switched to</p><ol style="list-pistyle-uart2type: none;"><li>a) Linux5.dtbo'''4</li>{| class="wikitable" style="width:800px;"
|-
| https://github.com/orangepi-xunlong/linux-orangepi/tree/'''40pin orange-pi- uart35.4-sun50iw9'''| '''sun50i}</ol><ol start="2" style="list-h616style-pitype: lower-uart3alpha;"><li>b) Linux6.dtbo'''1</li>{| class="wikitable" style="width:800px;"
|-
| https://github.com/orangepi-xunlong/linux-orangepi/tree/'''40pin orange-pi-6.1- uart4sun50iw9'''| '''sun50i}</ol></li></ol><ol start="2" style="list-style-type: lower-alpha;"><li><p>The git warehouse where the u-boot source code is stored is as follows. Please note that the branch of the u-boot-orangepi warehouse is switched to</p><ol style="list-h616style-pitype: lower-uart4alpha;"><li>a) v2018.dtbo'''05</li>{| class="wikitable" style="width:800px;"
|-
| https://github.com/orangepi-xunlong/u-boot-orangepi/tree/'''40pin v2018.05- uart5h618'''| '''sun50i}</ol><ol start="2" style="list-h616style-phtype: lower-uart5alpha;"><li>b) v2021.dtbo'''07</li>{| class="wikitable" style="width:800px;"
|-
| https://github.com/orangepi-xunlong/u-boot-orangepi/tree/'''40pin v2021.07- pwm1sunxi'''| }</ol></li></ol></li></ol><ol start="2" style="list-style-type: decimal;"><li><p>When orangepi-build is run for the first time, it will download the cross-compilation tool chain, u-boot and linux kernel source code. After successfully compiling a linux image, the files and folders that can be seen in orangepi-build are:</p><ol style="list-style-type: lower-alpha;"><li><p>'''build.sh''': Compile startup script</p></li><li><p>'''external''': Contains the configuration files needed to compile the image, scripts for specific functions, and the source code of some programs. The rootfs compressed package cached during the image compilation process is also stored in external.</p></li><li><p>'''kernel''': Store the source code of the linux kernel</p></li><li><p>'''sun50iLICENSE''': GPL 2 license file</p></li><li><p>'''README.md''': orangepi-h616build documentation</p></li><li><p>'''output''': Store compiled u-piboot, linux and other deb packages, compilation logs, and compiled images and other files</p></li><li><p>'''scripts''': Common script for compiling linux images</p></li><li><p>'''toolchains''': Store cross-compilation tool chain</p></li><li><p>'''u-pwm1.dtboboot''': Store the source code of u-boot</p></li><li><p>'''userpatches''': Store the configuration files needed to compile the script</p></li>{| class="wikitable" style="width:800px;"
|-
| '''40pin - pwm2'''| '''sun50i-h616-pi-pwm2.dtbo'''|test@test:~/orangepi-| build$ '''40pin - pwm3ls'''| '''sun50i-h616-pi-pwm3.dtbo'''|-| '''40pin - pwm4'''| '''sun50i-h616-pi-pwm4build.dtbo'''|-| '''40pin - spi1 cs0'''| '''sun50i-h616-spi1-cs0-spidevsh external kernel LICENSE output README.dtbo'''|md scripts toolchains u-| '''40pin - spi1 cs1'''| '''sun50i-h616-spi1-cs1-spidev.dtbo'''|-| '''40pin - spi1 cs0 cs1'''| '''sun50i-h616-spi1-cs0-cs1-spidev.dtbo'''|-| '''设Set USB0 to Host mode'''| '''sun50i-h616-usb0-host.dtbo'''|-| '''Turn off the green LED light'''| '''sun50i-h616-zero2w-disable-led.dtbo'''|-| '''How to close the UART0 debugging serial port'''| '''sun50i-h616-disable-uart0.dtboboot userpatches'''
|}
</ol>
</li></ol>
<ol startspan id="5" style="listcompile-styleu-type: decimal;boot"><li>If you need to open multiple configurations at the same time, just add the paths of multiple configurations directly after '''FDTOVERLAYS.''' For example, the configuration of opening i2c1 and uart5 at the same time is as follows</li></olspan>
[[File:zero2w-img275.png]]<span id/ol><ol start="4" style="how-tolist-installstyle-softwaretype: decimal;"><li><p>Then select the branch type of u-boot</spanp><ol style== How to install software =="list-style-type: lower-alpha;"> You can use <li><p>The current branch will compile the pacman package management tool u-boot v2018.05 version code that needs to install software that is not available in OPi OSbe used by the linux5.4 image. For example, </p></li><li><p>The next branch will compile the command u-boot v2021.07 version code that needs to install be used by the vim editor is as followslinux6.1 image.</p><p>[[File:zero2w-img276. png]]</p></li></ol></li><li><p>If you want select the next branch, you will also be prompted to install other softwareselect the memory size, and you only do not need to replace vim with select the package name current branch.</p><ol style="list-style-type: lower-alpha;"><li><p>If the development board you purchased has a memory size of 1.5GB, please select the first option.</p></li><li><p>If the software development board you want to installpurchased has 1GB or 2GB or 4GB memory size, please choose the second option.</p> <p>[[orangepi@orangepiFile:zero2w-pc ~img277.png]$ '''sudo pacman -Syy vim''']</p></li></ol></li></ol><span idol start="6" style="android-12-tvlist-systemstyle-usage-instructionstype: decimal;"><li><p>Then it will start to compile u-boot. Some of the information prompted when compiling the next branch is as follows:</spanp> = '''Android 12 TV system usage instructions''' = <span idol style="supportedlist-style-androidtype: lower-versionsalpha;"><li>Version of u-boot source code</spanli>== Supported Android versions == {| class="wikitable" style="width:800px;"
|-
| Android [ o.k. ] Compiling u-boot [ '''v2021.07''' ]|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Versionof the cross-compilation tool chain</li>{| Kernel versionclass="wikitable" style="width:800px;"
|-
| '''Android 12 TV Version'''| [ o.k. ] Compiler version [ '''linux5.4aarch64-linux-gnu-gcc 11''']
|}
</ol><span idol start="android3" style="list-12style-tvtype: lower-function-adaptation-statusalpha;"><li>Path to the compiled u-boot deb package</spanli>== Android 12 TV function adaptation status == {| class="wikitable" style="width:800px;"
|-
| [ o.k. ] Target directory [ '''Motherboard functionsorangepi-build/output/debs/u-boot''']|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>The package name of the compiled u-boot deb package</li>{| '''Android12 TV'''class="wikitable" style="width:800px;"
|-
| [ o.k. ] File name [ '''HDMI videolinux-u-boot-next-orangepizero2w_x.x.x_arm64.deb''']|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Compilation time</li>{| '''OK'''class="wikitable" style="width:800px;"
|-
| [ o.k. ] Runtime [ '''HDMI Audio1 min''']|}</ol><ol start="6" style="list-style-type: lower-alpha;"><li>Repeat the command to compile u-boot. Use the following command without selecting through the graphical interface. You can start compiling u-boot directly.</li>{| '''OK'''class="wikitable" style="width:800px;"
|-
| [ o.k. ] Repeat Build Options [ '''Typesudo ./build.sh BOARD=orangepizero2w BRANCH=next BUILD_OPT=u-C USB2.0 x 2boot''']| '''OK'''}</ol></li></ol><ol start="7" style="list-style-type: decimal;"><li>View the compiled u-boot deb package</li>{| class="wikitable" style="width:800px;"
|-
| test@test:~/orangepi-build$ '''ls output/debs/u-boot/''' '''TF card startuplinux-u-boot-next-orangepizero2w_x.x.x_arm64.deb'''| }</ol><ol start="8" style="list-style-type: decimal;"><li>When the orangepi-bulid compilation system compiles the u-boot source code, it will first synchronize the u-boot source code with the u-boot source code of the github server. Therefore, 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. ('''OKYou need to completely compile u-boot before you can turn off this function, otherwise it will prompt that the source code of u-boot cannot be found'''), otherwise the modifications will be restored. The method is as follows:</li> Set the IGNORE_UPDATES variable in u'''userpatches/config-default.conf''' to "yes" {| class="wikitable" style="width:800px;"
|-
| test@test:~/orangepi-build$ '''WIFIvim userpatches/config-default.conf'''| ...... IGNORE_UPDATES="'''OK<span style="color:#FF0000">yes</span>'''" ......|}</ol><ol start="9" style="list-style-type: decimal;"><li><p>When debugging u-boot code, you can use the following method to update u-boot in the linux image for testing</p><ol style="list-style-type: lower-alpha;"><li>First upload the compiled deb package of u-boot to the Linux system of the development board.</li>{| class="wikitable" style="width:800px;"
|-
| test@test:~/orangepi-build$ '''cd output/debs/u-boot''' test@test:~/orangepi_build/output/debs/u-boot$ '''Bluetoothscp \'''| '''OKlinux-u-boot-next-orangepizero2w_x.x.x_arm64.deb [mailto:root@192.168.1.xxx:/root root@192.168.1.xxx:/root]'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Install the new u-boot deb package just uploaded</li>{| class="wikitable" style="width:800px;"
|-
| orangepi@orangepi:~$ '''USB Camerasudo dpkg -i'''| '''OKlinux-u-boot-next-orangepizero2w_x.x.x_arm64.deb'''|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then run the nand-sata-install script</li>{| class="wikitable" style="width:800px;"
|-
| orangepi@orangepi:~$ '''LED Lightsudo nand-sata-install'''| }</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then select '''OK5 Install/Update the bootloader on SD/eMMC'''</li> |[[File:zero2w-img278.png]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li>After pressing the Enter key, a Warning will pop up first.</li> [[File:zero2w-img279.png]]</ol><ol start="6" style="list-style-type: lower-alpha;"><li>Press the Enter key again to start updating u-boot. After the update is completed, the following information will be displayed.</li> [[File:zero2w-img280.png]]</ol><ol start="7" style="list-style-type: lower-alpha;"><li>Then you can restart the development board to test whether the u-boot modification has taken effect.</li></ol></li></ol><span id="compile-the-linux-kernel"></span> | == Compile the linux kernel == # Run the '''40pin GPIObuild.sh'''script, remember to add sudo permissions ::{| '''OK'''class="wikitable" style="width:800px;"
|-
| '''40pin I2C'''| '''OK'''|-| '''40pin SPI1'''| '''OK'''|test@test:~/orangepi-| '''40pin UART'''| '''OK'''|-| '''40pin PWM'''| '''OK'''|-| '''Temperature Sensor'''| '''OK'''|-| '''Hardware watchdog'''| '''OK'''|-| '''Mali GPU'''| '''OK'''|-| '''Video codec'''| build$ '''OKsudo ./build.sh'''
|}
[[File:zero2w-img282.png]]</ol><span idol start="onboard4" style="list-ledstyle-light-display-instructionstype: decimal;"><li>Then select the model of the development board</spanli>== Onboard LED light display instructions ==
::[[File:zero2w-img276.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>If you have purchased choose to display the infrared remote control kernel configuration menu (other remote controls do not workthe second option) in step 3) and a 24pin expansion board that come with the development board, after connecting the 24pin expansion board to the development boardkernel configuration interface opened through '''make menuconfig''' will pop up. At this time, you can also use directly modify the return key on the remote control to return to the previous menukernel configuration. After modification, save and exit. The location Yes, compilation of the return key is as shown belowkernel source code will begin after exiting. Shown:</li>
[[File:zero2w-img303img283.png]]
<span idol style="howlist-tostyle-usetype: lower-adbalpha;"><li>If you do not need to modify the kernel configuration options, when running the build.sh script, pass '''KERNEL_CONFIGURE=no''' to temporarily block the pop-up of the kernel configuration interface.</spanli>{| class="wikitable" style= How to use ADB ="width:800px;" |-| test@test:~/orangepi-build$ '''sudo ./build.sh KERNEL_CONFIGURE=no'''|}<span id/ol><ol start="2" style="uselist-networkstyle-connectiontype: lower-alpha;"><li><p>b. You can also set '''KERNEL_CONFIGURE=no''' in the orangepi-adbbuild/userpatches/config-debugging"default.confconfiguration file to permanently disable this function.</p></spanli>=== Use network connection adb debugging ===<li><p>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.</p></li>
output/debs/linux-image-next-sun50iw9_x.x.x_arm64.deb|}</ol></li></ol><ol start="59" style="list-style-type: decimal;"><li>Then When the orangepi-bulid compilation system compiles the linux kernel source code, it will first synchronize the linux kernel source code with the linux kernel source code of the github server. Therefore, if you want to modify the linux kernel source code, you first need to turn off the update function of the source code ('''it needs to be completely compiled once This function can log in to only be turned off after obtaining the Linux kernel source code, otherwise it will prompt that the source code of the Linux kernel cannot be found'''), otherwise the android system through adb shell on Ubuntu PCmodifications will be restored. The method is as follows:</li></ol>
IGNORE_UPDATES="'''<span idstyle="usecolor:#FF0000">yes</span>'''"|}</ol><ol start="10" style="list-data-cablestyle-type: decimal;"><li><p>If the kernel is modified, you can use the following method toupdate the kernel and kernel module of the development board Linux system</p><ol style="list-connectstyle-adbtype: lower-debuggingalpha;"><li>Upload the compiled deb package of the Linux kernel to the Linux system of the development board</spanli>{| class="wikitable" style== Use data cable to connect adb debugging ==="width:800px;" |-| test@test:~/orangepi-build$ '''cd output/debs'''
::{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''sudo apt-get install -y adb./build.sh'''|}
<ol start="32" style="list-style-type: decimal;"><li>Check whether the ADB device is recognizedSelect '''Rootfs and all deb packages''' and press Enter</li></ol>
[[File:zero2w-img275.png]]
</ol>
<ol start="4" style="list-style-type: decimal;">
<li><p>Then select the branch type of the kernel source code. Different versions of the kernel source code maintain different rootfs types.</p><ol style="list-style-type: lower-alpha;"><li><p>In the current branch, you can log in to see three options: debian11, ubuntu20.04, and ubuntu22.04.</p></li><li><p>In the android system through adb shell on Ubuntu PCnext branch, you can see three options: debian11, debian12, and ubuntu22.04.</lip></olli>
<span iddiv class="view-how-to-set-hdmi-display-resolutionfigure"></span>== View how to set HDMI display resolution ==
</li></ol>
<ol start="7" style="list-style-type: decimal;">
<li>If you are compiling the server version of the image, you can also choose to compile the Standard version or the Minimal version. The Minimal version will have much less pre-installed software than the Standard version ('''please do not choose the Minimal version without special needs, because many things are not pre-installed by default. Some functions may not be available''')</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. Determine whether rootfs needs to be recompiled</ol><ol start="52" style="list-style-type: decimallower-alpha;"><li>After selecting the WI'''bullseye-xfce-FI you want to connect to, arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4.list''' Lists the password input interface shown below will pop up.package names of all packages installed by rootfs</li><{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''ls external/cache/rootfs/ol>'''
bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4.list|}</divol></li></ol><ol start="611" style="list-style-type: decimal;"><li>Then use If the keyboard to enter required rootfs already exists under '''external/cache/rootfs''', then compiling the password corresponding to rootfs again will directly skip the WI-FI, compilation process and then use will not restart the mouse to click compilation. When compiling the Enter button on the virtual keyboard image, it will also go to start connecting '''external/cache/rootfs''' to the WI-FIcheck whether it already exists. There is a cached rootfs available. If it is available, use it directly. This can save a lot of download and compilation time.</li></ol>
<div classspan id="figurecompile-linux-image"></span>
<span idol start="how-to-use-wi2" style="list-fistyle-hotspottype: decimal;"><li>Select '''Full OS image for flashing''' and press Enter</spanli>== How to use WI-FI hotspot ==
[[File:zero2w-img306img292.png]]
</div></ol>
<ol start="3" style="list-style-type: decimal;">
<li>Then select '''Network & Internet'''the model of the development board</li></ol> [[File:zero2w-img314.png]]
[[File:zero2w-img275.png]]
</ol>
<ol start="4" style="list-style-type: decimal;">
<li><p>Then select '''WIFI hotspot'''the branch type of the kernel source code. Different versions of the kernel source code maintain different rootfs types.</p><ol style="list-style-type: lower-alpha;"><li><p>In the current branch, you can see three options: debian11, ubuntu20.04, and ubuntu22.04.</olp></li> [[File<li><p>In the next branch, you can see three options:zero2w-img320debian11, debian12, and ubuntu22.04.png]]</p></li>
[[File:zero2w-img276.png]]
</ol>
</li></ol>
<ol start="5" style="list-style-type: decimal;">
<li>Then open '''Hotspot Enable'''. You can <p>If you select the next branch, you will also see be prompted to select the name memory size, and password of you do not need to select the generated hotspot in the picture belowcurrent branch. Remember them and use them when connecting to </p><ol style="list-style-type: lower-alpha;"><li><p>If the hotspot (if development board you need to modify the name and password purchased has a memory size of 1.5GB, please select the hotspot, you need to close Hotspot Enable firstoption. Then </p></li><li><p>If the development board you can modify it)purchased has 1GB or 2GB or 4GB memory size, please choose the second option.</p><p>[[File:zero2w-img277.png]]</p></li></ol></li><li><p>Then select the type of rootfs</p></li>
[[File:zero2w-img321img286.png]]</ol><ol start="7" style="list-style-type: decimal;"><li><p>Then select the type of image</p><ol style="list-style-type: lower-alpha;"><li><p>'''Image with console interface (server)''' Represents the image of the server version, which is relatively small in size.</p></li><li><p>'''Image with desktop environment'''Represents an image with a desktop, which is relatively large in size.</p></li>
<ol startdiv class="6figure" style="list-style-type: decimal;"><li>At this time, you can take out your mobile phone. If everything is normal, you can find the WIFI hotspot with the same name ('''here AndroidAP_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:zero2w-img322img287.png]]
</div></ol></li></ol><ol start="78" style="list-style-type: decimal;"><li>After If you are compiling the connection is successful, it will be displayed as shown below (server version of the interface will be different on different mobile phones, the specific interface is subject to the one displayed on your mobile phone). At this timeimage, you can open a web page on your mobile phone also choose to see if you can access compile the Standard version or the InternetMinimal version. If the web page can be opened normally, it means that The Minimal version will have much less pre-installed software than the Standard version ('''WIplease do not choose the Minimal version without special needs, because many things are not pre-FI Hotspotinstalled by default. Some functions may not be available''' of the development board can be used normally.)</li></ol>
[[File:zero2w-img107img289.png]]
::o. Finally, write the bin file of u-boot into the image through the dd command.
</ol>
<ol start="11" style="list-style-type: decimal;">
<li><p>After compiling the image, the following message will be displayed</p>
<ol style="list-style-type: lower-alpha;">
<li>Run The storage path of the compiled image</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Done building [ '''output/images/orangepizero2w_x.x.x_debian_bullseye_linux6.1.xx_xfce_desktop/orangepizero2w_x.x.x_debian_bullseye_linux6.1.xx_xfce_desktop.img''' ]|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Compilation time</li>{| class="wikitable" style="width:800px;" |-| '''[ o.k. ] Runtime [ 19 min ]'''|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Repeat the command to compile the image. Use the following command to set USB0 to HOST modestart compiling the image directly without selecting it through the graphical interface.</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepizero2w BRANCH=next BUILD_OPT=image RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=yes''' ]|}</ol></li></ol><span id="instructions-for-using-the-orange-pi-os-arch-system"></span>
<ol startspan id="3" style="listorange-pi-os-arch-system-styleuser-type: lowerguide-alpha;instructions"><li>The command to view the current mode of USB0 is</li></olspan>
</devdiv></video0li><li><p>First you need to select the language you want</p><div class="figure">
</div></li>
<li><p>After selecting the language, the user wizard will immediately switch to the corresponding language interface, as shown below in Chinese</p>
<div class="figure">
[[File:zero2w-img336img295.png]]
</div></li><li><p>Then select the area</p>
<div class="figure">
[[File:zero2w-img337img296.png]]
</div><ol start="5" style="list-style-type: decimal;"/li><li><p>Then use select the adb command to install the USB camera test APP into the Android system. Of course, you can also use a USB disk copy to install it.keyboard model</lip></oldiv class="figure">
<ol start="6" style="list-style-type: decimal;"/div></li><li>After installation, you can see the startup icon of the USB camera on the Android desktop.<p>Then create a new username and set a password</lip></oldiv class="figure">
[[File:zero2w-img338img298.png]]
<ol start="7" style="list-style-type: decimal;"/div></li><li><p>Then double-click to open make sure there is no problem with the USB camera APP selection, and you can see then click the output video of the USB camera.install '''button'''</lip></oldiv class="figure">
</div></li>
<li><p>After the installation is complete, you need to click the '''Finish''' button to restart the system.</p>
<div class="figure">
[[File:zero2w-img336img301.png]]
</div></li><li><p>The Orange Pi Hello program will automatically start after restarting. At this time, you need to remove the check '''mark of Start on startup''' in the lower right corner, otherwise you need to manually close the Orange Pi Hello program every time you start it.</p>
<div class="figure">
[[File:zero2w-img339img302.png]]
</div>
'''FDTOVERLAYS /dtbs/allwinner/overlay/<span style="color:#FF0000">xxx.dtbo</span>''' #Configuration that needs to be added
|}
</ol>
<ol start="3" style="list-style-type: decimal;">
<li><p>The GPIO test interface is as shown in the figure below. The two rows storage path of '''CheckBox''' buttons on the left have a one-to-one correspondence with the 40pin pinsxxx. When the '''CheckBox''' button is checked, the corresponding GPIO pin will be set to '''OUT''' mode and dtbo in the pin level OPi OS Arch image is set to high level; when unchecked, the GPIO pin level will as follows. Please note that not all dtbo under this path can 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, etcused.</p>{| class="wikitable" style="width:800px; when you click the" |-| <p>'''BLINK ALL GPIO/boot/dtbs/allwinner/overlay/''' button, all GPIO ports will cycle through outputting high and low levels. This function </p>|}</li><li><p>The DT overlays configuration that can be used to test all by the 40pin pins. GPIO port.development board is as follows</lip></olli>
|-
| '''GPIO序号40pin - i2c0'''| '''GPIO'''| '''功能'''| '''引脚'''|| '''引脚'''| '''功能'''| '''GPIO'''| '''GPIO序号sun50i-h616-pi-i2c0.dtbo'''
|-
|-
| '''26440pin - i2c2'''| '''PI8'''| '''TWI1sun50i-h616-pi-SDAi2c2.dtbo'''| '''3'''|| '''4'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''26340pin - uart2'''| '''PI7sun50i-h616-pi-uart2.dtbo'''| '''TWI1-SCL'''| '''540pin - uart3'''|| '''6'''| '''GNDsun50i-h616-pi-uart3.dtbo'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''26940pin - uart4'''| '''PI13'''| '''PWM3'''| '''7'''|| '''8'''| '''UART0_TX'''| '''PH0'''| '''224sun50i-h616-pi-uart4.dtbo'''
|-
|-
| '''22640pin - pwm1'''| '''PH2'''| '''UART5_TX'''| '''11'''|| '''12'''| style="textsun50i-h616-pi-align: left;"|| '''PI1'''| '''257pwm1.dtbo'''
|-
| '''22740pin - pwm2'''| '''PH3'''| '''UART5_RX'''| '''13'''|| '''14''sun50i-h616-pi-pwm2.dtbo'| '''GND'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''26140pin - pwm3'''| '''PI5'''| '''UART2_TX'''| '''15'''|| '''16'''| '''PWM4'''| '''PI14'''| '''270sun50i-h616-pi-pwm3.dtbo'''
|-
|-
| '''23140pin - spi1 cs0'''| '''PH7'''| '''SPI1_MOSI'''| '''19sun50i-h616-spi1-cs0-spidev.dtbo'''|| '''20'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''23240pin - spi1 cs1'''| '''PH8'''| '''SPI1_MISO'''| '''21'''|| '''22'''| '''UART2_RX'''| '''PI6'''| '''262sun50i-h616-spi1-cs1-spidev.dtbo'''
|-
| '''23040pin - spi1 cs0 cs1'''| '''PH6'''| '''SPI1_CLK'''| '''23'''|| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229sun50i-h616-spi1-cs0-cs1-spidev.dtbo'''
|-
|-
| '''266Turn off the green LED light'''| '''PI10'''| '''TWI2sun50i-h616-zero2w-SDA'''| '''27'''|| '''28'''| '''TWI2disable-SCL'''| '''PI9'''| '''265led.dtbo'''
|-
| '''256How to close the UART0 debugging serial port'''| '''PI0sun50i-h616-disable-uart0.dtbo'''| }</ol><ol start="5" style="textlist-style-aligntype: leftdecimal;"|>| <li>If you need to open multiple configurations at the same time, just add the paths of multiple configurations directly after '''29FDTOVERLAYS.'''For example, the configuration of opening i2c1 and uart5 at the same time is as follows</li>{|| '''30'''| '''GND'''| styleclass="text-align: left;wikitable"|| style="text-alignwidth: left800px;"|
|-
| [orangepi@orangepi-pc ~]$ '''271sudo vim /boot/extlinux/extlinux.conf'''| LABEL Orange Pi KERNEL /Image FDT /dtbs/allwinner/sun50i-h616-orangepi-zero2w.dtb '''PI15FDTOVERLAYS <span style="color:#FF0000">/dtbs/allwinner/overlay/sun50i-h616-pi-i2c1.dtbo /dtbs/allwinner/overlay/sun50i-h616-ph-uart5.dtbo</span>'''| }</ol><ol start="6" style="textlist-style-aligntype: leftdecimal;"|>| '''31'''<li>After setting, you need to restart the system for the configuration to take effect.</li>{|| '''32'''| '''PWM1'''| '''PI11'''| '''267'''class="wikitable" style="width:800px;"
|-
| [orangepi@orangepi-pc ~]$ '''268sudo reboot'''| '''PI12'''}</ol><span id="how-to-install-software"></span>| '''PWM2'''| '''33'''== How to install software ==|| '''34'''You can use the pacman package management tool to install software that is not available in OPi OS. For example, the command to install the vim editor is as follows. If you want to install other software, you only need to replace vim with the package name of the software you want to install.| '''GND'''{| styleclass="text-align: left;wikitable"|| style="text-alignwidth: left800px;"|
|-
|}
<ol startspan id="2" style="listandroid-12-tv-system-styleusage-type: decimal;instructions"><li>The device node corresponding to uart2 is '''/dev/ttyAS2''', and the device node corresponding to uart5 is'''/dev/ttyAS5'''</li></olspan>
<span id="supported-android-versions"></dev/ttyAS0 /dev/ttyAS1 '''/dev/ttyAS2 /dev/ttyAS5'''span>== Supported Android versions ==
|-
| '''GPIO serial numberType-C USB2.0 x 2'''| '''GPIO'''| '''Function'''| '''pin'''|| '''pin'''| '''Function'''| '''GPIO'''| '''GPIO serial numberOK'''
|-
| style="text-align: left;"|| style="text-align: left;"|| '''3.3V'''| '''1'''|| '''2TF card startup'''| '''5VOK'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''264WIFI'''| '''PI8OK'''| '''TWI1-SDA'''| '''3'''|| '''4'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''263Bluetooth'''| '''PI7OK'''| '''TWI1-SCL'''| '''5'''|| '''6USB Camera'''| '''GNDOK'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''269LED Light'''| '''PI13'''| '''PWM3'''| '''7'''|| '''8'''| '''UART0_TX'''| '''PH0'''| '''224OK'''
|-
|-
| '''22640pin I2C'''| '''PH2'''| '''UART5_TX'''| '''11'''|| '''12'''| style="text-align: left;"|| '''PI1'''| '''257OK'''
|-
| '''22740pin SPI1'''| '''PH3OK'''| '''UART5_RX'''| '''13'''|| '''14'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''26140pin UART'''| '''PI5'''| '''UART2_TX'''| '''15'''|| '''16'''| '''PWM4'''| '''PI14'''| '''270OK'''
|-
|-
| '''231Temperature Sensor'''| '''PH7OK'''| '''SPI1_MOSI'''| '''19'''|| '''20'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''232Hardware watchdog'''| '''PH8'''| '''SPI1_MISO'''| '''21'''|| '''22'''| '''UART2_RX'''| '''PI6'''| '''262OK'''
|-
| '''230Mali GPU'''| '''PH6'''| '''SPI1_CLK'''| '''23'''|| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229OK'''
|-
|-
| '''26624pin Expansion board function'''| '''PI10Android12 TV'''| -| '''100M network port'''| '''OK'''TWI2|-SDA| '''100M Ethernet port light'''| '''27OK'''|-| '''28USB2.0 HOST x 2'''| '''TWI2-SCLOK'''|-| '''PI9Infrared reception'''| '''265OK'''
|-
| '''256Headphone audio playback'''| '''PI0OK'''| style="text-align: left;"|| '''29'''|| '''30'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''271On/off button'''| '''PI15'''| style="text-align: left;"|| '''31'''|| '''32'''| '''PWM1'''| '''PI11'''| '''267OK'''
|-
| '''268LRADC'''| '''PI12'''| '''PWM2'''| '''33Custom buttons x 2'''|| '''34OK, The default setting is the volume up and down keys.'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|
|-
| '''258'''| '''PI2'''| style="textTV-align: left;"|| '''35'''|| '''36'''| style="text-align: left;"|| '''PC12OUT'''| '''76OK'''
|}
<ol startspan id="2" style="listonboard-led-light-styledisplay-type: decimal;instructions"><li>The device node corresponding to SPI1 CS0 is '''/dev/spidev1.0''', and the device node corresponding to SPI1 CS1 is '''/dev/spidev1.1'''</li></olspan>== Onboard LED light display instructions ==
<ol startspan id="5" style="listuse-network-connection-styleadb-type: decimal;debugging"><li>Then click the '''SPI_TEST''' button to open the SPI test interface</li></olspan>=== Use network connection adb debugging ===
<ol start="9" style="list-style-typep>* daemon not running; starting now at tcp: decimal;"5037</p> <li>Finally, the APP will display the read ID information of the onboard SPI Flash.</lip>* daemon started successfully</olp>
192.168.1.xxx:5555 device|}</ol><ol start="5" style="list-style-type: decimal;"><li>Then you can log in to the android system through adb shell on Ubuntu PC</li>{| class="wikitable" style="width:800px;"
|-
| test@test:~$ '''GPIO serial numberadb shell''' apollo-p2:/ #| '''GPIO'''}</ol><span id="use-data-cable-to-connect-adb-debugging"></span> === Use data cable to connect adb debugging === | '''Function'# 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.| '''pin'''|::[[File:zero2w-img304.png]] [[File:zero2w-img305.png]]| '''pin'''| '''Function'''<ol start="2" style="list-style-type: decimal;">| '''GPIO'''<li>Install adb tool on Ubuntu PC</li>{| '''GPIO serial number'''class="wikitable" style="width:800px;"
|-
|-
| test@test:~$ '''264adb devices'''| '''PI8'''| '''TWI1-SDA'''List of devices attached| '''3'''|4c00146473c28651dd0 device| '''4'''}| '''5V'''</ol>| <ol start="4" style="textlist-alignstyle-type: leftdecimal;"|><li>Then you can log in to the android system through adb shell on Ubuntu PC</li>{| class="wikitable" style="text-alignwidth: left800px;"|
|-
| test@test:~$ '''263adb shell''' apollo-p2:/ $| }</ol><span id="view-how-to-set-hdmi-display-resolution"></span> == View how to set HDMI display resolution == <ol style="list-style-type: decimal;"><li><p>Enter first '''PI7Settings'''</p><p>[[File:zero2w-img306.png]]</p></li>| <li><p>Then select '''TWI1-SCLDevice Preferences'''</p>| <p>[[File:zero2w-img307.png]]</p></li><li><p>Then select '''5Display & Sound'''</p>|<p>[[File:zero2w-img308.png]]</p></li>| <li><p>Then select '''6Advanced display settings'''</p><p>[[File:zero2w-img309.png]]</p></li>| <li><p>Then select '''GNDHDMI output mode'''</p><p>[[File:zero2w-img310.png]]</p></li><li><p>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.</p><p>[[File:zero2w-img311.png]]</p></li><li><p>The HDMI output of the development board supports 4K display. When connected to a 4K TV, you can see the 4K resolution option.</p><p>[[File:zero2w-img312.png]]</p></li></ol> <span id="hdmi-to-vga-display-test-1"></span>=== HDMI to VGA display test === | <ol style="textlist-style-aligntype: leftdecimal;"|><li><p>First you need to prepare the following accessories</p>| <ol style="textlist-style-aligntype: leftlower-alpha;"|><li>HDMI to VGA converter</li> [[File:zero2w-img144.png]]</ol><ol start="2" style="list-style-type: lower-alpha;"><li>A VGA cable and a Mini HDMI male to HDMI female adapter</li> [[File:zero2w-img145.png]] [[File:zero2w-img146.png]]</ol>|<ol start="3" style="list-style-type: lower-alpha;">| '''269'''<li>A monitor or TV that supports VGA interface</li></ol>| '''PI13'''</li></ol>| '''PWM3'''| '''7'''<ol start="2" style="list-style-type: decimal;">|<li>HDMI to VGA display test is as follows</li>| '''8'''| '''UART0_TX'''[[File:zero2w-img313.png]]| '''PH0'''{| '''224'''class="wikitable" style="background-color:#ffffdc;width:800px;"
|-
[[File:zero2w-img331.png]]</ol><ol start="27" style="list-style-type: decimal;"><li>The device node corresponding to i2c1 What is tested here is '''/dev/i2c-1'''the Bluetooth configuration process between the development board and the Android phone. At this time, and the device node corresponding following confirmation interface will pop up on the phone. Click the pairing button on the phone to i2c2 is '''/dev/i2c-2'''start the pairing process.</li></ol>
[[File:zero2w-img333.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>At this time, you can use the Bluetooth of your mobile phone to send a picture to the development board. After sending, you can see the following confirmation interface in the Android system of the development board, and then click '''/dev/i2c-1 /dev/i2c-2Accept''' to start receiving the pictures sent by the mobile phone.</dev/i2c-5li>
[[File:zero2w-img334.png]]</ol><ol start="310" style="list-style-type: decimal;"><li>First open wiringOP APP on Pictures received by the desktopBluetooth system of the development board Android system can be viewed in '''Received files'''.</li></ol>
[[File:zero2w-img351img335.png]]</ol><span id="how-to-set-usb0-to-host-mode-1"></span>
apollo-p2:/ #|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The command to view the current mode of USB0 is</li>{| class="wikitable" style="width:800px;" |-| apollo-p2:/ # '''cat /sys/devices/platform/soc@3000000/soc@3000000\:usbc0@0/otg_role''' usb_host|}</ol><span id="pinhow-pwmto-testuse-usb-camera"></span> === 40pin PWM test =How to use USB camera == # As can be seen from First insert the USB (UVC protocol) camera into the USB interface of the development board# If the table belowUSB camera is recognized normally, the available pwm are pwm1, pwm2, pwm3 and pwm4.corresponding video device node will be generated under /dev
::{| class="wikitable" style="width:800px;"
|-
| console:/ # '''GPIO serial numberls /dev/video0''' /dev/video0| '''GPIO'''} <ol start="3" style="list-style-type: decimal;"><li><p>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 "[[Orange Pi Zero 2W#How to use ADB| '''FunctionHow to use ADB''']]".</p></li>| <li><p>Download the USB camera test APP from the '''pinofficial tool'''on the development board information download page</p></li> <div class="figure"> [[File:zero2w-img336.png]] </div><div class="figure"> [[File:zero2w-img337.png]]|| '''pin'''</div></ol>| '''Function'''<ol start="5" style="list-style-type: decimal;">| '''GPIO'''<li>Then use the adb command to install the USB camera test APP into the Android system. Of course, you can also use a USB disk copy to install it.</li>{| '''GPIO serial number'''class="wikitable" style="width:800px;"
|-
| test@test:~$ '''adb install usbcamera.apk'''|}</ol><ol start="6" style="textlist-alignstyle-type: leftdecimal;"|><li>After installation, you can see the startup icon of the USB camera on the Android desktop.</li> [[File:zero2w-img338.png]]</ol>| <ol start="7" style="textlist-alignstyle-type: leftdecimal;"|>| '''3<li>Then double-click to open the USB camera APP and you can see the output video of the USB camera.3V'''</li></ol> | '''1'''<span id="android-system-root-description"></span>|| '''2'''== Android system ROOT description ==| '''5V'''{| styleclass="text-align: left;wikitable"|| style="textbackground-aligncolor: left#ffffdc;width:800px;"|
|-
| <big>'''264The Android system released by Orange Pi has been ROOT and can be tested using the following method.'''</big>| } # Download from the '''PI8official tool'''| on the development board data download page '''TWI1-SDArootcheck.apk'''| '''3'''|<div class="figure"> ::[[File:zero2w-img336.png]] </div><div class="figure"> ::[[File:zero2w-img339.png]] </div><ol start="2" style="list-style-type: decimal;"><li><p>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 "[[Orange Pi Zero 2W#How to use ADB| '''4How to use ADB''']]".</p></li>| '''5V'''<li><p>Then use the adb command to install rootcheck.apk into the Android system. Of course, you can also use a USB disk copy to install it.</p></li>{| styleclass="text-align: left;wikitable"|| style="text-alignwidth: left800px;"|
|-
| test@test:~$ '''263adb install rootcheck.apk'''| '''PI7'''}</ol><ol start="4" style="list-style-type: decimal;"><li>After installation, you can see the startup icon of the ROOT test tool on the Android desktop.</li> [[File:zero2w-img340.png]]</ol>| '''TWI1<ol start="5" style="list-style-SCL'''type: decimal;">| <li>The display interface after opening the '''5ROOT test tool'''for the first time is as shown below</li> [[File:zero2w-img341.png]]|</ol>| '''<ol start="6'''" style="list-style-type: decimal;">| <li>Then you can click '''GNDCHECK 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> | style[[File:zero2w-img342.png]]</ol><span id="texthow-to-use-align: left;miracastreceiver-to-cast-the-mobile-phone-screen-to-the-development-board"|></span> == How to use MiracastReceiver to cast the mobile phone screen to the development board == | <ol style="textlist-alignstyle-type: leftdecimal;"|>|<li><p>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 [[Orange Pi Zero 2W#WI-FI connection method| '''269the instructions in the WI-FI connection method.''']]</p></li>| <li><p>Then open the '''PI13MiracastReceiver'''application in the Android system of the development board</p>| <p>[[File:zero2w-img343.png]]</p></li><li><p>The interface after '''PWM3MiracastReceiver'''is opened is as follows</p>| <div class="figure"> [[File:zero2w-img344.png]] </div></li><li><p>Then find the screen mirroring function in the phone settings. Here we take '''7Xiaomi 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.</p>|<p>[[File:zero2w-img345.png]]</p></li><li><p>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.</p><p>[[File:zero2w-img346.png]]</p></li>| <li><p>Then the selection box shown in the figure below will pop up in the '''8MiracastReceiver'''| application interface of the development board. Here we can select '''UART0_TXAccept'''</p><p>[[File:zero2w-img347.png]]</p></li><li><p>Then you can see the content of the mobile phone screen on the HDMI screen connected to the development board</p><p>[[File:zero2w-img348.png]]</p></li></ol> <span id="method-of-turning-on-and-off-the-machine-through-buttons-or-infrared-remote-control"></span> == Method of turning on and off the machine through buttons or infrared remote control == 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:zero2w-img107.png]] The location of the power button on the 24pin expansion board is as shown in the figure below: [[File:zero2w-img269.png]]| The location of the infrared remote control power button is as follows: [[File: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 '''PH0OK'''to shut down the Android system. [[File: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. <span id="pin-interface-gpio-uart-spi-test"></span>== 40pin interface GPIO, UART, SPI test == {| '''224'''class="wikitable" style="background-color:#ffffdc;width:800px;"
|-
| <big>'''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.'''</big>|} <span id="pin-gpio-port-test-method"></span>=== 40pin GPIO port test method === # First open wiringOP APP on the desktop ::[[File:zero2w-img351.png]] <ol start="2" style="textlist-style-type: decimal;"><li>Then click the '''GPIO_TEST''' button to open the GPIO test interface</li> [[File:zero2w-img352.png]]</ol><ol start="3" style="list-style-aligntype: decimal;"><li>The GPIO test interface is as shown in the figure below. The two rows of '''CheckBox''' buttons on the lefthave 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> [[File:zero2w-img353.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button, and the output information is as shown below:</li> <div class="figure"> [[File:zero2w-img354.png]] </div></ol><ol start="5" style="list-style-type: decimal;"><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> [[File:zero2w-img355.png]]</ol><ol start="6" style="list-style-type: decimal;"|><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> [[File:zero2w-img356.png]]</ol>| <ol start="7" style="textlist-style-aligntype: leftdecimal;"|>| <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 '''GND0v''', it means the low level setting is successful.</li> [[File:zero2w-img357.png]]| </ol><ol start="8" style="list-style-type: decimal;"><li>Then click the '''9GPIO READALL'''button and you can see that the current pin 12 mode is OUT and the pin level is low level.</li> [[File:zero2w-img358.png]]</ol><span id="pin-uart-test-method"></span> === 40pin UART test method === # As can be seen from the table below, the default uarts available in the Android12 TV system are uart2 and uart5. Please note that uart0 is set as a debugging serial port by default. Please do not use uart0 as a normal serial port. <div style="display: flex;">::{|class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''10GPIO NO.'''| '''UART0_RXGPIO'''| '''PH1Function'''| '''225Pin'''
|-
| style="text-align: left;"|
| style="text-align: left;"|| '''3.3V'''| '''1'''|-| '''264'''| '''PI8'''| '''TWI1-SDA'''| '''3'''|-| '''263'''| '''PI7'''| '''TWI1-SCL'''| '''5'''|-| '''269'''| '''PI13'''| '''PI1PWM3'''| '''2577'''
|-
| style="text-align: left;"|
| style="text-align: left;"|
| '''GND'''
| '''9'''
|-
| '''261<span style="color:#FF0000">226</span>'''| '''<span style="color:#FF0000">PH2</span>'''| '''<span style="color:#FF0000">UART5_TX</span>'''| '''<span style="color:#FF0000">11</span>'''|-| '''<span style="color:#FF0000">227</span>'''| '''PI5<span style="color:#FF0000">PH3</span>'''| '''UART2_TX<span style="color:#FF0000">UART5_RX</span>'''| '''15<span style="color:#FF0000">13</span>'''|-| '''16<span style="color:#FF0000">261</span>'''| '''PWM4<span style="color:#FF0000">PI5</span>'''| '''PI14<span style="color:#FF0000">UART2_TX</span>'''| '''270<span style="color:#FF0000">15</span>'''
|-
| style="text-align: left;"|
| '''3.3V'''
| '''17'''
|-
| '''231'''
| '''SPI1_MOSI'''
| '''19'''
|-
| '''232'''
| '''SPI1_MISO'''
| '''21'''
|-
| '''230'''
| '''SPI1_CLK'''
| '''23'''
|-
| style="text-align: left;"|
| '''GND'''
| '''25'''
| '''PI10'''
| '''TWI2-SDA'''
| '''27'''
|-
| '''256'''
| style="text-align: left;"|
| '''29'''
|-
| '''271'''
| style="text-align: left;"|
| '''31'''
|-
| '''268'''
| '''PWM2'''
| '''33'''
|-
| '''258'''
| style="text-align: left;"|
| '''35'''
|-
| '''272'''
| style="text-align: left;"|
| '''37'''
|-
| style="text-align: left;"|
| '''GND'''
| '''39'''
|}{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''40Pin'''| '''Function'''| '''GPIO'''| '''GPIO NO.'''|-| '''2'''| '''5V'''| style="text-align: left;"|
| style="text-align: left;"|
|-| '''PI34'''| '''2595V'''|} <ol startstyle="2text-align: left;" || style="list-styletext-typealign: decimalleft;">|<li>First click the wiringOP icon to open wiringOP APP</li></ol>|-| '''6'''[[File:zero2w-img351.png]]| '''GND''' <ol start| style="3text-align: left;" || style="listtext-style-typealign: decimalleft;">||-<li>Then click the | '''PWM_TEST8''' button on the main interface of wiringOP to enter the PWM test interface</li></ol>| '''UART0_TX'''[[File:zero2w-img380.png]]| '''PH0'''| '''224'''<ol start="4" style="list-style|-type: decimal;"><li>The PWM test interface is as follows</li></ol>| '''10'''| '''UART0_RX'''<div class="figure">| '''PH1'''| '''225'''[[File:zero2w|-img381.png]]| '''12'''</div><ol start="5" | style="list-styletext-typealign: decimalleft;">|<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>| '''PI1'''| '''257'''[[File:zero2w|-img382.png]]| '''14'''| '''GND'''<ol start| style="6text-align: left;" || style="list-styletext-typealign: decimalleft;">||-| '''16'''<li>Then you can set the PWM period. The default configuration is | '''50000nsPWM4'''. The converted PWM frequency is | '''20KHzPI14'''</li></ol>| '''270'''[[File:zero2w|-img383.png]]| '''18'''<ol start="7" | style="list-styletext-typealign: decimalleft;">|<li>Then click the | '''EXPORTPH4'''button to export PWM</li></ol>| '''228'''[[File:zero2w|-img384.png]]| '''20'''<ol start| '''GND'''| style="8text-align: left;" || style="listtext-align: left;"||-| '''<span style-type="color: decimal;#FF0000">22<li/span>Then drag the progress bar below to change the PWM duty cycle, and then check '''Enable| ''' to output the PWM waveform.</lispan style="color:#FF0000">UART2_RX</olspan>''' [[File:zero2w-img385.png]] | '''<ol start="9" span style="list-style-typecolor: decimal;#FF0000"><li>Then use an oscilloscope to measure the corresponding pins in the 40pin development board and you can see the following waveform.PI6</li></olspan>''' [[File:zero2w-img386.png]] | '''<span idstyle="how-to-compile-android-12-source-codecolor:#FF0000">262</span>'''|-| '''24'''| '''SPI1_CS0'''= | '''How to compile Android 12 source codePH5''' =| '''229'''<span id="download|-the| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''233'''|-source| '''28'''| '''TWI2-code-of-androidSCL'''| '''PI9'''| '''265'''|-12"></span>== Download the source code of Android 12 ==| '''30'''| '''GND'''<ol | style="list-styletext-typealign: decimalleft;">|<li><p>First download the compressed package of the Android 12 source code and the compressed package of the files modified by Orange Pi Zero2w from Google Cloud Drive</p><ol | style="list-styletext-typealign: lower-alphaleft;">||-| '''32'''<li>Google Cloud Drive</li></ol>| '''PWM1'''</li></ol>| '''PI11'''| '''267'''[[File:zero2w|-img387.png]]| '''34'''| '''GND'''<ol start| style="2text-align: left;" || style="listtext-align: left;"||-| '''36'''| style="text-typealign: decimalleft;">|| '''PC12'''<li>After downloading the compressed package of Android 12 source code, please check whether the MD5 checksum is correct. If it is incorrect, please download the source code again. Here| '''76'''s how to check the MD5 checksum:</li></ol>|-test@test:~$ | '''md5sum -c H618-Android12-Src.tar.gz.md5sum38''' H618| style="text-Android12-Src.tar.gzaaalign: left;"|| '''OKPI4'''| '''260'''H618|-Android12| '''40'''| style="text-Src.tar.gzabalign: left;"|| '''OKPI3'''| '''259'''......|}</div>
<ol start="2" style="list-style-type: decimal;">
<li>The device node corresponding to uart2 is '''/dev/ttyAS2''', and the device node corresponding to uart5 is'''/dev/ttyAS5'''</li>
{| class="wikitable" style="width:800px;"
|-
|
<p>apollo-p2:/ # ls /dev/ttyAS*</p>
<p>/dev/ttyAS0 /dev/ttyAS1 '''<span style="color:#FF0000">/dev/ttyAS2 /dev/ttyAS5</span>'''</p>
|}
</ol>
<ol start="3" style="list-style-type: decimal;">
<li>Then you need to merge multiple compressed files into one, and then extract First open wiringOP APP on the Android source code. The command looks like this:desktop</li></ol> test@test:~$ '''cat H618-Android12-Src.tar.gza* > H618-Android12-Src.tar.gz''' test@test:~$ '''tar -xvf H618-Android12-Src.tar.gz'''
[[File:zero2w-img351.png]]
</ol>
<ol start="4" style="list-style-type: decimal;">
<li>Then unzip click the compressed package of the files modified by Orange Pi Zero2w</li></ol> test@test:~$ '''tar zxf opizero2w_android12_patches.tar.gzUART_TEST''' button to open the UART test@test:~$ '''ls''' '''opizero2w_android12_patches''' opizero2w_android12_patches.tar.gzinterface</li>
[[File:zero2w-img359.png]]
</ol>
<ol start="5" style="list-style-type: decimal;">
<li>Then copy The serial port test interface of wiringOP is as shown in the files modified by Orange Pi Zero2w to the Android source codefigure below</li></ol>
[[File:zero2w-img362.png]]</ol><span idol start="compile8" style="list-style-type: decimal;"><li><p>Then use Dupont wire to short the-source-code-rx and tx pins of-android-12"uart</p></spanli>== Compile <li><p>Then you can enter a paragraph of characters in the send edit box below and click the source code of Android 12 =='''SEND''' button to start sending.</p></li>
[https[File://repo.huaweicloud.com/ubuntuzero2w-releases/22img364.04png]]</ubuntuol><span id="pin-22.04.2spi-desktoptest-amd64.iso '''https:method"><//repo.huaweicloud.com/ubuntu-releases/22.04/ubuntu-22.04.2-desktop-amd64.iso''']span>
# First install As can be seen from the software packages needed to compile Android12 source codetable below, the spi available for the 40pin interface is spi1, and there are two chip select pins cs0 and cs1
=== 40pin I2C test method === # As can be seen from the table below, the Android12 TV system has i2c1 and i2c2 turned on by default. <div style="display: flex;">::{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''GPIO NO.'''| '''GPIO'''| '''Function'''| '''Pin'''|-| style="text-align: left;"|| style="text-align: left;"|| '''3.3V'''| '''1'''|-| '''<span style="color:#FF0000">264</span>'''| '''<span style="color:#FF0000">PI8</span>'''| '''<span style="color:#FF0000">TWI1-SDA</span>'''| '''<span style="color:#FF0000">3</span>'''|-| '''<span style="color:#FF0000">263</span>'''| '''<span style="color:#FF0000">PI7</span>'''| '''<span style="color:#FF0000">TWI1-SCL</span>'''| '''<span style="color:#FF0000">5</span>'''|-| '''269'''| '''PI13'''| '''PWM3'''| '''7'''|-| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''9'''|-| '''226'''| '''PH2'''| '''UART5_TX'''| '''11'''|-| '''227'''| '''PH3'''| '''UART5_RX'''| '''13'''|-| '''261'''| '''PI5'''| '''UART2_TX'''| '''15'''|-| style="text-align: left;"|| style="text-align: left;"|| '''3.3V'''| '''17'''|-| '''231'''| '''PH7'''| '''SPI1_MOSI'''| '''19'''|-| '''232'''| '''PH8'''| '''SPI1_MISO'''| '''21'''|-| '''230'''| '''PH6'''| '''SPI1_CLK'''| '''23'''|-| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''25'''|-| '''<span style="color:#FF0000">266</span>'''| '''<span style="color:#FF0000">PI10</span>'''| '''<span style="color:#FF0000">TWI2-SDA</span>'''| '''<span style="color:#FF0000">27</span>'''|-| '''256'''| '''PI0'''| style="text-align: left;"|| '''29'''|-| '''271'''| '''PI15'''| style="text-align: left;"|| '''31'''|-| '''268'''| '''PI12'''| '''PWM2'''| '''33'''|-| '''258'''| '''PI2'''| style="text-align: left;"|| '''35'''|-| '''272'''| '''PI16'''| style="text-align: left;"|| '''37'''|-| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''39'''|}{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''Pin'''| '''Function'''| '''GPIO'''| '''GPIO NO.'''|-| '''2'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"||-| '''4'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"||-| '''6'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"||-| '''8'''| '''UART0_TX'''| '''PH0'''| '''224'''|-| '''10'''| '''UART0_RX'''| '''PH1'''| '''225'''|-| '''12'''| style="text-align: left;"|| '''PI1'''| '''257'''|-| '''14'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"||-| '''16'''| '''PWM4'''| '''PI14'''| '''270'''|-| '''18'''| style="text-align: left;"|| '''PH4'''| '''228'''|-| '''20'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"||-| '''22'''| '''UART2_RX'''| '''PI6'''| '''262'''|-| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229'''|-| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''233'''|-| '''<span style="color:#FF0000">28</span>'''| '''<span style="color:#FF0000">TWI2-SCL</span>'''| '''<span style="color:#FF0000">PI9</span>'''| '''<span style="color:#FF0000">265</span>'''|-| '''30'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"||-| '''32'''| '''PWM1'''| '''PI11'''| '''267'''|-| '''34'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"||-| '''36'''| style="text-align: left;"|| '''PC12'''| '''76'''|-| '''38'''| style="text-align: left;"|| '''PI4'''| '''260'''|-| '''40'''| style="text-align: left;"|| '''PI3'''| '''259'''|}</div> <ol start="2" style="list-style-type: decimal;"><li>The device node corresponding to i2c1 is '''/dev/i2c-1''', and the device node corresponding to i2c2 is '''/dev/i2c-2'''</li>{| class="wikitable" style="width:800px;" |-| apollo-p2:/ # '''ls /dev/i2c-*''' '''<span style="color:#FF0000">/dev/i2c-1 /dev/i2c-2</span>''' /dev/i2c-5|}</ol><ol start="3" style="list-style-type: decimal;"><li>First open wiringOP APP on the desktop</li> [[File:zero2w-img351.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then click the '''I2C_TEST''' button to open the i2c test interface</li> [[File:zero2w-img370.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>The i2c test interface of wiringOP is shown in the figure below</li> [[File:zero2w-img371.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then click the device node selection box in the upper left corner to select the i2c you want to test</li> [[File:zero2w-img372.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Then connect an i2c device to the 40pin i2c pin. Here we take the ds1307 rtc module as an example.</li> [[File:zero2w-img178.png]]</ol><ol start="8" style="list-style-type: decimal;"><li><p>The i2c address of the ds1307 rtc module is 0x68. After connecting the lines, we can use the '''i2cdetect -y 1''' or '''i2cdetect -y 2''' command on the serial port command line to check whether the i2c address of the ds1307 rtc module can be scanned. If you can see the address 0x68, it means that the ds1307 rtc module is wired correctly.</p>{| class="wikitable" style="width:800px;" |-| <p>apollo-p2:/ # '''i2cdetect -y 1'''</p><p>'''Or'''</p><p>apollo-p2:/ # '''i2cdetect -y 2'''</p>|}<p>[[File:zero2w-img373.png]]</p></li><li><p>Then set the i2c address to 0x68 in wiringOP, and then click the '''OPEN''' button to open i2c</p><p>[[File:zero2w-img374.png]]</p></li><li><p>After clicking the '''OPEN''' button to open i2c, the display is as follows</p><p>[[File:zero2w-img375.png]]</p></li><li><p>Then we test writing a value to the register of the rtc module, for example, writing 0x55 to the 0x1c address</p><ol style="list-style-type: lower-alpha;"><li><p>We first set the address of the register to be written to 0x1c</p><p>[[File:zero2w-img376.png]]</p></li><li><p>Then set the value to be written to 0x55</p><p>[[File:zero2w-img377.png]]</p></li><li><p>Then click the '''WRITE BYTE''' button to perform the writing action</p><p>[[File:zero2w-img378.png]]</p></li></ol></li><li><p>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.</p><p>[[File:zero2w-img379.png]]</p></li></ol> <span id="pin-pwm-test"></span> === 40pin PWM test === # As can be seen from the table below, the available pwm are pwm1, pwm2, pwm3 and pwm4. <div style="display: flex;">::{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''GPIO NO.'''| '''GPIO'''| '''Function'''| '''Pin'''|-| style="text-align: left;"|| style="text-align: left;"|| '''3.3V'''| '''1'''|-| '''264'''| '''PI8'''| '''TWI1-SDA'''| '''3'''|-| '''263'''| '''PI7'''| '''TWI1-SCL'''| '''5'''|-| '''<span style="color:#FF0000">269</span>'''| '''<span style="color:#FF0000">PI13</span>'''| '''<span style="color:#FF0000">PWM3</span>'''| '''<span style="color:#FF0000">7</span>'''|-| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''9'''|-| '''226'''| '''PH2'''| '''UART5_TX'''| '''11'''|-| '''227'''| '''PH3'''| '''UART5_RX'''| '''13'''|-| '''261'''| '''PI5'''| '''UART2_TX'''| '''15'''|-| style="text-align: left;"|| style="text-align: left;"|| '''3.3V'''| '''17'''|-| '''231'''| '''PH7'''| '''SPI1_MOSI'''| '''19'''|-| '''232'''| '''PH8'''| '''SPI1_MISO'''| '''21'''|-| '''230'''| '''PH6'''| '''SPI1_CLK'''| '''23'''|-| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''25'''|-| '''266'''| '''PI10'''| '''TWI2-SDA'''| '''27'''|-| '''256'''| '''PI0'''| style="text-align: left;"|| '''29'''|-| '''271'''| '''PI15'''| style="text-align: left;"|| '''31'''|-| '''<span style="color:#FF0000">268</span>'''| '''<span style="color:#FF0000">PI12</span>'''| '''<span style="color:#FF0000">PWM2</span>'''| '''<span style="color:#FF0000">33</span>'''|-| '''258'''| '''PI2'''| style="text-align: left;"|| '''35'''|-| '''272'''| '''PI16'''| style="text-align: left;"|| '''37'''|-| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''39'''|}{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''Pin'''| '''Function'''| '''GPIO'''| '''GPIO NO.'''|-| '''2'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"||-| '''4'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"||-| '''6'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"||-| '''8'''| '''UART0_TX'''| '''PH0'''| '''224'''|-| '''10'''| '''UART0_RX'''| '''PH1'''| '''225'''|-| '''12'''| style="text-align: left;"|| '''PI1'''| '''257'''|-| '''14'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"||-| '''<span style="color:#FF0000">16</span>'''| '''<span style="color:#FF0000">PWM4</span>'''| '''<span style="color:#FF0000">PI14</span>'''| '''<span style="color:#FF0000">270</span>'''|-| '''18'''| style="text-align: left;"|| '''PH4'''| '''228'''|-| '''20'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"||-| '''22'''| '''UART2_RX'''| '''PI6'''| '''262'''|-| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229'''|-| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''233'''|-| '''28'''| '''TWI2-SCL'''| '''PI9'''| '''265'''|-| '''30'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"||-| '''<span style="color:#FF0000">32</span>'''| '''<span style="color:#FF0000">PWM1</span>'''| '''<span style="color:#FF0000">PI11</span>'''| '''<span style="color:#FF0000">267</span>'''|-| '''34'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"||-| '''36'''| style="text-align: left;"|| '''PC12'''| '''76'''|-| '''38'''| style="text-align: left;"|| '''PI4'''| '''260'''|-| '''40'''| style="text-align: left;"|| '''PI3'''| '''259'''|}</div> <ol start="2" style="list-style-type: decimal;"><li>First click the wiringOP icon to open wiringOP APP</li> [[File:zero2w-img351.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then click the '''PWM_TEST''' button on the main interface of wiringOP to enter the PWM test interface</li> [[File:zero2w-img380.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>The PWM test interface is as follows</li> <div class="figure"> [[File:zero2w-img381.png]] </div></ol><ol start="5" style="list-style-type: decimal;"><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> [[File:zero2w-img382.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then you can set the PWM period. The default configuration is '''50000ns'''. The converted PWM frequency is '''20KHz'''</li> [[File:zero2w-img383.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Then click the '''EXPORT'''button to export PWM</li> [[File:zero2w-img384.png]]</ol><ol start="8" style="list-style-type: decimal;"><li>Then drag the progress bar below to change the PWM duty cycle, and then check '''Enable''' to output the PWM waveform.</li> [[File:zero2w-img385.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then use an oscilloscope to measure the corresponding pins in the 40pin development board and you can see the following waveform.</li> [[File:zero2w-img386.png]]</ol><span id="how-to-compile-android-12-source-code"></span> = '''How to compile Android 12 source code''' = <span id="download-the-source-code-of-android-12"></span>== Download the source code of Android 12 == <ol style="list-style-type: decimal;"><li><p>First download the compressed package of the Android 12 source code and the compressed package of the files modified by Orange Pi Zero2w from Google Cloud Drive</p><ol style="list-style-type: lower-alpha;"><li>Google Cloud Drive</li> [[File:zero2w-img387.png]]</ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>After downloading the compressed package of Android 12 source code, please check whether the MD5 checksum is correct. If it is incorrect, please download the source code again. Here's how to check the MD5 checksum:</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''md5sum -c H618-Android12-Src.tar.gz.md5sum''' H618-Android12-Src.tar.gzaa: '''<span style="color:#FF0000">OK</span>''' H618-Android12-Src.tar.gzab: '''<span style="color:#FF0000">OK</span>''' ......|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then you need to merge multiple compressed files into one, and then extract the Android source code. The command looks like this:</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''cat H618-Android12-Src.tar.gz<span style="color:#FF0000">a</span>* > H618-Android12-Src.tar.gz''' test@test:~$ '''tar -xvf H618-Android12-Src.tar.gz'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then unzip the compressed package of the files modified by Orange Pi Zero2w</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''tar zxf opizero2w_android12_patches.tar.gz''' test@test:~$ '''ls''' '''opizero2w_android12_patches''' opizero2w_android12_patches.tar.gz|}</ol><ol start="5" style="list-style-type: decimal;"><li>Then copy the files modified by Orange Pi Zero2w to the Android source code</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''cp -rf opizero2w_android12_patches/* H618-Android12-Src/'''|}</ol><span id="compile-the-source-code-of-android-12"></span> == Compile the source code of Android 12 == {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Android12 is compiled on an x86_64 computer with <span style="color:#FF0000">Ubuntu 22.04</span> installed. Other versions of Ubuntu system package dependencies may have some differences. The image download address of the Ubuntu 22.04 <span style="color:#FF0000">amd64</span> version is as follows:''' [https://repo.huaweicloud.com/ubuntu-releases/22.04/ubuntu-22.04.2-desktop-amd64.iso '''https://repo.huaweicloud.com/ubuntu-releases/22.04/ubuntu-22.04.2-desktop-amd64.iso'''] '''The x86_64 computer hardware configuration for compiling Android12 source code recommends a memory of 16GB or more, and a hard disk space of 200GB or more is recommended. The more CPU cores, the better.'''</big>|} # First install the software packages needed to compile Android12 source code ::{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt-get update''' test@test:~$ '''sudo apt-get install -y git gnupg flex bison gperf build-essential \''' '''zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 \''' '''lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z1-dev ccache \''' '''libgl1-mesa-dev libxml2-utils xsltproc unzip u-boot-tools python-is-python3 \''' '''libssl-dev libncurses5 clang gawk'''|} <ol start="2" style="list-style-type: decimal;"><li><p>Then compile the code in the longan folder, which mainly contains u-boot and linux kernel</p><ol style="list-style-type: lower-alpha;"><li>First run '''./build.sh config''' to set compilation options</li>{| class="wikitable" style="width:800px;" |-| <p>test@test:~$ '''cd H618-Android12-Src/longan'''</p><p>test@test:~/H618-Android12-Src/longan$ '''./build.sh config'''</p> <p>Welcome to mkscript setup progress</p><p>All available platform:</p>:<p>0. android</p>:<p>1. linux</p><p>Choice [android]: '''<span style="color:#FF0000">0</span>'''</p><p>All available ic:</p>:<p>0. h618</p><p>Choice [h618]: '''<span style="color:#FF0000">0</span>'''</p><p>All available board:</p>:<p>0. ft</p>:<p>1. p1</p>:<p>2. p2</p>:<p>3. p7</p>:<p>4. p7l</p>:<p>5. perf1</p>:<p>6. perf2</p>:<p>7. perf3</p>:<p>8. qa</p><p>Choice [p2]: '''<span style="color:#FF0000">2</span>'''</p><p>All available flash:</p>:<p>0. default</p>:<p>1. nor</p><p>Choice [default]: '''<span style="color:#FF0000">0</span>'''</p><p>All available kern_ver:</p>:<p>0. linux-5.4</p><p>Choice [linux-5.4]: '''<span style="color:#FF0000">0</span>'''</p><p>All available arch:</p>:<p>0. arm</p>:<p>1. arm64</p><p>Choice [arm64]: '''<span style="color:#FF0000">1</span>'''</p><p>'''......'''</p><p>*** Default configuration is based on 'sun50iw9p1smp_h618_android_defconfig'</p><p>#</p><p># configuration written to .config</p><p>#</p><p>make[1]: Leaving directory '/home/test/H618-Android12-Src/longan/out/kernel/build'</p><p>make: Leaving directory '/home/test/H618-Android12-Src/longan/kernel/linux-5.4'</p><p>INFO: clean buildserver</p><p>INFO: prepare_buildserver</p>|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then run the '''./build.sh''' script to start compilation.</li>{| class="wikitable" style="width:800px;" |-| test@test:~/H618-Android12-Src/longan$ '''./build.sh'''|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>After compilation is completed, you will see the following output</li>{| class="wikitable" style="width:800px;" |-| sun50iw9p1 compile Kernel successful INFO: Prepare toolchain ... '''......''' INFO: build kernel OK. INFO: build rootfs ... INFO: skip make rootfs for android INFO: ---------------------------------------- INFO: build lichee OK.
INFO: ----------------------------------------
|}
</ol>
</li></ol>
<ol start="3" style="list-style-type: decimal;">
<li>Then use the following command to compile the Android source code and generate the final Android image</li>
{| class="wikitable" style="width:800px;"
|-
|
test@test:~$ '''cd H618-Android12-Src'''
test@test:~/H618-Android12-Src$ '''source build/envsetup.sh'''
test@test:~/H618-Android12-Src$ '''lunch apollo_p2-userdebug'''
test@test:~/H618-Android12-Src$ '''make -j8'''
test@test:~/H618-Android12-Src$ '''pack'''
|}
</ol>
<ol start="4" style="list-style-type: decimal;">
<li><p>The storage path of the Android image generated by compilation is:</p>
{| class="wikitable" style="width:800px;"
|-
|
<p>'''longan/out/h618_android12_p2_uart0.img'''</p>
|}
</li></ol>
<span id="appendix"></span>
= '''Appendix''' =
<span id="user-manual-update-history"></span>
== User manual update history ==
{| class="wikitable" style="width:800px;text-align: center;"
|-
| '''Version'''
| '''Date'''
| '''Release Notes'''
|-
| v1.0
| 2023-09-14
| initial version
|}
<span id="image-update-history"></span>
== Image update history ==
{| class="wikitable" style="width:800px;"
|-
| style="text-align: center;"| '''Date'''
| style="text-align: center;"| '''Release Notes'''
|-
| style="text-align: center;"| 2023-09-14
|
orangepizero2w_1.0.0_debian_bullseye_server_linux5.4.125.7z
orangepizero2w_1.0.0_ubuntu_focal_server_linux5.4.125.7z
orangepizero2w_1.0.0_ubuntu_focal_desktop_xfce_linux5.4.125.7z
orangepizero2w_1.0.0_debian_bullseye_desktop_xfce_linux5.4.125.7z
orangepizero2w_1.0.0_ubuntu_jammy_server_linux6.1.31.7z
orangepizero2w_1.0.0_debian_bookworm_server_linux6.1.31.7z
orangepizero2w_1.0.0_debian_bullseye_server_linux6.1.31.7z
orangepizero2w_1.0.0_ubuntu_jammy_desktop_xfce_linux6.1.31.7z
orangepizero2w_1.0.0_debian_bookworm_desktop_xfce_linux6.1.31.7z
orangepizero2w_1.0.0_debian_bullseye_desktop_xfce_linux6.1.31.7z
OrangePi_Zero2w_Android12_v1.0.tar.gz
Opios-arch-aarch64-xfce-opizero2w-23.09-linux6.1.31.img.xz