Changes

← Older edit

Orange Pi Zero 2W

43,117 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;"

[[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;" |-| <~~/li~~big>~~</ol>~~ '''After the development board's Linux system is started for the first time, orangepi_first_run.txt will be deleted or renamed to orangepi_first_run.txt.old. At this time, even if the orangepi_first_run.txt configuration file is reset, and then the development board's Linux system is restarted, orangepi_first_run. The configuration in txt will not take effect again, because this configuration will only take effect when the Linux system is started for the first time after burning it. Please pay special attention to this point.'''</big>|}</li></ol>

~~~~

== SSH remote login development board ==

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

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

~~~~

=== 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:~~orangepi@orangepi~~{| class="wikitable" style="width:~~~$ '''git clone https://github.com/jacksonliam/mjpg~~800px;" |-~~streamer'''</li><li>The image download address of Gitee is:~~| orangepi@orangepi:~$ '''git clone https://~~gitee~~github.com/~~leeboby~~jacksonliam/mjpg-streamer'''~~</li></ol>~~|}

</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~~big>~~</ol>~~ '''If there is noise during the headphone test, please pull out some of the headphones and do not plug them all the way in.'''</big>|}</li></ol>

~~~~

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

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

|

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

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

~~| '''PI3'''~~

~~| '''259'''~~

|}

~~<ol start~~{| class="3wikitable" style="~~list-style-type~~width: ~~decimal~~390px;">~~<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.''' ~~'''The storage path of the compiled wiringOP deb package in orangepi-build is: '''~~ ~~'''orangepi-build/external/cache/debs/arm64/wiringpi_x.xx.deb'''~~ ~~'''After entering the system, you can run the gpio readall command. If you can see the following output, it means that wiringOP has been pre~~margin-~~installed and can be used normally.'''~~ ~~[[File~~right:~~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~~20px;">~~<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~~align: ~~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~~center;">~~<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# '''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~~"

|-

~~| '''GPIO序号'''~~

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

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

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

|

| '''pin'''

| '''Function'''

| '''GPIO'''

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

|-

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

~~| '''3.3V'''~~

~~| '''1'''~~

|

| '''2'''

| '''5V'''

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

|-

~~| '''264'''~~

~~| '''PI8'''~~

~~| '''TWI1-SDA'''~~

~~| '''3'''~~

|

| '''4'''

| '''5V'''

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

|-

~~| '''263'''~~

~~| '''PI7'''~~

~~| '''TWI1-SCL'''~~

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

|

| '''6'''

| '''GND'''

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

|-

~~| '''269'''~~

~~| '''PI13'''~~

~~| '''PWM3/UART4_TX'''~~

~~| '''7'''~~

|

| '''8'''

| '''UART0_TX'''

| '''224'''

|-

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

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

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

|

| '''10'''

| '''UART0_RX'''

| '''225'''

|-

~~| '''226'''~~

~~| '''PH2'''~~

~~| '''UART5_TX'''~~

~~| '''11'''~~

|

| '''12'''

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

| '''257'''

|-

~~| '''227'''~~

~~| '''PH3'''~~

~~| '''UART5_RX'''~~

~~| '''13'''~~

|

| '''14'''

| '''GND'''

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

|-

~~| '''261'''~~

~~| '''PI5'''~~

~~| '''TWI0_SCL/UART2_TX'''~~

~~| '''15'''~~

|

| '''16'''

| '''PWM4/UART4_RX'''

| '''270'''

|-

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

~~| '''3.3V'''~~

~~| '''17'''~~

|

| '''18'''

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

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

| '''PH5'''

| '''229'''

|-

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

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

~~| '''25'''~~

|

| '''26'''

| '''SPI1_CS1'''

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

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

~~| '''31'''~~

|

| '''32'''

| '''PWM1'''

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

</ol>

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

~~<ol style~~=~~"list-style-type: decimal;"><li>In Linux systems, spi1 is turned off by default and needs~~ = How to ~~be turned on manually before it can be used. The opening steps are as follows:<ol style~~install wiringOP ==~~"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 figure below, and then use the '''space''' to select the > dtbo configuration of the SPI you want to open.</li></ol>~~</li></ol>~~

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

|-

| ~~'''dtbo configuration'''| '''illustrate~~<big>'''|Note that wiringOP is already pre-~~| '''spi1-cs0~~installed in the linux image released by Orange Pi. Unless the wiringOP code is updated, there is no need to re-~~cs1-spidev'''| '''Open cs0~~ download, compile and ~~cs1 of spi1 at the same time~~install, you can just use it directly.'''|-~~| '''spi1-cs0-spidev'''~~| '''~~Only open cs0~~ The storage path of ~~spi1'''~~|-~~| '''spi1~~the compiled wiringOP deb package in orangepi-~~cs1-spidev'''| '~~build is: ''~~Only open cs1 of spi1~~'''|}

~~[[File~~'''orangepi-~~img172~~build/external/cache/debs/arm64/wiringpi_x.~~png]]~~xx.deb'''

~~<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="2" style="list-style-type: decimal;"><li>Then check whether there is a~~ '''~~spidev1.x''' device node in~~ After entering the ~~Linux~~ system~~. If it exists~~, ~~it means that~~ you can run the ~~SPI1 configuration has taken effect~~gpio readall command.~~orangepi@orangepi:~$ '''ls /dev/spidev1*'''/dev/spidev1.0 /dev/spidev1.1'''Note that only when~~ If you ~~open spi1-cs0-cs1-spidev, you will~~ can see the ~~device nodes of the two spi.'''</li><li>Next~~following output, ~~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~~ it means that ~~the data of TX and RX are inconsistent.orangepi@orangepi:~$ '''sudo spidev_test -v~~ wiringOP has been pre-~~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 pins of SPI1 mosi (pin 19 in the 40pin interface) and miso (pin 21 in the 40pin interface)~~ installed 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 | ......@.…▒..................▒~~be used normally.~~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>~~</olbig>

~~=== 40pin I2C test ===~~img170.png|center]]

~~# As can be seen from~~ <big>'''WiringOP currently mainly adapts to the ~~table below~~functions of setting GPIO port input and output, ~~the i2c available for the 40pin interface are i2c0~~setting GPIO port output high and low levels, ~~i2c1~~ and ~~i2c2~~setting pull-up and pull-down resistors. Functions such as hardware PWM cannot be used.'''</big>|}

<ol style="list-style-type: decimal;"><li>Download the code of wiringOP{| class="wikitable" style="width:800px;"

|-

| ~~'''GPIO序号'''~~| orangepi@orangepi:~$ '''~~GPIO~~sudo apt update'''| orangepi@orangepi:~$ '''~~Function~~sudo apt install -y git'''| orangepi@orangepi:~$ '''~~pin'''~~|~~| '''pin~~git clone https://github.com/orangepi-xunlong/wiringOP.git -b next'''| ~~'''Function'''~~}{| ~~'''GPIO'''| '''GPIO NO.'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

~~| style="text-align: left;"~~|~~| style="text-align: left;"|~~| <big>'''Note that the source code needs to download the code of wiringOP next branch. Please don'3t miss the -b next parameter.3V'''| '''1If 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>|}~~| '''2'''~~</li>~~| '''5V'''~~<li>Compile and install wiringOP{| ~~style~~class="~~text-align: left;~~wikitable"|| style="~~text-align~~width: ~~left~~800px;"|

|-

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

|-

| ~~'''263'''~~| <big>'''~~PI7~~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>| ~~'''TWI1-SCL'''~~}~~| '''5'''~~|~~| '''6'''~~=== 40pin GPIO port test ===~~| '''GND'''~~| <ol style="~~text~~list-~~align~~style-type: ~~left~~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.{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|

|-

| ~~'''269'''~~| root@orangepi:~/wiringOP# '''~~PI13'''~~| gpio mode 2 out'''~~PWM3~~</~~UART4_TX'''~~p>| ~~'''7'''~~}|</li>~~| '''8'''| '''UART0_TX'''~~<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.{| ~~'''PH0'''| '''224'''~~class="wikitable" style="width:800px;"

|-

| ~~style="text-align~~root@orangepi: ~~left;"|~~| ~/wiringOP# '''gpio write 2 0'''|}~~| '''10'''| '''UART0_RX'''~~</li>~~| '''PH1'''~~<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.{| ~~'''225'''~~class="wikitable" style="width:800px;"

|-

| root@orangepi:~/wiringOP# '''~~226~~gpio write 2 1'''| ~~'''PH2'''~~}</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> ~~| '''UART5_TX'''~~~~| '''11'''~~|=== How to set the pull-down resistor of 40 Pin GPIO port ===~~| '''12'''~~| <ol style="~~text~~list-style-~~align~~type: ~~left~~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>~~| '''PI1'''~~<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.{| ~~'''257'''~~class="wikitable" style="width:800px;"

|-

| ~~'''227'''~~| root@orangepi:~/wiringOP# '''~~PH3~~gpio mode 2 in'''| ~~'''UART5_RX'''~~}~~| '''13'''~~</li>|~~| '''14'''| '''GND'''~~<li>After setting to input mode, execute the following command to set the GPIO port to pull-up mode.{| ~~style~~class="~~text-align: left;~~wikitable"|| style="~~text-align~~width: ~~left~~800px;"|

|-

| root@orangepi:~/wiringOP# '''~~261~~gpio mode 2 up'''|}</li><li>Then enter the following command to read the level of the GPIO port. If the level is 1, it means that the pull-up mode is set successfully.{| class="wikitable" style="width:800px;" | -| root@orangepi:~/wiringOP# '''gpio read 2''''''~~PI5~~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# '''~~TWI0_SCL~~gpio mode 2</~~UART2_TX~~span> 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.{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP# '''gpio read 2''''''150'''|}</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;"|-| '''16GPIO NO.'''| '''~~PWM4/UART4_RX~~GPIO'''| '''~~PI14~~Function'''| '''~~270~~pin'''

|-

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

| '''3.3V'''

| '''~~17'''~~|~~| '''18'''| style="text-align: left;"|| '''PH4'''| '''228~~1'''

|-

| '''~~231~~264'''| '''~~PH7~~PI8'''| '''~~SPI1_MOSI'''| '''19~~TWI1-SDA'''|| '''203'''~~| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~232~~263'''| '''PI7'''| '''TWI1-SCL'''| '''5'''|-| '''269'''| '''PI13'''| '''PWM3/UART4_TX'''| '''7'''|-| style="text-align: left;"|| 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;"|| style="text-align: left;"|| '''3.3V'''| '''17'''|-| '''231'''| '''~~PH8~~PH7'''| '''~~SPI1_MISO~~SPI1_MOSI'''| '''2119'''|-| '''22232'''| '''~~TWI0_SDA~~PH8</~~UART2_RX~~span>'''| '''~~PI6~~SPI1_MISO'''| '''~~262~~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/UART3_RX'''

| '''27'''

|~~| '''28'''| '''TWI2-SCL/UART3_TX'''| '''PI9'''| '''265'''~~|-| '''256'''

| '''PI0'''

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

|

~~| '''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 - i2c0~~2'''| '''~~pi-i2c0~~5V'''| style="text-align: left;"|| style="text-align: left;"|

|-

| '''~~40pin - i2c1~~4'''| '''~~pi-i2c1~~5V'''| style="text-align: left;"|| style="text-align: left;"|

|-

| '''~~40pin - i2c2~~6'''| '''~~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"~~

|-

~~| '''GPIO NO.'''| '''GPIO'''| '''Function'''| '''pin'''~~|~~| '''pin'''| '''Function'''| '''GPIO'''| '''GPIO NO.'''~~|-~~| style="text-align: left;"|| style="text-align: left;"|| '''3.3V'''| '''1'''~~|~~| '''2'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"|~~|-~~| '''264'''| '''PI8'''| '''TWI1-SDA'''| '''3'''~~|~~| '''4'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"|~~|-~~| '''263'''| '''PI7'''| '''TWI1-SCL'''| '''5'''~~|~~| '''6'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~|-~~| '''269'''| '''PI13'''| '''PWM3/UART4_TX'''| '''7'''~~|| '''8'''| '''UART0_TX'''

| '''PH0'''

| '''224'''

|-

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

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

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

|

| '''10'''

| '''UART0_RX'''

| '''225'''

|-

~~| '''226'''~~

~~| '''PH2'''~~

~~| '''UART5_TX'''~~

~~| '''11'''~~

|

| '''12'''

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

| '''257'''

|-

~~| '''227'''~~

~~| '''PH3'''~~

~~| '''UART5_RX'''~~

~~| '''13'''~~

|

| '''14'''

| '''GND'''

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

|-

~~| '''261'''| '''PI5'''| '''TWI0_SCL/UART2_TX'''| '''15'''~~|| '''16'''

| '''PWM4/UART4_RX'''

| '''PI14'''

| '''270'''

|-

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

~~| '''3.3V'''~~

~~| '''17'''~~

|

| '''18'''

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

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

|-

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

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

~~| '''31'''~~

|

| '''32'''

| '''PWM1'''

| '''267'''

|-

~~| '''268'''~~

~~| '''PI12'''~~

~~| '''PWM2'''~~

~~| '''33'''~~

|

| '''34'''

| '''GND'''

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

|-

~~| '''258'''| '''PI2'''| style="text-align: left;"|| '''35'''~~|| '''36'''

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

| '''PC12'''

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

<ol ~~start="2"~~ style="list-style-type: decimal;"><li>In Linux systems, ~~uart~~ 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:~$ '''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~~ figure below, and then use the '''space''' to select the ~~> serial port~~ dtbo configuration of the SPI you want to open.</li~~></ol></li></ol~~>

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

|-

| '''~~Multiplexing function in 40pin~~dtbo configuration'''| '''~~Corresponding dtbo configuration~~illustrate'''

|-

| '''~~40pin~~ spi1- ~~uart2~~cs0-cs1-spidev'''| '''~~pi-uart2~~Open cs0 and cs1 of spi1 at the same time'''

|-

| '''~~40pin~~ spi1- ~~uart3~~cs0-spidev'''| '''~~pi-uart3~~Only open cs0 of spi1'''

|-

|}

[[File:zero2w-~~img175~~img172.png]]</ol>

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

</li></ol>

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

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

|-

|

orangepi@orangepi:~$ '''ls /dev/spidev1*'''

/dev/spidev1.0 /dev/spidev1.1

|}

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

|-

|

<big>'''Note that only when you open spi1-cs0-cs1-spidev, you will see the device nodes of the two spi.'''</big>

|}

</li>

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

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

|-

|

orangepi@orangepi:~$ '''sudo spidev_test -v -D /dev/spidev1.0'''

spi mode: 0x0

bits per word: 8

max speed: 500000 Hz (500 KHz)

TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.

RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF | ............................….

|}

</li>

<li>Then short-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: 0x0

bits per word: 8

max speed: 500000 Hz (500 KHz)

TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.

RX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@.…▒..................▒.

|}

</li></ol>

~~<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~~ 40pin I2C test ~~method~~ ===

# As can be seen from the ~~following~~ tablebelow, the i2c available ~~pwm~~ for the 40pin interface are ~~pwm1, pwm2~~i2c0, ~~pwm3~~ i2c1 and ~~pwm4.~~i2c2

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

|-

| '''GPIO NO.'''

| '''GPIO'''

| '''Function'''

| '''~~Pin'''~~|~~| '''Pin'''| '''Function'''| '''GPIO'''| '''GPIO NO.~~pin'''

|-

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

| '''3.3V'''

| '''1'''

|

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

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

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

|-

| '''264'''| '''PI8'''| '''TWI1-SDA'''| '''3'''|-| '''~~4'''| '''5V'''~~| 263'''| '''~~PI7~~v'''| '''TWI1-SCL'''| '''~~5'''~~|~~| '''6'''| '''GND'''~~| 5'''|-| '''269'''

| '''PI13'''

| '''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'''| '''PI5'''| '''TWI0_SCL/UART2_TX'''| '''15~~'''~~|~~| '''16'''| '''PWM4~~</~~UART4_RX'''| '''PI14'''| '''270~~span>'''

|-

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

| '''PH6'''

| '''SPI1_CLK'''

| '''23'''

|

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

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

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

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

|-

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

| '''GND'''

| '''25'''

|

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

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

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

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

|-

| '''266'''| '''PI10'''| '''TWI2-SDA/UART3_RX'''| '''27~~'''~~|~~| '''28'''| '''TWI2-SCL~~</~~UART3_TX'''| '''PI9'''| '''265~~span>'''

|-

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

|

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

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

~~| '''PI3'''~~

~~| '''259'''~~

|}

{| 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~~ 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.{| 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 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 >~~ i2c 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~~picture below.~~'''~~ ~~~~</~~span>=== How to install wiringOP-Python ===~~ ~~<ol style="list-style-type: decimal;"><li><~~p>~~First install dependency packages~~~~root@orangepi:~# '''sudo apt-get update'''root@orangepi:~# '''sudo apt-get -y install git swig python3-dev python3-setuptools'''</li>~~<li~~>Then use the following command to download the source code of wiringOP-Python</li></ol~~>

{| class="wikitable" style="width:800px;text-align: center;"|-| '''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.Multiplexing function in 40pin'''| '''Corresponding dtbo configuration'''~~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~~40pin -~~Python~~i2c0''' ~~root@orangepi:~#~~ | '''~~git clone~~ pi-i2c0'''|-~~recursive https://github.com/orangepi~~| '''40pin -~~xunlong/wiringOP~~i2c1'''| '''pi-~~Python -b next~~i2c1'''|-~~root@orangepi:~#~~ | '''~~cd wiringOP~~40pin -~~Python~~i2c2''' ~~root@orangepi:~/wiringOP-Python#~~ | '''~~git submodule update~~ pi-~~-init --remote~~i2c2'''|}

[[File:zero2w-img173.png]]

</ol>

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

<li>~~Then use the following command to compile wiringOP-Python and install it into~~ After starting the Linux system ~~of the development board~~, first confirm that there is an open i2c device node under /dev{| class="wikitable" style="width:800px;" |-| ~~root~~orangepi@orangepi:~# $ '''~~cd wiringOP~~ls /dev/i2c-~~Python~~*'''~~root@orangepi:~/wiringOP-Python#~~ '''~~python3 generate~~/dev/i2c-~~bindings.py > bindings.i~~*'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>~~root@orangepi:~/wiringOP-Python#~~ '''~~sudo python3 setup~~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.~~py install~~'''</p~~></li~~>~~<li>~~~~Then enter the following command. If helpful information is output, it means wiringOP-Python is successfully installed. Press the~~ '''qThe method to accurately confirm the device node under /dev corresponding to the i2c bus is: ''' ~~key to exit the help information interface.~~</~~li></ol~~big>

~~root@orangepi:~/wiringOP-Python# '''python3 -c "import wiringpi; help(wiringpi)"'''~~

~~Help on module wiringpi~~<ol style="list-style-type:lower-alpha;"><li>'''First run the following command to check the corresponding relationship of i2c'''~~NAME~~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>

~~wiringpi~~

~~DESCRIPTION~~ ~~# This file was automatically generated by SWIG (http:~~<li>'''In the above output'''</~~/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.~~p><ol ~~start="5"~~ style="list-style-type: ~~decimal~~none;"><li>~~The steps to test whether wiringOP~~a) 5002000 is the register base address of the i2c0 bus, and i2c-~~Python~~ 0 shown behind it is ~~installed successfully under the python command line are as follows:~~its corresponding i2c device node</li><~~ol style="list~~li>b) 5002400 is the register base address of the i2c1 bus, and i2c-~~style-type: lower-alpha;"~~3 shown behind it is its corresponding i2c device node</li><li>~~First use~~ c) 5002800 is the ~~python3 command to enter~~ register base address of the ~~command line mode of > python3~~i2c2 bus, and i2c-4 shown behind it is its corresponding i2c device node</li></ol></li></ol>|}

</li></ol>

<li>Then start testing i2c, first install i2c-tools

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

|-

|

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

orangepi@orangepi:~$ '''sudo apt-get install -y i2c-tools'''

|}

</li>

<li>Then connect an i2c device to the 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-color:#ffffdc;width: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.'''

'''Different i2c device addresses are different. The 0x50 address in the picture below is just an example. Please refer to what you actually see.'''</big>

|}

~~root@orangepi~~[[File:~~~# '''python3'''~~ ~~<ol start="2" style="list~~zero2w-~~style-type: lower-alpha;"><li>Then import the python module of wiringpi</li></ol>~~img174.png]]

~~>>> '''import wiringpi;'''~~</div></li></ol>

<~~ol start~~span id="~~3" style="list~~pin-~~style~~uart-~~type: lower-alpha;~~test">~~<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~~></olspan>

~~>>> '''help(wiringpi)'''~~=== 40pin UART test ===

~~Help on module wiringpi:~~# 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.

~~NAME~~ ~~wiringpi~~ ~~DESCRIPTION~~ ~~# This file was automatically generated by SWIG (http://www.swig.org).~~ ~~# Version 4.0.2~~ # ~~# Do not make changes to this file unless you know what you are doing--modify~~ ~~# the SWIG interface file instead.~~ ~~CLASSES~~ ~~builtins.object~~ ~~GPIO~~ ~~I2C~~ ~~Serial~~ ~~nes~~ ~~class GPIO(builtins.object)~~ ~~| GPIO(pinmode=0)~~ | ~~>>>~~ <~~span id="pin-gpio-port-test-1">=== 40pin GPIO port test ===~~ '''Like wiringOP, wiringOP-Python can also determine which GPIO pin to operate by specifying the wPi number. Because there is no command to view the wPi number in wiringOP-Python, you can only view the board's wPi number and physics through the gpio command in wiringOP Correspondence of pins.''' ~~[[File:zero2w-img170.png]]~~ ~~<ol~~ div style="~~list-style-type~~display: ~~decimal~~flex;">~~<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~~ {| class="wikitable" style="~~list~~width:390px;margin-~~style~~right: 20px;text-~~type~~align: ~~lower-alpha~~center;"><li>First set the GPIO port to output mode, where the first > parameter of the '''pinMode''' function is the serial number of > the wPi corresponding to the pin, and the second parameter is > the GPIO mode.~~root@orangepi:~/wiringOP~~|-~~Python# '''python3 -c "import wiringpi; \'''~~| '''~~from wiringpi import~~ GPIO~~; wiringpi~~NO.~~wiringPiSetup() ; \~~'''~~~~| '''~~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.~~root@orangepi:~/wiringOP-Python#~~ | '''~~python3 -c "import wiringpi; \~~Function'''~~~~| '''~~from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\~~pin'''~~'''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.~~root@orangepi~~| style="text-align:~~~/wiringOP-Python# '''python3 -c &quot~~left;~~import wiringpi; \'''~~"|~~'''from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\''''''wiringpi.digitalWrite(2, GPIO.HIGH)"'''</li></ol></li><li>The steps for testing in the command line of python3 are as follows:<ol~~ | style="~~list~~text-~~style-type~~align: ~~lower-alpha~~left;">|~~<li>First use the python3 command to enter the command line mode of > python3root@orangepi:~#~~ | '''~~python3~~3.3V'''~~</li><li>Then import the python module of wiringpi>>>~~ | '''~~import wiringpi~~1'''~~>>> '''from wiringpi import GPIO'''</li>~~|-~~<li>Then set the GPIO port to output mode, where the first parameter > of the~~ | '''~~pinMode~~264'''~~function is the serial number of the wPi > corresponding to the pin, and the second parameter is the GPIO > mode.>>>~~ | '''~~wiringpi.wiringPiSetup()~~PI8'''~~0>>>~~ | '''~~wiringpi.pinMode(2, GPIO.OUTPUT)~~TWI1-SDA'''~~</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.~~>>>~~ | '''~~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.>>>~~ '''~~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 '''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.~~root@orangepi:~/wiringOP-Python#~~ | '''~~cd examples~~263'''~~root@orangepi:~/wiringOP-Python/examples#~~ | '''~~ls blink.py~~PI7'''~~~~| '''~~blink.py~~TWI1-SCL'''~~root@orangepi:~/wiringOP-Python/examples~~| '''~~# python3 blink.py~~5'''~~</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'''| '''1'''~~|~~| '''2'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"|~~|-~~| '''264'''| '''PI8'''| '''TWI1-SDA'''| '''3'''~~|~~| '''4'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"|~~|-~~| '''263'''| '''PI7'''| '''TWI1-SCL'''| '''5'''~~|~~| '''6'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~|-~~| '''269'''| '''PI13'''| '''PWM3/UART4_TX'''| '''7'''~~|~~| '''8'''| '''UART0_TX'''| '''PH0'''| '''224'''~~|-~~| style="text-align: left;"|| style="text-align: left;"|~~| '''GND'''| '''9~~'''~~|~~| '''10'''| '''UART0_RX'''| '''PH1'''| '''225~~'''|-| '''226'''

| '''PH2'''

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

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

|

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

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

~~| '''PI3'''~~

~~| '''259'''~~

|}

~~<ol start~~{| class="2wikitable" style="~~list~~width:390px;margin-~~style~~right: 20px;text-~~type~~align: ~~decimal~~center;">~~<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;">~~| '''pin'''~~<li>First run~~ | '''~~orangepi-config~~Function'''| '''~~. Ordinary users remember to add >~~ GPIO'''~~sudo~~| ''' ~~permissions~~GPIO NO.~~~~'''|-~~orangepi@orangepi:~$~~ | '''~~sudo orangepi-config~~2'''~~</li><li>Then select~~ | '''~~System~~5V'''~~[[File~~| style="text-align: left;"|| style="text-align:~~zero2w~~left;"||-~~img80.png]]</li><li>Then select~~ | '''4'''| '''~~Hardware~~5V'''~~[[File~~| style="text-align:~~zero2w~~left;"|| style="text-align: left;"||-~~img81.png]]</li><li>Then use the keyboard~~| '~~s arrow keys to locate the position shown > in the figure below, and then use the~~ ''6'''| '''~~space~~GND''' ~~to select the &gt~~| style="text-align: left; ~~dtbo configuration of the SPI you want to open.</li></ol></li></ol>~~"|{| ~~class~~style="~~wikitable~~text-align: left;"|

|-

| '''~~dtbo configuration~~8'''| '''~~illustrate~~UART0_TX'''| '''PH0'''| '''224'''

|-

| '''~~spi1-cs0-cs1-spidev~~10'''| '''~~Open cs0 and cs1 of spi1 at the same time~~UART0_RX'''| '''PH1'''| '''225'''

|-

| '''~~spi1~~12'''| style="text-~~cs0-spidev~~align: left;"|| '''PI1'''| '''~~Only open cs0 of spi1~~257'''

|-

| '''~~spi1-cs1-spidev~~14'''| '''~~Only open cs1 of spi1~~GND'''|} ~~<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>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 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.root@orangepi:~/wiringOP-Python# '''cd examples'''</li></ol>~~ ~~root@orangepi:~/wiringOP-Python/examples# '''python3 spidev_test.py \'''~~ ~~'''--channel 1 --port 0'''~~ ~~spi mode: 0x0~~ ~~max speed: 500000 Hz (500 KHz)~~ ~~Opening device /dev/spidev1.1~~ ~~TX | FF FF FF FF FF FF '''40 00 00 00 00 95''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.......…~~| ~~RX | FF FF FF FF FF FF '''FF FF FF FF FF FF''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF |.............….~~| ~~<ol start="6"~~ style="~~list~~text-~~style-type~~align: ~~decimal~~left;"><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'''</li></ol>~~ ~~root@orangepi:~/wiringOP-Python/examples# '''python3 spidev_test.py \'''~~ ~~'''--channel 1 --port 0'''~~ ~~spi mode: 0x0~~ ~~max speed: 500000 Hz (500 KHz)~~ ~~Opening device /dev/spidev1.1~~ ~~TX | FF FF FF FF FF FF '''40 00 00 00 00 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 |......@.......…|~~ ~~=== 40pin I2C test ===~~ ~~# As can be seen from the table below, the i2c available for the 40pin interface are i2c0, i2c1 and i2c2~~ {| ~~class="wikitable"~~

|-

|-

| '''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'''|-~~SDA~~| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''3229'''|-| '''426'''| '''5VSPI1_CS1'''| '''PH9'''| '''233'''| ~~style="text~~-~~align: left;"~~|'''28'''| ~~style="text~~'''TWI2-~~align: left;"~~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'''| '''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>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="~~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 serial port you want to open.</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 - uart2'''| '''~~PH6'''| '''SPI1_CLK'''| '''23'''~~|~~| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229~~pi-uart2'''

|-

~~| style="text-align: left;"|| style="text-align: left;"|~~| '''~~GND~~40pin - uart3'''| '''~~25'''~~|~~| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''233~~pi-uart3'''

|-

| '''~~266'''| '''PI10'''| '''TWI2~~40pin -~~SDA/UART3_RX'''| '''27'''~~|~~| '''28~~uart4'''| '''~~TWI2~~pi-~~SCL/UART3_TX'''| '''PI9'''| '''265~~uart4'''

|-

| '''~~256~~40pin - uart5'''| '''~~PI0~~ph-uart5'''| } [[File:zero2w-img175.png]]</ol><ol start="5" style="~~text~~list-~~align~~style-type: ~~left~~lower-alpha;"|><li>Then select '''<Save>''' to save[[File:zero2w-img83.png]]</li>| <li>Then select '''29<Back>'''|[[File:zero2w-img84.png]]</li>| <li>Then select '''30<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 '''~~GND~~/dev'''{| class="wikitable" style="~~text~~background-~~align~~color: ~~left~~#ffffdc;width:800px;"|-| <big>'''Note that the linux5.4 system is /dev/ttyASx.'''</big>|}{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|

|-

| orangepi@orangepi:~$ '''~~271~~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 '''~~PI15~~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="~~text~~background-~~align~~color: ~~left~~#ffffdc;width:800px;"|~~| '''31'''~~|~~| '''32'''| '''PWM1'''| '''PI11'''| '''267'''~~

|-

~~| '''268'''| '''PI12'''| '''PWM2'''| '''33'''~~|| <big>'''34Note 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.'''</big>| ~~'''GND'''~~}{| ~~style~~class="~~text-align: left;~~wikitable"|| style="~~text-align~~width: ~~left~~800px;"|

|-

| orangepi@orangepi:~$ '''~~258~~gpio serial /dev/ttySx # linux-6.1 test command'''| orangepi@orangepi:~$ '''~~PI2~~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. <div style="display: flex;">::{| class="wikitable" style="width:390px;margin-right: 20px;text-align: ~~left~~center;"|-| '''35GPIO NO.'''|| '''36GPIO'''~~| style="text-align: left;"|~~| '''~~PC12~~Function'''| '''76Pin'''

|-

~~| '''272'''~~

~~| '''PI16'''~~

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

~~| '''37'''~~

|

~~| '''38'''~~

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

| '''~~PI4~~3.3V'''| '''~~260~~1'''|-| '''264'''| '''PI8'''| '''TWI1-SDA'''| '''3'''|-| '''263'''| '''PI7'''| '''TWI1-SCL'''| '''5'''|-| '''269'''| '''PI13'''| '''PWM3/UART4_TX'''| '''7'''

|-

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

| '''GND'''

| '''399'''|-| '''40226'''| ~~style="text-align: left;"|~~'''PH2'''| '''~~PI3~~UART5_TX'''| '''~~259~~11'''|} ~~<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~~227'''~~. Ordinary users remember to add >~~ | '''~~sudo~~PH3''' ~~permissions.orangepi@orangepi:~$~~ | '''~~sudo orangepi-config~~UART5_RX'''~~</li><li>Then select~~ | '''~~System~~13'''~~[[File:zero2w~~|-~~img80.png]]</li><li>Then select~~ | '''261'''| '''~~Hardware~~PI5'''~~[[File:zero2w-img81.png]]<~~| '''TWI0_SCL/~~p></li>~~UART2_TX'''~~<li>Then use the keyboard~~| '~~s arrow keys to locate the position shown > in the picture below, and then use the~~ ''15'~~space~~''~~' to select the > corresponding i2c configuration in the picture below.</li></ol></li></ol>~~|-| style="text-align: left;"|{| ~~class~~style="~~wikitable~~text-align: left;"|| '''3.3V'''| '''17'''

|-

| '''~~Multiplexing function in 40pin~~231'''| '''~~Corresponding dtbo configuration~~PH7'''| '''SPI1_MOSI'''| '''19'''

|-

| '''~~40pin - i2c0~~232'''| '''~~pi-i2c0~~PH8'''| '''SPI1_MISO'''| '''21'''

|-

| '''~~40pin - i2c1~~230'''| '''~~pi-i2c1~~PH6'''| '''SPI1_CLK'''| '''23'''

|-

| ~~'''40pin - i2c2'''| '''pi-i2c2'''~~|} ~~[[File:zero2w-img173.png]]~~ ~~<ol start="5"~~ style="~~list-style~~text-~~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~~text-~~style-type~~align: ~~decimal~~left;">|~~<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~~GND'''~~~~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>~~25'''~~In the above output'''</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"~~

|-

|-

| '''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;"|| '''~~3.3V~~37'''|-| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''39'''|}{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''Pin'''| '''Function'''| '''GPIO'''| '''1GPIO NO.'''|-

| '''2'''

| '''5V'''

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

|-

~~| '''264'''~~

~~| '''PI8'''~~

~~| '''TWI1-SDA'''~~

~~| '''3'''~~

|

| '''4'''

| '''5V'''

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

|-

~~| '''263'''~~

~~| '''PI7'''~~

~~| '''TWI1-SCL'''~~

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

|

| '''6'''

| '''GND'''

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

|-

~~| '''269'''~~

~~| '''PI13'''~~

~~| '''PWM3/UART4_TX'''~~

~~| '''7'''~~

|

| '''8'''

| '''UART0_TX'''

| '''224'''

|-

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

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

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

|

| '''10'''

| '''UART0_RX'''

| '''225'''

|-

~~| '''226'''~~

~~| '''PH2'''~~

~~| '''UART5_TX'''~~

~~| '''11'''~~

|

| '''12'''

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

| '''257'''

|-

~~| '''227'''~~

~~| '''PH3'''~~

~~| '''UART5_RX'''~~

~~| '''13'''~~

|

| '''14'''

| '''GND'''

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

|-

| '''~~261'''| '''PI5'''| '''TWI0_SCL~~16</~~UART2_TX'''| '''15'''~~|~~| '''16~~span>'''| '''PWM4/UART4_RX'''| '''PI14'''| '''270'''

|-

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

~~| '''3.3V'''~~

~~| '''17'''~~

|

| '''18'''

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

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

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

~~| '''25'''~~

|

| '''26'''

| '''SPI1_CS1'''

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

| '''PC12'''

| '''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, uart~~ 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 ~~picture~~ figure below, and then use the '''space''' to select the ~~> serial port~~ configuration corresponding to the pwm you want to open.</p~~></li></ol~~><~~/li></ol~~p> ~~{| class="wikitable"~~|-~~| '''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~~img176.png]] <~~ol start="5" style="list-style-type: lower-alpha;"~~/p></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

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

|-

|

<big>'''Please execute the following commands under the root user.'''</big>

|}

<li>Enter the following command on the command line to make pwm1 output a 50Hz square wave

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

|-

|

root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip0/export'''

root@orangepi:~# '''echo 20000000 > /sys/class/pwm/pwmchip0/pwm1/period'''

root@orangepi:~# '''echo 1000000 > /sys/class/pwm/pwmchip0/pwm1/duty_cycle'''

root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip0/pwm1/enable'''

|}

</li>

<li>Enter the following command on the command line to make pwm2 output a 50Hz square wave</li>

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

|-

|

root@orangepi:~# '''echo 2 > /sys/class/pwm/pwmchip0/export'''

~~<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''''''注意, linux5.4系统为/dev/ttyASx.'''orangepi~~root@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: -~~echo 20000000 > 0~~Out: 1: -> 1<~~sys/p>~~Out: 2: -> 2<~~class/p>~~Out: 3: -> 3^C<~~pwm/~~p><~~pwmchip0/~~li>~~<li>Finally, you can run the '''serialTest.py''' program in examples to test the loopback function of the serial port. If you can see the following print, it means that the serial port loopback test is normal.~~'''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.'''root@orangepi:~/wiringOP-Python# '''cd examples'''root@orangepi:~/wiringOP-Python/examples# '''python3 serialTest.py --device "/dev/ttySx" # linux6.1 use'''<~~pwm2/p>~~root@orangepi:~/wiringOP-Python/examples#~~ period'''~~python3 serialTest.py --device "/dev/ttyASx" # linux5.4 use'''Out: 0: -> 0Out: 1: -> 1Out: 2: -> 2Out: 3: -> 3Out: 4:^Cexit</li></ol>~~ ~~== Hardware watchdog test ==~~

~~The watchdog_test program is pre-installed in the Linux system released by Orange Pi and can be tested directly.~~root@orangepi:~# '''echo 1000000 > /sys/class/pwm/pwmchip0/pwm2/duty_cycle'''

~~The method~~ root@orangepi:~# '''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 ~~run the watchdog_test program is as follows~~make pwm3 output a 50Hz square wave</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''echo 3 > /sys/class/pwm/pwmchip0/export'''

~~<ol style="list-style-type: lower-alpha;"><li>The second parameter 10 represents the counting time of the watchdog. If the dog is not fed within this time, the system will restart.</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 "keep alive" to indicate that the dog feeding is successful.~~orangepi~~root@orangepi:~$ # '''~~sudo watchdog_test 10'''open success<~~echo 20000000 > /p>~~options is 33152,identity is sunxi-wdt<~~sys/p>~~put_usr return,if 0,success:0<~~class/p>~~The old reset time is: 16<~~pwm/p>~~return ENOTTY,if -1,success:0<~~pwmchip0/p>~~return ENOTTY,if -1,success:0<~~pwm3/p>~~put_user return,if 0,success:0put_usr return,if 0,success:0keep alivekeep alivekeep alive</li></ol>~~period'''

~~<~~root@orangepi:~# '''echo 1000000 > /~~span>== Check the chipid of H618 chip ==~~sys/class/pwm/pwmchip0/pwm3/duty_cycle'''

~~The~~ root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip0/pwm3/enable'''|}</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Enter the following command ~~to view~~ on the ~~H618 chip chipid is as follows. The chipid of each chip is different, so you can use chipid~~ command line to ~~distinguish multiple development boards.~~make pwm4 output a 50Hz square wave</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~# '''echo 4 > /sys/class/pwm/pwmchip0/export''' root@orangepi:~# '''echo 20000000 > /sys/class/pwm/pwmchip0/pwm4/period'''

~~orangepi~~root@orangepi:~$ # '''~~cat~~ echo 1000000 > /sys/class/~~sunxi_info~~pwm/~~sys_info | grep "chipid"~~pwmchip0/pwm4/duty_cycle'''

~~sunxi_chipid~~ root@orangepi: ~~338020004c0048080147478824681ed1~~~# '''echo 1 > /sys/class/pwm/pwmchip0/pwm4/enable'''|}

<~~span id~~div class="~~python-related-instructions~~figure">~~== Python related instructions ==~~

~~=== How to compile and install Python source code ===~~img177.png]]

~~'''If the Python version in the Ubuntu or Debian system software repository you are using does not meet the development requirements~~ </div></ol></li></ol><span id="how-to-install-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 the latest version of Python.'''~~-wiringop-python">

~~'''The following demonstration is~~ == How to ~~compile and~~ install ~~the latest version of Python 3.9. If you want to compile~~ and ~~install other versions of~~ use wiringOP-Python~~, the method is the same (you need to download the source code corresponding to the Python you want to install).'''~~==

~~<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">~~<li>First install the dependency packages needed to compile Pythonorangepi@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 \'''~~| <pbig>'''~~libreadline-dev libffi-dev curl libbz2-dev'''</li><li>Then download~~ Note: The pin header on the ~~latest version of Python3.9 source code~~ 40pin interface is not soldered by default, and ~~unzip~~ you need to solder it~~orangepi@orangepi:~$ '''wget \~~yourself before it can be used.'''</pbig>~~[https://www.python.org/ftp/python/3.9.10/Python~~|}{| class="wikitable" style="background-~~3.9.10.tgz '''https~~color:~~//www.python.org/ftp/python/3.9.10/Python-3.9.10.tgz''']orangepi@orangepi~~#ffffdc;width:~~~$ '''tar xvf Python-3.9.10.tgz'''</li><li>Then run the configuration command~~800px;" ~~orangepi@orangepi:~$ '''cd Python~~|-~~3.9.10'''orangepi@orangepi:~$ '''./configure --enable-optimizations'''</li><li>Then compile and install Python3.9. The compilation time takes about half an hour.~~| <pbig>~~orangepi@orangepi:~$~~ '''~~make~~ wiringOP-~~j4'''orangepi@orangepi:~$ '''sudo make altinstall'''</li><li>After installation, you can use the following command to check~~ Python is the Python language version ~~number~~ of wiringOP library, used to operate the ~~Python you just installed.orangepi@orangepi:~$ '''python3.9 --version'''''~~development board's GPIO, I2C, SPI, UART and other hardware resources in the Python ~~3.9.10''~~program'~~</li><li>Then update piporangepi@orangepi:~$~~ ''~~'/usr/local/bin/python3.9 -m pip install --upgrade pip'''</li></ol>~~

~~~~'''Also please note that all the following commands are operated under the root user.'''</~~span~~big>~~=== 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 === How to install ~~the~~ wiringOP-Python ~~library, please remember to change the pip source.'''~~===

<li>First install ~~'''python3-pip'''~~dependency packages{| class="wikitable" style="width:800px;" |-| ~~orangepi~~root@orangepi:~$ # '''sudo apt-get update'''~~orangepi~~root@orangepi:~$ # '''sudo apt-get ~~install~~ -y install git swig 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~~ dev python3-~~p ~/.pip~~setuptools'''~~orangepi@orangepi:~$ '''cat <<EOF > ~/.pip/pip.conf''''''[global]''''''timeout = 6000''''''index-url = https://pypi.tuna.tsinghua.edu.cn/simple''''''trusted-host = pypi.tuna.tsinghua.edu.cn''''''EOF'''</li><li>Then use pip3 to install the Python library very quickly</li></ol>~~|}

</li>

<li>~~How~~ Then use the following command to ~~temporarily change~~ download the ~~pip~~ source ~~under Linux, where '''<packagename>''' needs to be replaced with a specific package name~~code of wiringOP-Python<p/li>~~orangepi@orangepi~~{| class="wikitable" style="background-color:~~~$ '''pip3 install &lt~~#ffffdc;~~packagename&gt~~width:800px; " |-~~i \'''~~| <pbig>'''~~https://pypi.tuna.tsinghua.edu.cn/simple~~ Note that the following git clone--~~trusted~~recursive command will automatically download the source code of wiringOP, because wiringOP-~~host pypi~~Python depends on wiringOP.~~tuna.tsinghua.edu~~Please make sure there are no errors during the download process due to network problems.cn'''~~</li></ol>~~

~~<span id="how~~'''If there is a problem downloading the code from GitHub, you can directly use the wiringOP-~~to-install~~Python source code that comes with the Linux image. The storage location is: /usr/src/wiringOP-~~docker">~~Python'''</~~span~~big>|}{| class="wikitable" style= ~~How to install Docker ==~~"width:800px;" |-| root@orangepi:~# '''git clone --recursive https://github.com/orangepi-xunlong/wiringOP-Python -b next'''

~~The Linux image provided by Orange Pi has Docker pre-installed, but the Docker service is not turned on by default. Use the~~ root@orangepi:~# '''~~enable_docker.sh~~cd wiringOP-Python''' ~~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.~~

root@orangepi:~/wiringOP-Python# '''git submodule update --init --remote'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Then use the following command to compile wiringOP-Python and install it into the Linux system of the development board{| class="wikitable" style="width:800px;" |-| root@orangepi:~$ # '''~~enable_docker~~cd wiringOP-Python'''root@orangepi:~/wiringOP-Python# '''python3 generate-bindings.shpy > bindings.i'''root@orangepi:~/wiringOP-Python# '''sudo 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 '''q''' key to exit the help information interface.</li>{| class="wikitable" style="width:800px;" |-| root@orangepi:~/wiringOP-Python# '''python3 -c "import wiringpi; help(wiringpi)"'''

~~You can use the following command to test docker. If '''hello-world''' can be run, docker can be used normally.~~Help on module wiringpi:

~~orangepi@orangepi:~$ '''docker run hello-world'''~~

~~Unable to find image 'hello-world:latest' locally~~NAME

~~latest~~: ~~Pulling from library/hello-world~~wiringpi

~~256ab8fe8778: Pull complete~~

~~Digest: sha256:7f0a9f93b4aa3022c3a4c147a449ef11e0941a1fd0bf4a8e6c9408b2600777c5~~DESCRIPTION

~~Status~~: ~~Downloaded newer image for hello-world~~# This file was automatically generated by SWIG (http:~~latest~~//www.swig.org).

~~'''Hello from Docker!'''~~: # Version 4.0.2

~~'''This message shows that your installation appears to be working correctly.'''~~: #

~~'''.….'''~~: # Do not make changes to this file unless you know what you are doing--modify

~~When using~~ : # the ~~docker~~ SWIG interface file instead.|}</ol><ol start="5" style="list-style-type: decimal;"><li>The steps to test whether wiringOP-Python is installed successfully under the python command~~, if you~~ line are ~~prompted for '''permission denied''', please add~~ as follows:<ol style="list-style-type: lower-alpha;"><li>First use the ~~current user~~ python3 command to enter the ~~docker user group so that you can run the docker~~ command ~~without sudo.~~line mode of > python3</li>{| class="wikitable" style="width:800px;" |-| ~~orangepi~~root@orangepi:~$ # '''~~sudo usermod -aG docker $USER~~python3'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>Then import the python module of wiringpi</li>{| class="wikitable" style="width:800px;" |-| >>> '''~~Note: You need to log out and log in again to the system to take effect. You can also restart the system.~~import wiringpi;'''|}<~~span id~~/ol><ol start="~~how~~3" style="list-tostyle-~~install-home~~type: lower-~~assistant~~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.</~~span~~li>{| class="wikitable" style= ~~How to install Home Assistant ==~~"width:800px;" |-| >>> '''help(wiringpi)'''

'''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.'''Help on module wiringpi:

~~~~

~~=== 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''']] section.</li>~~<li>Then you can search for the docker image of Home Assistantorangepi@orangepi:~$ '''docker search homeassistant'''</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.~~orangepi@orangepi:~$ '''docker pull homeassistant/home-assistant'''Using default tag: latestlatest: Pulling from homeassistant/home-assistantbe307f383ecc: Downloading5fbc4c07ac88: Download complete'''...... (Omit some output)'''3cc6a1510c9f: Pull complete7a4e4d5b979f: Pull completeDigest: sha256:81d381f5008c082a37da97d8b08dd8b358dae7ecf49e62ce3ef1eeaefc4381bbStatus: Downloaded newer image for homeassistant/home-assistant:latestdocker.io/homeassistant/home-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'''REPOSITORY TAG IMAGE ID CREATED SIZEhomeassistant/home-assistant latest bfa0ab9e1cf5 2 months ago '''1.17GB'''</li><li>At this point you can run the Home Assistant docker containerorangepi@orangepi:~$ '''docker run -d \''''''--name homeassistant \''''''--privileged \''''''--restart=unless-stopped \''''''-e TZ=Asia/Shanghai \''''''-v /home/orangepi/home-assistant:/config \''''''--network=host \''''''homeassistant/home-assistant:latest'''</li><li>Then enter【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.'''~~<div class="figure">~~NAME

~~[[File~~:~~zero2w-img180.png]]~~wiringpi

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

~~<li>Then enter your '''name, username''' and '''password''' and click '''Create Account'''~~

~~<div class="figure">~~

~~[[File:zero2w-img181.png]]~~DESCRIPTION

<: # This file was automatically generated by SWIG (http:/~~div><~~/~~li><li>Then follow the interface prompts to set according to your own preferences, and then click Next<div class="figure">~~www.swig.org).

~~[[File~~:~~zero2w-img182~~# Version 4.~~png]]~~0.2

~~</div></li><li>Then click Next<div class="figure">~~: #

~~[[File~~:~~zero2w~~# Do not make changes to this file unless you know what you are doing-~~img183.png]]~~-modify

~~</div></li><li>Then click Finish<div class="figure">~~: # the SWIG interface file instead.

~~[[File:zero2w-img184.png]]~~

~~</div></li><li>The main interface finally displayed by Home Assistant is as shown below[[File:zero2w-img185.png]]</li><li>Method to stop Home Assistant container<ol style="list-style-type: lower-alpha;"><li>The command to view the docker container is as followsorangepi@orangepi:~$ '''docker ps -a'''</li><li>The command to stop the Home Assistant container is as followsorangepi@orangepi:~$ '''docker stop homeassistant'''</li><li>The command to delete the Home Assistant container is as followsorangepi@orangepi:~$ '''docker rm homeassistant'''</li></ol></li></ol>~~CLASSES

~~=== Installation via python ===~~:builtins.object

'''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]]"'''::GPIO

~~<ol style="list-style-type~~: ~~decimal;"><li>First install dependency packagesorangepi@orangepi~~:~~~$ '''sudo apt-get update'''orangepi@orangepi:~$ '''sudo apt-get install -y python3 python3-dev python3-venv \''''''python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential \''''''libopenjp2-7 libtiff5 libturbojpeg0-dev tzdata''''''If it is debian12, please use the following command:'''orangepi@orangepi:~$ '''sudo apt-get update'''orangepi@orangepi:~$ '''sudo apt-get install -y python3 python3-dev python3-venv \''''''python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential \''''''libopenjp2-7 libturbojpeg0-dev tzdata'''</li><li>Then you need to compile and install Python3.9. For the method, please refer to the [[\l|'''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.''''''The default Python version of Ubuntu Jammy is Python3.10, so there is no need to compile and install it.''''''The default Python version of Debian Bookworm is Python3.11, so there is no need to compile and install it.'''</li><li>Then create a Python virtual environment'''Debian Bookworm is python3.11, please remember to replace the corresponding command.'''orangepi@orangepi:~$ '''sudo mkdir /srv/homeassistant'''orangepi@orangepi:~$ '''sudo chown orangepi:orangepi /srv/homeassistant'''orangepi@orangepi:~$ '''cd /srv/homeassistant'''orangepi@orangepi:~$ '''python3.9 -m venv .'''orangepi@orangepi:~$ '''source bin/activate'''(homeassistant) orangepi@orangepi:/srv/homeassistant$</li><li>Then install the required Python packages(homeassistant) orangepi@orangepi:/srv/homeassistant$ '''python3 -m pip install wheel'''</li><li>Then you can install Home Assistant Core(homeassistant) orangepi@orangepi:/srv/homeassistant$ '''pip3 install homeassistant'''</li><li>Then enter the following command to run Home Assistant Core(homeassistant) orangepi@orangepi:/srv/homeassistant$ '''hass'''</li><li>Then enter【'''development board IP address: 8123'''】 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.'''~~<div class="figure">~~I2C

~~[[File~~:~~zero2w-img180.png]]~~:Serial

~~</div></li></ol>~~::nes

~~~~

~~== OpenCV installation method ==~~

~~=== Use apt to install OpenCV ===~~:class GPIO(builtins.object)

~~<ol style="list-style-type~~: ~~decimal;"><li>The installation command is as followsorangepi@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~~| GPIO(pinmode=~~"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__)"''''''4.5.4'''</li><li>The version of OpenCV in Ubuntu20.04 is as follows:orangepi@orangepi:~$ '''python3 -c "import cv2; print(cv2.__version__)"''''''4.2.~~0~~'''</li><li>The version of OpenCV in Debian11 is as follows:orangepi@orangepi:~$ '''python3 -c "import cv2; print(cv2.__version__~~)~~"''''''4.5.1'''</li><li>The version of OpenCV in Debian12 is as follows:orangepi@orangepi:~$ '''python3 -c "import cv2; print(cv2.__version__)"''''''4.6.0'''</li></ol></li></ol>~~

~~== Set up the Chinese environment and install the Chinese input method ==~~:|

~~'''Note, before installing the Chinese input method, please make sure that the Linux system used by the development board is a desktop version.'''~~

>>>|}</ol></li></ol>~~=== Debian system installation method ===~~

~~<ol style~~=~~"list-style-type: decimal;"><li>First set the default '''locale''' to Chinese<ol style~~=~~"list-style-type: lower-alpha;"><li>Enter the following command to start configuring '''locale'''orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''</li>~~<li>Then select '''zh_CN.UTF-8 UTF-8''' in the pop-up interface (use > the up and down keys on the keyboard to move up and down, use > the space bar to select, and finally use the Tab key to move > the cursor to '''<OK>''', and then return Car can be used)~~[[File:zero2w-img186.png]]</li><li>Then set the default '''locale''' to '''zh_CN.UTF-8'''[[File:zero2w-img187.png]]</li><li>After exiting the interface, the '''locale''' setting will begin. > The output displayed on the command line is as follows:orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''Generating locales (this might take a while)...en_US.UTF-8... donezh_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">~~40pin GPIO port test ===

~~[[File~~{| class="wikitable" style="background-color:~~zero2w~~#ffffdc;width:800px;" |-| <big>'''Like wiringOP, wiringOP-Python can also determine which GPIO pin to operate by specifying the wPi number. Because there is no command to view the wPi number in wiringOP-~~img195~~Python, you can only view the board's wPi number and physics through the gpio command in wiringOP Correspondence of pins.~~png]]~~'''</big>

~~</div></li><li>Then put '''Google Pinyin''' on top[[File:zero2w-img196.png]]~~[[File:zero2w-~~img197~~img170.png|center]]~~</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'''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>~~ ~~=== Installation method of Ubuntu 20.04 system ===~~|}

<li>~~First open '''Language Support'''~~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-~~img201~~img171.png]]</li><li>~~Then find the '''Chinese (China)''' option~~The steps for testing directly with commands are as follows:<~~p>[[File~~ol style="list-style-type:~~zero2w~~lower-~~img202.png]]</li~~alpha;"><li>~~Then please use~~ First set the GPIO port to output mode, where the ~~left button~~ first parameter of the ~~mouse to select~~ '''~~Chinese (China)~~pinMode''' ~~and hold it down, then drag it up~~ function is the serial number of the wPi corresponding to the ~~starting position. After dragging~~pin, and the second parameter is the ~~display will be as shown below:~~GPIO mode.~~[[File~~{| class="wikitable" style="width:~~zero2w~~800px;" |-~~img203.png]]~~| <root@orangepi:~/~~li></ol>~~ wiringOP-Python# '''~~Note that this step is not easy to drag, please be patient and try it a few times.~~python3 -c "import wiringpi; \''' <~~ol start="4" style="list-style-type: decimal;"~~/p>~~<li>~~~~Then select~~ '''~~Apply System-Wide~~from wiringpi import GPIO; wiringpi.wiringPiSetup() ; \''' ~~to apply the Chinese settings to the entire system~~~~[[File~~'''wiringpi.pinMode(2, GPIO.~~png]]~~OUTPUT) ; "'''|}</li><li>Then set the ~~'''Keyboard input method system''' system~~ GPIO port to output a low level. After setting, you can use a multimeter to ~~'''fcitx'''~~measure the voltage value of the pin. If it is 0v, it means the low level is set successfully.~~[[File~~{| class="wikitable" style="width:~~zero2w~~800px;" |-~~img205.png]]~~| <root@orangepi:~/~~li><li>~~wiringOP-Python# '''~~Then restart the Linux system to make the configuration take effect~~python3 -c "import wiringpi; \'''</p~~></li~~>~~<li>~~~~After re-entering the system, please select~~ '''~~Do not ask me again~~from wiringpi import GPIO; wiringpi.wiringPiSetup() ;\''' ~~in the following interface, and then please decide according to your own preferences whether the standard folder should also be updated to Chinese~~~~[[File~~'''wiringpi.digitalWrite(2, GPIO.~~png]]~~LOW)"'''|}</li><li>Then set the GPIO port to output a high level. After setting, you can ~~see that~~ use a multimeter to measure the voltage value of the pin. If it is 3.3v, it means the setting of the ~~desktop~~ high level is ~~displayed in Chinese~~successful.~~[[File~~{| class="wikitable" style="width:~~zero2w~~800px;" |-~~img207.png]]~~| <root@orangepi:~/~~li><li>Then we can open~~ wiringOP-Python# '''~~Geany~~python3 -c "import wiringpi; \''' ~~to test the Chinese input method. The opening method is as shown in the figure below~~~~[[File:zero2w-img208~~'''from wiringpi import GPIO; wiringpi.~~png]]~~wiringPiSetup() ;\'''</p~~></li~~>~~<li>~~~~After opening '''Geany~~'''wiringpi.digitalWrite(2, ~~the English input method is still the default~~GPIO. ~~We can switch to the Chinese input method through the '''Ctrl+Space~~HIGH)"''' ~~shortcut key, and then we can input Chinese.~~|}<p/li>~~[[File:zero2w-img209.png]]~~</pol></li><~~/ol~~li> <~~span id="installation-method-~~p>The steps for testing in the command line of~~-ubuntu-22.04-system">~~python3 are as follows:</~~span~~p>~~=== Installation method of Ubuntu 22.04 system ===~~ <ol style="list-style-type: ~~decimal~~lower-alpha;"><li>First ~~open '''Language Support'''~~use the python3 command to enter the command line mode of python3{| class="wikitable" style="width:800px;" |-| ~~[[File~~root@orangepi:~~zero2w-img201.png]]~~~# '''python3'''|}</li><li>Then ~~find~~ import the python module of wiringpi{| class="wikitable" style="width:800px;" |-| >>> '''~~Chinese (China)~~import wiringpi''' ~~option~~~~[[File:zero2w-img210.png]]~~>>> '''from wiringpi import GPIO'''|}</li><li>Then ~~please use~~ set the GPIO port to output mode, where the ~~left button~~ first parameter of the ~~mouse to select~~ '''~~Chinese (China)~~pinMode''' ~~and hold it down, then drag it up~~ function is the serial number of the wPi corresponding to the ~~starting position. After dragging~~pin, and the second parameter is the ~~display will be as shown below:~~GPIO mode.{| class="wikitable" style="width:800px;" |-| ~~[[File:zero2w-img211~~>>> '''wiringpi.~~png]]~~wiringPiSetup()'''<~~/li~~p>0</olp> >>> '''~~Note that this step is not easy to drag~~wiringpi.pinMode(2, ~~please be patient and try it a few times~~GPIO.OUTPUT)'''|}<~~ol start="4" style="list-style-type: decimal;"~~/li><li>Then ~~select '''Apply System-Wide'''~~ set the GPIO port to output a low level. After setting, you can use a multimeter to ~~apply~~ measure the voltage value of the ~~Chinese settings to~~ pin. If it is 0v, it means the ~~entire system~~low level is set successfully.{| class="wikitable" style="width:800px;" |-| ~~[[File~~>>> '''wiringpi.digitalWrite(2, GPIO.~~png]]~~LOW)'''|}</li><li>~~'''~~Then ~~restart~~ set the ~~Linux system~~ GPIO port to ~~make~~ 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 ~~configuration take effect~~high level is successful.{| class="wikitable" style="width:800px;" |-| >>> '''wiringpi.digitalWrite(2, GPIO.HIGH)'''|}</li></ol></li><li>~~After re~~For wiringOP-~~entering~~ Python to set the GPIO high and low levels in the ~~system~~python code, ~~please select~~ you can refer to the '''~~Do not ask me again~~blink.py''' test program in the ~~following interface, and then please decide whether~~ examples. The '''blink.py''' test program will set the voltage of all GPIO ports in the 40 Pin of the ~~standard folder should also be updated~~ development board to ~~Chinese according to your own preferences~~continuously change high and low.~~[[File~~{| class="wikitable" style="width:~~zero2w~~800px;" |-~~img206.png]]~~| <root@orangepi:~/~~li><li>Then you can see that the desktop is displayed in Chinese~~wiringOP-Python# '''cd examples'''~~[[File~~root@orangepi:~~zero2w~~~/wiringOP-~~img207~~Python/examples# '''ls blink.~~png]]~~py'''</p~~></li~~>~~<li>~~~~Then open the Fcitx5 configuration program~~'''blink.py'''~~[[File~~root@orangepi:~~zero2w~~~/wiringOP-~~img213~~Python/examples'''# python3 blink.~~png]]~~py'''|}</li>~~<li>Then choose to use Pinyin input method~~~~<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~~ === 40pin SPI 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 enter Chinese.[[File:zero2w-img216.png]]</li></ol>~~===

~~== How to remotely log in to~~ table below, the ~~Linux system desktop ==~~spi available for the 40pin interface is spi1, and there are two chip select pins cs0 and cs1

<~~span id~~div style="~~remote-login-using-nomachine~~display: flex;"~~></span~~>::{| class="wikitable" style=~~= Remote login using NoMachine ===~~"width:390px;margin-right: 20px;text-align: center;"|-| '''~~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~~GPIO NO. ~~It is strongly recommended to read this document thoroughly to become familiar with the use of NoMachine. The document link is as follows:~~''' | '''~~https://knowledgebase.nomachine.com/DT10R00166~~GPIO''' | '''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 NoMachineFunction'~~s official documentation.~~''' | '''Before operating, please make sure that the Windwos computer and the development board are in the same LAN, and that you can log in to the Ubuntu or Debian system of the development board through ssh normally.Pin'''|-~~<ol~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">|~~<li>First download the installation package of the NoMachine software Linux '''arm64''' deb version, and then install it into the Linux system of the development board<ol~~ | style="~~list~~text-~~style-type~~align: ~~lower-alpha~~left;">|~~<li>Since H618 is an ARMv8 architecture SOC and the system we use is > Ubuntu or Debian, we need to download the~~ | '''3.3V'~~NoMachine for ARM > ARMv8 DEB~~''| '''1''' ~~installation package. The download link is as > follows:</li></ol></li></ol>~~|-| '''264'''| '''~~Note that this download link may change, please look for the Armv8/Arm64 version of the deb package.~~PI8'''| '''TWI1-SDA'''~~[https://www.nomachine.com/download/download&id=112&s=ARM~~ | '''~~https://downloads.nomachine.com/download/?id=118&distro=ARM~~3''']|-~~[[File:zero2w-img217.png]]~~ ~~<ol start="2" style="list-style-type: lower-alpha;"><li>In addition, you can also download the~~ | '''263'~~NoMachine~~''| '''PI7''' ~~installation > package from the official tool.[[File:zero2w~~| '''TWI1-~~img218.png]]~~SCL'''~~First enter the~~ | '''~~remote login software-NoMachine~~5''' ~~folder[[File:zero2w-img219.png]]~~|-| '''269'''~~Then download the arm64 version of the deb installation package~~| '''PI13'''~~[[File:zero2w-img220.png]]</li><li>Then upload the downloaded~~ | '''~~nomachine_x.x.x_x_arm64.deb~~PWM3/UART4_TX''' ~~to the > Linux system of the development board</li><li>Then use the following command to install~~ | '''~~NoMachine~~7''' ~~in the Linux &gt~~|-| style="text-align: left; ~~system of the development board~~"|~~orangepi@orangepi~~| style="text-align:~$ left;"|| '''GND'~~sudo dpkg -i nomachine_x.x.x_x_arm64_arm64.deb~~''| '''9'''~~</li></ol>~~ ~~~~<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>~~| '''226'''| '''~~Note that this download link may change.~~PH2''' | '''UART5_TX''~~https://downloads.nomachine.com/download/?id=9~~'| '''11''' ~~[[File:zero2w~~|-~~img221.png]]~~| '''227'''~~<ol start="3" style="list-style-type: decimal;">~~| '''PH3'''~~<li>Then install NoMachine in Windows.~~ | '''~~Please restart your computer after installation.~~UART5_RX'''~~</li><li>Then open~~ | '''~~NoMachine~~13''' ~~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.| '''261'''~~[[File:zero2w-img223.png]]</li>~~| '''PI5'''~~<li>Then click~~ | '''OKTWI0_SCL/UART2_TX'''~~[[File~~| '''15'''|-| style="text-align:~~zero2w~~left;"|| style="text-~~img224.png]]</li>~~align: left;"|~~<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~~| '''3.~~~~3V'''| '''17'''~~[[File:zero2w~~|-~~img225.png]]~~| '''</pspan style="color:#FF0000">231</lispan>'''| '''<~~li><p~~span style="color:#FF0000">~~Then click OK in the next interface.~~PH7</~~p></li~~span>'''| '''<lispan style="color:#FF0000">~~Finally you can see the desktop of the development board Linux system~~SPI1_MOSI</pspan>'''| '''<~~p>[[File~~span style="color:~~zero2w-img226.png]]</p~~#FF0000">19</~~li></ol~~span>'''|-| '''232'''| '''PH8''Before operating, please make sure that the Windwos computer and the development board are in the same LAN, and that you can log in to the Ubuntu or Debian system of the development board through ssh normally.''' | '''~~There are many problems with VNC testing in Ubuntu20.04, please do not use this method.'''~~ <ol span style="~~list-style-type~~color: ~~decimal;~~#FF0000">SPI1_MISO<~~li><p~~/span>~~First run the~~ '''~~set_vnc.sh~~| ''' ~~script to set up vnc,~~ 21'''~~remember to add sudo permission~~|-| '''s</pspan style="color:#FF0000">230<p/span>~~orangepi@orangepi:~$~~ '''~~sudo set_vnc.sh~~| '''<~~/p>~~<pspan style="color:#FF0000">~~You will require a password to access your desktops.~~PH6</pspan>~~Password:~~ ''~~'#Set the vnc password here, 8 characters~~'| '''</pspan style="color:#FF0000">SPI1_CLK<p/span>~~Verify:~~ '''~~#Set the vnc password here, 8 characters~~| '''<~~/p>~~span style="color:#FF0000">23<p/span>~~Would you like to enter a view-only password (y/n)?~~ '''n|-| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''25'''~~xauth: file /root/.Xauthority does not exist~~|-~~New~~ | '''266''X' ~~desktop is orangepi:1Creating default startup script /root/.vnc/xstartup~~| '''PI10'''~~Starting applications specified in~~ | '''TWI2-SDA/~~root/.vnc/xstartup~~UART3_RX'''~~Log file is /root/.vnc/orangepi:1.logKilling Xtightvnc process ID 3047New~~ | '''27''X' ~~desktop is orangepi:1Starting applications specified in /root/.vnc/xstartup~~|-~~Log file is /root/.vnc/orangepi:1.log</li>~~| '''256'''~~<li>The steps to use MobaXterm software to connect to the development board Linux system desktop are as follows:~~| '''PI0'''~~<ol~~ | style="~~list-style~~text-~~type~~align: ~~lower-alpha~~left;">|~~<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>~~| '''29'''~~</li></ol>~~|- ~~<div class~~| '''271'''| '''PI15'''| style="~~figure~~text-align: left;">|| '''31'''~~[[File:zero2w~~|-~~img227.png]]~~| '''268'''| '''PI12'''~~</div><ol start="2" style="list-style-type: lower-alpha;">~~| '''PWM2'''~~<li>Then enter the VNC password set earlier~~| '''33'''~~[[File:zero2w~~|-~~img228.png]]</li><li>After successful login, the interface is displayed as shown below, &gt~~| '''258'''| '''PI2'''| style="text-align: left; ~~and then you can remotely operate the desktop of the development > board Linux system.</li></ol>~~"|| '''35'''~~[[File:zero2w~~|-~~img229.png]]~~| '''272'''~~~~|~~== QT installation method ==~~| '''37'''|-~~<ol~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">|~~<li>Use the following script to install QT5 and QT Creator~~| style="text-align: left;"|~~orangepi@orangepi:~$~~ | '''~~install_qt.sh~~GND'''~~</li><li>After installation, the QT version number will be automatically printed.~~| '''39'''|}~~<ol~~ {| class="wikitable" style="~~list~~width:390px;margin-~~style~~right: 20px;text-~~type~~align: ~~lower-alpha~~center;">~~<li>The qt version that comes with Ubuntu20.04 is~~ |-| '''Pin'''| '''~~5.12.8~~Function'''~~orangepi@orangepi:~$~~ | '''~~install_qt.sh~~GPIO'''~~~~| '''GPIO NO.~~.....~~'''~~QMake version 3.1~~|-~~Using Qt version~~ | '''~~5.12.8~~2''' ~~in /usr/lib/aarch64-linux-gnu</li><li>The QT version that comes with Ubuntu22.04 is~~ | '''~~5.15.3~~5V'''~~orangepi@orangepi~~| style="text-align:~$ left;"|| style="text-align: left;"||-| '''~~install_qt.sh~~4'''~~......QMake version 3.1Using Qt version~~ | '''5V'''~~'5.15.3~~| style="text-align: left;"|| style="text-align: left;"||-| '''6'''| ' ~~in /usr/lib/aarch64-linux-gnu</li><li>The QT version that comes with Debian11 is~~ ''GND'~~5.15.2~~''~~'orangepi@orangepi~~| style="text-align:~~~$ ''~~left;"|| style="text-align: left;"||-| '~~install_qt.sh~~''8'''~~......~~| '''UART0_TX'''~~QMake version 3.1~~| '''PH0'''~~Using Qt version~~ | '''~~5.15.2~~224''' ~~in /usr/lib/aarch64-linux~~|-~~gnu</li><li>The QT version that comes with Debian12 is~~ | '''~~5.15.8~~10'''~~orangepi@orangepi:~$~~ | '''~~install_qt.sh~~UART0_RX'''~~......QMake version 3.1Using Qt version~~ | '''~~5.15.8~~PH1''' ~~in /usr/lib/aarch64-linux~~| '''225'''|-~~gnu</li></ol></li><li>Then you can see the QT Creator startup icon in~~ | '''~~Applications~~12'''~~[[File~~| style="text-align:~~zero2w-img230.png]]~~left;"|~~You can also use the following command to open QT Creatororangepi@orangepi:~$~~ | '''PI1'~~qtcreator~~''| '''257'''~~</li><li>The interface after QT Creator is opened is as follows[[File:zero2w~~|-~~img231.png]]</li><li>The version of QT Creator is as follows~~| '''14'''| '''GND'''~~<ol~~ | style="~~list~~text-align: left;"|| style="text-~~type~~align: ~~lower-alpha~~left;">||-~~<li>The default version of QT Creator in~~ | '''~~Ubuntu20.04~~16''' ~~is as > follows[[File:zero2w-img232.png]]</li><li>The default version of QT Creator in~~ | '''~~Ubuntu22.04~~PWM4/UART4_RX''' ~~is as > follows[[File:zero2w-img233.png]]</li>~~| '''PI14'''~~<li>The default version of QT Creator in~~ | '''~~Debian11~~270''' ~~is as follows[[File:zero2w~~|-~~img234.png]]</li><li>The default version of QT Creator in~~ | '''~~Debian12~~18''' ~~is as follows[[File~~| style="text-align:~~zero2w-img235.png]]</li></ol>~~left;"|~~</li>~~| '''PH4'''~~<li>Then set up QT~~| '''228'''~~<ol style="list-style~~|-~~type: lower-alpha;"><li>First open~~ | '''~~Help~~20'''~~->~~| '''~~About Plugins...~~GND'''~~.[[File~~| style="text-align:~~zero2w~~left;"|| style="text-align: left;"||-~~img236.png]]</li><li>Then remove the check mark of~~ | '''~~ClangCodeModel~~22'''<| '''TWI0_SDA/p>UART2_RX'''~~[[File:zero2w-img237.png]]</li>~~| '''PI6'''~~<li>~~| '''~~After setting up, you need to restart QT Creator~~262'''~~</li>~~|-| '''<~~li><p~~span style="color:#FF0000">~~Then make sure the GCC compiler used by QT Creator. If the > default is Clang, please change it to GCC.~~24<pspan>'''~~Debian12 please skip this step.~~| '''SPI1_CS0</pspan>'''| '''<pspan style="color:#FF0000">~~[[File:zero2w-img238.png]]~~PH5</pspan>'''| '''<~~p>[[File~~span style="color:~~zero2w-img239.png]]</p~~#FF0000">229</~~li></ol~~span>'''~~</li>~~|-| '''<~~li><p~~span style="color:#FF0000">~~Then you can open a sample code~~26</pspan>'''| '''<~~p>[[File~~span style="color:~~zero2w-img240.png]]</p~~#FF0000">SPI1_CS1</lispan>'''| '''<lispan style="color:#FF0000">~~After clicking on the sample code, the corresponding instruction document will automatically open. You can read the instructions carefully.~~PH9</pspan>'''| '''<~~p>[[File~~span style="color:~~zero2w-img241.png]]</p~~#FF0000">233</lispan>'''|-~~<li>Then click~~ | '''~~Configure Project~~28'''~~[[File:zero2w~~| '''TWI2-~~img242.png]]<~~SCL/~~p></li>~~UART3_TX'''| '''PI9'''~~<li>Then click the green triangle in the lower left corner to compile and run the sample code~~| '''265'''~~[[File:zero2w~~|-~~img243.png]]</li><li>After waiting for a period of time, the interface shown in the figure below will pop up, which means that QT can compile and run normally.~~| '''30'''~~[[File:zero2w-img244.png]]</li>~~| '''GND'''~~<li>References[https~~| style="text-align:~~//wiki.qt.io/Install_Qt_5_on_Ubuntu~~ left;"|| style="text-align: left;"||-| '''~~https://wiki.qt.io/Install_Qt_5_on_Ubuntu~~32'''~~][https://download.qt.io/archive/qtcreator~~ | '''PWM1'''| '''~~https://download.qt.io/archive/qtcreator~~PI11'''~~][https://download.qt.io/archive/qt~~ | '''~~https://download.qt.io/archive/qt~~267'''~~]</li></ol>~~ ~~== ROS installation method ==~~| '''34'''| '''GND'''~~=== 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~~36''' ~~[[File~~| style="text-align:~~zero2w-img245.png]]~~left;"|~~[[File:zero2w-img246.png]]~~ ~~[http://docs.ros.org/~~ | '''~~http://docs.ros.org~~PC12'''] | '''~~https://wiki.ros.org/Distributions~~76'''|-| '''38'''~~<ol start="2"~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">|~~<li>The link to the official installation documentation of ROS 1~~ | '''~~Noetic Ninjemys~~PI4''' ~~is as follows:[http://wiki.ros.org/noetic/Installation/Ubuntu~~ | '''260'''|-| '''~~http://wiki.ros.org/noetic/Installation/Ubuntu~~40'''~~]</li><li>In the official installation documentation of ROS~~ | style="text-align: left;"|| '''~~Noetic Ninjemys~~PI3'''~~, Ubuntu recommends using Ubuntu20.04, so please ensure that the system used by the development board is~~ | '''~~Ubuntu20.04 desktop system~~259'''~~.~~|}<~~p>[http:~~/~~/wiki.ros.org/noetic/Installation '''http://wiki.ros.org/noetic/Installation'''][[File:zero2w-img247.png]]</li><li>Then use the script below to install ros1orangepi@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>

<ol start="2" 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:~$ '''sudo orangepi-config'''|}</li><li>Then select '''System'''[[File:zero2w-img80.png]]</li><li>Then select '''Hardware'''~~Note that when running~~ [[File:zero2w-img81.png]]</li><li>Then use the ~~following command, you need~~ keyboard's arrow keys to ~~ensure that~~ locate the position shown in the ~~development board can access github normally~~figure below, ~~otherwise an error will be reported due to network problems.~~and then use the '''space'''to select the dtbo configuration of the SPI you want to open.</li>

{| class="wikitable" style="width:800px;text-align: center;"|-| '''~~The install_ros.sh script will try to modify /etc/hosts~~ dtbo configuration'''| '''illustrate'''|-| '''spi1-cs0-cs1-spidev'''| '''Open cs0 and ~~automatically run~~ cs1 of spi1 at the ~~following commands. However, this method cannot guarantee that github can be accessed normally every~~ same time~~. If install_ros.sh prompts the following error after installing ros1, please find other ways to allow the linux system~~ '''|-| '''spi1-cs0-spidev'''| '''Only open cs0 of spi1'''|-| '''spi1-cs1-spidev'''| '''Only open cs1 of ~~the development board~~ spi1'''|}</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then select '''<Save>''' to ~~access github normally, and then manually run the following Order~~save[[File:zero2w-img83.png]]</li><li>Then select ''' <Back>'''~~https~~[[File:zero2w-img84.png]]</~~raw~~li><li>Then select '''<Reboot>''' to restart the system to make the configuration take effect.~~githubusercontent~~[[File:zero2w-img85.~~com~~png]]</~~ros~~p></~~rosdistro~~li></~~master~~ol></~~rosdep~~li></~~osx~~ol><ol start="3" style="list-style-~~homebrew~~type: decimal;"><li>Then check whether there is a '''spidev1.~~yaml~~x'''device node in the Linux system. If it exists, it means that the SPI1 configuration has taken effect.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''ls /dev/spidev1*'''~~Hit https:~~/dev/~~raw~~spidev1.~~githubusercontent~~0 /dev/spidev1.~~com~~1</~~ros~~p>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that only when you open spi1-cs0-cs1-spidev, you will see the device nodes of the two spi.'''</~~rosdistro~~p></~~master~~big>|}</~~rosdep/base~~li><li>Then you can use the '''spidev_test.py''' program in examples to test the SPI loopback function. The '''spidev_test.~~yaml~~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'''~~ERROR~~: ~~error loading sources list~~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# '''cd examples'''

root@orangepi:~/wiringOP-Python/examples# '''~~The read operation timed out~~python3 spidev_test.py \'''

~~orangepi@orangepi:~$~~ '''~~source /opt/ros/noetic/setup.bash~~--channel 1 --port 0'''

~~orangepi@orangepi~~spi mode:~~~$ '''sudo rosdep init'''~~0x0

~~Wrote /etc/ros/rosdep/sources.list.d/20-default.list~~max speed: 500000 Hz (500 KHz)

~~Recommended: please run~~Opening device /dev/spidev1.1

~~rosdep update~~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 |......@.......…|

~~orangepi~~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# '''~~rosdep update~~cd examples'''

~~reading in sources list data from~~ root@orangepi:~/~~etc~~wiringOP-Python/~~ros/rosdep/sources.list~~examples# '''python3 spidev_test.dpy \'''

~~Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx~~'''-~~homebrew.yaml~~-channel 1 --port 0'''

~~Hit https~~spi mode:~~//raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml~~0x0

~~Hit https~~max speed:~~//raw.githubusercontent.com/ros/rosdistro/master/rosdep/python.yaml~~500000 Hz (500 KHz)

~~Hit https:~~Opening device /dev/~~raw~~spidev1.~~githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml~~1

~~Hit https~~TX | FF FF FF FF FF FF '''40 00 00 00 00 95</~~/raw~~span>''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@.....~~githubusercontent~~.~~com/ros/rosdistro/master/releases/fuerte~~.~~yaml~~…|

~~Query rosdistro index https~~RX | FF FF FF FF FF FF '''40 00 00 00 00 95</~~/raw~~span>''' FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D |......@......~~githubusercontent~~.~~com~~…||}</~~ros~~li></~~rosdistro/master~~ol></~~index-v4.yaml~~span>

~~Skip end-of-life distro "ardent"~~=== 40pin I2C test ===

~~Skip end-of-life distro "bouncy"~~# As can be seen from the table below, the i2c available for the 40pin interface are i2c0, i2c1 and i2c2

~~Skip end-of-life distro &quot~~<div style="display: flex;~~crystal&quot~~">::{| class="wikitable" style="width:390px; ~~Skip end~~margin-ofright: 20px;text-~~life distro "dashing&quot~~align: center;"|-~~Skip end-of-life distro "eloquent"~~| '''GPIO NO.'''| '''GPIO'''~~Add distro "foxy"~~| '''Function'''| '''Pin'''~~Add distro "galactic"~~|-~~Skip end~~| style="text-~~of-life distro "groovy&quot~~align: left;"| ~~Add distro "humble"~~ ~~Skip end~~| style="text-~~of-life distro "hydro&quot~~align: left;"|| '''3.3V'''~~Skip end-of-life distro "indigo"~~| '''1''' ~~Skip end-of~~|-~~life distro "jade"~~| '''264'''~~Skip end-of-life distro "kinetic"~~ ~~Skip end-of-life distro "lunar"~~ ~~Add distro "melodic"~~ ~~Add distro "noetic"~~ ~~Add distro "rolling"~~ ~~updated cache in /home/orangepi/.ros/rosdep/sources.cache~~ ~~<ol start="6"~~ | '''PI8<~~li><p~~/span>~~Then open a command line terminal window on the~~ '''~~desktop~~| '''~~, and then use the~~ TWI1-SDA'''~~test_ros.sh~~| ''' ~~script to start a small turtle routine to test whether ROS can be used normally.~~3</pspan>~~orangepi@orangepi:~$~~ '''~~test_ros.sh~~|-| '''<~~/p>~~span style="color:#FF0000">263</lispan>'''| '''<lispan style="color:#FF0000">v<p/span>~~After running the~~ '''~~test_ros.sh~~| ''' ~~script, a small turtle as shown in the picture below will pop up.~~</pspan style="color:#FF0000">~~[[File:zero2w~~TWI1-~~img248.png]]~~SCL</pspan>'''| '''<~~/li~~span style="color:#FF0000">~~<li>Then please keep the terminal window you just opened at the top~~5</~~p></li></ol~~span>''' ~~<div class="figure">~~ ~~[[File:zero2w~~|-~~img249.png]]~~| '''269'''<| '''PI13'''| '''PWM3/~~div>~~UART4_TX'''~~<ol start=~~| '''7'''|-| style="9text-align: left;" || style="~~list-style~~text-~~type~~align: ~~decimal~~left;">|~~<li>At this time, press the direction keys on the keyboard to control the little turtle to move up, down, left, and right.~~| '''GND'''| '''9'''~~[[File:zero2w~~|-~~img250.png]]</li></ol>~~| '''226'''| '''PH2'''~~=== How to install ROS 2 Galactic on Ubuntu20.04 ===~~| '''227'''| '''PH3'''~~<ol style="list-style-type: decimal;">~~| '''UART5_RX'''~~<li>The currently active version of ROS 2 is as follows, the recommended version is~~ | '''~~Galactic Geochelone~~13'''~~[[File:zero2w~~|-~~img251.png]]~~| '''</pspan style="color:#FF0000">~~[[File:zero2w-img252.png]]~~261<pspan>~~[http://docs.ros.org/~~ '''~~http://docs.ros.org~~| ''']</pspan style="color:#FF0000">PI5<p/span>'''~~http://docs.ros.org/en/galactic/Releases.html~~| '''</pspan style="color:#FF0000">TWI0_SCL</lispan>~~<li>The link to the official installation documentation of ROS 2~~ /UART2_TX'''~~Galactic Geochelone~~| ''' ~~is as follows~~15<pspan>'''~~docs.ros.org/en/galactic/Installation.html''''''http~~|-| style="text-align:~~//docs.ros.org/en/galactic/Installation/Ubuntu~~left;"|| style="text-~~Install-Debians~~align: left;"|| '''3.~~html~~3V'''| '~~</li>~~''17'''|-~~<li>In the official installation documentation of ROS 2~~ | '''~~Galactic Geochelone~~231'''~~, Ubuntu Linux recommends using Ubuntu20.04, so please ensure that the system used by the development board is the~~ | '''~~Ubuntu20.04 desktop system~~PH7'''~~. There are several ways to install ROS 2. The following demonstrates how to install ROS 2~~ | '''~~Galactic Geochelone~~SPI1_MOSI''' ~~through~~ | '''~~Debian packages~~19'''~~.</li><li>Use the~~ |-| '''~~install_ros.sh~~232''' ~~script to install ros2orangepi@orangepi:~$~~ | '''~~install_ros.sh ros2~~PH8'''~~</li><li>The~~ | '''SPI1_MISO'''~~install_ros.sh~~| ''' ~~script will automatically run the~~ 21'''~~ros2~~ |-h| '''230''' ~~command after installing ros2. If you can see the following print, it means that the ros2 installation is complete.usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...~~| '''PH6'''~~ros2 is an extensible command~~| '''SPI1_CLK'''| '''23'''|-~~line tool for ROS 2.optional arguments~~| style="text-align:~~~~left;"|~~~~| style="text-~~h, --help show this help message and exit~~align: left;"|~~Commands:~~| '''GND'''| '''25'''~~action Various action related sub~~|-~~commands~~| '''<pspan style="color:#FF0000">~~bag Various rosbag related sub-commands~~266</pspan>'''| '''<pspan style="color:#FF0000">~~component Various component related sub-commands~~PI10</pspan>'''<p| '''~~daemon Various daemon related sub~~TWI2-~~commands~~SDA</pspan>/UART3_RX'''| '''<pspan style="color:#FF0000">~~doctor Check ROS setup and other potential issues~~27</pspan>'''~~interface Show information about ROS interfaces~~|-~~launch Run a launch file~~| '''256'''~~lifecycle Various lifecycle related sub-commands~~| '''PI0'''~~multicast Various multicast related sub~~| style="text-~~commands~~align: left;"|~~node Various node related sub-commands~~| '''29'''~~param Various param related sub~~|-~~commandspkg Various package related sub-commands~~| '''271'''~~run Run a package specific executable~~| '''PI15'''~~security Various security related sub~~| style="text-~~commands~~align: left;"|~~service Various service related sub-commands~~| '''31'''~~topic Various topic related sub~~|-~~commandswtf Use `wtf` as alias to `doctor`~~| '''268'''~~Call `ros2 <command> -h` for more detailed usage.</li>~~| '''PI12'''~~<li>Then you can use the~~ | '''~~test_ros.sh~~PWM2''' ~~script to test whether ROS 2 is installed successfully. If you can see the following print, it means ROS 2 can run normally.orangepi@orangepi:~$~~ | '''~~test_ros.sh~~33'''~~[INFO] [1671174101.200091527] [talker]: Publishing:~~ |-| '''258''~~Hello World: 1~~'~~[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: 1][INFO] [1671174102.199572327] [talker]: Publishing:~~ | '''PI2''~~Hello World: 2~~'~~[INFO] [1671174102.204196299] [listener]~~| style="text-align: ~~I heard: [Hello World: 2]~~left;"|~~[INFO] [1671174103.199580322] [talker]: Publishing:~~ | '''35''~~Hello World: 3~~'~~[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]</li>~~|-~~<li>Run the following command to open rviz2orangepi@orangepi:~$~~ | '''272'''~~source /opt/ros/galactic/setup.bash'''orangepi@orangepi:~$~~ | '''~~ros2 run rviz2 rviz2~~PI16'''~~[[File~~| style="text-align:~~zero2w~~left;"|| '''37'''|-~~img253.png]]</li><li>For how to use ROS, please refer to the documentation of ROS 2.~~| style="text-align: left;"|~~[http~~| style="text-align:~~//docs.ros.org/en/galactic/Tutorials.html~~ left;"|| '''~~http://docs.ros.org/en/galactic/Tutorials.html~~GND'''~~]</li></ol>~~| '''39'''~~=== How to install ROS 2 Humble on Ubuntu22.04 ===~~ ~~<ol style="list-style-type: decimal;"><li>Use the install_ros.sh script to~~ | '''Pin'''| '''Function'''| '''~~install_ros.sh~~GPIO'''~~orangepi@orangepi:~$~~ | '''~~install_ros~~GPIO NO.~~sh ros2~~'''~~</li><li>The~~ |-| '''~~install_ros.sh~~2''' ~~script will automatically run the~~ | '''~~ros2 -h~~5V''' ~~command after installing ros2. If you can see the following print, it means that the ros2 installation is complete.usage~~| style="text-align: ~~ros2 [~~left;"|| style="text-~~h] Call `ros2 <command&gt~~align: left; "||-~~h` for more detailed usage. ...ros2 is an extensible command-line tool for ROS 2.~~| '''4'''~~optional arguments~~| '''5V'''| style="text-align:~~~~left;"|~~~~| style="text-h, align: left;"||-| '''6'''| '''GND'''| style="text-~~help show this help message and exitCommands~~align:~~~~left;"|~~action Various action related sub~~| style="text-~~commands~~align: left;"|~~bag Various rosbag related sub~~|-~~commandscomponent Various component related sub-commands~~| '''8'''~~daemon Various daemon related sub-commands~~| '''UART0_TX'''~~doctor Check ROS setup and other potential issues~~| '''PH0'''~~interface Show information about ROS interfaces~~| '''224'''~~launch Run a launch file~~|-~~lifecycle Various lifecycle related sub-commands~~| '''10'''~~multicast Various multicast related sub-commands~~| '''UART0_RX'''~~node Various node related sub-commands~~| '''PH1'''| '''225'''~~param Various param related sub~~|-~~commandspkg Various package related sub~~| '''12'''| style="text-~~commands~~align: left;"|~~run Run a package specific executable~~| '''PI1'''~~security Various security related sub-commands~~| '''257'''~~service Various service related sub~~|-~~commandstopic Various topic related sub-commands~~| '''14'''~~wtf Use `wtf` as alias to `doctor`~~| '''GND'''~~Call `ros2 <command&gt~~| style="text-align: left; ~~-h` for more detailed usage.</li>~~"|| style="text-align: left;"||-~~<li>Then you can use the~~ | '''~~test_ros.sh~~16''' ~~script to test whether ROS 2 is successfully installed. If you can see the following print, it means ROS 2 can run normally.orangepi@orangepi:~$~~ | '''~~test_ros.sh~~PWM4/UART4_RX'''~~[INFO] [1671174101.200091527] [talker]: Publishing:~~ | '''PI14''~~Hello World: 1~~'~~[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: 1][INFO] [1671174102.199572327] [talker]: Publishing:~~ | '''270''~~Hello World: 2~~'~~[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]~~|-~~[INFO] [1671174103.199580322] [talker]: Publishing:~~ | '''18''~~Hello World: 3~~'~~[INFO] [1671174103.204019965] [listener]~~| style="text-align: ~~I heard: [Hello World: 3]</li>~~left;"|~~<li>Run the following command to open rviz2~~| '''PH4'''~~orangepi@orangepi:~$~~ | '''~~source /opt/ros/humble/setup.bash~~228'''~~orangepi@orangepi:~$~~ |-| '''~~ros2 run rviz2 rviz2~~20'''| '''GND'''~~[[File~~| style="text-align:~~zero2w~~left;"|| style="text-align: left;"||-~~img254.png]]</li>~~| '''<~~li><p~~span style="color:#FF0000">~~Reference documentation~~22<pspan>'''~~http://docs.ros.org/en/humble/index.html~~| '''</pspan style="color:#FF0000">TWI0_SDA<p/span>~~[http://docs.ros.org/en/galactic~~/~~Tutorials.html~~ UART2_RX'''~~http://docs.ros.org/en/humble/Installation/Ubuntu-Install-Debians.html~~| ''']</pspan style="color:#FF0000">PI6</~~li></ol~~span>''' | '''262'''~~== How to install kernel header files ==~~|-| '''~~Debian11 system with Linux6.1 kernel will report GCC error when compiling kernel module. So if you want to compile the kernel module, please use Debian12 or Ubuntu22.04.~~24''' ~~<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/~~SPI1_CS0'''| '''PH5'''~~orangepi@orangepi:~$~~ | '''ls /opt/linux-headers*229'''~~/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:~$~~ | '''26'''| '''~~sudo dpkg -i /opt/linux-headers*.deb~~SPI1_CS1'''~~</li><li>After installation, you can see the folder where the kernel header file is located under~~ | '''~~/usr/src~~PH9'''~~.orangepi@orangepi:~$~~ | '''~~ls /usr/src~~233'''~~linux~~|-~~headers-x.x.x~~| '''</pspan style="color:#FF0000">28</lispan>'''| '''<lispan style="color:#FF0000">TWI2-SCL<p/span>~~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~~ /UART3_TX'''~~/usr/src/hello~~| '''~~. After entering this directory, then use the make command to compile.~~</pspan style="color:#FF0000">PI9<p/span>~~orangepi@orangepi:~$~~ '''~~cd /usr/src/hello/~~| '''</pspan style="color:#FF0000">265<p/span>~~orangepi@orangepi:/usr/src/hello$~~ '''~~sudo make~~|-| '''30'''| '''GND'''~~make~~ | style="text-~~C /lib/modules/5.4.125/build M~~align: left;"|| style=~~/usr/src/hello modules~~"text-align: left;"|~~make[1]: Entering directory '/usr/src/linux~~|-~~headers-5.4.125~~| '''32'''| '''PWM1'''~~CC [M] /usr/src/hello/hello.o~~| '''PI11'''| '''267'''~~Building modules, stage 2.~~|-~~MODPOST 1 modules~~| '''34'''~~CC [M] /usr/src/hello/hello.mod.o~~| '''GND'''~~LD [M] /usr/src/hello/hello.ko~~| style="text-align: left;"|~~make[1]~~| style="text-align: ~~Leaving directory '/usr/src/linux~~left;"||-~~headers-5.4.125'</li><li>After compilation, the~~ | '''~~hello.ko~~36''' ~~kernel module will be generatedorangepi@orangepi:/usr/src/hello$~~ | style="text-align: left;"|| '''~~ls *.ko~~PC12'''~~hello.ko</li><li>Use the~~ | '''76'''~~insmod''' command to insert the~~ |-| '''~~hello.ko~~38''' ~~kernel module into the kernelorangepi@orangepi~~| style="text-align:~~/usr/src/hello$~~ left;"|| '''~~sudo insmod hello.ko~~PI4'''~~</li><li>Then use the~~ | '''~~demsg~~260''' ~~command to view the output of the~~ |-| '''~~hello.ko~~40''' ~~kernel module. If you can see the following output, it means that the~~ | style="text-align: left;"|| '''~~hello.ko~~PI3''' ~~kernel module is loaded correctly.orangepi@orangepi:/usr/src/hello$~~ | '''259'''~~dmesg~~ | ~~grep "Hello"'''~~}</pdiv> <~~p>[ 2871.893988] '''Hello Orange Pi~~ ol start="2" style="list-style- ~~init'''</li~~type: decimal;"><li>~~Use the '''rmmod''' command~~ i2c is turned off by default in Linux systems and needs to be turned on manually to ~~uninstall the '''hello~~use it.~~ko''' kernel moduleorangepi@orangepi~~The opening steps are as follows:~~/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>~~ ~~== Testing of some programming languages supported by Linux system ==~~ ~~=== Debian Bullseye system ===~~ ~~<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 followsorangepi@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 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>Debian Bullseye has Python3 installed by default~~

<li>~~The specific version of Python is as followsorangepi@orangepi:~$~~ First run '''~~python3~~orangepi-config'''~~'''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.>>>'''Use the Ctrl+D shortcut key~~ Ordinary users remember to ~~exit python~~add '~~s interactive mode.~~''sudo'~~</li><li>Write the~~ ''~~'hello_world~~permissions.~~py''' program in Python language~~~~orangepi@orangepi~~{| class="wikitable" style="width:~~~$ '''vim hello_world.py'''~~800px;" ~~print('Hello World!')</li>~~|-~~<li>The result of running '''hello_world.py''' is as follows~~| orangepi@orangepi:~$ '''~~python3 hello_world.py~~sudo orangepi-config'''~~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-17orangepi@orangepi:~$~~ Then select '''~~sudo apt install -y openjdk-17-jdk~~System'''</p~~></li~~>~~<li>~~~~After installation, you can check the Java version.orangepi@orangepi~~[[File:~~~$ '''java~~ zero2w-~~-version'''~~img80.png]]</li><li>~~Write the Java version of~~ Then select '''~~hello_world.java~~Hardware'''~~orangepi@orangepi~~[[File:~~~$ '''vim hello_world~~zero2w-img81.~~java'''public class hello_world{public static void main(String[~~png]] ~~args){System.out.println("Hello World!");}}~~</li><li>Then ~~compile~~ use the keyboard's arrow keys to locate the position shown in the picture below, and ~~run~~ then use the '''~~hello_world.java~~space'''~~orangepi@orangepi:~$ '''javac hello_world~~to select the corresponding i2c configuration in the picture below.~~java'''~~~~orangepi@orangepi:~$ '''java hello_world'''Hello World!</li></ol>~~</li~~></ol~~>

~~<span id~~{| class="~~debian~~wikitable" style="width:800px;text-align: center;"|-| '''Multiplexing function in 40pin'''| '''Corresponding dtbo configuration'''|-| '''40pin - i2c0'''| '''pi-i2c0'''|-| '''40pin - i2c1'''| '''pi-i2c1'''|-| '''40pin -~~bookworm~~i2c2'''| '''pi-~~system">~~i2c2'''~~=== Debian Bookworm system ===~~|}

~~<ol style="list~~[[File:zero2w-~~style-type: decimal;">~~img173.png]]~~<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.~~</pol><ol start="5" style="list-style-type: lower-alpha;"><li>~~The version of a.gcc is as follows~~Then select </pspan class="mark"><Save><p/span>~~orangepi@orangepi:~$ '''gcc --version'''~~to save~~gcc (Debian 12.2.0~~[[File:zero2w-~~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~~img83.png]]</li><li>~~Write the '''hello_world.c''' program in C language~~Then select <~~/p>orangepi@orangepi:~$ '''vim hello_world.c'''</p~~span class="mark">~~#include~~ <~~stdio.h~~Back></pspan>~~int main(void)~~~~{printf("Hello World!\n");return 0;}~~[[File:zero2w-img84.png]]</li><li>Then ~~compile and run '''hello_world.c'''~~select </pspan class="mark"><Reboot><p/span>~~orangepi@orangepi:~$ '''gcc -o hello_world hello_world~~to restart the system to make the configuration take effect.~~c'''~~~~orangepi@orangepi~~[[File:~~~$ '''~~zero2w-img85.~~/hello_world'''Hello World!~~png]]</li></ol></li><li/ol><~~p>Debian Bookworm has Python3 installed by default</p~~!-- --><ol start="3" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The specific version of Python~~ After starting the Linux system, first confirm that there is ~~as follows~~an open i2c device node under </pspan class="mark">~~orangepi@orangepi:~$ '''python3'''<~~/p>~~Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] on linux~~dev</pspan>~~Type "help", "copyright", "credits" or "license" for more information.~~~~&gt~~{| class="wikitable" style="width:800px;~~>>~~" ~~'''Use the Ctrl+D shortcut key to exit python's interactive mode.'''</li>~~|-~~<li>Write the '''hello_world.py''' program in Python language~~| orangepi@orangepi:~$ '''~~vim hello_world.py'''<~~ls /p>~~print('Hello World!')<~~dev/~~p></li><li>The result of running~~ i2c-*'''~~hello_world.py''' is as follows~~~~orangepi@orangepi:~$~~ '''~~python3 hello_world.py~~/dev/i2c-*'''~~Hello World!</li></ol>~~|}~~</li><li>Debian Bookworm does not install Java compilation tools and operating environment by default.<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">~~<li>You can use the following command to install openjdk. The latest > version in Debian Bookworm is openjdk~~|-~~17~~| <pbig>~~orangepi@orangepi:~$~~ '''~~sudo apt install -y openjdk-17-jdk~~注意，这里说的Linux镜像具体指的是从Orange Pi资料下载页面下载的Debian或者Ubuntu这样的Linux发行版镜像。'''</~~p></li~~big>~~<li>After installation, you can check the Java version.~~|}~~orangepi@orangepi:~$ '''java -~~{| class="wikitable" style="background-~~version'''</li><li>Write the Java version of '''hello_world.java'''orangepi@orangepi~~color:~~~$ '''vim hello_world.java'''public class hello_world{public static void main(String[] args){System.out.println(&quot~~#ffffdc;~~Hello World!&quot~~width:800px;~~);~~" ~~}~~|-~~}</li>~~| <libig>~~Then compile and run~~ '''~~hello_world~~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.~~java~~'''~~orangepi@orangepi:~$~~ '''~~javac hello_world.java'''<~~The method to accurately confirm the device node under /p>~~orangepi@orangepi~~dev corresponding to the i2c bus is:~$ '''~~java hello_world'''Hello World!~~</~~li></ol></li></ol~~big>

~~~~

~~=== Ubuntu Focal system ===~~

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

~~<li>Ubuntu Focal is installed with the gcc compilation tool chain by default, which can directly compile C language programs in the Linux system of the development board.~~

<li>~~The version of a.gcc is as followsorangepi@orangepi:~$~~ '''~~gcc --version'''gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0Copyright (C) 2019 Free Software Foundation, Inc.This is free software; see~~ First run the ~~source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</li><li>Write~~ following command to check the corresponding relationship of i2c'''~~hello_world.c''' program in C language~~orangepi@~~orangepi~~orangepizero2w:~$ '''~~vim hello_world.c'''<~~ls /sys/devices/p>~~#include <stdio.h><~~platform/p>~~int main(void)<~~soc*/p>~~{<~~*/p>~~printf(~~i2c-* | grep "~~Hello World!\n~~i2c-[0-9]");'''~~return 0;<~~/p>~~}<~~sys/devices/platform/~~p><~~soc/~~li><li>Then compile and run '''hello_world~~5002000.~~c'''<~~i2c/p>~~orangepi@orangepi~~i2c-0:~~~$ '''gcc -o hello_world hello_world.c'''~~~~orangepi@orangepi:~$ '''./hello_world'''<~~/p>~~Hello World!<~~sys/~~p><~~devices/~~li><~~platform/~~ol>~~<soc/~~li><li>Ubuntu Focal has Python3 installed by default<~~5002400.i2c/p>~~<ol style="list-style-type: lower~~i2c-~~alpha;"><li>The specific version of Python3 is as followsorangepi@orangepi:~$ '''python3'''Python~~ 3~~.8.10 (default, Nov 14 2022, 12:59~~:~~47)~~~~[GCC 9.4.0] on linux<~~/p>~~Type "help", "copyright", "credits" or "license" for more information.<~~sys/p>~~>>><~~devices/p>~~'''Use the Ctrl+D shortcut key to exit python's interactive mode.'''<~~platform/~~p><~~soc/~~li><li>Write the '''hello_world~~5002800.~~py''' program in Python language<~~i2c/p>~~orangepi@orangepi~~i2c-4:~~~$ '''vim hello_world.py'''print('Hello World!')</li><li>The result of running '''hello_world.py''' is as follows~~~~orangepi@orangepi:~$ '''python3 hello_world.py'''<~~/p>~~Hello World!<~~sys/~~p><~~devices/~~li><~~platform/~~ol>~~<soc/~~li><li>Ubuntu Focal does not have Java compilation tools and running environment installed by default~~5002c00.<i2c/p>~~<ol style="list-style~~i2c-~~type~~5: ~~lower-alpha;"><li>You can use the following command to install openjdk-17~~~~orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''<~~/~~p><~~sys/~~li><li>After installation, you can check the Java version.<~~devices/p>~~orangepi@orangepi:~$ '''java --version'''<~~platform/p>~~openjdk 17.0.2 2022-01-18<~~soc/p>~~OpenJDK Runtime Environment (build 17.0.2+8-Ubuntu-120~~6000000.~~04)<~~hdmi/p>~~OpenJDK 64~~i2c-~~Bit Server VM (build 17.0.~~2~~+8-Ubuntu-120.04, mixed mode, sharing)</li><li>Write the Java version of '''hello_world.java'''orangepi@orangepi~~:~~~$ '''vim hello_world.java'''~~~~public class hello_world<~~/p>~~{<~~sys/p>~~public static void main(String[] args)<~~devices/p>~~{<~~platform/p>~~System.out.println("Hello World!");<~~soc/p>~~}}</li><li>Then compile and run '''hello_world~~7081400.~~java'''<~~i2c/p>~~orangepi@orangepi~~i2c-1:~~~$ '''javac hello_world.java'''orangepi@orangepi:~$ '''java hello_world'''Hello World!~~</li~~></ol></li></ol~~>

~~~~

~~=== Ubuntu Jammy system ===~~

~~<ol style="list-style-type: decimal;">~~<li>~~Ubuntu Jammy is installed with~~ '''In the ~~gcc compilation tool chain by default, which can directly compile C language programs in the Linux system of the development board.~~above output'''<ol style="list-style-type: ~~lower-alpha~~none;"><li>~~The version~~ a) 5002000 is the register base address of ~~a.gcc~~ the i2c0 bus, and i2c-0 shown behind it is ~~as follows~~its corresponding i2c device node~~orangepi@orangepi:~$ '''gcc --version'''~~</pli><pli>~~gcc (Ubuntu 11.3.0-1ubuntu1~22.04.1) '''11.3.0'''~~~~Copyright (C~~b) ~~2021 Free Software Foundation, Inc.This~~ 5002400 is ~~free software; see~~ the ~~source for copying conditions. There~~ register base address of the i2c1 bus, and i2c-3 shown behind it is ~~NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.~~its corresponding i2c device node</li><li>~~Write~~ c) 5002800 is the register base address of the ~~'''hello_world.c''' program in C language~~i2c2 bus, and i2c-4 shown behind it is its corresponding i2c device node<p/li>~~orangepi@orangepi:~$ '''vim hello_world.c'''~~</pol><p/li>~~#include <stdio.h>~~</pol>~~int main(void)~~|}~~{~~</pli>~~printf("Hello World!\n");~~</pol><~~p>return 0~~ol start="4" style="list-style-type: decimal;~~}</li~~"><li>Then ~~compile and run '''hello_world.c'''~~start testing i2c, first install i2c-tools{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~gcc~~ sudo apt-~~o hello_world hello_world.c~~get update'''orangepi@orangepi:~$ '''~~./hello_world~~sudo''' '''apt-get install -y i2c-tools'''~~Hello World!</li></ol>~~|}</li><li>~~Ubuntu Jammy has Python3 installed by default~~Then connect an i2c device to the i2c pin of the 40pin connector. Here we take the DS1307 RTC module as an example.<~~ol style="list-style-type~~p>[[File: ~~lower~~zero2w-~~alpha;"><li>~~img178.png]]~~The specific version of Python3 is as follows~~</pli><li>~~orangepi@orangepi:~$~~ Then use the '''~~python3~~i2cdetect -y x'''~~Python 3~~command.~~10.6 (main~~If the address of the connected i2c device can be detected, ~~May 29 2023, 11:10:38) [GCC 11.3~~it means that the i2c device is connected correctly.~~0] on linux~~~~Type &quot~~{| class="wikitable" style="background-color:#ffffdc;~~help&quot~~width:800px;~~, "copyright", "credits" or "license" for more information.~~" |-~~>>>~~| <pbig>~~'''Use the Ctrl+D shortcut key to exit python's interactive mode.~~'''~~</li><li>Write the~~ '''~~hello_world~~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.py''' ~~program in Python language~~~~orangepi@orangepi:~$ '''vim hello_world.py~~'''</pbig>~~print('Hello World!')</li>~~|}~~<li>The result of running '''hello_world.py''' is as followsorangepi@orangepi~~[[File:~~~$ '''python3 hello_world~~zero2w-img179.~~py'''~~png]]~~Hello World!~~</li></ol>~~</li><li>Ubuntu Jammy does not install Java compilation tools and operating environment by default.</p~~><ol start="7" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~You~~ Then you can ~~use~~ run the ~~following command to install openjdk-18orangepi@orangepi:~$~~ '''~~sudo apt install -y openjdk-18-jdk~~ds1307.py'''~~</li><li>After installation, you can check the Java version.orangepi@orangepi:~$~~ test program in '''~~java --version~~examples'''to read the RTC time~~openjdk 18.0.2~~{| class="wikitable" style="background-~~ea 2022~~color:#ffffdc;width:800px;" |-~~07-19~~| <pbig>~~OpenJDK Runtime Environment (build 18.0.2-ea+9-Ubuntu-222.04)~~~~OpenJDK 64~~'''Note that the x in i2c-~~Bit Server VM (build 18~~x in the following command needs to be replaced with the serial number of the device node corresponding to the i2c bus.~~0.2-ea+9-Ubuntu-222.04, mixed mode, sharing)~~'''</libig>~~<li>~~|}{| class="wikitable" style="width:800px;" |-| ~~Write the Java version of~~ root@orangepi:~/wiringOP-Python# '''~~hello_world.java~~cd examples'''~~orangepi~~root@orangepi:~$ /wiringOP-Python/examples# '''~~vim hello_world~~python3 ds1307.~~java~~py --device \'''~~public class hello_world{public static void main(String[] args){System.out.println(~~'''"~~Hello World!~~/dev/i2c-x");'''}Thu 2022-06-16 04:35:46}Thu 2022-06-16 04:35:47</p~~></li~~>~~<li>~~~~Then compile and run '''hello_world.java'''~~Thu 2022-06-16 04:35:48~~orangepi@orangepi:~$ '''javac hello_world.java'''~~^C~~orangepi@orangepi:~$ '''java hello_world'''~~exit~~Hello World!</li></ol>~~|}

</li></ol>

== Method of uploading files to the development board Linux system ==~~ ~~=== Method to upload files to the development board Linux system in Ubuntu PC ===~~ ~~~~==== How to upload files using scp command ====~~ ~~<ol style="list-style-type: decimal;"><li>Use the scp command to upload files to the Linux system of the development board in Ubuntu PC. The specific command is as follows<ol style="list-style-type: lower-alpha;"><li>'''file_path: '''Needs to be replaced with the path of the file to > be uploaded</li><li>'''orangepi: '''This is the user name of the development board's > Linux system. It can also be replaced with something else, > such as root.</li><li>'''192.168.xx.xx:''' This is the IP address of the development > board. Please modify it according to the actual situation.</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.xx.xx:/home/orangepi/'''</li></ol></li><li>If you want to upload a folder, you need to add the -r parametertest@test:~$ '''scp -r dir_path orangepi@192.168.xx.xx:/home/orangepi/'''</li><li>There are more usages of scp, please use the following command to view the man manual</li></ol~~>

=== 40pin UART test~~@test:~$ '''man scp'''~~===

~~==== How to upload files using filezilla ====~~# 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.

<ol div style="~~list-style-type~~display: ~~decimal~~flex;">~~<li>First install filezilla in Ubuntu PCtest@test~~:~~~$ '''sudo apt install~~ :{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-~~y filezilla~~| '''GPIO NO.'''~~</li><li>Then use the following command to open filezilla~~| '''GPIO'''~~test@test:~$~~ | '''~~filezilla~~Function'''~~</li><li>The interface after opening filezilla is as shown below. At this time, the remote site on the right is empty.~~| '''Pin'''|-~~<div class~~| style="~~figure~~text-align: left;">| ~~[[File~~| style="text-align:~~zero2w-img255.png]]~~left;"|| '''3.3V'''~~</div></li>~~| '''1'''|-~~<li>The method of connecting the development board is as shown in the figure below</li></ol>~~| '''264'''| '''PI8'''~~<div class="figure">~~| '''TWI1-SDA'''| '''3'''~~[[File:zero2w~~|-~~img256.png]]~~| '''263'''~~</div><ol start="5" style="list-style-type: decimal;"><li>Then choose to~~ | '''PI7'''~~save the password~~| ''' ~~and click~~ TWI1-SCL'''OK| '''5'''~~[[File:zero2w~~|-~~img257.png]]</li><li>Then select~~ | '''269'''~~Always trust this host~~| ''' ~~and click~~ PI13'''OK| '''<PWM3/~~p></li></ol>~~UART4_TX'''| '''7'''|-~~<div class~~| style="~~figure~~text-align: left;"> ~~[[File:zero2w-img258.png]]~~|~~</div><ol start="7"~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">|~~<li>After the connection is successful, you can see the directory structure of the development board~~| '''GND'''~~s Linux file system on the right side of the filezilla software.</li></ol>~~| '''9'''~~<div class="figure">~~ ~~[[File:zero2w~~|-~~img259.png]]~~| '''226'''~~</div>~~| '''PH2'''~~<ol start="8" style="list~~| '''UART5_TX'''| '''11'''|-~~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.</li></ol>| '''227'''| '''PH3'''~~<div class="figure">~~| '''UART5_RX'''| '''13'''~~[[File:zero2w~~|-~~img260.png]]~~| '''261'''~~</div>~~| '''PI5'''~~<ol start~~| '''TWI0_SCL/UART2_TX'''| '''15'''|-| style="9text-align: left;" || style="~~list-style~~text-~~type~~align: ~~decimal~~left;">|~~<li>After the upload is completed, you can go to the corresponding path in the development board Linux system to view the uploaded file~~| '''3.~~</li>~~3V'''~~<li>The method of uploading a folder is the same as the method of uploading a file, so I won~~| '''17'''~~t go into details here.</li></ol>~~|-~~~~| '''231'''| '''PH7'''~~=== Method to upload files from Windows PC to development board Linux system ===~~| '''SPI1_MOSI'''| '''19'''~~==== How to upload files using filezilla ====~~ ~~# First download the installation file of the Windows version of the filezilla software. The download link is as follows~~| '''232''' ~~[https://filezilla-project.org/download.php?type=client~~ | '''~~https://filezilla-project.org/download.php?type=client~~PH8''']| '''SPI1_MISO'''| '''21'''~~[[File:zero2w~~|-~~img261.png]]~~| '''230'''~~<div class="figure">~~| '''PH6'''| '''SPI1_CLK'''~~[[File:zero2w~~| '''23'''|-~~img262.png]]~~| style="text-align: left;"|~~</div><ol start="2"~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">|~~<li>The downloaded installation package is as shown below, then double-click to install it directly~~| '''GND'''~~~~| '''~~FileZilla_Server_1.5.1_win64-setup.exe~~25'''~~</li></ol>~~|-~~During the installation process, please select~~ | '''~~Decline~~266''' ~~on the following installation interface, and then select~~ | '''~~Next>~~PI10'''| '''TWI2-SDA/UART3_RX'''~~<div class="figure">~~| '''27'''~~[[File:zero2w~~|-~~img263.png]]~~| '''256'''~~</div>~~| '''PI0'''~~<ol start="3"~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">~~<li>The interface after opening filezilla is as shown below. At this time, the remote site on the right is empty.</li></ol>~~|| '''29'''~~<div class="figure">~~ ~~[[File:zero2w~~|-~~img264.png]]~~| '''271'''~~</div>~~| '''PI15'''~~<ol start="4"~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">~~<li>The method of connecting the development board is as shown in the figure below:</li></ol>~~|| '''31'''~~<div class="figure">~~ ~~[[File:zero2w~~|-~~img256.png]]~~| '''268'''~~</div>~~| '''PI12'''~~<ol start="5" style="list-style-type: decimal;"><li>Then choose to~~ | '''~~save the password~~PWM2''' ~~and click~~ | '''OK33'''~~</li></ol>~~|-| '''258'''~~<div class~~| '''PI2'''| style="~~figure">~~text-align: left;"|| '''35'''~~[[File:zero2w~~|-~~img265.png]]~~| '''272'''~~</div>~~| '''PI16'''~~<ol start="6"~~ | style="~~list-style~~text-~~type~~align: ~~decimal~~left;">|~~<li>Then select~~ | '''~~Always trust this host~~37''' ~~and click '''OK'''</li></ol>~~|-~~<div class~~| style="~~figure~~text-align: left;">|~~[[File:zero2w-img266.png]]~~ ~~</div><ol start="7"~~ | style="~~list-style~~text-~~type~~align: ~~decimal~~left;">|~~<li>After the connection is successful, you can see the directory structure of the development board~~| '''GND'''| '''39'''~~s Linux file system on the right side of the filezilla software.</li></ol>~~|}~~<div~~ {| class="~~figure~~wikitable"> ~~[[File~~style="width:~~zero2w~~390px;margin-~~img267.png]]~~ ~~</div><ol start="8" style="list-style~~right: 20px;text-~~type~~align: ~~decimal~~center;"><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>|-| '''Pin'''~~<div class="figure">~~| '''Function'''| '''GPIO'''~~[[File:zero2w-img268~~| '''GPIO NO.~~png]]~~'''|-~~</div>~~| '''2'''| '''5V'''~~<ol start~~| style="9text-align: left;" || style="~~list~~text-~~style-type~~align: ~~decimal~~left;">||-~~<li>After the upload is completed, you can go to the corresponding path in the development board Linux system to view the uploaded file.</li>~~| '''4'''~~<li>The method of uploading a folder is the same as the method of uploading a file, so I won~~| '''5V'''~~t go into details here.</li></ol>~~ ~~~~|~~== Instructions for using the logo on and off the machine ==~~ ~~<ol style~~| style="~~list-style~~text-~~type~~align: ~~decimal~~left;">|~~<li>The power on/off logo will only be displayed on the desktop version of the system by default.</li>~~|-~~<li>Set the~~ | '''6'~~bootlogo~~''| ' ~~variable to~~ ''GND'~~false~~''| style="text-align: left;"|| style="text-align: left;"||-| ' in ''8'~~/boot/orangepiEnv.txt~~''~~' to turn off the switch logo.orangepi@orangepi:~$~~ | '''~~sudo vim /boot/orangepiEnv.txt~~UART0_TX'''~~verbosity=1~~| '''~~bootlogo=false~~PH0'''~~</li><li>Set the~~ | '''~~bootlogo~~224''' ~~variable to~~ |-| '''~~true~~10''' in | '''~~/boot/orangepiEnv.txt~~UART0_RX''' ~~to enable the power on/off logo.orangepi@orangepi:~$~~ | '''PH1'~~sudo vim /boot/orangepiEnv.txt~~''| '''225'''~~verbosity=1~~|-~~~~| '''~~bootlogo=true~~12'''~~</li><li>The location of the boot logo picture in the Linux system is~~| style="text-align: left;"|| '''PI1'''~~~~| '''~~'/usr/share/plymouth/themes/orangepi/watermark.png~~257'''~~</li><li>After replacing the boot logo image, you need to run the following command to take effect~~|-~~orangepi@orangepi:~$~~ | '''~~sudo update-initramfs -u~~14'''~~</li></ol>~~| '''GND'''~~~~|~~== How to turn on the power button in Linux5.4 ==~~|-| '''16'''~~There is no power on~~| '''PWM4/~~off button on the main board of the development board. We can expand it through a 24pin expansion board. The location of the power on/off button on the expansion board is as follows:~~UART4_RX'''| '''PI14'''| '''270'''~~[[File:zero2w~~|-~~img269.png]]~~| '''18'''The power on/off button of the Linux 6.1 image is turned on by default, but the power on/off button of the Linux 5.4 kernel image is turned off by default and needs to be turned on manually for normal use. The steps are as follows: ~~<ol~~ | style="~~list-style~~text-~~type~~align: ~~decimal~~left;">|~~<li>First run~~ | '''~~orangepi-config~~PH4'''~~. Ordinary users remember to add~~ | '''~~sudo~~228''' ~~permissions.orangepi@orangepi:~$~~ |-| '''~~sudo orangepi-config~~20'''~~</li><li>Then select~~ | '''~~System~~GND'''~~[[File~~| style="text-align:~~zero2w~~left;"|| style="text-align: left;"||-~~img80.png]]</li><li>Then select~~ | '''~~Hardware~~22'''~~[[File:zero2w-img81.png]]<~~| '''TWI0_SDA/~~p></li>~~UART2_RX'''~~<li>Then use the keyboard~~| '''~~s arrow keys to locate the position shown in the picture below, and then use the~~ PI6'''~~space~~| '''262''' ~~to select the dtbo configuration of the SPI you want to open.[[File:zero2w~~|-~~img270.png]]</li><li>Then select~~ | '''~~<Save>~~24''' ~~to save[[File:zero2w-img83.png]]</li>~~| '''SPI1_CS0'''~~<li>Then select~~ | '''~~<Back>~~PH5'''~~[[File:zero2w~~| '''229'''|-~~img84.png]]</li><li>Then select~~ | '''~~<Reboot>~~26''' ~~to restart the system to make the configuration take effect.[[File:zero2w-img85.png]]</li></ol>~~| '''SPI1_CS1'''| '''PH9'''~~<~~SCL/~~span>== How to shut down and restart the development board ==~~UART3_TX'''~~<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~~PI9''' ~~command to shut down the Linux system of the development board before powering off, and then unplug the power supply.orangepi@orangepi:~$~~ | '''265'''|-| '''~~sudo poweroff~~30'''~~~~| '''~~Note that after turning off the development board, you need to unplug and replug the power supply before it can be turned on.~~GND'''~~</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.~~| style="text-align: left;"|~~[[File~~| style="text-align:~~zero2w~~left;"||-~~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.~~32'''~~</li><li>Use the~~ | '''~~reboot~~PWM1''' ~~command to restart the Linux system in the development boardorangepi@orangepi:~$~~ | '''~~sudo~~PI11''' | '''~~reboot~~267'''~~</li></ol>~~ ~~~~ = | '''~~Linux SDK——orangepi-build usage instructions~~34''' =| '''GND'''~~~~|| style=~~= Compilation system requirements ==~~"text-align: left;"||-~~The Linux SDK,~~ | '''~~orangepi-build~~36'''~~, only supports running on X64 computers with~~ | style="text-align: left;"|| '''~~Ubuntu 22.04~~PC12''' 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~~76'''~~, it means that the Ubuntu version currently used does not meet the requirements. Please change the system before performing the following operations.~~|-| '''38'''~~test@test~~| style="text-align:~$ left;"|| '''PI4'~~lsb_release -a~~''| '''260'''|-| '''40'''| style="text-align: left;"|| '''PI3'''| '''259'''|}</div>

~~No LSB modules~~ <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 ~~available~~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 picture below, and then use the '''space''' to select the serial port you want to open.</li>

~~Distributor ID~~{| class="wikitable" style="width: ~~Ubuntu~~800px;text-align: center;"|-| '''Multiplexing function in 40pin'''| '''Corresponding dtbo configuration'''|-| '''40pin - uart2'''| '''pi-uart2'''|-| '''40pin - uart3'''~~Description: Ubuntu 22.04 LTS~~| '''pi-uart3'''|-~~Release:~~ | '''40pin - uart4'''| '''~~22.04~~pi-uart4'''|-~~Codename:~~ | '''40pin - uart5'''| '''~~jammy~~ph-uart5'''|}

~~If the computer is installed with a Windows system and does not have Ubuntu 22~~[[File:zero2w-img175.png]]</ol><ol start="5" style="list-style-type: lower-alpha;"><li>Then select '''<Save>''' to save[[File:zero2w-img83.~~04 installed on it, you can consider using~~png]]</li><li>Then select '''~~VirtualBox~~<Back>''' or [[File:zero2w-img84.png]]</li><li>Then select '''~~VMware~~<Reboot>''' to ~~install an Ubuntu 22~~restart the system to make the configuration take effect.[[File:zero2w-img85.~~04 virtual machine in~~ png]]</li></ol></li></ol><ol start="3" style="list-style-type: decimal;"><li>After entering the ~~Windows~~ Linux system~~. But please note~~, ~~do not compile orangepi~~first confirm whether there is a uart5 device node under '''/dev'''{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-~~build on the WSL virtual machine~~| <big>'''注意, ~~because~~ linux5.4系统为/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-~~build has not been~~ circuit the rx and tx pins of the uart interface to be tested .</li><li>Use the '''gpio''' command in wiringOP to test the ~~WSL virtual machine~~loopback function of the serial port as shown below. If you can see the following print, ~~so there~~ it means the serial port communication is ~~no guarantee~~ normal.{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that ~~orangepi-build can~~ the last x in the gpio serial /dev/ttySx command needs to be ~~used normally in WSL. In addition, please do not compile~~ replaced with the ~~Linux system on~~ serial number of the ~~development board~~corresponding uart device node. ~~Use~~ '''</big>|}{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''gpio serial /dev/ttySx        # linux-~~build~~6. ~~The installation image download address of Ubuntu 22~~1 test command'''orangepi@orangepi:~$ '''gpio serial /dev/ttyASx        # linux-5.~~04 amd64 version is:~~4 test command'''

~~[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~~Out: 0: -> 0Out: 1: -> 1Out: 2: -> 2Out: 3: -> 3^C|}</li><li>Finally, you can run the '''serialTest.~~04 on your computer or virtual machine, please first set~~ py''' program in examples to test the ~~software source~~ loopback function of ~~Ubuntu 22~~the serial port.~~04 to Tsinghua source (or other domestic sources that~~ If you ~~think is fast)~~can see the following print, ~~otherwise~~ it means that the serial port loopback test is ~~easy to make errors due to network reasons when installing the software later~~normal. ~~The steps to replace Tsinghua Source are as follows:~~ ~~<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;"|-| <big><lip>~~For~~ '''Note that the ~~method~~ x in /dev/ttySx or /dev/ttyASx in the command needs to be replaced with the serial number of ~~replacing Tsinghua Source, please refer to~~ the ~~instructions on this page~~corresponding uart device node.'''</lip></olbig>|}{| class="wikitable" style="width:800px;" |-| ~~[https~~root@orangepi:~/wiringOP-Python# '''cd examples'''</~~mirrors~~p>root@orangepi:~/wiringOP-Python/examples# '''python3 serialTest.~~tuna.tsinghua.edu.cn~~py --device "/~~help/ubuntu~~dev/ ttySx" # linux6.1 use'''~~https~~root@orangepi:~/wiringOP-Python/~~mirrors~~examples# '''python3 serialTest.~~tuna.tsinghua.edu.cn~~py --device "/~~help/ubuntu~~dev/ttyASx" # linux5.4 use''']

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

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

~~[[File~~Out: 0: -> 0Out: 1: -> 1Out: 2: -> 2Out: 3:~~zero2w~~-~~img271.png]]~~> 3Out: 4:^Cexit|}</li></ol>

<~~ol start~~span id="~~3" style="list-style~~hardware-~~type: lower~~watchdog-~~alpha;~~test">~~<li>The contents of the '''/etc/apt/sources.list''' file that need to be replaced are:</li~~></olspan>

== Hardware watchdog test~~@test:~$ '''sudo mv /etc/apt/sources.list cat /etc/apt/sources.list.bak'''~~==

~~test@test:~$ '''sudo vim /etc/apt/sources~~The watchdog_test program is pre-installed in the Linux system released by Orange Pi and can be tested directly.~~list'''~~

# The ~~source code image~~ method to run the watchdog_test program is ~~commented by default to improve apt update speed. You can uncomment it yourself if necessary.~~as follows:

~~deb https~~<ol style="list-style-type:lower-alpha;"><li>The second parameter 10 represents the counting time of the watchdog. If the dog is not fed within this time, the system will restart.</~~mirrors~~li><li>We can feed the dog by pressing any key on the keyboard (except ESC).~~tuna~~After feeding the dog, the program will print a line "keep alive" to indicate that the dog feeding is successful.~~tsinghua.edu.cn~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo watchdog_test 10'''open successoptions is 33152,identity is sunxi-wdtput_usr return,if 0,success:0The old reset time is: 16return ENOTTY,if -1,success:0return ENOTTY,if -1,success:0put_user return,if 0,success:0put_usr return,if 0,success:0keep alivekeep alivekeep alive|}</~~ubuntu~~li></ ~~jammy main restricted universe multiverse~~ol>

~~# deb~~</ ~~jammy main restricted universe multiverse~~span>

~~deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse~~== Check the chipid of H618 chip ==

~~# deb-src https://mirrors~~The command to view the H618 chip chipid is as follows.~~tuna~~The chipid of each chip is different, so you can use chipid to distinguish multiple development boards.~~tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse~~

~~deb https~~{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''cat /sys/~~mirrors.tuna.tsinghua.edu.cn~~class/~~ubuntu~~sunxi_info/ ~~jammy-backports main restricted universe multiverse~~sys_info | grep "chipid"'''

~~# deb-src https~~sunxi_chipid :~~//mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse~~338020004c0048080147478824681ed1|}

~~deb https://mirrors.tuna.tsinghua.edu.cn~~</~~ubuntu/ jammy-security main restricted universe multiverse~~span>

~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-security main restricted universe multiverse~~== Python related instructions ==

~~# Pre~~=== How to ~~be enabled~~compile and install Python source code ===

{| class="wikitable" style="background-color:# ~~deb https~~ffffdc;width:~~//mirrors~~800px;" |-| <big>'''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 the latest version of Python.~~tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse~~'''

~~# deb-src https://mirrors.tuna~~'''The following demonstration is to compile and install the latest version of Python 3.~~tsinghua~~9.~~edu~~If you want to compile and install other versions of Python, the method is the same (you need to download the source code corresponding to the Python you want to install).~~cn/ubuntu~~'''</ ~~jammy-proposed main restricted universe multiverse~~big>|}

<ol ~~start="4"~~ style="list-style-type: ~~lower-alpha~~decimal;"><~~li>After the replacement, you need to update the package information and ensure that no errors are reported.</~~li><~~/ol~~p> ~~test@test:~$ '''sudo apt-get update'''~~ ~~<ol start="5" style="list-style-type: lower-alpha;">~~<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~~ First 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~~ dependency packages needed 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]]~~ compile Python</~~div~~p>'''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" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~branch~~sudo apt-get update'''| orangepi@orangepi:~$ '''sudo apt-get install -y build-essential zlib1g-dev \''''''ulibncurses5-dev libgdbm-dev libnss3-dev libssl-dev libsqlite3-~~boot Version~~dev \'''| '''~~linux Kernel version~~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:~$ '''~~current~~wget \'''| '''uhttps://www.python.org/ftp/python/3.9.10/Python-~~boot v2018~~3.9.10.05tgz'''| orangepi@orangepi:~$ '''~~linux5~~tar xvf Python-3.49.10.tgz'''|}</li><li>Then run the configuration command{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''cd Python-3.9.10'''orangepi@orangepi:~$ '''./configure --enable-optimizations'''|}</li><li>Then compile and install Python3.9. The compilation time takes about half an hour.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''make -j4'''orangepi@orangepi:~$ '''~~next~~sudo make altinstall'''|}</li><li>After installation, you can use the following command to check the version number of the Python you just installed.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''upython3.9 -~~boot v2021~~-version''''''Python 3.9.0710'''| }</li><li>Then update pip{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~linux6~~/usr/local/bin/python3.19 -m pip install --upgrade pip'''

|}

</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.'''~~=== How to replace pip source in Python ===

~~After downloading~~{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''The default source used by Linux system pip is the official source of Python. However, accessing the ~~following files~~ official source of Python in China is very slow, and ~~folders will be included:~~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.'''</big>|}

<li>First install '''python3-pip'''

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

|-

|

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

orangepi@orangepi:~$ '''sudo apt-get install -y python3-pip'''

|}

</li>

<li>How to permanently change the pip source under Linux

<li>First create a new '''~~build~~~/.pip''' directory, then add the '''pip.shconf'''configuration file, and set the pip source in it to Tsinghua source.{| class="wikitable" style="width: ~~Compile startup script~~800px;" |-| orangepi@orangepi:~$ '''mkdir -p ~/.pip'''</lip><lip>orangepi@orangepi:~$ '''cat <<EOF > ~/.pip/pip.conf''''''~~external~~[global]'''~~: Contains configuration files needed to compile the image, specific scripts, and source code of some programs, etc.~~'''timeout = 6000'''</lip>~~<li>~~'''~~LICENSE~~index-url = https://pypi.tuna.tsinghua.edu.cn/simple'''~~: GPL 2 license file~~'''trusted-host = pypi.tuna.tsinghua.edu.cn'''</lip>~~<li>~~'''~~README.md~~EOF'''~~: orangepi-build documentation~~|}</li><li>~~'''scripts''': Common script for compiling linux images~~Then use pip3 to install the Python library very quickly</li></ol></li>~~test@test:~/orangepi-build$~~ <li>How to temporarily change the pip source under Linux, where '''ls<packagename>'''needs to be replaced with a specific package name{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''~~build.sh external LICENSE README.md scripts~~pip3 install <packagename> -i \''' '''~~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~~https://pypi.tuna.tsinghua.edu.cn/simple -~~boot and linux kernel, and there is no cross~~-~~compilation tool required to compile u~~trusted-~~boot and linux kernel~~host pypi. ~~chain, this is normal, because these things are stored in other separate github repositories or some servers (their addresses will be detailed below)~~tuna. ~~Orangepi-build will specify the addresses of u-boot, Linux kernel and cross-compilation tool chain in the script and configuration file~~tsinghua. ~~When running orangepi-build, when it finds that these things are not available locally, it will automatically download them from the corresponding places~~edu.cn'''|}<~~span id="download-the-cross-compilation-tool-chain"~~/li></~~span~~ol>~~=== Download the cross-compilation tool chain ===~~

~~When orangepi~~<span id="how-~~build is run for the first time, it will automatically download the cross~~to-~~compilation '''toolchain''' and put it in the '''toolchains''' folder. Every time you run orangepi~~install-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.docker">

~~<div class~~=~~"figure">~~= How to install Docker ==

~~[[File:zero2w~~The Linux image provided by Orange Pi has Docker pre-~~img273~~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.~~png]]~~

~~</div>~~{| class="wikitable" style="width:800px;" ~~The mirror URL of the cross~~|-~~compilation tool chain in China is the open source software mirror site of Tsinghua University~~| orangepi@orangepi:~$ '''enable_docker.sh'''|}

~~[https://mirrors~~You can use the following command to test docker.~~tuna.tsinghua.edu.cn/armbian-releases/_toolchain/~~ If '''~~https://mirrors.tuna.tsinghua.edu.cn/armbian~~hello-~~releases/_toolchain/~~world''']can be run, docker can be used normally.

~~After toolchains is downloaded, it will contain multiple versions of cross~~{| class="wikitable" style="width:800px;" |-~~compilation t~~| orangepi@orangepi:~$ '''~~toolchain~~docker run hello-world''':

~~test@test~~Unable to find image 'hello-world:~~~/orangepi-build$ '''ls toolchains/''~~latest'locally

~~gcc~~latest: Pulling from library/hello-~~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~~world

~~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~~256ab8fe8778: Pull complete

~~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~~Digest: sha256:7f0a9f93b4aa3022c3a4c147a449ef11e0941a1fd0bf4a8e6c9408b2600777c5

~~gcc~~Status: Downloaded newer image for hello-~~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~~world:latest

~~The cross-compilation tool chain used to compile the H618 Linux kernel source code is:~~

'''<ol span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<li>linux5.4</li>~~Hello from Docker!</olspan>'''

'''~~gcc-arm-11~~This message shows that your installation appears to be working correctly.~~2-2022.02-x86_64-aarch64-none-linux-gnu~~'''

~~<ol start="2" style="list-style-type: lower-alpha;">~~'''.….'''~~<li>linux6.1</li></ol>~~|}

When using the docker command, if you are prompted for '''~~gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu~~permission denied''', please add the current user to the docker user group so that you can run the docker command without sudo.

~~The cross~~{| class="wikitable" style="width:800px;" |-~~compilation tool chain used to compile the H618 u~~| orangepi@orangepi:~$ '''sudo usermod -~~boot source code is:~~aG docker $USER'''|}

~~<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~v2018~~'''Note: You need to log out and log in again to the system to take effect.05You can also restart the system.'''</~~li></ol~~big>|}

~~'''gcc~~

~~<ol start~~=~~"2" style~~=~~"list-style-type: lower-alpha;"><li>v2021.07</li></ol>~~How to install Home Assistant ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~gcc-arm-11~~Note that this article will only provide methods for installing Home Assistant in Ubuntu or Debian systems.~~2-2022~~For detailed usage of Home Assistant, please refer to the official documentation or corresponding books.~~02-x86_64-aarch64-none-linux-gnu~~'''</big>|}

=== ~~orangepi-build complete directory structure description~~ Installation via docker ===

<li>~~After downloading~~First, please install docker and ensure that docker can run normally. For the ~~orangepi-build warehouse does not contain the source code~~ installation steps of ~~the linux kernel~~docker, ~~u-boot and cross-compilation tool chain. The source code of~~ please refer to the ~~linux kernel and u-boot is stored~~ instructions in ~~an independent git warehouse~~the [[Orange Pi Zero 2W#How to install Docker|'''How to Install Docker''']] section.</li><ol li>Then you can search for the docker image of Home Assistant{| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;"|-| orangepi@orangepi:~$ '''docker search homeassistant'''|}</li><li>Then use the following command to download the Docker image of Home Assistant to your local computer. The ~~git warehouse where~~ image size is about 1GB, and the ~~linux kernel source code is stored is as follows~~download time will be relatively long. Please ~~note that~~ be patient and wait for the ~~branch of the linux~~download to complete.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi ~~warehouse is switched~~ :~$ '''docker pull homeassistant/home-assistant'''Using default tag: latestlatest: Pulling from homeassistant/home-assistantbe307f383ecc: Downloading5fbc4c07ac88: Download complete'''...... (Omit some output)'''3cc6a1510c9f: Pull complete7a4e4d5b979f: Pull completeDigest: sha256:81d381f5008c082a37da97d8b08dd8b358dae7ecf49e62ce3ef1eeaefc4381bbStatus: Downloaded newer image for homeassistant/home-assistant:latestdocker.io/homeassistant/home-assistant:latest|}</li><li>Then you can use the following command toview the docker image of Home Assistant you just downloaded~~<ol~~ {| class="wikitable" style="~~list~~width:800px;" |-~~style~~| orangepi@orangepi:~$ '''docker images homeassistant/home-~~type: lower~~assistant'''REPOSITORY                                    TAG       IMAGE       ID       CREATED       SIZEhomeassistant/home-~~alpha~~assistant       latest       bfa0ab9e1cf5       2 months ago      '''1.17GB'''|}</li><li>~~Linux5.4~~At this point you can run the Home Assistant docker container{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''docker run -d \''':'''--name homeassistant \''':'''--privileged \''':'''--restart=unless-stopped \''':'''-e TZ=Asia/Shanghai \''':'''-v /home/orangepi/home-assistant:/config \'''</lip>:'''--network=host \'''</olp>:'''homeassistant/home-assistant:latest'''|}</li><li>Then enter【the IP address of the development board: 8123】in the browser to see the Home Assistant interface</olp>{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''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.'''</lip></olbig>|}<div class="figure">

~~https~~[[File:~~//github.com/orangepi~~zero2w-~~xunlong/linux-orangepi/tree/'''orange-pi-5~~img180.~~4-sun50iw9'''~~png]]

<~~ol start="2" style="list-style-type: lower-alpha;"~~/div></li><li>~~Linux6.1~~Then enter your '''name, username''' and '''password''' and click '''Create Account'''</lip><~~/ol~~div class="figure">

~~https~~[[File:~~//github~~zero2w-img181.~~com~~png]] </~~orangepi-xunlong~~div></~~linux-orangepi~~li><li>Then follow the interface prompts to set according to your own preferences, and then click Next</~~tree/'''orange-pi~~p><div class="figure"> [[File:zero2w-6img182.~~1-sun50iw9'''~~png]]

<~~ol start="2" style="list-style-type: lower-alpha;"~~/div></li><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~~Then click Next<~~ol style~~div class="~~list-style-type: lower-alpha;~~figure">~~<li>v2018.05</li></ol></li></ol~~>

~~https~~[[File:~~//github.com/orangepi-xunlong/u-boot~~zero2w-~~orangepi/tree/'''v2018~~img183.~~05-h618'''~~png]]

<~~ol start="2" style="list-style-type: lower-alpha;"~~/div></li><li>~~v2021.07~~Then click Finish</lip><~~/ol~~div class="figure">

~~https~~[[File:~~//github.com/orangepi-xunlong/u-boot~~zero2w-~~orangepi/tree/'''v2021~~img184.~~07-sunxi'''~~png]]

<~~ol start="2" style="list-style-type: decimal;"~~/div></li><li>~~When orangepi-build~~ The main interface finally displayed by Home Assistant is ~~run for the first time, it will download the cross~~as shown below[[File:zero2w-~~compilation tool chain, u-boot and linux kernel source code~~img185. ~~After successfully compiling a linux image, the files and folders that can be seen in orangepi-build are:~~png]]</li><li>Method to stop Home Assistant container

<li>~~'''build.sh''': Compile startup script</li><li>'''external''': Contains the configuration files needed~~ The command to ~~compile the image, scripts for specific functions, and the source code of some programs. The rootfs compressed package cached during~~ view the ~~image compilation process~~ docker container 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~~docker ps -a'''~~: GPL 2 license file~~|}</li><li>~~'''README.md''': orangepi-build documentation~~The command to stop the Home Assistant container is as follows</p~~></li~~>~~<li>'''output'''~~{| class="wikitable" style="width: ~~Store compiled u~~800px;" |-~~boot, linux and other deb packages, compilation logs, and compiled images and other files</li><li>~~| orangepi@orangepi:~$ '''~~scripts~~docker stop homeassistant'''~~: Common script for compiling linux images~~|}</li><li>~~'''toolchains''': Store cross-compilation tool chain~~The command to delete the Home Assistant container is as follows</p~~></li~~>~~<li>'''u-boot'''~~{| class="wikitable" style="width: ~~Store the source code of u~~800px;" |-~~boot</li><li>~~| orangepi@orangepi:~$ '''~~userpatches~~docker rm homeassistant'''~~: Store the configuration files needed to compile the script~~|}</li></ol>

</li></ol>

~~test@test:~~~</~~orangepi-build$ '''ls'''~~span>

~~'''build.sh external kernel LICENSE output README.md scripts toolchains u-boot userpatches'''~~=== Installation via python ===

~~'''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]]"'''</~~span~~big>~~== 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;"><li>~~Select~~ First install dependency packages{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''Usudo apt-~~boot package~~get update''' ~~and press Enter~~</lip>orangepi@orangepi:~$ '''sudo apt-get install -y python3 python3-dev python3-venv \'''</olp>'''python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential \'''<~~div class="figure"~~p> ~~[[File:zero2w~~'''libopenjp2-7 libtiff5 libturbojpeg0-~~img274.png]]~~ dev tzdata'''</~~div~~p>~~<ol start~~|}{| class="3wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;"|-| <big><lip>~~Then select~~ '''If it is debian12, please use the ~~model of the development board~~following command:'''</lip></olbig>orangepi@orangepi:~$ '''sudo apt-get update'''~~[[File~~orangepi@orangepi:~~zero2w~~~$ '''sudo apt-get install -y python3 python3-dev python3-~~img275.png]]~~venv \''''''python3-pip libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential \'''<~~ol start="4" style="list~~p>'''libopenjp2-~~style~~7 libturbojpeg0-~~type: decimal;"~~dev tzdata'''|}</li><li>Then ~~select~~ you need to compile and install Python3.9. For the ~~branch type of u-boot~~method, please refer to the [[Orange Pi Zero 2W#Python related instructions|'''Python source code compilation and installation method''']] section.~~<ol~~ {| class="wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>'''The ~~current branch will compile the u-boot v2018~~default Python version of Debian Bullseye is Python3.~~05 version code that needs~~ 9, so there is no need to ~~be used by the linux5.4 image~~compile and install it.'''</p~~></li~~>~~<li>~~'''The ~~next branch will compile the u-boot v2021~~default Python version of Ubuntu Jammy is Python3.~~07 version code that needs~~ 10, so there is no need to ~~be used by the linux6.1 image~~compile and install it.'''~~[[File:zero2w-img276~~'''The default Python version of Debian Bookworm is Python3.11, so there is no need to compile and install it.~~png]]~~'''</~~li></ol~~big>|}

</li>

<li>~~If you select the next branch~~Then create a Python virtual environment{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Debian Bookworm is python3.11, ~~you will also be prompted~~ please remember to ~~select~~ replace the ~~memory size, and you do not need to select the current branch~~corresponding command.'''</libig>|}{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo mkdir /olsrv/homeassistant'''orangepi@orangepi:~$ '''sudo chown orangepi:orangepi /srv/homeassistant'''<~~blockquote~~p>orangepi@orangepi:~$ '''cd /srv/homeassistant'''~~a. If the development board you purchased has a memory size of 1.5GB, please select the first option.~~ borangepi@orangepi:~$ '''python3. ~~If the development board you purchased has 1GB or 2GB or 4GB memory size, please choose the second option~~9 -m venv .'''orangepi@orangepi:~$ '''source bin/~~blockquote~~activate'''~~[[File~~(homeassistant) orangepi@orangepi:~~zero2w-img277.png]]~~/srv/homeassistant$|}</li><~~ol start~~li>Then install the required Python packages{| class="6wikitable" style="~~list-style-type~~width: ~~decimal~~800px;"|-| (homeassistant) orangepi@orangepi:/srv/homeassistant$ '''python3 -m pip install wheel'''|}</li><li>Then ~~it will start to compile u-boot. Some of the information prompted when compiling the next branch is as follows:~~you can install Home Assistant Core~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">|-| <lip>~~Version of u-boot source code~~(homeassistant) orangepi@orangepi:/srv/homeassistant$ '''pip3 install homeassistant'''</lip>|}</olli></li>Then enter the following command to run Home Assistant Core</olp>{| class="wikitable" style="width:800px;" ~~[ o.k. ] Compiling u~~|-~~boot [~~ | (homeassistant) orangepi@orangepi:/srv/homeassistant$ '''~~v2021.07~~hass''' ]|}<~~ol start~~/li><li>Then enter【'''development board IP address: 8123'''】 in the browser to see the Home Assistant interface{| class="2wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;"|-| <big><lip>~~Version of~~ '''When you run the hass command for the ~~cross-compilation tool chain~~first time, some libraries and dependency packages necessary for operation will be downloaded, installed and cached. This process may take several minutes. Note that you cannot see the Home Assistant interface in the browser at this time. Please wait for a while and then refresh it.'''</lip></olbig>|}<div class="figure">

[ ~~o.k~~[File:zero2w-img180. png] ~~Compiler version [ '''aarch64-linux-gnu-gcc 11'''~~ ]

<~~ol start="3" style="list-style-type: lower-alpha;"~~/div>~~<li>Path to the compiled u-boot deb package~~</li></ol>

~~[ o.k. ] Target directory [ '''orangepi~~</~~u-boot''' ]~~span>

~~<ol start~~=~~"4" style~~=~~"list-style-type: lower-alpha;"><li>The package name of the compiled u-boot deb package</li></ol>~~OpenCV installation method ==

~~[ o.k. ] File name [ '''linux~~=== Use apt to install OpenCV ===

<ol ~~start="5"~~ style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Compilation time~~<~~/li~~p>The installation command is as follows</olp> ~~[ o.k. ] Runtime [ '''1 min''' ]~~ ~~<ol start~~{| class="6wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;">~~<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~~p>~~</ol>~~ ~~[ o.k. ] Repeat Build Options [~~ orangepi@orangepi:~$ '''sudo ~~./build.sh BOARD=orangepizero2w BRANCH=next BUILD_OPT=u~~apt-~~boot~~get update''' ] <~~ol start="7" style="list-style-type: decimal;"~~/p><lip>~~View the compiled u-boot deb package</li></ol>~~ ~~test~~orangepi@~~test~~orangepi:~~~/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 the orangepi~~sudo apt-~~bulid compilation system compiles the u~~get install -~~boot source code, it will first synchronize the u~~y libopencv-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 compile u-boot before you can turn off this function, otherwise it will prompt that the source code of udev python3-~~boot cannot be found~~opencv'''~~), otherwise the modifications will be restored. The method is as follows:~~</~~li></ol~~p>|}<~~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><li>~~When debugging u-boot code, you can~~ Then use the following ~~method~~ command to ~~update u-boot in~~ print the version number of OpenCV. The output is normal, indicating that the ~~linux image for testing~~OpenCV installation is successful.

<li>~~First upload the compiled deb package~~ The version of uOpenCV 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 of OpenCV in Ubuntu20.04 is as follows:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3 -c "import cv2; print(cv2.__version__)"''''''4.2.0'''|}</li><li>The version of OpenCV in Debian11 is as follows:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3 -~~boot to the Linux system~~ c "import cv2; print(cv2.__version__)"''''''4.5.1'''|}</li><li>The version of ~~the development board~~OpenCV in Debian12 is as follows:{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''python3 -c "import cv2; print(cv2.__version__)"''''''4.6.0'''|}</li></ol>

</li></ol>

~~test@test:~/orangepi~~</~~debs/u-boot'''~~span>

~~test@test:~/orangepi_build/output/debs/u-boot$ '''scp \'''~~== Set up the Chinese environment and install the Chinese input method ==

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''~~linux-u-boot-next-orangepizero2w_x.x.x_arm64.deb [mailto:root@192.168.1~~Note, before installing the Chinese input method, please make sure that the Linux system used by the development board is a desktop version.~~xxx:/root root@192.168.1.xxx:/root]~~'''</big>|}

<~~ol start~~span id="~~2" style="list~~debian-~~style~~system-~~type: lower~~installation-~~alpha;~~method">~~<li>Install the new u-boot deb package just uploaded~~</~~li></ol~~span>=== Debian system installation method ===

<ol style="list-style-type: decimal;"><li>First set the default '''locale''' to Chinese<ol style="list-style-type: lower-alpha;"><li>Enter the following command to start configuring '''locale'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo dpkg-reconfigure locales'''|}</li><li>Then select '''zh_CN.UTF-8 UTF-8''' in the pop-up interface (use the up and down keys on the keyboard to move up and down, use the space bar to select, and finally use the Tab key to move the cursor to '''<OK>''', and then return Car can be used)[[File:zero2w-img186.png]]</li><li>Then set the default '''locale''' to '''zh_CN.UTF-8'''[[File:zero2w-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 -ireconfigure 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 '''~~linux~~Input Method'''[[File:zero2w-uimg188.png]]</li><li>Then select '''OK'''[[File:zero2w-~~boot~~img189.png]]</li><li>Then select '''Yes'''[[File:zero2w-~~next~~img190.png]]</li><li>Then select '''fcitx'''[[File:zero2w-img191.png]]</li><li>Then select '''OK'''[[File:zero2w-~~orangepizero2w_x~~img192.png]]</li><li>'''Then restart the Linux system to make the configuration take effect.x'''</li><li>Then open '''Fcitx configuration'''[[File:zero2w-img193.~~x_arm64~~png]]</li><li>Then click the + sign as shown in the picture below[[File:zero2w-img194.~~deb~~png]]</li><li>Then search '''Google Pinyin''' and click '''OK'''<div class="figure">

~~<ol start="3" style="list-style-type~~[[File: ~~lower-alpha;"><li>Then run the nand-sata~~zero2w-~~install script</li></ol>~~img195.png]]

</div></li><li>Then put '''Google Pinyin''' on top[[File:zero2w-img196.png]][[File:zero2w-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 ~~nand~~vim /etc/default/locale'''# File generated by update-localeLC_MESSAGES='''zh_CN.UTF-8'''LANG='''zh_CN.UTF-~~sata~~8'''LANGUAGE='''zh_CN.UTF-~~install~~8'''|}</li><li>Then '''restart the system''' and you will see that the system is displayed in Chinese.[[File:zero2w-img200.png]]</li></ol>

<~~ol start~~span id="~~4" style="list~~installation-method-of-~~style~~ubuntu-~~type: lower~~20.04-~~alpha;~~system">~~<li>Then select '''5 Install/Update the bootloader on SD/eMMC'''</li~~></olspan>

~~[[File:zero2w-img278~~=== Installation method of Ubuntu 20.~~png]]~~04 system ===

<ol style="list-style-type: decimal;"><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>|}</ol><ol start="54" style="list-style-type: ~~lower~~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-~~alpha;~~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 ~~pressing~~ opening '''Geany''', the ~~Enter~~ English input method is still the default. We can switch to the Chinese input method through the '''Ctrl+Space''' shortcut key, ~~a Warning will pop up first~~and then we can input Chinese.[[File:zero2w-img209.png]]</li></ol>

~~[[File:zero2w~~

~~<ol start~~=~~"6" style~~=~~"list-style-type: lower-alpha;"><li>Press the Enter key again to start updating u-boot~~= Installation method of Ubuntu 22. ~~After the update is completed, the following information will be displayed.</li></ol>~~04 system ===

<ol style="list-style-type: decimal;"><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><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-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-~~img280~~img213.png]]</li><li>Then choose to use Pinyin input method<div class="figure">

~~<ol start="7" style="list-style-type~~[[File: ~~lower-alpha;"><li>Then you can restart the development board to test whether the u~~zero2w-~~boot modification has taken effect~~img214.~~</li></ol>~~png]]

<~~span id="compile~~/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 theChinese input method. The opening method is as shown in the figure below[[File:zero2w-~~linux-kernel"~~img208.png]]</~~span~~li>~~== Compile~~ <li>After opening '''Geany''', the ~~linux kernel ==~~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>

~~# Run~~

~~test@test:~/orangepi-build$ '''sudo ./build.sh'''~~== How to remotely log in to the Linux system desktop ==

<~~ol start~~span id="~~2" style="list~~remote-login-~~style~~using-~~type: decimal;~~nomachine">~~<li>Select '''Kernel package''' and press Enter~~</~~li></ol~~span>=== Remote login using NoMachine ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Please ensure that the Ubuntu or Debian system installed on the development board is a <~~div class~~span style="~~figure~~color:#FF0000">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 follows:'''

~~[[File~~'''https:~~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~~/knowledgebase. ~~If you need to modify the kernel configuration, select the second one~~nomachine.<com/~~li>~~DT10R00166'''</olbig>|}~~[[File:zero2w-img282.png]]~~ ~~<ol start~~{| class="4wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">~~<li>Then select the model of the development board</li></ol>~~ ~~[[File:zero2w~~|-~~img275.png]]~~| <~~ol start="5" style="list-style-type: decimal;"~~big>~~<li>Then select~~ '''NoMachine supports Windows, Mac, Linux, iOS and Android platforms, so we can remotely log in and control the ~~branch type~~ Orange Pi development board through NoMachine on a variety of ~~the kernel source code</li></ol>~~ ~~<blockquote>a~~devices. The ~~current branch will compile~~ following demonstrates how to remotely log in to the Linux system desktop of the ~~linux5~~Orange Pi development board through NoMachine in Windows.~~4 kernel source code~~ bFor installation methods on other platforms, please refer to NoMachine's official documentation. ~~The next branch will compile the linux6.1 kernel source code~~'''</~~blockquote~~big>~~[[File:zero2w-img276.png]]~~|}~~<ol start~~{| class="6wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~If you choose to display~~ '''Before operating, please make sure that the ~~kernel configuration menu (~~Windwos computer and the ~~second option)~~ development board are in ~~step 3),~~ the ~~kernel configuration interface opened through '''make menuconfig''' will pop up. At this time~~same LAN, and that you can ~~directly modify~~ log in to the ~~kernel configuration. After modification, save and exit. Yes, compilation~~ Ubuntu or Debian system of the ~~kernel source code will begin after exiting~~development board through ssh normally.'''</~~li></ol~~big> ~~[[File:zero2w-img283.png]]~~|}

<li>First download the installation package of the NoMachine software Linux '''arm64''' deb version, and then install it into the Linux system of the development board

<li>~~If you do not~~ Since H618 is an ARMv8 architecture SOC and the system we use is Ubuntu or Debian, we need to ~~modify~~ download the ~~kernel configuration options, when running the build.sh script, pass~~ '''~~KERNEL_CONFIGURE~~NoMachine for ARM ARMv8 DEB''' installation package. The download link is as follows:</li>{| class="wikitable" style=no"background-color:#ffffdc;width:800px;" |-| <big>''' ~~to temporarily block~~ Note that this download link may change, please look for the ~~pop-up~~ Armv8/Arm64 version of the ~~kernel configuration interface~~deb package.'''</~~li></ol~~big>|}{| class="wikitable" style="width:800px;" |-| ~~test@test~~[https:~/~~orangepi-build$~~ /www.nomachine.com/download/download&id=112&s=ARM '''~~sudo~~ https://downloads.nomachine.com/~~build.sh KERNEL_CONFIGURE~~download/?id=118&distro=noARM''']|}

[[File:zero2w-img217.png]]

</ol>

<li>~~b. You~~ In addition, you can also ~~set~~ download the '''~~KERNEL_CONFIGURE=no~~NoMachine''' in installation package from the ~~orangepi-build~~official tool.</~~userpatches/config~~p>[[File:zero2w-~~default.confconfiguration file to permanently disable this function~~img218.png]]First enter the '''remote login software-NoMachine''' folder</lip>~~<li>~~If the following error is prompted when compiling the kernel, it is because the Ubuntu PC terminal interface is too small, causing the make menuconfig interface to be unable to be displayed. Please increase the Ubuntu PC terminal to the maximum size, and then rerun the build.sh script[[File:zero2w-img219.png]]<~~/li~~p>Then download the arm64 version of the deb installation package</olp> [[File:zero2w-~~img284~~img220.png]]</li> <~~ol start="7" style="list-style-type: decimal;"~~li>Then upload the downloaded '''nomachine_x.x.x_x_arm64.deb''' to the Linux system of the development board</li><li>~~Part~~ Then use the following command to install '''NoMachine''' in the Linux system of the ~~information prompted when compiling the next branch kernel source code is explained as follows:~~development board~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;"|-| orangepi@orangepi:~$ '''sudo dpkg -i nomachine_x.x.x_x_arm64_arm64.deb'''<li/p>~~Version of the linux kernel source code~~|}</li></ol>

</li></ol>

<li>Then download the installation package of the Windows version of the NoMachine software. The download address is as follows</li>

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

|-

|

<big>'''Note that this download link may change.'''</big>

|}

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

|-

|

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

|}

[ o[File:zero2w-img221.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then install NoMachine in Windows.k'''Please restart your computer after installation.'''</li><li>Then open '''NoMachine''' in Window[[File:zero2w-img222. png] ~~Compiling current kernel~~ ]</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 '''~~6.1.31~~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 start~~span id="~~2" style="list~~remote-~~style~~login-~~type: lower~~using-~~alpha;~~vnc">~~<li>The version of the cross-compilation tool chain used</li~~></olspan>

~~[ o.k. ] Compiler version [ '''aarch64-linux-gnu-gcc 11''' ]~~=== Remote login using VNC ===

~~<ol start~~{| class="3wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~lower-alpha~~800px;">|-| <libig>~~The default configuration file used by~~ '''Before operating, please make sure that the ~~kernel~~ Windwos computer and the ~~path where it is stored~~ development board are ~~as follows</li></ol>~~in the same LAN, and that you can log in to the Ubuntu or Debian system of the development board through ssh normally.'''

~~[ o.k. ] Using kernel config file [~~ '''~~orangepi-build/external/config/kernel/linux-6~~There are many problems with VNC testing in Ubuntu20.~~1-sun50iw9-next~~04, please do not use this method.~~config~~''' ]</big>|}

<ol ~~start="4"~~ style="list-style-type: ~~lower-alpha~~decimal;"><li>~~The path~~ First run the '''set_vnc.sh''' script to set up vnc, '''remember to ~~the kernel~~add sudo permission'''s{| class="wikitable" style="width:800px;" |-~~related deb package generated by compilation~~| orangepi@orangepi:~$ '''sudo set_vnc.sh'''</lip>You will require a password to access your desktops.</olp>

~~[ o.k. ] Target directory [ '''output/debs/''' ]~~

<~~ol start~~p>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<li/span>~~The package name of the kernel image deb package generated by compilation~~'''</lip>xauth: file /root/.Xauthority does not exist</olp>

~~[ o.k. ] File name [ '''linux-image-next-sun50iw9_x.x.x_arm64.deb''' ]~~

<~~ol start="6" style="list-style-type~~p>New 'X' desktop is orangepi: ~~lower-alpha;"><li>Compilation time</li>~~1</olp>

~~[ o.k. ] Runtime [ '''10 min''' ]~~

<~~ol start="7" style="list-style-type: lower-alpha;"~~p>Creating default startup script /root/.vnc/xstartup<lip>Finally, the compilation command to repeatedly compile the last selected kernel will be displayed. Use the following command without selecting through the graphical interface, and you can directly start compiling the kernel source codeStarting applications specified in /root/.vnc/xstartup</lip>Log file is /root/.vnc/orangepi:1.log</olp>

~~[ 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<ol style="list-style-type: lower-alpha;"><li>~~~~'''linux-dtb-next-sun50iw9_x.x.x_arm64.deb''' Contains dtb files used by the kernel~~Killing Xtightvnc process ID 3047</p~~></li><li>'''linux-headers-next-sun50iw9_x.x.x_arm64.deb''' Contains kernel header files</li><li>'''linux-image-next-sun50iw9_x.x.x_arm64.deb''' Contains kernel images and kernel modules</li></ol></li></ol~~>

~~test@test:~/orangepi-build$ '''ls output/debs/linux-*'''~~

~~output~~New 'X' desktop is orangepi:1</~~debs/linux-dtb-next-sun50iw9_x.x.x_arm64.deb~~p>

~~output/debs/linux-headers-next-sun50iw9_x.x.x_arm64.deb~~

~~output~~Starting applications specified in /~~debs~~root/~~linux-image-next-sun50iw9_x~~.~~x.x_arm64.deb~~ vnc/xstartup<~~ol start="9" style="list-style-type: decimal;"~~/p><lip>When the orangepi-bulid compilation system compiles the linux kernel source code, it will first synchronize the linux kernel source code with the linux kernel source code of the github server. 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 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 modifications will be restored. The method Log file is ~~as follows:<~~/~~li><~~root/~~ol>~~ ~~<blockquote>Set the IGNORE_UPDATES variable in '''userpatches~~.vnc/~~config-default~~orangepi:1.~~conf''' to "yes"~~log</~~blockquote~~p>~~test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''~~ ~~IGNORE_UPDATES="'''yes'''"~~|}<~~ol start="10" style="list-style-type: decimal;"~~/li><li>~~If the kernel is modified, you can~~ The steps to use ~~the following method~~ MobaXterm software to connect to ~~update the kernel and kernel module of~~ the development board Linux systemdesktop are as follows:

<li>~~Upload~~ First click Session, then select VNC, then fill in the ~~compiled deb package of the Linux kernel to the Linux system~~ IP address and port of the development board, and finally click OK to confirm.</li~~></ol></li></ol~~>

~~test@test:~/orangepi-build$ '''cd output/debs'''~~<div class="figure">

~~test@test~~[[File:~~~/orangepi~~zero2w-~~build/output/debs$ '''scp \'''~~ ~~'''linux-image-next-sun50iw9_x~~img227.~~x.x_arm64.deb root@192.168.1.xxx:/root'''~~png]]

</div></ol>

<li>~~Install~~ 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 ~~deb package~~ desktop of the ~~new linux kernel just uploaded~~development board Linux system.</lip></olli>

~~orangepi@orangepi~~[[File:~~~$ '''sudo dpkg~~ zero2w-~~i linux~~img229.png]]</ol></li></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></ol>~~QT installation method ==

~~orangepi@orangepi:~$ '''sudo''' '''reboot'''~~ ~~== Compile rootfs ==~~ ~~# 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 '''Rootfs and all deb packages''' and press Enter~~<~~/li~~p>Use the following script to install QT5 and QT Creator</olp> ~~<div~~ {| class="~~figure">~~ ~~[[File:zero2w-img285.png]]~~ ~~</div><ol start="3~~wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">|-| <lip>~~Then select the model of the development board~~orangepi@orangepi:~$ '''install_qt.sh'''</lip>~~</ol>~~ ~~[[File:zero2w-img275.png]]~~|}<~~ol start="4" style="list-style-type: decimal;"~~/li><li>~~Then select the branch type of the kernel source code. Different versions of~~ After installation, the ~~kernel source code maintain different rootfs types~~QT version number will be automatically printed.

<li>~~In the current branch, you can see three options~~The qt version that comes with Ubuntu20.04 is '''5.12.8'''{| class="wikitable" style="width: ~~debian11, ubuntu20~~800px;" |-| orangepi@orangepi:~$ '''install_qt.sh'''......QMake version 3.1Using Qt version '''5.12.8''' in /usr/lib/aarch64-linux-gnu|}</li><li>The QT version that comes with Ubuntu22.04~~, and ubuntu22~~is '''5.15.043'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_qt.sh'''......QMake version 3.1Using Qt version '''5.15.3''' in /usr/lib/aarch64-linux-gnu|}</li><li>~~In the next branch, you can see three options~~The QT version that comes with Debian11 is '''5.15.2'''{| class="wikitable" style="width: ~~debian11, debian12, and ubuntu22~~800px;" |-| orangepi@orangepi:~$ '''install_qt.sh'''.....04.QMake version 3.1Using Qt version '''5.15.2''' in /usr/lib/aarch64-linux-gnu|}</li><li>The QT version that comes with Debian12 is '''5.15.8'''</olp>{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_qt.sh'''......QMake version 3.1Using Qt version '''5.15.8''' in /usr/lib/aarch64-linux-gnu|}

</li></ol>

</li><li>Then you can see the QT Creator startup icon in '''Applications'''[[File:zero2w-~~img276~~img230.png]]You can also use the following command to open QT Creator~~<ol start~~{| class="5wikitable" style="~~list-style-type~~width: ~~decimal~~800px;"|-| orangepi@orangepi:~$ '''qtcreator'''|}</li>~~Then select the type of rootfs~~</li>The interface after QT Creator is opened is as follows</olp> [[File:zero2w-~~img286~~img231.png]]</li><li>The version of QT Creator is as follows<ol ~~start="6"~~ style="list-style-type: ~~decimal~~lower-alpha;"><li>The default version of QT Creator in '''Ubuntu20.04''' is as follows[[File:zero2w-img232.png]]</li><li>The default version of QT Creator in '''Ubuntu22.04''' is as follows[[File:zero2w-img233.png]]</li><li>The default version of QT Creator in '''Debian11''' is as follows[[File:zero2w-img234.png]]</li><li>The default version of QT Creator in '''Debian12''' is as follows[[File:zero2w-img235.png]]</li></ol></li><li>Then ~~select the type of image~~set up QT

<li>First open '''~~Image with console interface (server)~~Help'''->'''About Plugins...''' ~~Represents~~ .[[File:zero2w-img236.png]]</li><li>Then remove the ~~image~~ check mark of '''ClangCodeModel'''[[File:zero2w-img237.png]]</li><li>'''After setting up, you need to restart QT Creator'''</li><li>Then make sure the GCC compiler used by QT Creator. If the default is Clang, please change it to GCC.{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Debian12 please skip this step.'''</big>|}[[File:zero2w-img238.png]][[File:zero2w-img239.png]]</li></ol></li><li>Then you can open a sample code[[File:zero2w-img240.png]]</li><li>After clicking on the ~~server version~~sample code, ~~which is relatively small in size~~the corresponding instruction document will automatically open. You can read the instructions carefully.[[File:zero2w-img241.png]]</li><li>Then click '''~~Image with desktop environment~~Configure Project''' ~~Represents an image with~~ [[File:zero2w-img242.png]]</li><li>Then click the green triangle in the lower left corner to compile and run the sample code[[File:zero2w-img243.png]]</li><li>After waiting for a ~~desktop~~period of time, the interface shown in the figure below will pop up, which ~~is relatively large in size~~means that QT can compile and run normally.[[File:zero2w-img244.png]]</li><li>References{| class="wikitable" style="width:800px;" |-| [https://wiki.qt.io/Install_Qt_5_on_Ubuntu '''https://wiki.qt.io/Install_Qt_5_on_Ubuntu'''][https://download.qt.io/archive/qtcreator '''https://download.qt.io/archive/qtcreator'''][https:/ol/download.qt.io/archive/qt '''https://download.qt.io/archive/qt''']|}

</li></ol>

<~~div class~~span id="~~figure~~ros-installation-method">

~~[[File:zero2w-img287.png]]~~== ROS installation method ==

<~~/div><ol start~~span id="~~7" style="list~~how-to-install-ros-~~style~~1-~~type: decimal;"><li>If you are compiling the server version of the image, you can also choose to compile the Standard version or the Minimal version. The Minimal version will have much less pre~~noetic-~~installed software than the Standard version ('''please do not choose the Minimal version without special needs, because many things are not pre~~on-~~installed by default~~ubuntu20. ~~Some functions may not be available''')</li~~04"></olspan>=== How to install ROS 1 Noetic on Ubuntu20.04 ===

~~<div class="figure">~~# The currently active version of ROS 1 is as follows, the recommended version is '''Noetic Ninjemys'''

::[[File:zero2w-~~img288~~img245.png]]

~~</div><ol start="8" style="list-style~~::[[File:zero2w-~~type: decimal;"><li>If you are compiling a desktop version of the image, you also need to select the type of desktop environment. Currently, only XFCE is maintained, so please select an XFCE type desktop~~img246.~~</li></ol>~~png]]

::{| class="wikitable" style="width:800px;" |-| [~~[File~~http://docs.ros.org/ '''http:~~zero2w-img289~~//docs.ros.~~png]~~org''']

~~[[File~~'''https:~~zero2w-img290~~//wiki.~~png]]~~ros.org/Distributions'''|}

~~You~~ <ol start="2" style="list-style-type: decimal;"><li>The link to the official installation documentation of ROS 1 '''Noetic Ninjemys''' is as follows:{| class="wikitable" style="width:800px;" |-| [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'''.{| class="wikitable" style="width:800px;" |-| [http://wiki.ros.org/noetic/Installation '''http://wiki.ros.org/noetic/Installation'''][[File:zero2w-img247.png]]|}</li><li>Then use the script below to install ros1{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''install_ros.sh ros1'''|}</li><li>Before using the ROS tool, you first need to initialize rosdep. Then when compiling the source code, you can ~~then select additional packages~~ 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 ~~installed. Please press the Enter key here~~ reported due to ~~skip directly~~network problems.'''

~~[[File:zero2w-img291.png]]~~

~~<ol start="9" style="list-style-type: decimal;"><li>Then~~ '''The install_ros.sh script will try to modify /etc/hosts and automatically run the ~~compilation of rootfs will start~~following commands. However, this method cannot guarantee that github can be accessed normally every time. If install_ros. ~~Some~~ sh prompts the following error after installing ros1, please find other ways to allow the linux system of the ~~information prompted during compilation are as follows:<ol style="list-style-type: lower-alpha;"><li>Type of rootfs</li></ol></li></ol>~~development board to access github normally, and then manually run the following Order.'''

~~[ o.k. ] local not found [ Creating new rootfs cache for '''bullseye''' ]~~

~~<ol start="2" style="list-style-type~~'''https: ~~lower-alpha;"><li>The storage path of the compiled rootfs compressed package<~~/~~li><~~/~~ol>~~raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml'''

~~[ o.k. ] Target directory [~~ '''~~orangepi-build~~Hit https:/~~external~~/~~cache~~raw.githubusercontent.com/~~rootfs~~ros/rosdistro/master/rosdep/base.yaml''' ]

'''<~~ol start="3"~~ span style="~~list-style-type~~color: ~~lower-alpha;~~#FF0000">~~<li>The name of the rootfs compressed package generated by compilation</li>~~ERROR: error loading sources list:</olspan>'''

~~[ o.k. ] File name [~~ ::'''The read operation timed out'''~~bullseye~~</big>|}{| class="wikitable" style="width:800px;" |-~~xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar~~| orangepi@orangepi:~$ '''source /opt/ros/noetic/setup.~~lz4~~bash''' ]

~~<ol start="10" style="list-style-type~~orangepi@orangepi: ~~decimal;"><li>View the compiled rootfs compressed package<ol style="list-style-type: lower-alpha;"><li>~~~$ '''~~bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4~~sudo rosdep init''' ~~It is a compressed package of rootfs. The meaning of each field in the name is</li></ol></li></ol>~~

~~<blockquote>a) '''bullseye''' represents the type of Linux distribution of rootfs~~Wrote /etc/ros/rosdep/sources.list.d/20-default.list

~~b) '''xfce''' indicates that the rootfs is the desktop version, and if it is cli, it indicates the server version.~~Recommended: please run

~~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~~</blockquote><ol start="2" style="list-style-type~~: ~~lower-alpha;"><li>'''bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4.list''' Lists the package names of all packages installed by rootfs</li></ol>~~:rosdep update

~~test~~orangepi@~~test~~orangepi:~~~/orangepi-build~~$ '''~~ls external/cache/rootfs/~~rosdep update'''

~~bullseye-xfce-arm64~~reading in sources list data from /etc/ros/rosdep/sources.~~5250ec7002de9e81a41de169f1f89721~~list.~~tar.lz4~~d

~~bullseye-xfce-arm64~~Hit https://raw.~~5250ec7002de9e81a41de169f1f89721~~githubusercontent.~~tar.lz4~~com/ros/rosdistro/master/rosdep/osx-homebrew.~~current~~yaml

~~bullseye-xfce-arm64~~Hit https://raw.~~5250ec7002de9e81a41de169f1f89721~~githubusercontent.~~tar~~com/ros/rosdistro/master/rosdep/base.~~lz4.list~~yaml

~~<ol start="11" style="list-style-type~~Hit https: ~~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~~raw. ~~When compiling the image, it will also go to '''external~~githubusercontent.com/ros/~~cache~~rosdistro/~~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.<~~master/~~li><~~rosdep/~~ol>~~python.yaml

~~<~~Hit https:/~~span>== Compile linux image ==~~/raw.githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml

~~# Run the '''build~~Hit https://raw.~~sh''' script, remember to add sudo permissions~~githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml

~~test@test~~Query rosdistro index https:~/~~orangepi-build$ '''sudo~~ /raw.githubusercontent.com/~~build~~ros/rosdistro/master/index-v4.~~sh'''~~yaml

~~<ol start="2" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "ardent"">~~<li>Select '''Full OS image for flashing''' and press Enter</li></ol>~~

~~<div class="figure">~~Skip end-of-life distro "bouncy"

~~[[File:zero2w~~Skip end-~~img292.png]]~~of-life distro "crystal"

~~</div><ol start="3" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "dashing"">~~<li>Then select the model of the development board</li></ol>~~

~~[[File:zero2w~~Skip end-~~img275.png]]~~of-life distro "eloquent"

~~<ol start="4" style="list-style-type: decimal~~Add distro "">~~<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~~foxy"">~~<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></ol></li></ol>~~

~~[[File:zero2w-img276.png]]~~Add distro "galactic"

~~<ol start="5" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "">~~<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~~groovy"">~~<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></ol>~~

~~[[File:zero2w-img286.png]]~~Add distro "humble"

~~<ol start="7" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "">~~<li>Then select the type of image<ol style="list-style-type: lower-alpha~~hydro"">~~<li>'''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.</li></ol></li></ol>~~

~~<div class="figure">~~Skip end-of-life distro "indigo"

~~[[File:zero2w~~Skip end-~~img287.png]]~~of-life distro "jade"

~~</div><ol start="8" style="list~~Skip end-~~style~~of-~~type: decimal~~life distro "kinetic""><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>

~~<div class="figure">~~Skip end-of-life distro "lunar"

~~[[File:zero2w-img288.png]]~~Add distro "melodic"

~~</div><ol start="9" style="list-style-type: decimal~~Add distro "noetic"">~~<li>If you are compiling a desktop version of the image, you also need to select the type of desktop environment. Currently, only XFCE is maintained, so please select an XFCE type desktop.</li></ol>~~

~~[[File:zero2w-img289.png]]~~Add distro "rolling"

updated cache in /home/orangepi/.ros/rosdep/sources.cache|}</ol><ol start="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.{| 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-~~img290~~img248.png]]</li><li>Then please keep the terminal window you just opened at the top</li>

~~You can then select additional packages that need to be installed. Please press the Enter key here to skip directly.~~<div class="figure">

[[File:zero2w-~~img291~~img249.png]]

</div></ol><ol start="109" style="list-style-type: decimal;"><li>~~Then~~ At this time, press the ~~compilation of~~ direction keys on the ~~linux image will begin~~keyboard to control the little turtle to move up, down, left, and right. ~~The general process of compilation is as follows~~[[File:zero2w-img250.png]]</li></ol>

~~a. Initialize the compilation environment of Ubuntu PC and~~

b=== How to install ROS 2 Galactic on Ubuntu20. ~~Download the source code of u-boot and linux kernel (if already cached, only update the code)~~04 ===

~~c. Compile u~~<ol style="list-~~boot source code and generate u~~style-~~boot deb package~~type: decimal;"><li>The currently active version of ROS 2 is as follows, the recommended version is '''Galactic Geochelone'''d[[File:zero2w-img251. ~~Compile linux source code and generate linux~~png]][[File:zero2w-~~related deb packages~~ eimg252. ~~Make the deb package of linux firmware~~png]]{| class="wikitable" style="width:800px;" ~~f. Make the deb package of orangepi~~|-~~config tool~~| g[http://docs. ~~Create a deb package with board-level support~~ hros.org/ '''http://docs. ~~If you compile the desktop version image, you will also create a desktop-related deb package~~ros.org'''] i'''http://docs. ~~Check whether rootfs has been cached~~ros. ~~If not, re-create rootfs. If it has been cached, decompress it directly and use it~~org/en/galactic/Releases.html'''|}</li>~~j. Install~~ <li>The link to the ~~deb package generated previously into rootfs~~official installation documentation of ROS 2 '''Galactic Geochelone''' is as follows:{| class="wikitable" style="width:800px;" ~~k. Make some specific settings for different development boards and different types of images, such as pre~~|-~~installing additional software packages, modifying system configurations, etc.~~| l'''docs. ~~Then create the image file and format the partition~~ros. ~~The default type is ext4~~org/en/galactic/Installation.html''' m'''http://docs.ros. ~~Then copy the configured rootfs to the mirror partition~~org/en/galactic/Installation/Ubuntu-Install-Debians.html'''|}~~n. Then update initramfs~~</li> o<li>In the official installation documentation of ROS 2 '''Galactic Geochelone''', Ubuntu Linux recommends using Ubuntu20. ~~Finally~~04, ~~write~~ so please ensure that the ~~bin file of u-boot into~~ system used by the ~~image through~~ development board is the ~~dd command.~~ '''<~~ol start="11"~~ span style="~~list-style-type~~color: ~~decimal;~~#FF0000">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'''.</li><li>~~After compiling~~ Use the ~~image, the following message will be displayed~~'''install_ros.sh''' script to install ros2~~<ol~~ {| class="wikitable" style="~~list-style-type~~width: ~~lower-alpha~~800px;"|-| orangepi@orangepi:~$ '''install_ros.sh ros2'''|}</li>~~The storage path of the compiled image~~</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.</olp>{| class="wikitable" style="width:800px;" |-| <~~/li~~p>usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...</olp>

~~[ 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="~~p>ros2 is an extensible command-line tool for ROS 2~~" style="list-style-type: lower-alpha;"><li>Compilation time</li>~~.</olp>

~~'''[ o.k. ] Runtime [ 19 min ]'''~~

<~~ol start="3" style="list-style-type~~p>optional arguments: ~~lower-alpha;"~~:<~~li>Repeat the command to compile the image. Use the following command to start compiling the image directly without selecting it through the graphical interface.</li~~p>-h, --help show this help message and exit</olp>

~~[ 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 id="instructions~~p>Commands::action Various action related sub-~~for~~commands:bag Various rosbag related sub-~~using~~commands:component Various component related sub-~~the~~commands:daemon Various daemon related sub-~~orange~~commands:doctor Check ROS setup and other potential issues:interface Show information about ROS interfaces:launch Run a launch file:lifecycle Various lifecycle related sub-picommands:multicast Various multicast related sub-commands:node Various node related sub-commands:param Various param related sub-commands:pkg Various package related sub-commands:run Run a package specific executable:security Various security related sub-oscommands:service Various service related sub-~~arch~~commands:topic Various topic related sub-~~system"~~commands:wtf Use `wtf` as alias to `doctor`</~~span~~p>

~~= '''Instructions for using the Orange Pi OS Arch system''' =~~

:<~~span id="orange~~p>Call `ros2 <command> -~~pi-os-arch-system-function-adaptation-status"~~h` for more detailed usage.|}</~~span~~li>~~== Orange Pi OS Arch system function adaptation status ==~~<li>Then you can use the '''test_ros.sh''' script to test whether ROS 2 is installed successfully. If you can see the following print, it means ROS 2 can run normally.{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~Motherboard functions~~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: '~~OPi OS Arch~~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="width:800px;"

|-

| orangepi@orangepi:~$ '''~~HDMI video~~source /opt/ros/galactic/setup.bash'''| orangepi@orangepi:~$ '''OKros2 run rviz2 rviz2'''|}[[File:zero2w-img253.png]]</li><li>For how to use ROS, please refer to the documentation of ROS 2.{| class="wikitable" style="width:800px;"

|-

| [http://docs.ros.org/en/galactic/Tutorials.html '''~~HDMI Audio~~http://docs.ros.org/en/galactic/Tutorials.html''']| }</li></ol> === How to install ROS 2 Humble on Ubuntu22.04 === <ol style="list-style-type: decimal;"><li>Use the install_ros.sh script to '''OKinstall_ros.sh'''{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~Type-C USB2~~install_ros.~~0 x 2~~sh ros2'''| }</li><li>The '''install_ros.sh''' script will automatically run the '''OKros2 -h'''command after installing ros2. If you can see the following print, it means that the ros2 installation is complete.{| class="wikitable" style="width:800px;"

|-

| usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ... ros2 is an extensible command-line tool for ROS 2. optional arguments::-h, --help show this help message and exit Commands::action Various action related sub-commands:bag Various rosbag related sub-commands:component Various component related sub-commands:daemon Various daemon related sub-commands:doctor Check ROS setup and other potential issues:interface Show information about ROS interfaces:launch Run a launch file:lifecycle Various lifecycle related sub-commands:multicast Various multicast related sub-commands:node Various node related sub-commands:param Various param related sub-commands:pkg Various package related sub-commands:run Run a package specific executable:security Various security related sub-commands:service Various service related sub-commands:topic Various topic related sub-commands:wtf Use `wtf` as alias to `doctor` :Call `ros2 <command> -h` for more detailed usage.|}</li><li>Then you can use the '''~~TF Card Startup~~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.{| ~~'''OK'''~~class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~WIFI~~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: 'OKHello 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="width:800px;"

|-

| orangepi@orangepi:~$ '''~~Bluetooth~~source /opt/ros/humble/setup.bash'''| orangepi@orangepi:~$ '''OKros2 run rviz2 rviz2'''[[File:zero2w-img254.png]]|}</li><li>Reference documentation{| class="wikitable" style="width:800px;"

|-

| '''~~LED Light~~http://docs.ros.org/en/humble/index.html'''| [http://docs.ros.org/en/galactic/Tutorials.html '''OKhttp://docs.ros.org/en/humble/Installation/Ubuntu-Install-Debians.html''']|}</li></ol> == How to install kernel header files == {| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

| <big>'''~~40pin GPIO~~Debian11 system with Linux6.1 kernel will report GCC error when compiling kernel module. So if you want to compile the kernel module, please use Debian12 or Ubuntu22.04.'''</big>| } <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 '''OK/opt/'''{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~40pin I2C~~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{| ~~'''OK'''~~class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~40pin SPI~~sudo dpkg -i /opt/linux-headers*.deb'''| }</li><li>After installation, you can see the folder where the kernel header file is located under '''OK/usr/src'''.{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~40pin UART~~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 '''OK/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 '~~40pin PWM~~/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 '''OKhello.ko'''kernel module will be generated{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:/usr/src/hello$ '''~~Temperature Sensor~~ls *.ko'''hello.ko| }</li><li>Use the '''insmod''' command to insert the '''OKhello.ko'''kernel module into the kernel{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:/usr/src/hello$ '''~~Hardware watchdog~~sudo insmod hello.ko'''| }</li><li>Then use the '''OKdemsg'''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;"

|-

|}

</li><li>Use the '''rmmod''' command to uninstall the '''hello.ko''' kernel module{| class="wikitable" style="width:800px;"

|-

| ~~'''24pin expansion board function'''~~| orangepi@orangepi:/usr/src/hello$ '''~~OPi OS Arch~~sudo rmmod hello'''|-| orangepi@orangepi:/usr/src/hello$ '''~~100M network port'''~~dmesg | grep "Hello"'''~~OK'''~~|[ 2871.893988] Hello Orange Pi -~~| '''100M Ethernet port light'''| '''OK'''~~|-init~~| '''USB2~~[ 3173.~~0 HOST x 2'''| '''OK'''~~|-~~| '''Infrared reception'''| '''OK~~800892] '''|Hello Orange Pi -~~| '''Headphone audio playback'''| '''OK'''~~|-| exit'''On</~~off button'''| '''OK'''~~|-~~| '''LRADC''' '''Custom buttons x 2'''| '''OK'''~~|-~~| '''TV-OUT'''| '''NO'''~~p>

|}

</li></ol>

~~== Orange Pi OS Arch System User Guide Instructions ==~~

~~First~~ == Testing of ~~all, please note that the OPi OS Arch~~ some programming languages supported by Linux 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.==

~~When the OPi OS Arch~~ === Debian Bullseye system ~~settings through the user wizard (including creating a new user name and setting a password). The setup steps of the user wizard are as follows:~~===

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

<li>~~After burning~~ 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 ~~system, when you start it~~ source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</li><li>Write the ~~first time and enter the desktop, you will see the user wizard~~ '''hello_world.c''' program ~~shown~~ in ~~the figure below.~~C language~~<div~~ {| class="~~figure~~wikitable" style="width:800px;">|-| ~~[[File~~orangepi@orangepi:~~zero2w-img293~~~$ '''vim hello_world.c'''#include <stdio.~~png]]~~h>

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

~~<li>First you need to select the language you want~~

~~<div class="figure">~~

~~[[File~~int main(void){:~~zero2w-img294.png]]~~printf("Hello World!\n");

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

~~<li>After selecting the language, the user wizard will immediately switch to the corresponding language interface, as shown below in Chinese~~

~~<div class="figure">~~

~~[[File~~:~~zero2w~~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<ol style="list-style-type: lower-alpha;"><li>The specific version of Python is as follows{| class="wikitable" style="width:800px;" |-~~img295~~| orangepi@orangepi:~$ '''python3''''''Python 3.9.~~png]~~2''' (default, Feb 28 2021, 17:03:44)[GCC 10.2.1 20210110]on linuxType "help", "copyright", "credits" or "license" for more information.>>></~~div~~p>|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Use the Ctrl+D shortcut key to exit python's interactive mode.'''</big>|}</li><li>~~Then select~~ Write the ~~area~~'''hello_world.py''' program in Python language{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.py'''<~~div~~ p>print('Hello World!')|}</li><li>The result of running '''hello_world.py''' is as follows{| class="~~figure~~wikitable" style="width:800px;"|-| orangepi@orangepi:~$ '''python3 hello_world.py'''Hello World!|}~~[[File~~</li></ol></li><li>Debian Bullseye does not install Java compilation tools and operating environment by default.<ol style="list-style-type:~~zero2w~~lower-~~img296~~alpha;"><li>You can use the following command to install openjdk.~~png]]~~The latest version in Debian Bullseye is openjdk-17{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo apt install -y openjdk-17-jdk'''</~~div~~p>|}</li><li>~~Then select~~ After installation, you can check the ~~keyboard model~~Java version.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''java --version'''|}<~~div~~ /li><li>Write the Java version of '''hello_world.java'''{| class="~~figure~~wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.java'''public class hello_world{:public static void main(String[~~[File~~] args):{::~~zero2w-img297~~System.out.~~png]]~~println("Hello World!");:}}</~~div~~p>|}</li><li>Then ~~create a new username~~ compile and ~~set a password~~run '''hello_world.java'''~~<div~~ {| class="~~figure~~wikitable" style="width:800px;">|-| ~~[[File~~orangepi@orangepi:~~zero2w-img298~~~$ '''javac hello_world.~~png]]~~java'''orangepi@orangepi:~$ '''java hello_world'''Hello World!|}</li></ol></li></ol>

<~~/div></li><li><p~~span id="debian-bookworm-system">~~Then make sure there is no problem with the selection, and then click the install '''button'''~~~~<div class="figure"~~span>

~~[[File:zero2w-img299.png]]~~=== Debian Bookworm system ===

<ol style="list-style-type: decimal;"><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.<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 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 NO</~~div~~p>warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.|}</li><li>~~Then wait for~~ Write the ~~installation to complete~~'''hello_world.c''' program in C language~~<div~~ {| class="~~figure~~wikitable" style="width:800px;"|-| orangepi@orangepi:~$ '''vim hello_world.c'''#include <stdio.h>

~~[[File:zero2w-img300.png]]~~

<~~/div~~p>int main(void)</lip><lip>{~~After the installation is complete, you need to click the '''Finish''' button to restart the system.~~:printf("Hello World!\n");<~~div class="figure"~~/p>

~~[[File:zero2w-img301.png]]~~

:<~~/div~~p>return 0;</lip>~~<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.}~~<div class="figure">~~ ~~[[File:zero2w-img302.png]]~~|}</~~div~~li><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.~~~~</li></ol>~~ ~~== How to set DT overlays ==~~ ~~The multiplexing functions such as I2C/SPI/UART/PWM in the 40-pin development board are turned off by default in the kernel's dts,~~ Then compile and ~~the corresponding DT overlays need to be manually turned on before they can be used.~~ ~~The method to open DT overlays in OPi OS Arch system is as follows:~~ ~~# First open the~~ run '''~~/boot/extlinux/extlinux~~hello_world.~~conf~~c''' ~~configuration file~~ ~~[orangepi@orangepi-pc ~]$ '''sudo vim~~ </~~boot/extlinux/extlinux.conf'''~~p> ~~<ol start~~{| class="2wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">|-| <lip>~~Then open the corresponding configuration by adding~~ orangepi@orangepi:~$ '''~~FDTOVERLAYS''' '''/dtbs/allwinner/overlay/xxx.dtbo''' in '''/boot/extlinux/extlinux~~gcc -o hello_world hello_world.~~conf~~c'''</lip><~~/ol~~p> ~~'''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.'''~~ [orangepi@orangepi~~-pc~~ :~]$ '''~~sudo vim~~ ./~~boot/extlinux/extlinux.conf~~hello_world''' ~~LABEL Orange Pi~~ ~~KERNEL~~ Hello World!</~~Image~~p>|}~~FDT~~ </~~dtbs~~li></~~allwinner~~ol></~~sun50i-h616-orangepi-zero2w.dtb~~li> ~~'''FDTOVERLAYS~~ <li>Debian Bookworm has Python3 installed by default</~~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~~ specific version of ~~xxx.dtbo in the OPi OS Arch image~~ Python is as follows~~. Please note that not all dtbo under this path can be used.~~~~'''/boot/dtbs/allwinner/overlay/'''</li><li>The DT overlays configuration that can be used by the development board is as follows</li></ol>~~ {| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~Functions on the development board~~python3'''Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] on linuxType "help", "copyright", "credits" or "license" for more information.>>>|}{| ~~'''Corresponding DT overlays configuration'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

| <big>'''Use the Ctrl+D shortcut key to exit python'~~40pin - i2c0~~s interactive mode.'''</big>| }</li><li>Write the '''~~sun50i-h616-pi-i2c0~~hello_world.~~dtbo~~py'''program in Python language{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~40pin - i2c1~~vim hello_world.py'''print('Hello World!')| }</li><li>The result of running '''~~sun50i-h616-pi-i2c1~~hello_world.~~dtbo~~py'''is as follows{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~40pin - i2c2~~python3 hello_world.py'''Hello World!| ~~'''sun50i~~}</li></ol></li><li>Debian Bookworm does not install Java compilation tools and operating environment by default.<ol style="list-~~h616~~style-pitype: lower-~~i2c2~~alpha;"><li>You can use the following command to install openjdk.~~dtbo'''~~The latest version in Debian Bookworm is openjdk-17{| class="wikitable" style="width:800px;"

|-

| ~~'''40pin - uart2'''~~| orangepi@orangepi:~$ '''~~sun50i~~sudo apt install -~~h616~~y openjdk-pi17-~~uart2.dtbo~~jdk'''|-}</li>~~| '''40pin - uart3'''~~<li>After installation, you can check the Java version.{| ~~'''sun50i-h616-pi-uart3.dtbo'''~~class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~40pin~~ java - ~~uart4~~-version'''| }</li><li>Write the Java version of '''~~sun50i-h616-pi-uart4~~hello_world.~~dtbo~~java'''{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~40pin - uart5~~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 '''~~sun50i-h616-ph-uart5~~hello_world.~~dtbo~~java'''{| class="wikitable" style="width:800px;"

|-

|}

</li></ol>

<~~ol start~~span id="~~5" style="list~~ubuntu-~~style~~focal-~~type: decimal;~~system"><li>If you need to open multiple configurations at the same time, just add the paths of multiple configurations directly after '''FDTOVERLAYS.''' For example, the configuration of opening i2c1 and uart5 at the same time is as follows</li></olspan>

~~[orangepi@orangepi-pc ~]$ '''sudo vim /boot/extlinux/extlinux.conf'''~~=== Ubuntu Focal system ===

~~LABEL Orange Pi~~<ol style="list-style-type: decimal;"><li>Ubuntu Focal is installed with the gcc compilation tool chain by default, which can directly compile C language programs in the Linux system of the development board.<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 (Ubuntu 9.4.0-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.|}</li><li>Write the '''hello_world.c''' program in C language{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''vim hello_world.c'''#include <stdio.h>

~~KERNEL /Image~~

~~FDT~~ int main(void)</~~dtbs~~p>{</~~allwinner~~p>:printf("Hello World!\n");</~~sun50i-h616-orangepi-zero2w.dtb~~p>

~~'''FDTOVERLAYS /dtbs/allwinner/overlay/sun50i-h616-pi-i2c1.dtbo /dtbs/allwinner/overlay/sun50i-h616-ph-uart5.dtbo'''~~

:<~~ol start="6" style="list-style-type: decimal~~p>return 0;"<~~li>After setting, you need to restart the system for the configuration to take effect.</li~~p>}</olp>|}~~[orangepi@orangepi-pc ~]$ '''sudo reboot'''~~ ~~~~</~~span~~li>~~== How to install software ==~~ 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. ~~[orangepi@orangepi-pc ~]$ '''sudo pacman -Syy vim'''~~ <~~span id="android-12-tv-system-usage-instructions"~~li><~~/span~~p> = Then compile and run '''~~Android 12 TV system usage instructions~~hello_world.c''' = ~~~~</~~span~~p>~~== Supported Android versions ==~~ {| class="wikitable" style="width:800px;"

|-

|}

</li></ol></li><li>Ubuntu Focal has Python3 installed by default<~~span id~~ol style="~~android~~list-12style-tvtype: lower-~~function-adaptation-status~~alpha;"><li>The specific version of Python3 is as follows</~~span~~p>~~== Android 12 TV function adaptation status ==~~ {| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~Motherboard functions~~python3'''Python 3.8.10 (default, Nov 14 2022, 12:59:47)[GCC 9.4.0] on linuxType "help", "copyright", "credits" or "license" for more information.>>>| ~~'''Android12 TV'''~~}{| class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

| <big>'''~~HDMI video~~Use the Ctrl+D shortcut key to exit python's interactive mode.'''</big>| }</li><li>Write the '''OKhello_world.py'''program in Python language{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''vim hello_world.py''~~HDMI Audio~~'print('Hello World!')| }</li><li>The result of running '''OKhello_world.py'''is as follows{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~Type-C USB2~~python3 hello_world.~~0 x 2~~py'''Hello World!| ~~'''OK'''~~}</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 can use the following command to install openjdk-17{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~TF card startup~~sudo apt install -y openjdk-17-jdk'''|}</li><li>After installation, you can check the Java version.{| ~~'''OK'''~~class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~WIFI~~java --version'''openjdk 17.0.2 2022-01-18OpenJDK Runtime Environment (build 17.0.2+8-Ubuntu-120.04)OpenJDK 64-Bit Server VM (build 17.0.2+8-Ubuntu-120.04, mixed mode, sharing)| }</li><li>Write the Java version of '''OKhello_world.java'''{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~Bluetooth~~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 '''OKhello_world.java'''{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~USB Camera~~javac hello_world.java'''| orangepi@orangepi:~$ '''OKjava hello_world'''Hello World!|}</li></ol></li></ol> === Ubuntu Jammy system === <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 follows{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''gcc --version'''gcc (Ubuntu 11.3.0-1ubuntu1~22.04.1) '''~~LED Light~~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 '''OKhello_world.c'''program in C language{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~40pin GPIO~~vim hello_world.c'''#include <stdio.h> int main(void){:printf("Hello World!\n"); :return 0;}| }</li><li>Then compile and run '''OKhello_world.c'''{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~40pin I2C~~gcc -o hello_world hello_world.c'''| orangepi@orangepi:~$ '''OK./hello_world'''|-Hello World!| ~~'''40pin SPI1'''~~}~~| '''OK'''~~</li></ol>|-</li>~~| '''40pin UART'''~~<li>Ubuntu Jammy has Python3 installed by default~~| '''OK'''~~|<ol style="list-style-type: lower-alpha;">~~| '''40pin PWM'''~~<li>The specific version of Python3 is as follows{| ~~'''OK'''~~class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~Temperature Sensor~~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.>>>|}{| ~~'''OK'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

| <big>'''~~Hardware watchdog~~Use the Ctrl+D shortcut key to exit python's interactive mode.'''</big>| }</li><li>Write the '''OKhello_world.py'''program in Python language{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''vim hello_world.py''~~Mali GPU~~'print('Hello World!')| }</li><li>The result of running '''OKhello_world.py'''is as follows{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~Video codec~~python3 hello_world.py'''~~| '''OK'''~~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-18{| class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~24pin Expansion board function~~sudo apt install -y openjdk-18-jdk'''|}</li><li>After installation, you can check the Java version.{| ~~'''Android12 TV'''~~class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~100M network port~~java --version'''openjdk 18.0.2-ea 2022-07-19~~| '''OK'''~~OpenJDK Runtime Environment (build 18.0.2-ea+9-Ubuntu-222.04)|OpenJDK 64-Bit Server VM (build 18.0.2-ea+9-Ubuntu-222.04, mixed mode, sharing)| }</li><li>Write the Java version of '''~~100M Ethernet port light~~hello_world.java'''{| ~~'''OK'''~~class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~USB2~~vim hello_world.~~0 HOST x 2~~java'''~~| '''OK'''~~public class hello_world|-{~~| '''Infrared reception'''~~:public static void main(String[] args)~~| '''OK'''~~|-~~| '''Headphone audio playback'''| '''OK'''~~|-~~| '''On~~:{</~~off button'''~~p>~~| '''OK'''~~|-~~| '''LRADC''' '''Custom buttons x 2'''| '''OK, The default setting is the volume up and down keys~~::System.out.~~'''~~println("Hello World!");|-:}~~| '''TV-OUT'''| '''OK'''~~}

|}

</li><~~span id="onboard-led-light-display-instructions"~~li>Then compile and run '''hello_world.java'''</~~span~~p>~~== Onboard LED light display instructions ==~~ {| class="wikitable" style="width:800px;"

|-

|| orangepi@orangepi:~$ '''~~green light~~javac hello_world.java'''| orangepi@orangepi:~$ '''~~red light~~java hello_world'''|-~~| '''u-boot startup phase'''| '''Off'''| '''on'''~~|-~~| '''Kernel boot to enter the system'''| '''on'''| '''on'''~~Hello World!

|}

</li></ol>

~~== How to return to the previous interface in Android ==~~

~~We generally use the mouse and keyboard~~ == Method of uploading files 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-clicking the mouse, and the keyboard cannot return.~~Linux system ==

~~If you have purchased the infrared remote control (other remote controls do not work) and a 24pin expansion board that come with~~ === Method to upload files 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:~~Linux system in Ubuntu PC ===

~~[[File:zero2w~~==== How to upload files using scp command ====

<~~span id~~ol style="~~how~~list-style-type: decimal;"><li>Use the scp command toupload files to the Linux system of the development board in Ubuntu PC. The specific command is as follows<ol style="list-~~use~~style-type: lower-~~adb~~alpha;"><li>'''file_path: '''Needs to be replaced with the path of the file to be uploaded</li><li>'''orangepi: '''This is the user name of the development board's Linux system. It can also be replaced with something else, such as root.</li><li>'''192.168.xx.xx:''' This is the IP address of the development board. Please modify it according to the actual situation.</~~span~~li><li>'''/home/orangepi:''' The path in the development board Linux system can also be modified to other paths.{| class="wikitable" style= ~~How~~ "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 ~~ADB~~ the following command to view the man manual</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''man scp'''|}</ol>

~~~~=== ~~Use network connection adb debugging~~ How to upload files using filezilla ====

<ol style="list-style-type: decimal;"><li>First install filezilla in Ubuntu PC{| class="wikitable" style="width:800px;" |-| test@test:~$ '''~~Using network adb does not require a USB Typc C~~ sudo apt install -y filezilla'''|}</li><li>Then use the following command to open filezilla{| class="wikitable" style="width:800px;" |-| test@test:~$ '''filezilla'''|}</li><li>The interface ~~data cable to connect the computer and the development board~~after opening filezilla is as shown below. ~~Instead~~At this time, ~~it communicates through~~ the ~~network, so first make sure that~~ remote site on the ~~development board's wired or wireless network~~ right is ~~connected, and then obtain the IP address of the development board. Next To be used~~empty.~~'''~~<div class="figure">

~~# Make sure the '''service~~[[File:zero2w-img255.~~adb.tcp.port''' of the Android system is set to 5555 port number~~png]]

~~apollo-p2:~~</ ~~# '''getprop | grep "adb.tcp"'''~~div></li><li>The method of connecting the development board is as shown in the figure below</li>

~~[service.adb.tcp.port]: [5555]~~<div class="figure">

~~<ol start="2" style="list~~[[File:zero2w-~~style-type: decimal;"><li>If '''service.adb.tcp~~img256.~~port''' is not set, you can use the following command in the serial port to set the port number of the network adb</li></ol>~~png]]

~~apollo~~</div></ol><ol start="5" style="list-p2style-type:~~/ #~~ decimal;"><li>Then choose to '''save the password''' and click '''~~setprop service.adb.tcp.port 5555~~OK''' ~~apollo~~[[File:zero2w-~~p2:~~img257.png]]</ # li><li>Then select '''Always trust this host''~~stop adbd~~'and click '''OK'''</li>

~~apollo-p2:/ # '''start adbd'''~~<div class="figure">

~~<ol start="3" style="list~~[[File:zero2w-~~style-type: decimal;"><li>Install adb tool on Ubuntu PC</li></ol>~~img258.png]]

~~test@test~~</div></ol><ol start="7" style="list-style-type:~~~$ '''sudo apt-get update''~~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>

~~test@test:~$ '''sudo apt-get install -y adb'''~~<div class="figure">

~~<ol start="4" style="list~~[[File:zero2w-~~style-type: decimal;"><li>Then connect network adb on Ubuntu PC</li></ol>~~img259.png]]

~~test@test~~</div></ol><ol start="8" style="list-style-type:~~~$ '''adb connect 192.168.1.xxx:5555''' '''(Need~~ decimal;"><li>Then select the path to be ~~modified~~ uploaded to the ~~IP address~~ 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~~)'''~~.</li>

* daemon not running; starting now at tcp:5037<div class="figure">

* daemon started successfully[[File:zero2w-img260.png]]

~~connected~~ </div></ol><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 ~~192.168~~view the uploaded file.1</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.~~xxx:5555~~</li></ol>

~~test@test:~$ '''adb devices'''~~

~~List of devices attached~~=== Method to upload files from Windows PC to development board Linux system ===

~~192.168.~~==== How to upload files using filezilla ====

~~<ol start="5" style="list-style-type: decimal;"><li>Then you can log in to~~ # First download the ~~android system through adb shell on Ubuntu PC</li></ol>~~installation file of the Windows version of the filezilla software. The download link is as follows

~~test@test~~:~$ :{| class="wikitable" style="width:800px;" |-| [https://filezilla-project.org/download.php?type=client '''~~adb shell~~https://filezilla-project.org/download.php?type=client''']|}

~~apollo~~::[[File:zero2w-~~p2:/ #~~img261.png]]

<~~span id~~div class="~~use-data-cable-to-connect-adb-debugging~~figure">~~=== Use data cable to connect adb debugging ===~~

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

</div>

<li>~~Install adb tool on Ubuntu PC~~The downloaded installation package is as shown below, then double-click to install it directly</lip>{| class="wikitable" style="width:800px;" |-| '''FileZilla_Server_1.5.1_win64-setup.exe'''</olp>|}During the installation process, please select '''Decline''' on the following installation interface, and then select '''Next>'''

~~test@test:~$ '''sudo apt-get update'''~~<div class="figure">

~~test@test~~[[File:~~~$ '''sudo apt~~zero2w-~~get install -y adb'''~~img263.png]]

</div>

</li></ol>

<li>~~Check whether~~ The interface after opening filezilla is as shown below. At this time, the remote site on the ~~ADB device~~ right is ~~recognized~~empty.</li~~></ol~~>

~~test@test:~$ '''adb devices'''~~<div class="figure">

~~List of devices attached~~ ~~4c00146473c28651dd0 device~~[[File:zero2w-img264.png]]

</div></ol>

<li>~~Then you can log~~ The method of connecting the development board is as shown in to the ~~android system through adb shell on Ubuntu PC~~figure below:</li~~></ol~~>

~~test@test:~$ '''adb shell'''~~<div class="figure">

~~apollo~~[[File:zero2w-~~p2:/ $~~img256.png]]

<~~span id~~/div></ol><ol start="~~view-how~~5" style="list-tostyle-~~set-hdmi-display-resolution~~type: decimal;"><li>Then choose to '''save the password''' and click '''OK'''</~~span~~li>~~== View how to set HDMI display resolution ==~~

<~~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 ===~~img265.png]]

<~~ol style="list-style-type: decimal;"><li~~/div>~~First you need to prepare the following accessories~~</pol><ol start="6" style="list-style-type: ~~lower-alpha~~decimal;"><li>~~HDMI to VGA converter~~Then select '''Always trust this host''' and click '''OK'''</li~~></ol></li></ol~~>

~~[[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>~~img266.png]]

~~[[File:zero2w~~</div></ol><ol start="7" style="list-style-~~img145.png]] [[File~~type:~~zero2w-img146~~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.~~png]]~~</li>

<~~ol start~~div class="3figure" ~~style="list-style-type: lower-alpha;"><li>A monitor or TV that supports VGA interface</li></ol~~>

~~~~<ol start="2" style="list-style-type: decimal;"><li>HDMI to VGA display test is as follows</li></ol>img267.png]]

~~[[File~~</div></ol><ol start="8" style="list-style-type:~~zero2w~~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-~~img313~~click the mouse, and then click the upload option to start uploading the file to the development board.~~png]]~~</li>

'''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.'''<div class="figure">

~~== WI-FI connection method ==~~img268.png]]

~~# Choose first '''Settings''~~</div></ol><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.</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.</li></ol>

~~[[File:zero2w~~

~~<ol start~~=~~"2" style~~=~~"list-style-type: decimal;"><li>Then select '''Network & Internet'''</li></ol>~~Instructions for using the logo on and off the machine ==

~~[[File~~<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.</li><li>Set the '''bootlogo''' variable to '''false''' in '''/boot/orangepiEnv.txt''' to turn off the switch logo.{| class="wikitable" style="width:~~zero2w~~800px;" |-~~img314~~| orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.~~png]]~~txt'''verbosity=1'''bootlogo=false'''|}</li><~~ol start~~li>Set the '''bootlogo''' variable to '''true''' in '''/boot/orangepiEnv.txt''' to enable the power on/off logo.{| class="3wikitable" style="~~list~~width:800px;" |-| orangepi@orangepi:~$ '''sudo vim /boot/orangepiEnv.txt'''verbosity=1'''bootlogo=true'''|}</li><li>The location of the boot logo picture in the Linux system is{| class="wikitable" style~~-type~~="width: ~~decimal~~800px;"|-| '''/usr/share/plymouth/themes/orangepi/watermark.png'''|}</li><li>~~Then turn on WI~~After replacing the boot logo image, you need to run the following command to take effect{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo update-initramfs -FIu'''|}</li></ol>

~~[[File:zero2w~~

~~<ol start~~=~~"4" style~~=~~"list-style-type: decimal;"><li>After turning~~ How to turn on ~~WI-FI, you can see~~ the ~~searched signals under '''Available networks'''~~power button in Linux5.~~</li></ol>~~4 ==

~~[[File~~There is no power on/off button on the main board of the development board. We can expand it through a 24pin expansion board. The location of the power on/off button on the expansion board is as follows:~~zero2w-img316.png]]~~

~~<ol start="5" style="list-style-type~~[[File: ~~decimal;"><li>After selecting the WI~~zero2w-~~FI you want to connect to, the password input interface shown below will pop up~~img269.~~</li></ol>~~png]]

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

<ol style="list-style-type: decimal;"><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 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-~~img317~~img85.png]]</li></ol>

<~~/div><ol start~~span id="~~6" style="list~~how-to-~~style~~shut-~~type: decimal;"><li>Then use the keyboard to enter the password corresponding to the WI~~down-~~FI,~~ and ~~then use~~ -restart-the ~~mouse to click the Enter button on the virtual keyboard to start connecting to the WI~~-~~FI.</li~~development-board"></olspan>

~~<div class~~=~~"figure">~~= How to shut down and restart the development board ==

<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.{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo poweroff'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that after turning off the development board, you need to unplug and replug the power supply before it can be turned on.'''</big>|}</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-~~img318~~img269.png]]{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''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 [[Orange Pi Zero 2W#How to turn on the power button in Linux5.4|the method of opening the power button in Linux5.4]].'''</big>|}</li><li>Use the '''reboot''' command to restart the Linux system in the development board{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo''' '''reboot'''|}</li></ol>

<~~/div><ol start~~span id="~~7" style="list~~linux-sdkorangepi-build-~~style~~usage-~~type: decimal;~~instructions">~~<li>The display after successful WI-FI connection is as shown below</li~~></olspan>

~~[[File:zero2w~~= '''Linux SDK——orangepi-~~img319.png]]~~build usage instructions''' =

== ~~How to use WI-FI hotspot~~ Compilation system requirements ==

The Linux SDK, '''orangepi-build''', only supports running on X64 computers with '''Ubuntu 22.04''' installed. Therefore, before downloading orangepi-build, please ~~make sure~~ first ensure that the ~~Ethernet port~~ Ubuntu version installed on your computer is ~~connected~~ Ubuntu 22.04. The command to check the ~~network cable and can access~~ Ubuntu version installed on the ~~Internet normally~~computer is as follows.~~# Then select~~ If the Release field does not display '''~~Settings~~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;" |-~~img306.png]]~~| test@test:~$ '''lsb_release -a'''

~~<ol start="3" style="list-style-type: decimal;"><li>Then select '''Network & Internet'''</li></ol>~~No LSB modules are available.

~~[[File~~Distributor ID:~~zero2w-img314.png]]~~Ubuntu

~~<ol start="4" style="list-style-type~~Description: ~~decimal;"><li>Then select '''WIFI hotspot'''</li></ol>~~Ubuntu 22.04 LTS

~~[[File~~Release:~~zero2w-img320~~'''22.~~png]]~~04'''

~~<ol start="5" style="list-style-type~~Codename: ~~decimal;"><li>Then open~~ '''~~Hotspot Enable~~jammy'''. 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~~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-~~img321~~build.~~png]]~~The installation image download address of Ubuntu 22.04 amd64 version is:

~~<ol start~~{| class="6wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>At this time, you can take out your mobile phone~~|-| [https://repo. ~~If everything is normal, you can find the WIFI hotspot with the same name ('''here AndroidAP_7132''') shown under the '''Hotspot name''' in the picture above in the WI~~huaweicloud.com/ubuntu-~~FI list searched by the mobile phone~~releases/21. ~~Then you can click AndroidAP_7132 to connect to the hotspot~~04/ubuntu-21. ~~The password can be seen under the~~ 04-desktop-amd64.iso '''~~Hotspot password''' in the picture above~~https://mirrors.tuna.tsinghua.edu.<cn/~~li><~~ubuntu-releases/~~ol>~~ ~~[[File:zero2w~~22.04/ubuntu-22.04-desktop-~~img322~~amd64.~~png]~~iso''']|}

~~<ol start="7" style="list-style-type: decimal;"><li>~~After ~~the connection is successful, it will be displayed as shown below (the interface will be different~~ installing Ubuntu 22.04 on ~~different mobile phones~~your computer or virtual machine, please first set the ~~specific interface is subject to the one displayed on your mobile phone)~~software source of Ubuntu 22. ~~At this time, you can open a web page on your mobile phone~~ 04 to ~~see if~~ Tsinghua source (or other domestic sources that you ~~can access the Internet. If the web page can be opened normally~~think is fast), otherwise it ~~means that~~ is easy to make errors due to network reasons when installing the ~~'''WI-FI Hotspot''' of the development board can be used normally~~software later.~~</li></ol>~~The steps to replace Tsinghua Source are as follows:

~~[[File~~<ol style="list-style-type:~~zero2w~~lower-~~img323~~alpha;"><li>For the method of replacing Tsinghua Source, please refer to the instructions on this page.~~png]]~~</li>

{| class="wikitable" style="width:800px;" |-| [https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/ '''https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/''']|}</ol><~~span id~~ol start="2" style="~~how~~list-tostyle-~~check~~type: lower-~~the-ip-address-of-the-ethernet-port~~alpha;"><li>Note that the Ubuntu version needs to be switched to 22.04.</~~span~~li>~~== How to check the IP address of the Ethernet port ==~~

~~# There is no wired network interface on the main board~~ [[File:zero2w-img271.png]]</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The contents of the ~~development board~~'''/etc/apt/sources. ~~We can expand the 100M Ethernet through a 24pin expansion board~~list''' file that need to be replaced are:</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo mv /etc/apt/sources.list cat /etc/apt/sources.list.bak'''

~~[[File~~test@test:~~zero2w-img107~~~$ '''sudo vim /etc/apt/sources.~~png]]~~list'''

~~<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~~The source code image is commented by default to improve apt update speed.~~png]]</li><li>Then select '''Network & Internet'''[[File:zero2w-img325.png]]</li><li>Then you~~ You can ~~see the IP address of the development board's wired network port at the location shown in the picture below.[[File:zero2w-img326~~uncomment it yourself if necessary.~~png]]</li></ol>~~

~~<~~deb https:/~~span>== Bluetooth connection method ==~~/mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse

~~# Choose first~~ '''~~Settings~~#'''deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse

~~[[File~~deb https:~~zero2w~~//mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-~~img306.png]]~~updates main restricted universe multiverse

~~<ol start="2" style="list-style-type: decimal;"><li>Then select~~ '''~~Bluetooth~~#'''<deb-src https://mirrors.tuna.tsinghua.edu.cn/~~li><~~ubuntu/~~ol>~~jammy-updates main restricted universe multiverse

~~[[File~~deb https:~~zero2w~~//mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-~~img327.png]]~~backports main restricted universe multiverse

~~<ol start="3" style="list-style-type: decimal;"><li>Then Open~~ '''~~Bluetooth Enable~~#'''<deb-src https://mirrors.tuna.tsinghua.edu.cn/~~li><~~ubuntu/~~ol>~~jammy-backports main restricted universe multiverse

~~[[File~~deb https:~~zero2w~~//mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-~~img328.png]]~~security main restricted universe multiverse

~~<ol start="4" style="list-style-type: decimal;"><li>Then click~~ '''~~Pair new device~~#'''~~to start scanning for surrounding Bluetooth devices<~~deb-src https://mirrors.tuna.tsinghua.edu.cn/~~li><~~ubuntu/~~ol>~~jammy-security main restricted universe multiverse

~~[[File:zero2w-img329.png]]~~

~~<ol start="5" style="list-style-type: decimal;"><li>The searched Bluetooth devices will be displayed under~~ '''~~Available devices~~#'''~~</li></ol>~~Pre-release software source, not recommended to be enabled

~~[[File~~'''#''' deb https:~~zero2w~~//mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-~~img330.png]]~~proposed main restricted universe multiverse

'''#''' deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse|}</ol><ol start="64" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then click on~~ After the ~~Bluetooth device~~ replacement, you ~~want to connect~~ need to update the package information and ensure that no errors are reported.</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''sudo apt-get update'''|}</ol><ol start ~~pairing. When~~ ="5" style="list-style-type: lower-alpha;"><li>'''In addition, since the source code of the ~~following interface pops up~~kernel and Uboot are stored on GitHub, ~~please use~~ it is very important to ensure that the ~~mouse to select~~ computer can download the code from GitHub normally when compiling the image.'''~~Pair'''option~~</li></ol>

~~[[File:zero2w~~ == Obtain the source code of linux sdk ==

<~~ol start~~span id="~~7" style="list~~download-orangepi-build-~~style~~from-~~type: decimal;~~github"><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>=== Download orangepi-build from github ===

~~[[File:zero2w~~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-~~img332~~build.~~png]]~~Use the following command to download the orangepi-build code:

~~<ol start~~{| class="8wikitable" style="~~list-style-type~~width: ~~decimal~~800px;">~~<li>After pairing is completed, open~~ |-| test@test:~$ '''~~Paired devices~~sudo apt-get update''' ~~and you will see the paired Bluetooth devices.</li></ol>~~

~~[[File~~test@test:~~zero2w~~~$ '''sudo apt-~~img333.png]]~~get install -y git'''

~~<ol start~~test@test:~$ '''git clone https://github.com/orangepi-xunlong/orangepi-build.git -b next'''|}{| class="9wikitable" style="~~list~~background-~~style-type~~color:#ffffdc;width: ~~decimal~~800px;">|-| <libig>~~At this time~~'''Note that when using the H618 Soc development board, you ~~can use~~ need to download the ~~Bluetooth~~ source code of ~~your mobile phone to send a picture to~~ the ~~development board~~next branch of orangepi-build. ~~After sending, you can see~~ The above git clone command needs to specify the ~~following confirmation interface in the Android system~~ branch of the ~~development board, and then click '~~orangepi-build source code as next.''~~Accept~~'~~'' to start receiving the pictures sent by the mobile phone.</li>~~</olbig>

~~[[File:zero2w-img334.png]]~~<div class="figure">

~~<ol start="10" style="list~~[[File:zero2w-~~style-type: decimal;"><li>Pictures received by the Bluetooth system of the development board Android system can be viewed in '''Received files'''~~img272.~~</li></ol>~~png|center|800px]]

~~[[File~~</div>|}{| class="wikitable" style="background-color:#ffffdc;width:~~zero2w~~800px;" |-| <big>'''When downloading the orangepi-~~img335~~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.~~png]]~~'''</big>|}

~~== How to set USB0 to HOST mode ==~~boot and linux kernel versions currently used by the H618 series development boards are as follows:

~~As shown in the figure below, there are two Type~~{| class="wikitable" style="width:800px;text-~~C interfaces on the motherboard of the development board~~align: ~~USB0 and USB1~~center;"|-| '''branch'''| '''u-boot Version'''| '''linux Kernel version'''|-| '''current'''| '''u-boot v2018. ~~Both of these interfaces can be used to power the development board, and they can also be used as USB2~~05'''| '''linux5.~~0 HOST interfaces~~4'''|-| '''next'''| '''u-boot v2021. ~~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~~07'''| '''linux6.1'''|}

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~zero2w~~800px;" |-| <big>'''The branch mentioned here is not the same thing as the branch of orangepi-~~img160~~build source code, please don't get confused. This branch is mainly used to distinguish different kernel source code versions.~~png]]~~'''

~~USB0 of~~ '''We define the ~~Android12 TV system released~~ linux5.4 bsp kernel currently provided by ~~Orange Pi~~ Allwinner as the current branch. The latest linux6.1 LTS kernel 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 defined as the next branch.'''</big>|}

~~If you want to use USB0 to connect USB devices~~After downloading, ~~you need to set USB0 to HOST mode. The method is as follows~~the following files and folders will be included:

<li>~~Run the following command to set USB0 to HOST mode~~'''build.sh''':Compile startup script</li><li>'''external''': Contains configuration files needed to compile the image, specific scripts, and source code of some programs, etc.</olp></li> ~~apollo-p2~~<li>'''LICENSE''':GPL 2 license file</ # li><li>'''README.md'''~~cat~~ : orangepi-build documentation</~~sys~~p></~~devices~~li><li>'''scripts''': Common script for compiling linux images</~~platform~~p></~~soc@3000000~~li></~~soc~~ol>{| class="wikitable" style="width:800px;" |-| test@~~3000000\~~test:~~usbc0@0~~~/~~usb_host~~orangepi-build$ '''ls'''

~~host_chose finished!~~'''build.sh      external      LICENSE      README.md      scripts'''|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''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 (their addresses will be detailed below). Orangepi-build will specify the addresses of u-boot, Linux kernel and cross-compilation tool chain in the script and configuration file. When running orangepi-build, when it finds that these things are not available locally, it will automatically download them from the corresponding places.'''</big>|}

~~apollo~~</ #span>

~~<ol start~~=~~"2" style~~=~~"list~~= Download the cross-~~style-type: lower-alpha;"><li>Run the following command to switch back to Device mode</li></ol>~~compilation tool chain ===

~~apollo~~When orangepi-~~p2:/ #~~ build is run for the first time, it will automatically download the cross-compilation '''toolchain'''and put it in the ''~~cat /sys/devices/platform/soc@3000000/soc@3000000\:usbc0@0/usb_device~~'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.

~~device_chose finished!~~<div class="figure">

~~apollo~~[[File:zero2w-~~p2:/ #~~img273.png]]

<~~ol start="3" style="list-style-type: lower-alpha;"~~/div>~~<li>~~The ~~command to view~~ mirror URL of the cross-compilation tool chain in China is the ~~current mode~~ open source software mirror site of ~~USB0 is</li></ol>~~Tsinghua University:

~~apollo~~{| class="wikitable" style="width:800px;" |-p2| [https:/ # /mirrors.tuna.tsinghua.edu.cn/armbian-releases/_toolchain/ '''~~cat~~ https:/~~sys~~/~~devices~~mirrors.tuna.tsinghua.edu.cn/~~platform~~armbian-releases/~~soc@3000000/soc@3000000\:usbc0@0~~_toolchain/~~otg_role~~''']|}

~~usb_host~~After toolchains is downloaded, it will contain multiple versions of cross-compilation '''toolchain''':

~~<~~build$ '''ls toolchains/~~span>== How to use USB camera ==~~'''

~~# First insert the USB (UVC protocol) camera into the USB interface of the development board# If the USB camera is recognized normally, the corresponding video device node will be generated under /dev~~gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu

~~console:/ # '''ls /dev/video0'''~~gcc-linaro-4.9.4-2017.01-x86_64_aarch64-linux-gnu

~~/dev/video0~~gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabi

~~<ol start="3" style="list~~gcc-~~style~~arm-~~type: decimal;"><li>Then make sure that the adb connection between the Ubuntu PC and the development board is normal~~11. ~~For how to use adb, please refer to the instructions in the section "'''How to use ADB'''"~~2-2022.~~</li><li>Download the USB camera test APP from the '''official tool''' on the development board information download page</li></ol>~~02-x86_64-arm-none-linux-gnueabihf

~~<div class="figure">~~gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabi

~~[[File:zero2w~~gcc-~~img336~~linaro-aarch64-none-elf-4.8-2013.~~png]]~~11_linux

~~</div><div class="figure">~~gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu

~~[[File:zero2w~~gcc-~~img337~~linaro-5.5.0-2017.~~png]]~~10-x86_64_arm-linux-gnueabihf

~~</div><ol start="5" style="list~~gcc-~~style~~linaro-~~type: decimal;"><li>Then use the adb command to install the USB camera test APP into the Android system~~arm-linux-gnueabihf-4. ~~Of course, you can also use a USB disk copy to install it~~8-2014.~~</li></ol>~~04_linux

~~test@test:~$ '''adb install usbcamera~~gcc-arm-9.~~apk'''~~2-2019.12-x86_64-arm-none-linux-gnueabihf

~~<ol start="6" style="list~~gcc-~~style~~linaro-~~type: decimal;"><li>After installation, you can see the startup icon of the USB camera on the Android desktop~~7.~~</li></ol>~~4.1-2019.02-x86_64_aarch64-linux-gnu

~~[[File:zero2w~~gcc-~~img338~~linaro-arm-none-eabi-4.8-2014.~~png]]~~04_linux|}

~~<ol start="7" style="list~~The cross-~~style-type: decimal;"><li>Then double-click~~ compilation tool chain used to ~~open~~ compile the ~~USB camera APP and you can see the output video of the USB camera.</li></ol>~~H618 Linux kernel source code is:

<~~span id~~ol style="~~android~~list-~~system~~style-~~root~~type: lower-~~description~~alpha;"><li>linux5.4</~~span~~li>{| class="wikitable" style= ~~Android system ROOT description~~ "width:800px;" |-| '''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>linux6.1</li>{| class="wikitable" style="width:800px;" |-| '''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''|}</ol>The cross-compilation tool chain used to compile the H618 u-boot source code is:

<ol style="list-style-type: lower-alpha;"><li>v2018.05</li>{| class="wikitable" style="width:800px;" |-| '''gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabi'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>v2021.07</li>{| class="wikitable" style="width:800px;" |-| '''~~The Android system released by Orange Pi has been ROOT and can be tested using the following method~~gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''|}</ol>

~~# Download from the '''official tool''' on the development board data download page '''rootcheck.apk'''~~ ~~<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 "'''How to use ADB'''".</li>~~<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></ol>~~ ~~test@test:~$ '''adb install rootcheck.apk'''~~ ~~<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></ol>~~ ~~[[File:zero2w-img340.png]]~~ ~~<ol start="5" style="list-style-type: decimal;"><li>The display interface after opening the '''ROOT test tool''' for the first time is as shown below</li></ol>~~ ~~[[File:zero2w-img341.png]]~~ ~~<ol start~~=~~"6" style~~=~~"list-style~~orangepi-~~type: decimal;">~~<li>Then you can click '''CHECK NOW''' to start checking the ROOT status of the Android system. After the check is completed, the display is as follows. You can see that the Android system has obtained ROOT permissions.</li></ol> ~~[[File:zero2w-img342.png]]~~ ~~~~=build complete directory structure description = ~~How to use MiracastReceiver to cast the mobile phone screen to the development board~~ ==

<li>~~First~~After downloading, ~~please make sure~~ 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.<ol style="list-style-type: lower-alpha;"><li>The git warehouse where the linux kernel source code is stored is as follows. Please note that ~~both~~ the ~~development board and~~ branch of the ~~mobile phone are connected~~ linux-orangepi warehouse is switched to <ol style="list-style-type: none;"><li>a) Linux5.4</li>{| class="wikitable" style="width:800px;" |-| https://github.com/orangepi-xunlong/linux-orangepi/tree/'''orange-pi-5.4-sun50iw9'''|}</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/'''orange-pi-6.1-sun50iw9'''|}</ol></li></ol><ol start="2" style="list-style-type: lower-alpha;"><li>The git warehouse where the ~~same WIFI hotspot~~u-boot source code is stored is as follows. ~~For~~ Please note that the ~~method~~ branch of ~~connecting~~ the ~~development board to WIFI, please refer~~ u-boot-orangepi warehouse is switched to <ol style="list-style-type: lower-alpha;"><li>a) v2018.05</li>{| class="wikitable" style="width:800px;" |-| https://github.com/orangepi-xunlong/u-boot-orangepi/tree/'''v2018.05-h618'''|}</ol><ol start="2" style="list-style-type: lower-alpha;"><li>b) v2021.07</li>{| class="wikitable" style="width:800px;" |-| https://github.com/orangepi-xunlong/u-boot-orangepi/tree/'''v2021.07-sunxi'''|}</ol></li></ol></li></ol><ol start="2" style="list-style-type: decimal;"><li>When orangepi-build is run for the ~~instructions in~~ first time, it will download the WIcross-~~FI connection method~~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>~~Then open~~ '''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>'''~~MiracastReceiver~~kernel'''~~application in~~ : Store the ~~Android system~~ source code of the ~~development board~~linux kernel</li><li>'''LICENSE''': GPL 2 license file</li><li>'''README.md''': orangepi-build documentation</li><li>~~[[File~~'''output''':~~zero2w~~Store compiled u-~~img343.png]]~~boot, 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>~~The interface after~~ '''~~MiracastReceiver~~u-boot''' ~~is opened is as follows~~: Store the source code of u-boot</li><~~div~~ li>'''userpatches''': Store the configuration files needed to compile the script</li>{| class="~~figure~~wikitable" style="width:800px;"|-| test@test:~/orangepi-build$ '''ls''' '''build.sh      external      kernel      LICENSE      output      README.md      scripts      toolchains      u-boot      userpatches'''|}</ol></li></ol>

~~[[File:zero2w~~

~~</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~~== Compile u-~~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>~~boot ==

~~== Method of turning on and off the machine through buttons or infrared remote control ==~~build.sh script, remember to add sudo permissions

~~We can turn off or turn on the Android system of the development board through the power on~~{| class="wikitable" style="width:800px;" |-| test@test:~/~~off button or infrared remote control~~orangepi-build$ '''sudo . ~~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~~build.sh'''|}

~~[[File~~<ol start="2" style="list-style-type:~~zero2w~~decimal;"><li>Select '''U-~~img107.png]]~~boot package''' and press Enter</li>

~~The location of the power button on the 24pin expansion board is as shown in the~~ <div class="figure ~~below:~~">

[[File:zero2w-~~img269.png]]~~ ~~The location of the infrared remote control power button is as follows:~~ ~~[[File:zero2w-img349.png]]~~ When shutting down, we need to press and hold the power button or the power button on the infrared remote control, and then the Android system will pop up the confirmation dialog box shown in the figure below, and then select '''OK''' to shut down the Android system. ~~[[File:zero2w-img350.png]]~~ ~~After shutting down, press and hold the power button or the power button on the infrared remote control again to turn it on.~~ ~~== 40pin interface GPIO, UART, SPI test ==~~ ~~'''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 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></ol>~~ ~~[[File:zero2w-img352~~img274.png]]

</div></ol>

<li>~~The GPIO test interface is as shown in~~ Then select the ~~figure below. The two rows~~ model 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.development board</li>~~</ol>~~ ~~[[File:zero2w-img353.png]]~~

[[File:zero2w-img275.png]]

</ol>

<li>Then ~~click~~ select the branch type of u-boot<ol style="list-style-type: lower-alpha;"><li>The current branch will compile the ~~'''GPIO READALL''' button, and~~ u-boot v2018.05 version code that needs to be used by the ~~output information is as shown below:~~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> <~~div class="figure"~~p> [[File:zero2w-~~img354~~img276.png]]</li></ol></li><li>If you select the next branch, you will also be prompted to select the memory size, and you do not need to select the current branch.</~~div~~p><ol ~~start="5"~~ style="list-style-type: ~~decimal~~lower-alpha;"><li>~~There are a total of 28 GPIO ports available in~~ If 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~~ purchased has a ~~multimeter to measure the value of the voltage~~ memory size of ~~the pin. If it is '''3~~1.~~3v'''~~5GB, ~~it means~~ please select the ~~setting High level success~~first option.</li><li>If the development board you purchased has 1GB or 2GB or 4GB memory size, please choose the second option.</olp> [[File:zero2w-~~img355~~img277.png]]</li></ol></li></ol>

<li>~~Then click the '''GPIO READALL''' button and you can see that the current pin 12 mode is '''OUT''' and the pin level is high level.~~<~~/li~~p>~~</ol>~~ ~~[[File:zero2w-img356.png]]~~ ~~<ol start="7" style="list-style-type: decimal;"><li>Click the '''CheckBox''' button in the picture below again to uncheck~~ Then it~~, and pin 12~~ will ~~be set~~ start to ~~low level~~compile u-boot. ~~After setting, you can use a multimeter to measure the voltage value~~ Some of the ~~pin. If it is '''0v''', it means~~ information prompted when compiling the ~~low level setting~~ next branch is ~~successful.</li>~~as follows:</olp> ~~[[File:zero2w-img357.png]]~~ <ol ~~start="8"~~ style="list-style-type: ~~decimal~~lower-alpha;"><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.~~Version of u-boot source code</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" style="width:800px;"

|-

| ~~'''GPIO序号'''~~| [ o.k. ] Compiling u-boot [ '''~~GPIO~~v2021.07''']| ~~'''功能'''~~}~~| '''引脚'''~~|~~| '''引脚'''~~</ol>~~| '''功能'''~~<ol start="2" style="list-style-type: lower-alpha;">~~| '''GPIO'''~~<li>Version of the cross-compilation tool chain</li>{| ~~'''GPIO序号'''~~class="wikitable" style="width:800px;"

|-

~~| style="text-align: left;"~~|~~| style="text-align: left;"|| '''3~~[ o.k.3V] Compiler version [ '''~~| '''1~~aarch64-linux-gnu-gcc 11''']|}~~| '''2'''~~</ol>~~| '''5V'''~~| <ol start="3" style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"|><li>Path to the compiled u-boot deb package</li>{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|

|-

| ~~'''264'''~~| [ o.k. ] Target directory [ '''~~PI8'''| '''TWI1~~orangepi-build/output/debs/u-~~SDA~~boot''']| ~~'''3'''~~}|</ol>~~| '''~~<ol start="4~~'''| '''5V'''~~| " style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"|><li>The package name of the compiled u-boot deb package</li>{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|

|-

| ~~'''263'''~~| [ o.k. ] File name [ '''~~PI7'''| '''TWI1~~linux-u-boot-next-~~SCL~~orangepizero2w_x.x.x_arm64.deb''']| ~~'''5'''~~}|</ol>~~| '''6'''| '''GND'''~~| <ol start="5" style="~~text~~list-~~align~~style-type: ~~left~~lower-alpha;"|><li>Compilation time</li>{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|

|-

| ~~'''269'''~~| [ o.k. ] Runtime [ '''~~PI13~~1 min''']| ~~'''PWM3'''~~}~~| '''7'''~~|~~| '''8'''~~</ol>~~| '''UART0_TX'''~~<ol start="6" style="list-style-type: lower-alpha;">~~| '''PH0'''~~<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>{| ~~'''224'''~~class="wikitable" style="width:800px;"

|-

| [ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepizero2w BRANCH=next BUILD_OPT=u-boot''' ]|}</ol></li></ol><ol start="7" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|><li>View the compiled u-boot deb package</li>{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|~~| '''GND'''| '''9'''~~|~~| '''10'''| '''UART0_RX'''| '''PH1'''| '''225'''~~

|-

| ~~'''226'''~~| test@test:~/orangepi-build$ '''~~PH2~~ls output/debs/u-boot/'''~~| '''UART5_TX'''~~| '''11linux-u-boot-next-orangepizero2w_x.x.x_arm64.deb'''|}~~| '''12'''~~</ol>| <ol start="8" style="~~text~~list-style-~~align~~type: ~~left~~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. ('''~~PI1~~You 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'''~~257~~userpatches/config-default.conf'''to "yes" {| class="wikitable" style="width:800px;"

|-

| test@test:~/orangepi-build$ '''~~227~~vim userpatches/config-default.conf'''~~| '''PH3'''~~| ...... IGNORE_UPDATES="'''~~UART5_RX~~yes'''"~~| '''13'''~~|......| ~~'''14'''~~}~~| '''GND'''~~</ol>| <ol start="9" style="~~text~~list-style-~~align~~type: ~~left~~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="~~text~~list-~~align~~style-type: ~~left~~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$ '''~~261~~cd output/debs/u-boot'''| test@test:~/orangepi_build/output/debs/u-boot$ '''~~PI5~~scp \'''~~| '''UART2_TX'''~~| '''15linux-u-boot-next-orangepizero2w_x.x.x_arm64.deb [mailto:root@192.168.1.xxx:/root root@192.168.1.xxx:/root]'''|}~~| '''16'''~~</ol>~~| '''PWM4'''~~<ol start="2" style="list-style-type: lower-alpha;">~~| '''PI14'''~~<li>Install the new u-boot deb package just uploaded</li>{| ~~'''270'''~~class="wikitable" style="width:800px;"

|-

~~| style="text-align: left;"~~|~~| style="text-align~~orangepi@orangepi: ~~left;"|~~| ~$ '''~~3.3V~~sudo dpkg -i'''| '''17linux-u-boot-next-orangepizero2w_x.x.x_arm64.deb'''|}~~| '''18'''~~</ol>| <ol start="3" style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"|>~~| '''PH4'''~~<li>Then run the nand-sata-install script</li>{| ~~'''228'''~~class="wikitable" style="width:800px;"

|-

| orangepi@orangepi:~$ '''~~231~~sudo nand-sata-install'''| }</ol><ol start="4" style="list-style-type: lower-alpha;"><li>Then select '''~~PH7~~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>~~| '''SPI1_MOSI'''| '''19'''~~== Compile the linux kernel ==|| # Run the '''20build.sh'''script, remember to add sudo permissions~~| '''GND'''~~::{| ~~style~~class="~~text-align: left;~~wikitable"|| style="~~text-align~~width: ~~left~~800px;"|

|-

| test@test:~/orangepi-build$ '''~~232~~sudo ./build.sh'''| } <ol start="2" style="list-style-type: decimal;"><li>Select '''~~PH8~~Kernel package'''and press Enter</li> <div class="figure"> [[File:zero2w-img281.png]] </div></ol><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> [[File:zero2w-img282.png]]</ol>| <ol start="4" style="list-style-type: decimal;"><li>Then select the model of the development board</li> [[File:zero2w-img275.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then select the branch type of the kernel source code</li> ::a. The current branch will compile the linux5.4 kernel source code ::b. The next branch will compile the linux6.1 kernel source code ::[[File:zero2w-img276.png]]</ol><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 '''~~SPI1_MISO~~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>| [[File:zero2w-img283.png]] <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 '''21KERNEL_CONFIGURE=no'''to temporarily block the pop-up of the kernel configuration interface.</li>{|class="wikitable" style="width:800px;" | ~~'''22'''~~-| test@test:~/orangepi-build$ '''~~UART2_RX~~sudo ./build.sh KERNEL_CONFIGURE=no'''| }</ol><ol start="2" style="list-style-type: lower-alpha;"><li>b. You can also set '''~~PI6~~KERNEL_CONFIGURE=no'''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 Ubuntu PC terminal interface is too small, causing the make menuconfig interface to be unable to be displayed. Please increase the Ubuntu PC terminal to the maximum size, and then rerun the build.sh script.</li> [[File:zero2w-img284.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</li>{| ~~'''262'''~~class="wikitable" style="width:800px;"

|-

| ~~'''230'''~~| [ o.k. ] Compiling current kernel [ '''~~PH6~~6.1.31''']| ~~'''SPI1_CLK'''~~}~~| '''23'''~~|~~| '''24'''~~</ol>~~| '''SPI1_CS0'''~~<ol start="2" style="list-style-type: lower-alpha;">~~| '''PH5'''~~<li>The version of the cross-compilation tool chain used</li>{| ~~'''229'''~~class="wikitable" style="width:800px;"

|-

| [ o.k. ] Compiler version [ '''aarch64-linux-gnu-gcc 11''' ]|}</ol><ol start="3" style="~~text~~list-~~align~~style-type: ~~left~~lower-alpha;"|><li>The default configuration file used by the kernel and the path where it is stored are as follows</li>{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|~~| '''GND'''| '''25'''~~|~~| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''233'''~~

|-

| ~~'''266'''~~| [ o.k. ] Using kernel config file [ '''~~PI10'''| '''TWI2~~orangepi-build/external/config/kernel/linux-6.1-sun50iw9-~~SDA~~next.config''']| ~~'''27'''~~}|</ol>~~| '''28'''~~<ol start="4" style="list-style-type: lower-alpha;">~~| '''TWI2~~<li>The path to the kernel-~~SCL'''| '''PI9'''~~related deb package generated by compilation</li>{| ~~'''265'''~~class="wikitable" style="width:800px;"

|-

| [ o.k. ] Target directory [ '''~~256~~output/debs/''']| ~~'''PI0'''~~}</ol>| <ol start="5" style="~~text~~list-~~align~~style-type: ~~left~~lower-alpha;"|~~| '''29'''~~|>~~| '''30'''~~<li>The package name of the kernel image deb package generated by compilation</li>{| ~~'''GND'''| style~~class="~~text-align: left;~~wikitable"|| style="~~text-align~~width: ~~left~~800px;"|

|-

| [ o.k. ] File name [ '''~~271~~linux-image-next-sun50iw9_x.x.x_arm64.deb''']| ~~'''PI15'''~~}</ol>| <ol start="6" style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"|>~~| '''31'''~~<li>Compilation time</li>{|~~| '''32'''| '''PWM1'''| '''PI11'''| '''267'''~~class="wikitable" style="width:800px;"

|-

| ~~'''268'''| '''PI12'''~~| [ o.k. ] Runtime [ '''~~PWM2~~10 min''']| ~~'''33'''~~}|</ol>~~| '''34'''| '''GND'''~~| <ol start="7" style="~~text~~list-~~align~~style-type: ~~left~~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>{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|

|-

| [ o.k. ] Repeat Build Options [ '''~~258~~sudo ./build.sh BOARD=orangepizero2w BRANCH=next BUILD_OPT=kernel KERNEL_CONFIGURE=no''']| ~~'''PI2'''~~}</ol></li></ol><ol start="8" style="list-style-type: decimal;"><li>View the kernel-related deb package generated by compilation| <ol style="~~text~~list-~~align~~style-type: ~~left~~lower-alpha;"|>| <li>'''35linux-dtb-next-sun50iw9_x.x.x_arm64.deb'''Contains dtb files used by the kernel</li>|<li>'''linux-headers-next-sun50iw9_x.x.x_arm64.deb''' Contains kernel header files</li>| <li>'''36linux-image-next-sun50iw9_x.x.x_arm64.deb'''Contains kernel images and kernel modules</li>{| 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~~test@test: ~~left;"|| style="text~~~/orangepi-~~align: left;"|| '''GND'~~build$ ''| '~~''39'''~~|~~| '''40'''| style="text~~ls output/debs/linux-~~align: left;"|~~| *'''~~PI3'''| '''259'''~~|}

~~<ol start="2" style="list~~output/debs/linux-~~style~~dtb-~~type: decimal;"><li>The device node corresponding to uart2 is '''/dev/ttyAS2''', and the device node corresponding to uart5 is'''/dev/ttyAS5'''</li></ol>~~next-sun50iw9_x.x.x_arm64.deb

~~apollo-p2:~~output/ ~~# ls~~ debs/dev/ttyAS*linux-headers-next-sun50iw9_x.x.x_arm64.deb

output/~~dev~~debs/~~ttyAS0~~ linux-image-next-sun50iw9_x.x.x_arm64.deb|}</~~dev~~ol></~~ttyAS1~~ li></ol><ol start="9" style="list-style-type: decimal;"><li>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 ('''~~/dev/ttyAS2 /dev/ttyAS5~~it needs to be completely compiled once This function can only be turned off after obtaining the Linux kernel source code, otherwise it will prompt that the source code of the Linux kernel cannot be found'''), otherwise the modifications will be restored. The method is as follows:</li>

~~<ol start="3" style="list~~Set the IGNORE_UPDATES variable in '''userpatches/config-~~style-type: decimal~~default.conf''' to "yes"">~~<li>First open wiringOP APP on the desktop</li></ol>~~

~~[[File~~{| class="wikitable" style="width:~~zero2w~~800px;" |-~~img351~~| test@test:~/orangepi-build$ '''vim userpatches/config-default.~~png]]~~conf'''

IGNORE_UPDATES="'''yes'''"|}</ol><ol start="410" style="list-style-type: decimal;"><li>~~Then click~~ If the ~~'''UART_TEST'''button~~ kernel is modified, you can use the following method to ~~open~~ update the ~~UART test interface~~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</olli>{| class="wikitable" style="width:800px;" |-| test@test:~/orangepi-build$ '''cd output/debs'''

~~[[File~~test@test:~~zero2w~~~/orangepi-~~img359.png]]~~build/output/debs$ '''scp \'''

'''linux-image-next-sun50iw9_x.x.x_arm64.deb root@192.168.1.xxx:/root'''|}</ol><ol start="52" style="list-style-type: ~~decimal~~lower-alpha;"><li>~~The serial port test interface~~ Install the deb package of ~~wiringOP is as shown in~~ the ~~figure below~~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>

~~[[File:zero2w-img360.png]]~~== Compile rootfs ==

~~<ol start="6" style="list-style-type: decimal;"><li>Then select~~ # Run the ~~'''/dev/ttyAS2''' or'''/dev/ttyAS5''' node in the selection box[[File:zero2w-img361~~build.~~png]]</li><li>Enter the baud rate you want to set in the edit box~~sh script, ~~and then click the '''OPEN''' button~~ remember to ~~open the uart node. After the opening is successful, the '''OPEN''' button becomes unselectable, and the '''CLOSE''' button and '''SEND''' button become selectable.</li></ol>~~add sudo permissions

~~[[File~~:~~zero2w~~:{| class="wikitable" style="width:800px;" |-~~img362~~| test@test:~/orangepi-build$ '''sudo ./build.~~png]]~~sh'''|}

<ol start="82" 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~~ Select '''~~SEND~~Rootfs and all deb packages''' ~~button to start sending.~~and press Enter</li~~></ol~~>

~~[[File:zero2w-img363.png]]~~<div class="figure">

~~<ol start="10" style="list~~[[File:zero2w-~~style-type: decimal;"><li>If everything is normal, the received string will be displayed in the receiving box</li></ol>~~img285.png]]

~~[[File~~</div></ol><ol start="3" style="list-style-type:~~zero2w-img364.png]]~~decimal;"><li>Then select the model of the development board</li>

[[File:zero2w-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.<~~span id~~ol style="~~pin~~list-~~spi~~style-~~test~~type: lower-~~method~~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></~~span~~ol><ol start="5" style="list-style-type: decimal;"><li>Then select the type of rootfs</li> [[File:zero2w-img286.png]]</ol><ol start= ~~40pin SPI test method =~~"6" style="list-style-type: decimal;"><li>Then select the type of image<ol style="list-style-type: lower-alpha;"><li>'''Image with console interface (server)''' 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.</li>

~~# As~~ <div class="figure"> [[File:zero2w-img287.png]] </div></ol></li></ol><ol start="7" style="list-style-type: decimal;"><li>If you are compiling the server version of the image, you can also choose to compile the Standard version or the Minimal version. The Minimal version will have much less pre-installed software than the Standard version ('''please do not choose the Minimal version without special needs, because many things are not pre-installed by default. Some functions may not be ~~seen from~~ available''')</li> <div class="figure"> [[File:zero2w-img288.png]] </div></ol><ol start="8" style="list-style-type: decimal;"><li>If you are compiling a desktop version of the ~~table below~~image, you also need to select the ~~spi available for the 40pin interface~~ type of desktop environment. Currently, only XFCE is ~~spi1~~maintained, ~~and there are two chip~~ so please select an XFCE type desktop.</li> [[File:zero2w-img289.png]] [[File:zero2w-img290.png]] You can then select ~~pins cs0 and cs1~~additional packages that need to be installed. Please press the Enter key here to skip directly.

[[File:zero2w-img291.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Then the compilation of rootfs will start. Some of the information prompted during compilation are as follows:<ol style="list-style-type: lower-alpha;"><li>Type of rootfs</li>{| class="wikitable" style="width:800px;"

|-

| ~~'''GPIO serial number'''~~| [ o.k. ] local not found [ Creating new rootfs cache for '''~~GPIO~~bullseye''']| ~~'''Function'''~~}~~| '''pin'''~~|~~| '''pin'''~~</ol>~~| '''Function'''~~<ol start="2" style="list-style-type: lower-alpha;">~~| '''GPIO'''~~<li>The storage path of the compiled rootfs compressed package</li>{| ~~'''GPIO serial number'''~~class="wikitable" style="width:800px;"

|-

~~| style="text-align: left;"~~|~~| style="text-align: left;"|| '''3~~[ o.k.3V] Target directory [ '''~~| '''1~~orangepi-build/external/cache/rootfs''']|}~~| '''2'''~~</ol>~~| '''5V'''~~| <ol start="3" style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"|><li>The name of the rootfs compressed package generated by compilation</li>{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|

|-

| [ o.k. ] File name [ '''~~264~~bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4''']| }</ol></li></ol><ol start="10" style="list-style-type: decimal;"><li>View the compiled rootfs compressed package<ol style="list-style-type: lower-alpha;"><li>'''~~PI8~~bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4'''It is a compressed package of rootfs. The meaning of each field in the name is</li> | :a) '''~~TWI1-SDA~~bullseye'''represents the type of Linux distribution of rootfs| :b) '''3xfce'''indicates that the rootfs is the desktop version, and if it is cli, it indicates the server version.|| :c) '''4arm64'''represents the architecture type of rootfs| :d) '''5V25250ec7002de9e81a41de169f1f89721'''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="2" style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"|><li>'''bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4.list''' Lists the package names of all packages installed by rootfs</li>{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|

|-

| test@test:~/orangepi-build$ '''~~263~~ls external/cache/rootfs/'''~~| '''PI7'''| '''TWI1~~bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4 bullseye-xfce-~~SCL'''~~arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4.current ~~| '''5'''~~bullseye-xfce-arm64.5250ec7002de9e81a41de169f1f89721.tar.lz4.list|}~~| '''6'''~~</ol>~~| '''GND'''~~</li></ol>~~| style~~<ol start="~~text-align: left;~~11"|| style="~~text~~list-style-~~align~~type: ~~left~~decimal;"||->| <li>If the required rootfs already exists under '''~~269~~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 '''~~PI13~~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> ~~| '''PWM3'''~~~~| '''7'''~~|== Compile linux image ==~~| '''8'''~~| # Run the '''~~UART0_TX~~build.sh'''script, remember to add sudo permissions~~| '''PH0'''~~::{| ~~'''224'''~~class="wikitable" style="width:800px;"

|-

| ~~style~~test@test:~/orangepi-build$ '''sudo ./build.sh'''|} <ol start="~~text-align: left;~~2"|| style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|>| <li>Select '''~~GND~~Full OS image for flashing'''and press Enter</li>~~| '''9'''~~|<div class="figure">~~| '''10'''| '''UART0_RX'''~~[[File:zero2w-img292.png]]~~| '''PH1'''| '''225'''~~</div></ol>|<ol start="3" style="list-style-type: decimal;">~~| '''226'''~~<li>Then select the model of the development board</li>~~| '''PH2'''| '''UART5_TX'''~~[[File:zero2w-img275.png]]~~| '''11'''~~</ol>|<ol start="4" style="list-style-type: decimal;">~~| '''12'''~~<li>Then select the branch type of the kernel source code. Different versions of the kernel source code maintain different rootfs types.| <ol style="~~text~~list-style-~~align~~type: ~~left~~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>~~| '''PI1'''~~<ol start="5" style="list-style-type: decimal;">~~| '''257'''~~<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;">~~| '''227'''~~<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.~~| '''PH3'''~~[[File:zero2w-img277.png]]</li></ol>~~| '''UART5_RX'''~~</li>~~| '''13'''~~<li>Then select the type of rootfs</li>|~~| '''14'''~~[[File:zero2w-img286.png]]~~| '''GND'''~~</ol>| <ol start="7" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|><li>Then select the type of image| <ol style="~~text~~list-~~align~~style-type: ~~left~~lower-alpha;"||->| <li>'''~~261~~Image with console interface (server)'''Represents the image of the server version, which is relatively small in size.</li>| <li>'''~~PI5~~Image with desktop environment'''Represents an image with a desktop, which is relatively large in size.</li>~~| '''UART2_TX'''| '''15'''~~<div class="figure"> [[File:zero2w-img287.png]] </div></ol></li></ol>|<ol start="8" style="list-style-type: decimal;">| <li>If you are compiling the server version of the image, you can also choose to compile the Standard version or the Minimal version. The Minimal version will have much less pre-installed software than the Standard version ('''16please 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>~~| '''PWM4'''| '''PI14'''~~<div class="figure">~~| '''270'''~~|[[File:zero2w-img288.png]]| </div></ol><ol start="9" style="~~text~~list-~~align~~style-type: ~~left~~decimal;"|><li>If you are compiling a desktop version of the image, you also need to select the type of desktop environment. Currently, only XFCE is maintained, so please select an XFCE type desktop.</li> [[File:zero2w-img289.png]] [[File:zero2w-img290.png]] You can then select additional packages that need to be installed. Please press the Enter key here to skip directly. [[File:zero2w-img291.png]]</ol>| <ol start="10" style="~~text~~list-~~align~~style-type: ~~left~~decimal;"|><li>Then the compilation of the linux image will begin. The general process of compilation is as follows</li> ::a. Initialize the compilation environment of Ubuntu PC and install the software packages required for the compilation process. ::b. Download the source code of u-boot and linux kernel (if already cached, only update the code) ::c. Compile u-boot source code and generate u-boot deb package ::d. Compile linux source code and generate linux-related deb packages ::e. Make the deb package of linux firmware ::f. Make the deb package of orangepi-config tool ::g. Create a deb package with board-level support ::h. If you compile the desktop version image, you will also create a desktop-related deb package. ::i. Check whether rootfs has been cached. If not, re-create rootfs. If it has been cached, decompress it directly and use it. ::j. Install the deb package generated previously into rootfs ::k. Make some specific settings for different development boards and different types of images, such as pre-installing additional software packages, modifying system configurations, etc. ::l. Then create the image file and format the partition. The default type is ext4. ::m. Then copy the configured rootfs to the mirror partition. ~~| '''3~~::n.~~3V'''~~Then update initramfs~~| '''17'''~~|::o. Finally, write the bin file of u-boot into the image through the dd command.~~| '''18'''~~</ol>| <ol start="11" style="~~text~~list-~~align~~style-type: ~~left~~decimal;"|>~~| '''PH4'''~~<li>After compiling the image, the following message will be displayed~~| '''228'''~~<ol style="list-style-type: lower-alpha;">|-<li>The storage path of the compiled image</li>{| ~~'''231'''~~class="wikitable" style="width:800px;" | ~~'''PH7'''~~-| ~~'''SPI1_MOSI'''~~| [ o.k. ] Done building [ '''19output/images/orangepizero2w_x.x.x_debian_bullseye_linux6.1.xx_xfce_desktop/orangepizero2w_x.x.x_debian_bullseye_linux6.1.xx_xfce_desktop.img''']|}~~| '''20'''~~</ol>~~| '''GND'''~~| <ol start="2" style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"|><li>Compilation time</li>{| class="wikitable" style="~~text-align~~width: ~~left~~800px;"|

|-

| ~~'''232'''~~| '''~~PH8~~[ o.k. ] Runtime [ 19 min ]'''| ~~'''SPI1_MISO'''~~}~~| '''21'''~~|~~| '''22'''~~</ol>~~| '''UART2_RX'''~~<ol start="3" style="list-style-type: lower-alpha;">~~| '''PI6'''~~<li>Repeat the command to compile the image. Use the following command to start compiling the image directly without selecting it through the graphical interface.</li>{| ~~'''262'''~~class="wikitable" style="width:800px;"

|-

| [ o.k. ] Repeat Build Options [ '''~~230~~sudo ./build.sh BOARD=orangepizero2w BRANCH=next BUILD_OPT=image RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=yes''']| ~~'''PH6'''~~}</ol></li></ol>~~| '''SPI1_CLK'''~~| = '''23Instructions for using the Orange Pi OS Arch system'''=|~~| '''24'''~~~~| '''SPI1_CS0'''~~== Orange Pi OS Arch system function adaptation status ==~~| '''PH5'''~~{| ~~'''229'''~~class="wikitable" style="width:800px;text-align: center;"

|-

~~| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''25'''~~|~~| '''26'''| '''SPI1_CS1'''~~| '''~~PH9~~Motherboard functions'''| '''~~233~~OPi OS Arch'''

|-

| '''~~266~~HDMI video'''| '''~~PI10'''| '''TWI2-SDA'''| '''27'''~~|~~| '''28'''| '''TWI2-SCL'''| '''PI9'''| '''265~~OK'''

|-

| '''~~256~~HDMI Audio'''| '''~~PI0~~OK'''~~| style="text-align: left;"|| '''29'''~~|~~| '''30'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~271'''| '''PI15'''| style="text~~Type-~~align: left;"|| '''31'''~~|~~| '''32'''| '''PWM1'''| '''PI11~~C USB2.0 x 2'''| '''~~267~~OK'''

|-

| '''~~268~~TF Card Startup'''| '''~~PI12~~OK'''|-| '''WIFI'''| '''OK'''|-| '''Bluetooth'''| '''OK'''|-| '''LED Light'''| '''OK'''|-| '''40pin GPIO'''| '''OK'''|-| '''40pin I2C'''| '''OK'''|-| '''40pin SPI'''| '''OK'''|-| '''40pin UART'''| '''OK'''|-| '''40pin PWM'''| '''OK'''|-| '''~~PWM2~~Temperature Sensor'''| '''33OK'''|-| '''34Hardware watchdog'''| '''~~GND~~OK'''| ~~style="text~~-~~align: left;"~~|'''Mali GPU'''| '''NO'''

|-

| '''~~258~~Video codec'''| '''~~PI2'''~~| NO'''

|}

~~<ol start~~{| class="2wikitable" style="~~list~~width:800px;text-~~style-type~~align: ~~decimal~~center;">~~<li>The device node corresponding to SPI1 CS0 is~~ |-| '''24pin expansion board function'''| '''OPi OS Arch'''|-| '''100M network port'''| '''OK'''|-| '''100M Ethernet port light'''| '''OK'''|-| '''~~/dev/spidev1~~USB2.0HOST x 2'''~~, and the device node corresponding to SPI1 CS1 is~~ | '''OK'''|-| '''Infrared reception'''| '''OK'''|-| '''Headphone audio playback'''| '''OK'''|-| '''On/~~dev/spidev1.1~~off button'''~~</li></ol>~~| '''OK'''~~apollo~~|-~~p2:/ #~~ | '''LRADC''' '''Custom buttons x 2'''| '''ls /dev/spidev1.*OK'''|-| '''TV-OUT'''| '''NO</~~dev/spidev1.0 /dev/spidev1.1~~span>'''|}

<~~ol start~~span id="~~3" style="list~~orange-pi-os-arch-system-user-~~style~~guide-~~type: decimal;~~instructions">~~<li>Here is a demonstration to test the SPI1 interface through the '''w25qxx''' module. First, connect the w25qxx module to the SPI1 interface.</li~~></olspan>

'''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.'''== Orange Pi OS Arch System User Guide Instructions ==

~~<ol start="4" style="list-style-type: decimal;"><li>Then open wiringOP APP on~~ First of all, please note that the ~~desktop</li></ol>~~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.

~~[[File~~When the OPi OS Arch system is started for the first time, you need to 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 setup steps of the user wizard are as follows:~~zero2w-img351.png]]~~

<ol ~~start="5"~~ style="list-style-type: ~~decimal~~lower-alpha;"><li>~~Then click~~ After burning the system, when you start it for the ~~'''SPI_TEST''' button to open~~ first time and enter the ~~SPI test interface~~desktop, you will see the user wizard program shown in the figure below.</lip><~~/ol~~div class="figure">

[[File:zero2w-~~img365~~img293.png]]

<~~ol start="6" style="list-style-type: decimal;"~~/div></li><li>~~Then select the spi device node in the upper left corner. If~~ First you ~~test the onboard SPIFlash directly, just keep the default '''/dev/spidev0.0'''. If the '''w25qxx''' module is connected~~ need 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/spidev1.1'''~~language you want

[[File:zero2w-~~img366~~img294.png]]

</div></li>

<li>~~Then click~~ After selecting the ~~'''OPEN''' button~~ language, the user wizard will immediately switch to ~~initialize~~ the ~~SPI~~corresponding language interface, as shown below in Chinese<~~/li></ol~~div class="figure">

[[File:zero2w-~~img367~~img295.png]]

<~~ol start="8" style="list-style-type: decimal;"~~/div></li><li>Then ~~fill in the bytes that need to be sent, such as reading the ID information of the onboard SPIFlash, filling in~~ select the ~~address 0x9f in data[0], and then click the '''TRANSFER''' button~~area</lip><~~/ol~~div class="figure">

[[File:zero2w-~~img368~~img296.png]]

<~~ol start="9" style="list-style-type: decimal;"~~/div></li><li>~~Finally,~~ Then select the ~~APP will display the read ID information of the onboard SPI Flash.~~keyboard model</lip><~~/ol~~div class="figure">

[[File:zero2w-~~img369~~img297.png]]

<~~ol start~~/div></li><li>Then create a new username and set a password<div class="10figure" ~~style~~> [[File:zero2w-img298.png]] </div></li><li>Then make sure there is no problem with the selection, and then click the install '''button'''<div class="~~list~~figure"> [[File:zero2w-~~style~~img299.png]] </div></li><li>Then wait for the installation to complete<div class="figure"> [[File:zero2w-~~type~~img300.png]] </div></li><li>After the installation is complete, you need to click the '''Finish''' button to restart the system.<div class="figure"> [[File: ~~decimal;"~~zero2w-img301.png]] </div></li><li>If The Orange Pi Hello program will automatically start after restarting. At this time, you need to remove the ~~w25qxx module connected~~ check '''mark of Start on startup''' in the lower right corner, otherwise you need to ~~40pin SPI1 is read~~manually close the Orange Pi Hello program every time you start it.<div class="figure"> [[File:zero2w-img302.png]] </div>At this point, you can use the newly created username and password to log in to the ~~ID information of~~ OPi OS system through the ~~onboard SPI Flash is also similar~~serial port or ssh.</li></ol> == How to set DT overlays == The multiplexing functions such as I2C/SPI/UART/PWM in the 40-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.

~~=== 40pin I2C test method ===~~to open DT overlays in OPi OS Arch system is as follows:

# ~~As can be seen from~~ First open the ~~table below, the Android12 TV system has i2c1 and i2c2 turned on by default~~'''/boot/extlinux/extlinux.conf''' configuration file

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

|-

| ~~'''GPIO serial number'''~~| [orangepi@orangepi-pc ~]$ '''~~GPIO~~sudo vim /boot/extlinux/extlinux.conf'''| ~~'''Function'''~~}~~| '''pin'''~~|<ol start="2" style="list-style-type: decimal;">| <li>Then open the corresponding configuration by adding '''~~pin~~FDTOVERLAYS'''| '''~~Function~~/dtbs/allwinner/overlay/xxx.dtbo'''| in '''~~GPIO~~/boot/extlinux/extlinux.conf'''</li> {| ~~'''GPIO serial number'''~~class="wikitable" style="background-color:#ffffdc;width:800px;"

|-

~~| style="text-align: left;"~~|~~| style="text-align: left;"|~~| <big>'''3Note that xxx.dtbo in FDTOVERLAYS /dtbs/allwinner/overlay/xxx.dtbo needs to be replaced with the specific dtbo configuration, please do not copy it.~~3V'''| '''1~~'''</big>|}{| ~~'''2'''| '''5V'''| style~~class="~~text-align: left;~~wikitable"|| style="~~text-align~~width: ~~left~~800px;"|

|-

| [orangepi@orangepi-pc ~]$ '''~~264~~sudo vim /boot/extlinux/extlinux.conf'''~~| '''PI8'''| '''TWI1~~LABEL Orange Pi KERNEL /Image FDT /dtbs/allwinner/sun50i-h616-orangepi-~~SDA'''~~zero2w.dtb | '''3FDTOVERLAYS /dtbs/allwinner/overlay/xxx.dtbo'''#Configuration that needs to be added|}~~| '''4'''~~</ol>~~| '''5V'''~~| <ol start="3" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"|><li>The storage path of xxx.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="~~text-align~~width: ~~left~~800px;"|

|-

| ~~'''263'''~~| '''~~PI7~~/boot/dtbs/allwinner/overlay/'''| ~~'''TWI1-SCL'''~~}~~| '''5'''~~</li>|<li>The DT overlays configuration that can be used by the development board is as follows</li>~~| '''6'''| '''GND'''~~{| ~~style~~class="~~text-align: left;~~wikitable"|| style="width:800px;text-align: ~~left~~center;"|

|-

| '''~~269~~Functions on the development board'''| '''~~PI13'''| '''PWM3'''| '''7'''~~|~~| '''8'''| '''UART0_TX'''| '''PH0'''| '''224~~Corresponding DT overlays configuration'''

|-

~~| style="text-align: left;"|| style="text-align: left;"|~~| '''~~GND~~40pin - i2c0'''| '''9sun50i-h616-pi-i2c0.dtbo'''|-| '''1040pin - i2c1'''| '''~~UART0_RX'''| '''PH1'''| '''225~~sun50i-h616-pi-i2c1.dtbo'''

|-

| '''~~226~~40pin - i2c2'''| '''~~PH2'''| '''UART5_TX'''| '''11'''~~|~~| '''12'''| style="text~~sun50i-h616-pi-~~align: left;"|| '''PI1'''| '''257~~i2c2.dtbo'''

|-

| '''~~227~~40pin - uart2'''| '''~~PH3'''| '''UART5_RX'''| '''13'''~~|~~| '''14''~~sun50i-h616-pi-uart2.dtbo'| ''~~'GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~261~~40pin - uart3'''| '''~~PI5'''| '''UART2_TX'''| '''15'''~~|~~| '''16'''| '''PWM4'''| '''PI14'''| '''270~~sun50i-h616-pi-uart3.dtbo'''

|-

~~| style="text-align: left;"|| style="text-align: left;"|~~| '''~~3.3V~~40pin - uart4'''| '''~~17'''~~|~~| '''18'''| style="text~~sun50i-h616-pi-~~align: left;"|| '''PH4'''| '''228~~uart4.dtbo'''

|-

| '''~~231~~40pin - uart5'''| '''~~PH7'''| '''SPI1_MOSI'''| '''19'''~~|~~| '''20''~~sun50i-h616-ph-uart5.dtbo'| ''~~'GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~232~~40pin - pwm1'''| '''~~PH8'''| '''SPI1_MISO'''| '''21'''~~|~~| '''22'''| '''UART2_RX'''| '''PI6'''| '''262~~sun50i-h616-pi-pwm1.dtbo'''

|-

| '''~~230~~40pin - pwm2'''| '''~~PH6'''| '''SPI1_CLK'''| '''23'''~~|~~| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229~~sun50i-h616-pi-pwm2.dtbo'''

|-

~~| style="text-align: left;"|| style="text-align: left;"|~~| '''~~GND~~40pin - pwm3'''| '''~~25'''~~|~~| '''26'''| '''SPI1_CS1'''| '''PH9'''| '''233~~sun50i-h616-pi-pwm3.dtbo'''

|-

| '''~~266~~40pin - pwm4'''| '''~~PI10'''| '''TWI2~~sun50i-h616-~~SDA'''| '''27'''~~|~~| '''28'''| '''TWI2~~pi-~~SCL'''| '''PI9'''| '''265~~pwm4.dtbo'''

|-

| '''~~256~~40pin - spi1 cs0'''| '''~~PI0'''| style="text~~sun50i-h616-spi1-cs0-~~align: left;"|| '''29'~~spidev.dtbo''|| '~~''30'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~271~~40pin - spi1 cs1'''| '''~~PI15'''| style="text~~sun50i-h616-spi1-cs1-~~align: left;"|| '''31'''~~|~~| '''32'''| '''PWM1'''| '''PI11'''| '''267~~spidev.dtbo'''

|-

| '''~~268~~40pin - spi1 cs0 cs1'''| '''~~PI12'''| '''PWM2'''| '''33'''~~|~~| '''34'''| '''GND~~sun50i-h616-spi1-cs0-cs1-spidev.dtbo'''~~| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~258~~设Set USB0 to Host mode'''| '''~~PI2'''| style="text~~sun50i-h616-~~align: left;"|| '''35'''~~|~~| '''36'''| style="text~~usb0-~~align: left;"|| '''PC12'''| '''76~~host.dtbo'''

|-

| '''~~272~~Turn off the green LED light'''| '''~~PI16'''| style="text~~sun50i-h616-zero2w-~~align: left;"|| '''37'''~~|~~| '''38'''| style="text~~disable-~~align: left;"|| '''PI4'''| '''260~~led.dtbo'''

|-

~~| style="text-align: left;"|| style="text-align: left;"|~~| '''~~GND~~How to close the UART0 debugging serial port'''| '''~~39'''~~|~~| '''40'''| style="text~~sun50i-h616-disable-~~align: left;"|| '''PI3'''| '''259~~uart0.dtbo'''

|}

</ol>

<li>If you need to open multiple configurations at the same time, just add the paths of multiple configurations directly after '''FDTOVERLAYS.''' For example, the configuration of opening i2c1 and uart5 at the same time is as follows</li>

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

|-

|

[orangepi@orangepi-pc ~]$ '''sudo vim /boot/extlinux/extlinux.conf'''

~~<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></ol>~~LABEL Orange Pi

~~apollo-p2:~~KERNEL / ~~# '''ls /dev/i2c-*'''~~Image

~~'''~~FDT /~~dev~~dtbs/~~i2c~~allwinner/sun50i-~~1 /dev/i2c~~h616-~~2''' /dev/i2c~~orangepi-5zero2w.dtb

'''FDTOVERLAYS /dtbs/allwinner/overlay/sun50i-h616-pi-i2c1.dtbo /dtbs/allwinner/overlay/sun50i-h616-ph-uart5.dtbo'''|}</ol><ol start="36" style="list-style-type: decimal;"><li>~~First open wiringOP APP on~~ After setting, you need to restart the ~~desktop~~system for the configuration to take effect.</li>{| class="wikitable" style="width:800px;" |-| [orangepi@orangepi-pc ~]$ '''sudo reboot'''|}</ol>

~~[[File:zero2w-img351.png]]~~== How to install software ==

~~<ol start="4" style="list-style-type: decimal;"><li>Then click~~ You can use the ~~'''I2C_TEST''' button~~ pacman package management tool to ~~open~~ install software that is not available in OPi OS. For example, the ~~i2c test interface</li></ol>~~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.

{| class="wikitable" style="width:800px;" |-| [~~[File:zero2w~~orangepi@orangepi-~~img370.png]~~pc ~]$ '''sudo pacman -Syy vim'''|}

<~~ol start~~span id="~~5" style="list~~android-12-tv-system-~~style~~usage-~~type: decimal;~~instructions">~~<li>The i2c test interface of wiringOP is shown in the figure below</li~~></olspan>

~~[[File:zero2w-img371.png]]~~= '''Android 12 TV system usage instructions''' =

<~~ol start~~span id="~~6" style="list~~supported-~~style~~android-~~type: decimal;~~versions">~~<li>Then click the device node selection box in the upper left corner to select the i2c you want to test~~</~~li></ol~~span>== Supported Android versions ==

~~[[File~~{| class="wikitable" style="width:~~zero2w~~800px;text-~~img372~~align: center;"|-| Android Version| Kernel version|-| '''Android 12 TV Version'''| '''linux5.~~png]]~~4'''|}

<~~ol start~~span id="~~7" style="list~~android-12-tv-function-~~style~~adaptation-~~type: decimal;~~status">~~<li>Then connect an i2c device to the 40pin i2c pin. Here we take the ds1307 rtc module as an example.~~</~~li></ol~~span>== Android 12 TV function adaptation status ==

~~[[File:zero2w-img178.png]]~~ ~~<ol start~~{| class="8wikitable" style="~~list~~width:800px;text-~~style-type~~align: ~~decimal~~center;">~~<li>The i2c address of the ds1307 rtc module is 0x68. After connecting the lines, we can use the~~ |-| '''~~i2cdetect -y 1~~Motherboard functions''' or | '''~~i2cdetect -y 2~~Android12 TV''' 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~~HDMI video'''~~~~| '''OrOK'''~~apollo~~|-~~p2:/ #~~ | '''~~i2cdetect -y 2~~HDMI Audio'''~~[[File:zero2w-img373.png]]</li><li>Then set the i2c address to 0x68 in wiringOP, and then click the~~ | '''~~OPEN~~OK''' ~~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~~Type-~~img375~~C USB2.~~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 '~~0 x 2''~~WRITE BYTE~~'~~'' button to perform the writing action[[File:zero2w-img378.png]]</li></ol></li><li>Then click the~~ | '''~~READ BYTE~~OK''' ~~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"~~

|-

|-

| ~~style="text-align: left;"|| style="text-align: left;"|| '''3.3V'''| '''1''~~'|| '''2WIFI'''| '''5VOK'''~~| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~264~~Bluetooth'''| '''~~PI8~~OK'''~~| '''TWI1-SDA'''| '''3'''~~|~~| '''4'''| '''5V'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~263~~USB Camera'''| '''~~PI7~~OK'''~~| '''TWI1-SCL'''| '''5'''~~|~~| '''6'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~269~~LED Light'''| '''~~PI13'''| '''PWM3'''| '''7'''~~|~~| '''8'''| '''UART0_TX'''| '''PH0'''| '''224~~OK'''

|-

~~| style="text-align: left;"|| style="text-align: left;"|| '''GND'''| '''9'''~~|~~| '''10'''| '''UART0_RX'''~~| '''~~PH1~~40pin GPIO'''| '''~~225~~OK'''

|-

| '''~~226~~40pin I2C'''| '''~~PH2'''| '''UART5_TX'''| '''11'''~~|~~| '''12'''| style="text-align: left;"|| '''PI1'''| '''257~~OK'''

|-

| '''~~227~~40pin SPI1'''| '''~~PH3~~OK'''~~| '''UART5_RX'''| '''13'''~~|~~| '''14'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~261~~40pin UART'''| '''~~PI5'''| '''UART2_TX'''| '''15'''~~|~~| '''16'''| '''PWM4'''| '''PI14'''| '''270~~OK'''

|-

~~| style="text-align: left;"|| style="text-align: left;"|| '''3.3V'''| '''17'''~~|~~| '''18'''| style="text-align: left;"|~~| '''~~PH4~~40pin PWM'''| '''~~228~~OK'''

|-

| '''~~231~~Temperature Sensor'''| '''~~PH7~~OK'''~~| '''SPI1_MOSI'''| '''19'''~~|~~| '''20'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~232~~Hardware watchdog'''| '''~~PH8'''| '''SPI1_MISO'''| '''21'''~~|~~| '''22'''| '''UART2_RX'''| '''PI6'''| '''262~~OK'''

|-

| '''~~230~~Mali GPU'''| '''~~PH6'''| '''SPI1_CLK'''| '''23'''~~|~~| '''24'''| '''SPI1_CS0'''| '''PH5'''| '''229~~OK'''

|-

~~| style="text-align: left;"|| style="text-align: left;"|~~| '''~~GND~~Video codec'''| '''25OK'''|}~~| '''26'''~~{| ~~'''SPI1_CS1'''| '''PH9'''| '''233'''~~class="wikitable" style="width:800px;text-align: center;"

|-

| '''~~266~~24pin Expansion board function'''| '''~~PI10~~Android12 TV'''| ~~'''TWI2~~-~~SDA'''| '''27'''~~|~~| '''28'''| '''TWI2-SCL'''~~| '''~~PI9~~100M network port'''| '''~~265~~OK'''

|-

| '''~~256~~100M Ethernet port light'''| '''~~PI0~~OK'''~~| style="text-align: left;"|| '''29'''~~|~~| '''30'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~271~~USB2.0 HOST x 2'''| '''~~PI15'''| style="text-align: left;"|| '''31'''~~|~~| '''32'''| '''PWM1'''| '''PI11'''| '''267~~OK'''

|-

| '''~~268~~Infrared reception'''| '''~~PI12~~OK'''~~| '''PWM2'''| '''33'''~~|~~| '''34'''| '''GND'''| style="text-align: left;"|| style="text-align: left;"|~~

|-

| '''~~258~~Headphone audio playback'''| '''~~PI2'''| style="text-align: left;"|| '''35'''~~|~~| '''36'''| style="text-align: left;"|| '''PC12'''| '''76~~OK'''

|-

|-

~~| style="text-align: left;"|| style="text-align: left;"|~~| '''~~GND'''| '''39'''~~|~~| '''40'''| style="text~~TV-~~align: left;"|| '''PI3~~OUT'''| '''~~259~~OK'''

|}

<~~ol start~~span id="~~2" style="list~~onboard-led-light-~~style~~display-~~type: decimal;~~instructions">~~<li>First click the wiringOP icon to open wiringOP APP~~</~~li></ol~~span>== Onboard LED light display instructions ==

~~[[File~~{| class="wikitable" style="width:~~zero2w~~800px;text-~~img351.png]]~~align: center;"|-|| '''green light'''| '''red light'''|-| '''u-boot startup phase'''| '''Off'''| '''on'''|-| '''Kernel boot to enter the system'''| '''on'''| '''on'''|}

<~~ol start~~span id="~~3" style="list~~how-to-return-to-the-previous-interface-~~style~~in-~~type: decimal;~~android"><li/span>~~Then click the '''PWM_TEST''' button on the main interface of wiringOP~~ == How to return to ~~enter~~ the ~~PWM test~~ previous interface~~</li></ol>~~in Android ==

~~[[File:zero2w~~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-~~img380~~clicking the mouse, and the keyboard cannot return.~~png]]~~

~~<ol start="4" style="list-style-type: decimal;"><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 the previous menu. The ~~PWM test interface~~ location of the return key is as ~~follows</li></ol>~~shown below. Shown:

~~<div class="figure">~~[[File:zero2w-img303.png]]

~~[[File:zero2w~~== How to use ADB ==

<~~/div><ol start~~span id="~~5" style="list~~use-network-connection-~~style~~adb-~~type: decimal;~~debugging">~~<li>Then set which PWM you want to use in the Channel. The default is PWM1. If you want to set it to PWM2, just enter 2 in the Channel. PWM3 and PWM4 and so on.~~</~~li></ol~~span>=== Use network connection adb debugging ===

~~[[File~~{| class="wikitable" style="background-color:#ffffdc;width:~~zero2w~~800px;" |-~~img382~~| <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="6" style="list-style-type: decimal;"><li>Then you can set~~ # Make sure the ~~PWM period. The default configuration is~~ '''~~50000ns~~service.adb.tcp.port'''~~. The converted PWM frequency~~ of the Android system is ~~'''20KHz'''</li></ol>~~set to 5555 port number

~~[[File~~:~~zero2w~~:{| class="wikitable" style="width:800px;" |-| apollo-~~img383~~p2:/ # '''getprop | grep "adb.~~png]]~~tcp"'''

~~<ol start="7" style="list-style-type~~[service.adb.tcp.port]: ~~decimal;">~~[5555]~~<li>Then click the '''EXPORT'''button to export PWM</li></ol>~~|}

~~[[File~~<ol start="2" style="list-style-type: decimal;"><li>If '''service.adb.tcp.port''' is not set, you can use the following command in the serial port to set the port number of the network adb</li>{| class="wikitable" style="width:~~zero2w~~800px;" |-~~img384~~| apollo-p2:/ # '''setprop service.adb.tcp.~~png]]~~port 5555'''

~~<ol start="8" style="list~~apollo-~~style-type~~p2: ~~decimal;"><li>Then drag the progress bar below to change the PWM duty cycle, and then check~~ / # '''~~Enable~~stop adbd''' ~~to output the PWM waveform.</li></ol>~~

~~[[File~~apollo-p2:/ # '''start adbd'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Install adb tool on Ubuntu PC</li>{| class="wikitable" style="width:800px;" |-| test@test:~~zero2w~~~$ '''sudo apt-~~img385.png]]~~get update'''

test@test:~$ '''sudo apt-get install -y adb'''|}</ol><ol start="94" style="list-style-type: decimal;"><li>Then ~~use an oscilloscope~~ connect network adb on Ubuntu PC</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''adb connect 192.168.1.xxx:5555''' '''(Need to be modified to ~~measure~~ the ~~corresponding pins in~~ IP address of the ~~40pin~~ development board ~~and you can see the following waveform.</li></ol>~~)'''

~~[[File~~* daemon not running; starting now at tcp:~~zero2w-img386.png]]~~5037

<~~span id="how-to-compile-android-12-source-code"~~p>* daemon started successfully</~~span~~p>

~~= '''How~~ connected to ~~compile Android 12 source code''' =~~192.168.1.xxx:5555

~~~~

~~== Download the source code of Android 12 ==~~

~~<ol style="list-style-type~~test@test: ~~decimal;"><li>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<ol style="list-style-type: lower-alpha;"><li>Google Cloud Drive</li></ol></li></ol>~~~$ '''adb devices'''

~~[[File:zero2w-img387.png]]~~List of devices attached

192.168.1.xxx:5555 device|}</ol><ol start="25" 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~~ Then you can log in to ~~check~~ the ~~MD5 checksum:~~android system through adb shell on Ubuntu PC</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| test@test:~$ '''adb shell'''

~~test@test~~apollo-p2:~~~$ '''md5sum~~ / #|}</ol>

~~H618-Android12-Src.tar.gzaa: '''OK'''~~=== Use data cable to connect adb debugging ===

~~H618-Android12-Src~~# 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).~~tar.gzab: '''OK'~~In this case, the development board is powered by the computer's USB interface, so please ensure that the computer's USB interface can provide the most sufficient power to drive the development board.

::[[File:zero2w-img304.png]] [[File:zero2w-img305.~~....~~png]]

<li>Install adb tool on Ubuntu PC</li>

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

|-

|

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

test@test:~$ '''sudo apt-get install -y adb'''

|}

</ol>

<li>~~Then you need to merge multiple compressed files into one, and then extract~~ Check whether the ~~Android source code. The command looks like this:~~ADB device is recognized</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| test@test:~$ '''adb devices'''

~~test@test:~$ '''cat H618-Android12-Src.tar.gza* > H618-Android12-Src.tar.gz'''~~ ~~test@test:~$ '''tar -xvf H618-Android12-Src.tar.gz'''~~List of devices attached

4c00146473c28651dd0 device

|}

</ol>

<li>Then ~~unzip~~ you can log in to the ~~compressed package of the files modified by Orange Pi Zero2w~~android system through adb shell on Ubuntu PC</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| test@test:~$ '''adb shell'''

~~test@test~~apollo-p2:~/ $ ~~'''tar zxf opizero2w_android12_patches.tar.gz'''~~|}</ol>

~~test@test:~$ '''ls'''~~== View how to set HDMI display resolution ==

<ol style="list-style-type: decimal;"><li>Enter first '''~~opizero2w_android12_patches~~Settings''' ~~opizero2w_android12_patches~~[[File:zero2w-img306.~~tar~~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.gzpng]]</li></ol>

<~~ol start~~span id="~~5" style="list~~hdmi-to-vga-display-~~style~~test-~~type: decimal;~~1"><li/span>~~Then copy the files modified by Orange Pi Zero2w~~ === HDMI to ~~the Android source code</li></ol>~~VGA display test ===

~~test@test~~<ol style="list-style-type:~~~$ '''cp~~ decimal;"><li>First you need to prepare the following accessories<ol style="list-~~rf opizero2w_android12_patches/* H618~~style-~~Android12~~type: lower-~~Src~~alpha;"><li>HDMI to VGA converter</~~'''~~li>

[[File:zero2w-img144.png]]</ol><~~span id~~ol start="~~compile-the-source~~2" style="list-~~code~~style-oftype: lower-~~android-12~~alpha;"><li>A VGA cable and a Mini HDMI male to HDMI female adapter</~~span~~li>~~== Compile the source code of Android 12 ==~~

~~'''Android12 is compiled on an x86_64 computer with Ubuntu 22~~[[File:zero2w-img145.~~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:'''~~ png]] [[~~https~~File:~~//repo.huaweicloud.com/ubuntu~~zero2w-~~releases/22~~img146.04png]]</~~ubuntu~~ol><ol start="3" style="list-~~22.04.2~~style-~~desktop~~type: lower-~~amd64.iso '''https:~~alpha;"><li>A monitor or TV that supports VGA interface</li></~~repo.huaweicloud.com~~ol></~~ubuntu-releases~~li></~~22.04/ubuntu-22.04.2-desktop-amd64.iso''']~~ol>

~~'''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~~ <ol start="2" style="list-style-type: decimal;"><li>HDMI to VGA display test is ~~recommended. The more CPU cores, the better.'''~~as follows</li>

~~# First install the software packages needed to compile Android12 source code~~[[File:zero2w-img313.png]]

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

~~test@test:~$ '''sudo apt~~== WI-~~get install -y git gnupg flex bison gperf build-essential \'''~~FI connection method ==

# Choose first '''~~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 \~~Settings'''

~~'''libssl~~::[[File:zero2w-~~dev libncurses5 clang gawk'''~~img306.png]]

<li~~><p~~>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~~ select '''~~./build.sh config~~Network & Internet''' ~~to set compilation options</li></ol>~~</li~~></ol~~>

~~test@test~~[[File:~~~$ '''cd H618~~zero2w-~~Android12~~img314.png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then turn on WI-~~Src~~FI</~~longan'''~~li>

~~test@test~~[[File:~zero2w-img315.png]]</~~H618~~ol><ol start="4" style="list-~~Android12~~style-~~Src/longan$~~ type: decimal;"><li>After turning on WI-FI, you can see the searched signals under '''~~./build.sh config~~Available networks'''.</li>

~~Welcome~~ [[File:zero2w-img316.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>After selecting the WI-FI you want to ~~mkscript setup progress~~connect to, the password input interface shown below will pop up.</li>

~~All available platform:~~<div class="figure">

0[[File:zero2w-img317. ~~android~~png]]

1</div></ol><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. ~~linux~~</li>

~~Choice [android]: '''0'''~~<div class="figure">

~~All available ic~~[[File:zero2w-img318.png]]

~~0. h618~~</div></ol><ol start="7" style="list-style-type: decimal;"><li>The display after successful WI-FI connection is as shown below</li>

~~Choice~~ [~~h618~~[File:zero2w-img319.png]]~~: '''0'''~~</ol>

~~All available board:~~== How to use WI-FI hotspot ==

0# First, please make sure that the Ethernet port is connected to the network cable and can access the Internet normally. ft# Then select '''Settings'''

1::[[File:zero2w-img306. p1png]]

~~2. p2~~<ol start="3" style="list-style-type: decimal;"><li>Then select '''Network & Internet'''</li>

3[[File:zero2w-img314. p7png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then select '''WIFI hotspot'''</li>

4[[File:zero2w-img320. ~~p7l~~png]]</ol><ol start="5" 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>

5[[File:zero2w-img321. ~~perf1~~png]]</ol><ol start="6" style="list-style-type: decimal;"><li>At this time, you can take out your mobile phone. If everything is normal, you can find the WIFI hotspot with the same name ('''here AndroidAP_7132''') shown under the '''Hotspot name''' in the picture above in the WI-FI list searched by the mobile phone. Then you can click AndroidAP_7132 to connect to the hotspot. The password can be seen under the '''Hotspot password''' in the picture above.</li>

6[[File:zero2w-img322. ~~perf2~~png]]</ol><ol start="7" style="list-style-type: 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 '''WI-FI Hotspot''' of the development board can be used normally. ~~perf3~~</li>

8[[File:zero2w-img323. qapng]]</ol>

~~Choice [p2]: '''2'''~~== How to check the IP address of the Ethernet port ==

~~All available flash:~~# 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.

0::[[File:zero2w-img107. ~~default~~png]]

1<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. ~~nor~~png]]</li><li>Then select '''Network & Internet'''[[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.[[File:zero2w-img326.png]]</li></ol>

~~Choice [default]: '''0'''~~

~~All available kern_ver:~~== Bluetooth connection method ==

~~0. linux-5.4~~# Choose first '''Settings'''

~~Choice~~ ::[[~~linux~~File:zero2w-5img306.4png]]~~: '''0'''~~

~~All available arch~~<ol start="2" style="list-style-type:decimal;"><li>Then select '''Bluetooth'''</li>

0[[File:zero2w-img327. ~~arm~~png]]</ol><ol start="3" style="list-style-type: decimal;"><li>Then Open '''Bluetooth Enable'''</li>

1[[File:zero2w-img328. ~~arm64~~png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then click '''Pair new device'''to start scanning for surrounding Bluetooth devices</li>

~~Choice~~ [~~arm64~~[File:zero2w-img329.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>The searched Bluetooth devices will be displayed under '''1Available devices'''</li>

[[File:zero2w-img330.png]]</ol><ol start="6" style="list-style-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 '''~~......~~Pair'''option</li>

*** Default [[File:zero2w-img331.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>What is tested here is the Bluetooth configuration ~~is based~~ 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 ~~'sun50iw9p1smp_h618_android_defconfig'~~the phone to start the pairing process.</li>

#[[File:zero2w-img332.png]]</ol><ol start="8" style="list-style-type: decimal;"><li>After pairing is completed, open '''Paired devices''' and you will see the paired Bluetooth devices.</li>

~~# configuration written~~ [[File:zero2w-img333.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>At this time, you can use the Bluetooth of your mobile phone to send a picture to the development board. After sending, you can see the following confirmation interface in the Android system of the development board, and then click '''Accept''' to start receiving the pictures sent by the mobile phone.~~config~~</li>

#[[File:zero2w-img334.png]]</ol><ol start="10" style="list-style-type: decimal;"><li>Pictures received by the Bluetooth system of the development board Android system can be viewed in '''Received files'''.</li>

~~make~~[1[File:zero2w-img335.png]]~~: Leaving directory '~~</~~home/test/H618~~ol></~~build'~~span>

~~make: Leaving directory '/home/test/H618-Android12-Src/longan/kernel/linux-5.4'~~== How to set USB0 to HOST mode ==

~~INFO~~As shown in the figure below, there are two Type-C interfaces on the motherboard of the development board: ~~clean buildserver~~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.

~~INFO~~[[File: ~~prepare_buildserver~~zero2w-img160.png]]

~~<ol start="2" style="list-style-type: lower-alpha;"><li>Then run~~ USB0 of the ~~'''./build.sh''' script~~ 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 ~~start compilation~~connect USB devices .~~</li></ol>~~

~~test@test~~If you want to use USB0 to connect USB devices, you need to set USB0 to HOST mode. The method is as follows:~~~/H618-Android12-Src/longan$ '''./build.sh'''~~

<ol ~~start="3"~~ style="list-style-type: lower-alpha;"><li>~~After compilation is completed, you will see~~ Run the following ~~output~~command to set USB0 to HOST mode:</li><{| class="wikitable" style="width:800px;" |-| apollo-p2:/ # '''cat /sys/devices/platform/soc@3000000/soc@3000000\:usbc0@0/~~ol>~~usb_host'''

~~sun50iw9p1 compile Kernel successful~~host_chose finished! apollo-p2:/ #|}</ol><ol start="2" style="list-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''' device_chose finished! apollo-p2:/ #|}</ol><ol start="3" style="list-style-type: lower-alpha;"><li>The command to view the current mode of USB0 is</li>{| class="wikitable" style="width:800px;" |-| apollo-p2:/ # '''cat /sys/devices/platform/soc@3000000/soc@3000000\:usbc0@0/otg_role''' usb_host|}</ol> == How to use USB camera == # First insert the USB (UVC protocol) camera into the USB interface of the development board# If the USB camera is recognized normally, the corresponding video device node will be generated under /dev

~~INFO~~: ~~Prepare toolchain ...~~:{| class="wikitable" style="width:800px;" |-| console:/ # '''ls /dev/video0'''

~~'''......'''~~/dev/video0|}

~~INFO~~<ol start="3" style="list-style-type: ~~build kernel OK~~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|'''How to use ADB''']]".</li><li>Download the USB camera test APP from the '''official tool''' on the development board information download page</li>

~~INFO: build rootfs ...~~<div class="figure">

~~INFO~~[[File: ~~skip make rootfs for android~~zero2w-img336.png]]

~~INFO: ----------------------------------------~~</div><div class="figure">

~~INFO~~[[File: ~~build lichee OK~~zero2w-img337.png]]

~~INFO: -----------------------------------~~</div></ol><ol start="5" style="list-style-type: decimal;"><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>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''adb install usbcamera.apk'''|}</ol><ol start="6" style="list-style-type: 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="37" style="list-style-type: decimal;"><li>Then ~~use the following command~~ double-click to ~~compile~~ open the ~~Android source code~~ USB camera APP and ~~generate~~ you can see the output video of the ~~final Android image~~USB camera.</li></ol> ~~test@test:~$ '''cd H618~~ == Android system ROOT description == ~~test@test~~{| class="wikitable" style="background-color:#ffffdc;width:~~~/H618~~800px;" |-~~Android12-Src$~~ | <big>'''~~source build/envsetup~~The Android system released by Orange Pi has been ROOT and can be tested using the following method.sh'''</big>|} ~~test@test:~/H618-Android12-Src$~~ # Download from the '''~~lunch apollo_p2-userdebug~~official tool''' ~~test@test:~/H618-Android12-Src$~~ on the development board data download page '''~~make -j8~~rootcheck.apk''' ~~test@test~~<div class="figure"> :~:[[File:zero2w-img336.png]] </~~H618~~div><div class="figure"> ::[[File:zero2w-~~Android12-Src$ '''pack'''~~img339.png]] </div><ol start="42" style="list-style-type: decimal;"><li>~~The storage path of~~ Then make sure that the adb connection between the Ubuntu PC and the ~~Android image generated by compilation~~ 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|'''~~longan/out/h618_android12_p2_uart0.img~~How to use ADB''']]".</li>~~</ol>~~ <~~span id="appendix"~~li><~~/span~~p>Then use the adb command to install rootcheck.apk into the Android system. Of course, you can also use a USB disk copy to install it.</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''adb install rootcheck.apk'''|}</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><ol start="5" style="list-style-type: decimal;"><li>The display interface after opening the '''ROOT 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 '''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> [[File:zero2w-img342.png]]</ol> == How to use MiracastReceiver to cast the mobile phone screen to the development board == <ol style="list-style-type: 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|'''the instructions in the WI-FI connection method.''']]</li><li>Then open the '''MiracastReceiver'''application in the Android system of the development board[[File:zero2w-img343.png]]</li><li>The interface after '''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 '''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> == Method of turning on and off the machine through buttons or infrared remote control == We can turn off or turn on the Android system of the development board through the power on/off button or infrared remote control. However, it should be noted that there is no power on/off button and infrared receiver on the main board of the development board, and it needs to be expanded through a 24pin expansion board. [[File:zero2w-img107.png]] The location of the power button on the 24pin expansion board is as shown in the figure below: [[File:zero2w-img269.png]] The location of the infrared remote control power button is as follows: [[File:zero2w-img349.png]] When shutting down, we need to press and hold the power button or the power button on the infrared remote control, and then the Android system will pop up the confirmation dialog box shown in the figure below, and then select '''OK''' to shut down the Android system. [[File:zero2w-img350.png]] After shutting down, press and hold the power button or the power button on the infrared remote control again to turn it on. == 40pin interface GPIO, UART, SPI test == {| 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>|} === 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 '''GPIO READALL''' button, and the output information is as shown below:</li> <div class="figure"> [[File:zero2w-img354.png]] </div></ol><ol start="5" style="list-style-type: decimal;"><li>There are a total of 28 GPIO ports available in the 40-pin development board. The following takes pin 12 - corresponding to GPIO PI01 - corresponding to wPi serial number 6 - as an example to demonstrate how to set the high and low levels of the GPIO port. First click the '''CheckBox''' button corresponding to pin 12. When the button is selected, pin 12 will be set to high level. After setting, you can use a multimeter to measure the value of the voltage of the pin. If it is '''3.3v''', it means the setting High level success.</li> [[File:zero2w-img355.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then click the '''GPIO READALL''' button and you can see that the current pin 12 mode is '''OUT''' and the pin level is high level.</li> [[File:zero2w-img356.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Click the '''CheckBox''' button in the picture below again to uncheck it, and pin 12 will be set to low level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is '''0v''', it means the low level setting is successful.</li> [[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: 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>The device node corresponding to uart2 is '''/dev/ttyAS2''', and the device node corresponding to uart5 is'''/dev/ttyAS5'''</li>{| class="wikitable" style="width:800px;" |-| 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.png]]</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 '''SEND''' 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 '''SEND''' 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: 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'''|}{| 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'''|}</div> <ol start="2" style="list-style-type: decimal;"><li>The device node corresponding to SPI1 CS0 is '''/dev/spidev1.0''', and the device node corresponding to SPI1 CS1 is '''/dev/spidev1.1'''</li>{| class="wikitable" style="width:800px;" |-| apollo-p2:/ # '''ls /dev/spidev1.*''' '''/dev/spidev1.0      /dev/spidev1.1'''|}</ol><ol start="3" style="list-style-type: decimal;"><li>Here is a demonstration to test the SPI1 interface through the '''w25qxx''' module. First, connect the w25qxx module to the 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.'''</big>|}</ol><ol start="4" style="list-style-type: decimal;"><li>Then open wiringOP APP on the desktop</li> [[File:zero2w-img351.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>Then click the '''SPI_TEST''' button to open the SPI test interface</li> [[File:zero2w-img365.png]]</ol><ol start="6" style="list-style-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/spidev1.1'''<div class="figure"> [[File:zero2w-img366.png]] </div></li><li>Then click the '''OPEN''' button to initialize the SPI</li> [[File:zero2w-img367.png]]</ol><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> [[File:zero2w-img368.png]]</ol><ol start="9" style="list-style-type: decimal;"><li>Finally, the APP will display the read ID information of the onboard SPI Flash.</li> [[File:zero2w-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> === 40pin I2C test method === # As can be seen from the table below, the Android12 TV system has i2c1 and i2c2 turned on by default. <div style="display: flex;">::{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''GPIO NO.'''| '''GPIO'''| '''Function'''| '''Pin'''|-| style="text-align: left;"|| style="text-align: left;"|| '''3.3V'''| '''1'''|-| '''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>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-*''' '''/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> [[File:zero2w-img351.png]]</ol><ol start="4" style="list-style-type: decimal;"><li>Then click the '''I2C_TEST''' button to open the i2c test interface</li> [[File:zero2w-img370.png]]</ol><ol start="5" style="list-style-type: decimal;"><li>The i2c test interface of wiringOP is shown in the figure below</li> [[File:zero2w-img371.png]]</ol><ol start="6" style="list-style-type: decimal;"><li>Then click the device node selection box in the upper left corner to select the i2c you want to test</li> [[File:zero2w-img372.png]]</ol><ol start="7" style="list-style-type: decimal;"><li>Then connect an i2c device to the 40pin i2c pin. Here we take the ds1307 rtc module as an example.</li> [[File:zero2w-img178.png]]</ol><ol start="8" style="list-style-type: decimal;"><li>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 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> === 40pin PWM test === # As can be seen from the table below, the available pwm are pwm1, pwm2, pwm3 and pwm4. <div style="display: flex;">::{| class="wikitable" style="width:390px;margin-right: 20px;text-align: center;"|-| '''GPIO NO.'''| '''GPIO'''| '''Function'''| '''Pin'''|-| style="text-align: left;"|| style="text-align: left;"|| '''3.3V'''| '''1'''|-| '''264'''| '''PI8'''| '''TWI1-SDA'''| '''3'''|-| '''263'''| '''PI7'''| '''TWI1-SCL'''| '''5'''|-| '''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 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 the 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 image download 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><ol start="3" style="list-style-type: decimal;"><li>Then use the following command to compile the Android source code and generate the final Android image</li>{| class="wikitable" style="width:800px;" |-| test@test:~$ '''cd H618-Android12-Src''' test@test:~/H618-Android12-Src$ '''source build/envsetup.sh''' test@test:~/H618-Android12-Src$ '''lunch apollo_p2-userdebug''' test@test:~/H618-Android12-Src$ '''make -j8''' test@test:~/H618-Android12-Src$ '''pack'''|}</ol><ol start="4" style="list-style-type: decimal;"><li>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

Changes

Orange Pi Zero 2W

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Products

FAQ

Images Resources

Support

Tools