PINE64 - User contributions [en]

ROCKPro64

2023-06-07T23:18:29Z

I3master: Removed references to "I".

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful Single Board Computer released by PINE64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a Mali T-860 Quad-Core GPU. The key features include a PCIe x4 open ended slot, the use of LPDDR4 RAM, and industry standard heatsink mounting holes.

The ROCKPro64 is equipped with 2GB or 4GB LPDDR4 system memory, and 128Mb SPI boot Flash. There is also an optional eMMC module (up to 128GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 type C Host with DP 1.2, 1x USB 3.0 type A Host, 2x USB 2.0 Host, Gigabit Ethernet, PI-2 GPIO Bus, MiPi DSI interface, eDP interface, touch Panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different Operating Systems (OS) are freely available from the open source community, such as Android, Linux (Ubuntu, Debian, Arch), and BSD.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* 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
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* 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 Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 1 USB3.0 Host port
* 1 USB type C OTG port with DP output
* 2 USB2.0 Dedicated Host ports

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO Header
* PCIe 2.1 (4 full-duplex lanes with 20Gbps) x4 open ended port

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7″ LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
|
| For the "new" ROCKPro64 WIFI module: Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See [[#Getting wifi working ("new" wifi module)]] for the file contents and details.
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. On Manjaro ARM (kernel 6.2.5), WIFI seems to be stable with the firmware file. On a 5GHz network (802.11AC), it is possible to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is near impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| https://pine64.com/?product=rockpro64-playbox-enclosure
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://store.pine64.org/?product=rockpro64-heatsink
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCIe 2.1
|
|
|
|
|
|
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| https://store.pine64.org/?product=rtc-backup-battery-cr-battery
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: +12V @3A/5A with 5.5mm/2.1mm Type M Barrel type DC connector
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

* [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
* [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
* [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
* [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]

* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]

* [[ROCKPro64 Device Tree Overlays on Mainline]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NASCase|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A Quartz64-A mounted in an ITX case using 3D printed brackets]]

Allows mounting a ROCKPro64-A or Quartz64-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in your log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

Log in to your ROCKPro64, and run the following:

sudo -i
echo governor_simpleondemand >> /etc/initramfs-tools/modules && update-initramfs -u -k $(uname -r)
exit

Then, reboot.

== Hardware "Hacking" ==

=== Enabling PCIe 2.0 ===
By default, the RockPro64 runs the PCIe slot at gen 1 speeds because there might be stability issues with gen 2 speeds. The port can be switched back to gen 2 speeds by adding the following device tree overlay.

1. Copy and paste the device tree overlay file below into a new file (you could name it <code>pcie-2.0.dts</code>):
// Pulled from: https://forum.armbian.com/topic/23574-howto-enable-pcie-gen2-to-get-max-speed-of-nvme-rockpi-4b/
/dts-v1/;
/plugin/;

&pcie0 {
max-link-speed = <0x03>;
};

2. Compile the device tree into a binary file. Note that you will need <code>dtc</code> installed.
dtc -I dts -O dtb -@ pcie-2.0.dts -o pcie-2.0.dto

4. Copy or move the device tree from the current directory into the boot partition (in this case into the <code>/boot/dtbs/overlay/</code> folder). If you haven't yet created the <code>/boot/dtbs/overlay/</code> folder, then create it with <code>sudo mkdir /boot/dtbs/overlay/</code>
sudo cp pcie-2.0.dto /boot/dtbs/overlay/

5. Add the device compiled tree overlay file to the list of files u-boot needs to load. If you are using ManjaroARM (or ArchLinuxARM with a <code>extlinux.conf</code> file), then add the following line to the file <code>/boot/extlinux/extlinux.conf</code>:
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb

If you already have an <code>FDTOVERLAYS</code> line, then add a space at the end of the current line, then add this overlay file after that.
See here for details on this process: [[ROCKPro64 Device Tree Overlays on Mainline]]

The resulting <code>/boot/extlinux/extlinux.conf</code> file might look like below after adding this dtb file:
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb /dtbs/overlay/cpu-overclock.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 zfs=zroot rw rootwait audit=0 cpufreq.default_governor=schedutil

=== Overclocking (and undervolting) ===
The RK3399 can be overclocked. See here for details: [[Overclocking#RK3399-based devices]].
By overclocking, you do risk damaging your hardware, however, it is possible to achieve small, but measurable improvements in performance with an overclock. The overclock can be applied with a device tree overlay file.
Below is an example device tree overlay for CPU overclocking on the RockPro64. It may or may not work well on your device, but some have found that these speeds are stable.
The example below bumps the little cores up to 1.608GHz from 1.416GHz and bumps the big cores up to 2.088GHz from 1.8GHz.

1. Copy and paste the device tree overlay file below into a new file (you could name it <code>cpu-overclock.dts</code>):
// Pulled from: https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi
/dts-v1/;
/plugin/;

&cluster0_opp {
opp00 {
opp-hz = /bits/ 64 <408000000>;
opp-microvolt = <800000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <825000>;
};
opp02 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <850000>;
};
opp03 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <900000>;
};
opp04 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <975000>;
};
opp05 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <1100000>;
};
opp06 {
opp-hz = /bits/ 64 <1512000000>;
opp-microvolt = <1150000>;
};
opp07 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1200000>;
};
};
&cluster1_opp {
opp00 {
opp-hz = /bits/ 64 <408000000>;
opp-microvolt = <800000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <800000>;
};
opp02 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <825000>;
};
opp03 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <850000>;
};
opp04 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <900000>;
};
opp05 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <975000>;
};
opp06 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1050000>;
};
opp07 {
opp-hz = /bits/ 64 <1800000000>;
opp-microvolt = <1150000>;
};
opp08 {
opp-hz = /bits/ 64 <2016000000>;
opp-microvolt = <1250000>;
};
opp09 {
opp-hz = /bits/ 64 <2088000000>;
opp-microvolt = <1250000>;
};
};

2. Compile the device tree into a binary file. Note that you will need <code>dtc</code> installed.
dtc -I dts -O dtb -@ cpu-overclock.dts -o cpu-overclock.dto

4. Copy or move the device tree from the current directory into the boot partition (in this case into the <code>/boot/dtbs/overlay/</code> folder). If you haven't yet created the <code>/boot/dtbs/overlay/</code> folder, then create it with <code>sudo mkdir /boot/dtbs/overlay/</code>
sudo cp cpu-overclock.dto /boot/dtbs/overlay/

5. Add the device compiled tree overlay file to the list of files u-boot needs to load. If you are using ManjaroARM (or ArchLinuxARM with a <code>extlinux.conf</code> file), then add the following line to the file <code>/boot/extlinux/extlinux.conf</code>:
FDTOVERLAYS /dtbs/overlay/cpu-overclock.dtb

If you already have an <code>FDTOVERLAYS</code> line, then add a space at the end of the current line, then add this overlay file after that.
See here for details on this process: [[ROCKPro64 Device Tree Overlays on Mainline]]

The resulting <code>/boot/extlinux/extlinux.conf</code> file might look like below after adding this dtb file:
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb /dtbs/overlay/cpu-overclock.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 zfs=zroot rw rootwait audit=0 cpufreq.default_governor=schedutil

=== Getting wifi working ("new" wifi module) ===
ManjaroARM and ArchLinuxARM (and probably others) provide the NVRAM file needed to initialize the Wi-Fi module in the linux-firmware package, but it is listed under the generic name <code>brcmfmac43455-sdio.AW-CM256SM.txt</code>.
You can copy this file to the new name (that the driver looks for) with the following commands:
cd /usr/lib/firmware/brcm/
sudo cp brcmfmac43455-sdio.AW-CM256SM.txt brcmfmac43455-sdio.txt

Then, reboot and Wi-Fi should start working.
Details for this method are here: https://forum.pine64.org/showthread.php?tid=16635&pid=117061#pid117061
However, on a 5GHz network with <code>wireless-regdb</code> installed and the regulatory domain set to 'US', the adapter is almost unusable. Speeds are usually 0 bits per second. Sometimes a few packets can get through every few seconds, but that is it. On a 2.4GHz network, this is not an issue. This "can" be resolved by setting the regulator domain to 'GB' or 'CN', but this isn't a solution for you if you are in the USA, for instance. There are various other <code>brcmfmac43455-sdio.txt</code> files online that one can try. Some work better than others. Since these are text files where each line represents a property value, one can combine parts of these files to generate new firmware files for testing. One such combination yields decent results. This can be achieved by applying the patch below to the default <code>brcmfmac43455-sdio.AW-CM256SM.txt</code> file. With this firmware file, it is possible to get about 140Mbps up and down with this patch (with the regulatory domain set to 'US').

--- brcmfmac43455-sdio.AW-CM256SM.txt 2023-04-27 19:16:47.000000000 -0500
+++ brcmfmac43455-sdio.txt 2023-05-21 11:42:22.058517093 -0500
@@ -21,19 +21,18 @@
ltecxpadnum=0x0504
macaddr=00:90:4c:c5:12:38
manfid=0x2d0
-maxp2ga0=64
-maxp5ga0=80,82,76,77
-mcsbw202gpo=0x99355533
-mcsbw205ghpo=0x99855000
-mcsbw205glpo=0x99755000
-mcsbw205gmpo=0x9df55000
-mcsbw405ghpo=0xd9755000
-mcsbw405glpo=0xb8555000
-mcsbw405gmpo=0xed955000
-mcsbw805ghpo=0xd9555000
-mcsbw805glpo=0xc8555000
-mcsbw805gmpo=0xe9555000
-muxenab=0x10
+maxp2ga0=70
+maxp5ga0=73,74,73,73
+mcsbw202gpo=0x99333322
+mcsbw205ghpo=0x8a875444
+mcsbw205glpo=0x8a875444
+mcsbw205gmpo=0x8a875444
+mcsbw405ghpo=0xda844333
+mcsbw405glpo=0xda844333
+mcsbw405gmpo=0xdb844333
+mcsbw805ghpo=0xda555444
+mcsbw805glpo=0xdb555444
+mcsbw805gmpo=0xda555444
nocrc=1
ofdmlrbw202gpo=0x0033
pa2ga0=-112,6296,-662

To use this patch, copy it off into a file and use the <code>patch</code> command.
However, it might be easier to apply the patch by hand.
To do this, open the file <code>/usr/lib/firmware/brcm/brcmfmac43455-sdio.txt</code> (after completing the copy step above), delete the line with <code>maxp2ga0=64</code> through the line with <code>muxenab=0x10</code>.
Then add the following in its place:
maxp2ga0=70
maxp5ga0=73,74,73,73
mcsbw202gpo=0x99333322
mcsbw205ghpo=0x8a875444
mcsbw205glpo=0x8a875444
mcsbw205gmpo=0x8a875444
mcsbw405ghpo=0xda844333
mcsbw405glpo=0xda844333
mcsbw405gmpo=0xdb844333
mcsbw805ghpo=0xda555444
mcsbw805glpo=0xdb555444
mcsbw805gmpo=0xda555444

Reboot and the Wi-Fi (at least for 5GHz networks) should work well. It is not exactly clear what these fields do, so the impact this has on the Wi-Fi module or your ability to operate it legally in your country is not certain. It seems that this file is passed directly to the hardware, where it is interpreted by the Wi-Fi module itself. However, given that this file is simply a combination of other existing files for similar hardware, it might be fine to use.
The patch above only pulls in lines from the following firmware file: https://github.com/reMarkable/brcmfmac-firmware/blob/master/brcmfmac43455-sdio.txt.
This code comes with the following license - which is not replicated here because it will fill this wiki with text - see the link here for the license: https://github.com/reMarkable/brcmfmac-firmware/blob/master/LICENCE.

=== Stabilizing the system (underclocking the RAM) ===
By default, it seems that the some RockPro64 devices are not stable. This seems to manifest as gcc segfaulting randomly. Usually, this can be "fixed" by starting the build again and hoping gcc doesn't crash. If the build finishes or crashes at a different point, this is a good indicator that the system is not stable. The issue seems to be that the RAM is running a little too fast and some bits are getting randomly flipped. In this thread, it seems that the solution is to bring the RAM all the way down to 333MHz: https://forum.pine64.org/showthread.php?tid=11209. Other frequencies are possible, but the highest officially supported frequency below 800MHz is 666MHz, which is still a big step down from the default frequency of 800MHz provided by ManjaroARM. It is also possible to set arbitrary frequencies in u-boot. Frequencies that have been tested with this method are 702MHz and 752MHz. It seems that there is only a slight performance decrease at 752MHz compared to 800MHz. The PKGBUILD for this is available here: https://aur.archlinux.org/packages/uboot-rockpro64-foss

By default, this PKGBUILD uses the default RAM speed of 800MHz. Uncomment the line that begins with "patch" to enable the 752MHz patch. Details are in the comments at the top of the PKGBUILD.
If you would like to try out other frequencies, follow the instructions in the comments at the top of the PKGBUILD.

After building and installing, the install hook will prompt you on if you want to install the new build of U-Boot to EMMC. If you want to, press Y, otherwise, hit N and then copy and paste the printed <code>dd</code> commands and modify them to write to the correct device (change the <code>/dev/mmcblk</code> part).

After installing U-Boot and rebooting, U-Boot should print out that it set the RAM to 400MHz (initially). Then a few lines down, the RAM should be set to 752MHz.

[[Category:ROCKPro64]] [[Category:Rockchip RK3399]]

ROCKPro64 Getting Started

2023-05-29T19:17:09Z

I3master: Updated SPI flash install instructions.

This section gives important information to get the board up and running.

== Video Playback ==

Hardware video acceleration is supported in recent kernels and user needs only to install the relevant Mesa packages/ports, specifically the Mesa DRI drivers for Mali GPUs (Midgard/Bifrost). One can confirm via software glxinfo, or having the library file such as .../lib/dri/panfrost_dri.so.

Ayufan has some old documentation on [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/video-playback.md video playback here.] For your ROCKPro64 the install should be

<code>sudo apt-get install ffmpeg mpv libmali-rk-midgard-t86x-r14p0-gbm</code>

(These modules are included in the Ayufan desktop releases.) At which stage rkmpv myvideo.mp4 will play a fullscreen, hardware assisted, version of your video. rkmpv is at /usr/local/bin/rkmpv

== Using an NVMe Disk as rootfs ==

Forum member Bullet64 has documented [https://forum.frank-mankel.org/topic/208/booten-von-der-nvme-platte how to move rootfs to an NVMe disk.] This is useful until we get a full SPI option to boot from the NVMe.

== Setup a Serial Console (UART2) ==

{{Warning|RockPro64 is designed to use 3VDC3A (3 Volts Direct Current 3 Ampere) for the connection, using 5VDC and more might damage the board!}}

To use Serial Console you will a need operating system that supports it on your RockPro64, by default the serial console is provided for baud 9 600 which is far too slow for rockpro64 so consider using 1 500 000 (1.5Mbps) instead IF your serial console device supports it (many doesn't which results in their inability to use the console).

{{Warning|Do not connect RxD (pin 10) until the U-Boot SPL is running (see [[RK3399 boot sequence]]) or the SPL will not start.

To avoid this issue, a simple [[ROCKPro64 Serial Buffer Circuit]] can be installed between the RockPro64 and the serial adapter.}}

In terms of connections you need to perform the following from your serial console-capable device e.g. Pine64's Woodpecker available in store:

* GND <-> GND (pin 6)
* RxD <-> TxD (pin 8)
* TxD <-> RxD (pin 10)

After the configuration of your preferred operating system you can connect to the serial console using any of these commands:

$ screen /dev/ttyUSB0 1500000

$ picocom /dev/ttyUSB0 -b 1500000

$ minicom -D /dev/ttyUSB0 -b 1500000

NOTE: You might need a root permission if your user is not in the appropriate user-group e.g. <code>dialup</code> on GNU/Linux

Alternatively there is a detailed guide on forums: https://forum.pine64.org/showthread.php?tid=6387

GNU/Linux:

* With GNU/Linux on your RockPro64 the built-in support for serial console can be enabled by parsing parse e.g. <code>console=ttyS2,1500000n8</code> in the kernel command line, many distributions make this available by default, but consider verifying the contents of <code>/boot/extlinux/extlinux.conf</code> if you encounter issues.
* NOTE: the <code>n8</code> in the kernel argument means no parity, 8 bits per character

== Booting from USB or PXE ==

The default choice of boot device is first eMMC (if present) then SDcard. See [[ROCKPro64#Disable_eMMC | jumpers above for details on adjusting this sequence.]]

It is possible to flash the SPI to extend the options for boot devices to USB drives or PXE. The preferred method is now the rock64_write_spi_flash.sh script (see [[ROCKPro64#Useful_scripts | useful scripts above.]]) The Getting started wiki article has more details [[Getting started#Flashing_u-boot_to_SPI_Flash | here.]]

Background info and historic details of this usage [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/flash-spi.md can be found here.]
== Booting from SATA ==
U-Boot supports booting from SATA devices. However, it seems that this support was broken for the RockPro64 until U-Boot 2023.04. This version is not yet supplied by ManjaroARM, but can be compiled relatively easily in ManjaroARM and installed. The PKGBUILD here provides a version of U-Boot that supports SATA boot: https://aur.archlinux.org/packages/uboot-rockpro64-foss
There are instructions in the pinned comment on how to build this in ArchLinuxARM if needed.

Note that with this configuration, U-Boot is compiled to be installed on a micro SD card or EMMC module (at a specific address - not in a filesystem).
The install hook provided in this PKGBUILD will ask you if you want to write U-Boot to an EMMC module. If you want to install to a micro SD card instead, press 'n' when prompted and modify the `dd` commands that are printed out. The installer will then prompt to check if you want to install U-Boot to SPI flash. Hit 'Y' and then enter if this is what you want to do, but be sure that you know how to recover from a corrupted SPI flash (as SPI is the first boot device).
If you would prefer to install U-Boot to SPI flash yourself, see the guide here: https://wiki.gentoo.org/wiki/PINE64_ROCKPro64/Installing_U-Boot.

Once installed, both the boot partition and root partition may now exist on a SATA device.

=== Troubleshooting ===
If U-Boot fails to boot from SATA, you can attempt to debug the issue through the U-Boot command line.
* After booting your RockPro64, press any key repeatedly. Enter works well as it won't type anything on the screen when the prompt comes up.
* Once you get a prompt, type <code>pci</code> and hit enter. This will initialize the U-Boot PCIe subsystem. It is necessary for scanning for SATA devices.
* Now, type <code>scsi scan</code> and hit enter. This will scan for SATA devices. You should see your SATA device show up in the list with its reported capacity.
* You can now attempt to list partitions on the SATA device by running <code>part list scsi 0</code>. You may need to change the device number on the end (0 in the example) to match what was reported by the <code>scsi scan</code> command.

== Booting from SPI using u-boot ==

{{Warning|idbloader is not open-source}}

Always be prepared to recover from a broken SPI boot BEFORE flashing or you will end up with a broken boot.

In general the recovery is killswitching SPI through shorting pins 23 <-> 25 together and then loading u-boot from a storage device e.g. SD-card or eMMC where majority of GNU distributions e.g. Manjaro usually have u-boot packaged with the provided images.

Follow instructions in https://github.com/sigmaris/u-boot/wiki/Flashing-U-Boot-to-SPI#instructions-for-rockpro64

== Boot sequence ==

The RockPro64 boot sequence has been documented [https://github.com/sigmaris/u-boot/wiki/RockPro64-boot-sequence here] by sigmaris.

== OTG Mode ==

You can boot your ROCKPro64 into OTG mode with the use of the Recover button (see [[ROCKPro64#Switches | switch 28 above.]]) Note there are 2 OTG ports on your ROCKPro64: the type-C USB 3 socket is definitely one. From the schematic it appears the USB 3 (type A) socket is the other, but this has yet to be confirmed.

The method is to power off the board. Then push and hold the Recover button and push and release the Power button.
* If you have an Ayufan bootable image in either the SD-card or eMMC then there are 4 OTG modes [https://github.com/ayufan-rock64/linux-u-boot/commit/ea6efecdfecc57c853a6f32f78469d1b2417329b described here] including Android fastboot, RockUSB and MaskROM modes. Releasing the Recover button as soon as the white LED lights counts as 1 blink. Keeping it pressed you will get 2 blinks of the white LED etc. Once the board enters OTG mode the red LED will be lit. In mode 1 the boot and linux-root partitions of the card with the Ayufan image (partitions 6 & 7 of a Linux installation) are made available as devices. In all cases the USB device made available at the host has device ID 18d1:d00d.
* If you do not have an Ayufan image in either the SD-card or the eMMC, then neither white nor red LEDs will light, but the board will enter MaskROM mode where the USB device made available at the host has device ID 2207:330c.

== NVMe Drives ==

Please be aware that [https://pine64.com/product/rockpro64-pci-e-x4-to-m-2-ngff-nvme-ssd-interface-card the PINE64 SSD interface card] is intended for use with NVMe devices. These can be identified by the fact they have a single (Key M) notch, e.g. [https://www.wdc.com/content/dam/wdc/website/products/family/wd-black-pcie-ssd/wdfWDBlackSSD_PCIe_img1.jpg.imgw.500.500.jpg the WD Black devices.]

While M2/NGFF SATA devices (with a Key B notch, typically have Key M as well) will physically fit, they will not work. e.g. [https://www.wdc.com/content/dam/wdc/website/products/personal/internal_storage/wd_blue_3d_nand_sata_ssd/blue3d_product-overview.jpg.imgw.1000.1000.jpg WD Blue devices.]

== SATA Drives ==

SATA drives can be connected directly via the [https://pine64.com/product/pcie-to-dual-sata-iii-interface-card/ ROCKPro64 PCIe interface card.] Please note the card does not include the power cable - that is a [https://pine64.com/?product=rockpro64-power-cable-for-dual-sata-drives separate item.] Equally you must be aware that connecting SATA drives in this manner means they will be drawing power from your ROCKPro64 - please ensure you are using a 5A or better power supply.

ExplainingComputers did a YouTube [https://www.youtube.com/watch?v=9CCQicHwfDI ROCKPro64 PCIe SATA card review and tests using a Ubuntu console and OpenMediaVault.]

== Wi-Fi & Bluetooth Module ==
If you have bought the [https://pine64.com/product/rockpro64-1x1-dual-band-wifi-802-11ac-bluetooth-5-0-module Wi-Fi and Bluetooth module] from the Pine store then instructions for connecting it can be found on the accessories page [[Accessories_Step_by_Step_Guides#Wifi.2FBluetooth_module | here.]] '''Please note that the 0.7.9 Ayufan's Linux releases (August 2018) have deliberately DISABLED support for this module in the search for stability. It can be tested and used with the Android image.'''

It can also be used on Manjaro by installing ap6256-firmware and wireless-regdb packages.

== 7" LCD Touch Screen ==

Instructions for connecting the [https://pine64.com/?product=7-lcd-touch-screen-panel LCD touch screen] from the Pine [[Accessories_Step_by_Step_Guides#7.22_LCD_Touch_Screen_Panel | are here.]]

'''Note at present (August 2018) this screen is only supported by the Android image.'''

{{Warning|When using the touchscreen ensure the cables are properly connected and tightened down and that you do not let the metal backplate touch the SBC}}

== RTC Battery Backup ==

The Pine store has a couple of options for RTC battery backups: a [https://pine64.com/product/rtc-backup-battery-holder-2-x-aaa AAA version here] or a [https://pine64.com/product/rtc-backup-battery-holder-cr-2032 CR-2032 version here.] Instructions for plugging in either of them are also on the [[Accessories_Step_by_Step_Guides| Accessories page ]]. For the ROCKPro64, the backup plugs into the RTC connector, number 6 in the board layout diagram above, next to the USB3 and case screw point.

== Acrylic Open Enclosure ==

Assembly instructions for the [https://pine64.com/product/pine-a64-rockpro64-acrylic-open-enclosure acrylic enclosure] from the Pine store are also on the [[Accessories_Step_by_Step_Guides| Accessories page ]]

== NAS case ==

The [https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf Exploded View Installation Diagram] for the [https://pine64.com/product/rockpro64-metal-desktop-nas-casing NAS case from the Pine store].

Detailed '''NAS Case overview and assembly instructions''' can be found [[NASCase | here]].

ROCKPro64

2023-05-29T02:56:54Z

I3master: Added RAM underclocking instructions.

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful Single Board Computer released by PINE64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a Mali T-860 Quad-Core GPU. The key features include a PCIe x4 open ended slot, the use of LPDDR4 RAM, and industry standard heatsink mounting holes.

The ROCKPro64 is equipped with 2GB or 4GB LPDDR4 system memory, and 128Mb SPI boot Flash. There is also an optional eMMC module (up to 128GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 type C Host with DP 1.2, 1x USB 3.0 type A Host, 2x USB 2.0 Host, Gigabit Ethernet, PI-2 GPIO Bus, MiPi DSI interface, eDP interface, touch Panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different Operating Systems (OS) are freely available from the open source community, such as Android, Linux (Ubuntu, Debian, Arch), and BSD.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* 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
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* 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 Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 1 USB3.0 Host port
* 1 USB type C OTG port with DP output
* 2 USB2.0 Dedicated Host ports

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO Header
* PCIe 2.1 (4 full-duplex lanes with 20Gbps) x4 open ended port

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7″ LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
|
| For the "new" ROCKPro64 WIFI module: Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See [[#Getting wifi working ("new" wifi module)]] for the file contents and details.
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. After testing for a few hours, on Manjaro ARM (kernel 6.2.5), there haven't been stability issues found (WiFi stayed connected). On a 5GHz network (802.11AC), it was tested to be possible to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is near impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| https://pine64.com/?product=rockpro64-playbox-enclosure
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://store.pine64.org/?product=rockpro64-heatsink
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCIe 2.1
|
|
|
|
|
|
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| https://store.pine64.org/?product=rtc-backup-battery-cr-battery
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: +12V @3A/5A with 5.5mm/2.1mm Type M Barrel type DC connector
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

* [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
* [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
* [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
* [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]

* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]

* [[ROCKPro64 Device Tree Overlays on Mainline]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NASCase|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A Quartz64-A mounted in an ITX case using 3D printed brackets]]

Allows mounting a ROCKPro64-A or Quartz64-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in your log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

Log in to your ROCKPro64, and run the following:

sudo -i
echo governor_simpleondemand >> /etc/initramfs-tools/modules && update-initramfs -u -k $(uname -r)
exit

Then, reboot.

== Hardware "Hacking" ==

=== Enabling PCIe 2.0 ===
By default, the RockPro64 runs the PCIe slot at gen 1 speeds because there might be stability issues with gen 2 speeds. The port can be switched back to gen 2 speeds by adding the following device tree overlay.

1. Copy and paste the device tree overlay file below into a new file (you could name it <code>pcie-2.0.dts</code>):
// Pulled from: https://forum.armbian.com/topic/23574-howto-enable-pcie-gen2-to-get-max-speed-of-nvme-rockpi-4b/
/dts-v1/;
/plugin/;

&pcie0 {
max-link-speed = <0x03>;
};

2. Compile the device tree into a binary file. Note that you will need <code>dtc</code> installed.
dtc -I dts -O dtb -@ pcie-2.0.dts -o pcie-2.0.dto

4. Copy or move the device tree from the current directory into the boot partition (in this case into the <code>/boot/dtbs/overlay/</code> folder). If you haven't yet created the <code>/boot/dtbs/overlay/</code> folder, then create it with <code>sudo mkdir /boot/dtbs/overlay/</code>
sudo cp pcie-2.0.dto /boot/dtbs/overlay/

5. Add the device compiled tree overlay file to the list of files u-boot needs to load. If you are using ManjaroARM (or ArchLinuxARM with a <code>extlinux.conf</code> file), then add the following line to the file <code>/boot/extlinux/extlinux.conf</code>:
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb

If you already have an <code>FDTOVERLAYS</code> line, then add a space at the end of the current line, then add this overlay file after that.
See here for details on this process: [[ROCKPro64 Device Tree Overlays on Mainline]]

The resulting <code>/boot/extlinux/extlinux.conf</code> file might look like below after adding this dtb file:
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb /dtbs/overlay/cpu-overclock.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 zfs=zroot rw rootwait audit=0 cpufreq.default_governor=schedutil

=== Overclocking (and undervolting) ===
The RK3399 can be overclocked. See here for details: [[Overclocking#RK3399-based devices]].
By overclocking, you do risk damaging your hardware, however, it is possible to achieve small, but measurable improvements in performance with an overclock. The overclock can be applied with a device tree overlay file.
Below is an example device tree overlay for CPU overclocking on the RockPro64. It may or may not work well on your device, but I found that these speeds were stable for me.
The example below bumps the little cores up to 1.608GHz from 1.416GHz and bumps the big cores up to 2.088GHz from 1.8GHz.

1. Copy and paste the device tree overlay file below into a new file (you could name it <code>cpu-overclock.dts</code>):
// Pulled from: https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi
/dts-v1/;
/plugin/;

&cluster0_opp {
opp00 {
opp-hz = /bits/ 64 <408000000>;
opp-microvolt = <800000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <825000>;
};
opp02 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <850000>;
};
opp03 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <900000>;
};
opp04 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <975000>;
};
opp05 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <1100000>;
};
opp06 {
opp-hz = /bits/ 64 <1512000000>;
opp-microvolt = <1150000>;
};
opp07 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1200000>;
};
};
&cluster1_opp {
opp00 {
opp-hz = /bits/ 64 <408000000>;
opp-microvolt = <800000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <800000>;
};
opp02 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <825000>;
};
opp03 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <850000>;
};
opp04 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <900000>;
};
opp05 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <975000>;
};
opp06 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1050000>;
};
opp07 {
opp-hz = /bits/ 64 <1800000000>;
opp-microvolt = <1150000>;
};
opp08 {
opp-hz = /bits/ 64 <2016000000>;
opp-microvolt = <1250000>;
};
opp09 {
opp-hz = /bits/ 64 <2088000000>;
opp-microvolt = <1250000>;
};
};

2. Compile the device tree into a binary file. Note that you will need <code>dtc</code> installed.
dtc -I dts -O dtb -@ cpu-overclock.dts -o cpu-overclock.dto

4. Copy or move the device tree from the current directory into the boot partition (in this case into the <code>/boot/dtbs/overlay/</code> folder). If you haven't yet created the <code>/boot/dtbs/overlay/</code> folder, then create it with <code>sudo mkdir /boot/dtbs/overlay/</code>
sudo cp cpu-overclock.dto /boot/dtbs/overlay/

5. Add the device compiled tree overlay file to the list of files u-boot needs to load. If you are using ManjaroARM (or ArchLinuxARM with a <code>extlinux.conf</code> file), then add the following line to the file <code>/boot/extlinux/extlinux.conf</code>:
FDTOVERLAYS /dtbs/overlay/cpu-overclock.dtb

If you already have an <code>FDTOVERLAYS</code> line, then add a space at the end of the current line, then add this overlay file after that.
See here for details on this process: [[ROCKPro64 Device Tree Overlays on Mainline]]

The resulting <code>/boot/extlinux/extlinux.conf</code> file might look like below after adding this dtb file:
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb /dtbs/overlay/cpu-overclock.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 zfs=zroot rw rootwait audit=0 cpufreq.default_governor=schedutil

=== Getting wifi working ("new" wifi module) ===
ManjaroARM and ArchLinuxARM (and probably others) provide the NVRAM file needed to initialize the Wi-Fi module in the linux-firmware package, but it is listed under the generic name <code>brcmfmac43455-sdio.AW-CM256SM.txt</code>.
You can copy this file to the new name (that the driver looks for) with the following commands:
cd /usr/lib/firmware/brcm/
sudo cp brcmfmac43455-sdio.AW-CM256SM.txt brcmfmac43455-sdio.txt

Then, reboot and Wi-Fi should start working.
Details for this method are here: https://forum.pine64.org/showthread.php?tid=16635&pid=117061#pid117061
However, I noticed that on a 5GHz network with <code>wireless-regdb</code> installed and the regulatory domain set correctly (to 'US' for me), the adapter was almost unusable. Speeds were usually 0 bits per second. Sometimes a few packets would get through every few seconds, but that was it. On a 2.4GHz network, this was not an issue. This "can" be resolved by setting the regulator domain to 'GB' or 'CN', but this doesn't seem like a great solution. Instead, I tried various other <code>brcmfmac43455-sdio.txt</code> files found online. Some worked better than others. I combined parts of various files and found that applying the patch below to the default <code>brcmfmac43455-sdio.AW-CM256SM.txt</code> file fixed the issue. I was able to get about 140Mbps up and down with this patch (with the regulatory domain set correctly to 'US').

--- brcmfmac43455-sdio.AW-CM256SM.txt 2023-04-27 19:16:47.000000000 -0500
+++ brcmfmac43455-sdio.txt 2023-05-21 11:42:22.058517093 -0500
@@ -21,19 +21,18 @@
ltecxpadnum=0x0504
macaddr=00:90:4c:c5:12:38
manfid=0x2d0
-maxp2ga0=64
-maxp5ga0=80,82,76,77
-mcsbw202gpo=0x99355533
-mcsbw205ghpo=0x99855000
-mcsbw205glpo=0x99755000
-mcsbw205gmpo=0x9df55000
-mcsbw405ghpo=0xd9755000
-mcsbw405glpo=0xb8555000
-mcsbw405gmpo=0xed955000
-mcsbw805ghpo=0xd9555000
-mcsbw805glpo=0xc8555000
-mcsbw805gmpo=0xe9555000
-muxenab=0x10
+maxp2ga0=70
+maxp5ga0=73,74,73,73
+mcsbw202gpo=0x99333322
+mcsbw205ghpo=0x8a875444
+mcsbw205glpo=0x8a875444
+mcsbw205gmpo=0x8a875444
+mcsbw405ghpo=0xda844333
+mcsbw405glpo=0xda844333
+mcsbw405gmpo=0xdb844333
+mcsbw805ghpo=0xda555444
+mcsbw805glpo=0xdb555444
+mcsbw805gmpo=0xda555444
nocrc=1
ofdmlrbw202gpo=0x0033
pa2ga0=-112,6296,-662

To use this patch, copy it off into a file and use the <code>patch</code> command.
However, it might be easier to apply the patch by hand.
To do this, open the file <code>/usr/lib/firmware/brcm/brcmfmac43455-sdio.txt</code> (after completing the copy step above), delete the line with <code>maxp2ga0=64</code> through the line with <code>muxenab=0x10</code>.
Then add the following in its place:
maxp2ga0=70
maxp5ga0=73,74,73,73
mcsbw202gpo=0x99333322
mcsbw205ghpo=0x8a875444
mcsbw205glpo=0x8a875444
mcsbw205gmpo=0x8a875444
mcsbw405ghpo=0xda844333
mcsbw405glpo=0xda844333
mcsbw405gmpo=0xdb844333
mcsbw805ghpo=0xda555444
mcsbw805glpo=0xdb555444
mcsbw805gmpo=0xda555444

Reboot and the Wi-Fi (at least for 5GHz networks) should work well. I was unable to determine what these fields do, so I am not sure what impact this has on the Wi-Fi module or your ability to operate it legally in your country. From what I can tell (and I haven't looked into the process in too much depth), it seems that this file is passed directly to the hardware, where it is interpreted by the Wi-Fi module itself, but I am not sure on this. However, given that this file is simply a combination of other existing files for similar hardware, I would think that it should be fine.
I ended up pulling lines only from the file here: https://github.com/reMarkable/brcmfmac-firmware/blob/master/brcmfmac43455-sdio.txt.
This code comes with the following license (which I will not replicate here because it will fill this wiki with text - instead I have provided a link to its source): https://github.com/reMarkable/brcmfmac-firmware/blob/master/LICENCE.
I believe this license allows me to take these lines from one of the config files and provide them here in patch format.

=== Stabilizing the system (underclocking the RAM) ===
By default, it seems that the some RockPro64 devices are not stable. This seems to manifest as gcc segfaulting randomly. Usually, this can be "fixed" by starting the build again and hoping gcc doesn't crash. If the build finishes or crashes at a different point, this is a good indicator that the system is not stable. The issue seems to be that the RAM is running a little too fast and some bits are getting randomly flipped (at least for me). In this thread, it seems that the solution is to bring the RAM all the way down to 333MHz: https://forum.pine64.org/showthread.php?tid=11209. Other frequencies are possible, but the highest officially supported frequency below 800MHz I found was 666MHz, which is still a big step down from the default frequency of 800MHz provided by ManjaroARM. After looking through the U-Boot code, I found that it seems to be possible to set arbitrary frequencies. After giving this a test, I found that 702MHz was stable. After that, I tried a bit higher (at 752MHz). This was also stable. Given that this is less than 50MHz away from being unstable, I stopped there. It seems that there is only a slight performance decrease at this frequency compared to 800MHz. The PKGBUILD for this is available here: https://aur.archlinux.org/packages/uboot-rockpro64-foss

By default, this PKGBUILD uses the default RAM speed of 800MHz. Uncomment the line that begins with "patch" to enable the 752MHz patch. Details are in the comments at the top of the PKGBUILD.
If you would like to try out other frequencies, follow the instructions in the comments at the top of the PKGBUILD.

After building and installing, the install hook will prompt you on if you want to install the new build of U-Boot to EMMC. If you want to, press Y, otherwise, hit N and then copy and paste the printed <code>dd</code> commands and modify them to write to the correct device (change the <code>/dev/mmcblk</code> part).

After installing U-Boot and rebooting, U-Boot should print out that it set the RAM to 400MHz (initially). Then a few lines down, the RAM should be set to 752MHz.

[[Category:ROCKPro64]] [[Category:Rockchip RK3399]]

ROCKPro64 Getting Started

2023-05-29T01:25:41Z

I3master: added a missing word.

This section gives important information to get the board up and running.

== Video Playback ==

Hardware video acceleration is supported in recent kernels and user needs only to install the relevant Mesa packages/ports, specifically the Mesa DRI drivers for Mali GPUs (Midgard/Bifrost). One can confirm via software glxinfo, or having the library file such as .../lib/dri/panfrost_dri.so.

Ayufan has some old documentation on [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/video-playback.md video playback here.] For your ROCKPro64 the install should be

<code>sudo apt-get install ffmpeg mpv libmali-rk-midgard-t86x-r14p0-gbm</code>

(These modules are included in the Ayufan desktop releases.) At which stage rkmpv myvideo.mp4 will play a fullscreen, hardware assisted, version of your video. rkmpv is at /usr/local/bin/rkmpv

== Using an NVMe Disk as rootfs ==

Forum member Bullet64 has documented [https://forum.frank-mankel.org/topic/208/booten-von-der-nvme-platte how to move rootfs to an NVMe disk.] This is useful until we get a full SPI option to boot from the NVMe.

== Setup a Serial Console (UART2) ==

{{Warning|RockPro64 is designed to use 3VDC3A (3 Volts Direct Current 3 Ampere) for the connection, using 5VDC and more might damage the board!}}

To use Serial Console you will a need operating system that supports it on your RockPro64, by default the serial console is provided for baud 9 600 which is far too slow for rockpro64 so consider using 1 500 000 (1.5Mbps) instead IF your serial console device supports it (many doesn't which results in their inability to use the console).

{{Warning|Do not connect RxD (pin 10) until the U-Boot SPL is running (see [[RK3399 boot sequence]]) or the SPL will not start.

To avoid this issue, a simple [[ROCKPro64 Serial Buffer Circuit]] can be installed between the RockPro64 and the serial adapter.}}

In terms of connections you need to perform the following from your serial console-capable device e.g. Pine64's Woodpecker available in store:

* GND <-> GND (pin 6)
* RxD <-> TxD (pin 8)
* TxD <-> RxD (pin 10)

After the configuration of your preferred operating system you can connect to the serial console using any of these commands:

$ screen /dev/ttyUSB0 1500000

$ picocom /dev/ttyUSB0 -b 1500000

$ minicom -D /dev/ttyUSB0 -b 1500000

NOTE: You might need a root permission if your user is not in the appropriate user-group e.g. <code>dialup</code> on GNU/Linux

Alternatively there is a detailed guide on forums: https://forum.pine64.org/showthread.php?tid=6387

GNU/Linux:

* With GNU/Linux on your RockPro64 the built-in support for serial console can be enabled by parsing parse e.g. <code>console=ttyS2,1500000n8</code> in the kernel command line, many distributions make this available by default, but consider verifying the contents of <code>/boot/extlinux/extlinux.conf</code> if you encounter issues.
* NOTE: the <code>n8</code> in the kernel argument means no parity, 8 bits per character

== Booting from USB or PXE ==

The default choice of boot device is first eMMC (if present) then SDcard. See [[ROCKPro64#Disable_eMMC | jumpers above for details on adjusting this sequence.]]

It is possible to flash the SPI to extend the options for boot devices to USB drives or PXE. The preferred method is now the rock64_write_spi_flash.sh script (see [[ROCKPro64#Useful_scripts | useful scripts above.]]) The Getting started wiki article has more details [[Getting started#Flashing_u-boot_to_SPI_Flash | here.]]

Background info and historic details of this usage [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/flash-spi.md can be found here.]
== Booting from SATA ==
U-Boot supports booting from SATA devices. However, it seems that this support was broken for the RockPro64 until U-Boot 2023.04. This version is not yet supplied by ManjaroARM, but can be compiled relatively easily in ManjaroARM and installed. The PKGBUILD here provides a version of U-Boot that supports SATA boot: https://aur.archlinux.org/packages/uboot-rockpro64-foss
There are instructions in the pinned comment on how to build this in ArchLinuxARM if needed.

Note that with this configuration, U-Boot is compiled to be installed on a micro SD card or EMMC module (at a specific address - not in a filesystem).
The install hook provided in this PKGBUILD will ask you if you want to write U-Boot to an EMMC module. If you want to install to a micro SD card instead, press 'n' when prompted and modify the `dd` commands that are printed out. It should be possible to run the <code>mkimage</code> command to generate an SPI image of U-Boot. See here for details: https://wiki.gentoo.org/wiki/PINE64_ROCKPro64/Installing_U-Boot.

Once installed, both the boot partition and root partition may now exist on a SATA device.

=== Troubleshooting ===
If U-Boot fails to boot from SATA, you can attempt to debug the issue through the U-Boot command line.
* After booting your RockPro64, press any key repeatedly. Enter works well as it won't type anything on the screen when the prompt comes up.
* Once you get a prompt, type <code>pci</code> and hit enter. This will initialize the U-Boot PCIe subsystem. It is necessary for scanning for SATA devices.
* Now, type <code>scsi scan</code> and hit enter. This will scan for SATA devices. You should see your SATA device show up in the list with its reported capacity.
* You can now attempt to list partitions on the SATA device by running <code>part list scsi 0</code>. You may need to change the device number on the end (0 in the example) to match what was reported by the <code>scsi scan</code> command.

== Booting from SPI using u-boot ==

{{Warning|idbloader is not open-source}}

Always be prepared to recover from a broken SPI boot BEFORE flashing or you will end up with a broken boot.

In general the recovery is killswitching SPI through shorting pins 23 <-> 25 together and then loading u-boot from a storage device e.g. SD-card or eMMC where majority of GNU distributions e.g. Manjaro usually have u-boot packaged with the provided images.

Follow instructions in https://github.com/sigmaris/u-boot/wiki/Flashing-U-Boot-to-SPI#instructions-for-rockpro64

== Boot sequence ==

The RockPro64 boot sequence has been documented [https://github.com/sigmaris/u-boot/wiki/RockPro64-boot-sequence here] by sigmaris.

== OTG Mode ==

You can boot your ROCKPro64 into OTG mode with the use of the Recover button (see [[ROCKPro64#Switches | switch 28 above.]]) Note there are 2 OTG ports on your ROCKPro64: the type-C USB 3 socket is definitely one. From the schematic it appears the USB 3 (type A) socket is the other, but this has yet to be confirmed.

The method is to power off the board. Then push and hold the Recover button and push and release the Power button.
* If you have an Ayufan bootable image in either the SD-card or eMMC then there are 4 OTG modes [https://github.com/ayufan-rock64/linux-u-boot/commit/ea6efecdfecc57c853a6f32f78469d1b2417329b described here] including Android fastboot, RockUSB and MaskROM modes. Releasing the Recover button as soon as the white LED lights counts as 1 blink. Keeping it pressed you will get 2 blinks of the white LED etc. Once the board enters OTG mode the red LED will be lit. In mode 1 the boot and linux-root partitions of the card with the Ayufan image (partitions 6 & 7 of a Linux installation) are made available as devices. In all cases the USB device made available at the host has device ID 18d1:d00d.
* If you do not have an Ayufan image in either the SD-card or the eMMC, then neither white nor red LEDs will light, but the board will enter MaskROM mode where the USB device made available at the host has device ID 2207:330c.

== NVMe Drives ==

Please be aware that [https://pine64.com/product/rockpro64-pci-e-x4-to-m-2-ngff-nvme-ssd-interface-card the PINE64 SSD interface card] is intended for use with NVMe devices. These can be identified by the fact they have a single (Key M) notch, e.g. [https://www.wdc.com/content/dam/wdc/website/products/family/wd-black-pcie-ssd/wdfWDBlackSSD_PCIe_img1.jpg.imgw.500.500.jpg the WD Black devices.]

While M2/NGFF SATA devices (with a Key B notch, typically have Key M as well) will physically fit, they will not work. e.g. [https://www.wdc.com/content/dam/wdc/website/products/personal/internal_storage/wd_blue_3d_nand_sata_ssd/blue3d_product-overview.jpg.imgw.1000.1000.jpg WD Blue devices.]

== SATA Drives ==

SATA drives can be connected directly via the [https://pine64.com/product/pcie-to-dual-sata-iii-interface-card/ ROCKPro64 PCIe interface card.] Please note the card does not include the power cable - that is a [https://pine64.com/?product=rockpro64-power-cable-for-dual-sata-drives separate item.] Equally you must be aware that connecting SATA drives in this manner means they will be drawing power from your ROCKPro64 - please ensure you are using a 5A or better power supply.

ExplainingComputers did a YouTube [https://www.youtube.com/watch?v=9CCQicHwfDI ROCKPro64 PCIe SATA card review and tests using a Ubuntu console and OpenMediaVault.]

== Wi-Fi & Bluetooth Module ==
If you have bought the [https://pine64.com/product/rockpro64-1x1-dual-band-wifi-802-11ac-bluetooth-5-0-module Wi-Fi and Bluetooth module] from the Pine store then instructions for connecting it can be found on the accessories page [[Accessories_Step_by_Step_Guides#Wifi.2FBluetooth_module | here.]] '''Please note that the 0.7.9 Ayufan's Linux releases (August 2018) have deliberately DISABLED support for this module in the search for stability. It can be tested and used with the Android image.'''

It can also be used on Manjaro by installing ap6256-firmware and wireless-regdb packages.

== 7" LCD Touch Screen ==

Instructions for connecting the [https://pine64.com/?product=7-lcd-touch-screen-panel LCD touch screen] from the Pine [[Accessories_Step_by_Step_Guides#7.22_LCD_Touch_Screen_Panel | are here.]]

'''Note at present (August 2018) this screen is only supported by the Android image.'''

{{Warning|When using the touchscreen ensure the cables are properly connected and tightened down and that you do not let the metal backplate touch the SBC}}

== RTC Battery Backup ==

The Pine store has a couple of options for RTC battery backups: a [https://pine64.com/product/rtc-backup-battery-holder-2-x-aaa AAA version here] or a [https://pine64.com/product/rtc-backup-battery-holder-cr-2032 CR-2032 version here.] Instructions for plugging in either of them are also on the [[Accessories_Step_by_Step_Guides| Accessories page ]]. For the ROCKPro64, the backup plugs into the RTC connector, number 6 in the board layout diagram above, next to the USB3 and case screw point.

== Acrylic Open Enclosure ==

Assembly instructions for the [https://pine64.com/product/pine-a64-rockpro64-acrylic-open-enclosure acrylic enclosure] from the Pine store are also on the [[Accessories_Step_by_Step_Guides| Accessories page ]]

== NAS case ==

The [https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf Exploded View Installation Diagram] for the [https://pine64.com/product/rockpro64-metal-desktop-nas-casing NAS case from the Pine store].

Detailed '''NAS Case overview and assembly instructions''' can be found [[NASCase | here]].

ROCKPro64 Getting Started

2023-05-29T01:24:48Z

I3master: Added SATA boot information.

This section gives important information to get the board up and running.

== Video Playback ==

Hardware video acceleration is supported in recent kernels and user needs only to install the relevant Mesa packages/ports, specifically the Mesa DRI drivers for Mali GPUs (Midgard/Bifrost). One can confirm via software glxinfo, or having the library file such as .../lib/dri/panfrost_dri.so.

Ayufan has some old documentation on [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/video-playback.md video playback here.] For your ROCKPro64 the install should be

<code>sudo apt-get install ffmpeg mpv libmali-rk-midgard-t86x-r14p0-gbm</code>

(These modules are included in the Ayufan desktop releases.) At which stage rkmpv myvideo.mp4 will play a fullscreen, hardware assisted, version of your video. rkmpv is at /usr/local/bin/rkmpv

== Using an NVMe Disk as rootfs ==

Forum member Bullet64 has documented [https://forum.frank-mankel.org/topic/208/booten-von-der-nvme-platte how to move rootfs to an NVMe disk.] This is useful until we get a full SPI option to boot from the NVMe.

== Setup a Serial Console (UART2) ==

{{Warning|RockPro64 is designed to use 3VDC3A (3 Volts Direct Current 3 Ampere) for the connection, using 5VDC and more might damage the board!}}

To use Serial Console you will a need operating system that supports it on your RockPro64, by default the serial console is provided for baud 9 600 which is far too slow for rockpro64 so consider using 1 500 000 (1.5Mbps) instead IF your serial console device supports it (many doesn't which results in their inability to use the console).

{{Warning|Do not connect RxD (pin 10) until the U-Boot SPL is running (see [[RK3399 boot sequence]]) or the SPL will not start.

To avoid this issue, a simple [[ROCKPro64 Serial Buffer Circuit]] can be installed between the RockPro64 and the serial adapter.}}

In terms of connections you need to perform the following from your serial console-capable device e.g. Pine64's Woodpecker available in store:

* GND <-> GND (pin 6)
* RxD <-> TxD (pin 8)
* TxD <-> RxD (pin 10)

After the configuration of your preferred operating system you can connect to the serial console using any of these commands:

$ screen /dev/ttyUSB0 1500000

$ picocom /dev/ttyUSB0 -b 1500000

$ minicom -D /dev/ttyUSB0 -b 1500000

NOTE: You might need a root permission if your user is not in the appropriate user-group e.g. <code>dialup</code> on GNU/Linux

Alternatively there is a detailed guide on forums: https://forum.pine64.org/showthread.php?tid=6387

GNU/Linux:

* With GNU/Linux on your RockPro64 the built-in support for serial console can be enabled by parsing parse e.g. <code>console=ttyS2,1500000n8</code> in the kernel command line, many distributions make this available by default, but consider verifying the contents of <code>/boot/extlinux/extlinux.conf</code> if you encounter issues.
* NOTE: the <code>n8</code> in the kernel argument means no parity, 8 bits per character

== Booting from USB or PXE ==

The default choice of boot device is first eMMC (if present) then SDcard. See [[ROCKPro64#Disable_eMMC | jumpers above for details on adjusting this sequence.]]

It is possible to flash the SPI to extend the options for boot devices to USB drives or PXE. The preferred method is now the rock64_write_spi_flash.sh script (see [[ROCKPro64#Useful_scripts | useful scripts above.]]) The Getting started wiki article has more details [[Getting started#Flashing_u-boot_to_SPI_Flash | here.]]

Background info and historic details of this usage [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/flash-spi.md can be found here.]
== Booting from SATA ==
U-Boot supports booting from SATA devices. However, it seems that this support was broken for the RockPro64 until U-Boot 2023.04. This version is not yet supplied by ManjaroARM, but can be compiled relatively easily in ManjaroARM and installed. The PKGBUILD here provides a version of U-Boot that supports SATA boot: https://aur.archlinux.org/packages/uboot-rockpro64-foss
There are instructions in the pinned comment on how to build this in ArchLinuxARM if needed.

Note that with this configuration, U-Boot is compiled to be installed on a micro SD card or EMMC module (at a specific address - not in a filesystem).
The install hook provided in this PKGBUILD will ask you if you want to write U-Boot to an EMMC module. If you want to install to a micro SD card instead, press 'n' when prompted and modify the `dd` commands that are printed out. It should be possible to run the <code>mkimage</code> to generate an SPI image of U-Boot. See here for details: https://wiki.gentoo.org/wiki/PINE64_ROCKPro64/Installing_U-Boot.

Once installed, both the boot partition and root partition may now exist on a SATA device.

=== Troubleshooting ===
If U-Boot fails to boot from SATA, you can attempt to debug the issue through the U-Boot command line.
* After booting your RockPro64, press any key repeatedly. Enter works well as it won't type anything on the screen when the prompt comes up.
* Once you get a prompt, type <code>pci</code> and hit enter. This will initialize the U-Boot PCIe subsystem. It is necessary for scanning for SATA devices.
* Now, type <code>scsi scan</code> and hit enter. This will scan for SATA devices. You should see your SATA device show up in the list with its reported capacity.
* You can now attempt to list partitions on the SATA device by running <code>part list scsi 0</code>. You may need to change the device number on the end (0 in the example) to match what was reported by the <code>scsi scan</code> command.

== Booting from SPI using u-boot ==

{{Warning|idbloader is not open-source}}

Always be prepared to recover from a broken SPI boot BEFORE flashing or you will end up with a broken boot.

In general the recovery is killswitching SPI through shorting pins 23 <-> 25 together and then loading u-boot from a storage device e.g. SD-card or eMMC where majority of GNU distributions e.g. Manjaro usually have u-boot packaged with the provided images.

Follow instructions in https://github.com/sigmaris/u-boot/wiki/Flashing-U-Boot-to-SPI#instructions-for-rockpro64

== Boot sequence ==

The RockPro64 boot sequence has been documented [https://github.com/sigmaris/u-boot/wiki/RockPro64-boot-sequence here] by sigmaris.

== OTG Mode ==

You can boot your ROCKPro64 into OTG mode with the use of the Recover button (see [[ROCKPro64#Switches | switch 28 above.]]) Note there are 2 OTG ports on your ROCKPro64: the type-C USB 3 socket is definitely one. From the schematic it appears the USB 3 (type A) socket is the other, but this has yet to be confirmed.

The method is to power off the board. Then push and hold the Recover button and push and release the Power button.
* If you have an Ayufan bootable image in either the SD-card or eMMC then there are 4 OTG modes [https://github.com/ayufan-rock64/linux-u-boot/commit/ea6efecdfecc57c853a6f32f78469d1b2417329b described here] including Android fastboot, RockUSB and MaskROM modes. Releasing the Recover button as soon as the white LED lights counts as 1 blink. Keeping it pressed you will get 2 blinks of the white LED etc. Once the board enters OTG mode the red LED will be lit. In mode 1 the boot and linux-root partitions of the card with the Ayufan image (partitions 6 & 7 of a Linux installation) are made available as devices. In all cases the USB device made available at the host has device ID 18d1:d00d.
* If you do not have an Ayufan image in either the SD-card or the eMMC, then neither white nor red LEDs will light, but the board will enter MaskROM mode where the USB device made available at the host has device ID 2207:330c.

== NVMe Drives ==

Please be aware that [https://pine64.com/product/rockpro64-pci-e-x4-to-m-2-ngff-nvme-ssd-interface-card the PINE64 SSD interface card] is intended for use with NVMe devices. These can be identified by the fact they have a single (Key M) notch, e.g. [https://www.wdc.com/content/dam/wdc/website/products/family/wd-black-pcie-ssd/wdfWDBlackSSD_PCIe_img1.jpg.imgw.500.500.jpg the WD Black devices.]

While M2/NGFF SATA devices (with a Key B notch, typically have Key M as well) will physically fit, they will not work. e.g. [https://www.wdc.com/content/dam/wdc/website/products/personal/internal_storage/wd_blue_3d_nand_sata_ssd/blue3d_product-overview.jpg.imgw.1000.1000.jpg WD Blue devices.]

== SATA Drives ==

SATA drives can be connected directly via the [https://pine64.com/product/pcie-to-dual-sata-iii-interface-card/ ROCKPro64 PCIe interface card.] Please note the card does not include the power cable - that is a [https://pine64.com/?product=rockpro64-power-cable-for-dual-sata-drives separate item.] Equally you must be aware that connecting SATA drives in this manner means they will be drawing power from your ROCKPro64 - please ensure you are using a 5A or better power supply.

ExplainingComputers did a YouTube [https://www.youtube.com/watch?v=9CCQicHwfDI ROCKPro64 PCIe SATA card review and tests using a Ubuntu console and OpenMediaVault.]

== Wi-Fi & Bluetooth Module ==
If you have bought the [https://pine64.com/product/rockpro64-1x1-dual-band-wifi-802-11ac-bluetooth-5-0-module Wi-Fi and Bluetooth module] from the Pine store then instructions for connecting it can be found on the accessories page [[Accessories_Step_by_Step_Guides#Wifi.2FBluetooth_module | here.]] '''Please note that the 0.7.9 Ayufan's Linux releases (August 2018) have deliberately DISABLED support for this module in the search for stability. It can be tested and used with the Android image.'''

It can also be used on Manjaro by installing ap6256-firmware and wireless-regdb packages.

== 7" LCD Touch Screen ==

Instructions for connecting the [https://pine64.com/?product=7-lcd-touch-screen-panel LCD touch screen] from the Pine [[Accessories_Step_by_Step_Guides#7.22_LCD_Touch_Screen_Panel | are here.]]

'''Note at present (August 2018) this screen is only supported by the Android image.'''

{{Warning|When using the touchscreen ensure the cables are properly connected and tightened down and that you do not let the metal backplate touch the SBC}}

== RTC Battery Backup ==

The Pine store has a couple of options for RTC battery backups: a [https://pine64.com/product/rtc-backup-battery-holder-2-x-aaa AAA version here] or a [https://pine64.com/product/rtc-backup-battery-holder-cr-2032 CR-2032 version here.] Instructions for plugging in either of them are also on the [[Accessories_Step_by_Step_Guides| Accessories page ]]. For the ROCKPro64, the backup plugs into the RTC connector, number 6 in the board layout diagram above, next to the USB3 and case screw point.

== Acrylic Open Enclosure ==

Assembly instructions for the [https://pine64.com/product/pine-a64-rockpro64-acrylic-open-enclosure acrylic enclosure] from the Pine store are also on the [[Accessories_Step_by_Step_Guides| Accessories page ]]

== NAS case ==

The [https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf Exploded View Installation Diagram] for the [https://pine64.com/product/rockpro64-metal-desktop-nas-casing NAS case from the Pine store].

Detailed '''NAS Case overview and assembly instructions''' can be found [[NASCase | here]].

ROCKPro64

2023-05-29T01:00:27Z

I3master: Added license info

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful Single Board Computer released by PINE64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a Mali T-860 Quad-Core GPU. The key features include a PCIe x4 open ended slot, the use of LPDDR4 RAM, and industry standard heatsink mounting holes.

The ROCKPro64 is equipped with 2GB or 4GB LPDDR4 system memory, and 128Mb SPI boot Flash. There is also an optional eMMC module (up to 128GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 type C Host with DP 1.2, 1x USB 3.0 type A Host, 2x USB 2.0 Host, Gigabit Ethernet, PI-2 GPIO Bus, MiPi DSI interface, eDP interface, touch Panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different Operating Systems (OS) are freely available from the open source community, such as Android, Linux (Ubuntu, Debian, Arch), and BSD.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* 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
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* 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 Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 1 USB3.0 Host port
* 1 USB type C OTG port with DP output
* 2 USB2.0 Dedicated Host ports

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO Header
* PCIe 2.1 (4 full-duplex lanes with 20Gbps) x4 open ended port

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7″ LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
|
| For the "new" ROCKPro64 WIFI module: Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See [[#Getting wifi working ("new" wifi module)]] for the file contents and details.
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. After testing for a few hours, on Manjaro ARM (kernel 6.2.5), there haven't been stability issues found (WiFi stayed connected). On a 5GHz network (802.11AC), it was tested to be possible to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is near impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| https://pine64.com/?product=rockpro64-playbox-enclosure
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://store.pine64.org/?product=rockpro64-heatsink
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCIe 2.1
|
|
|
|
|
|
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| https://store.pine64.org/?product=rtc-backup-battery-cr-battery
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: +12V @3A/5A with 5.5mm/2.1mm Type M Barrel type DC connector
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

* [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
* [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
* [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
* [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]

* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]

* [[ROCKPro64 Device Tree Overlays on Mainline]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NASCase|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A Quartz64-A mounted in an ITX case using 3D printed brackets]]

Allows mounting a ROCKPro64-A or Quartz64-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in your log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

Log in to your ROCKPro64, and run the following:

sudo -i
echo governor_simpleondemand >> /etc/initramfs-tools/modules && update-initramfs -u -k $(uname -r)
exit

Then, reboot.

== Hardware "Hacking" ==

=== Enabling PCIe 2.0 ===
By default, the RockPro64 runs the PCIe slot at gen 1 speeds because there might be stability issues with gen 2 speeds. The port can be switched back to gen 2 speeds by adding the following device tree overlay.

1. Copy and paste the device tree overlay file below into a new file (you could name it <code>pcie-2.0.dts</code>):
// Pulled from: https://forum.armbian.com/topic/23574-howto-enable-pcie-gen2-to-get-max-speed-of-nvme-rockpi-4b/
/dts-v1/;
/plugin/;

&pcie0 {
max-link-speed = <0x03>;
};

2. Compile the device tree into a binary file. Note that you will need <code>dtc</code> installed.
dtc -I dts -O dtb -@ pcie-2.0.dts -o pcie-2.0.dto

4. Copy or move the device tree from the current directory into the boot partition (in this case into the <code>/boot/dtbs/overlay/</code> folder). If you haven't yet created the <code>/boot/dtbs/overlay/</code> folder, then create it with <code>sudo mkdir /boot/dtbs/overlay/</code>
sudo cp pcie-2.0.dto /boot/dtbs/overlay/

5. Add the device compiled tree overlay file to the list of files u-boot needs to load. If you are using ManjaroARM (or ArchLinuxARM with a <code>extlinux.conf</code> file), then add the following line to the file <code>/boot/extlinux/extlinux.conf</code>:
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb

If you already have an <code>FDTOVERLAYS</code> line, then add a space at the end of the current line, then add this overlay file after that.
See here for details on this process: [[ROCKPro64 Device Tree Overlays on Mainline]]

The resulting <code>/boot/extlinux/extlinux.conf</code> file might look like below after adding this dtb file:
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb /dtbs/overlay/cpu-overclock.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 zfs=zroot rw rootwait audit=0 cpufreq.default_governor=schedutil

=== Overclocking (and undervolting) ===
The RK3399 can be overclocked. See here for details: [[Overclocking#RK3399-based devices]].
By overclocking, you do risk damaging your hardware, however, it is possible to achieve small, but measurable improvements in performance with an overclock. The overclock can be applied with a device tree overlay file.
Below is an example device tree overlay for CPU overclocking on the RockPro64. It may or may not work well on your device, but I found that these speeds were stable for me.
The example below bumps the little cores up to 1.608GHz from 1.416GHz and bumps the big cores up to 2.088GHz from 1.8GHz.

1. Copy and paste the device tree overlay file below into a new file (you could name it <code>cpu-overclock.dts</code>):
// Pulled from: https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi
/dts-v1/;
/plugin/;

&cluster0_opp {
opp00 {
opp-hz = /bits/ 64 <408000000>;
opp-microvolt = <800000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <825000>;
};
opp02 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <850000>;
};
opp03 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <900000>;
};
opp04 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <975000>;
};
opp05 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <1100000>;
};
opp06 {
opp-hz = /bits/ 64 <1512000000>;
opp-microvolt = <1150000>;
};
opp07 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1200000>;
};
};
&cluster1_opp {
opp00 {
opp-hz = /bits/ 64 <408000000>;
opp-microvolt = <800000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <800000>;
};
opp02 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <825000>;
};
opp03 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <850000>;
};
opp04 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <900000>;
};
opp05 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <975000>;
};
opp06 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1050000>;
};
opp07 {
opp-hz = /bits/ 64 <1800000000>;
opp-microvolt = <1150000>;
};
opp08 {
opp-hz = /bits/ 64 <2016000000>;
opp-microvolt = <1250000>;
};
opp09 {
opp-hz = /bits/ 64 <2088000000>;
opp-microvolt = <1250000>;
};
};

2. Compile the device tree into a binary file. Note that you will need <code>dtc</code> installed.
dtc -I dts -O dtb -@ cpu-overclock.dts -o cpu-overclock.dto

4. Copy or move the device tree from the current directory into the boot partition (in this case into the <code>/boot/dtbs/overlay/</code> folder). If you haven't yet created the <code>/boot/dtbs/overlay/</code> folder, then create it with <code>sudo mkdir /boot/dtbs/overlay/</code>
sudo cp cpu-overclock.dto /boot/dtbs/overlay/

5. Add the device compiled tree overlay file to the list of files u-boot needs to load. If you are using ManjaroARM (or ArchLinuxARM with a <code>extlinux.conf</code> file), then add the following line to the file <code>/boot/extlinux/extlinux.conf</code>:
FDTOVERLAYS /dtbs/overlay/cpu-overclock.dtb

If you already have an <code>FDTOVERLAYS</code> line, then add a space at the end of the current line, then add this overlay file after that.
See here for details on this process: [[ROCKPro64 Device Tree Overlays on Mainline]]

The resulting <code>/boot/extlinux/extlinux.conf</code> file might look like below after adding this dtb file:
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb /dtbs/overlay/cpu-overclock.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 zfs=zroot rw rootwait audit=0 cpufreq.default_governor=schedutil

=== Getting wifi working ("new" wifi module) ===
ManjaroARM and ArchLinuxARM (and probably others) provide the NVRAM file needed to initialize the Wi-Fi module in the linux-firmware package, but it is listed under the generic name <code>brcmfmac43455-sdio.AW-CM256SM.txt</code>.
You can copy this file to the new name (that the driver looks for) with the following commands:
cd /usr/lib/firmware/brcm/
sudo cp brcmfmac43455-sdio.AW-CM256SM.txt brcmfmac43455-sdio.txt

Then, reboot and Wi-Fi should start working.
Details for this method are here: https://forum.pine64.org/showthread.php?tid=16635&pid=117061#pid117061
However, I noticed that on a 5GHz network with <code>wireless-regdb</code> installed and the regulatory domain set correctly (to 'US' for me), the adapter was almost unusable. Speeds were usually 0 bits per second. Sometimes a few packets would get through every few seconds, but that was it. On a 2.4GHz network, this was not an issue. This "can" be resolved by setting the regulator domain to 'GB' or 'CN', but this doesn't seem like a great solution. Instead, I tried various other <code>brcmfmac43455-sdio.txt</code> files found online. Some worked better than others. I combined parts of various files and found that applying the patch below to the default <code>brcmfmac43455-sdio.AW-CM256SM.txt</code> file fixed the issue. I was able to get about 140Mbps up and down with this patch (with the regulatory domain set correctly to 'US').

--- brcmfmac43455-sdio.AW-CM256SM.txt 2023-04-27 19:16:47.000000000 -0500
+++ brcmfmac43455-sdio.txt 2023-05-21 11:42:22.058517093 -0500
@@ -21,19 +21,18 @@
ltecxpadnum=0x0504
macaddr=00:90:4c:c5:12:38
manfid=0x2d0
-maxp2ga0=64
-maxp5ga0=80,82,76,77
-mcsbw202gpo=0x99355533
-mcsbw205ghpo=0x99855000
-mcsbw205glpo=0x99755000
-mcsbw205gmpo=0x9df55000
-mcsbw405ghpo=0xd9755000
-mcsbw405glpo=0xb8555000
-mcsbw405gmpo=0xed955000
-mcsbw805ghpo=0xd9555000
-mcsbw805glpo=0xc8555000
-mcsbw805gmpo=0xe9555000
-muxenab=0x10
+maxp2ga0=70
+maxp5ga0=73,74,73,73
+mcsbw202gpo=0x99333322
+mcsbw205ghpo=0x8a875444
+mcsbw205glpo=0x8a875444
+mcsbw205gmpo=0x8a875444
+mcsbw405ghpo=0xda844333
+mcsbw405glpo=0xda844333
+mcsbw405gmpo=0xdb844333
+mcsbw805ghpo=0xda555444
+mcsbw805glpo=0xdb555444
+mcsbw805gmpo=0xda555444
nocrc=1
ofdmlrbw202gpo=0x0033
pa2ga0=-112,6296,-662

To use this patch, copy it off into a file and use the <code>patch</code> command.
However, it might be easier to apply the patch by hand.
To do this, open the file <code>/usr/lib/firmware/brcm/brcmfmac43455-sdio.txt</code> (after completing the copy step above), delete the line with <code>maxp2ga0=64</code> through the line with <code>muxenab=0x10</code>.
Then add the following in its place:
maxp2ga0=70
maxp5ga0=73,74,73,73
mcsbw202gpo=0x99333322
mcsbw205ghpo=0x8a875444
mcsbw205glpo=0x8a875444
mcsbw205gmpo=0x8a875444
mcsbw405ghpo=0xda844333
mcsbw405glpo=0xda844333
mcsbw405gmpo=0xdb844333
mcsbw805ghpo=0xda555444
mcsbw805glpo=0xdb555444
mcsbw805gmpo=0xda555444

Reboot and the Wi-Fi (at least for 5GHz networks) should work well. I was unable to determine what these fields do, so I am not sure what impact this has on the Wi-Fi module or your ability to operate it legally in your country. From what I can tell (and I haven't looked into the process in too much depth), it seems that this file is passed directly to the hardware, where it is interpreted by the Wi-Fi module itself, but I am not sure on this. However, given that this file is simply a combination of other existing files for similar hardware, I would think that it should be fine.
I ended up pulling lines only from the file here: https://github.com/reMarkable/brcmfmac-firmware/blob/master/brcmfmac43455-sdio.txt.
This code comes with the following license (which I will not replicate here because it will fill this wiki with text - instead I have provided a link to its source): https://github.com/reMarkable/brcmfmac-firmware/blob/master/LICENCE.
I believe this license allows me to take these lines from one of the config files and provide them here in patch format.

=== Stabilizing the system (underclocking the RAM) ===
WIP

[[Category:ROCKPro64]] [[Category:Rockchip RK3399]]

ROCKPro64

2023-05-28T23:41:55Z

I3master: Added a disclaimer.

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful Single Board Computer released by PINE64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a Mali T-860 Quad-Core GPU. The key features include a PCIe x4 open ended slot, the use of LPDDR4 RAM, and industry standard heatsink mounting holes.

The ROCKPro64 is equipped with 2GB or 4GB LPDDR4 system memory, and 128Mb SPI boot Flash. There is also an optional eMMC module (up to 128GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 type C Host with DP 1.2, 1x USB 3.0 type A Host, 2x USB 2.0 Host, Gigabit Ethernet, PI-2 GPIO Bus, MiPi DSI interface, eDP interface, touch Panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different Operating Systems (OS) are freely available from the open source community, such as Android, Linux (Ubuntu, Debian, Arch), and BSD.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* 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
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* 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 Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 1 USB3.0 Host port
* 1 USB type C OTG port with DP output
* 2 USB2.0 Dedicated Host ports

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO Header
* PCIe 2.1 (4 full-duplex lanes with 20Gbps) x4 open ended port

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7″ LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
|
| For the "new" ROCKPro64 WIFI module: Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See [[#Getting wifi working ("new" wifi module)]] for the file contents and details.
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. After testing for a few hours, on Manjaro ARM (kernel 6.2.5), there haven't been stability issues found (WiFi stayed connected). On a 5GHz network (802.11AC), it was tested to be possible to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is near impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| https://pine64.com/?product=rockpro64-playbox-enclosure
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://store.pine64.org/?product=rockpro64-heatsink
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCIe 2.1
|
|
|
|
|
|
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| https://store.pine64.org/?product=rtc-backup-battery-cr-battery
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: +12V @3A/5A with 5.5mm/2.1mm Type M Barrel type DC connector
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

* [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
* [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
* [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
* [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]

* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]

* [[ROCKPro64 Device Tree Overlays on Mainline]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NASCase|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A Quartz64-A mounted in an ITX case using 3D printed brackets]]

Allows mounting a ROCKPro64-A or Quartz64-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in your log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

Log in to your ROCKPro64, and run the following:

sudo -i
echo governor_simpleondemand >> /etc/initramfs-tools/modules && update-initramfs -u -k $(uname -r)
exit

Then, reboot.

== Hardware "Hacking" ==

=== Enabling PCIe 2.0 ===
By default, the RockPro64 runs the PCIe slot at gen 1 speeds because there might be stability issues with gen 2 speeds. The port can be switched back to gen 2 speeds by adding the following device tree overlay.

1. Copy and paste the device tree overlay file below into a new file (you could name it <code>pcie-2.0.dts</code>):
// Pulled from: https://forum.armbian.com/topic/23574-howto-enable-pcie-gen2-to-get-max-speed-of-nvme-rockpi-4b/
/dts-v1/;
/plugin/;

&pcie0 {
max-link-speed = <0x03>;
};

2. Compile the device tree into a binary file. Note that you will need <code>dtc</code> installed.
dtc -I dts -O dtb -@ pcie-2.0.dts -o pcie-2.0.dto

4. Copy or move the device tree from the current directory into the boot partition (in this case into the <code>/boot/dtbs/overlay/</code> folder). If you haven't yet created the <code>/boot/dtbs/overlay/</code> folder, then create it with <code>sudo mkdir /boot/dtbs/overlay/</code>
sudo cp pcie-2.0.dto /boot/dtbs/overlay/

5. Add the device compiled tree overlay file to the list of files u-boot needs to load. If you are using ManjaroARM (or ArchLinuxARM with a <code>extlinux.conf</code> file), then add the following line to the file <code>/boot/extlinux/extlinux.conf</code>:
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb

If you already have an <code>FDTOVERLAYS</code> line, then add a space at the end of the current line, then add this overlay file after that.
See here for details on this process: [[ROCKPro64 Device Tree Overlays on Mainline]]

The resulting <code>/boot/extlinux/extlinux.conf</code> file might look like below after adding this dtb file:
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb /dtbs/overlay/cpu-overclock.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 zfs=zroot rw rootwait audit=0 cpufreq.default_governor=schedutil

=== Overclocking (and undervolting) ===
The RK3399 can be overclocked. See here for details: [[Overclocking#RK3399-based devices]].
By overclocking, you do risk damaging your hardware, however, it is possible to achieve small, but measurable improvements in performance with an overclock. The overclock can be applied with a device tree overlay file.
Below is an example device tree overlay for CPU overclocking on the RockPro64. It may or may not work well on your device, but I found that these speeds were stable for me.
The example below bumps the little cores up to 1.608GHz from 1.416GHz and bumps the big cores up to 2.088GHz from 1.8GHz.

1. Copy and paste the device tree overlay file below into a new file (you could name it <code>cpu-overclock.dts</code>):
// Pulled from: https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi
/dts-v1/;
/plugin/;

&cluster0_opp {
opp00 {
opp-hz = /bits/ 64 <408000000>;
opp-microvolt = <800000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <825000>;
};
opp02 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <850000>;
};
opp03 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <900000>;
};
opp04 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <975000>;
};
opp05 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <1100000>;
};
opp06 {
opp-hz = /bits/ 64 <1512000000>;
opp-microvolt = <1150000>;
};
opp07 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1200000>;
};
};
&cluster1_opp {
opp00 {
opp-hz = /bits/ 64 <408000000>;
opp-microvolt = <800000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <800000>;
};
opp02 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <825000>;
};
opp03 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <850000>;
};
opp04 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <900000>;
};
opp05 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <975000>;
};
opp06 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1050000>;
};
opp07 {
opp-hz = /bits/ 64 <1800000000>;
opp-microvolt = <1150000>;
};
opp08 {
opp-hz = /bits/ 64 <2016000000>;
opp-microvolt = <1250000>;
};
opp09 {
opp-hz = /bits/ 64 <2088000000>;
opp-microvolt = <1250000>;
};
};

2. Compile the device tree into a binary file. Note that you will need <code>dtc</code> installed.
dtc -I dts -O dtb -@ cpu-overclock.dts -o cpu-overclock.dto

4. Copy or move the device tree from the current directory into the boot partition (in this case into the <code>/boot/dtbs/overlay/</code> folder). If you haven't yet created the <code>/boot/dtbs/overlay/</code> folder, then create it with <code>sudo mkdir /boot/dtbs/overlay/</code>
sudo cp cpu-overclock.dto /boot/dtbs/overlay/

5. Add the device compiled tree overlay file to the list of files u-boot needs to load. If you are using ManjaroARM (or ArchLinuxARM with a <code>extlinux.conf</code> file), then add the following line to the file <code>/boot/extlinux/extlinux.conf</code>:
FDTOVERLAYS /dtbs/overlay/cpu-overclock.dtb

If you already have an <code>FDTOVERLAYS</code> line, then add a space at the end of the current line, then add this overlay file after that.
See here for details on this process: [[ROCKPro64 Device Tree Overlays on Mainline]]

The resulting <code>/boot/extlinux/extlinux.conf</code> file might look like below after adding this dtb file:
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb /dtbs/overlay/cpu-overclock.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 zfs=zroot rw rootwait audit=0 cpufreq.default_governor=schedutil

=== Getting wifi working ("new" wifi module) ===
ManjaroARM and ArchLinuxARM (and probably others) provide the NVRAM file needed to initialize the Wi-Fi module, but it is listed under the generic name <code>brcmfmac43455-sdio.AW-CM256SM.txt</code>.
You can copy this file to the new name (that the driver looks for) with the following commands:
cd /usr/lib/firmware/brcm/
sudo cp brcmfmac43455-sdio.AW-CM256SM.txt brcmfmac43455-sdio.txt

Then, reboot and Wi-Fi should start working.
Details for this method are here: https://forum.pine64.org/showthread.php?tid=16635&pid=117061#pid117061
However, I noticed that on a 5GHz network with <code>wireless-regdb</code> installed and the regulatory domain set correctly (to 'US'), the adapter was almost unusable. Speeds were usually 0 bits per second. Sometimes a few packets would get through every few seconds, but that was it. On a 2.4GHz network, this was not an issue. This "can" be resolved by setting the regulator domain to 'GB' or 'CN', but this doesn't seem like a great solution. Instead, I tried various other <code>brcmfmac43455-sdio.txt</code> files found online. Some worked better than others. I combined parts of various files and found that applying the patch below to the default <code>brcmfmac43455-sdio.AW-CM256SM.txt</code> file fixed the issue. I was able to get about 140Mbps up and down with this patch (with the regulatory domain set correctly to 'US').

--- brcmfmac43455-sdio.AW-CM256SM.txt 2023-04-27 19:16:47.000000000 -0500
+++ brcmfmac43455-sdio.txt 2023-05-21 11:42:22.058517093 -0500
@@ -21,19 +21,18 @@
ltecxpadnum=0x0504
macaddr=00:90:4c:c5:12:38
manfid=0x2d0
-maxp2ga0=64
-maxp5ga0=80,82,76,77
-mcsbw202gpo=0x99355533
-mcsbw205ghpo=0x99855000
-mcsbw205glpo=0x99755000
-mcsbw205gmpo=0x9df55000
-mcsbw405ghpo=0xd9755000
-mcsbw405glpo=0xb8555000
-mcsbw405gmpo=0xed955000
-mcsbw805ghpo=0xd9555000
-mcsbw805glpo=0xc8555000
-mcsbw805gmpo=0xe9555000
-muxenab=0x10
+maxp2ga0=70
+maxp5ga0=73,74,73,73
+mcsbw202gpo=0x99333322
+mcsbw205ghpo=0x8a875444
+mcsbw205glpo=0x8a875444
+mcsbw205gmpo=0x8a875444
+mcsbw405ghpo=0xda844333
+mcsbw405glpo=0xda844333
+mcsbw405gmpo=0xdb844333
+mcsbw805ghpo=0xda555444
+mcsbw805glpo=0xdb555444
+mcsbw805gmpo=0xda555444
nocrc=1
ofdmlrbw202gpo=0x0033
pa2ga0=-112,6296,-662

To use this patch, copy it off into a file and use the <code>patch</code> command.
However, it might be easier to apply the patch by-hand.
To do this, delete the line with `maxp2ga0=64` through the line with `muxenab=0x10`.
Then add the following in its place:
maxp2ga0=70
maxp5ga0=73,74,73,73
mcsbw202gpo=0x99333322
mcsbw205ghpo=0x8a875444
mcsbw205glpo=0x8a875444
mcsbw205gmpo=0x8a875444
mcsbw405ghpo=0xda844333
mcsbw405glpo=0xda844333
mcsbw405gmpo=0xdb844333
mcsbw805ghpo=0xda555444
mcsbw805glpo=0xdb555444
mcsbw805gmpo=0xda555444

Reboot and the Wi-Fi (at least for 5GHz networks) should work well. I was unable to determine what these fields do, so I am not sure what impact this has on the Wi-Fi module or your ability to operate it legally in your country. From what I can tell (and I haven't looked into the process in too much depth), it seems that this file is passed directly to the hardware, where it is interpreted by the Wi-Fi module itself, but I am not sure on this. However, given that this file is simply a combination of other existing files for similar hardware, I would think that it should be fine.
The additions to the existing, distribution-provided, file where pulled from here: https://github.com/reMarkable/brcmfmac-firmware/blob/master/brcmfmac43455-sdio.txt

=== Stabilizing the system (underclocking the RAM) ===
WIP

[[Category:ROCKPro64]] [[Category:Rockchip RK3399]]

ROCKPro64

2023-05-28T23:04:27Z

I3master: Added WIFI tips.

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful Single Board Computer released by PINE64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a Mali T-860 Quad-Core GPU. The key features include a PCIe x4 open ended slot, the use of LPDDR4 RAM, and industry standard heatsink mounting holes.

The ROCKPro64 is equipped with 2GB or 4GB LPDDR4 system memory, and 128Mb SPI boot Flash. There is also an optional eMMC module (up to 128GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 type C Host with DP 1.2, 1x USB 3.0 type A Host, 2x USB 2.0 Host, Gigabit Ethernet, PI-2 GPIO Bus, MiPi DSI interface, eDP interface, touch Panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different Operating Systems (OS) are freely available from the open source community, such as Android, Linux (Ubuntu, Debian, Arch), and BSD.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* 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
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* 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 Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 1 USB3.0 Host port
* 1 USB type C OTG port with DP output
* 2 USB2.0 Dedicated Host ports

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO Header
* PCIe 2.1 (4 full-duplex lanes with 20Gbps) x4 open ended port

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7″ LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
|
| For the "new" ROCKPro64 WIFI module: Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See [[#Getting wifi working ("new" wifi module)]] for the file contents and details.
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. After testing for a few hours, on Manjaro ARM (kernel 6.2.5), there haven't been stability issues found (WiFi stayed connected). On a 5GHz network (802.11AC), it was tested to be possible to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is near impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| https://pine64.com/?product=rockpro64-playbox-enclosure
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://store.pine64.org/?product=rockpro64-heatsink
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCIe 2.1
|
|
|
|
|
|
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| https://store.pine64.org/?product=rtc-backup-battery-cr-battery
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: +12V @3A/5A with 5.5mm/2.1mm Type M Barrel type DC connector
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

* [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
* [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
* [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
* [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]

* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]

* [[ROCKPro64 Device Tree Overlays on Mainline]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NASCase|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A Quartz64-A mounted in an ITX case using 3D printed brackets]]

Allows mounting a ROCKPro64-A or Quartz64-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in your log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

Log in to your ROCKPro64, and run the following:

sudo -i
echo governor_simpleondemand >> /etc/initramfs-tools/modules && update-initramfs -u -k $(uname -r)
exit

Then, reboot.

== Hardware "Hacking" ==

=== Enabling PCIe 2.0 ===
By default, the RockPro64 runs the PCIe slot at gen 1 speeds because there might be stability issues with gen 2 speeds. The port can be switched back to gen 2 speeds by adding the following device tree overlay.

1. Copy and paste the device tree overlay file below into a new file (you could name it <code>pcie-2.0.dts</code>):
// Pulled from: https://forum.armbian.com/topic/23574-howto-enable-pcie-gen2-to-get-max-speed-of-nvme-rockpi-4b/
/dts-v1/;
/plugin/;

&pcie0 {
max-link-speed = <0x03>;
};

2. Compile the device tree into a binary file. Note that you will need <code>dtc</code> installed.
dtc -I dts -O dtb -@ pcie-2.0.dts -o pcie-2.0.dto

4. Copy or move the device tree from the current directory into the boot partition (in this case into the <code>/boot/dtbs/overlay/</code> folder). If you haven't yet created the <code>/boot/dtbs/overlay/</code> folder, then create it with <code>sudo mkdir /boot/dtbs/overlay/</code>
sudo cp pcie-2.0.dto /boot/dtbs/overlay/

5. Add the device compiled tree overlay file to the list of files u-boot needs to load. If you are using ManjaroARM (or ArchLinuxARM with a <code>extlinux.conf</code> file), then add the following line to the file <code>/boot/extlinux/extlinux.conf</code>:
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb

If you already have an <code>FDTOVERLAYS</code> line, then add a space at the end of the current line, then add this overlay file after that.
See here for details on this process: [[ROCKPro64 Device Tree Overlays on Mainline]]

The resulting <code>/boot/extlinux/extlinux.conf</code> file might look like below after adding this dtb file:
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb /dtbs/overlay/cpu-overclock.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 zfs=zroot rw rootwait audit=0 cpufreq.default_governor=schedutil

=== Overclocking (and undervolting) ===
The RK3399 can be overclocked. See here for details: [[Overclocking#RK3399-based devices]].
By overclocking, you do risk damaging your hardware, however, it is possible to achieve small, but measurable improvements in performance with an overclock. The overclock can be applied with a device tree overlay file.
Below is an example device tree overlay for CPU overclocking on the RockPro64. It may or may not work well on your device, but I found that these speeds were stable for me.
The example below bumps the little cores up to 1.608GHz from 1.416GHz and bumps the big cores up to 2.088GHz from 1.8GHz.

1. Copy and paste the device tree overlay file below into a new file (you could name it <code>cpu-overclock.dts</code>):
// Pulled from: https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi
/dts-v1/;
/plugin/;

&cluster0_opp {
opp00 {
opp-hz = /bits/ 64 <408000000>;
opp-microvolt = <800000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <825000>;
};
opp02 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <850000>;
};
opp03 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <900000>;
};
opp04 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <975000>;
};
opp05 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <1100000>;
};
opp06 {
opp-hz = /bits/ 64 <1512000000>;
opp-microvolt = <1150000>;
};
opp07 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1200000>;
};
};
&cluster1_opp {
opp00 {
opp-hz = /bits/ 64 <408000000>;
opp-microvolt = <800000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <800000>;
};
opp02 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <825000>;
};
opp03 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <850000>;
};
opp04 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <900000>;
};
opp05 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <975000>;
};
opp06 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1050000>;
};
opp07 {
opp-hz = /bits/ 64 <1800000000>;
opp-microvolt = <1150000>;
};
opp08 {
opp-hz = /bits/ 64 <2016000000>;
opp-microvolt = <1250000>;
};
opp09 {
opp-hz = /bits/ 64 <2088000000>;
opp-microvolt = <1250000>;
};
};

2. Compile the device tree into a binary file. Note that you will need <code>dtc</code> installed.
dtc -I dts -O dtb -@ cpu-overclock.dts -o cpu-overclock.dto

4. Copy or move the device tree from the current directory into the boot partition (in this case into the <code>/boot/dtbs/overlay/</code> folder). If you haven't yet created the <code>/boot/dtbs/overlay/</code> folder, then create it with <code>sudo mkdir /boot/dtbs/overlay/</code>
sudo cp cpu-overclock.dto /boot/dtbs/overlay/

5. Add the device compiled tree overlay file to the list of files u-boot needs to load. If you are using ManjaroARM (or ArchLinuxARM with a <code>extlinux.conf</code> file), then add the following line to the file <code>/boot/extlinux/extlinux.conf</code>:
FDTOVERLAYS /dtbs/overlay/cpu-overclock.dtb

If you already have an <code>FDTOVERLAYS</code> line, then add a space at the end of the current line, then add this overlay file after that.
See here for details on this process: [[ROCKPro64 Device Tree Overlays on Mainline]]

The resulting <code>/boot/extlinux/extlinux.conf</code> file might look like below after adding this dtb file:
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb /dtbs/overlay/cpu-overclock.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 zfs=zroot rw rootwait audit=0 cpufreq.default_governor=schedutil

=== Getting wifi working ("new" wifi module) ===
ManjaroARM and ArchLinuxARM (and probably others) provide the NVRAM file needed to initialize the Wi-Fi module, but it is listed under the generic name <code>brcmfmac43455-sdio.AW-CM256SM.txt</code>.
You can copy this file to the new name (that the driver looks for) with the following command:
sudo cp brcmfmac43455-sdio.AW-CM256SM.txt brcmfmac43455-sdio.txt

Then, reboot and Wi-Fi should start working.
Details for this method are here: https://forum.pine64.org/showthread.php?tid=16635&pid=117061#pid117061
However, I noticed that on a 5GHz network with <code>wireless-regdb</code> installed and the regulatory domain set correctly (to 'US'), the adapter was almost unusable. Speeds were usually 0 bits per second. Sometimes a few packets would get through every few seconds, but that was it. On a 2.4GHz network, this was not an issue. This "can" be resolved by setting the regulator domain to 'GB' or 'CN', but this doesn't seem like a great solution. Instead, I tried various other <code>brcmfmac43455-sdio.txt</code> files found online. Some worked better than others. I combined parts of various files and found that applying the patch below to the default <code>brcmfmac43455-sdio.AW-CM256SM.txt</code> file fixed the issue. I was able to get about 140Mbps up and down with this patch (with the regulatory domain set correctly to 'US').

--- brcmfmac43455-sdio.AW-CM256SM.txt 2023-04-27 19:16:47.000000000 -0500
+++ brcmfmac43455-sdio.txt 2023-05-21 11:42:22.058517093 -0500
@@ -21,19 +21,18 @@
ltecxpadnum=0x0504
macaddr=00:90:4c:c5:12:38
manfid=0x2d0
-maxp2ga0=64
-maxp5ga0=80,82,76,77
-mcsbw202gpo=0x99355533
-mcsbw205ghpo=0x99855000
-mcsbw205glpo=0x99755000
-mcsbw205gmpo=0x9df55000
-mcsbw405ghpo=0xd9755000
-mcsbw405glpo=0xb8555000
-mcsbw405gmpo=0xed955000
-mcsbw805ghpo=0xd9555000
-mcsbw805glpo=0xc8555000
-mcsbw805gmpo=0xe9555000
-muxenab=0x10
+maxp2ga0=70
+maxp5ga0=73,74,73,73
+mcsbw202gpo=0x99333322
+mcsbw205ghpo=0x8a875444
+mcsbw205glpo=0x8a875444
+mcsbw205gmpo=0x8a875444
+mcsbw405ghpo=0xda844333
+mcsbw405glpo=0xda844333
+mcsbw405gmpo=0xdb844333
+mcsbw805ghpo=0xda555444
+mcsbw805glpo=0xdb555444
+mcsbw805gmpo=0xda555444
nocrc=1
ofdmlrbw202gpo=0x0033
pa2ga0=-112,6296,-662

To use this patch, copy it off into a file and use the <code>patch</code> command.
However, it might be easier to apply the patch by-hand.
To do this, delete the line with `maxp2ga0=64` through the line with `muxenab=0x10`.
Then add the following in its place:
maxp2ga0=70
maxp5ga0=73,74,73,73
mcsbw202gpo=0x99333322
mcsbw205ghpo=0x8a875444
mcsbw205glpo=0x8a875444
mcsbw205gmpo=0x8a875444
mcsbw405ghpo=0xda844333
mcsbw405glpo=0xda844333
mcsbw405gmpo=0xdb844333
mcsbw805ghpo=0xda555444
mcsbw805glpo=0xdb555444
mcsbw805gmpo=0xda555444

Reboot and the Wi-Fi (at least for 5GHz networks) should work "well".

=== Stabilizing the system (underclocking the RAM) ===
WIP

[[Category:ROCKPro64]] [[Category:Rockchip RK3399]]

ROCKPro64

2023-05-28T22:45:20Z

I3master: Updated overclocking to include an overview.

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful Single Board Computer released by PINE64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a Mali T-860 Quad-Core GPU. The key features include a PCIe x4 open ended slot, the use of LPDDR4 RAM, and industry standard heatsink mounting holes.

The ROCKPro64 is equipped with 2GB or 4GB LPDDR4 system memory, and 128Mb SPI boot Flash. There is also an optional eMMC module (up to 128GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 type C Host with DP 1.2, 1x USB 3.0 type A Host, 2x USB 2.0 Host, Gigabit Ethernet, PI-2 GPIO Bus, MiPi DSI interface, eDP interface, touch Panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different Operating Systems (OS) are freely available from the open source community, such as Android, Linux (Ubuntu, Debian, Arch), and BSD.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* 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
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* 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 Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 1 USB3.0 Host port
* 1 USB type C OTG port with DP output
* 2 USB2.0 Dedicated Host ports

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO Header
* PCIe 2.1 (4 full-duplex lanes with 20Gbps) x4 open ended port

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7″ LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
|
| For the "new" ROCKPro64 WIFI module: Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See here for the file contents and details: https://askubuntu.com/a/1211986. Some distros provide this file, but it is listed under the generic name "brcmfmac43455-sdio.AW-CM256SM.txt". If this file exists, you can create a symbolic link to it named "brcmfmac43455-sdio.txt" instead of downloading the firmware file listed above. This can be done with the following command <code>sudo ln -s /usr/lib/firmware/brcm/brcmfmac43455-sdio.AW-CM256SM.txt /usr/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. Then, reboot and WIFI should start working. Details for this method are here: https://forum.pine64.org/showthread.php?tid=16635&pid=117061#pid117061
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. After testing for a few hours, on Manjaro ARM (kernel 6.2.5), there haven't been stability issues found (WiFi stayed connected). On a 5GHz network (802.11AC), it was tested to be possible to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is near impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| https://pine64.com/?product=rockpro64-playbox-enclosure
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://store.pine64.org/?product=rockpro64-heatsink
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCIe 2.1
|
|
|
|
|
|
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| https://store.pine64.org/?product=rtc-backup-battery-cr-battery
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: +12V @3A/5A with 5.5mm/2.1mm Type M Barrel type DC connector
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

* [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
* [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
* [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
* [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]

* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]

* [[ROCKPro64 Device Tree Overlays on Mainline]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NASCase|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A Quartz64-A mounted in an ITX case using 3D printed brackets]]

Allows mounting a ROCKPro64-A or Quartz64-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in your log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

Log in to your ROCKPro64, and run the following:

sudo -i
echo governor_simpleondemand >> /etc/initramfs-tools/modules && update-initramfs -u -k $(uname -r)
exit

Then, reboot.

== Hardware "Hacking" ==

=== Enabling PCIe 2.0 ===
By default, the RockPro64 runs the PCIe slot at gen 1 speeds because there might be stability issues with gen 2 speeds. The port can be switched back to gen 2 speeds by adding the following device tree overlay.

1. Copy and paste the device tree overlay file below into a new file (you could name it <code>pcie-2.0.dts</code>):
// Pulled from: https://forum.armbian.com/topic/23574-howto-enable-pcie-gen2-to-get-max-speed-of-nvme-rockpi-4b/
/dts-v1/;
/plugin/;

&pcie0 {
max-link-speed = <0x03>;
};

2. Compile the device tree into a binary file. Note that you will need <code>dtc</code> installed.
dtc -I dts -O dtb -@ pcie-2.0.dts -o pcie-2.0.dto

4. Copy or move the device tree from the current directory into the boot partition (in this case into the <code>/boot/dtbs/overlay/</code> folder). If you haven't yet created the <code>/boot/dtbs/overlay/</code> folder, then create it with <code>sudo mkdir /boot/dtbs/overlay/</code>
sudo cp pcie-2.0.dto /boot/dtbs/overlay/

5. Add the device compiled tree overlay file to the list of files u-boot needs to load. If you are using ManjaroARM (or ArchLinuxARM with a <code>extlinux.conf</code> file), then add the following line to the file <code>/boot/extlinux/extlinux.conf</code>:
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb

If you already have an <code>FDTOVERLAYS</code> line, then add a space at the end of the current line, then add this overlay file after that.
See here for details on this process: [[ROCKPro64 Device Tree Overlays on Mainline]]

The resulting <code>/boot/extlinux/extlinux.conf</code> file might look like below after adding this dtb file:
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb /dtbs/overlay/cpu-overclock.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 zfs=zroot rw rootwait audit=0 cpufreq.default_governor=schedutil

=== Overclocking (and undervolting) ===
The RK3399 can be overclocked. See here for details: [[Overclocking#RK3399-based devices]].
By overclocking, you do risk damaging your hardware, however, it is possible to achieve small, but measurable improvements in performance with an overclock. The overclock can be applied with a device tree overlay file.
Below is an example device tree overlay for CPU overclocking on the RockPro64. It may or may not work well on your device, but I found that these speeds were stable for me.
The example below bumps the little cores up to 1.608GHz from 1.416GHz and bumps the big cores up to 2.088GHz from 1.8GHz.

1. Copy and paste the device tree overlay file below into a new file (you could name it <code>cpu-overclock.dts</code>):
// Pulled from: https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi
/dts-v1/;
/plugin/;

&cluster0_opp {
opp00 {
opp-hz = /bits/ 64 <408000000>;
opp-microvolt = <800000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <825000>;
};
opp02 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <850000>;
};
opp03 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <900000>;
};
opp04 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <975000>;
};
opp05 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <1100000>;
};
opp06 {
opp-hz = /bits/ 64 <1512000000>;
opp-microvolt = <1150000>;
};
opp07 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1200000>;
};
};
&cluster1_opp {
opp00 {
opp-hz = /bits/ 64 <408000000>;
opp-microvolt = <800000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <800000>;
};
opp02 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <825000>;
};
opp03 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <850000>;
};
opp04 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <900000>;
};
opp05 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <975000>;
};
opp06 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1050000>;
};
opp07 {
opp-hz = /bits/ 64 <1800000000>;
opp-microvolt = <1150000>;
};
opp08 {
opp-hz = /bits/ 64 <2016000000>;
opp-microvolt = <1250000>;
};
opp09 {
opp-hz = /bits/ 64 <2088000000>;
opp-microvolt = <1250000>;
};
};

2. Compile the device tree into a binary file. Note that you will need <code>dtc</code> installed.
dtc -I dts -O dtb -@ cpu-overclock.dts -o cpu-overclock.dto

4. Copy or move the device tree from the current directory into the boot partition (in this case into the <code>/boot/dtbs/overlay/</code> folder). If you haven't yet created the <code>/boot/dtbs/overlay/</code> folder, then create it with <code>sudo mkdir /boot/dtbs/overlay/</code>
sudo cp cpu-overclock.dto /boot/dtbs/overlay/

5. Add the device compiled tree overlay file to the list of files u-boot needs to load. If you are using ManjaroARM (or ArchLinuxARM with a <code>extlinux.conf</code> file), then add the following line to the file <code>/boot/extlinux/extlinux.conf</code>:
FDTOVERLAYS /dtbs/overlay/cpu-overclock.dtb

If you already have an <code>FDTOVERLAYS</code> line, then add a space at the end of the current line, then add this overlay file after that.
See here for details on this process: [[ROCKPro64 Device Tree Overlays on Mainline]]

The resulting <code>/boot/extlinux/extlinux.conf</code> file might look like below after adding this dtb file:
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb /dtbs/overlay/cpu-overclock.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 zfs=zroot rw rootwait audit=0 cpufreq.default_governor=schedutil

=== Improving WIFI (on 5GHz networks) ===
WIP

=== Stabilizing the system (underclocking the RAM) ===
WIP

[[Category:ROCKPro64]] [[Category:Rockchip RK3399]]

ROCKPro64

2023-05-28T22:39:44Z

I3master: Added a cpu overclocking template.

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful Single Board Computer released by PINE64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a Mali T-860 Quad-Core GPU. The key features include a PCIe x4 open ended slot, the use of LPDDR4 RAM, and industry standard heatsink mounting holes.

The ROCKPro64 is equipped with 2GB or 4GB LPDDR4 system memory, and 128Mb SPI boot Flash. There is also an optional eMMC module (up to 128GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 type C Host with DP 1.2, 1x USB 3.0 type A Host, 2x USB 2.0 Host, Gigabit Ethernet, PI-2 GPIO Bus, MiPi DSI interface, eDP interface, touch Panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different Operating Systems (OS) are freely available from the open source community, such as Android, Linux (Ubuntu, Debian, Arch), and BSD.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* 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
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* 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 Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 1 USB3.0 Host port
* 1 USB type C OTG port with DP output
* 2 USB2.0 Dedicated Host ports

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO Header
* PCIe 2.1 (4 full-duplex lanes with 20Gbps) x4 open ended port

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7″ LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
|
| For the "new" ROCKPro64 WIFI module: Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See here for the file contents and details: https://askubuntu.com/a/1211986. Some distros provide this file, but it is listed under the generic name "brcmfmac43455-sdio.AW-CM256SM.txt". If this file exists, you can create a symbolic link to it named "brcmfmac43455-sdio.txt" instead of downloading the firmware file listed above. This can be done with the following command <code>sudo ln -s /usr/lib/firmware/brcm/brcmfmac43455-sdio.AW-CM256SM.txt /usr/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. Then, reboot and WIFI should start working. Details for this method are here: https://forum.pine64.org/showthread.php?tid=16635&pid=117061#pid117061
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. After testing for a few hours, on Manjaro ARM (kernel 6.2.5), there haven't been stability issues found (WiFi stayed connected). On a 5GHz network (802.11AC), it was tested to be possible to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is near impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| https://pine64.com/?product=rockpro64-playbox-enclosure
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://store.pine64.org/?product=rockpro64-heatsink
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCIe 2.1
|
|
|
|
|
|
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| https://store.pine64.org/?product=rtc-backup-battery-cr-battery
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: +12V @3A/5A with 5.5mm/2.1mm Type M Barrel type DC connector
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

* [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
* [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
* [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
* [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]

* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]

* [[ROCKPro64 Device Tree Overlays on Mainline]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NASCase|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A Quartz64-A mounted in an ITX case using 3D printed brackets]]

Allows mounting a ROCKPro64-A or Quartz64-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in your log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

Log in to your ROCKPro64, and run the following:

sudo -i
echo governor_simpleondemand >> /etc/initramfs-tools/modules && update-initramfs -u -k $(uname -r)
exit

Then, reboot.

== Hardware "Hacking" ==

=== Enabling PCIe 2.0 ===
By default, the RockPro64 runs the PCIe slot at gen 1 speeds because there might be stability issues with gen 2 speeds. The port can be switched back to gen 2 speeds by adding the following device tree overlay.

1. Copy and paste the device tree overlay file below into a new file (you could name it <code>pcie-2.0.dts</code>):
// Pulled from: https://forum.armbian.com/topic/23574-howto-enable-pcie-gen2-to-get-max-speed-of-nvme-rockpi-4b/
/dts-v1/;
/plugin/;

&pcie0 {
max-link-speed = <0x03>;
};

2. Compile the device tree into a binary file. Note that you will need <code>dtc</code> installed.
dtc -I dts -O dtb -@ pcie-2.0.dts -o pcie-2.0.dto

4. Copy or move the device tree from the current directory into the boot partition (in this case into the <code>/boot/dtbs/overlay/</code> folder). If you haven't yet created the <code>/boot/dtbs/overlay/</code> folder, then create it with <code>sudo mkdir /boot/dtbs/overlay/</code>
sudo cp pcie-2.0.dto /boot/dtbs/overlay/

5. Add the device compiled tree overlay file to the list of files u-boot needs to load. If you are using ManjaroARM (or ArchLinuxARM with a <code>extlinux.conf</code> file), then add the following line to the file <code>/boot/extlinux/extlinux.conf</code>:
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb

If you already have an <code>FDTOVERLAYS</code> line, then add a space at the end of the current line, then add this overlay file after that.
See here for details on this process: [[ROCKPro64 Device Tree Overlays on Mainline]]

The resulting <code>/boot/extlinux/extlinux.conf</code> file might look like below after adding this dtb file:
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb /dtbs/overlay/cpu-overclock.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 zfs=zroot rw rootwait audit=0 cpufreq.default_governor=schedutil

=== Overclocking (and undervolting) ===
The RK3399 can be overclocked. See here for details: [[Overclocking#RK3399-based devices]].
By overclocking, you do risk damaging your hardware, however, it is possible to achieve small, but measurable improvements in performance with an overclock. The overclock can be applied with a device tree overlay file.
Below is an example device tree overlay for CPU overclocking on the RockPro64. It may or may not work well on your device, but I found that these speeds were stable for me.

1. Copy and paste the device tree overlay file below into a new file (you could name it <code>cpu-overclock.dts</code>):
// Pulled from: https://github.com/torvalds/linux/blob/master/arch/arm65/boot/dts/rockchip/rk3400-op2-opp.dtsi
/dts-v1/;
/plugin/;

&cluster0_opp {
opp00 {
opp-hz = /bits/ 64 <408000000>;
opp-microvolt = <800000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <825000>;
};
opp02 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <850000>;
};
opp03 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <900000>;
};
opp04 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <975000>;
};
opp05 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <1100000>;
};
opp06 {
opp-hz = /bits/ 64 <1512000000>;
opp-microvolt = <1150000>;
};
opp07 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1200000>;
};
};
&cluster1_opp {
opp00 {
opp-hz = /bits/ 64 <408000000>;
opp-microvolt = <800000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <800000>;
};
opp02 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <825000>;
};
opp03 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <850000>;
};
opp04 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <900000>;
};
opp05 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <975000>;
};
opp06 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1050000>;
};
opp07 {
opp-hz = /bits/ 64 <1800000000>;
opp-microvolt = <1150000>;
};
opp08 {
opp-hz = /bits/ 64 <2016000000>;
opp-microvolt = <1250000>;
};
opp09 {
opp-hz = /bits/ 64 <2088000000>;
opp-microvolt = <1250000>;
};
};

2. Compile the device tree into a binary file. Note that you will need <code>dtc</code> installed.
dtc -I dts -O dtb -@ cpu-overclock.dts -o cpu-overclock.dto

4. Copy or move the device tree from the current directory into the boot partition (in this case into the <code>/boot/dtbs/overlay/</code> folder). If you haven't yet created the <code>/boot/dtbs/overlay/</code> folder, then create it with <code>sudo mkdir /boot/dtbs/overlay/</code>
sudo cp cpu-overclock.dto /boot/dtbs/overlay/

5. Add the device compiled tree overlay file to the list of files u-boot needs to load. If you are using ManjaroARM (or ArchLinuxARM with a <code>extlinux.conf</code> file), then add the following line to the file <code>/boot/extlinux/extlinux.conf</code>:
FDTOVERLAYS /dtbs/overlay/cpu-overclock.dtb

If you already have an <code>FDTOVERLAYS</code> line, then add a space at the end of the current line, then add this overlay file after that.
See here for details on this process: [[ROCKPro64 Device Tree Overlays on Mainline]]

The resulting <code>/boot/extlinux/extlinux.conf</code> file might look like below after adding this dtb file:
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb /dtbs/overlay/cpu-overclock.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 zfs=zroot rw rootwait audit=0 cpufreq.default_governor=schedutil

=== Improving WIFI (on 5GHz networks) ===
WIP

=== Stabilizing the system (underclocking the RAM) ===
WIP

[[Category:ROCKPro64]] [[Category:Rockchip RK3399]]

ROCKPro64

2023-05-28T22:16:07Z

I3master: Added instructions on switching the PCIe port to gen 2 speeds.

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful Single Board Computer released by PINE64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a Mali T-860 Quad-Core GPU. The key features include a PCIe x4 open ended slot, the use of LPDDR4 RAM, and industry standard heatsink mounting holes.

The ROCKPro64 is equipped with 2GB or 4GB LPDDR4 system memory, and 128Mb SPI boot Flash. There is also an optional eMMC module (up to 128GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 type C Host with DP 1.2, 1x USB 3.0 type A Host, 2x USB 2.0 Host, Gigabit Ethernet, PI-2 GPIO Bus, MiPi DSI interface, eDP interface, touch Panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different Operating Systems (OS) are freely available from the open source community, such as Android, Linux (Ubuntu, Debian, Arch), and BSD.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* 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
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* 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 Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 1 USB3.0 Host port
* 1 USB type C OTG port with DP output
* 2 USB2.0 Dedicated Host ports

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO Header
* PCIe 2.1 (4 full-duplex lanes with 20Gbps) x4 open ended port

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7″ LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
|
| For the "new" ROCKPro64 WIFI module: Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See here for the file contents and details: https://askubuntu.com/a/1211986. Some distros provide this file, but it is listed under the generic name "brcmfmac43455-sdio.AW-CM256SM.txt". If this file exists, you can create a symbolic link to it named "brcmfmac43455-sdio.txt" instead of downloading the firmware file listed above. This can be done with the following command <code>sudo ln -s /usr/lib/firmware/brcm/brcmfmac43455-sdio.AW-CM256SM.txt /usr/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. Then, reboot and WIFI should start working. Details for this method are here: https://forum.pine64.org/showthread.php?tid=16635&pid=117061#pid117061
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. After testing for a few hours, on Manjaro ARM (kernel 6.2.5), there haven't been stability issues found (WiFi stayed connected). On a 5GHz network (802.11AC), it was tested to be possible to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is near impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| https://pine64.com/?product=rockpro64-playbox-enclosure
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://store.pine64.org/?product=rockpro64-heatsink
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCIe 2.1
|
|
|
|
|
|
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| https://store.pine64.org/?product=rtc-backup-battery-cr-battery
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: +12V @3A/5A with 5.5mm/2.1mm Type M Barrel type DC connector
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

* [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
* [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
* [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
* [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]

* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]

* [[ROCKPro64 Device Tree Overlays on Mainline]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NASCase|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A Quartz64-A mounted in an ITX case using 3D printed brackets]]

Allows mounting a ROCKPro64-A or Quartz64-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in your log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

Log in to your ROCKPro64, and run the following:

sudo -i
echo governor_simpleondemand >> /etc/initramfs-tools/modules && update-initramfs -u -k $(uname -r)
exit

Then, reboot.

== Hardware "Hacking" ==

=== Enabling PCIe 2.0 ===
By default, the RockPro64 runs the PCIe slot at gen 1 speeds because there might be stability issues with gen 2 speeds. The port can be switched back to gen 2 speeds by adding the following device tree overlay.

1. Copy and paste the device tree overlay file below into a new file (you could name it <code>pcie-2.0.dts</code>):
// Pulled from: https://forum.armbian.com/topic/23574-howto-enable-pcie-gen2-to-get-max-speed-of-nvme-rockpi-4b/
/dts-v1/;
/plugin/;

&pcie0 {
max-link-speed = <0x03>;
};

2. Compile the device tree into a binary file. Note that you will need <code>dtc</code> installed.
dtc -I dts -O dtb -@ pcie-2.0.dts -o pcie-2.0.dto

4. Copy or move the device tree from the current directory into the boot partition (in this case into the <code>/boot/dtbs/overlay/</code> folder). If you haven't yet created the <code>/boot/dtbs/overlay/</code> folder, then create it with <code>sudo mkdir /boot/dtbs/overlay/</code>
sudo cp pcie-2.0.dto /boot/dtbs/overlay/

5. Add the device compiled tree overlay file to the list of files u-boot needs to load. If you are using ManjaroARM (or ArchLinuxARM with a <code>extlinux.conf</code> file), then add the following line to the file <code>/boot/extlinux/extlinux.conf</code>:
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb

If you already have an <code>FDTOVERLAYS</code> line, then add a space at the end of the current line, then add this overlay file after that.
See here for details on this process: [[ROCKPro64 Device Tree Overlays on Mainline]]

The resulting <code>/boot/extlinux/extlinux.conf</code> file might look like below after adding this dtb file:
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3399-rockpro64.dtb
FDTOVERLAYS /dtbs/overlay/pcie-2.0.dtb /dtbs/overlay/cpu-overclock.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 zfs=zroot rw rootwait audit=0 cpufreq.default_governor=schedutil

=== Overclocking (and undervolting) ===
WIP

=== Improving WIFI (on 5GHz networks) ===
WIP

=== Stabilizing the system (underclocking the RAM) ===
WIP

[[Category:ROCKPro64]] [[Category:Rockchip RK3399]]

ROCKPro64

2023-05-20T16:06:46Z

I3master: Added an easier method for getting WIFI working on the RockPro64.

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful Single Board Computer released by PINE64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a Mali T-860 Quad-Core GPU. The key features include a PCIe x4 open ended slot, the use of LPDDR4 RAM, and industry standard heatsink mounting holes.

The ROCKPro64 is equipped with 2GB or 4GB LPDDR4 system memory, and 128Mb SPI boot Flash. There is also an optional eMMC module (up to 128GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 type C Host with DP 1.2, 1x USB 3.0 type A Host, 2x USB 2.0 Host, Gigabit Ethernet, PI-2 GPIO Bus, MiPi DSI interface, eDP interface, touch Panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different Operating Systems (OS) are freely available from the open source community, such as Android, Linux (Ubuntu, Debian, Arch), and BSD.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* 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
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* 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 Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 1 USB3.0 Host port
* 1 USB type C OTG port with DP output
* 2 USB2.0 Dedicated Host ports

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO Header
* PCIe 2.1 (4 full-duplex lanes with 20Gbps) x4 open ended port

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7″ LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
|
| For the "new" ROCKPro64 WIFI module: Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See here for the file contents and details: https://askubuntu.com/a/1211986. Some distros provide this file, but it is listed under the generic name "brcmfmac43455-sdio.AW-CM256SM.txt". If this file exists, you can create a symbolic link to it named "brcmfmac43455-sdio.txt" instead of downloading the firmware file listed above. This can be done with the following command <code>sudo ln -s /usr/lib/firmware/brcm/brcmfmac43455-sdio.AW-CM256SM.txt /usr/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. Then, reboot and WIFI should start working. Details for this method are here: https://forum.pine64.org/showthread.php?tid=16635&pid=117061#pid117061
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. After testing for a few hours, on Manjaro ARM (kernel 6.2.5), there haven't been stability issues found (WiFi stayed connected). On a 5GHz network (802.11AC), it was tested to be possible to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is near impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| https://pine64.com/?product=rockpro64-playbox-enclosure
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://store.pine64.org/?product=rockpro64-heatsink
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCIe 2.1
|
|
|
|
|
|
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| https://store.pine64.org/?product=rtc-backup-battery-cr-battery
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: +12V @3A/5A with 5.5mm/2.1mm Type M Barrel type DC connector
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

* [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
* [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
* [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
* [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]

* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]

* [[ROCKPro64 Device Tree Overlays on Mainline]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NASCase|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A Quartz64-A mounted in an ITX case using 3D printed brackets]]

Allows mounting a ROCKPro64-A or Quartz64-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in your log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

Log in to your ROCKPro64, and run the following:

sudo -i
echo governor_simpleondemand >> /etc/initramfs-tools/modules && update-initramfs -u -k $(uname -r)
exit

Then, reboot.

[[Category:ROCKPro64]] [[Category:Rockchip RK3399]]

ROCKPro64

2023-04-15T17:11:46Z

I3master: Explained which wifi module was used in testing.

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful Single Board Computer released by PINE64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a Mali T-860 Quad-Core GPU. The key features include a PCIe x4 open ended slot, the use of LPDDR4 RAM, and industry standard heatsink mounting holes.

The ROCKPro64 is equipped with 2GB or 4GB LPDDR4 system memory, and 128Mb SPI boot Flash. There is also an optional eMMC module (up to 128GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 type C Host with DP 1.2, 1x USB 3.0 type A Host, 2x USB 2.0 Host, Gigabit Ethernet, PI-2 GPIO Bus, MiPi DSI interface, eDP interface, touch Panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different Operating Systems (OS) are freely available from the open source community, such as Android, Linux (Ubuntu, Debian, Arch), and BSD.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* 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
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* 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 Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 1 USB3.0 Host port
* 1 USB type C OTG port with DP output
* 2 USB2.0 Dedicated Host ports

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO Header
* PCIe 2.1 (4 full-duplex lanes with 20Gbps) x4 open ended port

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7″ LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
|
| For the "new" ROCKPro64 WIFI module: Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See here for the file contents and details: https://askubuntu.com/a/1211986.
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. After testing for a few hours, on Manjaro ARM (kernel 6.2.5), I did not experience any stability issues (WIFI stayed connected). On a 5GHz network (802.11AC), I was able to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is near impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| https://pine64.com/?product=rockpro64-playbox-enclosure
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://store.pine64.org/?product=rockpro64-heatsink
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCIe 2.1
|
|
|
|
|
|
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| https://store.pine64.org/?product=rtc-backup-battery-cr-battery
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: +12V @3A/5A with 5.5mm/2.1mm Type M Barrel type DC connector
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

* [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
* [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
* [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
* [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]

* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]

* [[ROCKPro64 Device Tree Overlays on Mainline]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NASCase|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A Quartz64-A mounted in an ITX case using 3D printed brackets]]

Allows mounting a ROCKPro64-A or Quartz64-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in your log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

Log in to your ROCKPro64, and run the following:

sudo -i
echo governor_simpleondemand >> /etc/initramfs-tools/modules && update-initramfs -u -k $(uname -r)
exit

Then, reboot.

[[Category:ROCKPro64]] [[Category:Rockchip RK3399]]

ROCKPro64

2023-04-15T16:53:01Z

I3master: Moved the wifi tip into the correct column.

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful Single Board Computer released by PINE64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a Mali T-860 Quad-Core GPU. The key features include a PCIe x4 open ended slot, the use of LPDDR4 RAM, and industry standard heatsink mounting holes.

The ROCKPro64 is equipped with 2GB or 4GB LPDDR4 system memory, and 128Mb SPI boot Flash. There is also an optional eMMC module (up to 128GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 type C Host with DP 1.2, 1x USB 3.0 type A Host, 2x USB 2.0 Host, Gigabit Ethernet, PI-2 GPIO Bus, MiPi DSI interface, eDP interface, touch Panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different Operating Systems (OS) are freely available from the open source community, such as Android, Linux (Ubuntu, Debian, Arch), and BSD.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* 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
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* 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 Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 1 USB3.0 Host port
* 1 USB type C OTG port with DP output
* 2 USB2.0 Dedicated Host ports

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO Header
* PCIe 2.1 (4 full-duplex lanes with 20Gbps) x4 open ended port

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7″ LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
|
| Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See here for the file contents and details: https://askubuntu.com/a/1211986.
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. After testing for a few hours, on Manjaro ARM (kernel 6.2.5), I did not experience any stability issues (WIFI stayed connected). On a 5GHz network (802.11AC), I was able to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is near impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| https://pine64.com/?product=rockpro64-playbox-enclosure
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://store.pine64.org/?product=rockpro64-heatsink
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCIe 2.1
|
|
|
|
|
|
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| https://store.pine64.org/?product=rtc-backup-battery-cr-battery
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: +12V @3A/5A with 5.5mm/2.1mm Type M Barrel type DC connector
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

* [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
* [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
* [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
* [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]

* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]

* [[ROCKPro64 Device Tree Overlays on Mainline]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NASCase|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A Quartz64-A mounted in an ITX case using 3D printed brackets]]

Allows mounting a ROCKPro64-A or Quartz64-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in your log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

Log in to your ROCKPro64, and run the following:

sudo -i
echo governor_simpleondemand >> /etc/initramfs-tools/modules && update-initramfs -u -k $(uname -r)
exit

Then, reboot.

[[Category:ROCKPro64]] [[Category:Rockchip RK3399]]

ROCKPro64

2023-04-15T16:50:28Z

I3master: Added instructions on getting wifi and HDMI audio working.

[[File:ROCKPro64v21FRONT.jpg|400px|thumb|right|The ROCKPro64]]

The '''ROCKPro64''' is the most powerful Single Board Computer released by PINE64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a Mali T-860 Quad-Core GPU. The key features include a PCIe x4 open ended slot, the use of LPDDR4 RAM, and industry standard heatsink mounting holes.

The ROCKPro64 is equipped with 2GB or 4GB LPDDR4 system memory, and 128Mb SPI boot Flash. There is also an optional eMMC module (up to 128GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 type C Host with DP 1.2, 1x USB 3.0 type A Host, 2x USB 2.0 Host, Gigabit Ethernet, PI-2 GPIO Bus, MiPi DSI interface, eDP interface, touch Panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different Operating Systems (OS) are freely available from the open source community, such as Android, Linux (Ubuntu, Debian, Arch), and BSD.

== Getting Started ==

The article [[ROCKPro64 Getting Started]] gives important information to get the board up and running.

== Software releases ==

In the [[ROCKPro64 Software Releases]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

Please see the [[Getting started]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== Board Layout ==
[[Image:ROCKPro64v21REAR.jpg|thumb|right|A hi-res picture of v2.1 rear.]]
[[Image:FLIR 20220619 125451 686.jpg|thumb|right|A thermal image of v2.1 front (upside-down).]]

[[File:ROCKPro64_annotated.jpg|500px|An annotated ROCKPro64]]

=== Main Chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

=== Switches ===

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): performs a reset.

The Recover button (28, SW900): used to enter maskrom mode.

=== Connectors, Sockets and Headers ===

{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C (often referred to as 'RJ45')
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

=== LEDs ===

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

=== Jumpers ===
They are used for boot device selection, as described in the following section.

==== Disable eMMC ====

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

==== Disable SPI (while booting) ====
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

== Hardware Compatibility ==

The hardware compatibility list can be found under [[ROCKPro64 Hardware compatibility]].

== Board Features ==

This section outlines the most important characteristics of the board and its components.

=== SoC and Memory Specification ===
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

==== CPU Architecture ====

* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* 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
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

==== GPU Architecture ====

* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

==== System Memory ====
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

=== Display ===

* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

=== Video ===

* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* 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 Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

=== Camera ===

* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

=== Network ===

* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

=== Storage ===

* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 1 USB3.0 Host port
* 1 USB type C OTG port with DP output
* 2 USB2.0 Dedicated Host ports

=== Expansion Ports ===

* 2x20 pins "Pi2" GPIO Header
* PCIe 2.1 (4 full-duplex lanes with 20Gbps) x4 open ended port

==== GPIO Pins ====

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

===== Notes =====

* '''a:''' pulled high to 3.3V through 2.2kOhm resistor

===== Linux /dev/gpiochip Assignments =====

{| class=wikitable style="max-width: 1000px; text-align: center;"
|-
! scope="row" | Pin Nr.
| 3 || 5 || 7 || 8 || 10 || 11 || 12 || 13 || 15 || 16 || 18 || 19 || 21 || 22 || 23 || 24 || 26 || 27 || 28 || 29 || 31 || 32 || 33 || 35 || 36 || 37 || 38 || 40
|-
! scope="row" | Chip
| 1 || 1 || 4 || 4 || 4 || 1 || 3 || 1 || 1 || 1 || 4 || 1 || 1 || 4 || 1 || 1 || 1 || 1 || 1 || 4 || 4 || 3 || 3 || 3 || 3 || 3 || 3 || 3
|-
! scope="row" | Line
| 20 || 21 || 24 || 20 || 19 || 22 || 24 || 18 || 1 || 4 || 21 || 8 || 7 || 25 || 9 || 10 || 13 || 11 || 12 || 27 || 28 || 28 || 29 || 26 || 30 || 25 || 27 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API, the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>, and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source. Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them, and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on. Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

=== Working Features ===

{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7″ LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/Yes*
| Verified with Manjaro ARM (kernel 6.2.5). A config file ("firmware file") is needed at <code>/lib/firmware/brcm/brcmfmac43455-sdio.txt</code>. See here for the file contents and details: https://askubuntu.com/a/1211986.
|
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons. After testing for a few hours, on Manjaro ARM (kernel 6.2.5), I did not experience any stability issues (WIFI stayed connected). On a 5GHz network (802.11AC), I was able to get about 120Mbps using the "new" ROCKPro64 WIFI module.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it. This is working in Manjaro ARM (kernel 6.2.5). Select the <code>Analog Output (Built-in Audio Stereo)</code> option in the audio output device selection window (either use <code>pavucontrol</code> or the volume button in the KDE desktop). Despite the slightly misleading name, audio does go through the HDMI port. See here for details: https://forum.manjaro.org/t/no-hdmi-audio-on-rockpro64/25595/2.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is near impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| https://pine64.com/?product=rockpro64-playbox-enclosure
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://store.pine64.org/?product=rockpro64-heatsink
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCIe 2.1
|
|
|
|
|
|
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| https://store.pine64.org/?product=rtc-backup-battery-cr-battery
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

== Board Information, Schematics and Certifications ==
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: +12V @3A/5A with 5.5mm/2.1mm Type M Barrel type DC connector
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

Certifications:

* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
* [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
* [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

== Datasheets for Components and Peripherals ==

Rockchip RK3399 SoC information:

* [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
* [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
* [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
* [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]

LPDDR4 (200 Balls) SDRAM:

* [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]

eMMC information:

* [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
* [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
* [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
* [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]

SPI NOR Flash information:

* [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]

Heatsink related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
* [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]

Wireless related info:

* AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]

Ethernet related info:

* [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]

Peripheral related info:

* [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]

Remote control button mapping:

* [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]

Audio Codec (ES8316) (under board):

* [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

PWM controlled fan, SPDIF, and RTC Battery Backup headers:

* [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

== Useful Articles and Blog Posts ==

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]

* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]

* [[ROCKPro64 Device Tree Overlays on Mainline]]

== The NAS Case for the ROCKPro64 ==

[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

Please [[NASCase|follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

== 3D printable ITX mounting brackets ==

[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A Quartz64-A mounted in an ITX case using 3D printed brackets]]

Allows mounting a ROCKPro64-A or Quartz64-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

== Other Resources ==

* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]
* [[ROCKPro64 Installing Arch Linux ARM]]
* [[ROCKPro64 Powering From An ATX Supply]]

== Troubleshooting ==

=== No Video or GPU Acceleration on Debian ===

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in your log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

Log in to your ROCKPro64, and run the following:

sudo -i
echo governor_simpleondemand >> /etc/initramfs-tools/modules && update-initramfs -u -k $(uname -r)
exit

Then, reboot.

[[Category:ROCKPro64]] [[Category:Rockchip RK3399]]