Difference between revisions of "ROCK64"

From PINE64
Jump to navigation Jump to search
(https)
m (→‎ROCK64 Board Information, Schematics and Certifications: Change synfare link from HTTPS to HTTP until they fix their TLS)
(33 intermediate revisions by 5 users not shown)
Line 10: Line 10:
 
** [https://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]
 
** [https://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]
 
** [https://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]
 
** [https://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]
** [[Set MacAddress on ROCK64]]
+
** [[ROCK64 MAC Address]]
 +
 
 +
Under [[ROCK64 Software Release]] you will find a complete list of currently supported Operating System images that work with the ROCK64 as well as other related software.
  
=== [[ROCK64_Software_Release|ROCK64 Ver3 and Ver2]] ===
 
Under [[ROCK64_Software_Release|'ROCK64 Software and OS Image Download Section']] you will find a complete list of currently supported Operating System images that work with the ROCK64 as well as other related software.
 
 
The list includes OS images and descriptions of:
 
The list includes OS images and descriptions of:
  
https://files.pine64.org/sw/pine64_installer/json/armbian.png [https://wiki.pine64.org/index.php/ROCK64_Software_Release#Armbian'''Armbian Ubuntu Bionic Desktop on mainline Kernel (microSD / eMMC Boot)''']           https://files.pine64.org/sw/pine64_installer/json/armbian.png [https://wiki.pine64.org/index.php/ROCK64_Software_Release#Armbian'''Armbian Debian Buster on mainline Kernel (microSD / eMMC Boot)''']
+
* [[ROCK64_Software_Release#Armbian|Armbian (microSD / eMMC Boot)]]  
 
 
https://files.pine64.org/sw/pine64_installer/json/armbian.png [https://wiki.pine64.org/index.php/ROCK64_Software_Release#Armbian'''Armbian Ubuntu Bionic Desktop on legacy BSP Kernel (microSD / eMMC Boot)''']           https://files.pine64.org/sw/pine64_installer/json/armbian.png [https://wiki.pine64.org/index.php/ROCK64_Software_Release#Armbian'''Armbian Debian Buster on legacy BSP Kernel (microSD / eMMC Boot)''']
 
 
 
https://files.pine64.org/sw/pine64_installer/json/penguin.png [https://wiki.pine64.org/index.php/ROCK64_Software_Release#Ubuntu_18.04_Bionic'''Bionic Desktop LXDE (microSD /eMMC Boot)''']           https://files.pine64.org/sw/pine64_installer/json/penguin.png [https://wiki.pine64.org/index.php/ROCK64_Software_Release#Ubuntu_18.04_Bionic'''Bionic Minimal 64bit (microSD /eMMC Boot)''']
 
 
 
https://files.pine64.org/sw/pine64_installer/json/penguin.png [https://wiki.pine64.org/index.php/ROCK64_Software_Release#Ubuntu_18.04_Bionic'''Bionic Minimal 32bit (microSD /eMMC Boot)''']           https://files.pine64.org/sw/pine64_installer/json/containers.png [https://wiki.pine64.org/index.php/ROCK64_Software_Release#Ubuntu_18.04_Bionic'''Bionic Minimal Containers (microSD /eMMC Boot)''']  
 
  
[[ROCK64_Software_Release#LibreELEC.28KODI.29|'''LibreElec for KODI (microSD / eMMC Boot)''']]
+
* [[ROCK64_Software_Release#AOSC|AOSC (microSD / eMMC Boot)]]  
  
https://files.pine64.org/sw/pine64_installer/json/debian.png [https://wiki.pine64.org/index.php/ROCK64_Software_Release#Debian_Stretch'''Debian by ayufan (microSD / eMMC Boot)''']
+
* [[ROCK64_Software_Release#Manjaro ARM|Manjaro ARM (microSD / eMMC Boot)]]  
  
https://files.pine64.org/sw/pine64_installer/json/debian.png [https://wiki.pine64.org/index.php/ROCK64_Software_Release#Debian_by_mrfixit2001'''Debian by mrfixit2001 (microSD / eMMC Boot)''']
+
* [[ROCK64_Software_Release#Ubuntu 18.04 Bionic by ayufan|Ubuntu 18.04 Bionic by ayufan (microSD / eMMC Boot)]]
  
https://files.pine64.org/sw/pine64_installer/json/omv.png [https://wiki.pine64.org/index.php/ROCK64_Software_Release#OpenMediaVault '''OpenMediaVault 32bit (microSD / eMMC boot)''']           https://files.pine64.org/sw/pine64_installer/json/omv.png [https://wiki.pine64.org/index.php/ROCK64_Software_Release#OpenMediaVault'''OpenMediaVault 64bit (microSD / eMMC boot)''']
+
* [[ROCK64_Software_Release#Slackware|Slackware (microSD / eMMC Boot)]]
  
[[ROCK64_Software_Release#NextCloudPi|'''NextCloudPi(microSD /eMMC Boot)''']]  
+
* [[ROCK64_Software_Release#DietPi|DietPi (microSD / eMMC Boot)]]
  
[[ROCK64_Software_Release#Slackware|'''Slackware(microSD /eMMC Boot)''']]
+
* [[ROCK64_Software_Release#LibreELEC.28KODI.29|LibreElec for KODI (microSD / eMMC Boot)]]  
  
[[ROCK64_Software_Release#Recalbox|'''Recalbox(microSD /eMMC Boot)''']]
+
* [[ROCK64_Software_Release#Volumio 2 Digital Audio Player|Volumio 2 Digital Audio Player (microSD / eMMC Boot)]]
  
[[File:Netbsd2.png]] [https://wiki.pine64.org/index.php/ROCK64_Software_Release#NetBSD '''NetBSD (microSD / eMMC Boot)''']
+
* [[ROCK64_Software_Release#Debian_Stretch|Debian by ayufan (microSD / eMMC Boot)]]
  
[[ROCK64_Software_Release#Android_9.x_eMMC|'''Android 9.x (eMMC)''']]
+
* [[ROCK64_Software_Release#Debian_by_mrfixit2001|Debian by mrfixit2001 (microSD / eMMC Boot)]]
  
[[ROCK64_Software_Release#Android_8.x_eMMC|'''Android 8.x (eMMC)''']] / [[ROCK64_Software_Release#Android_8.x|'''Android 8.x (microSD Boot)''']]
+
* [[ROCK64_Software_Release#OpenMediaVault|OpenMediaVault 64bit (microSD / eMMC boot)]]
  
[[ROCK64_Software_Release#Android_7.x_eMMC|'''Android 7.x (eMMC)''']] / [[ROCK64_Software_Release#Android_7.x|'''Android 7.x (microSD Boot)''']]
+
* [[ROCK64_Software_Release#NextCloudPi|NextCloudPi(microSD / eMMC Boot)]]  
  
[[ROCK64_Software_Release#Android_TV_7.x_eMMC|'''Android TV 7.x (eMMC)''']] / [[ROCK64_Software_Release#Android_TV_7.x|'''Android TV 7.x (microSD Boot)''']]
+
* [[ROCK64_Software_Release#Recalbox|Recalbox(microSD / eMMC Boot)]]
  
=== [[ROCK64_Software_Release|ROCK64 Ver2 only]] ===
+
* [[ROCK64_Software_Release#NetBSD|NetBSD (microSD / eMMC Boot)]]
Under [[ROCK64_Software_Release|'ROCK64 Software and OS Image Download Section']] you will find a complete list of currently supported Operating System images that work with the ROCK64 as well as other related software.
 
  
The list includes OS images and descriptions of:
+
* [[ROCK64_Software_Release#Android_9.x_eMMC|Android 9.x (eMMC)]]
  
[[ROCK64_Software_Release#Manjaro_ARM|''' Manjaro KDE ARM (microSD /eMMC Boot)''']] / [[ROCK64_Software_Release#Manjaro_ARM|''' Manjaro LXQT ARM (microSD /eMMC Boot)''']]
+
* [[ROCK64_Software_Release#Android_8.x_eMMC|Android 8.x (eMMC)]] / [[ROCK64_Software_Release#Android_8.x|Android 8.x (microSD Boot)]]
  
[[ROCK64_Software_Release#Manjaro_ARM|''' Manjaro ARM Minimal (microSD /eMMC Boot)''']]
+
* [[ROCK64_Software_Release#Android_7.x_eMMC|Android 7.x (eMMC)]] / [[ROCK64_Software_Release#Android_7.x|Android 7.x (microSD Boot)]]
  
[[ROCK64_Software_Release#Cent_OS|''' Cent OS (microSD /eMMC Boot)''']]
+
* [[ROCK64_Software_Release#Android_TV_7.x_eMMC|Android TV 7.x (eMMC)]] / [[ROCK64_Software_Release#Android_TV_7.x|Android TV 7.x (microSD Boot)]]
  
[[ROCK64_Software_Release#DietPi|'''DietPi (microSD /eMMC Boot)''']]
 
 
[[ROCK64_Software_Release#Lakka|'''Lakka(microSD /eMMC Boot)''']]
 
 
[[ROCK64_Software_Release#NEMS_Linux|'''NEMS Linux (microSD /eMMC Boot)''']]
 
 
[[ROCK64_Software_Release#Volumio_Digital_Audio_Player|'''Volumio Digital Audio Player (microSD /eMMC Boot)''']]
 
 
[[ROCK64_Software_Release#Fedora|'''Fedora (microSD /eMMC Boot)''']]
 
 
[[ROCK64_Software_Release#Yocto|'''Yocto''']]
 
  
 
=== Quick Links to the Source of OS Images Build ===
 
=== Quick Links to the Source of OS Images Build ===
Line 84: Line 66:
 
* [https://dl.fail.pp.ua/slackware/images/rock64/ Slackware]
 
* [https://dl.fail.pp.ua/slackware/images/rock64/ Slackware]
  
=== State of software support for the hardware ===
+
=== State of Software Support for the Hardware ===
 +
 
 
{| class="wikitable sortable"
 
{| class="wikitable sortable"
 
! Requirement
 
! Requirement
Line 115: Line 98:
 
| yes
 
| yes
  
 +
|}
 +
 +
=== Upstreaming Status ===
 +
 +
{| class="wikitable plainrowheaders" border="1"
 +
! scope="col" | Function
 +
! scope="col" colspan="2" | Status
 +
! scope="col" | Component
 +
! scope="col" | Notes
 +
|-
 +
! scope="row" | Video Output
 +
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
 +
| <code>rockchipdrm</code>
 +
| With mpv, you'll need to specify something like <code>mpv --gpu-context=drm --drm-connector=1.HDMI-A-1</code> to get it to play back on a VT
 +
|-
 +
! scope="row" | 3D Acceleration
 +
| style="background:PaleGreen; text-align:center;"|Linux Mainline
 +
| style="background:PaleGreen; text-align:center;"|Upstream Mesa
 +
| <code>lima</code>
 +
| Very recent version recommended for the best experience. Has weird glitches on HDMI output in weston.
 +
|-
 +
! scope="row" | Video Decode
 +
| style="background:LightYellow; text-align:center;"|Linux Staging
 +
| style="background:#F99; text-align:center;"|Broken/Not in ffmpeg
 +
| <code>hantro_vpu</code> and <code>rockchip_vdec</code>, using <code>v4l2-requests</code>
 +
| [https://lore.kernel.org/linux-media/49b1-608d4d00-2b-62afdf80@101971638/ Soon to be moved out of staging], ffmpeg patch set [https://patchwork.ffmpeg.org/project/ffmpeg/patch/20201209202513.27449-3-jonas@kwiboo.se/ seemingly abandoned], does not work on newer kernels. [https://github.com/Kwiboo/FFmpeg/commits/v4l2-request-hwaccel-master-stable Git branch with commits]
 +
|-
 +
! scope="row" | Audio
 +
| colspan="2"  style="background:PaleGreen; text-align:center;"|Linux Mainline
 +
| <code>snd_soc_rockchip_*</code>
 +
|-
 +
! scope="row" | Power Button
 +
| colspan="2" style="background:PaleGreen; text-align:center;"|Linux Mainline
 +
| <code>rk805_pwrkey</code>
 +
| If your PWR switch does nothing unless held, this may need to be loaded manually with <code>modprobe</code> or by putting it in <code>/etc/modules-load.d/</code>
 
|}
 
|}
  
Line 128: Line 146:
 
* In-order pipeline with symmetric dual-issue of most instructions
 
* In-order pipeline with symmetric dual-issue of most instructions
 
* Unified system L2 cache
 
* Unified system L2 cache
* Include VFP v3 hardware to support single and double-precision operations
+
* Includes VFP v3 hardware to support single and double-precision operations
* Integrated 32KB L1 instruction cache, 32KB L1 data cache with 4-way set associative
+
* Integrated 32KB L1 instruction cache, 32KB 4-way set associative L1 data cache
 
* TrustZone technology support
 
* TrustZone technology support
 
* Full CoreSight debug solution
 
* Full CoreSight debug solution
* One separate power domains for CPU core system to support internal power switch and externally turn on/off based on different application scenario
+
* One separate power domain for CPU core system to support internal power switch, and to externally turn on/off based on different application scenario
 
* PD_A53: Cortex-A53 + Neon + FPU + L1 I/D Cache of core 2/3
 
* PD_A53: Cortex-A53 + Neon + FPU + L1 I/D Cache of core 2/3
 
* One isolated voltage domain to support DVFS
 
* One isolated voltage domain to support DVFS
 +
 +
==== Frequencies & Voltages ====
 +
 +
{| class="wikitable"
 +
! Frequency
 +
! Voltage
 +
|- style="text-align:right;"
 +
| 408 MHz
 +
| 0.950 V
 +
|- style="text-align:right;"
 +
| 600 MHz
 +
| 0.950 V
 +
|- style="text-align:right;"
 +
| 816 MHz
 +
| 1.000 V
 +
|- style="text-align:right;"
 +
| 1008 MHz
 +
| 1.100 V
 +
|- style="text-align:right;"
 +
| 1200 MHz
 +
| 1.225 V
 +
|- style="text-align:right;"
 +
| 1296 MHz
 +
| 1.300 V
 +
|}
 +
 +
==== Power Draw ====
 +
 +
These numbers for power draw have been measured through an USB power monitor (FNB38) while running the <code>stress</code> utility, whereby "cpu" stands for <code>stress --cpu 4</code> and "vm" stands for <code>stress --vm 4</code>. The former spins on the CPU, the latter stresses the memory. Real workloads are usually a mix of both. The tests were ran through ssh, with nothing besides power and ethernet plugged into the ROCK64
 +
 +
Please keep in mind that under real world usage, many other factors come into play. Having a display connected, running a graphical session, I/O and most importantly the connected USB peripherals can add a lot.
 +
 +
Helpful refresher on the formula for power (W) on DC: power = current &times; voltage, because the power factor is 1. The ROCK64 runs on 5V, so use that to calculate current if you need to.
 +
 +
{| class="wikitable"
 +
! Frequency
 +
! Power cpu
 +
! Power vm
 +
|- style="text-align:right;"
 +
| 1296 MHz
 +
| 2.64 W
 +
| 2.95 W
 +
|- style="text-align:right;"
 +
| 1200 MHz
 +
| 2.32 W
 +
| 2.69 W
 +
|- style="text-align:right;"
 +
| 1008 MHz
 +
| 1.90 W
 +
| 2.31 W
 +
|- style="text-align:right;"
 +
| 816 MHz
 +
| 1.62 W
 +
| 2.05 W
 +
|- style="text-align:right;"
 +
| 600 MHz
 +
| 1.45 W
 +
| 1.85 W
 +
|- style="text-align:right;"
 +
| 408 MHz
 +
| 1.33 W
 +
| 1.72 W
 +
|- style="text-align:right;"
 +
| Idle (no load)
 +
|colspan="2" style="text-align:center;"| 1.10 W
 +
|}
 +
 +
It appears a good upper bound for a headless setup is in the neighbourhood of 3 W, or the energy contained in 0.025 bananas per hour.
  
 
=== GPU Architecture ===
 
=== GPU Architecture ===
Line 164: Line 250:
  
 
=== Storage ===
 
=== Storage ===
* microSD - bootable, support SDHC and SDXC, storage up to 256GB
+
* microSD - bootable, supports SDHC and SDXC and storage up to 256GB
 
* eMMC - bootable (optional eMMC Module)
 
* eMMC - bootable (optional eMMC Module)
* 128Mbit (16MB) on-board SPI flash memory (empty by default) - bootable?
+
* 128Mbit (16MB) on-board SPI flash memory (empty by default) - bootable? Usually accessible as a [http://linux-mtd.infradead.org/doc/general.html Linux MTD] device at <code>/dev/mtd0</code>
 
* 1 USB3.0 Dedicated Host port
 
* 1 USB3.0 Dedicated Host port
 
* 2 USB2.0 Dedicated Host port (top one is USB-OTG)
 
* 2 USB2.0 Dedicated Host port (top one is USB-OTG)
  
 
=== Expansion Ports ===
 
=== Expansion Ports ===
 +
All GPIO pins, including UART, operate at 3.3V. (See VCCIO5 in the schematics.)
 +
 
* 2x20 pins "Pi2" GPIO Header
 
* 2x20 pins "Pi2" GPIO Header
 
* 2x11 pins "Pi P5+" GPIO Header (with 2nd 10/100Mbps Ethernet pins)
 
* 2x11 pins "Pi P5+" GPIO Header (with 2nd 10/100Mbps Ethernet pins)
Line 177: Line 265:
 
* Board Dimensions: 85mm x 56mm x 18.8mm
 
* Board Dimensions: 85mm x 56mm x 18.8mm
 
** [https://files.pine64.org/doc/rock64/rock64%20board%20dimension.pdf ROCK64 board dimension drawing]
 
** [https://files.pine64.org/doc/rock64/rock64%20board%20dimension.pdf ROCK64 board dimension drawing]
* Input Power: +5V @3A with 3.5mm/1.35mm Type H Barrel type DC connector (@2A still work if no heavy loading on USB 3.0 port)
+
* Input Power: +5V @3A with 3.5mm/1.35mm Type H Barrel type DC connector (@2A will work if there is no heavy load on the USB 3.0 port)
 
* ROCK64 ver 3.0 SBC related info
 
* ROCK64 ver 3.0 SBC related info
 
** [https://files.pine64.org/doc/rock64/Rock64%20Ver%203%20change%20notice.pdf ROCK64 SBC v3.0 Change Notice]
 
** [https://files.pine64.org/doc/rock64/Rock64%20Ver%203%20change%20notice.pdf ROCK64 SBC v3.0 Change Notice]
Line 190: Line 278:
 
** [https://files.pine64.org/doc/rock64/ROCK64_Pi-2%20_and_Pi_P5+_Bus.pdf ROCK64 SBC v2.0 Pi-2 and Pi-P5+ Bus GPIO Assignment]
 
** [https://files.pine64.org/doc/rock64/ROCK64_Pi-2%20_and_Pi_P5+_Bus.pdf ROCK64 SBC v2.0 Pi-2 and Pi-P5+ Bus GPIO Assignment]
 
* [https://github.com/Leapo/Rock64-R64.GPIO Github on ROCK64 GPIO library, thanks to Leapo]
 
* [https://github.com/Leapo/Rock64-R64.GPIO Github on ROCK64 GPIO library, thanks to Leapo]
* [https://synfare.com/599N105E/hwdocs/rock64/index.html Good documentation about ROCK64 GPIO pins article]
+
* [http://synfare.com/599N105E/hwdocs/rock64/index.html Good documentation about ROCK64 GPIO pins article]
 
* [https://files.pine64.org/doc/rock64/ROCK64_ES9023_Audio_100Mbps_Ethernet_Board.pdf ROCK64 Audio DAC with 10/100Mbps Ethernet POT Board Schematic]
 
* [https://files.pine64.org/doc/rock64/ROCK64_ES9023_Audio_100Mbps_Ethernet_Board.pdf ROCK64 Audio DAC with 10/100Mbps Ethernet POT Board Schematic]
 
* ROCK64 3-D autodesk drawing, thanks and courtesy of TeaPack
 
* ROCK64 3-D autodesk drawing, thanks and courtesy of TeaPack
Line 206: Line 294:
 
* Rockchip RK3328 SoC information:
 
* Rockchip RK3328 SoC information:
 
** [https://www.rock-chips.com/a/en/products/RK33_Series/2017/0118/829.html Rockchip RK3328 SoC Brief]
 
** [https://www.rock-chips.com/a/en/products/RK33_Series/2017/0118/829.html Rockchip RK3328 SoC Brief]
** [https://opensource.rock-chips.com/images/d/d7/Rockchip_RK3328_Datasheet_V1.1-20170309.pdf Rockchip RK3328 Datasheet V1.1]
+
** [https://rockchip.fr/RK3328%20datasheet%20V1.2.pdf Rockchip RK3328 Datasheet V1.2]
 
** [https://opensource.rock-chips.com/images/9/97/Rockchip_RK3328TRM_V1.1-Part1-20170321.pdf Rockchip RK3328 Technical Reference Manual part 1]
 
** [https://opensource.rock-chips.com/images/9/97/Rockchip_RK3328TRM_V1.1-Part1-20170321.pdf Rockchip RK3328 Technical Reference Manual part 1]
 
** [https://files.pine64.org/doc/rock64/Rockchip_RK805_Datasheet_V1.1%C2%A020160921.pdf Rockchip RK805 Datasheet V1.1]
 
** [https://files.pine64.org/doc/rock64/Rockchip_RK805_Datasheet_V1.1%C2%A020160921.pdf Rockchip RK805 Datasheet V1.1]
Line 231: Line 319:
 
* Remote control button mapping
 
* Remote control button mapping
 
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE A64 Button Mapping]
 
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE A64 Button Mapping]
 +
 +
== Enclosures ==
 +
 +
[[File:Rock64-Al-Case1-1.jpg|thumb|100px]]
 +
 +
The ROCK64 fits in three officially sold cases.
 +
 +
* [["Model B" Acrylic Open Enclosure]], [https://pine64.com/product/model-b-acrylic-open-enclosure/ Store]
 +
* [["Model B" Aluminum Waterproof Enclosure]], [https://pine64.com/product/model-b-aluminum-waterproof-enclosure/ Store]
 +
* [[ROCK64 Premium Aluminum Casing]], [https://pine64.com/product/model-b-premium-aluminum-casing/?v=0446c16e2e66 Store]
 +
 +
== Troubleshooting ==
 +
 +
=== HDMI output disconnects as soon as it connects ===
 +
 +
Some older monitors seemingly can get into a weird state wherein the ROCK64 is unable to establish a proper connection with them. [[User:CounterPillow]] has seen this happen on an iiyama ProLite G2773HS connected over HDMI, and an Acer P225HQL connected over an HDMI to DVI adapter. The symptoms usually are that you see the monitor briefly turn on its backlight without displaying a picture, but then immediately either shutting off again or showing a "No Signal" message.
 +
 +
The solution is to completely power down your ROCK64, also removing its power source. Then plug in the monitor, and start up the ROCK64 afterwards. You should now be getting a picture again.
 +
 +
=== Power button doesn't do anything on a short press (Linux) ===
 +
 +
Make sure the <code>rk805_pwrkey</code> module is loaded, e.g. with <code>lsmod | grep rk805_pwrkey</code>. If it doesn't show up, do a <code>modprobe rk805_pwrkey</code> as root. To make this persistent, create a <code>99-rk805_pwrkey.conf</code> in <code>/etc/modules-load.d/</code> with the content <code>rk805_pwrkey</code>
 +
 +
If it still doesn't work, make sure your init system is actually listening to the button press. With systemd, check <code>/etc/systemd/logind.conf</code> and make sure it's either all commented out (uses defaults) or contains something like <code>HandlePowerKey=poweroff</code>. You can change the short press action by setting <code>HandlePowerKey</code> to one of "ignore", "poweroff", "reboot", "halt", "kexec", "suspend", "hibernate", "hybrid-sleep", "suspend-then-hibernate", or "lock".
  
 
== Other Resources ==
 
== Other Resources ==

Revision as of 10:53, 3 June 2021

ROCK64

ROCK64 is a credit-card size 4K60P HDR Media Board Computer powered by Rockchip RK3328 Quad-Core ARM Cortex A53 64-Bit Processor and supports up to 4GB 1866MHz LPDDR3 memory. It provides an eMMC module socket, MicroSD Card slot, Pi-2 Bus, Pi-P5+ Bus, USB 3.0, and many other peripheral interfaces for makers to integrate with sensors and other devices. Many different Operating Systems (OS) are freely available from the open source community, such as Android 7.1, Debian, and Yocto.

ROCK64 sideimg.jpg

ROCK64 Software Images

Under ROCK64 Software Release you will find a complete list of currently supported Operating System images that work with the ROCK64 as well as other related software.

The list includes OS images and descriptions of:


Quick Links to the Source of OS Images Build

Some OS images are still in beta or nightly build which are only fit for testing purposes. These should usually be avoided for normal usage, since they are used at your own risk

State of Software Support for the Hardware

Requirement GNU/Linux Android/Linux Kodi/Linux
2160p 30Hz 8bit h264/h265/vp8 partial? 1 yes yes
UI using GPU no yes yes
Youtube no yes no
vp9 / mpeg4 / mpeg2 / 10bit HDR / YCbCr no yes? yes

Upstreaming Status

Function Status Component Notes
Video Output Linux Mainline rockchipdrm With mpv, you'll need to specify something like mpv --gpu-context=drm --drm-connector=1.HDMI-A-1 to get it to play back on a VT
3D Acceleration Linux Mainline Upstream Mesa lima Very recent version recommended for the best experience. Has weird glitches on HDMI output in weston.
Video Decode Linux Staging Broken/Not in ffmpeg hantro_vpu and rockchip_vdec, using v4l2-requests Soon to be moved out of staging, ffmpeg patch set seemingly abandoned, does not work on newer kernels. Git branch with commits
Audio Linux Mainline snd_soc_rockchip_*
Power Button Linux Mainline rk805_pwrkey If your PWR switch does nothing unless held, this may need to be loaded manually with modprobe or by putting it in /etc/modules-load.d/

SoC and Memory Specification

  • Based on Rockchip RK3328
Rockchip RK3328.png

CPU Architecture

  • Quad-core Cortex-A53 up to 1.5GHz CPU
  • Full implementation of the ARM architecture v8-A instruction set
  • ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
  • ARMv8 Cryptography Extensions
  • In-order pipeline with symmetric dual-issue of most instructions
  • Unified system L2 cache
  • Includes VFP v3 hardware to support single and double-precision operations
  • Integrated 32KB L1 instruction cache, 32KB 4-way set associative L1 data cache
  • TrustZone technology support
  • Full CoreSight debug solution
  • One separate power domain for CPU core system to support internal power switch, and to externally turn on/off based on different application scenario
  • PD_A53: Cortex-A53 + Neon + FPU + L1 I/D Cache of core 2/3
  • One isolated voltage domain to support DVFS

Frequencies & Voltages

Frequency Voltage
408 MHz 0.950 V
600 MHz 0.950 V
816 MHz 1.000 V
1008 MHz 1.100 V
1200 MHz 1.225 V
1296 MHz 1.300 V

Power Draw

These numbers for power draw have been measured through an USB power monitor (FNB38) while running the stress utility, whereby "cpu" stands for stress --cpu 4 and "vm" stands for stress --vm 4. The former spins on the CPU, the latter stresses the memory. Real workloads are usually a mix of both. The tests were ran through ssh, with nothing besides power and ethernet plugged into the ROCK64

Please keep in mind that under real world usage, many other factors come into play. Having a display connected, running a graphical session, I/O and most importantly the connected USB peripherals can add a lot.

Helpful refresher on the formula for power (W) on DC: power = current × voltage, because the power factor is 1. The ROCK64 runs on 5V, so use that to calculate current if you need to.

Frequency Power cpu Power vm
1296 MHz 2.64 W 2.95 W
1200 MHz 2.32 W 2.69 W
1008 MHz 1.90 W 2.31 W
816 MHz 1.62 W 2.05 W
600 MHz 1.45 W 1.85 W
408 MHz 1.33 W 1.72 W
Idle (no load) 1.10 W

It appears a good upper bound for a headless setup is in the neighbourhood of 3 W, or the energy contained in 0.025 bananas per hour.

GPU Architecture

System Memory

  • LPDDR3 RAM Memory Variants: 1GB, 2GB and 4GB.

Board Features

Video

  • Digital Video output up to 4K@60Hz
  • 4K HDR @ 60fps
  • H.264/AVC Base/Main/High/High10 profile @ level 5.1; up to 4Kx2K @ 60fps
  • H.265/HEVC Main/Main10 profile @ level 5.1 High-tier; up to 4Kx2K @ 60fps
  • VP9, up to 4Kx2K @ 60fps
  • MPEG-1, ISO/IEC 11172-2, up to 1080P @ 60fps
  • MPEG-2, ISO/IEC 13818-2, SP@ML, MP@HL, up to 1080P @ 60fps
  • MPEG-4, ISO/IEC 14496-2, SP@L0-3, ASP@L0-5, up to 1080P @ 60fps
  • VC-1, SP@ML, MP@HL, AP@L0-3, up to 1080P @ 60fps
  • MVC is supported based on H.264 or H.265, up to 1080P @ 60fps

Audio

  • 3.5mm A/V Jack (Composite Video Output and RCA Stereo support using conversion cable)

Network

  • 10/100/1000Mbps Ethernet
  • WiFi 802.11 b/g/n with Bluetooth 4.0 (optional USB dongle)

Storage

  • microSD - bootable, supports SDHC and SDXC and storage up to 256GB
  • eMMC - bootable (optional eMMC Module)
  • 128Mbit (16MB) on-board SPI flash memory (empty by default) - bootable? Usually accessible as a Linux MTD device at /dev/mtd0
  • 1 USB3.0 Dedicated Host port
  • 2 USB2.0 Dedicated Host port (top one is USB-OTG)

Expansion Ports

All GPIO pins, including UART, operate at 3.3V. (See VCCIO5 in the schematics.)

  • 2x20 pins "Pi2" GPIO Header
  • 2x11 pins "Pi P5+" GPIO Header (with 2nd 10/100Mbps Ethernet pins)

ROCK64 Board Information, Schematics and Certifications

https://files.pine64.org/doc/rock64/R64V3%20RTC%20Batt%20connector.png ROCK64 Rev3 SBC RTC Battery Connector polarity

Datasheets for Components and Peripherals

Enclosures

Rock64-Al-Case1-1.jpg

The ROCK64 fits in three officially sold cases.

Troubleshooting

HDMI output disconnects as soon as it connects

Some older monitors seemingly can get into a weird state wherein the ROCK64 is unable to establish a proper connection with them. User:CounterPillow has seen this happen on an iiyama ProLite G2773HS connected over HDMI, and an Acer P225HQL connected over an HDMI to DVI adapter. The symptoms usually are that you see the monitor briefly turn on its backlight without displaying a picture, but then immediately either shutting off again or showing a "No Signal" message.

The solution is to completely power down your ROCK64, also removing its power source. Then plug in the monitor, and start up the ROCK64 afterwards. You should now be getting a picture again.

Power button doesn't do anything on a short press (Linux)

Make sure the rk805_pwrkey module is loaded, e.g. with lsmod | grep rk805_pwrkey. If it doesn't show up, do a modprobe rk805_pwrkey as root. To make this persistent, create a 99-rk805_pwrkey.conf in /etc/modules-load.d/ with the content rk805_pwrkey

If it still doesn't work, make sure your init system is actually listening to the button press. With systemd, check /etc/systemd/logind.conf and make sure it's either all commented out (uses defaults) or contains something like HandlePowerKey=poweroff. You can change the short press action by setting HandlePowerKey to one of "ignore", "poweroff", "reboot", "halt", "kexec", "suspend", "hibernate", "hybrid-sleep", "suspend-then-hibernate", or "lock".

Other Resources