Changes

Orange Pi CM4

2,720 bytes removed, 17:28, 15 September 2023

no edit summary

[[File:~~media/image3~~cm4-img3.png]]

<big>'''Bottom view:'''</big>

[[File:~~media/image4~~cm4-img4.png]]

[[File:~~media/image5~~cm4-img5.png]]

<big>'''Bottom view:'''</big>

[[File:~~media/image6~~cm4-img6.png]]

[[File:~~media/image7~~cm4-img7.png]]

</div>

[[File:~~media/image8~~cm4-img8.png]]

</div>

[[File:~~media/image9~~cm4-img9.png]]

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

<li><p>TF card, a class 10 or above high-speed SanDisk card with a minimum capacity of 16GB (32GB or above recommended)</p>

<p>[[File:~~media/image10~~cm4-img10.png]]</p></li>

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

<p>[[File:~~media/image11~~cm4-img11.png]]</p></li>

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

<p>[[File:~~media/image12~~cm4-img12.png]]</p></li>

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

[[File:~~media/image13~~cm4-img13.png]]

</div>

</li>

<li><p>Power adapter. Orange Pi CM4 is recommended to use a 5V/3A Type-C power supply.</p>

<p>[[File:~~media/image14~~cm4-img14.png]]</p></li>

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

<p>[[File:~~media/image15~~cm4-img15.png]]</p></li>

<li><p>USB camera</p>

<p>[[File:~~media/image16~~cm4-img16.png]]</p></li>

<li><p>PCIe NVMe SSD, the development board supports SSDs with M.2 2230 and M.2 2242 specifications. M.2 2280 is also supported, but it cannot be fixed with screws.</p>

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

</li>

<li><p>100M or 1000M network cable, used to connect the development board to the Internet</p>

<p>[[File:~~media/image17~~cm4-img17.png]]</p></li>

<li><p>USB2.0 male-to-male data cable, used for burning images to eMMC, TF card, etc.</p>

[[File:~~media/image18~~cm4-img18.png]]

</div></li>

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

<p>[[File:~~media/image19~~cm4-img19.png]] [[File:~~media/image20~~cm4-img20.png]]</p></li>

<li><p>Personal computer with Ubuntu and Windows operating systems installed</p>

<li><p>The website for downloading the English version is:</p>

<p>[http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-3B.html '''http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-CM4.html''']</p>

<p>[[File:~~media/image21~~cm4-img21.png]]</p></li>

<li><p>The information mainly includes</p></li></ol>

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

<p>[[File:~~media/image22~~cm4-img22.png]]</p></li>

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

<p>[[File:~~media/image23~~cm4-img23.png]]</p></li>

<li><p>If you downloaded the version of balenaEtcher that needs to be installed, please install it first and then use it. If you downloaded the Portable version of balenaEtcher, just double-click to open it. The balenaEtcher interface after opening is as shown below:</p>

<p>[[File:~~media/image24~~cm4-img24.png]]</p>

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

|-

<big>'''If the following error is prompted when opening balenaEtcher:'''</big>

[[File:~~media/image25~~cm4-img25.png|center]]

<big>'''Please select balenaEtcher, right-click, and select Run as administrator.'''</big>

[[File:~~media/image26~~cm4-img26.png|center]]

|}

</li></ol>

::[[File:~~media/image27~~cm4-img27.png]]

</div></li>

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

<p>[[File:~~media/image28~~cm4-img28.png]]</p></li>

<li><p>After burning the Linux image, balenaEtcher will also verify the image burned into 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</p>

<p>[[File:~~media/image29~~cm4-img29.png]]</p></li>

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

[[File:~~media/image30~~cm4-img30.png]]

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

[[File:~~media/image18~~cm4-img18.png]]

</div></li>

[[File:~~media/image31~~cm4-img31.png]]

</div></li>

[[File:~~media/image32~~cm4-img32.png]]

</div>

<li><p>Then download the compressed package of the Linux operating system image file you want to burn from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-CM4-1.html '''Orange Pi information download page'''], and then use the decompression software to decompress it. In the decompressed file, the file ending with "'''.img'''" is the image file of the operating system. , the size is generally above 2GB</p></li>

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

<p>[[File:~~media/image33~~cm4-img33.png]]</p></li>

<li><p>Open '''DriverInstall.exe''' and install the Rockchip microdriver as follows</p>

<li><p>Click the "'''Driver Installation'''" button</p>

<p>[[File:~~media/image34~~cm4-img34.png]]</p></li>

<li><p>After waiting for a period of time, a window will pop up prompting "'''Driver installation successful'''", then click the "'''OK'''" button.</p>

<p>[[File:~~media/image35~~cm4-img35.png]]</p></li></ol>

</li>

<li><p>Then unzip '''RKDevTool_Release_v3.15.zip'''. This software does not need to be installed. Just find '''RKDevTool''' in the unzipped folder and open it.</p>

<p>[[File:~~media/image36~~cm4-img36.png]]</p></li>

<li><p>After opening the '''RKDevTool''' burning tool, because the computer has not connected to the development board through the USB2.0 male-to-male data cable at this time, the lower left corner will prompt "'''No device found'''"</p>

<p>[[File:~~media/image37~~cm4-img37.png]]</p></li>

<li><p>Then start burning the Linux image to the TF card</p>

<li><p>First, connect the development board to the Windows computer through a USB2.0 male-to-male data cable. The location of the USB2.0 programming port on the development board is as shown in the figure below.</p>

<p>[[File:~~media/image38~~cm4-img38.png]]</p></li>

<li><p>Make sure the TF card slot is not inserted into the TF card</p></li>

<li><p>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:</p>

<p>[[File:~~media/image39~~cm4-img39.png]]</p></li>

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

<p>[[File:~~media/image40~~cm4-img40.png]]</p></li>

<li><p>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'''"</p>

<p>[[File:~~media/image41~~cm4-img41.png]]</p></li>

<li><p>At this time, please insert the TF card into the TF card slot</p></li>

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

[[File:~~media/image42~~cm4-img42.png]]

</div></li>

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

<p>[[File:~~media/image43~~cm4-img43.png]]</p></li>

<li><p>Then select the '''<span class="mark">import configuration</span>''' option</p>

<p>[[File:~~media/image44~~cm4-img44.png]]</p></li>

<li><p>Then select the '''rk356x_linux_tfcard.cfg''' configuration file in the '''MiniLoader''' folder downloaded earlier, and click '''<span class="mark">Open</span>'''</p>

[[File:~~media/image45~~cm4-img45.png]]

</div></li>

<li><p>Then click '''<span class="mark">OK</span>'''</p>

<p>[[File:~~media/image46~~cm4-img46.png]]</p></li>

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

<p>[[File:~~media/image47~~cm4-img47.png]]</p></li>

<li><p>Then select '''MiniLoaderAll.bin''' in the '''MiniLoader''' folder downloaded earlier, and then click to '''<span class="mark">open</span>'''</p>

[[File:~~media/image48~~cm4-img48.png]]

</div></li>

<li><p>Then click on the location shown in the picture below</p>

<p>[[File:~~media/image49~~cm4-img49.png]]</p></li>

<li><p>Then select the path of the Linux image you want to burn, and then click '''<span class="mark">Open</span>'''</p>

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

<big><p>'''Before burning the image, it is recommended to rename the Linux image to be burned to orangepi.img or another shorter name, so that you can see the percentage of the burning progress when burning the image.'''</p></big>

|}

<p>[[File:~~media/image50~~cm4-img50.png]]</p></li>

<li><p>Then please check the option to '''<span class="mark">force writing by address</span>'''.</p>

<p>[[File:~~media/image51~~cm4-img51.png]]</p></li>

<li><p>Click the execute button again and it will start burning the Linux image to the tf card of the development board.</p>

<p>[[File:~~media/image52~~cm4-img52.png]]</p></li>

<li><p>The display log after the r.Linux image is burned is as shown below</p>

[[File:~~media/image53~~cm4-img53.png]]

</div></li>

[[File:~~media/image54~~cm4-img54.png]]

</div></li>

<li><p>Then click "'''Format'''". A warning box will pop up before formatting. After selecting "'''Yes (Y)'''", formatting will begin.</p></li></ol>

[[File:~~media/image55~~cm4-img55.png]]

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

<p>[[File:~~media/image56~~cm4-img56.png]]</p></li></ol>

[[File:~~media/image57~~cm4-img57.png]]

</div></li>

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

<p>[[File:~~media/image22~~cm4-img22.png]]</p></li>

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

<p>[[File:~~media/image58~~cm4-img58.png]]</p></li>

<li><p>Download the compressed Linux operating system image file you want to burn from [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-CM4-1.html '''Orange Pi's data download page'''], and then use the decompression software to decompress it. Files ending with "'''.img''' "in the decompressed files are the image files of the operating system, and the size is generally more than 2GB</p>

<p>The following command is used to decompress the compressed package ending in 7z</p>

<p>Orangepicm4_1.0.0_debian_bullseye_desktop_xfce_linux5.10.160.img: OK</p></li>

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

<p>[[File:~~media/image59~~cm4-img59.png]]</p></li>

<li><p>The specific steps to burn a Linux image using balenaEtcher are shown below</p>

<p>a. Select the path of the Linux image file to be burned</p>

[[File:~~media/image27~~cm4-img27.png]]

</div></li>

<li><p>The interface displayed during balenaEtcher burning the Linux image is as shown in the following figure. In addition, the progress bar showing purple indicates that the Linux image is burning to the TF card</p>

<p>[[File:~~media/image60~~cm4-img60.png]]</p></li>

<li><p>After the Linux image is burned, 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 following figure, the green progress bar indicates that the image has been burned, and balenaEtcher is verifying the burned image</p>

<p>[[File:~~media/image61~~cm4-img61.png]]</p></li></ol>

<li><p>The display interface of balenaEtcher after the successful burning is shown as the following figure. If the green indicator icon is displayed indicating that the image is burned successfully, you can exit balenaEtcher at this time, and then pull out the TF card and insert it into the TF card slot of the development board</p>

<p>[[File:~~media/image62~~cm4-img62.png]]</p></li></ol>

[[File:~~media/image18~~cm4-img18.png]]

</div></li>

[[File:~~media/image31~~cm4-img31.png]]

</div></li>

[[File:~~media/image32~~cm4-img32.png]]

</div>

<li><p>Download the compressed Linux operating system image file you want to burn from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-CM4-1.html '''Orange Pi's data download page'''], and then use the decompression software to decompress it. After decompressing the file, the file ending with "'''.img''' "is the image file of the operating system, and the size is generally more than 2GB</p></li>

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

<p>[[File:~~media/image33~~cm4-img33.png]]</p></li>

<li><p>Open '''DriverInstall.exe''' and install the SWick micro driver as follows</p>

<li><p>Click the "'''Driver Installation'''" button</p>

<p>[[File:~~media/image34~~cm4-img34.png]]</p></li>

<li><p>Wait for a period of time, the pop-up window will prompt > "'''Driver installation successful'''", and then click the > "'''OK'''" button</p>

<p>[[File:~~media/image35~~cm4-img35.png]]</p></li></ol>

</li>

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

<p>[[File:~~media/image36~~cm4-img36.png]]</p></li>

<li><p>After opening the '''RKDevTool''' burning tool, because the computer has not connected to the development board through the USB2.0 public-to-public data cable at this time, the lower left corner will indicate "'''no device found'''".</p>

<p>[[File:~~media/image37~~cm4-img37.png]]</p></li>

<li><p>Then start burning the Linux image into eMMC</p>

<li><p>First, connect the development board to the Windows computer through the USB2.0 male-to-public data cable. The position of the USB2.0 burning port on the development board is shown in the figure below</p>

<p>[[File:~~media/image38~~cm4-img38.png]]</p></li>

<li><p>Ensure that no TF card is inserted into the development board and no power supply is connected</p></li>

<li><p>Then press and hold the MaskROM button on the development board. The position of the MaskROM button on the development board is shown as follows:</p>

<p>[[File:~~media/image39~~cm4-img39.png]]</p></li>

<li><p>Then connect the Type-C interface to the development board, and power on, and then you can release the MaskROM button</p>

<p>[[File:~~media/image40~~cm4-img40.png]]</p></li>

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

<p>[[File:~~media/image41~~cm4-img41.png]]</p></li>

<li><p>Then place the mouse cursor on the field below</p>

[[File:~~media/image63~~cm4-img63.png]]

</div></li>

<li><p>Then click the right mouse button to pop up the selection interface as shown in the following figure</p>

<p>[[File:~~media/image43~~cm4-img43.png]]</p></li>

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

<p>[[File:~~media/image44~~cm4-img44.png]]</p></li>

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

[[File:~~media/image64~~cm4-img64.png]]

</div></li>

<li><p>Then click '''<span class="mark">OK</span>'''</p>

<p>[[File:~~media/image65~~cm4-img65.png]]</p></li>

<li><p>Then click on the location shown in the image below</p>

<p>[[File:~~media/image66~~cm4-img66.png]]</p></li>

<li><p>Select '''MiniLoaderAll.bin''' from the '''MiniLoader''' folder downloaded earlier, and then click '''<span class="mark">Open</span>'''</p>

[[File:~~media/image48~~cm4-img48.png]]

</div></li>

<li><p>Then click on the location shown in the image below</p>

<p>[[File:~~media/image67~~cm4-img67.png]]</p></li>

<li><p>Then select the path of the Linux image you want to burn and click '''<span class="mark">Open</span>'''</p>

<p>'''Before burning the image, it is recommended to rename the Linux image to orangepi.img or something shorter so that you can see the percentage of the burn progress when burning the image.'''</p>

<p>[[File:~~media/image50~~cm4-img50.png]]</p></li>

<li><p>Then check the '''<span class="mark">Force write to address</span>''' option</p>

<p>[[File:~~media/image68~~cm4-img68.png]]</p></li>

<li><p>Click the Execute button again to start burning the Linux image to eMMC on the development board</p>

<p>[[File:~~media/image69~~cm4-img69.png]]</p></li>

<li><p>The following figure shows the display log after the Linux image is burned</p>

<p>[[File:~~media/image70~~cm4-img70.png]]</p></li>

<li><p>After the Linux image is burned into eMMC, the Linux system automatically starts</p></li></ol>

</li></ol>

<li><p>M.2 2230 SSD specifications are as follows</p>

<p>[[File:~~media/image71~~cm4-img71.png]]</p></li>

<li><p>M.2 2242 SSDS are described as follows</p>

<p>[[File:~~media/image72~~cm4-img72.png]]</p></li></ol>

</li>

<li><p>Insert the NVMe SSD into the M.2 PCIe port on the development board and secure it</p>

<p>[[File:~~media/image73~~cm4-img73.png]]</p></li>

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

<p>[[File:~~media/image74~~cm4-img74.png]]</p></li>

<li><p>Then you need to prepare a good quality USB2.0 public-to-public data cable</p>

[[File:~~media/image18~~cm4-img18.png]]

</div></li>

[[File:~~media/image31~~cm4-img31.png]]

</div></li>

[[File:~~media/image32~~cm4-img32.png]]

</div>

<li><p>Download the compressed Linux operating system image file you want to burn from the [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-CM4-1.html '''Orange Pi's data download page'''], and then use the decompression software to decompress it. In the decompressed file, the file ending with "'''.img''' "is the image file of the operating system, and the size is generally more than 2GB</p></li>

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

<p>[[File:~~media/image33~~cm4-img33.png]]</p></li>

<li><p>Open '''DriverInstall.exe''' and install the Rockchip driver as follows</p>

<li><p>Click the "'''Driver Installation'''" button</p>

<p>[[File:~~media/image34~~cm4-img34.png]]</p></li>

<li><p>Wait for a period of time, the pop-up window will prompt > "'''Driver installation successful'''", and then click the > "'''OK'''" button</p>

<p>[[File:~~media/image35~~cm4-img35.png]]</p></li></ol>

</li>

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

<p>[[File:~~media/image36~~cm4-img36.png]]</p></li>

<li><p>After opening the '''RKDevTool''' burning tool, because the computer has not connected to the development board through the USB2.0 public-to-public data cable at this time, the lower left corner will indicate "'''No device found'''".</p>

<p>[[File:~~media/image37~~cm4-img37.png]]</p></li>

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

<li><p>First, connect the development board to the Windows computer > through the USB2.0 male-to-public data cable. The position of > the USB2.0 burning interface on the development board is shown > in the figure below</p>

<p>[[File:~~media/image38~~cm4-img38.png]]</p></li>

<li><p>Ensure that no TF card is inserted into the development board > and no power supply is connected</p></li>

<li><p>Then press and hold the MaskROM button on the development board. > The position of the MaskROM button on the development board is > shown as follows:</p>

<p>[[File:~~media/image39~~cm4-img39.png]]</p></li>

<li><p>Then connect the Type-C interface to the development board, and > power on, and then you can release the MaskROM button</p>

<p>[[File:~~media/image40~~cm4-img40.png]]</p></li>

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

<p>[[File:~~media/image41~~cm4-img41.png]]</p></li>

<li><p>Then place the mouse cursor on the field below</p>

[[File:~~media/image63~~cm4-img63.png]]

</div></li>

<li><p>Then click the right mouse button to pop up the selection > interface as shown in the following figure</p>

<p>[[File:~~media/image43~~cm4-img43.png]]</p></li>

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

<p>[[File:~~media/image44~~cm4-img44.png]]</p></li>

<li><p>Then go to the previously downloaded '''MiniLoader''' folder, > select the '''rk356x_linux_pcie.cfg''' configuration file, and > click '''Open'''</p>

[[File:~~media/image75~~cm4-img75.png]]

</div></li>

<li><p>Then click '''<span class="mark">OK</span>'''</p>

<p>[[File:~~media/image76~~cm4-img76.png]]</p></li>

<li><p>Then click on the location shown in the image below</p>

<p>[[File:~~media/image77~~cm4-img77.png]]</p></li>

<li><p>Select '''MiniLoaderAll.bin''' from the '''MiniLoader''' folder > downloaded earlier, and then click '''<span class="mark">Open</span>'''</p>

[[File:~~media/image48~~cm4-img48.png]]

</div></li>

<li><p>Then click on the location shown in the image below</p>

<p>[[File:~~media/image78~~cm4-img78.png]]</p></li>

<li><p>Then go to the previously downloaded '''MiniLoader''' folder, > select '''rkspi_loader.img''', and click '''<span class="mark">Open</span>'''</p>

[[File:~~media/image79~~cm4-img79.png]]

</div></li>

<li><p>Then click on the location shown in the image below</p>

<p>[[File:~~media/image80~~cm4-img80.png]]</p></li>

<li><p>Then select the path of the Linux image you want to burn and > click '''<span class="mark">Open</span>'''</p>

<p>'''Before burning the image, it is recommended to rename the Linux image to orangepi.img or something shorter so that you can see the percentage of the burn progress when burning the image.'''</p>

<p>[[File:~~media/image50~~cm4-img50.png]]</p></li>

<li><p>Then select '''<span class="mark">Force Write to address</span>'''</p>

<p>[[File:~~media/image81~~cm4-img81.png]]</p></li>

<li><p>Click the Run button again to start burning the Linux image to > the SSD</p>

<p>[[File:~~media/image82~~cm4-img82.png]]</p></li>

<li><p>The display log of the S.lux image after burning is shown in the > following figure</p>

<p>[[File:~~media/image83~~cm4-img83.png]]</p>

<p>'''If you have problems with burning, please clear the SPIFlash first and then burn the test. For instructions on how to clear SPIFlash, refer to the section on [[\l|how to clear SPIFlash using RKDevTool]].'''</p></li>

<li><p>After the image is burned, the Linux system in the SPIFlash+PCIe > SSD automatically starts. If it does not start properly, power > it on again.</p></li></ol>

<li><p>M.2 2230 SSDS are as follows</p>

<p>[[File:~~media/image71~~cm4-img71.png]]</p></li>

<li><p>M.2 2242 SSDS are described as follows</p>

<p>[[File:~~media/image72~~cm4-img72.png]]</p></li></ol>

</li>

<li><p>Insert the NVMe SSD into the M.2 PCIe port on the development board and secure it</p>

<p>[[File:~~media/image73~~cm4-img73.png]]</p></li>

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

<p>[[File:~~media/image74~~cm4-img74.png]]</p></li>

<li><p>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 [[\l|'''the method of burning a Linux image to a TF card''' '''based on a Windows PC''']] and '''[[\l|the method of burning a Linux image to a TF card based on an Ubuntu PC]].'''</p></li>

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

[[File:~~media/image84~~cm4-img84.png]]

</div>

[[File:~~media/image85~~cm4-img85.png]]

</div>

[[File:~~media/image86~~cm4-img86.png]]

</div>

<li><p>M.2 2230 SSDS are as follows</p>

<p>[[File:~~media/image71~~cm4-img71.png]]</p></li>

<li><p>M.2 2242 SSDS are described as follows</p>

<p>[[File:~~media/image72~~cm4-img72.png]]</p></li></ol>

</li>

<li><p>Insert the NVMe SSD into the M.2 PCIe port on the development board and secure it</p>

<p>[[File:~~media/image73~~cm4-img73.png]]</p></li>

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

<p>[[File:~~media/image74~~cm4-img74.png]]</p></li>

<li><p>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 '''[[\l|the method of burning a Linux image to a TF card based on a Windows PC]]''' and '''[[\l|the method of burning a Linux image to a TF card based on an Ubuntu PC]].'''</p></li>

<li><p>After starting the Linux system in the TF card, please make sure that the NVMe SSD has been properly recognized by Linux on the development board. If the NVMe SSD is correctly identified, run the '''sudo fdisk -l''' command to view information about the '''nvme'''</p>

[[File:~~media/image87~~cm4-img87.png]]

</div>

[[File:~~media/image88~~cm4-img88.png]]

</div>

[[File:~~media/image89~~cm4-img89.png]]

</div>

[[File:~~media/image90~~cm4-img90.png]]

</div>

<li><p>Open '''rkspi_loader.img'''. The following interface is displayed:</p>

<p>[[File:~~media/image91~~cm4-img91.png]]</p></li>

<li><p>Then click '''Select target'''</p></li></ol>

[[File:~~media/image92~~cm4-img92.png]]

</div>

[[File:~~media/image93~~cm4-img93.png]]

</div>

[[File:~~media/image94~~cm4-img94.png]]

</div>

[[File:~~media/image95~~cm4-img95.png]]

</div>

[[File:~~media/image96~~cm4-img96.png]]

</div>

[[File:~~media/image97~~cm4-img97.png]]

</div>

[[File:~~media/image98~~cm4-img98.png]]

</div>

[[File:~~media/image99~~cm4-img99.png]]

</div>

[[File:~~media/image100~~cm4-img100.png]]

</div>

[[File:~~media/image101~~cm4-img101.png]]

</div>

[[File:~~media/image102~~cm4-img102.png]]

</div>

[[File:~~media/image92~~cm4-img92.png]]

</div>

[[File:~~media/image93~~cm4-img93.png]]

</div>

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

[[File:~~media/image103~~cm4-img103.png]]

[[File:~~media/image104~~cm4-img104.png]]

</div>

[[File:~~media/image105~~cm4-img105.png]]

</div>

[[File:~~media/image106~~cm4-img106.png]]

</div>

<li>The burning process is shown as follows:</li></ol>

[[File:~~media/image107~~cm4-img107.png]]

[[File:~~media/image108~~cm4-img108.png]]

</div>

<li>The display after burning is as follows:</li></ol>

[[File:~~media/image109~~cm4-img109.png]]

[[File:~~media/image110~~cm4-img110.png]]

</div>

<li>Then enter the password orangepi for Linux and click > '''Authenticate'''</li></ol>

[[File:~~media/image111~~cm4-img111.png]]

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

<p>[[File:~~media/image112~~cm4-img112.png]]</p></li>

<li><p>Then select NVMe SSD</p></li></ol>

[[File:~~media/image113~~cm4-img113.png]]

</div>

[[File:~~media/image114~~cm4-img114.png]]

</div>

[[File:~~media/image115~~cm4-img115.png]]

</div>

<li><p>Then drag the capacity to the maximum as shown in the image below</p>

<p>[[File:~~media/image116~~cm4-img116.png]]</p></li>

<li><p>Then click '''Resize/Move'''</p>

<p>[[File:~~media/image117~~cm4-img117.png]]</p></li>

<li><p>Then click on the green'''√''' in the picture below</p>

<p>[[File:~~media/image118~~cm4-img118.png]]</p></li>

<li><p>Then click '''Apply'''</p>

<p>[[File:~~media/image119~~cm4-img119.png]]</p></li>

<li><p>Then click '''Close''' to close it</p>

<p>[[File:~~media/image120~~cm4-img120.png]]</p></li></ol>

<li><p>Upload the Linux image file to the Linux operating system on the > development board</p></li>

<li><p>Then use balenaEtcher to burn</p>

<p>[[File:~~media/image121~~cm4-img121.png]]</p></li>

<li><p>'''There is no need to manually expand the capacity after burning > the image using this method. The first startup will > automatically expand the capacity.'''</p></li></ol>

</li></ol>

[[File:~~media/image18~~cm4-img18.png]]

</div></li>

[[File:~~media/image31~~cm4-img31.png]]

</div></li>

[[File:~~media/image32~~cm4-img32.png]]

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

[[File:~~media/image122~~cm4-img122.png]]

</div></li>

<li><p>The first image is dedicated to HDMI display and supports 4K > display, if you do not use LCD screen, please download the > image without lcd</p></li>

<li><p>If you want to use an lcd screen, select an image with lcd</p>

<p>[[File:~~media/image123~~cm4-img123.png]]</p></li></ol>

</li></ol>

</li>

<li><p>Then use the decompression software to decompress the compressed package of the downloaded Android image. In the decompressed file, the file ending with ".img "is the Android image file, the size of which is more than 1GB</p></li>

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

<p>[[File:~~media/image33~~cm4-img33.png]]</p></li>

<li><p>Open '''DriverInstall.exe''' and install the SWick micro driver as follows</p>

<li><p>Click the "'''Driver Installation'''" button</p>

<p>[[File:~~media/image34~~cm4-img34.png]]</p></li>

<li><p>Wait for a period of time, the pop-up window will prompt "'''Driver installation successful'''", and then click the "'''OK'''" button</p>

<p>[[File:~~media/image35~~cm4-img35.png]]</p></li></ol>

</li>

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

<p>[[File:~~media/image36~~cm4-img36.png]]</p></li>

<li><p>After opening the '''RKDevTool''' burning tool, because the computer has not connected to the development board through the USB2.0 public-to-public data cable at this time, the lower left corner will display "'''No device found'''".</p>

<p>[[File:~~media/image37~~cm4-img37.png]]</p></li>

<li><p>Then start burning Android image to TF card</p>

<li><p>First, connect the development board to the Windows computer > through the USB2.0 male-to-public data cable. The position of > the USB2.0 burning interface on the development board is shown > in the figure below</p>

<p>[[File:~~media/image38~~cm4-img38.png]]</p></li>

<li><p>Then make sure that no TF card is inserted into the development > board and no power is connected</p></li>

<li><p>Then press and hold the MaskROM button on the development board. > The position of the MaskROM button on the development board is > shown as follows:</p>

<p>[[File:~~media/image39~~cm4-img39.png]]</p></li>

<li><p>Connect the development board to the Type-C port, and power on > the development board</p>

<p>[[File:~~media/image40~~cm4-img40.png]]</p></li>

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

<p>[[File:~~media/image41~~cm4-img41.png]]</p></li>

<li><p>Then insert the TF card into the development board</p></li>

<li><p>Then select '''<span class="mark">Advanced features</span>'''</p>

<p>[[File:~~media/image124~~cm4-img124.png]]</p></li>

<li><p>Then click on the location shown in the image below</p>

<p>[[File:~~media/image125~~cm4-img125.png]]</p></li>

<li><p>Select '''MiniLoaderAll.bin''' from the '''MiniLoader''' folder > downloaded earlier and click Open</p>

[[File:~~media/image48~~cm4-img48.png]]

</div></li>

<li><p>Then click '''<span class="mark">Download</span>'''</p>

<p>[[File:~~media/image126~~cm4-img126.png]]</p></li>

<li><p>The following figure is displayed after '''MiniLoaderAll.bin''' is > downloaded</p>

<p>[[File:~~media/image127~~cm4-img127.png]]</p></li>

<li><p>Then select the storage device as '''<span class="mark">SD</span>''' and click > '''<span class="mark">Switch storage</span>'''</p>

[[File:~~media/image128~~cm4-img128.png]]

</div></li>

[[File:~~media/image129~~cm4-img129.png]]

</div></li>

<li><p>Then click on the "'''Upgrade Firmware'''" section of the > burning tool</p>

<p>[[File:~~media/image130~~cm4-img130.png]]</p></li>

<li><p>Then click the "'''Firmware'''" button to select the path of the > Android image that you want to burn</p>

<p>[[File:~~media/image131~~cm4-img131.png]]</p></li>

<li><p>Finally, click the "'''Upgrade'''" button to start burning. The > log in the burning process is shown below. The Android system > will start automatically after the burning is complete.</p></li></ol>

</li></ol>

[[File:~~media/image132~~cm4-img132.png]]

</div>

[[File:~~media/image18~~cm4-img18.png]]

</div></li>

[[File:~~media/image122~~cm4-img122.png]]

</div></li>

<li><p>The first image is dedicated to HDMI display and supports 4K > display. If you don’t use LCD screen, please download the > image without lcd</p></li>

<li><p>If you want to use an LCD screen, please choose the image > with LCD</p>

<p>[[File:~~media/image123~~cm4-img123.png]]</p></li></ol>

</li></ol>

</li>

<li><p>Then use decompression software to decompress the compressed package of the downloaded Android image. In the decompressed file, the file ending with ".img" is the Android image file, with a size of more than 1GB.</p></li>

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

<p>[[File:~~media/image33~~cm4-img33.png]]</p></li>

<li><p>Open '''DriverInstall.exe''' and install the Rockchip microdriver as follows</p>

<li><p>Click the "'''Driver Installation'''" button</p>

<p>[[File:~~media/image34~~cm4-img34.png]]</p></li>

<li><p>After waiting for a period of time, a window will pop up prompting "'''Driver installation successful'''", then click the "'''OK'''" button.</p>

<p>[[File:~~media/image35~~cm4-img35.png]]</p></li></ol>

</li>

<li><p>Then unzip '''RKDevTool_Release_v3.15.zip'''. This software does not need to be installed. Just find '''RKDevTool''' in the unzipped folder and open it.</p>

<p>[[File:~~media/image36~~cm4-img36.png]]</p></li>

<li><p>After opening the '''RKDevTool''' burning tool, because the computer has not connected to the development board through the USB2.0 male-to-male data cable at this time, the lower left corner will prompt "'''No device found'''"</p>

<p>[[File:~~media/image37~~cm4-img37.png]]</p></li>

<li><p>Then start burning the Android image into eMMC</p>

<li><p>First, connect the development board to the Windows computer > through a USB2.0 male-to-male data cable. The location of the > development board’s USB2.0 burning interface is as shown in > the figure below.</p>

<p>[[File:~~media/image38~~cm4-img38.png]]</p></li>

<li><p>Then make sure that the development board is not inserted into > the TF card and not connected to the power supply</p></li>

<li><p>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:</p>

<p>[[File:~~media/image39~~cm4-img39.png]]</p></li>

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

<p>[[File:~~media/image40~~cm4-img40.png]]</p></li>

<li><p>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'''"</p>

<p>[[File:~~media/image41~~cm4-img41.png]]</p></li>

<li><p>Then please select '''<span class="mark">advanced functions</span>'''</p>

<p>[[File:~~media/image124~~cm4-img124.png]]</p></li>

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

<p>[[File:~~media/image125~~cm4-img125.png]]</p></li>

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

[[File:~~media/image48~~cm4-img48.png]]

</div></li>

<li><p>Then click '''<span class="mark">Download</span>'''</p>

<p>[[File:~~media/image126~~cm4-img126.png]]</p></li>

<li><p>The display after downloading '''MiniLoaderAll.bin''' is shown in the figure below</p>

<p>[[File:~~media/image133~~cm4-img133.png]]</p></li>

<li><p>Then select the storage device as '''EMMC''', and then click '''<span class="mark">Switch Storage</span>'''</p>

<p>[[File:~~media/image134~~cm4-img134.png]]</p></li>

<li><p>The successful switching is displayed as shown below</p>

<p>[[File:~~media/image135~~cm4-img135.png]]</p></li>

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

<p>[[File:~~media/image130~~cm4-img130.png]]</p></li>

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

<p>[[File:~~media/image131~~cm4-img131.png]]</p></li>

<li><p>Finally, click the "'''Upgrade'''" button to start burning. The > log during the burning process is as shown below. After > burning is completed, the Android system will start > automatically.</p>

[[File:~~media/image132~~cm4-img132.png]]

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

[[File:~~media/image122~~cm4-img122.png]]

</div></li>

<li><p>The first image is specifically used for HDMI display. It > supports 4K display. If you do not use the LCD screen, > download the image without LCD</p></li>

<li><p>If you want to use the LCD screen, select the image with LCD</p>

<p>[[File:~~media/image123~~cm4-img123.png]]</p></li></ol>

</li></ol>

</li>

<li><p>Then use the decompression software to decompress the downloaded Android image compressed package. In the files that are decompressed, the file ending with ".img" is the Android image file with a memory of more than 1GB</p></li>

<li><p>Then use the decompression software to decompress the '''SDDiskTool_v1.72.zip'''. This software does not need to be installed. Find the '''SD_Firmware_Tool.exe''' in the unzipped folder and open it.</p>

<p>[[File:~~media/image136~~cm4-img136.png]]</p></li>

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

<p>[[File:~~media/image137~~cm4-img137.png]]</p></li>

<li><p>After confirming the drive letter, you can format the TF card first and click the '''<span class="mark">Recover Disk</span>''' button in '''SDDiskTool'''. You can also use the '''SD Card Formatter''' mentioned earlier to format the TF card</p>

<p>[[File:~~media/image138~~cm4-img138.png]]</p></li>

<li><p>Then start writing the Android image to the TF card</p>

<li><p>Then select the path of the Android firmware in the "'''Select > Upgrade Firmware'''" column</p></li>

<li><p>Finally, click the "'''Start Creating'''" button to start > burning.</p>

<p>[[File:~~media/image139~~cm4-img139.png]]</p></li></ol>

</li>

<li><p>After the burning is completed, the display is as shown below, and then you can exit SDDiskTool</p>

<p>[[File:~~media/image140~~cm4-img140.png]]</p></li>

<li><p>Then pull out the TF card from the computer and insert it into the development board. After the development board is powered on, it will automatically start burning the Android image in the TF card into the eMMC of the development board.</p></li>

<li><p>If the development board is connected to an HDMI display, you can also see the progress bar of burning the Android image to eMMC from the HDMI display</p>

<p>[[File:~~media/image141~~cm4-img141.png]]</p></li>

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

<p>[[File:~~media/image142~~cm4-img142.png]]</p></li></ol>

<li><p>The M.2 2230 SSD is as follows</p>

<p>[[File:~~media/image71~~cm4-img71.png]]</p></li>

<li><p>The M.2 2242 specification SSD is as follows</p>

<p>[[File:~~media/image72~~cm4-img72.png]]</p></li></ol>

</li>

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

<p>[[File:~~media/image73~~cm4-img73.png]]</p></li>

<li><p>Please make sure that the SPI Flash has been attached to the development board. The location of the SPI Flash on the development board is as shown in the picture below. No other settings are required before starting burning</p>

<p>[[File:~~media/image74~~cm4-img74.png]]</p></li>

<li><p>You also need to prepare a good quality USB2.0 male-to-male data cable</p>

[[File:~~media/image18~~cm4-img18.png]]

</div></li>

[[File:~~media/image122~~cm4-img122.png]]

</div></li>

<li><p>The image without lcd is specially used for HDMI display and > supports 4K display. If you don’t use the LCD screen, > please download the image without lcd</p></li>

<li><p>If you want to use an LCD screen, please choose the image > with lcd</p>

<p>[[File:~~media/image143~~cm4-img143.png]]</p></li></ol>

</li></ol>

</li>

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

<p>[[File:~~media/image33~~cm4-img33.png]]</p></li>

<li><p>The steps to install the Rockchip driver after opening '''DriverInstall.exe''' are as follows</p>

<li><p>Click the "'''Driver Installation'''" button</p>

<p>[[File:~~media/image34~~cm4-img34.png]]</p></li>

<li><p>After waiting for a period of time, a window will pop up prompting "'''Driver installation successful'''", then click the "'''OK'''" button</p>

<p>[[File:~~media/image35~~cm4-img35.png]]</p></li></ol>

</li>

<li><p>Then unzip '''RKDevTool_Release_v3.15.zip'''. This software does not need to be installed. Just find '''RKDevTool''' in the unzipped folder and open it</p>

<p>[[File:~~media/image36~~cm4-img36.png]]</p></li>

<li><p>After opening the '''RKDevTool''' burning tool, because the computer has not yet connected to the development board through the USB2.0 male-to-male data cable, a message "'''No device found'''" will appear in the lower left corner.</p>

<p>[[File:~~media/image37~~cm4-img37.png]]</p></li>

<li><p>Then start burning the Android image to SPIFlash+NVMe SSD</p>

<li><p>First, connect the development board to the Windows computer > through a USB2.0 male-to-male data cable. The location of the > USB2.0 programming port on the development board is as shown > in the figure below.</p>

<p>[[File:~~media/image38~~cm4-img38.png]]</p></li>

<li><p>Make sure that the development board is not inserted into the TF > card and not connected to the power supply</p></li>

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

<p>[[File:~~media/image39~~cm4-img39.png]]</p></li>

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

<p>[[File:~~media/image40~~cm4-img40.png]]</p></li>

<li><p>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 devic'''e "</p>

<p>[[File:~~media/image41~~cm4-img41.png]]</p></li>

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

<p>[[File:~~media/image130~~cm4-img130.png]]</p></li>

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

<p>[[File:~~media/image131~~cm4-img131.png]]</p></li>

<li><p>Finally, click the "'''Upgrade'''" button to start burning. The > burning process is shown in the figure below. You can see that > the firmware will be burned into SPIFlash first, and then > burned into PCIE. The Android system will start automatically > after burning.</p>

<p>[[File:~~media/image144~~cm4-img144.png]]</p></li></ol>

</li></ol>

<li><p>The location of SPI Flash on the development board is shown in the figure below</p>

<p>[[File:~~media/image74~~cm4-img74.png]]</p></li>

<li><p>First of all, you need to prepare a good quality USB2.0 male-to-male data cable</p>

[[File:~~media/image18~~cm4-img18.png]]

</div></li>

[[File:~~media/image145~~cm4-img145.png]]

</div></li>

[[File:~~media/image146~~cm4-img146.png]]

</div>

</li>

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

<p>[[File:~~media/image33~~cm4-img33.png]]</p></li>

<li><p>The steps to install the Rockchip driver after opening '''DriverInstall.exe''' are as follows</p>

<li><p>Click the "'''Driver Installation'''" button</p>

<p>[[File:~~media/image34~~cm4-img34.png]]</p></li>

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

<p>[[File:~~media/image35~~cm4-img35.png]]</p></li></ol>

</li>

<li><p>Then unzip '''RKDevTool_Release_v3.15.zip'''. This software does not need to be installed. Just find '''RKDevTool''' in the unzipped folder and open it.</p>

<p>[[File:~~media/image36~~cm4-img36.png]]</p></li>

<li><p>After opening the '''RKDevTool'''burning tool, because the computer has not yet connected to the development board through the USB2.0 male-to-male data cable, a message "'''No device found'''" will appear in the lower left corner.</p>

<p>[[File:~~media/image37~~cm4-img37.png]]</p></li>

<li><p>Then you can start to clear the contents of the SPI FLASH</p>

<li><p>First, connect the development board to the Windows computer > through a USB2.0 male-to-male data cable. The location of the > USB2.0 programming port on the development board is as shown > in the figure below.</p>

<p>[[File:~~media/image38~~cm4-img38.png]]</p></li>

<li><p>Make sure that the development board is not inserted into the TF > card and not connected to the power supply</p></li>

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

<p>[[File:~~media/image39~~cm4-img39.png]]</p></li>

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

<p>[[File:~~media/image40~~cm4-img40.png]]</p></li>

<li><p>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'''"</p>

<p>[[File:~~media/image41~~cm4-img41.png]]</p></li>

<li><p>Then please select '''<span class="mark">advanced functions</span>'''</p>

<p>[[File:~~media/image124~~cm4-img124.png]]</p></li>

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

<p>[[File:~~media/image125~~cm4-img125.png]]</p></li>

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

[[File:~~media/image48~~cm4-img48.png]]

</div></li>

<li><p>Then click '''<span class="mark">Download</span>'''</p>

<p>[[File:~~media/image126~~cm4-img126.png]]</p></li>

<li><p>The display after downloading '''MiniLoaderAll.bin''' is shown in the figure below</p>

<p>[[File:~~media/image133~~cm4-img133.png]]</p></li>

<li><p>Then select the storage device as '''SPINOR'''</p>

<p>[[File:~~media/image147~~cm4-img147.png]]</p></li>

<li><p>Then click '''<span class="mark">switch storage</span>'''</p>

<p>[[File:~~media/image148~~cm4-img148.png]]</p></li>

<li><p>Then click '''<span class="mark">Erase All</span>''' and it will start erasing SPIFlash.</p>

<p>[[File:~~media/image149~~cm4-img149.png]]</p></li>

<li><p>The display log after erasing SPIFlash is shown in the figure below</p>

<p>[[File:~~media/image150~~cm4-img150.png]]</p></li></ol>

</li></ol>

[[File:~~media/image18~~cm4-img18.png]]

</div></li>

[[File:~~media/image145~~cm4-img145.png]]

</div></li>

[[File:~~media/image146~~cm4-img146.png]]

</div>

</li>

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

<p>[[File:~~media/image33~~cm4-img33.png]]</p></li>

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

<li><p>Click the "'''Driver Installation'''" button</p>

<p>[[File:~~media/image34~~cm4-img34.png]]</p></li>

<li><p>After waiting for a period of time, a window will pop up > prompting "'''Driver installation successful'''", then click > the "'''OK'''" button.</p>

<p>[[File:~~media/image35~~cm4-img35.png]]</p></li></ol>

</li>

<li><p>Then unzip '''RKDevTool_Release_v3.15.zip'''. This software does not need to be installed. Just find '''RKDevTool''' in the unzipped folder and open it.</p>

<p>[[File:~~media/image36~~cm4-img36.png]]</p></li>

<li><p>After opening the '''RKDevTool''' burning tool, because the computer has not connected to the development board through the USB2.0 male-to-male data cable at this time, the lower left corner will prompt "'''No device found'''"</p>

<p>[[File:~~media/image37~~cm4-img37.png]]</p></li>

<li><p>Then you can start to clear the content in eMMC</p>

<li><p>First, connect the development board to the Windows computer > through a USB2.0 male-to-male data cable. The location of the > USB2.0 programming port on the development board is as shown > in the figure below.</p>

<p>[[File:~~media/image38~~cm4-img38.png]]</p></li>

<li><p>Make sure that the development board is not inserted into the TF > card and not connected to the power supply</p></li>

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

<p>[[File:~~media/image39~~cm4-img39.png]]</p></li>

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

<p>[[File:~~media/image40~~cm4-img40.png]]</p></li>

<li><p>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'''"</p>

<p>[[File:~~media/image41~~cm4-img41.png]]</p></li>

<li><p>Then please select '''<span class="mark">advanced functions</span>'''</p>

<p>[[File:~~media/image124~~cm4-img124.png]]</p></li>

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

<p>[[File:~~media/image125~~cm4-img125.png]]</p></li>

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

[[File:~~media/image48~~cm4-img48.png]]

</div></li>

<li><p>Then click '''<span class="mark">Download</span>'''</p>

<p>[[File:~~media/image126~~cm4-img126.png]]</p></li>

<li><p>The display after downloading '''MiniLoaderAll.bin''' is shown in the figure below</p>

<p>[[File:~~media/image133~~cm4-img133.png]]</p></li>

<li><p>Then select the storage device as '''eMMC'''</p>

<p>[[File:~~media/image151~~cm4-img151.png]]</p></li>

<li><p>Then click '''<span class="mark">switch storage</span>'''</p>

<p>[[File:~~media/image152~~cm4-img152.png]]</p></li>

<li><p>Then click '''<span class="mark">Erase All</span>''' to start erasing the eMMC.</p>

<p>[[File:~~media/image153~~cm4-img153.png]]</p></li>

<li><p>The display log after erasing eMMC is as shown below</p>

<p>[[File:~~media/image154~~cm4-img154.png]]</p></li></ol>

</li></ol>

<li><p>First install the Orange Pi CM4 core board on the base board</p>

<p>[[File:~~media/image155~~cm4-img155.png]]</p></li>

<li><p>Then insert the TF card with the burned image into the TF card slot of the Orange Pi development board.</p></li>

<li><p>The development board has a Micro HDMI interface, and the development board can be connected to a TV or HDMI display through a Micro HDMI to HDMI cable. If you have purchased an LCD screen, you can also use the LCD screen to display the system interface of the development board</p></li>

[[File:~~media/image156~~cm4-img156.png]]

</div>

<li><p>The corresponding relationship between the GND, RXD and TXD pins of the development board’s debugging serial port is as shown in the figure below</p>

<p>[[File:~~media/image157~~cm4-img157.png]]</p></li>

<li><p>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 Dupont lines</p>

[[File:~~media/image158~~cm4-img158.png]]

</div>

<p>test@test:~$ '''sudo putty'''</p></li>

<li><p>After executing the putty command, the following interface will pop up</p>

<p>[[File:~~media/image159~~cm4-img159.png]]</p></li>

<li><p>First select the serial port setting interface</p>

<p>[[File:~~media/image160~~cm4-img160.png]]</p></li>

<li><p>Then set the parameters of the serial port</p>

[[File:~~media/image161~~cm4-img161.png]]

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

[[File:~~media/image162~~cm4-img162.png]]

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

</li>

<li><p>After starting the development board, you can see the Log information output by the system from the open serial terminal.</p>

<p>[[File:~~media/image163~~cm4-img163.png]]</p></li></ol>

<p>[https://mobaxterm.mobatek.net/ '''https://mobaxterm.mobatek.net''']</p></li>

<li><p>After entering the MobaXterm download page, click '''GET XOBATERM > NOW!'''</p>

<p>[[File:~~media/image164~~cm4-img164.png]]</p></li>

<li><p>Then choose to download the Home version</p>

<p>[[File:~~media/image165~~cm4-img165.png]]</p></li>

<li><p>Then select the Portable version. There is no need to install it after downloading. You can open it directly and use it.</p>

<p>[[File:~~media/image166~~cm4-img166.png]]</p></li></ol>

</li>

<li><p>After downloading, use decompression software to decompress the downloaded compressed package to get the MobaXterm executable software, and then double-click to open it.</p>

<p>[[File:~~media/image167~~cm4-img167.png]]</p></li>

<li><p>After opening the software, the steps to set up the serial port connection are as follows</p>

[[File:~~media/image168~~cm4-img168.png]]

</div>

[[File:~~media/image169~~cm4-img169.png]]

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

[[File:~~media/image170~~cm4-img170.png]]

</div>

<li><p>The black DuPont wire needs to be plugged into the GND pin of > the 40pin interface</p></li>

<li><p>The position of the 40Pin interface 5V pin and GND pin in the > development board is shown in the figure below, '''Remember not > to reverse'''</p>

<p>[[File:~~media/image171~~cm4-img171.png]]</p></li></ol>

</li></ol>

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

<p>[[File:~~media/image172~~cm4-img172.png]]</p></li>

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

<p>orangepi@orangepi:~$ '''sudo auto_login_cli.sh root'''</p></li>

[[File:~~media/image173~~cm4-img173.png]]

</div></li>

[[File:~~media/image174~~cm4-img174.png]]

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

<p>orangepi@orangepi:~$ '''sudo desktop_login.sh root'''</p></li>

<li><p>Then restart the system, it will automatically use the root user to log in to the desktop</p>

<p>[[File:~~media/image175~~cm4-img175.png]]</p>

<p>'''Note that if you use the root user to log in to the desktop system, you cannot use pulseaudio in the upper right corner to manage audio devices.'''</p>

<p>'''Also note that this is not a bug, since pulseaudio is not allowed to run as root.'''</p></li>

[[File:~~media/image176~~cm4-img176.png]]

</div></li>

[[File:~~media/image177~~cm4-img177.png]]

</div></li>

<p>orangepi@orangepi:~$ '''nmtui'''</p></li>

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

<p>[[File:~~media/image178~~cm4-img178.png]]</p></li>

<li><p>Select '''Activate a connect''' and press Enter</p>

<p>[[File:~~media/image179~~cm4-img179.png]]</p></li>

<li><p>Then you can see all the searched WIFI hotspots</p>

[[File:~~media/image180~~cm4-img180.png]]

</div></li>

[[File:~~media/image181~~cm4-img181.png]]

</div></li>

[[File:~~media/image182~~cm4-img182.png]]

</div></li>

[[File:~~media/image183~~cm4-img183.png]]

</div></li>

<li><p>Click the network configuration icon in the upper right corner of the desktop (please do not connect the network cable when testing WIFI)</p>

<p>[[File:~~media/image184~~cm4-img184.png]]</p></li>

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

<p>[[File:~~media/image185~~cm4-img185.png]]</p></li>

<li><p>Then enter the password of the WIFI hotspot, and then click '''Connect''' to start connecting to WIFI</p>

<p>[[File:~~media/image186~~cm4-img186.png]]</p></li>

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

<p>[[File:~~media/image187~~cm4-img187.png]]</p></li>

<li><p>If you can open other web pages after opening the browser, it means the WIFI connection is normal</p>

<p>[[File:~~media/image188~~cm4-img188.png]]</p></li></ol>

<p>orangepi@orangepi:~$ '''nmtui'''</p></li>

<li><p>Then select '''Edit a connection''' and press Enter</p>

<p>[[File:~~media/image189~~cm4-img189.png]]</p></li>

<li><p>Then select the network interface for which a static IP address needs to be set. For example, to set the static IP address of the '''Ethernet''' interface, select '''Wired connection 1'''.</p>

<p>[[File:~~media/image190~~cm4-img190.png]]</p></li>

<li><p>Then select '''Edit''' via the '''Tab''' key and press the Enter key</p>

<p>[[File:~~media/image191~~cm4-img191.png]]</p></li>

<li><p>Then use the Tab key to move the cursor to the'''<Automatic>''' position shown in the figure below to configure IPv4</p>

<p>[[File:~~media/image192~~cm4-img192.png]]</p></li>

<li><p>Then press Enter, select '''Manual''' through the up and down arrow keys, and then press Enter to confirm.</p>

<p>[[File:~~media/image193~~cm4-img193.png]]</p></li>

<li><p>The display after selection is as shown below</p>

<p>[[File:~~media/image194~~cm4-img194.png]]</p></li>

<li><p>Then move the cursor to '''<Show>''' via the Tab key</p>

<p>[[File:~~media/image195~~cm4-img195.png]]</p></li>

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

<p>[[File:~~media/image196~~cm4-img196.png]]</p></li>

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

<p>[[File:~~media/image197~~cm4-img197.png]]</p></li>

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

<p>[[File:~~media/image198~~cm4-img198.png]]</p></li>

<li><p>Then click '''<Back>''' to return to the previous level selection interface</p>

<p>[[File:~~media/image199~~cm4-img199.png]]</p></li>

<li><p>Then select '''Activate a connection''', then move the cursor to '''<OK>''', and finally click Enter</p>

<p>[[File:~~media/image200~~cm4-img200.png]]</p></li>

<li><p>Then select the network interface that needs to be set, such as '''Wired connection 1''', then move the cursor to '''<Deactivate>''', and press Enter to disable '''Wired connection 1'''</p>

<p>[[File:~~media/image201~~cm4-img201.png]]</p></li>

<li><p>Then please do not move the cursor, and then press the Enter key to re-enable '''Wired connection 1''', so that the static IP address set earlier will take effect</p>

<p>[[File:~~media/image202~~cm4-img202.png]]</p></li>

<li><p>Then you can exit nmtui through the '''<Back>'''and '''Quit''' buttons</p>

<p>[[File:~~media/image203~~cm4-img203.png]] [[File:~~media/image204~~cm4-img204.png]]</p></li>

<li><p>Then through '''ip addr show eth0''', you can see that the IP address of the network port has changed to the static IP address set earlier</p>

<p>orangepi@orangepi:~$ '''ip addr show eth0'''</p>

[[File:~~media/image205~~cm4-img205.png]]

</div>

[[File:~~media/image206~~cm4-img206.png]]

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

[[File:~~media/image207~~cm4-img207.png]]

</div>

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

[[File:~~media/image208~~cm4-img208.png]]

[[File:~~media/image209~~cm4-img209.png]]

</div></li>

[[File:~~media/image210~~cm4-img210.png]]

</div>

<li><p>Then choose to '''<span class="mark">save the password</span>''', and then click '''<span class="mark">OK</span>'''</p>

<p>[[File:~~media/image211~~cm4-img211.png]]</p></li>

<li><p>Then select '''<span class="mark">Always trust this host</span>''' and click '''<span class="mark">OK</span>'''</p></li></ol>

[[File:~~media/image212~~cm4-img212.png]]

</div>

[[File:~~media/image213~~cm4-img213.png]]

</div>

[[File:~~media/image214~~cm4-img214.png]]

</div>

[https://filezilla-project.org/download.php?type=client '''https://filezilla-project.org/download.php?type=client''']

[[File:~~media/image215~~cm4-img215.png]]

[[File:~~media/image216~~cm4-img216.png]]

</div>

[[File:~~media/image217~~cm4-img217.png]]

</div>

[[File:~~media/image218~~cm4-img218.png]]

</div>

[[File:~~media/image210~~cm4-img210.png]]

</div>

[[File:~~media/image219~~cm4-img219.png]]

</div>

[[File:~~media/image220~~cm4-img220.png]]

</div>

[[File:~~media/image221~~cm4-img221.png]]

</div>

[[File:~~media/image222~~cm4-img222.png]]

</div>

[[File:~~media/image223~~cm4-img223.png]]

</div></li>

<li><p>First open '''Display''' in '''Settings'''</p>

<p>[[File:~~media/image224~~cm4-img224.png]]</p></li>

<li><p>Then you can see the current resolution of the system</p>

<p>[[File:~~media/image225~~cm4-img225.png]]</p></li>

<li><p>Click the drop-down box of Resolution to see all resolutions currently supported by the display</p>

<p>[[File:~~media/image226~~cm4-img226.png]]</p></li>

<li><p>Then select the resolution you want to set and click Apply</p>

<p>[[File:~~media/image227~~cm4-img227.png]]</p></li>

<li><p>After the new resolution is set, select '''Keep the configuration'''</p>

<p>[[File:~~media/image228~~cm4-img228.png]]</p></li></ol>

<li><p>Click the Bluetooth icon in the upper right corner of the desktop</p>

<p>[[File:~~media/image229~~cm4-img229.png]]</p></li>

<li><p>Then select the adapter</p>

<p>[[File:~~media/image230~~cm4-img230.png]]</p></li>

<li><p>If prompted with the following interface, please select '''Yes'''.</p>

<p>[[File:~~media/image231~~cm4-img231.png]]</p></li>

<li><p>Then set the '''Visibility Setting''' to '''Always visible''' in the Bluetooth adapter setting interface, and then close it</p>

<p>[[File:~~media/image232~~cm4-img232.png]]</p></li>

<li><p>Then open the configuration interface of the Bluetooth device</p>

<p>[[File:~~media/image233~~cm4-img233.png]]</p></li>

<li><p>Click '''Search''' to start scanning for surrounding Bluetooth devices</p>

<p>[[File:~~media/image234~~cm4-img234.png]]</p></li>

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

<p>[[File:~~media/image235~~cm4-img235.png]]</p></li>

<li><p>When pairing, a pairing confirmation box will pop up in the upper right corner of the desktop. Just select '''Confirm''' to confirm. At this time, you also need to confirm on the mobile phone.</p>

<p>[[File:~~media/image236~~cm4-img236.png]]</p></li>

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

<p>[[File:~~media/image237~~cm4-img237.png]]</p></li>

<li><p>The interface for sending pictures is as follows</p>

<p>[[File:~~media/image238~~cm4-img238.png]]</p></li></ol>

support 2.4G WIFI+BT4.0

| [[File:~~media/image239~~cm4-img239.png]]

|-

| 2

support 2.4G +5G WIFI

| [[File:~~media/image240~~cm4-img240.png]]

|}

<p>TX bytes:23307 acl:0 sco:0 commands:125 errors:0</p></li>

<li><p>You can also see the Bluetooth icon on the desktop. Bluetooth is not turned on at this time, so a red '''x''' will be displayed</p>

<p>[[File:~~media/image241~~cm4-img241.png]]</p></li>

<li><p>Click '''Turn Bluetooth On''' to turn on Bluetooth</p>

<p>[[File:~~media/image242~~cm4-img242.png]]</p></li>

<li><p>The display after turning on Bluetooth is as follows</p>

<p>[[File:~~media/image243~~cm4-img243.png]]</p></li>

<li><p>For the Bluetooth test method, please refer to the section on [[\l|'''Bluetooth usage''']] and will not be repeated here.</p></li></ol>

<li><p>First, you need to prepare a USB camera as shown in the picture below or similar that supports UVC protocol, and then insert the USB camera into the USB interface of the Orange Pi development board</p>

<p>[[File:~~media/image16~~cm4-img16.png]]</p></li>

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

<p>orangepi@orangepi:~$ '''v4l2-ctl --list-devices'''</p>

<p>'''In addition, the serial number of the video is not necessarily video0, please refer to what you actually see.'''</p></li>

<li><p>In the desktop system, you can use Cheese to directly open the USB camera. The method of opening Cheese is as shown in the figure below:</p>

<p>[[File:~~media/image244~~cm4-img244.png]]</p>

<p>The interface after Cheese turns on the USB camera is as shown below:</p>

<p>[[File:~~media/image245~~cm4-img245.png]]</p></li>

<li><p>How to use fswebcam to test USB camera</p>

<li><p>First open the file manager</p>

<p>[[File:~~media/image246~~cm4-img246.png]]</p></li>

<li><p>Then find the following file (if there is no such audio file in the system, you can upload an audio file to the system yourself)</p>

[[File:~~media/image247~~cm4-img247.png]]

</div></li>

<li><p>Then select the audio.wav file, right-click and select open with vlc to start playing.</p>

<p>[[File:~~media/image248~~cm4-img248.png]]</p></li>

<li><p>How to switch between different audio devices such as HDMI playback and headphone playback</p>

<li><p>First open the volume control interface</p>

<p>[[File:~~media/image249~~cm4-img249.png]]</p></li>

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

<p>[[File:~~media/image250~~cm4-img250.png]]</p></li></ol>

</li></ol>

<li><p>First insert the headphones into the headphone jack of the development board</p>

<p>[[File:~~media/image251~~cm4-img251.png]]</p></li>

<li><p>Then you can use the '''aplay -l''' command to check the sound card devices supported by the Linux system. From the output below, we can see that '''card 0''' is the sound card device of rk809, which is the sound card device of the headset.</p>

<p>orangepi@orangepi:~$ '''aplay -l'''</p>

[[File:~~media/image252~~cm4-img252.png]]

</div></li>

<li><p>The following is the complete pin diagram of 40pin</p>

<p>[[File:~~media/image253~~cm4-img253.png]]</p></li>

<li><p>The table below is the picture of the left half of the complete > table above, so you can see it clearly</p>

<p>[[File:~~media/image254~~cm4-img254.png]]</p></li>

<li><p>The table below is the picture of the right half of the complete > table above, so you can see it clearly</p>

<p>[[File:~~media/image255~~cm4-img255.png]]</p></li></ol>

</li>

<li><p>There are a total of '''28''' GPIO ports in the 40pin interface, and the voltage of all GPIO ports is '''3.3v'''</p></li></ol>

[[File:~~media/image256~~cm4-img256.png]]

</div>

[[File:~~media/image256~~cm4-img256.png]]

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

# There are a total of 28 GPIO ports in the 40pins of the development board that can be used. The following uses pin 7—the corresponding GPIO is GPIO4_C3——the corresponding wPi serial number is 2—as an example to demonstrate how to set the high and low levels of the GPIO port

[[File:~~media/image257~~cm4-img257.png]]

Use gpio readall to see that the value (V) of pin 7 has changed to 0

[[File:~~media/image258~~cm4-img258.png]]

Use gpio readall to see that the value (V) of pin 7 has changed to 1

[[File:~~media/image259~~cm4-img259.png]]

'''Note that the 4 GPIO pins below the Orange Pi CM4 have an external 3.3V pull-up, so setting the pull-down is invalid, and the other pins can normally set the pull-up and pull-down resistor function'''

[[File:~~media/image260~~cm4-img260.png]]

# The following takes pin 11—the corresponding GPIO is GPIO3_C6—the corresponding wPi serial number is 5—as an example to demonstrate how to set the pull-up and pull-down resistance of the GPIO port

[[File:~~media/image261~~cm4-img261.png]]

# According to the schematic diagram of the 40pin interface, the spi available for Orange Pi CM4 is spi3

[[File:~~media/image262~~cm4-img262.png]]

<li>Then select '''System'''</li></ol>

[[File:~~media/image263~~cm4-img263.png]]

<li>Then select '''Hardware'''</li></ol>

[[File:~~media/image264~~cm4-img264.png]]

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

[[File:~~media/image265~~cm4-img265.png]]

<li>Then select '''<Save>'''Save</li></ol>

[[File:~~media/image266~~cm4-img266.png]]

<li>Then select'''<Back>'''</li></ol>

[[File:~~media/image267~~cm4-img267.png]]

<li>Then select'''<Reboot>''' Restart the system for the configuration to take effect</li></ol>

[[File:~~media/image268~~cm4-img268.png]]

<li>Then short-circuit the two pins of mosi (pin 19 in the 40pin interface) and miso (pin 21 in the 40pin interface) of SPI3 and run the output of spidev_test as follows, you can see the sending and receiving same data</li></ol>

[[File:~~media/image269~~cm4-img269.png]]

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

# As can be seen from the table below, the available i2c for Orange Pi CM4 is i2c2, i2c3 and i2c4, a total of three sets of i2c buses

[[File:~~media/image270~~cm4-img270.png]]

'''As can be seen from the above table, i2c4_m0 and spi3_m0 are multiplexed pins, and both cannot be opened at the same time. i2c3_m0 and uart3_m0 are also multiplexed pins, and both cannot be opened at the same time'''

<li>Then select '''System'''</li></ol>

[[File:~~media/image263~~cm4-img263.png]]

<li>Then select '''Hardware'''</li></ol>

[[File:~~media/image264~~cm4-img264.png]]

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

[[File:~~media/image271~~cm4-img271.png]]

<li>Then select '''<Save>''' Save</li></ol>

[[File:~~media/image266~~cm4-img266.png]]

<li>Then select '''<Back>'''</li></ol>

[[File:~~media/image267~~cm4-img267.png]]

<li>Then select'''<Reboot>''' Restart the system for the configuration to take effect</li></ol>

[[File:~~media/image268~~cm4-img268.png]]

orangepi@orangepi:~$ sudo i2cdetect -y 4 #i2c4 command

[[File:~~media/image272~~cm4-img272.png]]

# As can be seen from the table below, the available uarts of Orange Pi CM4 are three sets of uart buses: uart3, uart7 and uart9

[[File:~~media/image273~~cm4-img273.png]]

'''As can be seen from the above table, i2c3_m0 and uart3_m0 are multiplexed pins, and both cannot be opened at the same time'''

<li>Then select '''System'''</li></ol>

[[File:~~media/image263~~cm4-img263.png]]

<li>Then select '''Hardware'''</li></ol>

[[File:~~media/image264~~cm4-img264.png]]

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

[[File:~~media/image274~~cm4-img274.png]]

<li>Then select '''<Save>''' Save</li></ol>

[[File:~~media/image275~~cm4-img275.png]]

<li>Then select '''<Back>'''</li></ol>

[[File:~~media/image276~~cm4-img276.png]]

<li>Then select '''<Reboot>''' Restart the system for the configuration to take effect</li></ol>

[[File:~~media/image268~~cm4-img268.png]]

|}

[[File:~~media/image277~~cm4-img277.png]]

# As can be seen from the table below, Orange Pi CM4 has two channels of pwm available pwm11 and pwm15

[[File:~~media/image278~~cm4-img278.png]]

<li>Then select'''System'''</li></ol>

[[File:~~media/image279~~cm4-img279.png]]

<li>Then select '''Hardware'''</li></ol>

[[File:~~media/image264~~cm4-img264.png]]

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

[[File:~~media/image280~~cm4-img280.png]]

<li>Then select '''<Save>''' Save</li></ol>

[[File:~~media/image266~~cm4-img266.png]]

<li>Then select '''<Back>'''</li></ol>

[[File:~~media/image267~~cm4-img267.png]]

<li>Then select '''<Reboot>''' Restart the system for the configuration to take effect</li></ol>

[[File:~~media/image268~~cm4-img268.png]]

<li>Which of the above pwmchips corresponds to pwm11? Let’s first check the output of the '''ls /sys/class/pwm/ -l''' command, as shown below:</li></ol>

[[File:~~media/image281~~cm4-img281.png]]

<li>Then it can be known from the table below that the base address of the pwm11 register is fe6f0030, and then look at the output of the '''ls /sys/class/pwm/ -l''' command, you can see that pwmchip1 is linked to fe6f0030.pwm, so pwm11 corresponds to pwmchip as pwmchip1</li></ol>

[[File:~~media/image282~~cm4-img282.png]]

root@orangepi:~# '''echo 1 > /sys/class/pwm/pwmchip1/pwm0/enable'''

[[File:~~media/image283~~cm4-img283.png]]

[[File:~~media/image256~~cm4-img256.png]]

</div>

# The following takes pin No. 7—the corresponding GPIO is GPIO4_C3—the corresponding wPi number is 2—as an example to demonstrate how to set the high and low levels of the GPIO port

[[File:~~media/image257~~cm4-img257.png]]

# According to the schematic diagram of the 40pin interface, the spi available for Orange Pi CM4 is spi3

[[File:~~media/image262~~cm4-img262.png]]

<li>Then select '''System'''</li></ol>

[[File:~~media/image263~~cm4-img263.png]]

<li>Then select '''Hardware'''</li></ol>

[[File:~~media/image264~~cm4-img264.png]]

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

[[File:~~media/image265~~cm4-img265.png]]

<li>Then select '''<Save>'''Save</li></ol>

[[File:~~media/image266~~cm4-img266.png]]

<li>Then select '''<Back>'''</li></ol>

[[File:~~media/image267~~cm4-img267.png]]

<li>Then select'''<Reboot>''' Restart the system for the configuration to take effect</li></ol>

[[File:~~media/image268~~cm4-img268.png]]

# As can be seen from the table below, the available i2c for Orange Pi CM4 is i2c2, i2c3 and i2c4, a total of three sets of i2c buses

[[File:~~media/image270~~cm4-img270.png]]

'''As can be seen from the above table, i2c4_m0 and spi3_m0 are multiplexed pins, and both cannot be opened at the same time. i2c3_m0 and uart3_m0 are also multiplexed pins, and both cannot be opened at the same time'''

<li>Then select '''System'''</li></ol>

[[File:~~media/image263~~cm4-img263.png]]

<li>Then select '''Hardware'''</li></ol>

[[File:~~media/image264~~cm4-img264.png]]

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

[[File:~~media/image271~~cm4-img271.png]]

<li>Then select '''<Save>''' Save</li></ol>

[[File:~~media/image266~~cm4-img266.png]]

<li>Then select '''<Back>'''</li></ol>

[[File:~~media/image267~~cm4-img267.png]]

<li><p>Then select '''<Reboot>''' Restart the system for the configuration to take effect</p>

<p>[[File:~~media/image268~~cm4-img268.png]]</p></li></ol>

|}

[[File:~~media/image284~~cm4-img284.png]]

orangepi@orangepi:~$ sudo i2cdetect -y 4 #i2c4 command

[[File:~~media/image272~~cm4-img272.png]]

# As can be seen from the table below, the available uarts of Orange Pi CM4 are three sets of uart buses: uart3, uart7 and uart9

[[File:~~media/image273~~cm4-img273.png]]

'''As can be seen from the above table, i2c3_m0 and uart3_m0 are multiplexed pins, and both cannot be opened at the same time'''

<li>Then select '''System'''</li></ol>

[[File:~~media/image263~~cm4-img263.png]]

<li>Then select '''Hardware'''</li></ol>

[[File:~~media/image264~~cm4-img264.png]]

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

[[File:~~media/image274~~cm4-img274.png]]

<li>Then select'''<Save>''' Save</li></ol>

[[File:~~media/image275~~cm4-img275.png]]

<li>Then select '''<Back>'''</li></ol>

[[File:~~media/image276~~cm4-img276.png]]

<li>Then select'''<Reboot>'''Restart the system for the configuration to take effect</li></ol>

[[File:~~media/image268~~cm4-img268.png]]

|}

[[File:~~media/image277~~cm4-img277.png]]

[[File:~~media/image285~~cm4-img285.png]]

</div>

[[File:~~media/image87~~cm4-img87.png]]

</div>

[[File:~~media/image286~~cm4-img286.png]]

</div>

<li>Then select the AppImage version balenaEtcher, then click the right mouse button, and then click Execute to open balenaEtcher</li></ol>

[[File:~~media/image287~~cm4-img287.png]]

<li>The next thing to do is to wait patiently. When you see the following print information output from the terminal, it means that the BaoTa has been installed. The entire installation process takes about 34 minutes, and there may be some differences depending on the network speed</li></ol>

[[File:~~media/image288~~cm4-img288.png]]

<li><p>At this time, enter the panel address shown above in the browser to open the login interface of the BaoTa Linux panel, and then enter the '''username''' and '''password''' shown in the above figure at the corresponding position to log in.<br />

[[File:~~media/image289~~cm4-img289.png]]</p></li>

<li><p>After successfully logging into the pagoda, the following welcome interface will pop up. First, please read the user notice in the middle and drag it to the bottom, then you can select "I have agreed and read the "User Agreement"", and then click "Enter the panel" You can enter the BaoTa</p></li></ol>

[[File:~~media/image290~~cm4-img290.png]]

<li><p>If you do not have an account, you can go to the official website of the BaoTa (http://www.aapanel.com/)to register

[[File:~~media/image291~~cm4-img291.png]]</p></li>

<li><p>The final displayed interface is as shown in the figure below. You can intuitively see some status information of the Linux system on the development board, such as load status, CPU usage, memory usage, and storage space usage, etc.</p></li></ol>

[[File:~~media/image292~~cm4-img292.png]]

<li>Then select '''zh_CN.UTF-8 UTF-8''' in the pop-up interface (move up and down through the up and down direction keys on the keyboard, select through the space bar, and finally move the cursor to'''<OK>'''through the Tab key, and then return to car)</li></ol>

[[File:~~media/image293~~cm4-img293.png]]

<li>Then set the default '''locale''' as '''zh_CN.UTF-8'''</li></ol>

[[File:~~media/image294~~cm4-img294.png]]

<li>Then open '''Input Method'''</li></ol>

[[File:~~media/image295~~cm4-img295.png]]

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

[[File:~~media/image296~~cm4-img296.png]]

<li>Then Select '''Yes'''</li></ol>

[[File:~~media/image297~~cm4-img297.png]]

<li>Then Select '''fcitx'''</li></ol>

[[File:~~media/image298~~cm4-img298.png]]

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

[[File:~~media/image299~~cm4-img299.png]]

<li><p>Then open '''Fcitx configuration'''</p></li></ol>

[[File:~~media/image300~~cm4-img300.png]]

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

[[File:~~media/image301~~cm4-img301.png]]

[[File:~~media/image302~~cm4-img302.png]]

</div>

<li>Then bring'''Google Pinyin''' to the front</li></ol>

[[File:~~media/image303~~cm4-img303.png]]

[[File:~~media/image304~~cm4-img304.png]]

<li>Then open the '''Geany''' editor to test the Chinese input method</li></ol>

[[File:~~media/image305~~cm4-img305.png]]

<li>The Chinese input method test is as follows</li></ol>

[[File:~~media/image306~~cm4-img306.png]]

<li>Then '''restart the system''' and you can see that the system is displayed in Chinese</li></ol>

[[File:~~media/image307~~cm4-img307.png]]

# Open first '''Language Support'''

[[File:~~media/image308~~cm4-img308.png]]

<li>Then find the '''Chinese (China)''' option</li></ol>

[[File:~~media/image309~~cm4-img309.png]]

<li>Then please use the left mouse button to select '''Chinese (China)''' and hold it down, then drag it up to the initial position, and the display after dragging is as shown in the figure below:</li></ol>

[[File:~~media/image310~~cm4-img310.png]]

'''Note that this step is not easy to drag, please be patient and try a few more times.'''

<li>Then select '''Apply System-Wide''' to apply the Chinese settings to the entire system</li></ol>

[[File:~~media/image311~~cm4-img311.png]]

<li>Then set '''Keyboard input method system''' as '''fcitx'''</li></ol>

[[File:~~media/image312~~cm4-img312.png]]

<li><p>After re-entering the system, please choose '''not to ask me again''' in the following interface, and then please decide whether the standard folder should also be updated to Chinese according to your preferences</p></li></ol>

[[File:~~media/image313~~cm4-img313.png]]

<li>Then you can see that the desktop is displayed in Chinese</li></ol>

[[File:~~media/image314~~cm4-img314.png]]

<li>Then we can open '''Geany''' to test the Chinese input method, the opening method is as shown in the figure below</li></ol>

[[File:~~media/image315~~cm4-img315.png]]

<li>After opening'''Geany''', the default is English input method, we can switch to Chinese input method through '''Ctrl+Space'''shortcut key, and then we can input Chinese</li></ol>

[[File:~~media/image316~~cm4-img316.png]]

# Open first '''Language Support'''

[[File:~~media/image308~~cm4-img308.png]]

<li>Then find the '''Chinese (China)''' option</li></ol>

[[File:~~media/image317~~cm4-img317.png]]

<li>Then please use the left mouse button to select '''Chinese (China)''' and hold it down, then drag it up to the initial position, and the display after dragging is as shown in the figure below:</li></ol>

[[File:~~media/image318~~cm4-img318.png]]

'''Note that this step is not easy to drag, please be patient and try a few more times.'''

<li>Then select '''Apply System-Wide''' to apply the Chinese settings to the entire system</li></ol>

[[File:~~media/image319~~cm4-img319.png]]

<li><p>After re-entering the system, please choose '''not to ask me again''' in the following interface, and then please decide whether the standard folder should also be updated to Chinese according to your preferences</p></li></ol>

[[File:~~media/image313~~cm4-img313.png]]

<li>Then you can see that the desktop is displayed in Chinese</li></ol>

[[File:~~media/image314~~cm4-img314.png]]

<li>Then open the Fcitx5 configuration program</li></ol>

[[File:~~media/image320~~cm4-img320.png]]

[[File:~~media/image321~~cm4-img321.png]]

</div>

<li>The interface after selection is as shown below, and then click OK</li></ol>

[[File:~~media/image322~~cm4-img322.png]]

<li>Then we can open '''Geany'''to test the Chinese input method, the opening method is as shown in the figure below</li></ol>

[[File:~~media/image315~~cm4-img315.png]]

<li>After opening '''Geany''', the default is English input method, we can switch to Chinese input method through '''Ctrl+Space''' shortcut key, and then we can input Chinese</li></ol>

[[File:~~media/image323~~cm4-img323.png]]

[https://downloads.nomachine.com/download/?id=116&distro=ARM '''https://downloads.nomachine.com/download/?id=116&distro=ARM''']

[[File:~~media/image324~~cm4-img324.png]]

<li>In addition, you can also download the '''NoMachine''' installation package in the official tool</li></ol>

[[File:~~media/image325~~cm4-img325.png]]

<blockquote>First '''enter the remote login software-NoMachine''' folder

</blockquote>

[[File:~~media/image326~~cm4-img326.png]]

<blockquote>Then download the arm64 version of the deb installation package

</blockquote>

[[File:~~media/image327~~cm4-img327.png]]

[https://downloads.nomachine.com/download/?id=8 '''https://downloads.nomachine.com/download/?id=8''']

[[File:~~media/image328~~cm4-img328.png]]

<li><p>Then open NoMachine in Window '''NoMachine'''</p></li></ol>

[[File:~~media/image329~~cm4-img329.png]]

<li>After NoMachine starts, it will automatically scan other devices installed with NoMachine in the LAN. After entering the main interface of NoMachine, you can see that the development board is already in the list of connectable devices, and then click the position shown in the red box in the figure below You can start to log in to the Linux system desktop of the development board</li></ol>

[[File:~~media/image330~~cm4-img330.png]]

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

[[File:~~media/image331~~cm4-img331.png]]

[[File:~~media/image332~~cm4-img332.png]]

</div>

<li><p>Then click OK in the next interface</p></li>

<li><p>Finally, you can see the desktop of the development board Linux system</p>

<p>[[File:~~media/image333~~cm4-img333.png]]</p></li></ol>

[[File:~~media/image334~~cm4-img334.png]]

</div>

<li>Then enter the VNC password set earlier</li></ol>

[[File:~~media/image335~~cm4-img335.png]]

<li><p>After successful login, the interface is displayed as shown in the figure below, and then you can remotely operate the desktop of the Linux system on the development board</p>

<p>[[File:~~media/image336~~cm4-img336.png]]</p></li></ol>

<li>Then you can see the startup icon of QT Creator in '''Applications'''</li></ol>

[[File:~~media/image337~~cm4-img337.png]]

You can also use the following command to open QT Creator

<li>The interface after QT Creator is opened is as follows</li></ol>

[[File:~~media/image338~~cm4-img338.png]]

</li></ol>

[[File:~~media/image339~~cm4-img339.png]]

<li>The default version of QT Creator in '''Ubuntu22.04''' is as follows</li></ol>

[[File:~~media/image340~~cm4-img340.png]]

<li>The default version of QT Creator in '''Debian11''' is as follows</li></ol>

[[File:~~media/image341~~cm4-img341.png]]

<li>The default version of QT Creator in '''Debian12''' is as follows</li></ol>

[[File:~~media/image342~~cm4-img342.png]]

</li></ol>

[[File:~~media/image343~~cm4-img343.png]]

<li>Then remove the tick of '''ClangCodeModel'''</li></ol>

[[File:~~media/image344~~cm4-img344.png]]

'''Debian12 please skip this step.'''

[[File:~~media/image345~~cm4-img345.png]]

[[File:~~media/image346~~cm4-img346.png]]

<li>Then you can open a sample code</li></ol>

[[File:~~media/image347~~cm4-img347.png]]

<li>After clicking the sample code, the corresponding instruction document will be opened automatically, you can read the instruction carefully</li></ol>

[[File:~~media/image348~~cm4-img348.png]]

<li>Then click next '''Configure Project'''</li></ol>

[[File:~~media/image349~~cm4-img349.png]]

<li>Then click the green triangle in the lower left corner to compile and run the sample code</li></ol>

[[File:~~media/image350~~cm4-img350.png]]

<li>After waiting for a period of time, the interface shown in the figure below will pop up, which means that QT can compile and run normally</li></ol>

[[File:~~media/image351~~cm4-img351.png]]

# The current active version of ROS 1 is as follows, and the recommended version is '''Noetic Ninjemys'''

[[File:~~media/image352~~cm4-img352.png]]

[[File:~~media/image353~~cm4-img353.png]]

[http://docs.ros.org/ '''http://docs.ros.org''']

[http://wiki.ros.org/noetic/Installation '''http://wiki.ros.org/noetic/Installation''']

[[File:~~media/image354~~cm4-img354.png]]

[[File:~~media/image355~~cm4-img355.png]]

</div>

[[File:~~media/image356~~cm4-img356.png]]

</div>

<li>At this time, press the direction keys on the keyboard to control the little turtle to move up, down, left, and right</li></ol>

[[File:~~media/image357~~cm4-img357.png]]

# The current active version of ROS 2 is as follows, and the recommended version is '''Galactic Geochelone'''

[[File:~~media/image358~~cm4-img358.png]]

[[File:~~media/image359~~cm4-img359.png]]

[http://docs.ros.org/ '''http://docs.ros.org''']

[[File:~~media/image360~~cm4-img360.png]]

</div>

[[File:~~media/image361~~cm4-img361.png]]

</div>

'''If there is a problem with compiling the code you copied here, please go to the official tool to download the source code and upload it to the Linux system of the development board for testing.'''

[[File:~~media/image362~~cm4-img362.png]]

orangepi@orangepi:~$ '''make'''

'''Raspberry Pi 5-inch MIPI LCD display + Touch screenis shown in the figure below'''

[[File:~~media/image363~~cm4-img363.png]]

[[File:~~media/image364~~cm4-img364.png]]

<li>15pin MIPI cable</li></ol>

[[File:~~media/image365~~cm4-img365.png]]

<li>Then connect the 15pin MIPI cable to the Raspberry Pi 5-inch screen as shown in the figure below (note the orientation of the insulating surface)</li></ol>

[[File:~~media/image366~~cm4-img366.png]]

<li>Finally connect to the LCD interface of the Orange Pi CM4 development board</li></ol>

[[File:~~media/image367~~cm4-img367.png]]

<li>Then select '''System'''</li></ol>

[[File:~~media/image368~~cm4-img368.png]]

<li>Then select '''Hardware'''</li></ol>

[[File:~~media/image369~~cm4-img369.png]]

<li>Then use the arrow keys on the keyboard to navigate to raspi-7inch-touchscreen, and then use the space to select</li></ol>

[[File:~~media/image370~~cm4-img370.png]]

<li>Then select '''<Save>'''Save</li></ol>

[[File:~~media/image371~~cm4-img371.png]]

<li>Then select '''<Back>'''</li></ol>

[[File:~~media/image372~~cm4-img372.png]]

<li>Then select '''<Reboot>''' Restart the system for the configuration to take effect</li></ol>

[[File:~~media/image373~~cm4-img373.png]]

'''The above settings will eventually add the configuration of overlays=raspi-7inch-touchscreen to /boot/orangepiEnv.txt. After setting, you can check it first. If this configuration does not exist, then there is a problem with the settings.'''

<li>After startup, you can see the display of the LCD screen as follows:</li></ol>

[[File:~~media/image374~~cm4-img374.png]]

# First open '''Display''' Settings in Linux

[[File:~~media/image375~~cm4-img375.png]]

</li></ol>

[[File:~~media/image376~~cm4-img376.png]]

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

[[File:~~media/image377~~cm4-img377.png]]

<li>Then select '''Keep this configuration'''</li></ol>

[[File:~~media/image378~~cm4-img378.png]]

[[File:~~media/image379~~cm4-img379.png]]

</div></li>

[[File:~~media/image380~~cm4-img380.png]]

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

</li>

<li><p>Connect the 30pin eDP interface of the screen and the eDP interface of the development board with a 30pin single-head cable in the same direction</p>

<p>[[File:~~media/image381~~cm4-img381.png]]</p></li></ol>

<p>orangepi@orangepi:~$ '''sudo orangepi-config'''</p></li>

<li><p>Then select '''System'''</p>

<p>[[File:~~media/image368~~cm4-img368.png]]</p></li>

<li><p>Then select '''Hardware'''</p>

<p>[[File:~~media/image369~~cm4-img369.png]]</p></li>

<li><p>Then use the arrow keys on the keyboard to navigate to edp, and > then use the '''space''' to select</p>

<p>[[File:~~media/image382~~cm4-img382.png]]</p></li>

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

<p>[[File:~~media/image371~~cm4-img371.png]]</p></li>

<li><p>Then select '''<Back>'''</p>

<p>[[File:~~media/image372~~cm4-img372.png]]</p></li>

<li><p>Then select '''<Reboot>''' to restart the system to make the > configuration take effect</p>

<p>[[File:~~media/image373~~cm4-img373.png]]</p>

<p>'''The above settings will eventually add the configuration of overlays=edp to /boot/orangepiEnv.txt. After setting, you can check it first. If this configuration does not exist, then there is a problem with the settings.'''</p>

<p>'''If you find it troublesome to use orangepi-config, you can also use the vim editor to open /boot/orangepiEnv.txt, and then add the configuration of overlays=edp.'''</p>

</li>

<li><p>After startup, you can see the display of the eDP screen as follows:</p>

<p>[[File:~~media/image383~~cm4-img383.png]]</p></li></ol>

[[File:~~media/image384~~cm4-img384.png]]

</div>

# First, we can use the '''lsblk''' command to view all storage devices on the development board. The current development board is connected to an NVMe SSD and a U disk. The output is as follows:

[[File:~~media/image385~~cm4-img385.png]]

<li>Then use the '''zpool list''' command to see that the system has created a ZFS pool named '''pool1''', and the size of the ZFS pool pool1 is the size of the NVME SSD plus the size of the U disk</li></ol>

[[File:~~media/image386~~cm4-img386.png]]

<li>Then use the '''zpool list''' command to see that only 1.01G is actually occupied, because these 1001 files are all duplicates, indicating that the data deduplication function is effective.</li></ol>

[[File:~~media/image387~~cm4-img387.png]]

<li>Then the file size that can be seen through the '''ls -lh''' command and the space occupied in the ZFS pool are both '''27M'''</li></ol>

[[File:~~media/image388~~cm4-img388.png]]

<li>At this time, you can see that the size of the '''text.tar''' file is still 27M, but it only occupies 9.47M in the ZFS pool, indicating that the file is compressed</li></ol>

[[File:~~media/image389~~cm4-img389.png]]

[[File:~~media/image390~~cm4-img390.png]]

</div>

[[File:~~media/image391~~cm4-img391.png]]

</div>

[[File:~~media/image392~~cm4-img392.png]]

</div></li>

[[File:~~media/image393~~cm4-img393.png]]

</div></li>

<li>Then select '''5 Install/Update the bootloader on SD/eMMC''' to update the u-boot in the TF card or '''7 Install/Update the bootloader on SPI Flash''' to update the u-boot in the SPI Flash</li></ol>

[[File:~~media/image394~~cm4-img394.png]]

<li>After pressing the Enter key, a Warning will pop up first</li></ol>

[[File:~~media/image395~~cm4-img395.png]]

<li>Press the Enter key again to start updating u-boot, and the following information will be displayed after the update is completed</li></ol>

[[File:~~media/image396~~cm4-img396.png]]

[[File:~~media/image397~~cm4-img397.png]]

</div>

[[File:~~media/image393~~cm4-img393.png]]

</div>

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

[[File:~~media/image398~~cm4-img398.png]]

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

[[File:~~media/image399~~cm4-img399.png]]

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

[[File:~~media/image400~~cm4-img400.png]]

[[File:~~media/image401~~cm4-img401.png]]

</div>

[[File:~~media/image393~~cm4-img393.png]]

</div>

<li>Then select the type of rootfs</li></ol>

[[File:~~media/image402~~cm4-img402.png]]

[[File:~~media/image403~~cm4-img403.png]]

</div>

[[File:~~media/image404~~cm4-img404.png]]

</div>

[[File:~~media/image405~~cm4-img405.png]]

</div>

[[File:~~media/image406~~cm4-img406.png]]

You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.

[[File:~~media/image407~~cm4-img407.png]]

[[File:~~media/image408~~cm4-img408.png]]

</div>

[[File:~~media/image393~~cm4-img393.png]]

</div>

<li>Then select the type of rootfs</li></ol>

[[File:~~media/image402~~cm4-img402.png]]

[[File:~~media/image403~~cm4-img403.png]]

</div>

[[File:~~media/image404~~cm4-img404.png]]

</div>

[[File:~~media/image405~~cm4-img405.png]]

</div>

[[File:~~media/image406~~cm4-img406.png]]

You can then select additional packages that need to be installed. Please press the Enter key to skip directly here.

[[File:~~media/image407~~cm4-img407.png]]

[[File:~~media/image409~~cm4-img409.png]]

</div></li>

[[File:~~media/image410~~cm4-img410.png]]

</div></li>

[[File:~~media/image411~~cm4-img411.png]]

</div></li>

[[File:~~media/image412~~cm4-img412.png]]

</div></li>

[[File:~~media/image413~~cm4-img413.png]]

</div></li>

[[File:~~media/image414~~cm4-img414.png]]

</div></li>

[[File:~~media/image415~~cm4-img415.png]]

</div></li>

[[File:~~media/image416~~cm4-img416.png]]

</div></li>

[[File:~~media/image417~~cm4-img417.png]]

</div></li>

[[File:~~media/image418~~cm4-img418.png]]

</div>

<p>After restarting, you can see the display on the LCD screen as follows:</p></li></ol>

[[File:~~media/image419~~cm4-img419.png]]

<p>After restarting, you can see that the display of the eDP screen is as follows:</p></li></ol>

[[File:~~media/image420~~cm4-img420.png]]

# First click enter '''Setting'''

[[File:~~media/image421~~cm4-img421.png]]

<li>Then select '''Network & internet'''</li></ol>

[[File:~~media/image422~~cm4-img422.png]]

<li>Then select '''Wi-Fi'''</li></ol>

[[File:~~media/image423~~cm4-img423.png]]

<li>Then turn on the '''Wi-Fi''' switch</li></ol>

[[File:~~media/image424~~cm4-img424.png]]

<li>After turning on '''Wi-Fi''', if everything is normal, you can scan for nearby Wi-Fi hotspots</li></ol>

[[File:~~media/image425~~cm4-img425.png]]

<li>Then select the Wi-Fi you want to connect to, and the password input interface shown in the figure below will pop up</li></ol>

[[File:~~media/image426~~cm4-img426.png]]

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

[[File:~~media/image427~~cm4-img427.png]]

<li>After the Wi-Fi connection is successful, the display is as shown in the figure below:</li></ol>

[[File:~~media/image428~~cm4-img428.png]]

# Then select '''Settings'''

[[File:~~media/image421~~cm4-img421.png]]

<li>Then select '''Network & internet'''</li></ol>

[[File:~~media/image422~~cm4-img422.png]]

<li>Then select '''Hotspot & tethering'''</li></ol>

[[File:~~media/image429~~cm4-img429.png]]

<li>Then select '''Wi-Fi hotspot'''</li></ol>

[[File:~~media/image430~~cm4-img430.png]]

<li>Then turn on the '''Wi-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 (If you need to modify the name and password of the hotspot, you need to turn off the '''Wi-Fi hotspot''' first, and then you can modify it)</li></ol>

[[File:~~media/image431~~cm4-img431.png]]

<li>At this time, you can take out your mobile phone. If everything is normal, you can find the WIFI hotspot with the same name ('''here AndroidAP_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></ol>

[[File:~~media/image432~~cm4-img432.png]]

<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 '''WI-FI Hotspot''' of the development board can be used normally.</li></ol>

[[File:~~media/image433~~cm4-img433.png]]

# First click enter '''Setting'''

[[File:~~media/image421~~cm4-img421.png]]

<li>Then select '''Connected devices'''</li></ol>

[[File:~~media/image434~~cm4-img434.png]]

<li>Then click '''Pair new device''' to turn on Bluetooth and start scanning the surrounding Bluetooth devices</li></ol>

[[File:~~media/image435~~cm4-img435.png]]

<li>The searched Bluetooth devices will be displayed under '''Available devices'''</li></ol>

[[File:~~media/image436~~cm4-img436.png]]

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

[[File:~~media/image437~~cm4-img437.png]]

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

[[File:~~media/image438~~cm4-img438.png]]

<li>After the pairing is completed, you can see the paired Bluetooth device as shown in the figure below</li></ol>

[[File:~~media/image439~~cm4-img439.png]]

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

[[File:~~media/image440~~cm4-img440.png]]

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

[[File:~~media/image441~~cm4-img441.png]]

== [[File:~~media/image442~~cm4-img442.png]] ==

[[File:~~media/image379~~cm4-img379.png]]

</div></li>

[[File:~~media/image380~~cm4-img380.png]]

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

<li><p>Connect the FPC end of the 30pin single-head codirectional cable to the eDP interface of the development board, and connect the other end to the eDP interface of the screen</p></li></ol>

[[File:~~media/image381~~cm4-img381.png]]

<li><p>Then connect the Type-C power supply to the board and power it on. After the system starts, you can see the screen display as shown in the figure below</p>

<p>[[File:~~media/image443~~cm4-img443.png]]</p></li></ol>

# First click on the wiringOP icon to open the wiringOP APP

[[File:~~media/image444~~cm4-img444.png]]

<li>The main interface of wiringOP APP is displayed as shown in the figure below, and then click the '''GPIO_TEST''' button to open the GPIO test interface</li></ol>

[[File:~~media/image445~~cm4-img445.png]]

<li>The GPIO test interface is shown in the figure below. The two rows of '''CheckBox''' buttons on the left are in one-to-one correspondence with the 40pin pins. When the '''CheckBox''' button is checked, the corresponding GPIO pin will be set to '''OUT''' mode, and the pin level will be set to high level; when the checkbox is unchecked, the GPIO pin level will be set to low level; When the '''GPIO READALL''' button is pressed, information such as wPi number, GPIO mode, and pin level can be obtained; when the '''BLINK ALL GPIO''' button is clicked, the program will control the 28 GPIO ports to continuously switch between high and low levels</li></ol>

[[File:~~media/image446~~cm4-img446.png]]

<li>Then click the '''GPIO READALL''' button, the output information is as shown in the figure below:</li></ol>

[[File:~~media/image447~~cm4-img447.png]]

<li>There are a total of 28 GPIO ports in the 40pins of the development board that can be used. The following uses pin 7—the corresponding GPIO is GPIO4_A4—the corresponding wPi serial number is 2—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 7. When the button is selected, pin 7 will be set to high level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is 3.3v, it means setting high level success</li></ol>

[[File:~~media/image448~~cm4-img448.png]]

<li>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is '''OUT''', and the pin level is high</li></ol>

[[File:~~media/image449~~cm4-img449.png]]

<li>Click the '''CheckBox''' button in the figure below again to cancel the check status. Pin 7 will be set to low level. After setting, you can use a multimeter to measure the voltage value of the pin. If it is '''0v''', it means that the low level is set successfully.</li></ol>

[[File:~~media/image450~~cm4-img450.png]]

<li><p>Then click the '''GPIO READALL''' button, you can see that the current pin 7 mode is OUT, and the pin level is low</p>

<p>[[File:~~media/image451~~cm4-img451.png]]</p></li></ol>

<li><p>UART7 and UART9 are enabled by default in Android. The position of the 40pin is shown in the figure below, and the corresponding device nodes are '''/dev/ttyS7''' and '''/dev/ttyS9''' respectively</p>

<p>[[File:~~media/image452~~cm4-img452.png]]</p></li>

<li><p>First click on the wiringOP icon to open the wiringOP APP</p></li></ol>

[[File:~~media/image444~~cm4-img444.png]]

<li>The main interface of wiringOP APP is displayed as shown in the figure below, and then click the '''UART_TEST''' button to open the UART test interface</li></ol>

[[File:~~media/image453~~cm4-img453.png]]

<li>The serial port test interface of the APP is shown in the figure below</li></ol>

[[File:~~media/image454~~cm4-img454.png]]

<li>Take the test of '''UART7''' as an example below, select the '''/dev/ttyS7''' node in the selection box, enter the baud rate you want to set in the edit box, and then click the '''OPEN''' button to open the /dev/ttyS7 node. After the opening is successful, the '''OPEN''' button becomes unselectable, and the '''CLOSE''' button and '''SEND''' button become selectable</li></ol>

[[File:~~media/image455~~cm4-img455.png]]

<li>Then use Dupont wire to short the RXD and TXD pins of uart7</li></ol>

[[File:~~media/image456~~cm4-img456.png]]

<li>Then you can enter a character in the send edit box below, and click the '''SEND''' button to start sending</li></ol>

[[File:~~media/image457~~cm4-img457.png]]

<li>If everything is normal, the received string will be displayed in the receiving box</li></ol>

[[File:~~media/image458~~cm4-img458.png]]

# According to the schematic diagram of the 40pin interface, the spi available for Orange Pi 3B is spi3

[[File:~~media/image459~~cm4-img459.png]]

<li>Here, the SPI interface is tested through the w25q64 module. First, the w25q64 device is connected to the SPI3 interface</li></ol>

[[File:~~media/image460~~cm4-img460.png]]

<li>Then click the wiringOP icon to open the wiringOP APP</li></ol>

[[File:~~media/image444~~cm4-img444.png]]

<li>The main interface of wiringOP APP is displayed as shown in the figure below, click the SPI_TEST button to open the SPI test interface</li></ol>

[[File:~~media/image461~~cm4-img461.png]]

<li>Then click the '''OPEN''' button to initialize the SPI</li></ol>

[[File:~~media/image462~~cm4-img462.png]]

<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''' button</li></ol>

[[File:~~media/image463~~cm4-img463.png]]

<li>Finally, the APP will display the read ID information</li></ol>

[[File:~~media/image464~~cm4-img464.png]]

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

[[File:~~media/image465~~cm4-img465.png]]

# Android enables '''PWM11''' by default, and the corresponding pin is located at 40pin as shown in the figure below

[[File:~~media/image466~~cm4-img466.png]]

<li>First click on the wiringOP icon to open the wiringOP APP</li></ol>

[[File:~~media/image444~~cm4-img444.png]]

<li>Then click the '''PWM_TEST''' button on the main interface of wiringOP to enter the PWM test interface</li></ol>

[[File:~~media/image467~~cm4-img467.png]]

<li>The base address corresponding to PWM11 is '''fe6f0030''', here pwmchip0 shows '''fdd70020.pwm''' on the right, then you need to click the drop-down option to select other pwmchips until '''fe6f0030.pwm''' is displayed on the right</li></ol>

[[File:~~media/image468~~cm4-img468.png]]

<li>When the drop-down option selects '''pwmchip3''', the corresponding base address of PWM11 is '''fe6f0030''' on the right</li></ol>

[[File:~~media/image469~~cm4-img469.png]]

<li>Then confirm the PWM channel, the default is channel 0, and confirm the PWM cycle, the default configuration is '''50000ns''', converted to PWM frequency is '''20KHz''', you can modify it yourself, click the '''EXPORT''' button to export '''PWM11'''</li></ol>

[[File:~~media/image470~~cm4-img470.png]]

<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/image471~~cm4-img471.png]]

<li>Then use an oscilloscope to measure the No. 32 pin in the 40pin of the development board, and you can see the following waveform</li></ol>

[[File:~~media/image472~~cm4-img472.png]]

'''The development board has 4 USB interfaces, among which the USB interface marked in red box in the figure below can support both Host mode and Device mode, and the other 3 USB interfaces only support Host mode.'''

[[File:~~media/image473~~cm4-img473.png]]

'''The USB OTG interface defaults to Host mode, which can be used to connect USB devices such as mouse and keyboard. If you want to use ADB, you need to manually switch to Device mode.'''

<li><p>First open Settings</p>

<p>[[File:~~media/image421~~cm4-img421.png]]</p></li>

<li><p>Then select '''About tablet'''</p>

<p>[[File:~~media/image474~~cm4-img474.png]]</p></li>

<li><p>Then click the '''Build number''' menu bar several times with the mouse until the prompt '''You are now a developer!''' appears</p>

<p>[[File:~~media/image475~~cm4-img475.png]]</p></li>

<li><p>Then click to return to the previous menu</p>

<p>[[File:~~media/image476~~cm4-img476.png]]</p></li>

<li><p>Then select '''System'''</p>

<p>[[File:~~media/image477~~cm4-img477.png]]</p></li>

<li><p>Then select '''Advanced'''</p>

<p>[[File:~~media/image478~~cm4-img478.png]]</p></li>

<li><p>Then select '''Developer options''' in the expanded column</p>

<p>[[File:~~media/image479~~cm4-img479.png]]</p></li>

<li><p>Finally find the '''USB OTG Mode Switch''' switch, '''turn on the switch to switch to Device mode, turn off the switch to switch to Host mode'''</p></li></ol>

[[File:~~media/image480~~cm4-img480.png]]

[[File:~~media/image18~~cm4-img18.png]]

</div></li>

<li><p>Then refer to [[\l|'''the method of USB OTG mode switching''']] to switch USB OTG to Device mode</p></li>

<li><p>Then connect the development board to the Ubuntu PC through the USB2.0 male-to-male data cable. The position of the USB OTG interface on the development board is shown in the figure below:</p>

<p>[[File:~~media/image481~~cm4-img481.png]]</p></li>

<li><p>Then install the adb tool on the Ubuntu PC</p>

<p>test@test:~$ '''sudo apt update'''</p>

<li><p>Google Drive</p>

<p>[[File:~~media/image482~~cm4-img482.png]]</p></li></ol>

</li>

<li><p>After downloading the sub-volume compression package of the Android 11 source code, please check whether the MD5 checksum is correct, if not, please download the source code again</p>

Admin

Bureaucrats, Administrators

8,367

edits

Changes

Orange Pi CM4

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Products

FAQ

Images Resources

Support

Tools