Changes

Orange Pi CM4

5,873 bytes added, 14:34, 18 September 2023

→‎Method of burning using dd command

<li>Please ensure that the SPI Flash is affixed to the development board. The position of SPI Flash on the development board is shown in the figure below. No other Settings are required before burning

[[File:cm4-img74.png]]</li>

<li>Burning Linux image to SPIFlash+NVMe SSD requires TF card to complete, so first need to burn Linux image to TF card, and then use the TF card to start the development board into the Linux system. For the method of burning a Linux image to a TF card, see the two sections on [[\lOrange Pi CM4#Method of burning Linux image to TF card based on Windows PC|'''the method of burning a Linux image to a TF card''' '''based on a Windows PC''']] and '''[[\lOrange Pi CM4#Method of burning Linux image to TF card based on Ubuntu PC|the method of burning a Linux image to a TF card based on an Ubuntu PC]].'''</li>

<li>After starting the Linux system with TF card, we first burn the u-boot image into SPI Flash

<li>Run '''nand-sata-install'''l first. '''Ordinary users remember to ~~>~~ add sudo permission'''{| class="wikitable" style="width:800px;" |-| orangepi@orangepi:~$ '''sudo nand-sata-install'''|}</li><li>Then select '''7 Install/Update ther bootloader on SPI Flash'''</li~~></ol></li></ol~~>

[[File:cm4-img84.png]]

</div></ol>

<li>Then select '''<Yes>'''</li~~></ol~~>

[[File:cm4-img85.png]]

</div></ol>

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

[[File:cm4-img86.png]]

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

<li>Then upload the Linux image file (Debian or Ubuntu image downloaded from the official website) to the TF card. For details about how to upload a Linux image file to the development board, see section [[\lOrange Pi CM4#Method of uploading files to the development board Linux system|'''Uploading Files to the Linux system on the Development Board''']].</li>

<li>After uploading the image to the Linux system of the development board, we can enter the storage path of the image file in the command line of the Linux system of the development board. For example, I saved the Linux image of the development board in the directory '''/home/orangepi/Desktop'''. Then go to the '''/home/orangepi/Desktop''' directory and you will see the uploaded image file.

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

|-

|

orangepi@orangepi:~$ '''cd /home/orangepi/Desktop'''

orangepi@orangepi:~/Desktop$ '''ls'''

Orangepi3b_x.x.x_debian_bullseye_desktop_xfce_linux5.10.160.img

|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''How to enter the development board Linux system command line?''''''1. For details about how to log in to the terminal through the serial port, see section [[\lOrange Pi CM4#How to use the debugging serial port|Debugging Serial Port]].''''''2. For details about how to remotely log in to the Linux operating system over ssh, see section "[[\lOrange Pi CM4#SSH remote login development board|Logging In to the Development Board over SSH]]".''''''3. If you are connected to a display screen such as HDMI or LCD, you can open a command line terminal on the desktop.'''</big>|}</li>

<li>Next, let's first make sure that NVMe SSD has been properly recognized by Linux development board. If the NVMe SSD is correctly identified, run the '''sudo fdisk -l''' command to view information about the '''nvme'''

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

|-

|

orangepi@orangepi:~/Desktop$ '''sudo fdisk -l | grep "nvme0n1"'''

Disk /dev/nvme0n1: 1.86 TiB, 2048408248320 bytes, 4000797360 sectors

|}

Use the '''lspci''' command to see an NVME-related PCI device

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

|-

|

orangepi@orangepi:~/Desktop$ '''lspci'''

00:00.0 PCI bridge: Fuzhou Rockchip Electronics Co., Ltd Device 3566 (rev 01)

01:00.0 Non-Volatile memory controller: Realtek Semiconductor Co., Ltd. Device 5765 (rev 01)|}</li>

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

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

|-

|

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

orangepi@orangepi3b:~/Desktop$ '''sudo sync'''|}</li>

<li>You can then use the dd command to burn the Linux image of the development board into the NVMe SSD

<li>if = parameter in the command is to fill in behind the Linux + ~~>~~ Linux mirror image to store the full path name (such ~~>~~ as'''/home/orangepi/Desktop/Linux image name'''). Since ~~>~~ we have entered the path of the Linux image above, we only ~~>~~ need to fill in the name of the Linux image.</li><li>Do not copy the Linux image name in the following command. ~~>~~ Replace it with the actual image name (because the version of ~~>~~ the image may be updated).{| class="wikitable" style="width:800px;" |-|

'''sudo dd bs=1M if=Orangepi3b_x.x.x_debian_bullseye_desktop_xfce_linux5.10.160.img of=/dev/nvme0n1 status=progress'''

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

|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Note that if you are uploading a.7z or.xz or.gz Linux image file, remember to decompress it before burning it with the dd command.''''''A detailed description of all the parameters of the dd command and more usage can be seen by running the man dd command on Linux.'''</big>|}</li></ol>

</li>

<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, pull out the TF card, press the power button again, and then start the Linux system in the SPIFlash+NVMe SSD.</li>

<li>128GB NVMe SSD

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

|-

|

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

<pspan style="margin-right: 80px;">Filesystem Size Used Avail Use% Mounted on</pspan> <pspan style="margin-right: 110px;">udev 3.8G 8.0K 3.8G 1% /dev</pspan> <pspan style="margin-right: 100px;">tmpfs 769M 1.4M 768M 1% /run</pspan> <pspan style="margin-right: 25px;color:#FF0000">'''/dev/nvme0n1p2 ''''''118G ''''''5.8G ''''''111G ''''''5% /'''</pspan> <pspan style="margin-right: 100px;">tmpfs 3.8G 0 3.8G 0% /dev/shm</pspan> <pspan style="margin-right: 100px;">tmpfs 5.0M 4.0K 5.0M 1% /run/lock</pspan> <pspan style="margin-right: 100px;">tmpfs 3.8G 16K 3.8G 1% /tmp</pspan> <pspan style="margin-right: 25px;color:#FF0000">'''/dev/nvme0n1p1 ''''''256M ''''''90M ''''''166M ''''''36% /boot'''</pspan> <pspan style="margin-right: 65px;">/dev/zram1 194M 9.9M 170M 6% /var/log</pspan> <pspan style="margin-right: 100px;">tmpfs 769M 60K 769M 1% /run/user/1000</pspan> <pspan style="margin-right: 100px;">tmpfs 769M 48K 769M 1% /run/user/0</pspan> |}</li>

<li>2TB NVMe SSD

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

|-

|

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

<pspan style="margin-right: 80px;">Filesystem Size Used Avail Use% Mounted on</pspan> <pspan style="margin-right: 110px;">udev 3.8G 8.0K 3.8G 1% /dev</pspan> <pspan style="margin-right: 100px;">tmpfs 769M 1.4M 768M 1% /run</pspan> <pspan style="margin-right: 25px;color:#FF0000">'''/dev/nvme0n1p2 ''''''1.9T ''''''4.1G ''''''1.8T ''''''1% /'''</pspan> <pspan style="margin-right: 100px;">tmpfs 3.8G 0 3.8G 0% /dev/shm</pspan> <pspan style="margin-right: 100px;">tmpfs 5.0M 4.0K 5.0M 1% /run/lock</pspan> <pspan style="margin-right: 65px;">/dev/zram2 3.7G 76K 3.5G 1% /tmp</pspan> <pspan style="margin-right: 25px;color:#FF0000">'''/dev/nvme0n1p1 ''''''256M ''''''90M ''''''166M ''''''36% /boot'''</pspan> <pspan style="margin-right: 65px;">/dev/zram1 194M ~~15M 165M~~ 9.9M 170M 6% /var/log</pspan> <pspan style="margin-right: 100px;">tmpfs 769M 60K 769M 1% /run/user/1000</pspan> <pspan style="margin-right: 100px;">tmpfs 769M 48K 769M 1% /run/user/0</pspan> |}</li></ol>

</li>

<li>When the TF card and NVMe SSD burn exactly the same system, '''if the TF card and NVMe SSD are inserted in the development board, power on the development board at this time, u-boot will give priority to start the system in the TF card.''' However, since the TF card and the NVMe SSD system are identical, the UUID of the /'''boot''' partition and '''rootfs''' partition in the two storage devices are the same, which will cause the TF card may load the NVMe SSD partition when it is started. Run the following script to solve this problem.

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

|-

|

orangepi@orangepi:~$ '''sudo fix_mmc_ssd.sh'''

|}{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''An identical system means that the mirror name is exactly the same. Even if it is a Debian11 system, the version is different.'''</big>|}</li></ol>

=== Method of burning using balenaEtcher software ===

Admin

Bureaucrats, Administrators

8,367

edits

Wiki-Orange Pi β

Changes

Orange Pi CM4

Wiki-Orange Pi ^β