Radxa Wiki - User contributions [en]

Rockpi4/install/eMMC

2020-02-11T19:35:57Z

Raidboy: Added note about SPI interference in booting from eMMC

{{rockpi4_header}}

{{Languages|rockpi4/install/microSD}}

[[rockpi4 | ROCK Pi 4]] > [[rockpi4/install | Install]] > [[rockpi4/install/eMMC | Install on eMMC module]]

====Possible Issues====

RockPI4 v1.4 with SPI installed may have bootstrap code which is executed in before eMMC boostrap. This SPI bootstrap code may not be able to then boot third-party OS on eMMC, for example when booting an OS using MBR partition table instead of GUID partition table used by Radxa provided images. One example is the Armbian image on [[Rockpi4/downloads]] which uses MBR.

To overcome this issue, SPI bootstrap code can be disabled by connecting GPIO pins 23 with 25.

Alternatively, boot the Radxa version of debian from the download page from uSD and then excute:

$ sudo /usr/local/sbin/rockpi4b_erase_spi_flash.sh

====Step1: Requirements ====

This page describe how to download and install the image on an eMMC module and boot on ROCK Pi 4. You need at least the following.

* an eMMC module, you can buy it from radxa distributor, the eMMC module from Odroid or PINE64 also works on ROCK Pi 4. [[File:Emmc_module_top.png | 100px]] [[File:Emmc_module_bottom.png | 100px]]
* an eMMC to microSD breakout board [[File:Emmc_to_microSD_breakout_top.png | 100px]] [[File:Emmc_to_microSD_breakout_bottom.png | 100px]]

If you do not have an eMMC to μSD card converter board, you can also first install a linux system (e.g.: Debian) to a μSD Card (see [[Rockpi4/install/microSD]]) and then use the running Linux μSD System to install the desired system to the eMMC card with the eMMC card already inserted into the Rock PI 4. See below.

* a microSD card reader, either a USB card reader or the SD card reader on laptop
* a PC/laptop running Windows or Linux or MacOS

You also need the following to run on ROCK Pi 4

* ROCK Pi 4 board with power supply
* HDMI cable for display
* USB keyboard and mouse for input

====Step 2: Download necessary tools and image ====

* Etcher is the tool we use to write image. Download the right Etcher for your PC from [[Rockpi4/downloads]] page and install it. Check [[https://www.balena.io/etcher/ Etcher website]] for more info about Etcher.
* Choose the image you want to install from [[Rockpi4/downloads]] page and unzip it. The unzipped image name is like below:

rockpi4_debian_stretch_lxde_armhf_20181105_2120-gpt.img

We will use it for the writing.

====Step 3: Write the image to eMMC Module ====

3.1 Plug and click the eMMC module to the eMMC to uSD breakout board, plug the breakout board to microSD card reader. Plug the card reader on PC.

[[File:Emmc_module_on_card_reader.png]]

3.2 Run the application, for example, by executing the command on Ubuntu 16.04:

$ /bin/bash etcher-etcher-electron-1.4.5-x86_64.AppImage

3.3 In the etcher window, we click button Select image.

[[File:linux_etcher_select_image.png]]

3.4 In the etcher window, we click button Select Drive.

[[File:linux_etcher_select_driver.png]]

3.5 In the etcher window, we click button Flash.

[[File:linux_etcher_select_flash_button.png]]

3.6 In the etcher window, it shows us Flash Complete!

[[File:linux_etcher_show_complete.png]]

Done! Now you have successfully installed the OS image on eMMC module.

====Step 3 on Rock PI 4: Write the image to eMMC Module ====

If you have no eMMC to μSD card converter board, install Debian Linux (or another Linux variant) first to μSD. Insert both your μSD and the (empty) eMMC module into the Rock PI 4. Reboot it. It will boot from μSD. You can now use that Linux to download your desired OS from [[Rockpi4/downloads]] and install it onto the eMMC module. Example:

Verify that the system has booted from μSD, which should be /dev/mmcblk0p5 and that the eMMC module is found as /dev/mmcblk1:

$ dmesg | grep mmcblk
...
[...] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode.

$ ls -l /dev/mmcblk1
brw-rw---- 1 root disk 179, 0 Jan 6 13:25 /dev/mmcblk1

Then write your downloaded OS image to eMMC:

dd if=rockpi4_debian_stretch_lxde_armhf_20181105_2120-gpt.img of=/dev/mmcblk1

A CLI tool to write an image with write diagnostics is pv:

$ apt install pv
$ pv -ptera < rockpi4_debian_stretch_lxde_armhf_20181105_2120-gpt.img | dd of=/dev/mmcblk1 obs=512

Power off your Rock PI 4, remove the μSD and power on again. The system will now boot from the eMMC module.

====Step 4: Boot on ROCK Pi 4 ====

Rockpi4/dev/kernel-mainline

2020-01-07T12:49:29Z

Raidboy: /* Already fixed */

{{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/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/kernel-mainline

2020-01-07T12:48:27Z

Raidboy:

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

== 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/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/install/eMMC

2020-01-06T13:25:05Z

Raidboy: Added explanation how to install without uMMC adapter

{{rockpi4_header}}

{{Languages|rockpi4/install/microSD}}

[[rockpi4 | ROCK Pi 4]] > [[rockpi4/install | Install]] > [[rockpi4/install/eMMC | Install on eMMC module]]

====Step1: Requirements ====

This page describe how to download and install the image on an eMMC module and boot on ROCK Pi 4. You need at least the following.

* an eMMC module, you can buy it from radxa distributor, the eMMC module from Odroid or PINE64 also works on ROCK Pi 4. [[File:Emmc_module_top.png | 100px]] [[File:Emmc_module_bottom.png | 100px]]
* an eMMC to microSD breakout board [[File:Emmc_to_microSD_breakout_top.png | 100px]] [[File:Emmc_to_microSD_breakout_bottom.png | 100px]]

If you do not have an eMMC to μSD card converter board, you can also first install a linux system (e.g.: Debian) to a μSD Card (see [[Rockpi4/install/microSD]]) and then use the running Linux μSD System to install the desired system to the eMMC card with the eMMC card already inserted into the Rock PI 4. See below.

* a microSD card reader, either a USB card reader or the SD card reader on laptop
* a PC/laptop running Windows or Linux or MacOS

You also need the following to run on ROCK Pi 4

* ROCK Pi 4 board with power supply
* HDMI cable for display
* USB keyboard and mouse for input

====Step 2: Download necessary tools and image ====

* Etcher is the tool we use to write image. Download the right Etcher for your PC from [[Rockpi4/downloads]] page and install it. Check [[https://www.balena.io/etcher/ Etcher website]] for more info about Etcher.
* Choose the image you want to install from [[Rockpi4/downloads]] page and unzip it. The unzipped image name is like below:

rockpi4_debian_stretch_lxde_armhf_20181105_2120-gpt.img

We will use it for the writing.

====Step 3: Write the image to eMMC Module ====

3.1 Plug and click the eMMC module to the eMMC to uSD breakout board, plug the breakout board to microSD card reader. Plug the card reader on PC.

[[File:Emmc_module_on_card_reader.png]]

3.2 Run the application, for example, by executing the command on Ubuntu 16.04:

$ /bin/bash etcher-etcher-electron-1.4.5-x86_64.AppImage

3.3 In the etcher window, we click button Select image.

[[File:linux_etcher_select_image.png]]

3.4 In the etcher window, we click button Select Drive.

[[File:linux_etcher_select_driver.png]]

3.5 In the etcher window, we click button Flash.

[[File:linux_etcher_select_flash_button.png]]

3.6 In the etcher window, it shows us Flash Complete!

[[File:linux_etcher_show_complete.png]]

Done! Now you have successfully installed the OS image on eMMC module.

====Step 3 on Rock PI 4: Write the image to eMMC Module ====

If you have no eMMC to μSD card converter board, install Debian Linux (or another Linux variant) first to μSD. Insert both your μSD and the (empty) eMMC module into the Rock PI 4. Reboot it. It will boot from μSD. You can now use that Linux to download your desired OS from [[Rockpi4/downloads]] and install it onto the eMMC module. Example:

Verify that the system has booted from μSD, which should be /dev/mmcblk0p5 and that the eMMC module is found as /dev/mmcblk1:

$ dmesg | grep mmcblk
...
[...] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode.

$ ls -l /dev/mmcblk1
brw-rw---- 1 root disk 179, 0 Jan 6 13:25 /dev/mmcblk1

Then write your downloaded OS image to eMMC:

dd if=rockpi4_debian_stretch_lxde_armhf_20181105_2120-gpt.img of=/dev/mmcblk1

A CLI tool to write an image with write diagnostics is pv:

$ apt install pv
$ pv -ptera < rockpi4_debian_stretch_lxde_armhf_20181105_2120-gpt.img > /dev/mmcblk1

Power off your Rock PI 4, remove the μSD and power on again. The system will now boot from the eMMC module.

====Step 4: Boot on ROCK Pi 4 ====

Rockpi4/getting started

2020-01-06T13:07:38Z

Raidboy: Added note/pointer that installation can also be performed without eMMC to uSD adapter

{{rockpi4_header}}
{{Languages|rockpi4/getting_started}}

__TOC__

This guide is designed for ROCK Pi 4 enthusiast. The purpose is to learn about the ROCK Pi 4 board as well as how to prepare and set up for basic use. The ROCK Pi 4 has two models, one called ROCK Pi 4 Model A and the other called ROCK Pi 4 Model B. When you get a board, you need to know what Pi model it is and which hardware version it is. The information is printed in the top side of the board. We will introduce the board information as much as possible.

== What you need ==

=== Necessary ===
* ROCK Pi 4 main board
** ROCK Pi 4 Model A or Model B

* One of the Storage media below:
** [[rockpi4/hardware/μSD | μSD card]], larger than 8GB.
** [[rockpi4/hardware/emmc | eMMC Module]] , larger than 8GB with eMMC to μSD converter board.

* [[rockpi4/hardware/powersupply | Power supply]]
** The ROCK Pi 4 is powered by Type-C port and has a wide range of input voltage, from 9V to 21V. The Pi supports USB Type-C PD 2.0 with 9V/2A, 12V/2A, 15V/2A and 20V/2A. Besides, the Pi supports QC 3.0/2.0 with 9V/2A and 12V/1.5A.
** The Type-C cable you using needs to support data communication. We call it USB Type-C charging data cable.

* USB Keyboard and Mouse
** With four USB-A connectors, ROCK Pi 4 can be equipped with a full sized keyboard and mouse.

* Monitor and HDMI Cable
** ROCK Pi 4 is equipped with a full sized HDMI connector. HDMI capable monitor is recommended.
** HDMI EDID display data is used to determine the best display resolution. On monitors and TVs that support 1080p (or 4K) this resolution will be selected. If 1080p is not supported the next available resolution reported by EDID will be used. This selected mode will work with MOST but not all monitors/TVs.

*USB to TTL serial cable
**ROCK Pi 4 exports a dedicated serial console, which can access the low level debug message.

*USB Male A to Male A cable
**If you want write image on ROCK Pi 4 from USB OTG port or use fastboot/adb commands you need an USB Male A to Male A cable to connect ROCK Pi 4 and PC.

=== Optional ===
* μSD Card Reader
** For flashing the image into μSD Card or eMMC Module.

* USB type A to type A cable
** This is needed for fastboot/adb commands.

* USB to TTL serial cable
** This is needed for serial console.

* Ethernet cable
** ROCK Pi 4 supports Internet access via WIFI or Ethernet.
** An Ethernet cable is used to connect your ROCK Pi 4 to a local network and the Internet.

* Camera Module
** ROCK Pi 4 supports camera function.

* LCD Module
** ROCK Pi 4 supports LCD display function.

* Audio cable
** Audio can be played through speaker or headphones using a standard 3.5mm jack.

== Close look of ROCK Pi 4B ==
* ROCK Pi 4B front view
[[File:ROCKPI4B_Front_View.png|700px]]
* ROCK Pi 4B front with an angle view
[[File:ROCKPI4B_Angle_View.png|700px]]
* ROCK Pi 4B back view
[[File:ROCKPI4B_Back_View.png|700px]]

== Features ==

{| class="wikitable"
! Model
! colspan="1" width=42% | ROCK PI 4 Model A
! colspan="1" width=42% | ROCK PI 4 Model B
|-
! Processor
| colspan="2" | 64bits hexa core processor Rockchip RK3399 Dual Cortex-72, frequency 1.8GHz with qual Cortex-A53, frequency 1.4GHz Mali T860MP4 gpu, support OpenGL ES 1.1/2.0/3.0/3.1/3.2, Vulkan 1.0, Open CL 1.1 1.2, DX11.
|-
! Memory
| colspan="2" | LPDDR4 64bit dual channel LPDDR4@3200Mb/s, 1GB/2GB/4GB optioal
|-
! Storage
| colspan="2" | eMMC module (Optional industrial compatible high performance eMMC module, 8GB/16GB/32GB/64GB/128GB available) μSD card (μSD slot supports up to 128 GB μSD card) M.2 SSD (M.2 connector supports up to 2T M2 NVME SSD)
|-
! Display
| colspan="2" | HDMI 2.0 up to 4k@60 MIPI DSI 2 lanes via FPC connector HDMI and MIPI DSI can work at the same time, support mirror mode or extend mode.
|-
! Audio
| colspan="2" | 3.5mm jack with mic HD codec that supports up to 24-bit/96KHz audio.
|-
! Camera
| colspan="2" | MIPI CSI 2 lanes via FPC connector, support up to 800 MP camera.
|-
! Wireless
| None
| 802.11 ac wifi Bluetooth 5.0 with on board antenna
|-
! USB
| colspan="2" | USB 3.0 OTG X1, hardware switch for host/device switch, upper one USB 3.0 HOST X1, dedicated USB 3.0 channel, lower one USB 2.0 HOST X2
|-
! Ethernet
| GbE LAN
| GbE LAN with Power over Ethernet (PoE) support additional HAT is required for powering from PoE
|-
! IO
| colspan="2" | 40-pin expansion header 2 x UART 2 x SPI bus 3 x I2C bus 1 x PCM/I2S 1 x SPDIF 2 x PWM 1 x ADC 6 x GPIO 2 x 5V DC power in 2 x 3.3V DC power in
|-
! Others
| colspan="2" | RTC RTC battery connector for time backup(optional)
|-
! Power
| colspan="2" | USB PD, support USB Type C PD 2.0, 9V/2A, 12V/2A, 15V/2A, 20V/2A. Qualcomm® Quick ChargeTM: Supports QC 3.0/2.0 adapter, 9V/2A, 12V/1.5A
|-
! Size
| colspan="2" | 85mm x 54mm
|}

__TOC__

== Starting the board for the first time ==

ROCK Pi 4 can be started with eMMC or μSD Card. Now, you are presented with two options when installing your new operating system onto your ROCK Pi 4.

=== Prepare ===

* When start system with eMMC
Insert eMMC Module into eMMC to μSD card converter board. Insert the converter board into μSD Card Reader, which connects to host computer. The picture below shows. (add eMMC, eMMC to μSD Module and μSD Card Reader picture)

If you do not have an eMMC to μSD card converter board, you can also first install a linux system to a μSD Card and then use the running μSD System to install the desired system to the eMMC card with the eMMC card already inserted into the Rock PI 4. See [[Rockpi4/install/eMMC]].

* When start system with μSD Card
Insert the μSD Card into μSD Card Reader, which connects to host computer. The picture below shows. (add μSD Card and μSD Card Reader picture)

=== Write Image ===

* Download the flash tool, etcher, from [[rockpi4/downloads | Downloads]]. Choose the right version for your host operation system. Here we operate on host Ubuntu 16.04.

* After unpacking the package, we run the tool by executing the command

$ ./etcher-etcher-electron-1.4.5-x86_64.AppImage

If you get an error message: "No polkit authentication agent found" you can try and start it with sudo, but do know that this is running the tool as '''root'''.

* In the etcher window, click '''Select image'''.

[[File:linux_etcher_select_image.png]]

* In the etcher window, click '''Select Drive'''.

[[File:linux_etcher_select_driver.png]]

* In the etcher window, click '''Flash'''.

[[File:linux_etcher_select_flash_button.png]]

* In the etcher window, once it shows us Flash Complete! It is done and can be put into the RockPi.

[[File:linux_etcher_show_complete.png]]

=== Boot ===

* Now insert system storage media into the socket on board.
** Method of starting system with eMMC. The picture below shows. ('''Todo''': add picture)
** Methods of starting system with μSD Card. The picture below shows. ('''Todo''': add picture)

* Connect the ROCK Pi 4 to your display with the HDMI cable. Ensure that the source for the display is switched to the HDMI port you are using.
* Connect the USB keyboard and mouse.
* Connect the power supply to the ROCK Pi 4. The board will begin to immediately. (You might not see the boot sequence, on Ubuntu Server you will see the login prompt)

Wish you good luck!

=== Troubleshooting ===
* Refer [[Rockpi4/getting_started/troubleshooting | Troubleshooting page]]
* Post your issue on the forum: https://forum.radxa.com/c/rockpi4/Troubleshooting