Radxa Wiki - User contributions [en]

Rock5/guide

2024-11-04T03:08:34Z

Yanw:

{{rock5_header}}
{{Languages|rock5/guide}}

__NOTOC__

* [[rock5/guide/build-debian-from-debos-radxa | How to build Debian from debos-radxa]]
* [[rock5/guide/serial-console | How to using Serial Console]]
* [[rock5/guide/radxa-debian | How to use Radxa Official Debian]]
* [[rock5/guide/radxa-ubuntu | How to use Radxa Official Ubuntu]]
* [[rock5/guide/radxa-apt | Radxa APT]]
* [[rock5/guide/hdmiin | How to use hdmi in]]
* [[rock5/guide/sata | How to use M.2 E-key to SATA breakout board]]
* [[rock5/guide/spi-nvme-boot | SPI Nor Flash and NVME SSD boot]]
* [[rock5/guide/build-u-boot-on-5b | Build U-Boot on ROCK 5B]]
* [[rock5/guide/build-kernel-on-5b | Build Kernel on ROCK 5B]]
* [[rock5/guide/rockchip-mpp | Rockchip MPP]]
* [[rock5/guide/apmode | Setting AP Mode]]
* [[rock5/guide/linux-backupos| Linux Backup OS]]
* [[rock5/guide/5b-debian-12-bookworm | How to upgrade Rock 5B Debian 12 bookworm]]
* [[rock5/guide/5b-debian-icaclient-invisible-mouse-troubleshooting | Rock 5B Debian 11 ICAClient (Citrix workspace app for Linux) invisible mouse troubleshooting]]

------

* [[rock5/guide/android12 | Android12]]
* [[rock5/guide/wireless | Wireless ADB]]
* [[rock5/guide/Touch Screen Portable Monitor | Touch Screen Portable Monitor]]
* [[rock5/guide/GPIO interface power supply | GPIO interface power supply]]

Rock3/Android11

2024-01-26T09:28:04Z

Yanw: /* Setup board environment */

{{rock3_header}}

{{Languages|rock3/Android11}}

[[rock3 | ROCK 3]] > [[Rock3/Android11 | Andriod11]]

This page is a step-by-step tutorial how to build Rock 3 serail board Android11 image. Including：

* 3A 
* 3B 
* CM3IO 

Recommend build host is Ubuntu 20.04 64bit, for other hosts, refer official Android documents [https://source.android.com/setup/build/initializing Establishing a Build Environment].

=== Repo ===
<code bash>
radxa$ wget 'https://storage.googleapis.com/git-repo-downloads/repo' -P /tmp/
radxa$ sudo cp /tmp/repo /usr/local/bin/repo
radxa$ sudo chmod +x /usr/local/bin/repo
</code>

In China Download Repo:
<code bash>
radxa$ echo "export REPO_URL='https://mirrors.tuna.tsinghua.edu.cn/git/git-repo/'" >> ~/.bashrc
radxa$ source ~/.bashrc
radxa$ curl https://mirrors.tuna.tsinghua.edu.cn/git/git-repo -o /tmp/repo
radxa$ sudo cp /tmp/repo /usr/local/bin/repo
radxa$ sudo chmod +x /usr/local/bin/repo
</code>

=== DockerFile ===
<code>
FROM ubuntu:xenial

RUN apt-get update -y && apt-get install -y openjdk-8-jdk python git-core gnupg flex bison gperf build-essential \
zip curl liblz4-tool zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 \
lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache \
libgl1-mesa-dev libxml2-utils xsltproc unzip mtools u-boot-tools \
htop iotop sysstat iftop pigz bc device-tree-compiler lunzip \
dosfstools vim-common parted udev libssl-dev python3 python-pip lzop swig

#### For China
RUN curl https://mirrors.tuna.tsinghua.edu.cn/git/git-repo > /usr/local/bin/repo && \
chmod +x /usr/local/bin/repo && \
which repo
ENV REPO_URL='https://mirrors.tuna.tsinghua.edu.cn/git/git-repo/'
#### For China End

RUN pip install pycrypto
ENV USER=android11-docker
ARG USER_ID=0
ARG GROUP_ID=0
RUN groupadd -g ${GROUP_ID} jenkins-docker && useradd -m -g jenkins-docker -u ${USER_ID} android11-docker

USER android11-docker
</code>

Build DockerFile
<code>
radxa$ docker build -t android-builder:11.x --build-arg USER_ID=`id -u` --build-arg GROUP_ID=`id -g` $(which-dir-dockerfile-in)
</code>

=== Download source code ===
<code bash>
$ mkdir rock-android11
$ cd rock-android11
</code>
Then run:
<code bash>
radxa:rock-android11 $ repo init -u https://github.com/radxa/manifests.git -b Android11_Radxa_rk11 -m rockchip-r-release.xml
radxa:rock-android11 $ repo sync -d --no-tags -j4
</code>

=== Build ===
==== Use all-in-one build script ====

<code bash>
radxa:rock-android11 $ source build/envsetup.sh

# for Rock 3A
radxa:rock-android11 $ lunch rk356x_rock_3a_r-userdebug
# for Rock 3A if you want a box software
radxa:rock-android11 $ lunch rk356x_rock_3a_box-userdebug
# for Rock 3B
radxa:rock-android11 $ lunch rk356x_rock_3b_r-userdebug
# for Rock 3C
radxa:rock-android11 $ lunch rk356x_rock_3c_r-userdebug
# for Rock CM3 IO
radxa:rock-android11 $ lunch rk356x_rock_cm3_r-userdebug

radxa:rock-android11 $ ./build.sh -UACKup
# get images from IMAGE directory
</code>

==== Step by step Build ====
If you dont' want to use "Use all-in-one build script", you can follow this way to build image step by step.

===== Setup board environment =====
<code bash>
# for Rock 3A
radxa:rock-android11 $ export PRODUCT_NAME="rk356x_rock_3a_r"
radxa:rock-android11 $ export PRODUCT_UBOOT_CONFIG="radxa_rock_3a_toybrick"
radxa:rock-android11 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig"
radxa:rock-android11 $ export PRODUCT_KERNEL_DTS="rk3568-rock-3a"

# for Rock 3A box software
radxa:rock-android11 $ export PRODUCT_NAME="rk356x_rock_3a_box"
radxa:rock-android11 $ export PRODUCT_UBOOT_CONFIG="radxa_rock_3a_toybrick"
radxa:rock-android11 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig"
radxa:rock-android11 $ export PRODUCT_KERNEL_DTS="rk3568-rock-3a"

# for Rock 3B
radxa:rock-android11 $ export PRODUCT_NAME="rk356x_rock_3b_r"
radxa:rock-android11 $ export PRODUCT_UBOOT_CONFIG="radxa_rock_3a_toybrick"
radxa:rock-android11 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig android-11.config rock_3b.config"
radxa:rock-android11 $ export PRODUCT_KERNEL_DTS="rk3568-rock-3c"

# for Rock 3C
radxa:rock-android11 $ export PRODUCT_NAME="rk356x_rock_3c_r"
radxa:rock-android11 $ export PRODUCT_UBOOT_CONFIG="radxa_rock_3a_toybrick"
radxa:rock-android11 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig android-11.config rockcm3io.config"
radxa:rock-android11 $ export PRODUCT_KERNEL_DTS="rk3566-rock-3c"

# for Rock CM3 IO
radxa:rock-android11 $ export PRODUCT_NAME="rk356x_rock_cm3_r"
radxa:rock-android11 $ export PRODUCT_UBOOT_CONFIG="rk3566"
radxa:rock-android11 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig android-11.config rockcm3io.config"
radxa:rock-android11 $ export PRODUCT_KERNEL_DTS="rk3566-rock-cm3io"

</code>

===== Build u-boot =====
<code bash>
radxa:rock-android11 $ cd u-boot
radxa:rock-android11/u-boot $ make clean
radxa:rock-android11/u-boot $ make mrproper
radxa:rock-android11/u-boot $ make distclean
radxa:rock-android11/u-boot $ ./make.sh ${PRODUCT_UBOOT_CONFIG}
radxa:rock-android11 $ cd -
</code>
The generated images are '''idbloader.img''' , and '''uboot.img'''
===== Building kernel =====
<code bash>
radxa:rock-android11 $ cd kernel
radxa:rock-android11/kernel $ ADDON_ARGS="CC=../prebuilts/clang/host/linux-x86/clang-r383902b/bin/clang LD=../prebuilts/clang/host/linux-x86/clang-r383902b/bin/ld.lld"
radxa:rock-android11/kernel $ make clean
radxa:rock-android11/kernel $ make $ADDON_ARGS ARCH=arm64 ${PRODUCT_KERNEL_CONFIG}
radxa:rock-android11/kernel $ make $ADDON_ARGS ARCH=arm64 ${PRODUCT_KERNEL_DTS}.img -j$(nproc)

radxa:rock-android11 $ cd -
</code>

===== Building AOSP =====
<code bash>
radxa:rock-android11 $ source build/envsetup.sh
radxa:rock-android11 $ lunch ${PRODUCT_NAME}-userdebug
radxa:rock-android11 $ make -j$(nproc)
</code>
It takes a long time, take a break and wait...

===== Make images =====
<code bash>
radxa:rock-android11 $ rm -rf rockdev
radxa:rock-android11 $ ln -s RKTools/linux/Linux_Pack_Firmware/rockdev .
radxa:rock-android11 $ ./mkimage.sh
</code>

===== Pack Image =====
<code bash>
radxa:rock-android11 $ cd rockdev
radxa:rock-android11/rockdev $ rm -rf Image
radxa:rock-android11/rockdev $ ln -s Image-${PRODUCT_NAME} Image

</code>

1. RkUpdate Image
<code>
radxa:rock-android11/rockdev $ ./mkupdate_rk356x.sh
</code>
The images under rockdev/ are `update.img`

2. gpt Image
<code bash>
radxa:rock-android11/rockdev $ ./android-gpt.sh
</code>

=== Installation ===
* sdcard 
[https://wiki.radxa.com/Rock3/install/microSD Install on MicroSD] 
* emmc with reader 
[https://wiki.radxa.com/Rock3/install/eMMC Install on eMMC with USB to eMMC Reader] 
* emmc from usb port 
[https://wiki.radxa.com/Rock3/dev/usb-install Install on eMMC from USB port]

Rock3/Android11

2024-01-26T09:26:30Z

Yanw: /* Setup board environment */

{{rock3_header}}

{{Languages|rock3/Android11}}

[[rock3 | ROCK 3]] > [[Rock3/Android11 | Andriod11]]

This page is a step-by-step tutorial how to build Rock 3 serail board Android11 image. Including：

* 3A 
* 3B 
* CM3IO 

Recommend build host is Ubuntu 20.04 64bit, for other hosts, refer official Android documents [https://source.android.com/setup/build/initializing Establishing a Build Environment].

=== Repo ===
<code bash>
radxa$ wget 'https://storage.googleapis.com/git-repo-downloads/repo' -P /tmp/
radxa$ sudo cp /tmp/repo /usr/local/bin/repo
radxa$ sudo chmod +x /usr/local/bin/repo
</code>

In China Download Repo:
<code bash>
radxa$ echo "export REPO_URL='https://mirrors.tuna.tsinghua.edu.cn/git/git-repo/'" >> ~/.bashrc
radxa$ source ~/.bashrc
radxa$ curl https://mirrors.tuna.tsinghua.edu.cn/git/git-repo -o /tmp/repo
radxa$ sudo cp /tmp/repo /usr/local/bin/repo
radxa$ sudo chmod +x /usr/local/bin/repo
</code>

=== DockerFile ===
<code>
FROM ubuntu:xenial

RUN apt-get update -y && apt-get install -y openjdk-8-jdk python git-core gnupg flex bison gperf build-essential \
zip curl liblz4-tool zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 \
lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache \
libgl1-mesa-dev libxml2-utils xsltproc unzip mtools u-boot-tools \
htop iotop sysstat iftop pigz bc device-tree-compiler lunzip \
dosfstools vim-common parted udev libssl-dev python3 python-pip lzop swig

#### For China
RUN curl https://mirrors.tuna.tsinghua.edu.cn/git/git-repo > /usr/local/bin/repo && \
chmod +x /usr/local/bin/repo && \
which repo
ENV REPO_URL='https://mirrors.tuna.tsinghua.edu.cn/git/git-repo/'
#### For China End

RUN pip install pycrypto
ENV USER=android11-docker
ARG USER_ID=0
ARG GROUP_ID=0
RUN groupadd -g ${GROUP_ID} jenkins-docker && useradd -m -g jenkins-docker -u ${USER_ID} android11-docker

USER android11-docker
</code>

Build DockerFile
<code>
radxa$ docker build -t android-builder:11.x --build-arg USER_ID=`id -u` --build-arg GROUP_ID=`id -g` $(which-dir-dockerfile-in)
</code>

=== Download source code ===
<code bash>
$ mkdir rock-android11
$ cd rock-android11
</code>
Then run:
<code bash>
radxa:rock-android11 $ repo init -u https://github.com/radxa/manifests.git -b Android11_Radxa_rk11 -m rockchip-r-release.xml
radxa:rock-android11 $ repo sync -d --no-tags -j4
</code>

=== Build ===
==== Use all-in-one build script ====

<code bash>
radxa:rock-android11 $ source build/envsetup.sh

# for Rock 3A
radxa:rock-android11 $ lunch rk356x_rock_3a_r-userdebug
# for Rock 3A if you want a box software
radxa:rock-android11 $ lunch rk356x_rock_3a_box-userdebug
# for Rock 3B
radxa:rock-android11 $ lunch rk356x_rock_3b_r-userdebug
# for Rock 3C
radxa:rock-android11 $ lunch rk356x_rock_3c_r-userdebug
# for Rock CM3 IO
radxa:rock-android11 $ lunch rk356x_rock_cm3_r-userdebug

radxa:rock-android11 $ ./build.sh -UACKup
# get images from IMAGE directory
</code>

==== Step by step Build ====
If you dont' want to use "Use all-in-one build script", you can follow this way to build image step by step.

===== Setup board environment =====
<code bash>
# for Rock 3A
radxa:rock-android11 $ export PRODUCT_NAME="rk356x_rock_3a_r"
radxa:rock-android11 $ export PRODUCT_UBOOT_CONFIG="radxa_rock_3a_toybrick"
radxa:rock-android11 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig"
radxa:rock-android11 $ export PRODUCT_KERNEL_DTS="rk3568-rock-3a"

# for Rock 3A box software
radxa:rock-android11 $ export PRODUCT_NAME="rk356x_rock_3a_box"
radxa:rock-android11 $ export PRODUCT_UBOOT_CONFIG="radxa_rock_3a_toybrick"
radxa:rock-android11 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig"
radxa:rock-android11 $ export PRODUCT_KERNEL_DTS="rk3568-rock-3a"

# for Rock 3B
radxa:rock-android11 $ export PRODUCT_NAME="rk356x_rock_3b_r"
radxa:rock-android11 $ export PRODUCT_UBOOT_CONFIG="radxa_rock_3a_toybrick"
radxa:rock-android11 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig android-11.config rock_3b.config"
radxa:rock-android11 $ export PRODUCT_KERNEL_DTS="rk3568-rock-3b"

# for Rock 3C
radxa:rock-android11 $ export PRODUCT_NAME="rk356x_rock_3c_r"
radxa:rock-android11 $ export PRODUCT_UBOOT_CONFIG="radxa_rock_3a_toybrick"
radxa:rock-android11 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig android-11.config rockcm3io.config"
radxa:rock-android11 $ export PRODUCT_KERNEL_DTS="rk3568-rock-3b"

# for Rock CM3 IO
radxa:rock-android11 $ export PRODUCT_NAME="rk356x_rock_cm3_r"
radxa:rock-android11 $ export PRODUCT_UBOOT_CONFIG="rk3566"
radxa:rock-android11 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig android-11.config rockcm3io.config"
radxa:rock-android11 $ export PRODUCT_KERNEL_DTS="rk3566-rock-cm3io"

</code>

===== Build u-boot =====
<code bash>
radxa:rock-android11 $ cd u-boot
radxa:rock-android11/u-boot $ make clean
radxa:rock-android11/u-boot $ make mrproper
radxa:rock-android11/u-boot $ make distclean
radxa:rock-android11/u-boot $ ./make.sh ${PRODUCT_UBOOT_CONFIG}
radxa:rock-android11 $ cd -
</code>
The generated images are '''idbloader.img''' , and '''uboot.img'''
===== Building kernel =====
<code bash>
radxa:rock-android11 $ cd kernel
radxa:rock-android11/kernel $ ADDON_ARGS="CC=../prebuilts/clang/host/linux-x86/clang-r383902b/bin/clang LD=../prebuilts/clang/host/linux-x86/clang-r383902b/bin/ld.lld"
radxa:rock-android11/kernel $ make clean
radxa:rock-android11/kernel $ make $ADDON_ARGS ARCH=arm64 ${PRODUCT_KERNEL_CONFIG}
radxa:rock-android11/kernel $ make $ADDON_ARGS ARCH=arm64 ${PRODUCT_KERNEL_DTS}.img -j$(nproc)

radxa:rock-android11 $ cd -
</code>

===== Building AOSP =====
<code bash>
radxa:rock-android11 $ source build/envsetup.sh
radxa:rock-android11 $ lunch ${PRODUCT_NAME}-userdebug
radxa:rock-android11 $ make -j$(nproc)
</code>
It takes a long time, take a break and wait...

===== Make images =====
<code bash>
radxa:rock-android11 $ rm -rf rockdev
radxa:rock-android11 $ ln -s RKTools/linux/Linux_Pack_Firmware/rockdev .
radxa:rock-android11 $ ./mkimage.sh
</code>

===== Pack Image =====
<code bash>
radxa:rock-android11 $ cd rockdev
radxa:rock-android11/rockdev $ rm -rf Image
radxa:rock-android11/rockdev $ ln -s Image-${PRODUCT_NAME} Image

</code>

1. RkUpdate Image
<code>
radxa:rock-android11/rockdev $ ./mkupdate_rk356x.sh
</code>
The images under rockdev/ are `update.img`

2. gpt Image
<code bash>
radxa:rock-android11/rockdev $ ./android-gpt.sh
</code>

=== Installation ===
* sdcard 
[https://wiki.radxa.com/Rock3/install/microSD Install on MicroSD] 
* emmc with reader 
[https://wiki.radxa.com/Rock3/install/eMMC Install on eMMC with USB to eMMC Reader] 
* emmc from usb port 
[https://wiki.radxa.com/Rock3/dev/usb-install Install on eMMC from USB port]

Rock3/Android11

2024-01-26T09:23:23Z

Yanw: /* Use all-in-one build script */

{{rock3_header}}

{{Languages|rock3/Android11}}

[[rock3 | ROCK 3]] > [[Rock3/Android11 | Andriod11]]

This page is a step-by-step tutorial how to build Rock 3 serail board Android11 image. Including：

* 3A 
* 3B 
* CM3IO 

Recommend build host is Ubuntu 20.04 64bit, for other hosts, refer official Android documents [https://source.android.com/setup/build/initializing Establishing a Build Environment].

=== Repo ===
<code bash>
radxa$ wget 'https://storage.googleapis.com/git-repo-downloads/repo' -P /tmp/
radxa$ sudo cp /tmp/repo /usr/local/bin/repo
radxa$ sudo chmod +x /usr/local/bin/repo
</code>

In China Download Repo:
<code bash>
radxa$ echo "export REPO_URL='https://mirrors.tuna.tsinghua.edu.cn/git/git-repo/'" >> ~/.bashrc
radxa$ source ~/.bashrc
radxa$ curl https://mirrors.tuna.tsinghua.edu.cn/git/git-repo -o /tmp/repo
radxa$ sudo cp /tmp/repo /usr/local/bin/repo
radxa$ sudo chmod +x /usr/local/bin/repo
</code>

=== DockerFile ===
<code>
FROM ubuntu:xenial

RUN apt-get update -y && apt-get install -y openjdk-8-jdk python git-core gnupg flex bison gperf build-essential \
zip curl liblz4-tool zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 \
lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache \
libgl1-mesa-dev libxml2-utils xsltproc unzip mtools u-boot-tools \
htop iotop sysstat iftop pigz bc device-tree-compiler lunzip \
dosfstools vim-common parted udev libssl-dev python3 python-pip lzop swig

#### For China
RUN curl https://mirrors.tuna.tsinghua.edu.cn/git/git-repo > /usr/local/bin/repo && \
chmod +x /usr/local/bin/repo && \
which repo
ENV REPO_URL='https://mirrors.tuna.tsinghua.edu.cn/git/git-repo/'
#### For China End

RUN pip install pycrypto
ENV USER=android11-docker
ARG USER_ID=0
ARG GROUP_ID=0
RUN groupadd -g ${GROUP_ID} jenkins-docker && useradd -m -g jenkins-docker -u ${USER_ID} android11-docker

USER android11-docker
</code>

Build DockerFile
<code>
radxa$ docker build -t android-builder:11.x --build-arg USER_ID=`id -u` --build-arg GROUP_ID=`id -g` $(which-dir-dockerfile-in)
</code>

=== Download source code ===
<code bash>
$ mkdir rock-android11
$ cd rock-android11
</code>
Then run:
<code bash>
radxa:rock-android11 $ repo init -u https://github.com/radxa/manifests.git -b Android11_Radxa_rk11 -m rockchip-r-release.xml
radxa:rock-android11 $ repo sync -d --no-tags -j4
</code>

=== Build ===
==== Use all-in-one build script ====

<code bash>
radxa:rock-android11 $ source build/envsetup.sh

# for Rock 3A
radxa:rock-android11 $ lunch rk356x_rock_3a_r-userdebug
# for Rock 3A if you want a box software
radxa:rock-android11 $ lunch rk356x_rock_3a_box-userdebug
# for Rock 3B
radxa:rock-android11 $ lunch rk356x_rock_3b_r-userdebug
# for Rock 3C
radxa:rock-android11 $ lunch rk356x_rock_3c_r-userdebug
# for Rock CM3 IO
radxa:rock-android11 $ lunch rk356x_rock_cm3_r-userdebug

radxa:rock-android11 $ ./build.sh -UACKup
# get images from IMAGE directory
</code>

==== Step by step Build ====
If you dont' want to use "Use all-in-one build script", you can follow this way to build image step by step.

===== Setup board environment =====
<code bash>
# for Rock 3A
radxa:rock-android11 $ export PRODUCT_NAME="rk356x_rock_3a_r"
radxa:rock-android11 $ export PRODUCT_UBOOT_CONFIG="radxa_rock_3a_toybrick"
radxa:rock-android11 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig"
radxa:rock-android11 $ export PRODUCT_KERNEL_DTS="rk3568-rock-3a"

# for Rock 3A box software
radxa:rock-android11 $ export PRODUCT_NAME="rk356x_rock_3a_box"
radxa:rock-android11 $ export PRODUCT_UBOOT_CONFIG="radxa_rock_3a_toybrick"
radxa:rock-android11 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig"
radxa:rock-android11 $ export PRODUCT_KERNEL_DTS="rk3568-rock-3a"

# for Rock 3B
radxa:rock-android11 $ export PRODUCT_NAME="rk356x_rock_3b_r"
radxa:rock-android11 $ export PRODUCT_UBOOT_CONFIG="radxa_rock_3a_toybrick"
radxa:rock-android11 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig android-11.config rock_3b.config"
radxa:rock-android11 $ export PRODUCT_KERNEL_DTS="rk3568-rock-3b"

# for Rock CM3 IO
radxa:rock-android11 $ export PRODUCT_NAME="rk356x_rock_cm3_r"
radxa:rock-android11 $ export PRODUCT_UBOOT_CONFIG="rk3566"
radxa:rock-android11 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig android-11.config rockcm3io.config"
radxa:rock-android11 $ export PRODUCT_KERNEL_DTS="rk3566-rock-cm3io"

</code>

===== Build u-boot =====
<code bash>
radxa:rock-android11 $ cd u-boot
radxa:rock-android11/u-boot $ make clean
radxa:rock-android11/u-boot $ make mrproper
radxa:rock-android11/u-boot $ make distclean
radxa:rock-android11/u-boot $ ./make.sh ${PRODUCT_UBOOT_CONFIG}
radxa:rock-android11 $ cd -
</code>
The generated images are '''idbloader.img''' , and '''uboot.img'''
===== Building kernel =====
<code bash>
radxa:rock-android11 $ cd kernel
radxa:rock-android11/kernel $ ADDON_ARGS="CC=../prebuilts/clang/host/linux-x86/clang-r383902b/bin/clang LD=../prebuilts/clang/host/linux-x86/clang-r383902b/bin/ld.lld"
radxa:rock-android11/kernel $ make clean
radxa:rock-android11/kernel $ make $ADDON_ARGS ARCH=arm64 ${PRODUCT_KERNEL_CONFIG}
radxa:rock-android11/kernel $ make $ADDON_ARGS ARCH=arm64 ${PRODUCT_KERNEL_DTS}.img -j$(nproc)

radxa:rock-android11 $ cd -
</code>

===== Building AOSP =====
<code bash>
radxa:rock-android11 $ source build/envsetup.sh
radxa:rock-android11 $ lunch ${PRODUCT_NAME}-userdebug
radxa:rock-android11 $ make -j$(nproc)
</code>
It takes a long time, take a break and wait...

===== Make images =====
<code bash>
radxa:rock-android11 $ rm -rf rockdev
radxa:rock-android11 $ ln -s RKTools/linux/Linux_Pack_Firmware/rockdev .
radxa:rock-android11 $ ./mkimage.sh
</code>

===== Pack Image =====
<code bash>
radxa:rock-android11 $ cd rockdev
radxa:rock-android11/rockdev $ rm -rf Image
radxa:rock-android11/rockdev $ ln -s Image-${PRODUCT_NAME} Image

</code>

1. RkUpdate Image
<code>
radxa:rock-android11/rockdev $ ./mkupdate_rk356x.sh
</code>
The images under rockdev/ are `update.img`

2. gpt Image
<code bash>
radxa:rock-android11/rockdev $ ./android-gpt.sh
</code>

=== Installation ===
* sdcard 
[https://wiki.radxa.com/Rock3/install/microSD Install on MicroSD] 
* emmc with reader 
[https://wiki.radxa.com/Rock3/install/eMMC Install on eMMC with USB to eMMC Reader] 
* emmc from usb port 
[https://wiki.radxa.com/Rock3/dev/usb-install Install on eMMC from USB port]

Rock5/guide/android12

2024-01-10T06:35:36Z

Yanw: /* Download source code */

This page is a step-by-step tutorial how to build Rock 5 serail board Android12 image.

=== Repo ===
<code bash>
radxa$ wget 'https://storage.googleapis.com/git-repo-downloads/repo' -P /tmp/
radxa$ sudo cp /tmp/repo /usr/local/bin/repo
radxa$ sudo chmod +x /usr/local/bin/repo
</code>

In China Download Repo:
<code bash>
radxa$ echo "export REPO_URL='https://mirrors.tuna.tsinghua.edu.cn/git/git-repo/'" >> ~/.bashrc
radxa$ source ~/.bashrc
radxa$ curl https://mirrors.tuna.tsinghua.edu.cn/git/git-repo -o /tmp/repo
radxa$ sudo cp /tmp/repo /usr/local/bin/repo
radxa$ sudo chmod +x /usr/local/bin/repo
</code>

=== DockerFile ===
<code>
FROM ubuntu:xenial

RUN apt-get update -y && apt-get install -y openjdk-8-jdk python git-core gnupg flex bison gperf build-essential \
zip curl liblz4-tool zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 \
lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache \
libgl1-mesa-dev libxml2-utils xsltproc unzip mtools u-boot-tools \
htop iotop sysstat iftop pigz bc device-tree-compiler lunzip \
dosfstools vim-common parted udev libssl-dev python3 python-pip lzop swig

#### For China
RUN curl https://mirrors.tuna.tsinghua.edu.cn/git/git-repo > /usr/local/bin/repo && \
chmod +x /usr/local/bin/repo && \
which repo
ENV REPO_URL='https://mirrors.tuna.tsinghua.edu.cn/git/git-repo/'
#### For China End

RUN pip install pycrypto
ENV USER=android12-docker
ARG USER_ID=0
ARG GROUP_ID=0
RUN groupadd -g ${GROUP_ID} jenkins-docker && useradd -m -g jenkins-docker -u ${USER_ID} android12-docker

USER android12-docker
</code>

Build DockerFile
<code>
radxa$ docker build -t android-builder:12.x --build-arg USER_ID=`id -u` --build-arg GROUP_ID=`id -g` $(which-dir-dockerfile-in)
</code>

=== Download source code ===
<code bash>
$ mkdir rock-android12
$ cd rock-android12
</code>
Then run:
<code bash>
radxa:rock-android12 $ repo init -u https://github.com/radxa/manifests.git -b Android12_RK3588_Radxa_rk14 -m rockchip-s-release.xml
radxa:rock-android12 $ repo sync -d -j4
</code>

=== Build ===
==== Use all-in-one build script ====

<code bash>
radxa:rock-android12 $ source build/envsetup.sh
radxa:rock-android12 $ lunch RadxaRock5B-userdebug
radxa:rock-android12 $ ./build.sh -UACKup
# get images from IMAGE directory
</code>

==== Step by step Build ====
If you dont' want to use "Use all-in-one build script", you can follow this way to build image step by step.

===== Setup board environment =====
<code bash>
# for Rock 5B
radxa:rock-android12 $ export PRODUCT_NAME="RadxaRock5B"
radxa:rock-android12 $ export PRODUCT_UBOOT_CONFIG="rk3588"
radxa:rock-android12 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig"
radxa:rock-android12 $ export PRODUCT_KERNEL_DTS="rk3588-rock-5b"
</code>

===== Build u-boot =====
<code bash>
radxa:rock-android12 $ cd u-boot
radxa:rock-android12/u-boot $ make clean
radxa:rock-android12/u-boot $ make mrproper
radxa:rock-android12/u-boot $ make distclean
radxa:rock-android12/u-boot $ ./make.sh ${PRODUCT_UBOOT_CONFIG}
radxa:rock-android12 $ cd -
</code>
The generated images are '''idbloader.img''' , and '''uboot.img'''
===== Building kernel =====
Android 12.0 cannot directly burn kernel.img and resource.img, kernel.img and resource.img are included in boot.img
<code bash>
radxa:rock-android12 $ cd kernel-5.10
radxa:rock-android12/kernel-5.10 $ export PATH=../prebuilts/clang/host/linux-x86/clang-r416183b/bin:$PATH
radxa:rock-android12/kernel-5.10 $ alias msk='make CROSS_COMPILE=aarch64-linux-gnu- LLVM=1 LLVM_IAS=1'
radxa:rock-android12/kernel-5.10 $ msk ARCH=arm64 rockchip_defconfig android-11.config rock5b.config
radxa:rock-android12/kernel-5.10 $ msk ARCH=arm64 BOOT_IMG=../rockdev/Image-RadxaRock5B/boot.img rk3588-rock-5b.img

radxa:rock-android12 $ cd -
</code>
After compiling, you can directly burn the boot.img in the kernel-5.10 directory to the boot location of the machine. Please load the partition table first when burning (parameter.txt), so as not to burn the wrong location.

===== Building AOSP =====
<code bash>
radxa:rock-android12 $ source build/envsetup.sh
radxa:rock-android12 $ lunch ${PRODUCT_NAME}-userdebug
radxa:rock-android12 $ make -j$(nproc)
</code>
It takes a long time, take a break and wait...

===== Make images =====
<code bash>
radxa:rock-android12 $ rm -rf rockdev
radxa:rock-android12 $ ln -s RKTools/linux/Linux_Pack_Firmware/rockdev .
radxa:rock-android12 $ ./mkimage.sh
</code>

===== Pack Image =====
<code bash>
radxa:rock-android12 $ cd rockdev
radxa:rock-android12/rockdev $ rm -rf Image
radxa:rock-android12/rockdev $ ln -s Image-${PRODUCT_NAME} Image

</code>

1. RkUpdate Image
<code>
radxa:rock-android12/rockdev $ ./mkupdate.sh rk3588 Image
</code>
The images under rockdev/ are `update.img`

2. gpt Image
<code bash>
radxa:rock-android12/rockdev $ ./android-gpt.sh
</code>

Rock5/guide/android12

2024-01-10T06:34:13Z

Yanw: /* Download source code */

This page is a step-by-step tutorial how to build Rock 5 serail board Android12 image.

=== Repo ===
<code bash>
radxa$ wget 'https://storage.googleapis.com/git-repo-downloads/repo' -P /tmp/
radxa$ sudo cp /tmp/repo /usr/local/bin/repo
radxa$ sudo chmod +x /usr/local/bin/repo
</code>

In China Download Repo:
<code bash>
radxa$ echo "export REPO_URL='https://mirrors.tuna.tsinghua.edu.cn/git/git-repo/'" >> ~/.bashrc
radxa$ source ~/.bashrc
radxa$ curl https://mirrors.tuna.tsinghua.edu.cn/git/git-repo -o /tmp/repo
radxa$ sudo cp /tmp/repo /usr/local/bin/repo
radxa$ sudo chmod +x /usr/local/bin/repo
</code>

=== DockerFile ===
<code>
FROM ubuntu:xenial

RUN apt-get update -y && apt-get install -y openjdk-8-jdk python git-core gnupg flex bison gperf build-essential \
zip curl liblz4-tool zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 \
lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache \
libgl1-mesa-dev libxml2-utils xsltproc unzip mtools u-boot-tools \
htop iotop sysstat iftop pigz bc device-tree-compiler lunzip \
dosfstools vim-common parted udev libssl-dev python3 python-pip lzop swig

#### For China
RUN curl https://mirrors.tuna.tsinghua.edu.cn/git/git-repo > /usr/local/bin/repo && \
chmod +x /usr/local/bin/repo && \
which repo
ENV REPO_URL='https://mirrors.tuna.tsinghua.edu.cn/git/git-repo/'
#### For China End

RUN pip install pycrypto
ENV USER=android12-docker
ARG USER_ID=0
ARG GROUP_ID=0
RUN groupadd -g ${GROUP_ID} jenkins-docker && useradd -m -g jenkins-docker -u ${USER_ID} android12-docker

USER android12-docker
</code>

Build DockerFile
<code>
radxa$ docker build -t android-builder:12.x --build-arg USER_ID=`id -u` --build-arg GROUP_ID=`id -g` $(which-dir-dockerfile-in)
</code>

=== Download source code ===
<code bash>
$ mkdir rock-android12
$ cd rock-android12
</code>
Then run:
<code bash>
radxa:rock-android12 $ repo init -u https://github.com/radxa/manifests.git -b Android12_RK3588_Radxa_rk14 -m rockchip-s-release.xml
radxa:rock-android12 $ repo sync -d --no-tags -j4
</code>

=== Build ===
==== Use all-in-one build script ====

<code bash>
radxa:rock-android12 $ source build/envsetup.sh
radxa:rock-android12 $ lunch RadxaRock5B-userdebug
radxa:rock-android12 $ ./build.sh -UACKup
# get images from IMAGE directory
</code>

==== Step by step Build ====
If you dont' want to use "Use all-in-one build script", you can follow this way to build image step by step.

===== Setup board environment =====
<code bash>
# for Rock 5B
radxa:rock-android12 $ export PRODUCT_NAME="RadxaRock5B"
radxa:rock-android12 $ export PRODUCT_UBOOT_CONFIG="rk3588"
radxa:rock-android12 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig"
radxa:rock-android12 $ export PRODUCT_KERNEL_DTS="rk3588-rock-5b"
</code>

===== Build u-boot =====
<code bash>
radxa:rock-android12 $ cd u-boot
radxa:rock-android12/u-boot $ make clean
radxa:rock-android12/u-boot $ make mrproper
radxa:rock-android12/u-boot $ make distclean
radxa:rock-android12/u-boot $ ./make.sh ${PRODUCT_UBOOT_CONFIG}
radxa:rock-android12 $ cd -
</code>
The generated images are '''idbloader.img''' , and '''uboot.img'''
===== Building kernel =====
Android 12.0 cannot directly burn kernel.img and resource.img, kernel.img and resource.img are included in boot.img
<code bash>
radxa:rock-android12 $ cd kernel-5.10
radxa:rock-android12/kernel-5.10 $ export PATH=../prebuilts/clang/host/linux-x86/clang-r416183b/bin:$PATH
radxa:rock-android12/kernel-5.10 $ alias msk='make CROSS_COMPILE=aarch64-linux-gnu- LLVM=1 LLVM_IAS=1'
radxa:rock-android12/kernel-5.10 $ msk ARCH=arm64 rockchip_defconfig android-11.config rock5b.config
radxa:rock-android12/kernel-5.10 $ msk ARCH=arm64 BOOT_IMG=../rockdev/Image-RadxaRock5B/boot.img rk3588-rock-5b.img

radxa:rock-android12 $ cd -
</code>
After compiling, you can directly burn the boot.img in the kernel-5.10 directory to the boot location of the machine. Please load the partition table first when burning (parameter.txt), so as not to burn the wrong location.

===== Building AOSP =====
<code bash>
radxa:rock-android12 $ source build/envsetup.sh
radxa:rock-android12 $ lunch ${PRODUCT_NAME}-userdebug
radxa:rock-android12 $ make -j$(nproc)
</code>
It takes a long time, take a break and wait...

===== Make images =====
<code bash>
radxa:rock-android12 $ rm -rf rockdev
radxa:rock-android12 $ ln -s RKTools/linux/Linux_Pack_Firmware/rockdev .
radxa:rock-android12 $ ./mkimage.sh
</code>

===== Pack Image =====
<code bash>
radxa:rock-android12 $ cd rockdev
radxa:rock-android12/rockdev $ rm -rf Image
radxa:rock-android12/rockdev $ ln -s Image-${PRODUCT_NAME} Image

</code>

1. RkUpdate Image
<code>
radxa:rock-android12/rockdev $ ./mkupdate.sh rk3588 Image
</code>
The images under rockdev/ are `update.img`

2. gpt Image
<code bash>
radxa:rock-android12/rockdev $ ./android-gpt.sh
</code>

Rock5/guide/android12

2023-04-20T01:47:56Z

Yanw: /* Building kernel */

This page is a step-by-step tutorial how to build Rock 5 serail board Android12 image.

=== Repo ===
<code bash>
radxa$ wget 'https://storage.googleapis.com/git-repo-downloads/repo' -P /tmp/
radxa$ sudo cp /tmp/repo /usr/local/bin/repo
radxa$ sudo chmod +x /usr/local/bin/repo
</code>

In China Download Repo:
<code bash>
radxa$ echo "export REPO_URL='https://mirrors.tuna.tsinghua.edu.cn/git/git-repo/'" >> ~/.bashrc
radxa$ source ~/.bashrc
radxa$ curl https://mirrors.tuna.tsinghua.edu.cn/git/git-repo -o /tmp/repo
radxa$ sudo cp /tmp/repo /usr/local/bin/repo
radxa$ sudo chmod +x /usr/local/bin/repo
</code>

=== DockerFile ===
<code>
FROM ubuntu:xenial

RUN apt-get update -y && apt-get install -y openjdk-8-jdk python git-core gnupg flex bison gperf build-essential \
zip curl liblz4-tool zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 \
lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache \
libgl1-mesa-dev libxml2-utils xsltproc unzip mtools u-boot-tools \
htop iotop sysstat iftop pigz bc device-tree-compiler lunzip \
dosfstools vim-common parted udev libssl-dev python3 python-pip lzop swig

#### For China
RUN curl https://mirrors.tuna.tsinghua.edu.cn/git/git-repo > /usr/local/bin/repo && \
chmod +x /usr/local/bin/repo && \
which repo
ENV REPO_URL='https://mirrors.tuna.tsinghua.edu.cn/git/git-repo/'
#### For China End

RUN pip install pycrypto
ENV USER=android12-docker
ARG USER_ID=0
ARG GROUP_ID=0
RUN groupadd -g ${GROUP_ID} jenkins-docker && useradd -m -g jenkins-docker -u ${USER_ID} android12-docker

USER android12-docker
</code>

Build DockerFile
<code>
radxa$ docker build -t android-builder:12.x --build-arg USER_ID=`id -u` --build-arg GROUP_ID=`id -g` $(which-dir-dockerfile-in)
</code>

=== Download source code ===
<code bash>
$ mkdir rock-android12
$ cd rock-android12
</code>
Then run:
<code bash>
radxa:rock-android12 $ repo init -u https://github.com/radxa/manifests.git -b Android12_RK3588_Radxa_rk8 -m rockchip-s-release.xml
radxa:rock-android12 $ repo sync -d --no-tags -j4
</code>

=== Build ===
==== Use all-in-one build script ====

<code bash>
radxa:rock-android12 $ source build/envsetup.sh
radxa:rock-android12 $ lunch RadxaRock5B-userdebug
radxa:rock-android12 $ ./build.sh -UACKup
# get images from IMAGE directory
</code>

==== Step by step Build ====
If you dont' want to use "Use all-in-one build script", you can follow this way to build image step by step.

===== Setup board environment =====
<code bash>
# for Rock 5B
radxa:rock-android12 $ export PRODUCT_NAME="RadxaRock5B"
radxa:rock-android12 $ export PRODUCT_UBOOT_CONFIG="rk3588"
radxa:rock-android12 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig"
radxa:rock-android12 $ export PRODUCT_KERNEL_DTS="rk3588-rock-5b"
</code>

===== Build u-boot =====
<code bash>
radxa:rock-android12 $ cd u-boot
radxa:rock-android12/u-boot $ make clean
radxa:rock-android12/u-boot $ make mrproper
radxa:rock-android12/u-boot $ make distclean
radxa:rock-android12/u-boot $ ./make.sh ${PRODUCT_UBOOT_CONFIG}
radxa:rock-android12 $ cd -
</code>
The generated images are '''idbloader.img''' , and '''uboot.img'''
===== Building kernel =====
Android 12.0 cannot directly burn kernel.img and resource.img, kernel.img and resource.img are included in boot.img
<code bash>
radxa:rock-android12 $ cd kernel-5.10
radxa:rock-android12/kernel-5.10 $ export PATH=../prebuilts/clang/host/linux-x86/clang-r416183b/bin:$PATH
radxa:rock-android12/kernel-5.10 $ alias msk='make CROSS_COMPILE=aarch64-linux-gnu- LLVM=1 LLVM_IAS=1'
radxa:rock-android12/kernel-5.10 $ msk ARCH=arm64 rockchip_defconfig android-11.config rock5b.config
radxa:rock-android12/kernel-5.10 $ msk ARCH=arm64 BOOT_IMG=../rockdev/Image-RadxaRock5B/boot.img rk3588-rock-5b.img

radxa:rock-android12 $ cd -
</code>
After compiling, you can directly burn the boot.img in the kernel-5.10 directory to the boot location of the machine. Please load the partition table first when burning (parameter.txt), so as not to burn the wrong location.

===== Building AOSP =====
<code bash>
radxa:rock-android12 $ source build/envsetup.sh
radxa:rock-android12 $ lunch ${PRODUCT_NAME}-userdebug
radxa:rock-android12 $ make -j$(nproc)
</code>
It takes a long time, take a break and wait...

===== Make images =====
<code bash>
radxa:rock-android12 $ rm -rf rockdev
radxa:rock-android12 $ ln -s RKTools/linux/Linux_Pack_Firmware/rockdev .
radxa:rock-android12 $ ./mkimage.sh
</code>

===== Pack Image =====
<code bash>
radxa:rock-android12 $ cd rockdev
radxa:rock-android12/rockdev $ rm -rf Image
radxa:rock-android12/rockdev $ ln -s Image-${PRODUCT_NAME} Image

</code>

1. RkUpdate Image
<code>
radxa:rock-android12/rockdev $ ./mkupdate.sh rk3588 Image
</code>
The images under rockdev/ are `update.img`

2. gpt Image
<code bash>
radxa:rock-android12/rockdev $ ./android-gpt.sh
</code>

Rock5/guide/Touch Screen Portable Monitor

2023-04-12T11:01:31Z

Yanw: /* FAQ */

This page is how rock5 created the IDC file for Touch Screen Portable Monitor

===What is idc?===
idc (Input Device Configuration) is an input device configuration file, which contains device-specific configuration attributes that affect the behavior of the input device. For touch screen devices, an idc file is always required to define its behavior.

===How to edit IDC files===

Confirm the VID and PID of the Touch Screen.

$ lsusb
Bus 002 Device 005: ID 27c0:0858

Name the IDC file according to the ID.
$ ls /system/usr/idc
Vendor_27c0_Product_0858.idc

Edit IDC file

$ cat Vendor_27c0_Product_0858.idc
touch.deviceType = touchScreen
device.internal= 1
touch.orientationAware = 1
keyboard.layout = Vendor_27c0_Product_0858
keyboard.orientationAware = 1
cursor.mode = navigation
cursor.orientationAware = 1

The specific attribute configuration of the file can refer to https://source.android.com/docs/core/interaction/input/input-device-configuration-files

===How to load IDC file===
Create an IDC file under the device/rockchip/rk3588 directory of the SDK.

$ vim Vendor_27c0_Product_0858.idc

Add in the device.mk file.
PRODUCT_COPY_FILES += $(LOCAL_PATH)/Vendor_27c0_Product_0858.idc:$(TARGET_COPY_OUT_SYSTEM)/usr/idc/Vendor_27c0_Product_0858.idc

Recompile the firmware.
$ source build/envsetup.sh
$ lunch ${PRODUCT_NAME}-userdebug
$ ./build.sh -Au

===FAQ===
how to rotate the screen.
Modify the value of SF_PRIMARY_DISPLAY_ORIENTATION in device/rockchip/rk3588/BoardConfig.mk

- SF_PRIMARY_DISPLAY_ORIENTATION := 0
+ SF_PRIMARY_DISPLAY_ORIENTATION := 270
The touch screen cannot rotate with the screen.
Add a patch to the framework/native directory,the content is as follows

diff --git a/services/inputflinger/reader/mapper/TouchInputMapper.cpp b/services/inputflinger/reader/mapper/TouchInputMapper.cpp
index decbea4c3e..42c4612159 100644
--- a/services/inputflinger/reader/mapper/TouchInputMapper.cpp
+++ b/services/inputflinger/reader/mapper/TouchInputMapper.cpp
@@ -17,7 +17,7 @@
#include "../Macros.h"

#include "TouchInputMapper.h"
-
+#include "cutils/properties.h"
#include "CursorButtonAccumulator.h"
#include "CursorScrollAccumulator.h"
#include "TouchButtonAccumulator.h"
@@ -668,6 +668,29 @@ void TouchInputMapper::configureSurface(nsecs_t when, bool* outResetNeeded) {
if (viewportChanged) {
mViewport = *newViewport;

+ char buffer_orientation[270];
+ memset(buffer_orientation, 0, sizeof(buffer_orientation));
+ property_get("persist.sys.panel.flip", buffer_orientation, "270");
+ int cmpRet = atoi(buffer_orientation);
+ ALOGE("persist.sys.hwrotation= %d",cmpRet);
+ if (cmpRet == 0)
+ {
+ mViewport.orientation = DISPLAY_ORIENTATION_0;
+ }
+
+ else if (cmpRet == 90)
+ {
+ mViewport.orientation = DISPLAY_ORIENTATION_90;
+ }
+ else if (cmpRet == 180)
+ {
+ mViewport.orientation = DISPLAY_ORIENTATION_180;
+ }
+ else if (cmpRet == 270)
+ {
+ mViewport.orientation = DISPLAY_ORIENTATION_270;
+ }
+
if (mDeviceMode == DEVICE_MODE_DIRECT || mDeviceMode == DEVICE_MODE_POINTER) {
// Convert rotated viewport to natural surface coordinates.
int32_t naturalLogicalWidth, naturalLogicalHeight;
--

Rock5/guide/Touch Screen Portable Monitor

2023-04-03T10:04:51Z

Yanw: Created page with "This page is how rock5 created the IDC file for Touch Screen Portable Monitor ===What is idc?=== idc (Input Device Configuration) is an input device configuration file, which..."

This page is how rock5 created the IDC file for Touch Screen Portable Monitor

===What is idc?===
idc (Input Device Configuration) is an input device configuration file, which contains device-specific configuration attributes that affect the behavior of the input device. For touch screen devices, an idc file is always required to define its behavior.

===How to edit IDC files===

Confirm the VID and PID of the Touch Screen.

$ lsusb
Bus 002 Device 005: ID 27c0:0858

Name the IDC file according to the ID.
$ ls /system/usr/idc
Vendor_27c0_Product_0858.idc

Edit IDC file

$ cat Vendor_27c0_Product_0858.idc
touch.deviceType = touchScreen
device.internal= 1
touch.orientationAware = 1
keyboard.layout = Vendor_27c0_Product_0858
keyboard.orientationAware = 1
cursor.mode = navigation
cursor.orientationAware = 1

The specific attribute configuration of the file can refer to https://source.android.com/docs/core/interaction/input/input-device-configuration-files

===How to load IDC file===
Create an IDC file under the device/rockchip/rk3588 directory of the SDK.

$ vim Vendor_27c0_Product_0858.idc

Add in the device.mk file.
PRODUCT_COPY_FILES += $(LOCAL_PATH)/Vendor_27c0_Product_0858.idc:$(TARGET_COPY_OUT_SYSTEM)/usr/idc/Vendor_27c0_Product_0858.idc

Recompile the firmware.
$ source build/envsetup.sh
$ lunch ${PRODUCT_NAME}-userdebug
$ ./build.sh -Au

===FAQ===
The touch screen cannot rotate with the screen.
Add a patch to the framework/native directory,the content is as follows

diff --git a/services/inputflinger/reader/mapper/TouchInputMapper.cpp b/services/inputflinger/reader/mapper/TouchInputMapper.cpp
index decbea4c3e..42c4612159 100644
--- a/services/inputflinger/reader/mapper/TouchInputMapper.cpp
+++ b/services/inputflinger/reader/mapper/TouchInputMapper.cpp
@@ -17,7 +17,7 @@
#include "../Macros.h"

#include "TouchInputMapper.h"
-
+#include "cutils/properties.h"
#include "CursorButtonAccumulator.h"
#include "CursorScrollAccumulator.h"
#include "TouchButtonAccumulator.h"
@@ -668,6 +668,29 @@ void TouchInputMapper::configureSurface(nsecs_t when, bool* outResetNeeded) {
if (viewportChanged) {
mViewport = *newViewport;

+ char buffer_orientation[270];
+ memset(buffer_orientation, 0, sizeof(buffer_orientation));
+ property_get("persist.sys.panel.flip", buffer_orientation, "270");
+ int cmpRet = atoi(buffer_orientation);
+ ALOGE("persist.sys.hwrotation= %d",cmpRet);
+ if (cmpRet == 0)
+ {
+ mViewport.orientation = DISPLAY_ORIENTATION_0;
+ }
+
+ else if (cmpRet == 90)
+ {
+ mViewport.orientation = DISPLAY_ORIENTATION_90;
+ }
+ else if (cmpRet == 180)
+ {
+ mViewport.orientation = DISPLAY_ORIENTATION_180;
+ }
+ else if (cmpRet == 270)
+ {
+ mViewport.orientation = DISPLAY_ORIENTATION_270;
+ }
+
if (mDeviceMode == DEVICE_MODE_DIRECT || mDeviceMode == DEVICE_MODE_POINTER) {
// Convert rotated viewport to natural surface coordinates.
int32_t naturalLogicalWidth, naturalLogicalHeight;
--

Rock5/guide

2023-04-03T02:58:25Z

Yanw:

Rock5/guide

2023-04-03T02:57:36Z

Yanw:

Rock5/guide/wireless

2023-03-30T06:52:26Z

Yanw: /* ADB */

This page is a step-by-step tutorial on how to use wireless ADB for the Rock 5 serial board Android12 image.

===ADB===
Confirm whether adb is installed on the computer.If not, please install it.

Linux install
<code bash>
$ sudo apt-get update
$ sudo apt-get install -y android-tools-adb
</code>

===Rock 5 serial board ===
#Make sure your Rock5 is running Android 11 (API level 30) or higher.
#Make sure your computer and Rock5 are connected to the same wireless network.

==Steps==

Enable developer options.

find settings -> About tablet -> Build number. Tap the build number option seven times until you see the message "You are now a developer!"
Return to the previous interface, in the System option you can find the developer options.

Enable Wireless debugging option

[[File:Screenshot1.png]]

Ok, now adb can connect to this device based on IP address & Port

$ adb connect 10.0.0.16:45613
$ adb devices -l
10.0.0.16:45613 device product:RadxaRock5B model:Rock5B device:RadxaRock5B transport_id:5

Rock5/guide/wireless

2023-03-30T06:47:55Z

Yanw: /* Steps */

This page is a step-by-step tutorial on how to use wireless ADB for the Rock 5 serial board Android12 image.

===ADB===
Confirm whether adb is installed on the computer.If not, please install it.

Linux install
<code bash>
$ sudo apt-get update
$ sudo apt-get install -y adb
</code>

===Rock 5 serial board ===
#Make sure your Rock5 is running Android 11 (API level 30) or higher.
#Make sure your computer and Rock5 are connected to the same wireless network.

==Steps==

Enable developer options.

find settings -> About tablet -> Build number. Tap the build number option seven times until you see the message "You are now a developer!"
Return to the previous interface, in the System option you can find the developer options.

Enable Wireless debugging option

[[File:Screenshot1.png]]

Ok, now adb can connect to this device based on IP address & Port

$ adb connect 10.0.0.16:45613
$ adb devices -l
10.0.0.16:45613 device product:RadxaRock5B model:Rock5B device:RadxaRock5B transport_id:5

Rock5/guide/wireless

2023-03-30T06:42:14Z

Yanw: Created page with "This page is a step-by-step tutorial on how to use wireless ADB for the Rock 5 serial board Android12 image. ===ADB=== Confirm whether adb is installed on the computer.If not..."

This page is a step-by-step tutorial on how to use wireless ADB for the Rock 5 serial board Android12 image.

===ADB===
Confirm whether adb is installed on the computer.If not, please install it.

Linux install
<code bash>
$ sudo apt-get update
$ sudo apt-get install -y adb
</code>

===Rock 5 serial board ===
#Make sure your Rock5 is running Android 11 (API level 30) or higher.
#Make sure your computer and Rock5 are connected to the same wireless network.

==Steps==

Enable developer options.

find settings -> About tablet -> Build number. Tap the build number option seven times until you see the message "You are now a developer!"
Return to the previous interface, in the System option you can find the developer options.

Enable Wireless debugging option

[[File:Screenshot1.png]]

Ok, now adb can connect to this device based on IP address & Port

$ adb connect 10.0.0.16:45613
$ adb shell

File:Screenshot1.png

2023-03-30T06:27:17Z

Yanw:

Rock5/guide

2023-03-30T02:18:19Z

Yanw:

Rock5/guide

2023-03-30T02:17:38Z

Yanw:

Rock5/downloads

2022-11-03T08:19:47Z

Yanw: /* Official Images */

{{rock5_header}}
{{Languages|rock5/downloads}}

__NOTOC__

Official ROCK images can also be downloaded from

* '''[http://rock.sh/rockpi-baidupan BaiduPan(China)]'''
* '''[https://github.com/radxa/debos-radxa/releases/latest ROCK 5 Image Development Build]''' - The latest system images.

For usernames and passwords please check the [https://wiki.radxa.com/Rock/FAQ#What.27s_the_user_and_password_in_Lubuntu FAQ].

==== Tools====

{| class="wikitable"
|-
! style="width: 25%; text-align:center;" | Description
! style="width: 25%; text-align:center;" | Linux
! style="width: 25%; text-align:center;" | MacOS
! style="width: 25%; text-align:center;" | Windows
|-
| Etcher - A user friendly Image Writer
| [https://github.com/balena-io/etcher/releases/download/v1.7.9/balenaEtcher-1.7.9-x64.AppImage Linux 64bit], [https://github.com/balena-io/etcher/releases/download/v1.7.9/balenaEtcher-1.7.9-ia32.AppImage Linux 32bit]
| [https://github.com/balena-io/etcher/releases/download/v1.7.9/balenaEtcher-1.7.9.dmg balenaEtcher-1.4.9.dmg]
| [https://github.com/balena-io/etcher/releases/download/v1.7.9/balenaEtcher-Setup-1.7.9.exe balenaEtcher-Setup-1.4.9-x86.exe]
|}

==== Official Images====

{| class="wikitable"
|-
! style="width: 20%; text-align:center;" | Distribution
! style="width: 20%; text-align:center;" | Supported Boards
! style="width: 60%; text-align:center;" | Description
|-
| [[File:Android-Logo.jpg | 200px | link=https://github.com/radxa/manifests]]
|
* [https://github.com/radxa/manifests/releases ROCK 5B]
|
|-
| [[File:Debian-logo.png | 200px | link=https://github.com/radxa-build]]
|
* [https://github.com/radxa/debos-radxa/releases/download/20220919-0624/rock-5b-debian-bullseye-xfce4-arm64-20220919-0912-gpt.img.xz ROCK 5B]
| Debian Product. 
[[Rock5/linux/debian | Installation Wiki]] 
Debian 11 Bullseye 
[https://github.com/radxa/debos-radxa/releases/latest Change Log].
|-
| [[File:Ubuntu_logo.png | 200px | link=https://github.com/radxa-build]]
|

* [https://github.com/radxa/debos-radxa/releases/download/20220919-0624/rock-5b-ubuntu-focal-server-arm64-20220919-0839-gpt.img.xz ROCK 5B]

| Ubuntu Server Product. 
[[Rock5/linux/ubuntu | Installation Wiki]] 
Ubuntu Server 20.04. 
[https://github.com/radxa/debos-radxa/releases/latest Change Log].
|}

==== Third Party Images====

==== Community Built Images====

Rock5/downloads

2022-11-03T08:18:58Z

Yanw: /* Official Images */

{{rock5_header}}
{{Languages|rock5/downloads}}

__NOTOC__

Official ROCK images can also be downloaded from

* '''[http://rock.sh/rockpi-baidupan BaiduPan(China)]'''
* '''[https://github.com/radxa/debos-radxa/releases/latest ROCK 5 Image Development Build]''' - The latest system images.

For usernames and passwords please check the [https://wiki.radxa.com/Rock/FAQ#What.27s_the_user_and_password_in_Lubuntu FAQ].

==== Tools====

{| class="wikitable"
|-
! style="width: 25%; text-align:center;" | Description
! style="width: 25%; text-align:center;" | Linux
! style="width: 25%; text-align:center;" | MacOS
! style="width: 25%; text-align:center;" | Windows
|-
| Etcher - A user friendly Image Writer
| [https://github.com/balena-io/etcher/releases/download/v1.7.9/balenaEtcher-1.7.9-x64.AppImage Linux 64bit], [https://github.com/balena-io/etcher/releases/download/v1.7.9/balenaEtcher-1.7.9-ia32.AppImage Linux 32bit]
| [https://github.com/balena-io/etcher/releases/download/v1.7.9/balenaEtcher-1.7.9.dmg balenaEtcher-1.4.9.dmg]
| [https://github.com/balena-io/etcher/releases/download/v1.7.9/balenaEtcher-Setup-1.7.9.exe balenaEtcher-Setup-1.4.9-x86.exe]
|}

==== Official Images====

{| class="wikitable"
|-
! style="width: 20%; text-align:center;" | Distribution
! style="width: 20%; text-align:center;" | Supported Boards
! style="width: 60%; text-align:center;" | Description
|-
| [[File:Android-Logo.jpg | 200px | link=https://github.com/radxa/manifests]]
|
* [https://github.com/radxa/manifests/releases]
|
|-
| [[File:Debian-logo.png | 200px | link=https://github.com/radxa-build]]
|
* [https://github.com/radxa/debos-radxa/releases/download/20220919-0624/rock-5b-debian-bullseye-xfce4-arm64-20220919-0912-gpt.img.xz ROCK 5B]
| Debian Product. 
[[Rock5/linux/debian | Installation Wiki]] 
Debian 11 Bullseye 
[https://github.com/radxa/debos-radxa/releases/latest Change Log].
|-
| [[File:Ubuntu_logo.png | 200px | link=https://github.com/radxa-build]]
|

* [https://github.com/radxa/debos-radxa/releases/download/20220919-0624/rock-5b-ubuntu-focal-server-arm64-20220919-0839-gpt.img.xz ROCK 5B]

| Ubuntu Server Product. 
[[Rock5/linux/ubuntu | Installation Wiki]] 
Ubuntu Server 20.04. 
[https://github.com/radxa/debos-radxa/releases/latest Change Log].
|}

==== Third Party Images====

==== Community Built Images====

Rock5/guide/android12

2022-10-08T08:56:11Z

Yanw: Created page with "This page is a step-by-step tutorial how to build Rock 5 serail board Android12 image. === Repo === <code bash> radxa$ wget 'https://storage.googleapis.com/git-repo-downl..."

This page is a step-by-step tutorial how to build Rock 5 serail board Android12 image.

=== Repo ===
<code bash>
radxa$ wget 'https://storage.googleapis.com/git-repo-downloads/repo' -P /tmp/
radxa$ sudo cp /tmp/repo /usr/local/bin/repo
radxa$ sudo chmod +x /usr/local/bin/repo
</code>

In China Download Repo:
<code bash>
radxa$ echo "export REPO_URL='https://mirrors.tuna.tsinghua.edu.cn/git/git-repo/'" >> ~/.bashrc
radxa$ source ~/.bashrc
radxa$ curl https://mirrors.tuna.tsinghua.edu.cn/git/git-repo -o /tmp/repo
radxa$ sudo cp /tmp/repo /usr/local/bin/repo
radxa$ sudo chmod +x /usr/local/bin/repo
</code>

=== DockerFile ===
<code>
FROM ubuntu:xenial

RUN apt-get update -y && apt-get install -y openjdk-8-jdk python git-core gnupg flex bison gperf build-essential \
zip curl liblz4-tool zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 \
lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache \
libgl1-mesa-dev libxml2-utils xsltproc unzip mtools u-boot-tools \
htop iotop sysstat iftop pigz bc device-tree-compiler lunzip \
dosfstools vim-common parted udev libssl-dev python3 python-pip lzop swig

#### For China
RUN curl https://mirrors.tuna.tsinghua.edu.cn/git/git-repo > /usr/local/bin/repo && \
chmod +x /usr/local/bin/repo && \
which repo
ENV REPO_URL='https://mirrors.tuna.tsinghua.edu.cn/git/git-repo/'
#### For China End

RUN pip install pycrypto
ENV USER=android12-docker
ARG USER_ID=0
ARG GROUP_ID=0
RUN groupadd -g ${GROUP_ID} jenkins-docker && useradd -m -g jenkins-docker -u ${USER_ID} android12-docker

USER android12-docker
</code>

Build DockerFile
<code>
radxa$ docker build -t android-builder:12.x --build-arg USER_ID=`id -u` --build-arg GROUP_ID=`id -g` $(which-dir-dockerfile-in)
</code>

=== Download source code ===
<code bash>
$ mkdir rock-android12
$ cd rock-android12
</code>
Then run:
<code bash>
radxa:rock-android12 $ repo init -u https://github.com/radxa/manifests.git -b Android12_RK3588_Radxa_rk8 -m rockchip-s-release.xml
radxa:rock-android12 $ repo sync -d --no-tags -j4
</code>

=== Build ===
==== Use all-in-one build script ====

<code bash>
radxa:rock-android12 $ source build/envsetup.sh
radxa:rock-android12 $ lunch RadxaRock5B-userdebug
radxa:rock-android12 $ ./build.sh -UACKup
# get images from IMAGE directory
</code>

==== Step by step Build ====
If you dont' want to use "Use all-in-one build script", you can follow this way to build image step by step.

===== Setup board environment =====
<code bash>
# for Rock 5B
radxa:rock-android12 $ export PRODUCT_NAME="RadxaRock5B"
radxa:rock-android12 $ export PRODUCT_UBOOT_CONFIG="rk3588"
radxa:rock-android12 $ export PRODUCT_KERNEL_CONFIG="rockchip_defconfig"
radxa:rock-android12 $ export PRODUCT_KERNEL_DTS="rk3588-rock-5b"
</code>

===== Build u-boot =====
<code bash>
radxa:rock-android12 $ cd u-boot
radxa:rock-android12/u-boot $ make clean
radxa:rock-android12/u-boot $ make mrproper
radxa:rock-android12/u-boot $ make distclean
radxa:rock-android12/u-boot $ ./make.sh ${PRODUCT_UBOOT_CONFIG}
radxa:rock-android12 $ cd -
</code>
The generated images are '''idbloader.img''' , and '''uboot.img'''
===== Building kernel =====
<code bash>
radxa:rock-android12 $ cd kernel-5.10
radxa:rock-android12/kernel-5.10 $ make $ADDON_ARGS ARCH=arm64 ${PRODUCT_KERNEL_CONFIG}
radxa:rock-android12/kernel-5.10 $ make $ADDON_ARGS ARCH=arm64 ${PRODUCT_KERNEL_DTS}.img -j$(nproc)

radxa:rock-android12 $ cd -
</code>

===== Building AOSP =====
<code bash>
radxa:rock-android12 $ source build/envsetup.sh
radxa:rock-android12 $ lunch ${PRODUCT_NAME}-userdebug
radxa:rock-android12 $ make -j$(nproc)
</code>
It takes a long time, take a break and wait...

===== Make images =====
<code bash>
radxa:rock-android12 $ rm -rf rockdev
radxa:rock-android12 $ ln -s RKTools/linux/Linux_Pack_Firmware/rockdev .
radxa:rock-android12 $ ./mkimage.sh
</code>

===== Pack Image =====
<code bash>
radxa:rock-android12 $ cd rockdev
radxa:rock-android12/rockdev $ rm -rf Image
radxa:rock-android12/rockdev $ ln -s Image-${PRODUCT_NAME} Image

</code>

1. RkUpdate Image
<code>
radxa:rock-android12/rockdev $ ./mkupdate.sh rk3588 Image
</code>
The images under rockdev/ are `update.img`

2. gpt Image
<code bash>
radxa:rock-android12/rockdev $ ./android-gpt.sh
</code>

Rock5/downloads

2022-09-29T09:13:47Z

Yanw: /* Official Images */

{{rock5_header}}
{{Languages|rock5/downloads}}

__NOTOC__

Official ROCK images can also be downloaded from

* '''[http://rock.sh/rockpi-baidupan BaiduPan(China)]'''
* '''[https://github.com/radxa/debos-radxa/releases/latest ROCK 5 Image Development Build]''' - The latest system images.

For usernames and passwords please check the [https://wiki.radxa.com/Rock/FAQ#What.27s_the_user_and_password_in_Lubuntu FAQ].

==== Tools====

{| class="wikitable"
|-
! style="width: 25%; text-align:center;" | Description
! style="width: 25%; text-align:center;" | Linux
! style="width: 25%; text-align:center;" | MacOS
! style="width: 25%; text-align:center;" | Windows
|-
| Etcher - A user friendly Image Writer
| [https://github.com/balena-io/etcher/releases/download/v1.7.9/balenaEtcher-1.7.9-x64.AppImage Linux 64bit], [https://github.com/balena-io/etcher/releases/download/v1.7.9/balenaEtcher-1.7.9-ia32.AppImage Linux 32bit]
| [https://github.com/balena-io/etcher/releases/download/v1.7.9/balenaEtcher-1.7.9.dmg balenaEtcher-1.4.9.dmg]
| [https://github.com/balena-io/etcher/releases/download/v1.7.9/balenaEtcher-Setup-1.7.9.exe balenaEtcher-Setup-1.4.9-x86.exe]
|}

==== Official Images====

{| class="wikitable"
|-
! style="width: 20%; text-align:center;" | Distribution
! style="width: 20%; text-align:center;" | Supported Boards
! style="width: 60%; text-align:center;" | Description
|-
| [[File:Android-Logo.jpg | 200px | link=https://github.com/radxa/manifests]]
|
* [https://github.com/radxa/manifests/releases/tag/ROCK-android12 ROCK 5B]
|
|-
| [[File:Debian-logo.png | 200px | link=https://github.com/radxa-build]]
|
* [https://github.com/radxa/debos-radxa/releases/download/20220919-0624/rock-5b-debian-bullseye-xfce4-arm64-20220919-0912-gpt.img.xz ROCK 5B]
| Debian Product. 
[[Rock5/linux/debian | Installation Wiki]] 
Debian 11 Bullseye 
[https://github.com/radxa/debos-radxa/releases/latest Change Log].
|-
| [[File:Ubuntu_logo.png | 200px | link=https://github.com/radxa-build]]
|

* [https://github.com/radxa/debos-radxa/releases/download/20220919-0624/rock-5b-ubuntu-focal-server-arm64-20220919-0839-gpt.img.xz ROCK 5B]

| Ubuntu Server Product. 
[[Rock5/linux/ubuntu | Installation Wiki]] 
Ubuntu Server 20.04. 
[https://github.com/radxa/debos-radxa/releases/latest Change Log].
|}

==== Third Party Images====

==== Community Built Images====

Rockpi4/dev/compile-a-kernel-module-on-rockpi4

2021-10-20T11:01:43Z

Yanw: /* Software Support */

{{rockpi4_header}}

{{Languages|rockpi4/dev/libmraa}}

[[rockpi4 | ROCK Pi 4]] > [[rockpi4/dev | Development]] > [[rockpi4/dev/compile-a-kernel-module-on-rockpi4 | Compile a kernel module on ROCK Pi 4]]

=== Description ===

This guide is for compiling a kernel module for ROCK Pi 4 on ROCK Pi 4 board. You can use system images [https://dl.radxa.com/rockpi4/images/debian/ Debian] and [https://dl.radxa.com/rockpi4/images/ubuntu/ Ubuntu].

=== Software Support ===

For kernel, you need to upgrade to at least '''4.4.154-98-rockchip''' version.

Note that the latest U-boot and Kernel packages are in '''Radxa APT''' '''stretch-testing''' and '''bionic-testing''' repositories.

Also, you need to update rockchip-fstab, rockchip-overlay, u-boot packages. And [[rockpi4/radxa-apt | Radxa APT]] helps.

=== Example: r8152 device driver===

Here take r8152 device driver as an example.

Install necessary packages.

$ sudo apt-get install -y libssl-dev build-essential

Recompile dependent libraries.

$ cd /usr/src/linux-headers-$(uname -r)
$ make scripts

Download [https://github.com/wget/realtek-r8152-linux/archive/master.zip r8152 driver source code] to ROCK Pi 4 and extract it to home directory.

Go to the top-level directory of the source code

$ cd realtek-r8152-linux-master
$ ls
50-usb-realtek-net.rules compatibility.h Makefile r8152.c ReadMe.txt

Generate r8152.ko file.

$ make

Check kernel release and processor
$ uname -rp
4.4.154-98-rockchip-gcbc3da2ca32c aarch64

Check r8152 ko information

$ modinfo r8152.ko
filename: /home/rock/r8152_2.12.0/r8152.ko
version: v2.12.0 (2019/04/29)
license: GPL
description: Realtek RTL8152/RTL8153 Based USB Ethernet Adapters
author: Realtek nic sw <nic_swsd@realtek.com>
srcversion: 576F778ECF92A5E23120A75
...
depends:
vermagic: 4.4.154-98-rockchip-gcbc3da2ca32c SMP mod_unload aarch64

The vermagic of module should be the same as current kernel release version like 4.4.154-98-rockchip-gcbc3da2ca32c.

Install driver module to kernel.

$ sudo make install

Remove driver module.

$ sudo rmmod r8152

=== FAQs ===

=== Troubleshooting ===

If you have issue with compiling a kernel module on ROCK Pi 4, start a new post on the forum. https://forum.radxa.com/c/dev

Rockpi4/dev/kernel-mainline

2021-09-18T12:09:41Z

Yanw: /* Build kernel */

{{rockpi4_header}}

{{Languages|rockpi4/dev/kernel-mainline}}

[[rockpi4 | ROCK Pi 4]] > [[rockpi4/dev | Development]] > [[rockpi4/dev/kernel-mainline | Build mainline kernel(5.x)]]

ROCK Pi 4 is officially supported in mainline kernel since v5.1 thanks to developer Akash Gajjar from Mentor. Below is how to build it on a X86 Linux host PC and run on ROCK Pi 4.

== Please help to fix/enhance this page ==

=== Current status ===

As of 01/07/2020, these instructions are incomplete, incorrect and do not result in a working kernel. Please help to fix them.

Use [[https://forum.radxa.com/t/mainline-support-for-rockpi-4/131/91]] to discuss this page.

Tested with

* RockPI 4 A with 2GByte
* 16 GByte eMMC module (no uSD)
* Current debian (5.5.0-rc5-00039-gae6088216ce4).

Without any overlays configured, the kernel starts to boot with working console output, but then it seems to hang after the following output:

...
[ 14.670351] mmc_host mmc0: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0)
[ 14.674934] hctosys: unable to open rtc device (rtc0)

=== ID of root file system ===

The instructions show a specific PARTUUID. It seems as if the instructions should explain that the PARTUUID needs to be changed according to the PARTUUID of the boot partition on the boot device - aka: The same PARTUUID used with the 'old' radxa 4.4 kernel ?!

=== Use of overlays ===

The instructions on this page do not describe if/how overlays can be used with mainline kernel:

The instructions do not explain if overlays need to be compiled for the new kernel or not.

The instructions do not explain why overlays may fail to work, for example because all or some of the overlays do not have according entry points in the mainline kernel ?

The instructions do not explain if it is possible to configure u-boot so that there are different overlays enabled for different kernels - e.g.: all necessary overlays for the radxa 4.4 kernel and non (or others) for a mainline kernel. Is this even possible ?

Result: When attempting to use ANY overlays such as spi1-flash, the boot process fails to merge the overlays and reverts to boot the first (default) kernel instead.

The console log for this looks as follows:

...
reading /rk3399-rock-pi-4.dtb
54207 bytes read in 13 ms (4 MiB/s)
fdt addr 0000000008300000
fdt magic number edfe0dd0
fdt size 1048576
merge_dts_overlay
Retrieving file: /overlays/spi1-flash.dtbo
reading /overlays/spi1-flash.dtbo
765 bytes read in 11 ms (67.4 KiB/s)
overlay dtb(0x0000000008200000) is valid
fdt_overlay_apply 0000000008300000 0000000008200000
fdt_overlay_apply(): FDT_ERR_NOTFOUND
Can't load dts overlay
Can not merge dts overlay
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
...

=== Loadable modules ===

The kernel will need dynamically loaded modules. These need to be installed into /lib/modules/<kernel-name>.

It is unclear how to best do this when compiling on a separate PC (cross-compilation as explained).

When compiling locally on the Rock PI 4, this is easily achied by using "make modules_install".

=== Already fixed ===

01/07/2020 Added explanations how to add new kernel to existing boot file and choose from serial console during boot.

== Build kernel on linux PC ==

=== Requirement ===

$ sudo apt-get install libncurses-dev flex bison libssl-dev git

=== Get the mainline kernel source ===

$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux

=== Install toolchain from Linaro ===

$ wget https://releases.linaro.org/components/toolchain/binaries/7.3-2018.05/aarch64-linux-gnu/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz
$ sudo tar xvf gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz -C /usr/local/
$ export ARCH=arm64
$ export CROSS_COMPILE=/usr/local/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-

=== Build kernel===

$ make defconfig
$ make -j6

Copy '''arch/arm64/boot/Image''' and '''arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtb''' to your ROCK Pi 4.

== Install it on ROCK Pi 4.==

=== Copy files ===

$ sudo cp Image rk3399-rock-pi-4.dtb /boot/

=== Configure and Reboot ===

$ sudo vim /boot/extlinux/extlinux.conf

Add an entry as follows:

label kernel-mainline
kernel /Image
fdt /rk3399-rock-pi-4.dtb
append earlycon=uart8250,mmio32,0xff1a0000 swiotlb=1 coherent_pool=1m earlyprintk console=ttyS2,1500000n8 rw root=PARTUUID=b921b045-1d rootfstype=ext4 init=/sbin/init rootwait

Reboot you will have the new kernel booting.

If you have a serial console connected to the Rock PI 4, you can also add this kernel as a second or further boot entry and then select it during the bootstrap process as follows:

...
Retrieving file: /extlinux/extlinux.conf
reading /extlinux/extlinux.conf
956 bytes read in 17 ms (54.7 KiB/s)
select kernel
1: kernel-4.4.154-100-rockchip-gf7c3df9923c2
2: kernel-mainline
Enter choice: 2
...
...
2: kernel-mainline
Retrieving file: /Image
reading /Image

You need to be fast typing the desired number (2).

The benefit of this approach is that the bootstrap process will automatically revert booting the first (working radxa) kernel when the newly built kernel fails to boot - or that you can simply power cycle to boot the working kernel in case the newly built kernel does not work.

Rockpi4/dev/Debian

2021-09-16T11:38:59Z

Yanw: /* Install other build tools */

{{rockpi4_header}}

{{Languages|rockpi4/dev/Debian}}

[[rockpi4 | ROCK Pi 4]] > [[rockpi4/dev | Development]] > [[rockpi4/dev/Debian | Build Debian]]

=== Rockchip Debian SDK ===

Below is the instructions of how to build image for ROCK Pi 4 on a '''HOST PC'''.

==== Get the source code ====

You need Git to get multiple git repositories to build the image.

Install Git if you don't have it.

sudo apt-get update
sudo apt-get install git

Clone the source code

git clone -b master https://github.com/radxa/rockchip-bsp.git
cd rockchip-bsp
git submodule init
git submodule update

You will get

build kernel README.md rkbin rootfs u-boot

Directories usage introductions:

* build:
** Some script files and configuration files for building u-boot, kernel and rootfs.
* kernel:
** kernel source code, current version is 4.4
* rkbin:
** Prebuilt Rockchip binaries, include first stage loader and ATF(Arm Trustzone Firmware).
* rootfs:
** Bootstrap a Debian based rootfs, support architechture armhf and arm64, support Debian Jessie, Stretch and Buster.
* u-boot:
** u-boot as the second stage bootloader

==== Update the source code ====

The rockchip-bsp will be updated all the time, so you can update the source before building the system image.

cd rockchip-bsp
git checkout master
git fetch origin
git rebase origin/master
git submodule update

==== Install toolchain from Linaro ====

wget https://releases.linaro.org/components/toolchain/binaries/7.3-2018.05/aarch64-linux-gnu/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz
sudo tar xvf gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz -C /usr/local/
export CROSS_COMPILE=/usr/local/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-
export PATH=/usr/local/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu/bin:$PATH

Check if Linaro toolchain is the default choice:

which aarch64-linux-gnu-gcc
/usr/local/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-gcc

==== Install other build tools ====

sudo apt-get install gcc-aarch64-linux-gnu device-tree-compiler libncurses5 libncurses5-dev build-essential libssl-dev mtools
sudo apt-get install bc python dosfstools

If it appears that it cannot be installed. You can try the following method
sudo apt-get install aptitude
sudo aptitude install bc python dosfstools

==== Build u-boot ====

./build/mk-uboot.sh rockpi4b #For ROCK Pi 4 Mode B

The generated images will be copied to out/u-boot folder

ls out/u-boot/
idbloader.img rk3399_loader_v1.12.112.bin trust.img uboot.img

==== Build kernel ====
Build kernel with default '''rockchip_linux_defconfig'''

./build/mk-kernel.sh rockpi4b #For ROCK Pi 4 Mode B

===== Change kernel config(optional)=====

Optionally, if you want to change the default kernel config

cd kernel
export ARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu-
make rockchip_linux_defconfig
make menuconfig
cd ..
./build/mk-kernel.sh rockpi4b #For ROCK Pi 4 Mode B

You will get the kernel image and dtb file

ls out/kernel/
Image rockpi-4b-linux.dtb

==== Make rootfs image ====

Check out the rootfs source. The repository is '''https://github.com/radxa/rk-rootfs-build.git''' and the branch is '''debian'''.

To build 32bit rootfs:

export ARCH=armhf

To build 64bit rootfs:

export ARCH=arm64

Building a base debian system by ubuntu-build-service from linaro.

cd rootfs
sudo apt-get install binfmt-support qemu-user-static cpio gdisk
sudo dpkg -i ubuntu-build-service/packages/* # ignore the broken dependencies, we will fix it next step
sudo apt-get install -f
RELEASE=buster TARGET=desktop ARCH=arm64 ./mk-base-debian.sh

This will bootstrap a Debian Buster image, you will get a rootfs tarball named '''linaro-buster-alip-xxxx.tar.gz'''.

Building the rk-debian rootfs.

RELEASE=buster ARCH=arm64 ./mk-rootfs.sh

Creating the ext4 image(linaro-rootfs.img):

./mk-image.sh

==== Combine everything into one image ====

build/mk-image.sh -c rk3399 -b rockpi4 -t system -r rootfs/linaro-rootfs.img

This will combine u-boot, kernel and rootfs into one image and generate GPT partition table. Output is

out/system.img

==== Flash the image ====

For normal users, follow instructions [[Rockpi4/install | here]]. You will need the generated '''out/system.img''' only.

For developers, flash from USB OTG port, follow instructions [[Rockpi4/dev/usb-install |here]]. You will need the flash helper '''rk3399_loader_xxx.bin''' and generated '''out/system.img''' files.

==== Troubleshooting ====

Check [[Rockpi4/FAQs |ROCK Pi 4 FAQs]] first, if it doesn't help, start a new post on the forum https://forum.radxa.com/c/dev

Rock3/Debian

2021-09-10T10:00:30Z

Yanw: /* Bluetooth */

{{rock3_header}}

{{Languages|rock3/Debian}}

[[rock3 | ROCK 3]] > [[rock3/Debian | Debian]]

__TOC__

== Work with ROCK 3 Debian ==

=== Introduction to ROCK 3 Debian ===

ROCK 3 Debian is an easy to use desktop system. While working with ROCK 3 Debian, you will find it do well on playing music, Internet, Bluetooth, AI and so on.

ROCK 3 Debian uses '''systemd''' to manage system.

Command prepended by $ means the command may be executed by an unprivileged user. And command prepended by # means the command may be executed by an privileged user. But the symbol, $ or #, is not part of the command.

=== Access from the Host PC/Laptop ===

==== Option 1: Serial console ====

Check [[rock3/dev/serial-console | Serial Console]]

==== Option 2: SSH ====
SSH server is enabled on port 22 of ROCK 3 default image.

Please use [https://angryip.org/ angryip] to find your board IP address.

$ ping ip-of-device
$ ssh rock@ip-of-device

=== Debian Default User Account ===

Non-root User:

User Name : rock
Password : rock

===Desktop ===

The preinstalled Desktop is xfce4.

=== Install and update necessary packages ===

Add Radxa APT, see [[rock3/radxa-apt | Radxa APT]].

Install packages;

$ sudo apt-get update
$ sudo apt-get install -y rockchip-overlay
$ sudo apt-get install -y linux-4.4-rock-3-latest

=== Network Connection ===

There are two methods for network connection. One is Ethernet and the other is WIFI.

==== Ethernet Connection ====
You can use a network cable (one end connected to the external network port or route) to connect your ROCK 3 to the network. The ROCK 3 will automatically configure the network for your surfing on the Internet.

===== To test the Ethernet, we need to follow the steps: =====
* Switch to super user mode by command
$ sudo su

* Check whether the Ethernet is normal by command, ifconfig, which would show us a network card, eth0, and the Ethernet IP address. Also, use tool, ping, to connect to a normal domain.

$ ifconfig
$ ping www.baidu.com

* If failed to connect to a normal domain. , try

$ sudo dhclient eth0

==== WIFI Connection ====

When there is not a network cable for your ROCK 3 the WIFI connection is another good choice. ROCK Pi N10 supports 2.4G/5G WIFI and WIFI 6 wireless network.

=====To test the WIFI performance, we need to follow the steps:=====

* Switch to super user mode
$ sudo su

* Open the WIFI
$ nmcli r wifi on

* Scan WIFI
$ nmcli dev wifi

* Connect to WIFI network
$ nmcli dev wifi connect "wifi_name" password "wifi_password"

* Test WIFI perpormance by tool iperf.

===Bluetooth===
*Update necessary packages.
root@rock3a:~# apt-get update
root@rock3a:~# apt-get install broadcom-wifibt-firmware
*Check Bluetooth service.
root@rock3a:~# systemctl status bluetooth
*Run Bluetooth service if the Bluetooth service is inactive.
root@rock3a:~# systemctl start bluetooth
*Check Bluetooth device.
root@rock3a:~# hciconfig
hci0: Type: Primary Bus: UART
BD Address: 10:2C:6B:49:D5:53 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:850 acl:0 sco:0 events:58 errors:0
TX bytes:2814 acl:0 sco:0 commands:58 errors:0
*Example: Connect to Bluetooth Speaker.
*Install pulseaudio packages.
root@rock3a:~# apt-get install -y pulseaudio-module-bluetooth pulseaudio
*Run pulseaudio.
root@rock3a:~# pulseaudio --start
*Connect using bluetoothctl.
root@rock3a:~# bluetoothctl
[bluetooth]# default-agent
[bluetooth]# power on
[bluetooth]# scan on
[bluetooth]# trust 77:EC:79:4F:6B:AC
[bluetooth]# pair 77:EC:79:4F:6B:AC
[bluetooth]# connect 77:EC:79:4F:6B:AC
*Play songs and enjoy it.

=== Check DDR size ===
ROCK 3 has several different DDR sizes, such as 2G, 4G, 8G.
$ free -h
total used free shared buff/cache available
Mem: '''7.4Gi''' 72Mi 7.1Gi 16Mi 182Mi 7.2Gi
Swap: 0B 0B 0B

For example, the size of DDR on this board is 8G.

=== Storage device ===
* eMMC: /dev/mmcblk0
* uSD Card: /dev/mmcblk1
* NVME M.2 SDD: /dev/nvme0n1

=== Test RTC Device ===
First, plug in RTC battery and power on.Check the rtc device:
root@rock3a:~# dmesg | grep rtc
[ 0.749597] rk808-rtc rk808-rtc: registered as rtc0
[ 0.751404] rk808-rtc rk808-rtc: setting system clock to 2017-08-04 09:00:02 UTC (1501837202)

Second, use the follow commands to set the system time and synchronization to the rtc clock.
$ date -s "2021-08-17 20:03:00"
$ hwclock -w
$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:00:04.745124+00:00
$ poweroff
and then disconnect the power supply
Third, back to power after 10 mins and check whether the rtc clock run the same time
$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:10:14.745124+00:00

=== Test Audio Player===
Download a wav audio file, and use the command to test the HP player.

$ amixer -c 1 cset numid=1 3
numid=1,iface=MIXER,name='Playback Path'
; type=ENUMERATED,access=rw------,values=1,items=11
; Item #0 'OFF'
; Item #1 'RCV'
; Item #2 'SPK'
; Item #3 'HP'
; Item #4 'HP_NO_MIC'
; Item #5 'BT'
; Item #6 'SPK_HP'
; Item #7 'RING_SPK'
; Item #8 'RING_HP'
; Item #9 'RING_HP_NO_MIC'
; Item #10 'RING_SPK_HP'
: values=3

$ aplay -D plughw:1,0 test.wav
Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo

To test the Mic recordding， please follow：
$ amixer -c 1 cset numid=2 1
$ arecord -Dhw:1,0 -d 10 -f cd -r 44100 -c 2 -t wav ./mic_test.wav #this is a record command
Recording WAVE './mic_test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
$ aplay -D plughw:1,0 mic_test.wav

=== Test USB Host ===
Plug in the U dish and use the command by serial console.
$ '''dmesg | tail'''
[ 133.773558] usb 2-1: SerialNumber: CCYYB18M1CFKO4H4
[ 133.774332] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 133.774657] scsi host0: usb-storage 2-1:1.0
[ 134.841096] scsi 0:0:0:0: Direct-Access aigo U350 1100 PQ: 0 ANSI: 6
[ 134.846394] sd 0:0:0:0: [sda] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
[ 134.847554] sd 0:0:0:0: [sda] Write Protect is off
[ 134.847635] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 134.848824] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
'''[ 134.858173] sda: sda1'''
[ 134.861161] sd 0:0:0:0: [sda] Attached SCSI removable disk

$ '''sudo mount /dev/sda1 /mnt'''
$ '''lsblk'''
root@linaro-alip:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 14.7G 0 disk
└─sda1 8:1 1 14.7G 0 part /mnt
If /dev/sda1 is successfully mounted, this usb host is working properly.

===Test fan on / off===
Please execute with root permission

echo 0 > /sys/class/pwm/pwmchip0/export
echo 10000 > /sys/class/pwm/pwmchip0/pwm0/period
echo 5000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle
echo normal > /sys/class/pwm/pwmchip0/pwm0/polarity

echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable // on
echo 0 > /sys/class/pwm/pwmchip0/pwm0/enable // off

=== Changelogs ===

==== 2021.08.24 ====

'''rock3a_debian_buster_xfce4_arm64_20210824_0136-gpt.img'''

* Kernel version: 4.19.193-2-rockchip-g7cf7399ddb5c
* U-Boot version: 2017.09-gbd2fa07970e-210525

Rock3/Ubuntu

2021-09-10T10:00:05Z

Yanw: /* Bluetooth */

{{rock3_header}}

{{Languages|rock3/Ubuntu}}

[[rock3 | ROCK 3]] > [[rock3/Ubuntu | Ubuntu]]

__TOC__

== Work with ROCK 3 Ubuntu ==

=== Introduction to ROCK 3 Ubuntu ===

ROCK 3 Ubuntu server is an easy to use system. While working with ROCK 3 Ubuntu Server, you will find it do well on playing music, Internet, Bluetooth, AI and so on.

ROCK 3 Ubuntu server uses '''systemd''' to manage system.

Command prepended by $ means the command may be executed by an unprivileged user. And command prepended by # means the command may be executed by an privileged user. But the symbol, $ or #, is not part of the command.

=== Access from the Host PC/Laptop ===

==== Option 1: Serial console ====

Check [[rock3/dev/serial-console | Serial Console]]

==== Option 2: SSH ====
SSH server is enabled on port 22 of ROCK 3 default image.

Please use [https://angryip.org/ angryip] to find your board IP address.

$ ping ip-of-device
$ ssh rock@ip-of-device

=== Debian Default User Account ===

Non-root User:

User Name : rock
Password : rock

=== Install and update necessary packages ===

Add Radxa APT, see [[rock3/radxa-apt | Radxa APT]].

Install packages;

$ sudo apt-get update
$ sudo apt-get install -y rockchip-overlay
$ sudo apt-get install -y linux-4.4-rock-3-latest

=== Network Connection ===

There are two methods for network connection. One is Ethernet and the other is WIFI.

==== Ethernet Connection ====
You can use a network cable (one end connected to the external network port or route) to connect your ROCK 3 to the network. The ROCK 3 will automatically configure the network for your surfing on the Internet.

===== To test the Ethernet, we need to follow the steps: =====
* Switch to super user mode by command
$ sudo su

* Check whether the Ethernet is normal by command, ifconfig, which would show us a network card, eth0, and the Ethernet IP address. Also, use tool, ping, to connect to a normal domain.

$ ifconfig
$ ping www.baidu.com

* If failed to connect to a normal domain, try

$ sudo dhclient eth0

==== WIFI Connection ====

When there is not a network cable for your ROCK 3 the WIFI connection is another good choice. ROCK 3 supports 2.4G/5G WIFI and Wi-Fi 6 wireless network.

=====To test the WIFI performance, we need to follow the steps:=====

* Switch to super user mode
$ sudo su

* Open the WIFI
$ nmcli r wifi on

* Scan WIFI
$ nmcli dev wifi

* Connect to WIFI network
$ nmcli dev wifi connect "wifi_name" password "wifi_password"

* Test WIFI perpormance by tool iperf.

===Bluetooth===
*Update necessary packages.
root@rock3a:~# apt-get update
root@rock3a:~# apt-get install broadcom-wifibt-firmware
*Check Bluetooth service.
root@rock3a:~# systemctl status bluetooth
*Run Bluetooth service if the Bluetooth service is inactive.
root@rock3a:~# systemctl start bluetooth
*Check Bluetooth device.
root@rock3a:~# hciconfig
hci0: Type: Primary Bus: UART
BD Address: 10:2C:6B:49:D5:53 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:850 acl:0 sco:0 events:58 errors:0
TX bytes:2814 acl:0 sco:0 commands:58 errors:0
*Example: Connect to Bluetooth Speaker.
*Install pulseaudio packages.
root@rock3a:~# apt-get install -y pulseaudio-module-bluetooth pulseaudio
*Run pulseaudio.
root@rock3a:~$ pulseaudio --start
*Connect using bluetoothctl.
root@rock3a:~$ bluetoothctl
[bluetooth]# default-agent
[bluetooth]# power on
[bluetooth]# scan on
[bluetooth]# trust 77:EC:79:4F:6B:AC
[bluetooth]# pair 77:EC:79:4F:6B:AC
[bluetooth]# connect 77:EC:79:4F:6B:AC
*Play songs and enjoy it.

=== Check DDR size ===
*ROCK 3 has several different DDR sizes, such as 2G, 4G, 8G.
rock@rock3a:~$ free -h
total used free shared buff/cache available
Mem: 7.4Gi 85Mi 7.2Gi 8.0Mi 168Mi 7.2Gi
Swap: 0B 0B 0B
*For example, the size of DDR on this board is 8G.

=== Storage device ===
* eMMC: /dev/mmcblk0
* uSD Card: /dev/mmcblk1
* NVME M.2 SDD: /dev/nvme0n1

=== Test RTC Device ===
*First, plug in RTC battery and power on.Check the rtc device:

rock@rock3a:~$ dmesg | grep rtc
[ 0.878676] rk808-rtc rk808-rtc: registered as rtc0
[ 0.880447] rk808-rtc rk808-rtc: setting system clock to 2017-08-04 09:00:04 UTC (1501837204)

*Second, use the follow commands to set the system time and synchronization to the rtc clock.

$ date -s "2021-08-17 20:03:00"
$ hwclock -w
$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:00:04.745124+00:00
$ poweroff

*and then disconnect the power supply
*Third, back to power after 10 mins and check whether the rtc clock run the same time

$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:10:14.745124+00:00
===Test Audio Player===
*Download a wav audio file, and use the command to test the HP player.

$ amixer -c 1 cset numid=1 3
numid=1,iface=MIXER,name='Playback Path'
; type=ENUMERATED,access=rw------,values=1,items=11
; Item #0 'OFF'
; Item #1 'RCV'
; Item #2 'SPK'
; Item #3 'HP'
; Item #4 'HP_NO_MIC'
; Item #5 'BT'
; Item #6 'SPK_HP'
; Item #7 'RING_SPK'
; Item #8 'RING_HP'
; Item #9 'RING_HP_NO_MIC'
; Item #10 'RING_SPK_HP'
: values=3

$ aplay -D plughw:1,0 test.wav
$ Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo

*To test the Mic recordding， please follow:

$ amixer -c 1 cset numid=2 1
$ arecord -Dhw:1,0 -d 10 -f cd -r 44100 -c 2 -t wav ./mic_test.wav #this is a record command
Recording WAVE './mic_test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
$ aplay -D plughw:1,0 mic_test.wav

=== Test USB Host ===
*Plug in the U dish and use the command by serial console.

rock@rock3a:~$ dmesg | tail
[11831.172069] usb 8-1: SerialNumber: CCYYXI5KH5PRSNCA
[11831.175205] usb-storage 8-1:1.0: USB Mass Storage device detected
[11831.176984] scsi host0: usb-storage 8-1:1.0
[11832.272573] scsi 0:0:0:0: Direct-Access aigo U350 1100 PQ: 0 ANSI: 6
[11832.276158] sd 0:0:0:0: [sda] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
[11832.276756] sd 0:0:0:0: [sda] Write Protect is off
[11832.276774] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[11832.277126] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[11832.285978] sda: sda1
[11832.288023] sd 0:0:0:0: [sda] Attached SCSI removable disk

rock@rock3a:~$ sudo mount /dev/sda1 /mnt
rock@rock3a:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 14.7G 0 disk
└─sda1 8:1 1 14.7G 0 part /mnt

*If /dev/sda1 is successfully mounted, this usb host is working properly.

=== Test fan on / off ===
*Please execute with root permission

root@rock3a:~# echo 0 > /sys/class/pwm/pwmchip0/export
root@rock3a:~# echo 10000 > /sys/class/pwm/pwmchip0/pwm0/period
root@rock3a:~# echo 5000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle
root@rock3a:~# echo normal > /sys/class/pwm/pwmchip0/pwm0/polarity

root@rock3a:~# echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable // on
root@rock3a:~# echo 0 > /sys/class/pwm/pwmchip0/pwm0/enable // off

=== Changelogs ===

==== 2021.08.24 ====

'''rock3a_ubuntu_focal_server_arm64_20210823_2119-gpt.img'''

* Kernel version: 4.19.193-2-rockchip-g7cf7399ddb5c
* U-Boot version: 2017.09-gbd2fa07970e-210525

Rock3/Ubuntu

2021-09-10T09:57:29Z

Yanw:

{{rock3_header}}

{{Languages|rock3/Ubuntu}}

[[rock3 | ROCK 3]] > [[rock3/Ubuntu | Ubuntu]]

__TOC__

== Work with ROCK 3 Ubuntu ==

=== Introduction to ROCK 3 Ubuntu ===

ROCK 3 Ubuntu server is an easy to use system. While working with ROCK 3 Ubuntu Server, you will find it do well on playing music, Internet, Bluetooth, AI and so on.

ROCK 3 Ubuntu server uses '''systemd''' to manage system.

Command prepended by $ means the command may be executed by an unprivileged user. And command prepended by # means the command may be executed by an privileged user. But the symbol, $ or #, is not part of the command.

=== Access from the Host PC/Laptop ===

==== Option 1: Serial console ====

Check [[rock3/dev/serial-console | Serial Console]]

==== Option 2: SSH ====
SSH server is enabled on port 22 of ROCK 3 default image.

Please use [https://angryip.org/ angryip] to find your board IP address.

$ ping ip-of-device
$ ssh rock@ip-of-device

=== Debian Default User Account ===

Non-root User:

User Name : rock
Password : rock

=== Install and update necessary packages ===

Add Radxa APT, see [[rock3/radxa-apt | Radxa APT]].

Install packages;

$ sudo apt-get update
$ sudo apt-get install -y rockchip-overlay
$ sudo apt-get install -y linux-4.4-rock-3-latest

=== Network Connection ===

There are two methods for network connection. One is Ethernet and the other is WIFI.

==== Ethernet Connection ====
You can use a network cable (one end connected to the external network port or route) to connect your ROCK 3 to the network. The ROCK 3 will automatically configure the network for your surfing on the Internet.

===== To test the Ethernet, we need to follow the steps: =====
* Switch to super user mode by command
$ sudo su

* Check whether the Ethernet is normal by command, ifconfig, which would show us a network card, eth0, and the Ethernet IP address. Also, use tool, ping, to connect to a normal domain.

$ ifconfig
$ ping www.baidu.com

* If failed to connect to a normal domain, try

$ sudo dhclient eth0

==== WIFI Connection ====

When there is not a network cable for your ROCK 3 the WIFI connection is another good choice. ROCK 3 supports 2.4G/5G WIFI and Wi-Fi 6 wireless network.

=====To test the WIFI performance, we need to follow the steps:=====

* Switch to super user mode
$ sudo su

* Open the WIFI
$ nmcli r wifi on

* Scan WIFI
$ nmcli dev wifi

* Connect to WIFI network
$ nmcli dev wifi connect "wifi_name" password "wifi_password"

* Test WIFI perpormance by tool iperf.

===Bluetooth===
*Update necessary packages.
root@rock3a:~# apt-get update
root@rock3a:~# apt-get install rcokchip-overlay
root@rock3a:~# apt-get install linux-4.19-rock-3-latest
root@rock3a:~# apt-get install broadcom-wifibt-firmware
*Check Bluetooth service.
root@rock3a:~# systemctl status bluetooth
*Run Bluetooth service if the Bluetooth service is inactive.
root@rock3a:~# systemctl start bluetooth
*Check Bluetooth device.
root@rock3a:~# hciconfig
hci0: Type: Primary Bus: UART
BD Address: 10:2C:6B:49:D5:53 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:850 acl:0 sco:0 events:58 errors:0
TX bytes:2814 acl:0 sco:0 commands:58 errors:0
*Example: Connect to Bluetooth Speaker.
*Install pulseaudio packages.
root@rock3a:~# apt-get install -y pulseaudio-module-bluetooth pulseaudio
*Run pulseaudio.
root@rock3a:~$ pulseaudio --start
*Connect using bluetoothctl.
root@rock3a:~$ bluetoothctl
[bluetooth]# default-agent
[bluetooth]# power on
[bluetooth]# scan on
[bluetooth]# trust 77:EC:79:4F:6B:AC
[bluetooth]# pair 77:EC:79:4F:6B:AC
[bluetooth]# connect 77:EC:79:4F:6B:AC
*Play songs and enjoy it.

=== Check DDR size ===
*ROCK 3 has several different DDR sizes, such as 2G, 4G, 8G.
rock@rock3a:~$ free -h
total used free shared buff/cache available
Mem: 7.4Gi 85Mi 7.2Gi 8.0Mi 168Mi 7.2Gi
Swap: 0B 0B 0B
*For example, the size of DDR on this board is 8G.

=== Storage device ===
* eMMC: /dev/mmcblk0
* uSD Card: /dev/mmcblk1
* NVME M.2 SDD: /dev/nvme0n1

=== Test RTC Device ===
*First, plug in RTC battery and power on.Check the rtc device:

rock@rock3a:~$ dmesg | grep rtc
[ 0.878676] rk808-rtc rk808-rtc: registered as rtc0
[ 0.880447] rk808-rtc rk808-rtc: setting system clock to 2017-08-04 09:00:04 UTC (1501837204)

*Second, use the follow commands to set the system time and synchronization to the rtc clock.

$ date -s "2021-08-17 20:03:00"
$ hwclock -w
$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:00:04.745124+00:00
$ poweroff

*and then disconnect the power supply
*Third, back to power after 10 mins and check whether the rtc clock run the same time

$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:10:14.745124+00:00
===Test Audio Player===
*Download a wav audio file, and use the command to test the HP player.

$ amixer -c 1 cset numid=1 3
numid=1,iface=MIXER,name='Playback Path'
; type=ENUMERATED,access=rw------,values=1,items=11
; Item #0 'OFF'
; Item #1 'RCV'
; Item #2 'SPK'
; Item #3 'HP'
; Item #4 'HP_NO_MIC'
; Item #5 'BT'
; Item #6 'SPK_HP'
; Item #7 'RING_SPK'
; Item #8 'RING_HP'
; Item #9 'RING_HP_NO_MIC'
; Item #10 'RING_SPK_HP'
: values=3

$ aplay -D plughw:1,0 test.wav
$ Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo

*To test the Mic recordding， please follow:

$ amixer -c 1 cset numid=2 1
$ arecord -Dhw:1,0 -d 10 -f cd -r 44100 -c 2 -t wav ./mic_test.wav #this is a record command
Recording WAVE './mic_test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
$ aplay -D plughw:1,0 mic_test.wav

=== Test USB Host ===
*Plug in the U dish and use the command by serial console.

rock@rock3a:~$ dmesg | tail
[11831.172069] usb 8-1: SerialNumber: CCYYXI5KH5PRSNCA
[11831.175205] usb-storage 8-1:1.0: USB Mass Storage device detected
[11831.176984] scsi host0: usb-storage 8-1:1.0
[11832.272573] scsi 0:0:0:0: Direct-Access aigo U350 1100 PQ: 0 ANSI: 6
[11832.276158] sd 0:0:0:0: [sda] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
[11832.276756] sd 0:0:0:0: [sda] Write Protect is off
[11832.276774] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[11832.277126] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[11832.285978] sda: sda1
[11832.288023] sd 0:0:0:0: [sda] Attached SCSI removable disk

rock@rock3a:~$ sudo mount /dev/sda1 /mnt
rock@rock3a:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 14.7G 0 disk
└─sda1 8:1 1 14.7G 0 part /mnt

*If /dev/sda1 is successfully mounted, this usb host is working properly.

=== Test fan on / off ===
*Please execute with root permission

root@rock3a:~# echo 0 > /sys/class/pwm/pwmchip0/export
root@rock3a:~# echo 10000 > /sys/class/pwm/pwmchip0/pwm0/period
root@rock3a:~# echo 5000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle
root@rock3a:~# echo normal > /sys/class/pwm/pwmchip0/pwm0/polarity

root@rock3a:~# echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable // on
root@rock3a:~# echo 0 > /sys/class/pwm/pwmchip0/pwm0/enable // off

=== Changelogs ===

==== 2021.08.24 ====

'''rock3a_ubuntu_focal_server_arm64_20210823_2119-gpt.img'''

* Kernel version: 4.19.193-2-rockchip-g7cf7399ddb5c
* U-Boot version: 2017.09-gbd2fa07970e-210525

Rock3/Ubuntu

2021-09-10T09:30:35Z

Yanw:

{{rock3_header}}

{{Languages|rock3/Ubuntu}}

[[rock3 | ROCK 3]] > [[rock3/Ubuntu | Ubuntu]]

__TOC__

== Work with ROCK 3 Ubuntu ==

=== Introduction to ROCK 3 Ubuntu ===

ROCK 3 Ubuntu server is an easy to use system. While working with ROCK 3 Ubuntu Server, you will find it do well on playing music, Internet, Bluetooth, AI and so on.

ROCK 3 Ubuntu server uses '''systemd''' to manage system.

Command prepended by $ means the command may be executed by an unprivileged user. And command prepended by # means the command may be executed by an privileged user. But the symbol, $ or #, is not part of the command.

=== Access from the Host PC/Laptop ===

==== Option 1: Serial console ====

Check [[rock3/dev/serial-console | Serial Console]]

==== Option 2: SSH ====
SSH server is enabled on port 22 of ROCK 3 default image.

Please use [https://angryip.org/ angryip] to find your board IP address.

$ ping ip-of-device
$ ssh rock@ip-of-device

=== Debian Default User Account ===

Non-root User:

User Name : rock
Password : rock

=== Install and update necessary packages ===

Add Radxa APT, see [[rock3/radxa-apt | Radxa APT]].

Install packages;

$ sudo apt-get update
$ sudo apt-get install -y rockchip-overlay
$ sudo apt-get install -y linux-4.4-rock-3-latest

=== Network Connection ===

There are two methods for network connection. One is Ethernet and the other is WIFI.

==== Ethernet Connection ====
You can use a network cable (one end connected to the external network port or route) to connect your ROCK 3 to the network. The ROCK 3 will automatically configure the network for your surfing on the Internet.

===== To test the Ethernet, we need to follow the steps: =====
* Switch to super user mode by command
$ sudo su

* Check whether the Ethernet is normal by command, ifconfig, which would show us a network card, eth0, and the Ethernet IP address. Also, use tool, ping, to connect to a normal domain.

$ ifconfig
$ ping www.baidu.com

* If failed to connect to a normal domain, try

$ sudo dhclient eth0

==== WIFI Connection ====

When there is not a network cable for your ROCK 3 the WIFI connection is another good choice. ROCK 3 supports 2.4G/5G WIFI and Wi-Fi 6 wireless network.

=====To test the WIFI performance, we need to follow the steps:=====

* Switch to super user mode
$ sudo su

* Open the WIFI
$ nmcli r wifi on

* Scan WIFI
$ nmcli dev wifi

* Connect to WIFI network
$ nmcli dev wifi connect "wifi_name" password "wifi_password"

* Test WIFI perpormance by tool iperf.

=== Check DDR size ===
*ROCK 3 has several different DDR sizes, such as 2G, 4G, 8G.
rock@rock3a:~$ free -h
total used free shared buff/cache available
Mem: 7.4Gi 85Mi 7.2Gi 8.0Mi 168Mi 7.2Gi
Swap: 0B 0B 0B
*For example, the size of DDR on this board is 8G.

=== Storage device ===
* eMMC: /dev/mmcblk0
* uSD Card: /dev/mmcblk1
* NVME M.2 SDD: /dev/nvme0n1

=== Test RTC Device ===
*First, plug in RTC battery and power on.Check the rtc device:

rock@rock3a:~$ dmesg | grep rtc
[ 0.878676] rk808-rtc rk808-rtc: registered as rtc0
[ 0.880447] rk808-rtc rk808-rtc: setting system clock to 2017-08-04 09:00:04 UTC (1501837204)

*Second, use the follow commands to set the system time and synchronization to the rtc clock.

$ date -s "2021-08-17 20:03:00"
$ hwclock -w
$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:00:04.745124+00:00
$ poweroff

*and then disconnect the power supply
*Third, back to power after 10 mins and check whether the rtc clock run the same time

$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:10:14.745124+00:00
===Test Audio Player===
*Download a wav audio file, and use the command to test the HP player.

$ amixer -c 1 cset numid=1 3
numid=1,iface=MIXER,name='Playback Path'
; type=ENUMERATED,access=rw------,values=1,items=11
; Item #0 'OFF'
; Item #1 'RCV'
; Item #2 'SPK'
; Item #3 'HP'
; Item #4 'HP_NO_MIC'
; Item #5 'BT'
; Item #6 'SPK_HP'
; Item #7 'RING_SPK'
; Item #8 'RING_HP'
; Item #9 'RING_HP_NO_MIC'
; Item #10 'RING_SPK_HP'
: values=3

$ aplay -D plughw:1,0 test.wav
$ Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo

*To test the Mic recordding， please follow:

$ amixer -c 1 cset numid=2 1
$ arecord -Dhw:1,0 -d 10 -f cd -r 44100 -c 2 -t wav ./mic_test.wav #this is a record command
Recording WAVE './mic_test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
$ aplay -D plughw:1,0 mic_test.wav

=== Test USB Host ===
*Plug in the U dish and use the command by serial console.

rock@rock3a:~$ dmesg | tail
[11831.172069] usb 8-1: SerialNumber: CCYYXI5KH5PRSNCA
[11831.175205] usb-storage 8-1:1.0: USB Mass Storage device detected
[11831.176984] scsi host0: usb-storage 8-1:1.0
[11832.272573] scsi 0:0:0:0: Direct-Access aigo U350 1100 PQ: 0 ANSI: 6
[11832.276158] sd 0:0:0:0: [sda] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
[11832.276756] sd 0:0:0:0: [sda] Write Protect is off
[11832.276774] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[11832.277126] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[11832.285978] sda: sda1
[11832.288023] sd 0:0:0:0: [sda] Attached SCSI removable disk

rock@rock3a:~$ sudo mount /dev/sda1 /mnt
rock@rock3a:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 14.7G 0 disk
└─sda1 8:1 1 14.7G 0 part /mnt

*If /dev/sda1 is successfully mounted, this usb host is working properly.

=== Test fan on / off ===
*Please execute with root permission

root@rock3a:~# echo 0 > /sys/class/pwm/pwmchip0/export
root@rock3a:~# echo 10000 > /sys/class/pwm/pwmchip0/pwm0/period
root@rock3a:~# echo 5000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle
root@rock3a:~# echo normal > /sys/class/pwm/pwmchip0/pwm0/polarity

root@rock3a:~# echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable // on
root@rock3a:~# echo 0 > /sys/class/pwm/pwmchip0/pwm0/enable // off

=== Changelogs ===

==== 2021.08.24 ====

'''rock3a_ubuntu_focal_server_arm64_20210823_2119-gpt.img'''

* Kernel version: 4.19.193-2-rockchip-g7cf7399ddb5c
* U-Boot version: 2017.09-gbd2fa07970e-210525

Rock3/Ubuntu

2021-09-10T07:35:55Z

Yanw: /* Test USB Host */

{{rock3_header}}

{{Languages|rock3/Ubuntu}}

[[rock3 | ROCK 3]] > [[rock3/Ubuntu | Ubuntu]]

__TOC__

== Work with ROCK 3 Ubuntu ==

=== Introduction to ROCK 3 Ubuntu ===

ROCK 3 Ubuntu server is an easy to use system. While working with ROCK 3 Ubuntu Server, you will find it do well on playing music, Internet, Bluetooth, AI and so on.

ROCK 3 Ubuntu server uses '''systemd''' to manage system.

Command prepended by $ means the command may be executed by an unprivileged user. And command prepended by # means the command may be executed by an privileged user. But the symbol, $ or #, is not part of the command.

=== Access from the Host PC/Laptop ===

==== Option 1: Serial console ====

Check [[rock3/dev/serial-console | Serial Console]]

==== Option 2: SSH ====
SSH server is enabled on port 22 of ROCK 3 default image.

Please use [https://angryip.org/ angryip] to find your board IP address.

$ ping ip-of-device
$ ssh rock@ip-of-device

=== Debian Default User Account ===

Non-root User:

User Name : rock
Password : rock

=== Install and update necessary packages ===

Add Radxa APT, see [[rock3/radxa-apt | Radxa APT]].

Install packages;

$ sudo apt-get update
$ sudo apt-get install -y rockchip-overlay
$ sudo apt-get install -y linux-4.4-rock-3-latest

=== Network Connection ===

There are two methods for network connection. One is Ethernet and the other is WIFI.

==== Ethernet Connection ====
You can use a network cable (one end connected to the external network port or route) to connect your ROCK 3 to the network. The ROCK 3 will automatically configure the network for your surfing on the Internet.

===== To test the Ethernet, we need to follow the steps: =====
* Switch to super user mode by command
$ sudo su

* Check whether the Ethernet is normal by command, ifconfig, which would show us a network card, eth0, and the Ethernet IP address. Also, use tool, ping, to connect to a normal domain.

$ ifconfig
$ ping www.baidu.com

* If failed to connect to a normal domain, try

$ sudo dhclient eth0

==== WIFI Connection ====

When there is not a network cable for your ROCK 3 the WIFI connection is another good choice. ROCK 3 supports 2.4G/5G WIFI and Wi-Fi 6 wireless network.

=====To test the WIFI performance, we need to follow the steps:=====

* Switch to super user mode
$ sudo su

* Open the WIFI
$ nmcli r wifi on

* Scan WIFI
$ nmcli dev wifi

* Connect to WIFI network
$ nmcli dev wifi connect "wifi_name" password "wifi_password"

* Test WIFI perpormance by tool iperf.

=== Check DDR size ===
*ROCK 3 has several different DDR sizes, such as 2G, 4G, 8G.
rock@rock3a:~$ free -h
total used free shared buff/cache available
Mem: 7.4Gi 85Mi 7.2Gi 8.0Mi 168Mi 7.2Gi
Swap: 0B 0B 0B
*For example, the size of DDR on this board is 8G.

=== Storage device ===
* eMMC: /dev/mmcblk0
* uSD Card: /dev/mmcblk1
* NVME M.2 SDD: /dev/nvme0n1

=== Test RTC Device ===
*First, plug in RTC battery and power on.Check the rtc device:

rock@rock3a:~$ dmesg | grep rtc
[ 0.878676] rk808-rtc rk808-rtc: registered as rtc0
[ 0.880447] rk808-rtc rk808-rtc: setting system clock to 2017-08-04 09:00:04 UTC (1501837204)

*Second, use the follow commands to set the system time and synchronization to the rtc clock.

$ date -s "2021-08-17 20:03:00"
$ hwclock -w
$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:00:04.745124+00:00
$ poweroff

*and then disconnect the power supply
*Third, back to power after 10 mins and check whether the rtc clock run the same time

$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:10:14.745124+00:00

=== Test USB Host ===
*Plug in the U dish and use the command by serial console.

rock@rock3a:~$ dmesg | tail
[11831.172069] usb 8-1: SerialNumber: CCYYXI5KH5PRSNCA
[11831.175205] usb-storage 8-1:1.0: USB Mass Storage device detected
[11831.176984] scsi host0: usb-storage 8-1:1.0
[11832.272573] scsi 0:0:0:0: Direct-Access aigo U350 1100 PQ: 0 ANSI: 6
[11832.276158] sd 0:0:0:0: [sda] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
[11832.276756] sd 0:0:0:0: [sda] Write Protect is off
[11832.276774] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[11832.277126] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[11832.285978] sda: sda1
[11832.288023] sd 0:0:0:0: [sda] Attached SCSI removable disk

rock@rock3a:~$ sudo mount /dev/sda1 /mnt
rock@rock3a:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 14.7G 0 disk
└─sda1 8:1 1 14.7G 0 part /mnt

*If /dev/sda1 is successfully mounted, this usb host is working properly.

=== Test fan on / off ===
*Please execute with root permission

root@rock3a:~# echo 0 > /sys/class/pwm/pwmchip0/export
root@rock3a:~# echo 10000 > /sys/class/pwm/pwmchip0/pwm0/period
root@rock3a:~# echo 5000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle
root@rock3a:~# echo normal > /sys/class/pwm/pwmchip0/pwm0/polarity

root@rock3a:~# echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable // on
root@rock3a:~# echo 0 > /sys/class/pwm/pwmchip0/pwm0/enable // off

=== Changelogs ===

==== 2021.08.24 ====

'''rock3a_ubuntu_focal_server_arm64_20210823_2119-gpt.img'''

* Kernel version: 4.19.193-2-rockchip-g7cf7399ddb5c
* U-Boot version: 2017.09-gbd2fa07970e-210525

Rock3/Ubuntu

2021-09-10T07:33:16Z

Yanw:

{{rock3_header}}

{{Languages|rock3/Ubuntu}}

[[rock3 | ROCK 3]] > [[rock3/Ubuntu | Ubuntu]]

__TOC__

== Work with ROCK 3 Ubuntu ==

=== Introduction to ROCK 3 Ubuntu ===

ROCK 3 Ubuntu server is an easy to use system. While working with ROCK 3 Ubuntu Server, you will find it do well on playing music, Internet, Bluetooth, AI and so on.

ROCK 3 Ubuntu server uses '''systemd''' to manage system.

Command prepended by $ means the command may be executed by an unprivileged user. And command prepended by # means the command may be executed by an privileged user. But the symbol, $ or #, is not part of the command.

=== Access from the Host PC/Laptop ===

==== Option 1: Serial console ====

Check [[rock3/dev/serial-console | Serial Console]]

==== Option 2: SSH ====
SSH server is enabled on port 22 of ROCK 3 default image.

Please use [https://angryip.org/ angryip] to find your board IP address.

$ ping ip-of-device
$ ssh rock@ip-of-device

=== Debian Default User Account ===

Non-root User:

User Name : rock
Password : rock

=== Install and update necessary packages ===

Add Radxa APT, see [[rock3/radxa-apt | Radxa APT]].

Install packages;

$ sudo apt-get update
$ sudo apt-get install -y rockchip-overlay
$ sudo apt-get install -y linux-4.4-rock-3-latest

=== Network Connection ===

There are two methods for network connection. One is Ethernet and the other is WIFI.

==== Ethernet Connection ====
You can use a network cable (one end connected to the external network port or route) to connect your ROCK 3 to the network. The ROCK 3 will automatically configure the network for your surfing on the Internet.

===== To test the Ethernet, we need to follow the steps: =====
* Switch to super user mode by command
$ sudo su

* Check whether the Ethernet is normal by command, ifconfig, which would show us a network card, eth0, and the Ethernet IP address. Also, use tool, ping, to connect to a normal domain.

$ ifconfig
$ ping www.baidu.com

* If failed to connect to a normal domain, try

$ sudo dhclient eth0

==== WIFI Connection ====

When there is not a network cable for your ROCK 3 the WIFI connection is another good choice. ROCK 3 supports 2.4G/5G WIFI and Wi-Fi 6 wireless network.

=====To test the WIFI performance, we need to follow the steps:=====

* Switch to super user mode
$ sudo su

* Open the WIFI
$ nmcli r wifi on

* Scan WIFI
$ nmcli dev wifi

* Connect to WIFI network
$ nmcli dev wifi connect "wifi_name" password "wifi_password"

* Test WIFI perpormance by tool iperf.

=== Check DDR size ===
*ROCK 3 has several different DDR sizes, such as 2G, 4G, 8G.
rock@rock3a:~$ free -h
total used free shared buff/cache available
Mem: 7.4Gi 85Mi 7.2Gi 8.0Mi 168Mi 7.2Gi
Swap: 0B 0B 0B
*For example, the size of DDR on this board is 8G.

=== Storage device ===
* eMMC: /dev/mmcblk0
* uSD Card: /dev/mmcblk1
* NVME M.2 SDD: /dev/nvme0n1

=== Test RTC Device ===
*First, plug in RTC battery and power on.Check the rtc device:

rock@rock3a:~$ dmesg | grep rtc
[ 0.878676] rk808-rtc rk808-rtc: registered as rtc0
[ 0.880447] rk808-rtc rk808-rtc: setting system clock to 2017-08-04 09:00:04 UTC (1501837204)

*Second, use the follow commands to set the system time and synchronization to the rtc clock.

$ date -s "2021-08-17 20:03:00"
$ hwclock -w
$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:00:04.745124+00:00
$ poweroff

*and then disconnect the power supply
*Third, back to power after 10 mins and check whether the rtc clock run the same time

$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:10:14.745124+00:00

=== Test USB Host ===
*Plug in the U dish and use the command by serial console.

rock@rock3a:~$ dmesg | tail
[11831.172069] usb 8-1: SerialNumber: CCYYXI5KH5PRSNCA
[11831.175205] usb-storage 8-1:1.0: USB Mass Storage device detected
[11831.176984] scsi host0: usb-storage 8-1:1.0
[11832.272573] scsi 0:0:0:0: Direct-Access aigo U350 1100 PQ: 0 ANSI: 6
[11832.276158] sd 0:0:0:0: [sda] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
[11832.276756] sd 0:0:0:0: [sda] Write Protect is off
[11832.276774] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[11832.277126] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[11832.285978]"'sda: sda1'"
[11832.288023] sd 0:0:0:0: [sda] Attached SCSI removable disk

rock@rock3a:~$ sudo mount /dev/sda1 /mnt
rock@rock3a:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 14.7G 0 disk
└─sda1 8:1 1 14.7G 0 part /mnt

*If /dev/sda1 is successfully mounted, this usb host is working properly.

=== Test fan on / off ===
*Please execute with root permission

root@rock3a:~# echo 0 > /sys/class/pwm/pwmchip0/export
root@rock3a:~# echo 10000 > /sys/class/pwm/pwmchip0/pwm0/period
root@rock3a:~# echo 5000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle
root@rock3a:~# echo normal > /sys/class/pwm/pwmchip0/pwm0/polarity

root@rock3a:~# echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable // on
root@rock3a:~# echo 0 > /sys/class/pwm/pwmchip0/pwm0/enable // off

=== Changelogs ===

==== 2021.08.24 ====

'''rock3a_ubuntu_focal_server_arm64_20210823_2119-gpt.img'''

* Kernel version: 4.19.193-2-rockchip-g7cf7399ddb5c
* U-Boot version: 2017.09-gbd2fa07970e-210525

Rock3/Ubuntu

2021-09-10T06:59:57Z

Yanw:

Rock3/Debian

2021-09-08T03:51:30Z

Yanw:

{{rock3_header}}

{{Languages|rock3/Debian}}

[[rock3 | ROCK 3]] > [[rock3/Debian | Debian]]

__TOC__

== Work with ROCK 3 Debian ==

=== Introduction to ROCK 3 Debian ===

ROCK 3 Debian is an easy to use desktop system. While working with ROCK 3 Debian, you will find it do well on playing music, Internet, Bluetooth, AI and so on.

ROCK 3 Debian uses '''systemd''' to manage system.

Command prepended by $ means the command may be executed by an unprivileged user. And command prepended by # means the command may be executed by an privileged user. But the symbol, $ or #, is not part of the command.

=== Access from the Host PC/Laptop ===

==== Option 1: Serial console ====

Check [[rock3/dev/serial-console | Serial Console]]

==== Option 2: SSH ====
SSH server is enabled on port 22 of ROCK 3 default image.

Please use [https://angryip.org/ angryip] to find your board IP address.

$ ping ip-of-device
$ ssh rock@ip-of-device

=== Debian Default User Account ===

Non-root User:

User Name : rock
Password : rock

===Desktop ===

The preinstalled Desktop is xfce4.

=== Install and update necessary packages ===

Add Radxa APT, see [[rock3/radxa-apt | Radxa APT]].

Install packages;

$ sudo apt-get update
$ sudo apt-get install -y rockchip-overlay
$ sudo apt-get install -y linux-4.4-rock-3-latest

=== Network Connection ===

There are two methods for network connection. One is Ethernet and the other is WIFI.

==== Ethernet Connection ====
You can use a network cable (one end connected to the external network port or route) to connect your ROCK 3 to the network. The ROCK 3 will automatically configure the network for your surfing on the Internet.

===== To test the Ethernet, we need to follow the steps: =====
* Switch to super user mode by command
$ sudo su

* Check whether the Ethernet is normal by command, ifconfig, which would show us a network card, eth0, and the Ethernet IP address. Also, use tool, ping, to connect to a normal domain.

$ ifconfig
$ ping www.baidu.com

* If failed to connect to a normal domain. , try

$ sudo dhclient eth0

==== WIFI Connection ====

When there is not a network cable for your ROCK 3 the WIFI connection is another good choice. ROCK Pi N10 supports 2.4G/5G WIFI and WIFI 6 wireless network.

=====To test the WIFI performance, we need to follow the steps:=====

* Switch to super user mode
$ sudo su

* Open the WIFI
$ nmcli r wifi on

* Scan WIFI
$ nmcli dev wifi

* Connect to WIFI network
$ nmcli dev wifi connect "wifi_name" password "wifi_password"

* Test WIFI perpormance by tool iperf.

===Bluetooth===
*Update necessary packages.
root@rock3a:~# apt-get update
root@rock3a:~# apt-get install rcokchip-overlay
root@rock3a:~# apt-get install linux-4.19-rock-3-latest
root@rock3a:~# apt-get install broadcom-wifibt-firmware
*Check Bluetooth service.
root@rock3a:~# systemctl status bluetooth
*Run Bluetooth service if the Bluetooth service is inactive.
root@rock3a:~# systemctl start bluetooth
*Check Bluetooth device.
root@rock3a:~# hciconfig
hci0: Type: Primary Bus: UART
BD Address: 10:2C:6B:49:D5:53 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:850 acl:0 sco:0 events:58 errors:0
TX bytes:2814 acl:0 sco:0 commands:58 errors:0
*Example: Connect to Bluetooth Speaker.
*Install pulseaudio packages.
root@rock3a:~# apt-get install -y pulseaudio-module-bluetooth pulseaudio
*Run pulseaudio.
root@rock3a:~# pulseaudio --start
*Connect using bluetoothctl.
root@rock3a:~# bluetoothctl
[bluetooth]# default-agent
[bluetooth]# power on
[bluetooth]# scan on
[bluetooth]# trust 77:EC:79:4F:6B:AC
[bluetooth]# pair 77:EC:79:4F:6B:AC
[bluetooth]# connect 77:EC:79:4F:6B:AC
*Play songs and enjoy it.

=== Check DDR size ===
ROCK 3 has several different DDR sizes, such as 2G, 4G, 8G.
$ free -h
total used free shared buff/cache available
Mem: '''7.4Gi''' 72Mi 7.1Gi 16Mi 182Mi 7.2Gi
Swap: 0B 0B 0B

For example, the size of DDR on this board is 8G.

=== Storage device ===
* eMMC: /dev/mmcblk0
* uSD Card: /dev/mmcblk1
* NVME M.2 SDD: /dev/nvme0n1

=== Test RTC Device ===
First, plug in RTC battery and power on.Check the rtc device:
root@rock3a:~# dmesg | grep rtc
[ 0.749597] rk808-rtc rk808-rtc: registered as rtc0
[ 0.751404] rk808-rtc rk808-rtc: setting system clock to 2017-08-04 09:00:02 UTC (1501837202)

Second, use the follow commands to set the system time and synchronization to the rtc clock.
$ date -s "2021-08-17 20:03:00"
$ hwclock -w
$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:00:04.745124+00:00
$ poweroff
and then disconnect the power supply
Third, back to power after 10 mins and check whether the rtc clock run the same time
$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:10:14.745124+00:00

=== Test Audio Player===
Download a wav audio file, and use the command to test.
$ aplay -D plughw:1,0 test.wav

root@rock3a:~# aplay -D plughw:1,0 6.wav
xcb_connection_has_error() returned true
Playing WAVE '6.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo

=== Test USB Host ===
Plug in the U dish and use the command by serial console.
$ '''dmesg | tail'''
[ 133.773558] usb 2-1: SerialNumber: CCYYB18M1CFKO4H4
[ 133.774332] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 133.774657] scsi host0: usb-storage 2-1:1.0
[ 134.841096] scsi 0:0:0:0: Direct-Access aigo U350 1100 PQ: 0 ANSI: 6
[ 134.846394] sd 0:0:0:0: [sda] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
[ 134.847554] sd 0:0:0:0: [sda] Write Protect is off
[ 134.847635] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 134.848824] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
'''[ 134.858173] sda: sda1'''
[ 134.861161] sd 0:0:0:0: [sda] Attached SCSI removable disk

$ '''sudo mount /dev/sda1 /mnt'''
$ '''lsblk'''
root@linaro-alip:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 14.7G 0 disk
└─sda1 8:1 1 14.7G 0 part /mnt
If /dev/sda1 is successfully mounted, this usb host is working properly.

===Test fan on / off===
Please execute with root permission

echo 0 > /sys/class/pwm/pwmchip0/export
echo 10000 > /sys/class/pwm/pwmchip0/pwm0/period
echo 5000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle
echo normal > /sys/class/pwm/pwmchip0/pwm0/polarity

echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable // on
echo 0 > /sys/class/pwm/pwmchip0/pwm0/enable // off

=== Changelogs ===

==== 2021.08.24 ====

'''rock3a_debian_buster_xfce4_arm64_20210824_0136-gpt.img'''

* Kernel version: 4.19.193-2-rockchip-g7cf7399ddb5c
* U-Boot version: 2017.09-gbd2fa07970e-210525

Rock3/Debian

2021-09-07T02:18:53Z

Yanw:

{{rock3_header}}

{{Languages|rock3/Debian}}

[[rock3 | ROCK 3]] > [[rock3/Debian | Debian]]

__TOC__

== Work with ROCK 3 Debian ==

=== Introduction to ROCK 3 Debian ===

ROCK 3 Debian is an easy to use desktop system. While working with ROCK 3 Debian, you will find it do well on playing music, Internet, Bluetooth, AI and so on.

ROCK 3 Debian uses '''systemd''' to manage system.

Command prepended by $ means the command may be executed by an unprivileged user. And command prepended by # means the command may be executed by an privileged user. But the symbol, $ or #, is not part of the command.

=== Access from the Host PC/Laptop ===

==== Option 1: Serial console ====

Check [[rock3/dev/serial-console | Serial Console]]

==== Option 2: SSH ====
SSH server is enabled on port 22 of ROCK 3 default image.

Please use [https://angryip.org/ angryip] to find your board IP address.

$ ping ip-of-device
$ ssh rock@ip-of-device

=== Debian Default User Account ===

Non-root User:

User Name : rock
Password : rock

===Desktop ===

The preinstalled Desktop is xfce4.

=== Install and update necessary packages ===

Add Radxa APT, see [[rock3/radxa-apt | Radxa APT]].

Install packages;

$ sudo apt-get update
$ sudo apt-get install -y rockchip-overlay
$ sudo apt-get install -y linux-4.4-rock-3-latest

=== Network Connection ===

There are two methods for network connection. One is Ethernet and the other is WIFI.

==== Ethernet Connection ====
You can use a network cable (one end connected to the external network port or route) to connect your ROCK 3 to the network. The ROCK 3 will automatically configure the network for your surfing on the Internet.

===== To test the Ethernet, we need to follow the steps: =====
* Switch to super user mode by command
$ sudo su

* Check whether the Ethernet is normal by command, ifconfig, which would show us a network card, eth0, and the Ethernet IP address. Also, use tool, ping, to connect to a normal domain.

$ ifconfig
$ ping www.baidu.com

* If failed to connect to a normal domain. , try

$ sudo dhclient eth0

==== WIFI Connection ====

When there is not a network cable for your ROCK 3 the WIFI connection is another good choice. ROCK Pi N10 supports 2.4G/5G WIFI and WIFI 6 wireless network.

=====To test the WIFI performance, we need to follow the steps:=====

* Switch to super user mode
$ sudo su

* Open the WIFI
$ nmcli r wifi on

* Scan WIFI
$ nmcli dev wifi

* Connect to WIFI network
$ nmcli dev wifi connect "wifi_name" password "wifi_password"

* Test WIFI perpormance by tool iperf.

=== Check DDR size ===
ROCK 3 has several different DDR sizes, such as 2G, 4G, 8G.
$ free -h
total used free shared buff/cache available
Mem: '''7.4Gi''' 72Mi 7.1Gi 16Mi 182Mi 7.2Gi
Swap: 0B 0B 0B

For example, the size of DDR on this board is 8G.

=== Storage device ===
* eMMC: /dev/mmcblk0
* uSD Card: /dev/mmcblk1
* NVME M.2 SDD: /dev/nvme0n1

=== Test RTC Device ===
First, plug in RTC battery and power on.Check the rtc device:
root@rock3a:~# dmesg | grep rtc
[ 0.749597] rk808-rtc rk808-rtc: registered as rtc0
[ 0.751404] rk808-rtc rk808-rtc: setting system clock to 2017-08-04 09:00:02 UTC (1501837202)

Second, use the follow commands to set the system time and synchronization to the rtc clock.
$ date -s "2021-08-17 20:03:00"
$ hwclock -w
$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:00:04.745124+00:00
$ poweroff
and then disconnect the power supply
Third, back to power after 10 mins and check whether the rtc clock run the same time
$ hwclock -r
root@rock3a:~# hwclock -r
2021-08-17 20:10:14.745124+00:00

=== Test Audio Player===
Download a wav audio file, and use the command to test.
$ aplay -D plughw:1,0 test.wav

root@rock3a:~# aplay -D plughw:1,0 6.wav
xcb_connection_has_error() returned true
Playing WAVE '6.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo

=== Test USB Host ===
Plug in the U dish and use the command by serial console.
$ '''dmesg | tail'''
[ 133.773558] usb 2-1: SerialNumber: CCYYB18M1CFKO4H4
[ 133.774332] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 133.774657] scsi host0: usb-storage 2-1:1.0
[ 134.841096] scsi 0:0:0:0: Direct-Access aigo U350 1100 PQ: 0 ANSI: 6
[ 134.846394] sd 0:0:0:0: [sda] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
[ 134.847554] sd 0:0:0:0: [sda] Write Protect is off
[ 134.847635] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 134.848824] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
'''[ 134.858173] sda: sda1'''
[ 134.861161] sd 0:0:0:0: [sda] Attached SCSI removable disk

$ '''sudo mount /dev/sda1 /mnt'''
$ '''lsblk'''
root@linaro-alip:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 14.7G 0 disk
└─sda1 8:1 1 14.7G 0 part /mnt
If /dev/sda1 is successfully mounted, this usb host is working properly.

===Test fan on / off===
Please execute with root permission

echo 0 > /sys/class/pwm/pwmchip0/export
echo 10000 > /sys/class/pwm/pwmchip0/pwm0/period
echo 5000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle
echo normai > /sys/class/pwm/pwmchip0/pwm0/polarity

echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable // on
echo 0 > /sys/class/pwm/pwmchip0/pwm0/enable // off

=== Changelogs ===

==== 2021.08.24 ====

'''rock3a_debian_buster_xfce4_arm64_20210824_0136-gpt.img'''

* Kernel version: 4.19.193-2-rockchip-g7cf7399ddb5c
* U-Boot version: 2017.09-gbd2fa07970e-210525