Changes

Orange Pi 5 Plus

34,140 bytes removed, 15:13, 5 June 2023

no edit summary

'''Orange Pi 5~~''' '''~~Plus'''

'''User Manual'''

[[File:~~./images/~~media/image2.png|576x446px]]

'''目录'''

[[\l|1. Basic Features of Orange Pi 5 Plus [1](#basic-features-of-orange-pi-5-plus)]]

[[\l|1.1. What is Orange Pi 5 Plus [1](#what-is-orange-pi-5-plus)]]

[[\l|1.2. Purpose of Orange Pi 5 Plus [1](#purpose-of-orange-pi-5-plus)]]

[[\l|1.3. Hardware Specifications of Orange Pi 5 Plus [2](#hardware-specifications-of-orange-pi-5-plus)]]

[[\l|1.4. Top view and bottom view of Orange Pi 5 Plus [4](#_Toc6696)]]

[[\l|1.5. nterface details of Orange Pi 5 Plus [5](#nterface-details-of-orange-pi-5-plus)]]

[[\l|2. Introduction to the use of the development board [6](#introduction-to-the-use-of-the-development-board)]]

[[\l|2.1. Prepare the required accessories [6](#prepare-the-required-accessories)]]

[[\l|2.2. Download the image of the development board and related materials [14](#download-the-image-of-the-development-board-and-related-materials)]]

[[\l|2.3. Method of burning Linux image to TF card based on Windows PC [15](#method-of-burning-linux-image-to-tf-card-based-on-windows-pc)]]

[[\l|2.3.1. How to use balenaEtcher to burn Linux image [16](#how-to-use-balenaetcher-to-burn-linux-image)]]

[[\l|2.3.2. How to use RKDevTool to burn Linux image to TF card [21](#how-to-use-rkdevtool-to-burn-linux-image-to-tf-card)]]

[[\l|2.3.3. How to use Win32Diskimager to burn Linux image [29](#how-to-use-win32diskimager-to-burn-linux-image)]]

[[\l|2.4. Method of burning Linux image to TF card based on Ubuntu PC [32](#method-of-burning-linux-image-to-tf-card-based-on-ubuntu-pc)]]

[[\l|2.5. How to burn Linux image to eMMC [37](#_Toc20691)]]

[[\l|2.5.1. How to use RKDevTool to burn Linux image into eMMC [37](#how-to-use-rkdevtool-to-burn-linux-image-into-emmc)]]

[[\l|2.5.2. Using the dd command to burn the Linux image into eMMC [46](#using-the-dd-command-to-burn-the-linux-image-into-emmc)]]

[[\l|2.6. How to burn Linux image to SPIFlash+NVMe SSD [48](#how-to-burn-linux-image-to-spiflashnvme-ssd)]]

[[\l|2.6.1. The method of using the dd command to burn [48](#the-method-of-using-the-dd-command-to-burn)]]

[[\l|2.6.2. How to use balenaEtcher software to program [52](#how-to-use-balenaetcher-software-to-program)]]

[[\l|2.6.3. Using RKDevTool to burn [68](#using-rkdevtool-to-burn)]]

[[\l|2.7. How to burn OpenWRT image to SPI FLASH [77](#how-to-burn-openwrt-image-to-spi-flash)]]

[[\l|2.7.1. The method of using the dd command to burn [77](#the-method-of-using-the-dd-command-to-burn-1)]]

[[\l|2.7.2. Using RKDevTool to burn [78](#using-rkdevtool-to-burn-1)]]

[[\l|2.8. How to burn Android image to TF card [86](#how-to-burn-android-image-to-tf-card)]]

[[\l|2.9. How to burn Android image into eMMC [89](#how-to-burn-android-image-into-emmc)]]

[[\l|2.9.1. How to burn Android image into eMMC via Type-C cable [90](#how-to-burn-android-image-into-emmc-via-type-c-cable)]]

[[\l|2.9.2. How to burn Android 12 image into eMMC via TF card [95](#_Toc7343)]]

[[\l|2.10. How to burn Android image to SPIFlash+NVMe SSD [99](#how-to-burn-android-image-to-spiflashnvme-ssd)]]

[[\l|2.11. How to burn Orange Pi OS (Droid) image to TF card [104](#how-to-burn-orange-pi-os-droid-image-to-tf-card)]]

[[\l|2.12. How to burn Orange Pi OS (Droid) image into eMMC [107](#how-to-burn-orange-pi-os-droid-image-into-emmc)]]

[[\l|2.12.1. Burn Orange Pi OS (Droid) image toeMMC [107](#burn-orange-pi-os-droid-image-toemmc)]]

[[\l|2.12.2. Burn Orange Pi OS (Droid) image to eMMC via TF card [112](#burn-orange-pi-os-droid-image-to-emmc-via-tf-card)]]

[[\l|2.13. Burn Orange Pi OS (Droid) image to SPIFlash+NVMe SSD [117](#burn-orange-pi-os-droid-image-to-spiflashnvme-ssd)]]

[[\l|2.14. How to use RKDevTool to clear SPIFlash [122](#how-to-use-rkdevtool-to-clear-spiflash)]]

[[\l|2.15. Start the Orange Pi development board [129](#start-the-orange-pi-development-board)]]

[[\l|2.16. How to use the debugging serial port [130](#how-to-use-the-debugging-serial-port)]]

[[\l|2.16.1. Connection instruction of debugging serial port [130](#connection-instruction-of-debugging-serial-port)]]

[[\l|2.16.2. How to use the debugging serial port on the Ubuntu platform [132](#how-to-use-the-debugging-serial-port-on-the-ubuntu-platform)]]

[[\l|2.16.3. How to use the debugging serial port on Windows platform [135](#how-to-use-the-debugging-serial-port-on-windows-platform)]]

[[\l|3. Ubuntu/Debian Server and Xfce desktop system instructions [138](#ubuntudebian-server-and-xfce-desktop-system-instructions)]]

[[\l|3.1. Supported Ubuntu/Debian image types and kernel versions [138](#supported-ubuntudebian-image-types-and-kernel-versions)]]

[[\l|3.2. Linux system adaptation [139](#linux-system-adaptation)]]

[[\l|3.3. The format of linux commands in this manual [140](#the-format-of-linux-commands-in-this-manual)]]

[[\l|3.4. Linux system login instructions [142](#linux-system-login-instructions)]]

[[\l|3.4.1. Linux system default login account and password [142](#linux-system-default-login-account-and-password)]]

[[\l|3.4.2. How to set automatic terminal login in linux system [142](#how-to-set-automatic-terminal-login-in-linux-system)]]

[[\l|3.4.3. Instructions for automatic login of Linux desktop version system [143](#instructions-for-automatic-login-of-linux-desktop-version-system)]]

[[\l|3.4.4. The setting method of root user automatic login in Linux desktop version system [145](#the-setting-method-of-root-user-automatic-login-in-linux-desktop-version-system)]]

[[\l|3.4.5. The method of disabling the desktop in the Linux desktop version system [145](#the-method-of-disabling-the-desktop-in-the-linux-desktop-version-system)]]

[[\l|3.5. Onboard LED Light Test Instructions [146](#onboard-led-light-test-instructions)]]

[[\l|3.6. Network connection test [147](#network-connection-test)]]

[[\l|3.6.1. 2.5G Ethernet port test [147](#g-ethernet-port-test)]]

[[\l|3.6.2. WIFI connection test [149](#wifi-connection-test)]]

[[\l|3.6.3. How to set a static IP address [157](#how-to-set-a-static-ip-address)]]

[[\l|3.7. How to use E-Key PCIe WIFI6+Bluetooth module [165](#how-to-use-e-key-pcie-wifi6bluetooth-module)]]

[[\l|3.8. SSH remote login development board [167](#ssh-remote-login-development-board)]]

[[\l|3.8.1. SSH remote login development board under Ubuntu [167](#ssh-remote-login-development-board-under-ubuntu)]]

[[\l|3.8.2. SSH remote login development board under Windows [169](#ssh-remote-login-development-board-under-windows)]]

[[\l|3.9. How to use ADB [170](#how-to-use-adb)]]

[[\l|3.9.1. How to use network adb [170](#how-to-use-network-adb)]]

[[\l|3.9.2. adb3.9.2. Use type-c data cable to connect to adb [172](#adb3.9.2.-use-type-c-data-cable-to-connect-to-adb)]]

[[\l|3.10. The method of uploading files to the Linux system of the development board [175](#the-method-of-uploading-files-to-the-linux-system-of-the-development-board)]]

[[\l|3.10.1. How to upload files to the development board Linux system in Ubuntu PC [175](#how-to-upload-files-to-the-development-board-linux-system-in-ubuntu-pc)]]

[[\l|3.10.2. The method of uploading files to the development board Linux system in Windows PC [178](#the-method-of-uploading-files-to-the-development-board-linux-system-in-windows-pc)]]

[[\l|3.11. HDMI test [183](#hdmi-test)]]

[[\l|3.11.1. HDMI test [183](#hdmi-test-1)]]

[[\l|3.11.2. HDMI IN test method [185](#hdmi-in-test-method)]]

[[\l|3.11.3. HDMI to VGA display test [188](#hdmi-to-vga-display-test)]]

[[\l|3.11.4. HDMI resolution setting method [189](#hdmi-resolution-setting-method)]]

[[\l|3.12. How to use Bluetooth [192](#how-to-use-bluetooth)]]

[[\l|3.12.1. Test method of desktop image [192](#test-method-of-desktop-image-1)]]

[[\l|3.13. USB interface test [195](#usb-interface-test)]]

[[\l|3.13.1. Connect USB mouse or keyboard to test [195](#connect-usb-mouse-or-keyboard-to-test)]]

[[\l|3.13.2. Connect USB storage device test [195](#connect-usb-storage-device-test)]]

[[\l|3.13.3. USB wireless network card test [196](#usb-wireless-network-card-test)]]

[[\l|3.13.4. USB camera test [201](#usb-camera-test)]]

[[\l|3.14. Audio Test [203](#audio-test)]]

[[\l|3.14.1. Testing audio methods on desktop systems [203](#testing-audio-methods-on-desktop-systems)]]

[[\l|3.14.2. The method of using commands to play audio [205](#the-method-of-using-commands-to-play-audio)]]

[[\l|3.14.3. Method of using commands to test recording [208](#method-of-using-commands-to-test-recording)]]

[[\l|3.15. Temperature sensor [208](#temperature-sensor)]]

[[\l|3.16. 40 Pin Expansion Interface Pin Instructions [210](#pin-expansion-interface-pin-instructions)]]

[[\l|3.17. How to install wiringOP [212](#how-to-install-wiringop)]]

[[\l|3.18. 40 pin interface GPIO, I2C, UART, SPI, CAN and PWM test [214](#pin-interface-gpio-i2c-uart-spi-can-and-pwm-test)]]

[[\l|3.18.1. 40 pin GPIO port test [214](#pin-gpio-port-test)]]

[[\l|3.18.2. How to set the pull-down resistance of pin GPIO port [216](#how-to-set-the-pull-down-resistance-of-pin-gpio-port)]]

[[\l|3.18.3. 40 pin SPI test [217](#pin-spi-test)]]

[[\l|3.18.4. 40 pin I2C test [220](#_Toc18432)]]

[[\l|3.18.5. 40 pin UART test [223](#pin-uart-test)]]

[[\l|3.18.6. PWM test method [225](#pwm-test-method)]]

[[\l|3.18.7. CAN test method [230](#can-test-method)]]

[[\l|3.19. How to install and use wiringOP-Python [237](#how-to-install-and-use-wiringop-python)]]

[[\l|3.19.1. How to install wiringOP-Python [237](#how-to-install-wiringop-python)]]

[[\l|3.19.2. 40 pin GPIO port test [240](#pin-gpio-port-test-1)]]

[[\l|3.19.3. 40 pin SPI test [242](#pin-spi-test-1)]]

[[\l|3.19.4. 40 pin I2C test [246](#pin-i2c-test-1)]]

[[\l|3.19.5. 40 pin UART test [249](#pin-uart-test-1)]]

[[\l|3.20. Hardware watchdog test [251](#hardware-watchdog-test)]]

[[\l|3.21. Check the serial number of RK3588 chip [252](#check-the-serial-number-of-rk3588-chip)]]

[[\l|3.22. How to install Docker [252](#how-to-install-docker)]]

[[\l|3.23. How to download and install arm64 version balenaEtcher [253](#how-to-download-and-install-arm64-version-balenaetcher)]]

[[\l|3.24. The installation method of the pagoda linux panel [255](#the-installation-method-of-the-pagoda-linux-panel)]]

[[\l|3.25. Set the Chinese environment and install Chinese input method [261](#set-the-chinese-environment-and-install-chinese-input-method)]]

[[\l|3.25.1. Debian 11 system installation method [261](#debian-11-system-installation-method)]]

[[\l|3.25.2. ubuntu 20.04 system installation method [267](#ubuntu-20.04-system-installation-method)]]

[[\l|3.25.3. Ubuntu 22.04 installation method [271](#ubuntu-22.04-installation-method)]]

[[\l|3.26. How to remotely log in to the Linux system desktop method [277](#how-to-remotely-log-in-to-the-linux-system-desktop-method)]]

[[\l|3.26.1. Use NoMachine remote login [277](#use-nomachine-remote-login)]]

[[\l|3.26.2. Use VNC remote login [281](#use-vnc-remote-login)]]

[[\l|3.27. Some programming language test supported by thelinux system [283](#some-programming-language-test-supported-by-thelinux-system)]]

[[\l|3.27.1. Debian Bullseye system [283](#debian-bullseye-system)]]

[[\l|3.27.2. Ubuntu Focal system [285](#ubuntu-focal-system)]]

[[\l|3.27.3. Ubuntu Jammy system [286](#ubuntu-jammy-system)]]

[[\l|3.28. QT installation method [288](#qt-installation-method)]]

[[\l|3.29. ROS installation method [296](#ros-installation-method)]]

[[\l|3.29.1. Ubuntu 20.04 method of installing ROS 1 Noetic [296](#ubuntu-20.04-method-of-installing-ros-1-noetic)]]

[[\l|3.29.2. Ubuntu20.04 The method of installing ROS 2 Galactic [300](#ubuntu20.04-the-method-of-installing-ros-2-galactic)]]

[[\l|3.29.3. Ubuntu22.04 to install ROS 2 Humble [303](#ubuntu22.04-to-install-ros-2-humble)]]

[[\l|3.30. The method of installing the kernel header file [305](#the-method-of-installing-the-kernel-header-file)]]

[[\l|3.31. How to use 10.1 inch MIPI LCD screen [308](#how-to-use-10.1-inch-mipi-lcd-screen)]]

[[\l|3.31.1. 10.1 -inch MIPI screen assembly method [308](#inch-mipi-screen-assembly-method)]]

[[\l|3.31.2. Open the 10.1 -inch MIPI LCD screen configuration [310](#open-the-10.1–inch-mipi-lcd-screen-configuration)]]

[[\l|3.31.3. The server version of the image rotation display direction method [312](#the-server-version-of-the-image-rotation-display-direction-method)]]

[[\l|3.31.4. The desktop image rotation display and touch direction method [313](#the-desktop-image-rotation-display-and-touch-direction-method)]]

[[\l|3.32. Instructions for opening the logo use instructions [315](#instructions-for-opening-the-logo-use-instructions)]]

[[\l|3.33. Test methods for OV13850 and OV13855 MIPI camera [316](#test-methods-for-ov13850-and-ov13855-mipi-camera)]]

[[\l|3.34. Test method for infrared receiving [320](#test-method-for-infrared-receiving)]]

[[\l|3.35. The method to use RTC [323](#the-method-to-use-rtc)]]

[[\l|3.36. How to use the cooling PWM fan [324](#how-to-use-the-cooling-pwm-fan)]]

[[\l|3.37. The method of shutting down and restarting the development board [326](#the-method-of-shutting-down-and-restarting-the-development-board)]]

[[\l|4. Ubuntu22.04 Gnome Wayland Desktop system instructions [327](#ubuntu22.04-gnome-wayland-desktop-system-instructions)]]

[[\l|4.1. Ubuntu22.04 GNOME desktop system adaptation situation [328](#ubuntu22.04-gnome-desktop-system-adaptation-situation)]]

[[\l|4.2. Confirm that the current window system used by the system is Wayland [330](#confirm-that-the-current-window-system-used-by-the-system-is-wayland)]]

[[\l|4.3. Switch the method of default audio equipment [331](#switch-the-method-of-default-audio-equipment)]]

[[\l|4.4. GPU test method [332](#gpu-test-method)]]

[[\l|4.5. Chromium browser hard solution to play video test method [334](#chromium-browser-hard-solution-to-play-video-test-method)]]

[[\l|4.6. Kodi hard solution to play video test method [336](#kodi-hard-solution-to-play-video-test-method)]]

[[\l|4.7. Ubuntu22.04 Gnome to install ROS 2 Humble [344](#_Toc26708)]]

[[\l|4.8. Set the Chinese environment and the method of installing the Chinese input method [346](#set-the-chinese-environment-and-the-method-of-installing-the-chinese-input-method)]]

[[\l|5. Orange Pi OS Arch system use instructions [353](#orange-pi-os-arch-system-use-instructions)]]

[[\l|5.1. Orange Pi OS Arch system adaptation situation [353](#orange-pi-os-arch-system-adaptation-situation)]]

[[\l|5.2. How to use the M.2 E-Key PCIE WIFI6+Bluetooth module [355](#how-to-use-the-m.2-e-key-pcie-wifi6bluetooth-module)]]

[[\l|5.3. How to use 10.1 inch MIPI LCD screen [362](#how-to-use-10.1-inch-mipi-lcd-screen-1)]]

[[\l|5.3.1. 10.1 -inch MIPI screen assembly method [362](#inch-mipi-screen-assembly-method-1)]]

[[\l|5.3.2. How to open 10.1 -inch MIPI LCD screen configuration [365](#how-to-open-10.1–inch-mipi-lcd-screen-configuration)]]

[[\l|5.3.3. Method of rotating display and touch direction [366](#method-of-rotating-display-and-touch-direction)]]

[[\l|5.4. OV13850 and OV13855 MIPI test methods for testing [369](#ov13850-and-ov13855-mipi-test-methods-for-testing)]]

[[\l|5.5. Set the Chinese environment and the method of installing the Chinese input method [371](#set-the-chinese-environment-and-the-method-of-installing-the-chinese-input-method-1)]]

[[\l|5.6. HDMI IN test method [377](#hdmi-in-test-method-1)]]

[[\l|5.7. How to install wiringOP [380](#how-to-install-wiringop-1)]]

[[\l|5.8. 40 PIN interface GPIO, I2C, UART, SPI, CAN and PWM test [382](#pin-interface-gpio-i2c-uart-spi-can-and-pwm-test-1)]]

[[\l|5.8.1. 40 PIN GPIO port test [383](#pin-gpio-port-test-2)]]

[[\l|5.8.2. 40 PIN GPIO Port -to -Plattering resistance setting method [383](#pin-gpio-port–to–plattering-resistance-setting-method)]]

[[\l|5.8.3. 40 PIN SPI test [384](#pin-spi-test-2)]]

[[\l|5.8.4. 40 pin I2C test [387](#pin-i2c-test-2)]]

[[\l|5.8.5. 40 Pin's UART test [388](#pins-uart-test)]]

[[\l|5.8.6. PWM test method [390](#pwm-test-method-1)]]

[[\l|5.8.7. CAN's test method [393](#cans-test-method)]]

[[\l|6. Linux SDK——orangepi-build instructions [396](#linux-sdkorangepi-build-instructions)]]

[[\l|6.1. Compilation system requirements [396](#compilation-system-requirements)]]

[[\l|6.1.1. Compile with the Ubuntu22.04 system of the development board [396](#compile-with-the-ubuntu22.04-system-of-the-development-board)]]

[[\l|6.1.2. Compile with x64 Ubuntu22.04 computer [396](#compile-with-x64-ubuntu22.04-computer)]]

[[\l|6.2. Get the source code of linux sdk [399](#get-the-source-code-of-linux-sdk)]]

[[\l|6.2.1. Download orangepi-build from github [399](#download-orangepi-build-from-github)]]

[[\l|6.2.2. Download the cross-compilation toolchain [401](#download-the-cross-compilation-toolchain)]]

[[\l|6.2.3. orangepi-build complete directory structure description [402](#orangepi-build-complete-directory-structure-description)]]

[[\l|6.3. Compile u-boot [403](#compile-u-boot)]]

[[\l|6.4. Compile the linux kernel [407](#_Toc31297)]]

[[\l|6.5. Compile rootfs [413](#_Toc25559)]]

[[\l|6.6. Compile linux image [416](#compile-linux-image)]]

[[\l|7. Linux Development Manual [420](#linux-development-manual)]]

[[\l|7.1. The method of compiling the kernel source code separately in the linux system of the development board [420](#the-method-of-compiling-the-kernel-source-code-separately-in-the-linux-system-of-the-development-board)]]

[[\l|8. OpenWRT system instructions [422](#openwrt-system-instructions)]]

[[\l|8.1. OpenWRT version [422](#openwrt-version)]]

[[\l|8.2. OpenWRT Adaptation [423](#openwrt-adaptation)]]

[[\l|8.3. The first start to expand rootfs [423](#the-first-start-to-expand-rootfs)]]

[[\l|8.4. How to log in to the system [424](#how-to-log-in-to-the-system)]]

[[\l|8.4.1. Login via serial port [424](#login-via-serial-port)]]

[[\l|8.4.2. Log in to the system via SSH [424](#log-in-to-the-system-via-ssh)]]

[[\l|8.4.3. Log in to the LuCI management interface [425](#log-in-to-the-luci-management-interface)]]

[[\l|8.4.4. Log in to the terminal through the LuCI management interface [426](#log-in-to-the-terminal-through-the-luci-management-interface)]]

[[\l|8.4.5. Use IP address + port number to log in to the terminal [429](#use-ip-address-port-number-to-log-in-to-the-terminal)]]

[[\l|8.5. How to modify the IP address of the LAN port through the command line [430](#how-to-modify-the-ip-address-of-the-lan-port-through-the-command-line)]]

[[\l|8.6. How to modify the root password [431](#how-to-modify-the-root-password)]]

[[\l|8.6.1. Modify via command line [431](#modify-via-command-line)]]

[[\l|8.6.2. Modify through the LuCI management interface [432](#modify-through-the-luci-management-interface)]]

[[\l|8.7. USB interface test [433](#usb-interface-test-1)]]

[[\l|8.7.1. Mount the USB storage device under the command line [433](#mount-the-usb-storage-device-under-the-command-line)]]

[[\l|8.7.2. Mount the USB storage device on the LuCI management interface [434](#mount-the-usb-storage-device-on-the-luci-management-interface)]]

[[\l|8.8. How to use E-Key PCIe wireless network card [438](#how-to-use-e-key-pcie-wireless-network-card)]]

[[\l|8.8.1. How to create WIFI hotspot [438](#how-to-create-wifi-hotspot)]]

[[\l|8.8.2. How to connect to WIFI hotspot [443](#how-to-connect-to-wifi-hotspot)]]

[[\l|8.9. Installing packages via the command line [447](#installing-packages-via-the-command-line)]]

[[\l|8.9.1. Install via opkg in the terminal [447](#install-via-opkg-in-the-terminal)]]

[[\l|8.10. OpenWRT management interface installation software package [447](#openwrt-management-interface-installation-software-package)]]

[[\l|8.10.1. View the list of available software packages in the system [448](#view-the-list-of-available-software-packages-in-the-system)]]

[[\l|8.10.2. Example of installing software packages [449](#example-of-installing-software-packages)]]

[[\l|8.10.3. Remove package example [451](#remove-package-example)]]

[[\l|8.11. Using Samba Network Shares [453](#using-samba-network-shares)]]

[[\l|8.12. Zerotier Instructions [457](#zerotier-instructions)]]

[[\l|9. Compilation method of OpenWRT source code [460](#compilation-method-of-openwrt-source-code)]]

[[\l|9.1. Download OpenWRT source code [460](#download-openwrt-source-code)]]

[[\l|9.2. Compile OpenWRT source code [460](#compile-openwrt-source-code)]]

[[\l|10. Instructions for using the Android 12 system [462](#instructions-for-using-the-android-12-system)]]

[[\l|10.1. Supported Android versions [462](#supported-android-versions)]]

[[\l|10.2. Android function adaptation [462](#android-function-adaptation)]]

[[\l|10.3. How to use the USB wireless network card [464](#how-to-use-the-usb-wireless-network-card)]]

[[\l|10.4. M.2 How to use E-Key PCIe WIFI6+Bluetooth module [465](#m.2-how-to-use-e-key-pcie-wifi6bluetooth-module)]]

[[\l|10.5. WIFI connection test method [466](#wifi-connection-test-method)]]

[[\l|10.6. How to use Wi-Fi hotspot [468](#how-to-use-wi-fi-hotspot)]]

[[\l|10.7. Bluetooth test method [471](#bluetooth-test-method)]]

[[\l|10.8. Test method of HDMI In [474](#test-method-of-hdmi-in)]]

[[\l|10.9. How to use 10.9.10.1 inch MIPI screen [476](#how-to-use-10.9.10.1-inch-mipi-screen)]]

[[\l|10.10. OV13850 and OV13855 MIPI camera test method [477](#ov13850-and-ov13855-mipi-camera-test-method)]]

[[\l|10.11. 26pin interface GPIO, UART, SPI and PWM test [481](#pin-interface-gpio-uart-spi-and-pwm-test)]]

[[\l|10.11.1. 40pin GPIO port test [481](#pin-gpio-port-test-3)]]

[[\l|10.11.2. 40pin UART test [485](#pin-uart-test-2)]]

[[\l|10.11.3. 26pin SPI test [488](#pin-spi-test-3)]]

[[\l|10.11.4. 26pin PWM test [490](#pin-pwm-test)]]

[[\l|10.12. How to use ADB [493](#how-to-use-adb-1)]]

[[\l|10.12.1. Use the data cable to connect to adb debugging [493](#use-the-data-cable-to-connect-to-adb-debugging)]]

[[\l|10.12.2. Use network connection adb debugging [494](#use-network-connection-adb-debugging)]]

[[\l|10.13. 2.4G USB remote control tested by Android Box [495](#g-usb-remote-control-tested-by-android-box)]]

[[\l|10.14. How to use the infrared remote control of the Android Box system [496](#how-to-use-the-infrared-remote-control-of-the-android-box-system)]]

[[\l|10.15. How to use HDMI CEC function in Android Box system [497](#how-to-use-hdmi-cec-function-in-android-box-system)]]

[[\l|11. How to compile Android 12 source code [499](#how-to-compile-android-12-source-code)]]

[[\l|11.1. Download Android 12 source code [499](#download-android-12-source-code)]]

[[\l|11.2. Compile the source code of Android 12 [499](#compile-the-source-code-of-android-12)]]

[[\l|12. Instructions for using the Orange Pi OS Droid system [502](#instructions-for-using-the-orange-pi-os-droid-system)]]

[[\l|12.1. Function adaptation of OPi OS Droid system [502](#function-adaptation-of-opi-os-droid-system)]]

[[\l|12.2. Test method of HDMI In [503](#test-method-of-hdmi-in-1)]]

[[\l|13. Appendix [505](#appendix)]]

[[\l|13.1. User Manual Update History [505](#user-manual-update-history)]]

[[\l|13.2. Image update history [506](#image-update-history)]]

'''Of course, there are more functions. Relying on a strong ecosystem and a variety of expansion accessories, OPi 5 Plus can help users easily realize the delivery from idea to prototype to mass production. It is a maker, dreamer, amateur The ideal creative platform for enthusiasts.'''

~~~~

~~= =~~

~~~~

~~== ==~~

~~~~

~~== ==~~

*

| 86.5g

|-

| ! [[~~./images/~~media%20/image3.png|橙子LOGO-透明 (6)]]{w idth=“0.269444 44444444443in” hei ght=“0.3152777 7777777777in”}

'''rangePi™''' '''is a registered trademark of Shenzhen Xunlong Software Co., Ltd.'''

|

|}

~~~~

~~== ==~~

~~~~

~~== ==~~

~~-----~~

[[File:media/image4.jpeg|486x342px|Orange-Pi-5-PLUS-1]]

</div>

[[File:~~./images/~~media/image5.jpeg|495x329px|Orange-Pi-5-PLUS-2]]

</div>

~~~~

~~== ==~~

== nterface details of Orange Pi 5 Plus ==

[[File:~~./images/~~media/image6.png|600x553px]][[File:~~./images/~~media/image7.jpeg|576x483px|未标题-1]]

== ==~~ ~~

== ==

# TF card, a class 10 or above high-speed SanDisk card with a minimum capacity of 16GB (32GB or above is recommended)

[[File:~~./images/~~media/~~image9~~image8.png|124x96px]]

<li>TF card reader, used to burn the image into the TF card</li></ol>

[[File:~~./images/~~media/~~image10~~image9.png|139x106px]]

<li>Display with HDMI interface</li></ol>

[[File:~~./images/~~media/~~image11~~image10.png|313x205px]]

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

[[File:~~./images/~~media/~~image12~~image11.png|199x129px]]

'''\Note, if you want to connect a 4K or 8K display, please make sure that the HDMI cable supports 4K or 8K video display.'''

[[File:~~./images/~~media/~~image13~~image12.jpeg|243x166px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image14~~image13.jpeg|245x166px|98F5D70E2C9B3673E8ECE4B8ABDDFD80]]

</div>

[[File:~~./images/~~media/~~image15~~image14.jpeg|223x203px|IMG_7546]]

</div>

<li>Power adapter, Orange Pi 5 Plus is recommended to use 5V/4A Type-C power supply for power supply</li></ol>

[[File:~~./images/~~media/~~image16~~image15.png|274x194px]]

'''There are two Type-C ports that look the same on the development board. The one next to the network port is the power port, and the other Type-C port has no power supply function. Please don’t connect it wrong.'''

[[File:~~./images/~~media/~~image17~~image16.jpeg|269x240px|01]]

</div>

<li>The mouse and keyboard of the USB interface, as long as the mouse and keyboard of the standard USB interface are acceptable, the mouse and keyboard can be used to control the Orange Pi development board</li></ol>

[[File:~~./images/~~media/~~image18~~image17.png|311x264px]]

<li>USB camera</li></ol>

[[File:~~./images/~~media/~~image19~~image18.png|331x191px]]

'''The fan on the development board can adjust the speed and switch through PWM.'''

[[File:~~./images/~~media/~~image20~~image19.png|410x171px]]

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

[[File:~~./images/~~media/~~image21~~image20.png|143x112px]]

<li>The data cable of the Type-C interface, used for burning images, using ADB and other functions</li></ol>

[[File:~~./images/~~media/~~image22~~image21.png|143x113px]]

<li>Infrared remote control</li></ol>

[[File:~~./images/~~media/~~image23~~image22.png|170x173px]]

'''Note that the remote control of the air conditioner or the TV cannot control the Orange Pi development board. The operating system provided by Orange Pi can only ensure that the remote control provided by Orange Pi can be used by default.'''

<li>OV13850 camera with 13 million MIPI interface (common with OPi5/OPi5B)

[[File:~~./images/~~media/~~image24~~image23.png|268x151px]]</li>

<li>OV13855 camera with 13 million MIPI interface (common with OPi5/OPi5B)

[[File:~~./images/~~media/~~image25~~image24.png|253x150px]]</li>

<li>M.2 M-KEY 2280 specification NVMe SSD solid state drive, PCIe interface specification is PCIe3.0x4</li></ol>

<blockquote>[[File:~~./images/~~media/~~image26~~image25.png|358x104px]]

</blockquote>

'''The position where the eMMC module is inserted on the development board is shown in the figure below:'''

[[File:~~./images/~~media/~~image27~~image26.png|317x144px]]

<li>RTC battery, the interface is 2pin, 1.25mm pitch

[[File:~~./images/~~media/~~image28~~image27.png|250x134px]]</li></ol>

'''The location of the RTC battery interface on the development board is shown in the figure below:'''

[[File:~~./images/~~media/~~image29~~image28.png|344x126px]]

<li>Horn, the interface is 2pin, 1.25mm pitch</li></ol>

[[File:~~./images/~~media/~~image30~~image29.png|200x138px]]

'''The interface position of the speaker on the development board is shown in the figure below:'''

[[File:~~./images/~~media/~~image31~~image30.png|312x158px]]

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

[[File:~~./images/~~media/~~image32~~image31.png|217x89px|G7U7JZX(V`L$`A6864]38$P]] [[File:~~./images/~~media/~~image33~~image32.png|305x110px]]

| style="text-align: left;"| For burning Android and Linux images

|}

~~~~

~~= =~~

~~~~

~~== ==~~

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

~~<li></li>~~

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

~~-----~~

'''http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html'''

[[File:~~./images/~~media/~~image38~~image33.png|361x300px]]

<li>'''OpenWRT source code:''' saved on Github</li>

<li>'''Android image:''' saved on Google Cloud Disk</li>

<li>'''Ubuntu~~''' '''~~image'''：saved on Google Cloud Disk</li><li>'''Debian~~''' '''~~image'''：saved on Google Cloud Disk</li><li>'''Orange Pi OS~~''' '''~~image'''：saved on Google Cloud Disk</li><li>'''OpenWRT~~''' '''~~image'''：saved on Google Cloud Disk</li></ol>

</li></ol>

# Download the Linux operating system image file compression package that you want to burn from the '''Orange Pi data download page''', and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system. The size is generally above 2GB.

'''Note, if you download the OpenWRT image, you will see the following two types of images in the download link of the OpenWRT image, please download the image file in the~~''' '''~~"TF card, eMMC and NVME SSD boot image"~~''' '''~~folder.'''

[[File:~~./images/~~media/~~image39~~image34.png|277x88px]]

<li>Then download the burning software of Linux image——'''balenaEtcher,''' the download address is:</li></ol>

[https://www.balena.io/etcher/ '''https://www.balena.io/etcher/''']

<li>After entering the balenaEtcher download page, click the green download button to jump to the place where the software is downloaded</~~li></ol>~~ ~~== ==~~ ~~<ol start="3" style="list-style-type: decimal;"><li></li><li></li><li><ol style="list-style-type: lower-alpha;"~~p>~~<li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol></li></ol>~~ ~~== ==~~ ~~=== ===~~ ~~<ol start="6" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li>~~[[File:~~./images/~~media/~~image42~~image35.png|575x276px]]</li>

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

[[File:~~./images/~~media/~~image43~~image36.png|576x213px]]

<li>If the downloaded version of balenaEtcher needs to be installed, please install it before using it. If you downloaded the Portable version of balenaEtcher, just double-click to open it. The balenaEtcher interface after opening is shown in the figure below:</li></ol>

[[File:~~./images/~~media/~~image44~~image37.png|483x304px]]

'''When opening balenaEtcher, if the following error is prompted:'''

[[File:~~./images/~~media/~~image45~~image38.png|261x205px]]

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

[[File:~~./images/~~media/~~image46~~image39.png|300x104px|图形用户界面, 文本, 应用程序描述已自动生成]]

</div>

<li>The specific steps to use balenaEtcher to burn the Linux image are as follows</li></ol>

[[File:~~./images/~~media/~~image47~~image40.png|501x281px|03]]

</div>

<li>The interface displayed in the process of burning the Linux image by balenaEtcher is shown in the figure below, and the progress bar displays purple, indicating that the Linux image is being burned into the TF card.</li></ol>

[[File:~~./images/~~media/~~image48~~image41.png|506x317px]]

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

[[File:~~./images/~~media/~~image49~~image42.png|519x325px]]

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

[[File:~~./images/~~media/~~image50~~image43.png|523x324px]]

# First, you need to prepare a data cable with a good quality Type-C interface

[[File:~~./images/~~media/~~image22~~image21.png|193x196px]]

<li>Then insert the TF card into the card slot of the development board</li></ol>

[[File:~~./images/~~media/~~image53~~image44.png|300x87px]]

</li></ol>

[[File:~~./images/~~media/~~image54~~image45.png|382x97px]]

<li>Then download all the files below</li></ol>

[[File:~~./images/~~media/~~image55~~image46.png|392x145px]]

'''Note that the~~''' '''~~"MiniLoader-things needed to burn the Linux image"~~''' '''~~folder is hereinafter referred to as the MiniLoader folder.'''

<li>Then download the Linux operating system image file compression package that you want to burn from the '''Orange Pi data download page''', and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system , the size is generally more than 2GB</li></ol>

'''Note, if you download the OpenWRT image, you will see the following two types of images in the download link of the OpenWRT image, please download the image file in the~~''' '''~~"TF card, eMMC and NVME SSD boot image"~~''' '''~~folder.'''

[[File:~~./images/~~media/~~image39~~image34.png|301x95px]]

<li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image57~~image47.png|575x169px]]

</li></ol>

[[File:~~./images/~~media/~~image58~~image48.png|300x157px]]

<li>After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button.</li></ol>

[[File:~~./images/~~media/~~image59~~image49.png|429x223px]]

<li>Then decompress '''RKDevTool_Release_v2.96.zipRKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image60~~image50.png|575x170px]]

<li>After opening the '''RKDevTool''' burning tool, because the computer has not been connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li></ol>

[[File:~~./images/~~media/~~image61~~image51.png|402x189px]]

[[File:~~./images/~~media/~~image63~~image52.jpeg|400x113px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-2.jpg未标题-2]]

</div>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below：</li></ol>

[[File:~~./images/~~media/~~image64~~image53.png|382x93px]]

<li>Finally, connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button. The location of the Type-C power interface is as follows：</li></ol>

[[File:~~./images/~~media/~~image65~~image54.png|404x123px]]

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li></ol>

[[File:~~./images/~~media/~~image66~~image55.png|457x215px]]

[[File:~~./images/~~media/~~image68~~image56.png|455x216px|图片1]]

</div>

<li>Then click the right mouse button and the selection interface shown in the figure below will pop up</li></ol>

[[File:~~./images/~~media/~~image70~~image57.png|453x213px]]

<li>Then select the '''import configuration''' option</li></ol>

[[File:~~./images/~~media/~~image72~~image58.png|458x215px]]

<li>Then select the '''rk3588_linux_tfcard.cfg''' configuration file in the '''MiniLoader''' folder downloaded earlier, and click '''Open'''</li></ol>

[[File:~~./images/~~media/~~image74~~image59.png|483x227px]]

<li>Then click '''OK'''</li></ol>

[[File:~~./images/~~media/~~image76~~image60.png|483x227px]]

<li>Then click the position shown in the figure below</li></ol>

[[File:~~./images/~~media/~~image78~~image61.png|486x228px]]

<li>Then select '''MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and then click to '''open'''</li></ol>

[[File:~~./images/~~media/~~image80~~image62.png|492x231px]]

<li>Then click the position shown in the figure below</li></ol>

[[File:~~./images/~~media/~~image82~~image63.png|493x232px]]

'''Before burning the image, it is recommended to rename the linux image to be burned to orangepi.img or other shorter names, so that you can see the percentage value of the burning progress when burning the image.'''

[[File:~~./images/~~media/~~image84~~image64.png|499x234px]]

<li>Then please check the '''option to force writing by address'''</li></ol>

[[File:~~./images/~~media/~~image86~~image65.png|489x230px]]

<li>Then click the execute button to start burning the linux image to the tf card of the development board</li></ol>

[[File:~~./images/~~media/~~image88~~image66.png|492x231px]]

[[File:~~./images/~~media/~~image91~~image67.png|492x231px|%O4~FPPAT$0RH{3S~CGJ@@Q(1)]]

</div>

<li>After burning the linux image to the TF card, the linux system will start automatically.</li></ol>

~~~~

~~=== ===~~

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

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

~~<li></li>~~

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

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

</li></ol>

[https://www.sdcard.org/downloads/formatter/eula_windows/SDCardFormatterv5_WinEN.zip '''https://www.sdcard.org/downloads/formatter/eula_windows/SDCardFormatterv5_WinEN.zip''']

[[File:~~./images/~~media/~~image96~~image68.png|209x228px|选区_199]]

</div>

<li>Then click "'''Format'''", a warning box will pop up before formatting, and formatting will start after selecting "'''Yes (Y)'''"</li></ol>

[[File:~~./images/~~media/~~image97~~image69.png|304x147px]]

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

<blockquote>[[File:~~./images/~~media/~~image98~~image70.png|186x149px]]

</blockquote>

<li>Download the image file compression package of the Linux operating system that you want to burn from the '''Orange Pi data download page''', and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system. The size is generally more than 2GB</li></ol>

'''Note, if you download the OpenWRT image, you will see the following two types of images in the download link of the OpenWRT image, please download the image file in the~~''' '''~~"TF card, eMMC and NVME SSD boot image"~~''' '''~~folder.'''

[[File:~~./images/~~media/~~image39~~image34.png|309x98px]]

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

[http://sourceforge.net/projects/win32diskimager/files/Archive/ '''http://sourceforge.net/projects/win32diskimager/files/Archive/''']

[[File:~~./images/~~media/~~image99~~image71.png|297x206px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\a8fda8737c5b0b3b38fbb75ef68acfc.pnga8fda8737c5b0b3b38fbb75ef68acfc]]

</div>

<li>After the image writing is completed, click the "'''Exit'''" button > to exit, and then you

can pull out the TF card and insert it into the development board to start</li></ol>

~~~~

~~=== ===~~

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

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

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

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

# Download the balenaEtcher software, the download address is

[https://www.balena.io/etcher/ '''https://www.balena.io/etcher/''']

<li>After entering the balenaEtcher download page, click the green download button to jump to the place where the software is downloaded</li></ol>

[[File:~~./images/~~media/~~image42~~image35.png|575x276px]]

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

[[File:~~./images/~~media/~~image101~~image72.png|575x218px]]

<li>Download the Linux operating system image file compression package that you want to burn from the '''Orange Pi data download page,''' and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system. The size is generally more than 2GB</li></ol>

'''Note, if you download the OpenWRT image, you will see the following two types of images in the download link of the OpenWRT image, please download the image file in the~~''' '''~~"TF card, eMMC and NVME SSD boot image"~~''' '''~~folder.'''

[[File:~~./images/~~media/~~image102~~image73.png|275x87px|e6986fc9c8fc078e8cb6a9c39b76fb8]]

</div>

test@test:~$ '''7z x orangepi5plus_1.0.0_debian_bullseye_desktop_xfce_linux5.10.110.7z'''

test@test:~$ '''ls~~''' '''~~orangepi5plus_1.0.0_debian_bullseye_desktop_xfce_linux5.10.110.*'''

orangepi5plus_1.0.0_debian_bullseye_desktop_xfce_linux5.10.110.7z orangepi5plus_1.0.0_debian_bullseye_desktop_xfce_linux5.10.110.sha # checksum file

If you download the OpenWRT image, the compressed package ends with gz, and the decompression command is as follows：

test@test:~$ '''gunzip~~''' '''~~openwrt-aarch64-opi5plus-23.05-linux-5.10.110-ext4.img.gz'''

test@test:~$ '''ls openwrt-aarch64-opi5plus-23.05-linux-5.10.110-ext4.img'''

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

[[File:~~./images/~~media/~~image103~~image74.png|423x251px]]

[[File:~~./images/~~media/~~image47~~image40.png|501x281px|03]]

</div>

<li>The interface displayed in the process of burning the Linux image by balenaEtcher is shown in the figure below, and the progress bar displays purple, indicating that the Linux image is being burned into the TF card</li></ol>

[[File:~~./images/~~media/~~image104~~image75.png|576x247px]]

<li>The interface displayed in the process of burning the Linux image by balenaEtcher is shown in the figure below, and the progress bar displays purple, indicating that the Linux image is being burned into the TF card</li></ol>

[[File:~~./images/~~media/~~image105~~image76.png|576x252px]]

<ol start="1813" style="list-style-type: decimal;"><li>After successful burning, the display interface of balenaEtcher is as shown in the figure below. If a green indicator icon is displayed, it means that the image burning is successful. At this time, you can exit balenaEtcher, and then pull out the TF card and insert it into the TF card slot of the development board for use.</~~li></ol~~p> ~~~~<~~/span~~p>== [[File:~~./images/~~media/~~image106~~image77.png|576x340px]] == ~~<ol start="11" style="list-style-type: decimal;"><li>~~</~~li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li><li></li></ol>~~ ~~<ol start="19" style="list-style-type: decimal;"><li></li><li~~p></li></ol>

# The development board reserves the expansion interface of the eMMC module. Before programming the system to the eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The location of the eMMC interface is as follows：

[[File:~~./images/~~media/~~image108~~image78.png|307x141px]]

<li>It is also necessary to prepare a data cable with a good quality Type-C interface</li></ol>

[[File:~~./images/~~media/~~image22~~image21.png|150x152px]]

[[File:~~./images/~~media/~~image109~~image79.png|408x99px|c40e71d1a66216e12b3b4297138f749]]

</div>

[[File:~~./images/~~media/~~image110~~image80.png|337x138px|2feec28318eaa60c0514000158b889a]]

</div>

'''Note that the~~''' '''~~"MiniLoader-things needed to burn the Linux image"~~''' '''~~folder is hereinafter referred to as the MiniLoader folder.'''

[[File:~~./images/~~media/~~image102~~image73.png|340x108px|e6986fc9c8fc078e8cb6a9c39b76fb8]]

</div>

<li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe'''executable file in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image57~~image47.png|496x146px]]

</li></ol>

[[File:~~./images/~~media/~~image58~~image48.png|284x149px]]

<li>After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button.</li></ol>

[[File:~~./images/~~media/~~image59~~image49.png|296x154px]]

<li>Then decompress RKDevTool_Release_v3.15.zip, this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image60~~image50.png|484x143px]]

<li>After opening the '''RKDevTool''' burning tool, because the computer has not been connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li></ol>

[[File:~~./images/~~media/~~image61~~image51.png|442x208px]]

[[File:~~./images/~~media/~~image63~~image52.jpeg|403x114px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-2.jpg未标题-2]]

</div>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:</li></ol>

[[File:~~./images/~~media/~~image64~~image53.png|418x94px]]

<li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button</li></ol>

[[File:~~./images/~~media/~~image65~~image54.png|407x124px]]

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li></ol>

[[File:~~./images/~~media/~~image66~~image55.png|457x215px]]

<li>Then place the mouse cursor in the area below</li></ol>

[[File:~~./images/~~media/~~image95~~image81.png|458x215px]]

<li>Then click the right mouse button and the selection interface shown in the figure below will pop up</li></ol>

[[File:~~./images/~~media/~~image70~~image57.png|460x216px]]

<li>Then select the '''import configuration''' option</li></ol>

[[File:~~./images/~~media/~~image72~~image58.png|458x215px]]

<li>Then select the '''rk3588_linux_emmc.cfg''' configuration file in the '''MiniLoader''' folder downloaded earlier, and click '''Open'''</li></ol>

[[File:~~./images/~~media/~~image111~~image82.png|466x219px]]

<li>Then click '''OK'''</li></ol>

[[File:~~./images/~~media/~~image113~~image83.png|468x220px]]

<li>Then click the position shown in the figure below</li></ol>

[[File:~~./images/~~media/~~image115~~image84.png|462x217px]]

<li>Then select '''MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and then click to '''open'''</li></ol>

[[File:~~./images/~~media/~~image117~~image85.png|463x217px]]

<li>Then click the position shown in the figure below</li></ol>

[[File:~~./images/~~media/~~image118~~image86.png|459x216px]]

'''Before burning the image, it is recommended to rename the linux image to be burned to orangepi.img or other shorter names, so that you can see the percentage value of the burning progress when burning the image.'''

[[File:~~./images/~~media/~~image84~~image64.png|499x234px]]

<li>Then please check the option to '''force writing by address'''</li></ol>

[[File:~~./images/~~media/~~image120~~image87.png|501x235px]]

<li>Then click the execute button to start burning the linux image to the eMMC of the development board</li></ol>

[[File:~~./images/~~media/~~image122~~image88.png|502x236px]]

<li>The log displayed after burning the linux image is shown in the figure below</li></ol>

[[File:~~./images/~~media/~~image124~~image89.png|500x235px]]

<li>After burning the linux image into the eMMC, the linux system will > start automatically.</li></ol>

~~~~

~~== ==~~

~~~~

~~=== ===~~

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

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

~~<li></li>~~

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

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

# The development board reserves the expansion interface of the eMMC module. Before programming the system to the eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The location of the eMMC interface is as follows:

[[File:~~./images/~~media/~~image108~~image78.png|312x143px]]

<li>Then we can use the dd command to clear the eMMC. Note that after the '''of=''' parameter, please fill in the output result of the above command</li></ol>

orangepi@orangepi:~/Desktop$ '''sudo dd bs=1M if=/dev/zero of=/dev/mmcblk1~~''' '''~~count=1000 status=progress'''

orangepi@orangepi:~/Desktop$ '''sudo sync'''

</li></ol>

'''sudo dd bs=1M if=Orangepi5plus_x.x.x_debian_bullseye_desktop_xfce_linux5.10.110.img of=/dev/mmcblk1~~''' '''~~status=progress'''

'''sudo''' '''sync'''

'''Note, if you upload a~~''' '''~~.7z or .xz~~''' '''~~linux image compressed file, please remember to decompress it before using the dd command to burn.'''

'''The detailed description of all parameters of the dd command and more usage can be viewed by executing the man dd command in the linux system.'''

~~<li></li>~~

<li>After successfully burning the linux image of the development board to the eMMC, you can use the '''poweroff''' command to shut down. Then please pull out the TF card, and then short press the power button to turn on, and then the linux system in the eMMC will be started.</li></ol>

'''Note that all the following operations are performed on a Windows computer.'''

~~~~

~~=== ===~~

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

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

~~<li></li>~~

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

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

# First, you need to prepare an M-Key 2280 specification NVMe SSD solid state drive, and the specification of the PCIe interface in the M.2 slot of the development board is PCIe3.0x4.

[[File:~~./images/~~media/~~image26~~image25.png|306x89px]]

<li>Then insert the NVMe SSD into the M.2 PCIe interface of the development board shown in the figure below, and fix it</li></ol>

[[File:~~./images/~~media/~~image126~~image90.png|274x110px]]

<li>The position of the SPI Flash on the development board is shown in the figure below, no other settings are required before starting the programming</li></ol>

[[File:~~./images/~~media/~~image127~~image91.png|416x115px]]

[[File:~~./images/~~media/~~image146~~image92.png|355x174px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image147~~image93.png|356x179px|IMG_256]]

</div>

<li>Then please wait patiently for the burning to complete. After the burning is completed, the display will be as follows (a '''Done''' will be displayed in the lower left corner):</li></ol>

[[File:~~./images/~~media/~~image148~~image94.png|406x199px]]

'''There is no nand-sata-install script in OPi OS Arch system, please use the following command to mirror u-boot to SPI Flash:'''

<li>Then upload the linux image file (Debian, Ubuntu or OpenWRT image downloaded from the official website) to the TF card. For the method of '''uploading the linux image file to the development board,''' please refer to the description in the section of the method of uploading files to the development board Linux system.</li></ol>

'''Note, if you download the OpenWRT image, you will see the following two types of images in the download link of the OpenWRT image, please download the image file in the~~''' '''~~"TF card, eMMC and NVME SSD boot image"~~''' '''~~folder.'''

[[File:~~./images/~~media/~~image102~~image73.png|284x90px|e6986fc9c8fc078e8cb6a9c39b76fb8]]

</div>

.…

<li>Then we can use the dd command to clear the NVMe SSD (optional)</li></ol>

orangepi@orangepi5plus:~/Desktop$ '''sudo sync'''

<li>Then you can use the dd command to burn the linux image of the development board to the NVMe SSD

'''sudo''' '''sync'''

'''Note, if you upload a~~''' '''~~.7z or .xz or .gz~~''' '''~~linux image compressed file, please remember to decompress it before using the dd command to burn.'''

'''The detailed description of all parameters of the dd command and more usage can be viewed by executing the man dd command in the linux system.'''

<li>After successfully burning the linux image of the development board to the NVMe SSD, you can use the poweroff command to shut down. Then please pull out the TF card, and then short press the power button to turn on, then the linux system in SPIFlash+NVMe SSD will be started.</li></ol>

# First, you need to prepare an M-Key 2280 specification NVMe SSD solid state drive, and the specification of the PCIe interface in the M.2 slot of the development board is PCIe3.0x4.

[[File:~~./images/~~media/~~image26~~image25.png|375x108px]]

<li>Then insert the NVMe SSD into the M.2 PCIe interface of the development board shown in the figure below, and fix it</li></ol>

[[File:~~./images/~~media/~~image126~~image90.png|349x140px]]

<li>The position of the SPI Flash on the development board is shown in the figure below, no other settings are required before starting the programming</li></ol>

[[File:~~./images/~~media/~~image127~~image91.png|395x109px]]

[[File:~~./images/~~media/~~image149~~image95.png|506x249px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image150~~image96.png|406x207px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image151~~image97.png|406x205px|IMG_256]]

</div>

<li>Then enter the '''/usr/lib/linux-u-boot-legacy-orangepi5plus_1.x.x_arm64''' directory, select '''rkspi_loader.img''', and click '''Open'''to open</li></ol>

[[File:~~./images/~~media/~~image152~~image98.png|575x162px]]

<li>The interface after opening '''rkspi_loader.img''' is as follows:</li></ol>

[[File:~~./images/~~media/~~image153~~image99.png|379x181px]]

[[File:~~./images/~~media/~~image154~~image100.png|379x171px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image155~~image101.png|385x155px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image156~~image102.png|389x264px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image157~~image103.png|394x268px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image158~~image104.png|396x269px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image159~~image105.png|393x269px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image160~~image106.png|397x272px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image161~~image107.png|395x225px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image162~~image108.png|386x204px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image163~~image109.png|386x261px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image164~~image110.png|381x191px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image154~~image100.png|379x171px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image155~~image101.png|385x155px|IMG_256]]

</div>

<li>Then select the device name of the NVMe SSD '''/dev/nvme0n1''', and click '''Select'''</li></ol>

[[File:~~./images/~~media/~~image165~~image111.png|386x264px]]

[[File:~~./images/~~media/~~image166~~image112.png|389x264px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image167~~image113.png|392x268px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image168~~image114.png|390x267px|IMG_256]]

</div>

<li>The display of the burning process is as follows:</li></ol>

[[File:~~./images/~~media/~~image169~~image115.png|393x212px]]

[[File:~~./images/~~media/~~image170~~image116.png|395x205px|IMG_256]]

</div>

<li>After the burning is completed, the display is as follows:</li></ol>

[[File:~~./images/~~media/~~image171~~image117.png|398x227px]]

[[File:~~./images/~~media/~~image172~~image118.png|590x317px|IMG_256]]

</div>

<li>Then enter the password orangepi of the linux system, and then click '''Authenticate'''</li></ol>

[[File:~~./images/~~media/~~image173~~image119.png|356x173px]]

<li>Then click '''Fix'''</li></ol>

[[File:~~./images/~~media/~~image174~~image120.png|375x276px]]

[[File:~~./images/~~media/~~image175~~image121.png|452x187px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image176~~image122.png|451x187px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image177~~image123.png|448x345px|IMG_256]]

</div>

<li>Then drag the capacity to the maximum at the position shown in the figure below</li></ol>

[[File:~~./images/~~media/~~image178~~image124.png|339x210px]]

<li>and click '''Resize/Move'''</li></ol>

[[File:~~./images/~~media/~~image179~~image125.png|339x212px]]

<li>Then click the green one in the picture below'''√'''</li></ol>

[[File:~~./images/~~media/~~image180~~image126.png|425x166px]]

<li>Click again '''Apply'''</li></ol>

[[File:~~./images/~~media/~~image181~~image127.png|378x276px]]

<li>Then click '''Close''' to close</li></ol>

[[File:~~./images/~~media/~~image182~~image128.png|383x234px]]

[[File:~~./images/~~media/~~image183~~image129.png|575x361px|图片1]]

</div>

'''c.~~''' '''After~~ After using this method to burn the image, there is no need to manually expand the capacity, and it will automatically expand the capacity at the first startup.'''

=== Using RKDevTool to burn ===

~~<ol start="12" style="list-style-type: decimal;"><li>~~# First, you need to prepare an M-Key 2280 specification NVMe SSD solid state drive, and the specification of the PCIe interface in the M.2 slot of the development board is PCIe3.0x4.~~</li></ol>~~

[[File:~~./images/~~media/~~image26~~image25.png|261x75px]]

<li>Then insert the NVMe SSD into the M.2 PCIe interface of the development board shown in the figure below, and fix it</li></ol>

[[File:~~./images/~~media/~~image126~~image90.png|259x104px]]

<li>The position of the SPI Flash on the development board is shown in the figure below, no other settings are required before starting the programming</li></ol>

[[File:~~./images/~~media/~~image127~~image91.png|340x94px]]

<li>Then you need to prepare a data cable with good quality Type-C interface</li></ol>

[[File:~~./images/~~media/~~image22~~image21.png|123x124px]]

<li>Then download the Rockchip driver '''DriverAssitant_v5.12.zip''' and MiniLoader and the burning tool '''RKDevTool_Release_v3.15.zip''' from the Orange Pi data download page

[[File:~~./images/~~media/~~image109~~image79.png|371x90px|c40e71d1a66216e12b3b4297138f749]]

</div>

[[File:~~./images/~~media/~~image110~~image80.png|340x140px|2feec28318eaa60c0514000158b889a]]

</div>

'''Note that the "MiniLoader-things needed to burn the Linux image" folder is hereinafter referred to as the MiniLoader folder.'''

<li>Then download the Linux operating system image file compression package that you want to burn from the Orange Pi data download page, and then use the decompression software to decompress it. Among the decompressed files, the file ending with "'''.img'''" is the image file of the operating system , the size is generally more than 2GB</li></ol>

[[File:~~./images/~~media/~~image102~~image73.png|340x108px|e6986fc9c8fc078e8cb6a9c39b76fb8]]

</div>

<li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', then find '''DriverInstall.exe''' executable file in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image57~~image47.png|429x126px]]

<li>After opening '''DriverInstall.exe''', the steps to install the Rockchip driver are as follows

</li></ol>

[[File:~~./images/~~media/~~image58~~image48.png|300x157px]]

<li>After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button.</li></ol>

[[File:~~./images/~~media/~~image59~~image49.png|324x168px]]

<li>Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image60~~image50.png|455x135px]]

<li>After opening the '''RKDevTool''' burning tool, because the computer is not connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li></ol>

[[File:~~./images/~~media/~~image61~~image51.png|436x205px]]

<li>Then start burning the Linux image to the SSD

[[File:~~./images/~~media/~~image63~~image52.jpeg|446x126px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-2.jpg未标题-2]]

</div>

<li>Then press and hold the MaskROM button on the development board. The position of the MaskROM button on the development board is shown in the figure below:</li></ol>

[[File:~~./images/~~media/~~image64~~image53.png|424x103px]]

<li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button. The location of the Type-C power interface is as follows:</li></ol>

[[File:~~./images/~~media/~~image65~~image54.png|439x134px]]

<li>If the previous steps are successful, the development board will enter the MASKROM mode at this time, and the interface of the burning tool will prompt "'''Found a MASKROM device'''"</li></ol>

[[File:~~./images/~~media/~~image66~~image55.png|457x215px]]

[[File:~~./images/~~media/~~image185~~image130.jpeg|452x212px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-4.jpg未标题-4]]

</div>

<li>Then place the mouse cursor in the area below</li></ol>

[[File:~~./images/~~media/~~image70~~image57.png|453x213px]]

<li>Then select the '''Import configuration''' option</li></ol>

[[File:~~./images/~~media/~~image72~~image58.png|458x215px]]

<li>Then enter the MiniLoader folder downloaded earlier, then select the '''rk3588_linux_pcie.cfg''' configuration file, and click '''Open'''</li></ol>

[[File:~~./images/~~media/~~image186~~image131.png|462x217px]]

<li>Then click '''OK'''</li></ol>

[[File:~~./images/~~media/~~image187~~image132.png|468x220px]]

<li>Then click the location shown in the figure below</li></ol>

[[File:~~./images/~~media/~~image188~~image133.png|480x225px]]

<li>Then select '''MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and then click to '''open'''</li></ol>

[[File:~~./images/~~media/~~image80~~image62.png|484x227px]]

<li>Then click the position shown in the figure below</li></ol>

[[File:~~./images/~~media/~~image189~~image134.png|486x228px]]

<li>Then enter the '''MiniLoader''' folder downloaded earlier, select '''rkspi_loader.img,''' and click '''Open'''</li></ol>

[[File:~~./images/~~media/~~image190~~image135.png|501x235px]]

<li>Then click the location shown in the figure below</li></ol>

[[File:~~./images/~~media/~~image191~~image136.png|501x235px]]

'''Before burning the image, it is recommended to rename the linux image to be burned to orangepi.img or other shorter names, so that you can see the percentage value of the burning progress when burning the image.'''

[[File:~~./images/~~media/~~image84~~image64.png|499x234px]]

<li>Then please check the option to '''force write by address'''</li></ol>

[[File:~~./images/~~media/~~image192~~image137.png|487x229px]]

<li>Click the Execute button again to start burning the u-boot+linux image to SPIFlash+SSD</li></ol>

[[File:~~./images/~~media/~~image193~~image138.png|489x230px]]

<li>The display log after burning the image is shown in the figure below</li></ol>

[[File:~~./images/~~media/~~image194~~image139.png|490x230px]]

<li>After the image is burnt, it will automatically start the linux system in SPIFlash+PCIe SSD. If it does not start normally, please power on and try again.</li></ol>

~~~~

~~=== ===~~

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

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

~~<li></li>~~

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

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

'''Since the spi flash on the development board is only 16MB, this system basically cannot install much software, and currently only some basic functions can be realized.'''

~~~~

~~=== ===~~

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

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

~~<li></li>~~

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

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

[[File:~~./images/~~media/~~image203~~image140.png|329x112px|25566f72fb1f4567c78af07e73b5134]]

</div>

=== Using RKDevTool to burn ===

~~<ol start="10" style="list-style-type: decimal;"><li>~~# The position of the SPI Flash on the development board is shown in the figure below, no other settings are required before starting the programming~~</li></ol>~~

[[File:~~./images/~~media/~~image127~~image91.png|389x107px]]

<li>Then you need to prepare a data cable with good quality Type-C interface</li></ol>

[[File:~~./images/~~media/~~image22~~image21.png|152x154px]]

<li>Then download the Rockchip driver '''DriverAssitant_v5.12.zip''' and MiniLoader and the burning tool '''RKDevTool_Release_v3.15.zip''' from the Orange Pi data download page

[[File:~~./images/~~media/~~image102~~image73.png|340x108px|e6986fc9c8fc078e8cb6a9c39b76fb8]]

</div>

[[File:~~./images/~~media/~~image110~~image80.png|401x165px|2feec28318eaa60c0514000158b889a]]

</div>

'''Note that the''' "MiniLoader-things needed to burn the Linux image" '''folder is hereinafter referred to as the MiniLoader folder.'''

<li>Then download the '''OpenWRT''' image that can be booted from SPIFlash from the download page of Orange Pi. Limited by the capacity of SPIFlash, the image size is less than '''16MB.''' After opening the download link, you can see the following two types of OpenWRT images, please select the image in the '''SPIFlash boot image''' folder</li></ol>

[[File:~~./images/~~media/~~image203~~image140.png|329x112px|25566f72fb1f4567c78af07e73b5134]]

</div>

<li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image57~~image47.png|472x139px]]

<li>After opening '''DriverInstall.exe''', the steps to install the Rockchip driver are as follows

</li></ol>

[[File:~~./images/~~media/~~image58~~image48.png|276x145px]]

<li>After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button.</li></ol>

[[File:~~./images/~~media/~~image59~~image49.png|292x151px]]

<li>Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image60~~image50.png|467x138px]]

<li>After opening the '''RKDevTool''' burning tool, because the computer has not been connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li></ol>

[[File:~~./images/~~media/~~image61~~image51.png|402x189px]]

<li>Then start burning the OpenWRT image into SPI FLASH

[[File:~~./images/~~media/~~image63~~image52.jpeg|424x120px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-2.jpg未标题-2]]

</div>

<li>Then press and hold the MaskROM button on the development board. The position of the MaskROM button on the development board is shown in the figure below:</li></ol>

[[File:~~./images/~~media/~~image64~~image53.png|444x100px]]

<li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button</li></ol>

[[File:~~./images/~~media/~~image65~~image54.png|402x123px]]

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''Found a MASKROM device'''"</li></ol>

[[File:~~./images/~~media/~~image66~~image55.png|457x215px]]

[[File:~~./images/~~media/~~image185~~image130.jpeg|452x212px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-4.jpg未标题-4]]

</div>

<li>Then click the right mouse button and the selection interface shown in the figure below will pop up</li></ol>

[[File:~~./images/~~media/~~image70~~image57.png|453x213px]]

<li>Then select the '''Import configuration''' option</li></ol>

[[File:~~./images/~~media/~~image72~~image58.png|458x215px]]

<li>Then select the '''rk3588_linux_spiflash.cfg''' configuration file in the MiniLoader folder downloaded earlier, and click '''Open'''</li></ol>

[[File:~~./images/~~media/~~image204~~image141.png|465x218px]]

<li>Then click '''OK'''</li></ol>

[[File:~~./images/~~media/~~image205~~image142.png|466x219px]]

<li>Then click the location shown in the figure below</li></ol>

[[File:~~./images/~~media/~~image206~~image143.png|467x219px]]

<li>Then select '''MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and click '''Open'''</li></ol>

[[File:~~./images/~~media/~~image207~~image144.png|469x220px]]

<li>Then click the location shown in the figure below</li></ol>

[[File:~~./images/~~media/~~image208~~image145.png|452x212px]]

<li>Then select the path of the OpenWRT image you want to burn, and click '''Open'''

'''Before burning the image, it is recommended to rename the OpenWRT image to be burned to~~''' '''~~orangepi.img~~''' '''~~or other shorter names, so that you can see the percentage value of the burning progress when burning the image.'''</li></ol>

[[File:~~./images/~~media/~~image84~~image64.png|456x214px]]

<li>Then please make sure that the option to '''force writing by address''' is ticked</li></ol>

[[File:~~./images/~~media/~~image209~~image146.png|463x217px]]

<li>Click the '''Execute''' button again to start burning the OpenWRT image into SPIFlash</li></ol>

[[File:~~./images/~~media/~~image210~~image147.png|463x218px]]

<li>The display log after burning the OpenWRT image is shown in the figure below</li></ol>

[[File:~~./images/~~media/~~image211~~image148.png|465x219px]]

<li>The OpenWRT image will start automatically after burning, if it does not start normally, please try again with power on.</li></ol>

~~~~

~~== ==~~

~~~~

~~=== ===~~

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

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

~~<li></li>~~

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

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

~~~~

~~=== ===~~

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

~~<li></li>~~

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

~~~~

~~=== ===~~

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

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

~~<li></li>~~

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

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

</li></ol>

[[File:~~./images/~~media/~~image212~~image149.png|240x98px]]

c) The image with box is a image dedicated to the TV box

[[File:~~./images/~~media/~~image213~~image150.png|255x97px]]

<li>Then use decompression software to decompress '''SDDiskTool_v1.72.zip''', this software does not need to be installed, just find '''SD_Firmware_Tool.exe''' in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image214~~image151.png|575x138px]]

<li>After opening SDDiskTool, if the TF card is recognized normally, the inserted disk device will be displayed in the "'''Select Removable Disk Device'''" column. '''Please make sure that the displayed disk device is consistent with the drive letter of the TF card you want to burn''' If there is no display, you can try to unplug the TF card</li></ol>

[[File:~~./images/~~media/~~image215~~image152.png|267x228px]]

<li>After confirming the drive letter, you can format the TF card first, click the restore disk button in '''SDDiskTool''', or use the SD Card Formatter mentioned above to format the TF card</li></ol>

[[File:~~./images/~~media/~~image216~~image153.png|247x212px]]

c. Finally click the "'''Start Create'''" button to start burning the Android image to the TF card

[[File:~~./images/~~media/~~image217~~image154.png|346x292px]]

<li>After burning, you can exit the SDDiskTool software, and then you can pull out the TF card from the computer and insert it into the development board to start</li></ol>

[[File:~~./images/~~media/~~image218~~image155.png|304x258px]]

# The development board reserves an eMMC expansion interface. Before programming the system to eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The location of the eMMC interface is as follows:

[[File:~~./images/~~media/~~image108~~image78.png|307x141px]]

<li>It is also necessary to prepare a data cable with a good quality Type-C interface

[[File:~~./images/~~media/~~image22~~image21.png|134x136px]]</li>

<li>Then download Rockchip driver '''DriverAssitant_v5.12.zip''' and burning tool '''RKDevTool_Release_v3.15.zip''' from '''Orange Pi's data download page'''</li>

<li>Then download the Android image from '''Orange Pi's download page.'''</li></ol>

[[File:~~./images/~~media/~~image219~~image156.png|240x98px|4db492fa03e0cf83396c36286128350]]

</div>

<li>The image with box is a image dedicated to the TV box</li></ol>

[[File:~~./images/~~media/~~image213~~image150.png|255x97px]]

<li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image57~~image47.png|575x169px]]

</li></ol>

[[File:~~./images/~~media/~~image58~~image48.png|300x157px]]

<li>After waiting for a period of time, a pop-up window will prompt "driver installed successfully", then click "OK"</li></ol>

[[File:~~./images/~~media/~~image59~~image49.png|315x164px]]

<li>Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image60~~image50.png|454x134px]]

<li>After opening the '''RKDevTool''' burning tool, because the computer has not been connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li></ol>

[[File:~~./images/~~media/~~image61~~image51.png|442x208px]]

[[File:~~./images/~~media/~~image63~~image52.jpeg|439x124px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-2.jpg未标题-2]]

</div>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below：</li></ol>

[[File:~~./images/~~media/~~image64~~image53.png|456x103px]]

<li>Then connect the power supply of the Type-C interface to the development board, and power on</li></ol>

[[File:~~./images/~~media/~~image65~~image54.png|441x135px]]

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li></ol>

[[File:~~./images/~~media/~~image66~~image55.png|457x215px]]

<li>Then click the "'''Upgrade Firmware'''" column of the burning tool</li></ol>

[[File:~~./images/~~media/~~image220~~image157.png|442x208px]]

<li>Then click the "'''Firmware'''" button to select the path of the Android image that needs to be burned</li></ol>

[[File:~~./images/~~media/~~image222~~image158.png|444x209px]]

<li>Finally, click the "'''Upgrade'''" button to start burning, and the log during the burning process is shown in the figure below. After burning is completed, the Android system will start automatically.</lip><~~/ol~~p> [[File:~~./images/~~media/~~image224~~image159.png|449x211px]]</li></ol>

# The development board reserves an eMMC expansion interface. Before programming the system to eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The location of the eMMC interface is as follows:

[[File:~~./images/~~media/~~image108~~image78.png|392x180px]]

[[File:~~./images/~~media/~~image219~~image156.png|240x98px|4db492fa03e0cf83396c36286128350]]

</div>

</li></ol>

[[File:~~./images/~~media/~~image213~~image150.png|255x97px]]

[[File:~~./images/~~media/~~image214~~image151.png|429x103px]]

<li>After opening '''SDDiskTool''', if the TF card is recognized normally, the inserted disk device will be displayed in the "'''Select Removable Disk Device'''" column. '''Please make sure that the displayed disk device is consistent with the drive letter of the TF card you want to burn''', if there is no display, you can try to unplug the TF card</li></ol>

[[File:~~./images/~~media/~~image215~~image152.png|267x228px]]

<li>After confirming the drive letter, you can format the TF card first, click the '''restore disk''' button in '''SDDiskTool,''' or use the '''SD Card Formatter''' mentioned above to format the TF card</li></ol>

[[File:~~./images/~~media/~~image216~~image153.png|247x212px]]

</li></ol>

[[File:~~./images/~~media/~~image227~~image160.png|290x246px]]

[[File:~~./images/~~media/~~image228~~image161.png|285x243px]]

[[File:~~./images/~~media/~~image229~~image162.png|430x247px]]

<li>When the HDMI monitor displays the following information, it means that the burning of the Android image into the eMMC has been completed. At this time, the TF card can be pulled out, and then the Android system in the eMMC will start.</~~li></ol~~p> <~~span id="section-25"~~p>~~===~~ [[File:~~./images/~~media/~~image230~~image163.png|576x389px]] ~~===~~ ~~<ol start="18" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li></ol></li><li></li><li></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li>~~</~~li></ol></li><li></li><li></li><li></li><li~~p></li></ol>

# First, you need to prepare an M-Key 2280 specification NVMe SSD solid state drive, and the specification of the PCIe interface in the M.2 slot of the development board is PCIe3.0x4.

[[File:~~./images/~~media/~~image26~~image25.png|361x104px]]

<li>Then insert the NVMe SSD into the M.2 PCIe interface of the development board and fix it</li></ol>

[[File:~~./images/~~media/~~image126~~image90.png|355x143px]]

<li>The position of the SPI Flash on the development board is shown in the figure below, no other settings are required before starting the programming</li></ol>

[[File:~~./images/~~media/~~image127~~image91.png|415x114px]]

<li>It is also necessary to prepare a data cable with a good quality Type-C interface</li></ol>

[[File:~~./images/~~media/~~image22~~image21.png|150x152px]]

</li></ol>

[[File:~~./images/~~media/~~image231~~image164.png|234x91px]]

</li></ol>

[[File:~~./images/~~media/~~image232~~image165.png|241x70px]]

<li>Then use the decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image57~~image47.png|575x169px]] ~~8) After opening DriverInstall.exe, the steps to install the Rockchip driver are as follows~~

a8) After opening DriverInstall.exe, the steps to install the Rockchip driver are as followsa. Click the "'''Driver Install'''" button

[[File:~~./images/~~media/~~image58~~image48.png|300x157px]]

a. After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", then click the "'''OK'''" button

[[File:~~./images/~~media/~~image59~~image49.png|429x223px]]

<blockquote>9)Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it

</blockquote>

[[File:~~./images/~~media/~~image60~~image50.png|421x124px]]

<li>After opening the '''RKDevTool''' burning tool, because the computer is not connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li></ol>

[[File:~~./images/~~media/~~image61~~image51.png|442x208px]]

<li>Then start burning the Android image to SPIFlash+NVMe SSD

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

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

~~~~

<li>First, connect the development board to the Windows computer > through the Type-C data cable. The position of the Type-C > interface on the development board is shown in the figure > below</li></ol>

[[File:~~./images/~~media/~~image63~~image52.jpeg|418x118px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-2.jpg未标题-2]]

</div>

<li>Then press and hold the MaskROM button on the development board, the > position of the MaskROM button on the development board is shown > in the figure below:</li></ol>

[[File:~~./images/~~media/~~image64~~image53.png|443x100px]]

<li>Then connect the power supply of the Type-C interface to the > development board, and power on, and then release the MaskROM > button</li></ol>

[[File:~~./images/~~media/~~image65~~image54.png|449x137px]]

<li>If the previous steps are successful, the development board will > enter the '''MASKROM''' mode at this time, and the interface of the > burning tool will prompt "'''Found a MASKROM device'''"</li></ol>

[[File:~~./images/~~media/~~image66~~image55.png|457x215px]]

<li>Then click the "Upgrade Firmware" column of the burning tool</li></ol>

[[File:~~./images/~~media/~~image220~~image157.png|442x208px]]

<li>Then click the "Firmware" button to select the Android image to be > burned</li></ol>

[[File:~~./images/~~media/~~image222~~image158.png|447x210px]]

<li>Finally, click the "Upgrade" button to start burning. The burning > process is shown in the figure below. After the burning is > completed, the Android system will automatically start.</li></ol>

[[File:~~./images/~~media/~~image233~~image166.png|450x210px]]

# First prepare a TF card with 8GB or larger capacity. The transmission speed of the TF card must be class10 or above. It is recommended to use a TF card of SanDisk and other brands

# Then use the card reader to insert the TF card into the computer

# Then download the SDDiskTool programming tool from the '''Orange Pi data download page''', '''please make sure that the version of the~~''' '''~~SDDiskTool~~''' '''~~tool is the latest v1.72.'''

# Then download the Orange Pi OS (Droid) image from the O'''range Pi data download page''', open the download link of the Orange Pi OS (Droid) image, and you can see the following two types of images, please select the image below

[[File:~~./images/~~media/~~image235~~image167.png|286x49px]]

<li>Then use decompression software to decompress '''SDDiskTool_v1.72.zip''', this software does not need to be installed, just find '''SD_Firmware_Tool.ex''' in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image214~~image151.png|486x117px]]

<li>After opening '''SDDiskTool''', if the TF card is recognized normally, the inserted disk device will be displayed in the "'''Select Removable Disk Device'''" column. '''Please make sure that the displayed disk device is consistent with the drive letter of the TF card you want to burn''' , if there is no display, you can try to unplug the TF card</li></ol>

[[File:~~./images/~~media/~~image215~~image152.png|248x212px]]

<li>After confirming the drive letter, you can format the TF card first, click the '''restore disk''' button in SDDiskTool, or use the '''SD Card Formatter''' mentioned above to format the TF card</li></ol>

[[File:~~./images/~~media/~~image216~~image153.png|261x224px]]

</li></ol>

[[File:~~./images/~~media/~~image217~~image154.png|279x236px]]

<li>After burning, you can exit the SDDiskTool software, and then you can pull out the TF card from the computer and insert it into the development board to start</li></ol>

[[File:~~./images/~~media/~~image218~~image155.png|304x258px]]

# The development board reserves an eMMC expansion interface. Before programming the system to eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The location of the eMMC interface is as follows:

[[File:~~./images/~~media/~~image108~~image78.png|324x149px]]

<li>It is also necessary to prepare a data cable with a good quality Type-C interface</li></ol>

[[File:~~./images/~~media/~~image22~~image21.png|127x129px]]

<li>Then download the Orange Pi OS (Droid) image from the '''Orange Pi download page'''</li></ol>

[[File:~~./images/~~media/~~image235~~image167.png|286x49px]]

<li>Then use decompression software to decompress '''DriverAssitant_v5.12.zip''', then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image57~~image47.png|575x169px]]

</li></ol>

[[File:~~./images/~~media/~~image58~~image48.png|300x157px]]

<li>After waiting for a period of time, a pop-up window will prompt "driver installed successfully", and then click the "OK" button.</li></ol>

[[File:~~./images/~~media/~~image59~~image49.png|318x165px]]

<li>Then decompress'''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image60~~image50.png|575x170px]]

<li>After opening the '''RKDevTool''' burning tool, because the computer is not connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li></ol>

[[File:~~./images/~~media/~~image61~~image51.png|442x208px]]

[[File:~~./images/~~media/~~image63~~image52.jpeg|468x132px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-2.jpg未标题-2]]

</div>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:</li></ol>

[[File:~~./images/~~media/~~image64~~image53.png|479x108px]]

<li>Then connect the power supply of the Type-C interface to the development board, and power on</li></ol>

[[File:~~./images/~~media/~~image65~~image54.png|457x140px]]

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li></ol>

[[File:~~./images/~~media/~~image66~~image55.png|457x215px]]

<li>Then click the "'''Upgrade Firmware'''" column of the burning tool</li></ol>

[[File:~~./images/~~media/~~image220~~image157.png|461x217px]]

<li>Then click the "'''Firmware'''" button to select the path of the Orange Pi OS (Droid) image that needs to be burned</li></ol>

[[File:~~./images/~~media/~~image222~~image158.png|453x213px]]

<li>Finally, click the "'''Upgrade'''" button to start burning, and the log during the burning process is shown in the figure below. After burning, the Orange Pi OS (Droid) system will start automatically.</li></ol>

[[File:~~./images/~~media/~~image236~~image168.png|456x214px]]

# The development board reserves an eMMC expansion interface. Before programming the system to eMMC, you first need to purchase an eMMC module that matches the eMMC interface of the development board. Then install the eMMC module to the development board. The location of the eMMC interface is as follows:

[[File:~~./images/~~media/~~image108~~image78.png|342x157px]]

<li>Then download the Orange Pi OS (Droid) image from the '''Orange Pi download page'''</li></ol>

[[File:~~./images/~~media/~~image235~~image167.png|286x49px]]

<li>Then use decompression software to decompress '''SDDiskTool_v1.72.zip''', this software does not need to be installed, just find '''SD_Firmware_Tool.exe''' in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image214~~image151.png|454x109px]]

<li>After opening '''SDDiskTool''', if the TF card is recognized normally, the inserted disk device will be displayed in the "'''Select Removable Disk Device'''" column. '''Please make sure that the displayed disk device is consistent with the drive letter of the TF card you want to burn''', if there is no display, you can try to unplug the TF card.</li></ol>

[[File:~~./images/~~media/~~image215~~image152.png|267x228px]]

<li>After confirming the drive letter, you can format the TF card first, click the restore disk button in '''SDDiskTool''', or use the '''SD Card Formatter''' mentioned above to format the TF card</li></ol>

[[File:~~./images/~~media/~~image216~~image153.png|267x228px]]

d. Finally click the "'''Start Create'''" button to start burning

[[File:~~./images/~~media/~~image227~~image160.png|289x246px]]

<li>After the burning is completed, the display is as shown in the figure below, and then you can exit SDDiskTool</li></ol>

[[File:~~./images/~~media/~~image228~~image161.png|285x243px]]

<li>If the development board is connected to an HDMI display, you can also see the progress bar of burning the Orange Pi OS (Droid) image to eMMC from the HDMI display</li></ol>

[[File:~~./images/~~media/~~image229~~image162.png|430x247px]]

<li>When the HDMI monitor displays the following information, it means that the burning of the Orange Pi OS (Droid) image to the eMMC has been completed. At this time, the TF card can be pulled out, and then the Orange Pi OS (Droid) system in the eMMC will start to start .</li></ol>

[[File:~~./images/~~media/~~image230~~image163.png|576x389px]]

# First, you need to prepare a 2280 specification NVMe SSD solid state drive. The specification of the PCIe interface in the M.2 slot of the development board is PCIe3.0x4.

[[File:~~./images/~~media/~~image26~~image25.png|314x91px]]

<li>Then insert the NVMe SSD into the M.2 PCIe interface of the development board and fix it</li></ol>

[[File:~~./images/~~media/~~image126~~image90.png|323x130px]]

<li>The position of the SPI Flash on the development board is shown in the figure below, no other settings are required before starting the programming</li></ol>

[[File:~~./images/~~media/~~image127~~image91.png|382x105px]]

<li>It is also necessary to prepare a data cable with a good quality Type-C interface</li></ol>

[[File:~~./images/~~media/~~image22~~image21.png|143x145px]]

<li>Then download the Orange Pi OS (Droid) image, open the download link of the Orange Pi OS (Droid) image and you can see the following two types of images, please select the image with '''spi-nvme''' to download</li></ol>

[[File:~~./images/~~media/~~image238~~image169.png|352x62px]]

<li>Then use the decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image57~~image47.png|423x124px]]

</li></ol>

[[File:~~./images/~~media/~~image58~~image48.png|268x140px]]

<li>After waiting for a period of time, a pop-up window will prompt "'''driver installed successfully'''", and then click the "'''OK'''" button.</li></ol>

[[File:~~./images/~~media/~~image59~~image49.png|301x156px]]

<li>Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it</li></ol>

[[File:~~./images/~~media/~~image60~~image50.png|455x134px]]

<li>After opening the '''RKDevTool''' burning tool, because the computer is not connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"</li></ol>

[[File:~~./images/~~media/~~image61~~image51.png|442x208px]]

[[File:~~./images/~~media/~~image63~~image52.jpeg|435x123px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-2.jpg未标题-2]]

</div>

<li>Then press and hold the MaskROM button on the development board, the position of the MaskROM button on the development board is shown in the figure below:</li></ol>

[[File:~~./images/~~media/~~image64~~image53.png|460x103px]]

<li>Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button</li></ol>

[[File:~~./images/~~media/~~image65~~image54.png|440x134px]]

<li>If the previous steps are successful, the development board will enter the '''MASKROM''' mode at this time, and the interface of the burning tool will prompt "'''found a MASKROM device'''"</li></ol>

[[File:~~./images/~~media/~~image66~~image55.png|457x215px]]

<li>Then click the "'''Upgrade Firmware'''" column of the burning tool</li></ol>

[[File:~~./images/~~media/~~image220~~image157.png|457x215px]]

<li>Then click the "'''Firmware'''" button to select the Orange Pi OS (Droid) image to be burned</li></ol>

[[File:~~./images/~~media/~~image222~~image158.png|472x222px]]

<li>Finally, click the "'''Upgrade'''" button to start burning. The burning process is shown in the figure below. After the burning is completed, the Orange Pi OS (Droid) system will automatically start.</~~li></ol~~p> <~~span id="section-26"~~p>~~~~== [[File:~~./images/~~media/~~image239~~image170.png|476x225px]] == ~~<ol start="8" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li></ol></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li></ol>~~ ~~<ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li></li><li></li><li><ol style="list-style-type: lower-roman;"><li></li></ol>~~ ~~<ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol></li></ol>~~ ~~== ==~~ ~~<ol start="11" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li><li></li></ol>~~ ~~== ==~~ ~~=== ===~~ ~~<ol start="11" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol></li></ol>~~ ~~=== ===~~ ~~<ol start="15" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li>~~</lip>~~<li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li></ol></li><li></li><li></li><li></li><li></li></ol>~~ ~~== ==~~ ~~<ol start="12" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~</li></ol>

<li>The position of SPI Flash on the development board is shown in the figure below

[[File:~~./images/~~media/~~image127~~image91.png|389x107px]]</li>

<li>First, you need to prepare a data cable with a good quality Type-C interface

[[File:~~./images/~~media/~~image22~~image21.png|152x154px]]</li>

<li>Then download the Rockchip driver '''DriverAssitant_v5.12.zip''' and '''MiniLoader''' and the burning tool '''RKDevTool_Release_v3.15.zip''' from the '''Orange Pi data download page'''

<li>On the Orange Pi data download page, first select the '''official > tool''', and then enter the following folder</p~~></li~~>~~<li>~~[[File:~~./images/~~media/~~image242~~image171.png|486x155px]]</li>

<li>Then download all the files below

[[File:~~./images/~~media/~~image243~~image172.png|389x175px]]'''Note that the~~''' '''~~"MiniLoader-things needed to burn the Linux image"~~''' '''~~folder is hereinafter referred to as the MiniLoader folder.'''</li></ol>

</li>

<li>Then use the decompression software to decompress '''DriverAssitant_v5.12.zip''', and then find the '''DriverInstall.exe''' executable file in the decompressed folder and open it

[[File:~~./images/~~media/~~image57~~image47.png|472x139px]]</li>

<li>After opening '''DriverInstall.exe''', the steps to install the Rockchip driver are as follows

<li>Click the "'''Driver Installation'''" button

[[File:~~./images/~~media/~~image58~~image48.png|276x145px]]</li>

<li>After waiting for a period of time, a pop-up window will prompt > "'''The driver is installed successfully'''", and then click > the "'''OK'''" button.

[[File:~~./images/~~media/~~image59~~image49.png|292x151px]]</li></ol>

</li>

<li>Then decompress '''RKDevTool_Release_v3.15.zip''', this software does not need to be installed, just find '''RKDevTool''' in the decompressed folder and open it

[[File:~~./images/~~media/~~image60~~image50.png|467x138px]]</li>

<li>After opening the '''RKDevTool''' burning tool, because the computer has not been connected to the development board through the Type-C cable at this time, the lower left corner will prompt "'''No device found'''"

[[File:~~./images/~~media/~~image61~~image51.png|402x189px]]</li>

<li>Then you can start to clear the contents of the SPI FLASH

[[File:~~./images/~~media/~~image244~~image173.jpeg|424x120px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-1.jpg未标题-1]]

</div></li>

<li>Make sure the development board is not connected to the power > supply</li>

<li>Then press and hold the MaskROM button on the development board, > the position of the MaskROM button on the development board is > shown in the figure below:

[[File:~~./images/~~media/~~image64~~image53.png|444x100px]]</li>

<li>Then connect the power supply of the Type-C interface to the > development board, and power on, and then release the MaskROM > button

[[File:~~./images/~~media/~~image65~~image54.png|402x123px]]</li>

<li>If the previous steps are smooth, at this time the development > board will enter the '''Maskrom''' mode, and it will be prompted > "'''Find a Maskrom device'''" on the interface of the > recording tool

[[File:~~./images/~~media/~~image66~~image55.png|457x215px]]</li>

<li>Then please select '''advanced features'''

[[File:~~./images/~~media/~~image245~~image174.png|458x138px]]</li>

<li>Then click the position shown in the figure below

[[File:~~./images/~~media/~~image246~~image175.png|459x216px]]</li>

<li>Then select '''MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and then click Open

[[File:~~./images/~~media/~~image207~~image144.png|469x220px]]</li>

<li>Then click '''download'''

[[File:~~./images/~~media/~~image247~~image176.png|472x222px]]</li>

<li>The display after downloading '''MiniLoaderAll.bin''' is shown in the figure below

[[File:~~./images/~~media/~~image248~~image177.png|474x223px]]</li>

<li>Then select the storage device as '''SPINOR'''

[[File:~~./images/~~media/~~image249~~image178.png|467x220px]]</li>

<li>Then click '''switch storage'''

[[File:~~./images/~~media/~~image250~~image179.png|464x218px]]</li>

<li>Then click '''Erase All''' to start erasing SPIFlash

[[File:~~./images/~~media/~~image251~~image180.png|467x220px]]</li>

<li>The display log after erasing SPIFlash is shown in the figure below

[[File:~~./images/~~media/~~image252~~image181.png|450x212px]]</li></ol>

</li></ol>

# The development board has an Ethernet port, which can be plugged into a network cable for Internet access.

# Connect a '''high-quality''' power adapter with a 5V/4A USB Type-C interface.

#

'''Remember not to plug in a power adapter with a voltage output greater than 5V, as this will burn out the development board.'''

'''Many unstable phenomena during the power-on and start-up process of the system are basically caused by power supply problems, so a reliable power adapter is very important. If you find that there is a phenomenon of~~''' '''~~continuous restart during the startup process,~~''' '''~~please replace the~~''' '''~~power'''

'''supply or the Type-C data cable and try again.'''

[[File:~~./images/~~media/~~image253~~image182.jpeg|262x234px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\01.jpg01]]

</div>

<li>Then turn on the switch of the power adapter. If everything is normal, you can see the startup screen of the system on the HDMI monitor or LCD screen.</li>

<li>If you want to view the output information of the system through the debugging serial port, please use the serial cable to connect the development board to the computer. For the connection method of the serial port, please refer to the section on '''how to use the debugging serial port'''.</p~~></li><li></li><li~~></li></ol>

[[File:~~./images/~~media/~~image255~~image183.png|576x115px|07]]

</div>

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

[[File:~~./images/~~media/~~image256~~image184.png|485x174px]]</li>

<li>The GND, TXD and RXD pins of the USB to TTL module need to be connected to the debugging serial port of the development board through a DuPont line

[[File:~~./images/~~media/~~image257~~image185.png|524x189px|08]]

</div>

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

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

<li>After executing the putty command, the following interface will pop up</p~~></li></ol>~~ ~~<ol start="5" style="list-style-type: decimal;"><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol~~>~~</li><li></li></ol>~~ ~~=== ===~~ ~~<ol start="5" style="list-style-type: decimal;"><li></li><li></li><li></li><li>~~[[File:~~./images/~~media/~~image259~~image186.png|367x321px]]</li>

<li>First select the setting interface of the serial port

[[File:~~./images/~~media/~~image260~~image187.png|359x352px]]</li>

<li>Then set the parameters of the serial port

[[File:~~./images/~~media/~~image262~~image188.png|317x312px|09]]

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

[[File:~~./images/~~media/~~image264~~image189.png|345x340px|10]]

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

</li>

<li>After starting the development board, you can see the Log information output by the system from the opened serial port terminal</p~~></li><li></li~~>~~<li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li>~~[[File:~~./images/~~media/~~image265~~image190.png|287x208px]]</li></ol>

<li>Download MobaXterm website as follows

[https://mobaxterm.mobatek.net/ '''https://mobaxterm.mobatek.net''']</li><li>After entering the MobaXterm download page, click '''GET XOBATERM > NOW!'''</p~~></li></ol~~>~~</li><li><ol style="list-style-type: lower-alpha;"><li></li><li>~~[[File:~~./images/~~media/~~image266~~image191.png|576x334px]]</li>

<li>Then choose to download the Home version

[[File:~~./images/~~media/~~image267~~image192.png|353x231px]]</li>

<li>Then select Portable portable version, no need to install after downloading, just open it and use it

[[File:~~./images/~~media/~~image268~~image193.png|575x259px]]</li></ol>

</li>

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

~~<ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li>~~[[File:~~./images/~~media/~~image269~~image194.png|576x81px]]</li>

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

[[File:~~./images/~~media/~~image271~~image195.png|575x438px|11]]

</div>

<ol start="64" style="list-style-type: decimal;"><li>After clicking the "'''OK'''" button, you will enter the following interface. At this time, start the development board and you can see the output information of the serial port</p~~></li~~>~~<li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li></ol></li><li>~~<div class="figure">

[[File:~~./images/~~media/~~image273~~image196.png|575x291px|12]]

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

'''The content of this chapter is written based on the Ubuntu/Debian server version image and the xfce desktop version image.'''

'''If you are using the Ubuntu22.04 Gnome image, please first check the instructions in the chapter~~''' '''~~Ubuntu22.04 Gnome Wayland Desktop System Instructions.'''

'''You can refer to the instructions in this chapter for the content that does not exist in the chapter of~~''' '''~~Ubuntu22.04 Gnome Wayland Desktop System User Manual,~~''' '''~~but some details may be different, please pay special attention to this point.'''

'''If you are using the OPi OS Arch image, please refer to the chapter~~''' '''~~Orange Pi OS Arch System Instructions.'''

|-

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

| style="text-align: left;"| '''Linux5.10~~''' '''~~driver'''

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

| style="text-align: left;"| '''Ubuntu20.04'''

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

|-

| style="text-align: left;"| '''HDMI TX1~~''' '''~~Audio'''

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

|-

| style="text-align: left;"| '''HDMI TX2~~''' '''~~Video'''

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

|-

| style="text-align: left;"| '''HDMI TX2~~''' '''~~Audio'''

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

|-

| style="text-align: left;"| '''HDMI RX~~''' '''~~Video'''

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

|-

| style="text-align: left;"| '''HDMI RX~~''' '''~~Audio'''

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

|-

| style="text-align: left;"| '''RTC~~''' '''~~Chip'''

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

|-

| style="text-align: left;"| '''FAN~~''' '''~~interface'''

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

|-

| style="text-align: left;"| '''eMMC~~''' '''~~Extension ports'''

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

|-

| style="text-align: left;"| '''MaskROM~~''' '''~~button'''

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

|-

| style="text-align: left;"| '''Type-C ADB~~''' '''~~Function'''

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

|-

| style="text-align: left;"| '''Type-C DP~~''' '''~~Video'''

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

|-

| style="text-align: left;"| '''Type-C DP~~''' '''~~Audio'''

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

|}

'''Note that when entering the password,~~''' '''~~the specific content of the entered password will not be displayed on the screen, please do not think that there is any fault, just press Enter after inputting.'''

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

<li>By default, the Linux system automatically logs in to the terminal, and the default login user name is '''orangepi'''

[[File:~~./images/~~media/~~image274~~image197.png|387x253px]]</li>

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

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

[[File:~~./images/~~media/~~image275~~image198.png|576x324px|1]]

</div></li>

[[File:~~./images/~~media/~~image276~~image199.png|569x320px|IMG_256]]

</div>

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

<li>Then restart the system, it will automatically use the root user to log in to the desktop

[[File:~~./images/~~media/~~image277~~image200.png|362x152px]]

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

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

<li>There is a red, green and blue three-color light on the development board, and its location is shown in the figure below:

[[File:~~./images/~~media/~~image278~~image201.png|374x77px]]</li>

<li>'''As long as the development board is powered on, the red LED light will always be on, which is controlled by the hardware and cannot be turned off by the software. The red LED light can be used to determine whether the power supply of the development board is turned on normally.'''</li>

<li>The green and blue LED lights will keep blinking after the kernel boots, which is controlled by software.</li>

inet6 fe80::62b5:dc5e:728e:39a3/64 scope link noprefixroute

valid_lft forever preferred_lft forever

'''When using ifconfig to view the IP address, if the following information is prompted, it is because sudo is not added. The correct command is:~~''' '''~~sudo ifconfig'''

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

Command 'ifconfig' is available in the following places

'''There are three ways to check the IP address after the development board starts:'''

# '''Connect the HDMI display, then log in to the system and use the~~''' '''~~ip addr show~~''' '''~~command to view the IP address'''# '''Enter the~~''' '''~~ip addr show~~''' '''~~command in the debugging serial terminal to view the IP address'''

# '''If there is no debugging serial port and no HDMI display, you can also check the IP address of the development board's network port through the router's management interface. However, in this method, some people often cannot see the IP address of the development board normally. If you can't see it, the debug method looks like this:'''

<li>'''First check whether the Linux system has started normally. If the three-color light on the development board is flashing, it is generally started normally. If only the red light is on, it means that the system has not started normally;'''</li>

~~<li></li>~~

<li>'''Check whether the network cable is plugged in tightly, or try another network cable;'''</li>

<li>'''Try another router (I have encountered many problems with the router, such as the router cannot assign the IP address normally,~~''' '''~~or the IP address has been'''

'''assigned normally but cannot be seen in the router);'''</li>

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

'''First of all, please note that there is no WIFI module on the Orange Pi 5 Plus development board, and an external PCIe network card or USB network card is required to use the WIFI function.'''

'''For instructions on using the external PCIe network card, please refer to the section on~~''' '''~~how to use the PCIe WIFI6+Bluetooth module.'''

'''For instructions on using the external USB network card, please refer to the~~''' '''~~USB wireless network card test section.'''

'''Please do not connect to WIFI by modifying the~~''' '''~~/etc/network/interfaces~~''' '''~~configuration file. There will be problems connecting to the WIFI network in this way.'''

<li>If the development board is connected with a network cable, you > can '''remotely log in to the Linux system through ssh'''</li>

~~<li></li>~~

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

~~<li></li>~~

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

</li></ol>

[[File:~~./images/~~media/~~image279~~image202.png|575x250px|选区_011]]

</div></li>

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

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

[[File:~~./images/~~media/~~image280~~image203.png|345x215px]]</li>

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

[[File:~~./images/~~media/~~image281~~image204.png|349x216px]]</li>

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

[[File:~~./images/~~media/~~image283~~image205.png|358x226px]]</li>

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

[[File:~~./images/~~media/~~image285~~image206.png|357x226px]]</li>

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

[[File:~~./images/~~media/~~image286~~image207.png|352x225px]]</li>

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

[[File:~~./images/~~media/~~image287~~image208.png|349x223px]]</li>

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

'''The device node names of WIFI are not necessarily all wlan0, please refer to what you actually see.'''

<li>Click the network configuration icon in the upper right corner of the desktop (please do not connect the network cable when testing WIFI)

[[File:~~./images/~~media/~~image288~~image209.png|377x166px]]</li>

<li>Click '''More networks''' in the pop-up drop-down box to see all scanned WIFI hotspots, and then select the WIFI hotspot you want to connect to

[[File:~~./images/~~media/~~image289~~image210.png|576x353px]]</li>

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

[[File:~~./images/~~media/~~image290~~image211.png|320x163px]]</li>

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

[[File:~~./images/~~media/~~image291~~image212.png|576x308px]]</li>

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

[[File:~~./images/~~media/~~image293~~image213.png|574x222px]]</li></ol>

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

'''Please do not set a static IP address by modifying the~~''' '''~~/etc/network/interfaces~~''' '''~~configuration file.'''

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

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

[[File:~~./images/~~media/~~image294~~image214.png|234x234px]]</li>

<li>Then select the network interface that needs to set a static IP address, such as setting the static IP address of the Ethernet interface to select '''Wired connection 1''' or '''Wired connection 2'''

[[File:~~./images/~~media/~~image295~~image215.png|306x121px]]</li>

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

[[File:~~./images/~~media/~~image296~~image216.png|356x142px]]</li>

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

[[File:~~./images/~~media/~~image297~~image217.png|576x215px]]</li>

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

[[File:~~./images/~~media/~~image298~~image218.png|575x212px]]</li>

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

[[File:~~./images/~~media/~~image299~~image219.png|575x215px]]</li>

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

[[File:~~./images/~~media/~~image300~~image220.png|576x215px]]</li>

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

[[File:~~./images/~~media/~~image301~~image221.png|576x386px]]</li>

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

[[File:~~./images/~~media/~~image302~~image222.png|575x217px]]</li>

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

[[File:~~./images/~~media/~~image303~~image223.png|575x114px]]</li>

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

[[File:~~./images/~~media/~~image304~~image224.png|278x341px]]</li>

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

[[File:~~./images/~~media/~~image305~~image225.png|226x224px]]</li>

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

[[File:~~./images/~~media/~~image306~~image226.png|417x159px]]</li>

<li>Then re-select and enable '''Wired connection 2''', so that the static IP set earlier will take effect

[[File:~~./images/~~media/~~image307~~image227.png|414x160px]]</li>

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

[[File:~~./images/~~media/~~image308~~image228.png|260x224px]] [[File:~~./images/~~media/~~image309~~image229.png|225x225px]]</li>

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

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

| '''AX200'''

'''（PCIE+USB~~''' '''~~port)'''

| [[File:.media/~~images/%20media/image310~~image230.p%20ng]]

| '''Debian'''

| '''AX210'''

'''（PCIE+USB~~''' '''~~port)'''

| [[File:~~./images/~~media%20/~~image311~~image231.png]]{w idth=“1.06875in” height=“1.45in”}

| '''Debian'''

| '''RTL8852BE'''

'''（PCIE+USB~~''' '''~~port)'''

| [[File:.media/~~images/%20media/image312~~image232.p%20ng]]

| '''Debian'''

<li>Then insert the module into the M.2 E-Key interface of the development board and fix it. The position is shown in the figure below:

[[File:~~./images/~~media/~~image313~~image233.png|296x133px]]</li>

<li>Then open the configuration of the WIFI module in the Linux system, the steps are as follows:

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

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

[[File:~~./images/~~media/~~image314~~image234.png|374x173px]]</li>

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

[[File:~~./images/~~media/~~image315~~image235.png|373x162px]]</li>

<li>Then use the arrow keys of the keyboard to navigate to the > position shown in the figure below, and then use the space to > select the '''wifi-pcie''' configuration

[[File:~~./images/~~media/~~image316~~image236.png|298x40px]]</li>

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

[[File:~~./images/~~media/~~image317~~image237.png|297x80px]]</li>

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

[[File:~~./images/~~media/~~image318~~image238.png|255x71px]]</li>

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

[[File:~~./images/~~media/~~image319~~image239.png|256x113px]]</li></ol>

</li>

<li>If everything is normal after restarting the system, use the following command to see that there will be an additional WIFI device node. If you can't see it, please check if there is any problem with the previous configuration

root@192.168.1.xx's password: （Enter the password here, the default password is orangepi）

'''Note that when entering the password,~~''' '''~~the specific content of the entered password will not be displayed on the screen, please do not think that there is any fault, just press Enter after inputting.'''

'''If you are prompted to refuse the connection, as long as you are using the image provided by Orange Pi,~~''' '''~~please do not suspect that the password orangepi is wrong, but look for other reasons.'''

[[File:~~./images/~~media/~~image320~~image240.png|437x262px|953iring_001]]

</div>

[[File:~~./images/~~media/~~image322~~image241.png|575x292px|13]]

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

</li>

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

'''Note that when entering the password,~~''' '''~~the specific content of the entered password will not be displayed on the screen, please do not think that there is any fault, just press Enter after inputting.'''</li></ol>

[[File:~~./images/~~media/~~image323~~image242.png|576x192px]]

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

[[File:~~./images/~~media/~~image324~~image243.png|575x353px]]

test@test:~$ '''adb shell'''

'''root@orangepi5plus:/# <---~~''' '''~~After seeing this prompt, it means that you have successfully logged in to the development board'''

test@test:~$ '''adb reboot'''</li></ol>

'''If there is no adb tool in your Windows system, you can use the adb program in the RKDevTool software (this software is useful~~''' '''~~in the~~''' '''~~section on how to use RKDevTool to burn the Linux image to the TF card).'''

[[File:~~./images/~~media/~~image325~~image244.png|576x131px]]

'''An example using adb in Windows looks like this:'''

[[File:~~./images/~~media/~~image326~~image245.png|576x335px]]

<li>First prepare a good quality Type-C data cable

[[File:~~./images/~~media/~~image22~~image21.png|125x126px]]</li>

<li>Then connect the development board and Ubuntu PC through the Type-C data cable. The position of the Type-C interface of the development board is shown in the figure below:

[[File:~~./images/~~media/~~image244~~image173.jpeg|323x91px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-1.jpg未标题-1]]

</div></li>

test@test:~$ '''adb shell'''

'''root@orangepi5plus:/# <---~~''' '''~~After seeing this prompt, it means that you have successfully logged in to the development board'''

filename: 1 file pushed. 3.7 MB/s (1075091 bytes in 0.277s)</li></ol>

'''If there is no adb tool in your Windows system, you can use the adb program in the RKDevTool software (this software is useful~~''' '''~~in the section on how to use RKDevTool to burn the Linux image to the TF card).'''

[[File:~~./images/~~media/~~image325~~image244.png|576x131px]]

'''An example using adb in Windows looks like this:'''

[[File:~~./images/~~media/~~image327~~image246.png|576x304px]]

[[File:~~./images/~~media/~~image328~~image247.png|576x453px|截图 2022-12-03 19-04-40]]

</div></li>

[[File:~~./images/~~media/~~image330~~image248.png|575x128px|图片565]]

</div>

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

[[File:~~./images/~~media/~~image331~~image249.png|249x181px]]</li>

<li>Then choose to '''always trust this host''', and then click '''OK'''</li></ol>

[[File:~~./images/~~media/~~image332~~image250.png|278x150px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image333~~image251.png|533x330px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image334~~image252.png|529x414px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image335~~image253.png|472x171px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image336~~image254.png|384x276px]]

[[File:~~./images/~~media/~~image337~~image255.png|355x279px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image338~~image256.png|451x357px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image330~~image248.png|575x128px|图片565]]

</div>

[[File:~~./images/~~media/~~image340~~image257.png|207x146px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image341~~image258.png|221x109px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image342~~image259.png|449x332px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image343~~image260.png|461x340px|IMG_256]]

</div>

<li>There are two HDMI output interfaces on the development board, and their locations are shown in the figure below:

[[File:~~./images/~~media/~~image344~~image261.png|333x92px]]</li>

<li>By default, the Linux system configures HDMI_TX1 to support 8K display, and HDMI_TX2 supports only 4K display by default (only one HDMI_TX interface can support 8K display at a time). If you want to set HDMI_TX2 to support 8K display, please follow the steps below:

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

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

[[File:~~./images/~~media/~~image314~~image234.png|362x167px]]</li>

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

[[File:~~./images/~~media/~~image315~~image235.png|362x157px]]</li>

<li>Then use the arrow keys of the keyboard to navigate to the > position shown in the figure below, and then use the '''space''' > to select '''hdmi2-8k''' configuration

[[File:~~./images/~~media/~~image345~~image262.png|361x66px]]</li>

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

[[File:~~./images/~~media/~~image346~~image263.png|363x105px]]</li>

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

[[File:~~./images/~~media/~~image347~~image264.png|362x110px]]</li>

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

[[File:~~./images/~~media/~~image319~~image239.png|276x121px]]</li></ol>

</li>

<li>Then use HDMI to HDMI cable to connect Orange Pi development board and HDMI display

[[File:~~./images/~~media/~~image12~~image11.png|199x129px]]

'''Note, if you want to connect a 4K or 8K display, please make sure that the HDMI cable supports 4K or 8K video display.'''</li>

<li>After starting the linux system, if the HDMI display has image output, it means that the HDMI interface is in normal use</li></ol>

<li>The location of the HDMI In interface on the development board is as follows:

[[File:~~./images/~~media/~~image348~~image265.png|351x112px]]</li>

<li>First use the HDMI to HDMI cable shown in the figure below to connect the HDMI output of other devices to the HDMI In interface of the development board

[[File:~~./images/~~media/~~image12~~image11.png|199x129px]]</li>

<li>The HDMI In function of the Linux system is disabled by default, and the opening method is as follows:

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

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

[[File:~~./images/~~media/~~image314~~image234.png|362x167px]]</li>

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

[[File:~~./images/~~media/~~image315~~image235.png|362x157px]]</li>

<li>Then use the arrow keys of the keyboard to navigate to the > position shown in the figure below, and then use the '''space''' > to select the '''hdmirx''' configuration

[[File:~~./images/~~media/~~image349~~image266.png|359x82px]]</li>

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

[[File:~~./images/~~media/~~image346~~image263.png|363x105px]]</li>

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

[[File:~~./images/~~media/~~image347~~image264.png|362x110px]]</li>

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

[[File:~~./images/~~media/~~image319~~image239.png|276x121px]]</li></ol>

</li>

<li>Restart the system and open a terminal on the desktop, then run the '''test_hdmiin.sh''' script

[[File:~~./images/~~media/~~image350~~image267.png|576x324px|1]]

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

<li>HDMI to VGA Converter

[[File:~~./images/~~media/~~image351~~image268.png|155x104px]]</li>

<li>A VGA cable

[[File:~~./images/~~media/~~image352~~image269.png|148x133px]]</li>

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

</li>

<li>The HDMI to VGA display test is as follows:

[[File:~~./images/~~media/~~image353~~image270.png|575x341px]]

'''When using HDMI to VGA display, the development board and the Linux system of the development board do not need to make any settings, only the HDMI interface of the development board can display normally. So if there is a problem with the test, please check whether there is a problem with the HDMI to VGA converter, VGA cable and monitor.'''</li></ol>

<li>First open '''Display''' in '''Settings'''

[[File:~~./images/~~media/~~image354~~image271.png|576x370px]]</li>

<li>Then you can see the current resolution of the system

[[File:~~./images/~~media/~~image355~~image272.png|288x191px]]</li>

<li>Click the drop-down box of Resolution to see all resolutions currently supported by the monitor

[[File:~~./images/~~media/~~image356~~image273.png|353x233px]]</li>

<li>Then select the resolution you want to set, and click Apply

[[File:~~./images/~~media/~~image357~~image274.png|351x234px]]</li>

<li>After the new resolution is set, select '''Keep the configuration'''

[[File:~~./images/~~media/~~image358~~image275.png|462x251px]]</li></ol>

'''Please note that there is no Bluetooth module on the Orange Pi 5 Plus development board, and an external PCIe network card with Bluetooth or a USB network card with Bluetooth is required to use the Bluetooth function.'''

'''For instructions on using the external PCIe network card, please refer to the section on~~''' '''~~how to use the PCIe WIFI6+Bluetooth module.'''

'''For instructions on using the external USB network card, please refer to the~~''' '''~~USB wireless network card test section.'''

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

[[File:~~./images/~~media/~~image359~~image276.png|386x149px]]</li>

<li>Then select the adapter

[[File:~~./images/~~media/~~image360~~image277.png|375x165px]]</li>

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

[[File:~~./images/~~media/~~image361~~image278.png|248x85px]]</li>

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

[[File:~~./images/~~media/~~image362~~image279.png|243x229px]]</li>

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

[[File:~~./images/~~media/~~image363~~image280.png|438x179px]]</li>

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

[[File:~~./images/~~media/~~image364~~image281.png|322x217px]]</li></ol>

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

[[File:~~./images/~~media/~~image365~~image282.png|338x263px]]</li>

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

[[File:~~./images/~~media/~~image366~~image283.png|417x152px]]</li>

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

[[File:~~./images/~~media/~~image367~~image284.png|439x259px]]</li>

<li>The interface for sending pictures is as follows

[[File:~~./images/~~media/~~image368~~image285.png|437x253px]]</li></ol>

Support 2.4G WIFI+BT4.0

| [[File:~~./images/~~me%20dia/~~image369~~image286.png]]{width =“0.7868055555555555in” height= “0.8291666666666667in”}

|-

| 2

Support 2.4G +5G WIFI

| [[File:~~./images/~~me%20dia/~~image370~~image287.png]]{width =“0.8555555555555555in” height= “0.8145833333333333in”}

|-

| 3

Support BitTorrent 4.2

| [[File:~~./images/~~med%20ia/~~image371~~image288.jpeg|~~tb_image_share_1670 833201123~~tb_image_s hare_1670833201123]]{width =“0.8777777777777778in” height= “0.8777777777777778in”}

|}

TX bytes:23307 acl:0 sco:0 commands:125 errors:0</li>

<li>You can also see the bluetooth icon on the desktop. At this time, the bluetooth is not turned on, so a red '''x''' will be displayed

[[File:~~./images/~~media/~~image372~~image289.png|576x157px]]</li>

<li>Click '''Turn Bluetooth On''' to turn on Bluetooth

[[File:~~./images/~~media/~~image373~~image290.png|576x262px]]</li>

<li>The display after turning on Bluetooth is as follows

[[File:~~./images/~~media/~~image374~~image291.png|576x164px]]</li>

<li>For the test method of Bluetooth, please refer to the section on '''Bluetooth usage''', so I won’t go into details here</li></ol>

<li>First, you need to prepare a USB camera that supports the UVC protocol as shown in the figure below or similar, and then insert the USB camera into the USB port of the Orange Pi development board

[[File:~~./images/~~media/~~image19~~image18.png|277x160px]]</li>

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

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

'''In addition, the serial number of the video is not necessarily video0, please refer to what you actually see.'''</li>

<li>In the desktop system, Cheese can be used to directly open the USB camera. The method of opening Cheese is shown in the figure below:

[[File:~~./images/~~media/~~image375~~image292.png|474x302px]]

The interface after Cheese turns on the USB camera is shown in the figure below:

[[File:~~./images/~~media/~~image376~~image293.png|480x282px]]</li>

<li>Method of using fswebcam to test USB camera

<li>First open the file manager

[[File:~~./images/~~media/~~image377~~image294.png|257x126px]]</li>

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

[[File:~~./images/~~media/~~image379~~image295.jpeg|236x186px|图片10]]

</div></li>

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

[[File:~~./images/~~media/~~image380~~image296.png|241x195px]]</li>

<li>How to switch between different audio devices such as HDMI playback and headphone playback

<li>First open the volume control interface

[[File:~~./images/~~media/~~image381~~image297.png|294x161px]]</li>

<li>When playing audio, the audio device options that the playback > software can use will be displayed in '''Playback''', as shown > in the figure below, where you can set which audio device to > play to

[[File:~~./images/~~media/~~image382~~image298.png|575x303px]]</li></ol>

</li></ol>

<li>First insert the earphone into the earphone jack of the development board

[[File:~~./images/~~media/~~image383~~image299.png|365x89px]]</li>

<li>Then you can use the '''aplay -l''' command to view the sound card devices supported by the linux system. From the output below, you can see that '''card 3''' is the sound card device of es8388, that is, the sound card device of the headset

orangepi@orangepi:~$ '''aplay -l'''

<li>First, you need to prepare a speaker as shown in the figure below. The specification of the speaker seat on the development board is 2pin 1.25mm pitch

[[File:~~./images/~~media/~~image30~~image29.png|229x158px]]</li>

<li>The position of the speaker interface on the development board is as follows. After preparing the speaker, please insert it into the speaker interface of the development board

[[File:~~./images/~~media/~~image384~~image300.png|325x184px]]</li>

<li>The speaker and earphone use the same sound card. Before using the speaker, please make sure that the earphone jack is not plugged into the earphone (if the earphone is plugged in, the audio will be played to the earphone). Then use the '''aplay''' command to play the audio file that comes with the system. If the speaker can hear the sound, it means that the hardware can be used normally.

orangepi@orangepi:~$ '''aplay -D hw:3,0 /usr/share/sounds/alsa/audio.wav'''

<li>There is an onboard MIC on the development board, the location is as follows:

[[File:~~./images/~~media/~~image385~~image301.png|339x112px]]</li>

<li>Running the '''test_record.sh main''' command will record a piece of audio through the onboard MIC, and then play it to HDMI_TX1 and the headset.

orangepi@orangepi:~$ '''test_record.sh main'''

[[File:~~./images/~~media/~~image386~~image302.jpeg|575x166px|5725d46c4ff256fbd1d42ed5ba883f9f]]

</div>

~~<li></li>~~

<li>Please refer to the figure below for the order of the 40 pin expansion interface pins on the Orange Pi 5 Plus development board:

[[File:~~./images/~~media/~~image388~~image303.png|567x418px]]</li>

<li>The functions of the 40 pin interface pins on the Orange Pi 5 Plus development board are shown in the table below

<li>The following is the complete pin diagram of 40 pin

[[File:~~./images/~~media/~~image389~~image304.png|575x137px]]

The following is a color map containing some of the content in the above table:

[[File:~~./images/~~media/~~image390~~image305.png|575x199px]]</li>

<li>The table below is the picture of the left half of the complete > table above, so you can see it clearly

[[File:~~./images/~~media/~~image391~~image306.png|576x287px]]</li>

<li>The table below is the picture of the right half of the complete > table above, so you can see it clearly

[[File:~~./images/~~media/~~image392~~image307.png|575x263px]]'''The pwm in the above table has marked the base address of the corresponding register, which is useful when checking which pwmchip in~~''' '''~~/sys/class/pwm/~~''' '''~~corresponds to which pwm pin in the 40 pin header.'''</li></ol>

</li>

<li>There are a total of '''28''' GPIO ports in the 40 pin interface, and the voltage of all GPIO ports is '''3.3v'''.</li></ol>

[[File:~~./images/~~media/~~image393~~image308.png|575x403px|876iring_001]]

</div>

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

'''Note that Orange Pi 5 Plus needs to download the code of the wiringOP next branch, please don't miss the -b next parameter.'''

'''If you have problems downloading the code from GitHub, you can directly use the wiringOP source code that comes with the Linux image, and the storage location is:~~''' '''~~/usr/src/wiringOP'''</li>

<li>Compile and install wiringOP

orangepi@orangepi:~$ '''cd wiringOP'''

[[File:~~./images/~~media/~~image393~~image308.png|575x403px|876iring_001]]

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

[[File:~~./images/~~media/~~image394~~image309.png|575x145px|874iring_001]]

</div></li>

[[File:~~./images/~~media/~~image395~~image310.png|575x127px|874iring_002]]

</div></li>

[[File:~~./images/~~media/~~image396~~image311.png|575x131px|875iring_001]]

</div></li>

[[File:~~./images/~~media/~~image396~~image311.png|575x131px|875iring_001]]

</div></li>

<li>As can be seen from the figure below, the SPIs available for Orange Pi 5 Plus are SPI0 and SPI4

[[File:~~./images/~~media/~~image389~~image304.png|575x137px]]</li>

<li>The corresponding pins of SPI0 and SPI4 in 40pin are shown in the table below. SPI4_M1 and SPI4_M2 can only use one of them at the same time, and they cannot be used at the same time. They are all the same SPI4, but they are connected to different pins. Please don't think that they are two different sets of SPI buses.</li></ol>

| '''Pin 19'''

| '''Pin 12'''

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

|-

| '''MISO'''

| '''Pin~~''' '''~~21'''| '''Pin~~''' '''~~31'''

| '''Pin 10'''

|-

| '''CLK'''

| '''Pin~~''' '''~~23'''| '''Pin~~''' '''~~35'''| '''Pin~~''' '''~~22'''

|-

| '''CS0'''

| '''Pin~~''' '''~~24'''| '''Pin~~''' '''~~40'''| '''Pin~~''' '''~~31'''

|-

| '''CS1'''

| '''Pin~~''' '''~~26'''| '''Pin~~''' '''~~38'''

| '''none'''

|-

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

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

[[File:~~./images/~~media/~~image314~~image234.png|389x180px]]</li>

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

[[File:~~./images/~~media/~~image315~~image235.png|389x169px]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the > position shown in the figure below, and then use the '''space''' > to select the SPI configuration you want to open

[[File:~~./images/~~media/~~image397~~image312.png|388x132px]]</li>

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

[[File:~~./images/~~media/~~image346~~image263.png|391x113px]]</li>

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

[[File:~~./images/~~media/~~image347~~image264.png|404x123px]]</li>

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

[[File:~~./images/~~media/~~image319~~image239.png|332x146px]]</li></ol>

</li>

<li>After restarting, enter the system and first check whether there is a '''spidevx.x''' device node in the linux system. If it exists, it means that the SPI has been set up and can be used directly.

<li>As can be seen from the table below, the available i2c for Orange Pi 5 Plus is i2c2, i2c4, i2c5 and i2c8, a total of four sets of i2c buses.

[[File:~~./images/~~media/~~image389~~image304.png|575x137px]]</li>

<li>The corresponding pins of the 4 groups of I2C buses in 40pin are shown in the table below. I2C2_M0 and I2C2_M4 can only use one of them at the same time, and they cannot be used at the same time. They are all the same I2C2, but they are connected to different pins. Please don’t think that they are two different sets of I2C2 buses.</li></ol>

|-

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

| style="text-align: left;"| '''Pin~~''' '''~~3'''| style="text-align: left;"| '''Pin~~''' '''~~5'''

| style="text-align: left;"| '''i2c2-m0'''

|-

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

| style="text-align: left;"| '''Pin~~''' '''~~10'''| style="text-align: left;"| '''Pin~~''' '''~~8'''

| style="text-align: left;"| '''i2c2-m4'''

|-

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

| style="text-align: left;"| '''Pin~~''' '''~~22'''| style="text-align: left;"| '''Pin~~''' '''~~32'''

| style="text-align: left;"| '''i2c4-m3'''

|-

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

| style="text-align: left;"| '''Pin~~''' '''~~27'''| style="text-align: left;"| '''Pin~~''' '''~~28'''

| style="text-align: left;"| '''i2c5-m3'''

|-

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

| style="text-align: left;"| '''Pin~~''' '''~~29'''| style="text-align: left;"| '''Pin~~''' '''~~7'''

| style="text-align: left;"| '''i2c8-m2'''

|}

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

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

[[File:~~./images/~~media/~~image314~~image234.png|397x184px]]</li>

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

[[File:~~./images/~~media/~~image315~~image235.png|401x174px]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the > position shown in the figure below, and then use the '''space''' > to select the I2C configuration you want to open

[[File:~~./images/~~media/~~image398~~image313.png|406x153px]]</li>

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

[[File:~~./images/~~media/~~image346~~image263.png|380x109px]]</li>

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

[[File:~~./images/~~media/~~image347~~image264.png|355x108px]]</li>

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

[[File:~~./images/~~media/~~image319~~image239.png|323x142px]]</li></ol>

</li>

<li>After starting the linux system, first confirm that there are device nodes that need to use I2C under '''/dev'''

[[File:~~./images/~~media/~~image399~~image314.png|336x170px|521iring_001]]

</div>

<li>As can be seen from the table below, the uarts available for Orange Pi 5 Plus are uart1, uart3, uart4, uart6, uart7 and uart8, a total of 6 sets of uart buses

[[File:~~./images/~~media/~~image389~~image304.png|575x137px]]</li>

<li>The corresponding pins of the 6 groups of UART buses in 40pin are shown in the following table:</li></ol>

{| class="wikitable"

|-

| style="text-align: left;"| '''UART~~''' '''~~bus'''

| style="text-align: left;"| '''RX corresponds to 40pin'''

| style="text-align: left;"| '''TX corresponds to 40pin'''

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

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

[[File:~~./images/~~media/~~image314~~image234.png|403x186px]]</li>

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

[[File:~~./images/~~media/~~image315~~image235.png|413x179px]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the > position shown in the figure below, and then use the space to > select the UART configuration you want to open

[[File:~~./images/~~media/~~image400~~image315.png|408x144px]]</li>

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

[[File:~~./images/~~media/~~image346~~image263.png|405x117px]]</li>

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

[[File:~~./images/~~media/~~image347~~image264.png|401x122px]]</li>

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

[[File:~~./images/~~media/~~image319~~image239.png|320x141px]]</li></ol>

</li>

<li>After entering the linux system, first confirm whether there is a device node corresponding to uart under /dev

<li>As can be seen from the table below, the available PWM for Orange Pi 5 Plus includes six channels of PWM: pwm0, pwm1, pwm11, pwm12, pwm13 and pwm14

[[File:~~./images/~~media/~~image389~~image304.png|575x137px]]</li>

<li>The corresponding pins of PWM in 40pin are shown in the table below. Only one of PWM0_M0 and PWM0_M2, PWM1_M0 and PWM1_M2, PWM14_M0 and PWM14_M2 can be used at the same time, and they cannot be used at the same time. They are all the same PWM, but they are connected to different pins. Please don’t think that they are two different PWM bus.</li></ol>

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

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

[[File:~~./images/~~media/~~image314~~image234.png|416x192px]]</li>

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

[[File:~~./images/~~media/~~image315~~image235.png|457x198px]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the > position shown in the figure below, and then use the space to > select the PWM configuration you want to open

[[File:~~./images/~~media/~~image401~~image316.png|279x222px]]</li>

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

[[File:~~./images/~~media/~~image346~~image263.png|368x106px]]</li>

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

[[File:~~./images/~~media/~~image347~~image264.png|370x112px]]</li>

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

[[File:~~./images/~~media/~~image319~~image239.png|303x133px]]</li></ol>

</li>

<li>After opening a pwm, there will be an extra pwmchipX in '''/sys/class/pwm/''' (X is a specific number), for example, after opening pwm14, check the pwmchipX under '''/sys/class/pwm/''' two became three

[[File:~~./images/~~media/~~image402~~image317.png|576x77px|985iring_001]]

</div></li>

<li>Then it can be known from the table below that the base address of the pwm14 register is febf0020, and then look at the output of the '''ls /sys/class/pwm/ -l''' command, you can see that pwmchip2 is linked to febf0020.pwm, so pwm14 corresponds to pwmchip as pwmchip2

[[File:~~./images/~~media/~~image403~~image318.png|575x287px]]</li>

<li>Then use the following command to make pwm14 output a 50Hz square wave (please switch to the root user first, and then execute the following command)</li></ol>

root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip2/pwm0/enable'''

[[File:~~./images/~~media/~~image404~~image319.png|575x346px]]

<li>As can be seen from the table below, the available CAN bus for Orange Pi 5 Plus is CAN0 and CAN1, a total of two CAN buses

[[File:~~./images/~~media/~~image405~~image320.png|574x137px]]</li>

<li>In the linux system, the CAN in the 40 pin is closed by default, and it needs to be opened manually before it can be used. The detailed steps are as follows:

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

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

[[File:~~./images/~~media/~~image314~~image234.png|374x173px]]</li>

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

[[File:~~./images/~~media/~~image315~~image235.png|370x160px]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the > position shown in the figure below, and then use the space to > select the CAN configuration you want to open ('''can0-m0''' and > '''cam1-m0''' are optional for OPi 5 Plus)

[[File:~~./images/~~media/~~image406~~image321.png|370x61px]]</li>

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

[[File:~~./images/~~media/~~image346~~image263.png|332x96px]]</li>

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

[[File:~~./images/~~media/~~image347~~image264.png|341x103px]]</li>

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

[[File:~~./images/~~media/~~image319~~image239.png|283x125px]]</li></ol>

</li>

<li>After entering the Linux system, use the '''sudo ifconfig -a''' command, if you can see the CAN device node, it means that the CAN has been opened correctly

<li>The CANalyst-II analyzer used in the test is shown in the figure below

[[File:~~./images/~~media/~~image407~~image322.png|165x134px]]</li>

<li>CANalyst-II analyzer data download link

[https://www.zhcxgd.com/3.html '''https://www.zhcxgd.com/3.html''']</li>

<li>First install the software USBCANToolSetup

[[File:~~./images/~~media/~~image408~~image323.png|553x94px]]</li>

<li>The shortcut after installation of USBCANToolSetup is

[[File:~~./images/~~media/~~image409~~image324.png|59x80px]]</li>

<li>In addition, you need to install the USB driver

[[File:~~./images/~~media/~~image410~~image325.png|553x112px]]</li>

<li>The end of the USB interface of the CANalyst-II analyzer needs to be connected to the USB interface of the computer

[[File:~~./images/~~media/~~image411~~image326.png|137x121px]]</li>

<li>To test the CAN function, you need to prepare a CAN transceiver as shown in the figure below. The main function of the CAN transceiver is to convert the TTL signal of the CAN controller into the differential signal of the CAN bus

<li>The CANL pin of the CAN transceiver needs to be connected to the > H interface of the analyzer</li>

<li>The CANL pin of the CAN transceiver needs to be connected to the > L interface of the analyzer

[[File:~~./images/~~media/~~image412~~image327.png|243x78px]]</li></ol>

</li>

<li>Then you can open the USB-CAN software

[[File:~~./images/~~media/~~image413~~image328.png|553x267px]]</li>

<li>Then click to start the device

[[File:~~./images/~~media/~~image414~~image329.png|553x238px]]</li>

<li>Then click OK

[[File:~~./images/~~media/~~image415~~image330.png|279x110px]]</li>

<li>Set the baud rate to 1000k bps

[[File:~~./images/~~media/~~image416~~image331.png|322x268px]]</li>

<li>After successful opening, the USB-CAN software will display the serial number and other information

[[File:~~./images/~~media/~~image417~~image332.png|553x262px]]</li>

<li>Development board receives CAN message test

orangepi@orangepi:~$ '''sudo candump can0'''</li>

<li>Then send a message to the development board in the USB-CAN > software

[[File:~~./images/~~media/~~image418~~image333.png|553x188px]]</li>

<li>If the message sent by the analyzer can be received in the > development board, it means that the CAN bus can be used > normally

orangepi@orangepi5plus:~$ '''sudo candump can0'''

[[File:~~./images/~~media/~~image420~~image334.jpeg|483x377px|未标题-5]]

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

'''wiringOP-Python is the Python language version of wiringOP, which is used to operate the hardware resources of the development board, such as GPIO, I2C, SPI and UART, in the Python program.'''

'''In addition, please note that all the following commands are operated under the~~''' '''~~root~~''' '''~~user.'''

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

'''Note that the following~~''' '''~~git clone --recursive~~''' '''~~command will automatically download the source code of wiringOP, because wiringOP-Python depends on wiringOP. Please make sure that the download process does not report errors due to network problems.''''''If you have problems downloading the code from GitHub, you can directly use the wiringOP-Python source code that comes with the Linux~~''' '''~~image, and the storage location is:~~''' '''~~/usr/src/wiringOP-Python.'''

root@orangepi:~# '''git clone --recursive https://github.com/orangepi-xunlong/wiringOP-Python -b next'''

Cloning into 'wiringOP-Python'...

[[File:~~./images/~~media/~~image393~~image308.png|415x291px|876iring_001]]

</div>

[[File:~~./images/~~media/~~image394~~image309.png|419x106px|874iring_001]]

</div></li>

<li>As can be seen from the figure below, the SPIs available for Orange Pi 5 Plus are SPI0 and SPI4

[[File:~~./images/~~media/~~image389~~image304.png|575x137px]]</li>

<li>The corresponding pins of SPI0 and SPI4 in 40pin are shown in the table below. SPI4_M1 and SPI4_M2 can only use one of them at the same time, and they cannot be used at the same time. They are all the same SPI4, but they are connected to different pins. Please don't think that they are two different sets of SPI buses.</li></ol>

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

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

[[File:~~./images/~~media/~~image314~~image234.png|413x191px]]</li>

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

[[File:~~./images/~~media/~~image315~~image235.png|419x182px]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the > position shown in the figure below, and then use the space to > select the SPI configuration you want to open

[[File:~~./images/~~media/~~image397~~image312.png|415x141px]]</li>

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

[[File:~~./images/~~media/~~image346~~image263.png|415x120px]]</li>

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

[[File:~~./images/~~media/~~image347~~image264.png|414x126px]]</li>

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

[[File:~~./images/~~media/~~image319~~image239.png|293x129px]]</li></ol>

</li>

<li>After restarting, enter the system and first check whether there is a '''spidevx.x''' device node in the linux system. If it exists, it means that the SPI has been set up and can be used directly.

<li>As can be seen from the table below, the available i2c for Orange Pi 5 Plus is i2c2, i2c4, i2c5 and i2c8, a total of four sets of i2c buses.

[[File:~~./images/~~media/~~image389~~image304.png|575x137px]]</li>

<li>4组I2C总线在40pin中对应的引脚如下表所示。I2C2_M0和I2C2_M4同一时间只The corresponding pins of the 4 groups of I2C buses in 40pin are shown in the table below. I2C2_M0 and I2C2_M4 can only use one of them at the same time, and they cannot be used at the same time. They are all the same I2C2, but they are connected to different pins. Please don’t think that they are two different sets of I2C2 buses.</li></ol>

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

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

[[File:~~./images/~~media/~~image314~~image234.png|382x176px]]</li>

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

[[File:~~./images/~~media/~~image315~~image235.png|385x167px]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the > position shown in the figure below, and then use the space to > select the I2C configuration you want to open

[[File:~~./images/~~media/~~image398~~image313.png|381x144px]]</li>

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

[[File:~~./images/~~media/~~image346~~image263.png|347x100px]]</li>

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

[[File:~~./images/~~media/~~image347~~image264.png|325x98px]]</li>

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

[[File:~~./images/~~media/~~image319~~image239.png|254x112px]]</li></ol>

</li>

<li>After starting the linux system, first confirm that there is a device node corresponding to i2c under '''/dev'''

orangepi@orangepi:~$ '''ls /dev/i2c-*'''</li>

<li>Then connect an i2c device to the i2c pin of the 40 pin connector, here we take the ds1307 RTC module as an example

[[File:~~./images/~~media/~~image421~~image335.png|124x106px]]</li>

<li>Then use the '''i2cdetect -y''' command, if the address of the connected i2c device can be detected, it means that i2c can be recognized normally.

orangepi@orangepi:~$ '''sudo i2cdetect -y 2''' #i2c2 command

<li>As can be seen from the table below, the uarts available for Orange Pi 5 Plus are uart1, uart3, uart4, uart6, uart7 and uart8, a total of 6 sets of uart buses

[[File:~~./images/~~media/~~image389~~image304.png|575x137px]]</li>

<li>The corresponding pins of the 6 groups of UART buses in 40pin are shown in the following table:</li></ol>

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

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

[[File:~~./images/~~media/~~image314~~image234.png|404x186px]]</li>

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

[[File:~~./images/~~media/~~image315~~image235.png|403x175px]]</li>

<li>Then use the arrow keys on the keyboard to navigate to the > position shown in the figure below, and then use the '''space''' > to select the UART configuration you want to open

[[File:~~./images/~~media/~~image400~~image315.png|350x124px]]</li>

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

[[File:~~./images/~~media/~~image346~~image263.png|334x96px]]</li>

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

[[File:~~./images/~~media/~~image347~~image264.png|336x102px]]</li>

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

[[File:~~./images/~~media/~~image319~~image239.png|235x103px]]</li></ol>

</li>

<li>After entering the linux system, first confirm whether there is a device node corresponding to uart under /dev

[[File:~~./images/~~media/~~image422~~image336.png|527x211px|IMG_256]]

</div>

[[File:~~./images/~~media/~~image149~~image95.png|507x249px|IMG_256]]

</div></li>

[[File:~~./images/~~media/~~image423~~image337.png|429x263px|IMG_256]]

</div>

orangepi@orangepi:~/Desktop$ '''chmod +x balenaEtcher-1.7.9+5945ab1f-arm64.AppImage'''</li>

<li>Then select the AppImage version balenaEtcher, click the right > mouse button, and then click Execute to open balenaEtcher

[[File:~~./images/~~media/~~image424~~image338.png|145x118px]]</li></ol>

</li></ol>

== The installation method of the pagoda linux panel ==

'''Pagoda Linux panel is a server management software that improves operation and maintenance efficiency. It supports more than 100 server management functions such as one -click LAMP/LNMP/cluster/monitoring/website/FTP/database/Java (extracted from the~~''' '''~~official website of the pagoda)'''

<li>The order of compatibility recommendation of the pagoda Linux system is

'''Debian11~~''' '''~~> Ubuntu 22.04'''</li>

<li>Then enter the following command in the Linux system to start the installation of the pagoda

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

Do you want to install Bt-Panel to the /www directory now?(y/n): '''y'''</li>

<li>Then what to do is to wait patiently. When you see the printing information below the terminal output, it means that the pagoda has been installed. The entire installation process takes about 9 minutes. There may be some differences according to the difference in network speed

[[File:~~./images/~~media/~~image425~~image339.png|363x237px]]</li>

<li>At this time, enter the '''panel address''' displayed above in the browser to open the login interface of the pagoda Linux panel, and then enter the '''username''' and '''password''' displayed above in the corresponding position to log in to the pagoda.

[[File:~~./images/~~media/~~image426~~image340.png|576x241px]]</li>

<li>After successfully logging in to the pagoda, the following welcome interface will pop up. First, please take the intermediate user notice to read to the bottom, and then you can choose "I have agreed and read" User Agreement ", and then click" Enter the panel " You can enter the pagoda

[[File:~~./images/~~media/~~image427~~image341.png|576x213px]]</li>

<li>After entering the pagoda, you will first prompt that you need to bind the account of the pagoda official website. If you do n’t have an account, you can go to the official website of the pagoda '''(https://www.bt.cn)''' to register one

[[File:~~./images/~~media/~~image428~~image342.png|576x218px]]</li>

<li>The final display interface is shown in the figure below. You can intuitively see some status information of the development board Linux system, such as load status, CPU usage, memory usage, and storage space usage

[[File:~~./images/~~media/~~image429~~image343.png|574x283px]]</li>

<li>Test the SSH terminal login of the pagoda

<li>After opening the SSH terminal of the pagoda, you will first > prompt that you need to enter the password of the development > board system. At this time, enter '''orangepi''' in the password > box (the default password, if you have modification, please > fill in the modified one).

[[File:~~./images/~~media/~~image430~~image344.png|475x330px]]</li>

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

[[File:~~./images/~~media/~~image431~~image345.png|575x206px]]</li></ol>

</li>

<li>Software such as Apache, MySQL, and PHP can be installed in the software store of the pagoda. You can also deploy various applications in one click. Please explore it yourself

[[File:~~./images/~~media/~~image432~~image346.png|575x279px]]</li>

<li>Pagoda command line tool test

[[File:~~./images/~~media/~~image433~~image347.png|388x343px|815iring_001]]

</div></li>

<li>For more functions of the pagoda, please refer to the following information to explore by yourself

manual：[http://docs.bt.cn '''http://docs.bt.cn''']Forum address：[https://www.bt.cn/bbs '''https://www.bt.cn/bbs''']

GitHub Link：'''https://github.com/aaPanel/BaoTa'''</li></ol>

~~~~

~~== ==~~

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

~~<li></li>~~

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

~~<li></li>~~

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

~~</li>~~

~~<li></li>~~

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

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

<li>Then select '''zh_CN.UTF-8 UTF-8''' in the pop-up interface > (through the upper and lower direction keys on the keyboard to > move up and down, select it through the space key, and finally > move the cursor to '''<OK>''' through the Tab key, and then > press Enter key.)

[[File:~~./images/~~media/~~image434~~image348.png|575x296px]]</li>

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

[[File:~~./images/~~media/~~image435~~image349.png|575x160px]]</li>

<li>After exiting the interface,'''locale''' will be set. The output > displayed by the command line is shown below

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

Generating locales (this might take a while)...

en_US.UTF-8... done

</li>

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

[[File:~~./images/~~media/~~image436~~image350.png|575x361px]]</li>

<li>Then choose '''OK'''

[[File:~~./images/~~media/~~image437~~image351.png|295x212px]]</li>

<li>Then choose '''Yes'''

[[File:~~./images/~~media/~~image438~~image352.png|303x192px]]</li>

<li>Then choose '''fcitx'''

[[File:~~./images/~~media/~~image439~~image353.png|307x220px]]</li>

<li>Then choose '''OK'''

[[File:~~./images/~~media/~~image440~~image354.png|305x216px]]</li>

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

<li>Then Open '''Fcitx configuration'''

[[File:~~./images/~~media/~~image441~~image355.png|575x376px]]</li>

<li>Then click the “+” of the position shown in the figure below

[[File:~~./images/~~media/~~image442~~image356.png|280x187px]]</li>

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

[[File:~~./images/~~media/~~image443~~image357.png|291x196px]]</li>

<li>Then put '''Google Pinyin''' to the forefront

[[File:~~./images/~~media/~~image444~~image358.png|299x202px]][[File:~~./images/~~media/~~image445~~image359.png|300x202px]]</li>

<li>Then open the '''Geany''' Editor and test the Chinese input method.

[[File:~~./images/~~media/~~image446~~image360.png|349x212px]]</li>

<li>Chinese input method test is shown below

[[File:~~./images/~~media/~~image447~~image361.png|575x325px]]</li>

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

<li>If the entire system is required as Chinese, the variables in'''/etc/default/locale''' can be set to '''zh_CN.UTF-8'''

LANG='''zh_CN.UTF-8'''

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

<li>Then '''restart the system''' to see the system display as Chinese[[File:media/image362.png|576x356px]]</li></ol>

== ~~[[File:~~= ubuntu 20.~~/images/media/image448.png|576x356px]]~~ 04 system installation method ===

~~=== ===~~ ~~<ol start="17" style="list-style-type: decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li></ol></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~=== ubuntu 20.04 system installation method ===~~ <ol style="list-style-type: decimal;">

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

[[File:~~./images/~~media/~~image449~~image363.png|575x351px]]</li>

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

[[File:~~./images/~~media/~~image450~~image364.png|318x311px]]</li>

<li>Then use the left mouse button to select '''Chinese (China)''' and hold it down, and then drag it up to the beginning. The display after dragging is shown in the figure below：

[[File:~~./images/~~media/~~image451~~image365.png|324x320px]]</li></ol>

'''Note that this step is not very easy to drag, please try a few more times。'''

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

[[File:~~./images/~~media/~~image452~~image366.png|321x316px]]</li>

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

[[File:~~./images/~~media/~~image453~~image367.png|327x320px]]</li>

<li>'''Then restart the linux system to make the configuration effective'''</li>

<li>After re -entering the system, please choose '''not to ask me again''' at the interface below, and then determine whether the standard folder should be updated in Chinese according to your preference

[[File:~~./images/~~media/~~image454~~image368.png|303x247px]]</li>

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

[[File:~~./images/~~media/~~image455~~image369.png|575x383px]]</li>

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

[[File:~~./images/~~media/~~image456~~image370.png|576x292px]]</li><li>After opening '''Geany''', the default is an English input method. We can switch into Chinese input method through the '''Ctrl+Space''' shortcut keys, and then we can enter Chinese~~</li></ol>~~ <~~span id="section-36"~~p>~~===~~ [[File:~~./images/~~media/~~image457~~image371.png|575x308px]] ~~===~~ ~~<ol start="11" style="list-style-type: decimal;"><li>~~</~~li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li~~p></li></ol>

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

[[File:~~./images/~~media/~~image449~~image363.png|575x351px]]</li>

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

[[File:~~./images/~~media/~~image458~~image372.png|249x242px]]</li>

<li>Then please use the mouse to select '''Chinese (China)''' and hold it down, and then drag it up to the beginning. The display after the dragging is shown in the figure below:

[[File:~~./images/~~media/~~image459~~image373.png|267x262px]]</li></ol>

'''Note that this step is not very easy to drag, please try a few more times。'''

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

[[File:~~./images/~~media/~~image460~~image374.png|287x282px]]</li>

<li>'''Then restart the linux system to make the configuration effective'''</li>

<li>After re-entering the system, please choose '''not to ask me again''' at the interface below, and then determine whether the standard folder should be updated to Chinese according to your preference

[[File:~~./images/~~media/~~image454~~image368.png|303x247px]]</li>

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

[[File:~~./images/~~media/~~image455~~image369.png|575x383px]]</li>

<li>Then open the Fcitx5 configuration program

[[File:~~./images/~~media/~~image461~~image375.png|575x349px]]</li>

<li>Then choose to use Pinyin input method

[[File:~~./images/~~media/~~image462~~image376.png|338x267px]]</li>

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

[[File:~~./images/~~media/~~image463~~image377.png|366x290px]]</li>

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

[[File:~~./images/~~media/~~image456~~image370.png|576x292px]]</li>

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

[[File:~~./images/~~media/~~image464~~image378.png|434x308px]]</li></ol>

== How to remotely log in to the Linux system desktop method ==

'''Ubuntu Gnome Wayland~~''' '''~~image~~''' '''~~does not support nomachine and VNC described here to remotely log in to the desktop。'''

=== Use NoMachine remote login ===

'''Make sure the Ubuntu or Debian system installed on the development board is a~~''' '''~~desktop version. In addition, nomachine also provides detailed documents. It is strongly recommended to read this document to be familiar with the use of nomachine. The document links are shown below：'''

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

'''Note that this download link may change, please recognize the deb package of the Armv8/Arm64 version.'''

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

[[File:~~./images/~~media/~~image465~~image379.png|575x227px]]

<li>In addition, you can also download the installation package of > '''NoMachine''' in the '''official tools'''

[[File:~~./images/~~media/~~image466~~image380.png|70x86px]]

First Enter the '''remote login software-Nomachine''' Folder

[[File:~~./images/~~media/~~image467~~image381.png|256x46px]]

Then download the arm64 version of the deb installation package

[[File:~~./images/~~media/~~image468~~image382.png|180x109px]]</li>

<li>Then upload the downloaded '''nomachine_x.x.x_x_arm64.deb''' to the > Linux system of the development board</li>

<li>Then use the following command to install '''NoMachine''' in the Linux > system in the development board

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

[[File:~~./images/~~media/~~image469~~image383.png|575x163px]]

<li>Then install nomachine in Windows. '''Please restart the computer after installation'''</li>

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

[[File:~~./images/~~media/~~image470~~image384.png|76x66px]]</li>

<li>After Nomachine is started, it will automatically scan other devices installed in the local area network. After entering the main interface of Nomachine, you can see that the development board is already in the connected device list, and then click the location shown in the red box below in the figure below. You can start logging in to the Linux system desktop of the development board

[[File:~~./images/~~media/~~image471~~image385.png|321x92px]]</li>

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

[[File:~~./images/~~media/~~image472~~image386.png|269x184px]]</li>

<li>Then enter the username and password of the linux system in the corresponding position in the figure below, and then click '''OK''' to start logging in

[[File:~~./images/~~media/~~image473~~image387.png|303x204px]]</li>

<li>Then click OK in the next interface</li>

<li>Finally, you can see the desktop of the development board Linux system

[[File:~~./images/~~media/~~image474~~image388.png|411x246px]]</li></ol>

[[File:~~./images/~~media/~~image475~~image389.png|490x349px|图片1208]]

</div>

<li>Then enter the password of the previously set VNC

[[File:~~./images/~~media/~~image476~~image390.png|221x105px]]</li>

<li>The interface after the login is successfully displayed as shown in > the figure below, and then you can remotely operate the desktop of > the linux system remotely</li></ol>

[[File:~~./images/~~media/~~image477~~image391.png|405x293px]] ~~== ==~~ ~~=== ===~~ ~~<ol start="10" style="list-style-type: decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li></ol></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~=== ===~~ ~~<ol start="3" style="list-style-type: decimal;"><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li></ol>~~

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</li>

<li>'''hello_world.c''' program to write c language

orangepi@orangepi:~$ '''vim~~''' '''~~hello_world.c'''

#include <stdio.h>

int main(void)

'''Use CTRL+D shortcut key to exit Python's interactive mode。'''</li>

<li>'''hello_world.py''' program in Python language

orangepi@orangepi:~$ '''vim~~''' '''~~hello_world.py'''

print('Hello World!')</li>

<li>The results of running '''hello_world.py''' are shown below

<li>You can use the following command to install openjdk. The latest > version in Debian Bullseye is openjdk-17

orangepi@orangepi:~$ '''sudo~~''' '''~~apt install~~''' '''~~-y~~''' '''~~openjdk-17-jdk'''</li>

<li>After installation, you can check the version of Java

orangepi@orangepi:~$ '''java --version'''</li>

<li>Edit the '''hello_world.java''' of Java version

orangepi@orangepi:~$ '''vim~~''' '''~~hello_world.java'''

public class hello_world

{

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</li>

<li>The '''hello_world.c''' program that writes c language

orangepi@orangepi:~$ '''vim~~''' '''~~hello_world.c'''

#include <stdio.h>

int main(void)

'''Use CTRL+D shortcut key to exit Python's interactive mode。'''</li>

<li>The '''hello_world.py''' program that writes python language

orangepi@orangepi:~$ '''vim~~''' '''~~hello_world.py'''

print('Hello World!')</li>

<li>The results of running '''hello_world.py''' are shown below

<li>You can use the following command to install openjdk-17

orangepi@orangepi:~$ '''sudo~~''' '''~~apt install~~''' '''~~-y~~''' '''~~openjdk-17-jdk'''</li>

<li>After installation, you can check the version of the java

orangepi@orangepi:~$ '''java --version'''

OpenJDK 64-Bit Server VM (build 17.0.2+8-Ubuntu-120.04, mixed mode, sharing)</li>

<li>Edit the '''hello_world.java''' of Java version

orangepi@orangepi:~$ '''vim~~''' '''~~hello_world.java'''

public class hello_world

{

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</li>

<li>The '''hello_world.c''' program that writes c language

orangepi@orangepi:~$ '''vim~~''' '''~~hello_world.c'''

#include <stdio.h>

int main(void)

'''Use CTRL+D shortcut key to exit Python's interactive mode。'''</li>

<li>The '''hello_world.py''' program that writes python language

orangepi@orangepi:~$ '''vim~~''' '''~~hello_world.py'''

print('Hello World!')</li>

<li>The results of running '''hello_world.py''' are shown below

<li>You can use the following command to install openjdk-18

orangepi@orangepi:~$ '''sudo~~''' '''~~apt install~~''' '''~~-y~~''' '''~~openjdk-18-jdk'''</li>

<li>After installation, you can check the version of the java

orangepi@orangepi:~$ '''java --version'''

OpenJDK 64-Bit Server VM (build 18-ea+36-Ubuntu-1, mixed mode, sharing)</li>

<li>Edit the '''hello_world.java''' of Java version

orangepi@orangepi:~$ '''vim~~''' '''~~hello_world.java'''

public class hello_world

{

</li>

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

[[File:~~./images/~~media/~~image479~~image392.png|576x270px]]

You can also use the following command to open QT Creator

orangepi@orangepi:~$ '''qtcreator'''

'''libGL error: failed to load driver: rockchip'''</li>

<li>The interface after the QT Creator is opened is shown below

[[File:~~./images/~~media/~~image480~~image393.png|576x306px]]</li>

<li>The version of QT Creator is shown below

<li>The default version of QT Creator in '''Ubuntu20.04''' is shown > below

[[File:~~./images/~~media/~~image481~~image394.png|576x308px]]</li>

<li>The default version of QT Creator in '''Ubuntu22.04''' is shown > below

[[File:~~./images/~~media/~~image482~~image395.png|575x307px]]</li>

<li>The default version of QT Creator in '''Debian11''' is shown below

[[File:~~./images/~~media/~~image483~~image396.png|575x309px]]</li></ol>

</li>

<li>Then set the QT

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

[[File:~~./images/~~media/~~image484~~image397.png|573x164px]]</li>

<li>Then remove the hook of '''ClangCodeModel'''

[[File:~~./images/~~media/~~image485~~image398.png|575x359px]]</li>

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

<li>Then make sure that the GCC compiler used by QT Creator, if the > default is CLANG, please modify it to GCC

[[File:~~./images/~~media/~~image486~~image399.png|576x315px]][[File:~~./images/~~media/~~image487~~image400.png|575x307px]]</li></ol>

</li>

<li>Then you can open an example code

[[File:~~./images/~~media/~~image488~~image401.png|575x312px]]</li>

<li>After clicking the example code, you will automatically open the corresponding description document. You can carefully look at the instructions for the use

[[File:~~./images/~~media/~~image489~~image402.png|576x218px]]</li>

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

[[File:~~./images/~~media/~~image490~~image403.png|575x304px]]</li>

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

[[File:~~./images/~~media/~~image491~~image404.png|575x312px]]</li>

<li>After waiting for a while, the interface shown in the figure below will pop up. At this time, it means that QT can compile and run normally

[[File:~~./images/~~media/~~image492~~image405.png|576x308px]]</li>

<li>Reference information

[https://wiki.qt.io/Install_Qt_5_on_Ubuntu '''https://wiki.qt.io/Install_Qt_5_on_Ubuntu'''][https://download.qt.io/archive/qtcreator '''https://download.qt.io/archive/qtcreator'''][https://download.qt.io/archive/qt '''https://download.qt.io/archive/qt''']</li></ol>

== ROS installation method ==

=== Ubuntu 20.04 method of installing ROS 1 Noetic ===

~~<ol start="4" style="list-style-type: decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li></ol></li></ol>~~# The current active version of ROS 1 is shown below. The recommended version is '''Noetic Ninjemys'''

~~<~~[[File:media/~~span>=== ===~~image406.png|345x235px]]

~~<ol start="7" style="list-style-type~~[[File: ~~decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li></ol></li><~~media/~~ol>~~image407.png|576x210px]]

~~<~~[http:/~~span>=== ===~~/docs.ros.org/ '''http://docs.ros.org''']

~~<ol start="10" style="list-style-type~~'''https: ~~decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><~~/~~ol>~~</~~li><~~wiki.ros.org/~~ol>~~Distributions'''

<~~span id~~ol start="~~section~~2" style="list-style-44type: decimal;"><li>ROS 1 '''Noetic Ninjemys'''' official installation document links are shown below：[http://wiki.ros.org/noetic/Installation/Ubuntu '''http://wiki.ros.org/noetic/Installation/Ubuntu''']</li><li>Ubuntu 20.04 is recommended in the official installation document of ROS '''Noetic Ninjemys''', so please make sure that the system used in the development board is '''Ubuntu20.04 desktop version system'''[http://wiki.ros.org/noetic/Installation '''http://wiki.ros.org/noetic/Installation'''][[File:media/image408.png|312x176px]]</li><li>Then install Ros1 with the following script</~~span~~p>~~== ==~~orangepi@orangepi5plus:~$ '''install_ros.sh ros1'''</li><li>Before using the ROS tool, you need to initialize ROSDEP first, and then install some system dependencies and core components in some ROS when compiling the source code</li></ol>

~~<ol start="13" style="list-style-type: decimal;"><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li></ol></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~== ROS installation method ==~~ ~~=== Ubuntu 20.04 method of installing ROS 1 Noetic ===~~ ~~# The current active version of ROS 1 is shown below. The recommended version is '''Noetic Ninjemys'''~~ ~~[[File:./images/media/image493.png|345x235px]]~~ ~~[[File:./images/media/image494.png|576x210px]]~~ ~~'''http://docs.ros.org'''~~ ~~'''https://wiki.ros.org/Distributions'''~~ ~~<ol start="2" style="list-style-type: decimal;"><li>ROS 1 '''Noetic Ninjemys'''' official installation document links are shown below：'''http://wiki.ros.org/noetic/Installation/Ubuntu'''</li>~~<li>Ubuntu 20.04 is recommended in the official installation document of ROS '''Noetic Ninjemys''', so please make sure that the system used in the development board is '''Ubuntu20.04 desktop version system'''~~'''http://wiki.ros.org/noetic/Installation'''[[File:./images/media/image495.png|312x176px]]</li><li>Then install Ros1 with the following scriptorangepi@orangepi5plus:~$ '''install_ros.sh''' '''ros1'''</li><li>Before using the ROS tool, you need to initialize ROSDEP first, and then install some system dependencies and core components in some ROS when compiling the source code</li></ol>~~ '''Note that the following commands need to ensure that the development board can access GitHub normally, otherwise it will report an error due to network problems。'''

'''install_ros.sh~~''' '''~~script will try to modify/etc/hosts~~''' '''~~and run the following commands automatically. However, this method cannot guarantee that you can access github normally. If~~''' '''~~install_ros.sh~~''' '''~~has prompting the following errors after the~~''' '''~~ros1~~''' '''~~is installed, please think other methods to allow the linux system of the development board to access~~''' '''~~github~~''' '''~~normally, and then manually run the following manually command。'''

'''https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml'''

[[File:~~./images/~~media/~~image496~~image409.png|575x275px|图片4]]

</div></li>

[[File:~~./images/~~media/~~image497~~image410.png|576x275px|图片5]]

</div>

<li>At this time, press the direction button on the keyboard to control the small turtles up, down, left and right

[[File:~~./images/~~media/~~image498~~image411.png|575x296px]]</li></ol>

<li>The current active version of ROS 2 is shown below. The recommended version is '''Galactic Geochelone'''

[[File:~~./images/~~media/~~image499~~image412.png|576x271px]][[File:~~./images/~~media/~~image500~~image413.png|575x265px]][http://docs.ros.org/ '''http://docs.ros.org''']

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

<li>ROS 2 '''Galactic Geochelone''''s official installation document link is shown below：

[[File:~~./images/~~media/~~image501~~image414.png|576x324px|1]]

</div></li>

<li>How to use ROS, please refer to the document of ROS 2

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

[[File:~~./images/~~media/~~image502~~image415.png|576x324px|Screenshot from 2023-05-20 17-42-58]]

</div></li>

<li>Reference document

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

[http://docs.ros.org/en/galactic/Tutorials.html '''http://docs.ros.org/en/humble/Installation/Ubuntu-Install-Debians.html''']</li></ol>

<li>Use the following command to install the deb package of the kernel header file

'''The name of the kernel file deb package needs to be replaced with the actual name, please don’t copy it。'''

orangepi@orangepi:~$ '''sudo~~''' '''~~dpkg~~''' '''~~-i~~''' '''~~/opt/linux-headers-legacy-rockchip-rk3588_1.x.x_arm64.deb'''</li>

<li>After installation, you can see the folder where the kernel header file is located under the'''/usr/src'''

orangepi@orangepi:~$ '''ls /usr/src'''

<li>First write the code of the Hello kernel module, as shown > below：

orangepi@orangepi:~$ '''vim~~''' '''~~hello.c'''

#include <linux/init.h>

#include <linux/module.h>

MODULE_LICENSE("GPL");</li>

<li>Then write a makefile file that compiles the Hello kernel > module, as shown below：

orangepi@orangepi:~$ '''vim~~''' '''~~Makefile'''

ifneq ($(KERNELRELEASE),)

obj-m:=hello.o

endif</li>

<li>Then use the make command to compile the Hello kernel module, > and the output of the compilation process is shown below：

'''If you compile the code you copy here, if you have any problems, go to the~~''' '''~~official tool~~''' '''~~to download the source code and upload it to the Linux system of the development board for testing'''[[File:~~./images/~~media/~~image503~~image416.png|253x41px]]

orangepi@orangepi:~$ '''make'''

make -C /lib/modules/5.10.110-rockchip-rk3588/build M=/home/orangepi modules

hello.ko</li>

<li>Use the '''insmod''' command to insert the '''hello.ko''' kernel > module into the kernel

orangepi@orangepi:~$ '''sudo~~''' '''~~insmod hello.ko'''</li>

<li>Then use the '''demsg''' command to view the output of the > '''hello.ko''' kernel module. If you can see the output > instructions below, the hello.ko kernel module is loaded > correctly

orangepi@orangepi:~$ '''dmesg | grep "Hello"'''

[ 2871.893988] '''Hello Orange Pi -- init'''</li>

<li>Use the '''rmmod''' command to uninstall the '''hello.ko''' kernel > module

orangepi@orangepi:~$ '''sudo~~''' '''~~rmmod hello'''

orangepi@orangepi:~$ '''dmesg | grep "Hello"'''

[ 2871.893988] Hello Orange Pi -- init

<li>10.1 -inch MIPI LCD display+touch screen (this screen and > OPI5/OPI5B universal)

[[File:~~./images/~~media/~~image504~~image417.png|338x252px]]</li>

<li>Screen divert plate+31pin to 40pin line

[[File:~~./images/~~media/~~image505~~image418.png|230x199px|DD9A8F44-0D8F-4f06-9473-B539DEED850C]]

</div></li>

[[File:~~./images/~~media/~~image506~~image419.png|443x41px|C2164119-6EC3-49ae-9A95-BE323F51FAE1]]

</div></li>

<li>12pin touch screen row line

[[File:~~./images/~~media/~~image507~~image420.png|344x50px]]</li></ol>

</li>

<li>According to the figure below, the 12PIN touch screen row, 31PIN to 40PIN ducts, and 30pin MIPI cables get on the screen dial board. Pay attention to line of the touch screen the blue insulation face under . If you get an error, it will cause no display or unable to touch

[[File:~~./images/~~media/~~image508~~image421.png|574x142px]]</li>

<li>Place the connected rotor connected to the puzzle on the MIPI LCD screen according to the figure below, and connect the MIPI LCD screen and the rotary board through 31PIN to 40Pin row</li></ol>

[[File:~~./images/~~media/~~image509~~image422.png|382x563px]]

<li>Then connect the touch screen and the rotor board through the 12PIN touch screen line, pay attention to the orientation of the insulating surface.

[[File:~~./images/~~media/~~image510~~image423.png|253x161px]]</li>

<li>Finally connect to the LCD interface of the development board through the 30PIN MIPI duct

[[File:~~./images/~~media/~~image511~~image424.png|405x225px]]

'''Note that the touch interface below is not used for the LCD MIPI screen. It is currently a spare interface and cannot be used'''

[[File:~~./images/~~media/~~image512~~image425.png|334x70px]]</li></ol>

<li>The Linux image defaults to the configuration of the mipi lcd screen by default. If you need to use the mipi lcd screen, you need to open it manually。</li>

<li>The position of the development board MIPI LCD screen interface is shown below：

[[File:~~./images/~~media/~~image513~~image426.png|428x77px]]</li>

<li>The steps of opening the MIPI LCD configuration are shown below：

<li>First run the orangePi-config. Ordinary users remember to add > Sudo permissions

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

<li>Then choose '''System'''

[[File:~~./images/~~media/~~image314~~image234.png|379x175px]]</li>

<li>Then choos '''Hardware'''

[[File:~~./images/~~media/~~image315~~image235.png|379x164px]]</li>

<li>Then use the keyboard orientation to position the > '''opi5plus-lcd''', and then use the '''space''' to select

[[File:~~./images/~~media/~~image514~~image427.png|349x57px]]</li>

<li>Then select <Save>

[[File:~~./images/~~media/~~image515~~image428.png|263x123px]]</li>

<li>Then sele '''<Back>'''

[[File:~~./images/~~media/~~image516~~image429.png|264x116px]]</li>

<li>Then select the '''<Reboot>'''restart system to make the > configuration effective

[[File:~~./images/~~media/~~image517~~image430.png|226x105px]]</li></ol>

</li>

<li>After starting, you can see the display of the LCD screen as shown below (the default is vertical screen)：</li></ol>

[[File:~~./images/~~media/~~image518~~image431.png|169x244px]]

<li>2: Flip 180 degrees</li>

<li>3: Turn to 270 degrees clock

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

overlays=opi5plus-lcd

'''extraargs=cma=128M~~''' '''~~fbcon=rotate:3'''

'''Note that if/boot/orangepienv.txt is configured in the default default exiArgs = CMA = 128M, fbcon = rotate: 3 The configuration can be added to the extensraargs = cma = 128m (need to be separated by spaces)。'''</li></ol>

</li>

<li>First open '''Display''' settings in the Linux system

[[File:~~./images/~~media/~~image521~~image432.png|339x234px]]</li>

<li>Then select the direction you want to rotate in the '''Rotation'''

<li>'''Inverted''': Flipting up and down is equivalent to rotating 180 > degrees</li>

<li>'''Right''': Rotate 90 degrees to the right

[[File:~~./images/~~media/~~image522~~image433.png|330x208px]]</li></ol>

</li>

<li>Then click '''Apply'''

[[File:~~./images/~~media/~~image523~~image434.png|330x207px]]</li>

<li>Then click '''Keep this configuration'''

[[File:~~./images/~~media/~~image524~~image435.png|458x258px]]</li>

<li>At this time, the screen display has been rotated, and then the '''Display''' program is turned off</li>

<li>The above steps will only select the display direction, and it will not rotate the direction of touch. Use set_lcd_rotate.sh script to rotate the direction of touch. After this script is set, it will be automatically restarted, and then you can test whether the touch can be used normally

<li>'''Close the boot LOGO'''</li>

<li>'''Restart the system'''

'''The direction of the rotation touch is achieved by adding~~''' '''~~Option~~''' '''~~TransformationMatrix""x x x x x x x x x"in~~''' '''~~/usr/share/X11/xorg.conf.d/40-libinput.conf.~~''' '''~~Among them, "x x x x x x x x x" is different in different directions。'''</li></ol>

<li>Touch rotation reference materials

[https://wiki.ubuntu.com/X/InputCoordinateTransformation '''https://wiki.ubuntu.com/X/InputCoordinateTransformation''']</li></ol>

<li>OV13850 camera at 13 million MIPI interface

[[File:~~./images/~~media/~~image24~~image23.png|268x151px]]</li>

<li>13 million MIPI interface OV13855 camera

[[File:~~./images/~~media/~~image25~~image24.png|253x150px]]

The rotary board used by OV13850 and OV13855 cameras is the same as the FPC cable, but the two cameras are different from the position on the rotary board. The FPC lines are shown in the figure below. Please note that the FPC line is directed. It is marked that the '''TO MB''' must be inserted into the camera interface of the development board. It is marked that the end of '''TO CAMERA''' needs to be inserted on the camera transfer board。</li></ol>

[[File:~~./images/~~media/~~image525~~image436.png|373x78px]]

There are a total of 3 cameras on the camera to connect to the board, which can only be used one at the same time, as shown in the figure below, among which：

<li>The No. 3 interface is not used, just ignore it.</li></ol>

[[File:~~./images/~~media/~~image526~~image437.png|288x172px]]

Orange Pi 5 Plus development board has a total of 1 camera interface, which is shown below：

[[File:~~./images/~~media/~~image527~~image438.png|408x95px]]

The method of the camera inserted in the development board interface is shown below：

[[File:~~./images/~~media/~~image528~~image439.png|332x154px]]

After connecting the camera to the development board, we can use the following method to test the camera：

<li>First run the '''orangepi-config'''. Ordinary users remember to add '''sudo''' permissions

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

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

[[File:~~./images/~~media/~~image314~~image234.png|399x184px]]</li>

<li>Then choose '''Hardware'''

[[File:~~./images/~~media/~~image315~~image235.png|403x175px]]</li>

<li>Then use the keyboard to locate the position shown in the figure below, and then use the camera you want to open in the space. Among them, '''opi5plus-ov13850''' means using an OV13850 camera, '''opi5plus-ov13855''' indicates the use of OV13855 camera。

[[File:~~./images/~~media/~~image529~~image440.png|400x37px]]</li>

<li>Then choose '''<Save>'''

[[File:~~./images/~~media/~~image530~~image441.png|338x109px]]</li>

<li>Then choose '''<Back>'''

[[File:~~./images/~~media/~~image531~~image442.png|338x86px]]</li>

<li>Then select the'''<Reboot>''' restart system to make the configuration effective

[[File:~~./images/~~media/~~image319~~image239.png|316x139px]]</li>

<li>Then open a terminal in the desktop system and run the script below

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

[[File:~~./images/~~media/~~image532~~image443.png|576x324px|1]]

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

/dev/input/event10: SONiX USB Keyboard System Control

/dev/input/event11: PixArt USB Optical Mouse

Select the device event number [0-11]: '''0 #Select the serial number corresponding to~~''' '''~~Febf0030.pwm~~''' '''~~here'''

Input driver version is 1.0.1

Input device ID: bus 0x19 vendor 0x524b product 0x6 version 0x100

[[File:~~./images/~~media/~~image533~~image444.jpeg|199x183px|IMG_256]]

</div></li>

<li>Then press the button on the infrared receiver on the development board to press the button on the remote control. The position of the infrared receiver on the development board is as shown in the figure below：

[[File:~~./images/~~media/~~image534~~image445.png|346x92px]]</li>

<li>Then you can see that '''evtest''' will print the received key value

......

<li>A RTC battery interface is reserved on the development board, which is shown below：

[[File:~~./images/~~media/~~image29~~image28.png|344x126px]]</li>

<li>The RTC battery that needs to be purchased is shown below. The interface is 2pin, 1.25mm spacing

[[File:~~./images/~~media/~~image28~~image27.png|152x81px]]</li>

<li>The RTC chip used on the development board is Hym8563TS. This chip has the following characteristics：

<li>The development board is used for interfaces that connect the heat sink fan. The interface specifications are '''2pin 1.25mm''' spacing, '''5V voltage driver''', and the position of the fan interface is shown in the figure below：

[[File:~~./images/~~media/~~image20~~image19.png|410x171px]]</li>

<li>The fan on the development board can adjust the speed and switch through PWM, and the PWM pins used are '''PWM3_IR_M1'''</li>

<li>The Linux system uses the [https://github.com/orangepi-xunlong/linux-orangepi/blob/orange-pi-5.10-rk3588/drivers/hwmon/pwm-fan.c '''pwm-fan''' ] driver to control the fan by default. The DTS configuration used is shown below：

'''orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts'''

fan: pwm-fan {

Among it：

<li>'''pwms = <&pwm3~~''' '''~~0 50000 0>'''：The PWM of the control fan is > is PWM3。</li>

<li>'''cooling-levels = <0 50 100 150 200 255>'''：It is used to > configure the gear of the speed (PWM duty cycle). The number > and size of the gear can be defined by itself. Here are 6 > gears. The range of the speed is 0-255。</li>

<li>'''rockchip,temp-trips'''：It is used to configure the > corresponding relationship between the CPU temperature and the > fan speed gear. It can be adjusted according to actual needs. > The above configuration 50 degrees corresponding gear 1, 70 > degrees to the corresponding gear 5。

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

<li>In addition, the development board is equipped with a switch button, and you can also '''short press''' the switch button on the development board to turn off。

[[File:~~./images/~~media/~~image535~~image446.png|444x98px]]</li></ol>

'''Note that the Linux desktop system will pop up the confirmation box shown in the figure below after pressing the buttons. You need to click the~~''' '''~~Shut Down~~''' '''~~option to shut down.'''

[[File:~~./images/~~media/~~image536~~image447.png|256x240px]]

<li>After shutting down, press the switch button on the development board to turn on。

[[File:~~./images/~~media/~~image535~~image446.png|444x98px]]</li>

<li>Restart the command of the Linux system.

orangepi@orangepi:~$ '''sudo''' '''reboot'''</li></ol>

<li>First open the settings

[[File:~~./images/~~media/~~image537~~image448.png|243x181px]]</li>

<li>Then select about, if the '''Wayland''' description settings > displayed by '''Windowing System''' in a column are correct

[[File:~~./images/~~media/~~image538~~image449.png|362x303px]]</li></ol>

</li>

<li>When the '''Log Out''' is out of the system, it will enter the login interface below

[[File:~~./images/~~media/~~image539~~image450.png|258x108px]]</li>

<li>Please click the location shown below before logging in to the system again

[[File:~~./images/~~media/~~image540~~image451.png|259x108px]]</li>

<li>Then select '''Ubuntu on Wayland''' and enter the password login system

[[File:~~./images/~~media/~~image541~~image452.png|218x312px]]</li></ol>

<li>Open the settings first

[[File:~~./images/~~media/~~image537~~image448.png|221x164px]]</li>

<li>Then select '''Sound''', and then select the audio device you want to use in '''Output Device'''

[[File:~~./images/~~media/~~image542~~image453.png|375x314px]]</li></ol>

<li>Open a terminal on the desktop, and then enter the '''glmark2''' command. If you can see the '''Panfros''' after '''GL_VERDOR''', This shows that it is used in GPU.

orangepi@orangepi:~$ '''glmark2'''

[[File:~~./images/~~media/~~image543~~image454.png|381x258px]]</li>

<li>glmark2 running score test is generally more than 1,000 points

[[File:~~./images/~~media/~~image544~~image455.png|331x222px]]</li>

<li>Run '''gpu_load.sh''' script to view the current load of the GPU

orangepi@orangepi:~$ '''gpu_load.sh'''

[[File:~~./images/~~media/~~image545~~image456.png|529x281px]]</li></ol>

<li>First open the chromium browser

[[File:~~./images/~~media/~~image546~~image457.png|576x324px]]</li>

<li>Then enter '''chrome://gpu''' in the Chromium browser to view the support of GPU and video decoding

[[File:~~./images/~~media/~~image547~~image458.png|337x197px]]</li>

<li>Then you can open a video website to play a video file, or enter the following path name player to play a test video file in the browser.

'''/usr/local/test.mp4'''</li>

[[File:~~./images/~~media/~~image548~~image459.png|576x324px|Screenshot from 2023-05-22 15-01-46]]

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

<li>First log in the system

[[File:~~./images/~~media/~~image549~~image460.png|231x153px]] [[File:~~./images/~~media/~~image550~~image461.png|266x118px]]</li>

<li>When the login system will enter the login interface below

[[File:~~./images/~~media/~~image539~~image450.png|258x108px]]</li>

<li>Then click the location shown in the figure below

[[File:~~./images/~~media/~~image540~~image451.png|259x108px]]</li>

<li>Then select '''Kodi Wayland''', then enter the password login system

[[File:~~./images/~~media/~~image551~~image462.png|262x273px]]</li>

<li>The interface after Kodi is opened is displayed as shown below

[[File:~~./images/~~media/~~image552~~image463.png|461x259px|Screenshot from 2023-03-03 14-31-20]]

</div></li>

<li>Then click Settings

[[File:~~./images/~~media/~~image553~~image464.png|343x149px]]</li>

<li>Then select '''Player'''

[[File:~~./images/~~media/~~image554~~image465.png|474x268px]]</li>

<li>Then select '''Videos''', and then click '''Standard''' in the lower left corner

[[File:~~./images/~~media/~~image555~~image466.png|477x268px]]</li>

<li>After clicking twice, it will be switched to the '''Expert''' mode. The specific display is shown in the figure below

[[File:~~./images/~~media/~~image556~~image467.png|441x249px]]</li>

<li>Then open the '''Allow using DRM PRIME decoder''' in the P'''rocessing''' settings

[[File:~~./images/~~media/~~image557~~image468.png|442x250px]]</li>

<li>Then let's introduce a system's own test video test. You can also upload the video you want to play to the system, and then import and play

<li>First enter the main interface, then select '''Movies'''

[[File:~~./images/~~media/~~image558~~image469.png|424x239px]]</li>

<li>Then choose '''Add videos...'''

[[File:~~./images/~~media/~~image559~~image470.png|429x242px]]</li>

<li>Then choose '''Browse'''

[[File:~~./images/~~media/~~image560~~image471.png|428x270px]]</li>

<li>Then choose '''Root filesystem'''

[[File:~~./images/~~media/~~image561~~image472.png|414x169px]]</li>

<li>Then choose '''usr'''

[[File:~~./images/~~media/~~image562~~image473.png|416x273px]]</li>

<li>Then choose '''local'''

[[File:~~./images/~~media/~~image563~~image474.png|417x274px]]</li>

<li>Then choose '''OK'''

[[File:~~./images/~~media/~~image564~~image475.png|425x278px]]</li>

<li>Then choose '''OK'''

[[File:~~./images/~~media/~~image565~~image476.png|431x273px]]</li>

<li>Then choose OK

[[File:~~./images/~~media/~~image566~~image477.png|454x260px]]</li>

<li>Then enter the Local folder

[[File:~~./images/~~media/~~image567~~image478.png|456x258px]]</li>

<li>Then you can play '''test.mp4''' test video

[[File:~~./images/~~media/~~image568~~image479.png|462x262px]]</li></ol>

</li>

<li>When playing the video, you can run the '''vpu_debug.sh''' script under the command line (via SSH or serial port). If there is a print output below, it means that there is a hardware to decode the video

[ 1830.970563] rk_vcodec: fdc48100.rkvdec-core:1 session 3573:2 time: 2547 us

[ 1831.199650] rk_vcodec: fdc38100.rkvdec-core:0 session 3573:2 time: 2703 us</li>

<li>Play '''test.mp4''' video file CPU occupation rates of about '''20%~ 30%'''。[[File:media/image480.png|577x126px]]</li></ol>

==~~= [[File:./images/media/image569~~Ubuntu22.~~png|577x126px]] =~~04 Gnome to install ROS 2 Humble ==

<ol ~~start="3"~~ style="list-style-type: decimal;"><li><~~ol style="list-style-type: lower-alpha;"~~p>You can install ROS2 with '''install_ros.sh''' script<lip>orangepi@orangepi:~$ '''install_ros.sh ros2'''</li><li>install'''_ros.sh''' script will automatically run the '''ros2 -h''' command after ros2 is installed. If you can see the printing below</lip><lip>usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...</lip><lip>ros2 is an extensible command-line tool for ROS 2.</lip>optional arguments:</olp>-h, --help show this help message and exit</lip><lip>Commands:</lip>action Various action related sub-commands</olp>bag Various rosbag related sub-commands<~~span id="section~~p>component Various component related sub-~~46">~~commands</~~span~~p>~~=== ===~~ <~~ol start="8" style="list~~p>daemon Various daemon related sub-~~style-type: decimal;"~~commands<lip>doctor Check ROS setup and other potential issues</lip><lip>interface Show information about ROS interfaces<~~ol style="list-style-type: lower-alpha;"~~/p><lip>launch Run a launch file</lip><lip>lifecycle Various lifecycle related sub-commands</lip><lip>multicast Various multicast related sub-commands</lip><lip>node Various node related sub-commands</lip>param Various param related sub-commands</olp>pkg Various package related sub-commands</lip><lip>run Run a package specific executable</lip><lip>security Various security related sub-commands</lip><lip>service Various service related sub-commands</lip><lip>topic Various topic related sub-commands<~~ol style="list-style-type: lower-alpha;"~~/p><lip>wtf Use `wtf` as alias to `doctor`</lip><lip>Call `ros2 <command> -h` for more detailed usage.</li><li>Then you can use the '''test_ros.sh''' script to test whether the ROS 2 is successfully installed. If you can see the printing below, it means that the ROS 2 can run normally</lip><lip>orangepi@orangepi5plus:~$ '''test_ros.sh'''</lip>[INFO] [1671174101.200091527] [talker]: Publishing: 'Hello World: 1'</olp>[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: 1]</lip>[INFO] [1671174102.199572327] [talker]: Publishing: 'Hello World: 2'</olp> <~~!-- --~~p>[INFO] [1671174102.204196299] [listener]: I heard: [Hello World: 2]<~~ol start="5" style="list-style-type~~p>[INFO] [1671174103.199580322] [talker]: Publishing: 'Hello World: ~~decimal;"~~3'<lip>[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]</li><li>Run the following command to open rviz2</lip><lip>orangepi@orangepi:~$ '''source /opt/ros/humble/setup.bash'''</lip><lip>orangepi@orangepi:~$ '''ros2 run rviz2 rviz2'''</lip><~~/ol~~div class="figure">

~~<!-~~[[File:media/image481.png|576x324px|Screenshot from 2023- 05-22 15->~~<ol start="14" style="list~~17-~~style-type: decimal;"><li></li></ol>~~44]]

<~~span id="section~~/div></li><li>Reference document'''http://docs.ros.org/en/humble/index.html'''[http://docs.ros.org/en/galactic/Tutorials.html '''http://docs.ros.org/en/humble/Installation/Ubuntu-~~47"~~Install-Debians.html''']</~~span~~li></ol>~~== ==~~

<~~ol start~~span id="~~6" style="list~~set-the-chinese-environment-and-the-method-of-installing-the-chinese-~~style~~input-~~type: decimal;~~method">~~<li~~></lispan>~~<li></li><li></li><li></li><li></li></ol>~~== Set the Chinese environment and the method of installing the Chinese input method ==

<ol style="list-style-type: decimal;"><li>Open the settings first[[File:media/image448.png|243x181px]]</li><li>Then find the '''Region & Language''' option, and then click '''Manage Installed Languages''' options[[File:media/image482.png|576x352px]]</li><li>Then use the left mouse button to select '''Chinese (China)''' and hold it down, and then drag it up to the beginning. The display after the dragging is shown in the figure below：[[File:media/image483.png|575x428px]]</li><li>Then select the '''Apply System-48Wide''' to apply the Chinese settings to the entire system[[File:media/image484.png|576x427px]]</li><li>'''Then restart the linux system to make the configuration effective'''</li><li>After re -entering the system, please choose not to '''ask me again''' at the interface below, and then determine whether the standard folder should be updated to Chinese according to your preference[[File:media/image485.png|340x276px]]</li><li>Then you can see that the desktop is displayed as Chinese<div class=~~= ==~~"figure">

~~<ol style="list~~[[File:media/image486.png|576x324px|截图 2023-03-~~style~~08 09-~~type: lower~~34-~~alpha;"><li></li><li></li></ol>~~07]]

<~~!-- --~~/div><~~ol start="4" style="list-style-type: lower-alpha;"~~/li><li>Then open the Fcitx5 configuration program</lip><lip>[[File:media/image487.png|576x326px]]</li><li>Then choose to use Pinyin input method</lip><~~/ol~~div class="figure">

~~<!-- -~~[[File:media/image488.jpeg|576x429px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题->~~<ol start="10" style="list~~6.jpg未标题-~~style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~6]]

<~~span id="section-49"~~/div></~~span~~li>~~== ==~~<li>The interface after selecting is shown below, then click OK[[File:media/image489.png|504x373px]]</li><li>Then we can open the Chinese input method of '''Geany''' test, and the way to open is shown in the figure below[[File:media/image490.png|575x325px]]</li><li>After opening '''Geany''', the default is an English input method. We can switch into Chinese input method through the '''Ctrl+Space''' shortcut keys, and then we can enter Chinese[[File:media/image491.png|576x364px]]</li></ol>

<~~ol start~~span id="~~5" style="list~~orange-pi-os-arch-system-~~style~~use-~~type: decimal;~~instructions">~~<li~~></lispan>~~<li></li><li></li><li></li></ol>~~= Orange Pi OS Arch system use instructions =

== Orange Pi OS Arch system adaptation situation ==

~~<ol start~~{| class="6wikitable" |-| style="~~list~~text-~~style-type~~align: ~~decimal~~left;">| '''Function'''~~<li></li>~~| '''OPi OS Arch Gnome'''~~<li></li><li><ol~~ | style="~~list~~text-~~style-type~~align: ~~lower-alpha~~left;">| '''OPi OS Arch Xfce（To be released）'''~~<li></li>~~|-~~<li></li></ol></li><li><ol~~ | style="~~list~~text-~~style-type~~align: ~~lower-alpha~~left;">| '''HDMI TX1 video'''~~<li></li>~~| '''OK'''~~<li></li><li></li><li></li></ol></li><li></li></ol>~~ ~~~~| '''OK'''~~== ==~~|- ~~<ol start="4"~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">| '''HDMI TX1 Audio'''~~<li></li>~~| '''OK'''~~<li></li><li><ol~~ | style="~~list~~text-~~style-type~~align: ~~lower-alpha~~left;">| '''OK'''~~<li></li>~~|-~~<li></li><li></li></ol></li></ol>~~ ~~~~| '''HDMI TX2 video'''~~== ==~~| '''OK''' ~~<ol start="5"~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">| '''OK'''~~<li></li><li></li><li></li><li></li></ol>~~ ~~= =~~ ~~~~| '''HDMI TX2 Audio'''~~== ==~~| '''OK''' ~~-----~~ ~~-----~~ ~~~~| '''OK'''~~== ==~~ ~~== ==~~ ~~~~| '''HDMI RX video'''~~== ==~~| '''OK''' ~~~~| '''OK'''~~== ==~~ ~~== ==~~ ~~~~| '''HDMI RX Audio'''~~== Ubuntu22.04 Gnome to install ROS 2 Humble ==~~| '''OK''' ~~<ol~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">~~<li>You can install ROS2 with~~ | '''~~install_ros.sh~~OK''' ~~scriptorangepi@orangepi~~|-| style="text-align:~$ left;"| '''~~install_ros~~USB2.~~sh ros2~~0X2'''~~</li><li>install~~| '''~~_ros.sh~~OK''' ~~script will automatically run the~~ | style="text-align: left;"| '''~~ros2 -h~~OK''' ~~command after ros2 is installed. If you can see the printing belowusage: ros2 [-h] Call `ros2 <command>~~ |-~~h` for more detailed usage. ...ros2 is an extensible command~~| style="text-~~line tool for ROS 2.optional arguments~~align:~~-h, --help show this help message and exitCommands:action Various action related sub-commandsbag Various rosbag related sub-commandscomponent Various component related sub-commandsdaemon Various daemon related sub-commandsdoctor Check ROS setup and other potential issuesinterface Show information about ROS interfaceslaunch Run a launch filelifecycle Various lifecycle related sub-commandsmulticast Various multicast related sub-commandsnode Various node related sub-commandsparam Various param related sub-commandspkg Various package related sub-commandsrun Run a package specific executablesecurity Various security related sub-commandsservice Various service related sub-commandstopic Various topic related sub-commandswtf Use `wtf` as alias to `doctor`Call `ros2 &lt~~left;~~command> -h` for more detailed usage.</li><li>Then you can use the~~ "| '''~~test_ros~~USB3.sh0X2''' ~~script to test whether the ROS 2 is successfully installed. If you can see the printing below, it means that the ROS 2 can run normallyorangepi@orangepi5plus:~$~~ | '''~~test_ros.sh~~OK'''~~[INFO] [1671174101.200091527] [talker]: Publishing~~| style="text-align: left;"| '''OK''~~Hello World: 1~~'~~[INFO] [1671174101.235661048] [listener]: I heard: [Hello World: 1]~~|-~~[INFO] [1671174102.199572327] [talker]: Publishing~~| style="text-align: left;"| ''~~Hello World: 2~~'~~[INFO] [1671174102.204196299] [listener]: I heard: [Hello World:~~ 2~~][INFO] [1671174103~~.~~199580322] [talker]: Publishing:~~ 5G PCIe network port X2''~~Hello World: 3~~'~~[INFO] [1671174103.204019965] [listener]: I heard: [Hello World: 3]</li><li>Run the following command to open rviz2orangepi@orangepi:~$~~ | '''~~source /opt/ros/humble/setup.bash~~OK'''~~orangepi@orangepi~~| style="text-align:~$ left;"| '''~~ros2 run rviz2 rviz2~~OK'''~~<div class~~|-| style="~~figure~~text-align: left;"> ~~[[File:./images/media/image570.png|576x324px~~|~~Screenshot from 2023-05-22 15-17-44]]~~ ~~</div></li><li>Reference document~~'''~~http://docs~~2.~~ros.org/en/humble/index.html~~5G PCIe network portlight'''~~~~| '''~~http://docs.ros.org/en/humble/Installation/Ubuntu-Install-Debians.html~~OK'''~~</li></ol>~~ ~~~~| '''OK'''~~== Set the Chinese environment and the method of installing the Chinese input method ==~~|- ~~<ol~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">~~<li>Open the settings first[[File:./images/media/image537.png~~|~~243x181px]]</li><li>Then find the~~ '''~~Region & Language~~Debug serial port''' ~~option, and then click~~ | '''~~Manage Installed Languages~~OK''' ~~options[[File~~| style="text-align:~~./images/media/image571.png~~left;"|~~576x352px]]</li><li>Then use the left mouse button to select~~ '''~~Chinese (China)~~OK''' ~~and hold it down, and then drag it up to the beginning. The display after the dragging is shown in the figure below：[[File~~|-| style="text-align:~~./images/media/image572.png~~left;"|~~575x428px]]</li><li>Then select the~~ '''~~Apply System-Wide~~RTC chip''' ~~to apply the Chinese settings to the entire system[[File:./images/media/image573.png~~|~~576x427px]]</li><li>~~'''~~Then restart the linux system to make the configuration effective~~OK'''~~</li><li>After re~~ | style="text-~~entering the system, please choose not to~~ align: left;"| '''~~ask me again~~OK''' ~~at the interface below, and then determine whether the standard folder should be updated to Chinese according to your preference[[File:./images/media/image574.png|340x276px]]</li><li>Then you can see that the desktop is displayed as Chinese<div class="figure">~~ ~~[[File:./images/media/image575.png~~|~~576x324px|截图 2023~~-~~03-08 09-34-07]]~~ ~~</div></li><li>Then open the Fcitx5 configuration program[[File:./images/media/image576.png~~|~~576x326px]]</li><li>Then choose to use Pinyin input method<div class~~style="~~figure">~~ ~~[[File:./images/media/image577.jpeg|576x429px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~text-~~6.jpg未标题-6]]~~ ~~</div></li><li>The interface after selecting is shown below, then click OK[[File~~align:~~./images/media/image578.png~~left;"|~~504x373px]]</li><li>Then we can open the Chinese input method of~~ '''~~Geany~~FAN Fan interface''' ~~test, and the way to open is shown in the figure below[[File:./images/media/image579.png~~|~~575x325px]]</li><li>After opening~~ '''~~Geany''', the default is an English input method. We can switch into Chinese input method through the '''Ctrl+Space~~OK''' ~~shortcut keys, and then we can enter Chinese[[File:./images/media/image580.png~~|~~576x364px]]</li></ol>~~ ~~= Orange Pi OS Arch system use instructions =~~ ~~== Orange Pi OS Arch system adaptation situation ==~~ {| ~~class="wikitable"~~'''OK'''|-| style="text-align: left;"| '''~~Function~~eMMC Extension ports'''| '''~~OPi OS Arch Gnome~~OK'''| style="text-align: left;"| '''~~OPi OS Arch Xfce（To be released）~~OK'''|-| style="text-align: left;"| '''~~HDMI TX1 video~~AP6275P-WIFI'''

| '''OK'''

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

|-

| style="text-align: left;"| '''~~HDMI TX1 Audio~~AP6275P-BT'''

| '''OK'''

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

|-

~~| style="text-align: left;"| '''HDMI TX2 video'''| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI TX2 Audio'''| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI RX video'''| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI RX Audio'''| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''USB2.0X2'''| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''USB3.0X2'''| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''2.5G PCIe network port X2'''| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''2.5G PCIe network portlight'''| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Debug serial port'''| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''RTC chip'''| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''FAN Fan interface'''| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''eMMC Extension ports'''| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''AP6275P-WIFI'''| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''AP6275P-BT'''| '''OK'''| style="text-align: left;"| '''OK'''~~|-| style="text-align: left;"| '''AX200-WIFI'''

| '''OK'''

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

'''（PCIE+USB Port)'''

| [[File:.media/~~images/%20media/image310~~image230.p%20ng]]

| '''Debian'''

'''（PCIE+USB Port)'''

| [[File:~~./images/~~media%20/~~image311~~image231.png]]{w idth=“1.06875in” height=“1.45in”}

| '''Debian'''

'''（PCIE+USB Port)'''

| [[File:.media/~~images/%20media/image312~~image232.p%20ng]]

| '''Debian'''

<li>Then insert the WiFi module into the M.2 E-Key interface of the development board and fix it

[[File:~~./images/~~media/~~image313~~image233.png|403x181px]]</li>

<li>Then open the configuration of the WIFI module in the OPi OS Arch system, and the steps are shown below：

LINUX /Image

FDT /dtbs/rockchip/rk3588-orangepi-5-plus.dtb

'''FDTOVERLAYS /dtbs/rockchip/overlay/rk3588-wifi-pcie.dtbo~~''' '''~~#What needs to be added'''</li>

<li>'''Then restart the OPi OS Arch system'''</li></ol>

</li>

<li>First click the area in the upper right corner of the desktop

[[File:~~./images/~~media/~~image581~~image492.png|252x160px]]</li>

<li>Then choose Wi-Fi

[[File:~~./images/~~media/~~image582~~image493.png|337x215px]]</li>

<li>Then select the WIFI you want to connect

[[File:~~./images/~~media/~~image583~~image494.png|466x249px]]</li>

<li>Then enter the password of the wifi, and click '''Connect'''

[[File:~~./images/~~media/~~image584~~image495.png|284x188px]]</li>

<li>Then enter the following interface to see the wifi connection

[[File:~~./images/~~media/~~image585~~image496.png|544x383px]]</li></ol>

</li>

<li>Example of Bluetooth use：

<li>First click the area in the upper right corner of the desktop

[[File:~~./images/~~media/~~image581~~image492.png|272x173px]]</li>

<li>Then open the settings

[[File:~~./images/~~media/~~image586~~image497.png|288x238px]]</li>

<li>Then select Bluetooth in the settings, and make sure that the > switch button in the upper right corner of the Bluetooth is > opened

[[File:~~./images/~~media/~~image587~~image498.png|457x301px]]</li>

<li>Then choose the Bluetooth device you want to configure the > right, such as pairing with Android phones

[[File:~~./images/~~media/~~image588~~image499.png|451x296px]]</li>

<li>Then click '''Confirm''', the mobile phone also needs to confirm > the pairing

[[File:~~./images/~~media/~~image589~~image500.png|221x142px]]</li>

<li>The display of the Bluetooth and Android phone is shown below：

[[File:~~./images/~~media/~~image590~~image501.png|451x296px]]</li>

<li>Then click the paired Bluetooth device to pop up the operating > interface shown in the figure below

[[File:~~./images/~~media/~~image591~~image502.png|480x315px]]</li>

<li>Click '''Send Files...'''you can send a file to the phone</li></ol>

</li></ol>

[[File:~~./images/~~media/~~image592~~image503.png|525x297px]]

[[File:~~./images/~~media/~~image593~~image504.png|576x324px|Screenshot from 2023-04-21 04-17-07]]

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

<li>10.1 -inch MIPI LCD display+touch screen (common to OPI5/OPI5B)

[[File:~~./images/~~media/~~image504~~image417.png|308x237px]]</li>

<li>Screen divert+31pin to 40pin exhaust

[[File:~~./images/~~media/~~image505~~image418.png|160x139px|DD9A8F44-0D8F-4f06-9473-B539DEED850C]]

</div></li>

[[File:~~./images/~~media/~~image506~~image419.png|421x39px|C2164119-6EC3-49ae-9A95-BE323F51FAE1]]

</div></li>

<li>12pin touch screen line

[[File:~~./images/~~media/~~image507~~image420.png|300x44px]]</li></ol>

</li>

<li>According to the figure below, the 12PIN touch screen row, 31PIN to 40Pin line, and 30Pin MIPI cables get on the screen dial board. Pay attention to '''the blue insulation of the touch screen row line face to down'''. If an error is connected, it will cause no display or unable to touch..

[[File:~~./images/~~media/~~image508~~image421.png|574x142px]]</li>

<li>Place the connected rotor connected to the puzzle on the MIPI LCD screen according to the figure below, and connect the MIPI LCD screen and the rotary board through 31PIN to 40Pin row</li></ol>

[[File:~~./images/~~media/~~image509~~image422.png|382x563px]]

<li>Then connect the touch screen and the rotor board through the 12PIN touch screen line, pay attention to the orientation of the insulating surface

[[File:~~./images/~~media/~~image510~~image423.png|246x156px]]</li>

<li>Finally connect to the LCD interface of the development board through the 30PIN MIPI duct.

[[File:~~./images/~~media/~~image511~~image424.png|363x202px]]

'''Note that the touch interface below is not used for the LCD MIPI screen. It is currently a spare interface and cannot be used.'''

[[File:~~./images/~~media/~~image512~~image425.png|334x70px]]</li></ol>

<li>The position of the interface of the MIPI LCD screen on the development board is shown in the figure below

[[File:~~./images/~~media/~~image513~~image426.png|575x103px]]</li>

<li>OPi OS Arch image default is not to open the mipi lcd screen configuration. If you need to use the mipi lcd screen, you need to open it manually. The method of opening the mipi lcd configuration is shown below：

<li>First add the following configuration > in'''/boot/extlinux/extlinux.conf'''

[orangepi@orangepi ~]$ '''sudo~~''' '''~~vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

FDT /dtbs/rockchip/rk3588-orangepi-5-plus.dtb

'''FDTOVERLAYS~~''' '''~~/dtbs/rockchip/overlay/rk3588-opi5plus-lcd.dtbo~~''' '''~~#The configuration that needs to be added'''</li>

<li>'''Then restart the OPi OS Arch system'''</li></ol>

</li>

<li>After restarting, you can see the display of the LCD screen as shown below (default vertical screen)：</li></ol>

[[File:~~./images/~~media/~~image594~~image505.png|162x242px]]

<li>First click the area in the upper right corner of the desktop

[[File:~~./images/~~media/~~image581~~image492.png|193x123px]]</li>

<li>Then open the settings

[[File:~~./images/~~media/~~image586~~image497.png|193x159px]]</li>

<li>Then choose '''Displays'''

[[File:~~./images/~~media/~~image595~~image506.png|424x279px]]</li>

<li>Then select the direction you want to rotate in the '''Orientation''' of '''Displays'''

[[File:~~./images/~~media/~~image596~~image507.png|426x282px]]</li>

<li>Then choose '''Apply'''

[[File:~~./images/~~media/~~image597~~image508.png|425x282px]]</li>

<li>Then you can see that the screen has been rotated. At this time, you need to choose '''Keep Changes''' to determine the rotation

[[File:~~./images/~~media/~~image598~~image509.png|259x130px]]</li>

<li>The display of the LCD screen after 90 degrees is shown below：

[[File:~~./images/~~media/~~image599~~image510.png|359x229px]]</li>

<li>'''The touch function of the OPi OS Arch system LCD screen will rotate with the rotation of the display direction without other settings.'''</li></ol>

<li>OV13850 camera of 13 million MIPI interface

[[File:~~./images/~~media/~~image24~~image23.png|215x121px]]</li>

<li>13 million MIPI interface OV13855 camera

[[File:~~./images/~~media/~~image25~~image24.png|189x112px]]

The rotary board used by OV13850 and OV13855 cameras is the same as the FPC cable, but the two cameras are different from the position on the rotary board. The FPC lines are shown in the figure below. Please note that the FPC line is directed. It is marked that the '''TO MB''' must be inserted into the camera interface of the development board. It is marked that the end of '''TO CAMERA''' needs to be inserted on the camera transfer board。</li></ol>

[[File:~~./images/~~media/~~image525~~image436.png|370x77px]]

There are a total of 3 cameras on the camera to connect to the board, which can only be used at the same time, as shown in the figure below, of which：

<li>No. 3 interface is not used, just ignore it.</li></ol>

[[File:~~./images/~~media/~~image526~~image437.png|288x172px]]

Orange Pi 5 Plus development board has a total of 1 camera interface, which is shown below：

[[File:~~./images/~~media/~~image527~~image438.png|367x85px]]

The method of the camera inserted on the development board interface is shown below：

[[File:~~./images/~~media/~~image528~~image439.png|332x154px]]

After connecting the camera to the development board, we can use the following method to test the next camera：

<li>First add the following configuration in > '''/boot/extlinux/extlinux.conf'''

[orangepi@orangepi ~]$ '''sudo~~''' '''~~vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

[[File:~~./images/~~media/~~image600~~image511.png|576x324px|Screenshot from 2023-04-20 17-16-08]]

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

<li>First click the area in the upper right corner of the desktop

[[File:~~./images/~~media/~~image581~~image492.png|217x138px]]</li>

<li>Then open the settings

[[File:~~./images/~~media/~~image601~~image512.png|259x196px]]</li>

<li>Then find the '''Region & Language''' option

[[File:~~./images/~~media/~~image602~~image513.png|394x260px]]</li>

<li>Then choose '''Language'''

[[File:~~./images/~~media/~~image603~~image514.png|401x264px]]</li>

<li>Then select Chinese

[[File:~~./images/~~media/~~image604~~image515.png|443x290px]]</li>

<li>then click '''Select'''

[[File:~~./images/~~media/~~image605~~image516.png|443x292px]]</li>

<li>Then click '''Logout...''' log in to the system, and then log in to the system

[[File:~~./images/~~media/~~image606~~image517.png|395x260px]]</li>

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

[[File:~~./images/~~media/~~image607~~image518.png|498x280px|截图 2023-04-20 20-20-06]]

</div></li>

Enter a selection (default = all selected): '''1'''</li>

<li>Then open the Fcitx configuration program

[[File:~~./images/~~media/~~image608~~image519.png|395x223px]][[File:~~./images/~~media/~~image609~~image520.png|396x223px]]</li>

<li>Then add '''Google Pinyin''' input method

[[File:~~./images/~~media/~~image610~~image521.png|248x228px]][[File:~~./images/~~media/~~image611~~image522.png|372x252px]]</li>

<li>Then we can open a terminal test in the Chinese input method. After opening the terminal, if the English input method is still in English, we can switch to the Chinese input method through the '''Ctrl+Space''' shortcut keys, and then you can enter Chinese

[[File:~~./images/~~media/~~image612~~image523.png|459x258px|截图 2023-04-20 20-38-24]]

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

<li>The position of the development board HDMI In interface is shown below：

[[File:~~./images/~~media/~~image348~~image265.png|351x112px]]</li>

<li>First use the HDMI to HDMI line shown below to output the HDMI output of other devices to the HDMI In interface of the development board

[[File:~~./images/~~media/~~image12~~image11.png|199x129px]]</li>

<li>The OPi OS Arch system HDMI in function is closed by default, and the opening method is shown below：

<li>First add the following configuration in > '''/boot/extlinux/extlinux.conf'''

[orangepi@orangepi ~]$ '''sudo~~''' '''~~vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

FDT /dtbs/rockchip/rk3588-orangepi-5-plus.dtb

'''FDTOVERLAYS /dtbs/rockchip/overlay/rk3588-hdmirx.dtbo~~''' '''~~#The configuration that needs to be added'''</li>

<li>'''Then restart the OPi OS Arch system'''</li></ol>

</li>

[orangepi@orangepi ~]$ '''test_hdmiin.sh'''</li>

<li>Then you can see the input screen of the HDMI in (the HDMI in in the figure below shows the screen of the OPI5 development board HDMI output, and it is playing a video at this time). '''test_hdmiin.sh''' script defaults to the audio entered by HDMI in to the HDMI_TX1, HDMI_TX2 and ES8388 (representing speakers or headphones) of the development board.

[[File:~~./images/~~media/~~image613~~image524.png|576x326px]]</li>

<li>In addition to testing HDMI IN using '''test_hdmiin.sh''', we can also use '''Qt V4L2 test Utility''' to test HDMI in video ('''this method cannot test audio at present'''). The detailed steps are shown below：

<li>Enter the application list first

[[File:~~./images/~~media/~~image614~~image525.png|356x200px]]</li>

<li>Then find '''Qt V4L2 test Utility''' and open it

[[File:~~./images/~~media/~~image615~~image526.png|367x205px]]</li>

<li>Then make sure '''Qt V4L2 test Utility''' recognizes the HDMI In > device

[[File:~~./images/~~media/~~image616~~image527.png|508x185px]]</li>

<li>Then click the location shown in the figure below to see the > video entered by HDMI In

[[File:~~./images/~~media/~~image617~~image528.png|508x359px]]</li>

<li>The video window entered by HDMI In is shown below：

[[File:~~./images/~~media/~~image618~~image529.png|572x322px|Screenshot from 2023-05-22 18-12-56]]

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

== How to install wiringOP ==

'''Note that Wiringop has been pre -installed in the OPI OS Arch~~''' '''~~image~~''' '''~~released by Orange PI. Unless Wiringop's code is updated, it is not necessary to re -download and compile and install it,just use it directly.'''

'''After entering the system, you can run the gpio readall command. If you can see the output below, it means that wiringOP is pre -installed and can be used normally'''

[[File:~~./images/~~media/~~image619~~image530.png|434x308px]]

'''wiringOP is currently adapted to set the GPIO port input output, set the GPIO port output high and low level, and set the function of pulling and down resistance. It is impossible to use functions like hardware PWM.。'''

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

'''Note that Orange Pi 5 Plus needs to download the code of the wiringOP next branch, please don't miss the parameter of -b next。'''

'''If you have a problem with the download code from github, you can download the source code compression package of wiringOp.tar.gz in the~~''' '''~~official tools of the Orange Pi 5 Plus data download page'''[[File:~~./images/~~media/~~image620~~image531.png|356x88px]]</li>

<li>Compile and install wiringOP

[orangepi@orangepi ~]$ '''sudo pacman -Syy make gcc'''

[orangepi@orangepi wiringOP]$ '''sudo ./build'''</li>

<li>Test the output of the GPIO Readall command as follows

[[File:~~./images/~~media/~~image619~~image530.png|568x403px]]</li></ol>

FDT /dtbs/rockchip/rk3588s-orangepi-5.dtb

'''FDTOVERLAYS~~''' '''~~/dtbs/rockchip/overlay/rk3588-i2c1-m2.dtbo~~''' '''~~/dtbs/rockchip/overlay/rk3588-uart0-m2.dtbo'''

<li>A total of 28 GPIO ports can be used in the development board 40 PIN. Below is No. 7 pins -corresponding to GPIO1_D6 -corresponding WPI serial number 2 -as an example to demonstrate how to set the high and low level of the GPIO port

[[File:~~./images/~~media/~~image621~~image532.png|576x147px]]</li>

<li>First set the GPIO port as the output mode. The third parameter needs to enter the serial number of the wpi corresponding to the pins

[orangepi@orangepi ~]$ '''gpio mode~~''' '''~~2~~''' '''~~out'''</li>

<li>Then set the GPIO port output low level. After setting, you can use the value of the voltage of the pins with a multimeter. If it is 0V, it means that the low -power flat is set

[orangepi@orangepi ~]$ '''gpio write 2~~''' '''~~0'''</li>

<li>Then set the GPIO port output high level. After setting, you can use the value of the voltage of the pins with a multimeter. If it is 3.3V, it means that the high -power flat is set to be successful

[orangepi@orangepi ~]$ '''gpio write 2~~''' '''~~1'''</li></ol>

<li>Below the No. 7 pin — corresponding to GPIO1_D6 -corresponding WPI serial number 2 -to demonstrate how to set up and down pull -down resistance of the GPIO port

[[File:~~./images/~~media/~~image621~~image532.png|576x147px]]</li>

<li>First of all, you need to set the GPIO port as the input mode. The third parameter needs to enter the serial number of the wpi corresponding to the pins

[orangepi@orangepi ~]$ '''gpio mode~~''' '''~~2~~''' '''~~in'''</li>

<li>After the setting is set to input mode, execute the following command to set the GPIO port as the pull -down mode

[orangepi@orangepi ~]$ '''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 drawing mode is successful

[orangepi@orangepi ~]$ '''gpio read~~''' '''~~2'''

'''1'''</li>

<li>Then execute the following command to set the GPIO port as the drop-down mode

[orangepi@orangepi ~]$ '''gpio mode~~''' '''~~2~~''' '''~~down'''</li>

<li>Then enter the command below to read the level of the GPIO port. If the level is 0, it means that the drop -down mode is set successfully

[orangepi@orangepi ~]$ '''gpio read~~''' '''~~2'''

'''0'''</li></ol>

<li>As can be seen from the figure below, the SPI available for Orange Pi 5 Plus is SPI0 and SPI4

[[File:~~./images/~~media/~~image389~~image304.png|575x137px]]</li>

<li>The corresponding pins corresponding to SPI0 and SPI4 are shown in the table below. SPI4_M1 and SPI4_M2 can only be used at the same time, and they cannot be used at the same time. They are the same SPI4, but they are just getting different pins. Please don't think that they are two different SPI bus。</li></ol>

<li>First add the following configuration to the > '''/boot/extlinux/extlinux.conf'''

[orangepi@orangepi ~]$ '''sudo~~''' '''~~vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

<li>From the table below, the I2C available for Orange Pi 5 Plus is I2C2, I2C4, I2C5, and I2C8. There are four groups of I2C bus

[[File:~~./images/~~media/~~image389~~image304.png|575x137px]]</li>

<li>The corresponding pins corresponding to the 4 group I2C bus are shown below. I2C2_M0 and I2C2_M4 can only be used at the same time, and they cannot be used at the same time. They are the same I2C2, but they only receive different pins. Please don't think that they are two different I2C2 bus</li></ol>

<li>First add the following configuration in > '''/boot/extlinux/extlinux.conf'''.

[orangepi@orangepi ~]$ '''sudo~~''' '''~~vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

<li>As can be seen from the table below, the UART available for Orange Pi 5 Plus is UART1, UART3, UART4, UART6, UART7, and UART8. There are 6 sets of UART bus

[[File:~~./images/~~media/~~image389~~image304.png|575x137px]]</li>

<li>In the Linux system, the UART in 40 pin is closed by default, and it needs to be opened manually to use. The detailed steps are shown below：

<li>First add the following configuration to > the'''/boot/extlinux/extlinux.conf'''

[orangepi@orangepi ~]$ '''sudo~~''' '''~~vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

<li>From the table below, the PWMs available for Orange Pi 5 Plus include PWM0, PWM1, PWM11, PWM12, PWM13, and PWM14 a total of six PWM

[[File:~~./images/~~media/~~image389~~image304.png|575x137px]]</li>

<li>The corresponding pins of PWM in 40pin are shown below. PWM0_M0 and PWM0_M2, PWM1_M0 and PWM1_M2, PWM14_M0 and PWM14_M2 can only be used at the same time. They cannot be used at the same time. They are the same PWM, but they only get different pins. Please think that they are two different PWM bus</li></ol>

<li>First add the following configuration to > the'''/boot/extlinux/extlinux.conf'''

[orangepi@orangepi ~]$ '''sudo~~''' '''~~vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

{| class="wikitable"

|-

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

| style="text-align: left;"| '''Dtbo configuration'''

|-

[[File:~~./images/~~media/~~image622~~image533.png|575x78px|1010iring_001]]

</div></li>

<li>Then from the table below, the base address of the PWM14 register is FEBF0020, and then look at the output of the '''ls /sys/class/pwm/ -l''' command. You can see that the link in PWMCHIP2 is connected to Febf0020.PWM, so the PWM14 corresponds to PWMCHIP2

[[File:~~./images/~~media/~~image403~~image318.png|575x287px]]</li>

<li>Then use the following command to allow the PWM14 to output a 50Hz square wave (please switch to the root user first, and then execute the following command)</li></ol>

[root@orangepi ~]# '''echo~~''' '''~~0~~''' '''~~> /sys/class/pwm/pwmchip2/export'''

[root@orangepi ~]# '''echo~~''' '''~~20000000~~''' '''~~> /sys/class/pwm/pwmchip2/pwm0/period'''

[root@orangepi ~]# '''echo~~''' '''~~1000000~~''' '''~~> /sys/class/pwm/pwmchip2/pwm0/duty_cycle'''

[root@orangepi ~]# '''echo 1 > /sys/class/pwm/pwmchip2/pwm0/enable'''

[[File:~~./images/~~media/~~image404~~image319.png|575x346px]]

<li>As can be seen from the table below, the Canal bus available for Orange Pi 5 Plus is CAN0 and CAN1

[[File:~~./images/~~media/~~image405~~image320.png|574x137px]]</li>

<li>In the Linux system, the Can in 40 PIN is closed by default and needs to be opened manually to use. The detailed steps are shown below：

<li>First add the following configuration to > the'''/boot/extlinux/extlinux.conf'''

[orangepi@orangepi ~]$ '''sudo~~''' '''~~vim /boot/extlinux/extlinux.conf'''

LABEL Orange Pi

LINUX /Image

<li>After entering the Linux system, using the '''sudo~~''' '''~~ifconfig -a''' command If you can see the CAN device node, it means that the CAN has been opened correctly

[orangepi@orangepi ~]$ '''sudo pacman -Syy net-tools'''

[orangepi@orangepi ~]$ '''sudo~~''' '''~~ifconfig -a'''

can0: flags=128<NOARP> mtu 16

unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10 (UNSPEC)

<li>Use Canalyst-II analyzer to test CAN receiving messages, please refer to the content of the one-section of '''the Canalyst-II analyzer to test receive and send message'''</li></ol>

=~~= =~~Linux SDK——orangepi-build instructions =

<~~ol start~~span id="~~6" style="list~~compilation-~~style~~system-~~type: decimal;~~requirements">~~<li~~></lispan>~~<li></li><li></li><li></li><li></li></ol>~~== Compilation system requirements ==

~~== ==~~compile the Linux image of the development board on the x64 computer, or compile the Linux image of the development board on the Ubuntu22.04 system of the development board, please choose one according to your preference.'''

~~<ol start="13" style="list~~'''If you use orangepi-~~style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~build to compile the Linux image in the Ubuntu22.04 system of the development board, please do a good job of cooling (especially when the SSD starts). If the heat dissipation is not done well, it is prone to the error of file system runaway.'''

= == Compile with the Ubuntu22.04 system of the development board ===

<~~span id~~ol style="~~section~~list-63style-type: decimal;"><li>The Linux SDK, namely '''orangepi-build''', supports running on the '''Ubuntu 22.04''' of the development board (other systems have not been tested), so before downloading orangepi-build, please first ensure that the Ubuntu version installed on the development board is Ubuntu 22.04. The command to check the Ubuntu version installed on the development board is as follows. If the Release field does not display '''22.04''', it means that the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operations.orangepi@orangepi:~$ '''lsb_release -a'''No LSB modules are available.Distributor ID: UbuntuDescription: Ubuntu 22.04.1 LTS</~~span~~p>~~== ==~~Release: '''22.04'''Codename: jammy</li><li>'''Since the source codes such as the kernel and U-boot are stored on GitHub, it is very important to ensure that the development board can download codes from GitHub normally when compiling the image.'''</li></ol>

=== Compile with x64 Ubuntu22.04 computer ===

~~-----~~ ~~-----~~ ~~== ==~~ <ol ~~start="7"~~ style="list-style-type: decimal;"><li><~~/li~~p>The Linux SDK, '''orangepi-build''', supports running on computers with '''Ubuntu 22.04''' installed, so before downloading orangepi-build, please make sure that the Ubuntu version installed on your computer is Ubuntu 22.04. The command to check the Ubuntu version installed on the computer is as follows. If the Release field does not display '''22.04''', it means that the current Ubuntu version does not meet the requirements. Please replace the system before performing the following operations.</olp> ~~-----~~ test@test:~$ '''lsb_release -~~----~~ a'''<~~ol start="8" style="list-style-type: decimal;"~~/p><lip>No LSB modules are available.</lip><lip>Distributor ID: Ubuntu<~~ol style="list-style-type: lower-alpha;"~~/p><lip>Description: Ubuntu 22.04 LTS</lip><lip>Release: '''22.04'''</lip><~~/ol~~p>Codename: jammy</~~li><li~~p></li><li><~~ol style="list~~p>If the computer is installed with Windows system and there is no computer with Ubuntu 22.04 installed, you can consider using '''VirtualBox''' or '''VMware''' to install an Ubuntu 22.04 virtual machine in the Windows system. But please be careful not to compile orangepi-~~style~~build on the WSL virtual machine, because orangepi-~~type: lower~~build has not been tested in the WSL virtual machine, so it cannot be guaranteed that orangepi-~~alpha;">~~build can be used normally in WSL.<li/p></li><li><~~/li><li~~p>The download address of the installation image of Ubuntu 22.04 '''amd64''' version is：</lip><lip><[https://~~li><li><~~repo.huaweicloud.com/~~li><~~ubuntu-releases/~~ol>~~<21.04/~~li><li><ol style="list~~ubuntu-21.04-~~style~~desktop-~~type~~amd64.iso '''https: ~~lower~~//mirrors.tuna.tsinghua.edu.cn/ubuntu-releases/22.04/ubuntu-22.04-desktop-~~alpha;"><li>~~amd64.iso''']</lip><lip>or</lip><lip><'''https://repo.huaweicloud.com/ubuntu-releases/22.04/~~li><li>~~ubuntu-22.04.1-desktop-amd64.iso'''</~~li><li~~p></li><li><~~/li><li~~p>After installing Ubuntu 22.04 on the computer or virtual machine, please set the software source of Ubuntu 22.04 to Tsinghua source, otherwise it is easy to make mistakes due to network reasons when installing the software later</lip><~~li></li~~ol style="list-style-type: lower-alpha;"><li>For the method of replacing Tsinghua source, please refer to the > instructions on this web page</li></ol>

</li></ol>

~~<~~[https:/~~span>== ==~~/mirrors.tuna.tsinghua.edu.cn/help/ubuntu/ '''https://mirrors.tuna.tsinghua.edu.cn/help/ubuntu/''']

<ol start="2" style="list-style-type: lower-alpha;"><li>Note that the Ubuntu version needs to be switched to 22.04[[File:media/image534.png|576x241px]]</li><li>The content of the '''/etc/apt/sources.lis'''t file that > needs to be replaced istest@test:~$ '''sudo mv /etc/apt/sources.list /etc/apt/sources.list.bak'''test@test:~$ '''sudo vim /etc/apt/sources.list'''# By default, the source image is commented to improve the speed of apt update, you can uncomment it yourself if necessarydeb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiversedeb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiverse# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiversedeb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiverse# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-backports main restricted universe multiversedeb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-security main restricted universe multiverse# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-security main restricted universe multiverse# Pre-release software source, not recommended to enable# deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse~~=== ===~~# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse</li><li>After the replacement, you need to update the package information > and make sure there is no errortest@test:~$ '''sudo apt update'''</li><li>'''In addition, since the source codes such as the kernel and U-boot > are stored on GitHub, it is very important to ensure that the > computer can download codes from GitHub normally when compiling > the image.'''</li></ol>

<~~ol start~~span id="~~6" style="list~~get-the-~~style~~source-~~type: decimal;"><li><ol style="list~~code-~~style~~of-~~type: lower~~linux-~~alpha;~~sdk">~~<li~~></lispan>~~<li></li><li></li><li></li></ol></li><li></li><li></li><li></li><li></li></ol>~~== Get the source code of linux sdk ==

=== Download orangepi-build from github ===

~~<ol start="4" style="list~~# The linux sdk actually refers to the code of orangepi-~~style~~build. orangepi-~~type: decimal;"><li></li><li><ol style="list~~build is modified based on the armbian build system. Using orangepi-~~style~~build, multiple versions of linux images can be compiled. First download the code of orangepi-~~type: lower-alpha;"><li></li><li></li></ol></li><li></li></ol>~~build, the command is as follows：

~~=== ===~~get update'''

~~<ol start="9" style="list~~test@test:~$ '''sudo apt-~~style~~get install -~~type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~y git'''

~~<~~xunlong/~~span>== ==~~orangepi-build.git -b next'''

~~<ol start="3" style="list~~'''Note that the Orange Pi 5 Plus development board needs to download the source code of the next branch of orangepi-~~style~~build. The above git clone command needs to specify the branch of the orangepi-~~type: lower-alpha;"><li></li><li></li></ol>~~build source code as next.'''

<~~!-- --><ol start~~div class="4figure" ~~style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol~~>

~~<ol start="5" style="list-style-type~~[[File: ~~lower-alpha;"><li><~~media/~~li></ol>~~image535.png|576x298px|图片6]]

</div>

'''Downloading the orangepi-build code through the git clone command does not require entering the user name and password of the github account (the same is true for downloading other codes in this manual), if the Ubuntu PC prompts the user to enter the github account after entering the git clone command The name and password are usually entered incorrectly in the address of the orangepi-build warehouse behind the git clone. Please check the spelling of the command carefully, instead of thinking that we forgot to provide the username and password of the github account.'''

<ol start="2" style="list-style-type: decimal;"><li>The u---boot and linux kernel versions currently used by the development board are as follows</li></ol>

{| class="wikitable"

|-

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

| style="text-align: left;"| '''u-boot version'''

| style="text-align: left;"| '''linux kernel version'''

|-

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

| style="text-align: left;"| '''u-boot 2017.09'''

| style="text-align: left;"| '''linux5.10'''

|}

'''The branch mentioned here is not the same thing as the branch of the orangepi-~~----~~build source code, please do not confuse it. This branch is mainly used to distinguish different kernel source code versions.'''

~~<ol start="6" style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol>~~'''Currently, the linux5.10 bsp kernel provided by RK is defined as the legacy branch. If the mainline kernel is supported in the future, a current branch will be added.'''

~~== ==~~ <ol start="133" style="list-style-type: decimal;"><li><~~/li><li></li><li></li><li></li><li></li><li></li><li></li~~p>~~<li></li><li></li><li></li><li></li><li></li></ol>~~ ~~~~build will contain the following files and folders after downloading</~~span~~p>~~== ==~~ <ol ~~start="12"~~ style="list-style-type: ~~decimal~~lower-alpha;"><li><~~/li~~p>'''build.sh''': Compile the startup script<li/p></li><li><~~ol style="list-style-type~~p>'''external''': ~~lower-alpha~~Contains the configuration files needed to compile > the image, specific scripts, and the source code of some >">programs, etc.<li/p></li><li><~~/li~~p>'''LICENSE''': GPL 2 license file</olp></li><li><~~/li~~p>'''README.md''': orangepi-build documentation<li/p></li><li><~~ol style="list-style-type~~p>'''scripts''': ~~lower-alpha;"><li>~~General script for compiling linux images</lip><lip>test@test:~/orangepi-build$ '''ls'''</lip><lip>'''build.sh external LICENSE README.md scripts'''</lip><lip>'''If you downloaded the code of orangepi-build from github, after downloading, you may find that orangepi-build does not contain the source code of u-boot and linux kernel, nor does u-boot and linux kernel need to use cross-compilation tools Chain, this is normal, because these things are stored in other separate github warehouses or some servers (the addresses will be detailed below). orangepi-build will specify the address of u-boot, linux kernel and cross-compilation toolchain in the script and configuration file. When running orangepi-build, when it finds that there are no such things locally, it will automatically go to the corresponding place to download them.'''</~~li><li~~p></li></ol>

</li></ol>

== = Download the cross-compilation toolchain ===

~~<ol start="4" style="list~~'''The cross-~~style~~compilation toolchain will only be downloaded when the orangepi-~~type: decimal;"><li></li><li></li><li></li><~~build compilation image is used on an x64 computer. Compiling the linux image of the development board in the Ubuntu22.04 of the development board will not download the cross-compilation toolchain. At this time, orangepi-build/~~ol>~~toolchains will be an empty folder.'''

<~~span id~~ol style="~~section~~list-73style-type: decimal;"><li>When orangepi-build runs for the first time, it will automatically download the cross-compilation toolchain and put it in the toolchains folder. Every time after running the build.sh script of orangepi-build, it will check whether the cross-compilation toolchain in toolchains exists , if it does not exist, the download will be restarted, if it exists, it will be used directly, and the download will not be repeated.</~~span~~p><div class=~~= ==~~"figure">

~~<~~[[File:media/~~span>=== ===~~image536.png|575x278px|选区_396]]

</div></li><li>The image URL of the cross-compilation toolchain in China is the open source software image site of Tsinghua University[https://mirrors.tuna.tsinghua.edu.cn/armbian-releases/_toolchain/ '''https://mirrors.tuna.tsinghua.edu.cn/armbian-releases/_toolchain/''']</li><li>After '''toolchains''' is downloaded, it will contain multiple versions of cross-compilation toolchains, and the development board will only use two of themtest@test:~/orangepi-build$ '''ls toolchains/'''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnugcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihfgcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnugcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihfgcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabigcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabihfgcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnugcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabigcc-linaro-aarch64-none-elf-4.8-2013.11_linuxgcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linuxgcc-linaro-arm-none-eabi-4.8-2014.04_linux</li><li>The cross-compilation toolchain used to compile the linux kernel source code is<ol ~~start="5"~~ style="list-style-type: ~~decimal~~lower-alpha;"><li>linux5.10</lip>'''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''</li></ol></li><li>The cross-compilation tool chain used to compile the u-boot source code is<ol style="list-style-type: lower-alpha;"><li>v2017.09'''gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu'''</li></ol></li></ol>

<!span id="orangepi-build- complete-directory->~~<ol start="2" style="list-style~~structure-~~type: decimal;~~description">~~<li~~></~~li></ol~~span>=== orangepi-build complete directory structure description ===

<~~span id~~ol style="~~section~~list-style-75type: decimal;"><li>The orangepi-build repository does not contain the source code of the linux kernel, u-boot, and cross-compilation toolchain after downloading. The source code of the linux kernel and u-boot is stored in an independent git repository</~~span~~p>~~=== ===~~ <ol ~~start="7"~~ style="list-style-type: ~~decimal~~lower-alpha;"><li>The git warehouse where the linux kernel source code is stored > is as follows：'''https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-5.10-rk3588'''</li><li>The git warehouse where the u-boot source code is stored is as > follows：</lip>'''https://github.com/orangepi-xunlong/u-boot-orangepi/tree/v2017.09-rk3588'''</li></ol></li><li>When orangepi-build runs for the first time, it will download the cross-compilation toolchain, 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:</lip>a.'''build.sh''': compile startup scriptb.'''external''': Contains the configuration files needed to compile the image, scripts with specific functions, and the source code of some programs. The rootfs compressed package cached during the image compilation process is also stored in externalc.'''kerne'''l: stores the source code of the linux kernel. The folder named '''orange-pi-5.10-rk3588''' stores the kernel source code of the legacy branch of the RK3588/RK3588S series development boards. Please do not manually modify the name of the folder of the kernel source code. If it is modified, the kernel source code will be re-downloaded when the compilation system is runningd.'''LICENSE''': GPL 2 license filee.'''README.md''': orangepi-build documentationf.'''output''': Store compiled deb packages such as u-boot and linux, compilation logs, and compiled images and other filesg.'''scripts''': general scripts for compiling linux imagesh'''.toolchains''': store cross-compilation toolchaini.'''u-boot''': Store the source code of u-boot. The folder named '''v2017.09-rk3588''' stores the u-boot source code of the legacy branch of the RK3588/RK3588S series development boards. Please do not name the folder name of the u-boot source code Manual modification, if modified, the u-boot source code will be re-downloaded when the compilation system is runningj.'''userpatches''': Store configuration files needed to compile scripts<lip>test@test:~/orangepi-build$ '''ls'''</lip><lip>'''build.sh external kernel LICENSE output README.md scripts toolchains u-boot userpatches'''</li></ol>

==~~= =~~Compile u-boot ==

<ol ~~start="7"~~ style="list-style-type: decimal;"><li>Run the build.sh script, remember to add sudo permissiontest@test:~/orangepi-build$ '''sudo ./build.sh'''</li><li>Select '''U-boot package</lispan>''', then press Enter</olp><div class="figure">

[[File:media/image537.png|576x132px|选区_238]]

~~-----~~</div></li><li>Then select the model of the development board<div class="figure">

[[File:media/image538.png|576x289px|6]]

~~-----~~</div></li><ol li>Then it will start~~="9" style="list~~to compile u-~~style-type: decimal;"~~boot, and some information prompted during compilation is explained as follows~~<li>~~<ol style="list-style-type: lower-alpha;"><li>u-boot source code version[ o.k. ] Compiling u-boot [ '''v2017.09''' ]</li><li>The version of the cross-compilation toolchain</olp>[ o.k. ] Compiler version [ '''aarch64-linux-gnu-gcc 7.4.1''' ]</li><li>Path to the generated u-boot deb package</olp>[ o.k. ] Target directory [ '''orangepi-build/output/debs/u-boot''' ]</li><li>The package name of the generated u-boot deb package[ o.k. ] File name [ '''linux-u-boot-legacy-orangepi5plus_1.0.0_arm64.deb''' ]</li><li>Compilation time[ o.k. ] Runtime [ '''1 min''' ]</li><li>Repeat the command to compile u-boot, use the following command > to start compiling u-boot directly without selecting through > the graphical interface[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi5plus BRANCH=legacy BUILD_OPT=u-boot KERNEL_CONFIGURE=no''' ]</li></ol></li><li>View the u-boot deb package generated by compilationtest@test:~/orangepi-build$ '''ls output/debs/u-boot/'''linux-u-boot-legacy-orangepi5plus_1.0.0_arm64.deb</li><li>The files contained in the generated u-boot deb package are as follows<ol ~~start="2"~~ style="list-style-type: lower-alpha;"><li>Use the following command to decompress the deb packagetest@test:~/orangepi-build$ '''cd output/debs/u-boot'''test@test:~/orangepi_build/output/debs/u-boot$ $ '''sudo dpkg -x''' \'''linux-u-boot-legacy-orangepi5plus_1.0.0_arm64.deb . (Note that there is a "." at the end of the command)'''test@test:~/orangepi_build/output/debs/u-boot$ '''ls'''linux-u-boot-legacy-orangepi5plus_1.0.0_arm64.deb '''usr'''</li><li>The decompressed file is as followstest@test:~/orangepi-build/output/debs/u-boot$ '''tree usr'''usr└── lib├── linux-u-boot-legacy-orangepi5plus_1.0.0_arm64│ ├── idbloader.img│ ├── rkspi_loader.img│ └── u-boot.itb└── u-boot├── LICENSE├── orangepi_5_plus_defconfig└── platform_install.sh3 directories, 6 files</li></ol></li><!li>When the orangepi-bulid compilation system compiles the u- boot source code, it will first synchronize the u-boot source code with the u-boot source code of the github server, so if you want to modify the u-boot source code, you first need to turn off the download and update function of the source code '''(need This function can only be turned off after u-boot has been fully compiled, otherwise it will prompt that the source code of u-boot cannot be found. If the source code compressed package is downloaded from Google Drive, there is no such problem because the source code of u-boot cached)''', otherwise the changes made will be restored, the method is as follows：<~~ol start~~p>Set the IGNORE_UPDATES variable in userpatches/config-default.conf to "yes"test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''IGNORE_UPDATES="'''yes'''"</li><li>When debugging u-boot code, you can use the following method to update u-boot in the linux image for testing<ol style="list-style-type: ~~decimal~~lower-alpha;"><li>Upload the compiled u-boot deb package to the linux system of > the development boardtest@test:~/orangepi-build$ '''cd output/debs/u-boot'''test@test:~/orangepi_build/output/debs/u-boot$ '''scp \''''''linux-u-boot-legacy-orangepi5plus_1.0.0_arm64.deb [mailto:root@192.168.1.xxx:/root root@192.168.1.xxx:/root]'''</li><li>Then log in to the development board and uninstall the deb > package of u-boot installedroot@orangepi:~# '''apt purge -y linux-u-boot-orangepi5plus-legacy'''</li><li>Install the new u-boot deb package just uploadedroot@orangepi:~# '''dpkg -i''' '''linux-u-boot-legacy-orangepi5plus_1.0.0_arm64.deb'''</li><li>Then run the nand-sata-install script</olp>root@orangepi:~# '''nand-sata-install'''</li><li>Then select '''5 Install/Update the bootloader on SD/eMM''' to update the u-77boot in the TF card or '''7 Install/Update the bootloader on SPI Flash''' to update the u-boot in the SPI Flash[[File:media/image539.png|317x154px]]</li><li>After pressing the Enter key, a Warning will pop up first[[File:media/image540.png|314x170px]]</li><li>Press the Enter key again to start updating u-boot, and the > following information will be displayed after the update is > completed[[File:media/image541.png|223x125px]]</li>~~=== ===~~<li>Then you can restart the development board to test whether the > modification of u-boot takes effect</li></ol></li><li>Other useful information<ol ~~start="7"~~ style="list-style-type: ~~decimal~~lower-alpha;"><li>u-boot 2017.09 source code, the defconfig configuration file > used by the development board is</li><li>[https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/configs/orangepi_5_plus_defconfig '''orangepi-build/u-boot/v2017.09-rk3588/configs/orangepi_5_plus_defconfig''']u-boot > 2017.09 source code, the dts file used by the development > board is</li></ol></li></ol>

== [https://github.com/orangepi-xunlong/u-boot-orangepi/blob/v2017.09-rk3588/arch/arm/dts/rk3588-orangepi-5-plus.dts '''orangepi-build/u-boot/v2017.09-rk3588/arch/arm/dts/rk3588-orangepi-5-plus.dts''']Compile the linux kernel ==

<ol style="list-style-type: decimal;"><li>Run the build.sh script, remember to add sudo permissiontest@test:~/orangepi---build$ '''sudo ./build.sh'''</li><li>Select '''Kernel package''', then press Enter<div class="figure">

[[File:media/image542.png|575x116px|选区_240]]

~~-----~~</div></li><li>Then select the model of the development board<div class="figure">

~~<ol start="9" style="list-style-type~~[[File: ~~decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li></ol></li><~~media/~~ol>~~image538.png|576x289px|6]]

</div></li>

<li>Then it will prompt whether to display the kernel configuration interface. If you do not need to modify the kernel configuration, select the first one. If you need to modify the kernel configuration, select the second one.

[[File:media/image543.png|576x87px]]</li>

<li>If you choose to display the kernel configuration menu (the second option) in step 4), the kernel configuration interface opened by '''make menuconfig''' will pop up. At this time, you can directly modify the kernel configuration, save and exit after modification. Yes, after exiting, the kernel source code will be compiled

[[File:media/image544.png|575x400px]]</li></ol>

<!----- ~~-----~~><ol ~~start="2"~~ style="list-style-type: lower-alpha;"><li>If you do not need to modify the configuration options of the > kernel, when running the build.sh script, pass in > '''KERNEL_CONFIGURE=no''' to temporarily block the pop-up > kernel configuration interfacetest@test:~/orangepi-build$ '''sudo ./build.sh KERNEL_CONFIGURE=no'''</li><li>You can also set '''KERNEL_CONFIGURE=no''' in the > '''orangepi-build/userpatches/config-default.conf''' > configuration file, which can permanently disable this function</li><li>If the following error is displayed when compiling the kernel, it is > because the terminal interface of the Ubuntu PC is too small to > display the '''make menuconfig''' interface. Please > maximize the terminal of the Ubuntu PC and run the build.sh script > again[[File:media/image545.png|574x234px]]</li></ol>

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

~~<li></li>~~

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

~~~~

~~=== ===~~

<li>Part of the information prompted when compiling the kernel source code is as follows<ol style="list-style-type: lower-alpha;"><li>The version of the linux kernel source code[ o.k. ] Compiling current kernel [ '''5.10.110''' ]</li><li>The version of the cross-compilation toolchain used[ o.k. ] Compiler version [ '''aarch64-none-linux-gnu-gcc 11.2.1''' ]</li><li>The configuration file used by the kernel by default and the > path where it is stored[ o.k. ] Using kernel config file [ '''config/kernel/linux-rockchip-rk3588-legacy.config''' ]</li><li>The path of the deb package related to the kernel generated by > compiling[ o.k. ] Target directory [ '''orangepi-build/output/debs/''' ]</li><li>The package name of the compiled kernel image deb package[ o.k. ] File name [ '''linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb''' ]</li><li>The time used for compilation[ o.k. ] Runtime [ '''5 min''' ]</li><li>Finally, the compilation command to repeatedly compile the > kernel selected last time will be displayed. Use the following > command to start compiling the kernel source code directly > without selecting through the graphical interface[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi5plus BRANCH=legacy BUILD_OPT=kernel KERNEL_CONFIGURE=no''' ]</li></ol></li><li>View the deb package related to the kernel generated by compilation<ol style="list-style-type: lower-alpha;"><li>'''linux-dtb-legacy-rockchip-rk3588_1.0.0_arm64.deb''' Contains > dtb files used by the kernel</li><li>'''linux-headers-legacy-rockchip-rk3588_1.0.0_arm64.deb''' Include > kernel headers</li><li>'''linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb''' Contains > kernel images and kernel modulestest@test:~/orangepi-build$ '''ls output/debs/linux-*'''output/debs/linux-dtb-legacy-rockchip-rk3588_1.0.0_arm64.deb output/debs/linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deboutput/debs/linux-headers-legacy-rockchip-rk3588_1.0.0_arm64.deb</li></ol></li><li>The files contained in the generated linux-image deb package are as follows<ol style="list-style-type: lower-alpha;"><li>Use the following command to decompress the deb packagetest@test:~/orangepi-build$ '''cd output/debs'''</li></ol>

</li></ol>

test@test:~/orangepi_build/output/debs$ '''mkdir test'''

~~-----~~test@test:~/orangepi_build/output/debs$ '''cp \'''

'''linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb test/'''

~~-----~~test@test:~/orangepi_build/output/debs$ '''cd test'''

~~<ol start="2" style="list-style-type~~test@test: ~~lower-alpha;"><li><~~~/orangepi_build/output/~~li><~~debs/~~ol>~~test$ '''dpkg -x \'''

<!'''linux-image- legacy-rockchip->~~<ol start="8" style="list-style-type: decimal;"><li></li><li></li></ol>~~rk3588_1.0.0_arm64.deb .'''

test@test:~/orangepi_build/output/debs/test$ '''ls'''

'''boot etc lib''' linux-image-legacy-rockchip--rk3588_1.0.0_arm64.deb '''usr'''

<li>The decompressed file is as follows

test@test:~/orangepi-build/output/debs/test$ '''tree -L 2'''

.

├── boot

│ ├── config-5.10.110-rockchip-rk3588

│ ├── System.map-5.10.110-rockchip-rk3588

│ └── vmlinuz-5.10.110-rockchip-rk3588

├── etc

│ └── kernel

├── lib

│ └── modules

├── linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb

└── usr

├── lib

└── share</li></ol>

<ol start="109" style="list-style-type: decimal;"><li>The orangepi-bulid compilation system will first synchronize the linux kernel source code with the linux kernel source code of the github server when compiling the linux kernel source code, so if you want to modify the linux kernel source code, you first need to turn off the update function of the source code '''(you need to compile it once This function can only be turned off after the linux kernel source code, otherwise it will prompt that the source code of the linux kernel cannot be found. If the source code compressed package downloaded from Google Drive, there is no such problem, because the source code of linux has been cached)''', otherwise the The changes made will be reverted as follows:Set the IGNORE_UPDATES variable in '''userpatches/config-default.conf''' to "yes"test@test:~/orangepi-build$ '''vim userpatches/config-default.conf'''IGNORE_UPDATES="'''yes'''"</li><li>If the kernel has been modified, the following method can be used to update the kernel and kernel modules of the development board linux system<ol style="list-style-type: lower-alpha;"><li>Upload the deb package of the compiled linux kernel to the linux > system of the development boardtest@test:~/orangepi-build$ '''cd output/debs'''test@test:~/orangepi-build/output/debs$ '''scp \''''''linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb root@192.168.1.xxx:/root'''</li><li>Then log in to the development board and uninstall the deb > package of the installed linux kernelroot@orangepi:~# '''apt purge -y linux-image-legacy-rockchip-rk3588'''</li><li>Install the deb package of the new linux kernel just uploadedroot@orangepi:~# '''dpkg -i linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb'''</li><li>Then restart the development board, and then check whether the > kernel-related modifications have taken effectroot@orangepi:~# '''reboot'''</li></ol></li></ol>

<~~span id~~!-- --><ol start="~~section~~10" style="list-79style-type: decimal;"><li>Other useful information</~~span~~p><ol style=~~== ===~~"list-style-type: lower-alpha;"><li>The storage location of the kernel configuration file is as > follows, please do not go to the kernel source code to find > the kernel configuration file used by the development board</li><li>[https://github.com/orangepi-xunlong/orangepi-build/blob/next/external/config/kernel/linux-rockchip-rk3588-legacy.config '''orangepi-build/external/config/kernel/linux-rockchip-rk3588-legacy.config''']The > location of the dts file used by the development board is</li></ol></li></ol>

<~~ol start~~span id="~~9" style="list~~orangepi-buildkernelorange-pi-5.10-rk3588archarm64bootdtsrockchiprk3588-orangepi-5-~~style~~plus.dtscompile-~~type: decimal;~~rootfs">~~<li~~></lispan>== [https://github.com/orangepi-xunlong/linux-orangepi/blob/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts '''orangepi-build/kernel/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts'''<lispan id="_Toc25559" class="anchor"></~~li></ol~~span>]Compile rootfs ==

<li>Run the build.sh script, remember to add sudo permission

test@test:~/orangepi-build$ '''sudo ./build.sh'''</li>

<li>Select '''Rootfs and all deb packages''', then press Enter</li></ol>

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

[[File:media/image546.png|576x119px|选区_241]]

~~-----~~</div><ol start="113" style="list-style-type: decimal;"><li><~~ol style="list-style-type: lower-alpha;"><li></li~~p>Then select the model of the development board</olp><~~/li></ol~~div class="figure">

[[File:media/image538.png|576x289px|6]]

~~-----~~</div></li><li>Then select the type of rootfs (mainly maintain '''bullseye/focal/jammy''' at present)<div class="figure">

[[File:media/image547.png|575x180px|7]]

~~-----~~</div></li><li>Then select the type of image

<li>'''Image with console interface (server)''' Indicates the image of > the server version, which is relatively small</li><li>'''Image with desktop environment''' Indicates a mirror image with > a desktop, which is relatively large</olp><div class="figure">

~~<ol start="12" style="list-style-type~~[[File: ~~decimal;"><li><~~media/~~li><li></li><li></li><li></li><li></li></ol>~~image548.png|576x75px|选区_245]]

<~~span id="section~~/div></li></ol></li><li>If you are compiling the image of the server version, you can also choose to compile the Standard version or the Minimal version. The pre-installed software of the Minimal version will be much less than that of the Standard version '''(please do not choose the Minimal version if there is no special requirement, because many things are not pre-~~80">~~installed by default. Some functions may not be available)'''</~~span~~p><div class=~~== ===~~"figure">

~~<~~[[File:media/~~span>==== ====~~image549.png|576x78px|选区_397]]

<~~ol start="6" style="list-style-type: decimal;"><li~~/div></li><li><~~ol style="list-style-~~p>If you are compiling the image of the desktop version, you need to select the type~~: lower-alpha;"><li></li>~~of desktop environment. Currently, Ubuntu Jammy mainly maintains XFCE and Gnome desktops, Ubuntu Focal only maintains XFCE desktops, and Debian Bullseye mainly maintains XFCE and KDE desktops</olp><~~/li></ol~~div class="figure">

[[File:media/image550.png|575x99px|Selection_001]]

</div>[[File:media/image551.png|576x74px]]You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.[[File:media/image552.png|575x264px]]</li><li>Then it will start to compile rootfs, and some of the information prompted during compilation are as follows<ol style="list-style-type: lower-alpha;"><li>The type of rootfs[ o.k. ] local not found [ Creating new rootfs cache for '''jammy''']</li><li>The storage path of the compiled rootfs compressed package[ o.k. ] Target directory [ '''external/cache/rootfs''' ]</li><li>The name of the rootfs compressed package generated by > compilation[ o.k. ] File name [ '''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' ]</li><li>The time used for compilation[ o.k. ] Runtime [ '''13 min''' ]</li></ol></li><li>View the rootfs compressed package generated by compilation<ol style="list-style-type: lower-alpha;"><li>'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' is > the rootfs compressed package, the meaning of each field of > the name is<ol ~~start="2"~~ style="list-style-type: lower-alpha;"><li>'''jammy''' indicates the type of linux distribution of rootfs</li><li>'''xfce''' means rootfs is the type of desktop version, if it > is '''cli''', it means the type of server version</li><li>'''arm64''' represents the architecture type of rootfs</li><li>'''f930ff6ebbac1a72108a2e100762b18f''' is the MD5 hash value generated by the package names of all software packages installed by rootfs. As long as the list of software packages installed by rootfs is not modified, this value will not change. The compilation script will use this MD5 hash value to generate Determine whether rootfs needs to be recompiled</li></ol></li><li>'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.list''' > lists the package names of all packages installed by rootfstest@test:~/orangepi-build$ '''ls external/cache/rootfs/''''''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.currentjammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.list</li></ol></li><li>If the required rootfs already exists under '''external/cache/rootfs''', then compiling rootfs again will directly skip the compilation process and will not restart the compilation. When compiling the image, it will also go to '''external/cache/rootfs''' to find out whether it has If there is rootfs available in the cache, use it directly, which can save a lot of download and compilation time.</li></ol> == Compile linux image ==

~~~~<ol ~~start="8"~~ style="list-style-type: decimal;"><li>Run the build.sh script, remember to add sudo permissiontest@test:~/orangepi-build$ '''sudo ./build.sh'''</li><li>Select '''Full OS image for flashing''', then press Enter</li></ol>

~~-----~~[[File:media/image553.png|576x128px|选区_242]]

</div>

<li>Then select the model of the development board

~~-----~~[[File:media/image538.png|576x289px|6]]

<~~ol start="10" style="list-style-type: decimal;"~~/div></li><li>Then select the type of rootfs (mainly maintain '''bullseye/focal/jammy''' at present)</lip><~~/ol~~div class="figure">

~~<~~[[File:media/~~span>= Linux SDK——orangepi-build instructions =~~image547.png|575x180px|7]]

<~~span id~~/div></li><li>Then select the type of image<ol style="~~compilation~~list-style-~~system~~type: lower-~~requirements~~alpha;"><li>'''Image with console interface (server)''' Indicates the image of > the server version, which is relatively small</~~span~~p></li><li>'''Image with desktop environment''' Indicates a image with a > desktop, which is relatively large<div class=~~= Compilation system requirements ==~~"figure">

~~'''We can cross-compile the Linux image of the development board on the x64 computer, or compile the Linux image of the development board on the Ubuntu22~~[[File:media/image548.~~04 system of the development board, please choose one according to your preference.'''~~png|576x75px|选区_245]]

~~'''~~</div></li></ol></li><li>If you ~~use orangepi-build~~ are compiling the image of the server version, you can also choose to compile the ~~Linux image in~~ Standard version or the ~~Ubuntu22~~Minimal version.~~04 system~~ The pre-installed software of the ~~development board,~~ Minimal version will be much less than that of the Standard version '''(please do ~~a good job of cooling (especially when~~ not choose the ~~SSD starts). If the heat dissipation~~ Minimal version if there is no special requirement, because many things are not ~~done well, it is prone to the error of file system runaway~~pre-installed by default.Some functions may not be available)'''<div class="figure">

~~<~~[[File:media/~~span>=== Compile with the Ubuntu22~~image549.~~04 system of the development board ===~~png|569x77px|选区_397]]

<~~ol style="list-style-type: decimal;"~~/div></li><li>~~The Linux SDK, namely '''orangepi-build''', supports running on~~ If you are compiling the ~~'''Ubuntu 22.04'''~~ image of the ~~development board (other systems have not been tested)~~desktop version, ~~so before downloading orangepi-build, please first ensure that the Ubuntu version installed on the development board is Ubuntu 22.04. The command~~ you need to ~~check~~ select the ~~Ubuntu version installed on the development board is as follows. If the Release field does not display '''22~~type of desktop environment.~~04'''~~Currently, ~~it means that the current~~ Ubuntu ~~version does not meet the requirements. Please replace the system before performing the following operations.orangepi@orangepi:~$ '''lsb_release -a'''No LSB modules are available.Distributor ID:~~ Jammy mainly maintains XFCE and Gnome desktops, UbuntuFocal only maintains XFCE desktops, and Debian Bullseye mainly maintains XFCE and KDE desktops<~~p>Description: Ubuntu 22.04.1 LTSRelease: '''22.04'''Codename: jammy</li>~~<li>'''Since the source codes such as the kernel and U-boot are stored on GitHub, it is very important to ensure that the development board can download codes from GitHub normally when compiling the image.'''</li></oldiv class="figure">

~~<~~[[File:media/~~span>=== Compile with x64 Ubuntu22~~image550.~~04 computer ===~~png|575x99px|Selection_001]]

<~~ol style="list-style-type: decimal;"~~/div><lip>[[File:media/image551.png|576x74px]]~~The Linux SDK, '''orangepi-build''', supports running on computers with '''Ubuntu 22~~You can then select additional packages that need to be installed.~~04''' installed, so before downloading orangepi-build, please make sure that~~ Please press the ~~Ubuntu version installed on your computer is Ubuntu 22~~Enter key to skip directly here.04[[File:media/image552. ~~The command~~ png|575x264px]]</li><li>Then it will start to ~~check~~ compile the ~~Ubuntu version installed on the computer~~ linux image. The general process of compilation is as followsa. If Initialize the ~~Release field does not display '''22.04''', it means that the current~~ compilation environment of Ubuntu ~~version does not meet~~ PC and install the ~~requirements. Please replace the system before performing~~ software packages required for the ~~following operations.~~compilation process~~test@test:~$ '''lsb_release~~ b. Download the source code of u-~~a'''~~boot and linux kernel (if cached, only update the code)~~No LSB modules are available~~c.Compile u-boot source code and generate u-boot deb package~~Distributor ID: Ubuntu~~d. Compile the linux source code and generate linux-related deb packages~~Description: Ubuntu 22~~e.~~04 LTS~~Make the deb package of linux firmware~~Release: '''22~~f.~~04'''~~Make the deb package of the orangepi-config tool~~Codename: jammy~~g. Create a deb package supported by the board</p~~></li~~>~~<li>~~h. If you are compiling the ~~computer is installed with Windows system and there is no computer with Ubuntu 22.04 installed~~desktop image, you ~~can consider using '''VirtualBox''' or '''VMware''' to install an Ubuntu 22~~will also create desktop-related deb packagesi.~~04 virtual machine in~~ Check whether the ~~Windows system. But please be careful~~ rootfs has been cached, if not ~~to compile orangepi-build on~~ , recreate the ~~WSL virtual machine~~rootfs, ~~because orangepi-build~~ if it has ~~not~~ been ~~tested in the WSL virtual machine~~cached, ~~so it cannot be guaranteed that orangepi-build can be used normally in WSL.~~directly decompress and usej. Install the previously generated deb package into rootfs</lip>~~<li>~~~~The download address~~ k. Make some specific settings for different development boards and different types of ~~the installation image of Ubuntu 22~~images, such as pre-installing additional software packages, modifying system configuration, etc.~~04 '''amd64''' version is：~~~~'''https://mirrors~~l.~~tuna.tsinghua.edu.cn~~Then make an image file and format the partition, the default type is ext4</~~ubuntu-releases/22~~p>m.~~04/ubuntu-22.04-desktop-amd64.iso'''~~Then copy the configured rootfs to the mirrored partitionorn. Then update initramfs~~'''https://repo~~o.~~huaweicloud.com/ubuntu~~Finally, write the bin file of u-~~releases/22.04/ubuntu-22.04.1-desktop-amd64.iso'''~~boot into the image through the dd command</li><li>After ~~installing Ubuntu 22.04 on~~ compiling the ~~computer or virtual machine~~image, ~~please set~~ the ~~software source of Ubuntu 22.04 to Tsinghua source, otherwise it is easy to make mistakes due to network reasons when installing the software later~~following information will be prompted

<li>~~For the method~~ The storage path of ~~replacing Tsinghua source, please refer to~~ the ~~> instructions on this web page~~compiled image[ o.k. ] Done building [ '''output/images/orangepi5plus_1.0.0_debian_bullseye_linux5.10.110_xfce_desktop/orangepi5plus_1.0.0_debian_bullseye_linux5.10.110_xfce_desktop.img''' ]</li><li>Compilation time</li></ol>

</li></ol>

'''~~https~~[ o.k. ] Runtime [ 19 min ]''' <ol style="list-style-type:lower-alpha;"><li>Repeat the command to compile the image, and use the following > command to start compiling the image directly without selecting > through the graphical interface</~~/mirrors~~p>[ o.~~tuna~~k.~~tsinghua~~] Repeat Build Options [ '''sudo .~~edu~~/build.cnsh BOARD=orangepi5plus BRANCH=legacy BUILD_OPT=image RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=yes''' ]</~~help~~p></~~ubuntu~~li></~~'''~~ol> = Linux Development Manual = == The method of compiling the kernel source code separately in the linux system of the development board ==

<ol ~~start="2"~~ style="list-style-type: ~~lower-alpha~~decimal;"><li>~~Note that~~ First download the ~~Ubuntu version needs to be switched to 22.04[[File:./images/media/image625.png|576x241px]]</li><li>The content~~ Linux kernel source code of the ~~'''/etc/apt/sources.lis'''t file that > needs to be replaced is~~development board~~test@test:~$ '''sudo mv /etc/apt/sources.list /etc/apt/sources.list.bak~~'''~~test~~orangepi@~~test~~orangepi:~$ ~~'''sudo vim /etc/apt/sources.list'''# By default, the source image is commented to improve the speed of apt update, you can uncomment it yourself if necessarydeb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiverse# deb~~git clone -~~src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy main restricted universe multiversedeb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy~~-~~updates main restricted universe multiverse# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-updates main restricted universe multiversedeb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy~~depth=1 -~~backports main restricted universe multiverse# deb~~b orange-~~src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy~~pi-~~backports main restricted universe multiversedeb https://mirrors.tuna.tsinghua.edu~~5.~~cn/ubuntu/ jammy~~10-~~security main restricted universe multiverse# deb-src~~ rk3588 https://~~mirrors.tuna.tsinghua~~github.~~edu.cn/ubuntu~~com/ ~~jammy~~orangepi-~~security main restricted universe multiverse<~~xunlong/p>~~# Pre~~linux-~~release software source, not recommended to enable# deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ jammy-proposed main restricted universe multiverse~~orangepi'''</~~li>~~<li>~~After the replacement, you need to update the package information > and make sure there is no error~~</pol>~~test@test:~$ '''sudo apt update'''</li><li>~~'''~~In addition~~If you have problems downloading the code from github, ~~since~~ you can go to the official tool of the ~~source codes such as~~ development board to download the compressed kernel ~~and U-boot > are stored on GitHub~~source code package, then upload it ~~is very important~~ to ~~ensure that~~ the ~~> computer can download codes from GitHub normally when compiling >~~ linux system of the ~~image~~development board, and then decompress it.'''~~</li></ol>~~

~~<~~[[File:media/~~span>== Get the source code of linux sdk ==~~image554.png|223x86px]] [[File:media/image555.png|305x87px]]

~~=== Download orangepi-build from github ===~~'''The command to decompress the compressed kernel source code package is:'''

~~# The linux sdk actually refers to the code of~~ orangepi@orangepi:~$ '''tar zxf orange-pi-~~build~~5. ~~orangepi~~10-~~build is modified based on the armbian build system~~rk3588. ~~Using orangepi-build, multiple versions of linux images can be compiled~~tar. ~~First download the code of orangepi-build, the command is as follows：~~gz'''

~~test~~orangepi@~~test~~orangepi:~$ '''~~sudo apt~~mv orange-~~get update~~pi-5.10-rk3588 linux-orangepi'''

~~test@test:~$~~ '''~~sudo apt-get install -y git~~After decompression, please execute the following command to synchronize the source code with github to ensure that the source code is in the latest state:'''

~~test~~orangepi@~~test~~orangepi:~$ '''~~git clone''' '''https://github.com/orangepi~~cd linux-~~xunlong/~~orangepi~~-build.git''' '''-b next~~'''

orangepi@orangepi:~/linux-orangepi$ '''~~Note that the Orange Pi 5 Plus development board needs to download the source code of the''' '''next''' '''branch of orangepi-build. The above~~ git ~~clone command needs to specify the branch of the orangepi-build source code as next.~~pull'''

<~~div class~~ol start="~~figure~~2"style="list-style-type: decimal;"><li>Then configure the default kernel configurationorangepi@orangepi:~$ '''cd linux-orangepi'''orangepi@orangepi:~/linux-orangepi$ '''make rockchip_linux_defconfig'''</li></ol>

~~[[File:.~~'''The path of rockchip_linux_defconfig</~~images~~span> in the kernel source code is arch/~~media~~arm64/~~image626.png|576x298px|图片6]]~~configs/'''

<ol start="3" style="list-style-type: decimal;"><li>Then compile the kernel source code</~~div~~p>orangepi@orangepi:~/linux-orangepi$ '''~~Downloading~~ make -j10'''</li><li>Then install the kernel moduleorangepi@orangepi:~/linux-build code through the git clone command does not require entering the user name and password of the github account (the same is true for downloading other codes in this manual), if the Ubuntu PC prompts the user to enter the github account after entering the git clone command The name and password are usually entered incorrectly in the address of the orangepi~~-build warehouse behind the git clone. Please check the spelling of the command carefully, instead of thinking that we forgot to provide the username and password of the github account.~~$ '''sudo make modules_install'''</li></ol>

~~<ol start="2" style="list-style-type: decimal;"><li>~~'''The ~~u-boot and linux~~ installation path of the kernel ~~versions currently used by the development board are as follows<~~module is：/~~li><~~lib/~~ol>~~modules'''

~~{| class="wikitable"~~|-~~| style="text-align: left;"| '''branch~~'''~~| style="text-align: left;"| '''u-boot''' '''version'''| style="text-align: left;"| '''linux~~ After executing the sudo make modules_install command, you can see that there will be an additional kernel ~~version'''~~|-~~| style="text-align: left;"| '''legacy'''| style="text-align: left;"| '''u-boot 2017.09'''| style="text-align~~module folder under /lib/modules/: ~~left;"| '''linux5.10~~'''|}

orangepi@orangepi5plus:~$ '''The branch mentioned here is not the same thing as the branch of the orangepi-build source code, please do not confuse it. This branch is mainly used to distinguish different kernel source code versions.ls /lib/modules'''

'''~~Currently, the linux5~~5.10 ~~bsp kernel provided by RK is defined as the legacy branch. If the mainline kernel is supported in the future, a current branch will be added~~.110+'''5.10.110-rockchip-rk3588

<ol start="35" style="list-style-type: decimal;"><li>~~orangepi-build will contain the following files and folders after downloading<ol style="list-style-type: lower-alpha;"><li>'''build.sh''': Compile the startup script</li><li>'''external''': Contains the configuration files needed to compile >~~ Then install the kernel image~~, specific scripts,~~ and ~~the source code of some > programs, etc.~~uInitrd</p~~></li~~>~~<li>~~~~'''LICENSE''': GPL 2 license file</li><li>'''README.md''':~~ orangepi~~-build documentation</li><li>'''scripts''': General script for compiling linux imagestest~~@~~test~~orangepi:~/linux-orangepi~~-build~~$ '''lssudo make install'''<p/li>~~'''build.sh external LICENSE''' '''README.md''' '''scripts'''~~</pol>~~~~'''~~If you downloaded the code~~ The installation path of ~~orangepi-build from github, after downloading, you may find that orangepi-build does not contain~~ the ~~source code of u-boot and linux~~ kernel~~, nor does u-boot~~ image and linux kernel need to use cross-compilation tools Chain, this is normal, because these things are stored in other separate github warehouses or some servers (the addresses will be detailed below). orangepi-build will specify the address of u-uInitrd is：/boot, linux kernel and cross-compilation toolchain in the script and configuration file. When running orangepi-build, when it finds that there are no such things locally, it will automatically go to the corresponding place to download them./'''~~</li></ol></li></ol>~~

~~<~~sudo make install command, you can see that there will be one more kernel file under /~~span>=== Download the cross-compilation toolchain ===~~boot/：'''

~~'''The cross-compilation toolchain will only be downloaded when the~~ orangepi@orangepi5plus:~/orange-~~build compilation image is used on an x64 computer. Compiling the linux image of the development board in the Ubuntu22.04 of the development board will not download the cross~~pi-~~compilation toolchain~~5. ~~At this time, orangepi~~10-~~build~~rk3588$ '''ls /~~toolchains will be an empty folder.~~boot/vmlinuz*'''

~~<ol style="list~~'''/boot/vmlinuz-~~style~~5.10.110+''' /boot/vmlinuz-~~type: decimal;"><li>When orangepi-build runs for the first time, it will automatically download the cross-compilation toolchain and put it in the toolchains folder~~5. ~~Every time after running the build~~10.~~sh script of orangepi~~110-~~build, it will check whether the cross~~rockchip-~~compilation toolchain in toolchains exists , if it does not exist, the download will be restarted, if it exists, it will be used directly, and the download will not be repeated.~~rk3588 <~~div class="figure"~~br />'''The file /boot/Image is actually loaded when the system starts, and Image is a copy of the vmlinuz file'''

~~[[File~~<ol start="6" style="list-style-type:decimal;"><li>Then install the dtb file into '''/boot/dtb'''orangepi@orangepi:~/linux-orangepi$ '''sudo make dtbs_install INSTALL_DTBS_PATH=/boot/dtb/'''</li><li>Then restart the Linux system and the newly compiled kernel will be loadedorangepi@orangepi:~$ '''uname -r''''''5.10.110+'''</~~images~~p></~~media~~li></~~image627.png|575x278px|选区_396]]~~ol>

<~~/div></li><li>The image URL of the cross-compilation toolchain in China is the open source software image site of Tsinghua University'''https://mirrors.tuna.tsinghua.edu.cn/armbian-releases/_toolchain/'''</li><li>After '''toolchains''' is downloaded, it will contain multiple versions of cross-compilation toolchains, and the development board will only use two of themtest@test:~/orangepi-build$ '''ls toolchains/'''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnugcc-arm-11.2-2022.02-x86_64-arm-none-linux-gnueabihfgcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnugcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihfgcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabigcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabihfgcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnugcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabigcc-linaro-aarch64-none-elf-4.8-2013.11_linuxgcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linuxgcc-linaro-arm-none-eabi-4.8-2014.04_linux</li><li>The cross-compilation toolchain used to compile the linux kernel source code is<ol style~~span id="~~list-style~~openwrt-~~type: lower~~system-~~alpha;~~instructions">~~<li>linux5.10~~</pspan>~~'''gcc-arm-11.2-2022.02-x86_64-aarch64-none-linux-gnu'''</li></ol></li><li>The cross-compilation tool chain used to compile the u-boot source code is<ol style~~=~~"list-style-type: lower-alpha;"><li>v2017.09'''gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu'''</li></ol></li></ol>~~OpenWRT system instructions =

==~~= orangepi-build complete directory structure description =~~OpenWRT version ==

~~<ol style~~{| class="~~list-style-type: decimal;~~wikitable">~~<li>The orangepi-build repository does not contain the source code of the linux kernel, u-boot, and cross~~|-~~compilation toolchain after downloading. The source code of the linux kernel and u-boot is stored in an independent git repository<ol~~ | style="~~list~~text-~~style-type~~align: ~~lower-alpha~~left;">~~<li>The git warehouse where the linux kernel source code is stored > is as follows：~~| '''~~https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-5.10-rk3588~~OpenWRT version'''~~</li><li>The git warehouse where the u~~| style="text-~~boot source code is stored is as &gt~~align: left; ~~follows：~~"| '''~~https://github.com/orangepi-xunlong/u-boot-orangepi/tree/v2017.09-rk3588~~kernel version'''~~</li></ol></li><li>When orangepi~~|-build runs for the first time, it will download the cross-compilation toolchain, 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~~text-~~type~~align: ~~lower-alpha~~left;">~~<li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li>a.~~| '''~~build~~v22.~~sh''': compile startup scriptb~~03.4'''external''': Contains the configuration files needed to compile the image, scripts with specific functions, and the source code of some programs. The rootfs compressed package cached during the image compilation process is also stored in external~~c.'''kerne'''l~~| style="text-align: ~~stores the source code of the linux kernel. The folder named~~ left;"| '''~~orange-pi-5~~Linux5.10-rk3588''' stores the kernel source code of the legacy branch of the RK3588/RK3588S series development boards. Please do not manually modify the name of the folder of the kernel source code. If it is modified, the kernel source code will be re-downloaded when the compilation system is running~~d.'''LICENSE''': GPL 2 license filee.'''README~~.~~md''': orangepi-build documentationf.'''output''': Store compiled deb packages such as u-boot and linux, compilation logs, and compiled images and other filesg.'''scripts''': general scripts for compiling linux imagesh'''.toolchains''': store cross-compilation toolchain~~i.'''u-boot''': Store the source code of u-boot. The folder named '''v2017.09-rk3588''' stores the u-boot source code of the legacy branch of the RK3588/RK3588S series development boards. Please do not name the folder name of the u-boot source code Manual modification, if modified, the u-boot source code will be re-downloaded when the compilation system is running~~j.'''userpatches''': Store configuration files needed to compile scriptstest@test:~/orangepi-build$ '''ls''''''build.sh external kernel LICENSE output''' '''README.md''' '''scripts toolchains u-boot userpatches~~110'''~~</li></ol></li></ol>~~|}

== ~~Compile u-boot~~ OpenWRT Adaptation ==

~~<ol style~~{| class="~~list~~wikitable"|-| style="text-~~type~~align: ~~decimal~~left;">~~<li>Run the build.sh script, remember to add sudo permissiontest@test:~/orangepi-build$~~ | '''~~sudo ./build.sh~~Function'''~~</li><li>Select~~ | style="text-align: left;"| '''~~U-boot package~~OpenWRT'''~~, then press Enter<div class="figure">~~|- ~~[[File:./images/media/image628.png~~|~~576x132px|选区_238]]~~ ~~</div></li><li>Then select the model of the development board<div class~~style="~~figure~~text-align: left;">| '''USB2.0x2'''~~[[File:./images/media/image629.png~~|~~576x289px|6]]~~ ~~</div></li><li>Then it will start to compile u-boot, and some information prompted during compilation is explained as follows<ol~~ style="~~list-style~~text-~~type~~align: ~~lower-alpha~~left;">~~<li>u-boot source code version[ o.k. ] Compiling u-boot [~~ | '''~~v2017.09~~OK''' ~~]</li><li>The version of the cross~~|-~~compilation toolchain[ o.k. ] Compiler version [~~ | style="text-align: left;"| '''~~aarch64-linux-gnu-gcc 7~~USB3.~~4.1~~0x2''' ~~]</li><li>Path to the generated u~~| style="text-~~boot deb package[ o.k. ] Target directory [~~ align: left;"| '''~~orangepi-build/output/debs/u-boot~~OK''' ~~]</li><li>The package name of the generated u~~|-~~boot deb package[ o.k. ] File name [~~ | style="text-align: left;"| '''~~linux~~USB Type-~~u-boot-legacy-orangepi5plus_1~~C 3.0~~.0_arm64.deb~~''' ~~]</li><li>Compilation time[ o.k. ] Runtime [~~ | style="text-align: left;"| '''1OK''' |-| style="text-align: left;"| '''~~min~~3pin debugging serial port''' ~~]</li><li>Repeat the command to compile u~~| style="text-~~boot, use the following command &gt~~align: left; ~~to start compiling u-boot directly without selecting through > the graphical interface[ o.k. ] Repeat Build Options [~~ "| '''~~sudo ./build.sh BOARD=orangepi5plus~~OK''' |-| style="text-align: left;"| '''~~BRANCH=legacy BUILD_OPT=u-boot KERNEL_CONFIGURE=no~~TF card start''' ~~]</li></ol></li><li>View the u~~| style="text-~~boot deb package generated by compilationtest@test~~align:~~~/orangepi-build$~~ left;"| '''~~ls output/debs/u-boot/~~OK'''~~linux-u-boot-legacy-orangepi5plus_1.0.0_arm64.deb</li><li>The files contained in the generated u~~|-~~boot deb package are as follows<ol~~ | style="~~list-style~~text-~~type~~align: ~~lower-alpha~~left;">~~<li>Use the following command to decompress the deb packagetest@test:~/orangepi-build$~~ | '''cdSPIFlash+NVMe SSD Boot''' | style="text-align: left;"| '''~~output/debs/u-boot~~OK'''~~test@test~~|-| style="text-align:~~~/orangepi_build/output/debs/u-boot$ $~~ left;"| '''~~sudo~~SPIFlash boots the complete system''' | style="text-align: left;"| '''~~dpkg -x~~OK''' ~~\'''linux~~|-u| style="text-~~boot-legacy-orangepi5plus_1.0.0_arm64.deb .~~align: left;"| ''' ~~'''(Note that there is a "~~2.~~" at the end of the command)~~5G PCIe network port X2'''~~test@test~~| style="text-align:~~~/orangepi_build/output/debs/u-boot$~~ left;"| '''lsOK'''~~linux~~|-u| style="text-~~boot-legacy-orangepi5plus_1.0.0_arm64.deb~~ align: left;"| '''~~usr~~Network port status light'''~~</li><li>The decompressed file is as followstest@test~~| style="text-align:~~~/orangepi-build/output/debs/u-boot$~~ left;"| '''~~tree usr~~OK'''~~usr└── lib├── linux-u-boot-legacy~~|-~~orangepi5plus_1.0.0_arm64│ ├── idbloader.img│ ├── rkspi_loader.img│ └── u~~| style="text-~~boot.itb└── u-boot├── LICENSE├── orangepi_5_plus_defconfig└── platform_install.sh3 directories, 6 files</li></ol></li>~~<li>When the orangepi-bulid compilation system compiles the u-boot source code, it will first synchronize the u-boot source code with the u-boot source code of the github server, so if you want to modify the u-boot source code, you first need to turn off the download and update function of the source code align: left;"| '''(need This function can only be turned off after u-boot has been fully compiled, otherwise it will prompt that the source code of u-boot cannot be found. If the source code compressed package is downloaded fromled light''' | style="text-align: left;"| '''~~Google Drive, there is no such problem because the source code of u-boot cached)~~OK'''~~, otherwise the changes made will be restored, the method is as follows：Set the IGNORE_UPDATES variable in userpatches/config~~text-~~default.conf to &quot~~align: left;~~yes"test@test:~/orangepi-build$~~ "| '''~~vim userpatches/config-default.conf~~FAN fan interface'''~~IGNORE_UPDATES~~| style=~~&quot~~"text-align: left;"| '''~~yes~~OK'''~~"</li><li>When debugging u-boot code, you can use the following method to update u~~|-~~boot in the linux image for testing<ol~~ | style="~~list~~text-~~style-type~~align: ~~lower-alpha~~left;">~~<li>Upload the compiled u-boot deb package to the linux system of > the development boardtest@test:~/orangepi-build$~~ | '''~~cd''' '''output/debs/u~~AX200-~~boot~~WIFI'''~~test@test~~| style="text-align:~~~/orangepi_build/output/debs/u-boot$~~ left;"| '''~~scp~~OK''' |-| style="text-align: left;"| '''\AX200-WIFI'''~~'''linux~~| style="text-~~u-boot-legacy-orangepi5plus_1.0.0_arm64.deb~~align: left;"| ''' OK'''~~root@192.168.1.xxx:/root'''</li><li>Then log in to the development board and uninstall the deb > package of u~~|-~~boot installedroot@orangepi~~| style="text-align:~# left;"| '''~~apt~~eMMC extension interface''' | style="text-align: left;"| '''~~purge'''~~ OK'''|} </lispan>~~<li>Install the new u-boot deb package just uploaded~~== The first start to expand rootfs == <~~p>root@orangepi:~# '''dpkg~~ ol style="list-~~i''' '''linux~~style-~~u-boot-legacy-orangepi5plus_1.0.0_arm64.deb'''</li~~type: decimal;"><li>~~Then run~~ When the OpenWRT system is started for the first time, the ~~nand-sata-install scriptroot@orangepi:~#~~ '''~~nand~~resize-~~sata-install~~rootfs.sh'''script will be executed to expand the rootfs, and it will automatically restart after the expansion is completed</li><li>~~Then select~~ After logging in to the system, you can use the '''~~5 Install/Update the bootloader on SD/eMM~~df -h''' command to ~~update~~ view the size of rootfs. If it is consistent with the ~~u-boot in~~ actual capacity of the storage device (TF card , eMMC or ~~'''7 Install/Update~~ NVME SSD), it means that the ~~bootloader on SPI Flash''' to update the u-boot in the SPI Flash~~automatic expansion is running correctly~~[[File~~root@OpenWrt:~~./images/media/image630.png|317x154px]]~~~# df -h</p~~></li~~>~~<li>~~~~After pressing the Enter key, a Warning will pop up first~~Filesystem Size Used Available Use% Mounted on~~[[File:.~~'''/~~images~~dev/~~media/image631~~root 14.8G 14.7G 91.~~png|314x170px]]<~~6M 99% /~~p></li><li>Press the Enter key again to start updating u-boot, and the > following information will be displayed after the update is > completed~~'''~~[[File:~~tmpfs 495.5M 6.~~/images/media/image632~~1M 489.~~png|223x125px]]<~~4M 1% /~~p></li><li>Then you can restart the development board to test whether the > modification of u-boot takes effect~~tmp</p~~></li></ol~~>~~</li><li>~~~~Other useful information<~~tmpfs 512.0K 0 512.0K 0% /p>~~<ol style="list-style-type: lower-alpha;"><li>u-boot 2017.09 source code, the defconfig configuration file > used by the development board is~~dev~~'''orangepi-build~~/~~u-boot~~dev/~~v2017~~root 14.~~09-rk3588~~8G 14.7G 91.6M 99% /~~configs~~opt/~~orangepi_5_plus_defconfig'''~~docker</li>~~<li>u-boot 2017.09 source code, the dts file used by the development > board is~~</pol> <~~p>'''orangepi~~span id="how-~~build/u~~to-~~boot/v2017.09~~log-~~rk3588/arch/arm/dts/rk3588~~in-~~orangepi~~to-5the-~~plus.dts'''</p~~system"></~~li></ol~~span>~~</li></ol>~~== How to log in to the system ==

== ~~Compile the linux kernel~~ = Login via serial port ===

<li>~~Run~~ First, to use the ~~build.sh script~~debugging serial port, ~~remember~~ please refer to the chapter on how to ~~add sudo permissiontest@test:~/orangepi-build$ '''sudo ./build.sh'''~~use the debugging serial port</li><li>~~Select~~ The OpenWrt system will automatically log in as the '''~~Kernel package~~root'''user by default, ~~then press Enter~~and the display interface is as follows

[[File:~~./images/~~media/~~image633~~image556.png|~~575x116px~~576x290px|~~选区_240~~9D229F96-887B-4c6b-8E6E-681C9994DFA0]] </div></li></ol>

<~~/div~~span id="log-in-to-the-system-via-ssh"></lispan>~~<li>Then select~~ === Log in to the ~~model of the development board<div class~~system via SSH ===~~"figure">~~

~~[[File:~~'''Please note that in the OpenWrt system of Orange Pi 5 Plus, the network port near the typeC power interface is configured as a WAN port by default, and the network port near the HDMI port is configured as a LAN port by default.~~/images/media/image629.png|576x289px|6]]~~'''

<~~/div></li~~ol style="list-style-type: decimal;"><li>~~Then it will prompt whether~~ First connect the LAN port of the board to ~~display~~ the ~~kernel configuration interface. If you do not need to modify~~ network port of the ~~kernel configuration~~computer with a network cable, ~~select~~ so that the ~~first one. If you need to modify~~ network port of the ~~kernel configuration, select the second one.[[File:./images/media/image634.png|576x87px]]~~computer can obtain an IP address through DHCP</li><li>~~If you choose~~ The LAN port IP of the default board is set to ~~display~~ '''192.168.2.1''', so the ~~kernel configuration menu (~~computer can obtain the ~~second option) in step 4), the kernel configuration interface opened by~~ IP address starting with '''~~make menuconfig~~192.168.2''' ~~will pop up. At~~ at this time</li><li>If the computer is installed with an Ubuntu system, you can ~~directly modify~~ execute the following command to log in to the ~~kernel configuration~~system through SSH. By default, ~~save and exit after modification~~you can log in directly without a passwordtest@ubuntu:~$ '''ssh root@192. ~~Yes, after exiting~~168.2.1'''</li><li>After successfully logging in to the system, the ~~kernel source code will be compiled~~display is as shown in the figure below[[File:~~./images/~~media/~~image635~~image557.png|~~575x400px~~553x330px]]</li><li>If the computer is installed with Windows system, you can log in by referring to the method introduced in the section of SSH remote login to the development board under Windows.</li></ol>

<!span id="log-in- to-the->~~<ol style="list-style~~luci-~~type: lower~~management-~~alpha;"><li>If you do not need to modify the configuration options of the > kernel, when running the build.sh script, pass in > '''~~KERNEL_CONFIGURE=no~~</span~~>''' to temporarily block the pop-up > kernel configuration interface</p~~>~~test@test:~/orangepi-build$ '''sudo ./build.sh''' '''KERNEL_CONFIGURE~~=~~no'''</li><li>You can also set '''KERNEL_CONFIGURE~~=~~no'''~~ Log in to the ~~> '''orangepi-build/userpatches/config-default.conf''' > configuration file, which can permanently disable this function</li><li>If the following error is displayed when compiling the kernel, it is > because the terminal interface of the Ubuntu PC is too small to > display the '''make menuconfig''' interface. Please > maximize the terminal of the Ubuntu PC and run the build.sh script > again[[File:./images/media/image636.png|574x234px]]</li></ol>

~~<ol start="6" style="list-style-type: decimal;"><li>Part of the information prompted when compiling the kernel source code is as follows<ol style="list-style-type: lower-alpha;"><li>The version of the linux kernel source code[ o.k. ] Compiling current kernel [~~ '''~~5.10.110''' ]</li><li>The version of~~ Please note that the OpenWRT system configures the network port near the ~~cross~~Type-~~compilation toolchain used[ o.k. ] Compiler version [ '''aarch64-none-linux-gnu-gcc 11.2.1''' ]</li><li>The configuration file used by the kernel~~ C power port as a WAN port by default , and the ~~> path where it is stored[ o.k. ] Using kernel config file [ '''config/kernel/linux-rockchip-rk3588-legacy.config''' ]</li><li>The path of the deb package related to~~ network port near the ~~kernel generated~~ HDMI port as a LAN port by ~~> compiling[ o~~default.~~k. ] Target directory [ '''orangepi-build/output/debs/~~''' ~~]</li><li>The package name of the compiled kernel image deb package~~[ ~~o.k. ]~~ [File ~~name [ '''linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb''' ]<~~:media/~~p></li><li>The time used for compilation[ o.k~~image558. png|357x139px] ~~Runtime [ '''5''' '''min''' ]</li>~~<li>Finally, the compilation command to repeatedly compile the > kernel selected last time will be displayed. Use the following > command to start compiling the kernel source code directly > without selecting through the graphical interface~~[ o.k. ] Repeat Build Options [ '''sudo ./build.sh BOARD=orangepi5plus''' '''BRANCH=legacy BUILD_OPT=kernel KERNEL_CONFIGURE=no'''~~ ]~~</li></ol></li><li>View the deb package related to the kernel generated by compilation<ol style="list-style-type: lower-alpha;"><li>'''linux-dtb-legacy-rockchip-rk3588_1.0.0_arm64.deb''' Contains > dtb files used by the kernel</li><li>'''linux-headers-legacy-rockchip-rk3588_1.0.0_arm64.deb''' Include > kernel headers</li><li>'''linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb''' Contains > kernel images and kernel modulestest@test:~/orangepi-build$ '''ls output/debs/linux-*'''output/debs/linux-dtb-legacy-rockchip-rk3588_1.0.0_arm64.deb output/debs/linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deboutput/debs/linux-headers-legacy-rockchip-rk3588_1.0.0_arm64.deb</li></ol></li><li>The files contained in the generated linux-image deb package are as follows<ol style="list-style-type: lower-alpha;"><li>Use the following command to decompress the deb packagetest@test:~/orangepi-build$ '''cd''' '''output/debs'''</li></ol></li></ol>~~

~~test@test:~/orangepi_build/output/debs$~~ # First connect the LAN port of the board to the network port of the computer with a network cable, so that the network port of the computer can obtain an IP address through DHCP# The LAN port IP of the default board is set to '''~~mkdir test~~192.168.2.1''', so the computer can obtain the IP address starting with '''192.168.2''' at this time# Enter the IP address '''192.168.2.1''' in the browser on the computer to log in to the LuCI interface

~~test@test:~/orangepi_build/output/debs$ '''cp''' '''\'''~~<div class="figure">

~~'''linux~~[[File:media/image559.png|552x135px|2023-~~image~~04-~~legacy~~21 14-~~rockchip~~41-~~rk3588_1.0.0_arm64.deb test/'''~~42 的屏幕截图]]

~~test@test~~</div><ol start="4" style="list-style-type:~~~/orangepi_build/output/debs$~~ decimal;"><li>'''The OpenWrt system does not set a password by default''', so just click the '''~~cd test~~login'''button. After successful login, the interface is displayed as shown in the figure below[[File:media/image560.png|552x295px]]</li></ol>

~~test@test:~/orangepi_build/output~~</~~debs/test$ '''dpkg -x''' '''\'''~~span>=== Log in to the terminal through the LuCI management interface ===

'''~~linux~~Please note that the OpenWRT system configures the network port near the Type-~~image-legacy-rockchip-rk3588_1.0.0_arm64.deb~~ C power port as a WAN port by default, and the network port near the HDMI port as a LAN port by default.'''

~~test@test~~[[File:~media/~~orangepi_build/output/debs/test$ '''ls'''~~image558.png|357x139px]]

# First connect the LAN port of the board to the network port of the computer with a network cable, so that the network port of the computer can obtain an IP address through DHCP# The LAN port IP of the default board is set to '''~~boot etc lib~~192.168.2.1''' ~~linux-image-legacy-rockchip-rk3588_1~~, so the computer can obtain the IP address starting with '''192.0168.~~0_arm64.deb~~ 2''' at this time# Enter the IP address '''~~usr~~192.168.2.1'''in the browser on the computer to log in to the LuCI interface

<~~ol start~~div class="2figure" ~~style="list-style-type: lower-alpha;"><li>The decompressed file is as followstest@test:~/orangepi-build/output/debs/test$ '''tree -L 2'''.├── boot│ ├── config-5.10.110-rockchip-rk3588│ ├── System.map-5.10.110-rockchip-rk3588│ └── vmlinuz-5.10.110-rockchip-rk3588├── etc│ └── kernel├── lib│ └── modules├── linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb└── usr├── lib└── share</li></ol~~>

~~<ol start="9" style="list-style-type: decimal;">~~<li>The orangepi-bulid compilation system will first synchronize the linux kernel source code with the linux kernel source code of the github server when compiling the linux kernel source code, so if you want to modify the linux kernel source code, you first need to turn off the update function of the source code '''(you need to compile it once This function can only be turned off after the linux kernel source code, otherwise it will prompt that the source code of the linux kernel cannot be found. If the source code compressed package downloaded from''' '''Google Drive, there is no such problem, because the source code of linux has been cached)''', otherwise the The changes made will be reverted as follows:~~Set the IGNORE_UPDATES variable in '''userpatches/config-default.conf''' to "yes"test@test~~[[File:~~~/orangepi-build$ '''vim userpatches/config-default.conf'''IGNORE_UPDATES="'''yes'''"</li><li>If the kernel has been modified, the following method can be used to update the kernel and kernel modules of the development board linux system<ol style="list-style-type: lower-alpha;"><li>Upload the deb package of the compiled linux kernel to the linux > system of the development boardtest@test:~/orangepi-build$ '''cd''' '''output/debs'''test@test:~/orangepi-build/output/debs$ '''scp''' '''\'''<~~media/p>~~'''linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb root@192.168.1~~image559.~~xxx:/root'''</li><li>Then log in to the development board and uninstall the deb > package of the installed linux kernelroot@orangepi:~# '''apt purge~~ png|552x135px|2023-~~y''' '''linux~~04-~~image~~21 14-~~legacy~~41-~~rockchip-rk3588'''</li><li>Install the deb package of the new linux kernel just uploadedroot@orangepi:~# '''dpkg -i linux-image-legacy-rockchip-rk3588_1.0.0_arm64.deb'''</li><li>Then restart the development board, and then check whether the > kernel-related modifications have taken effectroot@orangepi:~# '''reboot'''</li></ol></li></ol>~~42 的屏幕截图]]

<~~!-- --~~/div><ol start="104" style="list-style-type: decimal;"><li>~~Other useful information<ol style="list-style-type: lower-alpha;"><li>The storage location of the kernel configuration file is as > follows, please do not go to the kernel source code to find~~ Select &gtquot; ~~the kernel configuration file used by the development board~~'''~~orangepi-build/external/config/kernel/linux-rockchip-rk3588-legacy.config~~Terminal'''~~</li><li>The location of~~ " in the ~~dts file used by the development board is~~"'''~~orangepi-build/kernel/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts~~Service'''~~</li></ol>~~" column of the navigation bar and click to enter</li></ol>

~~<~~[[File:media/~~span>== Compile rootfs ==~~image561.png|576x227px]]

<ol start="5" style="list-style-type: decimal;"><li>~~Run~~ At this time, the ~~build.sh script, remember to add sudo permission~~terminal interface is as shown in the figure below~~test@test~~[[File:~~~/orangepi-build$ '''sudo .~~media/~~build~~image562.~~sh'''~~png|576x407px]]</li><li>~~Select '''~~Enter the user name root to log in<~~span class="mark"~~/p>~~Rootfs and all deb packages~~[[File:media/~~span>''', then press Enter~~image563.png|575x334px]]</li></ol>

<~~div class~~span id="~~figure~~use-ip-address-port-number-to-log-in-to-the-terminal">=== Use IP address + port number to log in to the terminal ===

~~[[File:~~'''Please note that the OpenWRT system configures the network port near the Type-C power port as a WAN port by default, and the network port near the HDMI port as a LAN port by default.~~/images/media/image637.png|576x119px|选区_241]]~~'''

~~</div><ol start="3" style="list-style-type~~[[File: ~~decimal;"><li>Then select the model of the development board<~~media/p>~~<div class="figure">~~image558.png|357x139px]]

# First connect the LAN port of the board to the network port of the computer with a network cable, so that the network port of the computer can obtain an IP address through DHCP# The LAN port IP of the default board is set to '''192.168.2.1''', so the computer can obtain the IP address starting with '''192.168.2''' at this time# Then enter [~~[File~~http:./~~images~~/~~media~~192.168.2.1:7681/~~image629~~'''192.~~png|576x289px|6]~~168.2.1:7681''']in the browser to log in to the OpenWRT terminal

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

~~<li>Then select the type of rootfs (mainly maintain '''bullseye/focal/jammy''' at present)~~

[[File:~~./images/~~media/~~image638~~image564.png|~~575x180px~~553x296px|72023-04-21 14-54-26 的屏幕截图]]

</div~~></li><li>Then select the type of image</p~~><~~ol style~~span id="~~list~~how-~~style~~to-~~type: lower~~modify-~~alpha;"><li>'''Image with console interface (server)''' Indicates~~ the ~~image~~ -ip-address-of ~~>~~ -the ~~server version, which is relatively small</p~~-lan-port-through-the-command-line"></lispan>~~<li>'''Image with desktop environment''' Indicates a mirror image with > a desktop, which is relatively large<div class~~=~~"figure">~~= How to modify the IP address of the LAN port through the command line ==

~~[[File:~~# In the OpenWrt system, a command line tool uci is provided, which can easily modify, add, delete and read the content in the configuration file.For details, please refer to the official document# First use the following command to obtain the network configuration, the corresponding configuration file is '''/~~images~~etc/~~media~~config/~~image639~~network''', you can see that the value of '''network.~~png|576x75px|选区_245]]~~lan.ipaddr''' is '''192.168.2.1'''

~~</div></li></ol></li>~~<li>If you are compiling the image of the server version, you can also choose to compile the Standard version or the Minimal version. The pre-installed software of the Minimal version will be much less than that of the Standard version root@OpenWrt:~# '''~~(please do not choose the Minimal version if there is no special requirement, because many things are not pre-installed by default. Some functions may not be available)~~uci show network'''~~<div class="figure">~~

~~[[File:~~.~~/images/media/image640~~.~~png|576x78px|选区_397]]~~.

~~</div></li><li>If you are compiling the image of the desktop version, you need to select the type of desktop environment~~network. ~~Currently, Ubuntu Jammy mainly maintains XFCE and Gnome desktops, Ubuntu Focal only maintains XFCE desktops, and Debian Bullseye mainly maintains XFCE and KDE desktops<div class~~lan=~~"figure">~~interface

~~[[File:~~network.~~/images/media/image641~~lan.~~png|575x99px|Selection_001]]~~device='br-lan'

~~</div>[[File:~~network.~~/images/media/image642~~lan.~~png|576x74px]]You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.[[File:./images/media/image643.png|575x264px]]</li><li>Then it will start to compile rootfs, and some of the information prompted during compilation are as follows<ol style="list-style-type: lower-alpha;"><li>The type of rootfs[ o.k. ] local not found [ Creating new rootfs cache for '''jammy''']</li><li>The storage path of the compiled rootfs compressed package[ o.k. ] Target directory [ '''external/cache/rootfs''' ]</li><li>The name of the rootfs compressed package generated by > compilation[ o.k. ] File name [ '''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' ]</li><li>The time used for compilation[ o.k. ] Runtime [ '''13''' '''min''' ]</li></ol></li><li>View the rootfs compressed package generated by compilation<ol style="list-style-type: lower-alpha;"><li>'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4''' is > the rootfs compressed package, the meaning of each field of > the name is<ol style~~proto=~~"list-style-type: lower-alpha;"><li>~~'static'~~'jammy''' indicates the type of linux distribution of rootfs</li><li>'''xfce''' means rootfs is the type of desktop version, if it > is '''cli''', it means the type of server version</li><li>'''arm64''' represents the architecture type of rootfs</li>~~<li>'''f930ff6ebbac1a72108a2e100762b18f''' is the MD5 hash value generated by the package names of all software packages installed by rootfs. As long as the list of software packages installed by rootfs is not modified, this value will not change. The compilation script will use this MD5 hash value to generate Determine whether rootfs needs to be recompiled</li></ol>~~</li><li>'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.list''' > lists the package names of all packages installed by rootfstest@test:~/orangepi-build$ '''ls external/cache/rootfs/''''''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4'''jammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.currentjammy-xfce-arm64.f930ff6ebbac1a72108a2e100762b18f.tar.lz4.list</li></ol></li>~~<li>If the required rootfs already exists under '''external/cache/rootfs''', then compiling rootfs again will directly skip the compilation process and will not restart the compilation. When compiling the image, it will also go to '''external/cache/rootfs''' to find out whether it has If there is rootfs available in the cache, use it directly, which can save a lot of download and compilation time.</li></ol>

~~== Compile linux image =~~'''network.lan.ipaddr='192.168.2.1''''

~~<ol style~~network.lan.netmask=~~"list-style-type: decimal;"><li>Run the build~~'255.~~sh script, remember to add sudo permissiontest@test:~/orangepi-build$ '''sudo~~ 255.~~/build~~255.~~sh'''</li><li>Select '''Full OS image for flashing''~~0'~~, then press Enter</li></ol>~~

~~<div class~~network.lan.ip6assign=~~"figure">~~'60'

~~[[File:~~.~~/images/media/image644.png|576x128px|选区_242]]~~…

~~</div>~~

<li~~><p~~>Then ~~select~~ enter the ~~model of~~ following command to modify the ~~development board~~item '''network.lan.ipaddr'''</pli><~~div class="figure"~~/ol>

~~[[File~~root@OpenWrt:~# '''uci set network.~~/images/media/image629~~lan.~~png|576x289px|6]]~~ipaddr='192.168.100.1''''

<~~/div></li~~ol start="4" style="list-style-type: decimal;"><li~~><p~~>Then ~~select~~ enter the following command to complete the submission, that is, write to the ~~type of rootfs (mainly maintain '''bullseye/focal/jammy''' at present)~~configuration file</pli><~~div class="figure"~~/ol>

~~[[File~~root@OpenWrt:~~./images/media/image638.png|575x180px|7]]~~~# '''uci commit'''

~~</div></li><li>Then select~~ If the ~~type of image<ol style="list-style-type: lower-alpha;"><li>'''Image~~ IP address in red font is consistent with ~~console interface (server)''' Indicates~~ the ~~image of >~~ one to be set, it means that the ~~server version, which is relatively small</li><li>'''Image with desktop environment''' Indicates a image with a > desktop, which~~ modification is ~~relatively large<div class="figure">~~successful

~~[[File~~root@OpenWrt:.~# '''cat /~~images~~etc/~~media~~config/~~image639.png|576x75px|选区_245]]~~network'''

~~</div></li></ol></li>~~<li>If you are compiling the image of the server version, you can also choose to compile the Standard version or the Minimal version. The pre-installed software of the Minimal version will be much less than that of the Standard version '''~~(please do not choose the Minimal version if there is no special requirement, because many things are not pre-installed by default~~. ~~Some functions may not be available)~~..'''~~<div class="figure">~~

~~[[File:./images/media/image640.png|569x77px|选区_397]]~~config interface 'lan'

~~</div></li>~~<li>If you are compiling the image of the desktop version, you need to select the type of desktop environment. Currently, Ubuntu Jammy mainly maintains XFCE and Gnome desktops, Ubuntu Focal only maintains XFCE desktops, and Debian Bullseye mainly maintains XFCE and KDE desktops~~<div class="figure">~~option device 'br-lan'

~~[[File:./images/media/image641.png|575x99px|Selection_001]]~~option proto 'static'

~~</div>[[File:./images/media/image642.png|576x74px]]You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.[[File:./images/media/image643.png|575x264px]]</li><li>Then it will start to compile the linux image. The general process of compilation is as follows<ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li>a. Initialize the compilation environment of Ubuntu PC and install the software packages required for the compilation processb. Download the source code of u-boot and linux kernel (if cached, only update the code)c. Compile u-boot source code and generate u-boot deb packaged. Compile the linux source code and generate linux-related deb packagese. Make the deb package of linux firmwaref. Make the deb package of the orangepi-config toolg. Create a deb package supported by the boardh. If you are compiling the desktop image, you will also create desktop-related deb packagesi. Check whether the rootfs has been cached, if not, recreate the rootfs, if it has been cached, directly decompress and usej. Install the previously generated deb package into rootfsk. Make some specific settings for different development boards and different types of images, such as pre-installing additional software packages, modifying system configuration, etc.l. Then make an image file and format the partition, the default type is ext4m. Then copy the configured rootfs to the mirrored partitionn. Then update initramfso. Finally, write the bin file of u-boot into the image through the dd command</li></ol></li><li>After compiling the image, the following information will be prompted<ol style="list-style-type: lower-alpha;"><li>The storage path of the compiled image[ o.k. ] Done building [ ''~~option netmask '~~output/images/orangepi5plus_1.0~~255.~~0_debian_bullseye_linux5~~255.~~10.110_xfce_desktop/orangepi5plus_1~~255.0~~.0_debian_bullseye_linux5.10.110_xfce_desktop.img''~~' ~~]</li><li>Compilation time</li></ol></li></ol>~~

option ip6assign '~~''[ o.k. ] Runtime [''' '''19 min ]''~~60'

~~<ol style="list-style-type: lower-alpha;"><li>Repeat the command to compile the image, and use the following > command to start compiling the image directly without selecting > through the graphical interface[ o.k. ] Repeat Build Options [~~ '''~~sudo~~ option ipaddr '192.168.~~/build~~100.~~sh BOARD=orangepi5plus''' '''BRANCH=legacy''' '''BUILD_OPT=image RELEASE=bullseye''' ''~~1'~~BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=yes~~''' ~~]</li></ol>~~

~~= Linux Development Manual =~~...

<~~span id~~ol start="~~the~~5" style="list-~~method-of-compiling~~style-type: decimal;"><li>Restart the network through ubus, please refer to the~~-kernel-source-code-separately-in-~~official document for the~~-linux-system-~~usage instructions of~~-the-development-board"~~ubus</li></~~span~~ol>~~== The method of compiling the kernel source code separately in the linux system of the development board ==~~

~~<ol style="list-style-type~~root@OpenWrt: ~~decimal;"><li>First download the Linux kernel source code of the development board~~~# '''~~orangepi@orangepi:~$ git clone --depth=1 -b orange-pi-5.10-rk3588 https://github.com/orangepi-xunlong/linux-orangepi~~ubus call network restart'''~~</li></ol>~~

~~'''If you have problems downloading~~ <ol start="6" style="list-style-type: decimal;"><li>At this point, enter the ~~code from github,~~ command and you can ~~go to~~ see that the ~~official tool~~ IP of the ~~development board to download the compressed kernel source code package, then upload it to the linux system of the development board, and then decompress it~~LAN port is '''192.168.100.1'''root@OpenWrt:~# '''ifconfig br-lan'''br-lan Link encap:Ethernet HWaddr FE:55:13:A3:EF:E7inet addr:'''192.168.100.1'''Bcast:192.168.100.255 Mask:255.255.255.0inet6 addr: fd60:c4cd:1033::1/60 Scope:GlobalUP BROADCAST MULTICAST MTU:1500 Metric:1RX packets:0 errors:0 dropped:0 overruns:0 frame:0TX packets:3 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:0 (0.0 B) TX bytes:370 (370.0 B)</li></ol>

~~[[File:.~~</~~images/media/image645.png|223x86px]] [[File:./images/media/image646.png|305x87px]]~~span>== How to modify the root password ==

~~'''The~~ === Modify via command line ===

~~orangepi@orangepi:~$ '''tar zxf orange-pi-5~~# First enter passwd root on the command line of the system, and the following prompt message will appear.~~10-rk3588.tar.gz'''~~At this time, you can enter the password you want to set, and press the Enter key to confirm

~~orangepi~~root@~~orangepi~~OpenWrt:~$ /# '''~~mv''' '''orange-pi-5.10-rk3588''' '''linux-orangepi~~passwd root'''

'''~~After decompression, please execute the following command to synchronize the source code with github to ensure that the source code is in the latest state~~Enter new UNIX password:~~'''~~ ~~orangepi@orangepi:~$ '''cd''' '''linux-orangepi'''~~ ~~orangepi@orangepi:~/linux-orangepi$ '''git pull~~'''

<li~~><p~~>Then ~~configure~~ you will be prompted to re-enter the password. At this time, enter the ~~default kernel configurationorangepi@orangepi:~$ '''cd linux-orangepi'''orangepi@orangepi:~/linux-orangepi$ '''make rockchip_linux_defconfig'''~~password again to confirm and press Enter</li></ol>

'''~~The path of''' '''rockchip_linux_defconfig''' '''in the kernel source code is''' '''arch/arm64/configs/~~Retype password:'''

<li>~~Then compile the kernel source codeorangepi@orangepi:~/linux-orangepi$ '''make -j10'''</li><li>Then install the kernel moduleorangepi@orangepi:~/linux-orangepi$ '''sudo make modules_install'''~~The display of successful modification is as follows</li></ol>

'''~~The installation path of the kernel module is：/lib/modules~~passwd: password for root changed by root'''

~~'''After executing~~ </~~lib/modules/:'''~~span>=== Modify through the LuCI management interface ===

~~orangepi@orangepi5plus~~<ol style="list-style-type:~$ decimal;"><li>First refer to the login LuCI management interface to enter the OpenWRT management interface</li><li>Then follow the steps below to change the password<ol style="list-style-type: lower-alpha;"><li>Find the "'''System'''" option in the navigation bar and click</li><li>In the column options below the system, select "''ls 'Management > Rights'''" and click[[File:media/image565.png|552x256px]]</li><li>Select the "'''Router Password'''" option on the Tab page[[File:media/image566.png|552x211px]]</~~lib~~li></~~modules~~ol></li><li>Modify and save the router passworda. Enter the password you set in the "'''Password'''" and "'''Confirm Password'''" dialog boxes (if you are not sure whether the password is entered correctly, you can click the "*" icon behind the dialog box to display the input characters)b. Click "'''Save'''" to save the newly modified password[[File:media/image567.png|553x230px]]</li></ol>

'''5Note: In the "Password" and "Confirm Password" dialog boxes, the passwords entered twice must be consistent.~~10.110+~~''' ~~5.10.110-rockchip-rk3588~~

<ol start="54" style="list-style-type: decimal;"><li>~~Then install~~ After the ~~kernel image and uInitrd~~password is changed successfully, a pop-up box will pop up saying "'''The system password has been changed successfully'''". At this time, a password is required to log in to OpenWRT~~orangepi@orangepi~~[[File:~media/~~linux-orangepi$ '''sudo make install'''~~image568.png|563x222px]]</li></ol>

~~'''The installation path of the kernel image and uInitrd is：~~</~~boot/'''~~span>== USB interface test ==

~~'''After executing~~ === Mount the USB storage device under ~~/boot/：'''~~the command line ===

~~orangepi@orangepi5plus:~/orange-pi-5.10-rk3588$ '''ls /boot/vmlinuz*'''~~# First insert the U disk into the USB interface of the Orange Pi development board# Execute the following command, if you can see the output of sdX, it means that the U disk is recognized successfully

root@OpenWrt:~# '''cat /~~boot~~proc/~~vmlinuz-5.10.110+''' /boot/vmlinuz-5.10.110-rockchip-rk3588 '''The file /boot/Image is actually loaded when the system starts, and Image is a copy of the vmlinuz file~~partitions | grep "sd*"'''

~~<ol start="6" style="list-style-type: decimal;"><li>Then install the dtb file into '''/boot/dtb'''orangepi@orangepi:~/linux-orangepi$ '''sudo make dtbs_install INSTALL_DTBS_PATH=/boot/dtb/'''</li><li>Then restart the Linux system and the newly compiled kernel will be loadedorangepi@orangepi:~$ '''uname -r''''''5.10.110+'''</li></ol>~~major minor #blocks name

~~= OpenWRT system instructions =~~8 0 15126528 '''sda'''

<ol start="3" style="list-style-type: decimal;"><li>Use the mount command to mount the U disk to /mnt, and then you can view the files in the U disk</li></ol> root@OpenWrt:~# '''mount /dev/sda /mnt/''' root@OpenWrt:~# '''ls /mnt/''' test.txt <ol start="4" style="list-style-type: decimal;"><li>After mounting, you can view the capacity usage and mount point of the U disk through the df -h command</li></ol> root@OpenWrt:~# '''df -h | grep "sd"''' /dev/sda 14.4G 187.2M 14.2G 1% /mnt == ~~OpenWRT version~~ = Mount the USB storage device on the LuCI management interface === <ol style="list-style-type: decimal;"><li>First connect the U disk (or other storage device) to the development board via USB2.0</li><li>Then follow the login LuCI management interface to enter the LuCI management interface</li><li>Then in the LuCI management interface, click "System -> Mount Point" to enter the configuration interface of the mount point[[File:media/image569.png|553x256px]]</li><li>Then follow the steps below to add a mount point<ol style="list-style-type: lower-alpha;"><li>Find "'''Mount Point'''" at the bottom of the mount point > '''global setting interface'''</li><li>Under the mount point, select the "Add" button and click Enter</li></ol></li></ol> [[File:media/image570.png|553x163px]] <ol start="3" style="list-style-type: lower-alpha;"><li>Then the following pop-up interface will pop up[[File:media/image571.png|553x288px]]</li><li>Then you can start to mount the storage devicea) Check "'''Enabled'''"b) Select the actual connected device /dev/sda in the UUID column of general settings (choose according to your own device)c) Select "'''Custom'''" in the mount point column, and fill in the target directory to be mounted. Here, take the '''/mnt''' directory as an example, and press '''Enter''' to confirmd) Then click the "'''Save'''" button in the lower right corner</li></ol> [[File:media/image572.png|553x214px]] <ol start="5" style="list-style-type: decimal;"><li>Then you will return to the mount point global settings page, click "'''Save and Apply'''" in the lower left corner of the page to make the mount point take effect</li></ol> [[File:media/image573.png|535x325px]] <ol start="6" style="list-style-type: decimal;"><li>After saving, you can see the "'''mounted file system'''", the storage device has been mounted successfully</li></ol> [[File:media/image574.png|553x201px]] == How to use E-Key PCIe wireless network card == # The PCIe wireless network card models currently compatible with the OpenWRT image are as follows：

{| class="wikitable"

|-

|-

~~| style="text-align: left;"~~| '''~~v22.03.4~~1'''~~| style="text-align: left;"~~| '''~~Linux5.10.110~~AX200'''|}

~~== OpenWRT Adaptation ==~~'''（PCIE+ USB接口)'''

{| ~~class="wikitable"~~|-~~| style="text-align: left;"| '''Function'''| style="text-align: left;"| '''OpenWRT'''~~|-~~| style="text-align: left;"| '''USB2.0x2'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''USB3.0x2'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''USB Type-C 3.0'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''3pin debugging serial port'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''TF card start'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''SPIFlash+NVMe SSD Boot'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''SPIFlash boots the complete system'''| style="text-align~~[[File: ~~left;"| '''OK'''~~|-~~| style="text-align: left;"| '''2~~med%20ia/image230.~~5G PCIe network port X2'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Network port status light'''~~png]]~~| style="text-align: left;"~~| '''OKDebian'''|-~~| style="text-align: left;"| '''led light'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''FAN fan interface'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''AX200-WIFI'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''AX200-WIFI'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''eMMC extension interface'''| style="text-align: left;"| '''OK'''~~|}

~~== The first start to expand rootfs ==~~'''Ubuntu'''

~~<ol style="list-style-type: decimal;"><li>When the OpenWRT system is started for the first time, the~~ '''~~resize-rootfs.sh''' script will be executed to expand the rootfs, and it will automatically restart after the expansion is completed</li>~~<li>After logging in to the system, you can use the '''df -h''' command to view the size of rootfs. If it is consistent with the actual capacity of the storage device (TF card, eMMC or NVME SSD), it means that the automatic expansion is running correctly~~root@OpenWrt:~# df -hFilesystem Size Used Available Use% Mounted on'''/dev/root 14.8G 14.7G 91.6M 99% /~~OpenWRT'''~~tmpfs 495.5M 6.1M 489.4M 1% /tmptmpfs 512.0K 0 512.0K 0% /dev/dev/root 14.8G 14.7G 91.6M 99% /opt/docker</li></ol>~~

~~== How to log in to the system ==~~'''OPi OS Arch'''

~~=== Login via serial port ===~~| '''2'''| '''AX210'''

~~<ol style="list-style-type: decimal;"><li>First, to use the debugging serial port, please refer to the chapter on how to use the debugging serial port</li><li>The OpenWrt system will automatically log in as the~~ '''~~root~~（PCIE+ USB接口)''' ~~user by default, and the display interface is as follows<div class="figure">~~

| [[File:~~./images/~~media/~~image647~~i%20mage231.png~~|576x290px|9D229F96-887B-4c6b-8E6E-681C9994DFA0~~]]{wi dth=“1.06875in” h eight=“1.45in”}| '''Debian'''

~~</div></li></ol>~~'''Ubuntu'''

~~=== Log in to the system via SSH ===~~'''OpenWRT'''

'''Please note that in the OpenWrt system of Orange Pi 5 Plus, the network port near the typeC power interface is configured as a WAN port by default, and the network port near the HDMI port is configured as a LAN port by default.OPi OS Arch'''

~~<ol style="list-style~~|-~~type: decimal;"><li>First connect the LAN port of the board to the network port of the computer with a network cable, so that the network port of the computer can obtain an IP address through DHCP</li><li>The LAN port IP of the default board is set to '''192.168.2.1''', so the computer can obtain the IP address starting with~~ | '''~~192.168.2~~3''' ~~at this time</li><li>If the computer is installed with an Ubuntu system, you can execute the following command to log in to the system through SSH. By default, you can log in directly without a passwordtest@ubuntu:~$~~ | '''~~ssh root@192.168.2.1~~R TL8852BE'''~~</li><li>After successfully logging in to the system, the display is as shown in the figure below[[File:./images/media/image648.png|553x330px]]</li><li>If the computer is installed with Windows system, you can log in by referring to the method introduced in the section of SSH remote login to the development board under Windows.</li></ol>~~

~~=== Log in to the LuCI management interface ===~~'''（PCIE+ USB接口)'''

| [[File:med%20ia/image232.png]]| '''~~Please note that the OpenWRT system configures the network port near the Type-C power port as a WAN port by default, and the network port near the HDMI port as a LAN port by default.~~Debian'''

~~[[File:./images/media/image649.png|357x139px]]~~'''Ubuntu'''

~~# First connect the LAN port of the board to the network port of the computer with a network cable, so that the network port of the computer can obtain an IP address through DHCP# The LAN port IP of the default board is set to~~ '''~~192.168.2.1~~Not Supported OpenWRT'''~~, so the computer can obtain the IP address starting with '''192.168.2''' at this time# Enter the IP address '''192.168.2.1''' in the browser on the computer to log in to the LuCI interface~~

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

~~[[File:./images/media/image650.png|552x135px|2023-04-21 14-41-42 的屏幕截图]]~~'''OPi OS Arch'''

~~</div><ol start="4" style="list-style-type: decimal;"><li>~~'''~~The OpenWrt system does not set a password by default~~OPi OS Droid'''~~, so just click the '''login''' button. After successful login, the interface is displayed as shown in the figure below[[File:./images/media/image651.png|552x295px]]</li></ol>~~

~~=== Log in to the terminal through the LuCI management interface ===~~|}

~~'''Please note that the OpenWRT system configures the network port near the Type~~=== How to create WIFI hotspot ===

~~[[File:~~'''Note that AX200 and AX210 currently only support hotspots in the 2.~~/images/media/image649~~4G frequency band.~~png|357x139px]]~~In the 5G frequency band mode, there will be an error that the modified configuration of the wireless network card cannot be applied.'''

# <ol style="list-style-type: decimal;"><li>First ~~connect~~ insert the PCIe wireless network card into the ~~LAN~~ M.2 E-KEY port of the development board , and then connect the Type-C power supply to power up the ~~network port of~~ development board.[[File:media/image575.png|347x149px]]</li><li>After the ~~computer with a network cable~~system startup is complete, ~~so that~~ click '''Network -> Wireless''' to enter the ~~network port of the computer can obtain an IP address through DHCP~~wireless WiFi configuration interface.[[File:media/image576.png|553x155px]]</li># <li>The ~~LAN port IP~~ default wireless configuration of the ~~default board~~ OpenWRT system is ~~set to~~ '''~~192~~Master''' mode.~~168~~Here, for the convenience of the next operation, we will remove the default wireless connection.2[[File:media/image577.1png|517x162px]]</li><li>Then click '''~~, so~~ Save''' in the lower right corner of the page to make the ~~computer can obtain~~ configuration take effect.[[File:media/image578.png|553x179px]]</li><li>Then click the ~~IP address starting with~~ '''~~192~~Add''' button on the right.~~168~~[[File:media/image579.2png|553x138px]]</li><li>In the pop-up tab page ''' ~~at this time# Enter the IP address~~ Device Configuration'''~~192~~, we set the parameters as shown in the figure below.~~168~~[[File:media/image580.~~2.1~~png|552x268px]]</li><li>Then in '''Interface Configuration -> General Settings''' in , set the ~~browser on~~ mode to '''Access Point AP''', set the ~~computer to log in~~ '''ESSID''' (wireless network name) to '''OpenWrt''', and specify the ~~LuCI interface~~ network as '''<~~div~~ span class="~~figure~~mark">lan''' [[File:~~./images/~~media/~~image650~~image581.png|~~552x135px|2023-04-21 14-41-42 的屏幕截图~~553x234px]] </~~div~~p></li><~~ol start~~li>Then in '''Interface Configuration -~~style~~> Wireless Security''', select ''' WPA2-~~type~~PSK''' as the encryption algorithm; set the key (wireless password) to '''password'''[[File: ~~decimal;"~~media/image582.png|534x224px]]</li><li>~~Select "~~After the above settings are completed, click '''~~Terminal~~Save'''~~"~~ in the ~~"~~lower right corner of the page, and then exit the tab page[[File:media/image583.png|553x303px]]</li><li>Then click '''~~Service~~Save and Apply'''~~" column~~ in the lower right corner of the ~~navigation bar~~ page and ~~click~~ wait for the configuration to be applied.[[File:media/image584.png|553x216px]]</li><li>The display interface of successfully creating a hotspot is shown in the figure below[[File:media/image585.png|515x266px]]</li><li>Then use the mobile phone or computer to search for the WiFi corresponding to the SSID to ~~enter~~connect. After the connection is successful, as shown in the figure below[[File:media/image586.png|247x156px]]</li></ol>

~~[[File:.~~</~~images/media/image652.png|576x227px]]~~span>=== How to connect to WIFI hotspot ===

<ol ~~start="5"~~ style="list-style-type: decimal;"><li>Insert the PCIe wireless network card into the M.2 E-KEY port of the development board, and then connect the Type-C power supply to power the development board.[[File:media/image575.png|347x149px]]</li><li>After the system startup is complete, click '''Network -> Wireless''' to enter the configuration wireless WiFi interface.[[File:media/image576.png|553x155px]]</li><li>The default wireless configuration of the OpenWRT system is '''Master''' mode. Here, for the convenience of the next operation, we will remove the default wireless connection.[[File:media/image577.png|520x162px]]</li><li>Then click '''Save''' in the lower right corner of the page to make the configuration take effect.[[File:media/image578.png|520x179px]]</li><li>Then click the '''Scan''' button to scan the surrounding WiFi hotspots.[[File:media/image587.png|541x225px]]</li><li>Then the following window will pop up to display the available WiFi hotspots. At this time, click the '''Join Network''' button on the ~~terminal~~ right side of the WiFi hotspot you want to connect to connect to the WiFi hotspot.[[File:media/image588.png|553x89px]]</li><li>Then an interface is for connecting to a WiFi hotspot will pop up. We enter the password of the hotspot as shown in the figure below, and then click the '''Submit''' button.[[File:media/image589.png|552x135px]]</~~images~~p></li><li>Then the following interface will pop up, click the '''Save''' button in the lower right corner.[[File:media/~~image653~~image590.png|~~576x407px~~553x237px]]</li><li>~~Enter~~ Finally, you will return to the main interface of wireless configuration, click '''Save and Apply''' and wait for the ~~user name root~~ configuration to ~~log in~~be applied.[[File:media/image591.png|544x252px]]</~~images~~p></li><li>After successfully connecting to the WiFi hotspot, the interface is displayed as shown in the figure below.[[File:media/~~image654~~image592.png|~~575x334px~~547x232px]]</li></ol>

==~~= Use IP address + port number to log in to~~ Installing packages via the ~~terminal =~~command line ==

~~'''Please note that~~ === Install via opkg in the ~~HDMI port as a LAN port by default.'''~~terminal ===

~~[[File:./images/media/image649.png|357x139px]]~~# Update the list of available packages

root@OpenWrt:/# ~~First connect the LAN port of the board to the network port of the computer with a network cable, so that the network port of the computer can obtain an IP address through DHCP# The LAN port IP of the default board is set to '''192.168.2.1''', so the computer can obtain the IP address starting with '''192.168.2''' at this time# Then enter~~ '''~~192.168.2.1:7681~~opkg update''' ~~in the browser to log in to the OpenWRT terminal~~

<~~div class~~ol start="~~figure~~2"style="list-style-type: decimal;"><li>Get the software list</li></ol>

~~[[File~~root@OpenWrt:./~~images/media/image655.png|553x296px|2023-04-21 14-54-26 的屏幕截图]]~~# '''opkg list'''

<~~/div><li>Install the~~-ip-address-of-the-lan-port-through-the-command-line"~~specified package</li></~~span~~ol>~~== How to modify the IP address of the LAN port through the command line ==

~~# In the~~ root@OpenWrt ~~system, a command line tool uci is provided, which can easily modify, add, delete and read the content in the configuration file. For details, please refer to the official document~~:/# ~~First use the following command to obtain the network configuration, the corresponding configuration file is '''/etc/config/network''', you can see that the value of '''network.lan.ipaddr''' is~~ '''~~192.168.2.1~~opkg install <package name>'''

~~root@OpenWrt~~<ol start="4" style="list-style-type:~~~# '''uci show network'''~~decimal;"><li>Check the installed software</li></ol>

~~...~~root@OpenWrt:/# '''opkg list-installed'''

~~network.lan~~<ol start=~~interface~~"5" style="list-style-type: decimal;"><li>Uninstall the software</li></ol>

~~network.lan.device=~~root@OpenWrt:/# '''opkg remove <package name>''~~br-lan~~'

~~network.lan.proto~~== OpenWRT management interface installation software package ==~~'static'~~

'''~~network~~If you need to add new software packages, you can install them through the OpenWRT management interface.~~lan.ipaddr='192.168.2.1'~~'''

~~network.lan.netmask~~=== View the list of available software packages in the system ===~~'255.255.255.0'~~

~~network~~<ol style="list-style-type: decimal;"><li>First enter the package management pagea.~~lan~~Find the "'''System'''" option in the navigation bar and click to enterb.~~ip6assign=~~In the vertical column options below the system, select "'''software package''60'" and click to enter</li></ol>

[[File:media/image593.…png|552x227px]]

<ol start="32" style="list-style-type: decimal;"><li>Then ~~enter~~ the ~~following command~~ main page of the software package will appear, as shown in the figure below, to ~~modify~~ obtain the list of available softwarea. In the "'''Operation'''" option of the ~~item~~ software package, click "'''~~network~~Update List'''" to get the list of available software packagesb.~~lan.ipaddr~~On the Tab page, click "'''Available'''" to view the currently available software packagesc. View the number of currently available packages[[File:media/image594.png|553x232px]]</li></ol>

~~root@OpenWrt:~# '''uci set network.lan.ipaddr~~=== Example of installing software packages ===~~'192.168.100.1''''~~

<ol ~~start~~style="4list-style-type: decimal;" ><li>Take the installation package “'''luci-app-acl'''” as an example<ol style="list-style-type: ~~decimal~~lower-alpha;"><li>In the OpenWRT software package management interface, click the > filter dialog box and enter”'''luci-app-acl'''”</li><li>In the list of software packages, you can see the version, > package size and description information of the > “'''luci-app-acl'''”software package, and then click the > '''"Install"''' button[[File:media/image595.png|552x259px]]</li><li>Then ~~enter~~ the following ~~command~~ pop-up window will appear, click > '''"Install"'''[[File:media/image596.png|348x430px]]</li><li>Then wait for the installation to complete [[File:media/image597.png|576x96px]]</li><li>The display after the ~~submission~~installation is complete is as follows[[File:media/image598.png|506x289px]]</li></ol></li><li>Check whether the software package is installed successfullya. In the OpenWRT software package management interface, ~~that is~~click the filter dialog box and enter”'''luci-app-acl'''”b. Select and click '''"Available"''' on the Tab pagec. The “'''luci-app-acl'''” package will be displayed in the package list, ~~write to~~ and the ~~configuration file~~update status will be '''"installed"'''[[File:media/image599.png|576x196px]]</li></ol>

~~root@OpenWrt:~# '''uci commit'''~~=== Remove package example ===

If <ol style="list-style-type: decimal;"><li>Take the ~~IP address in red font is consistent with~~ removal of the package”'''luci-app-acl'''” as an example<ol style="list-style-type: lower-alpha;"><li>In the OpenWRT software package management interface, click the > filter dialog box and enter”'''luci-app-acl'''”</li><li>Select '''"Installed"''' on the Tab page to display the list of > installed software packages</li><li>Click '''"Remove"''' on the ~~one~~ right to remove the corresponding > software package[[File:media/image600.png|461x164px]]</li><li>Then the following pop-up window will be ~~set~~displayed, ~~it means that~~ click > '''"Remove"'''[[File:media/image601.png|415x129px]]</li><li>After the ~~modification~~ removal is successful, the display interface is as > follows[[File:media/image602.png|414x88px]]</li></ol></li><li>Check whether the software package is removed successfullya. In the OpenWRT software package management interface, click the filter dialog box and enter “'''luci-app-acl'''”b. Select and click '''"Installed"''' on the Tab pagec. The “'''luci-app-acl'''”package will not be displayed in the package list, and the “'''luci-app-acl'''” package has been removed successfully[[File:media/image603.png|493x187px]]</li></ol>

~~root@OpenWrt:~# '''cat /etc/config~~</~~network'''~~span>== Using Samba Network Shares ==

'''There are mainly two software options for OpenWRT LAN file sharing, Samba and NFS.The compatibility of the Samba system is better, while the performance of NFS is superior.For users who need to use Windows devices, it is recommended to choose Samba.'''

~~config~~ <ol style="list-style-type: decimal;"><li>Enter the management page of the Samba network share<ol style="list-style-type: lower-alpha;"><li>Find the '''"Service"''' option in the navigation bar and click > to enter</li><li>In the vertical column options below the service, select > '''"network sharing"''' and click to enter[[File:media/image604.png|553x205px]]</li></ol></li><li>Select the interface that the Samba service needs to monitor<ol style="list-style-type: lower-alpha;"><li>Select '''"General Settings"''' in the navigation bar of network > sharing and click to enter</li><li>The interface is specified according to actual needs. If you > want to access through the "wan port", set it to '''"wan"'''[[File:media/image605.png|500x222px]]</li></ol></li><li>Set the shared directory of the network sharea. In the '''"Shared Directory"''' of the '''"General Settings"''' of the network share, click '''"Add"''' the shared directory addressb. Enter the name of the shared folder as '''"mmt"''' under the namec. Under the path of the shared directory, choose to set the shared directory location '''"/mnt"'''d. Check '''"Browseable"''' and "Run anonymous user"e. Click '''"Save and Apply"''~~lan~~'to save the configuration<div class="figure">

~~option device 'br-lan'~~[[File:media/image606.png|575x217px|4]]

~~option proto~~ </div></li><li>window10 starts network discovery and sharing'~~static~~''Note: To access Samba under the Windows 10 system, you need to confirm whether Windows 10 has enabled network discovery and sharing for sharing. If it is not enabled, perform the following settings first.'''</li></ol>

~~option netmask '255.255.255~~<ol style="list-style-type: lower-alpha;"><li>Enable Samba v1/v2 accessa) Enter the "Control Panel" of Windows 10b) Click "Programs" on the left navigation bar of the control panelc) Select "Turn Windows features on or off" in Programs and Featuresd) Check "SMB 1.0'/CIFS file sharing support" in the pop-up box of enabling or disabling Windows functionse) Click "OK" to configure the application</li></ol>

~~option ip6assign '60'~~[[File:media/image607.png|575x316px]]

<ol start="2" style="list-style-type: lower-alpha;"><li>Turn on the network discovery of Windows 10a) Enter the "Control Panel" of Windows 10b) Select "Network and Internet" in the Control Panelc) Then open "Network and Sharing Center"d) Click | "Advanced Sharing Settings"e) Turn on '''~~option ipaddr~~ "Enable Network Discovery"'~~192.168.100.1~~''and '''"Enable File and Printer Sharing"'''f) Click "Save Changes" to save the Windows 10 network discovery configuration</li></ol>

[[File:media/image608...png|575x323px]]

<li>~~Restart~~ After the ~~network through ubus~~setting is completed, ~~please refer~~ enter \\OpenWrt in the address bar of the resource manager to access the ~~official document for~~ shared directory, the ~~usage instructions of ubus~~user name is root, and the password is the password set by the development board host</li></ol>

~~root@OpenWrt~~[[File:~~~# '''ubus call network restart'''~~media/image609.png|575x323px]]

<~~ol start~~span id="~~6" style="list~~zerotier-~~style-type: decimal;~~instructions">~~<li~~>~~At this point, enter the command and you can see that the IP of the LAN port is '''192.168.100.1'''~~</pspan>~~root@OpenWrt:~# '''ifconfig br-lan'''br-lan Link encap:Ethernet HWaddr FE:55:13:A3:EF:E7inet addr:'''192.168.100.1''' Bcast:192.168.100.255 Mask:255.255.255.0inet6 addr: fd60:c4cd:1033::1/60 Scope:GlobalUP BROADCAST MULTICAST MTU:1500 Metric:1RX packets:0 errors:0 dropped:0 overruns:0 frame:0TX packets:3 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:0 (0.0 B) TX bytes:370 (370.0 B)</li></ol>~~== Zerotier Instructions ==

~~== How to modify~~ client can directly join it through the ~~root password ==~~Network ID. The specific operation is as shown below.'''

<~~span id~~ol style="~~modify~~list-~~via~~style-~~command~~type: decimal;"><li>Log in to zerotier official website [https://my.zerotier.com/network '''https://my.zerotier.com/network'''], register and log in and click Network-~~line"~~>Create A Network to create a virtual local area network[[File:media/image610.png|575x118px]][[File:media/image611.png|574x166px]]</li><li>Click to enter the network console page, you can set the privacy option to public, so that the added network nodes do not need to be verified[[File:media/image612.png|353x257px]]</li><li>The following automatically assigns the address Here you can choose the network segment yourself, here is 172.27.*.*[[File:media/image613.png|374x233px]]</~~span~~li>~~=== Modify via~~ <li>Enter the following command ~~line ===~~in the OpenWRT terminal to join the virtual LAN created above, '''where 8286ac0e47d53bb5 is the Network ID of the virtual LAN created above'''</li></ol>

root@OpenWrt:/# '''zerotier-one -d''' # ~~First enter passwd root on the command line of the system, and the following prompt message will appear. At this time, you can enter the password you want to set, and press~~ Start the ~~Enter key to confirm~~zerotier client

root@OpenWrt:/# '''~~passwd root~~zerotier-cli join 8286ac0e47d53bb5'''#join the network

<ol start="5" style="list-style-type: decimal;"><li>Enter ifconfig in the terminal and you can see that there is already a new '''ztks54inm2''' device with an IP address of '''~~Enter new UNIX password:~~172.27.214.213'''</li></ol>

~~<ol start="2" style="list-style-type~~root@OpenWrt: ~~decimal;"><li>Then you will be prompted to re-enter the password. At this time, enter the password again to confirm and press Enter<~~/~~li></ol>~~# '''ifconfig'''

'''~~Retype password:~~ztks54inm2'''Link encap:Ethernet HWaddr F6:4E:DE:BF:D8:52

~~<ol start="3" style="list-style-type~~inet addr: ~~decimal;"><li>The display of successful modification is as follows</li></ol>~~'''172.27.214.213''' Bcast:172.27.255.255 Mask:255.255.0.0

~~'''passwd~~inet6 addr: ~~password for root changed by root'''~~fe80::e82f:d0ff:fe5a:867e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:2800 Metric:1

~~=== Modify through the LuCI management interface ===~~RX packets:18 errors:0 dropped:0 overruns:0 frame:0

~~<ol style="list-style-type~~TX packets: ~~decimal;"><li>First refer to the login LuCI management interface to enter the OpenWRT management interface</li><li>Then follow the steps below to change the password<ol style="list-style-type~~48 errors: ~~lower-alpha;"><li>Find the "'''System'''" option in the navigation bar and click</li><li>In the column options below the system, select "'''Management > Rights'''" and click[[File~~0 dropped:~~./images/media/image656.png|552x256px]]</li><li>Select the "'''Router Password'''" option on the Tab page[[File~~0 overruns:~~./images/media/image657.png|552x211px]]</li></ol></li><li>Modify and save the router password<ol style="list-style-type~~0 carrier: ~~lower-alpha;">~~<li>a. Enter the password you set in the "'''Password'''" and "'''Confirm Password'''" dialog boxes (if you are not sure whether the password is entered correctly, you can click the "*" icon behind the dialog box to display the input characters)~~b. Click "'''Save'''" to save the newly modified password[[File:./images/media/image658.png|553x230px]]</li></ol></li></ol>~~0

~~'''Note~~collisions: ~~In the "Password" and "Confirm Password" dialog boxes, the passwords entered twice must be consistent.'''~~0 txqueuelen:1000

~~<ol start="4" style="list-style-type~~RX bytes: ~~decimal;"><li>After the password is changed successfully, a pop-up box will pop up saying "'''The system password has been changed successfully'''"~~1720 (1. ~~At this time, a password is required to log in to OpenWRT[[File:./images/media/image659~~6 KiB) TX byte81 (8.~~png|563x222px]]</li></ol>~~2 KiB)

<~~span id~~ol start="~~usb-interface~~6" style="list-~~test~~style-1type: decimal;"><li>Install the zerotier client on another device (Ubuntu18.04 is used as an example here), execute the following command to install, and restart the computer after the installation is complete</~~span~~li></ol>~~== USB interface test ==~~

~~<~~s https://~~span>=== Mount the USB storage device under the command line ===~~install.zerotier.com | sudo bash'''

~~# First insert the U disk into the USB interface of~~ <ol start="7" style="list-style-type: decimal;"><li>After restarting, join the ~~Orange Pi development board# Execute~~ virtual LAN according to the ~~following command~~Network ID, if and you can also see that the ~~output of sdX~~ip address assigned by zerotier has been obtained. At this time, ~~it means that~~ the ~~U disk is recognized successfully~~Ubuntu PC and OrangePi R1 Plus LTS are in the same LAN, and the two can communicate freely</li></ol>

~~root~~test@~~OpenWrt~~ubuntu:~# $ '''~~cat /proc/partitions | grep "sd*"~~sudo zerotier-cli join 8286ac0e47d53bb5'''

~~major minor #blocks name~~test@ubuntu:~$ '''ifconfig'''

~~8 0 15126528~~ '''~~sda~~ztks54inm2''': flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 2800

~~<ol start="3" style="list-style-type: decimal;"><li>Use the mount command to mount the U disk to /mnt, and then you can view the files in the U disk</li></ol>~~inet '''172.27.47.214''' netmask 255.255.0.0 broadcast 172.27.255.255

~~root@OpenWrt~~inet6 fe80:~~~# '''mount /dev/sda /mnt/'''~~:5ce1:85ff:fe2b:6918 prefixlen 64 scopeid 0x20<link>

~~root@OpenWrt~~ether f6:~~~# '''ls /mnt/'''~~fd:87:68:12:cf txqueuelen 1000 (ethernet)

~~test~~RX packets 0 bytes 0 (0.~~txt~~0 B)

~~<ol start="4" style="list-style-type: decimal;"><li>After mounting, you can view the capacity usage and mount point of the U disk through the df -h command</li></ol>~~RX errors 0 dropped 0 overruns 0 frame 0

~~root@OpenWrt:~# '''df -h | grep "sd"'''~~TX packets 46 bytes 10006 (10.0 KB)

~~/dev/sda 14.4G 187.2M 14.2G 1% /mnt~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

<~~span id~~ol start="~~mount~~8" style="list-~~the-usb-storage-device-on~~style-type: decimal;"><li>Test whether the~~-luci-management-interface"~~two terminals can communicate</li></~~span~~ol>~~=== Mount the USB storage device on the LuCI management interface ===~~

~~<ol style="list-style-type~~root@OpenWrt: ~~decimal;"><li>First connect the U disk (or other storage device) to the development board via USB2~~/# '''ping 172.~~0</li><li>Then follow the login LuCI management interface to enter the LuCI management interface</li><li>Then in the LuCI management interface, click "System -> Mount Point" to enter the configuration interface of the mount point[[File:~~27.~~/images/media/image660~~47.~~png|553x256px]]</li><li>Then follow the steps below to add a mount point<ol style="list-style~~214 -~~type: lower-alpha;"><li>Find "'''Mount Point~~I ztks54inm2'''~~" at the bottom of the mount point > '''global setting interface'''</li><li>Under the mount point, select the "Add" button and click Enter</li></ol></li></ol>~~

~~[[File:~~PING 172.27.47.214 (172.27.~~/images/media/image661~~47.~~png|553x163px]]~~214): 56 data bytes

~~<ol start="3" style="list-style-type: lower-alpha;"><li>Then the following pop-up interface will pop up[[File:~~64 bytes from 172.~~/images/media/image662~~27.~~png|553x288px]]</li><li>Then you can start to mount the storage device</li><li></li><li></li><li></li><li>a) Check "'''Enabled'''"b) Select the actual connected device /dev/sda in the UUID column of general settings (choose according to your own device)c) Select "'''Custom'''" in the mount point column, and fill in the target directory to be mounted~~47. ~~Here, take the '''/mnt''' directory as an example, and press '''Enter''' to confirmd) Then click the "'''Save'''" button in the lower right corner</li></ol>~~1.209 ms

~~[[File~~64 bytes from 172.27.47.214:seq=1 ttl=64 time=1.~~/images/media/image663.png|553x214px]]~~136 ms

~~<ol start~~64 bytes from 172.27.47.214: seq=~~"5" style~~2 ttl=~~"list-style-type: decimal;"><li>Then you will return to the mount point global settings page, click "'''Save and Apply'''" in the lower left corner of the page to make the mount point take effect</li></ol>~~64 time=1.203 ms

~~[[File~~64 bytes from 172.27.47.214:seq=3 ttl=64 time=1.~~/images/media/image664.png|535x325px]]~~235 ms

~~<ol start="6" style="list-style-type: decimal;"><li>After saving, you can see the "'''mounted file system'''", the storage device has been mounted successfully</li></ol>~~^C

~~[[File:~~--- 172.~~/images/media/image665~~27.~~png|553x201px]]~~47.214 ping statistics ---

~~== How to use E-Key PCIe wireless network card ==~~4 packets transmitted, 4 packets received, 0% packet loss

~~# The PCIe wireless network card models currently compatible with the OpenWRT image are as follows：~~round-trip min/avg/max = 1.136/1.195/1.235 ms

~~{| class~~<ol start="~~wikitable~~9"|style="list-~~| '''serial number'''| '''model'''| '''Physical picture'''| '''Supported OS'''~~|style-type: decimal;">~~| '''1'''| '''AX200'''~~<li>other common commands of zerotier</li></ol>

root@OpenWrt:/# '''~~（PCIE+ USB接口)~~zerotier-one -d'''#Start the zerotier client

~~| ! [[.~~root@OpenWrt:/~~images/med%20ia/image310.png|./images/med%20ia/image310.png]]~~| # '''~~Debian~~zerotier-cli status'''#Get address and service status

root@OpenWrt:/# '''~~Ubuntu~~zerotier-cli join # Network ID'''#join the network

root@OpenWrt:/# '''~~OpenWRT~~zerotier-cli leave # Network ID'''#leave the network

root@OpenWrt:/# '''~~OPi OS Arch~~zerotier-cli listnetworks'''#list networks

|-~~| '''2'''| '''AX210'''~~OPENWRT_DEVICE_REVISION="v0"

~~'''（PCIE+ USB接口)'''~~OPENWRT_RELEASE="OpenWrt 22.03.4 r20123-38ccc47687"

~~| [[File:.%20~~</~~images/media/i%20mage311.png]]{wi dth~~span>=~~“1.06875in” h eight~~Compilation method of OpenWRT source code =~~“1.45in”}| '''Debian'''~~

~~'''Ubuntu'''~~== Download OpenWRT source code ==

~~'''OpenWRT'''~~# First execute the following command to download the openwrt-22.03 branch code

test@test:~$ '''~~OPi OS Arch~~sudo apt update'''

|-| test@test:~$ '''~~3'''| '''R TL8852BE~~sudo apt install -y git'''

test@test:~$ '''~~（PCIE+ USB接口)~~git clone https://github.com/orangepi-xunlong/openwrt.git -b openwrt-22.03'''

~~| ! [[./images/med%20ia/image312.png|.~~<ol start="2" style="list-style-type: decimal;"><li>After the OpenWRT code is downloaded, the following files and folders will be included</~~images~~li></~~med%20ia/image312.png]]| '''Debian'''~~ol>

test@test:~/openwrt$ '''~~Ubuntu~~ls'''

~~'''Not Supported OpenWRT'''~~BSDmakefile Config.in include Makefile README.md scripts toolchain

~~'''Android12'''~~Config feeds.conf.default LICENSE package rules.mk target tools

~~'''OPi OS Arch'''~~== Compile OpenWRT source code ==

~~'''OPi OS Droid'''~~<ol style="list-style-type: decimal;"><li>First install the following dependent packages (currently only tested on Ubuntu 20.04 to compile the following dependent packages, if you compile on other versions of the system, please install the dependent packages by yourself according to the error message)<ol style="list-style-type: lower-alpha;"><li>Method 1: The command to install dependent packages using a > script is as follows:</li></ol></li></ol>

|}test@test:~/openwrt$ '''sudo ./install_dep.sh'''

<~~span id~~ol start="~~how~~2" style="list-tostyle-~~create~~type: lower-~~wifi-hotspot~~alpha;"><li>Method 2: Install the dependency package directly using the following command</~~span~~li></ol>~~=== How to create WIFI hotspot ===~~

test@test:~/openwrt$ '''Note that AX200 and AX210 currently only support hotspots in the 2.4G frequency band. In the 5G frequency band mode, there will be an error that the modified configuration of the wireless network card cannot be applied.sudo apt update'''

~~<ol style="list-style-type: decimal;"><li>First insert the PCIe wireless network card into the M.2 E-KEY port of the development board, and then connect the Type-C power supply to power up the development board.[[File:./images/media/image666.png|347x149px]]</li><li>After the system startup is complete, click '''Network -> Wireless''' to enter the wireless WiFi configuration interface.[[File:./images/media/image667.png|553x155px]]</li><li>The default wireless configuration of the OpenWRT system is '''Master''' mode. Here, for the convenience of the next operation, we will remove the default wireless connection.[[File:./images/media/image668.png|517x162px]]</li><li>Then click '''Save''' in the lower right corner of the page to make the configuration take effect.[[File:./images/media/image669.png|553x179px]]</li><li>Then click the '''Add''' button on the right.[[File:./images/media/image670.png|553x138px]]</li><li>In the pop-up tab page '''Device Configuration''', we set the parameters as shown in the figure below.[[File:./images/media/image671.png|552x268px]]</li>~~<li>Then in '''Interface Configuration -> General Settings''', set the mode to '''Access Point AP''', set the '''ESSID''' (wireless network name) to '''OpenWrt''', and specify the network as '''lan'''~~[[File~~test@test:~~./images/media/image672.png|553x234px]]<~~~/~~li><li>Then in~~ openwrt$ '''~~Interface Configuration~~ sudo apt install -~~> Wireless Security''', select ''' WPA2-PSK''' as the encryption algorithm; set the key (wireless password) to '''password'''[[File:./images/media/image673.png|534x224px]]</li><li>After the above settings are completed, click '''Save''' in the lower right corner of the page, and then exit the tab page[[File:./images/media/image674.png|553x303px]]</li><li>Then click '~~y ack antlr3 asciidoc autoconf \''~~Save and Apply~~'~~'' in the lower right corner of the page and wait for the configuration to be applied.[[File:./images/media/image675.png|553x216px]]</li><li>The display interface of successfully creating a hotspot is shown in the figure below[[File:./images/media/image676.png|515x266px]]</li><li>Then use the mobile phone or computer to search for the WiFi corresponding to the SSID to connect. After the connection is successful, as shown in the figure below[[File:./images/media/image677.png|247x156px]]</li></ol>~~

~~=== How to connect to WIFI hotspot ===~~essential \'''

~~<ol style="list-style-type: decimal;"><li>Insert the PCIe wireless network card into the M.2 E-KEY port of the development board, and then connect the Type-C power supply to power the development board.[[File:./images/media/image666.png|347x149px]]</li><li>After the system startup is complete, click~~ '''~~Network~~ bzip2 ccache cmake cpio curl device-~~> Wireless''' to enter the configuration wireless WiFi interface.[[File:./images/media/image667.png|553x155px]]</li><li>The default wireless configuration of the OpenWRT system is '''Master''' mode. Here, for the convenience of the next operation, we will remove the default wireless connection.[[File:./images/media/image668.png|520x162px]]</li><li>Then click '''Save''' in the lower right corner of the page to make the configuration take effect.[[File:./images/media/image669.png|520x179px]]</li><li>Then click the '''Scan''' button to scan the surrounding WiFi hotspots.[[File:./images/media/image678.png|541x225px]]</li>~~<li>Then the following window will pop up to display the available WiFi hotspots. At this time, click the '''Join Network''' button on the right side of the WiFi hotspot you want to connect to connect to the WiFi hotspot.~~[[File:./images/media/image679.png|553x89px]]</li>~~<li>Then an interface for connecting to a WiFi hotspot will pop up. We enter the password of the hotspot as shown in the figure below, and then click the '''Submit''' button.~~[[File:./images/media/image680.png|552x135px]]</li><li>Then the following interface will pop up, click the '''Save''' button in the lower right corner.[[File:./images/media/image681.png|553x237px]]</li><li>Finally, you will return to the main interface of wireless configuration, click '''Save and Apply~~tree-compiler fastjar \''' ~~and wait for the configuration to be applied.[[File:./images/media/image682.png|544x252px]]</li><li>After successfully connecting to the WiFi hotspot, the interface is displayed as shown in the figure below.[[File:./images/media/image683.png|547x232px]]</li></ol>~~

~~== Installing packages via the command line ==~~multilib git gperf haveged \'''

~~=== Install via opkg in the terminal ===~~dev \'''

~~# Update the list of available packages~~'''libgmp3-dev libltdl-dev libmpc-dev libmpfr-dev \'''

~~root@OpenWrt:/#~~ '''~~opkg''' '''update~~libncurses5-dev \libncursesw5-dev libreadline-dev libssl-dev \'''

~~<ol start="2" style="list~~'''libtool lrzsz mkisofs msmtp nano ninja-~~style~~build p7zip p7zip-~~type: decimal;"><li>Get the software list</li></ol>~~full \'''

~~root~~'''patch pkgconf python2.7 python3 python3-pyelftools \''' '''libpython3-dev qemu-utils rsync scons squashfs-tools \''' '''subversion swig texinfo uglifyjs upx-ucl unzip \''' '''vim wget xmlto xxd zlib1g-dev''' <ol start="2" style="list-style-type: decimal;"><li>Then execute '''./scripts/feeds update -a''' and '''./scripts/feeds install -a''' to download dependent packages</li></ol> test@~~OpenWrt~~test:~/# openwrt$ '''~~opkg~~./scripts/feeds update -a''' test@test:~/openwrt$ '''~~list~~./scripts/feeds install -a'''

<li>~~Install~~ Then choose to use the ~~specified package~~configuration file of OrangePi 5 Plus<ol style="list-style-type: lower-alpha;"><li>Compile the image that supports TF card, eMMC, and NVMe startup, > and select the following configuration</li></ol></li></ol> test@test:~/openwrt$ '''cp configs/orangepi-5-plus-rk3588_defconfig .config''' <ol start="2" style="list-style-type: lower-alpha;"><li>Compile the image that supports SPIFlash startup, and select the > following configuration</li></ol>

~~root~~test@~~OpenWrt~~test:~/# openwrt$ '''~~opkg''' '''install <package name>~~cp configs/orangepi-5-plus-rk3588-spi_defconfig .config'''

<li>~~Check~~ Then execute the ~~installed software~~following command to make the configuration take effect</li></ol>

~~root~~test@~~OpenWrt~~test:~/# openwrt$ '''~~opkg''' '''list-installed~~make defconfig'''

<li>~~Uninstall~~ Execute the ~~software~~following command to start compiling the openwrt source code</li></ol> test@test:~/openwrt$ '''make V=s''' <ol start="6" style="list-style-type: decimal;"><li>After the compilation is complete, the path where the image is generated is:</li></ol>

~~root~~test@~~OpenWrt~~test:~/# openwrt$ '''~~opkg''' '''remove''' '''<package name>~~tree -L 1 bin/targets/rockchip/armv8/'''

~~<~~bin/targets/rockchip/armv8/~~span>== OpenWRT management interface installation software package ==~~

~~'''If you need to add new software packages, you can install them through the OpenWRT management interface~~├── config.~~'''~~buildinfo

~~=== View the list of available software packages in the system ===~~├── feeds.buildinfo

~~<ol style="list~~├── openwrt-~~style~~rockchip-~~type: decimal;"><li>First enter the package management page<ol style="list~~armv8-~~style~~xunlong_orangepi-~~type: lower~~5-~~alpha;"><li>a~~plus-ext4-sysupgrade. ~~Find the "'''System'''" option in the navigation bar and click to enterb~~img. ~~In the vertical column options below the system, select "'''software package'''" and click to enter</li></ol></li></ol>~~gz

~~[[File:~~├── openwrt-rockchip-armv8-xunlong_orangepi-5-plus.~~/images/media/image684.png|552x227px]]~~manifest

~~<ol start="2" style="list~~├── openwrt-~~style~~rockchip-~~type: decimal;"><li>Then the main page of the software package will appear, as shown in the figure below, to obtain the list of available software<ol style="list~~armv8-~~style~~xunlong_orangepi-~~type: lower~~5-~~alpha;"><li></li><li>a. In the "'''Operation'''" option of the software package, click "'''Update List'''" to get the list of available software packagesb. On the Tab page, click "'''Available'''" to view the currently available software packagesc. View the number of currently available packages[[File:~~plus-squashfs-sysupgrade.~~/images/media/image685~~img.~~png|553x232px]]</li></ol></li></ol>~~gz

~~=== Example of installing software packages ===~~

~~<ol style="list-style-type: decimal;"><li>Take the installation package “'''luci-app-acl'''” as an example<ol style="list-style-type: lower-alpha;"><li>In the OpenWRT software package management interface, click the > filter dialog box and enter”'''luci-app-acl'''”</li>~~<li>In the list of software packages, you can see the version, > package size and description information of the > “'''luci-app-acl'''”software package, and then click the > '''"Install"''' button~~[[File:~~├── profiles.~~/images/media/image686.png|552x259px]]</li><li>Then the following pop-up window will appear, click > '''"Install"'''[[File:./images/media/image687.png|348x430px]]</li><li>Then wait for the installation to complete[[File:./images/media/image688.png|576x96px]]</li><li>The display after the installation is complete is as follows[[File:./images/media/image689.png|506x289px]]</li></ol></li><li>Check whether the software package is installed successfully<ol style="list-style-type: lower-alpha;"><li></li><li>a. In the OpenWRT software package management interface, click the filter dialog box and enter”'''luci-app-acl'''”b. Select and click '''"Available"''' on the Tab pagec. The “'''luci-app-acl'''” package will be displayed in the package list, and the update status will be '''"installed"'''[[File:./images/media/image690.png|576x196px]]</li></ol></li></ol>~~json

~~=== Remove package example ===~~├── sha256sums

~~<ol style="list-style-type: decimal;"><li>Take the removal of the package”'''luci-app-acl'''” as an example<ol style="list-style-type: lower-alpha;"><li>In the OpenWRT software package management interface, click the > filter dialog box and enter”'''luci-app-acl'''”</li><li>Select '''"Installed"''' on the Tab page to display the list of > installed software packages</li><li>Click '''"Remove"''' on the right to remove the corresponding > software package[[File:~~└── version.~~/images/media/image691.png|461x164px]]</li><li>Then the following pop-up window will be displayed, click > '''"Remove"'''[[File:./images/media/image692.png|415x129px]]</li><li>After the removal is successful, the display interface is as > follows[[File:./images/media/image693.png|414x88px]]</li></ol></li><li>Check whether the software package is removed successfully<ol style="list-style-type: lower-alpha;"><li></li><li>a. In the OpenWRT software package management interface, click the filter dialog box and enter “'''luci-app-acl'''”b. Select and click '''"Installed"''' on the Tab pagec. The “'''luci-app-acl'''”package will not be displayed in the package list, and the “'''luci-app-acl'''” package has been removed successfully[[File:./images/media/image694.png|493x187px]]</li></ol></li></ol>~~buildinfo

~~== Using Samba Network Shares ==~~1 directory, 9 files

~~'''There are mainly two software options~~ = Instructions for using the ~~performance of NFS is superior. For users who need to use Windows devices, it is recommended to choose Samba.'''~~Android 12 system =

<~~ol style~~span id="~~list~~supported-~~style~~android-~~type: decimal;~~versions">~~<li>Enter the management page of the Samba network share~~</pspan>~~<ol style~~=~~"list-style-type: lower-alpha;"><li>Find the '''"Service"''' option in the navigation bar and click > to enter</li><li>In the vertical column options below the service, select > '''"network sharing"''' and click to enter[[File:./images/media/image695.png|553x205px]]</li></ol></li><li>Select the interface that the Samba service needs to monitor<ol style~~=~~"list-style-type: lower-alpha;"><li>Select '''"General Settings"''' in the navigation bar of network > sharing and click to enter</li><li>The interface is specified according to actual needs. If you > want to access through the "wan port", set it to '''"wan"'''[[File:./images/media/image696.png|500x222px]]</li></ol></li><li>Set the shared directory of the network share<ol style~~Supported Android versions =~~"list-style-type: lower-alpha;"><li></li><li></li><li></li><li>a. In the '''"Shared Directory"''' of the '''"General Settings"''' of the network share, click '''"Add"''' the shared directory addressb. Enter the name of the shared folder as '''"mmt"''' under the namec. Under the path of the shared directory, choose to set the shared directory location '''"/mnt"'''d. Check '''"Browseable"''' and "Run anonymous user"e. Click '''"Save and Apply"''' to save the configuration<div class~~=~~"figure">~~

~~[[File~~{| class="wikitable"|-| style="text-align: left;"| '''Android version'''| style="text-align: left;"| '''kernel version'''|-| style="text-align: left;"| '''Android 12'''| style="text-align:left;"| '''Linux5.~~/images/media/image697~~10'''|-| style="text-align: left;"| '''Android 12 Box'''| style="text-align: left;"| '''Linux5.~~png|575x217px~~10'''|~~4]]~~}

<~~/div></li></ol~~span id="android-function-adaptation"></lispan>~~<li>window10 starts network discovery and sharing~~'''Note: To access Samba under the Windows 10 system, you need to confirm whether Windows 10 has enabled network discovery and sharing for sharing. If it is not enabled, perform the following settings first.'''</li></ol>== Android function adaptation ==

~~<!-- -~~{| class="wikitable"|->~~<ol~~ | style="~~list-style~~text-~~type~~align: ~~lower-alpha~~left;">| '''Function'''~~<li>Enable Samba v1/v2 access<ol~~ | style="~~list~~text-~~style-type~~align: ~~lower-alpha~~left;">~~<li></li><li></li>~~| '''Android 12'''~~<li></li><li>a) Enter the &quot~~| style="text-align: left;~~Control Panel" of Windows 10~~"| '''Android12 Box'''~~b) Click "Programs" on the left navigation bar of the control panel~~|-~~c) Select "Turn Windows features on or off" in Programs and Featuresd) Check "SMB 1.0/CIFS file sharing support" in the pop-up box of enabling or disabling Windows functionse) Click "OK" to configure the application</li></ol></li></ol>~~ ~~[[File:./images/media/image698.png~~|~~575x316px]]~~ ~~<ol start="2"~~ style="~~list-style~~text-~~type~~align: ~~lower-alpha~~left;">~~<li>Turn on the network discovery of Windows 10~~| '''HDMI TX1 Display - 1080p'''~~<ol~~ | style="~~list-style~~text-~~type~~align: ~~lower-alpha~~left;">~~<li></li><li></li><li></li><li></li><li>a) Enter the "Control Panel" of Windows 10b) Select "Network and Internet" in the Control Panelc) Then open "Network and Sharing Center"d) Click~~ | ~~"Advanced Sharing Settings"e) Turn on~~ '''~~"Enable Network Discovery"~~OK''' ~~and~~ | style="text-align: left;"| '''~~"Enable File and Printer Sharing"~~OK'''~~f) Click "Save Changes" to save the Windows 10 network discovery configuration</li></ol></li></ol>~~|-~~[[File:./images/media/image699.png~~|~~575x323px]]~~ ~~<ol start="5"~~ style="~~list~~text-~~style-type~~align: ~~decimal~~left;"><li>After the setting is completed, enter \\OpenWrt in the address bar of the resource manager to access the shared directory, the user name is root, and the password is the password set by the development board host</li></ol> ~~[[File:./images/media/image700.png~~|~~575x323px]]~~ ~~== Zerotier Instructions ==~~ '''~~The OpenWRT system has pre~~HDMI TX1 Display -~~installed the zerotier client. After creating a virtual LAN on the zerotier official website, the client can directly join it through the Network ID. The specific operation is as shown below.~~4K 120HZ''' ~~<ol~~ | style="~~list-style~~text-~~type~~align: ~~decimal~~left;">~~<li>Log in to zerotier official website~~ | '''~~https://my.zerotier.com/network~~OK'''~~, register and log in and click Network~~| style="text-~~&gt~~align: left;~~Create A Network to create a virtual local area network~~"| '''OK'''~~[[File:./images/media/image701.png~~|~~575x118px]]~~-~~[[File:./images/media/image702.png~~|~~574x166px]]</li><li>Click to enter the network console page, you can set the privacy option to public, so that the added network nodes do not need to be verified[[File~~style="text-align:~~./images/media/image703.png~~left;"|~~353x257px]]</li><li>The following automatically assigns the address Here you can choose the network segment yourself, here is 172.27.*.*[[File:./images/media/image704.png|374x233px]]</li><li>Enter the following command in the OpenWRT terminal to join the virtual LAN created above,~~ '''~~where 8286ac0e47d53bb5 is the Network ID of the virtual LAN created above~~HDMI TX1 Display - 8K 60HZ'''~~</li></ol>~~ ~~root@OpenWrt~~| style="text-align:~~/# ''~~left;"| '''~~zerotier-one -d~~OK''' ~~#Start the zerotier client~~ ~~root@OpenWrt~~| style="text-align:/# left;"| '''~~zerotier-cli join 8286ac0e47d53bb5~~OK''' ~~#join the network~~|-~~<ol start="5"~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">~~<li>Enter ifconfig in the terminal and you can see that there is already a new~~ | '''~~ztks54inm2~~HDMI TX1 Audio''' ~~device with an IP address of~~ | style="text-align: left;"| '''~~172.27.214.213~~OK'''~~</li></ol>~~ ~~root@OpenWrt~~| style="text-align:/# left;"| '''~~ifconfig~~OK'''|-| style="text-align: left;"| '''~~ztks54inm2~~HDMI TX2 Display - 1080p''' ~~Link encap:Ethernet HWaddr F6:4E:DE:BF:D8:52~~ ~~inet addr~~| style="text-align:left;"| '''~~172.27.214.213~~OK''' ~~Bcast~~| style="text-align:~~172.27.255.255 Mask:255.255.0.0~~left;"| '''OK'''|-~~inet6 addr: fe80:~~| style="text-align:~~e82f:d0ff:fe5a:867e/64 Scope:Link~~left;"| '''HDMI TX2 Display - 4K 120HZ''' ~~UP BROADCAST RUNNING MULTICAST MTU~~| style="text-align:~~2800 Metric:1~~ ~~RX packets:18 errors:0 dropped:0 overruns:0 frame:0~~left;"| '''OK''' ~~TX packets~~| style="text-align:~~48 errors:0 dropped:0 overruns:0 carrier:0~~left;"| '''OK'''|-~~collisions:0 txqueuelen:1000~~ ~~RX bytes:1720 (1.6 KiB) TX byte81 (8.2 KiB)~~ ~~<ol start="6"~~ | style="~~list~~text-~~style-type: decimal~~align: left;"><li>Install the zerotier client on another device (Ubuntu18.04 is used as an example here), execute the following command to install, and restart the computer after the installation is complete</li></ol> ~~test@ubuntu:~$~~ | '''~~curl~~ HDMI TX2 Display -~~s https://install.zerotier.com | sudo bash~~8K 60HZ''' ~~<ol start="7"~~ | style="~~list-style~~text-~~type~~align: ~~decimal~~left;"><li>After restarting, join the virtual LAN according to the Network ID, and you can also see that the ip address assigned by zerotier has been obtained. At this time, the Ubuntu PC and OrangePi R1 Plus LTS are in the same LAN, and the two can communicate freely</li></ol> ~~test@ubuntu:~$~~ | '''~~sudo zerotier-cli join 8286ac0e47d53bb5~~OK''' ~~test@ubuntu~~| style="text-align:~$ left;"| '''~~ifconfig~~OK'''|-| style="text-align: left;"| '''~~ztks54inm2~~HDMI TX2 Audio'''| style="text-align: ~~flags=4163&lt~~left;~~UP,BROADCAST,RUNNING,MULTICAST> mtu 2800~~ ~~inet~~ "| '''~~172.27.47.214~~OK''' ~~netmask 255.255.0.0 broadcast 172.27.255.255~~ ~~inet6 fe80~~| style="text-align:~~:5ce1:85ff:fe2b:6918 prefixlen 64 scopeid 0x20<link&gt~~left;"| '''OK'''|-~~ether f6~~| style="text-align:~~fd:87:68:12:cf txqueuelen 1000 (ethernet)~~ left;"| '''HDMI RX ~~packets 0 bytes 0 (0.0 B)~~display''' ~~RX errors 0 dropped 0 overruns 0 frame 0~~ ~~TX packets 46 bytes 10006 (10.0 KB)~~ ~~TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0~~ ~~<ol start="8"~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">| '''OK'''~~<li>Test whether the two terminals can communicate</li></ol>~~ ~~root@OpenWrt~~| style="text-align:/# left;"| '''~~ping 172.27.47.214 -I ztks54inm2~~OK'''|-~~PING 172.27.47.214 (172.27.47.214)~~| style="text-align: ~~56 data bytes~~left;"| '''HDMI RX Audio''' ~~64 bytes from 172.27.47.214~~| style="text-align: ~~seq=0 ttl=64 time=1.209 ms~~left;"| '''OK''' ~~64 bytes from 172.27.47.214: seq~~| style=~~1 ttl=64 time=1.136 ms~~ ~~64 bytes from 172.27.47.214~~"text-align: ~~seq=2 ttl=64 time=1.203 ms~~left;"| '''OK'''|-~~64 bytes from 172.27.47.214: seq~~| style=~~3 ttl=64 time=1.235 ms~~ ^C "text-~~-- 172~~align: left;"| '''USB2.~~27.47.214 ping statistics ---~~0X2''' ~~4 packets transmitted, 4 packets received, 0% packet loss~~ ~~round~~| style="text-~~trip min/avg/max = 1.136/1.195/1.235 ms~~align: left;"| '''OK''' ~~<ol start="9"~~ | style="~~list-style~~text-~~type~~align: ~~decimal~~left;">~~<li>other common commands of zerotier</li></ol>~~ ~~root@OpenWrt:/#~~ | '''~~zerotier-one -d~~OK''' ~~#Start the zerotier client~~|-~~root@OpenWrt~~| style="text-align:/# left;"| '''~~zerotier-cli status~~2.5G PCIe network port X2''' ~~#Get address and service status~~ ~~root@OpenWrt~~| style="text-align:/# left;"| '''~~zerotier-cli join # Network ID~~OK''' ~~#join the network~~ ~~root@OpenWrt~~| style="text-align:/# left;"| '''~~zerotier-cli leave # Network ID~~OK''' ~~#leave the network~~|-~~root@OpenWrt~~| style="text-align:/# left;"| '''~~zerotier-cli listnetworks~~2.5G PCIe network port light''' ~~#list networks~~ ~~OPENWRT_DEVICE_REVISION~~| style=~~"v0&quot~~"text-align: left;"| '''OK''' ~~OPENWRT_RELEASE~~| style=~~"OpenWrt 22.03.4 r20123~~"text-~~38ccc47687&quot~~align: left;"| '''OK'''|-~~= Compilation method of OpenWRT source code =~~ ~~== Download OpenWRT source code ==~~ ~~# First execute the following command to download the openwrt-22.03 branch code~~ ~~test@test:~$~~ | '''~~sudo apt update~~Debug serial port''' ~~test@test~~| style="text-align:~~~$ '''sudo apt install~~left;"| ''' OK'''| style="text-yalign: left;"| ''' ~~'''git~~OK'''|-~~test@test:~$~~ | style="text-align: left;"| '''~~git clone~~RTC''' ~~'''https~~| style="text-align:~~//github.com/orangepi-xunlong/openwrt.git~~left;"| ''' OK'''| style="text-~~b openwrt-22.03~~align: left;"| '''OK'''|-~~<ol start="2"~~ | style="~~list-style~~text-~~type~~align: ~~decimal~~left;">~~<li>After the OpenWRT code is downloaded, the following files and folders will be included</li></ol>~~ ~~test@test:~/openwrt$~~ | '''lsFAN interface''' ~~BSDmakefile Config.in include Makefile README.md scripts toolchain~~ ~~Config feeds.conf.default LICENSE package rules.mk target tools~~ ~~~~| '''OK'''~~== Compile OpenWRT source code ==~~ ~~<ol~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">| '''OK'''<li>First install the following dependent packages (currently only tested on Ubuntu 20.04 to compile the following dependent packages, if you compile on other versions of the system, please install the dependent packages by yourself according to the error message)|-~~<ol~~ | style="~~list-style~~text-~~type~~align: ~~lower-alpha~~left;">~~<li>Method 1: The command to install dependent packages using a > script is as follows:</li></ol></li></ol>~~ ~~test@test:~/openwrt$~~ | '''~~sudo ./install_dep.sh~~eMMC extension interface''' ~~<ol start="2" style~~| style="~~list-style~~text-~~type~~align: ~~lower-alpha~~left;">~~<li>Method 2: Install the dependency package directly using the following command</li></ol>~~ ~~test@test:~/openwrt$~~ | '''~~sudo apt update~~OK''' ~~test@test~~| style="text-align:~~~/openwrt$~~ left;"| '''~~sudo apt install -y ack antlr3 asciidoc autoconf~~OK''' |-| style="text-align: left;"| '''\AP6275P-WIFI''' ~~'''automake autopoint binutils bison build~~| style="text-~~essential~~align: left;"| ''' ~~'''\~~OK''' | style="text-align: left;"| '''~~bzip2 ccache cmake cpio curl device-tree-compiler fastjar~~OK''' |-| style="text-align: left;"| '''\AP6275P-BT''' ~~'''flex gawk gettext gcc~~| style="text-~~multilib g++-multilib git gperf haveged~~align: left;"| ''' OK'''\| style="text-align: left;"| ''' OK'''~~help2man intltool libc6~~|-~~dev~~| style="text-~~i386 libelf-dev libglib2.0-dev~~align: left;"| ''' AX200-WIFI'''\| style="text-align: left;"| ''' NO'''~~libgmp3-dev libltdl~~| style="text-~~dev libmpc-dev libmpfr-dev'''~~ align: left;"| '''\NO'''|-| style="text-align: left;"| '''~~libncurses5~~AX200-~~dev~~BT''' ~~'''\libncursesw5~~| style="text-~~dev libreadline-dev libssl-dev'''~~ align: left;"| '''\NO''' ~~'''libtool lrzsz mkisofs msmtp nano ninja~~| style="text-~~build p7zip p7zip-full'~~align: left;"| '' '~~''\~~NO'''|-| style="text-align: left;"| '''~~patch pkgconf python2.7 python3 python3~~AX210-~~pyelftools \~~WIFI''' ~~'''libpython3~~| style="text-~~dev qemu-utils rsync scons squashfs-tools'~~align: left;"| '' '~~''\~~NO''' | style="text-align: left;"| '''~~subversion swig texinfo uglifyjs upx-ucl unzip \~~NO''' ~~'''vim wget xmlto xxd zlib1g~~|-~~dev'''~~ ~~<ol start="2"~~ | style="~~list-style~~text-~~type~~align: ~~decimal~~left;">~~<li>Then execute~~ | '''~~./scripts/feeds update~~ AX210-aBT''' ~~and~~ | style="text-align: left;"| '''~~./scripts/feeds install -a~~NO''' ~~to download dependent packages</li></ol>~~ ~~test@test~~| style="text-align:~~~/openwrt$~~ left;"| '''~~./scripts/feeds update -a~~NO'''|-~~test@test:~/openwrt$ '~~| style="text-align: left;"| '''~~./scripts/feeds install~~ RTL8852BE-aWIFI''' ~~<ol start="3"~~ | style="~~list~~text-~~style-type~~align: ~~decimal~~left;">| '''OK'''~~<li>Then choose to use the configuration file of OrangePi 5 Plus<ol~~ | style="~~list~~text-~~style-type~~align: ~~lower~~left;"| '''OK'''|-~~alpha~~| style="text-align: left;">| '''RTL8852BE-BT'''~~<li>Compile the image that supports TF card, eMMC, and NVMe startup, &gt~~| style="text-align: left; ~~and select the following configuration</li></ol>~~"| '''OK'''~~</li></ol>~~| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''Recovery button'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''Type-C interface USB3.0 function'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''Type-C interface ADB function'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''Type-C interface DP display function'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''Type-C interface DP audio playback'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''USB3.0 Hub'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''switch button'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''infrared function'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''led light'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''Onboard MIC'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''headphone playback'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''headphone recording'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''SPK Horn'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''40PIN GPIO'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''40PIN I2C'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''40PIN SPI'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''40PIN UART'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''40PIN PWM'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''TF card start'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''SPI Flash+NVME solid state boot'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''OV13850 camera'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''OV13855 camera'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''GPU'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''VPU'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''NPU'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''MIPI LCD display'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''MIPI LCD Touch'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''MIPI LCD backlight'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''|-| style="text-align: left;"| '''HDMI CEC function'''| style="text-align: left;"| '''NO'''| style="text-align: left;"| '''OK'''|}

~~test@test:~/openwrt$ '''cp configs/orangepi~~== How to use the USB wireless network card ==

~~<ol start="2" style="list-style-type: lower-alpha;"><li>Compile~~ # Currently, the USB wireless network card models compatible with the Android image ~~that supports SPIFlash startup, and select the > following configuration</li></ol>~~are as follows：

~~test@test~~{| class="wikitable"|-| style="text-align: left;"| '''Chip model'''| style="text-align: left;"| '''Function'''| style="text-align: left;"| '''VID&PID'''| style="text-align: left;"| '''Adaptation'''|-| style="text-align: left;"| '''RTL8723BU'''| style="text-align: left;"| '''2.4G WIFI+BT4.0'''| style="text-align: left;"| '''0bda:~~~/openwrt$~~ b720'''~~cp configs/orangepi~~| style="text-5align: left;"| '''Support WIFI and Bluetooth function, does not support hotspot'''|-~~plus~~| style="text-~~rk3588~~align: left;"| '''RTL8811CU'''| style="text-~~spi_defconfig~~ align: left;"| '''2.~~config~~4G +5G WIFI'''| style="text-align: left;"| '''0bda:c811'''| style="text-align: left;"| '''Support WIFI function and open hotspot'''|}

<ol start="42" style="list-style-type: decimal;"><li>The pictures of the above two USB wireless network cards are as follows：<ol style="list-style-type: lower-alpha;"><li>The picture of the RTL8723BU USB wireless network card module is > as follows：<div class="figure"> [[File:media/image614.png|175x103px|C89CEA9A-B322-42d2-B476-2392A50E6FC4]] </div></li><li>The picture of the RTL8811CU USB wireless network card module is > as follows：[[File:media/image615.png|124x107px]]</li></ol></li><li>The test methods of the above two types of USB wireless network cards are the same. First, the USB network card needs to be inserted into the USB interface of the development board.</li><li>Then ~~execute~~ , for the connection and test method of WIFI, please refer to the section of WIFI connection test method</li><li>For the ~~following command~~ Bluetooth test, please refer to ~~make~~ the ~~configuration take effect~~content of the Bluetooth test method</li></ol>

~~test@test:~~~</~~openwrt$ '''make''' '''defconfig'''~~span>== M.2 How to use E-Key PCIe WIFI6+Bluetooth module ==

~~<ol start="5" style="list-style-type: decimal;"><li>Execute the following command to start compiling the openwrt source code</li></ol>~~# The PCIe wireless network card models currently compatible with Android 12 are as follows：

~~test@test:~/openwrt$~~ {| class="wikitable"|-| '''serial number'''| '''model'''| '''Physical picture'''~~make V=s~~|-| '''1'''| '''RTL8852BE'''

~~<ol start="6" style="list-style-type: decimal;"><li>After the compilation is complete, the path where the image is generated is:</li></ol>~~'''(PCIE+USB interface)'''

~~test@test~~| [[File:~media/~~openwrt$ '''tree -L 1 bin/targets/rockchip/armv8/'''~~image6%2016.png]]|}

~~bin~~<ol start="2" style="list-style-type: decimal;"><li>First insert the PCIe wireless network card into the M.2 E-KEY interface of the development board and fix it</~~targets~~p>[[File:media/~~rockchip~~image617.png|263x178px]]</~~armv8~~p></li><li>Then connect the power supply of the Type-C interface to the development board, and power on</li><li>After the system starts, please refer to the section of WIFI connection test method for WIFI connection and test method</li><li>For the Bluetooth test, please refer to the content of the Bluetooth test method</li></ol>

~~├── config.buildinfo~~== WIFI connection test method ==

~~├── feeds~~'''First of all, please note that there is no WIFI module on the Orange Pi 5 Plus development board, and an external PCIe network card or USB network card is required to use the WIFI function.~~buildinfo~~'''

~~├── openwrt-rockchip-armv8-xunlong_orangepi-5-plus-ext4~~'''For instructions on using the external PCIe network card, please refer to the section on how to use the M.2 E-~~sysupgrade.img~~Key PCIe WIFI6+Bluetooth module.gz'''

~~├── openwrt-rockchip-armv8-xunlong_orangepi-5-plus~~'''For instructions on using the external USB network card, please refer to the section on how to use the USB wireless network card.~~manifest~~'''

~~├── openwrt-rockchip-armv8-xunlong_orangepi-5-plus-squashfs-sysupgrade.img.gz~~# First click to enter the '''Setting'''

~~├── packages~~[[File:media/image618.png|553x182px]]

~~├── profiles.json~~<ol start="2" style="list-style-type: decimal;"><li>Then select '''Network & internet'''</li></ol>

~~├── sha256sums~~[[File:media/image619.png|553x154px]]

~~└── version.buildinfo~~<ol start="3" style="list-style-type: decimal;"><li>Then select '''Internet'''</li></ol>

~~1 directory, 9 files~~[[File:media/image620.png|553x103px]]

<~~span id~~ol start="~~instructions~~4" style="list-~~for-using~~style-type: decimal;"><li>Then turn on the'''Wi-~~android-12-system"~~Fi''' switch</li></~~span~~ol>~~= Instructions for using the Android 12 system =~~

~~<~~[[File:media/~~span>== Supported Android versions ==~~image621.png|553x65px]]

~~{| class~~<ol start="5" style="~~wikitable~~list-style-type: decimal;"><li>After turning on '''Wi-Fi''', if everything is normal, you can scan to nearby Wi-Fi hotspots[[File:media/image622.png|549x172px]]</li><li>Then select the Wi-Fi you want to connect to, and the password input interface shown in the figure below will pop up[[File:media/image623.png|553x237px]]</li><li>Then use the keyboard to enter the password corresponding to Wi-Fi, and then use the mouse to click the Enter button in the virtual keyboard to start connecting to Wi-Fi[[File:media/image624.png|553x232px]]</li><li>The display after successful Wi-Fi connection is shown in the figure below：[[File:media/image625.png| 553x93px]]</li></ol> == How to use Wi-Fi hotspot == <ol style="~~text~~list-style-~~align~~type: ~~left~~decimal;"| ><li>First, please make sure that the Ethernet port is connected to the network cable and can access the Internet normally</li><li>Then select '''~~Android~~Settings''' [[File:media/image618.png|553x182px]]</li><li>Then select '''~~version~~Network & internet'''~~| style="text-align~~[[File: ~~left;"~~media/image619.png| 553x154px]]</li><li>Then select '''~~kernel version~~Hotspot & tethering'''[[File:media/image626.png|575x195px]]</li><li>Then select '''Wi-Fi hotspot'''[[File:media/image627.png| ~~style="text~~575x96px]]</li><li>Then turn on the '''Wi-~~align: left;"|~~ Fi hotspot''', you can also see the name and password of the generated hotspot in the figure below, remember them, and use them when connecting to the hotspot '''~~Android 12~~(if you need to modify the name and password of the hotspot, you need to turn off the Wi-Fi first -Fi hotspot before modification)'''~~| style="text-align~~[[File: ~~left;"~~media/image628.png| 575x187px]]</li><li>At this point, you can take out your mobile phone. If everything is normal, you can find the WIFI hotspot with the same name ('''here AndroidAP_6953''') displayed under the '''Hotspot name'''~~Linux5~~in the above picture in the WI-FI list searched by the mobile phone.10Then you can click '''AndroidAP_6953'''to connect to the hotspot, and the password can be seen under the '''Hotspot password''' in the above picture</li></ol> [[File:media/image629.png|-342x260px]] | <ol start="8" style="~~text~~list-~~align~~style-type: ~~left~~decimal;"| ><li>After the connection is successful, it will be displayed as shown in the figure below (the interface of different mobile phones will be different, the specific interface is subject to the display of your mobile phone). At this point, you can open a webpage on your mobile phone to see if you can access the Internet. If you can open the webpage normally, it means that the '''~~Android 12 Box~~WI-FI Hotspot'''of the development board can be used normally.</li></ol> [[File:media/image630.png| ~~style~~347x175px]] == Bluetooth test method == '''~~Linux5~~Please note that there is no Bluetooth module on the Orange Pi 5 Plus development board, and an external PCIe network card with Bluetooth or a USB network card with Bluetooth is required to use the Bluetooth function.10'''|}'''For instructions on using the external PCIe network card, please refer to the section on how to use the M.2 E-Key PCIe WIFI6+Bluetooth module.'''

~~== Android function adaptation ==~~'''For instructions on using the external USB network card, please refer to the section on how to use the USB wireless network card.'''

~~{| class~~<ol style="~~wikitable"~~|list-| style~~="text~~-~~align~~type: ~~left~~decimal;"| ><li>First click to enter the '''~~Function~~Setting'''~~| style="text-align~~[[File: ~~left;"~~media/image618.png| 553x182px]]</li><li>Then select '''~~Android 12~~Connected devices'''[[File:media/image631.png| ~~style="text-align: left;"|~~ 575x146px]]</li><li>Then click '''~~'Android12 Box~~Pair new device'''to turn on Bluetooth and start scanning the surrounding Bluetooth devices[[File:media/image632.png|-575x144px]]</li>~~| style="text-align: left;"|~~ <li>The searched Bluetooth devices will be displayed under '''~~HDMI TX1 Display - 1080p~~Available devices'''[[File:media/image633.png| ~~style="text-align: left;"|~~ 575x200px]]</li><li>Then click the Bluetooth device you want to connect to start pairing. When the following interface pops up, please use the mouse to select the '''OKPair'''option~~| style="text-align~~[[File: ~~left;"~~media/image634.png| ~~'''OK'''~~575x155px]]</li>|-<li>The test here is the configuration process of the development board and the Bluetooth of the Android mobile phone. At this time, the following confirmation interface will pop up on the mobile phone. After clicking the pairing button on the mobile phone, the pairing process will start[[File:media/image635.png| ~~style="text-align~~308x232px]]</li><li>After the pairing is completed, you can see the paired Bluetooth device as shown in the figure below[[File: ~~left;"~~media/image636.png| 575x170px]]</li><li>At this time, you can use the Bluetooth of your mobile phone to send a picture to the development board. After sending, you can see the following confirmation interface in the Android system of the development board, and then click '''~~HDMI TX1 Display - 4K 120HZ~~Accept'''to start receiving the picture sent by the mobile phone.[[File:media/image637.png| ~~style="text-align: left;"|~~ 575x250px]]</li><li>You can open the '''~~'OK~~Download'''directory in the file manager to view the pictures received by the Android system Bluetooth of the development board[[File:media/image638.png| 575x86px]]</li></ol> == Test method of HDMI In == <ol style="~~text~~list-style-~~align~~type: ~~left~~decimal;"~~| '''OK'''~~><li>The location of the HDMI In interface on the development board is as follows：[[File:media/image265.png|-351x112px]]</li><li>Then use the HDMI to HDMI cable shown in the figure below to connect the HDMI output of other devices to the HDMI In interface of the development board~~| style="text-align~~[[File: ~~left;"~~media/image11.png| ~~'''~~199x129px]]</li><li>Make sure that the HDMI output of the device connected to the HDMI ~~TX1 Display - 8K 60HZ'''~~In interface is normal, and then open the HDMI In test APP[[File:media/image639.png|532x167px]]</li><li>Then you can see the video input of HDMI In, and the audio input of HDMI In will also be output from the HDMI TX interface or headphone interface of the development board. The figure below shows the desktop of the Linux system of the OPi5 development board input through HDMI In.[[File:media/image640.png| ~~style~~533x301px]]</li></ol> == How to use 10.9.10.1 inch MIPI screen == '''OKPlease make sure that the Android image used is the image of the following two versions：'''~~| style="text-align: left;"|~~ '''OKOrangePi5Plus_RK3588_Android12_lcd_v1.x.x.img'''|-~~| style="text-align: left;"|~~ '''~~HDMI TX1 Audio~~OrangePi5Plus_RK3588_Android12_spi-nvme_lcd_v1.x.x.img'''| <ol style="~~text~~list-style-~~align~~type: ~~left~~decimal;"~~| '''OK'''~~>~~| style="text~~<li>The screen needs to be assembled first, please refer to the assembly method of the 10.1-~~align~~inch MIPI screen</li><li>The interface position of the LCD on the development board is shown in the figure below：[[File: ~~left;"~~media/image641.png| 317x80px]]'''OKNote that the touch interface below is not for the LCD MIPI screen. It is currently a spare interface and cannot be used.'''[[File:media/image425.png|334x70px]]</li><li>Connect the assembled screen to the LCD interface, connect the Type-C power supply to the board, and power on. After the system starts, you can see the screen display as shown in the figure below~~| style="text-align~~[[File: ~~left;"~~media/image642.png| ~~'''HDMI TX2 Display - 1080p'''~~517x345px]]</li></ol> ~~| style~~== OV13850 and OV13855 MIPI camera test method == Currently the development board supports two MIPI cameras, OV13850 and OV13855, the specific pictures are as follows： | <ol style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"~~| '''OK'''~~><li>OV13850 camera with 13 million MIPI interface[[File:media/image23.png|-268x151px]]</li><li>OV13855 camera with 13 million MIPI interface~~| style="text-align~~[[File: ~~left;"~~media/image24.png| 253x150px]]The adapter boards and FPC cables used by the OV13850 and OV13855 cameras are the same, but the positions of the two cameras connected to the adapter boards are different. The FPC cable is shown in the figure below. Please note that the FPC cable has a direction. The end marked '''~~HDMI TX2 Display - 4K 120HZ~~TO MB'''~~| style="text-align: left;"|~~ needs to be inserted into the camera interface of the development board, and the end marked '''OKTO CAMERA'''needs to be inserted into the camera adapter board.</li></ol> [[File:media/image436.png| 475x99px]] There are a total of 3 camera interfaces on the camera adapter board, and only one can be used at a time, as shown in the figure below, of which: <ol style="~~text~~list-~~align~~style-type: ~~left~~lower-alpha;"| ><li>'''OKNo.1 port is connected to OV13850 camera'''</li>|-~~| style="text-align: left;"|~~ <li>'''~~HDMI TX2 Display - 8K 60HZ~~No.2 interface is connected to OV13855 camera'''</li>~~| style~~<li>No. 3 interface is not used, just ignore it</li></ol> <div class="~~text-align~~figure"> [[File: ~~left;"~~media/image643.png|333x199px| ~~'''OK'''~~图片3]] </div>The location of the camera interface on the Orange Pi 5 Plus development board is shown in the figure below: ~~| style="text-align~~[[File: ~~left;"~~media/image644.png| ~~'''OK'''~~388x65px]] The method of inserting the camera into the CAM interface of the development board is as follows: [[File:media/image439.png|-285x132px]] After connecting the camera to the development board, we can use the following method to test the camera： | <ol style="~~text~~list-style-~~align~~type: ~~left~~lower-alpha;"><li>Open the camera APP on the desktop[[File:media/image645.png| ~~'''HDMI TX2 Audio'''~~491x279px]]</li><li>Then you can see the preview screen of the camera~~| style~~<div class="~~text~~figure"> [[File:media/image646.png|379x213px|Screenshot_20230317-~~align~~073757]] </div>Press and hold the mouse in the area shown in the red box in the picture below of the camera APP and then drag to the right to call up the switching interface for taking pictures and recording[[File: ~~left;"~~media/image647.png| 391x222px]]The switching interface of taking pictures and recording is as follows, click Video to switch to '''OKvideo'''recording mode~~| style~~<div class="~~text-align~~figure"> [[File: ~~left;"~~media/image648.png| ~~'''OK'''~~386x217px|Screenshot_20230317-074419]] </div>Click the position shown in the figure below to enter the camera setting interface[[File:media/image649.png| ~~style="text-align~~390x221px]]The setting interface of the camera is as follows：<div class="figure"> [[File: ~~left;"~~media/image650.png|429x241px| ~~'''HDMI RX display'''~~Screenshot_20230317-075325]] </div></li></ol> ~~| style~~== 26pin interface GPIO, UART, SPI and PWM test == ~~| style~~=== 40pin GPIO port test ===|-| <ol style="~~text~~list-style-~~align~~type: ~~left~~decimal;"><li>First click on the wiringOP icon to open the wiringOP APP[[File:media/image651.png| 552x183px]]</li><li>The main interface of wiringOP APP is displayed as shown in the figure below, and then click the '''~~HDMI RX Audio~~GPIO_TEST'''button to open the GPIO test interface~~| style="text-align~~[[File: ~~left;"~~media/image652.png| 553x131px]]</li><li>The GPIO test interface is shown in the figure below. The two rows of '''OKCheckBox'''~~| style="text~~buttons on the left are in one-to-~~align: left;"|~~ one correspondence with the 26pin pins. When the '''OKCheckBox'''|-~~| style="text-align: left;"|~~ button is checked, the corresponding GPIO pin will be set to '''~~USB2.0X2~~OUT'''~~| style="text-align: left~~mode, and the pin level will be set to high level; when the checkbox is unchecked, the GPIO pin level will be set to low level;"| When the '''OKGPIO READALL'''~~| style="text-align~~button is pressed, information such as the wPi number, GPIO mode, and pin level can be obtained.[[File: ~~left;"~~media/image653.png| 553x288px]]</li><li>Then click the '''OKGPIO READALL'''button, the output information is as shown in the figure below：[[File:media/image654.png|-553x310px]]</li>~~| style="text-align: left;"|~~ <li>There are a total of 28 GPIO ports in the 40pins of the development board that can be used. The following uses pin 11—the corresponding GPIO is GPIO1_A4—the corresponding wPi serial number is 5—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 11. When the button is selected, pin 11 will be set to high level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is '''23.~~5G PCIe network port X2~~3v''', it means setting high level success~~| style="text-align~~[[File: ~~left;"~~media/image655.png| 204x392px]]</li><li>Then click the '''OKGPIO READALL'''~~| style="text-align: left;"| '~~button, you can see that the current pin 7 mode is '''OKOUT''', and the pin level is high[[File:media/image656.png|-552x259px]]</li>~~| style="text-align: left;"|~~ <li>Click the '''~~2.5G PCIe network port light~~CheckBox'''~~| style="text-align: left;"|~~ button in the figure below again to cancel the check status. Pin 11 will be set to low level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is '''OK0v''', it means that the low level is set successfully.~~| style="text-align~~[[File: ~~left;"~~media/image657.png| 205x394px]]</li><li>Then click the '''OKGPIO READALL'''button, you can see that the current mode of pin 11 is OUT, and the pin level is low[[File:media/image658.png|-552x258px]]</li></ol> ~~| style~~=== 40pin UART test === | <ol style="~~text~~list-~~align~~style-type: ~~left~~decimal;"| ><li>'''UART3'OK''and '~~| style="text-align: left;"|~~ ''~~'OK~~UART8'''are enabled by default in Android. The position of the 40pin is shown in the figure below, and the corresponding device nodes are /dev/ttyS3 and /dev/ttyS8 respectively[[File:media/image659.png|-508x139px]]</li><li>First click on the wiringOP icon to open the wiringOP APP~~| style="text-align~~[[File: ~~left;"~~media/image651.png| 552x183px]]</li><li>The main interface of wiringOP APP is displayed as shown in the figure below, and then click the '''~~RTC~~UART_TEST'''button to open the UART test interface[[File:media/image660.png|552x123px]]</li><li>The serial port test interface of the APP is shown in the figure below</li></ol> [[File:media/image661.png| 552x310px]] <ol start="5" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"| ><li>Take the test of '''UART3'''as an example below, select the ''OK'/dev/ttyS3''~~| style="text-align: left;"|~~ ' node in the selection box, enter the baud rate you want to set in the edit box, and then click the '''OPEN'OK''button to open the '|-~~| style="text-align: left;"|~~ ''/dev/ttyS3'~~FAN interface~~''node. After opening successfully, click the OPEN button becomes unselectable, and the '~~| style="text-align: left;"|~~ ''CLOSE''' button and '''OKSEND'''button become selectable</li></ol> [[File:media/image662.png| 552x154px]] <ol start="6" style="~~text~~list-~~align~~style-type: ~~left~~decimal;"><li>Then use Dupont wire to short the RXD and TXD pins of uart3[[File:media/image663.png| 455x121px]]</li><li>Then you can enter a character in the send edit box below, and click the '''OKSEND'''button to start sending</li></ol> [[File:media/image664.png|-553x155px]] | <ol start="8" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"><li>If everything is normal, the received string will be displayed in the receiving box</li></ol> [[File:media/image665.png| ~~'''eMMC extension interface'''~~553x290px]] ~~| style~~=== 26pin SPI test === | <ol style="~~text~~list-style-~~align~~type: ~~left~~decimal;"><li>From the table below, the available SPIs for Orange Pi 5 Plus are SPI0 and SPI4[[File:media/image304.png| ~~'''OK'''~~575x137px]]</li><li>The Android system opens the SPI0 configuration by default. Here is a demonstration to test the SPI0 interface through the w25q64 module. First, connect the w25q64 device to the SPI0 interface.[[File:media/image666.png|-195x164px]]</li><li>Then click the wiringOP icon to open the wiringOP APP~~| style="text-align~~[[File: ~~left;"~~media/image651.png| 552x183px]]</li><li>The main interface of wiringOP APP is displayed as shown in the figure below, click the '''~~AP6275P-WIFI~~SPI_TEST'''button to open the SPI test interface[[File:media/image667.png| ~~style="text-align: left;"|~~ 552x123px]]</li><li>Then click the '''OKOPEN'''button to initialize the SPI</li></ol> [[File:media/image668.png| 552x155px]] <ol start="6" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"| ><li>Then fill in the bytes that need to be sent, such as reading the ID information of w25q64, fill in the address 0x9f in data[0], and then click the '''OKTRANSFER'''button[[File:media/image669.png|-575x252px]]</li><li>Finally, the APP will display the read ID information</li></ol> [[File:media/image670.png| 552x206px]] <ol start="8" style="~~text~~list-style-~~align~~type: ~~left~~decimal;"><li>The MANUFACTURER ID of the w25q64 module is EFh, and the Device ID is 4017h, corresponding to the value read above (h stands for hexadecimal)[[File:media/image671.png| ~~'''AP6275P-BT'''~~374x126px]]</li></ol> ~~| style~~=== 26pin PWM test === | <ol style="~~text~~list-style-~~align~~type: ~~left~~decimal;"| ><li>Android enables '''PWM10'''OKand '''|-~~| style="text-align: left;"| '''AX200-WIFI~~PWM14'''by default, and the corresponding pins are located at 40pin as shown in the figure below：[[File:media/image672.png| ~~style="text-align~~431x130px]]</li><li>First click on the wiringOP icon to open the wiringOP APP[[File: ~~left;"~~media/image651.png| 552x183px]]</li><li>Then click the '''NOPWM_TEST'''button on the main interface of wiringOP to enter the PWM test interface~~| style="text-align~~[[File: ~~left;"~~media/image673.png| 553x125px]]</li><li>The base address corresponding to PWM10 is '''febe0020'NO'', and the base address corresponding to PWM14 is '|-~~| style="text-align: left;"|~~ ''febf0020'~~AX200-BT~~''. Here, '~~| style="text~~''fd8b0020.pwm''' is displayed on the right of pwmchip0. At this time, you need to click the drop-~~align: left;"|~~ down option to select other pwmchips until '''NOfebe0020'''~~| style="text-align: left;"|~~ or '''NOfebf0020'''is displayed on the right.[[File:media/image674.png|553x111px]]</li><li>When the drop-~~| style="text-align: left;"|~~ down option menu selects '''pwmchip2''', the corresponding base address of '''~~AX210-WIFI~~PWM10'''~~| style="text-align: left;"|~~ is '''NOfebe0020'''on the right[[File:media/image675.png| ~~style="text~~553x102px]]</li><li>When the drop-~~align: left;"|~~ down option menu selects '''pwmchip4''', the corresponding base address of '''NOPWM14'''|-~~| style="text-align: left;"|~~ is '''~~AX210-BT~~febe0020'''on the right[[File:media/image676.png| ~~style="text-align: left;"|~~ 553x102px]]</li><li>Take the test of PWM10 as an example, we need to select '''NOpwmchip2'''~~| style="text-align~~[[File: ~~left;"~~media/image675.png| 553x102px]]</li><li>Then confirm the PWM period, the default configuration is '''50000ns''NO', converted to PWM frequency is ''|-~~| style="text-align: left;"|~~ '20KHz''', you can modify it yourself, click the open button to export '''~~RTL8852BE-WIFI~~PWM10'''[[File:media/image677.png| 552x101px]]</li><li>Then drag the drag bar below to change the PWM duty cycle, and then check Enable to output the PWM waveform</li></ol> [[File:media/image678.png|575x116px]] <ol start="10" style="~~text~~list-~~align~~style-type: ~~left~~decimal;"~~| '''OK'''~~><li>Then use an oscilloscope to measure the 31st pin in the 40pin of the development board, and you can see the following waveform</li></ol> ~~| style="text-align~~[[File: ~~left;"~~media/image679.png| ~~'''OK'''~~460x276px]]|-~~| style~~== How to use ADB == ~~| style~~~~| style~~=~~"text-align: left;"| '''OK'''~~|-~~| style~~=~~"text-align: left;"| '''Recovery button'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Type-C interface USB3.0 function'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Type-C interface ADB function'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Type-C interface DP display function'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Type-C interface DP audio playback'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''USB3.0 Hub'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''switch button'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''infrared function'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''led light'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Onboard MIC'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''headphone playback'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''headphone recording'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''SPK Horn'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''40PIN GPIO'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''40PIN I2C'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''40PIN SPI'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''40PIN UART'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''40PIN PWM'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''TF card start'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''SPI Flash+NVME solid state boot'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''OV13850 camera'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''OV13855 camera'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''GPU'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''VPU'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''NPU'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''MIPI LCD display'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''MIPI LCD Touch'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''MIPI LCD backlight'''| style="text-align: left;"| '''OK'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI CEC function'''| style~~=~~"text-align: left;"| '''NO'''| style~~Use the data cable to connect to adb debugging ===~~"text-align: left;"| '''OK'''~~|}

<~~span id~~ol style="~~how~~list-tostyle-~~use~~type: decimal;"><li>First prepare a good quality Type-C data cable[[File:media/image21.png|122x97px]]</li><li>Then connect the development board and Ubuntu PC through theType-~~usb~~C data cable. The position of the Type-~~wireless-network-card">~~C interface of the development board is shown in the figure below:</~~span~~p><div class=~~= How to use the USB wireless network card ==~~"figure">

~~# Currently, the USB wireless network card models compatible with the Android image are as follows：~~[[File:media/image52.jpeg|319x90px|C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题-2.jpg未标题-2]]

~~{| class="wikitable"~~</div></li>|-~~| style="text-align: left;"| '''Chip model'''| style="text-align: left;"| '''Function'''~~<li>Then install the adb tool on the Ubuntu PC~~| style="text-align~~test@test: ~~left;"|~~ ~$ '''~~VID&PID~~sudo apt update'''~~| style="text-align~~test@test: ~~left;"| '''Adaptation~~~$ '''|sudo apt -~~| style="text-align: left;"| '''RTL8723BU'''| style="text-align: left;"| '''2.4G WIFI+BT4.0~~y install adb'''</li>~~| style="text-align: left;"| '''0bda:b720'''~~<li>You can view the identified ADB devices through the following command~~| style="text-align~~test@test: ~~left;"|~~ ~$ '''~~Support WIFI and Bluetooth function, does not support hotspot~~adb devices'''|-List of devices attached~~| style="text-align: left;"| '''RTL8811CU'''~~S63QCF54CJ device~~| style="text-align~~test@test: ~~left;"|~~ ~$ '''~~2.4G +5G WIFI~~lsusb'''~~| style="text-align~~Bus 003 Device 006: ~~left;"| '''0bda~~ID 2207:~~c811'''| style="text-align: left;"| '''Support WIFI function and open hotspot'''~~0006</li>|}<li>Then you can log in to the android system through the adb shell on the Ubuntu PC</li></ol>

~~<ol start="2" style="list-style-type~~test@test: ~~decimal;"><li>The pictures of the above two USB wireless network cards are as follows：<ol style="list-style-type: lower-alpha;"><li>The picture of the RTL8723BU USB wireless network card module is > as follows：<div class="figure">~~~$ '''adb shell'''

~~[[File~~console:./~~images/media/image705.png|175x103px|C89CEA9A-B322-42d2-B476-2392A50E6FC4]]~~$

<~~/div></li><li>The picture of the RTL8811CU USB wireless network card module is &gt~~ol start="6" style="list-style-type: decimal; ~~as follows：[[File:./images/media/image706.png|124x107px]]</li></ol></li><li>The test methods of the above two types of USB wireless network cards are the same. First, the USB network card needs to be inserted into the USB interface of the development board.</li~~"><li>~~Then, for~~ Execute the ~~connection and test method of WIFI, please refer~~ following command to remount the ~~section of WIFI connection test method</li><li>For the Bluetooth test, please refer to the content of the Bluetooth test method~~Android system</li></ol>

~~== M.2 How to use E-Key PCIe WIFI6+Bluetooth module ==~~test@test:~$ '''adb root'''

~~# The PCIe wireless network card models currently compatible with Android 12 are as follows：~~test@test:~$ '''adb remount'''

~~{| class~~<ol start="~~wikitable~~7"|style="list-~~| '''serial number'''| '''model'''| '''Physical picture'''~~|style-type: decimal;">~~| '''1'''| '''RTL8852BE'''~~<li>Then you can transfer files to the Android system</li></ol>

test@test:~$ '''~~(PCIE+USB interface)~~adb push example.txt /system/'''

~~| [[File:.~~</~~i%20mages/media/image7%2007.png]]~~span>|}=== Use network connection adb debugging ===

~~<ol start="2" style="list-style-type: decimal;"><li>First insert~~ '''Using the ~~PCIe wireless~~ network ~~card into the M.2 E-KEY interface of the development board and fix it[[File:./images/media/image708.png|263x178px]]</li><li>Then connect the power supply~~ adb does not require a data cable of the ~~Type~~Typc-C interface to connect the computer and the development board, ~~and power on</li><li>After~~ but to communicate through the ~~system starts~~network, so first of all, please ~~refer to~~ ensure that the ~~section~~ wired or wireless network of ~~WIFI connection test method for WIFI connection and test method</li><li>For~~ the ~~Bluetooth test~~development board has been connected, ~~please refer to~~ and then obtain the ~~content~~ IP address of the ~~Bluetooth test method</li></ol>~~development board, and then to use.'''

<~~span id~~ol style="~~wifi~~list-~~connection~~style-~~test-method~~type: decimal;"><li>Make sure that the '''service.adb.tcp.port''' of the Android system is set to port number 5555console:/ # '''getprop | grep "adb.tcp"'''</~~span~~p>~~== WIFI connection test method ==~~[service.adb.tcp.port]: ['''5555''']</li><li>If '''service.adb.tcp.port''' is not set, you can use the following command to set the port number of network adb</li></ol>

console:/ # '''~~First of all, please note that there is no WIFI module on the Orange Pi 5 Plus development board, and an external PCIe network card or USB network card is required to use the WIFI function~~setprop service.adb.tcp.port 5555'''

console:/ # '''~~For instructions on using the external PCIe network card, please refer to the section on how to use the M.2 E-Key PCIe WIFI6+Bluetooth module.~~stop adbd'''

~~'''For instructions on using the external USB network card, please refer to the section on how to use the USB wireless network card.'''~~ console:/ # ~~First click to enter the '''Setting~~''' ~~[[File:./images/media/image709.png|553x182px]]~~ ~~<ol~~ start~~="2" style="list-style-type: decimal;"><li>Then select '''Network & internet~~adbd'''~~</li></ol>~~ ~~[[File:./images/media/image710.png|553x154px]]~~

<li>Install adb tool on Ubuntu PCtest@test:~$ '''sudo apt update'''test@test:~$ '''sudo apt install -y adb'''</li><li>Then ~~select~~ connect network adb on Ubuntu PCtest@test:~$ '''~~Internet~~adb connect 192.168.1.xxx''''''(The IP address needs to be changed to the IP address of the development board)'''* daemon not running; starting now at tcp:5037* daemon started successfullyconnected to 192.168.1.xxx:5555test@test:~$ '''adb devices'''List of devices attached192.168.1.xxx:5555 device</li><li>Then you can log in to the android system through the adb shell on the Ubuntu PC</li></ol>

~~[[File~~test@test:~~./images/media/image711.png|553x103px]]~~~$ '''adb shell'''

~~<ol start="4" style="list-style-type~~console: ~~decimal;"><li>Then turn on the '''Wi-Fi''' switch<~~/~~li></ol>~~#

~~[[File:./images/media~~</~~image712~~span>== 2.~~png|553x65px]]~~4G USB remote control tested by Android Box ==

<ol ~~start="5"~~ style="list-style-type: decimal;"><li>~~After turning on '''Wi-Fi''', if everything~~ A 2.4G USB remote control that has been tested so far is ~~normal, you can scan to nearby Wi-Fi hotspots~~shown in the figure below<~~p>[[File~~ol style="list-style-type:~~./images/media/image713.png|549x172px]]</li~~lower-alpha;"><li>~~Then select the Wi-Fi you want to connect to, and the password input interface shown in the figure below will pop up~~Contains a remote control[[File:~~./images/~~media/~~image714~~image680.png|~~553x237px~~199x149px]]</li><li>~~Then use the keyboard to enter the password corresponding to Wi-Fi, and then use the mouse to click the Enter button in the virtual keyboard to start connecting to Wi-Fi~~A USB wireless receiver[[File:~~./images/~~media/~~image715~~image681.png|~~553x232px~~110x119px]]</li></ol></li><li>The ~~display~~ Android Box system does not require any configuration, it can be used after ~~successful Wi-Fi connection is shown~~ plugging it in ~~the figure below：[[File:./images/media/image716.png|553x93px]]~~</li></ol>

== How to use ~~Wi-Fi hotspot~~ the infrared remote control of the Android Box system ==

<li>~~First~~The development board comes with an infrared receiver, ~~please make sure that the Ethernet port~~ and its location is ~~connected to~~ shown in the ~~network cable and can access the Internet normally</li><li>Then select '''Settings'''~~figure below：[[File:~~./images/~~media/~~image709~~image682.png|~~553x182px~~435x124px]]</li><li>~~Then select '''Network &''' '''internet'''[[File:./images/media/image710.png|553x154px]]</li><li>Then select '''Hotspot''' '''& tethering'''[[File:./images/media/image717.png|575x195px]]</li><li>Then select '''Wi-Fi hotspot'''[[File:./images/media/image718.png|575x96px]]</li><li>Then turn on the '''Wi-Fi hotspot'''~~Before testing infrared reception, ~~you can also see the name and password of the generated hotspot in the figure below, remember them, and use them when connecting to the hotspot '''(if you~~ we need to ~~modify the name and password of the hotspot, you need to turn off the Wi-Fi first -Fi hotspot before modification)'''~~prepare an infrared remote control<~~p>[[File:./images/media/image719.png|575x187px]]</li>~~<li>At this point, you can take out your mobile phone. If everything is normal, you can find the WIFI hotspot with the same name ('''here AndroidAP_6953''') displayed under the '''Hotspot name''' in the above picture in the WI-FI list searched by the mobile phone. Then you can click '''AndroidAP_6953''' to connect to the hotspot, and the password can be seen under the '''Hotspot password''' in the above picture</li></oldiv class="figure">

[[File:~~./images/~~media/~~image720~~image683.png|~~342x260px~~141x127px|6FBFE2FA-31A4-4a26-AC63-9A3E4E359FFF]]

<~~ol start="8" style="list-style-type: decimal;"~~/div><lip>~~After~~ '''Note: The Android system provided by Orange Pi only supports the ~~connection is successful~~remote control provided by Orange Pi by default, ~~it will be displayed as shown in~~ and the ~~figure below (the interface~~ remote control of ~~different mobile phones will~~ TV or air conditioner cannot be ~~different, the specific interface is subject~~ used.'''</li><li>The Android Box system has been adapted to ~~the display of your mobile phone). At~~ this ~~point, you can open a webpage on your mobile phone to see if you can access the Internet. If you can open the webpage normally~~remote control, and it ~~means that the '''WI-FI Hotspot''' of the development board~~ can be used ~~normally~~directly without other settings.</li></ol>

~~[[File:.~~</~~images/media/image721.png|347x175px]]~~span>== How to use HDMI CEC function in Android Box system ==

~~== Bluetooth test method ==~~'''HDMI CEC allows users to control all connected devices through HDMI with only one remote control. Based on this function, we can control the development board with the remote control of the TV.'''

'''~~Please note that there is no Bluetooth module on the Orange Pi 5 Plus development board~~Before testing this function, ~~and an external PCIe network card with Bluetooth or a USB network card with Bluetooth is required to use the Bluetooth function~~please make sure your TV supports HDMI CEC.'''

~~'''For instructions~~ <ol style="list-style-type: decimal;"><li>First connect the development board to the TV through the HDMI cable, then power on and start</li><li>Then turn on ~~using~~ the ~~external PCIe network card, please refer~~ HDMI CEC function in the TV settings. Different TVs may have different ways to turn it on. Here we take Xiaomi TV as an example. Press the ~~section~~ menu button on ~~how to use~~ the ~~M.2 E-Key PCIe WIFI6+Bluetooth module~~remote control, then select CEC remote control and press the confirmation button[[File:media/image684.png|575x323px]]</li><li>Then select '''"On"'''to open the HDMI CEC remote control[[File:media/image685.png|576x257px]]</li><li>At this point, you can control the Android Box system of the development board through the remote control of the TV</li></ol>

~~'''For instructions on using the external USB network card, please refer~~ = How to ~~use the USB wireless network card.'''~~compile Android 12 source code =

~~<ol style="list-style-type: decimal;"><li>First click to enter the '''Setting'''[[File:./images/media/image709.png|553x182px]]</li><li>Then select '''Connected devices'''[[File:./images/media/image722.png|575x146px]]</li><li>Then click '''Pair new device''' to turn on Bluetooth and start scanning the surrounding Bluetooth devices[[File:./images/media/image723.png|575x144px]]</li><li>The searched Bluetooth devices will be displayed under '''Available devices'''[[File:./images/media/image724.png|575x200px]]</li><li>Then click the Bluetooth device you want to connect to start pairing. When the following interface pops up, please use the mouse to select the '''Pair''' option[[File:./images/media/image725.png|575x155px]]</li>~~<li>The test here is the configuration process of the development board and the Bluetooth of the Android mobile phone. At this time, the following confirmation interface will pop up on the mobile phone. After clicking the pairing button on the mobile phone, the pairing process will start~~[[File:./images/media/image726.png|308x232px]]</li><li>After the pairing is completed, you can see the paired Bluetooth device as shown in the figure below[[File:./images/media/image727.png|575x170px]]</li>~~<li>At this time, you can use the Bluetooth of your mobile phone to send a picture to the development board. After sending, you can see the following confirmation interface in the Android system of the development board, and then click '''Accept''' to start receiving the picture sent by the mobile phone.~~[[File:./images/media/image728.png|575x250px]]</li><li>You can open the '''Download''' directory in the file manager to view the pictures received by the Android system Bluetooth of the development board[[File:./images/media/image729.png|575x86px]]</li></ol>~~ == ~~Test method of HDMI In~~ Download Android 12 source code ==

<li>~~The location of~~ First download the ~~HDMI In interface on the development board is as follows：~~Android 12 source code sub-volume compressed package from Google network disk[[File:~~./images/~~media/~~image348~~image686.png|~~351x112px~~575x138px]]</li><li>~~Then use~~ After downloading the ~~HDMI to HDMI cable shown in~~ sub-volume compression package of the ~~figure below to connect~~ Android 12 source code, please check whether the ~~HDMI output of other devices to the HDMI In interface of~~ MD5 checksum is correct, if not, please download the ~~development board~~source code again~~[[File~~test@test:~$ '''md5sum -c Android_12.~~/images/media/image12~~tar.gz.~~png|199x129px]]~~md5sum''''''Android_12.tar.gz00: confirm'''</lip><lip>'''Android_12.tar.gz01: confirm'''~~Make sure that the HDMI output of the device connected to the HDMI In interface is normal, and then open the HDMI In test APP~~'''Android_12.tar.gz02: confirm'''~~[[File:~~'''Android_12.~~/images/media/image730~~tar.~~png|532x167px]]~~gz03: confirm''''''Android_12.tar.gz04: confirm'''</lip><lip>'''Android_12.tar.gz05: confirm'''~~Then you can see the video input of HDMI In, and the audio input of HDMI In will also be output from the HDMI TX interface or headphone interface of the development board~~'''Android_12. ~~The figure below shows the desktop of the Linux system of the OPi5 development board input through HDMI In~~tar.gz06: confirm'''~~[[File~~'''Android_12.tar.gz07:.confirm'''</~~images~~p></~~media/image731.png|533x301px]]~~li><li>Then you need to merge multiple compressed files into one, and then decompress</li></ol>

~~ Android_12.~~1-inch-mipi-screen">== How to use 10~~tar.~~9.10.1 inch MIPI screen ==gz'''

test@test:~$ '''~~Please make sure that the Android image used is the image of the following two versions：~~tar -xvf Android_12.tar.gz'''

~~'''OrangePi5Plus_RK3588_Android12_lcd_v1.x.x.img'''~~~~'''OrangePi5Plus_RK3588_Android12_spi-nvme_lcd_v1.x.x.img'''~~== Compile the source code of Android 12 ==

<li>~~The screen needs to be assembled first, please refer~~ First install the software packages required to compile the ~~assembly method of the 10.1-inch MIPI screen~~Android12 source codetest@test:~$ '''sudo apt-get update'''</lip><lip>test@test:~$ '''sudo apt-get install -y git gnupg flex bison gperf build-essential \'''~~The interface position of the LCD on the development board is shown in the figure below：~~'''zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 \'''~~[[File:./images/media/image732.png|317x80px]]~~'''lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z1-dev ccache \''''''~~Note that the touch interface below is not for the LCD MIPI screen. It is currently a spare interface and cannot be used.~~libgl1-mesa-dev libxml2-utils xsltproc unzip'''~~[[File~~test@test:~~./images/media/image512.png|334x70px]]~~~$ '''sudo apt-get install -y u-boot-tools'''</li><li>~~Connect the assembled screen to the LCD interface, connect the Type-C power supply to~~ There is a build.sh compilation script in the ~~board~~source code, and ~~power on. After~~ the ~~system starts, you can see the screen display~~ compilation parameters are as ~~shown in the figure below~~follows~~[[File~~a.-'''U''':.compile uboot</~~images/media/image733~~p>b.~~png|517x345px]]~~-'''K''': compile kernel<~~/li~~p>c.-'''A''': compile android</olp> <~~span id="ov13850~~p>d.-'''u''': package and generate update.img andupdate_spi_nvme.imge.-~~ov13855~~'''o''': Compile the OTA packagef.-~~mipi-camera-test-method"~~'''d''': specify kernel dts</~~span~~li>~~== OV13850 and OV13855 MIPI camera test method ==~~ ~~Currently the development board supports two MIPI cameras~~<li>Compile uboot, kernel, ~~OV13850~~ android and ~~OV13855, the specific pictures are as follows：~~package them into update.img

<li>~~OV13850 camera with 13 million MIPI interface~~The command to compile and support HDMI 8K display image (LCD > off by default) is as follows：test@test:~$ '''cd Android_12'''~~[[File~~test@test:~/ Android_12$ '''source build/envsetup.sh'''test@test:~/~~images~~Android_12$ '''lunch rk3588_s-userdebug'''test@test:~/~~media~~Android_12$ '''./~~image24~~build.~~png|268x151px]]~~sh -AUKu'''</li><li>~~OV13855 camera with 13 million MIPI interface~~The command to compile and support LCD display image is as > follows：test@test:~$ '''cd Android_12'''test@test:~/ Android_12$ '''export DUAL_LCD=true'''~~[[File~~test@test:~/ Android_12$ '''source build/envsetup.sh'''test@test:~/ Android_12$ '''lunch rk3588_s-userdebug'''</~~images~~p>test@test:~/~~media~~Android_12$ '''./~~image25~~build.~~png|253x150px]]~~sh -AUKu'''</li><li>The ~~adapter boards and FPC cables used by~~ command to compile the image of the ~~OV13850 and OV13855 cameras are~~ Box version is as > follows：test@test:~$ '''cd Android_12'''test@test:~/ Android_12$ '''export BOARD=orangepi5plus'''test@test:~/ Android_12$ '''source build/envsetup.sh'''test@test:~/ Android_12$ '''lunch rk3588_box-userdebug'''test@test:~/ Android_12$ '''./build.sh -AUKu'''</li></ol></li><li>After the ~~same~~compilation is complete, ~~but~~ the ~~positions of the two cameras connected to the adapter boards are different~~following information will be printed********rkImageMaker ver 2.1********Generating new image, please wait...Writing head info...Writing boot file...Writing firmware...Generating MD5 data...MD5 data generated successfully!New image generated successfully!Making update.img OK. Make update image ok!</li><li>The ~~FPC cable is shown~~ final image file will be placed in the ~~figure below~~'''rockdev/Image-rk3588_s''' directory. Among them, '''update. ~~Please note~~ img''' is the boot image that supports TF card and eMMC, and '''update_spi_nvme.img''' is the ~~FPC cable has a direction~~boot image of NVME SSD[mailto:test@test:~OrangePi_4/rk3399-android-8.1$ test@test:~/Android_12$] '''cd rockdev/Image-rk3588s_s'''[mailto:test@test:~OrangePi_4/rk3399-android-8. ~~The end marked~~ 1$ test@test:~/Android_12/rockdev/Image-rk3588s_s $] '''~~TO MB~~ls update*''' ~~needs to be inserted into~~ update.img update_spi_nvme.img</li><li>If you compile the ~~camera interface~~ image of the ~~development board~~Box version, ~~and~~ the ~~end marked~~ final generated image file will be placed in the '''rockdev/Image-rk3588_box''' directory[mailto:test@test:~OrangePi_4/rk3399-android-8.1$ test@test:~/Android_12$] '''cd rockdev/Image-rk3588_box'''[mailto:test@test:~OrangePi_4/rk3399-android-8.1$ test@test:~/Android_12/rockdev/Image-rk3588_box$] '''~~TO CAMERA~~ls update*''' ~~needs to be inserted into the camera adapter board~~update.img update_spi_nvme.img</li></ol>

~~[[File:.~~</~~images/media/image525.png|475x99px]]~~span>= Instructions for using the Orange Pi OS Droid system =

~~There are a total~~ == Function adaptation of ~~which:~~OPi OS Droid system ==

~~<ol style~~{| class="~~list~~wikitable"|-| style="text-~~type~~align: ~~lower-alpha~~left;">~~<li>~~| '''~~No.1 port is connected to OV13850 camera~~Function'''~~</li><li>~~| style="text-align: left;"| '''~~No.2 interface is connected to OV13855 camera~~OPi OS Droid function adaptation'''~~</li><li>No. 3 interface is not used, just ignore it</li></ol>~~|- ~~<div class~~| style="~~figure~~text-align: left;">| '''HDMI TX1 display''' ~~[[File~~| style="text-align:~~./images/media/image734.png~~left;"|~~333x199px~~'''OK'''|~~图片3]]~~- ~~</div>The location of the camera interface on the Orange Pi 5 Plus development board is shown in the figure below~~| style="text-align:left;"| '''HDMI TX1 Audio''' ~~[[File~~| style="text-align:~~./images/media/image735.png~~left;"|~~388x65px]]~~'''OK'''|-~~The method of inserting the camera into the CAM interface of the development board is as follows~~| style="text-align:left;"| '''HDMI TX2 display''' ~~[[File~~| style="text-align:~~./images/media/image528.png~~left;"|~~285x132px]]~~'''OK'''|-~~After connecting the camera to the development board, we can use the following method to test the camera：~~ ~~<ol~~ | style="~~list~~text-align: left;"| '''HDMI TX2 Audio'''| style="text-~~type~~align: ~~lower-alpha~~left;">| '''OK'''~~<li>Open the camera APP on the desktop~~|-~~[[File~~| style="text-align:~~./images/media/image736.png~~left;"|~~491x279px]]</li>~~'''HDMI RX display'''~~<li>Then you can see the preview screen of the camera<div class~~| style="~~figure~~text-align: left;">| '''OK'''|-~~[[File~~| style="text-align:~~./images/media/image737.png~~left;"|~~379x213px~~'''HDMI RX Audio'''|~~Screenshot_20230317~~style="text-~~073757]]~~align: left;"| '''OK'''|-~~</div>Press and hold the mouse in the area shown in the red box in the picture below of the camera APP and then drag to the right to call up the switching interface for taking pictures and recording[[File~~| style="text-align:~~./images/media/image738.png~~left;"|~~391x222px]]The switching interface of taking pictures and recording is as follows, click Video to switch to~~ '''~~video~~USB2.0X2''' ~~recording mode<div class~~| style="~~figure~~text-align: left;">| '''OK'''|-~~[[File~~| style="text-align:left;"| '''2.~~/images/media/image739.png~~5G PCIe network port X2'''|~~386x217px|Screenshot_20230317~~style="text-~~074419]]~~ ~~</div>Click the position shown in the figure below to enter the camera setting interface[[File~~align:~~./images/media/image740.png~~left;"|~~390x221px]]~~'''OK'''~~The setting interface of the camera is as follows：~~|-~~<div class~~| style="~~figure~~text-align: left;">| '''2.5G PCIe network port light''' ~~[[File~~| style="text-align:~~./images/media/image741.png~~left;"|~~429x241px~~'''OK'''|~~Screenshot_20230317~~-~~075325]]~~ ~~</div></li></ol>~~ ~~~~| '''Debug serial port'''| style=~~= 26pin interface GPIO, UART, SPI and PWM test ==~~"text-align: left;"| '''OK'''|-~~~~| '''RTC'''| style=~~== 40pin GPIO port test ===~~"text-align: left;"| '''OK'''|-~~<ol~~ | style="~~list~~text-align: left;"| '''FAN interface'''| style="text-~~type~~align: ~~decimal~~left;">| '''OK'''~~<li>First click on the wiringOP icon to open the wiringOP APP~~|-~~[[File~~| style="text-align:~~./images/media/image742.png~~left;"|~~552x183px]]</li><li>The main interface of wiringOP APP is displayed as shown in the figure below, and then click the~~ '''~~GPIO_TEST~~eMMC extension interface''' ~~button to open the GPIO test interface[[File~~| style="text-align:~~./images/media/image743.png~~left;"|~~553x131px]]</li><li>The GPIO test interface is shown in the figure below. The two rows of~~ '''~~CheckBox~~OK''' ~~buttons on the left are in one~~|-to| style="text-~~one correspondence with the 26pin pins. When the~~ align: left;"| '''~~CheckBox~~AP6275P-WIFI''' ~~button is checked, the corresponding GPIO pin will be set to~~ | style="text-align: left;"| '''~~OUT~~OK''' ~~mode, and the pin level will be set to high level~~|-| style="text-align: left; ~~when the checkbox is unchecked, the GPIO pin level will be set to low level; When the~~ "| '''~~GPIO READALL~~AP6275P-BT''' ~~button is pressed, information such as the wPi number, GPIO mode, and pin level can be obtained.[[File~~| style="text-align:~~./images/media/image744.png~~left;"|~~553x288px]]</li><li>Then click the~~ '''~~GPIO READALL~~OK''' ~~button, the output information is as shown in the figure below：[[File~~|-| style="text-align:~~./images/media/image745.png~~left;"|~~553x310px]]</li>~~<li>There are a total of 28 GPIO ports in the 40pins of the development board that can be used. The following uses pin 11—the corresponding GPIO is GPIO1_A4—the corresponding wPi serial number is 5—as an example to demonstrate how to set the high and low levels of the GPIO port. First click the '''~~CheckBox~~AX200-WIFI''' ~~button corresponding to pin 11. When the button is selected, pin 11 will be set to high level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is~~ | style="text-align: left;"| '''~~3.3v~~NO'''~~, it means setting high level success[[File~~|-| style="text-align:~~./images/media/image746.png~~left;"|~~204x392px]]</li><li>Then click the~~ '''~~GPIO READALL~~AX200-BT''' ~~button, you can see that the current pin 7 mode is~~ | style="text-align: left;"| '''~~OUT~~NO'''~~, and the pin level is high[[File~~|-| style="text-align:~~./images/media/image747.png~~left;"|~~552x259px]]</li><li>Click the~~ '''~~CheckBox~~AX210-WIFI''' ~~button in the figure below again to cancel the check status. Pin 11 will be set to low level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is~~ | style="text-align: left;"| '''0vNO'''~~, it means that the low level is set successfully.[[File~~|-| style="text-align:~~./images/media/image748.png~~left;"|~~205x394px]]</li><li>Then click the~~ '''~~GPIO READALL~~AX210-BT''' ~~button, you can see that the current mode of pin 11 is OUT, and the pin level is low[[File~~| style="text-align:~~./images/media/image749.png~~left;"|~~552x258px]]</li></ol>~~'''NO'''|-~~~~| '''OK'''~~=== 40pin UART test ===~~|- ~~<ol~~ | style="~~list~~text-align: left;"| '''RTL8852BE-BT'''| style="text-~~type~~align: ~~decimal~~left;">~~<li>~~| '''~~UART3~~OK''' ~~and~~ |-| style="text-align: left;"| '''~~UART8~~Recovery button''' ~~are enabled by default in Android. The position of the 40pin is shown in the figure below, and the corresponding device nodes are /dev/ttyS3 and /dev/ttyS8 respectively[[File~~| style="text-align:~~./images/media/image750.png~~left;"|~~508x139px]]</li>~~'''OK'''~~<li>First click on the wiringOP icon to open the wiringOP APP~~|-~~[[File~~| style="text-align:left;"| '''Type-C interface USB3.~~/images/media/image742.png~~0 function'''| style="text-align: left;"|~~552x183px]]</li><li>The main interface of wiringOP APP is displayed as shown in the figure below, and then click the~~ '''~~UART_TEST~~OK''' ~~button to open the UART test interface[[File~~|-| style="text-align:~~./images/media/image751.png~~left;"|~~552x123px]]</li><li>The serial port test~~ '''Type-C interface ~~of the APP is shown in the figure below</li></ol>~~ADB function''' ~~[[File~~| style="text-align:~~./images/media/image752.png~~left;"|~~552x310px]]~~'''OK'''|-~~<ol start~~| style="5text-align: left;" | '''Type-C interface DP display function'''| style="~~list~~text-align: left;"| '''OK'''|-| style="text-~~type~~align: ~~decimal~~left;">~~<li>Take the test of~~ | '''~~UART3~~Type-C interface DP audio playback''' ~~as an example below, select the~~ | style="text-align: left;"| '''~~/dev/ttyS3~~OK''' ~~node in the selection box, enter the baud rate you want to set in the edit box, and then click the~~ |-| style="text-align: left;"| '''~~OPEN~~USB3.0 Hub''' ~~button to open the~~ | style="text-align: left;"| '''~~/dev/ttyS3~~OK''' ~~node. After opening successfully, click the OPEN button becomes unselectable, and the~~ |-| style="text-align: left;"| '''~~CLOSE~~switch button''' ~~button and~~ | style="text-align: left;"| '''~~SEND~~OK''' ~~button become selectable</li></ol>~~|-~~[[File:./images/media/image753.png~~|~~552x154px]]~~ ~~<ol start~~style="6text-align: left;" | '''infrared function'''| style="~~list~~text-~~style-type~~align: ~~decimal~~left;">| '''OK'''~~<li>Then use Dupont wire to short the RXD and TXD pins of uart3~~|-~~[[File~~| style="text-align:~~./images/media/image754.png~~left;"|~~455x121px]]</li><li>Then you can enter a character in the send edit box below, and click the~~ '''~~SEND~~led light''' ~~button to start sending</li></ol>~~ ~~[[File~~| style="text-align:~~./images/media/image755.png~~left;"|~~553x155px]]~~'''OK'''|-~~<ol start~~| style="8text-align: left;" | '''Onboard MIC'''| style="~~list-style~~text-~~type~~align: ~~decimal~~left;">| '''OK'''~~<li>If everything is normal, the received string will be displayed in the receiving box</li></ol>~~|- ~~[[File~~| style="text-align:~~./images/media/image756.png~~left;"|~~553x290px]]~~'''headphone playback''' ~~~~| '''OK'''~~=== 26pin SPI test ===~~|- ~~<ol~~ | style="~~list~~text-align: left;"| '''headphone recording'''| style="text-~~type~~align: ~~decimal~~left;">| '''OK'''~~<li>From the table below, the available SPIs for Orange Pi 5 Plus are SPI0 and SPI4~~|-~~[[File~~| style="text-align:~~./images/media/image389.png~~left;"|~~575x137px]]</li>~~'''SPK Horn'''<li>The Android system opens the SPI0 configuration by default. Here is a demonstration to test the SPI0 interface through the w25q64 module. First, connect the w25q64 device to the SPI0 interface.~~[[File~~| style="text-align:~~./images/media/image757.png~~left;"|~~195x164px]]</li>~~'''OK'''~~<li>Then click the wiringOP icon to open the wiringOP APP~~|-~~[[File~~| style="text-align:~~./images/media/image742.png~~left;"|~~552x183px]]</li><li>The main interface of wiringOP APP is displayed as shown in the figure below, click the~~ '''~~SPI_TEST~~40PIN GPIO''' ~~button to open the SPI test interface[[File~~| style="text-align:~~./images/media/image758.png~~left;"|~~552x123px]]</li><li>Then click the~~ '''~~OPEN~~OK''' ~~button to initialize the SPI</li></ol>~~|-~~[[File:./images/media/image759.png~~|~~552x155px]]~~ ~~<ol start~~style="6text-align: left;" | '''40PIN I2C'''| style="~~list~~text-~~style-type~~align: ~~decimal~~left;">~~<li>Then fill in the bytes that need to be sent, such as reading the ID information of w25q64, fill in the address 0x9f in data[0], and then click the~~ | '''~~TRANSFER~~OK''' ~~button[[File:./images/media/image760.png~~|~~575x252px]]</li><li>Finally, the APP will display the read ID information</li></ol>~~-~~[[File:./images/media/image761.png~~|~~552x206px]]~~ ~~<ol start~~style="8text-align: left;" | '''40PIN SPI'''| style="~~list-style~~text-~~type~~align: ~~decimal~~left;">| '''OK'''~~<li>The MANUFACTURER ID of the w25q64 module is EFh, and the Device ID is 4017h, corresponding to the value read above (h stands for hexadecimal)~~|-~~[[File~~| style="text-align:~~./images/media/image762.png~~left;"|~~374x126px]]</li></ol>~~'''40PIN UART''' ~~~~| '''OK'''~~=== 26pin PWM test ===~~|- ~~<ol~~ | style="~~list-style~~text-~~type~~align: ~~decimal~~left;">~~<li>Android enables~~ | '''~~PWM10~~40PIN PWM''' ~~and~~ | style="text-align: left;"| '''~~PWM14~~OK''' ~~by default, and the corresponding pins are located at 40pin as shown in the figure below：[[File:./images/media/image763.png~~|~~431x130px]]</li>~~-~~<li>First click on the wiringOP icon to open the wiringOP APP[[File~~| style="text-align:~~./images/media/image742.png~~left;"|~~552x183px]]</li><li>Then click the~~ '''~~PWM_TEST~~TF card start''' ~~button on the main interface of wiringOP to enter the PWM test interface[[File~~| style="text-align:~~./images/media/image764.png~~left;"|~~553x125px]]</li><li>The base address corresponding to PWM10 is~~ '''~~febe0020~~OK'''~~, and the base address corresponding to PWM14 is~~ |-| style="text-align: left;"| '''~~febf0020~~SPI Flash+NVME solid state boot'''~~. Here,~~ | style="text-align: left;"| '''~~fd8b0020.pwm~~OK''' ~~is displayed on the right of pwmchip0. At this time, you need to click the drop~~|-| style="text-~~down option to select other pwmchips until~~ align: left;"| '''~~febe0020~~OV13850 camera''' or | style="text-align: left;"| '''~~febf0020~~OK''' ~~is displayed on the right.[[File:./images/media/image765.png~~|~~553x111px]]</li>~~-~~<li>When the drop~~| style="text-~~down option menu selects~~ align: left;"| '''~~pwmchip2~~OV13855 camera'''~~, the corresponding base address of~~ | style="text-align: left;"| '''~~PWM10~~OK''' is |-| style="text-align: left;"| '''~~febe0020~~GPU''' ~~on the right[[File~~| style="text-align:~~./images/media/image766.png~~left;"|~~553x102px]]</li><li>When the drop-down option menu selects~~ '''~~pwmchip4~~OK'''~~, the corresponding base address of~~ |-| style="text-align: left;"| '''~~PWM14~~VPU''' is | style="text-align: left;"| '''~~febe0020~~OK''' ~~on the right[[File~~|-| style="text-align:~~./images/media/image767.png~~left;"|~~553x102px]]</li><li>Take the test of PWM10 as an example, we need to select~~ '''~~pwmchip2~~NPU'''~~[[File~~| style="text-align:~~./images/media/image766.png~~left;"|~~553x102px]]</li><li>Then confirm the PWM period, the default configuration is~~ '''~~50000ns~~OK'''~~, converted to PWM frequency is~~ |-| style="text-align: left;"| '''~~20KHz~~MIPI LCD'''~~, you can modify it yourself, click the open button to export~~ | style="text-align: left;"| '''~~PWM10~~NO'''~~[[File:./images/media/image768.png~~|~~552x101px]]</li><li>Then drag the drag bar below to change the PWM duty cycle, and then check Enable to output the PWM waveform</li></ol>~~-~~[[File:./images/media/image769.png~~|~~575x116px]]~~ ~~<ol start~~style="10text-align: left;" | '''HDMI CEC'''| style="~~list-style~~text-~~type~~align: ~~decimal~~left;">| '''NO'''~~<li>Then use an oscilloscope to measure the 31st pin in the 40pin of the development board, and you can see the following waveform</li></ol>~~|}

~~[[File:.~~</~~images/media/image770.png|460x276px]]~~span>== Test method of HDMI In ==

<~~span id~~ol style="~~how~~list-tostyle-type: decimal;"><li>The location of the HDMI In interface on the development board is as follows：[[File:media/image265.png|282x90px]]</li><li>Then use~~-adb-1"~~the HDMI to HDMI cable shown in the figure below to connect the HDMI output of other devices to the HDMI In interface of the development board[[File:media/image11.png|136x88px]]</li><li>Make sure that the HDMI output of the device connected to the HDMI In interface is normal, and then open the HDMI In test APP[[File:media/image687.png|395x222px]]</~~span~~li>~~== How~~ <li>Then the window shown in the figure below will appear. At this time, the video input of HDMI In cannot be seen. You need to click the position marked in the red box in the figure below to enlarge it to ~~use ADB ==~~full screen[[File:media/image688.png|384x229px]]</li><li>Then you can see the video input of HDMI In, and the audio input of HDMI In will also be output from the HDMI TX interface or headphone interface of the development board. The figure below shows the desktop of the Linux system of the OPi5 development board input through HDMI In.[[File:media/image689.png|400x238px]]</li></ol>

=~~== Use the data cable to connect to adb debugging ==~~Appendix =

<~~ol style~~span id="~~list~~user-~~style~~manual-~~type: decimal;~~update-history">~~<li>First prepare a good quality Type-C data cable~~</pspan>~~[[File:./images/media/image22.png|122x97px]]</li><li>Then connect the development board and Ubuntu PC through the Type-C data cable. The position of the Type-C interface of the development board is shown in the figure below:<div class~~=~~"figure">~~= User Manual Update History ==

~~[[File:./images/media/image63.jpeg~~{|~~319x90px~~class="wikitable"|~~C:\Users\orangepi\Desktop\用户手册插图\Pi5 Plus\未标题~~-~~2.jpg未标题-2]]~~| * *vers ion**

~~</div></li><li>Then install the adb tool on the Ubuntu PCtest@test:~$ '''sudo apt update'''test@test:~$ '''sudo apt''' '''-y''' '''install adb'''</li><li>You can view the identified ADB devices through the following commandtest@test:~$ '''adb devices'''List of devices attachedS63QCF54CJ devicetest@test:~$ '''lsusb'''Bus 003 Device 006: ID 2207:0006</li><li>Then you can log in to the android system through the adb shell on the Ubuntu PC</li></ol>~~| * *Date**

~~test@test:~$~~ | '''~~adb shell~~Updated Notes'''|-| v1.0| 202 3-05-22| initial version|-| v1.1| 202 3-05-24| 1. How to use the infrared remote control of the Android Box system

~~console:/ $~~2. Instructions for using the Orange Pi OS Droid system

~~<ol start="6" style="list~~|-~~style~~| v1.2| 202 3-05-~~type: decimal;">~~26~~<li>Execute the following command to remount the Android system<~~| 1. Ubuntu/~~li></ol>~~Debian: HDMI IN test method

~~test@test:~$ '''adb root'''~~2. Delete the instructions for using the RTL8821CU USB WIFI module, this module is not recommended

~~test@test:~$ '''adb remount'''~~|-| v1.3| 202 3-05-29| 1. Update the method of using RKDevTool to burn the image to spiflash+ssd

~~<ol start="7" style="list-style-type: decimal;"><li>Then you can transfer files~~ 2. Use RKDevTool to ~~the Android system</li></ol>~~clear SPIFlash

~~test@test:~$ '''adb push example.txt /system/'''~~|}

==~~= Use network connection adb debugging =~~Image update history ==

~~'''Using the network adb does not require a data cable of the Typc~~{| class="wikitable"|-C interface to connect the computer and the development board, but to communicate through the network, so first of all, please ensure that the wired or wireless network of the development board has been connected, and then obtain the IP address of the development board, and then to use.'''| * *Date**

~~<ol style="list-style-type: decimal;"><li>Make sure that the~~ | '''~~service.adb.tcp.port~~Updated Notes''' ~~of the Android system is set to port number 5555console:/ # '''getprop~~ | ~~grep "adb.tcp"'''~~-| 202 3-05-19~~[service~~| Orangepi5plus_1.~~adb~~0.~~tcp~~0_debian_bullseye_server_linux5.~~port]: ['''5555''']</li><li>If '''service.adb.tcp~~10.~~port''' is not set, you can use the following command to set the port number of network adb</li></ol>~~110

~~console:/ # '''setprop service~~Oran gepi5plus_1.~~adb~~0.~~tcp~~0_debian_bullseye_desktop_xfce_linux5.~~port 5555'''~~10.110

~~console:/ # '''stop adbd'''~~Orangepi5p lus_1.0.0_debian_bullseye_desktop_kde-plasma_linux5.10.110

~~console:/ # '''start adbd'''~~Orangepi5plus_1.0.0_ubuntu_focal_server_linux5.10.110

~~<ol start="3" style="list-style-type: decimal;"><li>Install adb tool on Ubuntu PCtest@test:~$ '''sudo apt update'''test@test:~$ '''sudo apt install''' '''-y''' '''adb'''</li><li>Then connect network adb on Ubuntu PCtest@test:~$ '''adb connect 192~~O rangepi5plus_1.0.~~168~~0_ubuntu_focal_desktop_xfce_linux5.110.~~xxx''' '''(The IP address needs to be changed to the IP address of the development board)'''~~110~~* daemon not running; starting now at tcp:5037* daemon started successfullyconnected to 192~~Orangepi5plus_1.~~168~~0.10_ubuntu_jammy_server_linux5.~~xxx:5555test@test:~$ '''adb devices'''List of devices attached192.168~~10.~~1.xxx:5555 device</li><li>Then you can log in to the android system through the adb shell on the Ubuntu PC</li></ol>~~110

~~test@test:~$ '''adb shell'''~~O rangepi5plus_1.0.0_ubuntu_jammy_desktop_xfce_linux5.10.110

~~console:/ #~~Or angepi5plus_1.0.0_ubuntu_jammy_desktop_gnome_linux5.10.110

~~== 2~~linux5.10.110.tar.~~4G USB remote control tested by Android Box ==~~gz

~~<ol style="list~~Opios-~~style~~droid-~~type: decimal;"><li>A 2.4G USB remote control that has been tested so far is shown in the figure below<ol style="list~~aarch64-~~style~~opi5plus-~~type: lower~~23.05-~~alpha;"><li>Contains a remote control[[File:~~linux5.~~/images/media/image771~~10.~~png|199x149px]]</li><li>A USB wireless receiver[[File:~~110-spi-nvme.~~/images/media/image772~~tar.~~png|110x119px]]</li></ol></li><li>The Android Box system does not require any configuration, it can be used after plugging it in</li></ol>~~gz

~~== How to use the infrared remote control of the Android Box system ==~~OrangePi5Plus_RK3588_Android12_v1.0.0.tar.gz

~~<ol style="list-style-type: decimal;"><li>The development board comes with an infrared receiver, and its location is shown in the figure below：[[File:~~OrangePi5Plus_RK3588_Android12_lcd_v1.~~/images/media/image773~~0.~~png|435x124px]]</li><li>Before testing infrared reception, we need to prepare an infrared remote control<div class="figure">~~0.tar.gz

~~[[File:~~OrangePi5Plus-RK3588_Android12-box_v1.0.0.~~/images/media/image774~~tar.~~png|141x127px|6FBFE2FA-31A4-4a26-AC63-9A3E4E359FFF]]~~gz

~~</div>'''Note: The Android system provided by Orange Pi only supports the remote control provided by Orange Pi by default, and the remote control of TV or air conditioner cannot be used~~OrangePi5Plus_RK3588_Android12_spi-nvme_v1.~~'''</li><li>The Android Box system has been adapted to this remote control, and it can be used directly without other settings~~0.~~</li></ol>~~0.tar.gz

~~== How to use HDMI CEC function in Android Box system ==~~nvme_lcd_v1.0.0.tar.gz

~~'''HDMI CEC allows users to control all connected devices through HDMI with only one remote control~~OrangePi5Plus-RK3588_Android12-box_spi-nvme_v1. ~~Based on this function, we can control the development board with the remote control of the TV~~0.~~'''~~0.tar.gz

~~'''Before testing this function, please make sure your TV supports HDMI CEC~~openwrt-aarch64-opi5plus-23.~~'''~~05-linux5.10.110-ext4.img.gz

~~<ol style="list-style-type: decimal;"><li>First connect the development board to the TV through the HDMI cable, then power on and start</li>~~<li>Then turn on the HDMI CEC function in the TV settings. Different TVs may have different ways to turn it on. Here we take Xiaomi TV as an example. Press the menu button on the remote control, then select CEC remote control and press the confirmation button~~[[File:./images/media/image775.png|575x323px]]</li><li>Then select '''"On"''' to open the HDMI CEC remote control[[File:./images/media/image776.png|576x257px]]</li><li>At this point, you can control the Android Box system of the development board through the remote control of the TV</li></ol>~~* initial version

~~= How to compile Android 12 source code =~~23.05-linux5.10.110.img.xz

~~== Download Android 12 source code ==~~5-plus-spi-squashfs-sysupgrade.bin

~~<ol style="list-style-type: decimal;"><li>First download the Android 12 source code sub-volume compressed package from Google network disk[[File:./images/media/image777.png|575x138px]]</li><li>After downloading the sub-volume compression package of the Android 12 source code, please check whether the MD5 checksum is correct, if not, please download the source code againtest@test:~$ '''md5sum -c Android_12.tar.gz.md5sum''''''Android_12.tar.gz00:''' '''confirm''''''Android_12.tar.gz01:''' '''confirm''''''Android_12.tar.gz02:''' '''confirm''''''Android_12.tar.gz03:''' '''confirm''''''Android_12.tar.gz04:''' '''confirm''''''Android_12.tar.gz05:''' '''confirm''''''Android_12.tar.gz06:''' '''confirm''''''Android_12.tar.gz07:''' '''confirm'''</li><li>Then you need to merge multiple compressed files into one, and then decompress</li></ol>~~* initial version

~~test@test:~$ '''cat Android_12~~|-| 202 3-05-24| Orangepi5p lus_1.~~tar~~0.~~gz0* > Android_12~~2_debian_bullseye_desktop_kde-plasma_linux5.~~tar~~10.~~gz'''~~110

~~test@test:~$ '''tar''' '''-xvf Android_12.tar.gz'''~~* Fix the problem that desktop audio cannot be used

~~== Compile the source code of Android 12 ==~~browser_110.0, which supports video playback in h264, h265, vp8, vp9 and av1 formats

~~<ol style="list~~|-~~style-type: decimal;"><li>First install the software packages required to compile the Android12 source codetest@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~~| 202 3-~~mesa~~05-~~dev libxml2-utils xsltproc unzip'''test@test:~$ '''sudo apt-get install''' '''-y''' '''u-boot-tools'''</li><li>There is a build.sh compilation script in the source code, and the compilation parameters are as follows~~26~~<ol style="list~~| Opio s-~~style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li>a.-'''U''': compile ubootb.-'''K''': compile kernelc.-'''A''': compile androidd.-'''u''': package and generate update.img and update_spi_nvme.imge.-'''o''': Compile the OTA packagef.-'''d''': specify kernel dts</li></ol></li><li>Compile uboot, kernel, android and package them into update.img<ol style="list-style-type: lower-alpha;"><li>The command to compile and support HDMI 8K display image (LCD > off by default) is as follows：test@test:~$ '''cd''' '''Android_12'''test@test:~/ Android_12$ '''source build/envsetup.sh'''test@test:~/ Android_12$ '''lunch rk3588_s-userdebug'''test@test:~/ Android_12$ '''./build.sh~~ arch-~~AUKu'''</li><li>The command to compile and support LCD display image is as > follows：test@test:~$ '''cd''' '''Android_12'''test@test:~/ Android_12$ '''export DUAL_LCD=true'''test@test:~/ Android_12$ '''source build/envsetup.sh'''test@test:~/ Android_12$ '''lunch rk3588_s~~aarch64-~~userdebug'''test@test:~/ Android_12$ '''./build.sh~~ gnome-~~AUKu'''</li><li>The command to compile the image of the Box version is as > follows：test@test:~$ '''cd''' '''Android_12'''test@test:~/ Android_12$ '''export BOARD=orangepi5plus'''test@test:~/ Android_12$ '''source build/envsetup.sh'''test@test:~/ Android_12$ '''lunch rk3588_box~~opi5plus-~~userdebug'''test@test:~/ Android_12$ '''~~23.~~/build.sh -AUKu'''</li></ol></li><li>After the compilation is complete, the following information will be printed********rkImageMaker ver 2~~05.1********~~Generating new image, please wait...Writing head info...Writing boot file...Writing firmware...Generating MD5 data...MD5 data generated successfully!New image generated successfully!Making update.img OK.Make update image ok!</li><li>The final image file will be placed in the '''rockdev/Image~~-~~rk3588_s''' directory~~linux5. ~~Among them, '''update~~10.~~img''' is the boot image that supports TF card and eMMC, and '''update_spi_nvme~~110.img~~''' is the boot image of NVME SSDtest@test:~/Android_12$ '''cd rockdev/Image-rk3588s_s'''test@test:~/Android_12/rockdev/Image-rk3588s_s $ '''ls update*'''update~~.~~img update_spi_nvme.img</li><li>If you compile the image of the Box version, the final generated image file will be placed in the '''rockdev/Image-rk3588_box''' directorytest@test:~/Android_12$ '''cd rockdev/Image-rk3588_box'''test@test:~/Android_12/rockdev/Image-rk3588_box$ '''ls update*'''update.img update_spi_nvme.img</li></ol>~~xz

~~= Instructions for using the Orange Pi OS Droid system =~~command line terminal and browser

~~== Function adaptation of OPi OS Droid system ==~~ ~~{| class="wikitable"~~|-~~| style="text-align: left;"| '''Function'''| style="text-align: left;"| '''OPi OS Droid function adaptation'''~~|-~~| style="text-align: left;"| '''HDMI TX1 display'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI TX1 Audio'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI TX2 display'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI TX2 Audio'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI RX display'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''HDMI RX Audio'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''USB2.0X2'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''2.5G PCIe network port X2'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''2.5G PCIe network port light'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Debug serial port'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''RTC'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''FAN interface'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''eMMC extension interface'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''AP6275P-WIFI'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''AP6275P-BT'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''AX200-WIFI'''| style="text-align: left;"| '''NO'''~~|-~~| style="text-align: left;"| '''AX200-BT'''| style="text-align: left;"| '''NO'''~~|-~~| style="text-align: left;"| '''AX210-WIFI'''| style="text-align: left;"| '''NO'''~~|-~~| style="text-align: left;"| '''AX210-BT'''| style="text-align: left;"| '''NO'''~~|-~~| style="text-align: left;"| '''RTL8852BE-WIFI'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''RTL8852BE-BT'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Recovery button'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Type-C interface USB3.0 function'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Type-C interface ADB function'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Type-C interface DP display function'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Type-C interface DP audio playback'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''USB3.0 Hub'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''switch button'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''infrared function'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''led light'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''Onboard MIC'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''headphone playback'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''headphone recording'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''SPK Horn'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''40PIN GPIO'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''40PIN I2C'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''40PIN SPI'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''40PIN UART'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''40PIN PWM'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''TF card start'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''SPI Flash+NVME solid state boot'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''OV13850 camera'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''OV13855 camera'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''GPU'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''VPU'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''NPU'''| style="text-align: left;"| '''OK'''~~|-~~| style="text-align: left;"| '''MIPI LCD'''| style="text-align: left;"| '''NO'''~~|-~~| style="text-align: left;"| '''HDMI CEC'''| style="text-align: left;"| '''NO'''~~|} ~~== Test method of HDMI In ==~~ ~~<ol style="list-style-type: decimal;"><li>The location of the HDMI In interface on the development board is as follows：[[File:./images/media/image348.png|282x90px]]</li><li>Then use the HDMI to HDMI cable shown in the figure below to connect the HDMI output of other devices to the HDMI In interface of the development board[[File:./images/media/image12.png|136x88px]]</li><li>Make sure that the HDMI output of the device connected to the HDMI In interface is normal, and then open the HDMI In test APP[[File:./images/media/image778.png|395x222px]]</li>~~<li>Then the window shown in the figure below will appear. At this time, the video input of HDMI In cannot be seen. You need to click the position marked in the red box in the figure below to enlarge it to full screen~~[[File:./images/media/image779.png|384x229px]]</li>~~<li>Then you can see the video input of HDMI In, and the audio input of HDMI In will also be output from the HDMI TX interface or headphone interface of the development board. The figure below shows the desktop of the Linux system of the OPi5 development board input through HDMI In.~~[[File:./images/media/image780.png|400x238px]]</li></ol>~~ ~~= Appendix =~~ ~~== User Manual Update History ==~~ ~~{| class="wikitable"~~|-| * *vers ion** | * *Date** ~~| '''Updated Notes'''~~|-~~| v1.0| 202 3-05-22| initial version~~|-~~| v1.1| 202 3-05-24| 1. How to use the infrared remote control of the Android Box system~~ ~~2. Instructions for using the Orange Pi OS Droid system~~ |-~~| v1.2| 202 3-05-26| 1. Ubuntu/Debian: HDMI IN test method~~ ~~2. Delete the instructions for using the RTL8821CU USB WIFI module, this module is not recommended~~ |-~~| v1.3| 202 3-05-29| 1. Update the method of using RKDevTool to burn the image to spiflash+ssd~~ ~~2. Use RKDevTool to clear SPIFlash~~ |} ~~== Image update history ==~~ ~~{| class="wikitable"~~|-| * *Date** ~~| '''Updated Notes'''~~|-~~| 202 3-05-19| Orangepi5plus_1.0.0_debian_bullseye_server_linux5.10.110~~ ~~Oran gepi5plus_1.0.0_debian_bullseye_desktop_xfce_linux5.10.110~~ ~~Orangepi5p lus_1.0.0_debian_bullseye_desktop_kde-plasma_linux5.10.110~~ ~~Orangepi5plus_1.0.0_ubuntu_focal_server_linux5.10.110~~ ~~O rangepi5plus_1.0.0_ubuntu_focal_desktop_xfce_linux5.10.110~~ ~~Orangepi5plus_1.0.0_ubuntu_jammy_server_linux5.10.110~~ ~~O rangepi5plus_1.0.0_ubuntu_jammy_desktop_xfce_linux5.10.110~~ ~~Or angepi5plus_1.0.0_ubuntu_jammy_desktop_gnome_linux5.10.110~~ ~~Opios-droid-aarch64-opi5plus-23.05-linux5.10.110.tar.gz~~ ~~Opios- droid-aarch64-opi5plus-23.05-linux5.10.110-spi-nvme.tar.gz~~ ~~OrangePi5Plus_RK3588_Android12_v1.0.0.tar.gz~~ ~~OrangePi5Plus_RK3588_Android12_lcd_v1.0.0.tar.gz~~ ~~OrangePi5Plus-RK3588_Android12-box_v1.0.0.tar.gz~~ ~~OrangePi5Plus_RK3588_Android12_spi-nvme_v1.0.0.tar.gz~~ ~~OrangePi5Plus_RK3588_Android12_spi-nvme_lcd_v1.0.0.tar.gz~~ ~~OrangePi5Plus-RK3588_Android12-box_spi-nvme_v1.0.0.tar.gz~~ ~~openwrt-aarch64-opi5plus-23.05-linux5.10.110-ext4.img.gz~~ * initial version |-~~| 202 3-05-22| Op ios-arch-aarch64-gnome-opi5plus-23.05-linux5.10.110.img.xz~~ ~~openwrt-rockchip -armv8-xunlong_orangepi-5-plus-spi-squashfs-sysupgrade.bin~~ * initial version |-~~| 202 3-05-24| Orangepi5p lus_1.0.2_debian_bullseye_desktop_kde-plasma_linux5.10.110~~ * Fix the problem that desktop audio cannot be used * Update the chromium browser to chromium-browser_110.0, which supports video playback in h264, h265, vp8, vp9 and av1 formats |-~~| 202 3-05-26| Opio s-arch-aarch64-gnome-opi5plus-23.05.1-linux5.10.110.img.xz~~ * Taskbar: remove calendar and music, add shortcuts for command line terminal and browser * Support to open the command line terminal through the shortcut key of CTRL+ALT+T ~~OrangePi5Plus_RK3588_Android12_v1.0.1.tar.gz~~ ~~OrangePi5Plus_RK3588_Android12_v1.0.1_lcd.tar.gz~~ ~~OrangePi5Plus_RK3588_Android12_v1.0.1_spi-nvme.tar.gz~~ ~~OrangePi5Plus_RK3588_Android12_v1.0.1_lcd_spi-nvme.tar.gz~~ * pre-install google play store ~~Orangepi5p lus_1.0.4_debian_bullseye_desktop_kde-plasma_linux5.10.110~~ * Support CTRL+ALT+T shortcut to open the command line terminal * Added shortcuts for konsole terminal and chromium browser in the taskbar * Optimize the display name of the audio device * Optimize test_hdmiin.sh test script * Fix the problem that spiflash+nvme ssd cannot start ~~Oran gepi5plus_1.0.4_debian_bullseye_desktop_xfce_linux5.10.110~~ * Support CTRL+ALT+T shortcut to open the command line terminal * Optimize the display name of the audio device * Optimize test_hdmiin.sh test script * Update the chromium browser to chromium-browser_110.0, which supports video playback in h264, h265, vp8, vp9 and av1 formats * Fix the problem that spiflash+nvme ssd cannot start ~~Or angepi5plus_1.0.4_ubuntu_focal_desktop_xfce_linux5.10.110 Or angepi5plus_1.0.4_ubuntu_jammy_desktop_xfce_linux5.10.110 Or angepi5plus_1.0.4_ubuntu_jammy_desktop_gnome_linux5.10.110~~ * Support CTRL+ALT+T shortcut to open the command line terminal * Optimize the display name of the audio device * Optimize test_hdmiin.sh test script * Fix the problem that spiflash+nvme ssd cannot start ~~Orangepi5plus_1.0.4_debian_bullseye_server_linux5.10.110 Orangepi5plus_1.0.4_ubuntu_focal_server_linux5.10.110 Orangepi5plus_1.0.4_ubuntu_jammy_server_linux5.10.110~~ * Fix the problem that spiflash+nvme ssd cannot start |} ~~= =~~ ~~== ==~~ ~~=== ===~~ ~~<ol start="3" style="list-style-type: decimal;"><li></li><li></li></ol>~~ ~~=== ===~~ ~~<ol start="5" style="list-style-type: decimal;"><li></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li></ol></li></ol>~~ ~~== ==~~ ~~=== ===~~ ~~<ol start="4" style="list-style-type: decimal;"><li></li><li></li></ol>~~ ~~-----~~ ~~-----~~ ~~<ol start="6" style="list-style-type: decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li></ol></li></ol>~~ ~~=== ===~~ ~~<ol start="6" style="list-style-type: decimal;"><li></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li></ol></li></ol>~~ ~~=== ===~~ ~~<ol start="3" style="list-style-type: decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol></li></ol>~~ ~~== ==~~ ~~<ol start="11" style="list-style-type: decimal;"><li></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li><li></li></ol></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li></ol>~~ ~~== ==~~ ~~<ol start="11" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol>~~ ~~<ol start="16" style="list-style-type: decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li></ol></li></ol>~~ ~~<ol start="20" style="list-style-type: decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li></ol>~~ ~~== ==~~ ~~<ol start="11" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li></ol></li><li></li></ol></li><li></li></ol>~~ ~~== ==~~ ~~<ol start="10" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol>~~ ~~<ol style="list-style-type: lower-alpha;"><li></li></ol></li></ol>~~ ~~= =~~ ~~== ==~~ ~~<ol start="8" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~= =~~ ~~== ==~~ ~~-----~~ ~~-----~~ ~~== ==~~ ~~-----~~ ~~-----~~ ~~== ==~~ ~~<ol start="3" style="list-style-type: decimal;"><li></li><li></li></ol>~~ ~~== ==~~ ~~=== ===~~ ~~<ol start="3" style="list-style-type: decimal;"><li></li><li></li></ol>~~ ~~=== ===~~ ~~<ol start="6" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~=== ===~~ ~~<ol start="5" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li></ol>~~ ~~=== ===~~ ~~<ol start="7" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~=== ===~~ ~~<ol start="4" style="list-style-type: decimal;"><li></li><li></li><li></li></ol>~~ ~~== ==~~ ~~<ol start="7" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~== ==~~ ~~=== ===~~ ~~<ol start="4" style="list-style-type: decimal;"><li></li><li></li><li></li></ol>~~ ~~=== ===~~ ~~<ol start="5" style="list-style-type: decimal;"><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li></li></ol>~~ ~~== ==~~ ~~=== ===~~ ~~<ol start="5" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li></ol>~~ ~~=== ===~~ ~~<ol start="7" style="list-style-type: decimal;"><li></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li></ol></li></ol></li><li></li><li></li></ol>~~ ~~== ==~~ ~~<ol start="6" style="list-style-type: decimal;"><li></li></ol>~~ ~~-----~~ ~~-----~~ ~~=== ===~~ ~~<ol start="13" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~=== ===~~ ~~<ol start="11" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~

~~== ==~~OrangePi5Plus_RK3588_Android12_v1.0.1.tar.gz

~~=== ===~~OrangePi5Plus_RK3588_Android12_v1.0.1_lcd.tar.gz

~~<ol start="6" style="list~~OrangePi5Plus_RK3588_Android12_v1.0.1_spi-~~style-type: decimal;"><li></li><li></li><li></li><li></li><li></li></ol>~~nvme.tar.gz

~~== ==~~nvme.tar.gz

~~=== ===~~install google play store

~~<ol start="3" style="list~~Orangepi5p lus_1.0.4_debian_bullseye_desktop_kde-~~style-type: decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li></ol>~~plasma_linux5.10.110

~~=== ===~~* Support CTRL+ALT+T shortcut to open the command line terminal

~~<ol start="3" style="list-style-type: decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li></ol>~~* Added shortcuts for konsole terminal and chromium browser in the taskbar

~~=== ===~~* Optimize the display name of the audio device

~~<ol start="3" style="list-style-type: decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li></ol>~~* Optimize test_hdmiin.sh test script

~~== ==~~* Fix the problem that spiflash+nvme ssd cannot start

~~<ol start="6" style="list-style-type: decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li></ol></li><li></li></ol>~~Oran gepi5plus_1.0.4_debian_bullseye_desktop_xfce_linux5.10.110

~~<ol start="3" style="list-style-type: lower-alpha;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li><li></li></ol></li></ol>~~* Support CTRL+ALT+T shortcut to open the command line terminal

~~<ol start="10" style="list-style-type: decimal;"><li></li></ol>~~ ~~== ==~~ ~~<ol start="10" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~= =~~ ~~== ==~~ ~~<ol start="3" style="list-style-type: decimal;"><li></li><li></li></ol>~~ ~~== ==~~* Optimize the display name of the audio device

~~<ol start="7" style="list-style-type: decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li></li><li></li><li></li></ol>~~* Optimize test_hdmiin.sh test script

~~= =~~browser_110.0, which supports video playback in h264, h265, vp8, vp9 and av1 formats

~~== ==~~* Fix the problem that spiflash+nvme ssd cannot start

Or angepi5plus_1.0.4_ubuntu_focal_desktop_xfce_linux5.10.110

Or angepi5plus_1.0.4_ubuntu_jammy_desktop_xfce_linux5.10.110

Or angepi5plus_1.0.4_ubuntu_jammy_desktop_gnome_linux5.10.110

~~-----~~* Support CTRL+ALT+T shortcut to open the command line terminal

* Optimize the display name of the audio device

~~-----~~ ~~== ==~~ ~~-----~~ ~~-----~~ ~~== ==~~ ~~<ol start="2" style="list-style-type: decimal;"><li></li></ol>~~ ~~-----~~ ~~-----~~ ~~<ol start="7" style="list-style-type: decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li></li><li></li><li></li></ol>~~ ~~== ==~~ ~~<ol start="6" style="list-style-type: decimal;"><li></li></ol>~~ ~~-----~~ ~~-----~~ ~~<ol start="7" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li></ol>~~ ~~== ==~~ ~~<ol start="9" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~== ==~~ ~~<ol start="9" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~== ==~~ ~~<ol start="10" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~== ==~~* Optimize test_hdmiin.sh test script

~~<ol~~ * Fix the problem that spiflash+nvme ssd cannot start~~="5" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li></ol>~~

Orangepi5plus_1.0.4_debian_bullseye_server_linux5.10.110<~~span id="section-136"~~br />Orangepi5plus_1.0.4_ubuntu_focal_server_linux5.10.110 ~~== ==~~Orangepi5plus_1.0.4_ubuntu_jammy_server_linux5.10.110

~~<ol~~ * Fix the problem that spiflash+nvme ssd cannot start~~="4" style="list-style-type: decimal;"><li></li><li></li><li></li></ol>~~ ~~== ==~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li></li><li></li></ol>~~ ~~<ol start="4" style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol>~~ ~~<ol start="3" style="list-style-type: lower-alpha;"><li></li><li></li></ol>~~ ~~== ==~~ ~~=== ===~~ ~~<ol start="9" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~=== ===~~ ~~<ol start="9" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~=== ===~~ ~~<ol start="9" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~=== ===~~ ~~<ol start="11" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~== ==~~ ~~=== ===~~ ~~<ol start="9" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~=== ===~~ ~~<ol start="6" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~== ==~~ ~~<ol start="3" style="list-style-type: decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li></li></ol>~~ ~~== ==~~ ~~<ol start="5" style="list-style-type: decimal;"><li></li><li></li><li></li></ol>~~ ~~== ==~~ ~~<ol start="5" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li></ol>~~ ~~= =~~ ~~== ==~~ ~~<ol start="4" style="list-style-type: decimal;"><li><ol style="list-style-type: lower-alpha;"><li></li><li></li></ol></li><li></li><li></li></ol>~~ ~~== ==~~ ~~<ol start="7" style="list-style-type: decimal;"><li></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li><li></li><li></li><li></li></ol></li><li><ol style="list-style-type: lower-alpha;"><li></li><li></li><li></li></ol></li><li></li><li></li><li></li></ol>~~ ~~= =~~ ~~== ==~~ ~~-----~~ ~~-----~~ ~~== ==~~ ~~<ol start="6" style="list-style-type: decimal;"><li></li><li></li><li></li><li></li><li></li></ol>~~ ~~= =~~ ~~== ==~~ ~~{| class="wikitable"~~|-||||-||||-||~~| #~~ # |-||~~| #~~ # |-||~~| #~~ #

|}

~~~~

~~== ==~~

~~-----~~

Admin

Bureaucrats, Administrators

8,367

edits

Wiki-Orange Pi β

Changes

Orange Pi 5 Plus

Wiki-Orange Pi ^β