Changes

← Older edit

Orange Pi CM4

1,291 bytes added, 19:55, 19 September 2023

→‎Download orangepi-build from github

[[File:cm4-img3.png|800px]]

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

[[File:cm4-img4.png|800px]]

[[File:cm4-img5.png|800px]]

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

[[File:cm4-img6.png|800px]]

[[File:cm4-img7.png|800px]]

</div>

=== Interface details of Orange Pi CM4 base board ===

[[File:cm4-img8.png|800px]]

</div>

</div></li>

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

[[File:cm4-img19.png|350px]] [[File:cm4-img20.png|450px]]</li>

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

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

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

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

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

</li>

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

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

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

<li>Ensure that no TF card is inserted into the development board ~~>~~ and no power supply is connected</li><li>Then press and hold the MaskROM button on the development board. ~~>~~ The position of the MaskROM button on the development board is ~~>~~ shown as follows:

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

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

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

<li>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'''".

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

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

</div></li>

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

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

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

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

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

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

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

<li>Select '''MiniLoaderAll.bin''' from the '''MiniLoader''' folder ~~>~~ downloaded earlier, and then click '''Open'''

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

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

<li>Then go to the previously downloaded '''MiniLoader''' folder, ~~>~~ select '''rkspi_loader.img''', and click '''Open'''

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

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

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

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

|-

<li>Then select '''Force Write to address'''

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

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

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

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

[[File:cm4-img83.png]]

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

|}

</li>

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

</li></ol>

[[File:cm4-img390.png|center|790px]]

</div>

<li>Then select '''Developer options''' in the expanded column

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

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

[[File:cm4-img480.png]]

</div></li>

<li>Then refer to [[\lOrange Pi CM4#The method of USB OTG mode switching|'''the method of USB OTG mode switching''']] to switch USB OTG to Device mode</li>

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

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

<li>Then install the adb tool on the Ubuntu PC

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

|-

|

test@test:~$ '''sudo apt update'''

test@test:~$ '''sudo apt -y install adb'''|}</li>

<li>You can view the identified ADB devices through the following command

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

|-

|

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

List of devices attached

S63QCF54CJ device

test@test:~$ '''lsusb'''

Bus 003 Device 006: ID 2207:0006|}</li><li>Then you can log in to the android system through the adb shell on the Ubuntu PC</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-|

test@test:~$ '''adb shell'''

console:/ $

|}</ol>

<li>Execute the following command to remount the Android system</li~~></ol~~>{| class="wikitable" style="width:800px;" |-|

test@test:~$ '''adb root'''

test@test:~$ '''adb remount'''

|}</ol>

<li>Then you can transfer files to the Android system</li~~></ol~~>{| class="wikitable" style="width:800px;" |-|

test@test:~$ '''adb push example.txt /system/'''

|}

</ol>

~~~~

=== Use network connection adb debugging ===

{| class="wikitable" style="background-color:#ffffdc;width:800px;" |-| <big>'''Using the network adb does not require a data cable to connect the computer and the development board, but to communicate through the network, so first make sure that the wired or wireless network of the development board is connected, and then obtain the IP address of the development board, which will be used later.'''</big>|}

<li>Make sure that the '''service.adb.tcp.port''' of the Android system is set to port number 5555

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

|-

|

console:/ # '''getprop | grep "adb.tcp"'''

[service.adb.tcp.port]: ['''5555''']|}</li><li>If '''service.adb.tcp.port''' is not set, you can use the following command to set the port number of network adb</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-|

console:/ # '''setprop service.adb.tcp.port 5555'''

console:/ # '''start adbd'''

|}</ol>

<li>Install adb tool on Ubuntu PC

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

|-

|

test@test:~$ '''sudo apt update'''

test@test:~$ '''sudo apt install -y adb'''|}</li>

<li>Then connect to the network adb on the Ubuntu PC

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

|-

|

test@test:~$ '''adb connect 192.168.1.xxx''' '''(IP地址需要修改为开发板的IP地址)'''

* daemon not running; starting now at tcp:5037

* daemon started successfully

connected to 192.168.1.xxx:5555

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

List of devices attached

192.168.1.xxx:5555 device|}</li><li>Then you can log in to the android system through the adb shell on the Ubuntu PC</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-|

test@test:~$ '''adb shell'''

console:/ #

|}</ol>

</li>

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

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

|-

|

test@test:~$ '''md5sum -c RK356X_Android11.tar.gz.md5sum'''

<pstyle="color:#FF0000">'''RK356X_Android11.tar.gz00: OK'''<pstyle="color:#FF0000">'''RK356X_Android11.tar.gz01: OK'''<pstyle="color:#FF0000">'''RK356X_Android11.tar.gz02: OK'''<pstyle="color:#FF0000">'''RK356X_Android11.tar.gz03: OK'''<pstyle="color:#FF0000">'''RK356X_Android11.tar.gz04: OK'''<pstyle="color:#FF0000">'''RK356X_Android11.tar.gz05: OK'''<pstyle="color:#FF0000">'''RK356X_Android11.tar.gz06: OK'''|}</li><li>Then you need to merge multiple compressed files for decompression</li>~~</ol>~~{| class="wikitable" style="width:800px;" |-| test@test:~$ '''cat RK356X_Android11.tar.~~gz0~~gz0* | tar -xvzf -'''|}</ol>

~~~~

== Compile the source code of Android 11 ==

<li>First install the software packages required to compile the Android11 source code

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

|-

|

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

test@test:~$ '''sudo apt-get install -y git gnupg flex bison gperf build-essential \'''

'''zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 libncurses5 \'''

'''lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z1-dev ccache \'''

'''libgl1-mesa-dev libxml2-utils xsltproc unzip liblz4-tool'''|}</li>

<li>There is a build.sh compilation script in the source code, and the compilation parameters are as follows

<li>-'''U''':Compile uboot</li><li>-'''K''':Compile kernel</li><li>-'''A''':compile android</li><li>-'''u''':Package and generate update.img and update_spi_nvme.img</li><li>-'''o''':Compile OTA package</li><li>-'''d''':Specify kernel dts</li></ol>

</li>

<li>Compile uboot, kernel, android and package them into update.img

<li>The command to compile and support HDMI 4K display mirroring > (LCD is turned off by default) is as follows:

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

|-

|

test@test:~$ '''cd RK356X_Android11'''

test@test:~/ RK356X_Android11$ '''export BOARD=orangepi3b'''

test@test:~/ RK356X_Android11$ '''source build/envsetup.sh'''

test@test:~/ RK356X_Android11$ '''lunch rk3566_r-userdebug'''

test@test:~/ RK356X_Android11$ '''./build.sh -AUKu'''|}</li>

<li>The command to compile and support LCD display mirroring (HDMI > is disabled by default) is as follows:

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

|-

|

test@test:~$ '''cd RK356X_Android11'''

test@test:~/ RK356X_Android11$ '''export BOARD=orangepi3b'''

test@test:~/ RK356X_Android11$ '''source build/envsetup.sh'''

test@test:~/ RK356X_Android11$ '''lunch rk3566_r-userdebug'''

test@test:~/ RK356X_Android11$ '''./build.sh -AUKu'''|}</li></ol>

</li>

<li>After the compilation is complete, the following information will be printed

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

|-

|

********rkImageMaker ver 2.1********

Generating new image, please wait...

Making update_spi_nvme.img OK.

Make update image ok!

/wspace3/RK3566/RK356X_Android11|}</li>

<li>The final image file will be placed in the '''rockdev/Image-rk3566_r/''' directory. Among them, '''update.img''' is the boot image that supports TF card and eMMC, and '''update_spi_nvme.img''' is the boot image of NVME SSD

{| class="wikitable" style="width:800px;" |-| ~~[mailto:test@test:~OrangePi_4/rk3399-android-8.1$~~ test@test:~/RK356X_Android11$] '''cd rockdev/Image-rk3566_r'''~~[mailto:test@test:~OrangePi_4/rk3399-android-8.1$~~ test@test:~/RK356X_Android11/rockdev/Image-rk3566_r $] '''ls update*'''update.img update_spi_nvme.img|}</li></ol>

== User Manual Update History ==

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

|-

| '''Version'''

== Image Update History ==

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

|-

| style="text-align:center;" | '''Date'''| style="text-align:center;" | '''Update Notes'''

|-

| style="text-align:center;" | 2023-08-29

|

Orangepicm4_1.0.0_ubuntu_focal_server_linux5.10.160.7z

Orangepicm4_1.0.0_debian_bookworm_desktop_xfce_linux5.10.160.7z

OrangePiCM4_RK3566_Android11_v1.0.0.tar.gz

OrangePiCM4_RK3566_Android11_lcd_spi-nvme_v1.0.0.tar.gz

* initial version

|-

| style="text-align:center;" | 2023-09-05| Opios-arch-aarch64-xfce-opicm4-23.09-linux5.10.160.img.xz

* initial version

|}

Admin

Bureaucrats, Administrators

6,556

edits

Wiki-Orange Pi β

Changes

Orange Pi CM4

Wiki-Orange Pi ^β