Changes

← Older edit

Orange Pi Zero 2W

52,516 bytes added, 20:33, 27 September 2023

→‎Download orangepi-build from github

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

</div>

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

</div>

[[File:zero2w-img5.png|800px]]

</div>

== Orange Pi Zero 2w 24pin expansion board interface details ==

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

</div>

[[File:zero2w-img7.png|800px]]

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

== Supported linux image types and kernel versions ==

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

|-

| '''Linux image type'''

The naming rules for Linux images are:

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

|-

|

'''Development board model_version number_Linux distribution type_distribution code_server or desktop_kernel version'''

|}

a. '''Development board models''': all are '''orangepizero2w'''. The model names of different development boards are generally different. Before burning the image, please make sure that the model name of the selected image matches the development board.

== Linux kernel driver adaptation situation ==

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

|-

| '''Board functions'''

|-

| '''Mali GPU'''

| '''NO'''| '''NO'''

|-

| '''Video codec'''

| '''NO'''| '''NO'''

|}

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

|-

| '''24pin expansion board function'''

|-

| '''TV-OUT'''

| '''NO'''| '''NO'''

|}

== Linux command format description in this manual ==

<li>All commands that need to be entered in the Linux system in this manual will be enclosed in the following boxes

{| class="wikitable" style="width:800px;height:40px;" |-| |}As shown below, the content in the yellow box indicates content that requires special attention, except for the commands inside.{| class="wikitable" style="background-color:#ffffdc;width:800px;height:40px;" |-| |}</li>

<li>Description of the prompt type before the command

<li>The prompt in front of the command refers to the red part in the ~~>~~ box below. This part is not part of the Linux command. ~~>~~ Therefore, when entering commands in the Linux system, please ~~>~~ do not also enter the content in the red font.{| class="wikitable" style="width:800px;" |-| '''orangepi@orangepi:~$ sudo apt update''''''root@orangepi:~#''' '''vim /boot/boot.cmd''''''test@test:~$ ssh ~~[mailto:root@192.168.1.36~~ root@192.168.1.]xxx''''''root@test:~# ls'''|}</li><li>'''root@orangepi:~$''' prompt indicates that this command is ~~>~~ entered in the '''Linux system of the development board'''. The ~~>~~ '''$''' at the end of the prompt indicates that the current ~~>~~ user of the system is an ordinary user. When executing a ~~>~~ privileged command, '''sudo''' needs to be added.</li><li>'''root@orangepi:~#''' The prompt indicates that this command is ~~>~~ entered in the '''Linux system of the development board'''. The ~~>~~ '''#''' at the end of the prompt indicates that the current ~~>~~ user of the system is the root user and can execute any ~~>~~ command you want to execute.</li><li>'''test@test:~$''' prompt indicates that this command was ~~>~~ entered in the Ubuntu PC or Ubuntu virtual machine, not the ~~>~~ Linux system of the development board. The '''$''' at the end ~~>~~ of the prompt indicates that the current user of the system is ~~>~~ an ordinary user. When executing privileged commands, sudo ~~>~~ needs to be added.</li><li>'''root@test:~#''' prompt indicates that this command is entered ~~>~~ in the Ubuntu PC or Ubuntu virtual machine, not the Linux ~~>~~ system of the development board. The '''#''' at the end of the ~~>~~ prompt indicates that the current user of the system is the ~~>~~ root user and can execute any command you want to execute.</li></ol>

</li>

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

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

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

'''verbosity=7'''

bootlogo=false

'''console=serial'''~~</li><li>~~|}</li><li>As shown below, some commands that cannot be written in one line ~~>~~ will be placed on the next line. As long as the black and bold ~~>~~ parts are the commands that need to be entered. When these ~~>~~ commands are entered into one line, the "\" at the end of ~~>~~ each line needs to be removed. This is not part of the ~~>~~ command. In addition, different parts of the command have ~~>~~ spaces, please don't miss them.{| class="wikitable" style="width:800px;" |-|

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

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

'''signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] \'''

'''https://download.docker.com/linux/debian \'''

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

</li></ol>

== Linux system login instructions ==

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

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

|-

| '''Account'''

|}

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''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 any malfunction. Just press Enter after entering the password.'''</big>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''When you are prompted for an incorrect password or there is a problem with the ssh connection, please note that as long as you are using the Linux image provided by Orange Pi, please do not suspect that the above password is incorrect, but look for other reasons.'''</big>|}

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

~~~~

=== How to set up automatic login of Linux system terminal ===

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

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

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

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

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

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

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

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

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

</div></li>

<li>Run the following command to prevent the desktop system from automatically logging into the desktop.

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo disable_desktop_autologin.sh'''|}</li><li>Then restart the system and a login dialog box will appear. At this time, you need to enter a password to enter the system.</li~~></ol~~>

[[File:zero2w-img78.png]]

</div></ol>

=== Setting method for automatic login of root user in Linux desktop system ===

<li>Execute the following command to set the desktop version of the system to automatically log in using the root user

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

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

[[File:zero2w-img79.png]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that if you use the root user to log in to the desktop system, you cannot use pulseaudio in the upper right corner to manage audio devices.''''''Also please note that this is not a bug, because pulseaudio is not allowed to run under the root user.'''</big>|}</li>

<li>Execute the following command to set up the desktop version of the system again to use the orangepi user to automatically log in

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

=== How to disable the desktop in Linux desktop system ===

<li>First enter the following command on the command line, '''please remember to add sudo permissions'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo systemctl disable lightdm.service'''|}</li>

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

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo reboot'''|}</li><li>'''The command to reopen the desktop is as follows, please remember to add sudo permissions'''{| class="wikitable" style="width:800px;" |-|

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

orangepi@orangepi:~$ '''sudo systemctl enable lightdm.service'''|}</li></ol>

== Onboard LED light test instructions ==

# There are two LED lights on the development board, one green light and one red light. The default display of the LED lights when the system is started is as follows:

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

|-

|

| '''Bright'''

|}

::{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The green light on the development board can be controlled through software. The red light will be on continuously after power is turned on and cannot be controlled through software.'''

'''When you get the development board, you may find that even if the TF card with the system burned is not inserted into the development board, the green light will flash after connecting the power supply to the development board. This is because the 16MB SPI Flash on the development board is factory default. A miniature Linux system will be burned. This system will set the green light to flash after entering the kernel.'''

'''If the Linux system in the SPI Flash is cleared, then without inserting the TF card with the system programmed in it, you will only see a steady red light on the development board after turning on the power.'''</big>|}

<li>The method of setting the green light to turn on and off and flash is as follows:

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

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

~~root@orangepi~~{| class="wikitable" style="width:~~~# '''cd /sys/class/leds/green_led'''</li><li>The command to set the green light to stop flashing is as &gt~~800px; ~~follows:~~" ~~root@orangepi:/sys/class/leds/green_led# '''echo none > trigger'''</li>~~|-~~<li>The command to set the green light to be always on is as > follows:~~| root@orangepi:~~/sys/class/leds/green_led~~~# '''~~echo default-on > trigger'''</li><li>The command to set the green light flashing is as follows:root@orangepi:~~cd /sys/class/leds/green_led~~# '''echo heartbeat > trigger~~'''~~</li></ol>~~|}

</li>

<li>The command to set the green light to stop flashing is as follows:{| class="wikitable" style="width:800px;" |-| root@orangepi:/sys/class/leds/green_led# '''echo none > trigger'''|}</li><li>The command to set the green light to be always on is as > follows:{| class="wikitable" style="width:800px;" |-| root@orangepi:/sys/class/leds/green_led# '''echo default-on > trigger'''|}</li><li>The command to set the green light flashing is as follows:{| class="wikitable" style="width:800px;" |-| root@orangepi:/sys/class/leds/green_led# '''echo heartbeat > trigger'''|}</li></ol></li><li>If you do not need the LED light to flash after powering on, you can use the following method to turn off the green light flashing

<li>First run '''orangepi-config'''. Ordinary users remember to add ~~>~~ '''sudo''' permissions.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li>

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

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

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

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

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

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

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

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

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

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

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

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

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

</li></ol>

== Operation instructions for rootfs partition capacity of Linux system in TF card ==

<li>After burning the Linux image of the development board into the TF card, you can check the usage of the TF card capacity on the '''Ubuntu computer'''. The steps are as follows:{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that failure to perform this step will not affect the automatic expansion of the Linux system of the development board. Here I just want to explain how to check the capacity of the TF card after burning the Linux image on the TF card.'''</big>|}

<li>First install the gparted software on your Ubuntu computer

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt install -y gparted'''|}</li>

<li>Then open gparted

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo gparted'''|}</li><li>After opening gparted, you can select the TF card in the upper ~~>~~ right corner, and then you can see the usage of the TF card ~~>~~ capacity.

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

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

</li>

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

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

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

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

|-

|

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

|}

</li></ol>

=== Method to prohibit automatic expansion of rootfs partition capacity in TF card ===

<li>First, burn the Linux image of the development board into the TF card on the '''Ubuntu computer''' (Windows is not available), and '''then unplug and insert the TF card again'''.</li>

<li>Then the Ubuntu computer will usually automatically mount the partition of the TF card. If the automatic mounting is normal, use the ls command to see the following output.

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

|-

|

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

bin    boot    dev    etc    home    lib    lost+found    media    mnt    opt    proc    root    run sbin    selinux    srv    sys    tmp    usr    var|}</li>

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

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

|-

|

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

[sudo] test ~~的密码:~~ 的密码：root@test:~'''#'''|}</li>

<li>Then enter the root directory of the Linux system in the TF card and create a new file named '''.no_rootfs_resize'''

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

|-

|

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

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

root@test:/media/test/opi_root/root# '''touch .no_rootfs_resize'''

root@test:/media/test/opi_root/root# '''ls .no_rootfs*'''

'''.no_rootfs_resize'''|}</li>

<li>Then you can uninstall the TF card, then pull out the TF card and insert it into the development board to start. When the Linux system starts, when the '''.no_rootfs_resize''' file is detected in the '''/root''' directory, rootfs will not be automatically expanded.</li>

<li>After disabling the automatic expansion of rootfs, you can enter the Linux system and you can see that the total capacity of the rootfs partition is only 4GB (the image tested here is the desktop version), which is much smaller than the actual capacity of the TF card, indicating that the automatic expansion of rootfs has been successfully disabled.

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

|-

|

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

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

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

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

|}

After restarting, enter the Linux system of the development board again and you will see that the rootfs partition has been expanded to the actual capacity of the TF card.

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

~~Filesystem Size Used Avail Use% Mounted on~~

~~udev 925M 0 925M 0% /dev~~

~~tmpfs 199M 3.2M 196M 2% /run~~

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

~~~~

=== Method to manually expand the capacity of rootfs partition in TF card ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If the total capacity of the TF card is large, such as 128GB, and you do not want the rootfs partition of the Linux system to use all the capacity of the TF card, you only want to allocate a part of the capacity, such as 16GB, to the Linux system, and then the remaining capacity of the TF card can be used for other purposes. use. Then you can use the content introduced in this section to manually expand the capacity of the rootfs partition in TF.'''</big>|}

<li>First, burn the Linux image of the development board into the TF card on the '''Ubuntu computer''' (Windows is not available), and '''then unplug and insert the TF card again'''.</li>

<li>Then the Ubuntu computer will usually automatically mount the partition of the TF card. If the automatic mounting is normal, use the ls command to see the following output.

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

|-

|

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

bin    boot    dev    etc    home    lib    lost+found    media    mnt    opt    proc    root    run sbin    selinux    srv    sys    tmp    usr    var|}</li>

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

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

|-

|

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

[sudo] test ~~的密码:~~ 的密码：root@test:~'''#'''|}</li>

<li>Then enter the root directory of the Linux system in the TF card and create a new file named '''.no_rootfs_resize'''

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

|-

|

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

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

root@test:/media/test/opi_root/root# '''touch .no_rootfs_resize'''

root@test:/media/test/opi_root/root# '''ls .no_rootfs*'''

'''.no_rootfs_resize'''|}</li></ol>

~~~~

<li>Then install the gparted software on your Ubuntu computer

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt install -y gparted'''|}</li>

<li>Then open gparted

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

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

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

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

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

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

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

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

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

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

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

|-

|

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

<pspan style="margin-right: 80px;">Filesystem Size Used Avail Use% Mounted on</pspan> <pspan style="margin-right: 110px;">udev 925M 0 925M 0% /dev</pspan> <pspan style="margin-right: 100px;">tmpfs 199M 3.2M 196M 2% /run</pspan> <pspan style="margin-right: 25px;color:#FF0000">'''/dev/mmcblk0p1 ''''''7.7G ''''''3.2G ''''''4.4G ''''''42% /'''</pspan> |}</li></ol>

=== Method to reduce the capacity of rootfs partition in TF card ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''After configuring the application or other development environment in the Linux system of the TF card, if you want to back up the Linux system in the TF card, you can use the method in this section to reduce the size of the rootfs partition first, and then start the backup.'''</big>|}

<li>First, insert the TF card you want to operate on your '''Ubuntu computer''' (not Windows)</li>

<li>Then install the gparted software on your Ubuntu computer

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt install -y gparted'''|}</li>

<li>Then open gparted

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

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

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

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

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

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

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

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

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

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

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

|-

|

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

<pspan style="margin-right: 80px;">Filesystem Size Used Avail Use% Mounted on</pspan> <pspan style="margin-right: 110px;">udev 925M 0 925M 0% /dev</pspan> <pspan style="margin-right: 100px;">tmpfs 199M 3.2M 196M 2% /run</pspan> <pspan style="margin-right: 25px;color:#FF0000">'''/dev/mmcblk0p1 ''''''7.7G ''''''3.2G ''''''4.4G ''''''42% /'''</pspan> |}</li></ol>

== 24Pin expansion board interface pin description ==

[[File:zero2w-img105.png]]

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

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

|-

| style="width:50px;" | 1| style="width:200px;" | 100M network port

| Used to connect to a wired network to access the Internet

|-

| The default settings of the Linux system are KEY_1 (Number 1 key) and KEY_ENTER (Enter key), which can be customized as other function keys by modifying the dts configuration.

|}

</ol>

<li>The adaptation of Linux5.4 and Linux6.1 systems to expansion boards is shown in the following table</li~~></ol~~>

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

|-

| '''24pin expansion board function'''

|-

| '''TV-OUT'''

| '''NO'''| '''NO'''

|}

</ol>

~~~~

== How to use the two LRADC buttons on the 24pin expansion board ==

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

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

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

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

|-

| '''Linux kernel'''

| '''KEY_ENTER, the enter key'''

|}

</ol>

<li>Through the '''evtest''' command, we can check the key values reported after KEY1 and KEY2 are pressed.

<li>linux5.4

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

|-

|

orangepi@orangepizero2w:~$ '''evtest'''

No device specified, trying to scan all of /dev/input/event*

Not running as root, no devices may be available.

Available devices:

'''/dev/input/~~event0~~event0: sunxi-keyboard'''

/dev/input/event1: sunxi-ir

/dev/input/event2: axp2101-pek

/dev/input/event6: PixArt USB Optical Mouse

/dev/input/event7: BRLTTY 6.3 Linux Screen Driver Keyboard

Select the device event number [0-7]: '''0 #You need to enter the serial number corresponding to sunxi-keyboard'''

Input driver version is 1.0.1

Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100

Input device name: "sunxi-keyboard"

Supported events:

:Event type 0 (EV_SYN):Event type 1 (EV_KEY)::Event code 2 (KEY_1)::Event code 28 (KEY_ENTER)

Properties:

Testing ... (interrupt to exit)

'''#The following are the key values reported after pressing KEY1 and KEY2'''

Event: time 1693555298.132314, type 1 (EV_KEY), code 2 (KEY_1), value 1

Event: time 1693555298.132314, -------------- SYN_REPORT ------------

Event: time 1693555298.601042, -------------- SYN_REPORT ------------

Event: time 1693555298.710415, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0

Event: time 1693555298.710415, -------------- SYN_REPORT ------------|}</li>

<li>linux6.1

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

|-

|

orangepi@orangepizero2w:~$ evtest

No device specified, trying to scan all of /dev/input/event*

Available devices:

/dev/input/event0: axp20x-pek

'''/dev/input/~~event1~~event1: 5070800.lradc'''

/dev/input/event2: SONiX USB Keyboard

/dev/input/event3: SONiX USB Keyboard Consumer Control

/dev/input/event5: PixArt USB Optical Mouse

/dev/input/event6: sunxi-ir

Select the device event number [0-6]: '''1 #You need to enter the serial number corresponding to 5070800.lradc'''

Input driver version is 1.0.1

Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100

Input device name: "5070800.lradc"

Supported events:

:Event type 0 (EV_SYN):Event type 1 (EV_KEY)::Event code 2 (KEY_1)::Event code 28 (KEY_ENTER)

Properties:

Testing ... (interrupt to exit)

'''#The following are the key values reported after pressing KEY1 and KEY2'''

Event: time 1694075818.810877, type 1 (EV_KEY), code 2 (KEY_1), value 1

Event: time 1694075818.810877, -------------- SYN_REPORT ------------

Event: time 1694075819.536128, -------------- SYN_REPORT ------------

Event: time 1694075819.705009, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0

Event: time 1694075819.705009, -------------- SYN_REPORT ------------|}</li></ol>

</li>

<li>If you need to modify the key values reported after KEY1 and KEY2 are pressed, you can use the following method:

<li>There is a '''sun50i-h618-lradc-keys.dts''' file under the ~~>~~ '''/usr/src/''' path, through which we can define KEY1 and KEY2 ~~>~~ as the desired key values.{| class="wikitable" style="width:800px;" |-|

orangepi@orangepizero2w:~$ '''cd /usr/src/'''

orangepi@orangepizero2w:/usr/src$ '''ls *.dts'''

sun50i-h618-lradc-keys.dts|}</li><li>The contents of the '''sun50i-h618-lradc-keys.dts''' file in the ~~>~~ linux5.4 system are as follows:<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) KEY1 correspondence: modify '''key0 = <600 2>;''' where 2 is ~~>~~ the number corresponding to the desired key value</li><li>b) KEY2 correspondence: modify '''key1 = <800 28>;''' where 28 ~~>~~ is the number corresponding to the desired key value{| class="wikitable" style="width:800px;" |-|

orangepi@orangepizero2w:/usr/src$ '''sudo vim sun50i-h618-lradc-keys.dts'''

/dts-v1/;

/plugin/;

/ {

:fragment@0 {::target = <&keyboard>; ::__overlay__ {:::status = "okay"; :::'''key0 = <600 2>;''':::'''key1 = <800 28>;'''::};:};

};

~~~~|}~~;};~~</li></ol>

</li>

<li>The contents of the c.linux6.1 system ~~>~~ '''sun50i-h618-lradc-keys.dts''' file are as follows:<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) KEY1 corresponding: modify '''linux,code = <2>;''' the 2 in > it is the number corresponding to the desired key value</li><li>b) KEY2 correspondence: modify '''linux,code = <28>;''' the 28 > in it is the number corresponding to the desired key value{| class="wikitable" style="width:800px;" |-| orangepi@orangepizero2w:/usr/src$ '''sudo ''' '''vim ''' '''sun50i-h618-lradc-keys.dts'''

/dts-v1/;

/plugin/;

/ {

:fragment@0 {::target = <&r_lradc>; ::__overlay__ {:::status = "okay"; :::button-500 {::::label = "KEY_1";::::'''linux,code = <2>;''':::}; :::button-800 {::::label = "KEY_ENTER";::::'''linux,code = <28>;''':::};::};:};

};

~~button-800 {label = "KEY_ENTER";'''linux,code = <28>;'''};};~~|}~~;};~~</li></ol>

</li>

<li>For the key values that can be set, please refer to the macro ~~>~~ definition in the '''input-event-codes.h''' header file. Its ~~>~~ path in the kernel source code is:{| class="wikitable" style="width:800px;" |-|

orange-pi-5.4-sun50iw9/include/uapi/linux/input-event-codes.h

orange-pi-6.1-sun50iw9/include/uapi/linux/input-event-codes.h|}</li><li>After modification, use the '''orangepi-add-overlay''' command to ~~>~~ add the sun50i-h618-lradc-keys.dts configuration to the ~~>~~ system.{| class="wikitable" style="width:800px;" |-|

orangepi@orangepizero2w:/usr/src$ '''sudo orangepi-add-overlay sun50i-h618-lradc-keys.dts'''

Compiling the overlay

Copying the compiled overlay file to /boot/overlay-user/

Reboot is required to apply the changes|}</li><li>Then restart the system and the customized key values will take ~~>~~ effect.</li></ol>

</li></ol>

== Network connection test ==

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

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

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

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

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

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

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

:link/ether 5e:ac:14:a5:93:b3 brd ff:ff:ff:ff:ff:ff:inet '''192.168.1.16'''/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0::valid_lft 259174sec preferred_lft 259174sec:inet6 240e:3b7:3240:c3a0:e269:8305:dc08:135e/64 scope global dynamic noprefixroute::valid_lft 259176sec preferred_lft 172776sec:inet6 fe80::957d:bbbd:4928:3604/64 scope link noprefixroute::valid_lft forever preferred_lft forever|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''There are three ways to check the IP address after the development board is started:'''

'''1. Connect the HDMI display, then log in to the system and use the ip a s eth0 command to check the IP address.'''

'''2. Enter the ip a s eth0 command in the debugging serial terminal to view the IP address.'''

'''3. If there is no debugging serial port or HDMI display, you can also check the IP address of the development board's network port through the router's management interface. However, with this method, people often fail to see the IP address of the development board. If you can't see it, here's how to debug it:'''

:'''A) First check whether the Linux system has started normally. If the green light of the development board flashes, it usually means that it has started normally. If only the red light is on, or the red and green lights are not on, it means that the system has not started normally;''':'''B) Check whether the network cable is plugged in tightly, or try another network cable;''':'''C) Try another router (I have encountered many problems with routers, such as the router being unable to assign an IP address normally, or the IP address being assigned normally but not being visible in the router);''':'''D) If there is no router to replace, you can only connect an HDMI display or use the debugging serial port to check the IP address.''' '''In addition, it should be noted that the development board's DHCP automatic allocation of IP addresses does not require any settings.'''</big>|}</li>

<li>The command to test network connectivity is as follows. The '''ping''' command can be interrupted by pressing the '''Ctrl+C''' shortcut key.

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

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

PING www.a.shifen.com (14.215.177.38) from 192.168.1.12 eth0: 56(84) bytes of data.

--- www.a.shifen.com ping statistics ---

4 packets transmitted, 4 received, 0% packet loss, time 3002ms

rtt min/avg/max/mdev = 6.260/6.770/7.275/0.373 ms|}</li></ol>

=== WIFI connection test ===

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

==== Server version image connects to WIFI through commands ====

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

<li>First log in to the Linux system, there are three ways:

a. If the development board is connected to a network cable, you can remotely log in to '''[[\lOrange Pi Zero 2W#SSH remote login development board|the Linux system through ssh]].'''

b. If the development board is connected to the debugging serial port, you can use the serial port terminal to log in to the Linux system.

c. If the development board is connected to an HDMI display, you can log in to the Linux system through the HDMI display terminal.</li></ol>

~~~~<ol start="2" style="list-style-type: decimal;">

<li>First use the '''nmcli dev wifi''' command to scan the surrounding WIFI hotspots

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

|-

|

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

|}

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

<li>'''wifi_name''' needs to be replaced with the name of the WIFI ~~>~~ hotspot you want to connect to</li><li>'''wifi_passwd''' needs to be replaced with the password of the ~~>~~ WIFI hotspot you want to connect to.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo nmcli dev wifi connect wifi_name password wifi_passwd'''Device 'wlan0' successfully activated with 'cf937f88-ca1e-4411-bb50-61f402eef293'.|}</li></ol>

</li>

<li>You can check the IP address of the wifi through the '''ip addr show wlan0''' command

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

|-

|

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

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

:link/ether 23:8c:d6:ae:76:bb brd ff:ff:ff:ff:ff:ff:inet '''192.168.1.11'''/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0::valid_lft 259192sec preferred_lft 259192sec:inet6 240e:3b7:3240:c3a0:c401:a445:5002:ccdd/64 scope global dynamic noprefixroute::valid_lft 259192sec preferred_lft 172792sec:inet6 fe80::42f1:6019:a80e:4c31/64 scope link noprefixroute::valid_lft forever preferred_lft forever|}</li>

<li>Use the '''ping''' command to test the connectivity of the wifi network. The '''ping''' command can be interrupted by pressing the '''Ctrl+C''' shortcut key.

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

|-

|

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

PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0: 56(84) bytes of data.

--- www.orangepi.org ping statistics ---

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

rtt min/avg/max/mdev = 41.321/44.864/48.834/2.484 ms|}</li></ol>

==== Server version image connects to WIFI graphically ====

<li>First log in to the Linux system, there are three ways:

a. If the development board is connected to a network cable, you can remotely log in to '''[[\lOrange Pi Zero 2W#SSH remote login development board|the Linux system through ssh]].'''

b. If the development board is connected to the debugging serial port, you can use the serial port terminal to log in to the Linux system (please use MobaXterm for the serial port software, the graphical interface cannot be displayed using minicom)

c. If the development board is connected to an HDMI display, you can log in to the Linux system through the HDMI display terminal.</li>

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

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

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

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

</div></li>

<li>You can check the IP address of the wifi through the '''ip a s wlan0''' command

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

|-

|

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

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

:link/ether 24:8c:d3:aa:76:bb brd ff:ff:ff:ff:ff:ff:inet '''192.168.1.11'''/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0::valid_lft 259069sec preferred_lft 259069sec:inet6 240e:3b7:3240:c4a0:c401:a445:5002:ccdd/64 scope global dynamic noprefixroute::valid_lft 259071sec preferred_lft 172671sec:inet6 fe80::42f1:6019:a80e:4c31/64 scope link noprefixroute::valid_lft forever preferred_lft forever|}</li>

<li>Use the '''ping''' command to test the connectivity of the wifi network. The '''ping''' command can be interrupted by pressing the '''Ctrl+C''' shortcut key.

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

|-

|

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

PING www.orangepi.org (182.92.236.130) from 192.168.1.49 wlan0: 56(84) bytes of data.

--- www.orangepi.org ping statistics ---

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

rtt min/avg/max/mdev = 41.321/44.864/48.834/2.484 ms|}</li></ol>

==== Test method for desktop image ====

=== Method to create WIFI hotspot through create_ap ===

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

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

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

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

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

'''* access-point-name: Hotspot name'''

'''* passphrase: hotspot password'''</big>|}

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

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

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

|}

</li></ol>

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

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

|-

|

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

Config dir: /tmp/create_ap.wlan0.conf.TQkJtsz1

wlan0: STA ce:bd:9a:dd:a5:86 RADIUS: starting accounting session D4FBF7E5C604F169

wlan0: STA ce:bd:9a:dd:a5:86 WPA: pairwise key handshake completed (RSN)

wlan0: EAPOL-4WAY-HS-COMPLETED ce:bd:9a:dd:a5:86|}</li>

<li>At this time, take out your mobile phone and find the WIFI hotspot named '''orangepi''' created by the development board in the searched WIFI list. Then you can click '''orangepi''' to connect to the hotspot. The password is '''orangepi''' set above.

</div></li>

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

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

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

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

::inet '''192.168.1.150''' netmask 255.255.255.0 broadcast 192.168.1.255::inet6 fe80::938f:8776:5783:afa2 prefixlen 64 scopeid 0x20<link>::ether 4a:a0:c8:25:42:82 txqueuelen 1000 (Ethernet)::RX packets 25370 bytes 2709590 (2.7 MB)::RX errors 0 dropped 50 overruns 0 frame 0::TX packets 3798 bytes 1519493 (1.5 MB)::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0::device interrupt 83|}

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

</div></li>

<li>If you want to specify a different network segment for the connected device, you can specify it through the -g parameter. For example, use the -g parameter to specify the network segment of the access point AP as 192.168.2.1.{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <~~/li></ol~~big> '''Note that in the following command, Debian12 needs to modify eth0 to end0.'''</big>|}{| class="wikitable" style="width:800px;" |-|

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

|}

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

</div>

</li></ol>

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

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

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

|}

</li></ol>

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

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

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

|}

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

</div>

</li></ol>

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

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

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

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

|}

</li></ol>

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

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

|-

|

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

Config dir: /tmp/create_ap.wlan0.conf.zAcFlYTx

wlan0: STA ce:bd:9a:dd:a5:86 RADIUS: starting accounting session 937BF40E51897A7B

wlan0: STA ce:bd:9a:dd:a5:86 WPA: pairwise key handshake completed (RSN)

wlan0: EAPOL-4WAY-HS-COMPLETED ce:bd:9a:dd:a5:86|}</li>

<li>At this time, take out your mobile phone and find the WIFI hotspot named '''orangepi''' created by the development board in the searched WIFI list. Then you can click '''orangepi''' to connect to the hotspot. The password is '''orangepi''' set above.

</div></li>

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

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

|-

|

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

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

::inet '''192.168.1.150''' netmask 255.255.255.0 broadcast 192.168.1.255::inet6 fe80::938f:8776:5783:afa2 prefixlen 64 scopeid 0x20<link>::ether 4a:a0:c8:25:42:82 txqueuelen 1000 (Ethernet)::RX packets 25370 bytes 2709590 (2.7 MB)::RX errors 0 dropped 50 overruns 0 frame 0::TX packets 3798 bytes 1519493 (1.5 MB)::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0::device interrupt 83|}

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

</div></li>

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

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

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

|}

</li></ol>

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

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

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

|}

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

</div>

</li></ol>

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

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

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

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

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

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

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

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

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

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

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

[[File:zero2w-img138.png]] [[File:zero2w-img139.png]]</li>

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

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

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

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

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

<li>Then you can test the network connectivity to check whether the IP address is configured OK. The '''ping''' command can be interrupted by using the '''Ctrl+C''' shortcut key.

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

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

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

--- 192.168.1.47 ping statistics ---

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

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

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

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

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

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

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

</li>

<li>中Then enter the following command, where

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

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

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

|-

|

orangepi@orangepi:~$ '''sudo nmcli con mod "Wired connection 1" \

ipv4.addresses "192.168.1.110" \'''

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

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

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

</li>

<li>Then restart the linux system

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

<li>Then re-enter the Linux system and use the '''ip addr show eth0''' command to see that the IP address has been set to the desired value.

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

|-

|

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

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

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

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

'''Why do you need 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. The Linux system machine can mount it normally and then modify the configuration file in it.''' '''If you want to modify it in a Windows system, 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.''' '''In addition, if you have any problems when trying to use Paragon ExtFS for Windows, please solve it yourself. We will not answer questions.'''</big>|}

<li>First burn the Linux image of the development board you want to use into 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)</li>

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

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

|-

|

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

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

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

bin    boot    dev    etc    home    lib    lost+found    media    mnt    opt    proc    root    run sbin    selinux    srv    sys    tmp    usr    var|}</li>

<li>Then enter the '''/boot''' directory of the Linux system burned in the TF card

{| class="wikitable" style="width:800px;" |-| test@test:~$ '''cd /media/test/opi_root/boot/'''|}</li>

<li>Then copy the '''orangepi_first_run.txt.template''' to '''orangepi_first_run.txt'''. Through the orangepi_first_run.txt configuration file, you can set the 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.

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

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

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

<li>Variable usage instructions in the orangepi_first_run.txt file

<li>'''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</li><li>'''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.</li><li>'''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</li><li>'''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...)</li><li>'''FR_net_wifi_ssid''' Variable is used to set the name of the ~~>~~ WIFI hotspot you want to connect to</li><li>'''FR_net_wifi_key''' Variable is used to set the password of the ~~>~~ WIFI hotspot you want to connect to</li><li>'''FR_net_use_static''' Variables are used to set whether the ~~>~~ static IP address of the WIFI or Ethernet port needs to be ~~>~~ set.</li><li>'''FR_net_static_ip''' The variable is used to set the static IP ~~>~~ address. Please set it according to your actual situation.</li><li>'''FR_net_static_gateway''' Variables are used to set the gateway. ~~>~~ Please set according to your actual situation.</li></ol>

</li>

<li>Here are some specific setting examples:

<li>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: <ol style="list-style-type: ~~lower-alpha~~none;"><li>a) Set '''FR_net_change_defaults''' to 1</li><li>b) Set '''FR_net_wifi_enabled''' to '''1'''</li><li>c) Set '''FR_net_wifi_ssid''' to the name of the WIFI hotspot you ~~>~~ want to connect to</li><li>d) Set '''FR_net_wifi_key''' to the password of the WIFI hotspot ~~>~~ you want to connect to</li></ol>

</li>

<li>For example, 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:<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) Set '''FR_net_change_defaults''' to '''1'''</li><li>b) Set '''FR_net_wifi_enabled''' to '''1'''</li><li>c) Set '''FR_net_wifi_ssid''' to the name of the WIFI hotspot you ~~>~~ want to connect to</li><li>d) Set '''FR_net_wifi_key''' to the password of the WIFI hotspot ~~>~~ you want to connect to</li><li>e) Set '''FR_net_use_static''' to '''1'''</li><li>f) Set '''FR_net_static_ip''' to the desired IP address</li><li>g) Set '''R_net_static_gateway''' to the corresponding gateway ~~>~~ address</li></ol>

</li>

<li>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<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) Set '''FR_net_change_default''' to '''1'''</li><li>b) Set '''FR_net_ethernet_enabled''' to '''1'''</li><li>c) Set '''FR_net_use_static''' to '''1'''</li><li>d) Set '''FR_net_static_ip''' to the desired IP address</li><li>e) Set '''FR_net_static_gateway''' to the corresponding gateway ~~>~~ address</li></ol>

</li></ol>

</li>

<li>After modifying the orangepi_first_run.txt file, you can exit the /boot directory of the development board Linux system in the TF card, uninstall the TF card, and then insert the TF card into the development board to start.</li>

<li>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.{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''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>

~~'''After the~~ == SSH remote login 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.'''==

~~== SSH remote login development board ==~~|-| <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>|}

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

'''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, please do not doubt whether the orangepi password is incorrect, but look for other reasons.'''</big>|}

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

[[File:zero2w-img140.png]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If ssh cannot log in to the Linux system normally, first check whether the IP address of the development board can be pinged. If there is no problem with pinging, you can log in to the Linux system through the serial port or HDMI display and enter the following command on the development board before trying again. Can it be connected?: '''~~</li></ol>~~

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

~~'''If it still doesn't work, please try restarting the system.'''~~

'''If it still doesn't work, please try restarting the system.'''</big>

|}

</li></ol>

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

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

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

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

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

</li>

<li>You will then be prompted to enter a password. The default passwords for both root and orangepi users are orangepi.

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''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 any malfunction. Just press Enter after entering the password.'''</big>|}

== HDMI test ==

</div></li>

<li>After starting the Linux system, if there is image output on the HDMI display, it means that the HDMI interface is working normally.{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <~~/li></ol~~big>'''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>

~~'''When you want to connect the HDMI of the development board to the HDMI interface of your laptop, please first confirm that your laptop supports the HDMI in function'''~~

'''When HDMI does not display, please first check whether the HDMI cable is plugged in tightly. After confirming that the wiring is OK, you can try a different screen to see if there is any display.'''

~~~~

=== HDMI to VGA display test ===

<li>HDMI to VGA display test is as follows

[[File:zero2w-img147.png]]

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''When using HDMI to VGA display, the development board and the Linux system of the development board do not need to make any settings. 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.'''</big>|}</li></ol>

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

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

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

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

|-

|

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

verbosity=1

console=both

disp_mode='''1080p60'''

fb0_width=1920

fb0_height=1080|}</li><li>The disp_mode variable supports setting values as shown in the table below</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>

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

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

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

|-

|

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

|}

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

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

'''fb0_width=1920'''

'''fb0_height=1080'''|}

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

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

|-

| '''HDMI resolution'''

=== Framebuffer cursor setting ===

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

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

<li>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 '''vt.global_cursor_default=1''', it will be displayed cursor), then restart the system and you will see that the cursor has disappeared.

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

|-

|

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

verbosity=1

fb0_width=1920

fb0_height=1080

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

== How to use Bluetooth ==

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

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

|-

|

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

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

hci0: Type: Primary Bus: UART

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

<li>Use '''bluetoothctl''' to scan for Bluetooth devices

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

|-

|

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

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

Discovery stopped

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

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

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

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

|-

|

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

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

'''Pairing successful #Prompt pairing successful'''

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

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

<li>After successful pairing, the Bluetooth interface of the mobile phone will appear as follows:

</div></li>

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

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

|-

|

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

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

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

<li>How to connect Bluetooth devices

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

|-

|

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

Agent registered

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

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

'''[orangepi]# #If this prompt appears, the connection is successful.'''|}</li>

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

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

<li>First run '''orangepi-config'''. Ordinary users remember to add ~~>~~ '''sudo''' permissions.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li><li>Then select '''System'''

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

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

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

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

[[File:zero2w-img161.png]]</li>

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

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

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

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

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

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

=== 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*"''' major minor #blocks name 8 0 30044160 '''sda''' 8 1 30043119 '''sda1''' |}

<li>Use the mount command to mount the U disk to '''/mnt''', and then you can view the files in the U disk</li~~></ol~~>{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''sudo mount /dev/sda1 /mnt/'''

test.txt

|}</ol>

<li>After mounting, you can 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>

~~~~

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

<li>First insert the USB network card into the USB interface of the development board, and then insert the network cable into the USB network card to ensure that the network cable can access the Internet normally. If you can see the following log information through the '''dmesg''' command, it means that the USB network card is recognized normally.

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

|-

|

orangepi@orangepi:~$ '''dmesg | tail'''

[ 121.985016] usb 3-1: USB disconnect, device number 2

[ 127.763031] IPv6: ADDRCONF(NETDEV_UP): enx00e04c362017: link is not ready

[ 129.892465] r8152 3-1:1.0 enx00e04c362017: carrier on

[ 129.892583] IPv6: ADDRCONF(NETDEV_CHANGE): enx00e04c362017: link becomes ready|}</li>

<li>Then you can see the device node of the USB network card and the automatically assigned IP address through the ifconfig command

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

|-

|

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

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

::inet '''192.168.1.177''' netmask 255.255.255.0 broadcast 192.168.1.255::inet6 fe80::681f:d293:4bc5:e9fd prefixlen 64 scopeid 0x20<link>::ether 00:e0:4c:36:20:17 txqueuelen 1000 (Ethernet)::RX packets 1849 bytes 134590 (134.5 KB)::RX errors 0 dropped 125 overruns 0 frame 0::TX packets 33 bytes 2834 (2.8 KB)::TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0|}</li>

<li>The command to test network connectivity is as follows

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

|-

|

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

PING www.a.shifen.com (14.215.177.38) from 192.168.1.12 eth0: 56(84) bytes of data.

--- www.a.shifen.com ping statistics ---

4 packets transmitted, 4 received, 0% packet loss, time 3002ms

rtt min/avg/max/mdev = 6.260/6.770/7.275/0.373 ms|}</li></ol>

=== USB camera test ===

<li>First insert the USB camera into the USB interface of the Orange Pi development board</li>

<li>Then you can see through the lsmod command that the kernel automatically loads the following modules

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

|-

|

orangepi@orangepi:~$ '''lsmod'''

<pspan style="margin-right: 100px;">Module Size Used by</pspan> <pspan style="margin-right: 100px;">~~'''~~uvcvideo 106496 0~~'''~~</pspan> |}</li>

<li>Through the v4l2-ctl command, you can see that the device node information of the USB camera is/dev/video0

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

|-

|

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

orangepi@orangepi:~$ '''sudo''' '''apt install -y v4l-utils'''

orangepi@orangepi:~$ '''v4l2-ctl --list-devices'''

USB 2.0 Camera (usb-sunxi-ehci-1):

::/dev/video0|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the l in v4l2 is the lowercase letter l, not the number 1.''''''In addition, the serial number of the video may not always be video0, please refer to what you actually see.'''</big>|}</li>

<li>Use fswebcam to test the USB camera

<li>Install fswebcam

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

|-

|

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

orangepi@orangepi:~$ '''sudo apt-get install -y fswebcam'''|}</li><li>After installing fswebcam, you can use the following command to ~~>~~ take pictures<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) -d Option to specify the device node of the USB camera</li><li>b) --no-banner Used to remove watermarks from photos</li><li>c) -r option is used to specify the resolution of the photo</li><li>d) -S Option to skip previous frames</li><li>e) ./image.jpg Used to set the name and path of the generated ~~>~~ photo{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''sudo''' '''fswebcam -d /dev/video0 \'''

'''--no-banner -r 1280x720 -S 5 ./image.jpg'''|}</li></ol></li><li>In the server version of Linux system, after taking the picture, you can use the scp command to transfer the taken picture to the Ubuntu PC for mirror viewing.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''scp image.jpg [mailto:test@192.168.1.55:/home/test test@192.168.1.55:/home/test] （Modify the IP address and path according to the actual situation）'''|}

</li>

~~<li>In the server version of Linux system, after taking the picture, > you can use the scp command to transfer the taken picture to > the Ubuntu PC for mirror viewing.orangepi@orangepi:~$ '''scp image.jpg [mailto:test@192.168.1.55:/home/test test@192.168.1.55:/home/test] （Modify the IP address and path according to the actual situation）'''</li>~~<li>In the desktop version of Linux system, you can directly view ~~>~~ the captured pictures through the HDMI display</li></ol>

</li>

<li>Use mjpg-streamer to test the USB camera

<li>Download mjpg-streamer

<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) Github download address:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''git clone https://github.com/jacksonliam/mjpg-streamer'''|}</li><li>b) The image download address of Gitee is:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''git clone https://gitee.com/leeboby/mjpg-streamer'''|}</li></ol>

</li>

<li>Install dependent software packages

<ol style="list-style-type: ~~lower-alpha~~none;"><li>a) Ubuntu system{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt-get install -y cmake libjpeg8-dev'''|}</li><li>b) Debian system{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt-get install -y cmake libjpeg62-turbo-dev'''|}</li></ol>

</li>

<li>Compile and install mjpg-streamer

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

|-

|

orangepi@orangepi:~$ '''cd mjpg-streamer/mjpg-streamer-experimental'''

orangepi@orangepi:~/mjpg-streamer/mjpg-streamer-experimental$ '''make -j4'''

orangepi@orangepi:~/mjpg-streamer/mjpg-streamer-experimental$ '''sudo make install'''|}</li>

<li>Then enter the following command to start mjpg_streamer

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the serial number of the video is not always video0, please refer to what you actually see.'''</big>|}{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~/mjpg-streamer/mjpg-streamer-experimental$ '''export LD_LIBRARY_PATH=.'''

orangepi@orangepi:~/mjpg-streamer/mjpg-streamer-experimental$ '''sudo ./mjpg_streamer -i "./input_uvc.so -d \'''

'''/dev/video0 -u -f 30" -o "./output_http.so -w ./www"'''|}</li><li>Then enter ['''the IP address of the development board: 8080'''] ~~>~~ in the 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.

== Audio test ==

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

<li>The output of the linux5.4 system is as follows, where '''card 0: ~~>~~ audiocodec''' is the sound card device required for headphone ~~>~~ playback{| class="wikitable" style="width:800px;" |-|

root@orangepi:~# '''aplay -l'''

**** List of PLAYBACK Hardware Devices ****

'''card 0: audiocodec [audiocodec], device 0: soc@3000000:codec_plat-5096000.codec 5096000.codec-0 []'''

:'''Subdevices: 1/1''':'''Subdevice #0: subdevice #0'''|}</li><li>The output of the b.linux6.1 system is as follows, where ~~>~~ '''audiocodec''' is the sound card device required for headphone ~~>~~ playback.{| class="wikitable" style="width:800px;" |-|

root@orangepi:~# '''aplay -l'''

**** List of PLAYBACK Hardware Devices ****

'''card 0: audiocodec [audiocodec], device 0: CDC PCM Codec-0 [CDC PCM Codec-0]'''

:'''Subdevices: 1/1''':'''Subdevice #0: subdevice #0'''|}</li></ol>

</li>

<li>Then use the '''aplay''' command to play the audio, and the sound can be heard through the headphones

{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''aplay -D hw:0,0 /usr/share/sounds/alsa/audio.wav'''Playing WAVE 'audio.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <~~/li></ol~~big> '''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>

~~~~

==== HDMI audio playback test ====

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

<li>HDMI audio playback does not require other settings, just use the '''aplay''' command to play directly

{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''aplay -D hw:2,0 /usr/share/sounds/alsa/audio.wav'''|}</li></ol>

=== Test audio methods on desktop systems ===

<li>First open the volume control interface

[[File:zero2w-img166.png]]</li>

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

== Infrared reception test ==

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

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

<li>Install ir-keytable infrared test software</li~~></ol~~>{| class="wikitable" style="width:800px;" |-|

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

orangepi@orangepi:~$ '''sudo''' '''apt-get install -y ir-keytable'''

|}</ol>

<li>Then execute ir-keytable to view the information of the infrared device

<li>linux5.4 system output is as follows</li~~></ol~~>~~</li></ol>~~{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''ir-keytable'''

Found /sys/class/rc/rc0/ 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>

<li>The output of the linux6.1 system is as follows

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

|-

|

orangepi@orangepi:~$ '''ir-keytable'''

Found /sys/class/rc/rc0/ with:

::Name: sunxi-ir::Driver: sunxi-ir::Default keymap: rc-empty::Input device: /dev/input/event5::LIRC device: /dev/lirc0::Attached BPF protocols: Operation not permitted::Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm::Enabled kernel protocols: lirc::bus: 25, vendor/product: 0001:0001, version: 0x0100::Repeat delay = 500 ms, repeat period = 125 ms|}</li></ol> <~~!-- --~~/li></ol>

<li>Before testing the infrared reception function, you need to prepare an Orange Pi-specific infrared remote control. '''Other remote controls do not support it'''.

<li>Then enter the '''ir-keytable -t''' command in the terminal, and then use the infrared remote control to press the button against the infrared receiver of the Orange Pi development board to see the received key code in the terminal.

<li>linux5.4 system output is as follows</li~~></ol~~>~~</li></ol>~~{| class="wikitable" style="width:800px;" |-|

orangepi@orangepi:~$ '''sudo ir-keytable -t'''

1598339152.914715: event type EV_MSC(0x04): scancode = 0xfb0410

|}</ol>

<li>linux6.1 system output is as follows

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

|-

|

orangepi@orangepi:~$ '''sudo ir-keytable -c -p NEC -t'''

Old keytable cleared

202.063219: lirc protocol(nec): scancode = 0x45c

202.063249: event type EV_MSC(0x04): scancode = 0x45c

202.063249: event type EV_SYN(0x00).|}</li></ol></li></ol>

~~~~

== Temperature sensor ==

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

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

<li>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{| class="wikitable" style="width:800px;" |-|

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

'''ddr'''_thermal_zone

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

'''57410'''|}</li><li>sensor2: GPU temperature sensor, the first command is used to view ~~>~~ the type of temperature sensor, the second command is used to view ~~>~~ the value of the temperature sensor{| class="wikitable" style="width:800px;" |-|

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

'''gpu'''_thermal_zone

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

'''59273'''|}</li><li>sensor3: VE'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.{| class="wikitable" style="width:800px;" |-|

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

'''ve'''_thermal_zone

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

'''58949'''|}</li></ol>

=== How to check the temperature in linux6.1 system ===

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

|-

|

orangepi@orangepi:~$ '''sensors'''

Adapter: Virtual device

temp1:          +'''47.4°C''' (crit = +110.0°C)

gpu_thermal-virtual-0

Adapter: Virtual device

temp1:          +'''48.7°C''' (crit = +110.0°C)

ddr_thermal-virtual-0

Adapter: Virtual device

temp1:          +'''47.8°C''' (crit = +110.0°C)

ve_thermal-virtual-0

Adapter: Virtual device

temp1:          +'''47.2°C''' (crit = +110.0°C)|}

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

</div></li>

<li>The functions of the 40 Pin interface pins on the development board are as shown in the table below</li~~></ol~~>

<div style="display: flex;">{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"

|-

| '''~~GPIO序号~~GPIO NO.'''

| '''GPIO'''

| '''Function'''

| '''pin'''

|

~~| '''pin'''~~

~~| '''Function'''~~

~~| '''GPIO'''~~

~~| '''GPIO NO'''~~

|-

| style="text-align: left;"|

| '''3.3V'''

| '''1'''

|

~~| '''2'''~~

~~| '''5V'''~~

~~| style="text-align: left;"|~~

|-

| '''264'''

| '''TWI1-SDA'''

| '''3'''

|

~~| '''4'''~~

~~| '''5V'''~~

~~| style="text-align: left;"|~~

|-

| '''263'''

| '''TWI1-SCL'''

| '''5'''

|

~~| '''6'''~~

~~| '''GND'''~~

~~| style="text-align: left;"|~~

|-

| '''269'''

| '''PWM3/UART4_TX'''

| '''7'''

|~~| '''8'''| '''UART0_TX'''| '''PH0'''| '''224'''~~|-

| style="text-align: left;"|

| '''GND'''

| '''9'''

|

~~| '''10'''~~

~~| '''UART0_RX'''~~

~~| '''PH1'''~~

~~| '''225'''~~

|-

| '''226'''

| '''UART5_TX'''

| '''11'''

|

~~| '''12'''~~

~~| style="text-align: left;"|~~

~~| '''PI1'''~~

~~| '''257'''~~

|-

| '''227'''

| '''UART5_RX'''

| '''13'''

|

~~| '''14'''~~

~~| '''GND'''~~

~~| style="text-align: left;"|~~

|-

| '''261'''

| '''TWI0_SCL/UART2_TX'''

| '''15'''

|

~~| '''16'''~~

~~| '''PWM4/UART4_RX'''~~

~~| '''PI14'''~~

~~| '''270'''~~

|-

| style="text-align: left;"|

| '''3.3V'''

| '''17'''

|

~~| '''18'''~~

~~| style="text-align: left;"|~~

~~| '''PH4'''~~

~~| '''228'''~~

|-

| '''231'''

| '''SPI1_MOSI'''

| '''19'''

|

~~| '''20'''~~

~~| '''GND'''~~

~~| style="text-align: left;"|~~

|-

| '''232'''

| '''SPI1_MISO'''

| '''21'''

|

~~| '''22'''~~

~~| '''TWI0_SDA/UART2_RX'''~~

~~| '''PI6'''~~

~~| '''262'''~~

|-

| '''230'''

| '''SPI1_CLK'''

| '''23'''

|

~~| '''24'''~~

~~| '''SPI1_CS0'''~~

~~| '''PH5'''~~

~~| '''229'''~~

|-

| style="text-align: left;"|

| '''GND'''

| '''25'''

|

~~| '''26'''~~

~~| '''SPI1_CS1'''~~

~~| '''PH9'''~~

~~| '''233'''~~

|-

| '''266'''

| '''TWI2-SDA/UART3_RX'''

| '''27'''

|

~~| '''28'''~~

~~| '''TWI2-SCL/UART3_TX'''~~

~~| '''PI9'''~~

~~| '''265'''~~

|-

| '''256'''

| style="text-align: left;"|

| '''29'''

|

~~| '''30'''~~

~~| '''GND'''~~

~~| style="text-align: left;"|~~

|-

| '''271'''

| style="text-align: left;"|

| '''31'''

|~~| '''32'''| '''PWM1'''| '''PI11'''| '''267'''~~|-

| '''268'''

| '''PI12'''

| '''PWM2'''

| '''33'''

|

~~| '''34'''~~

~~| '''GND'''~~

~~| style="text-align: left;"|~~

|-

| '''258'''

| style="text-align: left;"|

| '''35'''

|

~~| '''36'''~~

~~| style="text-align: left;"|~~

~~| '''PC12'''~~

~~| '''76'''~~

|-

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

~~| '''PI4'''~~

~~| '''260'''~~

|-

| '''4'''

| '''5V'''

| style="text-align: left;"|

|-

| '''6'''

| '''GND'''

~~| '''39'''~~

|

~~| '''40'''~~

| style="text-align: left;"|

| ~~'''PI3'''| '''259'''~~|} ~~<ol start="3"~~ style="~~list-style~~text-~~type~~align: ~~decimal~~left;">|~~<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>~~ ~~== 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.deb~~PH0''' ~~'''After entering the system, you can run the gpio readall command. If you can see the following output, it means that wiringOP has been pre-installed and can be used normally.'''~~ ~~[[File: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.''' ~~<ol style="list-style-type: decimal;"><li>Download the code of wiringOPorangepi@orangepi:~$ '''sudo apt update'''orangepi@orangepi:~$ '''sudo apt install -y git'''orangepi@orangepi:~$ '''git clone https://github.com/orangepi-xunlong/wiringOP.git -b next''''''Note that the source code needs to download the code of wiringOP next branch. Please don't miss the -b next parameter.''''''If there is a problem downloading the code from GitHub, you can directly use the wiringOP source code that comes with the Linux image. The storage location is: /usr/src/wiringOP.'''</li><li>Compile and install wiringOPorangepi@orangepi:~$ '''cd wiringOP'''orangepi@orangepi:~/wiringOP$ '''sudo ./build clean'''orangepi@orangepi:~/wiringOP$ '''sudo ./build'''</li><li>The output of the test gpio readall command is as follows[[File:zero2w-img170.png]]</li></ol>~~ ~~== 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.'''~~ ~~=== 40pin GPIO port test ===~~ ~~<ol style="list-style-type: decimal;"><li>The following uses pin No. 7 - corresponding to GPIO PI13 - corresponding to wPi serial number 2 - as an example to demonstrate how to set the high and low levels of the GPIO port.[[File:zero2w-img171.png]]</li><li>First set the GPIO port to output mode, and the third parameter needs to be the serial number of the wPi corresponding to the input pin.root@orangepi:~/wiringOP# '''gpio mode 2 out'''</li><li>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.root@orangepi:~/wiringOP# '''gpio write 2 0'''</li>~~<li>Then set the GPIO port to output a high level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is 3.3v, it means the setting of the high level is successful.~~root@orangepi:~/wiringOP# '''gpio write 2 1'''</li><li>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.</li></ol>~~ ~~=== How to set the pull-down resistor of 40 Pin GPIO port ===~~ ~~<ol style="list-style-type: decimal;">~~<li>The following uses pin No. 7—corresponding to GPIO PI13—corresponding to wPi serial number 2—as an example to demonstrate how to set the pull-up and pull-down resistors of the GPIO port.~~[[File:zero2w-img171.png]]</li><li>First, you need to set the GPIO port to input mode, and the third parameter needs to be the serial number of the wPi corresponding to the input pin.root@orangepi:~/wiringOP# ''~~| '~~gpio mode 2 in~~''~~'</li><li>After setting to input mode, execute the following command to set the GPIO port to pull-up mode.root@orangepi:~/wiringOP#~~ 224'''~~gpio mode 2 up'''</li><li>Then enter the following command to read the level of the GPIO port. If the level is 1, it means that the pull-up mode is set successfully.root@orangepi:~/wiringOP# '''gpio read 2''''''1'''</li><li>Then execute the following command to set the GPIO port to pull-down moderoot@orangepi:~/wiringOP# '''gpio mode 2 down'''</li><li>Then enter the following command to read the level of the GPIO port. If the level is 0, it means that the pull-down mode is set successfully.root@orangepi:~/wiringOP# '''gpio read 2''''''0'''</li></ol>~~ ~~=== 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"~~

|-

|-

| '''12'''

| style="text-align: left;"|

~~| style="text-align: left;"|~~| '''~~3.3V~~PI1'''| '''1257'''|-| '''214'''| '''5VGND'''

| style="text-align: left;"|

|-

| '''~~264~~16'''| '''~~PI8~~PWM4/UART4_RX'''| '''~~TWI1-SDA~~PI14'''| '''3270'''|-| '''~~4'''| '''5V~~18'''~~| style="text-align: left;"|~~

| style="text-align: left;"|

| '''PH4'''

| '''228'''

|-

| '''~~263'''| '''PI7'''| '''TWI1-SCL'''| '''5'''~~|~~| '''6~~20'''

| '''GND'''

| style="text-align: left;"|

|-

| '''~~269~~22'''| '''~~PI13~~TWI0_SDA/UART2_RX'''| '''PI6'''| '''262'''|-| '''24'''| '''~~PWM3/UART4_TX~~SPI1_CS0'''| '''PH5'''| '''229'''|-| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''7233'''|-| '''828'''| '''~~UART0_TX~~TWI2-SCL/UART3_TX'''| '''~~PH0~~PI9'''| '''~~224~~265'''

|-

| '''30'''

| '''GND'''

| style="text-align: left;"|

~~| '''GND'''~~

~~| '''9'''~~

|

~~| '''10'''~~

~~| '''UART0_RX'''~~

~~| '''PH1'''~~

~~| '''225'''~~

|-

| '''~~226~~32'''| '''~~PH2~~PWM1'''| '''~~UART5_TX~~PI11'''| '''~~11'''~~|~~| '''12'''| style="text-align: left;"|| '''PI1'''| '''257~~267'''

|-

| '''~~227'''| '''PH3'''| '''UART5_RX'''| '''13'''~~|~~| '''14~~34'''

| '''GND'''

| style="text-align: left;"|

|-

| '''~~261~~36'''| ~~'''PI5'''| '''TWI0_SCL/UART2_TX'''~~style="text-align: left;"| ~~'''15'''~~|~~| '''16'''| '''PWM4/UART4_RX'''~~| '''~~PI14~~PC12'''| '''~~270~~76'''

|-

| '''38'''

| style="text-align: left;"|

~~| style="text-align: left;"|| '''3.3V'''| '''17'''~~|~~| '''18'''| style="text-align: left;"|~~| '''~~PH4~~PI4'''| '''~~228~~260'''

|-

| '''~~231'''| '''PH7'''| '''SPI1_MOSI'''| '''19'''~~|~~| '''20'''| '''GND~~40'''

| style="text-align: left;"|

~~| style="text-align: left;"|~~|-| '''~~232~~PI3'''| '''~~PH8~~259'''| ~~'''SPI1_MISO'''~~}</div>~~| '''21'''~~</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 '''223.3v'''</li></ol> ~~| '''TWI0_SDA~~</~~UART2_RX'''~~span> == How to install wiringOP ==~~| '''PI6'''~~{| ~~'''262'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

| <big>'''~~230~~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.'''| '''~~PH6~~The storage path of the compiled wiringOP deb package in orangepi-build is: '''| '''~~SPI1_CLK~~orangepi-build/external/cache/debs/arm64/wiringpi_x.xx.deb'''| '''23After 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>'''24WiringOP 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>| ~~'''SPI1_CS0'''~~} <ol style="list-style-type: decimal;">~~| '''PH5'''~~<li>Download the code of wiringOP{| ~~'''229'''~~class="wikitable" style="width:800px;"

|-

~~| style="text-align: left;"~~|~~| style="text-align~~orangepi@orangepi: ~~left;"|~~| ~$ '''~~GND~~sudo apt update'''| orangepi@orangepi:~$ '''25sudo apt install -y git'''|| orangepi@orangepi:~$ '''~~26'''| '''SPI1_CS1~~git clone https://github.com/orangepi-xunlong/wiringOP.git -b next'''| ~~'''PH9'''~~}{| ~~'''233'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

| ~~'''266'''~~| <big>'''~~PI10~~Note that the source code needs to download the code of wiringOP next branch. Please don'''| t miss the -b next parameter.'''~~TWI2-SDA~~</~~UART3_RX'''~~p>| '''27If 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.'''</big>|}~~| '''28'''~~</li>~~| '''TWI2-SCL~~<li>Compile and install wiringOP</~~UART3_TX'''| '''PI9'''~~p>{| ~~'''265'''~~class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~256~~cd wiringOP'''| orangepi@orangepi:~/wiringOP$ '''~~PI0~~sudo ./build clean'''~~| style="text-align~~orangepi@orangepi: ~~left;"|~~| ~/wiringOP$ '''29sudo ./build'''|}~~| '''30'''~~</li><li>The output of the test gpio readall command is as follows[[File:zero2w-img170.png]]</li></ol>~~| '''GND'''| style~~ == 40pin interface GPIO, I2C, UART, SPI and PWM testing == {| class="wikitable" style="~~text~~background-~~align~~color: ~~left~~#ffffdc;width:800px;"|

|-

| <big>'''~~271~~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>| ~~'''PI15'''~~} === 40pin GPIO port test === | <ol style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|>~~| '''31'''~~<li>The following uses pin No. 7 - corresponding to GPIO PI13 - corresponding to wPi serial number 2 - as an example to demonstrate how to set the high and low levels of the GPIO port.|[[File:zero2w-img171.png]]</li>~~| '''32'''~~<li>First set the GPIO port to output mode, and the third parameter needs to be the serial number of the wPi corresponding to the input pin.{| ~~'''PWM1'''| '''PI11'''| '''267'''~~class="wikitable" style="width:800px;"

|-

| ~~'''268'''~~| root@orangepi:~/wiringOP# '''~~PI12'''| '''PWM2'''| '''33~~gpio mode 2 out'''|}~~| '''34'''~~</li>~~| '''GND'''~~<li>Then set the GPIO port to output a low level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is 0v, it means the low level is set successfully.{| ~~style~~class="~~text-align: left;~~wikitable"|| style="~~text-align~~width: ~~left~~800px;"|

|-

| ~~'''258'''| ''~~root@orangepi:~/wiringOP# '~~PI2~~'''| gpio write 2 0'''|}</li>~~| '''36'''~~<li>Then set the GPIO port to output a high level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is 3.3v, it means the setting of the high level is successful.{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|~~| '''PC12'''| '''76'''~~

|-

~~| '''272'''| '''PI16'''| style="text-align: left;"|| '''37'''~~|~~| '''38'''| style="text-align: left;"|| '''PI4'''| '''260'''~~|-~~| style="text-align: left;"~~|~~| style="text-align~~root@orangepi: ~~left;"|| '''GND'''| '''39'''~~|~~| '''40~~~/wiringOP# '''| gpio write 2 1'''

|}

</li>

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

=== How to set the pull-down resistor of 40 Pin GPIO port ===

<li>~~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:<ol style="list-style-type: lower-alpha;"><li>First run '''orangepi-config'''~~following uses pin No. ~~Ordinary users remember~~ 7—corresponding to ~~add > '''sudo''' permissions.orangepi@orangepi:~$ '''sudo orangepi~~GPIO PI13—corresponding to wPi serial number 2—as an example to demonstrate how to set the pull-~~config'''</li><li>Then select '''System'''[[File:zero2w~~up and pull-~~img80~~down resistors of the GPIO port.~~png]]</li><li>Then select '''Hardware'''~~[[File:zero2w-~~img81~~img171.png]]</li><li>~~Then use~~ First, you need to set the ~~keyboard's arrow keys~~ GPIO port to ~~locate the position shown > in the figure below~~input mode, and ~~then use~~ the ~~'''space'''~~ third parameter needs to ~~select~~ be the ~~> dtbo configuration~~ serial number of the ~~SPI you want~~ wPi corresponding to ~~open~~the input pin.~~</li></ol></li></ol>~~ {| class="wikitable" style="width:800px;"

|-

| root@orangepi:~/wiringOP# '''~~dtbo configuration~~gpio mode 2 in'''|}</li><li>After setting to input mode, execute the following command to set the GPIO port to pull-up mode.{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''~~illustrate~~gpio mode 2 up'''|}</li><li>Then enter the following command to read the level of the GPIO port. If the level is 1, it means that the pull-up mode is set successfully.{| class="wikitable" style="width:800px;"

|-

| root@orangepi:~/wiringOP# '''~~spi1-cs0-cs1-spidev~~gpio read 2'''| '''~~Open cs0 and cs1 of spi1 at the same time~~1'''|}</li><li>Then execute the following command to set the GPIO port to pull-down mode{| class="wikitable" style="width:800px;"

|-

| root@orangepi:~/wiringOP# '''~~spi1-cs0-spidev~~gpio mode 2 down'''| ~~'''Only open cs0~~ }</li><li>Then enter the following command to read the level of ~~spi1'''~~the GPIO port. If the level is 0, it means that the pull-down mode is set successfully.{| class="wikitable" style="width:800px;"

|-

| root@orangepi:~/wiringOP# '''~~spi1-cs1-spidev~~gpio read 2'''| '''~~Only open cs1 of spi1~~0'''

|}

</li></ol>

~~[[File:zero2w~~

~~<ol start~~=~~"5" style~~=~~"list-style-type: lower-alpha;"><li>Then select '''<Save>''' to save[[File:zero2w-img83.png]]</li><li>Then select '''<Back>'''[[File:zero2w-img84.png]]</li><li>Then select '''<Reboot>'''to restart the system to make the > configuration take effect.[[File:zero2w-img85.png]]</li></ol>~~= 40pin SPI test ===

~~<ol start="2" style="list-style-type: decimal;"><li>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.orangepi@orangepi:~$ '''ls /dev/spidev1*'''/dev/spidev1.0 /dev/spidev1.1'''Note that only when you open spi1-cs0-cs1-spidev, you will see the device nodes of~~ # As can be seen from the ~~two spi.'''</li><li>Next~~table below, ~~start~~ the spi ~~loopback test. Do not short-circuit~~ available for the ~~mosi and miso pins of SPI1 first. The output result of running spidev_test~~ 40pin interface is ~~as follows. You can see that the data of TX~~ spi1, and RX there are ~~inconsistent.orangepi@orangepi:~$ '''sudo spidev_test -v -D /dev/spidev1.0'''spi mode: 0x0bits per word: 8max speed: 500000 Hz (500 KHz)TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF | ............................….</li><li>Then short-circuit the~~ two chip select pins ~~of SPI1 mosi (pin 19 in the 40pin interface)~~ cs0 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.orangepi@orangepi:~$ '''sudo spidev_test -v -D /dev/spidev1.0'''spi mode: 0x0bits per word: 8max speed: 500000 Hz (500 KHz)TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.RX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.</li></ol>~~ ~~=== 40pin I2C test ===~~cs1

~~# As can be seen from the table below, the i2c available for the 40pin interface are i2c0, i2c1 and i2c2~~<div style="display: flex;">::{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"

|-

| '''~~GPIO序号~~GPIO NO.'''

| '''GPIO'''

| '''Function'''

| '''pin'''

|

~~| '''pin'''~~

~~| '''Function'''~~

~~| '''GPIO'''~~

~~| '''GPIO NO.'''~~

|-

| style="text-align: left;"|

| '''3.3V'''

| '''1'''

|

~~| '''2'''~~

~~| '''5V'''~~

~~| style="text-align: left;"|~~

|-

| '''264'''

| '''TWI1-SDA'''

| '''3'''

|

~~| '''4'''~~

~~| '''5V'''~~

~~| style="text-align: left;"|~~

|-

| '''263'''

| '''TWI1-SCL'''

| '''5'''

|

~~| '''6'''~~

~~| '''GND'''~~

~~| style="text-align: left;"|~~

|-

| '''269'''

| '''PWM3/UART4_TX'''

| '''7'''

|

~~| '''8'''~~

~~| '''UART0_TX'''~~

~~| '''PH0'''~~

~~| '''224'''~~

|-

| style="text-align: left;"|

| '''GND'''

| '''9'''

|

~~| '''10'''~~

~~| '''UART0_RX'''~~

~~| '''PH1'''~~

~~| '''225'''~~

|-

| '''226'''

| '''UART5_TX'''

| '''11'''

|

~~| '''12'''~~

~~| style="text-align: left;"|~~

~~| '''PI1'''~~

~~| '''257'''~~

|-

| '''227'''

| '''UART5_RX'''

| '''13'''

|

~~| '''14'''~~

~~| '''GND'''~~

~~| style="text-align: left;"|~~

|-

| '''261'''

| '''TWI0_SCL/UART2_TX'''

| '''15'''

|

~~| '''16'''~~

~~| '''PWM4/UART4_RX'''~~

~~| '''PI14'''~~

~~| '''270'''~~

|-

| style="text-align: left;"|

| '''3.3V'''

| '''17'''

|

~~| '''18'''~~

~~| style="text-align: left;"|~~

~~| '''PH4'''~~

~~| '''228'''~~

|-

| '''231'''| '''PH7'''| '''SPI1_MOSI'''| '''19'''|-| '''20232'''| '''~~GND~~PH8'''| '''SPI1_MISO'''| '''21'''|-| '''230'''| '''PH6'''| '''SPI1_CLK'''| '''23'''|-

| style="text-align: left;"|

|-~~| '''232'''| '''PH8'''| '''SPI1_MISO'''| '''21'''~~|~~| '''22'''| '''TWI0_SDA/UART2_RX'''| '''PI6'''| '''262'''~~|-~~| '''230'''| '''PH6'''| '''SPI1_CLK'''| '''23'''~~|~~| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229'''~~|-~~| style="text-align: left;"|| style="text-align: left;"|~~| '''GND'''

| '''25'''

|

~~| '''26'''~~

~~| '''SPI1_CS1'''~~

~~| '''PH9'''~~

~~| '''233'''~~

|-

| '''266'''

| '''TWI2-SDA/UART3_RX'''

| '''27'''

|

~~| '''28'''~~

~~| '''TWI2-SCL/UART3_TX'''~~

~~| '''PI9'''~~

~~| '''265'''~~

|-

| '''256'''

| style="text-align: left;"|

| '''29'''

|

~~| '''30'''~~

~~| '''GND'''~~

~~| style="text-align: left;"|~~

|-

| '''271'''

| style="text-align: left;"|

| '''31'''

|

~~| '''32'''~~

~~| '''PWM1'''~~

~~| '''PI11'''~~

~~| '''267'''~~

|-

| '''268'''

| '''PWM2'''

| '''33'''

|

~~| '''34'''~~

~~| '''GND'''~~

~~| style="text-align: left;"|~~

|-

| '''258'''

| style="text-align: left;"|

| '''35'''

|

~~| '''36'''~~

~~| style="text-align: left;"|~~

~~| '''PC12'''~~

~~| '''76'''~~

|-

| '''272'''

| style="text-align: left;"|

| '''37'''

|

~~| '''38'''~~

~~| style="text-align: left;"|~~

~~| '''PI4'''~~

~~| '''260'''~~

|-

| 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;"||-| '''4'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"||-| '''6'''| '''GND'''| style="text-align: left;"|

| style="text-align: left;"|

~~| '''PI3'''~~

~~| '''259'''~~

|}

~~<ol start="2" style="list-style-type: decimal;">~~

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

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

~~<li>First run '''orangepi-config'''. Ordinary users remember to add > '''sudo''' permissions.~~

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

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

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

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

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

<li>Then use the keyboard's arrow keys to locate the position shown > in the picture below, and then use the '''space''' to select the > corresponding i2c configuration in the picture below.</li></ol>

~~</li></ol>~~

~~{| class="wikitable"~~

|-

| '''~~Multiplexing function in 40pin~~8'''| '''~~Corresponding dtbo configuration~~UART0_TX'''| '''PH0'''| '''224'''

|-

| '''~~40pin - i2c0~~10'''| '''~~pi-i2c0~~UART0_RX'''| '''PH1'''| '''225'''

|-

| '''~~40pin~~ 12'''| style="text- ~~i2c1~~align: left;"|| '''PI1'''| '''~~pi-i2c1~~257'''

|-

| '''~~40pin - i2c2~~14'''| '''~~pi-i2c2~~GND'''|} ~~[[File:zero2w-img173.png]]~~ ~~<ol start="5"~~ style="~~list~~text-~~style-type~~align: ~~lower-alpha~~left;">~~<li>Then select <Save> to save[[File:zero2w-img83.png]]</li><li>Then select '''<Back>'''[[File:zero2w-img84.png]]</li><li>Then select '''<Reboot>''' to restart the system to make the > configuration take effect.[[File:zero2w-img85.png]]</li></ol>~~ ~~<ol start="3" style="list-style-type: decimal;"><li>After starting the Linux system, first confirm that there is an open i2c device node under /devorangepi@orangepi:~$ '''ls /dev/i2c-*'''~~|~~'''/dev/i2c-*''''''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.''''''The method to accurately confirm the device node under /dev corresponding to the i2c bus is: '''</li></ol>~~ ~~<ol style="list-style-type: lower-alpha;"><li>'''First run the following command to check the corresponding relationship of i2c'''~~orangepi@orangepizero2w:~$ '''ls /sys/devices/platform/soc*/*/i2c-* | ~~grep "i2c-[0-9]"'''/sys/devices/platform/soc/5002000.i2c/i2c-0:/sys/devices/platform/soc/5002400.i2c/i2c-3:/sys/devices/platform/soc/5002800.i2c/i2c-4:/sys/devices/platform/soc/5002c00.i2c/i2c-5:/sys/devices/platform/soc/6000000.hdmi/i2c-2:/sys/devices/platform/soc/7081400.i2c/i2c-1:</li><li>'''In the above output'''</li></ol>~~ ~~<ol~~ style="~~list-style~~text-~~type~~align: ~~lower-alpha~~left;">~~<li>5002000 is the register base address of the i2c0 bus, and i2c-0 shown behind it is its corresponding i2c device node</li><li>5002400 is the register base address of the i2c1 bus, and i2c-3 shown behind it is its corresponding i2c device node</li><li>5002800 is the register base address of the i2c2 bus, and i2c-4 shown behind it is its corresponding i2c device node</li></ol>~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then start testing i2c, first install i2c-toolsorangepi@orangepi:~$ '''sudo apt-get update'''orangepi@orangepi:~$ '''sudo apt-get install -y i2c-tools'''</li><li>Then connect an i2c device to the i2c pin of the 40pin connector</li><li>Then use the '''i2cdetect -y x''' x command. If the address of the connected i2c device can be detected, it means that i2c can be used normally.'''Note that x in the i2cdetect -y x command needs to be replaced with the serial number of the device node corresponding to the i2c bus.''''''Different i2c device addresses are different. The 0x50 address in the picture below is just an example. Please refer to what you actually see.'''<div class="figure">~~ ~~[[File:zero2w-img174.png]]~~ ~~</div></li></ol>~~ ~~=== 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. {| ~~class="wikitable"~~

|-

|-

| '''18'''

| style="text-align: left;"|

~~| style="text-align: left;"|~~| '''~~3.3V~~PH4'''| '''1228'''|-| '''220'''| '''5VGND'''

| style="text-align: left;"|

|-

| '''~~264~~22'''| '''~~PI8~~TWI0_SDA/UART2_RX'''| '''~~TWI1~~PI6'''| '''262'''|-| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229'''|-| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''233'''|-| '''28'''| '''TWI2-~~SDA~~SCL/UART3_TX'''| '''3PI9'''|'''265'''|-| '''430'''| '''5VGND'''

| style="text-align: left;"|

|-

| '''~~263~~32'''| '''~~PI7~~PWM1'''| '''~~TWI1-SCL~~PI11'''| '''5267'''|-| '''634'''

| '''GND'''

| style="text-align: left;"|

|-

| '''~~269~~36'''| ~~'''PI13'''| '''PWM3/UART4_TX'''~~style="text-align: left;"| ~~'''7'''~~|~~| '''8'''| '''UART0_TX'''~~| '''~~PH0~~PC12'''| '''~~224~~76'''

|-

| '''38'''

| style="text-align: left;"|

| '''PI4'''

| '''260'''

|-

| '''40'''

| style="text-align: left;"|

| '''~~GND~~PI3'''| '''9259'''|}</div> <ol style="list-style-type: decimal;"><li>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:<ol style="list-style-type: lower-alpha;"><li>First run '''orangepi-config'''. Ordinary users remember to add '''sudo''' permissions.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''10sudo orangepi-config'''| }</li><li>Then select '''~~UART0_RX~~System'''[[File:zero2w-img80.png]]</li>| <li>Then select '''~~PH1~~Hardware'''[[File:zero2w-img81.png]]</li>| <li>Then use the keyboard's arrow keys to locate the position shown in the figure below, and then use the '''~~225~~space'''to select the dtbo configuration of the SPI you want to open.</li> {| class="wikitable" style="width:800px;text-align: center;"

|-

| '''~~226~~dtbo configuration'''| '''~~PH2'''| '''UART5_TX'''| '''11'''~~|~~| '''12'''| style="text-align: left;"|| '''PI1'''| '''257~~illustrate'''

|-

| '''~~227'''| '''PH3~~spi1-cs0-cs1-spidev'''| '''~~UART5_RX~~Open cs0 and cs1 of spi1 at the same time'''~~| '''13'''~~|~~| '''14'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~261~~spi1-cs0-spidev'''| '''~~PI5'''| '''TWI0_SCL/UART2_TX'''| '''15'''~~|~~| '''16'''| '''PWM4/UART4_RX'''| '''PI14'''| '''270~~Only open cs0 of spi1'''

|-

| ~~style="text~~'''spi1-cs1-~~align: left;"~~spidev'''|'''Only open cs1 of spi1'''| } [[File:zero2w-img172.png]]</ol><ol start="5" style="~~text~~list-~~align~~style-type: ~~left~~lower-alpha;"|>| <li>Then select '''~~3.3V~~<Save>'''to save[[File:zero2w-img83.png]]</li>| <li>Then select '''17<Back>'''|[[File:zero2w-img84.png]]</li>| <li>Then select '''18<Reboot>'''to restart the system to make the configuration take effect.| [[File:zero2w-img85.png]]</li></ol></li></ol><ol start="2" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|>| <li>Then check whether there is a '''~~PH4~~spidev1.x'''device node in the Linux system. If it exists, it means that the SPI1 configuration has taken effect.{| ~~'''228'''~~class="wikitable" style="width:800px;"

|-

| ~~'''231'''~~| orangepi@orangepi:~$ '''~~PH7~~ls /dev/spidev1*'''~~| '''SPI1_MOSI'''| '''19'''~~/dev/spidev1.0 /dev/spidev1.1|}{| ~~'''20'''| '''GND'''| style~~class="~~text-align: left;~~wikitable"|| style="~~text~~background-~~align~~color:#ffffdc;width: ~~left~~800px;"|

|-

| ~~'''232'''~~| <big>'''~~PH8~~Note that only when you open spi1-cs0-cs1-spidev, you will see the device nodes of the two spi.'''</big>| ~~'''SPI1_MISO'''~~}~~| '''21'''~~|~~| '''22'''~~</li>~~| '''TWI0_SDA~~<li>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.</~~UART2_RX'''~~p>{| ~~'''PI6'''| '''262'''~~class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~230~~sudo spidev_test -v -D /dev/spidev1.0'''spi mode: 0x0bits per word: 8max speed: 500000 Hz (500 KHz)TX | FF FF FF FF FF FF '''~~PH6~~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 '''~~SPI1_CLK~~FF FF FF FF FF FF'''FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF | ............................….| }</li><li>Then short-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.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo spidev_test -v -D /dev/spidev1.0'''spi mode: 0x0bits per word: 8max speed: 500000 Hz (500 KHz)TX | FF FF FF FF FF FF ''23'40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.RX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.|}</li></ol> === 40pin I2C test === # As can be seen from the table below, the i2c available for the 40pin interface are i2c0, i2c1 and i2c2 <div style="display: flex;">::{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''24GPIO NO.'''| '''~~SPI1_CS0~~GPIO'''| '''~~PH5~~Function'''| '''~~229~~pin'''

|-

| style="text-align: left;"|

| '''~~GND~~3.3V'''| '''251'''|-| '''26264'''| '''~~SPI1_CS1~~PI8'''| '''~~PH9~~TWI1-SDA'''| '''~~233~~3'''|-| '''263'''| '''v'''| '''TWI1-SCL'''| '''5'''

|-

| '''~~266~~269'''| '''~~PI10~~PI13'''| '''~~TWI2-SDA~~PWM3/~~UART3_RX~~UART4_TX'''| '''~~27'''~~|~~| '''28'''| '''TWI2-SCL/UART3_TX'''| '''PI9'''| '''265~~7'''

|-

~~| '''256'''~~

~~| '''PI0'''~~

| style="text-align: left;"|

| ~~'''29'''~~style="text-align: left;"|~~| '''30'''~~

| '''GND'''

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

| style="text-align: left;"|

| '''31'''

|

~~| '''32'''~~

~~| '''PWM1'''~~

~~| '''PI11'''~~

~~| '''267'''~~

|-

| '''268'''

| '''PWM2'''

| '''33'''

|

~~| '''34'''~~

~~| '''GND'''~~

~~| style="text-align: left;"|~~

|-

| '''258'''

| style="text-align: left;"|

| '''35'''

|

~~| '''36'''~~

~~| style="text-align: left;"|~~

~~| '''PC12'''~~

~~| '''76'''~~

|-

| '''272'''

| style="text-align: left;"|

| '''37'''

|

~~| '''38'''~~

~~| style="text-align: left;"|~~

~~| '''PI4'''~~

~~| '''260'''~~

|-

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

~~| '''PI3'''~~

~~| '''259'''~~

|}

~~<ol start="2" style="list-style-type: decimal;">~~

~~<li>In Linux systems, uart is turned off by default and needs to be turned on manually before it can be used. The opening steps are as follows:~~

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

~~<li>First run '''orangepi-config'''. Ordinary users remember to add > '''sudo''' permissions.~~

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

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

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

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

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

~~<li>Then use the keyboard's arrow keys to locate the position shown > in the picture below, and then use the '''space''' to select the > serial port you want to open.</li></ol>~~

~~</li></ol>~~

~~{| class="wikitable"~~

|-

| '''~~Multiplexing function in 40pin~~4'''| '''~~Corresponding dtbo configuration~~5V'''| style="text-align: left;"|| style="text-align: left;"|

|-

| '''~~40pin - uart2~~6'''| '''~~pi-uart2~~GND'''| style="text-align: left;"|| style="text-align: left;"|

|-

| '''~~40pin - uart3~~8'''| '''~~pi-uart3~~UART0_TX'''| '''PH0'''| '''224'''

|-

| '''~~40pin - uart4~~10'''| '''~~pi-uart4~~UART0_RX'''| '''PH1'''| '''225'''

|-

| '''~~40pin - uart5~~12'''| ~~'''ph-uart5'''~~|} ~~[[File:zero2w-img175.png]]~~ ~~<ol start="5"~~ style="~~list~~text-~~style-type~~align: ~~lower-alpha~~left;">~~<li>Then select '''<Save>''' to save[[File:zero2w-img83.png]]</li><li>Then select '''<Back>'''[[File:zero2w-img84.png]]</li><li>Then select '''<Reboot>''' to restart the system to make the > configuration take effect.[[File:zero2w-img85.png]]</li></ol>~~ ~~<ol start="3" style="list-style-type: decimal;"><li>After entering the Linux system, first confirm whether there is a uart5 device node under '''/dev''''''Note that the linux5.4 system is /dev/ttyASx.'''orangepi@orangepi:~$ '''ls /dev/ttyS*'''/dev/ttySx</li><li>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.</li><li>Use the '''gpio''' command in wiringOP to test the loopback function of the serial port as shown below. If you can see the following print, it means the serial port communication is normal.'''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.'''orangepi@orangepi:~$ '''gpio serial /dev/ttySx # linux-6.1 test command'''orangepi@orangepi:~$ '''gpio serial /dev/ttyASx # linux-5.4 test command'''Out: 0: -> 0Out: 1: -> 1Out: 2: -> 2Out: 3: -> 3^C</li></ol>~~ ~~=== PWM test method ===~~ ~~# As can be seen from the following table, the available pwm are pwm1, pwm2, pwm3 and pwm4.~~ ~~{| class="wikitable"~~|-~~| '''GPIO NO.'''| '''GPIO'''| '''Function'''| '''Pin'''~~|~~| '''Pin'''| '''Function'''~~| '''~~GPIO~~PI1'''| '''~~GPIO NO.~~257'''

|-

| '''14'''

| '''GND'''

| style="text-align: left;"|

|-| '''~~3.3V~~16'''| '''1PWM4/UART4_RX'''|| '''2PI14'''| '''5V270'''| ~~style="text~~-~~align: left;"~~|'''18'''

| style="text-align: left;"|

| '''PH4'''

| '''228'''

|-

| '''~~264~~20'''| '''~~PI8'''| '''TWI1-SDA'''| '''3'''~~|~~| '''4'''| '''5V~~GND'''

| style="text-align: left;"|

|-

| '''~~263~~22'''| '''~~PI7~~TWI0_SDA/UART2_RX'''| '''~~TWI1~~PI6'''| '''262'''|-| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229'''|-| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''233'''|-| '''28'''| '''TWI2-SCL/UART3_TX'''| '''5PI9'''|'''265'''|-| '''630'''

| '''GND'''

| style="text-align: left;"|

|-

| '''~~269~~32'''| '''~~PI13~~PWM1'''| '''~~PWM3/UART4_TX~~PI11'''| '''~~7'''~~|~~| '''8'''| '''UART0_TX'''| '''PH0'''| '''224~~267'''

|-

| '''34'''

| '''GND'''

| style="text-align: left;"|

~~| '''GND'''~~

~~| '''9'''~~

|

~~| '''10'''~~

~~| '''UART0_RX'''~~

~~| '''PH1'''~~

~~| '''225'''~~

|-

| '''~~226'''| '''PH2'''| '''UART5_TX'''| '''11'''~~|~~| '''12~~36'''

| style="text-align: left;"|

| '''~~PI1~~PC12'''| '''~~257~~76'''

|-

| '''~~227~~38'''~~| '''PH3'''| '''UART5_RX'''| '''13'''~~|~~| '''14'''| '''GND'''| style="text-align: left;"|~~

| style="text-align: left;"|

| '''PI4'''

| '''260'''

|-

| '''~~261~~40'''~~| '''PI5'''| '''TWI0_SCL/UART2_TX'''| '''15'''~~|~~| '''16'''| '''PWM4/UART4_RX'''| '''PI14'''| '''270'''~~|-

| style="text-align: left;"|

~~| style="text-align: left;"|~~| '''~~3.3V~~PI3'''| '''17259'''|}~~| '''18'''~~</div> <ol start="2" style="list-style-type: decimal;"><li>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: | <ol style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"|>| <li>First run '''~~PH4~~orangepi-config'''| . Ordinary users remember to add '''~~228~~sudo'''permissions.{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~231~~sudo orangepi-config'''| }</li><li>Then select '''~~PH7~~System'''~~| '''SPI1_MOSI'''~~[[File:zero2w-img80.png]]</li>| <li>Then select '''19Hardware'''|[[File:zero2w-img81.png]]</li>| <li>Then use the keyboard's arrow keys to locate the position shown in the picture below, and then use the '''20space'''to select the corresponding i2c configuration in the picture below.</li>~~| '''GND'''~~{| ~~style~~class="~~text-align: left;~~wikitable"|| style="width:800px;text-align: ~~left~~center;"|

|-

| '''~~232~~Multiplexing function in 40pin'''| '''~~PH8'''| '''SPI1_MISO'''| '''21'''~~|~~| '''22'''| '''TWI0_SDA/UART2_RX'''| '''PI6'''| '''262~~Corresponding dtbo configuration'''

|-

| '''~~230~~40pin - i2c0'''| '''~~PH6'''| '''SPI1_CLK'''| '''23'''~~|~~| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229~~pi-i2c0'''

|-

~~| style="text-align: left;"|| style="text-align: left;"|~~| '''~~GND~~40pin - i2c1'''| '''~~25'''~~|~~| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''233~~pi-i2c1'''

|-

| '''~~266~~40pin - i2c2'''| '''~~PI10~~pi-i2c2'''| ~~'''TWI2~~} [[File:zero2w-img173.png]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then select <Save> to save[[File:zero2w-~~SDA~~img83.png]]</~~UART3_RX'''~~li>| <li>Then select '''27<Back>'''|[[File:zero2w-img84.png]]</li>| <li>Then select '''28<Reboot>'''to restart the system to make the configuration take effect.~~| '''TWI2~~[[File:zero2w-~~SCL~~img85.png]]</li></ol></~~UART3_TX'''~~li></ol><ol start="3" style="list-style-type: decimal;">~~| '''PI9'''~~<li>After starting the Linux system, first confirm that there is an open i2c device node under /dev{| ~~'''265'''~~class="wikitable" style="width:800px;"

|-

| ~~'''256'''| ''~~orangepi@orangepi:~$ '~~PI0~~'''~~| style="text~~ls /dev/i2c-~~align: left;"|~~| *'''~~29'''~~|| '''30/dev/i2c-*'''| ~~'''GND'''~~}{| ~~style~~class="~~text-align: left;~~wikitable"|| style="~~text~~background-~~align~~color: ~~left~~#ffffdc;width:800px;"|

|-

| <big>'''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.''''''The method to accurately confirm the device node under /dev corresponding to the i2c bus is: '''</big> <ol style="list-style-type: lower-alpha;"><li>'''~~271~~First run the following command to check the corresponding relationship of i2c'''orangepi@orangepizero2w:~$ '''ls /sys/devices/platform/soc*/*/i2c-* | grep "i2c-[0-9]"'''/sys/devices/platform/soc/5002000.i2c/i2c-0:/sys/devices/platform/soc/5002400.i2c/i2c-3:/sys/devices/platform/soc/5002800.i2c/i2c-4:/sys/devices/platform/soc/5002c00.i2c/i2c-5:/sys/devices/platform/soc/6000000.hdmi/i2c-2:/sys/devices/platform/soc/7081400.i2c/i2c-1:</li> <li>'''~~PI15~~In the above output'''<ol style="list-style-type: none;"><li>a) 5002000 is the register base address of the i2c0 bus, and i2c-0 shown behind it is its corresponding i2c device node</li><li>b) 5002400 is the register base address of the i2c1 bus, and i2c-3 shown behind it is its corresponding i2c device node</li><li>c) 5002800 is the register base address of the i2c2 bus, and i2c-4 shown behind it is its corresponding i2c device node</li></ol></li></ol>|}</li></ol><ol start="4" style="list-style-type: decimal;"><li>Then start testing i2c, first install i2c-tools{| class="wikitable" style="~~text~~width:800px;" |-| orangepi@orangepi:~$ '''sudo apt-get update'''orangepi@orangepi:~$ '''sudo apt-get install -y i2c-tools'''|}</li><li>Then connect an i2c device to the i2c pin of the 40pin connector</li><li>Then use the '''i2cdetect -y x''' x command. If the address of the connected i2c device can be detected, it means that i2c can be used normally.{| class="wikitable" style="background-~~align~~color:#ffffdc;width: ~~left~~800px;"|-| <big>'''Note that x in the i2cdetect -y x command needs to be replaced with the serial number of the device node corresponding to the i2c bus.''''''31Different i2c device addresses are different. The 0x50 address in the picture below is just an example. Please refer to what you actually see.'''</big>|}<div class="figure"> [[File:zero2w-img174.png]] </div></li></ol> === 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;"|-| '''32GPIO NO.'''| '''~~PWM1~~GPIO'''| '''~~PI11~~Function'''| '''~~267~~pin'''

|-

~~| '''268'''~~

~~| '''PI12'''~~

~~| '''PWM2'''~~

~~| '''33'''~~

|

~~| '''34'''~~

~~| '''GND'''~~

| style="text-align: left;"|

| '''3.3V'''

| '''1'''

|-

| '''264'''

| '''PI8'''

| '''TWI1-SDA'''

| '''3'''

|-

| '''263'''

| '''PI7'''

| '''TWI1-SCL'''

| '''5'''

|-

| '''269'''

| '''PI13'''

| '''PWM3/UART4_TX'''

| '''7'''

|-

~~| '''258'''~~

~~| '''PI2'''~~

| style="text-align: left;"|

~~| '''35'''~~

|

~~| '''36'''~~

| style="text-align: left;"|

| '''~~PC12~~GND'''| '''769'''|-| '''226'''| '''PH2'''| '''UART5_TX'''| '''11'''|-| '''227'''| '''PH3'''| '''UART5_RX'''| '''13'''|-| '''261'''| '''PI5'''| '''TWI0_SCL/UART2_TX'''| '''15'''

|-

~~| '''272'''~~

~~| '''PI16'''~~

| style="text-align: left;"|

~~| '''37'''~~

|

~~| '''38'''~~

| style="text-align: left;"|

| '''~~PI4~~3.3V'''| '''~~260~~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'''| '''3925'''|-| '''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;"|| '''4037'''|-| style="text-align: left;"|| style="text-align: left;"|| '''~~PI3~~GND'''| '''~~259~~39'''

|}

{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"

|-

| '''pin'''

| '''Function'''

| '''GPIO'''

| '''GPIO NO.'''

|-

| '''2'''

| '''5V'''

| style="text-align: left;"|

|-

| '''4'''

| '''5V'''

| style="text-align: left;"|

|-

| '''6'''

| '''GND'''

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

|-

| '''16'''

| '''PWM4/UART4_RX'''

| '''PI14'''

| '''270'''

|-

| '''18'''

| style="text-align: left;"|

| '''PH4'''

| '''228'''

|-

| '''20'''

| '''GND'''

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

|-

| '''32'''

| '''PWM1'''

| '''PI11'''

| '''267'''

|-

| '''34'''

| '''GND'''

| 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>~~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:<ol style="list-style-type: lower-alpha;"><li>First run '''orangepi-config'''. Ordinary users remember to add ~~>~~ '''sudo''' permissions.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li><li>Then select '''System'''[[File:zero2w-img80.png]]</li><li>Then select '''Hardware'''[[File:zero2w-img81.png]]</li><li>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.~~[[File:zero2w-img176.png]]</li><li>Then select '''<Save>''' to save[[File:zero2w-img83.png]]</li><li>Then select '''<Back>'''[[File:zero2w-img84.png]]</li><li>Then select '''<Reboot>''' to restart the system to make the > configuration take effect.[[File:zero2w-img85.png]]</li></ol></li><li>After restarting, you can start the PWM test'''Please execute the following commands under the root user.'''<ol style="list-style-type: lower-alpha;"><li>Enter the following command on the command line to make pwm1 > output a 50Hz square waveroot@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip0/export'''root@orangepi:~# '''echo 20000000 > /sys/class/pwm/pwmchip0/pwm1/period'''root@orangepi:~# '''echo 1000000 > /sys/class/pwm/pwmchip0/pwm1/duty_cycle'''root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip0/pwm1/enable'''</li><li>Enter the following command on the command line to make pwm2 > output a 50Hz square wave</li></ol></li></ol>~~ ~~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>== 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.'''~~ ~~=== How to install wiringOP-Python ===~~ ~~<ol style="list-style-type: decimal;"><li>First install dependency packagesroot@orangepi:~# '''sudo apt-get update'''root@orangepi:~# '''sudo apt-get -y install git swig python3-dev python3-setuptools'''</li><li>Then use the following command to download the source code of wiringOP-Python~~</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.'''

~~If there is a problem downloading the code from GitHub, you can directly use the wiringOP~~{| class="wikitable" style="width:800px;text-~~Python source code that comes with the Linux image. The storage location is~~align: center;"|-| '''Multiplexing function in 40pin'''| '''Corresponding dtbo configuration'''|-| '''40pin - uart2'''| '''pi-uart2'''|-| '''40pin - uart3'''| '''~~/usr/src/wiringOP~~pi-~~Python~~uart3'''|-~~root@orangepi:~#~~ | '''~~git clone~~ 40pin -uart4'''| '''pi-~~recursive https://github.com/orangepi~~uart4'''|-~~xunlong/wiringOP~~| '''40pin -~~Python~~ uart5'''| '''ph-~~b next~~uart5'''|}

~~root~~[[File:zero2w-img175.png]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then select '''<Save>''' to save[[File:zero2w-img83.png]]</li><li>Then select '''<Back>'''[[File:zero2w-img84.png]]</li><li>Then select '''<Reboot>''' to restart the system to make the configuration take effect.[[File:zero2w-img85.png]]</li></ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>After entering the Linux system, first confirm whether there is a uart5 device node under '''/dev'''{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the linux5.4 system is /dev/ttyASx.'''</big>|}{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ls /dev/ttyS*'''/dev/ttySx|}</li><li>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.</li><li>Use the '''gpio''' command in wiringOP to test the loopback function of the serial port as shown below. If you can see the following print, it means the serial port communication is normal.{| class="wikitable" style="background-color:# ffffdc;width:800px;" |-| <big>'''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.'~~cd wiringOP~~''</big>|}{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gpio serial /dev/ttySx # linux-6.1 test command'''orangepi@orangepi:~$ '''gpio serial /dev/ttyASx # linux-~~Python~~5.4 test command'''

~~root@orangepi:~/wiringOP-Python# '''git submodule update --init --remote'''~~

~~<ol start="3" style="list-style-type: decimal;"><li>~~~~Then use the following command to compile wiringOP~~Out: 0: -~~Python and install it into the Linux system of the development board~~> 0~~root@orangepi~~Out: 1:~~~# '''cd wiringOP~~-~~Python'''~~> 1~~root@orangepi~~Out: 2:~~~/wiringOP~~-~~Python# '''python3 generate-bindings.py~~ > ~~bindings.i'''~~2~~root@orangepi~~Out: 3:~~~/wiringOP~~-~~Python# '''sudo python3 setup.py install'''~~> 3^C~~</li><li>Then enter the following command. If helpful information is output, it means wiringOP-Python is successfully installed. Press the '''q''' key to exit the help information interface.~~|}</li></ol>

~~root@orangepi:~/wiringOP~~

~~Help on module wiringpi:~~=== PWM test method ===

~~NAME~~# As can be seen from the following table, the available pwm are pwm1, pwm2, pwm3 and pwm4.

~~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.~~ <~~ol start="5"~~ div style="~~list-style-type~~display: ~~decimal~~flex;">~~<li>The steps to test whether wiringOP-Python is installed successfully under the python command line are as follows~~:~~<ol~~ :{| class="wikitable" style="~~list~~width:390px;margin-~~style~~right: 20px;text-~~type~~align: ~~lower-alpha~~center;">~~<li>First use the python3 command to enter the command line mode of > python3</li></ol>~~|-~~</li></ol>~~ ~~root@orangepi:~#~~ | '''~~python3~~GPIO NO.''' ~~<ol start="2" style="list-style-type: lower-alpha;"><li>Then import the python module of wiringpi</li></ol>~~ ~~>>>~~ | '''~~import wiringpi;~~GPIO''' ~~<ol start="3" style="list-style-type: lower-alpha;"><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)~~Function''' ~~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)~~ | ~~>>>~~ ~~=== 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.Pin''' ~~[[File:zero2w~~|-~~img170.png]]~~ ~~<ol~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">|~~<li>The following uses pin No. 7 - corresponding to GPIO PI13 - corresponding to wPi serial number 2 - as an example to demonstrate how to set the high and low levels of the GPIO port.[[File:zero2w-img171.png]]</li><li>The steps for testing directly with commands are as follows:<ol~~ | style="~~list-style~~text-~~type~~align: ~~lower-alpha~~left;">|~~<li>First set the GPIO port to output mode, where the first > parameter of the~~ | '''~~pinMode~~3.3V''' ~~function is the serial number of > the wPi corresponding to the pin, and the second parameter is > the GPIO mode.root@orangepi:~/wiringOP-Python#~~ | '''~~python3 -c "import wiringpi; \~~1'''~~~~|-| '''~~from wiringpi import GPIO; wiringpi.wiringPiSetup() ; \~~264'''~~~~| '''~~wiringpi.pinMode(2, GPIO.OUTPUT) ; "~~PI8'''~~</li>~~<li>Then set the GPIO port to output a low level. After setting, you > can use a multimeter to measure the voltage value of the pin. > If it is 0v, it means the low level is set successfully.~~root@orangepi:~/wiringOP-Python#~~ | '''~~python3~~ TWI1-~~c "import wiringpi; \~~SDA'''~~~~| '''~~from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\~~3'''~~~~|-| '''~~wiringpi.digitalWrite(2, GPIO.LOW)"~~263'''~~</li>~~<li>Then set the GPIO port to output a high level. After setting, > you can use a multimeter to measure the voltage value of the > pin. If it is 3.3v, it means the setting of the high level is > successful.~~root@orangepi:~/wiringOP-Python#~~ | '''~~python3 -c "import wiringpi; \~~PI7'''~~~~| '''~~from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\~~TWI1-SCL'''~~~~| '''~~wiringpi.digitalWrite(2, GPIO.HIGH)"~~5'''~~</li></ol></li>~~|-| '''<~~li>The steps for testing in the command line of python3 are as follows:<ol~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<li>First use the python3 command to enter the command line mode of > python3~~269<pspan>~~root@orangepi:~#~~ '''~~python3~~| '''</pspan style="color:#FF0000">PI13</lispan>~~<li>Then import the python module of wiringpi>>>~~ '''~~import wiringpi~~| '''<~~/p>~~<pspan style="color:#FF0000">~~>>> '''from wiringpi import GPIO'''~~PWM3</pspan></~~li><li>Then set the GPIO port to output mode, where the first parameter > of the '''pinMode~~UART4_TX'''~~function is the serial number of the wPi > corresponding to the pin, and the second parameter is the GPIO > mode.>>> '''wiringpi.wiringPiSetup()~~| '''<~~/p>~~<pspan style="color:#FF0000">07<pspan>~~>>> '~~''~~wiringpi.pinMode(2, GPIO.OUTPUT)~~'~~''</li>~~<li>Then set the GPIO port to output a low level. After setting, you > can use a multimeter to measure the voltage value of the pin. > If it is 0v, it means the low level is set successfully.|-~~&gt~~| style="text-align: left;~~>> '''wiringpi.digitalWrite(2, GPIO.LOW)'''</li>~~"|~~<li>Then set the GPIO port to output a high level. After setting, &gt~~| style="text-align: left; ~~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.~~"|~~>>>~~ | '''~~wiringpi.digitalWrite(2, GPIO.HIGH)~~GND'''~~</li></ol></li><li>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~~9''' ~~test program will set the voltage of all GPIO ports in the 40 Pin of the development board to continuously change high and low.root@orangepi:~/wiringOP~~|-~~Python#~~ | '''~~cd examples~~226'''~~root@orangepi:~/wiringOP-Python/examples#~~ | '''~~ls blink.py~~PH2'''~~~~| '''~~blink.py~~UART5_TX'''~~root@orangepi:~/wiringOP-Python/examples~~| '''~~# python3 blink.py~~11'''~~</li></ol>~~ ~~=== 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"~~

|-

|-

| style="text-align: left;"|

| '''3.3V'''

| '''117'''|~~| '''2'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~264~~231'''| '''~~PI8~~PH7'''| '''~~TWI1-SDA~~SPI1_MOSI'''| '''319'''|~~| '''4'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~263~~232'''| '''~~PI7~~PH8'''| '''~~TWI1-SCL~~SPI1_MISO'''| '''521'''|~~| '''6'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~269~~230'''| '''~~PI13~~PH6'''| '''~~PWM3/UART4_TX~~SPI1_CLK'''| '''~~7'''~~|~~| '''8'''| '''UART0_TX'''| '''PH0'''| '''224~~23'''

|-

| style="text-align: left;"|

| '''GND'''

| '''925'''|-| '''10266'''| '''~~UART0_RX~~PI10'''| '''~~PH1~~TWI2-SDA/UART3_RX'''| '''~~225~~27'''

|-

| '''~~226~~256'''| '''~~PH2'''| '''UART5_TX'''| '''11'''~~|~~| '''12~~PI0'''

| style="text-align: left;"|

| '''~~PI1'''| '''257~~29'''

|-

| '''~~227~~271'''| '''~~PH3'''| '''UART5_RX'''| '''13'''~~|~~| '''14'''| '''GND~~PI15'''

| style="text-align: left;"|

| '''31'''

|-

| '''268'''

| '''PI12'''

| '''PWM2'''

| '''33'''

|-

| '''258'''

| '''PI2'''

| style="text-align: left;"|

| '''35'''

|-

| '''~~261~~272'''| '''~~PI5~~PI16'''| ~~'''TWI0_SCL/UART2_TX'''| '''15'''~~|style="text-align: left;"| ~~'''16'''| '''PWM4/UART4_RX'''| '''PI14'''~~| '''~~270~~37'''

|-

| style="text-align: left;"|

| '''3GND'''| '''39'''|}{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''Pin'''| '''Function'''| '''GPIO'''| '''GPIO NO.3V'''|-| '''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'''| '''17270'''|-| '''18'''| style="text-align: left;"|| '''PH4'''| '''228'''

|-

~~| '''231'''~~

~~| '''PH7'''~~

~~| '''SPI1_MOSI'''~~

~~| '''19'''~~

|

| '''20'''

| '''GND'''

| style="text-align: left;"|

|-

~~| '''232'''~~

~~| '''PH8'''~~

~~| '''SPI1_MISO'''~~

~~| '''21'''~~

|

| '''22'''

| '''TWI0_SDA/UART2_RX'''

| '''262'''

|-

~~| '''230'''~~

~~| '''PH6'''~~

~~| '''SPI1_CLK'''~~

~~| '''23'''~~

|

| '''24'''

| '''SPI1_CS0'''

| '''229'''

|-

~~| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''25'''~~|| '''26'''

| '''SPI1_CS1'''

| '''PH9'''

| '''233'''

|-

~~| '''266'''~~

~~| '''PI10'''~~

~~| '''TWI2-SDA/UART3_RX'''~~

~~| '''27'''~~

|

| '''28'''

| '''TWI2-SCL/UART3_TX'''

| '''265'''

|-

~~| '''256'''~~

~~| '''PI0'''~~

~~| style="text-align: left;"|~~

~~| '''29'''~~

|

| '''30'''

| '''GND'''

| style="text-align: left;"|

|-

| '''~~271'''| '''PI15'''~~| 32'''| '''PWM1'''| '''PI11'''| '''267'''

|-

~~| '''268'''~~

~~| '''PI12'''~~

~~| '''PWM2'''~~

~~| '''33'''~~

|

| '''34'''

| '''GND'''

| style="text-align: left;"|

|-

~~| '''258'''~~

~~| '''PI2'''~~

~~| style="text-align: left;"|~~

~~| '''35'''~~

|

| '''36'''

| style="text-align: left;"|

| '''76'''

|-

~~| '''272'''~~

~~| '''PI16'''~~

~~| style="text-align: left;"|~~

~~| '''37'''~~

|

| '''38'''

| style="text-align: left;"|

| '''260'''

|-

~~| style="text-align: left;"|~~

~~| '''GND'''~~

~~| '''39'''~~

|

| '''40'''

| style="text-align: left;"|

| '''259'''

|}

</div>

<li>~~In Linux systems, spi1~~ pwm is turned off by default in Linux systems and needs to be turned on manually ~~before~~ to use it ~~can be used~~. The opening steps are as follows:

<li>First run '''orangepi-config'''. Ordinary users remember to add ~~>~~ '''sudo''' permissions.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li>

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

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

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

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

<li>Then use the keyboard's arrow keys to locate the position shown ~~>~~ in the figure below, and then use the '''space''' to select the ~~> dtbo~~ configuration of corresponding to the ~~SPI~~ pwm you want to open.[[File:zero2w-img176.png]]</lip></olli></li>Then select '''<Save>''' to save</olp> ~~{| class="wikitable"~~|[[File:zero2w-img83.png]]</li>| <li>Then select '''~~dtbo configuration~~<Back>'''[[File:zero2w-img84.png]]</li>| <li>Then select '''~~illustrate~~<Reboot>'''to restart the system to make the configuration take effect.[[File:zero2w-img85.png]]</li></ol></li><li>After restarting, you can start the PWM test{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

| <big>'''~~spi1-cs0-cs1-spidev~~Please execute the following commands under the root user.'''</big>| ~~'''Open cs0 and cs1 of spi1 at~~ }<ol style="list-style-type: lower-alpha;"><li>Enter the following command on the ~~same time'''~~command line to make pwm1 output a 50Hz square wave{| class="wikitable" style="width:800px;"

|-

| root@orangepi:~# '''~~spi1-cs0-spidev~~echo 1 > /sys/class/pwm/pwmchip0/export'''| root@orangepi:~# '''~~Only open cs0 of spi1~~echo 20000000 > /sys/class/pwm/pwmchip0/pwm1/period'''|-| root@orangepi:~# '''~~spi1-cs1-spidev~~echo 1000000 > /sys/class/pwm/pwmchip0/pwm1/duty_cycle'''| root@orangepi:~# '''~~Only open cs1 of spi1~~echo 1 > /sys/class/pwm/pwmchip0/pwm1/enable'''

|}

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

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

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

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

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

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

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

~~~~

~~<ol start="3" style="list-style-type: decimal;">~~

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

~~orangepi@orangepi:~$ '''ls /dev/spidev1*'''~~

~~/dev/spidev1.0 /dev/spidev1.1~~

~~'''Note that only when you open spi1-cs0-cs1-spidev, you will see the device nodes of the two spi.'''</li>~~

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

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

~~<li>'''--channel''': Specify the channel number of SPI</li>~~

~~<li>'''--port''': Specify the port number of the SPI</li></ol>~~

</li>

<li>~~Without shorting~~ Enter the ~~mosi and miso pins of SPI1,~~ following command on the command line to make pwm2 output ~~result of running spidev_test.py is as follows. You can see that the data of TX and RX are inconsistent.~~a 50Hz square wave<p/li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~~~/wiringOP-Python~~# '''~~cd examples~~echo 2 > /sys/class/pwm/pwmchip0/export'''~~</li></ol>~~

root@orangepi:~~~/wiringOP-Python/examples~~# '''~~python3 spidev_test.py \~~echo 20000000 > /sys/class/pwm/pwmchip0/pwm2/period'''

root@orangepi:~# '''~~--channel 1 --port 0~~echo 1000000 > /sys/class/pwm/pwmchip0/pwm2/duty_cycle'''

~~spi mode~~root@orangepi: ~~0x0~~~# '''echo 1 > /sys/class/pwm/pwmchip0/pwm2/enable'''|}</ol><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>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''echo 3 > /sys/class/pwm/pwmchip0/export'''

~~max speed~~root@orangepi: ~~500000 Hz (500 KHz)~~~# '''echo 20000000 > /sys/class/pwm/pwmchip0/pwm3/period'''

~~Opening device~~ root@orangepi:~# '''echo 1000000 > /~~dev~~sys/~~spidev1.1~~class/pwm/pwmchip0/pwm3/duty_cycle'''

~~TX | FF FF FF FF FF FF~~ root@orangepi:~# '''~~40 00 00 00 00 95~~echo 1 > /sys/class/pwm/pwmchip0/pwm3/enable''' ~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D~~ |}</ol><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>{| class="wikitable" style="width:800px;" |~~......~~-| root@~~.......…|~~orangepi:~# '''echo 4 > /sys/class/pwm/pwmchip0/export'''

~~RX | FF FF FF FF FF FF~~ root@orangepi:~# '''~~FF FF FF FF FF FF~~echo 20000000 > /sys/class/pwm/pwmchip0/pwm4/period''' ~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |.............….|~~

~~<ol start="6" style="list-style-type: decimal;">~~<li>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.~~~~root@orangepi:~~~/wiringOP-Python~~# '''~~cd examples~~echo 1000000 > /sys/class/pwm/pwmchip0/pwm4/duty_cycle'''~~</li></ol>~~

root@orangepi:~~~/wiringOP-Python/examples~~# '''~~python3 spidev_test.py \~~echo 1 > /sys/class/pwm/pwmchip0/pwm4/enable'''|}

~~'''--channel 1 --port 0'''~~<div class="figure">

~~spi mode~~[[File: ~~0x0~~zero2w-img177.png]]

~~max speed: 500000 Hz (500 KHz)~~</div></ol></li></ol>

~~Opening device /dev/spidev1.1~~== How to install and use wiringOP-Python ==

TX {| ~~FF FF FF FF FF FF~~ class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~40 00 00 00 00 95~~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.''' ~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D~~ </big>|~~......@.......…~~}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-|<big>'''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'''

~~RX | FF FF FF FF FF FF~~ '''~~40 00 00 00 00 95~~Also please note that all the following commands are operated under the root user.''' ~~FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…~~</big>|}

=== ~~40pin I2C test~~ How to install wiringOP-Python ===

<ol style="list-style-type: decimal;"><li>First install dependency packages{| class="wikitable" style="width:800px;" |-| root@orangepi:~# ~~As can be seen from~~ '''sudo apt-get update'''root@orangepi:~# '''sudo apt-get -y install git swig python3-dev python3-setuptools'''|}</li><li>Then use the following command to download the ~~table below,~~ source code of wiringOP-Python</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that the ~~i2c available for~~ following git clone--recursive command will automatically download the ~~40pin interface~~ source code of wiringOP, because wiringOP-Python depends on wiringOP. Please make sure there are ~~i2c0, i2c1 and i2c2~~no errors during the download process due to network problems.'''

'''If there is a problem downloading the code from GitHub, you can directly use the wiringOP-Python source code that comes with the Linux image. The storage location is: /usr/src/wiringOP-Python'''</big>|}{| class="wikitable" style="width:800px;"

|-

| root@orangepi:~# '''~~GPIO NO~~git clone --recursive https://github.com/orangepi-xunlong/wiringOP-Python -b next'''| root@orangepi:~# '''~~GPIO~~cd wiringOP-Python'''~~| '''Function'''~~| root@orangepi:~/wiringOP-Python# '''~~Pin~~git submodule update --init --remote'''|}~~| '''Pin'''~~</ol>~~| '''Function'''~~<ol start="3" style="list-style-type: decimal;">~~| '''GPIO'''~~<li>Then use the following command to compile wiringOP-Python and install it into the Linux system of the development board{| ~~'''GPIO NO.'''~~class="wikitable" style="width:800px;"

|-

~~| style="text-align: left;"~~|~~| style="text-align~~root@orangepi: ~~left;"|~~| ~# '''~~3.3V~~cd wiringOP-Python'''| root@orangepi:~/wiringOP-Python# '''1python3 generate-bindings.py > bindings.i'''|| root@orangepi:~/wiringOP-Python# '''2sudo python3 setup.py install'''| }</li><li>Then enter the following command. If helpful information is output, it means wiringOP-Python is successfully installed. Press the '''5Vq'''key to exit the help information interface.</li>{| ~~style~~class="~~text-align: left;~~wikitable"|| style="~~text-align~~width: ~~left~~800px;"|

|-

| root@orangepi:~/wiringOP-Python# '''~~264~~python3 -c "import wiringpi; help(wiringpi)"'''~~| '''PI8'''| '''TWI1~~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--~~SDA'''~~modify~~| '''3'''~~|: # the SWIG interface file instead.| ~~'''4'''~~}~~| '''5V'''~~</ol>| <ol start="5" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|><li>The steps to test whether wiringOP-Python is installed successfully under the python command line are as follows:| <ol style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"><li>First use the python3 command to enter the command line mode of > python3</li>{|class="wikitable" style="width:800px;"

|-

| ~~'''263'''~~| root@orangepi:~# '''~~PI7~~python3'''| ~~'''TWI1-SCL'''~~}~~| '''5'''~~</ol>|~~| '''6'''| '''GND'''~~| <ol start="2" style="~~text~~list-~~align~~style-type: ~~left~~lower-alpha;"|><li>Then import the python module of wiringpi</li>{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|

|-

| >>> '''~~269~~import wiringpi;'''| ~~'''PI13'''~~}~~| '''PWM3~~</~~UART4_TX'''~~ol>~~| '''7'''~~<ol start="3" style="list-style-type: lower-alpha;">|<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>{| ~~'''8'''| '''UART0_TX'''| '''PH0'''| '''224'''~~class="wikitable" style="width:800px;"

|-

| ~~style="text-align: left~~>>"|~~| style="text-align: left~~>"|| '''~~GND~~help(wiringpi)'''~~| '''9'''~~|Help on module wiringpi: NAME :wiringpi DESCRIPTION : # This file was automatically generated by SWIG (http://www.swig.org). ~~| '''10'''~~: # Version 4.0.2~~| '''UART0_RX'''| '''PH1'''~~: #~~| '''225'''~~|: # 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) :| ~~'''226'''~~GPIO(pinmode=0) :| ~~'''PH2'''~~ >>>| ~~'''UART5_TX'''~~}</ol></li></ol>~~| '''11'''~~|=== 40pin GPIO port test ===~~| '''12'''~~{| class="wikitable" style="~~text~~background-~~align~~color:#ffffdc;width: ~~left~~800px;"|~~| '''PI1'''| '''257'''~~

|-

| <big>'''~~227~~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.'''</big> [[File:zero2w-img170.png| ~~'''PH3'''~~center]]| ~~'''UART5_RX'''~~} <ol style="list-style-type: decimal;"><li>The following uses pin No. 7 - corresponding to GPIO PI13 - corresponding to wPi serial number 2 - as an example to demonstrate how to set the high and low levels of the GPIO port.~~| '''13'''~~[[File:zero2w-img171.png]]</li>|<li>The steps for testing directly with commands are as follows:~~| '''14'''~~<ol style="list-style-type: lower-alpha;">| <li>First set the GPIO port to output mode, where the first parameter of the '''~~GND~~pinMode'''function is the serial number of the wPi corresponding to the pin, and the second parameter is the GPIO mode.{| ~~style~~class="~~text-align: left;~~wikitable"|| style="~~text-align~~width: ~~left~~800px;"|

|-

| root@orangepi:~/wiringOP-Python# '''~~261~~python3 -c "import wiringpi; \'''| '''~~PI5~~from wiringpi import GPIO; wiringpi.wiringPiSetup() ; \'''| '''~~TWI0_SCL~~wiringpi.pinMode(2, GPIO.OUTPUT</~~UART2_TX'''| '''15~~span>) ; "'''|}~~| '''16'''~~</li>~~| '''PWM4~~<li>Then set the GPIO port to output a low level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is 0v, it means the low level is set successfully.</~~UART4_RX'''| '''PI14'''~~p>{| ~~'''270'''~~class="wikitable" style="width:800px;"

|-

| ~~style="text-align~~root@orangepi: ~~left;"|| style="text~~~/wiringOP-~~align: left;"|~~| Python# '''~~3.3V~~python3 -c "import wiringpi; \'''| '''17from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\'''|| '''18wiringpi.digitalWrite(2, GPIO.LOW)"'''| }</li><li>Then set the GPIO port to output a high level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is 3.3v, it means the setting of the high level is successful.{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|~~| '''PH4'''| '''228'''~~

|-

| root@orangepi:~/wiringOP-Python# '''~~231~~python3 -c "import wiringpi; \'''| '''~~PH7~~from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\'''| '''~~SPI1_MOSI~~wiringpi.digitalWrite(2, GPIO.HIGH)"'''| ~~'''19'''~~}|</li></ol>~~| '''20'''~~</li>~~| '''GND'''~~<li>The steps for testing in the command line of python3 are as follows:| <ol style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"|><li>First use the python3 command to enter the command line mode of python3{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|

|-

| ~~'''232'''~~| root@orangepi:~# '''~~PH8~~python3'''| ~~'''SPI1_MISO'''~~}~~| '''21'''~~|</li>~~| '''22'''| '''TWI0_SDA~~<li>Then import the python module of wiringpi</~~UART2_RX'''| '''PI6'''~~p>{| ~~'''262'''~~class="wikitable" style="width:800px;"

|-

| ~~'''230'''~~| >>> '''~~PH6~~import wiringpi'''| >>> '''~~SPI1_CLK~~from wiringpi import GPIO'''| ~~'''23'''~~|~~| '''24'''~~}~~| '''SPI1_CS0'''~~</li>| <li>Then set the GPIO port to output mode, where the first parameter of the '''~~PH5~~pinMode'''function is the serial number of the wPi corresponding to the pin, and the second parameter is the GPIO mode.{| ~~'''229'''~~class="wikitable" style="width:800px;"

|-

| >>> '''wiringpi.wiringPiSetup()'''0>>> '''wiringpi.pinMode(2, GPIO.OUTPUT)'''|}</li><li>Then set the GPIO port to output a low level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is 0v, it means the low level is set successfully.{| class="wikitable" style="~~text~~width:800px;" |-~~align~~| >>> '''wiringpi.digitalWrite(2, GPIO.LOW)'''|}</li><li>Then set the GPIO port to output a high level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is 3.3v, it means the setting of the high level is successful.{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|-| >>> '''~~GND~~wiringpi.digitalWrite(2, GPIO.HIGH)'''| }</li></ol></li><li>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 '25''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.{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''26cd examples'''| root@orangepi:~/wiringOP-Python/examples# '''~~SPI1_CS1~~ls blink.py'''| '''~~PH9~~blink.py'''| root@orangepi:~/wiringOP-Python/examples'''~~233~~# python3 blink.py'''|}</li></ol> === 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: center;"

|-

| '''~~266~~GPIO NO.'''| '''~~PI10~~GPIO'''| '''~~TWI2-SDA/UART3_RX~~Function'''| '''~~27'''~~|~~| '''28'''| '''TWI2-SCL/UART3_TX'''| '''PI9'''| '''265~~Pin'''

|-

~~| '''256'''~~

~~| '''PI0'''~~

~~| style="text-align: left;"|~~

~~| '''29'''~~

|

~~| '''30'''~~

~~| '''GND'''~~

| style="text-align: left;"|

| '''3.3V'''

| '''1'''

|-

| '''264'''

| '''PI8'''

| '''TWI1-SDA'''

| '''3'''

|-

| '''263'''

| '''PI7'''

| '''TWI1-SCL'''

| '''5'''

|-

| '''~~271~~269'''| '''~~PI15'''| style="text-align: left;"|| '''31'''~~|~~| '''32'''| '''PWM1~~PI13'''| '''~~PI11~~PWM3/UART4_TX'''| '''~~267~~7'''

|-

~~| '''268'''~~

~~| '''PI12'''~~

~~| '''PWM2'''~~

~~| '''33'''~~

|

~~| '''34'''~~

~~| '''GND'''~~

| style="text-align: left;"|

| '''GND'''

| '''9'''

|-

| '''226'''

| '''PH2'''

| '''UART5_TX'''

| '''11'''

|-

| '''227'''

| '''PH3'''

| '''UART5_RX'''

| '''13'''

|-

| '''261'''

| '''PI5'''

| '''TWI0_SCL/UART2_TX'''

| '''15'''

|-

~~| '''258'''~~

~~| '''PI2'''~~

| style="text-align: left;"|

~~| '''35'''~~

|

~~| '''36'''~~

| style="text-align: left;"|

| '''~~PC12~~3.3V'''| '''7617'''|-| '''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'''

| style="text-align: left;"|

| '''37'''

|

~~| '''38'''~~

~~| style="text-align: left;"|~~

~~| '''PI4'''~~

~~| '''260'''~~

|-

| style="text-align: left;"|

| '''GND'''

| '''39'''

|

~~| '''40'''~~

~~| style="text-align: left;"|~~

~~| '''PI3'''~~

~~| '''259'''~~

|}

~~<ol start~~{| class="2wikitable" style="~~list-style-type~~width: ~~decimal~~390px;">~~<li>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:<ol style="list~~margin-~~style-type~~right: ~~lower-alpha~~20px;">~~<li>First run '''orangepi-config'''. Ordinary users remember to add > '''sudo''' permissions.orangepi@orangepi:~$ '''sudo orangepi~~text-~~config'''</li><li>Then select '''System'''[[File~~align:~~zero2w-img80.png]]</li><li>Then select '''Hardware'''[[File:zero2w-img81.png]]</li><li>Then use the keyboard's arrow keys to locate the position shown > in the picture below, and then use the '''space''' to select the &gt~~center; ~~corresponding i2c configuration in the picture below.</li></ol></li></ol>~~ ~~{| class="wikitable~~"

|-

| '''~~Multiplexing function in 40pin~~Pin'''| '''~~Corresponding dtbo configuration~~Function'''| '''GPIO'''| '''GPIO NO.'''

|-

| '''~~40pin~~ 2'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"||- ~~i2c0~~| '''4'''| '''pi5V'''| style="text-align: left;"|| style="text-align: left;"||-~~i2c0~~| '''6'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"||-| '''8'''| '''UART0_TX'''| '''PH0'''| '''224'''

|-

| '''~~40pin~~ 10'''| '''UART0_RX'''| '''PH1'''| '''225'''|-| '''12'''| style="text- ~~i2c1~~align: left;"|| '''PI1'''| '''pi257'''|-~~i2c1~~| '''14'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|

|-

| '''~~40pin - i2c2~~16'''| '''~~pi-i2c2~~PWM4/UART4_RX'''|} ~~[[File:zero2w-img173.png]]~~ ~~<ol start="5" style="list-style-type: lower-alpha;"><li>Then select <Save> to save[[File:zero2w-img83.png]]</li><li>Then select <Back>[[File:zero2w-img84.png]]</li><li>Then select <Reboot> to restart the system to make the > configuration take effect.[[File:zero2w-img85.png]]</li></ol>~~ ~~<ol start="3" style="list-style-type: decimal;"><li>After starting the Linux system, first confirm that there is an open i2c device node under /devorangepi@orangepi:~$ '''ls /dev/i2c-*''''''/dev/i2c-*''''''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.''''''The method to accurately confirm the device node under /dev corresponding to the i2c bus is:'''</li></ol>~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>~~'''~~First run the following command to check the corresponding relationship of i2c~~PI14'''~~~~orangepi@orangepizero2w:~$ '''ls /sys/devices/platform/soc*/*/i2c-* | ~~grep "i2c-[0-9]"'''/sys/devices/platform/soc/5002000.i2c/i2c-0:/sys/devices/platform/soc/5002400.i2c/i2c-3:/sys/devices/platform/soc/5002800.i2c/i2c-4:/sys/devices/platform/soc/5002c00.i2c/i2c-5:/sys/devices/platform/soc/6000000.hdmi/i2c-2:/sys/devices/platform/soc/7081400.i2c/i2c-1:</li><li>~~'''~~In the above output~~270'''~~</li></ol>~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li>002000 is the register base address of the i2c0 bus, and i2c-0 shown behind it is its corresponding i2c device node</li><li>5002400 is the register base address of the i2c1 bus, and i2c-3 shown behind it is its corresponding i2c device node</li><li>5002800 is the register base address of the i2c2 bus, and i2c-4 shown behind it is its corresponding i2c device node</li></ol>~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then start testing i2c, first install i2c-toolsorangepi@orangepi:~$ '''sudo apt-get update'''orangepi@orangepi:~$ '''sudo''' '''apt-get install -y i2c-tools'''</li><li>Then connect an i2c device to the i2c pin of the 40pin connector. Here we take the DS1307 RTC module as an example.[[File:zero2w-img178.png]]</li><li>Then use the '''i2cdetect -y x'''command. If the address of the connected i2c device can be detected, it means that the i2c device is connected correctly.'''Note that x in the i2cdetect -y x command needs to be replaced with the serial number of the device node corresponding to the i2c bus.'''</li></ol>~~ ~~[[File:zero2w-img179.png]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>Then you can run the '''ds1307.py''' test program in '''examples''' to read the RTC time'''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.'''root@orangepi:~/wiringOP-Python# '''cd examples'''root@orangepi:~/wiringOP-Python/examples# '''python3 ds1307.py --device \''''''"/dev/i2c-x"'''Thu 2022-06-16 04:35:46Thu 2022-06-16 04:35:47Thu 2022-06-16 04:35:48^Cexit</li></ol>~~ ~~=== 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. ~~{| class="wikitable"~~

|-

|-

~~| style="text-align: left;"|| style="text-align: left;"|| '''3.3V'''| '''1'''~~|| '''220'''| '''5VGND'''

| style="text-align: left;"|

|-

| '''~~264~~22'''| '''~~PI8~~TWI0_SDA/UART2_RX'''| '''~~TWI1-SDA~~PI6'''| '''3262'''|-| '''424'''| '''5VSPI1_CS0'''| '''PH5'''| '''229'''|-~~align~~| '''26'''|'''SPI1_CS1'''| '''PH9'''| '''233'''|-| '''28'''| '''TWI2-SCL/UART3_TX'''| '''PI9'''|'''265'''

|-

| '''~~263'''| '''PI7'''| '''TWI1-SCL'''| '''5'''~~|~~| '''6~~30'''

| '''GND'''

| style="text-align: left;"|

|-

| '''~~269~~32'''| '''~~PI13~~PWM1'''| '''~~PWM3/UART4_TX~~PI11'''| '''~~7'''~~|~~| '''8'''| '''UART0_TX'''| '''PH0'''| '''224~~267'''

|-

| '''34'''

| '''GND'''

| style="text-align: left;"|

~~| '''GND'''~~

~~| '''9'''~~

|

~~| '''10'''~~

~~| '''UART0_RX'''~~

~~| '''PH1'''~~

~~| '''225'''~~

|-

| '''~~226'''| '''PH2'''| '''UART5_TX'''| '''11'''~~|~~| '''12~~36'''

| style="text-align: left;"|

| '''~~PI1~~PC12'''| '''~~257~~76'''

|-

| '''~~227~~38'''| ~~'''PH3'''~~style="text-align: left;"|| '''~~UART5_RX~~PI4'''| '''13260'''|-| '''1440'''~~| '''GND'''| style="text-align: left;"|~~

| style="text-align: left;"|

| '''PI3'''

| '''259'''

|}

</div>

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

<li>First run '''orangepi-config'''. Ordinary users remember to add '''sudo''' permissions.

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

|-

| orangepi@orangepi:~$ '''~~261~~sudo orangepi-config'''| }</li><li>Then select '''~~PI5~~System'''~~| '''TWI0_SCL~~[[File:zero2w-img80.png]]</~~UART2_TX'''~~li>| <li>Then select '''15Hardware'''|[[File:zero2w-img81.png]]</li>| <li>Then use the keyboard's arrow keys to locate the position shown in the figure below, and then use the ''16'space''| '~~''PWM4~~to select the dtbo configuration of the SPI you want to open.</~~UART4_RX'''~~li>~~| '''PI14'''~~{| ~~'''270'''~~class="wikitable" style="width:800px;text-align: center;"

|-

~~| style="text-align: left;"|| style="text-align: left;"|| '''3.3V'''| '''17'''~~|~~| '''18'''| style="text-align: left;"|~~| '''~~PH4~~dtbo configuration'''| '''~~228~~illustrate'''

|-

| '''~~231'''| '''PH7~~spi1-cs0-cs1-spidev'''| '''~~SPI1_MOSI~~Open cs0 and cs1 of spi1 at the same time'''~~| '''19'''~~|~~| '''20'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~232~~spi1-cs0-spidev'''| '''~~PH8'''| '''SPI1_MISO'''| '''21'''~~|~~| '''22'''| '''TWI0_SDA/UART2_RX'''| '''PI6'''| '''262~~Only open cs0 of spi1'''

|-

| '''~~230~~spi1-cs1-spidev'''| '''~~PH6~~Only open cs1 of spi1'''| }</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then select '''~~SPI1_CLK~~<Save>'''to save[[File:zero2w-img83.png]]</li>| <li>Then select '''23<Back>'''|[[File:zero2w-img84.png]]</li>| <li>Then select '''24<Reboot>'''to restart the system to make the configuration take effect.[[File:zero2w-img85.png]]</li></ol></li></ol>~~| '''SPI1_CS0'''~~<ol start="3" style="list-style-type: decimal;">| <li>Then check whether there is a '''~~PH5~~spidev1.x'''device node in the Linux system. If it exists, it means that the SPI1 configuration has taken effect.{| ~~'''229'''~~class="wikitable" style="width:800px;"

|-

~~| style="text-align: left;"~~|~~| style="text-align~~orangepi@orangepi: ~~left;"|~~| ~$ '''~~GND~~ls /dev/spidev1*'''~~| '''25'''~~/dev/spidev1.0 /dev/spidev1.1|}{| ~~'''26'''| '''SPI1_CS1'''| '''PH9'''| '''233'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

| <big>'''~~266~~Note that only when you open spi1-cs0-cs1-spidev, you will see the device nodes of the two spi.'''</big>| }</li><li>Then you can use the '''spidev_test.py''' program in examples to test the SPI loopback function. The '''~~PI10~~spidev_test.py'''program needs to specify the following two parameters:<ol style="list-style-type: lower-alpha;"><li>'''--channel''': Specify the channel number of SPI</li><li>'''--port''': Specify the port number of the SPI</li></ol></li><li>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.{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''~~TWI2~~cd examples''' root@orangepi:~/wiringOP-~~SDA~~Python/~~UART3_RX~~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 '''2740 00 00 00 00 95'''FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…| RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |.............….|| }</li></ol><ol start="6" style="list-style-type: decimal;"><li>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.{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''28cd examples''' 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 '''~~TWI2~~40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…| RX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…||}</li></ol></~~UART3_TX~~span> === 40pin I2C test === # As can be seen from the table below, the i2c available for the 40pin interface are i2c0, i2c1 and i2c2 <div style="display: flex;">::{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''GPIO NO.'''| '''GPIO'''| '''~~PI9~~Function'''| '''~~265~~Pin'''

|-

~~| '''256'''~~

~~| '''PI0'''~~

~~| style="text-align: left;"|~~

~~| '''29'''~~

|

~~| '''30'''~~

~~| '''GND'''~~

| style="text-align: left;"|

| '''3.3V'''

| '''1'''

|-

| '''264'''

| '''PI8'''

| '''TWI1-SDA'''

| '''3'''

|-

| '''263'''

| '''v'''

| '''TWI1-SCL'''

| '''5'''

|-

| '''269'''

| '''PI13'''

| '''PWM3/UART4_TX'''

| '''7'''

|-

| style="text-align: left;"|

| '''GND'''

| '''9'''

|-

| '''226'''

| '''PH2'''

| '''UART5_TX'''

| '''11'''

|-

| '''227'''

| '''PH3'''

| '''UART5_RX'''

| '''13'''

|-

| '''261'''

| '''PI5'''

| '''TWI0_SCL/UART2_TX'''

| '''15'''

|-

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

| '''GND'''

| '''25'''

|-

| '''266'''

| '''PI10'''

| '''TWI2-SDA/UART3_RX'''

| '''27'''

|-

| '''256'''

| '''PI0'''

| style="text-align: left;"|

| '''29'''

|-

| '''271'''

| style="text-align: left;"|

| '''31'''

|

~~| '''32'''~~

~~| '''PWM1'''~~

~~| '''PI11'''~~

~~| '''267'''~~

|-

| '''268'''

| '''PWM2'''

| '''33'''

|~~| '''34'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~|-

| '''258'''

| '''PI2'''

| style="text-align: left;"|

| '''35'''

|

~~| '''36'''~~

~~| style="text-align: left;"|~~

~~| '''PC12'''~~

~~| '''76'''~~

|-

| '''272'''

| style="text-align: left;"|

| '''37'''

|

~~| '''38'''~~

~~| style="text-align: left;"|~~

~~| '''PI4'''~~

~~| '''260'''~~

|-

| style="text-align: left;"|

| '''GND'''

| '''39'''

|

~~| '''40'''~~

~~| style="text-align: left;"|~~

~~| '''PI3'''~~

~~| '''259'''~~

|}

~~<ol start~~{| class="2wikitable" style="~~list-style-type~~width: ~~decimal~~390px;">~~<li>In Linux systems, uart is turned off by default and needs to be turned on manually before it can be used. The opening steps are as follows:: <ol style="list-style~~margin-~~type~~right: ~~lower-alpha;"><li>First run '''orangepi-config'''. Ordinary users remember to add &gt~~20px; ~~'''sudo''' permissions.orangepi@orangepi:~$ '''sudo orangepi-config'''</li><li>Then select '''System'''[[File:zero2w~~text-~~img80.png]]</li><li>Then select '''Hardware'''[[File~~align:~~zero2w-img81.png]]</li><li>Then use the keyboard's arrow keys to locate the position shown &gt~~center; ~~in the picture below, and then use the '''space''' to select the > serial port you want to open.</li></ol></li></ol>~~ ~~{| class="wikitable~~"

|-

| '''~~Multiplexing function in 40pin~~Pin'''| '''~~Corresponding dtbo configuration~~Function'''| '''GPIO'''| '''GPIO NO.'''

|-

| '''~~40pin - uart2~~2'''| '''~~pi-uart2~~5V'''| style="text-align: left;"|| style="text-align: left;"|

|-

| '''~~40pin - uart3~~4'''| '''~~pi-uart3~~5V'''| style="text-align: left;"|| style="text-align: left;"|

|-

| '''~~40pin - uart4~~6'''| '''~~pi-uart4~~GND'''| style="text-align: left;"|| style="text-align: left;"|

|-

| '''~~40pin~~ 8'''| '''UART0_TX'''| '''PH0'''| '''224'''|- ~~uart5~~| '''10'''| '''~~ph-uart5~~UART0_RX'''|}'''PH1'''| '''225'''~~[[File:zero2w~~|-~~img175.png]]~~| '''12'''~~<ol start~~| style="5text-align: left;" || '''PI1'''| '''257'''|-| '''14'''| '''GND'''| style="~~list~~text-align: left;"|| style="text-~~type~~align: ~~lower-alpha~~left;">||-~~<li>Then select~~ | '''16'''~~<Save>~~| ''' ~~to save<~~PWM4/p>UART4_RX'''| '''PI14'''| '''270'''~~[[File:zero2w~~|-~~img83.png]]</li><li>Then select~~ | '''~~<Back>~~18'''~~[[File~~| style="text-align:~~zero2w-img84.png]]</li>~~left;"|| '''PH4'''~~<li>Then select~~ | '''~~<Reboot>~~228''' ~~to restart the system to make the > configuration take effect.[[File:zero2w~~|-~~img85.png]]</li></ol>~~| '''20'''~~~~| '''GND'''~~<ol start~~| style="3text-align: left;" || style="~~list-style~~text-~~type~~align: ~~decimal~~left;">||-~~<li>After entering the Linux system, first confirm whether there is a uart5 device node under~~ | '''~~/dev~~22'''| '''</pspan style="color:#FF0000">TWI0_SDA<p/span>/UART2_RX'''~~注意, linux5.4系统为/dev/ttyASx.~~| '''</pspan style="color:#FF0000">PI6<p/span>~~orangepi@orangepi:~$~~ '''ls /dev/ttyS*| '''</pspan style="color:#FF0000">262/~~dev/ttySx</li~~span>'''~~<li>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.</li><li>Use the~~ | '''24'''| '''~~gpio~~SPI1_CS0''' ~~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.~~| '''~~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.~~PH5'''~~orangepi@orangepi:~$~~ | '''229'''~~gpio serial /dev/ttySx # linux~~|-~~6.1 test command~~| '''26'''| '''SPI1_CS1'''| '''PH9'''~~orangepi@orangepi:~$~~ | '''233'''~~gpio serial /dev/ttyASx # linux~~|-~~5.4 test command~~| '''<~~/p>~~<pspan style="color:#FF0000">~~Out: 0: -> 0~~28</pspan>'''| '''<pspan style="color:#FF0000">~~Out: 1:~~ TWI2-~~> 1~~SCL</pspan>/UART3_TX'''| '''<pspan style="color:#FF0000">~~Out: 2: -> 2~~PI9</pspan>'''| '''<~~p>Out~~span style="color: ~~3: -> 3^C</p~~#FF0000">265</lispan>'''|-~~<li>Finally, you can run the~~ | '''~~serialTest.py~~30''' ~~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.~~| '''~~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.~~GND'''~~root@orangepi~~| style="text-align: left;"|| style="text-align:~~~/wiringOP~~left;"||-~~Python#~~ | '''32'''| '''PWM1'''| '''PI11'''| '''~~cd examples~~267'''~~root@orangepi:~/wiringOP~~|-~~Python/examples#~~ | '''~~python3 serialTest.py --device "/dev/ttySx" # linux6.1 use~~34'''~~root@orangepi:~/wiringOP-Python/examples#~~ | '''~~python3 serialTest.py --device "/dev/ttyASx" # linux5.4 use~~GND'''~~Out: 0~~| style="text-align: ~~-&gt~~left; ~~0~~"|~~Out: 1~~| style="text-align: ~~-&gt~~left; ~~1~~"|~~Out: 2:~~ |-~~> 2Out: 3~~| '''36'''| style="text-align: ~~-&gt~~left; ~~3~~"|| '''PC12'''~~Out: 4:^C~~| '''76'''~~exit</li></ol>~~|-| '''38'''~~~~|~~== 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>

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

<li>~~The second parameter 10 represents the counting time of the watchdog~~First run '''orangepi-config'''. ~~If the dog is not fed within this time, the system will restart~~Ordinary users remember to add '''sudo''' permissions.</p~~></li~~>~~<li>We can feed the dog by pressing any key on the keyboard (except ESC). After feeding the dog, the program will print a line &quot~~{| class="wikitable" style="width:800px;~~keep alive" to indicate that the dog feeding is successful.~~" |-| orangepi@orangepi:~$ '''sudo ~~watchdog_test 10~~orangepi-config'''~~open success~~|}</pli><pli>~~options is 33152,identity is sunxi-wdt~~~~put_usr return,if 0,success:0~~Then select '''System'''~~The old reset time is~~[[File: 16zero2w-img80.png]]~~return ENOTTY,if -1,success:0~~</pli><pli>~~return ENOTTY,if -1,success:0~~~~put_user return,if 0,success:0~~Then select '''Hardware'''~~put_usr return,if 0,success~~[[File:0zero2w-img81.png]]~~keep alive~~</pli><pli>~~keep alive~~~~keep alive~~Then use the keyboard's arrow keys to locate the position shown in the picture below, and then use the '''space''' to select the corresponding i2c configuration in the picture below.</li~~></ol~~>

~~<span id~~{| class="~~check~~wikitable" style="width:800px;text-align: center;"|-| '''Multiplexing function in 40pin'''| '''Corresponding dtbo configuration'''|-~~the~~| '''40pin -~~chipid~~i2c0'''| '''pi-ofi2c0'''|-~~h618~~| '''40pin -~~chip">~~i2c1'''| '''pi-i2c1'''|-| '''40pin - i2c2'''| '''pi-i2c2'''~~== Check the chipid of H618 chip ==~~|}

~~The command~~ [[File:zero2w-img173.png]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then select <Save> to save[[File:zero2w-img83.png]]</li><li>Then select <Back>[[File:zero2w-img84.png]]</li><li>Then select <Reboot> to restart the system to ~~view~~ make the configuration take effect.[[File:zero2w-img85.png]]</li></ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>After starting the ~~H618 chip chipid~~ Linux system, first confirm that there is ~~as follows~~an open i2c device node under /dev{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ls /dev/i2c-*''''''/dev/i2c-*'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''注意，这里说的Linux镜像具体指的是从Orange Pi资料下载页面下载的Debian或者Ubuntu这样的Linux发行版镜像。'''</big>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''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.''''''The ~~chipid of each chip~~ method to accurately confirm the device node under /dev corresponding to the i2c bus is ~~different, so you can use chipid to distinguish multiple development boards.~~: '''</big>

~~orangepi@orangepi:~$ '''cat /sys/class/sunxi_info/sys_info | grep "chipid"'''~~

~~sunxi_chipid~~ <ol style="list-style-type: lower-alpha;"><li>'''First run the following command to check the corresponding relationship of i2c'''orangepi@orangepizero2w:~$ '''ls /sys/devices/platform/soc*/*/i2c-* | grep "i2c-[0-9]"'''/sys/devices/platform/soc/5002000.i2c/i2c-0: ~~338020004c0048080147478824681ed1~~/sys/devices/platform/soc/5002400.i2c/i2c-3:<~~span id="python~~p>/sys/devices/platform/soc/5002800.i2c/i2c-~~related~~4:/sys/devices/platform/soc/5002c00.i2c/i2c-~~instructions"~~5:/sys/devices/platform/soc/6000000.hdmi/i2c-2:</~~span~~p>~~== Python related instructions ==~~/sys/devices/platform/soc/7081400.i2c/i2c-1:</li>

~~~~

~~=== How to compile and install Python source code ===~~

<li>'''If the Python version in the Ubuntu or Debian system software repository you are using does not meet the development requirements and you want to use the latest version of Python, you can use the following method to download the Python source code package to compile and install In the ~~latest version of Python.~~above output'''<ol style="list-style-type: none;">~~'''The following demonstration~~ <li>a) 5002000 is ~~to compile and install~~ the ~~latest version~~ register base address of ~~Python 3.9. If you want to compile~~ the i2c0 bus, and ~~install other versions~~ i2c-0 shown behind it is its corresponding i2c device node</li><li>b) 5002400 is the register base address of ~~Python~~the i2c1 bus, ~~the method~~ and i2c-3 shown behind it is its corresponding i2c device node</li><li>c) 5002800 is the ~~same (you need to download~~ register base address of the ~~source code~~ i2c2 bus, and i2c-4 shown behind it is its corresponding ~~to the Python you want to install).'''~~i2c device node</li></ol></li></ol>|}</li></ol><ol start="4" style="list-style-type: decimal;"><li>~~First~~ Then start testing i2c, first install ~~the dependency packages needed to compile Python~~i2c-tools{| class="wikitable" style="width:800px;" |-|

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

orangepi@orangepi:~$ '''sudo ~~apt-get install -y build-essential zlib1g-dev \''''''libncurses5-dev libgdbm-dev libnss3-dev libssl-dev libsqlite3-dev \''''''libreadline-dev libffi-dev curl libbz2-dev'''</li><li>Then download the latest version of Python3.9 source code and unzip itorangepi@orangepi:~$ '''wget \'''[https://www.python.org/ftp/python/3.9.10/Python-3.9.10.tgz '''https://www.python.org/ftp/python/3.9.10/Python-3.9.10.tgz''']orangepi@orangepi:~$ '''tar xvf Python-3.9.10.tgz'''</li><li>Then run the configuration commandorangepi@orangepi:~$ '''cd Python-3.9.10'''orangepi@orangepi:~$ '''./configure --enable-optimizations'''</li><li>Then compile and install Python3.9. The compilation time takes about half an hour.orangepi@orangepi:~$ '''make -j4'''orangepi@orangepi:~$ '''sudo make altinstall'''</li><li>After installation, you can use the following command to check the version number of the Python you just installed.orangepi@orangepi:~$ '''python3.9 --version''''''Python 3.9.10'''</li><li>Then update piporangepi@orangepi:~$ '''/usr/local/bin/python3.9 -m pip install --upgrade pip'''</li></ol>~~ ~~=== How to replace pip source in Python ===~~ '''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.''' ~~<ol style="list-style-type: decimal;"><li>First install~~ '''~~python3-pip~~'''~~orangepi@orangepi:~$ '''sudo apt-get update'''orangepi@orangepi:~$ '''sudo~~ apt-get install -y ~~python3-pip'''</li><li>How to permanently change the pip source under Linux<ol style="list-style-type: lower-alpha;"><li>First create a new '''~/.pip''' directory, then add the > '''pip.conf''' configuration file, and set the pip source in it > to Tsinghua source.orangepi@orangepi:~$ '''mkdir -p ~/.pip'''orangepi@orangepi:~$ '''cat <<EOF > ~/.pip/pip.conf''''''[global]''''''timeout = 6000''''''index-url = https://pypi.tuna.tsinghua.edu.cn/simple''''''trusted~~i2c-~~host = pypi.tuna.tsinghua.edu.cn~~tools'''~~'''EOF'''</li><li>Then use pip3 to install the Python library very quickly</li></ol>~~|}

</li>

<li>~~How~~ Then connect an i2c device to ~~temporarily change~~ the ~~pip source under Linux, where '''<packagename>''' needs to be replaced with a specific package name~~i2c pin of the 40pin connector. Here we take the DS1307 RTC module as an example.~~orangepi@orangepi~~[[File:~$ zero2w-img178.png]]</li><li>Then use the '''~~pip3 install <packagename>~~ i2cdetect -~~i \~~y x'''command. If the address of the connected i2c device can be detected, it means that the i2c device is connected correctly.{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>''''''~~https://pypi.tuna.tsinghua.edu.cn/simple~~ Note that x in the i2cdetect -~~-trusted-host pypi.tuna.tsinghua.edu~~y x command needs to be replaced with the serial number of the device node corresponding to the i2c bus.cn''''''</~~li></ol~~big>|}

[[File:zero2w-img179.png]]</li></ol><~~span id~~ol start="7" style="~~how-to~~list-~~install~~style-~~docker~~type: decimal;"><li>Then you can run the '''ds1307.py''' test program in '''examples''' to read the RTC time</~~span~~p>{| class="wikitable" style= ~~How~~ "background-color:#ffffdc;width:800px;" |-| <big>'''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 ~~install Docker~~ the i2c bus.'''</big>|}{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''cd examples'''root@orangepi:~/wiringOP-Python/examples# '''python3 ds1307.py --device \''''''"/dev/i2c-x"'''Thu 2022-06-16 04:35:46Thu 2022-06-16 04:35:47Thu 2022-06-16 04:35:48^Cexit|}</li></ol>

~~The Linux image provided by Orange Pi has Docker pre~~<span id="pin-installed, but the Docker service is not turned on by default. Use the '''enable_docker.sh''' script to enable the docker service, and then you can start using the docker command, and the docker service will be automatically started the next time you start the system.uart-test-1">

~~orangepi@orangepi:~$ '''enable_docker.sh'''~~=== 40pin UART test ===

~~You~~ # As can ~~use~~ be seen from the table below, the ~~following command to test docker~~available uarts are uart2, uart3, uart4 and uart5. ~~If '''hello-world''' can be run, docker can be used normally~~Please note that uart0 is set as a debugging serial port by default. Please do not use uart0 as a normal serial port.

~~orangepi@orangepi~~<div style="display:~~~$ '''docker run hello-world'''~~flex;">~~Unable to find image 'hello-world~~:~~latest' locally~~ ~~latest~~: ~~Pulling from library/hello-world~~ ~~256ab8fe8778~~{| class="wikitable" style="width: ~~Pull complete~~ ~~Digest~~390px;margin-right: ~~sha256~~20px;text-align:~~7f0a9f93b4aa3022c3a4c147a449ef11e0941a1fd0bf4a8e6c9408b2600777c5~~center;" ~~Status: Downloaded newer image for hello~~|-~~world:latest~~ | '''~~Hello from Docker!~~GPIO NO.''' | '''~~This message shows that your installation appears to be working correctly.~~GPIO''' | '''~~.….~~Function''' ~~When using the docker command, if you are prompted for~~ | '''~~permission denied~~Pin'''~~, please add the current user to the docker user group so that you can run the docker command without sudo.~~|-~~orangepi@orangepi~~| style="text-align:~$ left;"|| style="text-align: left;"|| '''~~sudo usermod -aG docker $USER~~3.3V''' | '''~~Note: You need to log out and log in again to the system to take effect. You can also restart the system.~~1''' ~~== How to install Home Assistant ==~~ | '''Note that this article will only provide methods for installing Home Assistant in Ubuntu or Debian systems. For detailed usage of Home Assistant, please refer to the official documentation or corresponding books.264''' ~~=== Installation via docker ===~~ ~~<ol style="list-style-type: decimal;"><li>First, please install docker and ensure that docker can run normally. For the installation steps of docker, please refer to the instructions in the [[\l~~|'''~~How to Install Docker~~263'''~~]] section.</li><li>Then you can search for the docker image of Home Assistantorangepi@orangepi:~$~~ | '''~~docker search homeassistant~~PI7'''~~</li>~~<li>Then use the following command to download the Docker image of Home Assistant to your local computer. The image size is about 1GB, and the download time will be relatively long. Please be patient and wait for the download to complete.| '''TWI1-SCL'''~~orangepi@orangepi:~$~~ | '''~~docker pull homeassistant/home-assistant~~5'''~~Using default tag: latest~~|-| '''269'''| '''PI13'''~~latest: Pulling from homeassistant~~| '''PWM3/~~home-assistant~~UART4_TX'''~~be307f383ecc: Downloading5fbc4c07ac88: Download complete~~| '''~~...... (Omit some output)~~7'''~~3cc6a1510c9f: Pull complete~~|-~~7a4e4d5b979f~~| style="text-align: ~~Pull complete~~left;"|~~Digest~~| style="text-align: ~~sha256:81d381f5008c082a37da97d8b08dd8b358dae7ecf49e62ce3ef1eeaefc4381bb~~left;"|~~Status: Downloaded newer image for homeassistant/home-assistant:latest~~| '''GND'''~~docker.io/homeassistant/home~~| '''9'''|-~~assistant:latest</li><li>Then you can use the following command to view the docker image of Home Assistant you just downloadedorangepi@orangepi:~$~~ | '''~~docker images homeassistant/home-assistant~~226'''~~REPOSITORY TAG IMAGE ID CREATED SIZE~~| '''PH2'''~~homeassistant/home-assistant latest bfa0ab9e1cf5 2 months ago~~ | '''~~1.17GB~~UART5_TX'''~~</li><li>At this point you can run the Home Assistant docker containerorangepi@orangepi:~$~~ | '''~~docker run -d \~~11'''~~~~|-| '''~~--name homeassistant \~~227'''~~~~| '''~~--privileged \~~PH3'''~~~~| '''~~--restart=unless-stopped \~~UART5_RX'''~~~~| '''~~-e TZ=Asia/Shanghai \~~13'''~~~~|-| '''~~-v /home/orangepi/home-assistant:/config \~~261'''~~~~| '''~~--network=host \~~PI5'''~~~~| '''~~homeassistant~~TWI0_SCL/~~home-assistant:latest~~UART2_TX'''~~</li><li>Then enter【the IP address of the development board: 8123】in the browser to see the Home Assistant interface~~| '''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 need to check whether there is a problem with the previous installation and setting process.15'''~~<div class~~|-| style="~~figure~~text-align: left;">|| style="text-align: left;"|~~[[File:zero2w-img180~~| '''3.~~png]]~~3V'''| '''17'''~~</div></li>~~|-~~<li>Then enter your~~ | '''~~name, username~~231''' ~~and~~ | '''~~password~~PH7''' ~~and click~~ | '''~~Create Account~~SPI1_MOSI'''~~<div class="figure">~~| '''19''' ~~[[File:zero2w~~|-~~img181.png]]~~| '''232'''~~</div></li>~~| '''PH8'''~~<li>Then follow the interface prompts to set according to your own preferences, and then click Next~~| '''SPI1_MISO'''~~<div class="figure">~~| '''21''' ~~[[File:zero2w~~|-~~img182.png]]~~| '''230'''~~</div></li>~~| '''PH6'''~~<li>Then click Next~~| '''SPI1_CLK'''~~<div class="figure">~~| '''23'''|-~~[[File~~| style="text-align:~~zero2w~~left;"|| style="text-~~img183.png]]~~align: left;"|| '''GND'''~~</div></li>~~| '''25'''~~<li>Then click Finish~~|-~~<div class="figure">~~| '''266'''| '''PI10'''~~[[File:zero2w~~| '''TWI2-~~img184.png]]~~SDA/UART3_RX'''| '''27'''~~</div></li><li>The main interface finally displayed by Home Assistant is as shown below~~|-~~[[File:zero2w-img185.png]]</li>~~| '''256'''~~<li>Method to stop Home Assistant container~~| '''PI0'''~~<ol~~ | style="~~list~~text-~~style-type~~align: ~~lower-alpha~~left;">|| '''29'''~~<li>The command to view the docker container is as follows~~|-~~orangepi@orangepi:~$~~ | '''~~docker ps -a~~271'''~~</li><li>The command to stop the Home Assistant container is as follows~~| '''PI15'''~~orangepi@orangepi~~| style="text-align:~$ left;"|| '''~~docker stop homeassistant~~31'''~~</li><li>The command to delete the Home Assistant container is as follows~~|-| '''268'''~~orangepi@orangepi:~$~~ | '''~~docker rm homeassistant~~PI12'''| '''PWM2'''~~</li></ol></li></ol>~~| '''33'''|-~~=== Installation via python ===~~| '''258'''| '''Before installation, please change the source of pip to a domestic source to speed up the installation of Python packages. For the configuration method, see the instructions in the section "[[\l|How to Change the Pip Source of Python]]"PI2''' ~~<ol~~ | style="~~list-style~~text-~~type~~align: ~~decimal~~left;">|~~<li>First install dependency packagesorangepi@orangepi:~$~~ | '''~~sudo apt-get update~~35'''~~orangepi@orangepi:~$~~ |-| '''~~sudo apt-get install -y python3 python3-dev python3-venv \~~272'''~~~~| '''~~python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential \~~PI16'''~~'''libopenjp2~~| style="text-~~7 libtiff5 libturbojpeg0-dev tzdata'''~~align: left;"|~~~~| '''~~If it is debian12, please use the following command:~~37'''~~orangepi@orangepi:~$ '''sudo apt~~|-~~get update'''orangepi@orangepi~~| style="text-align: left;"|| style="text-align:~$ left;"|| '''~~sudo apt-get install -y python3 python3-dev python3-venv \~~GND'''~~~~| '''~~python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential \~~39'''~~'''libopenjp2-7 libturbojpeg0~~|}{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-~~dev tzdata~~| '''Pin'''~~</li><li>Then you need to compile and install Python3.9. For the method, please refer to the [[\l|~~| '''Function'~~Python source code compilation and installation method~~''~~']] section.~~| '''~~The default Python version of Debian Bullseye is Python3.9, so there is no need to compile and install it.~~GPIO'''~~~~| '''~~The default Python version of Ubuntu Jammy is Python3.10, so there is no need to compile and install it~~GPIO NO.'''~~~~|-| '''~~The default Python version of Debian Bookworm is Python3.11, so there is no need to compile and install it.~~2'''~~</li><li>Then create a Python virtual environment~~| '''~~'Debian Bookworm is python3.11, please remember to replace the corresponding command.~~5V'''~~orangepi@orangepi~~| style="text-align:~~~$ '''sudo mkdir /srv/homeassistant'''~~left;"|~~orangepi@orangepi~~| style="text-align:~$ left;"||-| '''~~sudo chown orangepi:orangepi /srv/homeassistant~~4'''~~orangepi@orangepi:~$~~ | '''~~cd /srv/homeassistant~~5V'''~~orangepi@orangepi~~| style="text-align: left;"|| style="text-align:~$ left;"||-| '''~~python3.9 -m venv .'~~6'''~~orangepi@orangepi:~$~~ | '''~~source bin/activate~~GND'''~~(homeassistant) orangepi@orangepi~~| style="text-align:~~/srv/homeassistant$</li>~~left;"|| style="text-align: left;"|~~<li>Then install the required Python packages~~|-~~(homeassistant) orangepi@orangepi:/srv/homeassistant$~~ | '''~~python3 -m pip install wheel~~8'''~~</li><li>Then you can install Home Assistant Core~~| '''UART0_TX'''~~(homeassistant) orangepi@orangepi:/srv/homeassistant$~~ | '''~~pip3 install homeassistant~~PH0'''~~</li><li>Then enter the following command to run Home Assistant Core(homeassistant) orangepi@orangepi:/srv/homeassistant$~~ | '''~~hass~~224'''~~</li><li>Then enter【~~|-| '''~~development board IP address: 8123~~10'''~~】 in the browser to see the Home Assistant interface~~| '''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.UART0_RX'''~~<div class="figure">~~| '''PH1'''| '''225'''~~[[File:zero2w~~|-~~img180.png]]~~| '''12'''~~</div></li></ol>~~| style="text-align: left;"|| '''PI1'''| '''257'''~~== OpenCV installation method ==~~| '''14'''| '''GND'''~~~~|~~=== Use apt to install OpenCV ===~~ ~~<ol~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">||-~~<li>The installation command is as follows~~| '''16'''~~orangepi@orangepi:~$~~ | '''~~sudo apt-get update~~PWM4/UART4_RX'''~~orangepi@orangepi:~$~~ | '''~~sudo apt-get install -y libopencv-dev python3-opencv~~PI14'''~~</li><li>Then use the following command to print the version number of OpenCV. The output is normal, indicating that the OpenCV installation is successful.~~| '''270'''~~<ol style="list~~|-~~style-type: lower-alpha;"><li>The version of OpenCV in Ubuntu22.04 is as follows:orangepi@orangepi:~$~~ | '''~~python3 -c "import cv2; print(cv2.__version__)"~~18'''~~~~| style="text-align: left;"|| '''~~4.5.4~~PH4'''~~</li><li>The version of OpenCV in Ubuntu20.04 is as follows:~~| '''228'''|-~~orangepi@orangepi:~$~~ | '''~~python3 -c "import cv2; print(cv2.__version__)"~~20'''~~~~| '''~~'4.2.0~~GND'''~~</li><li>The version of OpenCV in Debian11 is as follows~~| style="text-align:~~~~left;"|~~orangepi@orangepi~~| style="text-align:~$ left;"||-| '''~~python3 -c "import cv2; print(cv2.__version__)"~~22'''~~~~| '''~~4.5.1~~TWI0_SDA/UART2_RX'''~~</li><li>The version of OpenCV in Debian12 is as follows:orangepi@orangepi:~$~~ | '''~~python3 -c "import cv2; print(cv2.__version__)"~~PI6'''~~~~| '''~~4.6.0~~262'''~~</li></ol></li></ol>~~ ~~== Set up the Chinese environment and install the Chinese input method ==~~|-| '''24'''| '''~~Note, before installing the Chinese input method, please make sure that the Linux system used by the development board is a desktop version.~~SPI1_CS0'''| '''PH5'''~~=== Debian system installation method ===~~| '''26''' ~~<ol style="list-style-type: decimal;"><li>First set the default~~ | '''~~locale~~SPI1_CS1''' ~~to Chinese<ol style="list-style-type: lower-alpha;"><li>Enter the following command to start configuring~~ | '''~~locale~~PH9'''~~orangepi@orangepi:~$~~ | '''~~sudo dpkg-reconfigure locales~~233'''~~</li><li>Then select~~ |-| '''~~zh_CN.UTF-8 UTF-8~~28''' ~~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>~~TWI2-SCL/UART3_TX'''~~, and then return Car can be used)[[File:zero2w-img186.png]]</li><li>Then set the default~~ | '''~~locale~~PI9''' to | '''~~zh_CN.UTF-8~~265'''~~[[File:zero2w~~|-~~img187.png]]</li><li>After exiting the interface, the~~ | '''~~locale~~30''' ~~setting will begin. > The output displayed on the command line is as follows:orangepi@orangepi:~$~~ | '''~~sudo dpkg-reconfigure locales~~GND'''~~Generating locales (this might take a while)...~~| style="text-align: left;"|~~en_US.UTF~~| style="text-~~8... done~~align: left;"|~~zh_CN.UTF~~|-~~8... doneGeneration complete.</li></ol>~~| '''32'''~~</li>~~| '''PWM1'''~~<li>Then open~~ | '''~~Input Method~~PI11'''~~[[File:zero2w~~| '''267'''|-~~img188.png]]</li><li>Then select~~ | '''OK34'''~~[[File:zero2w-img189.png]]</li><li>Then select~~ | '''GND''~~Yes~~'~~''[[File~~| style="text-align:~~zero2w-img190.png]]</li>~~left;"|| style="text-align: left;"||-~~<li>Then select~~ | '''~~fcitx~~36'''~~[[File~~| style="text-align:~~zero2w-img191.png]]</li>~~left;"|~~<li>Then select~~ | '''OKPC12'''~~[[File:zero2w~~| '''76'''|-~~img192.png]]</li><li>~~| '''~~Then restart the Linux system to make the configuration take effect.~~38'''~~</li><li>Then open~~ | style="text-align: left;"|| '''PI4'''| '''~~Fcitx configuration~~260'''~~[[File:zero2w~~|-~~img193.png]]</li><li>Then click the + sign as shown in the picture below~~| '''40'''| style="text-align: left;"|| '''PI3'''| '''259'''~~[[File:zero2w-img194.png]]</li>~~|}~~<li>Then search '''Google Pinyin''' and click '''OK'''~~<div ~~class="figure"~~>

<ol start="2" style="list-style-type: decimal;"><li>In Linux systems, uart is turned off by default and needs to be turned on manually before it can be used. The opening steps are as follows:: <ol style="list-style-type: lower-alpha;"><li>First run '''orangepi-config'''. Ordinary users remember to add '''sudo''' permissions.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo orangepi-config'''|}</li><li>Then select '''System'''[[File:zero2w-img80.png]]</li><li>Then select '''Hardware'''[[File:zero2w-~~img195~~img81.png]]</li><li>Then use the keyboard's arrow keys to locate the position shown in the picture below, and then use the '''space''' to select the serial port you want to open.</li>

{| class="wikitable" style="width:800px;text-align: center;"|-| '''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]]</~~div~~ol><~~/li~~ol start="5" style="list-style-type: lower-alpha;"><li>Then ~~put~~ select '''~~Google Pinyin~~<Save>''' ~~on top~~to save[[File:zero2w-~~img196.png]][[File:zero2w-img197~~img83.png]]</li><li>Then ~~open the~~ select '''~~Geany~~<Back>''' ~~editor to test the Chinese input method~~[[File:zero2w-~~img198~~img84.png]]</li><li>~~The Chinese input method test is as follows~~Then select '''<Reboot>''' to restart the system to make the configuration take effect.[[File:zero2w-~~img199~~img85.png]]</li></ol></li><p/ol>~~You can switch between Chinese and English input methods through the '''Ctrl+Space''' shortcut key~~</p!-- --><~~/li~~ol start="3" style="list-style-type: decimal;"><li>~~If you need~~ After entering the ~~entire~~ Linux system ~~to be displayed in Chinese~~, ~~you can set all variables in~~ first confirm whether there is a uart5 device node under '''/~~etc~~dev</~~default/locale~~span>''' to {| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~zh_CN~~注意, linux5.4系统为/dev/ttyASx.~~UTF-8~~'''</big>|}{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~sudo vim~~ ls /~~etc~~dev/~~default/locale~~ttyS*'''~~# File generated by update-locale~~/dev/ttySx|}</li><li>~~LC_MESSAGES='''zh_CN~~Then start testing the uart interface.~~UTF~~First use Dupont wire to short-~~8'''~~circuit the rx and tx pins of the uart interface to be tested.</li><li>~~LANG=~~Use the '''~~zh_CN.UTF-8~~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.{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>~~LANGUAGE=~~'''~~zh_CN~~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.~~UTF-8~~'''</libig>~~<li>~~|}{| class="wikitable" style="width:800px;" |-| ~~Then~~ orangepi@orangepi:~$ '''~~restart the system~~gpio serial /dev/ttySx        # linux-6.1 test command''' ~~and you will see that the system is displayed in Chinese.~~~~[[File~~orangepi@orangepi:~~zero2w~~~$ '''gpio serial /dev/ttyASx        # linux-~~img200~~5.~~png]]~~4 test command'''</p~~></li></ol~~>

~~~~

~~=== Installation method of Ubuntu 20.04 system ===~~

<~~ol style="list~~p>Out: 0: -~~style-type: decimal~~>"0<lip>Out: 1: -> 1~~First open '''Language Support'''~~Out: 2: -> 2~~[[File~~Out: 3:~~zero2w~~-~~img201.png]]~~> 3^C|}</li><li>~~Then find~~ Finally, you can run the '''~~Chinese (China)~~serialTest.py''' ~~option~~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.{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>~~[[File:zero2w-img202~~'''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.~~png]]~~'''</libig>~~<li>~~|}{| class="wikitable" style="width:800px;" |-| ~~Then please use the left button of the mouse to select~~ root@orangepi:~/wiringOP-Python# '''~~Chinese (China)~~cd examples''' ~~and hold it down, then drag it up to the starting position. After dragging, the display will be as shown below:~~~~[[File~~root@orangepi:~~zero2w~~~/wiringOP-~~img203~~Python/examples# '''python3 serialTest.~~png]]~~py --device "/dev/ttySx" # linux6.1 use'''root@orangepi:~/~~li>~~wiringOP-Python/examples# '''python3 serialTest.py --device "/dev/ttyASx" # linux5.4 use'''</olp>

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

~~<ol start="4" style="list-style-type: decimal;"><li>~~~~Then select '''Apply System~~Out: 0: -~~Wide''' to apply the Chinese settings to the entire system~~> 0~~[[File~~Out: 1:~~zero2w~~-~~img204.png]]~~> 1</p~~></li~~>~~<li>~~~~Then set the '''Keyboard input method system''' system to '''fcitx'''[[File~~Out: 2:~~zero2w~~-~~img205.png]]~~> 2</p~~></li~~>~~<li>~~~~'''Then restart the Linux system to make the configuration take effect'''</li><li>After re~~Out: 3: -entering the system, please select '''Do not ask me again''' in the following interface, and then please decide according to your own preferences whether the standard folder should also be updated to Chinese> 3~~[[File~~Out: 4:~~zero2w-img206.png]]~~^C</p~~></li~~>~~<li>~~~~Then you can see that the desktop is displayed in Chinese~~exit~~[[File:zero2w-img207.png]]~~|}</pli></liol>~~<li>Then we can open '''Geany''' to test the Chinese input method. The opening method is as shown in the figure below~~<~~p>[[File:zero2w~~span id="hardware-~~img208.png]]</li><li>After opening '''Geany''', the English input method is still the default. We can switch to the Chinese input method through the '''Ctrl+Space''' shortcut key, and then we can input Chinese.[[File:zero2w~~watchdog-~~img209.png]]</li~~test"></olspan>

~~=== Installation method of Ubuntu 22.04 system~~ =Hardware watchdog test ==

~~<ol style="list~~The watchdog_test program is pre-~~style-type: decimal;"><li>First open '''Language Support'''[[File:zero2w-img201.png]]</li><li>Then find~~ installed in the ~~'''Chinese (China)''' option[[File:zero2w-img210.png]]</li><li>Then please use the left button of the mouse to select '''Chinese (China)'''~~ Linux system released by Orange Pi and ~~hold it down, then drag it up to the starting position. After dragging, the display will~~ can be ~~as shown below:[[File:zero2w-img211~~tested directly.~~png]]</li></ol>~~

~~'''Note that this step~~ The method to run the watchdog_test program is ~~not easy to drag, please be patient and try it a few times.'''~~as follows:

<ol ~~start="4"~~ style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then select '''Apply System-Wide''' to apply~~ The second parameter 10 represents the counting time of the watchdog. If the ~~Chinese settings to~~ dog is not fed within this time, the ~~entire~~ system~~[[File:zero2w-img212~~will restart.~~png]]~~</li><li>~~'''Then restart~~ We can feed the dog by pressing any key on the keyboard (except ESC). After feeding the dog, the ~~Linux system~~ program will print a line "keep alive" to ~~make~~ indicate that the ~~configuration take effect'''~~dog feeding is successful.~~</li><li>~~{| class="wikitable" style="width:800px;" |-| ~~After re-entering the system, please select~~ orangepi@orangepi:~$ '''~~Do not ask me again~~sudo watchdog_test 10''' ~~in the following interface, and then please decide whether the standard folder should also be updated to Chinese according to your own preferences.~~~~[[File:zero2w-img206.png]]~~open successoptions is 33152,identity is sunxi-wdt</lip><lip>put_usr return,if 0,success:0~~Then you can see that the desktop~~ The old reset time is ~~displayed in Chinese~~: 16~~[[File~~return ENOTTY,if -1,success:~~zero2w-img207.png]]~~0return ENOTTY,if -1,success:0</lip>~~<li>~~~~Then open the Fcitx5 configuration program~~put_user return,if 0,success:0~~[[File~~put_usr return,if 0,success:~~zero2w-img213.png]]~~0keep alive</lip><lip>keep alive~~Then choose to use Pinyin input method~~keep alive|}</li><~~div class="figure"~~/ol>

~~[[File:zero2w~~

~~</div></li><li>The interface after selection is as shown below, then click OK[[File:zero2w-img215.png]]</li><li>Then we can open '''Geany''' to test~~ == Check the ~~Chinese input method. The opening method is as shown in the figure below[[File:zero2w-img208.png]]</li><li>After opening '''Geany''', the English input method is still the default. We can switch to the Chinese input method through the '''Ctrl+Space''' shortcut key, and then we can enter Chinese.[[File:zero2w-img216.png]]</li></ol>~~chipid of H618 chip ==

~~== How~~ H618 chip chipid is as follows. The chipid of each chip is different, so you can use chipid to ~~remotely log in to the Linux system desktop ==~~distinguish multiple development boards.

~~<~~| orangepi@orangepi:~$ '''cat /sys/class/sunxi_info/~~span>=== Remote login using NoMachine ===~~sys_info | grep "chipid"'''

'''Please ensure that the Ubuntu or Debian system installed on the development board is a desktop version of the system. In addition, NoMachine also provides detailed usage documentation. It is strongly recommended to read this document thoroughly to become familiar with the use of NoMachine. The document link is as followssunxi_chipid :~~'''~~338020004c0048080147478824681ed1|}

~~'''https:~~</~~/knowledgebase.nomachine.com/DT10R00166'''~~span>

'''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.'''== Python related instructions ==

~~'''Before operating, please make sure that the Windwos computer~~ === How to compile and ~~that you can log in to the Ubuntu or Debian system of the development board through ssh normally.'''~~install Python source code ===

~~<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <~~li><p~~big>~~First download the installation package of the NoMachine software Linux~~ '''~~arm64''' deb~~ If the Python version~~, and then install it into~~ in the ~~Linux~~ Ubuntu or Debian system of software repository you are using does not meet the development ~~board<ol style="list-style-type: lower-alpha;"><li>Since H618 is an ARMv8 architecture SOC~~ requirements and you want to use the ~~system we~~ latest version of Python, you can use ~~is > Ubuntu or Debian, we need~~ the following method to download the Python source code package to compile and install the latest version of Python.'''~~NoMachine for ARM > ARMv8 DEB''' installation package. The download link is as > follows:</li></ol></li></ol>~~

'''~~Note that this download link may change, please look for~~ The following demonstration is to compile and install the ~~Armv8/Arm64~~ latest version of Python 3.9. If you want to compile and install other versions of Python, the method is the same (you need to download the ~~deb package~~source code corresponding to the Python you want to install).'''</big>|}

[<ol style="list-style-type: decimal;"><li>First install the dependency packages needed to compile Python{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt-get update'''orangepi@orangepi:~$ '''sudo apt-get install -y build-essential zlib1g-dev \''''''libncurses5-dev libgdbm-dev libnss3-dev libssl-dev libsqlite3-dev \''''''libreadline-dev libffi-dev curl libbz2-dev'''|}</li><li>Then download the latest version of Python3.9 source code and unzip it{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''wget \''''''https://www.~~nomachine~~python.org/ftp/python/3.9.10/Python-3.9.10.tgz'''orangepi@orangepi:~$ '''tar xvf Python-3.9.10.~~com~~tgz'''</~~download~~p>|}</li><li>Then run the configuration command</~~download&id~~p>{| class=~~112&s~~"wikitable" style=~~ARM~~ "width:800px;" |-| orangepi@orangepi:~$ '''cd Python-3.9.10'''~~https~~orangepi@orangepi:~$ '''./configure --enable-optimizations'''</~~downloads~~p>|}</li><li>Then compile and install Python3.9.~~nomachine~~The compilation time takes about half an hour.~~com~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''make -j4'''</~~download~~p>orangepi@orangepi:~$ '''sudo make altinstall'''|}</li><li>After installation, you can use the following command to check the version number of the Python you just installed.</~~?id~~p>{| class="wikitable" style=~~118&amp~~"width:800px;~~distro=ARM~~" |-| orangepi@orangepi:~$ '''python3.9 --version''''''Python 3.9.10''']|}</li><li>Then update pip~~[[File~~{| class="wikitable" style="width:~~zero2w~~800px;" |-~~img217~~| orangepi@orangepi:~$ '''/usr/local/bin/python3.~~png]]~~9 -m pip install --upgrade pip'''|}</li></ol>

<~~ol start~~span id="~~2" style="list~~how-~~style~~to-~~type: lower~~replace-~~alpha;"><li>In addition, you can also download the '''NoMachine''' installation > package from the official tool.[[File:zero2w~~pip-~~img218.png]]First enter the '''remote login software-NoMachine''' folder[[File:zero2w-img219.png]]Then download the arm64 version of the deb installation package[[File:zero2w~~source-~~img220.png]]</li><li>Then upload the downloaded '''nomachine_x.x.x_x_arm64.deb''' to the > Linux system of the development board</li><li>Then use the following command to install '''NoMachine'''~~ in ~~the Linux > system of the development boardorangepi@orangepi:~$ '''sudo dpkg~~ -~~i nomachine_x.x.x_x_arm64_arm64.deb'''</li~~python"></olspan>

~~<ol start~~=~~"2" style~~=~~"list-style-type: decimal;"><li>Then download the installation package of the Windows version of the NoMachine software. The download address is as follows</li></ol>~~= How to replace pip source in Python ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~Note that this download link may~~ 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 changethe pip source.'''</big>|}

<ol style="list-style-type: decimal;"><li>First install '''python3-pip'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt-get update'''orangepi@orangepi:~$ '''sudo apt-get install -y python3-pip'''|}</li><li>How to permanently change the pip source under Linux<ol style="list-style-type: lower-alpha;"><li>First create a new '''~/.pip''' directory, then add the '''pip.conf''' configuration file, and set the pip source in it to Tsinghua source.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''mkdir -p ~/.pip'''orangepi@orangepi:~$ '''cat <<EOF > ~/.pip/pip.conf''''''[global]''''''timeout = 6000''''''index-url = https://~~downloads~~pypi.tuna.~~nomachine~~tsinghua.~~com~~edu.cn/~~download~~simple'''</~~?id~~p>'''trusted-host =9pypi.tuna.tsinghua.edu.cn''''''EOF'''|}~~[[File~~</li><li>Then use pip3 to install the Python library very quickly</li></ol></li><li>How to temporarily change the pip source under Linux, where '''<packagename>''' needs to be replaced with a specific package name{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''pip3 install <packagename> -i \''''''https:~~zero2w~~//pypi.tuna.tsinghua.edu.cn/simple -~~img221~~-trusted-host pypi.tuna.tsinghua.edu.~~png]]~~cn'''|}</li></ol>

~~<ol start~~=~~"3" style~~=~~"list-style-type: decimal;"><li>Then~~ How to install ~~NoMachine in Windows. '''Please restart your computer after installation.'''</li><li>Then open '''NoMachine''' in Window[[File:zero2w-img222.png]]</li>~~<li>After NoMachine is started, it will automatically scan other devices with NoMachine installed on the LAN. After entering the main interface of NoMachine, you can see that the development board is already in the list of connectable devices, and then click on the location shown in the red box in the picture below You can now log in to the Linux system desktop of the development board.~~[[File:zero2w-img223.png]]</li><li>Then click '''OK'''[[File:zero2w-img224.png]]</li><li>Then enter the username and password of the development board Linux system in the corresponding positions in the figure below, and then click OK to start logging in.[[File:zero2w-img225.png]]</li><li>Then click OK in the next interface.</li><li>Finally you can see the desktop of the development board Linux system[[File:zero2w-img226.png]]</li></ol>~~Docker ==

~~=== Remote login~~ installed, but the Docker service is not turned on by default. Use the '''enable_docker.sh''' script to enable the docker service, and then you can start using ~~VNC ===~~the docker command, and the docker service will be automatically started the next time you start the system.

{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''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 normallyenable_docker.sh'''|}

You can use the following command to test docker. If '''~~There are many problems with VNC testing in Ubuntu20.04, please do not use this method.~~hello-world'''can be run, docker can be used normally.

~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>First run the '''set_vnc.sh''' script to set up vnc, '''remember to add sudo permission'''s~~|-| ~~~~orangepi@orangepi:~$ '''~~sudo set_vnc.sh~~docker run hello-world'''~~You will require a password~~ Unable to ~~access your desktops.<~~find image 'hello-world:latest' locally latest: Pulling from library/p>hello-world 256ab8fe8778: Pull complete Digest: sha256:7f0a9f93b4aa3022c3a4c147a449ef11e0941a1fd0bf4a8e6c9408b2600777c5 ~~Password~~Status: Downloaded newer image for hello-world: ~~'''#Set the vnc password here, 8 characters~~latest '''<~~/p>Verify~~span style="color: ~~'''~~#~~Set the vnc password here, 8 characters'''~~FF0000">Hello from Docker!</pspan>~~Would you like to enter a view-only password (y/n)?~~ '''n '''</pspan style="color:#FF0000">~~xauth: file /root/~~This message shows that your installation appears to be working correctly.~~Xauthority does not exist~~</pspan>~~New~~ 'X' ~~desktop is orangepi:1Creating default startup script /root/.vnc/xstartup~~'~~Starting applications specified in /root/.vnc/xstartupLog file is /root/~~'''.~~vnc/orangepi:1~~….~~logKilling Xtightvnc process ID 3047New~~ 'X' ~~desktop is orangepi:1~~'~~Starting applications specified in /root/.vnc/xstartup~~|}~~Log file is /root/.vnc/orangepi:1.log</li><li>The steps to use MobaXterm software to connect~~ When using the docker command, if you are prompted for '''permission denied''', please add the current user to the ~~development board Linux system desktop are as follows:~~docker user group so that you can run the docker command without sudo. ~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>First click Session, then select VNC, then fill in the IP > address and port of the development board, and finally click > OK to confirm.</li></ol>~~|-| orangepi@orangepi:~$ '''sudo usermod -aG docker $USER'''~~</li></ol>~~|}

~~<div~~ {| class="~~figure~~wikitable" style="background-color:#ffffdc;width:800px;"|-| <big>'''Note: You need to log out and log in again to the system to take effect. You can also restart the system.'''</big>|}

~~[[File:zero2w~~

~~</div><ol start~~=~~"2" style~~=~~"list-style-type: lower-alpha;"><li>Then enter the VNC password set earlier[[File:zero2w-img228.png]]</li><li>After successful login, the interface is displayed as shown below, > and then you can remotely operate the desktop of the development > board Linux system.</li></ol>~~How to install Home Assistant ==

~~[[File~~{| class="wikitable" style="background-color:~~zero2w~~#ffffdc;width:800px;" |-~~img229~~| <big>'''Note that this article will only provide methods for installing Home Assistant in Ubuntu or Debian systems. For detailed usage of Home Assistant, please refer to the official documentation or corresponding books.~~png]]~~'''</big>|}

== ~~QT installation method~~ = Installation via docker ===

<li>~~Use~~ First, please install docker and ensure that docker can run normally. For the installation steps of docker, please refer to the instructions in the ~~following script~~ [[Orange Pi Zero 2W#How to install ~~QT5 and QT Creatororangepi@orangepi:~$~~ Docker|'''~~install_qt.sh~~How to Install Docker''']] section.</li><li>~~After installation,~~ Then you can search for the ~~QT version number will be automatically printed.~~docker image of Home Assistant~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>The qt version that comes with Ubuntu20.04 is '''5.12.8'''~~|-| orangepi@orangepi:~$ '''~~install_qt.sh~~docker search homeassistant'''~~......~~|}~~QMake version 3.1Using Qt version '''5.12.8''' in /usr/lib/aarch64-linux-gnu~~</li><li>Then use the following command to download the Docker image of Home Assistant to your local computer. The ~~QT version that comes with Ubuntu22.04~~ image size is ~~'''5~~about 1GB, and the download time will be relatively long.15Please be patient and wait for the download to complete.~~3'''~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~install_qt.sh~~docker pull homeassistant/home-assistant'''~~......~~Using default tag: latest~~QMake version 3.1~~latest: Pulling from homeassistant/home-assistant~~Using Qt version '''5.15.3''' in /usr/lib/aarch64-linux-gnu~~be307f383ecc: Downloading</p~~></li~~>~~<li>~~~~The QT version that comes with Debian11 is '''5.15.2'''~~5fbc4c07ac88: Download complete~~orangepi@orangepi:~$~~ '''~~install_qt~~.~~sh'''~~.....~~.QMake version 3.1Using Qt version '''5.15.2~~(Omit some output)''' ~~in /usr/lib/aarch64-linux-gnu~~</p~~></li~~>~~<li>~~~~The QT version that comes with Debian12 is '''5.15.8'''~~3cc6a1510c9f: Pull complete~~orangepi@orangepi~~7a4e4d5b979f:~~~$ '''install_qt.sh'''~~Pull complete~~......~~Digest: sha256:81d381f5008c082a37da97d8b08dd8b358dae7ecf49e62ce3ef1eeaefc4381bb~~QMake version 3.1~~Status: Downloaded newer image for homeassistant/home-assistant:latest~~Using Qt version '''5~~docker.~~15.8''' in~~ io/~~usr~~homeassistant/~~lib/aarch64~~home-~~linux-gnu~~assistant:latest~~</li></ol>~~|}

</li>

<li>Then you can ~~see~~ use the following command to view the ~~QT Creator startup icon in '''Applications'''~~docker image of Home Assistant you just downloaded~~[[File~~{| class="wikitable" style="width:~~zero2w~~800px;" |-~~img230.png]]You can also use the following command to open QT Creator~~| orangepi@orangepi:~$ '''~~qtcreator~~docker images homeassistant/home-assistant'''</p~~></li~~>~~<li>~~~~The interface after QT Creator is opened is as follows~~REPOSITORY                                    TAG       IMAGE       ID       CREATED       SIZE~~[[File:zero2w-img231.png]]<~~homeassistant/~~p></li><li>The version of QT Creator is as follows<ol style="list~~home-~~style-type: lower-alpha~~assistant       latest       bfa0ab9e1cf5       2 months ago    ">~~<li>The default version of QT Creator in '''Ubuntu20.04''' is as~~ &gtnbsp; ~~follows[[File:zero2w-img232.png]]</li><li>The default version of QT Creator in '''Ubuntu22.04''' is as~~ &gtnbsp; ~~follows[[File:zero2w-img233.png]]</li><li>The default version of QT Creator in~~ '''~~Debian11''' is as follows~~</pspan style="color:#FF0000">~~[[File:zero2w-img234~~1.~~png]]~~17GB</~~li><li><p~~span>~~The default version of QT Creator in ''~~'~~Debian12~~''~~' is as follows~~~~[[File:zero2w-img235.png]]</li></ol>~~|}

</li>

<li>~~Then set up QT~~At this point you can run the Home Assistant docker container~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>~~|-| ~~First open '''Help~~orangepi@orangepi:~$ '''docker run -~~>'''About Plugins...~~d \'''.:~~[[File:zero2w~~'''--~~img236.png]]~~name homeassistant \'''</p~~></li~~>~~<li>~~:~~Then remove the check mark of~~ '''~~ClangCodeModel~~--privileged \'''~~[[File~~:~~zero2w-img237.png]]</li><li>~~'''~~After setting up, you need to~~ --restart ~~QT Creator~~=unless-stopped \'''</p~~></li~~>~~<li>~~:~~Then make sure the GCC compiler used by QT Creator. If the > default is Clang, please change it to GCC.~~'''-e TZ=Asia/Shanghai \''':'''~~Debian12 please skip this step.~~-v /home/orangepi/home-assistant:/config \''':~~[[File:zero2w~~'''--~~img238.png]]~~network=host \''':~~[[File~~'''homeassistant/home-assistant:~~zero2w-img239.png]]~~latest'''~~</li></ol>~~|}

</li>

<li>Then ~~you can open a sample code[[File~~enter【the IP address of the development board:~~zero2w-img240.png]]</li><li>After clicking on~~ 8123】in the ~~sample code,~~ browser to see the ~~corresponding instruction document will automatically open. You can read the instructions carefully.~~Home Assistant interface~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~zero2w~~800px;" |-~~img241.png]]</li>~~| <libig>~~Then click~~ '''~~Configure Project'''[[File:zero2w-img242.png]]</li><li>Then click~~ It takes a while for the ~~green triangle in the lower left corner~~ Home Assistant container to ~~compile and run~~ start. If the ~~sample code[[File:zero2w-img243~~interface below does not display normally, please wait a few seconds before refreshing it.~~png]]</li><li>After~~ If the following interface is not displayed normally after waiting for more than a ~~period of~~ minute, it means there is a problem with the Home Assistant installation. At this time, you need to check whether there is a problem with the ~~interface shown in the figure below will pop up, which means that QT can compile~~ previous installation and ~~run normally.[[File:zero2w-img244.png]]</li><li>References[https://wiki.qt.io/Install_Qt_5_on_Ubuntu '''https://wiki~~setting process.~~qt.io/Install_Qt_5_on_Ubuntu~~''']<~~p>[https://download.qt.io~~/~~archive/qtcreator '''https://download.qt.io/archive/qtcreator''']</p~~big>|}<~~p>[https://download.qt.io/archive/qt '''https://download.qt.io/archive/qt''']</li></ol~~div class="figure">

~~== ROS installation method ==~~img180.png]]

<~~span id="how-to-install-ros-1-noetic-on-ubuntu20.04"~~/div></li><li>Then enter your '''name, username''' and '''password''' and click '''Create Account'''</~~span~~p><div class=~~== How to install ROS 1 Noetic on Ubuntu20.04 ===~~"figure">

~~# The currently active version of ROS 1 is as follows, the recommended version is '''Noetic Ninjemys'''~~[[File:zero2w-img181.png]]

~~[[File:zero2w-img245.png]]~~</div></li><li>Then follow the interface prompts to set according to your own preferences, and then click Next<div class="figure">

[[File:zero2w-~~img246~~img182.png]]

~~[http:~~</div></~~docs.ros.org~~li><li>Then click Next</ ~~'''http://docs.ros.org''']~~p><div class="figure">

~~'''https~~[[File:~~//wiki~~zero2w-img183.~~ros.org/Distributions'''~~png]]

~~<ol start="2" style="list-style-type: decimal;"><li>The link to the official installation documentation of ROS 1 '''Noetic Ninjemys''' is as follows:[http://wiki.ros.org/noetic/Installation/Ubuntu '''http://wiki.ros.org/noetic/Installation/Ubuntu''']</li>~~<li>In the official installation documentation of ROS '''Noetic Ninjemys''', Ubuntu recommends using Ubuntu20.04, so please ensure that the system used by the development board is '''Ubuntu20.04 desktop system'''.~~[http://wiki.ros.org/noetic/Installation '''http://wiki.ros.org/noetic/Installation'''][[File:zero2w-img247.png]]~~</pdiv></li><li>Then ~~use the script below to install ros1~~click Finish<~~p>orangepi@orangepi:~$ '''install_ros.sh ros1'''</li>~~<li>Before using the ROS tool, 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.</li></oldiv class="figure">

~~'''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~~[[File:zero2w-img184.~~'''~~png]]

~~'''~~</div></li><li>The ~~install_ros~~main interface finally displayed by Home Assistant is as shown below[[File:zero2w-img185.~~sh script will try to modify~~ png]]</~~etc~~p></hosts and automatically run the following commands. 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 li><li>Method to ~~allow the linux system of the development board~~ stop Home Assistant container<ol style="list-style-type: lower-alpha;"><li>The command to ~~access github normally, and then manually run~~ view the ~~following Order.~~docker container is as follows{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ ''' docker ps -a'''~~https:~~|}</~~raw.githubusercontent.com~~li><li>The command to stop the Home Assistant container is as follows</~~ros~~p>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''docker stop homeassistant'''</~~rosdistro~~p>|}</~~master~~li><li>The command to delete the Home Assistant container is as follows</~~rosdep/osx~~p>{| class="wikitable" style="width:800px;" |-~~homebrew.yaml~~| orangepi@orangepi:~$ '''docker rm homeassistant'''|}</li></ol></li></ol>

~~'''Hit https:~~</~~/raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml'''~~span>

~~'''ERROR: error loading sources list:'''~~=== Installation via python ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~The read operation timed out~~Before installation, please change the source of pip to a domestic source to speed up the installation of Python packages. For the configuration method, see the instructions in the section "[[Orange Pi Zero 2W#How to replace pip source in Python|How to Change the Pip Source of Python]]"'''</big>|}

<ol style="list-style-type: decimal;"><li>First install dependency packages{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~source~~ sudo apt-get update'''</~~opt~~p>orangepi@orangepi:~$ '''sudo apt-get install -y python3 python3-dev python3-venv \'''</~~ros~~p>'''python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential \'''</~~noetic~~p>'''libopenjp2-7 libtiff5 libturbojpeg0-dev tzdata'''</~~setup.bash~~p>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''If it is debian12, please use the following command:'''</big>orangepi@orangepi:~$ '''sudo apt-get update'''orangepi@orangepi:~$ '''sudo ~~rosdep init~~apt-get install -y python3 python3-dev python3-venv \''''''python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential \'''~~Wrote~~ '''libopenjp2-7 libturbojpeg0-dev tzdata'''</~~etc~~p>|}</~~ros~~li><li>Then you 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.</~~rosdep~~p>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The default Python version of Debian Bullseye is Python3.9, so there is no need to compile and install it.'''</~~sources~~p>'''The default Python version of Ubuntu Jammy is Python3.~~list~~10, so there is no need to compile and install it.d'''</~~20-~~p>'''The defaultPython version of Debian Bookworm is Python3.11, so there is no need to compile and install it.~~list~~'''</big>|}</li><li>Then create a Python virtual environment~~Recommended~~{| class="wikitable" style="background-color: #ffffdc;width:800px;" |-| <big>'''Debian Bookworm is python3.11, please ~~run~~remember to replace the corresponding command.'''</big>|}{| class="wikitable" style="width:800px;" ~~rosdep update~~|-| orangepi@orangepi:~$ '''~~rosdep update~~sudo mkdir /srv/homeassistant'''orangepi@orangepi:~$ '''sudo chown orangepi:orangepi /srv/homeassistant'''~~reading in sources list data from~~ orangepi@orangepi:~$ '''cd /~~etc~~srv/~~ros~~homeassistant'''</~~rosdep/sources~~p>orangepi@orangepi:~$ '''python3.~~list~~9 -m venv .d'''orangepi@orangepi:~$ '''source bin/activate'''~~Hit https~~(homeassistant) orangepi@orangepi:/srv/~~raw.githubusercontent.com~~homeassistant$|}</li><li>Then install the required Python packages{| class="wikitable" style="width:800px;" |-| (homeassistant) orangepi@orangepi:/~~ros~~srv/~~rosdistro~~homeassistant$ '''python3 -m pip install wheel'''</~~master~~p>|}</~~rosdep~~li><li>Then you can install Home Assistant Core</~~osx~~p>{| class="wikitable" style="width:800px;" |-~~homebrew.yaml~~| ~~Hit https~~(homeassistant) orangepi@orangepi:/srv/homeassistant$ '''pip3 install homeassistant'''</~~raw.githubusercontent.com~~p>|}</li><li>Then enter the following command to run Home Assistant Core{| class="wikitable" style="width:800px;" |-| (homeassistant) orangepi@orangepi:/~~ros~~srv/~~rosdistro~~homeassistant$ '''hass'''</~~master~~p>|}</~~rosdep~~li><li>Then enter【'''development board IP address: 8123'''】 in the browser to see the Home Assistant interface</~~base~~p>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''When you run the hass command for the first time, some libraries and dependency packages necessary for operation will be downloaded, installed and cached.~~yaml~~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.'''</big>|}<div class="figure">

~~Hit https~~[[File:~~//raw~~zero2w-img180.~~githubusercontent.com/ros/rosdistro/master/rosdep/python.yaml~~png]]

~~Hit https:~~</div></~~raw.githubusercontent.com~~li></~~ros/rosdistro/master/rosdep/ruby.yaml~~ol>

~~Hit https:~~</~~/raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml~~span>

~~Query rosdistro index https://raw.githubusercontent.com/ros/rosdistro/master/index-v4.yaml~~== OpenCV installation method ==

~~Skip end~~=== Use apt to install OpenCV ===

~~Skip end~~<ol style="list-style-type: decimal;"><li>The installation command is as follows{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt-get update'''orangepi@orangepi:~$ '''sudo apt-get install -y libopencv-dev python3-opencv'''|}</li><li>Then use the following command to print the version number of OpenCV. The output is normal, indicating that the OpenCV installation is successful.<ol style="list-style-type: lower-alpha;"><li>The version of OpenCV in Ubuntu22.04 is as follows:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3 -c "import cv2; print(cv2.__version__)"''''''4.5.4'''|}</li><li>The version ofOpenCV in Ubuntu20.04 is as follows:{| class="wikitable" style="width:800px;" |-~~life distro~~ | orangepi@orangepi:~$ '''python3 -c "~~bouncy~~import cv2; print(cv2.__version__)"''''''4.2.0'''~~Skip end~~|}</li><li>The version of OpenCV in Debian11 is as follows:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3 -c "import cv2; print(cv2.__version__)"''''''4.5.1'''|}</li><li>The version ofOpenCV in Debian12 is as follows:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3 -~~life distro~~ c "~~crystal~~import cv2; print(cv2.__version__)"''''''4.6.0'''|}</li></ol></li></ol>

~~Skip end~~

~~Skip end-of-life distro "eloquent"~~== Set up the Chinese environment and install the Chinese input method ==

~~Add distro &quot~~{| class="wikitable" style="background-color:#ffffdc;~~foxy&quot~~width:800px;" |-| <big>'''Note, before installing the Chinese input method, please make sure that the Linux system used by the development board is a desktop version.'''</big>|}

~~Add distro "galactic"~~=== Debian system installation method ===

~~Skip end~~<ol style="list-ofstyle-~~life distro &quot~~type: decimal;"><li>First set the default '''locale''' to Chinese<ol style="list-style-type: lower-alpha;~~groovy&quot~~"><li>Enter the following command to start configuring '''locale'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''|}</li>~~Add distro~~ <li>Then select '''zh_CN.UTF-8 UTF-8''' in the pop-up interface (use the up and down keys on the keyboard to move up and down, use the space bar to select, and finally use the Tab key to move the cursor to '''&~~quot~~lt;~~humble~~OK&~~quot~~gt;''', and then return Car can be used)[[File:zero2w-img186.png]]</li>~~Skip end~~<li>Then set the default '''locale''' to '''zh_CN.UTF-of8'''[[File:zero2w-~~life distro "hydro&quot~~img187.png]]</li><li>After exiting the interface, the '''locale''' setting will begin. The output displayed on the command line is as follows:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''Generating locales (this might take a while)...:en_US.UTF-8... done:zh_CN.UTF-8... doneGeneration complete.|}</li></ol></li><li>Then open '''Input Method'''[[File:zero2w-img188.png]]</li><li>Then select '''OK'''[[File:zero2w-img189.png]]</li><li>Then select '''Yes'''[[File:zero2w-img190.png]]</li><li>Then select '''fcitx'''[[File:zero2w-img191.png]]</li><li>Then select '''OK'''[[File:zero2w-img192.png]]</li><li>'''Then restart the Linux system to make the configuration take effect.'''</li><li>Then open '''Fcitx configuration'''[[File:zero2w-img193.png]]</li><li>Then click the + sign as shown in the picture below[[File:zero2w-img194.png]]</li><li>Then search '''Google Pinyin''' and click '''OK'''<div class="figure">

~~Skip end~~[[File:zero2w-~~of-life distro "indigo"~~img195.png]]

~~Skip end~~</div></li><li>Then put '''Google Pinyin''' on top[[File:zero2w-ofimg196.png]][[File:zero2w-~~life distro "jade&quot~~img197.png]]</li><li>Then open the '''Geany''' editor to test the Chinese input method[[File:zero2w-img198.png]]</li><li>The Chinese input method test is as follows[[File:zero2w-img199.png]]</li><li>You can switch between Chinese and English input methods through the '''Ctrl+Space''' shortcut key</li><li>If you need the entire system to be displayed in Chinese, you can set all variables in '''/etc/default/locale''' to '''zh_CN.UTF-8'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo vim /etc/default/locale'''# File generated by update-localeLC_MESSAGES='''zh_CN.UTF-8'''LANG='''zh_CN.UTF-8'''LANGUAGE='''zh_CN.UTF-8'''|}</li><li>Then '''restart the system''' and you will see that the system is displayed in Chinese.[[File:zero2w-img200.png]]</li></ol>

~~Skip end~~

~~Skip end-~~=== Installation method of~~-life distro "lunar"~~Ubuntu 20.04 system ===

~~Add distro &quot~~<ol style="list-style-type: decimal;~~melodic&quot~~"><li>First open '''Language Support'''[[File:zero2w-img201.png]]</li><li>Then find the '''Chinese (China)''' option[[File:zero2w-img202.png]]</li><li>Then please use the left button of the mouse to select '''Chinese (China)''' and hold it down, then drag it up to the starting position. After dragging, the display will be as shown below:[[File:zero2w-img203.png]]</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>|}~~Add distro "noetic&quot~~</ol><ol start="4" style="list-style-type: decimal;"><li>Then select '''Apply System-Wide''' to apply the Chinese settings to the entire system[[File:zero2w-img204.png]]</li><li>Then set the '''Keyboard input method system''' system to '''fcitx'''[[File:zero2w-img205.png]]</li><li>'''Then restart the Linux system to make the configuration take effect'''</li><li>After re-entering the system, please select '''Do not ask me again''' in the following interface, and then please decide according to your own preferences whether the standard folder should also be updated to Chinese[[File:zero2w-img206.png]]</li><li>Then you can see that the desktop is displayed in Chinese[[File:zero2w-img207.png]]</li><li>Then we can open '''Geany''' to test the Chinese input method. The opening method is as shown in the figure below[[File:zero2w-img208.png]]</li><li>After opening '''Geany''', the English input method is still the default. We can switch to the Chinese input method through the '''Ctrl+Space''' shortcut key, and then we can input Chinese.[[File:zero2w-img209.png]]</li></ol>

~~Add distro "rolling"~~

~~updated cache in /home/orangepi/~~=== Installation method of Ubuntu 22.~~ros/rosdep/sources.cache~~ ~~<ol start~~04 system ==~~"6" style~~=~~"list-style-type: decimal;"><li>Then open a command line terminal window on the '''desktop''', and then use the '''test_ros.sh''' script to start a small turtle routine to test whether ROS can be used normally.orangepi@orangepi:~$ '''test_ros.sh'''</li><li>After running the '''test_ros.sh''' script, a small turtle as shown in the picture below will pop up.[[File:zero2w-img248.png]]</li><li>Then please keep the terminal window you just opened at the top</li></ol>~~

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

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

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

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

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

[[File:zero2w-img211.png]]</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>

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

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

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

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

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

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

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

<li>Then open the Fcitx5 configuration program

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

<li>Then choose to use Pinyin input method

[[File:zero2w-~~img249~~img214.png]]

</div></li><~~ol start="9" style="list~~li>The interface after selection is as shown below, then click OK[[File:zero2w-~~style~~img215.png]]</li><li>Then we can open '''Geany''' to test the Chinese input method. The opening method is as shown in the figure below[[File:zero2w-~~type: decimal;"~~img208.png]]</li><li>~~At this time~~After opening '''Geany''', ~~press~~ the ~~direction keys on~~ English input method is still the ~~keyboard~~ default. We can switch to ~~control~~ the ~~little turtle to move up, down, left~~Chinese input method through the '''Ctrl+Space''' shortcut key, and ~~right~~then we can enter Chinese.[[File:zero2w-~~img250~~img216.png]]</li></ol> == How to remotely log in to the Linux system desktop ==

=== ~~How to install ROS 2 Galactic on Ubuntu20.04~~ Remote login using NoMachine ===

~~<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">~~<li>The currently active version of ROS 2 is as follows, the recommended version is '''Galactic Geochelone'''[[File:zero2w~~|-~~img251.png]][[File:zero2w-img252.png]][http://docs.ros.org/ '''http://docs.ros.org''']~~| <pbig>'''~~http://docs.ros.org/en/galactic/Releases.html'''</li><li>The link to the official installation documentation of ROS 2 '''Galactic Geochelone''' is as follows:'''docs.ros.org/en/galactic/Installation.html''''''http://docs.ros.org/en/galactic/Installation/Ubuntu-Install-Debians.html'''</li><li>In the official installation documentation of ROS 2 '''Galactic Geochelone''', Ubuntu Linux recommends using Ubuntu20.04, so please~~ Please ensure that the Ubuntu or Debian system ~~used by~~ installed on the development board is ~~the '''Ubuntu20.04 desktop system'''. There are several ways to install ROS 2. The following demonstrates how to install ROS 2 '''Galactic Geochelone''' through '''Debian packages'''.~~a <~~/p></li><li>Use the '''install_ros.sh''' script to install ros2orangepi@orangepi~~span style="color:~~~$ '''install_ros.sh ros2'''</p~~#FF0000">desktop version</lispan>~~<li>The '''install_ros.sh''' script will automatically run~~ of the ~~'''ros2 -h''' command after installing ros2~~system. ~~If you can see the following print~~In addition, ~~it means that the ros2 installation is complete.usage: ros2 [-h] Call `ros2 <command> -h` for more~~ NoMachine also provides detailed usagedocumentation. ~~...ros2~~ It is ~~an extensible command-line tool for ROS 2.optional arguments:-h, --help show~~ strongly recommended to read this ~~help message and exitCommands:action Various action related sub-commandsbag Various rosbag related sub-commandscomponent Various component related sub-commandsdaemon Various daemon related sub-commandsdoctor Check ROS setup and other potential issuesinterface Show information about ROS interfaceslaunch Run a launch filelifecycle Various lifecycle related sub-commandsmulticast Various multicast related sub-commandsnode Various node related sub-commandsparam Various param related sub-commandspkg Various package related sub-commandsrun Run a package specific executablesecurity Various security related sub-commandsservice Various service related sub-commandstopic Various topic related sub-commandswtf Use `wtf` as alias to `doctor`Call `ros2 <command> -h` for more detailed usage.</li><li>Then you can use the '''test_ros.sh''' script~~ document thoroughly to ~~test whether ROS 2 is installed successfully. If you can see~~ become familiar with the ~~following print, it means ROS 2 can run normally.orangepi@orangepi:~$ '''test_ros.sh'''[INFO] [1671174101.200091527] [talker]: Publishing: 'Hello World: 1'[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: 1][INFO] [1671174102.199572327] [talker]: Publishing: 'Hello World: 2'[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2][INFO] [1671174103.199580322] [talker]: Publishing: 'Hello World: 3'[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]</li><li>Run the following command to open rviz2orangepi@orangepi:~$ '''source /opt/ros/galactic/setup.bash'''orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''[[File:zero2w-img253.png]]</li><li>For how to~~ use ~~ROS, please refer to the documentation~~ of ~~ROS 2~~NoMachine.~~[http://docs.ros.org/en/galactic/Tutorials.html '''http~~The document link is as follows:~~//docs.ros.org/en/galactic/Tutorials.html~~'''~~]</li></ol>~~

'''https://knowledgebase.nomachine.com/DT10R00166'''<~~span id~~/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~~-install-ros-2-humble-~~remotely log in to the Linux system desktop of the Orange Pi development board through NoMachine in Windows. For installation methods on~~-ubuntu22~~other platforms, please refer to NoMachine's official documentation.~~04">~~'''</~~span~~big>|}{| class="wikitable" style=~~= How~~ "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 ~~install ROS 2 Humble on Ubuntu22~~the Ubuntu or Debian system of the development board through ssh normally.~~04 ===~~'''</big>|}

<li>~~Use~~ First download the ~~install_ros.sh script to '''install_ros.sh~~installation package of the NoMachine software Linux '''<~~/p>orangepi@orangepi~~span style="color:~~~$ '''install_ros.sh ros2'''</p~~#FF0000">arm64</lispan>~~<li>The~~ '''~~install_ros.sh''' script will automatically run the '''ros2 -h''' command after installing ros2. If you can see the following print~~deb version, and then install it ~~means that~~ into the Linux system of the ~~ros2 installation is complete.~~development board<~~p>usage~~ol style="list-style-type: ~~ros2 [~~lower-~~h] Call `ros2 &lt~~alpha;~~command> -h` for more detailed usage. ...</p~~"><pli>~~ros2~~ Since H618 is an ~~extensible command-line tool for ROS 2.optional arguments:-h, --help show this help message~~ ARMv8 architecture SOC and ~~exitCommands:action Various action related sub-commandsbag Various rosbag related sub-commandscomponent Various component related sub-commandsdaemon Various daemon related sub-commandsdoctor Check ROS setup and other potential issuesinterface Show information about ROS interfaceslaunch Run a launch filelifecycle Various lifecycle related sub-commandsmulticast Various multicast related sub-commandsnode Various node related sub-commandsparam Various param related sub-commandspkg Various package related sub-commandsrun Run a package specific executablesecurity Various security related sub-commandsservice Various service related sub-commandstopic Various topic related sub-commandswtf Use `wtf` as alias to `doctor`Call `ros2 <command> -h` for more detailed usage.</li><li>Then you can~~ the system we use ~~the '''test_ros.sh''' script~~ is Ubuntu or Debian, we need to ~~test whether ROS 2 is successfully installed. If you can see~~ download the ~~following print, it means ROS 2 can run normally.orangepi@orangepi:~$~~ '''~~test_ros.sh~~NoMachine for ARM ARMv8 DEB'''~~[INFO] [1671174101~~installation package.~~200091527] [talker]~~The download link is as follows: ~~Publishing: 'Hello World: 1'~~</pli>~~[INFO] [1671174101.235661048] [listener]~~{| class="wikitable" style="background-color: ~~I heard~~#ffffdc;width: ~~[Hello World: 1]~~800px;" ~~[INFO] [1671174102.199572327] [talker]: Publishing: 'Hello World: 2'~~|-~~[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]~~| <pbig>~~[INFO] [1671174103.199580322] [talker]: Publishing:~~ '~~Hello World: 3~~'~~[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]<~~'Note that this download link may change, please look for the Armv8/~~li><li>Run~~ Arm64 version of the ~~following command to open rviz2orangepi@orangepi:~$ '''source /opt/ros/humble/setup~~deb package.~~bash~~'''</pbig>~~orangepi@orangepi~~|}{| class="wikitable" style="width:~~~$ '''ros2 run rviz2 rviz2'''~~800px;" ~~[[File:zero2w~~|-~~img254.png]]</li><li>Reference documentation~~| ~~'''http://docs.ros.org/en/humble/index.html'''~~[~~http~~https://~~docs~~www.~~ros~~nomachine.~~org~~com/endownload/~~galactic/Tutorials.html~~ download&id=112&s=ARM '''~~http~~https://~~docs~~downloads.~~ros~~nomachine.~~org~~com/endownload/~~humble/Installation/Ubuntu-Install-Debians.html~~?id=118&distro=ARM''']~~</li></ol>~~|}

[[File:zero2w-img217.png]]</ol><~~span id~~ol start="2" style="~~how~~list-style-type: lower-alpha;"><li>In addition, you can also download the '''NoMachine''' installation package from the official tool.[[File:zero2w-img218.png]]First enter the '''remote login software-NoMachine''' folder[[File:zero2w-img219.png]]Then download the arm64 version of the deb installation package[[File:zero2w-img220.png]]</li><li>Then upload the downloaded '''nomachine_x.x.x_x_arm64.deb''' tothe Linux system of the development board</li><li>Then use the following command to install '''NoMachine''' in the Linux system of the development board{| class="wikitable" style="width:800px;" |-~~install~~| orangepi@orangepi:~$ '''sudo dpkg -~~kernel~~i nomachine_x.x.x_x_arm64_arm64.deb'''|}</li></ol></li></ol><ol start="2" style="list-~~header~~style-~~files~~type: decimal;"><li>Then download the installation package of the Windows version of the NoMachine software. The download address is as follows</~~span~~li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that this download link may change.'''</big>|}{| class= ~~How to install kernel header files~~ "wikitable" style="width:800px;" |-| '''https://downloads.nomachine.com/download/?id=9'''|}

[[File:zero2w-img221.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then install NoMachine in Windows. '''Please restart your computer after installation.'''</li><li>Then open '''NoMachine'''~~Debian11 system with Linux6~~in Window[[File:zero2w-img222.~~1 kernel~~ png]]</li><li>After NoMachine is started, it will ~~report GCC error when compiling kernel module~~automatically scan other devices with NoMachine installed on the LAN. ~~So if~~ After entering the main interface of NoMachine, you ~~want~~ 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 ~~compile~~ the ~~kernel module, please use Debian12 or Ubuntu22~~Linux system desktop of the development board.04[[File:zero2w-img223.png]]</li><li>Then click '''OK'''[[File:zero2w-img224.png]]</li><li>Then enter the username and password of the development board Linux system in the corresponding positions in the figure below, and then click OK to start logging in.[[File:zero2w-img225.png]]</li><li>Then click OK in the next interface.</li><li>Finally you can see the desktop of the development board Linux system[[File:zero2w-img226.png]]</li></ol>

<~~ol style~~span id="~~list~~remote-~~style~~login-~~type: decimal;~~using-vnc">~~<li>The Linux image released by OPi comes with the deb package of the kernel header file by default, and the storage location is '''/opt/'''~~</pspan>~~orangepi@orangepi:~$ '''ls /opt/linux-headers*'''/opt/linux-headers-xxx-sun50iw9_x.x.x_arm64.deb</li><li>Use the following command to install the deb package of the kernel header fileorangepi@orangepi:~$ '''sudo dpkg -i /opt/linux-headers*.deb'''</li><li>After installation, you can see the folder where the kernel header file is located under '''/usr/src'''.orangepi@orangepi:~$ '''ls /usr/src'''linux-headers-x.x.x</li>~~<li>Then you can compile the source code of the hello kernel module that comes with the Linux image. The source code of the hello module is in '''/usr/src/hello'''. After entering this directory, then use the make command to compile.~~orangepi@orangepi:~$ '''cd /usr/src/hello/'''orangepi@orangepi:/usr/src/hello$ '''sudo make'''make -C /lib/modules/5.4.125/build M~~=~~/usr/src/hello modulesmake[1]: Entering directory '/usr/src/linux-headers-5.4.125'CC [M] /usr/src/hello/hello.oBuilding modules, stage 2.MODPOST 1 modulesCC [M] /usr/src/hello/hello.mod.oLD [M] /usr/src/hello/hello.komake[1]: Leaving directory '/usr/src/linux-headers-5.4.125'</li><li>After compilation, the '''hello.ko''' kernel module will be generatedorangepi@orangepi:/usr/src/hello$ '''ls *.ko'''hello.ko</li><li>Use the '''insmod''' command to insert the '''hello.ko''' kernel module into the kernelorangepi@orangepi:/usr/src/hello$ '''sudo insmod hello.ko'''</li>~~<li>Then use the '''demsg''' command to view the output of the '''hello.ko''' kernel module. If you can see the following output, it means that the '''hello.ko''' kernel module is loaded correctly.~~orangepi@orangepi:/usr/src/hello$ '''dmesg | grep "Hello"'''[ 2871.893988] '''Hello Orange Pi -- init'''</li><li>Use the '''rmmod''' command to uninstall the '''hello.ko''' kernel moduleorangepi@orangepi:/usr/src/hello$ '''sudo rmmod hello'''orangepi@orangepi:/usr/src/hello$ '''dmesg | grep "Hello"'''[ 2871.893988] Hello Orange Pi -- init[ 3173.800892] '''Hello Orange Pi -- exit'''</li></ol>~~== Remote login using VNC ===

~~~~| <~~/span~~big>~~== Testing~~ '''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 ~~some programming languages supported by Linux system ==~~the development board through ssh normally.'''

'''There are many problems with VNC testing in Ubuntu20.04, please do not use this method.'''</big>~~=== Debian Bullseye system ===~~|}

<li>~~Debian Bullseye~~ First run the '''set_vnc.sh''' script to set up vnc, '''remember to add sudo permission'''s{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo set_vnc.sh'''You will require a password to access your desktops. Password:        '''#Set the vnc password here, 8 characters'''Verify:        '''#Set the vnc password here, 8 characters'''Would you like to enter a view-only password (y/n)? '''n'''xauth: file /root/.Xauthority does not exist New 'X' desktop is ~~installed with the gcc compilation tool chain by~~ orangepi:1 Creating default~~, which can directly compile C language programs~~ startup script /root/.vnc/xstartupStarting applications specified in /root/.vnc/xstartupLog file is /root/.vnc/orangepi:1.log Killing Xtightvnc process ID 3047 New 'X' desktop is orangepi:1 Starting applications specified in /root/.vnc/xstartupLog file is /root/.vnc/orangepi:1.log|}</li><li>The steps to use MobaXterm software to connect to the development board Linux system ~~of the development board.~~desktop are as follows:

<li>~~The version of a.gcc is as followsorangepi@orangepi:~$ '''gcc --version'''gcc (Debian 10.2.1-6) 10.2.1 20210110Copyright (C) 2020 Free Software Foundation~~First click Session, then select VNC, ~~Inc.This is free software; see~~ then fill in the ~~source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</li><li>Write~~ IP address and port of the ~~'''hello_world.c''' program in C languageorangepi@orangepi:~$ '''vim hello_world.c'''#include <stdio.h>int main(void){printf("Hello World!\n");return 0;}</li><li>Then compile~~ development board, and ~~run '''hello_world.c'''orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''orangepi@orangepi:~$ '''~~finally click OK to confirm.~~/hello_world'''Hello World!~~</li~~></ol~~>~~</li>~~<~~li>Debian Bullseye has Python3 installed by default<ol style~~div class="~~list-style-type: lower-alpha;~~figure">~~<li>The specific version of Python is as followsorangepi@orangepi~~[[File:~~~$ '''python3''''''Python 3~~zero2w-img227.~~9.2''' (default, Feb 28 2021, 17:03:44)[GCC 10.2.1 20210110~~png]] ~~on linuxType "help", "copyright", "credits" or "license" for more information.>>>'''Use the Ctrl+D shortcut key to exit python's interactive mode.'''</li><li>Write the '''hello_world.py''' program in Python languageorangepi@orangepi:~$ '''vim hello_world.py'''~~~~print('Hello World!')</li><li>The result of running '''hello_world.py''' is as followsorangepi@orangepi:~$ '''python3 hello_world.py'''Hello World!</li~~div></ol>~~</li><li>Debian Bullseye does not install Java compilation tools and operating environment by default.</p~~><ol start="2" style="list-style-type: lower-alpha;"><li>~~You can use~~ Then enter the ~~following command to install openjdk. The latest > version in Debian Bullseye is openjdk-17~~VNC password set earlier~~orangepi@orangepi~~[[File:~~~$ '''sudo apt install~~ zero2w-~~y openjdk-17-jdk'''~~img228.png]]</li><li>After ~~installation~~successful login, the interface is displayed as shown below, and then you can ~~check~~ remotely operate the desktop of the ~~Java version~~development board Linux system.~~orangepi@orangepi:~$ '''java --version'''~~</li>~~<li>Write the Java version of '''hello_world.java'''orangepi@orangepi~~[[File:~~~$ '''vim hello_world~~zero2w-img229.~~java'''public class hello_world{public static void main(String[~~png]] ~~args){System.out.println("Hello World!");}}</li><li>Then compile and run '''hello_world.java'''orangepi@orangepi:~$ '''javac hello_world.java'''orangepi@orangepi:~$ '''java hello_world'''Hello World!</li>~~</ol>

</li></ol>

~~=== Debian Bookworm system~~ =QT installation method ==

<li>~~Debian Bookworm is installed with~~ Use the ~~gcc compilation tool chain by default, which can directly compile C language programs in the Linux system of the development board.~~following script to install QT5 and QT Creator~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>The version of a.gcc is as followsorangepi@orangepi:~$ '''gcc -~~|-~~version'''gcc (Debian 12.2.0-14) 12.2.0Copyright (C) 2022 Free Software Foundation, Inc.This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</li><li>Write the '''hello_world.c''' program in C language~~| orangepi@orangepi:~$ '''~~vim hello_world~~install_qt.csh'''~~#include <stdio.h>int main(void){printf("Hello World!\n");return 0;~~|}~~</li><li>Then compile and run '''hello_world.c'''orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''orangepi@orangepi:~$ '''./hello_world'''Hello World!</li></ol>~~

</li>

<li>~~Debian Bookworm has Python3 installed by default~~After installation, the QT version number will be automatically printed.

<li>The ~~specific~~ qt version ~~of Python~~ that comes with Ubuntu20.04 is ~~as follows~~'''5.12.8'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~python3~~install_qt.sh'''~~Python 3~~.11.~~2 (main, Mar 13 2023, 12:18:29) [GCC 12~~.2.~~0] on linux~~..~~Type "help", "copyright", "credits" or "license" for more information~~QMake version 3.1~~>>>~~Using Qt version '''</pspan style="color:#FF0000">5.12.8<p/span>'''~~Use the Ctrl+D shortcut key to exit python's interactive mode.'''~~in /usr/lib/aarch64-linux-gnu|}</li><li>~~Write the~~ The QT version that comes with Ubuntu22.04 is '''~~hello_world~~5.py15.3''' ~~program in Python language~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~vim hello_world~~install_qt.pysh'''~~print('Hello World!')~~......</p~~></li~~>~~<li>~~~~The result of running '''hello_world~~QMake version 3.~~py''' is as follows~~1~~orangepi@orangepi:~$~~ Using Qt version '''~~python3 hello_world~~5.15.py3'''<in /p>~~Hello World!<~~usr/~~p><~~lib/~~li>~~aarch64-linux-gnu</olp>|}

</li>

<li>~~Debian Bookworm does not install Java compilation tools and operating environment by default~~The QT version that comes with Debian11 is '''5.15.2'''~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>You can use the following command to install openjdk. The latest > version in Debian Bookworm is openjdk~~|-~~17~~| orangepi@orangepi:~$ '''~~sudo apt install -y openjdk-17-jdk~~install_qt.sh'''......</lip>~~<li>~~~~After installation, you can check the Java~~ QMake version3.1~~orangepi@orangepi~~Using Qt version '''5.15.2'''~~java~~ in /usr/lib/aarch64-linux-~~version'''~~gnu|}</li><li>~~Write the Java~~ The QT version of that comes with Debian12 is '''~~hello_world~~5.~~java~~15.8'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~vim hello_world~~install_qt.~~java~~sh'''~~public class hello_world~~......{QMake version 3.1~~public static void main(String[] args)~~Using Qt version '''</pspan style="color:#FF0000">5.15.8<p/span>{<''' in /usr/lib/p>~~System.out.println("Hello World!");~~aarch64-linux-gnu~~~~|}</pli>~~}~~</pol></li><li>Then ~~compile and run~~ you can see the QT Creator startup icon in '''~~hello_world.java~~Applications'''~~orangepi@orangepi~~[[File:~~~$ '''javac hello_world~~zero2w-img230.~~java'''~~png]]You can also use the following command to open QT Creator{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~java hello_world~~qtcreator'''~~Hello World!~~|}</pli></li><~~/ol~~p>The interface after QT Creator is opened is as follows</lip><~~/ol~~p> ~~~~img231.png]]</~~span~~p>~~=== Ubuntu Focal system ===~~ <~~ol style="list-style-type: decimal;"~~/li><li>~~Ubuntu Focal~~ The version of QT Creator 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.~~as follows

<li>The default version of ~~a.gcc is as followsorangepi@orangepi:~$~~ QT Creator in '''~~gcc --version~~Ubuntu20.04'''is as follows~~gcc (Ubuntu 9.4.0~~[[File:zero2w-~~1ubuntu1~20.04.1) 9.4.0Copyright (C) 2019 Free Software Foundation, Inc.This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE~~img232.png]]</li><li>~~Write the~~ The default version of QT Creator in '''~~hello_world~~Ubuntu22.c04''' ~~program in C language~~is as follows~~orangepi@orangepi~~[[File:~~~$ '''vim hello_world.c'''#include <stdio~~zero2w-img233.~~h>int main(void){printf("Hello World!\n");return 0;}~~png]]</li><li>~~Then compile and run~~ The default version of QT Creator in '''~~hello_world.c~~Debian11'''is as follows~~orangepi@orangepi~~[[File:~~~$ '''gcc~~ zero2w-~~o hello_world hello_world~~img234.~~c'''~~png]]</li><li>~~orangepi@orangepi:~$~~ The default version of QT Creator in '''~~./hello_world~~Debian12'''is as follows~~Hello World!~~[[File:zero2w-img235.png]]</li></ol>

</li>

<li>~~Ubuntu Focal has Python3 installed by default~~Then set up QT

<li>~~The specific version of Python3 is as followsorangepi@orangepi:~$~~ First open '''Help'''~~python3~~->'''~~Python 3~~About Plugins...8'''.~~10 (default, Nov 14 2022, 12:59:47)~~[~~GCC 9~~[File:zero2w-img236.~~4.0~~png]] ~~on linux~~<p/li>~~Type "help", "copyright", "credits" or "license" for more information.~~</pli>~~>>>~~Then remove the check mark of '''ClangCodeModel'''~~'''Use the Ctrl+D shortcut key to exit python's interactive mode~~[[File:zero2w-img237.~~'''~~png]]</li><li>~~Write the '~~''~~hello_world.py~~'~~'' program in Python language~~</pspan style="color:#FF0000">After setting up, you need to restart QT Creator<p/span>~~orangepi@orangepi:~$ '''vim hello_world.py~~'''</li><pli>~~print('Hello World!')~~Then make sure the GCC compiler used by QT Creator. If the default is Clang, please change it to GCC.</lip>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <libig>~~The result of running~~ '''~~hello_world~~Debian12 please skip this step.py''' ~~is as follows~~</big>|}~~orangepi@orangepi~~[[File:~~~$ '''python3 hello_world~~zero2w-img238.~~py'''~~png]]~~Hello World!~~[[File:zero2w-img239.png]]</li></ol>

</li>

<li>~~Ubuntu Focal does not have Java compilation tools and running environment installed by default.<ol style="list-style-type: lower-alpha;"><li>You~~ Then you can ~~use the following command to install openjdk-17~~open a sample code~~orangepi@orangepi~~[[File:~~~$ '''sudo apt install~~ zero2w-~~y openjdk-17-jdk'''~~img240.png]]</li><li>After ~~installation~~clicking on the sample code, ~~you~~ the corresponding instruction document will automatically open. You can ~~check~~ read the ~~Java version~~instructions carefully.~~orangepi@orangepi~~[[File:~~~$ '''java~~ zero2w-~~-version'''~~img241.png]]<p/li>~~openjdk 17.0.2 2022-01-18~~</pli>~~OpenJDK Runtime Environment (build 17.0.2+8-Ubuntu-120.04)~~Then click '''Configure Project'''~~OpenJDK 64~~[[File:zero2w-~~Bit Server VM (build 17~~img242.~~0.2+8-Ubuntu-120.04, mixed mode, sharing)~~png]]</li><li>~~Write~~ Then click the green triangle in the lower left corner to compile and run the ~~Java version of '''hello_world.java'''~~sample code~~orangepi@orangepi~~[[File:~~~$ '''vim hello_world~~zero2w-img243.~~java'''~~png]]<p/li>~~public class hello_world~~</pli>{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.~~public static void main(String~~[[File:zero2w-img244.png]] ~~args)~~~~{~~</pli><pli>~~System.out.println("Hello World!");~~}References{| class="wikitable" style="width:800px;" |-| }<[https://~~p><~~wiki.qt.io/~~li><li>Then compile and run~~ Install_Qt_5_on_Ubuntu '''~~hello_world~~https://wiki.qt.~~java~~io/Install_Qt_5_on_Ubuntu''']~~orangepi@orangepi~~[https:~$ //download.qt.io/archive/qtcreator '''~~javac hello_world~~https://download.qt.~~java~~io/archive/qtcreator''']~~orangepi@orangepi~~[https:~$ //download.qt.io/archive/qt '''~~java hello_world~~https://download.qt.io/archive/qt''']~~Hello World!</li></ol>~~|}

</li></ol>

== ROS installation method == === ~~Ubuntu Jammy system~~ How to install ROS 1 Noetic on Ubuntu20.04 === # The currently active version of ROS 1 is as follows, the recommended version is '''Noetic Ninjemys''' ::[[File:zero2w-img245.png]]

~~<ol style="list-style-type~~: ~~decimal;"><li>Ubuntu Jammy 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.<ol style="list-style-type~~: ~~lower-alpha;"><li>The version of a.gcc is as followsorangepi@orangepi:~$ '''gcc --version'''gcc (Ubuntu 11.3.0-1ubuntu1~22.04.1) '''11.3.0'''Copyright (C) 2021 Free Software Foundation, Inc.This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</li><li>Write the '''hello_world.c''' program in C languageorangepi@orangepi:~$ '''vim hello_world.c'''#include <stdio.h>int main(void){printf("Hello World!\n");return 0;}</li><li>Then compile and run '''hello_world.c'''orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''orangepi@orangepi:~$ '''./hello_world'''Hello World!</li></ol></li><li>Ubuntu Jammy has Python3 installed by default<ol style="list-style-type~~[[File: ~~lower~~zero2w-~~alpha;"><li>The specific version of Python3 is as followsorangepi@orangepi:~$ '''python3'''Python 3~~img246.~~10.6 (main, May 29 2023, 11:10:38) [GCC 11.3.0~~png] ~~on linuxType "help", "copyright", "credits" or "license" for more information.>>>'''Use the Ctrl+D shortcut key to exit python's interactive mode.'''</li><li>Write the '''hello_world.py''' program in Python languageorangepi@orangepi:~$ '''vim hello_world.py'''print('Hello World!')</li><li>The result of running '''hello_world.py''' is as followsorangepi@orangepi:~$ '''python3 hello_world.py'''Hello World!</li></ol></li><li>Ubuntu Jammy does not install Java compilation tools and operating environment by default.<ol style="list-style-type: lower-alpha;"><li>You can use the following command to install openjdk-18orangepi@orangepi:~$ '''sudo apt install -y openjdk-18-jdk'''</li><li>After installation, you can check the Java version.orangepi@orangepi:~$ '''java --version'''openjdk 18.0.2-ea 2022-07-19OpenJDK Runtime Environment (build 18.0.2-ea+9-Ubuntu-222.04)OpenJDK 64-Bit Server VM (build 18.0.2-ea+9-Ubuntu-222.04, mixed mode, sharing)</li><li>Write the Java version of '''hello_world.java'''orangepi@orangepi:~$ '''vim hello_world.java'''public class hello_world{public static void main(String[~~] ~~args){System.out.println("Hello World!");}}</li><li>Then compile and run '''hello_world.java'''orangepi@orangepi:~$ '''javac hello_world.java'''orangepi@orangepi:~$ '''java hello_world'''Hello World!</li></ol></li></ol>~~

~~<~~| [http://docs.ros.org/ '''http://~~span>== Method of uploading files to the development board Linux system ==~~docs.ros.org''']

~~<~~'''https:/~~span>~~/wiki.ros.org/Distributions'''~~=== Method to upload files to the development board Linux system in Ubuntu PC ===~~|}

<~~span id~~ol start="~~how-to-upload-files-using-scp-command~~2"~~>==== How to upload files using scp command ====~~ ~~<ol~~ style="list-style-type: decimal;"><li>~~Use the scp command to upload files~~ The link to the ~~Linux system~~ official installation documentation of ~~the development board in Ubuntu PC. The specific command~~ ROS 1 '''Noetic Ninjemys''' is as follows:~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>~~|-| ~~'''file_path~~[http: ~~'''Needs to be replaced with the path of the file to > be uploaded<~~/~~p><~~/~~li><li>'''orangepi: '''This is the user name of the development board's > Linux system~~wiki. ~~It can also be replaced with something else, > such as root~~ros.<org/noetic/~~p><~~Installation/~~li><li>~~Ubuntu '''~~192.168.xx.xx~~http:~~''' This is the IP address of the development > board. Please modify it according to the actual situation.<~~/~~p><~~/~~li><li>'''/home/orangepi:''' The path in the development board Linux > system can also be modified to other paths.test@test:~$ '''scp file_path orangepi@192.168~~wiki.xxros.~~xx:~~org/~~home~~noetic/~~orangepi~~Installation/Ubuntu''']~~</li></ol>~~|}

</li>

<li>~~If you want to upload a folder~~In the official installation documentation of ROS '''Noetic Ninjemys''', Ubuntu recommends using Ubuntu20.04, ~~you need to add~~ so please ensure that the system used by the ~~-r parameter~~development board is '''Ubuntu20.04 desktop system'''.{| class="wikitable" style="width:800px;" |-| ~~test@test~~[http:~$ //wiki.ros.org/noetic/Installation '''~~scp -r dir_path orangepi@192~~http://wiki.~~168~~ros.xxorg/noetic/Installation'''][[File:zero2w-img247.~~xx:~~png]]</~~home~~p>|}</li><li>Then use the script below to install ros1{| class="wikitable" style="width:800px;" |-| orangepi/@orangepi:~$ '''install_ros.sh ros1'''|}</li><li>~~There are more usages of scp~~Before using the ROS tool, ~~please use the following command~~ you first need to ~~view~~ initialize rosdep. Then when compiling the ~~man manual~~source code, you can quickly install some system dependencies and some core components in ROS.</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''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.</olspan>'''

~~test@test:~$~~ '''~~man scp~~The install_ros.sh script will try to modify /etc/hosts and automatically run the following commands. However, this method cannot guarantee that github can be accessed normally every time. If install_ros.sh prompts the following error after installing ros1, please find other ways to allow the linux system of the development board to access github normally, and then manually run the following Order.'''

~~~~

~~==== How to upload files using filezilla ====~~

~~<ol style="list-style-type: decimal;"><li>First install filezilla in Ubuntu PCtest@test:~$~~ '''~~sudo apt install -y filezilla'''<~~https://raw.githubusercontent.com/ros/rosdistro/~~p><~~master/~~li><li>Then use the following command to open filezilla<~~rosdep/p>~~test@test:~$~~ osx-homebrew.yaml'''~~filezilla'''</li><li>The interface after opening filezilla is as shown below. At this time, the remote site on the right is empty.<div class="figure">~~

~~[[File~~'''Hit https:~~zero2w-img255~~//raw.~~png]]~~githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml'''

'''<~~/div></li><li>The method of connecting the development board is as shown in the figure below</li~~span style="color:#FF0000">ERROR: error loading sources list:</olspan>'''

::'''<~~div~~ span style="color:#FF0000">The read operation timed out'''</big>|}{| class="~~figure~~wikitable" style="width:800px;">|-| orangepi@orangepi:~$ '''source /opt/ros/noetic/setup.bash'''

~~[[File~~orangepi@orangepi:~~zero2w-img256.png]]~~~$ '''sudo rosdep init'''

<Wrote /~~div><ol start="5" style="~~etc/ros/rosdep/sources.list~~-style-type: decimal;"><li>Then choose to '''save the password''' and click '''OK'''<~~.d/p>~~[[File:zero2w~~20-~~img257~~default.~~png]]</li><li>Then select '''Always trust this host''' and click '''OK'''</li></ol>~~list

~~<div class="figure">~~Recommended: please run

~~[[File:zero2w-img258.png]]~~

~~</div><ol start="7" style="list-style-type~~: ~~decimal;"><li>After the connection is successful, you can see the directory structure of the development board's Linux file system on the right side of the filezilla software.</li></ol>~~:rosdep update

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

~~[[File:zero2w-img259~~reading in sources list data from /etc/ros/rosdep/sources.~~png]]~~list.d

<Hit https:/~~div><ol start="8" style="list-style-type: decimal;">~~<li>Then select the path to be uploaded to the development board on the right side of the filezilla software, select the file to be uploaded in Ubuntu PC on the left side of the filezilla software, right-click the mouse, and then click the upload option to start uploading the file to the development board/raw.githubusercontent.<com/ros/rosdistro/master/~~li><~~rosdep/~~ol>~~osx-homebrew.yaml

~~<div class="figure">~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml

~~[[File~~Hit https:~~zero2w-img260~~//raw.~~png]]~~githubusercontent.com/ros/rosdistro/master/rosdep/python.yaml

<Hit https:/~~div><ol start="9" style="list-style-type: decimal;"><li>After the upload is completed, you can go to the corresponding path in the development board Linux system to view the uploaded file~~/raw.githubusercontent.<com/~~p><~~ros/~~li><li>The method of uploading a folder is the same as the method of uploading a file, so I won't go into details here.<~~rosdistro/~~p><~~master/~~li><~~rosdep/~~ol>~~ruby.yaml

~~<~~Hit https:/~~span>=== Method to upload files from Windows PC to development board Linux system ===~~/raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml

~~==== How to upload files using filezilla ====~~v4.yaml

~~# First download the installation file~~ Skip end-of ~~the Windows version of the filezilla software. The download link is as follows~~-life distro "ardent"

~~[https://filezilla~~Skip end-~~project.org/download.php?type=client '''https://filezilla~~of-~~project.org/download.php?type=client''']~~life distro "bouncy"

~~[[File:zero2w~~Skip end-~~img261.png]]~~of-life distro "crystal"

~~<div class="figure">~~Skip end-of-life distro "dashing"

~~[[File:zero2w~~Skip end-~~img262.png]]~~of-life distro "eloquent"

~~</div><ol start="2" style="list-style-type: decimal~~Add distro "foxy"">~~<li>The downloaded installation package is as shown below, then double-click to install it directly'''FileZilla_Server_1.5.1_win64-setup.exe'''</li></ol>~~

~~During the installation process, please select '''Decline''' on the following installation interface, and then select '''Next~~Add distro &gtquot;galactic"~~'''~~

~~<div class="figure">~~Skip end-of-life distro "groovy"

~~[[File:zero2w-img263.png]]~~Add distro "humble"

~~</div><ol start="3" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "hydro"">~~<li>The interface after opening filezilla is as shown below. At this time, the remote site on the right is empty.</li></ol>~~

~~<div class="figure">~~Skip end-of-life distro "indigo"

~~[[File:zero2w~~Skip end-~~img264.png]]~~of-life distro "jade"

~~</div><ol start="4" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "kinetic"">~~<li>The method of connecting the development board is as shown in the figure below:</li></ol>~~

~~<div class="figure">~~Skip end-of-life distro "lunar"

~~[[File:zero2w-img256.png]]~~Add distro "melodic"

~~</div><ol start="5" style="list-style-type: decimal~~Add distro "noetic"">~~<li>Then choose to '''save the password''' and click '''OK'''</li></ol>~~

~~<div class="figure">~~Add distro "rolling"

~~[[File:zero2w-img265~~updated cache in /home/orangepi/.ros/rosdep/sources.~~png]]~~cache|}</~~div~~ol>

<li>Then ~~select~~ open a command line terminal window on the '''~~Always trust this host~~desktop''' , and ~~click~~ then use the '''OKtest_ros.sh'''script to start a small turtle routine to test whether ROS can be used normally.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''test_ros.sh'''|}</li><li>After running the '''test_ros.sh''' script, a small turtle as shown in the picture below will pop up.[[File:zero2w-img248.png]]</li><li>Then please keep the terminal window you just opened at the top</olli>

[[File:zero2w-~~img266~~img249.png]] </div></ol><ol start="9" style="list-style-type: decimal;"><li>At this time, press the direction keys on the keyboard to control the little turtle to move up, down, left, and right.[[File:zero2w-img250.png]]</li></ol> === How to install ROS 2 Galactic on Ubuntu20.04 ===

<ol style="list-style-type: decimal;"><li>The currently active version of ROS 2 is as follows, the recommended version is '''Galactic Geochelone'''[[File:zero2w-img251.png]]</~~div~~p><~~ol start~~p>[[File:zero2w-img252.png]]{| class="7wikitable" style="~~list~~width:800px;" |-| [http://docs.ros.org/ '''http://docs.ros.org''']'''http://docs.ros.org/en/galactic/Releases.html'''|}</li><li>The link to the official installation documentation of ROS 2 '''Galactic Geochelone''' is as follows:{| class="wikitable" style~~-type~~="width: ~~decimal~~800px;"|-| '''docs.ros.org/en/galactic/Installation.html''''''http://docs.ros.org/en/galactic/Installation/Ubuntu-Install-Debians.html'''|}</li>~~After~~ <li>In the ~~connection is successful~~official installation documentation of ROS 2 '''Galactic Geochelone''', Ubuntu Linux recommends using Ubuntu20.04, ~~you can see~~ so please ensure that the ~~directory structure of~~ system used by the development boardis the '~~s Linux file~~ ''Ubuntu20.04 desktop system on '''. There are several ways to install ROS 2. The following demonstrates how to install ROS 2 '''Galactic Geochelone''' through '''Debian packages'''.</li><li>Use the '''install_ros.sh''' script to install ros2{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_ros.sh ros2'''|}</li><li>The '''install_ros.sh''' script will automatically run the '''ros2 -h''' command after installing ros2. If you can see the ~~right side of~~ following print, it means that the ~~filezilla software~~ros2 installation is complete.</lip>{| class="wikitable" style="width:800px;" |-| usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...</olp>

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

~~[[File:zero2w~~ros2 is an extensible command-~~img267~~line tool for ROS 2.~~png]]~~

~~</div>~~

~~<ol start="8" style="list-style-type: decimal;">~~

<li>Then select the path to be uploaded to the development board on the right side of the filezilla software, select the file to be uploaded on the Windows PC on the left side of the filezilla software, right-click the mouse, and then click the upload option to start uploading the file to the development board.</li></ol>

<~~div class="figure"~~p>optional arguments::-h, --help show this help message and exit

~~[[File:zero2w-img268.png]]~~

Commands::action Various action related sub-commands:bag Various rosbag related sub-commands</~~div~~p>:<~~ol start="9" style="list~~p>component Various component related sub-~~style~~commands:daemon Various daemon related sub-~~type~~commands: ~~decimal;"~~doctor Check ROS setup and other potential issues:<lip>interface Show information about ROS interfaces:~~After the upload is completed, you can go to the corresponding path in the development board Linux system to view the uploaded~~ launch Run a launch file.:lifecycle Various lifecycle related sub-commands</lip>:<lip>multicast Various multicast related sub-commands~~The method of uploading~~ :node Various node related sub-commands:param Various param related sub-commands:pkg Various package related sub-commands:run Run a ~~folder is the same as the method of uploading a file, so I won't go into details here.~~package specific executable:security Various security related sub-commands:service Various service related sub-commands:topic Various topic related sub-commands</lip>:wtf Use `wtf` as alias to `doctor`</olp>

~~~~

~~== Instructions for using the logo on and off the machine ==~~

~~<ol style="list-style-type~~: ~~decimal;"><li>~~~~The power on/off logo will only be displayed on the desktop version of the system by default~~Call `ros2 <command> -h` for more detailed usage.|}</li><li>~~Set~~ Then you can use the '''~~bootlogo~~test_ros.sh''' ~~variable~~ script to ~~'''false''' in '''/boot/orangepiEnv~~test whether ROS 2 is installed successfully.~~txt''' to turn off~~ If you can see the ~~switch logo~~following print, it means ROS 2 can run normally.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~sudo vim~~ test_ros.sh'''</~~boot/orangepiEnv~~p>[INFO] [1671174101.~~txt'~~200091527] [talker]: Publishing: 'Hello World: 1'~~verbosity=~~[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: 1][INFO] [1671174102.199572327] [talker]: Publishing: 'Hello World: 2'[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2][INFO] [1671174103.199580322] [talker]: Publishing: '~~bootlogo=false''~~Hello World: 3'[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]|}</li><li>~~Set~~ Run the ~~'''bootlogo''' variable~~ following command to ~~'''true''' in '''/boot/orangepiEnv.txt''' to enable the power on/off logo.~~open rviz2{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~sudo vim~~ source /opt/ros/~~boot~~galactic/~~orangepiEnv~~setup.~~txt~~bash'''~~verbosity=1~~orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''|}~~'''bootlogo=true'''~~[[File:zero2w-img253.png]]</li><li>~~The location~~ For how to use ROS, please refer to the documentation of ~~the boot logo picture in the Linux system is~~ROS 2.{| class="wikitable" style="width:800px;" |-| [http://docs.ros.org/en/galactic/Tutorials.html '''http:/~~usr~~/~~share/plymouth~~docs.ros.org/~~themes~~en/~~orangepi~~galactic/~~watermark~~Tutorials.~~png~~html''']|}</li></ol> === How to install ROS 2 Humble on Ubuntu22.04 === <ol style="list-style-type: decimal;"><li>~~After replacing~~ Use the ~~boot logo image, you need~~ install_ros.sh script to ~~run the following command to take effect~~'''install_ros.sh'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~sudo update-initramfs -u~~install_ros.sh ros2'''|}</li><li>The '''install_ros.sh''' script will automatically run the '''ros2 -h''' command after installing ros2. If you can see the following print, it means that the ros2 installation is complete.{| class="wikitable" style="width:800px;" |-| usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...</olp>

~~~~

~~== How to turn on the power button in Linux5.4 ==~~

~~There~~ ros2 is ~~no power on/off button on the main board of the development board~~an extensible command-line tool for ROS 2. ~~We can expand it through a 24pin expansion board. The location of the power on~~</~~off button on the expansion board is as follows:~~p>

~~[[File:zero2w-img269.png]]~~

~~The power on~~optional arguments:</~~off button of the Linux 6.1 image is turned on by default~~p>:-h, ~~but the power on~~--help show this help message and exit</~~off button of the Linux 5.4 kernel image is turned off by default and needs to be turned on manually for normal use. The steps are as follows:~~p>

~~<ol style="list-style-type: decimal;">~~

~~<li>First run '''orangepi-config'''. Ordinary users remember to add '''sudo''' permissions.~~

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

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

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

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

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

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

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

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

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

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

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

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

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

<~~span id="how~~p>Commands::action Various action related sub-tocommands:bag Various rosbag related sub-~~shut~~commands:component Various component related sub-~~down~~commands:daemon Various daemon related sub-commands:doctor Check ROS setup andother potential issues:interface Show information about ROS interfaces:launch Run a launch file:lifecycle Various lifecycle related sub-~~restart~~commands:multicast Various multicast related sub-~~the~~commands:node Various node related sub-~~development~~commands:param Various param related sub-~~board"~~commands:pkg Various package related sub-commands</~~span~~p>~~== How~~ :run Run a package specific executable:security Various security related sub-commands:service Various service related sub-commands:topic Various topic related sub-commands:wtf Use `wtf` as alias to ~~shut down and restart the development board ==~~`doctor`

~~<ol style="list-style-type: decimal;">~~

<li>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 '''poweroff''' command to shut down the Linux system of the development board before powering off, and then unplug the power supply.

~~orangepi@orangepi:~$ '''sudo poweroff'''~~

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

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

~~[[File:zero2w-img269.png]]~~

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

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

~~orangepi@orangepi:~$ '''sudo''' '''reboot'''</li></ol>~~

:<~~span id~~p>Call `ros2 <command> -h` for more detailed usage.|}</li><li>Then you can use the '''test_ros.sh''' script to test whether ROS 2 is successfully installed. If you can see the following print, it means ROS 2 can run normally.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''test_ros.sh'''[INFO] [1671174101.200091527] [talker]: Publishing: 'Hello World: 1'[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: 1][INFO] [1671174102.199572327] [talker]: Publishing: 'Hello World: 2'[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2][INFO] [1671174103.199580322] [talker]: Publishing: 'Hello World: 3'[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]|}</li><li>Run the following command to open rviz2{| class="wikitable" style="~~linux~~width:800px;" |-~~sdkorangepi~~| orangepi@orangepi:~$ '''source /opt/ros/humble/setup.bash'''orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''[[File:zero2w-~~build~~img254.png]]|}</li><li>Reference documentation{| class="wikitable" style="width:800px;" |-| '''http://docs.ros.org/en/humble/index.html'''[http://docs.ros.org/en/galactic/Tutorials.html '''http://docs.ros.org/en/humble/Installation/Ubuntu-~~usage~~Install-~~instructions"~~Debians.html''']|}</li></~~span~~ol>

~~~~=~~= Compilation system requirements~~ How to install kernel header files ==

~~The Linux SDK, '''orangepi~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-~~build~~| <big>'''~~, only supports running on X64 computers~~ Debian11 system with ~~'''Ubuntu 22~~Linux6.~~04''' installed~~1 kernel will report GCC error when compiling kernel module. ~~Therefore, before downloading orangepi-build~~So if you want to compile the kernel module, please ~~first ensure that the Ubuntu version installed on your computer is Ubuntu 22~~use Debian12 or Ubuntu22.04. ~~The command to check the Ubuntu version installed on the computer is as follows. If the Release field does not display '''22.04~~'''~~, it means that the Ubuntu version currently used does not meet the requirements. Please change the system before performing the following operations.~~</big>|}

~~test~~<ol style="list-style-type: decimal;"><li>The Linux image released by OPi comes with the deb package of the kernel header file by default, and the storage location is '''/opt/'''{| class="wikitable" style="width:800px;" |-| orangepi@~~test~~orangepi:~$ '''~~lsb_release~~ ls /opt/linux-headers*'''/opt/linux-headers-xxx-sun50iw9_x.x.x_arm64.deb|}</li><li>Use the following command to install the deb package of the kernel header file{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg -i /opt/linux-headers*.deb'''|}</li><li>After installation, you can see the folder where the kernel header file is located under '''/usr/src'''.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ls /usr/src'''linux-headers-x.x.x|}</li><li>Then you can compile the source code of the hello kernel module that comes with the Linux image. The source code of the hello module is in '''/usr/src/hello'''. After entering this directory, then use the make command to compile.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''cd /usr/src/hello/'''orangepi@orangepi:/usr/src/hello$ '''sudo make'''make -C /lib/modules/5.4.125/build M=/usr/src/hello modulesmake[1]: Entering directory '/usr/src/linux-headers-5.4.125':CC [M] /usr/src/hello/hello.o:Building modules, stage 2.:MODPOST 1 modules:CC [M] /usr/src/hello/hello.mod.o:LD [M] /usr/src/hello/hello.komake[1]: Leaving directory '/usr/src/linux-headers-5.4.125'|}</li><li>After compilation, the '''hello.ko''' kernel module will be generated{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:/usr/src/hello$ '''ls *.ko'''hello.ko|}</li><li>Use the '''insmod''' command to insert the '''hello.ko''' kernel module into the kernel{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:/usr/src/hello$ '''sudo insmod hello.ko'''|}</li><li>Then use the '''demsg''' command to view the output of the '''hello.ko''' kernel module. If you can see the following output, it means that the '''hello.ko''' kernel module is loaded correctly.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:/usr/src/hello$ '''dmesg | grep "Hello"'''[ 2871.893988] '''Hello Orange Pi -- init'''|}</li><li>Use the '''rmmod''' command to uninstall the '''hello.ko''' kernel module{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:/usr/src/hello$ '''sudo rmmod hello'''orangepi@orangepi:/usr/src/hello$ '''dmesg | grep "Hello"'''[ 2871.893988] Hello Orange Pi -- init[ 3173.800892] '''Hello Orange Pi --aexit'''|}</li></ol>

~~No LSB modules are available.~~

~~Distributor ID: Ubuntu~~== Testing of some programming languages supported by Linux system ==

~~Description: Ubuntu 22.04 LTS~~=== Debian Bullseye system ===

~~Release~~<ol style="list-style-type: decimal;"><li>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.<ol style="list-style-type: lower-alpha;"><li>The version of a.gcc is as follows{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc --version'''gcc (Debian 10.2.1-6) 10.2.1 20210110Copyright (C) 2020 Free Software Foundation, Inc.This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</li><li>Write the '''hello_world.c'''program in C language{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '22''vim hello_world.04c'''#include <stdio.h>

~~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'''VirtualBox''' or '''VMware''' to install an Ubuntu 22.04 virtual machine in the Windows system. But please note, do not compile orangepi-build on the WSL virtual machine, because orangepi-build has not been tested in the WSL virtual machine, so 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 isint main(void){:printf("Hello World!\n");

~~[https://repo.huaweicloud.com/ubuntu-releases/21.04/ubuntu-21.04-desktop-amd64.iso '''https://mirrors.tuna.tsinghua.edu.cn/ubuntu-releases/22.04/ubuntu-22.04-desktop-amd64.iso''']~~

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:

:return 0;

}

|}

</li>

<li>Then compile and run '''hello_world.c'''

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

|-

|

orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''

orangepi@orangepi:~$ '''./hello_world'''

Hello World!

|}

</li></ol>

</li>

<li>Debian Bullseye has Python3 installed by default

<li>~~For the method of replacing Tsinghua Source, please refer to the instructions on this page.~~<~~/li~~p>~~</ol>~~ ~~[https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/ '''https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/''']~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>Note that the Ubuntu~~ The specific version ~~needs to be switched to 22.04.</li></ol>~~ ~~[[File:zero2w-img271.png]]~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li>The contents~~ of ~~the '''/etc/apt/sources.list''' file that need to be replaced are:</li></ol>~~ ~~test@test:~$ '''sudo mv /etc/apt/sources.list cat /etc/apt/sources.list.bak'''~~ ~~test@test:~$ '''sudo vim /etc/apt/sources.list'''~~ ~~# The source code image~~ Python is ~~commented by default to improve apt update speed. You can uncomment it yourself if necessary.~~ ~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse~~ ~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse~~ ~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse~~ ~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse~~ ~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse~~ ~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse~~ ~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-security main restricted universe multiverse~~ ~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-security main restricted universe multiverse~~ ~~# Pre-release software source, not recommended to 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 multiverse~~ ~~<ol 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.~~as follows</~~li></ol~~p> ~~test@test:~$ '''sudo apt-get update'''~~ ~~<ol start~~{| class="5wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;"><li>'''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.'''</li></ol> ~~== Obtain the source code of linux sdk ==~~ ~~=== 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://github.com/orangepi-xunlong/orangepi-build.git -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.''' ~~<div class="figure">~~ ~~[[File:zero2w-img272.png]]~~ ~~</div>~~'''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). 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 account.''' ~~The u-boot and linux kernel versions currently used by the H618 series development boards are as follows:~~ ~~{| class="wikitable~~"

|-

| orangepi@orangepi:~$ '''~~branch~~python3'''| '''~~u-boot Version~~Python 3.9.2'''(default, Feb 28 2021, 17:03:44)[GCC 10.2.1 20210110] on linuxType "help", "copyright", "credits" or "license" for more information.>>>|}{| ~~'''linux Kernel version'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

| <big>'''~~current~~Use the Ctrl+D shortcut key to exit python's interactive mode.'''</big>| }</li><li>Write the '''~~u-boot v2018~~hello_world.05py'''program in Python language{| ~~'''linux5.4'''~~class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~next~~vim hello_world.py'''print('Hello World!')| }</li><li>The result of running '''hello_world.py'u'' is as follows{| class="wikitable" style="width:800px;" |-~~boot v2021~~| orangepi@orangepi:~$ '''python3 hello_world.07py'''Hello World!| }</li></ol></li><li>Debian Bullseye does not install Java compilation tools and operating environment by default.<ol style="list-style-type: lower-alpha;"><li>You can use the following command to install openjdk. The latest version in Debian Bullseye is openjdk-17{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~linux6~~sudo apt install -y openjdk-17-jdk'''|}</li><li>After installation, you can check the Java version.1{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''java --version'''|}</li><li>Write the Java version of '''hello_world.java'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''public class hello_world{:public static void main(String[] args):{::System.out.println("Hello World!");:}}|}</li><li>Then compile and run '''hello_world.java'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''javac hello_world.java'''orangepi@orangepi:~$ '''java hello_world'''Hello World!

|}

</li></ol>

~~'''The branch mentioned here is not the same thing as the branch of orangepi~~

~~'''We define the linux5.4 bsp kernel currently provided by Allwinner as the current branch. The latest linux6.1 LTS kernel is defined as the next branch.'''~~ ~~After downloading, the following files and folders will be included:~~=== Debian Bookworm system ===

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

<li>~~'''build~~The version of a.~~sh''': Compile startup script~~gcc is as follows~~</li><li>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~external~~gcc --version'''~~: Contains configuration files needed to compile the image, specific scripts, and source code of some programs, etc.~~gcc (Debian 12.2.0-14) 12.2.0</lip><lip>Copyright (C) 2022 Free Software Foundation, Inc.~~'''LICENSE''': GPL 2 license file~~This is free software; see the source for copying conditions. There is NO</lip>~~<li>~~~~'''README~~warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.~~md''': orangepi-build documentation~~|}</li><li>Write the '''~~scripts~~hello_world.c'''~~: Common script for compiling linux images~~program in C language{| class="wikitable" style="width:800px;" |-| <~~/li~~p>~~</ol>~~ ~~test~~orangepi@~~test~~orangepi:~~~/orangepi-build~~$ '''lsvim hello_world.c'''#include <stdio.h>

~~'''build.sh external LICENSE README.md scripts'''~~

'''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 kernel. chain, this is normal, because these things are stored in other separate github repositories or some servers int main(~~their addresses will be detailed below~~void). 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 places.'''{:printf("Hello World!\n");

~~~~

~~=== Download the cross-compilation tool chain ===~~

When orangepi-build is run for the first time, it will automatically download the cross-compilation '''toolchain''' and put it in the '''toolchains''' folder. Every time you run orangepi-build's build.sh script, it will check whether the cross-compilation toolchain in toolchains exists. If If it does not exist, the download will be restarted. If it exists, it will be used directly without repeated downloading.

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

~~[[File:zero2w-img273.png]]~~

~~</div>~~

~~The mirror URL of the cross-compilation tool chain in China is the open source software mirror site of Tsinghua University:~~

~~[https://mirrors.tuna.tsinghua.edu.cn/armbian-releases/_toolchain/ '''https://mirrors.tuna.tsinghua.edu.cn/armbian-releases/_toolchain/''']~~

~~After toolchains is downloaded, it will contain multiple versions of cross-compilation t'''toolchain''':~~

~~test@test:~/orangepi-build$ '''ls toolchains/'''~~

~~gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu gcc-linaro-4.9.4-2017.01-x86_64_aarch64-linux-gnu gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabi~~

~~gcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihf gcc-linaro-4.9.4-2017.01-x86_64_arm-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:~~

:return 0;

}

|}

</li>

<li>Then compile and run '''hello_world.c'''

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

|-

|

orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''

orangepi@orangepi:~$ '''./hello_world'''

Hello World!

|}

</li></ol>

</li>

<li>Debian Bookworm has Python3 installed by default

<li>~~linux5.4~~<~~/li~~p>The specific version of Python is as follows</olp> ~~'''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''~~ ~~<ol start~~{| class="2wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">|-| <lip>~~linux6.1~~orangepi@orangepi:~$ '''python3'''</lip><~~/ol~~p> ~~'''gcc-arm-~~Python 3.11.2~~-2022~~(main, Mar 13 2023, 12:18:29) [GCC 12.2.~~02-x86_64-aarch64-none-~~0] on linux~~-gnu'''~~ ~~The cross-compilation tool chain used to compile the H618 u-boot source code is:~~ <~~ol style="list-style-type: lower-alpha;"~~/p><lip>~~v2018~~Type "help", "copyright", "credits" or "license" for more information.05</lip>>>></olp>|}~~'''gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabi'''~~ ~~<ol start~~{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;"|-| <big><lip>~~v2021~~'''Use the Ctrl+D shortcut key to exit python's interactive mode.07'''</lip></olbig>|}</li><li>Write the '''~~gcc-arm-11.2-2022~~hello_world.~~02-x86_64-aarch64-none-linux-gnu~~py''' ~~~~program in Python language</~~span~~p>{| class=~~== orangepi-build complete directory structure description ===~~ ~~<ol~~ "wikitable" style="~~list-style-type~~width: ~~decimal~~800px;"|-| orangepi@orangepi:~$ '''vim hello_world.py'''<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.print('Hello World!')|}<~~ol style="list-style-type: lower-alpha;"~~/li><li>The ~~git warehouse where the linux kernel source code is stored~~ result of running '''hello_world.py''' is as follows~~. Please note that the branch of the linux-orangepi warehouse is switched to~~~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">|-| <lip>~~Linux5~~orangepi@orangepi:~$ '''python3 hello_world.4py'''</lip>Hello World!</olp>|}

</li></ol>

</li~~></ol>~~ ~~https://github.com/orangepi-xunlong/linux-orangepi/tree/'''orange-pi-5.4-sun50iw9'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>Linux6.1</li></ol>~~ ~~https://github.com/orangepi-xunlong/linux-orangepi/tree/'''orange-pi-6.1-sun50iw9'''~~ ~~<ol start="2" style="list-style-type: lower-alpha;"~~><li>~~The git warehouse where the u-boot source code is stored is as follows~~Debian Bookworm does not install Java compilation tools and operating environment by default. ~~Please note that the branch of the u-boot-orangepi warehouse is switched to~~

<li>~~v2018~~You can use the following command to install openjdk.05The latest version in Debian Bookworm is openjdk-17{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''|}</li><li>After installation, you can check the Java version.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''java --version'''|}</li><li>Write the Java version of '''hello_world.java'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''public class hello_world{:public static void main(String[] args):{::System.out.println("Hello World!");:}}|}</li><li>Then compile and run '''hello_world.java'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''javac hello_world.java'''orangepi@orangepi:~$ '''java hello_world'''Hello World!|}</li></ol></li></ol>

~~https://github.com/orangepi~~</~~tree/'''v2018.05-h618'''~~span>

~~<ol start~~=~~"2" style~~=~~"list-style-type: lower-alpha;"><li>v2021.07</li></ol>~~= Ubuntu Focal system ===

~~https://github.com/orangepi-xunlong/u-boot-orangepi/tree/'''v2021.07-sunxi'''~~ <ol ~~start="2"~~ style="list-style-type: decimal;"><li>~~When orangepi-build~~ Ubuntu Focal is ~~run for~~ installed with the ~~first time, it will download the cross-~~gcc compilation tool chainby default, ~~u-boot and linux kernel source code. After successfully compiling a linux image, the files and folders that~~ which can ~~be seen~~ directly compile C language programs in ~~orangepi-build are:~~the Linux system of the development board.

<li>~~'''build.sh''': Compile startup script</li><li>'''external''': Contains the configuration files needed to compile the image, scripts for specific functions, and the source code~~ The version of ~~some programs~~a. ~~The rootfs compressed package cached during the image compilation process~~ gcc is ~~also stored in external.~~as follows</p~~></li~~>~~<li>'''kernel'''~~{| class="wikitable" style="width: ~~Store the source code of the linux kernel</li>~~800px;" |-| ~~<li>~~orangepi@orangepi:~$ '''~~LICENSE~~gcc --version'''~~: GPL 2 license file~~</p~~></li~~>~~<li>~~~~'''README~~gcc (Ubuntu 9.4.~~md''': orangepi~~0-~~build documentation~~1ubuntu1~20.04.1) 9.4.0</p~~></li~~>~~<li>~~~~'''output''': Store compiled u-boot~~Copyright (C) 2019 Free Software Foundation, ~~linux and other deb packages, compilation logs, and compiled images and other files~~Inc.</p~~></li~~>~~<li>~~~~'''scripts''': Common script~~ This is free software; see the source for ~~compiling linux images~~copying conditions. There is NO</p~~></li~~>~~<li>~~~~'''toolchains''': Store cross-compilation tool chain~~warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</li><li>Write the '''~~u-boot~~hello_world.c'''~~: Store the source code of u-boot~~program in C language~~</li><li>~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~userpatches~~vim hello_world.c'''~~: Store the configuration files needed to compile the script~~</p~~></li></ol~~><~~/li~~p>#include <stdio.h></olp>

~~test@test:~/orangepi-build$ '''ls'''~~

~~'''build.sh external kernel LICENSE output README.md scripts toolchains u-boot userpatches'''~~int main(void){:printf("Hello World!\n");

~~~~

~~== Compile u-boot ==~~

~~# Run the build.sh script, remember to add sudo permissions~~ ~~test@test~~:~~~/orangepi-build$ '''sudo ./build.sh'''~~ <~~ol start="2" style="list-style-type: decimal~~p>return 0;"<lip>~~Select '''U-boot package''' and press Enter~~}</~~li></ol>~~ ~~<div class="figure"~~p> ~~[[File:zero2w-img274.png]]~~|}</~~div~~li><~~ol start="3" style="list-style-type: decimal;"~~li><lip>Then ~~select the model of the development board~~compile and run '''hello_world.c'''</~~li></ol~~p> ~~[[File:zero2w-img275.png]]~~ ~~<ol start~~{| class="4wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then select the branch type of u~~|-~~boot<ol style="list-style-type: lower-alpha;">~~| ~~<li>~~~~The current branch will compile the u~~orangepi@orangepi:~$ '''gcc -~~boot v2018.05 version code that needs to be used by the linux5.4 image~~o hello_world hello_world.c'''</p~~></li~~>~~<li>~~~~The next branch will compile the u-boot v2021.07 version code that needs to be used by the linux6.1 image~~orangepi@orangepi:~$ '''./hello_world'''~~[[File:zero2w-img276.png]]~~Hello World!|}</li></ol>

</li>

<li>~~If you select the next branch, you will also be prompted to select the memory size, and you do not need to select the current branch.</li></ol>~~ ~~<blockquote>a. If the development board you purchased~~ Ubuntu Focal has ~~a memory size of 1.5GB, please select the first option.~~ ~~b. If the development board you purchased has 1GB or 2GB or 4GB memory size, please choose the second option.</blockquote>[[File:zero2w-img277.png]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Then it will start to compile u-boot. Some of the information prompted when compiling the next branch is as follows:~~Python3 installed by default

<li>~~Version~~ The specific version of uPython3 is as follows{| class="wikitable" style="width:800px;" |-~~boot source code~~| orangepi@orangepi:~$ '''python3'''</lip>Python 3.8.10 (default, Nov 14 2022, 12:59:47)[GCC 9.4.0] on linux</olp>Type "help", "copyright", "credits" or "license" for more information.</lip>>>></olp>|}~~[ o~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Use the Ctrl+D shortcut key to exit python's interactive mode.k'''</big>|}</li><li>Write the '''hello_world. ~~] Compiling u~~py''' program in Python language{| class="wikitable" style="width:800px;" |-~~boot [~~ | orangepi@orangepi:~$ '''~~v2021~~vim hello_world.07py''' ]print('Hello World!')|}<~~ol start~~/li><li>The result of running '''hello_world.py''' is as follows{| class="2wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3 hello_world.py'''Hello World!|}</li></ol></li><li>Ubuntu Focal does not have Java compilation tools and running environment installed by default.<ol style="list-style-type: lower-alpha;"><li>~~Version of~~ You can use the ~~cross~~following command to install openjdk-~~compilation tool chain~~17{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''|}</li><li>After installation, you can check the Java version.</olp>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''java --version'''openjdk 17.0.2 2022-01-18OpenJDK Runtime Environment (build 17.0.2+8-Ubuntu-120.04)~~[ o~~OpenJDK 64-Bit Server VM (build 17.k0. ~~] Compiler~~ 2+8-Ubuntu-120.04, mixed mode, sharing)|}</li><li>Write the Java version of '''hello_world.java'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''public class hello_world{:public static void main(String[ ] args):{::System.out.println("Hello World!");:}}|}</li><li>Then compile and run '''hello_world.java'''~~aarch64~~{| class="wikitable" style="width:800px;" |-~~linux-gnu-gcc 11~~| orangepi@orangepi:~$ '''javac hello_world.java'''orangepi@orangepi:~$ '''java hello_world''' ]Hello World!|}</li></ol></li></ol>

<~~ol start~~span id="~~3" style="list~~ubuntu-~~style~~jammy-~~type: lower-alpha;~~system">~~<li>Path to the compiled u-boot deb package</li~~></olspan>

~~[ o.k. ] Target directory [ '''orangepi-build/output/debs/u-boot''' ]~~=== Ubuntu Jammy system ===

<ol ~~start="4" style="list-style-type: lower-alpha;"><li>The package name of the compiled u-boot deb package</li></ol>~~ ~~[ o.k. ] File name [ '''linux-u-boot-next-orangepizero2w_x.x.x_arm64.deb''' ]~~ ~~<ol start="5" style="list-style-type: lower-alpha;"><li>Compilation time</li></ol>~~ ~~[ o.k. ] Runtime [ '''1 min''' ]~~ ~~<ol start="6" style="list-style-type: lower-alpha;"><li>Repeat the command to compile u-boot. Use the following command without selecting through the graphical interface. You can start compiling u-boot directly.</li></ol>~~ ~~[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepizero2w BRANCH=next BUILD_OPT=u-boot''' ]~~ ~~<ol start="7"~~ style="list-style-type: decimal;"><li>~~View the compiled u-boot deb package~~<~~/li~~p>~~</ol>~~ ~~test@test:~/orangepi-build$ '''ls output/debs/u-boot/'''~~ ~~'''linux-u-boot-next-orangepizero2w_x.x.x_arm64.deb'''~~ ~~<ol start="8" style="list-style-type: decimal;"><li>When~~ Ubuntu Jammy is installed with the ~~orangepi-bulid~~ gcc compilation ~~system compiles the u-boot source code~~tool chain by default, 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. ('''You need to completely which can directly compile ~~u-boot before you can turn off this function, otherwise it will prompt that~~ C language programs in the ~~source code~~ Linux system of ~~u-boot cannot be found'''), otherwise~~ the ~~modifications will be restored~~development board. ~~The method is as follows:</li></ol>~~ ~~<blockquote>Set the IGNORE_UPDATES variable in u'''userpatches/config-default.conf''' to "yes"</blockquote>test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''~~ ~~......~~ ~~IGNORE_UPDATES="'''yes'''"~~ ~~......~~ ~~<ol start="9" style="list-style-type: decimal;"><li>When debugging u-boot code, you can use the following method to update u-boot in the linux image for testing~~

<li>~~First upload the compiled deb package~~ The version of ua.gcc is as follows{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gcc --version'''gcc (Ubuntu 11.3.0-~~boot to~~ 1ubuntu1~22.04.1) '''11.3.0'''Copyright (C) 2021 Free Software Foundation, Inc.This is free software; see the ~~Linux system of the development board~~source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</li><li>Write the '''hello_world.c''' program in C language</olp>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.c'''</lip>#include <stdio.h></olp>

~~test@test:~/orangepi-build$ '''cd output/debs/u-boot'''~~

~~test@test:~~~int main(void)</~~orangepi_build~~p>{</~~output~~p>:printf("Hello World!\n");</~~debs/u-boot$ '''scp \'''~~p>

~~'''linux-u-boot-next-orangepizero2w_x.x.x_arm64.deb [mailto:root@192.168.1.xxx:/root root@192.168.1.xxx:/root]'''~~

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

~~<li>Install the new u-boot deb package just uploaded</li></ol>~~

~~orangepi@orangepi:~$ '''sudo dpkg -i''' '''linux-u-boot-next-orangepizero2w_x.x.x_arm64.deb'''~~

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

~~<li>Then run the nand-sata-install script</li></ol>~~

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

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

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

~~[[File:zero2w-img278.png]]~~

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

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

~~[[File:zero2w-img279.png]]~~

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

~~[[File:zero2w-img280.png]]~~

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

~~~~

~~== Compile the linux kernel ==~~

~~# Run the '''build.sh''' script, remember to add sudo permissions~~

~~test@test:~/orangepi-build$ '''sudo ./build.sh'''~~

~~<ol start="2" style="list-style-type: decimal;">~~

~~<li>Select '''Kernel package''' and press Enter</li></ol>~~

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

~~[[File:zero2w-img281.png]]~~

~~</div>~~

~~<ol start="3" style="list-style-type: decimal;">~~

<li>Then you will be prompted whether you need to display the kernel configuration interface. If you do not need to modify the kernel configuration, select the first one. If you need to modify the kernel configuration, select the second one.</li></ol>

~~[[File:zero2w-img282.png]]~~

~~<ol start="4" style="list-style-type: decimal;">~~

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

~~[[File:zero2w-img275.png]]~~

~~<ol start="5" style="list-style-type: decimal;">~~

~~<li>Then select the branch type of the kernel source code</li></ol>~~

~~<blockquote>a. The current branch will compile the linux5.4 kernel source code~~

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

~~</blockquote>~~

~~[[File:zero2w-img276.png]]~~

~~<ol start="6" style="list-style-type: decimal;">~~

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

~~[[File:zero2w-img283.png]]~~

:return 0;

}

|}

</li>

<li>Then compile and run '''hello_world.c'''

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

|-

|

orangepi@orangepi:~$ '''gcc -o hello_world hello_world.c'''

orangepi@orangepi:~$ '''./hello_world'''

Hello World!

|}

</li></ol>

</li>

<li>Ubuntu Jammy has Python3 installed by default

<li>~~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.~~<~~/li~~p>The specific version of Python3 is as follows</olp>{| class="wikitable" style="width:800px;" |-~~test~~| orangepi@~~test~~orangepi:~~~/orangepi-build~~$ '''~~sudo ./build.sh KERNEL_CONFIGURE=no~~python3'''Python 3.10.6 (main, May 29 2023, 11:10:38) [GCC 11.3.0] on linuxType "help", "copyright", "credits" or "license" for more information.<~~ol start~~p>>>>|}{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~b. You can also set~~ '''~~KERNEL_CONFIGURE=no~~Use the Ctrl+D shortcut key to exit python's interactive mode.''' ~~in the orangepi-build~~</~~userpatches/config-default.confconfiguration file to permanently disable this function.~~p></pbig>|}</li><li>If Write 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~~'''hello_world. ~~Please increase the Ubuntu PC terminal to the maximum size, and then rerun the build.sh script~~py''' program in Python language{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.py'''print('Hello World!')</lip>|}</olli> ~~[[File:zero2w-img284~~<li>The result of running '''hello_world.~~png]]~~py''' is as follows ~~<ol start~~{| class="7wikitable" style="~~list-style-type~~width: ~~decimal~~800px;"|-| orangepi@orangepi:~$ '''python3 hello_world.py'''Hello World!|}</li></ol></li><li>~~Part of the information prompted when compiling the next branch kernel source code is explained as follows:~~Ubuntu Jammy does not install Java compilation tools and operating environment by default.

<li>~~Version of~~ You can use the ~~linux kernel source code~~following command to install openjdk-18</lip>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-18-jdk'''</olp>|}</li><li>After installation, you can check the Java version.</olp>{| class="wikitable" style="width:800px;" |-~~[ o.k. ] Compiling current kernel [~~ | orangepi@orangepi:~$ '''~~6.1.31~~java --version''' ]openjdk 18.0.2-ea 2022-07-19<~~ol start="~~p>OpenJDK Runtime Environment (build 18.0.2~~" style="list~~-~~style~~ea+9-~~type: lower~~Ubuntu-~~alpha;"~~222.04)<lip>~~The version of the cross~~OpenJDK 64-Bit Server VM (build 18.0.2-ea+9-Ubuntu-~~compilation tool chain used~~222.04, mixed mode, sharing)</lip>|}</olli> ~~[ o.k. ] Compiler~~ <li>Write the Java version [ of '''~~aarch64-linux-gnu-gcc 11~~hello_world.java''' ] ~~<ol start~~{| class="3wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;"|-| orangepi@orangepi:~$ '''vim hello_world.java'''public class hello_world<lip>~~The default configuration file used by the kernel and the path where it is stored are as follows~~{</lip>:public static void main(String[] args)</olp>:{~~[ o~~::System.kout. ~~] Using kernel config file [ '''orangepi-build~~println("Hello World!");</~~external~~p>:}</~~config~~p>}</~~kernel~~p>|}</~~linux-6.1-sun50iw9-next~~li><li>Then compile and run '''hello_world.~~config~~java''' ]~~<ol start~~{| class="4wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;"|-| orangepi@orangepi:~$ '''javac hello_world.java'''orangepi@orangepi:~$ '''java hello_world'''<lip>Hello World!~~The path to the kernel-related deb package generated by compilation~~|}</li></ol> ~~[ o.k. ] Target directory [ '''output~~</~~debs~~li></~~''' ]~~ol>

<~~ol start~~span id="~~5" style="list~~method-of-uploading-files-to-the-development-~~style~~board-~~type: lower~~linux-~~alpha;~~system">~~<li>The package name of the kernel image deb package generated by compilation</li~~></olspan>

~~[ o.k. ] File name [ '''linux-image-next-sun50iw9_x.x.x_arm64.deb''' ]~~== Method of uploading files to the development board Linux system ==

<~~ol start~~span id="~~6" style="list~~method-to-upload-files-to-the-development-board-linux-system-~~style~~in-~~type: lower~~ubuntu-~~alpha;~~pc">~~<li>Compilation time~~</~~li></ol~~span>=== Method to upload files to the development board Linux system in Ubuntu PC ===

~~[ o.k. ] Runtime [ '''10 min''' ]~~==== How to upload files using scp command ====

<ol ~~start="7"~~ style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Finally,~~ Use the ~~compilation~~ scp command to ~~repeatedly compile~~ upload files to the Linux system of the ~~last selected kernel will be displayed~~development board in Ubuntu PC. ~~Use the following~~ The specific command ~~without selecting through the graphical interface, and you can directly start compiling the kernel source code.</li></ol>~~ ~~[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepizero2w BRANCH=next BUILD_OPT=kernel KERNEL_CONFIGURE=no''' ]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>View the kernel-related deb package generated by compilation~~is as follows

<li>'''~~linux-dtb-next-sun50iw9_x.x.x_arm64.deb~~file_path: ''' ~~Contains dtb files used by~~ Needs to be replaced with the path of the ~~kernel~~file to be uploaded</li><li>'''~~linux-headers-next-sun50iw9_x.x.x_arm64.deb~~orangepi: '''This is the user name of the development board' ~~Contains kernel header files~~s Linux system. It can also be replaced with something else, such as root.</li><li>'''~~linux-image-next-sun50iw9_x~~192.x168.~~x_arm64~~xx.~~deb~~xx:''' ~~Contains kernel images and kernel modules~~This is the IP address of the development board. Please modify it according to the actual situation.</li><li>'''/olhome/orangepi:''' The path in the development board Linux system can also be modified to other paths.{| class="wikitable" style="width:800px;" |-| test@test:~$ '''scp file_path orangepi@192.168.xx.xx:/home/orangepi/'''|}

</li></ol>

</li>

<li>If you want to upload a folder, you need to add the -r parameter

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

|-

|

test@test:~$ '''scp -r dir_path orangepi@192.168.xx.xx:/home/orangepi/'''

|}

</li>

<li>There are more usages of scp, please use the following command to view the man manual</li>

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

|-

|

test@test:~$ '''man scp'''

|}

</ol>

~~test@test:~/orangepi-build$ '''ls output/debs/linux-*'''~~ ~~output/debs/linux-dtb-next-sun50iw9_x.x.x_arm64.deb~~ ~~output/debs/linux-headers-next-sun50iw9_x.x.x_arm64.deb~~ ~~output/debs/linux-image-next-sun50iw9_x.x.x_arm64.deb~~==== How to upload files using filezilla ====

<ol ~~start="9"~~ style="list-style-type: decimal;"><li>~~When the orangepi~~First install filezilla in Ubuntu PC{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt install -~~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~~ y filezilla'''|}</li><li>Then use the ~~github server. Therefore, if you want~~ following command to ~~modify the linux kernel source code, you first need to turn off the update function of the source code (~~open filezilla{| class="wikitable" style="width:800px;" |-| test@test:~$ '''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 foundfilezilla''')|}</li><li>The interface after opening filezilla is as shown below. At this time, ~~otherwise~~ the ~~modifications will be restored~~remote site on the right is empty. ~~The method is as follows:~~</lip><~~/ol~~div class="figure">

~~<blockquote>Set the IGNORE_UPDATES variable in '''userpatches/config-default.conf''' to "yes"</blockquote>test@test~~[[File:~~~/orangepi-build$ '''vim userpatches/config~~zero2w-~~default~~img255.~~conf'''~~png]]

~~IGNORE_UPDATES="'''yes'''"~~</div></li><li>The method of connecting the development board is as shown in the figure below</li>

<~~ol start~~div class="10figure" ~~style="list-style-type: decimal;"><li>If the kernel is modified, you can use the following method to update the kernel and kernel module of the development board Linux system<ol style="list-style-type: lower-alpha;"><li>Upload the compiled deb package of the Linux kernel to the Linux system of the development board</li></ol></li></ol~~>

~~test@test~~[[File:~~~/orangepi~~zero2w-~~build$ '''cd output/debs'''~~img256.png]]

~~test@test~~</div></ol><ol start="5" style="list-style-type:~decimal;"><li>Then choose to '''save the password''' and click '''OK'''</~~orangepi~~p>[[File:zero2w-~~build~~img257.png]]</~~output~~p></~~debs$~~ li><li>Then select '''Always trust this host''' and click '''~~scp \~~OK'''</li>

~~'''linux-image-next-sun50iw9_x.x.x_arm64.deb root@192.168.1.xxx:/root'''~~<div class="figure">

~~<ol start="2" style="list-style-type~~[[File: ~~lower~~zero2w-~~alpha;"><li>Install the deb package of the new linux kernel just uploaded~~img258.~~</li></ol>~~png]]

~~orangepi@orangepi~~</div></ol><ol start="7" style="list-style-type:~~~$ '~~decimal;"><li>After the connection is successful, you can see the directory structure of the development board'~~'sudo dpkg -i linux-image-next-sun50iw9_x.x.x_arm64~~s Linux file system on the right side of the filezilla software.~~deb'''~~</li>

<~~ol start~~div class="3figure" ~~style="list-style-type: lower-alpha;"><li>Then restart the development board and check whether the kernel-related modifications have taken effect.</li></ol~~>

~~orangepi@orangepi~~[[File:~~~$ '''sudo''' '''reboot'''~~zero2w-img259.png]]

<~~span id~~/div></ol><ol start="8" style="~~compile~~list-style-~~rootfs~~type: decimal;"><li>Then select the path to be uploaded to the development board on the right side of the filezilla software, select the file to be uploaded in Ubuntu PC on the left side of the filezilla software, right-click the mouse, and then click the upload option to start uploading the file to the development board.</~~span~~li>~~== Compile rootfs ==~~

~~# Run the build.sh script, remember to add sudo permissions~~<div class="figure">

~~test@test~~[[File:~~~/orangepi~~zero2w-~~build$ '''sudo~~ img260.~~/build.sh'''~~png]]

</div></ol><ol start="29" style="list-style-type: decimal;"><li>~~Select~~ After the upload is completed, you can go to the corresponding path in the development board Linux system to view the uploaded file.</li><li>The method of uploading a folder is the same as the method of uploading a file, so I won'~~''Rootfs and all deb packages''' and press Enter~~t go into details here.</li></ol>

<~~div class~~span id="~~figure~~method-to-upload-files-from-windows-pc-to-development-board-linux-system">

~~[[File:zero2w-img285.png]]~~=== Method to upload files from Windows PC to development board Linux system ===

<~~/div><ol start~~span id="~~3" style="list~~how-to-upload-files-using-~~style~~filezilla-~~type: decimal;~~1">~~<li>Then select the model of the development board~~</~~li></ol~~span>==== How to upload files using filezilla ====

~~[[File:zero2w-img275~~# First download the installation file of the Windows version of the filezilla software.~~png]]~~The download link is as follows

~~<ol start~~::{| class="4wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then select the branch type of the kernel source code. Different versions of the kernel source code maintain different rootfs types.~~|-~~<ol style="list-style-type: lower-alpha;">~~| ~~<li>In the current branch, you can see three options~~[https: ~~debian11, ubuntu20.04, and ubuntu22.04.<~~/~~p><~~/~~li><li>In the next branch, you can see three options: debian11, debian12, and ubuntu22~~filezilla-project.04org/download.<php?type=client '''https:/~~p><~~/~~li><~~filezilla-project.org/~~ol>~~download.php?type=client''']~~</li></ol>~~|}

::[[File:zero2w-~~img276~~img261.png]]

<~~ol start~~div class="5figure" ~~style="list-style-type: decimal;"><li>Then select the type of rootfs</li></ol~~>

::[[File:zero2w-~~img286~~img262.png]]

</div><ol start="62" style="list-style-type: decimal;"><li>~~Then select the type of image~~The downloaded installation package is as shown below, then double-click to install it directly~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>~~|-| '''~~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.~~~~</li><li>~~|}During the installation process, please select '''~~Image with desktop environment~~Decline''' ~~Represents an image with a desktop~~on the following installation interface, ~~which is relatively large in size.</li></ol></li></ol>~~and then select '''Next>'''

[[File:zero2w-~~img287~~img263.png]]

</div>

</li></ol><ol start="73" style="list-style-type: decimal;"><li>~~If you are compiling the server version of the image~~The 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 default~~right is empty. ~~Some functions may not be available''')~~</li~~></ol~~>

[[File:zero2w-~~img288~~img264.png]]

</div></ol><ol start="84" 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-img289.png]]~~<div class="figure">

[[File:zero2w-~~img290~~img256.png]]

~~You can then select additional packages that need~~ </div></ol><ol start="5" style="list-style-type: decimal;"><li>Then choose to ~~be installed. Please press~~ '''save the ~~Enter key here to skip directly.~~password''' and click '''OK'''</li>

~~[[File:zero2w-img291.png]]~~<div class="figure">

~~<ol start="9" style="list-style~~[[File:zero2w-~~type: decimal;"><li>Then the compilation of rootfs will start~~img265. ~~Some of the information prompted during compilation are as follows:<ol style="list-style-type: lower-alpha;"><li>Type of rootfs</li></ol></li></ol>~~png]]

~~[ o.k. ] local not found [ Creating new rootfs cache for~~ </div></ol><ol start="6" style="list-style-type: decimal;"><li>Then select '''~~bullseye~~Always trust this host''' ]and click '''OK'''</li>

<~~ol start~~div class="2figure" ~~style="list-style-type: lower-alpha;"><li>The storage path of the compiled rootfs compressed package</li></ol~~>

[ ~~o.k~~[File:zero2w-img266. png] ~~Target directory [ '''orangepi-build/external/cache/rootfs'''~~ ]

</div></ol><ol start="37" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The name~~ After the connection is successful, you can see the directory structure of the ~~rootfs compressed package generated by compilation~~development board's Linux file system on the right side of the filezilla software.</li~~></ol~~>

~~[ o.k. ] File name [ '''bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4''' ]~~<div class="figure">

~~<ol start="10" style="list-style-type: decimal;"><li>View the compiled rootfs compressed package<ol style="list-style-type~~[[File: ~~lower-alpha;"><li>'''bullseye~~zero2w-~~xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4''' It is a compressed package of rootfs~~img267. ~~The meaning of each field in the name is</li></ol></li></ol>~~png]]

<~~blockquote~~/div>~~a) '''bullseye''' represents~~ </ol><ol start="8" style="list-style-type: decimal;"><li>Then select the ~~type~~ path to be uploaded to the development board on the right side of ~~Linux distribution~~ the filezilla software, select the file to be uploaded on the Windows PC on the left side of ~~rootfs~~the filezilla software, right-click the mouse, and then click the upload option to start uploading the file to the development board.</li>

~~b) '''xfce''' indicates that the rootfs is the desktop version, and if it is cli, it indicates the server version.~~<div class="figure">

~~c) '''arm64''' represents the architecture type of rootfs~~[[File:zero2w-img268.png]]

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</~~blockquote~~div></ol><ol start="29" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~'''bullseye-xfce-arm64~~After the upload is completed, you can go to the corresponding path in the development board Linux system to view the uploaded file.~~5250ec7002de9e81a41de169f1f89721.tar.lz4.list''' Lists~~ </li><li>The method of uploading a folder is the same as the ~~package names~~ method of ~~all packages installed by rootfs~~uploading a file, so I won't go into details here.</li></ol>

~~test@test:~/orangepi~~</~~'''~~span>

~~bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4~~== Instructions for using the logo on and off the machine ==

~~bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4.current~~ ~~bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4.list~~ <ol ~~start="11"~~ style="list-style-type: decimal;"><li>If The power on/off logo will only be displayed on the desktop version of the ~~required rootfs already exists under~~ system by default.</li><li>Set the '''bootlogo''' variable to '''false''' in '''~~external~~/~~cache~~boot/~~rootfs~~orangepiEnv.txt'''~~, then compiling~~ to turn off the ~~rootfs again will directly skip the compilation process and will not restart the compilation~~switch logo. ~~When compiling the image, it will also go to~~ {| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~external~~sudo vim /~~cache~~boot/~~rootfs~~orangepiEnv.txt''' ~~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 time.~~</lip>verbosity=1</olp> '''bootlogo=false'''~~== Compile linux image ==~~|}</li>~~# Run~~ <li>Set the '''~~build~~bootlogo''' variable to '''true''' in '''/boot/orangepiEnv.shtxt''' ~~script, remember~~ to ~~add sudo permissions~~enable the power on/off logo.{| class="wikitable" style="width:800px;" |-| ~~test~~orangepi@~~test~~orangepi:~~~/orangepi-build~~$ '''sudo vim /boot/orangepiEnv.txt'''verbosity=1</~~build.sh~~p>'''bootlogo=true'''|}</li><~~ol start~~li>The location of the boot logo picture in the Linux system is{| class="2wikitable" style="~~list~~width:800px;" |-| '''/usr/share/plymouth/themes/orangepi/watermark.png'''|}</li><li>After replacing the boot logo image, you need to run the following command to take effect{| class="wikitable" style~~-type~~="width: ~~decimal~~800px;">|-| <lip>~~Select~~ orangepi@orangepi:~$ '''~~Full OS image for flashing~~sudo update-initramfs -u''' ~~and press Enter~~|}</li></ol>

<~~div class~~span id="~~figure~~how-to-turn-on-the-power-button-in-linux5.4">

~~[[File:zero2w-img292~~== How to turn on the power button in Linux5.~~png]]~~4 ==

<There is no power on/~~div><ol start="3" style="list-style-type: decimal;"><li>Then select~~ off button on the ~~model~~ main board of the development board<. We can expand it through a 24pin expansion board. The location of the power on/~~li></ol>~~off button on the expansion board is as follows:

[[File:zero2w-~~img275~~img269.png]]

~~<ol start="4" style="list-style-type: decimal;"><li>Then select the branch type~~ The power on/off button of the ~~kernel source code~~Linux 6. ~~Different versions of~~ 1 image is turned on by default, but the ~~kernel source code maintain different rootfs types.<~~power on/p>~~<ol style="list-style-type: lower-alpha;"><li>In~~ off button of the ~~current branch, you can see three options: debian11, ubuntu20~~Linux 5.~~04,~~ 4 kernel image is turned off by default and ~~ubuntu22.04~~needs to be turned on manually for normal use.~~</li><li>In the next branch, you can see three options~~The steps are as follows: ~~debian11, debian12, and ubuntu22.04.</li></ol></li></ol>~~

~~[[File:zero2w-img276.png]]~~ <ol ~~start="5"~~ style="list-style-type: decimal;"><li>~~If you select the next branch, you will also be prompted to select the memory size, and you do not need~~ First run '''orangepi-config'''. Ordinary users remember to ~~select the current branch~~add '''sudo''' permissions.~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<li>If the development board you purchased has a memory size of 1.5GB, please select the first option.</li>~~|-~~<li>If the development board you purchased has 1GB or 2GB or 4GB memory size, please choose the second option.~~| ~~[[File~~orangepi@orangepi:~~zero2w~~~$ '''sudo orangepi-~~img277.png]]~~config'''~~</li></ol>~~|}

</li>

<li>Then select '''System'''[[File:zero2w-img80.png]]</li><li>Then select '''Hardware'''[[File:zero2w-img81.png]]</li><li>Then use the ~~type~~ keyboard's arrow keys to locate the position shown in the picture below, and then use the '''space''' to select the dtbo configuration of ~~rootfs~~the SPI you want to open.[[File:zero2w-img270.png]]</li><li>Then select '''<Save>''' to save[[File:zero2w-img83.png]]</li><li>Then select '''<Back>'''[[File:zero2w-img84.png]]</li><li>Then select '''<Reboot>''' to restart the system to make the configuration take effect.[[File:zero2w-img85.png]]</li></ol>

~~[[File:zero2w~~

== How to shut down and restart the development board == <ol ~~start="7"~~ style="list-style-type: decimal;"><li>~~Then select~~ During the running of the Linux system, if you directly unplug the power supply, it may cause the ~~type~~ file system to lose some data. It is recommended to use the '''poweroff''' command to shut down the Linux system of ~~image~~the development board before powering off, and then unplug the power supply.~~<ol~~ {| class="wikitable" style="~~list~~width:800px;" |-| orangepi@orangepi:~$ '''sudo poweroff'''|}{| class="wikitable" style="background-~~type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>'''~~Image with console interface (server)~~Note that after turning off the development board, you need to unplug and replug the power supply before it can be turned on.''' ~~Represents~~ </big>|}</li><li>In addition to using the poweroff command to shut down, you can also use the ~~image~~ power on/off button on the expansion board to shut down.[[File:zero2w-img269.png]]{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that Linux 5.4 requires manual configuration of the ~~server version~~power on/off button before it can be used. For the opening method, ~~which is relatively small~~ 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 ~~size~~Linux5.4]].'''</big>|}</li><li>Use the '''~~Image with desktop environment~~reboot'''~~Represents an image with a desktop, which is relatively large~~ command to restart the Linux system in ~~size.~~the development board{| class="wikitable" style="width:800px;" |-| <~~/li~~p>orangepi@orangepi:~$ '''sudo''' '''reboot'''</olp>|}

</li></ol>

<~~div class~~span id="~~figure~~linux-sdkorangepi-build-usage-instructions">

~~[[File:zero2w~~= '''Linux SDK——orangepi-~~img287.png]]~~build usage instructions''' =

<~~/div><ol start="8" style~~span id="~~list~~compilation-~~style~~system-~~type: decimal;~~requirements"><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></ol~~span>== Compilation system requirements ==

The Linux SDK, '''orangepi-build''', only supports running on X64 computers with '''<~~div class~~span style="~~figure~~color:#FF0000">Ubuntu 22.04''' 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 '''22.04''', it means that the Ubuntu version currently used does not meet the requirements. Please change the system before performing the following operations.

~~[[File~~{| class="wikitable" style="width:~~zero2w~~800px;" |-~~img288.png]]~~| test@test:~$ '''lsb_release -a'''

~~</div><ol start="9" style="list-style-type: decimal;"><li>If you~~ No LSB modules are ~~compiling a desktop version of the image, you also need to select the type of desktop environment~~available. ~~Currently, only XFCE is maintained, so please select an XFCE type desktop.</li></ol>~~

~~[[File~~Distributor ID:~~zero2w-img289.png]]~~Ubuntu

~~[[File~~Description:~~zero2w-img290~~Ubuntu 22.~~png]]~~04 LTS

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

~~[[File~~Codename:~~zero2w-img291.png]]~~'''jammy'''|}

~~<ol start="10" style="list~~If the computer is installed with a Windows system and does not have Ubuntu 22.04 installed on it, you can consider using'''VirtualBox''' or '''VMware''' to install an Ubuntu 22.04 virtual machine in the Windows system. But please note, do not compile orangepi-~~style~~build on the WSL virtual machine, because orangepi-~~type: decimal;"><li>Then~~ 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 ~~compilation of~~ Linux system on the ~~linux image will begin~~development board. Use orangepi-build. The ~~general process~~ installation image download address of ~~compilation~~ Ubuntu 22.04 amd64 version is ~~as follows</li></ol>~~:

a{| class="wikitable" style="width:800px;" |-| [https://repo.huaweicloud.com/ubuntu-releases/21.04/ubuntu-21.04-desktop-amd64.iso '''https://mirrors.tuna.tsinghua. ~~Initialize the compilation environment of Ubuntu PC and install the software packages required for the compilation process~~edu. bcn/ubuntu-releases/22. ~~Download the source code of u~~04/ubuntu-~~boot and linux kernel (if already cached, only update the code)~~ c22. ~~Compile u~~04-~~boot source code and generate u~~desktop-~~boot deb package~~amd64.iso''']|}

dAfter installing Ubuntu 22. ~~Compile linux~~ 04 on your computer or virtual machine, please first set the software source ~~code and generate linux-related deb packages~~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:

~~e. Make~~ <ol style="list-style-type: lower-alpha;"><li>For the ~~deb package~~ method of ~~linux firmware~~replacing Tsinghua Source, please refer to the instructions on this page.</li>

f{| class="wikitable" style="width:800px;" |-| [https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/ '''https://mirrors.tuna.tsinghua.edu. ~~Make~~ cn/help/ubuntu/''']|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Note that the ~~deb package of orangepi-config tool~~Ubuntu version needs to be switched to 22.04.</li>

g[[File:zero2w-img271.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The contents of the '''/etc/apt/sources. ~~Create a deb package with board~~list''' file that need to be replaced are:</li>{| class="wikitable" style="width:800px;" |-~~level support~~| test@test:~$ '''sudo mv /etc/apt/sources.list cat /etc/apt/sources.list.bak'''

~~h. If you compile the desktop version image, you will also create a desktop-related deb package~~test@test:~$ '''sudo vim /etc/apt/sources.list'''

i'''#''' The source code image is commented by default to improve apt update speed. ~~Check whether rootfs has been cached. If not, re-create rootfs. If it has been cached, decompress it directly and use~~ You can uncomment ityourself if necessary.

jdeb https://mirrors. ~~Install the deb package generated previously into rootfs~~tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse

k'''#''' deb-src https://mirrors.tuna.tsinghua. ~~Make some specific settings for different development boards and different types of images, such as pre-installing additional software packages, modifying system configurations, etc~~edu.cn/ubuntu/ jammy main restricted universe multiverse

ldeb https://mirrors. ~~Then create the image file and format the partition~~tuna. ~~The default type is ext4~~tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse

m'''#''' deb-src https://mirrors. ~~Then copy the configured rootfs to the mirror partition~~tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse

ndeb https://mirrors. ~~Then update initramfs~~tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse

o'''#''' deb-src https://mirrors. ~~Finally, write the bin file of u~~tuna.tsinghua.edu.cn/ubuntu/ jammy-~~boot into the image through the dd command.~~backports main restricted universe multiverse

~~<ol start="11" style="list~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-~~style-type: decimal;">~~security main restricted universe multiverse~~<li>After compiling the image, the following message will be displayed<ol style="list~~'''#''' deb-~~style-type~~src https: ~~lower-alpha;"><li>The storage path of the compiled image<~~/~~li><~~/~~ol>~~<mirrors.tuna.tsinghua.edu.cn/~~li><~~ubuntu/~~ol>~~jammy-security main restricted universe multiverse

~~[ 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 start="2" style="list~~'''#''' Pre-~~style-type: lower-alpha;"><li>Compilation time</li></ol>~~release software source, not recommended to be enabled

'''~~[ o.k. ] Runtime [ 19 min ]~~#'''deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse

'''#''' deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse|}</ol><ol start="34" style="list-style-type: lower-alpha;"><li>~~Repeat~~ After the ~~command~~ replacement, you need to ~~compile~~ update the ~~image~~package information and ensure that no errors are reported. ~~Use~~ </li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt-get update'''|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>'''In addition, since the ~~following command~~ source code of the kernel and Uboot are stored on GitHub, it is very important to ~~start~~ ensure that the computer can download the code from GitHub normally when compiling the image ~~directly without selecting it through the graphical interface~~.'''</li></ol>

~~[ 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''' ]~~span>

~~~~source code of linux sdk ==

=== Download orangepi-build from github == ~~'''Instructions for using the Orange Pi OS Arch system'''~~ =

~~<span id="orange~~Linux sdk refers to the orangepi-~~pi-os-arch~~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-~~function-adaptation~~build. Use the following command to download the orangepi-~~status">== Orange Pi OS Arch system function adaptation status ==~~build code:

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

|-

| test@test:~$ '''~~Motherboard functions~~sudo apt-get update'''| test@test:~$ '''~~OPi OS Arch~~sudo apt-get install -y git'''|-| test@test:~$ '''~~HDMI video~~git clone https://github.com/orangepi-xunlong/orangepi-build.git -b next'''| ~~'''OK'''~~}{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

| <big>'''~~HDMI Audio~~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.'''</big> <div class="figure"> [[File:zero2w-img272.png| ~~'''OK'''~~center|800px]] </div>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

| <big>'''~~Type~~When downloading the orangepi-~~C USB2~~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). 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 account.~~0 x 2~~'''</big>|} The u-boot and linux kernel versions currently used by the H618 series development boards are as follows: {| ~~'''OK'''~~class="wikitable" style="width:800px;text-align: center;"

|-

| '''~~TF Card Startup~~branch'''| '''OKu-boot Version'''| '''linux Kernel version'''

|-

| '''~~WIFI~~current'''| '''OKu-boot v2018.05'''| '''linux5.4'''

|-

| '''~~Bluetooth~~next'''| '''OKu-boot v2021.07'''| '''linux6.1'''|} {| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

| <big>'''The branch mentioned here is not the same thing as the branch of orangepi-build source code, please don't get confused. This branch is mainly used to distinguish different kernel source code versions.''' '''~~LED Light~~We define the linux5.4 bsp kernel currently provided by Allwinner as the current branch. The latest linux6.1 LTS kernel is defined as the next branch.'''</big>| } After downloading, the following files and folders will be included: <ol style="list-style-type: lower-alpha;"><li>'''build.sh'OK'': Compile startup script</li><li>'''external''': Contains configuration files needed to compile the image, specific scripts, and source code of some programs, etc.</li><li>'''LICENSE''': GPL 2 license file</li><li>'''README.md''': orangepi-build documentation</li><li>'''scripts''': Common script for compiling linux images</li></ol>{| class="wikitable" style="width:800px;"

|-

| ~~'''40pin GPIO'''| '''OK'''~~|-~~| '''40pin I2C'''| '''OK'''~~|test@test:~/orangepi-| build$ '''~~40pin SPI~~ls'''~~| '''OK'''~~|-~~| '''40pin UART'''| '''OK'''~~|-~~| '''40pin PWM'''| '''OK'''~~|-~~| '''Temperature Sensor'''| '''OK'''~~|-~~| '''Hardware watchdog'''| '''OK'''~~|-~~| '''Mali GPU'''| '''NO'''~~|-~~| '''Video codec'''~~| '''NObuild.sh      external      LICENSE      README.md      scripts'''

|}

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

|-

|}

~~== Orange Pi OS Arch System User Guide Instructions ==~~

~~First of all, please note that~~ === Download the OPi OS Arch system does not have a default orangepi user and password, so you cannot directly log in remotely through the serial port and ssh after the system is started after burning (not even the root user). This is different from Ubuntu and Debian systems.cross-compilation tool chain ===

When ~~the OPi OS Arch system~~ orangepi-build is ~~started~~ run for the first time, ~~you need to connect an HDMI display~~ it will automatically download the cross-compilation '''toolchain''' and ~~then initialize~~ put it in the ~~system settings through~~ '''toolchains''' folder. Every time you run orangepi-build's build.sh script, it will check whether the ~~user wizard (including creating a new user name and setting a password)~~cross-compilation toolchain in toolchains exists. ~~The setup steps of~~ If If it does not exist, the ~~user wizard are as follows:~~download will be restarted. If it exists, it will be used directly without repeated downloading.

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

~~<li>After burning the system, when you start it for the first time and enter the desktop, you will see the user wizard program shown in the figure below.~~

[[File:zero2w-~~img293~~img273.png]]

</div~~></li~~>~~<li>First you need to select~~ The mirror URL of the ~~language you want<div class="figure">~~cross-compilation tool chain in China is the open source software mirror site of Tsinghua University:

{| class="wikitable" style="width:800px;" |-| [~~[File~~https:~~zero2w~~//mirrors.tuna.tsinghua.edu.cn/armbian-~~img294~~releases/_toolchain/ '''https://mirrors.tuna.tsinghua.edu.~~png]~~cn/armbian-releases/_toolchain/''']|}

~~</div></li><li>~~After ~~selecting the language~~toolchains is downloaded, ~~the user wizard~~ it will ~~immediately switch to the corresponding language interface, as shown below in Chinese<div class="figure">~~contain multiple versions of cross-compilation '''toolchain''':

~~[[File~~{| class="wikitable" style="width:~~zero2w~~800px;" |-~~img295.png]]~~| test@test:~/orangepi-build$ '''ls toolchains/'''

~~</div></li><li>Then select the area<div class="figure">~~gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu

~~[[File:zero2w~~gcc-~~img296~~linaro-4.9.4-2017.~~png]]~~01-x86_64_aarch64-linux-gnu

~~</div></li><li>Then select the keyboard model<div class="figure">~~gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabi

~~[[File:zero2w~~gcc-~~img297~~arm-11.2-2022.~~png]]~~02-x86_64-arm-none-linux-gnueabihf

~~</div></li><li>Then create a new username and set a password<div class="figure">~~gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabi

~~[[File:zero2w~~gcc-~~img298~~linaro-aarch64-none-elf-4.8-2013.~~png]]~~11_linux

~~</div></li><li>Then make sure there is no problem with the selection, and then click the install '''button'''<div class="figure">~~gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu

~~[[File:zero2w~~gcc-~~img299~~linaro-5.5.0-2017.~~png]]~~10-x86_64_arm-linux-gnueabihf

~~</div></li><li>Then wait for the installation to complete<div class="figure">~~gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux

~~[[File:zero2w~~gcc-~~img300~~arm-9.2-2019.~~png]]~~12-x86_64-arm-none-linux-gnueabihf

~~</div></li><li>After the installation is complete, you need to click the '''Finish''' button to restart the system~~gcc-linaro-7.~~<div class="figure">~~4.1-2019.02-x86_64_aarch64-linux-gnu

~~[[File:zero2w~~gcc-~~img301~~linaro-arm-none-eabi-4.8-2014.~~png]]~~04_linux|}

~~</div></li><li>~~The ~~Orange Pi Hello program will automatically start after restarting. At this time, you need~~ cross-compilation tool chain used to ~~remove~~ compile 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.<div class="figure">~~H618 Linux kernel source code is:

~~[[File~~<ol style="list-style-type:~~zero2w~~lower-~~img302.png]]~~ ~~</div~~alpha;"><pli>~~At this point, you can use the newly created username and password to log in to the OPi OS system through the serial port or ssh~~linux5.~~~~4</li>{| class="wikitable" style="width:800px;" |-| '''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''|}</ol> <~~span id~~ol start="2" style="~~how~~list-tostyle-~~set-dt~~type: lower-~~overlays~~alpha;"><li>linux6.1</~~span~~li>{| class="wikitable" style= ~~How~~ "width:800px;" |-| '''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''|}</ol>The cross-compilation tool chain used to ~~set DT overlays ==~~compile the H618 u-boot source code is:

~~The multiplexing functions such as I2C~~<ol style="list-style-type: lower-alpha;"><li>v2018.05</~~SPI~~li>{| class="wikitable" style="width:800px;" |-| '''gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabi'''|}</~~UART~~ol><ol start="2" style="list-style-type: lower-alpha;"><li>v2021.07</~~PWM in the 40~~li>{| class="wikitable" style="width:800px;" |-~~pin development board are turned off by default in the kernel~~| '''~~s dts, and the corresponding DT overlays need to be manually turned on before they can be used~~gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''|}</ol>

~~The method to open DT overlays in OPi OS Arch system is as follows:~~=== orangepi-build complete directory structure description ===

~~# First open the '''/boot/extlinux/extlinux.conf''' configuration file~~ ~~[orangepi@orangepi-pc ~]$ '''sudo vim /boot/extlinux/extlinux.conf'''~~ <ol ~~start="2"~~ style="list-style-type: decimal;"><li>~~Then open the corresponding configuration by adding '''FDTOVERLAYS''' '''/dtbs/allwinner/overlay/xxx.dtbo''' in '''/boot/extlinux/extlinux.conf'''~~<~~/li~~p>~~</ol>~~ ~~'''Note that xxx.dtbo in FDTOVERLAYS /dtbs/allwinner/overlay/xxx.dtbo needs to be replaced with~~ After downloading, the orangepi-build warehouse does not contain the source code of the ~~specific dtbo configuration~~linux kernel, ~~please do not copy it.'''~~ ~~[orangepi@orangepi~~u-~~pc ~]$ '''sudo vim /~~boot~~/extlinux/extlinux~~and cross-compilation tool chain.~~conf'''~~ ~~LABEL Orange Pi~~ ~~KERNEL /Image~~ ~~FDT /dtbs/allwinner/sun50i~~The source code of the linux kernel and u-~~h616-orangepi-zero2w~~boot is stored in an independent git warehouse.~~dtb~~ ~~'''FDTOVERLAYS~~ </~~dtbs/allwinner/overlay/xxx.dtbo''' #Configuration that needs to be added~~p><ol ~~start="3"~~ style="list-style-type: ~~decimal~~lower-alpha;"><li>The ~~storage path of xxx.dtbo in~~ git warehouse where the ~~OPi OS Arch image~~ linux kernel source code is stored is as follows. Please note that ~~not all dtbo under this path can be used.~~the branch of the linux-orangepi warehouse is switched to<~~p>'''/boot/dtbs/allwinner/overlay/'''</li~~ol style="list-style-type: none;"><li>~~The DT overlays configuration that can be used by the development board is as follows~~a) Linux5.4</li~~></ol~~> {| class="wikitable" style="width:800px;"

|-

| https://github.com/orangepi-xunlong/linux-orangepi/tree/'''~~Functions on the development board~~orange-pi-5.4-sun50iw9'''| ~~'''Corresponding DT overlays configuration'''~~}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>b) Linux6.1</li>{| class="wikitable" style="width:800px;"

|-

| https://github.com/orangepi-xunlong/linux-orangepi/tree/'''~~40pin~~ orange-pi-6.1- ~~i2c0~~sun50iw9'''| ~~'''sun50i~~}</ol></li></ol><ol start="2" style="list-style-type: lower-alpha;"><li>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<ol style="list-~~h616~~style-pitype: lower-~~i2c0~~alpha;"><li>a) v2018.~~dtbo'''~~05</li>{| class="wikitable" style="width:800px;"

|-

| https://github.com/orangepi-xunlong/u-boot-orangepi/tree/'''~~40pin~~ v2018.05- ~~i2c1~~h618'''| ~~'''sun50i~~}</ol><ol start="2" style="list-~~h616~~style-pitype: lower-~~i2c1~~alpha;"><li>b) v2021.~~dtbo'''~~07</li>{| class="wikitable" style="width:800px;"

|-

| https://github.com/orangepi-xunlong/u-boot-orangepi/tree/'''~~40pin~~ v2021.07- ~~i2c2~~sunxi'''| }</ol></li></ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>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:<ol style="list-style-type: lower-alpha;"><li>'''build.sh''': Compile startup script</li><li>'''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.</li><li>'''kernel''': Store the source code of the linux kernel</li><li>'''~~sun50i~~LICENSE''': GPL 2 license file</li><li>'''README.md''': orangepi-~~h616~~build documentation</li><li>'''output''': Store compiled u-piboot, linux and other deb packages, compilation logs, and compiled images and other files</li><li>'''scripts''': Common script for compiling linux images</li><li>'''toolchains''': Store cross-compilation tool chain</li><li>'''u-~~i2c2.dtbo~~boot''': Store the source code of u-boot</li><li>'''userpatches''': Store the configuration files needed to compile the script</li>{| class="wikitable" style="width:800px;"

|-

| test@test:~/orangepi-build$ '''~~40pin - uart2~~ls'''| '''~~sun50i~~build.sh      external      kernel      LICENSE      output      README.md      scripts      toolchains      u-~~h616~~boot      userpatches'''|}</ol></li></ol> == Compile u-boot == # Run the build.~~dtbo'''~~sh script, remember to add sudo permissions {| class="wikitable" style="width:800px;"

|-

| ~~'''40pin - uart3'''| '''sun50i-h616-pi-uart3.dtbo'''~~|-~~| '''40pin - uart4'''| '''sun50i-h616-pi-uart4.dtbo'''~~|-~~| '''40pin - uart5'''| '''sun50i-h616-ph-uart5.dtbo'''~~|-~~| '''40pin - pwm1'''| '''sun50i-h616-pi-pwm1.dtbo'''~~|-~~| '''40pin - pwm2'''| '''sun50i-h616-pi-pwm2.dtbo'''~~|-~~| '''40pin - pwm3'''| '''sun50i-h616-pi-pwm3.dtbo'''~~|-~~| '''40pin - pwm4'''| '''sun50i-h616-pi-pwm4.dtbo'''~~|-~~| '''40pin - spi1 cs0'''| '''sun50i-h616-spi1-cs0-spidev.dtbo'''~~|test@test:~/orangepi-| build$ '''~~40pin - spi1 cs1'''| '''sun50i-h616-spi1-cs1-spidev~~sudo .~~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~~/build.~~dtbo~~sh'''|}

<ol start="52" style="list-style-type: decimal;"><li>~~If you need to open multiple configurations at the same time, just add the paths of multiple configurations directly after~~ Select '''~~FDTOVERLAYS.~~U-boot package''' ~~For example, the configuration of opening i2c1~~ and ~~uart5 at the same time is as follows~~press Enter</li~~></ol~~>

~~[orangepi@orangepi-pc ~]$ '''sudo vim /boot/extlinux/extlinux.conf'''~~<div class="figure">

~~LABEL Orange Pi~~[[File:zero2w-img274.png]]

~~KERNEL~~ </~~Image~~div></ol><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li>

~~FDT /dtbs/allwinner/sun50i-h616-orangepi~~[[File:zero2w-~~zero2w~~img275.~~dtb~~png]] ~~'''FDTOVERLAYS~~ </~~dtbs/allwinner/overlay/sun50i-h616-pi-i2c1.dtbo /dtbs/allwinner/overlay/sun50i-h616-ph-uart5.dtbo'''~~ol><ol start="64" style="list-style-type: decimal;"><li>~~After setting, you need to restart~~ Then select the ~~system for~~ branch type of u-boot<ol style="list-style-type: lower-alpha;"><li>The current branch will compile the ~~configuration~~ u-boot v2018.05 version code that needs to ~~take effect~~be used by the linux5.4 image.</li><li>The next branch will compile the u-boot v2021.07 version code that needs to be used by the linux6.1 image.</olp> [[~~orangepi@orangepi~~File:zero2w-~~pc ~~~img276.png]]~~$ '''sudo reboot'''~~</li></ol></li><li>If you select the next branch, you will also be prompted to select the memory size, and you do not need to select the current branch.<~~span id~~ol style="~~how~~list-tostyle-~~install~~type: lower-~~software~~alpha;"><~~/span~~li>~~== How to install software ==~~ ~~You can use~~ If the ~~pacman package management tool to install software that is not available in OPi OS~~development board you purchased has a memory size of 1. ~~For example~~5GB, please select the ~~command to install the vim editor is as follows~~first option. </li><li>If the development board you ~~want to install other software~~purchased has 1GB or 2GB or 4GB memory size, ~~you only need to replace vim with the package name of~~ please choose the ~~software you want to install~~second option. [[~~orangepi@orangepi~~File:zero2w-~~pc ~~~img277.png]~~$ '''sudo pacman -Syy vim'''~~]</li></ol></li></ol><~~span id~~ol start="6" style="~~android~~list-12style-~~tv-system-usage-instructions~~type: decimal;"><li>Then it will start to compile u-boot. Some of the information prompted when compiling the next branch is as follows:</~~span~~p> ~~= '''Android 12 TV system usage instructions''' =~~ <~~span id~~ol style="~~supported~~list-~~android~~style-~~versions~~type: lower-alpha;"><li>Version of u-boot source code</~~span~~li>~~== 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 version~~class="wikitable" style="width:800px;"

|-

| ~~'''Android 12 TV Version'''~~| [ o.k. ] Compiler version [ '''~~linux5.4~~aarch64-linux-gnu-gcc 11''']

|}

</ol><~~span id~~ol start="~~android~~3" style="list-12style-tvtype: lower-~~function-adaptation-status~~alpha;"><li>Path to the compiled u-boot deb package</~~span~~li>~~== Android 12 TV function adaptation status ==~~ {| class="wikitable" style="width:800px;"

|-

| [ o.k. ] Target directory [ '''~~Motherboard functions~~orangepi-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 video~~linux-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 Audio~~1 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 [ '''~~Type~~sudo ./build.sh BOARD=orangepizero2w BRANCH=next BUILD_OPT=u-~~C USB2.0 x 2~~boot''']| ~~'''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 startup~~linux-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$ '''~~WIFI~~vim userpatches/config-default.conf'''| ...... IGNORE_UPDATES="'''OKyes'''" ......|}</ol><ol start="9" style="list-style-type: decimal;"><li>When debugging u-boot code, you can use the following method to update u-boot in the linux image for testing<ol style="list-style-type: lower-alpha;"><li>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$ '''~~Bluetooth~~scp \'''| '''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 Camera~~sudo dpkg -i'''| '''OKlinux-u-boot-next-orangepizero2w_x.x.x_arm64.deb'''|}</ol><ol start="3" style="list-style-type: lower-alpha;">~~| '''LED Light'''~~<li>Then run the nand-sata-install script</li>{| ~~'''OK'''~~class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~40pin GPIO~~sudo nand-sata-install'''| }</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then select '''5 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> == Compile the linux kernel == # Run the '''OKbuild.sh'''script, remember to add sudo permissions ::{| 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'''

|}

~~{| class~~<ol start="~~wikitable~~2"|-~~| '''24pin Expansion board function'''| '''Android12 TV'''~~|style="list-~~| '''100M network port'''| '''OK'''~~|style-type: decimal;">| <li>Select '''~~100M Ethernet port light~~Kernel package'''~~| '''OK'''~~|-~~| '''USB2.0 HOST x 2'''| '''OK'''~~|-~~| '''Infrared reception'''| '''OK'''~~|-~~| '''Headphone audio playback'''| '''OK'''~~|-~~| '''On~~and press Enter</~~off button'''| '''OK'''~~|-~~| '''LRADC''' '''Custom buttons x 2'''| '''OK, The default setting is the volume up and down keys.'''~~|-~~| '''TV-OUT'''| '''OK'''~~|}li>

<~~span id~~div class="~~onboard-led-light-display-instructions~~figure">~~== Onboard LED light display instructions ==~~

~~{| class="wikitable"~~|[[File:zero2w-|~~| '''green light'''| '''red light'''~~|-~~| '''u-boot startup phase'''| '''Off'''| '''on'''~~|-~~| '''Kernel boot to enter the system'''| '''on'''| '''on'''~~|}img281.png]]

<~~span id~~/div></ol><ol start="~~how~~3" style="list-tostyle-~~return-to-the-previous-interface-in-android~~type: decimal;"><~~/span~~li>~~== How~~ Then you will be prompted whether you need to display the kernel configuration interface. If you do not need to ~~return~~ modify the kernel configuration, select the first one. If you need to modify the ~~previous interface in Android ==~~kernel configuration, select the second one.</li>

~~We generally use~~ [[File:zero2w-img282.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select the ~~mouse and keyboard to control the Android system~~ model of the development board~~. When entering certain interfaces and need to return to the previous interface or desktop, we can only return by right-clicking the mouse, and the keyboard cannot return.~~</li>

If you have purchased the infrared remote control (other remote controls do not work) and a 24pin expansion board that come with the development board, after connecting the 24pin expansion board to the development board, you can also use the return key on the remote control to return to [[File:zero2w-img275.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then select the ~~previous menu. The location~~ branch type of the ~~return key is as shown below. Shown:~~kernel source code</li>

~~[[File~~:~~zero2w-img303~~:a. The current branch will compile the linux5.~~png]]~~4 kernel source code

~~== How to use ADB ==~~::b. The next branch will compile the linux6.1 kernel source code

::[[File:zero2w-img276.png]]</ol><~~span id~~ol start="~~use~~6" style="list-~~network~~style-~~connection-adb-debugging~~type: decimal;"><li>If you choose to display the kernel configuration menu (the second option) in step 3), the kernel configuration interface opened through '''make menuconfig''' will pop up. At this time, you can directly modify the kernel configuration. After modification, save and exit. Yes, compilation of the kernel source code will begin after exiting.</~~span~~li>~~=== Use network connection adb debugging ===~~

~~'''Using network adb does not require a USB Typc C interface data cable to connect the computer and the development board~~[[File:zero2w-img283. Instead, it communicates through the network, so first make sure that the development board's wired or wireless network is connected, and then obtain the IP address of the development board. Next To be used.'''png]]

~~# Make sure~~ <ol style="list-style-type: lower-alpha;"><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.</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''~~service~~sudo .~~adb~~/build.~~tcp~~sh KERNEL_CONFIGURE=no'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>b.~~port~~You can also set '''KERNEL_CONFIGURE=no''' of in the orangepi-build/userpatches/config-default.confconfiguration file to permanently disable this function.</li><li>If the following error is prompted when compiling the kernel, it is because the ~~Android system~~ Ubuntu PC terminal interface is ~~set~~ too small, causing the make menuconfig interface to be unable to be displayed. Please increase the Ubuntu PC terminal to ~~5555 port number~~the maximum size, and then rerun the build.sh script.</li>

~~apollo~~[[File:zero2w-p2img284.png]]</ol></ol><ol start="7" style="list-style-type:decimal;"><li>Part of the information prompted when compiling the next branch kernel source code is explained as follows:<ol style="list-style-type: lower-alpha;"><li>Version of the linux kernel source code</ ~~# '''getprop~~ li>{| ~~grep &quot~~class="wikitable" style="width:800px;~~adb.tcp"'''~~" |-| [~~service~~o.~~adb~~k.~~tcp.port~~]: Compiling current kernel [~~5555~~'''6.1.31''' ]|}</ol><ol start="2" style="list-style-type: ~~decimal~~lower-alpha;"><li>If The version of the cross-compilation tool chain used</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Compiler version [ '''~~service.adb.tcp.port~~aarch64-linux-gnu-gcc 11''' ~~is not set, you can use the following command in the serial port to set the port number of the network adb~~]|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The default configuration file used by the kernel and the path where it is stored are as follows</olli>{| class="wikitable" style="width:800px;" ~~apollo~~|-~~p2:/ #~~ | [ o.k. ] Using kernel config file [ '''~~setprop service~~orangepi-build/external/config/kernel/linux-6.~~adb~~1-sun50iw9-next.~~tcp.port 5555~~config''']|} ~~apollo~~<ol start="4" style="list-p2style-type:lower-alpha;"><li>The path to the kernel-related deb package generated by compilation</ # li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Target directory [ '''~~stop adbd~~output/debs/''']|}</ol>~~apollo~~<ol start="5" style="list-p2style-type:lower-alpha;"><li>The package name of the kernel image deb package generated by compilation</ # li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] File name [ '''~~start adbd~~linux-image-next-sun50iw9_x.x.x_arm64.deb''']|}</ol><ol start="36" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Install adb tool on Ubuntu PC~~Compilation time</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-~~test@test:~$~~ | [ o.k. ] Runtime [ '''~~sudo apt-get update~~10 min''']|}</ol><ol start="7" style="list-style-type: lower-alpha;"><li>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 code.</li>~~test@test~~{| class="wikitable" style="width:~$ 800px;" |-| [ o.k. ] Repeat Build Options [ '''sudo ~~apt-get install -y adb~~./build.sh BOARD=orangepizero2w BRANCH=next BUILD_OPT=kernel KERNEL_CONFIGURE=no''']|}</ol></li></ol><ol start="48" style="list-style-type: decimal;"><li>~~Then connect network adb on Ubuntu PC~~View the kernel-related deb package generated by compilation</lip></olstyle="list-style-type: lower-alpha;"> ~~test@test:~$~~ <li>'''~~adb connect 192~~linux-dtb-next-sun50iw9_x.~~168~~x.1x_arm64.~~xxx:5555~~deb''' Contains dtb files used by the kernel</li><li>'''~~(Need to be modified to the IP address of the development board)~~linux-headers-next-sun50iw9_x.x.x_arm64.deb'''Contains kernel header files</li> * daemon not running; starting now at tcp:5037 * daemon started successfully ~~connected to 192~~<li>'''linux-image-next-sun50iw9_x.~~168~~x.1x_arm64.~~xxx~~deb''' Contains kernel images and kernel modules</li>{| class="wikitable" style="width:~~5555~~800px;" |-| test@test:~/orangepi-build$ '''~~adb devices~~ls output/debs/linux-*'''

~~List of devices attached~~output/debs/linux-dtb-next-sun50iw9_x.x.x_arm64.deb

~~192~~output/debs/linux-headers-next-sun50iw9_x.~~168~~x.1x_arm64.~~xxx:5555 device~~deb

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 PC~~modifications will be restored. The method is as follows:</li~~></ol~~>

~~test@test:~$~~ Set the IGNORE_UPDATES variable in '''~~adb shell~~userpatches/config-default.conf'''to "yes"

~~apollo~~{| class="wikitable" style="width:800px;" |-p2| test@test:~/orangepi-build$ '''vim userpatches/ #config-default.conf'''

IGNORE_UPDATES="'''yes'''"|}</ol><ol start="10" style=~~= Use data cable to connect adb debugging ===~~"list-style-type: decimal;"> ~~# Prepare a USB Type C interface data cable~~<li>If the kernel is modified, ~~plug one end of~~ you can use the ~~USB interface into the USB interface of~~ following method to update the ~~computer,~~ kernel and ~~plug one end of the USB Type C interface into the USB0 interface~~ kernel module of the development board ~~(see~~ Linux system<ol style="list-style-type: lower-alpha;"><li>Upload the ~~description~~ compiled deb package of the ~~picture on~~ Linux kernel to the ~~right below for the location~~ Linux system of ~~USB0). In this case,~~ the development board ~~is powered by the computer~~</li>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''cd output/debs''~~s USB interface, so please ensure that the computer~~'~~s USB interface can provide the most sufficient power to drive the development board.~~

~~[[File~~test@test:~~zero2w~~~/orangepi-~~img304.png]] [[File:zero2w-img305.png]]~~build/output/debs$ '''scp \'''

'''linux-image-next-sun50iw9_x.x.x_arm64.deb root@192.168.1.xxx:/root'''|}</ol><ol start="2" style="list-style-type: ~~decimal~~lower-alpha;"><li>Install ~~adb tool on Ubuntu PC~~the deb package of the new linux kernel just uploaded.</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg -i linux-image-next-sun50iw9_x.x.x_arm64.deb'''|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>Then restart the development board and check whether the kernel-related modifications have taken effect.</li>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo''' '''reboot'''|}</ol></li></ol> == Compile rootfs ==

~~test@test:~$ '''~~# Run the build.sh script, remember to add sudo ~~apt-get update'''~~permissions

::{| 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 recognized~~Select '''Rootfs and all deb packages''' and press Enter</li~~></ol~~>

~~test@test:~$ '''adb devices'''~~<div class="figure">

~~List of devices attached~~[[File:zero2w-img285.png]]

~~4c00146473c28651dd0 device~~</div></ol><ol start="3" style="list-style-type: decimal;"><li>Then select the model of the development board</li>

[[File:zero2w-img275.png]]

</ol>

<li>Then select the branch type of the kernel source code. Different versions of the kernel source code maintain different rootfs types.<ol style="list-style-type: lower-alpha;"><li>In the current branch, you can ~~log in to~~ see three options: debian11, ubuntu20.04, and ubuntu22.04.</li><li>In the ~~android system through adb shell on Ubuntu PC~~next branch, you can see three options: debian11, debian12, and ubuntu22.04.</lip></olli>

~~test@test~~[[File:~~~$ '''adb shell'''~~zero2w-img276.png]]</ol></li></ol><ol start="5" style="list-style-type: decimal;"><li>Then select the type of rootfs</li>

~~apollo~~[[File:zero2w-~~p2:~~img286.png]]</ $ol><~~span id~~ol start="6" style="~~view~~list-~~how~~style-totype: decimal;"><li>Then select the type of image<ol style="list-~~set~~style-~~hdmi~~type: lower-~~display-resolution~~alpha;"><li>'''Image with console interface (server)''' Represents the image of the server version, which is relatively small in size.</~~span~~li>~~== View how to set HDMI display resolution ==~~<li>'''Image with desktop environment''' Represents an image with a desktop, which is relatively large in size.</li>

<~~ol style~~div class="~~list-style-type: decimal;~~figure">~~<li>Enter first '''Settings'''[[File:zero2w-img306.png]]</li><li>Then select '''Device Preferences'''[[File:zero2w-img307.png]]</li><li>Then select '''Display & Sound'''[[File:zero2w-img308.png]]</li><li>Then select '''Advanced display settings'''[[File:zero2w-img309.png]]</li><li>Then select '''HDMI output mode'''[[File:zero2w-img310.png]]</li>~~<li>Then you can see the list of resolutions supported by the monitor. At this time, clicking the corresponding option will switch to the corresponding resolution. Please note that different monitors may support different resolutions. If you connect it to a TV, you will generally see more resolution options than the picture below.~~[[File:zero2w-img311.png]]</li><li>The HDMI output of the development board supports 4K display. When connected to a 4K TV, you can see the 4K resolution option.[[File:zero2w-img312.png]]</li></ol~~>

~~=== HDMI to VGA display test ===~~img287.png]]

~~<ol style="list-style-type: decimal;"><li>First you need to prepare the following accessories~~~~<ol style="list-style-type: lower-alpha;"><li>HDMI to VGA converter</li~~div></ol>

</li></ol>

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

~~[[File:zero2w-img144.png]]~~<div class="figure">

~~<ol start="2" style="list-style-type~~[[File: ~~lower~~zero2w-~~alpha;"><li>A VGA cable and a Mini HDMI male to HDMI female adapter</li></ol>~~img288.png]]

~~[[File~~</div></ol><ol start="8" style="list-style-type:~~zero2w-img145~~decimal;"><li>If you are compiling a desktop version of the image, you also need to select the type of desktop environment.~~png]] [[File:zero2w-img146~~Currently, only XFCE is maintained, so please select an XFCE type desktop.~~png]]~~</li>

~~<ol start="3" style="list-style-type~~[[File: ~~lower~~zero2w-~~alpha;"><li>A monitor or TV that supports VGA interface</li></ol>~~img289.png]]

~~~~<ol start="2" style="list-style-type: decimal;"><li>HDMI to VGA display test is as follows</li></ol>img290.png]]

~~[[File:zero2w-img313~~You can then select additional packages that need to be installed. Please press the Enter key here to skip directly.~~png]]~~

~~'''When using HDMI to VGA display, the development board and~~ [[File:zero2w-img291.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then the ~~Android system~~ compilation of ~~the development board do not need to make any settings~~rootfs will start. ~~You only need~~ Some of the ~~Mini HDMI interface~~ information prompted during compilation are as follows:<ol style="list-style-type: lower-alpha;"><li>Type of ~~the development board to display normally~~rootfs</li>{| class="wikitable" style="width:800px;" |-| [ o. ~~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~~k.] local not found [ Creating new rootfs cache for '''bullseye''' ]|}<~~span id~~/ol><ol start="2" style="wilist-fistyle-~~connection~~type: lower-~~method~~alpha;"><li>The storage path of the compiled rootfs compressed package</~~span~~li>{| class="wikitable" style= WI"width:800px;" |-~~FI connection method ==~~| ~~# Choose first~~ [ o.k. ] Target directory [ '''~~Settings~~orangepi-build/external/cache/rootfs''']|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The name of the rootfs compressed package generated by compilation</li>{| class="wikitable" style="width:800px;" |-| [o.k. ] File name [~~File:zero2w~~'''bullseye-xfce-~~img306~~arm64.~~png]~~5250ec7002de9e81a41de169f1f89721.tar.lz4''' ]|}</ol></li></ol><ol start="210" style="list-style-type: decimal;"><li>~~Then select~~ View the compiled rootfs compressed package<ol style="list-style-type: lower-alpha;"><li>'''~~Network & Internet~~bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4'''It is a compressed package of rootfs. The meaning of each field in the name is</li~~></ol~~>

~~[[File~~:~~zero2w-img314.png]]~~a) '''bullseye''' represents the type of Linux distribution of rootfs

~~<ol start="3" style="list-style-type~~: ~~decimal;"><li>Then turn on WI-FI</li></ol>~~b) '''xfce''' indicates that the rootfs is the desktop version, and if it is cli, it indicates the server version.

~~[[File~~:~~zero2w-img315.png]]~~c) '''arm64''' represents the architecture type of rootfs

: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="42" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~After turning on WI-FI, you can see the searched signals under~~ '''~~Available networks~~bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4.list'''.Lists the package names of all packages installed by rootfs</li><{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''ls external/cache/rootfs/~~ol>~~'''

~~[[File:zero2w~~bullseye-~~img316~~xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.~~png]]~~lz4

~~<ol start="5" style="list~~bullseye-~~style~~xfce-~~type: decimal;"><li>After selecting the WI-FI you want to connect to, the password input interface shown below will pop up~~arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4.~~</li></ol>~~current

bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4.list|}<~~div class~~/ol></li></ol><ol start="~~figure~~11"style="list-style-type: decimal;"><li>If the required rootfs already exists under '''external/cache/rootfs''', then compiling the rootfs again will directly skip the compilation process and will not restart the compilation. When compiling the image, it will also go to '''external/cache/rootfs''' to 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 time.</li></ol>

~~[[File:zero2w~~

~~</div><ol start~~=~~"6" style~~=~~"list-style-type: decimal;"><li>Then use the keyboard to enter the password corresponding to the WI-FI, and then use the mouse to click the Enter button on the virtual keyboard to start connecting to the WI-FI.</li></ol>~~Compile linux image ==

~~<div class="figure">~~# Run the '''build.sh''' script, remember to add sudo permissions

~~[[File~~:~~zero2w~~:{| class="wikitable" style="width:800px;" |-~~img318~~| test@test:~/orangepi-build$ '''sudo ./build.~~png]]~~sh'''|}

~~</div>~~<ol start="72" style="list-style-type: decimal;"><li>~~The display after successful WI-FI connection is as shown below~~Select '''Full OS image for flashing''' and press Enter</li~~></ol~~>

~~[[File:zero2w-img319.png]]~~<div class="figure">

~~== How to use WI-FI hotspot ==~~img292.png]]

~~# First, please make sure that the Ethernet port is connected to the network cable and can access the Internet normally.~~</div></ol><ol start="3" style="list-style-type: decimal;"># <li>Then select ~~'''Settings'''~~the model of the development board</li>

[[File:zero2w-~~img306~~img275.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select the branch type of the kernel source code. Different versions of the kernel source code maintain different rootfs types.<ol style="list-style-type: lower-alpha;"><li>In the current branch, you can see three options: debian11, ubuntu20.04, and ubuntu22.04.</li><li>In the next branch, you can see three options: debian11, debian12, and ubuntu22.04.</li>

[[File:zero2w-img276.png]]</ol></li></ol><ol start="35" style="list-style-type: decimal;"><li>If you select the next branch, you will also be prompted to select the memory size, and you do not need to select the current branch.<ol style="list-style-type: lower-alpha;"><li>If the development board you purchased has a memory size of 1.5GB, please select the first option.</li><li>If the development board you purchased has 1GB or 2GB or 4GB memory size, please choose the second option.[[File:zero2w-img277.png]]</li></ol></li><li>Then select the type of rootfs</li> [[File:zero2w-img286.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Then select the type of image<ol style="list-style-type: lower-alpha;"><li>'''~~Network & Internet~~Image with console interface (server)'''Represents the image of the server version, which is relatively small in size.</li><li>'''Image with desktop environment'''Represents an image with a desktop, which is relatively large in size.</olp></li>

~~[[File:zero2w-img314.png]]~~<div class="figure">

~~<ol start="4" style="list~~[[File:zero2w-~~style-type: decimal;"><li>Then select '''WIFI hotspot'''</li></ol>~~img287.png]]

~~[[File~~</div></ol></li></ol><ol start="8" style="list-style-type:~~zero2w~~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-~~img320~~installed by default.~~png]]~~Some functions may not be available''')</li>

<~~ol start~~div class="5figure" ~~style="list-style-type: decimal;">~~<li>Then open '''Hotspot Enable'''. You can also see the name and password of the generated hotspot in the picture below. Remember them and use them when connecting to the hotspot (if you need to modify the name and password of the hotspot, you need to close Hotspot Enable first. Then you can modify it)</li></ol>

[[File:zero2w-~~img321~~img288.png]]

</div></ol><ol start="69" style="list-style-type: decimal;"><li>~~At this time, you can take out your mobile phone.~~ If ~~everything is normal,~~ you ~~can find~~ are compiling a desktop version of 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~~ image, you ~~can click AndroidAP_7132 to connect~~ also need to select the ~~hotspot~~type of desktop environment. ~~The password can be seen under the '''Hotspot password''' in the picture above~~Currently, only XFCE is maintained, so please select an XFCE type desktop.</li~~></ol~~>

[[File:zero2w-~~img322~~img289.png]]

~~<ol start="7" style="list-style-type~~[[File: ~~decimal;">~~<li>After the connection is successful, it will be displayed as shown below (the interface will be different on different mobile phones, the specific interface is subject to the one displayed on your mobile phone). At this time, you can open a web page on your mobile phone to see if you can access the Internet. If the web page can be opened normally, it means that the '''WIzero2w-~~FI Hotspot''' of the development board can be used normally~~img290.~~</li></ol>~~png]]

~~[[File:zero2w-img323~~You can then select additional packages that need to be installed. Please press the Enter key here to skip directly.~~png]]~~

[[File:zero2w-img291.png]]</ol><~~span id~~ol start="~~how-to-check-the-ip-address-of-the~~10" style="list-~~ethernet~~style-~~port~~type: decimal;"><~~/span~~li>~~== How to check~~ Then the ~~IP address~~ compilation of the ~~Ethernet port ==~~linux image will begin. The general process of compilation is as follows</li>

~~# There is no wired network interface on~~ ::a. Initialize the ~~main board~~ compilation environment of Ubuntu PC and install the ~~development board. We can expand~~ software packages required for the ~~100M Ethernet through a 24pin expansion board~~compilation process.

~~[[File~~:~~zero2w~~:b. Download the source code of u-~~img107.png]]~~boot and linux kernel (if already cached, only update the code)

~~<ol start="2" style="list-style-type~~: ~~decimal;"><li>Then make sure the network port of the expansion board is connected to the router or switch</li><li>Then open '''Settings'''[[File~~:~~zero2w-img324~~c.~~png]]</li><li>Then select '''Network & Internet'''[[File:zero2w~~Compile u-~~img325.png]]</li><li>Then you can see the IP address of the development board's wired network port at the location shown in the picture below.[[File:zero2w~~boot source code and generate u-~~img326.png]]</li></ol>~~boot deb package

~~== Bluetooth connection method ==~~related deb packages

~~# Choose first '''Settings'''~~::e. Make the deb package of linux firmware

~~[[File~~:~~zero2w~~:f. Make the deb package of orangepi-~~img306.png]]~~config tool

~~<ol start="2" style="list-style~~::g. Create a deb package with board-~~type: decimal;"><li>Then select '''Bluetooth'''</li></ol>~~level support

~~[[File~~:~~zero2w~~:h. If you compile the desktop version image, you will also create a desktop-~~img327~~related deb package.~~png]]~~

~~<ol start="3" style="list-style~~::i. Check whether rootfs has been cached. If not, re-~~type: decimal;"><li>Then Open '''Bluetooth Enable'''</li></ol>~~create rootfs. If it has been cached, decompress it directly and use it.

~~[[File~~:~~zero2w-img328~~:j.~~png]]~~Install the deb package generated previously into rootfs

~~<ol start="4" style="list-style-type~~: ~~decimal;"><li>Then click '''Pair new device'''to start scanning~~ :k. Make some specific settings for ~~surrounding Bluetooth devices</li></ol>~~different development boards and different types of images, such as pre-installing additional software packages, modifying system configurations, etc.

~~[[File~~:~~zero2w-img329~~:l. Then create the image file and format the partition. The default type is ext4.~~png]]~~

~~<ol start="5" style="list-style-type~~: ~~decimal;"><li>The searched Bluetooth devices will be displayed under '''Available devices'''</li></ol>~~:m. Then copy the configured rootfs to the mirror partition.

~~[[File~~:~~zero2w-img330~~:n.~~png]]~~Then update initramfs

::o. Finally, write the bin file of u-boot into the image through the dd command.</ol><ol start="611" style="list-style-type: decimal;"><li>~~Then click on~~ After compiling the image, the following message will be displayed<ol style="list-style-type: lower-alpha;"><li>The storage path of the compiled image</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Done building [ '''output/images/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 ~~Bluetooth device you want~~ command to ~~connect to start pairing~~compile the image. ~~When~~ Use the following ~~interface pops up, please use~~ command to start compiling the ~~mouse to select~~ image directly without selecting it through the graphical interface.</li>{| class="wikitable" style="width:800px;" |-| [ o.k. ] Repeat Build Options [ '''~~Pair~~sudo ./build.sh BOARD=orangepizero2w BRANCH=next BUILD_OPT=image RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=yes'''~~option~~]|}</ol></li></ol>

~~[[File:zero2w-img331.png]]~~= '''Instructions for using the Orange Pi OS Arch system''' =

<~~ol start~~span id="~~7" style="list~~orange-pi-os-arch-system-function-~~style~~adaptation-~~type: decimal;~~status"><li>What is tested here is the Bluetooth configuration process between the development board and the Android phone. At this time, the following confirmation interface will pop up on the phone. Click the pairing button on the phone to start the pairing process.</~~li></ol~~span>== Orange Pi OS Arch system function adaptation status ==

~~[[File:zero2w-img332.png]]~~ ~~<ol start~~{| class="8wikitable" style="~~list~~width:800px;text-~~style-type~~align: ~~decimal~~center;">~~<li>After pairing is completed, open~~ |-| '''Motherboard functions'''| '''OPi OS Arch'''|-| '''HDMI video'''| '''OK'''|-| '''HDMI Audio'''| '''OK'''|-| '''Type-C USB2.0 x 2'''| '''OK'''|-| '''TF Card Startup'''| '''OK'''|-| '''WIFI'''| '''OK'~~Paired devices~~''|-| ''' ~~and you will see the paired~~ Bluetooth ~~devices.</li></ol>~~'''| '''OK'''|-| '''LED Light'''| '''OK'''|-| '''40pin GPIO'''| '''OK'''|-| '''40pin I2C'''| '''OK'''|-| '''40pin SPI'''| '''OK'''|-| '''40pin UART'''| '''OK'''|-| '''40pin PWM'''| '''OK'''|-| '''Temperature Sensor'''| '''OK'''|-| '''Hardware watchdog'''| '''OK'''~~[[File:zero2w~~|-~~img333.png]]~~| '''Mali GPU'''| '''<~~ol start="9"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">NO<li/span>At this time, you can use the Bluetooth of your mobile phone to send a picture to the development board. After sending, you can see the following confirmation interface in the Android system of the development board, and then click '''~~Accept~~|-| '''Video codec'''| ''' ~~to start receiving the pictures sent by the mobile phone.~~<~~/li~~span style="color:#FF0000">NO</olspan>'''|}

~~[[File:zero2w-img334.png]]~~ ~~<ol start~~{| class="10wikitable" style="~~list~~width:800px;text-~~style-type~~align: ~~decimal~~center;">~~<li>Pictures received by the Bluetooth system of the development~~ |-| '''24pin expansion board ~~Android system can be viewed in~~ function'''| '''OPi OS Arch'''|-| '''100M network port'''| '''OK'''|-| '''~~Received files~~100M Ethernet port light'''~~.</li></ol>~~| '''OK'''~~[[File:zero2w~~|-~~img335~~| '''USB2.~~png]]~~0 HOST x 2'''| '''OK'''~~<span id="how~~|-to| '''Infrared reception'''| '''OK'''|-~~set~~| '''Headphone audio playback'''| '''OK'''|-~~usb0~~| '''On/off button'''| '''OK'''|-to| '''LRADC''' '''Custom buttons x 2'''| '''OK'''|-~~host~~| '''TV-~~mode-1~~OUT'''| '''NO'''~~== How to set USB0 to HOST mode ==~~|}

~~As shown in the figure below, there are two Type~~<span id="orange-C interfaces on the motherboard of the development board: USB0 and USB1. Both of these interfaces can be used to power the development board, and they can also be used as USB2.0 HOST interfaces. The difference between USB0 and USB1 is that in addition to being set to HOST mode, USB0 can also be set to Device mode, while USB1 only has HOST mode.pi-os-arch-system-user-guide-instructions">

~~[[File:zero2w-img160.png]]~~== Orange Pi OS Arch System User Guide Instructions ==

~~USB0~~ First of all, please note that the ~~Android12 TV~~ OPi OS Arch system ~~released by Orange Pi is set to Device mode by~~ does not have a defaultorangepi user and password, so ~~when there~~ you cannot directly log in remotely through the serial port and ssh after the system is ~~no need to use USB0 Device mode~~ started after burning (~~ADB function needs to ensure that USB0 is in Device mode~~not even the root user)~~, it~~ . This is ~~recommended to use USB0 for power supply, so that USB1 can be directly used to connect USB devices~~ different from Ubuntu and Debian systems.

~~If you want to use USB0 to connect USB devices~~When the OPi OS Arch system is started for the first time, you need to ~~set USB0 to HOST mode~~connect an HDMI display and then initialize the system settings through the user wizard (including creating a new user name and setting a password). The ~~method is~~ setup steps of the user wizard are as follows:

<li>~~Run~~ After burning the system, when you start it for the ~~following command to set USB0 to HOST mode:~~first time and enter the desktop, you will see the user wizard program shown in the figure below.</lip><~~/ol~~div class="figure">

~~apollo~~[[File:zero2w-~~p2:/ # '''cat /sys/devices/platform/soc@3000000/soc@3000000\:usbc0@0/usb_host'''~~img293.png]]

~~host_chose finished!~~</div></li><li>First you need to select the language you want<div class="figure">

~~apollo~~[[File:zero2w-~~p2:/ #~~img294.png]]

<~~ol start="2" style="list-style-type: lower-alpha;"~~/div></li><li>~~Run~~ After selecting the language, the ~~following command to~~ user wizard will immediately switch ~~back~~ to ~~Device mode~~the corresponding language interface, as shown below in Chinese</lip><~~/ol~~div class="figure">

~~apollo~~[[File:zero2w-~~p2:/ # '''cat /sys/devices/platform/soc@3000000/soc@3000000\:usbc0@0/usb_device'''~~img295.png]]

~~device_chose finished!~~</div></li><li>Then select the area<div class="figure">

~~apollo~~[[File:zero2w-~~p2:/ #~~img296.png]]

<~~ol start="3" style="list-style-type: lower-alpha;"~~/div></li><li>~~The command to view~~ Then select the ~~current mode of USB0 is~~keyboard model</lip><~~/ol~~div class="figure">

~~apollo~~[[File:zero2w-~~p2:/ # '''cat /sys/devices/platform/soc@3000000/soc@3000000\:usbc0@0/otg_role'''~~img297.png]]

~~usb_host~~</div></li><li>Then create a new username and set a password<div class="figure">

~~== How to use USB camera ==~~img298.png]]

~~# First insert the USB (UVC protocol) camera into the USB interface of the development board~~</div></li>~~# If~~ <li>Then make sure there is no problem with the ~~USB camera is recognized normally~~selection, and then click the ~~corresponding video device node will be generated under~~ install '''button'''</~~dev~~p><div class="figure">

~~console~~[[File:~~/ # '''ls /dev/video0'''~~zero2w-img299.png]]

</~~dev~~div></~~video0~~li><li>Then wait for the installation to complete<div class="figure">

~~<ol start="3" style="list-style~~[[File:zero2w-~~type: decimal;">~~<li>Then make sure that the adb connection between the Ubuntu PC and the development board is normal. For how to use adb, please refer to the instructions in the section "'''How to use ADB'''"img300.~~</li><li>Download the USB camera test APP from the '''official tool''' on the development board information download page</li></ol>~~png]]

</div></li>

<li>After the installation is complete, you need to click the '''Finish''' button to restart the system.

[[File:zero2w-~~img336~~img301.png]]

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

[[File:zero2w-~~img337~~img302.png]]

</div>

<~~ol start="5" style="list-style-type: decimal;"~~p>~~<li>Then~~ At this point, you can use the ~~adb command~~ newly created username and password to log in to ~~install~~ the ~~USB camera test APP into~~ OPi OS system through the ~~Android system. Of course, you can also use a USB disk copy to install it~~serial port or ssh.</li></ol>

~~test@test:~$ '''adb install usbcamera.apk'''~~== How to set DT overlays ==

~~<ol start="6" style="list~~The multiplexing functions such as I2C/SPI/UART/PWM in the 40-~~style-type: decimal;"><li>After installation~~pin development board are turned off by default in the kernel's dts, ~~you can see~~ and the ~~startup icon of the USB camera~~ corresponding DT overlays need to be manually turned on ~~the Android desktop~~before they can be used.~~</li></ol>~~

~~[[File~~The method to open DT overlays in OPi OS Arch system is as follows:~~zero2w-img338.png]]~~

~~<ol start="7" style="list-style-type: decimal;"><li>Then double-click to~~ # First open the ~~USB camera APP and you can see the output video of the USB camera.<~~'''/boot/~~li><~~extlinux/~~ol>~~extlinux.conf''' configuration file

~~<~~pc ~]$ '''sudo vim /boot/extlinux/~~span>~~extlinux.conf'''~~== Android system ROOT description ==~~|}

<ol start="2" style="list-style-type: decimal;"><li>Then open the corresponding configuration by adding '''~~The Android system released by Orange Pi has been ROOT and can be tested using the following method~~FDTOVERLAYS''' '''/dtbs/allwinner/overlay/xxx.dtbo''' in '''/boot/extlinux/extlinux.conf'''</li>

{| class="wikitable" style="background-color:# ~~Download from the~~ ffffdc;width:800px;" |-| <big>'''~~official tool~~Note that xxx.dtbo in FDTOVERLAYS /dtbs/allwinner/overlay/xxx.dtbo needs to be replaced with the specific dtbo configuration, please do not copy it.''' ~~on the development board data download page~~ </big>|}{| class="wikitable" style="width:800px;" |-| [orangepi@orangepi-pc ~]$ '''~~rootcheck~~sudo vim /boot/extlinux/extlinux.~~apk~~conf'''

~~<div class="figure">~~LABEL Orange Pi

~~[[File:zero2w-img336.png]]~~KERNEL /Image

<FDT /~~div><div class="figure">~~dtbs/allwinner/sun50i-h616-orangepi-zero2w.dtb

~~[[File~~'''FDTOVERLAYS /dtbs/allwinner/overlay/xxx.dtbo''' #Configuration that needs to be added|}</ol><ol start="3" style="list-style-~~img339~~type: decimal;"><li>The storage path of xxx.~~png]]~~dtbo in the OPi OS Arch image is as follows. Please note that not all dtbo under this path can be used.{| class="wikitable" style="width:800px;" |-| '''/boot/dtbs/allwinner/overlay/'''|}</li><li>The DT overlays configuration that can be used by the development board is as follows</li>

~~</div><ol start~~{| class="2wikitable" style="~~list~~width:800px;text-~~style-type~~align: ~~decimal~~center;">~~<li>Then make sure that the adb connection between the Ubuntu PC and~~ |-| '''Functions on the development board ~~is normal~~'''| '''Corresponding DT overlays configuration'''|-| '''40pin - i2c0'''| '''sun50i-h616-pi-i2c0. ~~For how to use adb, please refer to the instructions in the section "~~dtbo'''|-| '''40pin - i2c1'''~~How to use ADB~~| '''~~"~~sun50i-h616-pi-i2c1.~~</li>~~dtbo'''|-| '''40pin - i2c2'''~~<li>Then use the adb command to install rootcheck~~| '''sun50i-h616-pi-i2c2.~~apk into the Android system~~dtbo'''|-| '''40pin - uart2'''| '''sun50i-h616-pi-uart2. ~~Of course, you can also use a USB disk copy to install it~~dtbo'''|-| '''40pin - uart3'''| '''sun50i-h616-pi-uart3.~~</li></ol>~~dtbo'''|-| '''40pin - uart4'''~~test@test:~$~~ | '''~~adb install rootcheck~~sun50i-h616-pi-uart4.~~apk~~dtbo'''|-| '''40pin - uart5'''~~<ol start="4" style="list~~| '''sun50i-h616-~~style~~ph-~~type: decimal;"><li>After installation, you can see the startup icon of the ROOT test tool on the Android desktop~~uart5.~~</li></ol>~~dtbo'''|-~~[[File:zero2w~~| '''40pin - pwm1'''| '''sun50i-h616-pi-~~img340~~pwm1.~~png]]~~dtbo'''|-~~<ol start="5" style="list~~| '''40pin - pwm2'''| '''sun50i-h616-pi-~~style~~pwm2.dtbo'''|-~~type: decimal;"><li>The display interface after opening the~~ | '''~~ROOT test tool~~40pin - pwm3''' ~~for the first time is as shown below</li></ol>~~| '''sun50i-h616-pi-pwm3.dtbo'''~~[[File:zero2w~~|-~~img341.png]]~~| '''40pin - pwm4'''~~<ol start="6" style="list~~| '''sun50i-h616-pi-~~style~~pwm4.dtbo'''|-~~type: decimal;"><li>Then you can click~~ | '''40pin - spi1 cs0''~~CHECK NOW~~'| '' ~~to start checking the ROOT status of the Android system~~'sun50i-h616-spi1-cs0-spidev. ~~After the check is completed, the display is as follows. You can see that the Android system has obtained ROOT permissions.</li></ol>~~dtbo'''|-| '''40pin - spi1 cs1'''~~[[File:zero2w~~| '''sun50i-h616-spi1-cs1-~~img342~~spidev.~~png]]~~dtbo'''|-| '''40pin - spi1 cs0 cs1'''~~<span id="how~~| '''sun50i-h616-spi1-tocs0-~~use~~cs1-~~miracastreceiver~~spidev.dtbo'''|-| '''设Set USB0 toHost mode'''| '''sun50i-~~cast~~h616-usb0-host.dtbo'''|-| '''Turn off thegreen LED light'''| '''sun50i-~~mobile~~h616-~~phone~~zero2w-~~screen~~disable-led.dtbo'''|-| '''How toclose the UART0 debugging serial port'''| '''sun50i-~~the~~h616-~~development~~disable-~~board">~~uart0.dtbo'''|}</~~span~~ol>~~== How to use MiracastReceiver to cast the mobile phone screen to the development board ==~~ <ol start="5" style="list-style-type: decimal;"><li>~~First, please make sure that both the development board and the mobile phone are connected~~ If you need to open multiple configurations at the same ~~WIFI hotspot. For~~ time, just add the ~~method~~ paths of ~~connecting the development board to WIFI, please refer to~~ multiple configurations directly after '''~~the instructions in the WI-FI connection method~~FDTOVERLAYS.'''~~</li><li>Then open~~ For example, the ~~'''MiracastReceiver'''application in the Android system~~ configuration of opening i2c1 and uart5 at the ~~development board[[File:zero2w-img343.png]]</li><li>The interface after '''MiracastReceiver''' is opened~~ same time is as follows</pli>~~<div~~ {| class="~~figure~~wikitable" style="width:800px;">|-| [~~[File:zero2w~~orangepi@orangepi-~~img344~~pc ~]$ '''sudo vim /boot/extlinux/extlinux.~~png]]~~conf'''

~~</div></li>~~<li>Then find the screen mirroring function in the phone settings. Here we take '''Xiaomi 12S Pro mobile phone''' as an example. Please research other brands of mobile phones by yourself. As shown in the picture below, click the button in the red box to open the screen mirroring function of the phone.~~[[File:zero2w-img345.png]]</li>~~<li>After waiting for a period of time, you will be able to see the searched connectable devices on your mobile phone, and then we can select the device corresponding to the development board to connect.~~[[File:zero2w-img346.png]]</li><li>Then the selection box shown in the figure below will pop up in the '''MiracastReceiver''' application interface of the development board. Here we can select '''Accept'''[[File:zero2w-img347.png]]</li><li>Then you can see the content of the mobile phone screen on the HDMI screen connected to the development board[[File:zero2w-img348.png]]</li></ol>~~LABEL Orange Pi

~~<~~KERNEL /~~span>== Method of turning on and off the machine through buttons or infrared remote control ==~~Image

~~We can turn off or turn on the Android system of the development board through the power on~~FDT /~~off button or infrared remote control. However, it should be noted that there is no power on~~dtbs/allwinner/~~off button and infrared receiver on the main board of the development board, and it needs to be expanded through a 24pin expansion board~~sun50i-h616-orangepi-zero2w.dtb

~~[[File~~'''FDTOVERLAYS /dtbs/allwinner/overlay/sun50i-h616-pi-i2c1.dtbo /dtbs/allwinner/overlay/sun50i-h616-~~img107~~ph-uart5.~~png]]~~dtbo'''|}</ol><ol start="6" style="list-style-type: decimal;">~~The location of~~ <li>After setting, you need to restart the ~~power button on~~ system for the ~~24pin expansion board is as shown in the figure below~~configuration to take effect.</li>{| class="wikitable" style="width:800px;" |-| [~~[File:zero2w~~orangepi@orangepi-~~img269.png]~~pc ~]$ '''sudo reboot'''|}</ol>

~~The location of the infrared remote control power button is as follows:~~== How to install software ==

~~[[File:zero2w-img349~~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.~~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 {| class="wikitable" style="width:800px;" |-| [orangepi@orangepi-pc ~]$ '''OKsudo pacman -Syy vim''' ~~to shut down the Android system.~~|}

~~[[File:zero2w~~

~~After shutting down, press and hold the power button or the power button on the infrared remote control again to turn it on.~~= '''Android 12 TV system usage instructions''' =

== ~~40pin interface GPIO, UART, SPI test~~ Supported Android versions ==

{| class="wikitable" style="width:800px;text-align: center;"|-| Android Version| Kernel version|-| '''~~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~~Android 12 TV Version'''| '''linux5.4'''|}

==~~= 40pin GPIO port test method =~~Android 12 TV function adaptation status ==

~~# First open wiringOP APP on the desktop~~ ~~[[File:zero2w-img351.png]]~~ ~~<ol start~~{| class="2wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>Then click the '''GPIO_TEST''' button to open the GPIO test interface</li></ol>~~ ~~[[File:zero2w~~text-~~img352.png]]~~ ~~<ol start="3" style="list-style-type~~align: ~~decimal~~center;">~~<li>The GPIO test interface is as shown in the figure below. The two rows of '''CheckBox''' buttons on the left have a one~~|-~~to-one correspondence with the 40pin pins. When the~~ | '''~~CheckBox~~Motherboard functions''' ~~button is checked, the corresponding GPIO pin will be set to~~ | '''~~OUT~~Android12 TV''' ~~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~~HDMI video''' ~~button, you can get information such as wPi number, GPIO mode, pin level, etc.; when you click the~~| '''~~BLINK ALL GPIO~~OK''' ~~button, all GPIO ports will cycle through outputting high and low levels. This function can be used to test all the 40pin pins. GPIO port.</li></ol>~~ ~~[[File:zero2w~~|-~~img353.png]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then click the~~ | '''~~GPIO READALL~~HDMI Audio''' ~~button, and the output information is as shown below:</li></ol>~~ ~~<div class="figure">~~ ~~[[File:zero2w-img354.png]]~~ ~~</div><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~~OK'''~~, it means the setting High level success.</li></ol>~~ ~~[[File:zero2w~~|-~~img355.png]]~~ ~~<ol start="6" style="list-style-type: decimal;"><li>Then click the~~ | '''~~GPIO READALL~~Type-C USB2.0 x 2''' ~~button and you can see that the current pin 12 mode is~~ | '''~~OUT~~OK''' ~~and the pin level is high level.</li></ol>~~ ~~[[File:zero2w~~|-~~img356.png]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>Click the '~~| ''~~CheckBox~~'TF card startup'' ~~button in the picture below again to uncheck it, and pin 12 will be set to low level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is~~ '~~''0v''', it means the low level setting is successful.</li></ol>~~ ~~[[File:zero2w-img357.png]]~~ ~~<ol start="8" style="list-style-type: decimal;"><li>Then click the~~ | '''~~GPIO READALL~~OK''' ~~button and you can see that the current pin 12 mode is OUT and the pin level is low level.</li></ol>~~ ~~[[File:zero2w-img358.png]]~~ ~~=== 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. ~~{| class="wikitable"~~

|-

| '''~~GPIO序号~~WIFI'''| '''~~GPIO'''| '''功能'''| '''引脚'''~~|~~| '''引脚'''| '''功能'''| '''GPIO'''| '''GPIO序号~~OK'''

|-

| ~~style="text-align: left;"|| style="text-align: left;"|| '''3.3V'''| '''1''~~'|| '''2Bluetooth'''| '''5VOK'''~~| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~264~~USB Camera'''| '''~~PI8~~OK'''~~| '''TWI1-SDA'''| '''3'''~~|~~| '''4'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~263~~LED Light'''| '''~~PI7~~OK'''| ~~'''TWI1~~-~~SCL'''| '''5'''~~|| '''640pin GPIO'''| '''~~GND~~OK'''~~| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~269~~40pin I2C'''| '''~~PI13'''| '''PWM3'''| '''7'''~~|~~| '''8'''| '''UART0_TX'''| '''PH0'''| '''224~~OK'''

|-

~~| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''9'''~~|~~| '''10'''| '''UART0_RX'''~~| '''~~PH1~~40pin SPI1'''| '''~~225~~OK'''

|-

| '''~~226~~40pin UART'''| '''~~PH2'''| '''UART5_TX'''| '''11'''~~|~~| '''12'''| style="text-align: left;"|| '''PI1'''| '''257~~OK'''

|-

| '''~~227~~40pin PWM'''| '''~~PH3~~OK'''~~| '''UART5_RX'''| '''13'''~~|~~| '''14'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~261~~Temperature Sensor'''| '''~~PI5~~OK'''| ~~'''UART2_TX'''| '''15'''~~|~~| '''16'''| '''PWM4'''~~-| '''~~PI14~~Hardware watchdog'''| '''~~270~~OK'''

|-

~~| style="text-align: left;"|| style="text-align: left;"|| '''3.3V'''| '''17'''~~|~~| '''18'''| style="text-align: left;"|~~| '''~~PH4~~Mali GPU'''| '''~~228~~OK'''

|-

| '''~~231~~Video codec'''| '''~~PH7~~OK'''| ~~'''SPI1_MOSI'''| '''19'''~~}|{| ~~'''20'''| '''GND'''| style~~class="~~text-align: left;~~wikitable"|| style="width:800px;text-align: ~~left~~center;"|

|-

| '''~~232~~24pin Expansion board function'''| '''~~PH8'''| '''SPI1_MISO'''| '''21'''~~|~~| '''22'''| '''UART2_RX'''| '''PI6'''| '''262~~Android12 TV'''

|-

| '''~~230~~100M network port'''| '''~~PH6'''| '''SPI1_CLK'''| '''23'''~~|~~| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229~~OK'''

|-

~~| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''25'''~~|~~| '''26'''| '''SPI1_CS1'''~~| '''~~PH9~~100M Ethernet port light'''| '''~~233~~OK'''

|-

| '''~~266~~USB2.0 HOST x 2'''| '''~~PI10'''| '''TWI2-SDA'''| '''27'''~~|~~| '''28'''| '''TWI2-SCL'''| '''PI9'''| '''265~~OK'''

|-

| '''~~256~~Infrared reception'''| '''~~PI0~~OK'''~~| style="text-align: left;"|| '''29'''~~|~~| '''30'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~271~~Headphone audio playback'''| '''~~PI15'''| style="text-align: left;"|| '''31'''~~|~~| '''32'''| '''PWM1'''| '''PI11'''| '''267~~OK'''

|-

| '''~~268~~On/off button'''| '''~~PI12~~OK'''~~| '''PWM2'''| '''33'''~~|~~| '''34'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~258~~LRADC''' '''Custom buttons x 2'''| '''~~PI2~~OK, The default setting is the volume up and down keys.'''| ~~style="text~~-~~align: left;"|~~| '''35TV-OUT'''|| '''36OK'''| } == Onboard LED light display instructions == {| class="wikitable" style="width:800px;text-align: ~~left~~center;"|~~| '''PC12'''| '''76'''~~

|-

~~| '''272'''~~

~~| '''PI16'''~~

~~| style="text-align: left;"|~~

~~| '''37'''~~

|

|-

| ~~style="text-align: left;"|| style="text-align: left;"|| '''GND~~'''| Kernel boot to enter the system'''~~39'''~~|~~| '''40'''| style="text-align: left;"|~~| '''~~PI3~~on'''| '''~~259~~on'''

|}

<~~ol start~~span id="~~2" style="list~~how-to-return-to-the-previous-interface-~~style~~in-~~type: decimal;~~android"><li/span>~~The device node corresponding~~ == How to return to ~~uart2 is '''/dev/ttyAS2''', and~~ the ~~device node corresponding to uart5 is'''/dev/ttyAS5'''</li></ol>~~previous interface in Android ==

~~apollo~~We generally use the mouse and keyboard to control the Android system of the development board. When entering certain interfaces and need to return to the previous interface or desktop, we can only return by right-p2:/ # ls /dev/ttyAS*clicking the mouse, and the keyboard cannot return.

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

~~<ol start="3" style="list~~[[File:zero2w-~~style-type: decimal;"><li>First open wiringOP APP on the desktop</li></ol>~~img303.png]]

~~[[File:zero2w~~== How to use ADB ==

<~~ol start~~span id="~~4" style="list~~use-network-connection-~~style~~adb-~~type: decimal;~~debugging">~~<li>Then click the '''UART_TEST'''button to open the UART test interface~~</~~li></ol~~span>=== Use network connection adb debugging ===

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~zero2w~~800px;" |-~~img359~~| <big>'''Using network adb does not require a USB Typc C interface data cable to connect the computer and the development board. Instead, it communicates through the network, so first make sure that the development board's wired or wireless network is connected, and then obtain the IP address of the development board. Next To be used.~~png]]~~'''</big>|}

~~<ol start="5" style="list-style-type: decimal;"><li>The serial~~ # Make sure the '''service.adb.tcp.port ~~test interface~~ ''' of ~~wiringOP~~ the Android system is ~~as shown in the figure below</li></ol>~~set to 5555 port number

~~[[File~~:~~zero2w~~:{| class="wikitable" style="width:800px;" |-| apollo-~~img360~~p2:/ # '''getprop | grep "adb.~~png]]~~tcp"'''

[service.adb.tcp.port]: [5555]|} <ol start="62" style="list-style-type: decimal;"><li>~~Then select the~~ If '''~~/dev/ttyAS2~~service.adb.tcp.port''' ~~or'''/dev/ttyAS5''' node~~ is not set, you can use the following command in the ~~selection box~~serial port to set the port number of the network adb</pli>~~[[File~~{| class="wikitable" style="width:~~zero2w~~800px;" |-~~img361.png]]<~~| apollo-p2:/~~p></li><li>Enter the baud rate you want to set in the edit box, and then click the~~ # '''~~OPEN''' button to open the uart node~~setprop service.adb.tcp. ~~After the opening is successful, the~~ port 5555'''~~OPEN~~ apollo-p2:/ # ''' ~~button becomes unselectable, and the~~ stop adbd'''~~CLOSE~~ apollo-p2:/ # ''' ~~button and~~ start adbd'''~~SEND''' button become selectable.~~|}</pol><ol start="3" style="list-style-type: decimal;"></li>Install adb tool on Ubuntu PC</olli>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt-get update'''

~~[[File~~test@test:~~zero2w~~~$ '''sudo apt-~~img362~~get install -y adb'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then connect network adb on Ubuntu PC</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''adb connect 192.~~png]]~~168.1.xxx:5555''' '''(Need to be modified to the IP address of the development board)'''

~~<ol start="8" style="list-style-type: decimal;"><li>~~~~Then use Dupont wire to short the rx and tx pins of uart</li><li>Then you can enter a paragraph of characters in the send edit box below and click the '''SEND''' button to start sending.~~* daemon not running; starting now at tcp:5037</p~~></li></ol~~>

~~[[File:zero2w-img363.png]]~~* daemon started successfully

~~<ol start="10" style="list-style-type~~connected to 192.168.1.xxx: ~~decimal;"><li>If everything is normal, the received string will be displayed in the receiving box</li></ol>~~5555

~~[[File:zero2w-img364.png]]~~

~~=== 40pin SPI~~ @test ~~method ===~~:~$ '''adb devices'''

~~# 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~~List of devices attached

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 number~~adb shell''' apollo-p2:/ #| ~~'''GPIO'''~~}~~| '''Function'''~~</ol>~~| '''pin'''~~|~~| '''pin'''~~=== Use data cable to connect adb debugging ===~~| '''Function'''| '''GPIO'~~# 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.~~| '''GPIO serial number'''~~|::[[File:zero2w-img304.png]] [[File:zero2w-img305.png]] ~~| style~~<ol start="~~text-align: left;~~2"|| style="~~text~~list-~~align~~style-type: ~~left~~decimal;"|>~~| '''3.3V'''~~<li>Install adb tool on Ubuntu PC</li>{| ~~'''1'''~~|~~| '''2'''| '''5V'''| style~~class="~~text-align: left;~~wikitable"|| style="~~text-align~~width: ~~left~~800px;"|

|-

| test@test:~$ '''~~264~~sudo apt-get update'''~~| '''PI8'''~~| test@test:~$ '''~~TWI1~~sudo apt-get install -~~SDA~~y adb'''| ~~'''3'''~~}|</ol>~~| '''4'''| '''5V'''~~| <ol start="3" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|><li>Check whether the ADB device is recognized</li>{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|

|-

| test@test:~$ '''~~263~~adb devices'''~~| '''PI7'''| '''TWI1-SCL'''~~List of devices attached~~| '''5'''~~|4c00146473c28651dd0 device| ~~'''6'''~~}~~| '''GND'''~~</ol>| <ol start="4" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|><li>Then you can log in to the android system through adb shell on Ubuntu PC</li>{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|

|-

| test@test:~$ '''~~269~~adb shell''' apollo-p2:/ $| }</ol> == View how to set HDMI display resolution == <ol style="list-style-type: decimal;"><li>Enter first '''~~PI13~~Settings'''[[File:zero2w-img306.png]]</li>| <li>Then select '''~~PWM3~~Device Preferences'''| [[File:zero2w-img307.png]]</li><li>Then select '''7Display & Sound'''|[[File:zero2w-img308.png]]</li>| <li>Then select '''8Advanced display settings'''[[File:zero2w-img309.png]]</li>| <li>Then select '''~~UART0_TX~~HDMI output mode'''[[File:zero2w-img310.png]]</li><li>Then you can see the list of resolutions supported by the monitor. At this time, clicking the corresponding option will switch to the corresponding resolution. Please note that different monitors may support different resolutions. If you connect it to a TV, you will generally see more resolution options than the picture below.[[File:zero2w-img311.png]]</li><li>The HDMI output of the development board supports 4K display. When connected to a 4K TV, you can see the 4K resolution option.[[File:zero2w-img312.png]]</li></ol> === HDMI to VGA display test === <ol style="list-style-type: decimal;"><li>First you need to prepare the following accessories<ol style="list-style-type: lower-alpha;"><li>HDMI to VGA converter</li> [[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;"><li>A monitor or TV that supports VGA interface</li></ol></li></ol> <ol start="2" style="list-style-type: decimal;"><li>HDMI to VGA display test is as follows</li> [[File:zero2w-img313.png]]~~| '''PH0'''~~{| ~~'''224'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

~~| style="text-align: left;"~~|~~| style="text-align: left;"|~~| <big>'''~~GND~~When using HDMI to VGA display, the development board and the Android system of the development board do not need to make any settings. You only need the Mini HDMI interface of the development board to display normally. So if there is a problem with the test, please check whether there is a problem with the HDMI to VGA converter, VGA cable and monitor.'''</big>| ~~'''9'''~~}|</ol>~~| '''10'''~~~~| '''UART0_RX'''| '''PH1'''| '''225'''~~|== WI-FI connection method ==~~| '''226'''~~| # Choose first '''~~PH2~~Settings'''~~| '''UART5_TX'''| '''11'''~~::[[File:zero2w-img306.png]]|~~| '''12'''~~| <ol start="2" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|>| <li>Then select '''~~PI1~~Network & Internet'''</li>~~| '''257'''~~|[[File:zero2w-img314.png]]~~| '''227'''~~</ol>~~| '''PH3'''~~<ol start="3" style="list-style-type: decimal;">~~| '''UART5_RX'''~~<li>Then turn on WI-FI</li>~~| '''13'''~~|[[File:zero2w-img315.png]]~~| '''14'''~~</ol>~~| '''GND'''| style~~<ol start="~~text-align: left;~~4"|| style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|>|<li>After turning on WI-| FI, you can see the searched signals under '''~~261~~Available networks'''.</li>~~| '''PI5'''| '''UART2_TX'''| '''15'''~~[[File:zero2w-img316.png]]|</ol>~~| '''16'''| '''PWM4'''| '''PI14'''| '''270'''~~|-| <ol start="5" style="~~text~~list-~~align~~style-type: ~~left~~decimal;"|><li>After selecting the WI-FI you want to connect to, the password input interface shown below will pop up.</li> ~~| style~~<div class="~~text-align: left;~~figure"|> ~~| '''3~~[[File:zero2w-img317.~~3V'''~~png]]~~| '''17'''~~|</div></ol>~~| '''18'''~~| <ol start="6" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|>~~| '''PH4'''| '''228'''~~|<li>Then use the keyboard to enter the password corresponding to the WI-FI, and then use the mouse to click the Enter button on the virtual keyboard to start connecting to the WI-FI.</li>~~| '''231'''| '''PH7'''~~<div class="figure">~~| '''SPI1_MOSI'''| '''19'''~~|[[File:zero2w-img318.png]]~~| '''20'''| '''GND'''~~</div></ol>~~| style~~<ol start="~~text-align: left;~~7"|| style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|>|<li>The display after successful WI-FI connection is as shown below</li>~~| '''232'''| '''PH8'''~~[[File:zero2w-img319.png]]~~| '''SPI1_MISO'''~~</ol>~~| '''21'''~~|~~| '''22'''| '''UART2_RX'''| '''PI6'''| '''262'''~~|== How to use WI-FI hotspot ==~~| '''230'''| '''PH6'''~~# First, please make sure that the Ethernet port is connected to the network cable and can access the Internet normally.| # Then select '''~~SPI1_CLK~~Settings'''~~| '''23'''~~|::[[File:zero2w-img306.png]]~~| '''24'''| '''SPI1_CS0'''~~<ol start="3" style="list-style-type: decimal;">| <li>Then select '''~~PH5~~Network & Internet'''</li>~~| '''229'''~~|[[File:zero2w-img314.png]]</ol>~~| style~~<ol start="~~text-align: left;~~4"|| style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|>| <li>Then select '''~~GND~~WIFI hotspot'''</li>~~| '''25'''~~|[[File:zero2w-img320.png]]~~| '''26'''~~</ol>~~| '''SPI1_CS1'''~~<ol start="5" style="list-style-type: decimal;">| <li>Then open '''~~PH9~~Hotspot Enable'''. You can also see the name and password of the generated hotspot in the picture below. Remember them and use them when connecting to the hotspot (if you need to modify the name and password of the hotspot, you need to close Hotspot Enable first. Then you can modify it)</li>~~| '''233'''~~|[[File:zero2w-img321.png]]~~| '''266'''| '''PI10'''~~</ol>~~| '''TWI2~~<ol start="6" style="list-style-~~SDA'''~~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 ('''27here AndroidAP_7132'''|| ) shown under the '''28Hotspot name'''~~| '''TWI2~~in the picture above in the WI-~~SCL~~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 '''~~| '''PI9~~Hotspot password'''in the picture above.</li>~~| '''265'''~~|[[File:zero2w-img322.png]]~~| '''256'''~~</ol>~~| '''PI0'''~~| <ol start="7" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|>| <li>After the connection is successful, it will be displayed as shown below (the interface will be different on different mobile phones, the specific interface is subject to the one displayed on your mobile phone). At this time, you can open a web page on your mobile phone to see if you can access the Internet. If the web page can be opened normally, it means that the '''29WI-FI Hotspot'''of the development board can be used normally.</li>|~~| '''30'''~~[[File:zero2w-img323.png]]~~| '''GND'''~~</ol>~~| style~~ ~~| style~~=~~"text-align~~= How to check the IP address of the Ethernet port == # There is no wired network interface on the main board of the development board. We can expand the 100M Ethernet through a 24pin expansion board. ::[[File: ~~left;"|~~|zero2w-img107.png]]~~| '''271'''| '''PI15'''~~| <ol start="2" style="~~text~~list-~~align~~style-type: ~~left~~decimal;"|><li>Then make sure the network port of the expansion board is connected to the router or switch</li>| <li>Then open '''31Settings'''|[[File:zero2w-img324.png]]</li>| <li>Then select '''32Network & Internet'''~~| '''PWM1''~~[[File:zero2w-img325.png]]</li><li>Then you can see the IP address of the development board's wired network port at the location shown in the picture below.~~| '''PI11'''~~[[File:zero2w-img326.png]]</li></ol>~~| '''267'''~~|~~| '''268'''| '''PI12'''~~== Bluetooth connection method ==~~| '''PWM2'''~~| # Choose first '''33Settings'''|~~| '''34'''~~::[[File:zero2w-img306.png]]~~| '''GND'''| style~~<ol start="~~text-align: left;~~2"|| style="~~text~~list-~~align~~style-type: ~~left~~decimal;"||->| <li>Then select '''~~258~~Bluetooth'''</li> ~~| '''PI2'''~~[[File:zero2w-img327.png]]</ol>| <ol start="3" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|>| <li>Then Open '''35Bluetooth Enable'''</li>|~~| '''36'''~~[[File:zero2w-img328.png]]</ol>| <ol start="4" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|~~| '''PC12'''~~>| <li>Then click '''76Pair new device'''|}to start scanning for surrounding Bluetooth devices</li>

[[File:zero2w-img329.png]]</ol><ol start="25" style="list-style-type: decimal;"><li>The ~~device node corresponding to SPI1 CS0 is '~~searched Bluetooth devices will be displayed under ''~~/dev/spidev1.0~~'~~'', and the device node corresponding to SPI1 CS1 is '''/dev/spidev1.1~~Available devices'''</li~~></ol~~>

~~apollo~~[[File:zero2w-img330.png]]</ol><ol start="6" style="list-p2style-type:~~/ #~~ decimal;"><li>Then click on the Bluetooth device you want to connect to start pairing. When the following interface pops up, please use the mouse to select the '''ls /dev/spidev1.*Pair'''option</li>

~~'''~~[[File:zero2w-img331.png]]</~~dev/spidev1~~ol><ol start="7" style="list-style-type: decimal;"><li>What is tested here is the Bluetooth configuration process between the development board and the Android phone. At this time, the following confirmation interface will pop up on the phone. Click the pairing button on the phone to start the pairing process.0 </~~dev/spidev1.1'''~~li>

[[File:zero2w-img332.png]]</ol><ol start="38" style="list-style-type: decimal;"><li>~~Here~~ After pairing is ~~a demonstration to test the SPI1 interface through the~~ completed, open '''~~w25qxx~~Paired devices''' ~~module. First, connect~~ and you will see the ~~w25qxx module to the SPI1 interface~~paired Bluetooth devices.</li~~></ol~~>

~~'''It doesn't matter if there is no w25qxx module~~[[File:zero2w-img333.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>At this time, ~~because there is~~ you can use the Bluetooth of your mobile phone to send a ~~SPIFlash on~~ picture to the development board ~~connected to SPI0~~. After sending, ~~and~~ you can see the ~~configuration of SPI0 is also turned on by default~~ following confirmation interface in the Androidsystem of the development board, ~~so we can also directly use the onboard SPIFlash for testing.~~and then click '''Accept'''to start receiving the pictures sent by the mobile phone.</li>

[[File:zero2w-img334.png]]</ol><ol start="410" style="list-style-type: decimal;"><li>~~Then open wiringOP APP on~~ Pictures received by the ~~desktop~~Bluetooth system of the development board Android system can be viewed in '''Received files'''.</li~~></ol~~>

[[File:zero2w-~~img351~~img335.png]]</ol>

~~<ol start~~=~~"5" style~~=~~"list-style-type: decimal;"><li>Then click the '''SPI_TEST''' button~~ How to ~~open the SPI test interface</li></ol>~~set USB0 to HOST mode ==

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

~~<ol start="6" style="list-style~~[[File:zero2w-~~type: decimal;">~~<li>Then select the spi device node in the upper left corner. If you test the onboard SPIFlash directly, just keep the default '''/dev/spidev0.0'''. If the '''w25qxx''' module is connected to the 40pin spi1 cs0, then please select'''/dev/spidev1.0''', if the w25qxx module is connected to the 40pin spi1 cs1, then please select '''/dev/spidev1img160.~~1'''<div class="figure">~~png]]

~~[[File:zero2w-img366~~USB0 of the Android12 TV system released by Orange Pi is set to Device mode by default, so when there is no need to use USB0 Device mode (ADB function needs to ensure that USB0 is in Device mode), it is recommended to use USB0 for power supply, so that USB1 can be directly used to connect USB devices .~~png]]~~

~~</div></li><li>Then click the '''OPEN''' button~~ If you want to ~~initialize the SPI</li></ol>~~use USB0 to connect USB devices, you need to set USB0 to HOST mode. The method is as follows:

~~[[File~~<ol style="list-style-type: lower-alpha;"><li>Run the following command to set USB0 to HOST mode:</li>{| class="wikitable" style="width:~~zero2w~~800px;" |-| apollo-~~img367.png]]~~p2:/ # '''cat /sys/devices/platform/soc@3000000/soc@3000000\:usbc0@0/usb_host'''

~~<ol start="8" style="list-style-type: decimal;"><li>Then fill in the bytes that need to be sent, such as reading the ID information of the onboard SPIFlash, filling in the address 0x9f in data[0], and then click the '''TRANSFER''' button</li></ol>~~host_chose finished!

~~[[File~~apollo-p2:~~zero2w~~/ #|}</ol><ol start="2" style="list-~~img368.png]]~~style-type: lower-alpha;"><li>Run the following command to switch back to Device mode</li>{| class="wikitable" style="width:800px;" |-| apollo-p2:/ # '''cat /sys/devices/platform/soc@3000000/soc@3000000\:usbc0@0/usb_device'''

~~<ol start="9" style="list-style-type: decimal;"><li>Finally, the APP will display the read ID information of the onboard SPI Flash.</li></ol>~~device_chose finished!

~~[[File~~apollo-p2:~~zero2w~~/ #|}</ol><ol start="3" style="list-~~img369.png]]~~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 ~~start~~>~~<li>If the w25qxx module connected to 40pin SPI1 is read, the ID information of the onboard SPI Flash is also similar.~~</~~li></ol~~span>

~~=== 40pin I2C test method~~ =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 below~~USB camera is recognized normally, the ~~Android12 TV system has i2c1 and i2c2 turned on by default.~~corresponding video device node will be generated under /dev

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

|-

| console:/ # '''~~GPIO serial number~~ls /dev/video0''' /dev/video0| ~~'''GPIO'''~~} <ol start="3" style="list-style-type: decimal;"><li>Then make sure that the adb connection between the Ubuntu PC and the development board is normal. For how to use adb, please refer to the instructions in the section "[[Orange Pi Zero 2W#How to use ADB| '''~~Function~~How to use ADB''']]".</li>| <li>Download the USB camera test APP from the '''~~pin~~official tool'''on the development board information download page</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="~~text~~list-~~align~~style-type: ~~left~~decimal;"|><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="~~text~~list-~~align~~style-type: ~~left~~decimal;"|>~~| '''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'''~~|~~| '''2'''~~== Android system ROOT description ==~~| '''5V'''~~{| ~~style~~class="~~text-align: left;~~wikitable"|| style="~~text~~background-~~align~~color: ~~left~~#ffffdc;width:800px;"|

|-

| <big>'''~~264~~The Android system released by Orange Pi has been ROOT and can be tested using the following method.'''</big>| } # Download from the '''~~PI8~~official tool'''| on the development board data download page '''~~TWI1-SDA~~rootcheck.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>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''']]".</li>~~| '''5V'''~~<li>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.</li>{| ~~style~~class="~~text-align: left;~~wikitable"|| style="~~text-align~~width: ~~left~~800px;"|

|-

| test@test:~$ '''~~263~~adb 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 '''~~GND~~CHECK NOW'''to start checking the ROOT status of the Android system. After the check is completed, the display is as follows. You can see that the Android system has obtained ROOT permissions.</li> ~~| style~~[[File:zero2w-img342.png]]</ol> == How to use MiracastReceiver to cast the mobile phone screen to the development board == | <ol style="~~text~~list-~~align~~style-type: ~~left~~decimal;"|>|<li>First, please make sure that both the development board and the mobile phone are connected to the same WIFI hotspot. For the method of connecting the development board to WIFI, please refer to [[Orange Pi Zero 2W#WI-FI connection method| '''~~269~~the instructions in the WI-FI connection method.''']]</li>| <li>Then open the '''~~PI13~~MiracastReceiver'''application in the Android system of the development board[[File:zero2w-img343.png]]</li>| <li>The interface after '''~~PWM3~~MiracastReceiver'''is opened is as follows| <div class="figure"> [[File:zero2w-img344.png]] </div></li><li>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.[[File:zero2w-img345.png]]</li><li>After waiting for a period of time, you will be able to see the searched connectable devices on your mobile phone, and then we can select the device corresponding to the development board to connect.|[[File:zero2w-img346.png]]</li>| <li>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_TX~~Accept'''~~| '''PH0'''~~[[File:zero2w-img347.png]]</li>~~| '''224'''~~<li>Then you can see the content of the mobile phone screen on the HDMI screen connected to the development board|[[File:zero2w-img348.png]]</li></ol>~~| style~~ ~~| style~~=~~"text~~= 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-~~align~~img269.png]] The location of the infrared remote control power button is as follows: [[File: ~~left;"|~~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 '''~~GND~~OK'''to shut down the Android system.~~| '''9'''~~|[[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. ~~| '''10'''~~~~| '''UART0_RX'''~~== 40pin interface GPIO, UART, SPI test ==~~| '''PH1'''~~{| ~~'''225'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

| <big>'''~~226~~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>| } === 40pin GPIO port test method === # First open wiringOP APP on the desktop ::[[File:zero2w-img351.png]] <ol start="2" style="list-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-type: decimal;"><li>The GPIO test interface is as shown in the figure below. The two rows of '''CheckBox''' buttons on the left have a one-to-one correspondence with the 40pin pins. When the '''CheckBox''' button is checked, the corresponding GPIO pin will be set to '''OUT''' mode and the pin level is set to high level; when unchecked, the GPIO pin level will be set to low level; when the GPIO is clicked When you click the '''GPIO READALL''' button, you can get information such as wPi number, GPIO mode, pin level, etc.; when you click the'''BLINK ALL GPIO''' button, all GPIO ports will cycle through outputting high and low levels. This function can be used to test all the 40pin pins. GPIO port.</li> [[File:zero2w-img353.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then click the '''~~PH2~~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 '''~~UART5_TX~~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 '''11OUT'''and the pin level is high level.</li> [[File:zero2w-img356.png]]</ol>|<ol start="7" style="list-style-type: decimal;">| <li>Click the '''CheckBox'''button in the picture below again to uncheck it, and pin 12will be set to low level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is '''0v''', it means the low level setting is successful.</li> [[File:zero2w-img357.png]]</ol><ol start="8" 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 low level.</li> [[File:zero2w-img358.png]]</ol> === 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: ~~left~~center;"|-| '''GPIO NO.'''|'''GPIO'''| '''~~PI1~~Function'''| '''~~257~~Pin'''

|-

~~| '''227'''~~

~~| '''PH3'''~~

~~| '''UART5_RX'''~~

~~| '''13'''~~

|

~~| '''14'''~~

~~| '''GND'''~~

| style="text-align: left;"|

| '''3.3V'''

| '''1'''

|-

| '''~~261~~264'''| '''PI8'''| '''TWI1-SDA'''| '''3'''|-| '''263'''| '''PI7'''| '''TWI1-SCL'''| '''5'''|-| '''269'''| '''PI13'''| '''PWM3'''| '''7'''|-| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''9'''|-| '''226'''| '''PH2'''| '''UART5_TX'''| '''11'''|-| '''227'''| '''~~PI5~~PH3'''| '''~~UART2_TX~~UART5_RX'''| '''1513'''|-| '''16261'''| '''~~PWM4~~PI5'''| '''~~PI14~~UART2_TX'''| '''~~270~~15'''

|-

| style="text-align: left;"|

| '''3.3V'''

| '''17'''

|

~~| '''18'''~~

~~| style="text-align: left;"|~~

~~| '''PH4'''~~

~~| '''228'''~~

|-

| '''231'''

| '''SPI1_MOSI'''

| '''19'''

|

~~| '''20'''~~

~~| '''GND'''~~

~~| style="text-align: left;"|~~

|-

| '''232'''

| '''SPI1_MISO'''

| '''21'''

|

~~| '''22'''~~

~~| '''UART2_RX'''~~

~~| '''PI6'''~~

~~| '''262'''~~

|-

| '''230'''

| '''SPI1_CLK'''

| '''23'''

|

~~| '''24'''~~

~~| '''SPI1_CS0'''~~

~~| '''PH5'''~~

~~| '''229'''~~

|-

| style="text-align: left;"|

| '''GND'''

| '''25'''

|

~~| '''26'''~~

~~| '''SPI1_CS1'''~~

~~| '''PH9'''~~

~~| '''233'''~~

|-

| '''266'''

| '''TWI2-SDA'''

| '''27'''

|

~~| '''28'''~~

~~| '''TWI2-SCL'''~~

~~| '''PI9'''~~

~~| '''265'''~~

|-

| '''256'''

| style="text-align: left;"|

| '''29'''

|

~~| '''30'''~~

~~| '''GND'''~~

~~| style="text-align: left;"|~~

|-

| '''271'''

| style="text-align: left;"|

| '''31'''

|

~~| '''32'''~~

~~| '''PWM1'''~~

~~| '''PI11'''~~

~~| '''267'''~~

|-

| '''268'''

| '''PWM2'''

| '''33'''

|

~~| '''34'''~~

~~| '''GND'''~~

~~| style="text-align: left;"|~~

|-

| '''258'''

| style="text-align: left;"|

| '''35'''

|

~~| '''36'''~~

~~| style="text-align: left;"|~~

~~| '''PC12'''~~

~~| '''76'''~~

|-

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

~~| '''PI4'''~~

~~| '''260'''~~

|-

| '''4'''

| '''5V'''

| style="text-align: left;"|

|-

| '''6'''

| '''GND'''

~~| '''39'''~~

|

~~| '''40'''~~

| style="text-align: left;"|

| ~~'''PI3'''| '''259'''~~|} ~~<ol start="2"~~ style="~~list-style~~text-~~type~~align: ~~decimal~~left;">|~~<li>The device node corresponding to i2c1 is '''/dev/i2c-1''', and the device node corresponding to i2c2 is '''/dev/i2c~~|-~~2'''</li></ol>~~ ~~apollo-p2:/ # '''ls /dev/i2c-*'''~~ ~~'''/dev/i2c-1 /dev/i2c-2''' /dev/i2c-5~~ ~~<ol start="3" style="list-style-type: decimal;"><li>First open wiringOP APP on the desktop</li></ol>~~ ~~[[File:zero2w-img351.png]]~~ ~~<ol start="4" style="list-style-type: decimal;"><li>Then click the '''I2C_TEST~~| ''' ~~button to open the i2c test interface</li></ol>~~ ~~[[File:zero2w-img370.png]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>The i2c test interface of wiringOP is shown in the figure below</li></ol>~~ ~~[[File:zero2w-img371.png]]~~ ~~<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></ol>~~ ~~[[File:zero2w-img372.png]]~~ ~~<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></ol>~~ ~~[[File:zero2w-img178.png]]~~ ~~<ol start="~~8~~" style="list-style-type: decimal;"><li>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.~~apollo-p2:/ #~~ | '''~~i2cdetect -y 1~~UART0_TX'''~~~~| '''OrPH0'''~~apollo-p2:/ #~~ | '''~~i2cdetect -y 2~~224'''~~[[File:zero2w~~|-~~img373.png]]</li><li>Then set the i2c address to 0x68 in wiringOP, and then click the~~ | '''~~OPEN~~10''' ~~button to open i2c[[File:zero2w-img374.png]]</li><li>After clicking the~~ | '''~~OPEN~~UART0_RX''' ~~button to open i2c, the display is as follows[[File:zero2w-img375.png]]</li><li>Then we test writing a value to the register of the rtc module, for example, writing 0x55 to the 0x1c address<ol style="list-style-type: lower-alpha;"><li>We first set the address of the register to be written to 0x1c[[File:zero2w-img376.png]]</li><li>Then set the value to be written to 0x55[[File:zero2w-img377.png]]</li><li>Then click the~~ | '''~~WRITE BYTE~~PH1''' ~~button to perform the writing action[[File:zero2w-img378.png]]</li></ol></li><li>Then click the~~ | '''~~READ BYTE~~225''' ~~button to read the value of the 0x1c register. If it displays 0x55, it means that the i2c read and write test has passed.[[File:zero2w-img379.png]]</li></ol>~~ ~~=== 40pin PWM test ===~~ ~~# As can be seen from the table below, the available pwm are pwm1, pwm2, pwm3 and pwm4.~~ ~~{| class="wikitable"~~

|-

|-

| '''14'''

| '''GND'''

| style="text-align: left;"|

|-| '''~~3.3V~~16'''| '''1PWM4'''|| '''2PI14'''| '''5V270'''| ~~style="text~~-~~align: left;"~~|'''18'''

| style="text-align: left;"|

| '''PH4'''

| '''228'''

|-

| '''~~264~~20'''| '''~~PI8'''| '''TWI1-SDA'''| '''3'''~~|~~| '''4'''| '''5V~~GND'''

| style="text-align: left;"|

|-

| '''~~263~~22'''| '''~~PI7~~UART2_RX'''| '''~~TWI1~~PI6'''| '''262'''|-| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229'''|-| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''233'''|-| '''28'''| '''TWI2-SCL'''| '''5PI9'''|'''265'''|-| '''630'''

| '''GND'''

| style="text-align: left;"|

|-

| '''~~269~~32'''| '''~~PI13~~PWM1'''| '''~~PWM3~~PI11'''| '''~~7'''~~|~~| '''8'''| '''UART0_TX'''| '''PH0'''| '''224~~267'''

|-

| '''34'''

| '''GND'''

| style="text-align: left;"|

~~| '''GND'''~~

~~| '''9'''~~

|

~~| '''10'''~~

~~| '''UART0_RX'''~~

~~| '''PH1'''~~

~~| '''225'''~~

|-

| '''~~226'''| '''PH2'''| '''UART5_TX'''| '''11'''~~|~~| '''12~~36'''

| style="text-align: left;"|

| '''~~PI1~~PC12'''| '''~~257~~76'''

|-

| '''~~227~~38'''~~| '''PH3'''| '''UART5_RX'''| '''13'''~~|~~| '''14'''| '''GND'''| style="text-align: left;"|~~

| style="text-align: left;"|

| '''PI4'''

| '''260'''

|-

| '''~~261~~40'''~~| '''PI5'''| '''UART2_TX'''| '''15'''~~|~~| '''16'''| '''PWM4'''| '''PI14'''| '''270'''~~|-

| style="text-align: left;"|

| '''PI3'''| '''259'''|}</div> <ol start="2" style="~~text~~list-style-~~align~~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: ~~left~~800px;"|-| apollo-p2:/ # ls /dev/ttyAS*/dev/ttyAS0      /dev/ttyAS1      '''/dev/ttyAS2      /dev/ttyAS5'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>First open wiringOP APP on the desktop</li> [[File:zero2w-img351.3Vpng]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then click the '''UART_TEST'''button to open the UART test interface</li> [[File:zero2w-img359.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>The serial port test interface of wiringOP is as shown in the figure below</li> [[File:zero2w-img360.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then select the '''/dev/ttyAS2''' or'''/dev/ttyAS5''' node in the selection box| [[File:zero2w-img361.png]]</li><li>Enter the baud rate you want to set in the edit box, and then click the '''OPEN''' button to open the uart node. After the opening is successful, the '''OPEN''' button becomes unselectable, and the '''CLOSE''' button and '''17SEND'''button become selectable.</li>|| [[File:zero2w-img362.png]]</ol><ol start="8" style="list-style-type: decimal;"><li>Then use Dupont wire to short the rx and tx pins of uart</li><li>Then you can enter a paragraph of characters in the send edit box below and click the '''18SEND'''button to start sending.</li> [[File:zero2w-img363.png]]</ol><ol start="10" style="list-style-type: decimal;"><li>If everything is normal, the received string will be displayed in the receiving box</li> [[File:zero2w-img364.png]]</ol> === 40pin SPI test method === # 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: ~~left~~center;"|-| '''GPIO NO.'''|'''GPIO'''| '''~~PH4~~Function'''| '''~~228~~Pin'''

|-

~~| '''231'''~~

~~| '''PH7'''~~

~~| '''SPI1_MOSI'''~~

~~| '''19'''~~

|

~~| '''20'''~~

~~| '''GND'''~~

| style="text-align: left;"|

| '''3.3V'''

| '''1'''

|-

| '''~~232~~264'''| '''~~PH8~~PI8'''| '''~~SPI1_MISO~~TWI1-SDA'''| '''~~21'''~~|~~| '''22'''| '''UART2_RX'''| '''PI6'''| '''262~~3'''

|-

| '''263'''| '''PI7'''| '''TWI1-SCL'''| '''5'''|-| '''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'''

|

~~| '''24'''~~

~~| '''SPI1_CS0'''~~

~~| '''PH5'''~~

~~| '''229'''~~

|-

| style="text-align: left;"|

| '''GND'''

| '''25'''

|

~~| '''26'''~~

~~| '''SPI1_CS1'''~~

~~| '''PH9'''~~

~~| '''233'''~~

|-

| '''266'''

| '''TWI2-SDA'''

| '''27'''

|

~~| '''28'''~~

~~| '''TWI2-SCL'''~~

~~| '''PI9'''~~

~~| '''265'''~~

|-

| '''256'''

| style="text-align: left;"|

| '''29'''

|~~| '''30'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~|-

| '''271'''

| '''PI15'''

| style="text-align: left;"|

| '''31'''

|

~~| '''32'''~~

~~| '''PWM1'''~~

~~| '''PI11'''~~

~~| '''267'''~~

|-

| '''268'''

| '''PWM2'''

| '''33'''

|

~~| '''34'''~~

~~| '''GND'''~~

~~| style="text-align: left;"|~~

|-

| '''258'''

| style="text-align: left;"|

| '''35'''

|}{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''36Pin'''| '''Function'''| '''GPIO'''| '''GPIO NO.'''|-| '''2'''| '''5V'''| style="text-align: left;"|

| style="text-align: left;"|

~~| '''PC12'''~~

~~| '''76'''~~

|-

| '''~~272~~4'''| '''~~PI16~~5V'''

| style="text-align: left;"|

~~| '''37'''~~

|

~~| '''38'''~~

| style="text-align: left;"|

~~| '''PI4'''~~

~~| '''260'''~~

|-

| '''6'''

| '''GND'''

| style="text-align: left;"|

|-

| '''8'''

| '''UART0_TX'''

| '''PH0'''

| '''224'''

|-

| '''10'''

| '''UART0_RX'''

| '''PH1'''

| '''225'''

|-

| '''12'''

| style="text-align: left;"|

| '''PI1'''

| '''257'''

|-

| '''14'''

| '''GND'''

~~| '''39'''~~

|

~~| '''40'''~~

| 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'''|-| '''28'''| '''TWI2-SCL'''| '''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;"|| '''~~PI3~~PC12'''| '''~~259~~76'''

|}

</div>

<li>~~First click~~ The device node corresponding to SPI1 CS0 is '''/dev/spidev1.0''', and the ~~wiringOP icon~~ device node corresponding to ~~open wiringOP APP~~SPI1 CS1 is '''/dev/spidev1.1'''</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| ~~[[File~~apollo-p2:~~zero2w-img351~~/ # '''ls /dev/spidev1.~~png]]~~*'''

'''/dev/spidev1.0      /dev/spidev1.1'''

|}

</ol>

<li>~~Then click~~ Here is a demonstration to test the SPI1 interface through the '''~~PWM_TEST~~w25qxx''' ~~button on~~ module. First, connect the ~~main interface of wiringOP~~ w25qxx module to ~~enter~~ the ~~PWM test~~ SPI1 interface.</li>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''It doesn't matter if there is no w25qxx module, because there is a SPIFlash on the development board connected to SPI0, and the configuration of SPI0 is also turned on by default in Android, so we can also directly use the onboard SPIFlash for testing.'''</olbig>|}~~[[File:zero2w-img380.png]]~~</ol>

<li>~~The PWM test interface is as follows~~Then open wiringOP APP on the desktop</li~~></ol~~>

~~<div class="figure">~~ [[File:zero2w-~~img381~~img351.png]] </~~div~~ol>

<li>Then ~~set which PWM you want to use in~~ click the ~~Channel. The default is PWM1. If you want~~ '''SPI_TEST''' button to ~~set it to PWM2, just enter 2 in~~ open the ~~Channel. PWM3 and PWM4 and so on.~~SPI test interface</li>~~</ol>~~ ~~[[File:zero2w-img382.png]]~~

[[File:zero2w-img365.png]]

</ol>

<li>Then select the spi device node in the upper left corner. If you ~~can set~~ test the ~~PWM period~~onboard SPIFlash directly, just keep the default '''/dev/spidev0. ~~The default configuration~~ 0'''. If the '''w25qxx''' module is connected to the 40pin spi1 cs0, then please select'''~~50000ns~~/dev/spidev1.0'''~~. The converted PWM frequency~~ , if the w25qxx module is connected to the 40pin spi1 cs1, then please select '''~~20KHz~~/dev/spidev1.1'''</lip><~~/ol~~div class="figure">

[[File:zero2w-~~img383~~img366.png]]

<~~ol start="7" style="list-style-type: decimal;"~~/div></li><li>Then click the '''~~EXPORT~~OPEN'''button to ~~export PWM~~initialize the SPI</lip></olli> ~~[[File:zero2w-img384.png]]~~

[[File:zero2w-img367.png]]

</ol>

<li>Then ~~drag~~ fill in the ~~progress bar below~~ bytes that need to ~~change~~ be sent, such as reading the ID information of the onboard SPIFlash, filling in the ~~PWM duty cycle~~address 0x9f in data[0], and then ~~check~~ click the '''~~Enable~~TRANSFER''' ~~to output the PWM waveform.~~button</li>~~</ol>~~ ~~[[File:zero2w-img385.png]]~~

[[File:zero2w-img368.png]]

</ol>

<li>~~Then use an oscilloscope to measure~~ Finally, the ~~corresponding pins in~~ APP will display the ~~40pin development board and you can see~~ read ID information of the ~~following waveform~~onboard SPI Flash.</li~~></ol~~>

[[File:zero2w-~~img386~~img369.png]]</ol><ol start="10" style="list-style-type: decimal;"><li>If the w25qxx module connected to 40pin SPI1 is read, the ID information of the onboard SPI Flash is also similar.</li></ol>

= ~~'''How to compile Android 12 source code'''~~ == 40pin I2C test method ===

~~== Download~~ table below, the ~~source code of Android 12 ==~~Android12 TV system has i2c1 and i2c2 turned on by default.

<ol div style="~~list~~display: flex;">::{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''GPIO NO.'''| '''GPIO'''| '''Function'''| '''Pin'''|-| style="text-~~type~~align: ~~decimal~~left;">|| style="text-align: left;"|| '''3.3V'''| '''1'''|-| '''<~~li><p~~span style="color:#FF0000">~~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~~264</pspan>'''| '''<ol span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">PI8<li/span>~~Google Cloud Drive~~'''| '''<~~/li~~span style="color:#FF0000">TWI1-SDA</olspan>'''| '''<~~/li~~span style="color:#FF0000">3</olspan>''' ~~[[File:zero2w~~|-~~img387.png]]~~ | '''<~~ol start~~span style="2color:#FF0000" >263'''| '''PI7<li/span>~~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~~''| '''TWI1-SCL</lispan>'''| '''5</olspan>'''|-~~test@test:~$~~ | '''~~md5sum -c H618-Android12-Src.tar.gz.md5sum~~269'''| '''PI13'''~~H618-Android12-Src.tar.gzaa:~~ | '''OKPWM3''' ~~H618-Android12-Src.tar.gzab:~~ | '''OK7'''|-~~......~~ ~~<ol start~~| style="3text-align: left;" || style="~~list-style~~text-~~type~~align: ~~decimal~~left;">|| '''GND'''| '''9'''|-| '''226'''~~<li>Then you need to merge multiple compressed files into one, and then extract the Android source code. The command looks like this:</li></ol>~~| '''PH2'''| '''UART5_TX'''~~test@test:~$~~ | '''11'''~~cat H618~~|-~~Android12~~| '''227'''| '''PH3'''| '''UART5_RX'''| '''13'''|-~~Src.tar.gza* > H618-Android12-Src.tar.gz~~| '''261'''| '''PI5'''| '''UART2_TX'''~~test@test:~$~~ | '''~~tar -xvf H618-Android12-Src.tar.gz~~15'''|-~~<ol start~~| style="4text-align: left;" || style="~~list~~text-~~style-type~~align: ~~decimal~~left;">|| '''3.3V'''| '''17'''|-| '''231'''| '''PH7'''| '''SPI1_MOSI'''| '''19'''|-| '''232'''~~<li>Then unzip the compressed package of the files modified by Orange Pi Zero2w</li></ol>~~| '''PH8'''| '''SPI1_MISO'''~~test@test:~$~~ | '''~~tar zxf opizero2w_android12_patches.tar.gz~~21'''|-~~test@test:~$~~ | '''230'''| '''lsPH6'''| '''SPI1_CLK'''| '''~~opizero2w_android12_patches~~23''' ~~opizero2w_android12_patches.tar.gz~~|-~~<ol start~~| style="5text-align: left;" || style="~~list-style~~text-~~type~~align: ~~decimal~~left;">|| '''GND'''| '''25'''|-| '''<lispan style="color:#FF0000">~~Then copy the files modified by Orange Pi Zero2w to the Android source code~~266</lispan>'''| '''PI10</olspan>''' ~~test@test:~$~~ | '''cp TWI2-~~rf opizero2w_android12_patches/* H618-Android12-Src~~SDA''' | '''27'''~~== Compile the source code of Android 12 ==~~|-| '''256'''| '''PI0''Android12 is compiled on an x86_64 computer with Ubuntu 22.04 installed. Other versions of Ubuntu system package dependencies may have some differences. The image download address of the Ubuntu 22.04 amd64 version is as follows'| style="text-align:left;"|| '''29'''|-~~[https://repo.huaweicloud.com/ubuntu-releases/22.04/ubuntu-22.04.2-desktop-amd64.iso~~ | '''271'''| '''~~https://repo.huaweicloud.com/ubuntu-releases/22.04/ubuntu-22.04.2-desktop-amd64.iso~~PI15''']| style="text-align: left;"|| '''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.31'''|-~~# First install the software packages needed to compile Android12 source code~~| '''268'''| '''PI12'''~~test@test:~$~~ | '''~~sudo apt-get update~~PWM2''' ~~test@test:~$~~ | '''~~sudo apt-get install -y git gnupg flex bison gperf build-essential \~~33'''|-| '''~~zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 \~~258''' | '''~~lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z1-dev ccache \~~PI2'''| style="text-align: left;"|| '''~~libgl1-mesa-dev libxml2-utils xsltproc unzip u-boot-tools python-is-python3 \~~35'''|-| '''~~libssl-dev libncurses5 clang gawk~~272'''| '''PI16'''~~<ol start="2"~~ | style="~~list-style~~text-~~type~~align: ~~decimal~~left;">|| '''37'''~~<li>Then compile the code in the longan folder, which mainly contains u~~|-~~boot and linux kernel<ol~~ | style="~~list~~text-align: left;"|| style="text-~~type~~align: ~~lower-alpha~~left;">|~~<li>First run~~ | '''~~./build.sh config~~GND''' ~~to set compilation options</li></ol></li></ol>~~ ~~test@test:~$~~ | '''~~cd H618-Android12-Src/longan~~39'''|}~~test@test~~{| class="wikitable" style="width:~~~/H618~~390px;margin-~~Android12~~right: 20px;text-~~Src/longan$~~ align: center;"|-| '''~~./build.sh config~~Pin'''| '''Function'''~~Welcome to mkscript setup progress~~| '''GPIO'''| '''GPIO NO.'''~~All available platform:~~|-| '''2'''~~0. android~~| '''5V'''| style="text-align: left;"|~~1. linux~~| style="text-align: left;"||-~~Choice [android]:~~ | '''04'''| '''5V'''~~All available ic~~| style="text-align:left;"|| style="text-align: left;"|~~0. h618~~|-| '''6'''~~Choice [h618]:~~ | '''0GND'''| style="text-align: left;"|~~All available board~~| style="text-align:left;"||-~~0. ft~~| '''8'''| '''UART0_TX'''~~1. p1~~| '''PH0'''| '''224'''~~2. p2~~|-| '''10'''~~3. p7~~| '''UART0_RX'''| '''PH1'''~~4. p7l~~| '''225'''|-~~5. perf1~~| '''12'''| style="text-align: left;"|~~6. perf2~~| '''PI1'''| '''257'''~~7. perf3~~ ~~8. qa~~|-| '''14'''~~Choice [p2]:~~ | '''2GND'''| style="text-align: left;"|~~All available flash~~| style="text-align:left;"||-~~0. default~~| '''16'''| '''PWM4'''| '''PI14'''~~1. nor~~| '''270'''|-~~Choice [default]:~~ | '''018''' ~~All available kern_ver~~| style="text-align:left;"|| '''PH4'''~~0. linux~~| '''228'''|-~~5.4~~| '''20'''~~Choice [linux-5.4]:~~ | '''0GND'''| style="text-align: left;"|~~All available arch~~| style="text-align:left;"||-~~0. arm~~| '''22'''| '''UART2_RX'''~~1. arm64~~| '''PI6'''~~Choice [arm64]:~~ | '''1262'''|-| '''~~......~~24'''| '''SPI1_CS0'''*** Default configuration is based on | '''PH5''~~sun50iw9p1smp_h618_android_defconfig~~'| '''229'''#|-| '''26'''~~# configuration written to .config~~| '''SPI1_CS1'''| '''PH9'''#| '''233'''|-~~make[1]~~| '''28''~~/home/test/H618~~'| '''TWI2-~~Android12-Src~~SCL</~~longan~~span>'''| '''PI9</~~out~~span>'''| '''265</~~kernel/build~~span>'''|-| '''30'''~~make: Leaving directory~~ | '''GND'''~~/home/test/H618~~| style="text-~~Android12~~align: left;"|| style="text-~~Src/longan/kernel/linux~~align: left;"||-~~5.4~~| '''32'''| '''PWM1'''| '''PI11'''~~INFO: clean buildserver~~| '''267'''|-~~INFO: prepare_buildserver~~| '''34'''| '''GND'''~~<ol start~~| style="2text-align: left;" || style="~~list~~text-align: left;"||-| '''36'''| style="text-~~type~~align: ~~lower-alpha~~left;">|~~<li>Then run the~~ | '''~~./build.sh~~PC12''' ~~script to start compilation.</li></ol>~~| '''76'''~~test@test:~/H618~~|-~~Android12-Src/longan$~~ | '''~~./build.sh~~38''' ~~<ol start~~| style="3text-align: left;" || '''PI4'''| '''260'''|-| '''40'''| style="~~list-style~~text-~~type~~align: ~~lower-alpha~~left;">|| '''PI3'''| '''259'''|}~~<li>After compilation is completed, you will see the following output</li>~~</oldiv> ~~sun50iw9p1 compile Kernel successful~~ ~~INFO: Prepare toolchain ...~~

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

~~INFO~~'''/dev/i2c-1      /dev/i2c-2'''      /dev/i2c-5|}</ol><ol start="3" style="list-style-type: decimal;"><li>First open wiringOP APP on the desktop</li>

~~INFO~~[[File: ~~build rootfs~~ 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>

~~INFO~~[[File: ~~skip make rootfs~~ zero2w-img178.png]]</ol><ol start="8" style="list-style-type: decimal;"><li>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.{| class="wikitable" style="width:800px;" |-| apollo-p2:/ # '''i2cdetect -y 1''''''Or'''apollo-p2:/ # '''i2cdetect -y 2'''|}[[File:zero2w-img373.png]]</li><li>Then set the i2c address to 0x68 in wiringOP, and then click the '''OPEN''' button to open i2c[[File:zero2w-img374.png]]</li><li>After clicking the '''OPEN''' button to open i2c, the display is as follows[[File:zero2w-img375.png]]</li><li>Then we test writing a value to the register of the rtc module, for ~~android~~example, writing 0x55 to the 0x1c address<ol style="list-style-type: lower-alpha;"><li>We first set the address of the register to be written to 0x1c[[File:zero2w-img376.png]]</li><li>Then set the value to be written to 0x55[[File:zero2w-img377.png]]</li><li>Then click the '''WRITE BYTE''' button to perform the writing action[[File:zero2w-img378.png]]</li></ol></li><li>Then click the '''READ BYTE''' button to read the value of the 0x1c register. If it displays 0x55, it means that the i2c read and write test has passed.[[File:zero2w-img379.png]]</li></ol>

~~INFO: --------------------------------------~~

~~INFO: build lichee OK.~~=== 40pin PWM test ===

~~INFO: ----------------------------------------~~# 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'''|-| '''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'''|-| '''266'''| '''PI10'''| '''TWI2-SDA'''| '''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'''| '''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'''|-| '''28'''| '''TWI2-SCL'''| '''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>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 ~~command~~ waveform.</li> [[File:zero2w-img386.png]]</ol> = '''How to compile Android 12 source code''' = == Download the source code of Android 12 == <ol style="list-style-type: decimal;"><li>First download the compressed package of the Android 12 source code and ~~generate~~ the ~~final~~ compressed package of the files modified by Orange Pi Zero2w from Google Cloud Drive<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: '''OK''' H618-Android12-Src.tar.gzab: '''OK''' ......|}</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.gza* > 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> == 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 Ubuntu 22.04 installed. Other versions of Ubuntu system package dependencies may have some differences. The imagedownload address of the Ubuntu 22.04 amd64 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>Then compile the code in the longan folder, which mainly contains u-boot and linux kernel<ol style="list-style-type: lower-alpha;"><li>First run '''./build.sh config''' to set compilation options</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''cd H618-Android12-Src/longan'''test@test:~/H618-Android12-Src/longan$ '''./build.sh config''' Welcome to mkscript setup progressAll available platform::0. android:1. linuxChoice [android]: '''0'''All available ic::0. h618Choice [h618]: '''0'''All available board::0. ft:1. p1:2. p2:3. p7:4. p7l:5. perf1:6. perf2:7. perf3:8. qaChoice [p2]: '''2'''All available flash::0. default:1. norChoice [default]: '''0'''All available kern_ver::0. linux-5.4Choice [linux-5.4]: '''0'''All available arch::0. arm:1. arm64Choice [arm64]: '''1''''''......'''*** Default configuration is based on 'sun50iw9p1smp_h618_android_defconfig'## configuration written to .config#make[1]: Leaving directory '/home/test/H618-Android12-Src/longan/out/kernel/build'make: Leaving directory '/home/test/H618-Android12-Src/longan/kernel/linux-5.4'INFO: clean buildserverINFO: prepare_buildserver|}</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><olstart="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>The storage path of the Android image generated by compilation is:{| class="wikitable" style="width:800px;" |-| '''longan/out/h618_android12_p2_uart0.img'''|}</li></ol> = '''Appendix''' = == User manual update history == {| class="wikitable" style="width:800px;text-align: center;"|-| '''Version'''| '''Date'''| '''Release Notes'''|-| v1.0| 2023-09-14| initial version|} == 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

~~= '''Appendix''' =~~

~~~~

~~== User manual update history ==~~

~~{| class="wikitable"~~

|-

~~| '''Version'''~~

~~| '''Date'''~~

~~| '''Release Notes'''~~

|-

~~| v1.0~~

~~| 2023-09-14~~

~~| initial version~~

|}

~~~~

~~== Image update history ==~~

~~{| class="wikitable"~~

|-

~~| '''Date'''~~

~~| '''Release Notes'''~~

|-

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

Admin

Bureaucrats, Administrators

8,367

edits

Wiki-Orange Pi β

Changes

Orange Pi Zero 2W

Wiki-Orange Pi ^β