first commit
237
OrangePi5Plus install to eMMC.md
Normal file
|
@ -0,0 +1,237 @@
|
||||||
|
range Pi User Manual Copyright reserved by Shenzhen Xunlong Software Co., Ltd
|
||||||
|
|
||||||
|
2\.5. **How to burn Linux image to eMMC**
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|**Note, after burning the image into eMMC, if the test finds that it cannot be**|
|
||||||
|
| - |
|
||||||
|
|**started, please clear the SPIFlash and try again. For the method of clearing**|
|
||||||
|
|**SPIFlash, please refer to the method of using RKDevTool to clear SPIFlash.**|
|
||||||
|
|
||||||
|
1. **How to use RKDevTool to burn Linux image into eMMC**
|
||||||
|
|
||||||
|
|**Note that all the following operations are performed on a Windows computer.**|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|**Note that the Linux image mentioned here specifically refers to the image of**|
|
||||||
|
| - |
|
||||||
|
|**Linux distributions such as Debian, Ubuntu, OpenWRT or OPi OS Arch**|
|
||||||
|
|**downloaded from the [Orange Pi data download page](http://www.orangepi.org/html/serviceAndSupport/index.html).**|
|
||||||
|
|
||||||
|
1) The development board reserves the expansion interface of the eMMC module. Before burning 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 eMMC module and the method of plugging into the development board are as follows:
|
||||||
|
|
||||||
|
![ref1] ![ref2]
|
||||||
|
|
||||||
|
![ref3]
|
||||||
|
|
||||||
|
2) It is also necessary to prepare a data cable with a good quality Type-C interface
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
3) Then download Rockchip **DriverAssitant\_v5.12.zip** and **MiniLoader** and the burning tool RKDevTool\_Release\_v2.96.zipRKDevTool\_Release\_v3.15.zip from the [Orange Pi data download page, ](http://www.orangepi.org/html/serviceAndSupport/index.html)please make sure that the version of the downloaded RKDevTool tool is v2.96.
|
||||||
|
1. On the download page of Orange Pi, first select the official tool, and then enter the following folder
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
2. Then download all the files below
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|**Note that the "MiniLoader-things needed to burn the Linux image" folder is**|
|
||||||
|
| - |
|
||||||
|
|**hereinafter referred to as the MiniLoader folder.**|
|
||||||
|
|
||||||
|
4) Then download the Linux operating system image file compression package that you want to burn from the **[Orange Pi data download page**](http://www.orangepi.org/html/serviceAndSupport/index.html)**, 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
|
||||||
|
|
||||||
|
**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.**|
|
||||||
|
||
|
||||||
|
|
||||||
|
5) 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
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
6) After opening **DriverInstall.exe,** the steps to install the Rockchip driver are as follows
|
||||||
|
1. Click the "**Driver Installation**" button
|
||||||
|
|
||||||
|

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

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

|
||||||
|
|
||||||
|
8) 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**"
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
9) Then start burning the Linux image into eMMC
|
||||||
|
1. 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
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
2. Make sure that the development board is not inserted into the TF card and not connected to the power supply
|
||||||
|
2. 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:
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
4. Then connect the power supply of the Type-C interface to the development board, and power on, and then release the MaskROM button
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
5. 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**"
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
6. Then place the mouse cursor in the area below
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
7. Then click the right mouse button and the selection interface shown in the figure below will pop up
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
8. Then select the **import configuration** option
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
9. Then select the **rk3588\_linux\_emmc.cfg** configuration file in the **MiniLoader** folder downloaded earlier, and click **Open**
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
10. Then click **OK**
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
11. Then click the position shown in the figure below
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
12. Then select **MiniLoaderAll.bin** in the **MiniLoader** folder downloaded earlier, and then click to **open**
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
13. Then click the position shown in the figure below
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
14. . Then select the path of the linux image you want to burn, and click **Open**
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|**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.**|
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
15. Then please check the option to **force writing by address**
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
16. Then click the execute button to start burning the linux image to the eMMC of the development board
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
17. The log displayed after burning the linux image is shown in the figure below
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
18. After burning the linux image into the eMMC, the linux system will start automatically.
|
||||||
|
|
||||||
|
|**Note, after burning the image into eMMC, if the test finds that it cannot be**|
|
||||||
|
| - |
|
||||||
|
|**started, please clear the SPIFlash and try again. For the method of clearing**|
|
||||||
|
|**SPIFlash, please refer to** the method of using RKDevTool to clear SPIFlash**.**|
|
||||||
|
|
||||||
|
2. **Using the dd command to burn the Linux image into eMMC**
|
||||||
|
|
||||||
|
|**Note that the Linux image mentioned here specifically refers to the image of**|
|
||||||
|
| - |
|
||||||
|
|**Linux distributions such as Debian, Ubuntu, OpenWRT or OPi OS Arch**|
|
||||||
|
|**downloaded from the Orange Pi data download page.**|
|
||||||
|
|
||||||
|
1) The development board reserves the expansion interface of the eMMC module. Before burning 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 eMMC module and the method of plugging into the development board are as follows:
|
||||||
|
|
||||||
|
![ref1] ![ref2]
|
||||||
|
|
||||||
|
![ref3]
|
||||||
|
|
||||||
|
2) Using the dd command to burn the linux image to eMMC needs to be done with a TF card, so first you need to burn the linux image to the TF card, and then use the TF card to start the development board to enter the linux system. For the method of burning the Linux image to the TF card, please refer to the instructions in the two sections of **the method of burning the Linux image to the TF card based on the Windows PC** and **the method of burning the Linux image to the TF card based on the Ubuntu PC.**
|
||||||
|
2) After using the TF card to start the linux system, we first upload the decompressed linux image file (Debian, Ubuntu image or OPi Arch 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.
|
||||||
|
2) After uploading the image to the linux system of the development board, we enter the storage path of the image file in the command line of the linux system of the development
|
||||||
|
|
||||||
|
board. For example, I store the linux image of the development board in the **/home/orangepi/Desktop** directory Download it, and then enter the **/home/orangepi/Desktop** directory to see the uploaded image file.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|orangepi@orangepi:~$ **cd /home/orangepi/Desktop**|
|
||||||
|
| - |
|
||||||
|
|orangepi@orangepi:~/Desktop$ **ls**|
|
||||||
|
|Orangepi5plus\_x.x.x\_debian\_bullseye\_desktop\_xfce\_linux5.10.160.img|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|**How to enter the command line of the development board linux system?**|
|
||||||
|
| - |
|
||||||
|
|**1. For the method of using the serial port to log in to the terminal, please refer to**|
|
||||||
|
|**the instructions in the section on how to use the debugging serial port.**|
|
||||||
|
|**2. Use ssh to remotely log in to the Linux system, please refer to the instructions in**|
|
||||||
|
|**the section of SSH remote login to the development board.**|
|
||||||
|
|**3. If a display screen such as HDMI or LCD is connected, you can open a command**|
|
||||||
|
|
||||||
|
**line terminal on the desktop.**
|
||||||
|
|
||||||
|
5) Next, we first use the following command to confirm the device node of eMMC
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|orangepi@orangepi:~/Desktop$ **ls /dev/mmcblk\*boot0 | cut -c1-12**|
|
||||||
|
| - |
|
||||||
|
|**/dev/mmcblk1**|
|
||||||
|
|
||||||
|
6) 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
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|orangepi@orangepi:~/Desktop$ **sudo dd bs=1M if=/dev/zero of=/dev/mmcblk1 count=1000 status=progress**|
|
||||||
|
| - |
|
||||||
|
|orangepi@orangepi:~/Desktop$ **sudo sync**|
|
||||||
|
|
||||||
|
7) Then you can use the dd command to burn the linux image of the development board into the eMMC
|
||||||
|
1. In the following command, the **if=** parameter is followed by the full path where the linux image is stored + the name of the Linux image (such as **the name of /home/orangepi/Desktop/Linux image**). Because we have entered the path of the linux image above, we only need to fill in the name of the Linux image.
|
||||||
|
1. Please do not copy the linux image name in the following command, but replace it with the actual image name (because the version number of the image may be updated).
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|**sudo dd bs=1M if=Orangepi5plus\_x.x.x\_debian\_bullseye\_desktop\_xfce\_linux5.10.160.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.**|
|
||||||
|
|
||||||
|
8) 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.
|
||||||
|
48
|
||||||
|
|
||||||
|
[ref1]: md_pictures/Aspose.Words.4646d834-1205-42bd-bfef-61dc6489a814.004.png
|
||||||
|
[ref2]: md_pictures/Aspose.Words.4646d834-1205-42bd-bfef-61dc6489a814.005.png
|
||||||
|
[ref3]: md_pictures/Aspose.Words.4646d834-1205-42bd-bfef-61dc6489a814.006.png
|
BIN
OrangePi_5_Plus_RK3588_user manual_v1.9.3.pdf
Normal file
14
README.md
Normal file
|
@ -0,0 +1,14 @@
|
||||||
|
# Installazione Orange Pi 5 Plus (Debian 12)
|
||||||
|
|
||||||
|
## Cosa serve
|
||||||
|
|
||||||
|
* sistema Windows
|
||||||
|
* tools ufficiali
|
||||||
|
* Android and linux image writing tool-RKDevTool and driver
|
||||||
|
* immagine del sistema operativo
|
||||||
|
* manuale
|
||||||
|
* cavo USB da Windows a Orange (USB-C)
|
||||||
|
|
||||||
|
SW scaricabile dal sito di orange <http://www.orangepi.org/>
|
||||||
|
|
||||||
|
[Orange Pi 5 Plus Download](http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus.html)
|
After Width: | Height: | Size: 1.7 KiB |
After Width: | Height: | Size: 242 B |
After Width: | Height: | Size: 428 B |
After Width: | Height: | Size: 16 KiB |
After Width: | Height: | Size: 24 KiB |
After Width: | Height: | Size: 72 KiB |
After Width: | Height: | Size: 12 KiB |
After Width: | Height: | Size: 19 KiB |
After Width: | Height: | Size: 29 KiB |
After Width: | Height: | Size: 370 B |
After Width: | Height: | Size: 21 KiB |
After Width: | Height: | Size: 52 KiB |
After Width: | Height: | Size: 18 KiB |
After Width: | Height: | Size: 19 KiB |
After Width: | Height: | Size: 58 KiB |
After Width: | Height: | Size: 28 KiB |
After Width: | Height: | Size: 83 KiB |
After Width: | Height: | Size: 81 KiB |
After Width: | Height: | Size: 84 KiB |
After Width: | Height: | Size: 34 KiB |
After Width: | Height: | Size: 38 KiB |
After Width: | Height: | Size: 34 KiB |
After Width: | Height: | Size: 34 KiB |
After Width: | Height: | Size: 31 KiB |
After Width: | Height: | Size: 30 KiB |
After Width: | Height: | Size: 25 KiB |
After Width: | Height: | Size: 32 KiB |
After Width: | Height: | Size: 25 KiB |
After Width: | Height: | Size: 38 KiB |
After Width: | Height: | Size: 35 KiB |
After Width: | Height: | Size: 34 KiB |
After Width: | Height: | Size: 35 KiB |
After Width: | Height: | Size: 412 B |
After Width: | Height: | Size: 136 B |