PINE64 - User contributions [en]

PINE A64-LTS

2022-01-03T12:41:13Z

Abcde: /* Pine A64-LTS, SOPine Module and Baseboard Information, Schematics, and Certifications */ add archive.org link to dead article.

[[File:PINEA64_LTS_sideimg.jpg|400px|thumb|right|The PINE A64-LTS]]
[[File:SOPINE_front.jpg|400px|thumb|right|The SOPINE A64]]

The '''PINE64-LTS''' is the long term supply version of the PINE A64 (+), ''PINE64's'' first single board computer, powered by Allwinner’s A64 quad-core ARM Cortex A53 64-Bit SoC. There are many operating systems available for the PINE A64-LTS created by the open source community and various partner projects. The PINE A64-LTS is guaranteed to be supplied until the year 2025 at the very least.

The '''SOPINE A64''' is a compute module powered by the same Quad-Core ARM Cortex A53 64-Bit Processor used in the PINE A64 with 2G LPDDR3 RAM memory, Power Management Unit, SPI Flash and integrated MicroSD Slot (for bootable OS images microSD card). The SOPINE module has a 5 years LTS (Long Term Supply) status, which means that it will be supplied to 2022 at the very least. There is a one year warranty period for the SOPINE module. This tiny compute module uses SODIMM-DDR3 form-factor and can be paired with either the Clusterboard, the Baseboard or a custom host PCB for industrial or other embedded applications. It is fully compatible with the PINE A64-LTS in terms of software support

== Software releases ==

'''Important''': The SOPine operating system images are compatible with PINE A64-LTS.

Please see [[SOPINE Software Release]] for a complete list of currently supported operating system images that work with the SOPine, as well as other related software. For a quick reference, the list includes the following operating system images:

* [[SOPINE_Software_Release#Armbian|Armbian]]
* [[SOPINE_Software_Release#AOSC|AOSC]]
* [[SOPINE Software Release#OpenEmbedded.2FYocto_Images|OpenEmbedded/Yocto]]
* [[SOPINE Software Release#OpenWRT|OpenWRT]]
* [[SOPINE Software Release#Volumio 2 Digital Audio Player|Volumio 2 Digital Audio Player]]
* [[SOPINE Software Release#FreedomBox|FreedomBox]]
* [[SOPINE Software Release#LibreELEC(KODI)|LibreELEC (KODI)]]
* [[SOPINE Software Release#NetBSD|NetBSD]]
* [[SOPINE Software Release#Android 6.x|Android 6.x]] / [[SOPINE Software Release#Android 5.x|Android 5.x]].

Below is a list of links to the build sources and environments for some operating system images. Some of themare labelled as '''beta or nightly builds''', which means they are fit for testing purposes only. Those images should be used at your own risk and are not fit for regular use.

* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ longsleep BSP Linux]
* [https://github.com/ayufan-pine64/linux-build/releases/latest/ ayufan Linux]
* [https://github.com/ayufan-pine64/android-7.1/releases/latest/ ayufan Android 7.1], [https://github.com/ayufan-pine64/android-6.0/releases/latest/ Android 6.0], and [https://github.com/ayufan-pine64/android-5.1/releases/latest/ Android 5.1]
* [https://pine64suse.weebly.com/download.html openSUSE]
* [https://dl.armbian.com/pine64so/archive/ SOPINE Armbian]
* [https://github.com/anarsoul/linux-build/releases/latest Arch Linux XFCE]
* [https://sourceforge.net/projects/openmediavault/files/Other%20armhf%20images/ OpenMediaVault]

== Accessories and Step-by-Step Guides ==

Please see [[Accessories Step by Step Guides]] for a list of guides for Pine A64 accessories; there you can find instructions and guides about the following:

* Enclosures
* Bluetooth and WiFi module
* Real Time Clock (RTC) battery
* Real Time Clock (RTC) battery holder
* First and third party cases
* Featured 3D printed cases (and more)

== SoC and Memory Specification ==
* Based on Allwinner A64/R18
** '''R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor.'''
[[File:Allwinner_A64.jpg|right]]
[[File:Allwinner_R18.png|right]]

=== CPU Architecture ===
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core ARM Cortex-A53 Processor@1152Mhz]
* A power-efficient ARM v8 architecture
* 64 and 32bit execution states for scalable high performance
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function
* Support Large Physical Address Extensions(LPAE)
* VFPv4 Floating Point Unit
* 32KB L1 Instruction cache and 32KB L1 Data cache
* 512KB L2 cache

=== GPU Architecture ===
* [https://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-400.php ARM Mali400MP2 Dual-core GPU]
* Support OpenGL ES 2.0 and OpenVG 1.1 standard

=== System Memory ===
* RAM Memory Variants: 2GB LPDDR3.
* Storage Memory: 128Mb SPI Flash and optional eMMC module from 16GB up to 128GB

== PINE A64-LTS Board Features ==
[[File:PINEA64 LTS board front.jpg|thumb|400px|Front view of a Pine A64-LTS board]]
[[File:PINEA64 LTS board back.jpg|thumb|400px|Rear view of a Pine A64-LTS board]]

=== Video ===
* Digital Video (Type A - full)

=== Audio ===
* 3.5mm stereo earphone/microphone plug

=== Network ===
* 10/100/1000Mbps Ethernet(PINE A64+ version), 10/100Mbps Ethernet(PINE A64 version)
* WiFi 802.11 b/g/n with Bluetooth 4.0 (optional)

=== Storage ===
* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* USB - 2 USB2.0 Host port

=== Expansion Ports ===
* DSI - Display Serial Interface, 4 lanes MiPi, up to 1080P
* CSI - CMOS Camera Interface up to 5 mega pixel
* TP - Touch Panel Port, SPI with interrupt
* RTC - Real Time Clock Battery Connector
* VBAT - Lithium Battery Connector with temperature sensor input
* Wifi/BT Module Header - SDIO 3.0 and UART
* 2x20 pins "Pi2" GPIO Header
* 2x17 pins "Euler" GPIO Header
* 2x5 pins "EXP" Console Header

== Pine A64-LTS, SOPine Module and Baseboard Information, Schematics, and Certifications ==
[[File:SOPINE Baseboard front.jpg|thumb|400px|Front view of a SOPine Baseboard]]
[[File:SOPINE front.jpg|thumb|400px|Front view of a SOPine module]]
[[File:SOPINE back.jpg|thumb|400px|Rear view of a SOPine module]]

* Model "A" Baseboard Dimensions: 133mm x 80mm x 19mm
* Input Power: DC 5V @ 2A, 3.7V Li-Ion battery connector, 3.5OD/1.35ID Barrel DC Jack connector, Euler connector
* [https://wiki.pine64.org/images/7/7d/Pine64_Board_Connector.png PINE A64 Connector Layout @courtesy of norm24]
* [https://wiki.pine64.org/images/d/da/Pine64_Connector.JPG PINE A64 Connector List]
* [https://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Pin-Assignments-ver-1.0.pdf SOPine Module Pin Assignment ver 1.0]
* [https://forum.pine64.org/showthread.php?tid=8058 a PDF mapping the pins from the A64 chip itself, to the gold-fingers on the SO-DIMM edge, to the multiple connectors on the baseboard and on the clusterboard, attached to this forum post.]
* [https://files.pine64.org/doc/Pine%20A64%20Schematic/Pine%20A64%20Pin%20Assignment%20160119.pdf PINE A64 Pi-2/Eular/Ext Bus/Wifi Bus Connector Pin Assignment (Updated 15/Feb/2016)]
** [https://synfare.com/599N105E/hwdocs/pine64/index.html Good documentation about PINE A64, A64+, and A64-LTS GPIO pins article] [https://web.archive.org/web/20190915051944/https://synfare.com/599N105E/hwdocs/pine64/index.html Archive.org link]
* Pine A64-LTS Schematic:
** [https://files.pine64.org/doc/SOPINE-A64/PINE%20A64-TLS-20180130.pdf Pine A64-LTS Schematic]
* SOPine Module Schematic:
** [https://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Schematic-ver-0.9.pdf SOPine Module Schematic]
* SOPine Model "A" Baseboard Schematic and PCB Board Resource:
** '''SOPine model "A" Baseboard is an hardware open source project but is not "OSH" compliant'''
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Baseboard%20Model%20A%20Rev%20B20170207.DSN SOPine Model "A" Baseboard Schematic capture Rev B DSN source file]
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Baseboard%20Model%20A%20Rev%20B20170207.pdf SOPine Model "A" Baseboard Schematic Rev B PDF file]
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Model%20A%20baseboard%20PCB%20layout%20PCB%20Job.tar SOPine Model "A" Baseboard PCB Job source file]
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Model%20A%20basedboard%20GERBER.tar SOPine Model "A" Baseboard PCB Gerber file]
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Model%20A%20baseboard%20PCB%20layout%20PDF.tar SOPine Model "A" Baseboard PCB Layout PDF file]
* PINE A64-LTS / SOPine Wifi/BT module Schematic
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf PINE A64 Wifi/BT Module Schematic]
* PINE A64-LTS / SOPine Stereo Audio Dac Board Schematic
**[https://forum.pine64.org/attachment.php?aid=697 PINE A64-LTS / SOPine Stereo Audio Dac Board Schematic]
* SOPine (together with model "A" baseboard) Certification:
** Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submits the SBC for FCC, CE, and ROHS certifications and obtain the certificates to prove that the SBC board can pass the testing. Please note, a final commercial product needs to perform its own testing and obtain its own certificate.
** [https://files.pine64.org/doc/cert/SOPine%20FCC%20certification%20VOC20170428.pdf SOPine with model "A" baseboard FCC Certificate]
** [https://files.pine64.org/doc/cert/SOPine%20CE%20certification%20VOC20170428.pdf SOPine with model "A" baseboard CE Certificate]
** [https://files.pine64.org/doc/cert/SOPine%20ROHS%20certification%20VOC20170322.pdf SOPine with model "A" baseboard RoHS Certificate]

== Datasheets for Components and Peripherals ==
* Allwinner A64/R18 SoC information:
** '''R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor.'''
** [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner-R18-Brief%20Sheet.pdf Allwinner R18 SoC Brief Introduction]
** [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64/R18 SoC Data Sheet V1.1 (Official Released Version)]
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64/R18 SoC User Manual V1.0 (Official Release Version)]
* X-Powers AXP803 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]
* LPDDR3 information:
** [https://files.pine64.org/doc/datasheet/pine64/AWL3A1632_mobile_lpddr3_1600Mbps.pdf Allwinner LPDDR3 Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/FORESEE%20178ball%2012x11.5%20LPDDR3%2016G%20Spec%20V1.0-1228.pdf Foresee LPDDR3 Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/K4E6E304EE-EGCE.pdf Samsung LPDDR3 Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/LPDDR3%20178ball%208Gb_H9CCNNN8JTALAR_Rev1.0.pdf Hynix LPDDR3 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]
* '''PINE A64, PINE A64+, PINE A64-LTS and SOPINE Related:'''
** 5MPixel CMOS Camera module information:
*** [https://files.pine64.org/doc/datasheet/pine64/YL-PINE64-4EC.pdf PINE64 YL-PINE64-4EC 5M Pixel CMOS Image Sensor Module (Description in Chinese)]
*** [https://files.pine64.org/doc/datasheet/pine64/S5K4EC%205M%208%205X8%205%20PLCC%20%20Data%20Sheet_V1.0.pdf S5K4EC 5MP CMOS Image Sensor SoC Module Datasheet]
*** [https://files.pine64.org/doc/datasheet/pine64/S5K4ECGX_EVT1_DataSheet_R005_20100816.pdf S5K4EC 5MP CMOS Image Sensor SoC Chip Datasheet]
*** [https://files.pine64.org/doc/datasheet/pine64/s5k4ec.c S5K4EC 5MP CMOS Image Sensor Driver Source Code in C language]
*** Early version Camera module information:
**** [https://files.pine64.org/doc/datasheet/pine64/D116-A64_Bonsen_cmos_camera.pdf Bonsen Kexin V118-A64-GC2145-HM5065 CMOS Image Sensor Module]
**** [https://files.pine64.org/doc/datasheet/pine64/HM5065-DS-V03.pdf HiMax 5MP CMOS Image Sensor SoC]
** LCD Touch Screen Panel information:
*** [https://files.pine64.org/doc/datasheet/pine64/FY07024DI26A30-D_feiyang_LCD_panel.pdf 7.0" 1200x600 TFT-LCD Panel Specification]
*** [https://files.pine64.org/doc/datasheet/pine64/HK70DR2459-PG-V01.pdf Touch Panel Specification]
*** [https://files.pine64.org/doc/datasheet/pine64/GT911%20Capacitive%20Touch%20Controller%20Datasheet.pdf GOODiX GT911 5-Point Capacitive Touch Controller Datasheet]
** Lithium Battery information:
*** [https://files.pine64.org/doc/datasheet/pine64/9070120P%203.7V%208000MAH.pdf 8000mAH Lithium Battery Specification]
** Ethernet PHY information:
*** [https://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver for PINE A64-LTS Board and SOPine Baseboard]
** Wifi/BT module information:
*** [https://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf PINE A64 Wifi/BT Module Schematic]
*** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]
** Enclosure information:
*** [https://files.pine64.org/doc/datasheet/case/playbox_enclosure_20160426.stp Playbox Enclosure 3D file]
*** [https://files.pine64.org/doc/datasheet/case/ABS_enclosure_20160426.stp ABS Enclosure 3D file]
*** [https://files.pine64.org/doc/datasheet/case/pine64%20Die%20Cast%20casing-final.jpg Outdoor Aluminum Cast Dust-proof IP67 Enclosure Drawing]
** Connector information:
*** [https://files.pine64.org/doc/datasheet/pine64/ePH.pdf 2.0mm PH Type connector specification use in Lithium Battery (VBAT) port and RTC Battery port]
*** [https://files.pine64.org/doc/datasheet/pine64/0.5FPC%20Front%20Open%20Connector%20H=1.5.pdf 0.5mm Pitch cover type FPC connector specification use in DSI port, TP port and CSI port]
** Remote control button mapping
*** [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE A64 Button Mapping]

== Pine A64 POT ==
* [[POT|PINE A64 Peripheral On Top (POT) and Related Devices]]
* [[Wifi_Remote_I2c|WiFi Remote I2c Quick Start Guide]]

== Other Resources ==
* [https://linux-sunxi.org/Pine64#Manufacturer_images Linux Sunxi Wiki page on PINE A64]
* [https://github.com/umiddelb/z2d/tree/master/pine64 Collection of scripts to set up a minimal Xenial 14.04.3 / Debian 8 Jessie root filesystem Contributed By Uli Middelberg]
* [https://github.com/apritzel/pine64 Linux Image created by Andre Przywara]
* [https://blog.hypriot.com/post/the-pine-a64-is-about-to-become=the-cheapest-ARM-64-bit-platform-to-run-Docker/ PINE A64 with HypriotOS by Dieter and Govinda]
* [https://sosfakeflash.wordpress.com/2008/09/02/h2testw-14-gold-standard-in-detecting-usb-counterfeit-drives/comment-page-3/#comment-9861 H2testw 1.4 – Gold Standard In Detecting USB Counterfeit Drives]
* [https://oss.digirati.com.br/f3/ F3 - an alternative to h2testw]
* [https://www.phoronix.com/scan.php?page=article&item=pine-64-benchmark&num=1 Benchmarking The Low-Cost PINE 64+ ARM Single Board Computer by Michael Larabel]
* [https://github.com/longsleep/build-pine64-image PINE64 Linux build scripts, tools and instructions by Longsleep]
* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ PINE64 Linux image by Longsleep]
* [https://www.youtube.com/playlist?list=PLgj96wTPcMKffRm_Sk6673Nfy_I6b5UJW A series of Youtube video on PINE A64 Developers Board by Michael Larson]
* [https://rayhightower.com/blog/2016/04/04/pine64-quick-start-guide-using-mac-os-x/ PINE64 Quick Start Guide (with Gotchas)]
* [https://softwarebakery.com/shrinking-images-on-linux Shrinking images on Linux by FrozenCow]
* [https://gitlab.manjaro.org/packages/community/manjaro-arm-installer Manjaro Arm installation script]

[[Category:SOPine]] [[Category:A64-LTS]] [[Category:Allwinner A64]]

Main Page

2021-11-20T16:45:29Z

Abcde: /* Chat Platforms */ typo

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones: '''[[PinePhone]]''' and '''[[PinePhone Pro]]'''
* Tablets: '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatch: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''', '''[[SOEdge]]''' and '''[[SOQuartz]]'''
* IP camera: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot.

{{note|1=The activity of community members varies depending on the time of day and the number of active users, so please be patient and do not expect questions to be answered immediately.}}

The community chat platforms are the following:
* '''Discord''': Use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''IRC''': The server is irc.pine64.org. Use <code>/list</code> command or the table below to see the full list of channels.
* '''Matrix and Telegram''': See the table below.

{| class="wikitable"
! Channel !! Matrix !! Telegram !! IRC
|-
| PINE64 News
| [https://app.element.io/#/room/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://app.element.io/#/room/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://app.element.io/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://app.element.io/#/room/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://app.element.io/#/room/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://app.element.io/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz64-dev
|-
| Pinebook and Pinebook Pro
| [https://app.element.io/#/room/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://app.element.io/#/room/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://app.element.io/#/room/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://app.element.io/#/room/#pinetab64:matrix.org #pinetab64:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://app.element.io/#/room/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #Pinetime
|-
| PineTime Development
| [https://app.element.io/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| Pinecil
| [https://app.element.io/#/room/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| Cube
| [https://app.element.io/#/room/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker
| [https://app.element.io/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://app.element.io/#/room/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://app.element.io/#/room/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #Offtopic
|}

There is also an unofficial Matrix Space at [https://app.element.io/#/room/#pine64-space:matrix.org #pine64-space:matrix.org] for supported clients that organizes all of the above matrix channels into one place.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.

PinePhone Pro

2021-10-15T15:47:56Z

Abcde: initial specs and some base info

The PinePhone Pro is an upgraded [[PinePhone]]. On 15 October 2021 Pine64 announced a successor to the PinePhone. It has 4 GB RAM and 128 GB eMMC, and has a hexa-core RK3399S processor. The RK3399S is a special version of the RK3399 made specifically for the PinePhone Pro.

== Introduction ==

== Links to information ==
*[https://www.pine64.org/pinephonepro/ Product Page]
*[https://www.pine64.org/2021/10/15/october-update-introducing-the-pinephone-pro/ Blogpost] with announcement
*[https://xnux.eu/log/#047 Megi]'s blogpost about the device

== Specifications ==

* '''Dimensions:''' 160.8 x 76.6 x 11.1mm
* '''Weight:''' Approx. 215g
* '''SIM Card:''' ?Micro-SIM?
* '''Display:'''
** '''Size:''' 6 inches (151mm) diagonal
** '''Type:''' 1440 x 720 in-cell IPS with Gorilla Glass 4™
** '''Resolution:''' 1440x720, 18:9 ratio
* '''System on Chip:''' Rockchip RK3399S 64bit SoC – 2x A72 and 4x A53 CPU cores @ 1.5GHz
* '''RAM:''' 4GB LPDDR4 @ 800MHz
* '''Internal Storage:''' 128GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC
* '''Back [[#Camera|Camera]]:''' 13MP Sony IMX258 with Gorilla Glass 4™ protective layer, LED Flash
* '''Front Camera:''' 5MP OmniVision OV5640 front-facing camera
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if hardware switch 6 is deactivated)
* '''Communication:'''
** '''[[#Modem|Modem]]:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28
** '''LTE-TDD''': B38, B39, B40, B41
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)
** '''WLAN & Bluetooth:''' AMPAK AP6255 WiFi 11ac + Bluetooth V4.1
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass
* '''Privacy switches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''[[#Battery|Battery]]:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery)
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== Components ==

== Press ==

For an overview about media of the PinePhone you can use for the news, blogs, or similar see [[PinePhone Press]].

== PinePhone board information, schematics and certifications ==

== Datasheets for components and peripherals ==

== Developer works ==

[[Category:PinePhone]] [[Category:PinePhone Pro]] [[Category:Rockchip RK3399]]

PinePhone Pro

2021-10-15T14:37:13Z

Abcde: typo

The PinePhone Pro is an upgraded [[PinePhone]]. It has 4 GB RAM and 128 GB eMMC, and has a hexa-core RK3399S processor. The RK3399S is a special version of the RK3399 made specifically for the PinePhone Pro.

Links to information:
*[https://www.pine64.org/pinephonepro/ Product Page]
*[https://www.pine64.org/2021/10/15/october-update-introducing-the-pinephone-pro/ Blogpost] with announcement
*[https://xnux.eu/log/#047 Megi]'s blogpost about the device

PinePhone Pro

2021-10-15T14:36:53Z

Abcde: added links

The PinePhone Pro is an upgraded [[PinePhone]]. It has 4 GB RAM and 128 GB eMMC, and has a hexa-core RK3399S processor. The RK3399S is a special version of the RK3399 made specifically for the PinePhone Pro.

Links to information:
[https://www.pine64.org/pinephonepro/ Product Page]
[https://www.pine64.org/2021/10/15/october-update-introducing-the-pinephone-pro/ Blogpost] with announcement
[https://xnux.eu/log/#047 Megi]'s blogpost about the device

Main Page

2021-10-15T12:58:22Z

Abcde: /* Chat Platforms */ rewording

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones and tablets: '''[[PinePhone]]''', '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatches: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''' and '''[[SOEdge]]'''
* IP cameras: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot. The community chat platforms are the following:

* '''Discord''': Use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''Matrix'''
* '''Telegram'''
* '''IRC''': The server is irc.pine64.org. There is a WebIRC client on www.pine64.org/web-irc, but use of a dedicated client is advised. Use <code>/list</code> command to see the full list of channels.

{{note|1=The activity of community members varies depending on the time of day and the number of active users, so please be patient and do not expect questions to be answered immediately.}}
{| class="wikitable"
! Channel !! Matrix !! Telegram !! IRC
|-
| PINE64 News
| [https://app.element.io/#/room/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://app.element.io/#/room/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://app.element.io/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://app.element.io/#/room/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://app.element.io/#/room/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://app.element.io/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz64-dev
|-
| Pinebook and Pinebook Pro
| [https://app.element.io/#/room/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://app.element.io/#/room/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://app.element.io/#/room/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://app.element.io/#/room/#pinetab:pine64.org #pinetab:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://app.element.io/#/room/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #pinetime
|-
| PineTime Development
| [https://app.element.io/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| Pinecil
| [https://app.element.io/#/room/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| Cube
| [https://app.element.io/#/room/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker
| [https://app.element.io/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://app.element.io/#/room/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://app.element.io/#/room/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #Offtopic
|}
There is an unofficial Matrix Space at [https://app.element.io/#/room/#pine64-space:matrix.org #pine64-space:matrix.org] that organizes all of the channels into one place. Requires the spaces beta to be enabled in Element or other supported clients.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.

Main Page

2021-10-15T12:55:47Z

Abcde: /* Chat Platforms */ more typo

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones and tablets: '''[[PinePhone]]''', '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatches: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''' and '''[[SOEdge]]'''
* IP cameras: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot. The community chat platforms are the following:

* '''Discord''': Use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''Matrix'''
* '''Telegram'''
* '''IRC''': The IRC channels can be reached via irc.pine64.org. There is a WebIRC client on www.pine64.org/web-irc/ but use of a dedicated client is advised. Use <code>/list</code> to see the full list of channels.

{{note|1=The activity of community members varies depending on the time of day and the number of active users, so please be patient and do not expect questions to be answered immediately.}}
{| class="wikitable"
! Channel !! Matrix !! Telegram !! IRC
|-
| PINE64 News
| [https://app.element.io/#/room/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://app.element.io/#/room/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://app.element.io/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://app.element.io/#/room/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://app.element.io/#/room/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://app.element.io/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz64-dev
|-
| Pinebook and Pinebook Pro
| [https://app.element.io/#/room/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://app.element.io/#/room/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://app.element.io/#/room/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://app.element.io/#/room/#pinetab:pine64.org #pinetab:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://app.element.io/#/room/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #pinetime
|-
| PineTime Development
| [https://app.element.io/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| Pinecil
| [https://app.element.io/#/room/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| Cube
| [https://app.element.io/#/room/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker
| [https://app.element.io/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://app.element.io/#/room/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://app.element.io/#/room/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #Offtopic
|}
There is an unofficial Matrix Space at [https://app.element.io/#/room/#pine64-space:matrix.org #pine64-space:matrix.org] that organizes all of the channels into one place. Requires the spaces beta to be enabled in Element or other supported clients.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.

Main Page

2021-10-15T12:52:12Z

Abcde: /* Chat Platforms */ typo's

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones and tablets: '''[[PinePhone]]''', '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatches: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''' and '''[[SOEdge]]'''
* IP cameras: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot. The community chat platforms are the following:

* '''Discord''': Use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''Matrix'''
* '''Telegram'''
* '''IRC''': The IRC channels can be reached via irc.pine64.org. There is a WebIRC client on www.pine64.org/web-irc/ but use of a dedicated client is advised. Use ''/list'' to see the full list of channels.

{{note|1=The activity of community members varies depending on the time of day and the number of active users, so please be patient and do not expect questions to be answered immediately.}}
{| class="wikitable"
! Channel !! Matrix !! Telegram !! IRC
|-
| PINE64 News
| [https://app.element.io/#/room/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://app.element.io/#/room/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://app.element.io/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://app.element.io/#/room/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://app.element.io/#/room/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://app.element.io/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz64-dev
|-
| Pinebook and Pinebook Pro
| [https://app.element.io/#/room/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://app.element.io/#/room/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://app.element.io/#/room/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://app.element.io/#/room/#pinetab:pine64.org #pinetab:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://app.element.io/#/room/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #pinetime
|-
| PineTime Development
| [https://app.element.io/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| Pinecil
| [https://app.element.io/#/room/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| Cube
| [https://app.element.io/#/room/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker
| [https://app.element.io/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://app.element.io/#/room/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://app.element.io/#/room/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #Offtopic
|}
There is an unofficial Matrix Space at [https://app.element.io/#/room/#pine64-space:matrix.org #pine64-space:matrix.org] that organizes all of the channels into one place. Requires the spaces beta to be enabled in Element or other supported clients.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.

Main Page

2021-10-15T12:32:27Z

Abcde: /* Chat Platforms */ reverted list description move

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones and tablets: '''[[PinePhone]]''', '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatches: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''' and '''[[SOEdge]]'''
* IP cameras: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot. The community chat platforms are the following:

* '''Discord''': use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''Matrix'''
* '''Telegram'''
* '''IRC''': The IRC channels can be reached via irc.pine64.org. There is a WebIRC on www.pine64.org/web-irc/ but use of a dedicated client is advised. Use '/list' to see the full list of channels.

{{note|1=The activity of community members varies depending on the time of day and the number of active users, so please be patient and do not expect questions to be answered immediately.}}
{| class="wikitable"
! Channel !! Matrix !! Telegram !! IRC
|-
| PINE64 News
| [https://app.element.io/#/room/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://app.element.io/#/room/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://app.element.io/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://app.element.io/#/room/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://app.element.io/#/room/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://app.element.io/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz64-dev
|-
| Pinebook and Pinebook Pro
| [https://app.element.io/#/room/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://app.element.io/#/room/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://app.element.io/#/room/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://app.element.io/#/room/#pinetab:pine64.org #pinetab:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://app.element.io/#/room/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #pinetime
|-
| PineTime Development
| [https://app.element.io/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| Pinecil
| [https://app.element.io/#/room/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| Cube
| [https://app.element.io/#/room/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker
| [https://app.element.io/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://app.element.io/#/room/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://app.element.io/#/room/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #Offtopic
|}
There is an unofficial Matrix Space at [https://app.element.io/#/room/#pine64-space:matrix.org #pine64-space:matrix.org] that organizes all of the channels into one place. Requires the spaces beta to be enabled in Element or other supported clients.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.

Main Page

2021-10-15T12:29:19Z

Abcde: /* Chat Platforms */ Small edits for readability

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones and tablets: '''[[PinePhone]]''', '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatches: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''' and '''[[SOEdge]]'''
* IP cameras: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot.

* '''Discord''': use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''Matrix'''
* '''Telegram'''
* '''IRC''': The IRC channels can be reached via irc.pine64.org. There is a WebIRC on www.pine64.org/web-irc/ but use of a dedicated client is advised. Use '/list' to see the full list of channels.

{{note|1=The activity of community members varies depending on the time of day and the number of active users, so please be patient and do not expect questions to be answered immediately.}}
The community chat platforms are the following:
{| class="wikitable"
! Channel !! Matrix !! Telegram !! IRC
|-
| PINE64 News
| [https://app.element.io/#/room/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://app.element.io/#/room/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://app.element.io/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://app.element.io/#/room/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://app.element.io/#/room/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://app.element.io/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz64-dev
|-
| Pinebook and Pinebook Pro
| [https://app.element.io/#/room/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://app.element.io/#/room/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://app.element.io/#/room/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://app.element.io/#/room/#pinetab:pine64.org #pinetab:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://app.element.io/#/room/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #pinetime
|-
| PineTime Development
| [https://app.element.io/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| Pinecil
| [https://app.element.io/#/room/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| Cube
| [https://app.element.io/#/room/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker
| [https://app.element.io/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://app.element.io/#/room/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://app.element.io/#/room/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #Offtopic
|}
There is an unofficial Matrix Space at [https://app.element.io/#/room/#pine64-space:matrix.org #pine64-space:matrix.org] that organizes all of the channels into one place. Requires the spaces beta to be enabled in Element or other supported clients.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.

Main Page

2021-10-15T12:08:47Z

Abcde: test adding patience note

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones and tablets: '''[[PinePhone]]''', '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatches: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''' and '''[[SOEdge]]'''
* IP cameras: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The community chat platforms are the following:

* '''Discord''': use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''Matrix''' and '''Telegram''':
* '''IRC''': The IRC channels can be reached via irc.pine64.org. There is a WebIRC on www.pine64.org/web-irc/ but use of a dedicated client is advised. The other networks and their users are represented by P64ProtocolBot. Use '/list' to see the full list of channels.

{{note|1=The activity of community members varies depending on the time of day and the number of active users, so please be patient and do not expect questions to be answered immediately.}}
{| class="wikitable"
! Channel !! Matrix !! Telegram !! IRC
|-
| PINE64 News
| [https://app.element.io/#/room/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://app.element.io/#/room/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://app.element.io/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://app.element.io/#/room/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://app.element.io/#/room/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://app.element.io/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz64-dev
|-
| Pinebook and Pinebook Pro
| [https://app.element.io/#/room/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://app.element.io/#/room/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://app.element.io/#/room/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://app.element.io/#/room/#pinetab:pine64.org #pinetab:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://app.element.io/#/room/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #pinetime
|-
| PineTime Development
| [https://app.element.io/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| Pinecil
| [https://app.element.io/#/room/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| Cube
| [https://app.element.io/#/room/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker
| [https://app.element.io/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://app.element.io/#/room/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://app.element.io/#/room/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #Offtopic
|}

* '''Matrix Space''': There is an unofficial Matrix Space at [https://app.element.io/#/room/#pine64-space:matrix.org #pine64-space:matrix.org] that organizes all of the channels into one place. Requires the spaces beta to be enabled in Element or other supported clients.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.

Main Page

2021-10-15T12:03:16Z

Abcde: /* Chat Platforms */ Edited IRC info according to discussion on #pine64

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones and tablets: '''[[PinePhone]]''', '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatches: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''' and '''[[SOEdge]]'''
* IP cameras: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The community chat platforms are the following:

* '''Discord''': use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''Matrix''' and '''Telegram''':
* '''IRC''': The IRC channels can be reached via irc.pine64.org. There is a WebIRC on www.pine64.org/web-irc/ but use of a dedicated client is advised. The other networks and their users are represented by P64ProtocolBot. Use '/list' to see the full list of channels.

{| class="wikitable"
! Channel !! Matrix !! Telegram !! IRC
|-
| PINE64 News
| [https://app.element.io/#/room/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://app.element.io/#/room/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://app.element.io/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://app.element.io/#/room/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://app.element.io/#/room/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://app.element.io/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz64-dev
|-
| Pinebook and Pinebook Pro
| [https://app.element.io/#/room/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://app.element.io/#/room/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://app.element.io/#/room/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://app.element.io/#/room/#pinetab:pine64.org #pinetab:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://app.element.io/#/room/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #pinetime
|-
| PineTime Development
| [https://app.element.io/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| Pinecil
| [https://app.element.io/#/room/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| Cube
| [https://app.element.io/#/room/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker
| [https://app.element.io/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://app.element.io/#/room/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://app.element.io/#/room/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #Offtopic
|}

* '''Matrix Space''': There is an unofficial Matrix Space at [https://app.element.io/#/room/#pine64-space:matrix.org #pine64-space:matrix.org] that organizes all of the channels into one place. Requires the spaces beta to be enabled in Element or other supported clients.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.

Main Page

2021-10-15T09:31:05Z

Abcde: /* Chat Platforms */ Removed IRC warning

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones and tablets: '''[[PinePhone]]''', '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatches: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''' and '''[[SOEdge]]'''
* IP cameras: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The community chat platforms are the following:

* '''Discord''': use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''Matrix''' and '''Telegram''':
{| class="wikitable"
! Channel !! Matrix !! Telegram
|-
| PINE64 News
| [https://app.element.io/#/room/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
|-
| General PINE64 chat
| [https://app.element.io/#/room/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
|-
| PINE A64(+), A64-LTS & SOPine
| [https://app.element.io/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
|-
| ROCK64 / ROCKPro64
| [https://app.element.io/#/room/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
|-
| Quartz64
| [https://app.element.io/#/room/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
|-
| Quartz64 Development
| [https://app.element.io/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
|-
| Pinebook and Pinebook Pro
| [https://app.element.io/#/room/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
|-
| PinePhone
| [https://app.element.io/#/room/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
|-
| PineNote
| [https://app.element.io/#/room/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
|-
| PineTab
| [https://app.element.io/#/room/#pinetab:pine64.org #pinetab:matrix.org]
| [https://t.me/PineTab @PineTab]
|-
| PineTime
| [https://app.element.io/#/room/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
|-
| PineTime Development
| [https://app.element.io/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
|-
| Pinecil
| [https://app.element.io/#/room/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
|-
| Pinetalk Podcast || Unavailable || Unavailable
|-
| Cube
| [https://app.element.io/#/room/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
|-
| Nutcracker
| [https://app.element.io/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
|-
| LoRa
| [https://app.element.io/#/room/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
|-
| Off-topic
| [https://app.element.io/#/room/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
|}

* '''Matrix Space''': There is an unofficial Matrix Space at [https://app.element.io/#/room/#pine64-space:matrix.org #pine64-space:matrix.org] that organizes all of the channels into one place. Requires the spaces beta to be enabled in Element or other supported clients.

* '''IRC''': The IRC channels can be reached via irc.pine64.org.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.

SOEDGE

2021-09-12T18:54:11Z

Abcde: Spelling fix

[[File:SOEdge.png|400px|thumb|right|The SOEdge]]

The '''SOEdge''' is a 3TOPS compute module that can be paired with the SOPine base board or USB 3.0 and PCIe adapters for development. It can connect to a SBC, such as the ROCKPro64 or a regular PC.

== Software releases ==

The SOEdge software releases can be found in the article [[SOEdge Software Releases]].

== Accessories Step-by-Step Guides ==
Under [[Accessories_Step_by_Step_Guides|'Guides for model A baseboard accessories']] you can find instructions and guides concerning:
* Enclosures
* Bluetooth and WiFi module
* Real Time Clock (RTC) battery
* Real Time Clock (RTC) battery holder
* First and third party cases
* Featured 3D printed cases (and more)

== SoC and Memory Specification ==
* Based on [https://www.rock-chips.com/a/en/products/RK18_Series/2019/0529/989.html Rockchip RK1808]
[[File:RK1808_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a35 Dual-core ARM Cortex-A35 Processor@1600-2000Mhz]
* A power-efficient ARM 64-Bit Armv8-A architecture
* AArch32 for full backward compatibility with Armv7
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function
* Support Large Physical Address Extensions(LPAE)
* VFPv4 Floating Point Unit
* 32KB L1 Instruction cache and 32KB L1 Data cache
* AArch64 for 64-bit support and new architectural features
* TrustZone security technology
* Neon Advanced SIMD
* DSP and SIMD extensions
* VFPv4 Floating point
* Hardware virtualization support
* 128KB L2 cache

=== Neural Process Unit NPU Capability ===
* [https://www.verisilicon.com/en/IPPortfolio/VivanteNPUIP NPU IP from Verisilicon Vivante]
* Support max 1920 Int8 MAC operation per cycle
* Support max192 Int16 MAC operation per cycle
* Support max 64 FP16 MAC operation per cycle
* 512KB internal buffer
* One isolated voltage domain to support DVFS
* [https://github.com/VeriSilicon/acuity-models Acuity models Github]

[[File:Vivante_Acuity_SDK.jpg]]

=== System Memory ===
* RAM Memory Variants: 2GB DDR4.
* Storage Memory: 128Mb SPI Flash and optional eMMC module from 16GB up to 128GB

== SOEdge Baseboard Features ==

=== Network ===
* 10/100/1000Mbps Ethernet
* WiFi 802.11 b/g/n with Bluetooth 4.0 (optional)

=== Storage ===
* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* USB - 2 USB2.0 Host port

=== Expansion Ports ===
* DSI - Display Serial Interface, 4 lanes MiPi, up to 1080P
* TP - Touch Panel Port, SPI with interrupt
* RTC - Real Time Clock Battery Connector
* VBAT - Lithium Battery Connector with temperature sensor input
* Wifi/BT Module Header - SDIO 3.0 and UART
* 2x20 pins "Pi2" GPIO Header
* PCIe 2x open ended slot

== SOEdge Module and Baseboard Information, Schematics, and Certifications ==
* Model "A" Baseboard Dimensions: 133mm x 80mm x 19mm
* Input Power: DC 12V @ 3A 5.5OD/2.1ID Barrel DC Jack connector

* SOEdge Module Schematic:
** [https://files.pine64.org/doc/SOEdge/SOEdge-Schematic-v2.0-190919.pdf SOEdge Module ver 2.0 20190919 Schematic]
** [https://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-topplace.pdf SOEdge Module ver 2.0 20190919 PCB Component Placement Top PDF file]
** [https://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-bottomplace.pdf SOEdge Module ver 2.0 20190919 PCB Component Placement Bottom PDF file]
** [https://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-topplace.dxf SOEdge Module ver 2.0 20190919 PCB Component Placement Top Drawing file]
** [https://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-bottomplace.dxf SOEdge Module ver 2.0 20190919 PCB Component Placement Bottom Drawing file]
** [https://files.pine64.org/doc/SOEdge/SOEdge%20Pin%20Assignments%20ver%201.00.xlsx SOEdge Module Pin Assignment ver 1.0 in Excel format(includes comparison chart to SOPine)]
** [https://files.pine64.org/doc/SOEdge/SOEdge%20Pin%20Assignments%20ver%201.00.ods SOEdge Module Pin Assignment ver 1.0 in Open Document format(includes comparison chart to SOPine)]
* SOEdge Model "A" Baseboard Schematic and PCB Board Resource:
** [https://files.pine64.org/doc/SOEdge/SOEDGE_MODEL_A_BASEBOARD_Schematic-20210223.pdf SOEdge Model "A" Baseboard Schematic 20210223 PDF file]
** [https://files.pine64.org/doc/SOEdge/SOEDGE_MODEL_A_BASEBOARD_PCB-TOP-20210223.pdf SOEdge Model "A" Baseboard 20210223 PCB Component Placement Top PDF file]
** [https://files.pine64.org/doc/SOEdge/SOEDGE_MODEL_A_BASEBOARD_PCB-BOT-20210223.pdf SOEdge Model "A" Baseboard 20210223 PCB Component Placement Bottom PDF file]
* SOEdge Neural AI Stick Schematic:
** [https://files.pine64.org/doc/SOEdge/SOEdge%20Neural%20AI%20Stick%20Schematic_V10.pdf SOEdge Neural AI Stick PDF file]
* SOEdge/SOPine/PINE A64 Wifi/BT module Schematic
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf PINE A64 Wifi/BT Module Schematic]
* SOEdge module together with model "A" baseboard Certification:
** Disclaimer: Please note that SOEdge module is not a "final" product and in general certification is not necessary. However, SOEdge module still submits the mpdel A baseboard for FCC, CE, and ROHS certifications and obtain the certificates to prove that can pass the testing. Please note, a final commercial product needs to perform its own testing and obtain its own certificate.
** Not yet available

== Datasheets for Components and Peripherals ==
* Rockchip RK1808 SoC information:
** [http://opensource.rock-chips.com/images/4/43/Rockchip_RK1808_Datasheet_V1.2_20190527.pdf Rockchip RK1808 ver 1.2 datasheet]
** [https://files.pine64.org/doc/datasheet/SOEdge/Rockchip%20RK1808%20TRM%20Part1%20V1.2--20190826%20open%20source.pdf Rockchip TK1808 Technical Reference Manual Part 1]
* Rockchip RK809 PMU (Power Management Unit) information:
** [https://rockchip.fr/RK809%20datasheet%20V1.01.pdf Rockchip RK809 PMIC Datasheet]
* DDR4 information:
** [https://files.pine64.org/doc/datasheet/SOEdge/Micron%208Gb_DDR4_SDRAM.pdf Micron DDR4 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]
* '''SOEdge Related:'''
** LCD Touch Screen Panel information:
*** [https://files.pine64.org/doc/datasheet/pine64/FY07024DI26A30-D_feiyang_LCD_panel.pdf 7.0" 1200x600 TFT-LCD Panel Specification]
*** [https://files.pine64.org/doc/datasheet/pine64/HK70DR2459-PG-V01.pdf Touch Panel Specification]
*** [https://files.pine64.org/doc/datasheet/pine64/GT911%20Capacitive%20Touch%20Controller%20Datasheet.pdf GOODiX GT911 5-Point Capacitive Touch Controller Datasheet]
** Ethernet PHY information:
*** [https://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver for SOEdge model A baseboard]
** Wifi/BT module information:
*** [https://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf SOEdge/SOPine/PINE A64 Wifi/BT Module Schematic]
*** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]
** Enclosure information:
*** [https://files.pine64.org/doc/datasheet/case/playbox_enclosure_20160426.stp Playbox Enclosure 3D file]
*** [https://files.pine64.org/doc/datasheet/case/ABS_enclosure_20160426.stp ABS Enclosure 3D file]
*** [https://files.pine64.org/doc/datasheet/case/pine64%20Die%20Cast%20casing-final.jpg Outdoor Aluminum Cast Dust-proof IP67 Enclosure Drawing]
** Connector information:
*** [https://files.pine64.org/doc/datasheet/pine64/ePH.pdf 2.0mm PH Type connector specification use in Lithium Battery (VBAT) port and RTC Battery port]
*** [https://files.pine64.org/doc/datasheet/pine64/0.5FPC%20Front%20Open%20Connector%20H=1.5.pdf 0.5mm Pitch cover type FPC connector specification use in DSI port, TP port and CSI port]

== SOEdge/SOPine Cluster Board Resource ==
* Cluster board is an hardware open source project and is available at the PINE64 store since late January 2018. It allows 7 SOPine or SOEdge devices to be installed simultaneously.
* Please note that this project is not "OSH" compliant
** [https://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2.DSN Clusterboard version 2.2 Schematic Capture source file]
** [https://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2_Schematic.pdf Clusterboard version 2.2 Schematic Capture PDF file]
** [https://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2.brd Clusterboard version 2.2 PCB Job source file]
** [https://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD%20V2.2-gerber.rar Clusterboard version 2.2 PCB Gerber file]
** [https://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2_PCB.pdf Clusterboard version 2.2 PCB Layout PDF file]
** [https://files.pine64.org/doc/clusterboard/clusterboard_20pins_header.jpg Clusterboard 20pins header definition]
** [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH56a43QTfd62c1cd96840f4ec37c60bcf12 Clusterboard 3D drawing in Fusion360]
** [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH56a43QTfd62c1cd968cd6bc203ac753401?viewState=NoIgbgDAdAjCA0ICGBmARgEwGZIOwGMBaDFADgFNCAWfAJi2o1IFZDmlTSIA2DW8-FTQgAukA Clusterboard PDF drawing]

= Linux Image Releases =

== Stock BSP ==

=== BSP Linux ver 1.1 Build from SDK ===
* Please unzip first and then using Rockchip tool to flash in
* [https://wiki.pine64.org/index.php/NOOB#Flashing_to_eMMC_using_Rockchip_Tools_.28Rock64_Only.29 Guide to flashing eMMC using Rockchip Tools]
** [http://files.pine64.org/os/SOEdge/stock/SOEdge_linux_v1.1.img.gz download from pine64.org]
** MD5 (TAR-GZip file): a6629f997ae2cae7d9d5324c4e942deda9
** File Size: 119MB

=== BSP Linux ver 1.1 Build as USB Stick application from SDK ===
* Please unzip first and then using Rockchip tool to flash in
* [https://wiki.pine64.org/index.php/NOOB#Flashing_to_eMMC_using_Rockchip_Tools_.28Rock64_Only.29 Guide to flashing eMMC using Rockchip Tools]
** [http://files.pine64.org/os/SOEdge/stock/SOEdge_linux_usb_compute_stick.img.gz download from pine64.org]
** MD5 (GZip file): af6ac45995f7ddd9343a7052efffaf30
** File Size: 47MB

== Factory Test Build ==

* Factory Test Build by Gamiee
* DD image (for 8GB microSD card or eMMC Module and above)
** [http://files.pine64.org/os/SOEdge/gamiee/update-soedge-factory-test-2021-03-23.img.gz download from pine64.org]
** MD5 (GZip file): b3d09933734eaaebb34c357b73f5c69e
** File Size: 119MB

= Linux BSP SDK =

== Linux BSP Kernel ver 1.1 ==
* [http://files.pine64.org/SDK/SOEdge/SOEdge_RK-BSP_SDK_v1.1.tar.gz Direct Download from pine64.org]
** MD5 (TAR-GZip file): a66c92e52824762d7c0a63400d6342ea
** File Size: 13.55GB

== Linux BSP Kernel ver 1.1 as USB Stick application ==
* [http://files.pine64.org/SDK/SOEdge/SOEdge_RK-BSP_USB_Dongle_SDK_v1.1.tar.gz Direct Download from pine64.org]
** MD5 (TAR-GZip file): 46f12441e8c35c06184681f355c89651
** File Size: 9.65GB

== Other Resources ==

[[Category:SOPine]] [[Category:Rockchip RK1808]]

Project Anakin

2021-09-12T18:53:31Z

Abcde: Spelling fix

= The Project "Anakin" - Phase 1 of PINE64 Smartphone "PinePhone" Development Kit =
Project Anakin is a marsh-up kit for the PINE64 Smartphone dubbed "PinePhone". It is used in the early stages of development as a starting point for affiliated projects.
PinePhone development has been broken down into three distinct phases:
* First phase - Project Anakin
* Second phase - purpose-built development kit code named "Don't be evil". It will be introduced at FOSDEM 2019
* Lastly, the third phase which is the PinePhone itself - scheduled to be released in Q3 2019 (pending on software development).

The Anakin kit consists of following components:
* SoPine Module
* SoPine Model A baseboard
* Pine A64 Wifi/BT module
* 16GB eMMC module
* 5 Mega Piixel CMOS Camera Sensor
* 7" Touch Screen LCD Panel
* Playbox Enclosure
* Lithium Ion Battery case (note: battery not included, can accommodate 1-3 pieces of 18650 size Lithium Ion batter. In general, one is good enough)
* Quectel EC20 R2.1 LTE Module (note: The SIM tray design not distinguish polarity well and all reverse slot in)

[[File:Anakin_kit_1.jpg]] [[File:Anakin_kit_2.jpg]] [[File:Anakin_kit_4.jpg]] [[File:Anakin_kit_3.jpg]]

You can also flash an OS image manually; please follow the instructions below.

= Software and OS Image Downloads =

== Arch Linux mainline build by anarsoul ==
* [https://github.com/anarsoul/linux-build/releases/latest Direct download latest release build from anarsoul github and look for archlinux-xfce-sopine-xxxxxxxx-x.img.xz]
* Login with
** User Name: alarm, Password: alarm
** User Name: root, Password: root
* please login root and execute "pacman -Syu" for latest update
* Standby feature not yet implemented

== AOSC Community mainline minimum build by icenowy ==
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]
** [https://github.com/AOSC-Dev/aosc-os-arm-bsps/tree/master/sunxi/u-boot-sun50i-a64-sopine-baseboard Icenowy's github for A64 SoC]
* Login with
** username: aosc
** password: anthon

= Mali-400 64-bit Driver =
== Mali-400 64-bit Driver [20171220] ==
* [[Mali_Driver|Mali 64-bit X11 and Wayland Driver Download]]

== Quick Links to Build Sources of OS Images ==
* [https://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix A64 mainline status matrix chart]

'''Some these OS images labelled as beta or nightly builds which means they are only fit for testing purposes

'''These images should be used at your own risk and are not fit for normal use'''

* [https://github.com/anarsoul/linux-build/releases/latest Arch Linux XFCE]
* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ longsleep BSP Linux]
* [https://github.com/ayufan-pine64/linux-build/releases/latest/ ayufan Linux]

= [[Accessories_Step_by_Step_Guides|Accessories Step-by-Step Guides]] =
Under [[Accessories_Step_by_Step_Guides|'Guides for PINE A64(+) accessories']] you can find instructions and guides concerning:
* Playbox Enclosure
* Bluetooth and WiFi module
* 7" Touch Screen LCD Panel

= SoC and Memory Specification =
* Based on Allwinner A64/R18
** '''R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor.'''
[[File:Allwinner_A64.jpg]] [[File:Allwinner_R18.png]]

== CPU Architecture ==
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core ARM Cortex-A53 Processor@1152Mhz]
* A power-efficient ARM v8 architecture
* 64 and 32bit execution states for scalable high performance
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function
* Support Large Physical Address Extensions(LPAE)
* VFPv4 Floating Point Unit
* 32KB L1 Instruction cache and 32KB L1 Data cache
* 512KB L2 cache

== GPU Architecture ==
* [https://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-400.php ARM Mali400MP2 Dual-core GPU]
* Support OpenGL ES 2.0 and OpenVG 1.1 standard

== System Memory ==
* RAM Memory Variants: 2GB LPDDR3.
* Storage Memory: SPI Flash and optional eMMC module from 16GB up to 64GB

= Project Anakin, SOPine Module and Baseboard Information, Schematics, and Certifications =
* Model "A" Baseoard Dimensions: 133mm x 80mm x 19mm
* Input Power: DC 5V @ 2A, 3.7V Li-Ion battery connector, 3.5OD/1.35ID Barrel DC Jack connector, Euler connector
* [https://wiki.pine64.org/images/7/7d/Pine64_Board_Connector.png PINE A64 Connector Layout @courtesy of norm24]
* [https://wiki.pine64.org/images/d/da/Pine64_Connector.JPG PINE A64 Connector List]
* [https://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Pin-Assignments-ver-1.0.pdf SOPine Module Pin Assignment ver 1.0]
* [https://files.pine64.org/doc/Pine%20A64%20Schematic/Pine%20A64%20Pin%20Assignment%20160119.pdf PINE A64 Pi-2/Eular/Ext Bus/Wifi Bus Connector Pin Assignment (Updated 15/Feb/2016)]
** [https://synfare.com/599N105E/hwdocs/pine64/index.html Good documentation about PINE A64, A64+, and A64-LTS GPIO pins article]
* SOPine Module Schematic:
** [https://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Schematic-ver-0.9.pdf SOPine Module Schematic]
* SOPine Model "A" Baseboard Schematic and PCB Board Resource:
** '''SOPine model "A" Baseboard is an hardware open source project but is not "OSH" compliant'''
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Baseboard%20Model%20A%20Rev%20B20170207.DSN SOPine Model "A" Baseboard Schematic capture Rev B DSN source file]
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Baseboard%20Model%20A%20Rev%20B20170207.pdf SOPine Model "A" Baseboard Schematic Rev B PDF file]
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Model%20A%20baseboard%20PCB%20layout%20PCB%20Job.tar SOPine Model "A" Baseboard PCB Job source file]
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Model%20A%20basedboard%20GERBER.tar SOPine Model "A" Baseboard PCB Gerber file]
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Model%20A%20baseboard%20PCB%20layout%20PDF.tar SOPine Model "A" Baseboard PCB Layout PDF file]
* SOPine (together with model "A" baseboard) Certification:
** [https://files.pine64.org/doc/cert/SOPine%20FCC%20certification%20VOC20170428.pdf SOPine with model "A" baseboard FCC Certificate]
** [https://files.pine64.org/doc/cert/SOPine%20CE%20certification%20VOC20170428.pdf SOPine with model "A" baseboard CE Certificate]
** [https://files.pine64.org/doc/cert/SOPine%20ROHS%20certification%20VOC20170322.pdf SOPine with model "A" baseboard RoHS Certificate]

== Datasheets for Components and Peripherals ==
* Allwinner A64/R18 SoC information:
** '''R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor.'''
** [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner-R18-Brief%20Sheet.pdf Allwinner R18 SoC Brief Introduction]
** [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64/R18 SoC Data Sheet V1.1 (Official Released Version)]
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64/R18 SoC User Manual V1.0 (Official Release Version)]
* X-Powers AXP803 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]
* LPDDR3 information:
** [https://files.pine64.org/doc/datasheet/pine64/AWL3A1632_mobile_lpddr3_1600Mbps.pdf Allwinner LPDDR3 Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/FORESEE%20178ball%2012x11.5%20LPDDR3%2016G%20Spec%20V1.0-1228.pdf Foresee LPDDR3 Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/K4E6E304EE-EGCE.pdf Samsung LPDDR3 Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/LPDDR3%20178ball%208Gb_H9CCNNN8JTALAR_Rev1.0.pdf Hynix LPDDR3 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/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf SanDisk eMMC Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/H26M64003DQR%20Datasheet.pdf Hynix eMMC Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/FORESEE_eMMC_NCEMBSF9-xxG%20SPEC%20A0%2020150730.pdf Foresee 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]
* '''Project Anakin module/component related information:'''
** 5MPixel Rear CMOS Camera module information:
*** [https://files.pine64.org/doc/datasheet/pine64/YL-PINE64-4EC.pdf PINE64 YL-PINE64-4EC 5M Pixel CMOS Image Sensor Module (Description in Chinese)]
*** [https://files.pine64.org/doc/datasheet/pine64/S5K4EC%205M%208%205X8%205%20PLCC%20%20Data%20Sheet_V1.0.pdf S5K4EC 5MP CMOS Image Sensor SoC Module Datasheet]
*** [https://files.pine64.org/doc/datasheet/pine64/S5K4ECGX_EVT1_DataSheet_R005_20100816.pdf S5K4EC 5MP CMOS Image Sensor SoC Chip Datasheet]
*** [https://files.pine64.org/doc/datasheet/pine64/s5k4ec.c S5K4EC 5MP CMOS Image Sensor Driver Source Code in C language]
** LCD Touch Screen Panel information:
*** [https://files.pine64.org/doc/datasheet/pine64/FY07024DI26A30-D_feiyang_LCD_panel.pdf 7.0" 1200x600 TFT-LCD Panel Specification]
*** [https://files.pine64.org/doc/datasheet/pine64/HK70DR2459-PG-V01.pdf Touch Panel Specification]
*** [https://files.pine64.org/doc/datasheet/pine64/GT911%20Capacitive%20Touch%20Controller%20Datasheet.pdf GOODiX GT911 5-Point Capacitive Touch Controller Datasheet]
** Lithium Battery information:

** Ethernet PHY information:
*** [https://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver for PINE A64+ Board]
*** [https://files.pine64.org/doc/datasheet/pine64/rtl8201cp.pdf Realtek RTL8201 10/100M Ethernet Transceiver for PINE A64 Board]
** Wifi/BT module information:
*** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]
** Enclosure information:
*** [https://files.pine64.org/doc/datasheet/case/playbox_enclosure_20160426.stp Playbox Enclosure 3D file]
** Connector information:
*** [https://files.pine64.org/doc/datasheet/pine64/ePH.pdf 2.0mm PH Type connector specification use in Lithium Battery (VBAT) port and RTC Battery port]
*** [https://files.pine64.org/doc/datasheet/pine64/0.5FPC%20Front%20Open%20Connector%20H=1.5.pdf 0.5mm Pitch cover type FPC connector specification use in DSI port, TP port and CSI port]
** LTE module information:
[[File:QUECTEL_EC20_Dongle-small.jpg]]
*** Note: The current Project Anakin kit deploy on using Quectel EC20_R2.1 which belongs to EC25 family. Actual production will use EC25 and EG25-G (still preliminary) module pending on region.
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC20_R2.1_LTE_Specification_V1.1.pdf Quectel EC20 R2.1 LTE Module Specification]
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_LTE_Specification_V1.4.pdf Quectel EC25 LTE Module Specification]
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EG25-G_LTE_Specification_V1.1_Preliminary_20180522%20(002).pdf Quectel EG25-G LTE Module Specification]
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25&EC21_QuecCell_AT_Commands_Manual_V1.1.pdf Quectel EC25 LTE Module AT Cammands Set Manual]
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_Hardware_Design_V1.3.pdf Quectel EC25 LTE Module Hardware Design Guide]
*** [https://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EC25_Reference_Design_Rev.D_20161111.pdf Quectel EC25 LTE Module Reference Design Guide]

= Other Resources =
* [https://linux-sunxi.org/Pine64#Manufacturer_images Linux Sunxi Wiki page on PINE A64]
* [https://github.com/apritzel/pine64 Linux Image created by Andre Przywara]
* [https://github.com/longsleep/build-pine64-image PINE64 Linux build scripts, tools and instructions by Longsleep]
* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ PINE64 Linux image by Longsleep]
* [https://softwarebakery.com/shrinking-images-on-linux Shrinking images on Linux by FrozenCow]
* [https://osmocom.org/projects/quectel-modems/wiki/EC25/24 Quectel EC-25 LTE module open source information]

[[Category:PinePhone]] [[Category:Allwinner A64]]

PINE A64-LTS

2021-09-12T18:52:12Z

Abcde: Spelling fix

[[File:PINEA64_LTS_sideimg.jpg|400px|thumb|right|The PINE A64-LTS]]
[[File:SOPINE_front.jpg|400px|thumb|right|The SOPINE A64]]

The '''PINE64-LTS''' is the long term supply version of the PINE A64 (+), ''PINE64's'' first single board computer, powered by Allwinner’s A64 quad-core ARM Cortex A53 64-Bit SoC. There are many operating systems available for the PINE A64-LTS created by the open source community and various partner projects. The PINE A64-LTS is guaranteed to be supplied until the year 2025 at the very least.

The '''SOPINE A64''' is a compute module powered by the same Quad-Core ARM Cortex A53 64-Bit Processor used in the PINE A64 with 2G LPDDR3 RAM memory, Power Management Unit, SPI Flash and integrated MicroSD Slot (for bootable OS images microSD card). The SOPINE module has a 5 years LTS (Long Term Supply) status, which means that it will be supplied to 2022 at the very least. There is a one year warranty period for the SOPINE module. This tiny compute module uses SODIMM-DDR3 form-factor and can be paired with either the Clusterboard, the Baseboard or a custom host PCB for industrial or other embedded applications. It is fully compatible with the PINE A64-LTS in terms of software support

== Software releases ==

'''Important''': The SOPine operating system images are compatible with PINE A64-LTS.

Please see [[SOPINE Software Release]] for a complete list of currently supported operating system images that work with the SOPine, as well as other related software. For a quick reference, the list includes the following operating system images:

* [[SOPINE_Software_Release#Armbian|Armbian]]
* [[SOPINE_Software_Release#AOSC|AOSC]]
* [[SOPINE Software Release#OpenEmbedded.2FYocto_Images|OpenEmbedded/Yocto]]
* [[SOPINE Software Release#OpenWRT|OpenWRT]]
* [[SOPINE Software Release#Volumio 2 Digital Audio Player|Volumio 2 Digital Audio Player]]
* [[SOPINE Software Release#FreedomBox|FreedomBox]]
* [[SOPINE Software Release#LibreELEC(KODI)|LibreELEC (KODI)]]
* [[SOPINE Software Release#NetBSD|NetBSD]]
* [[SOPINE Software Release#Android 6.x|Android 6.x]] / [[SOPINE Software Release#Android 5.x|Android 5.x]].

Below is a list of links to the build sources and environments for some operating system images. Some of themare labelled as '''beta or nightly builds''', which means they are fit for testing purposes only. Those images should be used at your own risk and are not fit for regular use.

* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ longsleep BSP Linux]
* [https://github.com/ayufan-pine64/linux-build/releases/latest/ ayufan Linux]
* [https://github.com/ayufan-pine64/android-7.1/releases/latest/ ayufan Android 7.1], [https://github.com/ayufan-pine64/android-6.0/releases/latest/ Android 6.0], and [https://github.com/ayufan-pine64/android-5.1/releases/latest/ Android 5.1]
* [https://pine64suse.weebly.com/download.html openSUSE]
* [https://dl.armbian.com/pine64so/archive/ SOPINE Armbian]
* [https://github.com/anarsoul/linux-build/releases/latest Arch Linux XFCE]
* [https://sourceforge.net/projects/openmediavault/files/Other%20armhf%20images/ OpenMediaVault]

== Accessories and Step-by-Step Guides ==

Please see [[Accessories Step by Step Guides]] for a list of guides for Pine A64 accessories; there you can find instructions and guides about the following:

* Enclosures
* Bluetooth and WiFi module
* Real Time Clock (RTC) battery
* Real Time Clock (RTC) battery holder
* First and third party cases
* Featured 3D printed cases (and more)

== SoC and Memory Specification ==
* Based on Allwinner A64/R18
** '''R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor.'''
[[File:Allwinner_A64.jpg|right]]
[[File:Allwinner_R18.png|right]]

=== CPU Architecture ===
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core ARM Cortex-A53 Processor@1152Mhz]
* A power-efficient ARM v8 architecture
* 64 and 32bit execution states for scalable high performance
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function
* Support Large Physical Address Extensions(LPAE)
* VFPv4 Floating Point Unit
* 32KB L1 Instruction cache and 32KB L1 Data cache
* 512KB L2 cache

=== GPU Architecture ===
* [https://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-400.php ARM Mali400MP2 Dual-core GPU]
* Support OpenGL ES 2.0 and OpenVG 1.1 standard

=== System Memory ===
* RAM Memory Variants: 2GB LPDDR3.
* Storage Memory: 128Mb SPI Flash and optional eMMC module from 16GB up to 128GB

== PINE A64-LTS Board Features ==
[[File:PINEA64 LTS board front.jpg|thumb|400px|Front view of a Pine A64-LTS board]]
[[File:PINEA64 LTS board back.jpg|thumb|400px|Rear view of a Pine A64-LTS board]]

=== Video ===
* Digital Video (Type A - full)

=== Audio ===
* 3.5mm stereo earphone/microphone plug

=== Network ===
* 10/100/1000Mbps Ethernet(PINE A64+ version), 10/100Mbps Ethernet(PINE A64 version)
* WiFi 802.11 b/g/n with Bluetooth 4.0 (optional)

=== Storage ===
* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* USB - 2 USB2.0 Host port

=== Expansion Ports ===
* DSI - Display Serial Interface, 4 lanes MiPi, up to 1080P
* CSI - CMOS Camera Interface up to 5 mega pixel
* TP - Touch Panel Port, SPI with interrupt
* RTC - Real Time Clock Battery Connector
* VBAT - Lithium Battery Connector with temperature sensor input
* Wifi/BT Module Header - SDIO 3.0 and UART
* 2x20 pins "Pi2" GPIO Header
* 2x17 pins "Euler" GPIO Header
* 2x5 pins "EXP" Console Header

== Pine A64-LTS, SOPine Module and Baseboard Information, Schematics, and Certifications ==
[[File:SOPINE Baseboard front.jpg|thumb|400px|Front view of a SOPine Baseboard]]
[[File:SOPINE front.jpg|thumb|400px|Front view of a SOPine module]]
[[File:SOPINE back.jpg|thumb|400px|Rear view of a SOPine module]]

* Model "A" Baseboard Dimensions: 133mm x 80mm x 19mm
* Input Power: DC 5V @ 2A, 3.7V Li-Ion battery connector, 3.5OD/1.35ID Barrel DC Jack connector, Euler connector
* [https://wiki.pine64.org/images/7/7d/Pine64_Board_Connector.png PINE A64 Connector Layout @courtesy of norm24]
* [https://wiki.pine64.org/images/d/da/Pine64_Connector.JPG PINE A64 Connector List]
* [https://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Pin-Assignments-ver-1.0.pdf SOPine Module Pin Assignment ver 1.0]
* [https://forum.pine64.org/showthread.php?tid=8058 a PDF mapping the pins from the A64 chip itself, to the gold-fingers on the SO-DIMM edge, to the multiple connectors on the baseboard and on the clusterboard, attached to this forum post.]
* [https://files.pine64.org/doc/Pine%20A64%20Schematic/Pine%20A64%20Pin%20Assignment%20160119.pdf PINE A64 Pi-2/Eular/Ext Bus/Wifi Bus Connector Pin Assignment (Updated 15/Feb/2016)]
** [https://synfare.com/599N105E/hwdocs/pine64/index.html Good documentation about PINE A64, A64+, and A64-LTS GPIO pins article]
* Pine A64-LTS Schematic:
** [https://files.pine64.org/doc/SOPINE-A64/PINE%20A64-TLS-20180130.pdf Pine A64-LTS Schematic]
* SOPine Module Schematic:
** [https://files.pine64.org/doc/SOPINE-A64/SOPINE-A64-Schematic-ver-0.9.pdf SOPine Module Schematic]
* SOPine Model "A" Baseboard Schematic and PCB Board Resource:
** '''SOPine model "A" Baseboard is an hardware open source project but is not "OSH" compliant'''
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Baseboard%20Model%20A%20Rev%20B20170207.DSN SOPine Model "A" Baseboard Schematic capture Rev B DSN source file]
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Baseboard%20Model%20A%20Rev%20B20170207.pdf SOPine Model "A" Baseboard Schematic Rev B PDF file]
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Model%20A%20baseboard%20PCB%20layout%20PCB%20Job.tar SOPine Model "A" Baseboard PCB Job source file]
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Model%20A%20basedboard%20GERBER.tar SOPine Model "A" Baseboard PCB Gerber file]
** [https://files.pine64.org/doc/SOPINE-A64/SOPine%20Model%20A%20baseboard%20PCB%20layout%20PDF.tar SOPine Model "A" Baseboard PCB Layout PDF file]
* PINE A64-LTS / SOPine Wifi/BT module Schematic
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf PINE A64 Wifi/BT Module Schematic]
* PINE A64-LTS / SOPine Stereo Audio Dac Board Schematic
**[https://forum.pine64.org/attachment.php?aid=697 PINE A64-LTS / SOPine Stereo Audio Dac Board Schematic]
* SOPine (together with model "A" baseboard) Certification:
** Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submits the SBC for FCC, CE, and ROHS certifications and obtain the certificates to prove that the SBC board can pass the testing. Please note, a final commercial product needs to perform its own testing and obtain its own certificate.
** [https://files.pine64.org/doc/cert/SOPine%20FCC%20certification%20VOC20170428.pdf SOPine with model "A" baseboard FCC Certificate]
** [https://files.pine64.org/doc/cert/SOPine%20CE%20certification%20VOC20170428.pdf SOPine with model "A" baseboard CE Certificate]
** [https://files.pine64.org/doc/cert/SOPine%20ROHS%20certification%20VOC20170322.pdf SOPine with model "A" baseboard RoHS Certificate]

== Datasheets for Components and Peripherals ==
* Allwinner A64/R18 SoC information:
** '''R18 and A64 are identical SoC but R18 committed for 10 years supply by vendor.'''
** [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner-R18-Brief%20Sheet.pdf Allwinner R18 SoC Brief Introduction]
** [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64/R18 SoC Data Sheet V1.1 (Official Released Version)]
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64/R18 SoC User Manual V1.0 (Official Release Version)]
* X-Powers AXP803 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]
* LPDDR3 information:
** [https://files.pine64.org/doc/datasheet/pine64/AWL3A1632_mobile_lpddr3_1600Mbps.pdf Allwinner LPDDR3 Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/FORESEE%20178ball%2012x11.5%20LPDDR3%2016G%20Spec%20V1.0-1228.pdf Foresee LPDDR3 Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/K4E6E304EE-EGCE.pdf Samsung LPDDR3 Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/LPDDR3%20178ball%208Gb_H9CCNNN8JTALAR_Rev1.0.pdf Hynix LPDDR3 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]
* '''PINE A64, PINE A64+, PINE A64-LTS and SOPINE Related:'''
** 5MPixel CMOS Camera module information:
*** [https://files.pine64.org/doc/datasheet/pine64/YL-PINE64-4EC.pdf PINE64 YL-PINE64-4EC 5M Pixel CMOS Image Sensor Module (Description in Chinese)]
*** [https://files.pine64.org/doc/datasheet/pine64/S5K4EC%205M%208%205X8%205%20PLCC%20%20Data%20Sheet_V1.0.pdf S5K4EC 5MP CMOS Image Sensor SoC Module Datasheet]
*** [https://files.pine64.org/doc/datasheet/pine64/S5K4ECGX_EVT1_DataSheet_R005_20100816.pdf S5K4EC 5MP CMOS Image Sensor SoC Chip Datasheet]
*** [https://files.pine64.org/doc/datasheet/pine64/s5k4ec.c S5K4EC 5MP CMOS Image Sensor Driver Source Code in C language]
*** Early version Camera module information:
**** [https://files.pine64.org/doc/datasheet/pine64/D116-A64_Bonsen_cmos_camera.pdf Bonsen Kexin V118-A64-GC2145-HM5065 CMOS Image Sensor Module]
**** [https://files.pine64.org/doc/datasheet/pine64/HM5065-DS-V03.pdf HiMax 5MP CMOS Image Sensor SoC]
** LCD Touch Screen Panel information:
*** [https://files.pine64.org/doc/datasheet/pine64/FY07024DI26A30-D_feiyang_LCD_panel.pdf 7.0" 1200x600 TFT-LCD Panel Specification]
*** [https://files.pine64.org/doc/datasheet/pine64/HK70DR2459-PG-V01.pdf Touch Panel Specification]
*** [https://files.pine64.org/doc/datasheet/pine64/GT911%20Capacitive%20Touch%20Controller%20Datasheet.pdf GOODiX GT911 5-Point Capacitive Touch Controller Datasheet]
** Lithium Battery information:
*** [https://files.pine64.org/doc/datasheet/pine64/9070120P%203.7V%208000MAH.pdf 8000mAH Lithium Battery Specification]
** Ethernet PHY information:
*** [https://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver for PINE A64-LTS Board and SOPine Baseboard]
** Wifi/BT module information:
*** [https://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf PINE A64 Wifi/BT Module Schematic]
*** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]
** Enclosure information:
*** [https://files.pine64.org/doc/datasheet/case/playbox_enclosure_20160426.stp Playbox Enclosure 3D file]
*** [https://files.pine64.org/doc/datasheet/case/ABS_enclosure_20160426.stp ABS Enclosure 3D file]
*** [https://files.pine64.org/doc/datasheet/case/pine64%20Die%20Cast%20casing-final.jpg Outdoor Aluminum Cast Dust-proof IP67 Enclosure Drawing]
** Connector information:
*** [https://files.pine64.org/doc/datasheet/pine64/ePH.pdf 2.0mm PH Type connector specification use in Lithium Battery (VBAT) port and RTC Battery port]
*** [https://files.pine64.org/doc/datasheet/pine64/0.5FPC%20Front%20Open%20Connector%20H=1.5.pdf 0.5mm Pitch cover type FPC connector specification use in DSI port, TP port and CSI port]
** Remote control button mapping
*** [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE A64 Button Mapping]

== Pine A64 POT ==
* [[POT|PINE A64 Peripheral On Top (POT) and Related Devices]]
* [[Wifi_Remote_I2c|WiFi Remote I2c Quick Start Guide]]

== Other Resources ==
* [https://linux-sunxi.org/Pine64#Manufacturer_images Linux Sunxi Wiki page on PINE A64]
* [https://github.com/umiddelb/z2d/tree/master/pine64 Collection of scripts to set up a minimal Xenial 14.04.3 / Debian 8 Jessie root filesystem Contributed By Uli Middelberg]
* [https://github.com/apritzel/pine64 Linux Image created by Andre Przywara]
* [https://blog.hypriot.com/post/the-pine-a64-is-about-to-become=the-cheapest-ARM-64-bit-platform-to-run-Docker/ PINE A64 with HypriotOS by Dieter and Govinda]
* [https://sosfakeflash.wordpress.com/2008/09/02/h2testw-14-gold-standard-in-detecting-usb-counterfeit-drives/comment-page-3/#comment-9861 H2testw 1.4 – Gold Standard In Detecting USB Counterfeit Drives]
* [https://oss.digirati.com.br/f3/ F3 - an alternative to h2testw]
* [https://www.phoronix.com/scan.php?page=article&item=pine-64-benchmark&num=1 Benchmarking The Low-Cost PINE 64+ ARM Single Board Computer by Michael Larabel]
* [https://github.com/longsleep/build-pine64-image PINE64 Linux build scripts, tools and instructions by Longsleep]
* [https://www.stdin.xyz/downloads/people/longsleep/pine64-images/ PINE64 Linux image by Longsleep]
* [https://www.youtube.com/playlist?list=PLgj96wTPcMKffRm_Sk6673Nfy_I6b5UJW A series of Youtube video on PINE A64 Developers Board by Michael Larson]
* [https://rayhightower.com/blog/2016/04/04/pine64-quick-start-guide-using-mac-os-x/ PINE64 Quick Start Guide (with Gotchas)]
* [https://softwarebakery.com/shrinking-images-on-linux Shrinking images on Linux by FrozenCow]
* [https://gitlab.manjaro.org/packages/community/manjaro-arm-installer Manjaro Arm installation script]

[[Category:SOPine]] [[Category:A64-LTS]] [[Category:Allwinner A64]]

SOEDGE

2021-09-12T18:50:13Z

Abcde: Clarity fix for clusterboard info

[[File:SOEdge.png|400px|thumb|right|The SOEdge]]

The '''SOEdge''' is a 3TOPS compute module that can be paired with the SOPine base board or USB 3.0 and PCIe adapters for development. It can connect to a SBC, such as the ROCKPro64 or a regular PC.

== Software releases ==

The SOEdge software releases can be found in the article [[SOEdge Software Releases]].

== Accessories Step-by-Step Guides ==
Under [[Accessories_Step_by_Step_Guides|'Guides for model A baseboard accessories']] you can find instructions and guides concerning:
* Enclosures
* Bluetooth and WiFi module
* Real Time Clock (RTC) battery
* Real Time Clock (RTC) battery holder
* First and third party cases
* Featured 3D printed cases (and more)

== SoC and Memory Specification ==
* Based on [https://www.rock-chips.com/a/en/products/RK18_Series/2019/0529/989.html Rockchip RK1808]
[[File:RK1808_icon.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/ip-products/processors/cortex-a/cortex-a35 Dual-core ARM Cortex-A35 Processor@1600-2000Mhz]
* A power-efficient ARM 64-Bit Armv8-A architecture
* AArch32 for full backward compatibility with Armv7
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function
* Support Large Physical Address Extensions(LPAE)
* VFPv4 Floating Point Unit
* 32KB L1 Instruction cache and 32KB L1 Data cache
* AArch64 for 64-bit support and new architectural features
* TrustZone security technology
* Neon Advanced SIMD
* DSP and SIMD extensions
* VFPv4 Floating point
* Hardware virtualization support
* 128KB L2 cache

=== Neural Process Unit NPU Capability ===
* [https://www.verisilicon.com/en/IPPortfolio/VivanteNPUIP NPU IP from Verisilicon Vivante]
* Support max 1920 Int8 MAC operation per cycle
* Support max192 Int16 MAC operation per cycle
* Support max 64 FP16 MAC operation per cycle
* 512KB internal buffer
* One isolated voltage domain to support DVFS
* [https://github.com/VeriSilicon/acuity-models Acuity models Github]

[[File:Vivante_Acuity_SDK.jpg]]

=== System Memory ===
* RAM Memory Variants: 2GB DDR4.
* Storage Memory: 128Mb SPI Flash and optional eMMC module from 16GB up to 128GB

== SOEdge Baseboard Features ==

=== Network ===
* 10/100/1000Mbps Ethernet
* WiFi 802.11 b/g/n with Bluetooth 4.0 (optional)

=== Storage ===
* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* USB - 2 USB2.0 Host port

=== Expansion Ports ===
* DSI - Display Serial Interface, 4 lanes MiPi, up to 1080P
* TP - Touch Panel Port, SPI with interrupt
* RTC - Real Time Clock Battery Connector
* VBAT - Lithium Battery Connector with temperature sensor input
* Wifi/BT Module Header - SDIO 3.0 and UART
* 2x20 pins "Pi2" GPIO Header
* PCIe 2x open ended slot

== SOEdge Module and Baseboard Information, Schematics, and Certifications ==
* Model "A" Baseboard Dimensions: 133mm x 80mm x 19mm
* Input Power: DC 12V @ 3A 5.5OD/2.1ID Barrel DC Jack connector

* SOEdge Module Schematic:
** [https://files.pine64.org/doc/SOEdge/SOEdge-Schematic-v2.0-190919.pdf SOEdge Module ver 2.0 20190919 Schematic]
** [https://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-topplace.pdf SOEdge Module ver 2.0 20190919 PCB Component Placement Top PDF file]
** [https://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-bottomplace.pdf SOEdge Module ver 2.0 20190919 PCB Component Placement Bottom PDF file]
** [https://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-topplace.dxf SOEdge Module ver 2.0 20190919 PCB Component Placement Top Drawing file]
** [https://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-bottomplace.dxf SOEdge Module ver 2.0 20190919 PCB Component Placement Bottom Drawing file]
** [https://files.pine64.org/doc/SOEdge/SOEdge%20Pin%20Assignments%20ver%201.00.xlsx SOEdge Module Pin Assignment ver 1.0 in Excel format(includes comparison chart to SOPine)]
** [https://files.pine64.org/doc/SOEdge/SOEdge%20Pin%20Assignments%20ver%201.00.ods SOEdge Module Pin Assignment ver 1.0 in Open Document format(includes comparison chart to SOPine)]
* SOEdge Model "A" Baseboard Schematic and PCB Board Resource:
** [https://files.pine64.org/doc/SOEdge/SOEDGE_MODEL_A_BASEBOARD_Schematic-20210223.pdf SOEdge Model "A" Baseboard Schematic 20210223 PDF file]
** [https://files.pine64.org/doc/SOEdge/SOEDGE_MODEL_A_BASEBOARD_PCB-TOP-20210223.pdf SOEdge Model "A" Baseboard 20210223 PCB Component Placement Top PDF file]
** [https://files.pine64.org/doc/SOEdge/SOEDGE_MODEL_A_BASEBOARD_PCB-BOT-20210223.pdf SOEdge Model "A" Baseboard 20210223 PCB Component Placement Bottom PDF file]
* SOEdge Neural AI Stick Schematic:
** [https://files.pine64.org/doc/SOEdge/SOEdge%20Neural%20AI%20Stick%20Schematic_V10.pdf SOEdge Neural AI Stick PDF file]
* SOEdge/SOPine/PINE A64 Wifi/BT module Schematic
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf PINE A64 Wifi/BT Module Schematic]
* SOEdge module together with model "A" baseboard Certification:
** Disclaimer: Please note that SOEdge module is not a "final" product and in general certification is not necessary. However, SOEdge module still submits the mpdel A baseboard for FCC, CE, and ROHS certifications and obtain the certificates to prove that can pass the testing. Please note, a final commercial product needs to perform its own testing and obtain its own certificate.
** Not yet available

== Datasheets for Components and Peripherals ==
* Rockchip RK1808 SoC information:
** [http://opensource.rock-chips.com/images/4/43/Rockchip_RK1808_Datasheet_V1.2_20190527.pdf Rockchip RK1808 ver 1.2 datasheet]
** [https://files.pine64.org/doc/datasheet/SOEdge/Rockchip%20RK1808%20TRM%20Part1%20V1.2--20190826%20open%20source.pdf Rockchip TK1808 Technical Reference Manual Part 1]
* Rockchip RK809 PMU (Power Management Unit) information:
** [https://rockchip.fr/RK809%20datasheet%20V1.01.pdf Rockchip RK809 PMIC Datasheet]
* DDR4 information:
** [https://files.pine64.org/doc/datasheet/SOEdge/Micron%208Gb_DDR4_SDRAM.pdf Micron DDR4 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]
* '''SOEdge Related:'''
** LCD Touch Screen Panel information:
*** [https://files.pine64.org/doc/datasheet/pine64/FY07024DI26A30-D_feiyang_LCD_panel.pdf 7.0" 1200x600 TFT-LCD Panel Specification]
*** [https://files.pine64.org/doc/datasheet/pine64/HK70DR2459-PG-V01.pdf Touch Panel Specification]
*** [https://files.pine64.org/doc/datasheet/pine64/GT911%20Capacitive%20Touch%20Controller%20Datasheet.pdf GOODiX GT911 5-Point Capacitive Touch Controller Datasheet]
** Ethernet PHY information:
*** [https://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver for SOEdge model A baseboard]
** Wifi/BT module information:
*** [https://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf SOEdge/SOPine/PINE A64 Wifi/BT Module Schematic]
*** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]
** Enclosure information:
*** [https://files.pine64.org/doc/datasheet/case/playbox_enclosure_20160426.stp Playbox Enclosure 3D file]
*** [https://files.pine64.org/doc/datasheet/case/ABS_enclosure_20160426.stp ABS Enclosure 3D file]
*** [https://files.pine64.org/doc/datasheet/case/pine64%20Die%20Cast%20casing-final.jpg Outdoor Aluminum Cast Dust-proof IP67 Enclosure Drawing]
** Connector information:
*** [https://files.pine64.org/doc/datasheet/pine64/ePH.pdf 2.0mm PH Type connector specification use in Lithium Battery (VBAT) port and RTC Battery port]
*** [https://files.pine64.org/doc/datasheet/pine64/0.5FPC%20Front%20Open%20Connector%20H=1.5.pdf 0.5mm Pitch cover type FPC connector specification use in DSI port, TP port and CSI port]

== SOEdge/SOPine Cluster Board Resource ==
* Cluster board is an hardware open source project and is available at the PINE64 store since late January 2018. It allows 7 SOPine or SOEdge devices to be installed simultaneously.
* Please note that this project is not "OSH" compliance.:
** [https://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2.DSN Clusterboard version 2.2 Schematic Capture source file]
** [https://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2_Schematic.pdf Clusterboard version 2.2 Schematic Capture PDF file]
** [https://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2.brd Clusterboard version 2.2 PCB Job source file]
** [https://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD%20V2.2-gerber.rar Clusterboard version 2.2 PCB Gerber file]
** [https://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2_PCB.pdf Clusterboard version 2.2 PCB Layout PDF file]
** [https://files.pine64.org/doc/clusterboard/clusterboard_20pins_header.jpg Clusterboard 20pins header definition]
** [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH56a43QTfd62c1cd96840f4ec37c60bcf12 Clusterboard 3D drawing in Fusion360]
** [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH56a43QTfd62c1cd968cd6bc203ac753401?viewState=NoIgbgDAdAjCA0ICGBmARgEwGZIOwGMBaDFADgFNCAWfAJi2o1IFZDmlTSIA2DW8-FTQgAukA Clusterboard PDF drawing]

= Linux Image Releases =

== Stock BSP ==

=== BSP Linux ver 1.1 Build from SDK ===
* Please unzip first and then using Rockchip tool to flash in
* [https://wiki.pine64.org/index.php/NOOB#Flashing_to_eMMC_using_Rockchip_Tools_.28Rock64_Only.29 Guide to flashing eMMC using Rockchip Tools]
** [http://files.pine64.org/os/SOEdge/stock/SOEdge_linux_v1.1.img.gz download from pine64.org]
** MD5 (TAR-GZip file): a6629f997ae2cae7d9d5324c4e942deda9
** File Size: 119MB

=== BSP Linux ver 1.1 Build as USB Stick application from SDK ===
* Please unzip first and then using Rockchip tool to flash in
* [https://wiki.pine64.org/index.php/NOOB#Flashing_to_eMMC_using_Rockchip_Tools_.28Rock64_Only.29 Guide to flashing eMMC using Rockchip Tools]
** [http://files.pine64.org/os/SOEdge/stock/SOEdge_linux_usb_compute_stick.img.gz download from pine64.org]
** MD5 (GZip file): af6ac45995f7ddd9343a7052efffaf30
** File Size: 47MB

== Factory Test Build ==

* Factory Test Build by Gamiee
* DD image (for 8GB microSD card or eMMC Module and above)
** [http://files.pine64.org/os/SOEdge/gamiee/update-soedge-factory-test-2021-03-23.img.gz download from pine64.org]
** MD5 (GZip file): b3d09933734eaaebb34c357b73f5c69e
** File Size: 119MB

= Linux BSP SDK =

== Linux BSP Kernel ver 1.1 ==
* [http://files.pine64.org/SDK/SOEdge/SOEdge_RK-BSP_SDK_v1.1.tar.gz Direct Download from pine64.org]
** MD5 (TAR-GZip file): a66c92e52824762d7c0a63400d6342ea
** File Size: 13.55GB

== Linux BSP Kernel ver 1.1 as USB Stick application ==
* [http://files.pine64.org/SDK/SOEdge/SOEdge_RK-BSP_USB_Dongle_SDK_v1.1.tar.gz Direct Download from pine64.org]
** MD5 (TAR-GZip file): 46f12441e8c35c06184681f355c89651
** File Size: 9.65GB

== Other Resources ==

[[Category:SOPine]] [[Category:Rockchip RK1808]]

User talk:Abcde

2021-06-20T09:29:29Z

Abcde: clean bygones

PineTab

2021-02-12T18:35:24Z

Abcde: /* Manjaro ARM */ Removed non functioning link, and clarified current status of images.

{{warning|1=IMPORTANT INFORMATION for '''Early Adopters''' - please [[PineTab/Early-Adopter|'''CLICK HERE''']] - some '''known issues''' are listed there}}

The PineTab is a 10" tablet created by Pine64.

== Specifications ==
* '''Dimensions:''' 11mm x 175mm x 260mm (Thickness, Width, Height)
* '''Weight:''' 575g (Tablet alone)
* '''Build:''' Plastic
* '''Storage:'''
** 64GB of internal eMMC storage
** MicroSD slot, bootable
** M.2 SSD slot, supports SATA and USB devices only, not NVME (optional)
* '''Cameras:''' 2Mpx Front, 5Mpx Rear
* '''SOC:''' Allwinner A64 Quad Core
* '''CPU:''' 4x ARM A53 1.152GHz
* '''GPU:''' Mali 400 MP2
* '''RAM:''' 2GB LPDDR3
* '''I/O:''' HD Video Out (Mini HDMI), Micro USB 2.0 OTG, USB 2.0 A host, 3.5mm Headphone/Mic combo,
* '''Network:'''
** WiFi (802.11b/g/n, 2.4GHz only)
** Bluetooth 2.1
** M.2 LTE / Cell MODEM card, (optional, and takes place of optional M.2 SSD)
* '''Display:'''
** '''Size:''' 10.1 inches (257mm) diagonal
** '''Type:''' HD IPS capacitive touchscreen, 16M colors
** '''Resolution:''' 1280x800, 16:10 ratio 
* '''Attachments/Accessories:''' Magnetically attached keyboard (optional)
* '''Battery:''' 6000MAh (6Ah)
* '''Misc. features:'''
** Volume rocker and home button
** Speakers and Microphone
** 2.5mm OD 0.7mm ID DC Jack Power (5V 2A) Port

== Keyboard ==
'''Overview:''' The PineTab detachable keyboard features a full function row, FN key functionality, meta key (where the Windows key would be) and all of the keys you need for daily use.

'''FN keys:''': Pause/play (F2), Stop (F3), Previous(F4), Next(F5), Music (F6), Mail (F7), Home (F8), Mute (F9), Vol- (F10), Vol+ (F11), Disable touchpad (F12), NumLock (Insert), Scroll Lock (Delete), PgUp (Up Arrow), PgDn (Down Arrow), Home (Left Arrow), End (Right Arrow), Digital Numpad (7,8,9,0,U,I,O,P,J,K,L,;,M,.,/)

==Versions==
* "pinetab-dev": development version sent to ~100 developers. This one is like the Early Adopter version, but has a different display panel.
* [[PineTab/Early-Adopter|Early Adopter]]: the first hardware revision of the PineTab, which shipped to customers.

[[File:PineTabBoard.jpeg|400px|thumb|right|The insides of the PineTab]]

== PineTab board information, schematics and certifications ==
* PineTab mainboard schematic:
** [https://files.pine64.org/doc/PineTab/PineTab%20Schematic%20v1.2-20191125.pdf PineTab mainboard Released Schematic ver 1.2]
** [https://files.pine64.org/doc/PineTab/PineTab%20Board%20View%20v1.2-20191201-top.pdf PineTab mainboard component placement ver 1.2 - Top View]
** [https://files.pine64.org/doc/PineTab/PineTab%20Board%20View%20v1.2-20191201-bottom.pdf PineTab mainboard component placement ver 1.2 - Bottom View]
* PineTab keyboard schematic:
** PineTab keyboard and Pinebook (Pro) keyboard using same controller and from same engineering source
** [https://files.pine64.org/doc/PineTab/Pinetab%20HB092A%20Keyboard%20Schematic.pdf PineTab Keyboard Schematic]
** [https://files.pine64.org/doc/PineTab/HB092_0884232458_Hynitron_PTP_20200514_662905_Linux_US_BackLight_CRC_175057F5.hex PineTab keyboard firmware code]
** [https://files.pine64.org/doc/PineTab/SH68F83V2.0.pdf PineTab Keyboard Controller Datasheet]

* PineTab certifications:
** [https://files.pine64.org/doc/cert/PineTab%20FCC-SDOC%20Certificate-S20060600404001.pdf PineTab FCC Certificate]
** [https://files.pine64.org/doc/cert/PineTab%20CE-RED%20Certificate-S20060600403.pdf PineTab CE RED Certificate]
** [https://files.pine64.org/doc/cert/PINETAB%20ROHS%20TEST%20REPORT.pdf PineTab ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner A64 SoC information:
** [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC brief introduction]
** [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]

* X-Powers AXP803 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC datasheet]

* LPDDR3 (178 Balls) SDRAM:
** [https://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf Artmem LPDDR3 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/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 64GB SanDisk eMMC Datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module datasheet]
** [https://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module datasheet]

* LCD touch screen panel information:
** [https://files.pine64.org/doc/datasheet/pinetab/GT9271.pdf GOODiX GT9271 Capacitive Touch Controller datasheet]
** [https://files.pine64.org/doc/datasheet/pinetab/GT9271_Config_20200818_142030_V66.cfg PineTab GT9271 Capacitive Touch Controller configuration file]

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723BS/RTL8723CS specification]

== Operating Systems ==
The PineTab will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distro (because the PineTab uses the mainline kernel), only few of them will actually be usable on Early Adopters PineTab, due to specifics of working with LCD panel. Among those listed all except for postmarketOS have working builds.

=== UBPorts ===
[[File:Ubports-logo.png|100px]]
The UBPorts Ubuntu Touch is what was preinstalled on the PineTab Early Adopters batch.

It can update itself in System Settings, and also a jenkins daily build can be downloaded at this updated address for the latest daily image:

https://ci.ubports.com/job/rootfs/job/rootfs-pinetab-systemimage/

The last stable builds are also listed and appear to be updated every few weeks.

It should be noted that as of 20th January the latest stable/release candidate and development builds still lacked Bluetooth, Rotation and had the same issues with online accounts etc

Online accounts access have a fix for Google accounts here https://github.com/rubencarneiro/account-plugins/releases

There are however significant updates to the original pinetab image (without the issues above)

The old image appears to be deprecated here
[https://ci.ubports.com/job/rootfs/job/rootfs-pinetab/ here]

In the event that WiFi fails to connect, the USB port can be used with an appropriate dongle to connect for internet using ethernet cable.

=== postmarketOS ===
[[File:PostmarketOS-logo.png|100px]]
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices.

It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...), and allows to encrypt your installation.

As of writing, postmarketOS supports the "pinetab-dev" and the Early Adopters versions of the PineTab.

The latest images can be downloaded [https://images.postmarketos.org/pinetab/ here], or you can refer to the [https://wiki.postmarketos.org/wiki/PINE64_PineTab_(pine64-pinetab) PineTab wiki page] for installation instructions.

=== Arch Linux ARM ===
[[File:Archlinux-logo.png|100px]]
Arch Linux ARM with Phosh as the UI selection, maintained by the DanctNIX community.

The latest image can be downloaded [https://github.com/dreemurrs-embedded/Pine64-Arch/releases here]

=== Manjaro ARM ===
[[File:Manjaro-logo.svg|100px]]
The PineTab "Early Adopter" edition is currently not supported by ManjaroARM.

Older Manjaro images with several different environments, including Phosh and Plasma, are available for the "Dev" pre-release but '''not working on "Early Adopters" PineTab''' can be downloaded [https://osdn.net/projects/manjaro-arm/storage/pinetab/ here]

=== Mobian ===
[[File:Debian-logo.png|100px]]
Mobian is a project providing Debian images for mobile devices.

PineTab images can be downloaded [https://images.mobian-project.org/pinetab/ here]. Password is '''1234'''

=== Sailfish OS ===

[[File:SailfishOS logo.png|100px]]

There is an early Alpha build available here thanks to PeperJohnny: https://forum.pine64.org/member.php?action=profile&uid=15246

http://peperjohnny.org/dl/sfos_alpha2.img.gz

There is a forum discussion with a description on how to compile and build your own here:

http://forum.pine64.org/showthread.php?tid=11850

Many things are still broken but Bluetooth, Audio, Rotation and Keyboard are working on the 2nd Alpha

== Installation instructions ==
For instructions on how to install the operating systems to the eMMC or microSD card see [[PinePhone Installation Instructions]]. The information is almost the same for the PineTab, as it is a very similar device. Do not try to use the PinePhone images though, use the PineTab images linked above.

=== Testing ===
To test an OS, just flash its image onto an microSD card, plug it into PineTab, and reboot.
Note that USB stick won't work.
Also note that you need to "flash", not just copy the file onto the card.
Also remember that you need to unpack image file if it's packed!

You can do it using Ubuntu Touch installed on the PineTab! For now, only Mobian is supported by the guide below.

* First, make sure you have enough free disk space and empty Downloads directory on the PineTab (while not strictly necessary, empty Downloads dir will simplify your typing. You can just move all files from there to another directory).
* Turn off Sleep when idle in the settings. Settings > Battery > Sleep when idle: Never
* Go to the Mobian link above and download compressed image (the one ending with .img.gz) - usual recommendation is to download latest, i.e. lowest one.
* Open terminal and type this in it:
cd Downloads
ls
* It should show you the name of the file you've just downloaded
* This file is compressed, so first you need to uncompress it. Type this into terminal:
gunzip *.gz && echo done
* This command will take some time (you won't see any progress until it's done). It either will succeed (and print "done") and fail (and print why).
* Now, let's have a look at disks. Type this into terminal:
lsblk
* It should show you a tree of disks and their partitions. If you don't have microSD card inserted yet, all of them begin with mmcblk2. Also, some of them have something in the "MOUNTPOINT" column
* Insert microSD card into PineTab. Note that all information on it will be deleted, so don't insert one with valuable information on it!
* type `lsblk` into terminal again.
* Note that now tree of disks has one or more new entries - starting with mmcblk0 - that's partitions of your microSD card.
* Confirm that size of mmcblk0 is close to size of the microSD card, and all lines starting with mmcblk0 have empty "MOUNTPOINT" column.
* now type this:
sudo dd if=`ls` of=/dev/mmcblk0 bs=1M status=progress
* It will take some time, depending on speed of your microSD card and size of image file
* Now, reboot your PineTab - type this into terminal:
sudo reboot
* PineTab should boot from the microSD you've just flashed

== Tips and tricks ==

=== Reset ===

If your PineTab is in unknown state or doesn't want to start.
Press power button for 7-8s. It makes a sound and you know it's totally off. 3 seconds after, power button again for 2-3s and it will start to boot. - thanks
@Aperricio on IRC for this hint

=== Display rotated 90° on Arch ARM ===
With the following command you can turn the display to landscape:

* echo 1 | sudo tee /sys/class/graphics/fbcon/rotate

This command does not persist a reboot.

[[Category:PineTab]] [[Category:Allwinner A64]]

Pinecil

2021-01-23T14:12:34Z

Abcde: It is a wiki

== Overall description ==
[[File:Pinecil-bb2-01_rotate.jpg]] 
The Pinecil is a portable, temperature controlled soldering iron. It also has the intended use of being a Risc-V development device using a breakout board. It's main features are:

* Portability
* Settable temperature
* Soldering tips:
** Replaceable
** More than half a dozen available. Currently sold as 2 separate sets of 4, one fine set, the other larger.
** Compatible with TS100
* Flexible power sources:
** Barrel jack
** USB Type C power delivery

There are additional features that include (Useful for devkit use):

* A Programmable Gigadevice Risc-V GD32V embedded processor
* 0.67" Monochrome Display that can render text or graphics
* Support for Idle detection, for automatic power down of tip

== Pictures ==

Pre-release:
<gallery>
File:Pinecil_Exploded_Diagram_ver_0.9.png|Pinecil renders|alt=alt language
File:PinecilPrototype.jpg|Pinecil prototype|alt=alt language
</gallery>

Production:
<gallery>
File:Pinecil-bb2-01.jpg|Pinecil and TS-B2 retail package|alt=alt language
File:Pinecil-Case-Red-1.jpg|Pinecil red casing|alt=alt language
</gallery>

== Pinecil tips ==
* Uses TS-100 compatible tips
* Tip model TS-B2 is the default tip supplied with the Pinecil
* Tip set 1 (left) & 2 (right): 
[[File:PinecilTipSets.jpg|800px]]

== Specifications ==
* '''Dimensions:''' 170mm with solder tip or 98mm without solder tip x 12.8mm x 16.2mm
* '''Weight:''' 30g with solder tip, 20g without solder tip
* '''CPU:''' GD32VF103TB 32-bit RV32IMAC RISC-V “Bumblebee Core” @ 108 MHz
* '''Display:''' 0.67" QUG 9616TSWCG02 96x16 Monochrome Matrix display
* '''Memory:'''
** 128KB Flash
** 32KB SRAM
* '''DC in (only one of the following at a time):'''
** 12V- 24V DC5525 Barrel Jack
** USB-C 12-20V PD
** QC3.0
** Recommend operating voltage 12-21V, maximum rating at 24V

== Pinecil board information, schematics and certifications ==

* Pinecil mainboard schematic:
** [https://files.pine64.org/doc/Pinecil/Pinecil_schematic_v1.0a_20201120.pdf Pinecil mainboard schematic ver 1.0 20201120, this is production version schematic]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Top PDF file]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Bottom PDF file]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Top Drawing file]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Bottom Drawing file]

* Pinecil certifications:
** [https://files.pine64.org/doc/cert/Pinecil%20CE%20RED%20Certificate-S20102803801001.pdf Pinecil CE RED Certificate]
** [https://files.pine64.org/doc/cert/Pinecil%20FCC%20Certificate-S20102803802001.pdf Pinecil FCC Certificate]
** [https://files.pine64.org/doc/cert/Pinecil%20RoHS10%20Certificate-S20102803803001.pdf Pinecil ROHS Certificate]

* Pinecil breakout board schematic:
** [https://files.pine64.org/doc/Pinecil/Pinecil_Breakout_Board_Schematic_v1.0_20201005.pdf Pinecil breakout board schematic ver 1.0 20201005]
** [https://files.pine64.org/doc/Pinecil/Pinecil_Breakout_Board_PCB_layout_v1.0_20201005.pdf Pinecil breakout board PCB layout ver 1.0]
* Photos:
<gallery>
File:Pinecil-breakout-board-02.jpg|Store photo
File:Pinecil breakout top.jpg|Top view
File:Pinecil breakout bottom.jpg|Bottom view
</gallery>

== Firmware Image Releases ==

* [https://github.com/pine64/pinecil-firmware-updater/releases/latest Latest Pinecil Firmware Updater] for MacOS and Windows

* [https://files.pine64.org/os/Pinecil/Pinecil_firmware_20201115.zip Pinecil production firmware 20201115, thanks to Ralimtek]

Links to development firmware and documentation:

* [https://github.com/Ralim/IronOS/releases GitHub repository for IronOS, from Ralimtek]
* [https://github.com/Ralim/IronOS/blob/master/Documentation/Flashing.md GitHub link for IronOS flashing documentation]

== Datasheets for components and peripherals ==
* GigaDevice RISC-V SoC information:
** [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_Datasheet_Rev%201.1.pdf GigaDevice RISC-V GD32VF103TB SoC Datasheet V1.1]
** [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_User_Manual_EN_V1.2.pdf GigaDevice RISC-V GD32VF103TB SoC Usermanual V1.2]
* Display Module information:
** [https://files.pine64.org/doc/datasheet/pinecil/1810010328_UG-Univision-Semicon-UG-9616TSWCG02_C88335.pdf QUG 9616TSWCG02 Display Module Datasheet]
* USB Type-C PD Controller information:
** [https://files.pine64.org/doc/datasheet/pinecil/FUSB302-D.PDF ON Semiconductor FUSB302 USB Type-C PD Controller Datasheet]
* Sensor information:
** [https://files.pine64.org/doc/datasheet/pinecil/BMA223-Bosch.pdf Bosch BMA223 Acceleration Sensor Datasheet]
** [https://files.pine64.org/doc/datasheet/pinecil/si7210-datasheet.pdf Silicon Lab Si7210 Hall-Effect Magnetic Position Sensor Datasheet]
** [https://files.pine64.org/doc/datasheet/pinecil/TMP35_36_37.pdf Analog Device TMP36 Temparature Sensor Datasheet]
* Power Regulator information:
** [https://files.pine64.org/doc/datasheet/pinecil/RT7272B-05.pdf Ricktek RT7272B 3A Switching Power Regulator Datasheet - on mainboard]
** [https://files.pine64.org/doc/datasheet/pinecil/LP6498B6F.pdf LowPowerSemi LP6498B6F 1.2A Switching Power Regulator Datasheet - on breakout board]
* Power MOSFET Switch information:
** [https://files.pine64.org/doc/datasheet/pinecil/Changjiang-Electronics-Tech-CJ-CJQ7328.pdf Chang Jiang CJQ7328 8A MOSFET Datasheet]
* OP Amp information:
** [https://files.pine64.org/doc/datasheet/pinecil/SGM8557.pdf SGMicro SGM8557-1 Low Noise OP Amp Datasheet]

== Batch changes ==

* For the first manufacture batch of the Pinecil, the copper ring connecting the earth screw to the tip was omitted as the engineering team found the TS100 design lacking. For the second round onwards, an improved design copper ring has been included as standard, and is also included with the replacement red and black handles. For normal operation of the iron, omission of the ring does not impact it's operation. If you are working with ESD components, you will however need it in order to ground the iron tip via the earth screw at the back of the iron. If you from the first batch, and need that part, please contact info at pine64 dot org with the subject "Pinecil copper ring", and include your order number and shipment will be arranged.

* The first batch of Pinecil's were rated 12-24v @ 65W. After some heated discussion on the discussion group, it was decided that it would be downgraded to 12-21V @ 60W, due to concern over the connection of the DC jack to the USB-PD chip, which has a recommended maximum of 21v, and absolute maximum of 28v.

== Development efforts ==

{| class="wikitable"
!
! Project Homepage
! Project Source
! Implementations

|-
! Ralimtek
| https://ralimtek.com
| https://www.gitmemory.com/Ralim
|}

=== How to update a firmware ===

(Method tested on Linux, should work on any OS which supply dfu-util 0.10, if your distro comes with 0.9 you might soft-brick your Pinecil)

{{warning|1=This potentially can brick your device. Do on your own risk!}}

{{note|1=If <code>dfu-util</code> command cannot find a device with 28e9:0189 ID, try to run it with <code>sudo</code>}}

{{note|1=To check if you can use dfu-util 0.9, you can use <code>dfu-util -l</code>. If it reports <code>alt=0, name="@Internal Flash /0x08000000/128*001Kg"</code> you are fine, otherwise you need to upgrade to 0.10, important part is <code>128*001Kg</code>, which is flash amount of blocks and block size, as a chip used in Pinecil have 128 KB of Flash with 1KB page size}}

# Enter an update mode. For that plug USB cable while holding *-* button (button, that's closest to USB-C port)
# Make a firmware backup: <code>dfu-util -d 28e9:0189 -a 0 -U ~/pinecil/internal.flash.stock -s 0x08000000</code>
## <code>28e9:0189</code> -- USB Device ID (can be obtained from <code>lsusb</code> or <code>dfu-util -l</code> but in dfu-util output it might be hard to identify the Pinecil device)
## <code>-a 0</code> -- selects partition to flash. List of possible options can be obtained via <code>dfu-util -l</code>. Partition 0 - internal SPI flash. Partition 1 - fuses (description of fuses can be found in User Manual for the chip)
## <code>-U</code> -- specifies a mode. U is upload, which means that firmware will be downloaded and saved to file (yes, that's confusing, but it is what it is, feel free to verify that in a manual of your version of dfu-util). Command must be followed by a path to file where you want to save your firmware. dfu-util will refuse to dump firmware if you already have a file with that name.
## <code>-s 0x08000000</code> -- specify the address in a flash from which dump will start. This can be obtained from <code>dfu-util -l</code>.
# Flash a new firmware: <code>dfu-util -d 28e9:0189 -a 0 -D Pinecil_EN.bin -s 0x08000000:mass-erase:force</code>
## <code>-D</code> -- is a mode to Download firmware to the device (yes, that's confusing, but you indeed Upload from device and Download to device with dfu-util). That should follow the file with the firmware. Update archive from Ralim usually contains two files: <code>.hex</code> and <code>.bin</code>. One that is required - is <code>.bin</code>. <code>_EN</code> is the language code of the firmware, means that <code>_EN</code> will flash english version of firmware.
## <code>-s 0x08000000:mass-erase:force</code> -- specified the address where to flash the file. <code>:mass-erase:force</code> is required to force-erase flash before updating firmware, otherwise you might have unpredictable results.

== Disassembly steps ==

# Remove tip if present.
## Let tip cool down.
## Loosen top (display side) screw (PH1) on the tip side of the device.
## Gently pull tip out.
# Slide rubber off towards the tip side.
# Remove the ground screw (longer screw on the top side towards the port side) (PH1).
# Remove the bottom screw (at the tip side, between the legs) (PH1).
# Slightly pull the two halves of the case apart at the tip side, enough to get a fingernail or guitar pick between the halves.
# Move the pick down the length of the split to loosen the bottom half's clips from the top half of the case.
# Once loose, remove the bottom half by moving it forward (it is retained by the top half at the port side).
# Remove the screws retaining the copper tip contacts (PH000).
# Remove the now loose copper tip contacts.
# Gently push the board towards the tip side by pushing on one of the ports (for example, by using a misaligned USB C connector).
# The PCB assembly is now free to be lifted out.
## The key caps are now no longer retained, carefully set aside the top half, or remove the caps and store them separately.

== Assembly steps ==

# Place the key caps into their recesses in the top half of the case.
# Place the PCB assembly into the top half of the case ports first.
## Lower the rest of the board into the case and move the PCB assembly towards the port side of the case (the DC barrel connector may be a firm place to gently push).
# Install the copper tip contacts.
## Orient the contact to align the alignment pin with the alignment hole next to the big hole on one of the big gold pads.
## Install and gently tighten the PH000 screw until the clip is no longer loose.
# Place the bottom half of the case into the top half by sliding the lip on the port side (side without the feet) of the bottom half under the arch of the port side of the top half.
# Gently close the case by bringing the two halves together, paying attention to each clip's alignment and ensuring the case edges align.
# Install the short PH1 screw at the bottom of the tip side of the case.
# Install the longer PH1 screw at the ground connection point at the top side of the case (between the display and the ports).
# Slide the rubber sleeve on (larger ridge first).
# Gently insert tip.
# Gently tighten the top PH1 screw to retain the tip.

== Power Supply Compatibility ==

The Pinecil can either work with a 12-21V battery or power supply via the 5525 centre positive jack, or with USB power supplies that support the QC2/QC3 or USB-PD (Power Delivery) specifications. QC2 and QC3 power supplies will only be able to provide a maximum of 12V, limiting the Pinecil to about 17W of thermal capability. A suitable USB-PD power supply / power bank will be able to provide 20V, allowing the Pinecil to deliver the full 60W of heat to soldering tip.

Known working QC/PD power adapters / power banks include:

Power adapter:
* [https://pine64.com/product/pinepower-120w-desktop-power-supply-us-version/ PinePower Desktop]
* [https://www.nekteck.com/product/usb-if-certified-usb-c-charger-nekteck-60w-type-c-wall-charger-power-delivery-pd3-0-travel-charger-compatible-with-macbook-pro-2018-macbook-air-ipad-pro-pixel-3-galaxy-note-9-s9-with-6ft-cable/ Nekteck 60W with 6ft cable]

Power bank:
* [http://beta.blitzwolf.com/-p-15.html Blitzwolf BW-P1 10400mah QC2]

Blacklist / Not compatible:

== Caring for a soldering iron ==

https://www.weller-tools.com/how-to-care-for-soldering-iron-tips/

https://www.eevblog.com/forum/beginners/best-way-to-clean-oxidized-soldering-iron-tip/

[[Category:Pinecil]]

Pinecil

2021-01-23T14:11:49Z

Abcde: /* Firmware Image Releases */ Added Pinecil Firmware Updater

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}
== Overall description ==
[[File:Pinecil-bb2-01_rotate.jpg]] 
The Pinecil is a portable, temperature controlled soldering iron. It also has the intended use of being a Risc-V development device using a breakout board. It's main features are:

* Portability
* Settable temperature
* Soldering tips:
** Replaceable
** More than half a dozen available. Currently sold as 2 separate sets of 4, one fine set, the other larger.
** Compatible with TS100
* Flexible power sources:
** Barrel jack
** USB Type C power delivery

There are additional features that include (Useful for devkit use):

* A Programmable Gigadevice Risc-V GD32V embedded processor
* 0.67" Monochrome Display that can render text or graphics
* Support for Idle detection, for automatic power down of tip

== Pictures ==

Pre-release:
<gallery>
File:Pinecil_Exploded_Diagram_ver_0.9.png|Pinecil renders|alt=alt language
File:PinecilPrototype.jpg|Pinecil prototype|alt=alt language
</gallery>

Production:
<gallery>
File:Pinecil-bb2-01.jpg|Pinecil and TS-B2 retail package|alt=alt language
File:Pinecil-Case-Red-1.jpg|Pinecil red casing|alt=alt language
</gallery>

== Pinecil tips ==
* Uses TS-100 compatible tips
* Tip model TS-B2 is the default tip supplied with the Pinecil
* Tip set 1 (left) & 2 (right): 
[[File:PinecilTipSets.jpg|800px]]

== Specifications ==
* '''Dimensions:''' 170mm with solder tip or 98mm without solder tip x 12.8mm x 16.2mm
* '''Weight:''' 30g with solder tip, 20g without solder tip
* '''CPU:''' GD32VF103TB 32-bit RV32IMAC RISC-V “Bumblebee Core” @ 108 MHz
* '''Display:''' 0.67" QUG 9616TSWCG02 96x16 Monochrome Matrix display
* '''Memory:'''
** 128KB Flash
** 32KB SRAM
* '''DC in (only one of the following at a time):'''
** 12V- 24V DC5525 Barrel Jack
** USB-C 12-20V PD
** QC3.0
** Recommend operating voltage 12-21V, maximum rating at 24V

== Pinecil board information, schematics and certifications ==

* Pinecil mainboard schematic:
** [https://files.pine64.org/doc/Pinecil/Pinecil_schematic_v1.0a_20201120.pdf Pinecil mainboard schematic ver 1.0 20201120, this is production version schematic]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Top PDF file]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Bottom PDF file]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Top Drawing file]
** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Bottom Drawing file]

* Pinecil certifications:
** [https://files.pine64.org/doc/cert/Pinecil%20CE%20RED%20Certificate-S20102803801001.pdf Pinecil CE RED Certificate]
** [https://files.pine64.org/doc/cert/Pinecil%20FCC%20Certificate-S20102803802001.pdf Pinecil FCC Certificate]
** [https://files.pine64.org/doc/cert/Pinecil%20RoHS10%20Certificate-S20102803803001.pdf Pinecil ROHS Certificate]

* Pinecil breakout board schematic:
** [https://files.pine64.org/doc/Pinecil/Pinecil_Breakout_Board_Schematic_v1.0_20201005.pdf Pinecil breakout board schematic ver 1.0 20201005]
** [https://files.pine64.org/doc/Pinecil/Pinecil_Breakout_Board_PCB_layout_v1.0_20201005.pdf Pinecil breakout board PCB layout ver 1.0]
* Photos:
<gallery>
File:Pinecil-breakout-board-02.jpg|Store photo
File:Pinecil breakout top.jpg|Top view
File:Pinecil breakout bottom.jpg|Bottom view
</gallery>

== Firmware Image Releases ==

* [https://github.com/pine64/pinecil-firmware-updater/releases/latest Latest Pinecil Firmware Updater] for MacOS and Windows

* [https://files.pine64.org/os/Pinecil/Pinecil_firmware_20201115.zip Pinecil production firmware 20201115, thanks to Ralimtek]

Links to development firmware and documentation:

* [https://github.com/Ralim/IronOS/releases GitHub repository for IronOS, from Ralimtek]
* [https://github.com/Ralim/IronOS/blob/master/Documentation/Flashing.md GitHub link for IronOS flashing documentation]

== Datasheets for components and peripherals ==
* GigaDevice RISC-V SoC information:
** [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_Datasheet_Rev%201.1.pdf GigaDevice RISC-V GD32VF103TB SoC Datasheet V1.1]
** [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_User_Manual_EN_V1.2.pdf GigaDevice RISC-V GD32VF103TB SoC Usermanual V1.2]
* Display Module information:
** [https://files.pine64.org/doc/datasheet/pinecil/1810010328_UG-Univision-Semicon-UG-9616TSWCG02_C88335.pdf QUG 9616TSWCG02 Display Module Datasheet]
* USB Type-C PD Controller information:
** [https://files.pine64.org/doc/datasheet/pinecil/FUSB302-D.PDF ON Semiconductor FUSB302 USB Type-C PD Controller Datasheet]
* Sensor information:
** [https://files.pine64.org/doc/datasheet/pinecil/BMA223-Bosch.pdf Bosch BMA223 Acceleration Sensor Datasheet]
** [https://files.pine64.org/doc/datasheet/pinecil/si7210-datasheet.pdf Silicon Lab Si7210 Hall-Effect Magnetic Position Sensor Datasheet]
** [https://files.pine64.org/doc/datasheet/pinecil/TMP35_36_37.pdf Analog Device TMP36 Temparature Sensor Datasheet]
* Power Regulator information:
** [https://files.pine64.org/doc/datasheet/pinecil/RT7272B-05.pdf Ricktek RT7272B 3A Switching Power Regulator Datasheet - on mainboard]
** [https://files.pine64.org/doc/datasheet/pinecil/LP6498B6F.pdf LowPowerSemi LP6498B6F 1.2A Switching Power Regulator Datasheet - on breakout board]
* Power MOSFET Switch information:
** [https://files.pine64.org/doc/datasheet/pinecil/Changjiang-Electronics-Tech-CJ-CJQ7328.pdf Chang Jiang CJQ7328 8A MOSFET Datasheet]
* OP Amp information:
** [https://files.pine64.org/doc/datasheet/pinecil/SGM8557.pdf SGMicro SGM8557-1 Low Noise OP Amp Datasheet]

== Batch changes ==

* For the first manufacture batch of the Pinecil, the copper ring connecting the earth screw to the tip was omitted as the engineering team found the TS100 design lacking. For the second round onwards, an improved design copper ring has been included as standard, and is also included with the replacement red and black handles. For normal operation of the iron, omission of the ring does not impact it's operation. If you are working with ESD components, you will however need it in order to ground the iron tip via the earth screw at the back of the iron. If you from the first batch, and need that part, please contact info at pine64 dot org with the subject "Pinecil copper ring", and include your order number and shipment will be arranged.

* The first batch of Pinecil's were rated 12-24v @ 65W. After some heated discussion on the discussion group, it was decided that it would be downgraded to 12-21V @ 60W, due to concern over the connection of the DC jack to the USB-PD chip, which has a recommended maximum of 21v, and absolute maximum of 28v.

== Development efforts ==

{| class="wikitable"
!
! Project Homepage
! Project Source
! Implementations

|-
! Ralimtek
| https://ralimtek.com
| https://www.gitmemory.com/Ralim
|}

=== How to update a firmware ===

(Method tested on Linux, should work on any OS which supply dfu-util 0.10, if your distro comes with 0.9 you might soft-brick your Pinecil)

{{warning|1=This potentially can brick your device. Do on your own risk!}}

{{note|1=If <code>dfu-util</code> command cannot find a device with 28e9:0189 ID, try to run it with <code>sudo</code>}}

{{note|1=To check if you can use dfu-util 0.9, you can use <code>dfu-util -l</code>. If it reports <code>alt=0, name="@Internal Flash /0x08000000/128*001Kg"</code> you are fine, otherwise you need to upgrade to 0.10, important part is <code>128*001Kg</code>, which is flash amount of blocks and block size, as a chip used in Pinecil have 128 KB of Flash with 1KB page size}}

# Enter an update mode. For that plug USB cable while holding *-* button (button, that's closest to USB-C port)
# Make a firmware backup: <code>dfu-util -d 28e9:0189 -a 0 -U ~/pinecil/internal.flash.stock -s 0x08000000</code>
## <code>28e9:0189</code> -- USB Device ID (can be obtained from <code>lsusb</code> or <code>dfu-util -l</code> but in dfu-util output it might be hard to identify the Pinecil device)
## <code>-a 0</code> -- selects partition to flash. List of possible options can be obtained via <code>dfu-util -l</code>. Partition 0 - internal SPI flash. Partition 1 - fuses (description of fuses can be found in User Manual for the chip)
## <code>-U</code> -- specifies a mode. U is upload, which means that firmware will be downloaded and saved to file (yes, that's confusing, but it is what it is, feel free to verify that in a manual of your version of dfu-util). Command must be followed by a path to file where you want to save your firmware. dfu-util will refuse to dump firmware if you already have a file with that name.
## <code>-s 0x08000000</code> -- specify the address in a flash from which dump will start. This can be obtained from <code>dfu-util -l</code>.
# Flash a new firmware: <code>dfu-util -d 28e9:0189 -a 0 -D Pinecil_EN.bin -s 0x08000000:mass-erase:force</code>
## <code>-D</code> -- is a mode to Download firmware to the device (yes, that's confusing, but you indeed Upload from device and Download to device with dfu-util). That should follow the file with the firmware. Update archive from Ralim usually contains two files: <code>.hex</code> and <code>.bin</code>. One that is required - is <code>.bin</code>. <code>_EN</code> is the language code of the firmware, means that <code>_EN</code> will flash english version of firmware.
## <code>-s 0x08000000:mass-erase:force</code> -- specified the address where to flash the file. <code>:mass-erase:force</code> is required to force-erase flash before updating firmware, otherwise you might have unpredictable results.

== Disassembly steps ==

# Remove tip if present.
## Let tip cool down.
## Loosen top (display side) screw (PH1) on the tip side of the device.
## Gently pull tip out.
# Slide rubber off towards the tip side.
# Remove the ground screw (longer screw on the top side towards the port side) (PH1).
# Remove the bottom screw (at the tip side, between the legs) (PH1).
# Slightly pull the two halves of the case apart at the tip side, enough to get a fingernail or guitar pick between the halves.
# Move the pick down the length of the split to loosen the bottom half's clips from the top half of the case.
# Once loose, remove the bottom half by moving it forward (it is retained by the top half at the port side).
# Remove the screws retaining the copper tip contacts (PH000).
# Remove the now loose copper tip contacts.
# Gently push the board towards the tip side by pushing on one of the ports (for example, by using a misaligned USB C connector).
# The PCB assembly is now free to be lifted out.
## The key caps are now no longer retained, carefully set aside the top half, or remove the caps and store them separately.

== Assembly steps ==

# Place the key caps into their recesses in the top half of the case.
# Place the PCB assembly into the top half of the case ports first.
## Lower the rest of the board into the case and move the PCB assembly towards the port side of the case (the DC barrel connector may be a firm place to gently push).
# Install the copper tip contacts.
## Orient the contact to align the alignment pin with the alignment hole next to the big hole on one of the big gold pads.
## Install and gently tighten the PH000 screw until the clip is no longer loose.
# Place the bottom half of the case into the top half by sliding the lip on the port side (side without the feet) of the bottom half under the arch of the port side of the top half.
# Gently close the case by bringing the two halves together, paying attention to each clip's alignment and ensuring the case edges align.
# Install the short PH1 screw at the bottom of the tip side of the case.
# Install the longer PH1 screw at the ground connection point at the top side of the case (between the display and the ports).
# Slide the rubber sleeve on (larger ridge first).
# Gently insert tip.
# Gently tighten the top PH1 screw to retain the tip.

== Power Supply Compatibility ==

The Pinecil can either work with a 12-21V battery or power supply via the 5525 centre positive jack, or with USB power supplies that support the QC2/QC3 or USB-PD (Power Delivery) specifications. QC2 and QC3 power supplies will only be able to provide a maximum of 12V, limiting the Pinecil to about 17W of thermal capability. A suitable USB-PD power supply / power bank will be able to provide 20V, allowing the Pinecil to deliver the full 60W of heat to soldering tip.

Known working QC/PD power adapters / power banks include:

Power adapter:
* [https://pine64.com/product/pinepower-120w-desktop-power-supply-us-version/ PinePower Desktop]
* [https://www.nekteck.com/product/usb-if-certified-usb-c-charger-nekteck-60w-type-c-wall-charger-power-delivery-pd3-0-travel-charger-compatible-with-macbook-pro-2018-macbook-air-ipad-pro-pixel-3-galaxy-note-9-s9-with-6ft-cable/ Nekteck 60W with 6ft cable]

Power bank:
* [http://beta.blitzwolf.com/-p-15.html Blitzwolf BW-P1 10400mah QC2]

Blacklist / Not compatible:

== Caring for a soldering iron ==

https://www.weller-tools.com/how-to-care-for-soldering-iron-tips/

https://www.eevblog.com/forum/beginners/best-way-to-clean-oxidized-soldering-iron-tip/

[[Category:Pinecil]]

User:JF

2020-11-12T10:39:39Z

Abcde: renamed page

I'm the maintainer of [https://github.com/JF002/Pinetime InfiniTime].

== Pages ==

- [[PineTime bootloader improvements]]

PineTime bootloader improvements

2020-11-11T19:53:48Z

Abcde: added category

== Introduction ==
This pages describes the improvements I propose to make to the bootloader and OTA to make the whole process more reliable.

My goals are:

* KISS : Keep It Stupid Simple. Simple code contains less bugs than complicated/complex code.
* As reliable as possible. 100% reliability is not feasible with the current hardware (no physical reset button, no bootloader in ROM code,...), but let's try to reach 99.9% reliability :)
* Provide a read-only factory image we'll be able to restore in case of unrecoverable errors during OTA
* Provide a way to upgrade the bootloader
* Provide a way to switch from MCUBoot to NRF bootloaders

== Current memory map ==
[[File:MemoryMap.png]]

Internal flash:
* Bootloader contains the MCUBoot bootloader.
* Boot log is currently not used. Can be use to provide reboot logs to the application
* App is the PRIMARY SLOT for MCUBoot : the firmware that is currently running.
* Scratch is used by MCUBoot as temporary storage for swap operation

External flash:
* Bootloader assets : boot logo
* OTA : SECONDARY SLOT for MCUBoot. During OTA, this is where the new version of the firmware is stored.
* FS : space available for the application firmware.

== Changes ==

=== Factory image ===
The factory image is a 'light' build of InfiniTime that contains the bare minimum code to provide OTA to the user : basic UI, BLE and OTA. No apps, no fancy functionalities,...
This factory image will be stored in the "bootloader assets" area of the external flash memory.

This factory image will be restored either automatically, when the bootloader detect it cannot boot from primary slot (App in internal memory) and secondary slot (OTA from exeternal).
The user can also request to restore this factory image if necessary (using the button?).

=== Bootloader assets ===
Graphics can be compressed using a simple RLE encoding. RLE encoding on 1 bits (2 colors images) is very efficient (115200KB -> 1-5KB).

In order to simplify the code, the graphics will be stored into the bootloader code instead of storing them into the external flash:
- Less code.
- Easier to flash/install for the user AND the factory (we literally spend WEEKS to successfully flash infinitime and the bootloader).
- Easier to document : 1 specific logo = bootloader mode
- Do not have to worry about the dynamic size of the logo (the binary size of the graphics will vary with the content when they are RLE encoded).

=== Bootloader ===
* Display the bootloader version on the screen and expose the version to the application firmware
* Provide a way to revert the firmware to the last working version AND to the factory firmware
* Display status and progression (progress bar similar to wasp-reloader, color code,...)
* Test as much as possible

=== Upgrade & Reloader ===
The reloader is a tool that allows to upgrade the current version of the bootloader AND to switch from MCUBoot to NRF and vice versa.

==== How does it work ? ====
* Upgrade
** The reloader is first OTAed like any firmware upgrade.
** When the system resets, MCUBoot swaps the application firmware with the reloader. The reloader upgrade the current bootloader and resets the system. It does NOT flag the image as validated. It resets the MCU.
** The new version of MCUBoot notice that the last upgrade is not validated and reverts to the firmware that was running just before.
** Voilà, you're running your firmware and a new version of the bootloader

* Switch bootloader
** The reloader is first OTAed like any firmware upgrade.
** When the system resets, MCUBoot swaps the application firmware with the reloader. The reloader overwrite the current bootloader with a new one and reset.
** The new bootloader is running.

* Switch
** From InfiniTime to wasp-os : the reloader contains the NRF Bootloader and Softdevice. This bootloader provides the OTA mecanism out of the box. Wasp-os is downloaded when the NRF bootloader is running
** From wasp-os to InfiniTime : the reloader contains the factory image (infinitime-factory). The complete version of InfiniTime will be OTAed when this factory image is running.

[[Category:PineTime]]

Bootloader improvements

2020-11-11T19:53:29Z

Abcde: Abcde moved page Bootloader improvements to PineTime bootloader improvements: classification

#REDIRECT [[PineTime bootloader improvements]]

PineTime bootloader improvements

2020-11-11T19:53:29Z

Abcde: Abcde moved page Bootloader improvements to PineTime bootloader improvements: classification

User:Abcde/Braveheart Recycle

2020-11-01T13:02:49Z

Abcde: /* Interfacing */ add bt/serial interface use

So there is a [https://pine64.com/product/pinephone-community-edition-3gb-32gb-mainboard-special-offer-for-braveheart-and-ubports-owners/ Mainboard upgrade] program now. While I think doing the [[PinePhone_Modding|fixes]] is a fun and not too difficult project (removing the mainboard is the most difficult part anyway!), there are reasons for some to want to do the upgrade. All these people will have a spare mainboard. There is a question on what to do with the mainboard that is left over when the mainboard is replaced. It can be regarded as spare and/or useless, but it still is a great device to play with, as it has a lot of power, and great pheripherals. The best thing of course is to send it to me, info upon request :P But for all others:

== What we still got ==
A SBC with very useful integrated devices:

* A64
* 2 GB RAM
* 16 GB eMMC
* Wifi/BT
* LTE modem
* Sensors
* Headphone/Serial
* UPS hardware
* Killswitches

When reusing parts of the phone that you do not use anyway, you can even add more functions, for instance, i have my camera's killswitched, so I could reuse them for a project.

----
But there are some things that need to be taken care of.
== [[User:Abcde/Braveheart_Recycle/Power|Power]] ==
The power would have to be added in an alternative way. This can include the battery charging, but also direct connecting to a permanent powersource.
== [[User:Abcde/Braveheart_Recycle/Interfacing|Interfacing]] ==
Without a screen we need some other way of setting up the device and have interaction. The easiest would likely be to add some bt headphones, and the serial. That way we already could add telephone capability.

== [[User:Abcde/Braveheart_Recycle/Antennae|Antennae]] ==
The back cover adds the antennae, so we need some other way to get this included
== [[User:Abcde/Braveheart_Recycle/Buttons|Buttons]] ==
There are some hardware buttons, but they are included in a difficult way.
== [[User:Abcde/Braveheart_Recycle/USBC|USBC]] ==
The USBC is a different board, so we need a new way to connect to there.
== Use cases ==
* Emergency internet router - If there are no ways to connect directly, you could use the LTE to get networking, and share it over wifi.
* Infobox - Remotely managed box to share info to communities over wifi, and syncing over LTE.
* Remote Sensor - For builtin, or added sensors. Can send info over LTE
* Lots more, I have a longer list, but please add yours.

As this is a community effort, we should be able to reuse the parts we have left.
Add here as much as you want!

User:Abcde/Braveheart Recycle

2020-11-01T12:12:11Z

Abcde: initial edit

So there is a [https://pine64.com/product/pinephone-community-edition-3gb-32gb-mainboard-special-offer-for-braveheart-and-ubports-owners/ Mainboard upgrade] program now. While I think doing the [[PinePhone_Modding|fixes]] is a fun and not too difficult project (removing the mainboard is the most difficult part anyway!), there are reasons for some to want to do the upgrade. All these people will have a spare mainboard. There is a question on what to do with the mainboard that is left over when the mainboard is replaced. It can be regarded as spare and/or useless, but it still is a great device to play with, as it has a lot of power, and great pheripherals. The best thing of course is to send it to me, info upon request :P But for all others:

== What we still got ==
A SBC with very useful integrated devices:

* A64
* 2 GB RAM
* 16 GB eMMC
* Wifi/BT
* LTE modem
* Sensors
* Headphone/Serial
* UPS hardware
* Killswitches

When reusing parts of the phone that you do not use anyway, you can even add more functions, for instance, i have my camera's killswitched, so I could reuse them for a project.

----
But there are some things that need to be taken care of.
== [[User:Abcde/Braveheart_Recycle/Power|Power]] ==
The power would have to be added in an alternative way. This can include the battery charging, but also direct connecting to a permanent powersource.
== [[User:Abcde/Braveheart_Recycle/Interfacing|Interfacing]] ==
Without a screen we need some other way of setting up the device and have interaction.
== [[User:Abcde/Braveheart_Recycle/Antennae|Antennae]] ==
The back cover adds the antennae, so we need some other way to get this included
== [[User:Abcde/Braveheart_Recycle/Buttons|Buttons]] ==
There are some hardware buttons, but they are included in a difficult way.
== [[User:Abcde/Braveheart_Recycle/USBC|USBC]] ==
The USBC is a different board, so we need a new way to connect to there.
== Use cases ==
* Emergency internet router - If there are no ways to connect directly, you could use the LTE to get networking, and share it over wifi.
* Infobox - Remotely managed box to share info to communities over wifi, and syncing over LTE.
* Remote Sensor - For builtin, or added sensors. Can send info over LTE
* Lots more, I have a longer list, but please add yours.

As this is a community effort, we should be able to reuse the parts we have left.
Add here as much as you want!

PinePhone Modding

2020-10-28T07:45:05Z

Abcde: typo

There are a number of options to hardware mod the PinePhone.

Some are upgrades to fix issues that were not done optimally in the production of that version of the electronics, and some are to add options that were not part of the phone spec.

== PRO TIP ==
Make pictures of the situation before and after your mods, so you can compare the change, and don't need to disassemble the device to get the right pics later.

==Device Specific Mods ==
There are a number of upgrades possible for the different versions of the PinePhone.

=== "Don't be evil" ===
*

=== BraveHeart ===
*PMIC mod - Stops the battery drain from a shutdown phone, draining the battery to 0V.
*VCONN mod - Unblocks the USB-C power negotiation rail, so convergence functions are unlocked.

=== UBPorts Community edition ===
*VCONN mod - Unblocks the USB-C power negotiation rail, so convergence functions are unlocked.

There are also a number of mods that can be done adding more functions by adding extra hardware to the pogo pins, and a number of options to change the screen protector.

At this moment there are not many pogo addons, and most are just connector boards. Likely the makers will add links to these projects to this page. Pine is looking into adding a N900 style keyboard attached to these pins.

== PMIC mod ==
[[PinePhone_1.1_VBUS_power_usage_Hardware_Fix]]
The original description of this fix is given on megi's pager here https://xnux.eu/devices/pp-pmic-fix.jpg
== VCONN mod ==
The original description of this fix is given on megi's pager here https://xnux.eu/devices/pp-usbc-fix.jpg
There is a discussion on the merits of the different ways to do the fix

=== VCONN mod, Removal only ===
[[PinePhone_1.2_VCONN_Hardware_Fix]]

There are now a few documented ways,
*Removal only, the tweezer "stupid" way: https://www.youtube.com/watch?v=j3jc7Mvn9Eo
*Removal only, the soldering iron "less stupid" way: https://www.youtube.com/watch?v=ZqOb45N2sMc
There are hopefully videos coming doing it the proper way, and so they can be linked here.

After this the firmware for the power negotiation chip needs to be upgraded, this can be done by running the factory test image, version http://images.postmarketos.org/pinephone/pine64-pinephone-20200724-factorytest55.img.xz or higher. This will do the firmware flashing and respond with a message indicating the state. After this the phone is ready for its added functions.
ANX states:
*No CC Fix - Fix not applied
*No USB Cable - No USBC connection, cannot upgrade firmware
*OK - Firmware Applied, you are all set

=== VCONN mod, Replacement ===
Using 2x NCP334FCT2G you could do the full fix, making VCONN powered devices able to negotiate power. IT needs the parts to be removed first without damaging the pads, and then replacing the parts.

==Laser cut parts==
Mcyam2 has created some laser cut templates for the rear facing components here:

https://imgur.com/a/LAUatOa

https://anonfiles.com/L0BeK5L5oe/ppsvg-backplate-CUTOUT_svg

Originally based on silver's work on a 3d printed rear frame

==3D Printed parts==

Silver has created a 3D-printable rear frame for the PinePhone and used it to create a folding keyboard design (work in progress), [[User:Silver/3d printed a folding keyboard mostly]].

https://ibb.co/album/ScDttH

https://www.youmagine.com/designs/pinephone-folding-keyboard-mockup

[[Category:PinePhone]]

ROCKPro64

2020-10-21T13:25:04Z

Abcde: Reverted edits by Abcde (talk) to last revision by Fxc

The [https://www.pine64.org/rockpro64/ '''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.

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.

= Board layout =
[[File:ROCKPro64_annotated.jpg]]

[[File:ROCKPro64v21FRONT.jpg|200px|thumb|right|A hi-res picture of v2.1 front]]

[[File:ROCKPro64v21REAR.jpg|200px|thumb|right|A hi-res picture of v2.1 rear]]

== 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): 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): perfoms a reset.

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

== Connectors, sockets and headers ==
{| class="wikitable sortable"
! 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;" | 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;" | 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 || 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, S = boot from the µSD card, M = boot from the eMMC module, X = unsupported combination):

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot
|-
| 0 || 0 || 0 || X
|-
| 0 || 0 || 1 || X
|-
| 0 || 1 || 0 || M
|-
| 0 || 1 || 1 || X
|-
| 1 || 0 || 0 || S
|-
| 1 || 0 || 1 || S
|-
| 1 || 1 || 0 || M
|-
| 1 || 1 || 1 || S
|}

=== 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.

= Getting Started =

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

== Start here - Software and OS Image Builds ==

In the '[[ROCKPro64 Software Release]]' 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 how to load each image.

The list includes OS images and descriptions of:

[{{fullurl:ROCKPro64_Software_Release#Armbian}} http://files.pine64.org/sw/pine64_installer/json/armbian.png] [[ROCKPro64_Software_Release#Armbian|'''Armbian (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#Debian_by_mrfixit2001}} http://files.pine64.org/sw/pine64_installer/json/debian.png] [[ROCKPro64_Software_Release#Debian_by_mrfixit2001|'''Debian (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#DietPi}} http://files.pine64.org/sw/pine64_installer/json/dietpi.png] [[ROCKPro64_Software_Release#DietPi|'''DietPi (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#OpenMediaVault}} http://files.pine64.org/sw/pine64_installer/json/omv.png] [[ROCKPro64_Software_Release#OpenMediaVault|'''Open Media Vault (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#LibreELEC.28KODI.29}} http://files.pine64.org/sw/pine64_installer/json/libreelec.png] [[ROCKPro64_Software_Release#LibreELEC.28KODI.29|'''LibreELEC for KODI (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#Slackware}} http://files.pine64.org/sw/pine64_installer/json/slackware.png] [[ROCKPro64_Software_Release#Slackware|'''Slackware (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#Nems_Linux}} http://files.pine64.org/sw/pine64_installer/json/nems.jpg] [[ROCKPro64_Software_Release#Nems_Linux|'''Nagios Enterprise Monitoring Server (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#NextCloudPi}} http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png] [[ROCKPro64_Software_Release#NextCloudPi|'''NextCloudPi (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#Cent_OS}} http://files.pine64.org/sw/pine64_installer/json/centos.jpg] [[ROCKPro64_Software_Release#Cent_OS|'''Cent OS (microSD Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#Manjaro_ARM}} http://files.pine64.org/sw/pine64_installer/json/manjaro.png] [[ROCKPro64_Software_Release#Manjaro_ARM|'''Manjaro ARM (microSD and eMMC Boot)''']]

[[File:Openwrt_logo_square.png|100px]] [[ROCKPro64_Software_Release#OpenWrt|'''OpenWrt (microSD and eMMC Boot)''']]

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

== More advanced Linux bits ==

Some Linux tips are given below.

=== How to update your Linux ===

For Debian/Ubuntu images entering the following commands at a terminal prompt

<code>sudo apt-get update</code> 
<code>sudo apt-get upgrade</code>

will keep your installation up to date. To update Ayufan images to the next release (when available) use the following command

<code>sudo apt-get dist-upgrade</code>

If you are happy to update your system to pre-releases of Ayufan images then modify /etc/apt/sources.list.d/ayufan-rock64.list as per the comment in that file.

The kernel in Ayufan releases is under active development and, if you wish to install a later version, then it is best to use a package manager. In synaptic (for example), if you search for package names linux-image-4.4 you should see your currently installed version(s) as well as any more recent ones. Similarly if you wish to install the mainline kernel then searching for linux-image-4.18 will show you what is available. '''At the time of writing (August 2018) there are significant features missing from the mainline kernel for aarch64 processors (e.g. HDMI sound).'''

=== Useful scripts ===
After you install an Ayufan image you will find some scripts in /usr/local/sbin/ and /usr/local/bin/ that may be useful. (Need to expand this section)

=== Video playback ===
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 deskop releases.) At which stage rkmpv myvideo.mp4 will play a fullscreen, hardware assisted, version of your video. rkmpv is at /usr/local/bin/rkmpv

=== Swapping kernel versions ===
extlinux is in use on Ayufan images (at least) which enables some switching between installed kernel versions - [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/extlinux.md intro documentation is here.] In particular after you install any additional kernels, you can edit your /boot/extlinux/extlinux.conf file to specify which of the kernels you have installed to use for the next boot.

From Ayufan version 0.7.11 the script /usr/local/sbin/change-default-kernel.sh does a nice little menu swap for you if you run it as root (sudo).

=== Using an NVMe disk for 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.

== More advanced bits related to any OS ==

This section gives some hints for advanced users.

=== Setup a serial console (UART)===
The early adopters (and late-comers who fiddle excessively with their boards!) have a need to monitor the low-level boot behaviour: this is done with a serial console and there [https://forum.pine64.org/showthread.php?tid=6387 is a great description how to get this working specifically for your ROCKPro64 here.]

=== Booting from USB or PXE ===

The default choice of boot device is first eMMC (if present) then SDcard. See [[ ROCKPro64_Main_Page#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_Main_Page#Useful_scripts | useful scripts above.]]) The NOOB wiki page has more details [[NOOB#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.]

=== 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_Main_Page#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 SDcard 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 SDcard 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://store.pine64.org/?product=rockpro64-pci-e-x4-to-m-2ngff-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=rockpro64-pci-e-to-dual-sata-ii-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://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-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.'''

=== RTC battery backup ===
The Pine store has a couple of options for RTC battery backups: a [https://store.pine64.org/?product=rtc-backup-battery-aaa-battery AAA version here] or a [https://store.pine64.org/?product=rtc-backup-battery-cr-battery CR-2032 version here.] Instructions for plugging in either of them are also on the [[ Accessories_Step_by_Step_Guides| Accessories page ]]

=== Acryllic open enclosure ===
Assembly instructions for the [https://store.pine64.org/?product=pine64-acrylic-open-enclosure acryllic enclosure] from the Pine store are also on the [[ Accessories_Step_by_Step_Guides| Accessories page ]]

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

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

= [[ROCKPro64_Hardware_Accessory_Compatibility|Hardware Compatibility]] =
== Hardware Compatibility Page ==
Please contribute to the hardware compatibility page, which lists hardware which has been tested with the rockpro64, whether successful or not.

* [[ROCKPro64_Hardware_Accessory_Compatibility#PCIe devices|PCIe devices]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#NVMe_SSD_drives|NVMe SSD drives]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#USB_hardware|USB hardware]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#USB_C_alternate_mode_DP|USB C alternate mode DP]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#Other_hardware|Other hardware]]

== Limitations ==
=== PCIe card issue and/or asynchronous external abort on flash read/write ===
==== Older firmware overwrites actively used memory ====
Some people get system freeze when:
* use SATA disk with ROCKPro64 PCIe card. (maybe on newer PCIe card ASM1062 vs ASM1061)
* or do read or write 4GB to the flash. (not using PCIe)

If you connect the serial console you will see a Linux kernel oops: (a)synchronous external abort.

Both issues are in fact the same software BUG. There is no hardware problem.
Currently most OS do use uboot with a rockpro blob FW which use memory that Linux kernel is not aware of.
People are currently fixing this BUG, but it may take some time.
In the mean time, you can fix it manually.

The latest u-boot can boot the rockpro64 without any blobs from rockchip. Install first arm-none-eabi-gcc and aarch64-linux-gnu-gcc compiler, then run the following commands:

git clone https://github.com/ARM-software/arm-trusted-firmware.git atf
make -C atf CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399 bl31
git clone https://gitlab.denx.de/u-boot/u-boot.git u-boot
cd u-boot/
git checkout v2020.01-rc5
make rockpro64-rk3399_defconfig
BL31=../atf/build/rk3399/release/bl31/bl31.elf make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu-

Which gives you idbloader.img and u-boot.itb. Copy them to the rockpro64, and run the following: (Or put your SD card into your PC)

sudo dd if=idbloader.img of=/dev/mmcblk0 seek=64
sudo dd if=u-boot.itb of=/dev/mmcblk0 seek=16384
sync

==== PCIe controller hardware error handling bug ====
There is an issue with the rk3399 pcie controller that is currently unmitigated:
*[https://lore.kernel.org/linux-pci/CAMdYz...gmail.com/ LKML Original Thread]
*[https://lkml.org/lkml/2020/4/6/320 LKML Additional Information]

The rk3399 pcie controller throws either a synchronous abort or a SError when a pcie device sends an unknown message.

The error type is determined by which cpu cluster handles the message.

=== Virtualization ===
The PCIe controller on the rk3399 is not behind an IOMMU.
This means it is not possible to safely pass through PCIe devices to a virtual machine.

= 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 provide 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 4096x2160 with AFBC supported；The other supports 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support display, 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
* 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

== Working Features ==
{| class="wikitable sortable"
! style="font-weight:bold;" | Feature/Option
! style="font-weight:bold;" | Android
! style="font-weight:bold;" | Android Version
! style="font-weight:bold;" | Linux
! style="font-weight:bold;" | Linux Version
! style="font-weight:bold;" | Test/Verify Steps
! style="font-weight:bold;" | Notes
! style="font-weight:bold;" | Product Link
|-
| Pine64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe this will help get this working? https://github.com/avafinger/pine64-touchscreen
| https://pine64.com/?product=7-lcd-touch-screen-panel
|-
| 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/No
|
|
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons.
| https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-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 then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| http://wiki.pine64.org/index.php/ROCKPro64_Main_Page#OTG_mode
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use ATS. https://github.com/tuxd3v/ats
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out what Frank Mankel has done. https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2
|
|-
| 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.
|
|-
| 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 fanctl to control the fan while keeping your CPU cool https://github.com/tuxd3v/fanctl
| 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
* [http://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [http://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [http://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [http://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [http://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [http://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [http://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]
* [http://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [http://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [http://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.
** [http://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
** [http://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
** [http://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCK64 RoHS Report]

= Datasheets for Components and Peripherals =
* Rockchip RK3399 SoC information:
** [http://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
** [http://opensource.rock-chips.com/images/2/28/Rockchip_RK3399_Datasheet_V1.8-20180529.pdf Rockchip RK3399 Datasheet V1.8]
** [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
** [http://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]
* LPDDR4 (200 Balls) SDRAM:
** [http://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]
* eMMC information:
** [http://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [http://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [http://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [http://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
** [http://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:
** [http://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [http://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]
* Heatsink related info:
** [http://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
** [http://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]
* Wireless related info:
** [[Media:AP6356 datasheet V1.0 07252014.pdf|AMPAK AP6356 2x2 Wi-Fi + Bluetooth4.1 Datasheet]]
* Ethernet related info:
** [http://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]
* Peripheral related info:
** [http://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]
* Remote control button mapping
** [http://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]

= 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
*[http://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[http://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

= 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.]

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

ROCKPro64

2020-10-21T13:24:27Z

Abcde: category test

The [https://www.pine64.org/rockpro64/ '''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.

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.

= Board layout =
[[File:ROCKPro64_annotated.jpg]]

[[File:ROCKPro64v21FRONT.jpg|200px|thumb|right|A hi-res picture of v2.1 front]]

[[File:ROCKPro64v21REAR.jpg|200px|thumb|right|A hi-res picture of v2.1 rear]]

== 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): 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): perfoms a reset.

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

== Connectors, sockets and headers ==
{| class="wikitable sortable"
! 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;" | 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;" | 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 || 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, S = boot from the µSD card, M = boot from the eMMC module, X = unsupported combination):

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot
|-
| 0 || 0 || 0 || X
|-
| 0 || 0 || 1 || X
|-
| 0 || 1 || 0 || M
|-
| 0 || 1 || 1 || X
|-
| 1 || 0 || 0 || S
|-
| 1 || 0 || 1 || S
|-
| 1 || 1 || 0 || M
|-
| 1 || 1 || 1 || S
|}

=== 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.

= Getting Started =

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

== Start here - Software and OS Image Builds ==

In the '[[ROCKPro64 Software Release]]' 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 how to load each image.

The list includes OS images and descriptions of:

[{{fullurl:ROCKPro64_Software_Release#Armbian}} http://files.pine64.org/sw/pine64_installer/json/armbian.png] [[ROCKPro64_Software_Release#Armbian|'''Armbian (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#Debian_by_mrfixit2001}} http://files.pine64.org/sw/pine64_installer/json/debian.png] [[ROCKPro64_Software_Release#Debian_by_mrfixit2001|'''Debian (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#DietPi}} http://files.pine64.org/sw/pine64_installer/json/dietpi.png] [[ROCKPro64_Software_Release#DietPi|'''DietPi (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#OpenMediaVault}} http://files.pine64.org/sw/pine64_installer/json/omv.png] [[ROCKPro64_Software_Release#OpenMediaVault|'''Open Media Vault (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#LibreELEC.28KODI.29}} http://files.pine64.org/sw/pine64_installer/json/libreelec.png] [[ROCKPro64_Software_Release#LibreELEC.28KODI.29|'''LibreELEC for KODI (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#Slackware}} http://files.pine64.org/sw/pine64_installer/json/slackware.png] [[ROCKPro64_Software_Release#Slackware|'''Slackware (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#Nems_Linux}} http://files.pine64.org/sw/pine64_installer/json/nems.jpg] [[ROCKPro64_Software_Release#Nems_Linux|'''Nagios Enterprise Monitoring Server (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#NextCloudPi}} http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png] [[ROCKPro64_Software_Release#NextCloudPi|'''NextCloudPi (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#Cent_OS}} http://files.pine64.org/sw/pine64_installer/json/centos.jpg] [[ROCKPro64_Software_Release#Cent_OS|'''Cent OS (microSD Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#Manjaro_ARM}} http://files.pine64.org/sw/pine64_installer/json/manjaro.png] [[ROCKPro64_Software_Release#Manjaro_ARM|'''Manjaro ARM (microSD and eMMC Boot)''']]

[[File:Openwrt_logo_square.png|100px]] [[ROCKPro64_Software_Release#OpenWrt|'''OpenWrt (microSD and eMMC Boot)''']]

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

== More advanced Linux bits ==

Some Linux tips are given below.

=== How to update your Linux ===

For Debian/Ubuntu images entering the following commands at a terminal prompt

<code>sudo apt-get update</code> 
<code>sudo apt-get upgrade</code>

will keep your installation up to date. To update Ayufan images to the next release (when available) use the following command

<code>sudo apt-get dist-upgrade</code>

If you are happy to update your system to pre-releases of Ayufan images then modify /etc/apt/sources.list.d/ayufan-rock64.list as per the comment in that file.

The kernel in Ayufan releases is under active development and, if you wish to install a later version, then it is best to use a package manager. In synaptic (for example), if you search for package names linux-image-4.4 you should see your currently installed version(s) as well as any more recent ones. Similarly if you wish to install the mainline kernel then searching for linux-image-4.18 will show you what is available. '''At the time of writing (August 2018) there are significant features missing from the mainline kernel for aarch64 processors (e.g. HDMI sound).'''

=== Useful scripts ===
After you install an Ayufan image you will find some scripts in /usr/local/sbin/ and /usr/local/bin/ that may be useful. (Need to expand this section)

=== Video playback ===
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 deskop releases.) At which stage rkmpv myvideo.mp4 will play a fullscreen, hardware assisted, version of your video. rkmpv is at /usr/local/bin/rkmpv

=== Swapping kernel versions ===
extlinux is in use on Ayufan images (at least) which enables some switching between installed kernel versions - [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/extlinux.md intro documentation is here.] In particular after you install any additional kernels, you can edit your /boot/extlinux/extlinux.conf file to specify which of the kernels you have installed to use for the next boot.

From Ayufan version 0.7.11 the script /usr/local/sbin/change-default-kernel.sh does a nice little menu swap for you if you run it as root (sudo).

=== Using an NVMe disk for 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.

== More advanced bits related to any OS ==

This section gives some hints for advanced users.

=== Setup a serial console (UART)===
The early adopters (and late-comers who fiddle excessively with their boards!) have a need to monitor the low-level boot behaviour: this is done with a serial console and there [https://forum.pine64.org/showthread.php?tid=6387 is a great description how to get this working specifically for your ROCKPro64 here.]

=== Booting from USB or PXE ===

The default choice of boot device is first eMMC (if present) then SDcard. See [[ ROCKPro64_Main_Page#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_Main_Page#Useful_scripts | useful scripts above.]]) The NOOB wiki page has more details [[NOOB#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.]

=== 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_Main_Page#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 SDcard 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 SDcard 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://store.pine64.org/?product=rockpro64-pci-e-x4-to-m-2ngff-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=rockpro64-pci-e-to-dual-sata-ii-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://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-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.'''

=== RTC battery backup ===
The Pine store has a couple of options for RTC battery backups: a [https://store.pine64.org/?product=rtc-backup-battery-aaa-battery AAA version here] or a [https://store.pine64.org/?product=rtc-backup-battery-cr-battery CR-2032 version here.] Instructions for plugging in either of them are also on the [[ Accessories_Step_by_Step_Guides| Accessories page ]]

=== Acryllic open enclosure ===
Assembly instructions for the [https://store.pine64.org/?product=pine64-acrylic-open-enclosure acryllic enclosure] from the Pine store are also on the [[ Accessories_Step_by_Step_Guides| Accessories page ]]

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

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

= [[ROCKPro64_Hardware_Accessory_Compatibility|Hardware Compatibility]] =
== Hardware Compatibility Page ==
Please contribute to the hardware compatibility page, which lists hardware which has been tested with the rockpro64, whether successful or not.

* [[ROCKPro64_Hardware_Accessory_Compatibility#PCIe devices|PCIe devices]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#NVMe_SSD_drives|NVMe SSD drives]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#USB_hardware|USB hardware]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#USB_C_alternate_mode_DP|USB C alternate mode DP]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#Other_hardware|Other hardware]]

== Limitations ==
=== PCIe card issue and/or asynchronous external abort on flash read/write ===
==== Older firmware overwrites actively used memory ====
Some people get system freeze when:
* use SATA disk with ROCKPro64 PCIe card. (maybe on newer PCIe card ASM1062 vs ASM1061)
* or do read or write 4GB to the flash. (not using PCIe)

If you connect the serial console you will see a Linux kernel oops: (a)synchronous external abort.

Both issues are in fact the same software BUG. There is no hardware problem.
Currently most OS do use uboot with a rockpro blob FW which use memory that Linux kernel is not aware of.
People are currently fixing this BUG, but it may take some time.
In the mean time, you can fix it manually.

The latest u-boot can boot the rockpro64 without any blobs from rockchip. Install first arm-none-eabi-gcc and aarch64-linux-gnu-gcc compiler, then run the following commands:

git clone https://github.com/ARM-software/arm-trusted-firmware.git atf
make -C atf CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399 bl31
git clone https://gitlab.denx.de/u-boot/u-boot.git u-boot
cd u-boot/
git checkout v2020.01-rc5
make rockpro64-rk3399_defconfig
BL31=../atf/build/rk3399/release/bl31/bl31.elf make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu-

Which gives you idbloader.img and u-boot.itb. Copy them to the rockpro64, and run the following: (Or put your SD card into your PC)

sudo dd if=idbloader.img of=/dev/mmcblk0 seek=64
sudo dd if=u-boot.itb of=/dev/mmcblk0 seek=16384
sync

==== PCIe controller hardware error handling bug ====
There is an issue with the rk3399 pcie controller that is currently unmitigated:
*[https://lore.kernel.org/linux-pci/CAMdYz...gmail.com/ LKML Original Thread]
*[https://lkml.org/lkml/2020/4/6/320 LKML Additional Information]

The rk3399 pcie controller throws either a synchronous abort or a SError when a pcie device sends an unknown message.

The error type is determined by which cpu cluster handles the message.

=== Virtualization ===
The PCIe controller on the rk3399 is not behind an IOMMU.
This means it is not possible to safely pass through PCIe devices to a virtual machine.

= 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 provide 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 4096x2160 with AFBC supported；The other supports 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support display, 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
* 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

== Working Features ==
{| class="wikitable sortable"
! style="font-weight:bold;" | Feature/Option
! style="font-weight:bold;" | Android
! style="font-weight:bold;" | Android Version
! style="font-weight:bold;" | Linux
! style="font-weight:bold;" | Linux Version
! style="font-weight:bold;" | Test/Verify Steps
! style="font-weight:bold;" | Notes
! style="font-weight:bold;" | Product Link
|-
| Pine64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe this will help get this working? https://github.com/avafinger/pine64-touchscreen
| https://pine64.com/?product=7-lcd-touch-screen-panel
|-
| 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/No
|
|
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons.
| https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-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 then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| http://wiki.pine64.org/index.php/ROCKPro64_Main_Page#OTG_mode
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use ATS. https://github.com/tuxd3v/ats
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out what Frank Mankel has done. https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2
|
|-
| 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.
|
|-
| 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 fanctl to control the fan while keeping your CPU cool https://github.com/tuxd3v/fanctl
| 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
* [http://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [http://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [http://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [http://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [http://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [http://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [http://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]
* [http://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [http://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [http://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.
** [http://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
** [http://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
** [http://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCK64 RoHS Report]

= Datasheets for Components and Peripherals =
* Rockchip RK3399 SoC information:
** [http://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
** [http://opensource.rock-chips.com/images/2/28/Rockchip_RK3399_Datasheet_V1.8-20180529.pdf Rockchip RK3399 Datasheet V1.8]
** [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
** [http://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]
* LPDDR4 (200 Balls) SDRAM:
** [http://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]
* eMMC information:
** [http://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [http://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [http://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [http://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
** [http://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:
** [http://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [http://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]
* Heatsink related info:
** [http://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
** [http://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]
* Wireless related info:
** [[Media:AP6356 datasheet V1.0 07252014.pdf|AMPAK AP6356 2x2 Wi-Fi + Bluetooth4.1 Datasheet]]
* Ethernet related info:
** [http://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]
* Peripheral related info:
** [http://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]
* Remote control button mapping
** [http://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]

= 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
*[http://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[http://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

= 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.]

{{ Category:ROCKPro64 }}

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

User:Aberts10/Cameras

2020-10-21T13:13:14Z

Abcde: typo

===PinePhone===
===PineTab===
===PineCube===
===RockPro64===
====ROCKPro64 13 MEGAPIXEL CAMERA MODULE – Standard Model====
[https://pine64.com/product/rockpro64-13-megapixel-camera-module-standard-model/ Store] page
====ROCKPro64 13 MEGAPIXEL CAMERA MODULE – m12 Mount Lens model====
[https://pine64.com/product/rockpro64-13-megapixel-camera-module-m12-mount-lens-model/ Store] page
===A64+===
====PINE64 5 MEGAPIXEL CAMERA MODULE====
[https://pine64.com/product/pine64-5-megapixel-camera-module/ Store] page

User:Aberts10/Cameras

2020-10-21T13:12:40Z

Abcde: added more cameras

===Pinephone===
===PineTab===
===PineCube===
===RockPro64===
====ROCKPro64 13 MEGAPIXEL CAMERA MODULE – Standard Model====
[https://pine64.com/product/rockpro64-13-megapixel-camera-module-standard-model/ Store] page
====ROCKPro64 13 MEGAPIXEL CAMERA MODULE – m12 Mount Lens model====
[https://pine64.com/product/rockpro64-13-megapixel-camera-module-m12-mount-lens-model/ Store] page
===A64+===
====PINE64 5 MEGAPIXEL CAMERA MODULE====
[https://pine64.com/product/pine64-5-megapixel-camera-module/ Store] page

PineTime FAQ

2020-10-21T13:06:56Z

Abcde: added open/closed version info.

=== Does PineTime run Linux? ===

No. [https://forum.pine64.org/showthread.php?tid=8112 Please read this forum article] for information about Linux on PineTime. Also check out the article [https://lupyuen.github.io/pinetime-rust-mynewt/articles/pinetime "PineTime doesn't run Linux... But that's OK!"]

=== Why are there two versions of the Pinetab in the store? ===
=== Why can I only buy the closed version in a 3-pack, and the open version per one? ===

TL:DR: The open PineTime is to develop on, The closed one only for production use, because of firmware uploads. That is why they are sold per 3.

In the current situation in development there are some reasons to want to be sure you only experiment with an open device. If you install the wrong firmware, your device could be bricked, until you find a way to open it, which will likely damage the device.
The idea is that if you want to develop an application for the PineTime, you will be testing it out first, and only after you know for sure your new firmware is well tested, you will install it on deployment devices. If you are in the deploy stage, having more than one PineTime is likely the point. So to prevent people from locking themselves out at the first test, it was decided to sell the closed version only as a pack of 3. Development can be done on an open device, so any issues can be easily handled.

=== How long does it take to ship my PineTime? ===

That depends on whether you chose for Standard or Express shipping. Standard shipping for the dev kit may take up to a few weeks.

=== How do I install new software on PineTime? ===

The nRF Connect mobile app (Android and iOS) may also be used to update the firmware on your PineTime. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#download-and-test-our-pinetime-firmware "Download and Test Our PineTime Firmware"]

Also see [[Reprogramming_the_PineTime|this page to see various methods of reprogramming the devkit PineTime the wired way]].

If you have a Sealed PineTime, flash only Certified PineTime Firmware to your PineTime. If you flash non-Certified PineTime Firmware, your Sealed PineTime may be bricked permanently.

The only Certified PineTime Firmware available today is [https://github.com/JF002/Pinetime/releases/tag/0.8.2 InfiniTime 0.8.2]. Download the file "dfu-0.8.2.zip" under "Assets" and flash to PineTime with nRF Connect. Refer to the instructions here: [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#download-and-test-our-pinetime-firmware "Download and Test Our PineTime Firmware"]

Remember to validate the firmware after flashing: Swipe up to show the menu, tap the Ticks icon, tap "Validate"

=== My PineTime arrived, now what? ===

You should start by testing out all the features of the watch, to make sure everything works. Power it on and check the display.

PineTime is shipped with InfiniTime firmware. Press the watch button to show the clock, then swipe up on the touchscreen to reveal the menu.

On your Android phone, install the nRF Connect mobile app to sync the date and time with PineTime. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#set-pinetime-date-and-time-with-nrf-connect "Set PineTime Date and Time with nRF Connect"] (nRF Connect on iOS can't be used for setting the date and time, because it doesn't implement the GATT Time Service)

Download the latest Certified PineTime Firmware (see the previous question) and flash to PineTime with nRF Connect. Refer to the instructions here: [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#download-and-test-our-pinetime-firmware "Download and Test Our PineTime Firmware"]

Remember to validate the firmware after flashing: Swipe up to show the menu, tap the Ticks icon, tap "Validate"

=== What's the OS that's preinstalled on the PineTime by default? ===

PineTime ships with the open source [https://github.com/JF002/Pinetime InfiniTime firmware].

To support firmware update and rollback, PineTime includes the open source [https://lupyuen.github.io/pinetime-rust-mynewt/articles/mcuboot MCUBoot Bootloader].

=== Can we use this OS or its source code? ===

Yes, [https://github.com/JF002/Pinetime InfiniTime] and the [https://lupyuen.github.io/pinetime-rust-mynewt/articles/mcuboot MCUBoot Bootloader] are open source.

=== Why is the back exposed? Is it supposed to snap on? ===

The back cover of the PineTime dev kit is exposed so that you can flash and debug the device with the SWD pins. The main unit and cover does not snap (lock) together. If you want to attach the back cover anyway, you can use glue or tape.

=== What hardware should I use to flash code to the PineTime? ===

There are several ways you can do this, check out [[Reprogramming the PineTime]]

=== How do I connect the PineTime to a programmer? ===

Here's how: [[PineTime devkit wiring]]

=== How do I set the time on PineTime? ===

You can use either nRF Connect, custom GadgetBridge build or the proprietary Da Fit app. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#set-pinetime-date-and-time-with-nrf-connect "Set PineTime Date and Time with nRF Connect"]

=== Is there a standard agreed method of pushing OTA updates so that one could seal the PineTime dev kit nicely? ===

InfiniTime supports firmware updates over Bluetooth LE with the nRF Connect mobile app. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#download-and-test-our-pinetime-firmware "Download and Test Our PineTime Firmware"]

=== My PineTime's screen shows garbage, how do I fix it? ===

This is usually caused by unplugging the device after it has booted, it needs to be reinitialised. To do so just restart the watch by removing power to it.

=== I have experience developing on Arduino. How does the PineTime compare? ===

To learn programming on PineTime, [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud check out this article]

Arduino provides the Arduino IDE (or you use the avr-gcc and avrdude command-line tools) which you can use to compile and upload code to an Arduino board. The PineTime and its ARM processor doesn't have this, so you'll have to familiarize yourself with tools like GCC for ARM, and OpenOCD. Some experience with Arduino does translate over to the PineTime, especially if you've worked with LCD's, or SPI. The PineTime is at least four times faster than an Arduino Uno (even faster at certain specific workloads due to hardware acceleration), and it has 32 times more RAM and 16 times more flash storage.

[https://github.com/lupyuen/ Lup Yuen Lee] (just call him Lup, rhymes with "Up") has written many articles on PineTime programming. [https://lupyuen.github.io/ Check out the articles here]

=== Can I code firmware for PineTime without an actual PineTime? ===

Yes, you may code PineTime Watch Faces and preview them in a web browser (thanks to WebAssembly)...

[https://lupyuen.github.io/pinetime-rust-mynewt/articles/simulator PineTime Simulator]

Then flash your firmware remotely to a real PineTime via Telegram, and watch your firmware run in a live video stream...

[https://github.com/lupyuen/remote-pinetime-bot/blob/master/README.md Remote PineTime]

=== What do I need for building PineTime firmware locally on my computer? ===

Most flavours of PineTime firmware (InfiniTime, Hypnos, Klok, wasp-os) will build fine on Linux (x64, Arm32, Arm64) and macOS. Just follow the instructions provided.

Download version 9-2020-q2-update of the [https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads Arm Embedded Toolchain arm-none-eabi-gcc]. Other versions of gcc may have problems building the firmware correctly.

On Windows, install [https://docs.microsoft.com/en-us/windows/wsl/about Windows Subsystem for Linux (WSL)] and execute the build steps inside the WSL Terminal (instead of the Windows Command Prompt). USB Programmers (like ST-Link and JLink) are not supported in WSL, so use the Windows Command Prompt to flash your built firmware to PineTime.

[https://github.com/lupyuen/pinetime-rust-mynewt/blob/master/README.md pinetime-rust-mynewt] firmware for PineTime supports building and flashing via the Windows Command Prompt (no need for MinGW and Docker).

=== Can I use Pinebook Pro for developing PineTime? ===

Yes, use version 9-2020-q2-update of the [https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads Arm Embedded Toolchain arm-none-eabi-gcc]. Other versions of gcc may have problems building the firmware correctly.

=== What is Arm Semihosting? ===

We use the SWD (Single Wire Debug) protocol created by Arm for flashing and debugging PineTime's nRF52832 microcontroller, which contains an Arm CPU. (SWD is derived from standard JTAG, but with fewer wires) With Arm CPUs you can trigger a software breakpoint, and allow the debugger (OpenOCD) to do something really nifty: Display a message, read console input, dump out a file, even read a file. That's called Arm Semihosting. [http://www.keil.com/support/man/docs/armcc/armcc_pge1358787046598.htm More about Arm Semihosting]

=== What is OpenOCD? ===

OpenOCD is Open On-Chip Debugger. It's the software that drives your microcontroller debugger/flasher. We need it for running any kind of flashing and debugging with Pi or ST-Link. gdb talks to OpenOCD for debugging firmware. gdb also works with VSCode for debugging firmware visually. [http://openocd.org/doc-release/html/About.html#What-is-OpenOCD_003f More about OpenOCD]

Please use [https://xpack.github.io/openocd xPack OpenOCD] with PineTime. Other versions of OpenOCD seem to have problems with PineTime.

=== How do I remove flash protection? ===

PineTime watches shipped before 20 Sep 2020 have flash protection enabled.

The flash protection can be removed using multiple different methods. If you don't have anything except the PineTime, not even a Raspberry Pi, then you have to order a programmer online: you can use a J-Link, CMSIS-DAP dongle and various other programmers. See [[Reprogramming_the_PineTime|this page to see various methods of reprogramming the PineTime]].

If your PineTime was shipped after 20 Sep 2020, you don't need to remove flash protection. They are shipped with flash protection disabled. You can flash and debug PineTime right away with ST-Link, JLink and Raspberry Pi.

=== Why can't you use ST-Link to remove nRF52 Flash Protection? ===

Because ST-Link is a High Level Adapter. It doesn't really implement all SWD functions, just a subset (probably to keep the price low). More details in the section "Why Visual Studio Code with ST-Link (instead of nRFgo Studio with J-LINK)" in the article [https://medium.com/@ly.lee/coding-nrf52-with-rust-and-apache-mynewt-on-visual-studio-code-9521bcba6004?source=friends_link&sk=bb4e2523b922d0870259ab3fa696c7da "Coding nRF52 with Rust and Apache Mynewt on Visual Studio Code"].

=== Since we need a low level SWD adapter like Raspberry Pi anyway, can we do everything on a Pi instead of ST-Link + Windows? ===

Yes, Raspberry Pi works for flashing and debugging PineTime, even for removing flash protection. We have a special version of OpenOCD called OpenOCD SPI that talks to PineTime's SWD port over SPI (without bit-banging). See [https://github.com/lupyuen/pinetime-updater/blob/master/README.md PineTime Updater]

=== Is there a 3D model of PineTime available somewhere? ===

Not yet. Someone did design a cover you can snap on to keep the back shut. [https://www.thingiverse.com/thing:4172849 More details]

=== Are there any alternatives to the wrist band provided with the PineTime? ===

No, but PineTime accepts standard 20mm wrist band that is widely available by a third party.

Note that some sellers have a different point of view on what standard is. So you should always check the fitting to make sure it looks like the one used by PineTime.

=== I'm stuck. How can I get help? ===

Chat with the PineTime Community on [[PineTime#Community|Matrix / Discord / Telegram / IRC]] (They are bridged into a single chatroom)

[[Category:PineTime]]

Main Page

2020-10-20T08:29:08Z

Abcde: added clusterboard

PINE64 is a community-driven company focused on creating high-quality, low cost ARM devices for businesses and individuals around the globe. PINE64 made its debut with the [[PINE_A64|Pine A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large and active community and offers a variety of resources for businesses and hobbyists to take advantage of their projects. To learn more about PINE64 and the available devices, please visit the main [https://www.pine64.org/ PINE64 website].

= Devices =

* [[PINE A64]]
* [[PINE A64-LTS/SOPine]], [[SOPine_Clusterboard | Clusterboard]]
* [[PINE H64]]
* [[PineCube]]
* [[PinePhone]]
* [[PineTab]]
* [[PineTime]]
* [[Pinebook Pro]]
* [[Pinebook]], [[1080P Pinebook]]
* [[Pinecil]]
* [[ROCK64]]
* [[ROCKPro64]]
* [[SOEdge]]

= Community and Support =
PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms which are all bridged together - messages sent via one platform will be sent to all other platforms automatically. The community chat platforms are:

'''Matrix'''
: [https://riot.im/app/#/room/#pine64:matrix.org #pine64:matrix.org] - General room
: [https://riot.im/app/#/room/#rock64:matrix.org #rock64:matrix.org] - ROCK64 / ROCKPro64 room
: [https://riot.im/app/#/room/#pinebook:matrix.org #pinebook:matrix.org] - Pinebook and Pinebook Pro room
: [https://riot.im/app/#/room/#pinephone:matrix.org #pinephone:matrix.org] - PinePhone room
: [https://riot.im/app/#/room/#pinetab:pine64.org #pinetab:matrix.org] - PineTab room
: [https://riot.im/app/#/room/#pinetime64:matrix.org #pinetime64:matrix.org] - PineTime room
: [https://riot.im/app/#/room/#offtopic64:matrix.org #offtopic64:matrix.org] - Off-topic room

'''IRC'''
: Server: [ircs://irc.pine64.org irc.pine64.org], type <code>/list</code> to see all channels (web IRC: https://www.pine64.org/web-irc/)

'''Discord'''
: [https://discordapp.com/invite/DgB7kzr Discord invite link]

'''Telegram'''
: [https://t.me/PINE64_News Pine64 News group]
: [https://t.me/mtrx_pine64 General group]
: [https://t.me/mtrx_rock64 ROCK64 / ROCKPro64 group]
: [https://t.me/mtx_pinebook Pinebook and Pinebook Pro group]
: [https://t.me/pinephone PinePhone group]
: [https://t.me/PineTab PineTab group]
: [https://t.me/pinetime PineTime group]
: [https://t.me/pine64offtopic Pine64 off-topic]

'''Forums'''
: Official [https://forum.pine64.org/ PINE64 Forum]

'''Reddit'''
: Official [https://www.reddit.com/r/PINE64official/ PINE64 Reddit]
: Official [https://www.reddit.com/r/PinePhoneOfficial/ PinePhone Reddit]

= Helpful Information for Beginners =
Sections dedicated to the very beginners who are just getting started in the SBC and ARM64 world. If you're just starting out and having issues with getting going, please consider browsing both sections for pointers.

'''Getting Started'''
: [[NOOB]] - Basic information on how to flash SD cards and eMMC modules as well as handling your devices.

'''Project Ideas'''
: [[Project]] - A variety of well-documented PINE64 projects to serve as inspiration.

SOEDGE

2020-10-19T18:47:38Z

Abcde: added category

== Software and OS Image Downloads ==
=== [[SOEdge_Software_Release]] ===

[{{fullurl:SOEdge_Software_Release#BSP}} http://files.pine64.org/sw/pine64_installer/json/penguin.png] [[SOEdge_Software_Release#BSP|'''BSP''']]

== [[Accessories_Step_by_Step_Guides|Accessories Step-by-Step Guides]] ==
Under [[Accessories_Step_by_Step_Guides|'Guides for model A baseboard accessories']] you can find instructions and guides concerning:
* Enclosures
* Bluetooth and WiFi module
* Real Time Clock (RTC) battery
* Real Time Clock (RTC) battery holder
* First and third party cases
* Featured 3D printed cases (and more)

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

=== CPU Architecture ===
* [http://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Dual-core ARM Cortex-A35 Processor@1600-2000Mhz]
* A power-efficient ARM 64-Bit Armv8-A architecture
* AArch32 for full backward compatibility with Armv7
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function
* Support Large Physical Address Extensions(LPAE)
* VFPv4 Floating Point Unit
* 32KB L1 Instruction cache and 32KB L1 Data cache
* AArch64 for 64-bit support and new architectural features
* TrustZone security technology
* Neon Advanced SIMD
* DSP and SIMD extensions
* VFPv4 Floating point
* Hardware virtualization support
* 128KB L2 cache

=== Neural Process Unit NPU Capability ===
* [https://www.verisilicon.com/en/IPPortfolio/VivanteNPUIP NPU IP from Verisilicon Vivantee]
* Support max 1920 Int8 MAC operation per cycle
* Support max192 Int16 MAC operation per cycle
* Support max 64 FP16 MAC operation per cycle
* 512KB internal buffer
* One isolated voltage domain to support DVFS
* [https://github.com/VeriSilicon/acuity-models Acuity models Github]

[[File:Vivante_Acuity_SDK.jpg]]

=== System Memory ===
* RAM Memory Variants: 2GB DDR4.
* Storage Memory: SPI Flash and optional eMMC module from 16GB up to 128GB

== SOEdge Baseboard Features ==

=== Network ===
* 10/100/1000Mbps Etherne
* WiFi 802.11 b/g/n with Bluetooth 4.0 (optional)

=== Storage ===
* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* USB - 2 USB2.0 Host port

=== Expansion Ports ===
* DSI - Display Serial Interface, 4 lanes MiPi, up to 1080P
* CSI - CMOS Camera Interface up to 5 mega pixel
* TP - Touch Panel Port, SPI with interrupt
* RTC - Real Time Clock Battery Connector
* VBAT - Lithium Battery Connector with temperature sensor input
* Wifi/BT Module Header - SDIO 3.0 and UART
* 2x20 pins "Pi2" GPIO Header
* PCIe 2x open ended slot

== SOEdge Module and Baseboard Information, Schematics, and Certifications ==
* Model "A" Baseboard Dimensions: 133mm x 80mm x 19mm
* Input Power: DC 12V @ 3A 5.5OD/2.1ID Barrel DC Jack connector

* SOEdge Module Schematic:
** [http://files.pine64.org/doc/SOEdge/SOEdge-Schematic-v2.0-190919.pdf SOEdge Module ver 2.0 20190919 Schematic]
** [http://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-topplace.pdf SOEdge Module ver 2.0 20190919 PCB Component Placement Top PDF file]
** [http://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-bottomplace.pdf SOEdge Module ver 2.0 20190919 PCB Component Placement Bottom PDF file]
** [http://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-topplace.dxf SOEdge Module ver 2.0 20190919 PCB Component Placement Top Drawing file]
** [http://files.pine64.org/doc/SOEdge/SoEdge-PCB-placement-v2.0-bottomplace.dxf SOEdge Module ver 2.0 20190919 PCB Component Placement Bottom Drawing file]
** [http://files.pine64.org/doc/SOEdge/SOEdge%20Pin%20Assignments%20ver%201.00.xlsx SOEdge Module Pin Assignment ver 1.0 in Excel format(includes comparison chart to SOPine)]
** [http://files.pine64.org/doc/SOEdge/SOEdge%20Pin%20Assignments%20ver%201.00.ods SOEdge Module Pin Assignment ver 1.0 in Open Document format(includes comparison chart to SOPine)]
* SOEdge Model "A" Baseboard Schematic and PCB Board Resource:
** [http://files.pine64.org/doc/SOEdge/SoEdge_Baseboard%20Schematic%20Model%20A-20200513.pdf SOEdge Model "A" Baseboard Schematic 20200513 PDF file]
** [http://files.pine64.org/doc/SOEdge/SoEdge_Baseboard_PCB_layout_Model_A2020-05-31.pdf SOEdge Model "A" Baseboard PCB Layout PDF file]
* SOEdge Neural AI Stick Schematic:
** [http://files.pine64.org/doc/SOEdge/SOEdge%20Neural%20AI%20Stick%20Schematic_V10.pdf SOEdge Neural AI Stick PDF file]
* SOEdge/SOPine/PINE A64 Wifi/BT module Schematic
** [http://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf PINE A64 Wifi/BT Module Schematic]
* SOEdge module together with model "A" baseboard Certification:
** Disclaimer: Please note that SOEdge module is not a "final" product and in general certification is not necessary. However, SOEdge module still submits the mpdel A baseboard for FCC, CE, and ROHS certifications and obtain the certificates to prove that can pass the testing. Please note, a final commercial product needs to perform its own testing and obtain its own certificate.
** Not yet available

== Datasheets for Components and Peripherals ==
* Rockchip RK1808 SoC information:
** [http://opensource.rock-chips.com/images/4/43/Rockchip_RK1808_Datasheet_V1.2_20190527.pdf Rockchip RK1808 ver 1.2 datasheet]
* Rockchip RK809 PMU (Power Management Unit) information:
** [https://rockchip.fr/RK809%20datasheet%20V1.01.pdf Rockchip RK809 PMIC Datasheet]
* DDR4 information:
** [http://files.pine64.org/doc/datasheet/SOEdge/Micron%208Gb_DDR4_SDRAM.pdf Micron DDR4 Datasheet]
* eMMC information:
** [http://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [http://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [http://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [http://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
** [http://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:
** [http://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [http://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]
* '''SOEdge Related:'''
** 5MPixel CMOS Camera module information:
*** [http://files.pine64.org/doc/datasheet/pine64/YL-PINE64-4EC.pdf PINE64 YL-PINE64-4EC 5M Pixel CMOS Image Sensor Module (Description in Chinese)]
*** [http://files.pine64.org/doc/datasheet/pine64/S5K4EC%205M%208%205X8%205%20PLCC%20%20Data%20Sheet_V1.0.pdf S5K4EC 5MP CMOS Image Sensor SoC Module Datasheet]
*** [http://files.pine64.org/doc/datasheet/pine64/S5K4ECGX_EVT1_DataSheet_R005_20100816.pdf S5K4EC 5MP CMOS Image Sensor SoC Chip Datasheet]
*** [http://files.pine64.org/doc/datasheet/pine64/s5k4ec.c S5K4EC 5MP CMOS Image Sensor Driver Source Code in C language]
** LCD Touch Screen Panel information:
*** [http://files.pine64.org/doc/datasheet/pine64/FY07024DI26A30-D_feiyang_LCD_panel.pdf 7.0" 1200x600 TFT-LCD Panel Specification]
*** [http://files.pine64.org/doc/datasheet/pine64/HK70DR2459-PG-V01.pdf Touch Panel Specification]
*** [http://files.pine64.org/doc/datasheet/pine64/GT911%20Capacitive%20Touch%20Controller%20Datasheet.pdf GOODiX GT911 5-Point Capacitive Touch Controller Datasheet]
** Ethernet PHY information:
*** [http://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver for SOEdge model A baseboard]
** Wifi/BT module information:
*** [http://files.pine64.org/doc/Pine%20A64%20Schematic/A64-DB-WIFI-BT-REV%20B.pdf SOEdge/SOPine/PINE A64 Wifi/BT Module Schematic]
*** [http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]
** Enclosure information:
*** [http://files.pine64.org/doc/datasheet/case/playbox_enclosure_20160426.stp Playbox Enclosure 3D file]
*** [http://files.pine64.org/doc/datasheet/case/ABS_enclosure_20160426.stp ABS Enclosure 3D file]
*** [http://files.pine64.org/doc/datasheet/case/pine64%20Die%20Cast%20casing-final.jpg Outdoor Aluminum Cast Dust-proof IP67 Enclosure Drawing]
** Connector information:
*** [http://files.pine64.org/doc/datasheet/pine64/ePH.pdf 2.0mm PH Type connector specification use in Lithium Battery (VBAT) port and RTC Battery port]
*** [http://files.pine64.org/doc/datasheet/pine64/0.5FPC%20Front%20Open%20Connector%20H=1.5.pdf 0.5mm Pitch cover type FPC connector specification use in DSI port, TP port and CSI port]

== SOEdge/SOPine Cluster Board Resource ==
* Cluster board is an hardware open source project and will be available at PINE64 store on late January 2018.
* Please note that this project is not "OSH" compliance.:
** [http://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2.DSN Clusterboard version 2.2 Schematic Capture source file]
** [http://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2_Schematic.pdf Clusterboard version 2.2 Schematic Capture PDF file]
** [http://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2.brd Clusterboard version 2.2 PCB Job source file]
** [http://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD%20V2.2-gerber.rar Clusterboard version 2.2 PCB Gerber file]
** [http://files.pine64.org/doc/clusterboard/PINE64%20CLUSTER%20BOARD_2_2_PCB.pdf Clusterboard version 2.2 PCB Layout PDF file]
** [http://files.pine64.org/doc/clusterboard/clusterboard_20pins_header.jpg Clusterboard 20pins header definition]
** [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH56a43QTfd62c1cd96840f4ec37c60bcf12 Clusterboard 3D drawing in Fusion360]
** [https://myhub.autodesk360.com/ue2b2f72e/g/shares/SH56a43QTfd62c1cd968cd6bc203ac753401?viewState=NoIgbgDAdAjCA0ICGBmARgEwGZIOwGMBaDFADgFNCAWfAJi2o1IFZDmlTSIA2DW8-FTQgAukA Clusterboard PDF drawing]

== Other Resources ==

[[Category:SOEdge]] [[Category:SOPine Clusterboard]] [[Category:SOEdge Baseboard]] [[Category:Rockchip RK1808]]

Reprogramming the PineTime

2020-10-18T23:05:40Z

Abcde: image fix

= Introduction =

The PineTime Dev Kit comes with the back not glued down to allow it to be easily reprogrammed, however the kit does not include an hardware programmer/debugger.

'''Before you can use your debugger/programmer, you probably have to [[PineTime devkit wiring|wire up your pinetime]].'''

There is a bewildering variety of different hardware programmers available but whatever programmer you have there are only a few tasks you will have to learn about:

* Unlock the device
* Upload new software
* Run a debugger

Unlocking the device is a one-time action that is needed to enable to debug port and provide full access to the device. Unlocking the device will erase all existing software from the internal flash.

'''Note: PineTime watches shipped after 20 Sep 2020 do not require unlocking. They are shipped unlocked.'''

= SWD Pinout =

See [[PineTime devkit wiring|PineTime devkit wiring]]

= nrfjprog (for Segger JLink) =

The following steps have been tested with the Segger JLink embedded in the [https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF52-DK NRF52-DK development board].

=== Hookup ===

Connect the Pinetime SWD pins to the debugger (P20 on NRF52-DK)

{| class="wikitable"
!Pinetime
!JLink
|-
|GND
|GND
|-
|SWDCLK
|SWDCLK
|-
|SWDIO
|SWDIO
|-
|VCC (3.3V)
|VTG (target detect)
|}

=== Unlocking the FLASH ===

Unlocking the device and erase the memory.

'''You need to execute this step only once, to remove the read protection on the memory. Note that it will erase the whole flash memory of the MCU!''' :

nrfjprog -f NRF52 --recover

=== Uploading new software ===

1. Program the BLE softdevice (if needed by the firmware). Replace PATH_TO_NRF_SDK by the path where you unzipped the [https://www.nordicsemi.com/Software-and-Tools/Software/nRF5-SDK NRF52 SDK] :

nrfjprog -f NRF52 --program /PATH_TO_NRF_SDK/components/softdevice/s132/hex/s132_nrf52_6.1.1_softdevice.hex --sectorerase

2. Program the firmware (replace firmware.hex by the actual filename of the firmware):

nrfjprog -f NRF52 --program firmware.hex --sectorerase

3. Reset and run the new firmware:

nrfjprog -f NRF52 --reset

= OpenOCD =

OpenOCD, the Open On-Chip Debugger supports multiple different adapters. You can read more about it here: http://openocd.org/

== Adapters ==

These examples allow you to use telnet to issue futher commands to the devkit. Using them you can connect to ''127.0.0.1'' (''localhost'') port ''4444'' using telnet and invoke OpenOCD commands. GDB should also be available on port ''3333''.

You can simplify your life by creating a configuration file that contains the interface, transport, target and speed configuration. Things like CLion also need one to work properly.

If you aren't using the latest version of OpenOCD, you might need to substitute things in these examples with older syntax (e.g. instead of ''adapter speed'' it's ''adapter_khz'').

=== CMSIS-DAP ===

Issue this command to initialize a connection to the devkit:

openocd \
-c 'source [find interface/cmsis-dap.cfg]' \
-c 'transport select swd' \
-c 'source [find target/nrf52.cfg]' \
-c 'adapter speed 8000' \
-c 'init'

=== JLink ===

Start OpenOCD:

openocd \
-c 'source [find interface/jlink.cfg]' \
-c 'transport select swd' \
-c 'source [find target/nrf52.cfg]' \
-c 'adapter speed 8000' \
-c 'init'

=== Raspberry Pi ===

openocd \
-c 'source [find interface/bcm2835spi.cfg]' \
-c 'bcm2835spi_speed 31200' \
-c 'source [find target/nrf52.cfg]' \
-c 'init'

=== STLink ===

Connect PineTime SWD Pins to ST-Link v2 as follows:

{| class="wikitable"
!PineTime
!ST-Link
|-
|GND
|GND
|-
|SWDCLK
|SWDCLK
|-
|SWDIO
|SWDIO
|-
|VCC (3.3V)
|3.3V
|}

[[File:pinetime-stlink.jpg|400px]]

Note that only the bottom row of pins on ST-Link are used.

To flash PineTime with ST-Link on Linux and macOS, use [https://github.com/lupyuen/pinetime-updater/blob/master/README.md PineTime Updater]

[[Frequently_asked_questions_about_the_PineTime|'''ST-Link can't be used to remove nRF52 flash protection''']]

== Unlocking the device ==

If you need to disable access port protection then you can do this using the following commands below.

This can be done in two ways:

Appending this to OpenOCD command line:

-c 'nrf52.dap apreg 1 0x04' -c 'nrf52.dap apreg 1 0x04 0x01' -c 'nrf52.dap apreg 1 0x04'

Or by using the telnet connection, just type in ''telnet localhost 4444'' and then you can issue commands to OpenOCD:

Note: ''Unlocking the device to remove access port protection will erase the contents of flash.''

telnet localhost 4444
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
> nrf52.dap apreg 1 0x04
0x00000000
> nrf52.dap apreg 1 0x04 0x01
> nrf52.dap apreg 1 0x04
0x00000001

(If the ''nrf52.dap'' command cannot be found, try just ''dap'' instead.)

== Uploading new software ==

Just issue this command, replace ''code.hex'' with your own (and cmsis-dap.cfg with an appropriate adapter).

openocd \
-c 'source [find interface/cmsis-dap.cfg]' \
-c 'transport select swd' \
-c 'source [find target/nrf52.cfg]' \
-c 'init' \
-c 'nrf5 mass_erase' \
-c 'program code.hex verify' \
-c 'reset' \
-c 'exit'

= Black Magic Probe =

BlackMagic Probe is an JTAG/SWD adapter with open-source firmware, allowing for it to be ported to a multitude of different boards. One of it's defining features is lack of need for intermediate software such as OpenOCD - one would just need to connect to the GDB server running on the chip and proceed with debugging. For more information, refer to [https://github.com/blacksphere/blackmagic/wiki wiki].

=== Native adapters ===

The native adapters are the official Black Magic family of debug adapters, including the original Black Magic Probe and the Black Magic Probe Mini. By buying the official hardware you are supporting the continued development of the Black Magic Probe software.

Providing your native adapter is running up-to-date firmware then it can be used to program your PineTime.

=== STM32 (Blue Pill) ===

It is possible to flash a popular development board based on STM32F103C8T6 microcontroller, known as Blue Pill, to make a BlackMagic Probe device. For example, one may follow instructions in [https://forum.pine64.org/showthread.php?tid=8816&pid=57095#pid57095 forum post] or [https://gist.github.com/darnel/dac1370d057e176386ca4026418abc2b gist] (mac os). Also, it is possible to use SWD pins on the board to flash other devices, instead using arbitrary pins on the board itself. See [https://buger.dread.cz/black-magic-probe-bmp-on-bluepill-stm32f103c8-minimum-system-development-board.html this link] for more detals.

=== Other hardware ===

The Black Magic Probe firmware can be run on a variety of host devices. See [https://github.com/blacksphere/blackmagic/wiki/Debugger-Hardware BMP Debugger Hardware] for more information.

=== Using the BMP to flash the PineTime ===

Refer to the BMP [https://github.com/blacksphere/blackmagic/wiki/Useful-GDB-commands wiki] for the full description of commands.
Overall, the process on Linux is like following. (/dev/ttyBmpGdb is a symlink created by the udev rule). It's useful to create a gdb script file (or .gdbinit) with following commands:

target extended-remote /dev/ttyBmpGdb
monitor swdp_scan
attach 1
file %firmware file%

Then one may use '''load''' command to flash the firmware, '''compare-sections''' to verify the upload, or '''monitor erase_mass''' to erase the firmware.

Then, proceed with debugging as normal.

= External links and additional tutorials =

* https://github.com/jlukanc1/pinetime-boot-flasher
* https://blog.aegrel.ee/absniffer-cmsis-dap-sniffer.html
* https://blog.dbrgn.ch/2020/5/16/nrf52-unprotect-flash-jlink-openocd/
* https://medium.com/@ly.lee/openocd-on-raspberry-pi-better-with-swd-on-spi-7dea9caeb590
* https://medium.com/@ly.lee/build-and-flash-rust-mynewt-firmware-for-pinetime-smart-watch-5e14259c55

[[Category:PineTime]]

Pinebook Pro

2020-10-18T23:00:24Z

Abcde: logo fix

= User Guide =
== Introducing PineBook Pro ==
[[File:PBP.jpg|400px|thumb|right|Pinebook Pro running Debian with MATE]]

The Pinebook Pro is a Linux and *BSD ARM laptop from [https://www.pine64.org/ PINE64]

It is built to be a compelling alternative to mid-ranged Chromebooks that people convert into Linux laptops. It features an IPS 1080p 14″ LCD panel, a premium magnesium alloy shell, high capacity eMMC storage, a 10,000 mAh capacity battery, and the modularity that only an open source project can deliver.

Key features include: the RK3399 SOC; USB-C for data, video-out and power-in (3A 5V); privacy switches for the microphone, BT/WiFi module, and camera; and expandable storage via NVMe (PCIe 4x) with an optional adapter.

The Pinebook Pro is equipped with 4GB LPDDR4 system memory, high capacity eMMC flash storage, and 128Mb SPI boot Flash. The I/O includes: 1x micro SD card reader (bootable), 1x USB 2.0, 1x USB 3.0, 1x USB type C Host with DP 1.2 and power-in, PCIe 4x for an NVMe SSD drive (requires an optional adapter), and UART (via the headphone jack by setting an internal switch).

The keyboard and trackpad both use the USB 2.0 protocol. The LCD panel uses eDP MiPi display protocol.

Many different Operating Systems (OS) are freely available from the open source community and partner projects. These include various flavors of Linux (Ubuntu, Debian, Manjaro, etc.) and *BSD.

== Software and OS Image Downloads ==

=== Default Manjaro KDE Desktop Quick Start ===

When you first get your Pinebook Pro and boot it up for the first time, it'll come with Manjaro using the KDE desktop. The Pinebook Pro is officially supported by the Manjaro ARM project, and support can be found on the [https://forum.manjaro.org/c/manjaro-arm/78 Manjaro ARM forums.]

On first boot, it will ask for certain information such as your timezone location, keyboard layout, username, password, and hostname. Most of these should be self-explanatory. Note that the hostname it asks for should be thought of as the "codename" of your machine, and if you don't know what it's about, you can make something up (use a single word, all lower case, no punctuation; e.g. "pbpro").

After you're on the desktop, be sure to update it as soon as possible and reboot after updates are finished installing. If nothing appears when you click on the Networking icon in your system tray to connect to your Wi-Fi, ensure the Wi-Fi [https://wiki.pine64.org/index.php/Pinebook_Pro#ANSI_Fn_.2B_F_keys_wrong_for_F9.2C_F10.2C_F11_and_F12 privacy switch] is not disabled.

=== [[Pinebook Pro_Software_Release|Pinebook Pro images]] ===
Under [[Pinebook Pro Software Release|'Pinebook Pro Software Release/OS Image Download Section']] you will find a complete list of currently supported Operating System images that work with the Pinebook as well as other related software.

The list includes OS images and descriptions of:

[{{fullurl:PinebookPro_Software_Release#elementary_OS}} [[File:elementaryLogo.png|125px]]] [[PinebookPro_Software_Release#elementary OS|'''elementary OS 6 (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Manjaro_ARM}} [[File:Manjaro.png|125px]]] [[PinebookPro_Software_Release#Manjaro ARM|'''Manjaro ARM (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Debian_Desktop}} [[File:Debian.png|125px]]] [[PinebookPro_Software_Release#Debian Desktop|'''Debian Desktop (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Bionic_LXDE}} [[File:Lxde.png|125px]]] [[PinebookPro_Software_Release#Bionic LXDE|'''Bionic LXDE (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Bionic_Mate}} [[File:Mate.png|125px]]] [[PinebookPro_Software_Release#Bionic Mate|'''Bionic Mate (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Fedora}} [[File:Fedora1.png|125px]]] [[PinebookPro_Software_Release#Fedora|'''Fedora (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#OpenSUSE}} [[File:Opensuse1.png|125px]]] [[PinebookPro_Software_Release#OpenSUSE|'''OpenSUSE (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Q4OS}} [[File:Q4os.png|125px]]] [[PinebookPro_Software_Release#Q4OS|'''Q4OS (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Armbian}} [[File:Armbian.png|125px]]] [[PinebookPro_Software_Release#Armbian|'''Armbian (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#NetBSD}} [[File:Netbsd.png|125px]]] [[PinebookPro_Software_Release#NetBSD|'''NetBSD (microSD and eMMC Boot)''']]

[{{fullurl:Pinebook_Pro_Software_Release#OpenBSD}} [[File:Puffy_mascot_openbsd.png|125px]]] [[Pinebook_Pro_Software_Release#OpenBSD|'''OpenBSD release for ARM64''']]

[{{fullurl:PinebookPro_Software_Release#Chromium}} [[File:Chromium.jpg|125px]]] [[PinebookPro_Software_Release#Chromium|'''Chromium (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Arch_Linux}} [[File:Archlinux-logo.png|125px]]] [[PinebookPro_Software_Release#Arch_Linux|'''Arch Linux ARM installer (microSD and USB boot)''']]

[{{fullurl:PinebookPro_Software_Release#Android_7.1_microSD}} [[File:Android_7.png|125px]]] [[PinebookPro_Software_Release#Android_7.1_microSD|'''Android 7.1 (microSD Boot)''']]           [{{fullurl:PinebookPro_Software_Release#Android_7.1_eMMC}} [[File:Android_7.png|125px]]] [[PinebookPro_Software_Release#Android_7.1_eMMC|'''Android 7.1 (eMMC)''']]

[{{fullurl:PinebookPro_Software_Release#Daniel_Thompson.27s_Debian_Installer_for_the_Pinebook_Pro}} [[File:Debian.png|125px]]] [[PinebookPro_Software_Release#Daniel_Thompson.27s_Debian_Installer_for_the_Pinebook_Pro|'''Debian Installer for Pinebook Pro''']]

[{{fullurl:Pinebook_Pro_Software_Release#Gentoo_Script_for_Pinebook_Pro}} [[File:GentooLogo.png|125px]]]
[[Pinebook_Pro_Software_Release#Gentoo_Script_for_Pinebook_Pro|'''Gentoo Script for Pinebook Pro''']]

[{{fullurl:PinebookPro_Software_Release#Kali_Linux_for_Pinebook_Pro}} [[File:Kali.jpeg|125px]]] [[PinebookPro_Software_Release#Kali_Linux_for_Pinebook_Pro|'''Kali Script for Pinebook Pro (microSD and eMMC Boot)''']]

=== Quick Links to OS Images Build Sources===
'''Some of the provided OS images are still in beta or nightly build and only fit for testing purposes. These images ought to be avoided for normal usage - use them at your own risk'''
* [https://github.com/ayufan-rock64/linux-build/releases/ ayufan's Linux build repo] (Includes Ubuntu 20.04 Focal Fossa and Debian Buster images. Click 'Assets' at the end of the releases text to view images)
* [https://github.com/ayufan-rock64/chromiumos-build/releases ayufan's Chromium OS build repo]
* [https://github.com/mrfixit2001/debian_desktop/releases mrfixit2001's Linux debian desktop build repo]

== Keyboard ==
The Pinebook Pro is available in two keyboard configurations: ISO and ANSI. Both the keyboard and trackpad in the Pinebook Pro use the USB 2.0 protocol and show up as such in xinput. The keyboard features function (Fn) keys in the F-key row, which include display brightness controls, sound volume, trackpad lock, and other functionality. There is also a custom PINE64 logo key that functions as Menu/Super key. It has also a secondary functionality for setting the privacy switches.

The keyboard firmware binary can be flashed from userspace using the provided open source utility.

Documentation for the keyboard can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]].

=== Typing special characters ===
The [[Wikipedia:British_and_American_keyboards#Other_keyboard_layouts|UK ISO Layout]] does not have dedicated keys for characters like the German umlauts (Ä,Ö,Ü, etc). Certain characters can still be generated by means of either key combinations or key sequences.
{| class="wikitable"
!Character
!Key combination/sequence
|-
|Ä, Ö, Ü, ä, ö, ü
|[[Wikipedia:AltGr_key|[AltGr]]]+'[' followed by [A], [O], [U], [a], [o] or [u]
|-
|µ
|[AltGr]+[m]
|-
|Ø, ø
|[AltGr]+[O], [AltGr]+[o]
|-
|@
|[AltGr]+[q] (as on the German layout)
|-
|ß
|[AltGr]+[s]
|-
|§
|[AltGr]+[S]
|-
|°
|[AltGr]+[)]
|}

=== Privacy Switches ===
There are three privacy switches mapped to the F10, F11 and F12 keys on the Pinebook Pro keyboard. They de/activate the following:

{| class="wikitable"
|+ Privacy switch function and description
! Combination
! Effect
! Description
! Notes
|-
! scope=row | PINE64 logo key+F10
| Microphone Privacy switch || CAPs lock LED blinks. 2 blinks = enabled, 3 blinks = disabled
|-
! scope=row | PINE64 logo key+F11
| WiFi Privacy switch || NUM lock LED blinks. 2 blinks = WiFi enabled / killswitch disabled, 3 blinks = WiFi disabled / killswitch enabled.
| '''Re-enabling requires reboot''' (or a [//forum.pine64.org/showthread.php?tid=8313&pid=52645#pid52645 command line hack to bind/unbind]).
|-
! scope=row | PINE64 logo key+F12
| Camera privacy switch || CAPs lock and NUM lock LEDs blink together. 2 blinks = enabled, 3 blinks = disabled
|}

'''(Press the PINE64 logo key plus F10/F11/F12) for 3 seconds)'''

The keyboard operates on firmware independant of the operating system. It detects if one of the F10, F11 or F12 keys is pressed in combination with the Pine key for 3 seconds. Doing so disables power to the appropriate peripheral, thereby disabling it. This has the same effect as cutting off the power to each peripheral with a physical switch. This implementation is very secure, since the firmware that determines whether a peripheral gets power is not part of the Pinebook Pro’s operating system. So the power state value for each peripheral cannot be overridden or accessed from the operating system. The power state setting for each peripheral is stored across reboots inside the keyboard's firmware flash memory.

== Trackpad ==
The trackpad is a reasonable size, has a matte finish that that your finger can slide along easily, and two actuating buttons. It is the only component of the Pinebook Pro held in place with strong adhesive tape. It supports multi-touch functionality.
Documentation for the trackpad can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]].
The trackpad firmware binary can be flashed from userspace using the provided open source utility (https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater). A fork with more recent changes is also available (https://github.com/jackhumbert/pinebook-pro-keyboard-updater) and may want to be considered instead while feature parity is different.

The trackpad controller is connected to the keyboard controller. All trackpad events go through the keyboard controller and it's software, then to the keyboard controller's USB port. Note that the trackpad does have separate firmware, (which has to be written through the keyboard controller).

'''Everyone with a Pinebook Pro produced in 2019 should update their keyboard and trackpad firmware.'''

Before you start:

Please refer to original documentation for details.

Your Pinebook Pro should be either fully charged or, preferably, running off of mains. This utility will be writing chips on the keyboard and trackpad, so a loss of power during any stage of the update can result in irrecoverable damage to your trackpad or keyboard.

The scripts ought to work on all OSs available for the Pinebook Pro. Some OSs may, however, require installation of relevant dependencies. The instructions below assume a Debian desktop. Newer Pinebook Pro models that come with Manjaro will require a different command to install the proper dependencies.

There are two keyboard versions of the Pinebook Pro: ISO and ANSI. You need to know which model you have prior to running the updater.
Firmware update steps for both models are listed below.

What you will need:

*Your Pinebook Pro fully charged or running off of mains power
*Connection to WiFi
*An external USB keyboard & mouse (or access to the Pinebook Pro via SSH)

'''ISO Model'''

From the terminal command line:

<pre>
git clone https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater
cd pinebook-pro-keyboard-updater
sudo apt-get install build-essential libusb-1.0-0-dev xxd
make
</pre>

Step 1
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-1 iso
sudo reboot
</pre>

Step 2 (after reboot)
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-2 iso
sudo reboot
</pre>

----

'''ANSI Model'''

*NOTE: Running step 1 on the ANSI keyboard model will make the keyboard and trackpad inaccessible until step 2 is ran, so an external keyboard must be connected to complete the update on this model!

From the terminal command line:

<pre>
git clone https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater
cd pinebook-pro-keyboard-updater
sudo apt-get install build-essential libusb-1.0-0-dev xxd
make
</pre>

Step 1
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-1 ansi
sudo reboot
</pre>

Step 2 (after reboot)
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-2 ansi
sudo reboot
</pre>
When done, if some of the keys produce incorrect characters, please check your OS’s language settings. For ANSI users, the default OS shipped with English UK as the default language. You can change it to English US if desired.

=== X-Windows & trackpad settings ===
Some forum members have found that an adjustment to X-Windows will allow finer motion in the trackpad. If you use the '''Synaptic''' mouse/trackpad driver, use this command to make the change live:
<pre>synclient MinSpeed=0.25</pre>
You may experiment with different settings, but 0.25 was tested as helping noticeably. 
 
To make the change persist across reboots, change the file <code>/etc/X11/xorg.conf</code> similar to below:
<pre> Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "MinSpeed" "0.25"
EndSection</pre>
The line <code>Option "MinSpeed" "0.25"</code> is the change. 
 
Another forum user built on the above settings a little, and have found these to be very good:
<pre>synclient MinSpeed=0.25
synclient FingerLow=30
synclient PalmDetect=1
synclient VertScrollDelta=64
synclient HorizScrollDelta=64</pre>

<code>FingerLow</code> has the same value as 'FingerHigh' in one config (30). It is believed to help reduce mouse movement as you lift your finger, but it's unknown whether synaptic works like this.
You may find this config to be comfortable for daily use.
 

The <code>right mouse click</code> is emulated by tapping with two fingers on the trackpad. If you feel that this is not very responsive you can try this value:
<pre> synclient MaxTapTime=250 </pre>.
 

== Power Supply ==
* Input Power: 5V DC @ 3A
* Mechanical: 3.5mm OD / 1.35mm ID, Barrel jack
* USB-C 5V, 15W PD quickcharge
* Only use one power input at a time, barrel jack OR USB-C

== LEDs ==
In total there are four LEDs on the Pinebook Pro, three of which are placed in the top left side of the keyboard, and one near the barrel-port:

:1. The red LED next to the barrel-port indicates charging. It will illuminate when mains power is supplied to the Pinebook Pro from either the standard power supply unit or a USB-C smartphone charger.

:2. The power indicator LED on the Pinebook Pro supports three different colours: green, amber and red. It is also capable of flashing/blinking to indicate activity. In the default Debian with MATE build, green LED means power and red means suspend (amber is unused).

:3. The Num lock, green LED.

:4. The Caps lock, green LED.

(The Num and Caps lock LEDs have a secondary function. When the privacy switches get activated they blink to confirm that switch has been activated.)

== Webcam ==
* Streaming video resolutions supported, (un-compressed):
** 320 x 240
** 640 x 480
** 800 x 600
** 1280 x 720
** 1600 x 1200
* Still frame resolutions supported:
** 160 x 120
** 176 x 144
** 320 x 240
** 352 x 288
** 640 x 480
** 800 x 600
** 1280 x 720
** 1600 x 1200
* Some people test with the application Cheese
WIP

== Microphones ==
While it has been said that some Pinebook Pro units contain only one microphone despite having two labeled microphone holes on the outer casing, other units do indeed contain two microphones. It is presently unclear which batches have either configuration; units from the initial community batch of 1000 units (following the initial 100) are believed to contain two, populating both labeled holes.

The wires leading to both microphones connect to the mainboard with a small white plastic connector, located directly adjacent to the ribbon cable attachment point for the keyboard interface.

'''Microphones not working?'''

If pavucontrol input doesn't show microphone activity try the [[Pinebook_Pro#Privacy_Switches]]; once that is set to on do the below; if that still hasn't fixed it you may want to check that the microphone connector is plugged in (see the [[Pinebook_Pro#Technical_Reference]]).

<pre>
run alsamixer from the command line > hit F6 and select the es8316 > hit F4 to get to the capture screen > select the bar labeled ADC >
> increase the gain to 0dB > change the audio profile in pavucontrol to another with input

Additionally:
you may want to modify ADC PGA to get the levels to where you want them
</pre>

== Bluetooth and WiFi ==
[[File:PinebookPro_WirelessIC_Location.jpg|400px|thumb|right|The Pinebook Pro's AP6256 wireless module]]
===Hardware Overview===
The Pinebook Pro contains an AMPAK AP6256 wireless module to provide Wi-Fi (compliant to IEEE 802.11ac) and Bluetooth (compliant to Bluetooth SIG revision 5.0). The module contains a Broadcom transceiver IC, believed to be the BCM43456, as well as the support electronics needed to allow the Wi-Fi and Bluetooth modes to share a single antenna.

The wireless module interfaces with the Pinebook Pro’s system-on-chip using a combination of three interfaces: Bluetooth functionality is operated by serial UART and PCM, while the Wi-Fi component uses SDIO. It is unknown if the module’s Bluetooth capabilites are usable under operating systems that do not support SDIO.

The module’s RF antenna pin is exposed on the mainboard via a standard Hirose U.FL connector, where a coaxial feedline links it to a flexible adhesive antenna situated near the upper right corner of the Pinebook Pro’s battery. As the RF connector is fragile and easily damaged, it should be handled carefully during connection and disconnection, and should not be reconnected frequently.

===Issues===
Problems have been reported with the Wi-Fi transceiver’s reliability during extended periods of high throughput, especially on the 2.4 GHz band. While the cause of this has yet to be determined, switching to the 5 GHz band may improve stability.

Since the Bluetooth transceiver shares both its spectrum and antenna with 2.4 GHz Wi-Fi, simultaneous use of these modes may cause interference, especially when listening to audio over Bluetooth. If Bluetooth audio cuts out frequently, switching to the 5 GHz band – or deactivating Wi-Fi – may help.

===Wi-Fi Capabilities===
Wi-Fi on the Pinebook Pro is capable of reaching a maximum data transfer rate of approximately 433 megabits per second, using one spatial stream. The transceiver does not support multiple spatial streams or 160-MHz channel bandwidths.

The Wi-Fi transceiver supports the lower thirteen standard channels on the 2.4 GHz band, using a bandwidth of 20 MHz. At least twenty-four channels are supported on the 5 GHz band, spanning frequencies from 5180 to 5320 MHz, 5500 to 5720 MHz, and 5745 to 5825 MHz, with bandwidths of 20, 40, or 80 MHz.

Maximum reception sensitivity for both bands is approximately -92 dBm. The receiver can tolerate input intensities of no more than -20 dBm on the 2.4 GHz band, and no more than -30 dBm on the 5 GHz band. Maximum transmission power is approximately +15 dBm for either band, falling further to approximately +10 dBm at higher data transfer rates on the 5 GHz band.

With current available drivers and firmware, the Wi-Fi interface supports infrastructure, ad-hoc, and access-point modes with satisfactory reliability. Monitor mode is not presently supported. Wi-Fi Direct features may be available, but it is unclear how to make use of them under Linux.

Be aware that Linux userspace utilities, such as <code>iw</code>, may report inaccurate information about the capabilities of wireless devices. Parameter values derived from vendor datasheets, or direct testing, should be preferred to the outputs of hardware-querying tools.

===Bluetooth Capabilities===
Bluetooth data transfer speeds have an indicated maximum of 3 megabits per second, but it is unclear what practical data rates can be expected. Audio streaming over Bluetooth is functioning normally, as is networking. Bluetooth Low-Energy functions, such as interacting with Bluetooth beacons, have not yet been tested conclusively.

The Bluetooth transceiver supports all 79 channel allocations, spanning frequencies from 2402 MHz to 2480 MHz. Reception sensitivity is approximately -85 dBm, with a maximum tolerable reception intensity of -20 dBm. Bluetooth transmission power is limited to +10 dBm.

===Disabling Bluetooth===
<pre>
#disable bluetooth once
sudo rfkill block bluetooth &&

#confirm
rfkill
</pre>

<pre>
#disable bluetooth on boot**
sudo systemctl enable rfkill-block@bluetooth
</pre>

<nowiki>**This does not do what one might want on certain distros, Manjaro XFCE for example. Try the below.</nowiki>

<pre>
right click on the bluetooth panel icon > select 'plugins' > PowerManager > configuration > deselect the auto power on option
</pre>

== LCD Panel ==
* Model: BOE NV140FHM-N49
* 14.0" (35.56cm) diagonal size
* 1920x1080 resolution
* 60hz refresh rate
* IPS
* 1000:1 contrast
* 250nt brightness
* 63% sRGB coverage
* 6 bit colour
* 30 pin eDP connection

Some people have tested hardware video decode using the following;
<pre>ffmpeg -benchmark -c:v h264_rkmpp -i file.mp4 -f null -</pre>

== External ports list ==
Here are a list of the external ports. See [[Pinebook_Pro#Expansion_Ports|Technical Reference - Expansion Ports]] for port specifications.
* Left side
** Barrel jack for power, (with LED)
** USB 3, Type A
** USB 3, Type C
* Right side
** USB 2, Type A
** Standard headset jack
** MicroSD card slot

== Using the UART ==
[[File:PBPUART.jpeg|400px|thumb|right|Headphone jack UART wiring reference.
 Swapping the tx and rx around from this also works and is more traditional.
 See [http://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf this] official Pine64 .pdf.]]

UART output is enabled by flipping the UART switch to the ON position (item 9). To do so you need to remove the Pinebook Pro's bottom cover - please follow [https://wiki.pine64.org/index.php/Pinebook_Pro_Main_Page#Accessing_the_Internals_-_Disassembly_and_Reassembly proper disassembly and reassembly protocol]. The OFF position is towards the touchpad, the ON position is towards the display hinges.

With the UART switch in the ON position, console is relayed via the audiojack and the laptop's sound is turned OFF. Please ensure that you are using a 3.3v interface (such as the CH340, FTDI-232R, or PL2303, which are sold in both 3.3v and 5v variants) to avoid damage to the CPU.

Insert the USB plug of the cable into an open USB port on the machine which will monitor. Run the following in a terminal:

<code>
$ lsusb
</code>

you should find a line similar to this:

<code>
Bus 001 Device 058: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
</code>

You may have to clean the USB contacts of the Serial cable to get a good connection if you do not find that line.

The audio jack of the Serial cable should be fully inserted into the Pinebook Pro audio port.

Serial output should now be accessible using screen, picocom or minicom (and others).
Examples:

<code>
screen /dev/ttyUSB0 1500000

picocom /dev/ttyUSB0 -b 1500000

minicom -D /dev/ttyUSB0 -b 1500000</code>

Old versions of U-Boot do not use the UART for console output. <strike>The console function is activated by the Linux kernel. Thus, if you use a non-Pinebook Pro Linux distro and want the UART as a console, you have to manually enable it.</strike>

== Using the optional NVMe adapter ==
The optional NVMe adapter allows the use of M.2 cards that support the NVMe standard, (but not SATA standard). The optional NVMe M.2 adapter supports '''M''' & '''M'''+'''B''' keyed devices, in both 2242 & 2280 physical sizes, the most common ones available. In addition, 2230 & 2260 are also supported, though NVMe devices that use those sizes are rare.

Once you have fitted and tested your NVMe drive, please add a note to this page [[Pinebook_Pro_Hardware_Accessory_Compatibility]] to help build a list of tried and tested devices.

=== Installing the adapter ===
The V2.1-2019-0809 SSD adapter that shipped with the initial Pinebook Pro batches had significant issues. A repair kit will be shipped to address those issues.
(If necessary, it can be modified to work. There is [https://forum.pine64.org/showthread.php?tid=8322&pid=52700#pid52700 an unofficial tutorial on the forums] describing these modifications.)

The updated SSD adapter, labeled V2-2019-1107, takes into account the prior problems with trackpad interference. New orders as of Feb. 22nd, 2020 will be the updated adapter.

Actual installation instructions are a work in progress. Unofficial instructions for installing V2-2019-1107 can be found [http://eli.gladman.cc/blog/2020/06/23/pine-book-pro-nvme.html here].

=== Post NVMe install power limiting ===
Some NVMe SSDs allow reducing the maximum amount of power. Doing so may reduce the speed, but it may be needed in the Pinebook Pro to both improve reliability at lower battery levels. And to reduce power used, to maintain battery life.
Here are the commands to obtain and change the power settings. The package 'nvme-cli' is required to run these commands. The example shows how to find the available power states, and then sets it to the lowest, non-standby setting, (which is 3.8 watts for the device shown);
<pre>$ sudo nvme id-ctrl /dev/nvme0
NVME Identify Controller:
...
ps 0 : mp:9.00W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
ps 1 : mp:4.60W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
ps 2 : mp:3.80W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
ps 3 : mp:0.0450W non-operational enlat:2000 exlat:2000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
ps 4 : mp:0.0040W non-operational enlat:6000 exlat:8000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-

$ sudo nvme get-feature /dev/nvme0 -f 2
get-feature:0x2 (Power Management), Current value:00000000
$ sudo nvme set-feature /dev/nvme0 -f 2 -v 2 -s
set-feature:02 (Power Management), value:0x000002</pre>
Some NVMe SSDs don't appear to allow saving the setting with "-s" option. In those cases, leave off the "-s" and use a startup script to set the non-default power state at boot. 
If you want to test performance without saving the new power setting semi-permanantly, then leave off the "-s" option. 
 
There is another power saving feature for NVMes, APST, (Autonomous Power State Transitions). This performs the power saving & transitions based on usage. To check if you have a NVMe SSD with this feature;
<pre>$ sudo nvme get-feature -f 0x0c -H /dev/nvme0</pre>
Information for this feature, (on a Pinebook Pro), is a work in progress.

=== Using as data drive ===
As long as the kernel in use has both the PCIe and NVMe drivers, you should be able to use a NVMe drive as a data drive. It can automatically mount when booting from either the eMMC or an SD card. This applies to Linux, FreeBSD, and Chromium, using the normal partitioning and file system creation tools. Android requires testing.

=== Using as OS root drive ===
The SoC does not include the NVMe boot code, so the NVMe is not in the SoC's boot order. However, using the [https://github.com/mrfixit2001/updates_repo/blob/v1.1/pinebook/filesystem/mrfixit_update.sh U-Boot update script] from the mrfixit2001 Debian or [https://pastebin.com/raw/EeK074XB Arglebargle's modified script], and [https://github.com/pcm720/rockchip-u-boot/releases the modified u-boot images] provided by forum user pcm720, you can now add support to boot from an NVMe drive. Binary images are useable with SD, eMMC, and [[Pinebook_Pro_SPI|SPI flash]]. For OS images using the mainline kernel, there are a few variants of U-Boot available that also support NVMe as the OS drive. Though these may require writing the U-Boot to the SPI flash for proper use of the NVMe as the OS drive.

The current boot order, per last testing, for this modified U-Boot is:
*MicroSD
*eMMC
*NVMe

For more information, please refer to [https://forum.pine64.org/showthread.php?tid=8439&pid=53764#pid53764 the forum post.]

It is also possible to initially boot off an eMMC or SD card, then transfer to a root file system on the NVMe. Currently, it is necessary to have the U-Boot code on an eMMC or SD card. (A forum member [https://forum.pine64.org/showthread.php?tid=8439 posted here] about using a modified version of U-Boot with NVMe drivers, that uses <code>/boot</code> and <code>/</code> off the NVMe drive. So this may change in the future.)

Please see [[Pinebook_Pro#Bootable Storage|Bootable Storage]].

== Caring for the PineBook Pro ==
=== Bypass Cables ===
The mainboard features two (disconnected by default) bypass cables that are only to be used with the battery disconnected. The female (10) male (6) ends of the bypass cables can be connected to provide power to the mainboard if you need to run the laptop without a battery. Please refer to this [http://files.pine64.org/doc/PinebookPro/PinebookPro_Engineering_Notice.pdf engineering notice].

'''Note that despite the bypass cable being a two conductor cable, it is only used as one. Both wires being soldered together on either side is normal!'''

WARNING: Do not connect the bypass cables with the battery connected. Using the bypass cables with the battery connected can permanently damage the computer.

=== [[Pinebook_Service_Step_by_Step_Guides|Pinebook Service Step-by-Step Guides]] ===
Placeholder for Pinebook Pro specific guides

Under [[Pinebook_Service_Step_by_Step_Guides|'Service Guides for Pinebook']] you can find instructions guides concerning disassembly of:

'''Note: The installation process on Pinebook Pro similar to 14" Pinebook'''

'''Note: The installation process is the reverse order of removal guide'''

* 14″ Pinebook Lithium Battery Pack Removal Guide
* 14″ Pinebook LCD Panel Screen Removal Guide
* 14″ Pinebook eMMC Module Removal Guide

== Using the SPI flash device ==

See [[Pinebook_Pro_SPI]]

The Pinebook Pro comes with a 128Mbit, (16MByte), flash device suitable for initial boot target, to store the bootloader. The SoC used on the Pinebook Pro boots from this SPI flash device first, before eMMC or SD card. At present, April 19, 2020, the Pinebook Pros ship without anything programmed in the SPI flash device. So the SoC moves on to the next potential boot device, the eMMC. ARM/ARM64 computers do not have a standardized BIOS, yet.

Here is some information on using the SPI flash device:

* You need the kernel built with SPI flash device support, which will supply a device similar to: <code>/dev/mtd0</code> 
* The Linux package below, will need to be available: <code>mtd-utils</code> 
* You can then use this program from the package to write the SPI device: <code>flashcp <filename> /dev/mtd0</code> 

Even if you need to recover from a defective bootloader written to the SPI flash, you can simply short pin 6 of the SPI flash to GND and boot. This will render the SoC bootrom unable to read from the SPI flash and have it fall back to reading the bootloader from other boot media like the eMMC or Micro SD card.

The procedures described above are a lot less risky than attaching an external SPI flasher and do not require any additional hardware. 
 
At present, April 19th, 2020, there is no good bootloader image to flash into the SPI flash device. This is expected to change, as there are people working on issue.

== FAQ ==
What cool software works out of the box? [[Pinebook Pro OTB Experience]]

= Software tuning guide =
Details on how to get the most out of a Pinebook Pro & its RK3399 SoC.

== Customizing the Pinebook Pro's default Manjaro KDE system ==
=== Watching DRM content (Netflix, etc.) ===
Most paid online streaming services use Widevine DRM to make their content more difficult to pirate. Widevine is not directly supported on Manjaro KDE, however it is still possible to watch DRM content via the "chromium-docker" package which downloads a 32-bit ARM container and installs Chromium with Widevine inside of that. While not space-efficient, or efficient in general, it's the recommended solution for watching this content on your Pinebook Pro. You can install this package with:
<pre>sudo pacman -Sy chromium-docker</pre>
=== Checking GPU capabilities ===
To see what versions of OpenGL and OpenGL ES are supported by the Pinebook Pro, what driver is in use, and what version of the driver is loaded, install the "mesa-demos" package with:
<pre>sudo pacman -Sy mesa-demos</pre>
And then run:
<pre>glxinfo | grep OpenGL</pre>
This will give detailed information about your graphics card and driver, useful for debugging.

=== Better GPU compatibility and performance ===
For better graphics performance, you may install the "mesa-git" package, built and supplied in the Manjaro ARM repos. This lets you bring in the latest features, optimizations, and bugfixes for the graphics driver used by the Pinebook Pro. Installation is as simple as:
<pre>pacman -Sy mesa-git</pre>
Then you may reboot to load the newer driver.

Note that this might also solve graphical glitches that you were seeing previously.

=== OpenGL ES 3.0 support ===
By default, with the current state of the Panfrost GPU driver, the Pinebook Pro supports OpenGL 2.1 and OpenGL ES 2.0. If you want to use OpenGL ES 3.0, you need to set the system-wide environment variable, open the '''/etc/environment''' file with:
<pre>kate /etc/environment</pre>
And then at the bottom of the file, on a new line, add:
<pre>PAN_MESA_DEBUG="gles3"</pre>
Then save the file, entering your password when prompted, and reboot the system. When you check your GPU capabilities, it should report OpenGL ES 3.0 and applications that rely on it should function properly. Note that GLES3 support is currently incomplete and some advanced rendering features may still not work properly.
== Customizing the Pinebook Pro's previously-default Debian system ==
Here are some hints on what you can do to customize the Pinebook Pro's previous factory image (aka [https://github.com/mrfixit2001/debian_desktop mrfixit2001 debian build])

=== Initial user changes, password, name, etc ===
When you first get your Pinebook Pro, you should consider setting strong passwords and making the default account your own.

* Reboot (this is just to ensure all background processes belong to the user are not running... there are other ways to achieve this but this way is easy)
* Once the machine reboots press Alt-Ctrl-F1 to bring up a text terminal
* Login as root (login: root, password: root)
* Set a strong password for the root user using the following command and it's prompts:
<pre># passwd (and follow prompts)</pre>
* Rename the rock user to your prefered username (replace myself with whatever you like):
<pre># usermod -l myself -d /home/myself -m rock</pre>
* Rename the rock group to match your preferred username:
<pre># groupmod -n myself rock</pre>
* Put your name in the account, (replace "John A Doe" with your name):
<pre># chfn -f "John A Doe" myself</pre>
* Set a strong password for the normal user:
<pre># passwd myself</pre>
* Log out of the text terminal:
<pre># logout</pre>
* Press Alt-Ctrl-F7 to go back to the login screen and then login as the normal user
* Open text terminal to fix login error: "Configured directory for incoming files does not exist";
<pre>$ blueman-services</pre>
Select "Transfer" tab and set "Incoming Folder" to myself
OR
If adduser is in distro, this is MUCH easier
sudo adduser $USER ,, fill out requested data
Then,, sudo adduser $USER $GROUP,,, 1 group at a time
To see which groups to add,,, id $USER, id rock

=== Changing the default hostname ===
Debian 9 has a command to allow you to change the hostname. You can see the current settings using;
<pre>> sudo hostnamectl
Static hostname: Debian-Desktop
Icon name: computer
Machine ID: dccbddccbdccbdccbdccbdccbdccbccb
Boot ID: ea99ea99ea99ea99ea99ea99ea99ea99
Operating System: Debian GNU/Linux 9 (stretch)
Kernel: Linux 4.4.210
Architecture: arm64</pre>
To change, use this, (with "My_Hostname" used as the example);
<pre>> sudo hostnamectl set-hostname My_Hostname</pre>
Whence done, you can re-verify using the first example.

Then you should backup and edit your <code>/etc/hosts</code> entry's name;
<pre>> sudo cp -p /etc/hosts /etc/hosts.`date +%Y%m%d`
> sudo vi /etc/hosts
127.0.0.1 localhost
127.0.0.1 My_Hostname
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
127.0.1.1 linaro-alip</pre>

=== Disable Chromium browser's prompt for passphrase & password storage ===

Perform the following steps:

* On the tool bar, hover over the Chromium icon
* Using the right mouse button, select '''Properties'''
* In the '''Command:''' line section, add <code>--password-store=basic</code> before the <code>%U</code>
* Use the '''x Close''' button to save the change
This will of course, use basic password storage, meaning any saved passwords are not encrypted. Perfectly fine if you never use password storage.

=== Changing the boot splash picture ===

The default boot splash picture can be replaced using the following instructions:

* Install '''ImageMagick''' which will do the conversion
<pre>$ sudo apt-get install imagemagick</pre>
* Create a 1920 x 1080 picture. For the best results, use a PNG image (It supports lossless compression).
* From the directory in which your new image is stored run the following commands
* Convert your image to the bootsplash raw format using imagemagick convert.
<pre>$ convert yoursplashimage.png -separate +channel -swap 0,2 -combine -colorspace sRGB RGBO:splash.fb</pre>
* Create a backup copy of your current splash screen
<pre>$ sudo cp /usr/share/backgrounds/splash.fb /usr/share/backgrounds/splash_original.fb</pre>
* Copy your new splash screen into place
<pre>$ sudo cp splash.fb /usr/share/backgrounds/splash.fb</pre>
* Set the correct permissions on the splash.fb file
<pre>$ sudo chmod 644 /usr/share/backgrounds/splash.fb</pre>
* If you do not want to see kernel console text messages, make sure you don't have '''Plymouth''' installed

=== Watching Amazon Prime videos with Chromium ===
When you create a new user, it will be necessary to launch the Chromium browswer with a specific user agent like below;
<pre>chromium-browser --user-agent="Mozilla/5.0 (X11; CrOS armv7l 6946.63.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36"</pre>
There may be more tweaks needed.

=== Enabling text boot time messages ===

By default, most Linux distros have a boot screen with a picture. To see all the boot time messages, use one of the following;

Default Debian
* Backup and edit the U-Boot configuration file:
<pre>cp -p /etc/default/u-boot /etc/default/u-boot.`date +%Y%m%d`
chmod a-w /etc/default/u-boot.`date +%Y%m%d`
vi /etc/default/u-boot</pre>
Remove the '''quiet''' and '''splash''' parameters. Leave everything else alone.
* Update the U-Boot configuration:
<pre>u-boot-update</pre>
* Test and verify you get what you think you should be seeing.
 
Manjaro
* Backup and edit the U-Boot configuration file:
<pre>cp -p /boot/extlinux/extlinux.conf /boot/extlinux/extlinux.conf.`date +%Y%m%d`
chmod a-w /boot/extlinux/extlinux.conf.`date +%Y%m%d`
vi /boot/extlinux/extlinux.conf</pre>
Change '''console=ttyS2,1500000''' to '''console=tty1''' 
Remove the '''bootsplash.bootfile''' option and it's parameter. 
You can add verbose logging by appending '''ignore_loglevel''' to the line where boot splash was. 
Leave everything else alone. 
* Test and verify you get what you think you should be seeing.

== Improving readability ==

Some people find that a 14" LCD screen with 1080p, (1920 x 1080), has text and icons a bit too small. There are things you can do to make the screen easier to use and read. 
* Increase the font size
* Use a font with more pronounced features
* Increase the various window manager sizes (e.g. increase the height of the tool bar)
* Change the color scheme to be easier on the eyes. Higher contrast can help usability.
* Change the window manager's decorations (e.g. use larger icons)
* Use a workspace manager, with one application per workspace
* When at home or office, use an external monitor
* Change the X-Windows DPI
 
However, do not change the resolution of the LCD screen, otherwise you may end up with a blank / black screen. If that happens, see this troubleshooting section for the fix: 
[[Pinebook_Pro#After_changing_builtin_LCD_resolution.2C_blank_screen|Blank screen after changing builtin LCD resolution]]

== Chromium tweaks ==

=== Flags ===

From the [https://github.com/mrfixit2001/updates_repo/blob/v1.8/pinebook/filesystem/default official Debian image]:

<pre>
--disable-low-res-tiling \
--num-raster-threads=6 \
--profiler-timing=0 \
--disable-composited-antialiasing \
--test-type \
--show-component-extension-options \
--ignore-gpu-blacklist \
--use-gl=egl \
--ppapi-flash-path=/usr/lib/chromium-browser/pepper/libpepflashplayer.so \
--ppapi-flash-version=32.0.0.255 \
--enable-pinch \
--flag-switches-begin \
--enable-gpu-rasterization \
--enable-oop-rasterization \
--flag-switches-end
</pre>

Note that in some cases, this may also decrease performance substantially, as observed when using these flags on the Manjaro KDE desktop. Feel free to experiment to find what is smoothest for you personally.

== gVim has performance issue ==
It appears that using GTK3 can cause very slow scrolling, while Vim in a terminal window works fine. 
Simply revert back to using GTK2, (how to do so is somewhat Linux distro-specific).

Another solution may be to run gVim with

GDK_RENDERING=image

environment variable set. It seems that this improves the performance by reverting back to software-only rendering.

== Kernel options ==
Here are some Pinebook Pro & its RK3399 SoC Linux specific options. If kernel version, (or version range specific), it should list that information in the description.

To see if a specific feature is enabled in the current kernel, you can use something like this;

<pre>
$ zgrep -i rockchip_pcie /proc/config.gz
# CONFIG_ROCKCHIP_PCIE_DMA_OBJ is not set
CONFIG_PHY_ROCKCHIP_PCIE=m
</pre>
If it's listed as <code>=m</code>, then it's a module. You can see if the module is loaded with;
<pre>
$ lsmod | grep -i rockchip_pcie
phy_rockchip_pcie 16384 0
</pre>
Note modules are not loaded until needed. Thus, we sometimes check the kernel configuration instead to see if a feature is configured first, then see if it's a module.

=== Hardware video decoding ===
Here is a method to check for hardware video decoding by the VPU. There are special Linux kernel modules that perform this function. 
Older systems, such as the previously-default Debian desktop, use the Rockchip-supplied kernel module <code>rk-vcodec</code>. To check, something like this can be used:
<pre>
$ lsmod | grep rk-vcodec
or
$ zgrep RK_VCODEC /proc/config.gz
CONFIG_RK_VCODEC=y
</pre>
Note that in the above example, the Rockchip video CODEC is not built as a module, but included into the kernel. Thus, it does not show up in the list modules check. 
 

Newer systems may use a different option as in the configuration below:
<pre>
$ zgrep HANTRO /proc/config.gz
CONFIG_VIDEO_HANTRO=m
CONFIG_VIDEO_HANTRO_ROCKCHIP=y
</pre>
  

= Troubleshooting guide =

The important thing is not to panic and if something goes wrong, to stop and consider carefully how to undo something, or, to redo it. This particularly applies when flashing a new operating system or new firmware to the touchpad.

[[Pinebook_Pro_Troubleshooting_Guide]]

= [[Pinebook_Pro_Hardware_Accessory_Compatibility|PineBookPro Hardware Compatibility]] =

Please contribute to the hardware compatibility page, which lists hardware which has been tested with the PBP, whether successful or not!

* [[Pinebook_Pro_Hardware_Accessory_Compatibility#NVMe_SSD_drives|NVMe SSD drives]]
* [[Pinebook_Pro_Hardware_Accessory_Compatibility#USB_hardware|USB hardware]]
* [[Pinebook_Pro_Hardware_Accessory_Compatibility#USB_C_alternate_mode_DP|USB C alternate mode DP]]
* [[Pinebook_Pro_Hardware_Accessory_Compatibility#Other_hardware|Other hardware]]
  
 

= Technical Reference =
== Accessing the Internals - Disassembly and Reassembly ==
[[File:Standoffs.png|400px|thumb|right|Pinebook Screw stand-offs correct placement and location]]

'''WARNING:''' Do not open the laptop by lifting the lid while the Pinebook Pro bottom cover is removed - this can cause structural damage to the hinges and/or other plastic components of the chassis such as the IO port cut-outs.

'''WARNING:''' When removing the back cover plate, use care if sliding fingertips between back cover plate and palm rest assembly. The back cover plate edges are sharp.

'''WARNING:''' When removing the back cover plate, use care to avoid damaging the speakers. They are stuck to the back cover with double-sided tape, and the thin wires are very delicate.

When disassembling the laptop make sure that it is powered off and folded closed. To remove the bottom cover of the Pinebook Pro, first remove the ten (10) Phillips head screws that hold the bottom section of the laptop in place. Remove the cover from the back where the hinges are situated by lifting it up and away from the rest of the chassis.

During reassembly, make sure that the back-screw standoffs are in place and seated correctly. To reassemble the Pinebook Pro, slide the bottom section into place so it meets the front lip of the keyboard section. Secure the front section (where the trackpad is located) in place using the short screws in the front left and right corners. Then proceed to pop in the bottom panel into place. Secure the bottom section (where hinges are located) by screwing in the left and right corners. Then screw in the remaining screws and run your finger though the rim on the chassis to make sure its fitted correctly. Note that the front uses the remaining 2 short screws.

NOTE: The screws are small and should only be finger tight. Too much force will strip the threads. If after installing screws the back cover plate has not seated properly on one side, open the display and hold the base on either side of the keyboard and gently flex the base with both hands in opposing directions. Once the side pops further in, then recheck the screws on that side. If it does not pop back in, just let it be.

NOTE: a basic 3d model to print replacement back-screw standoffs is available on Thingiverse [https://www.thingiverse.com/thing:4226648] pending release of something more definitive

== Pinebook Pro Internal Layout ==
=== Main chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM (21)
* SPI NOR flash memory (29)
* eMMC flash memory (26)
* WiFi/BT module (27)

=== Mainboard Switches and Buttons ===
There are two switches on the main board: disabling the eMMC (24), and enabling UART (9) via headphone jack.

The Reset and Recovery buttons (28): the reset button performs an immediate reset of the laptop. The Recovery button is used to place the device in maskrom mode; this mode allows flashing eMMC using Rockchip tools (e.g. rkflashtools).

[[File:PBPL_S.jpg]]

=== Key Internal Parts ===
{| class="wikitable"
|+ Numbered parts classification and description
! Number
! Type
! Descriptor
|-
! scope=row | 1
| Component || RK3399 System-On-Chip
|-
! scope=row | 2
| Socket || PCIe 4X socket for optional NVMe adapter
|-
! scope=row | 3
| Socket || Speakers socket
|-
! scope=row | 4
| Socket || Trackpad socket
|-
! scope=row | 5
| Component || Left speaker
|-
! scope=row | 6
| Connector || Power bridge connector
|-
! scope=row | 7
| Socket || Keyboard Socket
|-
! scope=row | 8
| Component || Optional NVMe SSD adapter
|-
! scope=row | 9
| Switch || UART/Audio switch - outputs UART via headphone jack
|-
! scope=row | 10
| Socket || Power bridge socket
|-
! scope=row | 11
| Socket || Battery socket
|-
! scope=row | 12
| Component || Trackpad
|-
! scope=row | 13
| Component || Battery
|-
! scope=row | 14
| Component || Right speaker
|-
! scope=row | 15
| Socket || MicroSD card slot
|-
! scope=row | 16
| Socket || Headphone / UART jack
|-
! scope=row | 17
| Socket || USB 2.0 Type A
|-
! scope=row | 18
| Socket || Daughterboard-to-mainboard ribbon cable socket
|-
! scope=row | 19
| Cable || Daughterboard-to-mainboard ribbon cable
|-
! scope=row | 20
| Component || microphone
|-
! scope=row | 21
| Component || LPDDR4 RAM
|-
! scope=row | 22
| Socket || Mainboard-to-daughterboard ribbon cable socket
|-
! scope=row | 23
| Socket || Microphone socket
|-
! scope=row | 24
| Switch || Switch to hardware disable eMMC
|-
! scope=row | 25
| Antenna || BT/WiFI antenna
|-
! scope=row | 26
| Component || eMMC flash memory module
|-
! scope=row | 27
| Component ||BT/WiFi module chip
|-
! scope=row | 28
| Buttons || Reset and recovery buttons
|-
! scope=row | 29
| Component || SPI flash storage
|-
! scope=row | 30
| Socket || eDP LCD socket
|-
! scope=row | 31
| Socket || Power in barrel socket
|-
! scope=row | 32
| Socket || USB 3.0 Type A
|-
! scope=row | 33
| Socket || USB 3.0 Type C
|}

=== Smallboard detailed picture ===

[[File:Pinebook_pro_smallboard.jpg]]

== Bootable Storage ==

=== Boot sequence details ===
The RK3399's mask 32KB ROM boot code looks for the next stage of code at byte off-set 32768, (sector 64 if using 512 byte sectors). This is where U-Boot code would reside on any media that is bootable. 
[[RK3399_boot_sequence|RK3399 boot sequence]]

=== Boot devices ===

The Pinebook Pro is capable of booting from eMMC, USB 2.0, USB 3.0, or an SD card. It cannot boot from USB-C. The boot order of the hard-coded ROM of its RK3399 SoC is: SPI NOR, eMMC, SD, USB OTG.

At this time, the Pinebook Pro ships with a Manjaro + KDE build with [https://www.denx.de/wiki/U-Boot/ uboot] on the eMMC. Its boot order is: SD, USB, then eMMC.

(An update has been pushed for the older Debian + MATE build that improves compatibility with booting other OSs from an SD card. In order to update, fully charge the battery, establish an internet connection, click the update icon in the toolbar, and then reboot your Pinebook Pro. Please see [https://forum.pine64.org/showthread.php?tid=7830 this log] for details.)

Please note that PCIe, the interface used for NVMe SSD on the Pinebook Pro, is not bootable on the RK3399 and therefore is not a part of the boot hierarchy. It is possible to run the desired OS from NVMe by pointing extlinux on the eMMC to rootfs on the SSD. This requires uboot, the Kernel image, DTB, and extlinux.conf
in a /boot partition on the eMMC.

=== eMMC information ===
The eMMC appears to be hot-pluggable. This can be useful if trying to recover data or a broken install. Best practice is probably to turn the eMMC switch to off position before changing modules.

The eMMC storage will show up as multiple block devices:
*mmcblk1boot0 - eMMC standard boot0 partition, may be 4MB
*mmcblk1boot1 - eMMC standard boot1 partition, may be 4MB
*mmcblk1rpmb - eMMC standard secure data partition, may be 16MB
*mmcblk1 - This block contains the user areas

Only the last is usable as regular storage device in the Pinebook Pro.
The device number of "1" shown above may vary, depending on kernel.

If the eMMC module is enabled after boot from an SD card, you can detect this change with the following commands as user "root";
<pre>
echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/unbind
echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/bind
</pre>

== Pinebook Pro Dimensions ==
* Dimensions: 329mm x 220mm x 12mm (WxDxH)
* Weight: 1.26Kg
* Screws
** Philips head type screws
** M2 flat head machine screws (measurements in mm)
** 4 x Small screws (used along the front edge): Head - 3.44, Thread Diameter - 1.97, Thread Length - 2.1, Overall length - 3.05
** 6 x Large screws: Head - 3.44, Thread Diameter - 1.97, Thread Length - 4.41, Overall Length - 5.85
* Rubber Feet
** 18mm diameter
** 3mm height
** Dome shaped

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

=== CPU Architecture ===
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
** Full implementation of the ARM architecture v8-A instruction set (both AArch64 and AArch32)
** ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
** ARMv8 Cryptography Extensions
** VFPv4 floating point unit supporting single and double-precision operations
** Hardware virtualization support
** TrustZone technology support
** Full CoreSight debug solution
** One isolated voltage domain to support DVFS
* Cortex-A72 (big cluster):
** [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
** Superscalar, variable-length, out-of-order pipeline
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
* Cortex-A53 (little cluster):
** [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
** In-order pipeline with symmetric dual-issue of most instructions
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* Cortex-M0 (control processors):
** [https://developer.arm.com/ip-products/processors/cortex-m/cortex-m0 Cortex-M0 CPU]
** Two Cortex-M0 cooperate with the central processors
** Architecture: Armv6-M
** Thumb/Thumb2 instruction set
** 32 bit only

=== 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 provide stunning visuals for UHD content.
* Frequency 650MHz
* Throughput 1300Mtri/s, 10.4Gpix/s
* Graphic interface standards:
** OpenGL® ES 1.1, 1.2, 2.0, 3.0, 3.1, 3.2. (Panfrost has initial support of 3.0 beginning 2020/02/27)
** Vulkan 1.0, using the Mali binary blob. (Panfrost does not support Vulkan as of 2020/06/24)
** OpenCL™ 1.1, 1.2
** DirectX® 11 FL11_1
** RenderScript™

=== System Memory ===
* RAM Memory:
** LPDDR4
** 800MHz, (limited by RK3399)
** Dual memory channels on the CPU, each 32 bits wide
** Quad memory channels on the RAM chip, each 16 bits wide, 2 bonded together for each CPU channel
** 4GB as a single 366 pin mobile RAM chip
* Storage Memory:
** 64GB eMMC module, can be upgraded to an 128GB eMMC module. (The initial PINE64 community build version shipped with a 128GB eMMC.)
** eMMC version 5.1, HS400, 8 bit on RK3399 side
** Bootable
* SPI flash:
** [[Pinebook Pro SPI]]
** 128Mbit / 16MByte
** 1 bit interface
** Bootable, (first boot device, ahead of eMMC & SD card)
** U-Boot images can be made to work, but as of 2020/06/24 there is no standardized image available.

=== Video out ===
* USB-C Alt mode DP
* Up to 3840x2160 p60, dependant on adapter, (2 lanes verses 4 lanes)

=== Expansion Ports ===
* MicroSD card:
** Bootable
** Supports SD, SDHC and SDXC cards, up to 512GB tested. SDXC standard says 2TB is the maximum.
** Version SD3.0, (MMC 4.5), up to 50MB/s
** SD card Application Performance Class 1 (A1), (or better), recommended by some users, for better IOPS
* USB ports:
** 1 x USB 2.0 Type-A Host Port, bootable
** 1 x USB 3.0 Type-A Host Port, 5Gbps, is not bootable
** 1 x USB 3.0 Type-C OTG Port, 5Gbps, (includes laptop charging function), is not bootable
** Note that high power USB devices may not work reliably on a PBP. Or they may draw enough power to drain the battery even when the PBP is plugged into A.C. One alternative is externally powered USB devices.
* Headphone jack switchable to UART console mux circuit

== Additional hardware ==
Hardware that is not part of the SoC.

=== Battery ===
* Lithium Polymer Battery (10,000 mAH)

=== Display ===
* 14.0" 1920x1080 IPS LCD panel
=== Lid closed magnet ===
There is a magnet to detect when the laptop lid is closed, so action can be taken like sleep. This meets up with the Hall sensor on the daughter / small board to detect lid closed.
* The magnet is located on the LCD panel right side, around 1.5 inches up measure from bottom edge.

=== Webcam ===
* Internal USB attached Webcam

=== Audio ===
* 3.5mm stereo earphone/microphone plug
* Built-in microphone
* Built-in stereo speakers:
** Oval in design
** 3 mm high x 20 mm x 30 mm

=== Network ===
* WiFi:
** 802.11 b/g/n/ac
** Dual band: 2.4Ghz & 5Ghz
** Single antenna
* Bluetooth 5.0

=== Optional NVMe adapter ===
* PCIe 2.x, 5GT/s per lane
* 4 PCIe lanes, can not be bifurcated, (however, can be used with 1 or 2 lane NVMe cards)
* '''M''' keyed, though '''M'''+'''B''' keyed devices will work too
* Maximum length for M.2 card is 80mm (M.2 2280). The following sizes will also work: 2230, 2242, 2260
* Power: 2.5W continuous, 8.25W peak momentary
* Does not support SATA M.2 cards
* Does not support USB M.2 cards

== Pinebook Pro Schematics and Certifications ==
* Pinebook Pro Main Board Schematic And Silkscreen:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_mainboard_schematic.pdf Pinebook Pro Main Board ver 2.1 Schematic]
** [https://wiki.pine64.org/images/3/30/Pinebookpro-v2.1-top-ref.pdf Pinebook Pro ver 2.1 Top Layer Silkscreen]
** [https://wiki.pine64.org/images/b/b7/Pinebookpro-v2.1-bottom-ref.pdf Pinebook Pro ver 2.1 Bottom Layer Silkscreen]
* Pinebook Pro Daughter Board Schematic:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_daughterboard_schematic.pdf Pinebook Pro Daughter Board ver 2.1 Schematic]
* Optional Pinebook Pro NVMe Adapter Schematic:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_NVMe-adapter_schematic.pdf Pinebook Pro NVMe Adapter Board ver 2.1 Schematic]
* Serial Console Earphone Jack Pinout:
** [http://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf Pinkbook Serial Console Earphone Jack Pinout]
* Pinebook Pro Case:
** [http://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.pdf AutoCAD PDF File ]
** [http://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.ai AutoCAD AI File ]
** [http://files.pine64.org/doc/PinebookPro/drawings/Pinebook%20Pro%20Principle%20Views.dwg AutoCAD DWG File ]
* Pinebook Pro Certifications:
** [http://files.pine64.org/doc/cert/Pinebook%20Pro%20FCC%20Certificate-S19071103501001.pdf Pinebook Pro FCC Certificate]
** [http://files.pine64.org/doc/cert/Pinebook%20Pro%20CE%20RED%20Certificate-S19051404304.pdf Pinebook Pro CE Certificate]
** [http://files.pine64.org/doc/cert/Pinebook%20Pro%20ROHS%20Compliance%20Certificate.pdf Pinebook Pro RoHS Certificate]

== Datasheets for Components and Peripherals ==
* Rockchip RK3399 SoC information:
** [http://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]
** [http://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]
* LPDDR4 (366 Balls) SDRAM:
** [http://files.pine64.org/doc/datasheet/PinebookPro/micron%20SM512M64Z01MD4BNK-053FT%20LPDDR4%20(366Ball).pdf Micron 366 balls Mobile LPDDR4 Datasheet]
* eMMC information:
** [http://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [http://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [http://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [http://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 64GB/128GB SanDisk eMMC Datasheet]
* SPI NOR Flash information:
** [http://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [https://wiki.pine64.org/images/b/b9/Ds-00220-gd25q127c-rev1-df2f4.pdf GigaDevice 128Mb SPI Flash Datasheet (UPDATED)]
* Wireless related info:
** [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf AMPAK AP6256 11AC Wi-Fi + Bluetooth5 Datasheet]
* Audio Codec (ES8316)
** [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]
* LCD Panel:
** [http://files.pine64.org/doc/datasheet/PinebookPro/NV140FHM-N49_Rev.P0_20160804_201710235838.pdf 14" 1920x1080 IPS LCD Panel datasheet]
* Internal USB 2 hub:
** [https://wiki.pine64.org/images/3/39/GL850G_USB_Hub_1.07.pdf GL850G USB Hub 1.07.pdf]
* Touchpad information:
** [http://files.pine64.org/doc/datasheet/PinebookPro/YX%20HK-9562%20HID%20I2C%20Specification.pdf Touchpad Specification for Pinebook Pro model]
* Keyboard information:
** [https://wiki.pine64.org/images/b/b0/SH68F83V2.0.pdf Sinowealth SH68F83 Datasheet]
** US ANSI: XK-HS002 MB27716023
* Full HD Camera sensor:
** [http://files.pine64.org/doc/datasheet/PinebookPro/HK-2145-263.pdf Full HD Camera module specification in Chinese]
** [http://files.pine64.org/doc/datasheet/PinebookPro/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GalaxyCore GC2145 Full HD Camera Sensor Data Sheet]
* Lithium Battery information:
** [http://files.pine64.org/doc/datasheet/pinebook/40110175P%203.8V%2010000mAh规格书-14.pdf 10000mAH Lithium Battery Specification for 14" model]
* Power path device:
** [https://wiki.pine64.org/images/9/99/Sis412dn.pdf N-MOS / MOSFET]
* NVMe adapter:
** [https://wiki.pine64.org/images/d/d0/Hirose-FH26W-35S-0.3SHW%2860%29-datasheet.pdf Compatible, not OEM! Use FH26-35S-0.3SHW flat flex connector]

== Versions ==
Pinebook Pro v1 and v2 were prototype models that did not make it to the public. The "first batch" (First 100 forum preorders) onward are v2.1. [https://forum.pine64.org/showthread.php?tid=8111]

=Skinning and Case Customization=
* Template files for creating custom skins. Each includes template layers for art placement, and CUT lines.
**[https://drive.google.com/open?id=1UKFlC53DO0GJm3Hz1E_669n_HhI45e4n Case Lid Template]
**[https://drive.google.com/open?id=1Q6bKGarMDhvWz3HdGvhL5qDhyHb546ve Case Bottom Template]
**[https://drive.google.com/open?id=1ugI74ygNJ3EN5jXks5jKvdpEAoxIzHo4 Case Palmrest Template]

= Other Resources =
* [https://forum.pine64.org/forumdisplay.php?fid=111 Pinebook Pro Forum]
* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [[RockPro64 Guides]]
* [https://riot.im/app/#/room/#pinebook:matrix.org Matrix Channel] (No login required to read)
* IRC Server: irc.pine64.org Channel: PineBook
* [https://discordapp.com/channels/463237927984693259/622348681538043924 Discord Channel]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]

[[Category:PineBook Pro]] [[Category:Rockchip RK3399]]

Pinebook Pro Software Releases

2020-10-18T22:59:43Z

Abcde: logo fix

= OS Image Releases =
For information on how to install these images onto your device, please see the [[NOOB]] Page, which includes information on writing images to the device eMMC or an SD card.

If Manjaro is installed on the eMMC you may experience issues booting different installations from SD card. [https://gitlab.manjaro.org/snippets/490 List of known affected distros and workaround].

== elementary OS ==
[[File:elementaryLogo.png|right|100px]]

=== elementary OS 6 [microSD/eMMC boot] ===

* Full version of elementary OS optimized for Pinebook Pro
* Experimental [https://builds.elementary.io/ “Early Access” build of elementary OS 6] (which has not been released as stable)
** Size: ~1.2 GB (varies since images are built daily)
* Polished first-run setup which helps you create a user before logging in
* Downloading, installation, etc. details at the [https://github.com/elementary/os/wiki/Pinebook-Pro elementary OS Wiki]

== Arch Linux ==
[[File:Archlinux-logo.png|right|100px]]

=== Arch Linux ARM install image [microSD/USB Boot] ===
* archiso image customized for Arch Linux ARM on the Pinebook Pro
* DD image (for 1GB or larger microSD card/USB stick):
** [https://github.com/nadiaholmquist/archiso-pbp/releases Direct download for latest releases from GitHub]
** size: 579MB
* Automatic login as root
* Make sure to thoroughly read the [https://github.com/nadiaholmquist/archiso-pbp/blob/master/README.md readme] and [https://github.com/nadiaholmquist/archiso-pbp/blob/master/FAQ.md FAQ], otherwise follow the normal Arch installation guide.

== CentOS 8 ==
[[File:Centos.png|right|100px]]

=== CentOS 8 Server with GUI install image [microSD/USB Boot] ===
* DD image (for 12GB or larger microSD card/USB stick):
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/centos8-202008-ARMDevelopers.img.xz Direct Download]

== Debian Desktop ==
[[File:debian.png|right|100px]]

=== Debian Desktop Community Build Image [microSD to eMMC] by mrfixit2001 ===
* This was previously the default operating system for the Pinebook Pro
* Includes desktop, Firefox browser, and LibreOffice
* DD image (for 8GB microSD card / 16GB eMMC module and above):
** [https://github.com/mrfixit2001/debian_desktop/releases/download/191226/pinebookpro-debian-desktop-mrfixit191226.img.xz Direct download release build 191226 from mrfixit2001's github]
*** MD5 (img file): 59838c1518b8b6da86a00d38b31ae904
*** File Size: 1.19GB
* Login with
** username: rock
** password: rock

== Ubuntu 20.04 Focal Fossa MATE / GNOME ==
[[File:UbuntuLogo.png|right|100px]]

=== Ubuntu 20.04 Focal Fossa MATE and GNOME Community Builds [microSD/ eMMC Boot] by ayufan ===
* Desktop Images featurng a standard Ubuntu suite of software to get you started.
* DD image (for 8GB microSD card /16GB eMMC module and above):
** [https://github.com/ayufan-rock64/linux-build/releases Direct download for latests releases and pre-releases on ayufan's github]
** size: 1.06GB
* Login with
** username: rock64
** password: rock64 (must be changed on initial boot)

== Ubuntu 18.04 Bionic Beaver LXDE ==
[[File:lxde.png|right|100px]]

=== Ubuntu 18.04 Bionic Beaver LXDE Community Build Image by ayufan [microSD and eMMC Boot] ===
* Included LXDE Desktop, Firefox Browser, and LibreOffice Suite
* DD image (for 8GB microSD card /16GB eMMC module and above):
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.9.14/bionic-lxde-pinebookpro-0.9.14-1159-armhf.img.xz Direct download release build 0.9.14 from ayufan's github]
** MD5 (XZ file): B74E8366615DAE89AEB5CC878F2B316B
** size: 763MB
* Login with
** username: rock64
** password: rock64

== Bionic Mate ==
[[File:mate.png|right|100px]]

=== Bionic Mate Community Build Image [microSD Boot] by ayufan ===
* Included Mate Desktop, Firefox Browser, and LibreOffice Suite
* DD image (for 8GB microSD card / 16GB eMMC module and above):
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.9.14/bionic-mate-pinebookpro-0.9.14-1159-armhf.img.xz Direct download release build 0.9.14 from ayufan's github]
** MD5 (XZ file): 5F60494B9248570FAF5853860A26B489
** size: 1.06GB
* Login with
** username: rock64
** password: rock64

== Manjaro ARM ==
[[File:Manjaro.png|right|100px]]

* The Manjaro project offers a mainline kernel with patches and modules to support PBPro hardware in two flavors. Both provide DD images and installer images (DD to SD card which will then install to eMMC when booted).
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum]

=== Manjaro ARM with KDE (Plasma) desktop [microSD / eMMC Boot] ===

* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-kde-plasma/ Direct download from Manjaro] (microSD image only)
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/kde-plasma/ Direct download from osdn.net] (both microSD and emmc-installer images)

=== Manjaro ARM with GTK (XFCE) desktop [microSD / eMMC Boot] ===

* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-xfce/ Direct download from Manjaro]
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/xfce/ Direct download from osdn.net]

=== Manjaro ARM with i3 tiling window manager [microSD / eMMC Boot] ===

* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-i3/ Direct download from Manjaro]
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/i3/ Direct download from osdn.net]

=== Manjaro ARM with Sway tiling window manager [microSD / eMMC Boot] ===

* [https://osdn.net/projects/manjaro-arm/storage/pbpro/sway/ Direct download from osdn.net]

=== Manjaro ARM installer ===

The [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer manjaro-arm-installer] script is intended to install Manjaro ARM directly to SD/eMMC cards without the need for images (including LXQT, Mate & CuboCore editions, as well as full disk encryption). Running on a Linux x86 computer, it can install Manjaro ARM directly to an empty eMMC using an eMMC to USB adapter. The script can also be run from SD to install an image to the eMMC.

==Kali Linux==
[[File:Kali.jpeg|right|100px]]

=== Kali Linux prebuilt OS images for Pinebook Pro [SD/eMMC boot]===
* Official pre-built OS images of Kali Linux for the Pinebook Pro featuring all tools you'd expect from the distribution.
* DD image (for 8GB microSD card /16GB eMMC module and above):
** [https://www.offensive-security.com/kali-linux-arm-images/ Direct download latest images from Offensive Security's website]
** size: 2.0GB
* Login with
** username:
** password:

== postmarketOS ==
[[File:PostmarketOS logo.png|right|100px]]

===Official postmarketOS build [microSD/ eMMC Boot] ===
* Official postmarketOS build with the GNOME desktop for the Pinebook Pro.
* DD image (for 8GB microSD card /16GB eMMC module and above):
** [http://images.postmarketos.org/pinebookpro/ Direct download latest images from postmarketOS]
** size: 400MB
* Login with
** username: demo
** password: demo OR 147147

== Q4OS ==
[[File:q4os.png|right|100px]]

=== Q4OS Test Build Image [microSD / eMMC Boot] ===
* Q4OS is advertised as a 'fast and powerful operating system based on the latest technologies while offering highly productive desktop environment'
* To learn more please visit the [https://forum.pine64.org/showthread.php?tid=8385 PINE64 forum] or official [https://q4os.org/index.html Q4OS website]
* DD image (for 8GB microSD card / eMMC module and above)
** [https://sourceforge.net/projects/q4os/files/testing/ Direct download latest release build from SourceForge]
* User account and password are created on first run

== OpenSUSE ==
[[File:Opensuse1.png|right|100px]]

=== OpenSUSE XFCE OS Image [microSD / eMMC Boot] ===
* This image contains an install of openSUSE tumbleweed with XFCE desktop environment.
* To learn more about OpenSUSE please visit the [https://www.opensuse.org/ official website].
* Pinebook Pro build instructions can be found [https://github.com/smithmcgriff/opensuse-on-pinebookpro-gnome here]
* DD image (for 16GB microSD card / eMMC module and above)
** [https://sourceforge.net/projects/opensuse-on-pinebookpro/files/Rel_1/ Direct download latest release build from SourceForge]
* login with:
** username: root
** password: linux

=== OpenSUSE GNOME 3 OS Image [microSD / eMMC Boot] ===
* This image contains an install of openSUSE tumbleweed with GNOME 3 desktop environment.
* To learn more about OpenSUSE please visit the [https://www.opensuse.org/ official website].
* Pinebook Pro build instructions can be found [https://github.com/smithmcgriff/opensuse-on-pinebookpro-gnome here]
* DD image (for 16GB microSD card / eMMC module and above)
** [https://sourceforge.net/projects/opensuse-on-pinebookpro/files/Rel_1/ Direct download latest release build from SourceForge]
* login with:
** username: tux
** password: susepassword

== Fedora ==
[[File:fedora1.png|right|100px]]

=== Fedora GNOME3 OS Image [microSD / eMMC Boot] ===
* This image contains an install of Fedora with GNOME3 desktop environment.
* To learn more about Fedora please visit the [https://getfedora.org/ official website].
* Pinebook Pro build instructions can be found [https://github.com/smithmcgriff/Fedora-on-pinebookpro here]
* DD image (for 8GB microSD card / eMMC module and above)
** [https://sourceforge.net/projects/opensuse-on-pinebookpro/files/Rel_2/ Direct download latest release build from SourceForge]
* login with:
** username: tux
** password: susepassword

=== Fedora 32 Workstation OS Image [microSD / eMMC Boot] ===
* This image contains an install of Fedora with GNOME3 desktop environment.
* To learn more about Fedora please visit the [https://getfedora.org/ official website].
* DD image (for 12GB microSD card / eMMC module and above)
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Workstation-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]
* login with:
** username: root
** password: fedora

=== Fedora 32 Cinnamon Desktop OS Image [microSD / eMMC Boot] ===
* This image contains an install of Fedora with GNOME3 desktop environment.
* To learn more about Fedora please visit the [https://getfedora.org/ official website].
* DD image (for 12GB microSD card / eMMC module and above)
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Cinnamon-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]
* login with:
** username: root
** password: fedora

=== Fedora 32 KDE Desktop OS Image [microSD / eMMC Boot] ===
* This image contains an install of Fedora with GNOME3 desktop environment.
* To learn more about Fedora please visit the [https://getfedora.org/ official website].
* DD image (for 12GB microSD card / eMMC module and above)
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-KDE-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]
* login with:
** username: root
** password: fedora

=== Fedora 32 Xfce Desktop OS Image [microSD / eMMC Boot] ===
* This image contains an install of Fedora with GNOME3 desktop environment.
* To learn more about Fedora please visit the [https://getfedora.org/ official website].
* DD image (for 12GB microSD card / eMMC module and above)
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Xfce-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]
* login with:
** username: root
** password: fedora

== Armbian ==
[[File:armbian.png|right|100px]]

=== Armbian [microSD / eMMC Boot] ===
* Armbian provides well-maintained Debian and Ubuntu OS images tailored to ARM devices
* To learn more please visit the [https://www.armbian.com/ Armbian's website]
* DD image (for 8GB microSD card / eMMC module and above)
** [https://www.armbian.com/pinebook-pro/ Direct download latest release from Armbian]
* login with:
** username: root
** password: 1234

==NetBSD==
[[File:netbsd.png|right|100px]]

=== NetBSD [microSD /eMMC Boot] ===
* To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page]
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]
** [http://www.armbsd.org/arm/ Direct download from NetBSD]
* Console and SSH default login:
** username: root
** password: [none]
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]

==OpenBSD==
[[File:Puffy_mascot_openbsd.png|right|100px]]

=== OpenBSD ===
* To learn more about OpenBSD, please visit [https://www.openbsd.org/ OpenBSD main page]
* ARM64 images, (including support for Pinebook Pro), can be found here [https://www.openbsd.org/arm64.html OpenBSD arm64]

== Chromium ==
[[File:chromium.jpg|right|100px]]

=== Chromium Community Build Image by ayufan [microSD and eMMC Boot] ===
* DD image (for 8GB microSD card/16GB eMMC module and above)
** [https://github.com/ayufan-rock64/chromiumos-build/releases/download/R77-12371.7.104.g78f88d6/chromiumos-rockpro64-R77-12371.7.104.g78f88d6.img.xz Direct download R77 build from ayufan's github]
** MD5 (XZ file): 7B747B6D2B041C5C0C6434DDB524DB66
** size: 387MB

==Recalbox==
[[File:RB.png|right|100px]]

=== Recalbox for Pinebook Pro [SD/eMMC boot]===
* Recalbox is a retrogaming Linux distribution allowing for emulation of all classic videogame systems.
* DD image (for 8GB microSD card /16GB eMMC module and above):
** [https://github.com/mrfixit2001/recalbox-rockchip/releases Direct download latest images from MrFixit's gitbub]
** size: 450MB
* SSH Login
** username: root
** password: recalboxroot

= Android Image Releases =
== Android 7.1 microSD ==
[[File:android_7.png|right|100px]]

=== Stock Android for DD method [micro SD Boot] [20190918] ===
* Production floor testing image
* Use 'dd' to write the image to the microSD card and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* DD image for 8GB microSD card
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_dd_20190918_stock_android_7.1_sdboot-8GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 207BCBFFF59C1AB29F8ADC63D426EACB
*** File Size: 562MB
* DD image for 16GB microSD card
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_dd_20190918_stock_android_7.1_sdboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): B1FC25A2F896F5C6B4B85EA6D1E75CDA
*** File Size: 571MB
* DD image for 32GB microSD card
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_dd_20190918_stock_android_7.1_sdboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): A07E2C2A2798A77375268E423A30048A
*** File Size: 589MB
* DD image for 64GB microSD card
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_dd_20190918_stock_android_7.1_sdboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284
*** File Size: 627MB

=== Stock for RK Flash tool [SD Boot] [20190427] ===
* Please unzip first and then using [http://files.pine64.org/os/ROCK64/android/SDDiskTool_v1.57.zip Rockchip SD Firmware Tool ver 1.57] to flash in, please remember to select "SD boot" option.
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_20190918_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]
** MD5 (GZip file): DBA2109C393F514132EC8D5FB6E8EBE2
** File Size: 555MB

== Android 7.1 eMMC ==
=== Stock Android for DD method [eMMC Boot] [20190807] ===
* Production floor testing image
* Please allows some time (around 5 minutes) for the initialization process on 1st boot
* DD image for 64GB eMMC Module
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_dd_20190807_stock_android_7.1_emmcboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 314583B550AFF0F424D9997D237D7046
*** File Size: 634MB
* DD image for 128GB eMMC Module
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_dd_20190807_stock_android_7.1_emmcboot-128GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 16942B8F9EEE79B81FADDB09AF7E2E80
*** File Size: 700MB

=== Stock for RK Flash tool [eMMC Boot] [20190807] ===
* Please unzip first and then using [http://files.pine64.org/os/ROCK64/android/AndroidTool_Release_v2.63.zip Rockchip Android tool ver 2.63] to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* [http://wiki.pine64.org/index.php/NOOB#Flashing_to_eMMC_using_Rockchip_Tools_.28Rock64_Only.29 Guide to flashing eMMC using Rockchip Tools]
* Please allow 3-5 minutes boot up time on first time for initialization
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_20190807_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]
** MD5 (GZip file): DC4C330787E57FC05F9D7D740F741620
** File Size: 555MB

= Linux Installer Releases =
== Debian Installer ==
[[File:debian.png|right|100px]]

=== Daniel Thompson's Debian Installer for the Pinebook Pro ===
* This is an image creator and Debian installer that runs from an existing Linux OS and installs Debian Bullseye
** Installer can configure an encrypted rootfs and provides a choice of desktops, including the default Debian desktop based on Gnome 3
** Strict adoption of upstream Debian packages (with exception of kernel and bootloaders) in order to provide a clean upgrade path as Bullseye matures
* Download at: https://github.com/daniel-thompson/pinebook-pro-debian-installer/
* Pull requests welcome but for discussion and support please use [https://forum.pine64.org/showthread.php?tid=8487 the forum topic].

For more information, see the [[Pinebook_Pro_Debian_Installer]] wiki page

=== Official Debian Installer Images ===
* Uses only the upstream kernel and firmware without special patches
* No graphical display yet, works only through serial console
* Requires adding the non-free component to your /etc/apt/sources.list file and installing the "firmware-linux" package for Wi-Fi and Bluetooth support
* Installer is loaded into RAM, can install onto the same media from which it’s booted
* Supports automatic partitioning and full disk encryption through LVM
* Installer currently doesn't install the bootloader, leaving the installed system in an unbootable state until it's manually added

[https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/ The relevant files are built daily here] and may sometimes be unavailable if the build system is having issues. The "README.concatenateable_images" file provides instructions on how to combine the partition.img.gz file with the firmware.pinebook-pro.rk3399.img.gz file in order to create a DD-able image.

The official images are '''not''' recommended yet until the display begins working and the installer properly installs the bootloader. Most users will want to see [[Pinebook Pro Debian Installer|Daniel Thompson's Debian Installer]] instead.

== Gentoo Script ==
[[File:GentooLogo.png|right|100px]]

=== Gentoo Script for Pinebook Pro ===
* This is a script that prepares a Gentoo arm64 stage 3 tarball for the Pinebook Pro
** The script takes care of device specifics like an optimized make.conf, an overlay that provides kernel and firmware amongst others, and other miscellaneous fixes
* The usual tarball setup as per [https://wiki.gentoo.org/wiki/Handbook:AMD64 Gentoo Handbook] is left to the user.
* Forum thread with instructions at https://forum.pine64.org/showthread.php?tid=8765

==Kali Script==
[[File:Kali.jpeg|right|100px]]

=== Kali Linux for Pinebook Pro ===
* This is a script to create official Kali Linux OS images for the Pinebook Pro
** The script carries out the build process in entirety and is Pinebook Pro specific
* Please pull the lastest [https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/pinebook-pro.sh Kali Linux install script] from the project's GitLab.
* For more information regarding building the OS image please read the README instruction at https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/README.md

[[Category:PineBook Pro]]

PineTab

2020-10-17T22:04:32Z

Abcde: Added logos

{{warning|1=IMPORTANT INFORMATION for '''Early Adopters''' - please [[PineTab/Early-Adopter|'''CLICK HERE''']] - some '''known issues''' are listed there}}

The PineTab is a 10" tablet created by Pine64.

== Specifications ==
* '''Dimensions:''' 11mm x 175mm x 260mm (Thickness, Width, Height)
* '''Weight:''' 575g (Tablet alone)
* '''Build:''' Plastic
* '''Storage:'''
** 64GB of internal eMMC storage
** MicroSD slot, bootable
** M.2 SSD slot, supports SATA and USB devices only, not NVME (optional)
* '''Cameras:''' 2Mpx Front, 5Mpx Rear
* '''SOC:''' Allwinner A64 Quad Core
* '''CPU:''' 4x ARM A53 1.152GHz
* '''GPU:''' Mali 400 MP2
* '''RAM:''' 2GB LPDDR3
* '''I/O:''' HD Video Out (Mini HDMI), Micro USB 2.0 OTG, USB 2.0 A host, 3.5mm Headphone/Mic combo,
* '''Network'''
** WiFi (802.11b/g/n, 2.4GHz only)
** Bluetooth 2.1
** M.2 LTE / Cell MODEM card, (optional, and takes place of optional M.2 SSD)
* '''Screen:''' 10.1" IPS 800x1280 Capacitive LCD
* '''Attachments/Accessories:''' Magnetically attached keyboard (optional)
* '''Battery:''' 6000MAh (6Ah)
* '''Misc. features:'''
** Volume rocker and home button
** Speakers and Microphone
** 2.5mm OD 0.7mm ID DC Jack Power (5V 2A) Port

== Keyboard ==
'''Overview:''' The PineTab detachable keyboard features a full function row, FN key functionality, meta key (where the Windows key would be) and all of the keys you need for daily use.

'''FN keys:''': Pause/play (F2), Stop (F3), Previous(F4), Next(F5), Music (F6), Mail (F7), Home (F8), Mute (F9), Vol- (F10), Vol+ (F11), Disable touchpad (F12), NumLock (Insert), Scroll Lock (Delete), PgUp (Up Arrow), PgDn (Down Arrow), Home (Left Arrow), End (Right Arrow), Digital Numpad (7,8,9,0,U,I,O,P,J,K,L,;,M,.,/)

==Versions==
For now there is only one version, also mentioned in the manual leaflet in the box.
* [[PineTab/Early-Adopter]]

[[File:PineTabBoard.jpeg|400px|thumb|right|The insides of the PineTab]]

== PineTab board information, schematics and certifications ==
* PineTab mainboard schematic:
** [http://files.pine64.org/doc/PineTab/PineTab%20Schematic%20v1.2-20191125.pdf PineTab mainboard Released Schematic ver 1.2]
** [http://files.pine64.org/doc/PineTab/PineTab%20Board%20View%20v1.2-20191201-top.pdf PineTab mainboard component placement ver 1.2 - Top View]
** [http://files.pine64.org/doc/PineTab/PineTab%20Board%20View%20v1.2-20191201-bottom.pdf PineTab mainboard component placement ver 1.2 - Bottom View]
* PineTab certifications:
** [http://files.pine64.org/doc/cert/PineTab%20FCC-SDOC%20Certificate-S20060600404001.pdf PineTab FCC Certificate]
** [http://files.pine64.org/doc/cert/PineTab%20CE-RED%20Certificate-S20060600403.pdf PineTab CE RED Certificate]

== Datasheets for components and peripherals ==
* Allwinner A64 SoC information:
** [http://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC brief introduction]
** [http://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
** [http://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]

* X-Powers AXP803 PMU (Power Management Unit) information:
** [http://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC datasheet]

* LPDDR3 (178 Balls) SDRAM:
** [http://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf Artmem LPDDR3 datasheet]

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

* CMOS camera module information:
** [http://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module datasheet]
** [http://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module datasheet]

* LCD touch screen panel information:
** [http://files.pine64.org/doc/datasheet/pinetab/GT9271.pdf GOODiX GT9271 Capacitive Touch Controller datasheet]
** [http://files.pine64.org/doc/datasheet/pinetab/GT9271_Config_20200818_142030_V66.cfg PineTab GT9271 Capacitive Touch Controller configuration file]

* Lithium battery information:

* WiFi/BT module information:
** [http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723BS/RTL8723CS specification]

== Operating Systems ==
The PineTab will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distro (because the PineTab uses the mainline kernel), only few of them will actually be usable on Early Adopters PineTab, due to specifics of working with LCD panel. Among those listed all except for postmarketOS have working builds.

=== UBPorts ===
[[File:Ubports-logo.png|100px]]
The UBPorts Ubuntu Touch is what preinstalled on PineTab Early Adopters batch.

It can update itself, and also jenkins daily build can be downloaded [https://ci.ubports.com/job/rootfs/job/rootfs-pinetab/ here]

In the event that WiFi fails to connect, the USB port can be used with an appropriate dongle to connect for internet using ethernet cable.

=== postmarketOS ===
[[File:PostmarketOS-logo.png|100px]]
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices.

The latest builds can be downloaded from the [https://images.postmarketos.org/pinetab/ images page] to be flashed to the PineTab.

More information is available at [https://postmarketos.org postmarketos.org] and on their [https://wiki.postmarketos.org/wiki/PINE64_PineTab_(pine64-pinetab) dedicated PineTab wiki page].

=== Arch Linux ARM ===
[[File:Archlinux-logo.png|100px]]
Arch Linux ARM with Phosh as the UI selection, maintained by the DanctNIX community.

The latest image can be downloaded [https://github.com/dreemurrs-embedded/Pine64-Arch/releases here]

=== Manjaro ARM ===
[[File:Manjaro-logo.svg|100px]]
Th first Manjaro ARM image confirmed to be working on Early Adopters PineTab can be downloaded [https://next.manjaro.org/index.php/s/aeXDtbWnnBNEM2Q here], ref [https://forum.manjaro.org/t/manjaro-arm-alpha2-with-phosh-pinetab/150/12 forum thread].

Older Manjaro images with several different environments, including Phosh and Plasma, but '''not working on Early Adopters PineTab''' can be downloaded [https://osdn.net/projects/manjaro-arm/storage/pinetab/ here]

=== Mobian ===
[[File:Debian-logo.png|100px]]
Mobian is a project providing Debian images for mobile devices.

PineTab images can be downloaded [https://images.mobian-project.org/pinetab/ here]. Password is '''1234'''

== Installation instructions ==
For instructions on how to install the operating systems to the eMMC or microSD card see [[PinePhone Installation Instructions]]. The information is almost the same for the PineTab, as it is a very similar device. Do not try to use the PinePhone images though, use the PineTab images linked above.

=== Testing ===
To test an OS, just flash its image onto an microSD card, plug it into PineTab, and reboot.
Note that USB stick won't work.
Also note that you need to "flash", not just copy the file onto the card.
Also remember that you need to unpack image file if it's packed!

You can do it using Ubuntu Touch installed on the PineTab! For now, only Mobian is supported by the guide below.

* First, make sure you have enough free disk space and empty Downloads directory on the PineTab (while not strictly necessary, empty Downloads dir will simplify your typing. You can just move all files from there to another directory).
* go to the Mobian link above and download compressed image (the one ending with .img.gz) - usual recommendation is to download latest, i.e. lowest one.
* Open terminal and type this in it:
cd Downloads
ls
* It should show you the name of the file you've just downloaded
* This file is compressed, so first you need to uncompress it. Type this into terminal:
gunzip *.gz && echo done
* This command will take some time (you won't see any progress until it's done). It either will succeed (and print "done") and fail (and print why).
* Now, let's have a look at disks. Type this into terminal:
lsblk
* It should show you a tree of disks and their partitions. If you don't have microCD card inserted yet, all of them begin with mmcblk2. Also, some of them have something in the "MOUNTPOINT" column
* Insert microSD card into PineTab. Note that all information on it will be deleted, so don't insert one with valuable information on it!
* type `lsblk` into terminal again.
* Note that now tree of disks has one or more new entries - starting with mmcblk0 - that's partitions of your microSD card.
* Confirm that size of mmcblk0 is close to size of the microSD card, and all lines starting with mmcblk0 have empty "MOUNTPOINT" column.
* now type this:
sudo dd if=`ls` of=/dev/mmcblk0 bs=1M status=progress
* It will take some time, depending on speed of your microSD card and size of image file
* Now, reboot your PineTab - type this into terminal:
sudo reboot
* PineTab should boot from the microSD you've just flashed

== Tips and tricks ==

=== Reset ===

If your PineTab is in unknown state or doesn't want to start.
Press power button for 7-8s. It makes a sound and you know it's totally off. 3 seconds after, power button again for 2-3s and it will start to boot. - thanks
@Aperricio on IRC for this hint

=== Display rotated 90° on Arch ARM ===
With the following command you can turn the display to landscape:

* echo 1 | sudo tee /sys/class/graphics/fbcon/rotate

This command does not persist a reboot.

[[Category:PineTab]] [[Category:Allwinner A64]]

SOPINE Armbian LCD and Camera

2020-10-17T21:34:43Z

Abcde: edit category

== LCD ==
1. DD the Armbian SOPINE image to the microSD Card and run on the board

2. Login through the terminal

3. # vi /boot/armbianEnv.txt (Change off to on)

pine64_lcd=on

4. # vi /etc/modules (Add following line)

gt9xxf_ts

5. reboot

Then the display will be on LCD and not HDMI

== Camera ==
1. DD the Armbian SOPINE image to the microSD Card and run on the board

2. Login through the terminal

3. Install Ubuntu Xenial Mate with ayufan's script

# cd ~
# wget https://github.com/longsleep/build-pine64-image/raw/master/simpleimage/platform-scripts/install_desktop.sh
# chmod +x install_desktop.sh
# ./install_desktop.sh mate

4. # vi /boot/armbianEnv.txt (Set to "s5k4ec" or "ov5640" depending on your camera module)

camera_type=s5k4ec

5. # vi /etc/modules (Add the following depending on your camera_type "s5k4ec" or "ov5640" above. Note that "vfe_v4l2" has a small letter 'L'2 not 12)

s5k4ec
vfe_v4l2

6. # reboot

7. Following https://github.com/avafinger/pine64_camera (Change "s5k4ec" to "ov5640" depending on your camera module)

# apt-get update
# apt-get upgrade
# apt-get remove --purge guvcview
# apt-get remove --purge libguvcview-1.1-1
# modprobe -r -f vfe_v4l2
# modprobe -r -f s5k4ec
# modprobe s5k4ec
# modprobe vfe_v4l2
# ls /dev/video0
# dmesg | grep OK
# sudo apt-get install libmp3lame-dev libx264-dev libpulse-dev libv4l-dev libsdl1.2-dev libgtk-3-dev portaudio19-dev libpng12-dev libavcodec-dev libavutil-dev libudev-dev libusb-1.0-0-dev libpulse-dev libgsl0-dev libv4l-dev
# cd ~
# wget https://raw.githubusercontent.com/avafinger/pine64_camera/master/libguvcview-1.2-1_2.0.3%2Bdebian-1_arm64.deb
# wget https://raw.githubusercontent.com/avafinger/pine64_camera/master/guvcview_2.0.3%2Bdebian-1_arm64.deb
# dpkg -i libguvcview-1.2-1_2.0.3+debian-1_arm64.deb
# dpkg -i guvcview_2.0.3+debian-1_arm64.deb

8. For testing, use Xenial Mate -> Applications -> Sound & Video -> guvcview
OR command line

# guvcview -d /dev/video0 -x 640x480 -r sdl -f yu12
# guvcview -d /dev/video0 -x 640x480 -r sdl -f nv12

[[Category:SOPine]]

Pine64

2020-10-17T21:33:13Z

Abcde: Abcde moved page Pine64 to Pine A64: Confusion with company name/device name

#REDIRECT [[Pine A64]]

1080P Pinebook Software Releases

2020-10-17T21:31:25Z

Abcde: typo

= Linux Image Releases =
'''Special thanks to Sunxi community, ayufan, and longsleep for their contributions'''

Below you will find useful links to various resources and forum threads:
* [https://linux-sunxi.org/Pinebook Sunxi Pinebook Page]

==Manjaro ARM==
http://files.pine64.org/sw/pine64_installer/json/manjaro.png

* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum]
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]
* Console and SSH default login:
** username: manjaro
** password: manjaro

=== Manjaro KDE Plasma ARM Community Build Image [microSD to eMMC Boot and microSD / eMMC Boot] ===
* This is microSD boot and install to eMMC version. Please follow bootup screen to complete eMMC installation process
* Please using this method to refrssh the Pinebook eMMC flash to Manjaro KDE Plasma build
* [https://osdn.net/projects/manjaro-arm/storage/pinebook/kde-plasma/ Direct download from osdn.net]

=== Manjaro I3 ARM Community Build Image [microSD / eMMC Boot] ===
* [https://osdn.net/projects/manjaro-arm/storage/pinebook/i3/ Direct download from osdn.net]

=== Manjaro KDE ARM Community Build Image [microSD / eMMC Boot] ===
* [https://osdn.net/projects/manjaro-arm/storage/pinebook/kde/ Direct download from osdn.net]

=== Manjaro LXQT ARM Community Build Image [microSD / eMMC Boot] ===
* [https://osdn.net/projects/manjaro-arm/storage/pinebook/lxqt/ Direct download from osdn.net]

=== Manjaro XFCE ARM Community Build Image [microSD / eMMC Boot] ===
* [https://osdn.net/projects/manjaro-arm/storage/pinebook/xfce/ Direct download from osdn.net]

== KDE Neon Image ==
http://files.pine64.org/sw/pine64_installer/json/kde.png

=== KDE Neon Community Build Image [microSD and eMMC Boot] ===
* DD image (for 8GB micoSD card and above)
** [https://files.kde.org/neon/images/pinebook-remix-nonfree/useredition/ Direct download latest release build from KDE Neon 1080P Pinebook]

=== Factory Restore KDE Neon Community Build Image [microSD to eMMC] [20181028] ===
* DD image (for 8GB micoSD card and above)
** [http://files.pine64.org/os/Pinebook/KDE/neon-pinebook-sd2emmc-1080p.img.gz Direct download from pine64.org]
*** MD5 (GZip file): D3C65FB812E125445C2EEA37FA99965F
*** File Size: 1.66GB
** Default Login (changed after 1st installtion setup) with
*** username: live
*** password: live

== Armbian ==
http://files.pine64.org/sw/pine64_installer/json/armbian.png

=== Armbian Xenial [microSD / eMMC Boot] [5.67] ===
* Armbian provides a build system and images for Debian/Xenial with BSP kernel and mainline kernel (beta)
* DD image (for 8GB micoSD card and above)
** [https://dl.armbian.com/pinebook-a64hd/archive/Armbian_5.67_Pinebook-a64hd_Ubuntu_xenial_default_3.10.107_desktop.7z Pinebook Armbian download mirrors]
* Login with
** username: root
** password: 1234
* To find out more about Armbian and available options please visit their [https://www.armbian.com/pinebook-a64/ site].

== Arch Linux mainline XFCE ==
http://files.pine64.org/sw/pine64_installer/json/archlinux.png

=== Arch Linux mainline with XFCE GUI by anarsoul ===
* Included XFCE Desktop, and Firefox browser
* DD image (for 8GB and above SD Card):
** [https://github.com/anarsoul/linux-build/releases/latest Direct download latest release build from anarsoul github and look for archlinux-xfce-pinebook-xxxxxxxx-x.img.xz]
* Login with
** User Name: alarm, Password: alarm
** User Name: root, Password: root
* please login root and execute "pacman -Syu" for latest update
* Standby feature not yet implememnted

'''* From SSH Login default disable root to access . So please first login alarm after command su password root to switch root'''

== KALI ==
http://files.pine64.org/sw/pine64_installer/json/KALI.png

=== KALI Build Image by Defensive Security [microSD / eMMC Boot] [2019.4] ===
* To learn more, please visit the official [https://www.offensive-security.com/kali-linux-arm-images/#2536677610546-d94f090d-c5ea KALI by Defensive Security website]
* DD image (for 8GB micoSD card and above)
** [https://images.offensive-security.com/arm-images/kali-linux-2019.4-pinebook.img.xz Direct download from Defensive Security]
*** MD5 (XZ file): 7E3643730D2D287A3726B641A6DA177C
*** File Size: 686MB

== /e/ ==
http://files.pine64.org/sw/pine64_installer/json/e.png

=== /e/OS Community Build Image p [microSD and eMMC Boot] [20190926] ===
* To learn more about /e/OS, please visit the [https://e.foundation/ official website]
* Please check out [https://medium.com/@edevelopers.blog/e-os-ports-for-the-pinebook-and-pinephone-596139c76479 this article] on the Pinebook /e/ build.
* For thread diiscussion please visit the [https://forum.pine64.org/showthread.php?tid=7954 PINE64 forum]
* DD image (for 8GB micoSD card and above)
** [http://files.pine64.org/os/Pinebook/e/e-n-pinebook_20190926.gz Direct download from pine64.org]
*** MD5 (GZip file): 4DC46A4E3ED2B47F4830E96DFCBBC6D8
*** File Size: 685MB

== AOSC ==
http://files.pine64.org/sw/pine64_installer/json/aosc.png

=== AOSC Community Build Image with Mate Desktop [microSD Boot] [20181016] ===
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]
* Known issue: no audio sound output.
* DD image (for 8GB micoSD card and above)
** [http://files.pine64.org/os/Pinebook/AOSC/sun50i-a64-pinebook_sunxi64-mate_2018-10-16.img.xz Direct download from pine64.org]
*** MD5 (GZip file): A52A7692C1690F342685451527343E6B
*** File Size: 2.62GB
* Login with
** username: aosc
** password: anthon

=== AOSC Community Build Image with Mate Desktop [eMMC Boot] [20181016] ===
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]
* Known issue: no audio sound output.
* DD image to eMMC module using USB adapter for eMMC module.
** [http://files.pine64.org/os/Pinebook/AOSC/sun50i-a64-pinebook_sunxi64-mate_2018-10-16_mmc2.img.xz Direct download from pine64.org]
*** MD5 (GZip file): 1EE68EFF94C6CDB8DFAD573195FC3F2B
*** File Size: 2.63GB
* Login with
** username: aosc
** password: anthon

== DietPi ==
http://files.pine64.org/sw/pine64_installer/json/dietpi.png

=== DietPi Community Build Image [microSD boot] ===
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6520 here]

* DD image to microSD card module and boot. Highly recommend using [https://etcher.io/ Etcher]
** [https://dietpi.com/downloads/images/DietPi_Pinebook-ARMv8-Stretch-Desktop.7z Direct download from DietPi website]
** MD5 (XZ file): fe37cf96b1112b0e37d0ca504346e461
** size: 233MB
* Login with
** username: root
** password: dietpi

==NetBSD==
http://files.pine64.org/sw/pine64_installer/json/netbsd.png

=== NetBSD Community Build Image [microSD Boot] ===
* To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page]
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]
** [http://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select 64bit - Pinebook]
** size: 345MB
* Console and SSH default login:
** username: root
** password: [none]
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]

==OpenBSD==
http://files.pine64.org/sw/pine64_installer/json/openbsd.jpg

=== OpenBSD 6.6-snapshot, Community Build Image (FVWM2 WM) ===
* To learn more about OpenBSD please visit [https://www.openbsd.org OpenBSD main page]
* DD image to microSD card or eMMC module (at least 8GB). Highly recommend using [https://etcher.io/ Etcher]
** https://www.dropbox.com/s/79hpdpehrbbk984/pinebook-2019-11-04.img.tgz.sha256?dl=0 (sha256)
** https://www.dropbox.com/s/yas1glfvvucb9a0/pinebook-2019-11-04.img.tgz?dl=0 (image)
** compressed size: 3.6GB
* Console and SSH default login:
** username: pine64
** username: pine64
** root password: pine64
* If you need more information please ping: https://forum.pine64.org/member.php?action=profile&uid=12423

== Q4OS ==
http://files.pine64.org/sw/pine64_installer/json/q4os.png

=== Q4OS Community Build Image [microSD Boot] ===
* Q4OS is advertised as a 'fast and powerful operating system based on the latest technologies while offering highly productive desktop environment'
* To learn more please visit the [https://forum.pine64.org/showthread.php?tid=4506 forum] or official [https://q4os.org/index.html Q4OS website]
* DD image (for 8GB micoSD card and above)
** [https://sourceforge.net/projects/q4os/files/stable/ Direct download latest release build from SourceForge and look for q4os-x.x-pinebook1080p.xx.zip]
* login with:
** username: adminq
** password: adminq

== Android 6.0 ==
http://files.pine64.org/sw/pine64_installer/json/android_6.png

=== Android 6.0.1 Stock Image [microSD to eMMC] [20181001] ===
* Rootable build
* LCD resolution is 1920 x1080
* Rooted DD image (advise 4GB microSD card and above):
** [http://files.pine64.org/os/Pinebook/android/android-ver6.0.1-rooted-20181001-1080P-pinebook-sd2emmc-lpddr3.img.gz Direct download from pine64.org]
*** MD5 (GZip file): E433A148CEBD743EADE6CAA765331A4B
*** File Size: 595MB

=== Android 6.0.1 Stock Image [microSD boot] [20181001] ===
* Rootable build
* LCD resolution is 1920 x1080
* Please use high performance microSD card for Android boot which request frequent random read access.
* Please ignore warning message regarding SD corrupted on home screen upper left corner
* DD images:
** For 8GB microSD Card
*** [http://files.pine64.org/os/Pinebook/android/android-rooted-ver6.0.1-20181001-1080P-pinebook-sdboot-lpddr3-8GB.img.gz Direct download from pine64.org]
**** MD5 (GZip file): CD27DF6083E6A4A5E7C8B986EB92FAA7
**** File Size: 553MB
** For 16GB microSD Card
*** [http://files.pine64.org/os/Pinebook/android/android-rooted-ver6.0.1-20181001-1080P-pinebook-sdboot-lpddr3-16GB.img.gz Direct download from pine64.org]
**** MD5 (GZip file): 1376AAE8382E96FD7B45B0998A5CD6E9
**** File Size: 703MB
** For 32GB microSD Card
*** [http://files.pine64.org/os/Pinebook/android/android-rooted-ver6.0.1-20181001-1080P-pinebook-sdboot-lpddr3-32GB.img.gz Direct download from pine64.org]
**** MD5 (GZip file): B54E7F323B316750654E385B078AEC58
**** File Size: 867MB
** For 64GB microSD Card
*** [http://files.pine64.org/os/Pinebook/android/android-rooted-ver6.0.1-20181001-1080P-pinebook-sdboot-lpddr3-64GB.img.gz Direct download from pine64.org]
**** MD5 (GZip file): C8DBC6293EB51E58F91E27364C8C587D
**** File Size: 734MB

= Linux BSP SDK =
== Linux BSP [4.0] ==
* [http://files.pine64.org/os/sdk/A64-ver4.0/A64-BSP-4.0.tar.gz Direct Download from pine64.org]
** MD5 (TAR-GZip file): 802D7C92D27177CBD17567359F9845A7
** File Size: 4.67GB

== Linux BSP [3.0] ==
* [http://files.pine64.org/os/sdk/A64-ver3.0/A64-BSP-3.0.tgz Direct Download from pine64.org]
** MD5 (TAR-GZip file): 898ACF446851DF3BE7B643F62CE3CE84
** File Size: 4.18GB

== Linux BSP [2.0], kernel [v3.10], with GPL compliance header ==
* [http://files.pine64.org/os/sdk/A64-ver2.0/A64-BSP-2.0-GPL.tar.gz Direct Download from pine64.org]
** MD5 (TAR-GZip file): 2EE11C9AED246C17995493F213A6A6DA
** File Size: 6.41GB

= Android SDK =
== Android Oreo [v8.1] ==
* [http://files.pine64.org/os/sdk/A64-ver4.0/A64-Android-8.1-SDK.tar.gz Direct Download from pine64.org]
** MD5 (TAR-Gzip file): 7E73672FE84F8CD099264D640E107EA3
** File Size: 28.87.95GB

== Android Nougat [v7.0] ==
* [http://files.pine64.org/os/sdk/A64-ver3.0/A64-Android-7.0-SDK.tgz Direct Download from pine64.org]
** MD5 (TAR-GZip file): 5D23D65BC1AA32B9048F62A4176BD9B3
** File Size: 22.60GB

== Android Marshmallow [v6.0] ==
* [http://files.pine64.org/os/sdk/A64-ver2.0/A64-Android-6.0-SDK.zip Direct Download from pine64.org]
** MD5 (Zip file): 12362D0B63EBF29FC363A50A942346D5
** File Size: 12.17GB

= Mali-400 64-bit Driver =
== Mali-400 64-bit Driver [20160622] ==
* [[Mali_Driver|Mali 64-bit Driver Download]]

= Other Tools =
* [https://drive.google.com/file/d/0B0cEs0lxTtL3VmstaEFfbmU1NFk/view?usp=sharing Allwinner PhoenixCard Bootable SD-Card Creator]
* [http://chinagadgetsreviews.com/download-dragonface-latest-version-v-2-2-5.html Allwinner DragonFace V2.2.5 software that will let you edit and modify A64 Android Build PhoenixCard image]
** [https://mega.nz/#!QxEjmaKB!S5nsVnzXVZg5aJ6qLtPOx1yJDPlbl0Vs4iV9VliRpE8 Direct download at Mega]

= Checking microSD Card Performance and whether it is Counterfeit =
* [https://sosfakeflash.wordpress.com/2008/09/02/h2testw-14-gold-standard-in-detecting-usb-counterfeit-drives/comment-page-3/#comment-9861 H2testw 1.4 – Gold Standard In Detecting USB Counterfeit Drives]
* [http://oss.digirati.com.br/f3/ F3 - an alternative to h2testw] This will help you to determine if the SD-Card is Counterfeit Drive or not

[[Category:PineBook]]

Overclocking

2020-10-17T21:17:12Z

Abcde: added categories

{{warning|1= This might damage your equipment or result in a unstable system, so do this at your own risk!}}
{{hint|This page is incomplete, you're welcome to improve it.}}
{{hint|All information regarding clock speeds, voltages and more are stored in the DTB (Device Tree Blob). You can learn more about it [https://elinux.org/Device_Tree_Reference here].}}

Overclocking is a way to get more performance out of the system by running it at higher clock speeds than the factory default, usually while putting out more heat and using more power. You can also downclock however.

= Preparation =
TODO, requires a compatible cross compiler (usually aarch64-linux-gnu), and clone the pine64 kernel repository.

Then after that just setup the variables for make.

In the future there will likely be a driver to adjust clockspeeds from userspace without the need to recompile.

= A64-based boards =
== GPU ==
Open <code>arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi</code> in a text editor.

Look for

<nowiki>
mali: gpu@1c40000 {
compatible = "allwinner,sun50i-a64-mali", "arm,mali-400";
reg = <0x01c40000 0x10000>;
interrupts = <GIC_SPI 97 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 98 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 99 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 100 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 102 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "gp",
"gpmmu",
"pp0",
"ppmmu0",
"pp1",
"ppmmu1",
"pmu";
clocks = <&ccu CLK_BUS_GPU>, <&ccu CLK_GPU>;
clock-names = "bus", "core";
resets = <&ccu RST_BUS_GPU>;

assigned-clocks = <&ccu CLK_GPU>;
assigned-clock-rates = <432000000>;
};
</nowiki>

The <code>assigned-clock-rates</code> line is set to <code>432000000</code>, this means that the GPU is clocked at 432MHz. So if you want 500MHz, set the value to <code>500000000</code>.

Save the dtsi file, and recompile the DTB.

The GPU appears to run stable overclocked to 560 Mhz, however more testing with a wider group of devices is needed.

{{note|Remember to run a benchmark tool (such as glmark2-es2) to help check stability.}}

== CPU ==

Stock speed: 1.152GHz CPU

== DRAM ==

{{warning|1=It is not recommended to exceed 667 MHz clockspeed on the DRAM. 624MHz is likely the upper limit.}}
{{hint|Make sure to set your DRAM to a multiple of 24.}}

When overclocking the GPU, it is a good idea to also overclock the DRAM, as the main bottleneck of the A64 SOC is the memory. The A64's maximum ram clockspeed falls just short of 667MHz. This may be unstable on your device however.

Around 600 MHz (PC-1200) should work fine, however some people have reported instability at lower clockspeeds. Arch Linux Arm uses a default clockspeed of 624MHz, with uboot builds available to easily switch out for a lower DRAM clockspeed.

It is possible that by reverse engineering the DRAM driver from allwinner that auto tuning can be accomplished to get the best performance.

Setting the DRAM clock is accomplished by modifying pinephone_defconfig in uboot (https://gitlab.com/pine64-org/u-boot/-/blob/crust/configs/pinephone_defconfig)

You can find simple instructions on doing so here: [https://wiki.pine64.org/index.php?title=Uboot Here]

= Rockchip RK3399 based boards =
The RK3399 clocks are found in <code>arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi</code>

More optimised voltages and clocks can be found in <code>arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi</code>
These include a slight overclock and undervolt, they are intended for the OP1 CPU found in many chromebooks but have worked fine in all recorded cases on regular RK3399s in other devices.

Specific to the Pinebook Pro DTS in tsys' kernels is an extra clock speed entry for the big cores in <code>arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts</code> 
It overrides the <code>opp08</code> entry for the big core cluster with one that runs 2GHz at 1.3V. 
It is up to you how to deal with this, either by just skipping opp08 in the main dtsi to keep using that entry or by removing that entry from the Pinebook Pro dts and adding your own to the regular dtsi.

==GPU==
Any clock speeds can be added for the GPU in <code>gpu_opp_table</code>

The highest safe voltage for the GPU is 1.2V as specified in the RK3399 schematic from Rockchip.

TuxThePenguin has found that the RK3399 in his Pinebook Pro can reach 950MHz on the GPU while being stable.

The stock speed for the GPU is 800Mhz

==CPU==
A set of available clock speeds that can be added to the CPU clusters can be found in <code>drivers/clk/rockchip/clk-rk3399.c</code> under <code>rk3399_cpuclkl_rates</code> for the little cores and <code>rk3399_cpuclkb_rates</code> for the big cores.

These clock speeds can be added to <code>cluster0_opp</code> for the small cores and <code>cluster1_opp</code> for the big cores respectively.

There is a hard limit of 1.8GHz on the little cores and 2.2GHz on the big cores.

The highest safe voltage for the little cores is 1.2V and for the big cores is 1.25V.

TuxThePenguin has found that the little cores on his RK3399 can run at 1.6GHz, and 2.08GHz on the big cores.

==DRAM==
TODO

= Rockchip RK3328 based boards =
TODO

[[Category:SOPine]] [[Category:Pine A64]] [[Category:Pine H64]] [[Category:A64-LTS]] [[Category:PineBook]] [[Category:PinePhone]] [[Category:PineTab]] [[Category:Rock64]] [[Category:PineBook Pro]] [[Category:ROCKPro64]] [[Category:Allwinner A64]] [[Category:Allwinner H6]] [[Category:Rockchip RK3399]] [[Category:Rockchip RK3328]]

POT

2020-10-17T21:10:09Z

Abcde: added category

''' Peripheral On Top (POT) '''
=='''POT Board Recommended PCB Dimension'''==
[http://files.pine64.org/doc/Pine%20A64%20Schematic/PineA64%20POT%20Board.rar POT board dimension for Pine A64 in DXF format]
[http://files.pine64.org/doc/Pine%20A64%20Schematic/PineA64%20POT%20Board.pdf POT board dimension for Pine A64 in PDF format]

=='''USB/UART Programming/Console Adapter (PMPROG01)'''==
[[File:USB_Prog.JPG]]
''Feature''
Base on Silicon Libs CP2102
Support Virtual COM Port Device Drivers
Support USBXpress™ Direct Driver Support
With XH 5 pin 2.54mm pitch connector for UART connection
Voltage Output on the connection is selectable to either 5V,3.3V or off
On board USB-B Connector Receptor
Connector J3 can direct insert into Pine A64 Exp-Bus to provide console access to Pine A64 board
I/O pin are protected with ESD protector IC.
On board 5x2pin connector can direct insert into Pine A64 Exp Bus for UART0 Console access
Can use for programming and debugging for Wifi Remote I/O board

''Related Specification and Document''
[[https://www.silabs.com/Support%20Documents/TechnicalDocs/CP2102-9.pdf CP2102 Datasheet]]
[[https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx Virtual COM Port Driver]]
[[http://www.silabs.com/products/mcu/Pages/USBXpress.aspx USBXpress Driver]]

[[File:PMPROG01_Rev2_USB_Serial_Programmer-4.jpg]]

[[File:PMPROG01_Rev2_USB_Serial_Programmer-1.jpg]]

[[File:PMPROG01_Rev2_USB_Serial_Programmer-3.jpg]]

[[File:PMWF01A Wifi Remote IO Rev3-1.jpg]]

=='''POT: Veroboard (PMVRB01)'''==
[[File:PMVRB01_board_layout.JPG]]

''Feature''
Sit on top of Pine A64 board
All the header receptor will have extended length pin to allow other POT board to insert on top of it
Allow easy access to all the I/O pin on the Pine A64 header
On board 4pcs of LED with current limiting resistor all direct connect to I/O pin for status indicator
On board 4pcs of Tact switch
On board XH5 2.54mm pitch connector for UART0 allow easy connection to USB/UART adapter for console access

[[File:PMVRB01_POT_Veroboard_Rev1-5.jpg]]

[[File:PMVRB01_POT_Veroboard_Rev1-3B.png]]

[[File:PMVRB01_POT_Veroboard_Rev1-2B.png]] POT Veroboard on Pine A64

[[File:PMVRB01_POT_Veroboard_Rev1-1B.png]] POT Veroboard 2 board stack on top of Pine A64

=='''POT: Multi I2C Bus (PMI2C01)'''==
[[File:PMI2C01_Board_Layout.JPG]]
''Feature''
Sit on top of Pine A64 board
All the header receptor will have extended length pin to allow other POT board to insert on top of it
Allow easy access to all the I/O pin on the Pine A64 header
2 channel of I2C bus is wire out for easy access
I2C bus repeater IC (PCA9517A) are included in each I2C bus to allow connection of more devices on each bus
Support 3.3V and 5V I2C bus for each channel separately
On Board separated 3.3V supply regulator for 3.3V I2C Bus
Each I2C bus pin are protected with ESD protector devices
Each channel consist of 4 pcs of XH 4 pin 2.54mm pitch connector and 2 pcs of XH 5 pin 2.54mm pitch connector
For the XH 4 pin connector, will consist of GND,SCL,SDA,5V pin
For the XH 5 pin connector, will consist of GND,nINT,SCL,SDA,5V pin
5V supplier is direct connect from Pine A64 adapter's supply thus prevent over loading Pine A64 board
The nINT pin will allow peripheral with interrupt pin link back to the Pine A64 I/O pin

''Related Specification and Document''
[http://www.nxp.com/documents/data_sheet/PCA9517A.pdf NXP PCA9517A Datasheet]
[http://www.nxp.com/documents/application_note/AN10658.pdf NXP AN10658 Sending I2C-bus signal via long communication cables]
[http://www.nxp.com/documents/application_note/AN11075.pdf NXP AN11075 Driving I2C-bus signals over twisted pair cables with PCA9605]
[http://wiki.pine64.org/images/d/d8/EnableI2cPullup.tar.gz Program to Enable I2c Port internal pull with full source code]
[http://pine.myggns.com/bozon/index.php?f=157836a20d7b7e Multi I2c Bus Schematic]

[[File:PMI2C01_I2C_Board_Rev1-1.jpg]]

[[File:PMI2C01_I2C_Board_Rev1-2.jpg]]

[[File:PMI2C01_I2C_Board_Rev1-3.jpg]]

[[File:PMVRB01_POT_Veroboard_Rev1-4.jpg]]

=='''POT: Shield Adapter (PMARD01)'''==
[[File:PMARD01_Shield_Adpater_POT.JPG]]
[[File:PMARD01_Arduino_Pin_Mapping.JPG]]
Adapter for Arduino Shield
Separate on board LM1117 3.3V LDO for the Shield
Base on Maxim MAX11609 on ADC input. Allow up to 5V analog signal
Extra 5V input DC jack socket (suitable for 4.0mm X 1.7mm DC Jack) for extra input power

''Related Specification and Document''
[http://https://www.maximintegrated.com/en/products/analog/data-converters/analog-to-digital-converters/MAX11609.html MAX11609 10bit I2C ADC]

=='''I2C Device: Humidity and Temperature Sensor (PMSDP01)'''==
[[File:PMSDO01_Dew_Point_Sensor.JPG]]
''Feature''
Base on Silicon Labs Si7021 I2C Humidity and Temperature Sensor
High Accuracy Temperature Sensor ±0.4 °C (max), –10 to 85 °C
0 to 100% RH operating range
Up to –40 to +125 °C operating range
On board 3.3V regulator
2pcs of XH 4pin 2.54 mm pitch connector to allow daisy chain of multiple I2C sensor

''Related Specification and Document''
[https://www.silabs.com/Support%20Documents/TechnicalDocs/Si7021-A20.pdf Si7021-A20 Datasheet]

[[File:PMSDO01_Dew_Point_Sensor_Rev1-1.jpg]]

=='''I2C Device: Ambient Light Sensor (PMSAL01)'''==
[[File:PMSAL01_Light_Sensor.JPG]]
''Feature''
Base on TAOS/AMS TSL2561T I2C Light Sensor
Approximates Human Eye Response
Programmable Interrupt Function allow user defined upper/lower limit trigger threshold
Automatically rejects 50/60Hz lighting ripple
Build with 2 channel of photodiode/ADC to allow more accurate calculation of light intensity (in Lux)
Can support up to 3pcs of sensor in the same I2C channel
On board 3.3V regulator
2pcs of XH 5pin 2.54 mm pitch connector to allow daisy chain of multiple I2C sensor

''Related Specification and Document''
[http://ams.com/eng/content/download/250094/975485/file/TSL2560_Datasheet_EN_v1.pdf TSL2561T Datasheet]

[[File:PMSAL01_Light_Sensor_Rev1-1.jpg]]

[[File:PMSAL01_Light_Sensor_Rev1-2.jpg]]

=='''WiFi Remote I2C (PMWF01A)'''==
[[File:PMWF01A.JPG]]
''Feature''
Base on ESP8266 Wifi Chipset
Connect to Wifi AP
On board chip antenna or U-FL connector for external antenna
On board relay contact (TE PCJ-105D3M with 3A 275Vac Contact) with screw type terminal contact to support AC Line On/Off
On board 1pc Tact-switch
XH 5 2.54mm pitch connector connecting I2C device
XH 6 2.54mm pitch connector for GPIO/SPI/PWM output
XH 2 2.54mm pitch connector for system power 5V input or output
DC Jack socket (suitable for 4.0mm X 1.7mm DC Jack) for system power input
UART Port connector ready for on chip programming using USB/UART Programming/Console Adapter (PMPROG01)
2pcs of XH 5pin 2.54 mm pitch connector to allow daisy chain of multiple I2C sensor
Further Detail info on the module can be found at [http://wiki.pine64.org/index.php/Wifi_Remote_I2c WiFi Remote I2c Quick Start Guide] wiki page

''Related Specification and Document''
[http://www.te.com/commerce/DocumentDelivery/DDEController?Action=srchrtrv&DocNm=PCJ_series_relay_data_sheet_E&DocType=DS&DocLang=EN TE PCJ-105D3M Relay Datasheet]
[https://drive.google.com/file/d/0B0cEs0lxTtL3SDdCcWd0LVI2bk0/view?usp=sharing ESP8266 Datasheet]
[http://bbs.espressif.com/ ESP8266 forum]

[[File:PMWF01A_Wifi_Remote_IO_Rev3-2.jpg]]

[[File:PMWF01A_Wifi_Remote_IO_Rev3-3.jpg]]

[[File:PMWF01A_Wifi_Remote_IO_Rev3-4.jpg]]

[[File:PMWF01A_Wifi_Remote_IO_Rev3-5.jpg]]

=='''Inter Connection Wire'''==
[[File:I2c_Cable_Connection.JPG]]

[[File:W5T4-01-15_UART_Programming_Console_Cable.JPG]]

[[File:W5T4-02-15_5Way_to_4Way_I2C_Cable.JPG]]

[[File:W4T4-03-15_4Way_I2C_Cable.JPG]]

[[File:W5T5-04-15_5Way_I2C_Cable.JPG]]

[[Category:Pine A64]]

PhoenixCard

2020-10-17T21:09:34Z

Abcde: added category

== How to Create MicroSD Card Android Image for Pine A64 ==

=== What do I need? ===

# The PhoenixCard software from Allwinner.
# You can download it [https://drive.google.com/file/d/0B0cEs0lxTtL3VmstaEFfbmU1NFk/view?usp=sharing here]
# A firmware image (.img files)
# A SD-Card (best Class 10 with 8GB or more SD-Card) - backup everything first, the Card will be formatted!
# An external SD-Card Reader
# A Windows PC

=== Step to create the SD-Card ===

[[File:PCard_Main.jpg|none|750px|PhoenixCard running on Windows]]

# Extract the PhonixCard-xx.rar file into an empty directory.
# Navigate into the directory where you installed PhoenixCard and start PhoenixCard.exe.
# Click '''DiskCheck''' and choose the drive with your SD-Card
# Click '''Img File''' and choose the file you want
# Write Mode must be set to '''Startup'''
# Press '''Burn'''
# Wait until the burning process is finished (you will see the progress in the progress bar and the notification window)

=== Booting Up the SD-Card ===

# Insert the SD-Card into the Pine64 and Power-up
# On the first time boot-up, it might take up to 5 minute for the system to get ready
# On the sub-sequence boot-up, it will only take about 40 to 60 second for the system to get ready

== Related Reference ==
* [http://www.cnx-software.com/2015/01/06/easily-create-an-androidlinux-bootable-sd-card-for-allwinner-a80-devices-with-phoenixcard-tool/ Easily Create an Android Bootable SD Card for Allwinner A80 Devices with PhoenixCard Tool]
* [http://www.ondaforum.com/topic/2022-boot-from-sd-card-or-flash-a-rom-with-phonixcard/ Boot from SD-Card or flash a ROM with PhonixCard]
* [http://www.androidsoldier.com/2013/11/upgrading-method-android-tablet.html How to upgrade tablet pc with Micro SD Card Tutorial]
* [https://www.youtube.com/watch?v=eKo82AUgbFM PhoenixCard Tutorial YouTube Video]

[[Category:Pine A64]]

ROCK64 MAC Address

2020-10-17T21:08:32Z

Abcde: added category

;Set MacAddress on ROCK64 with "Android eMMC" image
# [http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package] installation is required as prerequisite
# Download and unzip [http://files.pine64.org/doc/rock64/tools/WNpctool_V1.1.2_1226.zip WNpctool_V1.1.2_1226.zip]. Run WNpctool.exe "as Administrator" on Windows OS
# Press recovery button on ROCK64 and power ON the ROCK64. After 2 seconds release the recovery button
# Plug the USB Cable from Top USB2 slot of ROCK64 to PC USB slot (WNpctool will show "Found one loader" at the bottom)
# Fill in LANMAC: with small letter MacAddress (e.g. 01234567abcd) then press on Write button
# Unplug the USB Cable and reboot the ROCK64 and use DOS command "ping ..." and "arp -a" or [https://www.softperfect.com/products/networkscanner/ netscan] to check the MacAddress of the ROCK64

[[Category:Rock64]]

ROCKPro64 Software Releases

2020-10-17T21:07:47Z

Abcde: added category

= Linux Images =

== Armbian==
http://files.pine64.org/sw/pine64_installer/json/armbian.png

The ROCKPro64 is actively supported by Armbian. Armbian offers multiple images based on Ubuntu and Debian. To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]

== Ayufan releases - Ubuntu and Debian==

http://files.pine64.org/sw/pine64_installer/json/penguin.png

Forum thread concerning these releases can be found [https://forum.pine64.org/showthread.php?tid=6308 here]

A number of release versions are available based on either Ubuntu or Debian. In addition releases are available that are [https://github.com/ayufan-rock64/linux-build/releases/tag/0.9.14 stable] (based on a 4.4 kernel which has all the RockChip patches in it) or [https://github.com/ayufan-rock64/linux-build/releases pre-releases] (based on the latest linux kernel). An overview of the philosophy is [https://github.com/ayufan-rock64/linux-build on this GitHub page.]

Clicking through on any chosen release header (or expanding the "assets" section under the Changelog) will provide options to download many images suitable for the ROCKPro64 as well as others suitable for other devices such as the Rock64 and PinebookPro - please read the download filenames carefully to choose precisely the image you desire.

== Debian by Mrfixit2001 ==

http://files.pine64.org/sw/pine64_installer/json/debian.png

Mrfixit has engineered 2 releases based on Debian.

=== Feature complete desktop release ===

See forum thread [https://forum.pine64.org/showthread.php?tid=7269 here.]

* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]
** [https://github.com/mrfixit2001/debian_desktop/releases Direct download from GitHub]
* Login with
** username: rock
** password: rock

=== Minimal Debian ===

Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=7055 here]

* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]
** [https://github.com/mrfixit2001/debian_builds/releases Direct download from mrfixit2001's github]
* Login with
** username: rock
** password: rock

== Official Debian ==

http://files.pine64.org/sw/pine64_installer/json/debian.png

As of April 2020 Debian have a ROCKPro64 image available. See forum thread [https://forum.pine64.org/showthread.php?tid=9744 here.]

Instructions for creating a bootable image are in the README file on the Debian website, as at June 2020 these were in short
* Download firmware.rockpro64-rk3399.img.gz
* Download partition.img.gz
* zcat firmware.rockpro64-rk3399.img.gz partition.img.gz > complete_image.img
* dd if=complete_image.img of=your_chosen_boot_device bs=4M

What you now have is the official Debian installer that will boot and run on your ROCKPro64. You will need an Ethernet connection and to answer the various installer questions/options.

== DietPi ==
http://files.pine64.org/sw/pine64_installer/json/dietpi.png

=== DietPi Community Build Image [microSD / eMMC boot] ===
Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6520 here]

* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]
** [https://dietpi.com/downloads/images/DietPi_RockPro64-ARMv8-Stretch.7z Direct download from DietPi website]
** MD5 (XZ file): f2f42eb4521fa3f5eb7641263b1b76a4
** size: 59.4MB
* Login with
** username: root
** password: dietpi

== Arch ==

Folks are working on getting Arch going [https://forum.pine64.org/showthread.php?tid=6333 here in the forum.]

== OpenMediaVault ==

http://files.pine64.org/sw/pine64_installer/json/omv.png

OpenMediaVault is the next generation network attached storage (NAS) solution, [https://www.openmediavault.org/ click this link to OMV main page to learn more.]

Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]

=== Stretch 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]
** size: 392MB
* WebGUI Login:
** username: admin
** password: openmediavault
* SSH/ Console Login:
** username: root
** password: openmediavault
*** '''NB! You need to enable root login in OMV WebGUI'''
* [[OpenMediaVault|OpenMediaVault Basic Setup]]
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]

=== Stretch 64bit (aarch64) [microSD / eMMC Boot] [0.8.3] ===
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]
** size: 340MB
* WebGUI Login:
** username: admin
** password: openmediavault
* SSH/ Console Login:
** username: root
** password: openmediavault
*** '''NB! You need to enable root login in OMV WebGUI'''
* [[OpenMediaVault|OpenMediaVault Basic Setup]]
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]

== LibreELEC(KODI) ==

http://files.pine64.org/sw/pine64_installer/json/libreelec.png

=== Official LibreElec KODI Leia 9.2 Build Image [microSD / eMMC boot] ===

* Unzip and DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]
** [http://releases.libreelec.tv/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from LibreElec site]
** [http://files.pine64.org/os/ROCKPro64/libreelec/LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz Direct download from pine64.org]
*** MD5 (GZip file): DC9C57DA15474ACA0363113E1F0E5532
*** File Size: 135MB

== Slackware==

http://files.pine64.org/sw/pine64_installer/json/slackware.png

* Slackware is a very old, interesting, convenient and easy distribution.
* Visit the project's website here (http://fail.pp.ua)
* You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=6823)

=== Slackware Aarch64 Base Community Build Image [microSD Boot] [20191127] ===
* System without a graphical shell
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-base-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]
*** MD5 (XZ file): 27a92bf48fc51390c82d6bfd65239584
*** File Size: 271MB

=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20191127] ===
* System with a graphical shell
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
** [http://dl.fail.pp.ua/slackware/images/rockpro64/slarm64-current-aarch64-xfce-rootfs-14Oct19-4.4.203-rockpro64-build-20191127.img.xz Direct download from Slackware]
*** MD5 (XZ file): 489d1b6c8b289c30a174000555000668
*** File Size: 779MB

=== Slackware Aarch64 Miniroot Community Build Image [microSD Boot] [20190628] ===
* System without a graphical shell
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]
*** MD5 (XZ file): f0ec3c4780ee5281b2d41c1bf603f48c
*** File Size: 256MB

=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20190628] ===
* System with a graphical shell
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
** [http://files.pine64.org/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.org]
** [http://cdn.pine64.uk/os/ROCKPro64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.184-rockpro64-build-20190628.img.xz Direct download from pine64.uk]
*** MD5 (XZ file): 95fd494818ea4b07f532e25cd1015737
*** File Size: 729MB

* Login with
** Username : root
** Password : password

* To run the OS on eMMC
**Flash the image to micro SD, power up the board with micro SD and login
**Copy the image file to micro SD by using SFTP. The image file must be in .img. ''note : root user are not allow transfer file to micro SD.''
**After finish copy the file, power off the board and add eMMC module to the board
**Bootup the board, run below command for flashing to eMMC module
***>>dd if=[image file] of=/dev/mmcblk1 bs=10M
****''example : dd if=slack-current-aarch64-xfce_29Sep18-4.4.162-rockpro64-build-20181126.img of=/dev/mmcblk1 bs=10M''
***then edit 2 files in eMMC module:
***>> mount /dev/mmcblk1p1 /media
***>> echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt
***>> sed -i 's:mmcblk0p1:mmcblk1p1:' /media/etc/fstab
**After done, power off board and remove micro SD. Then bootup with only eMMC module.

== Nems Linux==
http://files.pine64.org/sw/pine64_installer/json/nems.jpg
* NEMS stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers.
* To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7306 PINE64 forum thread]
* Login with
** Username: nemsadmin
** Password: nemsadmin

=== NEMS Linux [microSD / eMMC Boot] [v1.5 - build 1] ===
* DD image (for 16GB micoSD card and above)
** [https://nemslinux.com/download/nagios-for-pine64.php Download torrent seed from NEMS Linux]
** [http://files.pine64.org/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.org]
** [http://cdn.pine64.uk/os/ROCKPro64/nems/NEMS_v1.5-RockPro64-Build1.zip Direct download from pine64.uk]
*** MD5 (XZ file): 2627bc0aa81e1c55de69a621d80987a5
*** File Size: 1.32GB

== NextCloudPi==

http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png

=== NextCloudPi Community Build Image [microSD / eMMC Boot] [03-10-19] ===
* NextCloudPi comes not only with NextCloud preinstalled, but also with management tools for backups, SSL certificates, SAMBA, enhanced security and more.
* Visit the project's [http://nextcloudpi.com website]
* You can follow the ongoing discussion about NextCloudPi on the [https://forum.pine64.org/showthread.php?tid=7265 forum]
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
** [http://files.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.org]
** [http://cdn.pine64.org/os/ROCKPro64/nextcloudpi/NextCloudPi_RockPro64_03-09-19.img.xz Direct download from pine64.uk]
*** MD5 (XZ file): 6ab1b08a8e4c2ed3abe40511749971a7
*** File Size: 312MB
* Login with
** username: root
** password: 1234

== CentOS ==

http://files.pine64.org/sw/pine64_installer/json/centos.jpg

=== CentOS-7 Community Build Image [microSD Boot] ===
* Centos-7.4.1708 with kernel from Armbian-5.67 (minimum build)
** DD image (for 8GB micoSD card and above)
** [https://github.com/Project31/centos-pine64/releases/download/v7.4.1708-v5.56/centos7-rock64pro.img.xz Project31 download mirrors]
* To find out more on installation process, please visit their [https://project31.github.io/pine64/ Project31 site]
* Login with
** username: root
** password: centos

== Manjaro ==

http://files.pine64.org/sw/pine64_installer/json/manjaro.png

=== Manjaro ARM [microSD / eMMC Boot] ===

Manjaro ARM now provide XFCE and KDE Plasma images for the ROCKPro64.

Download:

* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/xfce/ XFCE images] images
* [https://osdn.net/projects/manjaro-arm/storage/rockpro64/kde-plasma/ KDE Plasma] images

* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum]
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]

== Chromium ==

http://files.pine64.org/sw/pine64_installer/json/chromium.jpg
* To learn more please visit [https://forum.pine64.org/showthread.php?tid=7659 Forum]
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]

=== Chromium Community Build Image [microSD / eMMC Boot] [Beta (R76)] ===
* [https://github.com/ayufan-rock64/chromiumos-build/releases/download/R76-12239.4.100.gf2199d0/chromiumos-rockpro64-R76-12239.4.100.gf2199d0.img.xz Direct download from ayufan's github]
*** size: 357MB
*** MD5 (Zip file): 9ead15fd85e039de3445abdfd3c5013e

== Batocera Linux ==
http://files.pine64.org/sw/pine64_installer/json/batocera_linux.png
* It is an operating system in retrogaming
* Visit the project's website here (https://batocera.org/)
* You can follow the ongoing discussion about batocera.linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7084)

=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.25-20200310] ===
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
** [https://batocera.org/upgrades/rockpro64/stable/last/batocera-5.25-rockpro64-20200310.img.gz Direct download from batocera.org website]
*** File Size: 834MB
*** MD5 (gzip file): 9559c7570e48ca0a51bd9fc639b8a3c0

=== Batocera Linux Community Build Image [microSD / eMMC Boot] [5.24-20191108] ===
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
** [https://batocera.org/upgrades/rockpro64/stable/last/archives/20191108/batocera-5.24-rockpro64-20191108.img.gz Direct download from batocera.org website]
*** File Size: 857MB
*** MD5 (gzip file): 3228bf24e555ef75bba562dfe09f30a4

== Recalbox ==
http://files.pine64.org/sw/pine64_installer/json/recalbox.png
* Recalbox allows you to re-play a variety of videogame consoles and platforms in your living room, with ease!
* Visit the project's website here (https://www.recalbox.com/)
* You can follow the ongoing discussion about Recalbox on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7194)

=== Recalbox Community Build Image [microSD / eMMC Boot] ===
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
** [https://github.com/mrfixit2001/recalbox_rockpro64/releases Direct download latest release build from mrfixit2001 github]

== Odroid Retro Arena==
http://files.pine64.org/sw/pine64_installer/json/odroidretroarena.png

=== Odroid Retro Arena Community Build Image [microSD / eMMC Boot] [Beta 0.0.8] ===
* This is a BETA and therefore is not updatable nor supported however bugs or issues are appreciated to be identified and shared via the issues tab on our GitHub so that we can address them in the future. The Roshambo Case support is baked in with one major caveat due to kernel limitation: You can power the unit off by the POWER switch and the RESET button works 100% however to power the unit on you will need to manually plug/unplug the power cord. This limitation will not be present in future releases.
* Visit the project's [http://odroidarena.com/downloads/]
* You can follow the ongoing discussion about Odroid Retro Arena on the [https://forum.pine64.org/showthread.php?tid=7555 forum]
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
** [http://files.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.org]
** [http://cdn.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.uk]
*** MD5 (XZ file): fdfacfa8560356ba8d3aff0762c3e7cc
*** File Size: 4.06GB

== OpenWrt ==

[[File:Openwrt-logo.png|300px]]

=== OpenWrt Snapshot Build [microSD Boot] ===
* OpenWrt with 5.4 mainline linux kernel
** DD image (for 512MB micoSD card and above)
** [https://downloads.openwrt.org/snapshots/targets/rockchip/armv8/ OpenWrt snapshot page]
* To find out more on installation process, please visit their [https://openwrt.org/inbox/toh/pine64/pine64_rockpro64_v2.1 wiki]
* Login with SSH on
** default IP: 192.168.1.1
** username: root
* Install a WebGUI: [https://openwrt.org/docs/guide-quick-start/ssh_connect_to_the_internet_and_install_luci Use SSH to connect to the internet and install Luci Web interface]

= BSD Images =
==NetBSD==
[[File:Netbsd2.png]]

To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page]

* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]
** [http://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select 64bit - RockPro64]
** size: 339 MB
* Console and SSH default login:
** username: root
** password: [none]
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]

==OpenBSD==
http://files.pine64.org/sw/pine64_installer/json/openbsd.jpg

Instructions to get OPenBSD on your ROCKPro64 [https://github.com/jasperla/openbsd-rockpro64 are here.]

Forum discussions [https://forum.pine64.org/forumdisplay.php?fid=109 are there.]

= Android Images =
== Android 9.0.0 ==
http://files.pine64.org/sw/pine64_installer/json/android_9.png

=== Stock for DD method [eMMC Boot] [20200804] ===
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* Supports new RockPro64 AP6256 Wifi/BT module
* Support Sony IMX214 camera module and works on both MiPi-CSI ports
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)
* DD image for 8GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-8GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 7287fd0846616354615c8d3eff6a2a92
*** File Size: 602MB
* DD image for 16GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 78352bbf21198d062af8bab2217ee691
*** File Size: 611MB
* DD image for 32GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): c5c8dce419478f75f85f893ee4808dbd
*** File Size: 624MB
* DD image for 64GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): aab1cf4d30c4d16e6ce2672f3ecae935
*** File Size: 666MB

=== Stock for RK Flash tool [eMMC Boot] [20200804] ===
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20200708_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]
** MD5 (GZip file): 9ac830527814521e15b009fa2503c9e3
** File Size: 589MB

=== Stock for DD method [eMMC Boot] [20200708] ===
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* Supports new RockPro64 AP6256 Wifi/BT module
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)
* DD image for 8GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-8GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): ef5f5a890a9270734e0adee21f006837
*** File Size: 597MB
* DD image for 16GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 179bd684a468f800a86f7c658a543bef
*** File Size: 606MB
* DD image for 32GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): d930b757c4427be07b83c37a9c8494a1
*** File Size: 630MB
* DD image for 64GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 09a970d68a10bdb3d6495d55860940e6
*** File Size: 660MB

=== Stock for RK Flash tool [eMMC Boot] [20200708] ===
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20200708_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]
** MD5 (GZip file): 6d060ddd47ebcfd5cfcdbf90ec042c97
** File Size: 589MB

=== Stock for DD method [eMMC Boot] [20190427] ===
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)
* DD image for 16GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 3BA4C72D81BCFC4C21B3B5D2BCB4F9F7
*** File Size: 609MB
* DD image for 32GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 4965CCF50A8F06CEB2E4A6828A21F31C
*** File Size: 627MB
* DD image for 64GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 748EC28FE5D5395D33E858C913D744BF
*** File Size: 663MB

=== Stock for DD method [micro SD Boot] [20190506] ===
* DD image to microSD card and boot.
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)
* DD image for 8GB microSD card
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): E1C551E8106E178841E1C3F71432194A
*** File Size: 599MB
* DD image for 16GB microSD card
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 73592FDD5A2F52F08020F16AD99E8C8C
*** File Size: 609MB
* DD image for 32GB microSD card
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 74DE0FE528F210E4DD483B411A71904B
*** File Size: 627MB
* DD image for 64GB microSD card
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284
*** File Size: 663MB

=== Stock for RK Flash tool [eMMC Boot] [20190427] ===
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]
** MD5 (GZip file): 046BA4A07933120809FBE1B9577B7341
** File Size: 592MB

== Android 8.1.0 ==
http://files.pine64.org/sw/pine64_installer/json/android_8.png

=== Stock for DD method [eMMC Boot] [20180828] ===
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 9AEE21BC1B9DE886DCB0E64FA123988A
** File Size: 414MB

=== Stock for DD method [micro SD Boot] [20181212] ===
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)
* DD image (for 8GB micoSD card and above)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 5A6BB7FCD7B3F77FCEE99CE462AE7405
** File Size: 616MB

=== Stock for RK Flash tool [eMMC Boot] [20180828] ===
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 4DACFE927BB09EE9C56B5232A7F624EE
** File Size: 415MB

== Android 7.1.2 ==
http://files.pine64.org/sw/pine64_installer/json/android_7.png

=== Stock for DD method [eMMC Boot] [20180809] ===
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]
** MD5 (XZ file): 00F194017557017C2588724686E90CEA
** File Size: 498MB

=== Stock for RK Flash tool [eMMC Boot] [20180809] ===
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]
** MD5 (XZ file): 197A9905B48441D8655E7542F4643FE9
** File Size: 483MB

=== Stock for DD method [micro SD Boot] [20180920] ===
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180920_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]
** MD5 (XZ file): CE39642A379B357BB3E4BC80ACA2E0CE
** File Size: 765MB

=== Stock for DD method [eMMC Boot] [20180518] ===
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 33622034ACDBC31A7D7BB01ED634E29B
** File Size: 345MB

=== Stock for RK Flash tool [eMMC Boot] [20180518] ===
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 90C1991DADAE13ADC94E927F171F8920
** File Size: 342MB

=== Stock for install from SDcard to eMMC [microSD Boot] [20180921] ===
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel and UI follow tablet way (means not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180921_stock_android_7.1_sdboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): c6900e82a1d6ef397dcac241f76f43c9
** File Size: 350MB

== Android SDK ==

=== Android P SDK [v9.0] ===
* [http://files.pine64.org/SDK/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz Direct Download from pine64.org]
** MD5 (TAR-GZip file): 3CEBEEFD1A873BEEEC149148A785D92E
** File Size: 125.16GB

= For Linux Developer =

The Ayufan github page
* [https://github.com/ayufan-rock64/linux-build/releases Is here.]

Below are the LPDDR4 driver for RK3399

* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build]
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin rk3399_ddr_666MHz_v1.11.bin, this is alpha version]
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin rk3399_ddr_933MHz_v1.11.bin, this is alpha version]

ROCKPro64 related files

* [http://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz ROCKPro64 Kernel file]
* [http://files.pine64.org/os/ROCKPro64/driver/trust.img trust.img]

= Miscellaneous tools =

** [http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]
** [[Set MacAddress on ROCK64]]
** [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]
** [http://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]
** [http://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]

::::::::::[[ROCKPro64_Software_Release#top | Top of page]]

[[Category:ROCKPro64]]

ROCKPro64 Hardware compatibility

2020-10-17T21:05:32Z

Abcde: added category

= ROCKPro64 accessories - by type =

== PCIe devices ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes
|-
| NIC || Intel I350 Dual Port || || Mainline-5.4 || good || SR-IOV fails
|-
| NIC || Intel X520 Dual Port || 8086:10fb || Mainline-5.6 || good || SR-IOV fails
|-
| NIC || Intel 82571EB Dual Port (HP NC360T) || || Mainline-5.6 || crash || kernel crash on boot
|-
| GPU || nVidia GTX-645 || || Mainline-5.4 || crash || BAR size too small, triggers PCIe error handling bug
|-
| PCIe Switch || PCIE-EUX1-04 Ver.002 || || Mainline-5.4 || good ||
|-
| SATA Controller || ASM1062 4-Port || || Mainline-5.6 || good || tested only with one disk attached
|-hw
| SATA Controller || ASM1062 (rev 02) 4-Port ||1d87:0100|| Ayufan-4.4.190 || good || tested with four disks, 3 in raid 5
|-
| SATA Controller || IOCrest (Same as Syba?) SI-PEX40063 4-port, Marvell 88SE9235 chip || 1b4b:9235 || Debian unstable 5.7, 5.8 || good || Tested with two disks. SATA errors occurred with a WD Red drive in a cheap enclosure; resolved by connecting the same drive directly to the card.
|-
| SATA Controller || Ziyituod SATA Card ASM 1062+1093 6-Port || 1b21:0625 || Mainline-4.4 (armbian) || good || tested with 6 disks ||
|-
| Host Bus Adapter || LSI SAS 9211-4i || 1000:0070 || Ayufan-4.4.197 || good || tested with four disks attached
|}

== NVMe SSD drives ==
{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Kernel || Result || Notes || Power options Active only || Save power setting?
|-
| NVMe || Samsung 970 Evo || 500 GB || || Mainline-5.6 || good || - || defaults || defaults
|}

== USB hardware ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes
|-
|}

== USB C alternate mode DP ==
Note that only USB C alternate mode Display Port will pass video. Any HDMI, DVI or VGA port must be converted internally by the device from Display Port - or the device won't work for video.
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes
|-
|}

== Other hardware ==
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes
|-
|}
[[Category:ROCKPro64]]

ROCKPro64

2020-10-17T21:05:01Z

Abcde: added categories

The [https://www.pine64.org/rockpro64/ '''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.

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.

= Board layout =
[[File:ROCKPro64_annotated.jpg]]

[[File:ROCKPro64v21FRONT.jpg|200px|thumb|right|A hi-res picture of v2.1 front]]

[[File:ROCKPro64v21REAR.jpg|200px|thumb|right|A hi-res picture of v2.1 rear]]

== 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): 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): perfoms a reset.

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

== Connectors, sockets and headers ==
{| class="wikitable sortable"
! 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;" | 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;" | 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 || 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, S = boot from the µSD card, M = boot from the eMMC module, X = unsupported combination):

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot
|-
| 0 || 0 || 0 || X
|-
| 0 || 0 || 1 || X
|-
| 0 || 1 || 0 || M
|-
| 0 || 1 || 1 || X
|-
| 1 || 0 || 0 || S
|-
| 1 || 0 || 1 || S
|-
| 1 || 1 || 0 || M
|-
| 1 || 1 || 1 || S
|}

=== 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.

<div class="center" style="background-color: yellow;">[[#top | '''Return to top of page''']]</div>

= Getting Started =

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

== Start here - Software and OS Image Builds ==

In the '[[ROCKPro64 Software Release]]' 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 how to load each image.

The list includes OS images and descriptions of:

[{{fullurl:ROCKPro64_Software_Release#Armbian}} http://files.pine64.org/sw/pine64_installer/json/armbian.png] [[ROCKPro64_Software_Release#Armbian|'''Armbian (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#Debian_by_mrfixit2001}} http://files.pine64.org/sw/pine64_installer/json/debian.png] [[ROCKPro64_Software_Release#Debian_by_mrfixit2001|'''Debian (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#DietPi}} http://files.pine64.org/sw/pine64_installer/json/dietpi.png] [[ROCKPro64_Software_Release#DietPi|'''DietPi (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#OpenMediaVault}} http://files.pine64.org/sw/pine64_installer/json/omv.png] [[ROCKPro64_Software_Release#OpenMediaVault|'''Open Media Vault (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#LibreELEC.28KODI.29}} http://files.pine64.org/sw/pine64_installer/json/libreelec.png] [[ROCKPro64_Software_Release#LibreELEC.28KODI.29|'''LibreELEC for KODI (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#Slackware}} http://files.pine64.org/sw/pine64_installer/json/slackware.png] [[ROCKPro64_Software_Release#Slackware|'''Slackware (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#Nems_Linux}} http://files.pine64.org/sw/pine64_installer/json/nems.jpg] [[ROCKPro64_Software_Release#Nems_Linux|'''Nagios Enterprise Monitoring Server (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#NextCloudPi}} http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png] [[ROCKPro64_Software_Release#NextCloudPi|'''NextCloudPi (microSD and eMMC Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#Cent_OS}} http://files.pine64.org/sw/pine64_installer/json/centos.jpg] [[ROCKPro64_Software_Release#Cent_OS|'''Cent OS (microSD Boot)''']]

[{{fullurl:ROCKPro64_Software_Release#Manjaro_ARM}} http://files.pine64.org/sw/pine64_installer/json/manjaro.png] [[ROCKPro64_Software_Release#Manjaro_ARM|'''Manjaro ARM (microSD and eMMC Boot)''']]

[[File:Openwrt_logo_square.png|100px]] [[ROCKPro64_Software_Release#OpenWrt|'''OpenWrt (microSD and eMMC Boot)''']]

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

== More advanced Linux bits ==

Some Linux tips are given below.

=== How to update your Linux ===

For Debian/Ubuntu images entering the following commands at a terminal prompt

<code>sudo apt-get update</code> 
<code>sudo apt-get upgrade</code>

will keep your installation up to date. To update Ayufan images to the next release (when available) use the following command

<code>sudo apt-get dist-upgrade</code>

If you are happy to update your system to pre-releases of Ayufan images then modify /etc/apt/sources.list.d/ayufan-rock64.list as per the comment in that file.

The kernel in Ayufan releases is under active development and, if you wish to install a later version, then it is best to use a package manager. In synaptic (for example), if you search for package names linux-image-4.4 you should see your currently installed version(s) as well as any more recent ones. Similarly if you wish to install the mainline kernel then searching for linux-image-4.18 will show you what is available. '''At the time of writing (August 2018) there are significant features missing from the mainline kernel for aarch64 processors (e.g. HDMI sound).'''

=== Useful scripts ===
After you install an Ayufan image you will find some scripts in /usr/local/sbin/ and /usr/local/bin/ that may be useful. (Need to expand this section)

=== Video playback ===
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 deskop releases.) At which stage rkmpv myvideo.mp4 will play a fullscreen, hardware assisted, version of your video. rkmpv is at /usr/local/bin/rkmpv

=== Swapping kernel versions ===
extlinux is in use on Ayufan images (at least) which enables some switching between installed kernel versions - [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/extlinux.md intro documentation is here.] In particular after you install any additional kernels, you can edit your /boot/extlinux/extlinux.conf file to specify which of the kernels you have installed to use for the next boot.

From Ayufan version 0.7.11 the script /usr/local/sbin/change-default-kernel.sh does a nice little menu swap for you if you run it as root (sudo).

=== Using an NVMe disk for 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.

== More advanced bits related to any OS ==

This section gives some hints for advanced users.

=== Setup a serial console (UART)===
The early adopters (and late-comers who fiddle excessively with their boards!) have a need to monitor the low-level boot behaviour: this is done with a serial console and there [https://forum.pine64.org/showthread.php?tid=6387 is a great description how to get this working specifically for your ROCKPro64 here.]

=== Booting from USB or PXE ===

The default choice of boot device is first eMMC (if present) then SDcard. See [[ ROCKPro64_Main_Page#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_Main_Page#Useful_scripts | useful scripts above.]]) The NOOB wiki page has more details [[NOOB#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.]

=== 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_Main_Page#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 SDcard 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 SDcard 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://store.pine64.org/?product=rockpro64-pci-e-x4-to-m-2ngff-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://store.pine64.org/?product=rockpro64-pci-e-to-dual-sata-ii-interface-card ROCKPro64 PCIe interface card.] Please note the card does not include the power cable - that is a [https://store.pine64.org/?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://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-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://store.pine64.org/?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.'''

=== RTC battery backup ===
The Pine store has a couple of options for RTC battery backups: a [https://store.pine64.org/?product=rtc-backup-battery-aaa-battery AAA version here] or a [https://store.pine64.org/?product=rtc-backup-battery-cr-battery CR-2032 version here.] Instructions for plugging in either of them are also on the [[ Accessories_Step_by_Step_Guides| Accessories page ]]

=== Acryllic open enclosure ===
Assembly instructions for the [https://store.pine64.org/?product=pine64-acrylic-open-enclosure acryllic enclosure] from the Pine store are also on the [[ Accessories_Step_by_Step_Guides| Accessories page ]]

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

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

= [[ROCKPro64_Hardware_Accessory_Compatibility|Hardware Compatibility]] =
== Hardware Compatibility Page ==
Please contribute to the hardware compatibility page, which lists hardware which has been tested with the rockpro64, whether successful or not.

* [[ROCKPro64_Hardware_Accessory_Compatibility#PCIe devices|PCIe devices]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#NVMe_SSD_drives|NVMe SSD drives]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#USB_hardware|USB hardware]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#USB_C_alternate_mode_DP|USB C alternate mode DP]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#Other_hardware|Other hardware]]

== Limitations ==
=== PCIe card issue and/or asynchronous external abort on flash read/write ===
==== Older firmware overwrites actively used memory ====
Some people get system freeze when:
* use SATA disk with ROCKPro64 PCIe card. (maybe on newer PCIe card ASM1062 vs ASM1061)
* or do read or write 4GB to the flash. (not using PCIe)

If you connect the serial console you will see a Linux kernel oops: (a)synchronous external abort.

Both issues are in fact the same software BUG. There is no hardware problem.
Currently most OS do use uboot with a rockpro blob FW which use memory that Linux kernel is not aware of.
People are currently fixing this BUG, but it may take some time.
In the mean time, you can fix it manually.

The latest u-boot can boot the rockpro64 without any blobs from rockchip. Install first arm-none-eabi-gcc and aarch64-linux-gnu-gcc compiler, then run the following commands:

git clone https://github.com/ARM-software/arm-trusted-firmware.git atf
make -C atf CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399 bl31
git clone https://gitlab.denx.de/u-boot/u-boot.git u-boot
cd u-boot/
git checkout v2020.01-rc5
make rockpro64-rk3399_defconfig
BL31=../atf/build/rk3399/release/bl31/bl31.elf make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu-

Which gives you idbloader.img and u-boot.itb. Copy them to the rockpro64, and run the following: (Or put your SD card into your PC)

sudo dd if=idbloader.img of=/dev/mmcblk0 seek=64
sudo dd if=u-boot.itb of=/dev/mmcblk0 seek=16384
sync

==== PCIe controller hardware error handling bug ====
There is an issue with the rk3399 pcie controller that is currently unmitigated:
*[https://lore.kernel.org/linux-pci/CAMdYz...gmail.com/ LKML Original Thread]
*[https://lkml.org/lkml/2020/4/6/320 LKML Additional Information]

The rk3399 pcie controller throws either a synchronous abort or a SError when a pcie device sends an unknown message.

The error type is determined by which cpu cluster handles the message.

=== Virtualization ===
The PCIe controller on the rk3399 is not behind an IOMMU.
This means it is not possible to safely pass through PCIe devices to a virtual machine.

= 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 provide 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 4096x2160 with AFBC supported；The other supports 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support display, 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
* 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

== Working Features ==
{| class="wikitable sortable"
! style="font-weight:bold;" | Feature/Option
! style="font-weight:bold;" | Android
! style="font-weight:bold;" | Android Version
! style="font-weight:bold;" | Linux
! style="font-weight:bold;" | Linux Version
! style="font-weight:bold;" | Test/Verify Steps
! style="font-weight:bold;" | Notes
! style="font-weight:bold;" | Product Link
|-
| Pine64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe this will help get this working? https://github.com/avafinger/pine64-touchscreen
| https://store.pine64.org/?product=7-lcd-touch-screen-panel
|-
| 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/No
|
|
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons.
| https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-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 then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| http://wiki.pine64.org/index.php/ROCKPro64_Main_Page#OTG_mode
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use ATS. https://github.com/tuxd3v/ats
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out what Frank Mankel has done. https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2
|
|-
| 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.
|
|-
| 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://store.pine64.org/?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://store.pine64.org/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use fanctl to control the fan while keeping your CPU cool https://github.com/tuxd3v/fanctl
| https://store.pine64.org/?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
* [http://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [http://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [http://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [http://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [http://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [http://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [http://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]
* [http://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [http://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [http://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.
** [http://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
** [http://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
** [http://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCK64 RoHS Report]

= Datasheets for Components and Peripherals =
* Rockchip RK3399 SoC information:
** [http://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
** [http://opensource.rock-chips.com/images/2/28/Rockchip_RK3399_Datasheet_V1.8-20180529.pdf Rockchip RK3399 Datasheet V1.8]
** [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
** [http://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]
* LPDDR4 (200 Balls) SDRAM:
** [http://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]
* eMMC information:
** [http://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [http://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [http://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [http://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
** [http://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:
** [http://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [http://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]
* Heatsink related info:
** [http://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
** [http://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]
* Wireless related info:
** [[Media:AP6356 datasheet V1.0 07252014.pdf|AMPAK AP6356 2x2 Wi-Fi + Bluetooth4.1 Datasheet]]
* Ethernet related info:
** [http://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]
* Peripheral related info:
** [http://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]
* Remote control button mapping
** [http://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]

= 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
*[http://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[http://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

= Other Resources =
* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [[RockPro64 Guides]]
* IRC Server: irc.pine64.org Channel: ROCK64
* [https://store.pine64.org/?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.]

<div class="center" style="background-color: yellow;">[[#top | '''Return to top of page''']]</div>

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

ROCK64 Software Releases

2020-10-17T21:03:14Z

Abcde: added category

= Linux Image Releases =

== Armbian==

http://files.pine64.org/sw/pine64_installer/json/armbian.png

* Version 5.88 onward support Rock64-v3 board
* To find out more about Armbian and available options please visit their [https://www.armbian.com/rock64/ site]
* Armbian pack as 7zip, please unzip first before dd.
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]

=== Armbian Ubuntu Bionic Desktop on mainline Kernel [microSD / eMMC Boot] ===
** [https://dl.armbian.com/rock64/Bionic_current_desktop Direct download from Armbian]
* Login with
** username: root
** password: 1234

=== Armbian Debian Buster on mainline Kernel [microSD / eMMC Boot] ===
** [https://dl.armbian.com/rock64/Buster_current Direct download from Armbian]
* Login with
** username: root
** password: 1234

=== Armbian Ubuntu Bionic Desktop on legacy BSP Kernel [microSD / eMMC Boot] ===
** [https://dl.armbian.com/rock64/Bionic_legacy_desktop Direct download from Armbian]
* Login with
** username: root
** password: 1234

=== Armbian Debian Buster on legacy BSP Kernel [microSD / eMMC Boot] ===
** [https://dl.armbian.com/rock64/Buster_legacy Direct download from Armbian]
* Login with
** username: root
** password: 1234

== LibreELEC(KODI) ==

http://files.pine64.org/sw/pine64_installer/json/libreelec.png

=== Official LibreElec KODI Leia 9.2 Build Image [microSD / eMMC boot] ===

* Unzip and DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]
** [http://releases.libreelec.tv/LibreELEC-RK3328.arm-9.2.0-rock64.img.gz Direct download from LibreElec site]
** [http://files.pine64.org/os/ROCK64/libreelec/LibreELEC-RK3328.arm-9.2.0-rock64.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 56FD7F2CCFF345F6CCE6524C50E4A76A
*** File Size: 124MB

== Debian Stretch ==

http://files.pine64.org/sw/pine64_installer/json/debian.png

=== Debian Stretch Minimal 64bit (arm64) OS Image [microSD / eMMC Boot] [0.8.3] ===
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-minimal-rock64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]
** size: 212MB
* Login with
** username: rock64
** password: rock64
*Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6309&pid=39314#pid39314 here]

== Debian by mrfixit2001 ==

http://files.pine64.org/sw/pine64_installer/json/debian.png

=== Minimal Debian [microSD / eMMC Boot] ===
** DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]
** [https://github.com/mrfixit2001/debian_builds/releases Direct download from mrfixit2001's github]
** Version 190514 onward support Rock64-v3 board
* Login with
** username: rock
** password: rock

== Ubuntu 18.04 Bionic ==

http://files.pine64.org/sw/pine64_installer/json/penguin.png

=== Ubuntu 18.04 Bionic LXDE Desktop Image [microSD / eMMC Boot] [0.8.3] ===
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]
** size: 676MB
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/bionic-lxde-rock64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]
* Login with
** username: rock64
** password: rock64

=== Ubuntu 18.04 Bionic minimal 64bit (arm64) Image [microSD / eMMC Boot] [0.8.3] ===
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/bionic-minimal-rock64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]
** size: 295MB
* Login with
** username: rock64
** password: rock64

=== Ubuntu 18.04 Bionic minimal 32bit (armhf) Image [microSD / eMMC Boot] [0.8.3] ===
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/bionic-minimal-rock64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]
** size: 287MB
* Login with
** username: rock64
** password: rock64

=== Ubuntu 18.04 Bionic Containers Image (DockerCE & Kubernetes)[microSD / eMMC Boot] [0.8.3] ===
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/bionic-containers-rock64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]
** size: 390MB
* Login with
** username: rock64
** password: rock64
*Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6309 here]

== OpenMediaVault ==

http://files.pine64.org/sw/pine64_installer/json/omv.png

=== Jessie OpenMediaVault Community Build Image [microSD to eMMC] [0.5.15-136] by ayufan ===
* [https://www.openmediavault.org/ openmediavault is the next generation network attached storage (NAS) solution, click link to OMV main page]
* DD image to microSD card. Highly recommend using [https://etcher.io/ Etcher]
** Shorting the eMMC PIN with a jumper as shown on the 1st image of [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]. After power ON the box for 2-3 second, quickly remove the jumper. After boot, it will prompt for confirmation 'Y' to start writing the new image to the eMMC. Then follow the instructions on the screen
'''* There's a bug with eMMC in the "Stable" version of openmediavault linked from the wiki page. In order to use eMMC, please you need to be on the latest (pre-release) version which is linked here https://github.com/ayufan-rock64/linux-build/releases'''
*
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github]
* [http://files.pine64.org/os/ROCK64/omv/jessie-openmediavault-rock64-0.5.15-136-armhf_sd2emmc.img.xz Direct download from pine64.org]
** MD5 (XZ file): 7E423EF9146EA15403E7D1B4EA30594A
** File Size: 487MB
** Credentials (console/ssh, except OMV): rock64/rock64
** Credentials (OMV for Web): admin/openmediavault
** Credentials (OMV for console): root/openmediavault
* [[OpenMediaVault|OpenMediaVault Basic Setup]]
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]

=== Stretch OpenMediaVault OS Image 32bit (armhf) [microSD / eMMC Boot] [0.8.3] ===
* [https://www.openmediavault.org/ openmediavault is the next generation network attached storage (NAS) solution, click link to OMV main page to learn more]
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github] ''(pay attention to the release tag. Don't accidentaly choose a pre-release build)''
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rock64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]
** size: 391MB
* WebGUI Login:
** username: admin
** password: openmediavault
* SSH/ Console Login:
** username: root
** password: openmediavault
*** '''NB! You need to enable root login in OMV WebGUI'''
* [[OpenMediaVault|OpenMediaVault Basic Setup]]
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]
*Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6309 here]

=== Stretch OpenMediaVault OS Image 64bit (arm64) [microSD / eMMC Boot] [0.8.3] ===
* [https://www.openmediavault.org/ openmediavault is the next generation network attached storage (NAS) solution, click link to OMV main page to learn more]
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]
* [https://github.com/ayufan-rock64/linux-build/releases/ Release notes on ayufan Linux github] ''(pay attention to the release tag. Don't accidentaly choose a pre-release build)''
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]
** size: 340MB
* WebGUI Login:
** username: admin
** password: openmediavault
* SSH/ Console Login:
** username: root
** password: openmediavault
*** '''NB! You need to enable root login in OMV WebGUI'''
* [[OpenMediaVault|OpenMediaVault Basic Setup]]
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]
*Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6309 here]

== NextCloudPi==

http://files.pine64.org/sw/pine64_installer/json/nextcloudpi.png

=== NextCloudPi Community Build Image [microSD / eMMC Boot] [03-10-19] ===
* NextCloudPi comes not only with NextCloud preinstalled, but also with management tools for backups, SSL certificates, SAMBA, enhanced security and more.
* Visit the project's [http://nextcloudpi.com website]
* You can follow the ongoing discussion about NextCloudPi on the [https://forum.pine64.org/showthread.php?tid=6047 PINE64 forum]
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
** [http://files.pine64.org/os/ROCK64/nextcloudplus/NextCloudPi_Rock64_03-10-19.img.xz Direct download from pine64.org]
*** MD5 (XZ file): 1432c8b8082696f38770004b3cb5ac1e
*** File Size: 310MB
* Login with
** username: root
** password: 1234

== Recalbox ==
http://files.pine64.org/sw/pine64_installer/json/recalbox.png

=== Recalbox Community Build Image [microSD / eMMC boot] ===
* '''Only support ROCK64 ver2 SBC'''
* Recalbox allows you to re-play a variety of videogame consoles and platforms in your living room, with ease!
* To find out more about Recalbox and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7111 PINE64 forum thread]
*Visit the project's [https://www.recalbox.com/ website]
* DD image (for 8GB micoSD card and above)
** [https://github.com/mrfixit2001/recalbox_rock64/releases Direct download latest release build from mrfixit2001 github]

== Slackware==

http://files.pine64.org/sw/pine64_installer/json/slackware.png

* Slackware is a very old, interesting, convenient and easy distribution.
* Visit the project's website here (http://fail.pp.ua)
* You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=5868)

=== Slackware Aarch64 Miniroot Community Build Image [microSD Boot] [20190623] ===
* System without a graphical shell
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
** [http://files.pine64.org/os/ROCK64/slackware/slarm64-current-aarch64-base-rootfs-15Jun19-4.4.183-rock64-build-20190623.img.xz Direct download from pine64.org]
*** MD5 (XZ file): 2248d0153b4ba6a1a11bbd13d3f4304a
*** File Size: 252MB

=== Slackware Aarch64 XFCE Community Build Image [microSD Boot] [20190623] ===
* System with a graphical shell
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
** [http://files.pine64.org/os/ROCK64/slackware/slarm64-current-aarch64-xfce-rootfs-15Jun19-4.4.183-rock64-build-20190623.img.xz Direct download from pine64.org]
*** MD5 (XZ file): 3e5fdacd534a3c3a8c824239f897202f
*** File Size: 679MB

* Login with
** Username : root
** Password : password

* To run the OS on eMMC
**Flash the image to micro SD, power up the board with micro SD and login
**Copy the image file to micro SD by using SFTP. The image file must be in .img. ''note : root user are not allow transfer file to micro SD.''
**After finish copy the file, power off the board and add eMMC module to the board
**Bootup the board, run below command for flashing to eMMC module
***>>dd if=[image file] of=/dev/mmcblk1 bs=10M
****''example : dd if=slack-current-aarch64-xfce_08May18-4.4.126-rock64-build-20180508.img of=/dev/mmcblk1 bs=10M''
***then edit 2 files in eMMC module:
***>> mount /dev/mmcblk1p1 /media
***>> echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt
***>> sed -i 's:mmcblk0p1:mmcblk1p1:' /media/etc/fstab
**After done, power off board and remove micro SD. Then bootup with only eMMC module.

== Manjaro ARM ==

http://files.pine64.org/sw/pine64_installer/json/manjaro.png
* '''Only support ROCK64 ver2 SBC'''
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum]
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]
* Console and SSH default login:
** username: manjaro
** password: manjaro

=== Manjaro KDE ARM Community Build Image [microSD / eMMC Boot] [19.04] ===
* [https://osdn.net/frs/redir.php?m=pumath&f=%2Fstorage%2Fg%2Fm%2Fma%2Fmanjaro-arm%2Frock64%2Fkde%2F19.04%2FManjaro-ARM-kde-rock64-19.04.img.xz Direct download from osdn.net]
* [http://files.pine64.org/os/ROCK64/manjaro/Manjaro-ARM-kde-rock64-19.04.img.xz Direct download from pine64.org]
** size: 993MB
** MD5 (XZip file): 25319e6e944a45cf10642dd77a7f8742

=== Manjaro LXQT ARM Community Build Image [microSD / eMMC Boot] [19.04] ===
* [https://osdn.net/frs/redir.php?m=pumath&f=%2Fstorage%2Fg%2Fm%2Fma%2Fmanjaro-arm%2Frock64%2Flxqt%2F19.04%2FManjaro-ARM-lxqt-rock64-19.04.img.xz Direct download from osdn.net]
* [http://files.pine64.org/os/ROCK64/manjaro/Manjaro-ARM-lxqt-rock64-19.04.img.xz Direct download from pine64.org]
** size: 757 MB
** MD5 (XZip file): 7e0b6874e9155707cc9dedf674613829

=== Manjaro ARM Minimal Community Build Image [microSD / eMMC Boot] [19.04] ===
* [https://osdn.net/frs/redir.php?m=constant&f=%2Fstorage%2Fg%2Fm%2Fma%2Fmanjaro-arm%2Frock64%2Fminimal%2F19.04%2FManjaro-ARM-minimal-rock64-19.04.img.xz Direct download from osdn.net]
* [http://files.pine64.org/os/ROCK64/manjaro/Manjaro-ARM-minimal-rock64-19.04.img.xz Direct download from pine64.org]
** size: 327 MB
** MD5 (XZip file): 2490a4c416c226458971a308410683c0

== Cent OS ==

http://files.pine64.org/sw/pine64_installer/json/centos.jpg

=== CentOS-7 Community Build Image [microSD Boot] ===
* '''Only support ROCK64 ver2 SBC'''
* Centos-7.4.1708 with kernel from Armbian-5.69 (minimum build)
** DD image (for 8GB micoSD card and above)
** [https://github.com/Project31/centos-pine64/releases/download/v7.4.1708-v5.59/centos7-rock64.img.xz Project31 download mirrors]
* To find out more on installation process, please visit their [https://project31.github.io/pine64/ Project31 site]
* Login with
** username: root
** password: centos

== DietPi ==

http://files.pine64.org/sw/pine64_installer/json/dietpi.png

=== DietPi Community Build Image [microSD / eMMC boot] ===
* '''Only support ROCK64 ver2 SBC'''
* DietPi is a lightweight linux distribution of Debian Stretch
* To find out more about DietPi and available tweaks to the installation please visit the [http://forum.pine64.org/showthread.php?tid=1068 PINE64 forum thread]
* DD image (for 8GB micoSD card and above)
** [http://dietpi.com/downloads/images/ Direct download latest release build from dietpi.com and look for DietPi_Rock64-arm64-(xxx).7z]
* Login with
** username: root
** password: dietpi

== NEMS Linux ==

http://files.pine64.org/sw/pine64_installer/json/nems.jpg
* '''Only support ROCK64 ver2 SBC'''
* NEMS stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers.
* To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7306 PINE64 forum thread]
* Login with
** Username: nemsadmin
** Password: nemsadmin
* [https://docs.nemslinux.com/installation Installation Guide]
* To find out more on NEM Linux, please visit their [https://nemslinux.com/ site]

=== NEMS Linux [microSD / eMMC boot] [v1.5 - build 2] ===
* DD image (for 16GB micoSD card and above)
** [https://nemslinux.com/download/nagios-for-pine64.php Download torrent seed from NEMS Linux]
** [http://files.pine64.org/os/ROCK64/nems/NEMS_v1.5-Rock64-Build2.zip Direct download from pine64.org]
*** MD5 (XZ file): 6e2088922c5d197db8b8ba3057120389
*** File Size: 1.30GB

== Lakka ==

http://files.pine64.org/sw/pine64_installer/json/lakka.png

=== Lakka Community Build Image [microSD / eMMC Boot] ===
* [http://www.lakka.tv/ Lakka] The open source game console; a lightweight Linux distribution that transforms the Rock64 into a full blown retrogaming console
* Visit [https://forum.pine64.org/showthread.php?tid=5354 PINE64 forum] for more information about the Lakka release
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
** [http://www.lakka.tv/get/linux/rock64/ Direct download from Lakka]
* [[Lakka|Lakka Basic Setup]]

== Volumio Digital Audio Player ==

http://files.pine64.org/sw/pine64_installer/json/volumio.png

* '''Only support ROCK64 ver2 SBC'''
* Volumio is a linux-based headless DAP (digital audio player), which connects to your home stereo system or your DAC
* Visit the project's website [https://volumio.org/ here]
* You can follow the ongoing discussion about Volumio on the [https://forum.pine64.org/showthread.php?tid=5322 PINE64 forum]

=== Volumio Digital Audio Player Community Build Image [microSD Boot] [2.528-2019-01-12] ===
* DD image (for 8GB micoSD card and above)
** [http://updates.volumio.org/rock64/volumio/2.528/volumio-2.528-2019-01-12-rock64.img.zip Direct download from volumio.org]
*** MD5 (Zip file): 5b13311deac8a6fa89bf950e80285413
*** File Size: 314MB
* Login with
** Username: volumio
** Password: volumio
* '''Volumio is controlled using a Web-GUI which can be accessed via a web browser using the boards IP or volumio.local/'''

== Fedora ==

http://files.pine64.org/sw/pine64_installer/json/fedora.png

=== Fedora Minimal Community Build Image [microSD boot] [Preliminary Build] ===
* [https://github.com/fire219/rock64-fedora/releases/ Follow up on Fire219 github]

== Yocto ==

http://files.pine64.org/sw/pine64_installer/json/yocto.png

* [http://opensource.rock-chips.com/wiki_Yocto#Images Please follow this Rockchip-Yocto wiki page]
* Here is build command: MACHINE=evb-rk3328 DISTRO=rk-wayland . ./setup-environment -b build

= BSD Image Releases =

==NetBSD==

[[File:Netbsd.png]]

* To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page]
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]
** [http://www.invisible.ca/arm/netbsd-9/202009232320Z/NetBSD-9-aarch64-202009232320Z-rock64.img.gz Download directly from NetBSD]
** size: 280MB
* Console and SSH default login:
** username: root
** password: [none]
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]

==OpenBSD==

[[File:Openbsd.png]]

* You can install OpenBSD on your Rock64 by following [https://github.com/krjdev/rock64_openbsd these instructions]

= Android Image Releases =

== Android TV 9.x eMMC (No Google Play) ==

http://files.pine64.org/sw/pine64_installer/json/android_9.png

'''* For install Playstore on Android 9.0, please follows [https://forum.pine64.org/showthread.php?tid=8655 this forum thread]'''

=== Android 9.0 Stock Image [eMMC Boot] using DD method [20190617] ===
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]
* Please allow 3-5 minutes boot up time on first time for initialization
* DD image for 16GB eMMC module
** [http://files.pine64.org/os/ROCK64/android/ROCK64_dd_20190617_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): D985808B4CA912201372DC2F5F322AE9
*** File Size: 560MB
* DD image for 32GB eMMC module
** [http://files.pine64.org/os/ROCK64/android/ROCK64_dd_20190617_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 5D65A44F78BD08B4584413C8BEEAAF05
*** File Size: 579MB
* DD image for 64GB eMMC module
** [http://files.pine64.org/os/ROCK64/android/ROCK64_dd_20190617_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): B34D1C119386CBA1658E5F0FB9E4413D
*** File Size: 615MB

=== Android 9.0 Stock Image [eMMC Boot] using ROCKChip tools method [20190617] ===
* Please unzip first and then using Android tool to flash in
* The OTG port located at top USB 2.0 port, needs USB type A to type A cable.
* Please allow 3-5 minutes boot up time on first time for initialization
* This is Android TV build version
** [http://files.pine64.org/os/ROCK64/android/ROCK64_20190617_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 9B717263E7749A732C8B5C7D7D59C5C6
*** File Size: 544MB

=== Android 9.0 Stock Rooted Image [eMMC Boot] using DD method [20190618] ===
* DD image to eMMC module using USB adapter for eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]
* Please allow 3-5 minutes boot up time on first time for initialization
* DD image for 16GB eMMC module
** [http://files.pine64.org/os/ROCK64/android/ROCK64_dd_20190618_stock_rooted_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): DBB5B3D46B77A33BC9F09173C9788E6E
*** File Size: 561MB
* DD image for 32GB eMMC module
** [http://files.pine64.org/os/ROCK64/android/ROCK64_dd_20190618_stock_rooted_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 5F3B97EA72B3227082500B3FB1FAB44A
*** File Size: 579MB
* DD image for 64GB eMMC module
** [http://files.pine64.org/os/ROCK64/android/ROCK64_dd_20190618_stock_rooted_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 6833B124ABA3AC2269A6B4F51EFD1109
*** File Size: 615MB

=== Android 9.0 Stock Rooted Image [eMMC Boot] using ROCKChip tools method [20190618] ===
* Please unzip first and then using Android tool to flash in
* The OTG port located at top USB 2.0 port, needs USB type A to type A cable.
* Please allow 3-5 minutes boot up time on first time for initialization
* This is Rooted Android TV build version
* [http://wiki.pine64.org/index.php/NOOB#Flashing_to_eMMC_using_Rockchip_Tools_.28Rock64_Only.29 Guide to flashing eMMC using Rockchip Tools]
* [http://files.pine64.org/os/ROCK64/android/ROCK64_20190618_stock_rooted_android_9.0_emmcboot.img.gz Direct download from pine64.org]
** MD5 (GZip file): FC5F80C3A939AD0F8DCE5B85F22D20A1
** File Size: 544MB

== Android 9.x (No Google Play) ==

http://files.pine64.org/sw/pine64_installer/json/android_9.png

=== Android 9.0 Stock Rooted Image [microSD Boot] using DD method [20190621] ===
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher] or [https://github.com/pine64dev/PINE64-Installer/blob/master/README.md#download PINE64 Installer]
* Please allow 3-5 minutes boot up time on first time for initialization
* This is Rooted Android TV build version
* DD image for 8GB microSD card
** [http://files.pine64.org/os/ROCK64/android/ROCK64_dd_20190621_stock_rooted_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): A250B72CD6AAB24B8156DE08EB15530C
*** File Size: 546MB
* DD image for 16GB microSD card
** [http://files.pine64.org/os/ROCK64/android/ROCK64_dd_20190621_stock_rooted_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 09A6BACD71159853D5E4C6C21C883B0F
*** File Size: 556MB
* DD image for 32GB microSD card
** [http://files.pine64.org/os/ROCK64/android/ROCK64_dd_20190621_stock_rooted_android_9.0_sdboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): C68DC5D96F1C546B96EC690CE7BFE910
*** File Size: 574MB
* DD image for 64GB microSD card
** [http://files.pine64.org/os/ROCK64/android/ROCK64_dd_20190621_stock_rooted_android_9.0_sdboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 4EFC87B4CEE4C7655618DCA95EF7DD0D
*** File Size: 707MB

=== Android 9.0 Stock Rooted Image [microSD Boot] using ROCKChip SDDisk tools method [20190621] ===
* Please unzip first and then using Android tool to flash in
* Please allow 3-5 minutes boot up time on first time for initialization
* This is Rooted Android TV build version
* [http://files.pine64.org/os/ROCK64/android/SDDiskTool_v1.57.zip Rockchip SDDisk Tool ver 1.57]
* [http://files.pine64.org/os/ROCK64/android/ROCK64_20190621_stock_rooted_android_9.0_sdboot.img.gz Direct download from pine64.org]
** MD5 (GZip file): EE00D309745F842213E21B2F1E20C510
** File Size: 539MB

== Android 8.x TV eMMC (preinstalled Google Play Store) ==

http://files.pine64.org/sw/pine64_installer/json/android_8.png

=== Android 8.1. Stock Image [eMMC Boot] using DD method [20180606] ===
* DD image to eMMC module. Highly recommend using [https://etcher.io/ Etcher]
* Please allow 10-15 minutes boot up time on first time for initialization
* [http://files.pine64.org/os/ROCK64/android/rock64_20180606_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): C05846B89A6483DA911CEA604627524F
** File Size: 561MB

=== Android 8.1. Stock Image [eMMC Boot] using ROCKChip tools method [20180606] ===
* Please unzip first and then using Android tool to flash in
* The OTG port located at top USB 2.0 port
* [http://wiki.pine64.org/index.php/NOOB#Flashing_to_eMMC_using_Rockchip_Tools_.28Rock64_Only.29 Guide to flashing eMMC using Rockchip Tools]
* [http://files.pine64.org/os/ROCK64/android/rock64_android8.1_emmc_boot_v1.1.zip Direct download from pine64.org]
** MD5 (XZ file): 9738F060D2F62A83637797363D2B38C9
** File Size: 752MB

== Android 8.x TV ==

http://files.pine64.org/sw/pine64_installer/json/android_8.png

=== Android 8.1. Stock Image [microSD Boot] [20180623] ===
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
* Please allow 10-15 minutes boot up time on first time for initialization
* [http://files.pine64.org/os/ROCK64/android/rock64_20180623_stock_android_8.1_sdboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 85372A568C114ADE7CD9632CEBA193E9
** File Size: 575MB

== Android 7.x eMMC ==

http://files.pine64.org/sw/pine64_installer/json/android_7.png

=== Android 7.1.2 Stock Image [microSD to eMMC] [Rooted] [20171204] ===
* DD image to microSD card. Highly recommend using [https://etcher.io/ Etcher]
** Shorting the eMMC PIN with a jumper as shown on the 1st image of [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]. After power ON the box for 2-3 second, quickly remove the jumper, then it will start writing the new image to the eMMC. Please allow around 1 minute of boot up time before UI is presented via HDMI
* Please allow 10-15 minutes boot up time on first time for initialization
* USB 3.0 patches
* Enable Real Time Clock support for Popcorn Hour Transformer
* [http://files.pine64.org/os/ROCK64/android/rock64_20171204_stock_android_7.1.2_rooted_sd2emmc.img.xz Direct download from pine64.org]
** MD5 (XZ file): 43443467DFCAEDE767556843EB4D6707
** File Size: 558MB
* [[Set MacAddress on ROCK64]]

=== Android 7.1.2 Stock Image [eMMC Boot] [Rooted] [20171204] ===
* Please unzip first and then using Android tool to flash in
* USB 3.0 patches
* Enable Real Time Clock support for Popcorn Hour Transformer
* [http://files.pine64.org/os/ROCK64/android/rock64_20171204_stock_android_7.1.2_rooted_emmc.img.xz Direct download from pine64.org]
** MD5 (XZ file): 7C831F9E6B4311A3B3D4743FBBB628D0
** File Size: 544MB
* [[Set MacAddress on ROCK64]]

== Android 7.x ==

http://files.pine64.org/sw/pine64_installer/json/android_7.png

=== Android 7.1.2 Stock Image [microSD Boot] [Rooted] [20171204] ===
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
* Please allow 10-15 minutes boot up time on first time for initialization
* USB 3.0 patches
* Enable Real Time Clock support for Popcorn Hour Transformer
* [http://files.pine64.org/os/ROCK64/android/rock64_20171204_stock_android_7.1.2_rooted_sdboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 56520ED3DB6E587DA140AD314A055EB2
** File Size: 544MB

== Android TV 7.x eMMC ==

http://files.pine64.org/sw/pine64_installer/json/android_7.png

=== Android TV 7.1 Community Build Image [microSD to eMMC] [v0.3.4-r86] by ayufan ===
* DD image to microSD card. Highly recommend using [https://etcher.io/ Etcher]
** Shorting the eMMC PIN with a jumper as shown on the 1st image of [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]. After power ON the box for 2-3 second, quickly remove the jumper. After boot, it will prompt for confirmation 'Y' to start writing the new image to the eMMC. Then follow the instructions on the screen
* [https://github.com/ayufan-rock64/android-7.1/releases/tag/0.3.4 Release notes on ayufan Android 7.1 github]
* Please allow 5 minutes boot up time on first time for initialization
* [http://files.pine64.org/os/ROCK64/android/android-7.1-rock-64-rock64_atv-v0.3.4-r86-raw_sd2emmc.img.xz Direct download from pine64.org]
** MD5 (XZ file): 6FD1FA4BE87EC2D4E0862F66541BC6F0
** File Size: 716MB
* [[Set MacAddress on ROCK64]]

=== Android TV 7.1 Community Build Image [eMMC] by ayufan ===
* For eMMC flash-all image, please unzip first and then use Android tool to flash in
** [https://github.com/ayufan-rock64/android-7.1/releases/latest Direct download latest release build from ayufan github and look for android-7.1-rock-64-rock64_atv-x.x.x-xx-update.zip]
* [[Set MacAddress on ROCK64]]

== Android TV 7.x ==

http://files.pine64.org/sw/pine64_installer/json/android_7.png

=== Android TV 7.1 Community Build Image [microSD Boot] by ayufan ===
* [https://github.com/ayufan-rock64/android-7.1/releases/latest Direct download latest release build from ayufan github and look for android-7.1-rock-64-rock64_atv-x.x.x-xx-raw.img.gz]

= Android SDK =

=== Android P SDK [v9.0] ===
* [http://files.pine64.org//SDK/ROCK64/ROCK64_SDK_android9.0.tar.gz Direct Download from pine64.org]
** MD5 (TAR-GZip file): 1EAC08942E238293E3AF11C7890DF307
** File Size: 104.34GB
[[Category:Rock64]]